Call Telemetry for Cisco

Appearance

Rule Alerts and Alert Templates ​

Rules have a completely template for alerting with full variable support, as well as a list of alerts. Alerts are triggered when the rule is matched. Alerts can be sent to email, SMS, MS Teams through native integrations, or via webhooks to any Alert API.

Feature Requirements ​

Call Alert and Notifications require the following features to be enabled:

Alert Destinations ​

Rule Alerts can be sent to multiple destinations. The following alert types are supported natively on the rule page.

  • Email via SMTP
  • SMS via Twilio
  • MS Teams via Integration or Channel Webhook Screenshot of Alert Destinations

TIP

You can also use the Webhook App to send a templated payload trigger to any JSON API.

Composing Alert Templates ​

Alert Templates can contain variables that are replaced with the actual values at runtime. Variables are enclosed in double curly braces, like this: {{variable_name}}.

Each Policy App has it's own unique variables from the payloads processed, and a standard output message. Some Apps use this for success/failure, and some apps use this as their final output.

You can filter out any failure by using the toggle at the bottom, to exclude rendering any Messages output that may confuse a recipient with diagnostic information.

Screenshot showing rules with their alert messages and variables

Previewing an Alert Template ​

Complex Alert templates can be difficult to validate without valid data. To help you build those complex alerts, the Preview window automatically renders the alert based on the last Call Debug Test data.

The example below shows a preview of an alert rendered from the last call tests data. It shows a customized 911 alert, with the calling number, and the location of the calling phone, which includes switch, port, subnet, and other location data.

You can discover detailed emeregency dispatable locations and compose rich 911 alerts using realtime data with our 911 Location Discovery Sources for your emergency response notications.

Alert Variables ​

Alerts can contain variables that are replaced with the actual values at runtime. Variables are enclosed in double curly braces, like this: {{variable}} or {{parent_object.variable}} This tree allows you to visualize the variables available to you in the alert template.

Apps

Built-in Variables ​

The following variables are supported natively from the call events, and are available in all alerts.

  • Call Event Data

Discovery App Variables ​

The following variables are supported natively from the Discovery App, and are available in all alerts ONLY if the Phone Discovery App is enabled:

  • Location
  • Switch Device Details
  • Switch Neighbor Details
  • Layer 3 Next Hop Details (via ICMP Traceroute)

Custom App Workflows ​

Each App contains it's own unique variables from the payloads processed, and a standard output message for the alert template engine. For example the Webhook App will hit an API, and expose the entire response dictionary as a variable for use in the alert template.

  • Webhook App
  • Spam Reputation App
  • Subnet CSV Lookup
  • SOAP API App
  • PostgreSQL Lookup App
  • Send to Twilio
  • Send to Webex Teams
  • Send to MS Teams
  • Send to Email