User manual POLYCOM HDX SYSTEMS 3.0 RELEASE NOTES 12-2010

[. . . ] Release Notes Polycom® HDX® Systems, Version 3. 0 Polycom announces the latest release of Polycom® HDX® hardware and software. This document provides the latest information about the Polycom HDX systems and version 3. 0 software. For more information about using the features described in this document, refer to the product documentation available at www. polycom. com/videodocumentation. 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. If Security Mode is enabled on your system, you must use secure HTTPS access (for example, https://10. 11. 12. 13). [. . . ] In SIP calls between Polycom HDX and LifeSize 2. 6 systems, neither system has far-site camera control. In SIP calls between Polycom HDX and LifeSize systems, Polycom HDX systems send 711u audio. In a SIP multipoint HD call with a Polycom HDX 9004 system as the host, you cannot dial out to the second HD endpoint when LifeSize is connected as the first endpoint in the call. LifeSize systems may experience poor audio in SIP calls with Polycom HDX systems. LifeSize Express systems running 4. 0. 6(7) software transmit video at 15 frames per second in HD calls with Polycom HDX systems. Interoperability LifeSize VIDEO-56734 1. 0. 2 None VIDEO-56733 1. 0. 2 None VIDEO-56732 1. 0. 2 None VIDEO-60350 2. 0 None VIDEO-61014 2. 0 None VIDEO-71453 2. 5. 0. 1 None 40 Polycom, Inc. Release Notes Polycom HDX Systems, 3. 0 Category Interoperability LifeSize Issue ID VIDEO-77465 Found in Release 2. 5. 0. 7 Description A Polycom HDX system cannot send content when it is in a SIP call with a LifeSize Room system and H. 239 is enabled. When a Polycom HDX system is in an H. 323 point-to-point call with a LifeSize Room or LifeSize Room 200 system, the LifeSize system cannot control the Polycom HDX system's camera if the Polycom HDX system has far end camera control enabled. Calls between Polycom HDX systems and Lifesize Room Systems over IPv6 do not connect when both systems are configured for maximum security. H. 323 calls with Lifesize Team 220/4. 6. 1. 5 systems might not receive audio from Lifesize. Workaround To work around this issue, place the call using H. 323. VIDEO-84509 2. 6. 1 Place the call as a SIP call. VIDEO-86789 3. 0 None. VIDEO-88116 3. 0 Configure HDX for Basic mode. Note: Basic Mode severely limits the features available in a call. Among other things, Basic Mode disables content, far end camera control, and encryption. In Internet Explorer, go to Tools > Internet Options and click the Advanced tab. Under the Security section, make sure that Use SSL 3. 0 is the only SSL choice selected. Place the call again. Interoperability Microsoft Users might have trouble using Internet Explorer to access the web interface, but have no such trouble when using Mozilla Firefox. VIDEO-80679 2. 6 When a Polycom HDX system is configured for integration with Microsoft Office Communications Server and is in a point-to -point 2M SIP call, the call disconnects after approximately 10 hours. Polycom, Inc. 41 Release Notes Polycom HDX Systems, 3. 0 Category Interoperability Microsoft Issue ID VIDEO-61286 Found in Release 2. 0. 1 Description When People Video Adjustment is set to Stretch on a Polycom HDX 8000 HD system in a call with Microsoft Office Communicator, Office Communicator displays black video. The Office Communications Server should be configured to allow no more than 200 contacts (this is the default setting). If the Office Communications Server allows more than 200 contacts and more than 200 contacts are in the directory, the Polycom HDX system may show up to 200 contacts, or none. If there is a meeting password configured for a multipoint meeting hosted on a Polycom HDX system, Microsoft Office Communicator clients cannot join the meeting. Occasionally, if three Office Communicator clients simultaneously call a Polycom HDX system hosting a multipoint call, the Polycom HDX system restarts. The user interface of a Polycom HDX system hosting a multipoint call may experience reduced response when in a high-bandwidth, 5-way federated Interactive Connectivity Establishment (ICE) call. Polycom HDX systems do not support presence in federated ICE calls. Workaround None VIDEO-81020 2. 6 None VIDEO-82848 2. 6. 1 None VIDEO-84365 2. 6. 1 None VIDEO-83849 2. 6. 1 Reduce the call bandwidth used to place the call, or use a Polycom RMX system to host the multipoint call. VIDEO-84732 2. 6. 1 None 42 Polycom, Inc. Release Notes Polycom HDX Systems, 3. 0 Category Interoperability Microsoft Issue ID VIDEO-84717 Found in Release 2. 6. 1 Description During a federated Interactive Connectivity Establishment (ICE) call between an Office Communicator client and a Polycom HDX system, the Office Communicator client disconnects from the Polycom HDX system after approximately three hours. A Polycom HDX system hosting a multipoint call with five or more endpoints may restart if the call is encrypted and using ICE. Workaround Place the call again, or place the call between two Polycom HDX systems. VIDEO-84628 2. 6. 1 Do one of the following: · Use a Polycom RMX system to host the multipoint call. Place the calls to the Polycom HDX system hosting the multipoint call at 384 kbps or lower. · VIDEO-85242 2. 6. 1 If you experience connectivity issues with federated voice or video, check the Polycom web site for updates and notifications, and verify that you have the latest software version. Polycom continues to run tests between various Office Communications Server federated environments. [. . . ] 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. 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). [. . . ]