Driver configuration
Open the Drivers (ALERT -> Configuration -> Communication -> select tab Drivers).
Double click the Generic EspaX Driver to open its configuration.
Add a new driver instance, by clicking the Add button above.
You will find the description of the numbering below.
- the driver name of the driver instance, there can be more than one ESPA-X driver
- Sending message timeout in seconds, if there is no response within that time of the ESPA-X server
ALERT will rasie an alarm or switch to the other/secondary server - The trace in file activation
- ESPA-X master server IP address
- ESPA-X slave server IP address
- ESPA-X master server TCP/IP Port inbound/outbound
- ESPA-X slave server TCP/IP Port inbound/outbound
- The redundancy isn't implemented yet, it will be done soon
- Alarm server activation
If ALERT's ESPA-X client is used to transmit alarms to an alarm server only, then the according
check box must be activated "ESPA-X alarm server connection activation". Please note that the sending of user messages is not allowed in this mode. - Server timeout: sending out hearbeats in the specific time to check if the ESPA-X server is alive
- Reconnection timeout: the delay to reconnect to the server if the connection has been lost
- Tag/alarm reference of ALERT to rasie an alarm when the connnection is lost
- ESPA-X client name: e.g. the client name of the ALERT server (ESPA-X ALERT Client)
- The user name to authenticate at the ESPA-X Server
- The password according to the user account of the ESPA-X Server
- Alarm call acknowledgement
Manual, the user have to acknowledge (ack) manually by his handset
Auto, the call will automatically acked if the alarm message was sucessfully transmitted - Message call acknowledgement, see 16.
- ALERT doesn't support to be act as an ESPA-X server yet
User configuration
With the ESPA-X protocol, it is possible to do individual calls or group calls.
Please note: individual calls are not available with DAKS-Pro before Release 8.
Therefore, all calls have currently to be handled via group calls.
To do a group call, add the prefixing "G" to each call number, e.g. G0049707163975.
Group call must be configured in the ESPA-X server by an administrator. If you need to do individual call, then you need to define the user number as a group in the ESPA-X server.
Please communicate this with the ESPA-X administrator on site.
Priorities
The ESPA-X protocol allows managing 5 kinds of priorities (child element <CP-PRIO>):
- Emergency = Emergency, very urgent
- High = High
- Medium = Medium
- Standard = Standard
- Low = Low
It is possible to assign the priority of the alarm to the priority of the call. It should be done in the ESPAX.ini file with the following tags:
- Priority: the global priority, this parameter can assume one of the above priorities and applies to all alarms in ALERT. This parameter must be set after the configuration, otherwise no priority will be transmitted to the ESPA-X Server. Or leave it blank to use the mapping below (see sample).
- PrioEmergency: Values of the priorities for an Emergency call
- PrioHigh: Values of the priorities for a High call
- PrioMedium: Values of the priorities for a Medium call
- PrioStandard: Values of the priorities for a Standard call
- PrioLow: Values of the priorities for a Low call
The priority assignment must be in the following format, comma "," separated with no spaces,
the ranges, minus "-" separated, also without spaces.
Samples
Priority: Emergency
All the message are sent with an emergency call priority.
Priority:
PrioEmergency: 1,2,3,7-9
PrioHigh: 10-15
PrioMedium: 16,17
PrioStandard: 40-43
PrioLow: 21,22-23,24-30
Alarms with priority 1,2,3 and from 7 to 9 (include) are sent with an emergency call priority.
Alarms with priority from 10 to 15 are sent with a high call priority.
Alarms with priority from 16 to 17 are sent with a medium call priority.
Alarms with priority from 40 to 43 are sent with a standard call priority.
Alarms with priority from 21 to 30 are sent with a low call priority.