CDRs & message traces

From Logs to CDRs#

The sidebar report previously named Logs is now CDRs. Its existing report URL and this guide address remain available. It contains submission, delivery and charge records for SMS and Voice ingress; use live calls and VoIP statistics for call-level operations.

Find the right records#

Open CDRs and reveal the filters. Search by client, gateway, source/destination, domain, clicked IP, submit ID, provider message ID, OTP, status, text and date range as available. Select the correct time zone before matching provider evidence.

The Today cards remain today's summary. The totals above the table follow the applied report filters, so a historical view can show records even when the Today cards are zero. To reconcile with Dashboard, match its day and time zone manually.

Read a row#

Compare client, gateway, destination, incoming text, outgoing text, clicks, timestamp and status. Expand the row for additional details such as parts, per-part price and charge.

Trace a message#

Use Trace SMPP flow to review ordered events, commands, direction, status, IDs and errors. Follow the transition from received content through transformations and provider submission to receipt handling. A queued message is not necessarily submitted; a submitted message is not necessarily delivered.

URL click events#

The click count opens related events when available. Review time, IP, country, token, changed URL, user agent and referrer according to your permissions. A repeated click is not a new sent SMS.

Exports and deletion#

CSV export uses the report filters. Review the scope before clearing a single log, filtered logs or all logs. Deleting log evidence can make later diagnosis and reconciliation harder; it is separate from sending a manual DLR.

Retention and missing data#

Event retention and CDR/report storage are different concerns. Confirm the date range, live/archive window, timezone and retention before concluding that a record was never created.