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. [. . . ] 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. A workaround is to provision the Polycom VSX system a second time. 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. A workaround is to disable H. 239 or to downgrade the PCS software. 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. When a Polycom VSX system places an ISDN call at 336 kbps to a Sony PCS-TL50 while AES encryption is enabled on both systems, if the Polycom VSX system then attempts to send content to the Sony PCS-TL50 using the Polycom VSX Visual Concert, the Sony PCS-TL50 does not receive the content and experiences frozen video. A workaround is to retry the call at 384 kbps. In an H. 320 call when H. 239 is enabled (System > Admin Settings > Network > Call Preference), a Sony PCS-1600 and VS-1 with version 3. 33 are unable to connect to a Polycom HDX system. The workaround is to disable H. 239 on the Polycom HDX system. The Sony PCS-XG80 may not receive video sent from the VSX7000A in H. 323 encrypted calls. The Sony XG80 may have to try sending content multiple times before sending content successfully in H. 320 calls with VSX. [. . . ] 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. Configure Conduits or Access List Assignments for the following ports: · · TCP 1720 TCP 3230 - 3235 56 Release Notes V Series and VSX Systems, Version 9. 0. 6. 1 · · · · TCP 3603 TCP 389 UDP 3230-3253 UDP 1718-1719 Cisco PIX "fixup protocol h323 h225 1720" off with following ports open: Polycom V Series and VSX systems and all features will work properly. To turn off the "fixup protocol h323 h225 1720" feature, use the following command: no fixup protocol h323 h225 1720 2. Configure Conduits or Access List Assignments for the following ports: · For outbound interface -- TCP 1720 -- TCP 3230 - 3235 -- TCP 3603 -- TCP 389 -- UDP 3230-3253 -- UDP 1718-1719 · For inside interface, open all IP per video device. Use the following command to configure conduits or access points: conduit permit tcp host 255. 255. 255. 255 eq port any Where 255. 255. 255. 255 is the external IP address of the SME Appliance. [. . . ]