With Emergency Services support, when an emergency number is dialed, a Customer Emergency Services ID (CESID) is sent from the system to the Public Safety Answering Point (PSAP). The CESID is used as a key in the Automatic Location Information (ALI) database. The ALI database displays the precise location of the caller, as well as emergency services information identifying the proper medical, fire, or law enforcement agency for the location. It is important to ensure that you communicate all CESID changes to the ALI database (see Coordinating_CESID_with_the_ALI_Database).
Different state or provincial regulations may govern the CESID requirements at your location. Some require a unique CESID for every telephone, and others allow shared CESID if the telephone users are within sight of one another. One dialable directory number is required for each CESID.
The network environment must have all Layer 2 (L2) switches configured for Cisco Discovery Protocol (CDP), Spanning Tree Protocol (STP), or both. The system performs automatic CESID updating for IP devices that are moved to a known location. CESID Logs and CESID Alarms record all CESID-related activity on the system.
Appropriate trunk availability must be maintained for emergency services calls.
Any ARS string can be flagged as an Emergency Services number; commonly used numbers are 911 and 999. Ensure all combinations of the Emergency Services number are programmed appropriately in ARS. For example, if the Emergency Services number is 911 and some users may dial a leading digit (9) to access an outgoing line before dialing 911, program both 911 and 9-911.
The Emergency Services feature consists of the following elements:
(Required) CESID
support.
Sending alarms as Local
Notification of emergency calls to an attendant console or a display
set, where an attendant or set user can view alarm details and clear alarms.
Sending emergency response notification to a Mitel Emergency Response Adviser. For information about this product, refer to the Emergency Response Adviser documentation.
