Hi Bogdan,<div><br></div><div>Thanks for the suggestions!</div><div><br></div><div>So this means we´ll need new "listen" lines, right? Plus, we´d need some mechanism to round-robin through the destinations sockets - like dispatcher?</div>
<div><br></div><div>We´re also using force_send_socket(). Will we need to round-robin through the many ports we´re listening as well and choose one to force, or can we keep only one socket for that? In other words, could OS1 use only 1 output interface and still create multiple connections (given that OS1 is sending each call to a different OS2 interface at a time)?</div>
<div><br></div><div>Thanks again.</div><div>Mariana.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 8, 2012 at 2:21 PM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div bgcolor="#ffffff" text="#000000">
<tt>Hi Mariana,<br>
<br>
Because of the TCP conn reusage, between 2 SIP entities preserving
their IP and port, you will have only 1 TCP conn (per direction).
This will lead to a "tunneling" effect between 2 proxies - all
traffic will be pushed via a single connection.<br>
<br>
To avoid this, use multiple TCP interfaces (same ip but different
ports) between the 2 opensips - and when OS1 has to send to OS2 to
do dispatching over all interfaces of OS2 ; and vice versa. This
will create multiple connections between the 2 servers.<br>
<br>
I know it is not nice, but it solves the purpose - maybe in long
term we need some logical way to control the connection re-usage
(maybe depending on load/traffic - if too much, avoid reusing,
create a new conn).<br>
<br>
Regards,<br>
</tt>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre><div><div class="h5">
<br>
On 11/08/2012 01:52 PM, Mariana Arduini wrote:
</div></div><blockquote type="cite"><div><div class="h5">Hello all,
<div><br>
</div>
<div>We are using 2 OpenSIPS servers and TCP between them:</div>
<div><br>
</div>
<div>tcp ---> OSIPS1 <--- tcp ---> OPSIPS2 <--- tcp</div>
<div><br>
</div>
<div>OSIPS2 has a bunch of children processes running, but we can
only see few of them actually being used. When we use SIPp
scripts instead of OPSIPS1 and set it to use 1 TCP connection
per call (parameter -t tn), then we can see more than just a few
OPSIPS2 children processes being used.</div>
<div><br>
</div>
<div>The problem is this is decreasing OSIPS2 performance, so we
need to have OSIPS1 using more than just 1 TCP connection. Is
this possible?</div>
<div><br>
</div>
<div>Thanks in advance for any help!</div>
<div>
Mariana.</div>
</div></div><pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</div>
</blockquote></div><br></div>