# Emergency Services - CESID Programming

NOTE: For information about updating CESIDs, see CESID Maintenance.

## Program a CESID

You must program a CESID for each DN in the network, or for each device, or for each network zone, or at least a default value for the whole system. When determining the CESID for an emergency call, the system searches appropriate forms in the following order:

For MiNet IP devices:

1. L2 to CESID Mapping form (CESID associated with a device)

2. CESID Assignment form (CESID associated with a Directory Number)

3. Zone CESID field in the Network Zones form (CESID associated with a zone)

4. Default CESID form (default CESID associated with the whole system)

For TDM devices (and devices that do not have associated zones), and for non-Minet IP/SIP devices:

1. Directory Number (CESID Assignment form)

2. System (Default CESID form)

For SIP trunks:

- SIP trunks originating 911 calls use the CESID number in the From: header by default. If the Signal Privacy (if enabled) on Emergency Calls field in the SIP Peer Profile form is set to 'Yes', the CESID number is included only in the P-Asserted-Identity header and not in the From: header, when an emergency call is made from an extension with privacy enabled. In this case, the From: header will have "Private" name and "Anonymous" user instead of the user name and CESID number.

### To program CESIDs

1. Class of Service Options form

- Enable "Display ANI/ISDN Calling Number Only".

2. Program the ARS for the ISDN trunks.

- Trunk Attributes form

Assign the ISDN trunks in the

- Trunk Groups form

Put the trunks into a trunk group.

- ARS Routes form

Assign the Trunk Group to a route and designate the route as an Emergency route by selecting Emergency from the Route Type list.

- ARS Digits Dialed form

Add an entry for "911" (digits dialed 911, no digits to follow), and point this to this route.

NOTE: There are additional considerations if multiple emergency dialing strings are necessary for different geographic regions within a cluster. Emergency dialing strings must be COR restricted if the telephone set location is not served by the PSAP.

3. Program CESID information, using one of the following forms:

- CESID Assignment form

Assign a CESID number to each primary extension number, which can be either a registration or mobile directory number. The MAC address of the Layer 2 switch and the Layer 2 switch port identifier are detected by the system when an IP phone registers.

NOTE: You also have the option of manually assigning the MAC Address and port identifier to the Layer 2 switch ports in the L2 to CESID Mapping form. However, it is recommended that you allow the system to detect the address since this method is less prone to error.

- L2 to CESID Mapping form

Assign a CESID number to a device.

- - The "L2 Port MAC/Chassis ID" field displays the port MAC address of the Layer 2 switch. The MAC address is detected by the system when an IP phone registers. You also can manually assign the L2 switch port MAC addres during an Add operation, but not during an Edit operation.

  - The "L2 Port" field displays the identifier of the port. The port identifier is detected by the system when an IP phone registers. You can also manually assign the L2 switch port identifier during an Add operation, but not during an Edit operation.

  - Assign a CESID to each Layer 2 switch port.

- Network Zones form

Assign a Zone CESID number to each network zone. This programming is particularly important for Location Based Call Routing. Since the Network Zones is a shared form, if an emergency call is routed to a different zone, the system will still be able to retrieve the CESID information and locate the calling device, using the Default Zone ID.

- Default CESID form

Assign a default CESID number for the whole system.

## CESID in Clustered Environments

To propagate CESID over IP trunks in a clustered environment, the IP trunks need to be in the ARS route designated as an emergency route in the ARS Routes form.

## Modify a CESID

CESIDs are modified in the CESID Assignment form.

NOTE: For IP devices that have automatic CESID updating enabled, the system updates the L2 to CESID Mapping table with the new CESID when the IP Phone registers at a known location and automatically updates the CESID in the CESID Assignment form.

To manually modify a CESID

- CESID Assignment form

- Select the entry to modify, and click Change Member.

- Enter the new CESID and/or CESID Comments, and click Save.

## Add/Modify/Delete L2 to CESID Mapping

You can manually add, modify, or delete the CESID for a DN in the L2 to CESID Mapping table. We recommend that you do not manually enter information; however you may use this table to ensure that every port is assigned a CESID.

To add an entry to the L2 to CESID Mapping form

- L2 to CESID Mapping form

- Click Add.

- Enter the L2 Port MAC address, L2 Port number, and CESID.

- Click Save.

To modify an L2 to CESID Mapping

- L2 to CESID Mapping form

- Select an existing entry, and click Change.

- Enter the new CESID, and click Save.

To delete an L2 to CESID Mapping

- L2 to CESID Mapping form

- Select an existing entry, and click Delete.

NOTE: If a DN is deleted from the system (for example, through the 3300 System Administration Tool), the DN is automatically deleted from the CESID Assignment form; however, since the corresponding L2 to CESID Mapping may still be a valid mapping, the system does not delete any entries from the L2 to CESID Mapping table when a DN is deleted.

NOTE: The CESID can now be used as a location identifier (LID) and is no longer a dialable PSTN number. The Called Party Number (CPN) used as the callback number, when the call drops, will now use the callers current CPN configuration on the MiVoice Business or a Callback number assigned/allocated on the Vendor portal.

Related Topics

- Emergency Services - CESID Support Description

- Emergency Services - CESID Conditions

- Emergency Services - CESID Guidelines

- Emergency Services - CESID Maintenance