WarmTransfer
webex calling · published

Webex Calling device onboarding and activation codes

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

In Control Hub, an administrator adds a Webex Calling phone to a user or workspace either by entering its MAC address or by generating an activation code to enter on the device 36. Every Webex Calling device type can register by MAC address, whereas registration via activation code is available only for a subset of models 35.

Activation codes and supported models

Only specific Control Hub administrator roles have permission to generate activation codes 22. Each physical device requires its own unique activation code 21. Control Hub generates a 16-digit code that can be copied, emailed, or printed for entry on the device 16.

Activation codes have specific expiration windows based on the hardware category:

  • For Multiplatform (MPP) phones, an activation code expires after 30 days 17.
  • For Room devices, an activation code expires after 7 days 18.

The models documented as capable of registering using an activation code are:

  • Cisco IP Phone 6800, 7800, and 8800 Series (audio and video) 20
  • Cisco IP Conference Phone 7832 and 8832 20
  • Cisco Desk Phone 9800 Series 20
  • Cisco Wireless Phone 9821 20
  • Cisco Video Phone 8875 20

To enter an activation code on an MPP phone, the device must run firmware 11.3.1 SR2 or later 19. Separately, Cisco documentation states that a Cisco multiplatform device must run software version 11.3.1MES5 or later to be supported on Webex Calling 39. WarmTransfer's reading of the sources is that two Cisco articles state different MPP firmware floors for different purposes (11.3.1MES5 for support, 11.3.1 SR2 for entering an activation code), so an answer about minimum firmware should name which floor it means 34.

When onboarding an Analog Telephone Adapter (ATA) by activation code, all network settings must be configured before activating the device 9. Supported Cisco analog adapter models for Webex Calling are ATA191, ATA192, VG400, VG410, and VG420 8.

Provisioning and registration flow

In the provisioning flow documented by Cisco TAC, an MPP phone first contacts activate.cisco.com over HTTPS to perform activation 41. Following activation, the device receives a profile rule pointing to cisco.sipflash.com, from which it downloads its configuration file 42.

If a local DHCP server supplies a TFTP server address (using options such as 66, 150, 159, or 160), the MPP phone attempts to provision from that local TFTP server rather than Webex Calling servers, which causes provisioning to fail 27.

During the SIP registration phase, the phone first resolves a _sips._tcp SRV record for its Webex Calling access SBC domain; DNS resolution failures at this step cause registration failure 46. A normal, successful Webex Calling MPP registration exchange consists of an initial REGISTER answered with a 401 Unauthorized challenge, followed by an authenticated REGISTER containing digest credentials answered with 200 OK 45.

TAC diagnostic procedures collect Problem Report Tool (PRT) logs directly through the phone's web interface 43.

Workspace limits and device reassignment

Device assignment limits depend on the workspace license edition:

  • A workspace licensed with a Professional workspace license supports up to 5 Cisco Desk Phones, Cisco MPP phones, ATAs, or third-party devices 60.
  • A workspace licensed with a Common area workspace license supports only 1 device 59.

When reassigning an existing phone from one user or workspace to another, an administrator deletes the device assignment and factory resets the phone if it has not been reset already 44. Once reset, the phone displays the Activation Code screen 44.

Control Hub displays a "Webex Aware" status indication when a device has onboarded to the Webex platform and can use Webex-supported features 58. From a user's device view in Control Hub, an administrator can execute "Apply Changes" to have the phone retrieve and apply configuration changes, or trigger "Reboot" to force a device reboot 7. For bulk onboarding operations, Cisco recommends preparing the CSV file using a recently generated template 24.

Board, Desk, and Room devices

Webex Calling is supported on Board, Desk, and Room devices running RoomOS 10.x or newer 48. Webex Calling can be added to workspaces containing Board, Desk, or Room devices, but it cannot be added to Room USB devices 47.

On initial boot, a Board, Desk, or Room device checks for and installs RoomOS software updates, after which it presents a setup wizard where the 16-digit activation code is submitted 49. Applying a RoomOS device configuration template is a one-time operation; later edits made to the template are not applied to devices that have already received it 56.

Third-party device limitations

Cisco-managed third-party devices (such as Poly, Yealink, and AudioCodes) cannot be onboarded using activation codes or EDOS 5. Instead, administrators add them in Control Hub using their MAC address and complete deployment manually 5. Manual deployment requires factory resetting the device, accessing its web interface or local menu, entering the regional provisioning server URL, and rebooting the handset to trigger auto-provisioning 3.

Third-party devices carry several operational constraints:

  • They lack features available on Cisco devices, such as video calling, unified call history, cloud directories, hot desking, visual voicemail, and remote log collection 1.
  • Their configuration is locked, preventing administration via third-party vendor management tools 2.
  • Cisco TAC provides support only for basic SIP troubleshooting (such as basic calling and registration); TAC does not provide RMAs, third-party warranty support, or troubleshooting for third-party-specific features 6.

Device configuration and settings hierarchy

Webex Calling settings follow a defined configuration hierarchy: settings can be configured at the organization, location, and device levels 52. Device-level settings override location-level settings, and location-level settings override organization-level defaults 52. If default settings at the organization or location level are modified, any devices configured with custom overrides will not receive those updates 25. The device settings catalog covers ATA 191/192, VG4xx ATAs, DECT, Wi-Fi phones, and third-party Poly, Yealink, and AudioCodes hardware 51.

Control Hub also provides settings templates (covering general, messaging, meeting, calling, and Vidcast categories) applied at group or location levels, limited to 50 templates per type per organization 53. Calling settings templates configure user-level properties including caller ID, voicemail, music on hold, and announcement languages 53. WarmTransfer's reading of the sources is that "settings templates" (user and service policy for groups and locations) and "device configuration templates" (device parameters applied to selected devices) appear to be separate Control Hub features, so a question about device templates should not be answered from settings template documentation 57.

Software upgrade channels

Webex Calling manages MPP firmware distribution via upgrade channels:

  • Stable: The default software channel for MPP phones, Cisco ATA 191/192, and listed Yealink devices 14.
  • Preview: Installs upcoming production software 2 weeks prior to its release into the Stable channel 13.
  • Stable Delay: Installs an older software release previously in Stable and updates approximately once a quarter; Cisco advises restricting this channel to active support investigations with an open case 15.

External administrators cannot modify the MPP software upgrade channel 12. Channel assignments made on a single device take effect within a few minutes, whereas bulk channel modifications (supporting up to 1000 selected devices) apply during the regular maintenance window 11.

A Cisco announcement dated 11 August 2026 details a PhoneOS upgrade from 4.1.1 to 5.0.1 for Cisco 8875 and 9800 Series phones on Webex Calling 40. Cisco announced a migration of DECT DBS-110/210 base stations to new SBCs, which requires base firmware 5.1.3 or higher and enables device status, analytics and troubleshooting in Control Hub 26.

Enterprise-to-MPP firmware migration

Phones running Cisco Unified Communications Manager enterprise firmware can be converted to MPP firmware through Control Hub 29​32. The source enterprise firmware must be version 14.1 or later 29. Cisco IP Phone 8821 and 8831 models are not eligible for enterprise-to-MPP migration 30.

The enterprise-to-MPP workflow proceeds through several stages: importing devices via a CSV template, validating model eligibility, preparing for migration to generate migration licenses, completing the migration automatically or manually, and tracking progress in Control Hub 32. Automatic migration requires Cloud Connected UC, a wired Ethernet connection, and executes in batches capped at 200 devices 28. Wireless-capable phones lose their Wi-Fi configuration during MPP firmware conversion, requiring a wired connection during migration and manual Wi-Fi reconfiguration afterwards 31.

Alternatively, a migration license can be generated on the fly during onboarding by entering the Control Hub activation code directly into the enterprise phone's activation code field, triggering a reboot and registration 38.

See also

Applicability

Applies to: Cisco Webex Calling, Cisco Webex devices (RoomOS), Cisco Control Hub, Cisco Webex Calling with MPP phones, and Cisco Webex Calling devices. Deployments: multi-tenant. Sources checked 2026-09-25. The enterprise-to-MPP firmware migration requires phones to be running enterprise firmware version 14.1 or later 29. MPP phones require firmware 11.3.1 SR2 or later to register by activation code 19, and version 11.3.1MES5 or later for Webex Calling support 39. Board, Desk, and Room devices require RoomOS version 10.x or newer 48. DECT DBS-110/210 base stations require base firmware 5.1.3 or higher for the SBC migration 26. PhoneOS upgrade 5.0.1 applies to Cisco 8875 and 9800 Series phones 40.

What remains uncertain

The specific list of Control Hub administrator roles permitted to generate device activation codes is not covered by the sources below. The specific Yealink device models that support the Stable upgrade channel are not covered by the sources below.

See also

Related to

Referenced by

  • Webex Calling virtual lines — Virtual lines are assigned to MPP phones and Webex App only as non-primary lines after the device is onboarded

Sources

  1. 1
    Third-party devices on Webex Calling lack features available on Cisco devices, including video calling, unified call history, cloud directories, hot desking, visual voicemail and remote log collection.
    Supported devices for Webex Calling · third-party device limitations section · Checked 2026-09-25
  2. 2
    Cisco-managed third-party devices have a locked configuration and cannot be managed with the third-party vendor's own management tools.
    Cisco managed third-party device support on Webex Calling · device capabilities list and constraints · Checked 2026-09-25
  3. 3
    Manual deployment of a Cisco-managed third-party phone involves factory resetting it, opening its web interface or menu, entering the region-specific provisioning server URL, and rebooting to auto-provision.
    Cisco managed third-party device support on Webex Calling · administrator tasks / manual deployment procedure · Checked 2026-09-25
  4. 4
    Cisco-managed third-party devices are provisioned individually in Control Hub; bulk operations are not supported for them.
    Cisco managed third-party device support on Webex Calling · device capabilities / provisioning and deployment list · Checked 2026-09-25
  5. 5
    Cisco-managed third-party devices (such as Poly, Yealink and AudioCodes) cannot be onboarded with activation codes or EDOS; they are provisioned by MAC address in Control Hub and deployed manually.
    Cisco managed third-party device support on Webex Calling · device capabilities / provisioning and deployment list; administrator tasks · Checked 2026-09-25
  6. 6
    Cisco TAC supports Cisco-managed third-party devices only for basic SIP troubleshooting such as registration and basic calling, with no RMA, third-party warranty or third-party feature support.
    Cisco managed third-party device support on Webex Calling · support section · Checked 2026-09-25
  7. 7
    From a user's device page an admin can issue 'Apply Changes' (the phone downloads and applies configuration changes) or 'Reboot' (forces a reboot).
    Configure and manage Webex Calling devices · section 'Manage a device for a user' · Checked 2026-09-25
  8. 8
    Supported Cisco analog adapters for Webex Calling are ATA191, ATA192, VG400, VG410 and VG420.
    Supported devices for Webex Calling · Analog Telephone Adapters section · Checked 2026-09-25
  9. 9
    When onboarding an ATA by activation code, all network settings must be configured before the device is activated.
    Generate an activation code for a device · note in the user-device procedure · Checked 2026-09-25
  10. 10
    After an ATA is activated, its network settings can no longer be accessed on the device.
    Generate an activation code for a device · note in the user-device procedure, sentence following the ATA network-settings note · Checked 2026-09-25
  11. 11
    A channel change on a single device takes effect within a few minutes, while a bulk channel change (up to 1000 selected devices) is applied during the regular maintenance window.
    Devices software upgrade channels · procedures for single device and multiple devices · Checked 2026-09-25
  12. 12
    External administrators cannot change the MPP software upgrade channel.
    Devices software upgrade channels · notes / restrictions · Checked 2026-09-25
  13. 13
    The Preview channel installs the upcoming default software two weeks before it reaches the Stable channel.
    Devices software upgrade channels · section describing the Preview channel · Checked 2026-09-25
  14. 14
    Stable is the default software upgrade channel for Webex Calling MPP phones, Cisco ATA 191/192 and the listed Yealink models.
    Devices software upgrade channels · section describing the Stable channel; applicability list at top · Checked 2026-09-25
  15. 15
    The Stable Delay channel installs a software version that was previously in Stable and updates less often, typically about once a quarter; Cisco advises using it only during investigations with a support case open.
    Devices software upgrade channels · section describing the Stable Delay channel; best practices · Checked 2026-09-25
  16. 16
    The activation code Control Hub generates is 16 digits and can be copied, emailed or printed for entry on the device.
    Generate an activation code for a device · procedures for workspace devices and for user devices · Checked 2026-09-25
  17. 17
    A device activation code generated in Control Hub expires after 30 days for MPP phones.
    Generate an activation code for a device · introductory section of the article · Checked 2026-09-25
  18. 18
    A device activation code generated in Control Hub expires after 7 days for Room devices.
    Generate an activation code for a device · introductory section of the article · Checked 2026-09-25
  19. 19
    Cisco multiplatform phones must run firmware 11.3.1 SR2 or later for a user to enter an activation code on the phone.
    Configure and manage Webex Calling devices · section 'Add and assign devices in bulk' · Checked 2026-09-25
  20. 20
    The models listed as able to register by activation code are Cisco IP Phone 6800, 7800 and 8800 Series (audio and video), IP Conference Phone 7832 and 8832, Desk Phone 9800 Series, Wireless Phone 9821 and Video Phone 8875.
    Configure and manage Webex Calling devices · section 'Add and assign devices in bulk', list following the MAC/activation-code sentence · Checked 2026-09-25
  21. 21
    Each device needs its own unique activation code.
    Generate an activation code for a device · introductory section of the article · Checked 2026-09-25
  22. 22
    Only specific Control Hub administrator roles can generate activation codes.
    Generate an activation code for a device · introductory section of the article (links to account roles article) · Checked 2026-09-25
  23. 23
    For bulk device CSV import for Webex Calling users, the mandatory fields are Username, Type, Device Type, and Model when the device type is IP.
    Configure and manage Webex Calling devices · section 'Add and assign devices in bulk' · Checked 2026-09-25
  24. 24
    Cisco recommends preparing the bulk device CSV from a recently generated template.
    Configure and manage Webex Calling devices · section 'Add and assign devices in bulk' · Checked 2026-09-25
  25. 25
    When organization or location device defaults are changed, devices that have custom settings overriding those defaults are not updated.
    Configure and modify device settings in Webex Calling · organization-level / location-level settings procedure · Checked 2026-09-25
  26. 26
    Cisco announced a migration of DECT DBS-110/210 base stations to new SBCs, which requires base firmware 5.1.3 or higher and enables device status, analytics and troubleshooting in Control Hub.
    Announcements for the Webex Calling Devices · announcement 'Cisco DECT DBS-110/210 SBC Migration' (July 9, 2026) · Checked 2026-09-25
  27. 27
    If the DHCP server hands the phone a TFTP server address (options such as 66, 150, 159 or 160), the MPP phone tries to provision from that TFTP server instead of the Webex Calling servers and fails to provision.
    Troubleshoot MPP Phone in WxC for Provision and Registration · troubleshooting section on provisioning issues (DHCP/TFTP scenario) · Checked 2026-09-25
  28. 28
    Automatic enterprise-to-MPP migration requires a wired connection and Cloud Connected UC, and Control Hub triggers it in batches of at most 200 devices.
    Migrate enterprise phone to Webex Calling phone firmware · migration methods section (automatic migration) · Checked 2026-09-25
  29. 29
    Control Hub's enterprise-to-MPP phone migration requires the phones to be on enterprise firmware 14.1 or later.
    Migrate enterprise phone to Webex Calling phone firmware · prerequisites section · Checked 2026-09-25
  30. 30
    Cisco IP Phone 8821 and 8831 are not eligible for enterprise-to-MPP migration.
    Migrate enterprise phone to Webex Calling phone firmware · supported models section, note on ineligible 8800 devices · Checked 2026-09-25
  31. 31
    When wireless-capable phones are converted to MPP firmware they lose their Wi-Fi settings, so Cisco advises connecting them by Ethernet during migration and reconfiguring Wi-Fi afterwards.
    Migrate enterprise phone to Webex Calling phone firmware · wireless phones note · Checked 2026-09-25
  32. 32
    The Control Hub enterprise-to-MPP migration workflow runs: add devices via CSV template, verify device eligibility, prepare for migration (which generates licenses), complete migration automatically or manually, then monitor status in Control Hub.
    Migrate enterprise phone to Webex Calling phone firmware · workflow / procedure sections · Checked 2026-09-25
  33. 33
    Cisco stops allowing provisioning of a device model on Webex Calling 12 months before its published End-of-Hardware date, and devices stop working at End-of-Hardware.
    Supported devices for Webex Calling · end-of-life / end-of-support policy section · Checked 2026-09-25
  34. 34
    Two Cisco articles state different MPP firmware floors for different purposes (11.3.1MES5 for support, 11.3.1 SR2 for entering an activation code), so an answer about 'minimum firmware' should name which floor it means.inferred
    Supported devices for Webex Calling · Cisco multiplatform phones section, compared with cisco-help-n9r1aac section 'Add and assign devices in bulk' · Checked 2026-09-25
  35. 35
    Every Webex Calling device type can be registered by MAC address; activation-code registration is available only for a subset of models.
    Configure and manage Webex Calling devices · section 'Add and assign devices in bulk' · Checked 2026-09-25
  36. 36
    In Control Hub an administrator adds a Webex Calling phone to a user or workspace either by entering its MAC address or by generating an activation code to be entered on the device.
    Configure and manage Webex Calling devices · sections 'Add a phone to a user' and 'Add a phone to a new workspace' · Checked 2026-09-25
  37. 37
    Control Hub line configuration for a Webex Calling phone supports at most 16 accounts (lines) on a device.
    Configure and manage Webex Calling devices · section 'Configure lines - Add and reorder lines' · Checked 2026-09-25
  38. 38
    For an enterprise phone being migrated to MPP, a migration license can be generated on the fly by entering the Control Hub activation code in the phone's activation code field, after which the phone reboots and registers.
    Generate migration license for devices using activation code flow onboarding · purpose statement and onboarding procedure · Checked 2026-09-25
  39. 39
    The supported-devices article says a Cisco multiplatform device must run software version 11.3.1MES5 or later to be supported on Webex Calling.
    Supported devices for Webex Calling · Cisco multiplatform phones section · Checked 2026-09-25
  40. 40
    An announcement dated 11 August 2026 covers a PhoneOS firmware upgrade from 4.1.1 to 5.0.1 for Cisco 8875 and 9800 Series phones on Webex Calling.
    Announcements for the Webex Calling Devices · announcement 'Cisco PhoneOS 5.0.1 Firmware Upgrade' (August 11, 2026) · Checked 2026-09-25
  41. 41
    In Cisco's TAC-documented provisioning flow, an MPP phone first calls home to activate.cisco.com over HTTPS for activation.
    Troubleshoot MPP Phone in WxC for Provision and Registration · provisioning flow section · Checked 2026-09-25
  42. 42
    After activation the phone receives a profile rule pointing to cisco.sipflash.com, from which it downloads its configuration.
    Troubleshoot MPP Phone in WxC for Provision and Registration · provisioning flow section · Checked 2026-09-25
  43. 43
    TAC's MPP troubleshooting procedure collects Problem Report Tool (PRT) logs from the phone's web interface.
    Troubleshoot MPP Phone in WxC for Provision and Registration · diagnostic / log collection section · Checked 2026-09-25
  44. 44
    To reuse a phone already assigned to one Webex Calling user or workspace for another, the admin follows a reassignment procedure that includes deleting the device and factory resetting it if it was not already reset, after which the phone shows the Activation Code screen.
    Configure and manage Webex Calling devices · section 'Reassigning an existing phone to another user or device' · Checked 2026-09-25
  45. 45
    A successful Webex Calling MPP registration includes an initial REGISTER answered by 401 Unauthorized, followed by an authenticated REGISTER with digest credentials answered by 200 OK.
    Troubleshoot MPP Phone in WxC for Provision and Registration · registration process section · Checked 2026-09-25
  46. 46
    Before registering, the phone resolves a _sips._tcp SRV record for its Webex Calling access SBC domain; a DNS resolution failure is a documented cause of registration failure.
    Troubleshoot MPP Phone in WxC for Provision and Registration · registration process section and troubleshooting indicators (Couldn't resolve host) · Checked 2026-09-25
  47. 47
    Webex Calling can be added to workspaces with Board, Desk or Room devices but not to Room USB devices.
    Activate a Board, Desk, or Room series device · notes following the activation procedure · Checked 2026-09-25
  48. 48
    Webex Calling is supported on Board, Desk and Room devices running RoomOS 10.x or newer.
    Supported devices for Webex Calling · RoomOS / Board, Room and Desk devices section · Checked 2026-09-25
  49. 49
    A Board, Desk or Room device checks for and installs RoomOS updates at first boot and then runs a setup wizard in which the 16-digit activation code is entered.
    Activate a Board, Desk, or Room series device · activation procedure · Checked 2026-09-25
  50. 50
    The TAC technote lists TLS port 8934 for MPP phone signalling to the Webex Calling access SBCs.
    Troubleshoot MPP Phone in WxC for Provision and Registration · key URLs and ports section · Checked 2026-09-25
  51. 51
    The Webex Calling device settings article includes settings for ATA 191/192, VG4xx ATAs, DECT, Wi-Fi phones and third-party Poly, Yealink and AudioCodes devices.
    Configure and modify device settings in Webex Calling · device-specific settings tables · Checked 2026-09-25
  52. 52
    Webex Calling device settings can be set at organization, location and device level; device-level settings override location settings, which override organization settings.
    Configure and modify device settings in Webex Calling · overview section on configuration levels · Checked 2026-09-25
  53. 53
    Control Hub settings templates (general, messaging, meeting, calling, Vidcast) apply to groups or locations, with up to 50 templates of each type per organization; calling templates cover user settings such as voicemail, caller ID, music on hold and announcement language.
    Configure settings templates in Control Hub · overview, template types and limits sections · Checked 2026-09-25
  54. 54
    The RoomOS device configurations article lists Desk Phone 9800 Series support only for organization and location defaults, not for configuration templates.disputed
    Device configurations for Board, Desk, and Room Series devices (title as reported at fetch) · supported devices / requirements section · Checked 2026-09-25
  55. 55
    The 9800 Series and 8875 configuration article lists configuration templates, alongside organization, location, multi-device and individual settings, as a way to configure these phones on Webex Calling.disputed
    Configure 9800 Series and 8875 Phones on Control Hub · configuration methods sections · Checked 2026-09-25
  56. 56
    Applying a RoomOS device configuration template is a one-time operation: later edits to the template do not change devices it was already applied to.
    Device configurations for Board, Desk, and Room Series devices (title as reported at fetch) · section on applying templates · Checked 2026-09-25
  57. 57
    'Settings templates' (user and service policy for groups and locations) and 'device configuration templates' (device parameters applied to selected devices) appear to be separate Control Hub features, so a question about 'device templates' should not be answered from the settings-templates article.inferred
    Configure settings templates in Control Hub · whole article scope, compared with cisco-help-pyfxdf-roomos-config-templates · Checked 2026-09-25
  58. 58
    Control Hub shows a 'Webex Aware' indication for a device that has onboarded to the Webex platform and can use Webex-supported features.
    Configure and manage Webex Calling devices · section 'Manage a device for a user' · Checked 2026-09-25
  59. 59
    A workspace with a common area workspace license can have only one device.
    Configure and manage Webex Calling devices · section 'Add and assign devices in bulk', sentence following the Professional workspace limit · Checked 2026-09-25
  60. 60
    A workspace with a Professional workspace license can have up to 5 Cisco Desk Phones, Cisco MPP phones, ATAs or third-party devices.
    Configure and manage Webex Calling devices · section 'Add and assign devices in bulk' · Checked 2026-09-25

Documents

tier 2 current vendor documentation

Activate a Board, Desk, or Room series device

Cisco Webex · 2026-04-21 · accessed 2026-09-25

tier 2 current vendor documentation

Announcements for the Webex Calling Devices

Cisco Webex · 2026-09-15 · 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 9800 Series and 8875 Phones on Control Hub

Cisco Webex · 2026-08-06 · accessed 2026-09-25

tier 2 current vendor documentation

Configure and manage Webex Calling devices

Cisco Webex · 2026-09-01 · accessed 2026-09-25

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

Configure settings templates in Control Hub

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

tier 2 current vendor documentation

Device configurations for Board, Desk, and Room Series devices (title as reported at fetch)

Cisco Webex · 2026-04-21 · accessed 2026-09-25

tier 2 current vendor documentation

Devices software upgrade channels

Cisco Webex · 2026-06-19 · accessed 2026-09-25

tier 2 current vendor documentation

Generate an activation code for a device

Cisco Webex · 2026-01-12 · accessed 2026-09-25

tier 2 current vendor documentation

Generate migration license for devices using activation code flow onboarding

Cisco Webex · 2024-11-05 · accessed 2026-09-25

tier 2 current vendor documentation

Migrate enterprise phone to Webex Calling phone firmware

Cisco Systems, Inc. (Webex Help Center) · 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

Troubleshoot MPP Phone in WxC for Provision and Registration

Cisco Systems · 2024-04-18 · accessed 2026-09-25

Cite this page

APA

WarmTransfer. (2026, September 25). Webex Calling device onboarding and activation codes. WarmTransfer. https://warmtransfer.net/knowledge/webex-calling-device-onboarding

BibTeX

@misc{warmtransfer-webex-calling-device-onboarding,
  title  = {Webex Calling device onboarding and activation codes},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-calling-device-onboarding},
  note   = {Verified 2026-09-25}
}