Event log
The last 254 event messages are listed here.
Event messages have a certain severity level: Normal, Serious and Critical. Many event messages have both a negative impact (error occurred) and a positive impact (error corrected). Some event messages have no impact and, thus, no match. Severity level, positive or negative impact (if any) and the information, if there is a match or not, are indicated in the event table.
If an SRM server is indicated as signal destination, the event message severity level results in a change of system status. This can be seen in the SRM agent and is displayed with the corresponding colour (see section "SRM destination").
In the table below all possible event messages are listed with the activation conditions and detailed information on the parameters.
Event message |
Trigger condition |
Details1 |
Severity |
|---|---|---|---|
ATAS: Connection established |
ATAS: connection (re) established |
Date, time |
critical (positive, with match) |
ATAS: Connection lost |
ATAS: connection lost |
Cause (0: Logoff, 1: missing cycle signal), date, time |
critical (negative, with match) |
BluStar Client back within the licence limit |
A sufficient number of licences is now available again for BluStar clients. Parameter 1: 0 (not used) Licence type: 0 and 1: (not used), 2: BluStar CTI, 3: BluStar Softphone, 4: BluStar Video option, 5: BluStar Presence option |
Parameter 1, licence type, total purchased licences, date, time |
Serious (positive, with match) |
Card in service |
A card that was previously out of service is back in service again. |
Number of the expansion slot, date, time |
critical (positive, with match) |
Card out of service |
A card previously in operation has stopped functioning. |
Number of the expansion slot, date, time |
critical (negative, with match) |
Card reset |
A reset was carried out for one card |
Number of the expansion slot, date, time |
Serious (without match) |
Charge counter overflow |
Individual cumulative counter or cost centre counter overflow |
Cause (0: User / 1: Cost centre / 2: Exchange line / 3: Room), number, date, time |
Serious (without match) |
CL printer available again |
Printout on the system printer available once again |
Date, time |
Serious (positive, with match) |
CL printer blocked |
|
Interface, interfaces/card number, port number, date, time |
Serious (negative, with match) |
Compatible PMS application |
The external hotel management system (PMS application) is suitable for communicating with the communication server. |
Date, time |
critical (positive, with match) |
Configuration template available |
The missing configuration template for a Mitel SIP terminal is now available in the communication server file system. |
Date, time |
Serious (positive, with match) |
Connection to IP remote management (SRM) failed |
IP remote management connection set up (SRM = Secure IP Remote Management) has failed. Cause parameter:1: Connection attempt failed, 2: Authentication failed, 3: File upload rejected |
Cause, date, time |
Normal (negative, with match) |
Connection to IP remote management (SRM) restored |
IP remote management connection has been (SRM = Secure IP Remote Management) successfully restored. |
Date, time |
Normal (positive, with match) |
Connection to PMS system established |
A connection with a hotel management system (PMS system) has now been successfully established. |
Date, time |
critical (positive, with match) |
Connection to PMS system failed |
An unsuccessful attempt was made to establish a connection with a hotel management system (PMS system).Reason: 1: Call rejected, 2: Destination unobtainable, 3: Destination busy, 4: Connection timeout, 5: Wrong address, 6: Unknown error |
Error, date, time |
critical (negative, with match) |
CPU2 applications card Data communication out of service |
Data communications with the CPU2 applications card have been interrupted for an unusually long period of time (> 1 hour) due to an error (after a Windows update or for other reasons). |
Date, time |
critical (negative, with match) |
CPU2 applications card Data communications back in service |
Data communications with the CPU2 applications card have been restored. |
Date, time |
critical (positive, with match) |
Creation instance on backup communication server failed |
The backup communication server was unable to create or modify a user or terminal instance with the received configuration data. Note:
This event message is generated by the backup communication server. |
Instance type (0: User, 1: terminal), user number or terminal ID, date, time |
critical (negative, with match) |
Creation instance on backup communication server successful |
The backup communication server was able (following one or more previous failed attempts) to create or modify a user or terminal instance with the received configuration data. Note:
This event message is generated by the backup communication server. |
Instance type (0: User, 1: terminal), user number or terminal ID, date, time |
critical (positive, with match) |
CSTA sessions within the licence limit again |
CSTA Sessions licences are now available again. |
Number of licences, date, time |
Serious (positive, with match) |
CTI first party Connection established |
The first-party link was (re-)established |
User number, terminal ID, protocol type (0=ATPC3, 1=CSTA) date, time |
critical (positive, with match) |
CTI first party Connection lost |
The first-party link was interrupted because the cycle signal is missing. |
User number, terminal ID, protocol type (0=ATPC3, 1=CSTA) date, time |
critical (negative, with match) |
CTI third party: Connection established |
The third-party link was (re-)established |
IP address, protocol type (0=ATPC3, 1=CSTA), date, time |
critical (positive, with match) |
CTI third party: Connection lost |
The third-party link was interrupted |
Cause (0=Logoff, 1= missing cycle signal), IP address, protocol type (0=ATPC3, 1=CSTA) date, time |
critical (negative, with match) |
Definitive activation licence missing |
The initial temporary activation of the communication server for a certain duration (e.g. 90 days) was started. After this period, the communication server switches to restricted operating mode. |
Date, time |
critical (negative, with match) |
Definitive activation licence now present |
A licence file with a definitive activation licence was uploaded. |
Date, time |
critical (positive, with match) |
Dual Homing back within the licence limit |
There are now enough licences available for registering SIP phones in the Mitel 6800/6900 SIP series on a backup communication server. Note:
This event message is generated by the backup communication server. |
Date, time |
Serious (positive, with match) |
E-mail successfully sent |
The system has now successfully sent an e-mail. Meaning of the parameter values, see table below. |
Cause/action=0000, e-mail client, additional information, date, time |
critical (positive, with match) |
Emergency call ended |
The emergency call has been confirmed by a responsible person. |
Date, time |
critical (positive, with match) |
Emergency call started |
An emergency number out of the public emergency number list has been dialled. Note:
If an emergency number of the internal numbering plan has been dialled, no event message will be generated. |
Dialled number (the first 4 digits), user number, terminal ID (if user number ? 0) or trunk group ID (if user number = 0), date, time |
critical (negative, with match) |
ESME reachable |
The LAN connection between the SMSC and the ESME is now available |
IP address, date, time |
critical (positive, with match) |
ESME unreachable |
The LAN connection between the SMSC and the ESME is interrupted |
IP address, date, time |
critical (negative, with match) |
Ethernet activated again |
The overload on the Ethernet interface no longer exists. The interface has been reactivated. |
Date, time |
Normal (positive, with match) |
Ethernet deactivated due to high load |
The system has detected an overload on the Ethernet interface. The interface is temporarily deactivated. |
Date, time |
Normal (negative, with match) |
External auxiliary power supply failed (Mitel 470 only) |
The external auxiliary power supply to the communication server has failed. If the auxiliary power supply unit has been used for redundant operation, there are no short-term limitations. If the auxiliary power supply unit has been used to increase the power supply, the internal power supply unit overflow must be calculated. |
Date, time |
Serious (negative, with match) |
External auxiliary power supply in service (Mitel 470 only) |
The external auxiliary power supply to the communication server is working. |
Date, time |
Serious (positive, with match) |
External event message destination not reachable |
External signal destination not automatically reachable |
Cause (0: Busy /1: Not available /2:(not used), 2: Barred /3: not defined), date, time |
Serious (negative, with match) |
External event message destination reachable |
External signal destination is now reachable |
Date, time |
Serious (positive, with match) |
Fan failure (Mitel SMBC only) |
The fan is jammed or defective or the connection is no longer making contact.
|
Parameter, date, time |
critical (negative, with match) |
Fan failure (Mitel 470 only) |
The fan is jammed or defective or the connection is no longer making contact.
|
Parameter 1, parameter 2, date, time |
critical (negative, with match) |
Fan in operation ( Mitel SMBC only) |
The fan is back in service again after a failure.
|
Parameter, date, time |
critical (positive, with match) |
Fan in operation (Mitel 470 only) |
The fan is back in service again after a failure.
|
Parameter, date, time |
critical (positive, with match) |
FIAS command buffer full |
The command buffer to the PMS interface is full. |
Date, time |
critical (negative, with match) |
FIAS interface usable again |
The command buffer to the PMS interface is back below the critical limit. |
Date, time |
critical (positive, with match) |
Inactive radio unit port |
Radio unit not responding Reason: 0: Startup running, 1: Not registered, 2: Various nodes, 3: Port not permitted, 4: Local power supply, 5: Not connected, 6: Port reset, 7: Startup error, 8: Unknown error |
Card number, port number, radio unit ID/reason, date, time |
Serious (negative, with match) |
Incompatible PMS application |
The external hotel management system (PMS application) is not suitable for communicating with the communication server. |
PMS SW version, PMS interface version, PMS interface driver version, date, time |
critical (negative, with match) |
Incorrect or no wiring adapter (Mitel SMBC only) |
There is no wiring adapter in the wiring adapter slot or the wiring adapter fitted is unsuitable. |
Slot number, date, time |
Critical (without match) |
Insufficient bandwidth |
An user in an AIN is trying to set up a connection and the bandwidth currently available with the WAN link is insufficient. |
Link ID, WAN link name, available bandwidth in Kbit/s, date, clock |
Serious (without match) |
Internal event message destination not reachable |
Local output blocked or not available |
Cause (0: Busy /1: Not available /2:(not used), 2: Barred /3: not defined), date, time |
Serious (negative, with match) |
Internal event message destination reachable |
Local output available once again |
Date, time |
Serious (positive, with match) |
Internal power supply unit failed (Mitel 470 only) |
The internal power supply unit of the communication server has failed. If the auxiliary power supply unit has been used for redundant operation, there are no short-term limitations. If the auxiliary power supply unit has been used to increase the power supply, the external power supply unit overflow must be calculated. |
Date, time |
Serious (negative, with match) |
Internal power supply unit in service (Mitel 470 only) |
The internal power supply unit of the communication server is in service. |
Date, time |
Serious (positive, with match) |
IP address added to the DoS blocklist |
A DoS attack has taken place beyond the maximum configured admissible registration attempts or transactions. The IP address concerned has been included in the blocklist and will remain blocked for a set period. |
IP address, Cause (0: Registration / 1: Too many transactions / 2: No session / 3: modified message), date, time |
Serious (negative, with match) |
IP address changed: Regenerate TLS certificates |
The IP address of the communication server has changed. The TLS certificates have to be regenerated. For terminals down circuit from a NAT without ALG the public NAT gateway address has to be configured. |
Date, time |
Serious (without match) |
IP address removed from the DoS blocklist |
An IP address added previously due to a DoS (Denial of Service) attack was again removed from the blocklist and is no longer blocked. |
IP address, date, time |
Serious (positive, with match) |
IP phone: Connection lost |
An IP system phone is no longer connected to the communication server. |
User number, terminal ID, date, time |
Serious (negative, with match) |
IP phone: Connection re-established |
An IP system phone has re-established the connection to the communication server. |
User number, terminal ID, date, time |
Serious (positive, with match) |
IP system phone licence is now available |
A sufficient number of licences is now available again for MiVoice 5361 IP / 5370 IP / 5380 IP. |
Date, time |
Serious (positive, with match) |
Language file download failed |
The downloading of a language file via FTP server for an MitelSIP terminal has failed. |
Parameter 1: FTP server address, Parameter 2: Language file type and name, date, time |
Serious (negative, with match) |
Language file download successful |
The downloading of a language file via FTP server for an Mitel SIP terminal has been successfully completed. |
Parameter 1: FTP server address, Parameter 2: Language file type and name, date, time |
Serious (positive, with match) |
LCR on alternative network provider |
Automatic switch from primary network provider to secondary network provider using LCR function. |
Provider ID, date, time |
Normal (without match) |
Licence available for configured user (Mitel 470 and Virtual Appliance only) |
This event message is generated, if all configured users have a user licence (which was not the case before). |
Date, time |
Serious (positive, with match) |
Licence for integrated mobile/external phone available |
A sufficient number of licences is now available again for integrated mobile/external phones. |
Date, time |
Serious (positive, with match) |
Licence for PMS interface available |
The Hospitality PMS Interface licence or a sufficient number of Hospitality PMS Rooms licences are now available. |
Date, time |
Serious (positive, with match) |
Licence invalid, restricted operating mode 4 hours after restart |
The system software loaded requires a software release licence. Without this licence the system software’s functionality is severely restricted 4 hours after the restart. |
Date, time |
Serious (without match) |
Licence missing for configured user (Mitel 470 and Virtual Appliance only) |
This event message is generated, if one or more configured users have no user licence. Note:
To avoid a flood of messages this event message is generated only once (the first time a user is created without a user licence) |
Date, time |
Serious (negative, with match) |
Licences for offline operations expired |
The maximum period of 36 hours for the temporary licence activation has expired. |
Date, time |
Critical (without match) |
Link to gateway satellite lost (Virtual Appliance only) |
The communication server has lost the link to the gateway satellite. Without this link, the communication server switches to restricted operating mode after xx hours. |
Number of hours until restricted operating mode, date, time |
critical (negative, with match) |
Link to gateway satellite restored (Virtual Appliance only) |
The communication server has been able to restore the link to the gateway satellite. |
Date, time |
critical (positive, with match) |
Link to the licence server (SLS) has failed (Virtual Appliance only) |
It has been impossible for a long time to set up a link to the licence server. The system switches to restricted mode after a variable timeout (max. 72 hours). |
Date, time |
critical (negative, with match) |
Link to the licence server (SLS) has restored (Virtual Appliance only) |
It has been possible to restore a link to the licence server. |
Date, time |
critical (positive, with match) |
Local supply error on radio unit |
Local power supply of a SB-4+ / SB-8 / SB-8ANT radio unit failed or unavailable |
Card number, port number, date, time |
critical (negative, with match) |
Local supply on radio unit available |
Local power supply of a SB-4+ / SB-8 / SB-8ANT is now again available |
Card number, port number, date, time |
critical (positive, with match) |
Mains voltage failure |
Event message once mains power is restored
|
Date, time |
Serious (without match) |
Malfunction |
A hardware or software error has occurred. The error ID can help Support to pinpoint the possible cause of the error. |
Error ID, date, time |
Serious (without match) |
MiCollab: Terminal limit has been reached |
A MiCollab terminal could not be linked to a user because a limit has been reached (reason). reason = 0: Too much terminals per system reason = 1: Too much terminal per user reason = 2: Too much MiCollab clients per user |
User number, reason, date, time |
Serious (negative, with match) |
MiCollab: Within the terminal limits again |
A MiCollab terminal could now be linked to a user because it is within a limit again (reason). reason = 0: Terminals per system OK again reason = 1: Terminal per user OK again reason = 2: MiCollab clients per user OK again |
User number, reason, date, time |
Serious (positive, with match) |
Mitel Dialer within the licence limit again |
Mitel Dialer user licences are now available again. |
Date, time |
Serious (positive, with match) |
Mitel SIP terminals within the licence limit again |
Mitel SIP Terminals and Mitel 8000i Video Options licences are now available. |
Parameter 1=1: Mitel SIP Terminals licence, Parameter 2=1: Mitel 8000i Video Options licence, date, time |
Serious (positive, with match) |
Monitor event |
Monitor event |
Monitor Type, Date, Time |
Normal (without match) |
No configuration template |
A configuration template for a Mitel SIP terminal is missing in the communication server file system. Without the configuration template, no configuration file can be generated for this terminal type. |
No configuration template, date, time |
Serious (negative, with match) |
No DECT DSP channels available |
DECT channels on DSP-0x overloaded |
Date, time |
Normal (without match) |
No DTMF receiver available for integrated mobile/external phones |
A permanent DTMF receiver (for detection suffix dialling function codes) could not be assigned to an integrated mobile/external phone with enhanced functionality. |
BCS Ref., date, time |
Serious (without match) |
No other system clone detected (Virtual Appliance only) |
The clone detection service on the licence server (SLS cloud) could not find any other clone (system with the same EID) for a long time (24 hours). |
Date, time |
critical (positive, with match) |
No response from network |
No answer to Call Setup on BRI-T/PRI interface |
Port number of the exchange line circuit, date, time |
Normal (without match) |
No response from user |
No answer to incoming DDI call from user on S bus or DSI |
DDI No., date, time |
Normal (without match) |
Node: Connection lost |
A node is not connected to the Master for a certain amount of time (configurable). |
Node number, date, time |
critical (negative, with match) |
Node: Connection re-established |
A node is reconnected with the Master for a certain amount of time (configurable) after an interruption. |
Node number, date, time |
critical (positive, with match) |
Not enough licences for integrated mobile/external phones |
The connection setup with an integrated mobile/external phone has failed because the number of configured mobile/external phones is greater than the number of licences available. All the integrated mobile/external phones remain blocked until a sufficient number of licences are available. |
Number of licences, number of configured mobile/external phones, date, time |
Serious (negative, with match) |
NTP: Time synchronisation failed |
Time synchronization via the NTP server (NTP = Network Time Protocol) has failed. |
Date, time |
Serious (negative, with match) |
NTP: Time synchronisation re-established |
Time synchronization via the NTP server (NTP = Network Time Protocol) has been restored. |
Date, time |
Serious (positive, with match) |
Outgoing call rejected |
Call rejected by the network
|
Port number of the exchange line circuit, cause, date, time |
Normal (without match) |
Overheat (Mitel SMBC only) |
The temperature inside the communication server is too high. The appropriate measures must be taken immediately to improve the heat dissipation, e.g. by providing the required clearances, lowering the ambient temperature or installing the fan from the rack-mounting set (Mitel 430 only). |
critical (negative, with match) |
Card number, temperature, date, time |
Overheat (Mitel 470 only) |
The temperature inside the communication server is too high. Appropriate measures must be taken immediately to improve heat dissipation. Measures are automatically adopted, depending on where the overheating occurs: FXO and FXS interface card:
CPU2 applications card
Internal power supply unit PSU2U or call manager card CPU1:
Note:
|
Card number, temperature, date, time |
critical (negative, with match) |
Overload detected on USB port (CPU2) (Mitel 470 only) |
A (current) overload was detected on one of the USB interfaces on the applications card (CPU). Note:
The maximum current input at the USB interfaces varies. |
Date, time |
Normal (without match) |
Port out of service |
A port previously in operation has stopped functioning. |
Number of the slot, relevant port number, date, time |
Serious (without match) |
Possible clone detected for your system (Virtual Appliance only) |
The clone detection service on the licence server (SLS cloud) has detected a possible clone (system with the same EID). |
Date, time |
critical (negative, with match) |
QSIG licence limit reached |
Maximum number of licensed outgoing connections with QSIG protocol exceeded |
Route number, user number, date, time |
Serious (without match) |
Radio unit port active |
The radio unit is responding again |
Card number, port number, date, time |
Serious (positive, with match) |
Register error |
|
Card number, date, time |
Normal (without match) |
Remote maintenance disabled |
Remote maintenance has been deactivated |
Date, time |
Normal (positive, with match) |
Remote maintenance enabled |
The remote maintenance has been activated (The report is output unfiltered on local destinations). |
Date, time |
Normal (negative, with match) |
Restart of applications card CPU2 executed |
The restart of applications card CPU2 was executed successfully. |
Date, time |
critical (positive, with match) |
Restart of applications card CPU2 required |
The system has detected that a manual restart of the applications card CPU2 is required (e. g. for a security update). |
Date, time |
critical (negative, with match) |
Restricted operating mode disabled |
Restricted mode could be disabled again. |
Date, time |
critical (positive, with match) |
Restricted operating mode enabled (not valid for Virtual Appliance) |
The communication server has switched to restricted mode. Cause: 0: No valid licence |
Cause, date, time |
critical (negative, with match) |
Restricted operating mode enabled (Virtual Appliance only) |
The communication server has switched to restricted mode. Cause: 0: No valid licence. 1: Link to gateway satellite lost. 2: Max. duration without link to licence server reached. 3: Your system clone confirmed. 4: Licence check mode mismatch in SLS and MiVo400. 5: Support mode enabled. |
Cause, date, time |
critical (negative, with match) |
Satellites missing after supervision time |
After an AIN update (Master and all satellites) some satellites no longer have a connection to the Master. |
Total satellites missing, Satellites rolled back, Date, Time |
Serious (without match) |
Send e-mail failed |
The system was unable to send an e-mail because an error occurred. Meaning of the parameter values, see table below. |
Cause/action, e-mail client, additional information, date, time |
critical (negative, with match) |
SIMPLE/MSRP back within the licence limit |
There are now enough licences available for using the MSRP and/or SIMPLE protocol for users. |
Date, time |
Serious (positive, with match) |
SIP account available |
The SIP account has successfully registered with the SIP provider. |
Provider, account, date, time |
critical (positive, with match) |
SIP account not available |
The SIP account cannot register with the SIP provider for a certain reason (0: Provider unobtainable / 1: no permission). The event is triggered only if the parameter Registration required is configured to Yes. |
Provider, account, date, time |
critical (negative, with match) |
SMS gateway reachable |
External SMS gateway again reachable |
Date, time |
critical (positive, with match) |
SMS gateway unreachable |
External SMS gateway unobtainable by network provider or incorrectly configured |
Date, time |
critical (negative, with match) |
Software upgrade IP system phone failed |
The software update of an MiVoice 5361 IP / 5370 IP / 5380 IP has failed for the stated reason. |
User number, terminal ID, reason, date, time |
critical (negative, with match) |
Software upgrade IP system phone successful |
The software update of an MiVoice\ 5361 IP / 5370 IP / 5380 IP has now been successfully completed after unsuccessful attempt(s). |
User number, terminal ID, date, time |
critical (positive, with match) |
Software upload |
During an upload in system status:
|
Parameter 1:
Date, time |
Normal (without match) |
Standard SIP terminals within the licence limit again |
SIP Terminals and Video Terminals licences are now available. |
Parameter 1=1: SIP Terminals licence, Parameter 2=1: Video Terminals licence, date, time |
Serious (positive, with match) |
SX-200 call data record management system: Connection established |
The connection to the SX-200 call data record management system has been successfully established. |
Date, time |
critical (positive, with match) |
SX-200 call data record management system: Connection lost |
The connection to the SX-200 call data record management system has been lost. |
Date, time |
critical (negative, with match) |
SX-200 hotel management system: Connection established |
The connection to the SX-200 hotel management system has been successfully established. |
Date, time |
critical (positive, with match) |
SX-200 hotel management system: Connection lost |
The connection to the SX-200 hotel management system has been lost. |
Date, time |
critical (negative, with match) |
SX-200 voice mail management system: Connection established |
The connection to the SX-200 voice mail management system has been successfully established. |
Date, time |
critical (positive, with match) |
SX-200 voice mail management system: Connection lost |
The connection to the SX-200 voice mail management system has been lost. |
Date, time |
critical (negative, with match) |
Synchronisation loss on trunk |
A BRI/PRI interface entered in the clock pool has lost the system clock |
Port number, date, time |
Serious (negative, with match) |
Synchronisation re-established |
Synchronization with the network has been restored on at least one BRI/PRI interface. |
Date, time |
Serious (positive, with match) |
Synchronisation with backup communication server failed |
The primary communication server was unable to transmit the configuration data to the backup communication server. Note:
This event message is generated by the primary communication server. |
Backup communication server ID, date, time |
critical (negative, with match) |
Synchronisation with backup communication server successful |
The primary communication server was able (following one or more previous failed attempts) to transmit the configuration data to the backup communication server. Note:
This event message is generated by the primary communication server. |
Backup communication server ID, date, time |
critical (positive, with match) |
Synchronization on trunk re-established |
A BRI/PRI interface entered in the clock pool has been successfully re-synchronized with the system clock. |
Port number, date, time |
Serious (positive, with match) |
System memory usage below the critical range again |
The memory usage in the file system for a specific purpose has again fallen below a defined (Serious severity level) or critical (Critical severity level) value. Purpose (file type ID):0: File system, 1: Application, 2: Crash-Log, 3: Monitor-Log, 4: Announcement service, 5: Voice mail, 6: Music on hold, 7: Data backup, 8: Hospitality/Accommodation, 9: User folder |
File type ID, memory usage in %, date, time |
Serious / Critical (positive, with match) |
System memory usage over the critical range |
The memory usage in the file system for a specific purpose has exceeded a defined (Serious severity level) or critical (Critical severity level) value. Purpose (file type ID):0: File system, 1: Application, 2: Crash-Log, 3: Monitor-Log, 4: Announcement service, 5: Voice mail, 6: Music on hold, 7: Data backup, 8: Hospitality/Accommodation, 9: User folder |
File type ID, memory usage in %, date, time |
Serious / Critical (negative, with match) |
System overload |
Network access attempted when all lines are seized or the system is overloaded. |
Route number, user number, date, time |
Normal (without match) |
System phone in service again |
A system phone on the DSI bus is ready for operation again. |
Card number, port number, user number, date, time |
critical (positive, with match) |
System phone out of service |
A system phone on the DSI bus is defective or was disconnected. |
Card number, port number, user number, date, time |
critical (negative, with match) |
Temperature within normal range again |
Following overheating, the temperature inside the communication server is back in the normal operating range. |
Card number, temperature, date, time |
critical (positive, with match) |
Temporary activation expires on |
Reminder of the missing, definitive activation licence following connection setup with the communication server. |
Expiration date [DD.MM.YYYY], date, time |
Serious (without match) |
Terminal power supply: Overload (Mitel 470 only) |
Rated output slightly exceeded for > 4 s. |
Date, time |
critical (negative, with match) |
Terminal power supply: Shutdown (Mitel 470 only) |
Rated output clearly exceeded for 4 s. |
Date, time |
critical (negative, with match) |
Terminal power supply: Switching back on (Mitel 470 only) |
The power supply to the terminals was switched back on after deactivation due to overflow. |
Date, time |
critical (positive, with match) |
Terminal power supply: Within normal range again (Mitel 470 only) |
The power supply to the terminals is back in the normal rated output range following a slight, preceding overflow. |
Date, time |
critical (positive, with match) |
Test event message |
The configuration of message destinations can be tested with this event message. |
Date, time |
Serious (without match) |
The communication server has been restarted |
The communication server was restarted manually or automatically due to an error. |
Date, time |
Critical (without match) |
The licence limit for BluStar clients has been reached. |
A BluStar client was unable to register because there are too few licences for this client type. Parameter 1: 0 (not used) Licence type: 0 and 1: (not used), 2: BluStar CTI, 3: BluStar Softphone, 4: BluStar video option, 5: BluStar Presence option |
Parameter 1, licence type, total purchased licences, date, time |
Serious (negative, with match) |
The licence limit for CSTA sessions has been reached |
An application is unable to set up a CSTA session to monitor/check a terminal because there are too few CSTA Sessions licences available. |
Max. number of licences, date, time |
Serious (negative, with match) |
The licence limit for Dual Homing has been reached |
A SIP phone in the Mitel 6800/6900 SIP series has attempted to register on a backup communication server and not enough licences are available. Note:
This event message is generated by the backup communication server. |
Date, time |
Serious (negative, with match) |
The licence limit for Mitel Dialer has been reached |
Mitel Dialer could not be linked to a user because too few licences are available. |
Total purchased licences, date, time |
Serious (negative, with match) |
The licence limit for Mitel SIP terminals has been reached |
A Mitel SIP terminal is unable to register or use the video functionality because there are too few Mitel SIP Terminals or Mitel 8000i Video Options licences available. |
Parameter 1=1: Missing Mitel SIP Terminals licence, Parameter 2=1: Missing Mitel 8000i Video Options licence, Parameter 3=3: Max. number of licences, date, time |
Serious (negative, with match) |
The licence limit for SIMPLE/MSRP has been reached |
A third-party application wishes to use the MSRP and/or SIMPLE protocol for a user, but not enough licences are available. |
Date, time |
Serious (negative, with match) |
The licence limit for standard SIP terminals has been reached |
A standard SIP terminal is unable to register or use the video functionality because there are too few SIP Terminals or Video Terminals licences available. |
Parameter 1=1: Missing SIP Terminals licence, Parameter 2=1: Missing Video Terminals licence, Parameter 3=3: Max. number of licences, date, time |
Serious (negative, with match) |
TLS certificate expires soon |
A TLS certificate for a SIP node or SIP endpoint is about to expire (Serious severity level) or has just expired (Critical severity level) and needs to be renewed.If the endpoint type is = 0 (Mitel), then is parameter 2 = node ID.If the endpoint type is = 1 (3rd party), then the remaining parameter data contains the first eleven characters of the certificate name. |
Type of endpoint (0: Mitel, 1: 3rd party), node ID or certificate name, date, time |
Serious / Critical (without match) |
TLS certificate update failed |
The update of the TLS certificate for an SIP node or SIP endpoint via FTP has failed and needs to be renewed manually.If the endpoint type is = 0 (Mitel), then is parameter 2 = node ID.If the endpoint type is = 1 (3rd party), then the remaining parameter data contains the first eleven characters of the certificate name. Type of endpoint (0: Mitel, 1: 3rd party), node ID or certificate name, date, time |
critical (negative, with match) |
|
TLS certificate update successful |
A TLS certificate for a SIP node or SIP endpoint was successfully renewed.If the endpoint type is = 0 (Mitel), then is parameter 2 = node ID.If the endpoint type is = 1 (3rd party), then the remaining parameter data contains the first eleven characters of the certificate name. |
Type of endpoint (0: Mitel, 1: 3rd party), node ID or certificate name, date, time |
critical (positive, with match) |
TLS certificate was generated: Upgrade non-Mitel endpoints now |
A TLS certificate has been generated. If generation is manual, the certificate must be imported manually into the Mitel SIP nodes. The certificate must always be imported manually on all non-Mitel nodes and non-Mitel endpoints. |
Date, time |
Normal (without match) |
TLS server certificate: Validation failed |
While a TLS connection is established the validation of the certificate of the TLS server failed. |
Service, TCP port, reason, date, time |
critical (negative, with match) |
TLS server certificate: Validation successful |
The validation of the certificate of the TLS server was successful. |
Service, TCP port, date, time |
critical (positive, with match) |
Too few FoIP channels |
Setting up a fax connection via T.38 failed because no FoIP channel is available. |
Available FoIP channels on node |
Serious (without match) |
Too few licences for IP system phones |
A MiVoice 5361 IP / 5370 IP / 5380 IP was unable to register because there are too few IP system phone licences. |
Date, time |
Serious (negative, with match) |
Too few licences for PMS interface |
Either the Hospitality PMS Interface licence is missing or the number of Hospitality PMS Rooms licences available is insufficient. |
Number of licensed rooms, number of configured rooms, date, time |
Serious (negative, with match) |
Too few VoIP channel licences |
Connection setup failed because the licence limit for simultaneously active VoIP channels has been reached. |
No. of licensed VoIP channels, Date, Time |
Serious (without match) |
Too few VoIP channels |
An user is trying to set up a connection that requires one or more VoIP channels which are currently not available. |
Available VoIP channels on this node, date, time |
Normal (without match) |
Too many errors with the same ID |
An unusual amount of errors (more than 50 per hour) with the same error ID have occurred. |
Error ID, date, time |
Normal (without match) |
Too many event messages |
Number of message types exceeds limit entered in the table on:
|
Date, time |
Normal (without match) |
Too much user data |
System capacity exceeded |
Date, time |
Critical (without match) |
Total synchronization loss |
Network synchronisation has failed on all BRI/PRI interfaces |
Date, time |
Serious (negative, with match) |
Trial licence expired |
The duration for which a trial licence can be used for a specific feature has expired and there is no valid licence. |
Licence ID, date, time |
Serious (without match) |
USER EVENT MESSAGE |
With *77[nnnn] from a terminal |
nnnn [0000...99999], user number, date, time |
Serious (without match) |
User memory usage below the critical range again |
The memory usage in the file system for a specific user has again fallen below a defined (Serious severity level) or critical (Critical severity level) value. |
User number, memory usage in %, date, time |
Serious / Critical (positive, with match) |
User memory usage over the critical range |
The memory usage in the file system for a specific user has exceeded a defined (Serious severity level) or critical (Critical severity level) value. |
User number, memory usage in %, date, time |
Serious / Critical (negative, with match) |
Wake-up call failed |
The room wake-up call was not answered |
Room No., date, time |
Normal (negative, with match) |
Wake-up order confirmed |
The room wake-up call has now been answered |
Room No., date, time |
Normal (positive, with match) |
| Parameter 1 (XXYY) | Parameter 2: | Parameter 3: | ||
|---|---|---|---|---|
| Value | Reason (XX) | Action (YY)2 | E-mail client | Additional info depending on the e-mail client (XXYY) |
00 |
Not defined |
Not defined |
Not defined |
|
01 |
E-mail memory full |
Connection set up to SMTP server |
Voice mail |
XX: Mailbox ID YY: Message ID |
02 |
SMTP server access data invalid |
Extended registration on SMTP server |
Auto backup |
|
03 |
SMTP client cannot set up a connection to the server |
Registration on SMTP server |
Call recording |
User number |
04 |
Authentication failed |
Transmission of e-mail address |
Event message |
|
05 |
Temporary negative answer from SMTP server |
Transmission of e-mail recipient address Call logging for hospitality |
||
06 |
Temporary negative answer from SMTP server |
Prepare data transmission |
Configuration files |
XX: User ID YY: Terminal ID |
07 |
No answer from SMTP server |
Data transmission in progress |
||
08 |
E-mail attachment not found |
End data transmission |
||
09 |
Invalid host, domain or IP address on the communication server |
Prepare authentication (LOGIN) |
||
10 |
E-mail text too long (body) |
User name authentication (LOGIN) |
||
11 |
E-mail attachment too large |
Password authentication (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 authentication (CRAM-MD5) |
||
15 |
Invalid e-mail sender address |
Preparing to send next e-mail |
In the System events / Settings / Event tables"Event tables" view, you can set for each event and according to destination, how often an event message may appear for each period until it is issued on the configured destination.