> 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/use-cases/forward-redirection-request-to-incoming-leg.md).

# Forward redirection request to incoming leg

#### ***Applies to version(s): v2.8 and above***

In this scenario, the incoming call is sent to a SIP redirect server, which returns a 3xx message. The first contact is returned to the incoming leg while releasing the call.

![Redirect (no processing)](https://docs.telcobridges.com/w/images/b/b9/Redirect_\(no_processing\).png)

This is the call flow of such a scenario. A 302 Moved temporarily is returned from the SIP redirect server and the contact information is returned to the incoming leg. for example in ISDN, the contact number will be included in the redirection number of the RELEASE message.

![SIP Redirect callflow (stop)](https://docs.telcobridges.com/w/images/6/6e/SIP_Redirect_callflow_\(stop\).png)

| Configure Reason Cause                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Configure Routes                                                                                                                                                                                                                                                                                                                                              |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Toolpack:Modify\_NAP\_profile\_D](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/creating-profiles/README.md). You need to modify the default behavior or some reason causes: \***Profiles** -> Edit Reason Cause Mapping \*\***300 Multiple Choices**-> Route retry action -> Stop Call \*\***301 Moved Permanently**-> Route retry action -> Stop Call \*\***302 Moved Temporarily**-> Route retry action -> Stop Call Do this for all Reason Cause that will be used | Create normal routes to the redirect server: [Configure Routes](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/web-portal-2-9-call-routes-settings/README.md#static-route): \***Routes** -> Create New Static Route \*\***Name** -> To\_SIP\_Redirect\_Server \*\***NAP** -> any \*\***Remapped\_NAP** -> NAP\_SIP\_REDIRECT |

Also make sure these settings are applied: SIP -> Header Parameters -> Use legacy redirection mode \[checked] (old naming convention was: Allow Recurse)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/tmedia-documentation/use-cases/forward-redirection-request-to-incoming-leg.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.