> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/operations-and-support/troubleshooting/how-to/termination-cause-codes.md).

# Termination cause codes

Termination cause code reference: the mapping table between SS7 (Q.850) and SIP response codes, showing which code to use to drop a call and which to forward it.

### General Configuration

When configuring [termination cause codes](/tmedia-documentation/operations-and-support/troubleshooting/how-to/termination-cause-codes.md), use the following table as a guide. The *Drop* column represents codes to use when redirection contents should be dropped and the call should be terminated with the specified code. The *Forward* column represents codes to use when redirection contents should be forwarded to the incoming leg with the specified code. If the redirection requests must be processed, the codes are not used.

| Code | Drop | Drop | Forward | Forward |
| ---- | ---- | ---- | ------- | ------- |
| Code | SS7  | SIP  | SS7     | SIP     |
| 14   | 21   | 603  | 14      | 300     |
| 22   | 21   | 410  | 22      | 301     |
| 23   | 21   | 410  | 23      | 302     |
| 300  | 21   | 603  | 23      | 300     |
| 301  | 21   | 410  | 22      | 301     |
| 302  | 21   | 410  | 23      | 302     |
| 305  | 21   | 603  | 23      | 305     |
| 380  | 21   | 603  | 23      | 380     |

For each redirection cause code, choose **Process** to let the routing scripts process the redirection. Choose **Stop** to drop calls when receiving a redirection and use the above table to specify if the redirection contents should be dropped.

**To Modify a reason cause code:**

1- Click **Profiles** in the navigation panel.

![Configure ReasonCause 0](https://docs.telcobridges.com/w/images/a/a5/Configure_ReasonCause_0.png)

2- Select a profile:

![Configure ReasonCause 1](https://docs.telcobridges.com/w/images/a/af/Configure_ReasonCause_1.png)

3- Click **Edit Reason Cause Mapping**:

![Configure ReasonCause 2](https://docs.telcobridges.com/w/images/f/f4/Configure_ReasonCause_2.png)

4- Select the reason cause that you wish to create:

![Configure ReasonCause 3](https://docs.telcobridges.com/w/images/4/4f/Configure_ReasonCause_3.png)

5- Configure the reason cause values

* Click **Create**

![Configure ReasonCause 4](https://docs.telcobridges.com/w/images/9/97/Configure_ReasonCause_4.png)

### Complete list of Reason Cause mapping between the protocols:

[Reason Cause list in csv](https://docs.telcobridges.com/w/images/7/7e/Reason_Cause.xlsx)

#### Case for the 603 DECLINE and 200 TOOLPACK NORMAL

The TOOLPACK\_NORMAL reason code is mapped to the 603\_DECLINE reason code. The reason for this is the following:

A SIP BYE does not include a cause code, so on a normal call terminations, TMedia will send a BYE on SIP, and internally, a 200 TOOLPACK\_NORMAL (in the logs and the CDRs). When the call terminates unexpectedly, for example after a ACM, but before a ANM, Tmedia will still send a BYE on SIP, but internally, it will log a 603 Decline (REASON\_CODE\_603\_DECLINE).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://prosbcdocs.telcobridges.com/tmedia-documentation/operations-and-support/troubleshooting/how-to/termination-cause-codes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.