Hi Denis,
The ACK is routed based on the RR headers that were collected by INVITE
and returned in 200 OK. For such a scenario to work, opensips is doing
double routing (adds for itself 2 RR headers, one with the inbound
interface, one with the outbound interface).
Could you post the SIP capture of such a call to check if correct from
SIP point of view?
Regards,
Bogdan
Denis Putyato wrote:
Hello!
I have a such problem.
Opensips using 2 ports
One – 5068 for client which must register on Opensips
Second – 5060 for all other clients.
1) Client А registering on Opensips (socket: udp:2.2.2.2:5068). Client
A is behind NAT.
2) Client А receives incoming call (via lookup() function).
3) Call has such way
Cisco (source port 11111 sends INVITE to port 5060 of Opensips) –
Opensips (receives INVITE from Cisco to port 5060 and sends the INVITE
to client from source port 5068 to some client`s port) – Client A.
Everything work fine until client А answers. Then Client A sends to
Opensips (port 5068) 200 OK, Opensips retransmit it to Cisco (from
port 5060 to 11111), Cisco sends to Opensips ACK (from port 11111 to
5060) AND Opensips retransmit this ACK to client`s port FROM PORT
5060, BUT NOT 5068. This ACK didn`t reach client A because of NAT.
Thank you for any help.
------------------------------------------------------------------------
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Bogdan-Andrei Iancu
OpenSIPS Event - expo, conf, social, bootcamp
2 - 4 February 2011, ITExpo, Miami, USA
www.voice-system.ro
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
