> 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/configuration/steps-to-configure-label-routing-for-group-of-dids-to-multiple-outbound-naps.md).

# Steps to configure label routing for Group of DIDs to multiple outbound NAPs

> **Applies to:** Tmedia 3.0, 3.2, 3.3; SBC 3.1, 3.3

**Steps to configure label routing for Group of DIDs to a multiple outbound NAPs :**

* The scenario is a group of the DIDs/Prefix will be sent the a multiple designated outbound NAPs in priority mode with some manipulations: E.g. DIDs/Prefix shall be sent to NAP\_A and NAP\_B with priority 1, NAP\_C with priority 2 111 222 333 444 555 666 777 888 999

So a call with called number which has any of the above prefix will be sent to NAP\_A and NAP\_B in load-sharing mode, and if both NAP\_A and NAP\_B fail, it will then sent to NAP\_C Below are the steps to configure that regarding the digitmap file and definition files:

1- Compose the digitmap file - dm.csv, simple make it as below:

![priority dm.csv](https://docs.telcobridges.com/w/images/e/e5/Priority_dm.csv.jpg)

2- Compose definition file for NAP\_A,NAP\_B and NAP\_C:

![priority df.csv](https://docs.telcobridges.com/w/images/7/75/Priority_df.csv.jpg)

3- Import the dm.csv and the definition files via "File Db" menu

![priority filedb](https://docs.telcobridges.com/w/images/8/82/Priority_filedb.jpg)

4- Associate NAP\_A, NAP\_B and NAP\_C with the created dm.csv and the definition file, and generate routes

![priority Routeset](https://docs.telcobridges.com/w/images/3/35/Priority_Routeset.jpg)

5- Verify the Routes

![priority Routes](https://docs.telcobridges.com/w/images/c/cb/Priority_Routes.jpg)

6- Activate the configuration


---

# 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/configuration/steps-to-configure-label-routing-for-group-of-dids-to-multiple-outbound-naps.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.