Call Telemetry for Cisco

Appearance

911 Notifications and Cisco CER Integration ​

Call Telemetry makes is easy to get instant discovery data from your Cisco Callmanager, and build rich 911 alerts with location, subnet, and switch data, and get that data to your emergency response teams and systems in realtime.

  • IP Phone Data is discovered live, as the call is happening, to get the most accurate location data.
  • Subnet data is correlated with CDP and LLDP Neighbor switch and port data to build a rich location context for your 911 alerts - without ever touching a switch.
  • API Data can be queried in realtime to augment your 911 alerts with data from your Inventory like Cisco DNA, Meraki, Netbox or other systems.
  • Customizable Alert Templates render your data into MS Teams, SMS, Email alerts
  • Webhook Apps can send customized 911 alert data to any API, like lighting, paging, or other alerting systems.

Configuring 911 Notifications with Cisco Callmanager and Cisco Emergency Responder ​

Follow the normal policy configuration guide to setup your 911 policy. Add a rule to trigger on .*. Attach the ECC / CURRI Profile for Call Telemetry onto your 911 or 933 pattern, or CTI ports for Emergency Responder. CER continues to do your E911 compliance and ELIN transformations, and Call Telemetry gives you extra alerts.

Alert Example - 911 Notification with CDP and Subnet Data ​

Here's an example of a simple alert template. This can be enabled in just a few minutes, and you'll get a rich alert like this.

Call Telemetry Alert - 911 Demo
Call Event: 1234 called 911
Phone: SEP123456789012
Phone Description: An Awesome Description from Callmanager
Switch Name: DEMO Switch
Port: GigabitEthernet2/1
IP: 1.1.1.1
Subnet: 1.1.1.9/24

Alert Template Configuration ​

Here's the alert template that generated the above alert. This is a simple example, but you can build rich alerts with multiple variables.

A comprehensive list of variables is available in the Alert Variables section. Remember - your Call Apps can define your own expanded data variables.

Call Telemetry Alert - 911 Demo
Call Event: {{event.calling_number}} called {{event.called_number}}
Phone: {{phone.device_name}}
Phone Description: {{phone.description}}
Switch Name: {{neighbor.switch_name}}
Port: {{neighbor.neighbor_port}}
IP: {{neighbor.neighbor_ip}}
Subnet: {{phone.subnet}}

Adding Civic Address Data to your 911 Alerts ​

Adding address data is optional and based on matching the phone's switch and port to an address in Call Telemetry.

There are 4 tiers of location in Call Telemetry. Each object can be linked to an emergency dispatchable location with detailed descriptions. For example:

  • Subnet: "12th Floor" - Civic Address of Subnet
  • Switch: "12th Floor, North IDF" - Civic Address of Switch Neighbor or Subnet
  • Port: "Room 101, Floor 12" + Street Address from Subnet or Switch Neighbor or Subnet
  • Phone: "Main Lobby Door, Room 101, Floor 12" + Street Address from Switch Neighbor or Subnet

Where address is a civic address, near is a switch or port, and location is a room or phone location.

These translate to a rich alert like this:

Address: DEMO - XXXX Main St. Anytown, USA YYYYY
Near: DEMO - Switch Closet - XX Floor.
Location: DEMO - Room XX

Could we just transform the ELIN from the policy? Yes... let us know if you're interested.

This feature requires CUCM version 11.5.1.13900-42 (SU3) or higher. There was a field added in CURRI that makes this possible in that version. You'll still get 911 notifications in earlier versions, just not with location.