Has anyone had any success load balancing SIP? More specifically distributing SIP registrations across a number of access SBCs and maintaining persistence based on source IP. By maintaining source IP persistence subsequent calls would go to the SBC to which they are registered. In this case each of several SBCs cache registrations for a single SIP registrar. Has anyone used F5 or Kamailio for this..or some other SIP proxy or load balancer? Thank You, Aaron ---------------------------------------------------------------------- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
Ive done it with Brocade and Kamailio. From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Sykes, Aaron Sent: Tuesday, April 19, 2016 4:32 PM To: voiceops at voiceops.org Subject: [VoiceOps] Load balancing SIP Has anyone had any success load balancing SIP? More specifically distributing SIP registrations across a number of access SBCs and maintaining persistence based on source IP. By maintaining source IP persistence subsequent calls would go to the SBC to which they are registered. In this case each of several SBCs cache registrations for a single SIP registrar. Has anyone used F5 or Kamailio for this..or some other SIP proxy or load balancer? Thank You, Aaron ________________________________ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
Did you use these devices for this purpose on separate occasions or in unison? How many SBCs were being used in the distribution? Can you elaborate on the basic topology? Aaron From: Joseph Jackson [mailto:jjackson at aninetworks.net] Sent: Tuesday, April 19, 2016 2:34 PM To: Sykes, Aaron <Aaron.Sykes at cdk.com>; voiceops at voiceops.org Subject: RE: Load balancing SIP Ive done it with Brocade and Kamailio. From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Sykes, Aaron Sent: Tuesday, April 19, 2016 4:32 PM To: voiceops at voiceops.org<mailto:voiceops at voiceops.org> Subject: [VoiceOps] Load balancing SIP Has anyone had any success load balancing SIP? More specifically distributing SIP registrations across a number of access SBCs and maintaining persistence based on source IP. By maintaining source IP persistence subsequent calls would go to the SBC to which they are registered. In this case each of several SBCs cache registrations for a single SIP registrar. Has anyone used F5 or Kamailio for this..or some other SIP proxy or load balancer? Thank You, Aaron ________________________________ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
On separate occasions. The brocade load balancers have the option to be "sticky" - ie all follow on requests go to the same sbc. For the brocades they were placed topology wise in front of the SBCs so that all requests and replies cross the load balancer. You can do this by having the load balancer be the default gateway for the SBC's. It was pretty simple at least for the brocade configuration. Note that RTP traffic was not load balanced of course. I will see if I can find my notes on the kamailio config. Used the dispatch module if I remember correctly. I will try and find them as its been awhile. Joseph From: Sykes, Aaron [mailto:Aaron.Sykes at cdk.com] Sent: Tuesday, April 19, 2016 6:00 PM To: Joseph Jackson; voiceops at voiceops.org Subject: RE: Load balancing SIP Did you use these devices for this purpose on separate occasions or in unison? How many SBCs were being used in the distribution? Can you elaborate on the basic topology? Aaron From: Joseph Jackson [mailto:jjackson at aninetworks.net] Sent: Tuesday, April 19, 2016 2:34 PM To: Sykes, Aaron <Aaron.Sykes at cdk.com<mailto:Aaron.Sykes at cdk.com>>; voiceops at voiceops.org<mailto:voiceops at voiceops.org> Subject: RE: Load balancing SIP Ive done it with Brocade and Kamailio. From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Sykes, Aaron Sent: Tuesday, April 19, 2016 4:32 PM To: voiceops at voiceops.org<mailto:voiceops at voiceops.org> Subject: [VoiceOps] Load balancing SIP Has anyone had any success load balancing SIP? More specifically distributing SIP registrations across a number of access SBCs and maintaining persistence based on source IP. By maintaining source IP persistence subsequent calls would go to the SBC to which they are registered. In this case each of several SBCs cache registrations for a single SIP registrar. Has anyone used F5 or Kamailio for this..or some other SIP proxy or load balancer? Thank You, Aaron ________________________________ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
On 04/19/2016 07:07 PM, Joseph Jackson wrote:
Used the dispatch module if I remember correctly. I will try and find them as its been awhile.
Yep, dispatcher would be the canonical approach: http://kamailio.org/docs/modules/4.4.x/modules/dispatcher.html However, like many Kamailio modules, dispatcher simply provides some logic and database binding. You are free to implement your own (possibly more sophisticated) distribution strategies in Kamailio's elaborate DSL. -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 1447 Peachtree Street NE, Suite 700 Atlanta, GA 30309 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Alex would for sure know more than me (dude is wicked smart). Also this was a very very small install. -----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex Balashov Sent: Tuesday, April 19, 2016 6:09 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Load balancing SIP On 04/19/2016 07:07 PM, Joseph Jackson wrote:
Used the dispatch module if I remember correctly. I will try and find them as its been awhile.
Yep, dispatcher would be the canonical approach: http://kamailio.org/docs/modules/4.4.x/modules/dispatcher.html However, like many Kamailio modules, dispatcher simply provides some logic and database binding. You are free to implement your own (possibly more sophisticated) distribution strategies in Kamailio's elaborate DSL. -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 1447 Peachtree Street NE, Suite 700 Atlanta, GA 30309 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Kamailio provides an excellent and high-performance vehicle for doing this. It's probably one of its most canonical use-cases. You can do it in one of two ways: 1) Use Kamailio as a redirect server with some state. But this is the more complicated option, and requires that the registering endpoints follow redirects for REGISTER requests, which they don't always. 2) Use REGISTER pass-thru with the SIP Path extension: https://tools.ietf.org/html/rfc3327 Kamailio has a specific module for this: http://kamailio.org/docs/modules/4.4.x/modules/path.html ... and it works great. With a simple config that doesn't have a lot of external I/O dependencies, you can handle tens of thousands of registrations per second, at least. -- Alex Balashov | Principal | Evariste Systems LLC 1447 Peachtree Street NE, Suite 700 Atlanta, GA 30309 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Is there a reason the industry standard of using DNS SRV records wouldnt apply here? Be aware if this is access side and performing nat traversal you may encounter issues with far end nat devices barking if your response comes from a different IP than the original request went to. On 4/19/2016 2:32 PM, Sykes, Aaron wrote:
Has anyone had any success load balancing SIP? More specifically distributing SIP registrations across a number of access SBCs and maintaining persistence based on source IP. By maintaining source IP persistence subsequent calls would go to the SBC to which they are registered. In this case each of several SBCs cache registrations for a single SIP registrar. Has anyone used F5 or Kamailio for this..or some other SIP proxy or load balancer?
Thank You,
Aaron
------------------------------------------------------------------------ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On 04/19/2016 07:37 PM, Ryan Delgrosso wrote:
far end nat devices barking if your response comes from a different IP than the original request went to.
Use of Path would be necessary to deal with this. -- Alex Balashov | Principal | Evariste Systems LLC 1447 Peachtree Street NE, Suite 700 Atlanta, GA 30309 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
participants (4)
-
Aaron.Sykes＠cdk.com -
abalashov＠evaristesys.com -
jjackson＠aninetworks.net -
ryandelgrosso＠gmail.com