VoIP.infoThe independent guide to business communications.
VoIP.info Guide

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.

Reviewed 2026-10-27Analog interface and carrier behavior vary by device, region and firmwareIntermediateDocumentation based · not lab tested

Map the connection

The analog phone connects to the ATA's FXS port. The ATA connects to the IP network and presents a SIP endpoint to the PBX or provider. Confirm power requirements, network mode and the correct port before configuring an account. Use the provider's supported account and transport settings. An ATA is an endpoint with credentials and calling permissions, so apply the same provisioning and access controls used for an IP phone.

Match an FXS port with an FXO interface
An ATA FXS port supplies an analog phone interface. A carrier analog line supplies an FXO gateway port. Both gateways connect to SIP, but their analog roles are opposite.

FXS supplies the line service; FXO uses it. These are two separate connection examples. Never connect two live FXS sources together.

Test local and remote behavior

First confirm the attached phone can ring, go off-hook and send the expected digits. Match regional tone, impedance and caller-ID behavior to the actual equipment. Then verify SIP registration or the provider's intended non-registering arrangement. Make incoming and outgoing test calls with two-way audio. Include DTMF menus, caller ID, remote hangup and local hangup. If the analog handset has message-waiting indicators or hook-flash features, check those separately; support varies by ATA and PBX configuration.

Plan power and wiring

An ATA and the network equipment supporting it need power. Do not assume the old line's power behavior survives migration. Some mixed FXS/FXO devices provide a documented lifeline relay, but its usefulness depends on a working connected analog line and the exact hardware behavior. Avoid reusing building telephone wiring until it is disconnected from any incompatible line source and tested for the intended load. For a shared analog circuit, inventory every attached device. A configuration that works for one phone may not ring an entire parallel-wired installation reliably.

Trace an analog phone through one numbered gateway port

The GXW4200 v2 diagnostic starts with hook state and the physical pair.

Validate each HT812 V2 or HT814 V2 analog port

Use the paired diagnostic to separate cable, hook state, dial tone, ringing and DTMF from SIP registration and audio.

Diagnose a missing Grandstream V2 port by model first

The HT802/HT818 V2 diagnostic freezes exact model and expected port count before cable, phone, profile or firmware changes.

Connect an analog device only to the FXS port

On HT841 and HT881, the single FXS port serves the phone or fax; the four or eight FXO ports face PSTN or a traditional PBX.

Connect the analog phone to HT813 FXS, not FXO

The HT813 reference distinguishes the powered endpoint port from the PSTN-facing line port.

Do not treat a channel row as phone validation

The AMI DAHDI diagnostic carries channel evidence across driver, wiring and analog-line boundaries.

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

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 →
Hub · Vendor-neutral endpoint workflow plus Acrobits Cloud Softphone platform provisioning documentation reviewed October 8, 2026; exact parameters and precedence remain product-, service- and deployment-specific and no device or application was tested

Phone provisioning: repeatable endpoint deployment

Build a controlled path from a newly connected phone to the right identity, firmware and calling policy.

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

Legacy analog migration: phones, alarms and modems

Inventory service dependencies before replacing an analog circuit with an IP connection.

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 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 · 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 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 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 →