dslreports logo

Review by dev_null See Profile

  • Location: New England
  • Cost: $6 per month
  • Install: about 50 days
Pricing, 6 sec increments
None recently
Trusted communications partner
Web-site:
Ease of Installation:
Call Quality:
Reliability:
Tech Support:
Value for money:

I have removed a detailed description of my initial issues because they no longer reflect the experience I have with voip.ms, who has now become my primary phone service provider. All of my key DIDs are hosted by voip.ms and I use them extensively at home and for my home office. So some of the comments below reflect that early experience, rather than anything recent.

I began using voip.ms in 2010.

Update: June 2011:

After the initial growing pains, VOIP.MS has turned into a reliable, trusted partner. Can't convince the wife to give up the landline, so I've stuck with the paygo model and use it primarily for family and home office calls. I've been very satisfied since the early issues have been resolved and have increased the scores based on my experiences.

Update: March 2013
Still use VOIP.MS for my home office line, it's been pretty solid. Recently went with VOIPO for our home line (all you can eat for 7 bucks a month). Due to a recent relocation, the wife is on the phone for an hour or two a day with the folks back in the old area, so the appeal of unlimited (within reason) at a fixed cost was attractive. Wish VOIP.MS offered the same for residential use.

Update: August 2015
After some months of trying to sort out a number of issues with VOIPO, I threw in the towel and ported my primary 617 number to voip.ms on the per-minute plan.

I've had very good service over the past 1.5 years, and now have 3 lines with them, one being my old cell phone number which I call-forward.

Update: March 2016
After moving (again), I ported another line into voip.ms from google voice; GV worked fine, but I wanted the option of LIDB for when we were calling from our new home. Use a combination of voip.ms, localphone and circlenet for outgoing calls. Cost for home line with usage and e911 is less then $6/mo (who needs a flat rate at that price?). Very consistent service, very pleased with voip.ms.

Update: June 2016
Cleaned up some of the detail of my very early experience, and find that voip.ms continues to be a trusted communication partner. The only issue I find is that sometimes the CNAM dip accuracy is a little lower than I expect; for example a landline calling from voip.ms might have the city name, with callcentric it has the correct owner name. Minor issue.

member for 21.6 years, 3498 visits, last login: a few hours ago
updated 7.7 years ago


suppafly
Premium Member
join:2009-11-27
97000

suppafly

Premium Member

Update after resolution

For the sake of clarity we would like to clear up this case, even though it is now solved:

The customer entered a port request for his number to our network. The number did port correctly and worked fine.

Customer then approached us asking to do the CNAM update. The customer was on the firm idea that there is NO US-based telephone number that cannot have the CNAM updated. Please note that CNAM can not be updated for ALL USA ratecenters, so I mentioned on a ticket that it is not the case. We can gladly find out if any DID in our stock is editable, and in this case it was not.

Since the customer was so upset, we decided to do an internal port to another provider, and we paid for the internal porting fee as a courtesy. In cases when we need to do an internal port And then request the update, there may be some delays. The customer was advised on january 25th that this could take up to 25 business days, which were up on the date today march 1st (the review here was updated before the timeframe we gave to the customer was up).

Please be aware also that CNAM updates are not something automatic. It can take usually up to 15 business days (without taking in consideration the time of an internal port) and since there are several cnam-query providers used by companies in USA, it may be possible that for some specific provider they could be still fetching unrefreshed records. That is beyond our control since each provider may refresh their CNAM database as they please, however as mentioned on the ticket we verified the national database and this CNAM IS returning properly now.

The issue when vitelity was showing up as CID name was just transitory, as this was ported internally and then the CNAM update was applied.

Thank you for your understanding

dev_null
Pithy tag line goes here.
join:2002-08-14
New England
ARRIS S33
Asus RT-AC66U B1

dev_null

Member

Re: Update after resolution

Peter has been good about staying involved in this issue. As I observed above, I was told one thing at the time of the port (regarding CNAM/LiDB) and something else after the port completed, and VOIP.MS did the right thing to solve that issue.

However, w/r/t the recent CNAM/LiDB issue, as other reviewers have noted, and I observed as well, having tech support state that "we're working on it", with no detail, is quite frustrating and does nothing to allay concerns of customers. Had customer service been more forthright (e.g., the Vitality name thing is only a day or two until your LiDB is fixed, as Peter now states above), there would have been less consternation and heartache. Rather, I was told it would be 2 more weeks before it was fixed. CS needs a bit of training me thinks.

I do want to confirm that this seems largely resolved, if that wasn't clear above, and I plan to keep VOIP.MS as a provider.