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.
May 2006
3725-21988-013/A
Release Notes
V500 and VSX systems, version 8.5
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).
2
Release Notes
V500 and VSX systems, version 8.5
Security Mode requires secure access and a password for Web, Telnet, and FTP
access.
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.
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
3
Release Notes
V500 and VSX systems, version 8.5
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.
4
Release Notes
V500 and VSX systems, version 8.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.
5
Release Notes
V500 and VSX systems, version 8.5
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|
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>
6
Release Notes
V500 and VSX systems, version 8.5
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.
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
7
command.
Release Notes
V500 and VSX systems, version 8.5
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>
8
Release Notes
V500 and VSX systems, version 8.5
Corrected Issues in Version 8.5
The following table lists issues corrected in version 8.5.
IssueDescription
APIPreviously there was no way to enable VGA mode for monitor 2
through API commands. The
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.
configdisplay
command
Cameras
(VSX systems)
Chair ControlWhen using chair control, it no longer takes two clicks to
Content
Statistics
DirectoryYou can add a multipoint entry to a custom category.
Global
Management
System
Interoperability
Aethra
Interoperability
H.239
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.
acquire chair control.
PVX™ systems are listed as meeting participants during chair
control.
The Content Statistics screen displays transmit statistics for the
People+Content IP application.
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.
H.239 functions properly with Aethra Vega Star Gold 6.0.30.
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™
Interoperability
MCU
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.
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.
9
Release Notes
V500 and VSX systems, version 8.5
IssueDescription
Interoperability
MGC™
Interoperability
RADVISION
Interoperability
Remote Controls
Interoperability
Sony
Interoperability
TANDBERG
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.
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.
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.
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.
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.
10
Release Notes
V500 and VSX systems, version 8.5
IssueDescription
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+ContentFor 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.
11
Release Notes
V500 and VSX systems, version 8.5
IssueDescription
People+Content IPWhen 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.
SIPYou can now use the Recent Calls list to dial incoming calls.
SoftupdateV.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.
12
Release Notes
V500 and VSX systems, version 8.5
IssueDescription
User InterfaceIf 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 InterfaceThe 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.
13
Loading...
+ 29 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.