Extension Mobility is not working once we shutdown the CUCM Publisher in version 10.0

[ccg-collab1]

Hi,

We encountered an issue where in once we shutdown the Publisher, the extension mobility wont work. We already tried to restart Cisco Tomcat service however, the issue still persist. Upon checking the phone services and tried pressing the Update button for extension mobility, there was an error "Error occurred while retrieving information from database. No UPDATE permission for telecastersubscribedservice."

Is there a bug related to this one? 

I think extension mobility will still work on Subscriber even though we shutdown the Publisher.

Thank you,

[Marcelo Morais]

Hi,

 did you create an EM for both the Publisher and the Subscriber?

For example:

Main EM: http://<Publisher IP Addr>:8080/emapp/EMAppServlet?device=#DEVICENAME#
Secondary EM: http://<Subscriber IP Addr>:8080/emapp/EMAppServlet?device=#DEVICENAME#

Regards

[ccg-collab1]

Hi Marcelo,

I think there was no Secondary EM created.

So it means that we need to create another EM Services for the Secondary under the Phone Service? 

[Manish Gogna]

Hi,

You can check the following post for some good recommendations about EM failover config

https://supportforums.cisco.com/discussion/11697436/extension-mobility-redundancy-issue#3818187

Manish

- Do rate helpful posts -

[ccg-collab1]

Hi Manish,

Thanks for this one. 

Do i still need to configure Extension Mobility Service for the subscribers?

Here is the current configuration in our CUCM. Below Extension Mobility Service is pointing to the Publisher. Do we need to add another EM Service which is pointing to the CUCM Subscribers?

CM Servers

[Manish Gogna]

Hi,

You may either use the DNS round robin option or SLB option as specified in the earlier post that i mentioned. Apart from that  you can configure two services for Extension Mobility. One can be Extension Mobility_1 and the other could be Extension Mobility_2. In one we can mention the IP address of the Publisher and other one can be configured with that of the Subscriber. In this case you just need to inform the users to use the other service if one is down. Please refer to the following link:

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

Manish

- Do rate helpful posts -

[Marcelo Morais]

Hi,

 yes, you need this Secondary service for redundancy.

 Take a look at the links that Manish Gogna already posted.

Best regards.