[OpenSIPS-Users] TLS to UDP translation

[Bogdan-Andrei Iancu]

Hi Alexsandr,

Well, the problem is more complex a bit. I see you configured OpenSIPs 
to add PATH header to REGISTER before sending it to FS. The address in 
PATH has UDP transport, so FS (if supports PATH) should send the calls 
back to OpenSIPS by using the address from PATH (with UDP). The contact 
in register has TLS transport (and you fwd it to FS as it is), but it 
should not be used directly by FS because of the presence and priority 
of PATH hdr.

So, my only explanation is that FS does not support / not configured to 
handle PATH, so that it uses the address from contact, which is TLS.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


On 01/24/2013 03:04 PM, Chusov Alexsandr wrote:
> Yes Opensips proxying the REGISTER to FS.
> No, I get an error that TLC unsupported Profiles.
> it seems that this problem FS but I'm not sure yet. 
> http://jira.freeswitch.org/browse/FS-4989
>
>
> 2013/1/24 Bogdan-Andrei Iancu <bogdan at opensips.org 
> <mailto:bogdan at opensips.org>>
>
>     Hi Chusov,
>
>     Is your OpenSIPS proxying the REGISTER from clients to FS ? Do you
>     see how the INVITE FS wants to send via TLS looks like ?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>     OpenSIPS Founder and Developer
>     http://www.opensips-solutions.com
>
>
>     On 01/22/2013 12:36 PM, Chusov Alexsandr wrote:
>>     Hello.
>>     I'm trying to deploy Opensips  as a front-end for TLS-UDP
>>     translation, as a back-end would be FreeSWITCH.
>>     TLS -> Opensips -> UDP -> FreeSWITCH
>>     TLS work fine end point is registered. But when freeswitch send
>>     invite he tries use TLS instead of UDP. I understand the problem
>>     in "transport=tls"
>>
>>     Example register message:
>>
>>     REGISTER sip:10.222.0.22 SIP/2.0
>>     Record-Route: <sip:10.222.0.22;r2=on;lr=on>
>>     Record-Route: <sip:10.222.0.22;transport=tls;r2=on;lr=on>
>>     Via: SIP/2.0/UDP 10.222.0.22;branch=z9hG4bKcydzigwkX;i=1
>>     Via: SIP/2.0/TCP
>>     10.222.1.221:5060;branch=z9hG4bK317662383;rport=49521;alias
>>     From: <sip:2128 at 10.222.0.22
>>     <mailto:sip%3A2128 at 10.222.0.22>>;tag=905919494
>>     To: <sip:2128 at 10.222.0.22 <mailto:sip%3A2128 at 10.222.0.22>>
>>     Call-ID: 1735784069-5060-1 at BA.CCC.B.CCB
>>     <mailto:1735784069-5060-1 at BA.CCC.B.CCB>
>>     CSeq: 2011 REGISTER
>>     Contact:
>>     <sip:2128 at 10.222.1.221:5060;transport=tls>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000B823DB6B2>"
>>     Max-Forwards: 69
>>     User-Agent: Grandstream GXP1405 1.0.5.10
>>     Supported: path
>>     Expires: 0
>>     Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY,
>>     INFO, REFER, UPDATE, MESSAGE
>>     Content-Length: 0
>>     Path:
>>     <sip:10.222.0.22;lr;received='sip:10.222.1.221:49521;transport=tls'>
>>
>>
>>
>>     Sorry for my english
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org  <mailto: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/20130128/4f113571/attachment.htm>