| Review by Mango |
member for 4.4 years, 2585 visits, last login: a few hours ago
updated 359 days ago
- $15 per month
- "Multiple PoPs, BYOD, great sound quality, PAYG, lots of configuration options, Canadian CNAM."
- "Better than a landline."
Ease of Installation:
Value for money:
(ratings match consensus)
If you're a beginner, but want to gain a solid understanding of how VoIP works and have tons of professional-level features to play with, VoIP.ms is in my opinion the perfect starting point. And if this isn't your first rodeo and you already speak fluent SIP, VoIP.ms will likely be an excellent complement to - or even replacement for - your choice of SIP PBX. VoIP.ms' extensive feature list beats the vast majority of their competitors at this price point. I can set up sub accounts for as many devices as I like, I can have multiple voicemail boxes, and I can configure multiple devices to ring for incoming calls...even if they're not in the same location. I can set up an IVR to route inbound calls to the proper place. My favourite feature by far is Caller ID Filtering. I can't even remember the last time I received a call from a telemarketer. This is all in addition to audio quality that's every bit as good as a landline, and the best Caller ID Name in the industry. If this sounds good to you too, then welcome to VoIP.ms
I like having low ping time to my VoIP provider, but what is even more important is being able to switch PoPs to work around an internet routing issue. My ISP is cheap, but doesn't have the best track record for consistent internet routing and it's not uncommon for traffic from the west coast to the west coast to suddenly be routed through Washington, DC. This adds horrible latency and jitter that makes VoIP unusable, but fortunately with VoIP.ms and their unique multiple PoP setup, I can just switch PoPs and work around my ISP's problem. If I used a VoIP provider that had equipment in only one city, my only option would be to port to another provider. I am genuinely glad I don't have to port my number once or twice per year when my ISP has an issue. That said, I see people switching PoPs too often in troubleshooting. If routing and ping time are good and consistent, then playing PoP roulette is likely to "solve" your problem only by coincidence.
VoIP.ms has historically implemented a great deal of customer suggestions, however there have been few features released in the past two years. There are a some very important things that need improvement, that I think would make an already great VoIP provider even better.
- Their voicemail features would be complete with a "centralized" setup that did not require significant effort when switching between PoPs.
- Their multiple server setup would be complete (and they could possibly make the claim of 100% reliability) with automatic failover, including DNS SRV. We run a program on our Asterisk server that monitors VoIP.ms and changes our DID to a different PoP if our usual one goes down, however that's more complicated than it needs to be.
- Their call forwarding features would be complete with configurable answer confirmation.
Having said this, there are so few other VoIP providers that boast any of the features of VoIP.ms, that it's hard to argue a rating of any less than five stars.
Conclusion: thanks to VoIP.ms who have, for the past 3.5 years, proved to me that VoIP really can be better than a landline!
home setup Hi Mango,
Do you have a post somewhere detailing your setup? like what hardware/software you are using?
I'm a new customer to voip.ms for a couple months in Calgary. Have Telus Optik TV/Internet package. Cancelled my land line and ported the number to voip.ms. Couldn't seem to get the ported number working on the main account but managed to get it working via a sub-account. During the migration from Telus to voip.ms, got my Dlink-380 router replaced with an Actiontec one. I'm using a Grandstream HT-502 (2 port) behind the Actiontec as I don't have a static public ip. Using STUN server setup. Seems that every couple weeks I have to reboot my HT 502 unit by unplugging/plugging it back in. Not sure where my problem is but I figured your setup might point me in the right direction to make my setup more stable.
I've been testing voip.ms at work and it is working great. Have static ip's so thing are going a lot smoother with that implementation.
I'm planning in the near future to play with a software PBX. Currently tinkering with PBX in a Flash.