ESQK Guidelines for VoIP

NENA formed an Ad Hoc Working Group to address and provide guidance on VoIP E9-1-1 deployment issues that need a national approach – specifically Emergency Services Query Key (ESQK) assignment methods.  

First and foremost, it is recognized as a preliminary matter that full compliance with the NENA Interim Solution (i2) recommended standard may not be completely feasible in initial deployments, due to dependency on establishing the core Interim Solution functions, such as Validation Databases (VDBs) and Emergency Services Zone Routing Databases (ERDBs) and associated Root Servers nationally. This should not delay initial VoIP E9-1-1 service or delay subsequent efforts and commitments to reach full i2 compliance and wireline equivalent service levels within a reasonable time as i2 capabilities become available.  Second, it is also recognized that additional immediate guidance is needed related to the assignment of ESQKs, which are central to the provision of E9-1-1 for VoIP services.

NENA formed an Ad Hoc Working Group to address and provide guidance on VoIP E9-1-1 deployment issues that need a national approach – specifically Emergency Services Query Key (ESQK) assignment methods. First and foremost, it is recognized as a preliminary matter that full compliance with the NENA Interim Solution (i2) recommended standard may not be completely feasible in initial deployments, due to dependency on establishing the core Interim Solution functions, such as Validation Databases (VDBs) and Emergency Services Zone Routing Databases (ERDBs) and associated Root Servers nationally. This should not delay initial VoIP E9-1-1 service or delay subsequent efforts and commitments to reach full i2 compliance and wireline equivalent service levels within a reasonable time as i2 capabilities become available. Second, it is also recognized that additional immediate guidance is needed related to the assignment of ESQKs, which are central to the provision of E9-1-1 for VoIP services.

It is not in the scope of this document to explain exact details of any particular 9-1-1 SR, but to act as a way to understand the dynamics of the assignment and use of these routing codes. As stated earlier, this document is secondary to any network disclosure or other translation policy guides from any 9-1-1 System Service Provider. The reader of this document is encouraged to contact the 9-1-1 System Service Provider for any detailed questions on SR translations or policy details.

The Working Group seeks to give the reader the knowledge required to better understand and implement service, using recommended methods that are applicable in the field today