# TE Gateway Integration Guide

Many sites still hand off calls over a digital E1/T1/PRI span rather than over the internet. When you want your Cloud Voice hosted PBX (Private Branch Exchange, the phone system that switches calls for your organization) to carry traffic on one of those spans, a TE-series gateway bridges the physical trunk onto the platform and presents it to the PBX as a standard SIP trunk. This guide follows a complete example that joins a TE100 gateway to Cloud Voice and extends a single E1/T1/PRI trunk onto the phone system.

:::note[What E1/T1/PRI and SIP mean]
E1 and T1 are digital trunk standards used to carry many phone calls over a single line: a T1 (North American) span carries 23 voice channels, and an E1 (European) span carries 30. PRI stands for Primary Rate Interface, the signaling that sets up and tears down those calls. SIP stands for Session Initiation Protocol, the modern voice-over-internet protocol Cloud Voice uses internally. The gateway's job is to translate between the two.
:::

## How the integration works

The gateway terminates the E1/T1/PRI span and registers to Cloud Voice. From then on the extended trunk behaves like any other trunk on the PBX: calls follow your routing rules, and the gateway simply converts between the digital span and SIP in both directions.

:::note
A TE100 gateway extends exactly one E1/T1/PRI trunk. If a site needs more digital spans, plan for additional gateway capacity rather than trying to fit extra trunks onto a single TE100.
:::

![Cloud Voice, network diagram of a TE100 gateway bridging an E1/T1/PRI span to the hosted PBX over SIP](/images/pbx/te-gateway+p-series-ce.png)

## Reference environment

Every procedure in this guide refers back to the setup below. Your firmware versions and addresses will differ, but the workflow is the same, so substitute your own values wherever they appear.

| Equipment | Firmware version | IP address / domain |
| --- | --- | --- |
| Cloud Voice | 84.10.0.30 | pbx.example.com |
| TE100 Gateway | 61.0.0.7 | 192.168.6.168 |

:::caution
The gateway and the PBX are two separate ends of the same SIP trunk. The connection settings (such as the trunk credentials and ports) must match on both sides. If they do not agree, the trunk will not register and no calls will pass.
:::

## In this guide

Work through the topics in order. The first brings the gateway and the PBX together; the remaining two set up routing so the extended trunk can carry calls in each direction.

:::tip
Finish step 1 and confirm the trunk is registered before you attempt steps 2 and 3. Outbound and inbound routes have nothing to attach to until the trunk is up.
:::

1. [Connect Cloud Voice and the TE100 Gateway](/pbx/integrations/cloud-voice-te/connect-cloud-voice-ippbx-and-cloud-voice-te100-gateway/): register the gateway with the PBX and bring up one E1/T1/PRI trunk.
2. [Make outbound calls through the extended E1/T1/PRI trunk](/pbx/integrations/cloud-voice-te/make-outbound-calls-through-the-extended-e1-t1-pri-trunk/): add the outbound route that sends calls out over the extended trunk.
3. [Receive inbound calls through the extended E1/T1/PRI trunk](/pbx/integrations/cloud-voice-te/receive-inbound-calls-through-the-extended-e1-t1-pri-trunk/): add the inbound route that delivers calls arriving on the extended trunk.

:::caution
Adding or changing an outbound route affects which trunk your calls leave on, and that includes emergency (E911) calls. After you finish step 2, place a test call to confirm normal and emergency dialing still route the way you expect.
:::