Tried to call home and getting "The code you dialed is incorrect check the no you dialed" message. @ 3/17/10 11:32AM PST
Printable View
Tried to call home and getting "The code you dialed is incorrect check the no you dialed" message. @ 3/17/10 11:32AM PST
My wife just got the same. She is FURIOUS.
Everything seems fine. Only 2 support tickets in our main queue total.
It's possible there was a network blip for a few seconds, but usually we see a huge surge in tickets when there is.
We'll keep a close eye on things thought to see if anything comes up.
Must have been several network blips :-). The wife called, got the message, then called me and conference called so I could hear the same message (disconnected / not in service) - so the downtime was more than just the first call. She was pretty p*ssed off to say the least as she was trying to reach a child at home to coordinate travel plans and there was no other way to reach home. Luckily, it now appears to be fixed.Quote:
Originally Posted by VOIPoTim
I had an incoming call go directly to VOIPo voicemail this morning. I have my failover set to another phone number, so I'm not sure why failover isn't working for me. It was the same thing when there was latency problems a couple of days ago.Quote:
Originally Posted by Russell
If the VOIPo system recognizes there is a problem and sends calls to voicemail as a failover, why would it not recognize to send to my failover phone number I have set up?
The way our failover works, it should be either one or the other depending on what is set.Quote:
Originally Posted by scott2020
Do you have a ticket open?
Since we use the public internet sometimes it's out of our control.Quote:
Originally Posted by Russell
Sorry to hear your wife was upset. I hear so much about the ways of wives whether from customers or employees. The more I hear, the more I'm glad I don't have one. :)
LOL! My wife called last night too bitching that the phone doesn't work right. One way audio (again). Support had me forward the high ports (35000-65000 UDP I think), but I forgot to open those ports in the firewall!! Ooops.. So far today I've had no more issues with one-way audio so I think the problem was my firewall.Quote:
Originally Posted by VOIPoTim
Wives seem to get bent out of shape when the phone doesn't work.
When the pouty wives complain just remind them how much money they are saving over standard service. Show them that its close to $500 or more for a year, and see if pressing redial once a week is really worth the flowers, nice dinners and extra crap they bought with that $500.
My wife will tell you that an unreliable phone isn't worth free. That's what I told Vonage when I called to cancel, as my Vonage line had been pretty much unusable for months, despite multiple support tickets.
So far, she likes Voipo.
I have to agree with Steve. A telephone is a "bare essential" in the household, especially one with kids and/or parents/inlaws who may have a medical emergency at any time.
Yes, we have cell phones, but in a need of crisis, play date, or whatever, playing round robin with phone numbers to get a hold of someone sometimes isn't an option.
Luckily, after a few months of issues/instability, VOIPo support and I have worked out the issues and now I'm stable (no known outages for about a month).
-Craig
I don't have a ticket open yet. I was going to try disconnecting my end and then seeing what happens at fail over time. The past two times latency on the Internet was an issue, the failover went to VOIPo VM and not my failover number. I would like to reproduce it and then I'll open the ticket with more accurate dates/times.Quote:
Originally Posted by VOIPoTim
Naaaah, Wives are OK. I've had mine 44 years. There are times when I'd like to trade her in, but once you get used to them, they are bearable. Grandchildren are even better. :)Quote:
Originally Posted by VOIPoTim
Tonight there is horrible latency to central. I have been seeing it a lot lately into Dallas. Maybe someone at the data center can re-route around this latency or talk to their carriers and see if something can be done. My latency is only to VOIPo and not my other providers.Quote:
Originally Posted by scott2020
Can you send or post a traceroute?Quote:
Originally Posted by scott2020
We aren't really seeing any issues so would need something to show them if we report it.
I am also having issues on my lines today: Weird tones (both DTMF and other strange things), incoming calls going directly to voice mail, outgoing calls ringing busy when the other person says their phone rings and no one is on the other end, outgoing calls failing to connect, and 1/2 to 1 second delay echos.
I haven't opened a ticket since I can't pin down something solid to tell the support guys.
I opened a ticket. I gave the info I had, I can only hope they don't think I'm crazy ;)
When I see it again I'll send something over. Most often times I don't catch it right at the moment it is happening. Most of the time my wife tells me later the phone was "broken" and I look at my Asterisk logs to find there was high latency with the qualify. I have two other providers that did not show any problem with latency. If it is my Internet, all of the providers log around the same time the qualify latency was out of whack, but the last couple of days it was only the VOIPo route.Quote:
Originally Posted by VOIPoTim
Scott
Whaddyknow, another geezer. My wife and I were married in August 1965. I didn't think anyone in this forum would come close to that. :)Quote:
Originally Posted by MisterEd
Got me by a year. Yea, the whole world is full o' dem youngun's. :)Quote:
Originally Posted by caseydoug
You all sound like youngsters.Quote:
Originally Posted by caseydoug
We just passed the 53 year mark :rolleyes:
You are all making me feel young when I hit the BIG 50 this May.
My family was an instant family of five, so that anniversary will only be 16 years!
Heather had 3 girls, her best friend had 7 girls, I was outnumbered!
Ah, so that's why we're "Senior Members." Wonder if Voipo offers a senior citizen discount? :DQuote:
Originally Posted by burris
Stay around long enough, and it will change to Senile Member.
(They will maybe charge more when you are distracted :))
They do, but only if you make your calls during "The Early Bird Special.":rolleyes:Quote:
Originally Posted by MisterEd
I wish you guys would switch this chit-chat to a thread with a less ominous title!
The "Senior Member" is Tim's connotation.Quote:
Originally Posted by stevech
Complain to him;)
It is a catchy title :)
Wives with phone problems is not a good thing....makes life tough!
We have had several problems today. A couple of calls went directly to voice mail, several other calls rang but could not hear us when answered and another caller was greeted with some sort of message: "unable to complete call...".
Been quite a blippy day for sure!
No issues on our end. Contact support and they'll work with you.Quote:
Originally Posted by rsdiol
Sounds like you might need port forwarding.
If the ports aren't forwarded and the router blocks connection, it generates the error and the unable to complete calls is a generic message that the other provider plays.
Another issue tonight about our phone being "not in service". Phone rings a couple of times; we pick it up and hear nothing. Shortly thereafter phone rings again from same caller and all is well. The caller (our child) says she heard that our number was "not in service" the first time (I guess, while we were hearing the rings). 420208917_113882314@192.168.37.76 is the id of the questionable call.
Russell,
Yesterday I had couple of calls that went to voicemail after two rings. I created a ticket and they have notified the upstream carrier about this issue. Its working fine now. Voipo thinks its an issue with the upstream carrier.
Last week, a caller told me that they got the "phone not in service" message and got through the second time. I did not create a ticket for this and chalked it up to a network issue since it didn't happen again when I tested with my cell phone.
Things are a bit flaky here. People have called and they said that they get a fast busy but the call routes to my cell phone. I just tried calling my brother in law who is a voipo customer and there was a substantial pause before it started ringing and went to his failover number. Calling into a conference call today there was also a very long pause before the call picked up.
If you have issues, please submit a ticket so support can look into it.
With that said, I do think this week we may be hitting some load issues. We're doing another round of upgrades to our database cluster tonight to double capacity.
I don't know 100% that these are related, but for a few of the disconnected messages, the logs show a delay in the database query so the other carrier assumed it failed by the time it completed. So it could be related.
We didn't anticipate needing to go beyond that last upgrades, but we've grown about 10x in the last 2 months and have decided to just go ahead and double the hardware at this time.
http://forums.voipo.com/showthread.p...7825#post17825
I'm having similar issues as well (caller gets number is disconnected),
a few times on outbound, I get fast busy when dialing out.
I opened a TT (HBG-874105) and support is having me set up port
forwarding inside my pfsense box.
Somehow, I screwed that up (when I set the ATA to a static, it
no longer registers I can't get back into the ata - but that's a seperate
issue I hope support can help me with ... :-)
Do note a caller getting number is disconnected is due to issues on the VOIPo side - as Tim mentioned the database didn't respond quickly enough. Hopefully, measures being taken will improve things. I really like VOIPo and am hoping the various sever side issues get resolved and we don't have the experience of my former company after the SunRocket closure. Tim's honesty about the cause of the issue in this case is appreciated - I appreciate less "network glitch" reasons :-).Quote:
Originally Posted by slk2k
Tim, hopefully, we shouldn't have to report these number not in service issues. I'd like to imagine that reports can be run on your side to filter and determine the cause of such failed calls without us opening tickets.
I do realize that the "number is disconnected" issue may very well be a voipo-sided problem, but I was trying to follow the golden rule of "let support know about it". It it wasn't for my own idiocy (must of set the GW or DNS IP wrong), I would most likely still be on line....:(Quote:
Originally Posted by Russell
It's still important to contact support because it may not be related.
The vast majority of the cases we see with it are when port forwarding is not set.
It could be a variety of things.
And that's why I contacted support!! ;)
I do want to say "Thank You" for being so personally involved in your business!
Tim are you saying that the in the vast majority of the cases of the "number disconected or not in service", the issues are port forwarding? If yes, I'm very curious as to why the system doesn't either use the fallback number or voicemail instead of generating "number disconected or not in service".Quote:
Originally Posted by VOIPoTim