15 Nov
2006
15 Nov
'06
6:07 p.m.
Peter,
Event:dialog is not used for presence, it is used to retrieve
information about the status of a given dialog. It can be used to
provide services such as calling back whenever the user becomes
available again.
That's the reason openser PRESENCE implementation does not "work" with
this type of Event, just with events as presence and winfo.presence.
So either you treat SIMPLE-related messages with dialog in the Event
header as "normal" requests and forwards them to the end-points
expecting that they implement it or you will just get Bad Event
replies.
Samuel.
2006/11/15, Peter Gradwell <peter(a)gradwell.com>om>:
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:1000305@lon-sip-1.gradwell.net;user=phone SIP/2.0.
To: <sip:1000305@lon-sip-1.gradwell.net;user=phone>.
From: <sip:1000305@lon-sip-1.gradwell.net>;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:CNOgG7HbGwkzlYrxgc7RjID5rBqkrZFREwe644KJ40.@193.84.87.60: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:1000305@lon-sip-1.gradwell.net;user=phone>;tag=20c56ba31bbe85b9bc9d
0e09f876aff7.24f5.
From: <sip:1000305@lon-sip-1.gradwell.net>;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:1000305@lon-sip-1.gradwell.net;user=phone
out_uri=sip:1000305@lon-sip-1.gradwell.net 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:CNOgG7HbGwkzlYrxgc7RjID5rBqkrZFREwe644KJ40.@193.84.87.60:5082;line=2
7nd4hcq SIP/2.0.
Via: SIP/2.0/UDP 193.111.201.74;branch=z9hG4bKfc5a.9a187a95.0.
To: sip:1000301@lon-sip-1.gradwell.net;tag=9d6ee568.
From: sip:1000301@lon-sip-1.gradwell.net;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:1000301@lon-sip-1.gradwell.net>.
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:1000301@lon-sip-1.gradwell.net>;tag=9d6ee568.
From: <sip:1000301@lon-sip-1.gradwell.net>;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
--
peter gradwell. gradwell dot com Ltd. http://www.gradwell.com/
-- engineering & hosting services for email, web and voip --
-- http://www.peter.me.uk/ -- http://www.voip.org.uk/ --
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users