[VoiceOps] False 911 calls and old abandoned DID
caalvarez at gmail.com
Thu Jan 21 15:25:49 EST 2021
Interesting, here in AZ we just had rain for the first time in a long
time. And yeah, Qwest has always left 911-only dialtone in place, which I
think they are required to do.
On Thu, Jan 21, 2021 at 1:08 PM Dan Mostert <dan at delhitel.com> wrote:
> We’ve run into similar circumstances before with ported in numbers. The
> losing carrier, either on purpose under the idea of “left in place
> dial-tone”, or laziness, leaves a copper PSTN line configured as the
> customer still. They also don’t maintain their aging copper, so
> particularly when the cable is wet, short outs and ends up pulse-dialling
> 911 for them. Same deal- police response for an unresponsive / hang up
> 911, and a confused/annoyed customer. In our case, the PSAPs involved see
> this so much from the losing carrier every time it rains, we just educate
> everyone involved, and the PSAP / public safety have to deal with it. I’m
> interested in anyone else’s suggestions too.
> *From:* VoiceOps <voiceops-bounces at voiceops.org> *On Behalf Of *Carlos
> *Sent:* Thursday, January 21, 2021 3:01 PM
> *To:* voiceops at voiceops.org
> *Subject:* [VoiceOps] False 911 calls and old abandoned DID
> We have a customer who has received two calls from the police because
> "they" called 911, but they did not. The CLID shown is NOT one of theirs,
> but they think it might have been theirs many years ago. The CNAM on that
> number is their company name. Nobody answers the number, and it's with
> Qwest. Our logs show no calls to 911 from them.
> Any advice on this? It's just two calls at this point, just this week.
> They've been our customer for over five years, and this number has never
> been on our system.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the VoiceOps