21 Jul
2003
21 Jul
'03
7:05 p.m.
Hi,
I am testing SER version 0.8.11pre29 with two MSN Messenger(v4.6) clients.
I tried to send the following MESSAGE through SER with record-route header
added
by SER. However, the receiving MSN client responded with a 400 Bad Request
for that
message.
MESSAGE sip:192.170.106.49:7281 SIP/2.0
Max-Forwards: 10
Record-Route:
<sip:kchu@192.170.106.71;ftag=720e429c-41f0-4e2e-b7d0-fb238d4bc85c;lr>
Via: SIP/2.0/UDP
192.170.106.71;branch=z9hG4bK0c1f.a4d6a5.0
Via: SIP/2.0/UDP 192.170.106.101:8111
From: "ychu"
<sip:ychu@192.170.106.71>;tag=720e429c-41f0-4e2e-b7d0-fb238d4bc85c
To: <sip:kchu@192.170.106.71>
Call-ID: c09c262c-2f27-489e-b69d-01ae5a5ddb84(a)192.170.106.101
CSeq: 1 MESSAGE
Contact: <sip:192.170.106.101:8111>
User-Agent: Windows RTC/1.0
Content-Type: text/plain;
charset=UTF-8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AU
wAlADIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAOwAgAEUARgA9ADsAIABDAE8APQAwADsAIABDA
FMAPQAwADsAIABQAEYAPQAwAA0ACgANAAoA
Content-Length: 12
I noticed that there is a "ftag" parameter in the Record-Route header, but I
can't
find any definition for it from rfc3261. Is that a new parameter defined in
somewhere?
I was just wondering that it is the reason why MSN client was complaining
about
that message?
BR,
Kevin