User manual POLYCOM VSX 9.0.6.1 RELEASE NOTES 10-2010

[. . . ] Release Notes Polycom® V Series and VSX® Systems, Version 9. 0. 6. 1 Polycom is pleased to announce the release of version 9. 0. 6. 1 software for Polycom® V Series and VSX® systems. This document provides the latest information about version 9. 0. 6. 1 software for Polycom V Series and VSX systems. For more information about updating software and enabling system options, refer to the Installing Polycom V Series and VSX Software and Options document by navigating to www. polycom. com/support/video and clicking on the name of your product. Polycom VSX 3000A and Polycom V700 customers may experience flicker on their displays when upgrading to version 9. 0. 6. 1. This is normal behavior and it is critical that the system NOT be turned off during this process. [. . . ] When a Polycom VSX system joins an encrypted People+Content/H. 239 continuous presence Polycom MGC multipoint call, the Polycom VSX system does not support far end camera control. When a SIP site is added to a preconfigured Polycom MGC meeting room, the Polycom MGC can dial out to the SIP site. However, the SIP site connects only intermittently, and after this, the Polycom MGC is unable to connect automatically or manually to the SIP site but instead reports an "IP card general error" message for the SIP site. If a VSX system joins a multipoint call hosted by Polycom MGC while a participant is sending content, the VSX and V Series systems already in the call become audio-only participants. VIDEO-56707 VIDEO-74484 When a VSX system joins a continuous presence call hosted by Polycom MGC-50+TM. When Polycom MC-50 running version 9. 0. 18 software hosts a conference configured for dynamic Far-end Camera Control (FECC), the VSX system cannot control far-end cameras, and the other participants cannot control the VSX camera. To work around this problem, configure the conference's FECC setting to 6. 4. Polycom VSX 8000 and VSX 7000 display frozen video in 1920 kbps encrypted video switched conferences. In a transcoded H. 264 call through the Polycom MGC gateway, the VSX 7000A system transmits H. 264 QCIF. Interoperability Polycom VBP When a Polycom VSX system's call speed exceeds the Polycom VBP configured speed, calls placed through the Polycom VBP do not connect. Try lowering the Polycom VSX system's call speed. VIDEO-74483 VIDEO-7448 VIDEO-74497 VIDEO-80333 VIDEO-51036 30 Release Notes V Series and VSX Systems, Version 9. 0. 6. 1 Jira ID VIDEO-43239 Feature Interoperability RADVISION Limitation When a Polycom VSX system places an H. 320 to H. 323 gateway call through a RADVISION viaIP gateway, it cannot send or receive H. 239 content. Calls between H. 323 VSX 8000 systems and H. 320 iPower 9000 systems made through a RADVISION viaIP gateway may cause the iPower system to restart on hang-up. In a call between an H. 320 VSX system that has AES enabled and an H. 323 VSX system that has AES disabled and that is registered to the RADVISION ECS gatekeeper, you may hear an audio chirp on the H. 320 VSX system after the H. 323 VSX system hangs up the call. VIDEO-25691 VIDEO-57369 VIDEO-57142, VIDEO-57259 VIDEO-62334 Interoperability Polycom ReadiManager SE200 The video may not display during a call with the ReadiManager SE200 if passwords are required. A workaround is to use the ReadiManager SE200 without requiring passwords. When you attempt to provision a Polycom VSX system with a provisioning profile created on the ReadiManager SE200, the Polycom VSX system may not be fully provisioned with all of the details included on the provisioning profile. The VSX8000 system displays frozen or garbled video while in an RMX 1000 H. 323 video switching highest common conference with the VSX 8000. Polycom VSX 7000 transmits and receives H. 263 video in RMX 2000 conferences configured for H. 264. . VIDEO-80207 Interoperability Polycom RMX 1000TM Interoperability Polycom RMX 2000TM VIDEO-74304 31 Release Notes V Series and VSX Systems, Version 9. 0. 6. 1 Jira ID VIDEO-36628 VIDEO-25798 Feature Interoperability Sony Limitation VSX 8000 systems with a Sony BRC300 camera may not correctly move to camera presets. In H. 320 calls where a VSX system hosts the multipoint call, the Sony PCS-1 version 3. 02 may not receive content. In a H. 320 or H. 323 call between a VSX system and the Sony PCS-1 version 3. 30 or Sony PCS-G50 version 2. 42, the VSX system may begin to display video artifacts a few minutes after the Sony system begins to share content. In a SIP call between a VSX system and the Sony PCS-1 version 3. 41, Sony PCS-G50, or Sony PCS-G70 version 2. 6. 1, the VSX system may not transmit or receive audio. In an H. 320 call when H. 239 is enabled (System > Admin Settings > Network > Call Preference), a Sony PCS-G50 with version 2. 6. 1 is unable to send video to a Polycom VSX system or else sends only frozen video. When Polycom VSX systems participate in an H. 320 multipoint call that is hosted by the Sony PCS-G50, the Polycom VSX systems are unable to send content to the Sony PCS-G50 host system. However, the Sony PCS-G50 host system is able to send content to the Polycom VSX systems. [. . . ] Cisco PIX "fixup protocol h323 h225 1720" on with following ports open: Polycom V Series and VSX systems will work properly; however, with Cisco PIX setup in this manner you will be required to disable AES to connect sites through the Firewall. Cisco currently does not support AES or H. 239 in the "fixup protocol h323 h225 1720". In an H. 323 multipoint conference, when a Polycom VSX system hosts the multipoint call and is located behind a Cisco PIX 6. 3. 4 and 7. 0. 1 firewall among systems with H. 239 enabled, the Polycom V Series and VSX systems outside of the firewall may not receive video when other sites connect. Polycom V Series and VSX systems are unable to control the far end camera when it is located behind a Cisco PIX 6. 3. 4 and 7. 0. 1 firewall. [. . . ]