# Make Outbound Calls through the Extended E1/T1/PRI Trunk

With Cloud Voice connected to a TE100 gateway, the gateway's E1/T1/PRI trunk (a digital line that carries multiple voice channels) becomes an additional path for placing external calls. Routing does not happen automatically, though: you add an outbound route on the Cloud Voice side to hand calls off to the gateway, and a second route on the gateway to forward those calls onto the digital trunk. This page walks through both, along with mapping caller IDs to extensions and confirming the setup with a test call.

This guide assumes the SIP (Session Initiation Protocol, the signaling used to set up calls) account trunk between Cloud Voice and the gateway is already in place.

## Scenario

The steps below follow this example layout, where Cloud Voice extensions reach the outside world through the gateway's E1/T1/PRI trunk.

![Cloud Voice, outbound call flow from a PBX extension across the SIP link to the gateway and out over the E1/T1/PRI trunk](/images/pbx/te-gateway+p-series-make-calls-ce.png)

## Step 1: Add an outbound route on Cloud Voice

Create a route that sends calls from your extensions toward the gateway.

1. Sign in to the Cloud Voice portal and go to **Call Control > Outbound Route**, then click **Add**.
2. Configure these fields and leave the rest at their defaults:
   - **Name**: A label that identifies the route.
   - **Dial Pattern**: Define how dialed digits are matched. In this example, set **Pattern** to `X.` so users dial destination numbers exactly as they normally would.

     :::note
     In a dial pattern, `X` matches any single digit `0`-`9` and the trailing dot (`.`) matches one or more additional digits. So `X.` is a catch-all that matches any number the user dials, with no digits added or stripped.
     :::
   - **Trunk**: Choose the SIP account trunk that connects to the gateway. This example uses the trunk named `Connect-to-TE100-Gateway`.

     ![Outbound route with the gateway SIP account trunk selected as its trunk](/images/pbx/p-cloud-edition-outbound-route-te100.png)
   - **Extension / Extension Group**: Add the extensions allowed to dial out through this route. This example adds every extension.

     ![All extensions added to the outbound route's permitted list](/images/pbx/p560-outbound-route-extension.png)
3. Click **Save**, then **Apply**.

:::danger
A catch-all `X.` pattern also matches emergency numbers (such as 911), so those calls will route out the gateway's E1/T1/PRI trunk. Before relying on this route, confirm that emergency calls placed over that trunk reach the correct emergency service with the right location information. If they do not, callers may not be able to reach help in an emergency.
:::

## Step 2: Bind DOD numbers to extensions on Cloud Voice

Direct Outward Dialing (DOD) numbers let you tie a specific outbound caller ID to each extension, so the called party sees who is actually calling. Configure them on the trunk that reaches the gateway.

1. Go to **Extension and Trunk > Trunk** and edit the SIP account trunk connected to the gateway.
2. Open the **Outbound Caller ID** tab.
3. In the **Outbound Caller ID List** section, click **Add**, fill in the fields below, then click **Confirm**:
   - **Create Method**: Select **Outbound Caller ID Range**.
   - **Outbound Caller ID Range**: Set `505525301-505525302`.
   - **Extension Range**: Set `2001-2002`.

   ![Outbound caller ID range mapped to a matching extension range on the trunk](/images/pbx/outbound-caller-id-range.png)
4. Click **Save**, then **Apply**.

:::caution
The two ranges pair up in order, so give them the same number of entries. Here `505525301` maps to extension `2001` and `505525302` maps to `2002`. If the caller ID range is shorter than the extension range, the extra extensions get no DOD number and fall back to the trunk's default caller ID.
:::

## Step 3: Add an outbound route on the TE100 gateway

The gateway needs its own route to accept calls arriving from Cloud Voice and pass them onto the E1/T1/PRI trunk.

1. Sign in to the gateway's web interface and go to **Gateway > Route Settings > Route List**, then click **Add New Route**.
2. In the dialog, configure the route:
   - **Simple Mode**: Select **Yes**.
   - **Route Name**: A label that identifies the route.
   - **Call Comes in From**: Choose the SIP trunk that connects to Cloud Voice. This example uses `Trunk--CloudVoice`.
   - **Send Call Through**: Choose the E1/T1/PRI trunk that carries the call out. This example uses `Trunk--E1Trunk1`.

   ![Gateway route sending calls from the Cloud Voice SIP trunk out over the E1 trunk](/images/pbx/te100-from-ce-route.png)

   :::caution
   **Call Comes in From** must point at the SIP trunk that actually links back to Cloud Voice, and **Send Call Through** at the physical E1/T1/PRI trunk. Pick the wrong trunk on either side and the gateway rejects the call, so nothing reaches the outside line.
   :::
3. Click **Save**, then **Apply Changes**.

:::note
Changes on the gateway do not take effect until you click **Apply Changes**, which is a separate action from **Save**. If a test call fails, check that you applied the changes on both the gateway and Cloud Voice.
:::

## Step 4: Place a test call

Dial an external number from a Cloud Voice extension to confirm the path works. For example, extension `2001` calls `1588035242`: the destination rings, and it shows the bound caller ID `505525301`.

:::tip
Seeing `505525301` (and not a different number) at the far end confirms the DOD binding from Step 2 is working. If the wrong caller ID shows, revisit the caller ID and extension ranges on the trunk.
:::