Aastra 415 - Event Tables

Operation and Maintenance
229
Aastra 415/430 as of R3.2
syd-0344/1.6 – R3.2 – 09.2014
6. 5. 1. 2 Event tables
Event tables ( =f4)list all the event messages the system is capable of generating
(see Tab. 100).
There are 6 event tables. After a first start, all event tables are assigned at least one
destination. This assignment can be modified in the Message destinations ( =h1)
view. Each event table can be configured individually. This means it is possible with
a filter to decide which event message – if any – should be sent to a particular sig-
nal destination either immediately, with a delay or not at all.
• No event:
This type of incoming event messages are never sent to the linked destination.
• Every event:
This type of incoming event messages are all sent to the linked destination.
• Custom:
With this setting, you can determine how often the event message may appear
for each period, until they are sent to the linked destination.
The Frequency of an event message may range between 2 and 20. The Period is
indicated in hours, ranging between 1 and 672. The longest time period corre-
sponds to 28 days or 4 weeks.
09 Invalid host, domain or IP address on
the communication server
Prepare authentication
(LOGIN)
10 E-mail text too long (body) User name authentica-
tion (LOGIN)
11 E-mail attachment too large Password authentica-
tion (LOGIN)
12 Format of e-mail attachment not
supported
Authentication (PLAIN)
13 No e-mail recipient address Prepare encrypted
authentication (CRAM-
MD5)
14 Invalid e-mail recipient address Encrypted authentica-
tion (CRAM-MD5)
15 Invalid e-mail sender address Preparing to send next
e-mail
1)
Action carried out by the SMTP client at the point when the error occurred.
Parameter 1 (XXYY) Parameter 2: Parameter 3:
Value Reason (XX) Action (YY)
1)
E-mail client
Additional info
depending on the
e-mail client
(XXYY)