Thanks for posting on this topic again. In the current environment of Robo calls, this subject is more important than ever.
I personally emailed Tom Bakker (moderator of this forum) on Aug 2 to ask for an update, but have not heard back. The specs I suggested in my post in Oct 2018 are still valid.
Tom: When will we get something for Ooma?
Main things I miss are that blocked calls don't appear in your incoming call log and incoming SMS messages simply disappear into the ether (sender has no idea the msg wasn't delivered anywhere...)
But especially for call blocking, one thing that Ooma does way better is that there is no ringing of the phone at all! With Comcast esp. for Nomorobo calls, you get a single very annoying ring, which is because Comcast implements Nomorobo by forwarding calls, but this takes longer that what Ooma does. Eliminating the ring (which Ooma does I presume by implementing Nomorobo by actually subscribing to their blocked list) is a hugh benefit, but also really needs for Ooma to at least log the incoming call so you can see if things are working the way you want.
So this is a desperate plea to get incoming blocked calls noted in the call log.
note: scammers spoof 'reputable' numbers in hopes people will answer. hospitals are an obvious 'reputable' choice, but could easily earn a bad rep. on their own by calling erroneously transcribed numbers, etc.. they DO do a volume business.
Yesterday I emailed a salesman I haven't talked with in a long time. He called me this morning and his call was sent right to VM but I don't know why. Fortunately I did have the VM to at least known he called. He's in a company that uses 800 service but might have called on his cell phone or another number, there was no way for me to tell.
Not sure if Ooma is monitoring this forum or if we should contact them directly. I hate using the chat feature and would much prefer it if they just had a support email address I could send questions to.
Ooma announced ~2 yrs ago @ CES(?) that 'phase 2' of their enhanced call blocking would include logging of blocked calls, but then their focus shifted to home security. They may have hit a snag, but have never shared.
My solution to our problem was to enable email notification of new VMs. The originating number is included in the subject line... suitable to paste into a new contact list entry. Certainly, it could be more streamlined, but rather than wait for Ooma to implement a new feature, I practice a little 'self help'.
Subject: New VM from ECN COMMUNITY  (43 sec)
Of course, if the don't leave a msg, they weren't serious anyway... no loss.