Hi,<div>I'm only going to rephrase what James said, shorten the registration expiration timer and retry timers. That way phones will retry registrations lets say after 1 min so after 1 min all phones will failover to the secondary SRV record.</div>
<div><br></div><div>Regards,</div><div>Sammy<br><br><div class="gmail_quote">On Mon, Dec 12, 2011 at 10:35 AM, Mike Diehl <span dir="ltr"><<a href="mailto:mdiehl@diehlnet.com">mdiehl@diehlnet.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Actually, I've configured the phones to use DNS SRV records to find the Asterisk<br>
server, and this works very well. The problem is that when the router fails<br>
over, the phones IP address changes and this causes them to be unavailable<br>
<div class="im HOEnZb">from Asterisk's point of view.<br>
<br>
</div><div class="HOEnZb"><div class="h5">On Sunday 11 December 2011 10:02:21 pm Faisal Hanif wrote:<br>
> Why don't you use FQDN in phone instead of IP of server and configure DNS<br>
> Server to failover resolve to next IP while set SIP reg expiry same as DNS<br>
> TTL.<br>
><br>
> Regards,<br>
><br>
> Faisal Hanif<br>
> -----Original Message-----<br>
> From: <a href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a><br>
> [mailto:<a href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a>] On Behalf Of Mike Diehl<br>
> Sent: Monday, December 12, 2011 5:22 AM<br>
> To: Asterisk Users Mailing List - Non-Commercial Discussion<br>
> Subject: [asterisk-users] Multiple route failover zaps registration<br>
><br>
> Hi all,<br>
><br>
> I've got a customer who is bringing up a second Internet connection for<br>
> fail- over. I've configured a WRT54 with 2 LAN ports and arranged for it<br>
> to fail over when one of the routes is no longer available. That works<br>
> just fine at the IP level.<br>
><br>
> However, when the router fails over, the phones lose their registration,<br>
> presumably because their IP address has changed from Asterisk's point of<br>
> view.<br>
><br>
> The phones happen to be Polycom 335's, and I'm running Asterisk 1.6.2.9.<br>
><br>
> What is the best way to manage this situation so that the phones don't<br>
> become unavailable during failover?<br>
><br>
> I'm considering using the Tinc VPN solution to prevent the IP address from<br>
> chaing, but I'm hoping for a more simple solution.<br>
><br>
> Any ideas?<br>
<br>
--<br>
<br>
Take care and have fun,<br>
Mike Diehl.<br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</div></div></blockquote></div><br></div>