WarmTransfer
ccaas platforms · published

Yealink phones on UC platforms

Verified 2026-09-25 · 58 sources · tier 2–4 · 2 disputed

Disputed: 2 sources below carry conflicting evidence.

Yealink phones operate across multiple unified communications platforms through native software builds, direct SIP registrations, or cloud provisioning redirection 27​19​47. Platform capabilities, provisioning workflows, and support lifecycles vary depending on the target ecosystem and device architecture 25​58​39.

Microsoft Teams Native and SIP Gateway Support

Yealink provides both native Android-based Teams devices and standard SIP devices interoperable via Microsoft Teams SIP Gateway 27​19. For native Teams devices, Android OS and firmware updates originate from the OEM, receive certification from Microsoft, and are distributed via Teams Admin Center (TAC) or the Teams Rooms Pro management portal (PMP) 25. Updates applied via an OEM's own service must be certified and accessible in TAC or PMP for the hardware to remain eligible for support 25. Microsoft tests and supports only the latest and latest-minus-one releases of Microsoft applications on Teams Android devices and recommends enabling auto-update 26. Whether a device undergoes recertification, reaches end of sale, or reaches end of life is decided by the OEM, with Microsoft directing lifecycle inquiries to the manufacturer 35. After certification expiration, Microsoft states it supports the latest application version on the unit for 2 years, reserving the right to adjust this policy 38.

The native Teams portfolio spans several hardware generations 27​30​37:

  • Android 15 models: Yealink MP52 E2, MP54 E2, MP55 E2, MP56 E2 and MP58 E2 are listed as certified under the Microsoft Teams phones Android Certification Program, running Android 15, with a current certification end date of October 15, 2030 27. The Yealink MP66 W is certified as a Teams phone on Android 15 with a current certification end date of October 15, 2030 32. For Android 15 based Teams devices, the Microsoft Teams certification end date is October 15, 2030 and the Microsoft support end date is October 15, 2032 21. The latest Teams Admin Center firmware for Yealink MP52 E2, MP54 E2, MP55 E2, MP56 E2 and MP58 E2 in the public cloud is 176.15.0.194 (AOSP), released May 12, 2026, with a minimum version of 176.15.0.160 28. The latest Teams Admin Center firmware for the Yealink MP66 W in the public cloud is 202.15.0.16, released September 2, 2026 33.
  • Android 12 models: The original (non-E2) Yealink MP54, MP56 and MP58 Teams phones are certified on Android 12 with a current certification end date of August 15, 2028 30. The Yealink CP965 conference phone is certified for Teams on Android 12 with a current certification end date of August 15, 2028 22. Microsoft extended the certification end date for Android 12 and 13 Teams devices from October 6, 2026 to August 15, 2028, and extended their Microsoft support end date to August 15, 2030 20. The latest Teams Admin Center firmware for the original Yealink MP54, MP56 and MP58 is 122.15.0.243 (AOSP), released September 4, 2025, with a minimum version of 122.15.0.166 31. In TAC, Yealink Teams firmware 122.15.0.157 and 122.15.0.160 for MP54/MP56/MP58, and 143.15.0.68 for CP965, are marked Recalled in the Teams Admin Center firmware table 36.
  • Accessories: The Yealink EXP50 expansion module is certified for Teams when attached to MP56, MP58, MP56 E2 or MP58 E2, with a certification end date of August 15, 2027 23.
  • Historical hardware: Yealink T55/T55A, T56/T56A, T58/T57A and CP960 Teams phones on Android 7 reached Teams certification end on October 4, 2021 and Microsoft support end on October 4, 2023 37. The original Yealink MP52 and the VP59 video phone, both on Android 9, reached Teams certification end on August 5, 2023 and Microsoft support end on August 5, 2025 29.

In federal clouds, the certified hardware page lists AudioCodes and HP Poly releases for GCCH and DoD and has no Yealink table 34. WarmTransfer's reading of the sources is that Yealink native Teams phones probably have no Microsoft-released firmware path in GCC High or DoD tenants, so federal deployments should confirm with Microsoft or Yealink before choosing them 24.

For standard SIP devices connecting via Teams SIP Gateway, Microsoft Teams SIP Gateway lists Yealink SIP desk phones (T2x, T3x, T4x G/S/U and T5x W models) and Yealink DECT bases and handsets (W70B, W80, W90, W56H, W73H, W57R, W59R, AX83H, AX86R) as compatible devices 19. SIP Gateway requires the Teams user to have a phone number with PSTN calling enabled, and SIP Gateway is not yet available for DoD 18. SIP Gateway supports only IPv4, so Yealink SIP phones connecting to Teams through SIP Gateway must use IPv4 15.

Hardware series Approved firmware Minimum firmware Location discovery
Yealink T30, T30P, T31G, T31P and T33G 124.86.0.147 10 83 10 Dynamic (LLDP) 16
T42U, T43U, T46U and T48U 108.86.5.1 10 83 10 Dynamic 16​10
T53, T53W, T54W and T57W 96.86.5.1 10 83 10 Dynamic 16
Yealink T27G Not stated 83 10 Dynamic (LLDP) 16
Older T2x and T4xG Not stated 83 10 Static only 16
DECT (e.g. W70B) Region-specific (NOAM: 146.85.5.4, EMEA: 146.85.5.2, APAC: 146.85.5.3) 12 Not stated Static only 16

Before configuring SIP Gateway, each SIP device must be reset to factory defaults, must not be behind an HTTP/S proxy, and must reach Teams on TCP 5061 and UDP 49152-53247 for 52.112.0.0/14 and 52.122.0.0/15 14. When setting the SIP Gateway provisioning server URL through DHCP, Yealink phones use DHCP option 66, while Cisco, Poly and AudioCodes phones use option 160 13. For SIP Gateway bulk sign-in, the Yealink provisioning URL must include the tenant ID, for example http://noam.ipp.sdg.teams.microsoft.com/tenantid/ in North America, while Cisco phones append /$PSN.xml 11. SIP Gateway's Japanese UI language is not supported on Yealink phones; unsupported languages fall back to English 17.

Zoom Phone Deployment and Provisioning

Zoom Phone's certified hardware list includes Yealink T3x, T4x, T5x, T7x and T8x desk phones, the VP59, CP920/CP925/CP935W/CP960/CP965 conference phones and W-series DECT systems, plus accessories such as EXP50 and EXP55 57. Zoom states that Yealink devices manufactured before 2019 are not compatible with Zoom Phone encryption and certificate security requirements, and provisioning fails even if the device is added manually 56.

Zoom's zero-touch provisioning URL for Yealink phones is https://provyp.zoom.us/api/v2/pbx/provisioning/yealink, and Yealink phones support both zero-touch and assisted provisioning on Zoom Phone 58. For Zoom zero-touch provisioning, the phone must be added to the Zoom web portal before a new phone is powered on for the first time; a previously used phone must be factory reset 50. Zoom assisted provisioning for Yealink requires a supported Yealink device that has been added to the Zoom web portal, reset to factory defaults and running the latest supported firmware 51. In Zoom assisted provisioning, the admin opens the Yealink web UI (default admin/admin), goes to Settings > Auto Provision, enters the assisted provisioning URL in Server URL, clears the username and password fields, and clicks Confirm and then Auto Provision Now; the phone reboots several times 52. Zoom warns that no other provisioning server may be communicating with the Yealink phone while assisted provisioning is being completed 55. After a Yealink phone is provisioned to Zoom Phone, Zoom automatically updates its firmware to the latest supported version 53.

Webex Calling Provisioning and Support Boundaries

The Webex Calling supported devices list includes Yealink T3, T4, T5, T7 and T8 series desk phones, CP920, CP925, CP960 and CP965 conference phones, and W52B, W60B and W70B DECT bases with handsets 45. Webex Control Hub supports the Yealink T58A and T58V through the T58V device type 44. On Webex Calling, Yealink T4xS phones do not support the Call Park Extension feature 43.

To deploy a Yealink phone to Webex Calling manually, the admin factory-resets it (hold OK for 10 seconds), logs in to the web UI, enters the region-specific provisioning server URL under Settings > Auto Provision (for example https://yealink.sipflash.com for the US), and selects Confirm and then Auto Provision Now 41. Manual deployment of third-party devices to Webex Calling does not support activation codes or EDOS 42. For third-party devices such as Yealink on Webex Calling, Cisco TAC provides basic SIP troubleshooting only (registration verification and basic calling), with no remote log collection or customer syslog and no third-party RMA or warranty support 39.

YMCS and Remote Provisioning Service (RPS)

Yealink Management Cloud Service (YMCS) combines device deployment, management, analysis, active monitoring, fault diagnosis, account registration, RPS service and order management in one platform 47. In YMCS, an RPS server is added under RPS > Server > Add with a server name, a server URL used as the redirection address, and a username and password for that server; trusted and server certificates can be imported optionally 49. Deleting an RPS server in YMCS changes the binding status of its devices to unbound 46. Adding an RPS device in YMCS requires the device's MAC address (12 alphanumeric characters) and its Machine ID or serial number, which together verify ownership, and a newly added device is removed from other companies' accounts 48.

Yealink offers its Remote Provisioning Service (RPS) free of charge and directs requests for it through a support ticket 3. The redirection ecosystem includes operational considerations: 47

  • Sources disagree: Enreach told its SwyxON customers that the outdated Yealink RPS would be switched off on January 1, 2026 6.
  • Sources disagree: Enreach states that no compatible firmware exists for the CP920 and CP960 to use the new Yealink RPS, so SwyxON customers must enter the provisioning URL manually in the phone's web UI 1.
  • After the RPS-related firmware upgrade, some Yealink devices may ask the user for an RPS PIN the first time they connect to the new RPS server 8.
  • In the field, field reports suggest that the Yealink RPS change only affects phones going through first-time setup (for example after a factory reset); phones already connected to the provider's tenant keep working 2.
  • WarmTransfer's reading of the sources is that a Yealink phone that cannot reach the new RPS and is factory reset will not redirect zero-touch to Zoom, Webex Calling or another provider, and will likely need its provisioning URL entered manually under Settings > Auto Provision 9.

See also

Applicability

Applies to: Microsoft Teams Phone devices, Microsoft Teams SIP Gateway, Yealink YMCS, Microsoft Teams devices on Android, Zoom Phone, Cisco Webex Calling, Microsoft Teams Admin Center, and Yealink RPS. Deployments: multi-tenant, dod, and gcc-high. Sources checked 2026-09-25. In federal clouds, the certified hardware firmware section lists AudioCodes and HP Poly releases for GCCH and DoD and has no Yealink table 34, and SIP Gateway is not yet available for DoD 18.

What remains uncertain

  • Webex Calling Cisco-managed vs customer-managed device model for Yealink is not covered by the sources below.
  • Yealink phone security advisories and CVEs are not covered by the sources below.
  • YMCS licence tiers and pricing are not covered by the sources below.
  • YMCS management of Teams-native MP phones alongside Teams Admin Center is not covered by the sources below.
  • Per-model list of Yealink devices that support Zoom zero-touch provisioning is not covered by the sources below.
  • First-party confirmation of the old RPS shutdown date (Oct 2025 vs Jan 2026) is not covered by the sources below.
  • Deployment of Yealink devices across other UCaaS providers is not covered by the sources below.
  • Yealink SIP phones as third-party SIP devices on CUCM is not covered by the sources below.

See also

Related to

Sibling of

Referenced by

Sources

Documents

tier 2 current vendor documentation

[RPS] Statement on RPS Service Adjustment

Yealink · 2025-12-27 · accessed 2026-09-25

tier 2 current vendor documentation

Android versioning support for Teams devices

Microsoft · 2026-09-17 · accessed 2026-09-25

tier 2 current vendor documentation

Cisco managed third-party device support on Webex Calling

Cisco Systems, Inc. (help.webex.com) · 2026-07-28 · accessed 2026-09-16

tier 2 current vendor documentation

Configure SIP Gateway

Microsoft · 2024-08-08 · accessed 2026-09-21

tier 2 current vendor documentation

Getting started with provisioning desk phones

Zoom Communications · accessed 2026-09-25

tier 2 current vendor documentation

Manage RPS Devices

Yealink · 2026-03-24 · accessed 2026-09-25

tier 2 current vendor documentation

Manage RPS Server

Yealink · 2026-03-24 · accessed 2026-09-25

tier 2 current vendor documentation

Plan SIP Gateway

Microsoft · 2025-02-28 · accessed 2026-09-16

tier 2 current vendor documentation

Supported devices for Webex Calling

Cisco Systems, Inc. (help.webex.com) · 2026-07-20 · accessed 2026-09-16

tier 2 current vendor documentation

Teams phones certified hardware

Microsoft · 2026-09-23 · accessed 2026-09-25

tier 2 current vendor documentation

Yealink assisted provisioning guide

Zoom · accessed 2026-09-25

tier 2 current vendor documentation

Yealink Free Remote Provisioning Service

Yealink · accessed 2026-09-25

tier 2 current vendor documentation

YMCS Platform

Yealink · 2026-04-14 · accessed 2026-09-25

tier 2 current vendor documentation

Zoom Phone certified hardware

Zoom Communications · accessed 2026-09-25

tier 4 archived vendor documentation

New Yealink Redirection Service: What do SwyxON customers need to bear in mind?

Enreach · 2025-12-08 · accessed 2026-09-25

Cite this page

APA

WarmTransfer. (2026, September 25). Yealink phones on UC platforms. WarmTransfer. https://warmtransfer.net/knowledge/yealink-phones-uc

BibTeX

@misc{warmtransfer-yealink-phones-uc,
  title  = {Yealink phones on UC platforms},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/yealink-phones-uc},
  note   = {Verified 2026-09-25}
}