CUCM Configuration Intelligence
Configuration Intelligence gives Cisco CUCM teams a repeatable configuration-audit workflow: establish an approved baseline, see what changed, understand the risk, and collect evidence for review. The workflow stays in Call Telemetry—from the living configuration record and first snapshot through a comparison, restore preflight, or report package.
Before You Begin
These instructions match the GA Configuration Intelligence interface in Call Telemetry 0.8.7-stable.
You need:
- An authenticated Call Telemetry organization.
- A CUCM cluster configured in Call Telemetry with working AXL access.
- An active Premium license. Demo and Beta licenses also expose the workspace for evaluation and testing.
- At least one successful configuration snapshot before you compare changes or generate reports.
Community, Essentials, and Advanced organizations can see Configuration Intelligence in navigation, but the workspace remains locked and direct Config Audit API requests are rejected until Premium is active.
Follow the Configuration Intelligence Workflow
Use the pages in this section in order when you are setting up Configuration Intelligence for the first time.
| Stage | What You Accomplish | Guide |
|---|---|---|
| Enable and configure | Choose tracked objects, retention, masking, and notifications | Set Up Configuration Intelligence |
| Establish a baseline | Capture the current CUCM state and pin the approved snapshot | Create Snapshots and Schedules |
| Automate collection | Run recurring snapshots and optional evidence delivery | Create Snapshots and Schedules |
| Monitor and investigate | Review drift, risk, related changes, and impact | Investigate Configuration Changes |
| Compare and recover | Compare snapshots or live state, then review a restore preflight | Compare and Restore Configuration |
| Produce evidence | Generate report packages and document coverage | Generate Reports and Review Coverage |
What Configuration Intelligence Helps You Answer
- What changed in CUCM since the approved baseline?
- Which changes present the most operational risk?
- Did several changes occur in the same maintenance window?
- Does the current live mirror still match a known-good snapshot?
- What would a selective restore change before anything is applied?
- Which object types are fully tracked, partially tracked, planned, or known gaps?
Start With Settings
Open Configuration Intelligence and select Settings. Configure the tracked object types and retention policy before you create the first baseline.