8 Oct
2014
8 Oct
'14
9:45 a.m.
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, DanB On 07.10.2014 21:06, freeswitch-users-request@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?