<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Thanks for instruction, DanB, really very appreciate!<br>but... unfrtunately in my case opensips just added transport=tls ro RURI but stil send to endpoint via UDP.<br><br>In sip debug i see<br>U 2014/10/09 09:02:38.060324 opensips_IP:5060 -> endpoint_IP:51584<br>INVITE sip:username@endpoint_IP:51584;transport=tls SIP/2.0.<br>But It is UDP. I checked opensips logs and don't see even attempt to use TLS.<br><br>May be I miss something. I have configured TLS server side on opensips and able to receive TLS from startpoint on opensips side and <br>this way I can register my softphones and even do outbound calls via TLS. I keep registrations on FS.<br><br>It works fine:<br>startpoint ---TLS--->opensisp----UDP--->FS<br><br>but here i have problem becasue opensips can not send to enpoint via TLS<br>FS---UDP--->opensips-----TLS--->endpoint<br><br>This way inbound calls doesnt worl.<br>Not sure but may be I have to configure something additional on opensisp to have possibility to send via TLS if RURI will have transport=tls<br><br>Please advice.<br>Thanks<br><br><br><div>> Date: Thu, 9 Oct 2014 09:17:44 +0200<br>> From: danb.lists@gmail.com<br>> To: freeswitch-users@lists.freeswitch.org<br>> Subject: Re: [Freeswitch-users] fs_path with a 'transport' parameter<br>> <br>> Yuriy,<br>> <br>> You should not need to select the socket from where you send out your <br>> request in OpenSIPS.<br>> Just do something like this:<br>> <br>> * Remove previous transport parameter from ruri (for the case it was <br>> added by fs_path). Have the feeling it will work also without removing <br>> since opensips will overwrite.<br>> * Add a new transport parameter with what you got in your private <br>> header as transport in ruri params.<br>> """if is_present_hf("X-EpTransport") $ru = $ru + ";transport=" + <br>> $hdr(X-EpTransport);"""<br>> * Remove the private header.<br>> * Relay the request as you did previously, things should automatically <br>> work out for you due to transport param.<br>> <br>> Cheers,<br>> DanB<br>> <br>> On 09.10.2014 02:13, freeswitch-users-request@lists.freeswitch.org wrote:<br>> > Thanks for the good advice, DanB!<br>> > I thought about this to be honest.<br>> > Yes, FS can add header with X-EndpointTransport: tls and opensisp can detect this.<br>> > But... I am still not sure how let opensips know that it should use tls instead of udp for invite to endpoint.<br>> > I tried to use<br>> > force_send_socket(tls:my_IP:5061);<br>> > But looks like I can't convert transport by this.<br>> ><br>> > Will try to send by<br>> > t_relay("tls:1.2.3.4:6677");<br>> ><br>> > Probably it is the question more for opensips list in this case but It is related I hope.<br>> ><br>> > Will be grateful for advice<br>> > Thanks<br>> <br>> <br>> _________________________________________________________________________<br>> Professional FreeSWITCH Consulting Services: <br>> consulting@freeswitch.org<br>> http://www.freeswitchsolutions.com<br>> <br>> Official FreeSWITCH Sites<br>> http://www.freeswitch.org<br>> http://confluence.freeswitch.org<br>> http://www.cluecon.com<br>> <br>> FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>> http://www.cudatel.com<br>> <br>> FreeSWITCH-users mailing list<br>> FreeSWITCH-users@lists.freeswitch.org<br>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>> http://www.freeswitch.org<br></div> </div></body>
</html>