Polycom V500 Instruction Manual

May 2006
3725-21988-013/A
Release Notes
V500 and VSX Systems, Version 8.5
Polycom® is pleased to announce the release of version 8.5 software for the
V500™ and VSX™ systems. Polycom software release 8.5 is available as a
software update for customers with current service agreements.
To upgrade system software, use the Softupdate application. For more
information about upgrading software and enabling system options, refer to
the Upgrading Polycom Video Software document. The document and
Softupdate application are available at the Polycom Resource Center.
New Version of People+Content IP
The People+Content™IP application has been updated to version 1.1.0.7.
Version 1.1.0.7 includes the ability to use a VSX or V500 host name rather than
just an IP address, as well as improvements to maintain image quality even
when network performance is poor. You can download this new version from
the Polycom Resource Center.
Installing Version 8.5
As you install this version of V500 or VSX system software, you may notice
enhancements to Softupdate and changes in security options and passwords.
For more information, refer to the Softupdate Enhancements, Security
Enhancements, and Password Changes sections of this document.
VSX 3000A customers who are currently running version 8.0.x software may
experience flicker and unusual behavior on their displays when upgrading to
version 8.5. This is normal behavior and it is critical that the system NOT be turned
off during this process. The complete upgrade process should take no longer than
2-3 minutes, and after the upgrade is complete, the system will restart
automatically.

Release Notes
V500 and VSX systems, version 8.5
2
What’s New in This Release?
Softupdate Enhancements
Softupdate now gives you the following options when you select Custom
installation:
•Change the monitor configuration.
•Change the system’s network configuration.
•Erase the system flash memory.
Softupdate also includes new online help, which you can access by pressing
the F1 key or clicking the Help button in any dialog.
Security Enhancements
Version 8.5 provides several enhancements to make operating the system
more secure, including a new Security Mode on some systems and additional
password options. Starting with version 8.5, Softupdate uses secure FTP to
access the systems and verifies that the download has been digitally signed by
Polycom before installing it.
Security Mode
With version 8.5, you can configure VSX 3000A, VSX 5000, VSX 6000A,
VSX 7000s, VSX 7000e, and VSX 8000 systems to use Security Mode, which
provides secure access to the system. Security Mode is based on Transport
Layer Security (TLS) 1.0 using 168-bit Triple-DES. These protocols encrypt
management communication over IP, preventing access by unauthorized
users.
Every time you enable Security Mode, you must configure a new password for
the system. The password cannot be blank, and it cannot be the default value
(serial number).

Release Notes
V500 and VSX systems, version 8.5
3
Security Mode requires secure access and a password for Web, Telnet, and FTP
access.
Password Changes
Version 8.5 provides more flexibility and added protection for accessing
system Admin Settings. The admin password has been replaced by the room
password and the remote access password. You can set up a room password to
restrict access to the system locally. You can set up a remote access password
to restrict access to the system via FTP, Telnet, SNMP, or the web interface.
You can also choose to use the same password for both local room access and
remote access.
H.460 NAT Firewall Traversal
You can now configure VSX systems to use standards-based H.460.18 and
H.460.19 firewall traversal, which allows video systems to more easily
establish IP connections across firewalls.
Integration with Microsoft Live Communications Server (LCS)
Integration with Microsoft®LCS allows you to set up a list of LCS contacts on
a V500 or VSX system, see if the contacts are online, and call them without
knowing their addresses. Contacts appear in the directory and can also be
displayed on the home screen.
Out-of-box Monitor Configuration
When you power on your system for the first time, or after you erase the
system flash memory, the out-of-box setup wizard runs to let you configure
the system. Starting with version 8.5, the system displays the setup wizard on
both NTSC/PAL and VGA monitors so that you can complete the setup
Points to note about Security Mode:
•SNMP access is not available in Security Mode.
•Global Management System™ and ReadiManager™ SE200 are not compatible
with VSX systems in Security Mode.
•Software images for version 8.5 and later are digitally signed by Polycom. To
install an earlier version of system software, you must disable Security Mode.
•If Security Mode is not enabled, the system first attempts to use a secure
protocol (such as HTTPS), but reverts to the non-secure form of the protocol if
the management system does not have a secure client.
•If Security Mode is enabled, you must enter the room password to reset the
system.

Release Notes
V500 and VSX systems, version 8.5
4
regardless of the type of monitor connected. The setup wizard prompts you to
select your monitor configuration. At the end of the setup wizard, the system
restarts with the configuration you selected.
To configure a VSX 5000 or VSX 6000A for dual monitors, you must provide a
dual monitor option key.
Configurable Maximum Transmission Unit (MTU)
Different networks have different packet-handling characteristics. Some
networks can handle large packets, but some networks perform better with
small packets. If you have bad video or network errors because packets are too
large, you should decrease the MTU. If the network is burdened with
unnecessary overhead because the packets are too small, you should increase
the MTU. The default value is 1260.
Previously the MTU size was a static value that you could not change. In
version 8.5, you can configure the MTU for IP networks. This setting does not
apply to ISDN networks.
Basic Mode UI Configuration
You can now enable Basic Mode from the system’s user interface, in addition
to enabling it in the web interface.
Web Navigation
The web interface in version 8.5 is enhanced to provide easier navigation.
Maximum Number of Local Directory Entries
Systems running version 8.5 can store up to 1,000 local directory entries.
Improved Interaction with Global Directory Server
Version 8.5 includes improvements to communication and data handling
between the Global Directory Server and V500/VSX systems.
Save Global Directory to System is no longer enabled by default on the
Global Directory Servers screen (System > Admin Settings > Global
Services > Directory Servers). When Save Global Directory to System is
disabled, the system can only display up to 1,000 global directory entries. If
you enable Save Global Directory to System, the system can display up to
4,000 global directory entries by saving them to a file on your system.

Release Notes
V500 and VSX systems, version 8.5
5
You can now manually refresh the global directory on your system by clicking
the Polycom logo in the top right corner of the Directory screen and selecting
Refresh.
Improvements to Call Preferences
With version 8.5, you can allow users to place IP-to-ISDN or ISDN-to-IP calls
specifically through a gateway.
Using a Non-Polycom Remote Control
With the version 8.5 software, you can configure the system to accept input
from a programmable, non-Polycom remote without compatibility problems.
G.722.1 Annex C Audio
Version 8.5 uses the G.722.1 Annex C audio protocol for calls without stereo
enabled. Systems will still use Siren™ 14 for stereo. G.722.1 Annex C is similar
to Siren 14. You should not notice any difference except on the Call Statistics
screen. The Call Statistics screen specifies which audio protocol is being used
for the call.
Automatic Adjustment for Daylight Saving Time
You can now configure your system to automatically move the system clock
forward and back one hour for daylight saving time. The system does not need
to be connected to a time server to use this feature.
This new setting replaces the Daylight Saving Time setting, which manually
moved the system clock forward and back.
Automatic Camera Tracking with the Polycom Vortex
You can now use automatic camera tracking when you have a Vortex®mixer
connected instead of Polycom microphones.
Configurable Screen Saver Output
You can now configure whether the system sends black video or no signal to
the monitor or projector when the screen saver activates.

Release Notes
V500 and VSX systems, version 8.5
6
New API Commands
The following API commands are new in version 8.5.
addressdisplayedingab
Specifies whether to make the system address public or private in the global
directory.
addressdisplayedingab get
addressdisplayedingab private
addressdisplayedingab public
camerainput
Sets or gets the format for a video source.
camerainput {1..3} <get|s-video|composite>
configpresentation
Sets or gets the content presentation settings for Monitor 1 or Monitor 2.
configpresentation get
configpresentation <monitor1|monitor2> get
configpresentation monitor1 <near|far|content|near-or-far|
content-or-near|content-or-far|all>
configpresentation monitor2 <near|far|content|near-or-far|
content-or-near|content-or-far|all>
configpresentation monitor1 "value" monitor2 "value"
dialingentryfield
Sets or gets the configuration of the dialing entry field on the Place a Call
screen.
dialingentryfield <get|yes|no>
enablefirewalltraversal
Sets or gets the Enable NAT/Firewall Traversal setting. This feature requires
an Edgewater session border controller that supports H.460.
enablefirewalltraversal <get|on|off>
enablersvp
Sets or gets the RSVP (Resource Reservation Setup Protocol) setting on the
system, which requests that routers reserve bandwidth along an IP connection
path.
enablersvp <get|yes|no>

Release Notes
V500 and VSX systems, version 8.5
7
flash
Flashes the analog phone call, either an analog phone or a
SoundStation VTX 1000®.
flash [“callid”]
flash [“callid”] [“duration”]
h239enable
Sets or gets the H.239 People+Content setting.
h239enable get
h239enable <yes|no>
monitor1screensaverouput and monitor2screensaverouput
Sets or gets whether to send either black video or "No Signal" to Monitor 1 or
Monitor 2 when the screen saver activates.
monitor1screensaveroutput <get|black|no_signal>
monitor2screensaveroutput <get|black|no_signal>
mtumode and mtusize
Sets or gets the MTU mode. The
mtumode and mtusize commands allow you
to change the Maximum Transmission Unit (MTU) size, to adjust for the best
interoperability with the host network. Set
mtumode to specify , then use
mtusize to specify a value. If mtumode is set to default , the system
automatically sets the MTU value to 1260.
mtumode <get|default|specify>
mtusize <get|660|780|900|1020|1140|1260|1500>
nath323compatible
Sets or gets the NAT is H.323 Compatible setting.
nath323compatible <get|yes|no>
numberofrouterhops
Sets or gets the maximum number of router hops for streaming.
numberofrouterhops get
numberofrouterhops set {1..127}
primarycallchoice
Sets or gets the primary call type for placing calls.
primarycallchoice <get|isdn|ip|sip|manual>
registerall
Alias for the
all register command.

Release Notes
V500 and VSX systems, version 8.5
8
remotemonenable
Gets the state of remote room and call monitoring.
remotemonenable get
rs232monitor
Sets or gets the state of RS-232 serial port monitoring. When RS-232
monitoring is enabled, you can view all communication through the serial port
as output to Telnet port 23.
rs232monitor get
rs232monitor <on|off>
secondarycallchoice
Sets or gets the secondary call type for placing calls.
secondarycallchoice <get|isdn|ip|sip|none>
telnetmonitor
Sets or gets the state of Telnet session monitoring. When Telnet monitoring is
enabled, you can view all communication to and from the Telnet port 24
session as output to Telnet port 23.
telnetmonitor get
telnetmonitor <on|off>
unregisterall
Alias for the
all unregister command.
useroompassword
Sets or gets the Use Room Password for Remote Access setting.
useroompassword get
useroompassword <no|yes>
v35broadcastmode
Sets or gets the V.35 broadcast mode. This command is only applicable if you
have a V.35 network interface connected to your system.
v35broadcastmode <get|on|off>
videocallorder
Sets the video call order of the specified protocol to the specified slot.
videocallorder <isdn|h323|sip> <1|2|3>
voicecallorder
Sets the voice call order of the specified protocol to the specified slot.
voicecallorder <pots|voice|vtx> <1|2|3>

Release Notes
V500 and VSX systems, version 8.5
9
Corrected Issues in Version 8.5
The following table lists issues corrected in version 8.5.
Issue Description
API Previously there was no way to enable VGA mode for monitor 2
through API commands. The
configdisplay command
provides this ability.
When setting the administrator password from the API
interface, you can use the # and * characters. You can now use
the Alt key on the onscreen keyboard to access these
characters in the embedded user interface.
Cameras
(VSX systems)
You can calibrate a PowerCam™ Plus for auto camera tracking
without disabling stereo.
Auto Camera Tracking and Auto Camera Tracking to Presets
remain enabled after a system restart.
Chair Control When using chair control, it no longer takes two clicks to
acquire chair control.
PVX™ systems are listed as meeting participants during chair
control.
Content
Statistics
The Content Statistics screen displays transmit statistics for the
People+Content IP application.
Directory You can add a multipoint entry to a custom category.
Global
Management
System
If you received a support acknowledgement message from
Global Management System, you no longer need to press the
Home button on the remote to make the message go away.
Global Management System provisioning of the Primary and
Secondary Call Types is now supported.
Interoperability
Aethra
H.239 functions properly with Aethra Vega Star Gold 6.0.30.
Interoperability
H.239
H.239 now works with TANDBERG B10.2 (which can receive
VGA and SVGA resolutions for content), MGC 7.5.0.52, Sony
PCS-1 3.22, TANDBERG 6000 MXP F4.1, iPower 62.0.1208,
TANDBERG E5.2.
Interoperability
iPower™
In H.323 multipoint calls using AES encryption, with a
VSX system as the MCU and iPower and PVX systems as
endpoints, iPower did not transmit video if PVX was the second
endpoint. This has been corrected.
Interoperability
MCU
With MGC 7.0.0.72, far end camera control did not always work
if all sites in a voice-switched conference were ISDN. This has
been corrected.

Release Notes
V500 and VSX systems, version 8.5
10
Interoperability
MGC™
The VSX system displayed the near- and far-site mute icon
when it mutes during H.323 gateway calls with the MGC100
gateway, but the far end may not have been muted. This is
corrected with MGC 7.5.0.52.
Interoperability
RADVISION
Calls between a V500 or VSX system and a PVX system
through a RADVISION ECS gatekeeper had no Far End
Camera Control. This has been corrected.
Interoperability
Remote Controls
Third-party remote controls did not work correctly when
pressing the same button repeatedly. The user interface now
provides a Use Non-Polycom Remote setting to address this.
Interoperability
Sony
The VSX 8000 was unable to receive content from a Sony
PCS-1 in H.320 calls that used H.239, unless the VSX 8000
started and stopped sending content first. This has been
corrected.
In H.323 calls, V500 and VSX systems were sometimes unable
to control the Sony PCS-1 2.40 camera.
In H.320 2x64 calls to a Sony PCS-1, only one channel
connected. This has been corrected.
Interoperability
TANDBERG
In voice switching H.320 encrypted conferences, V500 or VSX
systems may have problems transmitting video. Continuous
presence conferences do not experience this problem. This
does not occur with TANDBERG MXP F4.1.
In H.323 H.239 calls with a TANDBERG 6000, the TANDBERG
system's content monitor will show a blank screen when the
call connects. This does not occur with TANDBERG E5.2.
In encrypted H.323 calls at 768 kbps or above with TANDBERG
B and E series systems, V500 or VSX systems may continue to
display video mute messages throughout the conference. The
does not occur with the TANDBERG MXP systems running
F2.5 software. This does not occur in unencrypted calls or with
TANDBERG E5.2.
Encryption is not supported with the TANDBERG Gateway
version 2.0 and earlier. In version 2.1, encryption is supported
on the H.320 side of the call only. This does not occur with
TANDBERG G3.0.
Issue Description

Release Notes
V500 and VSX systems, version 8.5
11
Interoperability
TANDBERG
The following issues were seen in H.239 calls between V500 or
VSX systems and TANDBERG E series systems.
•In 128 kbps calls between a VSX 8000 system and a
TANDBERG 6000E, content from the TANDBERG system
were sometimes sent to the wrong display. This has been
corrected.
•V500 and VSX systems did not always receive content in
calls with TANDBERG 880E systems. This has been
corrected.
In calls between a V500 or VSX system and a TANDBERG
6000 B9.1 system and E4.2 with H.239 enabled, the call
connected and the V500 or VSX system displayed video
correctly, but the TANDBERG system displayed black video.
When H.239 was disabled on either system, video was
displayed on the TANDBERG system correctly. This has been
corrected.
H.239 was not supported in H.320 V500 or VSX systems
multipoint calls with TANDBERG systems. This has been
corrected.
In H.320 H.239 conferences with a TANDBERG 6000 MXP
MCU, a V500 or VSX system was unable to receive or transmit
content. This has been corrected.
The VSX system does not receive video in H.323 voice
activated switching conferences with the TANDBERG 6000
E4.0 MCU. The does not occur in continuous presence
conferences.
H.239 functions properly with TANDBERG E5.2 and MXP F4.1.
People+Content For best results sending and receiving content, use call rates
greater than 128 kbps.
Changing laptop resolution while sending content may result in
the far site losing content. If this occurs, stop and restart
sending content.
Do not change the People+Content quality preference while
sending content.
The far site can select a camera source on the near site for
content. The only way the far site can then stop this source is to
start sending content itself.
In calls to TANDBERG systems, if H.239 is enabled on the
VSX system but not enabled on the TANDBERG system,
content will not be sent to the TANDBERG system (though the
VSX system may report that content is being sent).
In H.261 ISDN conferences through MGC, content may not be
displayed.
Issue Description

Release Notes
V500 and VSX systems, version 8.5
12
People+Content
IP
When you use People+Content IP to show content on a VSX
system, if a dialog box is displayed on the VSX system user
interface, the People+Content IP content will continue to
display on the VSX system until the dialog box is dismissed,
even if "Stop" is pressed on the People+Content IP application.
SIP You can now use the Recent Calls list to dial incoming calls.
Softupdate V.35 Calling Profile prefixes are saved when you update the
system software to version 8.5.
The VSX system is now able make V.35 calls after running
Softupdate, without the need to restart.
When reinstalling software version 7.x, you had to disable Save
System Settings during the installation to prevent
unpredictable behavior. Installing version 8.0 or later does not
display this problem.
Non-default call rates such as 56, 64,112 kbps, and so on had
to be selected again after an update to version 8.0. Installing
version 8.5 does not display this problem.
Issue Description

Release Notes
V500 and VSX systems, version 8.5
13
User Interface If you cleared all options for content display on the Monitors
screen, the default settings were applied after a system restart.
This has been corrected.
The Enable Basic Mode option is now available in the user
interface.
If Stereo was enabled, and then echo canceller was enabled,
stereo was disabled on the Polycom mics but no user interface
message appeared to notify the user. This has been corrected.
Web Interface The People+Content VGA option key on the VSX 7000e, when
enabled, was not displayed as enabled in the web interface.
In the web interface directory, when registered to Global
Directory Server, the user had to wait until the applet was fully
loaded. Refreshing the page killed the current session and
prevented updates from occurring. This has been corrected.
The Home Screen Settings page became inaccessible if you
entered an apostrophe in the Enter Marquee Text field. The
Screen Saver page became inaccessible if you entered an
apostrophe in the Screen Saver Text field. This has been
corrected.
Changing some values in the web interface would reboot the
system. The interface displayed a dialog noting that the system
would restart. This has been corrected.
The Directory screen in the web interface would hang while
trying read Global Address Book entries if the computer did not
have Sun JVM 1.2 or later installed. Microsoft Virtual Machine
was not supported. This has been corrected.
When editing directory entries in the web interface, the speed
and category entries were sometimes incorrect. This has been
corrected.
The ping utility did not always function properly from the web
interface. This has been corrected.
The trace route utility could not be performed from the web
interface. This has been corrected.
The Allow Directory Changes field did not get updated if
configured from the web interface. This has been corrected.
Issue Description

Release Notes
V500 and VSX systems, version 8.5
14
Web Interface On a VSX 6000, the web interface sometimes listed
Pro-Motion™ video even thought it was not valid for the
VSX 6000. This has been corrected.
An Internet Explorer web browser sometimes needed to be
restarted if it was being used to monitor a VSX system while
call preferences were changed between H.323 and SIP from
the embedded interface. This has been corrected.
If you toggled between H.323 and SIP enabled from the web
interface, the change was not implemented the first time (both
were disabled). You had to make the change a second time for
the new setting to be activated. This has been corrected.
When you changed the ISDN Switch Protocol from the
system's web interface and then clicked Update, only the first
line was shown. If you waited 5-10 seconds and pressed
refresh, all four lines were shown again. This has been
corrected.
After you created a multi-site entry in the directory via the web
interface and then tried to create another multi-site entry, the
participants you entered for the previous entry appeared in the
participants window. This has been corrected.
When browsing certain pages in the web interface using
Internet Explorer with the Sun Java plug-in installed, you may
have been asked to enter the admin user ID and
password. This has been corrected.
Issue Description

Release Notes
V500 and VSX systems, version 8.5
15
Feature Limitations
The feature limitations for version 8.5 are listed in the following table. If a
workaround is available, it is noted in the table.
Feature Limitation
AES Encryption You cannot activate encryption during a call.
Analog Phone Incoming POTS (analog phone) calls will not be reported in
the Recent Calls list.
API The
prilinebuildout set command does not work for
values -7.5 and -22.5.
Some color scheme modes may not be selectable using API
commands.
The
vcstream register command does not work from the
API interface.
The remotecontrol enable all command is not working.
So if remote control is disabled from the API interface, you
must restart the system to enable it again.
The notify sysalerts command does not return status
information on Auto Answer settings.
The gatewayprefix set and gatewaysuffix set API
commands accept special symbols as value parameters.
Entering another gatewayprefix set or gatewaysuffix
set
command with any value parameter forces the system to
restart.
The
chaircontrol set_password command does not work.
The notify vidsourcechanges command does not notify
about selecting a content source.
Currently API interfaces do not report when the system
restarts.
Use the command
callinfo all instead of display call .
If rollover dialing occurs (e.g. 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.

Release Notes
V500 and VSX systems, version 8.5
16
API If the control application issues a vcbutton play command
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
vcbutton [play|stop] functionality.
If the VSX system does not have an active LAN connection
and a resolved IP address when it boots, it will not report
system events on its serial port. It will resume reporting
events after the LAN is connected. To work around this issue
in an environment that does not have LAN connectivity,
configure a static IP address and use an RJ-45 loopback
connector to simulate an active LAN.
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.
Audio Playback volume is not adjustable on the start-up language
selection screen.
A VSX system with version 8.0 configured for fixed audio
output mode may have higher output gain than in previous
releases.
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.
Calling When you call a cell phone using voice over ISDN, set the
call quality to ISDN Phone. Setting the call quality to Auto
may result in unexpected behavior.
When two systems with dynamic bandwidth enabled connect
in a high line rate H.323 call (768 kbps or higher) over a DSL
or cable line, the system reports the line rate as the rate at
which the call was dialed. However, the call's actual
bandwidth is likely much lower, due to the DSL or cable line's
restricted uplink speed. The actual transmit bandwidth being
used in the call is displayed on page 2 of the Call Statistics
screen. Note that it is recommended that system
administrators set the Maximum Transmit Bandwidth
setting in System > Admin Settings > Network > IP >
Quality of Service > Bandwidth to match their DSL or cable
line's uplink speed, as this will prevent the system from trying
to transmit at rates higher than the DSL or cable line can
accommodate.
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
dialing order. To work around this behavior, set Analog
Phone ahead of ISDN Voice in the Call Preference list.
Feature Limitation

Release Notes
V500 and VSX systems, version 8.5
17
Cameras
(VSX systems)
There is no way for a user to get camera control for a camera
that is set to the content channel.
The Camera Calibration screen will always be displayed for
the VSX 7000e and VSX 8000, even though automatic
camera tracking only works with a PowerCam Plus camera.
To avoid a “keystone effect” in which the video image
appears tilted, make sure that the VSX 5000 camera is
pointed perpendicular to the subject.
Chair Control VSX 3000 systems may lose chair control ability, especially
in multipoint calls with all ISDN endpoints.
Selecting Acquire Chair on a VSX 7000 MCU may disable
Discussion mode view.
Closed Captions Closed captions cannot be sent through a gateway.
Conference on
Demand
Conference on Demand calls to ISDN endpoints 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 endpoints.
Configuration Do not change the VSX system monitor setting while sending
content.
VSX 5000 factory camera presets do not work.
Contact List If you enable the contact list home screen and want to install
a system software version earlier than 8.5, disable the
contact list before doing so. Either disable it in the user
interface before you run Softupdate, or disable the option to
save system settings when you run Softupdate.
Directory System names with Chinese hieroglyphs cannot be edited in
the directory using the system’s embedded interface.
New directory entries created in a new local category may
not be visible when you try to view them the first time, until
you move around in the screen.
Pressing Select on the remote control twice when selecting a
directory entry may lead to connection errors.
Far End Camera
Control
Far End Camera Control does not work reliably with
non-VSX system endpoints.
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.
Global Directory When dialing calls from the global directory, VSX systems set
the call speed based on the local call quality setting, rather
than the directory’s setting.
Feature Limitation

Release Notes
V500 and VSX systems, version 8.5
18
Global
Management
System
VSX 3000A systems cannot be provisioned using Global
Management System 7.0.1.212 or 7.0.4.
The GMS Call Statistics screen shows up to only three
endpoints in an internal multipoint conference, even if there
are more than three endpoints connected.
If you receive a support acknowledgement message from
Global Management System, press the Home button on the
remote to make the message go away.
Global Management System provisioning of the Primary and
Secondary Call Types is not supported.
Global Management System does not display H.320
information for V500 systems.
Starting with version 8.5, VSX systems provide two
passwords: a room password for local access via the system
user interface and a remote access password for access via
the web interface, etc. Setting the admin password in Global
Management System and SE200 will update the remote
access password. Currently, Global Management System
and SE200 do not provide a separate command to set the
room password. To work around this issue, select use "Use
Room Password for Remote Access" to set both passwords
to the same value, or use the web interface to set the room
password.
H.264 The following conditions apply to H.264:
•On 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 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.
H.331 When broadcast mode is enabled on a V.35 system and the
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 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 should enable People+Content.
When you enable People+Content in the H.331 configuration
of a V.35 system, you must also enable H.239 to send
content.
Interoperability
ADTRAN TSU 100
With V.35 systems, VSX systems can crash when in a call at
1280 kbps.
Feature Limitation

Release Notes
V500 and VSX systems, version 8.5
19
Interoperability
Aethra
In H.323 calls between a VSX 8000 system and some Aethra
systems, 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.
Interoperability
Avaya
AES Encryption is not supported while registered to the
Avaya Communication Manager (ACM).
When a V500 or VSX system attempts to call another V500
or VSX system through Avaya Communication Manager, the
near-site system continues to ring if the far site rejects the
call.
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.
H.320 calls in a Multipoint scenario with other systems
registered to the Avaya Communication Manager (ACM) are
not supported.
The Avaya Communication Manager (ACM) does not
support wideband audio over trunk calls in this release.
Wideband audio is not supported in this case. V500 and
VSX systems will connect with G.711 audio.
Cisco PIX does not pass through Annex H which is required
by the Avaya Communication Manager (ACM). V500 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).
Feature Limitation

Release Notes
V500 and VSX systems, version 8.5
20
Interoperability
Avaya
Avaya's IP Softphone (IPSP) with video set to manual will not
negotiate video with endpoints registered to a neighboring
gatekeeper.
In calls placed from a V500 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 Avaya Communication Manager
(ACM).
While registered to the ACM, VSX multipoint systems are
limited to four sites (internal multipoint + three far sites) in a
multipoint call.
When V500 and VSX systems that are registered to the ACM
call a ViewStation FX system registered to PathNavigator™,
the call connects with no remote video on the ViewStation
system.
Internal MCU calls from an iPower system to an Avaya IP
Softphone (IPSP), V500, or VSX system do not connect.
ACM Telephony features and IPSP video mute are not
supported with V500, VSX, iPower, or ViewStation® FX
systems behind PathNavigator.
iPower IMCU calls to VSX systems using Avaya do not
connect.
Interoperability
Check Point
Calls through a Check Point firewall configured for H.323
may have no audio or video. To work around this, disable the
H.323 traffic only protocol on Check Point and create new
rules on the Check Point for TCP1720, TCP3230-3237, UDP
3230-3253.
Interoperability
Cisco PIX
In an H.323 multipoint conference using a VSX system MCU
located behind a Cisco PIX 6.3.4 firewall among systems
with H.239 enabled, the V500 or VSX system outside of the
firewall may not receive video when other sites connect. To
avoid this, disable H.239 on all sites.
V500/VSX systems with AES encryption enabled cannot
connect using H.460 with Cisco PIX 506.
Interoperability
EdgeMarc
When using PathNavigator in conjunction with an EdgeMarc
E-30, do not configure PathNavigator with an alternate
gatekeeper.
If a VSX system is registered with an EdgeMarc E-30 that
uses PathNavigator, the VSX system still appears to be
registered even if it loses connectivity with the EdgeMarc.
SIP calls through an EdgeMarc E-30 are not supported.
Only Polycom PathNavigator gateways are supported when
connecting calls through an EdgeMarc E-30.
Feature Limitation