Set Up Configuration Intelligence

Configure what Call Telemetry tracks and how your team receives evidence before you establish the first CUCM baseline.

Confirm Premium Access

1. Sign in to Call Telemetry.
2. Confirm that the organization has an active Premium license. Demo and Beta licenses also provide evaluation access.
3. In the navigation, open Configuration Intelligence.
4. Select Settings.

The navigation section is visible to every tier. If it carries a Premium badge, the current organization is not entitled; use the locked explanation to review the required tier without loading Config Audit data.

Choose Tracked Object Types

The Object Types section controls which CUCM configuration objects are included in future snapshots.

1. Expand Object Types.
2. Search for an object type when the list is long.
3. Enable the objects your change process needs to monitor.
4. Keep related routing objects together so comparisons have useful context. For example, track Calling Search Spaces with Route Partitions.

Changing the selection affects new snapshots. Existing snapshots retain the scope captured when they were created.

Set Scheduling Defaults

Use Scheduling to choose the default frequency and the maximum number of snapshots that can run concurrently. These defaults are applied when you create a schedule, where you can still choose the final time and timezone.

Configure Retention and Storage

Use Storage & Retention to set:

• Retention Period (days) for completed snapshots.
• Max Snapshot Size (MB) to limit an individual capture.
• Optional S3-compatible storage details when your deployment uses custom storage.

Pinning a snapshot as a baseline protects its role in comparisons, but your organization should still align retention settings with its evidence policy.

Mask Sensitive Fields

Use Masking Rules to prevent sensitive values from appearing in snapshot evidence and reports.

1. Expand Masking Rules.
2. Add a field pattern and a clear description.
3. Enable the rule.
4. Save the settings before creating the next snapshot.

Test masking rules against a non-production evidence package before relying on them for a compliance workflow.

Configure Alerts and Delivery

Use the notification and delivery sections to route change evidence to the right team.

Alert Destinations

Set the change threshold and choose the configured destinations that should receive notifications. Use a threshold that highlights meaningful activity without hiding single high-risk changes.

Webex Destinations

In Alert Destinations, select Add Destination to open the central Alert Destinations page. Select New Destination, choose a Webex channel when it is available, and test the destination before relying on it for change alerts.

SFTP Delivery

Configure the host, port, username, authentication method, and remote path. Use Test Connection before you save the delivery configuration.

Save and Verify

1. Select Save Settings.
2. Confirm that the page reports a successful save.
3. Reopen the important sections and confirm the values persisted.
4. Continue to Snapshots and create the first baseline.

Create Snapshots and Schedules →