- Home
- /
- Article
Configure the Action Button for 9800 (Control Hub)
The Action button is the red button located at the top right of the phone. It allows users to quickly access designated services, such as emergency or custom services. You can custom the button to initiate events that suit your specific use cases. The information on this page applies to Cisco Desk Phone 9800 Series registered to Webex Calling.
Configure the Action button for emergency calls
The Action button for emergency calls ensures quick and easy access to critical assistance in workspaces.
1 |
From the customer view in Control Hub, go to Devices, and then select your phone. |
2 |
Select . |
3 |
Navigate to the Phone section and select Action Button. |
4 |
Configure the following parameters:
For more details about these parameters, see Parameters for the Action button. |
5 |
Select Next. |
6 |
Review your changes and select Apply. |
7 |
Select Close to close the page. |
Configure the Action button for a custom service
When you associate the Action button with a custom service, the phone users can access the service by the designated trigger, such as a single press, long press, or triple presses on the button.
1 |
From the customer view in Control Hub, go to Devices, and then select your phone. |
2 |
Select . |
3 |
Navigate to the Phone section and select Action Button. |
4 |
Configure the following parameters to associate the Action button with a custom service.
For more details about these parameters, see Parameters for the Action button. |
5 |
Select Next. |
6 |
Review your changes and select Apply. |
7 |
Select Close to close the page. |
Configure a single trigger for multiple events
A single trigger for multiple events allows one action on the action button to initiate several related processes simultaneously. This feature enhances responsiveness, reduces complexity, and ensures seamless workflow execution across applications.
1 |
From the customer view in Control Hub, go to Devices, and then select your phone. |
2 |
Select . |
3 |
Navigate to the Phone section and select Action Button. |
4 |
Configure the following parameters to enable the Action button to trigger multiple events at a time.
For more details about these parameters, see Parameters for the Action button. |
5 |
Select Next. |
6 |
Review your changes and select Apply. |
7 |
Select Close to close the page. |
Configure multiple triggers
You can configure the Action button to connect to multiple services and assign each service with its own trigger. For example, a long press on the Action button places a call to the designated emergency agent; a single short press on the button post a notification to the phones within the corporation.
1 |
From the customer view in Control Hub, go to Devices, and then select your phone. |
2 |
Select . |
3 |
Navigate to the Phone section and select Action Button. |
4 |
Set Service Trigger to MultiTrigger.
|
5 |
Go to Single Press, Long Press, and Press 3 times. and select your desired trigger from the available options - |
6 |
Configure the following parameters for your selected trigger:
For more details about these parameters, see Parameters for the Action button. |
7 |
Repeat Step 5 to 6 to configure more triggers. |
8 |
Select Next. |
9 |
Review your changes and select Apply. |
10 |
Select Close to close the page. |
References
Parameters for the Action button
The parameters for the Action button can be found in the configurations at device, location, and organization level.
For more information about how to configure phone settings at location and organization level, see Configure Cisco Desk Phone 9800 Series on Control Hub.
Parameter | Default and options | Description |
---|---|---|
Action Button Function |
Default: Off Options: Off, Emergency Call, Custom | |
Action Button Service Destination |
Default: Empty | |
Action Button Service Name |
Default: Empty | |
Allow Silent Emergency Call Retrieval |
Default: No Options: Yes, No |
Controls whether users can retrieve phone functionality during a silent emergency call. By default, once a silent emergency call is initiated, the phone locks all functions until the call recipient ends the call. When this parameter is set to Yes, users can press any key to restore normal phone operation while maintaining the emergency call. The call audio remains silent unless the user increases the volume using the Volume key. |
Custom Content Field |
Default: Empty |
This setting works only when the Action Button Function is set to Custom. Enter the HTTP data such as method, header, and post content, with a maximum length of 1024 characters. When configured, the phone sends an HTTP Post request when the Action is pressed. You can use macros in the HTTP data, such as $MA, $SN. For POST script examples and the syntax, see HTTP Post request for the Action button. |
Dial Out Delay |
Default: 5 Options: 0 - 30 |
Set the timeout period, in seconds, for the phone to initiate an emergency call or a custom action after the Action button is pressed. Set it to 0 if you prefer the phone to place the call or initiate an event immediately upon detecting the trigger, as specified by a single press, long press, or triple presses on the button. |
Service Trigger |
Default: Single Press Options: Single Press, Long Press, Press 3 times, MultiTrigger |
Choose how users can place an emergency call or initiate a custom service using the phone's Action button. Single Press: Press the Action button to trigger the associated call or service. Long Press: Press the Action button down for at least 2 seconds to trigger the associated call or service. Press 3 times: Press the Action button three times with intervals of one second between each press to trigger the associated call or service. MultiTrigger: Select this option to associate multiple triggers and events to the Action button. Go to the Service Trigger MultiTrigger section to select a trigger and configure the specific settings. For detailed information about multiple triggers, see Configure multiple triggers. |
Service Trigger MultiTrigger | Options: Single Press, Long Press, Press 3 times |
This setting works only when Service Trigger is set to MultiTrigger. Choose a trigger from the available options to open and configure the settings. For detailed information about multiple triggers, see Configure multiple triggers. For details about the MultiTrigger parameters, see Parameters for MultiTrigger. |
Silent Emergency Call |
Default: Disabled Options: Enabled, Disabled |
Silent emergency call is designed for discreet assistance in dangerous situations. It enables users to seek help without making any noise.
|
Parameter | Default and options | Description |
---|---|---|
Action Button Function |
Default: Off Options: Off, Emergency Call, Custom | |
Action Button Service Destination |
Default: Empty | |
Action Button Service Name |
Default: Empty | |
Custom Content Field |
Default: Empty |
This setting works only when the Action Button Function is set to Custom. Enter the HTTP data such as method, header, and post content, with a maximum length of 1024 characters. When configured, the phone sends an HTTP Post request when the Action is pressed. You can use macros in the HTTP data, such as $MA, $SN. For POST script examples and the syntax, see HTTP Post request for the Action button. |
Dial Out Delay |
Default: 5 Options: 0 - 30 |
Set the timeout period, in seconds, for the phone to initiate an emergency call or a custom action after the Action button is pressed. Set it to 0 if you prefer the phone to place the call or initiate an event immediately upon detecting the trigger, as specified by a single press, long press, or triple presses on the button. |
Silent Emergency Call |
Default: Disabled Options: Enabled, Disabled |
Silent emergency call is designed for discreet assistance in dangerous situations. It enables users to seek help without making any noise.
|
HTTP Post request for the Action button
The Action button on Cisco Desk Phone 9800 Series can be configured to trigger XML applications through HTTP Post requests.
In Custom Content Field, enter the request script. You can specify either XML or JSON content type and include macros in the request.
The following examples are in XML and JSON:
Sample #1: XML
--method POST
--header 'Content-Type: application/xml'
--body '<MetaData><Trigger>True</Trigger><Description>This is for HTTP POST XML</Description></MetaData>'
Sample #2: JSON
--method POST
--header 'Content-Type: application/json'
--body '{"events":[{"evtid":"12345", "parameters": {"trigger":true}, "Description":"This is for HTTP POST JSON"}]}'
The following example is for an HTTP Post request.
--method POST
--header 'Content-Type: application/xml'
--body '<MetaData><Trigger>True</Trigger><Description>This is for HTTP POST XML</Description></MetaData>'
Macro name | Macro expansion |
---|---|
#DEVICENAME# | The device name displayed in the calling system; for example, SEP845A3EC21288 |
$MA | MAC address using lowercase hex digits (000e08aabbcc). |
$MCASTADDR | Address of multicast paging application. |
$PN $PSN | Product Name; for example, DP-9851, DP-9871. |
$SN | Serial Number string; for example, FVH28022D0T. |
Macro variables supported in XML URLs
You can use macro variables in XML URLs. The following macro variables are supported:
-
User ID—UID1, UID2 to UIDn
-
Display name—DISPLAYNAME1, DISPLAYNAME2 to DISPLAYNAMEn
-
Auth ID—AUTHID1, AUTHID2 to AUTHIDn
-
Proxy—PROXY1, PROXY2 to PROXYn
-
MAC Address using lowercase hex digits—MA
-
Product Name—PN
-
Product Series Number—PSN
-
Serial Number—SERIAL_NUMBER
Macro Name | Macro Expansion |
---|---|
$ | The form $$ expands to a single $ character. |
A through P | Replaced by general-purpose parameters GPP_A through GPP_P. |
SA through SD | Replaced by special purpose parameters GPP_SA through GPP_SD. These parameters
hold keys or passwords used in provisioning. $SA through $SD are recognized as arguments to the optional resync URL qualifier, --key. |
MA | MAC address using lowercase hex digits (000e08aabbcc). |
MAU | MAC address using uppercase hex digits (000E08AABBCC). |
MAC | MAC address using lowercase hex digits with a colon to separate hex digit pairs (00:0e:08:aa:bb:cc). |
PN | Product Name; for example, Video Phone 8875, Desk Phone 9851. |
PSN | Product Series Number; for example, 8875, 9841, 9861 |
SN | Serial Number string; for example, 88012BA01234. |
CCERT | SSL Client Certificate status, installed or not installed. |
IP | IP address of the phone within its local subnet; for example, 192.168.1.100. |
EXTIP | External IP of the phone, as seen on the internet; for example, 66.43.16.52. |
SWVER |
Software version string. For example, PHONEOS.3-2-1-0104-37 |
HWVER |
Hardware version string. For example, 2.0.1 |
PRVST |
Provisioning State (a numeric string): -1 = explicit resync request 0 = power-up resync 1 = periodic resync 2 = resync failed, retry attempt |
UPGST |
Upgrade State (a numeric string): 1 = first upgrade attempt 2 = upgrade failed, retry attempt |
UPGERR |
Result message (ERR) of previous upgrade attempt; for example http_get failed. |
PRVTMR |
Seconds since last resync attempt. |
UPGTMR |
Seconds since last upgrade attempt. |
REGTMR1 |
Seconds since Line 1 lost registration with SIP server. |
REGTMR2 |
Seconds since Line 2 lost registration with SIP server. |
UPGCOND |
Legacy macro name. |
SCHEME |
File access scheme, one of TFTP, HTTP, or HTTPS, as obtained after parsing resync or upgrade URL. |
SERV |
Request target server host name, as obtained after parsing resync or upgrade URL. |
SERVIP |
Request target server IP address, as obtained after parsing resync or upgrade URL, possibly following DNS lookup. |
PORT |
Request target UDP/TCP port, as obtained after parsing resync or upgrade URL. |
PATH |
Request target file path, as obtained after parsing resync or upgrade URL. |
ERR |
Result message of resync or upgrade attempt. Only useful in generating result syslog messages. The value is preserved in the UPGERR variable in the case of upgrade attempts. |
UIDn |
The contents of the Line n UserID configuration parameter. |
ISCUST |
If unit is customized, value=1, otherwise 0. Customization status is viewable on Web UI Info page. |
INCOMINGNAME | Name associated with first connected, ringing, or inbound call. |
REMOTENUMBER |
Phone number of first connected, ringing, or inbound call. If there are multiple calls, the data associated with the first call found is provided. |
DISPLAYNAMEn | The contents of the Line N Display Name configuration parameter. |
AUTHIDn | The contents of the Line N auth ID configuration parameter. |