Warning: include(/home/abptech/www/Library/Navigation_Support_Header.lbi) [function.include]: failed to open stream: No such file or directory in /home/vg008web08/16/68/2916816/web/support/faqs/faq_snomphone_LED_explained.html on line 19
Warning: include() [function.include]: Failed opening '/home/abptech/www/Library/Navigation_Support_Header.lbi' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /home/vg008web08/16/68/2916816/web/support/faqs/faq_snomphone_LED_explained.html on line 19
Snom (190/320/360) Phone Function Keys Explained
Being a SIP phone, SIP messages control how these lights work.
First, define a button as "Destination" on the Function Keys page.
Simply put the extension # in the input box.
For the example below, I merely put 211 and the phone filled in
211@abptech.com..... automatically.
Next, turn on "Support Broken Registrar".
Next, turn off "Filter Packets from Registrar".
You can play with these two after you see how it works.
When you save that Function Key, the phone will send out a SUBSCRIBE
message to the proxy.
This is to subscribe to the state of the other end.
The proxy and the other end need to support this.
At this point 2 things can happen depending on the Proxy.
- The proxy forwards the SUBSCRIBE to the far phone (211).
Then the phone needs to remember everybody that has subscribed to
it and send out NOTIFY msgs when it makes/gets a call.
- The proxy keeps the SUBSCRIBE, does not forward it, and when the far
phone is dialed, the proxy sends a NOTIFY on behalf of the phone.
The Snom 4S and Asterisk can do this. See their documentation to see how.
The "<state>early|confirmed</state>" in the NOTIFY msgs below determines
the leds activity.
Use the SIP Trace page on the phone to verify this.
Following are the SIP messages and explainations:
--------------------------------------------------------------------------------
Sent to udp:209.189.239.106:5060 at 19/10/2005 12:26:20:770 (425 bytes):
#This message subscribes to the state of 211
SUBSCRIBE sip:211@abptech.com;user=phone SIP/2.0
Via: SIP/2.0/UDP 216.14.32.61:2051;branch=z9hG4bK-wkwhbwu19wgc;rport
From: <sip:2150@abptech.com>tag=gumvap0ha0
To: <sip:211@abptech.com;user=phone>
Call-ID: 3c2675eaad57-2fjnztudzq25@snom360
CSeq: 1 SUBSCRIBE
Max-Forwards: 70
Contact: <sip:2150@216.14.32.61:2051;line=xjqldyhz>
Event: dialog
Accept: application/dialog-info+xml
Expires: 3600
Content-Length: 0
#You should see a 200 OK in response to the SUBSCRIBE
--------------------------------------------------------------------------------
.... Skipped the 200 OK to the SUBSCRIBE above ....
--------------------------------------------------------------------------------
Received from udp:209.189.239.106:5060 at 19/10/2005 12:35:57:280 (580 bytes):
#This message turns the led OFF
NOTIFY sip:2150@216.14.32.61:2051;line=xjqldyhz SIP/2.0
Via: SIP/2.0/UDP 209.189.239.106:5060;branch=z9hG4bK-44e587400f6d8ef6a8d98ddeecf6edca
From: <sip:211@abptech.com;user=phone>tag=6sam28oefu
To: <sip:2150@abptech.com>tag=gumvap0ha0
Call-ID: 3c2675eaad57-2fjnztudzq25@snom360
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:211@abptech.com"></dialog-info>
--------------------------------------------------------------------------------
Sent to udp:209.189.239.106:5060 at 19/10/2005 12:35:57:290 (283 bytes):
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 209.189.239.106:5060;branch=z9hG4bK-44e587400f6d8ef6a8d98ddeecf6edca
From: <sip:211@abptech.com;user=phone>tag=6sam28oefu
To: <sip:2150@abptech.com>tag=gumvap0ha0
Call-ID: 3c2675eaad57-2fjnztudzq25@snom360
CSeq: 18 NOTIFY
Content-Length: 0
--------------------------------------------------------------------------------
Received from udp:209.189.239.106:5060 at 19/10/2005 12:35:57:430 (930 bytes):
#This message makes the led FLASH
NOTIFY sip:2150@216.14.32.61:2051;line=xjqldyhz SIP/2.0
Via: SIP/2.0/UDP 209.189.239.106:5060;branch=z9hG4bK-a566a0acd02fdaf578d455bc48614953
From: <sip:211@abptech.com;user=phone>tag=6sam28oefu
To: <sip:2150@abptech.com>tag=gumvap0ha0
Call-ID: 3c2675eaad57-2fjnztudzq25@snom360
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:211@abptech.com"><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:211@abptech.com</identity><target +
uri="sip:211@abptech.com"/></local><remote> +
<identity>sip:2112@abptech.com</identity><target +
uri="sip:2112@abptech.com"/></remote></dialog></dialog-info>
--------------------------------------------------------------------------------
Sent to udp:209.189.239.106:5060 at 19/10/2005 12:35:57:450 (283 bytes):
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 209.189.239.106:5060;branch=z9hG4bK-a566a0acd02fdaf578d455bc48614953
From: <sip:211@abptech.com;user=phone>tag=6sam28oefu
To: <sip:2150@abptech.com>tag=gumvap0ha0
Call-ID: 3c2675eaad57-2fjnztudzq25@snom360
CSeq: 19 NOTIFY
Content-Length: 0
--------------------------------------------------------------------------------
Received from udp:209.189.239.106:5060 at 19/10/2005 12:36:00:220 (934 bytes):
#This message makes the led STEADY ON
NOTIFY sip:2150@216.14.32.61:2051;line=xjqldyhz SIP/2.0
Via: SIP/2.0/UDP 209.189.239.106:5060;branch=z9hG4bK-a718cece01b3c69c1d666b3a7a03c366
From: <sip:211@abptech.com;user=phone>tag=6sam28oefu
To: <sip:2150@abptech.com>tag=gumvap0ha0
Call-ID: 3c2675eaad57-2fjnztudzq25@snom360
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:211@abptech.com"><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:211@abptech.com</identity><target uri="sip:211@abptech.com"/> +
</local><remote><identity>sip:2112@abptech.com</identity><target +
uri="sip:2112@abptech.com"/></remote></dialog></dialog-info> +
--------------------------------------------------------------------------------
Sent to udp:209.189.239.106:5060 at 19/10/2005 12:36:00:240 (283 bytes):
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 209.189.239.106:5060;branch=z9hG4bK-a718cece01b3c69c1d666b3a7a03c366
From: <sip:211@abptech.com;user=phone>tag=6sam28oefu
To: <sip:2150@abptech.com>tag=gumvap0ha0
Call-ID: 3c2675eaad57-2fjnztudzq25@snom360
CSeq: 20 NOTIFY
Content-Length: 0
--------------------------------------------------------------------------------
Received from udp:209.189.239.106:5060 at 19/10/2005 12:36:04:050 (580 bytes):
#This message turns the led BACK OFF
NOTIFY sip:2150@216.14.32.61:2051;line=xjqldyhz SIP/2.0
Via: SIP/2.0/UDP 209.189.239.106:5060;branch=z9hG4bK-05f4e06451c0349ccf9fb79c55280932
From: <sip:211@abptech.com;user=phone>tag=6sam28oefu
To: <sip:2150@abptech.com>tag=gumvap0ha0
Call-ID: 3c2675eaad57-2fjnztudzq25@snom360
CSeq: 21 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="21" state="full" entity="sip:211@abptech.com"></dialog-info>
--------------------------------------------------------------------------------
Sent to udp:209.189.239.106:5060 at 19/10/2005 12:36:04:060 (283 bytes):
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 209.189.239.106:5060;branch=z9hG4bK-05f4e06451c0349ccf9fb79c55280932
From: <sip:211@abptech.com;user=phone>tag=6sam28oefu
To: <sip:2150@abptech.com>tag=gumvap0ha0
Call-ID: 3c2675eaad57-2fjnztudzq25@snom360
CSeq: 21 NOTIFY
Content-Length:
--------------------------------------------------------------------------------
#Coming are the messages for a call Pickup
Received from udp:209.189.239.106:5060 at 28/4/2006 16:25:18:920 (950 bytes):
#A notify telling that the other line is ringing.
NOTIFY sip:3871505@216.14.32.61:2054;line=rn245rm9 SIP/2.0
Via: SIP/2.0/UDP 209.189.239.106:5060;branch=z9hG4bK-ef5dc5ddda8fe8c186f4c880e0adef7f
From: <sip:211@abptech.com;user=phone>;tag=xvj99oa4kq
To: <sip:3871505@abptech.com>;tag=zhmg5r5gwq
Call-ID: 3c26700c68fb-fr0tlu8pevvn@snom360-000413230534
CSeq: 10 NOTIFY
Max-Forwards: 70
Event: dialog
Subscription-State: active
Content-Type: application/dialog-info+xml
Content-Length: 501
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="10" state="full" entity="sip:211@abptech.com"> +
<dialog id="dummy" call-id="eb4f000d-b85c2874@192.168.1.172" local-tag="ka6rnwbn36" +
remote-tag="d07b4339bf62df38o0" direction="recipient"><state>early</state> +
<local><identity>sip:211@abptech.com</identity><target +
uri="sip:211@abptech.com"/></local><remote><identity>sip:2112@abptech.com</identity> +
<target uri="sip:2112@abptech.com"/></remote></dialog></dialog-info>
Notice the call-id and local-tag. These will end up in the coming INVITE | Replaces header.
This tells the proxy that my phone is going to take this call.
--------------------------------------------------------------------------------
Sent to udp:209.189.239.106:5060 at 28/4/2006 16:25:18:940 (299 bytes):
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 209.189.239.106:5060;branch=z9hG4bK-ef5dc5ddda8fe8c186f4c880e0adef7f
From: <sip:211@abptech.com;user=phone>;tag=xvj99oa4kq
To: <sip:3871505@abptech.com>;tag=zhmg5r5gwq
Call-ID: 3c26700c68fb-fr0tlu8pevvn@snom360-000413230534
CSeq: 10 NOTIFY
Content-Length: 0
--------------------------------------------------------------------------------
Sent to udp:209.189.239.106:5060 at 28/4/2006 16:25:23:210 (1162 bytes):
#I pressed that key with the flashing light and the phone sent this INVITE.
INVITE sip:2112@abptech.com SIP/2.0
Via: SIP/2.0/UDP 216.14.32.61:2054;branch=z9hG4bK-y7wfiw5j4k4y;rport
From: "Shanon Snom 360" <sip:3871505@abptech.com>;tag=fkbqooxqv2
To: <sip:2112@abptech.com>
Call-ID: 3c269bfdf1b3-elaa4cdv0pdi@snom360-000413230534
CSeq: 1 INVITE
Max-Forwards: 70
Contact: <sip:3871505@abptech.com;gruu=dolzqxk4>;flow-id=1
Replaces: eb4f000d-b85c2874@192.168.1.172;to-tag=d07b4339bf62df38o0;from-tag=ka6rnwbn36
P-Key-Flags: resolution="31x13", keys="4"
User-Agent: snom360/5.5
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
Allow-Events: talk, hold, refer
Supported: timer, 100rel, replaces, callerid
Session-Expires: 3600;refresher=uas
Content-Type: application/sdp
Content-Length: 368
v=0
o=root 1569910172 1569910172 IN IP4 216.14.32.61
s=call
c=IN IP4 216.14.32.61
t=0 0
m=audio 53378 RTP/AVP 0 8 9 2 3 18 4 101
a=rtpmap:0 pcmu/8000
a=rtpmap:8 pcma/8000
a=rtpmap:9 g722/8000
a=rtpmap:2 g726-32/8000
a=rtpmap:3 gsm/8000
a=rtpmap:18 g729/8000
a=rtpmap:4 g723/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv
Written by Shanon Swafford
2005/10/19
Last Modified:
2005/10/19
Warning: include(/home/abptech/www/Library/Navigation_Support_Footer.lbi) [function.include]: failed to open stream: No such file or directory in /home/vg008web08/16/68/2916816/web/support/faqs/faq_snomphone_LED_explained.html on line 336
Warning: include() [function.include]: Failed opening '/home/abptech/www/Library/Navigation_Support_Footer.lbi' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /home/vg008web08/16/68/2916816/web/support/faqs/faq_snomphone_LED_explained.html on line 336