# Message destinations

Configure here the destinations for event messages and assign them to an event table. Then you can check the configuration by sending a test event message.

In this view, you will have an overview of possible message destinations and see whether they are activated or not . Clicking on one of the icons on the left side gives you access to the configuration of the individual message destinations so you can assign them to an event table and send a test event message.

After a first start, all event tables are assigned to a message destination. (Exception: Local destination and SNMP destination use this event table.) You can assign event tables to several or no message destinations

Table 1. Message destinations
Fee multiplier value | Charges
System phone 1 | Event messages are sent to all system phones with display, which have been entered in message group or 16. See Services / Message/Announcement group view. The allocated event table 1 (default) is preconfigured for common use.
System phone 2 | Event messages are sent to all system phones with display, which have been entered in message group 15. See Services / Message/Announcement group view. The allocated event table 8 (default) is preconfigured for front desk terminals in hospitality environments.
E-mail destination | With the e-mail client integrated in the communication server, event messages can be sent to internal or external e-mail destinations. The condition for this is that the access to the SMTP server of the e-mail service provider must be set (see IP network / SMTP server view).
SNMP destination | SNMP stands for "Simple Network Management Protocol" and is used by Network Management Systems (NMS). If the Network Management System is to know the potential events of the communication system, the corresponding system components have to be defined in the form of configurable objects (Managed Objects: MO). These objects and the related event messages are stored in an object library referred to as the Management Information Base (MIB). The current MIB version can be downloaded from https://pbxweb.aastra.com The user name and password are required in order to access the data. For this, a registration with "Mitel Application Partner Programme" must be available.
Event log | Event messages are recorded in WebAdmin in the Maintenance / System events / Event log view. The last 254 event messages are visible. Active event messages and the last 10 Power failures are recorded in separate logs. If the maximum number of entries is exceeded, the oldest entry in each case is deleted. If active event messages are available, they are indicated on the left under the menu tree, with the symbol.
Local destination | Event messages are sent to a local IP destination (PC) via an Ethernet connection or via a temporary PPK communication channel (a terminal adapter or modem). Note: Event tables and signal destinations should be set in such a way that the event message External event message destination missing is signalled immediately to any signal destination still available.
External destination | Event messages are sent to an external IP destination (PC) via a temporary PPK communication channel (a terminal adapter or modem). Apart from a primary IP destination, an alternative IP destination can also be indicated. The following principles govern the way event messages are signalled to an external signal destination: Individual event messages are not signalled if they occur at short intervals. The event messages are stored temporarily for 5 minutes and then sent together to the external signal destination. If over a period of one hour an attempt is made unsuccessfully to send the event messages to the external signal destination, the signalling period is extended from 5 minutes to 4 hours. As soon as the event messages are successfully output at the external signal destination, the time period is reset to 5 minutes. If over a period of 1 hour an attempt is made unsuccessfully to send an event message to an external signal destination, the number of dialling attempts is reduced from 5 to 2. As soon as an event message has been successfully sent, the number of dialling attempts is increased to 5 again. If the attempt to send an event message to an external signal destination was unsuccessful, the system will generate the event message External event message destination missing. Note: Event tables and signal destinations should be set in such a way that the event message External event message destination missing is signalled immediately to any signal destination still available.
Alarm server (ATAS) | At this message destination, event messages are sent to an alarm server using the ATAS protocol. This may be an Mitel Alarm Server or a third-party alarm server. The use of the ATAS protocol is subject to a licence.
SRM destination | Event messages can also be sent to the SRM server. Depending on the severity level in the SRM agent, this changes the system status on the corresponding communication server line. The line colour changes at the same time. If the corresponding positive event message arrives later or if the event message is confirmed in WebAdmin, the status and colour are restored again. The following system statuses are defined: Normal (Blue colour): No active event messages with the severity level Serious or Critical is available. Serious (Yellow colour):At least one event message is available and needs to be closely examined. (Example: Charge counter overflow) Critical (Red colour)At least one event message is available and is hampering the system's function.(Example: Fan failure) Note: Not all negative event messages have a positive match. In this case, the event messages must be confirmed manually in WebAdmin. Event messages, which are not Serious or Critical, are not sent to the SRM server. The severity of individual event messages is given in the "Event types, in alphabetical order" table.

## System phone

Configuration:

1. Link the message destination with the event table you want.

2. In the linked event table, configure the filter criteria you want for all events.

3. Test the configuration by clicking the Send test event message button.

Note:

The message destination System phone cannot be activated or deactivated. Once system phones are entered in Message group 8 or 16, event messages are issued according to the filter criteria of the linked event table on the system phones.

## E-mail destination

Configuration:

1. Click on the button to define up to five E-mail addresses, each with a Subject.

2. Activate the e-mail destination.

3. Link the message destination with the event table you want.

4. In the linked event table, configure the filter criteria you want for all events.

5. Under Text language choose the language in which the event messages will be displayed at the destination.

   Note:

   The choice of language also applies to the output at the local destinations and system phones.

6. Test the configuration by clicking the Send test event message button.

## SNMP destination

Configuration:

1. Click on the button to define up to five SNMP destinations, by entering respectively Name, IP address or Host name and Port.

2. Activate the SNMP destination.

3. Link the message destination with the event table you want.

4. In the linked event table, configure the filter criteria you want for all events.

5. Define the Service port.

6. Test the configuration by clicking the Send test event message button.

Note:

The SNMP destination is linked with the same event table as the local destination. Any changes to the link and/or filter criteria for the linked event table also apply to the local destination.

## Event log

1. Link the message destination with the event table you want.

2. In the linked event table, configure the filter criteria you want for all events.

3. Test the configuration by clicking the Send test event message button.

Note:

- Normally, the signal destination event log is assigned to Event table 4. The filter on this event table is preconfigured for most event types in such a way that event messages are entered in the event log once they arrive.
- The message destination Event log cannot be activated or deactivated.

## Local destination

Configuration:

1. Activate the local destination.

2. Link the message destination with the event table you want.

3. In the linked event table, configure the filter criteria you want for all events.

4. Choose the output Format.

5. Under Text language choose the language in which the event messages will be displayed at the destination.

   Note:

   The choice of language also applies to the output at the e-mail destinations and system phones.

6. Under IP destination choose the Connection type and configure the corresponding parameters.

7. Test the configuration by clicking the Send test event message button.

Note:

The local destination is linked with the same event table as the SNMP destination. Any changes to the link and/or filter criteria for the linked event table also apply to the SNMP destination.

## External destination

Configuration:

1. Activate the external destination.

2. Link the message destination with the event table you want.

3. In the linked event table, configure the filter criteria you want for all events.

4. Under Primary IP destination and under Alternative IP destination choose the Connection type then configure the corresponding parameters.

5. Test the configuration by clicking the Send test event message button.

## Alarm server (ATAS)

Configuration:

1. Activate the alarm server destination.

2. Link the message destination with the event table you want.

3. In the linked event table, configure the filter criteria you want for all events.

4. Test the configuration by clicking the Send test event message button.

## SRM destination

Requirement: The SRM server connection is set up.

Configuration:

1. Activate the SRM destination.

2. Link the message destination with the event table you want.

3. In the linked event table, configure the filter criteria you want for all events.

   Note:

   Event messages, which are not Serious or Critical, are not sent to the SRM server. Please bear this in mind while configuring the connected events table. The severity of individual event messages is given in the "Event types, in alphabetical order" table.

4. Enter the IP address or Host name of the SRM server.

5. Use the default value (443) as Port.

6. For the parameter Host basic Uri, enter srm.

7. Enter any user name and password. The password must contain at least 8 characters with 2 special characters.

8. In a browser window, connect to the SRM server then click Edit for your system.

9. Go to the Login information tab and activate the option Allow status modifications by remote system.

10. Enter the same user name and password as you did under Point 4 in WebAdmin.

11. Start the SRM agent and search your system.

12. Return to WebAdmin and test the configuration by clicking the Send test event message button.

    -> The system status should change from Normal to Serious, and the line colour from blue to yellow.

Parent topic: Settings
↑