How to Configure Extension Mobility

Posted: July 7, 2011 in Call Manager - CUCM, Features

Tags: CUCM, Extension mobility
2

I had a request to do a quick write up on how to configure extension mobility properly.

These are the steps involved (considering Call manager Linux versions):

1 Configure extension mobility service by going into Device > Device settings > Phone
Services

The service URL is : http://call-manager-

IP:8080/emapp/EMAppServlet?device=#DEVICENAME#

If you want to set it up as an Enterprise service then check that box Enterprise Subscription
otherwise leave it. If you check that box, extension mobility service will appear globally for all
phones and you wont be able to find this service under phone Subscribe services in Step 2. If
you dont check that box then move to step 2

2 Under phone, susbcribe this service as follows by dropping down the menu at top right
corner and then going into Subscribe/Unsubscribe Service
3- Staying on the same phone page, scroll down and check the extension mobility check box
otherwise no one will be able to login:

4 Create a User device profile Device > Device Settings > Device profile. Any higher
generation phone profile will work on lower one but thats not true the other way around. So a
Cisco 7960 device profile can be used to login oo a 7912 phone but a Cisco 7912 UDP wont
login on a Cisco 7960 phone.

5 After creating UDP, the most important and sometimes missed step is to subscribe the
Extension mobility service again like step 2 at UDP level

6 Go into user from from User management > End user and add that device profile to it. Also
select the primary extension at that user page.

Login and you should be good to go. Any issues, it would either be related to service not
subscribed at UDP level or a UDP not associated with a user.

Web Link for EM:

There can be a situation where your Pub is down or inaccessible and users wants to login or
logout. As EM service is dependent on Publisher they wont be able to login/logout and will get
host not found.

There is a workaround where users can login to their phones through a web link.

To login using URL:

http://<CUCM-SUB IP
Address>/emapp/EMAppServlet?device=MACADDR&userid=USERID&seq=XXXXX

XXXXX = Pin

Example:

http://192.168.70.11/emapp/EMAppServlet?device=SEP001E4AF0F9E4&userid=ajon&seq=123
45
To logout the user:

http://&lt; CUCM-SUB IP
Address>/emapp/EMAppServlet?device=SEP001646D97913&doLogout=true

http://10.26.3.62:8080/emapp/EMAppServlet?device=#DEVICENAME#

https://10.26.3.62:8443/emapp/EMAppServlet?device=#DEVICENAME#

2. https://uccisco.wordpress.com/2014/06/14/troubleshooting-extension-mobility/

https://supportforums.cisco.com/document/93061/common-problems-extension-mobility

Extension Mobility is not working in a way its giving error 208 i.e., login
unavailable, then the steps to troubleshoot are:

Regenerate tomacat.pem & tomcat.der certificates from OS GUI

pageunder the option: Security->Certificate management
Restart Cisco Tomcat Service from OS platform on CLI using the
command: utils service restart Cisco Tomcat.
Restart Extension mobility & Cisco Trust Verification Service from
Serviceablity GUI page

Restart all the phones

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>