> 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/telecom-references/developer-reference/routing-scripts/call-diversion-options.md).

# Call Diversion Options

It's possible to control the call flow when a call diversion information is received in the alerting state.

Two fields are available: bridge\[ :diversion ] and bridge\[ :diversion\_reason ]

The internal release cause TOOLPACK\_DIVERT\_NOT\_ALLOWED is used by gateway application to terminate both legs.

```
bridge[ :diversion ] = :allowed
```

The alert message will not be analyzed and the call will be progressed. Default behavior. bridge\[ :diversion ] = :not\_allowed If the alert message indicates that the call is diverted, the call will be released no matter the In-band information to allow early media. bridge\[ :diversion ] = :not\_allowed\_w\_early\_media The call will be released If the alert message indicates that the call is diverted with in-band information to allow early media. bridge\[ :diversion\_reason ] = "\*" If the diversion is not allowed, the gateway will drop the call for any redirecting reason. bridge\[ :diversion\_reason ] = "0,1,2" or bridge\[ :diversion\_reason ] = "unknown,busy,no\_reply" If the diversion is not allowed, the redirecting reason will be analyzed and the call will only be dropped for the configured cases.

See [Redirecting number reason values](/telecom-references/developer-reference/routing-scripts.md).

![BackToMain](https://docs.telcobridges.com/w/images/1/1e/BackToMain.png)


---

# 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/telecom-references/developer-reference/routing-scripts/call-diversion-options.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.