# Emergency Alert and Response

Call Telemetry views 911 calls differently than traditional solutions. Our mission is to locate as much data as possible, and build a context location about the phone. We believe that some system knows now, or will know where phones are located. We have tied into CSV, HTTP, and Meraki API to add even more location information to realtime communication alerts. We also build tools to support Network Admins in wire mapping - like our QR Code Wire Mapping for Cisco, saving labor of wire mapping buildings while providing as much safety information as possible in an emergency situation.

# Solution Overview

# Requirements

  • Enterprise License
  • CUCM version 11.5.1.13900-42 (SU3) or higher.
    • Versions bellow this can still get 911 notifications but without location.

# What if I have Emergency Responder?

# We ❤️ Emergency Repsonder - we just add workflows and more discovery.

Great! This is not a replacement. It's an enhacement to your Emergency Response plan.

# Installing with Cisco Emergency Responder

Just attach the ECC / CURRI Profile for Call Telemetry onto your 911 pattern, or CTI ports for Emergency Responder. CER continues to do the ELIN transformations, and Call Telemetry gives you more location and alert workflows.

# What can you discover?

  • CUCM Device information
    • Model, Description, CUCM Location, etc.
  • Phone Details
    • CDP/LLDP, Subnet Mask
  • Traceroute to next hop
    • Identify phone as an MRA or VPN connected device
  • CSV Data about the Subnet - Any fields you want to provide
  • HTTP API Response containing further location information for use in variables
  • Meraki API - Location of device in Meraki Org for location context

# High Level Overview of Realtime Discovery

location_process

# Data Model:

Here's an example payload available after a successful discovery. You can use these fields in alerts or apps.

{
"event":{
"called_number":"1001",
"calling_devicename":"SEP000832C78E0F",
"calling_number":"231",
"id":21331,
"trigger_point_type":"translation_pattern"
},
"final":{
"action":"permit",
"modifiers":{
"calledname":,
"callednumber":,
"callingname":,
"callingnumber":
},
"reason":"permit rule",
"rule":{
"name":"test3",
"greeting_enabled":false,
"greeting_name":"Jason",
"calling_number":".*",
"called_number":"1001",
"policy_action":"permit"
}
},
"phone":{
"description":"Demo Phone - Room 101",
"device_name":"SEP000832C78E0F",
"device_pool":"Default",
"extension":"1001",
"firmware":"14.1.1.0001.136",
"ip":"192.168.123.218",
"location":{
"address":{
"name":"Home",
"address1":"1234 Main St",
"address2":,
"city":"Fairhope",
"state":"AL",
"zip":"36532"
},
"address_text":"1234 Main St Fairhope,AL 36532",
"match":"port",
"near":"IDF-Room101 Floor 1, NE Corner of Building.",
"port":{
"name":"GigabitEthernet1/0/15"
},
"switch":{
"name":"Switch",
"location":"IDF-Room101 Floor 1, NE Corner of Building.",
"ip":"192.168.123.214"
}
},
"model":"Cisco 7821",
"neighbor":{
"neighbor_ip":"192.168.123.214",
"neighbor_name":"Switch",
"neighbor_port":"GigabitEthernet1/0/15"
},
"next_hop":{
"fqdn":"Switch",
"hostname":"Switch",
"ip":"192.168.123.214",
"output":
},
"ris_data":{
"ActiveLoadID":"sip78xx.14-1-1-0001-136",
"Description":"Demo Phone - Room 101",
"DirNumber":"1001",
"IPv4":"192.168.123.218",
"Model":"Cisco 7821",
"Name":"SEP000832C78E0F",
"Status":"Registered",
"StatusReason":"0"
},
"status":"Registered",
"status_reason":"",
"subnet":{
"ip_with_cidr":"192.168.123.218/24",
"subnet":"192.168.123.0/24",
"subnet_base":"192.168.123.0/24",
"subnet_prefix":"24"
}
},
"policy":{
"name":"test",
"api_key":"950bd6e7-5555-5555-5555-bfcf9bfd73ab"
}
}