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 .
Polycom Touch Control Software
Polycom EagleEye Director Camera Software
Polycom HDX 4500 Desktop System
Polycom EagleEye Director Camera
Centralized Conferencing Control Protocol (CCCP)
Improved Functionality for Receiving and Sending 1080p Content
Configurable Remote Control Power Button Behavior
Camera Firmware Update for HDX 4000 Systems
Default Setting for Outgoing Call Speed
Polycom HDX System State Changes Through XML API
Receiving and Sending 1080p Content
Hardware and Software Compatibility
Hardware and Software Requirements
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 .
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.
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.
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:
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 .
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:
When configured for CCCP, a Polycom HDX system can perform the following tasks:
For more information about CCCP, refer to the following Polycom publications:
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 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 .
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.
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.
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.
This version is a maintenance release that includes updates from software testing with Microsoft Lync Server 2010.
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.
HDX software version 3.0 includes the features and functionality of version 2.6.1.3, with the following additions.
The new Polycom HDX 4000 HD system with Hardware Version C adds the following features:
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 .
Version 3.0 introduces support for the new Polycom Touch Control device.
The Polycom Touch Control has the following features:
You can use the Polycom Touch Control device instead of a handheld remote to control an HDX system.
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.
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.
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.
When you are in a call, you can use the Call screen to complete these tasks:
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.
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.
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.
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.
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.
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]
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.
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.
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.
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 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®).
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.
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.
You can use the sessions list to see information about everyone logged in to an HDX system including:
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:
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.
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.
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:
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:
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.
|
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.
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.
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.
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.
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.
The following systems now achieve a maximum frame rate of 15 fps for content in 1080p:
The following restrictions apply to receiving and 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.
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.
The following API commands are new in version 3.0.
The following table lists Polycom HDX system software versions that are compatible with Polycom hardware.
The following table lists issues corrected in version 3.0.0.1.
The following table lists issues corrected in version 3.0.
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.
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:
|
The following PTZ cameras are supported for use with Polycom HDX systems:
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.
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).
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.]
© 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.
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.