came over from Voipo and got my # ported on the 8th. i followed instructions and used my main account. I registered, got a dial tone, echo test failed. my call forwarding was working for my DID. but my ATA connected phone didn’t ring. So no inbound/outbound calls worked. I then moved to a sub-account. same results. i opened a ticket and response was slow at first, but then it picked up and they did a good job helping me, even called me up and worked with me. But nothing was ever solved. I updated the firmware, tried replacing cables etc. Switched from UDP to TCP, etc. Always the same…i have a dial tone. but dialing *xx, 4443 or any number I just hear static. my incoming calls are just going to my cell phone. Support says they can see my ATA is receiving and connecting to them (which makes sense because it is registering). I’m using T-Mobile 5G > netgear router > Ht702.
At this point, support just suggested an Ht802. That doesn’t really bother me, since this device is over 10 years old. Although I wasted a lot of my summer trying to figure this out. (With Voipo I changed Providers/Routers multiple times and it was always plug and play) But as a person who knows a little about computers, knowing the issue is driving me crazy.
I was wondering if my router can log data regarding an inbound call and show me what the ATA is seeing? I am 50/50 on finding another service, or buying a new ATA now.
I’d probably stay with voip,ms and get the HT802, if I were you. I ended up using a HT814 because I wanted additional analog extensions. But if you only need to have one or two analog lines the HT802 will work.
I appreciated the “plug and play” nature of voipo, even though that meant limits on what could be done with their service. I did not like the limited nature of their plug and play environment. I used their softphone to have access to my home number on vacation but otherwise it was just an analog service delivered via a proprietary set up.
If you’re not planning on going beyond an analog phone (or multiple) connected to a single line there are plug and play providers. I would check to make sure there were not any fees for porting in or out your number.
Congratulations on getting the HT702 to register on voip.ms … many people have not made it that far. As you say, it is old equipment.
I just ordered an HT802 over the internet for $30. Hopefully the problem will go away. I just like the convenience of phones all over the house, so a cordless phone with the base system connected to an ATA is all I care about. My voice mails get emailed to me, so I get them to my cell. Voip.ms will give me everything I need, and mostly likely even less expensive than Voipo.
But I have to admit, I would love to know the technical reason one person’s ht702 works and another person’s doesn’t. But when I saw the firmware I had was the 2012 version and the newest update is 2018…I can accept update the hardware for 30 bucks.
Got an ht802 and configured it and it registered. I have the exact same behaviors. After I register, inbound calls do not ring my phone. (They are forwarded to my cellphone by VOIP.MS). Outbound calls do not work. I can dial but nothing happens. I do have a dial tone.
I feel like now I should have jumped the Voip.ms ship last week. I’m 21 days fiddling around with this.
Try switching your VOIP.MS account (or sub account) to TLS. See the attached image for instructions. This solved this problem for me when using T-Mobile 5G internet, which apparently blocks non-TLS connections for VOIP.MS. Your 702 and the two ATAs that I mention in the image are pretty similar, so these instructions should work for yours. After making the changes in the ATA, reboot it.
@aleccler. You are the man. I switched from UDP to TLS and boom….the echo test worked. I called my cell phone from my DID. I called my DID from my cell phone. For me it appears that I only needed to switch to TLS from UDP on my HT802 and then to switch the setting on my VOIP.ms subaccount to encrypted = yes. Thanks for the help!
I had my HT814 (4 jack version of the 802) working without TLS then I decided to add the additional security. I also have Grandstream desktop phones so I use the 814 for a few analog extensions (such as a garage where I wanted a more rugged phone and the basement where I wanted more than one physical phone on the same extension.
Ok, finally got my HT702 to work. 1st, I updated the firmware, but don’t know if that matters. I found on their site, if you download the release notes, it is a zip file including the firmware that you can upload to the HT702.
2nd, I found when the HT702 doesn’t like the password or maybe the combination, it leaves **** in the password field, but if it likes them, it leaves the field blank.
I figured it couldn’t handle special characters in the password field. Nope.
Believe it or not, it didn’t like mu sub account name! Mine was …_HT702, and by creating a new sub acct as …_ATA, it all worked. Yes, seriously.
So, change your sub account name and fet away from whatever this weird bug is. My HT702 is now working..
Another TLS success story. 