Call Detail Records (CDR)
The Inbound CDR page provides granular, transaction-level log data for all incoming call sessions. Network operations, engineering, and billing teams use this page to inspect raw session records, audit call completion rates, analyze traffic patterns, and reconcile usage fees.
Filtering and Querying CDRs
| Filter | Description |
|---|
| Date & Time Range | Define custom start and end timestamps to isolate call traffic within specific operational windows. |
| Container / Entity | Limit results to traffic associated with specific containers or client entities. |
| Caller ID (ANI) / Destination (DNIS) | Search records by originating phone number or dialed target DID. |
| SIP Response Code | Filter logs by protocol status (e.g., 200 OK, 404 Not Found, 503 Service Unavailable) to isolate routing or carrier failures. |
| STIR/SHAKEN Attestation | Filter by caller identity verification level (Full [A], Partial [B], Gateway [C]). |
CDR Data Fields
| Field | Description |
|---|
| Call ID / Session GUID | Unique global identifier assigned to the inbound SIP call leg. |
| Start / End Time | Precise UTC timestamps marking call initiation, connection, and termination. |
| Originating Number (ANI) | Calling party’s phone number. |
| Destination Number (DNIS) | Dialed inbound phone number assigned within your account. |
| Duration | Total call session duration formatted in seconds or minutes. |
| SIP Status & Reason | Final SIP response status code and standard protocol release cause (e.g., 200 OK / NORMAL_CLEARING). |
| Attestation Level | Verified STIR/SHAKEN identity level assigned to the incoming caller ID. |
| Rate & Billed Cost | Origination rating tiers and total calculated cost for the call session. |
Available Actions
- View Session Diagnostics: Access raw SIP headers, ladder diagrams, and packet-level tracing for technical troubleshooting.
- Export CDRs: Export filtered CDR datasets in CSV or JSON format for offline billing analysis and automated reporting pipelines.