[cisco-voip] Extension Mobility Service URL

[stephen.welsh at unifiedfx.com]

I've seen some people create two Extension Mobility Service URL's and subscribed both services to all phones i.e.:

Primary Login Service
Backup Login Service

Cuts on the cost/complexity of a load balancer (the best solution), but does require the user to engage the back-up service manually.

Thanks

Stephen

On 22 Jul 2011, at 13:11, Bill Riley wrote:

> You need to use a hardware load balancer and point the URL to the load balancer IP.
>  
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of cips
> Sent: Friday, July 22, 2011 6:43 AM
> To: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Extension Mobility Service URL
>  
> Or you can use a single-sign-on application like ALM which does not rely on the service URL but verifies the cm’s for sending the logon logoff messages.
>  
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike King
> Sent: donderdag 21 juli 2011 23:07
> To: Cisco VoIPoE List
> Subject: [cisco-voip] Extension Mobility Service URL
>  
> We had to bring down a Subscriber last night, and had no issues other than extension mobility.  The services URL specifically referenced this Subscriber.
> Since we have a few subscribers, is there a way to make this a little more fault tolerant?  I notice most of the other URL's (Corporate Directory) all start with Application/Cisco instead ofhttp://IP address of server.
>  
> The next time I have a similar issue, and I need to change that URL, are they're any services I need to restart?  Reset phones?  Will it just work?
>  
> Mike
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110722/9ea546a9/attachment.html>