# CESID Assignment

## Purpose

The CESID Assignment form is used to assign a Customer Emergency Services ID (CESID) number to each prime directory number in the system. You can also use this form to assign CESID numbers to mobile users who log in from external locations. The CESID is sent to the Public Safety Answering Point (PSAP) in the event of an Emergency Call and is used as a key in the Automatic Location Information (ALI) database to pinpoint the precise location of the caller.

Use this form to perform the following tasks:

- Assign CESID Default Parameters

- Emergency Services - CESID Programming

- Program Emergency Services for a Line Interface Module

- View CESID Logs

For more information about the Mitel Line Interface Module (LIM):

- Line Interface Module Emergency Services Operation

## 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.

## Field Descriptions

Parameter | Description | Default Value
CESID key | System-generated, protected field. Uniquely identifies the CESID instance. |
Number | System-generated, protected field. Contains a list of all programmed prime directory numbers and mobile directory numbers in the system. These numbers include MiVoice IP Phones, ONS sets, Attendants, regular Hot Desk Users, and External Hot Desk Users (EHDUs). |
Name | System-generated, protected field. Contains the name programmed in the telephone directory against the corresponding prime directory number. |
Last Known <STP or CDP> L2 Port MAC | System-generated, protected field. Displays the MAC address of the Layer 2 switch port where the IP device is currently connected. If "Unstable" appears in this field it means that the device is receiving conflicting L2 MAC or Chassis ID and Port data. This issue can occur if the device is connected to an L2 switch that doesn't have STP, CDP enabled, but the network components higher up in the network tree have STP, CDP enabled. Therefore, the L2 broadcast from the switch higher in the network tree gets passed though the lower L2 switch and the phone receives L2 data from multiple sources. |
Last Known <STP, CDP > Port Identifier | System-generated, protected field. Displays the STP, CDP, (whichever is configured as the primary protocol in the "L2 Connectivity Detection Protocol" field) port number on the Layer 2 switch port where the IP device is currently connected. If the port number cannot be displayed, you may see one of the following messages: "Not Supported" - Indicates that the L2 switch does not have the primary protocol enabled. "Not Applicable" - Indicates a non-IP device. L2 fields do not apply. "Never Registered" - Indicates an IP device that has been programmed with the system but has never registered through an L2 connection point. The "CESID Updating" field will default to "Automatic" (the administrator can change this setting). "Unknown" - Indicates an IP device that has been programmed in the system, but when the device registered, the device did not have the firmware load required for connectivity detection. A CESID alarm is generated for this device. "Unstable" - It means that the device is receiving conflicting L2 MAC and Port data. This issue can occur if the device is connected to an L2 switch that doesn't have STP, CDP enabled, but the network components higher up in the network tree have the protocol enabled. Therefore, the L2 broadcast from the switch higher in the network tree gets passed though the lower L2 switch and the phone receives L2 data from multiple sources. |
CESID | Enter the CESID to be sent to the PSAP in the event of an emergency call. Up to 12 digits can be programmed. See the above Warning for important information regarding CESID length in a mixed release network. NOTE: Although a CESID can be programmed for any mobile DN, the system will only use it for External Hot Desk Users (EHDUs) that are logged on to private trunks. For regular hot desk users and EHDUs logged on to MiNET devices, the system will use the CESID associated with the set's registration DN. | Blank
CESID Comments | Enter location information for the specified person to present to the attendant console or other designated emergency answering point. This field is for internal use only and is not sent to the PSAP. You can fill in this field only if you enter a CESID. CESID Comments 'follow' the user DN when the DN is moved to a different L2 port provided the port supports CESID. | Blank
CESID Updating | Select Manual to turning off automatic CESID updating on a per-DN basis. DNs set to Manual will not have their CESID updated automatically or cause a CESID alarm when a CESID is detected missing. | For devices that support location detection, the default is Automatic. The default for other devices (for example: ONS, Generic SIP Phones, 5302 IP Phone, or wireless sets) is Manual, and the field is read-only.
Route Emergency Calls | Select one of the following: Through System Only - The default handling for emergency calls from sets without a Line Interface Module attached. Programming a set which has a Line Interface Module attached with through system only preference will result in emergency calls always being routed through the system. Through Analog Line First - In the event of an emergency call, the system will try to route the call through the analog line and if unsuccessful will route it through the system. Through Analog Line Only - In the event of an emergency call, the only option for routing the call is through the analog line. If the call cannot be made through the analog line, then failure handling is applied. | For systems without LIM the default is Through System Only.