# Emergency Services - CESID Conditions

WARNING: MiVoice Business 6.0 supports CESIDs up to 12 digits in length. This may have safety (and legal) implications in networks of older releases which only support 10-digit CESIDs. If you plan to use the longer CESIDs, you are strongly advised to upgrade the entire network to support the longer CESIDs first. Failure to do so could lead to emergency calls having incorrect CESID information in certain cases. For example, consider a hot desk user who is provisioned on a MiVoice Business system that uses 12-digit CESIDs who then logs in using a DN on a 10-digit MiVoice Business system. Because a hot desk DN uses the CESID assigned to the registration (login) DN for emergency call purposes, such calls will contain an incorrect CESID: instead of 12 digits, it will have only 10 (the last two are truncated) and the emergency route preference used will be "Through System Only," although the registration DN preference may be something else. The same scenario applies to resilient devices. Both the primary and secondary MiVoice Business system should be upgraded to avoid mismatched CESID lengths under failover/failback conditions.

- The CESID (Customer Emergency Services ID) must be a valid public network Listed Directory Number from 7 to 12 digit in length.

- A minimum of one L2 connectivity detection protocol (STP, or CDP) must be uniformly and consistently configured on all the L2 switches that the devices are connected to. The administrator must define the same protocol of choice for each MiVoice Business system in the network.

- CESID tagging is supported on ISDN PRI trunks from standalone systems or from within MSDN
  MITEL Superswitch Digital Network networks, which includes systems networked using IP trunks. If there are transit systems between the caller and the outgoing ISDN trunk, the CESID is propagated through the network to the PSAP
  See Public Safety Answering Point. (MSDN networks only). Sites without ISDN capability should route emergency calls to an attendant or security.

- If ISDN is programmed to block calling number ID, it will ignore this and send the calling number for emergency service calls.

- CESID is supported on SIP trunks.

- CESIDs are not associated with location independent entities such as ACD agents and regular Hot Desk users. If an ACD agent or regular Hot Desk user makes an emergency services call, the CESID associated with the originating set is sent.

- For EHDUs logged on to private trunks (such as a Suite EHDU), the CESID associated with the user’s mobile DN is sent. For EHDUs logged on to public trunks (such as cell phone), the external party’s public number is sent as the CESID. For EHDUs logged in over public trunks that provide no calling line identify, the EHDU configured external number is sent as the CESID.

NOTE: An EHDU external number configured with *, # or P characters cannot be used for the CESID. For EHDUs logged in internally (such as a Minet device), the CESID associated with the originating set is sent.

- Class of Restriction and Interconnect Restrictions remain in effect for emergency services calls. Specific users may be restricted from accessing the designated Emergency Services number.

- SMDR output and HCI events are changed in the event of an emergency services call; the prime directory number of the originating station is output.

## Automatic CESID Updating

- Automatic CESID updating is not supported on hubs where multiple devices report connectivity to the same L2 port, or on L2 switches that do not have STP, or CDP enabled. The system detects and logs this condition upon device registration.

- The MiVoice Business portion of the Mitel Emergency Services solution does not support handling of "special circumstance" DNs. Some DN users have special needs: for example, a DN may be associated with a wheelchair user or with an area where dangerous chemicals are stored. The PSAP may have a record associating a user or DN with this type of special circumstance. If such a device is moved, MiVoice Business treats it like any other device move and attempts to automatically update the CESID Assignment form. This causes the PSAP database to be out of sync with MiVoice Business. To avoid this situation, the administrator should ensure that such DNs are not allowed to move.

- Automatic CESID updating does not function during a database backup or restore.

- A log is generated if the system detects a conflict between STP, and CDP data.

- Automatic CESID updating should not be enabled for

- Devices in Teleworker mode or devices that are connected outside of the corporate firewall. 911 calls placed from such devices may report an incorrect CESID, or may be outside of the PSAP's coverage area. Devices are not compatible with the Mitel Emergency Services solution when they are operating outside the corporate network serviced by MiVoice Business. The reasons are as follows:

- 1. A Teleworker device operating outside the corporate network may or may not trigger a device move;

  2. The system will not be able to accurately assign a CESID to such a device outside the network;

  3. MiVoice Business will not be able to route the 911 correctly. Note that the system will not block the Teleworker device from making 911 calls, even if they are outside the corporate network. It is not recommended that users make 911 calls from devices operating in Teleworker mode outside the corporate firewall. It is best if the administrator change the CESID Updating state manual for Teleworker enabled devices.

- Generic SIP phones and the 5302

- Wireless devices

NOTE: Device move detection and CESID updating are not supported on non-IP devices.

## Location Based Call Routing

The Location Based Call Routing feature allows you to program the system to route emergency calls to services local to the device from which the user dials. For example, when a Chicago-based Hot Desk user logs into a device in New York and dials 911, the system routes the call to the New York Public Safety Answering Point (PSAP), not the Chicago PSAP.

Related Topics

- Emergency Services - CESID Support Description

- Emergency Services - CESID Guidelines

- Emergency Services - CESID Programming

- Emergency Services - CESID Maintenance

- Location Specification