# TA100/200 FXS Gateway Integration Guide

An FXS gateway lets you keep traditional analog equipment (desk phones, fax machines, door phones, overhead paging adapters, and similar devices) in service while still running everything through your Cloud Voice phone system. This guide uses a worked example to show how a TA100/200 FXS gateway registers to Cloud Voice as a trunk, so the analog phones plugged into it can place and receive calls like any other extension.

:::note[What the jargon means]
- **FXS** (Foreign Exchange Station) is the port type that supplies dial tone and ringing voltage to an analog device. The TA100/200 is an FXS gateway: you plug analog phones and fax machines directly into its FXS ports.
- **FXO** (Foreign Exchange Office) is the opposite port type, which connects to an incoming analog phone line. The TA100/200 does not use FXO, so do not confuse it with an FXO model.
- **PBX** (Private Branch Exchange) is the phone system itself. In this guide the PBX is your hosted Cloud Voice platform.
- **Trunk** is a connection that carries calls between the PBX and another system. Here the gateway registers to Cloud Voice as a trunk, and each analog phone behind it behaves like a Cloud Voice extension.
:::

:::caution[Analog phones and emergency (E911) calling]
Analog devices behind a gateway do not automatically report a street address for 911. Before you put an analog phone into daily use, confirm that emergency calling and the correct dispatchable location are configured for the extension or trunk it uses. If this step is skipped, a 911 call from that phone may reach the wrong dispatch center or none at all.
:::

## Test environment

The steps in this guide were validated against the setup below. Your firmware versions and network addresses will differ, so treat these values as a reference for the role each device plays rather than settings to copy.

![Cloud Voice, network topology linking a TA100/200 FXS gateway and its analog phones to the hosted phone system](/images/pbx/ta100-integration-pce.png)

| Equipment | Firmware version | IP address / domain name |
|-----------|------------------|--------------------------|
| Cloud Voice | 84.14.0.24 | cloudvoice.example.com |
| TA100/200 FXS Gateway | 44.19.0.30 | 192.168.28.46 |

:::note
The Cloud Voice side is reached by a domain name (its hosted address), while the gateway sits on your local network and is reached by a private IP address. The gateway must have working outbound internet access to register to Cloud Voice.
:::

## In this guide

Complete these topics in order. Each one builds on the previous, so calling will not work end to end until all three are done.

1. [Connect Cloud Voice and the TA100/200 FXS gateway](/pbx/integrations/cloud-voice-ta100-ta200/connect-cloud-voice-p-series-cloud-edition-and-cloud-voice-ta100-ta200-fxs-gateway/): pair the gateway with the PBX so you can extend one or more analog phones. This registers the gateway as a trunk and is the prerequisite for the two routing steps below.
2. [Make outbound calls from an analog phone connected to the gateway](/pbx/integrations/cloud-voice-ta100-ta200/make-outbound-calls-from-an-analog-phone-connected-to-cloud-voice-ta100-ta200-fxs-gateway/): add an outbound route so analog users can dial out over a PBX trunk.
3. [Receive inbound calls on an analog phone connected to the gateway](/pbx/integrations/cloud-voice-ta100-ta200/receive-inbound-calls-on-an-analog-phone-connected-to-cloud-voice-ta100-ta200-fxs-gateway/): add an inbound route so calls arriving on a PBX trunk ring the connected analog phone.

:::tip
Do the outbound and inbound steps as a matched pair. A phone that can only dial out, or only receive, is a common sign that one of the two routes is missing or misconfigured.
:::