A call fails

Every call carries a reason it ended the way it did. This page shows where that reason lives, how to read it, and what the most common ones mean.

Find the call

Open Overview > Calls, filter to the number, user, device or time in question, and click the row. The detail page opens with the full picture.

Call detail page General panel showing Status "NO ANSWER" and Hangupcause "1", alongside Date, Source, CallerID, Destination and Duration fields. — A call's General panel: Status is the plain-English outcome, Hangupcause is the numeric code behind it.

Status vs. Hangup Cause

Status is one of four outcomes: ANSWERED, BUSY, NO ANSWER or FAILED. Hangup Cause (on this page shown as a bare number under Hangupcause) is the specific reason underneath it — the same status can hide several different causes. The Calls list itself is often the faster place to read it, since there it's shown with its name, not just the number:

Calls list with a Hangup Cause column showing values like "16 · Normal call clearing" and "1 · Unallocated (unassigne...", next to the Status column. — The Calls list shows the cause as "code · name" — hover a truncated one for the full text.

The most common causes

These come from the network side (numbers below 128, the international Q.850 standard used by every telephone system) and from this product's own checks (numbers 200 and up). Always read the exact wording shown by the product — it's reproduced below, not paraphrased from memory.

Code	Name	What it usually means
`1`	Unallocated (unassigned) number	The dialled number is in a valid format but doesn't exist at the far end — most often a plain misdial.
`16`	Normal call clearing	Either side hung up normally after the call connected. Seen on `ANSWERED` calls — not a failure.
`17`	User busy	The destination is genuinely busy.
`19`	No answer from user (user alerted)	The destination's phone rang but nobody picked up in time.
`21`	Call rejected by Provider	The provider actively refused the call — worth a message to them with the call's time and numbers.
`34`	No circuit/channel available	No path was free to carry the call at that moment — usually temporary network congestion on the provider's side.
`127`	Interworking, unspecified	A catch-all the network uses when it has no more specific code to give.

And this product's own codes, all starting at 200 (never part of the network standard):

Code	Name	What it usually means
`201`	User is blocked	The calling customer's account is blocked. See A customer cannot call.
`203`	No rates for user	The customer's tariff has no rate for the dialled destination — nothing to charge it at, so the call is refused.
`204`	No suitable providers found	No provider in the routing plan (LCR) could take this call. See A provider is down.
`207`	Not clear who should receive call	An inbound call arrived from a provider that isn't set up as a recognised source — a configuration gap on this end, worth flagging rather than re-trying.
`211`	Low balance for user	The prepaid customer doesn't have enough balance. See A customer cannot call.
`225`	CallerID is banned	The number calling out is on a ban list and needs unbanning before it can be used again.
`902`	Quickforward DID: caller not recognized	An inbound call to a Quickforward number arrived from a caller number not registered as one of a device's CLIs.
`903`	Quickforward DID: no usable forward number	The caller was recognised, but no forward number is set up for them on that inbound number.

The full list — all codes, in both ranges — is under Statistics > Hangup causes, together with how often each one occurred over a date range:

Hangup causes statistics table with columns Code, Designation, Disposition, Calls, Share and Duration, listing entries such as 16 Normal call clearing, 901 Went to voicemail, 3 No route to destination, 903 Quickforward DID no usable forward number, 225 CallerID is banned, 201 User is blocked, 902 Quickforward DID caller not recognized. — Statistics > Hangup causes: the full reference list, with how often each code actually occurred.

When a call retried or failed over

If routing rules or a failed first attempt sent the call to a second provider, the call's detail page shows an Attempts (cause routing) table — one row per dial attempt, in order.

Attempts (cause routing) table with 2 dial legs: attempt 1 shows DIALSTATUS CONGESTION, Q.850 19 · No answer from user (user alerted), Decision failover; attempt 2 shows DIALSTATUS ANSWER, Decision done. — Attempts (cause routing): each provider tried, its DIALSTATUS, the Q.850 cause it gave back, and what the system decided to do next.

Column	Meaning
`Provider`	Which provider was tried for this attempt.
`DIALSTATUS`	Asterisk's own outcome for that one attempt (e.g. `ANSWER`, `CONGESTION`, `BUSY`, `NOANSWER`).
`Q.850`	The network cause code that specific provider returned for that attempt (from the same table above).
`Rule`	Which cause-routing rule matched, if any — see LCR: routing strategy and failover.
`Decision`	What happened next: `done` (the call ended, whether answered or not), or `failover` (moved on to the next provider).

This table only appears once at least one dial attempt was recorded; very old calls, or ones with a single straightforward attempt, may not show it.

Check

Read Status first, then the named Hangup Cause next to it in the Calls list (or the Attempts table's Q.850 column for a specific leg). Match it against the tables above; for anything not listed here, the full reference is one click away under Statistics.