Skip to main content

Architecture

Call Telemetry connects to Cisco Unified Communications via multiple APIs for real-time policy enforcement, analytics, phone control, and emergency services.

Cisco API Integrations​

APIProtocolPurposeFeatures
CURRIHTTPS callbackReal-time call routing decisionsPolicy Engine, call blocking, translations, greetings
CUBE XCCHTTPS / UC-WSAPISIP gateway call controlCUBE Analytics, external call policy
CDRSFTP uploadCall detail recordsReports, webhooks, missed calls, alerts
RISSOAPReal-time phone statusPhone dashboard, registration monitoring
AXLSOAPAdmin XML configurationUser sync, phone discovery, policy provisioning
JTAPITCP 2748 (CTI)Java Telephony APIRemote control, greeting injection, paging
Phone XMLHTTPIP phone web accessCDP/LLDP neighbor discovery, subnet mapping

Security & Permissions​

Each integration uses isolated credentials with minimal required permissions.

IntegrationCredentialPermission Level
CURRI / XCCAuto-generated API key per policy URLCall Telemetry issues the key
CDR (SFTP)Auto-generated username/passwordCall Telemetry issues credentials
AXL / RISCUCM Application UserRead-only for reporting; read/write for JTAPI and policy provisioning
CTI / JTAPICUCM Application UserCTI control permissions required

AXL / RIS (Read-Only)​

A single read-only AXL user covers most features:

tip

Read-only AXL/RIS covers reporting, phone dashboards, missed calls, and user sync. Read/write is required for automatic CURRI policy provisioning, JTAPI greeting injection (CTI port/route point provisioning), and CTI port auditing.

CTI / JTAPI​

A JTAPI Application User with CTI control permissions enables:

  • Remote phone control (place, hold, transfer, conference calls)
  • Greeting injection (G.711 audio into live calls)
  • Sequential and parallel paging
  • CTI port pool management

Requirements: Cisco JTAPI JAR matching your CUCM version (CUCM Administration > Plugins), network access to CTI Manager on TCP 2748.

Next Steps​