Documented specifications
AudioCodes · AudioCodes maintained a live product page and version 3.1 documentation at review; Microsoft listed Android 13 certification through August 15, 2028. The phone and G2 expansion module have separate certification records; software, availability and support can change independently.
| Specification | Documented value |
|---|---|
| Current Teams certification | Android 13; certification reference firmware 3.1.20; listed certification end date August 15, 2028 Source ↗ |
| Current Microsoft public-cloud firmware | 3.1.226 (AOSP), released September 10, 2026; the published bundle also identifies Teams, Intune, Authenticator and Admin Agent versions, but does not prove one phone installed them Source ↗ |
| Platform and display | MDEP-based Android 13 phone with a 5-inch colour touch screen Source ↗ |
| Action input | Dedicated programmable action button; configuration does not by itself prove an emergency route or completed call Source ↗ |
| Expansion module | Optional multi-purpose 5-inch G2 expansion module with its own certification lifecycle Source ↗ |
| Microphone control | Hardware microphone-off control is documented; verify physical and software state without treating it as end-to-end privacy proof Source ↗ |
| Power and management | PoE or external power plus AudioCodes Device Manager are documented; confirm the exact power design and management ownership Source ↗ |
Unlisted fields remain unverified. Platform compatibility and remaining support life require confirmation for the exact ordered model.
Separate platform, certification and running bundle
AudioCodes identifies the C456HD as an Android 13 MDEP phone. Microsoft listed Android 13 certification with reference firmware 3.1.20 through August 15, 2028, then separately published 3.1.226 (AOSP) on September 10, 2026. These records describe a platform, a certification baseline and a release line—not the installed or tenant-approved state of one unit.
Capture Android, firmware, Teams client, Intune, Authenticator and Admin Agent versions from both the phone and management plane. A certified model can still have an incomplete enrollment, stale bundle, missing licence or unsuitable policy.
Keep the programmable action button inside the emergency design
The programmable action button is an input. Assigning a destination does not prove dial-plan normalization, caller identity, dispatchable location, notification, carrier eligibility or a completed emergency call. Document the intended action, tenant policy, PSTN route, location source, expected screen state and failure fallback.
Use only provider-approved validation; never create an unplanned live emergency call. Preserve configuration and test evidence, and maintain an independent emergency path if the device, tenant, network or power path is unavailable.
Treat hardware microphone off as one privacy control
AudioCodes documents a hardware microphone-off control. Verify how the physical control, on-screen state, call state and restart behavior align, but do not represent it as proof that no other sensor, application path or administrative change exists. MDEP and Android certification likewise do not establish the tenant security posture.
Document the user-visible state, management restrictions, update policy, physical access and incident process. Test with authorized participants and avoid recording sensitive speech merely to demonstrate the control.
Track the G2 expansion module independently
Microsoft gives the C456HD G2 expansion module its own certification entry even though the phone and module shared reference firmware 3.1.20 and the same listed end date at review. Record host and module part numbers, versions, power and support lifecycles separately.
The module adds visible controls; it is not a separate carrier line, PBX registration, queue member or concurrency grant. Map each reception or monitored-contact action to the signed-in identity and policy, then test labels, pages, presence and call-state recovery with the exact host-module combination.
Prove power, network and management ownership
AudioCodes documents PoE or external power and Device Manager. Confirm the exact supply, switch budget, port policy and recovery behavior with all approved accessories attached. Preserve VLAN, addressing, DNS, time, certificate, enrollment and negotiated-call evidence instead of inferring readiness from a powered touch screen.
Assign ownership across AudioCodes and Microsoft management surfaces for inventory, configuration, policy, firmware, logs and retirement. Investigate disagreements between views before changing several layers at once.
Pilot the exact policy and workflow
Run an authorized pilot covering boot, enrollment, sign-in, policy arrival, accessibility settings, directory, inbound and outbound identity, hold, transfer, voicemail, action button, microphone control, expansion module, approved headset, update, restart and network or power recovery. Keep ordinary calling, emergency location and provider-approved emergency validation as separate evidence.
No C456HD, G2 expansion module, regional SKU, tenant, account, licence, policy, switch, accessory, firmware, application bundle, management service, protected session, emergency route, availability, compatibility, price, privacy outcome, audio result or live call was inspected or tested for this reference.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- AudioCodes C456HD product page ↗
- AudioCodes C456HD version 3.1 overview ↗
- AudioCodes native Teams phone releases ↗
- AudioCodes C456HD administrator settings ↗
- AudioCodes C456HD accessibility settings ↗
- Microsoft Teams certified phones and public-cloud firmware ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.