Hello Daniel,
i retried it and got this ACK message:
U 2012/04/20 10:34:18.272371 217.10.79.9:5060 -> 222.222.222.222:5060 ACK sip:222.222.222.222:5060 SIP/2.0. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bKbe0b.eb6512c7.3. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bKbe0b.eb6512c7.3. Via: SIP/2.0/UDP 217.10.79.9:5060;received=217.10.68.226;branch=z9hG4bK103ad8e1. Via: SIP/2.0/UDP 217.10.67.11:5060;received=217.10.67.11;branch=z9hG4bK103ad8e1;rport=5060. Route: sip:222.222.222.222;r2=on;lr=on;ftag=as7d93d4fe;did=b12.cd29f421,sip:172.20.100.74;r2=on;lr=on;ftag=as7d93d4fe;did=b12.cd29f421. Max-Forwards: 67. From: "0180290xxxxxx" sip:0180290xxxxxx@sipgate.de;tag=as7d93d4fe. To: sip:0049511xxxxxxxxx@sipgate.de;tag=ds-23faf43a-2782dca0. Contact: sip:0180290xxxxxx@217.10.67.11. Call-ID: 77ec46cd3d1b577137a57d3a589ce0cf@sipgate.de. CSeq: 102 ACK. Content-Length: 0. X-hint: rr-enforced.
2012/4/20 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
I tested with the ACK from the previous sip trace and the parsing went fine. Do you do changes over the sip message and then apply them before loose_route()?
If not, send the ack that matches the log messages you just added.