[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Linphone-developers] hi again :)

From: Ivica Babarovic
Subject: [Linphone-developers] hi again :)
Date: Tue, 22 Jul 2003 15:12:56 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

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. :) is Linphone client is MSN client

U ->
  NOTIFY sip: SIP/2.0..Via: SIP/2.0/UDP;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 ->
  SIP/2.0 400 Bad Request..Via: SIP/2.0/UDP;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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]