01-07-2010 07:37 PM - edited 03-19-2019 12:14 AM
Hello All,
Will pointing the IP of the service url for the Extension Mobility Service on the Subscriber and Publisher to there own IP's, establish extension mobility redundancy? So the phone register to the subscriber and login to the subscriber for extension mobility and if they subscriber crashes the publisher is pointing to itself? Thanks
Jason
Solved! Go to Solution.
01-08-2010 02:49 AM
Hi there,
In the past i have created a second em service with a different ip address let's say the pub and called the service em backup. If the primary server fails they can go into services from the phone and select the em backup service.
Cheers
Dave
01-07-2010 08:03 PM
"Serivce URL" is an "Enterprise Parameter", which means, it's clusterwide. You cannot set different URL for publisher and subscribers.
EM service is basically a web service. You may either use DNS (round-robin) or network load-balancer for redundancy.
Hope this helps.
Michael
01-08-2010 02:49 AM
Hi there,
In the past i have created a second em service with a different ip address let's say the pub and called the service em backup. If the primary server fails they can go into services from the phone and select the em backup service.
Cheers
Dave
02-09-2010 09:07 AM
Hi,
We have a product called ALM which basically controls single sign-on login/logout of the phone from the windows desktop.
Anyway, the side affect of the application is that it automatically scans active/responsive extension mobility services configured. e.g. if the main server/service fails and a failover/backup server is available, it will automatically try to use that. As soon as the primary EM server is up-and-running again, it will use that one again.
Search for ALM Spectra in google or click here:
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide