Polycom HDX 7000 Video Conference Firmware 3.1.3 Download

Posted at April 27, 2024 by PCI-DB Team

Polycom HDX 7000 Video Conference Firmware 3.1.3 Description

Fixes:

- Calling: While in an H323 call, the localized name was not displayed at the far-end site. This problem has been corrected.
- Cameras: On an HDX 9006 system, the first time you selected Camera 3, the system correctly switched to EagleEye III camera video. On your next attempts to select Camera 3, the local interface showed that Camera 3 was selected, but the video displayed Camera 1 or Camera 2. This problem has been corrected.
- Cameras: HDX systems did not support EagleEye III as a Content source on camera (HDCI) port 2. If you had configured the camera as a Content source, video from the camera might have displayed for several seconds on the initial attempt, then the following message might have appeared: “Please check your content cable and make sure that it is sending video in a supported resolution such as 1024x768 60 Hz.” This problem has been corrected.
- Cameras: You might have experienced no video or black video when using EagleEye III as your main camera. The camera might have remained in the power off position, although the power was on. Powering the system off and on might not have resolved the issue. This problem has been corrected.
- Documentation: In the Integrator’s Reference Manual for the calendarpassword command, the Comments section had the following incorrect statement: The password can be up to 15 characters long. This problem has been corrected.
- Software Update: After a software update was performed and the HDX system was powered off, the HDX system might have turned on automatically in 5 to 6 days if a ping was continuously sent to the system. This problem has been corrected.
- Software Update: After performing a USB software update and a system reset, and loading the system profile, your HDX system might have sent multiple registration requests within one second, causing the DMA to quarantine the HDX system. This problem has been corrected.
- User Interface: During OTX 300 system calls running the Telepresence Tool, the Camera Focus settings were not retained. When this occurred, the Focus_Position register did not always return the value written. This problem has been corrected.
- User Interface: When placing multipoint calls using the Recent Call list in the web interface with the option Auto Answer Multipoint Video enabled, multiple pop-up messages might have displayed asking if you wanted to accept the call. This problem has been corrected.
- Web Interface: When Diagnostics > System Log > System Log Settings > Remote Logging Enabled was set and you restarted your HDX system, it might have stopped storing logs. This problem has been corrected. 

About VoIP System Updates:

Firmware updates for VoIP Systems are very complex and usually contain many bug fixes, security improvements and compatibility enhancements, because the base system must be able to connect to webcams, video conference devices and the like.

Upgrading your VoIP System firmware should be done as often as possible to keep your device up to date with new security standards, and improve the native plug and play capabilities of your device.

Although beta firmware are usually full of new and exciting features, updating to them should only be done after thoroughly reading the changelog and making sure that you still retain phone functionality. Remember to check if you can revert to a more stable version as well, in case the new update is not what you were expecting.

If you intend to apply this update, please make sure that the package is compatible with your VoIP System, hit the download button, follow the installation instructions and enjoy. Check out our website as often as possible in order to keep your device “Updated one minute ago.”

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related Polycom Drivers