[cisco-voip] Extension Mobility Service URL

Bill Riley bill at hitechconnection.net
Fri Jul 22 08:11:49 EDT 2011


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 of http://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

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


More information about the cisco-voip mailing list