HP Poly announces the 8.3.0 release of Poly Voice Software (PVOS) for Poly Edge E only Series phones
Jan 06, 2024 Question: Since the move from Poly to HP where can I download Software?
Resolution: Please see >here< for an explanation and create an Account for Poly Lens in the cloud
Software version: PVOS 8.3.0
Release date:June 2025
The build ID is UCS 8.3.0.15436.
This release of PVOS includes new features, feature enhancements, and important field fixes.
Review the resolved issues in this release.
Review the new known issues in this release.
What’s new in PVOS 8.3.0
This release of PVOS includes new features, feature enhancements, and important field fixes.
Beginning in this release, Poly Edge E phones can operate in a Federal Information Processing Standards (FIPS) compatible mode that ensures use of cryptographic algorithms and methods approved by the U.S. government. While FIPS mode provides a higher level of security and data protection, it limits the Poly Edge E Series phones to using only FIPS-approved algorithms, preventing the use of potentially weaker or unvalidated algorithms.
Shared call appearances on the Zoom service can now interact with point-to-point and conference calls in new ways.
RFC 8760 updates RFC 3261 by modifying the Digest Access Authentication scheme used by SIP to add support for additional secure digest algorithms (SHA-256 and SHA-512/256) to replace the older and obsolete MD5 algorithm.
This release no longer provides compatibility for SSL v2 and v3 and TLS 1.0 abd 1.1 backwards compatibility options. TLS 1.3 is used by default, with a minimum supported TLS version of TLS 1.2 for backwards compatibility.
The latest TLS 1.3 standard offers improvements in speed and security of encrypted data. As of this release, TLS 1.3 is always offered when a TLS connection is created, with TLS 1.2 available for far end services that don’t yet support TLS 1.3.
Poly Voyager 4310, Poly Voyager Surround 85, Poly Voyager Legend 30, and Poly Voyager Legend 50 images have been added to the interface when you use Poly Fast Pair for Bluetooth pairing.
Many HTTP-based services offered on Poly Edge E phones now offer SHA256 digest access authentication (RFC 7616). For backwards compatibility with services unable to support SHA256, MD5 remains available, and you can disable it using new configuration parameters to specify which digest algorithm is permitted.
The REST API now offers session based authentication with three new APIs to create, list, and delete session data.
Poly Edge E phones now deny access to users who log in to the system web interface using the default user password. The user account must have a unique password to log in.
The usb.headset.config.enabled parameter is deprecated starting in this release.
The local contact directory on all Poly Edge E phones now supports up to 1000 contacts.
You can now bulk configure phones with company-specific information such as the Organizational Unit (OU), Locality (L), and Common Name (CN) using configuration parameters.
You can now choose to enforce two-factor authentication for access to the phone's system web interface.
An optional configuration parameter is now available to allow administrators to restrict software downgrades.
Poly Edge E FIPS compatibility mode
Beginning in this release, Poly Edge E phones can operate in a Federal Information Processing Standards (FIPS) compatible mode that ensures use of cryptographic algorithms and methods approved by the U.S. government. While FIPS mode provides a higher level of security and data protection, it limits the Poly Edge E Series phones to using only FIPS-approved algorithms, preventing the use of potentially weaker or unvalidated algorithms.
The following restrictions are now in place:
SSL v2, v3 and TLS v1.0 and 1.1 are no longer available
RSA, DSA and DH keys shorter than 2048 bits are prohibited
ECC keys shorter than 224 bits are prohibited
Cipher suites using RC4 are prohibited
Cipher suites using SHA1 MAC algorithms are prohibited
All export cipher suites are prohibited
3DES is prohibited
Certificate signatures using SHA1 and MD5 are prohibited
FIPS compatibility can be disabled allowing for limited backwards compatibility with less secure algorithms such as 3DES and SHA-1, as well as enabling access to stronger algorithms that are not yet validated under the FIPS program, however, key size enforcement restrictions listed above will remain active
The following parameters are now enabled by default:
device.sec.TLS.FIPS.enabled.set
device.sec.TLS.FIPS.enabled
When device.sec.TLS.FIPS.enabled="0", FIPS mode is disabled, which permits access to cryptographic algorithms that may be recognized as weaker, such as 3DES. It also permits access to stronger algorithms that are not yet validated under the FIPS program.
Zoom shared line appearances, join and merge calls, and participant view
Shared call appearances on the Zoom service can now interact with point-to-point and conference calls in new ways.
When another user of a shared line starts a multiparty conference call, the press and hold action on the shared line key now gives you the option to view the conference participants by pressing the Roster softkey.
You can join the conference via the Join softkey.
If another user is in a point-to-point call, after a press and hold, they can create a three way conference by pressing the Join softkey.
All configuration is managed through the Zoom administrative web portal.
Note: Selecting Roster will show the people in the call
SHA256/512 digest authentication schemes for SIP
RFC 8760 updates RFC 3261 by modifying the Digest Access Authentication scheme used by SIP to add support for additional secure digest algorithms (SHA-256 and SHA-512/256) to replace the older and obsolete MD5 algorithm.
Removal of obsolete SSL and TLS protocols
This release no longer provides compatibility for SSL v2 and v3 and TLS 1.0 abd 1.1 backwards compatibility options. TLS 1.3 is used by default, with a minimum supported TLS version of TLS 1.2 for backwards compatibility.
Support for TLS 1.3
The latest TLS 1.3 standard offers improvements in speed and security of encrypted data. As of this release, TLS 1.3 is always offered when a TLS connection is created, with TLS 1.2 available for far end services that don’t yet support TLS 1.3.
You can configure TLS 1.2 or TLS 1.3 as the minimum protocol version. You can’t disable use of TLS 1.3.
Headset support for Poly Fast Pair
Poly Voyager 4310, Poly Voyager Surround 85, Poly Voyager Legend 30, and Poly Voyager Legend 50 images have been added to the interface when you use Poly Fast Pair for Bluetooth pairing.
SHA256 for digest authentication is now available for HTTP-based services
Many HTTP-based services offered on Poly Edge E phones now offer SHA256 digest access authentication (RFC 7616). For backwards compatibility with services unable to support SHA256, MD5 remains available, and you can disable it using new configuration parameters to specify which digest algorithm is permitted.
|
Service |
Algorithm |
Parameter |
Default |
|
SIP |
Digest MD5 |
voipProt.SIP.auth.digest.md5.enabled voipProt.SIP.auth.digest.sha256-sess.enabled |
1 |
|
TR-69 |
Digest MD5 |
httpd.tr069.auth.digest.md5.enabled |
1 |
|
Modular Room (C60 Daisy Chaining) |
Digest MD5 |
httpd.mrprov.auth.digest.md5.enabled |
1 |
|
Telephony Event Notification Services |
Basic |
httpd.site.auth.basic.enabled |
0 |
|
Screen Capture |
Basic |
httpd.site.auth.basic.enabled |
0 |
|
XML Push API services |
Digest MD5 |
httpd.apps.auth.digest.md5.enabled |
1 |
|
XML Polling API services |
Digest MD5 |
httpd.apps.auth.digest.md5.enabled |
1 |
|
REST API |
Basic |
httpd.rest.auth.enabled |
0 |
The REST API now offers session based authentication with three new APIs to create, list, and delete session data.
For more information, refer to the Poly UC Software and Poly Voice Software REST API Reference Guide.
Poly Edge E phones now deny access to users who log in to the system web interface using the default user password. The user account must have a unique password to log in.
To set the user role login denial, refer to the Passwords section in the Securing the phone chapter of the Poly Edge E Series Phones Administrator Guide.
Deprecated usb.headset.config.enabled parameter
The usb.headset.config.enabled parameter is deprecated starting in this release.
Plantronics and Poly USB headsets remain supported, but select legacy headsets and adapters that previously offered limited configuration from the Poly Edge E onscreen menus now require customers to use Poly Lens Desktop App for configuration management.
These headsets include:
Blackwire 32xx/52xx/82xx Series
Savi 440/740 Series
DA80/90 Series
Increased maximum number of local contacts
The local contact directory on all Poly Edge E phones now supports up to 1000 contacts.
You can now bulk configure phones with company-specific information such as the Organizational Unit (OU), Locality (L), and Common Name (CN) using configuration parameters.
For more information, review Enable and configure SCEP.
Two-factor authentication for system web interface and diagnostic access
You can now choose to enforce two-factor authentication for access to the phone's system web interface.
You can apply two-factor authentication to all access attempts. You can also waive it for a configurable period after the first approval, with further waiver restrictions available based on the connection's source IP or the diagnostic service being accessed.
Applies to products:
Edge E Series
CCX Series
Trio 660
For more information, see the Poly Edge E Series Phones Administrator Guide PVOS 8.3.0.
Optional software rollback prevention
An optional configuration parameter is now available to allow administrators to restrict software downgrades.
Parameter: device.prov.rollbackProtection
Jul 25, 2013 Question: How can I set up Device parameters on my phone via a configuration file?
Resolution: Please check => here <=
Description: The default value of "Auto" applies only to CCX and Trio C60 phones running the Microsoft Teams base profile where rollback protection is enabled by default. For all other base profiles, and on Poly Edge E, the value of Auto applies the same meaning as "Disabled".
Resolved issues in PVOS 8.3.0
Review the resolved issues in this release.
|
Category |
Issue ID |
Description |
|---|---|---|
|
Audio |
VOICE-82671 |
Calls placed on hold experience one-way audio after resuming when SRTP sequence numbers roll over from 65,535 to 0 while the call is held. |
|
Calling |
VOICE-81149 |
Poly Edge E phones on the Google Voice service don’t play early media before the call connects. |
|
Interoperability |
VOICE-80929 |
The phone's web browser-based XML Telephony applications used for Metaswitch call services occasionally show errors reporting SSL/TLS handshake failed. |
|
Interoperability |
VOICE-77078 |
When an IP address is added to the set of a phone's proxies/servers via DNS and re-registration after failover with periodic failback is enabled, the phone gradually exhausts its resources and eventually ceases to maintain its SIP registration(s). |
|
Interoperability |
VOICE-72830 |
Diagnostic features, such as log collection, pcaps, and configuration information) initiated from PDMS-SP to Poly Edge E phones, fail after many hours of uptime due to the cloud connection dropping and not recovering on its own. |
|
Logs |
VOICE-82394 |
Poly Edge E logs harmless but suspicious Cannot decode the packet warnings when receiving keep-alive messages. |
|
Logs |
VOICE-78563 |
Logs available from the system web interface are cleared when restarting, limiting access to troubleshooting information on events leading up to the restart. |
|
Network |
VOICE-82168 |
The Poly Edge E phone log shows low memory, and the phone sometimes responds slowly in addition to other side effects. |
|
Network |
VOICE-81067 |
SIP registration renewal fails after one hour due to an error in matching the correct contact binding when both of the following conditions are met:
|
|
Reports |
VOICE-81027 |
Voice quality Mean Opinion Scores (MOS) for calls between Poly Edge E phones and Zoom desktop clients result in lower than expected values, despite perceived quality being much higher. |
|
User interface |
VOICE-79025 |
Poly Blackwire 32xx Series headsets can’t synchronize the mute state with Poly Edge E series phones when using the headset's mute button. |
|
Voice |
VOICE-82832 |
Star code calls placed after going offhook fail due to the asterisk (*) character being removed when call.internationalDialing.enabled="0". |
|
Voice |
VOICE-82759 |
Configuration file provisioning fails if a 302 response is received that directs the phone to an alternate file location. |
|
Voice |
VOICE-82608 |
Call control screens for Bluetooth paired mobile phones do not appear when call.enableOnNotRegistered="0" and multiple line key appearances of a SIP registration are configured. |
|
Voice |
VOICE-82168 |
Poly Edge E phones using LDAP query page sizes of 64 can sometimes experience low memory conditions resulting in slow response to key presses, audio delay at the start of calls, and logs reporting low memory warnings. |
|
Voice |
VOICE-81639 |
When BLF are configured across multiple line key pages and more than one call is remotely active, the flashing call activity indicators for some pages continue flashing even after a remote call is ended. |
|
Voice |
VOICE-78494 |
After registration failback occurs, SIP subscriptions for BLF, call-info, voicemail, etc that were established with the previous SBC before the failback occurred may not work until a subsequent failover. |
Known issues in PVOS 8.3.0
Review the new known issues in this release.
These release notes don’t provide a complete listing of all known issues for the software. Issues not expected to significantly impact customers with standard voice and video conferencing environments may not be included. In addition, the information in these release notes is provided as-is at the time of release and is subject to change without notice.
This known issues table only includes issues discovered during this release. For known issues in the previous release, review the Poly Voice Software 8.2.3 Release Notes.
|
Category |
Issue ID |
Description |
Workaround |
|---|---|---|---|
|
Audio |
VOICE-83035 |
Poly Edge E calls lose audio after a consultative transfer when all three callers involved are subscribers on the Google Voice service. |
None. |
|
Interoperability |
VOICE-83069 |
Poly Edge E calls on the Google Voice service can drop immediately on answer due to a DTLS audio negotiation failure. |
Set reg.x.ice.reInviteWithSelectedCandidate="0". |
|
Network |
VOICE-82688 |
XML telephony event notifications [from the phone] do not retry when challenged by 401 responses that request digest authentication algorithms other than basic |
None. |
|
User interface |
VOICE-81388 |
After restarting, the phone displays the warning DHCPv6 failed when configured in dual mode with LLDP/CDP enabled. |
None. |
Edge E
