Hi there, It seems that the Microsoft Messenger response to a loose routing Record-Route with a 400 Bad Request. Did anybody else have such an experience?
Christian If I send a packet like this: INVITE sip:[EMAIL PROTECTED]:8202 SIP/2.0 Via: SIP/2.0/UDP 192.168.0.22:5060;branch=z9hG4bK-rmqka3h9jwf6.0 Record-Route: <sip:192.168.0.22:5060;lr> Via: SIP/2.0/UDP 192.168.0.165:5060;branch=z9hG4bK-ca0302or28oi Max-Forwards: 19 From: "Christian Stredicke" <sip:[EMAIL PROTECTED]>;tag=xpnczoew15 To: <sip:[EMAIL PROTECTED]:8202> Call-ID: [EMAIL PROTECTED] CSeq: 1 INVITE Contact: <sip:[EMAIL PROTECTED]:5060;line=1> User-Agent: snom Version 1.12a Accept-Language: en Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, PRACK Supported: timer, 100rel, replaces Session-Expires: 7200 Content-Type: application/sdp Content-Length: 276 v=0 o=root 180 180 IN IP4 192.168.0.165 s=Call from 192.168.0.165 c=IN IP4 192.168.0.165 t=0 0 m=audio 10078 RTP/AVP 0 3 8 18 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:3 gsm/8000 a=rtpmap:18 g729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 MS Messenger responds with: SIP/2.0 400 Bad Request Via: SIP/2.0/UDP 192.168.0.22:5060;branch=z9hG4bK-rmqka3h9jwf6.0 Via: SIP/2.0/UDP 192.168.0.165:5060;branch=z9hG4bK-ca0302or28oi From: "Christian Stredicke" <sip:[EMAIL PROTECTED]>;tag=xpnczoew15 To: <sip:[EMAIL PROTECTED]:8202>;tag=eea83383-ee20-4895-ac0e-eff247a12f48 Call-ID: [EMAIL PROTECTED] CSeq: 1 INVITE Record-Route: <sip:192.168.0.22:5060;lr> User-Agent: Windows RTC/1.0 Content-Length: 0 -- Dr. Christian Stredicke snom technology AG sip:[EMAIL PROTECTED] pots:+493039833401 _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
