# Incoming Call Routing

## Incoming Call Routing

Once our inbound campaign is available, we must proceed to link an available "DID" telephone number to one of the SIP trunks through which call requests would arrive with the inbound campaign in question. That is, the assignment of the number and the inbound campaign to which all calls that enter OMniLeads on said DID number will be forwarded.

<figure><img src="https://documentacion-omnileads.readthedocs.io/es/latest/_images/campaigns_in_routes.png" alt=""><figcaption></figcaption></figure>

\_Figure 1: Incoming Routes\
\
In the following figure, you can view an *incoming route* on its configuration screen:

To generate a new incoming call route, we must access the menu *Connections -> Telephony -> Incoming Routes*, where the created routes are listed and new ones can also be added.

<figure><img src="https://content.gitbook.com/content/7qGfc9c0eCArZb6QcwvW/blobs/ZmialFkJCCz4MSVmGLQg/image.png" alt=""><figcaption></figcaption></figure>

Figure 2: Incoming route parameters

* **Destination:** Specific destination to send the channels to.&#x20;
* **Destination Type:** The type of destination where the incoming calls through this route will be sent. Destination types include inbound campaigns, IVRs, time conditions, caller identification, etc.&#x20;
* **Language:** The language used for playing default system prompts over the channels entering through the route.&#x20;
* **Caller ID Prefix:** The value set in this field will appear as a prefix to the Caller ID for each call through the corresponding trunk.&#x20;
* **DID Number:** The incoming number validated as a trigger for routing the call to the selected destination according to this route.&#x20;
* **Direct**: This check allows incoming routes to be routed directly to Contact Center agents. This is a typical scenario when we connect a PBX and the internal calls require direct communication with an agent, thus avoiding going through an incoming campaign.
* **Name:** The name assigned to the route (alphanumeric without spaces).

It is important to clarify that several routes with the same destination are allowed.


---

# Agent Instructions: 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:

```
GET https://docs.omnileads.net/english/contact-campaigns/inbound-campaign/incoming-call-routing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
