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

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.

Reviewed 2026-10-24Grandstream 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 testedIntermediateDocumentation based · not lab tested

Freeze the wiring and first failed direction

Record printed HT813 identity, hardware, serial or MAC, installed version, WAN and LAN links, the analog device on FXS, the PSTN or PBX line on FXO, and the first failing direction. Redact credentials, telephone numbers, PINs, certificates and packet payloads.

Stop if the device and line roles do not match. Do not move or interrupt a line serving emergency, alarm, lift, medical or other safety functions without an approved plan.

Trace only the failing call flow

For FXS-to-VoIP, preserve the FXS profile, registration and dial plan. For FXS-to-PSTN, add the access code and Route Call to PSTN rule. For PSTN-to-VoIP or VoIP-to-PSTN, preserve FXO identity or peer target, listener port, ring count, forwarding, PIN and stage method.

Grandstream’s peer example uses no registration and FXO port 5062 by default; a published example must not overwrite the deployed design.

Separate WAN, LAN, management and media reachability

Record effective router or bridge behavior, physical WAN and LAN roles, address, gateway, DNS, time, management path, SIP transport and RTP path. A device behind the HT813 LAN boundary has a different NAT and DHCP dependency from the HT813 WAN interface.

Link, web access, provisioning, registration, signaling and two-way media are separate checkpoints.

Inspect line state, supervision and lifeline

Preserve FXO line voltage or status, ringing, seizure, answer, caller ID and disconnect behavior with qualified tools and authorization. For lifeline, verify the intended phone is on FXS and the intended line on FXO, then compare normal-power and approved failure behavior.

Do not infer safe emergency or alarm operation from an ordinary call or a documented relay.

Reconcile configuration order and firmware evidence

Confirm exact model, current 1.0.19.6 listing, ht813fw.bin filename, May 15, 2025 release record and published MD5 before an authorized change. Check whether device-specific, model-specific or global provisioning supplied the effective value, and preserve resync, transfer, reboot and installed state.

Publication, checksum, download, restart and reachable management each stop short of proving the failed call path.

Retest the original symptom and adjacent boundary

After one authorized correction, repeat the original direction for line selection, ringing, caller ID, digits, answer, two-way audio and disconnect. Then test the adjacent FXS or FXO boundary, restart persistence, intended lifeline route and any required fax negotiation without expanding the result to untested services.

No adapter, line, PBX, call, packet, fax, outage or firmware action was tested for this diagnostic.

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

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

Grandstream phones

Evaluate Grandstream desk, cordless, analog and facility endpoints by exact model, operational role and supported management path.

Explore topic →
Device category · Current 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 tested

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.

Read guide →
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 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

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

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

NAT for VoIP: signaling and media addresses

Map each translation boundary and compare advertised destinations with reachable addresses.

Read guide →
Guide

Voice VLANs

Separate phone traffic operationally while keeping routing, security and QoS responsibilities explicit.

Read guide →
Guide · Wireshark 4.x / current upstream tool documentation; inspect installed versions

VoIP packet-capture methodology

Select interfaces, time windows and paired capture points that distinguish network loss from missing evidence.

Read guide →
Hub

VoIP troubleshooting

Use symptoms and evidence to isolate registration, routing, media and device faults.

Explore topic →