This document describes what to do in different scenarios for Phone Services not registering in Webex Unified CM.
Cisco recommends that you have knowledge of these topics:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
When Phone services do not connect, Webex provides a specific error code. All of the different error codes are listed in this link. This section describes how to solve the most common ones.
Failed to start a new SSO session. Try again.
Solution
Remove the CUCM server from the Expressway-C and re-add it. If the issue happens also on mobile, delete the Webex app and re-install it.
Can't load SSO browser page. Try again.
Solution
Most of the times this is an issue with the Identity Provider (IdP). Webex is not receiving the token and this requires deeper troubleshooting. Open a TAC case to troubleshoot this issue.
Sign into your account to use your phone services.
Solution
Ensure that the Mail ID of the CUCM user matches with the User ID of the user in Control Hub.
Sign into your account to use your phone services.
Solution
When the user log in to Webex and the Phone services credentials are not auto-populated, Webex fails with this error. To solve it, the user must manually enter the Phone services credentials.
Incorrect username or password.
Solution
Review that the user is able to log in to the Self-care portal. If they cannot log in, there is a Lightweight Directory Access Protocol (LDAP) issue. If they can log in, review that the certificates are valid and trusted.
Can't communicate with Unified CM server. Check your phone service preferences.
Solution
Ensure that the End user has the proper Role: Standard CCM End User. If the issue happens only over MRA, ensure that the communication between CUCM and the Expressway-C is in a good state. If needed, review that the certificates are exchanged between CUCM and Expressway-C and refresh the connection in Expressway-C.
Can't find your SRV record. Check your phone service preferences.
Solution
Webex neither finds the cisco-uds nor the collab-edge SRV records. To resolve this, configure the SRV records as per the guide.
No service discovered due to an untrusted certificate from server.
Solution
Validate this:
Webex failed to fetch UDS Servers from CUCM.
Solution
In CUCM, ensure the End user has the Client Services Framework (CSF) device assigned. In Control Hub, ensure that the user has the Unified CM license assigned.
Webex failed to query SSO status from CUCM during on-premises connection.
Solution
Ensure that the device can reach the CUCM server. Also, ensure that the SRV records are configured as per the guide.
Webex failed to query SSO status from Expressway during MRA connection.
Solution
Ensure that the device can reach the Expressway-E. Also, ensure that the SRV records are configured as per the guide.
Webex failed to fetch SSO authenticate URL from Expressway during MRA connection.
Solution
Ensure that the device can reach the Expressway-E. Also, ensure that the SRV records are configured as per the guide.
No Home cluster found.
Solution
Ensure the Home cluster checkbox is enabled for the affected user. If multiple clusters, ensure the Home cluster checkbox is enabled only on one cluster.
Failed to create device and CUCM replied with HTTP 500 error.
Solution
Ensure that the affected End user has a CSF device created and associated.
Failed to create device because no extension DN is associated with the userId in CUCM. CUCM replied with HTTP 601 error.
Solution
This error occurs when Auto-provisioning is enabled. For this feature to work, the End user must have a Primary extension. Add the Primary extenstion to solve the issue.
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
07-Jul-2026
|
Initial Release |