mitel 5000 error logs - denwa's guide

Mitel® 5000 and Inter-Tel® Axxess®

Message Print

M I T E L

Diagnostics Manual

Issue 23, January 2011

Mitel® 5000 and Inter-Tel® Axxess®

Message PrintDiagnostics Manual

Part Number550.8018

NoticeThis manual is released by Mitel Networks Corporation as a guide for certified service personnel. It provides information necessary to properly perform diagnostics on the systems.

The contents of this document reflect current company standards and are subject to revision or change without notice. Some features or applications mentioned may require a future release and are not available in the release. Future product features and applications are subject to availability and cost. Some features or applications may require additional hardware and/or specific software.

The contents of this manual may include technical or other inaccuracies. Mitel reserves the right to make revisions or changes without prior notice. Software packages released after the publication of this manual will be documented in addenda to the manual or succeeding issues of the manual.

For additional information and/or technical assistance in North America, certified technicians may contact:

Technical Support Department (USA)Mitel Networks Corporation

7300 West Boston StreetChandler, AZ 85226-32241-888-777-EASY (3279)

For information on how to contact Mitel Technical Support outside of North America, please refer to your Channel Support Agreement.

If you have any questions or comments regarding this manual or other technical documentation, contact the Technical Publications Department (USA) at:

[email protected]

Mitel® is a registered trademark of Mitel Networks Corporation.Inter-Tel® is a registered trademark of Inter-Tel (Delaware), Incorporated.

All other trademarks mentioned in this document are the property of their respective owners, including Mitel Networks Corporation and Inter-Tel (Delaware), Incorporated. All rights reserved.

© 2005–2011 Mitel Networks CorporationPersonal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from Mitel Networks Corporation.

mailto:[email protected]

Contents

Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page v

ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Alarm Messages (A000–1099) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Minor System Alarms (A000–A019) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

A000 Alarm Automatically Cleared. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2A001 Alarm Manually Cleared by Ext <eeeee> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2A002 Network Alarm Automatically Cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2A003 Network Alarm Manually Cleared by Ext <eeeee> . . . . . . . . . . . . . . . . . . . . . . . . . . . 2A010 Ext <eeeee> – <username> is Off-Hook (5000 Only). . . . . . . . . . . . . . . . . . . . . . . . . 2A011 Emergency Call Made by Ext <eeeee> – <username> @

<hot_desk_info> (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3A012 SMDR Printer Off-Line (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3A013 Message Printer Off-Line (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3A014 Real-Time Clock Needs to be Set (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3A015 Hardware Real-Time Clock Inoperative (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . 4A016 No Delayed Major Because System Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4A017 System Manager Link Connection Error <num>: <string> . . . . . . . . . . . . . . . . . . . . . 4A018 Invalid System Manager Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Minor Voice Processing Alarms (A020–A039) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5A020 Voice Mail Printer Off-Line (VPU/EM Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5A021 Voice Mail Unit 80% Full (VPU/EM Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5A022 Voice Mail Unit 100% Full (VPU/EM Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5A023 SMDR Unit 80% Full (VPU/EM Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6A024 SMDR Unit 100% Full (VPU/EM Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6A025 Voice Processing Unit <n>: <message>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6A026 Voice Processing Email Gateway is Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6A027 Voice Processing <app> Application Corrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6A028 Voice Processing Unit Out of Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7A030 <VoiceMailUnit> No Primary Language Prompts Installed . . . . . . . . . . . . . . . . . . . . . 7A031 <VoiceMailUnit> Hacker Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7A032 Extension <eeeee> Received Insufficient Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . 7

Major System Alarms (A100–A199) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8A100 Device <b.p.d> Extension <eeeee>: Reset Due to Excessive Data Errors . . . . . . . . 8A101 Device <b.p.d> Extension <eeeee>: Reset Due to Excessive Hardware Failures . . . 8A102 Serial Port <b.p.d>: Tx Interrupt is Not Operational (Axxess Only) . . . . . . . . . . . . . . 9A103 Serial Port <b.p.d>: Clock is Not Operational (Axxess Only) . . . . . . . . . . . . . . . . . . . 9A104 ALARM CPU: Database Corruption (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 9A105 CPU: Write-Protect is Not Operational (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . 10A106 CPU: Real-Time Clock is Not Operational (Axxess Only). . . . . . . . . . . . . . . . . . . . . 10A107 CPU: Watchdog is Not Operational (Axxess Only Pre v8.0). . . . . . . . . . . . . . . . . . . 10A108 CPU: Interval Timer is Intermittent (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 10A109 CPU: Watchdog Expired During Minor Reset (Axxess Only) . . . . . . . . . . . . . . . . . . 10A110 CPU: Database Feature Bundling Error (Axxess Only Pre v8.0) . . . . . . . . . . . . . . . 11A111 CPU: Battery Backed Memory Too Low (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 11

Rob Scott

Text

Rob Scott

Text

Contents

Page vi Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011

A112 CPU: Running Low on System Dynamic Memory (Heap) . . . . . . . . . . . . . . . . . . . . 12A114 <board_type> <card/bay> <port> in Red Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13A115 System History Frozen Due to a Software Exception. . . . . . . . . . . . . . . . . . . . . . . . 13A116 Database Battery Low (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13A117 Database Battery Jumper in Off Position (Axxess Only) . . . . . . . . . . . . . . . . . . . . . 13A118 Voice Mail Card Reset by OS (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13A119 Link to Secondary Cabinet Lost (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13A120 Static Memory Fault (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14A121 System History Frozen Due to a Freeze-On String . . . . . . . . . . . . . . . . . . . . . . . . . 14A122 Invalid or Missing Security Key – Audio Disabled. . . . . . . . . . . . . . . . . . . . . . . . . . . 14A123 PCMA <pcma> is Off-Line (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14A124 System Running on Backup Key: <xx> Hours Remaining (Axxess Only) . . . . . . . . 14A125 Invalid Software License: Reset in <xx> Minutes . . . . . . . . . . . . . . . . . . . . . . . . . . . 15A127 Unlicensed Device <ext> Failed to Come On-Line . . . . . . . . . . . . . . . . . . . . . . . . . . 15A128 <Extension>: User-Triggered Audio Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15A129 Unlicensed PRI Module <module> Port <port> Failed to

Come On-Line (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15A130 Unlicensed DEI Unit <unit> Failed to Come On-Line (5000 Only) . . . . . . . . . . . . . . 15A131 Voice Mail Ports Not Licensed (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15A132 Invalid or Missing License Key Information (5000 Only). . . . . . . . . . . . . . . . . . . . . . 16A133 License Key Recovery Attempt (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16A134 Channel Allocation Error on Board <number> Audio Session

<session> (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16A135 Channel IP Resource Campon Error (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 16A136 Automatic Diagnostics Delivery Transmission Failure . . . . . . . . . . . . . . . . . . . . . . . 16A137 Power Failure Detected – UPS Running on Battery (5000 Only) . . . . . . . . . . . . . . . 16A138 Unlicensed DT1 Module <module> Port <port> Failed to

Come On-Line (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17A139 Unlicensed DT1 Module <module> Port <port> Failed

to Allocate Echo Canceller (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17A140 Mismatch Between Database and Software License . . . . . . . . . . . . . . . . . . . . . . . . 17A141 No License for File-Based Audio <source>(5000 Only) . . . . . . . . . . . . . . . . . . . . . . 17A142 DEI #<number> Out of Voice Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17A143 Remote Configuration Failed <reason> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18A144 Ext <eeeee> SIP Registration Failure (5000 Only). . . . . . . . . . . . . . . . . . . . . . . . . . 18A145 Ext <eeeee> SIP Peer Out-of-Service (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . 18A146 Ext <eeeee> SIP Authentication Failure (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . 18A147 Ext <eeeee> SIP Peer License Error (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 19A148 System Exceeded PSTN Call Record (5000 Only). . . . . . . . . . . . . . . . . . . . . . . . . . 19

Major Voice Processing Alarms (A200–A224) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20A200 <VoiceMailUnit>: Hard Drive Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20A201 <VoiceMailUnit>: Channel Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20A202 <VoiceMailUnit>: Database Corruption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21A203 <VoiceMailUnit>: System Link Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21A204 <VoiceMailUnit>: Version Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Network Alarms (A225–A244) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Contents

Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page vii

System Application Alarms (A1001–A1099) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23A1001 DEI/DEM Failure (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23A1002 DEI Fan Failure (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23A1003 DDM-16 in Bay <b> Failed to Power Up Due to 3-DDM-16 Limit (5000 Only) . . . . 23A1004 DDM-16 in Bay <b> is not in a Compatible CS-5000 Chassis (5000 Only) . . . . . . 23A1007 MSP Alert <x> (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23A1008 DDM-16 in Bay <b> Failed to Power Up Due to an Unknown

Power Supply (5000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

System Messages (M0001–M9999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Operating System Startup Severe Messages (M0001–M0049) . . . . . . . . . . . . . . . . . . . . . . . . 24

M0001 CPU ROMs Failed Checksum – Bad or Not Present (Axxess Only Pre v8.0) . . . . 24M0002 CPU Dynamic RAM Not Present or Bad (Axxess Only Pre v8.0) . . . . . . . . . . . . . 24M0003 CPU Write-protected Database RAM Failure (Axxess Only Pre v8.0) . . . . . . . . . . 25M0004 CPU Interval Timer Failure (Axxess Only Pre v8.0) . . . . . . . . . . . . . . . . . . . . . . . . 25M0005 Task Initialization Table Error (Axxess Only Pre v8.0) . . . . . . . . . . . . . . . . . . . . . . 25M0006 Initialization Task Failure – Invalid OS Request (Axxess Only Pre v8.0) . . . . . . . . 25M0007 Exception Handler Task Failure – Invalid OS Request (Axxess Only Pre v8.0) . . 26M0008 CPU Interrupt Level 2 Stuck True (Axxess Only Pre v8.0). . . . . . . . . . . . . . . . . . . 26M0009 CPU Interrupt Level 3 Stuck True (Axxess Only Pre v8.0). . . . . . . . . . . . . . . . . . . 26M0010 CPU Interrupt Level 4 Stuck True (Axxess Only Pre v8.0). . . . . . . . . . . . . . . . . . . 26M0011 CPU Interrupt Level 5 Stuck True (Axxess Only Pre v8.0). . . . . . . . . . . . . . . . . . . 26M0012 OS Initialization Failure (Axxess Only Pre v8.0). . . . . . . . . . . . . . . . . . . . . . . . . . . 27M0013 CPU Interrupt Level 7 Stuck True (Axxess Only Pre v8.0). . . . . . . . . . . . . . . . . . . 27M0014 NCC Card Conflicts with CPU-020. Please Remove (Axxess Only) . . . . . . . . . . . 27

Operating System Startup Warning Messages (M0050–M0099) . . . . . . . . . . . . . . . . . . . . . . . 28M0050 Write-Protect Circuit Failure (Axxess Only Pre v8.0) . . . . . . . . . . . . . . . . . . . . . . . 28M0051 Real-Time Clock Inoperative (Axxess Only Pre v8.0) . . . . . . . . . . . . . . . . . . . . . . 28M0052 Real-Time Clock Stopped (Axxess Only Pre v8.0). . . . . . . . . . . . . . . . . . . . . . . . . 28M0053 WRN HW OS Real-Time Clock Needs Initialization (Axxess Only Pre v8.0) . . . . . 29M0054 WRN HW OS Watchdog Interrupt Inoperative (Axxess Only Pre v8.0) . . . . . . . . . 29

Database Informational Messages (M1000–M1999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30M1000 Off-Node Device ID <id> Automatically Created . . . . . . . . . . . . . . . . . . . . . . . . . . 30M1001 Network Time Synchronized by Node <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30M1002 Import of Device Info from Node <num> Started . . . . . . . . . . . . . . . . . . . . . . . . . . 30M1003 Import of Device Info from Node <num> Completed . . . . . . . . . . . . . . . . . . . . . . . 30M1004 Export of Device Info to Node <num> Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30M1005 Export of Device Info to Node <num> Completed . . . . . . . . . . . . . . . . . . . . . . . . . 31M1006 Removing Unused Off-Node Device ID <id> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31M1007 Automatically Created Node Route Group <ext>

for Node Number <node_number>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31M1008 New Node Route Group <ext>: <status> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31M1009 Station <id> Moved from <b.p.d> to <b.p.d> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31M1010 Node <num> Refused to Start a New Import Session – <reason> . . . . . . . . . . . . 32M1011 Delayed Major Reset <status>: <reason> <subreason> (Axxess Only) . . . . . . . . 32M1012 Software License Loaded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32M1013 CPU Type Change from <old> to <new> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Contents

Page viii Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011

M1014 DB Backup Rescheduled Due to Lock <lock_type>. . . . . . . . . . . . . . . . . . . . . . . . 33M1015 DB Backup Save: <status> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33M1016 DB Backup Restore: <status> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33M1017 Product Type Set to <product> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33M1018 Bypassing DB Backup Restore (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . 33M1019 New Node IP Connection Group: <ext>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34M1090 Using Default Voice Mail Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34M1091 Voice Processing Unit <error>: <message> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34M1092 <network group extension> Changing its Peer-to-Peer Value to <value> . . . . . . . 34M1093 IP Phone <id> Moved from Board <b1> to <b2> . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Hardware Informational Messages (M2000–M2999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36M2000 Board <brd> was Reset by IOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36M2001 Board <brd> (Card ID) <cid> Recovered from

Exception Processing (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36M2002 <b.p.d>: On-Line from <device>; <b.p.d>: Off-Line from <device> . . . . . . . . . . . . 36M2003 <b.p.d>: OMSCI Version <version> for <board> (Axxess Only) . . . . . . . . . . . . . . 36M2004 <text> from ASAI Device on Logical Port <log_port> (Axxess Only) . . . . . . . . . . . 37M2005 <b.p.d>: <message> from DSS/PKM <x> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37M2006 <b.p.d>: Power-Up from <device> <power-up-data>,

<major-version>, <minor-version> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37M2007 <b.p.d>: Power-Up from DSS <x>: Version = <v> . . . . . . . . . . . . . . . . . . . . . . . . . 37M2008 <action> from <client> Client on IP Port <port> . . . . . . . . . . . . . . . . . . . . . . . . . . . 38M2010 <b.p.d>: Redundant On-Line from DSS <x> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38M2011 <b.p.d>: On-Line from DSP <d>: BP = <bp>,

VSN = <v1>.<v2>, INFO = <info> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38M2012 <b.p.d>: Off-Line from DSP <d> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38M2013 <b.p.d>: Could Not <operation> Logical Port Ext <eeeee>

Reason: <why> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39M2014 <b.p.d>: Logical Port Ext <eeeee> <operation> (Axxess Only) . . . . . . . . . . . . . . . 39M2015 <b.p.d>: Could not <operation> I/O Channel (Axxess Only) . . . . . . . . . . . . . . . . . 39M2016 <b.p.d>: I/O Channel <operation> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . 39M2017 <b.p.d>: <type> Response Queue <operation> (Axxess Only) . . . . . . . . . . . . . . . 40M2018 <b.p.d>: <type> Response Queue Size <size> Bytes (Axxess Only) . . . . . . . . . . 40M2020 Loopback Test Timed Out on <board_type> <b.p.d> . . . . . . . . . . . . . . . . . . . . . . 40M2021 <b.p.d>: Downloading Latest Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . . 40M2022 <b.p.d>: Downloading Latest Firmware Version Completed

Successfully (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41M2023 <b.p.d>: Skipping Boot-Code Download (Axxess Only). . . . . . . . . . . . . . . . . . . . . 41M2024 <b.p.d>: Skipping Card-Specific Code Download (Axxess Only). . . . . . . . . . . . . . 41M2025 Card <card> Fully Busied Out (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41M2026 The Make-Busy Switch Timed Out on Card <card> (Axxess Only) . . . . . . . . . . . . 41M2027 <b.p.d>: Received Off-Line During Code Download (Axxess Only). . . . . . . . . . . . 42M2028 <b.p.d>: Initializing Board’s Companding Mode to <mode> . . . . . . . . . . . . . . . . . 42M2029 <address>: Device Busied Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42M2030 SLC16 48-Volt Power Supply Recovered on Board <board> (Axxess Only) . . . . . 42M2031 SLC16 72-Volt Power Supply Recovered on Board <board> (Axxess Only) . . . . . 42M2032 OS Info on <board_type> <b.p.d>, Additional Info: <data> (Axxess Only) . . . . . . 42

Contents

Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page ix

M2033 OS Version for CPU <cpu_number> is <version_string> (Axxess Only) . . . . . . . . 43M2034 On-Line from VoIP DSP(s) <numberstart>–<numberend> on Board <board> . . . 43M2035 Off-Line from VoIP DSP <numberstart>–<numberend> on Board <board> . . . . . 43M2036 Established IP LINK to Node <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44M2037 Closed IP LINK to Node <num> – Reason <reason> <string> . . . . . . . . . . . . . . . 44M2038 Failed Session Startup with Node <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44M2039 Dead Socket Response from Node <node_num>:

Reason <code>, <code_string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45M2040 CPC ‘*’ Button Pressed (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45M2041 CPC ‘*’ Button Acknowledged (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45M2042 Failed to Allocate a VoIP from Board <board>. . . . . . . . . . . . . . . . . . . . . . . . . . . . 45M2043 VoIP DSP <VoIP_DSP> on Board <board_num> is Unavailable Due to

Insufficient Networking VoIP from License (Axxess Only) . . . . . . . . . . . . . . . . . . . 46M2044 Session <session_id> is Closed Due to Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46M2045 <b.p.d>: <type> IP Address: <address> Hostname: <name> . . . . . . . . . . . . . . . . 46M2046 IP Connection <ext_received> Minor-Reset Notification

While Not On-Line (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47M2047 IP Connection <ext_received> Minor-Reset Notification (Axxess Only) . . . . . . . . 47M2048 Device <address> Unbusied Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47M2049 <ext>: Application Data and Control <conn> From <device>. . . . . . . . . . . . . . . . . 47M2050 Serial Input Queue Overflow – Character Ignored (Axxess Only) . . . . . . . . . . . . . 47M2094 CP Time Changed for Daylight Saving Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47M2095 <b.p.d>: Automatically Enabled Premium Feature: <feature>

(Axxess Only Pre v8.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48M2096 <b.p.d>: Automatic Equip of <board> Successful . . . . . . . . . . . . . . . . . . . . . . . . . 48M2097 System Reconfigure in Progress (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 48M2098 System Reconfigure Complete (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48M2099 <card> Real-Time Clock Stopped but Now Running (Axxess Only) . . . . . . . . . . . 49M2100 Timed-Out Waiting for a Ring Input on DI Circuit <b.p.d> . . . . . . . . . . . . . . . . . . . 49M2101 IPRC PAL Ignored on Board <board> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 49M2102 PIN Registration Successful For <new MAC address> on <extension> . . . . . . . . 49M2103 PIN Replacement Of <old MAC address> Successful for

<new MAC address> on <extension> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Engineering Informational Messages (M3000–M3999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

M3000 MAJOR RESET: Power-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50M3000 Minor Reset: Reset Button (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50M3000 Minor Reset: OS Detected Software Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50M3000 MAJOR RESET: OS Detected Software Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50M3000 MAJOR RESET: Watchdog Expired During OS MAJOR Reset Process. . . . . . . . 50M3000 MAJOR RESET: Watchdog Expired During OS Minor Reset Process . . . . . . . . . 51M3000 MAJOR RESET: Watchdog Expired During User Task MAJOR Reset Process . . 52M3000 MAJOR RESET: Watchdog Expired During User Task Minor

Reset Process (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52M3000 MAJOR RESET: User Task Detected Software Error . . . . . . . . . . . . . . . . . . . . . . 53M3000 Minor Reset: User Task Detected Software Error . . . . . . . . . . . . . . . . . . . . . . . . . 53M3000 MAJOR RESET: Delayed from Minor Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53M3000 MAJOR RESET: Delayed from System Reconfigure (Axxess Only) . . . . . . . . . . . 53

Contents

Page x Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011

M3000 MAJOR RESET: Delayed from Database Programming . . . . . . . . . . . . . . . . . . . . 53M3000 MAJOR RESET: Delayed from Heap Near Full . . . . . . . . . . . . . . . . . . . . . . . . . . . 54M3000 MAJOR RESET: Delayed from Heap Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . 54M3000 MAJOR RESET: Database Restore Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . 54M3000 MAJOR RESET: Database Programming Reset Command . . . . . . . . . . . . . . . . . 54M3000 MAJOR RESET: Database Programming Default Database Command . . . . . . . . 54M3000 MAJOR RESET: User Task Minor Initialization Failure (Axxess Only) . . . . . . . . . 54M3000 Minor Reset: Battery-Backed Memory Full (Axxess Only) . . . . . . . . . . . . . . . . . . . 55M3000 MAJOR RESET: Database Restore Connection Lost . . . . . . . . . . . . . . . . . . . . . . 55M3000 MAJOR RESET: Delayed from Resource Reconciliation. . . . . . . . . . . . . . . . . . . . 55M3000 MAJOR RESET: Delayed from Database Request . . . . . . . . . . . . . . . . . . . . . . . . 55M3000 MAJOR RESET: Major (or Minor) Reset Request

from Test Driver (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55M3000 Minor RESET: Other Cabinet Pressed Reset Button (Axxess Only) . . . . . . . . . . . 55M3000 MAJOR RESET: Other Cabinet Requested MAJOR Reset (Axxess Only) . . . . . . 55M3000 MAJOR RESET: Code Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56M3000 MAJOR RESET: Scheduled Delayed Major. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56M3000 MAJOR RESET: Low Battery on UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56M3000 MAJOR RESET: Reset Due to Change in Mindspeed ECAN Option . . . . . . . . . . 56M3001 System History of Node <frozen_node> <Frozen/UnFrozen>

from Node <freezing_node>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56M3002 System History of Node <frozen_node> <Frozen/UnFrozen>

by Ext <eeeee> at Node <freezing_node>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56M3003 System History <Freeze/UnFreeze> of Node <node_num>

Failed: Already <Frozen/UnFrozen> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57M3006 System in Use: Retrying Delayed Reset in 5 Minutes . . . . . . . . . . . . . . . . . . . . . . 57M3007 Call Processing Version: <version> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57M3008 <b.p.d>: Version Info for <board>: <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57M3009 Retrieving System History Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58M3010 <b.p.d>: Version Info for <board>: <data> (Axxess Only) . . . . . . . . . . . . . . . . . . . 58M3011 Automatic Diagnostics Delivery <status>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58M3012 CPH Compression Status: <status>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58M3050 BRI Trunk Port <b.p.d>: Registered SPID <spid> . . . . . . . . . . . . . . . . . . . . . . . . . 58M3051 Mailbox Resync <status> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58M3090 Input List Overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59M3091 Newer Code Image is Available (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 59M3092 Modem <modem> Reset by <device> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59M3093 Modem Connect – DSP <dsp>, Circuit <circuit>,

RX/TX Speed <rx>/<tx>, Mod <modulation> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59M3094 Modem Retrain – DSP <dsp>, Circuit <circuit>,

RX/TX Speed <rx>/<tx>, Mod <modulation> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59M3095 Modem Disconnect – DSP <dsp>, Circuit <circuit> . . . . . . . . . . . . . . . . . . . . . . . . 60M3096 Network Time Synchronization by Node <num> Ignored –

NTP Synchronization Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60M3100 Network Group Diagnostics Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60M3100 Network Group Diagnostics Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60M3101 Network Group Diagnostics has Detected Device <b.p.d> is Off-Line. . . . . . . . . . 60

Contents

Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page xi

M3102 Network Group Diagnostics Detected a Device Pair <b.p.d>and <b.p.d> Not Capable of Bidirectional Communication. . . . . . . . . . . . . . . . . . . 60

M3103 Network Group Diagnostics Detected a Firewall/NATBetween Device Pair <b.p.d> and <b.p.d>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

M3104 Network Group Diagnostics Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61M3105 Feature Disabled for Peer-to-Peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61M3106 Received Handshake from Remote Node <node> but Could Not Find Session

<session_id> or Off-Node IP Connection <connection> . . . . . . . . . . . . . . . . . . . . 61M3107 Received Last Handshaking but Could Not Find Session ID <session_id> . . . . . . 61M3108 Received Last Handshaking but Remote Node <node> Rejected IP Link . . . . . . . 61M3109 Device <device> Ext <eeeee> did Not Receive Release ACK

for TI Call ID <id> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62M3110 No More Data Connections for Board <board number>. . . . . . . . . . . . . . . . . . . . . 62M3111 Licence Manager <info>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62M3200 Periodic Database Diagnostics Options: <db_field> . . . . . . . . . . . . . . . . . . . . . . . 62M3201 Periodic Database Diagnostics: <details> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63M3250 Periodic Resource Diagnostics Options: <db_field> . . . . . . . . . . . . . . . . . . . . . . . 63M3251 Periodic Resource Diagnostics: <details> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63M3252 System Manager Requested Node Name Change to: <text> . . . . . . . . . . . . . . . . 63M3253 Call Processing Successfully Connected to System Manager. . . . . . . . . . . . . . . . 63M3254 Call Processing is Trying to Connect to System Manager

<username>@<ip_address>:<port_number> . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63M3255 <text> System Manager Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63M3256 Call Processing Received Unknown System Manager Event: <text> . . . . . . . . . . 64M3257 Call Processing Disconnected from System Manager <error code> . . . . . . . . . . . 64M3258 System Manager SSL Error: <text> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64M3259 Node <node> Enabled Mode <mode> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64M3500 <text> from ASAI Device on IP Address <xxx.xxx.xxx.xxx>. . . . . . . . . . . . . . . . . . 64M3501 <text> Socket Thread Started from IP Address <xxx.xxx.xxx.xxx> . . . . . . . . . . . . 64M3502 <text> Socket Thread Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64M3503 SYSOAI CMD: <text>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65M3504 Port <port>: SYSOAI CMD: <text>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65M3505 TCP <xxx.xxx.xxx.xxx>: SYSOAI CMD: <text> . . . . . . . . . . . . . . . . . . . . . . . . . . . 65M3506 Fax Tone Detected Fax Call Initiated: <board xx>,

<session xx>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65M3507 Retrieving Device File Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65M3508 NTP Synchronization Successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65M3509 Network Date/Time Changed by Node <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . 66M3510 Set Date/Time Feature Code Entered by Ext <eeeee> . . . . . . . . . . . . . . . . . . . . . 66M3511 Set Network Date/Time Feature Code Entered by Ext <eeeee> . . . . . . . . . . . . . . 66M3512 Synchronize Network Time Feature Code Entered by Ext <eeeee> . . . . . . . . . . . 66M3513 UPS Status <text> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66M3514 Request Remote Node <number> Span Connection Type

by <ntg> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66M3515 Received Remote Node <number> Span Connection Type

<type> Response by <ntg> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67M3516 <ntg> Remote Node <number> Span Connection Type has

Changed from <text1> to <text2>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Contents

Page xii Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011

M3517 <ntg> Remote Node <number> Span Connection Type to<text> Due to Older System Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

M3518 DSP <number1> on Module <number2> Forced Offline Due to 4-DEI Mode . . . . 67M3519 Remote Configuration Connection: <status> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68M3520 File-Based MOH Status: <status> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68M3521 Door Relay Activated By Ext. <eeeee> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Database Warning Messages (M4000–M4999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69M4000 <table>: No Match with Table for <object>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69M4001 Too Many Call Routing Tables Chained Together <limit> . . . . . . . . . . . . . . . . . . . 69M4002 Processed Invalid Call Routing Table Number <number> . . . . . . . . . . . . . . . . . . . 69M4003 Invalid Associated Extension <eeeee> in SMDR Message . . . . . . . . . . . . . . . . . . 69M4004 Invalid Extension <bad_ext> Removed from Extension List <ext_list> . . . . . . . . . 70M4005 Invalid ACD Agent ID <bad_ext> Removed from Extension List <ext_list>. . . . . . 70M4006 <prem_feat> Premium Feature Disabled on Node <number>

(Axxess Only Pre v8.0). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70M4007 Change of Off-Node Extension <ext> to <bad_ext> Failed Due to Conflict . . . . . . 70M4008 Remote Equip/Unequip/Update of Off-Node Ext <ext>

Prevented Due to <reason> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71M4009 Device Info Import for <ext> Failed: <reason>. . . . . . . . . . . . . . . . . . . . . . . . . . . . 71M4010 Remote Equip of Off-Node Device <ext1> Failed: Conflict with <ext2>. . . . . . . . . 71M4011 Another Node does Not Know About Node <number> . . . . . . . . . . . . . . . . . . . . . 71M4012 BRI Trunk Port <b.p.d> does Not have Any SPIDS Programmed . . . . . . . . . . . . . 72M4013 BRI Trunk Port<b.p.d> has an Invalid SPID <spid>. . . . . . . . . . . . . . . . . . . . . . . . 72M4014 ISDN Data Call Rejected on Trunk Group or Node Trunk Group <ext>. . . . . . . . . 72M4015 Node <number1> does Not Know About Node <number2> . . . . . . . . . . . . . . . . . 72M4016 <ext1> is Overriding Emergency Outgoing Access for <ext2>. . . . . . . . . . . . . . . . 73M4017 Invalid Software License Loaded: <reason> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73M4018 Invalid IP Connection ID detected: <id>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73M4019 <ext1> Does Not Have <str> Outgoing Access on Trunk

Group or Node Trunk Group or IP Connection <ext2>. . . . . . . . . . . . . . . . . . . . . . 73M4020 Invalid Extension Dialed on SIP Peer: <ext1> from

SIP Device: <ext2> Dialed Number: <str> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Hardware Warning Messages (M5000–M5999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

M5000 <brd_type> <slot_#>: DSP/8051 Version Number Conflict: 8051 Ver = <version>, DSP Ver = <dsp_ver> (Axxess Only). . . . . . . . . . . . . . . . . 74

M5001 <brd_type> <slot_#>: Invalid Highway or TimeslotSpecified: HWY = <highway>, TS = <timeslot> (Axxess Only) . . . . . . . . . . . . . . . 74

M5002 <brd_type> <slot_#>: DSP to Dual-Port RAM State Error forDSP <d>: State = <state> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

M5003 <brd_type> <slot_#>: OPC-to-DSP Command Error for DSP<x>: Command = <command> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

M5004 <brd_type> <slot_#>: DSP Illegal Response for DSP <d>:Response = <response> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

M5005 <brd_type> <slot_#>: DSP Response Size Error for DSP<number>: Size = <size> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

M5006 <brd_type> <slot_#>: Unexpected DSP Reset for DSP<number> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Contents

Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page xiii

M5007 <brd_type> <slot_#>: Unexpected DSP On-Line for DSP <number>: Boot-Page = <page> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 76

M5008 <brd_type> <slot_#>: Boot-Page Mismatch for DSP <number>: Boot-Page = <page> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 76

M5009 <brd_type> <slot_#>: <num> RS-232 Frame Errors (Axxess Only) . . . . . . . . . . . 77M5010 <brd_type> <slot_#>: RS-232 Receive Data Lost (Axxess Only) . . . . . . . . . . . . . 77M5011 <brd_type> <slot_#>: CPU Command Size Error:

Size = <number> (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77M5012 <brd_type> <slot_#>: DSP Response Data Error for

DSP <dsp>: Data = <byte> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77M5013 <brd_type> <slot_#>: DSP Window Time-Out Error for

DSP <dsp> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78M5014 <brd_type> <slot_#>: DSP Boot Time-Out Error for

DSP <dsp> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78M5015 <brd_type> <slot_#>: Caller ID Connect When Not Ready for Caller ID <rr> . . . . 78M5016 <brd_type> <slot_#>: RS-232 Transmit Data Lost (Axxess Only) . . . . . . . . . . . . . 78M5017 DSS Error for DSS <number> <b.p.d>: <s-Side> Frame Error . . . . . . . . . . . . . . . 79M5018 DSS Error for DSS <number> <b.p.d>: Command Inconsistency Error . . . . . . . . 79M5019 DSS Error for DSS <number> <b.p.d>: Data Lost Error . . . . . . . . . . . . . . . . . . . . 79M5020 <b.p.d>: Caller ID Terminated Due to Connect Timer Expired. . . . . . . . . . . . . . . . 80M5021 <b.p.d>: Caller ID Terminated Due to Data Timer Expired . . . . . . . . . . . . . . . . . . 80M5022 <b.p.d>: Caller ID Terminated Due to Carrier Lost. . . . . . . . . . . . . . . . . . . . . . . . . 80M5023 <b.p.d>: Caller ID Terminated Due to Frame Error . . . . . . . . . . . . . . . . . . . . . . . . 80M5024 <b.p.d>: Caller ID Terminated Due to Break Detected. . . . . . . . . . . . . . . . . . . . . . 80M5025 <eeeee>: Hardware Off-Line for Serial Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80M5028 High Ring Line Error for <b.p.d> End High Ring Line Error for <b.p.d> . . . . . . . . . 81M5029 Invalid CO Line State Error for <b.p.d>: State = <xx> . . . . . . . . . . . . . . . . . . . . . . 81M5030 <b.p.d>: Version Not Supported = <x> <phone> . . . . . . . . . . . . . . . . . . . . . . . . . . 82M5031 <b.p.d>: Version Not Supported = <v> (DSS <x>). . . . . . . . . . . . . . . . . . . . . . . . . 82M5032 <b.p.d>: Input from Off-Line <device>: <msg>. . . . . . . . . . . . . . . . . . . . . . . . . . . . 82M5033 <b.p.d>: Input from Off-Line <board>: <msg> . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82M5034 <b.p.d>: Input from Off-Line DSS <x>: <msg>. . . . . . . . . . . . . . . . . . . . . . . . . . . . 82M5035 <b.p.d>: Input from Unequipped <device>: <msg> . . . . . . . . . . . . . . . . . . . . . . . . 83M5036 <b.p.d>: Invalid Power-Up from <device> <power-up-data>,

<major-version>, <minor-version> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83M5037 Audio Path Blocking: <path-owner> Already Using Path <x> of <b.p.d> . . . . . . . . 83M5038 Audio Path: Invalid Requesting Device <b.p.d>. . . . . . . . . . . . . . . . . . . . . . . . . . . 83M5039 <b.p.d> <board1>: Incompatible DB Type = <board2> . . . . . . . . . . . . . . . . . . . . . 84M5040 <b.p.d> <board1>: Ignored DB Type = <board2> . . . . . . . . . . . . . . . . . . . . . . . . . 84M5041 <b.p.d> <board>: Input for Non-Existent DTMF Receiver: <msg>. . . . . . . . . . . . . 84M5042 <b.p.d> <board>: Input for Non-Allocated DTMF Receiver: <msg>. . . . . . . . . . . . 85M5043 <b.p.d> <board>: Input for Non-Existent Caller ID Receiver: <msg>. . . . . . . . . . . 85M5044 <b.p.d> <board>: Input for Non-Allocated Caller ID Receiver: <msg>. . . . . . . . . . 85M5045 DSS <x> <b.p.d>: Off-Line Ignored DSS is Off-Line . . . . . . . . . . . . . . . . . . . . . . . 86M5048 <b.p.d>: Invalid Board Type <board-type> for Hardware System . . . . . . . . . . . . . 86M5049 <b.p.d>: Invalid Port Type <port-type> for <board> . . . . . . . . . . . . . . . . . . . . . . . . 86M5052 <b.p.d>: Null Hardware Address in Message for <board> . . . . . . . . . . . . . . . . . . . 87

Contents

Page xiv Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011

M5054 <b.p.d>: Invalid On-Line Data for DSP <dsp-num>: BP = <page>, VSN = <v1>.<v2>, INFO = <dsp-info> . . . . . . . . . . . . . . . . . . . . . . 87

M5055 <b.p.d>: SL Adapter Plugged Into Keyset Device Ignored. . . . . . . . . . . . . . . . . . . 87M5056 <b.p.d>: Keyset Device Plugged into SL Adapter Ignored. . . . . . . . . . . . . . . . . . . 87M5057 <b.p.d>: DSP Watchdog Error from <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87M5058 <b.p.d>: Internal DSP Firmware Error from <name> . . . . . . . . . . . . . . . . . . . . . . . 88M5059 <b.p.d>: DSP Write Protect Violation from <name>. . . . . . . . . . . . . . . . . . . . . . . . 88M5060 <b.p.d>: DSP Static Variable Check Violation from <name> . . . . . . . . . . . . . . . . . 88M5061 <b.p.d>: DSP Invalid Command from Microcontroller from <name> . . . . . . . . . . . 88M5062 <b.p.d>: Inconsistency Error from <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88M5063 <b.p.d>: Output Queue Overflow Error from <name> . . . . . . . . . . . . . . . . . . . . . . 89M5064 <b.p.d>: Soft Error from <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89M5065 <b.p.d>: DSP Receive Buffer Empty Error from <name>. . . . . . . . . . . . . . . . . . . . 89M5066 <b.p.d>: DSP Transmit Buffer Full Error from <name> . . . . . . . . . . . . . . . . . . . . . 89M5067 <b.p.d>: Layer 2 Communications Errors from <name> . . . . . . . . . . . . . . . . . . . . 90M5068 <b.p.d>: Device Reset Due to Excessive Layer 2 Comm

Errors from <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91M5069 <b.p.d>: Device Lockout Due to Excessive Layer 2 Comm

Errors from <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91M5070 <b.p.d>: Excessive Data Errors from <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91M5071 <b.p.d> Port Reset Due to Excessive Data Errors from <name>. . . . . . . . . . . . . . 92M5072 <b.p.d> Port Lockout Due to Excessive Data Errors from <name> . . . . . . . . . . . . 92M5075 <b.p.d> Unexpected <string> Input from RS-232 Port (Axxess Only) . . . . . . . . . . 92M5076 <b.p.d> Ignoring Input from Unequipped MDPM: <msg> . . . . . . . . . . . . . . . . . . . 92M5077 <b.p.d> DSP Invalid Coefficient ID from <name> . . . . . . . . . . . . . . . . . . . . . . . . . 93M5078 <b.p.d> DSP Real-Time Shortage for <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . 93M5079 <b.p.d> RAM Sanity Check Error for <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93M5080 <b.p.d> LCD RAM Sanity Check Error for <name> . . . . . . . . . . . . . . . . . . . . . . . . 93M5081 <b.p.d> LCD Wait Ready Error for <name>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93M5082 <name> Once Allocated by <b.p.d> No Longer In Use – Making Available . . . . . 94M5083 <b.p.d> PP Device State Error for <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94M5084 <b.p.d> DID Ready-Timeout Sync Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94M5085 <b.p.d> Trunk Ready Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94M5086 <time> Threshold for <threshold> Errors Exceed on <board_type> <b.p.d>. . . . . 95M5087 OS Error on <board_type> <b.p.d>, Additional Info: <data> . . . . . . . . . . . . . . . . . 95M5088 <b.p.d> Outgoing E&M Call was Blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95M5089 <b.p.d> Caller ID Receiver Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96M5090 Rhetorex Driver Function <driver-func> Failed on

Channel <chan-num>: Result = <func-result> (VPU/EM Only) . . . . . . . . . . . . . . . 96M5091 <b.p.d> <board>: Input for Non-Existent Speakerphone: <msg> . . . . . . . . . . . . . 96M5092 <b.p.d> <board>: Input for Non-Allocated Speakerphone: <msg> . . . . . . . . . . . . 97M5093 <b.p.d> <item> RS-232 Response Queue Blocked

(<num> Tries) (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97M5094 <b.p.d> <item> RS-232 Response Queue Overflow

<num> Bytes (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97M5095 <b.p.d>: Timed-Out Waiting for CO Service Information . . . . . . . . . . . . . . . . . . . . 98M5096 <b.p.d>: Unable to Dedicate Voice Channel. None are Available for Use . . . . . . . 98M5097 <b.p.d>: Unable to Dedicate Voice Channel. Resource Failure. . . . . . . . . . . . . . . 99

Contents

Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page xv

M5098 <b.p.d>: Online Ignored for <type> DSS/PKM unit <limit: [limit]> . . . . . . . . . . . . . 99M5099 <card>: Real-Time Clock is Stopped (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 100M5100 <b.p.d>: Communications Error from <name> (Axxess Only) . . . . . . . . . . . . . . . 100M5101 <b.p.d>: Error Message Lost for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . 100M5102 <b.p.d>: Incorrect Interrupt Mask for <name> (Axxess Only) . . . . . . . . . . . . . . . 100M5103 <b.p.d>: No Response Error from <name> (Axxess Only). . . . . . . . . . . . . . . . . . 100M5104 <b.p.d>: OMSCI Error Code from <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101M5105 <b.p.d>: Spurious Reset for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 101M5106 <b.p.d>: State Error for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 101M5107 <b.p.d>: SWI Error from <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . 101M5108 <b.p.d>: Transmit Data Register Empty for <name> (Axxess Only) . . . . . . . . . . 101M5109 <b.p.d>: Timer Error for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . 101M5110 <b.p.d>: Transmission Error from <name> (Axxess Only) . . . . . . . . . . . . . . . . . . 102M5111 <b.p.d>: Trap Error for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 102M5112 <b.p.d>: Spurious Reset for <name> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . 102M5113 <b.p.d>: <name> Received Ground Start Programming (Axxess Only) . . . . . . . 102M5114 <b.p.d>: Reconfigure Request from <name> (Axxess Only) . . . . . . . . . . . . . . . . 102M5115 PP Command Sent After <num> Tries (Axxess Only) . . . . . . . . . . . . . . . . . . . . . 103M5116 <b.p.d>: (RMGR) Invalid PP Response: Type = <xx>,

Board = <bb>, Circuit = <cc>, MSG = <zz> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103M5117 <b.p.d>: (RMGR) Dialing Time-Out Error for <b.p.d> . . . . . . . . . . . . . . . . . . . . . 103M5118 <b.p.d>: (RMGR) DSP <x> Status Error = <error> . . . . . . . . . . . . . . . . . . . . . . . 103M5119 <side>: Fiber-Optic Local Error Count too High;

Rate = <rate> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104M5121 <side>: Fiber-Optic Remote Error Count too High;

Rate = <rate> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104M5122 Nodes did Not Respond to Broadcast Message from

Ext <eeeee>: Nodes <node_list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104M5123 <b.p.d> <board>: Incompatible ISDN FW Version = <ver1> (Expecting <ver2>)

(Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104M5124 <b.p.d> <board>: Incompatible FW Version = <ver1>

Expecting <ver2> or Higher (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105M5125 Received Call on Unequipped Trunk <b.p.d> . . . . . . . . . . . . . . . . . . . . . . . . . . . 105M5126 <b.p.d> Jumper Prevents Boot-Code Upgrade (Axxess Only). . . . . . . . . . . . . . . 105M5128 <b.p.d> Board is Out of Sync with Download Task (Axxess Only). . . . . . . . . . . . 105M5129 <b.p.d> Missing Jumper Protection for Card's Boot Sector (Axxess Only) . . . . . 106M5130 <b.p.d>: Must Remove BBPC for Normal Operation (Axxess Only) . . . . . . . . . . 106M5131 <b.p.d>: Boot Code Image is Empty (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . 106M5132 <b.p.d>: Name Code Image is Empty (Axxess Only). . . . . . . . . . . . . . . . . . . . . . 106M5133 <time>: Threshold for <threshold> Errors Exceed on BRI Port <b.p.d>. . . . . . . . 106M5134 OS Version Mismatch: Version Should be at

Least <version_string> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107M5135 <b.p.d>: (RMGR) Invalid DSP Command: Size = <xx>, Command = <zz> . . . . . 107M5136 <b.p.d>: Caller ID Transmitter Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107M5137 <b.p.d>: IP SoftPhone Programmed as an IP Keyset Device is Ignored . . . . . . . 107M5138 (RMGR) DSP Dialing Timeout Error for <b.p.d> . . . . . . . . . . . . . . . . . . . . . . . . . 108

Contents

Page xvi Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011

M5139 (RMGR) DSP Digit Queue Full Error for <b.p.d> . . . . . . . . . . . . . . . . . . . . . . . . . 108M5140 IP Phone With MAC <MAC address> Locked Out Due to

Failed PIN Attempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Engineering Warning Messages (M6000–M6999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

M6000 Invalid Reset Response Board <board>: DPR-WStat = <status>, IOC-State = <ioc_state> (Axxess Only) . . . . . . . . . . . . . 109

M6001 Reset Error Found by Board <board>: IOC-State = <ioc_state> . . . . . . . . . . . . . 109M6002 Power-Up Board <board> Not in Reset State:

PP-State = <pp_state>, IOC-State = <ioc_state>. . . . . . . . . . . . . . . . . . . . . . . . . 110M6003 Power-Up Invalid Board = <board>:

Board ID = <brd_id>, IOC-State = <ioc_state> . . . . . . . . . . . . . . . . . . . . . . . . . . 110M6004 Illegal Configure State = <ioc-substate>: In-Prog Flag = <config-flag> . . . . . . . . 111M6005 Board <board> Not Operational after Power-Up:

PP-State = <pp-state>, IOC-State = <ioc-state> . . . . . . . . . . . . . . . . . . . . . . . . . 111M6006 Board <board> Not Responding:

IOC-State = <ioc-state>, Sub-State = <ioc-substate> . . . . . . . . . . . . . . . . . . . . . 112M6007 Illegal Exception State = <ioc-substate>: In-Prog Flag = <exception-flag> . . . . . 112M6008 Board <board> Not Responding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112M6009 Time-Out Awaiting Minor Init ACK: Board = <board>,

IOC-State = <ioc-state>) (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113M6010 DPR Window Control ACK Invalid Window Status:

Board = <board>, IOC-State = <ioc-state>, Status = <status>, PP-State = <pp-state> (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

M6011 DPR Receive Queue Error: Board = <board> IOC-State = <ioc-state>, Status = <status> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

M6012 DPR Window Control ACK Invalid DPR Status: Board = <board>, IOC-State = <ioc-state>, Status = <status>, PP-State = <pp-state> (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

M6013 Received DPR Interrupt in Invalid State: IOC-State = <ioc-state> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

M6014 Board <board> Not in PPCB List: PPCB-List-Field = <ppcb> . . . . . . . . . . . . . . . 114M6015 Board <board> Not Found in PPCB List <ppcb> . . . . . . . . . . . . . . . . . . . . . . . . . 115M6016 Illegal MAJOR State (<major-substate>) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115M6017 Time-Out Awaiting MAJOR Init ACK: Board <board> (Axxess Only). . . . . . . . . . 115M6018 Illegal Minor State <minor-substate> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115M6019 NULL Queue Deallocate Attempt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115M6020 Input Queue Illegal Msg Length = <length>: 1st-Byte = <byte>. . . . . . . . . . . . . . 116M6021 Input Queue Illegal Device Type: Msg Length = <length>,

Device-Type = <type>, 2nd-Byte = <byte>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116M6022 Input Queue Illegal Command: Msg Length = <length>,

Device-Type = <type>, Command = <command> . . . . . . . . . . . . . . . . . . . . . . . . 116M6023 Input Queue Illegal Board = <board>: Device Type = <type>,

Command = <command>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117M6024 Board <board> Unexpected State: IOC-State = <ioc-state>,

PP-State = <pp-state> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117M6025 Board <board> Message with Invalid Length <length> (Axxess Only). . . . . . . . . 117M6026 SEND – Invalid Board Address <board> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118M6027 DKSC Illegal Message Length <length> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Contents

Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page xvii

M6028 DKSC Illegal Port: Board = <board> MsgLength = <length>Command = <command> Port = <port>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

M6029 DPR Window Control ACK Time-Out: Board = <board>,Status = <status>, PP-State = <pp-state> (Axxess Only). . . . . . . . . . . . . . . . . . . 119

M6030 Timer Interrupt in Invalid State <ioc-state> (Axxess Only) . . . . . . . . . . . . . . . . . . 119M6031 Interrupt Timer with Invalid Time-Out ID <timer_ID> . . . . . . . . . . . . . . . . . . . . . . 119M6032 Processed Packet to UnInitialized DKSC Port = <b.p.d>:

Queue-Type = <type>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119M6033 DKSC Illegal Command: Board = <board>

Msg Length = <length> Command = <command> . . . . . . . . . . . . . . . . . . . . . . . . 120M6034 IOC Timed-Out Waiting for DSP <dsp> to Reset (Axxent Only) . . . . . . . . . . . . . 120M6035 DSP <number> Not Responding (Axxent Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 120M6036 DSP DPR Window Control ACK Time-Out:

DSP = <number> Status = <status> (Axxent Only) . . . . . . . . . . . . . . . . . . . . . . . 120M6037 Not Compatible SW Version in Board <board> (Axxess Only) . . . . . . . . . . . . . . 120M6038 Fiber Error Class (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121M6046 Board <board> Reset Itself – <status>:

IOC-State = <ioc-state>, PP-State = <pp-state> (Axxess Only). . . . . . . . . . . . . . 121M6047 Serial Port <b.p.d> Lost at Least One Outgoing Message (Axxess Only) . . . . . . 121M6050 OS Request <request>: Unexpected Status <status> . . . . . . . . . . . . . . . . . . . . . 122M6051 <routine>: OS Request <request>: Queue Full Status Returned. . . . . . . . . . . . . 122M6052 OS Request <request>: Clock Failure Status Returned. . . . . . . . . . . . . . . . . . . . 122M6053 OS Request <request>: Invalid Delay <delay> (Axxess Only). . . . . . . . . . . . . . . 123M6054 OS Request <request>: Invalid Task ID <task-id> (Axxess Only) . . . . . . . . . . . . 123M6055 OS Request <request>: Attempted to Abort

Non-Preemptable Task <task-id> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . 123M6056 OS Request <request>: Invalid Message Length <length> (Axxess Only) . . . . . 123M6057 OS Request <request>: Invalid Board Number <b.p.d> (Axxess Only) . . . . . . . . 124M6058 OS Request <request>: Invalid Port Number <b.p.d> (Axxess Only) . . . . . . . . . 124M6059 OS Request <request>: Timer for Task <task-id>

Not Found <byte_list> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124M6060 OS Request <request> for <b.p.d>: Port Already Allocated (Axxess Only) . . . . . 124M6061 OS Request <request> for <b.p.d>:

Maximum Ports Already Allocated (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . 125M6062 OS Request <request> for <b.p.d>: Port Off-Line (Axxess Only) . . . . . . . . . . . . 125M6064 OS Request <request> Logical Port <port>: Port Unavailable (Axxess Only) . . . 125M6065 OS Request <request> for Logical Port <port>:

Port Not Allocated (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125M6066 OS Request <request> for Logical Port <port>:

Incompatible Protocol <value> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 126M6067 OS Request <request>: Invalid Use of Preemptable

Request by Task <task-id> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126M6068 OS Request <request>: Invalid Time Buffer <buffer> . . . . . . . . . . . . . . . . . . . . . 126M6069 OS Request <request>: Invalid Date Buffer <buffer>. . . . . . . . . . . . . . . . . . . . . . 126M6070 System History of Node <frozen_node> Automatically

Frozen Due to Software Exception (Axxess Only Pre v8.2) . . . . . . . . . . . . . . . . . 127M6071 System History of Node <frozen_node>

Automatically Frozen Due to Freeze-On String . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Contents

Page xviii Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011

M6072 Automatic System History Freeze of Node <node_num>Failed: Already Frozen (Axxess Only Pre v8.2) . . . . . . . . . . . . . . . . . . . . . . . . . . 127

M6073 <b.p.d> Automatic Equip of <board> Failed: <reason> . . . . . . . . . . . . . . . . . . . . 127M6074 Invalid Digit String <invalid length> with Max Length <max length> . . . . . . . . . . 128M6080 <routine>: Null Pointer Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128M6081 Extra Timer for Task <task-id>: <timer>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128M6082 Unrecognized Timer for Task <task-id>: <timer> . . . . . . . . . . . . . . . . . . . . . . . . . 128M6083 Unexpected Message for Task <task-id>: <msg> . . . . . . . . . . . . . . . . . . . . . . . . 128M6084 Unrecognized Message for Task <task-id>: <msg>. . . . . . . . . . . . . . . . . . . . . . . 129M6085 <b.p.d> On-Line Ignored for PRI Board,

Check Advanced CO Interfaces (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 129M6090 DOS Operation <op> Failed: File = <file>, Access = <type>,

Handle = <handle>, Result = <result> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129M6091 Invalid Event in State <state>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129M6092 Attempt to Reference Nonexistent Mailbox <mailbox> . . . . . . . . . . . . . . . . . . . . 130M6093 Attempt to Request Operation from Null Audio Port . . . . . . . . . . . . . . . . . . . . . . 130M6094 HW System Out of Sync for <b.p.d> Ext <eeeee>. . . . . . . . . . . . . . . . . . . . . . . . 130M6095 <Voice_Mail_Unit>: Minor Version Mismatch. . . . . . . . . . . . . . . . . . . . . . . . . . . . 130M6096 CP Timed Out Trying to Setup Call to ASAI Device. . . . . . . . . . . . . . . . . . . . . . . 130M6097 Exception Log Index Error – Reset to First Record . . . . . . . . . . . . . . . . . . . . . . . 131M6098 Exception Log Record Checksum Failure – Record Cleared at <address>. . . . . 131M6099 Corrupted Queue was Cleared: <queue_name> . . . . . . . . . . . . . . . . . . . . . . . . . 132M6100 CPU with MAC Address <macaddr> Does Not have

ATM Only PAL (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132M6101 Message System Version <version> Not Compatible Upgrade Node <node> . . 132M6102 Extension List Failure <reason>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132M6103 Exceeded Max Number of Off-Node Devices: Failed to Create <id>. . . . . . . . . . 133M6104 Generic Resource Failure <reason>: Data = <data> (Axxess Only) . . . . . . . . . . 133M6105 On-Line Failure Board <board> – Single Cabinet System (Axxess Only) . . . . . . 133M6106 Message Print Queue Copy Allocation Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . 133M6107 Datagram Message Cannot be Routed: <msg_name> . . . . . . . . . . . . . . . . . . . . 133M6108 No Node Route Group Programmed for Node <node> . . . . . . . . . . . . . . . . . . . . 133M6109 Record-A-Call Cannot Record Agent Helper or Supervisor . . . . . . . . . . . . . . . . . 134M6110 Unable to Reserve Data Connection IP Port: <port_id> for

Device: <device_id> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134M6111 Unable to Reserve Data Connection IP Port: <port_id> for

Device: <device_id> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134M6112 Buffer Overrun . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134M6113 Manager Node Change Request Failed Due to <text> . . . . . . . . . . . . . . . . . . . . 135M6114 Fax Call Failure Due to Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135M6115 Networking Call Failure Due to Insufficient Networking VoIPs from License . . . . 135M6116 <ext>: Auto-NAT Detection Failed – <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . 135M6117 NTP Synchronization Failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135M6118 <Station eeee> and <IP Connection eeee> have Same IP Address –

May Interfere with Auto-NAT Detection Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136M6119 <eeee>: Auto-NAT Detection Result is Not Confirmed . . . . . . . . . . . . . . . . . . . . 136M6120 Failed to Allocate VoIP Resource for Ext <eeeee> <string> . . . . . . . . . . . . . . . . 136M6121 Cannot Monitor Heap (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Contents

Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page xix

M6122 Exceeded Max Number of Agent IDs: Failed to Create <id> . . . . . . . . . . . . . . . . 137M6123 Conference Break Up Failed for <eeee>

Due to No Remaining VoIPs Conference Parties Disconnected . . . . . . . . . . . . . 137M6124 <s1> Module <N1> Port <N2> <s2> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137M6125 Device <ext> Failed to Find the Other Device <ext1> System

Echo Canceller Configuration Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137M6126 <eeee>: Audio Receive Port Changed From <old_port> to <new_port> . . . . . . . 138M6127 Generic SIP Error Message <s> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138M6128 <s1> File-Based Audio Source <N1> <s2> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138M6129 Module <number1> in DEI <number2> Failed to Come

Online: Not in Quad-DEI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138M6130 File-Based Audio Source <N1> - <s1>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138M6131 HTML Application File Not Found: Profile <number> File <filename> . . . . . . . . . 139M6132 <eeee>: HTML Application <app> Not Found for Language <lang> . . . . . . . . . . 139M6133 <eeee>: HTML Application <app> Not Found for Device Type <device> . . . . . . 139

Database Severe Error Messages (M7000–M7999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140M7000 Battery-Backed Memory Full for Equip of <object> <b.p.d>. . . . . . . . . . . . . . . . . 140M7001 Database Defaulted Due to OS Indicates Battery-Backed

Memory Corruption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140M7001 Database Defaulted Due to Internal Database Pointer is Invalid . . . . . . . . . . . . . 140M7001 Database Defaulted Due to Forced Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141M7001 Database Defaulted Due to CODE Change: Last Function Relocated . . . . . . . . 141M7001 Database Defaulted Due to CODE Change: Last CODE Table Relocated . . . . . 141M7002 Battery-Backed Memory Full for Extension List Addition <ext> . . . . . . . . . . . . . . 142M7003 Database Out-of-Synch: Record <id>, Sequence <seq>,

Bit <bit>, Max Bit <maxbit>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142M7004 Database Compression/Decompression Error. . . . . . . . . . . . . . . . . . . . . . . . . . . 142M7005 Another Node does Not Know About Node <number> . . . . . . . . . . . . . . . . . . . . 143M7006 Node <number1> does Not Know About Node <number2>. . . . . . . . . . . . . . . . . 143M7007 Invalid Software License – Reset in <xx> Minutes. . . . . . . . . . . . . . . . . . . . . . . . 143

Hardware Severe Error Messages (M8000–M8999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144M8000 <string> Condition Detected on <board_type> <b.p.d> . . . . . . . . . . . . . . . . . . . . 144M8001 <board_type> Problem: <type> (North America) . . . . . . . . . . . . . . . . . . . . . . . . . 144M8001 <board_type> Problem: <type> (Europe). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145M8002 <string> Condition Cleared on <board_type> <b.p.d> . . . . . . . . . . . . . . . . . . . . . 146M8003 All Calls on <board_type> <b.p.d> have been Dropped . . . . . . . . . . . . . . . . . . . 146M8004 <board_type> <b.p.d> Failed <test_type> Self-Test . . . . . . . . . . . . . . . . . . . . . . 146M8005 <device> <b.p.d> Command too Large for Buffer:

Length <xx > Buffer Size <yy> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147M8009 T1 Card <card> Detected Missing Network Clock Card

(Axxess Only Pre v8.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147M8010 <side>: Fiber FPR Indicates Abnormal Status = <status> (Axxess Only) . . . . . . 147M8011 <side>: No Signal from Fiber Optic Cable (Axxess Only) . . . . . . . . . . . . . . . . . . 148M8012 <side>: No Signal from Fiber Optic Cable;

Resetting Communication (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148M8013 <side>: Fiber-Optic Multiplexer is Out-of-Sync:

Sync = <sync> (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Contents

Page xx Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011

M8014 <side>: Fiber-Optic Multiplexer is Out-of-Sync (Two Masters): Sync = <sync> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

M8015 <side>: Fiber-Optic Multiplexer is Out-of-Sync; Resetting Comm Sync = <sync> (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . 149

M8019 <side>: Fiber Controller Inactive (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 149M8020 <side>: Fiber Controller Inactive too Long;

Resetting Communications (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149M8021 <side>: No Response from Other Fiber Controller (Axxess Only) . . . . . . . . . . . . 150M8022 <side>: Fiber Queue Time Out (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 150M8023 <side>: CP on Both Slave and Master (Axxess Only) . . . . . . . . . . . . . . . . . . . . . 150M8024 <side>: Fiber Error: Two Slaves Detected; Error Count =

<count> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150M8026 <b.p.d> Illegal Data Byte Sent to Board: Type = <xx>,

Board = <bb>, Circuit = <cc> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151M8027 <b.p.d> Illegal <type> Sent to Board: <data>. . . . . . . . . . . . . . . . . . . . . . . . . . . . 151M8028 <b.p.d> Illegal <type> Sent to Single-Line Adapter . . . . . . . . . . . . . . . . . . . . . . . 152M8030 SLC16 48-Volt Power Supply Fail on Board <board> (Axxess Only). . . . . . . . . . 152M8031 SLC16 72-Volt Power Supply Fail on Board <board> (Axxess Only). . . . . . . . . . 152M8032 <b.p.d> SLC16 QSLAC Failure for Devices <devices> (Axxess Only) . . . . . . . . 152M8046 <b.p.d> Invalid Subtask ID <task-ID> for <device>: <msg>. . . . . . . . . . . . . . . . . 153M8047 <b.p.d> Invalid Subtask ID <task-ID> for <board>: <msg> . . . . . . . . . . . . . . . . . 153M8050 <b.p.d> Null Message for <device> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154M8051 <b.p.d> Null Message for <board>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154M8053 <b.p.d> Invalid DSP Input <dsp_inp> from DSP <dsp_num>: <msg>. . . . . . . . . 155M8056 <b.p.d> <board>: Incompatible ISDN FW Version = <ver1> Expecting <ver2>

(Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155M8057 <b.p.d> <board>: Incompatible FW Version = ver1;

Expecting ver2 or Higher (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155M8058 <b.p.d> <board>: No Downloadable Firmware (Axxess Only) . . . . . . . . . . . . . . . 156M8059 <b.p.d> Bad Length in Code Image: <0xHHHHHHHH> (Axxess Only) . . . . . . . . 156M8060 <b.p.d> Bad Starting Address in Code Image: <0xHHHHHHHH>

(Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156M8061 <b.p.d> Boot Length Mismatch: Computed = <0xHHHHHHHH>, Image =

<0xHHHHHHHH> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156M8062 <b.p.d> Boot Checksum Mismatch:

Computed = <computed>, Image = <image> (Axxess Only) . . . . . . . . . . . . . . . . 157M8063 <b.p.d> Card-Specific Checksum Mismatch:

Computed = <computed>, Image = <image> (Axxess Only) . . . . . . . . . . . . . . . . 157M8064 <b.p.d> Boot Code Received Unknown Message:

<xx,xx,xx,xx,xx> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157M8065 <b.p.d> Code/Board Mismatch: Code ID = <0xXX_code>,

Board ID = <0xXX_board> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158M8066 <b.p.d> Three Consecutive Download Attempts Failed (Axxess Only) . . . . . . . . 158M8073 <b.p.d> Invalid <item> in Hardware Message: <msg>. . . . . . . . . . . . . . . . . . . . . 158M8074 <b.p.d> Invalid <item> in Hardware Error Message: <msg> . . . . . . . . . . . . . . . . 159M8080 <string> on BRI Port <b.p.d> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159M BRI Port Problem: <type> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159M8082 <string> Condition Cleared on BRI Port <b.p.d> . . . . . . . . . . . . . . . . . . . . . . . . . 159M8083 BRI Port <b.p.d> in Dead State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Contents

Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page xxi

M8090 Unable to Open COM2 Port: Result = <result> (Axxess Only) . . . . . . . . . . . . . . 160M8091 <ext>: Illegal Message Type Sent to Device:

<protocol_type> <reject_msg_typ> <info> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160M8092 Emergency Call Failed on Analog Line <error cause = error)> . . . . . . . . . . . . . . 160

Engineering Severe Error Messages (M9000–M9999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161M9000 MAJOR RESET/Minor Reset: OS Detected Software Error. . . . . . . . . . . . . . . . . 161M9000 MAJOR RESET: Watchdog Expired During OS MAJOR Reset Process. . . . . . . 161M9000 Minor Reset: Watchdog Expired During OS Minor Reset Process . . . . . . . . . . . 161M9000 MAJOR RESET: Watchdog Expired During User Task

MAJOR Reset Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161M9000 Minor Reset: Watchdog Expired During User Task Minor Reset Process . . . . . . 161M9000 MAJOR RESET/Minor Reset: User Task Detected Software Error . . . . . . . . . . . 162M9001 <type-of-exception>: Unrecognized Reset Code <0xHHHH> . . . . . . . . . . . . . . . 162M9002 <type-of-exception>: <exception-description> (Axxess Only) . . . . . . . . . . . . . . . 162M9002 Operator Request (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162M9002 POST Queue Overflow (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162M9002 Watchdog Occurred (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162M9002 Port Wait Queue Overflow (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163M9002 Quantum Count Failure (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163M9002 Executive Request Failure (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163M9002 Addressing Error (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163M9002 Illegal Instruction (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163M9002 Zero Divide (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163M9002 Check Instruction (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163M9002 Trap V Instruction (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164M9002 Privilege Violation (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164M9002 Trace (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164M9002 L1010 (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164M9002 L1111 (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164M9002 Reserved Vector (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164M9002 Format Error (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164M9002 Uninitialized Vector (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165M9002 Spurious Interrupt (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165M9002 Trap 0, Trap 6, Trap 7, Trap 8,..., Trap 15 (Axxess Only) . . . . . . . . . . . . . . . . . . 165M9002 Bus Error (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165M9002 Timer Overflow Error (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165M9002 Message Length Error (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165M9002 Invalid Logical Address from IOC (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . 165M9002 Real-Time Task too Far Behind (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . 166M9002 Parity Error (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166M9002 Invalid OS Command (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166M9002 User Task Requested Reset (Axxess Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166M9003 <type-of-exception>: Unrecognized Exception Code (<0xHHHH>): <msg> . . . . 166M9004 Heap Overflow (Axxess Only Pre v8.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167M9005 Heap Check Failure: <reason> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167M9006 Device: <routine-name> Extension Failure <ext>, Device <username> . . . . . . . 167M9007 Device: <routine-name> Could Not Allocate Non-Dialable Extension . . . . . . . . . 167

Contents

Page xxii Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011

M9008 Device: <routine-name> Could Not Release Non-Dialable Extension . . . . . . . . . 167M9009 Caller <ext-1> Dropped by <ext-2> While Recovering

from an Invalid Forward Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168M9010 Static Constructor Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168M9011 ASAI User Info Message Exceeds Maximum Allowed Length . . . . . . . . . . . . . . . 168M9012 ASAI Call Dropped by Call Processing Due to Invalid Call State. . . . . . . . . . . . . 168M9013 ASAI Call Dropped by ASAI Peer Due to Invalid Call State . . . . . . . . . . . . . . . . . 168M9014 Unable to Realloc Memory for ASAI User Info Message . . . . . . . . . . . . . . . . . . . 169M9015 The Dynamic Heap has been Defragmented (Axxess Only) . . . . . . . . . . . . . . . . 169M9016 DSP Watchdog Detected Failure of <device> . . . . . . . . . . . . . . . . . . . . . . . . . . . 169M9020 Exception Recorded: DMTRACK Synchronization Error on

Port <port> (Axxess Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169M9021 <eeee>: Null VoIP DSP Resource Pointer Found in

<routine> Resulting in No/One-Way Audio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170M9022 <eeee>: Invalid Audio Receive Port Range Received – Result = No Audio . . . . 170M9090 <Voice_Mail_Unit> PC Watchdog Reset Occurred (VPU/EM Only) . . . . . . . . . . 170

Mitel® 5000 and Inter-Tel® Axxess® Message Print Diagnostics Manual – Issue 23, January 2011 Page 1

Overview

OverviewThe 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.

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 ClearedFIELDS: 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 ClearedFIELDS: 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.



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:

x The printer ran out of paper (Data Terminal Ready [DTR] is not asserted) and hardware handshaking is enabled.

x The printer cable is unplugged or the printer is powered off.

x The printer cable, printer, or serial port are faulty.

x 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:




x 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.


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.



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 BusyFIELDS: 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 CertificateFIELDS: 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.


Alarm Messages (A000–1099): Minor Voice Processing Alarms (A020–A039)

Minor Voice Processing Alarms (A020–A039)This section defines the minor Voice Processing alarms. These alarms generally can be handled by the customer without the need for a service call.

A020 Voice Mail Printer Off-Line (VPU/EM Only)FIELDS: None.

CAUSES: The system could not write to the Voice Processing Print printer for 1 minute. The problem can be one of the following:





A021 Voice Mail Unit 80% Full (VPU/EM Only)FIELDS: None.

AXXESS CAUSE: The hard disk on the voice processing unit system is filled to 80% of capacity.

5000 CAUSE: The file system on the voice processing unit system is filled to 80% of capacity.

AXXESS ACTION: The number of saved messages or unheard messages must be reduced, or a larger hard disk must be used. Alternatively, if an SMDR buffer is used, you can free up more voice mail storage by reducing the size of the SMDR buffer.

5000 ACTION: The number of saved messages or unheard messages must be reduced, or a larger file system must be used. Alternatively, if an SMDR buffer is used on external voice mail units, you can free up more voice mail storage by reducing the size of the SMDR buffer.

A022 Voice Mail Unit 100% Full (VPU/EM Only)FIELDS: None.

AXXESS CAUSE: The hard disk on the voice processing unit system is filled to capacity.

5000 CAUSE: The file system on the voice processing unit system is filled to capacity.

AXXESS ACTION: The number of saved messages or unheard messages must be reduced, or a larger hard disk must be used. Alternatively, if an SMDR buffer is used, you can free up more voice mail storage by reducing the size of the SMDR buffer.

5000 ACTION: The number of saved messages or unheard messages must be reduced, or a larger file system must be used. Alternatively, if an SMDR buffer is used on external voice mail units, you can free up more voice mail storage by reducing the size of the SMDR buffer.

NOTEThe voice processing unit displays this alarm only when it first recognizes the 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.

NOTE

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 broadcast message.

Changing the size of the SMDR buffer discards all stored SMDR records. The Unified Voice Messaging Module on the 5000 does not have a SMDR buffer.



A023 SMDR Unit 80% Full (VPU/EM Only)FIELDS: None.

CAUSE: The portion of disk space on the voice processing unit hard disk reserved for SMDR storage is filled to 80% of capacity.

ACTION: Reduce SMDR Record storage by attaching a device capable of receiving the SMDR data to the SMDR communications port and initiate an SMDR dump procedure. If the 80% full condition occurs frequently, it is an indication that the SMDR buffer needs to be dumped more often or that the SMDR buffer size needs to be increased.

A024 SMDR Unit 100% Full (VPU/EM Only)FIELDS: None.

CAUSE: The portion of disk space on the voice processing unit hard disk reserved for SMDR storage is filled to capacity.

ACTION: At this point, the system discards the oldest SMDR records to make room for the new records. Increase the available SMDR Record storage by attaching a device capable of receiving the SMDR data to the SMDR communications port and initiate an SMDR dump procedure. If the 100% full condition occurs frequently, it is an indication that the SMDR buffer needs to be dumped more often or that the SMDR buffer size needs to be increased.

A025 Voice Processing Unit <n>: <message>FIELDS: n The alarm number.

message The alarm message text from voice processing.

CAUSE: An alarm was generated by the voice processing unit.

ACTION: None.

A026 Voice Processing Email Gateway is DisabledFIELDS: None.

CAUSE: The Voice Processing Email Gateway is not functioning.

ACTION: Verify the accuracy of the Email Gateway configuration in Database Programming. If that is correct, contact the Email Server administrator to determine if the system is on-line and the account configured in the Email Gateway configuration exists on the Email Server.

A027 Voice Processing <app> Application CorruptFIELDS: app The application that has become corrupt.

CAUSE: One of the VM APPS has become corrupt due to an internal software error or network problem.

ACTION: Get a freeze, and then call a technician. Next, reset the voice mail when the system is idle to try to clear the problem. As a last resort, reset the system.

NOTE Changing the size of the SMDR buffer discards all stored SMDR records. The Unified Voice Messaging Module on the 5000 does not reserve SMDR storage.

NOTEIncreasing or changing the size of the SMDR buffer discards all stored SMDR records. The Unified Voice Messaging Module on the 5000 does not reserve SMDR storage.

NOTE This alarm message type is reserved for future use.



A028 Voice Processing Unit Out of SyncFIELDS: None.

CAUSE: The Email Forwarding Task in Voice Mail is only partially configured. For example, the e-mail system is set to SMTP in Database Programming, but no administrator e-mail address is configured.

ACTION: Verify the accuracy of the E-mail Gateway configuration in Database Programming. An administrator e-mail address must be configured. The correct gateway address must be configured. Each mailbox that wants to use forward to e-mail and has it configured as either “Forward Only” or “Forward and Copy” must have a valid e-mail address.

A030 <VoiceMailUnit> No Primary Language Prompts Installed FIELDS: VoiceMailUnit: The voice mail unit (voice processing unit).

CAUSE: The voice processing unit was installed without any primary language prompts or the prompts installed do not match the Voice Mail Unit.

ACTION: Install the primary language prompts if no prompts are installed. If prompts are already installed, check the language of the prompts to ensure they match the Voice Mail Unit. Install the correct prompts if the language does not match the Voice Mail Unit.

A031 <VoiceMailUnit> Hacker AlertFIELDS: VoiceMailUnit: The voice mail unit (voice processing unit).

CAUSE: A voice mail subscriber or hacker entered an invalid passcode three times in a row.

ACTION: None. This could be the result of a voice mail subscriber forgetting or not entering his or her passcode correctly multiple times. If the voice mail subscriber believes someone is trying to hack into their mailbox, a voice mail freeze should be sent to Mitel Technical Support to identify the source of the caller.

A032 Extension <eeeee> Received Insufficient BandwidthFIELDS: eeeee The extension number of the device that received the insufficient bandwidth message.

CAUSE: The system detected that the IP phone's audio-receive timer has expired without receiving the first audio packet or the average-in-time-frame percentage has fallen below the threshold specified in the Voice Audio Session Configure Command.

ACTION: This indicates a network problem. Poor network conditions could cause packet loss or a firewall is preventing the caller from receiving audio packets. Dump the network diagnostics file for more information.

NOTE There is a system flag that can disable this alarm.

Alarm Messages (A000–1099): Major System Alarms (A100–A199)


Major System Alarms (A100–A199)This section defines the major System alarms. These alarms usually require a service call.

A100 Device <b.p.d> Extension <eeeee>: Reset Due to Excessive Data Errors

FIELDS: b.p.d The board/port/device designation of the device that is generating the excessive data errors.

eeeee The extension number of the device that is generating the excessive data errors.

AXXESS CAUSE: The phone is detecting an unusually large number of data errors in the data packets sent to the phone by the DKSC, DKSC16, or IPRC board. This is causing unnecessarily long transmission delays to the phone and possibly some service-affecting problems.

5000 CAUSE: The phone is detecting an unusually large number of data errors in the data packets sent to the phone by the IPRA or digital phone module. This is causing unnecessarily long transmission delays to the phone and possibly some service-affecting problems.

SYMPTOMS: Due to excessive data errors (see M5067 on page 90), the system resets the indicated device in an attempt to correct the problem. If there was audio at the device, the call has been dropped. If the problem continues, the device will be locked-out (see M5069 on page 91).

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 the appropriate hardware component. Return the faulty component to Mitel for repair. See M5068 (page 91) 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 M5068 (page 91) for more information.

A101 Device <b.p.d> Extension <eeeee>: Reset Due to Excessive Hardware Failures

FIELDS: b.p.d The board/port/device designation of the device that is generating the excessive hardware errors

eeeee The extension number of the device that is generating the excessive hardware errors

AXXESS CAUSE: The DKSC, DKSC16, or IPRC board is detecting an unusually large number of data errors in the data packets sent from the phone to the DKSC board. The phone may be having some hardware problems, or the cabling between the phone and the DKSC or DKSC16 is faulty. If the phone resides on an IPRC board, there would be network issues. However, it is unlikely this will happen because the connection between the IPRC and the phone is TCP connection.

5000 CAUSE: The IPRA or the digital phone module is detecting an unusually large number of data errors in the data packets sent from the phone to the IPRA or the digital phone module. The phone may be having some hardware problems, or the cabling between the phone and digital phone module is faulty. It is unlikely this will happen because the connection between the IPRA and the phone is a TCP connection.

SYMPTOMS: Due to excessive hardware failures (see M5070 on page 91), the system reset the indicated device to attempt to correct the problem. If there was audio at the device, the call has been dropped. If the problem continues, the device will be locked-out (see M5072 on page 92).



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 92) 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 92) for more information.

A102 Serial Port <b.p.d>: Tx Interrupt is Not Operational (Axxess Only)

FIELDS: b.p.d The board, port, and device numbers of the serial port that has a problem with interrupts

CAUSE: The indicated port does not signal the processor with an interrupt when the transmission of a character completes. The serial driver chip is probably faulty.

ACTION: Return the appropriate hardware component that has the indicated serial port (CPU board, OPC board, DKSC Data Port Module) to Mitel for repair.

A103 Serial Port <b.p.d>: Clock is Not Operational (Axxess Only)FIELDS: b.p.d The board, port, and device numbers of the serial port that has a clock which is not

operational.

CAUSE: The clock that governs the transmission speed of the serial port is not operating properly. The serial driver chip is probably faulty.

ACTION: Return the appropriate hardware component that has the indicated serial port (CPU board, OPC board, DKSC Data Port Module) to Mitel for repair.

A104 ALARM CPU: Database Corruption (Axxess Only)FIELDS: None.

CAUSE: The database stored in battery-backed memory on the CPU board did not checksum properly. The system performs the checksum test once a day to verify the integrity of the database. The memory chips may be faulty. However, there is one way this condition can occur without the memory being faulty. If the processor is doing a write into protected memory at the exact moment an external interruption occurs (loss of power, pressing the reset button, etc.), the data written to the write-protected memory may be corrupted.

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.

NOTE If the power is turned off, the system will default the database.



A105 CPU: Write-Protect is Not Operational (Axxess Only)FIELDS: None.

CAUSE: The write-protect circuitry on the CPU board is not functioning properly. The write-protect circuitry on the board helps prevent the database from getting corrupted by stray memory writes from the processor due to a software problem, a hardware problem, or random events when power is turned off.

ACTION: This condition will not cause any immediate problems. However, the database should be saved and the CPU board replaced with a functioning board to help prevent any possible problems from occurring.

A106 CPU: Real-Time Clock is Not Operational (Axxess Only)FIELDS: None.

CAUSE: The real-time clock circuitry is not functioning properly. The system will use a software clock to keep track of time. This means that date and time will need to be reset by hand each time the power is turned off, and will cause the time to drift more.

ACTION: When convenient, replace the board that contains the real-time clock chip. On an ACPU/MEM system, the clock is on the MEM board; on an CPU020/PCM system the clock is on the CPU020 board; on an Axxent system, the clock is on the Axxent CPU/Motherboard. Return the faulty board to Mitel for diagnosis and repair.

A107 CPU: Watchdog is Not Operational (Axxess Only Pre v8.0)FIELDS: None.

CAUSE: The watchdog circuitry on the CPU board is not operational. This circuitry prevents hardware or software errors from locking up the system indefinitely. If the system does not refresh the circuitry within a set time period, the system is forced to reset under the assumption that the system has died.

ACTION: This condition will not cause any immediate problems. However, for greater safety, the CPU board should be replaced. If the watchdog jumper is installed, remove it. The watchdog jumper is located just below the Actel gate array, near the upper middle of the CPU board.

A108 CPU: Interval Timer is Intermittent (Axxess Only)FIELDS: None.

CAUSE: The interval timer on the CPU board is not functioning properly. The system uses this timer to regulate events.

ACTION: Replace the CPU board. Return the faulty CPU board to Mitel for diagnosis and repair.

A109 CPU: Watchdog Expired During Minor Reset (Axxess Only)FIELDS: None.

CAUSE: When the system attempted a minor reset, it did not recover and refresh the watchdog timer, so the hardware watchdog assumed the system was dead.

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.

FSACTION: Report the problem to the engineering contact person for further analysis. Provide the CP Error Information and the database.



A110 CPU: Database Feature Bundling Error (Axxess Only Pre v8.0)

FIELDS: None.

CAUSE: The system detected an inconsistency between the hardware information about the number of feature bundling units available and the information stored in the database. The system assumes a hacker has attempted to steal feature units, so it defaults to the base number of feature units.

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.

A111 CPU: Battery Backed Memory Too Low (Axxess Only)FIELDS: None.

CAUSE: A user either requested a reminder message, left a message for another station, or queued onto another device. However, the system was too low on Battery Backed memory, so it could not store the information. It is also possible that a technician tried to add more stations, trunks, or boards to a system when Battery Backed memory was already low.

ACTION: Immediately save the database.

This condition should not happen unless there is extensive station message or queue traffic on a system, or if there is a software problem.

To determine if there is a software problem, verify station messages cannot be left for another station. Turn off power and remove the battery backup jumper for 30 seconds, and then restore the saved database. Reset the system. If you are able to leave several station messages on different stations without any problem, cancel the messages that were left and contact Mitel Field Service to report your results. Send the saved database to Mitel.

If you could not leave multiple station messages after restoring the saved database, the database must be too large. Verify that multiple stations do not have a large number of station messages left for them, and then cancel all queue operations from all phones on the system. If this does not solve the problem, contact Mitel Field Service to report your results. Send the saved database to Mitel Field Service.

FSACTION Report the problem to the engineering contact person for further analysis. Provide the CP Error Information and the database.

NOTE This alarm also occurs after restoring a database that has more features enabled than the system allows.



A112 CPU: Running Low on System Dynamic Memory (Heap) FIELDS: None.

CAUSES: Too much call activity (see below) or a software error.

The system uses dynamic memory that is on the CPU board to hold data that the software needs to use for performing call handling functions, storing temporary information, etc. Each device in the system (CO trunk, phone, etc.) requires some dynamic memory. In addition, each call that is currently active requires some dynamic memory. What has happened is that system has consumed most of the dynamic memory to handle the many calls which are active at the same time.

Because the system must have dynamic memory to run properly, it generates this alarm when it is low on dynamic memory. When the first threshold is met, (defined by the database field “Final Heap Warning” which is set to 10 percent of the total available “dynamic” memory), the system starts forcing CO trunk multiple ring-ins to ring only the primary attendant because ringing one station will consume less dynamic memory than ringing several stations. The alarm and a delayed major reset are activated at this time.

If the condition persists and less memory than the second threshold is met (defined by the database field Final Heap Warning, which defaults to 5 percent of the total available dynamic memory), the system starts to prevent new calls from being made. CO Trunk ring-ins are ignored and station users cannot make calls, they will receive an ALL CIRCUITS BUSY display. However, station users can answer calls at their station if some of the calls that are consuming system dynamic memory will be terminated, releasing some of the dynamic memory for others to use. The alarm and a delayed major reset are activated at this time.

If this condition persists and no dynamic memory is available, the system performs a major reset immediately. This will drop all active calls and free up all dynamic memory.

It is possible a software error is causing the trouble if the software is not releasing dynamic memory when it is done with it. This will slowly cause the system to lose dynamic memory and eventually new calls will hit the memory thresholds.

ACTION: Verify the customer's configuration does not have many trunks ringing into many stations, and that there are not many all-ring hunt groups configured with many stations in them. These items consume a lot of dynamic memory each time a call is made because the call fans out to make one call to each device in the list. This action consumes a lot of dynamic memory. If this configuration is present, reduce the number of stations in each multiple ring-in for a trunk or in each all-ring hunt group. This includes a linear or distributed hunt group that has an extension list with many stations in it as one of its ringing points.

After the system configuration changes have been made, reset the system by using the Database Programming or by powering the system down. This will clear up any memory left from the previous multiple ringing calls.

If the problem persists even after the number of CO Trunk multiple ring-in stations and all-ring hunt stations have been reduced, the problem may be due to a software error. Report this problem to Mitel Field Service, along with the saved database and the System History Logs.




A114 <board_type> <card/bay> <port> in Red AlarmAXXESS FIELDS: board_type A string specifying whether this is T1 or E1.

card The board number that the problem occurred on.

port The port number the error occurred on.

5000 FIELDS: board_type A string specifying whether the module is T1 or E1.

bay The expansion bay that the error occurred on.

port The port number the error occurred on.

CAUSE: An initial trouble condition was detected on the T1 or E1. If the condition lasts for several seconds, the Red Alarm Condition Detected message appears and all calls on the T1 or E1 will be dropped. See M8000 (page 144) and M8001 (page 144) for additional information.

ACTION: The initial trouble condition that was detected or the resulting Red Alarm must be resolved. See M8000 (page 144) and M8001 (page 144) for additional information.

A115 System History Frozen Due to a Software ExceptionFIELDS: None.

CAUSE: The system froze the System History automatically because a software exception occurred.

ACTION: Use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.


A116 Database Battery Low (Axxess Only)FIELDS: None.

CAUSE: The system has detected that the power-level of the database battery is low. After this occurs, the system continuously monitors the power-level of the battery and reports an alarm every hour, on the hour, until the battery is replaced.

ACTION: Replace the database battery.

A117 Database Battery Jumper in Off Position (Axxess Only)FIELDS: None.

CAUSE: The system has detected that the database battery jumper is in the off position.

ACTION: Insert the database battery jumper in the on position.

A118 Voice Mail Card Reset by OS (Axxess Only)FIELDS: None.

CAUSE: The Embedded Voice Mail Card failed to tickle the watchdog. The voice mail card was not operating properly and by resetting it, the OS attempts to clear up the problem.

ACTION: The problem should clear itself up. If the problem persists, replace the voice mail card.

A119 Link to Secondary Cabinet Lost (Axxess Only)FIELDS: None.

CAUSE: The fiber-optic link between the primary and secondary cabinet is not functioning properly. This could be due to either the fiber-optic cable being removed or compromised, or due to the secondary cabinet losing power. All devices in the secondary cabinet will be non-functional (i.e., off-line). The system will drop all calls that are in progress between cabinets when the link is lost.

ACTION: Determine why the fiber-optic link was compromised and fix the problem.



A120 Static Memory Fault (Axxess Only)FIELDS: None.

CAUSES: This alarm only applies to a Call Processing Server. The system was unable to establish a region of static, write-protected memory. This may occur for one of the following reasons:

The system could not open or create the static database file on disk.

The system found or created the database file on disk, but could not load it into program memory.

ACTION: Check the command line argument to make sure that it specifies a valid path for the database file. If that does not correct the problem, contact Mitel Field Service.

A121 System History Frozen Due to a Freeze-On StringFIELDS: None.

CAUSE: The system froze the System History automatically because a “freeze-on” string was output by MSG Print.



A122 Invalid or Missing Security Key – Audio DisabledFIELDS: None.

CAUSE: The hardware licensing device used to guard against software theft is either missing or invalid. If the hardware licensing device is valid, then there could be a hardware failure that requires a new hardware licensing device.

ACTION: The user should either purchase the software legally or contact their dealer to have the key replaced. The user should contact Technical Support if the hardware licensing device is valid.

A123 PCMA <pcma> is Off-Line (Axxess Only)FIELDS: pcma The CPU that is off-line.

CAUSE: This alarm only occurs on a Call Processing Server ATM system. The connection to the CPU in question has been lost. This could be due to either the cable being removed or compromised, or due to the chassis losing power. All devices in the chassis and attaching cabinet will be non-functional (i.e., off-line). The system will drop all calls that were in progress to that chassis when the link was lost.

ACTION: Determine why the link was compromised and fix the problem.

A124 System Running on Backup Key: <xx> Hours Remaining (Axxess Only)

FIELDS: xx The number of hours that the backup CP Server will continue to operate (countdown from 100 hours).

CAUSE: The connection to the master redundancy CP Server has been lost. Either the cable is removed or compromised, or the computer lost power or is failing mechanically. All devices in the chassis and attached cabinet will continue to function until the time expires, at which point the audio is terminated.

ACTION: If the master computer had a major failure, remove the key on the master and place it on the backup computer to reduce the risk of losing audio resources.



A125 Invalid Software License: Reset in <xx> MinutesFIELDS: x The number of minutes remaining until the system resets. This alarm initially displays 240

minutes (4 hours) and is generated every 5 minutes.

AXXESS CAUSE: The technician has not uploaded a software license for the system version loaded. If the software license has already been loaded, then there could be a hardware issue that would require a new CPC card or hardware licensing device.

5000 CAUSE: The technician has not uploaded a software license for the system version loaded. If the software license had already been loaded, then there could be a hardware issue that would require a new hardware licensing device.

ACTION: Log into Database Programming and upload the software license. If this does not fix the problem, the system thinks the software license is corrupted. Contact Technical Support immediately.

A127 Unlicensed Device <ext> Failed to Come On-LineFIELDS: ext The extension of the device that failed to come on-line due to a licensing error.

CAUSE: The CP received an on-line request from a device but there was not a device license available, therefore, the device cannot come on-line.

ACTION: Unequip the device or purchase more device licenses.

A128 <Extension>: User-Triggered Audio DiagnosticFIELDS: Extension The extension that activated the Audio Diagnostic Feature.

CAUSE: Someone has activated the Audio Diagnostic Feature from a phone (extension).

ACTION: Collect the freeze that was created from activating the Audio Diagnostic Feature.

A129 Unlicensed PRI Module <module> Port <port> Failed toCome On-Line (5000 Only)

FIELDS: module The module number that failed to come on-line due to a licensing error.

port The port number that failed to come on-line due to a licensing error.

CAUSE: The number of on-line PRI modules as specified by the PRI license count is exceeded. The PRI module will not come on-line.

ACTION: Remove a PRI module, unequip the offending PRI module, or purchase more PRI licenses.

A130 Unlicensed DEI Unit <unit> Failed to Come On-Line (5000 Only)

FIELDS: unit The DEI unit number that failed to come on-line due to a licensing error.

CAUSE: There is an unlicensed DEI unit as specified by the DEI license. The DEI unit will not come on-line.

ACTION: Purchase valid DEI unit license.

A131 Voice Mail Ports Not Licensed (5000 Only)FIELDS: None.

CAUSE: No licensed Unified Voice Messaging (UVM) ports.

ACTION: Purchase valid UVM port licenses.



A132 Invalid or Missing License Key Information (5000 Only)FIELDS: None.

CAUSE: The hardware licensing device, used to guard against software theft, is either missing or invalid. If the device is valid, then there could be a hardware failure that requires a new hardware licensing device.

ACTION: The user should either purchase the software legally or contact their dealer to have the hardware licensing device replaced. Users should contact Mitel Technical Support if the hardware licensing device is valid.

A133 License Key Recovery Attempt (5000 Only)FIELDS: None.

CAUSE: The hardware licensing device used to guard against software theft is missing or cannot be read. If the hardware licensing device is plugged in, then there could be a hardware failure and the system will try to recover by calling the reset_usb script. This recovery attempt is logged by this alarm.

ACTION: The user should contact Technical Support if the hardware licensing device is valid.

A134 Channel Allocation Error on Board <number> Audio Session<session> (5000 Only)

FIELDS: module The module that had the channel allocation error.

session The audio session where the channel allocation error occurred.

CAUSE: Call Processing tried to allocate a audio channel that the Processor Module/Expansion Module could not allocate.

ACTION: Freeze the system and contact Technical Support as soon as possible. Reset the system manually at the earliest convenience to clear up this issue.

A135 Channel IP Resource Campon Error (5000 Only)FIELDS: None.

CAUSE: Call Processing tried to allocate an IP resource and could not. Because the IP resource diagnostics level was set to log these scenarios as a problem, Call Processing will send this alarm.

ACTION: Freeze the system and contact Technical Support as soon as possible.

A136 Automatic Diagnostics Delivery Transmission FailureFIELDS: None.

CAUSE: A transmission failure occurred while attempting to do an Automatic Diagnostics Delivery (ADD). This may be caused by networking problems, ADD server failure, or bad configuration.

ACTION: Make sure Automatic Diagnostics Delivery is programmed correctly and that the ADD Server is accessible. Contact Technical Support if the problem persists.

A137 Power Failure Detected – UPS Running on Battery (5000 Only)

FIELDS: None.

CAUSE: The Mitel 5000 has a UPS attached via the USB interface. The 5000 system has detected that a power failure has occurred. The UPS is now running on battery.

ACTION: The UPS will maintain power for a limited period of time. The user should determine if the source of the power failure is caused locally (i.e., UPS power source is unplugged or there is an electrical breaker issue) or the failure is caused by downed service from the electrical provider.



A138 Unlicensed DT1 Module <module> Port <port> Failed toCome On-Line (5000 Only)

FIELDS: module The expansion module number that failed to come on-line due to a licensing error.

port The port number that failed to come on-line due to a licensing error.

CAUSE: The number of on-line DT1 second ports as specified by the license count is exceeded. The DT1 module second port will not come online.

ACTION: Unequip a module with a second port license and re-equip a different module which needs a second port license, or purchase more PRI licenses.

A139 Unlicensed DT1 Module <module> Port <port> Failedto Allocate Echo Canceller (5000 Only)

FIELDS: module The expansion module number (1-3 on a CS, 1-4 on a HX) that failed to come on-line due to a licensing error.

port The port number (1-2) that failed to come on-line due to a licensing error.

CAUSE: The number of echo cancellers for DT1 ports is exceeded. The DT1 port will not have an echo canceller allocated.

ACTION: Toggle the Echo Canceller Flag on a DT1 port that currently has an Echo Canceller license, and then toggle the flag on the DT1 port that you want to get the license, or purchase more Echo Canceller Licenses.

A140 Mismatch Between Database and Software License FIELDS: None.

CAUSE: There is a mismatch between the system size in the database and the software license. This most likely occurred because the software license was copied to the system, instead of uploading it through Database Programming.

ACTION: First, ensure that the correct software license is uploaded to the system using Database Programming. Next, default the database and use Database Programming to restore the database.

A141 No License for File-Based Audio <source>(5000 Only)FIELDS: source The file-based audio source that failed to come on-line due to a licensing error.

CAUSE: The maximum number of file-based audio sources exceeds the number allowed by the license.

ACTION: Unequip an existing file-based MOH source.

A142 DEI #<number> Out of Voice Channels FIELDS: number The DEI unit number (1-4).

CAUSE: One of the DEI units is out of voice channels. This typically happens in a system with three or four DEIs.

ACTION: Review the programming of each DEI. A DEI should not have more than 48 devices. Keep in mind that OHVA uses 2 voice channels (for a digital telephone).



A143 Remote Configuration Failed <reason>FIELDS: reason The reason for the configuration failure of the remote server.

CAUSE: The problem can be one of the following:

x Remote configuration already running.

x No response from server.

x Authentication failure.

x Server busy.

x Invalid serial number.

ACTION: Examine the state and configuration of the remote server.

A144 Ext <eeeee> SIP Registration Failure (5000 Only)FIELDS: eeeee The extension number of the SIP peer for which registration failed.

CAUSE: SIP registrations for the specified device have failed beyond provisioned failure threshold. This alarm is raised after registration is retried for the provisioned maximum number of times and registration is still not successful. This would stop further registration retries towards SIP peer.

ACTION: Correct any provisioning error for the SIP peer, or resolve any network or other issue that is causing the SIP Registrations to fail. In order to restart the registration process, an administrator can either change the operating state (INS -> OOS-Maint -> INS) or change any of the registration affecting database fields for this SIP peer. That would result in resetting the registration process. However, the administrator would have to clear this alarm explicitly.

A145 Ext <eeeee> SIP Peer Out-of-Service (5000 Only)FIELDS: eeeee The extension number of the SIP peer for which keep-alives or consecutive calls failed.

CAUSE: SIP keep-alives or consecutive calls for the specified SIP peer have failed beyond provisioned failure threshold. This alarm is raised when operating state of the SIP peer (Trunk Group or Voice Mail) changes from In-Service (INS) to Out-Of-Service (OOS). This alarm is cleared automatically when the SIP peer moves back to In-Service state.

ACTION: Correct any provisioning error for the SIP peer, or resolve any network or other issues that are causing the SIP keep-alives or calls to fail.

A146 Ext <eeeee> SIP Authentication Failure (5000 Only)FIELDS: eeeee The extension number of the SIP peer for which registration failed.

CAUSE: SIP authentication for the specified device has failed. This alarm is raised when a SIP Peer rejects the credentials in the SIP request (INVITE or REGISTER). These credentials are not retried as this would result in an endless loop. However, this alarm gives the administrator an opportunity to correct the credentials.

ACTION: Correct any provisioning error for the SIP peer and make sure correct credentials (username/password) are specified.

NOTE This is not an auto clearing alarm.

NOTE This is an auto clearing alarm.




A147 Ext <eeeee> SIP Peer License Error (5000 Only)FIELDS: eeeee The extension number of the SIP peer for which license error occurred.

CAUSE: The maximum number of calls/ports allocated for the specified SIP Peer exceeds the number allowed by the license.

ACTION: Make sure the number of calls/ports allocated for the SIP Peer is with in the limit allowed by the license.

A148 System Exceeded PSTN Call Record (5000 Only)FIELDS: None.

CAUSE: The system has exceeded the maximum number of PSTN call records for the Embedded Reporting feature. This limitation exists to prevent high call traffic systems from using an excessive amount of system resources.

ACTION: No action required. If the customer wants higher capacity of PSTN call records, they should consider upgrading to Mitel premium contact center solution.



Alarm Messages (A000–1099): Major Voice Processing Alarms (A200–A224)


Major Voice Processing Alarms (A200–A224)This section defines the major Voice Processing alarms. These alarms generally require a service call.

A200 <VoiceMailUnit>: Hard Drive FailureFIELDS: VoiceMailUnit The voice mail unit (voice processing unit).

AXXESS CAUSE: The hard drive on the voice processing unit has failed.

5000 CAUSE: This alarm only applies to external voice mail units. The hard drive on the voice processing unit has failed.

AXXESS ACTION: Save the database (if possible) and replace the hard drive in the voice processing unit.

5000 ACTION: For external voice mail units, save the database (if possible) and replace the hard drive in the voice processing unit.

A201 <VoiceMailUnit>: Channel FailureFIELDS: VoiceMailUnit The voice mail unit (voice processing unit).

AXXESS CAUSE: This alarm indicates that one of the voice processing unit voice boards is faulty or that a voice board software driver problem has occurred.

5000 CAUSE: For external voice mail units, this alarm indicates that one of the voice processing unit voice boards is faulty or that a voice board software driver problem has occurred.

For the Unified Voice Messaging system (UVM), this alarm may indicate a fatal error. The cause of the alarm is a result of an internal timeout where the UVM software did not receive a response in a timely manner. When this alarm occurs, the offending call will terminate prematurely. If the system encounters more than 16 occurrences of this alarm since the last system power-up, the system will stop UVM and generate two alarms in succession (alarm 201, and then eventually alarm 203).

AXXESS ACTION: First, determine whether the problem was temporary in nature (i.e., do additional calls to the voice processing unit to reproduce the same alarm). If the problem is not temporary in nature, attempt to clear up the problem by rebooting the voice processing unit. If this does not work or if the problem reoccurs, attempt to locate a faulty board by swapping boards in and out of the voice processing unit or by moving boards around within the voice processing unit. Test cables by swapping voice cables. Verify the CPU board or OPC board is not the source of the problem.

5000 ACTION: Perform the following procedures to classify the severity of the problem, and then report the test results to Mitel Technical Support.

For an external voice mail unit, attempt to clear the problem by rebooting the voice processing unit. If the problem continues, attempt to locate a faulty board by swapping boards in and out of the voice processing unit, or by moving boards around within the voice processing unit. Test the cables by swapping voice cables.

For Unified Voice Messaging (UVM), when this alarm appears it may indicate a fatal issue on the processor module. Perform the following to verify the state of the processor module:

1. Make a call to any UVM application and confirm audio. If UVM is not running due to this alarm, re-enable it using Database Programming. Make a call to UVM when it starts back up. If the UVM call has audio, there is no need to proceed to the next step.

2. If the first step has no-audio, make a call to one of the following devices: any IP phone, configuration assistant, or conference assistant. Determine if there is audio on the call.


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 5000 CP system with a PS-1, both the PS-1 and BS will require a reboot.

A202 <VoiceMailUnit>: Database CorruptionFIELDS: VoiceMailUnit The voice mail unit (voice processing unit).

CAUSE: One of the voice processing unit database files has been overwritten or otherwise corrupted. For example, there is an error on the hard disk which has resulted in invalid data being placed into the database files. A system reset may occur due to the invalid database.

ACTION: First, reboot the voice processing unit to see if the problem clears up. If the problem reoccurs, save the databases (both the system portions of the databases and the voice data on the voice processing unit) and default the databases. Do not restore the saved databases to the system or voice processing unit because the saved database is corrupted. Restore an older, valid database or manually reprogram the databases. You can restore just the system portion to get part of the database restored, then enable the voice processing unit and reprogram just the voice processing unit portion.

FSACTION: Report the problem to the engineering contact person for further analysis. Provide the CP Error Information, Voice Mail logs and the database.

A203 <VoiceMailUnit>: System Link DownFIELDS: VoiceMailUnit The voice mail unit (voice processing unit).

AXXESS CAUSE: The voice processing unit was rebooted, the voice processing unit RS-232 cable was disconnected or the communication channel was otherwise rendered inoperable. For example, the system serial port is faulty, the Voice Processing serial port is faulty, or the RS-232 cable is faulty.

5000 CAUSE: The voice processing unit or Unified Voice Messaging was rebooted, the voice processing unit IP connection was disconnected, or the voice processing unit or Unified Voice Messaging communication link was otherwise rendered inoperable.

AXXESS ACTION: First, see if the problem has already been corrected; if a call is attempted to an 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 RS-232 connection is still physically valid and that the port selected for voice processing unit communications is still valid and is programmed to 9600 baud with software handshaking. 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. 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.

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.

NOTE Rebooting the system will drop all calls.

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.

A204 <VoiceMailUnit>: Version MismatchFIELDS: VoiceMailUnit The voice mail unit (voice processing unit).

CAUSE: The version of voice processing unit connected to the system is incompatible or out-of-date.

ACTION: Determine the version of voice processing unit and system. Then, upgrade either or both systems. Go to the voice mail log files to determine the current version of the voice mail unit. Also, AVDAPMON will show the current version information.

Network Alarms (A225–A244)Call Processing Network alarms are only used internally to Call Processing to distinguish a local alarm from a network alarm. These are alarms sent to other nodes in the network to inform attendants of a problem. Because message print can be sent anywhere, these alarms will not generate a message print message on a remote node. In the example below, the local node would display alarm A011 in Message Print.

For example, when a remote node receives an emergency call alarm the main administrator will see NET ALARM #11 x<EXT> EMERGENCY. The second line of the display will state the node where the alarm originated. These network alarms indicate remote node alarms that do not require any different action than that of a local alarm.

NOTE Rebooting the system will drop all calls.


Alarm Messages (A000–1099): System Application Alarms (A1001–A1099)

System Application Alarms (A1001–A1099)This section defines the major System Application alarms. See the individual alarms to determine the level of service required.

A1001 DEI/DEM Failure (5000 Only)FIELDS: None.

CAUSE: An error occurred that caused the DEI/DEM application to fail.

ACTION: Restart the system. If the error persists, contact Mitel Technical Support.

A1002 DEI Fan Failure (5000 Only)FIELDS: None.

CAUSE: The system detected a failure of the DEI internal fan.

ACTION: Replace the affected DEI unit.

A1003 DDM-16 in Bay <b> Failed to Power Up Due to 3-DDM-16 Limit (5000 Only)

FIELDS: b: The bay number in which the DDM-16 is inserted.

CAUSE: The HX Controller supports a maximum of three DDM-16s.

ACTION: Remove one DDM-16.

A1004 DDM-16 in Bay <b> is not in a Compatible CS-5000 Chassis (5000 Only)


CAUSE: The CS Controller chassis does not support the DDM-16.

ACTION: Remove the DDM-16.

A1007 MSP Alert <x> (5000 Only)FIELDS: x: The MSP alert code.

CAUSE: The 5000 system has encountered an internal error.

ACTION: Contact Mitel Technical Support.

A1008 DDM-16 in Bay <b> Failed to Power Up Due to an UnknownPower Supply (5000 Only)


CAUSE: The DDM-16's power needs require that the system be able to identify the power supply.

ACTION: Use only authorized Mitel power supplies.

System Messages (M0001–M9999): Operating System Startup Severe Messages (M0001–M0049)


System Messages (M0001–M9999)M0001–M0049: Operating System Startup Severe messages

M0050–M0099: Operating System Startup Warning messages

M1000–M1999: Database Informational messages

M2000–M2999: Hardware Informational messages

M3000–M3999: Engineering Informational messages

M4000–M4999: Database Warning messages

M5000–M5999: Hardware Warning messages

M6000–M6999: Engineering Warning messages

M7000–M7999: Database Severe Problem messages

M8000–M8999: Hardware Severe Problem messages

M9000–M9999: Engineering Severe Problem messages

Operating System Startup Severe Messages (M0001–M0049)Severe problem messages are reported by the OS on the CPU Primary Port. These messages typically report on problems with the hardware that are detected by a startup self-test routine. The system is rendered inoperable until the problem is remedied. These messages are not grouped with the Severe Hardware messages because the OS writes the messages directly to the CPU Primary Port rather than using message print, which can be programmed to use any port.

M0001 CPU ROMs Failed Checksum – Bad or Not Present (Axxess Only Pre v8.0)

FIELDS: None.

CAUSE: As part of the system startup sequence after a power-up, the OS performs a checksum test on the ROM chips to verify they are present and properly installed. If the checksum fails, the ROMs are not installed properly, are missing, or are faulty.

ACTION: Verify all ROM chips are installed properly and seated well, and are all of the same software release. If the problem persists, try another set of ROMs.

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.

NOTE

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 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.



M0003 CPU Write-protected Database RAM Failure (Axxess Only Pre v8.0)

FIELDS: None.

CAUSE: One or more of the battery-backed RAM chips on the CPU or MEM board is not present, not pushed in all the way, or faulty. On the CPU and MEM boards, the battery-backed RAMs are the same as the normal dynamic RAMs.

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. If that doesn't solve the problem, there may be a serious software fault that shouldn't be seen in the field. Contact Mitel Field Service with this problem.

M0004 CPU Interval Timer Failure (Axxess Only Pre v8.0)FIELDS: None.

CAUSE: The interval timer circuit on the CPU board is not functioning properly. This circuit is tested as part of the OS Self Test that executes on power-up.

ACTION: Replace the CPU board. If that doesn't solve the problem, there may be a serious software fault that shouldn't be seen in the field. Contact Mitel Field Service with this problem.

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.

M0005 Task Initialization Table Error (Axxess Only Pre v8.0)FIELDS: None.

CAUSE: The OS detected an error in the Task Initialization table. This is a table in ROM that instructs the OS where each software task resides that runs under the OS.

ACTION: Replace the ROMs. If this doesn't clear the problem, there is a serious flaw with the CPU board. Replacing the CPU board. Contact Mitel Field Service with this problem.


M0006 Initialization Task Failure – Invalid OS Request (Axxess Only Pre v8.0)

FIELDS: None.

CAUSE: The Initialize task, which is the user task responsible for bringing the user portion of the system up into a running state was not able to complete its task because an OS executive request failed. The OS forces a major reset in this case. This error should never be seen in the field as it is due to a serious software error that will prevent the system from powering up.

ACTION: Contact Mitel Field Service with this problem.

FSACTION: Report the problem to the engineering contact person for further analysis.



M0007 Exception Handler Task Failure – Invalid OS Request (Axxess Only Pre v8.0)

FIELDS: None.

CAUSE: The Exception Handler task, which is the user task responsible for handling hardware and software exceptions and reporting the exceptions to the user, was not able to complete an OS executive request failed. The OS forces a major reset in this case. This error should never be seen in the field as it is due to a serious software error that will prevent the system from powering up.

ACTION: Contact Mitel Field Service with this problem.


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.
















M0012 OS Initialization Failure (Axxess Only Pre v8.0)FIELDS: None.

CAUSE: None.

ACTION: This message is obsolete. It should never appear. If it does, contact Mitel Field Service.






M0014 NCC Card Conflicts with CPU-020. Please Remove (Axxess Only)

FIELDS: None.

CAUSE: The NCC Card, which was previously required on older systems to allow T1 cards to sync up to the network, can not be used with the CPU-020 card. The NCC circuitry has been incorporated into the CPU-020 card itself. The OS will prevent the system from coming up -- the system will be dead.

ACTION: Power down the system and remove the NCC Card.

System Messages (M0001–M9999): Operating System Startup Warning Messages (M0050–M0099)


Operating System Startup Warning Messages (M0050–M0099)Warning messages reported by the OS on the CPU Primary Port. There must be at least one OS Startup Severe message in addition to the OS Startup Warning messages for this message to print. Otherwise, these messages are sent to the Exception Handler task and printed as different message numbers. These messages typically report on problems with the hardware that are detected by a startup self-test routine. The system is rendered inoperable until the problem is remedied (because an OS Startup Severe message is printed too). These messages are not grouped with the Warning Hardware messages because the OS writes the messages directly to the CPU Primary Port rather than using message print, which can be programmed to use any port.

M0050 Write-Protect Circuit Failure (Axxess Only Pre v8.0)FIELDS: None.

CAUSE: The protection circuitry that prevents stray writes from accidentally corrupting the battery-backed database is not working properly. This leaves the system open to a software problem that may destroy the database. Additionally, random events that occur when power is cycled may corrupt the database. However, this is not a serious error and the system can function properly for an unknown period of time before the system exhibits any problems due to this failure.

ACTION: When convenient, replace the CPU board.

M0051 Real-Time Clock Inoperative (Axxess Only Pre v8.0)FIELDS: None.

CAUSE: The real-time clock circuitry does not appear to function properly. This is not a serious problem. The system will function as if the real-time clock was not present and use a software clock. This means the date and time would have to be set manually, and may need updating periodically. It also means that a power outage will stop the system clock. The OS sends this Self Test result in a bit mask of self test minor alarms to the exception handler only during a MAJOR RESET following the port self test information.

ACTION: When convenient, replace the board that contains the real-time clock chip -- on an ACPU/MEM system, the clock is on the MEM board; on an CPU020/PCM system the clock is on the CPU020 board; on an Axxent system, the clock is on the Axxent CPU/Motherboard. Return the faulty board to Mitel for diagnosis and repair.

M0052 Real-Time Clock Stopped (Axxess Only Pre v8.0)FIELDS: None.

CAUSE: The real-time clock circuitry has stopped functioning. This is not a serious problem. The system will function as if the real-time clock was not present and use a software clock. However, you will have to set the date and time manually, and may have to update it periodically, due to drift. It also means that a power outage will stop the system clock. The OS sends this Self Test result in a bit mask of self test minor alarms to the exception handler only during a MAJOR RESET following the port self test information.

ACTION: When convenient, replace the board that contains the real-time clock chip -- on an ACPU/MEM system, the clock is on the MEM board; on an CPU020/PCM system the clock is on the CPU020 board; on an Axxent system, the clock is on the Axxent CPU/Motherboard. Return the faulty board to Mitel for diagnosis and repair.


System Messages (M0001–M9999): Operating System Startup Warning Messages (M0050–M0099)

M0053 WRN HW OS Real-Time Clock Needs Initialization (Axxess Only Pre v8.0)

FIELDS: None.

CAUSE: The real-time clock circuitry needs initialization.

ACTION: Report this problem to Mitel Field Service.


M0054 WRN HW OS Watchdog Interrupt Inoperative (Axxess Only Pre v8.0)

FIELDS: None.

CAUSE: The software protection circuitry that prevents the software from "hanging" the system is not functioning properly. If the OS does not reset the hardware watchdog periodically, it expires and forces the system to go through minor reset processing. This hardware failure leaves the system open to encountering a software problem that would require a power cycle or pushing the reset button to correct. However, this is not a serious error and the system can function properly for an extensive period of time before the system exhibits any problems due to this failure.

ACTION: When convenient, replace the CPU board. If this doesn't solve the problem, report the problem to 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

System Messages (M0001–M9999): Database Informational Messages (M1000–M1999)


Database Informational Messages (M1000–M1999)This section includes informational messages regarding the Database Programming or database operations. These messages do not affect normal system operation. No action is required.

M1000 Off-Node Device ID <id> Automatically CreatedFIELDS: id Node and Extension of new off-node device.

CAUSE: When devices accessible from other nodes are created, off-node devices are automatically created for the new device on all other nodes. This message indicates that a remote node has created a new device, and the corresponding off-node device has automatically been created on this node.

ACTION: Confirm that off-node access to the device is indeed desired.

M1001 Network Time Synchronized by Node <num>FIELDS: num Node number which initiated the synchronization.

CAUSE: The system clock was synchronized with the time on the indicated node. The sync network time will be generated periodically by node 1 to keep the network clocks in sync. It is also generated by an administrator on any node entering the Sync Network Minutes feature code. If the local time was off by 30 minutes or more, the hours may be set incorrectly.

ACTION: None.

M1002 Import of Device Info from Node <num> StartedFIELDS: num Node number which has begun sending device information

CAUSE: This message indicates that someone running Database Programming on a remote node has started an export of device information to this node. This node will receive information about all devices on the remote node and create a corresponding off-node device for each one. Existing off-node devices which are no longer present on the remote node will be deleted.

ACTION: None.

M1003 Import of Device Info from Node <num> CompletedFIELDS: num Node number which has completed sending device information

CAUSE: This message indicates that an import of device information from the indicated node has completed.

ACTION: None.

M1004 Export of Device Info to Node <num> StartedFIELDS: num Node number to which we are sending our device information.

CAUSE: This message indicates that someone running Database Programming has started a export of device information to the indicated node. This will result in the remote node creating corresponding off-node devices for all devices present on this node.

ACTION: None.



M1005 Export of Device Info to Node <num> CompletedFIELDS: num Node number which has completed processing of exported device information.

CAUSE: This message indicates that a node to which we were exporting our device information has completed processing the information that it received.

ACTION: None.

M1006 Removing Unused Off-Node Device ID <id>FIELDS: id The node number and extension of the off-node device which is being removed.

CAUSE: This message indicates that the previously existing off-node device with the indicated ID is no longer needed following an import of device information for the corresponding node. The off-node device is removed from the system.

ACTION: None.

M1007 Automatically Created Node Route Group <ext> for Node Number <node_number>

FIELDS: ext The extension of the node route group that was automatically created by the network status module.

node_number The node number of the new node route group.

CAUSE: This message indicates that the network status module has received an incoming static ping message from a node that it did not know about. The network status module used the information from static ping to create a new route group for the unknown node.

ACTION: None.

M1008 New Node Route Group <ext>: <status>FIELDS: ext The extension of the node route group that was automatically created by the network status

module.

status The status of the node route group creation.

CAUSE: This message indicates that the network status module has not created the node trunk group list.

ACTION: None.

M1009 Station <id> Moved from <b.p.d> to <b.p.d>FIELDS: id Node and extension of the station that moved ports.

b.p.d The board/port/device designation of the station the extension moved from.

b.p.d The board/port/device designation of the station the extension moved to.

CAUSE: This message indicates a station was moved from one port to another. The administrator has the capability to swap stations to help with AMCs (Adds/Moves/Changes). This is just to notify that it happened correctly. System OAI also has the capability to swap stations.

ACTION: None.



M1010 Node <num> Refused to Start a New Import Session – <reason>

FIELDS: num Node number from which this node was trying to import.

reason The reason the import failed (Database Programming, Phone Programming, OAI Programming, Voice Processor down, or No Response).

CAUSE: This message indicates that someone running Database Programming on a remote node started an import of device information from this node, or someone running Database Programming on this node has started an export of device information to a remote node. The import/export cannot continue because a programming session is taking place, the Voice Processor is not connected, or the remote node simply did not respond.

ACTION: End the programming session that is preventing the import/export and try again. In the case of a No Response, confirm all network connections.

FSACTION: This is almost always caused by a user being logged into Database Programming on the node that is not performing the import/export. Ask the technician to confirm that no Database Programming sessions are in progress.

M1011 Delayed Major Reset <status>: <reason> <subreason> (Axxess Only)

FIELDS: status Scheduled or Disabled. Indicates if the delayed major reset was just scheduled or disabled.

reason For "Scheduled," the reason it was scheduled. For "Disabled," the reason it was originally scheduled.

subreason For delayed major resets involving database changes, a numeric value is given for the specific type of database change.

CAUSE: This message indicates that someone made a change to the database that resulted in the scheduling or disabling of a delayed major reset.

ACTION: None. This message is for information purposes only.

M1012 Software License LoadedFIELDS: None.

CAUSE: A software license was successfully loaded onto the system.

ACTION: None.

M1013 CPU Type Change from <old> to <new>FIELDS: old The CPU type before the change.

new The CPU type after the change.

AXXESS CAUSE: A software license that caused the CPC CPU type to change was successfully loaded onto the system.

5000 CAUSE: This message indicates that a software license was successfully loaded into the system that caused the Mitel 5000 family to change from or to CS-5200 or CS-5400 (or other flavors).

ACTION: None.



M1014 DB Backup Rescheduled Due to Lock <lock_type>FIELDS: lock_type The entity that locked the database. Possible values include DB_PROGRAMMING,

KEYSET_PROGRAMMING, OAI_PROGRAMING, and EXPORT_PROGRAMMING.

CAUSE: The flash database save did not occur because the database is currently locked. The system will attempt to save the flash database again in five minutes.

ACTION: None.

M1015 DB Backup Save: <status>FIELDS: status Indicates one of the following:

x Successful: The database save was successful.

x No Changes: The database save was not necessary because there were no changes.

x Exceeded Re-try Attempts: The database save was not completed because it exceeded the number of re-try attempts.

x Save Disabled: The database save was not completed because the save feature is disabled.

x Failed Save: The database save failed.

CAUSE: A backup database save resulted in the indicated message.

ACTION: None.

M1016 DB Backup Restore: <status>FIELDS: status Indicates one of the following:

x Successful: The database restore was successful.

x Incomplete Restore: The backup database was not completely restored.

x Exceeded Re-try Attempts: The database restore was not completed because it exceeded the number of re-try attempts.

x Incompatible: The database restore was not completed because the database version was incompatible with the Call Processing version.

CAUSE: A backup database restore resulted in the indicated message.

ACTION: None.

M1017 Product Type Set to <product> (Axxess Only)FIELDS: product Indicates the new product type either Axxess or Eclipse.

CAUSE: The user logged into Database Programming when the system had an invalid or missing Software License. Database programming prompts the user to choose between Axxess or Eclipse. This message indicates the selection the user chosen.

ACTION: If the user selects the wrong product type, default the database via Database Programming and log back into the system to be re-prompted for the product type. Another way is to update a Software License that has the correct product type.

M1018 Bypassing DB Backup Restore (Axxess Only)FIELDS: None.

CAUSE: Someone pressed the * button while the system was powering up. This is an extreme method to bypasses the DB backup restore if the system is stuck in an infinite loop of DB backup restores.

ACTION: If the system was in an infinite loop of DB backup restores and the * button had to be pressed during power up, Mitel Engineering needs to get a copy of the DB backup database to determine why the system is in this state.



M1019 New Node IP Connection Group: <ext>FIELDS: ext The extension of the Node IP Connection Group automatically created by the network status

module.

CAUSE: The network status module has successfully created the node IP connection group.

ACTION: None.

M1090 Using Default Voice Mail ApplicationFIELDS: None.

AXXESS CAUSE: The Voice Processing Unit Application Table stored on the voice processing unit computer does not match the Voice Processing Application Table stored in the CP software. In other words, CP thinks voice processing extension numbers exist that the voice processing unit does not know about. Most likely a database restore caused the problem. You will see the message when you make a call to the voice processing.

5000 CAUSE: This message is common for Unified Voice Messaging and external voice mail connections. The Voice Processing Unit Application Table stored in the UVM does not match the Voice Processing Unit Application Table stored in the CP software. In other words, CP thinks voice processing unit extension numbers exist that the UVM or external voice mail does not know about. Most likely a database restore caused the problem. You will see the message when you make a call to the UVM or external voice mail.

ACTION: This error should no longer occur because the system and voice processing now always synchronize their tables whenever they connect. If this does occur, save the database with the voice processor connected and send any applicable voice processor logs that may help diagnose the problem. Send the report the problem to Mitel Field Service.


M1091 Voice Processing Unit <error>: <message>FIELDS: error Error number presented by the voice processing unit.

message Generic message generated by the voice processing unit.

CAUSE: This message is provided to give Voice Processing a mechanism for outputting informational messages. Refer to the Voice Processing Diagnostics Manual (part no. 550.8019) Alarm 216.

ACTION: Depends on the message.


M1092 <network group extension> Changing its Peer-to-Peer Value to <value>

FIELDS: network group extension This network group is changing its peer-to-peer audio flag based on an update from another node.

value This is the new value of the Network Group’s Peer-to-Peer flag.

CAUSE: Either an import or remote change to the network group has caused the value to change.

ACTION: None, if the change was expected. If unexpected, then the value should be checked and changed accordingly.



M1093 IP Phone <id> Moved from Board <b1> to <b2>AXXESS FIELDS: id Node and Extension of the IP Phone that moved to another IPRC.

b1 The board designation of IP Phone it moved from.

b2 The board designation of IP Phone it moved to.

5000 FIELDS: id Node and Extension of the IP Phone that moved to another IPRA.

b1 The IPRA (7) designation of IP Phone it moved from.

b2 The IPRA (7) designation of IP Phone it moved to.

AXXESS CAUSE: This message indicates an IP Phone was moved from one IPRC to another from Database Programming.

5000 CAUSE: This message indicates an IP Phone was moved from one IPRA to another from Database Programming.

ACTION: None.

System Messages (M0001–M9999): Hardware Informational Messages (M2000–M2999)


Hardware Informational Messages (M2000–M2999)Informational messages regarding the hardware or configuration of the hardware. Typically does not affect normal system operation. No action required.

M2000 Board <brd> was Reset by IOCAXXESS FIELDS: brd Number of the board that was reset.

5000 FIELDS: brd Number of the module or internal application that was reset.

AXXESS CAUSE: The IOC sends this message whenever it resets a peripheral board. This message is merely informational and is usually accompanied by one of the IOC error messages. This message tells us that software reset the board and some sort of hardware glitch did not occur.

5000 CAUSE: The system sends this message whenever it resets a module or internal application. This message is merely informational and is usually accompanied by one of the system error messages. This message tells us that software reset the module and some sort of hardware glitch did not occur.

AXXESS ACTION: Look at accompanying IOC error message(s); otherwise, none.

5000 ACTION: Look at accompanying system error message(s); otherwise, none.

M2001 Board <brd> (Card ID) <cid> Recovered from Exception Processing (Axxess Only)

FIELDS: brd Number of the board that recovered.

cid Card ID of the board that recovered.

CAUSE: The IOC sends this message to indicate that the specified board recovered from exception processing. That is, the board stopped responding to the IOC at some point; then, after sending the board a minor reset command (during exception processing), the board became operational once again.

ACTION: Look at accompanying IOC error message(s); otherwise, none.

M2002 <b.p.d>: On-Line from <device>; <b.p.d>: Off-Line from <device>

FIELDS: b.p.d The board/port/device designation of the device that went on line or off line.

device This is the name of the device.

CAUSE: The system receives an on-line notification whenever a device completes its power-up sequence. The system receives an off-line notification whenever a device is no longer available (e.g., device is unplugged).

ACTION: None.

M2003 <b.p.d>: OMSCI Version <version> for <board> (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the device that went on line or off line.

version The OMSCI version number.

board This is the name of the board.

CAUSE: The system receives an OMSCI version number whenever an analog phone board comes on-line. This applies only to the analog phone card.

ACTION: None.



M2004 <text> from ASAI Device on Logical Port <log_port> (Axxess Only)

FIELDS: text Text describing the message received from the ASAI device

log_port Logical port of the serial port connected to the ASAI device.

CAUSE: CP received a message of interest from the ASAI device. For example, "On-Line" and "Off-Line".

ACTION: None.

M2005 <b.p.d>: <message> from DSS/PKM <x>FIELDS: b.p.d The board/port/device designation of the DSS/PKM unit.

message Current status of the device (Offline, Online, Out of Range Online Error, or Online Error).

x The number of the device (1-2 for PKMs, 1-4 for DSSs) relative to its proximity to the phone in the daisy chain. Device number 1 is closest to the phone.

CAUSE: The system receives one of the following status notifications for a DSS or PKM unit:

x Offline: The device is no longer available (e.g., unplugged from the phone, lost power, phone unplugged).

x Online: The device has come online.

x Out of Range Online Error: An error was generated when the device attempted to register with Call Processing.

x Online Error: An internal Call Processing error was generated when the device attempted to come online.

ACTION: If the DSS/PKM should be online but is not, check each of the causes to determine the source of the problem. Otherwise, no action required.

M2006 <b.p.d>: Power-Up from <device> <power-up-data>, <major-version>, <minor-version>

FIELDS: b.p.d The board/port/device designation of the device that generated the power-up information.

device The type of the device that generated the power-up information.

power-up-data Contains the power-up data.

major-version Contains the major version number.

minor-version Contains the minor version number.

CAUSE: The system receives power-up information whenever an phone or SL set completes its power-up sequence.

ACTION: None.

M2007 <b.p.d>: Power-Up from DSS <x>: Version = <v>FIELDS: b.p.d The board/port/device designation of the DSS unit that generated the power-up

information.

x The number of the DSS unit.

v The version number of the DSS unit.

CAUSE: The system receives power-up information whenever a DSS completes its power-up sequence.

ACTION: None.

NOTE Programmable Key Modules (PKM) are supported on the Mitel 5000 only.



M2008 <action> from <client> Client on IP Port <port>FIELDS: action Text describing the message received from the client

client Text describing the client associated with the socket

port IP Port number of the socket connected to the client.

CAUSE: CP received a message of interest from the socket client. For example, "Log-In" and "Log-Out".

ACTION: None.

M2010 <b.p.d>: Redundant On-Line from DSS <x>FIELDS: b.p.d The board/port/device designation of the DSS unit that generated the redundant on-line.


CAUSE: A DSS unit is having problems due to a software or hardware error. However, this is a minor error and the system should continue to function normally.

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.


M2011 <b.p.d>: On-Line from DSP <d>: BP = <bp>, VSN = <v1>.<v2>, INFO = <info>

FIELDS: b.p.d The board/port/device designation of the board that is generating a DSP on line.

d The number of the DSP that is coming on line.

bp The boot page number field identifies the currently active DSP Boot Page.

v1 The major version number field identifies the current major version of the DSP code.

v2 The minor version number field identifies the current minor version of the DSP code.

info This information field defines the DSP processor type and its crystal speed.

CAUSE: The system receives an on-line notification whenever the DSP Processor completes its power-up sequence with the DSP chip. This message indicates that the DSP is powered up and ready to go.

ACTION: None.

M2012 <b.p.d>: Off-Line from DSP <d>FIELDS: b.p.d The board/port/device designation of the board that is generating a DSP off line.

d The number of the DSP that is going off line.

AXXESS CAUSE: The system receives an off-line notification whenever the DSP Processor resets and initiates a power-up sequence. This message indicates that the DSP is unavailable. This message also occurs if the OPC board on which the DSP resides goes off line.

5000 CAUSE: The system receives an off-line notification whenever the DSP Processor resets and initiates a power-up sequence. This message indicates that the DSP is unavailable.

AXXESS 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 by powering off and powering back on. If the DSP still remains off line, make sure the DSP chips and DSP PAL are properly seated in their sockets. If the DSP still doesn't come on line, replace the problem board, and send the faulty board to Field Service for analysis of this problem.



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.

M2013 <b.p.d>: Could Not <operation> Logical Port Ext <eeeee>Reason: <why> (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the device that has encountered the logical port error.

operation The logical port operation (e.g., allocate, deallocate, open, close, clear, configure).

eeeee the extension number of the logical port.

why The OS executive request return status code.

CAUSE: Normally, this is the result of a bad logical port number, a bad board, a non-existent board, or a different board other than what is programmed.

ACTION: Verify the programming to make sure the board is correct, and port exists for that card.

M2014 <b.p.d>: Logical Port Ext <eeeee> <operation> (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the device that has encountered the logical port success.

eeeee the extension number of the logical port.

operation the logical port operation (e.g., allocated, deallocated, opened, closed, cleared, configured).

CAUSE: None.

ACTION: None.

M2015 <b.p.d>: Could not <operation> I/O Channel (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that has encountered the I/O channel

error.

operation The I/O channel operation (e.g., allocate, deallocate, open, close, clear, configure).

CAUSE: Normally, this is the result of a bad logical port number, a bad board, a non-existent board, or a different board other than what is programmed.

ACTION: Verify the programming to make sure the board is correct, and port exists for that card.

M2016 <b.p.d>: I/O Channel <operation> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that has encountered the I/O channel

success.

operation the I/O channel operation (e.g., allocated, deallocated, opened, closed, cleared, configured).

CAUSE: None.

ACTION: None.



M2017 <b.p.d>: <type> Response Queue <operation> (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the device issuing the message.

type the response queue type (DSS or DTI).

operation the response queue operation (e.g., clear, flush, enqueue, dequeue, post timer, repost timer).

CAUSE: These messages are generated by the response queue logic of call processing's hardware devices. They are debug messages that relay queue operations.

ACTION: None. The messages should not occur in any field releases (Beta or Production).

M2018 <b.p.d>: <type> Response Queue Size <size> Bytes (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the device issuing the message.

type the response queue type (DSS or DTI).

size the size of the response queue in bytes.

CAUSE: These messages are generated by the response queue logic of call processing's hardware devices. They relay the size of the queue whenever a response is enqueued.

ACTION: None. These never occur in any field releases (Beta or Production).

M2020 Loopback Test Timed Out on <board_type> <b.p.d>FIELDS: board_type A string specifying whether this is a T1 or E1.

b.p.d The board/port/device where the timeout occurred.

AXXESS CAUSE: The user had requested a loopback test and had not cancelled the test before the Loopback Timeout timer expired. The card has terminated the loopback test.

5000 CAUSE: The user had requested a loopback test and had not cancelled the test before the Loopback Timeout timer expired. The T1/E1 module has terminated the loopback test.

AXXESS ACTION: None. If the T1 card was busied out, the T1 Busy-out Switch Timeout timer is registered and may expire soon.

5000 ACTION: None.

M2021 <b.p.d>: Downloading Latest Firmware VersionAXXESS FIELDS: b.p.d The board/port/device designation of the board that is being downloaded to.

version The image version that is being downloaded.

5000 FIELDS: b.p.d The board/port/device designation of the device that is being downloaded to.

version The image version that is being downloaded.

AXXESS CAUSE: The firmware on the board needs to be updated to the correct version. The board is most likely a PRI board. The board will now be re-programmed with the latest firmware version and will come back on-line after the download is completed.

5000 CAUSE: The firmware on the device needs to be updated to the correct version. The device is most likely a Model 8528 or 8568 phone. The device will now be re-programmed with the latest firmware version and will come back on-line after the download is completed.

AXXESS ACTION: If the board does not come back online, pull the board out and plug it back in. If the download is still unsuccessful, try downloading the latest firmware via the Upload Utility. If the board does not come back online, contact Mitel Technical Support.

5000 ACTION: If the device does not come back online within 5 minutes, unplug the device and plug it back in. If the device still does not come back online, contact Mitel Technical Support.



M2022 <b.p.d>: Downloading Latest Firmware Version CompletedSuccessfully (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the board that was downloaded to.

CAUSE: The firmware on the board was updated to the correct version. The board is most likely a PRI board. The board is now re-programmed with the latest firmware version and will come back on-line after the download is completed.

ACTION: If the card does not come back on-line, pull the card out and plug it back in. If the download is still unsuccessful, try downloading the latest firmware via the Upload Utility. If the card does not come back on-line, contact Mitel Field Service.

M2023 <b.p.d>: Skipping Boot-Code Download (Axxess Only)FIELDS: b.p.d The board/port/device designation of the board targeted for a download.

CAUSE: The firmware on the board aborted the boot-code download for some reason. Usually, it's OK if the card aborts the boot code because the boot code rarely needs an update. If there is a reason why the firmware needed the boot-code update, it sends another message after this one that better describes the error that occurred. The purpose of this message is to log the fact that the download didn't occur.

ACTION: Allow the download of the card-specific image to progress and finish (i.e., the LEDs will continue to toggle). If the card does not come back on-line after the download, pull the card out and plug it back in. If the card still does not come back on-line, contact Mitel Field Service.

M2024 <b.p.d>: Skipping Card-Specific Code Download (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the board targeted for a download.

CAUSE: The firmware on the board aborted the download of the card-specific code for some reason. The firmware will send an additional message indicating the specific reason for the abort. The purpose of this message is to log the fact that the download didn't occur.

ACTION: If the card does not come back on-line, pull the card out and plug it back in. If the card still does not come back on-line, contact Mitel Field Service. Additional messages in the message print output might offer additional insight into the problem.

M2025 Card <card> Fully Busied Out (Axxess Only)FIELDS: card The decimal card number that is fully busied out

CAUSE: The user had requested that a card busy itself out, either via an Applications programming request or by pressing the busy-out button. The system was able to fully busy out all devices on the card (i.e., no device was in use).

ACTION: None.

M2026 The Make-Busy Switch Timed Out on Card <card> (Axxess Only)

FIELDS: card The decimal card number that the busy switch timed out on

CAUSE: The user had requested that a card busy itself out, either via an Applications programming request or by pressing the busy-out button. The system was able to busy the card out. However, the Busy-Out Switch Timeout timer expired.

ACTION: Press the busy-out switch on the card to turn off the busy-out LED.



M2027 <b.p.d>: Received Off-Line During Code Download (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the board targeted for a download

CAUSE: The board went off-line for some reason (e.g., the user removed the board from the card slot) while a code download was in progress.

ACTION: If the user caused the off-line (e.g., removing the board from the card slot), no action is required. Otherwise, the board itself may be bad. If the board causes further problems, contact Mitel Field Service.

M2028 <b.p.d>: Initializing Board’s Companding Mode to <mode> FIELDS: b.p.d The board/port/device designation of the board that is initializing its DSP companding

mode

mode Either A-Law (US Standard) or Mu-Law (International Standard)

CAUSE: The system sets the companding type of the DSP on that board. The system determines how it should be set by the system-wide companding flag

ACTION: If the user caused the off-line (e.g., removing the board from the card slot), no action is required. Otherwise, the board itself may be bad. If the board causes further problems, contact Mitel Field Service.

M2029 <address>: Device Busied OutFIELDS: address The hardware address of the device that is busied out.

CAUSE: The user had requested a busy-out operation and this device has now entered the busy-out state.

ACTION: None.

M2030 SLC16 48-Volt Power Supply Recovered on Board <board> (Axxess Only)

FIELDS: board The decimal board number that the power supply has recovered on.

CAUSE: The 48 volt power supply on the indicated card had previously failed, and now has recovered.

ACTION: None.

M2031 SLC16 72-Volt Power Supply Recovered on Board <board> (Axxess Only)

FIELDS: board The decimal number of the board that the power supply has recovered on.

CAUSE: The 72-volt power supply on the indicated card had previously failed, and now has recovered.

ACTION: None.

M2032 OS Info on <board_type> <b.p.d>, Additional Info: <data> (Axxess Only)

FIELDS: board_type A string specifying if the card is a CPU type card.

b.p.d The board, port, and device numbers of the card that is sending the information.

data One to six bytes of additional data (engineering use only).

CAUSE: This informational applies only to a Call Processing Server. The software on the card may have detected an error condition during a reset and has reported the problem. Depending on the severity of the problem, calls on the card may or may not have been affected.

ACTION: No action is required unless the data indicates a bus error on the operating system.



M2033 OS Version for CPU <cpu_number> is <version_string> (Axxess Only)

FIELDS: cpu_number A non-zero integer indicating the CPU to which this message applies.

version_string Indicates the version of the CPU. This message uses the format [x.y.z] where x is the CP version, y is the OS version, and z is the minor version.

CAUSE: This informational applies only to a Call Processing Server. No action is required unless an M5134 message follows.

ACTION: None.

M2034 On-Line from VoIP DSP(s) <numberstart>–<numberend> on Board <board>

FIELDS: numberstart The first IP resource number.

numberend The last IP resource number.

board The board from which the IP resource(s) powered up on.

AXXESS CAUSE: The system receives an on-line notification whenever the DSP Processor completes its power-up sequence with the DSP chip. This message indicates that the DSP is powered up and ready to go.

5000 CAUSE: The system receives an on-line notification as the IPRA (either 7 or 9) comes on-line. This message indicates that additional IP resources are available for networking, SIP/MGCP trunking, or IP phones.

ACTION: None.

M2035 Off-Line from VoIP DSP <numberstart>–<numberend> on Board <board>

FIELDS: numberstart The first IP resource number.

numberend The last IP resource number.

board The board from which the VoIP DSP powered up on.

AXXESS CAUSE: The system receives an off-line notification whenever the DSP Processor resets and initiates a power-up sequence. This message indicates that the DSP is unavailable. This message also occurs if the IPRC board on which the DSP resides goes off line.

5000 CAUSE: The system receives an off-line notification whenever the IPRA shuts down. This message indicates that the IP resources are now unavailable.

AXXESS 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, Mitel recommends 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 by powering off and powering back on. If the DSP still remains off line, make sure the DSP chips and DSP PAL are properly seated in their sockets. If the DSP still does not come on line, replace the problem board and send the faulty board to Field Service for analysis.

5000 ACTION: Normally, the IP Resource will go off-line before coming on-line. Verify that the IP Resource has come on-line. However, if some problems have occurred which cause the IPRA 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 IP resources still do not come on line contact Field Service for analysis of this problem.



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.

M2036 Established IP LINK to Node <num>FIELDS: num The number of the node to which this node established an IP link.

CAUSE: The system is programmed for private networking over IP and successfully established an IP link to a remote node.

ACTION: None. The system is behaving properly unless it is not programmed for IP networking.

M2037 Closed IP LINK to Node <num> – Reason <reason> <string>FIELDS: num The number of the node to which this node had an IP link that was closed.

reason The reason why the session was closed.

string We translated the reason to its definitions.

CAUSE: The system is programmed for private networking over IP and closed an IP link to a remote node.

ACTION: If a node or IP connection was just removed from the system, this indicates proper operation. Otherwise, verify network connectivity.

AXXESS FS ACTION: This message usually occurs only when somebody disconnects a network connection or changes network programming. Verify private network programming and use “ping” commands from a computer on the IP network to verify network connectivity. Use the “ping” command on the IPRC to verify that the IPRCs have visibility to each other.

5000 FS ACTION: This usually occurs only when somebody disconnects a network connection or changes network programming. Verify private network programming and use “ping” commands from a computer on the IP network to verify network connectivity. Use the “ping” command from an IP device on the network to verify the Processor Modules/IPRCs (if networked to an Axxess system) have visibility to each other.

M2038 Failed Session Startup with Node <num>FIELDS: num The number of the node with which this node attempted to start an IP session and failed.

CAUSE: The system is programmed for private networking over IP but was unable to establish a session with the remote node.

ACTION: Verify private network programming between the two nodes. In particular, verify the IP address, the port numbers, and the P6XXX extension numbers of the IP connections. Verify network connectivity and the absences of firewalls and NATs.

FSACTION: If a network has already been connected, this generally only happens when something changes the network topology (changes an IP address, unplugs a cable, installs a firewall or NAT, etc.). For a newly installed network, the most common error is to incorrectly program the P6XXX extension numbers of the IP connections by not making them unique identifiers. Firewalls and NATs will also prevent sessions from starting properly.



M2039 Dead Socket Response from Node <node_num>: Reason <code>, <code_string>

FIELDS: node_num The remote node to which the socket was connected, where 0 = no socket.

code The reason why the connection is lost.

code_string We translated the error code to its definitions.

AXXESS CAUSE: The system had a link to a remote node that was dropped at the IPRC level.

5000 CAUSE: The system had a link to a remote node that was dropped at the IPRA level

ACTION: Verify private network programming between the two nodes. In particular, verify the IP addresses, the port numbers, and the P6XXX extension numbers of the IP connections. Verify network connectivity and the absence of firewalls and NATs.

FSACTION: If a network has already been connected, this generally only happens when someone changes the network topology (changes an IP address, unplugs a cable, installs a firewall or NAT, etc.). For a newly installed network, the most common error is to incorrectly program the P6XXX extension numbers of the IP connections by not making them unique identifiers. Firewalls and NATs will also prevent sessions from starting properly.

M2040 CPC ‘*’ Button Pressed (Axxess Only)FIELDS: None.

CAUSE: Someone pressed the * button on the CPC, requiring Call Processing to acknowledge an “are you alive” message. If Call Processing does not respond to this message within 15 seconds, the system performs a minor reset.

ACTION: None.

M2041 CPC ‘*’ Button Acknowledged (Axxess Only)FIELDS: None.

CAUSE: Someone pressed the * button on the CPC, and Call Processing acknowledged the “are you alive” message.

ACTION: None.

M2042 Failed to Allocate a VoIP from Board <board>AXXESS FIELDS: board The board of the IPRC from which CP tried to allocate a VoIP.

5000 FIELDS: board The IPRA (7 or 9) from which CP tried to allocate a VoIP.

AXXESS CAUSE: Call Processing received a setup request or indication, and it tried to allocate a VoIP for the new networking call. There are no more VoIPs available; they are either being used by another call or marked as OUT OF SERVICE.

Before an IP phone could come on-line, Call Processing tried to allocate a VoIP for that phone. There were no more phone VoIPs available.

AXXESS ACTION: Call Processing will camp on to the Node Route Group and the phone will display a camp-on message. Make sure that the VoIPs are not marked as OUT OF SERVICE in Database Programming. At an administrator phone, dump the IP connection extension or VoIP to see if all the VoIPs are in use for calls. If all the VoIPs are being used for calls, the user will get the next available VoIP when one of the calls terminates.

For the phone, make sure there are enough phone IP resources 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 phone will get the next available IP resource when one of the calls terminates or an phone goes off-line.



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.

M2043 VoIP DSP <VoIP_DSP> on Board <board_num> is Unavailable Due to Insufficient Networking VoIP from License (Axxess Only)

FIELDS: VoIP_DSP Indicates the DSP number that did not come on-line.

board_num Indicates the board number where the DSP is located.

CAUSE: A VoIP DSP on-line message was received from the IPRC, but the total number of VoIP DSP resources on-line exceeds the limit prescribed by the license.

ACTION: Verify the number of networking VoIPs that the software license supports. Upgrade the license or reduce the number of equipped VoIPs on the card.

M2044 Session <session_id> is Closed Due to ErrorFIELDS: session_id The session that we are trying to close.

AXXESS CAUSE: Call Processing received an error code of 9 in the IP socket input close response from the IPRC due to bad descriptor for close-socket command.

5000 CAUSE: Call Processing received an error code of 9 in the IP socket input close response from the IPRA due to bad descriptor for close-socket command. The socket is already closed and CP tried to close it again.

ACTION: None.

M2045 <b.p.d>: <type> IP Address: <address> Hostname: <name>AXXESS FIELDS: b.p.d The board/port/device designation of the board that came on-line.

type Either IPRC or CPC.

address The IP address of the IPRC (either dynamic or static).

name The IPRC’s or CPC’s hostname.

5000 FIELDS: board The board/port/device designation of the board that came on-line.

type Processor Module or IPRA.

address The IP address of the IPRA (either dynamic or static for the Processor Module and always static for the Processor Expansion Module).

name The Processor Module’s hostname.

AXXESS CAUSE: The IPRC or CPC has just come on-line. The system shows the IP address and the hostname of the IPRC or CPC.

5000 CAUSE: The IPRA or Processor Module has just came on-line. The system shows the IP address and the hostname of the IPRA or Processor Module.

ACTION: None.



M2046 IP Connection <ext_received> Minor-Reset NotificationWhile Not On-Line (Axxess Only)

FIELDS: ext_received Extension of the IP connection.

CAUSE: The IPRC sent Call Processing a minor reset notification even through it is not on-line.

ACTION: None.

M2047 IP Connection <ext_received> Minor-Reset Notification (Axxess Only)

FIELDS: ext_received Extension of the IP connection.

CAUSE: The IPRC sent Call Processing a minor reset notification because the IPRC experienced a minor reset due to an error or it was unplugged and plugged from the slot quickly.

ACTION: None.

M2048 Device <address> Unbusied Out FIELDS: address The hardware address of the device that is unbusied out.

CAUSE: The user had requested that a device be unbusied, and this device has now entered the idle state.

ACTION: None.

M2049 <ext>: Application Data and Control <conn> From <device>FIELDS: ext The extension of the device that its SAC (application data and control) connection got

connected or disconnected.

conn Connected or Disconnected

device This is the name of the device.

CAUSE: The system receives a connected or disconnected notification whenever the device's SAC connection has changed.

ACTION: None.

M2050 Serial Input Queue Overflow – Character Ignored (Axxess Only)

FIELDS: None.

CAUSE: A serial port input queue in the Operating System was full and another character was entered. There was no room to store the character, so it had to be ignored. This will only happen in an abusive situation such as pounding on a keypad or keyboard.

ACTION: No action need be taken, unless a user complains of having experienced a situation in which an input was ignored. In that case, simply explain to the user that they were pressing the keys so fast that the system couldn't keep up, that they were, in fact, abusing the system.

M2094 CP Time Changed for Daylight Saving Time FIELDS: None.

CAUSE: The system time changed because of Daylight Saving Time.

ACTION: No action required.



M2095 <b.p.d>: Automatically Enabled Premium Feature: <feature>(Axxess Only Pre v8.0)

FIELDS: feature The name of the Premium Feature that was automatically enabled

CAUSE: The system automatically enabled the indicated premium feature because a board that required the premium feature was automatically equipped.

ACTION: No action required, unless the installer does not want this premium feature enabled. The installer must use Database Programming to disable the premium feature.

M2096 <b.p.d>: Automatic Equip of <board> SuccessfulAXXESS FIELDS: b.p.d The board/port/device designation of the board that automatically equipped

board The board type of the board that automatically equipped

5000 FIELDS: b.p.d The board/port/device designation of the module that automatically equipped

board The type of module that automatically equipped

AXXESS CAUSE: The system successfully automatically equipped/upgraded the board when it was inserted into the system.

5000 CAUSE: The system successfully automatically equipped the module when it was inserted into the system.

AXXESS ACTION: No action required, unless the installer does not want the board equipped. The installer must use Database Programming to unequip the board.

5000 ACTION: No action required, unless the installer does not want the module equipped. The installer must use Database Programming to unequip the module.

M2097 System Reconfigure in Progress (Axxess Only)FIELDS: None.

CAUSE: The system has started the reconfiguration process. A system reconfigure queries the IOC about what boards are in the system, and forces off line any boards that have been removed. Then, the system processes all pending messages into CP, including any waiting hardware inputs. Finally, the system refreshes the status of all boards and devices. A system reconfigure is typically due to someone pressing the reset button on the front of the CPU board. This is part of normal system operation. It is possible a hardware problem causes this problem, but it would be extremely rare.

ACTION: If the problem occurs repeatedly and is not due to someone pressing the reset button, replace the CPU board.

M2098 System Reconfigure Complete (Axxess Only)FIELDS: None.

CAUSE: The System Reconfigure (see M2097 above) is complete. The physical hardware devices and boards should now be in sync with the CP software, including voice channel connections.

ACTION: None.

NOTE

Shortly following this message, the system will print out M2098 System Reconfigure Complete. If there is a problem with the reconfigure, the “Complete” 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.



M2099 <card> Real-Time Clock Stopped but Now Running (Axxess Only)

FIELDS: card The name of the card that the Real-Time Clock resides on. For Axxess, this will be CPU020. For AXXENT, this will be ACM.

CAUSE: Previously, the Operating System detected that the Real-Time Clock was not running. Now, however, the Operating System has detected that the Real-Time Clock IS running.

ACTION: Check the system time and date. If it is incorrect, set it to the proper time and date. As indicated for the alarm that is reported when the Real-Time Clock initially fails, however, it is still necessary to replace the CPU020 or ACM board. Return the faulty CPU020 or ACM board to Mitel for diagnosis and repair. Make sure that the temporary Real-Time Clock failure is reported.

M2100 Timed-Out Waiting for a Ring Input on DI Circuit <b.p.d>FIELDS: b.p.d the board/port/device of the trunk that timed-out waiting for a ring input.

CAUSE: This error is only for Loop-Start trunks configured for Japan DI service. This error indicates that the Loop-Start trunk timed-out on an incoming call waiting for the Central Office to ring the trunk. In this case, the trunk returns to an idle state where it is available for making an outgoing call or receiving and incoming call.

ACTION: Either increase the DI Ring DTMF Wait timer or have the Central Office decrease their timer.


M2101 IPRC PAL Ignored on Board <board> (Axxess Only)FIELDS: board The IPRC board that sent Call Processing the PAL information.

CAUSE: The installed IPRC has a PAL attached that is being ignored. IPRC networking/station PALs are no longer supported in Call Processing version 9.0 or later. If the license does not have any networking VoIPs available, the installer will not be able to program any networking VoIPs on the IPRC or make networking calls. From the diagnostic monitor, dump the VoIP DSP Manager under Resource Manager to verify the number of networking VoIPs available in the system.

ACTION: None.

M2102 PIN Registration Successful For <new MAC address> on <extension>

FIELDS: new MAC address: This is the MAC address of the newly-registered IP phone.

extension: The extension to which the new IP phone is registered.

CAUSE(S): A user registered an IP phone with the given MAC address to the extension shown using the system registration PIN.

ACTION: None.

M2103 PIN Replacement Of <old MAC address> Successful for<new MAC address> on <extension>

FIELDS: old MAC address: This is the replaced MAC address.

new MAC address: This is the MAC address of the newly-registered IP phone.

extension: The extension to which the new IP phone is registered.

CAUSE(S): A user replaced the MAC address of an IP phone with the given MAC address to the extension shown using the system replacement PIN.

ACTION: None.

System Messages (M0001–M9999): Engineering Informational Messages (M3000–M3999)


Engineering Informational Messages (M3000–M3999)Informational messages regarding internal Engineering issues, such as minor software errors or inconsistent device states. These messages typically do not affect normal system operation. No action required.

M3000 MAJOR RESET: Power-Up FIELDS: None.

CAUSE: The system was powered up.

ACTION: None.

M3000 Minor Reset: Reset Button (Axxess Only)FIELDS: None.

CAUSE: Someone pressed the reset button.

ACTION: None.

M3000 Minor Reset: OS Detected Software ErrorFIELDS: None.

CAUSE: The OS detected a serious software error, causing the system to go through a minor reset.

ACTION: Record as much information as possible about the events that preceded the minor reset. Use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.

FSACTION: Report the problem to the engineering contact person for further analysis. Provide a valid CP Error Information freeze and the database.

M3000 MAJOR RESET: OS Detected Software ErrorFIELDS: None.

CAUSE: The OS detected a serious software error that caused the system to perform a major reset and drop all calls.

ACTION: Record as much information as possible about the events that preceded the minor reset. Use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.


M3000 MAJOR RESET: Watchdog Expired During OS MAJOR Reset Process

FIELDS: None.

CAUSE: A Watchdog interrupt occurred during a major reset, causing another major reset to occur. The watchdog is present to prevent the system from "locking up" indefinitely. The watchdog should not expire during the major reset processing. If it does, there is a software error or serious database error that is messing up the system.

AXXESS ACTION: The system is probably in a continuous series of major resets. Cycle power. If the system comes up, perform the steps indicated below. If the system fails to come up, default the database by removing the battery-backed RAM jumper for at least 30 seconds with the power is off. If the still system fails to come up, remove all other boards except the CPU board. If the system still fails to come up, replace the CPU board. 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.



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.

M3000 MAJOR RESET: Watchdog Expired During OS Minor Reset Process

FIELDS: None.

CAUSE: A Watchdog interrupt occurred during a minor reset, causing a major reset to occur. The watchdog is present to prevent the system from "locking up" indefinitely. The watchdog should not expire during the minor reset processing. If it does, there is a software error or serious database error that is messing up the system.

AXXESS ACTION: If the system is operational, perform the steps indicated below. If the system fails to come up, remove all the boards except the CPU board and cycle power. If the system still fails to come up, default the database by removing the battery-backed RAM jumper for at least 30 seconds with the power is off. If the system still fails to come up, replace the CPU board. 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.






M3000 MAJOR RESET: Watchdog Expired During User Task MAJOR Reset Process

FIELDS: None.

CAUSE: A Watchdog interrupt occurred during a major reset, causing another major reset to occur. The watchdog is present to prevent the system from "locking up" indefinitely. The watchdog should not expire during the major reset processing. If it does, there is a software error or serious database error that is messing up the system.

AXXESS ACTION: The system is probably in a continuous series of major resets. Cycle power. If the system comes up, perform the steps indicated below. If the system fails to come up, default the database by removing the battery-backed RAM jumper for at least 30 seconds with the power is off. If the system still fails to come up, remove all other boards except the CPU board. If the system still fails to come up, replace the CPU board. 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.




M3000 MAJOR RESET: Watchdog Expired During User Task MinorReset Process (Axxess Only)

FIELDS: None.

CAUSE: A Watchdog interrupt occurred during a minor reset, causing a major reset to occur. The watchdog is present to prevent the system from "locking up" indefinitely. The watchdog should not expire during the minor reset processing. If it does, there is a software error or serious database error that is messing up the system.

ACTION: If the system is operational, perform the steps indicated below. If the system fails to come up, remove all the boards except the CPU and cycle power. If the system still fails to come up, default the database by removing the battery-backed RAM jumper when the power is off. If the system still fails to come up, replace the CPU board. If the system comes back up, restore a saved version of the customer's database and report the incident to Mitel Field Service. 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.

FSACTION: 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.



M3000 MAJOR RESET: User Task Detected Software ErrorFIELDS: None.

CAUSE: A task requested a reset.

ACTION: 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.


M3000 Minor Reset: User Task Detected Software ErrorFIELDS: None.

CAUSE: A task requested a minor reset.

ACTION: 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.


M3000 MAJOR RESET: Delayed from Minor ResetFIELDS: None.

CAUSE: A delayed major reset occurred, scheduled because a minor reset took place in the previous 24 hours.

ACTION: If possible, determine the exact reasons why the minor reset occurred. Because the major reset is a delayed reset, the cause of the minor reset may no longer exist in the system history. However, there may be some information in the Message Logs that will help determine the cause of the problem. Record as much information as possible about the events that preceded the minor reset. Use Database Programming to save the database and obtain the System Error Information. Contact Mitel Field Service with this information.


M3000 MAJOR RESET: Delayed from System Reconfigure (Axxess Only)

FIELDS: None.

CAUSE: A delayed major reset occurred, scheduled because a system reconfigure took place in the previous 24 hours. A delayed major reset after a system reconfigure is part of normal system operation.

ACTION: None.

M3000 MAJOR RESET: Delayed from Database ProgrammingFIELDS: None.

CAUSE: A delayed major reset occurred, scheduled because Database Programming requiring a system reset took place in the previous 24 hours. The major reset after certain database changes is part of normal system operation.

ACTION: None.



M3000 MAJOR RESET: Delayed from Heap Near FullFIELDS: None.

CAUSE: A major reset occurred because software determined that the CP Heap was nearly used up.

ACTION: Notify Mitel Field Service. Also see Alarm A112 for additional information and steps to follow.


M3000 MAJOR RESET: Delayed from Heap CorruptionFIELDS: None.

CAUSE: A delayed major reset occurred, scheduled because the CP software detected that the heap was corrupted.

ACTION: Notify Mitel Field Service.


M3000 MAJOR RESET: Database Restore CompleteFIELDS: None.

CAUSE: A major reset occurred following the completion of a Database Restore Operation. This is the normal and expected result after doing a database restore.

ACTION: None.

M3000 MAJOR RESET: Database Programming Reset CommandFIELDS: None.

CAUSE: A major reset occurred in direct response to a request made through Database Programming.

ACTION: None.

M3000 MAJOR RESET: Database Programming Default Database Command

FIELDS: None.

CAUSE: A major reset occurred following the defaulting of the database in direct response to a request made through Database Programming.

ACTION: None.

M3000 MAJOR RESET: User Task Minor Initialization Failure (Axxess Only)

FIELDS: None.

CAUSE: A major reset occurred because four minor resets occurred within 60 seconds.

ACTION: Perform the following steps: 1. Perform a "Get CP Error Information" and a "Database Save". 2. Save the files created on a single diskette. 3. Record any other information available as to what precipitated the major or minor reset. 4. Notify field service of the problem and provide them with the diskette.

FSACTION: Report this problem to the Engineering Contact with the above information for analysis to determine the cause of this problem.

NOTE

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 unlikely that this message will occur because the system will probably reset before this message has a chance of printing.



M3000 Minor Reset: Battery-Backed Memory Full (Axxess Only)FIELDS: None.

CAUSE: A database change attempted to allocate more Battery-Backed Memory than was available.


FSACTION: Field Service should then report the problem to the engineering contact.

M3000 MAJOR RESET: Database Restore Connection LostFIELDS: None.

CAUSE: A major reset occurred because the connection to the Database Restore Programming Session was lost. The database will be set back to its default state when the system comes back up.

ACTION: Determine why the connection to the Database Restore Session was lost. Attempt to perform the database restore again with a working database connection.

M3000 MAJOR RESET: Delayed from Resource ReconciliationFIELDS: None.

CAUSE: A delayed major Reset occurred, scheduled because a Resource Reconciliation took place and failed in the previous 24 hours.

ACTION: None.

M3000 MAJOR RESET: Delayed from Database RequestFIELDS: None.

CAUSE: A user requested a delayed major reset from Database Programming.

ACTION: None.

M3000 MAJOR RESET: Major (or Minor) Reset Requestfrom Test Driver (Axxess Only)

FIELDS: None.

CAUSE: The automated test driver task requested the system to perform a major or a minor.

ACTION: None.

M3000 Minor RESET: Other Cabinet Pressed Reset Button (Axxess Only)

FIELDS: None.

CAUSE: Someone pressed the reset button on the slave cabinet in a Quad cabinet system.

ACTION: None.

M3000 MAJOR RESET: Other Cabinet Requested MAJOR Reset (Axxess Only)

FIELDS: None.

CAUSE: A task on the secondary cabinet requested the primary cabinet to perform a major reset. This could be due to someone explicitly entering a major reset command while in the slave's on-line monitor. Normally, this message occurs only on the slave side, when the primary cabinet does a major itself.

ACTION: None.



M3000 MAJOR RESET: Code ChangeFIELDS: None.

CAUSE: The code in the flash changed.

ACTION: None.

M3000 MAJOR RESET: Scheduled Delayed MajorFIELDS: None.

CAUSE: A delayed Major reset was scheduled in Database Programming.

ACTION: None.

M3000 MAJOR RESET: Low Battery on UPS FIELDS: None.

CAUSE: A shutdown occurred in direct response to a “Low Battery” notification from the connected UPS.

ACTION: None.

M3000 MAJOR RESET: Reset Due to Change in Mindspeed ECAN Option

FIELDS: None.

CAUSE: A shutdown occurred in direct response to a change in the Mindspeed ECAN Option Programming.

ACTION: None.

M3001 System History of Node <frozen_node> <Frozen/UnFrozen>from Node <freezing_node>

FIELDS: frozen_node Node number of the node that was frozen/unfrozen.

Frozen/UnFrozen Indicates whether the System History was frozen or unfrozen.

freezing_node Node number of the node that requested the freeze/unfreeze

CAUSE: Someone froze or unfroze the system from an external source, possibly Database Programming or the On-Line Monitor. As an example: Database Programming automatically freezes the System History when it requests the System History information. Database Programming unfreezes the System History after receiving all the information.

ACTION: None. This message is for informational purposes only.

M3002 System History of Node <frozen_node> <Frozen/UnFrozen> by Ext <eeeee> at Node <freezing_node>

FIELDS: frozen_node The node number that was frozen/unfrozen.


eeeee The extension that requested the freeze/unfreeze.

freezing_node The node number that requested the freeze/unfreeze.

CAUSE: The System History was frozen or unfrozen by an Administrator phone.




M3003 System History <Freeze/UnFreeze> of Node <node_num> Failed: Already <Frozen/UnFrozen>

FIELDS: Freeze/Unfreeze The operation that failed.

node_num Node number of node which was already frozen/unfrozen.


CAUSE: The System History was already frozen or unfrozen.


M3006 System in Use: Retrying Delayed Reset in 5 MinutesFIELDS: None.

CAUSE: The system is attempting to do a delayed major reset, but it cannot due to the system being in use. The system will try to reset itself again in 5 minutes. Several conditions can cause the delayed major reset to be registered, such as various Database Programming changes and a minor reset.

ACTION: Normally, the only action necessary is to allow the system to come to idle so it can reset itself. However, if some problems have occurred which cause internal structures to be out of synchronization, the system may think that it is busy, when in actuality it isn't. In this case, we recommend that a tech reset the system manually, using the Database Programming's Reset System command in the Save/Restore screen. If the system is in a state such that Database Programming cannot connect, reset the system manually by powering off and powering back on.

M3007 Call Processing Version: <version>FIELDS: version Indicates the current version of Call Processing.

CAUSE: The Diagnostic Mode toggle feature code was entered by an administrator or the system performed some sort of a reset.

ACTION: None.

M3008 <b.p.d>: Version Info for <board>: <string>AXXESS FIELDS: b.p.d The board/port/device designation of the device that went on line or off line.

board The name of the board which originated the message.

string The string sent by the PP.

5000 FIELDS: b.p.d The board/port/device designation of the device that went on line or off line.

board The name of the module which originated the message.

string The string sent by the module and/or application.

AXXESS CAUSE: The version information is automatically sent to Message Print when the following boards power up: T1/E1, T1/E1 PRI, BRU, BRS and IPRC. The version information may also be requested through internal diagnostics.

5000 CAUSE: The version info is automatically sent to Message Print when the following modules come on-line: T1/E1, T1/E1 PRI, BRI and IPRA. The version info may also be requested through internal diagnostics.

ACTION: None.

NOTE

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 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.



M3009 Retrieving System History InformationFIELDS: None.

CAUSE: The System History was requested through Database Programming.

ACTION: None.

M3010 <b.p.d>: Version Info for <board>: <data> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that went on line or off line.

board The name of the board which originated the message.

data The bytes sent by the PP.

CAUSE: The peek data info was requested through internal diagnostics.

ACTION: None.

M3011 Automatic Diagnostics Delivery <status>FIELDS: status The system reports the current ADD status of the ADD thread to the user.

CAUSE: The ADD process has changed states and the system is informing the user of current state. For example, if the thread is running and the system tries to start another thread of the same type, then we will report that the first thread must finish execution before the next one can start.

ACTION: None.

M3012 CPH Compression Status: <status>FIELDS: status The warning/error status regarding the CPS CPH zipping algorithm.

CAUSE: The system/user is trying to freeze the system while the system is currently zipping the freeze files. The system can only zip one CPS freeze at a time. This happens on a CPS and on the Mitel 5000 products.

ACTION: None.

M3050 BRI Trunk Port <b.p.d>: Registered SPID <spid>FIELDS: b.p.d The board/port/device designation of the BRI Trunk Port that successfully registered the

SPID.

spid The SPID that the Central Office registered.

CAUSE: The Central Office has successfully registered the SPID from the indicated BRI Trunk Port. The BRI Trunk Port is now ready to receive calls from the associated directory number.

ACTION: None.

M3051 Mailbox Resync <status>FIELDS: status These are the possible messages from the resync process: Started, Completed, Error:

String Not Terminated, Error: Invalid Digit, Error: Invalid Extension, Error: Ext Not Found, Error: Invalid Device Type.

CAUSE: Successful resynchronization will show “Started” and “Completed” messages. Any other statuses could indicate that the resync process failed.

ACTION: For error statuses, get a valid CP freeze of the mailbox, re-sync the process, save the database, and capture voice processor logs. To force the mailbox re-sync, make sure voice mail is connected and Database Programming is not connected. From an administrator phone, enter in feature code "9933#622444<spkr>". Mailbox information will come from message print along with the request to perform a mailbox re-sync. Report the resulting information to Mitel Field Service.



M3090 Input List OverflowFIELDS: None.

CAUSE: This could occur if someone pressed a lot of keys very quickly while on a call to the voice processing unit. The voice processing unit was not able to store all the key presses in time, and some of the key presses were lost.

ACTION: No action is necessary unless the condition persists. If the problem persists, get a CP freeze, save the database, and obtain voice processor logs. Then, contact Mitel Field Service.

M3091 Newer Code Image is Available (Axxess Only)FIELDS: None.

CAUSE: If the card is flash-programmable, but the code image is empty, this message informs the user that a newer code image is available.

ACTION: None.

M3092 Modem <modem> Reset by <device>FIELDS: modem The node and extension number of the modem that was reset.

device The node and extension number of the device that reset the modem.

CAUSE: Someone entered the Modem Reset feature code. When the modem resets, it drops all connected calls and is restarted. The modem is usually reset if the modem is locked.

ACTION: None.

M3093 Modem Connect – DSP <dsp>, Circuit <circuit>, RX/TX Speed <rx>/<tx>, Mod <modulation>

FIELDS: dsp The DSP associated with the modem.

circuit The circuit number of the modem.

rx The receive speed at which the modem connects.

tx The transmit speed at which the modem connects.

modulation The type of modulation at which the modem connects.

CAUSE: The modem has answered an incoming call from another modem.

ACTION: None.

M3094 Modem Retrain – DSP <dsp>, Circuit <circuit>, RX/TX Speed <rx>/<tx>, Mod <modulation>

FIELDS: dsp The DSP associated with the modem.


rx The receive speed at which the modem connects.

tx The transmit speed at which the modem connects.

modulation The type of modulation at which the modem connects.

CAUSE: Changing line conditions has allowed or forced the modem to modify the connection aspects of the call.

ACTION: None.



M3095 Modem Disconnect – DSP <dsp>, Circuit <circuit>FIELDS: dsp The DSP associated with the modem.


CAUSE: The call has ended, and the modem is disconnected.

ACTION: None.

M3096 Network Time Synchronization by Node <num> Ignored – NTP Synchronization Enabled

FIELDS: num Node number which sent the Synchronize Network Time Datagram.

CAUSE: NTP Synchronization Enabled on local node.

ACTION: None.

M3100 Network Group Diagnostics StartedFIELDS: None.

CAUSE: Someone entered the Network Group Diagnostics feature code from the administrator phone.

ACTION: None.

M3100 Network Group Diagnostics CompletedFIELDS: None.

CAUSE: The Network Group Diagnostics is complete.

ACTION: None.

M3101 Network Group Diagnostics has Detected Device <b.p.d> is Off-Line

FIELDS: b.p.d The board/port/device designation of the device that is off-line.

CAUSE: The Network Group Diagnostics feature has detected that a device is off-line.

ACTION: None.

M3102 Network Group Diagnostics Detected a Device Pair <b.p.d>and <b.p.d> Not Capable of Bidirectional Communication

FIELDS: b.p.d The board/port/device designation of the device that did not receive a response to the ping message or that did not respond to the ping message.

CAUSE: The Network Group Diagnostics feature has detected a device pair that cannot use P2P audio.

ACTION: Make sure the Network Group is programmed correctly and that the devices are not separated by NATs and firewalls.

M3103 Network Group Diagnostics Detected a Firewall/NATBetween Device Pair <b.p.d> and <b.p.d>

FIELDS: b.p.d The board/port/device designation of the device that initiated a ping or that did not respond to the ping.

CAUSE: The Network Group Diagnostics feature has detected a firewall or NAT between two devices in the same Network Group.

ACTION: Make sure the Network Group is programmed correctly and that the devices are not separated by NATs and firewalls.



M3104 Network Group Diagnostics CompletedFIELDS: None.

CAUSE: The Network Group Diagnostics feature has completed.

ACTION: None.

M3105 Feature Disabled for Peer-to-PeerFIELDS: None.

AXXESS CAUSE: Agent Help/Record-A-Call feature is disabled for Peer-to-Peer in version 8.1 and later.

5000 CAUSE: Agent Help/Record-A-Call feature is disabled for Peer-to-Peer in Mitel CS-5200 and Mitel CS-5400.

ACTION: None.

M3106 Received Handshake from Remote Node <node> but Could Not Find Session <session_id> or Off-Node IP Connection <connection>

FIELDS: node The node Call Processing is trying to connect to.

session_id The session Call Processing is told to connect.

connection The off-node IP connection from which the IP_PORT_REQUEST_INFO message was sent to Call Processing.

CAUSE: The off-node IP connection programmed in Database Programming did not match the off-node IP connection that sent Call Processing the IP_PORT_REQUEST_INFO message. Call Processing will fail the session because it does not know about the off-node IP connection.

ACTION: Verify IP networking programming via Database Programming.

M3107 Received Last Handshaking but Could Not Find Session ID <session_id>

FIELDS: session_id The session for which Call Processing is about to set up the link status to be true.

CAUSE: Call Processing received the last handshake message (IP port request info confirm) for setting up the IP session. However, Call Processing can no longer find the session ID in the session manager’s session table because we have initiated the session. This could be caused by the IP connection that was used to start the session no longer exists or by network problems.

ACTION: Verify IP networking programming via Database Programming.

M3108 Received Last Handshaking but Remote Node <node> Rejected IP Link

FIELDS: node Remote node number Call Processing is trying to connect to.

AXXESS CAUSE: After Call Processing sent back the handshake “who are you response,” the remote node found that Call Processing has just established a session to an IPRC that is “fully” loaded with sockets. If there is another IPRC on the remote node that is not fully loaded, the remote node will reject this link and request that the local node try another off-node IPRC.

5000 CAUSE: After we sent back the handshake “who are you response”, the remote node found we have just established a session to an IPRA that is “fully” loaded with sockets. If there is another IPRA on the remote node that is not fully loaded, the remote node will reject this link and request the local node to try another off-node IPRA (or IPRC if networked to Axxess).

ACTION: None.



M3109 Device <device> Ext <eeeee> did Not Receive Release ACKfor 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.

M3110 No More Data Connections for Board <board number>AXXESS FIELDS: board number The board number of the IPRC that no longer has data connections.

5000 FIELDS: board number This is the module number (module 7 = Processor Module) of the IPRA that no longer has data connections.

CAUSE: The board has IP Devices such as IP Stations, IP Trunks, or networking data connections to other nodes and can support no more data connections.

ACTION: None.

AXXESS FS ACTION: To see what data connections exist on an IPRC, go into the IPRC's On-Line Monitor in Debug Session. Type ipdc to view all the IP phone data connections. Type socket and filter on port 5570 for all of the IP networking data connections.

5000 FS ACTION: To see what data connections exist on an IPRA, go to the unit’s Web page and view the Processor Module.

M3111 Licence Manager <info>FIELDS: info This is information the system prints out when there is an issue with the software license.

CAUSE: The board has IP Devices such as IP Stations, IP Trunks, or networking data connections to other nodes and can support no more data connections.

ACTION: Something has caused the software license to become invalid. This may be caused by a hacker trying to by-pass Mitel's licensing scheme, an invalid license loaded on the system, an error with the Mitel Master License data, or a possible bug in the licensing algorithm.

FSACTION: Ask the site to send a copy of the database, a message print log that shows the error, the “.isl” license loaded on the system and an dump of the license manager. Note that

M3200 Periodic Database Diagnostics Options: <db_field>FIELDS: db_field Describes which field was toggled and what the resulting value is.

CAUSE: One of the three database fields describing the operation of the periodic database diagnostics has been toggled.

ACTION: None.

NOTE An Automatic Diagnostics freeze will have the “.lm” file extension, which holds the license manager dump information.



M3201 Periodic Database Diagnostics: <details>FIELDS: details A text field that gives the details of the specific event associated with the database

diagnostics.

CAUSE: Notifies that a particular event has occurred with the periodic database diagnostics process.

ACTION: None.

M3250 Periodic Resource Diagnostics Options: <db_field>FIELDS: db_field Describes which field was toggled and what the resulting value is.

CAUSE: One of the three database fields describing the operation of the periodic resource diagnostics has been toggled.

ACTION: None.

M3251 Periodic Resource Diagnostics: <details>FIELDS: details A text field that gives the details of the specific event.

CAUSE: This message is to notify that an event associated with the periodic resource diagnostics has occurred.

ACTION: None.

M3252 System Manager Requested Node Name Change to: <text>FIELDS: text The new name of the node.

CAUSE: The System Manager instructed Call Processing to change the node name to the new node name.

ACTION: None.

M3253 Call Processing Successfully Connected to System Manager

FIELDS: None.

CAUSE: Call Processing successfully connected to System Manager.

ACTION: None.

M3254 Call Processing is Trying to Connect to System Manager <username>@<ip_address>:<port_number>

FIELDS: username Agent account name for System Manager

ip_address IP address of the System Manager Call Processing is attempting to make a connection.

port_number The port number of the System Manager Call Processing is attempting to make a connection.

CAUSE: Call Processing is trying to connect to System Manager.

ACTION: None.

M3255 <text> System Manager ServicesFIELDS: text Either Enabling or Disabling.

CAUSE: The System Manager feature has been enabled/disabled.

ACTION: None.



M3256 Call Processing Received Unknown System Manager Event: <text>

FIELDS: text The unknown event topic.

CAUSE: An unknown event topic was received by Call Processing. May indicate a version mismatch in the communication protocol between Call Processing and System Manager.

ACTION: Notify the System Manager administrator.

M3257 Call Processing Disconnected from System Manager <error code>

FIELDS: error code The reason System Manager disconnected.

CAUSE: The System Manager feature was either terminated by the user or the network connection was lost.

ACTION: See A017 (page 4).

M3258 System Manager SSL Error: <text>FIELDS: text The text associated with the error code in A017.

CAUSE: See A017 (page 4).

ACTION: See A017 (page 4).

M3259 Node <node> Enabled Mode <mode>FIELDS: node The node we are enabling for the specified mode.

mode Either Night or Day mode

CAUSE: Call Processing is confirming that it is entering Night or Day mode.

ACTION: None.

M3500 <text> from ASAI Device on IP Address <xxx.xxx.xxx.xxx>FIELDS: text The message received from the ASAI device (e.g., “On-Line” or “Off-Line”).

xxx.xxx.xxx.xxx The IP address of the ASAI device.

CAUSE: CP received a message of interest from the ASAI device. For example, "On-Line" and "Off-Line".

ACTION: None.

M3501 <text> Socket Thread Started from IP Address <xxx.xxx.xxx.xxx>

FIELDS: text The name of the socket thread.

xxx.xxx.xxx.xxx The IP address of the attached device.

CAUSE: Call Processing received a socket logon from an external client.

ACTION: None.

M3502 <text> Socket Thread StartedFIELDS: text The name of the socket thread.

CAUSE: Call Processing received a socket logon from an external client.

ACTION: None.



M3503 SYSOAI CMD: <text>FIELDS: text OAI Error String

CAUSE: An application error or some type of race condition.

ACTION: None.

M3504 Port <port>: SYSOAI CMD: <text>FIELDS: port The port number where the error occurred.

text OAI Error String.


ACTION: None.

M3505 TCP <xxx.xxx.xxx.xxx>: SYSOAI CMD: <text>FIELDS: xxx.xxx.xxx.xxx The IP address of the device.

text OAI Error String.


ACTION: None.

M3506 Fax Tone Detected Fax Call Initiated: <board xx>, <session xx>

FIELDS: board xx The parent board of the VoIP DSP resource used for this call.

session xx The VoIP number for this call.

CAUSE: The IP Resource application detected the V21 flags, and has enough T.38 resources to switch to fax mode.

ACTION: None.

M3507 Retrieving Device File TranslationFIELDS: None.

CAUSE: The Device File Translation was requested through database programming.

ACTION: None.

M3508 NTP Synchronization SuccessfulFIELDS: None.

CAUSE: The NTP Synchronization attempt was successful.

ACTION: None.

NOTE This message only occurs if the CPH "Log System OAI Input" flag is enabled.





M3509 Network Date/Time Changed by Node <num>FIELDS: num Node number that performed the Network Date/Time change.

CAUSE: Set Network Date/Time feature executed by remote or local node.

ACTION: None.

M3510 Set Date/Time Feature Code Entered by Ext <eeeee>FIELDS: eeeee The extension number of the device that entered the feature code.

CAUSE: An administrator entered the Set Date/Time feature code.

ACTION: None.

M3511 Set Network Date/Time Feature Code Entered by Ext <eeeee>

FIELDS: eeeee The extension number of the device that entered the feature code.

CAUSE: An administrator entered the Set Network Date/Time feature code.

ACTION: None.

M3512 Synchronize Network Time Feature Code Entered by Ext <eeeee>

FIELDS: eeeee The extension number of the device that entered the feature code.

CAUSE: An administrator entered the "Synchronize Network Time" feature code.

ACTION: None.

M3513 UPS Status <text>FIELDS: text The text describing the UPS status.

CAUSE: This message is purely informational. Examples of status information the system provides are, “UPS detected” (upon plugging in a UPS via the USB), “UPS removed” (unplugging UPS via USB), UPS on-line, UPS battery low, UPS manufacturer and UPS model number.

ACTION: None.

M3514 Request Remote Node <number> Span Connection Type by <ntg>

FIELDS: number The remote node number.

ntg The node trunk group associated with the T1/E1 PRI port.

CAUSE: This information is purely informational. The T1/E1 PRI port is programmed to use auto remote node span connection type detection. This is a status information to indicate that the port is making an attempt to learn the remote node's span connection type.

ACTION: None.



M3515 Received Remote Node <number> Span Connection Type<type> Response by <ntg>

FIELDS: number The remote node number.

type Remote Span Connection type.

ntg The node trunk group associated with the T1/E1 PRI port.

CAUSE: This information is purely informational. The T1/E1 PRI port is programmed to use auto remote node span connection type detection. This is a status information to indicate that the port has received the response to the request it made to learn the remote node's span connection type.

ACTION: None.

M3516 <ntg> Remote Node <number> Span Connection Type hasChanged from <text1> to <text2>

FIELDS: ntg The node trunk group associated with the T1/E1 PRI port.

number The remote node number.

text1 The original connection type.

text1 The new connection type.

CAUSE: This information is purely informational. The T1/E1 PRI port is programmed to use auto remote node span connection type detection. This is a status information to indicate that the port has received the response to the request and the new connection type is different from the last known connection type. Due to the connection type changing, the span-facing and system-side Echo Profiles of the b-channels programmed on the current port will be modified accordingly.

ACTION: None.

M3517 <ntg> Remote Node <number> Span Connection Type to<text> Due to Older System Version

FIELDS: ntg The node trunk group associated with the T1/E1 PRI port.

number The remote node number.

text The new connection type.

CAUSE: This information is purely informational. The T1/E1 PRI port is programmed to use auto remote node span connection type detection. This is a status information to indicate that the span it is connected to is an older node, that is, older than v2.3. The system is defaulting the remote span connection type to old T1/E1/PRI. Due to the new default, the span-facing and system-side Echo Profiles of the b-channels programmed on the current port will be modified accordingly.

ACTION: None.

M3518 DSP <number1> on Module <number2> Forced Offline Due to 4-DEI Mode

FIELDS: number1 The DSP number on the module.

number2 The module number associated with the DSP.

CAUSE: This message is informational only. The DSP on the DEM-16 modules in the DEIs do not come online when the system is in 4-DEI mode.

ACTION: None.



M3519 Remote Configuration Connection: <status>FIELDS: status The system reports the current remote configuration connection status.

CAUSE: The connection has changed and the system is informing the user of current state. The following are available states.

x Unknown (Initial status): An initial status before receiving a status from the remote configuration handler.

x Enable pending: After a user enables the remote programming feature and before receiving a confirmation.

x Disable pending: After a user disables the remote programming feature and before receiving a confirmation.

x VPN connected: VPN connection is established.

x Connected to configuration server: Connected to the remote configuration server.

x Disable: Remote Configuration feature is disabled.

x Server disconnected: Server connection is disconnected.

x VPN disconnected: VPN connection is disconnected.

ACTION: None.

M3520 File-Based MOH Status: <status>FIELDS: status The system reports the file-based MOH status for the given audio source number.

CAUSE: This message is informational only.

ACTION: None.

M3521 Door Relay Activated By Ext. <eeeee>FIELDS: eeeee: The extension number of the device that entered the feature code.

CAUSE(S): A phone activated the door relay feature.

ACTION: None.


System Messages (M0001–M9999): Database Warning Messages (M4000–M4999)

Database Warning Messages (M4000–M4999)Warning messages regarding the database and operations being performed on the database. There may be some effect on system operation. Report to Mitel Field Service.

M4000 <table>: No Match with Table for <object>FIELDS: table The name of the table. Could be "Call Cost" or "Numbering Plan Analysis".

object The object being searched for.

CAUSE: The software was searching for the specified object in the specified table and didn't find it. This indicates some form of software error. The software tried to handle the situation in a reasonable manner to continue service.

ACTION: Save the database. From Diagnostics Monitor/System Monitor, dump the “Numbering Plan Analysis” table via Database Records. Capture this information and send a report to Mitel Field Service.

FSACTION: Report the problem to the Engineering Contact for investigation and resolution of this software error.

M4001 Too Many Call Routing Tables Chained Together <limit>FIELDS: limit this is the limit on the length of a call routing table chain.

CAUSE: The software was following a call routing table chain and reached the limit on the length of the chain. The software allows call routing tables to route to other call routing tables. For safety and speed, the software imposes a limit on the length of this chain.

ACTION: Save the database and report the problem to Mitel Field Service.


M4002 Processed Invalid Call Routing Table Number <number>FIELDS: number this is the invalid number that the software tried to process.

CAUSE: The software was asked to a process a call routing table and it was given an invalid table number.

ACTION: Save the database and report the problem to Mitel Field Service.


M4003 Invalid Associated Extension <eeeee> in SMDR MessageFIELDS: eeeee The invalid associated extension number that the SMDR process found.

CAUSE: There is probably an invalid extension in the database that is causing the SMDR task to print this message. The database may have become corrupted due to a software error or some other external corruption.

ACTION: Save the database. Run the database periodic diagnostics and report the problem to Mitel Field Service.




M4004 Invalid Extension <bad_ext> Removed from Extension List <ext_list>

FIELDS: bad_ext The invalid extension number inside an extension list.

ext_list The extension list that held the invalid extension number.

CAUSE: Due to previous problems in the database update program, it may be possible that extensions get lost after a database restore. After a database restore the system goes through its extension lists to find any extensions that may be missing. If the system finds a missing extension, it prints this message and removes the extension from the extension list. Your system should function normally after this occurs.



M4005 Invalid ACD Agent ID <bad_ext> Removed from Extension List <ext_list>

FIELDS: badext The invalid ACD Agent ID inside an extension list

extlist The extension list that held the invalid ACD Agent ID

CAUSE: Due to previous problems in the database update program, it may be possible that ACD Agent IDs get lost after a database restore. After a database restore the system goes through its extension lists to find any ACD Agent IDs that may be missing. If the system finds a missing ACD Agent ID, it prints this message and removes the ACD Agent ID from the extension list. Your system should function normally after this occurs.



M4006 <prem_feat> Premium Feature Disabled on Node <number>(Axxess Only Pre v8.0)

FIELDS: prem_feat The name of the premium feature (for example, Networking)

number The number of the node that has the disabled premium feature.

CAUSE: A user tried to access a restricted premium feature. This can happen if the security PAL changed or the premium feature was disabled by the installer and the installer did not clean up the Database Programming to reflect the feature change.

ACTION: Update the security PAL or clean up the Database Programming to remove references to the disabled premium feature.

M4007 Change of Off-Node Extension <ext> to <bad_ext> Failed Due to Conflict

FIELDS: ext This is the existing off-node extension for which the change was attempted

badext This is the extension to which the change was requested

CAUSE: A remote node changed the extension of a device for which this node has an off-node extension. When this node attempted to modify the corresponding off-node device, the new extension was found to conflict with an existing extension on this node. The off-node device extension remains unchanged.

ACTION: Verify extension-numbering plan with those of remote nodes and update database accordingly.



M4008 Remote Equip/Unequip/Update of Off-Node Ext <ext>Prevented Due to <reason>

FIELDS: ext The extension of an off-node device which failed to be equipped or unequipped on this node.

reason Text describing the reason.

CAUSE: A programming session on a remote node equipped or unequipped a new device while there was an active programming session on the local node. The active local programming session prevented the changes being automatically made to the corresponding off-node device on this node. For an equip, the new device will be unavailable until an off-node device is created for it. For an unequip, there will still be an off-node device for the now nonexistent remote device.

Another cause of this problem is having a Voice Processor programmed but not connected. To ensure that the CP and Voice Processor databases stay in sync, the Voice Processor must be connected when any programming takes place in CP.

ACTION: Create the off-node devices manually on the local node if an equip, or delete the corresponding off-node device for an unequip. If the problem is due to Voice Processor programmed but not connected, make sure that if the system is programmed to have a Voice Processor, it is connected, or program the system to not have a Voice Processor.

M4009 Device Info Import for <ext> Failed: <reason>FIELDS: ext The off-node extension which could not be handled.

reason Text describing the reason.

CAUSE: During an import of off-node devices, we received information about an off-node device with the indicated extension. Due to the reason given, generally a conflict with an existing extension, the received information had to be ignored.

ACTION: Resolve extension conflicts and program the off-node devices manually.

M4010 Remote Equip of Off-Node Device <ext1> Failed: Conflict with <ext2>

FIELDS: ext1 The extension of an off-node device that Call Processing attempted to equip.

ext2 The extension of a Voice Processor extension ID or group list that ext1 conflicted with.

CAUSE: A programming session on a remote node caused this node to attempt to equip a new off-node device. While not a system-wide conflict, the new extension did cause a conflict with the indicated extension on the attached voice mail. This type of conflict is possible with Voice Processor group lists and extension IDs.

ACTION: This message indicates a numbering plan conflict. Determine the nature of the conflict, and reprogram extensions as necessary.

M4011 Another Node does Not Know About Node <number>FIELDS: number Node number of the new node that some other node does not know about.

CAUSE: A new node was added to the node that printed this message, but all other nodes know about this node.

ACTION: Log into Database Programming on all nodes in the system and add the new node, if it has not already been added. Do not forget to add the node trunk group/node IP connection group(s) to the new node so that the node knows how to route calls to the new node. Unlike M7005, this problem is a warning based on the configuration of the network. They system can still function properly, but we recommend that you add the new node to all other nodes as soon as you can because those other nodes will not be able to call the new node.

NOTE This message will also be generated when the device being equipped has an extension which conflicts with an existing extension on this node.



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.

M4013 BRI Trunk Port<b.p.d> has an Invalid SPID <spid>FIELDS: b.p.d The board/port/device of the BRI Trunk Port with the invalid SPID.

spid The SPID that the Central Office rejected.

CAUSE: The Central Office has rejected the indicated SPID from the indicated BRI Trunk Port.

ACTION: Log into Database Programming and either remove the indicated SPID and Directory pair or correct it. It is possible that the Central Office has not turned on the indicated SPID yet. You may need to contact the Central Office to get this problem resolved.

M4014 ISDN Data Call Rejected on Trunk Group or Node Trunk Group <ext>

FIELDS: ext The extension of the Trunk Group or Node Trunk Group.

CAUSE: The trunk group or node trunk group does not accept ISDN calls, and an ISDN device (for example, a video conference unit) tried to place an outgoing call or a private networking call using the trunk group or node trunk group.

ACTION: Log into Database Programming. If a trunk group reported the problem, see if all the trunks in the trunk group are B-Channel trunks. If so, change the ISDN Data Calls flag to “yes.” Otherwise, do not give the ISDN device outgoing access to that trunk group.

M4015 Node <number1> does Not Know About Node <number2> FIELDS: number1 The node number of the node that does not know about the new node in the system.

number2 The node number of the new node.

CAUSE: A new node was added to the private network. The node that printed this message knows about the node but another node indicated in the message print that it does not.

ACTION: Log into Database Programming on the indicated node in the system and add the new node, if it has not already been added. Do not forget to add the node trunk group/node IP connection group(s) to the new node so that the node knows how to route calls to the new node. Unlike M7005, this problem is a warning based on the configuration of the network. The system can still function properly, but we recommend that you add the new node to all other nodes as soon as you can because those other nodes will not be able to call the new node.

NOTE

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 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.



M4016 <ext1> is Overriding Emergency Outgoing Access for <ext2>

FIELDS: ext1 The station that is overriding the Emergency Outgoing Access field.

ext2 The Trunk Group or Node Trunk Group whose Emergency Outgoing Access field is not programmed properly.

CAUSE: A user dialed an emergency number and did not have emergency outgoing access properly programmed for that extension. The system overrode the programming and still dialed the emergency number.

ACTION: Program the Trunk Group’s or Node Trunk Group’s Emergency Outgoing Access extension list to include the station.

M4017 Invalid Software License Loaded: <reason>FIELDS: reason Why the software was not loaded.

CAUSE: A new software license, which was recently uploaded, could not be loaded for the reason indicated.

ACTION: Change the system database or upload a new software license that corrects the problem.

FSACTION Walk the installer through properly programming the Trunk Group's or Node Trunk Group's Emergency Outgoing Access extension list to include the station.

M4018 Invalid IP Connection ID detected: <id>FIELDS: id The ID of the IP Connection that is not valid.

CAUSE: A remote IP Connection ID does not match the ID of the actual IP Connection.

ACTION: Verify the actual IP-Connection ID and change the programming where appropriate, i.e. on the local node or remote node.

M4019 <ext1> Does Not Have <str> Outgoing Access on TrunkGroup or Node Trunk Group or IP Connection <ext2>

FIELDS: ext1 The Station that is trying to make an outgoing call.

str Day or night.

ext2 The Trunk Group or Node Trunk Group whose Outgoing Access field is not programmed properly.

CAUSE: A user dialed an outside number and did not have outgoing access properly programmed for that extension. The call is being rejected.

ACTION: Program the Trunk Group's or Node Trunk Group's Day/Night Outgoing Access extension list to include the station.

FSACTION Walk the installer through properly programming the Trunk Group's or Node Trunk Group's Day/Night Outgoing Access extension list to include the station.

M4020 Invalid Extension Dialed on SIP Peer: <ext1> from SIP Device: <ext2> Dialed Number: <str>

FIELDS: ext1 The extension of the SIP Peer that dialed the invalid extension.

ext2 The extension of the SIP Device that dialed the invalid extension.

str The dialed digits with an invalid extension.

CAUSE: A SIP device dialed a number that did not start with a valid extension. If the SIP device is dialing and outside number it needs to start the dialed number with the extension of a trunk, trunk group, or ARS followed by the outside number (e.g., 920004809619000).

ACTION: On the SIP Peer, verify the dialed number starts with a valid extension.

System Messages (M0001–M9999): Hardware Warning Messages (M5000–M5999)


Hardware Warning Messages (M5000–M5999)Warning messages regarding hardware configuration and operation. There may be some effect on system operation. Resolve if possible. Otherwise, report the problem to Mitel Field Service.

M5000 <brd_type> <slot_#>: DSP/8051 Version Number Conflict: 8051 Ver = <version>, DSP Ver = <dsp_ver> (Axxess Only)

FIELDS: brd_type The board type reporting the error (should always be “OPC Board”).

slot_# The slot number the OPC board is in.

version The software version number stored in the 8051's ROM.

dsp_ver The major.minor software version number stored in the DSP's ROM.

CAUSE: The message indicates that the software on the 8051 processor ROM and the software on the DSP ROM are different and incompatible. The DSP is prevented from operating.

ACTION: Return the indicated board to Mitel so the proper chips can be placed on the board.

M5001 <brd_type> <slot_#>: Invalid Highway or TimeslotSpecified: HWY = <highway>, TS = <timeslot> (Axxess Only)



highway The highway number sent in the invalid command.

timeslot The timeslot number sent in the invalid command.

CAUSE: The system sent an invalid command to the indicated OPC board. The command was probably a voice channel connection command. The OPC board ignores invalid commands, so some call's voice channel connection was not made. This is due to a software error.

ACTION: Perform a Freeze immediately following the message and then do a database save. Send the information to Mitel Field Service for examination and correction of this problem.

FSACTION: Send the System History and the database save to the Engineering Contact for immediate resolution of this problem.

M5002 <brd_type> <slot_#>: DSP to Dual-Port RAM State Error forDSP <d>: State = <state> (Axxess Only)

FIELDS: brd_type The board type reporting the error (should always be "OPC Board").


d The number of the DSP on the OPC board reporting the error.

state The invalid state the DSP was in when the state error was detected.

CAUSE: The DSP on the OPC board communicates with the board using Dual-Port RAM (RAM that can be accessed by two different processors). The DSP updates the Dual-Port RAM with its state value, and the 8051 on the OPC board checks the DSP state periodically. The state value was invalid when it was checked.

ACTION: If this error is occurring frequently, attempt to replace the indicated DSP chip. If that doesn't fix the problem, replace the OPC board and send the failing board to Field Service for examination.

FSACTION: Send the board to the Engineering Contact so we can determine what the problem is and fix it.



M5003 <brd_type> <slot_#>: OPC-to-DSP Command Error for DSP<x>: Command = <command> (Axxess Only)



x The number of the DSP on the OPC board reporting the error.

command The invalid command from the 8051 to the indicated DSP.

CAUSE: The 8051 on the OPC board gives commands to each of the DSPs on the OPC board. This message indicates one of the DSPs thinks the command given to it by the OPC board is invalid.

ACTION: Immediately perform a freeze. If the OPC causes problems, replace the OPC board. Send information to Mitel Field Service.

FSACTION: Give the board and the history information to the Engineering Contact for immediate analysis to determine and fix the problem.

M5004 <brd_type> <slot_#>: DSP Illegal Response for DSP <d>:Response = <response> (Axxess Only)



d The number of the DSP on the OPC board reporting the error.

response The invalid response from the DSP to the OPC board.

CAUSE: The 8051 on the OPC board gives commands to each of the DSPs on the OPC board, and the DSPs respond to the commands. This message indicates the OPC board thinks the response received from the indicated DSP is invalid.



M5005 <brd_type> <slot_#>: DSP Response Size Error for DSP<number>: Size = <size> (Axxess Only)



number The number of the DSP on the OPC board reporting the error.

size The invalid response size value.

CAUSE: The 8051 on the OPC board gives commands to each of the DSPs on the OPC board, and the DSPs respond to the commands. This message indicates the OPC board thinks the size field of the response received from the indicated DSP is invalid.





M5006 <brd_type> <slot_#>: Unexpected DSP Reset for DSP<number> (Axxess Only)



number The number of the DSP on the OPC board that went through a reset.

CAUSE: The indicated DSP unexpectedly went through reset processing for an unknown reason.

ACTION: First replace the indicated DSP chip. If the problem persists, replace the OPC board, and send the faulty board to Mitel Field Service for examination.

FSACTION: Send the board to the Engineering Contact for analysis and determination of this problem.

M5007 <brd_type> <slot_#>: Unexpected DSP On-Line for DSP <number>: Boot-Page = <page> (Axxess Only)



number The number of the DSP on the OPC board that came on-line.

page The boot page the DSP used when coming on-line.

CAUSE: The indicated DSP unexpectedly reported coming on line for an unknown reason.

ACTION: First, replace the indicated DSP. If the problem continues to occur, replace the OPC board and send the faulty OPC board to Mitel Field Service to analyze the defect in the board.

FSACTION: Send the board to the Engineering Contact for analysis and determination of this problem.

M5008 <brd_type> <slot_#>: Boot-Page Mismatch for DSP <number>: Boot-Page = <page> (Axxess Only)


slot The slot number the OPC board is in.

number The number of the DSP on the OPC board that came on-line.

page The boot page the DSP used when coming on-line.

CAUSE: The indicated DSP reported coming on line using an invalid boot-page number.

ACTION: First, replace the indicated DSP. If the problem continues to occur, there may be a database corruption that's sending an invalid Boot-Page number to the DSP. Do a database save and send it to Mitel Field Service for examination. Next, use Database Programming to examine the DSP configuration. Change the DSP value “nothing”, do an update. Then change the DSP value back to the correct value and update. If the problem continues to occur, replace the OPC board and send the faulty OPC board to Mitel Field Service to analyze the defect in the board.

FSACTION: Send the defective board and or database along to the Engineering Contact for analysis and resolution of this problem.



M5009 <brd_type> <slot_#>: <num> RS-232 Frame Errors (Axxess Only)

FIELDS: brd_type The board type reporting the error (should always be "OPC Board")

slot_# The slot number where the OPC board resides

num The number of frame errors

CAUSE: There were X number of framing errors, during a 10-second period, detected on the serial port of the indicated OPC board. This is probably due to using the wrong baud rate, but could be due to faulty serial cable wiring, a faulty OPC board, or a faulty transmitting device.

ACTION: Verify that you are using the same baud rate as the OPC board. Try using each baud rate, or connecting up to a different serial port to check cabling. Check the serial cable wiring and connectors. If the problem persists, replace the OPC board, then the transmitting device (the device that is transmitting serial information to the OPC board).

M5010 <brd_type> <slot_#>: RS-232 Receive Data Lost (Axxess Only)



CAUSE: The OPC board was unable to remove data fast enough from the serial port on the board, so some data sent to the OPC board was lost.

ACTION: Freeze the system. Replace the OPC board. Send the information to Mitel Field Service.

M5011 <brd_type> <slot_#>: CPU Command Size Error: Size = <number> (Axxess Only)



number The length value sent to the board.

CAUSE: A command was sent to the OPC board that had an invalid length field. The invalid command is not processed by the OPC board. The message may have been a DSP command (voice channel connection, Caller ID connection, etc.), so the system may temporarily exhibit improper operation. This message is due to a software error.

ACTION: Perform a Freeze immediately following the message. Send the information to Mitel Field Service.

FSACTION: Send the Freeze information to the Engineering Contact, so the error can be found and fixed.

M5012 <brd_type> <slot_#>: DSP Response Data Error for DSP <dsp>: Data = <byte> (Axxess Only)



dsp The DSP causing the error message.

byte The invalid data byte in the DSP response.

CAUSE: The processor on the OPC board received a response from the indicated DSP that the response had an illegal data value in it. This message is due to a software error. System operation will probably not be affected.


FSACTION: Give the OPC board and the history information to the Engineering Contact for immediate analysis to determine and fix the problem.



M5013 <brd_type> <slot_#>: DSP Window Time-Out Error for DSP <dsp> (Axxess Only)




CAUSE: The processor on the OPC board did not receive a response from the indicated DSP in time. The indicated DSP may not be functioning properly. This should be due to a hardware problem.

ACTION: Replace the OPC board.

M5014 <brd_type> <slot_#>: DSP Boot Time-Out Error for DSP <dsp> (Axxess Only)




CAUSE: The processor on the OPC board did not detect that the indicated DSP was able to "boot up" properly. The indicated DSP may not be functioning properly. This should be due to a hardware problem.

ACTION: Replace the OPC board.

M5015 <brd_type> <slot_#>: Caller ID Connect When Not Ready for Caller ID <rr>


slot_# The board slot number the OPC board is in.

rr The logical Caller ID receiver that received the invalid command.

CAUSE: A Caller ID Connect command was sent to a board that already had an Caller ID connection present on the indicated receiver. The Caller ID digits were lost for the call that caused the duplicate Caller ID connect command. This may be due to a software error.

ACTION: Perform a Freeze immediately following the message. Send the information to Mitel Field Service.

FSACTION: Send the System History information to the Engineering Contact for examination to resolve this problem.

M5016 <brd_type> <slot_#>: RS-232 Transmit Data Lost (Axxess Only)



CAUSE: This message should not be seen in the field. The OS software on the CPU continued to send serial data to the OPC board even though the OPC board could not send information out (the OPC board was XOFFed or hardware handshaking disabled serial transmission). More data was sent by the CPU board to the OPC board than the OPC board could buffer, so some data was lost. This is due to a software error.

ACTION: Report the error to Mitel Field Service.



M5017 DSS Error for DSS <number> <b.p.d>: <s-Side> Frame ErrorFIELDS: 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.

M5018 DSS Error for DSS <number> <b.p.d>: Command Inconsistency Error

FIELDS: number The DSS number the problem occurred on.


CAUSE: An invalid command is received by the DSS unit, or data is received when a command is expected. All commands and data are ignored until the system sends a reconfigure command to the phone. This is probably due to a software error, though it can occur as the result of a hardware problem.

ACTION: The software will attempt to clean up the problem by “reconfiguring” the DSS unit. Thus, the user should experience no major problems. 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 DSS unit, phone, and intervening cables.

M5019 DSS Error for DSS <number> <b.p.d>: Data Lost ErrorFIELDS: number The DSS number the problem occurred on.


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.



M5020 <b.p.d>: Caller ID Terminated Due to Connect Timer ExpiredFIELDS: b.p.d The board/port/device of the Caller-ID-programmed trunk whose connect timer expired.

CAUSE: The system allocated a Caller ID receiver when the trunk rang in, but the receiver did not detect carrier before the connect timer expired. The system will not drop the call, but the system will be unable to present Caller ID information because the Caller ID information (if any) was lost.

AXXESS ACTION: Make sure the specified hardware trunk connection is solid and free of static. Make sure the database matches the physical hardware configuration. That is, make sure the physical trunk really sends Caller ID information to the system. Frequently, the CO trunk has not been programmed correctly, so the CO isn't sending Caller ID information. Use a butt-set to listen on the trunk while it rings in. If you don't hear the modem tone (carrier) after the first ring, the trunk is not set up correctly; call the CO and have them enable the Caller ID. Otherwise, there may be a problem with the DSP chip on the OPC/CPU board. Make sure power-up information shows that the OPC/CPU DSPs are working properly. If the DSPs are on the OPC, verify that the OPC board does have a DSP chip and it is programmed to receive Caller ID information.

5000 ACTION: Make sure the specified hardware trunk connection is solid and free of static. Make sure the database matches the physical hardware configuration. That is, make sure the physical trunk really sends Caller ID information to the system. Frequently, the CO trunk has not been programmed correctly, so the CO isn't sending Caller ID information. Use a butt-set to listen on the trunk while it rings in. If you don't hear the modem tone (carrier) after the first ring, the trunk is not setup correctly; call the CO and have them enable the Caller ID. Otherwise, there may be a problem with the DSP chip on the mother board. Make sure power up information shows the DSP is working properly.

M5021 <b.p.d>: Caller ID Terminated Due to Data Timer ExpiredFIELDS: b.p.d The board/port/device of the Caller-ID-programmed trunk whose data timer expired.

CAUSE: The system detected the Caller ID carrier, but received no data before the data timer expired. The system will not drop the call, but the system will be unable to present Caller ID information because the system did not receive any Caller ID data.

ACTION: Make sure the specified hardware trunk connection is solid and free of static.

M5022 <b.p.d>: Caller ID Terminated Due to Carrier LostFIELDS: b.p.d The board/port/device of the Caller-ID-programmed trunk that lost Caller-ID carrier.

CAUSE: A poor connection caused the Caller ID receiver to lose carrier.


M5023 <b.p.d>: Caller ID Terminated Due to Frame ErrorFIELDS: b.p.d The board/port/device of the Caller-ID-programmed trunk that detected a frame error.

CAUSE: A poor connection caused the Caller ID receiver to detect a frame error.


M5024 <b.p.d>: Caller ID Terminated Due to Break DetectedFIELDS: b.p.d The board/port/device of the Caller-ID-programmed trunk that detected a break.

CAUSE: A poor connection caused the Caller ID receiver to detect a break.


M5025 <eeeee>: Hardware Off-Line for Serial PortFIELDS: eeeee The extension of the serial port that went off line.

CAUSE: The serial port went off line and is not available.

ACTION: Make sure the external device the serial port is connected to is not having problems. If so, reset the external device. Make sure the serial cable is connected properly. Replace the serial cable.



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.

M5029 Invalid CO Line State Error for <b.p.d>: State = <xx>FIELDS: b.p.d The board/port/device of the CO line that experienced the CO Line State Error

xx The state number of the CO trunk

AXXESS CAUSE: A command was sent to an LSC (or LSCD) board that was invalid for the current state of the indicated trunk circuit. Typically, this represents a software error where CP either sent a command that was invalid, or that CP thinks the CO trunk is in a different state than the LSC board thinks the state is in. This message can occasionally come up due to glare (the LSC board has sent a message to CP informing it of some event, and at the same time the system has sent a command to the trunk LSC requesting some action that happens to be invalid now that the event has occurred). Typically, the problem will not be service affecting. In some cases, though, the CO call that was active when the problem occurred will be affected.

5000 CAUSE: A command was sent to a LS application that was invalid for the current state of the indicated trunk circuit. Typically, this represents a software error where CP either sent a command that was invalid, or that CP thinks the CO trunk is in a different state than the LS application thinks the state is in. This message can occasionally come up due to glare (the LS application has sent a message to CP informing it of some event, and at the same time the system has sent a command to the LS trunk requesting some action that happens to be invalid now that the event has occurred). Typically, the problem will not be service affecting. In some cases, though, the CO call that was active when the problem occurred will be affected.

AXXESS ACTION: Normally, the trunk will return to a stable state and CP will resynchronize with the LSC board when the call is terminated. If the problem appears to affect the trunk circuit beyond the duration of a single call, press the reset button. If this doesn't solve the problem, remove and re-seat the LSC board. If the problem reappears repeatedly, it is probably due to a software error. Immediately following the error, perform a Freeze and send the information into Mitel Field Service.

5000 ACTION: Normally, the trunk will return to a stable state and CP will resynchronize with the LS application when the call is terminated. If the problem appears to affect the trunk circuit beyond the duration of a single call and it is on an expansion slot, remove and re-seat the LS expansion module, otherwise it is probably due to a software error. If the problem reappears, Immediately following the error, perform a Freeze and send the information into Mitel Field Service

NOTEEarly in Beta Test, a problem existed in the firmware that caused this to occur occasionally. If this is a Beta LSC (or LSCD) board, replace it with a newer release to see if the problem goes away.



M5030 <b.p.d>: Version Not Supported = <x> <phone>FIELDS: b.p.d The board/port/device designation of the unsupported phone.

x Indicates the major or minor version number.

phone The type of phone that is not supported.

CAUSE: Plugged in a phone that was unsupported.

ACTION: Unplug the unsupported phone and replace it with a supported phone.

M5031 <b.p.d>: Version Not Supported = <v> (DSS <x>)FIELDS: b.p.d The board/port/device designation of the unsupported DSS unit.

v The version number that the DSS unit.


CAUSE: Plugged in a DSS that was unsupported, or there is a problem with the DSS unit's hardware.

ACTION: Unplug the unsupported DSS unit and replace with a supported DSS unit.

M5032 <b.p.d>: Input from Off-Line <device>: <msg>FIELDS: b.p.d The board/port/device designation of the device that sent input while off line.

device The device type that sent input while off line.

msg The message that contains the invalid item.

CAUSE: The system received input from a device that was off line.

ACTION: Unless this is affecting the functionality of the system, this is a minor error and can be ignored. Otherwise, we recommend unplugging and plugging back in the device. Report the problem to Mitel Field Service along with a database save and valid CP freeze.

M5033 <b.p.d>: Input from Off-Line <board>: <msg>FIELDS: b.p.d The board/port/device designation of the board that sent input while off line.

board The board type that sent input while off line.


CAUSE: The system received input from a board that was off line.

ACTION: We recommend unplugging and plugging back in the board. Unless this is affecting the functionality of the system, this is a minor error and can be ignored. Otherwise, report problem to Mitel Field Service.

M5034 <b.p.d>: Input from Off-Line DSS <x>: <msg>FIELDS: b.p.d The board/port/device designation of the DSS unit that sent input while off line.

x The number of the DSS unit that sent input while off line.


CAUSE: The system received input from a DSS unit that was off line.

ACTION: We recommend unplugging and plugging back in the DSS unit. Unless this is affecting the functionality of the system, this is a minor error and can be ignored. Otherwise, report problem to Mitel Field Service along with a database save and valid CP freeze.



M5035 <b.p.d>: Input from Unequipped <device>: <msg>FIELDS: b.p.d The board/port/device designation of the device that sent input while unequipped.

device The device type of the device that sent input while unequipped.


CAUSE: The system received input from a device that was unequipped.

ACTION: Unless this is affecting the functionality of the system, this is a minor error and can be ignored. Otherwise, report problem to Mitel Field Service along with a database save and valid CP freeze.

M5036 <b.p.d>: Invalid Power-Up from <device> <power-up-data>,<major-version>, <minor-version>

FIELDS: b.p.d The board/port/device designation of the device that generated the invalid power-up information.

device The type of device that generated the invalid power-up information.

power-up-data Contains power-up data.

major-version Contains the major version number of the device.

minor-version Contains the minor version number of the device.

CAUSE: A device generated invalid power-up information.

ACTION: None. The system automatically resets the device to give the device another chance to come on line. If, however, the device frequently generates this message and never successfully comes on line, replace the device.

M5037 Audio Path Blocking: <path-owner> Already Using Path <x> of <b.p.d>

FIELDS: path-owner The device that is using the audio path. Phone (1) MDP (2) - Modem Data Port Module

x The audio path number that the path-owner is using that some other device wanted to use.

b.p.d The board/port/device designation of the device requesting the audio path that is not available.

CAUSE: A MDPM (Modem Data Port Module) is plugged into the PCDPM (PC DataPort Module), which is plugged into the phone. An OHVA shares the secondary audio path on the phone with the MDPM; therefore, only one path can be in use at one time. Below are two possible scenarios that would create this error message:

x The MDPM tried to come off-hook while the phone was receiving an OHVA. In this case, the user will hear dead silence over the MDPM. The user must wait until the OHVA call is finished and then toggle the hookswitch to receive dial tone.

x The phone tried to perform an OHVA while the MDPM was in use. In this case, the user calling this station will camp on to this station instead of performing an OHVA.

ACTION: None. This is really not a problem but may help a technician figure out why a user did not receive an OHVA or why his/her MPDM received dead silence when the user came off-hook. If you send a report to Mitel, please include a database save and valid CP freeze.

M5038 Audio Path: Invalid Requesting Device <b.p.d>FIELDS: b.p.d The board/port/device designation of the device that was invalid.

CAUSE: An audio path was requested for an invalid device.

ACTION: Unless this is affecting the functionality of the system, this is a minor error and can be ignored. Otherwise, report the problem to Mitel Field Service along with a database save and valid CP freeze.



M5039 <b.p.d> <board1>: Incompatible DB Type = <board2>FIELDS: b.p.d The board/port/device designation of the board that was incompatible.

board1 The board type that is plugged into the slot.

board2 The board type that is programmed in the database for the slot.

AXXESS CAUSE: The board type (as programmed in the database) does not exactly match the board type in the slot.

5000 CAUSE: The module type (as programmed in the database) does not exactly match the module inserted in one of the expansion bays.

AXXESS ACTION: Program the database to the correct board type or replace the board with the board type indicated by the database.

5000 ACTION: Program the database to the correct module type or replace the expansion module with the correct expansion module as indicated by the database.

M5040 <b.p.d> <board1>: Ignored DB Type = <board2>FIELDS: b.p.d The board/port/device designation of the hardware board that generated input that was

ignored.

board1 The board type that is plugged into the slot.

board2 The board type that is programmed in the database for the slot.

AXXESS CAUSE: The board type (as programmed in the database) does not exactly match the board type in the slot.

5000 CAUSE: The module type (as programmed in the database) does not exactly match the module inserted in one of the expansion bays.

AXXESS ACTION: Program the database to the correct board type or replace the board with the board type indicated by the database.

5000 ACTION: Program the database to the correct module type or replace the expansion module with the correct expansion module as indicated by the database.

M5041 <b.p.d> <board>: Input for Non-Existent DTMF Receiver: <msg>

FIELDS: b.p.d The board/port/device designation of the device that is generating input for a non-existent DTMF.

board The type of the hardware board that caused the DTMF warning message.


CAUSE: The system receives an input from a non-existent DTMF receiver when the resource manager does not recognize the input as coming from one of its allocated DTMF resources. This could happen if the resource manager's internal data structures become corrupted.

AXXESS ACTION: We recommend that the system be reset manually using Database Programming. If the system is in a state such that Database Programming cannot connect, reset the system manually by powering off and powering back on.

5000 ACTION: We recommend that the system be reset manually using Database Programming. If the system is in a state such that Database Programming cannot connect, reset the system manually by either rebooting the system from the LCD or by powering down the system and back on again.



M5042 <b.p.d> <board>: Input for Non-Allocated DTMF Receiver: <msg>

FIELDS: b.p.d The board/port/device designation of the device that is generating input for a non-allocated DTMF.

board The type of the hardware board that caused the DTMF warning message.


CAUSE: The system receives an input from a non-allocated DTMF when the resource manager recognize an input from a DTMF receiver that is not allocated to this device. This could happen if the resource manager's internal data structures become corrupted.

AXXESS ACTION: 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 by powering off and powering back on.


M5043 <b.p.d> <board>: Input for Non-Existent Caller ID Receiver: <msg>

FIELDS: b.p.d The board/port/device designation of the device that is generating input for a non-existent Caller ID.

board The type of the hardware board that caused the Caller ID warning message.


CAUSE: The system receives an input from a non-existent Caller ID when the resource manager does not recognize the input as coming from one of its allocated Caller ID resources. This could happen if the resource manager's internal data structures become corrupted.

ACTION: We recommend that the system be reset manually, using the Database Programming. If the system is in a state such that Database Programming cannot connect, reset the system manually by powering off and powering back on.


M5044 <b.p.d> <board>: Input for Non-Allocated Caller ID Receiver: <msg>

FIELDS: b.p.d The board/port/device designation of the device that is generating input for a non-allocated Caller ID.

board The type of the hardware board that caused the Caller ID warning message.


CAUSE: The system receives an input from a non-allocated Caller ID when the resource manager recognize an input from a Caller ID receiver that is not allocated to this device. This could happen if the resource manager's internal data structures become corrupted.

AXXESS ACTION: We recommend that the system be reset manually, using the Database Programming. If the system is in a state such that Database Programming cannot connect, reset the system manually by powering off and powering back on.




M5045 DSS <x> <b.p.d>: Off-Line Ignored DSS is Off-LineFIELDS: x The number of the DSS unit.

b.p.d The board/port/device designation of the DSS unit that generated an off-line input

CAUSE: The system received an off-line input from a DSS unit that was already off line.

ACTION: We recommend unplugging and plugging back in the DSS unit. Unless this is affecting the functionality of the system, this is a minor error and can be ignored. Otherwise, report the problem to Mitel Field Service.

M5048 <b.p.d>: Invalid Board Type <board-type> for Hardware System

FIELDS: b.p.d The board/port/device designation of the board with an invalid board type

board-type The invalid board type

AXXESS CAUSE: Database Programming tried to create an board with an invalid board type. This message occurs when you try to equip a new board and the board type communicated from Database Programming to the CP software is not valid.

5000 CAUSE: Database Programming tried to create a module with an invalid module type. This message occurs when you try to equip a new module and the communicated from Database Programming to the CP software is not valid.

ACTION: While in a remote session, Access the About Database Programming entry in the Help menu. Verify that the Program Version, the System Version, and the Voice Processing Version all match. If the versions do not match, contact Mitel Field Service to obtain the correct versions. If the versions match, terminate your programming session. Then start a new programming session and try your equip again. If the problem persists, contact Mitel Field Service.


M5049 <b.p.d>: Invalid Port Type <port-type> for <board>FIELDS: b.p.d The board/port/device designation of the board that tried to create an invalid port

port-type The invalid port type

board The board type that tried to create an invalid port

CAUSE: Database Programming tried to create a port with invalid port type. This message occurs when you try to equip a new port and the port type communicated from Database Programming to the CP software is not valid.

ACTION: While in a remote session, Access the About Database Programming entry in the Help menu. Verify that the Program Version, the System Version, and the Voice Processing Version all match. If the versions do not match, contact Mitel Field Service to obtain the correct versions. If the versions match, terminate your programming session. Then start a new programming session and try your equip again. If the problem persists, contact Mitel Field Service.




M5052 <b.p.d>: Null Hardware Address in Message for <board>FIELDS: b.p.d The board/port/device designation of the board that received a message with a null

hardware address

board The board type that was sent a message with a null hardware address

CAUSE: The CP software received a message that contained an invalid hardware address.

ACTION: Save the database. Run DB Test on the database. From Diagnostics Monitor/System Monitor, dump the hardware system. Manually reset the system using the Reset System command in Database Programming. If you cannot connect Database Programming to the system, reset the system by cycling power. Report the problem to Mitel Field Service.


M5054 <b.p.d>: Invalid On-Line Data for DSP <dsp-num>: BP = <page>, VSN = <v1>.<v2>, INFO = <dsp-info>

FIELDS: b.p.d The board/port/device designation of the board that sent the DSP on-line data

dsp-num The number of the DSP that sent the on-line data

page The currently active DSP Boot Page

v1 The major version of the DSP code

v2 The minor version of the DSP code

dsp-info The DSP processor type and its crystal speed

CAUSE: The CP software received an invalid on-line message. The DSP tried to boot out of a boot page that does not exist for this version of the DSP code.

ACTION: Use Database Programming to change the DSP configuration option. For example, reprogram the DSP to be DTMF receivers rather than Caller ID receivers). Report this problem to Mitel Field Service.

M5055 <b.p.d>: SL Adapter Plugged Into Keyset Device IgnoredFIELDS: b.p.d The board/port/device designation of the phone port with an SL adapter plugged into it

CAUSE: An SL adapter is plugged into a port programmed to be a phone port.

ACTION: Replace the SL adapter with a phone or use Database Programming to program the port as an SL adapter.

M5056 <b.p.d>: Keyset Device Plugged into SL Adapter IgnoredFIELDS: b.p.d The board/port/device designation of the SL adapter port with a phone plugged into it

CAUSE: A phone is plugged into a port programmed to be an SL adapter port.

ACTION: Replace the phone with an SL adapter or use Database Programming to program the port as a phone.

M5057 <b.p.d>: DSP Watchdog Error from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message.

name Either "Keyset Device" or "Keyset DSS Device".

CAUSE: The DSP in an Executive phone failed to update its watchdog location. This message generally indicates a hardware problem in the phone.

ACTION: Return the faulty phone to Mitel for repair.



M5058 <b.p.d>: Internal DSP Firmware Error from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message.


CAUSE: The DSP in an Executive phone detected a firmware error. This message generally indicates a hardware problem in the phone.


M5059 <b.p.d>: DSP Write Protect Violation from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message.


CAUSE: The DSP in an Executive phone attempted to write to a memory location that is not writable. This message generally indicates a hardware problem in the phone.


M5060 <b.p.d>: DSP Static Variable Check Violation from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message

name Either "Keyset Device" or "Keyset DSS Device"

CAUSE: The DSP in an Executive phone detected an error. A static variable in the DSP RAM changed inadvertently. The problem may be a DSP software error. However, the problem may occur because of static electricity or a power fluctuation. This message does not indicate a problem unless the message appears frequently.

ACTION: If the problem occurs frequently, return the faulty phone to Mitel for repair.

M5061 <b.p.d>: DSP Invalid Command from Microcontroller from <name>

FIELDS: b.p.d The board/port/device designation of the device that sent the error message


CAUSE: The DSP in an Executive phone detected an invalid command from the processor in the phone. This message generally indicates a hardware problem in the phone.


M5062 <b.p.d>: Inconsistency Error from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message

name A text string that specifies the type of device that sent the error message (e.g., “Phone”).

CAUSE: A device received a data (non-command) byte when it expected a command byte. This message may indicate faulty wiring or a hardware problem in the device.

AXXESS ACTION: Verify that the device wiring is correct. If the problem persists, move the device to another port or another board. If the problem follows the device, return the faulty device to Mitel for repair. Otherwise, return the faulty board for repair.

5000 ACTION: Verify that the device wiring is correct. If the problem persists, move the device to another port. If the problem follows the device, return the faulty device to Mitel for repair.



M5063 <b.p.d>: Output Queue Overflow Error from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message


CAUSE: A phone was not able to transmit data to the chassis fast enough, so the phone lost some data (keystrokes). This message may indicate faulty wiring or a hardware problem in the phone.

ACTION: Verify that the phone wiring is correct. If the problem persists, move the phone to another port or another board. If the problem follows the phone, return the faulty phone to Mitel for repair. Otherwise, return the faulty board for repair.


M5064 <b.p.d>: Soft Error from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message


CAUSE: A phone received some invalid data values in a command. The phone attempted to process the command, but the results may differ from the expected results. This message may indicate faulty wiring or a hardware problem in the phone.

ACTION: Verify that the phone wiring is correct. If the problem persists, move the phone to another port or another board. If the problem follows the phone, return the faulty phone to Mitel for repair. Otherwise, return the faulty board for repair.


M5065 <b.p.d>: DSP Receive Buffer Empty Error from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message


CAUSE: This message indicates that the DSP receive buffer latch in a phone is stuck active, preventing the processor from writing to the DSP.


M5066 <b.p.d>: DSP Transmit Buffer Full Error from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message


CAUSE: This message indicates a problem with the DSP in an Executive phone. The DSP transmit buffer latch is stuck active, preventing the processor from reading from the DSP.




M5067 <b.p.d>: Layer 2 Communications Errors from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message


AXXESS CAUSES: The phone detected an unusually large number of data errors in the data packets sent to the phone by the DKSC board. These errors cause unnecessarily long transmission delays to the phone and possibly some service-affecting problems.

A phone sends this error message when it detects a “Layer 2" error (Layer 2 is a level of the protocol between the phone and the DKSC board). A parity error occurred on a data byte received by the phone (suggesting a transmission error similar to a parity error on a modem call). The possible errors are:

x The phone detected a layer 2 command with a length of zero.

x The phone detected a layer 2 command with a length field that is too long.

x The phone detected a parity error occurred on a received data byte (suggesting a transmission error similar to a parity error on a modem call).

x The phone detected an invalid command.

x The phone sent a response to the DKSC board, but did not receive an acknowledge of the response from the DKSC board.

x The phone sent a response to the DKSC board, but received a parity error (which could have been the acknowledge) instead of an acknowledge of the response.

5000 CAUSES: The phone detected an unusually large number of data errors in the data packets sent to the phone by the system. These errors cause unnecessarily long transmission delays to the phone and possibly some service-affecting problems.

A phone sends this error message when it detects a “Layer 2" error (Layer 2 is a level of the protocol between the phone and the system). A parity error occurred on a data byte received by the phone (suggesting a transmission error similar to a parity error on a modem call). The possible errors are:

x The phone detected a layer 2 command with a length of zero.

x The phone detected a layer 2 command with a length field that is too long.

x The phone detected a parity error occurred on a received data byte (suggesting a transmission error similar to a parity error on a modem call).

x The phone detected an invalid command.

x The phone sent a response to the system, but did not receive an acknowledge of the response from the system.

x The phone sent a response to the system, but received a parity error (which could have been the acknowledge) instead of an acknowledge of the response.

AXXESS ACTION: This message does not indicate a serious communications problem between the DKSC card and the phone. Unplug the phone and plug it back in. If the problem persists or escalates please see the Action section for M5068.

5000 ACTION: This message does not indicate a serious communications problem between the system/DE module and the phone. Unplug the phone and plug it back in. If the problem persists or escalates please see the Action section for M5068.

SYMPTOMS: If the CP software receives additional "Layer 2" messages indicated device, the CP software will reset the device, dropping any active (talking) call at the device and generate an alarm (100). If the CP software receives still more messages from the same device, the CP software will "lock out" the device, meaning the CP software will ignore all inputs from the device until you unplug the device and then plug it back in.



M5068 <b.p.d>: Device Reset Due to Excessive Layer 2 CommErrors from <name>



CAUSE: See M5067 (page 90).

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 the appropriate hardware component. Return the faulty component to Mitel for repair.

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.

SYMPTOMS: See M5067 (page 90).

M5069 <b.p.d>: Device Lockout Due to Excessive Layer 2 CommErrors from <name>




ACTION: See M5068 (page 91).


M5070 <b.p.d>: Excessive Data Errors from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message


AXXESS CAUSE: The DKSC board detected an unusually large number of data errors in the data packets sent from the phone to the DKSC board. The phone may have some hardware problems, or the cabling between the phone and DKSC may be faulty.

5000 CAUSE: The system/DE module detected an unusually large number of data errors in the data packets sent from the phone to the system/DE module. The phone may have some hardware problems, or the cabling between the phone and system/DE module may be faulty.

AXXESS ACTION: This message does not indicate a serious communications problem between the DKSC card and the phone. Unplug the phone and plug it back in. If the problem persists or escalates please see the Action section for M5071.

5000 ACTION: This message does not indicate a serious communications problem between the system/DE module and the phone. Unplug the phone and plug it back in. If the problem persists or escalates please see the Action section for M5068.

SYMPTOMS: If the CP software receives additional "Excessive Data" messages indicated device, the CP software will reset the device, dropping any active (talking) call at the device and generate an alarm (100). If the CP software receives still more messages from the same device, the CP software will "lock out" the device, meaning the CP software will ignore all inputs from the device until you unplug the device and then plug it back in.



M5071 <b.p.d> Port Reset Due to Excessive Data Errors from <name>




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.

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.


M5072 <b.p.d> Port Lockout Due to Excessive Data Errors from <name>






M5075 <b.p.d> Unexpected <string> Input from RS-232 Port (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the RS-232 port that received the unexpected input

string Break, Data Lost or Frame Error

CAUSE: An RS-232 experienced a problem sending information across the link.

ACTION: Check the RS-232 cable, and make sure the connections are secure. If necessary, replace the RS-232 cable.

M5076 <b.p.d> Ignoring Input from Unequipped MDPM: <msg>FIELDS: b.p.d The board/port/device designation of the MDPM that sent the error message

msg The message that contains the invalid item

CAUSE: The CP software detected an MDPM plugged into a PCDPM attached to a phone, but the database indicates that no MDPM should be present, so the CP software will ignore all inputs from the MDPM. This situation causes no ill effects, other than a non-functional MDPM.

ACTION: Either remove the MDPM or change Database Programming to allow the MDPM. Leaving the MDPM connected causes no harm to the system.



M5077 <b.p.d> DSP Invalid Coefficient ID from <name>FIELDS: b.p.d The board/port/device designation of the phone that sent the DSP error


CAUSE: An internal software error caused the CP software to send an invalid speakerphone coefficient to the DSP in the indicated device.



M5078 <b.p.d> DSP Real-Time Shortage for <name>FIELDS: b.p.d The board/port/device designation of the phone that sent the DSP error


CAUSE: An internal design error has caused the DSP to exceed the real-time limitations of its microprocessor.



M5079 <b.p.d> RAM Sanity Check Error for <name>FIELDS: b.p.d The board/port/device designation of the phone that sent the error message


CAUSE: A software or hardware error caused the phone RAM to be corrupted.

ACTION: If this error message does not appear frequently, there is no need for action because the phone will reset itself in an attempt to correct the problem. If the error occurs frequently, replace the phone. Return the faulty phone to Mitel for repair. Provide the error number.

M5080 <b.p.d> LCD RAM Sanity Check Error for <name>FIELDS: b.p.d The board/port/device designation of the phone that sent the error message


CAUSE: A software or hardware error caused the phone LCD RAM to be corrupted.

ACTION: If this error message does not appear frequently, there is no need for action because the phone will reset itself in an attempt to correct the problem. If the error occurs frequently, replace the phone. Return the faulty phone to Mitel for repair. Provide the error number.

M5081 <b.p.d> LCD Wait Ready Error for <name>FIELDS: b.p.d The board/port/device designation of the phone that sent the error message


CAUSE: A malfunction occurred in the phone LCD controller.

ACTION: Unplug the phone then plug it back in. If the problem persists, replace the phone. Return the faulty phone to Mitel for repair. Provide the error number.



M5082 <name> Once Allocated by <b.p.d> No Longer In Use – Making Available

FIELDS: name Name of the unused, allocated resource: Caller ID Receiver, DTMF Receiver, Speakerphone, Voice Channel

b.p.d The board/port/device that allocated the resource

CAUSE: As part of normal resource reconciliation, the background task detected a resource leak. The indicated device owns but is not using the specified resource. This message is generally the result of a CP software error.


M5083 <b.p.d> PP Device State Error for <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message

name A string that specifies the name of the PP device that sent the error.

AXXESS CAUSE: The PP device was in a state that was not able to process a command issued by Call Processing. Typically this represents a software error where CP either sent a command was invalid, or that CP thinks that the device is in a different state than the board containing the device thinks the device is in. Currently the PP devices that may report this problem are the OPX and DID circuits attached to an SLA connected to a DKSC card.

5000 CAUSE: The PP device was in a state that was not able to process a command issued by Call Processing. Typically this represents a software error where CP either sent a command was invalid, or that CP thinks that the device is in a different state than the board containing the device thinks the device is in. Currently the PP devices that may report this problem are the OPX and DID circuits attached to an SLA connected to the system/DE module.

AXXESS ACTION: If the problem appears to affect the trunk circuit beyond the duration of a single call, press the reset button. If this doesn't solve the problem, remove and re-seat the board containing the device in error.

If the problem appears repeatedly, it is probably due to a software error. Immediately following the error, perform a Freeze and send the information into Mitel Field Service.

5000 ACTION: If the problem appears to affect the trunk circuit beyond the duration of a single call, perform a freeze and send the information to Mitel Field Service.

If the problem appears repeatedly, it is probably due to a software error. Immediately following the error, perform a Freeze and send the information into Mitel Field Service.

M5084 <b.p.d> DID Ready-Timeout Sync ErrorFIELDS: b.p.d The board/port/device designation of the DID trunk device that sent the error message.

CAUSE: The DID trunk received a Digit Register Ready command when it was not expected.

ACTION: If the problem appears repeatedly, it is probably due to a software error. Immediately following the error, perform a Freeze and send the information into Mitel Field Service.

M5085 <b.p.d> Trunk Ready TimeoutFIELDS: b.p.d The board/port/device designation of the trunk device that sent the error message.

CAUSE: The trunk received a ring signal and Call Processing did not issue a Digit Register Ready command to the PP device before the ready-timeout timer expired. This input pertains to DID and E&M trunks.

ACTION: DID, DNIS, or E&M addressing digits may have been lost.



M5086 <time> Threshold for <threshold> Errors Exceed on <board_type> <b.p.d>

FIELDS: time Daily or Hourly

threshold T1/E1 error threshold type. The types are detailed below.

board_type A string specifying whether the card is a T1 or E1 type.

b.p.d The board, port, and device numbers of the serial port that has a threshold error.

CAUSE: The T1 errors for the indicated T1 has exceeded the specified limit (daily or hourly), so a warning message has been displayed.

AXXESS ACTION: Resolve the indicated error. These errors are meaningful only when the T1 is not in Red Alarm and is relatively working normally. If the board is in Red Alarm, resolve the Red Alarm condition first (see M8001 page 144). When the T1 is out of red alarm and one of these messages appears, check its respective threshold (through Database Programming) and make sure it is set to its default or another reasonable value. If everything is programmed correctly and the errors still occur, resolve the problem with the central office.

The error types are: Bi-Polar Violations, CRC-6 Errors

The signal from the other T1 card has more bit errors than expected. Including: Out-of-Frame Errors, Controlled Slips, Errored Seconds, Severely Errored Seconds, and Unavailable Seconds

The T1 span has detected an excessive number of errors on the T1 span.

5000 ACTION: Resolve the indicated error. These errors are meaningful only when the T1 application is not in Red Alarm and is relatively working normally. If the T1 application is in Red Alarm, resolve the Red Alarm condition first (see M8001 page 144). When the T1 application is out of red alarm and one of these messages appears, check its respective threshold (through Database Programming) and make sure it is set to its default or another reasonable value. If everything is programmed correctly and the errors still occur, resolve the problem with the central office.

The error types are: Bi-Polar Violations, CRC-6 Errors

The signal from the other T1 card has more bit errors than expected. Including: Out-of-Frame Errors, Controlled Slips, Errored Seconds, Severely Errored Seconds, and Unavailable Seconds

The T1 span has detected an excessive number of errors on the T1 span.

M5087 OS Error on <board_type> <b.p.d>, Additional Info: <data>

FIELDS: board_type A string specifying whether the card is a T1 or E1 type.

b.p.d The board, port, and device numbers of the serial port that has a threshold error.

data One to six bytes of additional data (for Engineering use only)

CAUSE: The software on the T1 detected an error condition and reported the problem. Depending upon the severity of the problem, calls on the T1 may or may not have been affected.

ACTION: Report the problem to Mitel. Provide all the additional data values.

FSACTION: Report the problem to Engineering. Provide all the additional data values.

M5088 <b.p.d> Outgoing E&M Call was BlockedFIELDS: b.p.d The board/port/device designation of the trunk device that sent the error message.

CAUSE: The E&M trunk was seized to initiate an outgoing call and it did not receive the expected handshake signal from the far-end switch. This may be the result of incompatible handshaking types defined at each switch. It may also occur if the far-end switch is very busy.

ACTION: Verify that the trunk is programmed to use the same handshaking type at both switches.

NOTE See M2032 (page 42) if this message text does not match the exact wording.



M5089 <b.p.d> Caller ID Receiver UnavailableFIELDS: b.p.d the board/port/device of the Caller-ID-programmed trunk.

AXXESS CAUSE: The system was not able to allocate a Caller ID receiver to a trunk that is programmed to receive Caller ID information. As a result, the system ignored the Caller ID information sent by the Central Office. It is possible that no Caller ID receivers are programmed in the system. If Caller ID receivers are programmed in the system, the Options Card may not be on-line. If Caller ID receivers are programmed and the Options Card is on-line, all of the system's Caller ID receivers were in use when the ring was received on the trunk.

5000 CAUSE: The system was not able to allocate a Caller ID receiver to a trunk that is programmed to receive Caller ID information. As a result, the system ignored the Caller ID information sent by the Central Office. It is possible that no Caller ID receivers are programmed in the system or all of the system's Caller ID receivers were in use when the ring was received on the trunk.

AXXESS ACTION: Make sure that the system is programmed to have an Options Card that has at least one DSP configured to provide Caller ID receivers. Make sure that the Options card is on-line. If this has been done, and the message persists, you will have to add more Caller ID receivers to the system. This may require additional Options Card DSP chips.

5000 ACTION: Make sure that the system is programmed to have Caller ID receivers.

M5090 Rhetorex Driver Function <driver-func> Failed on Channel <chan-num>: Result = <func-result> (VPU/EM Only)

FIELDS: driver-func The Rhetorex driver function call number.

chan-num The channel number where function failed.

func-result The result returned from the function call.

CAUSE: A call to one of the functions of the Rhetorex driver on the voice processing unit failed, returning the indicated result. The Rhetorex functions include playing a prompt, listening for a DTMF digit, etc. Such a failure may affect voice processing unit performance. This message may be the result of a software error in the Voice Processing software.

ACTION: Report this problem to Mitel Field Service. Provide the function number, the channel number, and the result. Also supply as much information as possible about the activity on the voice processing unit prior to the message.


M5091 <b.p.d> <board>: Input for Non-Existent Speakerphone: <msg>

FIELDS: b.p.d The board/port/device designation of the device that is generating input for a non-existent speakerphone.

board The type of the hardware board that caused the speakerphone warning message.


CAUSE: The system receives an input from a non-existent speakerphone when the resource manager does not recognize the input as coming from one of its allocated speakerphone resources. This could happen if the resource manager's internal data structures gets messed up.

ACTION: 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 by powering off and powering back on.



M5092 <b.p.d> <board>: Input for Non-Allocated Speakerphone: <msg>

FIELDS: b.p.d The board/port/device designation of the device that is generating input for a non-allocated speakerphone.

board The type of the hardware board that caused the speakerphone warning message.


CAUSE: The system receives an input from a non-allocated speakerphone when the resource manager recognize an input from a speakerphone receiver that is not allocated to this device. This could happen if the resource manager's internal data structures gets messed up.

ACTION: 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 by powering off and powering back on.

M5093 <b.p.d> <item> RS-232 Response Queue Blocked (<num> Tries) (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the device whose RS-232 queue is blocked.

item A string that specifies the application using the RS-232 link.

num the number of attempts to send the RS-232 data before the queue was deemed to be blocked.

CAUSE: The RS-232 data queue associated with the specified device is blocked. The system has tried the specified number of times to send data to the RS-232 application and has deemed the RS-232 application to be off-line. No further RS-232 data can be sent to the RS-232 application. The data handshaking on the RS-232 link has been compromised. The cabling may be missing or inoperative. Power may be missing from one or more of the RS-232 link components.

ACTION: Verify that the RS-232 link at the device is still connected. Verify the cabling used for the RS-232 link. Verify that the PCDPM has power. In the case of a DSS unit, verify that each DSS unit has power. In the case of a computer, verify that the computer has power.

M5094 <b.p.d> <item> RS-232 Response Queue Overflow <num> Bytes (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the device whose RS-232 queue has overflowed.

item A string that specifies the application using the RS-232 link.

num the size (in bytes) of the queue when it overflowed.

CAUSE: The RS-232 data queue associated with the specified device has overflowed. The system was queueing RS-232 data for the RS-232 application and the queue has reached its maximum allowable size. It may be possible that the external application is in the process of shutting down, in which case the system is on its way towards detecting the shutdown of the external application. It just so happens that the queue filled up before the system has decided that the external application has shut down. If the external application is still present, it means that the system is trying to output data at rate that is much higher than the baud rate programmed for the RS-232 link.

ACTION: Verify that the RS-232 link at the device is still connected. Verify the cabling used for the RS-232 link. Verify that the PCDPM has power. In the case of a DSS unit, verify that each DSS unit has power. In the case of a computer, verify that the computer has power. Contact Mitel Field Service.



M5095 <b.p.d>: Timed-Out Waiting for CO Service InformationFIELDS: b.p.d The board/port/device designation of the device that was collecting CO service

information. CO service information consists of the following: Caller-ID, ANI, DID, and DNIS.

CAUSE: This depends on the CO service information being collected:

Caller-ID: The system did not connect the Caller-ID receiver in time to receive the carrier detect from the CO.

ANI, DID and DNIS: The system either did not connect the DTMF receiver in time to receive the DTMF digits from the CO or the trunk was incorrectly programmed to receive more digits than the CO is sending to the system.

ACTION: This depends on the CO service information being collected:

Caller-ID: The system was experiencing some sort of speed problem that prohibited the system from connecting a Caller-ID receiver to the trunk in time to receive the Caller-ID information. In this case, contact Mitel Field Service.

ANI, DID and DNIS: Verify that the trunk is programmed to receive the correct number of DTMF digits. If the trunk is programmed correctly, the system was experiencing some sort of speed problem that prohibited the system from connecting a DTMF receiver to the trunk in time to receive the digits. In this case, contact Mitel Field Service.

M5096 <b.p.d>: Unable to Dedicate Voice Channel. None are Available for Use

FIELDS: b.p.d the board/port/device of the device dedicating a voice channel.

CAUSE: The system has been programmed in such a way that no other voice channels are available to be dedicated to this device. This device will not be able to have a voice path on any of its connections.

AXXESS ACTION: Go into Database Programming and review the cabinet's resource allocation. Make sure the system has been configured correctly. We recommend that you unequip some boards that do not need to be equipped. Then 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 by powering off and powering back on.

5000 ACTION: Go into Database Programming and review the cabinet's resource allocation. Make sure the system has been configured correctly. We recommend that you remove any expansion modules that are not needed. Then 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 by powering off and powering back on.



M5097 <b.p.d>: Unable to Dedicate Voice Channel. Resource Failure.

FIELDS: b.p.d The board/port/device of the device dedicating a voice channel.

CAUSE: The system was not able to dedicate the voice channel to this device. This device will not have any voice path connections until this problem is resolved. This is an error condition that should not occur on a non-blocking system.

AXXESS ACTION: Go into Database Programming and review the cabinet's resource allocation. Make sure the system has been configured correctly. We recommend that you unequip some boards that do not need to be equipped. Then 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 by powering off and powering back on.

5000 ACTION: Go into Database Programming and review the cabinet's resource allocation. Make sure the system has been configured correctly. We recommend that you remove any expansion modules that are not needed. Then 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 by powering off and powering back on.

M5098 <b.p.d>: Online Ignored for <type> DSS/PKM unit <limit: [limit]>

FIELDS: b.p.d The board/port/device designation of the DSS/PKM unit.

type The type of DSS/PKM unit (physical or virtual).

limit The maximum allowed DSS/PKM units of the specified type.

CAUSE: The maximum number of allowed DSS/PKM units of the specified type has been reached. The system will not allow any more DSS/PKM units of the specified type to come online until some others go offline.

AXXESS ACTION: The database needs to be programmed to allow more DSS units of the specified type. Increasing this count may affect system performance. Contact Mitel Field Service before changing the database. To increase the DSS limits, in OLM go into System\Timers and Limits and modify one of 2 database fields: “DSS Units” (For Axxess physical DSS units) or “DTI DSS Units” (for desktop interface DSS). Under System\System Information\Metadatabase modify “DSS Consoles” (for Executone DSS units).

5000 ACTION: The database needs to be programmed to allow more DSS/PKM units of the specified type. Increasing this count may affect system performance. Contact Mitel Field Service before changing the database. To increase the DSS/PKM limits, in OLM go into System\Timers and Limits and modify the “DTI DSS/PKM Units”. Under System\System Information\Metadatabase modify “DSS/PKM Units”.

FS ACTION: None.

NOTE Programmable Key Modules (PKM) are supported on the Mitel 5000 only.



M5099 <card>: Real-Time Clock is Stopped (Axxess Only)FIELDS: card The name of the card that the Real-Time Clock resides on. For Axxess, this will be

CPU020. For AXXENT, this will be ACM.

CAUSE: The operating system detected that the real-time clock is not running. This may indicate that the real-time clock is faulty.

ACTION: No action need be taken unless this warning is seen more than once or this warning is NOT immediately followed by an informative message indicating that the clock is running once again. If this warning is seen multiple times or it is not followed by the message indicating the clock is running, the Real-Time Clock chip on the CPU020 or ACM board is faulty. Replace the CPU020 or ACM board. Return the faulty CPU020 or ACM board to Mitel for diagnosis and repair, making sure to alert them of the specific nature of the problem with the Real-Time Clock.

M5100 <b.p.d>: Communications Error from <name> (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the device that sent the error message.

name A text string that specifies the type of device that sent the error message (e.g., Phone).

CAUSE: This system detected either a parity error, a framing error or an overrun error.

ACTION: Swap the phone with one that seems to work. If the problem persists, freeze and save the system history and contact Mitel Technical Support.

M5101 <b.p.d>: Error Message Lost for <name> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that sent the error message.

name A text string that specifies the type of board that sent the error message (e.g., Phone).

CAUSE: The system detected an error, but lost the message due to queue full conditions.

ACTION: Freeze and save the system history and contact Mitel Technical Support.

M5102 <b.p.d>: Incorrect Interrupt Mask for <name> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that sent the error message.


CAUSE: The analog phone card detected an incorrect interrupt mask.

ACTION: Freeze and save the system history and contact Mitel Technical Support

M5103 <b.p.d>: No Response Error from <name> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that sent the error message.


CAUSE: The AKTS card polled an analog phone and the phone failed to respond.

ACTION: None.



M5104 <b.p.d>: OMSCI Error Code from <name>FIELDS: b.p.d The board/port/device designation of the device that sent the error message.


code The OMSCI error code.

CAUSE: The analog telephone firmware detected an Octal Master/Slave Communications Interface (OMSCI) error message. The error code identifies the particular OMSCI error.

AXXESS ACTION: Swap the board with one that seems to work. If the problem persists, freeze and save the system history and contact Mitel Technical Support.

5000 ACTION: If the problem persists, freeze and save the system history and contact Mitel Technical Support.

M5105 <b.p.d>: Spurious Reset for <name> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that sent the error message.


CAUSE: The AKTS card detected a spurious reset for an analog phone.

ACTION: None.

M5106 <b.p.d>: State Error for <name> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that sent the error message


CAUSE: The analog phone firmware card detected a state logic error.


M5107 <b.p.d>: SWI Error from <name> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that sent the error message


CAUSE: The analog telephone firmware detected a SWI interrupt.


M5108 <b.p.d>: Transmit Data Register Empty for <name> (Axxess Only)



CAUSE: The system issues this warning whenever the analog phone firmware receives a Transmit Data Register Empty (TDRE) interrupt.


M5109 <b.p.d>: Timer Error for <name> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that sent the error message.


CAUSE: The analog phone firmware detected either an input capture interrupt or a timer overflow.




M5110 <b.p.d>: Transmission Error from <name> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that sent the error message.


CAUSE: The analog phone firmware detected an error while communicating with an analog phone.

ACTION: Check wiring between the phone and the chassis.

M5111 <b.p.d>: Trap Error for <name> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that sent the error message.


CAUSE: The system issues this warning whenever the analog phone firmware either receives an invalid address or executes an invalid opcode.


M5112 <b.p.d>: Spurious Reset for <name> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that sent the error message.


CAUSE: The analog phone firmware detected a watchdog timer interrupt.

ACTION: Swap the phone with one that seems to work. If the problem persists, freeze and save the system history and contact Mitel Technical Support.

M5113 <b.p.d>: <name> Received Ground Start Programming (Axxess Only)



CAUSE: The system issues this warning when the call processing software tries to program a loop-start only circuit (i.e., an LSC or LSCD circuit) as a ground start circuit.

At the present time, there are three reasons that cause this error:

x Programming a Loop-Start-Only circuit as a Ground-Start circuit. For the Japan version of the system, an LGC card cannot be configured for Ground-Start.

x Programming a Loop-Start-Only circuit to provide Japan DI functionality which requires use of a Loop-Start circuit on an LGC card.

x Programming a Loop-Start-Only circuit to provide Japan CLIP functionality which requires use of a Loop-Start circuit on an LGC card.

ACTION: Verify Database Programming for the specified circuit. If the error persists, save the database, freeze and save the system history, and contact Mitel Field Service.

FSACTION: Report the problem to the Engineering contact person for further analysis.

M5114 <b.p.d>: Reconfigure Request from <name> (Axxess Only)FIELDS: b.p.d The board/port/device designation of the device that sent the error message.


CAUSE: The analog phone card requests that call processing reconfigure the specified device. It has been corrupted by a spurious reset.

ACTION: Report excessive errors to Mitel Field Service.



M5115 PP Command Sent After <num> Tries (Axxess Only)FIELDS: num The number of attempts necessary to send the PP command to the OS.

CAUSE: The OS queues were blocked for some reason; possibly due to an extreme amount of data traffic from the Primary cabinet-pair to the Secondary Cabinet pair. This condition is more likely to occur on a quad-cabinet system; it should never happen on a single-cabinet system.

ACTION: Contact Mitel Field Service.

M5116 <b.p.d>: (RMGR) Invalid PP Response: Type = <xx>, Board = <bb>, Circuit = <cc>, MSG = <zz>


xx The type of the invalid response.

bb The board from which the invalid response came from.

cc The circuit from which the invalid response came from.

zz The invalid message.

AXXESS CAUSE: A board sent an illegal response to CP (bug in the PP firmware), CP is missing a message handler for a particular response (bug in CP), or something unexpected happened.

5000 CAUSE: An application/module sent an illegal response to CP (bug in the PP firmware), CP is missing a message handler for a particular response (bug in CP), or something unexpected happened.

ACTION: Perform freeze and save database. Contact Mitel Field Service.

M5117 <b.p.d>: (RMGR) Dialing Time-Out Error for <b.p.d>FIELDS: b.p.d The board/port/device designation of the device that sent the error message.

b.p.d The board/port/device designation of the device that encountered the error.

AXXESS CAUSE: The Dialing Processor sent a pulse-dial digit to a board and the board failed to respond on time. This should only happen in an exception case (e.g., a board was unplugged in the middle of dialing).

5000 CAUSE: The Dialing Processor sent a pulse-dial digit to an application/module and the application/module failed to respond on time. This should only happen in an exception case (e.g., an application was killed or a module was unplugged in the middle of dialing.


M5118 <b.p.d>: (RMGR) DSP <x> Status Error = <error>FIELDS: b.p.d The board/port/device designation of the device that sent the error message.

x The DSP number reporting the error.

error The DSP error ID.

CAUSE: A DSP chip reported an error through the DSP Status Channel, a communications channel used by a DSP and its Host processor. This error should not occur unless there is an error in the DSP hardware/software design.




M5119 <side>: Fiber-Optic Local Error Count too High; Rate = <rate> (Axxess Only)

FIELDS: side Either “Master” or “Slave” -- indicates the cabinet side where the error message originated.

rate The error rate, in errors per second.

CAUSE: The IOC detected that the error count has increased by more that an acceptable rate (Bit Error Rate (BET) = 10^-9). The IOC noticed that this cabinet is slave to the fiber clock; therefore, we could possibly have two masters.

ACTION: Ensure fiber-optic cable is properly installed and verify that cable has no kinks or tight bends. If the problem persists, it may be due to a failing transmitter or receiver, so replace the PCM-F board.

M5121 <side>: Fiber-Optic Remote Error Count too High; Rate = <rate> (Axxess Only)

FIELDS: side Either "Master" or "Slave" which indicates the cabinet side where the error message originated.

rate The error rate, in errors per second.

CAUSE: The IOC detected that the error count has increased by more that an acceptable rate (Bit Error Rate (BET) = 10^-9). Because this side is the master of the fiber clock, the error count is probably not due to both sides being slaves of the fiber clock.

ACTION: Ensure fiber-optic cable is properly installed and verify that cable has no kinks or tight bends. If the problem persists, it may be due to a failing transmitter or receiver, so replace the PCM-F board.

M5122 Nodes did Not Respond to Broadcast Message from Ext <eeeee>: Nodes <node_list>

FIELDS: eeeee The extension which generated the network broadcast message.

node_listThe list of nodes from which we did not receive a acknowledgement of the broadcast message.

CAUSE: The listed nodes are unreachable. A physical link in the network may be down, a node in the network may be down, or the local or a remote database may be programmed incorrectly.

ACTION: Verify that the physical network connections are intact. Verify that each node in the network is functioning correctly. Verify that the databases are programmed correctly.

M5123 <b.p.d> <board>: Incompatible ISDN FW Version = <ver1> (Expecting <ver2>) (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the board that has the incompatible ISDN firmware version.

board The board type that is plugged into the slot.

ver1 The ISDN firmware version of the board that is plugged into the slot.

ver2 The ISDN firmware version that is expected.

CAUSE: The firmware on the board needs to be updated to the correct version. The board is most-likely a PRI board. The board will power-up without the correct firmware.

ACTION: Contact Mitel Field Service to determine the correct firmware for the board. Replace the EPROMs on the board.



M5124 <b.p.d> <board>: Incompatible FW Version = <ver1> Expecting <ver2> or Higher (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the board that has the incompatible firmware version.


ver1 The firmware version of the board that is plugged into the slot.

ver2 The lowest possible value expected.

CAUSE: The firmware on the board needs to be updated to the correct version. The board will power-up without the correct firmware.


M5125 Received Call on Unequipped Trunk <b.p.d>FIELDS: b.p.d This is the hardware address of the unequipped B-channel trunk that received the call.

AXXESS CAUSE: The Central Office or private network node that this board is connected to has the indicated B-channel trunk equipped and this system has it unequipped.

5000 CAUSE: The Central Office or private network node that this system is connected to has the indicated B-channel trunk equipped and this system has it unequipped.

ACTION: Equip the B-channel trunk or have the Central Office or the private network node unequip the B-channel trunk.

M5126 <b.p.d> Jumper Prevents Boot-Code Upgrade (Axxess Only)


CAUSE: The firmware boot code on the board could use an update, but the hardware jumper is in the position that prevents the firmware from modifying the boot sector. The firmware reports this warning only when the boot sector could use an upgrade. Boot-sector upgrades are necessary only when a bug fix exists in the new code.

ACTION: Remove the card, place the jumper in the correct position (opposite the current one), and then return the board to the slot. If the card-specific code doesn't need an update, the user must force the download of the boot code by pressing the make-busy switch while inserting the card. Keep the switch pressed until the LEDs start toggling at one-second intervals which indicates the download state.

M5128 <b.p.d> Board is Out of Sync with Download Task (Axxess Only)


CAUSE: Somehow, the board and the Download Task are out of sync, and the board detected the error. Most likely, the card was expecting the boot image when the Download Task sent the card-specific image (or vice versa).

ACTION: Remove the board from the system, then replace it so that it goes through its normal power-up sequence. If the problem persists after a couple of attempts, contact Mitel Field Service.



M5129 <b.p.d> Missing Jumper Protection for Card's Boot Sector (Axxess Only)


CAUSE: The jumper that provides hardware protection to the card's boot sector is not in the protection position. During normal operation, the jumper should always be in the protection position. This message will always occur after an internal download (i.e., download of PP code over the backplane) completes and the card resets. This message will also occur if the jumper is missing or somehow got in the unprotected position.

ACTION: Remove the card, place the jumper in the protection position (usually opposite the current one), and then return the board to the slot.

M5130 <b.p.d>: Must Remove BBPC for Normal Operation (Axxess Only)


CAUSE: A Boot Block Programming Card (BBPC) is installed on the board. Most likely, it was put there for restoring code to the boot sector.

ACTION: Remove the card, remove the BBPC from its connector, and then return the board to the slot. The card will not operate properly when a BBPC is plugged in.

M5131 <b.p.d>: Boot Code Image is Empty (Axxess Only)FIELDS: b.p.d The board/port/device designation of the board targeted for a download.

CAUSE: The firmware on the board could use an update, but the boot-code image on the CPU card (in CP software) is empty.

ACTION: Contact Mitel Field Service. There is a problem with the ICP code on the CPU card. There should not be any empty images.

M5132 <b.p.d>: Name Code Image is Empty (Axxess Only)FIELDS: b.p.d The board/port/device designation of the board targeted for a download.

name The name of the code image (e.g., BRU and BRS).

CAUSE: The firmware on the board could use an update, but the boot-code image on the CPU card (in CP software) is empty.

ACTION: Contact Mitel Field Service. There is a problem with the ICP code on the CPU card. There should not be any empty images.

M5133 <time>: Threshold for <threshold> Errors Exceed on BRI Port <b.p.d>

FIELDS: time Daily or hourly.

threshold BRI error threshold type (errored seconds or severely errored seconds).

b.p.d The board/port/device designation of the board that reported the problem.

CAUSE: The BRI errors for the indicated BRI port has exceeded the specified amount (daily or hourly).

ACTION: Resolve the indicated error. These errors are meaningful only when the BRI port is on-line and working normally. If the port is off-line, attempt to bring the port back on-line. If the port is on-line, check its respective threshold (through Database Programming) and make sure it is set to its default or another reasonable value. If everything is programmed correctly and the errors still occur, resolve the problem with the CO. The error types are:

x Errored Seconds,

x Severely Errored Seconds,

x The BRI span has detected an excessive number of errors on the BRI span.



M5134 OS Version Mismatch: Version Should be at Least <version_string> (Axxess Only)

FIELDS: version_string The minimum required version for the CPU. This message uses the format [x.y.z] where x is the CP version, y is the OS version, and z is the minor version.

CAUSE: Either the CP or OS version indicated in M2033, which precedes this message, does not match the version string identified in M5134. When displayed, the CPU will not be allowed to come on-line.

ACTION: Reflash the OS on the CPU card indicated by M2033 with the correct version.

M5135 <b.p.d>: (RMGR) Invalid DSP Command: Size = <xx>, Command = <zz>


xx The size of the invalid command.

zz Offending command ID.

AXXESS CAUSE: A board sent an illegal response to CP (bug in the PP firmware), CP is missing a message handler for a particular response, or something unexpected happened.

5000 CAUSE: A system sent an illegal response to CP (bug in the PP firmware), CP is missing a message handler for a particular response (bug in CP), or something unexpected happened.

ACTION: Contact Mitel Engineering.

M5136 <b.p.d>: Caller ID Transmitter Unavailable FIELDS: b.p.d The board/port/device designation of the single-line set programmed for Caller ID.

AXXESS CAUSE: The system was not able to allocate a Caller ID transmitter to a single-line set that is programmed to receive Caller ID information. As a result, the system ignored the Caller ID information. It is possible that no Caller ID transmitters are programmed in the system. If Caller ID transmitters are programmed in the system, the OPC may not be on-line. If Caller ID transmitters are programmed and the OPC is on-line, all of the system’s Caller ID transmitters were in use when the ring was received on the single-line set.

5000 CAUSE: The system was not able to allocate a Caller ID transmitter to a single-line station that is programmed to receive Caller-ID information. As a result, the system ignored the Caller ID information sent by the Central Office. It is possible that no Caller ID transmitters are programmed in the system or all of the system's Caller ID transmitters were in use when the ring was received on the single-line station.

AXXESS ACTION: Make sure that the system is programmed to have an OPC that has at least one DSP configured to provide Caller ID transmitters. Make sure that the OPC is on-line. If this has been done, and the message persists, you will have to add more Caller ID transmitters to the system. This may require additional OPC DSP chips.

5000 ACTION: Make sure that the system is programmed to have Caller-ID transmitters.

M5137 <b.p.d>: IP SoftPhone Programmed as an IP Keyset Device is Ignored

FIELDS: b.p.d The board/port/device designation of the keyset port was programmed with an IP SoftPhone.

CAUSE: An IP SoftPhone is plugged into a port programmed to be an IP Keyset port.

ACTION: Use Database Programming to program the IP Keyset with an actual IP Keyset device or create the proper IP SoftPhone device with the corresponding type.



M5138 (RMGR) DSP Dialing Timeout Error for <b.p.d>FIELDS: b.p.d: The board/port/device designation of the device that sent the error message

CAUSE(S): The On-board DSP sent a pulse-dial digit to its host and the host failed to respond with a Digit Done response on time. This should only happen in an exception case (e.g., a call is aborted in middle of pulse-dialing).

ACTION: Perform freeze and save database. Report the problem to Mitel Technical Support.

M5139 (RMGR) DSP Digit Queue Full Error for <b.p.d>FIELDS: b.p.d: The board/port/device designation of the device that sent the error message

CAUSE(S): The On-board DSP received a DTMF Dial Digits command from its host when its Digit Queue for the specified channel was full. This should only happen in an exception case (e.g., when the system is dialing too many DTMF digits at one time on a specific channel).

ACTION: Perform freeze and save database. Report the problem to Mitel Technical Support.

M5140 IP Phone With MAC <MAC address> Locked Out Due toFailed PIN Attempts

FIELDS: MAC address: The MAC address of the locked out IP phone.

CAUSE(S): An unprogrammed IP phone exceeded the maximum number of failed PIN registration or replacement attempts.

ACTION: None.


System Messages (M0001–M9999): Engineering Warning Messages (M6000–M6999)

Engineering Warning Messages (M6000–M6999)This section documents warning messages that relate to software operation. These messages indicate minor problems that should have no noticeable effect on system operation. If there is an effect, it should not be service affecting. Resolve the problem if possible. Otherwise, report the problem to Mitel Field Service.

M6000 Invalid Reset Response Board <board>: DPR-WStat = <status>, IOC-State = <ioc_state> (Axxess Only)

FIELDS: board Board number of board with the problem.

status Dual-Port RAM Window Status.

ioc-state IOC State.

CAUSE: When attempting to reset a peripheral board, the peripheral board indicated an incorrect Dual-Port RAM status. After the IOC resets a board, the board's first response to the IOC should be DS_NEW_STATE, which has the value zero.

ACTION: If the problem persists, replace the indicated board. Return the faulty board to Mitel for repair. Include the error message information with the board.

M6001 Reset Error Found by Board <board>: IOC-State = <ioc_state>

AXXESS FIELDS: board Board number of board with the problem.


5000 FIELDS: board Number of expansion module with the problem ioc-state: IOC State.


AXXESS CAUSE: The indicated board detected an error during its reset processing. The IOC reports this error when it sees the PP in its ERROR state.

5000 CAUSE: The indicated expansion module detected an error during its reset processing. The system reports this error when it sees the PP in its ERROR state.

AXXESS ACTION: First, remove and reinsert the board. If the error persists, replace the board. Return the faulty board to Mitel for repair. Include the error message information with the board.

5000 ACTION: First, remove and reinsert the expansion module. If the error persists, replace the expansion module. Return the expansion module to Mitel for repair. Include the error message information with the expansion module.



M6002 Power-Up Board <board> Not in Reset State: PP-State = <pp_state>, IOC-State = <ioc_state>


pp_state State number of the indicated board.

ioc_state IOC State

5000 FIELDS: board Number of expansion module with the problem.

pp_state State number of the indicated expansion module.

ioc-state IOC State

AXXESS CAUSE: When attempting to power up a peripheral board, the IOC found that the board was not in its reset state. Until the IOC begins communicating with the board, the board should be in its reset state. There may be a hardware problem on the board, with the power supply, or the backplane.

5000 CAUSE: When attempting to power up an expansion module, the system found that the expansion module was not in its reset state. Until the system begins communicating with the expansion module, the expansion module should be in its reset state. There may be a hardware problem on the expansion module or the expansion bay.

AXXESS ACTION: Remove and reinsert the board. If the problem persists, replace the board. Return the faulty board to Mitel for repair. Include the error message information with the board.

5000 ACTION: Remove and reinsert the expansion module. If the problem persists, replace the expansion module. Return the faulty expansion module to Mitel for repair. Include the error message information with the expansion module.

M6003 Power-Up Invalid Board = <board>: Board ID = <brd_id>, IOC-State = <ioc_state>


brd_id Board ID reported by the peripheral board.

ioc_state IOC State.


brd_id ID reported by the expansion module.


AXXESS CAUSE: When attempting to power up a peripheral board, the board provided an invalid board ID.

5000 CAUSE: When attempting to power up an expansion module, the expansion module provided an invalid ID.

ACTION: Replace the indicated peripheral board.

5000 ACTION: Replace the indicated expansion module.



M6004 Illegal Configure State = <ioc-substate>: In-Prog Flag = <config-flag>

FIELDS: ioc-substate IOC Configuration Sub-State.

config-flag Configuration-in-Progress Boolean Flag.

AXXESS CAUSE: When attempting to power up a peripheral board, the IOC found itself in an illegal substate. This message indicates a software error in the IOC or that the IOC dynamic RAM is corrupt.

5000 CAUSE: When attempting to power up an expansion board, the system found itself in an illegal substate. This message indicates a software error in the system.

ACTION: Report the problem to the engineering contact person for further analysis.

5000 ACTION: This problem indicates that the expansion module and the system are out of synchronization. First replace the expansion module. If the problem recurs, either the expansion bay is faulty, or the system has a software error. In this case, schedule a major reset for as soon as possible. If the major reset fixes the problem, the system probably has a software error. In this case, report the problem to Mitel Field Service.

M6005 Board <board> Not Operational after Power-Up: PP-State = <pp-state>, IOC-State = <ioc-state>


pp-state The state number of the indicated board.



pp-state The state number of the indicated module.


AXXESS CAUSE: While attempting to power up a peripheral board, the indicated board did not read the OPERATIONAL state. The board should move to the OPERATIONAL state after it has processed a major or minor reset command from the IOC.

5000 CAUSE: While attempting to power up an expansion module, the indicated expansion module did not read the OPERATIONAL state. The expansion module should move to the OPERATIONAL state after it has processed a major or minor reset command from the system.

AXXESS ACTION: This problem indicates that the board's processor and the IOC are out of synchronization. First replace the peripheral board. If the problem recurs, either the board slot in the backplane is faulty, or the IOC has a software error. In this case, schedule a major reset for as soon as possible. If the major reset fixes the problem, the IOC probably has a software error. In this case, report the problem to Mitel Field Service.

5000 ACTION: This problem indicates that the expansion module and the system are out of synchronization. First, replace the expansion module. If the problem recurs, either the expansion bay is faulty or the system has a software error. In this case, schedule a major reset as soon as possible. If the major reset fixes the problem, the system probably has a software error. In this case, report the problem to Mitel Field Service.




M6006 Board <board> Not Responding: IOC-State = <ioc-state>, Sub-State = <ioc-substate>



ioc-substate IOC Configuration Sub-State.

5000 FIELDS: board Number of expansion module with the problem..


ioc-substate IOC Configuration Sub-State.

AXXESS CAUSE: While attempting to power up a peripheral board, the board stopped responding to the IOC. This error message could be forced if you remove the board just as the IOC was powering it up.

5000 CAUSE: While attempting to power up an expansion module, the module stopped responding to the system. This error message could be forced if you remove the expansion module as the system was powering it up.

AXXESS ACTION: If this message occurs frequently and the IOC is unable to power up the board, replace the board. If the problem continues, there may be a problem with the backplane or the power supply. Replace in order the backplane, power supply, and the CPU board, if necessary.

5000 ACTION: If this message occurs frequently and the system is unable to power up the expansion module, replace the module. If the problem continues, there may be a problem with the expansion bay.

M6007 Illegal Exception State = <ioc-substate>: In-Prog Flag = <exception-flag>

FIELDS: ioc-substate IOC Exception Sub-State.

exception-flag Configuration-in-Progress Flag.

AXXESS CAUSE: When attempting to power up a peripheral board, the IOC found itself in an illegal substate. This message indicates a software error in the IOC or that the IOC dynamic RAM is corrupt.

5000 CAUSE: While performing exception processing on an expansion board, the system found itself in an illegal substate. This message indicates a software error in the system.


M6008 Board <board> Not RespondingAXXESS FIELDS: board Board number of board with the problem.


AXXESS CAUSE: The indicated board stopped responding to the IOC.

5000 CAUSE: The indicated expansion module stopped responding to the system.

AXXESS ACTION: The IOC prints this message whenever a peripheral board is removed from a running system; therefore, this message is normally informational only. If this message is being printed while the indicated board is in the system, replace the board. If the problem persists, there may be a faulty backplane or CPU board. Replace the backplane or the CPU board, if necessary.

5000 ACTION: The system prints this message whenever an expansion module is removed from a running system; therefore, this message is normally informational only. If this message is being printed while the indicated expansion module is in the system, replace the expansion module.



M6009 Time-Out Awaiting Minor Init ACK: Board = <board>, IOC-State = <ioc-state>) (Axxess Only)



CAUSE: The IOC sends this message if a timeout occurs while waiting for the board to acknowledge control of the Dual-Port RAM window after the IOC sends a minor reset command to the board.

ACTION: If this problem occurs frequently, replace the board. If the problem persists, replace the backplane, then the power supply.

M6010 DPR Window Control ACK Invalid Window Status: Board = <board>, IOC-State = <ioc-state>, Status = <status>, PP-State = <pp-state> (Axxess Only)



status Dual-Port RAM Status Field.

pp-state The state the board was in when the problem occurred.

CAUSE: The IOC reports this error if the indicated peripheral board acknowledged control of the Dual-Port RAM window with an unexpected status value. The board may have interrupted the IOC before the IOC was finished with the DPR window. A spurious Dual-Port RAM (level-4) interrupt may have occurred.

ACTION: First, replace the indicated peripheral board. If the problem persists, there may be other hardware problems in the system (e.g., other peripheral boards could be causing interference with the indicated board, the CPU board may be faulty, the backplane connectors may be faulty, etc.). Methodically replace the indicated components.

M6011 DPR Receive Queue Error: Board = <board> IOC-State = <ioc-state>, Status = <status> (Axxess Only)




CAUSE: The indicated peripheral board acknowledged control of the Dual-Port RAM window with one of the following DPR status values:

x $04: The PP detected a Zero Command Length Error.

x $05: The PP detected a Maximum Command Length Error.

ACTION: This error indicates that a problem occurred during the communications between the IOC and the indicated board. If the error messages occur frequently, replace the board. If the problem persists, there may be a faulty Dual-Port RAM chip on the CPU board, replace the CPU board.



M6012 DPR Window Control ACK Invalid DPR Status: Board = <board>, IOC-State = <ioc-state>, Status = <status>, PP-State = <pp-state> (Axxess Only)




pp-state The state number of the peripheral board indicated by board.

CAUSE: The IOC reports this error if the indicated peripheral board acknowledged control of the Dual-Port RAM window with an illegal status value.

ACTION: This problem must occur many times a day before it begins to functionally impact the system. If the problem occurs repeatedly, replace the board. If the problem persists, there may be other hardware problems in the system (e.g., other peripheral boards may be causing interference with the indicated board, the CPU board may be faulty, or the backplane connectors may be faulty).

M6013 Received DPR Interrupt in Invalid State: IOC-State = <ioc-state> (Axxess Only)

FIELDS: ioc-state IOC State.

CAUSE: The IOC received a Dual-Port RAM interrupt in an unexpected state. The IOC dynamic RAM area may be corrupt.

ACTION: If this error occurs frequently, schedule a major reset for as soon as possible. Otherwise, perform a system reconfigure by pressing the reset button.

M6014 Board <board> Not in PPCB List: PPCB-List-Field = <ppcb>AXXESS FIELDS: board Board number of board with the problem.

ppcb Value of the PP Control Block List field.



AXXESS CAUSE: The IOC attempted to remove the PPCB (associated with the board address) from a null PPCB list.

5000 CAUSE: The IOC attempted to remove the PPCB (associated with the expansion module) from a null PPCB list.

AXXESS ACTION: This error indicates that some of the IOC data structures are corrupt. If the system is having problems, (i.e., certain boards do not power up, etc.) schedule a major reset for as soon as possible. Otherwise, attempt a system reconfigure by pressing the reset button.

5000 ACTION: This error indicates that some of the IOC data structures are corrupt. If the system is having problems, (i.e., certain expansion modules do not power up, etc.) schedule a major reset for as soon as possible.



M6015 Board <board> Not Found in PPCB List <ppcb>AXXESS FIELDS: board Board number of board with the problem.




AXXESS CAUSE: The IOC attempted to remove the PPCB (associated with the board address) from the indicated PPCB list, but it could not be found.

5000 CAUSE: The IOC attempted to remove the PPCB (associated with the expansion module) from the indicated PPCB list, but it could not be found.

AXXESS ACTION: This error indicates that some of the IOC data structures are corrupt. If the system is having problems, (i.e., certain boards do not power up, etc.) schedule a major reset for as soon as possible. Otherwise, attempt a system reconfigure by pressing the reset button.

5000 ACTION: This error indicates that some of the system data structures are corrupt. If the system is having problems, (i.e., certain expansion modules do not power up, etc.) schedule a major reset for as soon as possible.

M6016 Illegal MAJOR State (<major-substate>)FIELDS: major-substate major reset sub-state value.

AXXESS CAUSE: While performing a major reset, the IOC found itself in an illegal substate. This message indicates a software error in the IOC or that the IOC dynamic RAM is corrupt.

5000 CAUSE: While performing a major reset, the system found itself in an illegal substate. This message indicates a software error in the system.

ACTION: Schedule a major reset for as soon as possible.

M6017 Time-Out Awaiting MAJOR Init ACK: Board <board> (Axxess Only)


CAUSE: The IOC sends this message if a timeout occurs while waiting for the PP to acknowledge control of the Dual-Port RAM window during major reset processing.

ACTION: If the IOC cannot power up the indicated peripheral board, replace the board.

M6018 Illegal Minor State <minor-substate>FIELDS: minor-substate Minor reset sub-state value.

AXXESS CAUSE: While performing minor reset (a soft reset that tries to clean up any system problems by dropping only the calls it has to) processing, the IOC found itself in an illegal substate. This indicates a software error in the IOC or that the IOC dynamic RAM is corrupt.

5000 CAUSE: While performing minor reset (a soft reset that tries to clean up any system problems by dropping only the calls it has to) processing, the system found itself in an illegal substate. This indicates a software error in the system.

ACTION: Schedule a major reset for as soon as possible.

M6019 NULL Queue Deallocate AttemptFIELDS: None.

CAUSE: The IOC attempted to deallocate a NULL queue node. If this error occurs, the IOC suffered a software error probably due to data corruption.




M6020 Input Queue Illegal Msg Length = <length>: 1st-Byte = <byte>

FIELDS: length Value of the message length field.

byte First data byte of illegal message.

AXXESS CAUSE: While processing a message for the input service queue, the IOC found a message with a length of zero or one. This message indicates that a user task (or an On-Line Monitor user) sent an invalid message to the IOC or that the data queues are corrupt.

5000 CAUSE: While processing a message for the input service queue, the system found a message with a length of zero or one. This message indicates that a user task (or an On-Line Monitor user) sent an invalid message to the system or that the data queues are corrupt.

ACTION: If the error occurs while sending a message using the On-Line Monitor, check the format of the message and try again. Otherwise, report the problem to the engineering contact person for further analysis.

M6021 Input Queue Illegal Device Type: Msg Length = <length>, Device-Type = <type>, 2nd-Byte = <byte>


type Value of the device type field.

byte Second data byte of illegal message.

AXXESS CAUSE: While processing a message for the input service queue, the IOC found a message with an illegal device type. This message indicates that a user task (or an On-Line Monitor user) sent an invalid message to the IOC or that the data queues are corrupt.

5000 CAUSE: While processing a message for the input service queue, the system found a message with an illegal device type. This message indicates that a user task (or an On-Line Monitor user) sent an invalid message to the system or that the data queues are corrupt.


M6022 Input Queue Illegal Command: Msg Length = <length>, Device-Type = <type>, Command = <command>



command Value of the command number field.

AXXESS CAUSE: While processing a message for the input service queue, the IOC found a message with an undefined command ID. This message indicates that a user task (or an On-Line Monitor user) sent an invalid message to the IOC or that the data queues are corrupt.

5000 CAUSE: While processing a message for the input service queue, the system found a message with an undefined command ID. This message indicates that a user task (or an On-Line Monitor user) sent an invalid message to the system or that the data queues are corrupt.




M6023 Input Queue Illegal Board = <board>: Device Type = <type>,Command = <command>

FIELDS: board Board number.



5000 FIELDS: board Number of expansion module.



AXXESS CAUSE: While processing a message for the input service queue, the IOC found a command with an illegal board address field. This message indicates that a user task (or an On-Line Monitor user) sent an invalid message to the IOC or that the data queues are corrupt.

5000 CAUSE: While processing a message for the input service queue, the system found a command with an illegal expansion module address field. This message indicates that a user task (or an On-Line Monitor user) sent an invalid message to the system or that the data queues are corrupt.

ACTION: If the error occurs while sending a message using On-Line Monitor, check the message format and try again. Otherwise, report the problem to the engineering contact for further analysis.

M6024 Board <board> Unexpected State: IOC-State = <ioc-state>,PP-State = <pp-state>

AXXESS FIELDS: board Board number of the problem board.


pp-state The state number of the PP indicated by the board.



pp-state The state number of the PP indicated by the module.

AXXESS CAUSE: While checking for receive messages from the indicated peripheral board, the IOC noticed that the PP made an unexpected state transition. If the board reset itself unexpectedly, the IOC could report this error.

5000 CAUSE: While checking for receive messages from the indicated expansion module, the system noticed that the PP made an unexpected state transition. If the board reset itself unexpectedly, the system could report this error.

AXXESS ACTION: If the IOC continues to report this error, replace the board.

5000 ACTION: If the system continues to report this error, replace the expansion module.

M6025 Board <board> Message with Invalid Length <length> (Axxess Only)

FIELDS: board Board number of the problem board.

length Value of the message length field.

CAUSE: While receiving a message from the Dual-Port RAM of the indicated board, the IOC found the message to have an invalid length byte. The DPR receive queue pointers may be corrupt.

ACTION: The IOC attempts to clean up the Dual-Port RAM by itself, so no action should be necessary. If the problem persists, replace the peripheral board. If the problem persists after replacing the board, there may be a hardware problem with the CPU board. Replace the CPU board.



M6026 SEND – Invalid Board Address <board>AXXESS FIELDS: board Board number of the problem board.

5000 FIELDS: board Number of the problem expansion module.

AXXESS CAUSE: The IOC received a send request message with an illegal destination board address. This error usually indicates that a user task (the CP software, for example) sent an invalid message.

5000 CAUSE: The system received a send request message with an illegal destination expansion module address. This error usually indicates that a user task (the CP software, for example) sent an invalid message.



M6027 DKSC Illegal Message Length <length>FIELDS: length Value of the message length field.

AXXESS CAUSE: The IOC received a message from a user task (the CP software, for example) with an illegal message length. This error could indicate a software error (in CP or the OS) or data corruption.

5000 CAUSE: The system received a message from a user task (the CP software, for example) with an illegal message length. This error could indicate a software error (in CP or the OS) or data corruption.


M6028 DKSC Illegal Port: Board = <board> MsgLength = <length>Command = <command> Port = <port>

AXXESS FIELDS: board Board number of the problem board.



port Value of the port number field.




port Value of the port number field.

AXXESS CAUSE: The IOC received a message from the CP software for a phone, but the circuit number field is illegal. This error could indicate a software error (in CP or the OS) or data corruption.

5000 CAUSE: The system received a message from the CP software for a phone, but the circuit number field is illegal. This error could indicate a software error (in CP or the OS) or data corruption.





M6029 DPR Window Control ACK Time-Out: Board = <board>,Status = <status>, PP-State = <pp-state> (Axxess Only)

FIELDS: board Board number of the problem board.


pp-state The state number of the Peripheral Board indicated by board.

CAUSE: The IOC reports this error when it times-out waiting for a peripheral board to acknowledge control of the Dual-Port RAM window while in the DATA state. Either the IOC lost the level-4 DPR window interrupt or the peripheral board did not interrupt the IOC within the allotted time.

ACTION: This error may occur occasionally with no harm to the system. If this error occurs frequently, replace the indicated peripheral board. If the error occurs from several different boards the situation is much more complex to diagnose. Any one of the boards in the system could be experiencing hardware problems, or there may be data corruption on the CPU board. Replace the indicated boards. If the problem persists, perform a major reset.

M6030 Timer Interrupt in Invalid State <ioc-state> (Axxess Only)FIELDS: ioc-state IOC State.

CAUSE: The IOC received a level-3 timer interrupt while in an unexpected state. The IOC's dynamic RAM area may be corrupted.

ACTION: If the errors occur frequently, schedule a major reset for as soon as possible. Otherwise, perform a system reconfigure by pressing the reset button.

M6031 Interrupt Timer with Invalid Time-Out ID <timer_ID>FIELDS: timer_ID Timer ID number.

AXXESS CAUSE: The IOC attempted to post a wakeup timer for an undefined timer ID. This error indicates a software error due to data corruption.

5000 CAUSE: The system attempted to post a wakeup timer for an undefined timer ID. This error indicates a software error due to data corruption.


M6032 Processed Packet to UnInitialized DKSC Port = <b.p.d>: Queue-Type = <type>

FIELDS: b.p.d. The board/port designation of the phone causing the error message.

type Circuit queue type.

AXXESS CAUSE: The IOC reports this error when it attempts to process a data packet for an uninitialized (i.e., yet to power up) phone. This error could indicate that the indicated phone or data port module is faulty.

5000 CAUSE: The system reports this error when it attempts to process a data packet for an uninitialized (i.e., yet to power up) phone device. This error could indicate that the indicated phone or data port module is faulty.

AXXESS ACTION: First, replace the indicated phone. If the Queue Type field is three (3), the data port module attached to the indicated phone could be faulty. If the error occurred by unplugging a phone or data port module, remove and reinsert the associated DKSC board. If problems persist, perform a system reconfigure by pressing the reset button.

5000 ACTION: First, replace the indicated phone. If the Queue Type field is three (3), the data port module attached to the indicated phone could be faulty. If the error occurred by unplugging a phone or data port module, remove and reinsert the associated DE module.



M6033 DKSC Illegal Command: Board = <board> Msg Length = <length> Command = <command>

FIELDS: board Board number of the device reporting the problem.



AXXESS CAUSE: The IOC detected an illegal DKSC command. This error usually indicates a software error where CP and the IOC are out of synchronization.

5000 CAUSE: The system detected an illegal DE module command. This error usually indicates a software error where CP and the system are out of synchronization.

ACTION: If the problem occurs frequently, 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. Provide the CP Error Information and the database.

M6034 IOC Timed-Out Waiting for DSP <dsp> to Reset (Axxent Only)

FIELDS: DSP Number of the DSP that timed-out.

CAUSE: The IOC tried to reset a DSP but got no response from the DSP.

ACTION: Replace the DSP chip.

M6035 DSP <number> Not Responding (Axxent Only)FIELDS: number DSP that stopped responding.

CAUSE: Note that this is an AXXENT only warning. The indicated DSP stopped responding to the IOC.

ACTION: The IOC prints this message whenever a DSP is removed from a running system; therefore, this message is normally informational only. If this message is being printed while the indicated DSP is in the system, replace the DSP. If the problem persists, there may be a faulty DSP. Replace the DSP, if necessary.

M6036 DSP DPR Window Control ACK Time-Out: DSP = <number> Status = <status> (Axxent Only)

FIELDS: number DSP number of the problem DSP.


CAUSE: Note that this is an AXXENT only warning. The IOC reports this error when it times-out waiting for a DSP to acknowledge control of the Dual-Port RAM window while in the DATA state. Either the IOC lost the level-4 DPR window interrupt or the DSP did not interrupt the IOC within the allotted time.

ACTION: This error may occur occasionally with no harm to the system. If this error occurs frequently, replace the indicated DSP. If the error occurs from several different DSPs, the situation is much more complex to diagnose. Any one of the DSPs in the system could be experiencing hardware problems, or there may be data corruption on the ACM board. Replace the ACM boards. If the problem persists, perform a major reset.

M6037 Not Compatible SW Version in Board <board> (Axxess Only)


CAUSE: The software on the card was not properly updated with the latest software and is not compatible with this call processing software installed.

ACTION: Upgrade the software to the latest version.



M6038 Fiber Error Class (Axxess Only)FIELDS: None.

CAUSE: This is the main class of Fiber-Optic Error messages. This error should never actually print. It is here only as a placeholder. See error messages in the range M8010 (page 147) through M8024 (page 150) for specific fiber-optic error messages.

ACTION: None.

M6046 Board <board> Reset Itself – <status>: IOC-State = <ioc-state>, PP-State = <pp-state> (Axxess Only)


status Dual-Port RAM status field.


pp-state State number of the peripheral board.

CAUSE: The IOC reports this error if the indicated peripheral board acknowledged control of the Dual-Port RAM window with a status value of any of the following:

x Internal-RAM Data Corruption

x ROM Checksum Error

x External RAM Error

x DPR Interrupt Timeout

ACTION: The action depends on the status as follows:

x Internal-RAM Data Corruption: No action is necessary as long as this error does not occur again. If the error recurs there may be a faulty 8051/8052 processor on the peripheral board. In this case, replace the processor on the board. If the error continues, replace the peripheral board because there may be a hardware failure on the board.

x ROM Checksum Error: Replace the ROM(s) on the indicated peripheral board (this may include replacing the processor if internal ROM is used by the board). If the error recurs, replace the peripheral board because there may be a hardware failure on the board.

x External RAM Error: Replace the external RAM. If the error recurs, replace the peripheral board because there may be a hardware failure on the board.

x DPR Interrupt Timeout: Because this board detected the absence of a communications interrupt from the system, the source of the error could be anywhere in the system software, system hardware, or board hardware. If the system (including the peripheral board) was previously working, chances are that there is a system software error (certain condition not handled properly). Schedule a major reset for as soon as possible. If the peripheral board was recently plugged in and the system was previously working, replace the peripheral board. If the error still occurs with the new board, use a different slot, a new system cabinet (faulty backplane), or a new CPU because there may be communications problems with that particular slot.

M6047 Serial Port <b.p.d> Lost at Least One Outgoing Message (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the hardware address of the serial port that lost the message.

CAUSE: The serial port was unable to send the message because it was flooded with too much information and could not buffer everything. This can happen if hardware handshaking is enabled on a serial port and the far-end device is disconnected. We only print this message the first time we lose an outgoing message after a successful send.

ACTION: If the port is no longer in use by an external device, remove the serial port from the Database programming.



M6050 OS Request <request>: Unexpected Status <status>FIELDS: request The executive request number.

status The status returned from the OS request.

CAUSE: This message indicates an error in the CP software or the OS software. The CP software invoked an OS executive request, and the OS returned a result that was different than expected. This error may affect system performance.

There was a change to the CSTA wait to reopen port timer in the system timers area in 8.xx software. Select the On-Line Monitor under View and then go to system timers and limits. Find the timer CSTA wait to reopen port timer and change the value to 0. You must do a system reset for this change to take affect. Refer to Knowledge Base Answer ID 1782 for the Corrective Action. If the problem persists perform the recommended action.



M6051 <routine>: OS Request <request>: Queue Full Status Returned

FIELDS: routine The name or address of the routine that generated the error message.

request The executive request number.

CAUSE: This message indicates an error in the CP software or the OS software. The CP software invoked an OS executive request, and the OS returned a result that was different than expected, and is typically an error response. This error may affect system performance.


M6052 OS Request <request>: Clock Failure Status ReturnedFIELDS: request The executive request number.

AXXESS CAUSE: The CP software tried to post an absolute timer or set the date/time, but the OS returned a result indicating a failure status. This failure will affect system performance. This failure may be due to a hardware problem on the MEM board, which contains the hardware real-time clock, or the CPU board. This message indicates a software error.

5000 CAUSE: The CP software tried to post an absolute timer or set the date/time, but the OS returned a result indicating a failure status. This failure will affect system performance. This failure may be due to a hardware problem with the real-time clock, or the main board. This message indicates a software error.

AXXESS ACTION: Replace the MEM board or the CPU board. If the problem recurs, 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.

5000 ACTION: Replace the main board. If the problem recurs, 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.




M6053 OS Request <request>: Invalid Delay <delay> (Axxess Only)FIELDS: request The request executive number.

delay The delay value requested.

CAUSE: The CP software tried to post a relative timer, but the OS returned a result indicating a failure status due to an invalid delay value (offset from the current time to the time the timer should expire). This error will affect system performance. This message indicates a software error.


M6054 OS Request <request>: Invalid Task ID <task-id> (Axxess Only)

FIELDS: request The executive request number.

task-id The invalid task identifier.

CAUSE: The CP software tried to post a timer for a task, or post a message to a task, but the OS returned a result indicating the task number is invalid. This error may affect system performance. This message indicates a software error.


M6055 OS Request <request>: Attempted to Abort Non-Preemptable Task <task-id> (Axxess Only)


task-id The identifier of the task to be aborted.

CAUSE: The CP software tried to abort a task, but the OS returned a result indicating the task to be aborted is a non-preemptable task, which cannot be aborted by design. This error may affect system performance. This message indicates a software error.


M6056 OS Request <request>: Invalid Message Length <length> (Axxess Only)


length The length of the message.

CAUSE: The CP software tried to send a message to a task or to one of the peripheral boards or devices, but the OS detected in invalid length field in the message. The OS discarded the message. This error may affect system performance. This message indicates a software error.





M6057 OS Request <request>: Invalid Board Number <b.p.d> (Axxess Only)


b.p.d The invalid board/port specifier.

CAUSE: The CP software tried to send a message to one of the peripheral boards or devices or to allocate a serial port, but the OS detected an invalid board number in the message or request. The OS discarded the message or request. This error may affect system performance. This message indicates a software error.


M6058 OS Request <request>: Invalid Port Number <b.p.d> (Axxess Only)


b.p.d The invalid board/port specifier.

CAUSE: The CP software tried to send a message to one of the peripheral boards or devices or to allocate a serial port, but the OS detected an invalid port number in the message or request. The OS discarded the message or request. This error may affect system performance. This message indicates a software error.


M6059 OS Request <request>: Timer for Task <task-id> Not Found <byte_list> (Axxess Only)


task-id The task number supplied for the request.

byte_list The bytes indicating the timer to cancel.

CAUSE: The CP software tried to cancel a timer, but the OS did not find a timer that matches the indicated byte list. The OS ignored cancel request. This error will not affect system performance. This message indicates a software error.


M6060 OS Request <request> for <b.p.d>: Port Already Allocated (Axxess Only)


b.p.d The board/port number supplied for the requested function.

CAUSE: The CP software tried to allocate a serial port, but the OS denied the request because the serial port is already allocated. The OS discards the duplicate allocate request. This error may affect system performance. This message indicates a software error.




M6061 OS Request <request> for <b.p.d>: Maximum Ports Already Allocated (Axxess Only)



CAUSE: The CP software tried to allocate a serial port, but the OS indicated that the maximum number of serial ports have already been allocated. Serial ports and DSS units that are equipped contribute to the count of allocated serial ports. The OS discarded allocate request. This error may affect system performance. This message indicates a software error or a database error (database error due to a software error).


M6062 OS Request <request> for <b.p.d>: Port Off-Line (Axxess Only)



CAUSE: The CP software tried to allocate a serial port, but the OS indicated that the indicated board/port is off-line (The OS prohibits the allocation of an off-line ports because there port is not plugged in). The OS discarded the allocate request. This error may affect system performance. This message indicates a software error.


M6064 OS Request <request> Logical Port <port>: Port Unavailable (Axxess Only)


port The logical serial port number.

CAUSE: The CP software tried to deallocate a serial port, but the OS indicated that the indicated logical port number is undefined. The OS discarded the deallocate request. This error will not affect system performance. This message indicates a software error.


M6065 OS Request <request> for Logical Port <port>: Port Not Allocated (Axxess Only)



CAUSE: The CP software tried to perform an request (open, deallocate, or configure) on a serial port, but the OS indicated that the logical serial port number is not allocated. The OS discarded the request. This error may affect system performance. This message indicates a software error, and may be due to any of the allocate warning messages (M6060, M6061, or M6062) because the allocate failed.




M6066 OS Request <request> for Logical Port <port>: Incompatible Protocol <value> (Axxess Only)



value The protocol value (in binary).

CAUSE: The CP software tried to open a port using the ASCII protocol (normal serial communication), but the OS indicated that the logical serial port uses a different protocol. The packet protocol used for ASAI serial ports is the only other protocol, and the ASAI device (Voice Processing or Database Programming computer) must be logged into the port to use the packet protocol. The OS discards the open request. This error may affect system performance. This message indicates a software error.


M6067 OS Request <request>: Invalid Use of Preemptable Request by Task <task-id> (Axxess Only)


task-id The identifier of the task performing the request.

CAUSE: The specified non-preemptable task requested an operation on a serial port that only a preemptable task may request. The OS discarded the request. This error may affect system performance. This message indicates a software error.


M6068 OS Request <request>: Invalid Time Buffer <buffer>FIELDS: request The executive request number.

buffer The contents of the buffer.

CAUSE: The CP software requested that the OS set the system time, but OS indicated that the time buffer was invalid. The OS discarded the request. This error may affect system performance. This message indicates a software error.


M6069 OS Request <request>: Invalid Date Buffer <buffer>FIELDS: request The executive request number.

buffer The contents of the buffer.

CAUSE: The CP software requested that the OS set the system date, but the OS indicated that the date buffer was invalid. The OS discarded the request. This error may affect system performance. This message indicates a software error.




M6070 System History of Node <frozen_node> AutomaticallyFrozen Due to Software Exception (Axxess Only Pre v8.2)

FIELDS: frozen_node Node number of the node that was frozen.

CAUSE: The system history was automatically frozen due to a software exception. There are places within the code of Call Processing Software that request automatic freezes when certain exceptional conditions arise.


M6071 System History of Node <frozen_node> Automatically Frozen Due to Freeze-On String

FIELDS: frozen_node Node number of the node that was frozen.

CAUSE: The system history was automatically frozen due to the output of a "freeze-on" string. The system provides the ability to request an automatic freeze when a programmed "freeze-on" string is output to MSG Print.


M6072 Automatic System History Freeze of Node <node_num>Failed: Already Frozen (Axxess Only Pre v8.2)

FIELDS: node_num node number of the node that attempted the automatic freeze.

CAUSE: The system attempted to automatically freeze the System History, but the System History was already frozen.


M6073 <b.p.d> Automatic Equip of <board> Failed: <reason>AXXESS FIELDS: b.p.d The board/port/device designation of the board that could not automatically equip.

board The board type of the board that could not automatically equip.

reason The reasons the automatic equip failed.

5000 FIELDS: b.p.d The board/port/device designation of the expansion module the could not automatically equip.

board The type of the expansion module that could not automatically equip.

reason The reasons the automatic equip failed.

AXXESS CAUSE: The system attempted to automatically equip the board, but the system could not successfully accomplish it.

5000 CAUSE: The system attempted to automatically equip the expansion module, but the system could not successfully accomplish it.

AXXESS ACTION: The action is dictated by the reason it failed:

x Database Programming In Session: A Database Programming session is currently in use. The Database Programming could be due to programming through applications, phone programming, or an OAI application. Terminate the Database Programming session and re-insert the board into the slot or equip the board through Database Programming.

x Board Not Supported: The board is not supported to automatically equip. Equip the board through Database Programming.



5000 ACTION: The action will be dictated by the reason it failed.

x Database Programming in Session: A Database Programming session is currently in use. The Database Programming could be due to programming through applications, phone programming or an OAI application. Terminate the Database Programming session and re-insert expansion module or equip the expansion module through Database Programming.

x Expansion Module Not Supported: The expansion module is not supported to automatically equip. Equip the expansion module through Database Programming.

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.

M6080 <routine>: Null Pointer ReceivedFIELDS: routine The name or address of the routine that generated the error message

CAUSE: The CP software detected an invalid pointer while accessing internal data structure. This message indicates a software error.

ACTION: None. This error generally causes no improper system operation. If the system operates improperly, schedule a delayed major reset or perform an immediate major reset depending upon how poorly the system is operating. When convenient notify Mitel Field Service with the information in the message.

M6081 Extra Timer for Task <task-id>: <timer>FIELDS: task-id The name or number of the task that received the timer.

timer The name or number of the extra timer.

CAUSE: The indicated task received an extra timer input when the task did not expect the timer.

ACTION: None. The error is not fatal and may not be noticeable. When convenient, notify Mitel Field Service with the information in the message.

M6082 Unrecognized Timer for Task <task-id>: <timer>FIELDS: task-id The name or number of the task that received the timer.

timer The name or number of the unrecognized timer.

CAUSE: The indicated task received a timer input that the task does not recognize.

ACTION: None. The error is rarely fatal and generally causes no improper system operation. When convenient, notify Mitel Field Service with the information in the message.

M6083 Unexpected Message for Task <task-id>: <msg>FIELDS: task-id The name or number of the task that received the message.

msg The name of the message.

CAUSE: The indicated task received a message that the task does not recognize.

ACTION: None. The error is rarely fatal and generally causes no improper system operation. If the system operates improperly, schedule a delayed major reset or perform an immediate major reset depending upon how poorly the system is operating. When convenient, notify Mitel Field Service with the information from the message.



M6084 Unrecognized Message for Task <task-id>: <msg>FIELDS: task-id The name or number of the task that received the message.

msg The name of the message.

CAUSE: The indicated task received a message that the task did not recognize.

ACTION: None. The error is rarely fatal and generally causes no improper system operation. If the system operates improperly, schedule a delayed major reset or perform an immediate major reset depending upon how poorly the system is operating. When convenient, notify Mitel Field Service with the information from the message.

M6085 <b.p.d> On-Line Ignored for PRI Board, Check Advanced CO Interfaces (Axxess Only)

FIELDS: b.p.d The board, port, and device numbers of the PRI board which was ignored.

CAUSE: The Advanced CO Interfaces Premium Feature is not enabled.

ACTION: Enable the Premium Feature for Advanced CO Interfaces.

M6090 DOS Operation <op> Failed: File = <file>, Access = <type>,Handle = <handle>, Result = <result>

FIELDS: op The number of the DOS operation that failed on the voice processing unit.

file The name of the file on the voice processing unit that the software tried to access.

type The type of access requested.

handle The “handle” number of the file.

result The result returned by DOS.

AXXESS CAUSE: This occur if any of the DOS file operations fail. If there is no diskette in the drive during a database save or restore, for example, then any access to that drive will result in one of these messages.

5000 CAUSE: (BVM Only) - This occurs if any of the DOS file operations fail.

(VPU/EM Only) - This occurs if any of the DOS file operations fail. If there is no diskette in the drive during a database save or restore, for example, then any access to that drive will result in one of these messages.

AXXESS ACTION: If you attempted database save or restore, make sure the drive contains formatted diskette. The severity of this message depends on what was happening when the message occurred. If these messages correspond with the system not functioning properly, notify Mitel Field Service.

5000 ACTION: (BVM Only) - The severity of this message depends on what was happening when the message occurred. If these messages correspond with the system not functioning properly, notify Mitel Field Service.

(VPU/EM Only) - If you attempted database save or restore, make sure the drive contains formatted diskette. The severity of this message depends on what was happening when the message occurred. If these messages correspond with the system not functioning properly, notify Mitel Field Service.


M6091 Invalid Event in State <state>FIELDS: state The name of the state where the invalid event occurred.

CAUSE: The Voice Processing software detected an unexpected event (input) in the indicated Voice Processing state. This error indicates a software error and may be service affecting.




M6092 Attempt to Reference Nonexistent Mailbox <mailbox>FIELDS: mailbox The extension number of the mailbox.

CAUSE: This message may occur if someone logged on to a mailbox at the same time you deleted that mailbox using Database Programming.

ACTION: If this message occurs when no one is programming the database, the message indicates a software error. Notify Mitel Field Service.


M6093 Attempt to Request Operation from Null Audio PortFIELDS: None.

CAUSE: This message indicates a Voice Processor internal software error.



M6094 HW System Out of Sync for <b.p.d> Ext <eeeee>FIELDS: b.p.d The board/port/device number where the hardware input was received.

eeeee The extension number of the expected device.

CAUSE: When the hardware system (part of the CP software) receives and input from a device, the hardware system routes the input to the appropriate internal device-processing routine using the extension number of the device. However, the hardware system could not find the extension number in the internal data structures. This message may occur while the system is processing an extension change request from Database Programming.

ACTION: If this message occurred during extension change processing, allow the system to come to idle; the problem should not recur. If the message recurs, there may be a software error. Freeze the system history. Then use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.


M6095 <Voice_Mail_Unit>: Minor Version MismatchFIELDS: Voice_Mail_Unit The voice mail unit (voice processing unit).

CAUSE: The minor version between the voice processing unit and system are different. This message occurs when you upgrade the voice processing unit without upgrading the system. The system will function normally.

ACTION: None.

M6096 CP Timed Out Trying to Setup Call to ASAI DeviceFIELDS: None.

CAUSE: The ASAI peer device (either the voice processing unit or the Database Programming computer) did not respond to a setup message sent by the CP software. This error may occur if someone calls voice processing in the first thirty seconds that the connection between the voice processing and the system fails because thirty seconds must elapse before the system detects the link outage. During those thirty seconds, the CP software attempts to send calls to the voice processing unit, but the computer will not respond.

ACTION: If the problem occurs frequently, freeze the system history. Then use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.



M6097 Exception Log Index Error – Reset to First RecordFIELDS: None.

AXXESS CAUSE: The system detected data corruption in an exception log record index. This is normal upon power-up of a new CPU, by defaulting the database or uploading new version of software to the CPU card. If this occurs at any other time, it may be due to a faulty RAM chip, a faulty CPU board, or faulty software.

5000 CAUSE: The ASAI peer device (either the voice processing unit computer or the Database Programming computer) did not respond to a setup message sent by the CP software. This error may occur if someone calls the voice processing unit in the first thirty seconds that the connection between the voice processing unit and the system fails because thirty seconds must elapse before the system detects the link outage. During those thirty seconds, the CP software attempts to send calls to the voice processing unit computer, but the computer will not respond.

AXXESS ACTION: If this occurs at any time other than the normal conditions described in the “Cause(s)” section, contact Mitel Field Service and replace the CPU board. This problem could occur at a later time in a different location causing a more serious, service-affecting result.

5000 ACTION: If this occurs at any time other than the normal conditions described in the “Cause” section, contact Mitel Field Service and replace the processor module. This problem could occur at a later time in a different location causing a more serious, service affecting result.

FSACTION: If this occurs at any time other than the normal conditions, report the problem to the engineering contact person for further analysis. Provide the CP Error Information and the database.

M6098 Exception Log Record Checksum Failure – Record Cleared at <address>

FIELDS: address This is the address that holds the cleared exception log record.

AXXESS CAUSE: The system detected data corruption in an exception log record. This is normal upon power-up of a new CPU, by defaulting the database or uploading new version of software to the CPU card. If this occurs at any other time, it may be due to a faulty RAM chip, a faulty CPU board, or faulty software.

5000 CAUSE: The system detected data corruption in an exception log record. This is normal upon power-up of a new system, by defaulting the database or uploading new version of software to the system. If this occurs at any other time, it may be due to faulty software or a faulty processor module.

AXXESS ACTION: If this occurs at any time other than the normal conditions described in the “Cause(s)” section, contact Mitel Field Service and replace the CPU board. This problem could occur at a later time in a different location causing a more serious, service-affecting result.


FSACTION: If this occurs at any time other than the normal conditions, report the problem to the engineering contact person for further analysis. Provide the CP Error Information and the database.



M6099 Corrupted Queue was Cleared: <queue_name>FIELDS: queue_name This is the name of the queue that was detected to be invalid and was cleared.

AXXESS CAUSE: The data in the queue was corrupted. This is normal upon power-up of a new CPU, by defaulting the database, manually clearing the queues and uploading new version of software to the CPU card. If this occurs at any other time, it may have been caused by a faulty RAM chip, a faulty CPU card, or faulty software.

5000 CAUSE: The data in the queue was corrupted. This is normal upon power-up of a new system, by defaulting the database or uploading new version of software to the system. If this occurs at any other time, it may be due to faulty software or a faulty processor module.

AXXESS ACTION: If this occurs at any time other than the normal conditions described in the “Cause(s)” section, contact Mitel Field Service and replace the CPU board. This problem could occur at a later time in a different location causing a more serious, service affecting result.


FSACTION: If this occurs at any time other than the normal conditions, report the problem to the engineering contact person for further analysis. Provide the CP Error Information (as much as possible) and the database.

M6100 CPU with MAC Address <macaddr> Does Not have ATM Only PAL (Axxess Only)

FIELDS: macaddr The MAC address of the CPU that does not have the ATM Only PAL.

CAUSE: The PAL on the PCMA board is not an ATM PAL.

ACTION: Replace the PAL on the indicated board with an ATM PAL.

M6101 Message System Version <version> Not Compatible Upgrade Node <node>

FIELDS: version The system message version of the node attempting to connect to the system.

node The number of the node with the incorrect version

AXXESS CAUSE: An incompatible node has attempted to connect to this node.

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.

M6102 Extension List Failure <reason>FIELDS: reason The Extension List Command that failed.

CAUSE: An internal software error has occurred.


FSACTION: Freeze system and save the database. Report the problem to the engineering contact person for further analysis.

NOTEFor v5.2, the system message version is 13; for v5.3, it is 15. Therefore, if a node has message version 14 or a version earlier than 13, this warning message will be sent.



M6103 Exceeded Max Number of Off-Node Devices: Failed to Create <id>

FIELDS: id The off-node device ID that was not created.

CAUSE: The maximum number of off-node devices has been reached.

ACTION: Log into Database Programming and 1) Remove unused off-node devices; 2) Consolidate off-node devices as wildcards; 3) As a last resort, increase the number of off-node devices on the system. If wildcards are used, keep in mind that the wildcards cannot have reference to a DSS-BLF key or a voice mailbox.

M6104 Generic Resource Failure <reason>: Data = <data> (Axxess Only)

FIELDS: reason The generic resource reason for the failure.

data Additional data specific to the reason.

CAUSE: An external resource failure, which is most likely an ATM signaling error, has occurred.

ACTION: No action is necessary for rare occurrences. If this error occurs many times within a short period of time, however, contact Mitel Field Service.

M6105 On-Line Failure Board <board> – Single Cabinet System (Axxess Only)

FIELDS: board The board number of the board that failed to come on-line.

CAUSE: The system supports a single-cabinet system only, and a board in the second cabinet is trying to come on-line.

ACTION: Update the software license to support a dual-cabinet system.

M6106 Message Print Queue Copy Allocation FailedFIELDS: None.

CAUSE: When performing a system freeze, Call Processing allocates storage for a complete copy of the entire Message Print queue. If the system is low on heap, the allocation for the storage space fails.

ACTION: None.

M6107 Datagram Message Cannot be Routed: <msg_name>FIELDS: msg_name The name of the datagram message that cannot be routed.

CAUSE: The system lost the link to remote nodes so the message cannot be routed to the remote node.

ACTION: Check private networking link status.

M6108 No Node Route Group Programmed for Node <node>FIELDS: node The node Call Processing could not route the message to.

CAUSE: Call Processing received a message, however, it does not have a path back to the source of the message.

ACTION: Check Database Programming to make sure the node is programmed and there is path to that node.



M6109 Record-A-Call Cannot Record Agent Helper or SupervisorFIELDS: None.

CAUSE: This message warns the user of one of the three scenarios: If a supervisor barges in on an agent that is currently recording his/her call OR a supervisor is recording an agent that requests agent help OR a supervisor has left a record-a-call recording an agent’s call and a second supervisor decides to barge in on the call. Because of hardware limitations, the supervisor’s or agent’s record-a-call cannot record the agent helper’s or supervisor’s voice.

ACTION: None.

M6110 Unable to Reserve Data Connection IP Port: <port_id> forDevice: <device_id> (Axxess Only)

FIELDS: port_id The ID of the IP port device that was to be used for the data connection.

device_id The ID of the device using the data connection.

CAUSE: This message warns the user that a remote node attempted to connect to the node and the IPRC that it used did not have any data connections. The Device field is the ID of the Remote IP Port Device attempting to establish. If there are no more data connections on the node, this message will occur repeatedly if a remote node is attempting to establish a link and the node will not be able to connect to the remote node.

ACTION: Make sure there are enough networking IPRCs to provide sufficient data connections for IP Devices, as well as Remote IP Port connections for every other IP Networking node in the system. An IPRC provides for 128 data connections for IP Devices and IP Networking. To see what data connections exist on an IPRC, go into the IPRC's On-Line Monitor in Debug Session. Type “ipdc” to view all the IP phone data connections. Type “socket” and filter on port 5570 for all of the IP networking data connections.

M6111 Unable to Reserve Data Connection IP Port: <port_id> forDevice: <device_id> (Axxess Only)

FIELDS: port_id The board index of the board where the Device will get a data connection.

device_id The ID of the device pending for the data connection.

CAUSE: This message warns the user that an IP Station or IP Trunk is waiting for a data connection to the indicated board. There are no other data connections in the system. After a data connection is freed, the IP station or IP trunk will get the freed data connection on a first-come-first-served basis.

ACTION: Make sure there are enough networking IPRCs to provide sufficient data connections for IP Devices, as well as Remote IP Port connections for every other IP Networking node in the system. An IPRC provides for 128 data connections for IP Devices and IP Networking. To see what data connections exist on an IPRC, go into the IPRC's On-Line Monitor in Debug Session. Type “ipdc” to view all the IP phone data connections. Type “socket” and filter on port 5570 for all of the IP networking data connections.

M6112 Buffer OverrunFIELDS: None.

CAUSE: This message indicates an internal Call Processing error. The software has written to memory beyond the buffer's limit.

ACTION: Freeze the system immediately and send the information to Mitel Field Service.




M6113 Manager Node Change Request Failed Due to <text>FIELDS: text Reason why the request failed.

CAUSE: This message warns the user that the request for changing the node's name failed due to an invalid new name, account ID did not match the assigned account ID, or security token was not received.

ACTION: Contact System Manager Administrator to ensure that the new node name is valid, the account ID matches the previously assigned account ID, and the security token is not null.

M6114 Fax Call Failure Due to Text FIELDS: None.

CAUSE: This message warns the user that the T.38 fax call has failed due to a lack of resources.

ACTION: Contact Administrator to ensure that there are enough channels reserved for FoIP calls and that T.38 is selected as the Fax Tx Encoding Type in the Node Trunk/IP Connection Group's Call Configuration.

M6115 Networking Call Failure Due to Insufficient Networking VoIPs from License

FIELDS: None.

CAUSE: The number of IP networking calls is exceeded as specified by the Networking VoIPs license count. The IP networking call failed.

ACTION: Purchase more Networking VoIPs license.

M6116 <ext>: Auto-NAT Detection Failed – <string>FIELDS: ext The station that ran the test.

string Default the NAT type to NATIVE or NAT Type Remains Unchanged.

CAUSE: The auto-NAT Detection flag is selected for an IP station. CP has issued 3 attempts to auto learn the NAT type of this station. However, all three attempts have failed because CP never received any responses or none of the responses are valid. The transmission between the IP phone and the IPRA is not reliable so if all the packets are lost, CP will never receive any responses from the IP station. When this occurs, the NAT type will be defaulted to NATIVE or will remain the same if the test is launched due to DB changes.

ACTION: Program the NAT type for this station manually or reset the IP phone to rerun the test.

M6117 NTP Synchronization FailedFIELDS: None.

CAUSE: The system attempted but failed to synchronize its clock with an atomic clock using NTP.

ACTION: Verify the NTP and/or DNS Database Programming. Check the NTP log for details.



M6118 <Station eeee> and <IP Connection eeee> have Same IP Address – May Interfere with Auto-NAT Detection Test

FIELDS: Station eeee The station's extension.

IP Connection eeee The IP connection's extension.

CAUSE: When an IP station comes on-line, CP compares the private IP address to the IP connections programmed in the system. CP found that the station and IP connection have the same private IP address. Because the auto-NAT detection test uses the IP addresses to determine the station's NAT type, having duplicate IP address could interfere the test.

ACTION: Verify the IP addresses are programmed correctly. If the NAT address is programmed on the IP connection, the auto-NAT detection should detect the presence of a NAT.

M6119 <eeee>: Auto-NAT Detection Result is Not ConfirmedFIELDS: eeee The station's extension.

CAUSE: The station's auto-NAT detection test result indicated the NAT type is NATIVE. This result has to been confirmed by the IP Connection where the station resides. After 3 tries, CP didn't get the confirmation from the IP Connection.

ACTION: Verify the private and NAT IP addresses of the IP Connection are programmed correctly. Also make sure that there are no devices in the station's network has the same IP Connection's private IP address.

M6120 Failed to Allocate VoIP Resource for Ext <eeeee> <string>FIELDS: eeeee The extension number of the device that requested the VoIP DSP resource.

string A string representing the location where this error occurred in the code or what type of call and vocoder.

CAUSES: Call Processing received a setup request or setup indication and tried to allocate an IP resource for the new networking call. There are no more networking IP resources available because they are being used by another call.

There are no more phone IP resources available when an IP phone tries to make an outgoing call, receive an incoming call or service a queue callback call.

ACTION: If there are no IP resources available, CP will camp on to the NRG for networking calls. The phone should see a camp on message displayed. If all of the IP resources are being used for calls, the user will get the next available resource when one of the calls terminate.

A phone display should see WAITING FOR RESOURCE on the display when making an outgoing call. However, the user will not get any indication when receiving an incoming call. If all the IP resources are being used for phones or networking calls, the phone will get the next available IP resources when one of the calls terminate.

M6121 Cannot Monitor Heap (Axxess Only)FIELDS: None.

CAUSE(S): The PSAPI.DLL file is missing or corrupt.

ACTION: Find a PSAPI.DLL from another Windows computer of the SAME version (i.e., NT to NT, 2K to 2K, no XP DLL file should be used on a 2K or NT box) and copy the file to the computer with the missing or corrupt file.

NOTE The system can be configured to reserve DSP resources for networking, station, trunk and emergency calls.



M6122 Exceeded Max Number of Agent IDs: Failed to Create <id>FIELDS: id Agent ID id that was not created.

CAUSE(S): The maximum number of agent ids has been reached.

ACTION: Log into Database Programming and first, remove unused agent ids. If this does not work, as a last resort, increase the number of agent ids the system.

M6123 Conference Break Up Failed for <eeee> Due to No Remaining VoIPs Conference Parties Disconnected

FIELDS: eeee The extension number of the device that broke up the conference.

CAUSE(S): An IP phone cannot break up a conference if there are no VoIPs available, for example the system has run out of VoIP DSP resources.

ACTION: The system drops the calls that would have gone on hold. The user will need to reestablish the calls once a VoIP becomes available. Reduce the number of devices that can allocate VoIP DSP resources. Alternatively, increase the VoIP DSP capacity of the system through a possible upgrade.

M6124 <s1> Module <N1> Port <N2> <s2> FIELDS: N1 Module Number.

N2 Port Number.

s1 This refers to the functions in the license manager with the error.

s2 This refers to the license type that is out of sync.

CAUSE(S): The software is out of sync with the License Manager. This is a software bug.

ACTION: Freeze the system immediately and send the information to Mitel Field Service. This does not cause any problems on the system.

M6125 Device <ext> Failed to Find the Other Device <ext1> SystemEcho 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.

NOTE The system can be configure to reserve DSP resources for networking, station, trunk, and emergency calls.



M6126 <eeee>: Audio Receive Port Changed From <old_port> to <new_port>

FIELDS: eeee The extension of the device that received a new port.

old_port The original audio receive port the system specified the set to use.

new_port The new audio receive port the set indicates it will use.

CAUSE(S): When a Mitel set comes online, the system has the option to send a command to the set to specify a port or a range of ports to be used for the Audio Receive Port. The system will only specify a port not a range at this time. The port received by the system is different from the port specified the system.

ACTION: This message is informational only.

M6127 Generic SIP Error Message <s> FIELDS: s A descriptive string of the SIP problem.

CAUSE: This warning is generated for SIP related errors.

ACTION: Check Database Programming for errors depending on the error message received.

M6128 <s1> File-Based Audio Source <N1> <s2> FIELDS: N1 File based audio source logical number.

s1 Refers to the functions in the license manager with the error.

s2 Refers to the license type that is out of sync.

CAUSE: The software is out of sync with the License Manager. This is a software bug.

ACTION: Freeze the system immediately and send the information to Mitel Field Service. The result of this message does not cause any problems on the system.

M6129 Module <number1> in DEI <number2> Failed to ComeOnline: Not in Quad-DEI Mode

FIELDS: number1 The bay number with the module that failed to come online.

number2 The DEI in which the module resides.

CAUSE: To use DEI 3 or 4 the system must be in Quad-DEI mode.

ACTION: Refer to the Database Programming online Help to put the system in Quad-DEI mode.

M6130 File-Based Audio Source <N1> - <s1> FIELDS: N1 File based audio source logical number.

s1 This refers to the a generic error or warning message with regard to the file-based audio source.

CAUSE: This is not necessarily a software issue. This could be something like a file-based audio source not being able to get a VOIP, etc.

ACTION: Freeze the system and send the information to Mitel if the message occurs along with any undesirable behavior.



M6131 HTML Application File Not Found: Profile <number> File <filename>

FIELDS: number The profile that is using the missing file.

filename The HTML application file that is not present.

CAUSE: An HTML phone application file that was previously on the system has been removed.

ACTION: Upload the required file, or use database programming to refresh the HTML application file list.

M6132 <eeee>: HTML Application <app> Not Found for Language <lang>

FIELDS: eeee The affected device extension.

app The HTML application name.

lang The language of the specified device.

CAUSE: A device is programmed to use an HTML application, which is not available for the language indicated.

ACTION: Upload the required file, or remove the application from the profile used by the indicated device.

M6133 <eeee>: HTML Application <app> Not Found for Device Type <device>



device The type of the specified device.

CAUSE: A device is programmed to use an HTML application, which is not available for the device type indicated.

ACTION: Upload the required file, or remove the application from the profile used by the indicated device.

M6134 <eeee>: HTML Applications Exceed Available Storage on Device


CAUSE: The applications in the indicated device’s application profile exceeds the available storage for that device.

ACTION: Review the applications in the device's application profile to make sure that they do not exceed the available storage on the device.

M6135 <eeee>: HTML Applications <app> Not FoundFIELDS: eeee The affected device extension.


CAUSE: A device is programmed to use an HTML application that is not available.

ACTION: Upload the required file, or remove the application from the profile that the indicated device uses.

M6136 Error Parsing HTML Application File <name>FIELDS: name The application filename that caused the error.

CAUSE: An error occured while reading the indicated HTML application file. This indicates malformed data or corruption in the application file.

ACTION: The indicated application file is unusable. Contact Mitel Technical Support and provide the application file for investigation.

System Messages (M0001–M9999): Database Severe Error Messages (M7000–M7999)


Database Severe Error Messages (M7000–M7999)This section documents severe error messages regarding the content of the database or the result of operations on the database. There may be a noticeable effect on system operation.

M7000 Battery-Backed Memory Full for Equip of <object> <b.p.d>FIELDS: object Either Board, Port, or Circuit.

b.p.d The board/port/device of the equipment that failed.

CAUSE: Database Programming attempted to equip one or more boards, ports, or circuits. However, the database memory is full, so the CP software rejected the equip. If you requested multiple equips, the CP software ignores any remaining equips (so there should be only message of this type for a multiple-equip request).

AXXESS ACTION: Unequip unnecessary devices (unused trunks, stations, boards, etc.) or remove stations from extension lists to make more database memory available.

5000 ACTION: Unequip unnecessary devices (unused trunks, stations, modules, etc.) or remove stations from extension lists to make more database memory available.

M7001 Database Defaulted Due to OS Indicates Battery-BackedMemory Corruption

FIELDS: None.

AXXESS CAUSE: The OS performs a checksum on the Battery-Backed Memory during the power-up-testing sequence. If the checksum does not match the stored checksum, the database is corrupt, so the system defaults the database. This message occurs when you remove the Battery-Backed Memory jumper to allow the memory to fade, and when you power up the system the first time.

5000 CAUSE: The system performs a checksum on the Persistent Memory during the power-up-testing sequence. If the checksum does not match the stored checksum, the database is corrupt, so the system defaults the database. This message occurs when you power down the system for an extended period of time, when new Call Processing software is loaded and, when you power up the system the first time.

ACTION: Try to determine what the last database updates were. Refer to the computer where Database Programming changes were made. The cpm.log may be able to help us determine what database changes may have caused this error. If necessary, restore the most recently saved database. If this message appeared unexpectedly, report the problem to Mitel Field Service.

FSACTION: Report the problem to the engineering contact person for further analysis. Try to obtain the entire failing CP board/module to help engineering diagnose the problem.

M7001 Database Defaulted Due to Internal Database Pointer is Invalid

FIELDS: None.

AXXESS CAUSE: The CP software maintains a pointer to crucial database information in the Battery-Backed memory. If this pointer becomes invalid (i.e., it doesn't point to the correct database information), the CP software must default the database because there is no way to access the crucial database information.

5000 CAUSE: The CP software maintains a pointer to crucial database information in the Persistent memory. If this pointer becomes invalid (i.e., it doesn't point to the correct database information), the CP software must default the database because there is no way to access the crucial database information.

ACTION: If necessary, restore the most recently saved database. If this message appeared unexpectedly, report the problem to Mitel Field Service.




M7001 Database Defaulted Due to Forced DefaultFIELDS: None.

AXXESS CAUSE: A user requested the database to be defaulted through an Database Programming Session. This message also occurs if you abort a database download; the CP software must default the database because it received only a partial download.

5000 CAUSE: A user requested the database to be defaulted through a Database Programming Session or the LCD display. This message also occurs if you abort a database download; the CP software must default the database because it received only a partial download.



M7001 Database Defaulted Due to CODE Change: Last Function Relocated

FIELDS: None.

AXXESS CAUSE: The Battery-Backed memory contains pointers to functions inside the CP software. If you change the CODE on the CPU board, these pointers become invalid because the functions moved. The CP software uses a pointer to the last function to detect a CODE change. If the CP software detects a CODE change, it must default the database.

5000 CAUSE: The Persistent memory contains pointers to functions inside the CP software. If you change the CODE on the CPU board, these pointers become invalid because the functions moved. The CP software uses a pointer to the last function to detect a CODE change. If the CP software detects a CODE change, it must default the database.



M7001 Database Defaulted Due to CODE Change: Last CODE Table Relocated

FIELDS: None.

AXXESS CAUSE: The Battery-Backed memory contains pointers to crucial tables inside the CP software. If you change the CODE on the CPU board, these pointers become invalid because the CODE tables moved. The CP software uses a pointer to the last table to detect a CODE change. If the CP software detects a CODE change, it must default the database.

5000 CAUSE: The Persistent memory contains pointers to crucial tables inside the CP software. If you change the CODE on the CPU board, these pointers become invalid because the CODE tables moved. The CP software uses a pointer to the last table to detect a CODE change. If the CP software detects a CODE change, it must default the database.





M7002 Battery-Backed Memory Full for Extension List Addition <ext>

FIELDS: ext The extension of the extension list that failed.

AXXESS CAUSE: Database Programming attempted to add more extensions to the given extension list. The list could not be expanded because the Battery-Backed memory is full. After this error occurs, the extension list will be empty because the extension list processing throws away the old extension list before it requests additional memory for the new one.

5000 CAUSE: Database Programming attempted to add more extensions to the given extension list. The list could not be expanded because the Persistent memory is full. After this error occurs, the extension list will be empty because the extension list processing throws away the old extension list before it requests additional memory for the new one.

ACTION: Reprogram the extension list to be smaller. Use Database Programming to save a copy of the database. Then contact Mitel Field Service.


M7003 Database Out-of-Synch: Record <id>, Sequence <seq>, Bit <bit>, Max Bit <maxbit>

FIELDS: id The Record ID of the database record that is out-of-synch.

seq The sequence number of the database request.

bit The bit number (or record number) of the record number that is out-of-synch.

maxbit The maximum bit number allowed for this Record ID.

CAUSE: The database being used by applications or the Voice Processing is out-of-synch with Call Processing's database. This is usually due to making a coding change either in CP or in Applications and not properly communicating the change the appropriate engineer in the other group. This problem should happen only during system development.

ACTION: If this system is under development, contact the appropriate person in the other group and synch up the database. Usually, the file ddlncap.hpp has the wrong values. If this message occurs in a system that is not under production, verify that the software running on the programming computer (or on the voice processing unit) matches the software on the system. If the software matches, save the database as far as possible and get a System History freeze. Report this information to Mitel Field Service.

M7004 Database Compression/Decompression ErrorFIELDS: None.

CAUSE: An internal error caused failure of the compression or decompression of database information. This usually causes the programming session to terminate.

ACTION: Disable (set to zero) the data compression flag in Database Programming Session Manager. If the problem continues, contact Mitel Field Service.

FSACTION: Report the problem to the engineering contact person for further analysis. Try to obtain the system database and note what operation the user was performing when the error was seen.



M7005 Another Node does Not Know About Node <number>FIELDS: number Node number of the new node that some other node does not know about.

CAUSE: A new node was added to the node that printed this message, but all other nodes know about this new node.

ACTION: Log into Database Programming on all other nodes in the system and add the new node, if it has not already been added. Do not forget to add the node trunk group(s) to the new node so that the node knows how to route calls to the new node. Unlike M4011, this problem is based on the configuration of the network. The system needs to know about the new node as soon as possible to avoid service-affecting problems.

M7006 Node <number1> does Not Know About Node <number2>FIELDS: number1 The node number of the node that does not know about the new node in the system.

number2 The node number of the new node.

CAUSE: A new node was added to the private network. The node that printed this message knows about the node, but another node indicated in the message print does not.

ACTION: Log into Database Programming on the indicated node in the system and add the new node, if it has not already been added. Do not forget to add the node trunk group(s) to the new node so that the node knows how to route calls to the new node. Unlike M4015, this problem is based on the configuration of the network. The system needs to know about the new node as soon as possible to avoid service-affecting problems.

M7007 Invalid Software License – Reset in <xx> MinutesFIELDS: xx The number of minutes before the next reset.

AXXESS CAUSE: A software license for the system version has not been uploaded. If the software license has already been loaded, there could be a hardware issue that would require a new CP Server hardware licensing device.

5000 CAUSE: The technician has not uploaded a software license for the system version loaded. If the software license had already been loaded, then there could be a hardware issue that would require a new hardware licensing device.

AXXESS ACTION: Log into Database Programming and upload the software license. If this does not fix the problem (e.g., the system thinks the software license is corrupted), transfer the software license to a new CP Server hardware licensing device or CPC and notify Mitel immediately.

5000 ACTION: Using Diagnostics Monitor/System Monitor under Dump Resource Managers, dump the License Manager and record this information. Validate that the hardware licensing device LED is on. If the hardware licensing device LED is off, report this immediately to Mitel Technical Support. If the hardware licensing device LED is on, log into Database Programming and upload the software license. If this does not fix the problem, the hardware licensing device may be faulty. Report this immediately to Mitel Technical Support.

System Messages (M0001–M9999): Hardware Severe Error Messages (M8000–M8999)


Hardware Severe Error Messages (M8000–M8999)This section documents severe error messages regarding the configuration or operation of hardware components or systems. There will be some effect on system operation.

M8000 <string> Condition Detected on <board_type> <b.p.d>FIELDS: string Either “Initial Trouble” or “Red Alarm” depending on how long the condition lasts. See

CAUSE below.

board_type A string specifying whether this is a T1 or E1.

b.p.d The board, port, and device numbers of the serial port that has a problem.

CAUSE: This message is coupled with message M8001. The “Initial Trouble Condition Detected” message occurs when a T1 detects one of the trouble conditions detailed in M8001. If the condition lasts for several seconds, the “Red Alarm Condition Detected” message appears and all calls on the T1 will be dropped (see M8003 page 146).

ACTION: Resolve the indicated problem(s) on the T1. See M8001 (below) for more information.

M8001 <board_type> Problem: <type> (North America)AXXESS FIELDS: board_type A string specifying whether this is a T1 or E1.

type The type of alarm that occurred on the T1/E1 card. See ACTION below for the causes.

5000 FIELDS: board_type A string specifying whether the expansion module is a T1 or E1 type.

type The type of alarm that occurred on the T1 or E1 module. See ACTION below for the causes.

AXXESS CAUSES: The T1 card detected the indicated type of problem (M8000). If the problem persists for several seconds, a Red Alarm occurred (see M8003 page 146). The types of errors and their causes are detailed below.

5000 CAUSES: The T1 module detected the indicated type of problem (M8000). If the problem persists for several seconds, a Red Alarm occurred (see M8003 page 146). The types of errors and their causes are detailed below.

AXXESS ACTION: These conditions must be resolved if the card is in Red Alarm.

x Receiver Loss of Signal from Network. The signal from the network was lost. Verify the cable is plugged into the T1, the signal from the network is present and operating properly, there is no installation problem (cabling, etc.), and that the T1 passes its self-test.

x Transmitter Loss of Signal from Network. The T1 is unable to transmit a valid T1 signal to the network. Verify the cable is plugged into the T1, there is no installation problem (cabling, etc.), and that the T1 passes its self-test. Replace the T1.

x Receiving Yellow Alarm. The T1 is receiving a yellow alarm from the network, indicating that the network (or other T1 in a private network) is having problems. Resolve the problems with network.

x Receiving Blue Alarm. The T1 is receiving a blue alarm from the network, indicating that the network (or other T1 in a private network) has lost the signal from this T1. If a Transmitter Loss of Signal from Network problem has occurred, follow the steps detailed there. Otherwise, there is a problem with the communication between the T1 and the network.

x T1 Signal Out-of-Frame. The T1 framing of the signal received from the network has been lost. This is typically due to one system using a clock that is less `reliable' than the clock used on another system. Verify that all T1’s in the system or network are configured properly to use the most accurate clock available. This could also occur if one or more T1s in a network have gone down, causing the network to use clocks that are less reliable. Also, refer to the actions detailed under “Receiver Loss of Signal from Network”.



x Severely Errored Seconds. The T1 has detected 10 consecutive Severely Errored Seconds. A Severely Errored Second is a second with excessive bit errors. In D4 format, a severely errored second is defined as a second with more than 1544 BPVs. In ESF format, a severely errored second is defined as a second with more than 330 CRC-6 violations. Bit errors can be caused by the same reasons a T1 signal becomes out of frame. Therefore, refer to the actions for T1 Signal Out-of-Frame.

x Transmitting Blue Alarm. The T1 has begun transmitting blue alarm. This can occur if Applications requests that the T1 transmit blue alarm, which is acceptable. It can also mean that the T1 has lost the signal from the network. Refer to the actions detailed under that item.

x Remote Loopback State. The remote T1 or network has put the local T1 into a remote loopback state for testing purposes. The T1 span will not be available for call handling until the test is complete.

M8001 <board_type> Problem: <type> (Europe)AXXESS FIELDS: board_type A string specifying whether this is a T1 or E1.

type The type of alarm that occurred on the T1/E1 card. See ACTION below for the causes.

5000 FIELDS: board_type A string specifying whether the expansion module is a T1 or E1 type.

type The type of alarm that occurred on the T1 or E1 module. See ACTION below for the causes.

AXXESS CAUSES: The T1 card detected the indicated type of problem (M8000 page 144). If the problem persists for several seconds, a Red Alarm occurred (see M8003 page 146). The types of errors and their causes are detailed below.

5000 CAUSES: The T1 module detected the indicated type of problem (M8000 page 144). If the problem persists for several seconds, a Red Alarm occurred (see M8003 page 146). The types of errors and their causes are detailed below.

ACTION: These conditions must be resolved if the T1/E1 is in Red Alarm:

x Receiver Loss of Signal from Network. The signal from the network was lost. Verify the cable is plugged into the T1, the signal from the network is present and operating properly, there is no installation problem (cabling, etc.), and that the T1 passes its self-test.

x Transmitter Loss of Signal from Network. The T1 is unable to transmit a valid T1 signal to the network. Verify the cable is plugged into the T1, there is no installation problem (cabling, etc.), and that the T1 passes its self-test. Replace the T1.

x Loss of Frame Synchronization. The T1 has detected a loss in frame synchronization. This is typically due to one system using a clock that is less reliable than the clock used on another system. Verify that all T1 in the system or network are configured properly to use the most accurate clock available. This could also occur if one or more T1’s in a network have gone down, causing the network to use clocks that are less reliable. Also, refer to the actions detailed under “Receiver Loss of Signal from Network”.

x Loss of Multiframe Synchronization. The T1 has detected a loss in multiframe synchronization. Refer to the actions detailed for the “Loss of Frame Synchronization”.

x Receiving Alarm Indication Signal (AIS). The T1 is receiving AIS from the network, indicating that the network (or other T1 in a private network) has lost the signal from this T1. If a Transmitter Loss of Signal from Network problem has occurred, follow the steps detailed there. Otherwise, there is a problem with the communication between the T1 and the network.

x Receiving Remote Alarm Indication (RAI). The T1 is receiving RAI from the network, indicating that the network (or other T1 in a private network) is having problems. Resolve the problems with network.

x Severely Errored Seconds. The T1 has detected 10 consecutive Errored Seconds.



x 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.

x 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.

x 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.

M8002 <string> Condition Cleared on <board_type> <b.p.d>FIELDS: string Either “Initial Trouble” or “Red Alarm” depending on how long the condition lasts. See

CAUSE below.

board_type A string specifying whether it is a T1 or E1.

b.p.d The board, port, and device in question.

CAUSE: This message occurs after M8000 or M8001 when all the trouble conditions on a T1 have been resolved. Although this message indicates problems have been resolved, it was made a severe message to ensure that someone seeing M8000 or M8001 would see this message.

ACTION: None.

M8003 All Calls on <board_type> <b.p.d> have been DroppedFIELDS: board_type A string specifying whether it is a T1 or E1.


CAUSE: This message occurs after the Red Alarm version of M8000 or M8001. When the T1 went into Red Alarm, any calls that were present on the T1 were dropped due to the severity of the error.

ACTION: Follow the actions of M8001 for the indicated condition(s) that caused the Red Alarm.

M8004 <board_type> <b.p.d> Failed <test_type> Self-TestFIELDS: board_type A string specifying whether it is a T1 or E1.


test_type The type of self-test that failed.

CAUSE: Each time the T1 powers up or is reset, it performs a self-test to verify that it is able to operate properly. If the self-test fails, messages are printed out alerting the user of the fact. The system does not let the T1 power-up, because it is in a non-operational state. The types of failures are:

x RAM: The RAM memory or associated circuitry on the T1 is bad. The T1 could not read/write all of RAM.

x Checksum: The ROM memory on the T1 is bad. The computed checksum does not match the built-in checksum.

x Heartbeat Timer: The T1's heartbeat timer is not operating properly.

x Crosspoint Switch: The T1 cannot access its digital crosspoint switch.

x Parallel Access Circuit: The T1 cannot properly access its Parallel Access Circuit.

x Dual Data Link Controller: The T1 cannot properly access its MC145488 Dual Data Link Controller (DDLC).

ACTION: Replace the T1.



M8005 <device> <b.p.d> Command too Large for Buffer: Length <xx > Buffer Size <yy>

FIELDS: device The name of the device reporting the error

b.p.d The board, port, and device numbers of the serial port that has a problem with interrupts

xx The length of the command.

yy The maximum allowed length for a command.

AXXESS CAUSE: Call Processing attempted to send either a Peripheral Processor command or a RS-232 message that exceeded the current size of the buffer used to build the message.

5000 CAUSE: Call Processing attempted to send either a Peripheral Processor command that exceeded the current size of the buffer used to build the message.

AXXESS ONLY PREV8.2 ACTION:

If this problem happens frequent enough, freeze the system history immediately after the next occurrence. If this problem happens infrequently, enable the “automatic freeze on system exception” flag in the On-Line Monitor; the next time the problem occurs, the system is automatically frozen and it generates an Alarm #115. Once the history is frozen, use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.

AXXESS POST V8.2AND 5000

If this problem occurs frequently, freeze the system history immediately after the next occurrence. If this problem is an infrequent occurrence, configure a message print freeze-on string for “M8005”. The system is automatically frozen and generates an Alarm #121. Preferably, use Automatic Diagnostics Delivery (ADD) to transmit the freeze information to Mitel Technical Support. If the Automatic Diagnostics Delivery is not available, use Database Programming to save the database and obtain the CP Error Information.


M8009 T1 Card <card> Detected Missing Network Clock Card(Axxess Only Pre v8.0)

FIELDS: card The decimal card number that detected the error.

CAUSE: A T1 card detected that a Network Clock Card (the NCC Card) is not present in the system. T1 requires that an NCC be present for the T1 cards to function properly.

ACTION: Add an NCC card to the system. If one is present, it may be defective or loose.

M8010 <side>: Fiber FPR Indicates Abnormal Status = <status> (Axxess Only)

FIELDS: side either "Master" or "Slave" -- indicates the cabinet side where the error message originated.

status The internal status of the DPR (Dual-Port RAM) fiber channel.

CAUSE: Either the IOP (8052) found something seriously wrong, or some errant code changes this byte and possibly others.

ACTION: If problem persists though minor resets and power cycles and/or the secondary cabinet pair does not come back on-line, then replace the PCM-F card and possibly the fiber cable. If problem still persists, replace the CPU020 board.



M8011 <side>: No Signal from Fiber Optic Cable (Axxess Only)FIELDS: side Either "Master" or "Slave" -- indicates the cabinet side where the error message originated.

CAUSE: The fiber-optic receiver on the PCM board does not detect the presence of the fiber-optic signal. This could be due to a damaged fiber-optic cable, from the cable being inserted incorrectly or from a failed fiber-optic transmitter or receiver.

ACTION: Examine the fiber-optic cable and the connections. If the connections or loose, tighten them. If the connectors are reversed, swap them. If there are crimps in the fiber-optic cable, replace the cable. Otherwise, the problem may be due to a failed fiber-optic transmitter or receiver. In this case, replace the PCM-F board.

M8012 <side>: No Signal from Fiber Optic Cable; Resetting Communication (Axxess Only)

FIELDS: side Either "Master" or "Slave" -- indicates the cabinet side where the error message originated.

CAUSE: There was no signal from the Fiber-Optic Cable for too much time. Therefore, the system software resets all communication to the fiber optic channel. This includes forcing all devices in the secondary cabinet-pair off-line and terminating all calls through the fiber optic cable. See M8011 (page 148) for additional information.

ACTION: See error 8011 (page 148).

M8013 <side>: Fiber-Optic Multiplexer is Out-of-Sync: Sync = <sync> (Axxess Only)


sync The bytes indicating the sync error.

CAUSE: The system software has detected that one of the fiber-optic multiplexer is out-of-synch with the fiber-optic multiplexer on the other system. The multiplexer (the big fiber chip) on each PCM-F sends out a sync signal through the fiber to the other PCM-F; the receiving PCM-F sends this sync signal back to the sender as well as sending its own sync signal; the first PCM-F will also return the second PCM-F's sync signal back. Therefore, each PCM-F expects to receive its own sync ("remote (other) PCM-F is in sync with this PCM-F") as well as the other PCM-F's sync ("local (this) PCM-F is in sync with the other PCM-F"). By removing just one fiber cable of the pair, you can see this error message and the LEDs in action; for example, remove the transmit cable from the first PCM-F. Obviously, the first PCM-F cannot send out its sync signal, and the second PCM-F does not receive this sync because you removed the cable; in addition the first PCM-F cannot send back the second PCM-F's sync signal nor can the second PCM-F receive its sync signal back again because that fiber cable is removed. Therefore, the first PCM-F receives the other cabinet's sync signal (local sync LED on), but it does not receive its own sync back from the second PCM-F (remote sync LED flashing); the second PCM-F does not receive either sync signal and flashes both LEDs. It seems like this case is fairly common; however, you cannot tell if the first PCM-F card has a bad transmitter, or if the second PCM-F card has a bad receiver.




M8014 <side>: Fiber-Optic Multiplexer is Out-of-Sync (Two Masters): Sync = <sync> (Axxess Only)



CAUSE: The system software has detected that the fiber-optic multiplexor is occasionally out-of-synch with the other system, which usually means that both sides of the fiber-optic cable are acting as masters. This could indicate that the incorrect boot EPROM was installed in the slave CPU020.

ACTION: Verify that the boot EPROM in the slave CPU020 is the correct boot EPROM.

M8015 <side>: Fiber-Optic Multiplexer is Out-of-Sync; Resetting Comm Sync = <sync> (Axxess Only)



CAUSE: The signal from the Fiber-Optic Cable was out-of-synch for too long. Therefore, the system software resets all communication to the fiber optic channel. This includes forcing all devices in the secondary cabinet-pair off-line and terminating all calls through the fiber optic cable. See M8014 (page 149) for additional information.


M8019 <side>: Fiber Controller Inactive (Axxess Only)FIELDS: side Either "Master" or "Slave" -- indicates the cabinet side where the error message originated.

CAUSE: The IOP (8052) tells the system software that the HDLC's receive line is inactive (RLI). This implies that the HDLC will not send or receive any data.

ACTION: If it does not cause the system software to reset the fiber communications (F_ERROR_HDLC_RLI_RESET) meaning the secondary cabinet pair to go off-line, then the problem went away. If it causes the reset of the fiber communications, then corrective action maybe necessary. If problem persists though minor resets and power cycles and/or the secondary cabinet pair does not come back on-line, then replace the PCM-F card and possibly the fiber cable. If problem still persists, replace the CPU020 board.

M8020 <side>: Fiber Controller Inactive too Long; Resetting Communications (Axxess Only)


CAUSE: The Fiber Controller was inactive for too long. Therefore, the system software resets all communication to the fiber optic channel. This includes forcing all devices in the secondary cabinet-pair off-line and terminating all calls through the fiber optic cable. See error message 8018 for more information.

ACTION: See M8018.



M8021 <side>: No Response from Other Fiber Controller (Axxess Only)

FIELDS: side either "Master" or "Slave" -- indicates the cabinet side where the error message originated.

CAUSE: The IOC failed to receive a "ping" response from the other side in a reasonable amount of time. Therefore, the IOC assumes that the link or the other side is dead and resets the fiber communications. This includes forcing all devices in the secondary cabinet-pair off-line and terminating all calls through the fiber optic cable. Generally it means that the secondary side has lost messages, has reset itself, or has been powered down.


M8022 <side>: Fiber Queue Time Out (Axxess Only)FIELDS: side either "Master" or "Slave" -- indicates the cabinet side where the error message originated.

CAUSE: The IOC has not been able to insert a message into the transmit side of the fiber DPR queue for quite a while, and it has not received any data from the other cabinet in a while. Therefore, the IOC assumes that the link or the other side is dead and resets the fiber communications. This includes forcing all devices in the secondary cabinet-pair off-line and terminating all calls through the fiber optic cable. This error case should never happen because if we are not able to transmit and we do not receive any message for quite a while, then we definitely will not be able to send a “ping” out to the other side, nor receive a “ping” response back; therefore, we should always encounter the “No Response” error (F_ERROR_NO_RESPONSE) before we encounter this error.


M8023 <side>: CP on Both Slave and Master (Axxess Only)FIELDS: side Either "Master" or "Slave" -- indicates the cabinet side where the error message originated.

CAUSE: The primary (with CP) cabinet receive an initial ping message that only a primary cabinet can transmit; therefore, we have two primary cabinets and two CPs.

ACTION: Replace the CPU in the secondary cabinet with a CPU020-X board.

M8024 <side>: Fiber Error: Two Slaves Detected; Error Count = <count> (Axxess Only)


count This value holds the special count that indicates there are two slaves present. Primarily used for internal diagnostics.

CAUSE: There is no direct way for the system to detect that both cabinet pairs are slaves to the fiber clocking except by a certain error count. If the IOC sees that the HDLC is not receiving valid frames (F_ERROR_HDLC_RLI), detects this special error count, and notices that it is slave to the fiber clock, it assumes the fiber optic controllers on both sides are acting as slave to the fiber clock and extracting their clocking from the fiber while neither side is providing clocking through the fiber. Obviously, this prevents any communication from occurring and causes a horrible sound on all DSP and cross-cabinet voice channels. The system should force the secondary cabinet off-line and recover. This problem usually indicates an internal software error.

ACTION: Because this problem relates to switching reference providers, try moving all reference providing cards (T1s and PRIs) to the same cabinet pair -- all on primary side or all on secondary side. If problem persists though minor resets and power cycles and/or the secondary cabinet pair does not come back on-line, then replace the PCM-F card and possibly the fiber cable. If problem still persists, replace the CPU020 board.



M8026 <b.p.d> Illegal Data Byte Sent to Board: Type = <xx>, Board = <bb>, Circuit = <cc>

FIELDS: b.p.d The board/port/device of the board that sent the illegal input.

xx The type of the invalid response.

bb The board from which the invalid response came from.

cc The circuit from which the invalid response came from.

CAUSE: Either an invalid command was sent to the PP, or the PP board is in an unexpected state (typically the first case). The PP board was unable to process and act upon the command sent to it. Typically, the command is not a very important command (i.e., doesn't affect service in most cases), so this problem is rarely critical.


If this problem happens frequently, freeze the system history immediately after the next occurrence. If this problem happens infrequently, enable the “automatic freeze on system exception” flag in the On-Line Monitor; the next time the problem occurs, the system is automatically frozen and it generates an Alarm #115. Once the history is frozen, use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.

AXXESS POST V8.2AND 5000 ACTION:

If this problem occurs frequently, freeze the system history immediately after the next occurrence. If the problem does not occur frequently, configure a message print freeze-on string for “M8026”. The system is automatically frozen and generates an Alarm #121. Preferably, use Automatic Diagnostics Delivery (ADD) to transmit the freeze information to Mitel. If ADD is not available, use Database Programming to save the database and obtain CP Error Information.

M8027 <b.p.d> Illegal <type> Sent to Board: <data>FIELDS: b.p.d the board/port/device of the board that sent the illegal input.

type One of “Device Address”, “Data Byte”, “Device Type”, or “Command ID”.

data The bytes sent by the PP.

CAUSE: Either an invalid command was sent to the PP, or the PP board is in an unexpected state (typically the first case). The PP board was unable to process and act upon the command sent to it for some reason. Typically, the command is not a very important command (i.e., doesn't affect service in most cases), so this problem is rarely critical.


If this problem happens frequently, freeze the system history immediately after the next occurrence. If this problem happens infrequently, enable the “automatic freeze on system exception” flag in the On-Line Monitor; the next time the problem occurs, the system is automatically frozen and it generates an Alarm #115. Once the history is frozen, use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information. This message is also generated if a DSP is programmed to be present, but it is faulty or is not present. If the board is an OPC board, verify that the number of DSPs programmed to be present on the board are actually present.


If this problem occurs frequently, freeze the system history immediately after the next occurrence. If the problem does not occur frequently, configure a message print freeze-on string for “M8027”. The next time the problem occurs, the system is automatically frozen and it generates an Alarm #121. After the history is frozen, use Automatic Diagnostics Delivery to transmit the freeze information to Mitel. If the Automatic Diagnostics Delivery is not available, use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.



M8028 <b.p.d> Illegal <type> Sent to Single-Line AdapterFIELDS: b.p.d The board/port/device of the board that sent the illegal input.

type One of “Device Address”, “Data Byte”, “Device-Type”, “Command ID”, or “Command Length”.

CAUSE: Either an invalid command was sent to the PP, or the PP board is in an unexpected state (typically the first case). The PP board was unable to process and act upon the command sent to it for some reason. Typically, the command is not a very important command (i.e., doesn't affect service in most cases), so this problem is rarely critical.


If this problem happens frequent enough, freeze the system history immediately after the next occurrence. If this problem happens infrequently, enable the “automatic freeze on system exception” flag in the On-Line Monitor; the next time the problem occurs, the system is automatically frozen and it generates an Alarm #115. Once the history is frozen, use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information. This message is also generated if a DSP is programmed to be present, but is faulty or is not present. If the board is an OPC board, verify that the number of DSPs programmed to be present on the board are actually present.


If this problem happens frequent enough, freeze the system history immediately after the next occurrence. If this problem happens infrequently, configure a message print freeze-on string for “M8028”. The system is automatically frozen and it generates an Alarm #121. Preferably, use Automatic Diagnostics Delivery to transmit the freeze information to Mitel. If the Automatic Diagnostics Delivery is not available, use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.

M8030 SLC16 48-Volt Power Supply Fail on Board <board> (Axxess Only)

FIELDS: board The decimal board number of the board with the failed power supply.

CAUSE: Hardware failure.

ACTION: The SLC16 card's 48-volt power supply is the primary power source for the board, and it will not function without it. Replace the power supply.

M8031 SLC16 72-Volt Power Supply Fail on Board <board> (Axxess Only)

FIELDS: board The decimal board number of the board with the failed power supply.


ACTION: The SLC16 card's 72-volt power supply is not providing sufficient voltage. The 72V power supply provides ringing to the single line phones. The singe line phones attached to this board will not be able to ring, but will otherwise function normally. Replace the power supply.

M8032 <b.p.d> SLC16 QSLAC Failure for Devices <devices> (Axxess Only)

FIELDS: b.p.d The board/port/device of the board that sent the illegal input.

devices The devices on this board affected by the failure.


ACTION: When a SLAC fails, the four ports indicated in the error message will not operate. Replace the board.



M8046 <b.p.d> Invalid Subtask ID <task-ID> for <device>: <msg>FIELDS: b.p.d The board/port/device designation of the board with an invalid subtask ID.

task-ID The task ID that has an invalid subtask ID associated with it.

device The type of device that generated the input that contained the invalid subtask ID.


CAUSE: The CP software received a message that contained a invalid subtask ID.





M8047 <b.p.d> Invalid Subtask ID <task-ID> for <board>: <msg>FIELDS: b.p.d The board/port/device designation of the board with an invalid subtask ID.

task-ID The task ID that has an invalid subtask ID.

board The board type that generated the input that contained the invalid subtask ID.


CAUSE: The CP software received a message that contained a invalid subtask ID.




If this problem happens frequent enough, freeze the system history immediately after the next occurrence. If this problem happens infrequently, configure a message print freeze-on string for “M8047”. The system is automatically frozen and it generates an Alarm #121. Preferably, use Automatic Diagnostics Delivery to transmit the freeze information to Mitel. If the Automatic Diagnostics Delivery is not available, use Database Programming to save the database and obtain the CP Error Information. Report the problem to the engineering contact person for further analysis.



M8050 <b.p.d> Null Message for <device>FIELDS: b.p.d The board/port/device designation of the device that received the null message.

device The device type that was sent the null message.

CAUSE: The CP software received a message that did not contain any information.





M8051 <b.p.d> Null Message for <board>FIELDS: b.p.d The board/port/device designation of the board that received the null message.

board The board type that was sent the null message.

CAUSE: The CP software received a message that did not contain any information.







M8053 <b.p.d> Invalid DSP Input <dsp_inp> from DSP <dsp_num>: <msg>

FIELDS: b.p.d The board/port/device designation of the board that sent the invalid DSP input.

dsp_inp The input received from the DSP.

dsp_num The number of the DSP that is sending the invalid input.


CAUSE: The CP software received an invalid DSP input.


If this problem happens frequent enough, freeze the system history immediately after the next occurrence. If this problem happens infrequently, enable the “automatic freeze on system exception” flag in the On-Line Monitor; the next time the problem occurs, the system is automatically frozen and it generates an Alarm #115. Once the history is frozen, use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information. If the problem persists, verify that the DSP chip is properly seated in its socket. If the DSP still generates invalid data, replace the indicated board and return the faulty board to Mitel for repair.



5000 ACTION: If the board number is 8, then the Processor Module has the DSP error. If the board number is between 10 and 12, then the DE-1 unit has the DSP error. If the board number is between 13 and 15, then the DE-2 has the DSP error.

M8056 <b.p.d> <board>: Incompatible ISDN FW Version = <ver1> Expecting <ver2> (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the board that has the incompatible ISDN firmware version.


ver1 The ISDN firmware version of the board that is plugged into the slot.

ver2 The ISDN firmware version that is expected.

CAUSE: The firmware on the board needs to be updated to the correct version. The board is most likely a PRI board. The board will not power-up without the correct firmware.

ACTION: Contact Mitel Field Service to determine the correct firmware for the board.

M8057 <b.p.d> <board>: Incompatible FW Version = ver1;Expecting ver2 or Higher (Axxess Only)

FIELDS: b.p.d The board/port/device designation of the board that has the incompatible firmware version.


ver1 The firmware version of the board that is plugged into the slot.

ver2 The lowest possible value expected.

CAUSE: The firmware on the board needs to be updated to the correct version. The board will not power-up without the correct firmware.




M8058 <b.p.d> <board>: No Downloadable Firmware (Axxess Only)FIELDS: b.p.d The board/port/device designation of the board that has the no firmware to download.


CAUSE: The firmware on the board needs to be updated to the correct version. However, the software does not support that board type's display.

ACTION: Contact Mitel Field Service to notify them of the error. Replace the board if possible with one that is already loaded with the latest firmware.

M8059 <b.p.d> Bad Length in Code Image: <0xHHHHHHHH> (Axxess Only)


0xHHHHHHHH The value that the board considers an invalid length.

CAUSE: The firmware on the board needs a code update, and the Download Task started the download. However, the board detected an invalid length value. Image length values should be an even number of long words, so there is a problem with either the image itself or the software on the CPU card.


M8060 <b.p.d> Bad Starting Address in Code Image: <0xHHHHHHHH> (Axxess Only)


0xHHHHHHHH The value that the board considers an invalid starting address.

CAUSE: The firmware on the board needs a code update, and the Download Task started the download. However, the board detected an invalid starting address. Starting address values are fixed for both boot and card- specific code, so they should never change. If there is an unexpected starting address, there is a problem with either the image itself or the software on the CPU card.


M8061 <b.p.d> Boot Length Mismatch: Computed = <0xHHHHHHHH>, Image = <0xHHHHHHHH> (Axxess Only)


0xHHHHHHHH (Computed): The boot code contains a length value embedded in its code. The firmware adjusts this value by a constant factor to get a value that should match the length value in the code image.

0xHHHHHHHH (Image): The image contains a length value. After adjusting the length value embedded in the boot code, the two length values should match.

CAUSE: The firmware on the board needs a code update, and the Download Task started the download. However, there is a mismatch on the two length values that should always be equal. Most likely, the boot image on the CPU card is corrupted or there was an error in transmission of the image over the backplane.

ACTION: You will see (via message print) the board automatically attempt subsequent downloads until one succeeds up to a maximum of three attempts. If the problem persists in the subsequent downloads, contact Mitel Field Service to notify them of the error. Replace the board if possible with one that is already loaded with the latest firmware.



M8062 <b.p.d> Boot Checksum Mismatch: Computed = <computed>, Image = <image> (Axxess Only)


computed The 8-byte checksum (xxxx.xxxx.xxxx.xxxx) that the boot code computed.

image The 8-byte checksum (xxxx.xxxx.xxxx.xxxx) that the code image contains.

CAUSE: The firmware on the board needs a code update, and the Download Task started the download. After receiving the boot image, the firmware computes a checksum and compares it to the checksum of the image. The firmware reports this error when there is a mismatch. Errors in transmission across the backplane or a corrupted code image on the CPU card could cause this error.

ACTION: Because this code is the boot code, the system doesn't automatically make subsequent attempts unless the card-specific code also needs updated. If subsequent attempts aren't automatic, use the make-busy switch to force a download attempt. If the problem persists in the subsequent downloads, contact Mitel Field Service to notify them of the error. Replace the board if possible with one that is already loaded with the latest firmware.

M8063 <b.p.d> Card-Specific Checksum Mismatch: Computed = <computed>, Image = <image> (Axxess Only)


computed The 8-byte checksum (xxxx.xxxx.xxxx.xxxx) that the boot code computed.

image The 8-byte checksum (xxxx.xxxx.xxxx.xxxx) that the code image contains.

CAUSE: The firmware on the board needs a code update, and the Download Task started the download. After receiving the card-specific image, the firmware computes a checksum and compares it to the checksum of the image. The firmware reports this error when there is a mismatch. Errors in transmission across the backplane or a corrupted code image on the CPU card could cause this error.

ACTION: You will see (via message print) the board automatically attempt subsequent downloads until one succeeds up to a maximum of three attempts. If the problem persists in the subsequent downloads, contact Mitel Field Service to notify them of the error. Replace the board if possible with one that is already loaded with the latest firmware.

M8064 <b.p.d> Boot Code Received Unknown Message:<xx,xx,xx,xx,xx> (Axxess Only)


xx,xx,xx,xx,xx The first five bytes of the unrecognized message.

CAUSE: While the boot code had control of the board, the boot code received a message that it did not recognize. It's possible that the message was a leftover message from another board in unflushed queues. We also use this message to catch fundamental flaws in messaging between boards and the Download Task.

ACTION: Contact Mitel Field Service to notify them of the error.



M8065 <b.p.d> Code/Board Mismatch: Code ID = <0xXX_code>,Board ID = <0xXX_board> (Axxess Only)


0xXX_code The ID value contained in the image.

0xXX_board The ID value read from a hardware register on the board. Value 0x0E indicates boot code for all boards.

CAUSE: The ID in the code image doesn't match the ID in the board's hardware register.

ACTION: Contact Mitel Field Service to notify them of the error.

M8066 <b.p.d> Three Consecutive Download Attempts Failed (Axxess Only)


CAUSE: Either the code image on the CPU card is corrupted, or there are communication problems between the CPU card and the telecom board.

ACTION: Try uploading the CPU software again, re-seating the CPU card (without power, of course), and re-seating the telecom board. Power up again, and see if the problem persists. Contact Mitel Field Service to notify them of the error.

M8073 <b.p.d> Invalid <item> in Hardware Message: <msg>FIELDS: b.p.d The board/port/device designation of the device that sent the error message.

item The name of the item that is invalid.


CAUSE: A hardware message contains a field that is invalid due to a software/hardware error.


If this problem happens frequent enough, freeze the system history immediately after the next occurrence. If this problem happens infrequently, set a freeze on-string for this MP message. The system is automatically frozen and it generates an Alarm #115. Once the history is frozen, use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.





M8074 <b.p.d> Invalid <item> in Hardware Error Message: <msg>FIELDS: b.p.d The board/port/device designation of the device that sent the error message.

item The name of the item that is invalid.


CAUSE: A hardware message contains a field that is invalid due to a software/hardware error.


If this problem happens frequent enough, freeze the system history immediately after the next occurrence. If this problem happens infrequently, set a freeze on-string for this MP message. The system is automatically frozen and it generates an Alarm #115. Once the history is frozen, use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.



M8080 <string> on BRI Port <b.p.d>FIELDS: string Either “Initial Trouble Condition Detected” or “Alarm Occurred” depending on how long the

condition lasts. See Cause(s) below.

b.p.d The hardware address of the port that the problem occurred on.

CAUSE: This message is coupled with message M. The “Initial Trouble Condition Detected” message occurs when a BRI port detects one of the trouble conditions detailed in M. If the condition lasts for several seconds, the “Alarm Occurred” message appears.

ACTION: Resolve the indicated problem(s) on the BRI port. See M (below) for more information.

M BRI Port Problem: <type>FIELDS: type The type of alarm that occurred on the BRI port. See ACTION below for the causes.

CAUSE: The BRI port detected the indicated type of problem (M8080). If the problem persists for several seconds, the port will go off-line. The types of errors and their causes are detailed below.

ACTION: Loss of Signal from Network (LOS): The signal from the Basic Rate Interface was lost. Verify that there is no installation problem (cabling, etc.), that the port is correctly configured (station or trunk), and that the BRI passes its self-test.

Frame Synchronization Lost (SYNC): The framing synchronization of the signal received from the basic rate network has been lost. This is typically due to one system using a clock that is less reliable than the clock on another system. Verify that all clock-supplying cards in the system or network are configured properly to use the most accurate clock available. This could also occur if one or more clock-providing cards in the system or network have gone down, causing the network to use clocks that are less reliable.

M8082 <string> Condition Cleared on BRI Port <b.p.d>FIELDS: string Either “Initial Trouble” or “Alarm” depending on type of problem reported in M8080 or M.

b.p.d The hardware address of the port on which the problem was cleared.

CAUSE: This message occurs after M8080 or M when all the trouble conditions on a port have been resolved. Although this message indicates problems have been resolved, it was made a severe message to ensure that someone seeing M8080 or M would see this message.

ACTION: No action is necessary.



M8083 BRI Port <b.p.d> in Dead StateFIELDS: b.p.d The hardware address of the port that is in the dead state.

CAUSE: This message occurs if the hardware detects a problem with a BRI port. After this point, the BRI port is no longer functional.

AXXESS ACTION: The specified port on the BRU/BRS card is defective and no longer functional. The user may have to use one of the other ports. If multiple ports on the card are dead, replace the card.

5000 ACTION: The specified port on the BRI module is defective and no longer functional. The user may have to use one of the other ports. If multiple ports on the module are dead, replace the module.

M8090 Unable to Open COM2 Port: Result = <result> (Axxess Only)FIELDS: result The error code returned from the DOS open command.

CAUSE: This error occurs if the Voice Processing software could not open the COM2 serial port. This message may indicate that there is a hardware problem with the serial port or a configuration error (i.e., the voice processing unit does not contain a COM2 port).

ACTION: Verify that the voice processing unit computer has a COM2 port physically present and that it is configured to be present on the computer. If so, replace the COM2 port if it is a separate board in the computer. If the COM2 port is integrated into the computer motherboard, replace the computer motherboard.

M8091 <ext>: Illegal Message Type Sent to Device: <protocol_type> <reject_msg_typ> <info>

FIELDS: ext The device that received the illegal input.

protocol_type Minet or extended minet.

reject_msg_typ The message type code of the rejected message.

info May contain addition information that will indicate why the message was rejected. If the message is TAG based, this field can contain the TAG number.

CAUSE: This response is used by a Mitel IP phone to indicate to CP that it has received a message that is not supported.

ACTION: If this problem happens frequent enough, freeze the system history immediately after the next occurrence. If this problem happens infrequently, configure a message print freeze-on string for “M8091”. The system is automatically frozen and it generates an Alarm #121. Preferably, use Automatic Diagnostics Delivery (ADD) to transmit the freeze information to Mitel. If the ADD is not available, use Database Programming to save the database and obtain the CP Error Information.

M8092 Emergency Call Failed on Analog Line <error cause = error)>

FIELDS: error cause: The error returned from the Line Interface Module.

CAUSE(S): This error occurs if the emergency call cannot be made on an analog line using Line Interface Module. This message may indicate the absence of LIM module in the phone, non-configuration of LIM, analog line already in use, or lack response from LIM.

ACTION: Verify that Line Interface Module is connected and configured.


System Messages (M0001–M9999): Engineering Severe Error Messages (M9000–M9999)

Engineering Severe Error Messages (M9000–M9999)This section documents severe error messages regarding internal operation of the System CPU software. There will be some effect on system operation, probably in a service-effecting manner.

M9000 MAJOR RESET/Minor Reset: OS Detected Software ErrorFIELDS: None.

CAUSE: The OS detected a problem in the System CPU software severe enough that either a major or minor reset was required for system recovery.


M9000 MAJOR RESET: Watchdog Expired During OS MAJOR Reset Process

FIELDS: None.

CAUSE: A major reset occurred because the OS did not complete its major reset processing before the watchdog expired.


M9000 Minor Reset: Watchdog Expired During OS Minor Reset Process

FIELDS: None.

CAUSE: A minor reset occurred because the OS did not complete its minor reset processing before the watchdog expired.

ACTION: Use Database Programming to save the database and obtain the CP Error Information.Contact Mitel Field Service with this information.

M9000 MAJOR RESET: Watchdog Expired During User TaskMAJOR Reset Process

FIELDS: None.

CAUSE: A major reset occurred because a user software task did not complete its major reset processing before the watchdog expired.


M9000 Minor Reset: Watchdog Expired During User Task Minor Reset Process

FIELDS: None.

CAUSE: A minor reset occurred because a user software task did not complete its minor reset processing before the watchdog expired.




M9000 MAJOR RESET/Minor Reset: User Task Detected Software Error

FIELDS: None.

CAUSE: A user software task detected a problem in the software severe enough that either a major or minor reset was required for system recovery.


M9001 <type-of-exception>: Unrecognized Reset Code <0xHHHH>FIELDS: type-of-exception Either “Exception Recorded”, “Minor Reset”, or “Major Reset”.

0xHHHH The unrecognized reset code.

CAUSE: A reset occurred, but the user task does not recognize the reset code provided by the OS.


M9002 <type-of-exception>: <exception-description> (Axxess Only)

FIELDS: type-of-exception Either “Exception Recorded”, “Minor Reset”, or “Major Reset”.

exception-description A string that explains the exception (see below).

CAUSE: The causes depend on the Exception Description that appears in the message (see below).


M9002 Operator Request (Axxess Only)FIELDS: None.

CAUSE: A system operator requested a reset via any means, and the software did not handle the reset properly. The reset should have been handled as an informative reset rather than a severe reset. This message indicates a serious error in either the either OS software, the User Exception Handler Task software, or the system RAM such that data was corrupted as the reset was taking place.

ACTION: See common action for message M9002 on page 161.

M9002 POST Queue Overflow (Axxess Only)FIELDS: None.

CAUSE: The OS inter-task message queue overflowed. This error is a severe software error. Either the message queue is not large enough, a user task is abusing the message queue, the OS is mishandling the queue, or a RAM failure occurred as the queue was being manipulated.


M9002 Watchdog Occurred (Axxess Only)FIELDS: None.

CAUSE: The watchdog timer on the CPU board expired. This message indicates that the software spent too much time in a "loop" without pending for a message. This error may indicate a software problem or a RAM failure causing data corruption.




M9002 Port Wait Queue Overflow (Axxess Only)FIELDS: None.

CAUSE: The OS I/O port wait queue overflowed. Either the OS I/O port wait queue is not large enough, a user task is abusing that queue, the OS is mishandling that queue, or there was a RAM failure such that data was corrupted as that queue was being manipulated.


M9002 Quantum Count Failure (Axxess Only)FIELDS: None.

CAUSE: A user task retained control of the processor for too long (real-time). The OS detected this and aborted the task. If the task was an I/O task, the OS may not reset the system. However, if the task was a real-time task such as the CP software or the Initializer task, the OS may reset the system. This message may indicate a software or RAM failure.


M9002 Executive Request Failure (Axxess Only)FIELDS: None.

CAUSE: A User Task invoked one of the OS executive requests improperly. This message may indicate a software error such that either the user task misused the request or the OS mishandled the request. The message may also indicate a RAM failure such that data was corrupted as the request was invoked or handled.


M9002 Addressing Error (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board attempted to transfer control to an odd address or the software attempted to read data from an odd address. This message indicates either a software or a hardware failure.


M9002 Illegal Instruction (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board transferred control a location holding an illegal instruction. This message indicates either a software or a hardware failure.


M9002 Zero Divide (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board attempted to divide by zero. This message indicates either a software or a hardware failure.


M9002 Check Instruction (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board executed a check instruction that failed. This message indicates either a software or a hardware failure.




M9002 Trap V Instruction (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board executed a "trap V" instruction. This message indicates either a software or a hardware failure.


M9002 Privilege Violation (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board attempted to execute a supervisor-mode instruction in user mode. This message indicates either a software or a hardware failure.


M9002 Trace (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board experienced a trace exception. This message indicates either a software or a hardware failure.


M9002 L1010 (Axxess Only)FIELDS: None.



M9002 L1111 (Axxess Only)FIELDS: None.



M9002 Reserved Vector (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board experienced an interrupt that vectored control through the reserved interrupt vector. This message indicates either a software or a hardware failure.


M9002 Format Error (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU attempted to return from exception with an invalid stack frame. This message indicates either a software or a hardware failure.




M9002 Uninitialized Vector (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board experienced an interrupt that vectored control through the uninitialized interrupt vector. This message indicates either a software or a hardware failure.


M9002 Spurious Interrupt (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board experienced a spurious interrupt (i.e., the bus error signal terminated the interrupt acknowledge cycle). This message indicates either a software or a hardware failure.


M9002 Trap 0, Trap 6, Trap 7, Trap 8,..., Trap 15 (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board invoked an illegal trap instruction. This message indicates either a software or a hardware failure.


M9002 Bus Error (Axxess Only)FIELDS: None.

CAUSE: The software running on the main processor on the CPU board experienced a bus error. This message indicates either a software or a hardware failure.


M9002 Timer Overflow Error (Axxess Only)FIELDS: None.

CAUSE: The IOC experienced a timer overflow. This indicates a software problem in the IOC or a RAM failure causing data corruption that confused the IOC.


M9002 Message Length Error (Axxess Only)FIELDS: None.

CAUSE: A user task sent a message to the IOC with an erroneous message length. This message might indicate a software error in the user task, the OS, or the IOC, or RAM failure.


M9002 Invalid Logical Address from IOC (Axxess Only)FIELDS: None.

CAUSE: The OS received a invalid logical address from the IOC. This might indicate a software error in the OS or the IOC, or a RAM failure.




M9002 Real-Time Task too Far Behind (Axxess Only)FIELDS: None.

CAUSE: The real-time task is too far behind and causes a user-detected fault. This message might indicate a software error in the user task, the OS, or the IOC, or RAM failure.


M9002 Parity Error (Axxess Only)FIELDS: None.

CAUSE: The OS detected a parity error. The CPU board may be faulty. However, there may be a software problem in the OS or the IOC.


M9002 Invalid OS Command (Axxess Only)FIELDS: None.

CAUSE: The IOC received an invalid OS command. This message may indicate a software error in the OS or the IOC, a RAM failure, or a faulty CPU board.


M9002 User Task Requested Reset (Axxess Only)FIELDS: None.

CAUSE: A user task requested a reset and the software did not handle the reset properly. The reset should have been handled as an informative reset or as a severe reset with a different coded message. This message indicates a serious error in either the either OS software, the User Exception Handler Task software, or the system RAM such that data was corrupted as the reset was taking place.


M9003 <type-of-exception>: Unrecognized Exception Code (<0xHHHH>): <msg>

FIELDS: type-of-exception Either “Exception Recorded”, “Minor Reset”, or “Major Reset”.

0xHHHH The unrecognized reset code.

msg Any data contained within the message.

AXXESS CAUSE: An exception occurred, but the user task does not recognize the exception code provided by the OS.

5000 CAUSE: An exception occurred, but the user task does not recognize the exception code provided by the system.





M9004 Heap Overflow (Axxess Only Pre v8.0)FIELDS: None.

CAUSE: The system attempted to allocate more memory than is currently available. This message may indicate a software error that causes memory to be allocated but never released. Such an error will eventually use all the available memory in the system. Additionally, there may be very little memory available because the system is very busy with all-ring calls, pages, and heavy use of DSS status keys.

ACTION: None. The system will perform a major reset if heap overflows, so all calls and system activity will terminate. If this problem occurs frequently, report the problem to Mitel Field Service.

M9005 Heap Check Failure: <reason>FIELDS: reason This string indicates the cause of the heap failure.

CAUSE: The validation logic for the dynamic heap has found an error in the heap data structures.

ACTION: The system may experience a major reset when this problem occurs. Freeze the system history. Use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.

M9006 Device: <routine-name> Extension Failure <ext>, Device <username>

FIELDS: routine-name The routine name that failed, Add or Remove.

ext The extension that failed.

username The username of the device that failed – or additional information indicating the failure.

CAUSE: The CP software tried to Add or Remove an extension from the extension manager's internal data structures. This error may occur if the CP software tries to create a device with an extension number that already exists. The error may also occur if the CP software tries to remove an extension that does not exist.

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. You may need to schedule a major reset to clean up this problem.

M9007 Device: <routine-name> Could Not Allocate Non-Dialable Extension

FIELDS: routine-name The routine name that generated this error.

CAUSE: The CP software tried create a non-dialable extension, but there are none available.


M9008 Device: <routine-name> Could Not Release Non-Dialable Extension

FIELDS: routine-name The routine name that generated this error.

CAUSE: The CP software tried to remove a non-dialable extension from the extension manager's internal data structures, but the extension does not exist. The extension manager's internal data structures are messed up.




M9009 Caller <ext-1> Dropped by <ext-2> While Recovering from an Invalid Forward Path

FIELDS: ext-1 Extension number of the device dropped.

ext-2 Extension number of the original destination (the device that started the forward chain).

CAUSE: This message indicates an error in the CP software.

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. As a temporary fix for this problem remove any forward programming at the station indicated by ext-2.

M9010 Static Constructor FailedFIELDS: None.

AXXESS CAUSE: This message indicates a software error or a compiler error. The CP software detected an error while creating an object that is stored in battery-backed memory. The integrity of the database is questionable.

5000 CAUSE: This message indicates a software error or a compiler error. The CP software detected an error while creating an object that is stored in persistent memory. The integrity of the database is questionable.



M9011 ASAI User Info Message Exceeds Maximum Allowed LengthFIELDS: None.

CAUSE: Database Programming or Voice Mail attempted to send a message to the CP software that exceeded the maximum size allowed.


M9012 ASAI Call Dropped by Call Processing Due to Invalid Call State

FIELDS: None.

CAUSE: An external ASAI device (Database Programming or Voice Mail) received a message from the CP software out of sequence. The external ASAI device and responded with a status message indicating that the states do not match. Because the states do not match, the CP software drops the call.


M9013 ASAI Call Dropped by ASAI Peer Due to Invalid Call StateFIELDS: 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.




M9014 Unable to Realloc Memory for ASAI User Info MessageFIELDS: None.

CAUSE: Database Programming attempted to send a message to the CP software that exceeded the current size of the buffer used to build the message. During this attempt, CP was unable to allocate more memory for the buffer.

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. If the Database Programming connection does not work, create a Remedy ticket and enable Automatic Diagnostics Delivery (ADD). This will send the freeze information to Mitel.

M9015 The Dynamic Heap has been Defragmented (Axxess Only)FIELDS: None.

CAUSE: The dynamic heap is in a critical situation. All available heap has been allocated to the free list. In turn, all of this memory has either been allocated to requesting processes or to the bucket cache. The system has decided to return all of the bucket cache memory to the free list in an attempt to defragment the heap. This is a last-ditch effort to keep the system alive. The system is dangerously close to running out of heap memory.

ACTION: The system may need to undergo a major reset when this problem occurs. Use Database Programming to save the database and obtain the CP Error Information. Contact Mitel Field Service with this information.

M9016 DSP Watchdog Detected Failure of <device>FIELDS: device The device that is not responding.

CAUSE: The OS detected that the indicated voice resource DSP was not responding.

ACTION: When this condition is detected, the system is not capable of processing voice resource commands. The result is the system will immediately reboot to clear the condition based on what version of the cs-ipra package is running.

Prior to 1.2 Release-10, the system will automatically reset when this error is encountered. No other action is necessary to restore operation, because the system will automatically reset.

Starting at 1.2 Release-10 which includes cs-ipra Version, 1.2.131, the system will no longer reset or show the alarm, but will print a message in the ipra log. If this message is seen, the admin should check to see if VoIP resources are working. If the admin gets no audio on a IP phone call out a trunk, or no audio to the UVM, then the system must be reset to correct the problem. If this simple test is does not result in no audio, then the message can be ignored.

FSACTION: Report the problem to the engineering contact for further analysis. Provide the CP Error Information and the database freeze. Escalate ticket to Engineering immediately.

M9020 Exception Recorded: DMTRACK Synchronization Error onPort <port> (Axxess Only)

FIELDS: port The port number that had the error.

CAUSE: The OS detected a problem with its internal RS-232 queues. The OS has attempted to correct the problem.

ACTION: This message only indicates that there may be a problem. If the system shows signs of problems in other areas, contact Mitel Field Service with the error logs.



M9021 <eeee>: Null VoIP DSP Resource Pointer Found in<routine> Resulting in No/One-Way Audio

FIELDS: eeee The extension of the device that had the error.

routine The function name where we found a null pointer.

CAUSE: When requesting a voice channel for a call going through the backplane, the IP phone involved must have a VoIP DSP resource allocated. The system tries to allocate a voice channel but it cannot find the phone's VoIP DSP resource. As a result, the voice channel allocation request will be aborted and there will be no audio for this call.

ACTION: This message only indicates that there may be a call processing bug. Contact Mitel Field Service and provide the error logs.

FSACTION: If the error persists, then report the problem to the engineering contact for further analysis. Provide the CP Error Information and the database freeze.

M9022 <eeee>: Invalid Audio Receive Port Range Received – Result = No Audio

FIELDS: eeee The extension of the device that had the error.

CAUSE: When a Mitel set comes online, the system has the option to send a command to the set to specify a port or a range of ports to be used for the Audio Receive Port. The system will only specify a port not a range at this time. The system will not know which port the set will use for its calls if the set responses with a range. This will cause no audio for all its calls.

ACTION: This message only indicates that there may be a phone firmware bug. Check the phone firmware version and contact Mitel Field Service along with the error logs.

FSACTION: If the error persists, then report the problem to the engineering contact person for further analysis. Provide the phone firmware Information, CP error information, and the database.

M9090 <Voice_Mail_Unit> PC Watchdog Reset Occurred (VPU/EM Only)

FIELDS: Voice_Mail_Unit The voice mail unit (voice processing unit).

CAUSE: This message occurs when voice processing unit resets. You will see this message the next time Voice Unit comes up, after it resets. This message is part of normal voice processing unit operation under the following circumstances:

x When you default the voice processing unit database, the voice processing unit uses the watchdog to reset, so this message will appear the next time the voice processing unit comes up.

x If you cancel the restore of the voice processing unit database, the voice processing unit defaults the database as indicated above.

ACTION: If this message appears under other circumstances, examine the message print log to determine if there is additional information indicating why this message occurred. If the problem persists, attempt to replace the Voice Processing interface boards in the voice processing unit cabinet.

Part No. 550.8018Issue 23, January 2011

A661/9129A

mitel 5000 error logs - denwa's guide

Technology

position axxess

contents mitel

mitel technical support

secondary cabinet lost

low axxess only11 text

os axxess only13 a119

a104 alarm cpu

a028 voice processing