Review by koreyb 
member for 8.3 years, 1561 visits, last login: a few hours ago
updated 342 days ago
 Etobicoke,ON
 Contract price not specified.  "Customer Service has been good, fairly easy to work with. Pay for what you need! Outgoing Calls are VERY VERY CLEAR!" "Support done via tickets or online chat only. NO FLAT RATE PACKAGE Support isn't available on Sundays." "Not too bad! Has all the features you would ever need! PAY ONLY FOR WHAT YOU NEED!"
| Web-site:
Ease of Installation:
Call Quality:
Reliability:
Tech Support:
Value for money:
(ratings match consensus)
|
I have had the service for a month.. So far things have been not bad!
Incoming DID issues from the start:
I've ported my number over from Primus and from day one I've experienced issues where audio on incoming calls has had blips and drop outs on the far end of the call (what the caller hears) After almost 4 weeks, the problem seems to be with the Montreal and Toronto POP's. As a temp fix, I'm using Chicago's server, which has improved things greatly. I have tested Chicago and Seattle in the past, but they must have fixed something on those servers as well because it seems to be clearer than it was before on those servers. It seems there's a few customers with this issue, so hopefully it's fixed soon.
Outgoing calls have been flawless from day one on any server.. Very happy where. Very clear, very crisp. How it should be!
I run my own asterisk box,(PBX IN A FLASH) and it works perfectly! But can be setup very simply with a SIP phone or adaptor. I like the ability to control every aspect and assign everyone their own extension and vmail. (I know GEEKY)
I would not recommend this service for someone who does not have a geek in their life or is comfortable with setting stuff up themselves. It's really a DIY type service. But the cost savings are great. We only spent 10 dollars last month, and that included the 5 dollar unlimited DID FEE! We use the phone a lot too!
Update Aug 19 2010:
The DID issue still has not been corrected.. Support says they have to replace the Toronto server with a new one, in hopes to fix things for the few users who have came forward. Most users are likely unaware of the issue as it only effects audio on the callers end from outside the voip.ms network. This is likely why things are going so slow on the replacement.
Using Chicago's DID seems to for the most part correct the issue, but due to long distances and many hops between Toronto and Chicago, at times of the day, the line gets dicey on both directions on incoming calls.
Outgoing has never been an issue.
If this new server is installed, and the issues are not corrected, I will have no choice but to move my did away from them and use someone else. I also use freephoneline for a 2nd did number and have no issues. It's sad when you pay a monthly fee and have issues, where something that is free you don't.
Nov 8 2010
Just an update that the team at VOIP.ms has got their issues figured out.. It would seem the Main Toronto and Montreal servers where overloaded.. They added a 2nd server, and it seems to have corrected the issues..
Hopefully it stays this way... It's been solid since the install of the new servers.
UPDATE JUNE 15 2012
Once all the issue where resolved, it's been really good.. I have no real issues with this company.. Only wish they had some flat rate packages... but they are solid, and seems to work for my needs!
Comments:
 Reviews:
 ·Cablemas
2 edits | Answer regarding your DID. The DID itself is not the issue, as you can see it works correctly when routed to severs other than Montreal and Toronto.
This issue you are reporting has been brought to our attention by less than 5 customers. This does not mean the issue is being ignored, brushed off or disregarded, but it clearly shows the scope of the issue (We have more than 22,000 DIDs).
We have responded to the customers reporting this specific issue, that for now the current work around is to simply use a different server, while we do a planned hardware upgrade of the toronto and montreal servers.
Hardware upgrades are not performed as fast as we would like with all providers, but we are moving forward with the change (Which was already planned due to our increase of canadian customers, we just decided to move the plan forward)
I do understand you wish to use a specific server to connect to, but since we have customers overseas using USA servers properly, I would believe that from Canada you should receive a very acceptable latency for most of our USA servers.
Please keep in mind that while some providers give you only one server to connect to, we have 11 servers to connect to (2 in Canada, 8 in USA, and 1 in Europe, plus the ones we will add in the following months), so please keep using a USA server while we complete the server upgrade in Canada.
Thank you for your attention
--
Peter Sahui - VoIP.ms | |
|  | koreybReplace the CRTC NOW
join:2005-01-08
East York, ON Reviews:
·TekSavvy Cable
 ·voip.ms
| Re: Answer regarding your DID. said by suppafly:The DID itself is not the issue, as you can see it works correctly when routed to severs other than Montreal and Toronto. This issue you are reporting has been brought to our attention by less than 5 customers. This does not mean the issue is being ignored, brushed off or disregarded, but it clearly shows the scope of the issue (We have more than 22,000 DIDs). We have responded to the customers reporting this specific issue, that for now the current work around is to simply use a different server, while we do a planned hardware upgrade of the toronto and montreal servers. Hardware upgrades are not performed as fast as we would like with all providers, but we are moving forward with the change (Which was already planned due to our increase of canadian customers, we just decided to move the plan forward) I do understand you wish to use a specific server to connect to, but since we have customers overseas using USA servers properly, I would believe that from Canada you should receive a very acceptable latency for most of our USA servers. Please keep in mind that while some providers give you only one server to connect to, we have 11 servers to connect to (2 in Canada, 8 in USA, and 1 in Europe, plus the ones we will add in the following months), so please keep using a USA server while we complete the server upgrade in Canada. Thank you for your attention With all due respect Peter, having 11+ servers are great but when the traffic between the home user and your pop becomes the issue, due to distance (which will happen when you live in Toronto and have to use a far off server to get things working correctly). This is the reason I would like to connect to Montreal as I do for my outbound calls without issue.
I'm trying to use Montreal because of a much better ping time and the fact there is no traffic issues between it and my home. Toronto is no longer routed via Torix and goes 1/2 way across the country to get back to Toronto, which is useless really as it has the largest issues.
I do not buy that it's only effecting less than 5 users... maybe my expectations are too high coming from Primus... but I still feel people who have not called their line from a Bell Canada or something outside the voip.ms network would find they ALL have these issues, when connected to Toronto or Montreal.
Freephoneline, has worked for me without any issues like this, as has call centric, vbuzzer, etc. etc.
I'm not saying I'm being ignored, I'm saying that due to the few reports the urgency just isn't there. I also have been reporting this issue since June when I moved my number over. IT's almost September and no fix really has happened other than moving thing to Chicago which was a temp solution. Most people would have said the hell with it and moved their number away from your company by now, but due to your reputation I'm giving you guys a chance to correct the issue. | |
| | | MartinMVoIP.msPremium,VIP
join:2008-07-21
1 edit | Re: Answer regarding your DID. Our users don't all have that issue, as you say. We've over 11,000 Canadian DIDs currently in use by our user base.
I'm truly sorry about what you experienced but we offered a valid alternative meanwhile.
We already have new servers on your prefered locations.
--
Martin - VoIP.ms | |
|
| |
|
