Have you tried replacing its power adapter? I’ve read that for small electronics like this, it’s often the power adapter that goes bad first. I have two Grandstream HT802v2 that have been working fine for a year (never needed to reboot), but if they start acting up replacing the power adapter is the first thing I’ll try.
According to https:// wiki.voip.ms/article/Grandstream_HT802v2 the Grandstream ATAs are the most widely used ATAs on VoIP.ms, so they must not be too bad.
Edit. Immediately after posting this I read the post below which reports replacing a Grandstream power adapter fixed his issue.
I’m not entirely sure who actually manufactures it — it might even be produced specifically for Sandman since I can’t find a clear OEM listed anywhere. The description makes it sound like a technician’s dream, with just about every parameter configurable, and the price isn’t bad at all compared to most ATAs with similar flexibility.
I’m wondering if anyone here has hands‑on experience with this unit. Does it live up to the claims, especially in terms of advanced configuration and real‑world reliability?
I must say I do not have the best experience so far with my HT802. I power-cycle it every night to have proper functionning. I never took the time to investigate. Power adapter? I do not know. But anyway, my next step will be to buy a SIP device directly. More expensive, but more reliable. No more ATA.
@InvaderJim
“According to https:// wiki.voip.ms/article/Grandstream_HT802v2 the Grandstream ATAs are the most widely used ATAs on VoIP.ms, so they must not be too bad.”
They usually do fine with plain vanilla settings. I don’t remember them all but I tightened the security using most of the available options (TLS and more). That’s where the problems started. This thing doesn’t like TLS.
@aleclerc ATA is not the issue. Do as you please with SIP. I don’t mind having traditionnal wireless phones in the house. I’m very pleased with the HP/Poli/Obi ATA402. Twice the price of the hit and miss Grandstream but still cheaper than good SIP.
The HT802 works perfectly well with TLS. Even the previous generation HT70x. Works without flaw. In fact, it solved many call quality problems. Plain vanilla settings need tweaking to work (for example: https://wiki.voip.ms/article/Grandstream_HandyTone_802_-_HT802)
It is actually an issue I have with my HT802 device. I never had issue with my HT701, this is why I bought this HT802 when the HT701 died. But this unit is not as good. It might be a bad number. This is neertheless my experience with the product.
So your experience with the HP ATA 402 is a positive one and nice to read about.
Having traditional phones in the house is quite fine for me too. But since my set is very old, and the my HT802 ATA is not very reliable, I might just go for devices that can work without ATAs at all.
Between buying a HP ATA402, or for the same price a Grandstream DP755 base with a DP730 phone unit, today I would do the later. Bye bye ATAs!
This is not an issue related to the TLS connection. It has worked for years, days in and out.
This is something else, but I never took the time to investigate (all settings are correct).
After about 24-48 hours, sometimes 3 days, the device will think it is still connected to the servers of voip.ms, but voip.ms will say the device is disconnected.
The only way to make it works again (easily) is to reboot it.
So my simple solution was to reboot it every 24 hours.
"After about 24-48 hours, sometimes 3 days, the device will think it is still connected to the servers of voip.ms, but voip.ms will say the device is disconnected.
The only way to make it works again (easily) is to reboot it."
This is very similar to the issue I was having as soon as TLS was enabled. According to ChatGPT it is common with the HT802:
To ChatGPT: Grantstream ATA stops receiving calls after few days, rebooting it bring it back online. Any explications?
Yes — this is a fairly common symptom with the Grandstream HT802 V2 when using SIP over TLS.
If rebooting restores incoming calls, the ATA is usually losing SIP registration or the TLS session silently dies after some time.
The most likely causes are:
NAT/firewall session timeout
SIP keepalive disabled or too infrequent
TLS cipher / firmware bugs
SIP registration expiration mismatch
Memory leak or firmware instability
Several users have reported HT802v2 firmware issues specifically around TLS registration and needing periodic reboots.
What typically fixes it:
Enable SIP OPTIONS Keep Alive
Reduce registration expiration
Upgrade/downgrade firmware carefully
Disable weak TLS ciphers
Schedule periodic reboot if firmware remains unstable
TLS works fine with my HT802v2 ATAs, but TLS is another thing that can break. If HP/Poly works, then I agree that’s a good solution. I also never thought about using a straight SIP phone system and bypassing the ATAs, might look into that next time.
I have the same issue. I have tried every possible tweak that has been recommended, and the device would show as connected on my end, but voip.ms would show it as not connected. The only thing that has consistently worked for me is scheduling a reboot every morning at 3 AM. Without that, the registration eventually drops even though the ATA still thinks it is online.
So you are definitely not alone in seeing this behavior.
I updated the firmware four days ago, and so far so good. I am on a 4 days streak.
I do not know on the long run yet, but I think this might just have been an issue with the firmware I had (from 1.0.59.3 to 1.0.65.1). Crossing my fingers!
I also set up my device to auto-update by using the correct URL in the “Firmware Server Path” advanced settings page: firmware.grandstream.com.
Just maybe it can help you to? (Unless you already have this version.)
I believe there were at least two updates between the version you had and the one you have now. My HT802 was set to auto update, and I think I received the version you mentioned in mid January.
My other HT models are from the 700 series, and those are end of life, so there are no new updates for them. I used all of these devices with my prior provider without any issues, and these small problems only started after I moved to voip.ms.
My past providers offered BYOD, but they also supplied Grandstream devices and worked with Grandstream directly when issues came up. I think that is why everything always worked well. Since voip.ms does not offer ATA hardware, they likely never speak with the ATA manufacturers. Some of my devices even have a provider drop down list with about fifteen providers, but voip.ms is not listed.
Thank you for providing the manufacturer. I had never heard of FlyingVoice before. I do wonder if these units work as well as they claim. I have never had anyone report their experience with one.
