Cisco managed third-party device support on Webex Calling

Publisher

Cisco

URL

https://help.webex.com/en-us/article/njwkamr

Published

2026-07-28

Updated

unknown

Accessed

2026-09-30

HTTP status

200

License

Cisco proprietary; no-redistribution; short excerpts and locators only

Source notes citing this source

• Avaya desk phones are not among the vendors Cisco lists for third-party Webex Calling support, so an Avaya estate should plan to replace handsets with supported Cisco or listed third-party devices. inferred in context
• Third-party devices on Webex Calling get standard SIP phone features only, manual deployment without activation codes, individual (not bulk) provisioning in Control Hub, and no third-party RMA or warranty support. in context
• Cisco's third-party device support page for Webex Calling lists Poly, Yealink, Yealink DECT, AudioCodes and Snom devices. in context
• Cisco-managed third-party devices can be assigned to users or workspaces and support primary lines, shared lines and monitored lines. in context
• Cisco-managed third-party devices are deployed manually with no activation code or EDOS support, are provisioned one device at a time in Control Hub with no bulk option, and run a locked configuration with no third-party device management. in context
• For AudioCodes, Poly, Snom and Yealink devices, the manual deployment instructions begin by resetting the phone to factory default settings. in context
• Once the third-party devices are exposed to the customer, an administrator provisions them by MAC address as managed devices through Control Hub. in context
• A Poly phone is pointed at Webex Calling from its Advanced admin settings by setting the provisioning boot server to Static, the server type to HTTPS, and the server address to the regional URL (for the US, https://plcm.sipflash.com). in context
• The provisioning URL a Cisco-managed third-party device is pointed at is specific to both the device vendor and the Webex Calling region, with separate URLs published for regions including US, UK, EU, EUN, AU, CA, JP, KSA and India. in context
• The third-party device support article lists managing device settings in Control Hub as a capability of Cisco-managed third-party devices and has a 'Supported device settings' section for Poly, Yealink and Yealink DECT. disputed in context
• Cisco-managed third-party devices support standard SIP phone features only, with no advanced feature support. in context
• Cisco-managed third-party devices appear in the existing Control Hub device list alongside Cisco devices, and their statuses are displayed there. in context
• Cisco-managed third-party devices are supported through the normal TAC ticketing process for basic SIP troubleshooting, including SIP registration verification and basic calling, with no remote log collection, no third-party feature support and no third-party RMA or warranty support. in context
• A Yealink phone is pointed at Webex Calling by logging in to its web interface, opening Settings then Auto Provision, entering the regional Server URL (for the US, https://yealink.sipflash.com), and choosing Auto Provision Now, which reboots and provisions the phone. in context

Cite this source record

APA

WarmTransfer. (2026, July 28). Cisco managed third-party device support on Webex Calling. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-njwkamr-third-party-device-support-b

BibTeX

@misc{warmtransfer-cisco-help-njwkamr-third-party-device-support-b,
  title  = {Cisco managed third-party device support on Webex Calling},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-njwkamr-third-party-device-support-b},
  note   = {Cisco, accessed 2026-09-30}
}