Topics
Introducing the Polycom VBP System Version 9.1.5.2.......................................................................................................................... 2 What’s New in the Polycom VBP System Version 9.1.5.2..................................................................................................................... 2 Out of the Box Installation notes ............................................................................................................................................................. 2 Interoperability ......................................................................................................................................................................................... 3 Known Issues............................................................................................................................................................................................. 3 Installation Recommendation .................................................................................................................................................................. 4 New Features introduced in VOS 9.1.5.2................................................................................................................................................ 4 Fixes and Enhancements in VOS 9.1.5.2................................................................................................................................................. 4 New Features introduced in VOS 9.1.5.1................................................................................................................................................ 5 Fixes and Enhancements in VOS 9.1.5.1................................................................................................................................................. 5 New Features introduced in VOS 9.1.5................................................................................................................................................... 6 Fixes and Enhancements in VOS 9.1.5.................................................................................................................................................... 6 New Features introduced in VOS 9.1.4................................................................................................................................................... 7 Fixes and Enhancements in VOS 9.1.4.................................................................................................................................................... 7 New Features introduced in VOS 9.1.3................................................................................................................................................... 8 Fixes and Enhancements in VOS 9.1.3.................................................................................................................................................... 8 New Features introduced in VOS 8.11.1................................................................................................................................................. 8 Fixes and Enhancements in VOS 8.11.1.................................................................................................................................................. 8 New Features introduce in VOS 8.9.1 ..................................................................................................................................................... 9 Fixes and Enhancements in VOS 8.9.1.................................................................................................................................................... 9 Upgrade Instructions .............................................................................................................................................................................. 11 Upgrade procedure ................................................................................................................................................................................. 11 Obtaining Further Assistance................................................................................................................................................................ 11
Copyright Information © 2009 Polycom, Inc. All rights reserved. 3725-77600-001D7 (October 2009) 1765 West 121st Avenue Westminster, CO 80234-2301 U.S.A. Trademark/ Patent 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 the property of their respective owners. The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc.

1



Introducing the Polycom VBP System Version 9.1.5.2
This document describes the enhancements and fixes provided by the Polycom Video Border Proxy (VBP) VoIP Operating System (VOS), version 9.1.5.2. It includes all modifications made since VBP VOS version 7.2.2

What’s New in the Polycom VBP System Version 9.1.5.2
The Polycom VBP system version 9.1.5.2 is primarily a maintenance release too include the new 200E hardware to the VBP product family. This VBP release support’s all legacy H.323 video scenario’s and adds support for SIP audio. For more information on SIP audio supported scenarios visit the Polycom Support web site for the configuration guide.

Out of the Box Installation notes
When installing the VBP-E system for the first time, the systems DHCP server is enabled and serving out an IP address range of 192.168.1.150 – 192.168.1.199 to your computer dynamically. By default the systems DHCP server does NOT assign default DNS server information. After configuring the Network parameters e.g WAN IP Address, Default gateway, Primary and Secondary DNS servers the system will now assign these DNS server IP addresses to the DHCP server. If you’re configuring the VBP system for a dynamic WAN type, check the DHCP server page after you have configured the Network parameters for the presence of DNS server IP addresses received from the provider’s server. For testing Internet connectivity you will need to renew your computers DHCP address to receive valid DNS server information. You can disable/enable your network adapter, disconnect and reconnect your Ethernet cable, or from a command prompt on a Windows OS type ipconfig release then ipconfig -renew. After you verify your computer now has valid Primary and Secondary DNS server IP addresses you will now be able to open a web browser and verify Internet browsing.

2



Interoperability
• • • • • • • • • • • • Polycom CMA 4000/5000 server v4.01.02 or higher (see note) Polycom V and VSX Series v8.7.1 or higher Polycom ViewStation SP/MP/512/H.323 v7.5.4 Polycom PVX v8.0.2 or higher Polycom ViewStation FX/EX/4000 v6.0.5 Polycom HDX systems v2.0.3.1 or higher Polycom QDX 6000 (all versions) Polycom MGC v8.0.2 or higher Polycom RSS2000 v3.0.2 or higher Polycom RMX 2000 v3.0 or higher Polycom RMX 1000 (all versions) Polycom DMA 7000 v1.0 or higher

Note: The following issues, which may impact VBP functionality exist in CMA 4.01.02. These issues are addressed in CMA version 4.01.04 • Duplicate Aliases – When a CMAD or HDX in VC2 mode moves from an internal CMA connection to an external VBP Access Proxy connection you might experience a scenario where the endpoint cannot connect to the CMA Server. An HDX endpoint is likely in this state if it displays an indicator stating that the gatekeeper service is down. A CMAD client is likely in this state if cannot progress beyond the “signing into the media server” message. In some cases, gracefully logging out of the internal location and waiting at least 10 minutes before an external login can reduce the chances of experiencing this issue. Dual Redundancy – When deploying 2 VBP’s and 2 CMA server’s for what is called “Dual Redundancy” if the MASTER CMA server fails, this forces the BACKUP CMA server to have control of all services, it is possible when this CMA failover happens, this CMA server may NOT send responses from the VIP (virtual IP) causing messages to be sent from the physical IP, the VBP is expecting messages to come from the VIP and will not be forwarded to the remote client. When deploying “Single Redundancy” 2 VBP’s and 1 CMA server, If the MASTER VBP fails, the BACKUP VBP will take over and function as expected.

•

Known Issues
• In VOS 9.1.5.2 the Polycom VBP-E series does not support the Access Proxy feature, although the feature is present in the GUI. VBP-E series platforms will support this feature in a future release. Access Proxy feature support is fully functional in the VBP-ST series. Bug 1463 – ESCVIU-27 – Facility messages are not supported on the VBP-E platforms

•

3



Installation Recommendation
Platform 200E only Upgrade Recommendation Default image Comment This release is the first firmware support for the new VBP 200E hardware platform. This VBP release is only available for the 200E hardware. The system will ship with this release. A hotfix is available through Polycom support for other hardware platforms. This release includes an SSH daemon security update introduced in VOS 9.1.3.

New Features introduced in VOS 9.1.5.2
• 200E hardware platform introduced in VOS 9.1.5.2

Fixes and Enhancements in VOS 9.1.5.2
• • Bug 3546: Added 200E hardware ID support Bug 4213 - VIU-94 - Access Proxy - NTLM string longer than 512 is not being forwarded: Increased buffer size to 2048 to handle longer NTLM authorization messages. This issue was found after the production release of 9.1.5.1, some Windows system platforms received service updates to their NTLM libraries which caused the NTLM authorization string to be longer that 512. Bug 4314 – ESCVIU-25 – Gatekeeper neighboring in LAN/Subscriber-side gatekeeper mode with a CMA gatekeeper – When gatekeeper neighboring to a providers network for ISDN offnet dialing, the providers gatekeeper was re-writing the destination alias in the LCF, when the call SETUP arrived with this modified alias the VBP’s ALG did not track the original LRQ and modified LCF correctly resulting in a ALG restart. Bug 4320 was also addressed as a direct cause on Bug 4314 – an incorrect source port was assigned as port 0 for transparent LCF responses. Bug 3598 – SIP – The system by default is configured with a SIP Server of 0.0.0.0, after an unknown time period the ALG will restart. Bug 4690 – Access Proxy – Change the default session timer to 30 mins from 60 mins. This timer is used to clean up Access Proxt clients that have disconnected from the system without logging out.

•

• •

4



•

Bug 4689 – VIU-101 – Access Proxy – Authorizations for clients using Network credentials or cached network credentials could not login. The Access Proxy was not updating the content length of the authorization fields be forwarded to CMA. The CMA server was rejecting the authorization as a bad request. Bug 4599 – Access Proxy – Logging cleanup Bug 4596 – Access Proxy – Supporting multiple clients behind a SoHo NAT device was not functioning correctly. The client tracking logic only allowed for 1 device behind a SoHo NAT, when this device logged out the remaining clients experienced a loss of Presence and LDAP directory services. Bug 4600 – Access Proxy – Configuration file cleanup. Bug 2874 – Access Proxy – Access Proxy configuration files not saved with the “ewn save” command – accessproxies.conf and accessproxy.conf now saved correctly. Bug 2961 – Access Proxy – Access Proxy UI configuration allowed a duplicate “Subscriber port” to be configured.

• •

• •

•

New Features introduced in VOS 9.1.5.1
• None

Fixes and Enhancements in VOS 9.1.5.1
• Bug 4074: Log rotation fix for iptables logging - log rotation capability has also been added to Access Proxy, the system will now have 8, 250K ap-iptables.log files located in /var/log that track the dynamic “add” or “delete” firewall rules for authenticated VC2 based endpoints. This file also tracks VC2 endpoints that have become unavailable that indicates they have been “deleted”. ap-iptables.log ap-iptables.log.1 ap-iptables.log.2 ap-iptables.log.3 ap-iptables.log.4 ap-iptables.log.5 ap-iptables.log.5 ap-iptables.log.6 ap-iptables.log.7

5



•

Bug 4075: Fixed accessproxyrc startup problem with multi cores, 6400, 6400LF, 6400LF2

New Features introduced in VOS 9.1.5
• • • Copied key/cert to /usr/local/ssl/certs Access Proxy o Added support for HDX. Changed handling of the incoming authentication message from the HDX client. Allow LAN side E/P's to dial ANNEX O If an incoming call used an AnnexO dialing string where the IP address was the address of the system itself, we would not forward the call. Now we strip of the IP address from the alias if it is matching the address of the system itself, and completes the call using the alias part of the AnnexO string.

Fixes and Enhancements in VOS 9.1.5
• • • • • • • • • • Bug 2298: Annex-O LAN->LAN calls are GK routed. Bug 3883: VBP incorrectly assigning RTP ports We now attempt to match the RTP forwarding entries according to the signaled session IDs so that the forward and reverse stream gets the same port number. Bug 3857: Access Proxy - Enable Logging. Default Access Proxy.conf file has been copied to /etc/default/ for reference. Additional enhancements to the log messages to provide before information. Bug 3858: Access Proxy - Added Log Level support. Access proxy can now print out logs of varying levels by modifying /etc/config/Access Proxy.conf. Update LOG_LEVEL with either LVL_INF, LVL_DBG, LVL_DAT. Bug 3867: Access Proxy - HTTPS access to the system on alternate port. Firewall rules in config_ep_fw.sh and config_em_fw.sh have been updated. Text/Warnings has also been updated on the Firewall page, HTTPS Certificate page and the Access Proxy page. Bug 3873: Access Proxy - VRRP Support. Access proxy will start via /etc/Access Proxyrc if VRRP is enabled and is in MASTER state. Access Proxy will self-terminate if the state changes to BACKUP. Bug 3873: Access Proxy - VRRP Support. Modified config_vrrp.sh to insert the appropriate allow iptables rules when the system is running in VBP-ST mode. Bug 3859: In Embedded Gatekeeper mode, not all the aliases are display this limitation has been removed. Message of the Day" configured or not; a longer than 8 characters password will now be rejected. Bug 3929: bandwidth tracking problem for h.460 nat'd endpoint initiated calls, this is a result of the fix for bug 2217 and is now resolved.

6