WarmTransfer
ccaas platforms · published

Poly phones on Teams and Webex and Zoom

Verified 2026-09-25 · 60 sources · tier 2

Poly devices integrate across major UC platforms through platform-native Android applications, vendor-managed SIP gateways, or generic SIP registration 31​43​50​56. Supported features, provisioning mechanisms, and operating system lifecycles differ considerably depending on whether devices connect to Microsoft Teams, Cisco Webex Calling, or Zoom Phone 31​50​58.

Microsoft Teams

Native Android Teams Phones

Poly CCX350, CCX400, CCX500, CCX505, and CCX600, along with Trio C60 (including C60 NR and C60 ND), are certified under the Microsoft Teams phones Android Certification Program on Android 12, carrying a certification end date of August 15, 2028 43. The Poly EM60 expansion module, compatible with CCX505 and CCX600, is Teams-certified through August 15, 2027 44. For devices on Android 12 and 13, Microsoft extended the certification end date from October 6, 2026 to August 15, 2028, and the support end date to August 15, 2030 1. After a certification expires, Microsoft commits to supporting the latest version of Teams device applications for 2 years, though it reserves the right to alter that policy 48. Native Teams certification for Poly Trio 8500 and 8800 on Android 7 ended on October 4, 2021, and Microsoft support ended on October 4, 2023 47.

Android OS and firmware builds are supplied by the OEM to Microsoft for certification and distributed via Teams admin center (TAC) or Teams Rooms Pro Management portal (PMP); firmware installed through an OEM's own service must be Microsoft-certified and listed in TAC or PMP to remain eligible for Microsoft support 3. Microsoft tests and supports only the latest and latest-1 versions of Teams applications on Android devices; resolving defects in older builds requires updating to the latest version 2.

As of 2026-09-23, the latest public cloud firmware released via TAC for CCX350/400/500/505/600 and Trio C60 is 9.5.1.0067 (AOSP), released September 15, 2026 and bundling Teams client 1449/1.0.94.2026047602 46. Poly CCX and Trio C60 firmware 9.0.0.10460 is marked as "Recalled" in Microsoft's documentation, with the next release listed as 9.0.1.6562 dated December 16, 2024 42. Firmware 9.5.0.1321 was released to GCC High on September 17, 2026, and to DoD on September 18, 2026, when the public cloud was on 9.5.1.0067 45.

Management Transition to PMP

Management of Teams Android devices is transitioning from TAC to PMP, and automatic updates through TAC have ceased except for the mandatory Admin Agent 14. PMP management requires Admin Agent version 830 (1.0.0.202606082157) or later in commercial clouds; devices running earlier versions receive no application or firmware updates until TAC pushes the required Admin Agent update 9. For GCC, GCC High, and DoD, the minimum Admin Agent version is 856 (1.0.0.202607160723), and mandatory Admin Agent updates cannot be paused 10.

If a Teams Android device runs an Admin Agent earlier than 794, it must be manually updated to OEM-portal firmware that contains Admin Agent 794 or later before Microsoft's Zero-Day Update mechanism can update it automatically 8. Once an administrator confirms PMP update rings, the action cannot be reversed, and all Teams phones—except those on an Admin Agent below 830—map to the default General ring regardless of their prior TAC phase 13. PMP applies automatic updates strictly within a fixed nightly window between 12 AM and 5 AM device local time, with no custom maintenance windows supported 11. Trio8800 and trio8500 are listed as legacy devices that are end of life and no longer officially supported for the PMP Admin Agent transition 15. Neither TAC nor PMP supports application or firmware updates for SIP devices 12.

Teams SIP Gateway

Microsoft Teams SIP Gateway enables compatible third-party Poly SIP devices to sign in using corporate credentials and execute calls 31. The SIP Gateway compatible-devices table lists no CCX models 26. Supported Poly models and their firmware thresholds include the following: 41​39​37​20​21​35​16

Model Series Minimum Firmware Approved Firmware
Poly VVX 150, 201, 250, 300, 301, 310, 311, 350, 400, 401, 410, 411, 450, 500, 501, 600 and 601 41 5.9.5 41 5.9.7.3480 (VVX 300/310/400/410/500/600); 6.4.6.2656 (VVX 250/350/450) 39
Trio 8500, Trio 8800 37 5.9.5.3182 37 7.2.4.0185 37
Poly Edge E100, E220, E300, E320, E350, E400, E450, E500 and E550 20 8.1.0.12774 20 8.5.1.0508 20
Poly Edge V 200, 250, 250+, 400, 450, 650, 800 and 850 21 8.5.1.0565 21 None listed 21
Poly Rove B1, B2 and B4 bases; Rove 20, 30 and 40 handsets 35 8.0.11 35 8.0.11 35
Poly ATA 400 and ATA 402 16 4.0.1.6480 16 4.0.1.6480 16
Poly OBi 300 and OBi 302 16 3.2.4.8441 16 3.2.5.8732 16

Omegaline VVX 250, 350, and 450 are also supported with a minimum firmware of 5.9.5 41. Before onboarding, devices must be reset to factory defaults and reach at least minimum firmware 23.

Teams SIP Gateway requires users to have PSTN calling enabled on their phone number 34. The service is not yet available for the DoD cloud 27. It supports only IPv4 networking, even though the broader Teams service supports IPv4 and IPv6 24. SIP devices can act as Teams call queue agents, but because SIP Gateway does not publish presence for them, presence-based routing is unsupported 28. SIP Gateway automatically offboards paired devices that have not connected for 30 days and unpaired devices after 14 days; recovering an offboarded device requires a factory reset 36.

Enabling users requires setting SIP devices can be used for calls (or -AllowSIPDevicesCalling in PowerShell) in Teams calling policy, which defaults to False and can take up to 24 hours to propagate 18. The provisioning server URL is pushed via DHCP option 160 for Poly phones (using http://noam.ipp.sdg.teams.microsoft.com, http://emea.ipp.sdg.teams.microsoft.com, or http://apac.ipp.sdg.teams.microsoft.com) 19​33. Enrolling common area phones involves generating a verification code in TAC and dialing *55*<code> on the device 22. Bulk sign-in supports batches up to 100 devices with up to 3 concurrent batches per region, applicable to devices within 72 hours of onboarding or 168 hours of being signed out 17. When the tenant ID is appended to the provisioning URL for bulk sign-in, Poly ATAs use $mac.cfg rather than mac.ini 29.

For location discovery, Poly VVX 300, 310, 400, 410, 500, 600, ATA 400/402, and OBi 300/302 support only static location 16​40. Dynamic location discovery is supported on Poly Rove (via LLDP), Trio 8500/8800, and VVX 150, 201, 250, 301, 311, 350, 401, 411, 450, 501, and 601 35​40. For Poly devices, LLDP must be enabled at the switch level for subnet-length-based dynamic location discovery 32.

On Poly VVX devices using SIP Gateway, Japanese is only partially supported, and the voicemail softkey is hardcoded as "VM" across all languages due to a string-length limit 38.

Poly Lens Integration

Microsoft states that customers can use Poly Lens to manage device-side configurations for VVX and Trio hardware deployed on SIP Gateway 25. On SIP Gateway, devices automatically reboot and install selected firmware 30. Under Poly Lens Assisted Provisioning, Lens retrieves SIP Gateway settings and applies them as part of its Configuration Policy 5. Microsoft settings take the highest precedence across Lens policy layers, though select parameters can be overridden 5. This integration is configured per device under Manage > Inventory > Settings > Integrations > Microsoft Teams, where administrators select the region and device language for provisioned devices 7.

Cisco Webex Calling

Poly devices on Webex Calling are deployed manually without activation codes or Cisco EDOS 50. In Control Hub, devices are provisioned one at a time with no bulk provisioning options, device configurations are locked against third-party management tools, and Control Hub exposes no device settings 50.

Poly devices on Webex Calling do not support Device Settings, Software Channels, or Call Park Extensions, with the single exception that the Poly Trio C60 supports Call Park Extensions 51. Cisco's technical support scope for third-party devices covers basic SIP troubleshooting (registration verification and basic calling) 49. Cisco offers no remote log collection, customer syslog, third-party feature support, or warranty/RMA support for these devices 49.

Zoom Phone

Zoom Phone requires Polycom devices to run UCS firmware 4.0.0 or later, and it does not support Polycom VVX OBi edition phones 56​57. Devices provisioned to Zoom Phone automatically upgrade to the latest supported firmware version 53. Supported Trio 8500 and 8800 conference phones are listed on firmware 7.2.8.0096 with Zero Touch Provisioning (ZTP) enabled and SRTP set to AES-128 by default (AES-256 optional) 55.

Assisted provisioning is available for supported Polycom VVX, SoundPoint, and SoundStation models 52. The workflow requires adding the device MAC in the Zoom web portal, performing a factory reset, configuring the phone's web UI to Server Type HTTPS with the Zoom assisted provisioning URL and blank credentials, setting the DHCP Boot Server to Static, and rebooting 52. Because Zoom Phone enforces TLS 1.2, a Poly SoundStation IP 6000 with an old updater/boot loader that lacks TLS 1.2 can fail provisioning until the updater is upgraded 54.

Zoom Phone Appliance Mode

Poly CCX 400, CCX 505, and CCX 600 operate as Zoom Phone Appliances (ZPA) on Android 9 and firmware 8.1.8.2935, with recertification due to complete in October 2026 59. Zoom does not currently support Poly PVOS 9.x.x for ZPA mode, requiring CCX devices on PVOS 9.x.x to be downgraded 60. WarmTransfer's reading of the sources is that as of late September 2026, one CCX firmware line cannot serve both platforms: Teams-certified CCX builds are 9.x on Android 12, while Zoom Phone Appliance mode requires 8.1.8.2935 on Android 9, meaning moving a CCX from current Teams firmware to ZPA therefore implies a firmware downgrade 4.

To convert a CCX phone to a Zoom Phone Appliance, an administrator selects "Zoom Phone" as the Base Profile in the device startup menu 58. Zoom details distinct conversion procedures for new devices, devices from other providers, devices previously configured for Teams, and devices already running Zoom Phone in generic SIP mode 58.

See also

Applicability

Applies to: Microsoft Teams SIP Gateway, Microsoft Teams phones certification, Microsoft Teams admin center, Microsoft Teams devices on Android, Microsoft Teams Rooms Pro Management portal, Cisco Webex Calling, Zoom Phone, Zoom Phone Appliance, HP Poly Poly CCX, and HP Poly Poly Lens. Deployments: multi-tenant, dod, gcc, and gcc-high. Sources checked 2026-09-25. Teams SIP Gateway is not available for the DoD cloud 27. Teams Android CCX firmware 9.5.0.1321 applies to GCC High and DoD clouds, while public commercial cloud uses 9.5.1.0067 46​45. Minimum Admin Agent requirements for PMP update management are version 830 for commercial tenants and version 856 for GCC, GCC High, and DoD environments 9​10.

What remains uncertain

Whether Poly Edge E or Edge V devices can be provisioned as Cisco-managed devices on Webex Calling is not covered by the sources below.

Whether Zoom Phone Appliance certification for CCX models on Android 9 concluded as scheduled in October 2026 is not covered by the sources below.

See also

Related to

  • Cisco Desk and Room devices for calling — Webex Calling device support; Poly phones are Cisco-managed third-party devices with reduced provisioning and support scope.
  • SIP registration failures — Poly provisioning failures (TLS 1.2 updater; DHCP option 160; factory reset prerequisites) overlap SIP registration troubleshooting.
  • Yealink phones on UC platforms — Parallel third-party desk-phone topic; same SIP Gateway; Webex third-party and Zoom certified-hardware sources cover both vendors.

Referenced by

  • Yealink phones on UC platforms — Parallel third-party desk phone vendor topic; the Teams certified-hardware and SIP Gateway compatibility tables cover both vendors side by side

Sources

  1. 1
    For Teams devices on Android 12 and 13, Microsoft extended the certification end date from October 6, 2026 to August 15, 2028, and the Microsoft support end date to August 15, 2030.
    Android versioning support for Teams devices · Android OS and OEM firmware support, Note and table rows Android 12 and Android 13 · Checked 2026-09-25
  2. 2
    Microsoft tests and supports the latest and latest-1 versions of the Microsoft applications on Teams Android devices; to get a fix for a defect in an older version, customers must install the latest version.
    Android versioning support for Teams devices · Microsoft Teams Devices Applications Support, paragraphs 2 and 3 · Checked 2026-09-25
  3. 3
    Android OS and firmware for Teams devices are supplied by the OEM to Microsoft for certification and distributed through TAC or PMP. Firmware installed through an OEM's own service must be Microsoft-certified and available in TAC or PMP for the device to remain eligible for Microsoft support.
    Android versioning support for Teams devices · Android OS and OEM firmware support, paragraphs 1 and 2 · Checked 2026-09-25
  4. 4
    As of late September 2026, one CCX firmware line cannot serve both platforms: Teams-certified CCX builds are 9.x on Android 12, while Zoom Phone Appliance mode requires 8.1.8.2935 on Android 9. Moving a CCX from current Teams firmware to ZPA therefore implies a firmware downgrade.inferred
    Certified Zoom Phone Appliances · Poly table rows and PVOS 9.x note, read against the certified-hardware Firmware tab · Checked 2026-09-25
  5. 5
    With Poly Lens Assisted Provisioning, Poly Lens retrieves the device's Microsoft Teams SIP Gateway settings and applies them as part of its Configuration Policy. The Microsoft settings take the highest precedence over all other Lens policy layers, although select parameters can be overridden.
    Lens Assisted Provisioning · Lens Assisted Provisioning category page, overview · Checked 2026-09-25
  6. 6
    Poly Lens documentation for Lens Assisted Provisioning to Teams SIP Gateway reportedly lists CCX 400, 500, 505 and 600 alongside VVX, Trio and Edge E as compatible families, while Microsoft's SIP Gateway compatible-devices table lists no CCX model.disputed
    Microsoft Teams Integration (Lens Assisted Provisioning) · Microsoft Teams Integration, supported device families list · Checked 2026-09-25
  7. 7
    Lens Assisted Provisioning is enabled per device in Poly Lens: open the device under Manage > Inventory, go to Settings > Integrations > Microsoft Teams, turn the feature on, and choose the SIP Gateway region (Americas, EMEA or APAC) and the device language. The device must be in a Provisioned state with Device Provisioning enabled on the account.
    Microsoft Teams Integration (Lens Assisted Provisioning) · Microsoft Teams Integration, prerequisites and device-level steps · Checked 2026-09-25
  8. 8
    A Teams Android device with Admin Agent earlier than 794 must first be updated manually to OEM-portal firmware that contains Admin Agent 794 or later. From 794, Microsoft's Zero-Day Update mechanism updates the Admin Agent automatically.
    Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal · Guidance for devices with older Admin Agent versions · Checked 2026-09-25
  9. 9
    PMP update management for Teams Android devices requires Admin Agent version 830 (1.0.0.202606082157) or later. A Teams phone below 830 receives no app or firmware updates until its Admin Agent is updated, and TAC pushes that Admin Agent update.
    Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal · Device type specific updates guidance, Teams phones, items 2 and 3; Moving Android updates section · Checked 2026-09-25
  10. 10
    For GCC, GCC High and DoD, the minimum Admin Agent version for PMP management is 856 (1.0.0.202607160723), and these mandatory Admin Agent updates cannot be paused.
    Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal · Updates guidance for government cloud customers, Important note · Checked 2026-09-25
  11. 11
    PMP installs automatic updates on Android Teams devices only in a fixed nightly maintenance window from 12 AM to 5 AM device local time. Admins cannot configure a custom window.
    Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal · Key update management capabilities, item 5; FAQ 'Does PMP support custom maintenance window' · Checked 2026-09-25
  12. 12
    Neither TAC nor PMP supports app or firmware updates for SIP devices (such as VVX or Edge E on SIP Gateway).
    Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal · Frequently asked questions, 'Can admins manage app/firmware updates for SIP devices via PMP?' · Checked 2026-09-25
  13. 13
    Once an admin confirms PMP update rings, which cannot be reversed, every Teams phone is mapped to the default General ring whatever its TAC phase. Phones on Admin Agent below 830 are the exception.
    Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal · Moving Android updates from auto-update phases in TAC to rings in PMP, one-time mapping bullets and Warning · Checked 2026-09-25
  14. 14
    Management of Teams Android devices, including Teams phones, is moving from the Teams admin center to the Teams Rooms Pro Management portal (PMP). Automatic updates through TAC have stopped, except for the minimum required Admin Agent.
    Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal · Overview: what is changing; Moving Android updates from auto-update phases in TAC to rings in PMP, 'As part of general availability (GA)' bullets · Checked 2026-09-25
  15. 15
    Microsoft lists Trio8800 and trio8500 among the legacy Teams Android devices that are end of life and no longer officially supported for the PMP Admin Agent transition.
    Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal · Guidance for unsupported or end of live devices, legacy device list · Checked 2026-09-25
  16. 16
    For Teams SIP Gateway, Poly ATA 400 and ATA 402 are listed at firmware 4.0.1.6480, and Poly OBi 300 and OBi 302 have minimum firmware 3.2.4.8441 and approved firmware 3.2.5.8732; all four support only static location.
    Plan SIP Gateway · Compatible devices table, Poly rows ATA 400, ATA 402, OBi 300, OBi 302 and footnote 3 · Checked 2026-09-25
  17. 17
    SIP Gateway bulk sign-in handles batches of up to 100 devices, with at most 3 concurrent batches per region. It applies to devices within 72 hours of onboarding, or within 168 hours of being signed out.
    Configure SIP Gateway · Bulk sign in, opening paragraph and scenario bullets · Checked 2026-09-25
  18. 18
    Users are enabled for SIP Gateway through a Teams calling policy setting ('SIP devices can be used for calls', or -AllowSIPDevicesCalling in Set-CsTeamsCallingPolicy). It defaults to False, and policy propagation can take up to 24 hours.
    Configure SIP Gateway · Enable SIP Gateway for the users in your organization, By using PowerShell and Note · Checked 2026-09-25
  19. 19
    For Cisco, Poly and AudioCodes phones, the SIP Gateway provisioning server URL is delivered with DHCP option 160; Yealink and Alcatel-Lucent Enterprise phones use option 66.
    Configure SIP Gateway · Set the SIP Gateway provisioning server URL, Manually, Note bullets · Checked 2026-09-25
  20. 20
    For Teams SIP Gateway, Poly Edge E100, E220, E300, E320, E350, E400, E450, E500 and E550 have minimum firmware 8.1.0.12774 and approved firmware 8.5.1.0508.
    Plan SIP Gateway · Compatible devices table, Poly rows Edge E100 to Edge E550 · Checked 2026-09-25
  21. 21
    For Teams SIP Gateway, Poly Edge V 200, 250, 250+, 400, 450, 650, 800 and 850 are listed with minimum firmware 8.5.1.0565 and no approved firmware version.
    Plan SIP Gateway · Compatible devices table, Poly rows Edge V 200 to Edge V 850 · Checked 2026-09-25
  22. 22
    To enroll a SIP device provisioned in Teams admin center, the admin generates a verification code for the device's MAC address, and on the device dials *55* followed by that code.
    Configure SIP Gateway · Provision and enroll SIP devices as common area phones, steps 3 and 4 · Checked 2026-09-25
  23. 23
    Before a SIP device is configured for SIP Gateway it must be reset to factory defaults, and it must be on at least the minimum supported firmware before onboarding.
    Configure SIP Gateway · Before you can configure SIP Gateway; Using DHCP, paragraph on minimum firmware · Checked 2026-09-25
  24. 24
    SIP Gateway supports only IPv4, even though the Teams service and clients support both IPv4 and IPv6.
    Configure SIP Gateway · Microsoft Teams and IPv6 · Checked 2026-09-25
  25. 25
    Microsoft states that customers can use Poly Lens to manage the device-side configuration of Poly VVX and Trio devices used with SIP Gateway.
    Plan SIP Gateway · Compatible devices section, Note on AudioCodes OVOC and Poly Lens · Checked 2026-09-25
  26. 26
    The Poly section of the Teams SIP Gateway compatible-devices table lists Trio, VVX, Rove, Edge E, Edge V, ATA and OBi models and no CCX model.
    Plan SIP Gateway · Compatible devices table, Poly section (all rows) · Checked 2026-09-25
  27. 27
    SIP Gateway is not yet available for the DoD cloud.
    Plan SIP Gateway · Requirements to use SIP Gateway, Note · Checked 2026-09-25
  28. 28
    SIP devices can be Teams call queue agents through SIP Gateway, but SIP Gateway does not publish presence for them, so presence-based routing is not supported.
    Plan SIP Gateway · Benefits of SIP Gateway, Call Queues and voice apps support bullet · Checked 2026-09-25
  29. 29
    When the tenant ID is added to the SIP Gateway provisioning URL for bulk sign-in, Poly ATAs use $mac.cfg in place of mac.ini.
    Configure SIP Gateway · Bulk sign in prerequisites, item 2, Important note · Checked 2026-09-25
  30. 30
    The Poly remark in the SIP Gateway compatible-devices table says the device will automatically reboot and install the selected firmware, and it links the Poly Lens provisioning guide.
    Plan SIP Gateway · Compatible devices table, Poly vendor header row, Remarks and Links columns · Checked 2026-09-25
  31. 31
    Microsoft Teams SIP Gateway lets compatible third-party SIP devices, including devices from Poly, sign in to Teams with corporate credentials and make and receive calls.
    Plan SIP Gateway · Plan SIP Gateway, introductory paragraph · Checked 2026-09-25
  32. 32
    For Poly devices on Teams SIP Gateway, LLDP must be turned on at the switch level for subnet-length-based dynamic location discovery.
    Plan SIP Gateway · Compatible devices section, Note following the table footnotes (For Poly devices, LLDP...) · Checked 2026-09-25
  33. 33
    The regional SIP Gateway provisioning server URLs are http://noam.ipp.sdg.teams.microsoft.com (Americas), http://emea.ipp.sdg.teams.microsoft.com (EMEA) and http://apac.ipp.sdg.teams.microsoft.com (APAC).
    Configure SIP Gateway · Set the SIP Gateway provisioning server URL, Using DHCP · Checked 2026-09-25
  34. 34
    To use SIP Gateway, Teams users must have a phone number with PSTN calling enabled.
    Plan SIP Gateway · Requirements to use SIP Gateway · Checked 2026-09-25
  35. 35
    For Teams SIP Gateway, Poly Rove B1, B2 and B4 bases and Rove 20, 30 and 40 handsets are listed with minimum and approved firmware 8.0.11, and they support dynamic location discovery through LLDP.
    Plan SIP Gateway · Compatible devices table, Poly Rove rows and footnote 1 · Checked 2026-09-25
  36. 36
    SIP Gateway automatically offboards paired (signed-in) devices that have not connected for 30 days and unpaired devices after 14 days; an offboarded device can be onboarded again after a factory reset.
    Plan SIP Gateway · Benefits of SIP Gateway, Off board stale devices bullet · Checked 2026-09-25
  37. 37
    For Teams SIP Gateway, Poly Trio 8500 and Trio 8800 have minimum firmware 5.9.5.3182 and approved firmware 7.2.4.0185.
    Plan SIP Gateway · Compatible devices table, Poly rows Trio 8500 and Trio 8800 · Checked 2026-09-25
  38. 38
    On SIP Gateway, Japanese is only partially supported on Polycom VVX, and the voicemail softkey on Poly VVX is hardcoded as 'VM' in every language because of a string-length limitation.
    Configure SIP Gateway · Set a SIP device's UI language, Supported languages, Note · Checked 2026-09-25
  39. 39
    For Teams SIP Gateway, the approved firmware for Poly VVX 300, 310, 400, 410, 500 and 600 is 5.9.7.3480, while the approved firmware for VVX 250, 350 and 450 is 6.4.6.2656.
    Plan SIP Gateway · Compatible devices table, Poly rows, Approved firmware version column · Checked 2026-09-25
  40. 40
    Under Teams SIP Gateway, Poly VVX 300, 310, 400, 410, 500 and 600 support only static location, while VVX 150, 201, 250, 301, 311, 350, 401, 411, 450, 501 and 601 and the Trio 8500/8800 support dynamic location discovery.
    Plan SIP Gateway · Compatible devices table, Poly rows superscripts 2 and 3 with table footnotes · Checked 2026-09-25
  41. 41
    The SIP Gateway compatible-devices table lists Poly VVX 150, 201, 250, 300, 301, 310, 311, 350, 400, 401, 410, 411, 450, 500, 501, 600 and 601 (plus Omegaline VVX 250/350/450), all with minimum firmware 5.9.5.
    Plan SIP Gateway · Compatible devices table, Poly rows VVX150 through VVX601 · Checked 2026-09-25
  42. 42
    Poly CCX/Trio C60 firmware 9.0.0.10460 is marked 'Recalled' in Microsoft's Teams phones firmware table; the next listed release, 9.0.1.6562, is dated December 16, 2024.
    Teams phones certified hardware · Firmware tab, Public cloud, HP | Poly table, rows 9.0.1.6562 and 9.0.0.10460 · Checked 2026-09-25
  43. 43
    Poly CCX350, CCX400, CCX500, CCX505, CCX600 and Trio C60 (including C60 NR and C60 ND) are certified under the Microsoft Teams phones Android Certification Program on Android 12, with a current certification end date of August 15, 2028.
    Teams phones certified hardware · Certified Teams phones tab, Poly rows · Checked 2026-09-25
  44. 44
    The Poly EM60 expansion module, supported on CCX505 and CCX600, is Teams-certified with a certification end date of August 15, 2027.
    Teams phones certified hardware · Certified Teams phones tab, row Poly EM60 supported on CCX505 and CCX600 · Checked 2026-09-25
  45. 45
    Poly CCX350/400/500/505/600 and Trio C60 firmware 9.5.0.1321 was released to GCC High on September 17, 2026 and to DoD on September 18, 2026. The public cloud already had 9.5.1.0067.
    Teams phones certified hardware · Firmware tab, Firmware versions released to the Federal clouds, HP | poly table, first two rows · Checked 2026-09-25
  46. 46
    As of 2026-09-23, the latest Poly firmware released to the public cloud through Teams admin center for CCX350/400/500/505/600 and Trio C60 is 9.5.1.0067 (AOSP), released September 15, 2026 and bundling Teams client 1449/1.0.94.2026047602.
    Teams phones certified hardware · Firmware tab, Firmware versions released to the Public cloud, HP | Poly table, first row · Checked 2026-09-25
  47. 47
    Native Teams certification for Poly Trio 8500/8800 (Android 7) ended on October 4, 2021, and Microsoft support ended on October 4, 2023.
    Teams phones certified hardware · End of certification tab, row Teams phones - conference Poly Trio 8500/8800 · Checked 2026-09-25
  48. 48
    After a Teams device's certification expires, Microsoft commits to supporting the latest version of the Teams devices applications on that device for two years, and it reserves the right to change that policy.
    Teams phones certified hardware · Introductory section, paragraph beginning 'After a certification expires' · Checked 2026-09-25
  49. 49
    For Cisco-managed third-party devices on Webex Calling, Cisco provides only basic SIP troubleshooting (registration verification and basic calling). It offers no remote log collection or customer syslog, no third-party feature support, and no third-party RMA or warranty support.
    Cisco managed third-party device support on Webex Calling · Technical support section · Checked 2026-09-25
  50. 50
    On Webex Calling, Poly devices are deployed manually, without activation codes or EDOS. They are provisioned one at a time in Control Hub (no bulk), their configuration is locked (no third-party device management), and there are no device settings in Control Hub.
    Cisco managed third-party device support on Webex Calling · Cisco managed third-party device support, provisioning and deployment bullets · Checked 2026-09-25
  51. 51
    On Webex Calling, Poly devices do not support Device Settings, Software Channels or Call Park Extensions, except that the Poly Trio C60 supports Call Park Extensions.
    Supported devices for Webex Calling · Third-party devices, Poly note on unsupported features · Checked 2026-09-25
  52. 52
    Zoom's Poly assisted provisioning applies to supported Polycom VVX, SoundPoint and SoundStation phones. The device is first added in the Zoom web portal and factory reset. Then, in the phone's web UI, the admin sets Server Type HTTPS with the assisted provisioning URL and blank credentials, sets DHCP Boot Server to Static, and saves, after which the phone reboots.
    Poly assisted provisioning guide · Poly assisted provisioning guide, Prerequisites and provisioning steps · Checked 2026-09-25
  53. 53
    Poly devices provisioned to Zoom Phone automatically upgrade to the latest firmware version Zoom supports.
    Zoom Phone certified hardware · Zoom Phone Certified Hardware, Poly section notes · Checked 2026-09-25
  54. 54
    Zoom Phone enforces TLS 1.2, so a Poly SoundStation IP 6000 with an old updater/boot loader that lacks TLS 1.2 can fail provisioning until the updater is upgraded.
    Poly assisted provisioning guide · Poly assisted provisioning guide, SoundStation IP 6000 boot loader note · Checked 2026-09-25
  55. 55
    Zoom Phone's certified hardware table lists firmware 7.2.8.0096 (dated 7/19/2026) for Poly Trio 8500 and Trio 8800, with SRTP AES-128 by default and AES-256 optional, and with ZTP enabled.
    Zoom Phone certified hardware · Zoom Phone Certified Hardware, Poly table, rows Trio 8500 and Trio 8800 · Checked 2026-09-25
  56. 56
    Zoom Phone works only with Polycom devices running UCS firmware 4.0.0 or later.
    Zoom Phone certified hardware · Zoom Phone Certified Hardware, Desk phones, Poly section notes · Checked 2026-09-25
  57. 57
    Zoom Phone does not support Polycom VVX OBi edition phones.
    Zoom Phone certified hardware · Zoom Phone Certified Hardware, Poly section notes · Checked 2026-09-25
  58. 58
    To convert a supported Poly CCX phone to a Zoom Phone Appliance, the admin selects 'Zoom Phone' as the Base Profile in the phone's startup menu. Zoom documents separate workflows for new phones, phones from another provider, phones previously used with Microsoft Teams, and phones already on Zoom Phone in SIP mode.
    Converting a Poly phone to a Zoom Phone Appliance · Converting a Poly phone to a Zoom Phone Appliance, conversion workflow sections · Checked 2026-09-25
  59. 59
    Zoom's certified Zoom Phone Appliance list gives Poly CCX 400, CCX 505 and CCX 600 (with or without camera) as supported on firmware 8.1.8.2935 and Android 9, with recertification in progress and due to complete in October 2026.
    Certified Zoom Phone Appliances · Certified Zoom Phone Appliances, Poly table rows CCX 400, CCX 505, CCX 600 · Checked 2026-09-25
  60. 60
    Zoom does not currently support Poly PVOS 9.x.x on Zoom Phone Appliances, so a CCX phone running PVOS 9.x.x must be downgraded to the certified ZPA firmware.
    Certified Zoom Phone Appliances · Certified Zoom Phone Appliances, Poly section note · Checked 2026-09-25

Documents

tier 2 current vendor documentation

Android versioning support for Teams devices

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

tier 2 current vendor documentation

Certified Zoom Phone Appliances

Zoom · 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

Converting a Poly phone to a Zoom Phone Appliance

Zoom · accessed 2026-09-25

tier 2 current vendor documentation

Lens Assisted Provisioning

HP Inc. (Poly Lens) · accessed 2026-09-25

tier 2 current vendor documentation

Microsoft Teams Integration (Lens Assisted Provisioning)

HP Inc. (Poly Lens) · 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

Poly assisted provisioning guide

Zoom · accessed 2026-09-25

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

Transitioning updates management for Teams Android devices from Teams Admin Center to the Teams Rooms Pro Management Portal

Microsoft · 2026-08-28 · accessed 2026-09-25

tier 2 current vendor documentation

Zoom Phone certified hardware

Zoom Communications · accessed 2026-09-25

Cite this page

APA

WarmTransfer. (2026, September 25). Poly phones on Teams and Webex and Zoom. WarmTransfer. https://warmtransfer.net/knowledge/poly-phones-uc

BibTeX

@misc{warmtransfer-poly-phones-uc,
  title  = {Poly phones on Teams and Webex and Zoom},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/poly-phones-uc},
  note   = {Verified 2026-09-25}
}