Q.850 cause codes and SIP responses
Q.850 causes come from the telephone network. Knowing which SIP response each one becomes tells you whether to try another route or stop.
Updated · By the VOS3000 Web team
Quick answer: Q.850 cause codes are the ISDN reasons a call ended, such as 16 normal clearing, 17 user busy or 34 no circuit available. RFC 3398 maps each one to a SIP response, so 17 becomes 486 and 34 becomes 503. In VOS3000 they show in the CDR Termination reason as codes up to 128, with the same names as the manual's H.323 list.
- Where you see them
- CDR Termination reason, codes up to 128
- Mapping
- RFC 3398, Q.850 to SIP
- Fail over on
- 34, 38, 41, 42, 47 (all 503)
- Do not fail over on
- 1, 17, 28 (404, 486, 484)
Where you see them in VOS3000
Every CDR has a Termination reason. Negative codes are VOS3000's own, codes from 300 to 606 are SIP responses, and codes up to 128 are Q.850 causes, usually passed on by a carrier that has a TDM or SS7 leg. The names VOS3000 uses, such as UserBusy or NoCircuitChannelAvailable, are the H.323 ReleaseComplete reasons in the manual's end-reason section. The CDR also has a Reason field with the peer's Reason header, which often carries the cause as Reason: Q.850;cause=17. Look up any code in the termination reason lookup.
Common causes and their SIP mapping
The SIP column is the mapping in RFC 3398. Carriers do not always follow it, so treat it as the usual case.
| Cause | VOS3000 name | Meaning | SIP (RFC 3398) | Routing |
|---|---|---|---|---|
| 1 | UnallocatedNumber | The number does not exist. | 404 Not Found | Stop: wrong on every route. |
| 16 | NormalCallClearing | A normal hang-up. | BYE or CANCEL | None needed. |
| 17 | UserBusy | The called user is busy. | 486 Busy Here | Stop: the user is busy everywhere. |
| 18 | NoResponse | No answer from the user's equipment. | 408 Request Timeout | Often worth one more route. |
| 19 | NoAnswer | It rang, nobody answered. | 480 Temporarily Unavailable | Normal; do not fail over. |
| 21 | CallRejected | The call was refused. | 403 Forbidden | Check caller ID and number format; then try another route. |
| 27 | DestinationOutOfOrder | The far end cannot be reached. | 502 Bad Gateway | Fail over. |
| 28 | InvalidNumberFormat | The number is incomplete or badly formatted. | 484 Address Incomplete | Stop and fix your rewrite rules. |
| 31 | NormalUnspecified | A normal ending with no detail. | 480 Temporarily Unavailable | Look at ASR before acting. |
| 34 | NoCircuitChannelAvailable | No free circuit. | 503 Service Unavailable | Fail over. |
| 38 | NetworkOutOfOrder | The network is down. | 503 Service Unavailable | Fail over. |
| 41 | TemporaryFailure | A short-term fault. | 503 Service Unavailable | Fail over. |
| 42 | Congestion | Switching equipment is congested. | 503 Service Unavailable | Fail over. |
| 47 | ResourceUnavailable | A resource ran out. | 503 Service Unavailable | Fail over. |
| 58 | BearerCapNotPresentlyAvailable | The requested media or bearer is not available. | 503 Service Unavailable | Check codecs, then fail over. |
| 88 | IncompatibleDestination | The destination cannot take this type of call. | 503 Service Unavailable | Check codecs and fax settings. |
| 102 | TimerExpiry | A protocol timer ran out. | 504 Server Time-out | Fail over; ask the carrier. |
| 127 | InterworkingUnspecified | A fault between networks, no detail. | 500 Server Internal Error | Fail over; ask the carrier. |
In the other direction RFC 3398 maps 404 to 1, 486 to 17, 480 to 18, 408 to 102 and 503 to 41, so a cause you see may already have passed through SIP once.
Using causes for failover
When a routing gateway fails a call, VOS3000 tries the next one; see routing order. On the routing gateway, Stop switching response code lists the responses that should end the search. Put the answers that are true on every route there, such as 404, 484 and 486, and leave 503 and 502 out so congestion moves the call on. For a long run of 34 or 42 from one carrier, look at its capacity and the Line limit you set.
Passing causes on
The Reason setting on a routing gateway adds a Reason header to the hang-up signalling, or passes on the one received. On the mapping gateway, Replace failed reason picks the error the customer receives for each termination reason. For VOS3000's own codes, see termination reasons.
Questions about this topic
What is a Q.850 cause code?
A number from 0 to 127, defined by the ITU-T in Q.850, that says why a call ended in ISDN and SS7 networks. SIP carries it in a Reason header or maps it to a SIP response.
Which RFC maps Q.850 to SIP?
RFC 3398, which covers ISUP and SIP interworking. It maps each cause to a SIP response, for example 17 to 486 Busy Here and 34 to 503 Service Unavailable.
Why do I see 16 on calls that never connected?
Some carriers send 16 NormalCallClearing for any ending. Check the call duration and the SIP response before trusting the cause.
Can VOS3000 pass the Q.850 cause on to my customer?
Yes. The Reason setting on a routing gateway adds or passes on the Reason header in the hang-up signalling, and Replace failed reason on the mapping gateway chooses which error the customer gets.
Run VOS3000 without the server work
Pick a VOS3000 server hosted by us, or have us install VOS3000 on your own server. VOS3000 Web and the Android app come with it.
Keep reading
All termination reasons
Every VOS3000 end reason code with what it means, plus SIP and Q.850 codes.
Termination reason lookup
Type a code like -55 or 486, or a name, and see what it means.
Calls failing: 403, 404, 408, 503 and -69
What the common SIP errors and VOS3000 reasons mean, and where to look first.
Routing order and LCR
How VOS3000 sorts routing gateways: prefix, priority, ASR, lowest rate, and when it fails over.