Rules can be configured to trigger the Vocera CUCM Adapter to send messages to Cisco phones registered with the Cisco Unified Communications Manager.
See the Vocera Platform Dataset Guide for information about working with rules. See Configuring a Vocera CUCM Adapter for information about the adapter settings.
In the Adapter Settings, configure the Rule Settings fields to manage message delivery.
| Setting | Description |
|---|---|
| Alert Heading | The heading shown on the top of the login screen for the alert. Can be hard-coded text or an attribute expression in the form of an attribute #{...}. |
| Phone |
The phone number(s) to which the alert message will be delivered. Can be hard-coded text or an attribute expression in the form of an attribute #{...}. If hard-coded, the value can be a single phone number, or multiple phone numbers that are comma-separated. Required when "Static Message" is not enabled. |
| Static Message |
If enabled, the adapter will send plain text to a Cisco phone. When enabled, the "Parameters" and "Workflow Page" will be disabled and "Static Message Content" will be marked as required. If not enabled, the "Phone" and "WorkflowPage" fields are required and the "Static Message Content" field is disabled. |
| Static Message Content |
The content to be sent as static text. Required if "Static Message" is enabled. |
| Workflow Page |
The workflow page that will be displayed on the phone when the message is delivered. The page will display all currently defined workflow pages grouped by the workflow that contains them. Required when "Static Message" is not enabled. |
| Parameters | Additional query string parameters that will be passed to the workflow page when it is opened. Parameters are entered in the form "key=value", one per line. |
| Templated Priority |
If enabled, the priority for the rule will be set by a templated attribute expression. If not enabled, the "Execute Priority" and "Priority Level" fields are required. When enabled, the "Priority" field displays, and is required.
|
| Priority |
Begin typing to display an autocomplete option for the expected values, or enter a templated attribute expression which evaluates to one of the expected values. Expected alert priority values are "URGENT", "HIGH", or "NORMAL". The execute priority and alert priority are mapped internally from these expected values when sending a message. Required when "Templated Priority" is enabled. |
| Execute Priority | Defined by Cisco, specifies the priority for when the
workflow page, audio alert, and vibration execution will occur. The
choices are "Immediate", "When Idle", and "Only if Idle". " Immediate" will execute the URL regardless of the phone state, even if other calls or actions are in progress. "When Idle" will execute the URL when the phone becomes idle. "Only If Idle" will execute the URL if the phone is idle when the request occurs, and will never execute the URL if the phone is not idle when the request occurs. Displays when "Templated Priority" is not enabled. |
| Priority Level |
The severity level of the message. Tracked by the device object so that rules can filter out lower severity level messages. Options are "High", "Medium", and "Low". Displays when "Templated Priority" is not enabled. |
| Vibrate Enabled | If enabled, tells the phone to vibrate when the message is received (based on Execute Priority). |
| Audible Alert | If enabled, tells the phone to play the sound defined in "Alert Sound" when the message is received (based on Execute Priority). |
| Alert Sound | The sound file for the phone to play if "Audible Alert" is enabled. Leave this field empty to play the default alert sound. |
