# Emergency location data sets

For each emergency location, a data set must be set up. This data sets are then assigned to terminals. In this wav, the communication server is able to send the location identifier to the provider connected with an PSAP (Public Safety Answering Point).

For each emergency location, whether it is a building, an out side area, a floor in a building, a room in a floor, or even a single phone on a desk, an emergency location data set must be set up.

Table 1. Emergency location a data set
Destination | Explanation
ID | ID of the data set.
Name | Short name or description
Do not send the 'Emergency location identifier' | Prevents sending the emergency location identifier to the provider. This is useful for integrated mobile phones or other external phones, which are not static on a certain location.
Emergency location identifier | This is the string (max. 30 chars) sent to the provider.
Municipality identifier | Identifies the ZIP code associated with the originating call location. This value is appended to the location ID to form the Calling Line Identification (CLI) information in the outgoing SIP header (If the Trunk groups are configured to append the value to the location ID, see "Editing the trunk groups".
Route | Route to be used for the outgoing call. If empty, the route defined at the user will be used.
Info | Define a more detailed info text here, which is sent to the internal emergency response team.
Internal emergency response team | Assign an internal emergency response team here. The team, or rather their terminals, are alerted with a message/pop-up on their screens and a loud alarm/ringing noise.
Hospitality Manager | A message/pop-up appears in the Hospitality Manager application together with a loud alarm/ringing noise.
Alert e-mail address list (comma separated) | For additional notifications, comma separated e-mail addresses can be defined here.

See also...

## Focus topic

"Emergency service support"

Parent topic: Emergency calls
↑