[asterisk-users] Multiple route failover zaps registration

2011-12-11 Thread Mike Diehl
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


Re: [asterisk-users] Multiple route failover zaps registration

2011-12-11 Thread James Sharp

On 12/11/2011 07:22 PM, Mike Diehl wrote:

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?



Shorten the registration expiration time on the phones?  It'll make them 
a bit chattier, but it'll make sure Asterisk has the most recent IP address.


Shorten it down to as long as you feel the phones can be without 
service, but also make sure you don't make them too chatty so they're 
reregistering every second.


--
_
-- 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


Re: [asterisk-users] Multiple route failover zaps registration

2011-12-11 Thread Faisal Hanif
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


--
_
-- 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


Re: [asterisk-users] Multiple route failover zaps registration

2011-12-11 Thread Mike Diehl
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


Re: [asterisk-users] Multiple route failover zaps registration

2011-12-11 Thread Sammy Govind
Hi,
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.

Regards,
Sammy

On Mon, Dec 12, 2011 at 10:35 AM, Mike Diehl mdi...@diehlnet.com wrote:

 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

--
_
-- 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

Re: [asterisk-users] Multiple route failover zaps registration

2011-12-11 Thread James Sharp

On 12/12/2011 12:35 AM, Mike Diehl wrote:

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.



And that's why I was suggesting the short registration timer.  I'm 
assuming that the LAN connections/WRT54 is for client phones, not the 
server.


The phone registers, Asterisk sees it as coming from 75.0.0.1 port 5060 
(the external IP of the WRT54).  And the phone re-registers every 30 
seconds, and Asterisk just refreshes the registration.


Now, the primary internet connection falls over and the WRT switches to 
the other connection.  If you set the registration timeout to a short 
interval, the phone sends out a register message and Asterisk sees it as 
coming from 85.0.0.1, port 5060.  Asterisk then updates the registration 
IP for that peer and it can deliver and receive calls from those phones.


The only thing that will happen is that active calls *will* get dropped. 
 There is no way to hide the IP change from that without the VPN tunnel.




--
_
-- 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