Skip to content
Phone Guides

Asterisk logs, CDR, CEL and queue_log

Choose records according to the question they answer. An application log, a call-detail record and a queue event describe different aspects of a phone call. Combining their totals without a defined model can produce misleading reports.

Source-reviewed, 18 October 2026. Prepared from the cited documentation. Reporting examples have not been independently tested by Phone Guides. Scope: Asterisk 22 concepts; backend modules, configuration and schema depend on the installation.

Match the evidence to the question

Evidence Useful question Limit to retain
General/verbose/error logs Which application or configuration step failed? Content depends on enabled log channels and levels
SIP trace What signalling did each peer send? Does not establish every media packet or application event
CDR What call-summary records did the configured backend produce? A business interaction need not equal one record
CEL Which channel-related events occurred? Requires correlation and event interpretation
queue_log What happened in a queue? Queue reporting is distinct from all call traffic

The official logging overview describes logging destinations and runtime controls. Record effective logger.conf settings, output location and rotation/access policy before asking why an event is absent from a particular file.

Interpret call summaries with a defined model

CDR data is useful for summaries, but first define what your report calls a call. Transfers, forwarding, parallel dial attempts and applications can create records that do not map one-to-one to the original caller's interaction. A billed amount from a provider is also a separate record with its own rules.

Use the official CDR documentation and the matching backend reference. Preserve raw evidence and the transformation rules behind a report. Do not silently discard additional legs as duplicates merely because the displayed caller and destination look similar.

Use events for a richer sequence

CEL records channel events rather than replacing every field in a CDR. Establish which event types and backend are configured, how timestamps are stored and which identifiers join related records. Then build a timeline appropriate to the question.

The CEL documentation describes this event-oriented source. A missing event may reflect configuration, backend failure or an incorrect query; it is not automatically proof that the event did not occur. Compare service errors and the relevant call evidence.

Keep queue measures separate

Queue records can distinguish waiting, member activity, completion and abandonment. The queue log reference defines event fields. Use those meanings instead of estimating queue wait from an arbitrary pair of general call timestamps.

Define treatment of overflow, transfers, repeat callers and calls that never enter the queue. Record timezone and date-boundary rules. An answered-call count that includes transfers can answer a different question from the number of unique callers served.

Build a private correlation record

For a single investigation, keep the time/window, originating/destination scope, relevant channel identifiers, related-call identifiers where available, and the backend record keys. Identify which system supplied each timestamp. Protect subscriber information, credentials and recordings; keep redacted incident notes separate from raw evidence with restricted access.

Use short diagnostic windows when enabling extra tracing, and turn the extra output off afterwards. Retain enough metadata to explain the evidence without logging every caller-entered secret or entire database response.

Verify reporting changes

For your own checks, choose an ordinary call, an unanswered call, a transferred call and a queue abandonment. Compare the records produced with the documented model before trusting a new aggregate report. Check backend/database errors, retention and storage limits as well as successful writes.

Related: first troubleshooting checks, queues and backup/restore. Return to Asterisk documentation.