Hello,
Not clear from the diagram, but the UAC2 is behind the NAT, not OpenSIPS
and UAC1, right ?
As Laszlo suggested, you need a force_rport(), but not only for INVITE,
but for all requests coming from behind the NAT - like the BYE, in your
case.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 04/04/2013 05:29 PM, Гогичашвили Андрей wrote:
Hello! I have some trouble with nat handling.
I have such scheme:
uac1---opensips---(NAT)---uac2
I call to UAC2 and signaling establishment is ok. When UAC2 sends
BYE opensips translates 200OK (received from UAC1) to the wrong port.
BYE generated by UAC2 has such via header:
"Via: SIP/2.0/UDP 192.168.18.137:5060;branch=z9hG4bK8b517b11a415"
and the BYE comes from U 2013/04/04 17:21:50.287792 1.1.1.1:59292 ->
2.2.2.2:5068
Where 1.1.1.1 -- nat, 2.2.2.2 - opensips
Opensips adds one more via header to the BYE:
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bK7f45.debc1592.0.
and changes first via header by adding received field:
Via: SIP/2.0/UDP
192.168.18.137:5060;received=1.1.1.1;branch=z9hG4bK8b517b11a415
200 OK got from UAC1 opensips tries to send not to 1.1.1.1:59292 but
to 1.1.1.1:5060
The question is how can we make opensips to send 200 OK to 59292 port?
Thank you for any help.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
