Call Telemetry for Cisco

Appearance

CUBE Telemetry via Webhooks ​

Feature Overview ​

This feature allows you to send CUBE XCC events (ALERTING, CONNECTED, DISCONNECTED) with Caller ID information to third party JSON webhook endpoints. This can be used to integrate with other systems or to send alerts based on XCC events.

Several customer have asked - Can we get live streaming call event telemetry without using Cisco JTAPI / TSP or building our own CUBE XCC / WSAPI Integration?

Currently the payload includes the following fields:

json
{
call_state:"DISCONNECTED"
called_number:"+12512501663"
calling_number:"+12517676234"
timestamp:"2024-11-23T16:03:36.200940Z"
}

Read about Call Telemetry's integration with Cisco CUBE using the XCC API here.

Read more about XCC API on Cisco XCC API documentation

Feature Requirements ​

Configuration ​

  1. Navigate to the CUBE XCC Webhooks page in the Call Telemetry Web UI, under Cubes, XCC Webhooks.

  2. Add a new Webhook by clicking the Add Webhook button.

Webhook Details ​

  • Enter a webhook Name, Description, and the URL of the endpoint you want to send the XCC events to.
  • Select the XCC Events you want to send to the webhook - such as ALERTING, CONNECTED, DISCONNECTED.
  • Enable the Webhook via toggle button.
  • Associate the Webhook with a CUBE.
  • Add additional Headers if needed.
  • Click Save.

CUBE XCC Webhooks Edit

On saving, your screen should look like this:

CUBE XCC Webhooks Logs

  1. Place a test call to the CUBE and verify the Webhook is sending the XCC events to the endpoint. View logs by clicking the calendar icon on the table row.

You can see recent webhook logs and their reqest and response details, and any HTTP Errors.

Example Webhook logs: ​

CUBE XCC Webhooks Logs

Example Webhook Errors: ​

CUBE XCC Webhooks Log Errors