Call Telemetry for Cisco

Appearance

911 Cisco IP Phone Discovery App ​

Feature Overview ​

Phone Discovery App is a post call app can be attached to a 911 Call Alert Rule, and discovers Cisco Callamanger and Cisco IP Phone data in realtime as the call is being connected. This app queries the phone for Callmanager, Network and Subnet Data, which is then available for use in downstream Apps or Alerts to provide more context to your emergency response teams.

Feature Requirements ​

Discovering Network Elements ​

  • Query Cisco IP Phone Information from Callmanager:
    • Obtain Phone Model, Description, and Device Pool details.
  • Query Live Cisco IP Phone Details:
    • Discover Network Switch CDP and LLDP Neighbor and Switch Port details
    • Discover Subnet and Mask information
  • Perform Traceroute Analysis:
    • Identify IP Phone connectivity by tracing the route to the next hop.

This data is attached to the call and available as variables for any other post call app to use.

Stacking with other Apps for more location data ​

The Phone Discovery App can be used in conjunction with other Apps to build a rich context of data for your emergency response teams.

Other related Apps include:

  • Subnet CSV - Compares the Subnet discovered from the Phone to a CSV list, with optional data fields adding more context. List can be downloaded per schedule.
  • XML Query App - Queries an XML SOAP Service with context data, like the phone MAC address, and can gain more context location for alerts.
  • Webhook App - Can query a JSON API and attach the body to the call for use in alerts.

You can compose detailed Call Alerts with this data, or use it in other Apps to trigger actions based on the phone's location or network data.

json
{
  "app_data": {
    "phone-discovery": {
      "data": {
        "neighbor": {
          "neighbor_ip": "192.168.123.214",
          "neighbor_name": "Switch",
          "neighbor_port": "GigabitEthernet1/0/5",
          "output": "Phone Neighbor Query successful."
        },
        "next_hop": {
          "fqdn": "Switch",
          "hostname": "SWITCH",
          "icmp_output": "ICMP Traceroute skipped as CDP is present.",
          "ip": "192.168.123.214"
        },
        "phone": {
          "description": "Auto 1006",
          "device_name": "SEPC4143C8B8BF9",
          "device_pool": "Default",
          "extension": "1006",
          "firmware": "9.4.1.3SR3",
          "ip": "192.168.123.218",
          "model": "Cisco 6921",
          "neighbor": {
            "neighbor_ip": "192.168.123.214",
            "neighbor_name": "Switch",
            "neighbor_port": "GigabitEthernet1/0/5",
            "output": "Phone Neighbor Query successful."
          },
          "next_hop": {
            "fqdn": "Switch",
            "hostname": "SWITCH",
            "icmp_output": "ICMP Traceroute skipped as CDP is present.",
            "ip": "192.168.123.214"
          },
          "ris_data": {
            "ActiveLoadID": "SCCP69xx.9-4-1-3SR3",
            "Description": "Auto 1006",
            "DirNumber": "1006",
            "IPv4": "192.168.123.218",
            "Model": "Cisco 6921",
            "Name": "SEPC4143C8B8BF9",
            "Status": "Registered",
            "StatusReason": "0"
          },
          "status": "Registered",
          "status_reason": "",
          "subnet": "192.168.123.0/24"
        },
        "subnet": "192.168.123.0/24"
      },
      "message": "Phone Discovery App completed.",
      "provider_message": "Phone Discovery App completed.",
      "result": "success"
    }

Network Switch Hostname Transformations ​

Custom network switch hostname transformations can be applied to the data. This is useful for translating switch names to a more human readable format for security and emergency response staff.

Screenshot showing hostname transformations