extension mobility redunduncy

Unanswered Question

SRND of CUCM 6.x is talking about how to configure extension mobility redunduncy. i have configured them exactally as it mentioned in the document using Microsoft DNS Server. but even then redunduncy does not work. when i shutdown the publisher server then extension mobility also goes down. when i press the services button it just gets stuck at "requesting" and then in the end gives me error saying "host not found".

i have got CUCM Version

following are the changes implemented for this EM redunduncy to work

1. configured microsoft DNS server with a domain name called bashrebank.corp.network

2. configured hostname bb-agc-ccm-emrr under the above mentioned domain pointing to both the CUCM IP addresses. so the FQDN is bb-agc-ccm-emrr.bashrebank.corp.network

3. testing the name resolution through my pc and it resolved to both the server by doing ping and NSLOOKUP

4. changed the services URL IP Address in the enterprise parameters to FQDN.

5. configured the EM URL IP Address to FQDN

6. configured DHCP so that DNS server ip address could be assigned to IP phones.

7. reloaded the IP phones so that changes could take effect.

8. confirmed from IP phones web page that changes have taken effect in serives URL and DNS server.

9. restarted CUCM publisher and subscriber

10. removed the publisher ethernet cable for testing

11. but EM did not work it gave me error as it mentioned above.

Please tell me where i have gone wrong with this configuration.

thanks and regards


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)


i configured everything pointing to subscriber ip address including services url and EM url even then phones could not connect to services when publisher is unavalaible.

I think EM on subscriber is not working. i have already checked EM service is running on the subscriber.

any suggestions



helawamry Thu, 01/05/2012 - 15:00
User Badges:

Hi Manish,

Did you find solution for this issue, actually we are facing the same issue excatly with the same call manager version.

I think there is problem with call manager version itself.

Thank you for you cooperation.




This Discussion