VIEW TOPIC

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."

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.

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.

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? Sorry, couldn't resist since we were fresh off the writing topic.

Still no fix on my caller id... but hoping for one soon. It's been about two weeks now...

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.

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.

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?

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.

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

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.

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

Thank you!