We are currently using Extension Mobility on some of our phones, and we have both a Publisher and Subscriber server. The Extension Mobility service currently points only to the Publisher server. Is there a way to provide redundancy in the case that the Publisher goes down, the Service can point to the Subscriber to allow users to login and logout?
When the publisher is unavailable, phone updates cannot occur, call forwarding cannot be modified, message-waiting state information will be lost, and Cisco CallManager Extension Mobility stops functioning.
You can use a hostname in the phone service URL and use DNS for redundancy by setting up the DNS server to resolve the hostname to the IP of Publisher and Subscriber.
When the publisher is unavailable, phone updates cannot occur, call forwarding cannot be modified, message-waiting state information will be lost, and Cisco CallManager Extension Mobility stops functioning.
That's what I was afraid of. Thank you for the good information.
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
