Hello Alex
Contact string from OK response (Fork of Linphone)
Contact: <sip:user_7u9bbhcwxz@96.231.222.110:52303;transport=tcp>;+sip.instance="<urn:uuid:64862a3d-4380-4e21-89db-9e718493a4b1>"
RURI header from FreeSwitch 1.6.20 ACK
Request-Line: ACK sip:user_7u9bbhcwxz@96.231.222.110:52303;transport=tcp SIP/2.0
Hi,
There are UAs and gateways out there which construct the ACK
incorrectly and always set the domain of the RURI to the next hop.
Does the Request URI of the ACK match the remote Contact in the 200 OK?
On Mon, May 14, 2018 at 09:39:44PM +0300, Sergey Safarov wrote:
> Hello
> I have a call with not passed ACK by Kamailio. http://prntscr.com/jhtobo
> Same behaviour i looked before when SIP endpoint contact string is wrong
> In this call look as contact string correct is correct (packets 7 and 8)
> and i not understand why ACK (packet 9) not passed to callee.
>
> Could you help me understand this.
>
> PCAP file is create using homer tracer and TCP transport packets is stored
> as UDP.
>
> Sergey
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users