Actually, I've configured the phones to use DNS SRV records to find the 
Asterisk 
server, and this works very well.  The problem is that when the router fails 
over, the phones IP address changes and this causes them to be unavailable 
from Asterisk's point of view.

On Sunday 11 December 2011 10:02:21 pm Faisal Hanif wrote:
> Why don't you use FQDN in phone instead of IP of server and configure DNS
> Server to failover resolve to next IP while set SIP reg expiry same as DNS
> TTL.
> 
> Regards,
> 
> Faisal Hanif
> -----Original Message-----
> From: asterisk-users-boun...@lists.digium.com
> [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Mike Diehl
> Sent: Monday, December 12, 2011 5:22 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: [asterisk-users] Multiple route failover zaps registration
> 
> Hi all,
> 
> I've got a customer who is bringing up a second Internet connection for
> fail- over.  I've configured a WRT54 with 2 LAN ports and arranged for it
> to fail over when one of the routes is no longer available.  That works
> just fine at the IP level.
> 
> However, when the router fails over, the phones lose their registration,
> presumably because their IP address has changed from Asterisk's point of
> view.
> 
> The phones happen to be Polycom 335's, and I'm running Asterisk 1.6.2.9.
> 
> What is the best way to manage this situation so that the phones don't
> become unavailable during failover?
> 
> I'm considering using the Tinc VPN solution to prevent the IP address from
> chaing, but I'm hoping for a more simple solution.
> 
> Any ideas?

-- 

Take care and have fun,
Mike Diehl.

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to