thr3ads.net - asterisk users - [Asterisk-Users] Connecting to a cluster of SIP servers [Apr 2006]

If this information is useful, please help other people find it:
Share via:

Steve Hill

2006-Apr-22 02:12 UTC

[Asterisk-Users] Connecting to a cluster of SIP servers

My Asterisk server is connecting to "sip.plus.net", which resolves to 
multiple IP addresses:

     sip.plus.net.           300     IN      A       84.92.0.75
     sip.plus.net.           300     IN      A       84.92.0.76
     sip.plus.net.           300     IN      A       84.92.5.189
     sip.plus.net.           300     IN      A       84.92.5.190

If one of these machines is down (i.e. it's not replying to the SIP 
packets or it's sending back ICMP Port Unreachable), Asterisk keeps trying 
the same server. Shouldn't Asterisk move on to the next server 
automatically in this case? It seems to only way to do this at the moment 
is to run the "reload" command, which causes it to do a DNS lookup and
it
may then pick one of the other servers.

-- 

  - Steve
    xmpp:steve@nexusuk.org   sip:steve@nexusuk.org   http://www.nexusuk.org/

      Servatis a periculum, servatis a maleficum - Whisper, Evanescence

billy@kersting.com

2006-Apr-22 04:26 UTC

head link

[Asterisk-Users] Connecting to a cluster of SIP servers

Although there maybe a better way, this would work:

1. Add the IP's into your sip.conf and set qualify=yes.
2. Make your dialplan something like the following:
	exten => _X.,1,Dial,SIP/${EXTEN}@84.92.0.75
	exten => _X.,2,Hangup
	exten => _X.,102,Dial,SIP/${EXTEN}@84.92.0.76
	exten => _X.,103,Hangup
	exten => _X.,203,Dial,SIP/${EXTEN}@84.92.0.189
	exten => _X.,204,Hangup
	exten => _X.,304,Dial,SIP/${EXTEN}@84.92.0.190
	exten => _X.,305,Hangup

This would make your failover work but certainly wouldn't help with the load
balancing between the servers. If any cannot qualify or are congested, they
will automatically failover to the next server.

I believe most people use an SER proxy for this type of application. It
seems to work well with the round robin type DNS.

William	

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Steve Hill
Sent: Saturday, April 22, 2006 5:13 AM
To: Asterisk-Users@lists.digium.com
Subject: [Asterisk-Users] Connecting to a cluster of SIP servers


My Asterisk server is connecting to "sip.plus.net", which resolves to 
multiple IP addresses:

     sip.plus.net.           300     IN      A       84.92.0.75
     sip.plus.net.           300     IN      A       84.92.0.76
     sip.plus.net.           300     IN      A       84.92.5.189
     sip.plus.net.           300     IN      A       84.92.5.190

If one of these machines is down (i.e. it's not replying to the SIP 
packets or it's sending back ICMP Port Unreachable), Asterisk keeps trying 
the same server. Shouldn't Asterisk move on to the next server 
automatically in this case? It seems to only way to do this at the moment 
is to run the "reload" command, which causes it to do a DNS lookup and
it
may then pick one of the other servers.

-- 

  - Steve
    xmpp:steve@nexusuk.org   sip:steve@nexusuk.org   http://www.nexusuk.org/

      Servatis a periculum, servatis a maleficum - Whisper, Evanescence

_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

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


__________ NOD32 1.1447 (20060316) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com

Douglas Garstang

2006-Apr-24 08:12 UTC

head link

[Asterisk-Users] Connecting to a cluster of SIP servers

You can't use round robin DNS. Round robin DNS will cause every SIP packet
to potentially go through a different static path, which will break things.
> -----Original Message-----
> From: billy@kersting.com [mailto:billy@kersting.com]
> Sent: Saturday, April 22, 2006 5:27 AM
> To: 'Asterisk Users Mailing List - Non-Commercial Discussion'
> Subject: RE: [Asterisk-Users] Connecting to a cluster of SIP servers
> 
> 
> Although there maybe a better way, this would work:
> 
> 1. Add the IP's into your sip.conf and set qualify=yes.
> 2. Make your dialplan something like the following:
> 	exten => _X.,1,Dial,SIP/${EXTEN}@84.92.0.75
> 	exten => _X.,2,Hangup
> 	exten => _X.,102,Dial,SIP/${EXTEN}@84.92.0.76
> 	exten => _X.,103,Hangup
> 	exten => _X.,203,Dial,SIP/${EXTEN}@84.92.0.189
> 	exten => _X.,204,Hangup
> 	exten => _X.,304,Dial,SIP/${EXTEN}@84.92.0.190
> 	exten => _X.,305,Hangup
> 
> This would make your failover work but certainly wouldn't 
> help with the load
> balancing between the servers. If any cannot qualify or are 
> congested, they
> will automatically failover to the next server.
> 
> I believe most people use an SER proxy for this type of 
> application. It
> seems to work well with the round robin type DNS.
> 
> William	
> 
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com
> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of 
> Steve Hill
> Sent: Saturday, April 22, 2006 5:13 AM
> To: Asterisk-Users@lists.digium.com
> Subject: [Asterisk-Users] Connecting to a cluster of SIP servers
> 
> 
> My Asterisk server is connecting to "sip.plus.net", which
resolves to
> multiple IP addresses:
> 
>      sip.plus.net.           300     IN      A       84.92.0.75
>      sip.plus.net.           300     IN      A       84.92.0.76
>      sip.plus.net.           300     IN      A       84.92.5.189
>      sip.plus.net.           300     IN      A       84.92.5.190
> 
> If one of these machines is down (i.e. it's not replying to the SIP 
> packets or it's sending back ICMP Port Unreachable), Asterisk 
> keeps trying 
> the same server. Shouldn't Asterisk move on to the next server 
> automatically in this case? It seems to only way to do this 
> at the moment 
> is to run the "reload" command, which causes it to do a DNS 
> lookup and it 
> may then pick one of the other servers.
> 
> -- 
> 
>   - Steve
>     xmpp:steve@nexusuk.org   sip:steve@nexusuk.org   http://www.nexusuk.org/

      Servatis a periculum, servatis a maleficum - Whisper, Evanescence

_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

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


__________ NOD32 1.1447 (20060316) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com


_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

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

Sergio García Murillo

2006-Apr-24 08:43 UTC

head link

[Asterisk-Users] Connecting to a cluster of SIP servers

How about using LVS?

http://www.ultramonkey.org/3/topologies/lb-overview.html


-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Douglas Garstang
Sent: lunes, 24 de abril de 2006 17:12
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] Connecting to a cluster of SIP servers

You can't use round robin DNS. Round robin DNS will cause every SIP packet
to potentially go through a different static path, which will break things.
> -----Original Message-----
> From: billy@kersting.com [mailto:billy@kersting.com]
> Sent: Saturday, April 22, 2006 5:27 AM
> To: 'Asterisk Users Mailing List - Non-Commercial Discussion'
> Subject: RE: [Asterisk-Users] Connecting to a cluster of SIP servers
> 
> 
> Although there maybe a better way, this would work:
> 
> 1. Add the IP's into your sip.conf and set qualify=yes.
> 2. Make your dialplan something like the following:
> 	exten => _X.,1,Dial,SIP/${EXTEN}@84.92.0.75
> 	exten => _X.,2,Hangup
> 	exten => _X.,102,Dial,SIP/${EXTEN}@84.92.0.76
> 	exten => _X.,103,Hangup
> 	exten => _X.,203,Dial,SIP/${EXTEN}@84.92.0.189
> 	exten => _X.,204,Hangup
> 	exten => _X.,304,Dial,SIP/${EXTEN}@84.92.0.190
> 	exten => _X.,305,Hangup
> 
> This would make your failover work but certainly wouldn't 
> help with the load
> balancing between the servers. If any cannot qualify or are 
> congested, they
> will automatically failover to the next server.
> 
> I believe most people use an SER proxy for this type of 
> application. It
> seems to work well with the round robin type DNS.
> 
> William	
> 
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com
> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of 
> Steve Hill
> Sent: Saturday, April 22, 2006 5:13 AM
> To: Asterisk-Users@lists.digium.com
> Subject: [Asterisk-Users] Connecting to a cluster of SIP servers
> 
> 
> My Asterisk server is connecting to "sip.plus.net", which
resolves to
> multiple IP addresses:
> 
>      sip.plus.net.           300     IN      A       84.92.0.75
>      sip.plus.net.           300     IN      A       84.92.0.76
>      sip.plus.net.           300     IN      A       84.92.5.189
>      sip.plus.net.           300     IN      A       84.92.5.190
> 
> If one of these machines is down (i.e. it's not replying to the SIP 
> packets or it's sending back ICMP Port Unreachable), Asterisk 
> keeps trying 
> the same server. Shouldn't Asterisk move on to the next server 
> automatically in this case? It seems to only way to do this 
> at the moment 
> is to run the "reload" command, which causes it to do a DNS 
> lookup and it 
> may then pick one of the other servers.
> 
> -- 
> 
>   - Steve
>     xmpp:steve@nexusuk.org   sip:steve@nexusuk.org   http://www.nexusuk.org/

      Servatis a periculum, servatis a maleficum - Whisper, Evanescence

_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

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


__________ NOD32 1.1447 (20060316) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com


_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
--------------------------------------------------------------------------------------
This message and any files transmitted with it are confidential and intended
solely
for the use of the individual or entity to whom they are addressed. No
confidentiality
or privilege is waived or lost by any wrong transmission. 
If you have received this message in error, please immediately destroy it and
kindly
notify the sender by reply email.
You must not, directly or indirectly, use, disclose, distribute, print, or copy
any
part of this message if you are not the intended recipient. Opinions,
conclusions and
other information in this message that do not relate to the official business of
Ydilo Advanced Voice Solutions, S.A. shall be understood as neither given nor
endorsed by it.
--------------------------------------------------------------------------------------

Douglas Garstang

2006-Apr-24 08:58 UTC

head link

[Asterisk-Users] Connecting to a cluster of SIP servers

Well, for a start, there's a single director, which means a single point of
failure. Really, I wonder why they even bother.
> -----Original Message-----
> From: Sergio Garc?a Murillo [mailto:Sergio.Garcia@ydilo.com]
> Sent: Monday, April 24, 2006 9:44 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [Asterisk-Users] Connecting to a cluster of SIP servers
> 
> 
> 
> How about using LVS?
> 
> http://www.ultramonkey.org/3/topologies/lb-overview.html
> 
> 
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com 
> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of 
> Douglas Garstang
> Sent: lunes, 24 de abril de 2006 17:12
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [Asterisk-Users] Connecting to a cluster of SIP servers
> 
> You can't use round robin DNS. Round robin DNS will cause 
> every SIP packet to potentially go through a different static 
> path, which will break things.
> 
> > -----Original Message-----
> > From: billy@kersting.com [mailto:billy@kersting.com]
> > Sent: Saturday, April 22, 2006 5:27 AM
> > To: 'Asterisk Users Mailing List - Non-Commercial Discussion'
> > Subject: RE: [Asterisk-Users] Connecting to a cluster of SIP servers
> > 
> > 
> > Although there maybe a better way, this would work:
> > 
> > 1. Add the IP's into your sip.conf and set qualify=yes.
> > 2. Make your dialplan something like the following:
> > 	exten => _X.,1,Dial,SIP/${EXTEN}@84.92.0.75
> > 	exten => _X.,2,Hangup
> > 	exten => _X.,102,Dial,SIP/${EXTEN}@84.92.0.76
> > 	exten => _X.,103,Hangup
> > 	exten => _X.,203,Dial,SIP/${EXTEN}@84.92.0.189
> > 	exten => _X.,204,Hangup
> > 	exten => _X.,304,Dial,SIP/${EXTEN}@84.92.0.190
> > 	exten => _X.,305,Hangup
> > 
> > This would make your failover work but certainly wouldn't 
> > help with the load
> > balancing between the servers. If any cannot qualify or are 
> > congested, they
> > will automatically failover to the next server.
> > 
> > I believe most people use an SER proxy for this type of 
> > application. It
> > seems to work well with the round robin type DNS.
> > 
> > William	
> > 
> > -----Original Message-----
> > From: asterisk-users-bounces@lists.digium.com
> > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of 
> > Steve Hill
> > Sent: Saturday, April 22, 2006 5:13 AM
> > To: Asterisk-Users@lists.digium.com
> > Subject: [Asterisk-Users] Connecting to a cluster of SIP servers
> > 
> > 
> > My Asterisk server is connecting to "sip.plus.net", which 
> resolves to 
> > multiple IP addresses:
> > 
> >      sip.plus.net.           300     IN      A       84.92.0.75
> >      sip.plus.net.           300     IN      A       84.92.0.76
> >      sip.plus.net.           300     IN      A       84.92.5.189
> >      sip.plus.net.           300     IN      A       84.92.5.190
> > 
> > If one of these machines is down (i.e. it's not replying to the
SIP
> > packets or it's sending back ICMP Port Unreachable), Asterisk 
> > keeps trying 
> > the same server. Shouldn't Asterisk move on to the next server 
> > automatically in this case? It seems to only way to do this 
> > at the moment 
> > is to run the "reload" command, which causes it to do a DNS 
> > lookup and it 
> > may then pick one of the other servers.
> > 
> > -- 
> > 
> >   - Steve
> >     xmpp:steve@nexusuk.org   sip:steve@nexusuk.org   
> http://www.nexusuk.org/
> 
>       Servatis a periculum, servatis a maleficum - Whisper, 
> Evanescence
> 
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 
> 
> __________ NOD32 1.1447 (20060316) Information __________
> 
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
> 
> 
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> --------------------------------------------------------------
> ------------------------
> This message and any files transmitted with it are 
> confidential and intended solely 
> for the use of the individual or entity to whom they are 
> addressed. No confidentiality 
> or privilege is waived or lost by any wrong transmission. 
> If you have received this message in error, please 
> immediately destroy it and kindly 
> notify the sender by reply email.
> You must not, directly or indirectly, use, disclose, 
> distribute, print, or copy any 
> part of this message if you are not the intended recipient. 
> Opinions, conclusions and 
> other information in this message that do not relate to the 
> official business of 
> Ydilo Advanced Voice Solutions, S.A. shall be understood as 
> neither given nor endorsed by it. 
> --------------------------------------------------------------
> ------------------------
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>

Douglas Garstang

2006-Apr-24 09:40 UTC

head link

[Asterisk-Users] Connecting to a cluster of SIP servers

> -----Original Message-----
> From: Aaron Daniel [mailto:amdtech@shsu.edu]
> Sent: Monday, April 24, 2006 10:06 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [Asterisk-Users] Connecting to a cluster of SIP servers
> 
> 
> On Mon, 24 Apr 2006, Douglas Garstang wrote:
> 
> > You can't use round robin DNS. Round robin DNS will cause 
> every SIP packet to potentially go through a different static 
> path, which will break things.
> 
> Huh?  Has this happened to you in practice?
It sure has. Polycom phone queries DNS for domain.com and gets round robin IP of
192.168.10.1. It sends a REGISTER request to that IP. Asterisk at 192.168.10.1
sends back a 407 Proxy Auth required. The polycom phone then queries DNS again
and gets 192.168.10.2 this time and sends the REGISTER with auth info included
this time to Asterisk at 192.168.10.2. The Asterisk at 192.168.10.2 box goes
'huh. What the hell is this for?' becuase it never received the original
REGISTER, and drops it on the floor. The phone never gets an OK to its register
request.

Doug.

Possibly Parallel Threads

Search for more possibly parallel threads

asterisk users - Apr 2006 - Connecting to a cluster of SIP servers

[Asterisk-Users] Connecting to a cluster of SIP servers

[Asterisk-Users] Connecting to a cluster of SIP servers

[Asterisk-Users] Connecting to a cluster of SIP servers

[Asterisk-Users] Connecting to a cluster of SIP servers

[Asterisk-Users] Connecting to a cluster of SIP servers

[Asterisk-Users] Connecting to a cluster of SIP servers

Possibly Parallel Threads