Data Gap Check

Open Data Gap Check in the sidebar. Select a period of up to 31 days and a quiet-interval threshold, then select Check indexed calls. The check is manual and runs in a separate read-only worker; it does not continuously scan the call database. Only one check runs at a time.

Horizontal timelines

Daily bars run from 00:00 to 24:00 in your browser's local time zone. Blue segments contain indexed calls. Muted red segments mark possible quiet intervals, grey means no indexed calls, and striped sections are unverified or outside the selected period. Select a segment to see its exact times and details.

Cluster activity combines calls across managers. Individual manager timelines provide context; inactivity on a backup node is not itself an alert about missing files.

Filename evidence

Separate findings distinguish sequence discontinuities, resets, failed imports, pending imports, duplicate receipts and conflicting recorded hashes. Findings show available filenames and their confidence/category. Local retention, selective imports and source behaviour can explain missing sequence values. A failed import does not alone establish corrupt source data.

Verify node roles

An administrator can assign discovered filename nodes as primary, backup, excluded or unverified and configure thresholds. Map a Call Manager ID only after verifying it: a filename node ID is not automatically the same as the Call Manager ID in call records. Backup, excluded and unverified nodes do not generate per-node inactivity alerts.

These checks do not certify completeness and never repair, reimport or delete records automatically. Verify candidates against CUCM and operational context before drawing conclusions.