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.

+ 42 hidden pages