Architecture and API Integrations

Cisco APIs

Call Telemetry uses realtime event streams from Cisco Callmanager, and Cisco IP Phones for policy enforcement, and telemetry events.

• Cisco CURRI API and Extended Call Control Profiles - provides realtime call event data, and policy control from Cisco Callmanager.
• Cisco XCC and UC-WSAPI for IOS - provides realtime call event data, and policy control from Cisco IOS CUBE routers.
• Cisco CDR - is processed to obtain additional call events data for reports, missed calls, and CDR Webhooks.
• Cisco RIS - Callmanager API that provides realtime phone registration status. Thi
• Cisco AXL - Callmanager API that provides User data.
• Cisco IP Phone XML - Web Access on the phone for CDP and Subnet discovery.

External APIs and Live Telemetry Events

Call Telemetry also has realtime and post-call events triggers, and can with external APIs to provide additional data and control.

These are examples of where you can leverage external APIs to augment your Cisco Callmanager environment:

• Centralized Extended Call Policy Control and Blocking
• Realtime Call Event Apps to query other APIs for actions, like block, rename, or redirect.
• Post Call Event Apps to query API events. POST call data to other systems like CRMs.
• 911 Alerting with API Discovery to add Dispatachable Emeregency Data to Emeregency Notification template alerts.
• CDR Event Webhooks to trigger on any CDR conditions.
• Missed Call Events to Email and Webex Teams

Security permissions needed

• Cisco Callmanager CURRI API, Cisco IOS CUBE XCC: A unique API key is issued by Call Telemetry for each policy url.

• Cisco CDR: A unique username and password for SFTP are generated by Call Telemetry.

• AXL and RIS User can be issued as read-only permissions, and are used in several product components:

• Missed Call Notifications and Alerts
• IP Phone Dashboard and Reports
• Automatic provision of Call Policies
• Jabber Portal
• Phone XML Portal
• Phone Discovery App

• CTI User is used in the following features:

• Remote Control of Cisco IP Phones

Integration Details

The integration guide covers the integration process with Cisco Callmaanger. The following outlines exactly where each API is used in Call Telemetry.

Most Call Telemetry users will only need to configure one user with read-only AXL and RIS roles.

Cisco Callmanager CURRI API and Policy Engine

A unique API key is issued by Call Telemetry for each policy url.

Callmanager AXL is required for the activities below:

• Automatic Extended Call Control Profile Provisioning - Automatic Extended Call Control Profile creation within Cisco Callmanager requires a valid AXL user with read/write permissions. Policies can be created manually, this feature is optional. Learn more in the Policy Design Guide.
• Call Discovery Apps - If you have Premium licensing, the Phone Discovery App requires AXL and RIS permissions to discover live Cisco IP Phone data.
• Jabber Portal - If you have Advanced licensing, the Jabber Portal requires read-only AXL permissions to query user data.
• Phone Portal - If you have Advanced licensing, the Phone XML Portal requires read-only AXL permissions to query user data.

Cisco IOS CUBE XCC

You can link Cal Telemetry to Cisco CUBE XCC API for call policy processing and Cisco CUBE Analytics and Call Detail Reporting. This is the preferred method for enforcement at scale.

Cisco CDR Reports and Webhooks

A SFTP username and password is generated from Call Telemetry. An admin will configure the upload of Cisco Billing records to the SFTP server.

Missed Call Alerts and Notifications

Cisco AXL is required for this feature. A read-only AXL user is acceptable.

Dashboard and Cisco IP Phone Remote Control

• Cisco Callmanager AXL, RIS are required for this feature. A read-only AXL user is acceptable.
• Cisco Callmaanger CTI User is required for Remote Control feature.

High Level Diagram