WarmTransfer
Configuration · guide

Setting up third-party SIP phones on Webex Calling

Verified 2026-09-30 · 60 sources · tier 2–3

For Webex Calling administrators and partner engineers configuring endpoints in Control Hub..

Webex Calling supports native Cisco phones, vendor-managed third-party handsets, and customer-configured generic SIP endpoints 29. Cisco positions third-party device onboarding primarily to facilitate customer migrations to Webex Calling 36.

Before you start

Cisco lists supported Cisco devices and supported third-party devices in separate groups, with a distinct customer-managed category for items like door phones, intercoms, speakers, and pagers 29. That customer-managed category names endpoints from Algo, 2N, Grandstream, CyberData, Axis, and Singlewire 26. The customer-managed option allows administrators to onboard devices like overhead pagers, door phones, analog adapters, and digital fax units 22. See also Setting up analog devices and ATAs on Webex Calling.

Cisco IP phones connected to the Webex cloud gain device-dependent capabilities including One Button to Join, Webex Meetings access, directory and contact search, user presence, and serviceability requests 40. In contrast, Cisco-managed third-party devices support standard SIP phone features only and do not provide advanced features 54. Specifically, Yealink, Poly, and Snom devices do not support video calling, unified call history, cloud directories, Webex meeting support, hot desking, layout configuration, device templates, visual voicemail, remote log collection, or time-of-day mode 33. Poly devices additionally lack device settings, software channels, and call park extensions, though the Poly Trio C60 retains call park extensions 42.

For Cisco-managed third-party devices, TAC provides support through standard ticketing for basic SIP troubleshooting only, such as verifying registration and basic calling, excluding remote log collection, third-party feature assistance, RMA, and warranty handling 57. For customer-managed devices, Cisco Technical Support does not investigate issues 18, and the customer owns the SIP credentials and bears responsibility for any fraud caused by failing to secure them 10.

What changes by situation

Pick your answers to see only your path. Nothing is sent anywhere until you make a plan.

How will this device get its configuration?
Who owns the device in Control Hub?

Two questions. One permanent page you can send to your manager.

Step 1 Confirm device eligibility

A Cisco phone (MPP or other Cisco device) that Webex Calling manages natively

Do

Verify that the Cisco multiplatform device runs software version 11.3.1MES5 or later 39. If users will activate the device by typing an activation code directly on the phone, confirm it runs firmware 11.3.1 SR2 or later 37.

Verify

Check the device software version display to ensure it meets version 11.3.1MES5 or later 39.

Rollback

Suggested rollback: No configuration changes were made during this verification step.

A Poly, Yealink, Snom or AudioCodes device from the supported list, configured by Webex through a provisioning URL

Do

Verify that the device appears on the supported list: Poly VVX 150, 250, 350 and 450, Poly CCX 400, 500, 505, 600 and 700, Poly Edge E series, Poly Trio 8300, 8800 and C60, and Poly ATA 400 and 402 43; Yealink T3, T4, T5, T7 and T8 series desk phones, Yealink CP conference phones, and Yealink DECT bases W52B, W60B and W70B with their handsets 59; Snom D3, D7 and D8 series phones, AudioCodes 425HD, 445HD and C450HD phones, and AudioCodes MP-1xx, MP-2xx and MP-5xx analog adapters 52. Confirm the device has not passed its end-of-life date: Poly VVX 101, 201, 301, 311, 401, 411, 501, and 601 reached end of life on 31 March 2026; Yealink SIP-T40G and W52P reached end of life on 30 September 2026; and Yealink SIP-T42S, T46S, and T48S are scheduled for 31 March 2027 30. Devices past end of life do not receive configuration updates, allow no new provisioning changes, and cannot be reprovisioned once deleted from Control Hub 31.

Verify

Confirm the physical device model matches an active model in the supported list and is not past its end-of-life cutoff date 30.

Rollback

Suggested rollback: No configuration changes were made during this verification step.

A third-party SIP device I configure by hand with SIP credentials from Control Hub (door phone, pager, ATA, generic SIP phone or gateway)

Do

Confirm the device satisfies Webex Calling security standards, as all customer-managed devices must 23. Check that the device supports SIP over TLS 1.2 or TLS 1.3 58 and the SRTP key suite AES_CM_128_HMAC_SHA1_80 53. Verify minimum firmware requirements against the endpoint manufacturer's documentation 16. For example, Algo requires firmware 3.4.4 or later 2, while first-generation 8180, 8028, and 8128 models cannot register because they lack TLS and SRTP 3. Do not attempt to onboard modems, as modems are not supported in Webex Calling 41.

Verify

Review the vendor documentation and device firmware level to confirm TLS 1.2 or 1.3 and SRTP AES_CM_128_HMAC_SHA1_80 support 58​53.

Rollback

Suggested rollback: No configuration changes were made during this verification step.

Step 2 Ensure device onboarding is enabled

A Cisco phone (MPP or other Cisco device) that Webex Calling manages natively

Do

Proceed directly to onboarding in Control Hub; native Cisco devices do not require third-party provisioning approval 38.

Verify

Suggested check: Verify that device addition options are accessible in Control Hub.

Rollback

Suggested rollback: No pre-activation changes need reversal.

A Poly, Yealink, Snom or AudioCodes device from the supported list, configured by Webex through a provisioning URL

Do

Request that your Cisco account manager approve and enable the supported third-party devices for provisioning in Control Hub 1. Administrators can provision these devices by MAC address only after they have been exposed to the customer organization 34.

Verify

Open Control Hub and verify that third-party vendors and models are visible in the device selection menu 34.

Rollback

Suggested rollback: Contact the account manager to remove provisioning permissions if enablement was performed in error.

A third-party SIP device I configure by hand with SIP credentials from Control Hub (door phone, pager, ATA, generic SIP phone or gateway)

Do

Confirm whether your organization requires Cisco account manager approval to expose third-party provisioning options 1, and check whether Customer Managed Devices is present under the device type options in Control Hub 8.

Verify

Check that Customer Managed Devices is selectable when adding a device in Control Hub 8.

Rollback

Suggested rollback: No account changes need reversal.

Step 3 Configure network and firewall rules

A Cisco phone (MPP or other Cisco device) that Webex Calling manages natively

Do

Turn off SIP Application Layer Gateway (SIP ALG) or equivalent SIP inspection on all firewalls and routers along the path 51.

Verify

Confirm that SIP ALG features are disabled on the network hardware 51.

Rollback

Suggested rollback: Re-enabling SIP ALG is not recommended.

A Poly, Yealink, Snom or AudioCodes device from the supported list, configured by Webex through a provisioning URL

Do

Turn off SIP Application Layer Gateway (SIP ALG) or equivalent SIP inspection on all firewalls and routers along the path 51.

Verify

Confirm that SIP ALG features are disabled on the network hardware 51.

Rollback

Suggested rollback: Re-enabling SIP ALG is not recommended.

A third-party SIP device I configure by hand with SIP credentials from Control Hub (door phone, pager, ATA, generic SIP phone or gateway)

Do

Turn off SIP Application Layer Gateway (SIP ALG) or equivalent SIP inspection on all firewalls and routers along the path 51.

Verify

Confirm that SIP ALG features are disabled on the network hardware 51.

Rollback

Suggested rollback: Re-enabling SIP ALG is not recommended.

Step 4 Add the device in Control Hub

A named user (personal usage) + A Cisco phone (MPP or other Cisco device) that Webex Calling manages natively

Do

In Control Hub, assign the phone to the user by entering its MAC address or by generating an activation code 38.

Verify

Suggested check: Verify the device entry appears under the user's profile in Control Hub.

Rollback

Suggested rollback: Remove the newly added device from the user profile in Control Hub.

A workspace (shared usage: lobby, door, paging zone, common-area phone) + A Cisco phone (MPP or other Cisco device) that Webex Calling manages natively

Do

In Control Hub, assign the phone to the workspace by entering its MAC address or by generating an activation code 38.

Verify

Suggested check: Verify the device appears assigned to the target workspace in Control Hub.

Rollback

Suggested rollback: Delete the device from the workspace configuration in Control Hub.

A named user (personal usage) + A Poly, Yealink, Snom or AudioCodes device from the supported list, configured by Webex through a provisioning URL

Do

In Control Hub, add the device to the user by MAC address as a managed device 34​7. Add devices individually, as Cisco-managed third-party endpoints must be provisioned 1 device at a time without bulk import or activation codes 28.

Verify

Confirm that the device appears in the Control Hub device list alongside native Cisco devices 55.

Rollback

Delete the device from Control Hub 31. Note that if the unit is past its end-of-life date, it cannot be reprovisioned 31.

A workspace (shared usage: lobby, door, paging zone, common-area phone) + A Poly, Yealink, Snom or AudioCodes device from the supported list, configured by Webex through a provisioning URL

Do

In Control Hub, add the device to the workspace by MAC address as a managed device 34​7. Provision the device individually; bulk onboarding and activation codes are not supported 28.

Verify

Verify the device appears in the Control Hub device inventory with its workspace assignment 55.

Rollback

Remove the device from the workspace in Control Hub, observing that models past end of life cannot be reprovisioned 31.

A named user (personal usage) + A third-party SIP device I configure by hand with SIP credentials from Control Hub (door phone, pager, ATA, generic SIP phone or gateway)

Do

In Control Hub, navigate to Management > Devices > Add device, select Personal usage, specify the user, choose Customer Managed Devices as the device type, select the device vendor, input the device MAC address, accept the disclaimer, and save 8. If the vendor is not explicitly listed, choose either the Generic SIP Phone or Generic SIP Gateway profile intended for SIP-TLS 1.2 compliant endpoints 15. Add devices individually; customer-managed devices cannot be added through bulk operations 17.

Verify

Ensure Control Hub displays the newly generated Line ID (user part and domain part), SIP Username, SIP Password, and Outbound Proxy address 14.

Rollback

Delete the device lines under Configure Lines, then delete the device in Control Hub, and remove SIP line data from the hardware 11.

A workspace (shared usage: lobby, door, paging zone, common-area phone) + A third-party SIP device I configure by hand with SIP credentials from Control Hub (door phone, pager, ATA, generic SIP phone or gateway)

Do

In Control Hub, go to Management > Devices > Add device, select Shared usage, choose New workspace, name the workspace, select the Customer Managed Devices type, choose the vendor (or generic profile), enter the MAC address, and assign calling service, location, and a phone number 9​15. Ensure device limits are respected: a professional-license workspace supports up to 5 customer-managed devices, while a common area workspace license permits only 1 device 27. Add each device individually without bulk tooling 17.

Verify

Verify that Control Hub presents the Line ID, SIP Username, SIP Password, and Outbound Proxy address 14.

Rollback

Delete the device lines from Configure Lines, delete the device entity from the workspace in Control Hub, and wipe SIP line credentials from the physical device 11.

Step 5 Capture credentials and server details

A Cisco phone (MPP or other Cisco device) that Webex Calling manages natively

Do

No manual SIP credentials need to be captured; onboarding relies on direct MAC address association or activation codes 38.

Verify

Suggested check: Verify that the activation code is noted if one was generated in Control Hub.

Rollback

Suggested rollback: No credentials need to be purged.

A Poly, Yealink, Snom or AudioCodes device from the supported list, configured by Webex through a provisioning URL

Do

No manual SIP credentials need to be captured; the endpoint receives a locked provisioning configuration directly from Webex Calling 28.

Verify

Suggested check: Verify the device MAC address is correctly entered in Control Hub.

Rollback

Suggested rollback: No credentials need to be purged.

A third-party SIP device I configure by hand with SIP credentials from Control Hub (door phone, pager, ATA, generic SIP phone or gateway)

Do

Immediately copy and securely record the Line ID (both user part and domain part), SIP Username, SIP Password, and Outbound Proxy address displayed on the confirmation screen 14. This confirmation dialog is the last time the SIP password can be seen in full 19. Maintain strict custody of these credentials, as the customer owns the SIP credentials and bears full liability for fraud resulting from security compromises 10.

Verify

Confirm that the Line ID user and domain parts, SIP Username, SIP Password, and Outbound Proxy are recorded before closing the dialog 14​19.

Rollback

If the password is misplaced or exposed, navigate in Control Hub to Management > Devices, select the device Details, click Reset Password, and copy the newly generated credential 20.

Step 6 Configure the physical endpoint

A Cisco phone (MPP or other Cisco device) that Webex Calling manages natively

Do

If the phone was provisioned using an activation code, power on the device and enter the code on the physical handset 38.

Verify

Suggested check: Confirm that the phone downloads its configuration and displays the assigned user or workspace line.

Rollback

Suggested rollback: Factory reset the phone using its hardware interface to clear the activation status.

A Poly, Yealink, Snom or AudioCodes device from the supported list, configured by Webex through a provisioning URL

Do

Reset the endpoint to its factory default settings prior to configuring deployment parameters 32. Configure the phone to point to the regional Webex provisioning URL for its specific vendor 45:

  • On Yealink: Access the web interface, open Settings > Auto Provision, input the regional Server URL (such as https://yealink.sipflash.com for the US), and click Auto Provision Now 60.
  • On Poly: Open Advanced admin settings, configure the provisioning boot server to Static, set the server type to HTTPS, and enter the regional URL in the server address field (such as https://plcm.sipflash.com for the US) 44.

Verify

Confirm that the endpoint reboots and applies its provisioned profile; for Yealink, clicking Auto Provision Now initiates a reboot and provisioning cycle 60.

Rollback

Perform a factory default reset on the endpoint to purge the Webex provisioning URL and reset configuration parameters 32.

A third-party SIP device I configure by hand with SIP credentials from Control Hub (door phone, pager, ATA, generic SIP phone or gateway)

Do

Log in to the physical device management interface and enter the SIP configuration fields using Cisco's mapping:

  • Map the Line ID user part to the device address or user name 13.
  • Map the SIP Username to the authentication user ID or register name 13.
  • Map the SIP Password to the authentication password 13.
  • Map the Outbound Proxy to the outbound proxy address 13.
  • Map the Line ID domain part to the SIP server address 13.
  • Enable DNS SRV so the endpoint can resolve the Outbound Proxy domain 12.
  • Configure Port to 0 and Transport to TLS on both the outbound proxy and the SIP server configuration entries 21.
  • Configure SRTP to offer AES_CM_128_HMAC_SHA1_80 53.

When configuring an Algo device, enter the SIP Extension from the Line ID user part, SIP Domain from the Line ID domain part, Authentication ID from the SIP Username, Authentication Password from the SIP Password, and Outbound Proxy from Control Hub 4. On Algo's Advanced SIP tab, set SDP SRTP Offer to Standard and SDP SRTP Offer Crypto Suite to AES_CM_128_HMAC_SHA1_80 5.

Verify

Check the endpoint's internal status screen to verify active SIP registration; on Algo devices, confirm a successful registration on the device's Status tab 6.

Rollback

Remove the Webex SIP credentials, Outbound Proxy, and line configuration from the physical device 11.

Step 7 Add additional lines

A Cisco phone (MPP or other Cisco device) that Webex Calling manages natively

Do

Verify

Suggested check: Additional line configuration falls outside this workflow.

Rollback

Suggested rollback: No line changes to reverse.

A Poly, Yealink, Snom or AudioCodes device from the supported list, configured by Webex through a provisioning URL

Do

Configure primary, shared, or monitored lines for the device in Control Hub as needed 7.

Verify

Suggested check: Verify the additional line registrations show on the handset screen.

Rollback

Suggested rollback: Remove the newly added shared or monitored lines in Control Hub.

A third-party SIP device I configure by hand with SIP credentials from Control Hub (door phone, pager, ATA, generic SIP phone or gateway)

Do

To add a shared line, open the device in Control Hub, select Configure Lines from the Device Management tile, add a shared port configuration, and save 24. On the physical device, configure the added line using the SIP Username, SIP Password, and Outbound Proxy saved from the initial line 24.

Verify

Inspect the endpoint status interface to confirm the additional SIP line registers successfully 6.

Rollback

Under Configure Lines in Control Hub, remove the shared line, and delete the corresponding line settings from the physical device 11.

Step 8 Confirm registration and operational status

A Cisco phone (MPP or other Cisco device) that Webex Calling manages natively

Do

Verify

Suggested check: Check the physical device screen to ensure the phone displays its extension and network registration status.

Rollback

Suggested rollback: Reset network configuration or reapply activation settings if registration fails.

A Poly, Yealink, Snom or AudioCodes device from the supported list, configured by Webex through a provisioning URL

Do

Locate the endpoint in the Control Hub device list to monitor its operational status 55. If the device fails to register or complete basic calls, open a support ticket with TAC, which handles basic SIP troubleshooting and registration verification for managed third-party hardware 57.

Verify

Verify that the device list in Control Hub displays a valid operational status for the third-party endpoint 55.

Rollback

Suggested rollback: Verify device network reachability and recheck the regional provisioning URL in the phone settings 45.

A third-party SIP device I configure by hand with SIP credentials from Control Hub (door phone, pager, ATA, generic SIP phone or gateway)

Do

Inspect the device's local administrative interface directly to verify SIP registration status 6. Do not expect detailed device status reporting in Control Hub, as Cisco documents detailed status views only for RoomOS devices and Cisco IP phones on PhoneOS 4.0.1 or later 56. All registration and feature troubleshooting must be handled directly by the customer or endpoint vendor, as Cisco Technical Support does not investigate customer-managed device issues 18.

Verify

Confirm that the physical device web interface or status tab reflects an active, registered state 6.

Rollback

Suggested rollback: Check device credentials against the recorded SIP settings and retest DNS SRV resolution 12.

Step 9 Manage day-two device settings

A Cisco phone (MPP or other Cisco device) that Webex Calling manages natively

Do

Modify device settings at the organization or location level in Control Hub as necessary, then resync the device from Control Hub or from the device settings menu so changes take effect 48.

Verify

Verify that updated settings are applied to the handset following the resync operation 48.

Rollback

Revert the modified parameter in Control Hub and execute another resync 48.

A Poly, Yealink, Snom or AudioCodes device from the supported list, configured by Webex through a provisioning URL

Do

Inspect your tenant to determine whether device settings can be modified for your specific model in Control Hub, and note that the device settings article states Poly and Yealink devices are available as Webex Calling managed devices while pointing AudioCodes configuration to its own site 46. If settings are adjusted in Control Hub, resync the phone from Control Hub or its settings menu for the configuration to take effect 48. Do not attempt management via third-party device management suites, as the endpoint runs a locked Webex configuration 28.

Verify

Verify that any changed setting is reflected on the device following a resync 48.

Rollback

Revert the altered configuration option in Control Hub and resync the endpoint 48.

A third-party SIP device I configure by hand with SIP credentials from Control Hub (door phone, pager, ATA, generic SIP phone or gateway)

Do

Perform all administrative changes directly on the endpoint hardware, as configuration is maintained manually 10. If administrative personnel depart or a credential compromise is suspected, rotate the SIP password in Control Hub by browsing to Management > Devices, selecting the device Details, and clicking Reset Password 20. Immediately copy the newly generated password and update the authentication password field on the physical device 20​13.

Verify

Confirm that the endpoint re-registers successfully with the newly applied SIP password on its status page 6.

Rollback

If the updated password fails, execute Reset Password in Control Hub again to generate another credential, as previously issued passwords cannot be viewed 19​20.

Step 10 Decommission endpoints

A Cisco phone (MPP or other Cisco device) that Webex Calling manages natively

Do

Verify

Suggested check: Endpoint decommissioning can be done by deleting the device from Control Hub and resetting the device to factory defaults.

Rollback

Suggested rollback: Re-add the device by MAC address or activation code 38.

A Poly, Yealink, Snom or AudioCodes device from the supported list, configured by Webex through a provisioning URL

Do

Check the device model against the end-of-life schedule before removing it from Control Hub, because an end-of-life device cannot be reprovisioned once deleted and must be replaced with a supported alternative 30​31. If decommissioning is intended, delete the device from Control Hub and perform a factory reset on the physical hardware 32​31.

Verify

Confirm that the device is removed from the Control Hub device list 55.

Rollback

Models not subject to end of life can be re-onboarded via MAC address provisioning, but reprovisioning is blocked for models past their end-of-life dates 31.

A third-party SIP device I configure by hand with SIP credentials from Control Hub (door phone, pager, ATA, generic SIP phone or gateway)

Do

Under Configure Lines, remove each configured line, then delete the device entry in Control Hub 11. On the physical device, remove the SIP line credentials, Outbound Proxy, and server definitions for every line that was deleted 11.

Verify

Inspect the physical endpoint interface to verify that all Webex SIP registration data and credentials have been erased 11.

Rollback

Re-create the device in Control Hub, capturing the newly generated SIP credentials and configuring them on the physical unit 14​13.

Applicability

Applies to: Cisco Webex Calling, Algo SIP endpoints, and Cisco Control Hub. Deployments: multi-tenant. Sources checked 2026-09-30. Cisco multiplatform devices require software version 11.3.1MES5 or later, or 11.3.1 SR2 or later for activation-code entry 39​37. Third-party device provisioning URLs differ by vendor and region across locations including the US, UK, EU, EUN, AU, CA, JP, KSA, and India 45.

What remains uncertain

Whether account manager approval is required specifically for the customer-managed devices group is not covered by the sources below. Specific network signaling ports and media destination port ranges are not covered by the sources below. The root certificates required by third-party devices to validate the TLS signaling connection are not covered by the sources below. Emergency calling features, locations, and callback configuration for customer-managed endpoints are not covered by the sources below. Functional differences between the Generic SIP Phone and Generic SIP Gateway profiles are not covered by the sources below. Specific menu navigation paths for AudioCodes and Snom endpoints are not covered by the sources below. Licensing requirements beyond workspace device limits are not covered by the sources below.

Sources

  1. 1
    Using the listed third-party devices on Webex Calling requires approval from the Cisco account manager to enable them for provisioning in Control Hub.
    Supported devices for Webex Calling · section 'List of supported third-party devices', introductory sentences · Checked 2026-09-30
  2. 2
    Algo requires its devices to run firmware 3.4.4 or later to register to Webex Calling.
    Cisco Webex Registration Guide · introductory requirements · Checked 2026-09-30
  3. 3
    Algo states that its first-generation 8180, 8028 and 8128 models lack TLS and SRTP support and cannot register to Webex Calling.
    Cisco Webex Registration Guide · limitations / exceptions list · Checked 2026-09-30
  4. 4
    On an Algo device the SIP Domain is the part of the Webex Line ID after the @, the SIP Extension is the part before it, the Authentication ID is the Webex SIP Username, the Authentication Password is the Webex SIP Password, and the Outbound Proxy is the address shown in Control Hub.
    Cisco Webex Registration Guide · Algo device configuration, Basic Settings SIP tab field table · Checked 2026-09-30
  5. 5
    Algo instructs setting the SDP SRTP Offer to Standard and the SDP SRTP Offer Crypto Suite to AES_CM_128_HMAC_SHA1_80 on the Advanced SIP tab when registering to Webex Calling.
    Cisco Webex Registration Guide · Algo device configuration, Advanced Settings, Advanced SIP tab · Checked 2026-09-30
  6. 6
    Algo's guide has the installer confirm a successful registration on the Algo device's own Status tab.
    Cisco Webex Registration Guide · Algo device configuration, final verification step · Checked 2026-09-30
  7. 7
    Cisco-managed third-party devices can be assigned to users or workspaces and support primary lines, shared lines and monitored lines.
    Cisco managed third-party device support on Webex Calling · section 'Onboard third party devices', capability bullets · Checked 2026-09-30
  8. 8
    To add a customer-managed device to a user, the administrator goes to Management, Devices, Add device in Control Hub, selects Personal usage, names the owner, chooses Customer Managed Devices as the device type, selects the device vendor, enters the MAC address, and confirms the disclaimer before saving.
    Add your customer managed device · section 'Add customer-managed device to user', numbered steps · Checked 2026-09-30
  9. 9
    To add a customer-managed device to a new workspace, the administrator goes to Management, Devices, Add device, selects Shared usage then New workspace, names the workspace, chooses the customer-managed device type, vendor and MAC address, and assigns the calling service, location and phone number.
    Add your customer managed device · section 'Add customer-managed device to new workspace', numbered steps · Checked 2026-09-30
  10. 10
    For a customer-managed device the customer provisions the device manually, owns the SIP authentication credential, and is responsible for any fraud arising from a failure to secure it.
    Add your customer managed device · section 'Get started with customer-managed devices', disclaimer · Checked 2026-09-30
  11. 11
    Removing a customer-managed device means deleting its lines under Configure Lines and then the device in Control Hub, and the administrator must also remove the SIP line data from the physical device for every line removed.
    Add your customer managed device · deletion steps and the note that follows them · Checked 2026-09-30
  12. 12
    A customer-managed device must be provisioned to use DNS SRV, which resolves the domain given as the Outbound Proxy.
    Add your customer managed device · device provisioning notes following the field-mapping table · Checked 2026-09-30
  13. 13
    Cisco's field-mapping example puts the Line ID user part in the phone's address or user name, the SIP Username in the authentication user ID or register name, the SIP Password in the authentication password, the Outbound Proxy in the outbound proxy address, and the Line ID domain part in the SIP server address.
    Add your customer managed device · field-mapping table with Poly (Line 1) and Yealink (Account1) columns · Checked 2026-09-30
  14. 14
    After a customer-managed device is added, Control Hub displays the Line ID (a user part and a domain part), the SIP Username, the SIP Password and the Outbound Proxy address.
    Add your customer managed device · section 'Add customer-managed device to user', final step and field table · Checked 2026-09-30
  15. 15
    Customer-managed devices offer two generic SIP profiles, Generic SIP Phone and Generic SIP Gateway, intended for SIP-TLS 1.2 compliant devices.
    Add your customer managed device · section 'Get started with customer-managed devices' · Checked 2026-09-30
  16. 16
    Cisco says minimum firmware requirements apply to customer-managed devices and refers the reader to the third-party vendor's documentation for them.
    Add your customer managed device · section 'Get started with customer-managed devices' · Checked 2026-09-30
  17. 17
    Customer-managed devices are not supported when adding devices in bulk.
    Add your customer managed device · section 'Get started with customer-managed devices' · Checked 2026-09-30
  18. 18
    Cisco Technical Support does not investigate issues with devices that connect through the customer-managed provisioning option.
    Add your customer managed device · section 'Get started with customer-managed devices' · Checked 2026-09-30
  19. 19
    The confirmation shown when a customer-managed device is added is the last time the SIP password can be seen in full.
    Add your customer managed device · section 'Add customer-managed device to user', note after the final step · Checked 2026-09-30
  20. 20
    The SIP password of a customer-managed device is regenerated from Management, Devices, the device's Details, Reset Password, and the new password must be copied when it is shown.
    Add your customer managed device · password reset steps · Checked 2026-09-30
  21. 21
    In Cisco's Poly and Yealink example, both the Outbound Proxy and Server 1 entries on a customer-managed device are set to Port 0 and Transport TLS.
    Add your customer managed device · device provisioning notes following the field-mapping table · Checked 2026-09-30
  22. 22
    The customer-managed device option lets an enterprise administrator provision third-party SIP devices such as door phones, overhead pagers, analog adapters and digital fax solutions on Webex Calling.
    Add your customer managed device · section 'Get started with customer-managed devices' · Checked 2026-09-30
  23. 23
    Every third-party device added as a customer-managed device must support the Webex Calling security requirements.
    Add your customer managed device · section 'Get started with customer-managed devices' · Checked 2026-09-30
  24. 24
    A shared line is added to a customer-managed device from the device's Configure Lines page by adding a shared port configuration, and the SIP username, password and Outbound Proxy saved from the first line are used for the added line when provisioning the physical device.
    Add your customer managed device · shared line steps (Device Management tile, Configure Lines) · Checked 2026-09-30
  25. 25
    Setting the port to 0 alongside the DNS SRV instruction implies the device is meant to learn the signalling port from the SRV record rather than from a statically entered port.inferred
    Add your customer managed device · device provisioning notes following the field-mapping table · Checked 2026-09-30
  26. 26
    The customer-managed group of the supported-devices list names Algo, 2N, Grandstream, CyberData, Axis and Singlewire endpoints.
    Supported devices for Webex Calling · section 'List of supported third-party devices', customer-managed devices rows · Checked 2026-09-30
  27. 27
    A workspace with a professional workspace license can have up to five customer-managed devices, and a workspace with a common area workspace license can have only one device.
    Add your customer managed device · section 'Add customer-managed device to new workspace' · Checked 2026-09-30
  28. 28
    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.
    Cisco managed third-party device support on Webex Calling · section 'Onboard third party devices', capability bullets · Checked 2026-09-30
  29. 29
    Cisco's supported-devices article for Webex Calling lists supported Cisco devices and supported third-party devices separately, and within the third-party list it has a separate customer-managed group for door phones, intercoms, speakers and pagers.
    Supported devices for Webex Calling · sections 'List of supported Cisco devices' and 'List of supported third-party devices' · Checked 2026-09-30
  30. 30
    As of the 22 September 2026 revision, Cisco lists Poly VVX 101, 201, 301, 311, 401, 411, 501 and 601 as end of life on 31 March 2026, and lists Yealink SIP-T40G and W52P with an end-of-life date of 30 September 2026 and Yealink SIP-T42S, T46S and T48S with 31 March 2027.
    Supported devices for Webex Calling · section 'End of Life announcement for Cisco Managed Devices', device tables · Checked 2026-09-30
  31. 31
    Once a Cisco-managed third-party device reaches its end-of-life date it no longer receives configuration updates and no new provisioning changes are permitted, and a device removed from Control Hub after that date cannot be reprovisioned.
    Supported devices for Webex Calling · section 'End of Life announcement for Cisco Managed Devices', policy provisions · Checked 2026-09-30
  32. 32
    For AudioCodes, Poly, Snom and Yealink devices, the manual deployment instructions begin by resetting the phone to factory default settings.
    Cisco managed third-party device support on Webex Calling · section 'Manual deployment instructions', first step under each vendor · Checked 2026-09-30
  33. 33
    Yealink, Poly and Snom devices on Webex Calling do not support video calling, unified call history, cloud directories, Webex meeting support, hot desking, layout configuration or device templates, visual voicemail, remote log collection, or time of day mode.
    Supported devices for Webex Calling · section 'Limitations' · Checked 2026-09-30
  34. 34
    Once the third-party devices are exposed to the customer, an administrator provisions them by MAC address as managed devices through Control Hub.
    Cisco managed third-party device support on Webex Calling · section 'Onboard third party devices' · Checked 2026-09-30
  35. 35
    Call media to Webex Calling is SRTP over UDP to destination port ranges that include 8500 to 8699 and 19560 to 65535.
    Port Reference Information for Webex Calling · connection table, row 'Call media to Webex Calling' · Checked 2026-09-30
  36. 36
    Cisco states that the use of third-party devices exists to facilitate customer migrations to Webex Calling.
    Supported devices for Webex Calling · section 'List of supported third-party devices', introductory sentences · Checked 2026-09-30
  37. 37
    A Cisco multiplatform device must be running firmware 11.3.1 SR2 or later for a user to enter an activation code on the device.
    Configure and manage Webex Calling devices · section 'Add a phone to a user' · Checked 2026-09-30
  38. 38
    In Control Hub an administrator assigns devices to users and workspaces and can add a Cisco phone either by MAC address or by generating an activation code to enter on the device.
    Configure and manage Webex Calling devices · section 'Add a phone to a user' · Checked 2026-09-30
  39. 39
    A Cisco multiplatform device must run software version 11.3.1MES5 or later to be used with Webex Calling.
    Supported devices for Webex Calling · section 'List of supported Cisco devices' · Checked 2026-09-30
  40. 40
    Cisco IP phones connected to the Webex cloud gain device-type-dependent features that include One Button to Join, Webex Meetings access, Webex directory and contact search, Webex user presence, and serviceability requests.
    Webex features available on Cisco IP Phones · section 'Webex features available on Cisco IP Phones' · Checked 2026-09-30
  41. 41
    Cisco states that modems are not supported in Webex Calling.
    Supported devices for Webex Calling · section 'List of supported third-party devices', note after the AudioCodes ATA rows · Checked 2026-09-30
  42. 42
    Poly devices on Webex Calling additionally do not support device settings, software channels, or call park extensions, the last with the exception of the Poly Trio C60.
    Supported devices for Webex Calling · section 'Limitations', Poly list · Checked 2026-09-30
  43. 43
    The supported third-party list includes Poly VVX 150, 250, 350 and 450, Poly CCX 400, 500, 505, 600 and 700, Poly Edge E series, Poly Trio 8300, 8800 and C60, and Poly ATA 400 and 402.
    Supported devices for Webex Calling · section 'List of supported third-party devices', Poly rows · Checked 2026-09-30
  44. 44
    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).
    Cisco managed third-party device support on Webex Calling · section 'Manual deployment instructions', Poly devices · Checked 2026-09-30
  45. 45
    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.
    Cisco managed third-party device support on Webex Calling · section 'Manual deployment instructions', URL lists under AudioCodes, Poly, Snom and Yealink · Checked 2026-09-30
  46. 46
    The device settings article has a 'Third-party device settings' section stating that Poly and Yealink devices are available as Webex Calling managed devices, and it points AudioCodes configuration to AudioCodes' own site.
    Configure and modify device settings in Webex Calling · section 'Third-party device settings' · Checked 2026-09-30
  47. 47
    The supported-devices article says Yealink and Poly third-party devices have no device settings through Control Hub and no configuration overrides.disputed
    Supported devices for Webex Calling · section 'List of supported third-party devices', provisioning and deployment bullets · Checked 2026-09-30
  48. 48
    After device settings are changed in Control Hub, devices must be resynced from Control Hub or from the device's own settings menu for the change to take effect.
    Configure and modify device settings in Webex Calling · sections 'Configure settings for organizations' and 'Configure settings for locations', closing note · Checked 2026-09-30
  49. 49
    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
    Cisco managed third-party device support on Webex Calling · section 'Onboard third party devices', capability bullets; section 'Supported device settings' · Checked 2026-09-30
  50. 50
    Devices send SIP-TLS call signalling to the Webex Calling service subnets on TCP destination port 8934.
    Port Reference Information for Webex Calling · connection table, row 'Call signaling to Webex Calling (SIP TLS)', Devices entry · Checked 2026-09-30
  51. 51
    Cisco recommends turning off SIP Application Layer Gateway or similar SIP-aware functionality on routers and firewalls in the path to Webex Calling.
    Port Reference Information for Webex Calling · section 'Firewall configuration', SIP Application Layer Gateway paragraph · Checked 2026-09-30
  52. 52
    The supported third-party list includes Snom D3, D7 and D8 series phones, AudioCodes 425HD, 445HD and C450HD phones, and AudioCodes MP-1xx, MP-2xx and MP-5xx analog adapters.
    Supported devices for Webex Calling · section 'List of supported third-party devices', SNOM and AudioCodes rows · Checked 2026-09-30
  53. 53
    The SRTP key suite Webex Calling supports for secure media is AES_CM_128_HMAC_SHA1_80.
    Security requirements for Webex Calling · section 'Requirements for SIP and media' · Checked 2026-09-30
  54. 54
    Cisco-managed third-party devices support standard SIP phone features only, with no advanced feature support.
    Cisco managed third-party device support on Webex Calling · section 'Onboard third party devices', capability bullets · Checked 2026-09-30
  55. 55
    Cisco-managed third-party devices appear in the existing Control Hub device list alongside Cisco devices, and their statuses are displayed there.
    Cisco managed third-party device support on Webex Calling · section 'Onboard third party devices' · Checked 2026-09-30
  56. 56
    Cisco's article on the detailed device status view in Control Hub describes it for devices running RoomOS and for Cisco IP phones running PhoneOS 4.0.1 and later.
    View device statuses on Control Hub · section 'View statuses' · Checked 2026-09-30
  57. 57
    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.
    Cisco managed third-party device support on Webex Calling · section 'Onboard third party devices', support bullets · Checked 2026-09-30
  58. 58
    Webex Calling supports TLS 1.2 and TLS 1.3 for secure SIP.
    Security requirements for Webex Calling · section 'Requirements for SIP and media' · Checked 2026-09-30

Documents

tier 2 current vendor documentation

Add your customer managed device

Cisco · 2026-02-09 · accessed 2026-09-30

tier 2 current vendor documentation

Cisco managed third-party device support on Webex Calling

Cisco · 2026-07-28 · accessed 2026-09-30

tier 2 current vendor documentation

Configure and manage Webex Calling devices

Cisco · 2026-09-01 · accessed 2026-09-30

tier 2 current vendor documentation

Configure and modify device settings in Webex Calling

Cisco Webex · 2026-07-28 · accessed 2026-09-25

tier 2 current vendor documentation

Port Reference Information for Webex Calling

Cisco · 2026-09-08 · accessed 2026-09-30

tier 2 current vendor documentation

Security requirements for Webex Calling

Cisco · 2026-04-28 · accessed 2026-09-30

tier 2 current vendor documentation

Supported devices for Webex Calling

Cisco · 2026-09-22 · accessed 2026-09-30

tier 2 current vendor documentation

View device statuses on Control Hub

Cisco · 2026-03-24 · accessed 2026-09-30

tier 2 current vendor documentation

Webex features available on Cisco IP Phones

Cisco · 2026-01-12 · accessed 2026-09-30

tier 3 vendor-maintained repositories

Cisco Webex Registration Guide

Algo Communication Products Ltd. · 2026-09-22 · accessed 2026-09-25

Cite this page

APA

WarmTransfer. (2026, September 30). Setting up third-party SIP phones on Webex Calling. WarmTransfer. https://warmtransfer.net/guides/webex-calling-third-party-phone-setup

BibTeX

@misc{warmtransfer-webex-calling-third-party-phone-setup,
  title  = {Setting up third-party SIP phones on Webex Calling},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/guides/webex-calling-third-party-phone-setup},
  note   = {Verified 2026-09-30}
}