TCP is very resource demanding and for those situations where the server is not required to work with TCP is very usefull to have the option of disabling TCP part.<br><br>There are examples, such as embedded platforms with controlled SIP UA connecting to it where there's no need for TCP stuff and lots of resources are available for other processes.<br>
<br>Not much related to RFCs...<br><br>Sam<br><br><div class="gmail_quote">2009/12/18 <span dir="ltr"><<a href="mailto:opensips@encambio.com">opensips@encambio.com</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;">
<br>
Hello list,<br>
<br>
Somewhere I read that OpenSIPS 1.6.0 allows to disable TCP but not<br>
UDP because UDP is required by the SIP RFC, so I looked at the RFCs.<br>
<br>
RFC 2543 states that 'UDP and TCP should be implemented.'<br>
RFC 3261 states that 'UDP and TCP must be implemented.'<br>
<br>
It would seem intuitive that OpenSIPS developers force the OpenSIPS<br>
runtime to conform to the most recent RFC, meaning that neither UDP<br>
nor TCP listening is possibly disabled.<br>
<br>
...or the developers allow the admin (config file editor) to disable<br>
either UDP or TCP. This could be because the developers want to<br>
support the oldest RFC for backwards compatibility for example,<br>
or because they want to allow the admin to make the decision<br>
themselves.<br>
<br>
But the current release of OpenSIPS does not allow UDP to be<br>
disabled, while allowing TCP to be disabled. Can somebody explain<br>
why this policy was chosen or what is wrong with my logic?<br>
<br>
Regards,<br>
Brian<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>
</blockquote></div><br>