[OpenSIPS-Users] OpenSIPS TLS and rtpproxy

[Bogdan-Andrei Iancu]

Hello,

It means your config cannot deal with NATed clients, and for TCP is the
routes doing the translation.

I suggest to enable NAT traversal into your opensips cfg - you can
re-generate the config with NAT traversal support.

Regards,

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


On 07/05/2013 12:30 PM, debelizmaj wrote:
> Bogdan,
> Thank you. I checked messages between caller-server-callee and notice
> difference. 
> In all messages Via, From and To fields in TCP are filled with server local
> address but in TLS signaling with public address (firewall transwer all
> network from public ip to server local ip)
>
> Client nat public ip is 89.216.xx.xx
> Server's firewall public ip 89.216.yy.yyy
>
> example:
> TLS. server->caller
>
> SIP/2.0 200 OK 
> Max-Forwards: 70 
> Record-Route: <sip:89.216.yy.yyy:5061;transport=tls;lr;did=5e4.e80bf6d1> 
> Via: SIP/2.0/TLS
> 192.168.1.101:5061;received=89.216.xx.xx;rport=21631;branch=z9hG4bK1523675438 
> From: <sip:1003 at 89.216.yy.yyy>;tag=2087179651 
> To: <sip:1001 at 89.216.yy.yyy>;tag=654266152 
> Call-ID: 1592566511 at 192.168.1.101 
> CSeq: 702 INVITE 
> Contact: <sip:1001 at 192.168.1.100:58163;transport=tcp> 
> Content-Type: application/sdp 
> Content-Length: 791 
>
> v=0 
> o=- 3344 3344 IN IP4 192.168.1.100 
> s=Minisip Session 
> t=0 0 
> a=key-mgmt:mikey
> AQgFANOSfdUCAABIaS7ZAAAAAAAzHkiuAAAAAAMA1YDrq2igbp8DAK93XBxNMG+FSpQ7J/sQH62rdfsUh8g9LLk/3QwXDUs0xEIdVmbHAxVoyPJf/BVmE6QvYC70mdLViX3i38P3XGhN6UdIV8xurKZVHWfH45BJ3TeqvAfVbJOvqO2kP3OjoM+CVSITvqom5HGijhMR/INj3315Y3sRytHMmY7dbh68WR8kXBviv47bqRWEgxiwoEZBwgN/p1WqBsQ5EV3MT0Zk8QhpXYOnEkuaYh74qY5aUINy4drRMMiqZWA1UOt4DgABAH5TjtixGDwSDHz4LFxVG2Vd9Ml5wOY+7GW6SCkHk4RR/rOUsxbNcNuvC0wJY6L2BJpKigQ97J1XuJnANjIwo6t3AwfOoWO74yxmjc7piid8LVStOCE1zeDtvuEStkKN8fQ70tbLahRaL8DLBdtZ4/BgY5s8djOPjfsTmy5ZALGaWai+knbNGrewUjH457Fid5vFuHNQY+YEwKQxPzy4BK376o5Nu3swSO3qmFfJkr/J3tX6kR+4zH7nvQFYGnaVwgAAAAAAAbnXQEJtF83kwKTX1Fgka4iXbAwZ
> m=audio 56124 RTP/SAVP 8 
> c=IN IP4 10.99.10.249 
> a=rtpmap:8 PCMA/8000/1 
> a=fmtp:8 
> a=nortpproxy:yes
>
> and 
>
> TCP server->caller
>
> SIP/2.0 200 OK 
> Max-Forwards: 70 
> Record-Route: <sip:89.216.yy.yyy;transport=tcp;lr;did=029.725bafb3> 
> Via: SIP/2.0/TCP
> 192.168.1.101:5060;received=89.216.xx.xx;rport=49387;branch=z9hG4bK1169924990 
> From: <sip:1003 at 10.99.10.249:5060>;tag=1234642285 
> To: <sip:1001 at 10.99.10.249:5060>;tag=2114921007 
> Call-ID: 469267232 at 192.168.1.101 
> CSeq: 402 INVITE 
> Contact: <sip:1001 at 192.168.1.100:5060;transport=tcp> 
> Content-Type: application/sdp 
> Content-Length: 791 
>
> v=0 
> o=- 3344 3344 IN IP4 192.168.1.100 
> s=Minisip Session 
> t=0 0 
> a=key-mgmt:mikey
> AQgFAKI1epQCAAAsRYooAAAAAAB/f8pcAAAAAAMA1YDoOOkTlDEDALIxavzmvlhu6E9oELjhXEGLc8lwerqD9XwfGHHadm/LaE+roPfKUIqqIAgqFTWv5FR+bF0paWW9NDDK7QSXkQMd+goW32TSHmkowVoLz+HQXTIlyLm6xDDFcz5ceVCGjdLupqYhNAwncUH0/bYhL1k3kpxwGVu3gSWBkqFk8PZ1Iu8zZrT3t042GHdj43IN4ZfNV966n2IN/6HHhJjTiAUazmKlG1RhXpQyuvVrCptn8U2jb154ukJmqLMRjQWP4wABACExe7sgaxjx+G6KTdu0tFbI81/2FSsrELY9KNmzudUoExSd1DtzPCVefFLL3SlrajyQDiEXz63HvAOEiXLbpLnFoNSibi/Twsa8MlOHu6zdrFPrmw6KfH6nmZ99CzB8y5Hjqd7P/4aAdiVlBJtu0rblY3OUlSgVhdCdqqRTa9Nkv1sAdJDYM9hoa0g/EzvEuyeUXuO82Rr/YMD/cemu7y6M++y2AsxyxQ9VWIFP0DA02LqCKQalko/jhifwx3bh6AAAAAAAAVyLJU07jcqW68Iv8u+sdAL9CD8h
> m=audio 46486 RTP/SAVP 8 
> c=IN IP4 10.99.10.249 
> a=rtpmap:8 PCMA/8000/1 
> a=fmtp:8 
> a=nortpproxy:yes
>
> Is this problem? difference between addresses?
>
>
>
> --
> View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-TLS-and-rtpproxy-tp7587053p7587068.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>