Page 1 of 1

Ooma Premier - Is it starting to recognize robo callers?

Posted: Fri May 03, 2019 11:10 am
by EdKeating
I've noticed something that may have started in the current release of Ooma 414894 or may have started on the previous release..
Several recent spoofed calls from local spoofed caller IDs now have this happen:
Call rings, I pick up and say nothing, robocall starts playing message, call is cut off at 10-11 seconds duration.
Is this a partial implementation of Stir/Shaken which happens to take that length of time to determine that the caller ID was spoofed? Or is this just coincidental observations?

Re: Ooma Premier - Is it starting to recognize robo callers?

Posted: Mon May 06, 2019 7:24 am
by EdKeating
Actually, its happening on all inbound calls. After about 10 seconds, call drops. Outbound calls not affected.
Last 10 calls is only showing last 4 calls and new one causes previous one to drop off. Ooma unit shows online and no problems. Last 4 calls Originate is ok, termination is not.

1 8475711170 496 1 0 1 2.60 0.05 508 99 4.16
2 18475711170 2202 22 0 22 3.55 1.95 2222 120 4.09
3 8475711170 4268 1 0 1 5.81 1.65 4268 139 4.02
4 18475711170 3276 21 0 21 4.24 0.17 3292 99 4.17

Re: Ooma Premier - Is it starting to recognize robo callers?

Posted: Tue May 07, 2019 3:27 pm
by lmacmil
Lots of robocall recordings are not tripped until they detect a voice. When I answer a suspected robocall, I don't say a thing. Probably 75% of the time, the call ends within 5 seconds. In many cases, the caller ID is simply the city and state (usually my state.)

I recently took the plunge with Premier (did the annual service and got a free HD3 handset) and it has cut down my robocalls by 90%. Used to get 2-5 per day, now getting 2 or 3 a week. I add the number to NoMoRobo but generally don't bother with the MyOoma blocked call list because they change the numbers too often.