I had an HT702 and it kept de-registering every handful of days. Turned out that the device would randomly delete settings like the SIP user, or password or the server addresses. Could not figure out why it was happening so I bought a brand new HT802v2.
I followed the instructions for setup at https://wiki.voip.ms/article/Grandstream_HT802v2. The new device registered fine. I can get inbound calls just fine. BUT, I can’t dial out at all. I just get rapid beeping after entering a phone number. It never even tries to dial the number.
Is there some settings on the new HT802v2 that are defaulted that the setup instructions missed to change? I contacted support but none of the changes they suggested to do in my account have helped (like increasing my minimum international calling price per minute… huh?).
So, HT702 worked fine but it would loose random settings from FX port and de-register every few days.
Bought a new HT802V2 and it registers, gets inbound calls but can’t make any outbound calls…I am guessing there must be something in FX Port settings defaults that would need to change.
Any ideas what I can try?
Many Thanks.
UPDATE: I decided to copy the settings from HT702 instead of the ones that were listed on the HT802v2 setup page. I changed the Vcoder to be first be g722, then G729, PCMA then PCMU for all other choices. I think that did the trick…. I was now able to dial out again.
Well, I decided to copy the settings from HT702 instead of the ones that were listed on the HT802v2 setup page. I changed the Vcoder to be first be g722, then G729, PCMA then PCMU for all other choices. I think that did the trick…. I was now able to dial out again.
No idea what it does, I was just randomly trying things.
I had a similar problem with a client. Where a de-registration occurred but the HT802 did not recover from it even if all the keep-alive setting were configured.
I think that the problem was that the router/modem (all in one box) was resetting during the night when the ISP was pushing a firmware update. My theory is that the HT802 did not link the way the ethernet link, the DHCP server and the internet link were coming back up from the router/modem and the HT802 fell into a registration blackhole. In order to solve that problem, I configured a daily reboot of the HT802, scheduled after the usual ISP update time. The registration has been rock solid since then.
Another solution that I was thinking of was to put the HT802 on a separate ethernet switch. That would stabilize the ethernet link on the HT802 and would not cause a link down/up when the modem updates. In turn, that would prevent a DHCP request from the HT802 when the modem/router is not ready to respond to it because it is still booting up.
A fast busy signal when dialing may also be caused by a wrong dial plan.
I switched over to VoIP.ms when VoIPo shut down, since VoIP.ms was the provider they recommended as a replacement. My old HT702 always worked perfectly with VoIPo, but I’ve found it doesn’t behave nearly as well with VoIP.ms.
I’m still not sure every answer I’ve received is correct, but one thing I was told is that VoIPo used some kind of “media relay” or media proxy on all calls, and VoIP.ms does not. That apparently made NAT a non‑issue on VoIPo, while VoIP.ms relies on direct RTP. Because of that difference, I’ve been told the HT702 is missing a key setting that VoIP.ms expects: “Enable SIP OPTIONS keep alive.” The HT702 simply doesn’t have that option in its firmware, while the HT802v2 does.
My issues started with registration problems that never happened on VoIPo. Adding a STUN server helped — the HT702 now stays registered and can make/receive calls reliably. But then I ran into one‑way audio after a certain amount of time. Depending on the settings, the call either drops to a reorder tone after about 45 minutes, or goes silent after about an hour. I’ve been told this is because the HT702 can’t send SIP OPTIONS keep‑alive packets, so the NAT binding eventually dies.
At this point the recommendation I’m getting is to replace the HT702 with an HT802v2, since the 802v2 has the SIP OPTIONS keep‑alive feature that VoIP.ms relies on for long‑duration call stability.
Just sharing my experience in case it helps someone else who moved from VoIPo to VoIP.ms and is still using older Grandstream hardware.