[OpenSIPS-Users] Transport identification

Daniel Goepp dan at goepp.net
Fri Mar 5 18:18:06 CET 2010


We are doing some interop work with another switch, and it is having some
trouble with TCP vs UDP.  Because of the packet size for these specific
calls we need to do them TCP.  However the record-route in our 200 OK has no
transport set, and according to the RFC, no transport for SIP default is
UDP.  This means that all our signaling is TCP, until we get an ACK back
from this box, and it then is UDP, but too big and breaks the call.  I have
found the add_rr_param, so I could do a add_rr_param(";transport=tcp"), but
I only want to do this for calls that are currently using TCP.  I looked for
a function to test the protocol used, but couldn't find one.  Anyone know
what it is?  Also, it would seem the appropriate thing for OpenSIPS to do
would be to automatically put the ;transport=xxx in the RR based on the
current protocol of the dialog.  Thoughts on that?

Thanks

-dg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20100305/24098caa/attachment.htm 


More information about the Users mailing list