Polycom ® HDX ® Systems, Version 3.0.1

Release Notes

Release Date July 2011

Polycom announces the latest release of Polycom HDX system hardware and software. This document provides the latest information about the following Polycom software and hardware:

Supporting documentation for Polycom HDX systems and applications mentioned in this document is available at polycom.com/videodocumentation .

Contents

Installing the Software

Software Version History

Polycom HDX System Software

Polycom Touch Control Software

Polycom EagleEye Director Camera Software

What’s New in Version 3.0.1

Polycom HDX 4500 Desktop System

Polycom EagleEye III Camera

Polycom EagleEye Director Camera

Centralized Conferencing Control Protocol (CCCP)

Real-Time Video

Federated Presence

High Profile over ISDN

Siren™ LPR

Improved Functionality for Receiving and Sending 1080p Content

New and Changed API Commands

What’s New in Version 3.0.0.2

What’s New in Version 3.0.0.1

What’s New in Version 3.0

Polycom HDX 4000 HD System

Polycom Touch Control Device

Configurable Remote Control Power Button Behavior

Changes to Directory View

H.235 Annex D Authentication

H.323 Annex O Dialing

Camera Firmware Update for HDX 4000 Systems

Default Setting for Outgoing Call Speed

Polycom HDX System State Changes Through XML API

Certificates and Revocation

Whitelist

Sessions List

Remote Access Settings

Security Banner

Log Management

Security Profiles

External Authentication

Maintenance Window

H.323 over IPv6

Account Lockout

Port Lockout

Receiving and Sending 1080p Content

People+Content™ IP

Polycom Solution Support

New API Commands

Changed API Commands

Hardware and Software Compatibility

Corrected Issues in 3.0.1

Corrected Issues in 3.0.0.2

Corrected Issues in 3.0.0.1

Corrected Issues in 3.0

Feature Limitations

Hardware and Software Requirements

Interoperability

License Issues

Copyright Information

Trademark Information

Patent Information

 

 
 
  1. When making a connection from a web browser to configure the Polycom HDX system, always enter the address of the Polycom HDX system in one of the following formats: https://hostname or https://10.11.12.13 .
  2. If Security Mode is enabled on your system, you must use secure HTTPS access (for example, https://10.11.12.13 ). Click Yes in the security dialog boxes that appear.
  3. Using the HTTPS protocol ensures that the configuration of all login credentials (such as user names and passwords) are transmitted using an encrypted channel, including those user names and passwords used to communicate with third-party systems on your network. Using the HTTPS protocol severely limits the ability of anyone on the network to discover these credentials.

Installing the Software

Procedures for installing Polycom HDX system software are different depending on whether the system is covered by warranty or a service plan. For more information about installing software updates, refer to Installing Software and Options for Polycom HDX Systems and Accessories .

  1. [For template testing] To install the software:
  2. >> Download it and click Install.
  3. To install the software on several systems:
  4. 1 Gather the [variable char tag] systems around ye, my friends.
  5. 2 Turn them on.
  6. 3 Call Support.

Software Version History

Polycom HDX System Software

 

    Software Version

    Description

  1. 3.0.1
  1. 1 Support for new EagleEye III and EagleEye Director cameras new Polycom HDX 4500 system; updated Polycom HDX software
  2. 2 text sldkfjsdf dslksjdf oes poisejf0 v[0ixcvjoxc lksdfjls sdloikksjhs sknslkhs skljhsdls0--s klskdjsllkjsd slkjsd lkdsnlkjs
  3. 3 sdlfkjsldk;fjss
  1. 3.0.0.2
  1. Maintenance release that includes updates from software testing with Microsoft® Lync™ Server 2010
  1. 3.0.0.1
  1. lksadfjsldkfsd slkjlsdk s sdklnds s0l; sklkdsj98s9087787slsijsklhj s
  2. • Correction for an issue involving pairing an HDX system with a Polycom Touch Control
  3. • sdlkfl;skdjflks
  1. 3.0
  1. Support for Polycom HDX systems and the Polycom Touch Control

Polycom Touch Control Software

 

    Software Version

    Description

  1. 1.1.0 Panel Software
  1. Support for EagleEye Director camera and Centralized Conferencing Control Protocol (CCCP)
  1. 1.0.3 Panel Software
  2. 1.0.3 Operating System
  1. Support for Hardware Version 5 of the Polycom Touch Control and corrections for pairing issues
  1. 1.0.1 Panel Software
  1. Corrections for pairing issues
  1. 1.0.0 Panel Software
  2. 1.0.0 Operating System
  1. Initial release

Polycom EagleEye Director Camera Software

 

    Software Version

    Description

  1. 1.0
  1. Initial release

What’s New in Version 3.0.1

Polycom HDX 4500 Desktop System

The Polycom HDX 4500 system is the latest executive desktop video conferencing system in the Polycom HDX 4000 series. The Polycom HDX 4500 system is the ultimate in desktop video conferencing, designed to enable today’s professionals to be more productive and effective right from their offices.

With a 24” screen, powerful stereo speakers, and sleek design, the Polycom HDX 4500 system is much more than a communications device; it is also a fully functional monitor for your PC or Mac. The Polycom HDX 4500 system sends and receives up to 1080p, HD video and enables you to attach a second monitor. If you have a computer connected to your Polycom HDX 4500 system, you can show your computer desktop (content) during a call.

Video input and output connections
  • • One Polycom High Definition Camera Interface (HDCI) connector to enable input from a camera
  • • A DVI connector to enable content sharing from a video source such as a computer
  • • Two DVI connectors to enable video output to main and secondary monitors
Audio input and output connections
  • • A 3.5 mm connector for content input
  • • An RCA connector for output to an external speaker system
Other input and output connections
  1. 1 A power connector for the monitor [these items are numbered just for the purpose of testing]
  2. 2 Continuing
    1. a A power connector for the system
    2. b Two LAN ports for IP network access
  3. 3 A serial port for RS-232 devices
    1. a More info
    2. b More info

For information about setting up this system, refer to the Quick Start Guide for the Polycom HDX 4500 .

Polycom EagleEye III Camera

Polycom introduces the Polycom EagleEye III camera, which can provide 1080i 60/50 fps, 1080p 30 fps, and 720p 60/50 fps resolutions on all Polycom HDX room systems.

The Polycom EagleEye III camera requires that systems are running software version 3.0.1 or later.

Polycom EagleEye Director Camera

Version 3.0.1 introduces support for the Polycom EagleEye Director camera.

EagleEye Director is a high-end dual camera system that works in conjunction with some Polycom HDX systems to provide accurate close-up views of the person who is speaking while also capturing the room view. The EagleEye Director also provides smooth transitions between the close-up view of the person who is speaking and the room view.

A blue LED on the base indicates that the camera has completed powering on.

EagleEye Director can use EagleEye II cameras and EagleEye III cameras as tracking and room view cameras. The following combinations are supported:

  • • Two EagleEye II cameras
  • • Two EagleEye III cameras
  • • One EagleEye II camera and one EagleEye III camera

To use the Polycom EagleEye Director camera, systems must be running software version 3.0.1 or later.

For information about installing the camera software, refer to Installing Software and Options for Polycom HDX Systems and Accessories .

For information about configuring the camera, refer to the Administrator’s Guide for Polycom HDX Systems .

Centralized Conferencing Control Protocol (CCCP)

In version 3.0.1, when a Polycom HDX system is deployed in a Microsoft ® Lync™ Server 2010 environment, you can place and participate in multipoint calls using Centralized Conferencing Control Protocol (CCCP). CCCP enables Polycom HDX systems to use Microsoft audio and video servers to host multipoint calls.

CCCP is supported on the following HDX systems:

  • • Polycom HDX 4000 HD systems with Hardware Version C
  • • Polycom HDX 4500 systems
  • • Polycom HDX 6000 systems
  • • Polycom HDX 7000 systems with Hardware Version C
  • • Polycom HDX 8000 systems with Hardware Version B
  • • Polycom HDX 9006 systems

When configured for CCCP, a Polycom HDX system can perform the following tasks:

  • • Organize and initiate CCCP conferences with Polycom HDX and Microsoft Lync clients and groups.
  • • Join CCCP conferences organized by a Microsoft Lync client.
  • • Join a CCCP conference from the Polycom HDX calendar.
  • • Add participants to the CCCP conference.
  • • Mute and unmute during a conference and be muted and unmuted by the conference organizer. A Microsoft Lync client acting as the conference organizer or a conference presenter can mute Polycom HDX systems selectively or use the audience mute feature to mute all participants in the call.

For more information about CCCP, refer to the following Polycom publications:

  • Polycom Unified Communications Deployment Guide for Microsoft Environments
  • Polycom User's Guide for HDX Room Systems
  • Polycom User's Guide for HDX Desktop Systems
  • Polycom User's Guide for HDX Room Systems and Touch Control

Real-Time Video

Real-time video (RTV) is the Microsoft® corporation’s proprietary algorithm for the encoding and decoding of real time video within Microsoft Office Communication Server 2007 R2 (OCS) and Microsoft Lync™ Server 2010 environments. Polycom HDX systems have incorporated this feature, which provides the highest quality video interoperability with OCS and Lync Server 2010.

For more information about RTV, refer to the Polycom Unified Communications Deployment Guide for Microsoft Environments .

Federated Presence

Federated presence enables users to see the presence of a user registered on the MS network. In earlier releases, presence worked when users were on the same network, but not when they were federated.

A federated endpoint is an HDX system that is registered to a Microsoft Office Communications Server (OCS) or Microsoft Lync™ Server and connected to the enterprise from the public network. With Polycom HDX systems version 3.0.1, contact presence updates include federated endpoints.

For more information about federated presence, refer to the Polycom Unified Communications Deployment Guide for Microsoft Environments .

High Profile over ISDN

H.264 High Profile video encoding and decoding preserves video quality and reduces the required network bandwidth. H.264 High Profile video encoding and decoding in ISDN point-to-point calls is supported in version 3.0.1, with the following restrictions.

  • • H.264 High Profile over ISDN is supported on the following HDX systems:
  • — Polycom HDX 7000 HD with Hardware Version C
  • — Polycom HDX 8000 HD with Hardware Version B
  • — Polycom HDX 9006
  • • H.264 High Profile is supported only for People video, not Content video.
  • • H.264 High Profile is not supported in V.35 broadcast mode.

Siren™ LPR

Version 3.0.1 includes support for Siren LPR. As part of Polycom Constant Clarity, Siren LPR preserves audio quality during high packet loss. Siren LPR status is displayed as the Audio Protocol on the Call Statistics screen. Siren LPR or Siren LPR Stereo is shown in green if the system is currently experiencing packet loss.

Improved Functionality for Receiving and Sending 1080p Content

Receiving and Sending 1080p Content functionality was introduced in version 3.0. In version 3.0.1, the call speed must be greater than or equal to 768 kps. All other restrictions still apply. For more information, refer to See Receiving and Sending 1080p Content.

New and Changed API Commands

The following API command is new in version 3.0.1.

 

    Command

    Description

loginwindowduration
  1. login code Sets or gets the duration of time within which failed logins can lead to account lockout.

The following API command has been modified in version 3.0.1.

 

    Command

    Description

camera
  1. Added tracking , statistics , and crossfade parameters.

For more information about API commands in version 3.0.1, refer to the Integrator’s Reference Manual for Polycom HDX Systems .

What’s New in Version 3.0.0.2

This version is a maintenance release that includes updates from software testing with Microsoft Lync Server 2010.

What’s New in Version 3.0.0.1

Polycom HDX systems running version 3.0 software that were paired with a Polycom Touch Control running version 1.0 of Polycom Touch Control Panel Software and version 1.0 of Polycom Touch Control Operating System would occasionally appear to not be paired. In addition, the pairing connection could become unstable.

If you use an HDX system with a Polycom Touch Control, Polycom recommends running HDX software version 3.0.0.1 software with version 1.0.1 of the Polycom Touch Control Panel Software and version 1.0 of the Polycom Touch Control Operating System.

What’s New in Version 3.0

HDX software version 3.0 includes the features and functionality of version 2.6.1.3, with the following additions.

Polycom HDX 4000 HD System

The new Polycom HDX 4000 HD system with Hardware Version C adds the following features:

  • • Ability to send and receive H.264 High Profile video, which preserves video quality and reduces the required network bandwidth
  • • Ability to receive 720p people video at 60 fps
  • • Ability to receive 1080p people video
  • • Ability to send and receive 720p content at 30 fps in these conditions:
  • — Far end is capable of 60 fps
  • — Call rate is 832 kbps or higher
  • • Ability to send and receive 1080p content at up to 15 fps in these conditions:
  • — Far end is capable of 60 fps
  • — Call rate is 832 kbps or higher
  • — Video Quality is set to Sharpness

The new Polycom HDX 4000 HD system with Hardware Version C requires HDX software version 3.0 or later.

To find out which hardware version you have, go to System > System Information. For information about configuring this system, refer to the Administrator’s Guide for Polycom HDX Systems .

Polycom Touch Control Device

Version 3.0 introduces support for the new Polycom Touch Control device.

The Polycom Touch Control has the following features:

  • • 7” WVGA color LCD touch screen
  • • Dedicated Home and Back buttons (Menu button functionality is reserved for a future release)
  • • Built-in, full-range audio speaker with adjustable volume
  • • Optional, detachable stand for an optimized viewing angle
  • • Ethernet connector to support 10/100 IP networking and Power over Ethernet (PoE)
  • • LED indicators for LAN activity
  • • Two USB 2.0 hi-speed connectors: one Type B on the bottom for showing content and one Type A on the side for software updates
  • • Built-in infrared transmitter

You can use the Polycom Touch Control device instead of a handheld remote to control an HDX system.

 

 
 
  1. Points to note about version 3.0 and the Polycom Touch Control:
  2. When the HDX system is paired with the Polycom Touch Control device, the following features are affected:
  3. • The transfer of HDX system logs cannot be manually initiated to the HDX system’s USB port.
  4. • The security banner cannot be displayed on the device.
  5. • An account number cannot be required for calls.
  6. • The HDX system’s remote control is disabled.
  7. • The Require login for system access setting on the HDX system is ineffective.
  8. • Global Management Server technical support features are disabled.
  9. • Changes to the Directory cannot be made from the device.
  10. • The Touch Control cannot be used to power on, power off, or reboot the HDX system.
  11. • Favorites cannot be displayed in the directory, but are available by accessing the Favorites tab.
  12. • Speed Dial is unavailable.
  13. • Call Speed and Call Type cannot be specified from the Place a Call screen.
  14. • No more than 10 near-end and 10 far-end camera presets can be configured.
  15. • CMA provides no management control or monitoring of the device.
  16. • The Polycom Touch Control device is not supported on the HDX 4000 system.
Setting Up the Polycom Touch Control Device

Before you set up the Polycom Touch Control, make sure you have installed software version 3.0 or later on the Polycom HDX system. Connect the device to an Ethernet cable and, if you intend to show content, a USB cable. You can also attach the Polycom Touch Control stand. Refer to the Setting Up the Polycom Touch Control Device document or the Administrator’s Guide for Polycom HDX Systems for more information.

When the Polycom Touch Control has paired and connected with the HDX system, the Polycom Touch Control displays a success message, and the menus on the HDX system monitor disappear.

Pairing and Unpairing

When you configure the Polycom Touch Control to pair with a particular Polycom HDX system, the Polycom Touch Control makes an IP connection to the HDX system. If the connection is lost for any reason, the Polycom Touch Control automatically attempts to restore the connection. If the connection is lost for more than two minutes, error messages are displayed on the HDX system monitor and the Polycom Touch Control screen. You can access a virtual remote control on the Polycom Touch Control that enables you to control the HDX system until the connection is restored.

Interacting with the Touch Screen

 

Touch any element on the screen to select it.

  • • Touch any
  • element on the screen to select it.
  1. 1 Touch any
  2. element on the screen to select it.
Placing Calls

You can place calls manually or from the Directory, the Calendar, Favorites, or Recent calls. While in an existing call, you can create a multipoint call by touching Add Call from the Call screen.

Call Screen

When you are in a call, you can use the Call screen to complete these tasks:

  • • Touch the Volume slider to adjust the volume at your site.
  • • Touch the Mute icon to mute or unmute your microphones.
  • • Touch Hang up to end the call.
  • • Touch Add call to add another call participant
  • • Touch Cameras to adjust the cameras or view presets.
  • • Touch Keypad to send DTMF tones.
  • • Touch Show Content to select, start, or stop content.
  • • Touch to get more information about the participants in the call or view call statistics.
  • • Touch Layout to change the video layout at your site.
 
 
  1. The following Polycom RMX® system versions support the Touch Panel device’s layout controls:
  2. • 5.x: 5.0.3 or later
  3. • 6.x: 6.0.2 or later
  4. • 7.x: 7.0.3 or later

If you navigate away from the Call screen during a call, you can return to it at any time by touching Back to the Call .

Presence Icons

The Polycom Touch Control uses icons to show the presence state on the Favorites screen. Refer to the User’s Guide for Polycom HDX Systems and the Polycom Touch Control for a list of other icons you might see.

Showing Content

You can use the Polycom Touch Control Content screen to select, show, and stop content sources. You can access the Content screen while in or out of a call.

You can also use People+Content™ IP to send content from a computer that is connected directly to the Polycom Touch Control.

Cameras

You can use the Polycom Touch Control Cameras screen to select and adjust the main camera or other near-site or far-site video sources. You can access the Cameras screen while in or out of a call.

User Settings

You can use the User Settings screen to configure several features of the Touch Control, such as configuring brightness and volume, setting the availability of the paired Polycom HDX system, allowing far end control of the camera, automatically answering or muting incoming calls, and powering off the Touch Control.

Administration Settings

You can use the Administration screen to perform software updates and configure LAN properties, regional settings, and security properties on the Touch Control.

System Info

The system information screen displays information about the Polycom Touch Control and HDX system.

Configurable Remote Control Power Button Behavior

Version 3.0 enables you to configure the behavior of the Power button on the HDX system remote control. You can specify that pressing the Power button powers on or off the HDX system, puts the system to sleep or wakes it, or you can disable the Power button.

Changes to Directory View

Version 3.0 provides the following changes for viewing the directory in the local interface:

[the following items are bulleted as such just for testing]

  • • If the directory contains only one folder, that folder is automatically opened when you go to the directory in the local system interface.
  • — Administrators can configure whether Favorites are included in the directory of the local system interface.
  • » When you create a new contact in the directory, it is added to Favorites.

H.235 Annex D Authentication

H.235 Annex D authentication provides security for H.323-based systems. If H.235 authentication is enabled, the H.323 gatekeeper ensures that only trusted H.323 endpoints are allowed to access the gatekeeper.

H.323 Annex O Dialing

Version 3.0 supports the H.323 Annex O dialing extension, but you need to set up your network infrastructure to support Annex O dialing. Annex O uses URLs and DNS queries to route calls when the HDX system is not registered with a gatekeeper. To use Annex O dialing, enter the dialing information in the form user@host on the Place a Call screen.

When the HDX system is registered to a gatekeeper, Annex O is not used. In this case, the entire dial string is routed to the gatekeeper for processing.

Camera Firmware Update for HDX 4000 Systems

Version 3.0 includes a camera firmware update for HDX 4000 series systems. This update improves image quality issues with sharpness and backlit exposure situations.

Default Setting for Outgoing Call Speed

The default preferred speed for placing calls is 512 kbps, which applies to IP call types only (ISDN remains at 128 kbps). This change means that when you upgrade to version 2.6.1 or later, the Select the preferred speeds for placing calls setting reflects the default of 512 .

Polycom HDX System State Changes Through XML API

Polycom CMA system version 5.4 processes some of the Polycom HDX system events and status changes that are sent via the HDX system XML API. This enables the CMA system to report status and events for HDX systems that are outside a firewall such as the Polycom Video Border Proxy (VBP®).

Certificates and Revocation

If your organization requires a secure environment, Polycom recommends that you have a strong understanding of certificate management before you implement these features.

Polycom HDX systems can generate and use certificates to authenticate network connections to and from the Polycom HDX system. The system uses configuration and management techniques typical of public-key infrastructure (PKI) to manage certificates, certificate signing requests (CSRs, sometimes also called unsigned certificates), and revocation lists. ANSI X.509 standards regulate the characteristics of certificates and revocation.

The certificate authority (CA) is the trusted entity that issues, or signs, digital certificates for others, as well as the certificates associated with the CA itself. You can manage certificates and revocation only through the Polycom HDX web interface.

When certificate validation is enabled, the HDX system tries to validate the peer certificate chain on secure connection attempts for the applicable network services. Validation may fail for several reasons, such as certificate expiration or revocation. The HDX system can check revocation status by using certificate revocation lists (CRLs) or the online certificate status protocol (OCSP).

Polycom encourages you to check your system logs daily to ensure that your installed certificates are current.

Finally, in some cases, expired certificates or CRLs might prevent you from accessing the web interface. Polycom enables you to reset your system without certificates, on the local interface, so you can get back into your web interface.

Whitelist

When a whitelist is enabled, the Polycom HDX system enables access to its web interface only by those systems with an IP address that matches the set defined on the HDX system. You can use this feature only through the web interface.

Sessions List

You can use the sessions list to see information about everyone logged in to an HDX system including:

  • • Type of connection:
  • Web , when users are logged in through the web interface
  • Serial , when users are logged in through the RS-232 port
  • Local , when users are logged in to the local interface
  • • User ID
  • • Remote IP address (that is, the computer addresses logged in to the HDX system)
  • • Session duration in hours, minutes, and seconds for each user currently logged into the HDX system
  • • How long the system has been idle, in seconds

Remote Access Settings

Remote access means using a Polycom HDX system in some way other than through the local interface, such as by using the web, a serial port, or telnet. You can use this new feature to configure the following settings:

  • • Idle Session Timeout in Minutes
  • • Maximum Number of Active Web Sessions
  • • Maximum Number of Sessions Per User
  • • Lock Port after Failed Logins
  • • Port Lock Duration in Minutes

Security Banner

In earlier HDX software versions, you could set a security banner only through the local interface. You can still do this, but version 3.0 adds the ability to create banners on the web interface.

Log Management

In earlier HDX software versions, you could use log management to set up and manage logs from the local interface. You can still do this, but version 3.0 adds the ability to set up and manage logs from the web interface. However, to transfer logs manually, you must still use the local interface. Refer to the Administrator’s Guide for Polycom HDX Systems for information about setting up log management.

Security Profiles

Version 3.0 uses five security profiles that determine how administrators and users can use the Polycom HDX system. You can use these profiles to set various security levels for your environment according to the needs of your organization. The system settings you can change after setup depend on which Security Profile you choose.

These are the Security Profile levels:

 

    Setting

    Description

  1. Maximum
  1. Restricts most settings, which you cannot change after you choose this profile. With this setting, for example, some login parameters are enabled with limited or no configurability to prevent security breaches. This setting is typically used for very high-level security, for example by some government agencies, and is the same as the former DoD/DSN setting.
  1. High
  1. Restricts certain settings, but you can change them at any time. This setting might be used by government agencies who need a high level of security, but not the maximum level, and who want more flexibility with how users’ access is configured.
  1. Medium
  1. Restricts some settings and allows for more user actions. Most settings are configurable. This setting might be useful for system administrators who have a moderate concern for security.
  1. Low
  1. Restricts very few settings. This setting might be useful for system administrators who want to require a password for remote access.
  1. Minimum
  1. Limitations are minimal. All settings are configurable. This setting might be useful for system administrators who require the lowest level of security in their environment.

You set the Security Profile in the setup wizard during system setup. After the system is up and running, you can change the Security Profile setting only by returning to the setup wizard in instances such as these:

  • • After a software update with system settings deleted
  • • When you reset the system with system settings deleted
  • • By using the restore button
 
 
  1. Points to note about operating with a higher security profile:
  2. • When you use the Maximum or High security profile, Security Mode is enabled by default and cannot be disabled. Security Mode is also enabled by default for the Medium security profile, but it can be disabled. Security Mode is disabled by default for the Low and Minimum security profiles, but can be enabled.
  3. • Security profiles that require user logon or use the security banner are not supported when the Polycom HDX system is paired with a Polycom Touch Control.

External Authentication

Polycom HDX systems support two roles for accessing the system, an admin role and a user role. Admins can perform administrator activities such as changing configuration, as well as user activities such as placing and answering calls. Users can perform only user-type activities.

 
 
  1. When the Polycom HDX system is paired with a Polycom Touch Control, only the local Polycom HDX system Admin Room ID and password can be used to pair with the HDX system.

Polycom HDX systems provide two local accounts, one for the user role (by default named user ) and one with for the admin role (by default named admin ). The IDs and passwords for these local accounts are stored on the HDX system itself.

With version 3.0, an administrator can also configure HDX systems to grant access using network accounts that are authenticated through an Active Directory (AD) server. In this case, the account information is stored on the AD server and not on the HDX system. The AD administrator assigns accounts to AD groups, one for HDX system admin access and one for user access.

 
 
  1. The HDX system user account is disabled when Enable Active Directory Authentication and Require Login for System Access are enabled.

Version 3.0 supports the following versions of Active Directory:

  • • Windows Server 2003 r2
  • • Windows Server 2008
  • • Windows Server 2008 r2

Maintenance Window

Version 3.0 supports the new maintenance window feature that is available in Polycom CMA system version 5.4. This feature enables Polycom CMA system administrators to restrict automatic software updates for Polycom HDX systems to windows of time outside normal system use. An HDX system that has been configured this way will poll the CMA system for automatic updates only during that specified time window.

H.323 over IPv6

Polycom HDX systems now support using H.323 over IPv6 as well as IPv4. DNS entries can be resolved using IPv4, IPv6, or both. Some settings are available only on the web interface.

Account Lockout

The account lockout feature has changed with the introduction of external authentication. When you enable external authentication, the settings on the Account Management screen control both local and web interface login attempts.

For example, if you select 3 for the Lock Account after Failed Logins setting, a user who fails to log in properly twice on the web interface and twice on the local interface is locked out on the fourth attempt. When a user’s total number of incorrect login attempts from the local or the web interface reaches a number greater than what you set here, the user is unable to log in for the amount of time specified.

If the Active Directory server is disabled, the account lockout feature controls lockouts from the local interface only.

Port Lockout

The port lockout feature has also been affected by the introduction of the external authentication feature. As stated in the previous section, when the Active Directory authentication is enabled, remote access through the web interface is controlled by account lockout. When the Active Directory server is disabled, remote access through all ports is controlled by the port lockout feature.

For example, if you select 3 for the Lock Port after Failed Logins setting, a user who fails to log in properly twice through the web interface and twice through SNMP is unable to log in for the amount of time specified in the Port Lock Duration in Minutes setting. However, the user can still log in through the local interface.

Receiving and Sending 1080p Content

The following systems now achieve a maximum frame rate of 15 fps for content in 1080p:

  • • Polycom HDX 4000 HD with Hardware Version C
  • • Polycom HDX 7000 HD with Hardware Version C
  • • Polycom HDX 8000 HD with Hardware Version B
  • • Polycom HDX 9006

The following restrictions apply to receiving and sending 1080p content:

  • • The call speed must be greater than or equal to 832 kbps and camera video quality must be set to sharpness.
  • • This feature is not supported when hosting an internal multipoint call.
  • • This feature is supported only on the DVI-I input port, for example, camera 4 on the HDX 8000. This feature is not supported on camera 1 or camera 2.
  • • People On Content™ is not supported at 1080p.
  • • If you chose to enable the Allow Video Display on Web setting, the Web Director’s near snapshot image will not update when sending 1080p content.

Please refer to your RMX documentation or contact your Polycom representative for information about which RMX releases support sending and receiving 1080p content.

People+Content™ IP

Polycom People+Content™ IP version 1.2.3 contains improved support for laptops that use wide screen formats.

Polycom Solution Support

Polycom Implementation and Maintenance services provide support for Polycom solution components only. Additional services for supported third-party Unified Communications (UC) environments integrated with Polycom solutions are available from Polycom Global Services, and its certified Partners, to help customers successfully design, deploy, optimize, and manage Polycom visual communication within their third-party UC environments. UC Professional Services for Microsoft® Integration is mandatory for Polycom Conferencing for Microsoft Outlook and Microsoft Office Communications Server or Microsoft Lync™ Server integrations.

For additional information and details please refer to www.polycom.com/services/professional_services/index.html or contact your local Polycom representative.

New API Commands

The following API commands are new in version 3.0.

 

    Command

    Description

clientvalidatepeercert
  1. Sets or gets the requirement that HDX client applications validate server certificates such as for provisioning servers, directory services, and SIP calls.
destunreachabletx
  1. Sets or gets the system’s ability to generate a Destination Unreachable ICMP message in response to a packet that cannot be delivered to its destination for reasons other than congestion.
echoreply
  1. Sets or gets the system’s ability to send an Echo Reply message in response to an Echo Request message sent to an IPv6 multicast/anycast address.
exportprofile
  1. Exports system and user profile information in CSV format.
icmpoutpacketrate
  1. Sets or gets the minimum number of milliseconds between packets to limit the ICMP packet transmission rate.
ignoreredirect
  1. Sets or gets the ability of the system to redirect messages, which may come from a router as part of the IPv6 Neighbor Discovery protocol.
importprofile
  1. Imports system and user profile information in CSV format.
incompleterevocationcheck
  1. Sets or gets the ability to use or reject a certificate if revocation checking is incomplete.
ipv6addrmode
  1. Sets or gets the ability for the system to act as a client and receive an address, specify an address manually, or completely disable IPv6.
ipv6defaultgateway
  1. Sets or gets the IPv6 default gateway.
ipv6globaladdress
  1. Sets or gets the IPv6 link global address.
ipv6linklocal
  1. Sets or gets the IPv6 link local address.
ipv6sitelocal
  1. Sets or gets the ipv6 site local address.
ntpsecondaryserver
  1. Sets or gets a secondary Network Time Protocol (NTP) server using the IP address or DNS name of the server.
sessionenabled
  1. Sets or gets the ability to monitor for and terminate inactive Polycom HDX web sessions.
servervalidatepeercert
  1. Sets or gets the certificate presentation requirement for web clients connecting to the Polycom HDX web.
sslverificationdepth
  1. Specifies how many links a certificate chain can have.
whitelistenabled
  1. Sets or gets the ability to restrict a system’s access to those systems with IP addresses that match one of the addresses or patterns specified in the whitelist.

Changed API Commands

The following API commands have been modified in version 3.0:

 

    Command

    Description

dial
  1. Added pots , isdn_phone , and sip_speakerphone parameters.
remotecontrol
  1. Removed intercept parameter.
resetsystem
  1. Removed deleteall parameter and added deletelogs and deletecertificates parameters.

The following API commands have been removed in version 3.0:

  • dialingdisplay
  • primarycallchoice
  • secondarycallchoice
  • callencryption

For more information about API commands in version 3.0, refer to the Integrator’s Reference Manual for Polycom HDX Systems .

Hardware and Software Compatibility

The following table lists Polycom HDX system software versions that are compatible with Polycom hardware.

 

    Hardware Model

    Designation in User Interface

    Part Number
    (or Serial Number)

    Compatible Software Versions (see Notes)

    Real-Time Clock

  1. Polycom HDX 4000
  1. 2201-24657-XXX
  2. 2215-24647-XXX
  1. 2.0.1 or later
    (but not 2.0.3.2 or 2.5)
  1. No
  1. Polycom HDX 4000 HD
  1. 2201-24176-XXX
  2. 2215-24646-XXX
  1. 2.0.1 or later
    (but not 2.0.3.2 or 2.5)
  1. No
  1. Polycom HDX 4000 HD
  1. Rev C
  1. 2201-12698-XXX
  2. 2215-12699-XXX
  1. 2.7.0J, 3.0 or later
  1. Yes
  1. Polycom HDX 4500
  1. 2201-61845-XXX
  2. 2215-09830-XXX
  1. 3.0.1 or later
  1. Yes
  1. Polycom HDX 6000 HD
  1. 2201-28619-XXX
  2. 2215-28711-XXX
  1. 2.5.0.6 or later
  1. Yes
  1. Polycom HDX 7000
  1. 2201-27285-XXX
  2. 2215-27427-XXX
  1. 2.0.2 or later
    (but not 2.5)
  1. No
  1. Polycom HDX 7000
  1. 2201-28629-XXX
  2. 2215-28632-XXX
  1. 2.5.0.1 or later
  1. Yes
  1. Polycom HDX 7000 HD
  1. Hardware Version A (running 2.5.x or later versions of software, blank with earlier versions)
  1. 2201-27284-XXX 2215-27426-XXX
  1. 2.0.2 or later
    (but not 2.0.3.2 or 2.5)
  1. No
  1. Polycom HDX 7000 HD
  1. Hardware Version B
  1. 2201-28128-XXX
  2. 2215-28127-XXX
  1. 2.5.0.1 or later
  1. Yes
  1. Polycom HDX 7000 HD
  1. Hardware Version C
  1. 2201-26773-XXX
  2. 2215-26771-XXX
  1. 2.5.0.7 or later
  1. Yes
  1. Polycom HDX 8000 HD
  1. Hardware Version A (2.5.x or later versions of software, blank with earlier versions)
  1. 2201-24506-XXX
  2. 2215-24614-XXX
  1. 2.0 or later
    (but not 2.0.0J, 2.0.3.2, or 2.5)
  1. No
  1. Polycom HDX 8000 HD
  1. Hardware Version B
  1. 2201-27951-XXX
  2. 2215-27952-XXX
  1. 2.5.0.1 or later
  1. Yes
  1. Polycom HDX 9001
  1. 2201-23784-XXX
  2. 2201-23795-XXX
  3. 2215-23796-XXX
  4. 2201-28218-XXX
  1. 2.0.0J, 2.0.2 or later
    (but not 2.0.3.2 or 2.5)
  1. Yes
  1. Polycom HDX 9002
  1. 2201-23783-XXX
  2. 2201-23782-XXX
  3. 2215-23788-XXX
  4. 2201-28217-XXX
  5. 2215-23788-XXX
  6. 2201-29004-XXX
  1. 2.0.5J or later
    (but not 2.5 or 2.5.0.1)
  1. Yes
  1. Polycom HDX 9004
  1. 2201-23722-XXX
  2. 2201-23283-XXX
  3. 2215-23358-XXX
  4. 2201-28216-XXX
  5. 2215-23358-XXX
  6. 2201-29006-XXX
  1. 2.0.0J and 2.0.2 or later
    (but not 2.0.3.2, 2.5, or 2.5.0.1)
  1. Yes
  1. Polycom HDX 9006
  1. Hardware Version B
  1. 2201-32806-XXX
  2. 2215-23134-XXX
  1. 2.6 or later
  1. Yes
  1. Notes:
  2. • The column “Compatible Software Versions” shows the approved/qualified software versions. Software Update enforces most of these rules.
  3. • Systems that do not have a real-time clock will not retain the time of day across reboots. They should be configured to use an NTP server.

Corrected Issues in 3.0.1

The following table lists issues corrected in version 3.0.1.

 

    Category

    Jira ID

    Description

  1. Automatic Provisioning
  1. VIDEO-71385
  1. If Polycom HDX systems, operating with automatic provisioning, are unable to reach the presence service for an extended period of time (for example, due to a server problem or network outage), they will now reregister to the server after it becomes available.
  1. Automatic Provisioning
  1. VIDEO-67861
  1. If the Polycom HDX system is not connected to the IP network at startup, it will now check for provisioning changes before the next scheduled polling interval.
  1. Calling
  1. VIDEO-51939
  1. Ring tones on incoming H.323 calls do not stop working after a few calls and do not produce a very short chirp.
  1. Contacts
  1. VIDEO-68748
  1. You can now add Contacts that support presence by using the web interface instead of having to add them in the system’s local interface.
  1. Directory
  1. VIDEO-60603
  1. Directory entries now successfully connect calls to sites dialed over ISDN voice. You do not need to add voice sites manually.
  1. Interoperability BroadSoft BroadWorks
  1. VIDEO-88121
  1. Blind Transfer SIP calls in a Broadworks environment did not connect. This problem has been corrected.
  1. Interoperability BroadSoft BroadWorks
  1. VIDEO-88122
  1. Call Pick Up SIP calls in a Broadworks environment experienced audio problems. This problem has been corrected.
  1. Interoperability BroadSoft BroadWorks
  1. VIDEO-88123
  1. Attended Transfer SIP calls in a Broadworks environment did not work when the HDX system was configured to use UDP as its transport protocol. This problem has been corrected.
  1. Interoperability LifeSize
  1. VIDEO-88116
  1. H.323 calls with Lifesize Team 220/4.6.1.5 systems sometimes did not receive audio from Lifesize. This problem has been corrected.
  1. Interoperability PathNavigator™
  1. VIDEO-53371
  1. When registered to the PathNavigator, multipoint directory entries with speed configured for Auto sometimes failed. This problem has been corrected.
  1. Interoperability PathNavigator
  1. VIDEO-60656
  1. When Use PathNavigator for Multipoint Calls was set to Dynamic on a Polycom HDX 8000 HD or Polycom HDX 4000 series system, 5-way and higher multipoint calls were not placed automatically. This problem has been corrected.
  1. Interoperability Polycom RMX System
  1. VIDEO-86864
  1. Calls hosted on an RMX 7.0.x system would occasionally experience distorted video. This problem has been corrected.
  1. Interoperability TANDBERG
  1. VIDEO-86162
  1. The double-byte, H.323 name of a Polycom HDX system can be displayed when the system is in an H.323 call hosted on a TANDBERG bridge.
  1. Localization
  1. VIDEO-71091
  1. Localized directory entries of between 31 and 34 characters are now displayed correctly.
  1. Monitors
  1. VIDEO-52390
  1. In H.320 multipoint calls with four or more far sites hosted by a Polycom HDX system, with AES encryption enabled, the user interface no longer responds slowly.
  1. Monitors
  1. VIDEO-61097
  1. Video from some computers is no longer slightly clipped on the left side when viewed on a Polycom HDX system 4000 series display.
  1. User Interface
  1. VIDEO-54356
  1. When the trace route diagnostic screen lists more than one line in the results, it is not necessary to use the Back button on the remote control to exit the screen.
  1. User Interface
  1. VIDEO-55049
  1. In some cases, a warning is now displayed in the user interface when a user changes the settings for content display in the web interface.
  1. Web Interface
  1. VIDEO-51966
  1. When a user enters an invalid Console IP address, the user can correct the address before the IP error message displays multiple times followed by a Stack overflow at line: 131 message.
  1. Web Interface
  1. VIDEO-60654
  1. You can now use the web interface for closed captioning while operating in secure mode.
  1. Web Interface
  1. VIDEO-84031
  1. The Admin Settings > Network > IP Network > H.323 Settings > Current IP Address field in the web interface is not an editable field; however, it appeared to be editable in previous releases. This problem has been corrected.

Corrected Issues in 3.0.0.2

The following table lists issues corrected in version 3.0.0.2.

 

    Issue

    Jira ID

    Description

  1. API
  1. VIDEO-83150
  1. The Integrator Reference Manual for Polycom HDX Systems was updated to correctly describe the feedback of the camera register command.
  1. Calling
  1. VIDEO-88911
  1. An HDX system improperly prompted the user for a password when the user attempted to hang up an internal multipoint call. This issue has been corrected.
  1. H.323
  1. VIDEO-88910
  1. H.323 calls that traversed firewalls using the Polycom VBP™ series or another H.460 device experienced various problems such as failure to connect or no audio/video. This issue has been corrected.
  1. Interoperability Microsoft Lync Server
  1. VIDEO-88912
  1. When a Lync server called an HDX system that was already in a call with another HDX system and escalated the call to video, some of the participants in the conference did not receive video. This issue has been corrected.
  1. Interoperability SoundStation ® IP 7000
  1. VIDEO-81353
  1. Occasionally, when a SoundStation IP 7000 was attached to a Polycom HDX system, the SoundStation IP 7000 made faint audio popping sounds. This issue has been corrected.
  1. Polycom Touch Control
  1. VIDEO-89542
  1. The Polycom Touch Control would indicate it was paired with the HDX system when in fact it had lost the pairing connection. Version 1.0.3 of the Polycom Touch Control Panel Software and version 1.0.3 of the Polycom Touch Control Operating System resolved this issue.
  1. SIP
  1. VIDEO-71148
  1. SIP calls across firewalls sometimes failed to connect fully. This issue has been corrected.
  1. Software Update
  1. VIDEO-88909
  1. Polycom HDX 9002 failed to detect input on input 1. This issue has been corrected.

Corrected Issues in 3.0.0.1

The following table lists issues corrected in version 3.0.0.1.

 

    Issue

    Jira ID

    Description

  1. Polycom Polycom Touch Control Device
  1. VIDEO-88393
  1. On occasion, HDX systems running 3.0 software paired with Polycom Touch Control running version 1.0 of Polycom Touch Control Panel Software and version 1.0 of Polycom Touch Control Operating System would get out of sync on the status of pairing between them. In addition, the pairing connection could become unstable.
  2. HDX version 3.0.0.1 software, together with version 1.0.1 of the Polycom Touch Control Panel Software and version 1.0 of the Polycom Touch Control Operating System, resolves this issue.

Corrected Issues in 3.0

The following table lists issues corrected in version 3.0.

 

    Issue

    Jira ID

    Description

  1. Audio
  1. VIDEO-84517
  1. If more than three endpoints are connected to a Polycom HDX system hosting a multipoint call, and one of the endpoints plays audio content, and that endpoint is not the last endpoint connected to the call, audio is no longer garbled.
  1. Audio
  1. VIDEO-84718
  1. Polycom HDX 9001 systems no longer experience distorted audio when the following sequence of events occurs:
  2. 1. The Polycom HDX 9001 system places a POTS call.
  3. 2. The Polycom HDX 9001 system places a video call to an endpoint that supports stereo.
  4. 3. The Polycom HDX 9001 system places a video call to an endpoint that does not support stereo.
  1. Automatic Provisioning
  1. VIDEO-70052
  2. VIDEO-70539
  1. Configuring automatic provisioning information in the out-of-box setup wizard (or configuring the system to not use provisioning) and later moving back to the provisioning page to change this information caused an issue that has been corrected.
  1. Calling
  1. VIDEO-83607
  1. Video is no longer delayed on a Polycom HDX 9001 system when in a multipoint call with a Polycom HDX 8000 system with Hardware Version B that is hosting the multipoint call and sending content.
  1. Calling
  1. VIDEO-76321
  1. When a leading zero was used in the IP address, the ifconfig command treated the value incorrectly. This issue has been corrected.
  1. Contacts
  1. VIDEO-70531
  1. With Allow Directory Changes provisioned to disabled, you could add Contacts but not delete them. This issue has been corrected.
  1. Content
  1. VIDEO-85286
  1. Polycom HDX systems can now send content when in a call with a Polycom RMX system when content resolution is configured for 800x600.
  1. Content
  1. VIDEO-72048
  1. On occasion the far endpoint stopped receiving content if the presenter changed screen resolution from 12x7 to 10x7. This issue has been corrected.
  1. Interoperability Avaya
  1. VIDEO-86608
  1. When registering an HDX system running version 2.6.1 to Avaya Aura™ 6.0, the registration for the HDX system is no longer rejected with a message of Missing/Invalid Header .
  1. Interoperability Microsoft
  1. VIDEO-84367
  1. When a Polycom HDX system hosting a multipoint call is in a Office Communications Server SIP call with three Office Communicator clients, connecting to another Polycom HDX system via SIP no longer results in degraded video on the Polycom HDX system that joined the call.
  1. Interoperability Microsoft
  1. VIDEO-83905
  1. When a Microsoft Office Communicator client is in an audio-only call with a Polycom HDX system that is already in a point-to-point call with another Polycom HDX system, the Office Communicator client can now connect to the Polycom HDX system by video.
  1. Interoperability Polycom MGC™
  1. VIDEO-51962
  1. Polycom HDX systems in high-speed, video-switched conferences with Polycom Pro-Motion™ on Polycom MGC sometimes experienced video artifacts when sending content. Polycom MGC 8.0.0.26 resolved this issue.
  1. Interoperability Polycom RMX System
  1. VIDEO-74566
  1. Polycom HDX systems running 2.5.0.5 or earlier could sometimes crash with RMX 4.0 in 4 Mbps 1080p calls. This issue has been corrected.
  1. Interoperability Polycom Video Border Proxy™ (VBP™)
  1. VIDEO-84719
  1. Polycom HDX systems no longer restart after approximately 90 minutes when all of the following conditions are true:
  2. • The Polycom HDX system is in an H.323 call.
  3. • The H.323 call is routed through a Polycom VBP system.
  4. • The Polycom HDX system has SIP enabled, and the SIP proxy server specified is incorrect.
  1. Interoperability Polycom VSX® Systems
  1. VIDEO-82744
  1. When a Polycom HDX 8006 system is in a mixed call with a Polycom VSX system connected over H.323 and a Polycom HDX 9001 system connected over ISDN, the Polycom HDX 9001 system no longer shows video latency in the PIP window when content is stopped and started among the different endpoints.
  1. Interoperability Polycom VSX Systems
  1. VIDEO-74778
  1. When a Polycom VSX system running version 9.0.5 made a SIP connection to an existing point-to-point H.323 call between two Polycom HDX endpoints, the Polycom HDX system hosting the multipoint call appeared unresponsive and the call statistics indicated no transmit or receive video on any of the endpoints. Upgrading the VSX system to version 9.0.5.1 resolves the issue.
  1. Interoperability Polycom VSX Systems
  1. VIDEO-49020
  1. VSX version 8.5.1 did not activate PVEC (Polycom Video Error Concealment) in a call with a Polycom HDX system that experienced network errors. VSX version 8.5.2 addresses this issue.
  1. Interoperability Polycom VSX Systems
  1. VIDEO-59956
  1. Calls from a VSX system version 8.7 did not connect when using the UDP transport protocol. VSX version 8.7.1 resolves this issue.
  1. Interoperability Polycom VVX® 1500 System
  1. VIDEO-84464
  1. Audio can now be heard from any site when a Polycom HDX system hosting a multipoint call connects via SIP to a Polycom VVX1500 phone and a TANDBERG E20 system.
  1. Interoperability Sony
  1. VIDEO-81306
  1. When a Sony XG80 system is hosting a multipoint call greater than H.323 128 kbps with two Polycom HDX systems, the second Polycom HDX system that joins the call no longer transmits distorted video.
  1. Interoperability Sony
  1. VIDEO-76241
  1. When a Sony PCS-XG80 is hosting a multipoint call, and two Polycom HDX systems connect to it via H.323, the second Polycom HDX system to connect no longer displays distorted video during the conference.
  1. Interoperability SoundStation IP 7000
  1. VIDEO-80858
  1. Occasionally, the SoundStation IP 7000 lost the dial tone when connected to a Polycom HDX system. This issue has been corrected.
  1. Interoperability SoundStation IP 7000
  1. VIDEO-87427
  1. When a SoundStation IP 7000 system was attached to a Polycom HDX system, a call did not connect if dialing a SIP address that was 20 characters or greater. This issue has been corrected.
  1. Interoperability TANDBERG
  1. VIDEO-74376
  1. In SIP calls greater than 2 Mbps with a TANDBERG MXP or Codian MCU, the call connects at 1920 kbps. This issue was corrected in TANDBERG 6000 MXP F9.0.
  1. Monitors
  1. VIDEO-70164
  1. You can now configure both Monitor 1 and Monitor 2 to display far-end video.
  1. Monitors
  1. VIDEO-84366
  1. Endpoints in a point-to-point SIP call receiving content no longer display frozen video if the system sending content switches from sending content from Camera 4 to Camera 2 without first stopping content on Camera 4.
  1. Multipoint
  1. VIDEO-83800
  1. When a Polycom HDX system hosting a multipoint call has Multipoint Mode set to Full Screen and is in a conference with three or more endpoints, the name of one site no longer displays while displaying the video from a different site.
  1. Multipoint
  1. VIDEO-84593
  1. In 4-way calls between Polycom HDX systems with stereo enabled, the last endpoint no longer connects with mono instead of stereo.
  1. Multipoint
  1. VIDEO-76695
  1. Occasionally, a Polycom HDX 9004 system acting as a Multipoint Control Unit (MCU) crashed when sending content in the following scenario:
  2. • Eight endpoints are in the call.
  3. • Transcoding is set to OFF.
  4. • Monitor 1 has Far, Near, Content, and DME enabled.
  5. • Monitor 2 is set to OFF.
  6. • MCU is sending content at 10x7.
  7. • All three Picture-in-Picture windows are displayed on Monitor 1.
  8. This issue has been corrected.
  1. People+
    Content™ IP
  1. VIDEO-81147
  1. When sending content with People+Content IP, the content image no longer displays black bars on the side when the PC has been configured for a 16:9 aspect ratio.
  1. People+
    Content IP
  1. VIDEO-81288
  1. When using People+Content IP to send content, residual artifacts might have been observed in areas with chroma-only changes. This issue was corrected in Polycom People+Content IP version 1.2.3.
  1. People on Content™
  1. VIDEO-83850
  1. When a Polycom HDX system hosting a multipoint call has People On Content configured and is in a multipoint SIP call, the far endpoints no longer display black video. This issue occurred when the Polycom HDX system hosting the multipoint call stops sending content via People+Content IP and begins sending content via People On Content.
  1. People on Content
  1. VIDEO-79760
  1. People on Content no longer displays video artifacts if the content source is not enabled.
  1. Provisioning
  1. VIDEO-80756
  1. Polycom HDX systems can now have the remote access password provisioned when they are being managed by Polycom CMA in traditional management mode.
  1. Power
  1. VIDEO-83487
  1. Polycom HDX 6000 systems no longer restart when receiving a call after the content input resolution is changed from 10x7 to 720p.
  1. Remote Control
  1. VIDEO-84364
  1. Occasionally, pressing a button on the remote control caused the cursor to move ahead two positions instead of one. This issue has been corrected.
  1. Remote Control
  1. VIDEO-84516
  1. Polycom HDX systems no longer become non-responsive when using the remotecontrol intercept API command because the intercept parameter has been removed from the remotecontrol command.
  1. Security
  1. VIDEO-70377
  1. If your system was in Security Mode and you used the web interface, browsers sometimes displayed warning messages stating that The security certificate for the web site “Polycom” cannot be verified. This warning does not appear when using the certificates capability added in version 3.0.
  1. Software Update
  1. VIDEO-72721
  1. Polycom HDX 9000 series systems occasionally displayed a shifted or split progress screen during a software update. This issue has been corrected.
  1. User Interface
  1. VIDEO-81342
  1. On page 3 of the Security Settings screens you could not place the yellow cursor on Allow Video Display on Web when navigating from the top to the bottom and moving downward. This issue has been corrected.
  1. User Interface
  1. VIDEO-82741
  1. Setting the Time Server to Auto no longer sets ntp.polycom.com as the time server.
  1. User Interface
  1. VIDEO-71164
  1. When attempting to clear SIP-related configuration items in the embedded user interface, you no longer need to move the cursor out of the text box to another place on the screen to ensure that the configuration change takes effect.
  1. Video
  1. VIDEO-71244
  1. In calls with 1080p resolution, Polycom HDX systems transmitted video at a low frame rate during scenes with high motion (for example, when panning the camera). This issue has been corrected.
  1. Web Interface
  1. VIDEO-80194
  1. The web interface did not display the hardware version for revision A of the Polycom HDX 7000 and 8000 products under Tools > System Information. This issue has been corrected.

Feature Limitations

The following table lists the known feature limitations for the version 3.0.1 release. If a workaround is available, it is noted in the table.

 

    Category

    Issue ID

    Found in Release

    Description

    Workaround

  1. Active Directory server
  1. VIDEO-85246
  1. 3.0
  1. Setting the Security Profile to Maximum during the Setup Wizard causes External Authentication to be enabled. Although administrators can create local user IDs and passwords, local users will not be able to access the HDX system as long as External Authentication is enabled.
  1. After you complete the Setup Wizard, go to System > Admin Settings > General Settings > Security > External Authentication and disable the Enable Active Directory Authentication setting to enable local users to access the system.
  1. Analog Phone
  1. VIDEO-80791
  1. 2.6
  1. Incoming calls from analog phones do not display on the Recent Calls screen.
  1. None
  1. Analog Phone
  1. VIDEO-73949
  1. 2.5.0.4
  1. Do not use the analog phone connector if you are using a Polycom HDX 9000 series system in Hong Kong or South Africa. If your Polycom HDX 9000 series system came with a telephone adapter, refer to the accompanying telephone adapter setup sheet for information on whether the adapter is needed in your area.
  1. None
  1. API
  1. VIDEO-51280
  1. 1.0
  1. The remotecontrol enable all command does not work after disabling the remote. Use remotecontrol disable none to enable the remote control buttons.
  1. None
  1. API
  1. VIDEO-55286
  1. 1.0.2
  1. state[ALLOCATED]
  2. cs: call[38] chan[0] dialstr[172.26.48.42] state[RINGING]
  3. cs: call[38] chan[0] dialstr[172.26.48.42] state[BONDING]
  4. cs: call[38] chan[0] dialstr[172.26.48.42] state[COMPLETE]
  5. active: call[38] speed[512]
  6. The notification in boldface is not applicable to calls made to and received from IP end points.
  1. None
  1. Audio
  1. VIDEO-55634
  1. 1.0.1
  1. If you establish multiple calls between the two systems, you may experience audio feedback.
  1. None
  1. Audio
  1. VIDEO-60669
  1. 2.0
  1. Incoming voice calls do not work in a password-protected conference.
  1. None
  1. Audio
  1. VIDEO-70543
  1. 2.5
  1. When you plug a headset into the Polycom HDX 4000 series panel, the system’s built-in microphones and any attached microphones are automatically muted even though the Enable Polycom Microphones and Enable Built-In Microphones configuration settings remain selected.
  1. None
  1. Audio
  1. VIDEO-69705
  1. 2.5
  1. Starting with the release 2.5, Polycom HDX systems do not play music while restarting. Polycom HDX systems running software version 2.6 play an announcement tone once the system has been successfully restarted.
  1. None
  1. Audio
  1. VIDEO-69796
  1. 2.5
  1. You cannot enable or disable Stereo while in a call.
  1. None
  1. Audio
  1. VIDEO-69797
  1. 2.5
  1. Do not connect or disconnect a Polycom SoundStation IP 7000 conference phone or Polycom HDX digital microphones while in a call. Doing so may result in some anomalous behavior such as audio coming out both the conference phone and Polycom HDX system. To restore normal operation, hang up the call.
  1. None
  1. Audio
  1. VIDEO-71505
  1. 2.5.0.1
  1. Volume changes made during the setup wizard are lost when the system restarts.
  1. None
  1. Automatic Provisioning
  1. VIDEO-80706
  1. 2.6
  1. The Polycom HDX Gateway Country Code value is not provisioned when the Polycom CMA Administrator has created a scheduled provisioning profile with a value for the Gateway Country code.
  1. Update the Gateway Country Code value manually on the Polycom HDX system via the local system interface or web interface.
  1. Automatic Provisioning
  1. VIDEO-82959
  1. 2.6.1
  1. Occasionally, when a Polycom HDX system is configured for dynamic management mode with a CMA server, the Polycom HDX system is not provisioned with the correct user name based on the provisioned User ID.
  1. None
  1. Automatic Provisioning
  1. VIDEO-71305
  1. 2.5.0.1
  1. Polycom HDX systems operating with automatic provisioning check for software updates at an interval specified by the administrator. If an update is required, Polycom HDX 4000 systems perform the update even if they are currently being used as PC displays.
  1. None
  1. Automatic Provisioning
  1. VIDEO-71440
  1. 2.5.0.1
  1. Polycom HDX systems sold in Russia do not operate with automatic provisioning.
  1. None

Hardware and Software Requirements

To use the web interface, you need Microsoft Internet Explorer 6.x, 7.x., or 8.x.

To integrate a Polycom SoundStation IP 7000 phone with a Polycom HDX system, use the following software versions:

 

    SoundStation IP 7000 phone software version

    Polycom HDX series system software version

  1. 3.2.1 or 3.2.2 and BootROM 4.2.0
  1. 2.5.0.7, 2.5.0.8
  1. 3.2.3 and BootROM 4.2.2
  1. 2.6.0, 2.6.0.1, 2.6.1
  1. 3.3.1 and BootROM 4.3.0
  1. 2.6.1.3, 3.0, 3.0.0.1, 3.0.0.2, 3.0.1

Interoperability

 
 
  1. For more information about using Polycom HDX systems as part of a Polycom–partner product solution, refer to the Polycom–partner product deployment guides available at support.polycom.com .

The following PTZ cameras are supported for use with Polycom HDX systems:

  • • Polycom EagleEye View (requires HDX system software 2.6 or later)
  • • Polycom EagleEye HD
  • • Polycom EagleEye 1080 (requires HDX system software 2.5 or later)
  • • Polycom EagleEye II (requires HDX system software 2.6.1 or later)
  • • Polycom EagleEye III (requires HDX system software 3.0.1)
  • • Polycom EagleEye Director (requires HDX system software 3.0.1)
  • • Polycom PowerCam™ Plus (SD camera)
  • • Polycom PowerCam (SD camera))
  • • Sony EVI-D30/31 (SD camera)
  • • Sony EVI-D70 / Vaddio WallVIEW 70 (SD camera)
  • • Sony EVI-D100 / Vaddio WallVIEW 100 (SD camera)
  • • Sony BRC-300 / Vaddio WallVIEW 300 (SD camera)
  • • Elmo PTC-100S/110R/150S/160R (SD camera)
  • • Canon VC-C50i/Vaddio WallVIEW 50i (SD camera)
  • • Sony BRC-H700
  • • Sony EVI-HD1

Video conferencing systems use a variety of algorithms to compress audio and video. In a call between two systems, each end transmits audio and video using algorithms supported by the other end. In some cases, a system may transmit a different algorithm than it receives. This process occurs because each system independently selects the optimum algorithms for a particular call, and different products may make different selections. This process should not affect the quality of the call.

Polycom HDX systems are tested extensively with a wide range of products. The following list is not a complete inventory of compatible equipment. It simply indicates the products that have been tested for compatibility with the HDX systems software 3.0.1 release.

 

    Type

    Product

    Version

  1. NAT/Firewall/Border Controller
  1. Linksys WRT54G2
  1. 1.5.00
  1. NETGEAR FR114P
  1. 1.5 Release 14
  1. NETGEAR WGR614v10
  1. 1.0.2.26_51.0.59NA
  1. Polycom Video Border Proxy™ (VBP™) 5300 E/S
  1. 9.1.5.3
  1. Management Systems and Recorders
  1. Polycom RSS 4000
  1. 6.0.0, 6.4.0
  1. Polycom Video Media Center™ (VMC™) 1000
  1. 2.0 build 5.3.0.110
  1. Gatekeeper, Gateways, External MCU, Bridges, Call Managers
  1. Avaya ACM
  1. R015x.02.0.947.3
  1. Cisco Unified Communications Manager
  1. 6.0, 7.0 (must use Polycom HDX software version 2.5.0.6_00_cisco-3966)
  1. Cisco 3745
  1. 12.4
  1. Codian 4505
  1. 4.1 (1.51)
  1. OpenSER
  1. 1.0.2
  1. Polycom CMA 4000, CMA 5000
  1. 5.4.0
  1. Polycom Global Management System
  1. 7.1.10.1
  1. Polycom Distributed Media Application™ (DMA™) 7000
  1. 2.0.2, 2.3
  1. Polycom ReadiManager SE200
  1. 3.0.7 ER1
  1. Polycom PathNavigator
  1. 7.0.14
  1. Polycom RMX 1000
  1. 2.1.2-25338
  1. Polycom RMX 2000™, Polycom RMX 4000
  1. 7.0.2, 7.1
  1. Polycom RMX1500
  1. 7.0.2, 7.1
  1. Polycom MGC
  1. 9.0.4.3
  1. RADVISION ECS
  1. 7.1.2.12
  1. TANDBERG Gateway
  1. G3.2
  1. TANDBERG Gatekeeper
  1. N6.1
  1. Endpoints
  1. Aethra X3
  1. 12.1.19
  1. Aethra X7
  1. 12.1.7
  1. LifeSize Express
  1. 4.7.11(4)
  1. LifeSize Room
  1. 4.7.11(4)
  1. LifeSize Room 200
  1. 4.7.11(4)
  1. LifeSize Team
  1. 4.1.1(17)
  1. LifeSize Desktop
  1. 2.0.2.191
  1. Polycom CMAD
  1. 5.1.0.0060
  1. Polycom CMAD MAC
  1. 5.1.1.52000_1178
  1. Polycom DSTMedia Broad5
  1. 2.0.0
  1. Polycom DSTMedia K60
  1. 2.0.1
  1. Polycom iPower 9000
  1. 6.2.0.1208
  1. Polycom PVX
  1. 8.0.4, 8.0.16
  1. Polycom QDX® 6000
  1. 4.0.1
  1. Polycom V500, Polycom V700™
  1. 9.0.6.1
  1. Polycom ViewStation 512
  1. 7.5.4
  1. Polycom ViewStation FX
  1. 6.0.5
  1. Polycom SoundPoint® IP 601
  1. 3.1.4.0070
  1. Polycom VVX1500
  1. 3.3.1.0769
  1. Polycom SoundStation IP 4000
  1. 3.1.4.0070
  1. Endpoints
  1. Polycom VSX 3000, VSX 5000, VSX 6000
  1. 9.0.6.1
  1. Polycom VSX 7000, VSX 7000e, VSX 8000
  1. 9.0.6.1
  1. Sony PCS-1
  1. 3.42
  1. Sony PCS-G50
  1. 2.70
  1. Sony PCS-G70
  1. 2.63
  1. Sony PCS-XG80
  1. 2.14
  1. Sony PCS-TL50
  1. 2.42
  1. TANDBERG Edge95 MXP, MXP 880, MXP 1500, MXP 1700, MXP 6000
  1. F9.0.2
  1. TANDBERG MXP 150
  1. L6.0.2
  1. TANDBERG 6000 B Series
  1. B10.3
  1. TANDBERG 6000 E Series
  1. E5.3
  1. TANDBERG E20
  1. 2.2.1.224666
  1. TANDBERG C90
  1. TC4.0.1.240265
  1. TANDBERG C20
  1. TC4.0.1.240265
  1. Microsoft Office Communications Server and Microsoft Lync™ Server 2010 Solution
  1. Microsoft Office Communications Server 2007 R2
  1. 2007 SP2
  1. Microsoft Office Communicator Client R2
  1. 3.5.6907.221
  1. F5 BIG-IP Load Balancer 1500
  1. 9.1.2 (40.2)
  1. Microsoft Exchange 2010 server
  1. Update 3
  1. Microsoft Exchange 2007 server
  1. Update 4 SP2
  1. Microsoft Outlook 2007
  1. 2007 SP2
  1. Lync2010 SP0
  1. 4.0.7457.0
  1. Lync2010 client
  1. 4.0.7577.0
  1. Exchange 2010 SP0
  1. 14.00.0702.000
  1. PCO
  1. 1.0.2 build 1
  1. BroadSoft Solution
  1. BroadSoft BroadWorks
  1. 16 SP1

License Issues

OpenSSL License

Copyright (c) 1998-2007 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License

Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscape’s SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed.

If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)"

The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-).

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement:

"This product includes software written by Tim Hudson (tjh@cryptsoft.com)"

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License.]

Copyright Information

© 2011 Polycom, Inc. All rights reserved.

Polycom, Inc.
4750 Willow Road
Pleasanton, CA 94588-2708
USA

No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format.

As between the parties, Polycom, Inc., retains title to and ownership of all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g., a book or sound recording).

Every effort has been made to ensure that the information in this manual is accurate. Polycom, Inc., is not responsible for printing or clerical errors. Information in this document is subject to change without notice.

Trademark Information

Polycom ® , the Polycom “Triangles” logo, and the names and marks associated with Polycom’s products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common-law marks in the United States and various other countries.

All other trademarks are the property of their respective owners.

Patent Information

The accompanying products may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc.

Document Part Number XXXXXXXXXXXXXXX