Hi Daniel,<br><br>Yes it is actually terminating and opening a new connection.<br><br>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.<br><br>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.<br><br>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)<br><br>Best,<br>Colin<br><div class="gmail_quote"><div dir="ltr">On Thu, Jun 23, 2016 at 1:34 AM Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Hello,</p>
<p>is the tcp load balancer changing the source address, like
accepting the connection from the phone and then opening one to
kamailio?</p>
<p>Do you need haproxy because of other reasons or only for sip?</p>
<p>A kamailio load balancer (sip aware) is also quite fast.<br>
</p>
Cheers,<br>
Daniel</div><div bgcolor="#FFFFFF" text="#000000"><br>
<br>
<div>On 23/06/16 04:32, Colin Morelli wrote:<br>
</div>
</div><div bgcolor="#FFFFFF" text="#000000"><blockquote type="cite">
<div dir="ltr">Hey all,
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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).</div>
<div><br>
</div>
<div>However - this poses an issue with source addresses. Does
Kamailio support anything like the proxy protocol (<a href="http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt" target="_blank"><a href="http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt" target="_blank">http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt</a></a>)
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?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Colin</div>
</div>
<br>
<fieldset></fieldset>
<br>
</blockquote></div><div bgcolor="#FFFFFF" text="#000000"><blockquote type="cite"><pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Daniel-Constantin Mierla
<a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a> - <a href="http://www.kamailio.org" target="_blank">http://www.kamailio.org</a>
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></pre>
</div>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote></div>