Action URLs are basically HTTP GET Requests that allow the phone to interact with web server applications. They can be used to send various data from the phone to a web server, like the customized settings stored on the phone; passwords are replaced by empty strings. Action URLs can be triggered by predefined events ("Action URL Settings" page of the phone's web interface) or manually by a pressing a function key that has been programmed to trigger an action.

With this setting, your phone will automatically accept incoming calls when it is idle. If you leave the text field empty, incoming calls for all configured identities will be accepted; if you enter the number of an identity in the text field, only calls to that identity will be accepted automatically (i.e., 1 for Identity 1, 2 for Identity 2 etc.).

This function key allows showing the status (idle, ringing, held call, busy) of another extension on the key's LED. By pressing the key, it may also be possible to pick up calls ringing on the extension, to dial the extension when the phone is idle, and to transfer an incoming call ringing on your own extension. These functionalities depend on your PBX; for more information, please check snom's interoperability page and the PBX manual.
With Asterisk, generally use this feature rather than extension.

This is a function key that is connected to your PBX to perform a task specified in the buttons document. For more information, see the detailed feature description at http://wiki.gigasetpro/Features/LED_Remote_Control.

This function key can be used by call agents to perform one of three different functions, depending on the value entered in the "Number" text field:

• Logging onto and off the system.
  Text field entry: F_CALL_AGENT_LOGGEDIN.
  
  
• Signalìng readyness to accept calls. For this function to work, the agent must be logged in.
  Text field entry: F_CALL_AGENT_READY.
  
  
• Announcing that they are working after a call. For this function to work, the agent must be logged in.
  Text field entry: F_CALL_AGENT_WORKINGAFTERCALL.

This function key can be used for PBX-based conferences and for local conferences on the phone itself.

• PBX-based conferences. When a conference room or conference account has been created on the server for an individual identity, you can dedicate a function key to calling and monitoring the conference room. Select the identity and the "Conference server" function from the respective drop-down menus and enter the SIP URI of the conference room in the "Number" text field. For information on how to use this key with your particular PBX, please check the PBX manual.
  
  
• Phone-based conferences. If there is no SIP URI in the text field, pressing the function key will initiate a phone-based conference with all held calls and any active call.

This function allows the specification of arbitrary key sequences (allowed digits: "0-9", "*", "#", "A-D" and flash: "!") which will be sent via DTMF when this key is pressed during an active call.

This function key allows showing the status (idle, ringing, held call, busy) of another extension on the key's LED. By pressing the key, it may also be possible to pick up calls ringing on the extension, to dial the extension when the phone is idle, and to transfer an incoming call ringing on your own extension. These functionalities depend on your PBX; for more information, please check interoperability page and the PBX manual.
With Asterisk, generally use BLF rather than this function.

All incoming calls will be forwarded to the number (extension or external phone number) specified under "Number". The key is used to turn forwarding of all calls on and off; the red LED lights up when the function is turned on.

Pressing a function key mapped with "Intercom" will establish a two-way connection to the extension specified in the "Number" text field; that extension must have enabled intercom reception on its web interface (Advanced Settings > Behavior tab > Phone Behavior > Intercom Policy "only in idle" or "always").

"Intercom Policy" settings on the phone being called via intercom:

Always: The intercom call will connect to the called phone automatically; if the called phone is in a call, that call will be placed on hold.

Only in idle: The intercom call will connect to the called phone automatically if the called phone is idle. If it is in a call, the incoming intercom call will be announced as call waiting.

Off: Pressing the intercom key will call the extension specified in the "Number" text field where it will be treated like any other incoming call, i.e., ring, be forwarded, etc.

This function key can be used for regular calls to an extension that is reached via an IVR or auto attendant and a number of voice prompts where the caller has to make a selection by pressing a key after or during the prompt. If you know which keys need to be pressed in which order in order to reach the desired extension, the entire process can be automated and considerably speeded up.

The syntax for the "Number" text field entry is <phone_number>;dtmf=<n>,<n>, etc. The angle brackets <>including their content are placeholders for the variables that you must replace by the actual characters. The comma represents a pause of one second, and n represents any number key on the alphanumeric keypad.

Example: The number to dial is (917) 555-3814. When the connection has been established, the caller will hear three prompts. After the first prompt, he must press key 1; after the second prompt, he must press 3; and after the third prompt he must press 1 to reach the desired extension. The entry in the "Number" text field must look like this: 9175553814;dtmf=1,3,1.

Usage: When the phone is in idle mode, press the key to dial the number. As soon as the connection has been established, the phone will automatically send the DTMF tones associated with the alphanumeric keys 1, 3, and 1 with a one-second pause between them.

(If the function type "IVR" doesn't work on individual phones, try "Speed dial" with the above description.)

 When this key type is selected, a drop-down menu opens under "Number". For the available selections, see the following section "Key Events".

Default setting for all freely programmable function keys. Incoming calls will go to the first free "line" key, and outgoing calls will use the first free line key.

Line keys can be used to make outgoing calls with the identity selected from a particular key's "Context" menu and to have incoming calls for that identity going to that particular function key. If the key is busy, the incoming call will go to the first free line key.

This function key enables the phone to send multicast streams to IP multicast group addresses. The multicast IP address and port are entered in the "Number" text field in the format <multicast IP address>:<port> (e.g., 239.255.255.245:5555). The angle brackets <>including their content are placeholders for the variables that you must replace by the actual characters.

Please note: This key is for sending multicast streams. To allow reception of multicast streams, multicast support must be enabled on the phone's web interface, Advanced settings > SIP/RTP tab > Multicast by setting Multicast Support to "on". You must also enter the IP addresses of the multicasts you wish to receive in ascending order of priority, 10 being the highest. In case of simultaneous multicasts, the one with the highest priority at any given time will override the others.

If a park orbit has been set up on the server, a function key mapped with the Park Orbit functionality can EITHER serve to park calls on the park orbit OR to park as well as retrieve calls, depending on the type of server used. Select the server type on the Configuration Identity page of the context identity, SIP tab, from the "Server Type Support" drop-down menu. Enter the "phone number" of the Park Orbit and/or the park position in the text field of "Number", for example orbit1@my.proxy.com or 700@my.proxy.com etc.

If supported by your PBX, the LED of this function key will reflect the presence status (ringing, busy, available, etc.) of the extension specified in the "Number" text field. The function key can also be used to dial the extension, usually when the destination signals availability.

Pressing the function key mapped with "Push2Talk" will establish a two-way connection to the extension specified in the "Number" text field for as long as the key is pressed; that extension must have enabled intercom reception on its web interface (Advanced Settings > Behavior tab > Phone Behavior > Intercom Policy "only in idle" or "always").

• On 870 phones, this key type will establish an Intercom connection.
• On 820/821 phones, this key type is only available on keys P2 and P3.
• On 760 phones, this key type is not available on key P4.

Bridged lines (Bridged Line Appearance (BLA)) are shared by two or more users; when one of them is using the line, the others are blocked from using it. This key type makes it possible to monitor whether a shared line is busy (the LED is lit) or not (the LED is off).

The URI of the shared line is set under "Number".

Besides using the "Speed Dial" page on the web interface to program speed dial numbers, you can also put the functionality on the freely programmable function keys with LEDs to be able to speed dial frequently used and/or long numbers without having to enter the complete phone number.

Enter one phone number with any required prefixes (area code, country code, operator/auto attendant, etc.) in the "Number" text field for any given freely programmable function key with LEDs. Example: 0019175557813.

Or enter a partial phone number (country, area code etc.) and complete the number on the dialog screen. In this case, enter the partial number, followed by a semicolon and "number=incomplete" in the text field. Example: 001917555; number=incomplete.

Making SIP calls without audiovisual indication on the phone user interface (PUI).

Examples for using this feature:

• Controlling settings on the PBX with dedicated keys that turn PBX functions on and off. The available functions must have been set on the PBX and they must be accessible from the phone, typically by dialing a star code. Phone function keys can be dedicated to activating and deactivating call forwarding and DND mode, transferring, picking up, and parking/unparking calls, etc. Depending on the settings on your PBX, you may either have to dedicate one key each for activating and deactivating a given function or to dedicate one key for both activating and deactivating the function.
• Silent alarms or emergency calls.
  If the standard behavior of this function key type does not meet your requirements, it is possible to customize it. Copy the standard XML configuration of the key from the Settings page of the phone's web user interface (WUI) and edit it to suit your needs. Then paste the edited XML into the "Number" text field and change the key's type to "Xml definition"

Transferring active calls and ringing incoming calls to the number set in the "Number" text field. Pressing the key once will transfer the active or ringing call.

If the text field is empty, pressing the key will put the "Enter number" screen on the display. Enter the number and press / to complete the transfer.

For further information, see the article "Transferring calls" in the chapter "Using the phone".

The phone does not record the voice streams at all; they must be recorded on the PBX where a recording account must be set up. Pressing the key when the phone is idle will establish a connection between the phone and the recording account, making it possible to record spoken memos, meetings, or conferences. Pressing the key during a call will establish a three-party conference with the two phones and the recording account as participants. Please be advised that you must respect the legal restrictions of your country for recording calls with or without the participants' knowledge and permission.

Copy the XML sub tag of the action(s) you want the key to perform into the text field. The currently available settings can be found here: http://wiki.gigasetpro.com/Features/Mass_Deployment/Setting_Files/XML/XmlSubTags.