CUCM Extension Mobility Service

[yarinezra]

Hello i’ve been asked this multiple times now.

Say i have 4 Cucm servers in a cluster, 1 Pub.

The publisher servers is the only one running the Extension Mobility service, if the publisher shuts down, what happens to the phones already logged in to profiles?

[Shalid Kurunnan Chalil · Accepted solution]

Hi,

the users cannot login or logout from the phone. 

Regards,

[Sadav Ansari · Accepted solution]

So if Publisher down EM services not work and on the phone it will logged out automatically.

There are two services - 'Extension Mobility' is the actual API that runs on each server. This is what you can start/stop from feature services in serviceablity. If you stop this on a server, the actual EM webpage/web service (which is found on the 'network' services page in CUCM serviceability) knows which servers are running the EM API, and can fail over automatically. So if you stop EM API on the publisher, the EM web service will just use the subcriber EM API. This is what has happened when you have 'stopped' EM.

This is all well and good, but in the case where your publisher is truly down, both the EM web service/web page and the EM API are gone. The key one here is that the EM webpage is gone, and this is the only service that the phones directly connect to - i.e. the target of the phone service URL, specified typically by hostname or IP.

So if you want to overcome this limitation you have to configure Server load balancing (SLB), Check the below link for your reference.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/cmapps.html#wp1189079

Pls rate if its “Helpful”. If this answered your question pls click “Accept as Solution”.

[Roger Kallberg · Accepted solution]

Nothing happens to phones that are already logged in. As the server that is running the service is not available it’s not possible to make any changes to the state of the service on the phones.