VoIP.info Device category

Analog telephone adapters and FXS gateways

Choose FXS port count, analog electrical behavior, SIP identity, power and failure handling before preserving telephone-side devices on an IP service.

Reviewed 2026-09-27Current Grandstream ATA and FXS-gateway catalogues plus exact-model documentation reviewed September 27, 2026; no adapter, gateway, analog device, wiring, PBX, provider, fax or call testedIntermediateDocumentation based · not lab tested

Select the analog role before the port count

An FXS port supplies the telephone-side analog interface used by a conventional phone or other suitable subscriber device. An FXO port consumes a line supplied by a carrier or another FXS source. They can share an RJ11 shape but are not interchangeable. For preserving analog endpoints on SIP, choose an ATA or FXS gateway; for bringing retained analog carrier lines into a PBX, choose and engineer an FXO gateway.

Never connect two live line-supplying sources or reconnect building wiring until any outside-line source is isolated and the circuit is identified. Record every port's role, cable, attached device, SIP identity, caller identity and calling permissions.

Scale by failure domain, not just density

A compact ATA can serve one or a few telephone-side devices, while a dense FXS gateway can consolidate many ports. Density changes the impact of adapter, power, switch, PBX and provisioning failure. Compare required simultaneous calls and SIP-account or profile behavior with the physical port count; those numbers are not automatically equal.

For current Grandstream examples, the HT802 v2 presents two FXS ports and one 10/100 Mbps network port, the HT812 v2 adds a router and two Gigabit ports, and the GXW4216 v2 concentrates sixteen FXS interfaces. Those are architectural distinctions, not a ranking or proof of suitability.

Inventory the attached analog behavior

Identify whether each port serves a telephone, fax machine, modem-like device, door controller, alarm, lift, medical device or another interface. Confirm supported ringing load, caller-ID format, country impedance and tone settings, DTMF behavior, hook flash, answer and disconnect supervision with the exact equipment. A dial tone can be generated locally even when upstream calling is unavailable.

Treat fax and other modem-like uses as separate acceptance cases. A T.38 feature label does not establish PBX, provider or destination interoperability, and a successful short voice call does not validate a multi-page fax. Regulated, emergency and life-safety services require their approved connectivity and failure plan.

Design power, network and provisioning ownership

An ATA replaces the powered behavior people may associate with a traditional line with a chain that can include a local adapter, switch, router, PBX, WAN and provider. Document backup-power scope and duration, monitored failure signals, user instructions and recovery ownership. Do not claim lifeline behavior unless the exact hardware, analog line, wiring and test prove it.

Keep administrator access, provisioning tenant, firmware branch, configuration backup and certificate policy tied to the exact hardware generation. Similar names such as HT802 and HT802 v2 do not authorize cross-loading firmware. For used devices, confirm release from any prior management relationship as well as local reset access.

Commission every port and failure path

Test each port for idle state, ringing, answer, inbound and outbound caller identity, DTMF, hold or flash workflow where used, disconnect, a long call and authorized destinations. Reboot the endpoint and confirm the intended configuration returns. Then test approved loss cases for local power, Ethernet, switch, PBX, WAN and provider, including restoration without duplicate or stale registration.

For fax, run incoming and outgoing multi-page tests through the real service and representative destinations. Record device model, hardware revision, firmware, analog load, PBX or provider, codec or T.38 result, operator and date. No electrical, interoperability, capacity, resilience, security, availability, support-term or price result was produced for this category.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.