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
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
Hi Ssergey, the ACK seem OK, but the R-URI does not contain the "sip.instance" parameter defined in the 200 OK's Contact. Usually all contact parameter should be preserved when constructing the ACK R-URI. Does your server receive the ACK, but it is not able to forward it back to the callee (if yes, do you see any ERROR in the logs) ? Or it just don't receive the ACK at all?
Daniel
On 05/14/2018 08:39 PM, 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
Thanks Daniel for your response. My response in text inline.
вт, 15 мая 2018 г. в 11:27, Daniel Grotti dgrotti@sipwise.com:
Hi Ssergey, the ACK seem OK, but the R-URI does not contain the "sip.instance" parameter defined in the 200 OK's Contact. Usually all contact parameter should be preserved when constructing the ACK R-URI. Does your server receive the ACK, but it is not able to forward it back to the callee (if yes, do you see any ERROR in the logs) ?
Yes kamailio is received ACK message but not forwarder (loose routed) to callee. I not able to kamailio log (tow many debug info). I goes to clarify what need to look and then reproduce. End user is reported silence after answer. Here 1) caller side is FreeSwitch 1.6.20 2) callee side is forked linphone
Sergey
Or it just don't receive the ACK at all?
Daniel
On 05/14/2018 08:39 PM, 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 Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-
Alex Balashov -
Daniel Grotti -
Sergey Safarov