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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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/[EMAIL PROTECTED] exten = _X.,2,Hangup exten = _X.,102,Dial,SIP/[EMAIL PROTECTED] exten = _X.,103,Hangup exten = _X.,203,Dial,SIP/[EMAIL PROTECTED] exten = _X.,204,Hangup exten = _X.,304,Dial,SIP/[EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] 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
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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/[EMAIL PROTECTED] exten = _X.,2,Hangup exten = _X.,102,Dial,SIP/[EMAIL PROTECTED] exten = _X.,103,Hangup exten = _X.,203,Dial,SIP/[EMAIL PROTECTED] exten = _X.,204,Hangup exten = _X.,304,Dial,SIP/[EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] 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
RE: [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:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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/[EMAIL PROTECTED] exten = _X.,2,Hangup exten = _X.,102,Dial,SIP/[EMAIL PROTECTED] exten = _X.,103,Hangup exten = _X.,203,Dial,SIP/[EMAIL PROTECTED] exten = _X.,204,Hangup exten = _X.,304,Dial,SIP/[EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] 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
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? -- Aaron Daniel Computer Systems Technician Sam Houston State University [EMAIL PROTECTED] (936) 294-4198 ___ --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
RE: [Asterisk-Users] Connecting to a cluster of SIP servers
-Original Message- From: Aaron Daniel [mailto:[EMAIL PROTECTED] 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. ___ --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
Re: [Asterisk-Users] Connecting to a cluster of SIP servers
On Monday 24 April 2006 11:12, 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. Um... The media gateways do not do a DNS lookup for every packet they send out... At least no sane one... -A. ___ --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
RE: [Asterisk-Users] Connecting to a cluster of SIP servers
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. Makes sense. We only use the round robin records for the outbound proxy, so the only time they use the other servers is when they make outgoing calls. As for the registrations, the phones register with a primary server and a secondary server (or in the case of the polycoms, if server one is down, it re-registers with server two immediately... it works, we've tested it), so any server in the round robin group knows about the phones when they make outbound calls. However, I think in the sense of actually MAKING phone calls, once it gets an ip address for a round-robined host, it continues talking to that host... i.e. Once the phone's in a conversation, all related packets for the stream go through the same server, not to any other server in the group. -- Aaron Daniel Computer Systems Technician Sam Houston State University [EMAIL PROTECTED] (936) 294-4198 ___ --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
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. Is it not safe to re-lookup the DNS records if the peer goes unreachable? It seems a bit broken to just mark the peer as unreachable and keep sending packets to the dead host when there are others listed by DNS as able to handle traffic for that domain. -- - Steve xmpp:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] 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
RE: [Asterisk-Users] Connecting to a cluster of SIP servers
On Sat, 22 Apr 2006, [EMAIL PROTECTED] wrote: 1. Add the IP's into your sip.conf and set qualify=yes. Ick, that's quite horrible :) And rather defeats the point of DNS - I'd need to know if any of the IPs were changed. I'm wondering if there are any bad side effects to hacking sip_poke_noanswer() to re-do the DNS lookup when a host goes unreachable. That way it'd also work for situations where the remote machine has updated it's DNS to point at a different server and then taken the original server down. -- - Steve xmpp:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] 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
[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:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] 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
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/[EMAIL PROTECTED] exten = _X.,2,Hangup exten = _X.,102,Dial,SIP/[EMAIL PROTECTED] exten = _X.,103,Hangup exten = _X.,203,Dial,SIP/[EMAIL PROTECTED] exten = _X.,204,Hangup exten = _X.,304,Dial,SIP/[EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] 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
