7 Oct
2016
7 Oct
'16
3:30 a.m.
I think the Route set as presented in the first email is correct. The
Client is also having a proxy, so the caller device has to use the Route
set from bottom up, sending first to its proxy, which should send to
Kamailio's public IP. If the caller device is sending directly to
kamailio, then there is something wrong with that device.
Cheers,
Daniel
On 06/10/16 16:38, Alex Balashov wrote:
The order of the Record-Route headers is very
relevant, and must
strictly correspond to the order in which the intermediate proxy chain
is traversed. The RR header of the Kamailio closest to your Client
will be at the top of the RR stack, and this will be the first hop in
the Route set used in in-dialog requests (e.g. end-to-end ACKs, BYEs,
reinvites).
Thus, it is entirely appropriate that your client is trying to send
the ACK to 192.168.0.200 on the network/transport layer.
-- Alex
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Oct 24-26, 2016 - http://www.asipto.com