Hi Hugh, Hi Daniel,
yes i think so. but i didnt know how i can prevent this. For testing i flush my config and use the default kamailio 3.2.3 config.
Still the same behavoir. Sipgate uac incoming calls got "failed to parse Route HF"
Full Trace (25kB) here:
I think the intressting part is that: http://srv01.0x300.de/failed_to_parse_Route_HF_3.txt
U 2012/04/20 14:54:34.419042 222.222.222.222:5060 -> 217.10.79.9:5060 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK173d.117f2af3.1;rport=5060. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK173d.117f2af3.1. Via: SIP/2.0/UDP 217.10.79.9:5060;branch=z9hG4bK36e26ce6;received=217.10.68.222. Via: SIP/2.0/UDP 217.116.117.71:5060;rport=5060;branch=z9hG4bK36e26ce6;received=217.116.117.71. From: "0180290xxxxxx" sip:0180290xxxxxx@sipgate.de;tag=as37f8b14a. To: sip:0049511xxxxxxxxx@sipgate.de;tag=ds-64cb3b56-ca705dad. Call-ID: 1959dd904259fcda3e288f293c744aca@sipgate.de. CSeq: 102 INVITE. Content-Length: 216. Content-Type: application/sdp. Record-Route: sip:172.20.100.74;r2=on;lr=on;ftag=as37f8b14a. Record-Route: sip:222.222.222.222;r2=on;lr=on;ftag=as37f8b14a. Record-Route: sip:217.10.79.9;lr;ftag=as37f8b14a. Record-Route: sip:172.20.40.2;lr=on. Record-Route: sip:217.10.79.9;lr;ftag=as37f8b14a. Supported: replaces. Supported: 100rel. Allow: INVITE. Allow: ACK. Allow: BYE. Allow: CANCEL. Allow: OPTIONS. Allow: NOTIFY. Allow: REFER. Allow: PRACK. Allow: INFO. Allow: UPDATE. Allow: MESSAGE. Contact: sip:172.20.100.61. . v=0. o=aculab-12645C01 314123282 314123282 IN IP4 172.20.100.61. s=-. c=IN IP4 172.20.100.71. t=0 0. m=audio 19516 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20.
U 2012/04/20 14:54:34.459000 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=z9hG4bK173d.117f2af3.3. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK173d.117f2af3.3. Via: SIP/2.0/UDP 217.10.79.9:5060;received=217.10.68.222;branch=z9hG4bK3fbd0091. Via: SIP/2.0/UDP 217.116.117.71:5060;received=217.116.117.71;branch=z9hG4bK3fbd0091;rport=5060. Route: sip:222.222.222.222;r2=on;lr=on;ftag=as37f8b14a,sip:172.20.100.74;r2=on;lr=on;ftag=as37f8b14a. Max-Forwards: 67. From: "0180290xxxxxx" sip:0180290xxxxxx@sipgate.de;tag=as37f8b14a. To: sip:0049511xxxxxxxxx@sipgate.de;tag=ds-64cb3b56-ca705dad. Contact: sip:0180290xxxxxx@217.116.117.71. Call-ID: 1959dd904259fcda3e288f293c744aca@sipgate.de. CSeq: 102 ACK. Content-Length: 0. X-hint: rr-enforced. .
U 2012/04/20 14:54:34.459205 222.222.222.222:5060 -> 172.20.100.74:5060 ACK sip:172.20.100.74;r2=on;lr=on;ftag=as37f8b14a SIP/2.0. Via: SIP/2.0/UDP 222.222.222.222;branch=z9hG4bKcydzigwkX. Via: SIP/2.0/UDP 217.10.79.9:5060;rport=5060;branch=z9hG4bK173d.117f2af3.3. Via: SIP/2.0/UDP 172.20.40.2;branch=z9hG4bK173d.117f2af3.3. Via: SIP/2.0/UDP 217.10.79.9:5060;received=217.10.68.222;branch=z9hG4bK3fbd0091. Via: SIP/2.0/UDP 217.116.117.71:5060;received=217.116.117.71;branch=z9hG4bK3fbd0091;rport=5060. Route: . Max-Forwards: 66. From: "0180290xxxxxx" sip:0180290xxxxxx@sipgate.de;tag=as37f8b14a. To: sip:0049511xxxxxxxxx@sipgate.de;tag=ds-64cb3b56-ca705dad. Contact: sip:0180290xxxxxx@217.116.117.71. Call-ID: 1959dd904259fcda3e288f293c744aca@sipgate.de. CSeq: 102 ACK. Content-Length: 0. X-hint: rr-enforced.