This document describes the common problems in Extension Mobility.
-Verify that you have configured the Extension Mobility service
-Verify the service URL is correct
– Start/Restart the EM services on each node you are running.
This error comes when you haven’t enabled the extension mobility , subscribed the phones/device profiles to the service as needed and haven’t associated user to a device profile.
The above error comes when you haven’t subscribed the phone or device profile to the EM profile. Once this is done you should be able to see the EM profile and log in correctly.
1. Check the Enterprise Parameters to make sure that the Synchronization Between Auto Device Profile and Phone Configuration is set to True.
2. Subscribe the phone to the Cisco Extension Mobility service.
The user should check that the correct UserID and PIN were entered; the user should check with the system administrator that the UserID and PIN are correct.
Make sure that you have chosen "Enable Extension Mobility" check box on the Phone Configuration window.
Make sure that you have associated a Device Profile to the user.
Verify that the Cisco Extension Mobility service is running by choosing Cisco Unified Serviceability > Tools > Control Center—Feature Services
Check whether the user is logged in to another phone. If multiple logins need to be allowed, ensure the Multiple Login Behavior service parameter is set to Multiple Logins Allowed
Enter a valid userid and PIN.
Check that the URL that is configured for Cisco Extension Mobility is correct and there should be no space in between.
Set service provisioning to default or internal. Refer Bug CSCtx70127
Follow the below steps in order to resolve the issue:-
1. Go to Certificat managent under security
2. Delete/Add Cisco Tomcat Cert
3. Restart Cisco Tomcat service,Cisco Trust verification service and EM service.
4. Try login to EM.
This error comes when the device or phone load does not support EMCC (eg. non-supported phone models,supported phone models with older phone load).It could also be the incorrect service URL and/or secure Service URL.
This error comes when "Validate IP Address" service parameter is set to true and user tries to login/logout from a machine whose IP address is not trusted i.e. not listed in Trusted List of Ips service parameter)
-> In the CUCM OS Administration page, re-generate the "Tomcat" certificates in all the nodes in the cluster. When the certificate is re-generated, the new certificate will be updated in the DB and CertMgr component should create the tomcat-trust.keystore file.
-> Restart Tomcat in all the nodes.
Access the service from the services button on the phone or downgrade the phone firmware to 9-0-2SR2 or earlier.
If you are running Cisco CallManager Extension Mobility on an IBM-340 platform, check that the system allows anonymous access to the Login Service web site.
And talso check the URL of the Login Service may not be configured properly in the LDAP directory. Check that the URL is correct.