Fix Forwarding Key to send URL to Server - Revision history

Horemu at 19:06, 22 April 2011

2011-04-22T19:06:01Z

Harald.saller: /* LED control */

2010-09-23T08:37:23Z

‎LED control

Harald.saller: /* LED control */

2010-09-23T08:36:48Z

‎LED control

Harald.saller: /* LED control */

2010-09-23T08:35:51Z

‎LED control

Harald.saller: /* Current Operation */

2010-09-23T08:33:52Z

‎Current Operation

Horemu: /* Accessing the Call Forwarding functionality */

2010-09-22T07:27:50Z

‎Accessing the Call Forwarding functionality

Horemu: /* Accessing the Call Forwarding functionality */

2010-09-22T07:26:59Z

‎Accessing the Call Forwarding functionality

Horemu: /* Accessing the Call Forwarding functionality */

2010-09-21T14:05:48Z

‎Accessing the Call Forwarding functionality

Horemu: /* Call forward toggle functionality using external server */

2010-09-21T14:04:53Z

‎Call forward toggle functionality using external server

Horemu at 13:57, 21 September 2010

2010-09-21T13:57:17Z

← Older revision		Revision as of 19:06, 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 86: / Line 86: @@
 LED control: 100
-An
   SUBSCRIBE sip:100@192.168.010
 is sent to 192.168.0.10 after configuration and any startup.
@@ Line 92: / Line 92: @@
 LED control: Allice@192.168.6.100
-An
   SUBSCRIBE sip: Allice@192.168.6.100
 is sent to 192.168.6.100 after configuration and any startup.

@@ Line 80: / Line 80: @@
 The LED control is done via Dialog event package (RFC 4235), which is the standard Asterisk implementation. The phone will automatically add the configured SIP proxy, if no Domain is given in the URL.
-The phone will SUBSRIBE to the given URL. The LED can be controlled over subsequent NOTIFYs.
+The phone will SUBSCRIBE to the given URL. The LED can be controlled over subsequent NOTIFYs.
 '''Examples'''

@@ Line 78: / Line 78: @@
 == LED control ==
-The LED control is done via Dialog event package (RFC 4235), which is the standard Asterisk implemen-tation. The phone will automatically add the configured SIP proxy, if no Domain is given in the URL.
+The LED control is done via Dialog event package (RFC 4235), which is the standard Asterisk implementation. The phone will automatically add the configured SIP proxy, if no Domain is given in the URL.
 The phone will SUBSRIBE to the given URL. The LED can be controlled over subsequent NOTIFYs.

@@ Line 12: / Line 12: @@
 At present, pressing the fixed forwarding key on a SIP OpenStage phone controls its built-in forwarding functionality. A popup is displayed, allowing the user to both toggle forwarding and edit forwarding destinations. Forwarding state is reflected by a stylised icon and forwarding destination on the Call-View idle screen. The key has two modes of operation:
 * Phone based forwarding: Forwarding is performed by the OpenStage Phone. When the user configures forwarding types and destinations, they are stored on the phone. This is the mode of operation when the SIP ‘Server Features’ configuration parameter is set to '''No'''.
-* Server based forwarding: Forwarding is performed by the SIP Server. When the user configures forwarding types and destinations, a uaCSTA request is sent to the OpenScape Voice de-tailing the new settings. This is the mode of operation when the SIP ‘Server Features’ configuration parameter is set to '''Yes'''.
+* Server based forwarding: Forwarding is performed by the SIP Server. When the user configures forwarding types and destinations, a uaCSTA request is sent to the OpenScape Voice detailing the new settings. This is the mode of operation when the SIP ‘Server Features’ configuration parameter is set to '''Yes'''.
 This '''current operation''' when the fixed forwarding key is pressed will be packaged as a function definition named '''Built-in forwarding'''. This will be the default function allocated to the fixed forwarding key, and will only be programmable against this key.

@@ Line 41: / Line 41: @@
 Configuration of the above functionality against the fixed forwarding key will be realised by a new key function and operation parameter related to the key. Configuration of these parameters will be limited to administrators using the [[DLS]] and [[WBM]]. There will be no indication to a user via any mechanism that operation of the fixed forwarding key is configurable.
-[[File:FixForwardingKeytosendURLtoServer-1.png|thumb|450px|left|Fixed Key Setting for Forwarding Key]]<br clear="left"/>
+[[File:FixForwardingKeytosendURLtoServer-1.png|thumb|400px|left|Fixed Key Setting for Forwarding Key]]<br clear="left"/>
 * '''Built-in Forwarding''': The forwarding key works as known in all previous software versions
 * '''Server Feature''': The forwarding key triggers an external SIP Server for call forwarding
-[[File:FixForwardingKeytosendURLtoServer-2.png|thumb|450px|left|Fixed forwarding key settings]]<br clear="left"/>
+[[File:FixForwardingKeytosendURLtoServer-2.png|thumb|400px|left|Fixed forwarding key settings]]<br clear="left"/>
 == Feature Code ==

← Older revision		Revision as of 07:26, 22 September 2010
Line 41:		Line 41:
	Configuration of the above functionality against the fixed forwarding key will be realised by a new key function and operation parameter related to the key. Configuration of these parameters will be limited to administrators using the [[DLS]] and [[WBM]]. There will be no indication to a user via any mechanism that operation of the fixed forwarding key is configurable.		Configuration of the above functionality against the fixed forwarding key will be realised by a new key function and operation parameter related to the key. Configuration of these parameters will be limited to administrators using the [[DLS]] and [[WBM]]. There will be no indication to a user via any mechanism that operation of the fixed forwarding key is configurable.

−	--- ~~ToDo IMG --~~-	+	[[File:FixForwardingKeytosendURLtoServer-1.png\|thumb\|450px\|left\|Fixed Key Setting for Forwarding Key]]<br clear="left"/>
		+
		+	* '''Built-in Forwarding''': The forwarding key works as known in all previous software versions
		+	* '''Server Feature''': The forwarding key triggers an external SIP Server for call forwarding
		+
		+	[[File:FixForwardingKeytosendURLtoServer-2.png\|thumb\|450px\|left\|Fixed forwarding key settings]]<br clear="left"/>
		+
		+	== Feature Code ==
		+
		+	This code is sent in an '''INVITE''' to the given destination, if the phone is idle. The phone will automatically add the configured '''SIP''' proxy, if no Domain is given in the URL.
		+
		+	'''Examples'''
		+
		+	Feature code: 100
		+
		+	An
		+	INVITE sip:100@192.168.0.10
		+	is sent to 192.168.0.10, if the key is pressed and the phone is idle
		+
		+	Feature code: Allice@192.168.6.100
		+
		+	An
		+	INVITE sip: Alice@192.168.6.100
		+	is sent to 192.168.6.100, if the key is pressed.and the phone is idle.
		+
		+	== DTMF Digits ==
		+
		+	These digits are sent, when the phone is in an call state. The digits are sent inband or out of band. It depends on the configuration.
		+
		+	'''Example'''
		+
		+	DTMF digits: 1234#
		+
		+	The DTMF digits are sent, if the key is pressed and the phone is in an call.
		+
		+	== LED control ==
		+
		+	The LED control is done via Dialog event package (RFC 4235), which is the standard Asterisk implemen-tation. The phone will automatically add the configured SIP proxy, if no Domain is given in the URL.
		+
		+	The phone will SUBSRIBE to the given URL. The LED can be controlled over subsequent NOTIFYs.
		+
		+	'''Examples'''
		+
		+	LED control: 100
		+
		+	An
		+	SUBSCRIBE sip:100@192.168.010
		+	is sent to 192.168.0.10 after configuration and any startup.
		+
		+	LED control: Allice@192.168.6.100
		+
		+	An
		+	SUBSCRIBE sip: Allice@192.168.6.100
		+	is sent to 192.168.6.100 after configuration and any startup.

← Older revision		Revision as of 14:05, 21 September 2010
Line 41:		Line 41:
	Configuration of the above functionality against the fixed forwarding key will be realised by a new key function and operation parameter related to the key. Configuration of these parameters will be limited to administrators using the [[DLS]] and [[WBM]]. There will be no indication to a user via any mechanism that operation of the fixed forwarding key is configurable.		Configuration of the above functionality against the fixed forwarding key will be realised by a new key function and operation parameter related to the key. Configuration of these parameters will be limited to administrators using the [[DLS]] and [[WBM]]. There will be no indication to a user via any mechanism that operation of the fixed forwarding key is configurable.

−	--- IMG ---	+	--- ToDo IMG ---

← Older revision		Revision as of 14:04, 21 September 2010
Line 25:		Line 25:

	Control of the fixed forwarding key LED will be relinquished to the SIP server via a subscription related to the key. The LED state as controlled by the server will be reflected by the visibility of the stylised forwarding icon on the phone’s idle CallView screen. The call forwarding destination will not be displayed.		Control of the fixed forwarding key LED will be relinquished to the SIP server via a subscription related to the key. The LED state as controlled by the server will be reflected by the visibility of the stylised forwarding icon on the phone’s idle CallView screen. The call forwarding destination will not be displayed.
		+
		+	== Call forward functionality using external server, but no toggle functionality assumed ==
		+
		+	Similarly to above, in this configuration the fixed forwarding key will be programmed as function '''Server Feature'''. The Key functionality will be set to '''Unspecified Call Forwarding'''. No assumption is made that the key will be used to toggle call forwarding. It is still considered, however, that the functionality of the key will be generally call forwarding related, therefore '''Built-in forwarding''' will be disabled, and [[LED]] control will be relinquished to the SIP server.
		+
		+	As no toggle functionality is assumed, no prompt to '''Toggle call forwarding''' will be shown. Instead, the FAC or DTMF sequence will be immediately sent to the external server, as defined in the FD for the '''Server Feature''' functionality. In line with this, no stylised forwarding icon will be displayed on the idle CallView screen.
		+
		+	== No functionality assumed ==
		+
		+	In this configuration, the forwarding key will be programmed as function '''Server Feature''', and the Key
		+	Functionality will be set to '''Unspecified'''. No assumptions will be made as to the operation of the key. Built-in forwarding will not be disabled. Pressing the key will cause the FAC to be sent immediately to the SIP server, and there will be no UI response either via displaying the call forwarding icon or changing the state of forwarding LEDs. The SIP Server will still have control of the state of the fixed forwarding key LED.
		+
		+	== Accessing the Call Forwarding functionality ==
		+
		+	Configuration of the above functionality against the fixed forwarding key will be realised by a new key function and operation parameter related to the key. Configuration of these parameters will be limited to administrators using the [[DLS]] and [[WBM]]. There will be no indication to a user via any mechanism that operation of the fixed forwarding key is configurable.
		+
		+	--- IMG ---

@@ Line 6: / Line 6: @@
 }}
-This feature description describes the requirement that [[SIP]] OpenStage phones with a fixed forwarding key available should be capable of having the key programmed as alternative function to the default built-in forwarding. The primary requirement is for the key to be programmable with a function capa-ble of sending a feature access code to a remote SIP server in order to toggle forwarding; functionality that is currently available on FPKs as the '''Server Feature''' key function.
+This feature description describes the requirement that [[SIP]] OpenStage phones with a fixed forwarding key available should be capable of having the key programmed as alternative function to the default built-in forwarding. The primary requirement is for the key to be programmable with a function capable of sending a feature access code to a remote SIP server in order to toggle forwarding; functionality that is currently available on FPKs as the '''Server Feature''' key function.
 == Current Operation ==