[Software] Poly Edge E PVOS 8.6.0 Poly CCX and Trio C60 PVOS 9.5.0

SteffenBaierUK · ‎07-01-2026

Hello all,

HP Poly announces the 9.5.0 release of Poly Voice Software (PVOS) for Poly CCX Series phones and Poly Trio C60, and PVOS 8.6.0 for Edge E Phones

Poly Voice Software 9.5.0 & 8.6.0

Poly announces the 9.5.0 release of Poly Voice Software (PVOS) for CCX IP Series and the Trio C60 and 8.6.0 for Edge E Phones

Software version: Poly Voice Software 9.5.0 & Poly Voice Software 8.6.0

Release date: 06 2026

The build IDs are:

CCX IP Series: 9.5.0.1321
Trio C60: 9.5.0.1321
Edge E: 8.6.0.1321

For more information, review the [Link to RN on HP Support].

Important Information

- Customer Bulletin -
Posted to HP Support for each voice product

https://support.hp.com/us-en/document/ish_12619493-12619464-16

HP will be changing the Root CA Certificate and trust chain used for issuing the manufacturing installed certificate (MIC) on new Poly products in 2026, starting with Edge V. For existing products, TBD.

Take Action: We recommend all partners install this public root certificate as soon as convenient to minimize disruption on receiving new Poly products using the HP issuing chain. All products will eventually have this new Root CA

New Phone MAC address ranges change

B4:E2:5B:xx:xx:xx
B8:87:88:xx:xx:xx
AC:F4:66:xx:xx:xx

What's new

This release of Poly Voice Software (PVOS) 9.5.0/8.6.0 includes new features, feature improvements, and important field fixes.

Deprecation Warning:

EAP authentication methods removed in this release

This software release deprecates support for the EAP‑MD5, EAP-TTLS-NONE, EAP-PEAPv0-NONE, and EAP-PWD authentication methods used in 802.1X and Wi‑Fi connectivity.

These EAP-methods have been removed from the on screen and system web interfaces and and may no longer be selected for use. Phones already using these EAP methods at the time of upgrade will continue to operate using the deprecated EAP method, however, upon change to another method, they will no longer be selectable. Customers using these methods should transition to a supported and more secure authentication method prior to upgrading to ensure uninterrupted network access.

Enable ports for Link Layer Discovery Protocol advertisement

This release enables you to configure the ports for Link Layer Discovery Protocol (LLDP) advertisement using the parameter device.net.lldp.advertisement.port.

Enable/disable of LLDP transmission on the PC port
Addresses an issue reported by Zoom customers where the Zoom client was using the LLDP packet from the PC port to discover its network location

Maintains interoperability while giving admins granular control over LLDP behavior

device.net.lldp.advertisement.port.set - (boolean, 0 | 1) – Apply the value set in device.net.lldp.advertisement.port
device.net.lldp.advertisement.port - (enum, null | 0 or All | 1 or LAN) – Select port for LLDP advertisements

Network administrator password for remote access

This release includes a network administrator password for remote access to the administrator menu on the phone.

Previously, the administrator password was need ed for you to access the administrator menu on the phone locally or remotely.

When setting the administrator network password, the password must comply with the following criteria:

At least one uppercase letter
At least one lowercase letter
At least one numeric character
At least one special character

device.auth.networkAdminPassword – (string, 0 – 300 characters)
Password for network admin

sec.pwd.length.network – (integer, 8 – 300, default 12)
Minimum number of characters needed for the network admin password

sec.pwd.uppercase.network – (integer, 0 – 300, default 1)
Minimum number of uppercase characters needed for the network admin password

sec.pwd.lowercase.network – (integer, 0 – 300, default 1)
Minimum number of lowercase characters needed for the network admin password

sec.pwd.numeric.network – (integer, 0 – 300, default 1)
Minimum number of numeric characters needed for the network admin password

sec.pwd.specialcharacters.network – (integer, 0 – 300, default 1)
Minimum number of special characters needed for the network admin password

Note: Remember to include device.set="1" and device.auth.networkAdminPassword.set="1" parameters in the configuration file to apply the “device” parameter changes.

Open source licenses are available in the system web interface

Starting with this release, you can find a list of open source software in the system web interface.

The open source licenses are in the menu in the upper-right corner .

SIP enhancements

This release includes several SIP protocol enhancements focused on improving connection stability, retry behavior, and interoperability with service providers.

Key improvements include:

Standards-based retry handling for SIP subscriptions

Problem
- Phones kept retrying failed subscriptions too quickly causing signal storms in large deployments
- Specifically, an issue with service provider level deployments
What Changed
- Added smart retry backoff logic (waits longer after each failure)
- Applies to BLF and presence
Updated keepalive behavior for improved network resilience

Problem
- In large service provider networks that have multiple SIP servers and SBCs, each line registration can failover to different SBCs
- The current implementation on the phones is to register to one server or SBC, and not each one that the phone is registered to
What Changed
- Improved keepalive behavior to send keepalive packets to all SBCs that the phone is registered to

Enhanced support for Zoom Phone call forwarding features

<?xml version="1.0" encoding="UTF-8"?>
  <ForwardingEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
    <monitorCrossRefID></monitorCrossRefID>
    <device><notKnown/></device>
    <forwardingType>forwardImmediate</forwardingType>
    <forwardStatus>false</forwardStatus>
    <forwardTo> </forwardTo>
    <forwardingAlwaysSupport>false</forwardingAlwaysSupport>
    <forwardingAlwaysEditSupport>false</forwardingAlwaysEditSupport>
    <forwardingNoAnswerSupport>false</forwardingNoAnswerSupport>
    <forwardingBusySupport>false</forwardingBusySupport>
</ForwardingEvent>

Further improves the Zoom Phone call forward feature sync that was added in PVOS 8.5.0/9.4.0
Supports handling of a new signaling element in the “as-feature-event” SIP NOTIFY body – forwardingAlwaysEditSupport
If forwardingAlwaysEditSupport is set to false by Zoom Phone call server, the phone will set reg.x.serverFeatureControl.cf.readonly="1" in the SIP provisioning layer > This means that setting the parameter to a different value via the provision template will not override what is set from the SIP provisioning layer. It can be overridden if changed in the web UI, but it is not recommended that the administrator changes the parameter from the web UI – this will be considered as a misconfiguration.

No soft keys to edit, save or enable/disable

These changes improve device performance in environments with network instability, network address translation (NAT) traversal, and cloud-based SIP services.

Support for Fast Pair with HP Poly headsets

This release adds support for using Fast Pair on CCX phones to connect with Bluetooth enabled Poly headsets.

Applies to:

CCX 500, 505, CCX 600, CCX 700
Enables quick pairing between CCX phones and user devices (mobile/PC)
Reduces setup time by minimizing manual entry and steps
Guided on-device prompts for fast, intuitive pairing
Secure pairing flow using authenticated session/token exchange
Integrates with provisioning and user sign-in workflows

Support for VQMon separate interval reports

This release adds support for VQMon for separate interval reports for discrete periods along with cumulative reports.

VQMon switches between high-level call summaries and detailed, interval-based reporting. Administrators can now more quickly and easily identify when and where call quality issues happen.

New parameter:

voice.qualityMonitoring.collector.periodType

Values: Cumulative (default) or Discrete

When set to Cumulative, interval reports will describe quality metrics for increasingly cumulative periods of time with each new report being sent based on voice.qualityMonitoring.collector.period

When set to "Discrete", each interval period provides quality metrics for only the most recent period length defined by voice.qualityMonitoring.collector.period

Updates VQMon reporting to use the RFC6035-compliant interval-based reporting format

Moves from cumulative metrics (whole call) to discrete interval “chunks” during the call
Provides more granular, time-based quality visibility (e.g., where issues occurred in the call)
Aligns with standard SIP QoS reporting mechanisms used by collectors/analytics platforms

Trigger customizable actions on state changes

This release contains new parameters that allow administrators to trigger customizable actions depending on the state changes on the phone.

To support customer relationship management (CRM) systems, Poly Voice Software (PVOS) includes new parameters that trigger customizable actions on call state changes.

Turns the phone into an integrated workflow endpoint, enabling real-time automation and deep integration with enterprise systems.

Introduces an event-driven automation framework tied to call states (ringing, connected, disconnected, etc.)
Enables phones to trigger REST APIs (HTTP GET/POST with no web content) or execute EFK macros automatically (including EFK actions to display web content on the web browser)
Supports up to 20 configurable actions, with priority and delay control
Allows integration with CRM systems and web services (e.g., auto-launch customer info on incoming call)
Rich contextual data in triggers (phone details, timestamps)

Variable Name	Description	EFK URL	UriGet URL	UriPost URL
{phoneMac]	Phone MAC address	Yes	Yes	Yes (and in JSON body)
{phoneIP}	Phone IP address	Yes	Yes	Yes (and in JSON body)
{phoneModel}	Phone model	Yes	Yes*	Yes* (and in JSON body)
{eventTime}	Timestamp of the event	Yes	Yes	Yes (and in JSON body)
{remoteNumber}	Number of the far-end of the call	No	Yes	Yes (and in JSON body)
{remoteName}	Name of the far-end of the call	No	Yes*	Yes* (and in JSON body)
{isEmergencyCall}	Emergency call	No	Yes	Yes (and in JSON body)
{isDistressCall}	Distress call	No	Yes	Yes (and in JSON body)

Note: Caveats and Recommendations

If certain values have spaces, like {phoneModel} and {remoteName}, then the UriGet/UriPost action fails to execute due to malformed URL. The values encoded for these variables in the JSON body is ok.
Workaround: Do not use the variables in the URL. Extract them from the JSON body.
Recommend to add a 1 or 2-second delay to allow the phone to handle the call before trying to invoke the EFK action.

onCallAction.x.enabled - (boolean, 0 | 1) - Enable or disable the action
onCallAction.x.name - (string) - Name of action
onCallAction.x.onState - Call state trigger for action 
(enum – IncomingCallRinging | IncomingCallConnected | IncomingCallDisconnected | OutgoingCallRinging | OutgoingCallConnected | OutgoingCallDisconnected | OutgoingEmergencyCallConnected | OutgoingEmergencyCallDisconnected | OutgoingDistressCallConnected | OutgoingDistressCallDisconnected)
onCallAction.x.type - (enum – Efk | UriPost | UriGet) - Type of action to execute (EFK macro or HTTP request)
onCallAction.x.action - (string - URI or macro name) – Target HTTP POST/GET URI or EFK macro (must use !MacroName syntax) to execute
onCallAction.x.delay - (int, 0-10) - Delay (seconds) before executing the action
onCallAction.x.priority - (int, 0+) - Execution priority when multiple actions exist

Other related parameters (for EFK action):

efk.efklist.x.action.string - (string) – Web URL to display on the web browser
efk.efklist.x.status - (boolean, 0 | 1) – Enable or disable the EFK
efk.efklist.x.mname – (string) – Macro name for the EFK

Example Configurations and Behaviors:

onCallAction.1.enabled="1"
onCallAction.1.name="WebDisplayCallDetails"
onCallAction.1.onState="IncomingCallRinging"
onCallAction.1.type="Efk"
onCallAction.1.action="!WebDisplayCallDetailsMacro"
onCallAction.1.delay="1"
onCallAction.1.priority="1"
efk.efklist.49.action.string="http://192.168.2.15/ssawc/test.html?stationId=1203980-waegsdfaw-0920jads890h2w&phoneMac={phoneMac}&ip={phoneIP}&model={phoneModel}&time={eventTime}"
efk.efklist.49.status="1"
efk.efklist.49.mname="WebDisplayCallDetailsMacro"
onCallAction.3.enabled="0"
onCallAction.3.name="UriPostTest"
onCallAction.3.onState="IncomingCallRinging"
onCallAction.3.type="UriPost"
onCallAction.3.action="http://PlcmSpIp:[email protected].
2.15/test/request"
onCallAction.3.delay="3"
onCallAction.3.priority="2"

POST /test/request HTTP/1.1
Host: 192.168.2.15
User-Agent: Microbrowser/1.1 PolyEdge-Edge_E350-UA/8.6.0.1283
Type/Application
Accept: */*
Content-Type: application/json
Content-Length: 278
{"actionName": "UriPostTest", "actionOn": "0", "phoneMac": "4825671359c5",
"phoneIp": "192.168.33.112", "phoneModel": "Edge E350", "eventTime": "2026-
06-24T15:49:32-06:00", "isEmergencyCall": false, "isDistressCall": false,
"remoteNumber": "2551", "remoteName": "Made Up Name Go1"}

Users configure a primary line

This release adds the ability for users to designate a primary line for incoming and outgoing calls.

Users can select a preferred default line on the phone

Instead of relying on provisioning server
- Set by the user, no dependency on IT team
- Can also be set via configuration
```
up.primaryLine="<reg-index>"
```
Ensures outgoing calls default to the user’s chosen line
If multiple lines ring, the phone prioritizes the selected primary line
Users can still manually select other lines when needed. User must select the line to answer incoming calls on other (non-primary) lines.
Default behavior unchanged if no primary line is selected.

Wi-Fi configuration on startup

This release enables you to configure Wi-Fi settings at startup on CCX and Trio C60 phones without a wired network connection.

Applies to: CCX 505, CCX 600, CCX 700 and Trio C60 (feature parity for Edge OOB experience)

Key Features

No Ethernet required for initial setup
Wi‑Fi selection available during OOB flow
Enables faster deployment for remote users
Reduces dependency on pre-provisioned networks

Basic Workflow

Boot → Device powers on into OOB flow
Wi‑Fi Selection → User selects network (no Ethernet required)
Provisioning → Device pulls config from server
Sign‑In / Registration → User authenticates (Teams / SIP / etc.)

Zoom server configuration takes priority

Zoom Phone call server configuration takes priority over the configuration parameter of the phone for the call forward sync parameters.

There are parameters that you can set on the phone to control whether call forward sync for the phone or specific lines are read-only. The Zoom Phone call server configuration takes priority over these parameters that administrators configure on the phone or the lines.

Updated Libraries & Agents

c-ares 1.34.5 library is now the current version on Poly phones
c-ares is the DNS resolver library used by Poly phone software (app + platform) to resolve hostnames into IP addresses
wpa_supplicant 2.11 and 2.12 now supported
wpa_supplicant is the Wi‑Fi / 802.1X authentication service running on Edge E phone’s Linux OS

Updates to Microsoft apps

The following information includes the updates for the Microsoft apps for the Poly Voice Software (PVOS) 9.5.0 release.

The following table includes the updates to the Microsoft apps for this release.

**Microsoft APK Versions**
APK Name	New APK Version
Microsoft Teams	1449/1.0.94.2026047602
Microsoft Intune APK	25.02.1
Microsoft Authenticator APK	6.2601.189
Microsoft Admin Agent APK	1.0.0.202604060507.product

Resolved issues in PVOS 9.5.0 / 8.6.0

Review the list of resolved issues in the Poly Voice Software (PVOS) 9.5.0 release.

Note: These release notes don’t provide a complete listing of all resolved issues included in the software. User experience updates, performance fixes, and enhancements may not be included. In addition, the information in these release notes is as-is at the time of release and is subject to change without notice.

Resolved issues for PVOS 9.5.0
Category	Issue ID	Product	Description
Network	VOICE-85589	CCX and Poly Trio C60	On CCX phones and Trio C60 using IPv6 SLAAC, outbound SIP calls can fail while inbound calls still work.
Network	VOICE-85593	CCX	On phones using dual-stack networking with IPv4 preferred, calls can connect with no audio when SIP registration uses IPv6 and RTP uses IPv4.
Partner Applications	VOICE-87212	CCX 350	On CCX 350 phones using Microsoft Teams, the phone may reboot while idle or during a call.
Partner Applications	VOICE-87167	CCX 600 and CCX 700	On CCX 600 and CCX 700 phones using BroadWorks server-side call recording, the Start softkey doesn’t appear when more than one call is active.
Partner Applications	VOICE-86782	CCX	On CCX phones using Zoom multi-party conference, the Dialpad softkey doesn’t appear during the conference, which prevents Dual-Tone Multi-Frequency (DTMF) entry.
Partner Applications	VOICE-86589	CCX and Trio C60	On phones using Zoom Phone, redirected calls can omit original call information on the phone screen when Zoom sends unsupported X-Redirect-Info header values.
Peripherals	VOICE-87681	CCX 400 and CCX 350	On phones with an Algo 2507 Ring Detector and Algo 8148 Flasher connected, the headset ringer volume resets after reboot and the ring detector doesn’t activate.
Peripherals	VOICE-87306	CCX 500 and CCX 505	On phones running PVOS 9.0.0 or later, receive audio crackles when using a Poly BT700-C USB dongle with Poly Voyager Focus 2 headsets on the USB-C port.
Peripherals	VOICE-86757	CCX 505	On phones paired with a Poly Voyager Focus 2 headset, the call button doesn’t end the active call during call waiting.
Provisioning	VOICE-87689	CCX 500	On CCX 500 phones registered to BroadWorks Call Center, incoming call center calls show a Back to call banner instead of the full incoming call screen.
Provisioning	VOICE-87655	CCX 505, CCX 600, and Trio C60 phones with Microsoft Teams	On phones with Microsoft Teams, Wi‑Fi settings remain available to users after administrators disable Wi‑Fi in the configuration.
System Update	VOICE-87889	CCX and Trio C60	On the CCX and Trio C60 phones in Microsoft Teams mode with static IP addressing after updating to 9.4.0.1491, the phone can show as offline in Teams Admin Center and can't place outgoing calls.
System Update	VOICE-86669	CCX and Trio C60	On phones with STIR/SHAKEN enabled, memory usage increases during call processing.
System Update	VOICE-86680	CCX and Trio C60	On phones with STIR/SHAKEN enabled and URL dialing disabled, the incoming caller ID can display the verstat string instead of the phone number.

Known issues for PVOS 9.5.0 / 8.6.0

Review the new known issues in the Poly Voice Software (PVOS) 9.5.0 release.

Note: These release notes don’t offer a complete listing of all known issues for the software. Issues not expected to affect significantly customers with standard voice and video conferencing environments may not be included. In addition, the information in these release notes is offered as-is at the time of release and is subject to change without notice.

This known issues table only includes issues found during this release. For known issues in the previous release, see Known Issues in .

Known issues for PVOS 9.5.0
Category	Issue ID	Product	Description	Workaround
Configuration	VOICE-88441	Trio C60	The system web interface shows an incorrect WPAD status even though WPAD is working correctly.	Verify WPAD operation through actual proxy behavior instead of the system web interface status.
Configuration	VOICE-88313	Trio C60	The system web interface displays an incorrect maximum value for the `call.localConference.maxParticipants` parameter.	Configure the parameter through provisioning or use the platform-supported value instead of relying on the system web inteface to show the limit.
Device interface	VOICE-87541	CCX	On CCX devices, the Call Forward menu may be inaccessible, preventing users from viewing or modifying call forwarding settings.

Previous releases

Edge E, CCX, Trio C60 combined:

Older PVOS 8.5.1 & PVOS 9.4.1 release >here<
Older PVOS 8.5.0 & PVOS 9.4.0 release >here<
Older PVOS 8.4.1 & PVOS 9.3.1 release >here<
Older PVOS 8.4.0 & PVOS 9.3.0 release >here<
Older PVOS 8.3.1 release >here< & PVOS 9.2.1 release >here<
Older PVOS 8.3.0 release >here< & PVOS 9.2.0 release >here<

CCX or Trio C60 Standalone

Older 9.2.1 release >here<
Older 9.2.0 release >here<
Older 9.1.1 release >here<
Older 9.1.0 release >here<
Older 9.0.1 release >here<
Older 9.0.0 release >here<

Edge E, CCX, Trio C60 & Trio 8300 combined:

Older 8.3.1 release >here<
Older 8.3.0 release >here<
Older 8.2.3 release >here<
Older 8.2.2 release >here<
Older 8.2.1 release >here<
Older 8.2.0 release >here<
Older 8.1.8 release >here<
Older 8.1.7 release >here<
Older 8.1.6 release >here<
Older 8.1.5 release >here<
Older 8.1.4 release >here<
Older 8.1.3 release >here<
Older 8.1.2 release >here<
Older 8.1.1 Release >here<
Older 8.1.0 Release >here<
Older 8.0.2 Release >here<
Older 8.0.1 Release >here<
Older 8.0.0 Release >here<
Older 7.3.2 Release >here<
Older 7.3.1 Release >here<

CCX & Trio combined

Trio 8800 & Trio 8500 only 7.2.8 Release >here<
Older 7.2.7 Release >here<
Older 7.2.6 Release >here<
Older 7.2.5 Release >here<
Older 7.2.4 Release >here<
Older 7.2.3 Release >here<
Older 7.2.2 Rev B Release >here<
Older 7.2.1 Rev B Release >here<
Older 7.2.1 Release >here<
Older 7.1.4 Release >here<
Older 7.1.1 Release >here<
Older 7.1.0 Release >here<
Older 7.0.3 Release >here<
Older 7.0.2 Release >here<
Older 7.0.1 Release >here<
Older 7.0.0 Release >here<

CCX:

Older 6.2.23.0202 Release >here<
Older 6.2.22.0185 Release >here<
Older 6.2.21.1198 Release >here<

Trio:

Older 5.9.5 Rev AB => here <=
Older 5.9.5 Rev AA => here <=
Older 5.9.4 Rev AB => here <=
Older 5.9.4 Rev AA => here <=
Older 5.9.3 Rev AB => here <=
Older 5.9.3 Rev AA => here <=
Older 5.9.2 Rev AB => here <=
Older 5.9.2 Rev AA => here <=
Older 5.9.1 Rev AC => here <=
Older 5.9.1.10906 Rev AB => here <=
Older 5.9.1.10419 Rev AA => here <=
Older 5.9.0.11421 Rev AD => here <=