# Setting up the Webex App for Unified CM calling Systems: Webex App For Unified CM and Control Hub administrators setting up Webex App for on-premises calling. Canonical: https://warmtransfer.net/guides/cucm-webex-app-calling-setup Last verified: 2026-10-01 Webex App provides calling through [Cisco Unified CM](https://warmtransfer.net/knowledge/cisco-unified-cm) either as a direct SIP softphone or by cross-launching Cisco Jabber[^28][^34]. Deployment involves configuring service discovery, device profiles, access control groups, and Control Hub calling behaviors[^1][^11][^52]. ## Before you start - Ensure user accounts are managed in a Webex organization in Control Hub with a paid subscription[^47]. - Calling in Webex App (Unified CM) does not require a specific license assignment for calling itself, but softphone registrations count toward Unified CM device licensing[^36][^37]. - A user with 3 or more apps or devices requires Cisco Unified Workspace Licensing (CUWL) perpetual licensing or a Flex Calling subscription[^37]. - Note that Webex App does not support Extension Mobility[^45]. ## What changes by situation - Which app places the Unified CM calls? Webex App registers to Unified CM as the softphone; Keep Jabber for calling and launch it from Webex App. - Do users need Unified CM calling off the corporate network without a VPN? Yes, through Expressway Mobile and Remote Access; No, only on the corporate network or over VPN. - How are the Webex App softphone devices created in Unified CM? Webex App creates the device when the user signs in; An administrator creates each CSF, BOT, TCT or TAB device. - How does Webex App find Unified CM? Use the user's email domain for SRV lookup; Use a UC Manager profile. ## Step 1: Confirm prerequisites **Webex App registers to Unified CM as the softphone** ### Do Confirm that Unified CM runs Release 11.5(1) SU3 or later for desktop clients[^54]. If iOS endpoints are used, verify that Unified CM runs 11.5(1) SU8 or a later SU on the 11.5 train, or 12.5(1) SU3 or a later SU on the 12.5 train for Apple Push Notification support[^55]. Confirm that the user's Webex email account matches the mail ID of the Unified CM end user to support centralized call history[^29]. ### Verify Suggested check: Verify that Unified CM meets the minimum release versions and that email attributes match across systems. ### Rollback Suggested rollback: No configuration changes are made in this step. **Keep Jabber for calling and launch it from Webex App** ### Do Confirm that users are configured in a paid Webex organization managed in Control Hub and already place calls using Cisco Jabber[^34][^47]. ### Verify Suggested check: Verify that pilot user accounts appear in Control Hub and run functional Jabber clients. ### Rollback Suggested rollback: No configuration changes are made in this step. ## Step 2: Onboard cluster to Cloud-Connected UC **Webex App registers to Unified CM as the softphone + Webex App creates the device when the user signs in** ### Do In Control Hub, go to Services > Connected UC and click Get Started on the UC Management card[^17]. For Unified CM 12.5(1)SU2 and later, connect the built-in agent by running `utils ucmgmt organization ` followed by `utils ucmgmt agent enable` in the CLI[^13]. For Unified CM releases before 12.5(1)SU2, install the Control Hub-generated COP file on all cluster nodes without rebooting[^14]. Ensure nodes have internet access directly or via proxy to `*.ucmgmt.cisco.com` and `*.webex.com`[^15]. ### Verify Verify that the onboarded nodes appear in Connected UC Inventory and assign them to a cluster group, checking that the installation log verification code matches Control Hub[^18]. ### Rollback Delete the cluster from Control Hub to uninstall the Cloud-Connected UC agent and telemetry module from all cluster nodes[^16]. **Webex App registers to Unified CM as the softphone + An administrator creates each CSF, BOT, TCT or TAB device** ### Do Skip this step, as Cloud-Connected UC is not required for manual softphone provisioning unless using the Control Hub Jabber migration wizard[^35]. ### Verify Suggested check: Confirm manual provisioning is planned. ### Rollback Suggested rollback: No changes to revert. **Keep Jabber for calling and launch it from Webex App + Webex App creates the device when the user signs in** ### Do Skip this step, as cross-launch calling relies on existing Cisco Jabber infrastructure[^34]. ### Verify Suggested check: Confirm that Jabber remains the active client. ### Rollback Suggested rollback: No changes to revert. **Keep Jabber for calling and launch it from Webex App + An administrator creates each CSF, BOT, TCT or TAB device** ### Do Skip this step, as cross-launch calling relies on existing Cisco Jabber infrastructure[^34]. ### Verify Suggested check: Confirm that Jabber remains the active client. ### Rollback Suggested rollback: No changes to revert. ## Step 3: Configure trusted certificates **Webex App registers to Unified CM as the softphone + Yes, through Expressway Mobile and Remote Access** ### Do Deploy SHA-256 or stronger certificates on Unified CM chaining to an OS-trusted CA or pre-deployed root[^22]. Webex App does not provide prompts to accept untrusted certificates[^20]. WarmTransfer's reading of the sources is that untrusted certificates stop sign-in[^33]. If using self-signed certificates for MRA, assign different common names to the Unified CM Tomcat and CallManager certificates, as Expressway cannot trust 2 self-signed certificates with identical common names[^21]. Include the Unified CM registration domains as subject alternative names on the Expressway-E certificate[^19]. ### Verify Suggested check: Verify that the Expressway-E certificate contains all Unified CM registration domains in its Subject Alternative Names list. ### Rollback Suggested rollback: Re-import previous certificates onto Expressway-E and Unified CM. **Webex App registers to Unified CM as the softphone + No, only on the corporate network or over VPN** ### Do Ensure the Unified CM Tomcat certificate uses SHA-256 or a later secure signature algorithm[^22]. Webex App does not prompt users to accept untrusted certificates[^20]. WarmTransfer's reading of the sources is that an untrusted certificate is likely to prevent phone-services sign-in rather than prompt the user[^33]. Ensure the certificate chains to a CA trusted by the operating system, or deploy any self-signed certificate to the OS in advance[^22]. ### Verify Suggested check: Verify that endpoint operating systems trust the Unified CM certificate without certificate security alerts. ### Rollback Suggested rollback: Revert to the previously installed certificates in Unified CM. **Keep Jabber for calling and launch it from Webex App + Yes, through Expressway Mobile and Remote Access** ### Do Skip this step, as Cisco Jabber retains its existing certificate validation behavior[^34]. ### Verify Suggested check: Confirm Jabber signs in successfully. ### Rollback Suggested rollback: No changes to revert. **Keep Jabber for calling and launch it from Webex App + No, only on the corporate network or over VPN** ### Do Skip this step, as Cisco Jabber retains its existing certificate validation behavior[^34]. ### Verify Suggested check: Confirm Jabber signs in successfully. ### Rollback Suggested rollback: No changes to revert. ## Step 4: Configure UC services and service profiles **Webex App registers to Unified CM as the softphone** ### Do In Unified CM, configure a CTI UC service so Webex App can retrieve user-associated devices[^26]. Optionally configure a voicemail UC service and voicemail pilot number pointing to Cisco Unity Connection[^60]. Attach the UC services to a service profile, optionally setting it as the cluster default[^51]. Note that Webex App uses the same Unified CM-hosted client configuration file as Jabber[^50]. Do not use Visual Voicemail on both Jabber and Webex App concurrently[^61]. ### Verify Suggested check: Check the end user profile in Unified CM to confirm the service profile and CTI service are assigned. ### Rollback Suggested rollback: Disassociate the UC services from the service profile or restore the previous service profile assignment. **Keep Jabber for calling and launch it from Webex App** ### Do Skip this step, as Jabber utilizes its current UC service profile configuration[^34]. ### Verify Suggested check: Confirm Jabber continues to retrieve its existing UC service profile. ### Rollback Suggested rollback: No changes to revert. ## Step 5: Publish DNS service discovery records **Webex App registers to Unified CM as the softphone + Yes, through Expressway Mobile and Remote Access** ### Do Publish `_cisco-uds._tcp.` on internal DNS pointing to Unified CM[^52]. On public DNS, publish `_collab-edge._tls.` pointing to Expressway-E[^39][^53]. Ensure that `_cisco-uds` records are not resolvable outside the internal network, or MRA negotiation through Expressway-E will fail to start[^41]. Avoid 192.168.x.x internal DNS servers for Android clients[^2]. ### Verify Suggested check: Query `_collab-edge._tls.` publicly to confirm resolution, and verify that `_cisco-uds._tcp.` does not resolve on external DNS. ### Rollback Suggested rollback: Remove the published public and internal DNS SRV records. **Webex App registers to Unified CM as the softphone + No, only on the corporate network or over VPN** ### Do Publish the internal DNS SRV record `_cisco-uds._tcp.` pointing to Unified CM, using port 8443 as referenced in Cisco guidance[^52]. Set `` to the user email domain or the voice services domain[^59]. Avoid using a 192.168.x.x address as the internal DNS server for Webex on Android, as the client may mistakenly treat the network as external MRA Wi-Fi[^2]. ### Verify Suggested check: Perform an `nslookup` or `dig` query internally for `_cisco-uds._tcp.` and confirm it returns Unified CM nodes. ### Rollback Suggested rollback: Remove the `_cisco-uds._tcp.` SRV record from internal DNS servers. **Keep Jabber for calling and launch it from Webex App + Yes, through Expressway Mobile and Remote Access** ### Do Skip this step, retaining existing DNS records used by Cisco Jabber[^34]. ### Verify Suggested check: Verify that Jabber continues to discover services via existing DNS records. ### Rollback Suggested rollback: No changes to revert. **Keep Jabber for calling and launch it from Webex App + No, only on the corporate network or over VPN** ### Do Skip this step, retaining existing DNS records used by Cisco Jabber[^34]. ### Verify Suggested check: Verify that Jabber continues to discover services via existing DNS records. ### Rollback Suggested rollback: No changes to revert. ## Step 6: Configure UC Manager profiles **Webex App registers to Unified CM as the softphone + Use the user's email domain for SRV lookup** ### Do Skip this step, as service discovery will rely on the default email domain without a profile[^9]. ### Verify Suggested check: Confirm calling behavior uses the email domain default. ### Rollback Suggested rollback: No changes to revert. **Webex App registers to Unified CM as the softphone + Use a UC Manager profile** ### Do In Control Hub, go to Management > Organization Settings > UC Manager Profiles > Add Profile[^57]. Enter the Voice Services Domain, technical requirement when SRV records do not use the login email domain and mandatory for MRA[^59]. If Webex App user IDs differ from Unified CM user IDs, or if ILS is not enabled across clusters, enter the UDS Server address[^58]. ### Verify Confirm that the new profile is listed under UC Manager Profiles in Control Hub[^57]. ### Rollback Delete the profile using the ellipsis menu on the UC Manager Profiles page in Control Hub[^57]. **Keep Jabber for calling and launch it from Webex App + Use the user's email domain for SRV lookup** ### Do Skip this step, as cross-launch relies on Jabber calling configuration[^34]. ### Verify Suggested check: Confirm cross-launch configuration is selected. ### Rollback Suggested rollback: No changes to revert. **Keep Jabber for calling and launch it from Webex App + Use a UC Manager profile** ### Do Skip this step, as cross-launch relies on Jabber calling configuration[^34]. ### Verify Suggested check: Confirm cross-launch configuration is selected. ### Rollback Suggested rollback: No changes to revert. ## Step 7: Provision softphone devices and user accounts **Webex App registers to Unified CM as the softphone + Webex App creates the device when the user signs in** ### Do In Control Hub, activate Webex app Provisioning for Unified CM Calling under Services > Connected UC > Service Management[^4]. Under Services > Calling > Client Settings > Unified CM Settings, enable Allow auto-provisioning for Webex and choose desktop and mobile, desktop only, or mobile only[^4]. Assign the user the Register to Unified Communications Manager license, avoiding assigning a Webex Calling license unless Webex Calling is required[^6]. Ensure the user has an associated primary extension in Unified CM and that their Unified CM user ID or email matches their Webex identity service record[^5][^8]. Assign the user to the Standard CCM End Users and Standard CTI Enabled groups[^1]. ### Verify Have a user sign in to Webex App and confirm that the matching CSF, BOT, TCT, or TAB device is automatically created in Unified CM[^3]. ### Rollback Turn off the Allow auto-provisioning toggle in Control Hub and delete auto-created devices in Unified CM, waiting 5 to 10 minutes before re-provisioning the same device type[^8]. **Webex App registers to Unified CM as the softphone + An administrator creates each CSF, BOT, TCT or TAB device** ### Do In Unified CM Administration, navigate to Device > Phone > Add New and select Cisco Unified Client Services Framework (CSF) for desktop, Cisco Dual Mode for iPhone (TCT), Cisco Dual Mode for Android (BOT), or Cisco Jabber for Tablet (TAB)[^27][^28]. Ensure TCT, BOT, and TAB device names begin with the uppercase prefix, contain at most 15 characters, and use only A-Z, 0-9, period, underscore, or hyphen[^38]. Under Device Information, configure the Owner User ID and directory number, then associate the device under User Management > End User > Device Association[^46]. Add the user to the Standard CCM End Users and Standard CTI Enabled access control groups[^1]. ### Verify Verify that the configured softphone device appears in the user's Controlled Devices list in Unified CM Administration[^24]. ### Rollback Suggested rollback: Delete the created softphone devices and remove device associations from the user profile. **Keep Jabber for calling and launch it from Webex App + Webex App creates the device when the user signs in** ### Do Skip this step, as user accounts utilize existing Cisco Jabber devices[^34]. ### Verify Suggested check: Verify that Jabber device configurations remain active in Unified CM. ### Rollback Suggested rollback: No changes to revert. **Keep Jabber for calling and launch it from Webex App + An administrator creates each CSF, BOT, TCT or TAB device** ### Do Skip this step, as user accounts utilize existing Cisco Jabber devices[^34]. ### Verify Suggested check: Verify that Jabber device configurations remain active in Unified CM. ### Rollback Suggested rollback: No changes to revert. ## Step 8: Enable Apple and Google push notifications **Webex App registers to Unified CM as the softphone + Yes, through Expressway Mobile and Remote Access** ### Do In Cisco Unified CM Administration, go to Advanced Features > Cisco Cloud Onboarding and select Enable Push Notifications[^48]. Verify that Expressway runs Release X12.6 or later to support push notifications over MRA[^32]. ### Verify Suggested check: Confirm that Push Notifications are checked in the administration interface and the external traversal system runs X12.6 or later. ### Rollback Uncheck Enable Push Notifications under Advanced Features > Cisco Cloud Onboarding in Unified CM Administration[^48]. **Webex App registers to Unified CM as the softphone + No, only on the corporate network or over VPN** ### Do In Cisco Unified CM Administration, go to Advanced Features > Cisco Cloud Onboarding and select Enable Push Notifications[^48]. Ensure Unified CM meets the minimum release requirements for Apple Push Notification support on iOS[^55]. ### Verify Suggested check: Check the Cloud Onboarding page in administration to confirm the push status is active. ### Rollback In Cisco Unified CM Administration, navigate to Advanced Features > Cisco Cloud Onboarding and uncheck Enable Push Notifications[^48]. **Keep Jabber for calling and launch it from Webex App + Yes, through Expressway Mobile and Remote Access** ### Do Skip this step, maintaining Jabber's existing push notification architecture[^34]. ### Verify Suggested check: Verify Jabber notifications function as configured. ### Rollback Suggested rollback: No changes to revert. **Keep Jabber for calling and launch it from Webex App + No, only on the corporate network or over VPN** ### Do Skip this step, maintaining Jabber's existing push notification architecture[^34]. ### Verify Suggested check: Verify Jabber notifications function as configured. ### Rollback Suggested rollback: No changes to revert. ## Step 9: Configure calling behavior in Control Hub **Webex App registers to Unified CM as the softphone + Use the user's email domain for SRV lookup** ### Do Configure calling behavior at the organization level under Services > Calling > Settings > Webex App in the Calling Behavior section, via group templates, or at the user level under Management > Users > user > Calling > Calling Behavior[^10][^11][^12]. Select Use the email domain of the user[^9]. ### Verify Suggested check: Verify in Control Hub that the target user's Calling Behavior displays "Use the email domain of the user". ### Rollback Suggested rollback: In Control Hub user settings, re-enable Use organization level settings to inherit organization defaults. **Webex App registers to Unified CM as the softphone + Use a UC Manager profile** ### Do Configure calling behavior at the organization level under Services > Calling > Settings > Webex App, via group templates, or per user under Management > Users > user > Calling > Calling Behavior[^10][^11][^12]. Select Use UC Manager Profile for calling and pick the configured profile from the dropdown[^9]. ### Verify Suggested check: Confirm that the user's Calling Behavior in Control Hub shows the assigned UC Manager Profile. ### Rollback Suggested rollback: Set the calling behavior back to organization default settings or clear the profile assignment. **Keep Jabber for calling and launch it from Webex App + Use the user's email domain for SRV lookup** ### Do In Control Hub, configure calling behavior at the organization, group, or user level and select Open Cisco Jabber from the Webex app[^10][^12][^34]. Unified CM registration of Webex App and cross-launch cannot be enabled together[^49]. ### Verify Suggested check: Verify that the cross-launch option is saved in Control Hub user calling settings. ### Rollback Deselect Open Cisco Jabber from the Webex app and reselect Calling in Webex App (Unified CM)[^49]. **Keep Jabber for calling and launch it from Webex App + Use a UC Manager profile** ### Do In Control Hub, configure calling behavior at the organization, group, or user level and select Open Cisco Jabber from the Webex app[^10][^12][^34]. Unified CM registration of Webex App and cross-launch cannot be enabled together[^49]. ### Verify Suggested check: Verify that the cross-launch option is saved in Control Hub user calling settings. ### Rollback Deselect Open Cisco Jabber from the Webex app and reselect Calling in Webex App (Unified CM)[^49]. ## Step 10: Test on the corporate network **Webex App registers to Unified CM as the softphone** ### Do In Webex App, Settings > Phone Services shows which calling service the user is signed in to[^63]. ### Verify Confirm that no registration warning icon appears in Webex App[^62]. If registration fails, hover over the icon to view the error details or click it to see recommended next steps such as signing in to phone services[^62]. Suggested check: Sign in to the client on the local network, then place, receive, hold, and transfer a test call. ### Rollback Suggested rollback: Sign out of phone services in the client and revert calling behavior in the management portal. **Keep Jabber for calling and launch it from Webex App** ### Do The calling behavior setting Open Cisco Jabber from the Webex app lets Unified CM users place calls in Jabber, launched from Webex App[^34]. ### Verify Verify that the call is handed off and placed using Cisco Jabber[^34]. Suggested check: Initiate an outbound call from the primary app and confirm the separate telephony client handles it. ### Rollback Suggested rollback: Revert calling behavior in the management portal if cross-launch fails to trigger. ## Step 11: Test off the corporate network **Webex App registers to Unified CM as the softphone + Yes, through Expressway Mobile and Remote Access** ### Do Ensure the Expressway traversal pair runs Release X8.11.4 or later[^30]. Note that MRA failover requires Unified CM Release 14.0 or later and Expressway Release X14.0 or later[^31][^56]. ### Verify Verify that Webex App registers through Expressway-E without a warning icon and completes calls[^62]. Suggested check: Disconnect the pilot endpoint from the local network and any secure tunnel, launch the client, and place and receive calls over the public internet. ### Rollback Suggested rollback: Disconnect the remote endpoint and re-verify connectivity on the local corporate network. **Webex App registers to Unified CM as the softphone + No, only on the corporate network or over VPN** ### Do Skip this step, as MRA is not deployed and off-network calling requires VPN access[^40]. ### Verify Suggested check: Confirm that remote users access telephony exclusively over VPN. ### Rollback Suggested rollback: No changes to revert. **Keep Jabber for calling and launch it from Webex App + Yes, through Expressway Mobile and Remote Access** ### Do Skip this step, as external connectivity is handled by Jabber's existing MRA deployment[^34]. ### Verify Suggested check: Confirm the separate telephony client registers externally. ### Rollback Suggested rollback: No changes to revert. **Keep Jabber for calling and launch it from Webex App + No, only on the corporate network or over VPN** ### Do Skip this step, as Jabber users connect externally via VPN[^34]. ### Verify Suggested check: Confirm the separate telephony client connects over VPN. ### Rollback Suggested rollback: No changes to revert. ## Step 12: Clear coexistence conflicts **Webex App registers to Unified CM as the softphone** ### Do Before expanding rollout, verify that any CTI remote device (CTI-RD) or Cisco Spark-RD device is removed for the user in Unified CM[^24][^64]. Confirm that Cisco Jabber is not registered to Unified CM in softphone mode on the same machine at the same time[^23][^65]. Do not configure 10-line support or mobile multiline on Unified CM for users who still use Jabber, as doing so causes phone services registration failure in Jabber[^42]. ### Verify Confirm that the user's active softphone devices remain registered in Controlled Devices without conflicting remote devices[^24][^66]. ### Rollback Suggested rollback: Re-add any required remote devices in Unified CM if legacy services require them. **Keep Jabber for calling and launch it from Webex App** ### Do Maintain Jabber line configurations within standard supported limits and avoid multiline configurations that exceed Jabber specifications[^42]. ### Verify Suggested check: Verify that the telephony client maintains phone service registration. ### Rollback Suggested rollback: No changes to revert. ## Applicability Applies to: Cisco Unified Communications Manager, Cisco Webex App, Cisco Webex Control Hub, Cisco Webex Cloud-Connected UC, Cisco Expressway, and Cisco Jabber. Deployments: on-premises, hybrid, and multi-tenant. Sources checked 2026-10-01. Calling in Webex App (Unified CM) requires Unified CM 11.5(1) SU3 or later for desktop softphones[^54]. Apple Push Notification support on iOS requires Unified CM 11.5(1) SU8 or later on the 11.5 train, or 12.5(1) SU3 or later on the 12.5 train[^55]. Mobile and Remote Access requires Expressway-C and Expressway-E traversal pairs at X8.11.4 or later[^30]. Push notifications over MRA require Expressway X12.6 or later[^32]. MRA failover requires Unified CM Release 14.0 or later and Expressway Release X14.0 or later[^31][^56]. Auto-provisioning requires Unified CM 11.5 or later, Webex App 41.12 or later, Expressway X14.0.2 or later, and Cloud-Connected UC activated for on-premises devices[^7]. ## What remains uncertain Expressway traversal zone configuration, external firewall traversal policies, certificate authority enrollment workflows, and IM and Presence integrations are not covered by the sources below. Whether the Expressway X14.0.2 minimum version for auto-provisioning applies to clusters that do not deploy MRA is not covered by the sources below. Specific contact center features supported when cross-launching Jabber versus native Webex App registration are not covered by the sources below. ## Sources [^1]: End users for Calling in Webex App (Unified CM) must be in at least the Standard CCM End Users and Standard CTI Enabled access control groups. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Configure Unified CM end users > Associate users with devices. Checked 2026-09-30. [^2]: Cisco advises against using a 192.168.x.x address as the internal DNS server for Webex on Android because the app may wrongly treat the network as MRA (external) Wi-Fi. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Deploy > Service discovery options (Android note). Checked 2026-09-30. [^3]: With auto-provisioning, signing in to Webex App on a new device creates the matching CSF, BOT, TCT or TAB device in Unified CM if it does not already exist. Source: [Auto-Provisioning of Webex App for Calling in Webex (Unified CM)](https://help.webex.com/en-US/article/ki34wo/Auto-Provisioning-of-Webex-App-for-Calling-in-Webex-(Unified-CM)), Overview; device types. Checked 2026-09-30. [^4]: Auto-provisioning is enabled by activating the Webex app Provisioning for Unified CM Calling service under Services > Connected UC > Service Management, then turning on Allow auto-provisioning for Webex under Services > Calling > Client Settings > Unified CM Settings and choosing desktop and mobile, desktop only or mobile only. Source: [Auto-Provisioning of Webex App for Calling in Webex (Unified CM)](https://help.webex.com/en-US/article/ki34wo/Auto-Provisioning-of-Webex-App-for-Calling-in-Webex-(Unified-CM)), Enable auto-provisioning. Checked 2026-09-30. [^5]: For auto-provisioning the Unified CM user ID or email must match the user's record in the Webex identity service. Source: [Auto-Provisioning of Webex App for Calling in Webex (Unified CM)](https://help.webex.com/en-US/article/ki34wo/Auto-Provisioning-of-Webex-App-for-Calling-in-Webex-(Unified-CM)), Prerequisites. Checked 2026-09-30. [^6]: Auto-provisioning requires the Register to Unified Communications Manager license assigned to the user in Control Hub, and a Webex Calling license should not be assigned unless the user needs Webex Calling. Source: [Auto-Provisioning of Webex App for Calling in Webex (Unified CM)](https://help.webex.com/en-US/article/ki34wo/Auto-Provisioning-of-Webex-App-for-Calling-in-Webex-(Unified-CM)), Prerequisites; Limitations. Checked 2026-09-30. [^7]: Auto-provisioning requires Unified CM 11.5 or later, Webex App 41.12 or later, Expressway X14.0.2 or later, and Cloud-Connected UC activated for on-premises devices. Source: [Auto-Provisioning of Webex App for Calling in Webex (Unified CM)](https://help.webex.com/en-US/article/ki34wo/Auto-Provisioning-of-Webex-App-for-Calling-in-Webex-(Unified-CM)), Prerequisites. Checked 2026-09-30. [^8]: Auto-provisioning needs the user to have a primary extension associated in Unified CM, and after a device is deleted the same device type should not be re-provisioned for 5 to 10 minutes. Source: [Auto-Provisioning of Webex App for Calling in Webex (Unified CM)](https://help.webex.com/en-US/article/ki34wo/Auto-Provisioning-of-Webex-App-for-Calling-in-Webex-(Unified-CM)), Limitations. Checked 2026-09-30. [^9]: For Unified CM users, calling behavior offers Use the email domain of the user (the default) or Use UC Manager Profile for calling with a profile chosen from a dropdown. Source: [Set up calling behavior](https://help.webex.com/en-us/article/1lvb42/Set-up-calling-behavior), For Unified CM users. Checked 2026-09-30. [^10]: Organization-level calling behavior is set in Control Hub under Services > Calling > Settings > Webex App in the Calling Behavior section, and group overrides are created as Webex App templates on the Templates tab. Source: [Set up calling behavior](https://help.webex.com/en-us/article/1lvb42/Set-up-calling-behavior), Organization level; Group level. Checked 2026-09-30. [^11]: Calling behavior can be set at organization level, overridden for a user group through a template, or overridden for an individual user by turning off Use organization level settings. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Deploy > Set up calling behavior and UC manager profiles in Control Hub. Checked 2026-09-30. [^12]: User-level calling behavior is set in Control Hub under Management > Users, selecting the user, then Calling > Calling Behavior. Source: [Set up calling behavior](https://help.webex.com/en-us/article/1lvb42/Set-up-calling-behavior), User level. Checked 2026-09-30. [^13]: From Unified CM 12.5(1)SU2 the Cloud-Connected UC agent is built in and is connected with the CLI commands utils ucmgmt organization and utils ucmgmt agent enable. Source: [Set up Webex Cloud-Connected UC for on-premises devices](https://help.webex.com/en-us/article/nzt6c0b/Set-up-Webex-Cloud-Connected-UC-for-on-premises-devices), Onboard Unified CM clusters > built-in agent. Checked 2026-09-30. [^14]: For Unified CM releases before 12.5(1)SU2, an agent COP file generated in Control Hub is installed on all nodes of the cluster, with no server or cluster reboot required. Source: [Set up Webex Cloud-Connected UC for on-premises devices](https://help.webex.com/en-us/article/nzt6c0b/Set-up-Webex-Cloud-Connected-UC-for-on-premises-devices), Onboard Unified CM clusters > agent COP file. Checked 2026-09-30. [^15]: Cloud-Connected UC nodes need internet access, directly or through a configured proxy, to *.ucmgmt.cisco.com and *.webex.com. Source: [Set up Webex Cloud-Connected UC for on-premises devices](https://help.webex.com/en-us/article/nzt6c0b/Set-up-Webex-Cloud-Connected-UC-for-on-premises-devices), Prerequisites > proxy and firewall. Checked 2026-09-30. [^16]: Deleting a cluster from Control Hub uninstalls the Cloud-Connected UC agent and telemetry module from all of its nodes. Source: [Set up Webex Cloud-Connected UC for on-premises devices](https://help.webex.com/en-us/article/nzt6c0b/Set-up-Webex-Cloud-Connected-UC-for-on-premises-devices), Delete a cluster from Control Hub. Checked 2026-09-30. [^17]: Cloud-Connected UC onboarding starts in Control Hub under Services > Connected UC by clicking Get Started on the UC Management card. Source: [Set up Webex Cloud-Connected UC for on-premises devices](https://help.webex.com/en-us/article/nzt6c0b/Set-up-Webex-Cloud-Connected-UC-for-on-premises-devices), Onboard Unified CM clusters. Checked 2026-09-30. [^18]: After agent installation, onboarded nodes appear in the Connected UC Inventory where they are assigned to a cluster group, and a verification code in the installation logs should match the one Control Hub displays. Source: [Set up Webex Cloud-Connected UC for on-premises devices](https://help.webex.com/en-us/article/nzt6c0b/Set-up-Webex-Cloud-Connected-UC-for-on-premises-devices), Cluster groups; verify onboarding. Checked 2026-09-30. [^19]: The Expressway-E certificate must include the Unified CM registration domains as subject alternative names. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Certificate requirements > Expressway-E. Checked 2026-09-30. [^20]: Unlike Jabber, Webex App does not prompt users with the option to accept an untrusted certificate. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Certificate requirements. Checked 2026-09-30. [^21]: For MRA with self-signed certificates, the Unified CM Tomcat and CallManager certificates must have different common names because Expressway cannot trust two self-signed certificates with the same CN. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Certificate requirements > MRA. Checked 2026-09-30. [^22]: Certificates using deprecated signature algorithms such as SHA-1 are not supported; Unified CM certificates must use SHA-256 or a later secure signature algorithm, and must chain to a CA known to the operating system or a self-signed certificate the administrator has deployed to the OS in advance. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Certificate requirements. Checked 2026-09-30. [^23]: Cisco's troubleshooting checklist says to confirm Jabber is not registered to Unified CM at the same time on the same machine as Webex App. Source: [Deployment guide for Calling in Webex App (Unified CM) - Manage and troubleshoot](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_0101.html), Manage and troubleshoot > troubleshooting checklist. Checked 2026-09-30. [^24]: Before opening a case, Cisco's checklist says to confirm any CTI-RD or Cisco Spark-RD device was removed from Unified CM for the user and that the user's devices are in Controlled Devices. Source: [Deployment guide for Calling in Webex App (Unified CM) - Manage and troubleshoot](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_0101.html), Manage and troubleshoot > troubleshooting checklist. Checked 2026-09-30. [^25]: CSF device names are limited to 15 characters using a-z, A-Z and 0-9. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Configure Unified CM end users > Create and configure Webex App softphone devices > device name table (CSF row). Checked 2026-09-30. [^26]: The CTI UC service gives Webex App the location of the CTI service, which retrieves the list of devices associated with the user. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Deploy > Configure UC services. Checked 2026-09-30. [^27]: Webex App softphone devices are created manually in Unified CM Administration under Device > Phone > Add New by selecting the matching phone type, and at least one device is needed for every user configured for Calling in Webex App (Unified CM). Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Configure Unified CM end users > Create and configure Webex App softphone devices. Checked 2026-09-30. [^28]: In softphone mode Webex App registers to Unified CM as a SIP device of product type Cisco Unified Client Services Framework (CSF) on desktop, TCT or BOT on mobile, and TAB on tablets. Source: [Deployment guide for Calling in Webex App (Unified CM)](https://help.webex.com/article/nj8v6wg/Deployment-guide-for-Calling-in-Webex-App-(Unified-CM)), Create and configure Webex App softphone devices. Checked 2026-09-30. [^29]: For centralized call history, the user's Webex email account must match the mail ID of the Unified CM end user. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Requirements > centralized call history. Checked 2026-09-30. [^30]: An Expressway-C and Expressway-E traversal pair at X8.11.4 or later is required for Calling in Webex App (Unified CM) over MRA. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Requirements > Expressway for Mobile and Remote Access. Checked 2026-09-30. [^31]: MRA failover for Calling in Webex App (Unified CM) requires Expressway Release X14.0 or later. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Requirements > Expressway for Mobile and Remote Access (MRA failover note). Checked 2026-09-30. [^32]: Push notifications for Webex App over MRA require Expressway X12.6 or later. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Requirements > Expressway for Mobile and Remote Access. Checked 2026-09-30. [^33]: Because Webex App gives users no option to accept an untrusted certificate, a Unified CM or Expressway certificate the endpoint OS does not already trust is likely to stop phone-services sign-in rather than prompt the user (inferred). Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Certificate requirements. Checked 2026-09-30. [^34]: Where an organization uses Jabber for calling, the calling behavior setting Open Cisco Jabber from the Webex app lets Unified CM users place calls in Jabber, launched from Webex App. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Deploy > Set up calling behavior and UC manager profiles in Control Hub. Checked 2026-09-30. [^35]: Control Hub has a Migrate Jabber to Webex app wizard under Services > Updates that sets calling behavior (email domain or UC Manager profile) for selected users of a Cloud-Connected UC cluster, and allows one migration task at a time. Source: [Migrate Jabber users with Cloud-Connected UC to Webex App](https://help.webex.com/en-US/article/nejw7ue/Migrate-Jabber-Users-with-Cloud-Connected-UC-to-Webex-app), Migrate Jabber users; limitations. Checked 2026-09-30. [^36]: User accounts must be managed in the Webex organization but do not need a specific license assignment to use Calling in Webex App (Unified CM). Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > License requirements. Checked 2026-09-30. [^37]: Webex App softphone registrations count toward Unified CM device licensing, and users with three or more apps or devices require CUWL perpetual licensing or a Flex Calling subscription. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > License requirements. Checked 2026-09-30. [^38]: TCT (iPhone), BOT (Android) and TAB (tablet) device names must begin with that uppercase prefix, use only A-Z, 0-9, period, underscore and hyphen, and be at most 15 characters. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Configure Unified CM end users > Create and configure Webex App softphone devices > device name table. Checked 2026-09-30. [^39]: Public DNS must carry _collab-edge._tls. SRV records so endpoints can discover the Expressway-E used for MRA, and Expressway supports calling for MRA-connected Webex clients on Windows, Mac, iOS and Android. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X14.3) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X14-3/mra/exwy_b_mra-deployment-guide-x143/exwy_m_requirements-for-mra.html), MRA requirements > DNS records > Public DNS; supported clients. Checked 2026-09-30. [^40]: MRA must be deployed on Expressway if Webex App users need to connect from outside the corporate network. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Deploy > Mobile and Remote Access. Checked 2026-09-30. [^41]: The _cisco-uds SRV records must not be resolvable outside the internal network, otherwise the client will not start MRA negotiation through Expressway-E. Source: [Mobile and Remote Access Through Cisco Expressway Deployment Guide (X14.3) - MRA Requirements and Prerequisites](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X14-3/mra/exwy_b_mra-deployment-guide-x143/exwy_m_requirements-for-mra.html), MRA requirements > DNS records > Local DNS. Checked 2026-09-30. [^42]: Ten-line support and mobile multiline do not work for Jabber, and adding either to Unified CM results in phone services registration failure on Jabber. Source: [Deployment guide for Calling in Webex App (Unified CM) - Overview of Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_01.html), Overview > multiline (Jabber note). Checked 2026-09-30. [^43]: Webex App supports up to 10 Unified CM lines on desktop and up to 8 on mobile (disputed). Source: [Deployment guide for Calling in Webex App (Unified CM) - Overview of Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_01.html), Overview > multiline. Checked 2026-09-30. [^44]: Some users may need advanced calling features not yet in Webex App, such as contact center features and multiline, and Cisco recommends cross-launching Jabber for them as an interim solution (disputed). Source: [Upgrade Jabber with IM and Presence to Webex App](https://help.webex.com/en-us/article/980p3k/Upgrade-Jabber-with-IM-and-Presence-to-Webex-App), Plan / cross-launch interim solution. Checked 2026-09-30. [^45]: Webex App does not support Extension Mobility. Source: [Deployment guide for Calling in Webex App (Unified CM) - Overview of Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_01.html), Overview > limitations. Checked 2026-09-30. [^46]: Each softphone device gets a directory number and an Owner User ID under Device Information, and the device is associated to the end user under User Management > End User > Device Association. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Configure Unified CM end users > Add a directory number to the device; Associate users with devices. Checked 2026-09-30. [^47]: Users of Calling in Webex App (Unified CM) must be in a Webex organization managed in Control Hub with a paid subscription. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Requirements > Webex organization. Checked 2026-09-30. [^48]: Push notifications are enabled in Unified CM Administration under Advanced Features > Cisco Cloud Onboarding by checking Enable Push Notifications, after which Unified CM uses the Apple or Google push service. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Configure Unified CM end users > Configure push notifications and recommended settings. Checked 2026-09-30. [^49]: Unified CM registration of Webex App and cross-launch cannot be enabled together; switching back requires disabling cross-launch and reselecting Calling in Webex App (Unified CM). Source: [Deployment guide for Calling in Webex App (Unified CM) - Manage and troubleshoot](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_0101.html), Manage and troubleshoot > troubleshooting checklist (calling behavior). Checked 2026-09-30. [^50]: Webex App uses the same Unified CM-hosted client configuration file as Jabber to configure calling features and the Jabber-to-Webex migration tooling. Source: [Upgrade Jabber with IM and Presence to Webex App](https://help.webex.com/en-us/article/980p3k/Upgrade-Jabber-with-IM-and-Presence-to-Webex-App), Update Unified CM configuration file. Checked 2026-09-30. [^51]: The deployment task flow creates a service profile, configures UC services and attaches them to the service profile, with an option to make the service profile the cluster default. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Deploy > Create default service profile; Configure service profile with UC services. Checked 2026-09-30. [^52]: The _cisco-uds._tcp SRV record gives the client the location of Unified CM from which it retrieves service profiles; the guide's example uses port 8443. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Deploy > Service discovery options. Checked 2026-09-30. [^53]: The _collab-edge._tls SRV record gives the client the location of Expressway-E for Mobile and Remote Access. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Deploy > Service discovery options. Checked 2026-09-30. [^54]: Calling in Webex App (Unified CM) on desktop requires Unified CM Release 11.5(1) SU3 or later. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Requirements > Unified CM requirements. Checked 2026-09-30. [^55]: Apple Push Notification support for Webex App on iOS requires Unified CM 11.5(1) SU8 or a later SU on the 11.5 release, or 12.5(1) SU3 or a later SU on the 12.5 release. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Requirements > Unified CM requirements (iOS). Checked 2026-09-30. [^56]: MRA failover for Calling in Webex App (Unified CM) requires Unified CM Release 14.0 or later. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > Requirements > Unified CM requirements (MRA failover note). Checked 2026-09-30. [^57]: UC Manager profiles are added in Control Hub under Management > Organization Settings > UC Manager Profiles > Add Profile, and edited or deleted from the profile's ellipsis menu. Source: [UC Manager profiles in Control Hub](https://help.webex.com/en-us/article/n51zz9x/UC-Manager-Profiles-in-Cisco-Webex-Control-Hub), Create a UC Manager profile; Edit or delete. Checked 2026-09-30. [^58]: The UC Manager profile UDS Server field is needed when the Webex App user ID does not match the Unified CM user ID, or when ILS is not enabled in a multi-cluster Unified CM deployment. Source: [UC Manager profiles in Control Hub](https://help.webex.com/en-us/article/n51zz9x/UC-Manager-Profiles-in-Cisco-Webex-Control-Hub), Create a UC Manager profile > UDS Server. Checked 2026-09-30. [^59]: The UC Manager profile Voice Services Domain holds the domain used for SRV records when the login email domain is not used for service discovery, and it is required for MRA. Source: [UC Manager profiles in Control Hub](https://help.webex.com/en-us/article/n51zz9x/UC-Manager-Profiles-in-Cisco-Webex-Control-Hub), Create a UC Manager profile > Voice Services Domain. Checked 2026-09-30. [^60]: The voicemail UC service ties into an existing Unity Connection deployment and provides voicemail retrieval to users associated with the corresponding service profile; a voicemail pilot number is configured as part of the same workflow. Source: [Deployment guide for Calling in Webex App (Unified CM) - Deploy Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_010.html), Deploy > Configure UC services workflow > Configure voicemail pilot number; Configure UC services. Checked 2026-09-30. [^61]: For server performance reasons, Cisco advises not to use Visual Voicemail with both Jabber and Webex App at the same time. Source: [Deployment guide for Calling in Webex App (Unified CM) - Prepare your environment for Calling in Webex App (Unified CM)](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html), Prepare your environment > coexistence note on Visual Voicemail. Checked 2026-09-30. [^62]: A warning icon appears in Webex App when it fails to register to Unified CM; hovering shows the error and clicking shows recommended next steps such as signing in to phone services. Source: [Deployment guide for Calling in Webex App (Unified CM) - Manage and troubleshoot](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_0101.html), Manage and troubleshoot > registration status. Checked 2026-09-30. [^63]: In Webex App, Settings > Phone Services shows which calling service the user is signed in to: Unified CM, Webex Calling, or calling hosted by a service provider. Source: [Webex App | Find out what calling service you have](https://help.webex.com/en-us/article/nbtgrzx/Webex-App-Find-Out-What-Calling-Service-You-Have), How to identify your service; desktop and mobile steps. Checked 2026-10-01. [^64]: The Unified CM troubleshooting checklist says to verify that any CTI remote device (CTI-RD) or Cisco Spark remote device for the user was removed, and to delete any stray remote devices. Source: [Deployment guide for Calling in Webex App (Unified CM) - Manage and troubleshoot](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_0101.html), Registration issues checklist. Checked 2026-10-01. [^65]: Jabber and Webex App cannot both be registered to Unified CM in softphone mode at the same time on the same machine, so Jabber should be exited. Source: [Deployment guide for Calling in Webex App (Unified CM) - Manage and troubleshoot](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_0101.html), Registration issues checklist. Checked 2026-10-01. [^66]: A softphone device that is missing from the Unified CM end user's Controlled Devices is a listed cause of Calling in Webex App (Unified CM) failures; the fix is to add the softphone device to Controlled Devices. Source: [Deployment guide for Calling in Webex App (Unified CM) - Manage and troubleshoot](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_0101.html), Unified CM configuration issues list. Checked 2026-10-01.