Just coming over from now-defunct VOIPO and having trouble getting my equipment (HT702) to register.
Seems pretty simple. Choose a SIP Server and provide your credentials along with some ports.
I don’t see any restrictions on my router.
What else should I check?
Steven
Have the same problem with my HT702.
Haven’t heard back from VOIP.MS support.
We need a solution.
I have the same problem with my HT702.
Hello @tothrec2, @Berto, @hmklopfenstein,
I have the same device and it works OK. You can check the following wiki page for detailed instructions for setup. If I remember correctly, it was enough to make it work. There are little settings to tweak. Also, I use TLS connection.
https://wiki.voip.ms/article/Grandstream_HandyTone_702_-_HT702
For the specific settings for TLS:
https://wiki.voip.ms/article/Call_Encryption_-_TLS/SRTP
Kind regards.
I had previously configured everything correctly based on the HT702 article.
I tried turning on TLS, but it still would not register.
I’m guessing there are some HT702’s that are not compatible.
It would be nice to hear from support on this issue, preferably with a solution, but I have yet to hear anything. I have not received an e-mail from them.
Do you have the latest firmware installed?
COnfiguration issues are, from experience, the usual culprit. (Especially with TLS, which works very well, but the details are important for it to work.)
Yes, I have the latest firmware and I’ve rechecked the settings probably 20 times.
Not sure what else to do.
I should add that I also have a Polycom VVX-301 which works fine. It connected immediately after configuring it. It’s just the Grandstream which won’t connect.
On a hunch, I figured that maybe if I create a new sub-account for the Grandstream it would work since my Polycom works with a sub-account.
So I created a sub-account for the Grandstream and it worked. It finally registered.
This seems like an issue on the VOIP.MS side which should be fixed.
If anyone is still having issues getting their Grandstream device connected, try creating a sub account and connect it to that.
Not sure what the implications of this are since the “main” account still shows unregistered.
After some testing, it appears that even though the device is now registered, I cannot receive calls.
Ugh… This whole process has been a nightmare.
I don’t see the word Firmware on the Status page. Where is it shown?
Program – 1.0.4.8 Bootloader – 1.0.0.7 Core – 1.0.4.1 Base – 1.0.4.7
The Grandstream firmware release notes shows the most recent version (from 2018) is Version 1.0.10.3
On the Advanced tab it seems to be configured to check every time it boots up.
Having pretty much the same issue as Berto - I can make outgoing calls just fine - Incoming rings and shows the caller id but hangs up as soon as I answer.
Yeah, that’s the page I used for configuration. Did you notice that the screen shots have different values than the text-based instructions?
Also, I thought TLS was an encryption method, not a connection type. Did I mis-read?
Thanks for the suggestion. I’ll give it a try (couldn’t hurt).
But my first thought is that you needed a sub-account since you’d already configured the Polycom.
Same here. Registered, but I get are busy signals, and have been through the settings 3 times.
I configured the Polycom on a sub-account first. I hadn’t tried it on the main account until recently and it doesn’t work on the main either. So, neither my Polycom or Grandstream work on the main account, but I created sub-accounts for them and they work on those. Got the DID routing set to the Grandstream sub-account.
Not sure what else to try.
I think I had this same issue - the 702 has two line out ports - try switching to the other port.
Yeah, I had to do that with voipo. But, it doesn’t make any difference except I can’t access the 502 configuration when using the LAN port.
I don’t think it has anything to do with the hardware. Neither my Grandstream or my Polycom will register on the “main” account. I had to create sub-accounts to get them to register.
My guess is that the service won’t work right (no incoming calls, or whatever) if the main account doesn’t have a registered device, even though the routing is set to one of the sub-accounts.
It’s all theory of course, but that’s all we’ve got since VOIP.MS support is non-existent.
I’ve been digging into the tech a bit and thought I’d pass along a couple notes:
SIP handles the connection
RTP (realtime transport protocol) handles the audio.
So if you are able to connect, but don’t have any audio, check for conflicts with the RTP Port you are using. For example, my Prox readers use 10000 and 100001, so I can’t use the suggested port of 10000.
Just want to add one more. Tried many times and ways, spoke with someone at sales and was supposed to have this fixed by tech support two days ago. I haven’t heard anything further.
This does not reflect well on voip.ms.