• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
Guidelines
Transitioned from Poly to HP? Discover where to find your software downloads by Clicking here
SteffenBaierUK
Level 15
‎09-30-2025 08:52 AM
Views : 3,855
No ratings

Poly announces the new release of Poly Voice Software Lite - DECT (PVOS-L DECT) 8.0.12 for Poly Rove DECT IP phones.

 

Software version: PVOS-L DECT 8.0.12

Release date: September 2025

The build ID is:

  • 8.0.12.0006

For more information, review the Poly Rove DECT IP Phones 8.0.12 release notes.

 

  • What’s new in Poly Rove 8.0.12
    This release of Poly Rove DECT IP Phones includes new features and important field fixes.
  • Resolved issues in Poly Rove 8.0.12
    Review the resolved issues in this release.
  • Known issues in Poly Rove 8.0.12
    There are no new known issues in this release.

This release of Poly Rove DECT IP Phones includes new features and important field fixes.

FIRMWARE:

 

Note: The European Union Radio Equipment Directive (EU RED) Cybersecurity Amendment 2022/30 identified in Article 3.3(d), (e) focuses on ensuring all radio equipment and products with network interfaces and services comply with essential requirements for security and resilience of radio equipment and address cyber threats. PVOS-L DECT 8.0.12 is compliant to EU RED cybersecurity requirements.

 

  • Group paging

    Poly Rove is now able to participate in group paging with other Poly UCS devices. Send and receive broadcast pages with other Poly desk, conference, and wireless phones.

  • HTTPS required for the system web interface

    HTTPS is now required for accessing the Poly Rove system web interface.

  • SHA-256 support

    The SHA-256 digest algorithm is now available for use in validating custom Root CA certificate checksums, for HTTP digest authentication to provisioning services, and for authentication when accessing the Poly Rove system's web interface.

  • System web interface login protection

    You can now configure the system web interface to lock out a user after a set number of failed login attempts in a specific time frame. This feature can protect the interface from a brute force attack.

  • Minimum TLS version now defaults to TLS 1.2

    As of this software release, fallback to deprecated TLS versions is disabled.

Group paging

 

Poly Rove is now able to participate in group paging with other Poly UCS devices. Send and receive broadcast pages with other Poly desk, conference, and wireless phones.

Group paging enables you to broadcast one-way audio announcements to users who are subscribed to a specific page group. Group paging is available on all Poly Rove phones.

Using group paging on Poly Rove

 

Use the Group Paging feature to make an announcement over a group of phones.

If group paging is configured on your phone, you do the following:

  • Subscribe to a paging group.

  • Change the default paging group used for sending pages using the Push-To-Talk (PTT) method on the Poly Rove handset.

  • Send a page to a group by selecting a group from the paging menu.

  • Send a page using the PTT action.

Subscribe to a paging group

Group paging allows users to subscribe to up to 8 paging groups.

Important: Changing the subscription from the handset will override the PageGroupReceiveMask setting on the Rove base station. Resetting the settings on the handset will revert the settings on the handset to match PageGroupReceiveMask.

 

Procedure

  1. On the phone’s local interface, go to Menu > Settings > Group Subscribe.
  2. Scroll to the group you want to subscribe to.
  3. Toggle to enable the subscription.
  4. Press Back to save your changes.


Changing the default paging group

Change the default paging group that the handset sends to when the PTT key is pressed and held.

Important: Changing the default paging group from the handset will override the PageGroupPushToTalk setting on the Rove base station. Resetting the settings on the handset will revert the settings on the handset to match PageGroupPushToTalk.

Procedure

  1. On the phone’s local interface, go to Menu > Settings > Default Group.
  2. Use the up and down arrow keys to highlight the desired default paging group.
  3. Press Select to save your changes

 

Paging a group

 

Send an outgoing group page by selecting a group from the menu.

Procedure

  1. On the phone’s idle screen, select the Speaker key.
  2. Scroll and highlight the desired group.
  3. Press Call and wait a few seconds.

    Your phone sends a preamble.

  4. Begin speaking.
  5. Press the End key when you have finished your message.

Send a page using the PTT action

 

Send an outgoing group page by selecting a group from the menu and using the PTT key to transmit.

Procedure

  1. Select the Speaker key.
  2. Scroll and highlight the desired group.
  3. Do one of the following:

    • On the Poly Rove 20 handset, press and hold the center navigation button.

    • On the Poly Rove 30 and Poly Rove 40 handsets, press and hold the Mute button.

  4. Begin speaking.
  5. Release the PTT button when you have finished speaking.

Group paging and PTT parameters

 

Use the following parameters to configure group paging and Push-To-Talk (PTT) settings.

 

Multicast group paging parameters

 

Use the parameters in the following list to configure multicast group paging.

Note: Administrators must enable paging and PTT before users can subscribe to a page group.

 

    Enable
  • Enables multicast group paging.
  • Default: False

    MulticastAddress
  • The valid IPv4 address is used for all page groups.
  • Default: 224.0.1.116

    MulticastPort
  • Port used for all page groups.
  • Default: 5001

    TTL
  • TTL value of outgoing (multicast) RTP packets.
  • Value range: 1 to 255
  • Default: 2

 

    AudioCodec
  • Audio codec to use for outgoing pages.
  • Default: G722
  • G711U

Group name parameters

 

Use the parameters in the following list to configure the group name settings.

GroupName

A user-friendly name to label the group.

String (maximum 19 characters)

Default:

  • Group1 (for Page Group 1)

  • Group2 (for Page Group 2)

  • Group3 (for Page Group 3)

  • Group4 (for Page Group 4)

  • Group5 (for Page Group 5)

  • Group6 (for Page Group 6)

  • Priority (for Page Group 7)

  • Emergency (for Page Group 😎

PolycastGroup

The Poly UC Software multicast paging group channel to use.

Value range: 1 to 25

Default:

  • 1 (for Page Group 1)

  • 2 (for Page Group 2)

  • 3 (for Page Group 3)

  • 4 (for Page Group 4)

  • 5 (for Page Group 5)

  • 6 (for Page Group 6)

  • 24 (for Page Group 7)

  • 25 (for Page Group 😎

PageTimeout

Limit of the outbound page duration (in number of minutes) to avoid accidentally jamming the page group channel.

Value range: 0 to 31

Default: 0

 

Handset page group and PTT parameters

 

Use the parameters in the following list to configure the handset page group and PTT settings.

PageGroupPushToTalk

Page group used when the PTT button is pressed.

Default: 1

PageGroupTransmitMask

The page groups that the handset is allowed to broadcast to. The most significant bit in the mask represents group 8 and the least significant bit in the mask represents group 1.

For example, if the handset is allowed to transmit to all groups, then the bit mask value is 11111111, which is calculated to a decimal value of 255.

Default: 255

PageGroupReceiveMask

Page groups that the handset is allowed to receive pages on. The most significant bit in the mask represents group 8, and the least significant bit in the mask represents group 1.

For example, if the handset is allowed to transmit to all groups, then the bit mask value is 11111111, which is calculated to a decimal value of 255.

Default: 255

 

Limitations for group paging

 

The following limitations apply when using group paging on Poly Rove phones.

  • Enabling group paging on Poly Rove decreases the number of concurrent calls allowed on the system by two.

  • Only one group page can be active on the Poly Rove system at one time. If there is an active page and a user tries to send a group page from a Poly Rove handset, the handset displays an error.

  • There are 25 UC Software page groups users can subscribe to, but you can configure only up to 8 page groups on Poly Rove. By default, the phone selects page groups 1 to 6, as well as the priority (24) and emergency (25) groups.

    While Poly Rove can send and receive group pages for the priority and emergency groups, there is no special handling of those groups. Poly Rove treats them the same as the other page groups.

  • The audio codec used for group paging must match all other devices and phones on the network that support the multicast group paging feature.

    For example, if you configure poly Rove to use G722 for the group paging codec, then you must also configure all UCS phones on the network to use the G722 codec for multicast group paging.

  • Group pages are only broadcast on handsets registered to base stations located on the group page originator's broadcast subnet, unless Poly Rove B2 and Poly Rove B4 systems are comprised of base stations on multiple network subnets, however, group pages will only be broadcast on handsets registered to base stations that are located on the group page originator's broadcast subnet unless the local network switching infrastructure permits cross-subnet multicast traffic.

  • The caller ID used in outgoing group pages from Poly Rove use the SIP display name (X_DisplayNumber) configured for the lowest SPx service that the handset is assigned to. If there is no configured SIP display name, then the phone uses the IPEI of the handset sending the group page as the caller ID.

HTTPS required for the system web interface

 

HTTPS is now required for accessing the Poly Rove system web interface.

 

SHA-256 support
 

The SHA-256 digest algorithm is now available for use in validating custom Root CA certificate checksums, for HTTP digest authentication to provisioning services, and for authentication when accessing the Poly Rove system's web interface.

  • Configure certificate checksums using SHA-256

    Configure SHA-256 in the checksum options in the system web interface

  • SHA-256 for provisioning services

    The Poly Rove HTTP client can now use SHA-256 and SHA-256-sess digest algorithms when authenticating to HTTP provisioning services for configuration files and software as defined in RFC 7616. These new algorithms are on by default and are available in addition to MD5 for backwards compatibility. Poly Rove systems will use the digest method provided by the topmost authentication challenge header in an HTTP GET response.

  • Configure SHA-256 digest authentication for the system web interface

    Optionally configure the system web interface to require SHA-256 digest access authentication for login (RFC 7616).

Configure certificate checksums using SHA-256

 

Configure SHA-256 in the checksum options in the system web interface

Procedure

  1. In the system web interface, go to System Management > Device Admin.
  2. Under Platform CA N, enter the URL of the root CA certificate to download in the Value column for the DownloadURL parameter.
  3. Optional: If you want the device to validate the integrity of the certificate file, enter the MD5 or SHA-256 checksum of the certificate file in the Value column.
  4. Select Submit.

SHA-256 for provisioning services

 

The Poly Rove HTTP client can now use SHA-256 and SHA-256-sess digest algorithms when authenticating to HTTP provisioning services for configuration files and software as defined in RFC 7616. These new algorithms are on by default and are available in addition to MD5 for backwards compatibility. Poly Rove systems will use the digest method provided by the topmost authentication challenge header in an HTTP GET response.

 

Configure SHA-256 digest authentication for the system web interface

 

Optionally configure the system web interface to require SHA-256 digest access authentication for login (RFC 7616).

For backwards compatibility with services unable to support SHA-256, MD5 remains available. You can disable it using new configuration parameters to specify which digest algorithm is permitted.

Procedure

  1. In the system web interface, go to System Management > Device Admin > Web Server.
  2. Under Web Server, select either MD5 or SHA-256 as the value for AuthDigestAlgorithm in the Value column.
  3. Select Submit.

System web interface login protection

 

You can now configure the system web interface to lock out a user after a set number of failed login attempts in a specific time frame. This feature can protect the interface from a brute force attack.

 

Web protection parameters

 

Configure the web protection feature using the following settings.

LockOut

Enables or disables the web server lock-out feature.

1 (default) - Enabled

0 - Disabled

LockOutPeriod

The period of time the user is locked out of the web server.

60 to 300 seconds

60 (default)

LockOutInvalidAttempts

Specifies the maximum number of failed login attempts after which the user is locked out from the web server.

3 to 20

5 (default)

LockOutInvalidAttemptsDuration

After a user reaches the maximum failed login attempts within this time duration, the user is locked out from the web server.

60 to 300 seconds

60 (default)

 

Minimum TLS version now defaults to TLS 1.2

 

As of this software release, fallback to deprecated TLS versions is disabled.

TLS 1.2 is now the minimum version permitted for fallback when connecting to external services in order to adhere to industry security recommendations by the IETF and NIST.

TLS Platform Profile 1 now defaults to TLS v1.2 and is accessible from the system web interface at System Management > Device Admin > TLSPlatform Profile 1 > Protocol.

For services that require deprecated TLS versions, TLSv1.0 and TLSv1.1 remain available as configuration options for backwards compatibility.

 

Resolved issues in Poly Rove 8.0.12

 

Review the resolved issues in this release.

Note: These release notes don’t provide a complete listing of all resolved issues that are included in the software. User Experience updates, performance fixes, and enhancements might 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.
Table 1. Resolved issues

Category

Issue ID

Description

Audio

O-832

The caller can occasionally hear a brief click or burst of static-like noise immediately after a call connects.

Audio

O-807

In cases where a Poly Rove system is configured to prioritize wideband codecs (such as Opus or G.722) over narrowband codecs, for the first call that routes through services where early-media codec negotiation takes place in the SIP 180 or 183 responses to choose G.711u-law, G.711a-law, or G.726, two-way audio is missing from the call.

Calling

O-820

If a call is put on hold from Poly Rove and the held party blind transfers the call to a transfer destination that supports audio codecs that are different from the audio codec used in the original call, then the call is disconnected when Poly Rove resumes the call.

Calling

O-340

When Poly Rove receives a negative or rejected request from a BroadSoft centralized conference call request, the initial call fails.

Interoperability

O-798

Poly Rove uses the wrong Dialog IDs when retrieving a parked call using the INVITE+Replaces method.

Logs

O-846

Syslog and SIP log exports fail from the system web interface when the Poly Rove web server is configured for HTTPS (port 443).

Network

O-848

Web server pages are slow to load over HTTPS with certain cipher suites.

Network

O-824

After an extended network or service provider outage, Poly Rove tries to failover to the SIP service using only the UDP transport. This causes registration failures when the service provider doesn’t offer UDP transport for SIP.

Software Updates

O-774

If the Broadworks XSI credentials are configured manually from the system web interface and the base station is upgraded from a release prior to 8.0.7 to 8.0.7 or later, incorrect XSI credentials are used and the handset can’t access the Broadworks directory.

User interface

O-819

Poly Rove can't parse the contact directory if the contact is missing the <telephone> tag or if there is a blank entry in the directory list.

 

 

Release History


This section lists the release history of Poly Rove.

 

Release History

 

Release             Release Date        Features

8.0.12

Sep 2025
  • Minimum TLS 1.2
  • Web Protection
  • SHA-256
  • Group Paging

8.0.11

April 2025
  • Installing custom certificates via PEM
  • Updated Root CA Certificate list
  • Extended character length for SIP AuthUserName parameter
  • Call park pickup enhancements

8.0.10

July 2024
  • Support for Backup Proxy Server
  • Support for multipart/mixed content type in the SIP INVITE
  • New parameter to control expiry for SIP SUBSCRIBE requests
  • Other Fixes and enhancements

8.0.9

Mar 2024
  • Zoom Phone aim park call support

8.0.8

Dec 2023
  • Additional function types for line keys
  • New TLS platform parameter
  • Support for mediasec
  • Removed support for SECP192K1 and SECP192R1

8.0.7

Aug 2023

•     Enhanced PTT  

•     Strict Line Seize

•     Time-Limited Search on Directory Server 

•     Extended Character Length for BroadWorks Fields

8.0.6

May 2023

•     Support for XML App Development

•     Japanese Language Support

8.0.5

April 2023

•     Single-Cell Base Station

•     Wireless Handset and SIP Registrations

•     DECT Repeaters

•     Programmable Line Keys

•     Improved Battery Life

•     3.5 mm Headset Port

•     Enhanced Call Parking

8.0.5

February 2023

•     Handset Sanitized Mode

•     New Ringtones Added

•     Option to Provide Transport Attribute in lowercase

•     New Option to Adjust Handset Volume

•     New Name – PVOS-L

8.0.3

July 2022

•     Phone Line Status Display on the Home Screen

•     Configure E911/HELD in Poly Rove

•     Easy Registration for the Poly Rove B4 Base Station

•     Manual Designation of a Provisioning Primary Cell

8.0.2

January 2022

•     Request Configuration Files with a check-sync SIP NOTIFY Message

•     DTMF Enhancements

8.0.1

July 2021

•     Configure TLS Cipher Suite

•     Support for ITSP SIP User Agent Name

•     Removed X_LineName Parameter

•     Added Ability to Remove Handsets and Repeaters through Provisioning

•     New Device Maintenance Description

8.0.0

March 2021

•     Single/Dual-Cell and Multi-Cell Base Stations

•     Wireless Handset and SIP Registrations

•     DECT Repeaters

•     Antimicrobial Coating

•     Bluetooth Pairing

•     Programmable Emergency Button

•     Programmable Function Keys

•     UC Software Configuration 
0 Kudos
Was this article helpful? Yes No
Contributors
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.