RedSky :: The Leader in E911 Solutions
  • RedSky :: The Leader in E911 Solutions :: Solutions
  • RedSky :: The Leader in E911 Solutions :: Products
  • RedSky :: The Leader in E911 Solutions :: Services
  • RedSky :: The Leader in E911 Solutions :: Knowledge Base
  • RedSky :: The Leader in E911 Solutions :: E911 Center

E911 for Digital and Analog Phones

Comprehensive E911 protection requires proper configuration of and integration with all call servers, PBXs and gateways on the network.

There are two key requirements for E911 – the ten-digit number (ANI/ELIN) that is out-pulsed by the PBX/call server and the Automatic Location Identification data record (ALI/ERL) that is stored in the regional database. For E911 to work, three things need to happen to tie these two components together.

1) The PBX/Call Server must be configured to out-pulse the proper ten-digit (ANI/ELIN) number of the 911 caller. This is usually the DID number of the caller.

2) Local ISDN-PRI or CAMA trunks must be implemented to send the ANI/ELIN over the Public Switched Telephone Network (PSTN) to the local Public Safety Answering Point (PSAP).

3) The regional ALI database must be populated with the ALI records that contain the detailed location information associated to each ANI/ELIN.

When 911 is dialed, the 911 dispatcher at the local PSAP receives the ANI/ELIN, which accesses the regional ALI database to pull up the detailed ALI record defining the exact address and location of the caller.

For purposes of illustration, here is a diagram of how an emergency call is handled when placed from a traditional PBX/Call Server-based phone system equipped with RedSky's E911 Manager™.

E911 Manager PBX