MWI Subscription - Revision history

Horemu at 19:09, 22 April 2011

2011-04-22T19:09:50Z

Horemu: /* Busy Lamp Field and Directed Call Pickup */

2010-09-27T06:41:42Z

‎Busy Lamp Field and Directed Call Pickup

Horemu at 04:29, 24 September 2010

2010-09-24T04:29:22Z

Horemu: /* Use of Dialog Event Package (RFC 4245) */

2010-09-24T04:27:21Z

‎Use of Dialog Event Package (RFC 4245)

Horemu: /* Some remarks about the SIP implementation */

2010-09-24T04:20:12Z

‎Some remarks about the SIP implementation

Horemu at 04:17, 24 September 2010

2010-09-24T04:17:43Z

Horemu at 13:44, 23 September 2010

2010-09-23T13:44:10Z

Horemu at 13:33, 23 September 2010

2010-09-23T13:33:58Z

Horemu at 13:32, 23 September 2010

2010-09-23T13:32:30Z

Horemu: /* Some remarks about the SIP implementation */

2010-09-23T13:30:07Z

‎Some remarks about the SIP implementation

← Older revision		Revision as of 19:09, 22 April 2011
Line 1:		Line 1:
		+	{{Breadcrumb\|0\|0\|{{dev-en}}\|OpenStage}}
	{{OS-FD-Access}}{{FD-Sytematics-Box		{{OS-FD-Access}}{{FD-Sytematics-Box
	\| family = {{FD-Cat\|OpenStage}}		\| family = {{FD-Cat\|OpenStage}}

@@ Line 15: / Line 15: @@
 == Busy Lamp Field and Directed Call Pickup ==
-The Busy Lamp Field feature in its most basic form provides the phone user the ability to monitor the state of other users/devices.  Typically the information provided to the monitored user will allow them to determine whether the monitored user/device is idle, ringing or connected and it may also in some environments be able to indicate call held, line sized and forwarding states.
+The [[OpenStage Busy Lamp Field 40|Busy Lamp Field]] feature in its most basic form provides the phone user the ability to monitor the state of other users/devices.  Typically the information provided to the monitored user will allow them to determine whether the monitored user/device is idle, ringing or connected and it may also in some environments be able to indicate call held, line sized and forwarding states.
-The monitoring user is informed of the state of the remote device by the [[LED]] associated with the BLF FPK and optionally by a alert tone/beep when the remote device receives an incoming call.
+The monitoring user is informed of the state of the remote device by the [[LED]] associated with the BLF [[FPK]] and optionally by a alert tone/beep when the remote device receives an incoming call.
 Additional functionality may be provided by the monitored users device by having an associated FPK and modifying the action performed when pressing the key depending on the current dialog state.  For example when idle pressing the key may initiate a call to the monitored user and when ringing press-ing the key may initiate a pickup of the ringing call. In the HiPath 8000 environment BLF type functionality is provided by the DSS feature.

@@ Line 1: / Line 1: @@
-<accesscontrol>OS-FD</accesscontrol>{{OS-FD-Access}}{{constr|[[User:Horemu|Horemu]] 15:33, 23 September 2010 (CEST)}}{{FD-Sytematics-Box
+{{OS-FD-Access}}{{FD-Sytematics-Box
 | family   = {{FD-Cat|OpenStage}}
 | model    = {{FD-Cat|OpenStage 60}}<br/>{{FD-Cat|OpenStage 80}}

@@ Line 81: / Line 81: @@
 ''The Asterisk Server responds with a '''200 OK'''.''
-SIP/2.0 200 OK
+ SIP/2.0 200 OK
-Via: SIP/2.0/UDP 137.223.238.18:5060;branch=z9hG4bK-1-0;received=137.223.238.18
+ Via: SIP/2.0/UDP 137.223.238.18:5060;branch=z9hG4bK-1-0;received=137.223.238.18
-From: sipp <sip:6000@137.223.238.18:5060>;tag=1
+ From: sipp <sip:6000@137.223.238.18:5060>;tag=1
-To: sut <sip:6001@137.223.238.41:5060>;tag=as065f0599
+ To: sut <sip:6001@137.223.238.41:5060>;tag=as065f0599
-Call-ID: 1-648@137.223.238.18
+ Call-ID: 1-648@137.223.238.18
-CSeq: 1 SUBSCRIBE
+ CSeq: 1 SUBSCRIBE
-User-Agent: Asterisk PBX
+ User-Agent: Asterisk PBX
-Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
+ Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
-Supported: replaces
+ Supported: replaces
-Expires: 3600
+ Expires: 3600
-Contact: <sip:6001@137.223.238.41>;expires=3600
+ Contact: <sip:6001@137.223.238.41>;expires=3600
-Content-Length: 0
+ Content-Length: 0
---- The Asterisk Server generates an initial NOTIFY for the subscription and indicates that extension “6001” is idle (dialog state = terminated).
+ NOTIFY sip:6000@137.223.238.18:5060 SIP/2.0
-NOTIFY sip:6000@137.223.238.18:5060 SIP/2.0
+ <?xml version="1.0"?>
-Via: SIP/2.0/UDP 137.223.238.41:5060;branch=z9hG4bK35d158aa;rport
+ <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" enti-ty="sip:6001@137.223.238.41:5060">
-From: sut <sip:6001@137.223.238.41:5060>;tag=as065f0599
+ <dialog id="6001">
-To: sipp <sip:6000@137.223.238.18:5060>;tag=1
+ <state>'''terminated'''</state>
-Contact: <sip:6001@137.223.238.41>
+ </dialog>
-Call-ID: 1-648@137.223.238.18
+ </dialog-info>
-<?xml version="1.0"?>
+''The phone responds to the '''NOTIFY''' with a '''200OK'''.''
---- The phone responds to the NOTIFY with a 200OK.
+ SIP/2.0 200 OK
-SIP/2.0 200 OK
+''Multiple dialogs reported in a dialog event.''
 A single SIP NOTIFY may contain information relating to multiple dialogs active at the BLF Destination. For example when the BLF destination receives a call waiting call. In this case the phone must parse all dialogs to determine the state to be reported. The state with the highest priority is used to set the state of the BLF LED and any associated popup.
@@ Line 135: / Line 134: @@
 The priority is as follows:
-Priority	Dialog State	Call State at BLF Destination	BLF LED State
+{|
-.	State = Early,direction=recipient.	Incoming call alerting at destination.	Flashing (Incoming Call)
+! Priority
-a.	State = Early, direc-tion=originator	Outgoing call.	On (Busy)
+! Dialog State
-b.	State = Confirmed	Established Call (Including held)	On (Busy)
+! Call State at BLF Destination
-.	State = Terminated	Call has been cleared	Off (Idle).
+! BLF LED State
-Picking-Up a call ringing a BLF destination.
+=== Picking-Up a call ringing a BLF destination. ===
 To pickup a call ringing a BLF destination the procedure followed by the Picking-up OpenStage phone depends on configuration and on the amount of information received in the dialog event as follows.
-Picking-Up using a feature access code.
+=== Picking-Up using a feature access code ===
 If a feature access code is configured for BLF Pickup then the OpenStage phone generates an INVITE using the feature access code (FAC) and the BLF Destination in the Request-URI of the INVITE request. The content of the INVITE would be as followed (Note – Only the significant headers are shown).
-INVITE sip:<FAC><BLF Destination>@SIPServerDomain SIP/2.0
+ INVITE sip:'''<FAC><BLF Destination>'''@SIPServerDomain SIP/2.0
-From: <sip:6000>;tag=drfgdfdg
+ From: <sip:6000>;tag=drfgdfdg
-To: sip:<FAC><BLF Destination>
+ To: sip:'''<FAC><BLF Destination>'''
-Call-ID: gshgshjgsgshjgshjg
+ Call-ID: gshgshjgsgshjgshjg
-CSeq: 1 INVITE
+ CSeq: 1 INVITE
-Accept: application/sdp
+ Accept: application/sdp
-Content-Type: application/sdp
+ Content-Type: application/sdp
-Content-Length: xxx
+ Content-Length: xxx
-…
+ …
 This method is used whenever a feature access code is configured for BLF Pickup.
-Picking-Up using the SIP Replaces Header (RFC 3891).
+=== Picking-Up using the SIP Replaces Header (RFC 3891) ===
 If no BLF Pickup feature access code is configured and the dialog event received from the SIP Server contains at a minumum the “call-id” and the “local” and “remote” elements then the OpenStage phone shall  folllow the Picking-Up UA procedures as specified in the OSCAR SIP Directed Pickup Specification. This involves generating a SIP a SIP INVITE with Replaces header.

@@ Line 60: / Line 60: @@
 This section provides some guidance on the SIP protocol aspects of susbcribing to the SIP Server for dialog event information and for picking up calls ringing the BLF Destination.
-Use of Dialog Event Package (RFC 4245)
+=== Use of Dialog Event Package (RFC 4245) ===
 On initialisation the OpenStage phone will initiate a subscription to the dialog event package for each FPK configured for the BLF feature. An example of this subscription and a subsequent notify received from an Asterisk server is given below.
---- A SIP SUBSCRIBE request is generated for a BLF key configured to monitor extension “6001”.
+''A SIP SUBSCRIBE request is generated for a BLF key configured to monitor extension '''6001'''.''
-SUBSCRIBE sip:6001@137.223.238.41:5060 SIP/2.0
+ SUBSCRIBE sip:6001@137.223.238.41:5060 SIP/2.0
-Via: SIP/2.0/UDP 137.223.238.18:5060;branch=z9hG4bK-1-0
+ Via: SIP/2.0/UDP 137.223.238.18:5060;branch=z9hG4bK-1-0
-From: sipp <sip:6000@137.223.238.18:5060>;tag=1
+ From: sipp <sip:6000@137.223.238.18:5060>;tag=1
-To: sut <sip:6001@137.223.238.41:5060>
+ To: sut <sip:6001@137.223.238.41:5060>
-Call-ID: 1-648@137.223.238.18
+ Call-ID: 1-648@137.223.238.18
-CSeq: 1 SUBSCRIBE
+ CSeq: 1 SUBSCRIBE
-Contact: sip:6000@137.223.238.18:5060
+ Contact: sip:6000@137.223.238.18:5060
-Max-Forwards: 70
+ Max-Forwards: 70
-Event: dialog
+ Event: dialog
-Accept: application/dialog-info+xml
+ Accept: application/dialog-info+xml
-Expires: 3600
+ Expires: 3600
-Content-Length: 0
+ Content-Length: 0
---- The Asterisk Server responds with a 200 OK.
+''The Asterisk Server responds with a '''200 OK'''.''
 SIP/2.0 200 OK

@@ Line 11: / Line 11: @@
 : Administrator Pages -> System -> Features -> Services -> Message waiting server address
-[[File:MWI-Subscription-1.png|400px]]
+[[File:MWI-Subscription-1.png|250px]]
 == Busy Lamp Field and Directed Call Pickup ==

@@ Line 11: / Line 11: @@
 : Administrator Pages -> System -> Features -> Services -> Message waiting server address
-[[File:MWI-Subscription-1|400px]]
+[[File:MWI-Subscription-1.png|400px]]
 == Busy Lamp Field and Directed Call Pickup ==
@@ Line 32: / Line 32: @@
 : System -> Features -> Services
-[[File:MWI-Subscription-2|400px]]
+[[File:MWI-Subscription-2.png|400px]]
 === BLF Key ===
@@ Line 39: / Line 39: @@
 : System -> Features -> Program keys
-[[File:MWI-Subscription-3|400px]]
+[[File:MWI-Subscription-3.png|400px]]
 * '''Key Label''': Name of the FPK displayed on the screen
@@ Line 51: / Line 51: @@
 : System -> Features -> Configuration
-[[File:MWI-Subscription-4|400px]]
+[[File:MWI-Subscription-4.png|400px]]
 * '''BLF alerting''': ''Beep'' or ''Ring''

← Older revision		Revision as of 13:30, 23 September 2010
Line 58:		Line 58:
	== Some remarks about the SIP implementation ==		== Some remarks about the SIP implementation ==

−	-----	+	This section provides some guidance on the SIP protocol aspects of susbcribing to the SIP Server for dialog event information and for picking up calls ringing the BLF Destination.
		+
		+	Use of Dialog Event Package (RFC 4245)
		+
		+	On initialisation the OpenStage phone will initiate a subscription to the dialog event package for each FPK configured for the BLF feature. An example of this subscription and a subsequent notify received from an Asterisk server is given below.
		+
		+	--- A SIP SUBSCRIBE request is generated for a BLF key configured to monitor extension “6001”.
		+
		+	SUBSCRIBE sip:6001@137.223.238.41:5060 SIP/2.0
		+	Via: SIP/2.0/UDP 137.223.238.18:5060;branch=z9hG4bK-1-0
		+	From: sipp <sip:6000@137.223.238.18:5060>;tag=1
		+	To: sut <sip:6001@137.223.238.41:5060>
		+	Call-ID: 1-648@137.223.238.18
		+	CSeq: 1 SUBSCRIBE
		+	Contact: sip:6000@137.223.238.18:5060
		+	Max-Forwards: 70
		+	Event: dialog
		+	Accept: application/dialog-info+xml
		+	Expires: 3600
		+	Content-Length: 0
		+
		+	--- The Asterisk Server responds with a 200 OK.
		+
		+	SIP/2.0 200 OK
		+	Via: SIP/2.0/UDP 137.223.238.18:5060;branch=z9hG4bK-1-0;received=137.223.238.18
		+	From: sipp <sip:6000@137.223.238.18:5060>;tag=1
		+	To: sut <sip:6001@137.223.238.41:5060>;tag=as065f0599
		+	Call-ID: 1-648@137.223.238.18
		+	CSeq: 1 SUBSCRIBE
		+	User-Agent: Asterisk PBX
		+	Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
		+	Supported: replaces
		+	Expires: 3600
		+	Contact: <sip:6001@137.223.238.41>;expires=3600
		+	Content-Length: 0
		+
		+
		+	--- The Asterisk Server generates an initial NOTIFY for the subscription and indicates that extension “6001” is idle (dialog state = terminated).
		+
		+	NOTIFY sip:6000@137.223.238.18:5060 SIP/2.0
		+	Via: SIP/2.0/UDP 137.223.238.41:5060;branch=z9hG4bK35d158aa;rport
		+	From: sut <sip:6001@137.223.238.41:5060>;tag=as065f0599
		+	To: sipp <sip:6000@137.223.238.18:5060>;tag=1
		+	Contact: <sip:6001@137.223.238.41>
		+	Call-ID: 1-648@137.223.238.18
		+	CSeq: 102 NOTIFY
		+	User-Agent: Asterisk PBX
		+	Max-Forwards: 70
		+	Event: dialog
		+	Content-Type: application/dialog-info+xml
		+	Subscription-State: active
		+	Content-Length: 212
		+
		+	<?xml version="1.0"?>
		+	<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" enti-ty="sip:6001@137.223.238.41:5060">
		+	<dialog id="6001">
		+	<state>terminated</state>
		+	</dialog>
		+	</dialog-info>
		+
		+	--- The phone responds to the NOTIFY with a 200OK.
		+
		+	SIP/2.0 200 OK
		+	Via: SIP/2.0/UDP 137.223.238.41:5060;branch=z9hG4bK35d158aa;rport
		+	From: sut <sip:6001@137.223.238.41:5060>;tag=as065f0599
		+	To: sipp <sip:6000@137.223.238.18:5060>;tag=1
		+	Call-ID: 1-648@137.223.238.18
		+	CSeq: 102 NOTIFY
		+	Contact: <sip:137.223.238.18:5060;transport=UDP>
		+	Content-Length: 0
		+
		+	Multiple dialogs reported in a dialog event.
		+
		+	A single SIP NOTIFY may contain information relating to multiple dialogs active at the BLF Destination. For example when the BLF destination receives a call waiting call. In this case the phone must parse all dialogs to determine the state to be reported. The state with the highest priority is used to set the state of the BLF LED and any associated popup.
		+
		+	The priority is as follows:
		+
		+	Priority Dialog State Call State at BLF Destination BLF LED State
		+	1. State = Early,direction=recipient. Incoming call alerting at destination. Flashing (Incoming Call)
		+	2a. State = Early, direc-tion=originator Outgoing call. On (Busy)
		+	2b. State = Confirmed Established Call (Including held) On (Busy)
		+	3. State = Terminated Call has been cleared Off (Idle).
		+
		+	Picking-Up a call ringing a BLF destination.
		+
		+	To pickup a call ringing a BLF destination the procedure followed by the Picking-up OpenStage phone depends on configuration and on the amount of information received in the dialog event as follows.
		+
		+	Picking-Up using a feature access code.
		+
		+	If a feature access code is configured for BLF Pickup then the OpenStage phone generates an INVITE using the feature access code (FAC) and the BLF Destination in the Request-URI of the INVITE request. The content of the INVITE would be as followed (Note – Only the significant headers are shown).
		+
		+	INVITE sip:<FAC><BLF Destination>@SIPServerDomain SIP/2.0
		+	From: <sip:6000>;tag=drfgdfdg
		+	To: sip:<FAC><BLF Destination>
		+	Call-ID: gshgshjgsgshjgshjg
		+	CSeq: 1 INVITE
		+	Accept: application/sdp
		+	Content-Type: application/sdp
		+	Content-Length: xxx
		+	…
		+
		+	This method is used whenever a feature access code is configured for BLF Pickup.
		+
		+	Picking-Up using the SIP Replaces Header (RFC 3891).
		+
		+	If no BLF Pickup feature access code is configured and the dialog event received from the SIP Server contains at a minumum the “call-id” and the “local” and “remote” elements then the OpenStage phone shall folllow the Picking-Up UA procedures as specified in the OSCAR SIP Directed Pickup Specification. This involves generating a SIP a SIP INVITE with Replaces header.
		+
		+	Picking-Up using an INVITE to the remote target-URI.
		+
		+	If no BLF Pickup feature access code is configured and the dialog event contains the “local” and “re-mote” elements but no “call-id” then the OpenStage phone using the same procedures as defined in 0 but without including a Replaces header in the INVITE request.
		+
		+	This method relies on the SIP Server setting the remote target-uri to be something that it will recognise as a call pickup request.