According to my wife this happened to her once in the past as well.
Has this happened to other people and is there something I can do to optimize my environment to ensure it doesn't happen again?
So back to what I'm asking.....
Have other people experienced this? We have experienced it twice in about a month of usage. Is that a normal rate? Have people found the cause of it? Any solutions to improve it?
As you would note, some of these things can be improved by a change on Ooma's end. The VOIP reminder is misplaced. Before I pull that trigger I'd like to understand it better.
We've been battling an echo issue when my in-laws call us. Ooma CS has been working to get it cleared up. The providers that Ooma use say it's a problem with the in-laws cordless phone, but the more I thought about it, the more I don't think that's the case. We never have problems when we call them, only when the call us.
bryanlyle was right on about if it is a recurring problem to keep a log and let the ooma tech's look into it. When I first started using ooma I had echo problems on only some numbers in my local area code. It was odd - if 360 432-xxx1 was OK it didn't mean that 360 432-xxx2 would also be usable. After a lot of testing (even to the point of ooma setting up a system in their lab with a phone number one digit off of my number) they solved the echo. Then, for about a week, I had the problems you are describing. Ocassional calls that were not usable. I let them know of the times and numbers, and since the latest fix, things have been stellar. It could be that the partner ooma is using in your area needs to make some tweaks - or that ooma needs to make some in their routing tables. Either way, I know that ooma will do their best to take care of it. Please let us know when things go stellar for you again and what ooma's resolution was.
ps - I still have a separate landline with Qwest for financial reasons. The other day I was on a call to a fairly large company and had even worse call quality than I ever had with ooma. Go figure?!
VoIP hardware: 2 Telo w/3 handsets & Linx / ooma core
Total Lines: 8 / Numbers: 11 / Handsets: 20
Lifetime Premier Member
Friends don't remember what Landline Integration was or why we did it.
I know from reading other posts that Ooma can do something about it. Right now I don't really feel like harassing them about two problematic calls.
oops! Sorry didn't mean to sound like a lecture..... my bad. I forgot to run my response through Miss Manners. Where's the Racoon when you need him!I don't really need that lecture. I got it.
I understand. Type fast, think slow. I do that all of the time!WayneDsr wrote:oops! Sorry didn't mean to sound like a lecture..... my bad. I forgot to run my response through Miss Manners. Where's the Racoon when you need him!I don't really need that lecture. I got it.
Isn't that due to typical settings that would lead to that?Aveamantium wrote:Is there any chance that your inbound bandwidth happened to be saturated at the time of the call? Not sure what you're using for Qos but Qos really only works "efficiently" in the outbound direction and not the inbound.
I didn't have anything going on at the time. Hanging up and calling back immediately solved the problem so I doubt it was my network.