Subject: Re: [Users] Presence module and Snom phones
From: Anca Vamanu <[email-masked]>
To: Peter Gradwell <[email-masked]>
Date: Wed, 15 Nov 2006 17:39:56 +0200

Hello,

As described in RFC 4235 ,   dialog  is an event package for INVITE- 
initiated dialog usages.
It seems to allows users to subscribe to another user and to receive 
notification of the changes in
state of  INVITE-initiated dialog usages in which the subscribed-to user 
is involved.
It is a different package  not connected to presence, so this Subscribe 
should not be handled by
the presence module. 
Openser does not have support for this package, so the reply you get is  
"489 Bad Event".

All the best,

Anca Vamanu

Peter Gradwell wrote:

>Hi
>
>We are wondering if anyone has used the new presence module with Snom
>phones because it looks like it just doesn't work with the subscribe
>types that snom use.
>
>Basically snom uses Event: dialog in the headers which the module
>doesn't support.
>
>Here is the subscribe after I hacked it to allow Event: dialog
>
>U 2006/11/15 14:22:04.699050 193.84.87.60:5082 -> 193.111.201.74:5060
>SUBSCRIBE sip:[email-masked];user=phone SIP/2.0.
>To: <sip:[email-masked];user=phone>.
>From: <sip:[email-masked]>;tag=23c9f970.
>Via: SIP/2.0/UDP
>193.84.87.60:5082;branch=z9hG4bK-d87543-65b974429da21b246a5f-1-cHAyZGM4N
>jUxNzk0YjIyNTJkNjdmNw..-d87543-.
>Call-ID: 0c296edb42d0dd85472907b1da99411d.
>CSeq: 452392058 SUBSCRIBE.
>Contact:
><sip:[email-masked]:5082;line=
>27nd4hcq>.
>Expires: 3600.
>Max-Forwards: 69.
>Accept: application/dialog-info+xml.
>Event: dialog.
>Content-Length: 0.
>.
>
>
>U 2006/11/15 14:22:04.707409 193.111.201.74:5060 -> 193.84.87.60:5082
>SIP/2.0 200 OK.
>To:
><sip:[email-masked];user=phone>;tag=20c56ba31bbe85b9bc9d
>0e09f876aff7.24f5.
>From: <sip:[email-masked]>;tag=23c9f970.
>Via: SIP/2.0/UDP
>193.84.87.60:5082;branch=z9hG4bK-d87543-65b974429da21b246a5f-1-cHAyZGM4N
>jUxNzk0YjIyNTJkNjdmNw..-d87543-.
>Call-ID: 0c296edb42d0dd85472907b1da99411d.
>CSeq: 452392058 SUBSCRIBE.
>Expires: 3600.
>Server: OpenSer (1.2.0-dev6-notls (i386/linux)).
>Content-Length: 0.
>Warning: 392 193.111.201.74:5060 "Noisy feedback tells:  pid=14435
>req_src_ip=193.84.87.60 req_src_port=5082
>in_uri=sip:[email-masked];user=phone
>out_uri=sip:[email-masked] via_cnt==1".
>.
>
>Then openser sends out this notify
>
>U 2006/11/15 14:22:04.733404 193.111.201.74:5060 -> 193.84.87.60:5082
>NOTIFY
>sip:[email-masked]:5082;line=2
>7nd4hcq SIP/2.0.
>Via: SIP/2.0/UDP 193.111.201.74;branch=z9hG4bKfc5a.9a187a95.0.
>To: sip:[email-masked];tag=9d6ee568.
>From: sip:[email-masked];tag=10.14435.1163600524.9.
>CSeq: 183348005 NOTIFY.
>Call-ID: d250aa54d4fab3ffa3e96ac7ea73303f.
>User-Agent: OpenSer (1.2.0-dev6-notls (i386/linux)).
>Event: dialog.
>Contact: <sip:[email-masked]>.
>Subscription-State: pending;expires=3600.
>Content-Type: application/watcherinfo+xml.
>.
>
>Which is most significantly the wrong content type for snoms (as the
>subscribe said, they want application/dialog-info+xml) and also doesn't
>have a message body on the notify - so the snom tells openser where to
>go:
>
>U 2006/11/15 14:22:04.841722 193.84.87.60:5082 -> 193.111.201.74:5060
>SIP/2.0 489 Bad Event.
>To: <sip:[email-masked]>;tag=9d6ee568.
>From: <sip:[email-masked]>;tag=10.14435.1163600524.9.
>Via: SIP/2.0/UDP 193.111.201.74;branch=z9hG4bKfc5a.9a187a95.0.
>Call-ID: d250aa54d4fab3ffa3e96ac7ea73303f.
>CSeq: 183348005 NOTIFY.
>Content-Length: 0.
>.
>
>Thoughts welcome!
>
>Thanks
>peter
>
>  
>