VoIP.infoThe independent guide to business communications.
VoIP.info Device reference

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.

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

Documented specifications

Open IP Phone Compare →

Grandstream · 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.

HT802 V2: manufacturer-sourced facts
SpecificationDocumented value
Analog ports2 RJ11 FXS ports; physical ports are not profiles, identities, registrations or simultaneous calls Source ↗
SIP profiles2 SIP profiles through the two FXS ports; assignment and registration require per-port confirmation Source ↗
Network boundaryOne 10/100 Mbps Ethernet port; HT818 V2 dual-port routing behavior must not be copied to this model Source ↗
IndicatorsPOWER, NET, PHONE1 and PHONE2 LEDs describe device and port state, not completed calls or analog-line quality Source ↗
Fax capabilityT.38 is listed for Fax-over-IP; negotiation and successful document delivery remain separate evidence Source ↗
ProvisioningTR-069 and XML configuration are listed; fetch, apply, reboot and effective values remain separate Source ↗
Firmware binaryFirmware 1.0.15.3 names ht80xv2fw.bin for HT801 V2 and HT802 V2 Source ↗
Downgrade boundaryAfter 1.0.9.3 or later, downgrade to 1.0.7.5 or earlier is not supported because of CPU-frequency adjustments Source ↗

Unlisted fields remain unverified. Platform compatibility and remaining support life require confirmation for the exact ordered model.

Identify HT802 V2 before comparing another two-port ATA

Record the printed HT802 V2 identity, part and hardware version, serial or MAC, and the program, bootloader, core, base and CPE versions exposed by the status page. Original HT802, HT802 V2 and HT812 V2 can all appear in two-port discussions but have different network and firmware boundaries.

A current product page or release record establishes published documentation, not the installed build, local inventory, provider approval or remaining support.

Keep two ports, two profiles and account state separate

HT802 V2 exposes two FXS ports and documents two SIP profiles. Each port still needs an effective profile, SIP User ID, Authenticate ID, credential state and registration result. A dial tone, LED or working call on one port does not prove that the other independently registered or inherited the intended policy.

Map each physical port to its attached analog device, profile, identity, inbound treatment, outbound treatment and any hunting role before editing credentials.

Respect the single-interface network boundary

The HT802 V2 product and datasheet describe one 10/100 Mbps Ethernet interface. It is not the dual-Gigabit NAT-router topology documented for HT818 V2. Record switch port, link speed, VLAN source, address, gateway, DNS and NTP; do not troubleshoot a nonexistent LAN-versus-WAN port choice.

Network link, provisioning reachability, registration, signaling and bidirectional media remain separate checkpoints.

Treat LEDs and status as state hints

POWER, NET, PHONE1 and PHONE2 indicators help locate device, link and port state. A registered or off-hook indication does not measure analog voltage, ringing, cable continuity, caller-ID format, DTMF or audio. The IVR can announce the assigned address, but that does not establish SIP reachability.

For each port, preserve the status snapshot and then test the authorized analog device, cable, dial tone, inbound ring, digits, answer and two-way media in sequence.

Bind provisioning and firmware to HT80x V2

Grandstream documents TR-069, XML and several transfer protocols for provisioning and upgrades. Release 1.0.15.3 names ht80xv2fw.bin for HT801 V2 and HT802 V2; the similarly dated ht81xv2fw.bin belongs to HT812 V2, HT814 V2 and HT818 V2. File-name similarity is not model compatibility.

Preserve the requested file, response, image name, release-record checksum, apply or reboot event and effective component versions. Do not treat download or restart as success.

Accept calls and fax without hiding the downgrade limit

Grandstream lists T.38 and common analog telephony functions, but a checked option or successful registration does not prove a completed call or fax. Pilot inbound and outbound identity, ring, answer, DTMF, caller ID, two-way audio, fax negotiation when required, restart and configuration persistence.

A unit at 1.0.9.3 or later is not documented as downgradeable to 1.0.7.5 or earlier. No adapter, analog device, network, PBX, call, fax or firmware change was tested for this reference.

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

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

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 →