My client has Voip.ms and incoming calls work but outbound calls dont work and they say it just beeps like a busy signal. Voip.ms customer support sucks alot, theres no phone number.. and their a phone company.. Irony. Theres no chat feature. So they have the worlds slowest email based support in 2025. This seems to be a common problem with this company so I was hoping someone on here experienced it before. Their “cs” keeps looking at client’s logs and keeps asking if its working because their trying place calls and have not tried trouble shooting the issue on their end.
Generally issues dialing out are related to the dial plan programmed into the phone or device connecting to voip.ms. Many of us fellow users have overcome such issues as seen in the community threads.
If you would like community assistance, it would be helpful to know how your client is connecting to voip.ms. Are they using an analog phone connected to an ATA? A VoiP phone? Is their device connected to a system at their location or is it connected to a voip.ms server?
Receiving inbound calls is good and shows that the phone/device is connected to voip.ms. That gets you past the “cannot get my device to connect” stage. And if those inbound calls are working (audio passing both ways) that gets you past most common configuration problems.
Can they reach any number such as the 4443 and 4747 test numbers? Can they reach *97/98 voicemail?
1 Like
Hey thanks for the interest, its upsetting cause I dont think people should have to help each other out when were all paying a service to do it you know. This is just a side thing for me thats usually really easy enter voip.ms not easy at all. Im trying convert ppl over to another voip company like voiply or 1 voip but until they do here we are. Most people from voipo have a HT802 because voipo handed those out and provided good CS via remote. These are simple residential setups phone (cl82257) > ATA (HT802)> router (rt-arch 13) > modem > voipms. Im sure its an easy setting, I just dont have the ability to try a bunch of troubleshooting. No outbound calls go out, just get beeps after dialing. Inbound is fine. Thanks!!
Look at the Profile setting on the 802 for “Dial Plan” … the simpler the better.
This will allow any number beginning with a digit or any number beginning with a star.
The voip.ms wiki suggests this string …which would allow any string of digits or stars
If you want to get more creative you can, but simple usually works.
I can’t help with your issue because mine is different, but I agree 100 percent that customer support is dreadful: unresponsive, uncomprehending, unprofessional, and ultimately unhelpful. I’ll spare you the details of my issue, which is still unresolved after two months, but I decided to pursue workarounds until it becomes practical to port out. I hope your problem resolves.
Add me to the list of users with this issue. Ported over from Voipo. I carefully followed the directions to reprogram my ATA for Voip.ms. Inbound calls works, but outbound always results in a busy signal. I have tried everything to reach Voip.ms for assistance but no one ever gets back to me.
Wanted to add I am having similar issues. Ported over my parents phone from voipo. Took a bit to get the HT802 box configured but I was successful. Calls worked fine until 9/15 midday. Now calls work inbound and outbound but once connected voice does not work. Power reset box does not good. Unfortunately I am not onsite so can’t dig into the config at this time, but I would be skeptical that would do any good. What would cause the HT802 box to ‘lose’ a configuration that allows calls but not voice? Until then i will wait to see if my ticket gets a response.
Hello all,
I would suggest to anyone that has sound issues (not hearing), to use a secure TLS connection if it is not the case (which would surprise me).
I have seen this behaviour many times in the past. Pakets on UPD behind a NAT and complex network infrastructures, and firewall and router not configured properly, will inevitably lead to such issues. This is complex.
The simplest solution is to use a secure TLS connection as all traffic will go through one simple crypted TCP connection and will most probably solve your problems.
https://wiki.voip.ms/article/Call_Encryption_-_TLS/SRTP
Be careful as you setup, every single detail is important for it to work. (Especially SRTP settings, often overlooked.) Check if you find instructions for you specific device.
For the HT802:
https://wiki.voip.ms/article/Grandstream_HandyTone_802_-_HT802#Call_Encryption_-_TLS.2FSRTP
Kind regards!
I agree a thousand percent - no support and I have the same issue. No way to make outgoing calls. Voip.ms suggested a couple of “solutions” in configuration. They did not work. Any suggestions would be very helpful.