[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Linphone-developers] hi again :)
From: |
Klaus Darilion |
Subject: |
RE: [Linphone-developers] hi again :) |
Date: |
Wed, 23 Jul 2003 14:27:37 +0200 |
Maybe MSN is strictly RFC3265 conform, because RFC3265 section 3.2.4 defines:
...
NOTIFY requests MUST contain "Subscription-State" headers which indicate the
status of the subscription.
...
If adding this header does not work, please send the complete trace (SUBSCRIBE
+ NOTIFY) for further debugging.
Klaus
-----Original Message-----
From: Ivica Babarovic [mailto:address@hidden
Sent: Wed 23.07.2003 13:25
To: address@hidden
Cc:
Subject: Re: [Linphone-developers] hi again :)
Klaus Darilion wrote:
> The event header is missing, in your case:
>
> Event: presence
>
> regards,
> Klaus
>
>>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 ...
Thank you for your response Klaus. I added the Event header and still got a bad
request responce from
windows messenger. The last two packets look like this:
10.41.2.41 = Linphone
10.41.2.52 = Messenger
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=2930826916..From: <sip:address@hidden>;tag=42013..To:
"kvasenica" <sip:address@hidden>
;tag=3420d618-8da2-4f37-b1b5-42873a310a34..Call-ID: address@hidden: 1
NOTIFY..Contact: <sip:address@hidden>..Event: presence..user-agent: oSI
P/Linphone-0.8.0..Content-Length: 0....
#
U 10.41.2.52:2184 -> 10.41.2.41:5060
SIP/2.0 400 Bad Request..Via: SIP/2.0/UDP
10.41.2.41:5060;branch=2930826916..From: <sip:address@hidden>;tag=42013..To:
"kvasenica" <sip:address@hidden>;tag=3420d6
18-8da2-4f37-b1b5-42873a310a34..Call-ID: address@hidden: 1
NOTIFY..User-Agent: Windows RTC/1.0..Content-Length: 0....
exit
I observed this process betwen two messengers and I noticed that they dont use
event header. They add an XML message to the
body of a packet and thats how they achieve event notification. Here is how it
looks NOTIFY from one messenger to another:
10.41.2.56 1. messenger
10.41.2.197 2. messenger
U 10.41.2.56:1657 -> 10.41.1.197:13712
NOTIFY sip:10.41.1.197:13712 SIP/2.0..Via: SIP/2.0/UDP
10.41.2.56:8170..From:
<sip:address@hidden>;tag=edcda7b2-41d6-4cba-a8c9-d40f73e9860e..To: "emsy"
<sip:address@hidden>;tag=0285094
e-06f7-43a9-9cbe-f3914b428122..Call-ID: address@hidden: 1 NOTIFY..Contact:
<sip:10.41.2.56:8170>..User-Agent: Windows RTC/1.0..Content-Type:
application/xpidf+xml
..Content-Length: 346....<?xml version="1.0"?>.<!DOCTYPE presence.PUBLIC
"-//IETF//DTD RFCxxxx XPIDF 1.0//EN" "xpidf.dtd">.<presence>.<presentity
uri="sip:address@hidden;method=SUBSCRIBE"
/>.<ato
m id="1003">.<address uri="sip:10.41.2.56:8170;user=ip"
priority="0.800000">.<status status="open" />.<msnsubstatus substatus="online"
/>.</address>.</atom>.</presence>.
Naturaly, :) I tried to emulate this and added a simmilar body to my NOTIFY
packet on linphone.
Of course nothing happened .. bad request again.
Any ideas?
TIA,
Babarovic Ivica
_______________________________________________
Linphone-developers mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/linphone-developers