This document helps Mitel engineers interpret the error information (message print) produced by the Mitel 5000 phone system. Now known as MiVoice Office!
25. Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page 1
Overview
Overview
The Message Print Diagnostics Manual supports both the Mitel 5000 Communications Platform
(CP) and the Inter-Tel Axxess system. This manual contains alarm and message definitions to
make it easier for the user to find needed information. When necessary, alarm and message
definitions are tagged for clarification (see Table 1) to identify product-specific information.
Table 1. Product Descriptors
This Tag... Has this meaning...
Axxess Only Pre v8.0 The alarm or message and the definition information is only applicable to an Inter-Tel
Axxess system that is v8.0 (or earlier).
Axxess Only Pre v8.2 The message and the definition information is only applicable to an Inter-Tel Axxess
system that is prior to v8.2.
Axxess Only Pre v8.2
Action
Steps the customer or installation technician can take to correct the alarm or message is
only applicable to an Inter-Tel Axxess system that is prior to v8.2
Axxess Only The alarm or message and the definition information is only applicable to an Inter-Tel
Axxess system that is v8.1 (or later).
Axxess Field(s) The variable field(s) in the alarm or message is only applicable to an Inter-Tel Axxess
system.
Axxess Cause(s) The cause(s) of the alarm or message is only applicable to an Inter-Tel Axxess system.
Axxess Action Steps the customer or installation technician can take to correct the alarm or message is
only applicable to an Inter-Tel Axxess system.
Axxess FS Action Action the Field Service Technician is to take in response to the alarm or message is
only applicable to an Inter-Tel Axxess system.
Axxess Post v8.2 and
5000
The message and the definition information is only applicable to an Inter-Tel Axxess
system that is v8.2 (or later) and is also applicable to a Mitel 5000 system.
Axxess Post v8.2 and
5000 Action
Steps the customer or installation technician can take to correct the alarm or message is
only applicable to an Inter-Tel Axxess system that is v8.2 (or later) and is also applicable
to a Mitel 5000 system.
5000 Only The alarm or message and the definition information is only applicable to a Mitel 5000.
5000 Field(s) The variable field(s) in the alarm or message is only applicable to a Mitel 5000 system.
5000 Cause(s) The cause(s) of the alarm or message is only applicable to a Mitel 5000 system.
5000 Action Steps the customer or installation technician can take to correct the alarm or message is
only applicable to a Mitel 5000 system.
5000 FS Action Action the Field Service Technician is to take in response to the alarm or message is
only applicable to a Mitel 5000 system.
UVM Only The information is only applicable to a system using the Mitel 5000 Unified Voice
Messaging.
VPU/EM Only The information is only applicable to a system using external Voice Mail.
Axxent Only The alarm or message and the definition information is only applicable to an Inter-Tel
Axxent system.
26. Alarm Messages (A000–1099): Minor System Alarms (A000–A019)
Page 2 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011
Alarm Messages (A000–1099)
Minor System Alarms (A000–A019) (see below): Can be handled without calling a technician.
Minor Voice Processing Alarms (A020–A039) (see page 5): Can be handled without calling a
technician.
Major System Alarms (A100–A199) (see page 8): Require assistance from a technician.
Major Voice Processing Alarms (A200–A224) (see page 20): Require assistance from a
technician.
Network Alarms (A225–A244) (see page 22): These alarms are for either Call Processing or
Voice Processing and are handled the same as the local alarm is handled.
System Application Alarms (A1001–A1099) (see page 23): These alarms indicate an issue with
one of the system applications. See the individual alarm descriptions for additional information.
Minor System Alarms (A000–A019)
This section defines the minor System alarms. These alarms can generally be handled by the
customer without the need for a service call.
A000 Alarm Automatically Cleared
FIELDS: None.
CAUSE: The condition causing the alarm was resolved and the alarm automatically cleared itself.
ACTION: None.
A001 Alarm Manually Cleared by Ext <eeeee>
FIELDS: eeeee The extension number of the device that cleared the alarm.
CAUSE: An administrator entered the "Clear Alarm" feature code.
ACTION: None.
A002 Network Alarm Automatically Cleared
FIELDS: None.
CAUSE: The condition causing the alarm was resolved and the alarm automatically cleared itself.
ACTION: None.
A003 Network Alarm Manually Cleared by Ext <eeeee>
FIELDS: eeeee The extension number of the device that cleared the alarm.
CAUSE: An administrator entered the Clear Network Alarm feature code.
ACTION: None.
A010 Ext <eeeee> – <username> is Off-Hook (5000 Only)
FIELDS: eeeee The extension number of the device that is off-hook.
username The username of the device that is off-hook
CAUSE: The handset of the indicated extension has been removed from the cradle (on-hook) position for
longer than the Inactivity Alarm timer allows.
ACTION: Return the handset of the indicated extension to the cradled (on-hook) position.
NOTE There is a system flag that can disable this alarm.
27. Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page 3
Alarm Messages (A000–1099): Minor System Alarms (A000–A019)
A011 Emergency Call Made by Ext <eeeee> – <username> @
<hot_desk_info> (5000 Only)
FIELDS: eeeee The extension number of the device that made the emergency call.
username: The username of the device that made the emergency call.
hot_desk_info: If Hot Desking exists, the extension and username of the Hot Desk base phone
location.
CAUSE: A station dialed the Emergency Call feature code to report an emergency.
ACTION: No action is required other than to clear the alarm. It may be helpful to determine who made the
emergency call to handle the emergency situation in an orderly manner (directing emergency
services to the requesting party, etc.).
A012 SMDR Printer Off-Line (Axxess Only)
FIELDS: None.
CAUSES: The system could not write to the SMDR printer for 5 minutes. The problem can be one of the
following:
The printer ran out of paper (Data Terminal Ready [DTR] is not asserted) and hardware
handshaking is enabled.
The printer cable is unplugged or the printer is powered off.
The printer cable, printer, or serial port are faulty.
Database Programming or the Voice Processing was connected for a duration of 5
minutes to the port that SMDR is programmed to use and there was SMDR information to
print.
ACTION: Remedy the problem according to causes listed, and then verify that printing continues.
A013 Message Printer Off-Line (Axxess Only)
FIELDS: None.
CAUSES: The system could not write to the Message Print printer for 5 minutes. The problem can be one
of the following:
The printer ran out of paper (Data Terminal Ready [DTR] is not asserted) and hardware
handshaking is enabled.
The printer cable is unplugged or the printer is powered off.
The printer cable, printer, or serial port are faulty.
Database Programming or the Voice Processing was connected for a duration of 5
minutes to the port that message print is programmed to use and there were messages to
print.
ACTION: Remedy the problem according to causes listed, and then verify that printing continues.
A014 Real-Time Clock Needs to be Set (Axxess Only)
FIELDS: None.
CAUSE: The real-time clock chip (present only with a MEM board on the CPU board) has not been
initialized and needs to be initialized before it can begin keeping proper time. This condition will
occur when a system is first set up. This condition also occurs when the system is powered
down and the battery jumper disabled or the battery is removed. It also occurs if a tech removes
the MEM board from the CPU, for example, to upgrade ROMs or a PAL.
ACTION: At an administrator station, enter the “Set Date and Time” feature code and program the
system's date and time.
NOTE
A database restore will set the time and date to that of the remote computer if the
restore occurs on a system where the time and date are uninitialized.
28. Alarm Messages (A000–1099): Minor System Alarms (A000–A019)
Page 4 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011
A015 Hardware Real-Time Clock Inoperative (Axxess Only)
FIELDS: None.
CAUSE: The hardware real-time clock chip is not operating. This may occur when a system is first set
up. This condition also may occur when the system is powered down and the battery jumper
disabled or the battery is removed.
ACTION: Cycle power to the system.
A016 No Delayed Major Because System Busy
FIELDS: None.
CAUSE: The system was unable to perform a scheduled delayed major reset because the system was
not idle. The system will continue to try to perform the delayed major reset every 5 minutes.
This could be cause by the system being truly busy. For Axxess v9.0 or 5000 v1.0 and later, a
programming inactivity timer will automatically close the connection when Database
Programming remains connected and idle for the duration of the timer setting. In this instance,
the system is not prevented from performing a major reset as scheduled. However, if the
“Forced Reset If Not Idle” flag in Database Programming is enabled, the system will perform the
delayed major regardless if the system is idle or not.
ACTION: Dump the call diagnostics to determine what calls on preventing the system to reset. If the
active calls are not correct, run the “Resource” Periodic Diagnostics to attempt to repair the
stale resources. If this fails, reset the system manually.
A017 System Manager Link Connection Error <num>: <string>
FIELDS: num The certificate/link error code number.
string The certificate/link error.
CAUSE: There are many reasons the certificate can fail verification. Common errors are #9 (certificate
not yet valid) and #19 (self-signed certificate). Error code 0 typically indicates an incorrect IP
address, username, or password. The error string comes from a generic SSL library. Because
the phones can only display 16 characters, for any error strings that are greater than 16
characters, the system will show CERTIFICATE ERR. The user can go into message print log to
view the true SSL error string and the text based explanation of the error.
ACTION: Most errors can be resolved by ensuring you are connecting to the correct System Manager
server, re-uploading the correct System Manager certificate, and/or ensuring that the system
time is set correctly.
A018 Invalid System Manager Certificate
FIELDS: None.
CAUSE: A corrupt certificate file was uploaded or there was an error in writing the file.
ACTION: Re-upload the certificate, or if that file is damaged, create a new certificate in the System
Manager and upload that certificate.