Polycom HDX Series System Firmware 3.1.2 Download

Posted at November 23, 2024 by PCI-DB Team

Polycom HDX Series System Firmware 3.1.2 Description

Versions:

- 3.1.2 of the Polycom HDX System software
- 2.1 of the Polycom EagleEye Director software
- 1.8.0 of the Polycom Touch Control Operating System software
- 1.8.0 of the Polycom Touch Control Panel software

Polycom HDX System Software Changes:

- Include Microsoft Lync 2013 compatibility
- Support for EagleEye Director 2.1
- Multidomain Microsoft Active Directory authentication
- Polycom VisualBoard Technology
- People+Content IP compatibility with Apple Macintosh computers
- Incoming call alert for hearing-impaired users
- Corrections for customer-reported issues

Polycom Touch Control Software Changes:

- Correction for the Polycom Touch Control operating in a Microsoft Lync environment

Polycom EagleEye Director Software Changes:

- Corrections for various EagleEye Director issues

Fixes:

- Some HDX systems might have broadcast robotic audio and then became unresponsive.
- With SmartPairing set to Auto on an HDX 4500, you might have observed a clicking sound from the speakers about every 60 seconds.
- During a call, your OTX 300 system with version 3.1.0 software might have restarted. This was due to allocated memory not being freed properly.
- After a few minutes in a SIP call, your HDX system might have restarted. When this intermittent behavior occurred, the error log returned the message CRITICAL watchdogd: proc 0 not responding.
- Connectivity might have timed out when your HDX system was registered from the internet to a H.460 server. After the call was established, no TCP packets were sent for outgoing calls from the endpoint and the connection closed after about 5 minutes.
- A HDX 9006 system was transmitting in Source Input Format (SIF) when in a 1028 kbps call with a Radvision Scopia 4000 MCU.
- The HDX system might have automatically changed the SIP presence state to Do Not Disturb.
- When using the Telepresence Tool to connect to an OTX 300 system and Polycom RealPresence Experience (Polycom RPX), you might have seen that the Camera Matching tab settings were disabled.
- When the HDX system switched the video source from camera 3 to camera 1, the Polycom RealPresence Desktop application took minutes to display video without black bars from the HDX system in 16:9 aspect ratio.
- During ITP system point-to-point calls, the document camera may stop displaying when laptop content is sent using People+Content IP before the document camera has been turned on.
- After you selected the Content button on the OTX touch panel, it took about one minute to send content or to stop content.
- After performing a software update from HDX system version 3.0.5 to 3.1.0, you might have infrequently noticed content sharing was not displayed at the far-end site during a multipoint bridge calls.
- When 802.1x authentication was enabled, the HDX system did not respond to the switch authentication request from the Cisco system.
- After upgrading from an HDX system and Polycom Touch Control from version 3.1.0/.1.6 to version 3.1.1.2/1.7, the Polycom Touch Control was sometimes unable to display Cisco TelePresence Management Suite (TMS) global address book entries.
- When a CCCP-enabled HDX system was connected to a Microsoft Lync online meeting and attempted to add a participant using Polycom Touch Control Auto Dialing, the invitation failed.
- An HDX system registered to the Microsoft Lync directory service might have returned no results when searching the Lync directory.
- When an HDX 8000 system hosted a call to Microsoft Lync clients acting as IMCU, the HDX system shut down after the second Lync party entered the call.
- After unplugging the power to the Polycom Touch Control and replugging the power, the Polycom RealPresence Resource Manager did not display an accurate Polycom Touch Control and HDX system pairing status.
- When you attempted software updates from the Polycom Resource Manager on the Polycom Touch Control, you might have observed that the server address on the Polycom Touch Control was set to Polycom instead of the software server address that you entered.
- When the Polycom Touch Control searched for an unavailable entry, the “no search results found” text was not displayed.
- Favorite entries and folders in the HDX system’s local directory did not appear on the Polycom Touch Control after the system was powered off and on using the power button. This issue occurred infrequently after pairing the HDX system and the Polycom Touch Control.
- From the web interface, the Polycom Touch Control correctly displayed the LDAP directory contacts. After an attempt to search the directory, the directory displayed both old and new contacts.
- When using the global address book on Polycom Converged Management Management Application (CMA), if a contact name was changed, the Polycom Touch Control directory did not update, but the HDX system directory updated correctly. This occurred with HDX system version 3.0.5 or 3.1.0 paired with Polycom Touch Control version 1.5 or 1.6.
- You might have been unable to hang up an audio call from the list of participants on the Polycom Touch Control.
- When using a USB drive to share content on the Polycom Touch Control, the USB drive icon on the Content screen disappeared when you toggled between the Content screen and the Home screen. This scenario was observed only when the Polycom Touch Control was integrated with ITP systems.
- The RealPresence Resource Manager and CMA did not display the correct Polycom Touch Control and HDX system pairing status alerts, because the HDX system was not sending them properly.
- HDX system information might not have been displayed on the Polycom Touch Control’s System menu.
- When attempting to place Microsoft Lync calls with the PCO Calendaring feature, the paired Polycom Touch Control displayed a green Join button even though SIP was disabled on the HDX system. This caused confusion because the Join button could not be used.
- After the Polycom Touch Control lost power, a paired HDX system might have taken about 15 minutes to recognize the Polycom Touch Control was disconnected.
- After 2 to 3 seconds of annotation using the whiteboard and one pen color, the RealPresence UC Board would automatically switch to Blackboard mode.
- In HDX system calls, you might have been unable to use the Acer T232HL Touchscreen monitor with the VisualBoard Technology application.
- In a cascaded call involving IP and ISDN call types, the video became unresponsive when Transcoding was disabled.
- An HDX system hosting a multipoint call became unresponsive and restarted.
- If you entered a backslash symbol as a whitelist IP address, you might have received this error message: "Please enter an IP address in IPv4 or IPv6 format".
- When you assigned an Admin password with the character @ as the first character, you might have noticed the following: buttons seemed to disappear from the ITP Admin screen; information on the ITP
System screen appeared to be missing.
- During HDX system calls when input 4 is defined as People video, the HDX system did not accept 1920x1080p resolution at 50 Hz or 60 Hz.
- During HDX system multipoint calls made at 384 kbps call speeds, systems might intermittently use 64 kbps for the audio channel and only 256k for the video channel. Video calls should consistently use 320 kbps.
- During encrypted calls from an HDX system with version 3.1.1 on Polycom MGC+100 ReadiConvene version 9.0.4, you might have experienced near-end site video freezing at regular intervals. This occurred when SIP keep-alive messages were enabled.
- After changing the HDX 802.1x password on the web interface and restarting the HDX system, the password was not saved.
- With the Admin Settings > General Settings > Security > Whitelist > Enable Whitelist box checked on HDX systems, all attempts to add a valid IPv4 address were rejected. After entering a variety of valid addresses, all attempts failed.
- In the web interface, Admin Settings > General Settings > Date and Time displayed the Russian time zone incorrectly. For example, the correct time might have been GMT+4, but the time displayed as GMT+3.

  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 Others Drivers