> 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/parameter-reference/routing.md). # Routing and numbering parameters Call routing, dial plans, prefixes and LNP. 23 parameters. ## A | Parameter | Description | | ------------------ | ------------------------------------------------------------------------------------------------------------------------- | | **additonal naps** | Custom columns will automatically create custom attributes in routing scripts that can be used to take routing decisions. | ## C | Parameter | Description | | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | **Call Transfer Options: Call Transfer Mode** | Indicates how to handle call transfer requests received on outgoing call legs using this profile. | | **Called** | The Called parameter is used to set a filter to which each called number of an incoming call will be compared to see if the call matches the route. | | **Calling** | The Called parameter is used to set a filter to which each calling number of an incoming call will be compared to see if the call matches the route. | | **CDR Mode** | Available choices: \*Text CDR only \*RADIUS CDR only \*Text and RADIUS CDR \*RADIUS CDR with text CDR fallback | | **CDR System Id** | Unique identifier of this system used as part of the the CDR 'Session Id' field (to make it unique across systems). | ## D | Parameter | Description | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | **Destination call leg remapped Profile** | Profile to use for the outgoing call of this route. | | **domain** | Custom columns will automatically create custom attributes in routing scripts that can be used to take routing decisions. | ## E | Parameter | Description | | ------------------------------ | ------------------------------------------------- | | **Enable periodic CDR update** | Enable periodic CDR update through call duration. | ## F | Parameter | Description | | -------------------- | ---------------------------------------- | | **File name prefix** | The prefix for grouped IRI record files. | ## N | Parameter | Description | | --------- | --------------------------------------------------------------------------------------------- | | **NAP** | The NAP parameter identifies a network access point (NAP) to be associated with a new object. | ## P | Parameter | Description | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | **Periodic CDR update time** | Delay in seconds between periodic update of CDR through call duration | | **prio** | Custom columns will automatically create custom attributes in routing scripts that can be used to take routing decisions. | ## R | Parameter | Description | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | **Remapped Called** | Remapping rule for called number (outgoing call will be made using the modified called number) | | **Remapped Calling** | Remapping rule for calling number (outgoing call will be made using the modified calling number.) | | **Remapped NAP** | The Remapped NAP parameter is used to define which outgoing NAP will be selected when a particular route is used. | | **Reverse CDR call origin** | If 'Reverse CDR call origin' is checked, CDR OriginatorName will show 'originate' for incoming call leg and 'answer' for outgoing call leg. | | **Routeset Name** | The name of the Routeset. | ## S | Parameter | Description | | ------------------------------------ | -------------------------------------------------- | | **Source call leg remapped Profile** | Profile to use for the incoming leg of this route. | ## T | Parameter | Description | | --------------------------------- | ------------------------------------------------------------------------------------- | | **Test Mode** | \* Outgoing: Generate an outgoing call that will not be subject to the routing table. | | **Translate privacy information** | Enable the SIP privacy behavior (RFC 3323). | ## U | Parameter | Description | | ----------------------------------- | ----------------------------------------------------------------------------------------------------------- | | **Use alternate anonymous address** | The "from" URI will be altered to sip:anonymous@\[gateway IP] instead of sip:. | | **Use script** | Routing script to use for routing incoming calls to outgoing calls. | --- # 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/telecom-references/parameter-reference/routing.md?ask=&goal= ``` `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.