TB30s SIP Administrator Guide v1.3 Page 94 of 259
Accept: application/dialog-info+xml
Expires: 3600
Content-Length: 0
--------------------------------------------------------------------------------
The UA 2200@lan should receive the 200 OK to the SUBSCRIBE above ....
---------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Received from udp:10.0.0.5:5060 at 19/10/2005 12:35:57:280 (580 bytes):
#This turns the LED corresponding to 2205 OFF at 2200@lan
NOTIFY sip:2200@10.0.0.1:2051;line=xjqldyhz SIP/2.0
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK-44e587400f6d8ef6a8d98ddeecf6edca
From: <sip:2205@lan.net;user=phone>tag=6sam28oefu
To: <sip:2200@lan.net>tag=gumvap0ha0
Call-ID: 3c2675eaad57-2fjnztudzq25@TB30
CSeq: 18 NOTIFY
Max-Forwards: 70
Event: dialog
Subscription-State: active
Content-Type: application/dialog-info+xml
Content-Length: 150
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="18" state="full"
entity="sip:2205@lan.net"></dialog-info>
--------------------------------------------------------------------------------
.... The UA 2200@lan should send the 200 OK to the NOTIFY above ....
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Received from udp:10.0.0.5:5060 at 19/10/2005 12:35:57:430 (930 bytes):
#This make the led FLASH
NOTIFY sip:2200@10.0.0.1:2051;line=xjqldyhz SIP/2.0
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK-a566a0acd02fdaf578d455bc48614953
Page 6 de 9
From: <sip:2205@lan.net;user=phone>tag=6sam28oefu
To: <sip:2200@lan.net>tag=gumvap0ha0
Call-ID: 3c2675eaad57-2fjnztudzq25@TB30
CSeq: 19 NOTIFY
Max-Forwards: 70
Event: dialog
Subscription-State: active
Content-Type: application/dialog-info+xml
Content-Length: 500
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="19" state="full" +
entity="sip:2205@lan.net"><dialog id="dummy" call-id="feb21493- d84a9bd6@192.168.0.113" +
local-tag="6yln5cag4d" remote-tag="fe9c856f35980aao0" +
direction="recipient"><state>early</state> +
<local><identity>sip:2205@lan.net</identity><target +
uri="sip:2205@lan.net"/></local><remote> +
<identity>sip:22052@lan.net</identity><target +
uri="sip:22052@lan.net"/></remote></dialog></dialog-info>
--------------------------------------------------------------------------------
.... The UA 2200@lan should send the 200 OK to the NOTIFY above ....
---------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Received from udp:10.0.0.5:5060 at 19/10/2005 12:36:00:220 (934 bytes):
#This makes the led STEADY ON
NOTIFY sip:2200@10.0.0.1:2051;line=xjqldyhz SIP/2.0
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bK-a718cece01b3c69c1d666b3a7a03c366
From: <sip:2205@lan.net;user=phone>tag=6sam28oefu
To: <sip:2200@lan.net>tag=gumvap0ha0
Call-ID: 3c2675eaad57-2fjnztudzq25@TB30
CSeq: 20 NOTIFY
Max-Forwards: 70
Event: dialog
Subscription-State: active
Content-Type: application/dialog-info+xml
Content-Length: 504
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="20" state="full" +
entity="sip:2205@lan.net"><dialog id="dummy" call-id="feb21493-
d84a9bd6@192.168.0.113" +
local-tag="6yln5cag4d" remote-tag="fe9c856f35980aao0" +
direction="recipient"><state>confirmed</state> +
<local><identity>sip:2205@lan.net</identity><target uri="sip:2205@lan.net"/> +