Polycom V Series, VSX Series User Manual

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. The complete upgrade should take approximately 2-3 minutes over IP, and after the upgrade is complete, the system will restart automatically.

PC Card Slot Removed

The following table lists the systems on which the mechanism for the PC Card slot has been removed and is NOT available for use.

System Model Part Number

VSX 7000e 2201-22230-301

VSX 8000 2201-21400-301

What’s New in the 9.0.6.1 Release?

In this release, a number of customer reported issues have been corrected. For details, refer to Corrected Issues in Version 9.0.6.1 on page 9.

2201-22230-309 2201-22230-314 2201-22230-350

2201-21400-309 2201-21400-314

October 2010 3725-21988-027/A

Release Notes V Series and VSX Systems, Version 9.0.6.1

What’s New in the 9.0.6 Release?

AES Required Setting

In this release, you have more control over the AES Encryption behavior on the 128 MB systems. Previously, you could only specify whether to encrypt calls with other sites that support AES encryption. If you had AES Encryption enabled but the far site did not have AES encryption enabled, the call connected without encryption. In version 9.0.6, you can select Off, When Available, or Required for Video Calls Only.

This feature is only available on the 128 MB systems (V700, VSX 3000A, VSX 5000, VSX 6000A, VSX 7000s, VSX 7000e, VSX 8000). You can determine the memory size of your system by referring to the System Information page (System > System Information); the memory size is noted as (64) or (128) after the Model name.

A lock icon in the user interface indicates whether the call is encrypted.

• In a multipoint call, the host system displays if all connections in the call are encrypted.

• In a multipoint call, the host system displays if one or more connections in the call are not encrypted.

• Far-end systems that are connected with encryption display .

• Far-end systems that are connected without encryption display .

Some connections might be encrypted while others are not. To avoid security risks, Polycom recommends that all participants communicate the state of their encryption icon verbally at the beginning of a call.

Points to note about AES Encryption:

• You cannot enable AES encryption during a call.

• AES Encryption can be configured for Required for Video Calls Only on 128 MB

systems only.

• If you enable Security Mode before upgrading the system to version 9.0.6, this setting is automatically set to When Available but can be changed.

• If you enable Security Mode after installing version 9.0.6 the system uses Required for Video Calls Only for AES Encryption.

• AES Encryption is not supported for systems registered to an Avaya H.323 gatekeeper.

Directory Tab Search by Russian Alphabet

When the system language is set to Russian, you can now choose whether to set the Directory’s alphabet tabs to Russian or English. You can toggle

Release Notes V Series and VSX Systems, Version 9.0.6.1

between the two languages by clicking the Language button above the tabs. You can use either the English or Russian alphabet tabs to move through the directory and then scroll to the name you want.

New Version of People+Content™ IP

Polycom People+Content™ IP version 1.2.2 is now available on the Polycom web site, on the Downloads page for each VSX system. Version 1.2.2 includes performance improvements and fixes to address minor technical issues.

The People+Content IP option key is included with the Polycom VSX 8000 and is optional for all other Polycom VSX and V Series systems. For information about purchasing the People+Content IP option, please contact your Polycom distributor.

For information about using People+Content IP to display content, refer to the Getting Started Guide for your product.

What’s New in the 9.0.5.2 Release?

In this version, you can configure the system to let you use the remote control to mute the sound you hear from the main speakers.

To use the Snap button to mute the speakers:

1. Go to System > Admin Settings > General Settings > System Settings >

Remote Control.

2. Select Snap Button Option and choose Mute Speakers.

To mute your main speakers:

• Press the Snap button. The sound from the main speakers is muted.

To unmute your main speakers:

• Press the Snap button. The sound from the main speakers is restored to the previous level.

Release Notes V Series and VSX Systems, Version 9.0.6.1

What’s New in the 9.0.5.1 Release?

Support for Increased Number of Directory Entries

With version 9.0.5.1, 128 MB Polycom V Series or VSX systems can store and display up to 5000 directory entries when registered to the Polycom Converged Management Application™ (CMA™) server. The 128 MB systems include Polycom V700, Polycom VSX 3000A, Polycom VSX 5000, Polycom VSX 6000A, Polycom VSX 7000s, Polycom VSX 7000e, and Polycom VSX 8000.

This feature is supported only on 128 MB systems, which include Polycom V700, Polycom VSX 3000A, Polycom VSX 5000, Polycom VSX 6000A, Polycom VSX 7000s, Polycom VSX 7000e, and Polycom VSX 8000.

You can determine the memory size of your system by referring to the System Information page (System > System Informatio n); the memory size is noted as (64) or (128) after the Model name.

When the Save the Global Directory to System setting (System > Admin Settings > Global Services > Directory Services) is enabled, a 128 MB system

can display up to 5000 entries. When the Save the Global Directory to Sys tem setting is disabled, a 128 MB system stores and displays only the first 1000 entries.

A 64 MB system can display only the first 1000 entries, regardless of whether Save the Global Directory to the System setting is enabled.

When registered to the Polycom CMA server, Polycom V Series and VSX systens cannot register to any other directory server. After running Softupdate, verify the Directory Server settings:

1. Go to System > Admin Settings > Global Services > Directory Servers.

2. If registration to a Polycom CMA server is enabled, disable registration to

all other directory servers.

New Version of People+Content™ IP

Polycom People+Content™ IP version 1.2.1 is now available on the Polycom web site, on the Downloads page for each VSX system. Version 1.2.1 includes performance improvements and fixes to address minor technical issues.

For information about using People+Content IP to display content, refer to the Getting Started Guide for your product.

Release Notes V Series and VSX Systems, Version 9.0.6.1

What’s New in the 9.0.5 Release?

Mixed H.323 and SIP Calls

In version 9.0.5, H.323 and SIP calling can be enabled simultaneously, and the Polycom system can place and participate in mixed H.323 and SIP calls.

To enable H.323 and SIP calling:

1. Go to System > Admin Settings > Network > Call Preference.

2. Select IP H.323.

3. Select SIP.

Changing these settings does not cause the system to restart. H.323 names cannot be all numeric in Polycom VSX software version 9.0.5 and

later.

When the Polycom system is enabled for both H.323 and SIP calling, the user interface includes the following changes:

• The Place a Call screen includes IP H.323 and IP SIP as available call type

selections within Call Quality. For calls dialed manually, the Polycom system attempts to place the call

using the specified call type. For calls dialed automatically, the Polycom system uses the specified call type first in the dialing order.

• On the Network Dialing screen, the Dialing Order can include both

IP H.323 and IP SIP as separate selections.

• The System Status screen includes a dual “Gatekeeper:/Registrar Server:”

entry with distinct visual indicators to display the registration status of both the H.323 gatekeeper and the SIP registrar.

• The available call types for new directory entries include H.323 and SIP.

Release Notes V Series and VSX Systems, Version 9.0.6.1

What’s New in the 9.0.1 Release?

Polycom VSX software version 9.0.1 provides a fix for an issue associated with the password encryption feature introduced in Polycom VSX software version

9.0.

When a Polycom VSX system with Security Mode enabled was upgraded from a previous software version to Polycom VSX software version 9.0, the room password no longer worked. As a result, the Admin Settings became inaccessible even when the previously used room password was correctly entered on the system.

For a Polycom VSX system with password encryption and Security Mode enabled, Polycom recommends that you delete the room password or disable Security Mode before downgrading from sof t wa re versi on 9. 0 or late r to a bu il d pri or to ve rsio n 9. 0.

What’s New in the 9.0 Release?

Some features are only available on the 128 MB systems (V700, VSX 3000A, VSX 5000, VSX 6000A, VSX 7000s, VSX 7000e, VSX 8000).

Refer to the System Information page (System > System Information) for the memory size of the system, noted as (64) or (128) after the Model name.

Polycom Lost Packet Recovery™

This feature is only available on the 128 MB systems (V700, VSX 3000A, VSX 5000, VSX 6000A, VSX 7000s, VSX 7000e, VSX 8000).

Version 9.0 provides improved dynamic bandwidth allocation (DBA) and new error concealment for Polycom Video Error Concealment (PVEC) using Polycom Lost Packet Recovery™ (LPR™). The new DBA algorithm downspeeds the call to reduce packet loss to a manageable level under normal operating environments. This allows Polycom LPR to recreate the remaining lost packets.

Points to note about Polycom LPR:

• Polycom LPR is available on H.323 calls only; it is not supported on SIP or

H.320 calls.

• Polycom LPR is available in point-to-point calls only; it is not supported in multipoint calls.

• Polycom LPR is not available on Avaya networks.

Release Notes V Series and VSX Systems, Version 9.0.6.1

For complete protection against network packet loss, enable both Polycom LPR and DBA; the combination of DBA and Polycom LPR provides virtually error-free video. On average, visible video disruptions can be expected only once every 5 minutes for average packet loss scenarios of 3% or less, and more often for packet loss scenarios higher than 3%.

To use Polycom LPR, both the near -e n d system and the far-end syst e m must have the Enable PVEC setting enabled. If the far-end system does not have this setting enabled, the near-end system uses PVEC rather than Polycom LPR.

SIP Signaling of DTMF Digits

Version 9.0 supports signaling for DTMF digits during SIP calls, as specified by RFC 2833.

Supported DTMF digits include the numbers 0–9, the asterisk (*), and the number sign (#).

This feature is not supported in the following scenarios:

• Calls with AES encryption enabled

• Multipoint calls

Microsoft® Windows® Vista Support for Softupdate

With version 9.0, you can use the Softupdate application with the Microsoft® Windows® Vista updating the software on VSX systems and V Series systems.

, Windows XP, or Windows 2000 operating system when

Indication for Basic Mode

In version 9.0, the Call Statistics screen indicates whether the VSX system or V Series system is operating in Basic Mode.

To view the Basic Mode indicator:

1. Go to System > Diagnostics > Call Statistics.

2. Select .

3. View the Call Type field.

“(Basic Mode)” is appended to the data in the Call Type field when the VSX system or V Series system is operating in Basic Mode.

AES Encryption Icon

With version 9.0, the VSX system or V Series system continually displays an icon whenever AES Encryption is enabled on the system.

Release Notes V Series and VSX Systems, Version 9.0.6.1

The icon behavior is as follows:

• The icon displays as locked throughout the call when AES

• The icon is absent when AES Encryption is not enabled on the near-end

• The icon displays as unlocked throughout the call when AES

The call may not be AES encrypted because the VSX system or V Series system is operating in Basic Mode or because one or more of the far-end systems do not have AES Encryption enabled.

Password Encryption

The password encryption feature is an enhancement to Security Mode. Because Security Mode is only available on the 128 MB systems (V700, VSX 3000A, VSX 5000, VSX 6000A, VSX 7000s, VSX 7000e, VSX 8000), password encryption is also only available on the 128 MB systems.

Encryption is enabled on the near-end system and the call is AES encrypted.

system.

Encryption is enabled on the near-end system but the call is not AES encrypted.

Version 9.0 includes enhanced password encryption for meeting, room, and remote access passwords.

When Security Mode is enabled, the VSX system stores all meeting, room, and remote access passwords using the SHA-1 algorithm rather than using clear text.

Password Display

Meeting, room, and remote access passwords now always appear as a series of asterisks as you type them into a configuration screen or login box.

To enter numbers in a password field, use the remote control number buttons. To enter letters in a password field, press Keyboard on the remote control.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Re-entering to Confirm Passwords

In some cases, you must now re-enter passwords to confirm them.

• When updating or entering a meeting, room, or remote access password,

• When enabling Security Mode, you must now enter and confirm a new

• When enabling or disabling Security Mode, you must now enter and

you are now prompted to re-enter the password to confirm it.

room password, even if a room password is already in use on the system.

confirm each meeting, room, and remote access password that is set.

You cannot change the configuration variables when using uploaded profiles (Utilities > Profile Center) through the system’s web interface, even if the uploaded profiles contain one or more of these variables. These configuration variables are also excluded from downloaded profiles.

roomsw, sw, meetingpassword, websw

New Version of People+Content™ IP

Polycom People+Content™ IP version 1.2 is now available on the Polycom web site, on the Downloads page for each VSX system. Version 1.2 includes performance improvements and fixes to address minor technical issues.

The People+Content IP option key is included with the VSX 8000 and is optional for all other Polycom VSX and V Series systems. For information about purchasing the People+Content IP option, please contact your Polycom distributor.

For information about using People+Content IP to display content, refer to the Getting Started Guide for your product.

Corrected Issues in Version 9.0.6.1

The following table lists issues corrected in version 9.0.6.1.

, and

securemode

Feature Issue ID Description

Conference on Demand

Dynamic Bandwidth

VIDEO-85517 Previously, when "Use PathNavigator for Multipoint Calls"

was set to "Always", the multipoint call through multipoint entry failed in the following circumstances:

• The Polycom VSX failed to register with a gatekeeper;

• The Polycom VSX was registered with a gatekeeper but

the Conference on Demand feature is disabled.

This has been corrected.

VIDEO-85519 A problem has been resolved that prevented the video rate to

return to a higher level after a period of time without packet loss.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Feature Issue ID Description

Encryption VIDEO-85524 In 9.0.6 release, When AES was configured to “When

Firewall Traversal VIDEO-85523 A problem has been resolved that caused the call

Gatekeeper VIDEO-85527 Previously, when DNS server did not return gatekeeper IP

Available”, Polycom VSX could not place H.323 calls to Polycom

® ViewStation®.

This has been corrected.

disconnected if the firewall limited the timeout of TCP connection to less than 120 minutes.

address timely, the Polycom VSX systems failed to send the registration request to gatekeeper after rebooting.

This has been corrected.

Interoperability: Polycom CMA

VIDEO-85525 A problem has been corrected that caused the ISDN-only

Polycom VSX systems to advertise also the IP and SIP capability to Polycom CMA.

VIDEO-85526 Previously, when Polycom VSX downspeeded an H.323 call

after Polycom

® CMA™ Gatekeeper approved a higher call

rate, Polycom CMA’s Site-Link statistics still displayed the originally approved rate instead of the actual rate.

This has been corrected.

Interoperability: RADVISION MCU

VIDEO-85529 Previously, when Polycom VSX placed an ISDN call to a

RADVISION MCU, sometimes the start part of the IVR audio was truncated.

This has been corrected.

Interoperability: Tandberg VCS GK

VIDEO-85528 Previously, when Polycom VSX received join command from

the Tandberg VCS Control Gatekeeper, VSX rebooted. This has been corrected.

Web Interface VIDEO-85518 Previously, when creating a group name in local directory in

Japanese via Web interface, the characters saw garbled from TV interface.

This has been corrected.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Corrected Issues in Version 9.0.6

The following table lists issues corrected in version 9.0.6.

Feature Issue ID Description

Directory VIDEO-82381 A problem has been resolved that prevented the Local

Directory from importing through the Web Interface if it contained more than175 entries.

VIDEO-82373 A problem has been corrected that caused the Polycom VSX

system to display duplicate entries in the Directory if it failed to register to the Global Directory Server after rebooting.

Dynamic Bandwidth

Interoperability: Polycom MGC

Interoperability: RADVISION

Interoperability: Polycom RMX 2000

Interoperability: Switches

Monitors VIDEO-82376 Previously, when Monitor 1 was configured as VGA, sending

Network VIDEO-82371 In previous versions, after a lost LAN connection is restored,

VIDEO-82377 Polycom VSX now correctly renegotiates the bandwidth to a

higher level after a period of time without packet loss.

VIDEO-82369 Previously, when the Polycom V500 system connected to the

Polycom MGC in H.264 video switching mode, the V500 crashed. This has been corrected.

VIDEO-82374 A problem has been resolved that prevented the Polycom

VSX system from using an E.164 number when using H.460 via a RADVISION gateway.

VIDEO-82370 When the Polycom VSX system sent content and then

received content from the far site in a call using the Polycom RMX 2000, the VSX did not decrease the people video transmit rate correctly. This problem has been corrected.

VIDEO-82380 In previous versions, the Polycom VSX system could not

make calls to some cell phone networks if the PRI switch protocol was configured as NTT INS-1500. This problem has been corrected.

content caused missing pixels in the upper left corner of the screen. This problem has been resolved.

the VSX system did not re-establish a Global Directory Server (GDS) connection to Polycom CMA until the VSX is rebooted or GDS was disabled and re-enabled. This has been corrected.

Secure Mode VIDEO-82379 You can now access the Polycom VSX system via a secure

telnet session.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Feature Issue ID Description

User Interface VIDEO-82382

VIDEO-74426

VIDEO-82375 The web interface now correctly displays the Use

VIDEO-82378 The system now adjusts for NZDT correctly when you enable

VIDEO-82372 After you update the profile with Screen Saver Text and Logo

in previous versions, if the System Name contains special characters, including those used for non-English languages, the system displays an error when you attempt to save the System Profile.This has been corrected.

PathNavigator for Multipoint Calls option when the system registers to PathNavigator.

Auto Adjust for Daylight Saving Time.

Screen Text containing Japanese characters, the text strings now display correctly.

Corrected Issues in Version 9.0.5.2

The following table lists issues corrected in version 9.0.5.2.

Feature Issue ID Description

Calling VIDEO-76641

VIDEO-76643

You can now call an E.164 number when the system is connected to another system using a similar E.164 number.

When you place a call from a locally saved Global Addressbook, you can now call endpoints with presence icons that show they are unavailable.

Internal Multipoint VIDEO-76638 The Make Me Broadcaster command now works correctly in

multipoint calls hosted by the VSX system.

General VIDEO-76647 A problem has been corrected that could prevent a profile

from uploading to the Polycom VSX system. The system’s Advanced ISDN settings are now saved when

you delete the system settings.

Recording VIDEO-76640 In previous versions, content stops if you change the VCR

Record Source using API commands. Now, changing the record source without affecting the content display.

User Interface VIDEO-76636 In previous versions, the near-end system’s name is 36

characters long, the name was truncated when displayed on the far-end system. This problem has been resolved.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Corrected Issues in Version 9.0.5.1

The following table lists issues corrected in version 9.0.5.1.

Jira ID Issue Description

VIDEO-72196 Interoperability

Polycom Converged Management Application (CMA)

VIDEO-72196

VIDEO-72346

VIDEO-72204 Profiles If you updated VSX system software, including erasing

VIDEO-71250

VIDEO-72206

Interoperability Polycom ReadiManager SE200

SIP When a VSX system hosted an H.323 multipoint call and

If Display Name in the Global Directory was unchecked on the VSX system, the VSX system sometimes could not register to the Polycom CMA server. This has been corrected.

If Display Name in the Global Directory was unchecked on the VSX system, the VSX system sometimes could not register to the ReadiManager SE200. This has been corrected.

When using the ReadiManager SE200 to perform automatic provisioning, the V Series and VSX systems did not retain the provisioned gatekeeper entries . This has been corrected.

system flash memory and going through the out-of-box setup , you sometimes could not store or upload a profile to the VSX system and received an error message instead. (This is usually referred to as the setup wizard.) This has been corrected.

then attempted but subsequently failed to add a SIP site to the call, the Polycom VSX system that was previously connected to the call via H.323 sometimes crashed or was no longer able to see video even if the host system hung up the call and attempted to reconnect with the H.323 system. This has been corrected.

When a VSX system was added to an existing multipoint SIP call, some or all sites sometimes displayed frozen video or rebooted. This has been corrected.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Issue Description

VIDEO-72190 Softupdate When updating to VSX software version 9.0.5 from a

previous version, the Softupdate sometimes appeared to complete but the software was not updated. This has been corrected.

VIDEO-72199

VIDEO-72207

VIDEO-72203 Web Interface When using the system’s web interface to place a call, if you

User Interface When Display Icons in a Call was disabled on a VSX system,

if you placed a call with the VSX system and then used the remote control to decrease the volume , the remote control then ceased to function during the call. This has been corrected.

When a VSX system had Monitor 1 set to VGA and Near/Far while Monitor 2 was set to S-Video and Near/Far/Content, the VSX system would not retain the Content setting after a reboot. This has been corrected.

used the Call button on the system’s web interface remote control to place a call before using any of the other buttons on that remote control, the VSX system became unusable and required a reboot. This has been corrected.

Corrected Issues in Version 9.0.5

The following table lists issues corrected in version 9.0.5.

Jira ID Issue Description

VIDEO-67632

VIDEO-67626

API The

when you used the remote control to access presets. This has been corrected.

Changing the SNMP community name using the

snmpcommunity set

local interface or the system’s web interface to show the change made through the API. This has been corrected.

preset register

command did not give notification

command did not cause the system’s

VIDEO-65625 H.239 If you disabled H.239 (System > Admin Settings > Network

> Call Preference), you also needed to disable Polycom LPR. Otherwise, when you placed a call, the system could be very slow or unresponsive. This has been corrected.

VIDEO-67639 Interoperability

PathNavigator

VIDEO-67633 Interoperability

Polycom ReadiManager SE200

When a VSX 3000A or VSX 7000s system was registered to the Polycom PathNavigator™ gatekeeper, the Gatekeeper screen (System > Admin Settings > Network > IP > H.323 Settings) erroneously displayed a nonfunctional selection (“When calling 4+ sites”). This has been corrected.

The Polycom logo displayed instead of the near-site or far-site video when a live image was requested during a call with the Polycom ReadiManager® SE200. This has been corrected.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Issue Description

VIDEO-67637, VIDEO-68095

People+Content IP When both H.323 and SIP were enabled (System > Admin

Settings > Network > Call Pref erenc e), People+Content IP could not successfully show content to all sites in a SIP call or a mixed H.323 and SIP call. This has been corrected.

VIDEO-67628

SIP The SIP Settings screen (System > Admin Settings >

Network > IP > SIP Settings) in the system’s local interface did not show asterisks when the SIP password was entered. This has been corrected.

VIDEO-67631

Pressing the Far button on the remote control during a SIP call did not allow the user to control the far-site camera. This has been corrected.

VIDEO-67992

After a system successfully registered with a SIP server, the SIP registration would fail after the system was rebooted. This has been corrected.

VIDEO-68087 Softupdate If the user elected to not retain the directory entries and

sample sites when using Softupdate, the Speed Dial and Contacts were accessible from the Place a Call screen but could not be dialed. This has been corrected.

VIDEO-67626

User Interface Changing the Read-Only Community name (System >

Admin Settings > Global Services > SNMP) did not cause the system’s web interface or the API to show the change. This has been corrected.

VIDEO-67629

The Password field for the Global Directory (System > Admin Settings > Global Services > Directory Servers) did not allow you to enter letters. This has been corrected.

VIDEO-67630

The Global Directory Servers screen (System > Admin Settings > Global Services > Directory Servers) did not show asterisks when a password was entered. This has been corrected.

VIDEO-67635

When Monitor 1 was set to VGA with a resolution of 1024x768 (System > Admin Settings > Monitors > Monitors), some screens displayed the page numbers outside of the border at the bottom of the screen. This has been corrected.

VIDEO-67990

When Monitor 1 was set to VGA with a resolution of 1024x768 (System > Admin Settings > Monitors >

Monitors), the Security screen (System > Admin Settings > General Settings > Security) displayed a misaligned

Allow Access to User Settings checkbox. This has been corrected.

VIDEO-68082

The availability control on the contact list home screen displayed the “available” or “busy” status in all capital letters. This has been corrected.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Issue Description

VIDEO-67626

VIDEO-67636

VIDEO-67640

VIDEO-67641

Web Interface Changing the Read-Only Community name (Admin

Settings > Global Services > SNMP) did not cause the system’s local interface or the API to show the change. This has been corrected.

When accessing the system’s web interface on a laptop computer with the resolution set to 1024x768 or below, the Welcome screen did not include a scroll bar by default and resulted in the bottom of that screen not being visible. This has been corrected.

The Sites screen (Admin Settings > General Settings > Sites) did not include instructions about how to display a site name on the home screen. This has been corrected.

The Remote Monitoring feature did not display video until after the Web Director was accessed. This has been corrected.

Corrected Issue in Version 9.0.1

The following table lists the issue corrected in version 9.0.1.

Jira ID Issue Description

VIDEO-66690 Security Mode When a Polycom VSX system with Security Mode enabled

was upgraded from a previous software version to Polycom VSX software version 9.0, the room password no longer worked. As a result, the Admin Settings became inaccessible even when the previously used room password was correctly entered on the system. This has been corrected.

Corrected Issues in Version 9.0

The following table lists issues corrected in version 9.0.

Jira ID Issue Description

VIDEO-64161

VIDEO-64163

VIDEO-25802 Directory New directory entries created in a new local category were

API Changes made using the

did not result in any command feedback. This has been corrected.

Using the on the VSX system did not work correctly. This has been corrected.

not visible when you tried to view them the first time, until you moved around in the screen. This has been corrected.

timediffgmt

audiotransmitlevel

command to provision the time zone

command

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Issue Description

VIDEO-64140

Global Management System

VIDEO-64156

VIDEO-64163

VIDEO-61821 Interoperability

Avaya

VIDEO-64208

Interoperability Nortel

VIDEO-64209

VIDEO-64210

VIDEO-64211

VIDEO-64212

The Management Servers list (System > Admin Settings > Global Services > Management Servers) displayed URLs for the Polycom Global Management System™ even after the VSX system or V Series system unregistered from the Global Management System. This has been corrected.

When the Global Management System became unavailable, the VSX system or V Series system no longer displayed the global directory entries even when Save Global Directory to

System (System > Admin Settings > Global Services > Directory Servers) was enabled. This has been corrected.

Using the Global Management System to provision the time zone on the VSX system or V Series system did not work correctly. This has been corrected.

When V500 systems, VSX systems, or Polycom HDX systems registered to the 8700 ACM and attempted to call into the Polycom RMX, the call sometimes connected without video. This has been corrected.

SIP calls placed between VSX systems or V Series systems and the Nortel Multimedia Communication Server (MCS) Multimedia PC client did not connect. This has been corrected.

When a call was transferred between VSX systems or V Series systems and the Nortel MCS Multimedia PC (MMPC) client using the “Announce Caller” feature, the resulting call included audio but not video on all systems. This has been corrected.

When a caller used the “Call Park” feature during SIP calls between VSX systems or V Series systems and the Nortel MMPC client, the other system in the call was not put on audio and video hold. This has been corrected.

During a SIP call between VSX systems or V Series systems

unHold

using the Nortel MCS, using the

Telnet command to

remove the hold status on a call did not remove the hold

unHold

status on the system that initiated the

command. This

has been corrected. Using Telnet to register VSX systems or V Series systems

with the Nortel MCS did not work. This has been corrected.

VIDEO-64134 Interoperability

SoundStation VTX 1000

In voice over ISDN calls using the Polycom SoundStation VTX 1000® conference phone and a VSX system, the button for hanging up the audio call did not display on the SoundStation VTX 1000. This has been corrected.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Issue Description

VIDEO-64127, VIDEO-64138

Interoperability TANDBERG

In ISDN calls with a TANDBERG MPS 800 and VSX 7000s or VSX 7000 system at call rates of 384 kbps and 512 kbps, the VSX 7000s or VSX 7000 system did not maintain 30 frames per second when sending H.239 content. The frame rate also sometimes did not return to 30 fps after the H.239 stream was stopped. This has been corrected.

VIDEO-64158

The payload number and clock rate for far-end camera control of TANDBERG systems were incorrect on VSX systems. This has been corrected.

VIDEO-48009 SIP When a Polycom VSX system called a SIP account logged in

to Windows Messenger, messages sent to the Polycom VSX system from Windows Messenger were interpreted as video calls. This has been corrected.

VIDEO-64167 SNMP The SNMP MIBs (Management Information Bases) on the

VSX 7000 and VSX 7000s systems displayed two identical ifIndex values. This has been corrected.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Issue Description

VIDEO-64129

VIDEO-64142

VIDEO-64169

VIDEO-54055

VIDEO-64132

VIDEO-64146

VIDEO-64155

VIDEO-30630

VIDEO-25800

VIDEO-60987

User Interface On the VSX7000, VSX7000s, VSX7000e, and VSX 8000

systems, the Camera Control setting (System > Admin Settings > General Settings > Serial Port) was unavailable when the RS-232 Mode setting was set to Camera PTZ (or Sony PTZ in previous versions). This has been corrected.

While performing an ISDN software update (System > Utilities > Software Update), the VSX system allowed the user to attempt to place a call, and the VSX system would then crash. This has been corrected.

The ping test is now available for use with both H.323 and non-H.323 devices (System > Diagnostics > Network > PING).

After you registered a gatekeeper through System > Admin Settings > Network > IP > H.323 Settings, Polycom VSX systems with IP only or with ISDN disabled were displaying truncated E.164 extension information on the home screen. This has been corrected.

Web Interface Using both single-byte and double-byte characters when

entering a new Directory entry caused the Localized Name to be corrupted when it was saved. This has been corrected.

The complete list of local and global directory entries was not always displayed when accessing the directory (Place a Call > Directory). This has been corrected.

After installing People+Content IP on a PC and connecting People+Content IP to the VSX system or V Series system, pressing the Graphics button on the remote control in the web interface (Tools > Remote Control) did not send the content and displayed an error message. This has been corrected.

If you used the web interface to join a conference with a meeting password, the meeting password you entered was also set as the meeting password for your system. This has been corrected.

SIP registration status was not displayed in the system’s web interface. This has been corrected.

On the VSX 3000, the System Information page (Tools > System Information) of the system’s web interface displayed the memory size of the system as (128) rather than as (64). This has been corrected.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Feature Limitations

The feature limitations for version 9.0.6.1 are listed in the following table. If a workaround is available, it is noted in the table.

Jira ID Feature Limitation

VIDEO-25793 AES Encryption You cannot activate encryption during a call. VIDEO-25872

VIDEO-69904

VIDEO-54035

VIDEO-54039

VIDEO-25817 VIDEO-25839

VIDEO-25846

VIDEO-25850

VIDEO-25801 VIDEO-30124

VIDEO-25849 VIDEO-25893

VIDEO-44551

VIDEO-65056

Analog Phone Incoming POTS (analog phone) calls will not be reported in the

Recent Calls list. A Polycom VSX system and an analog phone cannot establish

a call when the meeting password is set on the Polycom VSX system.

API If you execute the

Camera button on the Polycom VSX remote control or after executing the system does not take you to the home screen until you execute the

button home

Attempting to execute the opening parenthesis but no closing parenthesis with the accompanying text causes the text to be defaulted to no text and fails to return an error message about illegal parameters.

The

prilinebuildout set

-7.5 and -22.5. The

vcstream register

API interface. The

remotecontrol enable all

if remote control is disabled from the API interface, you must restart the system to enable it again.

The

gatewayprefix set

commands accept special symbols as value parameters. Entering another command with any value parameter forces a restart.

API interfaces do not report when the system restarts. The

callencryption

subcommands: Each of these returns a

The

chaircontrol set_password

Use the command If rollover dialing occurs (for example, the system automatically redials a number as ISDN if it fails to connects when dialed as IP), the system will report an “ended” event for each failed attempt.

chaircontrol set_password

The and therefore prevents setting the password through the API.

button home

button camera

command a second time.

gatewayprefix set

command supports the following

whenavailable|required|disabled|get

yes|no

callinfo all

command after clicking the

command, the Polycom VSX

sleeptext set

command does not work for values

command does not work from the

command is not working. So

and

gatewaysuffix set

value.

command does not work.

instead of

command with an

API

gatewaysuffix set

display call

command does not work

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-44547

VIDEO-55622

VIDEO-56545

VIDEO-57527

VIDEO-57528

VIDEO-65001

VIDEO-65060 VIDEO-65059

API If the control application issues a

when a system that had been playing content is in the process of stopping content, the system may return the error “vcbutton [play|stop] command ignored due to current processing". If this occurs, restart the system to restore functionality.

The screen name returned by the does not always match the name displayed in the user interface. When programming and calling a screen, please navigate to that screen in the user interface and then use the

getscreen

API command to determine the API name for that

screen. If you send a command to change a setting on a user interface

screen while viewing that screen on the monitor, you might have to leave the screen and return to it to see the change take effect.

Using the

set

parameter to set values with the

snmpcommunity, snmpconsoleip, snmplocation snmpsystemdescription

API commands restarts the system

without prompting the user. When requireacctnumtodial and validateacctnum are

enabled, the user is prompted for setaccountnumber when attempting to dial a call through the API. When the user enters the setaccountnumber command, an “error: command not found” message is returned and the call cannot be dialed. A workaround is to disable the requireacctnumtodial and validateacctnum commands.

The chaircontrol req_term_name, chaircontrol set_term_name, chaircontrol view_broadcaster, and chaircontrol set_password API commands do not function correctly.

In Polycom VSX software version 9.0.1 and later, you can no longer use the

adminpassword set

the room password on the system. The

streamannounce

command does not work and does not

set or get the streaming announcement setting. The

callpreference sip yes

64 MB systems when you enter “y” to “restart system for changes to take effect. restart now? <y,n>”.

vcbutton play command

vcbutton [play|stop]

getscreen

API command

snmpadmin

, and

API command to change

command does not restart

VIDEO-25765

VIDEO-25688

VIDEO-61218

VIDEO-30190

Audio Playback volume is not adjustable on the start-up language

selection screen. When one VCR or DVD player is connected to a VSX 6000 or

VSX 7000 to play content into the call, and another is connected to record the call, audio from the VCR or DVD player content is not recorded.

Calls placed at a call speed of 64 kbps connect at G.729A 8 kbps audio rather than at G.722 16 kbps audio.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-55522 Boot UI Downgrading the boot UI on the VSX 3000 or VSX 3000A may

damage the boot UI and cause the Polycom VSX system to become unusable.

VIDEO-30290

VIDEO-57377

VIDEO-69899

VIDEO-70444

VIDEO-80332

VIDEO-79798

Calling On a VSX 8000, if you make a POTS call to an analog or cell

phone and then try to call the number again from the Recent Calls list, the call is dialed as voice over ISDN if ISDN Voice is listed ahead of Analog Phone in the Call Preference dia ling order. To work around this behavior, set Analog Phone ahead of ISDN Voice in the Call Preference list.

If the VSX 5000 has the Preferred Dialing Method setting (System > Admin Settings > Network > Call Preference) set to Auto and the Call Type is changed from IP to SIP, the VSX 5000 may display an error message and may not successfully dial and connect a call with a SIP site. A workaround is to change the Preferred Dialing Method to Manual before changing the Call Type to SIP.

If you enable both H.323 and SIP (System > Admin > Network > Call Preference), designate Manual as the Preferred Dialing Method (System > Admin > Network > Call Preference > Next), create a single-site entry in the Directory, and call that entry, you receive a dialog box for confirming the call protocol. However, at this point, the call will connect regardless of what buttons you press on the remote control.

If you use the VSX system to place an IP call and then attempt to call an audio-only site, if the audio-only site does not answer, the VSX system does not time out the audio-only call automatically. A workaround is to hang up the audio-only call manually.

H.323 names cannot be all numeric in Polycom VSX software version 9.0.5 and later.

In a V.35 call at 768 kbps or higher, adding another site to the call causes the VSX system to crash when it downspeeds.

In multipoint calls hosted by the VSX 8000, the frame rate drops from 30 fps to 15 fps when more than four sites participate in the call.

VIDEO-54060

Cameras The V700 incorrectly displays an icon for the second camera

option if you press Far twice on the remote control during a call.

VIDEO-25740

There is no way for a user to get camera control for a camera that is set to the content channel.

VIDEO-25792

The Camera Calibration screen will always be displayed for the VSX 7000e and VSX 8000, even though automatic camera tracking only works with a Polycom PowerCam™ Plus camera.

To avoid a “keystone effect” in which the video image appears

VIDEO-25511

tilted, make sure that the VSX 5000 camera is pointed perpendicular to the subject.

VIDEO-25835 Chair Control Selecting Acquire Chair on a VSX 7000 that can host

multipoint calls may disable Discussion mode view.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-25705 Closed Captions Closed captions cannot be sent through a gateway.

VIDEO-44515

Conference on Demand

Conference on Demand calls to ISDN sites may fail when dialed from an H.323-only system. To work around this issue, provide the full international number, including country code,

for ISDN sites. VIDEO-57503, VIDEO-57517, VIDEO-57478

When using a VSX system to initiate an all-IP or mixed IP and

ISDN, multipoint, H.264 Conference on Demand call using

PathNavigator, you may be unable to send content and may

instead receive a “Far site does not support dual streams”

message after pressing the graphics button on the remote

control. A workaround is to use H.263 instead. VIDEO-26068

Configuration Do not change the Polycom VSX system monitor setting while

sending content. VIDEO-26182,

VIDEO-43170, VIDEO-57151

Factory camera presets (press the Near button and then the

Preset button on the remote control) are not available on the

VSX 5000. However, you can program presets after you

receive the system. VIDEO-25741 Directory System names using double-byte character sets (DBCS)

should be edited in the directory using the system’s web

interface. VIDEO-54932 Dual Monitor

Emulation

Content is displayed incorrectly on the Polycom VSX 3000

when it is configured for dual monitor emulation and is

receiving content during a 1472 kbps call. Workarounds

include disabling dual monitor emulation on the Polycom VSX

3000 or reducing the call speed to 512 kbps. VIDEO-85515 Dynamic

Bandwidth

For 64M Polycom VSX systems, the video protocol may drop

down from H.264 to H.263 when experiencing packet loss, and

it does not roll back to H.264 after a period of time without

packet loss. VIDEO-54178 Far End Camera

Control

Far-site camera presets that you set with the V700, VSX 3000,

and VSX 5000 may not work. VIDEO-57410 Gatekeepers When the primary gatekeeper becomes unavailable, the

VSX system may require up to 5 minutes to successfully

gatekeeper becomes available again, the VSX system may

require up to 10 minutes to successfully re-register to the

primary gatekeeper. If the gatekeeper (such as the

PathNavigator) is set to routed mode and the VSX system is in

a call when the gatekeeper goes down or comes back online,

the call will be disconnected.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-25761

VIDEO-62740

VIDEO-72843

VIDEO-74303

VIDEO-74302

VIDEO-25795 VIDEO-40448

VIDEO-74301

Gateway Calls In calls through a gateway, selecting a far-site camera source

that is not being used shows frozen video from the previous

camera source, instead of a blue screen.

H.323-H.320-H.323 gateway calls placed using a valid TCS4

extension delimiter (##) between the dial string and E.164

extension fail to connect to the second gateway and, ultimately,

to the system being called. A workaround is to dial the call

without ## and the E.164 extension, allow the call to connect to

the second gateway, and then manually enter the E.164

extension of the system you are calling.

Global Directory If a 64 MB system (V500, VSX 3000A, VSX 5000, VSX 6000A,

VSX 7000s, VSX 7000e, VSX 8000) is registered to a Polycom

CMA 5000 and configured to store a local copy of a Global

Directory that contains more than 1000 entries, the system

crashes when you attempt to open an entry if the directory

includes more than 1000 entries.

After the system registers with Polycom CMA 5000 and

unregisters from other directory servers, the System Status

page incorrectly shows status for the disconnected directory

servers.

When you search the directory server for an invalid address

and then attempt to return to the Place a Call screen, the

system responds slowly.

Global Management System

Global Management System 7.0 does not display H.320

information for V500 systems.

The Global Management System Call Statistics screen shows

up to only three sites in an internal multipoint call, even when

more than three sites are connected.

The Global Management System does not display time server

and Global Directory alerts correctly for managed Polycom

VSX systems.

Global Management System provisioning of the Primary and

Secondary Call Types is not supported.

H.264 The following conditions apply to H.264:

• On Polycom VSX systems other than a VSX 8000 using TV monitors, H.264 is supported in point-to-point calls up to 768 kbps. On systems that use an interlaced camera, the transmit preference at 768 kbps is H.263 Pro-Motion.

• On Polycom VSX systems other than a VSX 8000 using single-monitor VGA, H.264 is supported in point-to-point calls up to 512 kbps.

• H.264 Pro-Motion is supported in point-to-point calls between VSX 8000 systems up to 1.4 Mbps.

• On VSX 8000 systems, H.264 is supported in calls with up to four sites.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-25762

H.331 When broadcast mode is enabled on a V.35 system and the

VIDEO-30762

VIDEO-25784 Interoperability

ADTRAN TSU 100

VIDEO-25750

Interoperability Aethra

VIDEO-57288 VIDEO-57524

VIDEO-74430

VIDEO-57299 VIDEO-57529

audio protocol is set to G.711U, the far site might hear a pop when the call is disconnected.

In an H.331 call between two Polycom VSX systems with H.264 video configured and with People+Content turned off, neither site can send content to the other site. To resolve this problem, the site sending content shou l d e na b le People+Content.

When enabling People+Content in the H.331 configuration of a V.35 system, you must also enable H.239 to send content.

With V.35 systems, VSX systems can crash when in a call at 1280 kbps.

In H.323 calls between a VSX 8000 system and the Aethra Vega Star Gold version 5.1.35, content is sent from the Aethra system as a single stream and no far-site video is displayed on the VSX 8000, even though the VSX 8000 displays the dual stream icon.

In H.263 calls between a VSX system and the Aethra Vega X7 version 11.1.4 beta, the Aethra Vega X7 may constantly repeat the caps exchange if the Aethra Vega X7 has annex J and I enabled on its H.263 cap set. As a result, the VSX system call log may show constant capset exchange requests from the Aethra Vega X7, and the VSXsystem video may display constant video updates throughout the duration of the call.

In UDP SIP calls with the Polycom VSX system, the Aethra X3 system does not receve video, and the Aethra system eventually reboots.

When a VSX 5000 calls the Aethra Vega Star Gold version

6.00.0022 at 336k over ISDN, the VSX 5000 may show only

the near-site video after AES encryption is confirmed.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-25528 VIDEO-25523

VIDEO-25521

VIDEO-25520 VIDEO-25516

VIDEO-25524

VIDEO-25522

VIDEO-25519

VIDEO-25515

VIDEO-55929

VIDEO-57521

VIDEO-60302

VIDEO-62331

Interoperability Avaya

AES Encryption is not supported while registered to the Avaya Communication Manager (ACM).

When a V500 system or VSX system attempts to call another V500 system or VSX system through the ACM, the near-site system continues to ring if the far site rejects the call and has Auto Answer Point-to-Point Video or Auto Answer Multipoint Video set to No.

NAT is not supported for systems registered to the Avaya Communication Manager.

While connected to the ACM, telephony features are not supported to systems behind a neighboring gatekeeper.

Cisco PIX does not pass through Annex H which is required by the ACM. V500 systems and VSX systems will not connect calls across a Firewall that does not pass Annex H.

Call forward busy/Don’t Answer does not work with a multipoint VSX system set to forward (registered to the ACM).

Avaya's IP Softphone (IPSP) with video set to manual will not negotiate video with sites registered to a neighboring gatekeeper.

In calls placed from a V500 system or VSX system, the far-site system name may show a neighboring gatekeeper, such as “PathNavigator,” instead of the actual system name.

G728 k and G722.1-16 k audio codecs are not available when registered to the ACM.

If a Polycom iPower™ system hosts multipoint calls and calls an Avaya IP Softphone (IPSP), a V500 system using Avaya, or a VSX system using Avaya, the call does not connect.

In multipoint calls, far-site names are displayed as the system name entered on the ACM for each system rather than as the local system name.

V500 systems or VSX systems configured for NTSC and using the ACM may incorrectly send 4CIF video (normally a PAL format) while sending content.

The Gatekeeper IP Address field is cleared and you must manually re-enter the Gatekeeper IP address after setting Use Gatekeeper (System > Admin Settings > Network > IP > H.323 Settings) to Off and then changing it to On.

When a V500 system or VSX system that is registered to the ACM is in a call with a V500 system or VSX system that is registered to the PathNavigator, audio is not transmitted to the system that is registered to the ACM.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-65178

Interoperability Avaya

VIDEO-65424

VIDEO-80338

VIDEO-30365, VIDEO-30606

Interoperability Cisco PIX

VIDEO-39276

VIDEO-57636

VIDEO-46631 VIDEO-61807 Interoperability

Codian

When Use Gatekeeper (System > Admin Settings > Network > IP > H.323 Settings) is set to Specify with PIN, the system may attempt to register with a different gatekeeper when an incorrect PIN is entered.

If the V500 system or VSX system is registered with the ACM but is subsequently disconnected from the network, when network connectivity returns, the V500 system or VSX system may not re-register with the ACM automatically.

In a call between the VSX system and the Avaya 1X Communicator (version 5.2.947 patch 1003), the VSX system may receive erratic video.

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 firewall among systems with H.239 enabled, the V Series system or VSX system outside of the firewall may not receive video when other sites connect. To avoid this, disable H.239 on all sites.

V Series systems or VSX systems with AES encryption enabled cannot connect using H.460 with Cisco PIX 506.

V Series systems or VSX systems with H.239 enabled may not be able to send or receive content using H.239 with Cisco PIX

515. A workaround is to disable H.239.

When a VSX system places a 768 kbps or higher call to the Codian bridge, the Polycom VSX system may become unresponsive and must be restarted. A workaround is to place a call at 512 kbps or 384 kbps.

VIDEO-65689

VIDEO-25512

VIDEO-65198 VIDEO-65201

VIDEO-65200

Interoperability iPower

Interoperability LifeSize

In H.323 multipoint calls with AES encryption, with a Polycom VSX system hosting a multipoint call with iPower and Polycom PVX™, iPower will not transmit video if Polycom PVX is the second site. Instead, call the Polycom PVX system first.

When an iPower dials into a VSX 7000e that is hosting the multipoint call and another VSX system joins the call, the iPower will disconnect. To work around this issue, connect the iPower as the second or later participant in the conference.

When using the internal multipoint capabilities of the VSX 8000 to connect a LifeSize Room system to a multipoint SIP call, video freeze may occur on the far-end systems.

In a point-to-point SIP call between a LifeSize Room system and another system, both systems have distorted audio. This occurs both when the LifeSize Room system places a call and when the LifeSize Room system receives the call.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-44503

VIDEO-39278 VIDEO-43386

VIDEO-25790

VIDEO-57579

VIDEO-57596

VIDEO-64209

VIDEO-65674

Interoperability Linksys

Interoperability Microsoft

Interoperability Nortel

Systems behind Linksys BEFSR41 will not receive calls. Use of the V Series system or VSX system with a wireless

network bridge behind a Linksys WRT54G wireless broadband router may be problematic and has not been qualified. If connectivity problems arise, ensure that the WRT54G has the latest available firmware installed on it.

Linksys RV082 does not work in H.460 calls with Polycom VSX systems and the Polycom Video Border Proxy™ (VBP™).

Linksys BEFSX41 routers may restart in calls that use H.460. Polycom VSX systems running version 8.5 in UPnP setups with

Linksys (and maybe other) NAT boxes cause video calls to stop connecting.

V Series systems and VSX systems can make but not receive calls when behind a Microsoft® MN-500 UPnP device.

V500 and VSX systems may unregister to the Microsoft Live Communications Server (LCS) every nine hours.

When V500 and most VSX systems are connected to the Microsoft LCS, QCIF video is sent and is not scaled up to CIF in a 3-way or higher multipoint call. This limitation does not affect the VSX 8000 systems.

Communication is not established when a Polycom VSX system or V Series system attempts to communicate with the Nortel Multimedia Communication Server (MCS) or MCS Media Application Server (MAS) using the syntax

conference@<server>

, because the Nortel MCS and Nortel

MAS support Digital Video Express (DIVX) video only. While connected to a Nortel MCS server, when a VSX system

calls another VSX system or calls the Nortel MCS Multimedia PC (MMPC) client, the call does not route to voice mail when there is no answer.

VIDEO-54925 Interoperability

Olevia

Using a composite connection between an Olevia monitor and the PAL V500 may result in compromised signal quality. A workaround is to use an S-Video connection instead.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-56720

VIDEO-55678

VIDEO-61215

VIDEO-61764

Interoperability PathNavigator

When you use a VSX 8000 system that is registered to the PathNavigator gatekeeper to dial far sites using the system names, the VSX 8000 may be idle and may not provide any audio feedback that the call was placed before actually connecting the call.

If multiple VSX systems are registered to the same PathNavigator gatekeeper and have PathNavigator set to Always, attempting to place a multipoint call between the systems may fail and may instead return a “Cannot connect call, network error” message. A workaround is to set PathNavigator to Dynamic instead.

When two V Series systems or VSX systems call each other simultaneously when registered to the PathNavigator gatekeeper, one of both of the systems may crash and have to be restarted. A workaround is to set Auto Answer Point-to-Point Video or Auto Answer Multipoint Video (System > Admin

Settings > General Settings > System Settings > Call Settings) to No to prompt you to manually answer an incoming

call. When V Series systems or VSX systems are registered to the

PathNavigator gatekeeper, directory additions are saved inconsistently as either IP addresses or as E.164 extensions, depending upon the multipoint scenario. As a result, users may be prompted to save the directory addition for the same site more than once.

VIDEO-70933

VIDEO-74305

VIDEO-74429

VIDEO-69200 VIDEO-69201

Interoperability Polycom Converged Management Application™ (CMA™)

Interoperability Polycom HDX 4000

When you attempt to use the Polycom Converged Management Application™ (CMA™) system to perform a Softupdate on a VSX system, the Polycom CMA system automatically generates a default command line that includes a

-kb default switch. This -kb switch validates both the Software

Key Code file and the Option Key Code file. However, if the Option Key Code file is not present, the Softupdate fails. A future workaround may be to use an optional -ksb switch to validate only the Software Key Code file.

When a VSX system registers to a Polycom CMA 5000, an alert on the System Status page incorrectly indicates a problem with the Global Directories while the directory entries are downloaded to the system.

On a VSX system that is registered to Polycom CMA 5000, disabling the registration does not take effect immediately.

When a Polycom HDX 4000™ system calls a VSX 8000 system and sends content, if the VSX 8000 user changes the monitor assignment during the call from VGA to Monitor 1 or from Monitor 1 to VGA via the system’s web interface, the video on Monitor 1 freezes or the content is lost. A workaround is for the Polycom HDX 4000 to resend the content.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-39277

VIDEO-74300

VIDEO-25861

VIDEO-25733, VIDEO-29979

VIDEO-56707

VIDEO-74484

VIDEO-74483

VIDEO-7448

VIDEO-74497

VIDEO-80333

Interoperability Polycom MGC

H.320 calls to a Polycom MGC™ continuous presence, H.239, and IVR conference transmit H.263 video instead of H.264.

When you use a Polycom Visual Concert ™ to send content from a VSX 7000 while in an MGC-25™ conference configured for software video session mode, the VSX system crashes.

Some ISDN sites may fail to connect when blast-dialing from Polycom MGC. Redial any sites that fail to connect manually.

When the Polycom MGC dials out to the Polycom VSX system in H.323 Pro-Motion, it connects H.263 (no annexes) at 30 fps. This is due to a difference in the way the Polycom MGC and Polycom VSX system set rates in their video caps and how they use the caps to determine the call rate. The result is that a 768 kbps call looks to the Polycom VSX system like a 704 kbps call, so Pro-Motion is not selected as the transmit video mode. The workaround for this is to set the Polycom VSX system to do Pro-Motion at 512 kbps and above.

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.

When a VSX system joins a continuous presence call hosted by Polycom MGC-50+™. the VSX system negotiates H.263 video instead of H.264 video.

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.

VIDEO-51036 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.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-43239

Interoperability RADVISION

VIDEO-25691

VIDEO-57369

VIDEO-57142, VIDEO-57259

Interoperability Polycom ReadiManager

VIDEO-62334

SE200

VIDEO-80207 Interoperability

Polycom RMX 1000™

VIDEO-74304 Interoperability

Polycom RMX 2000™

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.

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..

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-36628 VIDEO-25798

VIDEO-57435

VIDEO-64267

VIDEO-66556, VIDEO-71271

VIDEO-71281

VIDEO-71266

VIDEO-72103

VIDEO-74489

VIDEO-74488

VIDEO-80342

VIDEO- 74358

Interoperability Sony

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.

In an H.320 call with a Sony PCS-G50 v2.6.1 system with H.239 enabled, the Sony system’s video freezes after the call connects.

Far-end camera control (FECC) does not work in SIP calls between VSX systems and Sony PSS-1, PDX-G50, or XG80 systems.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-25880

VIDEO-30086

VIDEO-30669

VIDEO-30643

VIDEO-26123

VIDEO-32644

VIDEO-47902

VIDEO-26145

VIDEO-47903

Interoperability SoundStation VTX 1000

Pressing the CALL button on the SoundStation VTX 1000 conference phone when the Polycom VSX system is idle causes the Polycom VSX system to play a brief announcement tone and display full-screen local video. Continue to dial the call normally using the VTX 1000 phone’s keypad.

When a SoundStation VTX 1000 connected to a Polycom VSX system calls another SoundStation VTX 1000 connected to a Polycom VSX system, the analog icon is displayed in the near screen along with the VTX 1000 icon and encryption status.

When you place a H.323 call from a Polycom VSX system connected to a SoundStation VTX 1000 and then use the SoundStation VTX 1000 to add an audio call, muting the Polycom VSX system's microphones blocks the audio site from hearing audio.

When a SoundStation VTX 1000 attempts to add video when connected to a V.35 system and ISDN call speed is set to 384 kbps, the call speed is ignored and the SoundStation VTX 1000 dials 128 kbps.

On a VSX 6000 with a SoundStation VTX 1000 attached, the Call Type choice is disabled when you use the Web Director to place a call.

When the far site hangs up a call to a SoundStation VTX 1000, you also need to hang up the SoundStation VTX 1000, just like a regular phone.

Turning off the Console Mics from the SoundStation VTX 1000 menu has no effect when the phone is used with a VSX system. To disable the phone microphones in this case, disable the Enable Polycom Microphones option on the VSX system.

If an audio-only site is included in a call and then hangs up, the VTX 1000 does not receive a disconnect tone. If the call was initiated from the VTX phone pad or the audio-only site, hang up from the VTX 1000. If the call was initiated from the Polycom VSX system, hang up from either the Polycom VSX system or the VTX 1000.

A call with VSX 6000, SoundStation VTX 1000, and Dial IP placed from the SoundStation VTX 1000 keypad has no far video.

In audio calls between SoundStation VTX 1000 conference phones with a Polycom Vortex® mixer connected, the option to add a video call is not available on the VTX 1000 phone.

VIDEO-25875 Interoperability

Switches

Some ISDN switches will add the area code to numbers when calling from the Recent Calls list (especially if you dial a number that had dialed into the system previously). In such cases, the call will not connect. The system will have to be set to dial local numbers without an area code.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-74493

VIDEO-74491

VIDEO-25490, VIDEO-25777, VIDEO-25732,

VIIDEO-25739

VIDEO-36383

VIDEO-37527

VIDEO-39274

VIDEO-43039

VIDEO-56212

VIDEO-65198

VIDEO-65484

Interoperability TANDBERG

In 768 kbps and higher calls with the Tandbarg 6000 MXP running F8.0 software, Polycom VSX 8000 and Polycom VSX 7000 display video that appears stretched horizontally with black borders appear on the top and bottom of the screen (also known as “letterbox video”). Video transmitted from the VSX system looks enlarged and appears jittery.

In H.323 and H.320 calls with the Tandberg 6000 B, content sent by the VSX system appears to be corrupted.

You may see the following issues in H.239 calls between V Series systems and VSX systems and TANDBERG E series systems. TANDBERG MXP systems handle these issues correctly.

• TANDBERG E series systems do not receive H.264 video sent by V Series systems and VSX systems.

• With encryption enabled, the TANDBERG 880 displays tiling on its content monitor when a PAL V Series system or VSX system sends content to it.

The VSX 8000 does not maintain 60 frames per second when sending content to the TANDBERG 6000 MXP in 1920 kbps H.323 calls.

SIP calls placed from Polycom VSX systems to TANDBERG MXP 4.0 systems at 128 kbps may experience audio and video problems. Calls to TANDBERG MXP 4.1 systems do not experience these issues.

In calls with the TANDBERG 880E ver 5.0 that use H.239, Polycom VSX systems may transmit H.263 video rather than H.264.

Polycom VSX systems are unable to connect to the TANDBERG 6000 MXP F3.2 system in SIP calls.

Polycom MGC voice-switched conferences with TANDBERG and Polycom VSX systems may end up in secondary (audio-only) mode when one site sends content. To work around this, set up the conference as continuous presence (transcoding).

Polycom VSX systems using the TANDBERG Management Suite (TMS) cannot establish multipoint calls. In the TMS, the Max Number of Video Calls setting is uneditable and is set to 1 by default.

When using the internal multipoint capabilities of the VSX 8000 to connect multiple systems in a SIP call, video freeze may occur on the Tandberg 6000 MXP system.

TA NDBERG and Polycom products use dif ferent techniques to generate the AES checksum shown on the Call Statistics screen. As a result, these numbers will not agree in calls between Tandberg and Polycom systems..

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-74427

Interoperability TANDBERG

VIDEO-74570

VIDEO-80337

VIDEO-71231 Interoperability:

Telanetix

VIDEO-56723

Interoperability VCON

VIDEO-56724

VIDEO-25764

Interoperability ViewStation

VIDEO-25788 VIDEO-25853

VIDEO-30092

VIDEO-47646

VIDEO-61763

Tandberg 1700 MXP and and Edge 95 running version 8.0 software do not transmit video to Polycom VSX systems.

The Polycom VSX system experiences garbled audio for the first few minutes of an H.320 multipoint call hosted by TANDBERG Edge95 MCU. Typically, this problem resolves after a few minutes.

When a VSX 8000 system hosts an encrypted multipoint ISDN call through a Tandberg G.32 gateway, the VSX 8000 system may crash after the call connects.

Telanetix video systems do not receive audio in G .722.1 Annex C calls with Polycom VSX 7000 systems.

When a Polycom VSX system has stereo enabled (System >

Admin Settings > Audio > Audio Settings > Enable Polycom StereoSurround) and is in a call with a VCON HD

3000 version 0270.M03.D29.H18, the Polycom VSX system may not receive audio. The workaround is to disable stereo on the Polycom VSX system.

When a VSX 7000 has H.239 enabled (System > Admin Settings > Network > Call Preference) and is in a call with a VCON HD 3000 version 0270.M03.D29.H18, the VSX 7000 may not receive video from the VCON HD 3000.

When sending content from V Series or VSX systems to a Polycom ViewS tation® SP128 system, content may go beyond the edges of the ViewStation monitor.

In calls with ViewStation SP128 systems, Far End Camera Control might not work for the first 3 minutes or so.

In multipoint calls with V Series systems or VSX systems running 8.0 and hosting the multipoint call, when a ViewStation 512 is added as a site, the ViewStation may get distorted content from the V Series system or VSX system.

When a V Series system or VSX system is sending content to a ViewStation FX, the ViewStation FX should not take a snapshot. Instead, the V Series system or VSX system should first stop sending content before the ViewStation FX sends a snapshot.

Placing a call from ViewStation FX system running version

6.0.5.15 to a VSX 6000A, VSX 3000, or VSX 7000e system

fails to connect using H.323 (IP) if registered to the PathNavigator with encryption enabled. Both systems report "\ disconnected". A workaround is to disable encryption.

When a VSX 8000 hosts a multipoint call and calls multiple sites including a Polycom HDX system and a ViewStation FX system, the Polycom HDX system makes a loud noise when the ViewStation FX attempts to connect to the VSX8000, and the ViewStation FX cannot be connected to the call successfully.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-25499 Localization While Softupdate is running, the message “Your system is in

the process of being updated.” shown on the Polycom system is always in English, even on international systems.

VIDEO-60491 Monitors

Pressing the Graphics button on the remote control while using the Westinghouse LCD HD 19” monitor may turn off the monitor.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-73960 VIDEO-30054

VIDEO-52355 VIDEO-25503

VIDEO-25496

VIDEO-25796

VIDEO-57103

VIDEO-47148

VIDEO-65130

Multipoint When a 64 MB Polycom VSX system hosts a 4-way multipoint

call, the system may reboot or crash. On a Polycom VSX system in a multipoint chair control call, all

far site systems see frozen video if you disconnect the site that is the broadcaster. To restore video, select one of the remaining sites as the broadcaster.

Users in multipoint ISDN calls that include systems using different software versions may see video instead of content.

When a conference has a meeting password set and another system dials in, the video from the system dialing in can be viewed by the conference sites even before it enters the password. The conference video and audio is not available at the system dialing in until it actually joins the conference.

Only a VSX 8000 system that can host a multipoint call supports H.264 in multipoint calls, and it is limited to 3 video + 1 local conference site. If the conference size increases, the protocol negotiated is H.263. Once it drops back to a 4-way call or lower, H.264 is not re-negotiated.

Discussion mode is turned off in cascaded calls hosted by the VSX system.

Things to note about multipoint calling:

• Dual Monitor Emulation is disabled in multipoint calls on the VSX 3000, VSX 7000, VSX 7000s, and VSX 7000e, which support Polycom StereoSurround™ or AES Encryption, but not both. If AES Encryption is enabled, the system automatically turns off StereoSurround.

• In multipoint calls on VSX 8000 systems, only one of the following features is supported: Dual Monitor Emulation, StereoSurround, or AES Encryption. If more than one of these are enabled, the system turns off all but one. The system gives highest priority to AES Encryption. Otherwise, the system gives higher priority to Dual Monitor Emulation, and turns off StereoSurround.

• In VSX 8000 multipoint calls with three or more far sites, Dual Monitor Emulation, StereoSurround, and AES Encryption are not supported.

When using a VSX 7000e to host a multipoint call, if you select a lower speed in the middle of the call, a momentary extraneous noise may occur on the VSX 7000e.

In a four-way multipoint call with discussion mode and with the VSX 8000 hosting the multipoint call, continuous presence may not be shown on Monitor 1. Instead, voice-activated switching may occur, moving active far sites to Monitor 1 and/or Monitor

When a meeting password is set, the user of a system dialing into the conference is prompted to authenticate the system by manually entering the meeting password.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-69903

VIDEO-69901

VIDEO-69906

VIDEO-70785

VIDEO-71132

VIDEO-69202

Multipoint When the Polycom VSX 8000 hosts a multipoint conference at

its maximum capacity (six sites) and an additional call is attempted, the Polycom VSX 8000 does not connect the new call. However, the error message erroneously mentions a lack of support for the requested channel type.

When the Polycom VSX 8000 hosts a multipoint call and shares content, the Content Statistics screen (press Help on the remote control during a call, then Next > Next) on the Polycom VSX 8000 shows the Content Format statistic for itself alone. The content statistics for the other systems in the conference are not displayed.

In a multipoint call that is placed at a call speed that is not a multiple of 56 kbps and that has Auto Answer Multipoint set to Y es, calls can only downspeed to call speeds that are multiples of 64. Otherwise, the incoming call is rejected.

When a VSX system hosts a multipoint call where one or more far sites are connected via ISDN at 1920 kbps, when an additional far site is added to the call via H.323, that site is not visible on the monitor of the VSX series host system. This problem results from downspeeding in mixed ISDN and H.323 calls. A workaround is to initiate the ISDN calls at a lower call speed, such as 512 kbps.

In a multipoint ISDN call where one site sends content to the other sites, the Call Statistics screen (System > Diagnostics > Call Statistics > Next) erroneously indicates both a Transmit and Receive stream for each site.

In a four-way multipoint call with discussion mode and with the VSX 8000 hosting the multipoint call, the VSX 8000 system name rather than the active speaker’s name is displayed on the systems not hosting the call.

VIDEO-54170 VIDEO-57526

VIDEO-26008, VIDEO-26254

Network When H.323 sites are registered to different gatekeepers (such

as the PathNavigator and RADVISION) and are connected via an H.320 gateway (such as the Polycom MGC), the call may not connect. A workaround is to use the DTMF dialpad to enter the extension.

When a system behind a non-H.323 compatible NAT makes a call to an site outside the NAT, the far site is unable to control the camera of the system behind the NAT.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-54200

VIDEO-80339

VIDEO-25773

VIDEO-26178

VIDEO-57252 VIDEO-55819

People+Content Due to variations between computer resolutions, the Horizontal

Position, Vertical Position, and Phase settings for VGA input are not retained when restarting a Polycom VSX system that is connected to the Polycom VSX Visual Concert™.

In a point-to-point SIP call on a system configured for Visual Concert VGA output,sending content using the Visual Concert causes the far-site video to be poor.

Polycom VSX systems treat content audio sources as mono, even if the system is configured for stereo.

You may experience problems sending a content source using Web Director if the system is already sending content selected with the remote control.

When viewing content on the Polycom VSX system, some anomalies may be perceived. The way Polycom has chosen to display the image is to show the content building on the screen. This means that the first image seen does not have full content resolution and the viewer will see it build to full resolution. This build time is dependent on the bandwidth of the call and the content sharing bandwidth allocation setting located at System

> Admin Settings > Monitors > Graphics VGA: Quality Preference.

When a call is active, the local view is the same as the far site, both in resolution and frame rate. All sites will then see the same image at about the same time and the same resolution, making it easier to discuss the image as the local parties see the same image as the far site.

When viewing the content locally, the image will build and display in the same way as when a call is active.

When using a system with a Polycom VSX Visual Concert connected, the image at the Polycom VSX Visual Concert output will not show as many anomalies as when connected to the output at the Polycom VSX system.

Under packet loss above 5%, the VSX system may take an extended period of time to display content.

It is not possible to send two different H.264 streams simultaneously.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

People+Content IP If you use People+Content IP with the Windows firewall

VIDEO-43054

VIDEO-36435

VIDEO-57355

VIDEO-56481

VIDEO-71264

VIDEO-71263

VIDEO-73714

VIDEO-73713

enabled, be sure to configure the firewall to allow the application to proceed. If you continue to have problems, disable the Microsoft firewall when using People+Content IP .

On some computers, video clips running in Windows Media Player cannot sent to Polycom VSX using People+Content IP. To work around this issue, configure Windows Media so that it does not use overlays: In Windows Media Player, select Tools > Options > Performance > Advanced. Uncheck “Use overlays”.

People+Content IP works in Security Mode, but the link between the computer and the Polycom VSX system is not encrypted/secure.

When using People+Content IP to send content from one VSX system to another VSX system during a 768 kbps video call, there may be a delay of 2-3 seconds between the time when the content is displayed on the PPCIP source (for example, the PC) and when the content is displayed on the VSX systems.

Changing screen resolutions while sending content with People+Content IP may result in displayed content that is not rescaled correctly. A workaround is to stop sending content before changing screen resolutions.

When using People+Content IP version 1.2 in an H.323 point-to-point call with Polycom VSX systems, you cannot use the remote control to send PPCIP content. A workaround is to use PPCIP version 1.1 instead or to send content using PPCIP version 1.2 using the PPCIP application instead of the remote control.

In a multipoint ISDN call, if one site sends content using People+Content IP and then stops sending the content, if a different site then attempts to send content using the Polycom VSX Visual Concert, the content is not sent. However, the site attempting to send the content can view the content locally. A workaround is to hang up and reconnect the call and to have the site send content using the Polycom VSX Visual Concert before any sites send content using PPCIP.

When using PPCIP to share content in a multipoint call, the main camera’s video is not restored when you stop sending content by pressing the PPCIP Stop button. To work around this problem, stop sending content by pressing the Graphics button on the Polycom VSX system’s remote control instead.

When you use PPCIP version 1.2.1.455 to send content and then stop sending content, the video transmit rate does not recover to 720K.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

Pro-Motion H.264 Pro-Motion H.264 is supported only in point-to-point calls

VIDEO-44507 Product Activation At www.polycom.com/support/login, use uppercase characters

VIDEO-43046 Profiles Profiles provide a limited backup capability but do not save the

Security When you set the Web Access Port on the system’s web

VIDEO-25968, VIDEO-26224

between VSX 8000 systems up to 1.4 Mbps. Pro-Motion H.264 video turns off in the following situations:

• Setting the camera to Sharpness instead of Motion prevents sending Pro-Motion H.264 video.

• Streaming prevents sending Pro-Motion H.264 video.

• Content sharing turns off Pro-Motion H.264 in both

directions until content is stopped.

• Multipoint calling turns off Pro-Motion H.264 in all directions for the duration of the call.

for any letters in the serial numbers or licenses.

entire configuration of a system. Refer to the Administrator’s Guide for more information.

interface Security page, specify a port number of 1025 or greater, and make sure that the port is not already in use.

In an encrypted H.320 call, adding a voice over ISDN call causes the Polycom VSX system to show that the call is not encrypted. This indication represents that the voice call is not encrypted; encryption remains in use on the H.320 video call.

The Russian version of the software does not include certain security features. Security Mode and AES Encryption have been removed from the Russian user interface and documentation for this release.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-71358

VIDEO-44517

VIDEO-36133 VIDEO-36449

Security Mode Points to note about Security Mode:

• SNMP access is not available in Security Mode.

• Global Management System, ReadiManager SE200, and

Polycom CMA systems cannot monitor Polycom VSX systems in Security Mode.

• If Security Mode is enabled, you must enter the room password to reset the system (System > Diagnostics > Reset System). If you forget the room password while the system is in Security Mode, contact your Polycom distributor or Polycom Technical Support.

• The web interface allows only HTTPS connections using TLS when Security Mode is enabled. Make sure that your web browser has TLS capabilities enabled.

Do not load a profile taken from a Polycom VSX system in Security Mode onto a system that is not in Security Mode. Similarly, do not load a profile t aken from a system that was not in Security Mode on a system that is in Security Mode.

Polycom VSX systems with Security Mode enabled cannot be added to a Global Management System server.

While in Security Mode, your browser may display warning messages stating that the security certificate for the web site “Polycom” cannot be verified. Click “Yes, I want to accept the certificate” to continue normal operation.

To help ensure the security of the system, Polycom VSX systems require that you provide new passwords when switching into Security Mode. Enter a new password when prompted by the system.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

Single-Monitor VGA

Single-monitor VGA has the following limitations:

• Only the steel gray color scheme is supported.

• The system switches from dual monitor emulation to

full-screen mode when sending or receiving content.

• On systems other than a VSX 8000, the H.264 maximum call speed is reduced to 512 kbps if stereo audio is enabled with a VGA main monitor.

• On VSX 5000, VSX 7000s, and VSX 7000e systems configured for single-monitor VGA:

Dual Monitor Emulation is disabled in multipoint calls. The system can support AES Encryption or StereoSurround, but not both. If AES Encryption is enabled, the system automatically turns off StereoSurround.

In point-to-point calls, only one of the following features is supported: Dual Monitor Emulation, StereoSurround, or AES Encryption. If you have more than one of these enabled, the system turns off all but one. The system gives highest priority to AES Encryption, if it is enabled. If AES Encryption is not enabled, the system gives higher priority to Dual Monitor Emulation, and turns off StereoSurround.

Dual Monitor Emulation is automatically disabled at call rates greater than 512 kbps.

• On VSX 8000 systems configured for single-monitor VGA: In multipoint calls, only one of the following features is

supported: Dual Monitor Emulation, StereoSurround, or AES Encryption. If you have more than one of these enabled, the system turns off all but one. The system gives highest priority to AES Encryption, if it is enabled. If AES Encryption is not enabled, the system gives higher priority to Dual Monitor Emulation, and turns off StereoSurround.

In VSX 8000 multipoint calls with three or more far sites, Dual Monitor Emulation, StereoSurround, and AES Encryption are not supported.

Dual Monitor Emulation is automatically disabled at call rates greater than 1 Mbps.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-25722

VIDEO-25498

VIDEO-25497

VIDEO-25491

VIDEO-25754 VIDEO-25735

VIDEO-25826

VIDEO-25867

VIDEO-25868

VIDEO-25690

VIDEO-56721

VIDEO-44521

VIDEO-56063

VIDEO-56709

VIDEO-65199

SIP V Series systems and VSX systems do not support firewall or

NAT traversal in SIP calls. The Polycom MGC does not support Far End Camera Control

in a SIP conference. The Polycom MGC does not support content sharing in a SIP

conference. When Transport Protocol on the SIP Settings screen is set to

Both (TCP and UDP), the roll-over may cause a delay. H.264 SIP calls do not support content sharing. SIP transfers always report back successful, even if they fail to

transfer successfully. When a system is registered to Global Directory Server/Global

Address Book and SIP is enabled instead of H.323, a non-ISDN system may show an incorrect alert message for Global Directory Server/Global Address Book registration.

In 64 kbps SIP calls between a VSX system and Windows Messenger, Windows Messenger may not receive video.

When packet loss occurs, SIP calls may hang up automatically . Do not transfer either end of a SIP call that is connected to a

Polycom VSX system. In a multipoint call with an H.320 site and a SIP site, the call

fails if the Polycom VSX system is hosting the multipoint call and calls the H.320 site first.

This release does not support dialing SIP calls using a DNS name, such as VSX.austin.polycom.com. Other address forms, such as email (for example, any@host.austin.polycom.com) work.

When SIP is enabled (System > Admin Settings > Network > Call Preference), V Series systems and VSX systems are unable to register to the Global Directory Server.

The following features are not available when the SIP protocol is in use:

• Polycom Video and Audio Error Concealment

• Encryption

• People and Content (H.239 and Polycom People+Content)

• H.263 Pro-Motion

When a password is set on an bridge, a SIP site that dials into the bridge is not prompted for the meeting password and cannot join the call.

When using the internal multipoint capabilities of the VSX 8000 system to connect multiple systems in a SIP call, if a call is placed to the VSX 8000 system after the VSX 8000 system already placed outgoing calls to other systems, the incoming call connects briefly and then disconnects completely.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-65198

VIDEO-65204

VIDEO-69905

VIDEO-71283

VIDEO-71284

VIDEO-71282

VIDEO-71280

VIDEO-71265

SIP When using the internal multipoint capabilities of the VSX 8000

system to connect multiple systems in a SIP call, video freeze may occur on some of the systems.

In a mixed H.320 and SIP multipoint call that uses the internal multipoint capabilities of the Polycom HDX 9001™ system, video sent from the H.320 VSX systems may have problems if the H.320 sites are dialed first. A workaround is to dial the SIP sites before dialing the H.320 sites.

When a Polycom VSX system joins a multipoint call using SIP, the Polycom VSX system should receive a prompt to enter the meeting password. However, this prompt does not appear. Also, the resulting call connection may be ended automatically.

When a V .35 Polycom VSX system hosts a mixed V.35 and SIP multipoint call, any other V .35 Polycom VSX systems in the call are unable to use FECC to control the camera of the host system when the host system is configured as the active speaker. However, any SIP sites in the call can control the host system’s camera using FECC. After the SIP sites disconnect from the call, the V.35 sites can then use FECC to control the host system’s camera using FECC.

When a Polycom VSX system hosts a mixed ISDN and SIP multipoint call, if any of the other sites in the call are configured as the active speaker, then the host system is unable to use FECC to control the camera of the ISDN or SIP sites in the call.

In a SIP call between two Polycom VSX systems, attempting to send content from one system to another using PPCIP with the H.263 video protocol fails or results in video freeze.

When Polycom VSX systems participate in a multipoint SIP call that includes a third-party system, downspeeding is not available. For example, when a Polycom VSX system places a SIP call to a third-party system at 768 kbps, if a second Polycom VSX system attempts to place a SIP call to the first Polycom VSX system at a lower call speed, the call is rejected.

When a Polycom SoundPoint® IP 601 or Polycom SoundStation® IP 4000 SIP phone places a SIP call to a Polycom VSX system after Stereo is already enabled on the Polycom VSX system, the SIP phone does not receive audio but the Polycom VSX system does receive audio.

VIDEO-26119 Snapshots V Series systems or VSX systems do not support receiving

H.261 Annex D snapshots.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-25747 VIDEO-25724

SNMP Current SNMP implementation is only used for alerts and does

not support any remote management. By default, SNMP consoles return trap numbers. To get the

equivalent trap messages in text, the polycom.mib file must be downloaded from the SNMP page of the system’s web interface (Admin Settings > Global Services > SNMP).

VIDEO-54118 Softupdate VSX 3000A and 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. The complete upgrade should take no longer than 2-3 minutes, and after the upgrade is complete, the system will restart automatically.

VIDEO-74170

If your Polycom VSX system is registered to both a Polycom CMA 5000 and other global directory servers when you update to version 9.0.5.1, you must unregister from Polycom CMA 5000 before you can unregister from the global directory servers. You can then register to the Polycom CMA 5000 again.

VIDEO-36845

Polycom support at www.polycom.com/support/login currently does not support logging in via Softupdate. This means that the command-line switches -ku, -kp and the “No I need to get a

key” options won’t work. VIDEO-36663 VIDEO-54674

System settings must not be saved during a downgrade when

installing a system software version earlier than 8.5.

Unchecking the retain system checkboxes in Softupdate while

downgrading to version 8.5 may cause the V Series system or

VSX system to become unusable. VIDEO-55923

Launching the Softupdate executables for version 8.7 or later

may prompt Windows to display an Open File - Security

Warning dialog box that indicates an unknown publisher. The

workaround is to select Run and to proceed with the

Softupdate installation. VIDEO-25773,

VIDEO-30185

StereoSurround The Polycom VSX Visual Concert does not support stereo

audio - a stereo input is converted to mono.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-54143

VIDEO-54037

VIDEO-25876

VIDEO-25725

VIDEO-25775

VIDEO-53652

VIDEO-30135

VIDEO-30129

VIDEO-56849

VIDEO-56852

User Interface When a network cable is unplugged and reconnected, the

Polycom VSX system may require 1 to 20 minutes to reconnect

to the Directory Server. A workaround is to recheck Register

on the Global Directory Servers screen (System > Admin

Settings > Global Services > Directory Servers) to manually

reconnect to the Directory Server.

When the V700 is in a call with another Polycom VSX system,

the Polycom VSX system does not display a message

indicating that far-site camera control is unavailable on the

V700 when you press Far on the Polycom VSX remote control.

During the out-of-box setup, if you select SIP instead of H.323,

the system will restart before configuration is complete. After

the restart, the system will return to the LAN Properties page,

allowing you to complete system configuration.

A VSX 8000 system set up for single-monitor VGA displays a

black border around the user interface screens.

If you set Line Input to Audio Mixer and check Enable

Polycom StereoSurround, a message is displayed that

Polycom microphones will be disabled. The microphones are

actually disabled in this case, even though the System Status

screen shows them as active.

The monitor configuration options changed in software version

8.5 to include additional fields and add more flexibility for

output configurations. If you update software from a version

earlier than 8.5, you may need to reconfigure the monitor

settings.

Incoming POTS calls are not recorded in the Recent Calls list.

Outgoing POTS calls are listed correctly.

Systems that are configured to use a UPnP NAT and are

registered with a gatekeeper do not display the E.164

extension on the Place a Call screen.

When using the system’s web interface to access the

VSX 8000, disabling the Allow Access to User Settings field

(Admin Settings > General Settings > Security) and

selecting Update does not automatically remove User Settings

from the System page (System) in the system’s local interface

when the System page is already visible. A workaround is to

navigate away from the System page in the system’s local

interface and then to return to it.

After you register a Polycom VSX system to a Global Directory

Server (GDS) and/or verify that the Register checkbox is

enabled (Admin Settings > Global Services > Directory

Servers), if you change the GDS that the Polycom VSX system

is registered to, the Register checkmark disappears and you

must re-enter it.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-57143

VIDEO-57723

VIDEO-60986, VIDEO-61173

VIDEO-61761

VIDEO-62493, VIDEO-62496

VIDEO-65187

VIDEO-69902

User Interface If you register a Polycom VSX system to the Global Directory

Server (System > Admin Settings > Global Services >

Directory Servers) but do not enter an area code for the ISDN

number associated with a Polycom VSX system (System >

Admin Settings > Network > ISDN), the GDS may not show

the ISDN number for the associated system. Also,

point-to-point and multipoint calls may not be able to be placed

to or from the Polycom VSX system via the directory entry. A

workaround is to enter the area code for the ISDN number of

the Polycom VSX system, unregister, and then re-register the

system to the GDS server, and refresh the entry for the

associated system in the GDS.

The H.239 setting (System > Admin Settings > Network >

Call Preference) is now enabled by default and may cause

problems with content sharing on legacy systems. A

workaround is to disable the H.239 setting.

The Dialing Rules button label on the Global Services page

(System > Admin Settings > Global Services) has been

removed, and the configuration items associated with it

(Always Dial Area Code, and Dial 1+ for all USA calls) have

been moved to the Location page (System > Admin Settings

> General Settings > Location).

When updating software over ISDN (System > Utilities >

Software Update) on a VSX system with an ISDN Quad BRI

module, not plugging in all four lines before initiating the ISDN

software update causes the software update to freeze before

completion.

ISDN software update is not available on V Series systems.

The Sony PTZ setting is renamed as the Camera PTZ setting

in Polycom VSX software version 9.0.1 and later.

If a VSX system receives an H.320 call after you initiate the

software update over ISDN (System > Utilities > Software

Update), the ISDN software update is disrupted and the

system crashes.

When a Polycom VSX system sends or receives content during

a call, the Call Statistics screen (System > Diagnostics > Call

Statistics > Next) fails to show information about the used

content rate.

VIDEO-74487

If a Polycom VSX hosts a multipoint call when it is configured to

require a meeting password and auto-answer multipoint calls,

the system does not prompt to accept an incoming call from a

Polycom PVX or Polycom CMA Desktop system. Because of

this, these systems cannot join the multipoint call.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-25731

VIDEO-25965 VIDEO-26222

VIDEO-25730

VIDEO-68719

VIDEO-55709, VIDEO-57109 VIDEO-57519 VIDEO-57522

VIDEO-57108

V.35 In H.320 calls from a V.35 VSX system with encryption

enabled, the far-site system does not recover from a

momentary loss of data.

V.35 profiles are not localized. They appear in English.

When you place a V .35 Direct Connect call from a VSX 7000 to

a ViewStation EX running release 6.0.1 software, the call may

not connect. When the call fails to connect, the Polycom VSX

system's user interface displays the dialing screen and the

ViewStation EX system's user interface does not appear to be

receiving a call. Disconnecting the call and reconnecting

should clear the problem.

Video VSX systems send video in low frame rates when using a

camera set to Sharpness.

When the VSX 3000, VSX 3000A, or VSX 5000 system has

Backlight Compensation (System > Admin Settings >

Cameras) disabled and is set to a Power Frequency of 50 Hz,

selecting different Camera Brightness settings does not

change the brightness level on the system.

Video Overlay The monitor image is not rescaled to add the video overlay

border. Instead, the video overlay is displayed on top of the

monitor image. Due to this configuration, portions of video or

content might be obscured. Adjusting the TV or monitor display

settings may help to correct this problem.

Depending upon the type of monitor that the system uses, the

drop shadow on the video overlay may partially obscure

various sides of the overlay and create an unbalanced overlay

appearance.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-54194

VIDEO-54041

VIDEO-25812

VIDEO-25830 VIDEO-30134

VIDEO-46556 VIDEO-55660

VIDEO-56825

VIDEO-25871

VIDEO-43492

VIDEO-37827 VIDEO-45170

VIDEO-69902

Web Interface When updating the Call Profiles (Admin Settings > Network >

V.35/RS-449/RS-530) in the system’s web interface, you must

select Update twice before any updates will occur.

The third Polycom VSX system to dial into a call via the

system’s web interface is not prompted to enter the meeting

password and is dropped from the call.

Web Director on VSX Web does not give the remote

administrator any way to start or stop Polycom People+Content

IP.

The system’s web interface does not give access to the

following utilities: Calendar and Call Scheduler.

The system’s web interface Call Summary page (Diagnostics

> System Status > Call Summary) does not include a Serial

Calls section listing V.35 calls. The calls are included in the

total call number. To see a listing of V.35 calls, refer to the

system user interface.

Using the system interface and the system’s web interface

simultaneously when answering calls could cause problems.

When you load a saved profile for a different Global Directory

Server, the system does not automatically register with the

Global Directory Server even though registration appears

successful. The workaround is to recheck Register on the

Global Directory Servers screen (Admin Settings > Global

Services > Directory Servers) to manually connect to the

Directory Server.

When accessing and saving the Call Detail Report through the

system’s web interface (Utilities > Call Detail Report) of a PC

that does not have Microsoft Word installed on it, extraneous

text will appear at the top of the Call Detail Report.

If time server settings are changed from the system’s web

interface during a call, the system may try to disconnect the

call.

If you use the system’s web interface shortly before installing

version 8.5, the system’s web interface will be temporarily

unusable after the upgrade. A workaround is to clear your

browser's cache or wait an hour so the system will

automatically clear the obsolete pages from the earlier

Polycom VSX version.

When Security Mode is enabled, the remote control in the

system’s web interface is disabled.

When you search for a directory entry in the system’s web

interface, the entry is highlighted but its information is not

displayed. This only happens if you used search to find the

entry.

When a Polycom VSX system sends or receives content during

a call, the Call Statistics screen (Diagnostics > Call Statistics)

fails to show information about the used content rate.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-36609

VIDEO-56336

VIDEO-56311

VIDEO-25768 VIDEO-56849

VIDEO-59208

VIDEO-60836

VIDEO-60837

Web Interface To ensure the security of the system, Polycom VSX systems

require that you provide a new password when entering

Security Mode. If you configure Security Mode via the system’s

web interface, your browser’s pop-up blocker may prevent you

from receiving the dialog box used to update the password and

enter Security Mode. To work around this issue, disable your

pop-up blocker before starting the password change, or

temporarily bypass it by holding down the CTRL key while

pressing OK to the “Any changes made to this setting will

cause your system to restart” message.

When exporting a directory (Utilities > Import/Export

Directory) from the system through the Web UI, Microsoft

Internet Explorer may block the File Download dialog box. A

workaround is to press and hold the Ctrl key, click the Export

button, and wait for the File Download dialog box to appear.

Selecting Update in the V.35 Call Profiles field (Admin

Settings > Network) prompts an error message. A

workaround is to select Update again to update the field.

The Recent Calls page is not translated, so date and other

information appears in English.

When using the system’s web interface to access the

VSX 8000, disabling the Allow Access to User Settings field

(Admin Settings > General Settings > Security) and

selecting Update does not automatically remove User Settings

from the System page (System) in the system’s local interface

when the System page is already visible. A workaround is to

navigate away from the System page in the system’s local

interface and then to return to it.

When enabled, the Call Detail Report (CDR) provides the

system's call history, and you can view the CDR from the

system’s web interface. However, the CDR is not available

immediately. Instead, within 5 minutes of the end of the call, the

CDR is written to memory and you can then download the data

in CSV format for sorting and formatting.

If you use a PC with Windows Vista installed to access the

Directory Servers page (Admin Settings > Glob al Serv ices >

Directory Servers) of the system’s web interface, entering an

address for a GDS, selecting Register, and clicking Update do

not update the GDS information on 128 MB systems (V700,

VSX 3000A, VSX 5000, VSX 6000A, VSX 7000s, VSX 7000e,

and VSX 8000).

If you use a PC with Windows Vista installed to access the

Sites page (Admin Settings > General Settings > Sites) of

the system’s web interface, you receive a message saying that

the page uses Java. After the page attempts to load the

Directory information, you receive an error message saying

that the Directory download occurred with errors. This occurs

on 128 MB systems (V700, VSX 3000A, VSX 5000,

VSX 6000A, VSX 7000s, VSX 7000e, and VSX 8000). A

workaround is to install Java run-time on the PC.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Jira ID Feature Limitation

VIDEO-60990

VIDEO-57900

VIDEO-62682

VIDEO-65212

VIDEO-65195

VIDEO-65202

VIDEO-67779, VIDEO-69872

VIDEO-69900

Web Interface On the VSX 3000 and V700, the Cameras page (Admin

Settings > Cameras) of the system’s web interface does not

display the Camera 1 field and icon.

When you attempt to export a directory from the V Series and

Polycom VSX

systems to a PC through the system’s web interface (Utilities > Import/Export Directory, then VSX —> PC), the system may report a successful export while actually exporting an empty file. A workaround is to upgrade from Microsoft Java Virtual Machine (JVM) to Sun JVM.

The VSX 7000e and VSX 8000 may be unable to answer incoming POTS calls from the system’s web interface regardless of whether Auto Answer Point-to-Point Video (Admin Settings > General Settings > System Settings > Call Settings) is set to Yes or No.

When you attempt to import a profile from PC to the V Series or Polycom VSX

system through the system’s web interface (Utilities > Profile Center, then PC —> VSX), the system will only restore settings that had been changed from default when the profile was saved originally (VSX —> PC). Thus, profiles should only be applied to systems with recently erased system flash memory.

After you view various pages in the system’s web interface, if you click the Back button in Microsoft Internet Explorer, you exit the system’s web interface.

When you attempt to import a directory from a PC to the Polycom V Series or VSX

system through the system’s web interface (Utilities > Import/Export Directory, then PC —> VSX), content in the body section of the Import/Export Directory page is missing after the import completes. A workaround is to click the Refresh button in Microsoft Internet Explorer.

The Import/Export Directory screen (Utilities > Import/Export Directory) in the system’s web interface does not display the directory table until after the .csv file is downloaded.

If you enter the address for a global directory server through the system’s web interface (Admin Settings > Global Services > Directory Servers), check Save Global Directory to System, click the Update button, navigate to the Directory screen to add a few new local sites, return to the Directory Servers screen, change the current global directory server, click Update, return to the Directory screen, and change the group to Local, the new local sites are no longer displayed in the system’s web interface. However , these sites are displayed in the system’s local interface.

VIDEO-25721 Web Streaming Web streaming does not work with RealPlayer.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Interoperability

The following PTZ cameras are supported for use with VSX systems:

• Polycom PowerCam

• Polycom PowerCam Plus (VSX 7000e, VSX 8000)

• Sony BRC-300, EVI-D30, EVI-D70, or EVI-D100 (for NTSC systems)

• Sony EVI-D31 or EVI-D100P (for PAL systems)

Polycom V Series and VSX 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 9.0 release.

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.

Type Product Version

NAT/Firewall Cisco PIX 506E Cisco PIX 604 IOS 6.3(5), 6.3(3)

Cisco PIX 515 7.2.1 Cisco Router (QoS and NAT) Cisco 3640 IOS 12.4(13), Cisco 3745 12.3(14) D-Link DI-604 3.51 Linksys BEFSR41 1.04.17 Linksys BEFVP41 1.01.04 3/08/2005 NETGEAR FR114P FR114P V1.5_14 NETGEAR RP614 RP614v4 Polycom VBP 4350 7.2.2 Polycom VBP 5300 7.2.2

Release Notes V Series and VSX Systems, Version 9.0.6.1

Type Product Version

Gatekeeper, Gateways

Management Systems

Avaya Communication Manager 4.0 Cisco gatekeeper 12.2(8r)T2 FC1, Cisco 2621 MCM 12.3(20),Cisco

3745 12.4 Codian MCU 3.0 Global Management System 7.1.1.107, 7.1.0.004 PathNavigator 7.00.05, 7.00.03, 7.00.11 Polycom CMA 5000 4.0.1/4.01.00 Polycom MGC 25 gateway MCU 8.0.0.27, 9.0, 9.0.1.52; MCMS 8.0.0.128,

9.0.1.8 Polycom RMX 1.1.0.103, 1.1.1, 2.0.0.56, 2.0.2.25 Polycom RMX 2000 4.0.1.29 Polycom ReadiManager SE200 1.0.1, 2.0, 3.0, 3.00.08 RADVISION ECS gatekeeper 4.1.0.0, 5.6.2.4 RADVISION viaIP gateway 5.00.0.22 TANDBERG gatekeeper N6.1 TA N D BER G ga te w a y G3.2, 3.2 Polycom Global Management System 7.1.003, 7.1.8.001 Polycom RSS 1.1.0.001, 2.0, 3.0.1.742, 4.0.0.001 Polycom VCM1000 1.0-b001

External MCUs, Bridges, Call Managers

Avaya Communication Manager 4.0 Cisco CallManager 4.2 Polycom MGC 25 MCU 8.0.0.27, 9.0, 9.0.1.52; MCMS 8.0.0.128 Polycom MGC 50 MCU 8.0.0.27, 9.0, 9.0.1.52; MCMS 8.0.0.128 Polycom MGC 100 MCU 8.0.0.27, 9.0, 9.0.1.52; MCMS 8.0.0.128 RADVISION viaIP MCU 3.5.0.9 TANDBERG MPS J3.2

Sites Aethra X3 10.7.32

Aethra X7 12.1.7 Aethra Vega Star Gold 6.0.49 Aethra Vega Star 6.0.49 iPower 9000 6.2.0.1208 LifeSize Team 2.6.0 (14), 3.0

Release Notes V Series and VSX Systems, Version 9.0.6.1

Type Product Version

Sites Polycom CMA Desktop™ 4.1.0

Polycom iPower™ 6.2.0 Polycom HDX 9001 1.0.2-354, 2.0, 2.0.3.1 Polycom HDX 9002™ 1.0.2-354, 2.0, 2.0.3.1 Polycom HDX 9004™ 1.0.2-354, 2.0, 2.0.3.1, 2.5.0.2 Polycom HDX 8004™ 2.5.0.2 Polycom HDX 7001™ 2.0.3.21 Polycom HDX 4000™ 2.5.0.2 Polycom PVX™ 8.0.2.0235, 8.0.2.4 Polycom VVX™ 1500 3.1.3.0139 Polycom QDX™ 6000 3.0 Polycom DST K60 2.0.1 Polycom DST B5 2.0 Polycom VS512 7.5.4SP - 04MAR2005, 7.5.4.10 Sony PCS-1 DSP 03.23, Host 01.01, 3.42 Sony PCS-G50 2.70 Sony PCS-G70 02.42, 02.51, 2.63 Sony PCS-XG80 2.0.3 TANDBERG MXP 150 L5.1 TANDBERG 880 E E5.3 NTSC TANDBERG 880 F MXP F6.0 NTSC, F6.1 TANDBERG MXP 1700 F8.0 TANDBERG MXP 6000 F8.0 TANDBERG 6000 B B10.3 NTSC, B10.3 TANDBERG 6000 E E5.3 NTSC, E5.3 TANDBERG 6000 F MXP F6.0 NTSC, F6.1 TANDBERG Edge95 MXP F8.0 V500 8.5.3, 8.7, 8.7.1 V700 8.5.3, 8.7, 8.7.1 VCON HD 3000 0270.M03.D29.H18 ViewStation FX 6.0.5, 6.0.5.17, 6.0.5.22

Release Notes V Series and VSX Systems, Version 9.0.6.1

Type Product Version

Sites ViewStation SP128 7.5.4SP - 04MAR2005

ViewStation SP384 7.5.4SP - 04MAR2005 VSX 3000 8.5.3, 8.7, 8.7.1 VSX 3000A 8.5.3, 8.7, 8.7.1 VSX 5000 8.5.3, 8.7, 8.7.1 VSX 6000 8.5.3, 8.7, 8.7.1 VSX 6000A 8.5.3, 8.7, 8.7.1 VSX 7000 8.5.3, 8.7, 8.7.1 VSX 7000e 8.5.3, 8.7, 8.7.1 VSX 7000s 8.5.3, 8.7, 8.7.1 VSX 8000 8.5.3, 8.7, 8.7.1

Cisco PIX Firewall

Cisco PIX “fixup protocol h323 h225 1720” on only:

H.323 video sites will have connection and video incompatibilities. Cisco currently does not support AES or H.239 in the “fixup protocol h323

h225 1720”.

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. Also, H.239 will not work properly in this configuration.

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. To avoid this, disable H.239 on all sites.

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

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.

1. To turn off the “fixup protocol h323 h225 1720” feature, use the following

2. Configure Conduits or Access List Assignments for the following ports:

• For outbound interface

command:

no fixup protocol h323 h225 1720

— 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.

If an site receives inbound video calls from outside the LAN, use the following command to create a static connection for each internal site:

static (inside,outside) xxx.xxx.xxx.xxx iii.iii.iii.iii netmask

Release Notes V Series and VSX Systems, Version 9.0.6.1

Hardware and Software Requirements

To access the system’s web interface, use Microsoft Internet Explorer 6.x or later as your web browser and make sure that you have Java 1.2 or later installed.

To take advantage of the latest features for integrating a Polycom VSX system and SoundStation VTX 1000 conference phone, the Polycom VSX system requires version 7.5 or later software and the VTX 1000 requires version 1.5 or later software.

The VSX 8000 is designed to work with the Vortex mixer. For this configuration, you need Vortex firmware 2.5.2 or later, Polycom Conference Composer™ version 2.7.0 or later, and Polycom VSX system software version

7.5 or later. Web streaming participants must have the Apple QuickTime player installed

on their PC to view the multicast stream. The following versions are required for compatibility with the Avaya

Communication Manager (ACM):

• iPower 6.0.0.315 or later

• ViewStation FX version 6.0 or later

• ViewStation version 7.0 or later

• PathNavigator version 7.00.02.0189 or later, routed mode

• Global Management System version 7.0.1.212 or later

• V Series systems and VSX systems version 8.0.3 or later

Warranty and Registration

The Polycom V Series and VSX series products include a one-year hardware warranty (30-day return upon receipt at factory) and 90-day software warranty.

Complete the one-time product registration form at www.polycom.com/support/video to access software downloads. Using the information provided as part of product registration, Polycom will make every effort to send you electronic notification of software releases as and when available.

means, electronic or mechanical, for any purpose, witho ut the express written permission of Polycom, Inc.

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.

Release Notes V Series and VSX Systems, Version 9.0.6.1

License Terms

The free distribution and use of this software in both source and binary form is allowed (with or without changes) provided that:

1. distributions of this source code include the above copyright notice, this list of

2. distributions in binary form include the above copyright notice, this list of

3. the copyright holder's name is not used to endorse products built using this

conditions and the following disclaimer;

conditions and the following disclaimer in the documentation and/or other associated materials;

software without specific written permission.

Disclaimer

This software is provided 'as is' with no explicit or implied warranties in respect of its properties, including, but not limited to, correctness and fitness for purpose.

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 property of their respective owners.

Release Notes V Series and VSX Systems, Version 9.0.6.1

Polycom V Series, VSX Series User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual