# Configuring the system for the emergency service support

In general steps are optional. The less is configured the less accuracy of the emergency location is available up to no information if nothing is configured.

1. Create the required internal emergency response teams and add members (users) to the teams. Tick the e-mail checkbox if the members should receive an additional e-mail notification. An emergency response team could be responsible for several locations, but if the locations are far apart, then several such teams are required.

2. Create and name an emergency data location data set for each location, including the official emergency location identifier, the route to be used for the emergency call and an info text to be displayed to the internal emergency response teams and/or the Hospitality Manager. Add additional e-mail addresses if needed.

3. If LCR is used in the system configuration, make sure that in all routes used for emergency calls, the checkbox Supress LCR is ticked.

4. Assign an emergency location to the whole system. This is useful for small systems, when all terminals share the location identifier (are situated at the same place).

5. Assign an emergency location to all AIN nodes. This is useful when each building is served by its own AIN node.

6. Assign an emergency location to all DECT radio units. This is useful when radio units are spread across several buildings but (because of synchronization issues) are all connected to the same AIN node.

7. Define a table of IP address ranges and assign an emergency location to each range. This is useful when the IT department assigns each building / floor / office a different range of IP addresses and therefore the communication server can determine the emergency location from the IP address, even if the terminal moves around.

8. Assigns an emergency location to individual terminals. This is useful if certain terminals do not follow the rule for the AIN node they are connected to or for SIP or IP terminals that are installed at fix locations but not at the masters location.

9. The company’s IT department configures their switches so that they provide the emergency location identifier to the Mitel SIP phones via the LLDP protocol. This can be used when the switches support it. Then the user can just move his Mitel SIP terminal from one place to another and the emergency location is automatically adapted.

10. Configure for all trunk groups that are used for private networking purposes a default location identifier. This is assuming that all calls from there reside in the same location.

11. Configure for all trunk groups that are connected to the public network which protocol shall be used to send the emergency location identifier to the provider. Note that this setting is dependant of the networking type, the provider and the country

12. Configure all emergency numbers, for which a location identifier has to be send out, in the public emergency number list. When the routing detects, that one of these numbers is dialled, it determines the correct emergency location identifier for the calling terminal and includes it in the outgoing call. Avoid conflicts of public emergency numbers with the internal numbering plan.

Parent topic: Function codes and services
↑