Dinowitz questions steps taken to resolve the issue after 6 a.m.
Dinowitz asks what steps were taken. Gelobter explains teams looked at hardware, headsets, and position-specific issues. Barbera adds they triaged what was believed to be a looping alarm auto-dialer, engaged Verizon for alarm routing, and escalated when the broader scope became clear.
So I guess it's safe to say that by 6 a.m.
We knew that it wasn't just alarm companies having some issues with the...
At that time, the reported issue was with that same caller ID, which is the 10-digit emergency alarm number.
Can you repeat that?
I'm sorry, I didn't catch the response.
The second response or the full response?
The second response.
At that time, the reported issue was with that same caller ID, the 10-digit alarm emergency number.
Okay, and can you repeat again what steps were taken to resolve the issue?
I deferred.
OTI.
So between, starting at 6 a.m.
When there was the shoulder tap identifying the issues that the call takers were presenting at those two positions,
there were a number of elements looked at, including looking at hardware, headsets, and all of those types of things.
I don't know, DC Barbera, if you want to provide any more color.
So from the time that the initial issue was reported at those two positions, technical teams began troubleshooting those positions.
Obviously, there could be a number of technical problems that could be impacting audio conditions.
Once they learned that there was an increase in volume of alarm calls,
they started to triage what was believed to be a looping alarm auto dialer, which is a common occurrence where they'll continuously call in over and over again and there would not be audio conditions.
So they started to triage that as an alarm company issue, and that's when Verizon was engaged for alarm routing.
Okay.