Has an IP address, but can't ping it or open the web UI¶
Symptom: *** then 02 reads out an address such as 192.168.2.189, but pinging it or browsing to http://192.168.2.189 from another computer on the home network gets no response.
There are two causes, and often both apply at once.
Cause 1: Web access from the WAN port is disabled¶
The HT812 is a router. NET1 (the internet port) is its WAN side, and web access from that side may be disabled. Check and enable it with the voice menu:
- Dial
***on a Touch-Tone phone connected to Phone 1 or Phone 2. - Dial
12. The ATA says whether web access is enabled or disabled. - If it's disabled, press
9to enable it. - Reboot the HT812 (
***,99, then9, or unplug the power).
Ping may still get no reply after this. Use a browser to test whether the device is reachable, not ping.
Cause 2: Subnet clash with a 192.168.2.x home network¶
The HT812's own LAN side (NET2) defaults to 192.168.2.1/24. Bell Canada's Home Hub and Giga Hub routers also use 192.168.2.x for the home network.
When the home router gives the HT812's WAN port an address like 192.168.2.189, both sides of the HT812 are on 192.168.2.0/24. When a computer at, say, 192.168.2.20 sends it a request, the HT812 thinks 192.168.2.20 is on its own LAN side and sends the reply out NET2, where nothing is listening. The device has a valid address but never answers.
Fix: connect directly to NET2 and remove the clash.
- Leave NET1 connected to the home router.
- Connect a laptop to NET2 with an Ethernet cable.
- Turn off the laptop's Wi-Fi, so it isn't also on the home 192.168.2.x network.
- The laptop should get an address from the HT812. If it doesn't, set a static address of
192.168.2.50, netmask255.255.255.0, gateway192.168.2.1. - Browse to
http://192.168.2.1and log in (see Logging in). - In the network settings, choose one of:
- Bridge mode (recommended): the HT812 becomes an ordinary device on the home network, with a single layer of NAT. NET2 then acts as a pass-through port rather than a separate LAN.
- Router mode with a different LAN subnet, for example
192.168.10.1/255.255.255.0. - Apply and reboot.
- Unplug the laptop from NET2, turn its Wi-Fi back on, and get the current address from
***then02. In bridge mode the address may change after the reboot. - Browse to the new address.
Then add a DHCP reservation for the HT812 on the home router so its address stays the same.
The same clash happens with any home router that uses 192.168.2.0/24, not just Bell's.
NET2 doesn't get an address from the home router¶
That's expected. NET2 is the HT812's LAN port. In router mode it hands out addresses rather than requesting one, so a cable from the home router must go into NET1 (the internet/WAN port). NET2 is for a computer or other device you want behind the HT812, or for direct access to the web UI as described above.
The voice menu (IVR) doesn't respond¶
- The IVR is opened with
***, which needs a Touch-Tone phone. A rotary phone can't dial*, so keep a basic Touch-Tone corded phone around for setup and troubleshooting. A pulse-to-tone converter with star support also works (see Using a rotary phone today). - Dial the digits steadily. Long pauses can cause the menu to time out.
Common IVR options:
| Option | Function |
|---|---|
*** |
Open the voice menu |
02 |
Read out the current IP address |
12 |
WAN-side web access status; press 9 to enable, then reboot |
47 |
Direct IP call |
99 |
Reset/reboot menu (see Factory reset) |
Did the factory reset work?¶
Holding the reset button gives no spoken confirmation. To check:
- Hold the button for at least 7 seconds with the Ethernet cable unplugged (holding longer, such as 10 seconds, is fine).
- Afterwards, try logging in with the default password from the label. If a password you set earlier still works, the reset didn't happen.
- See Factory reset for the web UI and IVR alternatives.
Phone or connector problems¶
- Dial tone on the phone but nothing else: the phone, cord and FXS port are working. The remaining setup is network and SIP account configuration.
- A plug doesn't fit a phone's jack: it may be a handset or headset jack rather than a line jack, or the unit may be an extra-handset charger rather than a base station. See Telephone connectors.
Call problems¶
| Symptom | Likely cause |
|---|---|
| Not registered | Wrong SIP server, username or password; check the Status page |
| Can call out, phone never rings | Provider routes the number to a different account, or (VoIP.ms) the ATA's server doesn't match the DID's POP |
| Incoming calls stop after a while | NAT mapping expiring: lower Register Expiration, enable keep-alive |
| One-way or no audio | SIP ALG on the home router (turn it off), or double NAT (use bridge mode) |
| Rotary digits wrong | Dial needs cleaning/adjustment, or pulse dialing not enabled on that port |
| Can't use voicemail or phone menus on a rotary phone | Rotary phones can't send *, #, or tones during a call; use a pulse-to-tone converter |
Provider-specific checks are on each provider page, for example VoIP.ms.
Sources¶
- HT81x – Quick User Guide – Grandstream (IVR options 02, 12, 47, 99; default LAN address 192.168.2.1)
- HT8xx V2 – FAQ – Grandstream (WAN-side web access)
- HT812/HT814 Administration Guide – Grandstream
- Factory Reset Your Grandstream HT812 ATA – SpectrumVoIP