[VoiceOps] 911 Database Stuff

[Nathan Anderson]

I still am not completely up to speed on the NG911 stuff admittedly, so take
with grain of salt, but...

 

My understanding has always been that E911 database cruft is not a big deal
because each E911 aggregator essentially runs their own database, and the
lookups are done at the time of the 911 call & the source of the call is taken
into account (however the carrier is trunked to the E911 SP; e.g., the
particular SIP peer if trunking between carrier and E911 provider is done via
IP), so even if two carriers use the same E911 aggregator and have conflicting
entries for the same TN in their database, the correct address will still get
sent to the PSAP, because the query that's executed isn't only "where TN = xxx"
but is the equivalent of "where

 

From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Mike Hammett
via VoiceOps
Sent: Tuesday, October 18, 2022 3:22 PM
To: voiceops at voiceops.org
Subject: [VoiceOps] 911 Database Stuff

 

Going through a migration from E911 to NG911, I've been peering into what and
how we do 911, both old and new.

 

A) Not all services have a web UI for you to make changes. Intrado does, but
the new one does not. Only way is to upload SOI files. I guess we gotta figure
out how to do that.

B) We have more entries than we have TNs.

C) People are bad at documentation.

 

I'm assuming we should be deleting records for customers that disconnected
service. I'm not sure we've done that, based on the records that I see.

For customers that port away, I'm assuming we're supposed to be unlocking the
TN for the new provider to take over the record.

If I unlock it, but the new provider never migrates away, what do I do with it?

What happens if a provider inserts a duplicate record?

 



-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com



Midwest Internet Exchange
http://www.midwest-ix.com



 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20221018/de1b1f4a/attachment-0001.htm>