2
2 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 9-1-1 Selective Routing Introduction 1. The CLEC 9-1-1 network is designed to accommodate ANI failure. Each trunk group serves a specific default PSAP based on an assigned Emergency Service Number (ESN). 2. An area code and exchange (NPA-NXX) may be used ubiquitously within a rate center which results in telephone numbers (TN) within the NPA-NXX being assigned within multiple default PSAP jurisdictions. 3. ALI records are submitted by the CLECs on day of customer install. The ALI submission results in TN/ESN processing in the SR by the ILEC the next day or thereafter. 4. Where multiple default PSAPs exist within a rate center boundary, line class screening is employed in the CLEC switch to guide a call to a designated CLEC 9-1-1 trunk group. 5. When the calling party's number is not determinable by the Selective Router (SR), the call is directed to the PSAP associated with the CLEC 9-1-1 trunk group. 6. Where multiple default PSAPs exist within a rate center boundary and when the ALI has not been processed to the SR, NPA-NXX (or NPA-NXX-N) wildcards increase the likelihood of routing to an inappropriate PSAP.

3
3 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 Denver Market 9-1-1 Default Routing Tactical Proposal Recommendation –For Rate Centers with multiple default PSAP boundaries, use current technology available in the DMS 100 to route calls based on Trunk Group in the case where when TN/ESN not found in the SRDB. oRemove NPA-NXX and NPA-NXX-X wildcards in the SRDB. oReload the SRDB with all TN/ESN records (based on ALI DB records). Challenges –To improve load time, determine whether the DMS 100 will accept an SRDB table load from a single restore (over a single night) instead of processing individual TNs in serial (which would take days or weeks). –Regarding incremental costs, determine impacts on existing (Qwest/ICO) network design (as in the case of Remote/Hosts), impacts on switch upgrades, and impacts to the number of channels at affected PSAPs. –To fund costs, identify cost recovery mechanisms (through CO PUC). –To maintain current arrangement where reasonable, determine whether it is desirable/possible to support wildcards for some rate centers while removing wildcards for others. –To ensure follow-up, identify actions to be taken when NRF in SRDB. –To reduce the possibility of a antiquated ALI records appearing at the PSAP, identify whether customer disconnects should result in a delete request in the SRDB.

4
4 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 Denver Market 9-1-1 Default Routing Strategic Proposal Seek a CO PUC Recommendation –Request that the Colorado PUC commission a recommendation with support from industry subject matter experts. oCase study: Atlanta established Multi-jurisdictional-PSAPs as a result of Rate Center Consolidations. oCase study: Minneapolis utilizes trunk group based default routing. Request NENA Develop a Comprehensive Default Routing Standard –Seek a Default Routing standard which includes consideration of Rate Centers which include multiple Default PSAPs. Request Intrado Develop a Near-Real-Time ALIDB/SRDB Update Capability –Request near-real-time updates of both the ALIDB and SRDB. Review Other Qwest Options –Implement Lucent (5Es) as was the case in Minneapolis

About project

Feedback

To ensure the functioning of the site, we use cookies. We share information about your activities on the site with our partners and Google partners: social networks and companies engaged in advertising and web analytics. For more information, see the Privacy Policy and Google Privacy &amp Terms.
Your consent to our cookies if you continue to use this website.