Twilio Timeout: Inconsistent 'canceled' Status

Question

Problem: Inconsistent 'canceled' CallStatus in  Timeout
When an outbound call uses the timeout attribute on the <Dial> verb, Twilio waits for the called party to answer. If the caller hangs up before the call is answered, Twilio sends a StatusCallback with a CallStatus value. Although the documentation lists canceled as a possible status, real‑world tests show that this value is not always returned; many carriers deliver no-answer or failed instead.
The uncertainty makes it difficult to implement deterministic cleanup and billing logic. Developers must decide whether to rely on canceled, treat any non‑completed status as a failure, or inspect additional fields such as callDuration to infer the caller’s intent.
What status does Twilio reliably send when a caller ends the call before connection? Are there carrier‑specific differences that affect this value? How can an application reliably detect a user‑initiated hang‑up in all scenarios?

Tasadduq Burney · Answer

Determining Caller Hang-ups During 
There is no single CallStatus value that Twilio reliably sends across all carriers when a caller hangs up before a connection is established. While canceled is the intended status for user-initiated terminations during the dialing phase, carrier-level signaling often maps these disconnects to no-answer or failed.

The Cause of Status Inconsistency
The discrepancy arises because Twilio maps PSTN (Public Switched Telephone Network) disconnect codes to a simplified set of statuses. Different carriers handle the "caller hang-up" signal differently; some signal a standard disconnect, while others signal a failure to establish the session. Consequently, the StatusCallback may report no-answer even if the caller was the one to terminate the call.

Reliable Detection Strategy
To deterministically detect if a call was never answered (regardless of whether the caller hung up or the timeout expired), you should rely on a combination of CallStatus and CallDuration rather than the status string alone.

Verify CallDuration: A value of 0 confirms the call never reached the "in-progress" state.
  Group Non-Completed Statuses: Treat canceled, no-answer, and failed as a single "Unanswered" category for cleanup and billing logic.
  Ignore completed: Any call with a status of completed and a CallDuration greater than 0 was successfully connected.

Verification Steps
To map the specific behavior of your target carriers, perform the following test:

Initiate a <Dial timeout="30"> request.
  Manually terminate the call from the caller's side at the 5-second mark.
  Log the CallStatus and CallDuration received at your StatusCallback URL.
  Repeat this across different destination country codes to identify carrier-specific mapping patterns.

Required Diagnostic: To refine this recommendation, please specify if you are dialing primarily to VoIP numbers or traditional PSTN landlines, as signaling behavior differs significantly between the two.

Twilio <Dial> Timeout: Inconsistent 'canceled' Status

Problem: Inconsistent 'canceled' CallStatus in Timeout

1 answer

Determining Caller Hang-ups During

The Cause of Status Inconsistency

Reliable Detection Strategy

Verification Steps

Your perspective belongs here.

0 question comments