Having trouble placing or receiving calls or using your voicemail system on Ooma Telo VoIP Phones? Post your questions here.
#69411 by Bobby B
Fri Nov 19, 2010 5:28 pm
Unfortunately there aren't any known workarounds for the problem - it doesn't seem to depend on any settings that a system has configured.


Aveamantium wrote:Bobby, is there a workaround that people can implement prior to the fix being released. Or are there particular settings that cause this, which can be avoided?
#69443 by ShinKen
Sat Nov 20, 2010 9:18 am
Bobby B wrote:The Engineering team recently fixed this bug and we're targeting to get this fix out by mid-December. Due to the high priority of this bug, we would've liked to have started the rollout of this fix immediately, however the rollout is blocked by several other bug fix dependencies.


Bobby, Thank you for the update I look forward to this fix.
#69447 by mhowie
Sat Nov 20, 2010 10:06 am
Just a note to state my Ooma Core system has been suffering from this bug for at least the last couple of months. After yet another incident I came to the forum and found this is indeed a real problem and there is a lot of energy in this thread about the aggravation it is causing.

I'm unclear what caused this bug to become imbedded in the system (I will read the entire thread for details) but would ask that Ooma please get this fix out ASAP in order that a normal calling process might be restored.
#69534 by MsCoulter
Mon Nov 22, 2010 11:15 am
This is also happening to me, plus, caller ID does not pick these calls up...they ring once or twice and go to voicemail with no caller ID record on the phone or in the ooma, unless they leave a message. I emailed support toda to get an ETA and they got back to me promptly, but no ETA is in sight. I wonder if this is really on a back burner?
#69542 by ObviousMan
Mon Nov 22, 2010 2:23 pm
This was happening to my Hub since about mid-October. Initially infrequently, now many more calls get "The person who you dialed..." In fact it would go into this mode until you either power it down/up or disconnect/reconnect to the network.
My VM is set to max rings, and I can tell this had happen more than 3-4 dozen times, as half the time it was happening to me trying to dial home while on the business trip. My wife had reported over a dozen such occurrences too as she was trying to check up on kids from work. I am barely holding my wife from jumping into waiting ATT arms, she's so upset.
I swear I had not read fudder's post before writing the above.
I can barely wait for the fix.
#69544 by MsCoulter
Mon Nov 22, 2010 3:09 pm
I would think that ooma would want to expedite the fix since so many users are affected. I find it hard to believe there are other bugs that take priority. Maybe the support staff is much smaller than we think?

For the record I have the ooma hub/scout and no extra services. My voicemail pickup was set to 27 seconds and I upped it to 29 seconds today. I only receive 1-3 calls per day so its hard for me to notice how many fail especially since if they don't leave a message, there is no way to know if they were sent to voicemail, and they are not recorded on my caller ID so I can't call them back.
#69545 by roadshow
Mon Nov 22, 2010 3:38 pm
This issue is still happening to me every day. OOMA Support Team needs to address this immediately. Please send the firmware fix ASAP. And please don't forget about your loyal Hub users. we are having thesame problem.
#69572 by Asok
Tue Nov 23, 2010 10:54 am
Just piling on with a "me too". My Ooma has been having issues for months - going back to the big Ooma East Coast outage (even though I live on the West Coast near Seattle).

Some calls get in, but most ring once and go to voicemail. Some days are better than others. Rebooting my modem, router, an Ooma will sometimes seem to fix the problem, but it always comes back. I have pretty fast internet (20 down / 6 up) and have spent several hours on the phone with Ooma support tweaking my configuration and adjusting QoS values.

It's all very frustrating. Most people that know me, just call my cell now. I've converted others to Ooma and they seem to have random problems as well. It is just become a joke in conversation now. "Sorry, my Ooma is acting up today" is a common way to start a conversation when calling someone back after a missed call.
#69581 by dschmidt_2000
Tue Nov 23, 2010 12:45 pm
Bobby B wrote:The Engineering team recently fixed this bug and we're targeting to get this fix out by mid-December. Due to the high priority of this bug, we would've liked to have started the rollout of this fix immediately, however the rollout is blocked by several other bug fix dependencies.

Great news! Is this a bug fix that requires pushing new firmware out to the Hub and Telo or is this on the server side?
Will the release be done with release notes and a list of what was fixed?
dave

Who is online

Users browsing this forum: No registered users and 9 guests