Yes, multiple listeners (same ip, different ports) on receiver (let's
say OS2) and using dispatcher on OS1 to do round-robin (or so) over all
listeners on OS2.
force_send_socket() is to control the interface the message will go out
- what you actually have to do is to choose different destinations (OS1
-> OS2) to ensure a proper LB of traffic through all TCP conns.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 11/08/2012 07:19 PM, Mariana Arduini wrote:
Hi Bogdan,
Thanks for the suggestions!
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?
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)?
Thanks again.
Mariana.
On Thu, Nov 8, 2012 at 2:21 PM, Bogdan-Andrei Iancu
<[email protected] <mailto:[email protected]>> wrote:
Hi Mariana,
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.
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.
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).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 11/08/2012 01:52 PM, Mariana Arduini wrote:
Hello all,
We are using 2 OpenSIPS servers and TCP between them:
tcp ---> OSIPS1 <--- tcp ---> OPSIPS2 <--- tcp
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.
The problem is this is decreasing OSIPS2 performance, so we need
to have OSIPS1 using more than just 1 TCP connection. Is this
possible?
Thanks in advance for any help!
Mariana.
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
