> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get2dial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Hangup causes

> What a call's hangup cause and SIP response code actually mean, explained in plain, non-telecom language.

Every [call detail record](/reports/call-detail-records) carries a **hangup cause** (a named
reason the call ended) and, for calls that didn't complete normally, a **SIP response code**
from the carrier.

<Note>
  Hangup cause values come directly from the underlying telephony stack, which supports more
  causes than Get2Dial specifically acts on. The table below covers the causes Get2Dial's own
  dialer recognizes and classifies — you might occasionally see a cause not listed here; it's
  still a standard telephony cause, just not one Get2Dial treats specially.
</Note>

## Hangup causes Get2Dial classifies

| Cause                  | Plain meaning                                              | Get2Dial treats it as                                                             |
| ---------------------- | ---------------------------------------------------------- | --------------------------------------------------------------------------------- |
| `USER_BUSY`            | The destination was busy                                   | Busy                                                                              |
| `CALL_REJECTED`        | The destination actively rejected the call                 | Busy                                                                              |
| `NO_ANSWER`            | The destination didn't answer in time                      | No answer                                                                         |
| `NO_USER_RESPONSE`     | No response from the destination                           | No answer                                                                         |
| `ALLOTTED_TIMEOUT`     | The maximum ring time elapsed                              | No answer                                                                         |
| `ORIGINATOR_CANCEL`    | The call was cancelled before it was answered              | No answer                                                                         |
| `SUBSCRIBER_ABSENT`    | The destination wasn't reachable                           | No answer                                                                         |
| `NORMAL_CLEARING`      | The call ended normally — most answered calls end this way | Not classified as a failure                                                       |
| `NO_ROUTE_DESTINATION` | No route could reach the dialed number                     | Routing failure — see [Outbound calls fail](/troubleshooting/outbound-calls-fail) |

## SIP response codes

For calls that failed before being answered, the CDR also shows the carrier's SIP response
code.

| Range | Meaning                                                              |
| ----- | -------------------------------------------------------------------- |
| 2xx   | Success — the call was answered                                      |
| 4xx   | Client error — for example, `404` (number not found) or `486` (busy) |
| 5xx   | Server error — for example, `503` (carrier temporarily unavailable)  |
| 6xx   | Global failure — the destination refuses the call outright           |

## Related

<CardGroup cols={2}>
  <Card title="Search call detail records" href="/reports/call-detail-records" />

  <Card title="Outbound calls fail" href="/troubleshooting/outbound-calls-fail" />
</CardGroup>