Beruflich Dokumente
Kultur Dokumente
For additional information and/or technical assistance in North America, certified technicians may contact:
Mitel Networks Corporation
Technical Support Department (USA)
1146 North Alma School Road
Mesa, AZ 85201
1-888-777-EASY (3279)
Trademarks
The trademarks, service marks, logos and graphics (collectively "Trademarks") appearing on Mitel's
Internet sites or in its publications are registered and unregistered trademarks of Mitel Networks
Corporation (MNC) or its subsidiaries (collectively "Mitel") or others. Use of the Trademarks is prohibited
without the express consent from Mitel. Please contact our legal department at legal@mitel.com for
additional information. For a list of the worldwide Mitel Networks Corporation registered trademarks, please
refer to the website: http://www.mitel.com/trademarks.
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Alarm Messages (A000–1099) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Minor System Alarms (A000–A019) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
A000 Alarm Automatically Cleared. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
A001 Alarm Manually Cleared by Ext <eeeee> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
A002 Network Alarm Automatically Cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
A003 Network Alarm Manually Cleared by Ext <eeeee> . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
A010 Ext <eeeee> – <username> is Off-Hook (5000 Only). . . . . . . . . . . . . . . . . . . . . . . . . 2
A011 Emergency Call Made by Ext <eeeee> – <username> @
<hot_desk_info> (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
A012 SMDR Printer Off-Line (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
A013 Message Printer Off-Line (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
A014 Real-Time Clock Needs to be Set (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
A015 Hardware Real-Time Clock Inoperative (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . 4
A016 No Delayed Major Because System Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
A017 System Manager Link Connection Error <num>: <string> . . . . . . . . . . . . . . . . . . . . . 4
A018 Invalid System Manager Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Minor Voice Processing Alarms (A020–A039) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
A020 Voice Mail Printer Off-Line (VPU/EM Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
A021 Voice Mail Unit 80% Full (VPU/EM Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
A022 Voice Mail Unit 100% Full (VPU/EM Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
A023 SMDR Unit 80% Full (VPU/EM Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
A024 SMDR Unit 100% Full (VPU/EM Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
A025 Voice Processing Unit <n>: <message>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
A026 Voice Processing Email Gateway is Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
A027 Voice Processing <app> Application Corrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
A028 Voice Processing Unit Out of Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
A030 <VoiceMailUnit> No Primary Language Prompts Installed . . . . . . . . . . . . . . . . . . . . . 7
A031 <VoiceMailUnit> Hacker Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
A032 Extension <eeeee> Received Insufficient Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . 7
Major System Alarms (A100–A199) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
A100 Device <b.p.d> Extension <eeeee>: Reset Due to Excessive Data Errors . . . . . . . . 8
A101 Device <b.p.d> Extension <eeeee>: Reset Due to Excessive Hardware Failures . . . 8
A102 Serial Port <b.p.d>: Tx Interrupt is Not Operational (Axxess Only) . . . . . . . . . . . . . . 9
A103 Serial Port <b.p.d>: Clock is Not Operational (Axxess Only) . . . . . . . . . . . . . . . . . . . 9
A104 ALARM CPU: Database Corruption (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 9
A105 CPU: Write-Protect is Not Operational (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . 10
A106 CPU: Real-Time Clock is Not Operational (Axxess Only). . . . . . . . . . . . . . . . . . . . . 10
A107 CPU: Watchdog is Not Operational (Axxess Only Pre v8.0). . . . . . . . . . . . . . . . . . . 10
A108 CPU: Interval Timer is Intermittent (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 10
A109 CPU: Watchdog Expired During Minor Reset (Axxess Only) . . . . . . . . . . . . . . . . . . 10
A110 CPU: Database Feature Bundling Error (Axxess Only Pre v8.0) . . . . . . . . . . . . . . . 11
A111 CPU: Battery Backed Memory Too Low (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 11
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page v
Contents
Page vi Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Contents
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page vii
Contents
Page viii Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Contents
M2031 SLC16 72-Volt Power Supply Recovered on Board <board> (Axxess Only) . . . . . 43
M2032 OS Info on <board_type> <b.p.d>, Additional Info: <data> (Axxess Only) . . . . . . 43
M2033 OS Version for CPU <cpu_number> is <version_string> (Axxess Only) . . . . . . . . 44
M2034 On-Line from VoIP DSP(s) <numberstart>–<numberend> on Board <board> . . . 44
M2035 Off-Line from VoIP DSP <numberstart>–<numberend> on Board <board> . . . . . 44
M2036 Established IP LINK to Node <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
M2037 Closed IP LINK to Node <num> – Reason <reason> <string> . . . . . . . . . . . . . . . 45
M2038 Failed Session Startup with Node <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
M2039 Dead Socket Response from Node <node_num>:
Reason <code>, <code_string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
M2040 CPC ‘*’ Button Pressed (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
M2041 CPC ‘*’ Button Acknowledged (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
M2042 Failed to Allocate a VoIP from Board <board>. . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
M2043 VoIP DSP <VoIP_DSP> on Board <board_num> is Unavailable Due to
Insufficient Networking VoIP from License (Axxess Only) . . . . . . . . . . . . . . . . . . . 47
M2044 Session <session_id> is Closed Due to Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
M2045 <b.p.d>: <type> IP Address: <address> Hostname: <name> . . . . . . . . . . . . . . . . 47
M2046 IP Connection <ext_received> Minor-Reset Notification
While Not On-Line (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
M2047 IP Connection <ext_received> Minor-Reset Notification (Axxess Only) . . . . . . . . 48
M2048 Device <address> Unbusied Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
M2049 <ext>: Application Data and Control <conn> From <device>. . . . . . . . . . . . . . . . . 48
M2050 Serial Input Queue Overflow – Character Ignored (Axxess Only) . . . . . . . . . . . . . 48
M2094 CP Time Changed for Daylight Saving Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
M2095 <b.p.d>: Automatically Enabled Premium Feature: <feature>
(Axxess Only Pre v8.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
M2096 <b.p.d>: Automatic Equip of <board> Successful . . . . . . . . . . . . . . . . . . . . . . . . . 49
M2097 System Reconfigure in Progress (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 49
M2098 System Reconfigure Complete (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
M2099 <card> Real-Time Clock Stopped but Now Running (Axxess Only) . . . . . . . . . . . 50
M2100 Timed-Out Waiting for a Ring Input on DI Circuit <b.p.d> . . . . . . . . . . . . . . . . . . . 50
M2101 IPRC PAL Ignored on Board <board> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 50
M2102 PIN Registration Successful For <new MAC address> on <extension> . . . . . . . . 50
M2103 PIN Replacement Of <old MAC address> Successful for
<new MAC address> on <extension> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Engineering Informational Messages (M3000–M3999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
M3000 MAJOR RESET: Power-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
M3000 Minor Reset: Reset Button (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
M3000 Minor Reset: OS Detected Software Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
M3000 MAJOR RESET: OS Detected Software Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
M3000 MAJOR RESET: Watchdog Expired During OS MAJOR Reset Process. . . . . . . . 51
M3000 MAJOR RESET: Watchdog Expired During OS Minor Reset Process . . . . . . . . . 52
M3000 MAJOR RESET: Watchdog Expired During User Task MAJOR Reset Process . . 53
M3000 MAJOR RESET: Watchdog Expired During User Task Minor
Reset Process (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
M3000 MAJOR RESET: User Task Detected Software Error . . . . . . . . . . . . . . . . . . . . . . 54
M3000 Minor Reset: User Task Detected Software Error . . . . . . . . . . . . . . . . . . . . . . . . . 54
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page ix
Contents
Page x Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Contents
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page xi
Contents
Page xii Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Contents
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page xiii
Contents
Page xiv Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Contents
M5098 <b.p.d>: Online Ignored for <type> DSS/PKM unit <limit: [limit]> . . . . . . . . . . . . 100
M5099 <card>: Real-Time Clock is Stopped (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 101
M5100 <b.p.d>: Communications Error from <name> (Axxess Only) . . . . . . . . . . . . . . . 101
M5101 <b.p.d>: Error Message Lost for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . 101
M5102 <b.p.d>: Incorrect Interrupt Mask for <name> (Axxess Only) . . . . . . . . . . . . . . . 101
M5103 <b.p.d>: No Response Error from <name> (Axxess Only). . . . . . . . . . . . . . . . . . 101
M5104 <b.p.d>: OMSCI Error Code from <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
M5105 <b.p.d>: Spurious Reset for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 102
M5106 <b.p.d>: State Error for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 102
M5107 <b.p.d>: SWI Error from <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . 102
M5108 <b.p.d>: Transmit Data Register Empty for <name> (Axxess Only) . . . . . . . . . . 102
M5109 <b.p.d>: Timer Error for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . 102
M5110 <b.p.d>: Transmission Error from <name> (Axxess Only) . . . . . . . . . . . . . . . . . . 103
M5111 <b.p.d>: Trap Error for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 103
M5112 <b.p.d>: Spurious Reset for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 103
M5113 <b.p.d>: <name> Received Ground Start Programming (Axxess Only) . . . . . . . 103
M5114 <b.p.d>: Reconfigure Request from <name> (Axxess Only) . . . . . . . . . . . . . . . . 103
M5115 PP Command Sent After <num> Tries (Axxess Only) . . . . . . . . . . . . . . . . . . . . . 104
M5116 <b.p.d>: (RMGR) Invalid PP Response: Type = <xx>,
Board = <bb>, Circuit = <cc>, MSG = <zz> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
M5117 <b.p.d>: (RMGR) Dialing Time-Out Error for <b.p.d> . . . . . . . . . . . . . . . . . . . . . 104
M5118 <b.p.d>: (RMGR) DSP <x> Status Error = <error> . . . . . . . . . . . . . . . . . . . . . . . 104
M5119 <side>: Fiber-Optic Local Error Count too High;
Rate = <rate> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
M5121 <side>: Fiber-Optic Remote Error Count too High;
Rate = <rate> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
M5122 Nodes did Not Respond to Broadcast Message from
Ext <eeeee>: Nodes <node_list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
M5123 <b.p.d> <board>: Incompatible ISDN FW Version = <ver1> (Expecting <ver2>)
(Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
M5124 <b.p.d> <board>: Incompatible FW Version = <ver1>
Expecting <ver2> or Higher (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
M5125 Received Call on Unequipped Trunk <b.p.d> . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
M5126 <b.p.d> Jumper Prevents Boot-Code Upgrade (Axxess Only). . . . . . . . . . . . . . . 106
M5128 <b.p.d> Board is Out of Sync with Download Task (Axxess Only). . . . . . . . . . . . 106
M5129 <b.p.d> Missing Jumper Protection for Card's Boot Sector (Axxess Only) . . . . . 107
M5130 <b.p.d>: Must Remove BBPC for Normal Operation (Axxess Only) . . . . . . . . . . 107
M5131 <b.p.d>: Boot Code Image is Empty (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . 107
M5132 <b.p.d>: Name Code Image is Empty (Axxess Only). . . . . . . . . . . . . . . . . . . . . . 107
M5133 <time>: Threshold for <threshold> Errors Exceed on BRI Port <b.p.d>. . . . . . . . 107
M5134 OS Version Mismatch: Version Should be at
Least <version_string> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
M5135 <b.p.d>: (RMGR) Invalid DSP Command: Size = <xx>, Command = <zz> . . . . . 108
M5136 <b.p.d>: Caller ID Transmitter Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
M5137 <b.p.d>: IP SoftPhone Programmed as an IP Keyset Device is Ignored . . . . . . . 108
M5138 (RMGR) DSP Dialing Timeout Error for <b.p.d> . . . . . . . . . . . . . . . . . . . . . . . . . 109
M5139 (RMGR) DSP Digit Queue Full Error for <b.p.d> . . . . . . . . . . . . . . . . . . . . . . . . . 109
M5140 IP Phone With MAC <MAC address> Locked Out Due to
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page xv
Contents
Page xvi Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Contents
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page xvii
Contents
Page xviii Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Contents
M6125 Device <ext> Failed to Find the Other Device <ext1> System
Echo Canceller Configuration Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
M6126 <eeee>: Audio Receive Port Changed From <old_port> to <new_port> . . . . . . . 139
M6127 Generic SIP Error Message <s> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
M6128 <s1> File-Based Audio Source <N1> <s2> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
M6129 Module <number1> in DEI <number2> Failed to Come
Online: Not in Quad-DEI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
M6130 File-Based Audio Source <N1> - <s1>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
M6131 HTML Application File Not Found: Profile <number> File <filename> . . . . . . . . . 140
M6132 <eeee>: HTML Application <app> Not Found for Language <lang> . . . . . . . . . . 140
M6133 <eeee>: HTML Application <app> Not Found for Device Type <device> . . . . . . 140
Database Severe Error Messages (M7000–M7999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
M7000 Battery-Backed Memory Full for Equip of <object> <b.p.d>. . . . . . . . . . . . . . . . . 141
M7001 Database Defaulted Due to OS Indicates Battery-Backed
Memory Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
M7001 Database Defaulted Due to Internal Database Pointer is Invalid . . . . . . . . . . . . . 141
M7001 Database Defaulted Due to Forced Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
M7001 Database Defaulted Due to CODE Change: Last Function Relocated . . . . . . . . 142
M7001 Database Defaulted Due to CODE Change: Last CODE Table Relocated . . . . . 142
M7002 Battery-Backed Memory Full for Extension List Addition <ext> . . . . . . . . . . . . . . 143
M7003 Database Out-of-Synch: Record <id>, Sequence <seq>,
Bit <bit>, Max Bit <maxbit>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
M7004 Database Compression/Decompression Error. . . . . . . . . . . . . . . . . . . . . . . . . . . 143
M7005 Another Node does Not Know About Node <number> . . . . . . . . . . . . . . . . . . . . 144
M7006 Node <number1> does Not Know About Node <number2>. . . . . . . . . . . . . . . . . 144
M7007 Invalid Software License – Reset in <xx> Minutes. . . . . . . . . . . . . . . . . . . . . . . . 144
Hardware Severe Error Messages (M8000–M8999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
M8000 <string> Condition Detected on <board_type> <b.p.d> . . . . . . . . . . . . . . . . . . . . 145
M8001 <board_type> Problem: <type> (North America) . . . . . . . . . . . . . . . . . . . . . . . . . 145
M8001 <board_type> Problem: <type> (Europe). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
M8002 <string> Condition Cleared on <board_type> <b.p.d> . . . . . . . . . . . . . . . . . . . . . 147
M8003 All Calls on <board_type> <b.p.d> have been Dropped . . . . . . . . . . . . . . . . . . . 147
M8004 <board_type> <b.p.d> Failed <test_type> Self-Test . . . . . . . . . . . . . . . . . . . . . . 147
M8005 <device> <b.p.d> Command too Large for Buffer:
Length <xx > Buffer Size <yy> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
M8009 T1 Card <card> Detected Missing Network Clock Card
(Axxess Only Pre v8.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
M8010 <side>: Fiber FPR Indicates Abnormal Status = <status> (Axxess Only) . . . . . . 148
M8011 <side>: No Signal from Fiber Optic Cable (Axxess Only) . . . . . . . . . . . . . . . . . . 149
M8012 <side>: No Signal from Fiber Optic Cable;
Resetting Communication (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
M8013 <side>: Fiber-Optic Multiplexer is Out-of-Sync:
Sync = <sync> (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
M8014 <side>: Fiber-Optic Multiplexer is Out-of-Sync (Two Masters): Sync = <sync>
(Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
M8015 <side>: Fiber-Optic Multiplexer is Out-of-Sync;
Resetting Comm Sync = <sync> (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . 150
M8019 <side>: Fiber Controller Inactive (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page xix
Contents
Page xx Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Contents
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page xxi
Contents
M9011 ASAI User Info Message Exceeds Maximum Allowed Length . . . . . . . . . . . . . . . 169
M9012 ASAI Call Dropped by Call Processing Due to Invalid Call State. . . . . . . . . . . . . 169
M9013 ASAI Call Dropped by ASAI Peer Due to Invalid Call State . . . . . . . . . . . . . . . . . 169
M9014 Unable to Realloc Memory for ASAI User Info Message . . . . . . . . . . . . . . . . . . . 170
M9015 The Dynamic Heap has been Defragmented (Axxess Only) . . . . . . . . . . . . . . . . 170
M9016 DSP Watchdog Detected Failure of <device> . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
M9020 Exception Recorded: DMTRACK Synchronization Error on
Port <port> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
M9021 <eeee>: Null VoIP DSP Resource Pointer Found in
<routine> Resulting in No/One-Way Audio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
M9022 <eeee>: Invalid Audio Receive Port Range Received – Result = No Audio . . . . 171
M9090 <Voice_Mail_Unit> PC Watchdog Reset Occurred (VPU/EM Only) . . . . . . . . . . 171
Page xxii Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Overview
Overview
The Message Print Diagnostics Manual supports the MiVoice Office 250 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.
Please note that as of release 6.1, the Mitel 5000 Communications Platform (CP) is rebranded
to the MiVoice Office 250 platform. All references in this document to the 5000 CP product apply
to the MiVoice Office 250 Product.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 1
Alarm Messages (A000–1099): Minor System Alarms (A000–A019)
Page 2 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Alarm Messages (A000–1099): Minor System Alarms (A000–A019)
A database restore will set the time and date to that of the remote computer if the
NOTE
restore occurs on a system where the time and date are uninitialized.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 3
Alarm Messages (A000–1099): Minor System Alarms (A000–A019)
Page 4 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Alarm Messages (A000–1099): Minor Voice Processing Alarms (A020–A039)
The voice processing unit displays this alarm only when it first recognizes the
NOTE condition. It will not repeat the alarm unless someone reboots the voice
processing unit or solves the problem.
NOTE Changing the size of the SMDR buffer discards all stored SMDR records.
To send a broadcast message requesting that users delete their old messages,
you will first need to delete a few messages to free up enough space for the
NOTE broadcast message.
Changing the size of the SMDR buffer discards all stored SMDR records. The
Unified Voice Messaging Module on the 5000 CP does not have a SMDR buffer.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 5
Alarm Messages (A000–1099): Minor Voice Processing Alarms (A020–A039)
Changing the size of the SMDR buffer discards all stored SMDR records. The
NOTE Unified Voice Messaging Module on the 5000 CP does not reserve SMDR
storage.
Increasing or changing the size of the SMDR buffer discards all stored SMDR
NOTE records. The Unified Voice Messaging Module on the 5000 CP does not reserve
SMDR storage.
Page 6 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Alarm Messages (A000–1099): Minor Voice Processing Alarms (A020–A039)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 7
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
Page 8 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
AXXESS ACTION: Check the phone (perform a self-test). Check the cabling (the wiring is sound, all unused wires
are punched down to ground, the cable does not run near any sources of strong interference),
and connectors (amphenols, punch-down blocks, etc.). Swap the questionable phone with
another phone to see if the problem follows the wiring or the phone. Swap the DKSC board with
another DKSC board to see if the problem follows the DKSC board. Replace or fix the
appropriate hardware component. See M5071 (page 93) for more information.
5000 ACTION: Check the phone (perform a self-test). Check the cabling (the wiring is sound, all unused wires
are punched down to ground, the cable does not run near any sources of strong interference),
and connectors (amphenols, punch-down blocks, etc.). Swap the questionable phone with
another phone to see if the problem follows the wiring or the phone. Replace the appropriate
hardware component. Return the faulty component to Mitel for repair. See M5071 (page 93) for
more information.
NOTE If the power is turned off, the system will default the database.
ACTION: Save the database to the computer via an “axx” file as soon as possible. Do not save the “axx”
file on top of a previously known-good database because this database may be too corrupted in
a critical location. Keep in mind that the “Backup Database” may be a non-corrupted database.
If the existing database appears corrupted, default the system's database, without the voice
processor connected. After the system powers up, the default database LED will be on. Reset
the system one time to force a “Backup Restore”. If the “Backup Restore” reveals a corrupted
database, restore the last known “axx” file.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 9
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
Page 10 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
This alarm also occurs after restoring a database that has more features enabled
NOTE
than the system allows.
ACTION: If the problem is a hacker, take necessary lawful action. Otherwise, try another feature chip. If
the problem persists, replace the CPU board. If this alarm occurs due to restoring a database
that had too many features turned on, go into the Premium Features Selection screen and re-
enable the appropriate features.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 11
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
Page 12 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 13
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
Page 14 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 15
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
Page 16 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 17
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
Page 18 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
This is an auto clearing alarm. This alarm will be automatically cleared by the
NOTE
MiVO 250 when the SIP Phone registers again using a secure Password.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 19
Alarm Messages (A000–1099): Major System Alarms (A100–A199)
Debug logging level and Extended CP Logging may be enabled under the
guidance of Mitel Product Support. This alarm will be automatically cleared by the
system when the debug logging level for all Applications or Extended CP logging
NOTE
are disabled after investigations are completed. The Alarm 150 will not appear on
administrator telephones, it will only appear within System Administration and
Diagnostics, and Message Print.
Page 20 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Alarm Messages (A000–1099): Major Voice Processing Alarms (A200–A224)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 21
Alarm Messages (A000–1099): Major Voice Processing Alarms (A200–A224)
If step 1 or step 2 had audio, the alarm is most likely related to an internal software issue.
Notice that the system has registered a delayed major and will perform a soft reset at the
system delayed major time.
If step 1 or step 2 had no-audio, the processor module has encountered a fatal issue. Perform a
system reboot at the first possible opportunity. Mitel recommends that the Database
Programming administrator enable "reboot system" in the delayed major settings. This will
cause the entire system to reboot at the system delayed major time. For a Mitel 5000 system
with a PS-1, both the PS-1 and BS will require a reboot.
If resetting both systems does not clear the problem, there is probably a hardware problem. You
can check the port by creating a Database Programming session on the port.
Page 22 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
Alarm Messages (A000–1099): Network Alarms (A225–A244)
5000 ACTION: First, see if the problem has already been corrected; if a call is attempted to a voice processing
unit extension and any message other than “xxx IS UNPLUGGED” is displayed, then the
problem has corrected itself. If the problem does not correct itself, verify that the voice
processing unit IP settings is still valid (IP address and IP port). Viewing message print will
show whether the voice mail ASAI link can be established. If so, reboot the voice processing
unit and determine whether this corrects the problem, such as voice processing unit extensions
can be called after the voice processing unit has completed its reboot process. If the voice
processing unit is still inaccessible, attempt to clear up the problem by rebooting the system.
For external VM units, if resetting both systems does not clear the problem, there is a potential
hardware/software problem on the voice mail unit. For Unified Voice Messaging, create a
Remedy ticket and enable Automatic Diagnostics Delivery (ADD). Send the ADD freeze to
Technical Support.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 23
Alarm Messages (A000–1099): System Application Alarms (A1001–A1099)
Page 24 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Operating System Startup Severe Messages (M0001–M0049)
The fact that the OS must use the CPU's primary port for reporting errors during
the system startup phase suggests that IT IS BEST TO HAVE MESSAGE PRINT
NOTE
CONNECTED TO THE PRIMARY CPU PORT. It is also best to have message
print connected to the primary CPU port when first powering up a new system.
M0002 CPU Dynamic RAM Not Present or Bad (Axxess Only Pre
v8.0)
FIELDS: None.
CAUSE: One or more of the RAM chips on the CPU or MEM board is not present, not pushed in all the
way, or is faulty.
ACTION: Power the system down and remove the CPU board. Verify all the RAM chips are present and
the pins on the chips are in the sockets properly. Push on each chip to verify it is in its socket
properly. Reinsert the board. If the error message repeats itself, swap out the RAM or the entire
CPU or MEM board.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 25
System Messages (M0001–M9999): Operating System Startup Severe Messages (M0001–M0049)
Page 26 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Operating System Startup Severe Messages (M0001–M0049)
M0008 CPU Interrupt Level 2 Stuck True (Axxess Only Pre v8.0)
FIELDS: None.
CAUSE: The processor on the CPU board is continuously receiving a level 2 interrupt. This prevents the
CPU from running normally.
ACTION: Replace the CPU board. If the problem recurs, contact Mitel Field Service.
FSACTION: Report the problem to the engineering contact person for further analysis. Try to obtain the
entire failing CPU board to help engineering diagnose the problem.
M0009 CPU Interrupt Level 3 Stuck True (Axxess Only Pre v8.0)
FIELDS: None.
CAUSE: The processor on the CPU board is continuously receiving a level 3 interrupt. This prevents the
CPU from running normally.
ACTION: Replace the CPU board. If the problem recurs, contact Mitel Field Service.
FSACTION: Report the problem to the engineering contact person for further analysis. Try to obtain the
entire failing CPU board to help engineering diagnose the problem.
M0010 CPU Interrupt Level 4 Stuck True (Axxess Only Pre v8.0)
FIELDS: None.
CAUSE: The processor on the CPU board is continuously receiving a level 4 interrupt. This prevents the
CPU from running normally.
ACTION: Replace the CPU board. If the problem recurs, contact Mitel Field Service.
FSACTION: Report the problem to the engineering contact person for further analysis. Try to obtain the
entire failing CPU board to help engineering diagnose the problem.
M0011 CPU Interrupt Level 5 Stuck True (Axxess Only Pre v8.0)
FIELDS: None.
CAUSE: The processor on the CPU board is continuously receiving a level 5 interrupt. This prevents the
CPU from running normally.
ACTION: Replace the CPU board. If the problem recurs, contact Mitel Field Service.
FSACTION: Report the problem to the engineering contact person for further analysis. Try to obtain the
entire failing CPU board to help engineering diagnose the problem.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 27
System Messages (M0001–M9999): Operating System Startup Severe Messages (M0001–M0049)
M0013 CPU Interrupt Level 7 Stuck True (Axxess Only Pre v8.0)
FIELDS: None.
CAUSE: The processor on the CPU board is continuously receiving a level 7 interrupt. This prevents the
CPU from running normally.
ACTION: Replace the CPU board. If the problem recurs, contact Mitel Field Service.
FSACTION: Report the problem to the engineering contact person for further analysis. Try to obtain the
entire failing CPU board to help engineering diagnose the problem.
Page 28 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Operating System Startup Warning Messages (M0050–M0099)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 29
System Messages (M0001–M9999): Operating System Startup Warning Messages (M0050–M0099)
Page 30 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Database Informational Messages (M1000–M1999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 31
System Messages (M0001–M9999): Database Informational Messages (M1000–M1999)
Page 32 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Database Informational Messages (M1000–M1999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 33
System Messages (M0001–M9999): Database Informational Messages (M1000–M1999)
Page 34 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Database Informational Messages (M1000–M1999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 35
System Messages (M0001–M9999): Database Informational Messages (M1000–M1999)
Page 36 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 37
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
NOTE Programmable Key Modules (PKM) are supported on the Mitel 5000 only.
Page 38 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 39
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
5000 ACTION: Normally, the DSP will go off line before coming on line. Verify that the DSP has come on line.
However, if some problems have occurred which cause the DSP to go off line and not come
back on line, we recommend that the system be reset manually, using the Database
Programming's Reset System command. If the system is in a state such that Database
Programming cannot connect, reset the system manually through the front panel LCD and
navigation buttons. If the DSP still doesn't come on line contact Field Service for analysis of this
problem.
FSACTION: Report the problem to the engineering contact person for further analysis. Provide the entire
failing CPU board to help engineering diagnose the problem.
Page 40 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 41
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
Page 42 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 43
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
Page 44 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
AXXESS FS ACTION: Report the problem to the engineering contact person for further analysis. Provide the entire
failing CPU board to help engineering diagnose the problem.
5000 FS ACTION: Report the problem to the engineering contact person for further analysis. Send the offending
Processor module or Processor Expansion Card to Mitel Field Service.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 45
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
Page 46 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
5000 ACTION: Call Processing will camp on to the Node Route Group and the phone will display a camp-on
message. In Database Programming, make sure there are enough IP resources available for
networking.
For the phone, make sure there are enough phone VoIPs programmed in Database
Programming. IP phones must allocate VoIPs from the board where they reside. The phones
with display should see WAITING FOR RESOURCE on the display. If all the VoIPs are being
used for phones or networking calls, the station will get the next available VoIP when one of the
calls terminates or an phone goes off-line.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 47
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
Page 48 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
Shortly following this message, the system will print out M2098 System
Reconfigure Complete. If there is a problem with the reconfigure, the “Complete”
NOTE message may not occur and the system will hang. In this case, you will have to
power the system down to get it to come back up. Additionally, contact Mitel Field
Service to report this problem.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 49
System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)
Page 50 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 51
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
5000 ACTION: The system is probably in a continuous series of major resets. Attempt to reset the system
using the front panel LCD and navigation keys. Cycle power once the system shut down safely.
If the system comes up, perform the steps indicated below. If the system fails to come up,
remove all other modules except the Processor Module. If the system still fails to come up,
replace the Processor Module. If the system comes back up, restore a saved version of the
customer's database. Record as much information as possible about the events that preceded
the major reset. Use Database Programming to save the database and obtain the CP Error
Information. Contact Mitel Field Service with this information.
AXXESS FS ACTION: Report the problem to the engineering contact person for further analysis. Provide a valid CP
Error Information freeze and the database. If the technician replaced the CPU board, try to
obtain the entire failing CPU board to help engineering diagnose the problem.
5000 FS ACTION: Report the problem to the engineering contact person for further analysis. Provide a valid CP
Error Information freeze and the database. If the technician replaced the Processor Module and/
or Processor Expansion Module, send these modules to engineering so they can diagnose the
problem.
Page 52 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 53
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Page 54 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Because CP relies so heavily on the heap, a heap corruption could cause other
serious problem to occur, such as bus errors and minor resets. Therefore, it is
NOTE
unlikely that this message will occur because the system will probably reset before
this message has a chance of printing.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 55
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Page 56 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 57
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Before shutting down the system, the technician can dump "Call Diagnostics" to
determine what calls may be preventing the system from resetting. If the "Call
NOTE Diagnostics" are not helpful, run the Resource Periodic Diagnostics to help identify
and/or clean up any failures within the system. If this is not successful, then reset
the system.
Page 58 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 59
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Page 60 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 61
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Page 62 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
M3109 Device <device> Ext <eeeee> did Not Receive Release ACK
for TI Call ID <id>
FIELDS: device The device that did not receive the expected message.
eeeee The device’s extension.
id The TI call id that Call Processing posts in the ti_api_translator table.
CAUSE: This information applies only to private networking calls. Call Processing needs to receive a
release ack from the remote node before we can tear down a networking call. However, Call
Processing failed to receive anything from the remote while the wait state timer expired. As a
result, Call Processing will send a disconnect or clear request to the remote node and then tear
down the networking call. The private networking link to the remote is probably down in this
case.
ACTION: None.
An Automatic Diagnostics freeze will have the “.lm” file extension, which holds the
NOTE
license manager dump information.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 63
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Page 64 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 65
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
This message only occurs if the CPH "Log System OAI Input" flag is
NOTE
enabled.
This message only occurs if the CPH "Log System OAI Input" flag is
NOTE
enabled.
This message only occurs if the CPH "Log System OAI Input" flag is
NOTE
enabled.
Page 66 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 67
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Page 68 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 69
System Messages (M0001–M9999): Database Warning Messages (M4000–M4999)
Page 70 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Database Warning Messages (M4000–M4999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 71
System Messages (M0001–M9999): Database Warning Messages (M4000–M4999)
This message will also be generated when the device being equipped has an
NOTE
extension which conflicts with an existing extension on this node.
Page 72 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Database Warning Messages (M4000–M4999)
M4012 BRI Trunk Port <b.p.d> does Not have Any SPIDS
Programmed
FIELDS: b.p.d The board/port/device of the BRI Trunk Port that reported the error.
CAUSE: The BRI Trunk Port does not have any SPIDs programmed.
ACTION: Log into Database Programming and program the SPIDs and Directory Numbers assigned to
this port. The Central Office provides these values when the BRI circuit is ordered.
Non-ISDN trunks cannot accept ISDN data calls. If a node trunk group reported
the problem, see if the node trunk group is connected to a 3200N. If so, do not
NOTE give outgoing access to the ISDN device. Otherwise, change the ISDN Data Calls
flag to “yes.”
Due to voice compression, a 3200N cannot accept ISDN data calls.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 73
System Messages (M0001–M9999): Database Warning Messages (M4000–M4999)
Page 74 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 75
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 76 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 77
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 78 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 79
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
M5017 DSS Error for DSS <number> <b.p.d>: <s-Side> Frame Error
FIELDS: number The DSS number the problem occurred on.
b.p.d The board/port/device of the DSS unit reporting the error.
s-Side The DSS-side indicator (A-Side or B-Side).
CAUSE: A framing error was detected on the indicated DSS. A framing error is detected by an invalid
framing bit (stop bit) in the information sent to the DSS unit from the phone or intermediate DSS
unit. The invalid command or data byte is ignored. The problem is caused by transmission
errors, possibly due to Electromagnetic Interference, a faulty transmitter, or a faulty receiver.
ACTION: An occasional problem is acceptable. Verify there is no major EMI source near the DSS cables.
If the problem persists, replace the DSS unit, phone, and intervening cables.
M5019 DSS Error for DSS <number> <b.p.d>: Data Lost Error
FIELDS: number The DSS number the problem occurred on.
b.p.d The board/port/device of the DSS unit reporting the error.
AXXESS CAUSE: Data from the DSS unit was not sent to the DKSC board fast enough, so data stored in the DSS
unit to be sent to the system was lost. This message indicates a hardware problem.
5000 CAUSE: Data from the DSS unit was not sent to the DE module fast enough, so data stored in the DSS
unit to be sent to the system was lost. This message indicates a hardware problem.
ACTION: Except for lost DSS keystrokes, the user should experience no major problems. Replace the
indicated DSS unit. Verify there is no major EMI source near the DSS cables. Perform a freeze
immediately following the problem and send the results to Mitel Field Service. If the problem
persists, replace the phone, and intervening cables.
Page 80 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 81
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
M5028 High Ring Line Error for <b.p.d> End High Ring Line Error
for <b.p.d>
FIELDS: b.p.d The board/port/device of the trunk that experienced the high ring line error.
CAUSE: A High Ring Line Error message is printed whenever a trunk circuit's Ring Detect Status bit is
active for an unusually long period of time. This generally indicates a hardware failure or wiring
problem. The End High Ring Line Error message is printed when the trunk circuit's Ring Detect
Status bit becomes deactivated after it was active for an unusually long period of time. This
corresponds to the error condition appearing to be corrected.
AXXESS ACTION: For the High Ring Line Error, verify that the wiring is correct for the indicated trunk circuit. If the
problem persists, replace the LSC (or LSCD) board.
5000 ACTION: For the High Ring Line Error, verify that the wiring is correct for the indicated trunk circuit. If the
problem persists, replace the LS expansion module or immediately following the error, perform
a Freeze and send the information to Mitel Field Service. If the problem occurs on one of the 2
on-board loopstart trunks, report the information to Mitel Field Service.
Early in Beta Test, a problem existed in the firmware that caused this to occur
NOTE occasionally. If this is a Beta LSC (or LSCD) board, replace it with a newer
release to see if the problem goes away.
Page 82 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 83
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 84 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 85
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 86 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 87
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 88 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 89
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 90 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 91
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 92 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 93
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 94 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 95
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 96 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 97
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 98 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 99
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
NOTE Programmable Key Modules (PKM) are supported on the Mitel 5000 only.
Page 100 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 101
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 102 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 103
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 104 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 105
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 106 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 107
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Page 108 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 109
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 110 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 111
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 112 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 113
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 114 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 115
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 116 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 117
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 118 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 119
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 120 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 121
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 122 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 123
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 124 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 125
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 126 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 127
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 128 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
M6074 Invalid Digit String <invalid length> with Max Length <max
length>
FIELDS: invalid length The current length of the digit string.
max length The digit string’s maximum length.
CAUSE: Corrupted data.
ACTION: Freeze on this string and send the information to Engineering.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 129
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 130 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 131
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 132 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
For v5.2, the system message version is 13; for v5.3, it is 15. Therefore, if a node
NOTE has message version 14 or a version earlier than 13, this warning message will be
sent.
5000 CAUSE: Mitel CS5200/CS5400 v1.0 systems will only network with versions of Axxess v8.1 or later and
other Mitel CS5200/CS5400 v1.0 systems.
ACTION: Upgrade the indicated node to the appropriate system message version.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 133
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 134 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 135
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 136 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
The system can be configured to reserve DSP resources for networking, station,
NOTE
trunk and emergency calls.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 137
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
The system can be configure to reserve DSP resources for networking, station,
NOTE
trunk, and emergency calls.
M6125 Device <ext> Failed to Find the Other Device <ext1> System
Echo Canceller Configuration Number
FIELDS: ext The device on the Dual T1/E1/PRI who is trying to determine the dynamically echo canceller
setting.
ext1 The other device that ext is connected.
CAUSE(S): The system echo canceler configuration setting are set dynamically on each call depending on
the type of connection. There are times the other device information stored in the call info is not
a valid ID and the system depends on that information to determine what the other device is.
Because the information is not available, the system cannot find out what the other device is, so
the system will use the medium profile setting.
ACTION: This should only affect Dual T1/E1/PRI modules. If the device involved does not reside on a
Dual T1, discard the warning. Otherwise, freeze the system immediately and send the
information to Mitel Engineering. Engineering is only enabling this warning in development and
the field should be removed before production.
Page 138 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 139
System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)
Page 140 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Database Severe Error Messages (M7000–M7999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 141
System Messages (M0001–M9999): Database Severe Error Messages (M7000–M7999)
Page 142 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Database Severe Error Messages (M7000–M7999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 143
System Messages (M0001–M9999): Database Severe Error Messages (M7000–M7999)
Page 144 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 145
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Page 146 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Transmitting Alarm Indication Signal (AIS). The T1 has begun transmitting AIS. This can
occur if Applications requests that the T1 transmit AIS, which is acceptable. It can also
mean that the T1 has lost the signal from the network. Refer to the to the actions detailed
under that item.
Transmitting Remote Alarm Indication (RAI). This alarm should not occur because it is not
implemented. The current T1 code transmits RAI only when it is in Red Alarm for a reason
other than receiving AIS. This alarm would be active if the T1 would transmit RAI when not
in the Red Alarm State. Notify Field Service if this ever occurs.
Remote Loopback State. This alarm should not occur because the T1 transceiver can't
detect a loopback code. Notify Field Service if this ever occurs.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 147
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Page 148 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 149
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Page 150 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 151
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Page 152 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 153
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Page 154 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 155
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Page 156 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 157
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Page 158 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 159
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Page 160 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 161
System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)
Page 162 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 163
System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)
Page 164 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 165
System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)
Page 166 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 167
System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)
Page 168 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)
M9013 ASAI Call Dropped by ASAI Peer Due to Invalid Call State
FIELDS: None.
CAUSE: The CP software received a message from an ASAI peer device out of sequence and
responded with a status message indicating that the states do not match. Because the states do
not match, the ASAI peer device drops the call. This relates primarily with calls to the Voice
Mail.
ACTION: Freeze the system history immediately. Then use Database Programming to save the database
and obtain the CP Error Information. Contact Mitel Field Service with this information.
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 169
System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)
Page 170 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)
Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018 Page 171
System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)
Page 172 Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, May 2018
© Copyright 2018, Mitel Networks Corporation. All Rights Reserved. The Mitel word and logo are trademarks of Mitel Networks
Corporation, including itself and subsidiaries and authorized entities. Any reference to third party trademarks are for reference only and Mitel
mitel.com makes no representation of ownership of these marks.