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?
Bobby, Thank you for the update I look forward to this fix.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.
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.
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.
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.
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.
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?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.
Will the release be done with release notes and a list of what was fixed?