VoIP.infoThe independent guide to business communications.
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-10-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.

Scale from an ATA to a high-density FXS gateway

The GXW4200 v2 family guide covers 16-, 24-, 32- and 48-port mapping, profiles, hunting and firmware boundaries.

Map Grandstream V2 FXS ports before selecting density

The HT812 V2 provides two FXS ports and the HT814 V2 four, while both document two SIP profiles. Port density is not profile or call capacity.

Compare low-density and eight-port Grandstream V2 roles

The HT802 V2 and HT818 V2 both document two SIP profiles, despite very different FXS counts and network architectures.

Keep Grandstream FXO and FXS roles separate

HT841 and HT881 are PSTN-facing FXO gateways with one separate FXS port; compare the four-line and eight-line boundaries.

Use HT813 when both endpoint and line roles are required

HT813 has one device-facing FXS port and one PSTN-facing FXO port; the reference keeps those roles and routes separate.

Keep ATA and DAHDI evidence distinct

The AMI DAHDI guide distinguishes Asterisk DAHDI channels from SIP-connected ATA ports and endpoint behavior.

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.

Continue your research

Hub

IP phones

Research handsets by daily workflow, supported provisioning and documented hardware capabilities.

Explore topic →
Guide · Analog interface and carrier behavior vary by device, region and firmware

FXS vs FXO: connect the right analog roles

Understand line-supplying and line-consuming ports before choosing an ATA or analog gateway.

Read guide →
Guide · Analog interface and carrier behavior vary by device, region and firmware

Connecting an analog phone to VoIP with an ATA

Validate the local analog interface and the IP calling service as separate parts of one deployment.

Read guide →
Guide · Analog interface and carrier behavior vary by device, region and firmware

Connecting an analog line to a PBX through FXO

Plan inbound routing, line seizure and disconnect supervision for a retained analog service.

Read guide →
Guide · Analog interface and carrier behavior vary by device, region and firmware

Fax over VoIP: T.38 relay versus G.711 passthrough

Choose a fax path from end-to-end support and observed document delivery, not a codec checkbox.

Read guide →
Device reference · Grandstream exact-model HT802 V2 and HT818 V2 product pages and datasheets, current HT80x V2 and HT81x V2 administration and user guides, and firmware 1.0.15.3 release notes dated September 17, 2026 were reviewed October 24, 2026. Exact V2 model, hardware, component versions, firmware binary family, network topology, FXS port, profile, identity, registration, hunting role, analog behavior, signaling, media, fax mode, provisioning state and accepted service remain separate evidence. Published firmware and management capabilities do not prove the installed build, provider approval, successful change, compatibility, capacity or availability. No adapter, analog device, cable, line condition, network, VLAN, router, account, PBX, packet, call, fax, image, checksum, price, inventory, support entitlement or vendor response was inspected or tested

Grandstream HT802 V2: two FXS ports, single Ethernet and firmware identity

Keep two analog ports and profiles separate from the single 10/100 network interface, effective provisioning, registration, media and the HT80x V2 firmware image.

Two-port analog telephone adapter
Grandstream maintains an exact-model product page, current HT80x V2 guides and current V2 firmware records. Those records do not establish local inventory, global remaining support, provider approval or the build installed on an individual adapter.

Read guide →
Device reference · Grandstream exact-model product pages and datasheets, current HT81x V2 administration and user guides, firmware 1.0.15.3 release notes dated September 17, 2026, and the current firmware-upgrade guide were reviewed October 24, 2026. Exact V2 identity, hardware and software component versions, network role, FXS port, SIP profile, SIP identity, registration, hunting-group membership, analog electrical path, signaling, media, fax negotiation, provisioning state and completed call or fax remain separate evidence. Published firmware is not proof of the installed build, provider approval or a successful change. No adapter, analog telephone, fax device, cable, line voltage, ring cadence, caller ID, switch, router, SIP service, PBX, account, packet, call, fax, firmware image, price, availability, compatibility, support entitlement or vendor response was inspected or tested

Grandstream HT812 v2: two FXS ports, profiles and firmware boundaries

Keep two analog ports, two SIP profiles, integrated routing, registration, T.38, provisioning and the V2 firmware family as separate evidence.

Two-port analog telephone adapter with integrated router
Grandstream maintains an exact-model product page, current HT81x V2 guides and current V2 firmware records. Those records do not establish local stock, a remaining global support term, provider approval or the build installed on a particular adapter.

Read guide →
Device reference · Current Grandstream GXW4200 Series product, datasheet, user-manual, installation, FAQ, firmware, GDMS and provisioning documentation reviewed October 23, 2026; exact hardware revision, regional SKU, stock, support term, approved firmware, rollback path, PBX or provider policy, credentials, cabling, analog load, caller-ID behavior, fax path, hunt design, power, network and failover behavior remain deployment specific; no gateway, analog endpoint, cabling, RJ21 assembly, PBX, profile, credential, registration, hunt group, provisioning job, firmware image, fax, DTMF, call, media stream, power event or failover was inspected or tested

Grandstream GXW4216 v2 FXS gateway

Plan sixteen analog ports against SIP account mapping, cabling, fax tests and security configuration.

Analog FXS gateway
Manufacturer documentation available at review; exact SKU availability, remaining support period and approved firmware not established.

Read guide →
Guide · Vendor-neutral workflow; exact parameters and precedence depend on model and firmware

Phone firmware deployment and rollback planning

Upgrade a mixed endpoint estate without assuming every model or intermediate release behaves alike.

Read guide →
Device family guide · Current Grandstream GXW4200 Series product, datasheet, user-manual, installation, FAQ, firmware, GDMS and provisioning documentation reviewed October 23, 2026; exact hardware revision, regional SKU, stock, support term, approved firmware, rollback path, PBX or provider policy, credentials, cabling, analog load, caller-ID behavior, fax path, hunt design, power, network and failover behavior remain deployment specific; no gateway, analog endpoint, cabling, RJ21 assembly, PBX, profile, credential, registration, hunt group, provisioning job, firmware image, fax, DTMF, call, media stream, power event or failover was inspected or tested

Grandstream GXW4200 v2 FXS gateways: ports, profiles and firmware boundaries

Plan GXW4216, GXW4224, GXW4232 and GXW4248 v2 deployments without confusing analog ports, SIP profiles, account registration, hunting, provisioning or firmware lanes.

Read guide →
Troubleshooting · Current Grandstream GXW4200 Series product, datasheet, user-manual, installation, FAQ, firmware, GDMS and provisioning documentation reviewed October 23, 2026; exact hardware revision, regional SKU, stock, support term, approved firmware, rollback path, PBX or provider policy, credentials, cabling, analog load, caller-ID behavior, fax path, hunt design, power, network and failover behavior remain deployment specific; no gateway, analog endpoint, cabling, RJ21 assembly, PBX, profile, credential, registration, hunt group, provisioning job, firmware image, fax, DTMF, call, media stream, power event or failover was inspected or tested

Grandstream GXW4200 v2 port registers but rings wrong port or cannot call

Trace one GXW4200 v2 analog port from cabling and hook state through profile, identity, registration, hunting, PBX routing and media without treating Registered as end-to-end proof.

Read guide →
Device reference · Grandstream exact-model product pages and datasheets, current HT81x V2 administration and user guides, firmware 1.0.15.3 release notes dated September 17, 2026, and the current firmware-upgrade guide were reviewed October 24, 2026. Exact V2 identity, hardware and software component versions, network role, FXS port, SIP profile, SIP identity, registration, hunting-group membership, analog electrical path, signaling, media, fax negotiation, provisioning state and completed call or fax remain separate evidence. Published firmware is not proof of the installed build, provider approval or a successful change. No adapter, analog telephone, fax device, cable, line voltage, ring cadence, caller ID, switch, router, SIP service, PBX, account, packet, call, fax, firmware image, price, availability, compatibility, support entitlement or vendor response was inspected or tested

Grandstream HT814 v2: four FXS ports, profiles and firmware boundaries

Keep four analog ports, two SIP profiles, hunting behavior, integrated routing, fax modes and the V2 firmware family as separate evidence.

Four-port analog telephone adapter with integrated router
Grandstream maintains an exact-model product page, current HT81x V2 guides and current V2 firmware records. Those records do not establish local stock, a remaining global support term, provider approval or the build installed on a particular adapter.

Read guide →
Troubleshooting · Grandstream exact-model product pages and datasheets, current HT81x V2 administration and user guides, firmware 1.0.15.3 release notes dated September 17, 2026, and the current firmware-upgrade guide were reviewed October 24, 2026. Exact V2 identity, hardware and software component versions, network role, FXS port, SIP profile, SIP identity, registration, hunting-group membership, analog electrical path, signaling, media, fax negotiation, provisioning state and completed call or fax remain separate evidence. Published firmware is not proof of the installed build, provider approval or a successful change. No adapter, analog telephone, fax device, cable, line voltage, ring cadence, caller ID, switch, router, SIP service, PBX, account, packet, call, fax, firmware image, price, availability, compatibility, support entitlement or vendor response was inspected or tested

Grandstream HT812 V2 or HT814 V2 port registers but phone, fax or audio fails

Find the first mismatch across V2 identity, FXS port and profile mapping, hunting, analog wiring, signaling, media, fax negotiation, NAT or firmware.

Read guide →
Device reference · Grandstream exact-model HT802 V2 and HT818 V2 product pages and datasheets, current HT80x V2 and HT81x V2 administration and user guides, and firmware 1.0.15.3 release notes dated September 17, 2026 were reviewed October 24, 2026. Exact V2 model, hardware, component versions, firmware binary family, network topology, FXS port, profile, identity, registration, hunting role, analog behavior, signaling, media, fax mode, provisioning state and accepted service remain separate evidence. Published firmware and management capabilities do not prove the installed build, provider approval, successful change, compatibility, capacity or availability. No adapter, analog device, cable, line condition, network, VLAN, router, account, PBX, packet, call, fax, image, checksum, price, inventory, support entitlement or vendor response was inspected or tested

Grandstream HT818 V2: eight FXS ports, two profiles and routed topology

Keep eight analog ports distinct from two SIP profiles, dual-Gigabit routing, hunting, line-test evidence, provisioning and the HT81x V2 firmware image.

Eight-port FXS gateway with integrated NAT router
Grandstream maintains an exact-model product page, current HT81x V2 guides and current V2 firmware records. Those records do not establish local inventory, global remaining support, provider approval or the build installed on an individual gateway.

Read guide →
Troubleshooting · Grandstream exact-model HT802 V2 and HT818 V2 product pages and datasheets, current HT80x V2 and HT81x V2 administration and user guides, and firmware 1.0.15.3 release notes dated September 17, 2026 were reviewed October 24, 2026. Exact V2 model, hardware, component versions, firmware binary family, network topology, FXS port, profile, identity, registration, hunting role, analog behavior, signaling, media, fax mode, provisioning state and accepted service remain separate evidence. Published firmware and management capabilities do not prove the installed build, provider approval, successful change, compatibility, capacity or availability. No adapter, analog device, cable, line condition, network, VLAN, router, account, PBX, packet, call, fax, image, checksum, price, inventory, support entitlement or vendor response was inspected or tested

Grandstream HT802 V2 or HT818 V2 has missing ports, wrong network mode or failed firmware

Find the first mismatch in exact V2 identity, expected port count, single-interface versus routed topology, profile mapping, provisioning or firmware binary family.

Read guide →
Device reference · Grandstream exact-family HT841 and HT881 product information, datasheet, September 2026 user manual, FAQ, quick-installation and provisioning guidance, firmware 1.0.11.8 release notes dated August 14, 2026, and the UCM interconnection guide updated May 4, 2026 were reviewed October 24, 2026. Model, hardware, FXO line, FXS device, SIP profile, identity, registration, peer trunk, port mapping, PBX route, PSTN state, lifeline mode, firmware, provisioning, signaling, media, fax and accepted service remain separate evidence. Grandstream sources conflict on whether the two Ethernet ports are 10/100 or 10/100/1000; exact hardware, negotiated link and interface status must be inspected rather than inferred. Published defaults and capabilities do not prove installed configuration, compatibility, capacity, availability, provider approval or a successful change. No gateway, line, analog device, cable, network, PBX, account, packet, call, fax, outage, firmware image, checksum, price, inventory, support entitlement or vendor response was inspected or tested

Grandstream HT841: four FXO lines, one FXS port and lifeline mapping

Keep four PSTN-facing FXO ports distinct from the single FXS device port, three SIP profiles, per-port routing, bridge or router mode, lifeline relay and HT8x1 firmware state.

Four-port FXO gateway with one FXS port
Grandstream maintains a current shared product record, September 2026 manual and August 2026 firmware record. Those records do not establish installed hardware or firmware, local availability, provider approval, support entitlement or remaining service life.

Read guide →
Device reference · Grandstream exact-family HT841 and HT881 product information, datasheet, September 2026 user manual, FAQ, quick-installation and provisioning guidance, firmware 1.0.11.8 release notes dated August 14, 2026, and the UCM interconnection guide updated May 4, 2026 were reviewed October 24, 2026. Model, hardware, FXO line, FXS device, SIP profile, identity, registration, peer trunk, port mapping, PBX route, PSTN state, lifeline mode, firmware, provisioning, signaling, media, fax and accepted service remain separate evidence. Grandstream sources conflict on whether the two Ethernet ports are 10/100 or 10/100/1000; exact hardware, negotiated link and interface status must be inspected rather than inferred. Published defaults and capabilities do not prove installed configuration, compatibility, capacity, availability, provider approval or a successful change. No gateway, line, analog device, cable, network, PBX, account, packet, call, fax, outage, firmware image, checksum, price, inventory, support entitlement or vendor response was inspected or tested

Grandstream HT881: eight FXO lines, one FXS port and lifeline mapping

Keep eight PSTN-facing FXO ports distinct from the single FXS device port, three SIP profiles, per-port routing, bridge or router mode, lifeline relay and HT8x1 firmware state.

Eight-port FXO gateway with one FXS port
Grandstream maintains a current shared product record, September 2026 manual and August 2026 firmware record. Those records do not establish installed hardware or firmware, local availability, provider approval, support entitlement or remaining service life.

Read guide →
Troubleshooting · Grandstream exact-family HT841 and HT881 product information, datasheet, September 2026 user manual, FAQ, quick-installation and provisioning guidance, firmware 1.0.11.8 release notes dated August 14, 2026, and the UCM interconnection guide updated May 4, 2026 were reviewed October 24, 2026. Model, hardware, FXO line, FXS device, SIP profile, identity, registration, peer trunk, port mapping, PBX route, PSTN state, lifeline mode, firmware, provisioning, signaling, media, fax and accepted service remain separate evidence. Grandstream sources conflict on whether the two Ethernet ports are 10/100 or 10/100/1000; exact hardware, negotiated link and interface status must be inspected rather than inferred. Published defaults and capabilities do not prove installed configuration, compatibility, capacity, availability, provider approval or a successful change. No gateway, line, analog device, cable, network, PBX, account, packet, call, fax, outage, firmware image, checksum, price, inventory, support entitlement or vendor response was inspected or tested

Grandstream HT841 or HT881 routes the wrong PSTN line, loses lifeline or stops calls after firmware

Find the first mismatch in FXO versus FXS role, per-port SIP and PBX routing, bridge or router mode, physical lifeline mapping, activation state or HT8x1 firmware evidence.

Read guide →
Device reference · Grandstream exact-model HT813 product information, datasheet, user and administration guides, FAQ, quick-installation, provisioning and peer-trunk guidance, current firmware index, and firmware 1.0.19.6 release notes dated May 15, 2025 were reviewed October 24, 2026. FXS endpoint, FXO PSTN line, SIP profile, identity, registration, peer trunk, dial plan, forwarding, stage method, WAN or LAN role, NAT, lifeline relay, line supervision, firmware, signaling, media, fax and accepted service remain separate evidence. Published defaults and capabilities do not prove installed configuration, compatibility, capacity, availability, provider approval, regulatory suitability or a successful change. No adapter, analog device, PSTN line, cable, network, PBX, provider account, packet, call, fax, alarm, emergency workflow, outage, firmware image, checksum, price, inventory, support entitlement or vendor response was inspected or tested

Grandstream HT813: one FXS phone, one FXO PSTN line and lifeline routing

Keep the device-facing FXS port distinct from the PSTN-facing FXO port, two SIP profiles, WAN and LAN roles, peer or registered routing, lifeline relay and exact-model firmware state.

Hybrid ATA with one FXS port and one FXO port
Grandstream maintains a current product record, documentation set and general firmware listing for HT813. Those records do not establish installed hardware or firmware, local availability, provider approval, support entitlement or remaining service life.

Read guide →
Troubleshooting · Grandstream exact-model HT813 product information, datasheet, user and administration guides, FAQ, quick-installation, provisioning and peer-trunk guidance, current firmware index, and firmware 1.0.19.6 release notes dated May 15, 2025 were reviewed October 24, 2026. FXS endpoint, FXO PSTN line, SIP profile, identity, registration, peer trunk, dial plan, forwarding, stage method, WAN or LAN role, NAT, lifeline relay, line supervision, firmware, signaling, media, fax and accepted service remain separate evidence. Published defaults and capabilities do not prove installed configuration, compatibility, capacity, availability, provider approval, regulatory suitability or a successful change. No adapter, analog device, PSTN line, cable, network, PBX, provider account, packet, call, fax, alarm, emergency workflow, outage, firmware image, checksum, price, inventory, support entitlement or vendor response was inspected or tested

Grandstream HT813 FXS, FXO, lifeline or PSTN call route fails

Find the first mismatch in physical port role, FXS or FXO SIP profile, PSTN direction, peer or registered routing, WAN or LAN topology, lifeline relay, line supervision or exact-model firmware state.

Read guide →
Guide · Current branch-23-generated Asterisk DAHDIShowStatus, DAHDIShowChannels, DAHDIChannel, SpanAlarm and SpanAlarmClear documentation, channel fundamentals, AMI v2, event-filtering and network-security guidance were reviewed October 27, 2026; installed Asterisk and DAHDI versions, chan_dahdi availability, kernel drivers, spans, timing, signaling, hardware, carrier facilities, analog lines, manager permissions and filters, channel activity and alarm state remain deployment-specific; no PBX, FreePBX system, module, driver, card, gateway, span, channel, line, carrier circuit, configuration, manager account, credential, event stream, call, packet or audio was inspected or tested

Asterisk AMI DAHDI span and channel inventory with alarm evidence

Use DAHDIShowStatus, DAHDIShowChannels and DAHDI events as separate span, channel and change observations without turning an AMI response into proof of physical-circuit health.

Read guide →
Troubleshooting · Current branch-23-generated Asterisk DAHDIShowStatus, DAHDIShowChannels, DAHDIChannel, SpanAlarm and SpanAlarmClear documentation, channel fundamentals, AMI v2, event-filtering and network-security guidance were reviewed October 27, 2026; installed Asterisk and DAHDI versions, chan_dahdi availability, kernel drivers, spans, timing, signaling, hardware, carrier facilities, analog lines, manager permissions and filters, channel activity and alarm state remain deployment-specific; no PBX, FreePBX system, module, driver, card, gateway, span, channel, line, carrier circuit, configuration, manager account, credential, event stream, call, packet or audio was inspected or tested

Asterisk AMI DAHDI span or channel is missing, alarmed or inconsistent

Find the first divergence across version support, module and driver state, span snapshot, channel snapshot, configuration ownership, alarm events and the physical circuit.

Read guide →