Hmm... Well, in this case I'll try to do the following: check message length before forwarding. If it's close to maximum limit - use TCP transport, otherwise - UDP.<br><br><div class="gmail_quote">2009/11/2 Iñaki Baz Castillo <span dir="ltr"><<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">El Viernes, 30 de Octubre de 2009, Alexander escribió:<br>
<div class="im">> BTW, what do you think about possible performance loss because of TCP? Or<br>
> it's neglible?<br>
<br>
</div>The problem of SIP TCP in OpenSIPS is not the performance, but the fact that<br>
each running OpenSIPS process blocks until its TCP transaction in processed.<br>
<font color="#888888"><br>
<br>
--<br>
</font><div><div></div><div class="h5">Iñaki Baz Castillo <<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>