[Freeswitch-users] fs_path with a 'transport' parameter
nasida at live.ru
Wed Oct 8 19:32:54 MSD 2014
Thanks for the good advice, DanB!
I thought about this to be honest.
Yes, FS can add header with X-EndpointTransport: tls and opensisp can detect this.
But... I am still not sure how let opensips know that it should use tls instead of udp for invite to endpoint.
I tried to use
But looks like I can't convert transport by this.
Will try to send by
Probably it is the question more for opensips list in this case but It is related I hope.
Will be grateful for advice
> Date: Wed, 8 Oct 2014 11:45:48 +0200
> From: danb.lists at gmail.com
> To: freeswitch-users at lists.freeswitch.org
> Subject: Re: [Freeswitch-users] fs_path with a 'transport' parameter
> Hi Yuriy,
> We have solved this issue by adding a custom header with the transport
> OpenSIPS need to use when sending the call out (extract that info in
> OpenSIPS, eg: X-EndpointTransport: udp).
> A more elegant solution would be custom ruri params being sent out by
> FreeSWITCH, however not sure how doable that would be technically
> speaking since the transport is automatically written out from the one
> you set in fs_path.
> Hope this helps,
> On 07.10.2014 21:06, freeswitch-users-request at lists.freeswitch.org wrote:
> > I can add transport parameter I need on FS side, but how opensips will
> > >know that it should use a different transport for INVITE to an endpoint?
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> Official FreeSWITCH Sites
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users