Yuriy, You should not need to select the socket from where you send out your request in OpenSIPS. Just do something like this: * Remove previous transport parameter from ruri (for the case it was added by fs_path). Have the feeling it will work also without removing since opensips will overwrite. * Add a new transport parameter with what you got in your private header as transport in ruri params. """if is_present_hf("X-EpTransport") $ru = $ru + ";transport=" + $hdr(X-EpTransport);""" * Remove the private header. * Relay the request as you did previously, things should automatically work out for you due to transport param. Cheers, DanB On 09.10.2014 02:13, freeswitch-users-request@lists.freeswitch.org wrote:
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 force_send_socket(tls:my_IP:5061); But looks like I can't convert transport by this.
Will try to send by t_relay("tls:1.2.3.4:6677");
Probably it is the question more for opensips list in this case but It is related I hope.
Will be grateful for advice Thanks