TA1600/2400/3200 FXS Gateway Integration Guide

A TA1600, TA2400, or TA3200 FXS gateway lets you keep analog equipment, desk phones, fax machines, or overhead paging units, on a modern hosted system. Each FXS port on the gateway terminates one analog line, and once the gateway is joined to Cloud Voice those lines behave like ordinary extensions on your phone system: they can dial out through your PBX trunks and take calls that arrive on them. This guide walks through a worked example so you can adapt the same steps to your own deployment.

Note

Some acronyms used throughout this guide:

• FXS (Foreign Exchange Station): the port type that supplies dial tone, ringing voltage, and power to an analog device. You plug an ordinary analog phone or fax machine straight into an FXS port.
• PBX (Private Branch Exchange): the phone system that routes calls between extensions and out to the public phone network. Here the PBX is Cloud Voice.
• SIP (Session Initiation Protocol): the signaling protocol the gateway uses to register to Cloud Voice and set up calls.

Reach for a gateway when a device only speaks analog and cannot be replaced with a network (VoIP) phone, for example a legacy fax machine, a door phone, or an overhead paging amplifier.

How the integration works

The gateway registers to Cloud Voice over SIP and bridges its analog ports to the PBX. Each analog port maps to a PBX extension. Calls still ride your Cloud Voice trunks and follow your routing rules; the gateway simply converts between the digital SIP audio and the analog line, handing the audio off to the phone plugged into each port.

Note

In the example the gateway sits on the local network with a private IP address (192.168.28.46) while Cloud Voice is reached at a public domain. The gateway makes the connection outbound to the cloud, so no inbound port forwarding is required on your firewall for the gateway to register.

Reference environment

The procedures throughout this guide were validated with the setup below. Your firmware versions and addresses will differ, but the workflow is the same.

Equipment	Firmware version	IP address / domain
Cloud Voice	84.12.0.32	pbx.example.com
TA1600/2400/3200 FXS Gateway	47.0.0.54	192.168.28.46

Caution

Analog phones reached through a gateway place emergency (911) calls out through your Cloud Voice trunk, not through a local line. Emergency services see the location and callback number registered for that trunk or extension, which may not match where the analog phone physically sits. Before you hand these phones to end users, confirm the correct E911 (Enhanced 911) address and caller ID are provisioned for each analog extension so a 911 call reaches the right dispatch center.

In this guide

Work through the topics in order. Start by joining the gateway to the PBX, then enable outbound and inbound calling for the connected analog phones.

• Connect Cloud Voice and the TA1600/2400/3200 FXS Gateway, register the gateway to Cloud Voice so its analog ports become PBX extensions.
• Make Outbound Calls from a Connected Analog Phone, add an outbound route so analog phones can dial out over a PBX trunk.
• Receive Inbound Calls on a Connected Analog Phone, add an inbound route so calls on a PBX trunk reach the analog phone.

Tip

Do not skip ahead. Outbound and inbound routing only work once the gateway is registered and its ports appear as extensions, so complete the connection topic first and confirm each analog phone gets a dial tone before moving on.