cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1194
Views
15
Helpful
2
Replies

Extension Mobility Failover solutions

Omar1212
Level 1
Level 1

Hi,

First time posting here.

We are currently running CUCM in my work place and we have ! 1 Publisher and 2 Subscribers.
We had an issue  with one of our subscribers few days ago which has led to the user to not be able to log out or in of their phones.

When looking at the service that the devices and profiles are subscribed I found that they service is configured to point to the failed subscriber. Creating a another servers and pointing it to the other subscriber or publisher solved my problem.

my question is, would there be a way to configure automatic failover for the service  ? 


What is usually being in this sort of situation and what is the current standard  ? is that standard to point to the pub for example ?

any pointers or help is appreciated 


2 Replies 2

Ratheesh Kumar
VIP Alumni
VIP Alumni
Hi there
Welcome to the hub !!!

Yes for EM FO, you can have these options.

* Multiple IP Phone Services for Extension Mobility
* Extension Mobility using DNS Round-Robin algorithm
* A Server Load Balancing – Highly Recommended

Below are some good guides you can go thru.

https://www.uccollabing.com/extension-mobility-redundancy-high-availability/
http://www.ucguerrilla.com/2012/05/redundancy-considerations-and-cisco-ip.html

Hope this Helps

Cheers
Rath!

***Please rate helpful posts and if applicable mark "Accept as a Solution"***


As @Ratheesh Kumar  mentioned  you can have multiple Services or  if your phones use DNS, you can achieve it by the DNS. If customer doesn't have SLB, just for EM most of the customer doesn't go with SLB.Some  where I read its possible to make SLB using ios but again you need to try it googling.

Attached is a SRND for version 11, refer the guide corresponding   to your version.Go through High Availability for IP Phone Services

 

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab11/collab11/cmapps.html

 

 

 

 



Response Signature