> 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/route-parameters-and-call-routing.md).

# Route Parameters and Call Routing

### Route parameters

All call routes may have these parameters:

* calling
* called
* nap
* remapped\_calling
* remapped\_called
* remapped\_nap
* remapped\_destination\_leg\_profile (called remapped\_profile prior to Toolpack 2.9)
* remapped\_source\_leg\_profile (called remapped\_incoming\_profile prior to Toolpack 2.9)

Example:

```
route[:remapped_nap]
```

| ![NoteIcon](https://docs.telcobridges.com/w/images/b/b6/NoteIcon.png) | You can add dynamic route attributes using the Web Portal. These attributes can be referenced by their name. For example: \*priority \*weight |
| --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |

### Routing calls toward registered users

Static routes normally choose an outbound NAP to forward the call to. It is also possible to create routes from which the outbound NAP is dynamically chosen by matching a registered user (when using [SIP registration forwarding](https://telcobridges.com/learning/session-border-controller/softphone-and-the-sbc/)).

More information can be found [here](https://telcobridges.com/learning/session-border-controller/softphone-and-the-sbc/) about the way to control the [priority of "dynamic" vs "static" routes](https://telcobridges.com/learning/session-border-controller/softphone-and-the-sbc/).

More information can be found \[\[#Registered\_Users\_Information|here]] about using routing scripts to access registered users information during call routing.

![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/route-parameters-and-call-routing.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.