Documented specifications
HP Poly · Listed by Microsoft at review with Android 12 certification ending August 15, 2028; certification, application support, firmware publication, exact SKU availability and remaining manufacturer support can change.
| Specification | Documented value |
|---|---|
| Current Teams certification | Android 12; certification reference firmware 9.0.0.10315; listed certification end date August 15, 2028 Source ↗ |
| Current Microsoft firmware table | 9.5.1.0067 (AOSP), released September 15, 2026, was the published CCX 350/400/500/505/600 and Trio C60 line at review; this is not evidence of the installed version Source ↗ |
| Display | 5-inch multi-touch color LCD Source ↗ |
| Network | Two Gigabit Ethernet RJ-45 ports Source ↗ |
| Headset and USB | RJ-9 headset port, electronic hook switch support and one USB Type-A port Source ↗ |
| Documented codecs | G.711 A-law and mu-law, G.722, G.722.1, G.729AB, iLBC and Opus Source ↗ |
| Documented security mechanisms | 802.1X, SRTP, digest authentication, encrypted configuration files, HTTPS provisioning, TLS and AES-256 SRTP are listed; deployment is not established Source ↗ |
| Mounting | Optional wall-mount hardware is listed separately Source ↗ |
Unlisted fields remain unverified. Platform compatibility and remaining support life require confirmation for the exact ordered model.
Match the exact mode to the workload
HP markets this CCX 400 order as a Microsoft Teams phone. Start with the required Teams workload and exact part number, then confirm the supplied software mode and administrator documentation. HP's product specification also lists SIP registrations and SIP-related protocols; that does not establish that the Teams-configured unit can register to an arbitrary SIP PBX or that mode conversion is included.
For a personal desk, validate assigned-user sign-in and policy. For a lobby, break room or other shared space, use the current common-area resource-account and Teams Shared Space licensing workflow where applicable. Do not reuse a personal identity merely to make the screen activate.
Treat certification as dated acceptance evidence
At review, Microsoft's Teams phone table lists the Poly CCX 400 on Android 12 with certification reference firmware 9.0.0.10315 and an August 15, 2028 certification end date. The same page's current firmware table lists 9.5.1.0067 (AOSP), released September 15, 2026, for a group that includes the CCX 400. The reference certification build, latest published build and installed build are three different facts.
Capture all three at commissioning. Recheck the live list before purchase or upgrade because Microsoft can revise certification and firmware tables, and because a later application or operating-system policy may change the usable lifecycle.
Validate network, power and physical interfaces
HP lists a five-inch multi-touch color display, two Gigabit Ethernet ports, an RJ-9 headset interface, electronic hook switch support and one USB Type-A port. Confirm the actual package, PoE source, switch budget, VLAN, DHCP, DNS, time and tenant reachability before assigning users. Connector presence does not establish accessory compatibility.
Pilot the approved headset and any wall kit with the ordered device. Test cold boot and recovery after switch, DHCP and service interruption. Record the switch port, phone serial and part number so that a later firmware or certification question can be tied to the physical unit.
Configure identity, policy and calling as one change
Assign the account type, usage location, licence and phone policy before sign-in. If PSTN calling is required, provision the intended connection and number and validate outbound, inbound and emergency behavior from the installed location. For a common-area account, verify CommonAreaPhoneSignIn, Conditional Access behavior, directory exposure, hot-desking policy and sign-out recovery.
Microsoft notes that policy propagation can take time and may require sign-out and sign-in. Preserve the baseline before changing several tenant controls at once, and do not use successful registration or sign-in as proof that call queues, caller identity or emergency routing work.
Interpret security and codec lists narrowly
HP lists codecs including G.711, G.722, G.729AB, iLBC and Opus, plus mechanisms including 802.1X, TLS, SRTP, HTTPS provisioning and encrypted configuration files. These are documented capabilities, not evidence that a tenant enables them, that every call negotiates a named codec, or that the deployed network validates certificates and protected media correctly.
Inspect the running phone, tenant and network rather than copying the product list into an acceptance record. Keep credentials out of screenshots and captures, apply least-privilege administration and test certificate renewal and device replacement through the supported management path.
Run a bounded acceptance test
On the installed unit, verify sign-in, directory scope, inbound and outbound calls, hold, transfer, mute, voicemail indication, headset control, speaker behavior, policy restrictions, reboot recovery and the required shared-space workflow. Record installed firmware, Teams and Microsoft application versions with the result.
No CCX 400, Teams tenant, PBX, PSTN service, accessory, network or call was tested for this reference. The cited sources do not establish price, stock, accessory inclusion, audio quality, local compatibility or remaining support beyond the dated statements reproduced here.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Microsoft Teams certified hardware and current firmware: Poly CCX 400 ↗
- HP Poly CCX 400 Business Media Phone for Microsoft Teams product specification ↗
- Microsoft: set up common-area phones ↗
- Microsoft: plan Teams phone deployment ↗
- Microsoft Teams Shared Space licensing ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.