[Software] VVX UC Software

Polycom Employee & Community Manager

[Software] VVX UC Software

What’s New in This Release?


Poly Unified Communications (UC) Software is a release for OpenSIP and Skype for Business deployments.

These release notes provide important information on software updates, phone features, and known issues.


DNS Cache Configuration Update


When you enable the DNS cache restore parameter (dns.cache.dynamicRestore.enable), you can now configure the number of retries the phone attempts before it restores the cache using the


dns.queryRetryCount parameter.







0 to 48 - The number of retries that the phone attempts before the cache is restored.

0 - Disable.

4 (default).


Ignore Software Upgrades


You can configure Poly phones to ignore software upgrades using the following options:


● Users can ignore software upgrades until the next synch event.

● Users can ignore subsequent upgrade dialogs.




1 - The Ignore and Ignore until next Reboot/Sync softkeys display on the phone’s local interface during a software upgrade alert.

0 (default) - Users can defer software upgrades up to three times.


SNTP Resiliency


Poly phones can try alternate sources for SNTP addresses and offsets if attempts to contact the time server don’t work due to one of the following issues:


● The attempt fails.

● The phone receives invalid or no responses.


Enhanced Failover Configuration Updates


Poly UC Software 6.3.1 includes improvements to failover configuration.


SBC Line Registration


Line registration ensures that the phone maps lines to the session border controller (SBC), based on the DNS response. When you restart the device, it re-executes the initial DNS logic using NAPTR lookup to resolve the appropriate SBC IP addresses.


Fast Failover


This release introduces fast failover. In regular failover, the phone makes four attempts to contact a server before it fails over.


When you set the 






parameter to 3, the phone makes only three attempts to contact the server before it tries to register with another server.


Failover from TCP to TLS Crypto Attribute for SRTP


Poly phones support failing over from a TCP connection to a TLS connection. When the phone fails over to the TLS connection, the phone inserts the crypto attribute into the message to the new server to enable SRTP.


SBC List Traversal


In previous releases when SBC failover occurred, the phone restarted SBC selection from a failover proxy list rather than attempting to connect with an SBC of the same weight and priority. In this release, the phone uses the weight and priority configured in the DNS record to select the new SBC.


Enhanced Failover Configuration Parameters


Use the following parameters to configure enhanced failover features.








1 - Enable Line to SBC mapping and SBC list traversal.

0 (default) - Disable.






 2000-5000 - Define the time to wait before failing over to the next IP in the list of records resolved by the DNS server applicable only before the TCP connection establishment. 5000 (default).


AES 256 Encryption for SRTP Support


Poly phones support 2 methods of AES-256 Media encryption: GCM and ICM.






1 - Enable AES-256 GCM Encryption for SRTP Support.

0 (Default) - Disable. 






1 - Enable AES-256 ICM Encryption for SRTP Support.

0 (Default) - Disable.


Appending Strings to the User Agent Header


Poly phones allow user agent header strings to accept alphanumeric and special characters up to 256 characters total. 






0-256 - Characters allowed in the user agent header string.





voIpProt.SIP.header.userAgentAppendString="/%BW_MAC %/%BW_ORG_ID%- %BW_ENT_ID%-%BW_GROUP_ID%/%BW_CURRENT_Config_Version%“ 



The phone sends the following user agent header:



User-Agent: PolycomVVX-VVX_501-UA/ Group1/V12.0




Security Updates


See the Polycom Security Center for information about known and resolved security vulnerabilities.


  • Older 6.3.0 release >here<

If official support is required please check how to phone or open a case here

The title Poly Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.


⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓SIGNATURE ⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓
Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
Please also ensure you always check the VoIP , Video Endpoint , Microsoft Voice , PSTN or other FAQ's in the different sections