[VoiceOps] False 911 calls and old abandoned DID

Brandon Svec bsvec at teamonesolutions.com
Thu Jan 21 15:24:32 EST 2021

That does raise the question of if they have other dial tone not managed by Carlos that may have initiated the calls though. 

Brandon Svec 

> On Jan 21, 2021, at 12: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.
> Dan
> From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Carlos Alvarez
> 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.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20210121/c63a0dc0/attachment.htm>

More information about the VoiceOps mailing list