voip.ms discussion - Page 45 - Canadian TV, Computing and Home Theatre Forums

FunkyTown · 2010-02-01, 10:05 PM

Well the sound is still not quite as clear as the premium. The connection is faster though.

Have you noticed the premium route can take up to 6 seconds before the ring starts? Value has only a 1 second delay.

marunio · 2010-02-01, 10:14 PM

I am using premium routing.
Found the problem - did not have CallerID set in Main Account settings.
Noticed that only my name was showing up on the destination phone and not number.
Feel silly....
Thanks.
m

Mango · 2010-02-01, 10:31 PM

I hadn't noticed the delay but now that you mention it I do. I wonder what causes that?

FunkyTown · 2010-02-01, 10:40 PM

I don't know. I assume whatever company they are using to route premium calls has something wrong with the way they manage their PSTN trunks. In this digital age there should be no delay. It could even be a dial plan problem. You know if you don't place S0 at the end of your dial string there would be a delay like this. However the S0 is there on my end, and when using value it connects immediately. Premium has never connected immediately. There's always been a delay.

sdh · 2010-02-04, 08:19 AM

Voip.ms is really an amazing company. Great features, great rates. But recently they've been having a major problem on their value lines: they're not passing caller ID!!! This just started happening at the end of 2009/beginning of 2010 (was working previously) and will hopefully be fixed. But just to give anyone a warning that currently it only works on their premium lines.

A bit frustrating as friends/family wont answer calls based on the fact that the don't recognize the number. Hopefully they'll fix it soon!!!!!

Mango · 2010-02-04, 10:56 AM

Caller ID is never guaranteed on the value route. That's not a "major problem," that's one specific reason why Value routing is cheaper.

If it worked 100% of the time, then they would raise the price and call it the premium route

FunkyTown · 2010-02-04, 04:44 PM

The main reason it's value is because of the inferior audio quality. Value always carried my number but not my name. I don't recall it ever displaying a Quebec phone number until recently.

I agree Voip.ms is a great company, but I do have a concern with what next is going to stop working. When things are improved I don't mind, but when things are worse today than yesterday it is bothersome. There's a lack of trust and reliability that goes with it.

On incoming caller id I've often seen:

NS POTS LINE

You get charged for this lookup too. What's up with that? The same person from the same number calls me on my cell or at work and their name comes up. With voip.ms, POTS phone comes up and they still charge for the lookup?

They mentioned not long ago that number lookups will be cached and we will only be charged for numbers not found in the cache. Yet the same person could call me 10 times in one hour and I'd be charged for all 10 lookups. It will be nice when they start providing the customized directory feature.

Mango · 2010-02-04, 08:03 PM

Quote:

Originally Posted by FunkyTown

when things are worse today than yesterday it is bothersome. There's a lack of trust and reliability that goes with it.

OMG. Overdramatic much? They state right in their FAQ that they do not guarantee Caller ID on the value route. I don't see why people complain so much about outbound Caller ID on the value route. It's like going to the Scratch-and-Dent section at Sears and complaining that the stuff there has scratches and dents.

If Outbound Caller ID is that big of an issue for you, just use premium routing like I do.

Regarding your incoming cnam problem: strange question I know, but what does it display when your friend calls if cnam is turned off for your DID?

m.

FunkyTown · 2010-02-04, 08:53 PM

I am using Premium right now because I can't stand the variations of quality and service from value. Keep your personal attacks to yourself Mango. That goes against forum rules and I don't appreciate it. Not sure if you work at voip.ms or wish you did. There's no need for the sarcasm.

Now another change has been made over the past 2 days. My mom hasn't been able to call me for 2 days thanks to this recent change. I've got a rule setup to send anonymous calls to voicemail. Now when mom calls instead of getting:

NS POTS PHONE

I'm getting "Unavailable", with the number 902-xxx-xxxx.

The voip.ms system is now treating the call as an anonymous call and mom was being routed to voicemail. Being 84 she doesn't leave messages. It bothers me that changes keep taking place without proper testing. If there was another voip company offering BYOD with the similar features I like I would leave. Maybe Google will come out with something.

The sad thing is, right now voip.ms is likely one of the better BYOD companies, but there is a huge improvement that could be made in the way they test their changes.

Instead of stating "POTS NUMBER", it comes in as "Unavailable"

gobe · 2010-02-04, 10:54 PM

Quote:

Originally Posted by Mango

.... Regarding your incoming cnam problem....

Believe it or not, I have been having inbound CNAM problem since Feb 2 ....

Background: I am on Premium route (always) and have enabled CNAM for my DIDs and have not changed a thing on my setup. CNAM from 2 of my regular callers always work and show proper names since last September when I signed up with Voip.ms but ever since Feb 2 their names do NOT show up anymore, the name field is now showing their numbers...so the display name field and the display number field show exactly the same info.

I have opened a ticket and have been debugging this problem with Voip.ms for the last 2 days over support Chat.... today, voip.ms indicates that they may have found something and is checking with their carrier to see if that's where the problem originated ... they said they would have an answer for me tomorrow (Feb 5)

Anyone else have their inbound CNAM stopped working partially ?
My problem is some callers have Name display, some callers have numbers display only and those were the callers that used to have name displayed prior to Feb 2. US number that should have name displayed don't ... this all started on Feb 2, 2010

.

FunkyTown · 2010-02-04, 11:26 PM

Yes that's when the issues I'm having started.

When I look through the tickets I've opened with Voip.ms, there has not been one month since they started their new ticket system that I haven't had trouble. In late January I was forced to switch to value route because I could not get premium route to work. No sound after dialing a number. At the same time, all calls in my call log were showing up double.

Don't get me wrong, I love enhancements, but they need to be tested. Some of the issues I've encountered have not been complex issues. I find them right away and I'm not doing anything complicated. I'm not on the phone often. Yet I find bugs every month on the premium route. I was with Primus before this and the biggest problem with Primus over 2004 thru 2009 was they did not offer BYOD. I never had issues with caller id, my call logs, audio issues, 1-866 numbers, etc.

Many friends and co-workers of mine have not bought in to the voip phone service. Their number one concern is reliability. VoIP has some very negative connotations surrounding it due to lack of reliability. In this aspect companies offering voip need to be extra careful not to propagate these concerns. It's quite serious! It's very bad for business to have ongoing issues with your service. It's bad for voip in general.

Mango · 2010-02-05, 12:39 AM

Quote:

Originally Posted by FunkyTown

Not sure if you work at voip.ms or wish you did.

I can assure you I do not work for VoIP.ms.

If either of you gets an answer regarding inbound cnam, please post if you have the time. I'm not having any issues but I am curious

m.

FunkyTown · 2010-02-07, 10:42 AM

Well the Incoming caller id is still broken. Found another bug today. I called a 613 Ottawa number and was connected to my party. In the call log it states 0.02010000 cents per minute, AUSTRALIA METRO CITIES. I was billed at that rate.

We all know that voip is not perfect, but these problems are not voip problems. They are problems with Voip.ms not properly testing on-going changes that they keep making.

I've created 3 trouble tickets in the past 3 weeks.

Mango · 2010-02-07, 11:35 AM

The country code for Australia is 61 so that is likely the source of the bug. I hope they get that sorted asap.

I too discovered a billing issue this weekend...but my conscience does not allow me to describe it until after they fix it

m.

FunkyTown · 2010-02-07, 11:55 AM

Ha! I have kept quiet about most of the issues but my conscience is starting to become very annoyed with the large number of issues. I love some of the features voip.ms has. That's where it ends. I think they need to spend more time testing.

In 2009 I had entries in my call log from the 1-866 toll free numbers coming up as China. I've never called China in my life, and I've got international calling OFF in my profile, so why their system continues to think I'm calling overseas is beyond me.

Their service is not reliable when there are constant issues going on. It is a "dramatic" number of tickets I've created over the past 6 months. I'm thinking of switching to another company because at this rate, who knows if 911 will work if I need it.

2010-02-01, 10:14 PM	#662
marunio Rookie Join Date: Oct 2008 Posts: 8	Long distance ring on local calls. I am using premium routing. Found the problem - did not have CallerID set in Main Account settings. Noticed that only my name was showing up on the destination phone and not number. Feel silly.... Thanks. m

2010-02-01, 10:31 PM	#663
Mango Join Date: Nov 2008 Location: Alberta Posts: 797	I hadn't noticed the delay but now that you mention it I do. I wonder what causes that? __________________ Mango's dial plan for an OBi ATA

2010-02-04, 08:19 AM	#665
sdh Rookie Join Date: Feb 2010 Posts: 8	Caller ID on Value Voip.ms is really an amazing company. Great features, great rates. But recently they've been having a major problem on their value lines: they're not passing caller ID!!! This just started happening at the end of 2009/beginning of 2010 (was working previously) and will hopefully be fixed. But just to give anyone a warning that currently it only works on their premium lines. A bit frustrating as friends/family wont answer calls based on the fact that the don't recognize the number. Hopefully they'll fix it soon!!!!!

2010-02-04, 10:56 AM	#666
Mango Join Date: Nov 2008 Location: Alberta Posts: 797	Caller ID is never guaranteed on the value route. That's not a "major problem," that's one specific reason why Value routing is cheaper. If it worked 100% of the time, then they would raise the price and call it the premium route __________________ Mango's dial plan for an OBi ATA

2010-02-07, 11:35 AM	#674
Mango Join Date: Nov 2008 Location: Alberta Posts: 797	The country code for Australia is 61 so that is likely the source of the bug. I hope they get that sorted asap. I too discovered a billing issue this weekend...but my conscience does not allow me to describe it until after they fix it m. __________________ Mango's dial plan for an OBi ATA

2010-02-01, 10:05 PM	#661
FunkyTown Join Date: May 2006 Location: Gatineau, QC Posts: 1,165	Well the sound is still not quite as clear as the premium. The connection is faster though. Have you noticed the premium route can take up to 6 seconds before the ring starts? Value has only a 1 second delay.

2010-02-01, 10:40 PM	#664
FunkyTown Join Date: May 2006 Location: Gatineau, QC Posts: 1,165	I don't know. I assume whatever company they are using to route premium calls has something wrong with the way they manage their PSTN trunks. In this digital age there should be no delay. It could even be a dial plan problem. You know if you don't place S0 at the end of your dial string there would be a delay like this. However the S0 is there on my end, and when using value it connects immediately. Premium has never connected immediately. There's always been a delay.

2010-02-04, 04:44 PM	#667
FunkyTown Join Date: May 2006 Location: Gatineau, QC Posts: 1,165	The main reason it's value is because of the inferior audio quality. Value always carried my number but not my name. I don't recall it ever displaying a Quebec phone number until recently. I agree Voip.ms is a great company, but I do have a concern with what next is going to stop working. When things are improved I don't mind, but when things are worse today than yesterday it is bothersome. There's a lack of trust and reliability that goes with it. On incoming caller id I've often seen: NS POTS LINE You get charged for this lookup too. What's up with that? The same person from the same number calls me on my cell or at work and their name comes up. With voip.ms, POTS phone comes up and they still charge for the lookup? They mentioned not long ago that number lookups will be cached and we will only be charged for numbers not found in the cache. Yet the same person could call me 10 times in one hour and I'd be charged for all 10 lookups. It will be nice when they start providing the customized directory feature.

2010-02-04, 08:53 PM	#669
FunkyTown Join Date: May 2006 Location: Gatineau, QC Posts: 1,165	I am using Premium right now because I can't stand the variations of quality and service from value. Keep your personal attacks to yourself Mango. That goes against forum rules and I don't appreciate it. Not sure if you work at voip.ms or wish you did. There's no need for the sarcasm. Now another change has been made over the past 2 days. My mom hasn't been able to call me for 2 days thanks to this recent change. I've got a rule setup to send anonymous calls to voicemail. Now when mom calls instead of getting: NS POTS PHONE I'm getting "Unavailable", with the number 902-xxx-xxxx. The voip.ms system is now treating the call as an anonymous call and mom was being routed to voicemail. Being 84 she doesn't leave messages. It bothers me that changes keep taking place without proper testing. If there was another voip company offering BYOD with the similar features I like I would leave. Maybe Google will come out with something. The sad thing is, right now voip.ms is likely one of the better BYOD companies, but there is a huge improvement that could be made in the way they test their changes. Instead of stating "POTS NUMBER", it comes in as "Unavailable"

2010-02-04, 11:26 PM	#671
FunkyTown Join Date: May 2006 Location: Gatineau, QC Posts: 1,165	Yes that's when the issues I'm having started. When I look through the tickets I've opened with Voip.ms, there has not been one month since they started their new ticket system that I haven't had trouble. In late January I was forced to switch to value route because I could not get premium route to work. No sound after dialing a number. At the same time, all calls in my call log were showing up double. Don't get me wrong, I love enhancements, but they need to be tested. Some of the issues I've encountered have not been complex issues. I find them right away and I'm not doing anything complicated. I'm not on the phone often. Yet I find bugs every month on the premium route. I was with Primus before this and the biggest problem with Primus over 2004 thru 2009 was they did not offer BYOD. I never had issues with caller id, my call logs, audio issues, 1-866 numbers, etc. Many friends and co-workers of mine have not bought in to the voip phone service. Their number one concern is reliability. VoIP has some very negative connotations surrounding it due to lack of reliability. In this aspect companies offering voip need to be extra careful not to propagate these concerns. It's quite serious! It's very bad for business to have ongoing issues with your service. It's bad for voip in general.

2010-02-07, 10:42 AM	#673
FunkyTown Join Date: May 2006 Location: Gatineau, QC Posts: 1,165	Well the Incoming caller id is still broken. Found another bug today. I called a 613 Ottawa number and was connected to my party. In the call log it states 0.02010000 cents per minute, AUSTRALIA METRO CITIES. I was billed at that rate. We all know that voip is not perfect, but these problems are not voip problems. They are problems with Voip.ms not properly testing on-going changes that they keep making. I've created 3 trouble tickets in the past 3 weeks.

2010-02-07, 11:55 AM	#675
FunkyTown Join Date: May 2006 Location: Gatineau, QC Posts: 1,165	Ha! I have kept quiet about most of the issues but my conscience is starting to become very annoyed with the large number of issues. I love some of the features voip.ms has. That's where it ends. I think they need to spend more time testing. In 2009 I had entries in my call log from the 1-866 toll free numbers coming up as China. I've never called China in my life, and I've got international calling OFF in my profile, so why their system continues to think I'm calling overseas is beyond me. Their service is not reliable when there are constant issues going on. It is a "dramatic" number of tickets I've created over the past 6 months. I'm thinking of switching to another company because at this rate, who knows if 911 will work if I need it.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode