Problems using My Ooma? Ideas on how we can make it better? You’ve come to the right place.
#78196 by lbmofo
Mon Mar 28, 2011 9:21 pm
nn5i wrote:In order to provide customers with the best possible experience while Ooma grows its customer base, we update our systems from time to time. We have not yet developed a workaround for this problem, nor can we predict when it will be corrected. Our Network Operations Department is aware of your issue, and we hope to resolve it this weekend. Thank you for your patience.

Nice. I see one omission though; I think the writer also wanted to convey "issue does not affect all customers."
#78209 by nn5i
Tue Mar 29, 2011 5:20 am
lbmofo wrote:Nice. I see one omission though; I think the writer also wanted to convey "issue does not affect all customers."

Yup, that's one possibility. It's hard to tell what he was trying to say. I considered eliminating my whole first sentence and writing something similar to what you suggest.

Rewriting has its political side. When rewriting for a new client, one makes fewer changes than for a client to whom one has proven oneself over time.
#78256 by lbmofo
Tue Mar 29, 2011 9:07 pm
AlpacaLips wrote:Sorry to interrupt this meeting of the Writer's Mutual Admiration Society... (That's a JOKE! Lighten up! Sheesh!)

As of today, my caller ID is back to normal.

Thanks for reporting AlpacaLips. Your userid is a variant of Apocalypse?! :) APackofLips? :P Sorry, couldn't resist since we were fresh off the writing topic.
#78278 by ntoy
Wed Mar 30, 2011 9:59 am
lhight wrote:Still no fix on my caller id... but hoping for one soon. It's been about two weeks now...


Hello,

Currently bug 10543. No updates yet.
#78294 by Bobby B
Wed Mar 30, 2011 4:44 pm
The latest on bug 10543 - it has been fixed and we're targeting to deploy the Telo release with this fix next week after QA testing has completed. Telos affected by this bug will get the update first.
#78298 by tomcat
Wed Mar 30, 2011 5:56 pm
Bobby B wrote:The latest on bug 10543 - it has been fixed and we're targeting to deploy the Telo release with this fix next week after QA testing has completed. Telos affected by this bug will get the update first.

If all telos have the same firmware (I am assuming they do), why would some be effected while others are not?
#78314 by Bobby B
Thu Mar 31, 2011 9:02 am
It depends on the Ooma phone number you have. The root of the problem is the inbound caller-ID phone number for certain Ooma phone numbers have a special character in it that the Telo doesn't know how to handle today. The fix will correct this special character handling.

tomcat wrote:If all telos have the same firmware (I am assuming they do), why would some be effected while others are not?
#78323 by tomcat
Thu Mar 31, 2011 10:42 am
Bobby B wrote:It depends on the Ooma phone number you have. The root of the problem is the inbound caller-ID phone number for certain Ooma phone numbers have a special character in it that the Telo doesn't know how to handle today. The fix will correct this special character handling.

tomcat wrote:If all telos have the same firmware (I am assuming they do), why would some be effected while others are not?

Thank you!

Who is online

Users browsing this forum: No registered users and 11 guests