[SR-Users] Kamailio Behind TCP Load Balancer

[Daniel-Constantin Mierla]

Hello,


On 23/06/16 12:57, Colin Morelli wrote:
> Hi Daniel,
>
> Yes it is actually terminating and opening a new connection.
>
> I don't need HAProxy for anything at the moment, I was mentioning it
> for its support of the proxy protocol which enables applications to
> get source address information behind TCP load balancers.
>
> I'm not so much worried about the speed of kamailio - I'm confident
> it's quite fast. But for every piece of infrastructure I need to stand
> up, there's another opportunity for failure. Being able to use an ELB
> at the edge lets me place some of that hard work on Amazon, who has
> already thought of things like DNS load balancing, multi zone
> failover, etc.
>
> I think it'd be great if Kamailio could support something like proxy
> protocol to allow this scenario to work (it's just a single line sent
> right after a TCP connection is opened)
I haven't found any need myself for using haproxy, and as we work as a
community adding features as one needs them, if someone will submit a
patch for support of haproxy, will be considered, of course. Personally
I have no haproxy around, so not something that I quickly look further
at such feature.

Cheers,
Daniel
>
> Best,
> Colin
> On Thu, Jun 23, 2016 at 1:34 AM Daniel-Constantin Mierla
> <miconda at gmail.com <mailto:miconda at gmail.com>> wrote:
>
>     Hello,
>
>     is the tcp load balancer changing the source address, like
>     accepting the connection from the phone and then opening one to
>     kamailio?
>
>     Do you need haproxy because of other reasons or only for sip?
>
>     A kamailio load balancer (sip aware) is also quite fast.
>
>     Cheers,
>     Daniel
>
>
>     On 23/06/16 04:32, Colin Morelli wrote:
>>     Hey all,
>>
>>     I'm looking to put Kamailio behind a TCP load balancer that is
>>     SIP-unaware. My application is deployed in AWS and I'm tying to
>>     place Kamailio behind an ELB.
>>
>>     For the most part, everything is fine. For my specific
>>     implementation I'm disabling UDP as a signaling transport and
>>     using only TLS. This enables me to not have to worry about a
>>     SIP-aware LB at the edge because replies to an incoming request
>>     will be sent over the existing established TCP socket (avoiding
>>     any crazy routing requirements).
>>
>>     However - this poses an issue with source addresses. Does
>>     Kamailio support anything like the proxy protocol
>>     (http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt) for
>>     getting TCP stream information from a load balancer? Do I need to
>>     go back to exposing it directly to the world so that I can get
>>     source addresses?
>>
>>     Thanks,
>>     Colin
>>
>>
>>     _______________________________________________
>>     SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>     sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
>>     http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>     -- 
>     Daniel-Constantin Mierla
>     http://www.asipto.com - http://www.kamailio.org
>     http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda
>
>     _______________________________________________
>     SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
>     list
>     sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
>     http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>

-- 
Daniel-Constantin Mierla
http://www.asipto.com - http://www.kamailio.org
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20160624/afb6b10f/attachment.html>