[Linphone-developers] hi again :)

[Ivica Babarovic]

Well I managed to come to the stage when I send NOTIFY packet but I get
respond from MSN that I'm sending a >>bad request<<. So, I managed to get
over the problem of missing call-leg.
How do I find out why is my request badly formed. In RFC it says:
"The Reason-Phrase SHOULD identify the syntax problem in more detail,
for example, (Missing Call-ID header field)."
Where does this messages pop out? Where do I find out this Reason-Phrase?

Here are my last two packets from the process of subscribing.
Number 5. and 6. from previous mail if you remeber. :)

10.41.2.41 is Linphone client
10.41.2.52 is MSN client

U 10.41.2.41:5060 -> 10.41.2.52:8435
  NOTIFY sip:10.41.2.52:8435 SIP/2.0..Via: SIP/2.0/UDP 10.41.2.41:5060;branch=1190815359..From: 
<sip:address@hidden>;tag=3f645..To: "kvasenica" <sip:address@hidden>
  ;tag=e152a09e-30c9-4ce9-81c0-b83119b04e44..Call-ID: address@hidden: 1 
NOTIFY..Contact: <sip:address@hidden>..user-agent: oSIP/Linphone-0.8.0.
  .Content-Length: 0....
#
U 10.41.2.52:1956 -> 10.41.2.41:5060
  SIP/2.0 400 Bad Request..Via: SIP/2.0/UDP 10.41.2.41:5060;branch=1190815359..From: 
<sip:address@hidden>;tag=3f645..To: "kvasenica" <sip:address@hidden>;tag=e152a0
  9e-30c9-4ce9-81c0-b83119b04e44..Call-ID: address@hidden: 1 
NOTIFY..User-Agent: Windows RTC/1.0..Content-Length: 0....



TIA ... really need your help here. Dont know how to find out what is wrong
with NOTIFY packet. Why it is badly formed.

Best regards,
Babarovic Ivica