Documented specifications
Grandstream · Manufacturer product documentation was live at review; support term, regional stock and future availability were not established.
| Specification | Documented value |
|---|---|
| Analog interfaces | 2 FXS ports; no FXO role documented on the product page Source ↗ |
| SIP profiles | 2 Source ↗ |
| Ethernet | One 10/100 Mbps port Source ↗ |
| Provisioning | TR-069 and XML configuration files Source ↗ |
| Signaling and media mechanisms | TLS and SRTP supported; configured use and certificate validation still require verification Source ↗ |
| Fax mechanism | T.38 supported; endpoint, PBX and carrier interoperability not established Source ↗ |
| Local indicators | Power, network, phone 1 and phone 2 LEDs Source ↗ |
Unlisted fields remain unverified. Platform compatibility and remaining support life require confirmation for the exact ordered model.
Use the two FXS ports for telephone-side devices
The HT802 v2 supplies two FXS interfaces for analog telephone-side devices and presents them to SIP through two documented profiles. It is not an FXO gateway for connecting carrier-supplied analog lines. Identify every RJ11 cable and isolate building wiring from any live outside-line source before connection.
Two physical ports do not by themselves prove an accepted ringing load, simultaneous-call policy, caller-ID format or fax result. Record the attached device, required regional electrical settings, SIP identity and outbound authorization for each port.
Do not infer a faster network port from v2
Grandstream's current HT802 v2 product page specifies one 10/100 Mbps Ethernet port, the same headline speed shown on the separate HT802 page. The v2 label identifies a hardware generation; it is not evidence of Gigabit Ethernet, PoE, Wi-Fi, routing or an FXO port.
Match the chassis label and hardware generation to the firmware directory and provisioning inventory. Keep configuration, firmware and recovery material for HT802 and HT802 v2 separate even where their visible feature lists overlap.
Treat TLS, SRTP and T.38 as mechanisms
The manufacturer lists TLS, SRTP and T.38 support. Verify that the intended PBX or provider supports the exact transport and media policy, that certificate validation is configured, and that protected calls fail as intended when negotiation or trust fails. Do not describe a public-telephone or fax path as protected end to end without evidence for every segment.
For fax, test incoming and outgoing multi-page documents with the real fax devices, PBX, provider and destination types. T.38 support on the adapter does not establish carrier interoperability or an acceptable G.711 fallback.
Commission analog behavior and failure recovery
For each FXS port, test idle line state, dial tone, DTMF, ringing, answer, caller ID, hold or flash behavior where used, disconnect supervision, a long call and recovery after adapter, switch, PBX and WAN interruption. Confirm the attached load and regional impedance or cadence settings instead of copying another site's template.
An ATA needs local power and network service. Document what users should do during their loss, and do not represent the adapter as a substitute for approved alarm, lift, medical, emergency or life-safety connectivity. No analog, network, SIP, fax, security, resilience, availability or price behavior was tested for this record.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Grandstream HT802 v2 product page ↗
- Grandstream analog telephone adaptor catalogue ↗
- Grandstream firmware directory ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.
