Fire Truck Came.......

Having trouble placing or receiving calls or using your voicemail system on Ooma Telo VoIP Phones? Post your questions here.
Post Reply
dlongnecker
Posts: 1
Joined: Fri Nov 15, 2019 7:11 pm

Fire Truck Came.......

Post by dlongnecker » Fri Nov 15, 2019 7:16 pm

Cooking some dinner and triggered the fire alarm. I was working in the shop. Family turned off the ADT firealarm like they are supposed to.

While I was working my cellphone rang. It said, possible Spammer ADT. They said they tried to call the house, but couldn't get ahold of anyone so they dispatched a Fire Truck.

Firemen came, and I got charged for a false alarm.

I checked my Ooma Call Log and there is no record of a call from ADT. In fact no BLOCKED calls show up.

Is this a known problem with OOMA? I want to be able to whitelist ADT, but need to know the number that appeared.

D=

TonyW
Posts: 285
Joined: Tue Jun 24, 2014 6:24 am

Re: Fire Truck Came.......

Post by TonyW » Sat Nov 16, 2019 3:35 am

All documented behavior. My solution is to send all levels of blocked calls to VM & configure Ooma to send an email notification for a new VM. Originating # will be part of the subject text. Works for me.

murphy
Posts: 7280
Joined: Tue Jan 27, 2009 12:49 pm
Location: Pennsylvania

Re: Fire Truck Came.......

Post by murphy » Sat Nov 16, 2019 3:40 am

The mad dash to block robocalling has resulted in many valid callback numbers being blocked. Apparently companies like ADT use their callback numbers to cold call potential clients. That gets them added to the block list. I had a similar experience with my alarm company. I changed the configuration so the first number for them to call is my cellphone instead of an Ooma number. There is not just one callback number to white list. My alarm company has at least five that I know of. ADT being bigger probably has a lot more. They have to be able to handle multiple alarms from the entire country at the same time. Sadly my alarm company was totally unaware that call blocking, such as NoMoRobo, exists.

I don't understand why the alarm got called in in the first place. All alarm systems are required to wait a minimum of 30 seconds after an alarm before they place the call. That is plenty of time to clear a false alarm which prevents the call.
Customer since January 2009
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx

AFOSAWIPS
Posts: 5
Joined: Fri Jul 06, 2018 6:29 am

Re: Fire Truck Came.......

Post by AFOSAWIPS » Sat Jan 04, 2020 12:27 pm

I had a visit from the PD yesterday after accidentally hitting the panic alarm button on my remote. Verification call from them was blocked and the police showed 5 min later. Half hour later they called on my cell, which was not primary, and said the attempt to reach me on my Ooma line reached a "disconnected number". According to ADT only 1 phone # should show on any outbound calls of this sort 800-328-2727, so I don't see why Nomorobo blocks it. I have added to contacts, but I assume the Nomorobo block overrides that. Have added my cell as a 2nd primary # since there is no call blocking app on that.

murphy
Posts: 7280
Joined: Tue Jan 27, 2009 12:49 pm
Location: Pennsylvania

Re: Fire Truck Came.......

Post by murphy » Sat Jan 04, 2020 1:01 pm

They probably use that number for cold calling potential customers. That is guaranteed to get the number added to the block list. Put the number in your Ooma contact list. That is supposed to "whitelist" the number and let it through in spite of NoMoRobo. I had the same problem with my alarm company and my cell phone is now primary.

I deleted "panic" from my fob a long time ago after having it in my shirt pocket and tripping the alarm while carrying something heavy.
Customer since January 2009
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx

TonyW
Posts: 285
Joined: Tue Jun 24, 2014 6:24 am

Re: Fire Truck Came.......

Post by TonyW » Sat Jan 04, 2020 8:05 pm

I had an excuse to explicitly test this function today while playing phone tag w/ the landlord.

- Call from landlord was blocked. Went straight to voicemail.

- Temporarily removed ALL blocks.

Unsure which list caused the block. Web search turned up no reports to the usual places.

- Next call from landlord rang phone & was logged.

- Added logged caller to Contact List & restored ALL blocks.

- Next call from landlord rang phone & was logged.

Whitelisting seems to be working as advertised.

Post Reply