The CESID (Customer Emergency Services ID) must be a valid public network 7 or 10 digit Listed Directory Number.
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 3300 ICP in the network.
CESID tagging is only supported on ISDN PRI trunks from standalone systems or from within MSDN MITEL Services 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.
CESIDs are not associated with location independent entities such as ACD agents and Hot Desk users. If an ACD agent or Hot Desk user makes an emergency services call, 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 is not supported on hubs where multiple devices report connectivity to the same L2 port, or on L2 switches that do not have CDP or STP enabled. The system detects and logs this condition upon device registration.
The 3300 ICP 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, the 3300 ICP 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 the 3300 ICP. 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 CDP and STP 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 the 3300 ICP. 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) The 3300 ICP 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
YA Pro softphones. The YA Pro cannot detect L2 connectivity data.
Wireless devices
Note: Device move detection and CESID updating are not supported on non-IP devices.
