VoIP.infoThe independent guide to business communications.
VoIP.info Troubleshooting

Poly Trio C60 SIP, Teams, USB, calendar or room audio fails

Find the first mismatch across exact variant, base profile, call application, identity, network, power, provisioning, calendar, host selection, expansion topology and installed PVOS.

Reviewed 2026-10-24Current HP product, exact-variant data sheets, Trio C60 administration and user guides, support library and PVOS 9.5.x release record were reviewed October 24, 2026. HP lists Trio C60 build 9.5.1.0067 with an August 2026 release date, but a release record is not proof of the installed image, provider or tenant approval, completed update, resolved incident or effective feature. Exact product number, full-radio or no-radio hardware, base profile, active call application, OpenSIP registration, Teams sign-in, USB or Bluetooth host, room-system pairing, calendar account, network path, power path, provisioning owner, installed firmware, signaling and media remain separate evidence. No conference phone, label, radio, switch, PoE source, USB host, Bluetooth device, room system, expansion microphone, daisy chain, calendar account, tenant, SIP account, PBX, certificate, configuration, packet, call, meeting, media stream, emergency workflow, price, inventory, availability, compatibility, certification result, support entitlement or vendor response was inspected or testedIntermediateDocumentation based · not lab tested

Freeze the exact unit, mode and first failed workflow

Record product number, full-radio or no-radio hardware, MAC address, installed PVOS, base profile, active call application, power source, network interface, attached hosts and microphones, account or tenant owner, time and the first failed step. Redact credentials, meeting links, tokens, phone numbers, certificates and packet payloads.

Preserve state before changing profiles, resetting the phone or replacing firmware.

Stop at a variant or application mismatch

Confirm whether the unit actually contains Bluetooth and Wi-Fi and whether it is running Generic OpenSIP, Microsoft Teams, USB audio or a paired room workflow. A no-radio model cannot gain missing hardware from configuration, and an authenticated Teams app does not prove an OpenSIP line.

Reproduce the symptom in only the intended application before crossing modes.

Trace power, network, provisioning and identity in order

Prove 802.3at input, link, VLAN or authorized SSID, address, DNS, time, provisioning request, response, apply event and effective base profile. Then inspect the exact OpenSIP registration, Teams sign-in or room-system pairing used by the failed attempt.

Reachability, configuration download, registration and completed call remain separate checkpoints.

Separate calendar discovery from call or meeting completion

Record calendar account ownership, synchronization time, meeting identity, displayed join target and the request launched by one-touch join. A visible event does not prove current credentials, tenant policy, a successful join or working media.

Preserve the response and resulting session before changing the calendar source.

Follow audio through the selected owner and topology

Identify whether Trio C60, a USB computer, Bluetooth device, external bridge or paired room system owns signaling and media. Inventory the selected microphone and speaker, mute state, expansion microphones, daisy-chain order, SDP or application media state and packets in both directions.

A connected host, lit microphone or answered call does not prove the intended capture and playback path.

Retest under the approved PVOS lifecycle

HP lists PVOS 9.5.1 build 9.5.1.0067 released August 2026. Preserve current and target builds, provider or tenant approval, artifact identity, backup, certificates, pilot and rollback. After one authorized correction, repeat the original SIP, Teams, USB, calendar or audio workflow.

No device or live workflow was tested for this diagnostic.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Device reference · Current HP product, exact-variant data sheets, Trio C60 administration and user guides, support library and PVOS 9.5.x release record were reviewed October 24, 2026. HP lists Trio C60 build 9.5.1.0067 with an August 2026 release date, but a release record is not proof of the installed image, provider or tenant approval, completed update, resolved incident or effective feature. Exact product number, full-radio or no-radio hardware, base profile, active call application, OpenSIP registration, Teams sign-in, USB or Bluetooth host, room-system pairing, calendar account, network path, power path, provisioning owner, installed firmware, signaling and media remain separate evidence. No conference phone, label, radio, switch, PoE source, USB host, Bluetooth device, room system, expansion microphone, daisy chain, calendar account, tenant, SIP account, PBX, certificate, configuration, packet, call, meeting, media stream, emergency workflow, price, inventory, availability, compatibility, certification result, support entitlement or vendor response was inspected or tested

HP Poly Trio C60: SIP, Teams, radio, USB and PVOS evidence

Separate exact radio variant, base profile, three OpenSIP registrations, Teams, USB or Bluetooth audio, calendar state, daisy chaining and installed PVOS.

IP conference phone and room-audio endpoint
HP maintains current product, support, guide and PVOS release surfaces. Those records do not establish local inventory, regional orderability, remaining support period, tenant approval, interoperability or the build installed on a particular unit.

Read guide →
Hub

HP Poly phones

Separate desk, cordless and room devices, then verify the exact platform and firmware combination.

Explore topic →
Buying guide

Conference phones and room audio

Choose by room acoustics, participant placement and meeting workflow.

Read guide →
Guide

Planning VoIP for conference rooms

Match the room, microphones and joining workflow to the people who will use them.

Read guide →
Device category · Current first-party HP Poly Sync, Yealink SP96 and Jabra Speak2 75 product and technical documentation reviewed September 28, 2026; no speakerphone, host, application, account, meeting, room, wireless path, battery or call tested

USB and Bluetooth speakerphones

Choose host-connected room audio by application ownership, connection path, room acoustics, privacy, power and repeatable acceptance rather than pairing or a platform badge alone.

Read guide →
Hub · Vendor-neutral endpoint workflow plus Acrobits Cloud Softphone platform provisioning documentation reviewed October 8, 2026; exact parameters and precedence remain product-, service- and deployment-specific and no device or application was tested

Phone provisioning: repeatable endpoint deployment

Build a controlled path from a newly connected phone to the right identity, firmware and calling policy.

Explore topic →
Guide · Vendor-neutral workflow; exact parameters and precedence depend on model and firmware

Phone firmware deployment and rollback planning

Upgrade a mixed endpoint estate without assuming every model or intermediate release behaves alike.

Read guide →
Guide

PoE for IP phones

Check power standard, port capability, aggregate budget and outage behavior before selecting a switch.

Read guide →
Guide

Voice VLANs

Separate phone traffic operationally while keeping routing, security and QoS responsibilities explicit.

Read guide →
Hub

VoIP security

Reduce PBX exposure, constrain calling permissions and prepare for accountable recovery.

Explore topic →
Guide · FreePBX 17 · Debian 12; Sangoma field reference is explicitly labelled PBX GUI version 13, reviewed September 30, 2026

Register an IP phone with FreePBX: contact and call evidence

Map registrar, SIP identity, authentication and transport without treating a registration indicator as completed-call evidence.

Read guide →
Troubleshooting · RFC 3261 with current Asterisk PJSIP documentation; Asterisk 22 LTS and FreePBX 17 deployment context; no live test

SIP phone will not register: locate the failed evidence state

Separate local account state, REGISTER transport, endpoint identity, digest exchange, AoR binding and contact renewal.

Read guide →
Troubleshooting · Current Sangoma End Point Manager administration, supported-device, basefile, firmware and support-scope documentation reviewed October 1, 2026; no PBX, module, phone, file, credential, firmware or provisioning exchange was inspected or tested

Phone provisioning succeeds but settings stay wrong

Trace device identity, template ownership, generated artifacts, transport, parsing, activation and later overwrite without treating one successful download as complete provisioning.

Read guide →
Troubleshooting · Asterisk 22 LTS · FreePBX 17 / Debian 12 checks

One-way VoIP audio

Trace the missing direction from advertised media address to receiving endpoint.

Read guide →
Troubleshooting · Asterisk 22 LTS · FreePBX 17 / Debian 12 checks

VoIP call connects but has no audio

Separate endpoint audio selection from a media path that fails in both directions.

Read guide →