I've switched to using the regular toll number for my conference calls since this had been limited to toll-free numbers, but even then, I still got disconnected during my call this morning after 15 minutes. Fortunately, after connecting back in, I didn't hear my Ooma voicemail greeting haunting me.
This is with a steady 2.5mbps down / 400kbps up.
According to http://www.whichvoip.com/voip/speed_test/ppspeed.html, my voip's QOS is mostly Green /94~99% (3 out of 5) /or "yellow" / 60% (2 out of 5)
In any case, Ooma blamed it on the AT&T modem. After calling AT&T, and got transferred to 5 different people (dropped call on a landline, no less), AT&T has agreed to shipped a new modem (per Ooma's suggestion as a fix to lower the jitter to below 5 ms).
I was just wondering: did I just spend a whopping 90 minutes trying fix Ooma's BS? Or is there really an issue with DSL's jitter?
The disconnecting symptom is odd, though. I was on a conference call where each caller is announced to the group when they arrive and leave. After getting disconnected, I called back in immediately and heard my name as having joined the conference. Five minutes after that, I then heard my name as having left the conference. It would seem that my disconnected call remained connected to the conference bridge for five minutes after my Ooma Hub had disconnected the call. That seems quite odd.
My experience with calling Ooma's technical support has not been positive, instead getting rote instructions about restoring the Hub to factory settings or otherwise taking a wait-and-see attitude to see whether the problem recurs. I'm a bit reticent to call them when the problem occurs next, but the more common issue is that I'm in the middle of a call when it does happen, so I can't take the time right then to call support and see what they suggest. I should give them a try again the next time it occurs.
My drop-call problems are ALL with non-800/866/8xx pre-fixes. It's been happening sporadically for months, but it just got really bad today - twice in a row. That's when I just switched to my cell....imarollingstone wrote:I've done some experimentation, my conference numbers have non 800 numbers available. When I use the normal numbers for the same conference I have no issues at all. My conference calls are typically 877 numbers. I dialed an 877 number for a call I was hosting and the phone disconnected within 2 minutes. When dialing the non 877 number, there is no issue at all.
This is really getting irritating reading all these posts which indicate either Ooma's not willing, or not knowing how to fix this problem.
The Problem is "not" fixed. Two dropped calls consecutively. Both non-8xx numbers.Bobby B wrote:As of 15 min ago, all the servers have been upgraded with the fix for bug 8494 (sometimes calls disconnect on conferences) and bug 8492 (sometimes voicemail prompt loops if the remote party doesn't hangup).
Please let us know if you experience any further dropped calls on conference calls (please note the called number, date/time).
And to quote someone else earlier - Ooma was "not" free - we had to pay to get device for the service in the first place.