This document is written for NENA Technical Committee leadership and members. A requirement for participating in the Technical Committee process is to adhere to all procedures outlined in this document.

This document sets forth NENA standards for all Service Providers (SPs) involved in providing dial tone to end users whether or not they are the 9-1-1 Database Management System Provider (DBMSP) or a SP in an Enhanced 9-1-1 area. It includes Database Maintenance, Quality measurements, INP, LNP and Number Pooling standards to be utilized for any 9-1-1 system that provides information for data display. It defines measurements that support meaningful computations to allow for a better understanding of database quality and timeliness of database updates.

Voice over Internet Protocol (VoIP) is poised to become the predominant technology used in the telecommunications industry. As the public adopts VoIP, E9-1-1 calls will increasingly originate from VoIP users. Some VoIP telecommunications service provider networks, however, are not natively compatible with the existing E9-1-1 infrastructure. NENA is developing a view of migratory (i2) and long-term (i3) solutions that will continue to support location-based routing of E9-1-1 calls and delivery of location-related information to PSAPs.

This NENA document sets forth standards for PSAP jurisdictions, Access Infrastructure Providers (AIP), Service Providers and Data Base Management System Providers (DBMSPs) in reporting and resolving discrepancies that occurred during a 9-1-1 call. These processes are meant to standardize ANI/ALI Trouble and “No Record Found” reporting to facilitate their timely resolution. An ANI/ALI Trouble is defined as a wrong ANI, no ANI or an ALI Discrepancy, which includes “No Record Found”. This document takes into account all the technologies available for 9-1-1 calls to date. Due to the various ways these technologies deliver 9-1-1 calls to PSAPs, there are various timelines for resolution of discrepancies.

This “NENA Company ID Registration Service Technical Information Document” defines the Company ID program and provides instructions for companies to register their company identification.

This document sets forth recommended NENA standards for all Local Service Providers involved in providing dial tone to end users.

Recent technical developments make it possible for Private Branch Exchange Telephone Systems (PBX) to provide Telephone Station level Automatic Number Identification (ANI). This NENA Technical Reference defines the requirements and methods to accomplish the provisioning of Private Switch 9-1-1 (PS/911) data in conjunction with the use of a Multi Line Telephone System (MLTS) or Private Branch Exchange (PBX) telephone system. For the purpose of this document and to be consistent with other NENA documents, a Private Branch Exchange telephone system or PBX will be referred to as a Multi-Line Telephone System or MLTS.

Recent technology innovations have made it critically important for organizations to address the challenge of identifying the location of the users of communications systems during emergencies in the Multi Line Telephone System1 (MLTS) environment. This paper and the accompanying diagrams will discuss many of the issues related to the location of individuals during emergencies in the MLTS environment. It will further outline the current suggested methods of dealing with the challenge using commonly available technology as recommended in this document by NENA.

DOCUMENT RENUMBERED TO 71-501 Version 1.1, September 8, 2009
Please see the current version

With the implementation of NG9-1-1^(?) there will be many forms of additional data available to emergency responders. This document covers the use of additional data associated with a call, a location, a caller and a PSAP. Together with the SIP Invite and PIDF-LO, additional data associated with a call has the ability to look at other data sources; i.e., Vehicle Emergency Data Set (VEDS) to assist in determining the appropriate call routing and handling.