VoIP.ms call termination issues
I've been with VoIP.ms for a few years now, and have helped many people on this forum - though not as much as Mango. :-)
For the past month to 6 weeks, I've been experiencing strange issues on outbound calls. Most of the issues have been to the Halifax area. Tonight I tried calling the Bell voicemail number to retrieve some voicemail that I have on my Bell line. I dialed the 902-429-6245 number 12 times in total. 8 out of the 12 calls were met with a recording, "Desole, vous avez composez la mauvais numero - The number you have dialed is not in service". Looking in the call log, it shows that I dialed 902-429-6245 and that is definitely a working Bell number and has been in service for at least 30 years now. It's the main voicemail number in Halifax if you have Bell service there.
Occasionally I'm also getting messages, "Your call cannot be completed as dialed. Distributel" I call back and the next time it usually works. The calls all show up in the log --> same number dialed each time.
I have a friend living in Halifax running a business. She's been on my case daily lately with issues. She's been experiencing the same issues as mine above, but one of the other issues she is having is when she dials a number, the number people see on their call display is 902-482-8086. This used to happen once in a while, but now it happens more often than not. Especially when dialing numbers commencing with 902-456-xxxx. She has her customers and suppliers telling her the number showing is 902-482-8086. We reported it to VoIP.ms. They said, "You should be using premium routing if you want to avoid that because caller id is not guaranteed on the value routing."
She did not want to pay the extra money as it's 2.4% more expensive than the regular value routing. However, today was the last day for her. She was ready to throw her phones out the window with the complaints she's been getting and she has been having issues dialing numbers too. So she switched her service over to premium routing. This was at 11:15 this morning. Since then, twice this afternoon while dialing local Halifax numbers guess what, 902-482-8086 showed up. When you call the number back you get a message stating, "The number you have dialed is not in service. Please hang up now."
This is very bad for a business, and I can completely understand her frustrations. Her and I together have filled up pages of examples where this stuff is happening in the VoIP.ms ticket. After switching over to premium and still having this issue we are completely beside ourselves right now. It's so very disappointing.
Something has changed recently (within the past 2 months) at VoIP.ms because premium quality is behaving like value quality. Surely they would not be charging customers more money and sending the calls through the same routes? That would be misleading now wouldn't it?
Last week they had a day where 8 calls would not complete. The Distributel message would come on. After they redial the number, it works (usually). There was one instance where she had to redial it twice before it would work. After keying pages and pages, we got a response from VoIP.ms stating they have tested the numbers we gave them and they all appear to be working. Let us know if you have any more issues. It's like we were blown off. Our first write-up to VoIP.ms indicated it works one minute, not the next. We gave examples with the unique ids of calls that did not work, and to hear "Everything works when we try" is very annoying. It's enough to say that we are lying about the constant issues that we are having. We've started recording our outgoing calls for proof of the issues.
I call a lot of Ottawa numbers too, and I never have issues calling Ottawa. It's always Halifax. Whatever carriers they are using in Halifax suck, and to make matters worse, the charge is higher when you call a Halifax number.
At this point the store owner is not satisfied with VoIP.ms. It's been several months of issues and lately the outgoing calls are pathetic. I will never recommend a business to use VoIP.ms again as a provider unless this company gets things working and stops using carriers who cannot seem to handle the traffic.
I'd be very interested in knowing if any of you are experiencing these same issues.