voip.ms Reviews

I needed to call a US embassy this week. INTL calls are blocked on all accounts until you submit your ID to their online form. Form says they'll unlock INTL calls within 24 hours. That was Thursday. Still ignored through Wednesday, I had to go into chat but INTL calls were now clearly unlocked to make INTL calls. When I went to make the call, their servers were not configured to allow service. I'm not a novice at SIP clients and following their setup guides. The problem really was they hadn't configured routing correctly on their server. I informed them and they blamed the inbuilt Android SIP client and asked I used Zoiper. Same problem with Zoiper because they hadn't setup the routes in their server. I even sent them a screen recording and screenshots making it all unmistakable the problem was on their end. A day later, without apologizing for not acknowledging the problem was on their end and wasting a bunch of my time, they messaged back "it's possible to enable the routes to your account for the destination you've reported, however, please note that calls to this destination will have a rate of $0.34" That's interesting because their call rate sheet advertised $0.06. I say go ahead and do it because I don't expect them to lose money and I just want it working finally. They promise they've "enabled the routes." Another day later, nope, yet again they failed to actually do it. I inform them. The say they'll fix it. Another day later I try a final time. Nope still not fixed. I sign up for Google Voice which works immediately and just say they handled fixing it exceedingly poor. Their response...not an apology but suggesting I was using the incorrect dial codes which was demonstrably wrong given our correspondence and the screen recording I'd sent them.

I set up a voice.ms account yesterday and configured that account using an Obi202 today. I was running into difficulties with the configuration so-called "customer services" for support and was told that voip.ms does not recommend obi talk and I could not get configuration help other than through the receipt of a pretty technical pdf sheet that they provided a link to. When I asked which devices they do support I was told "Can't recommend a device as I'm not a user or haven't used them all". In short, the voip.ms service agents are so ill-trained they know zippo about the devices that work on the service that employs them. The alternative is that they are instructed to avoid answering. I gave up on that customer service rep (Fred) and sought the help I needed through other online forums, which I found. After configuring the service, I made my first call on the voip.ms line (which is through their Vancouver 2 exchange) to my cellphone, my cellphone indicated the incoming call was from Russia so I placed a support ticket with voip and asked two questions. The first was: What do I need to do to reflect that the call was placed from the Vancouver area, not Russia? The second was: Is voip was a Russian based service? Neither of my questions were answered by the support agent (John) but I did get some lame excuse about why Russia might be shown as the origin of the call. That excuse did not sound plausible. Of the $20 I uploaded to my voip account yesterday, $10.10 was consumed in setting up which includes a month's outgoing calls, which is pretty reasonable. However, a voip service that mistakenly indicates I'm placing calls from Russia will result in so many calls not being answered that the service is not worth having. That, along with the quite derisory quality of customer service I received, and the risk of voip.ms being a Russian based company with whatever potential security issues that might attach to that circumstance, means I'm dropping them today like a hot potato.

Been using voip.ms for 5 yrs - no issues other than an the odd re-set of carrier server and then my service is back online. Haven't had service for 2 days now. Voip.ms website for config is "this site can't be reached" on Google search. Has Voip.ms gone under/out of business? How do I get my DID number back from them? Anybody have any thoughts? SOL for the moment

I've used www.voip.ms for years with at max a dozen numbers (DIDs). They've done well the vast majority of the time until now. I recently attempted to port out a number. It’s only reasonable that voip.ms use automation as the primary means of fulfilling ports. Computer automation is FAST and I expect 99.9% of ports succeed via automation. In this case, despite having voip.ms provide me the necessary authorization info via email (matched my account records as well) and emailing it to the receiving carrier, it’s been 9 days, hours of frustration, and a dozen unsuccessful attempts. Account Name **** **** Address *** **** **** City **** State ** ZIP Code ***** No pin Account number and BTN- ********** Voip.ms assures me if only the receiving carrier would share the PON (port order number) identifier with them they'd investigate and resolve whatever the hangup is. I find it fishy voip.ms doesn't already see the PON when each port attempt takes place (it seems they're outsourcing that part of their business to another vendor and collaborate poorly) It's equally suspect as to why the receiving carrier doesn't see the PON identifier either. The receiving carrier may outsource as well. When the automation doesn’t succeed, my experience has been that voip.ms shirks assuming ownership for the problem and an effective secondary means to allowing these to succeed. The receiving carrier has been willing to conference call, chat, email chain etc. Especially because the receiving carrier could be communicating with voip.ms the very moment the request is initiated, voip.ms acknowledge and promptly resolve any hitch in the process. Voip.ms has stonewalled such reasonable efforts. It seems rotten a person should have to go so far as to contact the FCC/NPAC. I used to be an evangelist for their service. Now, I'm just desperate to get my numbers released voip.ms