Call blocking 'ends with'
I see that call blocking now allows specifying names that "end with" something.
I'd like to use this to block calls from e.g. "BRAINTREE MA", but not calls where the name of the caller happens to end with "MA", eg. "OOMA". If I add an 'ends-with' block and enter a space followed by MA for the name, it looks like the space gets dropped.
Is there a way to use ends-with blocking to accomplish what I want?
I'd like to use this to block calls from e.g. "BRAINTREE MA", but not calls where the name of the caller happens to end with "MA", eg. "OOMA". If I add an 'ends-with' block and enter a space followed by MA for the name, it looks like the space gets dropped.
Is there a way to use ends-with blocking to accomplish what I want?
Re: Call blocking 'ends with'
Yes MyOoma strips the space when submitting the string to the backend,
so went ahead and added "* MA" using our database console.
so went ahead and added "* MA" using our database console.
Re: Call blocking 'ends with'
Will individual users be able to apply similar filters manually, in future? Or will this be akin to enabling the high-bandwidth codec, requiring support intervention?
Re: Call blocking 'ends with'
yes you will need to call support
Re: Call blocking 'ends with'
Can the same be done for me with my existing filters or do I need to call customer support?
Re: Call blocking 'ends with'
@Tom I receive a good deal of robocalls formatted such as:
Detroit, MI
Southfield, MI
City, State
The Block List won't allow a ",". I would prefer to do an exact match because hospitals, etc may use
the city name in it's caller ID string.
"Yes MyOoma strips the space when submitting the string to the backend,
so went ahead and added "* MA" using our database console."
Does your backend automatically eliminate punctuation characters when matching the incoming Caller ID string?
Detroit, MI is sent to the our Block List as "DetroitMI" and the same logic is used on the incoming information?
If so I will add "DetroitMI" to my Block List.
Detroit, MI
Southfield, MI
City, State
The Block List won't allow a ",". I would prefer to do an exact match because hospitals, etc may use
the city name in it's caller ID string.
"Yes MyOoma strips the space when submitting the string to the backend,
so went ahead and added "* MA" using our database console."
Does your backend automatically eliminate punctuation characters when matching the incoming Caller ID string?
Detroit, MI is sent to the our Block List as "DetroitMI" and the same logic is used on the incoming information?
If so I will add "DetroitMI" to my Block List.
Re: Call blocking 'ends with'
I apologize that I know this has been asked before - I tried searching before posting. How can (assuming it can be done) an area code + prefix be blocked? Was thinking 727-555-**** or #? or blank after?
Re: Call blocking 'ends with'
https://my.ooma.com/preferences/call_blocking
Edit my block list
Block a number > I want to block "Numbers that start with..." > enter "727-555" > save
Edit my block list
Block a number > I want to block "Numbers that start with..." > enter "727-555" > save
Re: Call blocking 'ends with'
Thanks - this time put it in my Ooma notes.