Webhooks & Exports
Send real-time call data to external systems using webhooks. Call Telemetry can stream CUBE call events, forward CDR records, or trigger custom API calls during live calls — powering CRM integrations, analytics dashboards, and automated workflows.
Webhook Types
| Type | Trigger | Data | Use Case |
|---|---|---|---|
| CUBE Webhooks | CUBE call state changes (alerting, connected, disconnected) | Lightweight JSON with caller/called numbers and timestamps | Screen pops, real-time dashboards, CRM updates |
| CDR Webhooks | New CDR record processed | Full CDR payload with conditional filters | Billing sync, compliance logging, analytics |
| Policy App Webhooks | Call matches a policy rule | Call event data with template variables | CRM caller ID resolution, custom routing logic |
Guides
| Guide | Description |
|---|---|
| CUBE Call Event Webhooks | Stream real-time call events from Cisco CUBE gateways |
| CDR Webhooks | Forward CDR records to external systems with conditional triggers |
| Policy App Webhooks | Trigger API calls during live calls for CRM lookups or custom workflows |
Requirements
- Call Telemetry Appliance 0.8.3 or later
- A webhook-capable endpoint (HTTPS recommended) accessible from the Call Telemetry appliance
- For CUBE webhooks: Cisco CUBE with XCC Integration
- For CDR webhooks: CDR Integration configured
- For policy webhooks: CURRI API Integration configured
Licensing
| Feature | Community | Essentials+ |
|---|---|---|
| CUBE Call Event Webhooks | -- | Yes |
| CDR Webhooks | -- | Yes |
| Policy App Webhooks | -- | Yes |
Related Documentation
- CUBE XCC Integration — Configure CUBE for call event streaming
- CDR Integration — Set up CDR collection via SFTP
- REST API Contact Resolution — CRM caller ID via policy webhooks
- Call Policy Configuration — Rule triggers and app association