[OpenSIPS-Users] Disabling TCP or UDP (RFC forbidden)

[samuel]

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.

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.

Not much related to RFCs...

Sam

2009/12/18 <opensips at encambio.com>

>
> Hello list,
>
> Somewhere I read that OpenSIPS 1.6.0 allows to disable TCP but not
> UDP because UDP is required by the SIP RFC, so I looked at the RFCs.
>
>  RFC 2543 states that 'UDP and TCP should be implemented.'
>  RFC 3261 states that 'UDP and TCP must be implemented.'
>
> It would seem intuitive that OpenSIPS developers force the OpenSIPS
> runtime to conform to the most recent RFC, meaning that neither UDP
> nor TCP listening is possibly disabled.
>
> ...or the developers allow the admin (config file editor) to disable
> either UDP or TCP. This could be because the developers want to
> support the oldest RFC for backwards compatibility for example,
> or because they want to allow the admin to make the decision
> themselves.
>
> But the current release of OpenSIPS does not allow UDP to be
> disabled, while allowing TCP to be disabled. Can somebody explain
> why this policy was chosen or what is wrong with my logic?
>
> Regards,
> Brian
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20091223/bc159e3e/attachment.htm