Operation and Maintenance
268
Aastra 470 ab R3.0
syd-0337/1.5 – R3.0 – 05.2013
These 4 Event Logs protocols are not printed out automatically; likewise, your at-
tention is not drawn to any incoming event message. The protocols have to be re-
trieved manually in the Fault & Maintenance Manager or printed out.
See also:
Event messages entered in the protocols of the Event Logs can also be
retrieved on the Office 45 using the System Assistant function on
Office 45 (see "Maintenance menu on the Office 45", page 275).
E-mail signal destination
With the e-mail client integrated in the communication server, event messages can
be sent to internal or external e-mail destinations. After a first-start of the commu-
nication server, the signal destination E-mail destination is automatically allocated
event table 5. Up to 5 e-mail destinations can be defined in the Fault & Mainte-
nance Manager, and e-mail notification can be activated or deactivated globally.
For the communication server to send the e-mails, the IP address or the host name,
the port and, where necessary, a user name with password must be configured un-
der SMTP server in the Configuration Manager.
Alarm server destination (ATAS)
Event messages can also be sent via the ATAS interface (e.g. to an alarm server). Af-
ter a first-start of the communication server, the signal destination Alarm server des-
tination (ATAS) is automatically allocated event table 6. In the Fault and Mainte-
nance Manager, the notification service can be switched on or off globally via the
ATAS interface on the alarm server.
Testing the signal destination configuration
To test the configuration, you can trigger a test event message via the Fault & Main-
tenance Manager. The event message is signalled without any delay, directly at the
selected signal destination.
If the communication server is connected with AMS via a TA, the test event mes-
sages will be signalled only once the connection is cleared down.
To Next Page
Loading...
