PBXDom logo PBXDom

FROM RAW FILES TO CLEAR EVIDENCE

Cisco CDR analyzer.Find the record.Understand the call.

Search your CUCM call records, understand the fields and take the evidence with you.

  • Combine files and spot duplicate records.
  • Find numbers, devices, timestamps and causes.
  • Inspect the source. Export what matters.

Free. No signup. Your call data stays in the isolated workspace in this tab.

Just need to convert a timestamp? →
01 / OPEN

Bring the original export.

Select CUCM CDR text or CSV files, preferably with their field-name header. Headerless and damaged files can be recovered with explicit import notes; always review the field mapping.

02 / INVESTIGATE

Follow the evidence.

Search a number, narrow the time window and inspect a record. Original fields and source lines stay available throughout.

03 / TAKE IT WITH YOU

Export your findings.

Download filtered rows, raw fields or a single record’s evidence. No email gate and no account required.

WHEN A FILE CHECK BECOMES A DAILY JOB

Keep your Cisco reporting running.

This tool examines the files you select. PBXDom collects supported Cisco call records continuously for call history and reporting.

Check Cisco reporting compatibility →

Know what the records can tell you.

Is a record the same as a customer call?

No. Transfers and other call features can produce several records. A zero connection timestamp describes that record; it does not prove that nobody answered elsewhere. Related call IDs are investigation candidates, not a verified end-to-end journey.

Which files can I open?

Uncompressed UTF-8 CUCM CDR files with column names, including extensionless billing exports and compatible CSV subsets. Column order can vary. Start with the synthetic example to see the format. CMR audio diagnostics, CUBE exports, ZIP archives, Excel workbooks and formatted CAR report layouts are not supported. The limit is 20 files, 10 MB and 25,000 data rows per batch.

What happens to my data?

Parsing, filtering and downloads run inside a sandboxed workspace. Its network connections and access to the surrounding page are blocked. It does not store call records in browser storage. Clear data removes the working dataset; downloaded files remain on your device. The surrounding website measures coarse actions such as opening the sample or exporting, without filenames, searches, numbers or record contents.

Can this diagnose audio quality, fraud or missed revenue?

Not from CDR records alone. The tool shows record evidence and data inconsistencies. It does not infer MOS, customer intent, financial loss, complete call paths or your dial plan. Cause codes describe recorded clearing conditions and may need signaling traces for a root-cause diagnosis.

How are timestamps, duplicates and exports handled?

CUCM timestamps are interpreted as UTC seconds. Choose a display time zone for date-specific offsets; time filters always use UTC. Exact duplicates compare all field names and values, independently of column order. They remain available but are excluded from results by default. CSV downloads escape formula-like values for spreadsheets; the JSON evidence download preserves the original field values.

Interpretation references: Cisco record format · Cisco field definitions · Cisco collection setup