Not sure what to make of that, and AFAIK there is no way for you to effectively block it.
There are a few threads floating around here about requests to add more powerful blacklisting by allowing wildcards and custom filters, etc. To me, this is one more reason why Ooma should do this.
Depending on how advanced they want to get, I know that allowing custom filters can be risky in that a customer could possibly create a filter that would block legitimate calls (or even all calls if you're really careless), but perhaps if Ooma made it an "advanced option
" and explained the potential negative consequences, they could still do it.
I think the ability to use wildcards in the CID name and/or number would make the blacklist filters much more powerful. Something as simple as "555-****" or "*SMITH" to block anyone with the last name of Smith (not that I'd use such a broad and careless filter but you get the idea).
If they want to get even fancier, allow something like REGEX-based filters, maybe even with a REGEX builder that would make it easier for customers unfamiliar with REGEX to build custom filters.
Also of course, as has been suggested, show a log of calls that have been blocked/sent to VM.
This would be very handy for troubleshooting as well as seeing how many unwanted calls you are avoiding!