CDR Viewer

CDR Viewer

Add one or many CDR records as JSON and read each call as parties, timing, routing, disconnect cause and both SIP legs. Everything is read in your browser and nothing is uploaded.

Drop CDR files hereJSON from Kibana / Elasticsearch: one record, an array, a search response, or several of them. Each upload is added to the records you already loaded.
Or paste JSON (one or several records)
No records yet. Add a CDR file or paste JSON above.

About this tool

The CDR Viewer turns raw Sonus/Ribbon SBC CDR exports (JSON from Elasticsearch/Kibana) into a readable call report with troubleshooting aids. It is built for support, NOC and voice engineers who need to answer quickly: what happened to this call, which leg failed, where did it go, and was the audio good. It runs in your browser; files are read locally and nothing is uploaded.

Reading a call

  • Call summary with a one-sentence description, key facts and a ready-made ticket text
  • Findings with hints per disconnect cause: abnormal Q.850 cause, slow policy or routing, rerouting, cause differing between legs
  • Call map ladder diagram, path through the SBC, routing, timing and disconnect details
  • Start and Stop records are told apart

Troubleshooting

  • Transfers linked by SREF, decoded SREF fields, transfer timing and a Transfers tab
  • FQDN or IP per leg and an FQDN resolution box
  • Call quality: R-factor, jitter, loss, packets and bytes, codec by name, one-way audio and transcoding findings
  • Call IDs with copy buttons and a Wireshark filter for the call and its linked legs
  • Contact center parameters (icbu, icci, icct, bgid) and caller ID / PAI

Many records

  • Search and filters for outcome, direction, cause, trunk group, time, quality issues and record type
  • Table with selectable columns and CSV copy
  • Statistics by cause, direction, destination, route label, trunk group, gateway, customer and country
  • Compare two calls, notes, repeat callers, number masking and optional storage in this browser

Some field meanings are best guesses and not yet confirmed against Ribbon documentation: the SREF layout, disconnect initiator, transport codes and the contact center labels. Findings use fixed limits: R-factor below 70, jitter above 30 ms, policy server above 100 ms and routing above 1000 ms.

Version history

Current version 3.0 · 2 Nov 2026