[OpenSIPS-Users] TLS to UDP

[Daniel Goepp]

We have run into similar situations where transport changes.  The most
common reason that we have found is due to non-explicit transport.  We have
implemented explicit setting of transport in the contact / record-route to
make sure that transport is honored.  If there is no transport, the RFC
says that UDP should be used.

Some examples:

add_rr_param(";transport=$pr");

and

search_append("Contact:.*sip:[^>[:cntrl:]]*", ";transport=tls");

These are just some examples, you will of course need to play around with
your config based on your needs and logic.



-dg


On Wed, Mar 6, 2013 at 8:47 AM, Chris Martineau <chris at ghosttelecom.com>wrote:

>  Hi,****
>
> ** **
>
> I have configured an incoming TLS service from the client which is working
> fine.****
>
> ** **
>
> Opensips converts it to UPD and feeds it to some freeswitch servers.****
>
> ** **
>
> All works okay until cleardown, whereby if the far end clears, the BYE
> message is not converted from UDP back to TLS.****
>
> ** **
>
> Should opensips remember the dialog path in this instance and route the
> BYE back over TLS or do I have to create a route in the config to handle
> this?****
>
> ** **
>
> If I have to create a route how do identify the BYE as needing to be
> returned over TLS? I have mixed calls on the server, some tls some udp and
> the udp works fine.****
>
> ** **
>
> Any examples would be great.****
>
> ** **
>
> I am on 1.6.4.****
>
> ** **
>
> Regards****
>
> ** **
>
> Chris****
>
> ** **
>
> _______________________________________________
> 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/20130306/c567db6f/attachment.htm>