553-3001-411 - 15.00 Mensajes

Title page
Nortel Communication Server 1000

Nortel Communication Server 1000 Release 4.5
Software Input/Output
System Messages
Document Number: 553-3001-411
Document Release: Standard 15.00
Date: January 2006
Year Publish FCC TM

Copyright Nortel Networks Limited 2006
All Rights Reserved
Produced in Canada
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design
or components as progress in engineering and manufacturing may warrant.
Nortel, Nortel (Logo), the Globemark, This is the Way, This is Nortel (Design mark), SL-1, Meridian 1, and
Succession are trademarks of Nortel Networks.
12
Page 3 of 2360
Contents
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Finding the latest updates

on the Nortel web site . . . . . . . . . . . . . . . . . . . . . . .
15
How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
About this document . . . . . . . . . . . . . . . . . . . . . . .
19
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
ACD: Automatic Call Distribution

Load Management . . . . . . . . . . . . . . . . . . . . . . . . . .
27
SNMP trap: ADD: Automatic Call

Distribution Data Dump . . . . . . . . . . . . . . . . . . . . .
43
SNMP trap: AMH: Auxiliary Message Handler . . .
47
SNMP trap: AML: Application

Module Link (LD 48) . . . . . . . . . . . . . . . . . . . . . . . .
51
SNMP trap: AMLM: Application

Module Link Maintenance (LD 48) . . . . . . . . . . . . .
53
SNMP trap: ATM: Automatic Trunk

Maintenance (LD 92) . . . . . . . . . . . . . . . . . . . . . . . .
59
System Messages
Page 4 of 2360
Contents
SNMP trap: AUD: Software Audit (LD 44) . . . . . . .
69
SNMP trap: AUTH: Authorization Code (LD88) . . 119

SNMP trap: BERR: Bus Error Monitor . . . . . . . . . 123
SNMP trap: BIC: Bus Interface Circuit . . . . . . . . . 133
SNMP trap: BKP: Remote Backup
(Small Systems and Succession 1000 systems) . 135
SNMP trap: BRI: Basic Rate Interface . . . . . . . . . 139
SNMP trap: BRIT: BRI Trunks . . . . . . . . . . . . . . . . 161
SNMP trap: BSD: Background
Signaling Diagnostic (LD 45) . . . . . . . . . . . . . . . . . 171
SNMP trap: BUG: Software Error Monitor . . . . . . 185
SNMP trap: CCBR: Customer Configuration
Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . 577
SNMP trap: CCED: Core Common Equipment
Diagnostic (LD 135) . . . . . . . . . . . . . . . . . . . . . . . . 579
SNMP trap: CDM: Call Detail Recording
Diagnostic (LD 40, LD 42) . . . . . . . . . . . . . . . . . . . 597
SNMP trap: CDN: Control DN . . . . . . . . . . . . . . . . 611
SNMP trap: CIOD: Core Input/Output
Diagnostic (LD 137) . . . . . . . . . . . . . . . . . . . . . . . . 613
SNMP trap: CLKC: Clock Controller . . . . . . . . . . . 637
553-3001-411
Standard 15.00
January 2006
Contents
Page 5 of 2360
SNMP trap: CMON: Core Monitor . . . . . . . . . . . . . 643

SNMP trap: CND: Caller's Name Display . . . . . . . 645
SNMP trap: CNF: Conference Circuit
Diagnostic (LD 38) . . . . . . . . . . . . . . . . . . . . . . . . . . 647
SNMP trap: CNI: Core to Network Interface . . . . . 653
SNMP trap: COM: Data Communication . . . . . . . . 659
SNMP trap: CRI: Carrier Remote IPE . . . . . . . . . . . 663
SNMP trap: CSA: Command and
Status Link Diagnostic (LD 48) . . . . . . . . . . . . . . . 671
SNMP trap: CSC: Customer Service Change . . . . 677
SNMP trap: DBMT: Database Media Transfer . . . . 685
SNMP trap: DCH: D-channel Diagnostic (LD 96) . 693
SNMP trap: DLO: Disk Layout . . . . . . . . . . . . . . . . 711
SNMP trap: DROL: Daily Routine Overlay . . . . . . 713
SNMP trap: DSET: Digital Set Download . . . . . . . 715
SNMP trap: DSL: DSL Diagnostic (LD 32) . . . . . . . 717
SNMP trap: DTA: Digital Trunk Diagnostic . . . . . . 719
SNMP trap: DTC: Digital Trunk Clock
Controller Diagnostic (LD 60) . . . . . . . . . . . . . . . . . 735
System Messages
Page 6 of 2360
Contents
SNMP trap: DTD: Dial Tone Detector

Diagnostic (LD 34) . . . . . . . . . . . . . . . . . . . . . . . . . 739
SNMP trap: DTI: Digital Trunk Interface
Diagnostic (LD 60) . . . . . . . . . . . . . . . . . . . . . . . . . 741
SNMP trap: DTM: Digital Trunk
Maintenance (LD 75) . . . . . . . . . . . . . . . . . . . . . . . . 759
SNMP trap: DTRK: Digital Trunk
Diagnostic (LD 60) . . . . . . . . . . . . . . . . . . . . . . . . . 773
SNMP trap: EDD: Equipment
Data Dump (LD 43) . . . . . . . . . . . . . . . . . . . . . . . . . 777
SNMP trap: ELAN: Ethernet
Local Area Network . . . . . . . . . . . . . . . . . . . . . . . . 787
SNMP trap: EMR: Emergency Key (ACD) . . . . . . . 789
SNMP trap: ERR: Error Monitor (Hardware) . . . . . 791
SNMP trap: ESA: Emergency Services Access . . 887
SNMP trap: ESDA: Enhanced Serial Data
Interface (LD 48) . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
SNMP trap: ESDI: Enhanced Serial Data
Interface (LD 48) . . . . . . . . . . . . . . . . . . . . . . . . . . . 891
SNMP trap: ESN: Electronic
Switched Network (LD 86, LD 87 and LD 9 . . . . . . 893
SNMP trap: FHW: Faulty Hardware . . . . . . . . . . . . 921
553-3001-411
Standard 15.00
January 2006
Contents
Page 7 of 2360
SNMP trap: FIJI: Fiber Junctor Interface . . . . . . . . 925

SNMP trap: FIR: Fibre Remote IPE . . . . . . . . . . . . 953
SNMP trap: FMEM: Flash Memory . . . . . . . . . . . . . 959
SNMP trap: HTM: Hyper-text markup language . . 967
SNMP trap: HWI: Hardware Infrastructure
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
SNMP trap: HWR: Hardware Reset . . . . . . . . . . . 1027
SNMP trap: ICU: Intercept Computer
Update (LD 51). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1033
SNMP trap: INI: Initialize . . . . . . . . . . . . . . . . . . . . 1035
SNMP trap: INST: Installation . . . . . . . . . . . . . . . . 1047
SNMP trap: IOD: Input/Output
Diagnostic (LD 37) . . . . . . . . . . . . . . . . . . . . . . . . . 1069
SNMP trap: ISR: Intergroup Switch and
System Clock Generator Diagnostic (LD 39) . . . 1083
SNMP trap: ITG: Integrated
IP Telephony Gateway . . . . . . . . . . . . . . . . . . . . . 1093
SNMP trap: ITS: Internet IP Telephony Server . . 1165
SNMP trap: LIS: Location Information Services . 1185
SNMP trap: LNK: Link Diagnostic (LD 48) . . . . . 1187
System Messages
Page 8 of 2360
Contents
SNMP trap: MAT: Meridian

Administration Tools . . . . . . . . . . . . . . . . . . . . . . 1207
SNMP trap: MCT: Malicious Call Trace . . . . . . . . 1213
SNMP trap: MFC: Multifrequency
Compelled Signaling (LD 54) . . . . . . . . . . . . . . . . 1215
SNMP trap: MFD: Multifrequency
Signaling Diagnostic (LD 54) . . . . . . . . . . . . . . . . 1217
SNMP trap: MFE: Multifrequency
SNMP trap: MFK: Multifrequency
Signaling for KD3 . . . . . . . . . . . . . . . . . . . . . . . . . 1227
SNMP trap: MFR: Multifrequency Receiver . . . . 1229
SNMP trap: MFS: Multifrequency
Sender Diagnostic for ANI (LD 46) . . . . . . . . . . . 1231
SNMP trap: MISP: Multi-purpose ISDN
Signaling Processor . . . . . . . . . . . . . . . . . . . . . . . 1235
SNMP trap: MPH: Meridian Packet Handler . . . . 1247
SNMP trap: MRB: Message Registration Block . 1255
SNMP trap: MSDL: Multi-purpose
Serial Data Link . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257
SNMP trap: MWL: Message Waiting
Lamps Reset (LD 61) . . . . . . . . . . . . . . . . . . . . . . 1275
553-3001-411
Standard 15.00
January 2006
Contents
Page 9 of 2360
SNMP trap: NACD: Network Automatic

Call Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . 1277
SNMP trap: NCT: Network Call Trace . . . . . . . . . 1281
SNMP trap: NPR: Network and
Peripheral Equipment Diagnostic(LD 32) . . . . . . 1323
SNMP trap: NWS: Network and
SNMP trap: OHAS: Off-Hook Alarm Security . . . 1357
SNMP trap: OSM: Operating
System Messaging . . . . . . . . . . . . . . . . . . . . . . . . 1359
SNMP trap: OSN: On-Site Notification . . . . . . . . 1363
SNMP trap: OVD: Overload Monitor . . . . . . . . . . 1365
SNMP trap: OVL: Overlay Loader . . . . . . . . . . . . 1369
SNMP trap: PCH: System Patch reports . . . . . . . 1381
SNMP trap: PMS: Property Management
System Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 1397
SNMP trap: PRI: Primary Rate
Interface Diagnostic (LD 60) . . . . . . . . . . . . . . . . . 1399
SNMP trap: PWR: Power and
System Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . 1425
System Messages
Page 10 of 2360
Contents
SNMP trap: QoS: Quality of Service . . . . . . . . . . 1431

SNMP trap: RCV: Recovery Messages . . . . . . . . 1443
SNMP trap: RLC: Reach Line Card . . . . . . . . . . . 1445
SNMP trap: RPD: 1.5 Mb/s Remote
Peripheral Equipment Diagnostic (LD 33) . . . . . 1449
SNMP trap: RPE: 2.0 Mb/s Remote
Peripheral Equipment Alarm Handler (LD 53) . . 1457
SNMP trap: RPL: 1.5 Mb/s Remote
Peripheral Equipment Local
End Diagnostic (LD 62) . . . . . . . . . . . . . . . . . . . . 1465
SNMP trap: RPM: 2.0 Mb/s Remote
Peripheral Equipment Diagnostic (LD 53) . . . . . 1471
SNMP trap: RPT: System Reporting . . . . . . . . . . 1479
SNMP trap: SCH: Service Change . . . . . . . . . . . 1481
SNMP trap: SCR: System Clock Reference . . . . 2003
SNMP trap: SCSI: Small Computer
System Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . 2005
SNMP trap: SDL: Peripheral Software Download 2013
SNMP trap: SECA: Security
Administration Alarm . . . . . . . . . . . . . . . . . . . . . . 2021
SNMP trap: SEC: Security Notification Monitor
553-3001-411
Standard 15.00
January 2006
2023
Contents
Page 11 of 2360
SNMP trap: SRPT: System Reports . . . . . . . . . . . 2027

SNMP trap: SYS: System Loader . . . . . . . . . . . . . 2069
SNMP trap: TDS: Tone and Digit
Switch Diagnostic (LD 34) . . . . . . . . . . . . . . . . . . 2181
SNMP trap: TEMU: Tape Emulation . . . . . . . . . . . 2193
SNMP trap: TFC: Traffic Control (LD 2) . . . . . . . . 2211
SNMP trap: TFN: Customer Network Traffic . . . . 2219
SNMP trap: TFS: Traffic Measurement . . . . . . . . 2221
SNMP trap: TMDI: T1 Multi Purpose
Digital Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 2225
SNMP trap: TMF: Test Multifrequencies . . . . . . . 2239
SNMP trap: TRA: Call Trace (LD 80) . . . . . . . . . . 2243
SNMP trap: TRK: Trunk Diagnostic (LD 36) . . . . 2249
SNMP trap: TTY: Teletype Error Reports . . . . . . 2275
SNMP trap: VAS: Value Added Server . . . . . . . . 2279
SNMP trap: VTN: Voice Port TN . . . . . . . . . . . . . . 2287
SNMP trap: WEB: Web Server . . . . . . . . . . . . . . . 2289
SNMP trap: XCT: Conference, Tone and
Digit Switch, and Multifrequency . . . . . . . . . . . . . 2303
System Messages
Page 12 of 2360
Contents
SNMP trap: XMI: Network to Controller Message

Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2307
Faceplate LED codes . . . . . . . . . . . . . . . . . . . . . . 2311
553-3001-411
Standard 15.00
January 2006
14
Page 13 of 2360
Revision history
January 2006
Standard15.00. This document is up-issued to include system message

number BUG9098 (CR Q01135699-02) . See page 563 for details.
August 2005
Standard14.00. This document is up-issued for Communication Server 1000

Release 4.5.
September 2004
Standard 13.00. This document is up-issued for Communication Server 1000

Release 4.0.
October 2003
Standard 12.00. This document is up-issued to support Succession 3.0

Software.
November 2002
Standard 11.00. This global document is up-issued to include system

messages required for Succession Communication Server for Enterprise
(CSE) 1000, Release 2.0 and to support Meridian 1 Release 25.4x.
January 2002
Standard 10.00. This global document is up-issued to include messages

required for Release 25.40.
December 2000
Standard 9.00. This global document is up-issued to include messages

required for Option 11C IP Expansion and for ITG and CP PII System
Messages.
System Messages
Page 14 of 2360
Revision history
April 2000
Standard 8.00. This document is issued to include content required for

Release 25.0x.
April 2000
Standard 7.00. This document is issued to include updates and changes

required for X11 Release 25.0x.
June 1999

March 1999

October 1997

August 1996

December 1995
Standard 2.00. This document is up-issued to include updates and changes

July 1995

This document has the new NTP number 553-3001-411 and contains error
message modules previously contained in International NTPs 553-2311-311
and 553-2301-511 and Book 2 of North American NTP 553-3001-400.
553-3001-411
Standard 15.00
January 2006
16
Page 15 of 2360
Finding the latest updates

on the Nortel web site
The content of this documentation was current at the time the product
was released. To check for updates to the latest documentation and
software for CS 1000 Release 4.5, click one of the links below.
Latest Software
Takes you directly to the Nortel

page for CS 1000 Release 4.5
software.
Latest Documentation
Takes you directly to the Nortel

page for CS 1000 Release 4.5
documentation.
System Messages
Page 16 of 2360
553-3001-411
Finding the latest updates on the Nortel web site
Standard 15.00
January 2006
18
Page 17 of 2360
How to get help

This section explains how to get help for Nortel products and services.
Getting help from the Nortel Web site

The best way to get technical support for Nortel products is from the Nortel
Technical Support Web site:
www.nortel.com/support
This site provides quick access to software, documentation, bulletins, and
tools to address issues with Nortel products. More specifically, the site
enables you to:
download software, documentation, and product bulletins
search the Technical Support Web site and the Nortel Knowledge Base
for answers to technical issues
sign up for automatic notification of new software and documentation for

Nortel equipment
open and manage technical support cases
Getting help over the telephone from a Nortel Solutions

Center
If you dont find the information you require on the Nortel Technical Support
Web site, and have a Nortel support contract, you can also get help over the
phone from a Nortel Solutions Center.
In North America, call 1-800-4NORTEL (1-800-466-7835).
System Messages
Page 18 of 2360
How to get help
Outside North America, go to the following Web site to obtain the phone
number for your region:
www.nortel.com/callus
Getting help from a specialist by using an Express Routing

Code
To access some Nortel Technical Solutions Centers, you can use an Express
Routing Code (ERC) to quickly route your call to a specialist in your Nortel
product or service. To locate the ERC for your product or service, go to:
www.nortel.com/erc
Getting help through a Nortel distributor or reseller

If you purchased a service contract for your Nortel product from a distributor
or authorized reseller, contact the technical support staff for that distributor
or reseller.
553-3001-411
Standard 15.00
January 2006
24
Page 19 of 2360
About this document

This document is a global document. Contact your system supplier or your
Nortel representative to verify that the hardware and software described are
supported in your area.
Subject
This document provides information on interpreting and responding to a
system message.
Note on legacy products and releases
This NTP contains information about systems, components, and features that
are compatible with Nortel Communication Server 1000 Release 4.5
software. For more information on legacy products and releases, click the
Technical Documentation link under Support on the Nortel home page:
www.nortel.com/
Applicable systems
This document applies to the following systems:
Communication Server 1000S (CS 1000S)
Communication Server 1000M Chassis (CS 1000M Chassis)
Communication Server 1000M Cabinet (CS 1000M Cabinet)
Communication Server 1000M Half Group (CS 1000M HG)
Communication Server 1000M Single Group (CS 1000M SG)
Communication Server 1000M Multi Group (CS 1000M MG)
System Messages
Page 20 of 2360
About this document
Communication Server 1000E (CS 1000E)
Meridian 1 PBX 11C Chassis
Meridian 1 PBX 11C Cabinet
Meridian 1 PBX 51C
Meridian 1 PBX 61C
Meridian 1 PBX 81
Meridian 1 PBX 81C

Note: When upgrading software, memory upgrades may be required on
the Signaling Server, the Call Server, or both.
553-3001-411
Standard 15.00
January 2006
About this document
Page 21 of 2360
System migration
When particular Meridian 1 systems are upgraded to run CS 1000
Release 4.5 software and configured to include a Signaling Server, they
become CS 1000M systems. Table 1 lists each Meridian 1 system that
supports an upgrade path to a CS 1000M system.
Table 1
Meridian 1 systems to CS 1000M systems
This Meridian 1 system...
Maps to this CS 1000M system
CS 1000M Chassis
CS 1000M Cabinet
Meridian 1 PBX 51C
CS 1000M Half Group
Meridian 1 PBX 61C
CS 1000M Single Group
Meridian 1 PBX 81
CS 1000M Multi Group
Meridian 1 PBX 81C
CS 1000M Multi Group
For more information, see one or more of the following NTPs:
Communication Server 1000M and Meridian 1: Small System Upgrade

Procedures (553-3011-258)
Communication Server 1000M and Meridian 1: Large System Upgrade

Procedures (553-3021-258)
Communication Server 1000S: Upgrade Procedures (553-3031-258)
System Messages
Page 22 of 2360
About this document
Intended audience
This document is intended for individuals responsible for installing,
administering and maintaining Communication Server 1000 and Meridian 1
systems.
Conventions
Terminology
In this document, the following systems are referred to generically as
system:
Communication Server 1000S (CS 1000S)
Communication Server 1000M (CS 1000M)
Communication Server 1000E (CS 1000E)
Meridian 1
The following systems are referred to generically as Small System:
Communication Server 1000M Chassis (CS 1000M Chassis)
Communication Server 1000M Cabinet (CS 1000M Cabinet)
The following systems are referred to generically as Large System:
553-3001-411
Communication Server 1000M Half Group (CS 1000M HG)
Communication Server 1000M Single Group (CS 1000M SG)
Communication Server 1000M Multi Group (CS 1000M MG)
Meridian 1 PBX 51C
Meridian 1 PBX 61C
Meridian 1 PBX 81
Meridian 1 PBX 81C
Standard 15.00
January 2006
About this document
Page 23 of 2360
Related information
This section lists information sources that relate to this document.
NTPs
The following NTPs are referenced in this document:
Features and Services (553-3001-306)
Software Input/Output: Administration (553-3001-311)
Software Input/Output: Maintenance (553-3001-511)
Online
To access Nortel documentation online, click the Technical Documentation
link under Support on the Nortel home page:
www.nortel.com/
CD-ROM
To obtain Nortel documentation on CD-ROM, contact your Nortel customer
representative.
System Messages
Page 24 of 2360
553-3001-411
About this document
Standard 15.00
January 2006
26
Page 25 of 2360
Introduction
This document provides information on interpreting and responding to a
system message. System messages are typically a 3 or 4 digit number or a 3
or 4 letter mnemonic.
The following flags are included in the description of each message:
Critical to Monitor - messages are identified by support personnel as

the most important system messages to monitor on their TTY ports
and/or monitoring system.
Simple Network Management Protocol (SNMP) Trap - if a system

message in this guide is flagged as yes, the system message is generated
as an SNMP trap.
Note: Certain messages, in certain circumstances, may not be sent as an
SNMP trap, such as when a user is running a manual diagnostic.
Action - this indicates the appropriate action to clear the alarm.
Severity - this indicates the impact of the event that generated the alarm.
Severity levels
The ITG and ITS messages are generated from the Voice Gateway Media
Card, Signaling Server, and IP Phone. These messages are reported through
the Signaling Server. The Signaling Server does not have a faceplate display.
Alarms appear in the Signaling Server's report log or through the SNMP on
an Alarm browser. ITG and ITS messages incorporate the severity category
of the message in the first digit of the four-digit number.
System Messages
Page 26 of 2360
Introduction
1 = Critical: A service affecting condition has occurred and immediate

corrective action is required.
2 = Major: A service affecting condition has occurred and an urgent
corrective action is required.
3 = Minor: A non-service affecting fault condition has occurred but
corrective action should be taken in order to prevent a more serious fault.
4 = Information: A non-service affecting condition has occurred, this alarm/
event is for information only.
5 = Warning: A potential service affecting condition has been detected, and
some diagnostic action is required.
6 = Indeterminate: A service affecting condition whose impact is unknown.
Note: Signaling server and IP Line only - this severity is not used on
Call Server.
7 = Information: A non-service affecting condition has occurred, this alarm/
event is for information only.
8 = Cleared: A fault condition has been cleared either by system initiated or
user initiated action.
553-3001-411
Standard 15.00
January 2006
2310
Page 27 of 2360
ACD: Automatic Call Distribution Load

Management
The Automatic Call Distribution (ACD) Load Management feature is used by
supervisors to alter the ACD configuration in response to changing traffic
loads. Refer to the ACD Load Management NTP for details.
The ACD messages are output while load management functions are being
performed.
Messages
ACD0000
Program Identifier
Action:
Severity: Minor.
ACD0001
Critical to Monitor: No.
SNMP trap: No
Noisy ACD terminal; disabled since noise threshold exceeded.

Action:
Severity: Minor.
ACD0002
SNMP trap: No
Too many invalid characters entered on ACD terminal; disabled since invalid
character threshold was exceeded.
Action:
Severity: Minor.
ACD0003
SNMP trap: No
Invalid character entered.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 28 of 2360
ACD0004
Cannot transfer the reported agent to another queue.

Action:
Severity: Minor.
ACD0005
SNMP trap: No
Cumulative time-out count exceeded due to slow response of the high-speed

link. Traffic is too heavy. Auxiliary processor has difficulty processing the
messages.
Action:
Severity: Minor.
ACD0006
SNMP trap: No
TTY I/O block pointer for the high-speed link is nil.

Action: Remove the high-speed link in software, then redefine it. If problem
persists, perform a system reload or parallel reload.
Severity: Minor.
ACD0007
SNMP trap: No
Pointer to high-speed link data is nil. Take same action as for ADD160.
Action: Remove the high-speed link in software, then redefine it. If the problem
Severity: Minor.
ACD0008
SNMP trap: No
No call register available at this moment.

Action: If message persists, increase the number of call registers for the
customer.
Severity: Minor.
ACD0010
SNMP trap: No
Invalid input character; only blanks allowed.

Action:
Severity: Minor.
ACD0011
SNMP trap: No
Input buffer size exceeded; field too long.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 29 of 2360
ACD0012
Unknown command.
Action:
Severity: Minor.
ACD0013
SNMP trap: No
Invalid day; valid range 1 to 31.

Action:
Severity: Minor.
ACD0014
SNMP trap: No
Invalid month; valid range 1 to 12.

Action:
Severity: Minor.
ACD0015
SNMP trap: No
Invalid day-month combination.

Action:
Severity: Minor.
ACD0016
SNMP trap: No
Invalid hour; valid range 0 to 23.

Action:
Severity: Minor.
ACD0017
SNMP trap: No
Invalid schedule; valid range 0 to 3.

Action:
Severity: Minor.
ACD0018
SNMP trap: No
Invalid day of week; valid range 1 to 7.

Action:
Severity: Minor.
ACD0019
SNMP trap: No
Same day cannot be reentered.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 30 of 2360
ACD0020
Too many digits supplied for DN.

Action:
Severity: Minor.
ACD0021
SNMP trap: No
Invalid digits; valid digits are 0 to 9 and *.

Action:
Severity: Minor.
ACD0022
SNMP trap: No
Invalid digit; valid digits are 0 to 9.

Action:
Severity: Minor.
ACD0023
SNMP trap: No
DN supplied is not a valid ACD-DN.

Action:
Severity: Minor.
ACD0024
SNMP trap: No
Invalid RAN time threshold or time-out.

Action:
Severity: Minor.
ACD0025
SNMP trap: No
SNMP trap: No
Invalid RAN route.

Action:
Severity: Minor.
ACD0026
Invalid threshold values.

Action:
Severity: Minor.
ACD0027
SNMP trap: No
Queue overflow destination cannot be itself.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 31 of 2360
ACD0028
Invalid value of 'T' in TSF.

Action:
Severity: Minor.
ACD0029
SNMP trap: No
Same report option cannot be reentered.

Action:
Severity: Minor.
ACD0030
SNMP trap: No
SNMP trap: No
Invalid report option.

Action:
Severity: Minor.
ACD0031
DN supplied is not a valid trunk route access code.

Action:
Severity: Minor.
ACD0032
SNMP trap: No
Route does not auto-terminate (for SRTA command), or no members for this
route (for SRTA & SPRI commands).
Action:
Severity: Minor.
ACD0033
SNMP trap: No
Member number out of range.

Action:
Severity: Minor.
ACD0034
SNMP trap: No
Invalid member number; for SRTA command it could also mean that the
number selected did not have an auto-terminating ACD-DN defined.
Action:
Severity: Minor.
ACD0035
SNMP trap: No
SNMP trap: No
Invalid priority value.

Action:
Severity: Minor.
System Messages
Page 32 of 2360
ACD0036
No empty position for agent in new queue.

Action:
Severity: Minor.
ACD0037
SNMP trap: No
DN supplied is not a valid ACD Position-ID.

Action:
Severity: Minor.
ACD0038
SNMP trap: No
Position selected must be an agent, not a supervisor.

Action:
Severity: Minor.
ACD0039
SNMP trap: No
An agent position can only be moved to a supervisor position, not another

agent position.
Action:
Severity: Minor.
ACD0040
SNMP trap: No
SNMP trap: No
Invalid key number.

Action:
Severity: Minor.
ACD0041
Key number not reserved for agent position on supervisor's telephone.

Action:
Severity: Minor.
ACD0042
SNMP trap: No
Cannot transfer an agent position, currently being observed by its supervisor,

to another supervisor.
Action:
Severity: Minor.
ACD0043
SNMP trap: No
Command number for library command is out of range (0-99).

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 33 of 2360
ACD0044
Only a list command (LAPA, LATS, LRTA) can be stored in the library.
Action:
Severity: Minor.
ACD0045
SNMP trap: No
No message (MSG) call registers are available for sending a library command.
Action:
Severity: Minor.
ACD0046
SNMP trap: No
Invalid parameter list for library command.

Action:
Severity: Minor.
ACD0047
SNMP trap: No
Too many parameters for storage.

Action:
Severity: Minor.
ACD0048
SNMP trap: No
Too many ACD-DN; maximum is 6.

Action:
Severity: Minor.
ACD0049
SNMP trap: No
Unable to fulfill request - system error.

Action:
Severity: Minor.
ACD0050
SNMP trap: No
Data not available because of initialization.

Action:
Severity: Minor.
ACD0051
SNMP trap: No
Request for DTOT is outside of current daily reporting period.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 34 of 2360
ACD0052
Unable to fulfill request - another report is running.

Action:
Severity: Minor.
ACD0053
SNMP trap: No
Invalid input for report number.

Action:
Severity: Minor.
ACD0054
SNMP trap: No
No reports requested for DTOT/STOT.

Action:
Severity: Minor.
ACD0055
SNMP trap: No
DTOT/STOT only valid for senior supervisor.

Action:
Severity: Minor.
ACD0056
SNMP trap: No
High speed link does not exist.

Action:
Severity: Minor.
ACD0057
SNMP trap: No
High speed link is down. Codes ACD101-ACD105.

Action:
Severity: Minor.
ACD0058
SNMP trap: No
Invalid directory number.

Action:
Severity: Minor.
ACD0100
SNMP trap: No
Invalid digit. Valid digits are 0-9, * and #.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 35 of 2360
ACD0101
TLDD value must be from 10 to 1800.

Action:
Severity: Minor.
ACD0102
SNMP trap: No
All ACD-DNs specified for SQ0n must be unique.

Action:
Severity: Minor.
ACD0103 DN
SNMP trap: No
The Target ACD-DN (dn) cannot answer TOF calls for this Source ACD-DN
because it already services 6 Source ACD-DNs.
Action: To define the TLDD value remove the affected Target ACD-DN from this
source ACD-DN or from another Source ACD-DN.
Severity: Minor.
ACD0104 DN
SNMP trap: No
When deleting the Target ACD-DN (dn) from a Source ACD-DN with a TOFT
value defined, the Source TOF queue address could not be found in the
unprotected line block. This may indicate corrupted data (see BUG88) and the
Source TOF calls are not terminating to the Target Agents.
Action: Run the Audit Program (LD 44) and/or perform manual Initialization. If
the problem persists , contact your service representative.
Severity: Minor.
ACD0105
SNMP trap: No
The TLDD command is not allowed when the TOF package is restricted.
Codes above ACD106 apply to X11, Release 12 and later.
Action:
Severity: Minor.
ACD0106
SNMP trap: No
Valid only for ACD Package D services.

Action:
Severity: Minor.
ACD0107
SNMP trap: No
The Priority Agent Package (PRI) is not equipped.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 36 of 2360
ACD0108
This command is only valid with the Load Management package equipped.
Action:
Severity: Minor.
ACD0109
SNMP trap: No
Agent Priority is out of range. Ranges: NT and XT = 1-48 All others = 1-32
(This includes RT.)
Action:
Severity: Minor.
ACD0115
SNMP trap: No
Command is only valid when ACD Package B is equipped.

Action:
Severity: Minor.
ACD0116
SNMP trap: No
Command is not valid for ACD-D customers.

Action:
Severity: Minor.
ACD0117
SNMP trap: No
The STOR command was not completed successfully.

Action:
Severity: Minor.
ACD0211
SNMP trap: No
Call is in the TOF queue, but the TOF call bit is not set.
Action:
Severity: Minor.
ACD0212
SNMP trap: No
Call is not in the TOF queue, but the TOF bit is set.
Action:
Severity: Minor.
ACD0213
SNMP trap: No
A Ring Again (RGA) call is in the TOF queue.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 37 of 2360
ACD0214
A Call Party Recall call is in the TOF queue.

Action:
Severity: Minor.
ACD0300
SNMP trap: No
Package for M2216 sets is not equipped.

Action:
Severity: Minor.
ACD0301
SNMP trap: No
The message number is out-of-range (0-99).

Action:
Severity: Minor.
ACD0302
SNMP trap: No
The distribution list number is out-of-range (0-9).

Action:
Severity: Minor.
ACD0303
SNMP trap: No
The entry number is out-of-range (0-9).

Action:
Severity: Minor.
ACD0304
SNMP trap: No
SNMP trap: No
Allocate block failed.

Action:
Severity: Minor.
ACD0310
Command not available without the NACD package 178.

Action:
Severity: Minor.
ACD0311
SNMP trap: No
You cannot use the NITE command with Night Tables defined in NACD.
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 38 of 2360
ACD0312
You cannot use the TLDD command with Day Tables defined in NACD.
Action:
Severity: Minor.
ACD0313
SNMP trap: No
Invalid Table name. Only D (Day) and N (Night) are valid.

Action:
Severity: Minor.
ACD0314
SNMP trap: No
Input value is out-of-range.

Action:
Severity: Minor.
ACD0315
SNMP trap: No
The specified Target table is full.

Action:
Severity: Minor.
ACD0319
SNMP trap: No
The Advance Network package 148 and Network ACD package 178 are
required for Targets across the Network.
Action:
Severity: Minor.
ACD0320
SNMP trap: No
No Night Table has been defined for this ACD-DN.

Action:
Severity: Minor.
ACD0321
SNMP trap: No
No Day Table has been defined for this ACD-DN.

Action:
Severity: Minor.
ACD0322
SNMP trap: No
This Target ID does not exist in the table specified.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 39 of 2360
ACD0323
Only the Senior Supervisor can execute this command.

Action:
Severity: Minor.
ACD0324
SNMP trap: No
This ACD-DN does not have any routing tables defined.

Action:
Severity: Minor.
ACD0325
SNMP trap: No
You do not have enough memory left to allocate for this routing table.
Action:
Severity: Minor.
ACD0326
SNMP trap: No
You cannot define a new Day Table when this ACD-DN still has a TOFT
defined.
Action:
Severity: Minor.
ACD0327
SNMP trap: No
You cannot define a new Night Table when the NCFW DN is defined for this
ACD-DN.
Action:
Severity: Minor.
ACD0328
SNMP trap: No
The CWLF or CWLW thresholds cannot be defined or changed unless the

NCWL option is set in LD 23.
Action:
Severity: Minor.
ACD0329
SNMP trap: No
Commands only accepted when RPRT = Yes.

Action:
Severity: Minor.
ACD0330
SNMP trap: No
Commands only valid if EAR package is equipped.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 40 of 2360
ACD0331
Commands only valid if CCR package is equipped.

Action:
Severity: Minor.
ACD0332
SNMP trap: No
That DN is not a valid Control DN.

Action:
Severity: Minor.
ACD0333
SNMP trap: No
Invalid input. Expected response is either ON or OFF.

Action:
Severity: Minor.
ACD0334
SNMP trap: No
Commands not valid for a CDN.

Action:
Severity: Minor.
ACD0336
SNMP trap: No
Cannot change the CNTL option from NO to YES if the VSID for the CDN is
not defined.
Action:
Severity: Minor.
ACD0337
SNMP trap: No
Cannot change the TSFT option for a CDN with CNTL set to NO.
Action:
Severity: Minor.
ACD0338
SNMP trap: No
An ACD DN defined for data service access may not be used

as a default ACD DN.
Action:
Severity: Minor.
ACD0339
SNMP trap: No
Cannot change the TLDA option for a CDN with CNTL set to NO.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 41 of 2360
ACD0340
Cannot change the TLDB option for a CDN with CNTL set to NO.
Action:
Severity: Minor.
ACD0341
SNMP trap: No
Cannot change the TLDC option for a CDN with CNTL set to NO.
Action:
Severity: Minor.
ACD0342
SNMP trap: No
Default ACD DN must be a valid ACD DN.

Action:
Severity: Minor.
ACD0343
SNMP trap: No
Command not available without the Supplementary features package 131.

Action:
Severity: Minor.
ACD0344
SNMP trap: No
RTQT must be set in range 0-30

Action:
Severity: Info.
ACD0345
SNMP trap: No
To enable FORC please set RTQT to 0 or to enable RTQT please set FORC
to no.
Action:
Severity: Info.
ACD0346
SNMP trap: No
DN entered is not a valid MQA ACD DN.

Action:
Severity: Info.
ACD0347
SNMP trap: No
User has entered a duplicate ACD DN for the MQA agent.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 42 of 2360
ACD0348
Not valid for MQA agent.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 43 of 2360
ADD: Automatic Call Distribution Data

Dump
Automatic Call Distribution (ACD) data is dumped using the ACD Data Dump
(ADD) program. ADD is only available when the ACD Auxiliary Data System
(ACD-ADS) is equipped. ACD-ADS is documented as a special feature in the
Automatic Trunk Maintenance NTP.
The ADD program is loaded automatically by the system on receipt of an
AUXUP command from the auxiliary processor. The program cannot be
invoked manually and, when in use, cannot be aborted. Once loaded, ACD
configuration data is sent to the auxiliary processor from the SL-1 through the
high-speed link.
Messages
ADD0000
ADD Program is running.

Action:
Severity: Info.
ADD0009
Critical to Monitor: Yes.
SNMP trap: No
SNMP trap: Yes
Program aborted.
Action:
Severity: Minor.
ADD0099
High speed link is down.

Action: Use Link Diagnostic (LD 48) to check link status.
Severity: Minor.
ADD0100
SNMP trap: Yes
High-speed link is down.

Action:
Severity: Minor.
ADD0101
SNMP trap: Yes
Re-attempt to get message call register (CR) failed. The SL-1 has run out of
call registers.
Action: Increase the number of call registers (not the number of message call
registers).
Severity: Minor.
SNMP trap: Yes
System Messages
Page 44 of 2360
ADD0102 C
ACD list cannot be found for customer c.

Action:
Severity: Minor.
ADD0103 L S C U
SNMP trap: Yes
Terminal Number translation failed.
Action:
Severity: Minor.
ADD0104 L S C U
SNMP trap: Yes
Key 0 of the set is not an ACD-DN.
Action:
Severity: Minor.
ADD0105 L S C U
SNMP trap: Yes
SNMP trap: Yes
TN is not equipped.
Action:
Severity: Minor.
ADD0150 C
No route for customer c.

Action:
Severity: Minor.
ADD0151
SNMP trap: Yes
SNMP trap: Yes
No trunk number.
Action:
Severity: Minor.
ADD0160
Enqueuing to send message failed. Data associated with the high-speed link
may be corrupted.
Severity: Minor.
ADD0170
SNMP trap: Yes
AUX did not respond to AUX_M_SIN message.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 45 of 2360
ADD0180
The chosen release protocol by the AUX is not within the range specified by
SL-1.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 46 of 2360
553-3001-411
Standard 15.00
January 2006
Page 47 of 2360
AMH: Auxiliary Message Handler

The resident Auxiliary Message Handler program is used to communicate with
the Automatic Call Distribution Package D (ACD-D) auxiliary processor. Error
codes from this resident program are prefixed with AMH. The AMH program is
available only when the ACD Auxiliary Data System (ACD-ADS) feature is
equipped.
The AMH messages indicate hardware or software faults on the auxiliary
processor. The format of these error messages is distinct from that for SL-1
error messages. Refer to the manufacturer's documentation or follow local
procedures to determine the action to be taken in response to Auxiliary
Processor error messages.
Messages
AMH0000
Program Identifier.
Action:
Severity: Info.
AMH0001
SNMP trap: No
Output buffer not empty; counter limit exceeded.

Action: Check Serial Data Interface (SDI) associated with the high-speed link
(see LD 48).
Severity: Critical.
AMH0002
SNMP trap: Yes
High-speed link is down. The SL-1 has declared the link to be no good for
transmission of application messages. Usually means the auxiliary processor
has difficulty handling the messages.
Action:
Severity: Critical.
AMH0003
SNMP trap: Yes
Cumulative Negative Acknowledgment (NAK) count exceeded due to noisy

high-speed link.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 48 of 2360
AMH0004
The SL-1 and the auxiliary processor are out of synchronization.

Action: Check baud rates of the SDI for the high-speed link and high-speed link
port on the auxiliary processor. Check high-speed link cable.
Severity: Critical.
AMH0005
SNMP trap: Yes
Cumulative time-out count exceeded due to slow response of the high-speed

link. Traffic is too heavy. Auxiliary processor has difficulty processing the
messages. This message occurs when 10 or more timeouts have occurred on
Acknowledgments (ACK) from the AUX in a 30 minute period. The time-out
counter is reset every 30 minutes. Timeout is an appropriate ACK not received
within normal 2 second period. (True time-out period may very from 0.001 to
21.99 seconds.) Timeouts greater than 22 seconds will cause the link to drop
with an AMH002 message.
Action:
Severity: Minor.
AMH0006
SNMP trap: Yes
TTY I/O block pointer for high-speed link is nil. Take same action as for
ADD160.
persists, perform a system reload or parallel reload
Severity: Minor.
AMH0007
SNMP trap: Yes
Pointer to high-speed link data is nil.

Action: Remove the high speed link in software, then redefine it. If problem
Severity: Minor.
AMH0008
SNMP trap: Yes
No call register available at this moment.

Action: If message persists, increase the number of call registers for the
customer.
Severity: Minor.
AMH0010
SNMP trap: Yes
The SL-1 System ID does not match the AUX ACD_D disk directory.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 49 of 2360
AMH0011
The AUX could not select a release protocol from the high and low specified
by the SL-1.
Action:
Severity: Minor.
AMH0012
SNMP trap: Yes
MAX using protocol <=.RLS23_PROTOCOL cannot support reporting for

more than 240 queues. The number of queues with RPRT = Yes exceeds this
limit of 240.
Action:
Severity: Info.
AMH0200
SNMP trap: Yes
Warning: the process of transferring data from the output buffer in memory to
the output data register on the SDI card locked once but is now recovered.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 50 of 2360
553-3001-411
Standard 15.00
January 2006
Page 51 of 2360
AML: Application Module Link (LD 48)

An Application Module Link (AML) connects the system with applications such
as Meridian Mail, Meridian Link and CCR. These links are provided by
Enhanced Serial Data Interface (ESDI) or Multi-purpose Serial Data Interface
(MSDL) cards.
LD 48 is used to maintain these links. AML messages are output to indicate
command error and status conditions on these links.
Messages
AML0001 x
ESDI: To enable CSL, ESDL has to be in "BUSY" state. Where x= AML

number in decimal.
Action:
Severity: Info.
AML0002 x
SNMP trap: No
ESDI/MSDL: For SWCH AML n1 n2 command, both links should belong to the
same VAS. Where x= AML number in decimal.
Action:
Severity: Info.
AML0003 x
SNMP trap: No
ESDI/MSDL: For SWCH AML n1 n2 command, n2 should be in the STANDBY

state. Where x=AML number in decimal.
Action:
Severity: Info.
AML0004 x
SNMP trap: No
No VAS ID exists for the given AML. Therefore layer seven cannot be enabled.
Where: x= AML number in decimal.
Action:
Severity: Info.
AML0005 x
SNMP trap: Yes
ESDI/MSDL: For SWCH AML n1 n2 command, n1 should be in the ACTIVE

state. Where: x= AML number in decimal.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 52 of 2360
AML0006 x
ESDI/MSDL: There is no response to polling message. Where: x= AML

number in decimal.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 53 of 2360
AMLM: Application Module Link

Maintenance (LD 48)
An Application Module Link (AML) connects the system with applications such
as Meridian Mail, Meridian Link and CCR. These links are provided by
Enhanced Serial Data Interface (ESDI) or Multi-purpose Serial Data Interface
(MSDL) cards.
LD 48 is used to maintain these links. AMLM messages are output to indicate
command error and status conditions on these links.
Messages
AMLM0001 x
Illegal card type on AML x. Only ESDI or MSDL cards are allowed.
Action:
Severity: Minor.
AMLM0002 x
SNMP trap: Yes
For SMLP command, both ports must be in the loop back mode.
Action: Issue CNFG command first.
Severity: Minor.
AMLM0003 x
SNMP trap: Yes
The address of the ESDI status register on AML x is corrupt.

Action:
Severity: Minor.
AMLM0004 x
SNMP trap: Yes
For SMLP command both ESDI ports must be in IDLE state.

Action:
Severity: Minor.
AMLM0006 x
SNMP trap: Yes
Automatic Set Up command not supported for MSDL AML x.

Action: For MSDL AML, first ensure the MSDL AML auto recovery is turned ON.
Next enable the link using ENL AML #. This will establish and enable the layer 7
for the MSDL AML.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 54 of 2360
AMLM0007 x
AML background AUDIT not supported for ESDI AML.

Action:
Severity: Minor.
AMLM0008
SNMP trap: Yes
Both of the MSDL AML links must be in the disabled state. Then the
stimulation loop back command can be issued.
Action:
Severity: Minor.
AMLM0009
SNMP trap: Yes
Loop back from ESDI to MSDL or MSDL to ESDI not allowed.

Action:
Severity: Minor.
AMLM0010 x
SNMP trap: Yes
The MSDL AML command request is rejected since link x is already disabled.
Action:
Severity: Minor.
AMLM0011 x
SNMP trap: Yes
The MSDL AML command request is rejected, since link x is already

established.
Action:
Severity: Minor.
AMLM0012 x
SNMP trap: Yes
The MSDL AML command request is rejected, since link x is already released.
Action:
Severity: Minor.
AMLM0013 x
SNMP trap: Yes
The MSDL AML command request is rejected, since link x is already enabled.
Action:
Severity: Minor.
AMLM0014 x
SNMP trap: Yes
The MSDL AML command request is rejected, since link x is in process of self
test.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 55 of 2360
AMLM0015 x
The MSDL AML command request is rejected, since link x is in process of

establishing.
Action:
Severity: Minor.
AMLM0016 x
SNMP trap: Yes

releasing.
Action:
Severity: Minor.
AMLM0017 x
SNMP trap: Yes

disabling.
Action:
Severity: Minor.
AMLM0018 x
SNMP trap: Yes

loadware downloading.
Action:
Severity: Minor.
AMLM0019 x
SNMP trap: Yes

auditing.
Action:
Severity: Minor.
AMLM0020 x
SNMP trap: Yes
The MSDL AML command request is rejected, since link x is in the disable
state.
Action: First use the ENL AML # command.
Severity: Minor.
AMLM0021 x
SNMP trap: Yes
The MSDL AML command request is rejected, since link x is not in the disable
state.
Action: First use the DIS AML # command.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 56 of 2360
AMLM0022 x
The ESDI AML or MSDL AML command is rejected since it is not allowed at
this point.
Action:
Severity: Minor.
AMLM0023 x
SNMP trap: Yes
Data corruption. The ESDI AML IO priority number is corrupted on AML x.

Action:
Severity: Minor.
AMLM0024 x
SNMP trap: Yes
There is no response from the ESDI card. The ESDI hardware may not be
equipped.
Action:
Severity: Minor.
AMLM0025 x
SNMP trap: Yes
Error: ESDI in permanent interrupt.

Action:
Severity: Minor.
AMLM0026 x
SNMP trap: Yes
For ESDI self test, the port under test should be in IDLE state and the other
port of the ESDI card, if defined should be in the DISABLE state.
Action:
Severity: Minor.
AMLM0027 x
SNMP trap: Yes
The MSDL AML request is rejected, since the MSDL card is not operational.
Action:
Severity: Minor.
AMLM0028 x
SNMP trap: Yes
Warning: AML x is disabled and will not recover. This is regardless of the fact
that the AML auto recovery was previously turned to the ON mode. The MSDL
AML loadware requested to disable the link, and since this type of disable is
not recoverable, the Meridian 1 will disable the link and will not attempt to
recover.
Action: You must manually enable the AML link to bring the link up again.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 57 of 2360
AMLM0029
Warning: The AML is disabled and will not recover, since the MSDL AML
background AUDIT failed to recover from the failure. This is regardless of the
fact that the AML auto recovery was previously turned to the ON mode.
Action: You must manually enable the AML link to bring the link up again.
Severity: Minor.
AMLM0030
SNMP trap: Yes
The reset command is not supported for the ESDI AML. The command is only
supported for MSDL AML.
Action:
Severity: Minor.
AMLM0031
SNMP trap: Yes
The reset command is allowed only when the link is established, and no
pending link tasks are queued.
Action:
Severity: Minor.
AMLM0032
SNMP trap: Yes
Since the link is resetting the outgoing AML command is not executed.
Action: Wait until the link reset activity is terminated, and then try the command
again.
Severity: Minor.
AMLM0033
SNMP trap: Yes
Warning: The AML went into an audit. After the audit it was determined that
the link should recover to the disable state. If the auto recovery is turned ON,
then regardless of it, the AML will remain in the disable state and will not
attempt to recover.
Action: The craftsperson should manually bring the link up.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 58 of 2360
553-3001-411
Standard 15.00
January 2006
Page 59 of 2360
ATM: Automatic Trunk Maintenance (LD

92)
The Automatic Trunk Maintenance (ATM) program tests TIE, CSA, WATS,
FEX, DID and COT trunk groups automatically each day, at times scheduled
in the ATM Schedule Block. The ATM program also allows the manual testing
of trunks.
Messages
ATM0000
Program identifier.
Action:
Severity: Info.
ATM0001
SNMP trap: No
No schedule block exist.

Action:
Severity: Info.
ATM0002
SNMP trap: Yes
No schedule block for this hour.

Action:
Severity: Info.
ATM0003
SNMP trap: Yes
ATM aborted because it cannot perform far to near test.

Action:
Severity: Info.
ATM0004
SNMP trap: Yes
User specified reference trunk does not meet loss criteria for reference trunk.
Action:
Severity: Info.
ATM0005
SNMP trap: Yes
SNMP trap: No
Illegal input character

Action:
Severity: Info.
System Messages
Page 60 of 2360
ATM0006
Loop out-of-range
Action:
Severity: Info.
ATM0007
SNMP trap: No
SNMP trap: No
Shelf out-of-range
Action:
Severity: Info.
ATM0008
Terminal Number translation (TNTRANS) failed on Tone Detector

Action:
Severity: Info.
ATM0009
SNMP trap: Yes
No Tone Detector available to proceed onward.

Action:
Severity: Info.
ATM0010
SNMP trap: Yes
No Tone Detector is defined in the data base, or Tone Detector failed self-test
Action:
Severity: Info.
ATM0011
SNMP trap: Yes
SNMP trap: No
Missing ATM route data

Action:
Severity: Info.
ATM0015
ATM got wrong loop message.

Action:
Severity: Info.
ATM0016
SNMP trap: Yes
Tone detector is not maintenance busy when it should be, the system sets it.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 61 of 2360
ATM0018
User specified reference trunk is not available.

Action:
Severity: Info.
ATM0020
SNMP trap: Yes
Given trunk is unequipped.

Action:
Severity: Info.
ATM0041 C
SNMP trap: Yes
Customer c does not exist.

Action:
Severity: Info.
ATM0042 C
SNMP trap: Yes
Customer number c is out-of-range.

Action:
Severity: Info.
ATM0051 C R
SNMP trap: Yes
Customer c, Route r does not exist.

Action:
Severity: Info.
ATM0052 C R
SNMP trap: Yes
Customer c, Route r has no member.

Action:
Severity: Info.
ATM0053 C R
SNMP trap: Yes
Customer c, Route r has no ATM data.

Action:
Severity: Info.
ATM0054 C R
SNMP trap: Yes
Cannot find any reference trunk for customer c, route r to perform near to far
test.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 62 of 2360
ATM0055 C R
Customer c, Route number r is out-of-range.

Action:
Severity: Info.
ATM0056 C R
SNMP trap: Yes
Member number is out-of-range for customer c, route r.

Action:
Severity: Info.
ATM0057 C R
SNMP trap: Yes
Member number is not defined for specified customer c, route r.

Action:
Severity: Info.
ATM0058 C R
SNMP trap: Yes
ATM aborted because this customer c, route r has FEDC equal to FEC.
Action:
Severity: Info.
ATM0059 C R
SNMP trap: Yes
For ATMU and ATMC commands, the test and reference trunk units cannot be
the same.
Action:
Severity: Info.
ATM0071 C R M
SNMP trap: Yes
Missing active call register during test of customer c, route r, member m, most
probably because far-end on-hook.
Action:
Severity: Info.
ATM0201
SNMP trap: Yes
Last command is still in progress.

Action:
Severity: Info.
ATM0202
SNMP trap: Yes
SNMP trap: Yes
Invalid argument(s).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 63 of 2360
ATM0203
Invalid command.
Action:
Severity: Info.
ATM0204
SNMP trap: Yes
Loop for first TN is out-of-range.

Action:
Severity: Info.
ATM0205
SNMP trap: Yes
Loop for second TN is out-of-range.

Action:
Severity: Info.
ATM0206
SNMP trap: Yes
Loop type for first TN is not supported by ATM.

Action:
Severity: Info.
ATM0207
SNMP trap: Yes
Loop type for second TN is not supported by ATM.

Action:
Severity: Info.
ATM0208
SNMP trap: Yes
Shelf for first TN is out-of-range.

Action:
Severity: Info.
ATM0209
SNMP trap: Yes
Shelf for second TN is out-of-range.

Action:
Severity: Info.
ATM0210
SNMP trap: Yes
Card for first TN is out-of-range.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 64 of 2360
ATM0211
Card for second TN is out-of-range.

Action:
Severity: Info.
ATM0212
SNMP trap: Yes
Card for first TN does not exist in the data base.

Action:
Severity: Info.
ATM0213
SNMP trap: Yes
Card for second TN does not exist in the data base.

Action:
Severity: Info.
ATM0214
SNMP trap: Yes
Card type for first TN is not a trunk.

Action:
Severity: Info.
ATM0215
SNMP trap: Yes
Card type for second TN is not a trunk.

Action:
Severity: Info.
ATM0216
SNMP trap: Yes
Unit for first TN is out-of-range.

Action:
Severity: Info.
ATM0217
SNMP trap: Yes
Unit for second TN is out-of-range.

Action:
Severity: Info.
ATM0218
SNMP trap: Yes
Unit for first TN does not exist in the data base.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 65 of 2360
ATM0219
Unit for second TN does not exist in the data base.

Action:
Severity: Info.
ATM0220
SNMP trap: Yes
Unit trunk type for first TN is not supported by ATM.

Action:
Severity: Info.
ATM0221
SNMP trap: Yes
Unit trunk type for second TN is not supported by ATM.

Action:
Severity: Info.
ATM0222
SNMP trap: Yes
Channel for first TN is out-of-range.

Action:
Severity: Info.
ATM0223
SNMP trap: Yes
Channel for second TN is out-of-range.

Action:
Severity: Info.
ATM0224
SNMP trap: Yes
Loop and Channel for first TN is invalid.

Action:
Severity: Info.
ATM0225
SNMP trap: Yes
Loop and Channel for second TN is invalid.

Action:
Severity: Info.
ATM0226
SNMP trap: Yes
Channel for first TN does not exist in the data base.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 66 of 2360
ATM0227
Channel for second TN does not exist in the data base.

Action:
Severity: Info.
ATM0228
SNMP trap: Yes
Channel for first TN is not configured as a trunk.

Action:
Severity: Info.
ATM0229
SNMP trap: Yes
Channel for second TN is not configured as a trunk.

Action:
Severity: Info.
ATM0230
SNMP trap: Yes
Specified TNs not for same customer.

Action:
Severity: Info.
ATM0231
SNMP trap: Yes
Specified TNs not for same route.

Action:
Severity: Info.
ATM0232
SNMP trap: Yes
Loop for first TN does not exist in the data base.

Action:
Severity: Info.
ATM0233
SNMP trap: Yes
Loop for second TN does not exist in the data base.

Action:
Severity: Info.
ATM0235
SNMP trap: Yes
Loop for first TN is not a superloop.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 67 of 2360
ATM0236
Loop for second TN is not a superloop.

Action:
Severity: Info.
ATM0240
SNMP trap: Yes
TDET is restricted. Disk does not have Tone Detector package 65 enabled.
Action:
Severity: Info.
ATM0241
SNMP trap: Yes
TN/Route tested is not an ADM TN/Route.

Action:
Severity: Info.
ATM0242
SNMP trap: Yes
RETEST. For TNs in IDLE_STATUS and ABRT_RESULT.

Action:
Severity: Info.
SNMP trap: Yes
ATM0301 L S C U X Y The specified Tone Detector has failed testing due to faulty operation or
lack of response. x and y indicate the mode and test that failed.
Action:
Severity: Info.
ATM0302
SNMP trap: Yes
The specified tone detector cannot be used by ATM because it was unable to
perform the self-test.
Action:
Severity: Info.
ATM0304
SNMP trap: Yes
No tone and digit switch is available for tone detector testing.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 68 of 2360
553-3001-411
Standard 15.00
January 2006
Page 69 of 2360
AUD: Software Audit (LD 44)

LD 44 monitors system operation and provides an indication of the general
state of system operation. The program is concerned with the system
software. When a software problem is encountered, the program attempts to
clear the problem automatically.
Audit messages are not to be interpreted as hardware faults though certain
codes can indicate hardware-related problems. Ignore the audit outputs for
normal system maintenance, when classifying and isolating faults. When audit
outputs are excessive or continue to occur, the problem must be reported.
*CRINFO = Any Call Register (CR) information that follows an AUD message
consists of: CR pointer, the progress mark word, and the originating and
terminal numbers contained in the CR (4 words in total).
Messages
AUD0000
One pass made by audit. No errors detected. System software OK.

Action: No action to be taken.
Severity: Info.
AUD0001
SNMP trap: Yes
An attendant CR pointer is pointing outside the Call Register (CR) range.

Source list or destination pointer set to nil. Terminal Number (TN), CR
information, attendant loop and progress mark are output.
Action:
Severity: Minor.
AUD0002
SNMP trap: Yes
Attendant CR pointer is pointing to CR which does not contain its TN. Source
list or destination list set to nil. TN, CR information attendant loop and progress
mark are output.
Action:
Severity: Minor.
AUD0003
SNMP trap: Yes
Station active Call Register pointer is outside CR range. Active CR pointer set
to nil. TN, CR information and progress mark are output.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 70 of 2360
AUD0004
Digitone receiver is pointing to CR which does not contain its TN. Active Call
Register of Digitone receiver set to nil. TN, CR information and progress mark
are output.
Action:
Severity: Minor.
AUD0005
SNMP trap: Yes
Station (line, trunk) pointing to CR which does not contain its terminal number.
Active Call Register set to nil. TN, CR information and progress mark are
output.
Action:
Severity: Minor.
AUD0006
SNMP trap: Yes
Given queue has incorrect block length. Length in queue block is corrected.
Action:
Severity: Minor.
AUD0007
SNMP trap: Yes
Given block was found in queue but QUEUE UNIT block pointer was incorrect.
Queue is corrected. Block pointer, type, queue.
Action:
Severity: Minor.
AUD0008
SNMP trap: Yes
Conference pointer is pointing to CR outside of CR range. Conference pointer

is set to nil. CR information, conference loop, conference slot and progress
mark are output.
Action:
Severity: Minor.
AUD0009
SNMP trap: Yes
Conference pointer is pointing to CR which does not contain its conference

loop, time slot or TN. Conference pointer is set to nil. CR information,
conference loop, conference slot and progress mark are output. If repeated,
fault may be in conference card.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 71 of 2360
AUD0010
Conference pointer is pointing to CR which does not have originating type as

conference. TN, CR information and progress mark output. If repeated, fault
may be in conference card.
Action: No action. Refer problem to operating company.
Severity: Minor.
AUD0011
SNMP trap: Yes
End pointer of queue not pointing to last CR in the queue. Relink. Head
pointer, end pointer and queue output.
Action:
Severity: Minor.
AUD0012
SNMP trap: Yes
Link queue contains CR with its CR link outside of CR range. Relink. Head
pointer, CR link, queue output.
Action:
Severity: Minor.
AUD0014
SNMP trap: Yes
Call Register not in expected queue. Link into queue. CR information, queue
and progress mark output.
Action:
Severity: Minor.
AUD0015
SNMP trap: Yes
Trunk block contains incorrect TN. Correct TN.

Action:
Severity: Minor.
AUD0016
SNMP trap: Yes
CR should be unlinked. Unlinks CR. CR information and progress mark output.

Action:
Severity: Minor.
AUD0017
SNMP trap: Yes
Network even map is not the same as the network even audit map. Network
map has been updated to match audit map. No Action required. Output: Loop,
network even map, and network even audit map.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 72 of 2360
AUD0018
Network odd map is not the same as the network odd map. Network map has
been updated to match audit map. Output: Loop, network odd map, and
network odd audit map.
Action: No Action required.
Severity: Minor.
AUD0019
SNMP trap: Yes
Network audit indicates time slot is not in use but network memory is marked
busy. Time slot is marked idle. Output: Slot address and memory contents are
output.
Action: If AUD019 is repeated, particularly without AUD0017 and AUD0018 a
fault in the peripheral signaling card may be indicated. Check PS card.
Severity: Minor.
AUD0020
SNMP trap: Yes
Attendant loop is greater than the allowable maximum of five.

Action: Contact operating company. CR information and progress mark output.
Severity: Minor.
AUD0021
SNMP trap: Yes
TN in CR does not have pointer to this CR. TN in CR cleared. CR information

and progress mark output.
Action:
Severity: Minor.
AUD0022
SNMP trap: Yes
CR for Recorded Announcement (RAN) trunk is used with incorrect TN. CR is

idled.
Action:
Severity: Minor.
AUD0023
SNMP trap: Yes
Digitone receiver still attached even though progress mark not ready or
dialing. Digitone receiver made idle. CR information and progress mark output.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 73 of 2360
AUD0024
CR contains invalid Digitone receiver TN. Digitone receiver TN in CR cleared.

CR information and progress mark output.
Action:
Severity: Minor.
AUD0026
SNMP trap: Yes
Circular link queue. Relinked. Queue is output.

Action:
Severity: Minor.
AUD0027
SNMP trap: Yes
Invalid AUXPM in Call Register. Call register information is output. The Call
Register is idled.
Action:
Severity: Minor.
AUD0028
SNMP trap: Yes
Call Register (CR) has no pointer to it. The CR has been released. No action
required. Output: CR information, TN and progress mark
Action:
Severity: Minor.
AUD0029
SNMP trap: Yes
Bad TN in CR. No action. Contact operating company. CR information, TN and

progress mark output.
Action:
Severity: Minor.
AUD0030
SNMP trap: Yes
Call Register has type AIOD (Automatically Identified Outward Dialing) but CR
is not in AIOD queue. CR is idled. CR information is output.
Action:
Severity: Minor.
AUD0031
SNMP trap: Yes
Junctor map is not the same as the junctor audit map. Junctor map is
corrected. Junctor group, junctor map and junctor audit map are output.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 74 of 2360
AUD0032
Junctor audit indicates a timeslot is idle but the junctor memory is marked
busy. Time slot is marked idle. Junctor address and memory contents are
output.
Action:
Severity: Minor.
AUD0033
SNMP trap: Yes
Circular list of auxiliary Call Registers is broken. All known CR in the list are
idled including the father CR. CR information, auxiliary CR ID, Process Type
and Pointer to next auxiliary are output for each CR idled.
Action:
Severity: Minor.
AUD0034
SNMP trap: Yes
An auxiliary ARS Call Register points to a main Call Register which has an
illegal main PM. The auxiliary CR is idled. CR information for the main CR and
the auxiliary CR are output.
Action:
Severity: Minor.
AUD0035
SNMP trap: Yes
End of Call Detail Recording (CDR) queue reached without finding a CR for
the port but the port pointer is not END_OF_QUEUE. The port pointer is set to
END_OF_QUEUE. Port number is output.
Action:
Severity: Minor.
AUD0036
SNMP trap: Yes
The port is not a CDR port but the port pointer does not point to
END_OF_QUEUE. The port pointer is set to END_OF_QUEUE. Port number
is output.
Action:
Severity: Minor.
AUD0037
SNMP trap: Yes
The CDR queue is broken. The port pointer is set to the start of the CDR
queue. Port number is output.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 75 of 2360
AUD0038
The first CR for a CDR port number has been found but the port pointer does
not point to it. The port pointer is made to point to the CR. Port, CDR customer
are output.
Action:
Severity: Minor.
AUD0039
SNMP trap: Yes
A CDR CR has invalid port bits set in the CR. Invalid bits are cleared. Port,
CDR customer are output.
Action: Customer Data Block (CDB) should be checked for errors in data.
Severity: Minor.
AUD0040
SNMP trap: Yes
A CDR CR has been found with no port bits set while Auditing a port queue.
The CR is idled. Output: port, CDR customer.
Action:
Severity: Minor.
AUD0041
SNMP trap: Yes
The successor of an RGAT CR has a higher priority than the CR itself.

Successor priority is set to the CR priority. Output is 4 pairs of numbers, the
first referring to the CR, the second to the successor. The pairs are RGAT
priority, RGA_PM, ORIGTN and CR address.
Action:
Severity: Minor.
AUD0042
SNMP trap: Yes
Terminal does not match TN in Call Register. Terminal CR information output.

RLA pointer pointing to the CR is cleared.
Action:
Severity: Minor.
AUD0043
SNMP trap: Yes
RLA Call Register pointer is not in Call Register range. Output: RLA_CR_PTR,
CR information. RLA CR pointer is cleared.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 76 of 2360
AUD0044
CR with main Progress Mark of RLA_CONF_DISC found. Output: CR info. CR

is idled.
Action:
Severity: Minor.
AUD0045
SNMP trap: Yes
RLA Call Register is found, but there are no pointers in the RLA block to this
Call Register. Output: CR information. CR is idled.
Action:
Severity: Minor.
AUD0046
SNMP trap: Yes
Unable to TNTRANS RLA TN. Output: TN, CR information. CR is idled.

Action:
Severity: Minor.
AUD0047
SNMP trap: Yes
A talk slot is set in the Call Register but the RLA_CONF_TN is set in the RLA
block while the pointer to the CR is RLA_INFO. Output: CR information. Talk
slot is idled.
Action:
Severity: Minor.
AUD0048
SNMP trap: Yes
Either the originating or terminating TN is not set in an RLA CR with a talk slot.
Output: CR information. Talk slot idled.
Action:
Severity: Minor.
AUD0049
SNMP trap: Yes
Unable to find protected loop block for Tone Detector (TD) slot in RLA CR.
Output: TD SLOT and CR information.
Action:
Severity: Minor.
AUD0050
SNMP trap: Yes
Protected loop block found via TD slot in RLA Call Register but loop type is not
TD loop. Output: PLOOP block, loop type, TD slot and CR information.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 77 of 2360
AUD0051
Protected loop block found via TD slot in RLA CR but ULOOP block pointer is
nil. Output: PLOOP block, loop type, TD slot and CR information.
Action:
Severity: Minor.
AUD0052
SNMP trap: Yes
TD slot set in RLA CR but no valid TN can be found. Output: TD slot and CR
information. CR is idled.
Action:
Severity: Minor.
AUD0054
SNMP trap: Yes
Main PM is CAS_INFO_TONE but the RLA_INFO pointer in the RLA block is

not pointing to this Call Register. Output: CR information. CR is idled.
Action:
Severity: Minor.
AUD0055
SNMP trap: Yes
The main PM is neither ringing nor established but the pointer in the RLA block
to this RLA Call Register is not RLA_DEST. Output: CR information. CR is
idled.
Action:
Severity: Minor.
AUD0056
SNMP trap: Yes
Nil pointer to ACD_LIST or U_ACD_BLOCK. Output: Customer and

ACD_LIST_PTR.
Action:
Severity: Minor.
AUD0057
SNMP trap: Yes
Queue ID of Automatic Call Distribution (ACD) queue is not ACD. Output:

Customer, U-ACD-BLOCK-PTR, ACD queue type and queue ID. Queue ID
corrected.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 78 of 2360
AUD0058
End pointer of ACD queue does not point to the last CR in the queue. Output:
Customer, U_ACD_BLOCK_PTR and ACD queue type.
Action:
Severity: Minor.
AUD0059
SNMP trap: Yes
Queue length in ACD queue block differs from number in queue. Output:
Customer, U_ACD_BLOCK_PTR and ACD queue type. Queue length
corrected.
Action:
Severity: Minor.
AUD0060
SNMP trap: Yes
ACD queue contains CR with pointer out of CR range. Output: Customer,

U_ACD_BLOCK_PTR, ACD queue type and CR link. ACD queue terminated
at this CR.
Action:
Severity: Minor.
AUD0061
SNMP trap: Yes
QUEUE-IN of CR in ACD queue is not ACD. Output: Customer,

U_ACD_BLOCK_PTR, ACD queue type and QUEUE_IN. QUEUE_IN
corrected.
Action:
Severity: Minor.
AUD0062
SNMP trap: Yes
CR in given ACD queue but AUXPM does not match. Output: Customer,
U_ACD_BLOCK_PTR, ACD queue type and CR information. AUXPM
corrected.
Action:
Severity: Minor.
AUD0063
SNMP trap: Yes
Invalid ACD AUXPM. Output: Customer, U_ACD_BLOCK_PTR, ACD queue

type and CR information. CR idled.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 79 of 2360
AUD0064
ACD CR has son CR but it is not a RAN CR. Output: CR information for son
CR and father CR. Son CR is idled.
Action:
Severity: Minor.
AUD0065
SNMP trap: Yes
DNTRANS for ACD Call Register failed. Unable to find correct queue. Output:
CR info, DIGIT_WORDS 0 . CR idled.
Action:
Severity: Minor.
AUD0066
SNMP trap: Yes
Nil pointer returned from DNTRANS for ACD CR. Unable to find correct queue.
Output: CR info, DIGIT_WORDS 0 .
Action:
Severity: Minor.
AUD0067
SNMP trap: Yes
CR found in main ACD queue. Output: CR information. Call Register is idled.

Action:
Severity: Minor.
AUD0068
SNMP trap: Yes
ACD block linkage broken. Output: Customer and ACD index.

Action:
Severity: Minor.
AUD0069
SNMP trap: Yes
ACD CR not in correct queue. Output: CR information. CR linked into queue

according to the AUXPM.
Action:
Severity: Minor.
AUD0070
SNMP trap: Yes
CR found with MAINPM_SPECIAL while process is ACD_RAN_PROCESS.

Output: CR information. CR idled.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 80 of 2360
AUD0071
CR found with MAINPM_SPECIAL and invalid process. Output: CR

information. CR idled.
Action:
Severity: Minor.
AUD0072
SNMP trap: Yes
Attendant terminal in CR has no pointer to this CR. CR was being used for
special function. Output: CR information. CR idled.
Action:
Severity: Minor.
AUD0073
SNMP trap: Yes
Digit display CR with MAINPM_SPECIAL but not in 2 s queue. Output: CR

information. CR idled.
Action:
Severity: Minor.
AUD0074
SNMP trap: Yes
TTR attached when no TTR should be present. Output: CR information and

TTR-TN. TTR is idled.
Action:
Severity: Minor.
AUD0075
SNMP trap: Yes
Trunk detected in half-disconnect state but no timing is active on the

CR.Output: CR information, Trunk TN and TRUNKPM. Release message sent
to trunk, active CR set to nil, TN in CR cleared.
Action:
Severity: Minor.
AUD0076
SNMP trap: Yes
Music trunk has a bad Call Register in active CR. Output: CR information. The
active CR is cleared.
Action:
Severity: Minor.
AUD0077
SNMP trap: Yes
Music CALLREG has a bad conference TN. Output: CR information. The Call
Register is idled.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 81 of 2360
AUD0078
Music CALLREG has a bad AUXPM. Output: CR information. The Call

Register is idled.
Action:
Severity: Minor.
AUD0079
SNMP trap: Yes
Music on hold has improper CALLREG. Output: CR Information. The Call

Register is idled.
Action:
Severity: Minor.
AUD0080
SNMP trap: Yes
Music dialed connection has improper CALLREG. Output: CR information.

The Call Register is idled.
Action:
Severity: Minor.
AUD0081
SNMP trap: Yes
Music source has improper CALLREG. Output: CR information. The Call

Register is idled.
Action:
Severity: Minor.
AUD0082
SNMP trap: Yes
Message Call Register is not in the expected queue (.QU_AUX_HSOP or

.QU_AUX_HSIP). Output: Call Register information.
Action:
Severity: Minor.
AUD0083
SNMP trap: Yes
Wandering message Call Register. Output: Call Register information.

Action:
Severity: Minor.
AUD0084
SNMP trap: Yes
Call Register in cadence queue was found to contain no originating party. Any
ringing will be removed from the terminating party and the Call Register will be
idled.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 82 of 2360
AUD0085
CR in attendant queue has AUXCR not equal to RAN_RAN_PROCESS: CR

information and queue.
Action:
Severity: Minor.
AUD0086
SNMP trap: Yes
No wanted party call present for Break-In. Break-In bit in CONLOOP reset.
Output: CR Information.
Action:
Severity: Minor.
AUD0087
SNMP trap: Yes
No attendant-destination CR found for Break-In feature. Console restored to

state prior to Break-In. Output: CR Information.
Action:
Severity: Minor.
AUD0088
SNMP trap: Yes
Break-In CONLOOP reset.

Action:
Severity: Minor.
AUD0089
SNMP trap: Yes
Break-In indicated but no active attendant and loop. Console returned to state
prior to Break-In. Output: CR Information.
Action:
Severity: Minor.
AUD0091
SNMP trap: Yes
Audit has found that Zone bandwidth does not match actual usage. Zone
information has been updated to actual value.
Action:
Severity: Major.
AUD0092
SNMP trap: Yes
Procedure VTRK_OBT_AUDIT: ACTIVECR field in the unprotected virtual

trunk block is nil, but a TDS is allocatd for the out-of-band tone. The tone is
removed.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 83 of 2360
AUD0093
PTN associated with an IDLE VTN removed

Action:
Severity: Info.
AUD0094 x y z
SNMP trap: Yes
Loop with no physical timeslots is marked with faulty timeslots. May cause
AUD0017 or AUD0018 Parameter 1 = loop Parameter 2 = TSEFAULTWORD
Parameter 3 = TSOFAULTWORD
Action:
Severity: Minor.
AUD0095
SNMP trap: Yes
Audit message for printing diagnostic information related to ISA MIN-MAX

Action:
Severity: Major.
AUD0096
SNMP trap: Yes
DWC; ACD Calls Waiting show very large numbers, related to CCR.
Action:
Severity: Minor.
AUD0098
SNMP trap: Yes
The CR has not been unlinked from the BFS key on BSC after the call was
gone from boss or secretary (BSFE feature).
Action: Report to your technical support group.
Severity: Minor.
AUD0099
SNMP trap: Yes
Invalid MAINPM. Output: CR information. CR is idled.

Action:
Severity: Minor.
AUD0100
SNMP trap: Yes
Audit indicates that a conference slot is not in use but it is marked as busy or
vice versa. The conference slot is marked in accordance with its real state.
Output: Conference loop, an old and a new value of the conference slots map.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 84 of 2360
AUD0101
Message CR is not in range. The message CR is not idle. Output: %

<DCH_ID> <INDEX_NUM> <MSGCR>
Action: Contact your technical support.
Severity: Minor.
AUD0102
SNMP trap: Yes
CLI CR has not been released at the end of the call.

Severity: Minor.
AUD0199
SNMP trap: Yes
Incorrect CRPTR.
Severity: Minor.
AUD0200
SNMP trap: Yes
Invalid ORIGTN in Group Call (except conference circuit.) Warning message.

CR information is output.
Action:
Severity: Minor.
AUD0201
SNMP trap: Yes
No Group Call customer data. Idle CR information and customer number are
output.
Action:
Severity: Minor.
AUD0202
SNMP trap: Yes
No unprotected Group Call data. Warning message. Customer number and

group number are output.
Action:
Severity: Minor.
AUD0203
SNMP trap: Yes
CR has no pointer to Group Call data. Set GRP_ULPTR in CR. CR

information, new ULPTR and old ULPTR are output.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 85 of 2360
AUD0204
CR number does not match GRP_CALL_CRPTR position.

Action: Set new CR_NO. CR information, new CR_NO, old CR_NO are output.
Severity: Minor.
AUD0205
SNMP trap: Yes
Group Call ORIG_BIT has incorrect information.

Action: Set GRP_ORIG bit in CR. CR information is output.
Severity: Minor.
AUD0206
SNMP trap: Yes
Group Call busy bit not set.

Action: Reset busy bit only in ORIG call. CR information is output.
Severity: Minor.
AUD0207
SNMP trap: Yes
Cannot find group data pointer in CR.

Action: Reset Group Call data in CR. CR information, OLD_ULPTR are output.
Severity: Minor.
SNMP trap: Yes
AUD0208
Action: Reset Group Call data in CR. CR information is output.
Severity: Minor.
SNMP trap: Yes
AUD0209
Action: Reset one group member in Group Call. Reset group data I CR and
member data. CR information and member number are output.
Severity: Minor.
AUD0211
SNMP trap: Yes
AUXCR of NFCR process not in CR range.

Action:
Severity: Minor.
AUD0212
SNMP trap: Yes
Invalid main PM for NFCR process.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 86 of 2360
AUD0213
A Ring Again call is in the TOF queue.

Action:
Severity: Minor.
AUD0214
SNMP trap: Yes
ORIG timer type is invalid and has been corrected as indicated: CRPTR
CRWORD(0) BLOCKTYPE CURRENT_TYPE SHOULD_BE_TYPE or
TIMING_BLK_PTR TN BLOCKTYPE CURRENT_TYPE
SHOULD_BE_TYPE.
Action:
Severity: Minor.
AUD0300
SNMP trap: Yes
SNMP trap: Yes
Invalid son type.

Action:
Severity: Minor.
AUD0301
Signaling son register with invalid main PM in the Call Register.

Action:
Severity: Minor.
AUD0302
SNMP trap: Yes
Invalid testline type or index in CR.

Action:
Severity: Minor.
AUD0303
SNMP trap: Yes
CR not in customer data block.

Action:
Severity: Minor.
AUD0304
SNMP trap: Yes
Invalid testline PM in CR.

Action:
Severity: Minor.
AUD0305
SNMP trap: Yes
Invalid state type combination.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 87 of 2360
AUD0306
Invalid TN type for testline call.

Action:
Severity: Minor.
AUD0307
SNMP trap: Yes
TN's active CR does not point to CR.

Action:
Severity: Minor.
AUD0308
SNMP trap: Yes
DLI Channel was idled as a result of the network map Audit TERMINAL TN,
GROUP/LOOP, DLI_CHANNEL (1-24)
Action:
Severity: Minor.
AUD0309
SNMP trap: Yes
DLI Channel used for CSL was found idle. Channel is forced to BUSY status.
GROUP/LOOP
Action:
Severity: Minor.
AUD0310
SNMP trap: Yes
DLI Channel with DISABLED or MAINTENANCE-BUSY status was found idle.

Channel is forced to BUSY status. GROUP/LOOP, DLI CHANNEL (1-24)
Action:
Severity: Minor.
AUD0311
SNMP trap: Yes
DLI Channel assignment data is inconsistent. Channel found BUSY is forced

to IDLE status. GROUP/LOOP, DLI CHANNEL (1-24)
Action:
Severity: Minor.
AUD0312
SNMP trap: Yes
Assigned DLI Channel was found idle. Channel is forced to BUSY status.
TERMINAL TN, GROUP/LOOP, DLI_CHANNEL (1-24)
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 88 of 2360
AUD0313
Invalid screen state on M3000 TOUCHPHONE in dialtone queue. The valid

state is DIALTONE state or CONFERENCE/TRANSFER/DIALTONE state.
TERMINAL TN, QU_IN, TSET STATE, CRPTR, ORG TN, ORG TYPE,
TERTN, TERTYPE
Action:
Severity: Minor.
AUD0314
SNMP trap: Yes
Invalid screen state on M3000 TOUCHPHONE in ringing queue when transfer

indication is set. The valid state is TRANSFER RINGBACK or CONFERENCE
RINGBACK state. TERMINAL TN, QU_IN, TSET STATE, CRPTR, ORG TN,
ORG TYPE, TERTN, TERTYPE
Action:
Severity: Minor.
AUD0315
SNMP trap: Yes
Invalid screen state on M3000 TOUCHPHONE in ringing queue when transfer

indication is not set. The valid state is RINGBACK state. TERMINAL TN,
QU_IN, TSET STATE, CRPTR, ORG TN, ORG TYPE, TERTN, TERTYPE.
This applicable on all phases.
Action:
Severity: Minor.
AUD0316
SNMP trap: Yes
DLI channel was still assigned to a station after the channel was either idled
or reassigned. The assignment was cleared. BCS station TN, group/loop, DLI
channel number (1-24).
Action:
Severity: Minor.
AUD0317
SNMP trap: Yes
A BCS station has an out-of-range channel assignment (greater than 24)

probably due to data corruption of the unprotected BCS unit block. The
assignment was cleared. BCS station TN, group/loop, DLI channel number
(1-24).
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 89 of 2360
AUD0318 DATA
Target TOF queue pointers to source TOF queue are incorrect. Error has been
corrected. Output data: Customer number, target and source ACD-DN.
Action:
Severity: Minor.
AUD0319
SNMP trap: Yes
LLC BLKING or LLC BLKING VAL is corrupted.

Action:
Severity: Minor.
AUD0320
SNMP trap: Yes
Target ACD-DN already answering calls for the maximum amount of source
queues. Customer, Target ACD-DN, Source ACD-DN.
Action:
Severity: Minor.
AUD0321
SNMP trap: Yes
Cannot set ACD pointers for ORIGTN in the Idle Agent Queue.
Action: Take CR out of the Idle Agent Queue.
Severity: Minor.
AUD0322
SNMP trap: Yes
Although the priority is set in the Call Register, there is no pointer to the Priority
Agent Table in the Unprotected Data for the ACD data block.
Action: Clear the Agent Priority in the CR. {Priority in CR} {Agent's Priority}
{ACD-DN}
Severity: Minor.
AUD0323
SNMP trap: Yes
The Priority set in the Agent's block does not match the Priority in the Call
Register for the Idle Agent Queue. {CR Priority} {Agent Block Priority} {Cust
No} {ACD-DN}
Action:
Severity: Minor.
AUD0324
SNMP trap: Yes
The Priority Agent's Call Register is in queue, but the pointer for that priority in
the Priority Agent Table equals END_OF_QUEUE.
Action: Take the CR out of the Idle Agent Queue and put back in the proper
place. {Priority} {Customer No} {ACD-DN}
Severity: Minor.
SNMP trap: Yes
System Messages
Page 90 of 2360
AUD0325
The Priority Agent's CR is in queue, but the pointer for that priority in the
Priority Agent Table does not point to the last Call Register of that priority.
Action: Update the pointer in the priority agent table to point to the last CR of
that priority. {Priority} {Customer No} {ACD-DN}
Severity: Minor.
AUD0326
SNMP trap: Yes
Account Call Register found, but the package is not enabled. AUXPM OF
.ACD_ACNT_ENTRY, BUT .ACD_ACCT_PKG RESTRICTED *CRINFO.
Action: Darken ACNT lamp, idle CR and clear pointer in agent's block.
Severity: Minor.
AUD0327
SNMP trap: Yes
ORIGTN of Account CR is not an ACD AGENT. *CRINFO.

Action: Darken ACNT lamp, idle CR and clear point
Severity: Minor.
AUD0328
SNMP trap: Yes
Agent is not active on an ACD call. *CRINFO.

Action: Darken ACNT lamp, idle CR and clear pointer in agent's block.
Severity: Minor.
AUD0329
SNMP trap: Yes
Account Key is not allocated to ACD set corresponding to Account Call

Register. ORIGKEY in the ACNT CR is not an ACNT key. *CRINFO.
Action: Idle CR and clear pointer in agents block
Severity: Minor.
AUD0330
SNMP trap: Yes
Account key is found to be in an improper state. The ACNT key is dark, but
NO_ACT_CODE_ENT is .TRUE. *CRINFO.
Action: Clear the NO_ACT_CODE_ENT field in agent's block.
Severity: Minor.
AUD0331
SNMP trap: Yes
An FGD auxiliary Call Register is associated with an incoming FGDT trunk, but
the trunk does not recognize this Call Register as its auxiliary CR. The FGD
auxiliary CR is idled. Output data is AUX_FGD_CRINFO, FGD_TN,
FGD_AUX_CR (address of CR and FGD fields in the AUX Call Register).
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 91 of 2360
AUD0332 DATA
An FGD auxiliary Call Register is associated with a terminal that is not an

incoming FGDT trunk. The FGD auxiliary CR is idled. Output data is
AUX_FGD_CRINFO, FGD_TN, FGD_AUX_CR (address of CR and FGD
fields in the aux Call Register).
Action:
Severity: Minor.
AUD0334
SNMP trap: Yes
Call Register found in main APL output queue. Call Register is idled. APL_NO,
LINK_NO:CRPTR, CRWORD 0 - 3, *IMS_MSG
Action:
Severity: Minor.
AUD0335
SNMP trap: Yes
An APL Call Register is floating around. Call Register is idled. APL_NO,

LINK_NO:CRPTR, CRWORD 0 - 3, *IMS_MSG
Action:
Severity: Minor.
AUD0336
SNMP trap: Yes
QUEUE_ID of Call Register in APL output queue is not APL. QUEUE_ID is

corrected. APL_NO, QUEUE_ID
Action:
Severity: Minor.
AUD0337
SNMP trap: Yes
The end pointer in APL output queue is not pointed to the last element in the
queue. END_PTR is reset to point to the last element in the queue. APL_NO,
LINK_NO:ENDPTR, CRWORD[0 -3], *IMS_MSG
Action:
Severity: Minor.
AUD0338
SNMP trap: Yes
Queue length in APL queue block differs from number in queue. Queue length
corrected. APL_NO, LINK_NO:ENDPTR, CRWORD[0 -3], *IMS_MSG.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 92 of 2360
AUD0339
Queue contains CR with pointer outside of CR range. The queue is terminated

at the previous block. APL_NO, LINK_NO:PROCESSINGPTR, CRWORD[0
-3], IMS_MSG.
Action:
Severity: Minor.
AUD0340
SNMP trap: Yes
QUEUE_IN of APL CR is not APL. Reset QUEUE_IN to APL queue id.

APL_NO, LINK_NO:PROCESSINGPTR, CRWORD[0 -3], *IMS_MSG.
Action:
Severity: Minor.
AUD0341
SNMP trap: Yes
For empty queue, processing pointer is not equal to END_OF_QUEUE.

Action: Reset processing pointer to END_OF_QUEUE. APL_NO,
PROCESSINGPTR, QUEUE_PTR.
Severity: Minor.
AUD0342
SNMP trap: Yes
For empty queue, end pointer is not pointing back to queue data block.
Action: Reset end pointer to END_OF_QUEUE. APL_NO, ENDPTR,
QUEUE_PTR.
Severity: Minor.
AUD0354
SNMP trap: Yes
Status update PM out-of-range.

Action:
Severity: Minor.
AUD0355
SNMP trap: Yes
No ACD CR is associated with the main CR for telset messaging CR.

*CRINFO
Action:
Severity: Minor.
AUD0360
SNMP trap: Yes
LINK_Q_HDR is NIL (IMS package restricted), but APL port is configured.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 93 of 2360
AUD0367
No father Call Register linked to parked son CR. *CRINFO, PARKPM, CALL
PARK ACCESS ID, PARKING PARTY TN, RECALL_ATTN_INDEX Son CR
is idled.
Action:
Severity: Minor.
AUD0368
SNMP trap: Yes
No son register linked to parked father CR. Son CR is idled. *CRINFO

Action:
Severity: Minor.
AUD0370
SNMP trap: Yes
Data base of Server {VAS ID} cannot be audited. The Command and Status
Link to the Server is disabled. {VAS ID} Note: parameters in decimal.
Action:
Severity: Minor.
AUD0371
SNMP trap: Yes
Data base audit of Server {VAS ID} is stopped due to error when sending
AUDIT CSL message on SL-1. {data element id} identifies the data element
being audited when the message was sent. {VAS ID} {cust no} {data element
id} Note: parameters in decimal.
Action:
Severity: Minor.
AUD0372
SNMP trap: Yes
Data base audit of Server {VAS ID} is stopped when auditing given data
element. There was no response from the Server to the SL-1 audit CSL
messages. {VAS ID} {cust no} {data element id} Note: parameters in decimal.
Action:
Severity: Minor.
AUD0373
SNMP trap: Yes
Data base audit of Server {VAS ID} is stopped by the Server audit program.
{VAS ID} {cust no} Note: parameters in decimal.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 94 of 2360
AUD0374
Error in the Server {VAS ID}'s data base for the given SL-1 administered data
element was detected. The data has been added or modified. {VAS ID} {cust
no} {data element id} Note: parameters in decimal.
Action:
Severity: Minor.
AUD0375
SNMP trap: Yes
Server {VAS ID} audit removed given SL-1 administered data element from
the Server's data base. The data element does not exist in the SL-1 data base.
{VAS ID} {cust no} {data element id} Note: parameters in decimal.
Action:
Severity: Minor.
AUD0376
SNMP trap: Yes
Error has been detected in the SL-1 data base for the given Server
administered data element. The data has been added or modified. {VAS ID}
{cust no} {data element id} Note: parameters in decimal.
Action:
Severity: Minor.
AUD0377
SNMP trap: Yes
SL-1 audit removed given Server administered data element from the SL-1
data base. The data does not exist in Server {VAS ID}'s data base. {VAS ID}
{cust no} {data element id} Note: parameters in decimal.
Action:
Severity: Minor.
AUD0378
SNMP trap: Yes
Data base audit of Server {VAS ID} is stopped because there were not enough
Call Registers available. {VAS ID} Note: parameters in decimal.
Action:
Severity: Minor.
AUD0379
SNMP trap: Yes
ADDON_LINK of addon in the idle queue is not within the valid add-on range.
The queue will be ended at the last valid addon. (Generic X08). LAST
ELEMENT, ADDON_LINK, QUEUE
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 95 of 2360
AUD0380
HEAD_PTR of the idle addon queue is out of valid addon range. The queue
will be treated as an empty queue (X08). QUEUE_BLOCK_PTR, HEAD_PTR,
CR_ADDON_START, CR_ADDON_ENQUEUE.
Action:
Severity: Minor.
AUD0381
SNMP trap: Yes
Call Reference # does not match in U_CREF_TAB. Call Register being

audited was pointing to an addon that was either in the idle queue or was not
pointing back to this Call Register.
Action:
Severity: Minor.
AUD0382
SNMP trap: Yes
Call Reference number does not match in BRIT_U_CREF. Call Register being
audited was using an invalid call reference.
Action:
Severity: Info.
AUD0383
SNMP trap: Yes
Invalid PRA message Call Register is ideled because the Dchannel/DSL

pointers of the PRA msgcr cannot be set.
Action:
Severity: Info.
AUD0389
SNMP trap: Yes
The Agent's CR is not ordered correctly according to its priority in the Idle
Agent Queue.
Action: Take the CR out of the Idle Agent Queue and put it back in the proper
order. {Priority} {Customer No.} {ACD-DN}
Severity: Minor.
AUD0390
SNMP trap: Yes
Data base mismatch has been detected in Server {VAS ID}'s data base for the
given SL-1 administered data element. The error cannot be repaired by Audit.
Action: The craftsperson should load the appropriate overlay program and
remove the data. {VAS ID} {cust no} {data element id} Note: parameters in
decimal.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 96 of 2360
AUD0391
Data base mismatch has been detected in the SL-1's data base for the given
Server {VAS ID} administered data element. The error cannot be repaired by
Audit.
Action: The craftsperson should use the appropriate server administration
program to remove the data. {VAS ID} {cust no} {data element id} Note:
parameters in decimal.
Severity: Minor.
AUD0392
SNMP trap: Yes
MSG CRin the UNP. Trunk block is nil, but active CR is not nil.
Action:
Severity: Minor.
AUD0393
SNMP trap: Yes
MSG CR in the UNP. Trunk block is not nil, but active CR is nil.
Action:
Severity: Minor.
AUD0395
SNMP trap: Yes
MSG CR & active CR in the UNP. Trunk block is not nil, but MSG CR in the
call reference table is nil.
Action:
Severity: Minor.
AUD0396
SNMP trap: Yes
MSG CR in the call reference table is nil, but U_CALL_REF_# is not zero.
Action:
Severity: Minor.
AUD0398
SNMP trap: Yes
TNTRANS failed when MSG_CR = NIL.

Action:
Severity: Minor.
AUD0399
SNMP trap: Yes
MSG_CR = NIL, but active CR = NIL.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 97 of 2360
AUD0400
CREF_MSG_CR = NIL & C_CALL_REF = 0.

Action: Run Audit again. You may need to run Audit several times until
AUD0400 no longer appears.
Severity: Minor.
AUD0418
SNMP trap: Yes
CMF_TN of active CMF S/R not correct. CMF_TN set to terminal.

Action:
Severity: Minor.
AUD0419
SNMP trap: Yes
MFE_TN of active MFE S/R not correct. MFE_TN set to terminal.

Action:
Severity: Minor.
SNMP trap: Yes
AUD0422 A B C D E F G H I A call with MAINPM = .REORDER was found not to be receiving nor
waiting for overflow tone. Overflow tone will be given. Where: a = CR Addr
MAINPM/AUXPM
b = Originating Type
c = Originating TN, d = Terminating Type
e = Terminating TN f = QUEUE IN g = CR Dialed DN h = Digit Words (0) i =
Queue Type
Action:
Severity: Minor.
AUD0423
SNMP trap: Yes
AUDIT has detected an inconsistent DPNSS1 MWI table.

Action: The AUDIT program resets the inconsistent information.
Severity: Major.
AUD0442
SNMP trap: Yes
A Call Register with non-nil CRLINK does not have a QUEUE_ID. CRLINK has
been set to NIL - CRINFO, CRLINK.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 98 of 2360
AUD0502
Invalid MAINPM for CR with son CR for periodic Camp-On tone. CR

information and MAINPM are output.
Action:
Severity: Minor.
AUD0503
SNMP trap: Yes
No father CR is linked to the son CR. Call Register (CR) information is output,
the son CR is idled.
Action:
Severity: Minor.
AUD0504
SNMP trap: Yes
Invalid MAINPM for son CR periodic Camp-On tone. Call Register (CR)
information and MAINPM are output.
Action:
Severity: Minor.
AUD0507 TN DN
SNMP trap: Yes
A DID number is wrongly associated with the set for (Hospitality

Management). TN of set and DID number are printed DID number is cleared.
Action:
Severity: Minor.
SNMP trap: Yes
AUD0515 X Y TN1 TN2 Slot y on Loop x has been reserved as a non-reusable slot for tn1, but can
still be used on tn2. Procedure DTI_SLOT_AUD
Action:
Severity: Minor.
AUD0516 Y R
SNMP trap: Yes
Slot y is on a loop is reusable, but has a non-zero RESERV_COUNT value

against it in the U_SLOT_SHARE_BLK. Procedure CHK_RESERV_COUNT.
R = Reserve Count
Action:
Severity: Minor.
AUD0517
SNMP trap: Yes
BKI_SECRECY_BIT. The Break-In with Secrecy (BKIS) bit is set while BKIS
is not active. The BKIS bit is cleared.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 99 of 2360
AUD0518
Less than 10 percent of the XMI message registers are in the idle queue.
Action:
Severity: Minor.
AUD0519 i c l
SNMP trap: Yes
A count of the XMI message registers having queue ID "I" do not match the
field length for that queue's data block. i = queue ID, c = Count for message
register, l = Length from the queue data block.
Action:
Severity: Minor.
AUD0520 i c
SNMP trap: Yes
The set pointers have failed for Virtual Network Services (VNS). i = VNS Index,
c = Customer number.
Action:
Severity: Minor.
AUD0521 i c p a
SNMP trap: Yes
The CR pointer does not match the Virtual Network Services (VNS) Active CR.
i = VNS Index, c = Customer number, p = CR Pointer, a = Active CR for VNS.
Action:
Severity: Minor.
AUD0522 i c m a
SNMP trap: Yes
In the Virtual Network Service application, there exists a VNS Index mismatch
or Invalid call state. i = VNS Index, c = Customer number, m = Message CR,
a = Active CR for VNS
Action:
Severity: Minor.
AUD0523
SNMP trap: Yes
Invalid MAINPM for RADIO PAGING process. *CRINFO

Action:
Severity: Minor.
AUD0524
SNMP trap: Yes
Unable to locate son CR when father CR indicates an RPA_PROCESS son

type. *CRINFO
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 100 of 2360

AUD0525
Invalid main PM for RPA son CR. Main PM for the Radio Paging son should
be Radio Page. *RPA_SON_INFO
Action:
Severity: Minor.
AUD0526
SNMP trap: Yes
RPA state error. If RPA CALL bit is set, then RPA ANSWER cannot be set and
vice versa. *CRINFO (Father)
Action:
Severity: Minor.
AUD0527
SNMP trap: Yes
Son CR found when RPA call has been answered. *FATHER_SON_INFO

Action:
Severity: Minor.
AUD0528
SNMP trap: Yes
RPA CALL bit is not set when father has an RPA Process son type.
*FATHER_SON_INFO
Action:
Severity: Minor.
AUD0529
SNMP trap: Yes
Father and RPA son do not have the same ORIGTNs. *FATHER_SON_INFO,
ORIGTN of SON CR
Action:
Severity: Minor.
AUD0530
SNMP trap: Yes
RPA father CR has trunk still attached while undergoing meet-me or recall
timing. *RPA_SON_INFO
Action:
Severity: Minor.
AUD0531
SNMP trap: Yes
The RPA son is not in the meet-me queue as expected. *RPA_SON_INFO

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 101 of 2360

AUD0532
The trunk is not a Radio Paging trunk. *FATHER_SON_INFO,

RPA_CR_ROUTE_NUM in Son CR
Action:
Severity: Minor.
AUD0533
SNMP trap: Yes
Main PM should only go to ringing when the RPA trunk is dropped.

*RPA_SON_INFO, PROCESS_TYPE of RPA SON CR
Action:
Severity: Minor.
AUD0534
SNMP trap: Yes
Invalid AUXPM for Single System RPA. AUXPM of RPA accessing is valid
only for multisystem RPA configurations. *CRINFO
Action:
Severity: Minor.
AUD0535
SNMP trap: Yes
Invalid AUXPM for RPA son when AUXPM of father CR is RPA accessing.
*father_son_info
Action:
Severity: Minor.
AUD0536
SNMP trap: Yes
RPA process son type expected when AUXPM of Main CR is RPA accessing.
*CRINFO (Father)
Action:
Severity: Minor.
AUD0537
SNMP trap: Yes
Invalid AUXPM for RPA package unequipped. *CRINFO (Father)

Action:
Severity: Minor.
AUD0538
SNMP trap: Yes
Unable to find the father CR for this RPA son CR. *rpa_son_info
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 102 of 2360

AUD0539
Invalid Main PM when RPA package is not equipped. *rpa_son_info

Action:
Severity: Minor.
AUD0540
SNMP trap: Yes
Son CR is not in the Meet-Me queue as expected. *rpa_son_info

Action:
Severity: Minor.
AUD0541
SNMP trap: Yes
TERTN of Father CR should be an RPA trunk. *Father_Son_Info

Action:
Severity: Minor.
AUD0542
SNMP trap: Yes
RPA son type is invalid for RPA_Answer state. *crinfo

Action:
Severity: Minor.
AUD0543
SNMP trap: Yes
TNtrans of the TERTN in Father CR failed. *crinfo

Action:
Severity: Minor.
AUD0544
SNMP trap: Yes
RPA system PTR is nil. *Father_Son_Info

Action:
Severity: Minor.
AUD0545
SNMP trap: Yes
SETCUSTPTRS failed. Unable to find customer pointers. *crinfo

Action:
Severity: Minor.
AUD0546
SNMP trap: Yes
No RPA son type indicated in the Father CR. *crinfo

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 103 of 2360

AUD0547
SET ROUTE PTRS failed. Invalid route associated with the TERTN. *crinfo
Action:
Severity: Minor.
AUD0548
SNMP trap: Yes
No ACD CR is associated with the MAIN CR for CCR process.

Action:
Severity: Minor.
AUD0549
SNMP trap: Yes
Process type must be ICP_PROCESS (CCR).

Action:
Severity: Minor.
AUD0550
SNMP trap: Yes
SNMP trap: Yes
DN type is not a CDN.

Action:
Severity: Minor.
AUD0551
DN type is not an ACD DN.

Action:
Severity: Minor.
AUD0552
SNMP trap: Yes
CCR restoration timeslice Call Register does not point to the call to be
restored.
Action:
Severity: Minor.
AUD0553
SNMP trap: Yes
The timeslice Call Register is not in the two second queue.

Action:
Severity: Minor.
AUD0554
SNMP trap: Yes
Mainpm of ICP call which is presented to an agent should be .RINGING.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 104 of 2360

AUD0555
ICP SON does not have a father CR.

Action:
Severity: Minor.
AUD0557 DATA
SNMP trap: Yes
Message CR does not match linkage in message CR table. Output data:

Address of the message CR TN in the message CR Call reference number in
the message CR
Linkage in message CR table
TN in the message CR linked from CR table
Call reference number in the message CR linked from CR table
Action:
Severity: Minor.
AUD0558 DATA
SNMP trap: Yes
B-channel packet data nail up connection between DSL B-channel and Packet
Handler is broken. The DSL B-channel TN is output with the following error
code and additional data:
1 = No Call Register for nail up connection
2 = TNTRANS on PRI channel TN failed. PRI Channel TN is also output
3 = Invalid PRI loop type. PRI channel TN is also output
4 = PRI channel is not dedicated for the connection. Channel TN is also output
5 = Incorrect TRUNK PM. PRI channel TN is also output
6 = Invalid Call Register contents. Address of the Call Register, types of both
originating and terminating parties, type of call and MAIN PM are also output.
Action:
Severity: Minor.
AUD0559 DATA
SNMP trap: Yes
Invalid information transfer capability (BCAP). Output data: TN, call reference
number and the BCAP value stored in the message CR.
Action:
Severity: Minor.
AUD0560
553-3001-411
SNMP trap: Yes
Inconsistent message CR and CR linkages. Output data: DSL TN, call

reference number and the following error code:000001 = CR is missing and
usage bit is not set. Message CR will be discarded 000002 = Message CR is
missing and usage bit is not set. CR will be discarded
000005 = CR is missing. Message CR will be discarded and usage bit is
cleared
000006 = Message CR is missing. CR will be discarded and usage bit is
cleared. For 000001 and 000005, the call reference number and the cause
Standard 15.00
January 2006
Page 105 of 2360

value in the message CR are output. For 000002 and 000006, the AUX &
MAIN PMs, the originating and terminating parties' TNs and the dialed DN (in
Hex) in the CR are output.
Action:
Severity: Minor.
AUD0561 DATA
SNMP trap: Yes
Incorrect number of VCE/DTA calls. The number of calls stored is updated

with the number of calls counted. Output data: DSL TN, type, number of calls
counted and number of calls stored.
Action:
Severity: Minor.
AUD0562 TN
SNMP trap: Yes
No DSL data. The TN is output.

Action:
Severity: Minor.
AUD0563
SNMP trap: Yes
The CCR_IVR_CR pointer in the CCR main Call Register does not point to its
CCR IVR Call Register. The pointer will be set to point to the CCR IVR Call
Register like it should. Procedure TERMCRPTR.
Action:
Severity: Minor.
AUD0564
SNMP trap: Yes
The main Call Register for a CCR IVR call connected to an IVR port is not in
its CDN like it should be. Procedure TERMCRPTR.
Action:
Severity: Minor.
AUD0565
SNMP trap: Yes
M911 aux cr in the trunk block is not the same as the cr being audited.
Severity: Minor.
AUD0566
SNMP trap: Yes
TN in aux cr is not an M911 trunk.

Severity: Minor.
SNMP trap: Yes
System Messages
Page 106 of 2360

AUD0570
The B CH link for printed {DCHNO} is blocked for outgoing calls

(DCH_OTG_BUSY is set) and no outgoing call is active on the BCH link. Link
is unblocked.
Action:
Severity: Minor.
SNMP trap: Yes
AUD0571 Q QPTR I N H This XMI queue's data block is corrupted. q = queue being audited qptr
= pointer to queue data block
If QPTR is not NIL, the following fields are printed from the queue data block:
i = queue ID from queue data block n = queue length from queue data block
hptr = pointer to head of queue eptr = pointer to end of queue
Action:
Severity: Minor.
SNMP trap: Yes
AUD0572 Q I MPTR MLN This XMI message register has an invalid queue ID or link pointer. q =
queue being audited, i = message register's queue ID, mptr = message
register pointer, mlnk = link to next message register in queue.
Action:
Severity: Minor.
AUD0573 Q
SNMP trap: Yes
This XMI queue is corrupted. q = queue being audited

Action:
Severity: Minor.
AUD0574 I MPTR
SNMP trap: Yes
This XMI message register has an invalid queue ID.i = message register's
queue ID, mptr = message register pointer.
Action:
Severity: Minor.
AUD0575
SNMP trap: Yes
TCAP CR is in invalid state; it will be idled.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 107 of 2360

AUD0576 DATA
Call ID in CR does not match Call ID entry in internal table. Internal Table entry
cleared. Output data appears as follows. {Call ID} {CUST} {CR} {MAIN & AUX
PMs} {ORIGTYPE/TERTYPE} {ORIGTN} {TERTN} {QUEUE_IN}
{CR_DIALLED_DN} {DIGITLOAD} {DIGITS...}
Action:
Severity: Minor.
AUD0577
SNMP trap: Yes
Call ID in Call Register does not have associated pointer in Call ID Table. Call
ID field in CR set to zero. Output data appears as follows: {Call ID} {CUST}
{CR} {MAIN & AUX PMs} {ORIGTYPE/TERTYPE} {ORIGTN} {TERTN}
{QUEUE_IN} {CR_DIALLED_DN} {DIGITLOAD} {DIGITS...}
Action:
Severity: Minor.
AUD0578
SNMP trap: Yes
Table entry references CR with out of range Call ID. Call ID in CR set to zero
and internal Table entry cleared. Output data appears as follows: {Call ID}
{CUST} {CR} {MAIN & AUX PMs} {ORIGTYPE/TERTYPE} {ORIGTN}
{TERTN} {QUEUE_IN} {CR_DIALLED_DN} {DIGITLOAD} {DIGITS...}
Action:
Severity: Minor.
AUD0579
SNMP trap: Yes
Internal Call ID Table entry references conference block which does not
contain expected Call ID value. Internal Table entry cleared. Output data
appears as follows. {U_CONF_PTR} {Call ID}
Action:
Severity: Minor.
AUD0580
SNMP trap: Yes
No conference exists for Call ID value in conference block. Associated entry

in internal Call ID Table is cleared, as well as Call ID field in conf blk. Output
data appears as follows:{U_CONF_PTR} {Call ID} {Conf Group}
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 108 of 2360

AUD0581
Out of range Call ID associated with {Conf Group} found in conference block.
Call ID field in conference block set to zero. Output data appears as follows:
{U_CONF_PTR} {Call ID} {Conf Group}
Action:
Severity: Minor.
AUD0582
SNMP trap: Yes
Call ID in conference block associated with {Conf Group} does not have
associated pointer in Call ID Table. Call ID field in conference block set to zero.
Output data appears as follows: {U_CONF_PTR} {Call ID} {Conf Group}
Action:
Severity: Minor.
AUD0583
SNMP trap: Yes
The nail up of tandem connection is not correct. Recovery is performed.

Output appears as follows: {error number} {incoming PRI TN} {outgoing PRI
TN} Error numbers: 1 = no Call Register for the dedicated connection 3 =
invalid PRI loop type, 4 = PRI TN is not configured for tandem connection 5 =
incorrect trunk pm 6 = invalid content at Call Register (content is printed) 8 =
PRI TN does not match what is stored in the Call Register
Action:
Severity: Minor.
AUD0587
SNMP trap: Yes
MF S/R pointing to CR which does not contain its TN. Active Call Register of
MF S/R set to nil. TN, CDR information, and progress mark are output.
Action:
Severity: Minor.
AUD0588
SNMP trap: No
MFK TN of active MFK S/R not correct. MFK TN set to terminal.

Action:
Severity: Minor.
AUD0589
SNMP trap: No
Procedure AUDIT_DPNSS_ISDN: TNTRANS failed on DPNSS_TN field of

the DPNSS ISDN CR. This Call Register is idled.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 109 of 2360

AUD0590
Procedure AUDIT_DPNSS_ISDN: DPNSS_TN field of the DPNSS ISDN CR

does not correspond to a trunk. This Call Register is idled.
Action:
Severity: Minor.
AUD0591
SNMP trap: Yes

does not correspond to a DPNSS trunk. This Call Register is idled.
Action:
Severity: Minor.
AUD0592
SNMP trap: Yes

is not correctly linked to the unprotected DPNSS channel block. This Call
Register is idled.
Action:
Severity: Minor.
AUD0593
SNMP trap: Yes
Procedure AUDIT_DPNSS_ISDN: ACTIVECR field of the unprotected

DPNSS channel block is nil. This Call Register is idled.
Action:
Severity: Minor.
SNMP trap: Yes
AUD0598 {ORIGTN} {Login TN} TN is registered as logged into Set Based Administration but its
active CR does not have an SBA process, the login session and its resources
are released.
Action:
Severity: Minor.
AUD0599 TN
SNMP trap: Yes
TN is registered as logged into Set Based Administration but its active CR

does not have an SBA process, the login session and its resources are
released.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 110 of 2360

AUD0600 {TN} {MAINPM} {AUXPM} TN is registered as logged into Set Based Administration
but its MAINPM and AUXPM do not contain valid values. They should be:
MAINPM = DIALING and AUXPM = SBA_DIALING or MAINPM = SPECIAL
and AUXPM = SBA_TIMEOUT
Action:
Severity: Minor.
SNMP trap: Yes
AUD0601 TN IDX1 IDX2 The session index being audited (idx1) contains TN as the logged in TN,
however, the SBA_SESSION_IDX field in the SBA son CR contains a different
session number (idx2). All resources associated with session (idx1) are
released from the multi-user login tables.
Action:
Severity: Minor.
AUD0602
SNMP trap: Yes
A TN or DN resource was found allocated to a Set Based Administration

session which is no longer logged in. The resource is released
Action:
Severity: Minor.
AUD0604
SNMP trap: Yes
Answered M911 Abandoned Calls cannot be .ESTABLISHED

Action:
Severity: Minor.
AUD0605
SNMP trap: Yes
Illegal AUXPM for M911 Abandoned Call...should be .M911_CAB

Action:
Severity: Minor.
AUD0606
SNMP trap: Yes
No SON CR for M911 Abandoned Call

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 111 of 2360

AUD0607
Unsuccessful check for an established EI conference: pointer AUXCR in

Ublock of the Orig channel does not match the identified Unwanted CR of the
EI conference.
Action: Force AUXCR the Unwanted CR.
Severity: Minor.
AUD0608
SNMP trap: Yes
Unsuccessful check for an established EI conference: pointer AUXCR in

Ublock of the Unwanted channel does not match the identified Orig CR of the
EI conference.
Action: Force AUXCR the Orig'sCR.
Severity: Minor.
AUD0609
SNMP trap: Yes
Unsuccessful check for an established EI conference: The SW could not

identify the EI Originating party.
Action: If possible, revert the EI conference back to the ordinary conference.
Clear EI flags and reserved slots if any.
Severity: Minor.
AUD0610
SNMP trap: Yes

identify the EI Wanted party.
Action: If possible, revert the EI conference back to an ordinary conference.
Severity: Minor.
AUD0611
SNMP trap: Yes

identify the EI Unwanted party.
Action: If possible, revert the EI conference back to an ordinary conference.
Severity: Minor.
AUD0617
SNMP trap: Yes
Illegal ORIGTYPE or ORIGTN info in answered M911 Abandoned Call

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 112 of 2360

AUD0618
The M911 AUX CR un protected trunk block should not point to aux CR for an
abandoned call.
Action:
Severity: Info.
AUD0619
SNMP trap: Yes
Unable to find the father CR for this L1MFC son CR. CRINFO is output. This
CR is idle.
Action:
Severity: Info.
SNMP trap: Yes
AUD0620 {tn} {priority} {acd dn} An MQA ACD agent was found to have an invalid Priority value
associated with an ACD DN. The priority was changed to equal the Priority
value in the PRI field in the set's Protected Line Block (use OVL 20 to print
TNB).
Action:
Severity: Minor.
SNMP trap: Yes
AUD0621 {tn} {acd dn} An MQA agent was found to have a DN in its MQA data block which is
not a valid ACD DN. The agent should log out immediately and log back in
specifying new ACD DNs.
Action:
Severity: Minor.
SNMP trap: Yes
AUD0622 {tn} {acd dn} An MQA ACD agent was found to be serving an ACD DN that is not
compatible with MQA. Specifically, one of the following prompts in OVL 23 is
set for the ACD DN: IVMS, DSAC, IVR, IMS, or the DN is a CDN. The agent
should log out immediately and log back in specifying new ACD DNs to serve.
Action:
Severity: Minor.
SNMP trap: Yes
AUD0623 cust route old_counter new_counter Actual number of idle trunks in route is different
than number in idle-trunk-counter in route block. Counter is corrected.
Action: If AUD0623 occurs frequently, contact your technical support group.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 113 of 2360

AUD0624
Busy ISPC link not associated to any end-user.

Action: Use overlays 60 and 80 to detect if any inconsistent connections exist.
If so, run AUDIT again. If the corruption still exists, then remove and reconfigure
the corrupted TNs.
Severity: Major.
AUD0625
SNMP trap: No
ISPC data structures corruption.

Action: Use overlays 60 and 80 to detect if any inconsistent connections exist.
If so, run AUDIT again. If the corruption still exists, then remove and reconfigure
the corrupted TNs.
Severity: Major.
AUD0626
SNMP trap: No
IDLE ISPC link associated to an end-user.

Action: Use overlays 60 and 80 to detect if any consistent connections exist. If
so, run AUDIT again. If the corruption still exists, then remove and reconfigure the
corrupted TNs.I
Severity: Info.
AUD0632
SNMP trap: No
The VDN data structure is corrupted. Some VDN blocks may be lost.
Action: AUDIT has restored the recoverable VDN blocks. VDN blocks which
have been lost must be recreated in LD 79.
Severity: Major.
AUD0633
SNMP trap: Yes
Tried to disconnect invalid TERTN of a DPNSS. Diversion validation call.

Severity: Minor.
AUD0634
SNMP trap: Yes
A Diversion Validation call was found in an improper state.

Severity: Minor.
AUD0642
SNMP trap: Yes
Invalid start on value is found from the acquired call register

Severity: Minor.
SNMP trap: Yes
System Messages
Page 114 of 2360

AUD0643
Invalid SFR feature is found from SFR call register.

Action: Contact your technical support group.
Severity: Info.
AUD0644
SNMP trap: Yes
Invalid Application VAS ID is found from an IAGT TN.

Severity: Major.
AUD0645
SNMP trap: Yes
P_IAGT_BLK is not allocated for an IAGT TN. IAGT TN is deacquired.

Severity: Major.
AUD0646
SNMP trap: Yes
IAGT_TERMINAL is updated due to mismatch with IAGT TN.

Severity: Major.
AUD0647
SNMP trap: Yes
IAGT TN (control login ACD agent) is not linked to IAGT link.

Severity: Major.
AUD0648
SNMP trap: Yes
Audit VAS ID is invalid.

Severity: Major.
AUD0649
SNMP trap: Yes
The last IAGT TN pointer of the IAGT link is not referenced to the last IAGT TN
from the IAGT link.
Action:
Severity: Major.
AUD0650
SNMP trap: Yes
The TITH Call Register does not match the RAN Route data.
Action: Report the problem is the condition persists.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 115 of 2360

AUD0651
The TITH CR is lost.

Action:
Severity: Minor.
AUD0652
SNMP trap: Yes
RAN Broadcast Timeslice Call Register is not in the 128ms queue.

Action:
Severity: Minor.
AUD0653
SNMP trap: Yes
The TITH Call Register is not in the 2S queue.

Action: Report the problem if the condition persists.
Severity: Minor.
AUD0654
SNMP trap: Yes
IAGT TN is linked to an IAGT link which is not matched with application VAS
ID.
Severity: Minor.
AUD0655
SNMP trap: Yes
Invalid attendant number in the priority buzz call register.

Action:
Severity: Major.
AUD0656
SNMP trap: Yes
Priority buzz call register should be linked to the unprotected attendant block.
Action:
Severity: Major.
AUD0657
SNMP trap: Yes
An Attendant Console can have only one priority buzz process call register
associated with it.
Action:
Severity: Major.
AUD0658
SNMP trap: Yes
Attendant cannot be maintenance busy or position busy when it has a priority

buzz call register associated with it.
Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 116 of 2360

AUD0659
Console type associated with priority buzz call register is not supported.
(Analog Console).
Action:
Severity: Major.
AUD0660
SNMP trap: Yes
The priority buzz call register should be in the 2 seconds timing queue.
Action:
Severity: Major.
AUD0661
SNMP trap: Yes
Broadcast trunk list was found to be broken and was subsequently rebuilt.
Severity: Minor.
AUD0662
SNMP trap: Yes
Broadcast speechpath counts were found to mismatch and were subsequently

realigned.
Severity: Minor.
AUD0663
SNMP trap: Yes
Tone Detector pointing to CR does not contain its terminal number. Active call
register set to nil. TN, CR information, progress mark and TDET_TN are
output.
Action:
Severity: Minor.
AUD0678
SNMP trap: Yes
CMON - Incorrect structure linkage on TER CCC Call Register.

Severity: Minor.
AUD0679
SNMP trap: No
CMON - Invalid value for the ORIG or TER CCC PM.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 117 of 2360

AUD0680
CMON - Monitoring structures still exist whereas monitored call is released.

Audit will release the CCC calls if they exist.
Severity: Minor.
AUD0681
SNMP trap: Yes
CMON - This CCC Call Register is not properly linked to its CM_DATA
structure. Audit will release the CCC call.
Severity: Minor.
AUD0682
SNMP trap: Yes
The CID(Call ID) Table is being audited.

Any incorrect entry in the CID table is rectified.
Severity: Minor.
AUD0683
SNMP trap: Yes
The number of IP sets counted on the Secondary Call Server differs from the
saved value; the first field contains the saved value and the second field
contains the counted value.
Action: No user action required. The saved value automatically adjusts to match
the actual count.
Severity: Minor.
AUD0684
SNMP trap: Yes
PRI table entry mismatch is found.

Severity: Minor.
AUD0685
SNMP trap: Yes
BRI table entry mismatch is found.

Severity: Minor.
AUD0686
SNMP trap: Yes
GF_UTILITY fails check and validate global values in C++ code.

Severity: Minor.
SNMP trap: Yes
System Messages
Page 118 of 2360

AUD0687
The number of IP sets counted on the Secondary Call Server differs from the
saved value. The first field contains the saved value and the second field
contains the counted value.
Action: Action: No user action required. The saved value automatically adjusts
to match the actual count.
Severity: Minor.
SNMP trap: No
AUD0700 xxxx yyyy Where xxxx = timeslot word and yyyy = junctor word. Mobility Audit is
checking the MISP/EIMC nail up connection. It detected a timeslot reserved
for an EIMC but the EIMC_TN is marked as .SLOT_NOT_USED.
Action: Disable the MISP and enable the MISP.
Severity: Minor.
AUD9056
SNMP trap: Yes
The audit has detected an inconsistency in the SS7 BLO/UBL timing

mechanism (for T12, T13, T14, T15, or T-08).
Action: Check that all the BLO.UBL messages have been sent and
acknowledged.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 119 of 2360
AUTH: Authorization Code (LD88)

The AUTH messages are generated while performing service change
procedures in the Authorization Code program (LD 88). The following are the
two types of authorization codes defined in LD 88:
BAUTbasic authorization codes
NAUTnetwork authorization codes
Messages
AUTH0000
Program Identifier
Action:
Severity: Minor.
AUTH0001
SNMP trap: No
Incorrect response to prompt request.

Action:
Severity: Info.
AUTH0002
SNMP trap: No
Service change password incorrect.

Action:
Severity: Info.
AUTH0003
SNMP trap: No
Customer data block does not exist.

Action:
Severity: Info.
AUTH0004
SNMP trap: No
Number entered is out-of-range.

Action:
Severity: Info.
AUTH0005
SNMP trap: No
Number of AUTHCODE digits entered does not match ALEN.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 120 of 2360

AUTH0006
Authcode database does not exist for specified customer.

Action:
Severity: Info.
AUTH0007
SNMP trap: No
Authcode already exists.

Action:
Severity: Info.
AUTH0008
SNMP trap: No
Specified authcode does not exist.

Action:
Severity: Info.
AUTH0009
SNMP trap: No
Specified Authcode already exists.

Action:
Severity: Info.
AUTH0010
SNMP trap: No
Not enough memory to allocate space.

Action:
Severity: info.
AUTH0011
SNMP trap: No
Authcode datablock cannot be deleted because Authcodes are still defined in

the Authcode table.
Action:
Severity: Info.
AUTH0012
SNMP trap: No
Input was received which requested a halt of the current process being
executed.
Action:
Severity: Info.
AUTH0013
SNMP trap: No
BAUT or NAUT package with which Authcode is associated is not active.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 121 of 2360

AUTH0014
System time-of-day has not been set via service change.

Action:
Severity: Info.
AUTH0015
SNMP trap: No
Route blobk selected for RAN does not exist or is not of type RAN.
Action:
Severity: Info.
AUTH0100
SNMP trap: No
That password has print only class of service allowed.

Action:
Severity: Info.
AUTH0101
SNMP trap: No
As the user, you do not have access to this data.

Action:
Severity:
AUTH0103
SNMP trap: No
When the authorization code (ACOD) length is ALEN = 4, the NMBR only
accepts values 0 - 9999.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 122 of 2360
553-3001-411
Standard 15.00
January 2006
Page 123 of 2360
BERR: Bus Error Monitor

Messages
BERR0000
CP local slave BERR.

Action:
Severity: Critical.
BERR0001
SNMP trap: Yes
CP IPB master data error.

Action:
Severity: Critical.
BERR0002
SNMP trap: Yes
CP IPB master time out.

Action:
Severity: Critical.
BERR0003
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
CP IPB master error.

Action:
Severity: Critical.
BERR0004
CP local decode error.

Action:
Severity: Critical.
BERR0005
CP illegal access.
Action:
Severity: Critical.
BERR0006
CP BIC default BERR {address}.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 124 of 2360

BERR0007
CP BIC BERR {address}.

Action:
Severity: Critical.
BERR0010
SNMP trap: Yes
CP triggered BERR {address}.

Action:
Severity: Critical.
BERR0012
SNMP trap: Yes
SRA DMA access BERR {address}.

Action:
Severity: Critical.
BERR0016
SNMP trap: Yes
CP SRA parity BERR {address}.

Action:
Severity: Critical.
BERR0017
SNMP trap: Yes
CP HPM timeout BERR {address}.

Action:
Severity: Critical.
BERR0020
SNMP trap: Yes
CP AP No response BERR {address}.

Action:
Severity: Critical.
BERR0021
SNMP trap: Yes
CP AP BIC IPB parity {address}, {ERRZ}.

Action:
Severity: Critical.
BERR0022
SNMP trap: Yes
CP AP local BERR {address}, {ERRZ}.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 125 of 2360

BERR0023
CP AP BIC illegal access {address}, {ERRZ}.

Action:
Severity: Critical.
BERR0024
SNMP trap: Yes
CP AP BIC default BERR {address}, {ERRZ}.

Action:
Severity: Critical.
BERR0200
SNMP trap: Yes
SIMM: Write protection violation.

Action:
Severity: Critical.
BERR0201 x y
SNMP trap: Yes
SIMM x y: Parity error at remote x y (address).

Action: Reseat the SIMMs. If the problem persists, replace the CP card.
Severity: Critical.
BERR0202 x y
SNMP trap: Yes
SIMM x y: Parity error at local x y (address).

Severity: Critical.
BERR0203 X Y
SNMP trap: Yes
SIMM x y: Unrecoverable memory or register Write error at x y (address).

Severity: Critical.
BERR0204 x y
SNMP trap: Yes
SIMM x y: Unrecoverable memory or register Read/Write error at x y

(address).
Severity: Critical.
BERR0300 x y z
SNMP trap: Yes
CNIP xyz: {address}, {BERZ}.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 126 of 2360

BERR0400 x y
CNIB x y: data parity error.

Action:
Severity: Critical.
BERR0401 x y
SNMP trap: Yes
CNIB x y: Local master parity error.

Action:
Severity: Critical.
BERR0402 x y
SNMP trap: Yes
CNIB x y: Local master timeout.

Action:
Severity: Critical.
BERR0403 x y
SNMP trap: Yes
CNIB x y: Local master bus error.

Action:
Severity: Critical.
BERR0404 x y
SNMP trap: Yes
CNIB x y: IPB event interrupt read.

Action:
Severity: Critical.
BERR0405 X Y
SNMP trap: Yes
CNIB x y: Local priority request asserted.

Action:
Severity: Critical.
BERR0406 x y
SNMP trap: Yes
CNIB x y: Unaligned ID EPROM access.

Action:
Severity: Critical.
BERR0407 x y
SNMP trap: Yes
CNIB x y: Unaligned event interrupt access.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 127 of 2360

BERR0408 x y
CNIB x y: {ADD}, {PARERRZ}, {IPBNT}, {BERRZ}, {ERRZ}.

Action:
Severity: Critical.
BERR0500
SNMP trap: Yes
HI EXC Self x: Restarting self due to queue corruption.

Action:
Severity: Critical.
BERR0501
SNMP trap: Yes
HI EXC Self x: Retrying Bus error analysis.

Action:
Severity: Critical.
BERR0502 x
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
HI EXC Self x: TID: y

Action: x.
Severity: Critical.
BERR0503 x
HI EXC Self x:
Action: x.
Severity: Critical.
BERR0504 x
HI EXC x: Task x suspended.

Action:
Severity: Critical.
BERR0505 x
SNMP trap: Yes
HI EXC x: Recovered from Bus error in ISR x (address).

Action:
Severity: Critical.
BERR0506 x
SNMP trap: Yes
HI EXC x: Starting analysis of Bus error from unknown task at x (address).

Note that the state of this task cannot be changed.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 128 of 2360

BERR0507 x
HI EXC x: Starting analysis of task x.

Action:
Severity: Critical.
BERR0508 x y
SNMP trap: Yes
HI EXC x: Completing analysis of task x. Decision: y.

Action:
Severity: Critical.
BERR0509
SNMP trap: Yes
HI EXC x: Bus error in ISR. SR = a, PC = b, Addr = c, SSW = d.

Action:
Severity: Critical.
BERR0510
SNMP trap: Yes
HI EXC x: Bus error in task x. SR = a, PC = b, Addr = c, SSW = d.

Action:
Severity: Critical.
BERR0511
SNMP trap: Yes
HI EXC x: Restart of Task x has been averted. Unknown address y has been
remapped. Number of remapped addresses: z. Total number of remaps: n.
Action:
Severity: Critical.
BERR0512
SNMP trap: Yes
HI EXC x: Address remap threshold has been exceeded.

Action: Restart the system.
Severity: Critical.
BERR0513
SNMP trap: Yes
HI EXC x: Address remap has been initialized.

Action:
Severity: Critical.
BERR0514
SNMP trap: Yes
HI EXC x: Recovered from Bus error at address x.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 129 of 2360

BERR0515
HI EXC x: Analyzing task x. Recommendation: y.

Action:
Severity: Critical.
BERR0600 x y z
SNMP trap: Yes
NCB x y:
Action: Check device x at address y in group z. Check I/O device, network
device, or PS card.
Severity: Critical.
BERR0601 x
SNMP trap: Yes
NCB x y: No response from 3PE on group x.

Action: Check both connectors on both ends of the CNI to 3PE cable. Be sure
the 3PE Enable/Disable switch is Enabled (up), and switch settings are correct.
Severity: Critical.
BERR0700
SNMP trap: Yes
EXCH: Total threshold exceeded: {vector}, {PC}, {fault address}.

Action:
Severity: Critical.
BERR0701
SNMP trap: Yes
EXCH: Threshold exceeded: {vector}, {PC}.

Action:
Severity: Critical.
BERR0702
SNMP trap: Yes
EXCH: Total threshold exceeded: {vector}, {PC}, {fault address}.

Action:
Severity: Critical.
BERR0703
SNMP trap: Yes
EXCH: Total threshold exceeded: {vector}, {PC}.

Action:
Severity: Critical.
BERR0704
SNMP trap: Yes
EXCH x: y in ISR. SR = a, PC = b, Addr = c, SSW = d

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 130 of 2360

BERR0705
EXCH x: y in task n. SR = a, PC = b, Addr = c, SSW = d

Action:
Severity: Critical.
BERR0800 x y
SNMP trap: Yes
IOP x y: ERRZ reason register content:??

Action:
Severity: Critical.
BERR0801 x y
SNMP trap: Yes
IOP x y: BIC detected an IPB data parity error.

Action:
Severity: Critical.
BERR0802 x y
SNMP trap: Yes
IOP x y: BIC detected a local data parity error.

Action:
Severity: Critical.
BERR0803 x y
SNMP trap: Yes
IOP x y: Local IOP bus timer timed out.

Action:
Severity: Critical.
BERR0804 X Y
SNMP trap: Yes
IOP x y: BIC received a local bus error.

Action:
Severity: Critical.
BERR0805 x y
SNMP trap: Yes
IOP x y: IPB attempted an event interrupt read.

Action:
Severity: Critical.
BERR0806 x y
SNMP trap: Yes
IOP x y: Local IOP bus asserted priority request during an inbound cycle.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 131 of 2360

BERR0807 x y
IOP x y: IPB attempted an unaligned IDP ROM access.

Action:
Severity: Critical.
BERR0808 x y
SNMP trap: Yes
IOP x y: IPB attempted an unaligned event interrupt.

Action:
Severity: Critical.
BERR0809 x y
SNMP trap: Yes
IOP x y: IOP window is disabled.

Action:
Severity: Critical.
BERR0810 x y
SNMP trap: Yes
IOP x y: Wrong IOP window size.

Action:
Severity: Critical.
BERR0811 x y
SNMP trap: Yes
IOP x y: Wrong IOP substitution address: x should be y.

Action:
Severity: Critical.
BERR0812 X Y
SNMP trap: Yes
IOP x y: Wrong IOP IPB match address: x should be y.

Action:
Severity: Critical.
BERR0813 x y
SNMP trap: Yes
IOP x y: Wrong IOP top of card address: x should be y.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 132 of 2360
553-3001-411
Standard 15.00
January 2006
Page 133 of 2360
BIC: Bus Interface Circuit

These messages are Test Failure messages for the Bus Interface Circuit (BIC)
that provides the interfaces and protocols for the Inter Processor Bus (IPB).
Messages
BIC0000 x y
BIC x y register read/write/verify test failed.

Action:
Severity: Minor.
BIC0001 x y
SNMP trap: No
BIC x y BIC/SRA interface IPBINT test failed.

Action:
Severity: Minor.
BIC0002 x y
SNMP trap: No
BIC x y BIC/SRA interface PARERR test failed.

Action:
Severity: Minor.
BIC0003 x y
SNMP trap: No
BIC x y arbitration test failed.

Action:
Severity: Minor.
BIC0004 x y
SNMP trap: No
SNMP trap: No
SNMP trap: No
BIC x y IRQ test failed.

Action:
Severity: Minor.
BIC0005 x y
BIC x y timer test failed.

Action:
Severity: Minor.
BIC0006 x y
BIC x y IOP event interrupt test failed.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 134 of 2360

BIC0007 x y
BIC x y CP self event interrupt test failed.

Action:
Severity: Minor.
BIC0008 x y
SNMP trap: No
BIC x y initial conditions failure.

Action:
Severity: Minor.
BIC0009 x y
SNMP trap: No
BIC x y window test failure.

Action:
Severity: Minor.
BIC0010 x y
SNMP trap: No
BIC x y testing the ASIC.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 135 of 2360
BKP: Remote Backup (Small Systems

and Succession 1000 systems)
Messages
BKP0001
Not applicable on CPU/Conf to System Core upgrade.

Action:
Severity: Info.
BKP0002
SNMP trap: No
Indicates a mismatch in the data file.

Action: 1. Compare the file again with the XVR command.2. If the verification
fails again, repeat the backup or restore process, and then re-verify using the
XVR command.3. Check your communications package parameters. Make sure
that the parameters such as Mode (should be set to BINARY) or Protocol (should
be set to XModem) are correctly set. Another possible cause is that the
communications package is stripping characters.
Severity: Info.
BKP0003
SNMP trap: No
Indicates that the Flash ROM in use contains invalid data and the procedure
failed.
Action: 1. When doing a backup (with the XBK command):a. Do an EDD to
update the flash ROM in use.b. Repeat the backup procedure using the XBK
command.2. When doing a Verify (with the XVR command) after performing a
backup (with the XBK command):a. do an EDD to update the flash ROM in useb.
repeat the Verify procedure using the XVR command3. When doing a restore
(with the XRT command):a. check the customer data file being transmitted to
ensure that it is the correct one.b. repeat the Restore procedure using the XRT
command. If it still fails, then a corrupted customer data file is a probablity.4.
When doing a Verify (with the XVR command) after performing a Restore (with
the XRT command):a. repeat the Restore procedure using the XRT command
Severity: Info.
SNMP trap: No
System Messages
Page 136 of 2360

BKP0004
Indicates a failure to erase either the cartridge Flash ROM (when in override
mode) or System Core (NTBK45) Flash ROM or the Primary and Secondary
Flash ROM on the Small System Controller card (NTDK20) on option 11C
systems.
Action: 1. Repeat the Restore procedure.2. If it fails again, a faulty Flash ROM
is the probable cause. Replace the System Core card or the S/W cartridge as
appropriate. Note: Option 11C systems are not equipped with S/W cartridges.
Severity: Info.
BKP0005
SNMP trap: No
SNMP trap: No
Copy failed (fatal).

Action:
Severity: Info.
BKP0006
Checksum failed on the restored configuration data.

Action:
Severity: Info.
BKP0007
SNMP trap: No
Indicates that the Flash ROM is not available at this time (it is being used by
another process).
Action: Wait for the current process to complete, and try again.
Severity: Info.
BKP0008
SNMP trap: No
Indicates that a transmission error occurred. The procedure may have

timed-out or there was a problem on the telephone line such as excessive
noise.
Action: Repeat the procedure.
Severity: Info.
BKP0009
SNMP trap: No
Overwrite error (fatal). Indicates that the Flash ROM could not be written
properly.
Action: 1. Repeat the Restore procedure using the XRT command. If it still fails,
ensure the file size does not exceed the size of the Flash ROM.2. If it fails again,
a faulty Flash ROM is the probable cause. Replace the System Core card or the
software cartridges as appropriate.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 137 of 2360

BKP0010
Not applicable to Option 11E

Action:
Severity: Info.
BKP0011
SNMP trap: No
Indicates that the Site ID in the customer data being restored (XRT command)
or verified (XVR command) does not match that of the Options 11 data stored
in the system. Note: The procedure completes normally. This message is only
a warning.
Action: 1. When doing a Restore (with the XRT command):a. If using this feature
as an install tool, this message is normal and does not indicate an error condition.
The site ID will be automatically corrected on the next data dump (EDD) and
backup.b. Check the customer data file to ensure it is the correct one. You may
inadvertently be restoring the wrong data file to the Option 11. If the data file is
correct, contact your technical support group.2. When doing a Verify (with the
XVR command) after a Restore (with the XRT command) or a backup (with the
XBK command): a. do an EDD to update the flash ROM in use b. repeat the
Restore or Backup procedure c. Repeat the Verify procedure
Severity: Info.
BKP0012
SNMP trap: No
Allocation error (fatal). Indicates that the Flash ROM could not be written
properly.
Action: 1. Repeat the Restore procedure using the XRT command. If it still fails,
ensure the file size does not exceed the size of the Flash ROM.2. If it still fails, a
faulty Flash ROM is the probable cause. Replace the System Core card or the
software cartridges as appropriate.
Severity: Info.
BKP0013
SNMP trap: No
Not appliable to Option 11E.

Action:
Severity: Info.
BKP0014
SNMP trap: No
The cartridge is not marked as PREP (fatal).

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 138 of 2360

BKP0015
The CPU/Conf. data is not marked as UPG

Action: Try reloading old cartridge and UPG again.
Severity: Info.
BKP0016
SNMP trap: No
The cartridge already has extracted data on it (fatal).

Action:
Severity: Info.
BKP0017
SNMP trap: No
Unable to flag cartridge as having extracted data (fatal).

Action:
Severity: Info.
BKP0018
SNMP trap: No
Insufficient space on cartridge for CPU/Conf data (fatal).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 139 of 2360
BRI: Basic Rate Interface

BRI messages indicate status and error conditions with ISDN Basic Rate
Interface hardware.
BRI0100 to 0399 are status messages turned on by the SETM MISP {loop#}
MNT command in LD 48. Use RSET MISP {loop#} MNT to stop printing these
messages.
Messages
BRI0000
Program Identifier
Action:
Severity: Minor.
BRI0100 tn x y
SNMP trap: No
MISP sent line card update message. The values for x and y are 6 digit HEX
numbers with each digit indicating the status of a DSL. The DSLs are identified
as follows: x = 00321 y=007654 The possible status conditions are: 0 = No
error 1 = Invalid DSL address 2 = Forced disconnect has timed out 3 = Invalid
state change 4 = MISP application failed to complete layer 1 connection 7 =
MISP application failed to queue the request Example: BRI100 l s c 004000
000000, where 4 indicates that the application failed to complete layer 1
connection on DSL 3.
Action:
Severity: Critical.
BRI0102 tn x
SNMP trap: Yes
MISP sent DSL update message. This message consists of one word (x) that
indicates the DSL status as follows: 0 = No error 1 = Invalid DSL address 2 =
Forced disconnect has timed out 3 = Invalid state change 4 = MISP application
failed to complete layer 1 connection 7 = MISP application failed to queue the
request Example: BRI100 l s c d 000003, where 3 indicates and invalid state
change on DSL l s c d.
Action:
Severity: Critical.
BRI0104 tn x y
SNMP trap: Yes
MISP sent DSL status message. The values x and y indicate the new DSL
state and the reason for the change. New DSL states (x): 0 = Unequipped 1 =
Disabled 2 = Maintenance busy 3 = Reserved for future use 4 = Enabled, but
network (layer 2) is in release state 5 = Enabled and network (layer 2) is
established 6 = Busy Possible reasons for change of state (y): 1 = The first
System Messages
Page 140 of 2360

network (layer 2) link has been established 2 = The last network (layer 2) link
has been released 3 = A DSL overload counters has been reached 4 =
Excessive layer 1 errors on a DSL have been detected
Action:
Severity: Critical.
BRI0105 tn x y
SNMP trap: Yes
MISP sent DSL B-channel status message. The values x and y indicate the
new DSL state and the reason for the change. New DSL states (x): 0 =
Unequipped 1 = Disabled 2 = Maintenance busy 3 = Reserved for future use
4 = Enabled, but network (layer 2) is in release state 5 = Enabled and network
(layer 2) is established 6 = Busy Possible reasons for change of state (y): 1 =
The first network (layer 2) link has been established 2 = The last network (layer
2) link has been released 3 = A DSL overload counters has been reached 4 =
Excessive layer 1 errors on a DSL have been detected
Action:
Severity: Critical.
BRI0107 tn x x x
SNMP trap: Yes
MISP sent line card audit message. The output data includes 8 fields (x x ... x)
providing the call reference of B-channels on each DSL (0-7). Each field is
formatted as 00B2B1, where B2 or B1 call reference status can be: 00 = No
error 01 = Missing MISP call reference 02 = Missing M1 CPU call reference 03
= M1 CPU/MISP have different call reference
Action:
Severity: Critical.
BRI0109 tn x y
SNMP trap: Yes
MISP sent line card status audit message. The values for x and y are 6 digit
HEX numbers with each digit indicating the status of a DSL. The DSLs are
identified as follows: x = 003210 y = 007654 The possible status conditions
are: 0 = No error 1 = DSL TN invalid (.me_bad_dsl) 2 = Force disconnect
time-out (.me_forcedisc_to) 3 = Bad state change (.me_bad_stt_chg) 4 =
Open layer 1 failure (.me_open_l1_fail) 7 = Could not queue the request
(.me_que_req_fail)
Action:
Severity: Critical.
SNMP trap: Yes
BRI0110 tn w x y z t MISP received line card B-channel status audit message. The B-channel
status consists of four words (w, x, y and z). The digits in these words indicate
the B1 and B2 channel status for each DSL as follows: w x y z = 001100
003322 005544 007766 (B2B1 for each DSL) For example: the first "1" is B2
553-3001-411
Standard 15.00
January 2006
Page 141 of 2360

channel on DSL 1, the second "1" is B1 channel on DSL 1. The possible status
conditions are: 0 = No error 1 = invalid DSL TN (.me_bad_dsl) 2 = Force
disconnect time-out (.me_forcedisc_to) 3 = Bad state change
(.me_bad_stt_chg) 4 = Open layer 1 failure (.me_open_l1_fail) 7 = Could not
queue the request (.me_que_req_fail)
Action:
Severity: Critical.
BRI0113 tn x
SNMP trap: Yes
MISP sent TEI check message. The value for x can be: 0 = TN cannot be found
(bad_tn) 1 = DSL is in wrong state (bad_dsl) 2 = Cannot send message to TE
(no_misp_resource)
Action:
Severity: Critical.
BRI0200 tn x
SNMP trap: Yes
Line card self test response. The response (x) can be: 0 = Passed self-test 1
= Line card microcontroller's internal RAM failure 2 = Line card
microcontroller's external RAM failure 3 = Line card microcontroller's EPROM
failure 4 = Network timeslot controller failure 5 = PAD EPROM failure 6 =
Microwire controller failure 7 = Reserved for future use 8 = DSL 0 transceiver
failure 9 = DSL 1 transceiver failure A = DSL 2 transceiver failure B = DSL 3
transceiver failure C = DSL 4 transceiver failure D = DSL 5 transceiver failure
E = DSL 6 transceiver failure F = DSL 7 transceiver failure
Action:
Severity: Critical.
BRI0201 tn x
SNMP trap: Yes
DSL reports layer 1 status. The status (x) is defined as follows. For SILCs in
network terminator (NT) mode, the possible status conditions can be: 0 = S/T
transceiver failure 1 = Physical (layer 1) is activated successfully 2 = Physical
(layer 1) is deactivated successfully 3 = Physical (layer 1) is losing
synchronization 4 = Physical (layer 1) is in the process of being established 5
= Physical (layer 1) failed to get established For SILCs in terminal equipment
(TE) mode, the possible status conditions can be: 0 = S/T interface transceiver
failure 1 = Physical (layer 1) is activated successfully 2 = Deactivation was
requested from far end 3 = Physical (layer 1) is losing synchronization 4 =
Physical (layer 1) is in the process of being activated 5 = Physical (layer 1)
failed to get established For UILCs in terminal equipment (TE) mode, the
possible status conditions can be: 0 = U interface transceiver failure 1 =
Physical (layer 1) is activated successfully 2 = Deactivation was requested
System Messages
Page 142 of 2360

from far-end 3 = Physical (layer 1) is losing synchronization 4 = Physical (layer
1) is in the process of being activated 5 = Physical (layer 1) failed to get
established 6 = Physical (layer 1) failed to be activated
Action:
Severity: Critical.
BRI0202 tn
SNMP trap: Yes
Line card responds to audit DSL state message. Five decimal numbers are
displayed following the DSL address indicating the status of the DSL. These
numbers specify the mode, B1 and B2 channel status, DSL sampling, framing,
and activation: Mode: 0 = Disabled 1 = NT1 mode, adaptive sampling 2 = NT1
mode, fixed sampling 3 = TE mode B1: 0 = B-channel disabled 1 = B-channel
enabled B2: 0 = B-channel disabled 1 = B-channel enabled Framing: 0 =
Multi-framing disabled 1 = Multi-framing enabled Activation: 0 = Waiting to be
activated 1 = Automatically activated
Action:
Severity: Critical.
BRI0204 tn
SNMP trap: Yes
Line card responds to terminal equipment query message.

Action:
Severity: Critical.
BRI0234
SNMP trap: Yes
Protocol Error: ZERO length for optional information element (IE). Output:
DSL: x DATA: y x = DSL number y = Information element (IE) identifier
Action:
Severity: Info.
BRI0255
SNMP trap: No
Protocol Error: Information request type is not supported. A message error or

a protocol error will be generated depending on whether the IE is mandatory
or not. Output: DSL: x DATA: y z x = DSL number y = Message type z =
Information element (IE) identifier
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 143 of 2360

BRI0256
Protocol Error: Wrong length for information request IE. The length on the
received IE is beyond the range. A message error or a protocol error will be
generated depending on whether the IE is mandatory or not. Output: DSL: x
DATA: y z x = DSl number y = Message type z = Information element (IE)
identifier
Action:
Severity: Info.
BRI0257
SNMP trap: No
Protocol Error: Information request specific is not supported. A message error

or a protocol error will be generated depending on whether the IE is mandatory
or not. Output: DSL: x DATA: y z x = DSL number y = Message type z =
Information element (IE) identifier
Action:
Severity: Info.
BRI0266
SNMP trap: No
Protocol Error: TCAP Package type is not recognized by Network Message

Center (NMC) feature. Output: DSL: x DATA: a b c d e f x = DSL number a =
TCAP package type b = TCAP component type c = Problem d = Originating
digit e = Destination digits f = Customer number
Action:
Severity: Info.
BRI0300 tn xy zz
SNMP trap: No
MISP sent interface data download message. Where x is the message type, y
is the message ID, and zz is the error code as follows: 0 = No error 1 = invalid
DSL TN (.ae_bad_dsl) 2 = Force disconnect time-out (.ae_forcedisc_to) 3 =
Terminal memory full (.ae_trm_mem_full) 4 = DSL not disabled
(.ae_dsl_not_dsbl) 5 = Interface memory full (.ae_if_mem_full)
Action:
Severity: Critical.
BRI0301 tn xy zz
SNMP trap: Yes
MISP sent timeslot download message. Where x is the message type, y is the
message ID, and zz is the error code as follows: 0 = No error 1 = invalid DSL
TN (.ae_bad_dsl) 2 = Force disconnect time-out (.ae_forcedisc_to) 3 = Bad
timeslot type (.ae_bad_ts_type) 4 = DSL active (.ae_dsl_active) 5 = Table full
(.ae_table_full) 6 = Invalid timeslot (.ae_lscd_ts_bad) 7 = Backup D-channel
enable failed (.ae_enbl_bd_fail)
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 144 of 2360

BRI0302 tn xy zz
MISP sent packet data download message. Where x is the message type, y is
the message ID, and zz is the error code as follows: 0 = No error 1 = invalid
Bad timeslot type (.ae_bad_ts_type) 4 = DSL active (.ae_dsl_active) 5 = Table
full (.ae_table_full) 6 = Invalid timeslot (.ae_lscd_ts_bad) 7 = Bd-channel
enable failed (.ae_enbl_bd_fail)
Action:
Severity: Critical.
BRI0303 tn xy zz
SNMP trap: Yes
MISP sent protocol data download message. Where x is the message type, y
is the message ID, and zz is the error code as follows: 0 = No error 1 = invalid
Bad protocol number (.ae__bad_prot_num) 4 = Protocol memory full
(.ae_prot_mem_ful) 5 = Invalid protocol (.ae_prot_bad)
Action:
Severity: Critical.
BRI0304 tn xy zz
SNMP trap: Yes
MISP sent Terminal Service Profile (TSP) data download message. Where x
is the message type, y is the message ID, and zz is the error code as follows:
0 = No error 1 = Invalid DSL TN (.ae_bad_dsl) 2 = Force disconnect time-out
(.ae_forcedisc_to) 3 = Bad TSP number (.ae_tsp_mem_ful) 4 = TSP memory
full (.ae_dn_mem_ful) 5 = Invalid TSP (.ae_tsp_bad)
Action:
Severity: Critical.
BRI0312
SNMP trap: Yes
Downloading Layer 3 tables to the MISP time-out. Default tables in MISP will
be used.
Action:
Severity: Critical.
BRI0314
SNMP trap: Yes
Downloading Layer 3 tables to the MISP failed. Default tables in MISP will be
used.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 145 of 2360

BRI0315
The BRI line card or BRSC does not have an MISP assigned to it.
Action: 1. Load LD 27. 2. CHG the configuration for the card. 3. At the MISP
prompt, enter a configured MISP loop number.
Severity: Critical.
BRI0316
SNMP trap: Yes
The interface parameters pertaining to the specified BRI line card are being
downloaded. Another independent task has requested to downloaded
interface parameters of the same line card. Since only one task can be active
at a given time, the second request is refused.
Action: Wait 30 seconds. If the entire line card is behaving properly, then the
second request was redundant. However, if you notice some oddities occurring
on certain DSLs, load LD 32 and use the DISU command to disable those DSLs,
then use the ENLU command to enable them. Any discrepancies should be
eliminated.
Severity: Critical.
BRI0317
SNMP trap: Yes
The command cannot be performed because the superloop network card is in

disabled state.
Action: 1. Load LD 32. 2. Execute the command to enable the XNET, ENLL
{XNET LOOP NUMBER}. 3. Retry the command.
Severity: Critical.
BRI0318
SNMP trap: Yes
The command cannot be performed because the controller card is in disabled

state.
Action: 1. Load LD 32. 2. Execute the command to enable the XPEC, ENXP
{XPEC NUMBER}. 3. Retry the command.
Severity: Critical.
BRI0319
SNMP trap: Yes
Failed to receive a response message from the BRSC card.

Action: 1. Check that the BRSC card is present in shelf. 2. If present, remove
the card, wait one second, then insert it into the same slot.3. If problem remains,
turn on the message monitor in LD 48.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 146 of 2360

BRI0320
Message intended for a served card (i.e., BRSCs) via the MISP card. The
MISP rejected the message. The reason for rejecting it is not displayed unless
the message monitor is turned on in LD 48.
Action:
Severity: Critical.
BRI0321
SNMP trap: Yes
During the fast interface download to the MISP application, the application
rejected the data for one of the interfaces belonging to the stated card TN. The
reason for failure is not displayed unless the message monitor is turned on in
LD 48.
Action:
Severity: Critical.
BRI0322
SNMP trap: Yes
During the fast interface download to the MISP application, the application
rejected the data for one of the TSPs belonging to the stated card tn. The
reason for failure is not displayed unless the message monitor is turned on in
LD 48.
Action:
Severity: Critical.
BRI0323
SNMP trap: Yes
Whenever the MISP BRIL or the BRSC application is enabled, the interface
configuration is sent to the ISDN BRI line card. This message indicates that
both the stated DSL TN and the consecutive ones configuration failed to get
sent. The interface chip on ISDN BRI line card will retain its original
configuration. If there were no configuration, the interface will be in UNEQ
state (in hardware, i.e., ISDN BRI line card).
Action: 1. Check state of the superloop controller card. 2. Check state of the
controller card. 3. Use LD 32 to first disable and then re-enable the two interfaces
encountered the failure. This action causes the configuration data to be
downloaded. If this fails, turned on the SSD message monitor in LD 48.
Severity: Critical.
BRI0324
SNMP trap: Yes
Cannot perform the requested task because the BRSC basecode is in

operational.
Action: Enable the BRSC basecode with the following: 1. Load LD 32. 2. Issue
the command ENLC BASE L S C 3. The BRSC basecode should get enabled
unless a problem is encountered.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 147 of 2360

BRI0325
After all the interface parameters (pertaining to a single BRI line card) have
been downloaded, the MISP card failed to acknowledge some or all of the
data.
Action: Wait 30 seconds. If the entire line card is behaving properly, then the
second request was redundant. However, if you notice some oddities occurring
on certain DSLs, load LD 32 and use the DISU command to disable those DSLs,
then use the ENLU command to enable them. Any discrepancies should be
eliminated.
Severity: Critical.
BRI0326
SNMP trap: Yes
Unable to send a message to the MISP card. A TN might follow the message
number. It either indicates the MISP loop number or the line card for which the
message was related to.
Action: Make sure that the MISP basecode and/or the related application is
operational. If so, there might be unable to handle the large flow of messages at
this time. Try the command later.
Severity: Critical.
BRI0327
SNMP trap: Yes
Unable to send a message to the BRSC card. A TN might follow the message
number. It either indicates the BRSC card TN or the BRI line card for which the
message was related to.
Action: Make sure that the superloop network card and controller card are
operational. If so, there might be unable to handle the flow of messages at this
time. Try the command later.
Severity: Critical.
BRI0328
SNMP trap: Yes
The Meridian 1 did not receive a message response from the MISP. A
message was sent (typically to the bootcode/basecode on the MISP, but the
response either was not sent by MISP or received by software.
Action: 1. Verify that the MISP/BRSC card is present in the shelf. 2. Verify that
MISP/BRSC is not malfunctioning. 3. Retry the portion of the command that
failed.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 148 of 2360

BRI0329
The Meridian 1 was not able to build an interface/TSP message during the fast
interface downloading process.
Action: 1. The application could be in disabled/transient state. 2. The pool of
message buffers is empty. 3. Retry the portion of the command that failed.
Severity: Critical.
BRI0330
SNMP trap: Yes
General information message. The relevant information follows the error

mnemonic.
Action:
Severity: Minor.
BRI0331
SNMP trap: Yes
The BRSC base or BRI application code will be downloaded to the card(s) as
soon as there is no program loaded.
Action: Quit the program by entering END if one is loaded.
Severity: Critical.
BRI0332
SNMP trap: Yes
The Enable BRSC base or BRI application task is suspended. Task will
resume when software downloading is done.
Action: If a program is loaded, quit the program by entering END to start
software download.
Severity: Critical.
BRI0333
SNMP trap: Yes
MISP did not respond to the D Channel Packet Switch Data (DPSD)
Connection data down load message.
Action:
Severity: Critical.
BRI0334
SNMP trap: Yes
MISP responded with an indication to the D Channel Packet Switch Data

(DPSD) Connection data down load message.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 149 of 2360

BRI0400
BRSC card does not exist, thus a dedicated connection cannot be established
or removed.
Action:
Severity: Critical.
BRI0401
SNMP trap: Yes
Must be a BRSC card to have this type of Bd-channel connections.

Action:
Severity: Critical.
BRI0402
SNMP trap: Yes
BD-channel dedicated connection cannot be established because there is no

available path between the MISP and the ISDN PRI loops.
Action:
Severity: Critical.
BRI0404
SNMP trap: Yes
Cannot download timeslot information to BRSC BRI Application.

Action:
Severity: Critical.
BRI0416
SNMP trap: Yes
Received ab M4 from the UILC card indicating that the S/T interface at NT1 is
deactivated.
Action: Check connection to the far end.
Severity: Critical.
SNMP trap: Yes
BRI0421 dsl# OVLD xxxx The overload control for the indicated BRIT D channel is active. Any
incoming new call setup request is rejected by protocol control. Where: dsl# is
the BRIT DSL tn xxxx is the number of ISDN messages during the last time
interval
Severity: Critical.
SNMP trap: Yes
System Messages
Page 150 of 2360

BRI0422
The UPIE layer 3 loadware INIT Rebuild Timer has expired. The BRIE INIT
rebuild process has been aborted. Transient call will not be rebuilt. Output
data: MISP LOOP: x DATA: y. Where: x= MISP loop number and y= message
type.
Severity: Info.
BRI0801
SNMP trap: No
Dedicated connection between the MISP and the line card cannot be
established.
Action:
Severity: Critical.
BRI0802
SNMP trap: Yes
SNMP trap: Yes
Task is aborted.
Action:
Severity: Minor.
BRI0803
Application is being enabled.

Action:
Severity: Minor.
BRI0805
SNMP trap: Yes
Error detected while downloading protocol to application; application is still

being enabled.
Action:
Severity: Critical.
BRI0806
SNMP trap: Yes
Protocol download message not acknowledged; application is still being

enabled.
Action:
Severity: Critical.
BRI0807
SNMP trap: Yes
Line card update message cannot be sent to the application.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 151 of 2360

BRI0808
Line card cannot be put in maintenance busy mode because message cannot
be sent to the MISP.
Action:
Severity: Critical.
BRI0809
SNMP trap: Yes
Basecode application has been enabled or disabled.

Action:
Severity: Critical.
BRI0810
SNMP trap: Yes
MISP is not present in the specified shelf.

Action: Make sure that you specified the correct shelf.
Severity: Info.
BRI0811
SNMP trap: Yes
SNMP trap: Yes
Data corruption.
Action:
Severity: Critical.
BRI0812
Resources not available to process the task; try again later.

Action:
Severity: Minor.
BRI0813
SNMP trap: Yes
Another task waiting to be processed.

Action: Wait at least 30 seconds and try again.
Severity: Minor.
BRI0814
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Illegal command.
Action:
Severity: Info.
BRI0815
Loop is unequipped.
Action:
Severity: Info.
System Messages
Page 152 of 2360

BRI0816
Loop is not configured as an MISP card.

Action:
Severity: Info.
BRI0817
SNMP trap: Yes
MISP BASECODE/Application is already in enabled state.

Action: If the behavior of the MISP BASECODE and/or Application is not
indicative of an enabled one, please disable it and then enable it. This could be a
mismatch of states between software and hardware.
Severity: Info.
BRI0818
SNMP trap: Yes
The specified application is not configured on the MISP.

Action:
Severity: Info.
BRI0819
SNMP trap: Yes
Peripheral loadware downloading to the MISP failed.

Action: Check to see that loadware is present on the diskette and the diskette is
inserted in disk drive.
Severity: Minor.
BRI0820
SNMP trap: Yes
One of the following has happened. 1. The MISP card has failed the self test,
or 2. Previous Flash EPROM Test may had been interrupted.
Action: Retry the command after 5 minutes. If problem persists, replace the
card.
Severity: Critical.
BRI0821
SNMP trap: Yes
Application cannot be enabled or disabled because software is being

downloaded.
Action:
Severity: Info.
BRI0822
SNMP trap: Yes
Task aborted. Firmware download cannot be completed because the

application is enabled.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 153 of 2360

BRI0823
Unable to send message to the MISP to enable or disable basecode

application.
Action:
Severity: Minor.
BRI0824
SNMP trap: Yes
MISP cannot perform the enable/disable tasks.

Action:
Severity: Minor.
BRI0825
SNMP trap: Yes
Message cannot be sent to remove application from the MISP's EEPROM.

Action:
Severity: Minor.
BRI0826
SNMP trap: Yes
Socket IDs have not been assigned to this application. Task is aborted.
Action:
Severity: Minor.
BRI0827
SNMP trap: Yes
Message to enable or disable has timed out; task aborted.

Action:
Severity: Minor.
BRI0828
SNMP trap: Yes
MISP is disabled; task cannot be performed.

Action:
Severity: Minor.
BRI0829
SNMP trap: Yes
The application is missing from the MISP card.

Action:
Severity: Minor.
BRI0830
SNMP trap: Yes
Basecode application is in transient state.

Action: Try the command again later.
Severity: Info.
SNMP trap: Yes
System Messages
Page 154 of 2360

BRI0831
MISP has sent an undefined response.

Action:
Severity: Minor.
BRI0832
SNMP trap: Yes
Protocols could not be downloaded to the MISP.

Action: Make sure that the MISP is enabled.
Severity: Minor.
BRI0834
SNMP trap: Yes
Hardware fault has been detected on the MISP.

Action:
Severity: Critical.
BRI0835
SNMP trap: Yes
The MISP card failed to process the "Protocol Download Request" message.
Action:
Severity: Critical.
BRI0836
SNMP trap: Yes
All applications must be disabled before disabling basecode.

Action:
Severity: Info.
BRI0837
SNMP trap: Yes
MISP basecode disabled without disabling the application(s); will attempt to

release application's resources but an INIT might be required if problems
persist.
Action:
Severity: Critical.
BRI0840
SNMP trap: Yes
Enabling or disabling process took too long; process was aborted.

Action:
Severity: Critical.
BRI0841
SNMP trap: Yes
Dedicated channel to the packet handler could not be established.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 155 of 2360

BRI0842
Dedicated channel to the packet handler could not be disconnected.

Action:
Severity: Critical.
BRI0843
SNMP trap: Yes
MISP basecode application failed; will try again in 0.5 second.

Action:
Severity: Critical.
BRI0844
SNMP trap: Yes
Automatic application software is pending.

Action: The download cannot be accomplished as long as LD 32 is active. Exit
the program to allow download.
Severity: Info.
BRI0845
SNMP trap: Yes
Enabling process was aborted and application firmware was not downloaded.
Action: Check to see that the firmware is present on the diskette and the diskette
is inserted in the disk drive. Also the MISP may be busy updating the flash
EPROM.
Severity: Minor.
BRI0846
SNMP trap: Yes
Application cannot be automatically enabled. Five tries to download the

application firmware failed.
Action: Enable application in LD 32.
Severity: Critical.
BRI0847
SNMP trap: Yes
Application loadware has been removed from the MISP.

Action:
Severity: Critical.
BRI0848
SNMP trap: Yes
Application is not identified with a socket ID, no communication with the MISP.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 156 of 2360

BRI0849
Task aborted. Meridian 1 cannot access the application information block on

the MISP.
Action:
Severity: Critical.
BRI0850
SNMP trap: Yes
DSL parameter cannot be downloaded because one or more pointers are nil.
Action: Try manually enabling the DSL to force the parameter to download. If
this does not work, remove the DSL and then recreate it using LD 27.
Severity: Critical.
BRI0851
SNMP trap: Yes
DSL parameter cannot be downloaded because Meridian 1 could not send

Action:
Severity: Critical.
BRI0852
SNMP trap: Yes
DSL parameter cannot be downloaded because no Call Register is available.

Action:
Severity: Critical.
BRI0853
SNMP trap: Yes
DSL parameter cannot be downloaded because the download request

message was invalid.
Action:
Severity: Critical.
BRI0854
SNMP trap: Yes
DSL parameter cannot be downloaded because the specified TSP is invalid.

Action:
Severity: Critical.
BRI0855
SNMP trap: Yes
DSL parameter cannot be downloaded because the MISP did not

acknowledge the download message.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 157 of 2360

BRI0856
DSL parameter cannot be downloaded because download procedure timed

out.
Action:
Severity: Critical.
BRI0857
SNMP trap: Yes
DSL parameter cannot be downloaded because the MISP and/or application

is disabled.
Action:
Severity: Critical.
BRI0858
SNMP trap: Yes
Line card does not exist, thus a dedicated connection cannot be established
or removed.
Action:
Severity: Minor.
BRI0859
SNMP trap: Yes
Only BRI line cards can have BD-channel connections.

Action:
Severity: Minor.
BRI0860
SNMP trap: Yes
SNMP trap: Yes
Software error.
Action:
Severity: Critical.
BRI0861
MISP is disabled, could not make a dedicated connection.

Action:
Severity: Critical.
BRI0862
SNMP trap: Yes
No path available to setup a D-channel dedicated connection.

Action:
Severity: Critical.
BRI0863
SNMP trap: Yes
Cannot send a message to the MISP to update the HDLC.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 158 of 2360

BRI0864
Cannot send a message to the MISP to update the HDLC.

Action:
Severity: Critical.
BRI0865
SNMP trap: Yes
Software bug: PRI loop pointer is nil.

Action:
Severity: Critical.
BRI0866
SNMP trap: Yes
PRI loop is disabled and a dedicated connections cannot be made.

Action:
Severity: Critical.
BRI0867
SNMP trap: Yes
Dedicated connection cannot be established or removed because the loop is

not
Action:
Severity: Critical.
BRI0868
SNMP trap: Yes
SNMP trap: Yes
B-channel is busy.
Action:
Severity: Critical.
BRI0870
Call Register is not available to establish a B-channel or BD-channel

dedicated connection.
Action:
Severity: Critical.
BRI0871
SNMP trap: Yes
A dedicated connection cannot be established because there is no available

path between the Extended Network Card and the ISDN PRI loops.
Action:
Severity: Critical.
BRI0872
SNMP trap: Yes
Invalid number for the specified B-channel or BD-channel type.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 159 of 2360

BRI0873
Unable to establish or remove a dedicated B-channel or BD-channel

connection because the ISDN PRI loop is disabled.
Action:
Severity: Critical.
BRI0874
SNMP trap: Yes

connection because the channel is in disabled state.
Action:
Severity: Critical.
BRI0875
SNMP trap: Yes

connection because the channel is in maintenance busy state.
Action:
Severity: Critical.
BRI0876
SNMP trap: Yes
Failure to establish BD-channel. Specified channel is busy.

Action:
Severity: Critical.
BRI0877
SNMP trap: Yes
BD-channel dedicated connection cannot be established because there is no

available path between the MISP and the ISDN PRI loops.
Action:
Severity: Critical.
BRI0878
SNMP trap: Yes
Cannot send a message to the MISP to update the HDLC about the
BD-channel.
Action:
Severity: Critical.
BRI0879
SNMP trap: Yes
Cannot send a message to the MISP to update the timeslot mapping for the
dedicated BD-channel connection.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 160 of 2360

BRI0880
Cannot establish D-channel, B-channel, or BD-channel dedicated connection

because the MISP application is disabled.
Action:
Severity: Critical.
BRI0881
SNMP trap: Yes
Failure to build BD-channel because the dedicated B-channel on the PRI loop
is BUSY.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 161 of 2360
BRIT: BRI Trunks

BRIT messages indicate status and error conditions for BRI Trunks. These
messaged can indicate:
Protocol errors associated with BRI Link
Database errors associated with BRI Link
Messages
BRIT0100 DSL
The B-channel indicated in the outgoing SETUP is locked out because the
far-end is using an alternate B-channel.
Action:
Severity: Info.
BRIT0101 DSL c
SNMP trap: No
The B-channel is locked out due to a RELCOMP or RELEASE. The message

has been received with one of the following cause (c) values: 82 = channel
does not exist 44 = requested channel is not available 6 = alternate channel
acceptable
Action:
Severity: Info.
BRIT0202
SNMP trap: No
Protocol Error: Incorrect value for extension bit. Output: DSL: x DATA: y z x =
DSL number y = Message type z = Information Element (IE)
Action: If the condition persists, contact your technical support group.
Severity: Minor.
BRIT0203
SNMP trap: No
Protocol Error: Mandatory Notification description invalid. Output: DSL: x

DATA: y z x = DSL number y = Message type z = Information Element (IE)
Severity: Minor.
BRIT0206
SNMP trap: No
Protocol Error: The length of the incoming call reference value was incorrect.
The length allowed is 1. There may be a compatibility problem with the far end.
Output: DSL: x DATA: y x = DSL number y = Call reference length
Severity: Minor.
SNMP trap: No
System Messages
Page 162 of 2360

BRIT0207
Protocol Error: Wrong message type. Output: DSL: x DATA: y x = DSL number
y = Message type
Severity: Minor.
BRIT0208
SNMP trap: No
Protocol Error: Wrong information element (IE) for message type. Output:
DSL: x DATA: y x = DSL number y = Message type
Severity: Minor.
BRIT0209
SNMP trap: No
Protocol Error: Undefined information element (IE) for message type. Output:
Severity: Minor.
BRIT0210
SNMP trap: No
Protocol Error: Wrong coding standard. Output: DSL: x DATA: y x = DSL

number y = Coding standard
Severity: Minor.
BRIT0211
SNMP trap: No
Protocol Error: Incorrect extension bit. Output: DSL: x DATA: y x = DSL

number y = Message type
Severity: Minor.
BRIT0212
SNMP trap: No
Protocol Error: Bearer capability (BC) - Information transfer not supported.

Output: DSL: x DATA: y x = DSL number y = Transfer capability
Severity: Minor.
BRIT0213
SNMP trap: No
Protocol Error: Bearer capability (BC) - Information transfer rate/mode not

supported. Output: DSL: x DATA: y x = DSL number y = Transfer rate
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 163 of 2360

BRIT0214
Protocol Error: Bearer capability (BC) - Layer 1 protocol ID not correct. Output:
DSL: x DATA: y x = DSL number y = Protocol ID
Severity: Minor.
BRIT0215
SNMP trap: No
Protocol Error: Bearer capability (BC) - Rate is not correct. Output: DSL:x
DATA: y x = DSL number y = Message type
Severity: Minor.
BRIT0216
SNMP trap: No
Protocol Error: Bearer capability (BC) - Rate is not correct. Output: DSL: x
DATA: y x = DSL number y = Rate
Severity: Minor.
BRIT0217
SNMP trap: No
Protocol error: General location not supported. Output: DSL:x DATA: y x =

DSL number y = General location number
Severity: Minor.
BRIT0218
SNMP trap: No
Protocol Error: Cause value not supported. Output: DSL: x DATA: y x = DSL
number y = Cause information element (IE)
Severity: Minor.
BRIT0219
SNMP trap: No
Protocol Error: channel ID octet 3 error. Output DSL: x DATA: y x = DSL

number y = B-channel number
Severity: Minor.
BRIT0222
SNMP trap: No
Protocol Error: Channel number does not exist. Output: DSL: x DATA: y x =
DSL number y = B-channel number
Severity: Minor.
SNMP trap: No
System Messages
Page 164 of 2360

BRIT0223
Protocol Error: CREF flag in SETUP message is incorrect. Output: DSL: x

DATA: y x = DSL number y = Call reference number
Severity: Minor.
BRIT0224
SNMP trap: No
Protocol Error: State message error, protocol violation. The state IE is not
appropriate for the current state. Output: DSL: x DATA: a b c d e x = DSL
number a = Pointer to BRIT message call register b = UTN c = State PM d =
Message type e = Call reference number
Severity: Minor.
BRIT0225
SNMP trap: No
Protocol Error: State message error, protocol violation. Release complete

received in U11 or U31 state. Output: DSL: x DATA: y x = DSL number y =
Message type
Severity: Minor.
BRIT0227
SNMP trap: No
Protocol Error: Message received in NULL state. Output: DSL: x DATA: y x =

DSL number y = Message type
Severity: Minor.
BRIT0228
SNMP trap: No
Protocol Error: Mandatory Channel ID missing in ALERTing. Output: DSL: x

DATA: y x = DSL number y = NONE
Severity: Minor.
BRIT0229
SNMP trap: No
Protocol Error: Mandatory Channel ID missing in incoming CONNect

message. Output: DSL: x DATA: y x = DSL number y = NONE
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 165 of 2360

BRIT0232
Protocol Error: PROGRESS INDICATOR not supported. Output: DSL: x

DATA: y x = DSL number y = Message type
Severity: Minor.
BRIT0233
SNMP trap: No
Protocol Error: ZERO length for mandatory information element (IE). Output
DSL: x DATA:y x = DSL number y = Information element (IE) identifier
Severity: Minor.
BRIT0235
SNMP trap: No
Protocol Error: Bearer capability (BC) - Layer ID is not correct. Output: DSL: x
DATA: y x = DSL number y = Layer ID
Severity: Minor.
BRIT0236
SNMP trap: No
Protocol Error: Incorrect Transit Network Selection (TNS) Network ID. Output:
Severity: Minor.
BRIT0237
SNMP trap: No
Protocol Error: Message length exceeds buffer size. Output: DSL: x DATA: y
x = DSL number y = message type
Severity: Minor.
BRIT0238
SNMP trap: No
Protocol Error: Protocol discriminator is not compatible with the message

received. Output: DSL: x DATA: y x = DSL number y = Protocol discriminator
Severity: Minor.
BRIT0239
SNMP trap: No
Protocol Error: Maintenance message is not allowed for this DSL interface.
Output: DSL: x DATA: y x = DSL number y = Message type
Severity: Minor.
SNMP trap: No
System Messages
Page 166 of 2360

BRIT0241
Protocol Error: No response from far end to this BRIT call. Output: DSL: x
DATA: y x = DSL number y = B-channel number
Severity: Minor.
BRIT0242
SNMP trap: No
Protocol Error: Received a BRIT message with an unsupported service

identifier. Output: DSL: x DATA: y x = DSL number y = Service identifier
Action:
Severity: Minor.
BRIT0243
SNMP trap: No
Protocol Error: Service discriminator is not supported by BRIT.Output: DSL: x

DATA: y x = DSL number y = Service discriminator
Severity: Minor.
BRIT0244
SNMP trap: No
Protocol/Database Error: Facility reject message received. Output: DSL: x

DATA: a b c d e x = DSl number a = Originating PNI b = Originating number c
= Destination PNI d = Destination number e = Reason
Action: Verify that the PNI values are correct in the customer and route data
block and are consistent with the switch on the other end of the link.
Severity: Minor.
BRIT0245
SNMP trap: No
Database Error: Missing PNI number in the customer data block. Output: DSL:
x DATA: y z x = DSL number y = Customer number z = Service ID
Action: Look into the customer data block to configure the PNI.
Severity: Minor.
BRIT0246
SNMP trap: No
Protocol Error: Received bad facility information element (IE). Output: DSL: x
DATA: y x = DSL number y = Error indication
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 167 of 2360

BRIT0247
Database Error: PNI missing in Route Data Block. Output: DSL: x DATA: y x
= DSL number y = Service identifier
Severity: Minor.
BRIT0248
SNMP trap: No
Protocol Error: ROSE component sent is being rejected. Output: DSL: x

DATA: y x = DSL number y = Service identifier
Severity: Minor.
BRIT0249
SNMP trap: No
Protocol Error: ISDN: Received a Status message with CAUSE = 30. This is
normally received in response to a Status Inquiry but the Meridian 1 did not
send out a Status Inquiry message. The Status message is ignored. Output:
DSL: x DATA: y x = DSL number y = DSL interface ID
Severity: Minor.
BRIT0250
SNMP trap: No
Protocol Error: Received information element (IE) is in the wrong code set.
Output: DSL: x DATA: y x = DSL number y = Information element (IE)
identifier.
Severity: Minor.
BRIT0251
SNMP trap: No
Protocol Error: The Presentation Method of Protocol Profile (PMPP) is wrong

in the High Layer Compatibility IE. Output: DSL: x DATA: y x = DSL number y
= High Layer Compatibility PMPP
Severity: Minor.
BRIT0252
SNMP trap: No
Protocol Error: The Interpretation of High Layer Characteristics ID is wrong the

High Layer Compatibility IE. Output: DSL: x DATA: y x = DSL number y = High
Layer Compatibility INTERPRT
Severity: Minor.
SNMP trap: No
System Messages
Page 168 of 2360

BRIT0253
Protocol Error: The High Layer Characteristic ID is wrong in the High Layer
Compatibility IE. Output: DSL: x DATA: y x = DSL number y = Release ID z =
Service identifier
Severity: Minor.
BRIT0254
SNMP trap: No
Database Error: The DSL is interfacing with a software issue not supported by
the application. Output: DSL: x DATA: y z x = DSl number y = Release ID z =
Service identifier
Action: Verify that the release ID in the configuration record is the same as the
software release running on the far end switch.
If available, turn on the Alarm Filtering Package (#243) or Upgrade all the ISDN
MCDN switches to the same software release.
Severity: Minor.
BRIT0261
SNMP trap: No
Database Error: The DSL interface for routing Network Message Service
(NMS) facility messages is not a Meridian 1 interface. Output: DSL: x DATA:
a b c d x = DSL number a = Operation code for TCAP protocol b = Originating
digits c = Terminating digits d = Customer number
Action: Verify database configuration.
Severity: Minor.
BRIT0262
SNMP trap: No
Protocol Error: Invalid value for the interface identifier field or channel ID
information element from an incoming message. Output: DSL: x DATA: y x =
DSL number y = Message type
Severity: Minor.
BRIT0265
SNMP trap: No
Database Error: A Facility Reject message was received. Destination digits

cannot be translated. Output: DSL: x DATA: a b c d e x = DSL number a =
TCAP package type b = Problem (NOXLAN/NONMS) c = Originating digits d
= Destination digits e = Customer number
Action: Verify numbering plan database are consistent between the near and far
end switches.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 169 of 2360

BRIT0267
Protocol Error: TCAP package type is not recognized by Network Message

Center (NMC) feature. Output: DSL: x DATA: a b c d x= DSL number a = TCAP
package type b = Originating digits c = Destination digits d = Customer number
Severity: Minor.
BRIT0268
SNMP trap: No
Protocol Error: TCAP Component is not recognized by Network Message

Center (NMC) feature. Output: DSL: x DATA: a b c d x = DSL number a =
TCAP package type b = TCAP component type c = Originating digits d =
Destination digits e = Customer number
Severity: Minor.
BRIT0269
SNMP trap: No
Protocol Error: TCAP Operation is not recognized by Network Message

Center (NMC) feature. Output: DSL: x DATA: a b c d e f x = DSL number a =
TCAP package type b = TCAP component type c = Operation d = Originating
digits e = Destination digits f = Customer number
Severity: Minor.
BRIT0270
SNMP trap: No
Protocol Error: TCAP parameter is not recognized by Network Message

Center (NMC) feature. Output: DSL: x DATA: a b c d e f g x = DSL number a
= TCAP package type b = TCAP component type c = Operation d = Parameter
e = Originating digits f = Destination digits g = Customer number
Severity: Minor.
BRIT0271
SNMP trap: No
Database Error: LDN0 must be defined for the customer for ISDN DID calls in
order to determine the number of digits expected for successful call
termination. Output: DSL: x DATA: y x = DSL number y = Customer number
Action: Configure LDN0 in the customer data block.
Severity: Minor.
BRIT0272
SNMP trap: No
Message is ping-pong between two nodes.

Action: Check the numbering plan configuration on both sides.
Severity: Minor.
SNMP trap: No
System Messages
Page 170 of 2360

BRIT0273
An application has requested to send a Facility/Facility Reject message on an

unsupported ISDN interface. The request is being rejected.
Output : DSL Number, BRIT type, Service identifier. The following service
identifiers are defined:
1. Network Ring Again.
2. Network ACD.
3. Network Attendant Service.
4. Network Message Center.
5. Trunk Route Optimization.
6. Network Call Trace.
7. Remote Virtual Queuing.
8. VNS Service.
9. Network Remote Call Forward.
10. Network Radio paging.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 171 of 2360
BSD: Background Signaling Diagnostic

(LD 45)
The Background Signaling and Switching Diagnostic program (LD 45) tests
peripheral equipment and is used to perform continuity tests on superloops.
Any telephone, terminal, console or card that fails the signaling test may be
disabled by this program. To re-enable the device, see LD 32. If a device fails
the signaling test and is disabled, it will be automatically re-enabled if it passes
a subsequent signaling test, whether the test was manually requested or
automatically initiated.
For superloops use LD 30 to test signaling and network memories.
This Overlay is not available on Option 11 systems. Use Overlay 30 (LD 30)
to perform signaling tests on these systems.
Messages
BSD0000
Background Signaling and Diagnostic (LD 45) has been loaded.

Action:
Severity: Info.
BSD0001
SNMP trap: Yes
SNMP trap: Yes
Invalid command.
Action:
Severity: Minor.
BSD0002
An attempt was made to enter a command while a previous TEST command

was still being executed. The new command is ignored.
Action:
Severity: Minor.
BSD0022
SNMP trap: Yes
During execution of a TEST command, the continuity test procedure

encountered an "all channels busy" condition. One or more of the continuity
tests were not performed.
Action: Retry TEST command later. No fault is implied by this message.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 172 of 2360

BSD0023 loop
During execution of a TEST command, a message request

generating/detecting patterns is not able to be sent to the NT8D04 Network
card.
Action:
Severity: Minor.
BSD0024 loop
SNMP trap: Yes
During execution of a TEST command, cannot query the continuity test result
of the NT8D04 Network card.
Action:
Severity: Minor.
SNMP trap: Yes
BSD0080 c: s1 s2 sn Program has switched to CPU c. When this CPU is active, IGS card(s) s1,
s2, etc., either do not respond or fail the memory test.
Action: 1. Compare the BSD080 list of IGS cards with the BSD082 list of IGS
cards. IGS cards which appear in both lists are likely to be faulty. Go to LD 39.
Use the commands STAT IGS x and ENL IGS x to identify and enable disabled
IGS cards. If the IGS card cannot be enabled, replace it. 2. If a particular IGS card
either generates only a BSD080 message or generates no BSD082 message, the
fault is likely to be on the CE EXT connecting CPU c to the Network Shelf. Go to
LD 35. Use the commands STAT EXT and ENL EXT to identify and enable either
the disabled Segmented Bus Extender card or the 3 Port Extender card. Replace
any cards which remain disabled after this procedure.
Severity: Critical.
SNMP trap: Yes
BSD0081 c: l1 l2 ln Program has switched to CPU c. When this CPU is active, Network loops l1,
l2, etc. either do not respond or fail the memory test.
Action: 1. Compare the BSD081 list of network loops with the BSD083 list of
network loops. If a network loop appears in both lists, then the card associated
with that loop may be faulty. Go to LD 32. Use the commands STAT l and ENLL
l to identify and enable disabled loops. Replace the Network card if loops remain
disabled after this procedure. 2. If no Network card on a particular network shelf
responds, the fault may be: a. on the IGS (Intergroup Switch) card on that network
shelf. Go to LD 39. Use the commands STAT IGS x and ENLL l to identify and
enable disabled IGS cards. If an IGS card remains disabled, replace it. b. in the
cable which connects the IGS card to the junctor. Replace this cable and run LD
45 (BSD) to verify that the fault has been cleared. c. on the Peripheral Signaling
(PS) card for that shelf. Go to LD 32. Use the commands STAT PER x and E PS
x to identify and enable disabled PS cards. If a PS card remains disabled, replace
it. 3. If Clock Controller 0 (SCG 0) is active to shelf 0, a faulty cable probably
553-3001-411
Standard 15.00
January 2006
Page 173 of 2360

exists. Replace the faulty cable and verify that the fault has been cleared in LD
45. The faulty cable will be found between: a. the Clock Controller card and the
junctor, or b. the Network card and Peripheral Buffer card, or c. two Peripheral
Buffer cards. 4. If a network loop only appears in a BSD081 message, or if no
BSD083 message follows, the probable fault can be found on: a. the CE EXT
connecting the network shelf (containing the Network card) to the active CPU c.
b. the cable connecting the CE EXT to the network shelf. Go to LD 35. Use the
commands STAT EXT and ENL EXT x to identify and enable disabled extended
pairs belonging to either Segmented Bus Extender cards or 3 Port Extender
cards. Replace the extender card if any extender pairs remain disabled after this
procedure.
Severity: Critical.
BSD0090
SNMP trap: Yes
The program has detected a power fault indication.

Action: Check power monitor indicators. If there is a power failure but no fault is
found, the minor alarm lamp lights on the attendant console. If a power fault has
been detected and the overlay area is idle, then LD 45 is run in background. To
restore the regular background programs defined in LD 17, let LD 45 run twice
and issue the clear major alarm command (CMAJ) from LD 30, LD 34, LD 35, LD
54 or LD 92.
Severity: Critical.
BSD0110 l1 l2 ln
SNMP trap: Yes
Loops l1, l2, etc. are unable to transmit speech to any loop on the other
network shelf of that group. Minor alarm lamp lit on attendant console.
Suspect: 1. If there is only one terminal loop on the other shelf, the associated
Network card may be faulty. 2. If only one loop (l1) appears in the list, there is
a possible intermittent fault in the network for Loop l1. 3. If only one loop (l1)
appears in the list, an intermittent fault may exist in either the Peripheral Buffer
or the Controller connected to loop l1. 4. The Peripheral Buffer (PB) or
Controller may be faulty. 5. A faulty cable between the Network card and the
Peripheral Buffer 6. A faulty cable between superloop and the Controller 7. A
faulty Network card on loops l1, l2, etc. 8. CE EXT between CPUs may be
faulty 9. PS cards 10. Other network, CONF and TDS cards 11. IGS cards
CPU cards
Action: The following actions correspond numerically to the fault locations listed
above: 1. Go to LD 32. Identify and attempt to enable any disabled cards using
the STAT 1 and ENLL 1 commands. Replace Network card(s) if faults do not
clear. 2. Go to LD 32. Identify and attempt to enable any disabled cards using the
STAT 1 and ENLL 1 commands. Replace Network card(s) if faults do not clear.
3. Replace these cards, starting with the card on the highest numbered PE shelf
of the loop. 4. Go to LD 32. Identify and attempt to enable disabled PB cards with
System Messages
Page 174 of 2360

the commands STAT l s and ENL l s. You may check the status of a Controller
card by inputting the command XPCT x. Alternatively, you may elect to unseat,
reseat and then test a controller card. 5. Replace faulty cable. 6. Replace faulty
cable between Controller backplane and Superloop. 7. Go to LD 32. Identify and
attempt to enable disabled Network cards with the commands STAT l and ENL l.
If loops remain disabled, replace the card. 8. You will need to do one of the
following: a. Check and replace the Segmented Bus Extender card or the 3 Port
Extender card. b. Replace any faulty cables connecting extenders associated
with the standby CPU and the network shelf containing the affected IGS card. 9.
Go to LD 32. Use the commands STAT PER x and ENPS x to identify and enable
disabled PS cards. If the PS card remains disabled, replace it. 10. CFN card
status may be checked in LD 34. TDS card status may be checked in LD 38. 11.
IGS card status may be checked in LD 39. CPU card status may be checked in
LD 35 by using the TCPU command. Avoid using the TCPU command during
periods of heavy telephone usage as it may cause the system to reload.
Severity: Critical.
BSD0112
SNMP trap: Yes
Loops unable to xmit via IGS on corresponding shelf

Action: Please contact your technical support.
Severity: Major.
BSD0113
SNMP trap: Yes
Loops unable to xmit via IGS on opposite shelf

Severity: Major.
BSD0114
SNMP trap: Yes
Loops could not xmit to other group

Severity: Major.
BSD0115
SNMP trap: Yes
Loops could not receive from other group

Severity: Major.
BSD0116
SNMP trap: Yes
No Loops could xmit to other group

Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 175 of 2360

BSD0117
Loops could not receive

Severity: Major.
BSD0122
SNMP trap: Yes
No loop in this group could receive junctors

Severity: Major.
BSD0123
SNMP trap: Yes
Junctors could be received by only 1 of 2 net shelves

Severity: Major.
BSD0124
SNMP trap: Yes
No loops in this group could reveive junctors

Severity: Major.
BSD0131
SNMP trap: Yes
Junctor memory test of IGS pack failed

Severity: Major.
BSD0132
SNMP trap: Yes
Junctor memory test of IGS pack detected address decode

Severity: Major.
SNMP trap: Yes
BSD0202 loop: s1 s1 sn The continuity test from network loop to shelves (indicated by s1, s2,
etc.) has failed. The minor alarm lamp lit on attendant console. If L is an RPE
loop, using LD 33 may aid in fault location. Probable fault in: 1. RPE loop, if L
is an RPE loop. 2. Peripheral Buffer card(s) on shelf/shelves listed P 3.
interconnecting cable to PE shelves 4. Network card 5. IGS cards in the same
group 6. CE EXT connecting CPU 7. PS cards 8. all other network, conference
and TDS cards in same group 9. For superloops the continuity test failed from
System Messages
Page 176 of 2360

network pack L to Peripheral Controllers s1 and s2. Probable fault in: a.
Peripheral Controller b. cables to Peripheral Controller shelf backplane and
Superloop Network card. c. NT8D04 Network card
above: 1. Go to LD 33. Test the RPE loop. See the RPE NTP for further
information. 2. Go to LD 32. Identify and attempt to enable disabled PB cards with
the commands STAT l s and ENL l s. Replace PB cards that remain disabled. 3.
Replace cable and run test in LD 45 to confirm that the fault has been cleared. 4.
Go to LD 32. Use the commands STAT l and ENLL l to identify and enable
disabled loops. Replace the Network card if loops remain disabled. 5. Replace
the IGS card and run LD 45 (BSD) to verify the fault is cleared. 6. Go to LD 39.
Use the commands STAT IGS x and ENL IGS x to identify and enable disabled
IGS cards. If the IGS card cannot be enabled, replace it. Run LD 45 to confirm
that the fault has been cleared. 7. Go to LD 32. Use the commands STAT PER x
and ENPS x to identify and enable disabled PS cards. If the PS card remains
disabled, replace it. 8. CFN card status may be checked in LD 34. TDS card
status may be checked in LD 38. 9. To correct these faults: a. Go to LD 32. Use
the XPCT x command to test the Controller. If the Controller fails the test, replace
it. b. Replace the cable and run LD 45 (BSD) to verify the fault is cleared. c. Go
to LD 32. Use the commands STAT l and XNTT l to identify and test superloops.
If a superloop fails the test, replace it.
Severity: Critical.
BSD0205 loop
SNMP trap: Yes
Continuity checker on loop L suggest that the network is faulty.

Action: Go to LD 32. Use the commands STAT l and ENLL l to identify and
enable disabled loops. Replace the Network card if loops remain disabled.
Severity: Critical.
SNMP trap: Yes
BSD0206 loop: l1 l2 ln Loop unable to receive speech from l1, l2, etc. Minor alarm lamp lit on
attendant console. Probable fault cause: 1. Network card for loop l 2. If you
cannot receive only one loop (l1), there is a possible intermittent fault in the
Network card for loop l1. This is the expected fault type if any other loops
cannot receive l1 or if L1 appears in a BSD0110 message. 3. If only one loop
(l1) cannot be received, possible intermittent fault in one of the peripheral
buffer connected to loop l1 4. All other network, conference and TDS cards in
the same group.
above: 1. Go to LD 32. Use the commands STAT l and ENLL l to identify and
enable disabled loops. Replace the Network card if loops remain disabled. 2. Go
to LD 32. Use the commands STAT l and ENLL l to identify and enable disabled
553-3001-411
Standard 15.00
January 2006
Page 177 of 2360

loops. Replace the Network card if loops remain disabled 3. Replace each
Peripheral Buffer in turn, starting with the one on the highest numbered PE shelf.
The test should then be allowed to run long enough to indicate whether the
problem will persist. 4. CFN card status may be checked in LD 34. TDS card
status may be checked in LD 38.
Severity: Critical.
BSD0208 loop: ts
SNMP trap: Yes
The software network map indicates that timeslot s of loop L is idle but network
memory word for that slot is not idle. The indicated slot is marked busy in the
software map and the current continuity test of loop L is abandoned. A
possible software fault may exist which is similar to the type referred to in
BUG0365. If several BSD0208 or BUG0365 messages appear which involve
loop L or if a BSD0203 message appears involving loop L, the network for loop
L is probably faulty. See BSD203 comments.
Action: Go to LD 32. Use the commands STAT l and ENLL l to identify and
enable disabled loops. Replace the Network card if loops remain disabled.
Contact technical support staff if replacing loop l does not clear the fault.
Severity: Critical.
BSD0601 j1 j2 g
SNMP trap: Yes
No loop tested on groups could receive from junctor J1, J2 or faults: 1. IGS 2.
3PE 3. SCG
above: 1. Go to LD 39. Use the commands STAT IGS x and ENL IGS x to identify
and enable disabled IGS cards. If the IGS card cannot be enabled, replace it. Run
LD 45 to confirm that the fault has been cleared. 2. Identify and attempt to enable
disabled extender pairs (associated with the Segmented Bus Extender card and
3 Port Extender card) with the commands STAT EXT and ENL EXT x. Replace
extender cards that remain disabled. 3. Get status of SCG0 (if clock controller, go
to Input/Output guide, LD 60). Replace the disabled SCG card and run LD 45
(BSD) again to verify fault cleared.
Severity: Minor.
BSD0606
SNMP trap: Yes
It is not applicable to XNPD card.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 178 of 2360

BSD0659
Cannot perform test on non-BRSC card. Loopback address must be a BRSC

card TN plus a dummy unit number.
Action: Enter a BRSC card TN plus a dummy unit number.
Severity: Minor.
BSD0660
SNMP trap: Yes
Cannot perform test on the ISDN line card or DSL. The BRSC BRI application
that performs Layer 2 signaling processing for the line card or DSL must be in
ENABLED state.
Action: Check the BRSC state and enable it if necessary.
Severity: Minor.
BSD0661
SNMP trap: Yes
Cannot perform test on the BRSC.

Action: The BRSC BASE application must be in ENABLED state and the BRI
application must be in MANUALLY DISABLED state. If the BRI application is
enabled, disable only the application in LD 32 with the DISC BRI command. If the
BASE application is disabled, enable only the BASE application in LD 32 with the
ENLC BASE command.
Severity: Minor.
BSD0662
SNMP trap: Yes
Input TN is already in another test.

Action: Enter another TN.
Severity: Minor.
BSD0663
SNMP trap: Yes
Input DSL TN is undefined.

Action: Enter another DSL TN.
Severity: Minor.
BSD0800
SNMP trap: Yes
SNMP trap: Yes
Command executing.
Action:
Severity: Minor.
BSD0801
No Call Register available.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 179 of 2360

BSD0802
No superloop Network card.

Action:
Severity: Minor.
BSD0803
SNMP trap: Yes
SNMP trap: Yes
No Controller card.
Action:
Severity: Minor.
BSD0804
Requested time slot is busy.

Action:
Severity: Minor.
BSD0805
SNMP trap: Yes
No time slots free on superloop. If test is run on E-1 or T-1, the timeslot may
not be available because of the specific timeslot to a carrier allocation.
Action:
Severity: Minor.
BSD0806
SNMP trap: Yes
Loop back channel not available.

Action:
Severity: Minor.
BSD0807
SNMP trap: Yes
Time-out waiting for network response.

Action:
Severity: Minor.
BSD0808
SNMP trap: Yes
SNMP trap: Yes
Requested TN is busy.
Action:
Severity: Minor.
BSD0809
Requested TN is maintenance busy.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 180 of 2360

BSD0810
Controller does not belong to Controller.

Action:
Severity: Minor.
BSD0811
SNMP trap: Yes
SNMP trap: Yes
No terminal at that TN.

Action:
Severity: Minor.
BSD0812
Digital terminal at that TN.

Action:
Severity: Minor.
BSD0813
SNMP trap: Yes
Slot on requested junctor is busy.

Action:
Severity: Minor.
BSD0814
SNMP trap: Yes
No junctors available for generate slot.

Action:
Severity: Minor.
BSD0816
SNMP trap: Yes
Tags not available.

Action: Stop a test by executing XSTP command and try again.
Severity: Minor.
BSD0817
SNMP trap: Yes
Generate message could not be sent. The system is temporarily out of

message registers.
Action: Wait and try again.
Severity: Minor.
BSD0818
SNMP trap: Yes
Detect message could not be sent. The system is temporarily out of message
registers.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 181 of 2360

BSD0819
XMI message could not be sent. The system is temporarily out of message
registers.
Severity: Minor.
BSD0820
SNMP trap: Yes
Last one-shot test still running.

Action: Wait until the test is completed or stop the test by executing XSTP 0
command and try again.
Severity: Minor.
BSD0821
SNMP trap: Yes
Tag number has not been assigned to a test.

Action:
Severity: Minor.
BSD0822
SNMP trap: Yes
Database error: pointer nil.

Action:
Severity: Minor.
BSD0823
SNMP trap: Yes
One-shot status not printed.

Action: Use XSTA command to get the test status.
Severity: Minor.
BSD0824
SNMP trap: Yes
SNMP trap: Yes
Loop is disabled.
Action:
Severity: Minor.
BSD0825
Controller card is disabled.

Action: Enable the card before performing the test.
Severity: Minor.
BSD0826
SNMP trap: Yes
The DSL is disabled.

Action: Enable it before performing the test.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 182 of 2360

BSD0827
Message could not be sent to the MISP application.

Action: Check the MISP and the application status.
Severity: Minor.
BSD0828
SNMP trap: Yes
Message could not be sent to the MISP because the MISP express output
buffer is not available.
Action:
Severity: Minor.
BSD0829
SNMP trap: Yes
Cannot do loopback on a non-BRI line card.

Action:
Severity: Minor.
BSD0830
SNMP trap: Yes
The loop back test can only be performed between an MISP card and one of
the BRI line cards assigned to it.
Action:
Severity: Minor.
BSD0831
SNMP trap: Yes
MISP does not respond; use XSTP command to terminate test. The Network
card may have no recollection of the command, or the card was not able to
communicate with the Meridian 1.
Action:
Severity: Minor.
BSD0832
SNMP trap: Yes
Suspended tags refer to test cases where the Network card did not
acknowledge the reception of the test message.
Action: Use the command XSTP to free the test case.
Severity: Minor.
BSD0833
SNMP trap: Yes
Not able to send message to the MISP.

Action: Check the MISP status.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 183 of 2360

BSD0834
Line cards not defined at the specified DSL.

Action:
Severity: Minor.
BSD0835
SNMP trap: Yes
All DSLs must be in disabled state.

Action:
Severity: Minor.
BSD0836
SNMP trap: Yes
The network loop is not an MISP card.

Action:
Severity: Minor.
BSD0837
SNMP trap: Yes
Test case number does not match its test data.

Action:
Severity: Minor.
BSD0838
SNMP trap: Yes
Command not applicable to Network/DTR card.

Action:
Severity: Minor.
BSD0839
SNMP trap: Yes
DSInvalid L TN used or already in test.

Action:
Severity: Minor.
BSD0840
SNMP trap: Yes
MPH application is not defined in this MISP loop.

Action:
Severity: Minor.
BSD0841
SNMP trap: Yes
LBTY entered does not match with GEN TYPE.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 184 of 2360

BSD0843
NWIF is not defined.

Action:
Severity: Minor.
BSD0844
SNMP trap: Yes
State of IF for MPH application is not in MDIS EQUIP.

Action:
Severity: Minor.
BSD0845
SNMP trap: Yes
SNMP trap: Yes
Invalid MCU TN.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 185 of 2360
BUG: Software Error Monitor

The Software Error Monitor program monitors call processing continuously.
When the call processing software detects information that is not in the correct
format, or when invalid information is detected, a BUG message is output.
Hardware problems are generally reported with ERR messages.
BUG messages generally appear in the following format:
BUGxxx <return address stack>
Some messages contain a second line with additional data, as listed below. In
listing parameters, the symbol *(ptr) is used to abbreviate common lists:
(crptr)
CRWORD 0:ptr (progress marks and types)
ORIGTN:ptr
TERTN:ptr
QUEUEIN:ptr
Messages
BUG0001
Global procedure missing. Procedure NOGLOBAL

Action:
Severity: Minor.
BUG0004
SNMP trap: Yes
pd EUROMCID_HANDLER has been called with an invalid source parameter.

Severity: Minor.
BUG0005
SNMP trap: Yes
Invalid ORIGTN in 128 ms timing list. *(CRPTR). Procedure WORKSHED

Action:
Severity: Minor.
BUG0006
SNMP trap: Yes
pd MCID_ACT_REQ incorrect msgcr pointer.

Severity: Minor.
SNMP trap: Yes
System Messages
Page 186 of 2360

BUG0007
Call Register (CR) does not point back to trunk Block. *(ACTIVEPTR)
Procedure WORKSHED
Action:
Severity: Minor.
BUG0008
SNMP trap: Yes
Input Message from an invalid card type. CARDTYPE, TN Procedure

WORKSHED
Action:
Severity: Minor.
BUG0009
SNMP trap: Yes
pd MCID-ACT-REQ incorrect state of the EUROISDN trk over which MCID is

attempted, must be established or disconnected.
Severity: Minor.
BUG0010
SNMP trap: Yes
Invalid TERTN in 128 ms timing list. *(CRPTR) Procedure WORKSHED

Action:
Severity: Minor.
BUG0011
SNMP trap: Yes
CR linked in RING_QUEUE; timer value not allowed. Procedure WORKSHED

Action:
Severity: Minor.
BUG0012
SNMP trap: No
This BUG message is output from patches 529 and 752 and is for debugging
purpose only. Ignore this message.
Action:
Severity: Minor.
BUG0013
SNMP trap: No
This BUG message is output from patches 537, 562, 574, 653, 731, and 752
and is for debugging purpose only. Ignore this message
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 187 of 2360

BUG0014
pd MCID_ACT_REQ could not get a call register to handle MCID signaling

(MCID_PROT_CR).
Severity: Minor.
BUG0015
SNMP trap: Yes
Trying to find a path to an unequipped loop. ULPXPTR or ULPYPTR = NIL.

Procedure FINDONEWAY. Output: TN1, TN2 (unpacked format).
Action:
Severity: Minor.
BUG0016
SNMP trap: Yes
pd MCID_ACT_REQ could not link the protocol cr to the msg cr.

Severity: Minor.
BUG0017
SNMP trap: Yes
pd MCID_SND_FAC could not get a call register to build the facility msg.
Severity: Minor.
BUG0018
SNMP trap: Yes
pd MCID_RCV_RES on reception of the result to an MCID request culd not

find the MCID protocol cr.
Severity: Minor.
BUG0019
SNMP trap: Yes
pd MCID_RCV_RES checks on apdu received unsuccessfully.

Severity: Minor.
BUG0020
SNMP trap: Yes
Ujunctor group pointer = NIL. Two given loops on different groups. LOOP1,
LOOP2 Procedure PATHFIND
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 188 of 2360

BUG0021
pd MCID_RCV_RES invalid value of rose component, must be ret-res, reject,

ret-err.
Severity: Minor.
BUG0022
SNMP trap: Yes
pd MCID_RET_ERR invalid tag for error value.

Severity: Minor.
BUG0023
SNMP trap: Yes
BLOCK_PTR could not be found in specified queue. Procedure PATHFIND

Action:
Severity: Minor.
BUG0024
SNMP trap: No
BLOCK_PTR could not be found in specified queue. Procedure PATHFIND

Action:
Severity: Minor.
BUG0025
SNMP trap: No
Ujunctor group pointer = NIL. Two given loops on different groups. LOOP1,
LOOP2 Procedure PATHIDLE
Action:
Severity: Minor.
BUG0026
SNMP trap: Yes
pd MCID_RET_ERR invalid value of the error for MCID service.

Severity: Minor.
BUG0027
SNMP trap: Yes
Invalid entry in Index Table.

Action:
Severity: Major.
BUG0028
SNMP trap: No
pd MCID_RCV_MSG unexpected msg sent during MCID process.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 189 of 2360

BUG0029
pd MCID_SND_MSG unexpected message sent during MCID process.

Severity: Minor.
BUG0030
SNMP trap: Yes
Trying to idle path for nonexistent/unequipped loop or slot zero. TN1, TN2
(unpacked format), SLOT Procedure PATHIDLE
Action:
Severity: Minor.
BUG0031
SNMP trap: Yes
pd MCID_IDLE_CR the MCID protocol call register is invalid.

Severity: Minor.
BUG0032
SNMP trap: Yes
NXT_TTR_THIS_GRP is corrupted. Value is reset.

:TTR_GROUP, NXT_TTR_THIS_GRP [TTR_GROUP]
Severity: Minor.
BUG0033
SNMP trap: Yes
Physical TN and Virtual TN pointer mapping Invalid.

Action:
Severity: Major.
BUG0035
SNMP trap: No
One of the two loops is unequipped. ULP_PTR = NIL. LOOP1, LOOP2

Procedure SETONEWAY
Action:
Severity: Minor.
BUG0040
SNMP trap: Yes
One of the loops involved in the connection is: a) not equipped (ULP_PTR =
NIL b) not a TERM_LOOP or CONF_LOOP
c) not enabled d) slot is zero LOOP1, LOOP2, SLOT Procedure
NTWKMEMORY
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 190 of 2360

BUG0050
Unable to find and remove the Call Register. Procedure FINDREMOVE

Action:
Severity: Minor.
BUG0055
SNMP trap: No
TERMINAL does not match either TN in Call Register. Disconnecting TN,

ORIGTN, TERTN, ORIGPM (TN in packed format) Procedure DISCONNECT
Action:
Severity: Minor.
BUG0056
SNMP trap: No
Call in .RAN_WAITING with non-zero TERTN. Procedure DISCONNECT

Action:
Severity: Minor.
BUG0057
SNMP trap: No
Attempt to disconnect terminal from nonexistent or disabled conference loop.

Procedure DISCONNECT
Action:
Severity: Minor.
BUG0058
SNMP trap: Yes
Attempt to set up simple call between nonexistent or disabled terminals.

Action:
Severity: Minor.
BUG0059
SNMP trap: Yes
Attempt to disconnect nonexistent or disabled trunks from conference.

Action:
Severity: Minor.
BUG0060
SNMP trap: Yes
TNTRANS fails. Procedure LINKCONF

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 191 of 2360

BUG0065
Message to a loop where looptype is not equal to TERM_LOOP TN (packed),

LOOPTYPE Procedure PERIPH_MSG
Action:
Severity: Minor.
BUG0070
SNMP trap: No
Timing lost with call in .OUTPULSING state. ORIGTN, DIGITLOAD,

DIGITUNLOAD, CRDIGITS(0) CRDIGITS(3) (TN in packed format, digits in
packed hex). Procedure DIGPROC
Action:
Severity: Minor.
BUG0071
SNMP trap: No
Illegal intercept condition. Procedure DIGPROC

Action:
Severity: Minor.
BUG0072
SNMP trap: Yes
Failed to set customer pointers. Procedure LIN500

Action:
Severity: Minor.
BUG0073
SNMP trap: No
Invalid call to procedure TRK_ACCESS. Procedure LIN500

Action:
Severity: Minor.
BUG0074
SNMP trap: No
500-type set on-hook but still engaged in PBX half disconnect timing.
Procedure LIN500
Action:
Severity: Minor.
BUG0075
SNMP trap: No
PBX line has been software busy but PM = .IDLE. Cleared now. TERMINAL,
*(CRPTR) Procedure LIN500
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 192 of 2360

BUG0079
NWK_DROP_BACK flag is cleared.

Action:
Severity: Info.
BUG0080
SNMP trap: Yes
Invalid switch hook state in .READY state. (Should be off-hook TERMINAL

(packed format), *(CRPTR) Procedure LIN500.
Action:
Severity: Info.
BUG0081
SNMP trap: Yes
The number of Survivable Cabinets configured in the system has reached the
limit.
Action:
Severity: Major.
SNMP trap: Yes
BUG0082 yyyyyyyy A message has been received from a DCS set with a corrupt data block.
yyyyyyyy is the packed TN of the offending DCS set. An attach message has
been received for a DCS set. The software uses home-DN template data to
store the set location information, but the home_DN template data for this set
is missing. The attach message has been ignored. The DCS set yyyyyyyy will
not be able to receive calls to the home DN when at a visitor site.
Action: Remove the data for the telephone and recreate it.
Severity: Minor.
BUG0083
SNMP trap: Yes
Quotient out-of-range in the procedure BCH_TO_TN.

Action:
Severity: Minor.
BUG0084
SNMP trap: Yes
Data corruption in data block BFS_TN_MON.

Severity: Major.
BUG0085
SNMP trap: Yes
Invalid switch hook state in .RINGING state. (should be off-hook) TERMINAL

(packed format), *(CRPTR) Procedure LIN500
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 193 of 2360

BUG0086
Corrupted BFS_TN_MON.
Action: Perform a manual INI to rebuild the BFS_TN_MON or contact your
technical support group.
Severity: Critical.
BUG0087
SNMP trap: Yes
MNABIT is set before calling NWKMEMORIES.

Action:
Severity: Info.
BUG0088
SNMP trap: Yes
The DCS set is in a locked-out state.

Action:
Severity: Minor.
BUG0089
SNMP trap: Yes
VNS has entered a recursive loop which would result in stack overflow.
REQUEST_OUTPUT calls VNS to send a message on the VNS bearer.
Eventually VNS calls REQUEST_OUTPUT to actually send the message. But
every time the channel number passed makes it look as it a VNS D-channel
message is being sent. Hence it tries to send another message on the VNS
bearer and again the same problem happens. This goes on recursively until
the stack overflow occurs. To prevent INI, the recursive loop has been broken
( or stopped).
The following values are printed along with the BUG:
Timestamp
ORIGN, TERTN
VNS_TER_INDEX
MSGCRPTR
MSG_CRPTR, VNS_INDEX
Action: Contact your technical support group. Report the problem and advise
them of the parameters output.
Severity: Major.
BUG0090
SNMP trap: Yes
TNTRANS fails. TN (unpacked format) Procedure CTICHECK

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 194 of 2360

BUG0091
Wireless Visitors ISM counter corruption encountered. Counter is reset to 0.

Severity: Info.
BUG0092 C R
SNMP trap: Yes
The customer number (CNO) passed into Procedure $SET_ROUTE_PTRS is

out of range.
C = Customer Number
R=Route Number
Action: Investigate possible data corruption.
Severity: Minor.
BUG0093
SNMP trap: Yes
The code for executing the CLKC card related command in Overlay 39 or 60
received a failure return code from SET_MSDLMISP_PTR.
Action: Check for CLKC database corruption in MSDL related structure.
Severity: Minor.
BUG0094
SNMP trap: Yes
Either Overlay 39, or Overlay 60, is waiting for a message from the CLKC, but
the response pending field suddenly clears. The response pending field
indicates that a software entity is waiting for a message from the MSDL/MISP
interface which is used by the CLKC card.
Action:
Severity: Minor.
BUG0095
SNMP trap: Yes
XFER lamp winking but no hold situation. TERMINAL, *(CPRTR) Procedure

BCS/CALL_TRANSFER
Action:
Severity: Minor.
BUG0096
SNMP trap: Yes
CONF_HAS_WTD_MEM - GLOBAL BCS1; conference pointer nil or not a

conference group. Procedure BCS/CALL_TRANSFER
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 195 of 2360

BUG0097
Buffer did not empty.

Action:
Severity: Minor.
BUG0098 C R
SNMP trap: Yes
The route number (RNO) passed into Procedure $SET_ROUTE_PTRS is out

of range.
C = Customer Number
R = Route Number
Severity: Minor.
BUG0099
SNMP trap: Yes
Invalid channel number input for converting into slotmap.

Action:
Severity: Info.
BUG0100
SNMP trap: Yes
TNTRANS fails. *(CRPTR) Procedure BCS/CALL_TRANSFER

Action:
Severity: Minor.
BUG0101
SNMP trap: Yes
ACTIVECR (PBX case) or KEYLINK (SL-1 case) points to an address not in

CR range. Station TN, SSDKEY, KEYLINK, (packed) Procedure
GET_KEYLINK
Action:
Severity: Minor.
BUG0102
SNMP trap: Yes
User has been registered at Branch Office for more than 2 weeks.
Action: Force to disconnect and redirect to Main Office.
Severity: Info.
BUG0103
SNMP trap: No
Internet Telephones have been serviced at the Branch Office in survival mode
beyond the licensed period.
Action: Use Branch Office config to redirect the sets to the Main Office or do a
software installation.
Severity: Info.
SNMP trap: Yes
System Messages
Page 196 of 2360

BUG0104
A Major software bug was encountered. A description of the event is contained

in the error
message.
Action: A manual intervention of the software upgrade process may be required.
Contact your
Severity: Major.
BUG0105
SNMP trap: Yes
Double timeslot problem prevented. TN is printed. Procedure CLEAR_NTWK

Action:
Severity: Minor.
BUG0109
SNMP trap: Yes
Action for RMK could not be identified. Procedure INITCR

Action:
Severity: Minor.
BUG0110
SNMP trap: Yes
TERMINAL does not match ORIG_ITEM. TERMINAL Procedure INITCR

Action:
Severity: Minor.
BUG0111
SNMP trap: No
Call Register is not in range. Procedure IDLECR

Action:
Severity: Minor.
BUG0112
SNMP trap: Yes
A software bug was encountered. The remote upgrade feature has recovered
from the problem.
Severity: Info.
BUG0113
SNMP trap: Yes
Unit type configured on PBX card is not defined, due to possible corruption.
Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 197 of 2360

BUG0114
DCH number is out of range.

Action:
Severity: Critical.
BUG0115
SNMP trap: Yes
TERMINAL does not match DN or TN in Call Register. TERMINAL (packed

format), *(CRPTR) Procedure LIN500 / DNKEY / FORCEDISCONNECT /
DISCONNECT
Action:
Severity: Minor.
BUG0116
SNMP trap: Yes
AML: Could not register <mod_name>

Severity: Major.
BUG0117
SNMP trap: Yes
AML: Could not send to Comm Manager.

Severity: Major.
BUG0118
SNMP trap: Yes
AML: trying to send null message.

Severity: Major.
BUG0119
SNMP trap: Yes
AML: Null message received.

Severity: Major.
BUG0120
SNMP trap: Yes
ACTIVECR points to an idle CR or to a CR with no matching TN. Procedure

TRUNKS/COTRUNK
Action:
Severity: Minor.
BUG0121
SNMP trap: No
AML: Could not send to amlMsgQId.

Action: Contact your technical support group
Severity: Major.
SNMP trap: Yes
System Messages
Page 198 of 2360

BUG0122
AML: Could not create amlAppSem

Severity: Major.
BUG0123
SNMP trap: Yes
AML: Could not create amlMsgQId.

Severity: Major.
BUG0124
SNMP trap: Yes
AML: Could not re-create amlMsgQId.

Severity: Major.
BUG0125
SNMP trap: Yes
Off-Hook from a ground start trunk in half disconnected state. Procedure

TRUNKS/CO_INCOMING
Action:
Severity: Minor.
BUG0126
SNMP trap: No
AML: Error deleting amlMsgQId.

Severity: Major.
BUG0127
SNMP trap: Yes
AML: Could not send update health message to the other side.
Severity: Major.
BUG0128
SNMP trap: Yes
AML: Could not send add application message to the inactive side.
Severity: Major.
BUG0129
SNMP trap: Yes
AML: Could not send delete application message to the inactive side.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 199 of 2360

BUG0130

TRUNKS/EM_DX_TRUNK
Action:
Severity: Minor.
BUG0131
SNMP trap: No
On-hook from AUTOVON trunk in AWAIT-REPLY state. Procedure

TRUNKS/EM_DX_TRUNK.
Action:
Severity: Minor.
BUG0132
SNMP trap: No
AML: Wrong message received of type <type>

Severity: Major.
BUG0133
SNMP trap: Yes
AML: Failed to init task.

Severity: Major.
BUG0134
SNMP trap: Yes
AML: Failed to recover task.

Severity: Major.
BUG0135
SNMP trap: Yes

TRUNKS/LOOPSIG_TRUNK
Action:
Severity: Minor.
BUG0136
SNMP trap: No
AML: Task spawn failed.

Severity: Major.
SNMP trap: Yes
System Messages
Page 200 of 2360

BUG0137
STATION_INDEX for single appearance 500 set should not exceed 1.

Procedure: SC_FIX_CR
Output: STATION_INDEX
Action: Save a hard copy of the BUG printout. Contact your technical support
group.
Severity: Info.
BUG0140
SNMP trap: Yes
Invalid PM state (.IDLE) Procedure TRUNKS/TIE_INCOMING

Action:
Severity: Minor.
BUG0145
SNMP trap: No
Off-hook from TIE trunk in half disconnected state. Procedure

TRUNKS/TIE_INCOMING
Action:
Severity: Minor.
BUG0146
SNMP trap: No
A IP SSD message <word0> <word1> <word2> <word3>, which indicates

RTC (Real Time Clock) failure, was sent to SL1 task.
Action:
Severity: Minor.
BUG0147
SNMP trap: Yes
LCS: Failed to send message, input parameter pointer is null.

Severity: Major.
BUG0148
SNMP trap: Yes
LCS:Failed to send message, destination is not LCS, dest=%d (where %d is

enum of destination task name).
Severity: Major.
BUG0149
SNMP trap: Yes
DR: Disk synchronization has failed due to an unknown message [type =

0x%x] received.
Action: Contact your technical support
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 201 of 2360

BUG0150
Off-Hook from TIE trunk in .READY state. Procedure

TRUNKS/TIE_INCOMING
Action:
Severity: Minor.
BUG0151
SNMP trap: No
PDT: Task (task name) restart error, tid, errno.

Severity: Major.
BUG0152
SNMP trap: Yes
PDT: Task (task name) resume error, tid, errno.

Severity: Major.
BUG0153
SNMP trap: Yes
PDT: Task (task name) suspend error, tid, errno.

Severity: Major.
BUG0154
SNMP trap: Yes
SEG: invalid size [x] requested where x is the size requested

Severity: Minor.
BUG0155
SNMP trap: Yes
Invalid CO trunk timeout. Procedure INCOMING_TRUNK_TO

Action:
Severity: Minor.
BUG0156
SNMP trap: No
SEG: invalid block to be freed : ptr [x], header ptr [y] where x is the pointer to
the block y is the header pointer to the block
Severity: Minor.
SNMP trap: Yes
System Messages
Page 202 of 2360

BUG0157
SEG: invalid block to be freed : ptr [x], header ptr [y] magic [z] where x is the
pointer to the block y is the header pointer to the block z is the magic cookie
for the block
Severity: Minor.
BUG0158
SNMP trap: Yes
SEG: Function [x] called where x is the name of the function

Action: None
Severity: Info.
BUG0159
SNMP trap: Yes
SEG: no free space to be allocated

Severity: Major.
BUG0160
SNMP trap: Yes
Invalid trunk timeout. Procedure OUTGOING_TRUNK_TO

Action:
Severity: Minor.
BUG0162
SNMP trap: No
SEG: semMCreate failed during initialization

Severity: Major.
BUG0163
SNMP trap: Yes
SEG: Failed to get vm state at page addr [a] for addr [b] where a is the page
boundary address b is the memory address
Action: If messages persist, contact your technical support group.
Severity: Minor.
BUG0164
SNMP trap: Yes
SEG: Failed to set vm state at page addr [a] for addr [b] where a is the page
boundary address b is the memory address
Action: If messages persist, contact your technical support group.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 203 of 2360

BUG0165
ATTNCUSTNO:CRPTR and CUSTNO:PLORIGPTR do not match.

ATTNCUSTNO, CUSTNO, TN (packed format), *(CRPTR) Procedure
DIGPROC
Action:
Severity: Minor.
BUG0166
SNMP trap: Yes
SET_ROUTE_PTRS fail. TN, ROUTE NUMBER, CUSTOMER NUMBER.

Procedure DIGPROC
Action:
Severity: Minor.
BUG0167
SNMP trap: Yes
TEMP PATH; outpulsing trunk TN invalid. Procedure DIGPROC

Action:
Severity: Minor.
BUG0168
SNMP trap: No
A minor software bug was encountered. A description of the event is contained

in the error message.
Action: The remote upgrade feature is trying to recover from the event. If the
event repeats itself, a manual intervention of the remote upgrade process may be
required. Contact your technical support group.
Severity:
BUG0169
SNMP trap: No
SWO: failed to initialize tSwoTask, errno [err].

Action: Contact your Technical Support
Severity: Critical.
BUG0170
SNMP trap: Yes
KEYLINK (SL-1) or ACTIVECR (PBX) = NIL when another set with same DN
is active in conference. TN (unpacked format), DN (packed hex format),
*(CRPTR) Procedure DISCONNECT/TNACTIVTEST
Action:
Severity: Minor.
BUG0171
SNMP trap: Yes
SWO: Failed to activate SWO task

Action: Contact your Technical Support.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 204 of 2360

BUG0172
SWO: Failed to send to swoMsgQId, errno [err].

Severity: Critical.
BUG0173
SNMP trap: Yes
SWO: Failed to create swoMsgQId, errno [er].

Severity: Critical.
BUG0174
SNMP trap: Yes
SWO: failed to register with Communication Manager.

Action: Contact your Technical Support
Severity: Critical.
BUG0175
SNMP trap: Yes
DN of a station trying to restore a held call does not match DN of

ORIGTN:CRPTR or TERTN:CRPTR. TN (unpacked hex format), DN (packed
hex format), *(CRPTR) Procedure RESTORE
Action:
Severity: Minor.
BUG0176
SNMP trap: Yes
SWO: failed to receive from swoMsgQId [msgQID], errno[err].

Severity: Critical.
BUG0177
SNMP trap: Yes
SWO: failed to stop all HI periodic jobs.

Action:
Severity: Minor.
BUG0178
SNMP trap: Yes
SWO: failed to start all HI periodic jobs.

Action:
Severity: Minor.
BUG0179
SNMP trap: Yes
SWO: failed to send to lcsMsgQId.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 205 of 2360

BUG0180
Termination on original station fails after Call Forward-No Answer is denied

due to blocking. *(CRPTR) Procedure CALLFW_NA
Action:
Severity: Minor.
BUG0181
SNMP trap: No
Termination on call forwarded station fails after Call Forward-No Answer.

*(CRPTR) Procedure CALLFW_NA
Action:
Severity: Minor.
BUG0182
SNMP trap: Yes
SWO: Received unknown message of type %d.

Severity: Critical.
BUG0183
SNMP trap: Yes
LCS: Can't stop SL1 task.

Severity: Critical.
BUG0184
SNMP trap: Yes
IPM: Failed to assign the HSP IP address to fei1 in ipmPostSwo.

Severity: Critical.
BUG0185
SNMP trap: Yes
ORIGPM is not .RINGING or .BUSY or .REORDER after doing Call

Forward-No Answer Dialed DN, CFNA_DN (DNs in packed hex format),
*(CRPTR). Procedure: DISC_TER
Action:
Severity: Minor.
BUG0186
SNMP trap: Yes
SWO: Stop And Copy failed.

Action: Check the HSP
Severity: Critical.
SNMP trap: Yes
System Messages
Page 206 of 2360

BUG0187
LCS: Can't proceed with graceful switchover. Can't stop SL1 task
Severity: Critical.
BUG0188
SNMP trap: Yes
LCS:Graceful switchover unsuccessful. Inactive side failed to receive the

SWO message.
Severity: Critical.
BUG0189
SNMP trap: Yes
LCS: Graceful switchover unsuccessful. Stop&Copy failed and LcsSCFail

message lost
Severity: Critical.
BUG0190
SNMP trap: Yes
Call Register out-of-range. *(CRPTR) Procedures LINK & UNLINK

Action:
Severity: Minor.
BUG0191
SNMP trap: Yes
Attempted to link Lockout Call Register into a queue. No Call Register was
linked into any queue.
Action:
Severity: Minor.
BUG0192
SNMP trap: Yes
CM: HSP init failed.

Severity: Critical.
BUG0193
SNMP trap: Yes
Failed to start task [%s], errno: [err]

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 207 of 2360

BUG0194
Attempt to remove CR from CDR queue while queue is protected. Procedure

REMOVE
Action:
Severity: Minor.
BUG0195
SNMP trap: Yes
BLOCK_PTR could not be found in specified queue. Procedure REMOVE

Action:
Severity: Minor.
BUG0196
SNMP trap: Yes
Call Register is out-of-range. {CRPTR} {TERMINAL} {ORIGITEM} {TERITEM}

Procedure REMOVECRPTR
Action:
Severity: Minor.
BUG0197
SNMP trap: Yes
Sending to %s [msgQID] failed, errno: [err]

Severity: Critical.
BUG0198
SNMP trap: Yes
CM: Secondary server ether socket bind fail

Severity: Critical.
BUG0199
SNMP trap: Yes
Failed to create %s message queue, errno: [err]

Severity: Critical.
BUG0200
SNMP trap: Yes
Attempt to store more than 11 parms in a print register. Procedure

STORE_PARM
Action:
Severity: Minor.
BUG0201
SNMP trap: Yes
Attempt to store parm into an empty print queue. Procedure STORE_PARM

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 208 of 2360

BUG0202
Failed to delete %s [semaphoreID] semaphore, errno:[err].

Severity: Critical.
BUG0203
SNMP trap: Yes
CM: Secondary server socket receive Error.

Severity: Critical.
BUG0204
SNMP trap: Yes
cmPriProcessMsg: CM dispatch local message fail, Destination is [%d]

Severity: Critical.
BUG0206
SNMP trap: Yes
Failed to delete %s [0x%x], errno: [err]

Severity: Critical.
BUG0207
SNMP trap: Yes
CM: Can't create cmSockClntSem semaphore

Severity: Critical.
BUG0208
SNMP trap: Yes
CM: HSP Server init failed

Severity: Critical.
BUG0209
SNMP trap: Yes
CM: HSP Server accept failed.

Severity: Critical.
BUG0210
SNMP trap: Yes
No Call Register available. Procedure DIGITKEY

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 209 of 2360

BUG0211
Idle station but active CR in line card. TN (packed format) Procedure

DIGITKEY
Action:
Severity: Minor.
BUG0212
SNMP trap: No
CM: Create %s socket failed.

Severity: Critical.
BUG0213
SNMP trap: Yes
CM: setsockopt error

Severity: Critical.
BUG0214
SNMP trap: Yes
Receive from %s [0x%x] failed, errno [err]

Severity: Critical.
BUG0215
SNMP trap: Yes
SRC connection of attendant not jointly held. TN (packed format) Procedure

LOOPKEY
Action:
Severity: Minor.
BUG0216
SNMP trap: No
CM: Can't Get remote IP.

Severity: Critical.
BUG0217
SNMP trap: Yes
CM: Can't Get local current IP

Severity: Critical.
BUG0218
SNMP trap: Yes
CM: Can't Get remote Default IP

Severity: Critical.
SNMP trap: Yes
System Messages
Page 210 of 2360

BUG0219
CM: Secondary client can't Send to [%s]:[%d]

Severity: Critical.
BUG0220
SNMP trap: Yes
Loop lamp lit but active loop not set to correct loop number TN, LOOP,
ACTIVELOOP Procedure LOOPKEY
Action:
Severity: Minor.
BUG0221
SNMP trap: No
Queue time out-of-range (traffic statistics problem). Queue Delay Time, Traffic
Time, Queue Insert Time, Current Time-of-Day. Procedure LOOPKEY
Action:
Severity: Minor.
BUG0222
SNMP trap: Yes
CM: Secondary client received bad message.

Severity: Critical.
BUG0223
SNMP trap: Yes
CPM: Invalid usage of the cmPrimarySend function

Severity: Critical.
BUG0224
SNMP trap: Yes
CM: Detected message that is larger than primary connection's MTU

Severity: Critical.
BUG0225
SNMP trap: Yes
More than the expected two party conference. NUMBER OF CONFEREES

Procedure RLSKEY
Action:
Severity: Minor.
BUG0226
SNMP trap: Yes
Detected invalid message destination on primary connection

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 211 of 2360

BUG0227
cpmInit: deleting cpm task tCpmS

Severity: Critical.
BUG0228
SNMP trap: Yes
malloc failed
Severity: Critical.
BUG0230
SNMP trap: Yes
Invalid TN. TN Procedure RLSKEY

Severity: Minor.
BUG0234
SNMP trap: Yes
HIREM: Data of object %p, %d bytes, is larger the the maximum size %d
HIREM: Invalid msg option passed in hiRemSendCreateObj.
Severity: Critical.
BUG0235
SNMP trap: Yes
Invalid DEST lamp state. STATE Procedure RLSKEY

Action:
Severity: Minor.
BUG0236
SNMP trap: Yes
CM: Can't connect to the other side. Create client socket failed.
Severity: Critical.
BUG0237
SNMP trap: Yes
CM: Shutdown server timeout.

Severity: Critical.
BUG0238
SNMP trap: Yes
CM: Can't write to the HSP. Client socket error.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 212 of 2360

BUG0239
CM: Shutdown client timeout.

Severity: Critical.
BUG0240
SNMP trap: Yes
Invalid SRC lamp state. STATE Procedure RLSKEY

Action:
Severity: Minor.
BUG0241
SNMP trap: No
A loop on the attendant console (TERMINAL) is being idled but the SRC link
is NON-NIL.
Action: See action for BUG242. *(CRPTR) TERMINAL Procedure RLSKEY.
Severity: Minor.
BUG0242
SNMP trap: Yes
A loop on the attendant console (TERMINAL) is being idled but the DEST link
is NON-NIL. *(CRPTR) TERMINAL Procedure RLSKEY
Action: In the case of BUG241 and BUG242, determine, if possible, the type of
call being processed at the time the message appeared. Determine also the
actions of the TN from (*CRPTR). It is possible that Call registers could be lost.
Repeating BUG messages of the type above must be followed by running AUDIT.
Severity: Minor.
BUG0243
SNMP trap: Yes
CM: Can't init HSP Server. Create server socket failed with errno [err].Where
[err]: error number
Severity: Critical.
BUG0244
SNMP trap: Yes
CM: Can't init HSP Server. Bind server socket failed with errno [err].Where
[err]: error number
Severity: Critical.
BUG0245
SNMP trap: Yes
Night lamp is lit but position busy lamp is not. TN Procedure NITEKEY
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 213 of 2360

BUG0246
CM: Can't init HSP Server. Create cmSockSvrSem semaphore failed.

Severity: Critical.
BUG0247
SNMP trap: Yes
CM: Can't init HSP Server. Create cmSockSvrSem semaphore failed.

Severity: Critical.
BUG0248
SNMP trap: Yes
CM: HSP Server accept returned error, errno [err]Where [err]: error number
Severity: Critical.
BUG0249
SNMP trap: Yes
Observe is not allowed because OUSA CLS is configured and SCL associated
with the OBV key does not exist.
Action:
Severity: Critical.
BUG0250
SNMP trap: Yes
No call of that type in attn queue but queue count states otherwise. ICITYPE,
QUEUE SIZE Procedure ICIKEY
Action:
Severity: Minor.
BUG0251
SNMP trap: Yes
PCA Phones ISM counter corruption encountered.

Counter is reset to 0
Action:
Severity: Info.
BUG0252
SNMP trap: Yes
TRK_UNIT expected in MFC_COMPLETE

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 214 of 2360

BUG0253
Utility procedure called with invalid required data. Parameters: global number
and optional debugging parameters.
Action: Report the problem text to the operating company.
Severity: Minor.
BUG0254
SNMP trap: Yes
Unknown bandwidth policy. Possible data corruption.

Action: Check zone table content in OVL117.
Severity: Info.
BUG0255
SNMP trap: Yes
Flash recall but unit type is not .PBX TN, TYPE Procedure ICIKEY
Action:
Severity: Minor.
BUG0256
SNMP trap: No
Call register is invalid in IDLECR.

Parameters: call register pointer
Action: Report the problem text to the operating company.
Severity: Minor.
BUG0257
SNMP trap: Yes
Unable to map phantom loop to a real loop. Procedure FINDONEWAY.

Output: TNX, TNY (unpacked format), *(CRPTR).
Action: Please contact technical support group. Go to the PDT and turn
enhanced BUG CR printing option on in order to get more detailed BUG output (if
the problem occurs again).
Severity: Major.
BUG0258
SNMP trap: Yes
Failed to spawn the tQoSIP task. errno [errno].

Action: Contact your local support group, the system cannot monitor QoS
violation events.
Severity: Major.
BUG0260
SNMP trap: Yes
Call Register is not linked to attendant. *(CRPTR) Procedure ONHOOK

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 215 of 2360

BUG0261
Message exceeds max msg size of [expected size], size detected [actual size].
violation events.
Severity: Minor.
BUG0262
SNMP trap: Yes
qosIPMsgQ message queue does not exist, ending the tQoSIP task.
violation events.
Severity: Major.
BUG0263
SNMP trap: Yes
Unexpected message detected message number [msgNum]

Action:
Severity: Info.
BUG0265
SNMP trap: Yes
Invalid destination lamp state. STATE Procedure ONHOOK

Action:
Severity: Minor.
BUG0266
SNMP trap: No
ACTIVECR points to a call register that is in the IDLE queue.

Action: Please contact technical support group.
Severity: Major.
BUG0267
SNMP trap: Yes
Protected pointer (DNPTR) is out of protected memory range.

Procedure DNTRANS2.
Output: DN (packed format: low word, hi word), lower bound of protected
store,
DNPTR, upper bound of protected store, customer number.
Severity: Major.
BUG0268
SNMP trap: Yes
Unit type is incorrect.

Output: Protected line pointer, unit type
Severity: Major.
SNMP trap: Yes
System Messages
Page 216 of 2360

BUG0269
IP Peer SIP Trunks ISM counter corruption encountered.

Action: Contact your Nortel Networks Technical Support Group.
Severity: Minor.
BUG0270
SNMP trap: Yes
Terminal does not match ORIG_ITEM.TERMINAL, *(CRPTR). Procedure:

ONHOOK
Action:
Severity: Minor.
BUG0271
SNMP trap: Yes
TERTN:CRPTR doesn't match with the Network timeslot Memory.

Action:
Severity: Info.
BUG0272
SNMP trap: No
A BCS TN block is expected. Procedure SET_IS_2D_BUSY.

Output: packed TN and unit type for dialed N block, packed TN and unit type
for terminating TN block, TERTN:CRPTR.
Action:
Severity: Minor.
BUG0273
SNMP trap: Yes
Mis Configured DSC. Location A and Location B has same distance steering
code towards each other. The configuration is wrong (Cause Ping Pong).
Please change the configuration.
Action:
Severity: Major.
BUG0274
SNMP trap: No
Call register to be idled is found in ACD queue.

Action:
Severity: Minor.
BUG0275
SNMP trap: Yes
Invalid lamp states. STATE Procedure OFFHOOK

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 217 of 2360

BUG0276
Call register to be idled is still linked to IVR CR.

Action:
Severity: Info.
BUG0277
SNMP trap: Yes
NCFW DN is a combination of (LOC+ACD DN) or (ACOD+ACD DN).

Action:
Severity: Minor.
BUG0278
SNMP trap: Yes
IP Peer H.323 Trunks counter corruption encountered. Counter is reset to

zero.
Severity: Info.
BUG0279
SNMP trap: Yes
A non idled DTR is found.

Severity: Major.
BUG0280
SNMP trap: Yes
Connection does not correspond to lamp state. STATE, *(CRPTR).

Procedure: ATTNHOLDKEY
Action:
Severity: Minor.
BUG0281
SNMP trap: No
Timing block pointer is out of range. Parameters: block pointer, queue, timer1,
timer2 (queue and timers valid for errors in LINK)
Action: Report problem to the operating company.
Severity: Major.
BUG0282
SNMP trap: Yes
Call register has an invalid block type. Parameters: call register pointer, block
type, queue.
Severity: Major.
SNMP trap: Yes
System Messages
Page 218 of 2360

BUG0283
Block pointer is marked as a call register but is not in range. Parameters: block
pointer, 7 words of the block header
Severity: Major.
BUG0284
SNMP trap: Yes
Timing block not marked as being in a queue contains invalid queue pointers.
Parameters: block pointer, block type, forward link, backwards link.
Severity: Major.
BUG0285
SNMP trap: Yes
Invalid destination connection. (CRPTR) Procedure ATTNHOLDKEY

Action:
Severity: Minor.
BUG0286
SNMP trap: No
The attendant-reserved slot of a held call and the slot actually used by the
station do not match. RESERVED SLOT on attendant console is updated to
value TALKSLOT. ORIGTN, TERTN, TALKSLOT, RESERVED SLOT.
Procedure ATTNHOLDKEY
Action:
Severity: Minor.
BUG0287
SNMP trap: Yes
ACTIVECR for an attendant console should be unused but contains a value.

Parameters: ACTIVECR, TN, (contents of ACTIVECR)
Action: Report the problem to the operating company.
Severity: Minor.
BUG0288
SNMP trap: Yes
Call is in ACD queue , but DIGIT_WORDS contains non ACD DN.

Action:
Severity: Minor.
BUG0289
SNMP trap: Yes
The KEYLINK on the Trans key should not be in IDLE state. The LAMP of the
Trans key is set to DARK and the KEYLINK is set to nil. TN is printed.
Procedure CALL_TRANSFER.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 219 of 2360

BUG0290
No third Call Register reserved after attendant hold and release. ATTN_TN
Procedure RESETHOLD
Action:
Severity: Minor.
BUG0291
SNMP trap: Yes
Loop number exceeded it's limits. Procedure: SETTONE.

Severity: Minor.
BUG0292
SNMP trap: Yes
FUNC_DATA_PTR returned invalid pointer.

Action:
Severity: Major.
BUG0293
SNMP trap: Yes
The call cannot be sent to CSDN queue under normal call redirection.
Action: Check call redirection feature and redirection DN (CFW, FDN, HUNT,
etc). The DN cannot be CSDN.
Severity: Minor.
BUG0294
SNMP trap: Yes
Invalid PRB_PTR route pointer. Procedure TEMPPATH.

Action:
Severity: Minor.
BUG0295
SNMP trap: Yes
No attendant unit type in Call Register. *(CRPTR) Procedure RELINK

Action:
Severity: Minor.
BUG0296
SNMP trap: Yes
Invalid customer number. Procedure OFFER_ATTN_RTSA

Action:
Severity: Minor.
BUG0297
SNMP trap: No
Invalid Attendant number. Procedure OFFER_ATTN_RTSA

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 220 of 2360

BUG0298
Invalid ATTN_OFFER_TYPE parameter. Procedure OFFER_ATTN_RTSA

Action:
Severity: Minor.
BUG0299
SNMP trap: No
A timing block was corrupted and is repaired.

Parameters: Corrupted and corrected timing block markers.
Action:
Severity: Major.
BUG0300 (135)
SNMP trap: Yes
Invalid TN translation. TN Procedure ATTNPATHS

Action:
Severity: Minor.
BUG0301
SNMP trap: No
The system configuration had a corrupt value for the software generic, the
software release and issue, or the release subissue. The value, which the
system requires to reload, has been corrected.
Action: Report the corruption to your Nortel Networks distributor.
Severity: Minor.
BUG0305
SNMP trap: Yes
Invalid TN translation. TN Procedure RELEASE

Action:
Severity: Minor.
BUG0306
SNMP trap: No
PARM_PTR is NIL in procedure ENB_AML_IP_LK.

Action:
Severity: Major.
BUG0307
SNMP trap: Yes
AML IP: <procedure name>: <text describing the error, with relevant
parameters>.
Where: <procedure name> is the name of the procedure where the problem
occurred.
Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 221 of 2360

BUG0308
PDT: Semaphore (semaphore name) create error.

Severity: Major.
BUG0309
SNMP trap: Yes
PDT: Semaphore (semaphore name) take error, id, errno.

Severity: Major.
BUG0310
SNMP trap: Yes
Invalid attendant number. CUSTOMER, ATTN_NUMBER Procedure

SETATTNPTRS
Action:
Severity: Minor.
BUG0311
SNMP trap: No
PDT: Table information (description) get error, tid, slot, p1, p2.
Severity: Major.
BUG0312
SNMP trap: Yes
PDT: Table information (description) set error, tid, slot, p1, p2.
Severity: Major.
BUG0313
SNMP trap: Yes
Shorter DN conflict. Procedure SETATTNPTRS

Action:
Severity: Minor.
BUG0314
SNMP trap: No
Shorter DN conflict. Procedure SETATTNPTRS

Action:
Severity: Minor.
BUG0315
SNMP trap: No
Invalid customer number. CUSTOMER NUMBER. Procedure

SETCUSTPTRS
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 222 of 2360

BUG0316
Call ID is invalid
Action:
Severity: Minor.
BUG0317
SNMP trap: Yes
Detected NULL pointer.

Action: Verify pbxLinkMon system operation is correct.
Severity: Major.
BUG0318
SNMP trap: Yes
Detected task related error.

Severity: Major.
BUG0319
SNMP trap: Yes
Invalid tn encountered in SEND_TO_MAIN.

Action: Contact Nortel representative if occurs repeatedly.
Severity: Minor.
BUG0320
SNMP trap: Yes
TD_G_LOOP:CRPTR not a tone loop. LOOP, *(CRPTR). Procedure

REMOVETONETER
Action:
Severity: Minor.
BUG0321
SNMP trap: Yes
Same as BUG320 but loop_type not MF_SENDER. Procedure

REMOVETONETER
Action:
Severity: Minor.
BUG0322
SNMP trap: Yes
Wrong Bandwidth <Intra/Inter> Usage calculation. Zone: <zone number>

Severity: Minor.
BUG0325
SNMP trap: Yes
TD_G_LOOP:CRPTR not a tone loop. LOOP, *(CRPTR) Procedure

IDLETONE
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 223 of 2360

BUG0326
CARDLAN: Outstanding message for session n has been discarded.

Message type m dest d number of messages expected x received y.
Action:
Severity: Info.
BUG0327
SNMP trap: Yes
CARDLAN: Missing header message for session n. Data message has been
discarded.
Action:
Severity: Info.
BUG0328
SNMP trap: Yes
CARDLAN: Invalid message m received for session n.

Action:
Severity: Info.
BUG0329
SNMP trap: Yes
CARDLAN: Invalid message m received for session n.

Action:
Severity: Info.
BUG0330
SNMP trap: Yes
Traffic start times mismatch. PRESENT_TIME, TNX, TNY, CALL_TYPE,

START_TIME1, START_TIME2, TIME_SLOT, START_TIME3,
START_TIME4. For Meridian SL-1 N and XN machines with Generic X11:
TIME_SLOTX, TIME_SLOTY. Procedure PATHIDLE
Call Types
0 Dial ton 1 Busy 2 Overflow tone
3 Ringback ton
Ring ton
5 Miscellaneous tone 6 Outpulser
7 8 Digitone 9 Incoming trunk
10 Outgoing trunk 11 Intra 12 Tandem trunk 13 Reserved connection only.
Action:
Severity: Minor.
BUG0331
SNMP trap: Yes
CARDLAN: Invalid cabinet number n for sending message to. Message type
x dest d.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 224 of 2360

BUG0332
IPM failed to set HSP IP addresses.

Action:
Severity: Info.
BUG0334
SNMP trap: Yes
LCS: Invalid message sent from LCS to IPM.

Action:
Severity: Info.
BUG0335
SNMP trap: Yes
Invalid argument to AIOD_MODULE. SOURCE Procedure AIOD_MODULE

Action:
Severity: Minor.
BUG0336
SNMP trap: No
Invalid customer number or route number from CO trunk. CUSTNO,

ROUTENO, TN. Procedure AIOD_MODULE
Action:
Severity: Minor.
BUG0337
SNMP trap: No
DBSYNC: Invalid command x received.

Action:
Severity: Info.
BUG0338
SNMP trap: Yes
CARDLAN: Error updating XIM memory - dest d contents w x y z.

Action:
Severity: Info.
BUG0339
SNMP trap: Yes
CARDLAN: Received message from invalid session n. Message type is t.

Action:
Severity: Info.
BUG0340
SNMP trap: Yes
Invalid TN. Minor alarm lamp lit on attendant console. Procedure

AIOD_MODULE
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 225 of 2360

BUG0341
Request to allocate speechpath between a Call Server TDM TN and an IPMG

TN.
Action: Contact Nortel representative if occurring repeatedly.
Severity: Minor.
BUG0342
SNMP trap: Yes
PTN allocation error. TN. The two TNs and their associated PTNs are printed.
Action: Contact Nortel representative if occurring repeatedly.
Severity: Minor.
BUG0343
SNMP trap: Yes
CARDLAN: Received Header message with invalid num_msgs m from

session n Message is discarded.
Action:
Severity: Info.
BUG0344
SNMP trap: Yes
CARDLAN: Received too many data messages from session s.

Data message is discarded.
Action:
Severity: Info.
BUG0345
SNMP trap: Yes
Invalid unit type from ORIGTN. ORIGTN, TYPE. Procedure AIOD_MODULE

Action:
Severity: Minor.
BUG0346
SNMP trap: No
SSD: Received SSD message of invalid type t from call server. Message is
discarded.
Action:
Severity: Info.
BUG0347
SNMP trap: Yes
SSD: The queued SSD message is targeted for an invalid cabinet n. Message
is discarded.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 226 of 2360

BUG0348
An error has been captured at GF related C++ code. This error is used to
report anomalies spanning 4 categories (Critical, Major, Minor and
Information). Dependant upon the category, this error might lead to corruption
and INIs.
Action:
Action: Contact your Nortel Networks Technical Support Group to assess the
potential impact upon the system.
Severity: High.
BUG0349
SNMP trap: No
RFC: setServParms: servInData pointer is NIL.

Action:
Severity: High.
BUG0350
SNMP trap: Yes
Invalid AIOD progress mark. AIOD_TN, PROGRESS MARK Procedure

AIOD_MODULE
Action:
Severity: Minor.
BUG0351
SNMP trap: No
Cannot open Secondary Call Server state file.

Action: Verify hard disk accessibility. If the Call Server went to
OUTOFLICENSE, reinstall the software.
Severity: Major.
BUG0352
SNMP trap: Yes
Secondary Call Server state file is corrupted.

Action: Reinstall the software.
Severity: Major.
BUG0353
SNMP trap: Yes
IPM: ELAN network interface (port number) receive stop error, times
attempted, errno
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 227 of 2360

BUG0354
IPM: ELAN network interface (port number) enable error, times

attempted, errno.
Action: In overlay 137, use the "stat elnk" command to verify ELAN network
interface is enabled
- If neccessary, use the "dis elnk" and "enl elnk" commands to
reset the port.
- Contact your technical support.
Severity: Info.
BUG0355
SNMP trap: Yes
Fail PERIPH_MSG. Minor alarm lamp lit on attendant console. TN, MSG.
Procedure AIOD_MODULE
Action:
Severity: Minor.
BUG0356
SNMP trap: No
The number of TNs <number> in the Boss Secretary Arrangement is out of

range.
Action:
Severity: Minor.
BUG0357
SNMP trap: No
LCS: Operation (operation type) pending timeout, timeout

type.
Severity: Major.
BUG0358 a b
SNMP trap: Yes
Parameters: a b. One of TNs is Physical TN. "a" and "b" are TNs
Action: Contact Nortel Networks representative if occurring repeatedly
Severity: Minor.
BUG0359
SNMP trap: Yes
TN TS oldPTN newPTN
Invalid IPMG PTN
Action: Contact Nortel representative if occurring repeatedly
Severity: Info.
SNMP trap: Yes
System Messages
Page 228 of 2360

BUG0360
Invalid card type from force disconnect. TN, AIOD CARD TYPE. Procedure
AIOD_MODULE
Action:
Severity: Minor.
BUG0361
SNMP trap: No
The RLF_LAMP is WINKING, but the KEYLINK is not in CR range (procedure

ADDON/WINKING or CALL_TRANSFER/WINKING).
Action: {UTN:ADDRESS(ORIG_ITEM)} and call Register.
Severity: Info.
BUG0362
SNMP trap: Yes
Telephone set template address is corrupt.

Parameters: line pointer, template pointer.
Action: Report the problem to the operating company
Severity: Major.
BUG0363
SNMP trap: Yes
Telephone set template data offset is corrupt.

Parameters: function number, line pointer, template pointer, data offset
Action: Report the problem to the operating company
Severity: Major.
BUG0364
SNMP trap: Yes
LCS: Cannot send to CM

Action:
Severity: Info.
BUG0365
SNMP trap: Yes
Network map indicates timeslot is idle but network memory is not idle. TN1,
TN2 (packed format), BADLOOP, SLOT1, SLOT2, CONTENTS. 811 and 911
versions: DATA0, DATA1. Procedure PATHFIND
Action:
Severity: Minor.
BUG0366
SNMP trap: Yes
Unable to create a new VMB block. Insufficient memory. Procedure

NEW_VMB.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 229 of 2360

BUG0367
Invalid case in CASE statement. Procedures MPH_MAINT, MPH_RCV_MSG.

Severity: Minor.
BUG0368
SNMP trap: Yes
Call register found in 128 millisecond timeout queue with MAINPM as

SPECIAL and AUXPM as IAGT_ADCR_MA, but the call register is not used
for MARP & MADN IACR / IDCR processing.
Action:
Severity:
BUG0369
SNMP trap: Yes
The number of Converged Desktop Users has reached the ISM limit allowed.
Severity: Minor.
BUG0370
SNMP trap: Yes
Network map indicates timeslot is idle but network memory is not idle. TN1,
TN2, BADLOOP, SLOT, CONTENTS. Procedure PATHFIND
Action:
Severity: Minor.
BUG0371
SNMP trap: No
TN3, *(ACTIVECR OF TN3), TALKSLOT_JUNC.ACTIVECR OF TN3.

Procedure PATHFIND
Action:
Severity: Minor.
BUG0372
SNMP trap: No
TN4, *(ACTIVECR OF TN4), TALKSLOT_JUNC.ACTIVECR OF TN4.

Procedure PATHFIND. TN1, TN2 are the TN involved in the call to pathfind.
TN3, TN4 are the TN diagnosed as Being involved in a connection using the
timeslot in question.
Action:
Severity: Minor.
BUG0373
SNMP trap: No
The number of TR 87 API Controlled sets has reached the ISM limit allowed.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 230 of 2360

BUG0374
Converged Desktop Telephones ISM counter encountered corruption.

Counter is reset to 0.
Severity: Minor.
BUG0375
SNMP trap: Yes
No conference pointer. *(CRPTR). Procedure REM_BI_BV_TONE

Action:
Severity: Minor.
BUG0376
SNMP trap: No
Microsoft Convergence Gold Level ISM counter encountered corruption.

Counter is reset to 0.
Severity: Minor.
BUG0377
SNMP trap: Yes
Invalid key number during an attempt to log a call. PROCEDURE

REM_RING_BCS
Severity: Major.
BUG0378
SNMP trap: Yes
Failed to update QoS call CAC tree. Zone: <zone number>.

Action: Analyze the QoS tree with LD 117 CAC commands. Reinstall the tree if
required.
Severity: Major.
BUG0379
SNMP trap: Yes
IPM: Fixing of the HSP addresses failed

Action:
Severity: Info.
BUG0380
SNMP trap: No
No destination pointer when removing tone. *(CRPTR). Procedure

REM_BI_BV_TONE
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 231 of 2360

BUG0381
IPM: IfAddrSet failed: Can't assign IP address to ELAN port.

Action: None
Severity: Info.
BUG0382
SNMP trap: Yes
IPM: HSP and ELNK addresses are not allowed in the same subnet.
ipmHspSetAddr failed.
Action: Reconfigure the HSP IP address to be in a different subnet than the
ELAN.
Severity: Info.
BUG0383
SNMP trap: Yes
Wrong Bandwidth <Intra/Inter> Usage calculation. Zone: <zone number>.

Severity: Major.
BUG0384
SNMP trap: No
Attempt of accessing non-existent zone. Zone: <zone number>.

Severity: Minor.
BUG0385
SNMP trap: No
CRPTR = NIL. Procedure REMOVEQ

Action:
Severity: Minor.
BUG0386
SNMP trap: No
CPND Name pointer is out of protected memory range. Procedure

PTR_TO_LANG.
Severity: Major.
BUG0387
SNMP trap: Yes
Invalid START_TIME Procedure : SET_DURATION Output: TNX, TNY.

Severity: Minor.
BUG0389
SNMP trap: Yes
Attendant ANUM corruption.

Action: Not applicable.
Severity: Info.
SNMP trap: Yes
System Messages
Page 232 of 2360

BUG0390
CRPTR = NIL. Procedure INSERTQ

Action:
Severity: Minor.
BUG0395
SNMP trap: Yes
Invalid customer number in Call Register. *(CRPTR), ATTNCUSTNO

(decimal). Procedure INCR_ATTN_QU
Action:
Severity: Minor.
BUG0400
SNMP trap: Yes
Invalid customer number in Call Register. *(CRPTR), ATTNCUSTNO

(decimal). Procedure DECR_ATTN_QU
Action:
Severity: Minor.
BUG0401
SNMP trap: Yes
Resource locator: invalid message type (MESSAGE_TYPE).

Severity: Major.
BUG0402
SNMP trap: Yes
Resource locator: invalid data pointer (VITN_DATA_PTR is nil).

Severity: Major.
BUG0403
SNMP trap: Yes
Resource locator: invalid TN.

Severity: Major.
BUG0404
SNMP trap: Yes
Communication problem with audio connection proxy.

Severity: Major.
BUG0405
SNMP trap: Yes
Number to be displayed is negative. NUMBER (hex). Procedure

DECIMAL_CONVERT
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 233 of 2360

BUG0410
Number cannot be represented in specified number of digits. NUMBER,

DIGITS. Procedure DECIMAL_CONVERT
Action:
Severity: Minor.
BUG0420
SNMP trap: No
ORIGTN or TERTN to be idled in Call Register does not match the TN pointed
to by ITEMPTR. Procedure TRUNKS
Action:
Severity: Minor.
BUG0424
SNMP trap: Yes
Invalid trunk state. Procedure TRUNKS

Action:
Severity: Minor.
BUG0425
SNMP trap: Yes
Attempt to seize a non-idle trunk. TN. Procedure TRUNKS

Action:
Severity: Minor.
BUG0426
SNMP trap: Yes
A NWK route access code is not stored in the system memory. Procedure
TRUNKS
Action:
Severity: Minor.
BUG0427
SNMP trap: No
A call through the NWK trunk is camped on but the Call Register is not pointing
to the trunk. The call is disconnected. Procedure TRUNKS
Action:
Severity: Minor.
BUG0428
SNMP trap: No
The NWK trunk which was to be reused had already been reused. Procedure
TRUNKS
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 234 of 2360

BUG0429
Input received by sender/receiver not associated with active Call Register.

Procedure TRUNKS
Action:
Severity: Minor.
BUG0430
SNMP trap: Yes
Invalid CDR request. Procedure CDR

Action:
Severity: Minor.
BUG0431
SNMP trap: Yes
IDLECR has tried to clear the msgcr with C++ links. Probable reason could be,
MSGCR was expected to contain SS information but was not able to process.
Action: Immediate need is to get the call scenario and forward the BUG traces
to Design Team for investigating the reason.
Severity: Minor.
BUG0435
SNMP trap: No
TNTRANS on ORIGTN or TERTN failed. Procedure CDR

Action:
Severity: Minor.
BUG0440
SNMP trap: Yes
TNTRANS on TERTN failed. Procedure CDR

Action:
Severity: Minor.
BUG0445
SNMP trap: Yes
Invalid UNITTYPE detected. Procedure CDR

Action:
Severity: Minor.
BUG0455
SNMP trap: Yes
CDR_BIT was set for trunks being idled. TN, *(CRPTR). Procedure
IDLETRUNK
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 235 of 2360

BUG0460
An attempt to write to protected data store, location 0 by any of the Data

Administration Programs. Procedure WRITEPDS
Action:
Severity: Minor.
BUG0461
SNMP trap: No
WRITEPDSBIT_: an attempt to write to protected data store, location 0 by any

of the Data Administration Programs. Procedure WRITEPDS
Action:
Severity: Minor.
BUG0470
SNMP trap: No
Attempt to transfer to attendant illegal unit (i.e., attendant). Procedure

XFERATTN
Action:
Severity: Minor.
BUG0474
SNMP trap: No
CRPTR not in CR range. {TN} {CRPTR} {CRWORD(0)} {ORIGNTN}{TERTN}

{QUEUE_IN}. Procedure RAN_MODULE
Action:
Severity: Minor.
BUG0475
SNMP trap: Yes
CRPTR = nil in entry to RAN_MODULE. Procedure RAN_MODULE

Action:
Severity: Minor.
BUG0476
SNMP trap: Yes
Invalid RAN_STATE from RAN_TRUNK_TO. Procedure RAN_MODULE

Action:
Severity: Minor.
BUG0477
SNMP trap: Yes
Invalid argument from PERPHI_MSG. Procedure RAN_MODULE

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 236 of 2360

BUG0478
ULRANPTR = nil in removing timing block. Procedure RAN_MODULE

Action:
Severity: Minor.
BUG0479
SNMP trap: Yes
RAN_ITEM is not an RAN trunk. Procedure RAN_MODULE

Action:
Severity: Minor.
BUG0481
SNMP trap: Yes
Attempt to write unprotected location. Procedure WRITEPDS_

Action:
Severity: Minor.
BUG0482
SNMP trap: Yes
Attempt to get unprotected storage on protected page. Procedure GETPDATA

Action:
Severity: Minor.
BUG0483
SNMP trap: No
Attempt to get protected storage on unprotected page. Procedure GETPDATA

Action:
Severity: Minor.
BUG0484
SNMP trap: No
Attempt to write to program store area. UGLOB3: Procedure WRITEPDS@.

Procedure GETPDATA
Action:
Severity: Minor.
BUG0485
SNMP trap: No
Invalid parameter passed to PROCEDURE OVERLOAD. Procedure

OVERLOAD
Action:
Severity: Minor.
BUG0486
SNMP trap: No
Not allowed to write at this location (SL-1 SN and ST). Procedure WRITEDDS
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 237 of 2360

BUG0487
An attempt has been made to write to protected data that is in a block of

memory that is unused. Data is not changed.
Parameters: logical page, address, new value, free memory block data (3
words), page_tail, and block count from the tail.
Action: This error indicates one of two errors. Either an incorrect pointer has
been used to select an address to write, or a data block has two users. Data
corruption is possible. Contact the operating company with the full text of the error
message.
Severity: Major.
BUG0490
SNMP trap: Yes
A father Call Register is trying to create a fourth son (only allowed to create a
maximum of 3 sons), or Son Process type greater than maximum allowed for
the SL-1 system. Procedure File AUXNNN
Action:
Severity: Minor.
BUG0491
SNMP trap: Yes
Either father or son is not a Call Register. Procedure File AUXNNN

Action:
Severity: Minor.
BUG0492
SNMP trap: Yes
The SON_CR pointer passed in does not point to a CR (X08). Illegal process
ID in father Call Register (X11). Procedure CREATE_SON
Action:
Severity: Minor.
BUG0493
SNMP trap: Yes
Attempt to attach more than one son Call Register of the same type.
Procedure CREATE_SON
Action:
Severity: Minor.
BUG0494
SNMP trap: Yes
Broken queue in auxiliary Call Register when attempting to add a new son to
the father (X08). The FATHER_CR pointer passed in does not point to a CR
(X11). Procedure CREATE_SON
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 238 of 2360

BUG0495
Circular linked list is probably broken (i.e., have looped more than the
maximum no. of sons allowed). Procedure REMOVE_SON
Action:
Severity: Minor.
BUG0496
SNMP trap: Yes
Trying to remove a nonexistent son. Procedure REMOVE_SON

Action:
Severity: Minor.
BUG0497
SNMP trap: Yes
Trying to remove a son when no sons exist (i.e., there is no circular list).
Procedure REMOVE_SON
Action:
Severity: Minor.
BUG0498
SNMP trap: Yes
FATHER_CR is not a Call Register. Procedure REMOVE_SON

Action:
Severity: Minor.
BUG0499
SNMP trap: Yes
There is no circular linked list for the FATHER_CR. Procedure FIND_SON

Action:
Severity: Minor.
BUG0500
SNMP trap: Yes
Trying to find a son Call Register when no circular list exists. Procedure
FIND_SON
Action:
Severity: Minor.
BUG0501
SNMP trap: Yes
The FATHER_CR passed in is not a CR. Procedure FIND_SON

Action:
Severity: Minor.
BUG0502
SNMP trap: Yes
There is no circular list for the SON CR passed in. Procedure FIND_FATHER
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 239 of 2360

BUG0503
The SON CR passed in is a FATHER CR. Procedure FIND_FATHER

Action:
Severity: Minor.
BUG0504
SNMP trap: Yes
There is no father in the list or the circular list is corrupted. Procedure

FIND_FATHER
Action:
Severity: Minor.
BUG0505
SNMP trap: Yes
The SON CR passed in is not a CR. Procedure FIND_FATHER

Action:
Severity: Minor.
BUG0506
SNMP trap: Yes
Father does not exist or circular list structure has been broken or corrupted.
Procedure REMOVE_AUXCR
Action:
Severity: Minor.
BUG0507
SNMP trap: Yes
The CR passed in is not a CR. Procedure REMOVE_AUXCR

Action:
Severity: Minor.
BUG0510
SNMP trap: Yes
Invalid function code passed to RPE_MODULE. Procedure RPE_MODULE

Action:
Severity: Minor.
BUG0511
SNMP trap: Yes
RPE function requested on non-RPE loop. Procedure RPE_MODULE

Action:
Severity: Minor.
BUG0512
SNMP trap: Yes
RPE function requested for disabled loop. Procedure RPE_MODULE

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 240 of 2360

BUG0513
Pointer to unprotected loop block or to either RPE data block is nil. Procedure
RPE_MODULE
Action:
Severity: Minor.
BUG0514
SNMP trap: Yes
Invalid RPE queue function code. The RPE block is removed for the queue.
Procedure RPE_MODULE
Action:
Severity: Minor.
BUG0515
SNMP trap: No
Invalid RPE timer function code. The RPE block is removed from the 2 s
queue. Procedure RPE_MODULE
Action:
Severity: Minor.
BUG0516
SNMP trap: No
Bad RPE queue function. RPE block removed from queue. Procedure
RPE_MODULE
Action:
Severity: Minor.
BUG0517
SNMP trap: Yes
Bad RPE timeout type. No time-outs performed. Procedure RPE_MODULE

Action:
Severity: Minor.
BUG0518
SNMP trap: Yes
RPE timing block overflowed. Alarm is not timed. Procedure RPE_MODULE

Action:
Severity: Minor.
BUG0520
SNMP trap: Yes
Idling a Call Register that is still linked as an auxiliary Call Register. Call
Register idle and a task request for Audit is made. Procedure IDLECR_
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 241 of 2360

BUG0525
Used in AUX but unreported. Procedure AUX

Action:
Severity: Minor.
BUG0526
SNMP trap: No
Used in AUX but unreported. Procedure AUX

Action:
Severity: Minor.
BUG0528
SNMP trap: No
CRPTR = nil in entry to ANI_MODULE. {CRPTR} {CRWROD(0)} {ORIGTN}

{TERTN} {QUEUE_IN}. Procedure ANI_MODULE
Action:
Severity: Minor.
BUG0529
SNMP trap: Yes
TDS should not connect at that time. Procedure ANI_MODULE

Action:
Severity: Minor.
BUG0530
SNMP trap: No
Invalid TN. Procedure ANI_MODULE

Action:
Severity: Minor.
BUG0531
SNMP trap: Yes
Invalid state. {TN} {SOURCE} {ANI_PM} {AUX_PM} {TRK_IN}. Procedure

ANI_MODULE
Action:
Severity: Minor.
BUG0532
SNMP trap: Yes
AUX_CRPTR = nil in entry to ANI_MODULE. {CRPTR} {CRWORD(0)}

{ORIGTN} {TERTN} {QUEUE_IN}. Procedure ANI_MODULE
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 242 of 2360

BUG0533
Trunk TN for CAMA trunk is not set up in Call Register. Procedure

ANI_MODULE
Action:
Severity: Minor.
BUG0534
SNMP trap: Yes
Invalid ORIGTN. {CRPTR} {CRWORD(0)} {ORIGTN} {TERTN} {QUEUE_IN}.

Procedure ANI_MODULE
Action:
Severity: Minor.
BUG0535
SNMP trap: Yes
INVALID_DN for ORIGTN. {CRPTR} {CRWORD(0)} {ORIGTN} {TERTN}

{QUEUE_IN}. Procedure ANI_MODULE
Action:
Severity: Minor.
BUG0536
SNMP trap: Yes
Call Register pointed by CRPTR is not main call register or ANI Call Register.
{CRPTR} {CRWORD (0)} {ORIGTN} {TERTN} {QUEUE_IN}. Procedure
ANI_MODULE
Action:
Severity: Minor.
BUG0537
SNMP trap: Yes
Invalid customer number or route number. {ROUTE NUMBER} {CUSTOMER

NUMBER} {AUX CRPTR}. Procedure ANI_MODULE
Action:
Severity: Minor.
BUG0538
SNMP trap: Yes
Invalid CUSTOMER NUMBER. {TN} {CUSTOMER NUMBER} {CRPTR}

{CRWORD(0)}{ORIGTN} {TERTN} {QUEUE_IN}. Procedure ANI_MODULE
Action:
Severity: Minor.
BUG0539
SNMP trap: No
Invalid ROUTE NUMBER or CUSTOMER NUMBER in ANI_GET_CR_TONE.

Procedure ANI_MODULE
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 243 of 2360

BUG0541
No ARS_ROUTEPTR when mashing digits for supposedly good trunk.

*CRPTR *AUX_CRPTR. Procedure ARS_MODULE
Action:
Severity: Minor.
BUG0550
SNMP trap: No
Invalid TN. Procedure VCOM

Action:
Severity: Minor.
BUG0555
SNMP trap: Yes
CAMS nesting level exceeded. Procedure START_CAMS

Action:
Severity: Minor.
BUG0556
SNMP trap: No
Parameter passed to START_CAMS is out-of-range. Procedure

START_CAMS
Action:
Severity: Minor.
BUG0560
SNMP trap: No
CAMS nesting underflow; i.e., STOP_CAMS called before START_CAMS.

Procedure STOP_CAMS
Action:
Severity: Minor.
BUG0565
SNMP trap: No
SET_ROUTE_PTRS failed on a RAN route. Route, Cust, DIGIT_WORDS(0),

* (CRPTR). Procedure GIVE_ROA
Action:
Severity: Minor.
BUG0566
SNMP trap: Yes
IDLE_AUXCR failed. CRWORD(4), AUXLINK, * (CRPTR). Procedure

IDLE_ROA_CALL
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 244 of 2360

BUG0567
DENY_TONES, TN_TRANS, fails. Procedure IDLE_ROA_CALL

Action:
Severity: Minor.
BUG0568
SNMP trap: Yes
DENY_TONES, Call Register does not point to conference. Procedure

IDLE_ROA_CALL
Action:
Severity: Minor.
BUG0569
SNMP trap: Yes
A son CR other than AUTH, ARS or CHARGE was found. Procedure RGA
Action:
Severity: Minor.
BUG0570
SNMP trap: Yes
Call Register said trunks but DN did not. *(CRPTR). Procedure RGA
Action:
Severity: Minor.
BUG0571
SNMP trap: No
A TERTYPE other than set was found in the RGA set queue. *(CRPTR).
Procedure RGA
Action:
Severity: Minor.
BUG0572
SNMP trap: No
SETCUSTPTRS failed on CR in RGA trunks queue. *(CRPTR). Procedure

RGA
Action:
Severity: Minor.
BUG0573
SNMP trap: Yes
TNTRANS of TERTN failed in FREE_TRUNK. *(CRPTR). Procedure RGA

Action:
Severity: Minor.
BUG0575
SNMP trap: Yes
CANCEL called with invalid AUXPM. *(CRPTR). Procedure RGA

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 245 of 2360

BUG0576
Ring Again activated against a DN that was not a set or a trunk.

DIGIT_WORDS 0 :CRPTR, *(CRPTR). Procedure RGA
Action:
Severity: Minor.
BUG0577
SNMP trap: No
When processing the Ring Again set queue, an invalid DN or TN was

encountered. DIGIT_WORDS 0 :CRPTR, *(CRPTR). Procedure RGA
Action:
Severity: Minor.
BUG0579
SNMP trap: Yes
Nil pointer passed to RGA_SEARCHROUTE. Procedure RGA

Action:
Severity: Minor.
BUG0580
SNMP trap: No
Invalid conference loop passed to LINKCONF. Procedure LINKCONF

Action:
Severity: Minor.
BUG0590
SNMP trap: Yes
Too few digits in DN. Procedure SCRSA

Action:
Severity: Minor.
BUG0591
SNMP trap: No
Invalid DN. Procedure SCRSA

Action:
Severity: Minor.
BUG0592
SNMP trap: No
DN indicates a PBX rather than a block. Procedure SCRSA

Action:
Severity: Minor.
BUG0593
SNMP trap: No
DN indicates a block rather than a free space. Procedure SCRSA

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 246 of 2360

BUG0594
DN tree corrupt. Procedure SCRSA

Action:
Severity: Minor.
BUG0595
SNMP trap: No
DN indicates something other than a DN block. Procedure SCRSA

Action:
Severity: Minor.
BUG0599
SNMP trap: No
BREAK_IN Procedure SCRSA

Action:
Severity: Minor.
BUG0600
SNMP trap: Yes
Non CDR CR in CDR Queue.{Customerid} {Port}. Procedure CDR

Action:
Severity: Minor.
BUG0601
SNMP trap: Yes
Broken CDR Queue. {Customerid} {Port}. Procedure CDR

Action:
Severity: Minor.
BUG0602
SNMP trap: Yes
Nil CDR Port Pointer. {Customerid} {Port}. Procedure CDR

Action:
Severity: Minor.
BUG0603
SNMP trap: Yes
Invalid record type in CDR Call Register {CDR_Record 7 } . Procedure CDR

Action:
Severity: Minor.
BUG0604
SNMP trap: No
BREAK_IN - WANTED_DISC; wanted party has no link to attendant's Call

Register. Procedure BREAK_IN
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 247 of 2360

BUG0605
BREAK_IN - WANTED_DISC; TNTRANS for attendant failed. Procedure

BREAK_IN
Action:
Severity: Minor.
BUG0606
SNMP trap: Yes
BREAK_IN - FIND_WANTED_TN; CR, TN or TYPE of WANTED_TN is

wrong. Procedure BREAK_IN
Action:
Severity: Minor.
BUG0607
SNMP trap: Yes
BREAK_IN - JOIN_CONF; conference pointer is nil. Procedure BREAK_IN

Action:
Severity: Minor.
BUG0608
SNMP trap: Yes
BREAK_IN - TNTRANS failed. Procedure BREAK_IN

Action:
Severity: Minor.
BUG0609
SNMP trap: Yes
BREAK_IN - SUCCESS; BRK_CRLINK is nil. Procedure BREAK_IN

Action:
Severity: Minor.
BUG0610
SNMP trap: Yes
TNTRANS failure on dialed party TN. Procedure AUTOVON

Action:
Severity: Minor.
BUG0611
SNMP trap: No
SPEECHPATH idled, could not be recovered. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0612
SNMP trap: No
Dialed party not in conference. Procedure AUTOVON.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 248 of 2360

BUG0613
ATTN_DEST path to dialed party notreserved in ATV_SLOT. Procedure

AUTOVON.
Action:
Severity: Minor.
BUG0614
SNMP trap: No
Invalid MAINPM for dialed party in completion to busy. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0615
SNMP trap: No
Failure to complete a call after idling paths. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0616
SNMP trap: No
Failure to recover idled tone paths. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0617
SNMP trap: No
TNTRANS failed on the ORIGTN for an outgoing preempted trunk to be

re-seized
Action:
Severity: Major.
BUG0618
SNMP trap: No
Station type is not a PBX, BCS or BRI in SLPREM

Action:
Severity: Minor.
BUG0619
SNMP trap: No
Active CR ^= Keylink for non-DN key call preemption

Action:
Severity: Minor.
BUG0620
SNMP trap: No
Preempted call involved attn is not on SRC or DEST

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 249 of 2360

BUG0621
Incoming preemption is aborted after conference disconnect due to CRPTR =

NIL
Action:
Severity: Minor.
BUG0622
SNMP trap: No
Incoming preemption is aborted after ringing disconnect due to CRPTR = NIL

Action:
Severity: Minor.
BUG0623
SNMP trap: No
Outgoing preemption is aborted after conference disconnect due to CRPTR =

NIL
Action:
Severity: Minor.
BUG0624
SNMP trap: Yes
Outgoing preemption is aborted after ringing disconnect due to CRPTR = NIL

Action:
Severity: Minor.
BUG0625
SNMP trap: No
Unable to set up attendant pointers. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0626
SNMP trap: No
Station Loop preemption is aborted after conference disconnect due to

CRPTR = NIL
Action:
Severity: Minor.
SNMP trap: No
SNMP trap: No
BUG0627
Action:
Severity: Minor.
BUG0628
SETCUSTPTRS failure. Procedure AUTOVON.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 250 of 2360

BUG0629
TNTRANS failure on conferee (completion to busy). Procedure AUTOVON.

Action:
Severity: Minor.
BUG0630
SNMP trap: No
TNTRANS failure on trunk TN (outgoing preemption). Procedure AUTOVON.

Action:
Severity: Minor.
BUG0631
SNMP trap: Yes
Failure to complete call after party goes on-hook. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0632
SNMP trap: No
Invalid unit type in dialing state. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0633
SNMP trap: Yes
No dialed party on completion to busy conference. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0634
SNMP trap: No
Invalid call to global AUTOVON

Action:
Severity: Minor.
BUG0635
SNMP trap: Yes
Invalid party in completion to busy conference. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0636
SNMP trap: Yes
Invalid party in incoming preemption conference. Procedure AUTOVON.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 251 of 2360

BUG0637
Invalid party in outgoing preemption conference. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0638
SNMP trap: No
Invalid call to global SLPREM.

Action:
Severity: Minor.
BUG0639
SNMP trap: No
Station Loop preemption is aborted due to CRPTR = NIL after a held call is
disconnected.
Action:
Severity: Minor.
BUG0640
SNMP trap: No
Outgoing preemption invoked on an invalid route. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0641
SNMP trap: No
Idle trunk found during preemptive searching. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0642
SNMP trap: No
TNTRANS failure on incoming timing call register. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0643
SNMP trap: No
Invalid incoming preemption TIMER1 timeout. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0644
SNMP trap: No
Invalid incoming preemption TIMER2 timeout. Procedure AUTOVON.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 252 of 2360

BUG0645
Failure to recover idled speech path (outgoing Preemption). Procedure

AUTOVON.
Action:
Severity: Minor.
BUG0646
SNMP trap: No
SET_ROUTE_PTRS failure. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0647
SNMP trap: No
Invalid AUTOVON timeout. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0648
SNMP trap: No
Invalid conference TN. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0649
SNMP trap: No
TNTRANS failure on attendant TN. Procedure AUTOVON.

Action:
Severity: Minor.
BUG0650
SNMP trap: No
ACCESS_ORIG_TER Unit type: ORIG_LINE_PTR is zero. Procedure

ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0651
SNMP trap: Yes
ACCESS_ORIG_TER Unit type: ORIG_LINE_PTR is greater than .ATTN.

Procedure ACCESS_ORIG_TER
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 253 of 2360

BUG0652
LINE_CALL Unit type: TER_LINE_PTR is zero. Procedure

ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0653
SNMP trap: Yes
LINE_CALL Unit type: TER_LINE_PTR is greater than ATTN. Procedure

ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0654
SNMP trap: Yes
STN_TO_ATTN Unit type: TER_LINE_PTR is zero after substitution of

DESTPTR. Procedure ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0655
SNMP trap: Yes
STN_TO_ATTN Unit type: TER_LINE_PTR is greater than .ATTN after

substitution of DESTPTR. Procedure ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0656
SNMP trap: Yes
STN_TO_ATTN unit on DESTPTR does not tntrans for substitution.

Action:
Severity: Minor.
BUG0657
SNMP trap: Yes
STN_TO_ATTN CRPTR does not equal SRCPTR. Procedure

ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0658
SNMP trap: Yes
TRUNK_CALL Unit type: TER_LINE_PTR is zero. Procedure

ACCESS_ORIG_TER
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 254 of 2360

BUG0659
TRUNK_CALL Unit type: TER_LINE_PTR is greater than .ATTN. Procedure

ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0660
SNMP trap: Yes
TRK_TO_ATTN Unit type: TER_LINE_PTR is zero after substitution of

DESTPTR. Procedure ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0661
SNMP trap: Yes
TRK_TO_ATTN Unit type: TER_LINE_PTR is greater than .ATTN after

substitution of DESTPTR. Procedure ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0662
SNMP trap: Yes
TRK_TO_ATTN unit on DESTPTR does not TNTRANS for substitution.

Action:
Severity: Minor.
BUG0663
SNMP trap: Yes
TRK_TO_ATTN CRPTR does not equal SRCPTR. Procedure

ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0664
SNMP trap: Yes
ATTN_CALL Unit type: ORIG_LINE_PTR is zero after substitution of

NEW_TN. Procedure ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0665
SNMP trap: Yes
ATTN_CALL Unit type: ORIG_LINE_PTR is greater than .ATTN after

substitution of NEW_TN. Procedure ACCESS_ORIG_TER
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 255 of 2360

BUG0666
ATTN_CALL NEW_TN does not TNTRANS. Procedure

ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0667
SNMP trap: Yes
ACCESS_CONF non-conference loop passed in CFTN. Procedure

ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0668
SNMP trap: Yes
LEAST_RESTR_TN DNTYPE not .MIXSL-1PR_DN. Procedure

ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0669
SNMP trap: Yes
RLT_REMOTE trunk on originating side of ACCESS_ORIG_TER was not

intercepted to RLTR_CALL. Procedure ACCESS_ORIG_TER
Action:
Severity: Minor.
BUG0670
SNMP trap: Yes
TERTYPE not PBX or SL-1 or NNABIT set and DNTYPE not multiple
appearance. *CRPTR. Procedure FIND_FRE_TN
Action:
Severity: Minor.
BUG0671
SNMP trap: Yes
Invalid unit type in ITEM. ORIG_ITEM_PTR, *CRPTR.Procedure

FIND_FRE_TN
Action:
Severity: Minor.
BUG0675
SNMP trap: Yes
Invalid message type from auxiliary processor. Procedure AUX_INP_Q

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 256 of 2360

BUG0676
High-speed link does not exist. Procedure AUX_INP_Q

Action:
Severity: Minor.
BUG0677
SNMP trap: Yes
Illegal attempt to put the message Call Register into the high-speed output
queue. Procedure AUX_LINK_MSG_CR
Action:
Severity: Minor.
BUG0680
SNMP trap: Yes
SET_ACD_POS_PTRS encountered a station that was not a SL-1 set, did not
have key 0 as an ACD key or the U_ACD_POS_PTR was NIL. TN. Procedure
ACD.
Action:
Severity: Minor.
BUG0681
SNMP trap: Yes
SET_ACD_PTRS failed. CUST, DN. Procedure ACD

Action:
Severity: Minor.
BUG0682
SNMP trap: Yes
ACD_LINK failed because the Call Register was already in a queue.

*(CRPTR). Procedure ACD
Action:
Severity: Minor.
BUG0683
SNMP trap: Yes
ACD_REMOVE was given a Call Register that was not in an ACD queue.
Action:
Severity: Minor.
BUG0684
SNMP trap: Yes
ACD_REMOVE encountered an invalid AUXPM in an ACD Call Register.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 257 of 2360

BUG0685
SET_ROUTE_PTRS failed on a RAN route. ROUTE, CUST, DIGIT_WORDS

0 , *(CRPTR). Procedure ACD
Action:
Severity: Minor.
BUG0687
SNMP trap: Yes
IDLE_AUXCR failed in IDLE_ACDRAN_CALL. CRWORD 4 , AUXCRLINK,

Action:
Severity: Minor.
BUG0688
SNMP trap: Yes
Agent or call failed to TNTRANS in SUCCESSFUL_TERM.

*(ACD_CALL_CR), *(ACD_AGENT_CR). Procedure ACD
Action:
Severity: Minor.
BUG0689
SNMP trap: Yes
Improper input to APPLYTERMINATION. TERTN, *(CRPTR). Procedure ACD

Action:
Severity: Minor.
BUG0691
SNMP trap: Yes
A logged on ACD agent was automatically logged out when a LD 11 change

was made to that set.
Action:
Severity: Minor.
BUG0693
SNMP trap: Yes
Bad entry to ACD. SOURCE Procedure ACD

Action:
Severity: Minor.
BUG0694
SNMP trap: Yes
RAN_TIMING found ORIGTN that failed to TNTRANS. *(CRPTR. Procedure

ACD
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 258 of 2360

BUG0695
SET CUST PTRS failed. Customer number. Procedure ACD

Action:
Severity: Minor.
BUG0697
SNMP trap: Yes
Agent-ID to be removed cannot be found in the Agent-ID table. Customer

number, Agent-ID. Procedure ACD
Action:
Severity: Minor.
BUG0698
SNMP trap: Yes
Agent-ID table does not exist for this customer. Customer number. Procedure
ACD
Action:
Severity: Minor.
BUG0700
SNMP trap: No
Invalid action requested of CAS main. Procedure ACD

Action:
Severity: Minor.
BUG0701
SNMP trap: Yes
Cannot set RLA ptrs. The data for BUG701 to BUG732 inclusive, is as follows:
Action:
Severity: Minor.
BUG0702
SNMP trap: Yes
Input parameter 'event' is out-of-range. File CASRXXX. See BUG701 for

output.
Action:
Severity: Minor.
BUG0704
SNMP trap: Yes
Incorrect state for receipt of .RLT_ANS_SUPV. File CASRXXX. See BUG701

for output.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 259 of 2360

BUG0705
Invalid state in flash disc. (Simple case). File CASRXXX. See BUG701 for
output.
Action:
Severity: Minor.
BUG0706
SNMP trap: Yes
Invalid state in flash disc. (Conf. case). File CASRXXX. See BUG701 for
output.
Action:
Severity: Minor.
BUG0707
SNMP trap: Yes
Attempt to apply Ringback to no existing source. File CASRXXX. See BUG701

for output.
Action:
Severity: Minor.
BUG0708
SNMP trap: Yes
CRPTR is not RLA_SOURCE or RLA_DEST. File CASRXXX. See BUG701

for output.
Action:
Severity: Minor.
BUG0710
SNMP trap: Yes
Invalid state encountered. File CASRXXX. See BUG701 for output.

Action:
Severity: Minor.
BUG0711
SNMP trap: Yes
Members still connected to an idle conference. File CASRXXX. See BUG701

for output.
Action:
Severity: Minor.
BUG0713
SNMP trap: Yes
RLA_PM = .RLA_EXTENDING and RLA_SOURCE = nil. File CASRXXX. See

BUG701 for output.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 260 of 2360

BUG0714
ORIGTN in SCR_CR cannot TNTRANS. File CASRXXX. See BUG701 for

output.
Action:
Severity: Minor.
BUG0715
SNMP trap: Yes
Invalid RLA state. File CASRXXX. See BUG701 for output.

Action:
Severity: Minor.
BUG0716
SNMP trap: Yes
Invalid tone timeout in extending state. File CASRXXX. See BUG701 for
output.
Action:
Severity: Minor.
BUG0717
SNMP trap: Yes
Invalid tone timeout in SOURCE_DISC state. File CASRXXX. See BUG701

for output.
Action:
Severity: Minor.
BUG0718
SNMP trap: Yes
Invalid CONF. State in tone timeout. File CASRXXX. See BUG701 for output.
Action:
Severity: Minor.
BUG0719
SNMP trap: Yes
RLA_HALF_DISC state and data not zero. File CASRXXX. See BUG701 for
output.
Action:
Severity: Minor.
BUG0720
SNMP trap: Yes
RLA_PM does not match DEST_CR state. The call is established but
RLA_PM is still in extending state. File CASRXXX. See BUG701 for output.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 261 of 2360

BUG0721
CRPTR set to nil but is already nil. File CASRXXX. See BUG701 for output.
Action:
Severity: Minor.
BUG0722
SNMP trap: Yes
RLT trunk timeout but active CR is nil. File CASRXXX. See BUG701 for
output.
Action:
Severity: Minor.
BUG0725
SNMP trap: Yes
RLT seizure and ACTIVECR not nil. File CASRXXX. See BUG701 for output.
Action:
Severity: Minor.
BUG0727
SNMP trap: Yes
Call to IDLESPEECH with .ALL_PATHS when one of SRC or DEST is not

there. File CASRXXX. See BUG701 for output.
Action:
Severity: Minor.
BUG0728
SNMP trap: Yes
CAS key defined on illegal set. File CASRXXX. See BUG701 for output.
Action:
Severity: Minor.
BUG0729
SNMP trap: Yes
Invalid MAINPM in Call Register. File CASRXXX. See BUG701 for output.
Action:
Severity: Minor.
BUG0730
SNMP trap: Yes
ORIGTO not in infotone CR. File CASRXXX. See BUG701 for output.
Action:
Severity: Minor.
BUG0731
SNMP trap: Yes
TERTO not allowed. File CASRXXX. See BUG701 for output.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 262 of 2360

BUG0732
Attempt to build conference connection without ORIG and TER parties. File
CASRXXX. See BUG701 for output.
Action:
Severity: Minor.
BUG0733
SNMP trap: Yes
RLA index not equal to zero when presenting the call. File CASRXXX. See
BUG701 for output.
Action:
Severity: Minor.
BUG0735
SNMP trap: Yes
Invalid Action--Attempting to pickup a Held Call from a trunk. File CASRXXX.

See BUG701 for output.
Action:
Severity: Minor.
BUG0740
SNMP trap: Yes
Procedure SET_DISPLAY. Subprocedure ATTNSIDE failed. File DDSPXXX

Action:
Severity: Minor.
BUG0741
SNMP trap: Yes
Procedure SET_DISPLAY. Subprocedure DISPLAY_OUR_DN failed. File

DDSPXXX
Action:
Severity: Minor.
BUG0742
SNMP trap: Yes
Procedure DISPLAY_MODE. 'Delay display' timer has timeout but DISPLAY

key KEYLINK does not point to the CR in the timing list. File DDSPXXX
Action:
Severity: Minor.
BUG0743
SNMP trap: Yes
The LED state for the active Display key was dark or flashing. Neither state is
valid. Possible loss of Call Register.
Action: Run audit (LD 44). Procedure DISPLY_KEY, file DDSPXXX.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 263 of 2360

BUG0744
Procedure DISPLAY_MODE. No Call Register attached to Display Key. File

DDSPXXX
Action:
Severity: Minor.
BUG0745
SNMP trap: Yes
Invalid function code passed to SET_DISPLAY. File DDSPXXX

Action:
Severity: Minor.
BUG0750
SNMP trap: Yes
SET_CUST_PTRS failed from GET_ATTN_DN. CUST.

Action:
Severity: Minor.
BUG0755
SNMP trap: Yes
DNTRANS2 returned other than .ATN_DN in ATTN_DN_BLK_PTR. CUST,

DN, DNTYPE. Procedure ATTN_DN_BLK_PTR
Action:
Severity: Minor.
BUG0771
SNMP trap: Yes
Invalid customer number. Procedure ARST.

Action:
Severity: Minor.
BUG0774
SNMP trap: No
Unable to set up customer pointers. Procedure ARST

Action:
Severity: Minor.
BUG0780
SNMP trap: No
CRPTR is invalid. Procedure DISA_MODULE

Action:
Severity: Minor.
BUG0781
SNMP trap: No
MAINPM .DIALING, .READY or .DELAYDIALING. Procedure DISA_MODULE

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 264 of 2360

BUG0782
CUSTNO:PLORIGPTR fails SETCUSTPTRS. Procedure

CHARGE_ACCOUNT
Action:
Severity: Minor.
BUG0783
SNMP trap: No
Extended function not .CPN_FN or .CHG_FN. Procedure

CHARGE_ACCOUNT
Action:
Severity: Minor.
BUG0784
SNMP trap: No
CRPTR is invalid. Procedure CHARGE_AUTHCODE

Action:
Severity: Minor.
BUG0785
SNMP trap: No
Procedure called with an invalid SOURCE parameter. Procedure

CHARGE_AUTHCODE
Action:
Severity: Minor.
BUG0786
SNMP trap: No
ORIGTN does not TNTRANS. Procedure CHARGE_AUTHCODE

Action:
Severity: Minor.
BUG0787
SNMP trap: No
CUSTNO: PLORIGPTR fails SETCUSTPTRS. Procedure

CHARGE_AUTHCODE
Action:
Severity: Minor.
BUG0788
SNMP trap: No
AUXPM does not indicate CHARGE/CPN/AUTH. Procedure

CHARGE_AUTHCODE
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 265 of 2360

BUG0789
CONF_TN is not a conference loop. Procedure CHARGE_AUTHCODE

Action:
Severity: Minor.
BUG0790
SNMP trap: No
Son Call Register cannot be linked. Procedure CHARGE_AUTHCODE

Action:
Severity: Minor.
BUG0791
SNMP trap: No
There is no son Call Register linked. Procedure CHARGE_AUTHCODE

Action:
Severity: Minor.
BUG0803
SNMP trap: No
No ACD_LIST_PTR for current customer. Procedure ACD_REPORTS

Action:
Severity: Minor.
BUG0804
SNMP trap: Yes
You cannot OUT SCB data block while ACD Package C reports are scheduled
to
Action:
Severity: Minor.
BUG0805
SNMP trap: Yes
Nil pointers to IO_BLOCK or U_ACD_PRINT block. Procedure ACD_IO

Action:
Severity: Minor.
BUG0806
SNMP trap: Yes
Nil pointer to ACD SCHEDULE BLOCK. Procedure ACD_IO

Action:
Severity: Minor.
BUG0807
SNMP trap: Yes
Nil pointer to P_ACD_LIST or P_ACD_BLOCK or ACD_POS_LIST.

Procedure CD_IO
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 266 of 2360

BUG0808
ACD I/O terminal not defined in logical unit table. Procedure ACD_IO
Action:
Severity: Minor.
BUG0809
SNMP trap: Yes
Invalid TN in field ACD_POS_ID for an ACD agent position. Procedure

ACD_IO
Action:
Severity: Minor.
BUG0810
SNMP trap: Yes
ACD key data not set up properly. Procedure ACD_IO

Action:
Severity: Minor.
BUG0811
SNMP trap: Yes
ACD position expected not found in ACD_POS_LIST. Procedure ACD_IO

Action:
Severity: Minor.
BUG0820
SNMP trap: Yes
Invalid ACD supervisor in observe procedure. Procedure ACD_IO

Action:
Severity: Minor.
BUG0821
SNMP trap: Yes
Invalid key state for ACD supervisor observe key. Procedure ACD_IO
Action:
Severity: Minor.
BUG0822
SNMP trap: Yes
ACD supervisor's active CR does not equal the observe key link while in
observe mode. Procedure ACD_IO
Action:
Severity: Minor.
BUG0824
SNMP trap: Yes
Invalid Call Register used to set one way conference speech path. Procedure
ACD_IO
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 267 of 2360

BUG0826
Illegal entry point. Procedure MUSIC

Action:
Severity: Minor.
BUG0827
SNMP trap: Yes
Conferee count for music trunk not correct. Procedure MUSIC

Action:
Severity: Minor.
BUG0828
SNMP trap: Yes
Originating side of ACD call is invalid to receive music. Procedure MUSIC

Action:
Severity: Minor.
BUG0829
SNMP trap: Yes
Conference loop on music trunk not the loop assigned. Procedure MUSIC
Action:
Severity: Minor.
BUG0840
SNMP trap: Yes
Logical page parameter out-of-range. Procedure File MEMXXX

Action:
Severity: Minor.
BUG0841
SNMP trap: Yes
Block size parameter is not correct. Procedure File MEMXXX.

Output: PAGE#, BLKSIZE.
Action:
Severity: Minor.
BUG0842
SNMP trap: Yes
Attempt to copy a data block onto itself. Procedure File MEMXXX

Action:
Severity: Minor.
BUG0843
SNMP trap: Yes
Attempt to copy a data block past the end of memory. Procedure File
MEMXXX
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 268 of 2360

BUG0844
Attempt to release in low (reserved) memory. Procedure File MEMXXX

Action:
Severity: Minor.
BUG0845
SNMP trap: Yes
Attempt to release beyond end of memory. Procedure File MEMXXX

Action:
Severity: Minor.
BUG0846
SNMP trap: Yes
Invalid message received. Reason = [reason]. Header info - Source : [n1],

Dest : [n2], Type [n3], Size [n4], MagicNo [n5]. Where
reason = "invalid message header" or "invalid size"
Action: Message is discarded and the communication channel is re-established.
However, if problem persists, please contact Nortel support.
Severity: Major.
BUG0850
SNMP trap: Yes
Divide overflow. Procedure File SCMMXXX (Memory Management LD 29)

Action:
Severity: Minor.
BUG0851
SNMP trap: No
Invalid task request: EXEC_PM, TASKPM, current request new request.

Procedure File SCMMXXX (Memory Management LD 29)
Action:
Severity: Minor.
BUG0852
SNMP trap: No
Task stack underflow. Procedure File SCMMXXX (Memory Management LD

29)
Action:
Severity: Minor.
BUG0853
SNMP trap: No
Print buffer overflow. Procedure File SCMMXXX (Memory Management LD

29)
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 269 of 2360

BUG0854
Logical page list overflow. Procedure File SCMMXXX (Memory Management

LD 29)
Action:
Severity: Minor.
BUG0855
SNMP trap: No
Task stack overflow. Procedure File SCMMXXX (Memory Management LD

29)
Action:
Severity: Minor.
BUG0856
SNMP trap: No
Invalid control byte in print buffer. Procedure File SCMMXXX (Memory

Management LD 29)
Action:
Severity: Minor.
BUG0857
SNMP trap: No
Detected a NULL pointer

Action: Contact your local support.
Severity: Minor.
BUG0858
SNMP trap: Yes
An unsupported case encountered in the code.

Severity: Minor.
BUG0860
SNMP trap: Yes
Attempt to write unprotected memory using a protected write operator.

Procedure WRITEPDS (X08). Invalid state of an agent position occurred.
Procedure File ADSXXX (X11).
Action:
Severity: Minor.
BUG0888
SNMP trap: Yes
Sum of the variables TB_SRC_COUNT and PB_DEST_COUNT is

out-of-range. Should be 0 to 7. Logic error. Contact manufacturer. Procedure
TRUNK_BARRING
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 270 of 2360

BUG0960
Illegal party dialed park DN. Procedure TRUNK_BARRING

Action:
Severity: Minor.
BUG0961
SNMP trap: No
Cannot locate park block at recall time. Procedure TRUNK_BARRING

Action:
Severity: Minor.
BUG0962
SNMP trap: No
Cannot locate attendant park key. Procedure TRUNK_BARRING

Action:
Severity: Minor.
BUG0963
SNMP trap: No
Held call could not be removed successfully from music conference.

Procedure TRUNK_BARRING
Action:
Severity: Minor.
BUG0964
SNMP trap: No
Music source connection could not be dropped. Procedure

TRUNK_BARRING
Action:
Severity: Minor.
BUG0965
SNMP trap: No
Bad parameters passed to start the music or stop the music from caller.
Action:
Severity: Minor.
BUG0966
SNMP trap: No
Attendant supervisor monitored attendant's source not on line 0. Procedure

TRUNK_BARRING
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 271 of 2360

BUG0967
Attendant console to be monitored does not have its secondary TN on line one
of the same card as its prime TN; move the secondary TN. Procedure
TRUNK_BARRING
Action:
Severity: Minor.
BUG0968
SNMP trap: No
SON Call Register could not be released in start the music. Procedure
TRUNK_BARRING
Action:
Severity: Minor.
BUG0969
SNMP trap: No
Bad music trunk route parameters; find music trunk. Procedure

TRUNK_BARRING
Action:
Severity: Minor.
BUG0970
SNMP trap: No
TN two and/or three on the monitored attendant's card are currently used;
delete them. Procedure TRUNK_BARRING
Action:
Severity: Minor.
BUG0971
SNMP trap: No
One of two loops is unequipped. ULP_PTR = NIL. Format is: LOOP1, LOOP2
Action:
Severity: Minor.
BUG0972
SNMP trap: No
Unable to set new conference originator (COMCT). Procedure

TRUNK_BARRING
Action:
Severity: Minor.
BUG0973
SNMP trap: No
No conference originator found (COMCT). Procedure TRUNK_BARRING

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 272 of 2360

BUG0980
Unit type is not trunk. Procedure TRUNK_BARRING

Action:
Severity: Minor.
BUG0981
SNMP trap: No
Cannot do TNTRANS on TERTN. Procedure TRUNK_BARRING

Action:
Severity: Minor.
BUG0990
SNMP trap: No
Attempt to write to slot when not seized. Procedure RPS Memory Test
Action:
Severity: Minor.
BUG0991
SNMP trap: No
Attempt to read slot when not seized. Procedure RPS Memory Test
Action:
Severity: Minor.
BUG0992
SNMP trap: No
Attempt to seize slot while slot is already seized. Fatal error. Procedure RPS
Memory Test
Action:
Severity: Minor.
BUG0993
SNMP trap: No
SETBLKPTRS failed on DISI_LOOP. DISI

Action:
Severity: Minor.
BUG0994
SNMP trap: No
CHECK_CONTY called when no slot seized. Continuity Test

Action:
Severity: Minor.
BUG0995
SNMP trap: Yes
Attempt to seize slot while slot already seized. Fatal error. Continuity Test
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 273 of 2360

BUG0996
Attempt to issue RPD message while output in progress. Printing Routines

Action:
Severity: Minor.
BUG0997
SNMP trap: No
Output line buffer overflow. Printing Routines

Action:
Severity: Minor.
BUG0998
SNMP trap: No
Stack overflow. Fatal error. Task Stack

Action:
Severity: Minor.
BUG0999
SNMP trap: Yes
Stack underflow. Fatal error. Task Stack

Action:
Severity: Minor.
BUG1000
SNMP trap: Yes
{action TN}{current TN}{event}{action state} {state}{sub state}{process count}.

Task Stack
Action:
Severity: Minor.
BUG1001
SNMP trap: No
Data length adjusted from X to Y where: X is the original data length and Y is
the max packet data size.
Severity: Minor.
BUG1002
SNMP trap: Yes
Semaphore take error, taskSem_id=X, errno=Y.

Severity: Minor.
SNMP trap: Yes
System Messages
Page 274 of 2360

BUG1003
An Error has been captured in C++ GF code and the error is related to DCH
data structures.
Action: Please find the call scenario and contact Design/Technology group as
soon as possible.
Severity: Major.
BUG1004
SNMP trap: Yes
An Error has been captured in C++ GF code and the error is related to Call
Reference related data structures.
Action: Please try to get the call scenario and contact Design/Technology group
as soon as possible.
Severity: Major.
BUG1005
SNMP trap: Yes
An Error has been captured in C++ GF code and the error is related to Path
object.
Severity: Major.
BUG1006
SNMP trap: Yes
An Error has been captured in C++ GF code and the error is related to
Transport Interface.
Severity: Major.
BUG1007
SNMP trap: Yes
An Error has been captured in C++ GF code and the error is related to Sender
Receiver objects.
Severity: Major.
BUG1008
SNMP trap: Yes
An Error has been captured in C++ GF code and the error is related to Buffers
Data.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 275 of 2360

BUG1009
Message Handler.
Severity: Major.
BUG1010
SNMP trap: Yes
An Error has been captured in C++ GF code and the error is related to Call
Control.
Severity: Major.
BUG1011
SNMP trap: Yes
Supplementary Service.
Severity: Major.
BUG1012
SNMP trap: Yes
Operation Table.
Severity: Major.
BUG1013
SNMP trap: Yes
Invalid DN or TN in retrieving the original dialed items at SIP CD call. If the call
redirection failed, the call might not be returned to the original dialed DN.
Action:
Severity: Major.
BUG1023
SNMP trap: Yes
Illegal trunk type for PRA outgoing call. Task Stack

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 276 of 2360

BUG1300
Timeout when call is in an invalid state. RGAPM not valid. Queuing

Action:
Severity: Minor.
BUG1301
SNMP trap: Yes
TCOS value greater than 7. Queuing

Action:
Severity: Minor.
BUG1302
SNMP trap: Yes
TN translation failed for call originator. Queuing

Action:
Severity: Minor.
BUG1303
SNMP trap: Yes
Failure to set up route pointers for route in route list. Queuing

Action:
Severity: Minor.
BUG1304
SNMP trap: Yes
Inconsistent eligible route information for CBQ(a) after ERWT. Queuing

Action:
Severity: Minor.
BUG1305
SNMP trap: Yes
RGA activation occurred when call is in state that is not permitted. Queuing
Action:
Severity: Minor.
BUG1306
SNMP trap: Yes
Failure to set customer pointer (SET_CUST_PTRS) for call originator.

Queuing
Action:
Severity: Minor.
BUG1307
SNMP trap: Yes
Failure to set ESN data block pointer (ESN_DB_PTR) for call originator.
Queuing
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 277 of 2360

BUG1308
Failure to set route list pointer (ESN_RTE_LST_PTR) for call originator.

Queuing
Action:
Severity: Minor.
BUG1309
SNMP trap: Yes
Invalid SON Call Register exists when RGA activated to enter CBQ. Queuing
Action:
Severity: Minor.
BUG1310
SNMP trap: Yes
Invalid entry type for DIST_RING. Distinctive Ringing

Action:
Severity: Minor.
BUG1311
SNMP trap: Yes
SET_CUST_PTRS failure in DIST_RING. Distinctive Ringing

Action:
Severity: Minor.
BUG1312
SNMP trap: Yes
TNTRANS failure in DIST_RING. Distinctive Ringing

Action:
Severity: Minor.
BUG1313
SNMP trap: Yes
SET_ROUTE_PTRS failure in DIST_RING. Distinctive Ringing

Action:
Severity: Minor.
BUG1314
SNMP trap: Yes
PCDATAPR equals nil when call procedure SET_ESN_PTRS. Distinctive

Ringing
Action:
Severity: Minor.
BUG1316
SNMP trap: Yes
NARS - invalid source. NRS/BARS

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 278 of 2360

BUG1319
DNIS call cannot terminate because the DNIS route is not marked for
auto-terminate or IDC translation. {customer number}{route number}.
Action:
Severity: Minor.
BUG1320
SNMP trap: No
Non-ACD Call Register found on dark SDN key.

Action:
Severity: Minor.
BUG1321
SNMP trap: Yes
SNMP trap: Yes
TN Translation failed.
Action:
Severity: Minor.
BUG1322
Failed to find the route (CDR).

Action:
Severity: Minor.
BUG1323
SNMP trap: Yes
Failed to find the route (CDR).

Action:
Severity: Minor.
BUG1329
SNMP trap: Yes
Missing NARS/BARS main Call Register. Queuing.

Action:
Severity: Minor.
BUG1330
SNMP trap: Yes
SNMP trap: Yes
Bad case. Queuing

Action:
Severity: Minor.
BUG1332
Bad entry point for Individual Hold (I-Hold). Individual Hold

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 279 of 2360

BUG1333
Terminal activating I-Hold is invalid. Individual Hold

Action:
Severity: Minor.
BUG1334
SNMP trap: Yes
I-Hold orig timing out, Hold flag not set. Individual Hold
Action:
Severity: Minor.
BUG1335
SNMP trap: Yes
I-Hold ter timing out, Hold flag not set. Individual Hold
Action:
Severity: Minor.
BUG1336
SNMP trap: Yes
Invalid TN removing call from I-Hold. Individual Hold

Action:
Severity: Minor.
BUG1337
SNMP trap: Yes
Protected terminal loop block pointer is nil called by (CH.TN.CONVERT)

Queuing
Action:
Severity: Minor.
BUG1338
SNMP trap: Yes
TN to channel conversion fails called by PRINT_TN (GLOBAL3). Queuing

Action:
Severity: Minor.
BUG1339
SNMP trap: No
Digital Trunk Interface (DTI) signaling (non-ESN) encounters invalid source

parameter or invalid call type. Queuing
Action:
Severity: Minor.
BUG1340
SNMP trap: Yes
The TERTN of a NARS call is not a TRK. Queuing

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 280 of 2360

BUG1341
The Timeslot being written, already had data in its contents. TNX, TNY,
LOOPX, SLOTX, NETWORK ADDRESS, DATA0, DATA1, NTWK EVEN
MAP, NTWK ODD MAP. Queuing
Action:
Severity: Minor.
BUG1342
SNMP trap: No
The supervisor TN being moved configured with NSVC key does not equal TN
in ACD position block.
Action:
Severity: Minor.
BUG1343
SNMP trap: Yes
A call coming in on a DNIS route is not auto-terminate or idc.

Action: Intercept to attendant.
Severity: Minor.
BUG1346
SNMP trap: Yes
This item is not a trunk and cannot be idled. Procedure Abort_Call (DIGPR)
Action:
Severity: Minor.
BUG1347
SNMP trap: Yes
WRITEPDS_FIELD fails because field designated is out-of-range. Procedure

Abort_Call (DIGPR)
Action:
Severity: Minor.
BUG1348
SNMP trap: No
Procedure OPAO IN AFFECT (GLOB4) is unable to set route pointers to see

if the trunk involved is performing an OPAO call. Call Register info follows.
Procedure Abort_Call (DIGPR)
Action:
Severity: Minor.
BUG1349
SNMP trap: Yes
Procedure OPAO IN EFFECT (GLOB4) is unable to set the trunk involved

pointers to see if it is performing an OPAO call. Call Register info follows.
Procedure Abort_Call (DIGPR)
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 281 of 2360

BUG1350
Procedure REQ DTN 4 OPAO (SCTRK) could not acquire the route pointer for
the trunk being service changed to see if the route is OPR allowed. The route
number and trunk TN follows. Procedure Abort_Call (DIGPR)
Action:
Severity: Minor.
BUG1351
SNMP trap: Yes
Procedure ALL MEMBERS DTN (SCRDB) could not acquire the route
member's pointers to see if the trunk has DTN COS. Route number, member
number, and member TN to follow. Procedure Abort_Call (DIGPR)
Action:
Severity: Minor.
BUG1352
SNMP trap: Yes
ALL_MEMBERS_DTN (SCRDB) could not acquire the route member.

Customer number, Route number, and Member TN to follow.
Action:
Severity: Minor.
BUG1353
SNMP trap: No
ALL_MEMBERSDTN (SCRDB) could not find route member though member

list block said it existed. Customer number, Route number, and Member TN to
follow.
Action:
Severity: Minor.
BUG1354
SNMP trap: No
Message registration - proc MSG_REG, Itemptr should not be nil.

Action:
Severity: Minor.
BUG1355
SNMP trap: Yes
Message registration - proc INCR_CUST_MTR metorcustptr is nil.

Action:
Severity: Minor.
BUG1356
SNMP trap: Yes
Call Register marked '.SLP_STATION' is not in conference.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 282 of 2360

BUG1357
Procedure MONITOR_AUX_MSG (ADS) has an invalid Protected pointer to

the ACD block. Call Register information follows.
Action:
Severity: Minor.
BUG1358
SNMP trap: Yes
Procedure MONITOR_AUX_MSG (ADS) is unable to set up the pointers to

determine if the ACD-DN is Virtual or Actual for a specific customer. Customer
and DN follow.
Action:
Severity: Minor.
BUG1359
SNMP trap: Yes
Channel index non-existent in Prot. Cref. Table.

Action:
Severity: Minor.
BUG1360
SNMP trap: Yes
Last index is greater than Table length in ASSIGN_REFNUM.

Action:
Severity: Minor.
BUG1361
SNMP trap: Yes
TNTRANS fail in LINK_MSGCR.

Action:
Severity: Minor.
BUG1362
SNMP trap: Yes
MSGCR in UCREF_TBL is NIL but call can be rebuilt.

Action:
Severity: Minor.
BUG1363
SNMP trap: Yes
MSGCR is NIL for T.O, Answer & Disconnect.

Action:
Severity: Minor.
BUG1364
SNMP trap: Yes
Invalid state in STATE_HANDLER.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 283 of 2360

BUG1365
Invalid SOURCE in STATE_HANDLER's call state.

Action:
Severity: Minor.
BUG1366
SNMP trap: Yes
PRA TN does not match either ORIGTN or TERTN in active CR in

IDLE_B_CHANNEL.
Action:
Severity: Minor.
BUG1367
SNMP trap: Yes
TN TRANS fail in Procedure CANNOT_REBUILD.

Action:
Severity: Minor.
BUG1369
SNMP trap: Yes
Loop # out-of-range in BCH_TO_TN.

Action:
Severity: Minor.
BUG1370
SNMP trap: Yes
B channel is 0 in TN_TO_BCH.
Action:
Severity: Minor.
BUG1371
SNMP trap: Yes
Loop # missing in DCH block in TN_TO_BCH.

Action:
Severity: Minor.
BUG1372
SNMP trap: Yes
Ref # not match in UCREF_TBL in RELEASE_REFNUM.

Action:
Severity: Minor.
BUG1373
SNMP trap: Yes
Invalid MAINPM after DNTRANS for incoming call.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 284 of 2360

BUG1374
Inc MSGCR is NIL in SEND_ON_ORIG, DISC_ORIG_SIDE, INIT_MSG_CR.

Action:
Severity: Minor.
BUG1375
SNMP trap: Yes
SET_ROUTE_PTRS in ENBLOC_DIALING, TERMINATE

ENBLOC_TIMEOUT.
Action:
Severity: Minor.
BUG1376
SNMP trap: Yes
TNTRANS on ORIGTN fail in INIT_MSG_CR.

Action:
Severity: Minor.
BUG1377
SNMP trap: Yes
Setcustptrs failed in get_clid, get_prog_called, and get_redirecting.

Action:
Severity: Minor.
BUG1378
SNMP trap: Yes
CRPTR/MSGCR is not idled in LINK_MSGCR.

Action:
Severity: Minor.
BUG1379
SNMP trap: Yes
TNTRANS fail in REQUEST_OUTPUT.

Action:
Severity: Minor.
BUG1380
SNMP trap: Yes
SNMP trap: Yes
Invalid DCH pointers.

Action:
Severity: Minor.
BUG1381
PRI reported DCH is out-of-service, but it is not the one configured.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 285 of 2360

BUG1382
Invalid timeout event.

Action:
Severity: Minor.
BUG1383
SNMP trap: Yes
No channel TN for channel reset.

Action:
Severity: Minor.
BUG1385
SNMP trap: Yes
Illegal trunk type for PRA outgoing call.

Action:
Severity: Minor.
BUG1386
SNMP trap: Yes
Incoming/Outgoing Call on a non-PRA B-Channel.

Action:
Severity: Minor.
BUG1387
SNMP trap: Yes
MAINPM & AUXMP of CR that is pointed to by the priority Agent Table does
not equal : QU_ACD & .ACD_IDLE_POS_QD Procedure Idle_Prior_Agent.
Action:
Severity: Minor.
BUG1388
SNMP trap: Yes
The AGT_PRIORITY field in the CR is not within range. Procedure

Idle_Prior_Agent.
Action:
Severity: Minor.
BUG1389
SNMP trap: Yes
The index to the call reference table is 0 which should never happen. Do not
idle the call reference number.
Action: Do not idle the call reference number.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 286 of 2360

BUG1500
Parameters to NUM_DN_MEMBERS do not identify a valid SL-1 DNBLOCK.

Procedure NUM_DN_MEMBERS
Action:
Severity: Minor.
BUG1501
SNMP trap: Yes
Parameters to GET_DN_MEMBERS request an invalid DN member number.

Procedure GET_DN_MEMBERS
Action:
Severity: Minor.
BUG1502
SNMP trap: Yes
Unable to identify the required TN in GET_NEWSPEECH. Procedure

GET_NEWSPEECH
Action:
Severity: Minor.
BUG1503
SNMP trap: Yes
Unable to restore old speech path after blocking in GET_NEWSPEECH.

Procedure GET_NEWSPEECH
Action:
Severity: Minor.
BUG1504
SNMP trap: Yes
A set cannot be relocated (probably due to a clash on one of the keys).

Procedure SET_RELOCATE
Action:
Severity: Minor.
BUG1505
SNMP trap: Yes
OVL cannot Log in even though the overlay area is idle. Procedure
OVL_SUPERVISOR
Action:
Severity: Minor.
BUG1506
SNMP trap: Yes
A bad AUXPM was encountered while the MAINPM was dialing. Procedure
DIG_PR
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 287 of 2360

BUG1507
Terminal is not a valid TN. Procedure AABCS OR AAPBX

Action:
Severity: Minor.
BUG1616
SNMP trap: Yes
Procedure BUSY_LAMP: SETCUSTPRTS failed. Procedure MEET_ME

Action:
Severity: Minor.
BUG1617
SNMP trap: No
Cannot provide announcement to tandem trunks. Procedure MEET_ME

Action:
Severity: Minor.
BUG1650
SNMP trap: No
Cannot clear minor alarm until Time and Date is reset (for SAR feature).
Procedure MEET_ME
Action:
Severity: Minor.
BUG1690
SNMP trap: No
Parameters to NUM_DN_MEMBERS do not identify a valid SL-1 DNBLOCK.

Action:
Severity: Minor.
BUG1691
SNMP trap: No
Parameters to GET_DN_MEMBERS request an invalid DN member number.

Action:
Severity: Minor.
BUG1692
SNMP trap: No
Unable to identify the required TNs in GET_NEWSPEECH.

Action:
Severity: Minor.
BUG1693
SNMP trap: No
Unable to restore old speechpath after blocking in GET_NEWSPEECH.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 288 of 2360

BUG2000
The PLDN CRLINK of the CR is bad or PLDN cr is already in a queue.

Action:
Severity: Minor.
BUG2001
SNMP trap: Yes
Digital Telephones ISM counter corruption encountered. Counter is reset to 0.

Action:
Severity: Minor.
BUG2002
SNMP trap: Yes
Analogue Telephones ISM counter corruption encountered. Counter is reset

to 0.
Action:
Severity: Minor.
BUG2003
SNMP trap: Yes
Cannot send expansion SSD message to main.

Action:
Severity: Major.
BUG2004
SNMP trap: Yes
STARTUP: Cannot get %s of Cabinet %d, where s = subnet mask or IP

address, d = cabinet number
Action:
Severity: Major.
BUG2005
SNMP trap: Yes
RPC: Cannot start RPC service. Cabinet type [m] Reason [x] where m = MAIN
or IPEXP, x = <reason string>
Action:
Severity: Major.
BUG2006
SNMP trap: Yes
RPC: Server terminated. Cabinet type [m] reason [x] where m = MAIN or
IPEXP, x = <reason string>
Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 289 of 2360

BUG2007
PMON: Cannot spawn %s, errno = %p, where s = cpPmonStatusAtLinkUp or

spawnStatutsTask, p = errno
Action:
Severity: Major.
BUG2008
SNMP trap: Yes
LCS: taskSpawn failed. Failure when spawning LCS task

Severity: Critical.
BUG2009
SNMP trap: Yes
LSC: send failed in split command from overlay 35.

Action:
Severity: Info.
BUG2010
SNMP trap: Yes
LCS: send failed in cutover command from overlay 135.

Action:
Severity: Info.
BUG2011
SNMP trap: Yes
LCS: send failed in join command from overlay 135.

Action:
Severity: Info.
BUG2012
SNMP trap: Yes
LCS: send failed in gswo command from overlay 135.

Action:
Severity: Major.
BUG2013
SNMP trap: Yes
LCS: cmQSend() error, lcsMsgQId [ID], errno [err].Where [ID]: lcsMsgQIdErr:

error number
Severity: Critical.
BUG2014
SNMP trap: Yes
LCS: cmQDelete() error in lcs Send()

Severity: Critical.
SNMP trap: Yes
System Messages
Page 290 of 2360

BUG2015
LCS: cmQCreate() error in lcsSend()

Severity: Critical.
BUG2016
SNMP trap: Yes
LCS: cmQCreate() error in lcsTaskInit(), errno [err]Where err: error number

Severity: Critical.
BUG2017
SNMP trap: Yes
LCS: cmInit() error. Call to cmInit failed.

Action:
Severity: Info.
BUG2018
SNMP trap: Yes
LCS: Comm Mgr registration failed. LCS registration with communication

manager failed.
Action:
Severity: Info.
BUG2019
SNMP trap: Yes
LCS: drInitPhase2() error. Call to drInit Phase2 failed.

Action:
Severity: Info.
BUG2020
SNMP trap: Yes
LCS: voteInit() error. Call to voteInit failed.

Action:
Severity: Info.
BUG2021
SNMP trap: Yes
LCS: hbInit() error. Call to hbInit failed.

Action:
Severity: Info.
BUG2022
SNMP trap: Yes
LCS: cpmImit() error.Call to cpmInit failed.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 291 of 2360

BUG2023
LCS: <s> timer create failed in lcsTaskInit(), errno [err].Where <s> : timer
IdErr: error number
Severity: Critical.
BUG2024
SNMP trap: Yes
LCS: <s> timer connect failed, errno [err]Where <s>: timer IDErr: error number
Severity: Critical.
BUG2025
SNMP trap: Yes
LCS: <s> timer set failed.Where <s>: timer ID

Severity: Critical.
BUG2026
SNMP trap: Yes
LCS: Recovery failed.

Severity: Critical.
BUG2027
SNMP trap: Yes
LCS: Task init failed.

Severity: Critical.
BUG2028
SNMP trap: Yes
<mod>.: Unable to recover message queue [id], errno [err]. Where:<mod>:

DR, LCS[id]: drMsgQId, lcsMsgQId
Severity: Critical.
BUG2029
SNMP trap: Yes
xxx. Incoming message disregarded due to version y incompatible with current

version z.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 292 of 2360

BUG2030
LCS: Can't delete lcsMsgQId [queueId] in recovery action, errno [err].Where

[queueId] = queue ID[err] = error number
Severity: Critical.
BUG2031
SNMP trap: Yes
LCS: Can't create lcsMsgQId in recovery action, errno [err]Where [err] = error
number
Severity: Critical.
BUG2032
SNMP trap: Yes
LCS: <s> timer delete failed, errno [err].Where <s> timer name[err]: error
number
Severity: Critical.
BUG2033
SNMP trap: Yes
LCS: <s> timer create failed in lcsRecovery(), errno [err]Where <s> timer
name[err]: error number
Severity: Critical.
BUG2038
SNMP trap: Yes
LCS: hiHealthGet() error.

Action:
Severity: Info.
BUG2039
SNMP trap: Yes
LCS: vote sending failed. Send vote message through communication

manager primary channel failed.
Action:
Severity: Info.
BUG2040
SNMP trap: Yes
LCS: heartbeat sending failed. Send heartbeat message through

communication manager primary channel failed.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 293 of 2360

BUG2041
LCS: checkpoint mgr sending failed.

Action:
Severity: Major.
BUG2042
SNMP trap: Yes
LCS: disk redundancy sending failed.

Action:
Severity: Major.
BUG2043
SNMP trap: Yes
Switchover mg sending failed.

Action:
Severity: Major.
BUG2044
SNMP trap: Yes
LCS: remote LCS sending failed on primary channel.

Action:
Severity: Info.
BUG2045
SNMP trap: Yes
LCS: remote LCS sending failed on secondary channel.

Action:
Severity: Info.
BUG2046
SNMP trap: Yes
LCS: fopen() error in IcsStateSet(). fopen failed.

Action:
Severity: Info.
BUG2047
SNMP trap: Yes
LCS: fputc() error in IcsStateSet(). fputc failed.

Action:
Severity: Info.
BUG2048
SNMP trap: Yes
Failed to create semaphore for input queue state.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 294 of 2360

BUG2049
CPM: Active CPM failed to send sync data to inactive side.

Action:
Severity: Info.
BUG2050
SNMP trap: Yes
CPM: Failed to create semaphore for CPM task state.

Action: From pdt, type cpmInit to re-inialize cpm task.
Severity: Info.
BUG2053
SNMP trap: Yes
CPM: Active CPM failed to send data update message to inactive side.
Action:
Severity: Info.
BUG2055
SNMP trap: Yes
CPM: Inactive CPM failed to send syncStart message to active CPM.

Action:
Severity: Info.
BUG2061
SNMP trap: Yes
CPM: Failed to create its message queue.

Action:
Severity: Info.
BUG2062
SNMP trap: Yes
CPM: CPM task, tCpmS failed to create its input queue.

Action: From pdt, type cpmResetLocalQ to re-create the queue.
Severity: Info.
BUG2064
SNMP trap: Yes
CPM received stop update message from LCS.

Action:
Severity: Info.
BUG2065
SNMP trap: No
CPM: Failed to send message type %d to remote side.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 295 of 2360

BUG2067
CPM: Invalid message.%s passed to cpmFSM: Side= %s, State = %s.

Action:
Severity: Info.
BUG2073
SNMP trap: Yes
HIRM: Can't send create message.

Severity: Critical.
BUG2074
SNMP trap: Yes
HIRM: Failed to send create message to the other side.

Severity: Critical.
BUG2075
SNMP trap: Yes
HIRM: Could not get obj name of <p>.Where <p> is object ID

Action: From pdt, type hiRemInit to re-initialize the task.
Severity: Critical.
BUG2076
SNMP trap: Yes
HIRM: Failed to delete hiRemMsgQId [queueId], errno [err].

Severity: Critical.
BUG2078
SNMP trap: Yes
HIRM: Failed to create hiRemMsgQId, errno [err].

Severity: Critical.
BUG2079
SNMP trap: Yes
HIRM: Failed to send to hiRemMsgQId [queueId], errno [err].

Severity: Critical.
BUG2080
SNMP trap: Yes
HIRM: Failed to create tHiRem task, errno [err].

Severity: Critical.
SNMP trap: Yes
System Messages
Page 296 of 2360

BUG2081
HIRM: Failed to create new object on active side.

Severity: Critical.
BUG2082
SNMP trap: Yes
HIREM: Passed NULL object id

Severity: Critical.
BUG2083
SNMP trap: Yes
IPM: Can't send to CM.

Severity: Critical.
BUG2084
SNMP trap: Yes
A corrupted DPNSS/DASS2 trunk is created.

Action: Report the problem.
Severity: Info.
BUG2085
SNMP trap: No
Problem to get the SS7 message cr: it is missing or the link from the PRA
message cr is corrupted.
Action:
Severity: Major.
BUG2086
SNMP trap: No
BUG in BNE_HANDLER.
Action:
Severity: Minor.
BUG2090
SNMP trap: Yes
The number of ISDN B Channel TNs configured in the system is equal to or

less than zero.
Action:
Severity: Minor.
BUG2091
SNMP trap: No
The number of DTI Channel TNs configured in the system is equal to or less
than zero.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 297 of 2360

BUG2092
The number of Analog Trunk TNs configured in the system is equal to or less
than zero.
Action:
Severity: Minor.
BUG2093
SNMP trap: Yes
The number of data Port Tns configured in the system is equal to or less than
zero.
Action:
Severity: Minor.
BUG2094
SNMP trap: Yes
The number of Phantom Port Tns configured in the system is equal to or is less
than zero.
Action:
Severity: Minor.
BUG2095
SNMP trap: Yes
The number of CLASS Telephone TNs configured in the system is equal to or

less than zero.
Action:
Severity: Minor.
BUG2096
SNMP trap: Yes
The number of Attendant Console TNs configured in the system is equal to or

less than zero.
Action:
Severity: Minor.
BUG2097 msg n
SNMP trap: Yes
Invalid message type read in from remote TTY. Procedure:

REMOTETTY_MAINT. Msg =Message Type, n = Remote TTY number
Action:
Severity: Minor.
BUG2098 n
SNMP trap: Yes
Bad pointers in procedure REMOTETTY_MAINT. Could be due to invalid TTY

number n. n = Remote TTY number.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 298 of 2360

BUG2099 <return-address stack> TN, ITEMPTR, LNUM, LIGHT. Invalid input data. Procedure
BCSLAMP.
Action:
Severity: Minor.
BUG2100
SNMP trap: Yes
<HB> UDP socket creation failed for cabinet xx.

Action:
Severity: Critical.
BUG2101
SNMP trap: Yes
Cannot bind UDP socket on cabinet xx.

Action:
Severity: Critical.
BUG2102
SNMP trap: Yes
<HB> Creation of %s task failed on cabinet xx.

Action:
Severity: Critical.
BUG2103
SNMP trap: Yes
<HB> Creation of %s message queue failed on cabinet xx.

Action:
Severity: Critical.
BUG2104
SNMP trap: Yes
<HB> Wrong cabinet number : xx.

Action:
Severity: Major.
BUG2105
SNMP trap: Yes
<HB> Message queue does not exist on cabinet xx.

Action:
Severity: Major.
BUG2106
SNMP trap: Yes
<HB> Cannot create <watchdog name> for yy link on cabinet xx.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 299 of 2360

BUG2107
<HB> Cannot allocate memory for sempahore on cabinet xx.

Action:
Severity: Critical.
BUG2108
SNMP trap: Yes
<HB> Cannot start watchdog on cabinet xx.

Action:
Severity: Critical.
BUG2109
SNMP trap: Yes
<HB> Cannot allocate memory for ping structure on cabinet xx.

Action:
Severity: Info.
BUG2110
SNMP trap: Yes
<HB> Cannot get IP addresses on cabinet xx.

Action:
Severity: Critical.
BUG2111
SNMP trap: Yes
<HB> Wrong cabinet type value : xx.

Action:
Severity: Info.
BUG2112
SNMP trap: Yes
<HB> Cannot start polling mechanism between the main cabinet and the
expansion cabinet x.
Action:
Severity: Critical.
BUG2114
SNMP trap: Yes
The number of survivable cabinets configured in the system has exceeded the
limits.
Action:
Severity: Info.
BUG2120
SNMP trap: Yes
The number of ITG ISDN Trunks configured in the system is equal to or less
than zero.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 300 of 2360

BUG2121
Invalid FFC request type in case statement, for VTLN/VTLF.

Action:
Severity: Minor.
BUG2122 type
SNMP trap: Yes
Procedure FIND_EXP_TTY: invalid card type.

Action:
Severity: Minor.
BUG2129
SNMP trap: Yes
Remote TTY: Failure to create/open pipe

Action:
Severity: Major.
BUG2130
SNMP trap: Yes
Remote TTY: Failure to create socket

Action:
Severity: Major.
BUG2131
SNMP trap: Yes
Remote TTY: Failure to bind socket

Action:
Severity: Major.
BUG2132
SNMP trap: Yes
Remote TTY: Socket x failed to listen

Action:
Severity: Major.
BUG2133
SNMP trap: Yes
Remote TTY: Number of fd's is over the limit

Action:
Severity: Minor.
BUG2134
SNMP trap: Yes
Remote TTY: Select failed.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 301 of 2360

BUG2135
Remote TTY: Socket x failed to accept connection.

Action:
Severity: Major.
BUG2136
SNMP trap: Yes
Remote TTY: Failure to send pipe message x.

Action:
Severity: Minor.
BUG2137
SNMP trap: Yes
Remote TTY: Cabinet x is not in range.

Action:
Severity: Minor.
BUG2138
SNMP trap: Yes
Remote TTY: End of file received, socket x is closed.

Action:
Severity: Minor.
BUG2139
SNMP trap: Yes
Remote TTY: Error reading socket x for cabinet y

Action:
Severity: Minor.
BUG2140
SNMP trap: Yes
Remote TTY: Error writing to socket x for cabinet y.

Action:
Severity: Minor.
BUG2141
SNMP trap: Yes
The pointer to the STS_MSG_STRUC has not been initialized correctly.

Action:
Severity: Info.
BUG2142
SNMP trap: Yes
The server based application Set-t-Set Messaging has received an invalid

type of STATE_BITS form ASL when set password session is ended.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 302 of 2360

BUG2143
The served-based application Set-to-Set Messaging has received an invalid

type of EVENT_INFO from ASL when receiving password or time-out
messages.
Action:
Severity: Info.
BUG2144
SNMP trap: Yes
The status of Set-toSet Messaging cannot be turned ON if no message is

defined.
Action:
Severity: Info.
BUG2145
SNMP trap: Yes
The server-based application Set-toSet Messaging has received an invalid

type of STATE_BITS from ASL when pressing "Cancel" in the Edit mode.
Action:
Severity: Info.
BUG2146
SNMP trap: Yes
The server-based application Set-to-Set Messaging has received an invalid

type of EVENT_INFO from ASL when pressing a soft key.
Action:
Severity: Info.
BUG2147
SNMP trap: Yes
The server-based application Set-toSet messaging has received an invalid

type of STS_CMD flag from ASL STS_CMD and only take two values:
STS_START and STS_CONTINUE.
Action:
Severity: Info.
BUG2200
SNMP trap: Yes
Cannot send CardLAN IP message.

Action:
Severity: Info.
BUG2201
SNMP trap: Yes
ssdServer:can't open stream socket.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 303 of 2360

BUG2202
ssdServer: can't bind local address.

Action:
Severity: Major.
BUG2203
SNMP trap: Yes
ssdServer: can't accept connect request.

Action:
Severity: Major.
BUG2204
SNMP trap: Yes
ssdServer: undefined shelf.

Action:
Severity: Major.
BUG2208
SNMP trap: Yes
ipSsdServerRx: error reading socket.

Action:
Severity: Major.
BUG2209
SNMP trap: Yes
startSsdServer: ssd server already running.

Action:
Severity: Minor.
BUG2210
SNMP trap: Yes
startSsdServer: unable to spawn ssdServer.

Action:
Severity: Major.
BUG2211
SNMP trap: Yes
ipIntSSD: unable to initialize ssd server.

Action:
Severity: Major.
BUG2212
SNMP trap: Yes
ipIntSSD: ssdServer not registered.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 304 of 2360

BUG2213
callBackSsd: unknown server address.

Action:
Severity: Major.
BUG2214
SNMP trap: Yes
WRITE_REMOTE_SSD: undefined shelf number.

Action:
Severity: Major.
BUG2215
SNMP trap: Yes
ssdServer: Error spawning ssd server task.

Action:
Severity: Major.
BUG2216
SNMP trap: Yes
ssdClient: undefined shelf number.

Action:
Severity: Major.
BUG2217
SNMP trap: Yes
ssdClient: can't open stream socket.

Action:
Severity: Major.
BUG2218
SNMP trap: Yes
ssdClient: ssd server not responding.

Action:
Severity: Major.
BUG2219
SNMP trap: Yes
tcpCliTask: error reading socket.

Action:
Severity: Major.
BUG2220
SNMP trap: Yes
startSsdClient: client already running.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 305 of 2360

BUG2221
startSsdClient: unable to spawn ssdClient.

Action:
Severity: Major.
BUG2222
SNMP trap: Yes
ssdQCreate: Error creating message queue.

Action:
Severity: Major.
BUG2223
SNMP trap: Yes
ssdQCreate: Error spawning sl1TcpRcv task.

Action:
Severity: Major.
BUG2224
SNMP trap: Yes
ssdQCreate: Error spawning ipSsdTx task.

Action:
Severity: Major.
BUG2226
SNMP trap: Yes
ipSsdBuf: Error reading ssd msg queue.

Action:
Severity: Major.
BUG2227
SNMP trap: Yes
ipSsdTx: socket write error.

Action:
Severity: Major.
BUG2228
SNMP trap: Yes
ipSsdTx: dropping ssd msg.

Action:
Severity: Major.
BUG2229
SNMP trap: Yes
ssdQSend: error writing to ssd queue.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 306 of 2360

BUG2230
CardLAN: CardLAN handler not created.

Action:
Severity: Major.
BUG2231
SNMP trap: No
CardLAN: Failure to create message queue.

Action:
Severity: Major.
BUG2232
SNMP trap: No
CardLAN: Failure t start Tx task.

Action:
Severity: Major.
BUG2233
SNMP trap: No
CardLAN: Error reading message queue.

Action:
Severity: Minor.
BUG2234
SNMP trap: No
CardLAN: Error writing to socket x for connection x.

Action:
Severity: Minor.
BUG2235
SNMP trap: Yes
CardLAN: Failure to send message.

Action:
Severity: Minor.
BUG2236
SNMP trap: No
CardLAN: Connection not initialized.

Action:
Severity: Major.
BUG2237
SNMP trap: Yes
CardLAN: Error writing message to SL1 XIM memory.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 307 of 2360

BUG2238
CardLAN: Message is not delivered for connection x.

Action:
Severity: Minor.
BUG2239
SNMP trap: Yes
CardLAN: Error on select in Rx task.

Action:
Severity: Minor.
BUG2252
SNMP trap: Yes
100 Base T voice: Can't configure voice header.

Action:
Severity: Major.
BUG2254
SNMP trap: Yes
100 Base T Voice: Can't get remote IP address.

Action:
Severity: Major.
BUG2255
SNMP trap: Yes
100 Base T Voice: Can't get local IP address..

Action:
Severity: Major.
BUG2256
SNMP trap: Yes
100 Base T Voice: Can't get network interface.

Action:
Severity: Major.
BUG2257
SNMP trap: Yes
100 Bbase T Voice: Can't get MAC address.

Action:
Severity: Major.
BUG2258
SNMP trap: Yes
100 Base T Voice: Can't write to voice FPGA.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 308 of 2360

BUG2259
100 Base T Voice: Can't set voice PCM channel size.

Action:
Severity: Minor.
BUG2260
SNMP trap: Yes
BOOTP Client: Can't enable voice transmission.

Action:
Severity: Major.
BUG2261
SNMP trap: Yes
SNMP trap: Yes
BOOTP Client: Can't

find network interface.
Action:
Severity: Major.
BUG2262
BOOTP Client: Can't set broadcast flag.

Action:
Severity: Minor.
BUG2263
SNMP trap: Yes
BOOTP Client: Send BOOTP message failed.

Action:
Severity: Minor.
BUG2264
SNMP trap: Yes
BOOTP Server : Can't create socket.

Action:
Severity: Major.
BUG2265
SNMP trap: Yes
BOOTP Server: Can't bind to socket.

Action:
Severity: Major.
BUG2266
SNMP trap: Yes
BOOTP Server: Can't find MAC address in database.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 309 of 2360

BUG2267
BOOTP Server: Can't add entry in ARP table.

Action:
Severity: Minor.
BUG2268
SNMP trap: Yes
BOOTP Server: Can't get local IP address.

Action:
Severity: Minor.
BUG2269
SNMP trap: Yes
BOOTP Server: Can't send reply back to BOOTP client.

Action:
Severity: Major.
BUG2270
SNMP trap: Yes
100 Base T Voice: Can't spawn server.

Action:
Severity: Major.
BUG2271
SNMP trap: Yes
BOOTP Serve: Can't find subnet mask.

Action:
Severity: Minor.
BUG2272
SNMP trap: Yes
This feature supports Taurus display terminals only.

Action:
Severity: Minor.
BUG2273
SNMP trap: Yes
SNMP trap: Yes
Invalid length (count).

Action:
Severity: Minor.
BUG2275
HB: message Q create failed, errno[err]

Severity: Critical.
SNMP trap: Yes
System Messages
Page 310 of 2360

BUG2276
HB: CM register failed.

Action:
Severity: Major.
BUG2277
SNMP trap: Yes
HB: Time out msg send failed.

Action:
Severity: Major.
BUG2278
SNMP trap: Yes
HB: timer create failed. errno[err]

Severity: Critical.
BUG2279
SNMP trap: Yes
HB: timer connect failed.

Action:
Severity: Major.
BUG2280
SNMP trap: Yes
HB: message receive error. errno[err]

Severity: Critical.
BUG2281
SNMP trap: Yes
SNMP trap: Yes
HB: FSM failed.

Action:
Severity: Major.
BUG2282
HB: secondary sending failed.

Action:
Severity: Major.
BUG2283
SNMP trap: Yes
HB: primary sending failed.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 311 of 2360

BUG2284
HB: local sending failed.

Action:
Severity: Major.
BUG2286
SNMP trap: Yes
HB: receives an unexpected msg, type = %d, state = %d, channel = %d.
Action:
Severity: Major.
BUG2287
SNMP trap: Yes
SNMP trap: Yes
HB: set timer error.

Action:
Severity: Major.
BUG2290
HB: HBWaitEtherRep - HB threshold exceeded.

Action:
Severity: Major.
BUG2291
SNMP trap: Yes
HB: is in an invalid state.

Action:
Severity: Major.
BUG2292
SNMP trap: Yes
HB: task start failed. errno=[err]

Severity: Critical.
BUG2293
SNMP trap: Yes
HIREM: failed to send message to CM.

Severity: Critical.
BUG2295
SNMP trap: Yes
HB: The /U DISK have INCONSISTENT IMAGE.

Action: Try to delay ungswo by %d cycle.
Severity: Major.
SNMP trap: Yes
System Messages
Page 312 of 2360

BUG2335
CardLAN: Failure to send message.

Action:
Severity: Minor.
BUG2340
SNMP trap: Yes
CardLAN: Error reading from socket x for connection x.

Action:
Severity: Minor.
BUG2341
SNMP trap: Yes
CardLAN: Error writing to socket x for cabinet.

Action:
Severity: Minor.
BUG2342
SNMP trap: Yes
CardLAN: Failure to start server task.

Action:
Severity: Major.
BUG2343
SNMP trap: No
CardLAN: Invalid cabinet number x.

Action:
Severity: Major.
BUG2344
SNMP trap: Yes
CardLAN: Failure to start Rx task.

Action:
Severity: Major.
BUG2345
SNMP trap: No
CardLAN: Failure to open server stream socket.

Action:
Severity: Major.
BUG2346
SNMP trap: Yes
CardLAN: Failure to bind local address.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 313 of 2360

BUG2348
CardLAN: Failure to get remote IP address.

Action:
Severity: Major.
BUG2349
SNMP trap: Yes
IPM: ipmIoctl - Semaphore take failed, errno [err].

Severity: Critical.
BUG2350
SNMP trap: Yes
IPM: ipmIoctl - Semaphore give error, errno [err].

Severity: Critical.
BUG2351
SNMP trap: Yes
CardLAN: Failure to start client task.

Action:
Severity: Major.
BUG2352
SNMP trap: Yes
IPM: Can't assign IP mask to fei1.

Action:
Severity: Major.
BUG2353
SNMP trap: Yes
IPM: Can't assign IP to fei1.

Action:
Severity: Major.
BUG2361
SNMP trap: Yes
TIMESYNCCLIENT: create FAILED.

Action:
Severity: Major.
BUG2362
SNMP trap: Yes
TIMESYNCCLIENT: unknown host %s.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 314 of 2360

BUG2363
TIMESYNCCLIENT: could not open socket.

Action:
Severity: Major.
BUG2364
SNMP trap: Yes
TIMESYNCCLIENT: bind failed.

Action:
Severity: Major.
BUG2365
SNMP trap: Yes
TIMESYNCCLIENT: Can't send message to %s:%d.

Action:
Severity: Major.
BUG2366
SNMP trap: Yes
TIMESYNCCLIENT: Error in receiving message.

Action:
Severity: Major.
BUG2367
SNMP trap: Yes
TIMESYNCCLIENT: Invalid message from %s:%d.

Action:
Severity: Major.
BUG2368
SNMP trap: Yes
timeSyncInit: Error in creating msg queue.

Action:
Severity: Major.
BUG2369
SNMP trap: Yes
timeSyncInit: wdCreate FAILED.

Action:
Severity: Major.
BUG2370
SNMP trap: Yes
timeSyncRollCall: mesg Queue sending error.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 315 of 2360

BUG2372
timeSyncServer: bind failed.

Action:
Severity: Major.
BUG2373
SNMP trap: Yes
timeSyncServer: error in receiving message.

Action:
Severity: Major.
BUG2374
SNMP trap: Yes
timeSyncServer: can't send message to %s:%d.

Action:
Severity: Major.
BUG2375
SNMP trap: Yes
timeSyncServer: Invalid request receiving from %s:%d.

Action:
Severity: Major.
BUG2376
SNMP trap: Yes
timeSyncUpdateReqTask: could not open socket.

Action:
Severity: Major.
BUG2377
SNMP trap: Yes
timeSyncUpdateReqTask: bind failed.

Action:
Severity: Major.
BUG2378
SNMP trap: Yes
timeSyncUpdateReqTask: mesg queue can't receive mesg.

Action:
Severity: Major.
BUG2379
SNMP trap: Yes
timeSyncUpdateReqTask: can't send message to %s:%d.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 316 of 2360

BUG2380
timeSyncUpdateReqTask: unknown mesg retrieved from mesg queue.

Action:
Severity: Major.
BUG2381
SNMP trap: Yes
timeSyncInsertBspInetAddre: too many bsps registered with timeSyncServer.

Action:
Severity: Major.
BUG2387
SNMP trap: Yes
VOTE: voteTaskInit - cmRegister error.

Action:
Severity: Major.
BUG2388
SNMP trap: Yes
VOTE: voteRun - timer create failed.

Action:
Severity: Major.
BUG2389
SNMP trap: Yes
VOTE: voteRun - timer connect failed.

Action:
Severity: Major.
BUG2391
SNMP trap: Yes
VOTE: voteSendMsg - cmPrimarySend error, channel = x.

Action:
Severity: Major.
BUG2392
SNMP trap: Yes
VOTE: voteSendMsg - Sending to remote Vote Mgr via HSP failed.

Action:
Severity: Major.
BUG2393
SNMP trap: Yes
VOTE: voteSendMsg - cmSecondarySend error, channel = x.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 317 of 2360

BUG2394
VOTE: receives an unexpected msg, type = %d, state = %d.

Action:
Severity: Major.
BUG2395
SNMP trap: Yes
VOTE: voteFSM - set timer error.

Action:
Severity: Major.
BUG2396
SNMP trap: Yes
VOTE: voteFSM - cancel timer error.

Action:
Severity: Major.
BUG2397
SNMP trap: Yes
VOTE: vote is in an invalid state %d.

Action:
Severity: Major.
BUG2398
SNMP trap: Yes
VOTE: vote task start failed, errno=[err]

Severity: Critical.
BUG2480
SNMP trap: Yes
Disk Partition: tried to pminit ( ) with an invalid drive number.

Action:
Severity: Major.
BUG2481
SNMP trap: Yes
Disk Partition: could not create the ide device.

Action:
Severity: Major.
BUG2482
SNMP trap: Yes
Disk Partition: only found %d partitions on hard disk.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 318 of 2360

BUG2483
Disk Partition: could not create hard disk device %s.

Action:
Severity: Major.
BUG2484
SNMP trap: Yes
Disk Partition: could not initialize hard disk partition %s.

Action:
Severity: Major.
BUG2485
SNMP trap: Yes
Disk Partition: error initializing partitions.

Action:
Severity: Major.
BUG2488
SNMP trap: Yes
Disk Partition: received an invalid IDE drive to attach.

Action:
Severity: Major.
BUG2489
SNMP trap: Yes
Disk Partition: received an invalid partition number to attach.

Action:
Severity: Major.
BUG2492
SNMP trap: Yes
Disk Partition: format requested on invalid drive number.

Action:
Severity: Major.
BUG2493
SNMP trap: Yes
Disk Partition: could not fill out format config information.

Action:
Severity: Major.
BUG2494
SNMP trap: Yes
Disk Partition: unable to format partition %s.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 319 of 2360

BUG2495
Disk Partition: unable to find the active partition.

Action:
Severity: Major.
BUG2496
SNMP trap: Yes
Disk Partition: could not attach device to DOS for formatting.

Action:
Severity: Major.
BUG2497
SNMP trap: Yes
Disk Partition: unable to open partition %s for formatting.

Action:
Severity: Major.
BUG2498
SNMP trap: Yes
Disk Partition: unable to format partition %s.

Action:
Severity: Major.
BUG2499
SNMP trap: Yes
Disk Redundancy: pminit ( ) failed.

Action:
Severity: Major.
BUG2500
SNMP trap: Yes
Disk Redundancy: drSmallInit ( ) failed.

Action:
Severity: Major.
BUG2501
SNMP trap: Yes
Disk Redundancy: psInit ( ) failed.

Action:
Severity: Major.
BUG2503
SNMP trap: Yes
Disk Redundancy: partition selector could not find device matching one
requested.
Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 320 of 2360

BUG2504
Disk Redundancy: couldn't mount partition %s.

Action:
Severity: Info.
BUG2505
SNMP trap: Yes
Disk Redundancy: asked to create a NULL dr device.

Action:
Severity: Major.
BUG2506
SNMP trap: Yes
Disk Redundancy: not enough memory for redundant device.

Action:
Severity: Major.
BUG2507
SNMP trap: Yes
Disk Redundancy: not enough memory for ps device.

Action:
Severity: Major.
BUG2508
SNMP trap: Yes
Disk Redundancy: could not install Partition Selector driver.

Action:
Severity: Major.
BUG2509
SNMP trap: Yes
Disk Redundancy: could not add PS device %s.

Action:
Severity: Major.
BUG2510
SNMP trap: Yes
Disk Redundancy: asked to send a NULL message.

Action:
Severity: Major.
BUG2511
SNMP trap: Yes
Disk Redundancy: sending to LCS failed.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 321 of 2360

BUG2512
DR: send message to CM queue failed.

Severity: Critical.
BUG2513
SNMP trap: Yes
DR: asked to send to unknown destination or unknown message. Destination

<d>, message type <d>.
Action:
Severity: Info.
BUG2514
SNMP trap: Yes
Disk Redundancy: got an invalid device during drBigInit.

Action:
Severity: Major.
BUG2515
SNMP trap: Yes
DR: could not create <s> semaphore, errno[err]

Severity: Critical.
BUG2516
SNMP trap: Yes
DR: could not spawn DR task.

Severity: Critical.
BUG2517
SNMP trap: Yes
DR: tried to take recovery action and failed.

Severity: Critical.
BUG2518
SNMP trap: Yes
<Mod>: Receive from <s> [id] failed, errno [err]. Recreating the
queueWhere:<Mod> = module name : DR, HIREM,LCS<s> = queue name:
drMsgQId, hiRemMsgQId,, lcsMsgQId<err>: error number
Severity: Major.
BUG2519
SNMP trap: Yes
DR: failed to delete drMsgQId [id] during recovery, errno [err].

Severity: Critical.
SNMP trap: Yes
System Messages
Page 322 of 2360

BUG2520
DR: failed to create drMsgQId during recovery, errno [err]

Severity: Critical.
BUG2521
SNMP trap: Yes
DR: failed to create drMsgQId during drTaskInit(), errno [err].

Severity: Critical.
BUG2522
SNMP trap: Yes
Disk Redundancy: could not register with CM.

Action:
Severity: Major.
BUG2523
SNMP trap: Yes
DR: could not create drSyncQId queue, errno [err]

Severity: Critical.
BUG2524
SNMP trap: Yes
DR: Cannot start disk-sync due to file corrupt in local disk. Please re-install
both software & database on this side!
Severity: Critical.
BUG2525
SNMP trap: Yes
DR: drMsgQId full. Failed to send disk resync message.

Severity: Critical.
BUG2526
SNMP trap: Yes
Disk Redundancy: failed to create drMsgQ during recovery.

Action:
Severity: Major.
BUG2527
SNMP trap: Yes
DR: Cannot clear message queue, %s: id [0x%x], errno

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 323 of 2360

BUG2530
LCS: fopen() error in lcsStateGet(). fopen failed.

Action:
Severity: Info.
BUG2531
SNMP trap: Yes
LCS: fputc(1) error in lcsStateGet(). fputc failed.

Action:
Severity: Info.
BUG2532
SNMP trap: Yes
LCS: fgetc() error in lcsStateGet(). fgetc failed.

Action:
Severity: Info.
BUG2533
SNMP trap: Yes
LCS: fputc() error in lcsStateGet() .fputc failed.

Action:
Severity: Info.
BUG2541
SNMP trap: Yes
LCS:Invalid message sent from LCS to disk redundancy.

Action:
Severity: Info.
BUG2542
SNMP trap: Yes
LCS: Invalid message sent to remote LCS.

Action:
Severity: Info.
BUG2543
SNMP trap: Yes
LCS: Invalid msg: %s in state:%s.

Action:
Severity: Info.
BUG2544
SNMP trap: Yes
SNMP trap: Yes
LCS: Invalid state: %s.

Action:
Severity: Info.
System Messages
Page 324 of 2360

BUG2545
LCS: SWO init error. Graceful SWO locked.

Severity: Critical.
BUG2551
SNMP trap: Yes
SNMP trap: Yes
LCS: ipmInit() error.

Action:
Severity: Info.
BUG2572
File system operation (operation type) error on

pathname, CPU side, errno.
Severity: Major.
BUG2575
SNMP trap: Yes
Disk Redundancy: Slave received sync block out of range.

Action:
Severity: Major.
BUG2576
SNMP trap: Yes
Disk Redundancy: Slave received too few syn blocks.

Action:
Severity: Major.
BUG2577
SNMP trap: Yes
DR: received unknown message, type <d>

Action:
Severity: Info.
BUG2579
SNMP trap: Yes
DR: Can't send to drMsgQId [semId]. Queue is full, trying to resync.

Severity: Major.
BUG2580
SNMP trap: Yes
Disk Redundancy: problem flushing file system during disk sync.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 325 of 2360

BUG2581
Disk Redundancy: requested to stop disk sync during disk sync.

Action:
Severity: Info.
BUG2582
SNMP trap: Yes
Disk Redundancy: disk sync did not complete.

Action:
Severity: Major.
BUG2583
SNMP trap: Yes
Disk Redundancy: error sending message during disk sync.

Action:
Severity: Major.
BUG2584
SNMP trap: Yes
DR: Can't spawn disk sync task,errno [err]

Severity: Critical.
BUG2586
SNMP trap: Yes
Disk Redundancy: disk sync not allowed because of mismatching disks.

Action:
Severity: Major.
BUG2587
SNMP trap: Yes
DR: Can't take drBlockSem [semId], errno [err]

Severity: Critical.
BUG2588
SNMP trap: Yes
DR: Cannot create the signal file (%s) on core side %d.
Severity: Critical.
BUG2589
SNMP trap: Yes
DR: Can't take drStateSem [semId], errno [err] Where semId is the semaphore
ID Err is the error number
Severity: Critical.
SNMP trap: Yes
System Messages
Page 326 of 2360

BUG2590
DR: Cannot remove the signal file (%s) after disk-sync is completed.
Action:
Severity: Major.
BUG2620
SNMP trap: Yes
Ethernet Telephones ISM counter encountered corruption. Counter is reset to

0.
Action:
Severity: Minor.
BUG2621
SNMP trap: Yes
The maximum license limit has been reached for the number of IP Phones
type 2002 and 2004 and IP Softphones type 2050 allowed to be configured in
the system. Software counting error has been detected.
Action: Report the problem to customer support.
Severity: Minor.
BUG2622
SNMP trap: Yes
Virtual TN call processing problem occurs.

Action:
Severity: Minor.
BUG2623
SNMP trap: Yes
type 2001 allowed to be configured in the system. Software counting error has
been detected.
Action: Report the problem to customer support.
Severity: Minor.
BUG3000
SNMP trap: Yes
Invalid state in APL module. {APL_SOURCE} {INVALID_TYPE} {INVALID

DATA}. The event is ignored. Procedure APL
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 327 of 2360

BUG3001
Message CR to link into APL output queue is not in idle queue.

{APL_SOURCE} {APL_DATA} {APL_PTR} {PRIORITY} {LINK NUMBER}
{BLOCK PTR} {BUG_PRINT_CR}. The message CR is not linked to the APL
output queue. Procedure APL
Action:
Severity: Minor.
BUG3002
SNMP trap: Yes
Queue data block for the APL output queue is not associated.
{APL_SOURCE} {APL_DATA} {APL_PTR} {APL_NUMBER} {BLOCK_PTR}
{LINK_Q_HDR} {BUG_PRINT_CR}. The event is ignored. Procedure APL
Action:
Severity: Minor.
BUG3003
SNMP trap: Yes
The message CR in APL output queue is not set to the .QU_APL_OP when
removing the CR from the queue. {APL_SOURCE} {APL_DATA} {APL_PTR}
{APL_NUMBER} {BLOCK_PRT} {BUG_PRINT_CR}. If back link is formed,
QUEUE_IN is updated to QU_APL_OP. Procedure APL
Action:
Severity: Minor.
BUG3004
SNMP trap: Yes
APL output handler has a request to send messages and the specific link is
not defined in configuration. {APLINKOP} {APL_REQ_TO_SEND}
{APL_RDY_TO_SEND}. Clear the request. Procedure APL
Action:
Severity: Minor.
BUG3005
SNMP trap: Yes
There is a request to send output messages and the output queue is empty.
{APL_SOURCE} {ACTIVE_APL} {APLINKOP} {APL_REQ_TO_SEND}
{APL_PHY_NUM} {U_APL_PTR} {QUEUE_PTR} {LINK_Q_HDR}. Clear the
request. Procedure APL
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 328 of 2360

BUG3006
The length of the input message is either too small or too large. {APP_TYPE}
{MSG_TYPE} {PACKET_IDX} {MESSAGE_LENGTH} {APL_ NUMBER}
{MSG_SIZE_PTR} {U_APL_PTR}. Ignore the input message. Procedure APL
Action:
Severity: Minor.
BUG3007
SNMP trap: Yes
The length of the output message is too large. {APL_SOURCE}

{ACTIVE_APL} {APLINKOP} {APL_NUMBER} {MESSAGE LENGTH}
{MESSAGE TYPE} {CUSTOMER NUMBER} {APPLICATION NUMBER}.
Action:
Severity: Minor.
BUG3010
SNMP trap: Yes
Invalid state for procedure SEND_MSG. {MESSAGE TYPE} {APPLICATION}

{LINK_NUMBER} {CUSTOMER #} {MSG_DATA} {MSG_PTR} {CR_PTR}
{USER_PTR}. Ignore the event. Procedure APL
Action:
Severity: Minor.
BUG3011
SNMP trap: Yes
Invalid state for PROC_IMS_I_MSG Procedure APL

Action:
Severity: Minor.
BUG3012
SNMP trap: Yes
Message type out-of-range {MESSAGE TYPE}. Ignore the message.

Procedure APL
Action:
Severity: Minor.
BUG3013
SNMP trap: Yes
Application type out-of-range {APPLICATION NUMBER} Ignore the message.

Procedure APL
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 329 of 2360

BUG3014
Link number out-of-range {LINK NUMBER}. Ignore the message. Procedure

APL
Action:
Severity: Minor.
BUG3015
SNMP trap: Yes
The message length of the output message is either too small or too large.
{MESSAGE TYPE} {APPLICATION} {MESSAGE LENGTH}. Ignore the
message. Procedure APL
Action:
Severity: Minor.
BUG3016
SNMP trap: Yes
Store the digits into orig DN of the output message exceed the size of the field.
{POINTER TO THE MESSAGE CR}. Ignore additional digits.
Action:
Severity: Minor.
BUG3050
SNMP trap: Yes
Network call is blocked because of an invalid source to the signaling module.

Action:
Severity: Minor.
BUG3051
SNMP trap: Yes
Invalid (undefined) call type.

Action:
Severity: Minor.
BUG3052
SNMP trap: No
Number to be displayed is negative.

Action:
Severity: Minor.
BUG3053
SNMP trap: Yes
Number cannot be represented in the specified number of digits.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 330 of 2360

BUG3054
Invalid TMG state.

Action:
Severity: Minor.
BUG3055
SNMP trap: Yes
TMG unable to find ACD CR.

Action:
Severity: Minor.
BUG3060
SNMP trap: Yes
ACD pointers corrupted.

Action:
Severity: Minor.
BUG3067
SNMP trap: Yes
Network control data block has not been defined.

Action:
Severity: Minor.
BUG3068
SNMP trap: No
Invalid (unidentified) sub-call type. Also occurs when LD 36 is used with a

remote maintenance phone to dial an ISL TIE line. TRK017 occurs if the call
is answered.
Action:
Severity: Minor.
BUG3069
SNMP trap: No
Test line event out-of-range.

Action:
Severity: Minor.
BUG3070
SNMP trap: Yes
Invalid event Test LINE_PM.

Action:
Severity: Minor.
BUG3071
SNMP trap: Yes
SNMP trap: Yes
Invalid test line timeout.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 331 of 2360

BUG3072
Customer Translation failed.

Action:
Severity: Minor.
BUG3073
SNMP trap: Yes
SNMP trap: Yes
TN translation failed.
Action:
Severity: Minor.
BUG3074
BLOCK_CALL should not be returned from procedure CHECK_SAT_RTE.

Action:
Severity: Minor.
BUG3075
SNMP trap: Yes
Invalid return code from procedure CHECK_SAT_RTE.

Action:
Severity: Minor.
BUG3076
SNMP trap: Yes
Pointer to conference block equals NIL.

Action:
Severity: Minor.
BUG3077
SNMP trap: No
Point to protected loop block equals NIL.

Action:
Severity: Minor.
BUG3078
SNMP trap: No
Loop type does not equal conference loop.

Action:
Severity: Minor.
BUG3080
SNMP trap: No
Invalid source for NXFER.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 332 of 2360

BUG3081
Initial TNTRANS call failed in TELSET (TST); status (Generic update. Status
update attempt abandoned) {end}
Action:
Severity: Minor.
BUG3082
SNMP trap: Yes
Initial SETCUSTPTRS call failed in TST (status update). Status update

attempt is abandoned.
Action:
Severity: Minor.
BUG3083
SNMP trap: Yes
Invalid TST calling parameter. Status update attempt is ignored.

Action:
Severity: Minor.
BUG3085
SNMP trap: Yes
TNTRANS call failed after AUX reply received by Status Update.

Action: Continue looking for valid TN with same DN.
Severity: Minor.
BUG3091
SNMP trap: Yes
Invalid directory number mix.

Action:
Severity: Minor.
BUG3092
SNMP trap: Yes
Bad CALL_PARK entry point.

Action:
Severity: Minor.
BUG3093
SNMP trap: Yes
Bad PM when CALL_PARK_BIT is set.

Action:
Severity: Minor.
BUG3094
SNMP trap: Yes
System Park ID is not valid.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 333 of 2360

BUG3095
Returned System Park ID out-of-range.

Action:
Severity: Minor.
BUG3096
SNMP trap: Yes
Returned System Park ID invalid.

Action:
Severity: Minor.
BUG3097
SNMP trap: No
TNTRANS on originator failed in procedure ORIG_IS_SAT.

Action:
Severity: Minor.
BUG3098
SNMP trap: No
SET_ROUTE_PTRS failed in procedure ORIG_IS_SAT.

Action:
Severity: Minor.
BUG3099
SNMP trap: No
TNTRANS on either ORIG or TER. TN in HELD_ON failed procedure

CHECK_SAT_RITE.
Action:
Severity: Minor.
BUG4000
SNMP trap: No
TNTRANS failed in NSIG module.

Action:
Severity: Minor.
BUG4001
SNMP trap: No
Call Register idled when SON CR still linked.

Action:
Severity: Minor.
BUG4002
SNMP trap: Yes
TRKS called from DIGPR: ORIG_ITEM not a trunk.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 334 of 2360

BUG4003
TRKS called from DIGPR: ORIG and TER both not trunks.
Action:
Severity: Minor.
BUG4005
SNMP trap: No
Lost time slot idle Call Register.

Action:
Severity: Minor.
BUG4006
SNMP trap: Yes
Lost time slot reserved path lost when getting a new one.
Action:
Severity: Minor.
BUG4007
SNMP trap: Yes
BSD call cut off at path find.

Action:
Severity: Minor.
BUG4008
SNMP trap: No
BSD call cut off at path idle.

Action:
Severity: Minor.
BUG4009
SNMP trap: No
Invalid display message type for the BGD.

Action:
Severity: Minor.
BUG4011
SNMP trap: Yes
DNTRANS value indicates that the ACD-DN entered after the Display key was
pressed is/is not an ACD-DN. However, ACD pointers cannot be set on this
DN (procedure ACD-DN Digits). This BUG message appears on the DDSP
Module.
Action:
Severity: Minor.
BUG4012
SNMP trap: Yes
DN key lock-up prevented. Trunk in readied state ringing set.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 335 of 2360

BUG4013
Unable to set up route pointers for NFCR toll clock.

Action:
Severity: Minor.
BUG4014 data
SNMP trap: Yes
Invalid state-event combination. Data: trk_tn source fgd_inc_pm.

Action:
Severity: Minor.
BUG4015 data
SNMP trap: Yes
ACTIVE CR of FGD_ITEM is NIL. Data output is trktn source fgd_ini_pm.

Action:
Severity: Minor.
SNMP trap: Yes
BUG4016 loop ts n0 n1 Cannot read Network Card control memory. Output: Loop = superloop
number, ts = timeslot, n0 = NWKdata0, n1 = NWKdata1
Action:
Severity: Minor.
SNMP trap: Yes
BUG4017 loop ts n0 n1 Cannot write data into Network Card control memory. Output: Loop =
superloop number, ts = timeslot, n0 = NWKdata0, n1 = NWKdata1
Action:
Severity: Minor.
BUG4019
SNMP trap: No
The PRI loop is not a primary DCH or a secondary DCH loop. It is a data
corruption. With the D channel number and the loop number check the PRI
loop block.
Action:
Severity: Minor.
BUG4021
SNMP trap: Yes
At Attendant Alternate Answering (AAA) timeout, the attendant is neither the

ORIG nor TER party. AAA is only applicable to the attendant. Procedure
AAA_Timeout
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 336 of 2360

BUG4023 IFC x DCHNO y An invalid DCH_Interface_ID was encountered. Either the value is
out-of-range or the interface is not expected in the logic which issued the bug.
Where: x = DCH_Interface_ID, y = D channel number.
Action:
Severity: Minor.
BUG4025
SNMP trap: Yes
Cannot determine if XTRUNK value is Universal Trunk (NT8D14) or E&M

Dictation Trunk (NT8D15).
Action:
Severity: Minor.
BUG4026
SNMP trap: No
Invalid entry into procedure NMC_HANDLER.

Action:
Severity: Minor.
BUG4027
SNMP trap: Yes
An out-of-range ISDN message index has been detected while building a

message. Message cannot be correctly encoded.
Action:
Severity: Minor.
BUG4030
SNMP trap: Yes
An Analog Line Card (NT8D03) supported PBX set (500/2500 type) went
off-hook but the mainpm in the associated Call Register was improper. The
mainpm was not RINGING, ESTABLISHED, CAMPON, CWAITING,
SPECIAL, RAN_WAITING, nor was it CDR. Software will idle the call.
Action:
Severity: Minor.
BUG4031 ssd tn
SNMP trap: Yes
An Analog Line Card (NT8D03) supported 500 set sent an input message for
a dialed digit with more than 10 pulses, thus interpreted by software to be an
invalid dialed digit. Software will ignore this input. In X11 Release 17 the input
SSD message and TN are output.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 337 of 2360

BUG4032
Pointer to PSDL Output CR is NIL.

Action:
Severity: Minor.
BUG4036
SNMP trap: Yes
NIL pointer in procedure call.

Action: Do a SYSLOAD; on continued failure, contact supplier. CAUTION:
SYSLOAD interrupts call processing.
Severity: Minor.
BUG4037
SNMP trap: Yes
Possible corruption of memory (global pointer).

Severity: Minor.
BUG4038
SNMP trap: Yes
Attempt to idle a Call Register with a NIL pointer.

Severity: Minor.
BUG4039
SNMP trap: Yes
Possible corruption of memory (global variable).

Severity: Minor.
BUG4041
SNMP trap: Yes
Possible corruption of memory (global variable).

Severity: Minor.
BUG4042
SNMP trap: Yes
Possible corruption of memory (data).

Severity: Major.
SNMP trap: Yes
System Messages
Page 338 of 2360

BUG4043
PSDL procedure called with an invalid command.

Severity: Minor.
BUG4044
SNMP trap: Yes
Disk manager must release the old user before it can assign a new user to the
disk.
Action:
Severity: Minor.
BUG4045
SNMP trap: Yes
SS CR holds invalid information

Action:
Severity: Minor.
BUG4046
SNMP trap: Yes
Invalid Facility I.E. information received.

Action:
Severity: Minor.
BUG4047
SNMP trap: Yes
This Service Identifier is not supported by TCAP.

Action:
Severity: Minor.
BUG4048
SNMP trap: Yes
The Local Transaction code is missing in SS CR.

Action:
Severity: Minor.
BUG4049
SNMP trap: Yes
Invalid Service discriminator received in TCAP.

Action:
Severity: Minor.
BUG4050
SNMP trap: Yes
Missing component type in SS CR.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 339 of 2360

BUG4051
Mandatory information for request output is missing.

Action:
Severity: Minor.
BUG4057
SNMP trap: Yes
Global XI_UTILS called with dataptr = NIL.

Action:
Severity: Minor.
BUG4058
SNMP trap: Yes
Attendant Alternate Answering (AAA) task ID is out-of-range. Global

procedure AAA_ALT_ANS.
Action:
Severity: Minor.
BUG4059
SNMP trap: Yes
Attendant Alternate Answering (AAA) timing should not already be active.

Procedure AAA_START_TIME.
Action:
Severity: Minor.
BUG4060
SNMP trap: Yes
Attendant Alternate Answering (AAA) timing was not done in the 2 second
queue. Procedure AAA_STOP_TIME.
Action:
Severity: Minor.
BUG4061
SNMP trap: Yes
PSW packet length exceeds output buffer length.

Action:
Severity: Minor.
BUG4062
SNMP trap: Yes
Pointer is nil for input block or storage buffer.

Action:
Severity: Minor.
BUG4063
SNMP trap: Yes
Undefined auxiliary customer pointer. This message applies to Release 15.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 340 of 2360

BUG4064
Illegal parameter passed to WRT_AWU_CU.

Action:
Severity: Minor.
BUG4065
SNMP trap: Yes
Cannot get AWU timeslot.

Action:
Severity: Minor.
BUG4068
SNMP trap: Yes
ACTIVECR or MSG_CRPTR of the U_TRK_BLOCK is NIL in Procedure

O_NO_GL_CHNEGO. PRA_TN is printed.
Action:
Severity: Minor.
BUG4069
SNMP trap: Yes
PD-DTI_IDLE_SLOT is called to remove a reserved timeslot but the reserved

timeslot count is already zero.
Action:
Severity: Minor.
BUG4070
SNMP trap: No
XMI-Message did not enqueue.

Action:
Severity: Minor.
BUG4071
SNMP trap: Yes
XMI-Incomplete message found in queue.

Action:
Severity: Minor.
BUG4072 loop
SNMP trap: Yes
XMI-New message started without finishing the previous message. This may
be a Network Card or Peripheral Controller firmware problem.
Action:
Severity: Minor.
BUG4076
SNMP trap: Yes
XMI-Message to idle must first be removed from a queue.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 341 of 2360

BUG4078
XMI-Message has a bad type (usually greater than 127).

Action:
Severity: Minor.
BUG4079
SNMP trap: Yes
XMI-Unknown application number.

Action:
Severity: Minor.
BUG4080
SNMP trap: Yes
An out-of-range index has been detected for the "Type of Number" field
contained in some ISDN information elements. The field cannot be correctly
encoded or decoded.
Action:
Severity: Minor.
BUG4081
SNMP trap: Yes
An out-of-range index has been detected for the 'Numbering Plan' field
contained in some ISDN information elements. The field cannot be correctly
encoded or decoded.
Action:
Severity: Minor.
BUG4082
SNMP trap: Yes
Intercept Computer (IPC) package does not support more than 4 digit DNs.
Action:
Severity: Minor.
BUG4108
SNMP trap: No
Incoming msg not allowed for this application.

Action:
Severity: Minor.
BUG4109
SNMP trap: Yes
SNMP trap: Yes
VAS ID out-of-range.
Action:
Severity: Minor.
System Messages
Page 342 of 2360

BUG4110
Invalid source to ESDI_MAINT.

Action:
Severity: Minor.
BUG4111
SNMP trap: Yes
Invalid ESDI input. May be generated under certain conditions if the port is
connected to an application that is busy. Example Option 11C with Meridian
Mail. This is design intent, however if message persist, contact technical
support.
Action:
Severity: Minor.
BUG4112
SNMP trap: Yes
Invalid source to CSL_MAINT procedure.

Action:
Severity: Minor.
BUG4113
SNMP trap: Yes
Database error. For example, CLS_PM does not match the global word
CSL_ACTIVE, CSL STANDBY.
Action:
Severity: Minor.
BUG4114
SNMP trap: Yes
When there is a disconnect msg received on SATN but the flag in maintenance
CR indicates it is not set up yet. Software error.
Action:
Severity: Minor.
BUG4115
SNMP trap: No
SADM with class of service of CMS but cannot find CSL block with matching
SATN.
Action:
Severity: Minor.
BUG4116
SNMP trap: Yes
SNMP trap: Yes
CSL CR pointer is NIL.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 343 of 2360

BUG4117
MRID is not found in the CSL CR.

Action:
Severity: Minor.
BUG4120
SNMP trap: Yes
No MRID could be allocated to an originating call to IS/DS services.

Action:
Severity: Minor.
BUG4124
SNMP trap: Yes
Unprotected Unit block is missing from terminal TN. Cannot set speechpath on
LI Loop.
Action:
Severity: Minor.
BUG4125
SNMP trap: Yes
Message CE is not in QU_NONE.

Action:
Severity: Minor.
BUG4126
SNMP trap: Yes
Output queue is not allocated.

Action:
Severity: Minor.
BUG4127
SNMP trap: Yes
Message CR ID is not .QU_CSL_OP.

Action:
Severity: Minor.
BUG4128
SNMP trap: Yes
Output message has length zero.

Action:
Severity: Minor.
BUG4129
SNMP trap: Yes
Output message exceeds link frame length. Check N1 parameter in Overlay

17.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 344 of 2360

BUG4130
DLI_AUDIT_TYPE was not set up when either DTI_LOOP_INIT or

DTI_PWR_INIT was set.
Action:
Severity: Minor.
BUG4135
SNMP trap: No
Invalid ESDI_pm or ESDI_Auxpm.

Action:
Severity: Minor.
BUG4138
SNMP trap: Yes
Failed to set ACD pointers when canceling/answering a RGA on ACD call.

Action:
Severity: Minor.
BUG4139
SNMP trap: Yes
TNTRANS failed when canceling/answering RGA or ACD entry or handling

BCS time-out. date: customer number, ACD DN, ACD entry, *(crptr).
Action:
Severity: Minor.
BUG4140
SNMP trap: Yes
ACD key is not configured on the TN when RGA or handling BCS time-out.
data: customer number, ACD DN, ACD entry, *(crptr).
Action:
Severity: Minor.
BUG4150
SNMP trap: Yes
An incoming CSL DATA message has been received with an invalid message
subtype. {message type} {message subtype} {VAS ID} {customer number}.
Parameters are in hex.
Action:
Severity: Minor.
BUG4151
SNMP trap: Yes
CSL_COADMIN has been called with an invalid source. Parameter is in hex.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 345 of 2360

BUG4152
CSAI/CSLDATA_MSG has been called with an invalid CSL DATA message

subtype. Parameters are in hex.
Action:
Severity: Minor.
BUG4153
SNMP trap: Yes
An incoming CSL DATA data service DN message has been received, but the
CSL link (stored in the message Call Register) does not translate to a valid
VAS ID. Parameter is in hex.
Action:
Severity: Minor.
BUG4155
SNMP trap: Yes
Flag indicates that an incoming CSL CONFIRM message has been received
from the Server, but CSL_MSGPTR is NIL.
Action:
Severity: Minor.
BUG4156
SNMP trap: Yes
DSDN_VAS_TBL_PTR for that customer is NIL. {message type} {message
subtype} {VAS ID} {customer number} {data service DN} {access code}.
Action:
Severity: Minor.
BUG4158
SNMP trap: Yes
customer number (from the message) is invalid. {message type} {message
subtype} {VAS ID} {customer number} {data service DN} {access code}.
Action:
Severity: Minor.
BUG4159
SNMP trap: Yes
An incoming CSL DATA delete data service DN message has been received
and the data service DN exists, but the entry for that DN is not in the
DSDN_LIST. {message type} {message subtype} {VAS ID} {customer
number} {data service DN} {access code}. Parameters are in hex.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 346 of 2360

BUG4160
An incoming CSL DATA delete data service DN message has been received
and the data service DN exists, But no entries are defined for that customer
and VAS Server. {message type} {message subtype} {VAS ID} {customer
number} {data service DN} {access code}. Parameters are in hex.
Action:
Severity: Minor.
BUG4161
SNMP trap: Yes
CSAI - not able to build alpha block, should not occur since alpha TNs were
already checked.
Action:
Severity: Minor.
BUG4162
SNMP trap: Yes
Flag indicates reception of CSL CONFIRM message, but CSL_MSGPRT is

not a CSL message CR.
Action:
Severity: Minor.
BUG4163
SNMP trap: Yes
Flag indicates reception of CSL CONFIRM message, but CSL_MSGPRT is

not a CONFIRM message.
Action:
Severity: Minor.
BUG4164
SNMP trap: Yes
Flag indicates reception of CSL CONFIRM message, but customer number is

wrong.
Action:
Severity: Minor.
BUG4165
SNMP trap: Yes
Flag indicates reception of CLS CONFIRM message, but from wrong Server.
Action:
Severity: Minor.
BUG4200
SNMP trap: Yes
Trunk TN failed TNTRANS. Procedure TEN_SET_UP_CPG.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 347 of 2360

BUG4201
Station TN failed TNTRANS. Procedure TEN_SET_UP_CPG.

Action:
Severity: Minor.
BUG4202
SNMP trap: Yes
Caller is neither a trunk nor a station. Procedure TEN_SET_UP_CPG.

Action:
Severity: Minor.
BUG4203
SNMP trap: Yes
Message to Digital set should not use BCS output buffer. Procedure BCSOP
Action:
Severity: Minor.
BUG4204
SNMP trap: Yes
Invalid input command from digital sets. Procedure TCM_INPUT_MSG.

Action:
Severity: Minor.
BUG4205
SNMP trap: Yes
Invalid input for procedure HANDLE_CMD_A.

Action:
Severity: Minor.
BUG4206
SNMP trap: Yes
Invalid input for procedure HANDLE_B1.

Action:
Severity: Minor.
BUG4207
SNMP trap: Yes
Invalid input for procedure HANDLE_B4.

Action:
Severity: Minor.
BUG4208
SNMP trap: Yes
Invalid input for procedure HANDLE_CMD_C.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 348 of 2360

BUG4209
Invalid input for procedure TOUCH_KEY_FUNC & TOUCH_KEY_FUNC2.

Action:
Severity: Minor.
BUG4210
SNMP trap: Yes
Invalid input for procedure TOUCH_CP.

Action:
Severity: Minor.
BUG4211 yyyy
SNMP trap: Yes
Invalid input for procedure FIXED_KEY. yyyy = the fixed key number
Action:
Severity: Minor.
BUG4212 yyyy
SNMP trap: Yes
Invalid input for procedure ProGRAMMABLE_KEY. yyyy = BCS_FUNCTION.

Action:
Severity: Minor.
BUG4213
SNMP trap: Yes
Invalid input for procedure TOUCH_LOCAL_COMM

Action:
Severity: Minor.
BUG4214
SNMP trap: Yes
Invalid input command for maintenance.

Action:
Severity: Minor.
BUG4215
SNMP trap: Yes
Invalid input command for compact dial pad digit. DIAL_PAD.

Action:
Severity: Minor.
BUG4216
SNMP trap: Yes
Excess invalid input messages from digital sets. Every input message is
counted. When the total count reaches a limit, this bug message will be printed
and the count is reset to zero.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 349 of 2360

BUG4217
Unit equipped message is received from given TN when unit is active on call.
Action:
Severity: Minor.
BUG4219
SNMP trap: Yes
Invalid output command. Procedure TCM_OUTPUT_MSG

Action:
Severity: Minor.
BUG4220
SNMP trap: Yes
Invalid input command for maintenance mode.

Action:
Severity: Minor.
BUG4221
SNMP trap: Yes
Unit unequipped message is received.

Action:
Severity: Minor.
BUG4222
SNMP trap: Yes
Display is equipped, but displayblkptr is nil.

Action:
Severity: Minor.
BUG4223
SNMP trap: Yes
VCE_TN_ORIG call is set on data TN Call Register but active Call Register of
voice TN equals nil.
Action:
Severity: Minor.
BUG4224
SNMP trap: Yes
CMC_ON bit is set but current PROT_INDEX is not CMC and CDRCR is equal
to end-of-queue.
Action:
Severity: Minor.
BUG4225
SNMP trap: Yes
AMP analog Call Register pointer equal nil.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 350 of 2360

BUG4226
Change_to_data procedure is called when the data TN is in orig_TN.

Action:
Severity: Minor.
BUG4227
SNMP trap: Yes
Invalid AUXPM in attendant queue.

Action:
Severity: Minor.
BUG4228
SNMP trap: Yes
Active loop does not equal non-active but SRPTR and DES equal nil.
Action:
Severity: Minor.
BUG4230
SNMP trap: Yes
IDLESTATION - neither the SRCPTR or DESTPTR equal CRPTR.

Action:
Severity: Minor.
BUG4231
SNMP trap: Yes
SETLAMPSTATE: SSDKEY passed is greater than the sets last key.

Action:
Severity: Minor.
BUG4232
SNMP trap: Yes
LED required but not present on key.

Action:
Severity: Minor.
BUG4233
SNMP trap: Yes
Attempted tds ringtone connection for digital set. Procedure

APPLYRINGTONE
Action:
Severity: Minor.
BUG4234
SNMP trap: Yes
Ringslot-junc = 1 and station is not a digital set. Procedure REMRINGTONE

(GLOB1).
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 351 of 2360

BUG4235
Procedure CHK_FOR_DATA. Called with wrong parameter.

Action:
Severity: Minor.
BUG4236
SNMP trap: Yes
Attempt to send data message and neither the ORIGTN or TERTN in the call
Action:
Severity: Minor.
BUG4237
SNMP trap: Yes
Voice TN answers or originates data call but fails TNTRANS.

Action:
Severity: Minor.
BUG4238
SNMP trap: Yes
Attempt to idle data CR that was originated by the voice TN but there is no
corresponding CR in the voice TN active CR. Procedure CMD_DATA_IDLE
Action:
Severity: Minor.
BUG4239
SNMP trap: Yes
Voice TN originated data call in progress but data TN fails TNTRANS or is

disabled. Procedure CHANGE_TO_DATA TCM INPUT_MSG. Procedure
CMD_ILDE TCM OUTPUT_MSG
Action:
Severity: Minor.
BUG4240
SNMP trap: Yes
Procedure TSET_DATA_CALL SL-TOUCH updated to data initiation state

and there has been no positive response from TADA.
Action:
Severity: Minor.
BUG4241
SNMP trap: Yes
Procedure DATA_RGA_ACCEPT RGA key is not defined properly for data TN

at ring-again-accept time.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 352 of 2360

BUG4242
CRPTR is equal to nil.

Action:
Severity: Minor.
BUG4243
SNMP trap: Yes
Active Call Register if voice set does not equal CPTR CMD_DATA_CFD
(digital telephones).
Action:
Severity: Minor.
BUG4244
SNMP trap: Yes
SNMP trap: Yes
TNTRANS failed.
Action:
Severity: Minor.
BUG4246
Buzz (bcs2) unit type is not a bcs unit.

Action:
Severity: Minor.
BUG4247
SNMP trap: Yes
Invalid ran route and customer.

Action:
Severity: Minor.
BUG4248
SNMP trap: No
Procedure MAX. KEYLINKS passed. Unit type is not a BCS unit.

Action:
Severity: Minor.
BUG4249
SNMP trap: Yes
GET_EXT_UNIT called for a non-terminal loop TN. Must fix calling procedure
to process TN in an alternate manner.
Action:
Severity: Minor.
BUG4250
SNMP trap: Yes
TNTRANS failed on NFCR abort-call.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 353 of 2360

BUG4251
Invalid course for RES_SCBCS.

Action:
Severity: Minor.
BUG4252
SNMP trap: Yes
Invalid return from Procedure RAN Required.

Action:
Severity: Minor.
BUG4253
SNMP trap: Yes
ACD TOF call bit set on non-active incalls key of agent (ACD).
Action:
Severity: Minor.
BUG4254
SNMP trap: No
ACD pointers of Target or Source cannot be set. Procedure: Fail2.

Action:
Severity: Minor.
BUG4255
SNMP trap: Yes
This source ACD DN cannot be added to this target ACD DN because it is

already servicing the maximum amount of flow-queue (INIT).
Action:
Severity: Minor.
BUG4256
SNMP trap: Yes
Invalid AUXPM. Procedures link into TOF queue and scan Overflow TOF
queue.
Action:
Severity: Minor.
BUG4257
SNMP trap: Yes
CONF PTR passed to CONF6_CONTROL (DIGPR) is nil.

Action:
Severity: Minor.
BUG4258
SNMP trap: Yes
Invalid conference loop passed to CONF6_CONTROL (DIGPR).

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 354 of 2360

BUG4259
Invalid Party ID for SLP conference disconnect.

Action:
Severity: Minor.
BUG4260
SNMP trap: No
TN Trans failure on SLP calling party.

Action:
Severity: Minor.
BUG4261
SNMP trap: No
TN Trans failure on SLP dialed party

Action:
Severity: Minor.
BUG4262
SNMP trap: No
SLP call found on Attendant destination

Action:
Severity: Minor.
BUG4263
SNMP trap: No
Cannot set ATTN PTRS (atgb2).

Action:
Severity: Minor.
BUG4266
SNMP trap: Yes
What has occurred: Invalid call signaling msg.

Action:
Severity: Minor.
BUG4267
SNMP trap: Yes
What has occurred: CRPTR = nil after from DIGPROC.

Action:
Severity: Minor.
BUG4268
SNMP trap: Yes
What has occurred: Invalid MAINPM for interflowed call.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 355 of 2360

BUG4269
IDC translation failed. Call intercept to attendant.

Action:
Severity: Minor.
BUG4270
SNMP trap: Yes
Invalid constant at X25_call.

Severity: Minor.
BUG4271
SNMP trap: No
Return NIL ptr at RCV_CALL_ACCEPTED.

Action:
Severity: Minor.
BUG4272
SNMP trap: No
PS not found at receive BNR.

Severity: Minor.
BUG4273
SNMP trap: No
PS not found at receive_RR.

Severity: Minor.
BUG4274
SNMP trap: No
PS not found at X25_flow_input.

Severity: Minor.
BUG4275
SNMP trap: No
Invalid constant at X25_handler.

Severity: Minor.
BUG4276
SNMP trap: No
Invalid constant at proto_conv.

Severity: Minor.
SNMP trap: No
System Messages
Page 356 of 2360

BUG4277
Return NIL ptr at proto_conv.

Severity: Minor.
BUG4278
SNMP trap: No
TTY_IO_PTR = NIL at ISDNAP_IN.

Severity: Minor.
BUG4279
SNMP trap: No
U_CSL_PTR=NIL at ISDNAP_IN.
Severity: Minor.
BUG4280
SNMP trap: No
DEVICE=NIL at load_buf.
Severity: Minor.
BUG4281
SNMP trap: No
TTY_IO_PTR =NIL at load_buf.

Severity: Minor.
BUG4282
SNMP trap: No
Invalid constant at X25_restart.

Severity: Minor.
BUG4283
SNMP trap: No
This procedure should not be called at RZC_restart_cnfirm.

Severity: Minor.
BUG4284
SNMP trap: No
Invalid lay 3_state at REC_Restart_cnfrm.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 357 of 2360

BUG4285
Invalid constant at X25_state_mgr.

Severity: Minor.
BUG4286
SNMP trap: No
Invalid lay 3_state at Do_X25_input.

Severity: Minor.
BUG4287
SNMP trap: No
Invalid VC state at validate_state.

Severity: Minor.
BUG4288
SNMP trap: No
Invalid P4 state at check_P4 state.

Severity: Minor.
BUG4289
SNMP trap: No
Cannot find active LCN at DO_X25_output.

Severity: Minor.
BUG4290
SNMP trap: No
Invalid constant at Recv_bad_pkt.

Severity: Minor.
BUG4291
SNMP trap: No
Invalid constant at X25_Timer.

Severity: Minor.
BUG4292
SNMP trap: No
VC_Timer_ptr=NIC at Set_VC_Timer.
Severity: Minor.
SNMP trap: No
System Messages
Page 358 of 2360

BUG4293
VC_Timer_ptr=NIC at clr_VC_Timer.
Severity: Minor.
BUG4294
SNMP trap: No
X25_link_Tim_ptr=NIC at Set x25_Tim_T10.

Severity: Minor.
BUG4295
SNMP trap: No
X25_link_Tim_ptr=NIC at clr_X25_Tim_T10.
Severity: Minor.
BUG4296
SNMP trap: No
No user_Num found at X25_VC_Set_ptr.

Severity: Minor.
BUG4297
SNMP trap: No
Invalid_output pkt at upd_out_stat.

Severity: Minor.
BUG4298
SNMP trap: No
NIL ptr found at Init_X25_link.

Severity: Minor.
BUG4299
SNMP trap: No
NIL ptr found at init_X25_VC.

Severity: Minor.
BUG4300
SNMP trap: No
The NET_CR_PTR of the Call Register in use is not in the addon range.
Further use of this pointer will cause corruption. NET_CR_PTR (X08 Rls 10).
Pretranslation PM not zeroed (X11).
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 359 of 2360

BUG4301
Invalid addon type passed to procedure IDLE_CR_ADDON or procedure

GET_CR_ADDON. ADDON_TYPE (X08 Rls 10). Pretranslation PM incorrect,
second pass (X11).
Action:
Severity: Minor.
BUG4302
SNMP trap: Yes
Incoming networking trunk call dropped due to system inability to allocate a

networking addon. *(CRPTR X08 Rls 10). Pretranslation PM incorrect, second
pass (X11).
Action:
Severity: Minor.
BUG4303
SNMP trap: Yes
Incoming networking trunk call dropped due to system loss of networking

addon. *(CRPTR) (X08 Rls 10). TN pointer is not loaded (PLORIGPTR = NIL)
(X11).
Action:
Severity: Minor.
BUG4304
SNMP trap: Yes
Outgoing networking trunk call aborted due to system loss of networking

addon. *(CRPTR) (X08 Rls 10). Non-existent calling type (X11).
Action:
Severity: Minor.
BUG4305
SNMP trap: Yes
Attempt to idle addon failed due to invalid addon pointer. ADDON_PTR (X08
Rls 10). Customer data-pointer is nil (X11).
Action:
Severity: Minor.
BUG4310
SNMP trap: Yes
During the setup of an optimized conference, the original calls' Call Register
was found not to have an addon (conference setup will continue) (X08 Rls 10).
Auto relocate TN not found on a digital telephone (X11).
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 360 of 2360

BUG4321
CH_TN_CONVERT failed (X08 DTI). Supervisor package is equipped, prime

TN must be on unit 0 or 4 (X11).
Action:
Severity: Minor.
BUG4322
SNMP trap: Yes
DTI2_HANDLER: DTI2_O_ABCD or DTI2_I_ABCD invalid signal type

requested by software (X08 DTI). Supervisor package is equipped, secondary
TN must be on unit 1 or 5 (X11).
Action:
Severity: Minor.
BUG4323
SNMP trap: Yes
DTI2_HANDLER: CONVRT_TIME_UNIT. Time unit out-of-range (X08 DTI).

Supervisor package is equipped, units 2 and 3 must be free of stations (X11).
Action:
Severity: Minor.
BUG4326
SNMP trap: Yes
Invalid originator for Interflow, Night Call Forward (X11) or Busy Tone calls.
Action:
Severity: Minor.
BUG4327
SNMP trap: Yes
Back_PTR equals nil for Night Call Forward (X11). DT12_HANDLER:

DT12_INPUT, DT12_I_PPM or DT12_I_ABCD. Invalid TN (X08 DTI).
Action:
Severity: Minor.
BUG4332
SNMP trap: Yes
Procedure SEARCH_ROUTE module DIGLB: LAST_SELECTED out of

bounds.
Action:
Severity: Minor.
BUG4336
SNMP trap: No
Analog PPM procedure called for digital trunk channel. Prints TN an PPM
module TASK parameter (X08 DTI). Error source passed into
ACD_COLL_STATS (X11).
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 361 of 2360

BUG4337
Invalid return code to try_interflow from procedure check_IFDN (X11). Digital

PPM procedure called for analog trunk. Prints TN and PPM module TASK
parameter (X08 DTI).
Action:
Severity: Minor.
BUG4338
SNMP trap: Yes
Invalid return code to ran_timing from procedure check_NCFW_dn (X11).

Invalid source for digital trunks (X08 DTI).
Action:
Severity: Minor.
BUG4341
SNMP trap: Yes
TTY10BLK_PTL=NIL at FREE_U_X25_DATA.
Severity: Minor.
BUG4342
SNMP trap: No
U_DATA_BLK_PTR=NIL at FREE_U_X25_DATA.
Severity: Minor.
BUG4343
SNMP trap: No
X25_I_PTR=NIL at FREE_U_X25_DATA.
Severity: Minor.
BUG4344
SNMP trap: No
X25_O_PTR=NIL at FREE_U_X25_DATA.
Severity: Minor.
BUG4345
SNMP trap: No
U_X25_BLK_PTR=NIL at FREE_U_X25_DATA.
Severity: Minor.
BUG4346
SNMP trap: No
Invalid case at X25 handler.

Severity: Minor.
SNMP trap: No
System Messages
Page 362 of 2360

BUG4347
Invalid X25 link with standby (CSLM). X25 link has no standby.
Action:
Severity: Minor.
BUG4348
SNMP trap: No
Son Cr type set_Ring_cr linked to the main cr is not equal to that on the timing
queue.
Action:
Severity: Minor.
BUG4349
SNMP trap: Yes
PARM_INDIC has been set to incorrect value in "STOR" ACD Load

Management Command. There is a software bug in module ACDL, procedure
IN_PARM_INDIC to an unexpected value.
Action:
Severity: Minor.
BUG4356
SNMP trap: Yes
Invalid trunk tn found when checking for the R2 mod feature.

Action:
Severity: Minor.
BUG4357
SNMP trap: Yes
Invalid route found in module mfc.

Action:
Severity: Minor.
BUG4358
SNMP trap: Yes
Invalid CMF TN found on a R2 mod trunk.

Action:
Severity: Minor.
BUG4360
SNMP trap: Yes
TNTRANS failed in module mfc.

Action:
Severity: Minor.
BUG4375
SNMP trap: Yes
NIL ptr found at init_X25_VC.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 363 of 2360

BUG4376
X25_U_VC_ptr=NIC at update_V.
Severity: Minor.
BUG4377
SNMP trap: No
X25_U_blk_ptr=NIL at upd_lay3_state.
Severity: Minor.
BUG4378
SNMP trap: No
X25_U_VC_ptr=NIC at upd_data_xfer.
Severity: Minor.
BUG4379
SNMP trap: No
Invalid constant at flow handler.

Severity: Minor.
BUG4380
SNMP trap: No
No clr_call for PVC at DO_SND_CLR_IND.

Severity: Minor.
BUG4381
SNMP trap: No
Procedure RSANI Invalid source for procedure call. *(CRPTR)

Action:
Severity: Minor.
BUG4382
SNMP trap: Yes
Procedure BCSTO. Invalid TN found in TERMINAL. *CRPTR)

Action:
Severity: Minor.
BUG4383
SNMP trap: Yes
Procedure LIN500TO. Invalid source for procedure call. *(CRPTR)

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 364 of 2360

BUG4384
Procedure LIN500TO. Invalid ORIGTN found in TERMINAL. *(CRPTR)

Action:
Severity: Minor.
BUG4385
SNMP trap: Yes
Procedure LIN500TO. Invalid TERTN found in TERMINAL. *(CRPTR)

Action:
Severity: Minor.
BUG4386
SNMP trap: Yes
Procedure ATTENDANTTO _ Invalid TN found in TERMINAL. *(CRPTR)

Action:
Severity: Minor.
BUG4387
SNMP trap: Yes
Procedure RLA. Invalid TN found in TERMINAL. *(CRPTR)

Action:
Severity: Minor.
BUG4390
SNMP trap: Yes
ACD_ITEMPTR is not an ACD agent.

Action:
Severity: Minor.
BUG4391
SNMP trap: Yes
Cannot set pointers for ACD Agent.

Action:
Severity: Minor.
BUG4392
SNMP trap: Yes
Agents template pointer is NIL.

Action:
Severity: Minor.
BUG4393
SNMP trap: Yes
Agents account CR never released.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 365 of 2360

BUG4394
ACNT key is on a non-lamp key number.

Action:
Severity: Minor.
BUG4395
SNMP trap: Yes
Bad source into ACD_ACNT_Code Procedure.

Action:
Severity: Minor.
BUG4396
SNMP trap: Yes
ACNT key in FLASHING state.

Action:
Severity: Minor.
BUG4397
SNMP trap: Yes
Account Code CR equals NIL and ACD_ACNT_IN_PROG bit set in active CR.
Action:
Severity: Minor.
BUG4398
SNMP trap: Yes
ACNT key WINKING or LIT, but agent not active on ACD call.
Action:
Severity: Minor.
BUG4500
SNMP trap: Yes
BREAKIN: Incorrect task number passed to BKI_MAIN.

Action:
Severity: Minor.
BUG4501
SNMP trap: Yes
BREAKIN: SAVE_BKI_SLDT: TN is not an attendant.

Action:
Severity: Minor.
BUG4502
SNMP trap: Yes
BREAKIN: RECONSTRUCT_BKI. Attempt to reconstruct simple call with

nonexistent terminal(s).
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 366 of 2360

BUG4503
BREAKIN: SET_UP_BKIN: INTICR failed.

Action:
Severity: Minor.
BUG4504
SNMP trap: Yes
BREAKIN: RECONSTRUCT_CALL: SAVESLOT is nonexistent.

Action:
Severity: Minor.
BUG4510
SNMP trap: Yes
CRPTR = NIL (FTC_HANDLER).

Action:
Severity: Minor.
BUG4511
SNMP trap: Yes
FTC table does not exist. Table 0 used.

Action:
Severity: Minor.
BUG4553
SNMP trap: Yes
X25-SET-PTR failed.
Severity: Minor.
BUG4554
SNMP trap: No
Invalid case # at X25 handler.

Severity: Minor.
BUG4555
SNMP trap: No
Invalid LAY3 state at X25.

Severity: Minor.
BUG4556
SNMP trap: No
X25_VC_Set_ptr failed at X25.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 367 of 2360

BUG4557
IO BLOCKLINK=NIL at X25.
Action: Investigate data corruption.
Severity: Minor.
BUG4558
SNMP trap: No
U_CSL_PTR=NIL at X25.
Severity: Minor.
BUG4559
SNMP trap: No
Device address=NIL.
Severity: Minor.
BUG4560
SNMP trap: No
IDN key on non-lamp key

Action:
Severity: Minor.
BUG4561
SNMP trap: Yes
Invalid treatment found for DND treatment options.

Action:
Severity: Minor.
BUG4562
SNMP trap: Yes
PREO =1, and Pretrans block =NIL

Action:
Severity: Minor.
BUG4563
SNMP trap: Yes
Pretranslation block pointer is NIL.

Action:
Severity: Minor.
BUG4564 t
SNMP trap: Yes
Parameter downloading failed: invalid xcard_type t passed to the procedure

Param_Download.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 368 of 2360

BUG4565 loop
Parameter downloading failed: loop is undefined or is not a superloop.

Action:
Severity: Minor.
BUG4566 loop s
SNMP trap: Yes
Parameter downloading failed. Peripheral Controller is undefined for given

address.
Action:
Severity: Minor.
BUG5000
SNMP trap: Yes
Operation not defined (NAS).

Action:
Severity: Minor.
BUG5001
SNMP trap: Yes
Tag not defined for operation (NAS).

Action:
Severity: Minor.
BUG5002
SNMP trap: Yes
Value not defined for this primitive (NAS).

Action:
Severity: Minor.
BUG5003
SNMP trap: Yes
Cannot call ENCODE with a sequence (NAS).

Action:
Severity: Minor.
BUG5004
SNMP trap: Yes
Primitive not valid for this operation (NAS).

Action:
Severity: Minor.
BUG5005
SNMP trap: Yes
Problem during setup of operation (NAS).

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 369 of 2360

BUG5006
Invalid originating TN (ORIGTN) in Call Register during NAS.

Action:
Severity: Minor.
BUG5007
SNMP trap: Yes
Invalid customer number. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5008
SNMP trap: Yes
Nil pointer to NAS alternatives (insert digits). Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5009
SNMP trap: Yes
No digits to be inserted for NAS routing. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5010
SNMP trap: Yes
Wink not valid for NAS (Fast Flash). Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5011
SNMP trap: Yes
Lamp state out-of-range or not allowed. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5012
SNMP trap: Yes
Invalid NAS check. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5013
SNMP trap: Yes
TNTRANS failed in NAS related procedure. Procedure nas_check_ptrs.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 370 of 2360

BUG5014
Warning: BKI Term node executing original code. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5015
SNMP trap: Yes
Invalid call state for invoking of attendant control Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5016
SNMP trap: Yes
Attempt to invoke attendant control on non BCS/PBX unit, or by a non-NAS

attendant. Procedure nas_check_ptrs.
Action:
Severity: Minor.
BUG5017
SNMP trap: Yes
Return-error or return-result received for attendant control when no invoke

was sent. Procedure nas_check_ptrs.
Action:
Severity: Minor.
BUG5018
SNMP trap: Yes
Invalid call state to receive return result or return error for attendant control.
Procedure nas_check_ptrs.
Action:
Severity: Minor.
BUG5019
SNMP trap: Yes
Attendant control operation received in an invalid PRA message. Procedure

nas_check_ptrs.
Action:
Severity: Minor.
BUG5020
SNMP trap: Yes
Far end reject of ring held party activation. Procedure nas_check_ptrs.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 371 of 2360

BUG5021
Invalid PRA message or state for ring held party operation reception.
Action:
Severity: Minor.
BUG5022
SNMP trap: Yes
Invalid onhook or offhook message received. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5023
SNMP trap: Yes
Onhook or offhook called for a call not involved with an ISDN trunk. Procedure
nas_check_ptrs.
Action:
Severity: Minor.
BUG5024
SNMP trap: Yes
Invalid case for reception of ring held party activation. Procedure

nas_check_ptrs.
Action:
Severity: Minor.
BUG5025
SNMP trap: Yes
Problem idling SSMSGCR at end of PRA. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5026
SNMP trap: Yes
Break-in encountered invalid data. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5027
SNMP trap: Yes
Unexpected return value from nas_routing in PRA, digproc or NARS.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 372 of 2360

BUG5028
NIL msg_crptr in the ulpraprt. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5029
SNMP trap: Yes
Problem in SETCUSTPTRS. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5030
SNMP trap: Yes
Cannot idle NARS Call Register. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5032
SNMP trap: Yes
Camp-On desired party ringing, however last message received not as

expected. Procedure nas_check_ptrs.
Action:
Severity: Minor.
BUG5033
SNMP trap: Yes
Unexpected EVENT received at tandem node. Procedure nas_check_ptrs.

Action:
Severity: Minor.
BUG5035
SNMP trap: Yes
Unexpected condition in NAS anti-tromboning procedure or related procedure.

Action:
Severity: Minor.
BUG5041
SNMP trap: Yes
SNMP trap: Yes
Invalid Source (NACD).

Action:
Severity: Minor.
BUG5042
Invalid package type (NACD).

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 373 of 2360

BUG5043
Invalid message type (NACD).

Action:
Severity: Minor.
BUG5044
SNMP trap: Yes
Invalid state (NACD). Procedure Invalid State.

Action:
Severity: Minor.
BUG5045
SNMP trap: Yes
Invalid return from NITE_TRMT_REQD (NACD).

Action:
Severity: Minor.
BUG5046
SNMP trap: Yes
Invalid AUXPM (NACD). Procedure LINK_INTO_TOF_Q

Action:
Severity: Minor.
BUG5047
SNMP trap: Yes
Call has not been removed from the queue (NACD). Procedure
LINK_IN_MIDDLE
Action:
Severity: Minor.
BUG5048
SNMP trap: Yes
Incorrect Access Code (ACOD) length (NACD). Procedure SEND_LOG_REQ

Action:
Severity: Minor.
BUG5049
SNMP trap: Yes
Parameters are too long for Call Request or Status Exchange (NACD).
Procedure SEND_LOG_REQ, or SEND_STAT_EXCH
Action:
Severity: Minor.
BUG5050
SNMP trap: Yes
Cannot create son cr (NACD). Procedure SEND_LOG_REQ,

NACD_AGT_AVAIL, SEND_CALLSETUP, NACD_CALLSETUP.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 374 of 2360

BUG5051
Cannot set ACD pointers (NACD). Procedure SET_ACD_PTRS,

SET_2ND_ACD_PTRS, NACD_NETQ_PROC
Action:
Severity: Minor.
BUG5052
SNMP trap: Yes
Cannot find father CR (NACD). Procedure CALL_REQ_TO,

NACD_CALLSETUP, NACD_NETQ_PROC.
Action:
Severity: Minor.
BUG5053
SNMP trap: Yes
The duration tag is missing (NACD). Procedure CALL_REQ_TO

Action:
Severity: Minor.
BUG5054
SNMP trap: Yes
CRPTR is not set to the main CR. Procedure NACD_AGT_AVAIL,

SEND_CALLSETUP, NACD_CALLSETUP, SEND_NOVF,
CLEAN_UP_ROSE_CR.
Action:
Severity: Minor.
BUG5055
SNMP trap: Yes
Cannot find the TCAP CR. Procedure NACD_AGT_AVAIL,

NACD_AGT_UNRESV, RESERV_TIMER_TO, NACD_ALERT,
NACD_NETQ_PROC.
Action:
Severity: Minor.
BUG5056
SNMP trap: Yes
Cannot remove Target Node. Procedure NACD_AGT_AVAIL,

NACD_AGT_UNRESEV, RESERV_TIMER_TO, NACD_CALLSETUP,
AGT_FREE_SENT
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 375 of 2360

BUG5057
Cannot TNTRANS Agent. Procedure NACD_BUZZ_TO, DECR_AGT_DIS,

NACD_CALLSETUP
Action:
Severity: Minor.
BUG5058
SNMP trap: Yes
Cannot TNTRANS Originating TN for Main CR. Procedure

SEND_CALLSETUP.
Action:
Severity: Minor.
BUG5059
SNMP trap: Yes
Main & AUXPM are incorrect on Agent's CR. Procedure NACD_CALLSETUP

Action:
Severity: Minor.
BUG5060
SNMP trap: Yes
Agent's keylink not set correctly. Procedure NACD_CALLSETUP.

Action:
Severity: Minor.
BUG5061
SNMP trap: Yes
Cannot remove son by PTR. Procedure NACD_ALERT

Action:
Severity: Minor.
BUG5062
SNMP trap: Yes
TERTYPE is not a trunk CR. Procedure CLEAN_UP_RESECR

Action:
Severity: Minor.
BUG5063
SNMP trap: Yes
Invalid AUXPM. Procedure REMOVE_FR_Q, NACD_RET_TO_Q

Action:
Severity: Minor.
BUG5064
SNMP trap: Yes
Trying to remove a call that is in the 128 ms queue. Procedure

REMOVE_FR_Q
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 376 of 2360

BUG5065
Invalid Agent Priority. Procedure REMOVE_FR_Q

Action:
Severity: Minor.
BUG5067
SNMP trap: Yes
Main CR indicates NACD_PROC son, but the AUX_CRLINK is nil. Procedure

NACD_REM_LOC, NACD_LINK_LOC.
Action:
Severity: Minor.
BUG5069
SNMP trap: Yes
No trunk ACOD in the NACD_ROSE_CR to use as an originating DN.

Action:
Severity: Minor.
BUG5070
SNMP trap: Yes
Invalid reason code given in the Procedure DO_REASON.

Action:
Severity: Minor.
BUG5071
SNMP trap: Yes
The AUX_CRLINK for this Call Register is corrupted. It exceeds the maximum
number of son Call Registers allowed.
Action:
Severity: Minor.
BUG5072
SNMP trap: Yes
Procedure REMOVE was called incorrectly to remove the call from the register
that was linked to the ACD Call Request queue.
Action:
Severity: Minor.
BUG5073
SNMP trap: Yes
% In procedure IDLECR, the destined callregister is already in idle queue.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 377 of 2360

BUG5074
Cannot find the Message CR for this data base request transaction. Message
will not be sent.
Action:
Severity: Minor.
BUG5075
SNMP trap: Yes
Invalid Timer type encountered in 2 s queue, NACD will idle the CR.
Action:
Severity: Minor.
BUG5076
SNMP trap: Yes
Resend timer time-out occurred in an invalid application state. The CR will be

idled.
Action:
Severity: Minor.
BUG5077
SNMP trap: Yes
BLOCK_PTR is not in the ACD queue. Procedure REMOVE_FR_Q

Action:
Severity: Minor.
BUG5078
SNMP trap: Yes
BLOCK_PTR in not in a Call Register. Procedure REMOVE_FR_Q

Action:
Severity: Minor.
BUG5081 T xxxx
SNMP trap: Yes
An invalid timer value is present in the procedure PRA_GET_TIMER. Where:

T= Timer identified and xxxx= timer value
Severity: Minor.
BUG5082 xx
SNMP trap: Yes
Invalid numbering type in msg cr for International Interface. Where: xx =

number type
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 378 of 2360

BUG5083 xx
Invalid Message type from SEND_ON_ORIG (PRA). Where: xx = Message

Type
Action:
Severity: Minor.
BUG5084
SNMP trap: Yes
PRA_O_GL_CRPTR of the PRA_MSG_CR is NIL in O_GLARE_CHNEGO.

Action:
Severity: Minor.
BUG5087
SNMP trap: Yes
TNTRANS on the alternate B-channel failed in Procedure INC_CH_NEGO.

CHANNEL_TN is printed.
Action:
Severity: Minor.
BUG5088
SNMP trap: Yes
An invalid digit has been detected in the message CR while encoding a

number for an outgoing ISDN message. The number was skipped and not put
in the outgoing message.
Action:
Severity: Minor.
BUG5089
SNMP trap: Yes
An invalid type was found for the Timer 1 Auxiliary Timing block. Global: DCH
Handler. Procedure AUX_TIMER1_TO. Field: DCH_AUX_T1_TYPE
Action:
Severity: Minor.
BUG5090 tn
SNMP trap: Yes
NIL value returned for the key template address for this Digital Set. The set
must be redefined in the data base. Procedure GET_TEMPL_PTR
Action:
Severity: Minor.
BUG5092
SNMP trap: Yes
DATA_PTR has exceeded MAX_DATA-PTR. PRS BV16048

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 379 of 2360

BUG5093
Processing pointer for specified queue is nil QU_ID.

Action:
Severity: Minor.
BUG5094
SNMP trap: Yes
DATA_PTR or MAX_DATA_PTR is corrupted.

Action:
Severity: Minor.
BUG5095
SNMP trap: No
Tone cr could not be removed from list of sons (Periodic Camp-on Tone
feature).
Action:
Severity: Minor.
BUG5096
SNMP trap: Yes
The DN programmed as a forwarding DN is not an internal DN, or does not

exist.
Action:
Severity: Minor.
BUG5097
SNMP trap: Yes
The DN programmed as a forwarding DN is not a single appearance DN.

Action:
Severity: Minor.
BUG5098
SNMP trap: Yes
The DN programmed as a forwarding DN is not a secretary set.

Action:
Severity: Minor.
BUG5099
SNMP trap: Yes
ORIGTN has been programmed as both a Boss and a Secretary telephone

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 380 of 2360

BUG5100
Warning: FIFO treatment of Q is not provided. DIGPROC is returning a

different CR back onto one of the ATTN Qs processed by WKSD. Call
processing still works. *(CRPTR)
Action:
Severity: Minor.
BUG5101
SNMP trap: Yes
Loop is not an RPE2 loop or necessary loop blocks do not exist.

Action:
Severity: Minor.
BUG5102
SNMP trap: Yes
RPE2 group is automatically spared but there is no group pointer.

Action:
Severity: Minor.
BUG5104
SNMP trap: Yes
No timeslot is available for RPE2 call rebuild.

Action:
Severity: Minor.
BUG5106
SNMP trap: Yes
The In-band ANI route found is not an auto-terminating route. All IANI routes
should be auto-terminating.
Action:
Severity: Minor.
BUG5107
SNMP trap: Yes
DLAMP is in an invalid state (greater than .lit)

Action:
Severity: Minor.
BUG5108
SNMP trap: Yes
CRPTR is not in range when L DISCONNECT is requested.

Action: Notify the attendant to release the SRC/DEST if this occurs. The
disconnect message is ignored and there may be a stuck path.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 381 of 2360

BUG5110
The CRPTR is not in range when a release is requested during an

ATTN_RLS_CALL.
Action: Notify the attendant to release the SRC/DEST if this occurs. If the
release is not allowed and the request is ignored, there may be a stuck path.
Severity: Minor.
SNMP trap: Yes
BUG5112 tn1 tn2 y s Slot Y has been reserved as a re-usable slot for tn1, but the NWK memory
shows that Slot s is also active for tn2. Global Procedure FINDONEWAY.
Local Procedure CHK_VALID_REUSE
Action:
Severity: Minor.
BUG5113 tn s
SNMP trap: Yes
Slot s is marked as a re-usable slot assigned to tn, but its RESERV_COUNT

field is zero in the U_SLOT_SHARE_BLK. Global Procedure IDLEONEWAY.
Local Procedure DTI_IDLE_SLOT
Action:
Severity: Minor.
BUG5114
SNMP trap: Yes
TFM - NIL ROUTE POINTER, prints route number

Action:
Severity: Minor.
BUG5115
SNMP trap: Yes
The system cannot retrieve the pointer for the 500/2500 set's protected line
data block.
Action:
Severity: Minor.
BUG5116
SNMP trap: Yes
Your attempt to link a CR to the Attendant has failed. BKI_LINK_TO_ATTN.

Action:
Severity: Minor.
BUG5117
SNMP trap: Yes
Your attempt to link a CR to desired party failed. BKI_LINK_TO_DES

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 382 of 2360

BUG5118
Unable to activate/deactivate the Break-In with Secrecy (BKIS) feature.

Action:
Severity: Minor.
BUG5119
SNMP trap: Yes
The number of TNs configured in the system is equal to or less than zero.
Action:
Severity: Minor.
BUG5120
SNMP trap: Yes
The number of ACD Agents/Supervisors configured in the system is equal to

or less than zero.ACD Agents ISM counter corruption encountered. Counter is
reset to 0.
Action:
Severity: Minor.
BUG5121
SNMP trap: Yes
The number of ACD-DNs configured is equal to or less than zero.

Action:
Severity: Minor.
BUG5122
SNMP trap: Yes
The number of AST sets configured is equal to or less than zero.

Action:
Severity: Minor.
BUG5124
SNMP trap: Yes
Invalid source to Trunk Optimization (TRO) handler.

Action:
Severity: Minor.
BUG5125
SNMP trap: Yes
Facility is not contained in facility message.

Action:
Severity: Minor.
BUG5126
SNMP trap: Yes
TRO father cr is missing.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 383 of 2360

BUG5127
TRO supplementary cr is missing.

Action:
Severity: Minor.
BUG5128
SNMP trap: Yes
Invalid operation value in facility IE.

Action:
Severity: Minor.
BUG5129
SNMP trap: Yes
Invalid FAC (invoke, rr, re, rej) message received.

Action:
Severity: Minor.
BUG5130
SNMP trap: Yes
SNMP trap: Yes
Invalid call state.

Action:
Severity: Minor.
BUG5131
Cannot initiate TRO call at originating node.

Action:
Severity: Minor.
BUG5133
SNMP trap: Yes
SNMP trap: Yes
No NARS on CR.
Action:
Severity: Minor.
BUG5135
Failed to send facility message.

Action:
Severity: Minor.
BUG5136
SNMP trap: Yes
SNMP trap: Yes
CRPTR is NIL
Action:
Severity: Info.
System Messages
Page 384 of 2360

BUG5144
The identifier for that information request is invalid.

Action:
Severity: Minor.
BUG5145
SNMP trap: Yes
Invalid lamp state for the WUK key on a BCS set. Procedure
AWU_WUK_PRESSED. Dark, lit or flash are the only valid lamp states.
Action:
Severity: Minor.
BUG5146
SNMP trap: Yes
Invalid WRITE_TYPE value passed in procedure WRT_AWU_TN.

Action:
Severity: Minor.
BUG5147
SNMP trap: Yes
Invalid AWU_TYPE value passed in procedure AWU_KEY.

Action:
Severity: Minor.
BUG5148
SNMP trap: Yes
Pointer(s) is (are) not correctly set before the procedure WUK_DARK_OR_LIT

is called from procedure AWU_KEY. Possible data corruption.
Action:
Severity: Minor.
BUG5149
SNMP trap: Yes
CRPTR=NIL when it should already exist. Procedure WUK_LAMP_FLASH.

Action:
Severity: Minor.
BUG5150
SNMP trap: Yes
Procedure WUK_RESTORE was incorrectly called when the set was not a
BCS set.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 385 of 2360

BUG5151 q i
An XMI message register in this queue has an incorrect or invalid ID. Where:
q = XMI queue, i = message register's ID.
Action:
Severity: Minor.
BUG5152 i
SNMP trap: No
An XMI message register has an invalid queue ID. Where: i = message

register's queue ID.
Action:
Severity: Minor.
BUG5153 q
SNMP trap: No
This XMI queue is corrupted. Where: q = XMI queue.

Action:
Severity: Minor.
BUG5154 q
SNMP trap: No
This XMI queue's data block is corrupted. Where: q = XMI queue.

Action:
Severity: Minor.
BUG5155 a
SNMP trap: No
The message register address passed to XI_UTILS or XI_HELPER is outside

the valid message register address space. Where: a = address.
Action:
Severity: Minor.
BUG5156
SNMP trap: Yes
The DN type for that set is incorrect; it cannot be M2000 or 500/2500 type
telephone sets. Procedure: WUK_DARK_OR_LIT or FFC_FIND_AWU_TN
Action:
Severity: Minor.
SNMP trap: Yes
BUG5157 loop ts n0 n1 Attempt to write to an invalid timeslot. Procedure Write_NWK.

Output:Loop=superloop number, ts = timeslot, n0 = NWKdata0, n1 =
NWKdata1
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 386 of 2360

BUG5158
Corrupted data. The SDAC STATE in the CR is invalid when Single Digit
Access to Services (SDAC) translation is not allowed.
Action:
Severity: Minor.
BUG5159
SNMP trap: Yes
The system has encountered an invalid RPNS counter. RPNS = Recall with
Priority in Night Service
Action:
Severity: Minor.
BUG5160
SNMP trap: Yes
Software error. The L1 signaling cannot change to Level 2 signaling when the
current signaling level is other than level 1.
Action:
Severity: Minor.
BUG5161
SNMP trap: Yes
Software error. The son Call Register used for L1 signaling cannot be found,
or the son Call Register is not allocated.
Action:
Severity: Minor.
BUG5162
SNMP trap: Yes
The L1/ISDN Gateway ROSE-type Call Register cannot be found. The

L1/ISDN Gateway information has been lost. Ringtone cannot be applied to
the destination.
Action:
Severity: Minor.
BUG5163
SNMP trap: Yes
The L1/ISDN Gateway ROSE-type Call Register cannot be linked to the PRA
message Call Register. The L1/ISDN Gateway information is not sent.
Ringtone cannot be applied to the destination.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 387 of 2360

BUG5164
The L1/ISDN gateway has failed during a call because of an L1 signaling

failure. The L1/ISDN Gateway call fails.
Action:
Severity: Minor.
BUG5165
SNMP trap: Yes
The MFC level is not a valid L1 MFC signal level.

Action:
Severity: Minor.
BUG5166
SNMP trap: Yes
The L1 MFC input received is not a valid signal supported at this level.
Action:
Severity: Minor.
BUG5167
SNMP trap: Yes
There is no supported SS function found in the SS table.

Action:
Severity: Minor.
BUG5168
SNMP trap: Yes
Cannot find a DN or TN. No CNI information has been assigned in the Trunk
data
Action:
Severity: Minor.
BUG5169
SNMP trap: Yes
That is an invalid response to the SS digit received.

Action:
Severity: Minor.
BUG5170
SNMP trap: Yes
No supplementary service function found.

Action:
Severity: Minor.
BUG5171
SNMP trap: Yes
That is an invalid response to the CNI digit.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 388 of 2360

BUG5172
That is an invalid response to the SS function.

Action:
Severity: Minor.
BUG5173
SNMP trap: Yes
That is an invalid response to the level 3 backward signal.

Action:
Severity: Minor.
BUG5174
SNMP trap: Yes
That is an invalid response to the level 3 forward signal.

Action:
Severity: Minor.
BUG5175
SNMP trap: Yes
TCAP Call Register not in 2 second queue. Procedure adp_free_sent,

resrv_timer_to
Action:
Severity: Minor.
BUG5176
SNMP trap: No
TNTRANS has failed for RTSA (PD. update CW)

Action:
Severity: Minor.
BUG5177
SNMP trap: Yes
The Attendant TN is 0 (PD. update CW)

Action:
Severity: Minor.
BUG5178
SNMP trap: Yes
The ATTNDPTR = NIL (PD. update CW)

Action:
Severity: Minor.
BUG5179
SNMP trap: Yes
The SET_ROUTE_PTRS failed in the TIE_INC_INP procedure. A forced

release is needed because you may have a stuck trunk.
Action: Check the TN indicated in the CRPTR information for status.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 389 of 2360

BUG5180
Please wait while the Virtual Network Service (VNS) performs some call
processing.
Action:
Severity: Minor.
BUG5181
SNMP trap: Yes
There was a nil pointer found during Virtual Network Service (VNS) call
processing.
Action:
Severity: Minor.
BUG5182
SNMP trap: Yes
There is a PRA call reference mismatch affecting the VNS Index pointer.
(Virtual Network Services), run an audit.
Action:
Severity: Minor.
BUG5183
SNMP trap: Yes
That task number is invalid for Virtual Network Services (VNS).

Action:
Severity: Minor.
BUG5184
SNMP trap: Yes
Virtual Network Service (VNS) trunk flag was set improperly, it has been
cleared.
Action:
Severity: Minor.
BUG5185
SNMP trap: Yes
VNS D-channel pointers cannot be restored

Action:
Severity: Minor.
BUG5186
SNMP trap: Yes
No pointer to VNS timing block

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 390 of 2360

BUG5187
Invalid information in VNS timing block

Action:
Severity: Minor.
BUG5189
SNMP trap: Yes
Invalid VNS timer to start {timer}

Action:
Severity: Minor.
BUG5190 x
SNMP trap: Yes
An invalid request was passed to ISDN when the source was ISDN_TO.
Where: x = decimal integer value
Action: Please report this software occurrence to your Northern Telecom
technical support personnel.
Severity: Minor.
BUG5191
SNMP trap: Yes
Not expected Default case statement executed (Scrps).

Action:
Severity: Minor.
BUG5192
SNMP trap: No
DN-PSA tree corrupted (Scrps).

Action:
Severity: Minor.
BUG5193
SNMP trap: No
Invalid Task passed to RPA module.

Action:
Severity: Minor.
BUG5194
SNMP trap: Yes
Invalid new RPA PM state. State is not changed.

Action:
Severity: Minor.
BUG5195
SNMP trap: Yes
Father CR (CRPTR) passed to RPA should not be NULL.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 391 of 2360

BUG5196
An RPA son CR was expected but not found.

Action:
Severity: Minor.
BUG5197
SNMP trap: Yes
Invalid timeout or change of On-/Off-Hook state is passed to RPA. Called from

TRKS.
Action:
Severity: Minor.
BUG5198
SNMP trap: Yes
Pd. Idle AUXCR failed in pd. RPA idle RAN.

Action:
Severity: Minor.
BUG5200
SNMP trap: Yes
Pd. Idle AUXCR failed in procedure Give RAN.

Action:
Severity: Minor.
BUG5201
SNMP trap: Yes
CRPTR equal to nil when a value was expected during a radio paging call.
Action:
Severity: Minor.
BUG5202
SNMP trap: Yes
TN trans on Origin or on Paging TN failed during a radio paging call.

Action:
Severity: Minor.
BUG5203
SNMP trap: Yes
Setting system or customer pointers failed during a radio paging call.

Action:
Severity: Minor.
BUG5204
SNMP trap: Yes
Mode digit stored for an RPA call is not a number.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 392 of 2360

BUG5205
No digits found in the DN when an RPA DN trans done.

Action:
Severity: Minor.
BUG5206
SNMP trap: Yes
SNMP trap: Yes
Wrong RPA PM found.

Action:
Severity: Minor.
BUG5207
TN trans on TTR TN stored in CR failed.

Action:
Severity: Minor.
BUG5208
SNMP trap: Yes
Wrong task to pd. Get TTR Path.

Action:
Severity: Minor.
BUG5209
SNMP trap: Yes
No father CR found when SON_CR processed in queue.

Action: Wait to receive a tone.
Severity: Minor.
BUG5210
SNMP trap: Yes
Setting ATTN pointers during an RPA call failed.

Action:
Severity: Minor.
BUG5211
SNMP trap: Yes
Digitload or Digitunload not correctly set during an RPA call.

Action:
Severity: Minor.
BUG5212
SNMP trap: Yes
Wrong return value for RPA DN trans.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 393 of 2360

BUG5213
DN PSA tree corrupted.

Action:
Severity: Minor.
BUG5214
SNMP trap: Yes
Wrong state when outpulse of octothorpe on RPA trunk is terminated.

Action:
Severity: Minor.
BUG5215
SNMP trap: Yes
Invalid DN stored for RPA recall.

Action:
Severity: Minor.
BUG5216
SNMP trap: Yes
Invalid PM found during cancel recall.

Action:
Severity: Minor.
BUG5217
SNMP trap: Yes
Invalid TN found during cancel recall.

Action:
Severity: Minor.
BUG5218
SNMP trap: Yes
No Call Register available.

Action:
Severity: Minor.
BUG5219
SNMP trap: Yes
Cannot create a radio paging son.

Action:
Severity: Minor.
BUG5220
SNMP trap: Yes
Radio paging accessed with invalid origtype.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 394 of 2360

BUG5221
The radio paging father CR cannot be found.

Action:
Severity: Minor.
BUG5222
SNMP trap: Yes
Invalid AUXPM in the radio paging son when timeout in the meet-me queue
occurred.
Action:
Severity: Minor.
BUG5223
SNMP trap: Yes
Customer pointers cannot be set.

Action:
Severity: Minor.
BUG5224
SNMP trap: Yes
The radio paging Father CR cannot be found.

Action:
Severity: Minor.
BUG5225
SNMP trap: Yes
Illegal origtype when trying to answer a radio paging call.

Action:
Severity: Minor.
BUG5226
SNMP trap: Yes
ORIGTN in the radio paging father and son are not the same.
Action:
Severity: Minor.
BUG5227
SNMP trap: Yes

Action:
Severity: Minor.
BUG5228
SNMP trap: Yes
When trying to abandon a radio paging call, neither the father nor the son CR
could be found.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 395 of 2360

BUG5229

Action:
Severity: Minor.
BUG5230
SNMP trap: Yes
Wrong task for Call Transfer to radio paging system.

Action:
Severity: Minor.
BUG5231
SNMP trap: Yes
No SON CR when Set RPA Item is called.

Action:
Severity: Minor.
BUG5232
SNMP trap: Yes
TER TN of CRPTR is expected to be RPA trunk and is not.

Action:
Severity: Minor.
BUG5233
SNMP trap: Yes
The paging party is not a set or trunk.

Action:
Severity: Minor.
BUG5234
SNMP trap: Yes
No orig TN in Father CR.

Action:
Severity: Minor.
BUG5242
SNMP trap: Yes
We are unable to obtain the Unprotected data store required for the Ringing
Change feature.
Action:
Severity: Minor.
BUG5243
SNMP trap: Yes
The SECL indication between the SRC and DEST is incoherent.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 396 of 2360

BUG5246
Warning: Data corruption! A bad DTR data block has been identified in an
initialization. The internal TN is shown as a hex code, so the return address
stack is not output.
Severity: Minor.
BUG5247
SNMP trap: Yes
The TIME_SYNCH procedure has been invoked by an invalid parameter.

Action:
Severity: Minor.
SNMP trap: No
BUG5248 PACKED TN xx The B-channel entered is not in an appropriate state for Overlap
Sending. This B-channel should not be entering this procedure:
PRA_OUTPULSING.
Severity: Minor.
SNMP trap: Yes
BUG5249 CR INFO The SEARCH_ROUTE has determined that this call should revert back to
Enbloc Dialing. Either Overlap Sending was initiated by a software error, or the
SEARCH_ROUTE is returning the wrong value.
Action:
Severity: Minor.
BUG5250
SNMP trap: Yes
If pbx_unit is passed into bcs lamp, setssdptr will return an incorrect ptr and
cause data corruption.
Action:
Severity: Minor.
BUG5251
SNMP trap: Yes
If pbx_unit is passed into set-lamp state, setssdptr will return an incorrect ptr
and cause data corruption.
Action:
Severity: Minor.
BUG5252
SNMP trap: Yes
That parameter for the TIME_SYNCH procedure is invalid.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 397 of 2360

BUG5253 A D O T The active Call Register is nil. No DNP message is sent to the Meridian Mail
server, and no call modification information is transmitted.
Where; A = xxxx, operation code for TCAP protocol D = xxx, parameter data
for TCAP protocol
O = xxxxxxx, Originating digits T = xxxxxxx, Terminating digits
Action:
Severity: Minor.
BUG5254
SNMP trap: Yes
Unable to set up customer pointers. Hospitality procedure.

Action:
Severity: Minor.
BUG5255
SNMP trap: Yes
TNTRANS failed. Hospitality and Disconnect procedures.

Action:
Severity: Minor.
SNMP trap: Yes
BUG5256 tn1 tn2 dn Link from set to tree is corrupted. The PPM trunk is disconnected. Where :
tn = TN of set; tn2 =TN of PPM trunk; dn = DID-DN of set.
Action:
Severity: Minor.
BUG5257 tn dn
SNMP trap: Yes
Link from set to tree is corrupted. Data: tn = TN of set, dn = DID-DN of set.

Action:
Severity: Minor.
BUG5258
SNMP trap: Yes
CRPTR was found NIL. Hospitality procedure.

Action:
Severity: Minor.
BUG5259
SNMP trap: Yes
A command has been received from the PMS to check-out a patient. The
patient status was InRoom. The data for the phone cannot be found for use by
another patient.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 398 of 2360

BUG5260
Conference pointer is NIL. Procedures HSP_CHECK_RAN

HSP_CONF_FLAG of RAN
Action:
Severity: Minor.
BUG5261
SNMP trap: Yes
No RAN trunk could be found in a Hospitality RAN conference.

HSP_CHECK_RAN of Hospitality.
Action:
Severity: Minor.
BUG5262
SNMP trap: Yes
Hospitality RAN CR could not be removed from list of sons. HSP_IDLE_SON

of Hospitality and RAN.
Action:
Severity: Minor.
BUG5263
SNMP trap: Yes
Attempt to use HIDN flexible feature code, but the package is not equipped.
FFC_DO_HIDN procedure.
Action:
Severity: Minor.
BUG5264
SNMP trap: Yes
Illegal case executed in a CASE statement. FFC_DO_HIDN procedure.

Action:
Severity: Minor.
BUG5265
SNMP trap: Yes
Attempt to use HREL flexible feature code, but the package is not equipped.
FFC_DO_HREL procedure.
Action:
Severity: Minor.
BUG5266
SNMP trap: Yes
Illegal case executed in a CASE statement. FFC_DO_HREL procedure.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 399 of 2360

BUG5267
Invalid DID number. HSP_GETLEAF_PTR of Hospitality.

Action:
Severity: Minor.
BUG5268
SNMP trap: Yes
Illegal case executed in a CASE statement. Hospitality procedure.

Action:
Severity: Minor.
BUG5269
SNMP trap: Yes
Attempt to charge a PPM call to an idle room. The PPM trunk is disconnected.
HSP_RCVD_COUNT of Hospitality.
Action:
Severity: Minor.
BUG5270
SNMP trap: Yes
Son Call Register could not be retrieved. Hospitality procedure.

Action:
Severity: Minor.
BUG5271
SNMP trap: Yes
Unable to set up route pointers

Action:
Severity: Minor.
BUG5273
SNMP trap: Yes
Procedure RMS_CHG_STAT. When finding the Maid ID number, there was an

invalid room status operation.
Action:
Severity: Minor.
BUG5276
SNMP trap: Yes
Unexpected value for slot map. Checks the decoding of slot map.
Action:
Severity: Minor.
BUG5277
SNMP trap: Yes
Procedure MAID_ID_START. Should only be called for an RMK key operation

or Dial Access.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 400 of 2360

BUG5279
Trying to display an invalid room status. Valid room status numbers are (0) - 7.
Action:
Severity: Minor.
BUG5280
SNMP trap: Yes
Invalid request for NCT_HANDLER.

Action:
Severity: Minor.
BUG5281
SNMP trap: Yes
ROSE error for Network Call Trace.

Action:
Severity: Minor.
BUG5282
SNMP trap: Yes
Call is blocked at the originating node, but the NCT Locator has no value
assigned.
Action:
Severity: Minor.
BUG5283
SNMP trap: Yes
Call is blocked at the tandem node, but the NCT Locator has no value
assigned.
Action:
Severity: Minor.
BUG5290
SNMP trap: Yes
Unexpected Mainpm or Auxpm while processing address acknowledge signal

for incoming Japanese DID trunk call. The dialed digits will not be
acknowledged; the calling party should receive busy tone from the far-end
equipment. crptr.
Action:
Severity: Minor.
BUG5291
SNMP trap: Yes
Out of the ACD_SOURCE case.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 401 of 2360

BUG5292
In procedure DIAL_UPDATE, the cleaning status should have already been

verified; the saved cleaning status value was somehow overwritten or was
never initialized.
Action:
Severity: Minor.
BUG5295
SNMP trap: Yes
TNTRANS failed in procedure give_default.

Action:
Severity: Minor.
BUG5296
SNMP trap: Yes
CCR call is not in the CDN queue.

Action:
Severity: Minor.
BUG5298
SNMP trap: Yes
Call to be removed from CDN is not a main Call Register (ICP_remove).

Action:
Severity: Minor.
BUG5299
SNMP trap: Yes
Terminating set is not a BCS or PBX set. Cannot set_pos_ptr in ICP module.
Action:
Severity: Minor.
BUG5300
SNMP trap: Yes
Terminating set is not an ACD set. Cannot set_pos_ptr in the CCR module.
Action:
Severity: Minor.
BUG5301
SNMP trap: Yes
In global procedure idctrans of cpndqury, current tree_digit_code of nfcr/idc

block indicates an idc_ptr, but this pointer is nil. Data may be corrupted.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 402 of 2360

BUG5306
The trunk is already in the timing queue. No Real Time PPM timing can be
started on it.
Action:
Severity: Minor.
BUG5307
SNMP trap: Yes
The trunk to be idled is still flagged as timed for Real Time PPM feature.
Action:
Severity: Minor.
BUG5308
SNMP trap: Yes
The trunk state is not valid if this time out is due to Real Time PPM (trunkpm
may
Action:
Severity: Minor.
BUG5309
SNMP trap: Yes
Invalid source value passed to procedure. Format : BUG xxxx aaaa bbbb cccc
dddd eeee ffff ; where: xxxx = Return Address Stack, aaaa = data parameter
specific to each message, bbbb = the current value of CL_CURRENT_CARD,
cccc = the current CL_L3- STATE, dddd = the current CL_L2-STATE, eeee =
the current CL_XI_RX-STATE, ffff = the current CL_XI_TX-STATE
Action:
Severity: Minor.
BUG5310
SNMP trap: Yes
Invalid CL_L3_STATE in cardlan. Where: aaaa = Do not care.

Action: For 'Format' see BUG5309.
Severity: Minor.
BUG5311
SNMP trap: Yes
Invalid CL_L2_STATE.in cardlan. Where: aaaa = Do not care.

Severity: Minor.
BUG5313
SNMP trap: Yes
Cardlan received an invalid message. Where: aaaa = message.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 403 of 2360

BUG5314
Cardlan procedure CL_L2_SEND failed to send an outgoing message.

Where: aaaa = Do not care.
Severity: Minor.
BUG5315
SNMP trap: Yes
Invalid loop type on output SSD message. Loop must be a superloop.

Action:
Severity: Minor.
BUG5317
SNMP trap: Yes
Invalid cardlan CL_L3_AUXSTATE. Where: aaaa = CL_L3_AUXSTATE.

Severity: Minor.
BUG5318
SNMP trap: Yes
Invalid CL_XI_RX_STATE. Where: aaaa = CL_XI_RX_STATE.

Severity: Minor.
BUG5319
SNMP trap: Yes
Invalid message in cardlan XIM conversion. Where: aaaa =

CL_XI_MSGTYPE.
Severity: Minor.
BUG5320
SNMP trap: Yes
XI message out of sequence in cardlan. Where: aaaa = XI_SEQ_STATE of the

message.
Severity: Minor.
BUG5321
SNMP trap: Yes
Attempt to send a cardlan message while polling was enabled. Message

ignored. Where aaaa = Don't care.
Action: For 'format' see BUG5309.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 404 of 2360

BUG5322
Invalid IVD channel number was detected in an input message. Message

ignored.
Action:
Severity: Minor.
BUG5324
SNMP trap: Yes
Input IVD message is discarded.

Action:
Severity: Minor.
BUG5325
SNMP trap: Yes
Output SSD message is discarded.

Action:
Severity: Minor.
BUG5326
SNMP trap: Yes
Invalid CL_CURRENT_CARD was detected in cardlan. Problem has been

avoided. Where: aaaa = CL_CURRENT_CARD.
Severity: Minor.
BUG5327
SNMP trap: Yes
Invalid cardlan message type detected. Use RAS to determine which

procedure had the problem. Where: aaaa = message type.
Severity: Minor.
BUG5329
SNMP trap: Yes
An invalid message received from the DDCS (PRI2 used for DPNSS) for
DPNSS alarms.
Action:
Severity: Minor.
BUG5330
SNMP trap: Yes
Software problem - the system thinks that another DDSL is being enabled or
disabled.
Action: Check the status of all DDSLs and verify the desired states.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 405 of 2360

BUG5331
Invalid case for setting DTI2 pads. This case should only be used for
DPNSS/DASS in the PRI2 module.
Action:
Severity: Minor.
BUG5332
SNMP trap: Yes
Set DCH pointers failed for DPNSS code.

Action:
Severity: Minor.
BUG5333
SNMP trap: Yes
Problem enabling or disabling the DDSL/DDCS. The config_loop was not of

the correct type.
Action:
Severity: Minor.
BUG5334
SNMP trap: Yes
An enable/disable was attempted when the no_lampaudit flag was set. The
command failed.
Action: Before repeating the command, use command DLMP 0 (LD 77)
Severity: Minor.
BUG5335
SNMP trap: Yes
SET_U_CSL_PTR failed. Global Procedure.

Action:
Severity: Minor.
BUG5336
SNMP trap: Yes
Bad entry to the global procedure ICP.

Action:
Severity: Minor.
BUG5337
SNMP trap: Yes
Invalid message is sent to the CCR application.

Action:
Severity: Minor.
BUG5338
SNMP trap: Yes
SET_CDN_PTRS failed. Procedure CCR or ADS

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 406 of 2360

BUG5339
MAIMPM of the incoming CCR call should be DIALING before it gets queued
to the CDN or default ACD DN.
Action:
Severity: Minor.
BUG5340
SNMP trap: Yes
Invalid function code entry to the procedure CCR_STATS.

Action:
Severity: Minor.
BUG5341
SNMP trap: Yes
The CCR message cr received from CSAI is nil.

Action:
Severity: Minor.
BUG5342
SNMP trap: Yes
The unit type of the originating set of a CCR call is TTR_UNIT or unknown, this
is an error condition.
Action:
Severity: Minor.
BUG5343
SNMP trap: Yes
The CCR son cr is nil, but the call was answered at this son process.
Action:
Severity: Minor.
BUG5344
SNMP trap: Yes
DPNSS_SUPP_SERV was called with an invalid Source parameter.

Action:
Severity: Minor.
BUG5345
SNMP trap: Yes
ITEMPTR was unexpectedly NIL in DPNSS_SUPP_SER.

Action:
Severity: Minor.
BUG5346
SNMP trap: Yes
An invalid supplementary service state was encountered in

DPNSS_SUPP_SERV.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 407 of 2360

BUG5347
RGA_CR_NOW_CRPTR failed to restore the RGA Call Register in

DPNSS_SUPP_SERV.
Action:
Severity: Minor.
BUG5348
SNMP trap: Yes
The Call Register was corrupted when channel was seized for a Call Back
When Free (BCWF) call.
Action:
Severity: Minor.
BUG5349
SNMP trap: Yes
TNTRANS failed on the ORIGTN in DPNSS_SUPP_SERV.

Action:
Severity: Minor.
BUG5350
SNMP trap: Yes
An attempt to set up the DPNSS channel pointer in CBWF failed.

Action:
Severity: Minor.
BUG5351
SNMP trap: Yes
PABX_FUNCTION was incorrectly set for DPNSS CBWF.

Action:
Severity: Minor.
BUG5352
SNMP trap: Yes
A syntax error was found in a DPNSS message which DIO failed to detect.
Action:
Severity: Minor.
BUG5353
SNMP trap: Yes
The state of a dialed item could not be determined by STATE_OF_TER.

Action:
Severity: Minor.
BUG5354
SNMP trap: Yes
SET_ROUTE_PTRS failed for a DPNSS channel in DPNSS_SUPP_SERV.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 408 of 2360

BUG5355
SETCUSTPTRS failed for a DPNSS channel in DPNSS_SUPP_SERV.

Action:
Severity: Minor.
BUG5356
SNMP trap: Yes
CREATE_SON failed to kink the DPNSS and RGA Call Registers.

Action:
Severity: Minor.
BUG5357
SNMP trap: Yes
CRPTR was unexpectedly NIL in DPNSS_SUPP_SERV.

Action:
Severity: Minor.
BUG5358
SNMP trap: Yes
The called party was not rung by DIGPROC even though it was free when
attempting to complete a CBWF.
Action:
Severity: Minor.
BUG5359
SNMP trap: Yes
An auxiliary Call Register could not be idled.

Action:
Severity: Minor.
BUG5360
SNMP trap: Yes
A son register cannot be transferred.

Action:
Severity: Minor.
BUG5361
SNMP trap: Yes
The RGAT son Call Register has disappeared in DPNSS_SUPP_SERV.

Action:
Severity: Minor.
BUG5362
SNMP trap: Yes
An invalid RGA _AUXPM was encountered in DPNSS_SUPP_SERV.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 409 of 2360

BUG5363
DIGPROC was asked to find a DPNSS channel but found something else
instead.
Action:
Severity: Minor.
BUG5364
SNMP trap: Yes
Saved CSL_MSG_PTR is NIL (for CCR response messages).

Action:
Severity: Minor.
BUG5365
SNMP trap: Yes
Invalid MSG_TYPE form MSL-1 CCR application.

Action:
Severity: Minor.
BUG5369
SNMP trap: Yes
DTI system data block does not exist. It may indicate a possible data
corruption if you had a DDB defined already, otherwise if you have GPRI
package 167 enabled, please use OVL73 to create a DDB because it is
necessary for ITG Dynamic Loss Plan feature.
Action: Define DDB in OVL73
Severity: Minor.
BUG5370
SNMP trap: Yes
The header table pointer to DTI/PRI pad category table does not exist.
Possible data corruption.
Action:
Severity: Minor.
BUG5371
SNMP trap: Yes
The 1.5 Mb/s DTI/PRI pad category table does not exist. Possible data
corruption.
Action:
Severity: Minor.
BUG5372
SNMP trap: Yes
Buffer to the PARI (QPC720) hardware has overflowed.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 410 of 2360

BUG5373
No conference circuits are available.

Action:
Severity: Minor.
BUG5374
SNMP trap: Yes
Previous fifo transaction not complete. Programming will continue

Action:
Severity: Minor.
BUG5375
SNMP trap: Yes
SNMP trap: Yes
Invalid CAM_ID.
Action:
Severity: Minor.
BUG5376
Conference circuit cannot be removed.

Action:
Severity: Minor.
BUG5377
SNMP trap: Yes
Active party not found in speaker array.

Action:
Severity: Minor.
BUG5378
SNMP trap: Yes
SNMP trap: Yes
Invalid bo3 number.

Action:
Severity: Minor.
BUG5381
Invalid control memory timeslot address.

Action:
Severity: Minor.
BUG5391
SNMP trap: Yes
An attempt to send a response message in cardlan occurred while the Rx

buffer was empty.
Action: Refer to BUG5309
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 411 of 2360

BUG5392
An expedited data unit (XDU) was received by the MSDL/MISP handler. It was
an interface XDU, that is, the intended recipient of the message was the
MSDL/MISP handler itself. One of the following three fields held an invalid
value:
1. In a Shared RAM suspend message, the field specifying which ring of
buffers (transmit, receive or both) is to be suspended was invalid.
2. The command type itself was invalid.
3. In a Transmit Flow Control Synchronization response message, the Socket
ID was invalid.
Action:
Severity: Minor.
BUG5393
SNMP trap: Yes
A message was received (either DU or XDU) that held an invalid Socket ID.
Action:
Severity: Minor.
BUG5394 x
SNMP trap: Yes
An application attempted to release a Socket ID that was invalid

(out-of-range). x = the invalid Socket ID value in hexadecimal.
Action:
Severity: Minor.
BUG5395
SNMP trap: Yes
Invalid application ID encountered when attempting to remove all applications

for an MSDL/MISP card from the PSDL tree.
Action:
Severity: Minor.
BUG5396
SNMP trap: Yes
The MSDL/MISP failed self tests, and the CSTAT value does not contain the
value H.DEAD.
Action:
Severity: Minor.
BUG5397
SNMP trap: Yes
The code for executing the MSDL commands in overlays 37, 42, 48 and 96
received a failure return code from SET_MSDLMISP_PTR.
Action: Check for MSDL database corruption.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 412 of 2360

BUG5398
One of the MSDL overlays is waiting for a message from the MSDL, and then
all of a sudden the response pending field is clear. The response pending field
indicates that some software entity is waiting for a message from the
MSDL/MISP.
Action:
Severity: Minor.
BUG5399
SNMP trap: Yes
The MSDL audit has detected that the device enabled bit in the physical IO
data block is clear when the MSDL card status is Enabled. This means that the
Meridian 1 is not checking the card for interrupts.
Action:
Severity: Minor.
BUG5400
SNMP trap: Yes
Failed to disable the card; this should have unconditionally succeeded. Card
is now in the System Disabled - Not Responding state.
Action:
Severity: Minor.
BUG5401
SNMP trap: Yes
The memory location in the Meridian 1 where the status of the MSDL/MISP is
kept holds an invalid value.
Action:
Severity: Minor.
BUG5402 x y
SNMP trap: Yes
The CSUBSTAT field on the MDSL/MISP contained invalid data.

Where x = The MSDL/MISP card number (in decimal), y = The value that was
invalid.
When the card in question is an MSDL, one possible reason for this bug
message is that there are multiple cards in the system with the same device
number as the MSDL. Therefore when the read is performed to the register on
the MSDL, it may not be the MSDL card that is responding. (This will not be
the case for the MISP, as the device address is determined by its position in
the network shelf.)
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 413 of 2360

BUG5403 l s c u
Data corruption occurred while trying to outpulse the Hi-mail (FAXS) command
sequence to a fax server. Procedure FAXS_DO_CMD.
Action:
Severity: Minor.
BUG5406
SNMP trap: Yes
The Call Register contains an invalid TRK_INS_PM.

Action:
Severity: Minor.
BUG5407
SNMP trap: Yes
The string in the CPND array is over 24 characters, the request to display this
string is ignored.
Action:
Severity: Minor.
BUG5408
SNMP trap: Yes
Procedure INSTALL_CARD has been called with an invalid SOURCE

parameter.
Action:
Severity: Minor.
BUG5409
SNMP trap: Yes
Cannot reserve a work area to install all the XDTR units.

Action:
Severity: Minor.
BUG5410
SNMP trap: Yes
There is no timeslot information in the Call Register to set up or take down the
Automatic Wake-up call. Procedure SETSPEECH_MGRP.
Output: return address stack, followed by a second BUG5410 with
U_G_LOOP of the AWU RAN and the set, the TALKSLOT_WORK and
TALKJUNC_WORD of the CR, TN of the AWU RAN and TN of the RAN set.
Action:
Severity: Minor.
BUG5411
SNMP trap: Yes
Uninitialized DESTPTR in procedure OFHLLAMPWINK, not service affecting.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 414 of 2360

BUG5414
T309 only link DCH_AUX_BLK_PTR of the primary DCH to the timing queue.
Action:
Severity: Minor.
BUG5416
SNMP trap: Yes
Conference timeslot is not in a valid state. Conference will not be set up or

town down properly. :Conference loop, timeslot, conference number, function.
Severity: Major.
BUG5417
SNMP trap: Yes
Invalid number of conference members. Conference will not be set up or torn

down properly :Conference loop, timeslot, conference number, function
members.
Severity: Major.
BUG5419
SNMP trap: Yes
Conferee count decrement below zero. This is an invalid condition, it will be

reset to zero.
Action:
Severity: Minor.
BUG5420
SNMP trap: Yes
There is no unprotected TN block pointer for TNx; or a path is trying to be set

up when there is no unprotected TN block pointer for TNy. Procedure
SETONEWAY_AWU. Output: return address stack, followed by a second
BUG5420 with the GLOOPX and U_G_LOOP for TNy.
Action:
Severity: Minor.
BUG5421
SNMP trap: Yes
The junctor reservation status bits 6 and 7 have an incorrect state of H.10.
Procedure AWU_GET_JUNCTOR. Output: return address stack, followed by
a second BUG5421 with the TN of the AWU RAN and set, the group the set is
in, and the contents of the AWU_RESV_JUNC (set's group) for the AWU RAN.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 415 of 2360

BUG5422
Used for debugging. Prints out the contents of the AWU RAN's unprotected
route data block. Output: return address stack, followed by a second
BUG5422 with the AWU RAN TN, "J", the group number and the
corresponding contents of that group's
AWU_RESV_JUNC(group):RAN_JUNCBLK_PRT.
Action:
Severity: Minor.
BUG5423
SNMP trap: Yes
Cannot get a print register to output Enhanced Call Trace report.

Action:
Severity: Minor.
BUG5424
SNMP trap: No
No alerter defined for Enhanced Call Trace so it cannot be rung.

Action: Define alert by prompt CTAL in LD 56.
Severity: Minor.
BUG5425
SNMP trap: No
No background terminal defined and LD 15 CTBG option is set to Yes. The

EMCT reports cannot be printed.
Action: Define a background terminal or change the CTBG option.
Severity: Minor.
BUG5427
SNMP trap: No
Overflow of charge calculation in Enhanced Charge Display, result is more

than 2 words.
Action:
Severity: Minor.
BUG5429
SNMP trap: No
Could not get a CR for timing purposed with Enhanced Charge Display.
Action:
Severity: Minor.
BUG5430
SNMP trap: No
PPOINTER to TN line should be nil for the current task of Enhanced Charge
Display.
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 416 of 2360

BUG5431
TNTRANS failed on the TN of set or SECTN of Attn for Enhanced Charge

Display of charge information.
Action:
Severity: Minor.
BUG5433
SNMP trap: No
The loop type is out-of-range or not supported.

Action:
Severity: Minor.
BUG5434
SNMP trap: Yes
CRPTR=NIL in procedure RAN_PROBLEM. Cannot proceed with removing

CRs from faulty AWU RAN.
Action:
Severity: Minor.
BUG5437
SNMP trap: Yes
SCTNTRANS failed. A bad TN was found for a DIG member.

Action:
Severity: Minor.
BUG5438
SNMP trap: Yes
The number of Digital Subscriber Loops (DSLs) configured has reached the
limit.
Action:
Severity: Minor.
BUG5439
SNMP trap: Yes
The number of Logical Terminal IDs (LTIDs) configured has reached the limit.
Action:
Severity: Minor.
BUG5440
SNMP trap: Yes
Invalid feature type passed in procedure BRI_INTERACT. Check the calling

procedure. Assumed no interaction with BRI, BRI_INTERACT returned false.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 417 of 2360

BUG5442
Unable to send messages to the BRI line card.

Action:
Severity: Minor.
BUG5443
SNMP trap: Yes
Invalid source to BRICP module.

Action:
Severity: Minor.
BUG5444
SNMP trap: Yes
BRI call processing message timeout in the wrong state.

Action:
Severity: Minor.
BUG5445
SNMP trap: Yes
BRI B-channel specified by the MISP is used by other call and cannot be
released.
Action:
Severity: Minor.
BUG5446
SNMP trap: Yes
Information element is missing in incoming BRI call processing message.

Action:
Severity: Minor.
BUG5447
SNMP trap: Yes
Information element is invalid in the incoming BRI call processing message.

Action:
Severity: Minor.
BUG5448
SNMP trap: Yes
BRI call processing packet message length is invalid.

Action:
Severity: Minor.
BUG5449
SNMP trap: Yes
BRI Message Handler failed to send a message.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 418 of 2360

BUG5450
Invalid mainpm after digit translation, BRI call is cleared.

Action:
Severity: Minor.
BUG5451
SNMP trap: Yes
Cannot tntrans on the specified DSL TN.

Action:
Severity: Minor.
BUG5452
SNMP trap: Yes
Unable to obtain a new call reference.

Action:
Severity: Minor.
BUG5453
SNMP trap: Yes
BRI call cannot be connected because of incompatibility of the B-channel with

the
Action:
Severity: Minor.
BUG5454
SNMP trap: Yes
Message CR cannot be found for incoming PRI call destined for a BRI
terminal.
Action:
Severity: Minor.
BUG5455
SNMP trap: Yes
Unable to hold BRI call, crptr is nil.

Action:
Severity: Minor.
BUG5456
SNMP trap: Yes
Unable to retrieve BRI call, crptr is nil.

Action:
Severity: Minor.
BUG5457
SNMP trap: Yes
Problem encountered in releasing the call.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 419 of 2360

BUG5458
Invalid source to the BRI_INTERACT procedure.

Action:
Severity: Minor.
BUG5459
SNMP trap: No
Invalid source to bri_maint module.

Action:
Severity: Minor.
BUG5460
SNMP trap: Yes
Undefined source to bri_maint module for MISP.

Action:
Severity: Minor.
BUG5461
SNMP trap: Yes
Undefined source to bri_maint module for Line card.

Action:
Severity: Minor.
BUG5462
SNMP trap: Yes
Card type expected is BRI line card.

Action:
Severity: Minor.
BUG5463
SNMP trap: Yes
Protected card pointer is nil.

Action:
Severity: Minor.
BUG5464
SNMP trap: Yes
Non-key function data ptr is nil for DSL data.

Action:
Severity: Minor.
BUG5465
SNMP trap: Yes
TNTRANS failed for DSL.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 420 of 2360

BUG5466
MISP protected loop pointer is nil.

Action:
Severity: Minor.
BUG5467
SNMP trap: Yes
MISP unprotected loop pointer is nil.

Action:
Severity: Minor.
BUG5468
SNMP trap: Yes
Cannot set up MSDL/MISP pointers.

Action:
Severity: Minor.
BUG5469
SNMP trap: Yes
Timeslot assignment controller data failed to be downloaded.

Action:
Severity: Minor.
BUG5471
SNMP trap: Yes
Illegal CSL_SOURCE for the case statement. Output: AML: {aml number in
decimal} and S: {csl_source in HEX}
Action:
Severity: Minor.
BUG5472
SNMP trap: Yes
Corruption. The card type is not of type ESDI_CARD. As a result the outgoing
ESDI operation has failed.
Output: AML: {aml number in decimal} and C: {io_card_type in HEX}
Action:
Severity: Minor.
BUG5473
SNMP trap: Yes
The address of status register of ESDI card is illegal. As a result the outgoing
ESDI operation has failed. Output: AML: {aml number in decimal} and R:
{statregadd in HEX}
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 421 of 2360

BUG5474
Corruption. The card type is not of type ESDI_CARD. As a result the incoming
ESDI operation has failed. Output: AML: {aml number in decimal} and C:
{io_card_type in HEX}
Action:
Severity: Minor.
BUG5475
SNMP trap: Yes
The address of status register of ESDI card is illegal. As a result the incoming
ESDI operation has failed. Output: AML: {aml number in decimal} and R:
{statregadd in HEX}
Action:
Severity: Minor.
BUG5476
SNMP trap: Yes
The Priority 5 message type is no longer supported. Output: AML: (aml

number in decimal} and P: {msg_priority in HEX}
Action:
Severity: Minor.
BUG5477
SNMP trap: Yes
The outgoing ESDI Command is not executed, since the IO card type is not
the ESDI_CARD. Output: AML: {aml number in decimal} and C: {csldata in
HEX}
Action:
Severity: Minor.
BUG5478
SNMP trap: Yes
Illegal case statement for identifier SOURCE in procedure CSL_UTILITIES.

Output: S: {source in HEX}
Action:
Severity: Minor.
BUG5483
SNMP trap: Yes
The input buffer pointer send from msdlmisp_handler handler is nil. Output: I:
{msdl_index in HEX}
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 422 of 2360

BUG5484
Corrupt MSDL card index. Output: I: {msdl_index in HEX}

Action:
Severity: Minor.
BUG5485
SNMP trap: Yes
The pointer (I_CSL_PNTR) pointing to the AML input buffer is nil. This pointer
must be set to point to the input buffer selected by the msdlmisp_handler.
Output: AML: {aml number in decimal}
Action:
Severity: Minor.
BUG5486
SNMP trap: Yes
Unsupported incoming MSDL AML (indication, confirmation) primitive.

Output: AML: {aml number in decimal} and PRM: {aml_prmi_id in HEX}
Action:
Severity: Minor.
BUG5487
SNMP trap: Yes
The SET_MSDLMISP_PTR failed to set the required pointers to the MSDL

data structures.
Output: AML: {aml number in decimal} and INX: {msmi_index_num in HEX}
Action:
Severity: Minor.
BUG5488
SNMP trap: Yes
Unknown outgoing MSDL AML primitive.

Output: AML: {aml number in decimal} and PRI: {o_req in HEX}
Action:
Severity: Minor.
BUG5489
SNMP trap: Yes
Illegal application type only: (PRA_LOG_APPLI, CSL_LOG_APPLI,

SDI_LOG_APPLI) are allowed.
Output: {application type in HEX {logical application number in HEX} {ioptr
pointer in HEX} {p_csl_pntr in HEX} {u_csl_pntr in HEX} {phy_csl_pntr in HEX}
{i_csl_pntr in HEX}} {o_csl_pntr in HEX}
{csl_cr_pntr in HEX}
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 423 of 2360

BUG5490
The value of pointer LOG_IO_PTR is nil.

Output: { application type in HEX
} {logical application number in HEX} {ioptr pointer in HEX} {p_csl_pntr in HEX}
{u_csl_pntr in HEX} {phy_csl_pntr in HEX} {i_csl_pntr in HEX} {o_csl_pntr in
HEX {csl_cr_pntr in HEX}
Action:
Severity: Minor.
BUG5491
SNMP trap: Yes
Did not complete the command check. Output {aml number in HEX} S: {aml
active state in HEX} T: {aml target state in HEX}
Action:
Severity: Minor.
BUG5492
SNMP trap: Yes
Did not choose a mode. Expected modes are: delay or go-ahead.

Output: {aml number in HEX} ; S: {aml active state in HEX} ; N: {aml new target
state in HEX}
Action:
Severity: Minor.
BUG5493
SNMP trap: Yes
No outgoing command (i.e., request) which causes a state change is allowed,

when the link is in a wait state or audit state or download state.
Output: {aml number in HEX} ;S: {aml active state in HEX} ; N: {aml new target
state in HEX}
Action:
Severity: Minor.
BUG5494
SNMP trap: Yes
A non-existing outgoing request primitive is selected.

Output: {aml number in HEX} ; S: {aml active state in HEX} ; T: {aml target
state in HEX}
Action:
Severity: Minor.
BUG5495
SNMP trap: Yes
A non existing incoming primitive is received. Output: {aml number in HEX} ;S:
{aml active state in HEX} ; P: {incoming primitive ID in HEX}
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 424 of 2360

BUG5496
Unknown MSDL AML firmware state.

Output: {aml number in HEX} ;S: {aml loadware state in HEX}
Action:
Severity: Minor.
BUG5497
SNMP trap: Yes
Unknown MSDL AML AUDIT request reason.

Output: {aml number in HEX} ;R: {MSDL aml audit request reason in HEX}
Action:
Severity: Minor.
BUG5498
SNMP trap: Yes
No state change occurs, because the MSDL AML primitive is not known. This
is a software bug and should not occur.
Output: {aml number in HEX} ;S: {aml active state in HEX} ; P: {primitive ID in
HEX}
Action:
Severity: Minor.
BUG5499
SNMP trap: Yes
The MSDL AML primitive is not allowed to be printed.

Output: {aml number in HEX} ;P: {primitive ID in HEX}
Action:
Severity: Minor.
BUG5500
SNMP trap: Yes
The value of pointer LOG_IO_TBL_PTR[APPL_TYPE] is nil.

Output: {application type in Hex {logical application number in Hex} {ioptr
pointer in Hex} {p_csl_pntr in Hex {u_csl_pntr in Hex}{phy_csl_pntr in
Hex{i_csl_pntr in Hex} {o_csl_pntr in Hex {csl_cr_pntr in Hex}
Action:
Severity: Minor.
BUG5501
SNMP trap: Yes
The value of pointer P_DCH_BLK_PTR[log_num] is nil.

Output: {application type in Hex {logical application number in Hex}{ioptr
pointer in Hex}{p_csl_pntr in Hex}{u_csl_pntr in Hex}{phy_csl_pntr in
Hex{i_csl_pntr in Hex}{o_csl_pntr in Hex} {csl_cr_pntr in Hex}
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 425 of 2360

BUG5502
The required global pointers for the ISDN PRI application cannot be set by
procedure SET_IO_PTRS.
Output: {application type in Hex{logical application number in Hex} {ioptr
pointer in Hex}{p_csl_pntr in Hex{u_csl_pntr in Hex}{phy_csl_pntr in
Hex{i_csl_pntr in Hex} {o_csl_pntr in Hex{csl_cr_pntr in Hex}
Action:
Severity: Minor.
BUG5503
SNMP trap: Yes
The value of pointer P_CSL_BLK_PTR[log_num] is nil.

Output: {application type in Hex {logical application number in Hex} {ioptr
pointer in Hex}{p_csl_pntr in Hex {u_csl_pntr in Hex}{phy_csl_pntr in Hex
{i_csl_pntr in Hex} {o_csl_pntr in Hex {csl_cr_pntr in Hex}
Action:
Severity: Minor.
BUG5504
SNMP trap: Yes
The required global pointers for the AML application cannot be set by
procedure SET_IO_PTRS
Output:
{application type in Hex {logical application number in Hex} {ioptr pointer in
Hex} {p_csl_pntr in Hex {u_csl_pntr in Hex} {phy_csl_pntr in Hex} {i_csl_pntr
in Hex} {o_csl_pntr in Hex} { csl_cr_pntr in Hex}
Action:
Severity: Minor.
BUG5505
SNMP trap: Yes
Procedure AML_TO_PDATA should never be called if pointer PC_AML_PTR

is nil.
Action:
Severity: Minor.
BUG5506
SNMP trap: Yes
Illegal case number in procedure NEXT_AML_PM.

Action:
Severity: Minor.
BUG5507
SNMP trap: Yes
Illegal case number in procedure DO_AML_UNIT.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 426 of 2360

BUG5508
Illegal case number in procedure DO_SDI_UNIT.

Action:
Severity: Minor.
BUG5509
SNMP trap: Yes
Procedure SDI_TO_PDATA should never be called if pointer PC_SDI_PTR is

nil.
Action:
Severity: Minor.
BUG5510
SNMP trap: Yes
Illegal case number in procedure NEXT_SDI_PM.

Action:
Severity: Minor.
BUG5511
SNMP trap: Yes
Cannot allocate MSDL data structures.

Action:
Severity: Minor.
BUG5512
SNMP trap: Yes
Unable to allocate socket id's for the logical application configured on the
MSDL card.
Action:
Severity: Minor.
BUG5513
SNMP trap: Yes
Serious problem in rebuilding the I/O table, will cause data corruption and
requires a system reload.
Action:
Severity: Minor.
BUG5514
SNMP trap: Yes
Set MSDL pointers failed.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 427 of 2360

BUG5515
RLR route is not supported for CDR; this configuration should have been
blocked.
Action:
Severity: Minor.
BUG5516
SNMP trap: Yes
The number of logical D channels configured in the system has reached the
system limit allowed for D channels.
Action:
Severity: Minor.
BUG5517
SNMP trap: Yes
The number of logical AML's configured in the system has reached the system
limit allowed for AML's.
Action:
Severity: Minor.
SNMP trap: Yes
BUG5518 {DCH NUMBER} {REASON CODE} Background audit cannot be done for the DCH
because of bad DCH data structures. The following reason codes have been
defined:
1. Bad card type defined for DCH.
2. Set MSDL pointers failed.
3. Set MSDL pointers failed while trying to suspend DCH recovery until
midnight.
Action:
Severity: Minor.
BUG5519
SNMP trap: Yes
An invalid procedure call has been made to the MSDL DCH interface.
Action:
Severity: Minor.
BUG5520
SNMP trap: Yes
Set DCH pointers fail during a DCH loadware download task on the MSDL
card.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 428 of 2360

BUG5521
Set MSDL pointers fail during a DCH loadware download task on the MSDL
card.
Action:
Severity: Minor.
BUG5522
SNMP trap: Yes
Invalid return code from msdlmisp_maint for a DCH enable application

request.
Action:
Severity: Minor.
BUG5523
SNMP trap: Yes
The MSDL Handler says that the DCH loadware is not resident on the MSDL
card. It should have been downloaded.
Action:
Severity: Minor.
BUG5524
SNMP trap: Yes
Response to the enable application message from the MSDL was an

unrecognized (i.e., invalid) value.
Action:
Severity: Minor.
BUG5526
SNMP trap: Yes
AWU module, procedure BLOCKED. Could not find the set with CLS CCSA to
update the Wake Up call information. Wake up information is not updated.
Action:
Severity: Minor.
BUG5527
SNMP trap: Yes
TNTRANS failed for the set with the wake up call, TERTN:CRPTR. Wake up
information is not updated. Procedure AWU_DISCONNECT.
Action:
Severity: Minor.
BUG5528
SNMP trap: Yes
ICP_MCR is NIL in procedure CCR_RESTORE2QS.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 429 of 2360

BUG5529
There is no Call Register to restore in procedure CCR_RESTORE2QS.

Action:
Severity: Minor.
BUG5530
SNMP trap: Yes
Cannot TNTRANS on Save terminal. Procedure DISC_WORK.

Action:
Severity: Minor.
BUG5531
SNMP trap: Yes
Cannot TNTRANS on Terminal. Procedure DISC_WORK.

Action:
Severity: Minor.
BUG5532 data
SNMP trap: Yes
When outing a TN block, a TN block of an invalid unit type was encountered.

The entry is removed from the relocation table but the storage for the block is
not freed. Protected data store is unnecessarily occupied and cannot be
re-accessed
Output data: TN xxxxxx TN PTR: yyyyyy UNIT TYPE: z Where: xxxxxx = hex
value of TN being relocated
yyyyyy = hex value of TN pointer (pointer to TN block)
z = hex value for the unit type
Action:
Severity: Minor.
BUG5536
SNMP trap: Yes
The MSDL says that the SDI application is not resident on the card. It should
have been downloaded.
Action:
Severity: Minor.
BUG5537
SNMP trap: Yes
Response to the enable application msg from the MSDL was an unrecognized
(i.e. invalid) value.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 430 of 2360

BUG5538
A problem encountered when trying to setup MSDL pointers.

Action:
Severity: Minor.
BUG5539
SNMP trap: Yes
The SDI I/F Handler received an invalid primitive type.

Action:
Severity: Minor.
BUG5540
SNMP trap: Yes
The SDI I/F Handler was called with an uninitialized incoming message
pointer.
Action:
Severity: Minor.
BUG5541
SNMP trap: Yes
The global procedure MSDL_SDI_HANDLER was called with an invalid

source type.
Action:
Severity: Info.
BUG5542
SNMP trap: Yes
The global procedure MSDL_SDI_MAINT was called with an invalid source

type.
Action:
Severity: Minor.
BUG5543
SNMP trap: Yes
The global procedure MSDL_SDI_UTILITY % was called with an invalid

source type.
Action:
Severity: Minor.
BUG5544
SNMP trap: Yes
The SDI state machine for the specified TTY port is in an invalid state.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 431 of 2360

BUG5545
The sub-state of the SDI state machine for the specified TTY port is in an
invalid state.
Action:
Severity: Minor.
BUG5546
SNMP trap: Yes
The sdi pointer in the log_io_tbl is nil.

Action:
Severity: Minor.
BUG5547
SNMP trap: Yes
Cannot set sdi pointers in procedure set_io_ptrs.

Action:
Severity: Minor.
BUG5548
SNMP trap: Yes
WKSD_ATTNQ_NS_CR is not nil, but WKSD_ATTNQ_NS_CR and CRPTR

pointers are not equal. Proc. NFNS_CONT_STRT. Impact: NFNS timer is not
activated. This call will not be disconnected after the {NFNS} customer
predefined period.
Action:
Severity: Minor.
BUG5552
SNMP trap: Yes
Invalid RGAPM value in stop_or_retry. CRPTR is output.

Action:
Severity: Minor.
BUG5553
SNMP trap: Yes
Failed to set customer pointer in INIT_NCOS. CRPTR is output.

Action:
Severity: Minor.
BUG5554
SNMP trap: Yes
Failed to set ESN data block pointer in INIT_NCOS. CRPTR is output.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 432 of 2360

BUG5555
Failed to set route list pointer in INIT_NCOS. CRPTR is output.

Action:
Severity: Minor.
BUG5556
SNMP trap: Yes
Invalid operation value in Facility information element in SETUP message.

D-channel number, Rose operation value and CRPTR is output.
Action:
Severity: Minor.
BUG5557
SNMP trap: Yes
Invalid operation value in Facility information element in Facility message.

D-channel number, ROSE operation value and CRPTR is output.
Action:
Severity: Minor.
BUG5558
SNMP trap: Yes
Invalid operation value in Facility information element. D-channel number,

Rose operation value and CRPTR is output.
Action:
Severity: Minor.
BUG5559
SNMP trap: Yes
Invalid return error component is received. D-channel number, Rose operation

value and CRPTR is output.
Action:
Severity: Minor.
BUG5560
SNMP trap: Yes
Invalid reject component is received. D-channel number, Rose operation

value and CRPTR is output.
Action:
Severity: Minor.
BUG5561
SNMP trap: Yes
Cannot offer RVQ call to originator because of TNTRANS failure. D-channel

number, Rose operation value and CRPTR is output.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 433 of 2360

BUG5562
DTAD data corrupted (bad pointer/bad tone).

Action:
Severity: Minor.
BUG5566
SNMP trap: Yes
The download state for the MSDL application is invalid. The following
information is provided
1. The name of the card,
2. The device number (MSDL) or loop number (MISP)
3. The application name
4. The hex value of the download state
Action:
Severity: Minor.
BUG5567
SNMP trap: Yes
An attempt to enable an application on the MSDL/MISP was made, however

the application id passed in to the routine that does the enabling was invalid.
Action:
Severity: Minor.
BUG5568
SNMP trap: Yes
The transmit expedited buffer was queued, waiting for a TEE interrupt from the
card that never came. Given the current state of the card, no message should
have been queued. The card name, the device number (loop number for
MISP) and the first 5 words in the buffer are output.
Action:
Severity: Minor.
BUG5569
SNMP trap: Yes
Invalid return code from the resident maintenance software for the MSDL
(Msdlmisp_maint). The return value is output, along with a 0 or 1, indicating
which occurrence of this BUG was responsible for the message being printed.
Action:
Severity: Minor.
BUG5570
SNMP trap: Yes
The MSDL/MISP sent a message to the SL-1 indicating that it received a

message with a format error. There are either three or four fields output with
this message:
1. The MSDL card number or the MISP loop number,
2. The type of formatting error (value of 0: unknown or unexpected message,
value of 1: invalid message length),
System Messages
Page 434 of 2360

3. The message id of the "bad" message, and
4. If the formatting error type was message length, the length of the actual
message.
Action:
Severity: Minor.
BUG5573 x
SNMP trap: Yes
Invalid ROSE component type received on D-channel x.

Action:
Severity: Minor.
BUG5574 x y z
SNMP trap: Yes
Invalid return result value in Facility message. The D-channel number x,

ROSE
Action:
Severity: Minor.
BUG5575 x y z
SNMP trap: Yes
Invalid return result is received. The D-channel number x, ROSE return result
y, and CRPTR z is output.
Action:
Severity: Minor.
BUG5576
SNMP trap: Yes
MISP's physical I/O block pointer is nil.

Action:
Severity: Minor.
BUG5577
SNMP trap: Yes
Unprotected BRI DSL pointer is nil.

Action:
Severity: Minor.
BUG5578
SNMP trap: Yes
Protected line block pointer is nil.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 435 of 2360

BUG5583
That entry is out-of-range.

Action:
Severity: Minor.
BUG5587
SNMP trap: Yes
The midnight recovery only bit was set for the MSDL or MISP in question, and
it should not have been. Three fields are output with this BUG:
1. The card name.
2. The MSDL card number or the MISP loop number.
3. The application download fail count for the basecode.
Action:
Severity: Minor.
BUG5588
SNMP trap: Yes
Case statement out-of-range in procedure CCR_GIVE_IVR.

Action:
Severity: Minor.
BUG5590
SNMP trap: Yes
DTSL_USE_NT_HW is out-of-range.
Action:
Severity: Minor.
BUG5591
SNMP trap: Yes
The current value of DTSL_USE_NT_HW is valid but it is not consistent with

the operation being done.
Action:
Severity: Minor.
BUG5593
SNMP trap: Yes
No DN was available for the message, so "0" will be sent as the DN. This may
cause problems at the far-end and the call to be dropped.
Action:
Severity: Minor.
BUG5594
SNMP trap: Yes
TNTRANS failed on manual trunk termination. Procedure TEMPPATH.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 436 of 2360

BUG5596
SET_ROUTE_PTRS failed (DPNSS Three-Party Service). Output data: trunk

TN for which pointers setting failed.
Action:
Severity: Minor.
BUG5597
SNMP trap: Yes
Setup of Attendant Pointers failed (DPNSS Three-Party Service)

Action:
Severity: Minor.
BUG5600
SNMP trap: Yes
The MSDL/MISP background audit detected that the memory location holding
the MSDL/MISP status contains an invalid value. The audit will attempt to
correct it. Two fields are output with this message: the card name and the
MSDL card number or the MISP loop number.
Action:
Severity: Minor.
BUG5601
SNMP trap: Yes
The SL-1 received a maintenance message from the MSDL/MISP, and the
message type was invalid. There are three fields output with this message:
1. The name of the card.
2. The MSDL card number or the MISP loop number.
3. The invalid message type (also known as "command/status").
Action:
Severity: Minor.
BUG5605
SNMP trap: Yes
When reading the application information block from the MSDL/MISP card, an
invalid application ID was encountered. This implies that there may be
corruption in the application information block. Three fields are output with this
error message:
1. The card name. 2. The MSDL card number or the MISP loop number (in
decimal). 3. The application ID that is considered to be invalid.
Action:
Severity: Minor.
BUG5606
SNMP trap: No
SNMP trap: Yes
Failed to set io pointers.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 437 of 2360

BUG5608
DPNSS Route Optimization, SET_CUST_PTRS failed.

Action:
Severity: Minor.
BUG5609
SNMP trap: Yes
DPNSS Route Optimization, TNTRANS failed.

Action:
Severity: Minor.
BUG5610
SNMP trap: Yes
DPNSS Route Optimization, speechpath cannot be reserved. Route

Optimization request is rejected.
Action:
Severity: Minor.
BUG5611
SNMP trap: Yes
DPNSS Route Optimization, PSTN to PSTN connection is forbidden.

Action:
Severity: Minor.
BUG5612
SNMP trap: Yes
DPNSS Route Optimization, CDR configuration is inconsistent between the

old and the new route.
Action:
Severity: Minor.
BUG5616
SNMP trap: Yes
DIGPROC returned back to CO_MAY_CAMP with mainpm not set to busy or

reorder indicating some failure in selection an outgoing channel for call offer.
Action:
Severity: Minor.
BUG5617
SNMP trap: Yes
Failed to clear all tests in procedure SET_ATTNPTRS for a DPNSS Call Offer
Call
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 438 of 2360

BUG5618
No error has occurred.

Action:
Severity: Minor.
BUG5619
SNMP trap: No
Procedure CO_STOP_CAMPON called when the service state was not

SUPP_SERV_CO.
Action:
Severity: Minor.
BUG5620
SNMP trap: Yes
The pointer PC_AML_PTR is nil.

Action:
Severity: Minor.
BUG5621
SNMP trap: Yes
Cannot allocate PDS for the VAS data structures.

Action:
Severity: Minor.
BUG5622
SNMP trap: Yes
SETSPEECHPATH failed in a DPNSS1 Redirection related procedure.

Action:
Severity: Minor.
BUG5623
SNMP trap: Yes
An unexpected NIM or NAM message was received on a call involved in

DPNSS1 redirection.
Action:
Severity: Minor.
BUG5624
SNMP trap: Yes
The TNs are scrambled in a DPNSS1 redirection call. ACTIVECR could not be
set correctly.
Action:
Severity: Minor.
BUG5625
SNMP trap: Yes
The DPNSS1 redirection Call Register pointer is out-of-range.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 439 of 2360

BUG5626
Configuration of NAS alternatives is not good for DPNSS1 redirection. FLEN

must be set to 0, and enough digits to route the call must be entered. The old
call will be kept (no redirection performed).
Action:
Severity: Minor.
BUG5627
SNMP trap: Yes
Invalid source entry for DPNN_NTWK_SERV global.

Action:
Severity: Minor.
BUG5629
SNMP trap: Yes
An unexpected condition has occurred in that the mainpm was dialing and the
TERTN is zero in the DPNSS Call Offer case.
Action:
Severity: Minor.
BUG5630
SNMP trap: Yes
SET_ROUTE_PTRS failed in DMS_NSF while building outgoing ISA NSF IE.

SID value defaults to 0. FACY defaults to TIE.
Action:
Severity: Minor.
BUG5632 x
SNMP trap: Yes
SNMP trap: No
Invalid class ID X = Hex

Action:
Severity: Minor.
BUG5633 x
Invalid object ID X = Hex

Action:
Severity: Minor.
BUG5634 x
SNMP trap: No
Invalid HI start request X = Hex

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 440 of 2360

BUG5635 x y
Error occurred in init phase Y (decimal) of class X (name).

Action:
Severity: Minor.
BUG5636 x
SNMP trap: No
Invalid name of HI Main Database file X.

Action:
Severity: Minor.
BUG5637 x
SNMP trap: No
Failed to open HI Main Database file X.

Action:
Severity: Minor.
BUG5638 x
SNMP trap: No
Failed to get class X record from HI Main Database file.

Action:
Severity: Minor.
BUG5639 x
SNMP trap: No
Corrupted class X record in HI Main Database file.

Action:
Severity: Minor.
BUG5640 x
SNMP trap: No
Unknown class name X.

Action:
Severity: Minor.
BUG5641 x
SNMP trap: No
Unknown object name X.

Action:
Severity: Minor.
BUG5642 x
SNMP trap: No
Failure to allocate protected memory of size X.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 441 of 2360

BUG5643 x
Failure to allocate unprotected memory of size X.

Action:
Severity: Minor.
BUG5644 x y
SNMP trap: No
Object X is in invalid fault monitoring state Y.

Action:
Severity: Minor.
BUG5645 x
SNMP trap: No
Failed to deliver message to HI server. OS error X (Hex).

Action:
Severity: Minor.
BUG5646 x
SNMP trap: No
Failed to resume periodic server X.

Action:
Severity: Minor.
BUG5647 x y
SNMP trap: No
Invalid attribute Y of periodic server X.

Action:
Severity: Minor.
BUG5648
SNMP trap: No
Broken list of HI classes.

Action:
Severity: Minor.
BUG5649 x
SNMP trap: No
Invalid class ID X in the list of HI classes.

Action:
Severity: Minor.
BUG5650 x
SNMP trap: No
Broken list of class X objects.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 442 of 2360

BUG5651 x y
Invalid object ID X in the list of class Y objects.

Action:
Severity: Minor.
BUG5656 x y
SNMP trap: No
Assertion of condition failed in file X line Y.

Action:
Severity: Minor.
BUG5662
SNMP trap: No
SET_ROUTE_PTRS failed in procedure EQA_CALL_REST. Output:

Customer, route, call register.
Action:
Severity: Minor.
BUG5663 x
SNMP trap: Yes
Object x returned ERROR when IPB row propagated Link operation.

Action:
Severity: Minor.
BUG5664 x
SNMP trap: No
Object x returned ERROR when IPB row propagated HWEnable operation.

Action:
Severity: Minor.
BUG5665
SNMP trap: No
CP database parse error.

Action:
Severity: Minor.
BUG5666
SNMP trap: No
IPB database parse error.

Action:
Severity: Minor.
BUG5667
SNMP trap: No
IPB monitor internal error.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 443 of 2360

BUG5668
Error returned from space manager function call.

Action:
Severity: Minor.
BUG5669
SNMP trap: No
Error returned from BIC lib.

Action:
Severity: Minor.
BUG5670
SNMP trap: No
Bad service route pointer for ISA route in procedure EQA_CALL_REST.

Action:
Severity: Minor.
BUG5671
SNMP trap: Yes
SETCUSTPTRS failed in procedure EQA_CALL_REST. Output: Call Register

Action:
Severity: Minor.
BUG5673
SNMP trap: Yes
Invalid type in case statement.

Action:
Severity: Minor.
BUG5674
SNMP trap: No
An invalid call is made to disable port 0 on the MSDL card. This message
indicates that the SDI application is not configured on port 0.
Action:
Severity: Minor.
BUG5680
SNMP trap: Yes
Multiparty Operations (MPO) should have recovered this misoperation, MPO

parameters are still set : MPO_MISOP_DN and MPO_RCV_CNL-TONE.
Active call is disconnected.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 444 of 2360

BUG5681
Protocol or state problem in NAS environment. It is printed from various places

in global procedure NAS_DECODE (module NAS) and in the global
SACP_IEN.
Action:
Severity: Minor.
BUG5682
SNMP trap: Yes
IEN feature condition error. It is printed from various places in the global
SACP_IEN, and from procedure SPECIAL_ORIGTO (module WORKSHED).
Action:
Severity: Minor.
BUG5684
SNMP trap: Yes
Illegal MSDL AML recovery state.

Action:
Severity: Minor.
BUG5685
SNMP trap: Yes
Set MSDL pointers failed. Task being formed was releasing of socket id's. Info:
IO_DEVICE, IO_LOGNUM, CD_INDX (card index).
Action:
Severity: Minor.
BUG5686
SNMP trap: Yes
Set MSDL pointers failed. Task being formed was allocation of socket id's.
Info: IO_DEVICE, IO_LOGNUM, CD_INDX (card index).
Action:
Severity: Minor.
BUG5687
SNMP trap: Yes
DTOB(.DTOB_UNQ_MSG,...) returned a NIL pointer. Pd. DASS_INPUT

Action:
Severity: Minor.
BUG5688
SNMP trap: Yes
DTS_EVENT is out-of-range. Pd. DASS_INPUT

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 445 of 2360

BUG5689
CHECKDTSL failed. Pd. DASS_INPUT.

Action:
Severity: Minor.
BUG5690
SNMP trap: Yes
DTS_ERR_LUT was requested to output an error msg which is not defined.

Action:
Severity: Minor.
BUG5691
SNMP trap: Yes
Requested operation not defined. Pd DTOB.

Action:
Severity: Minor.
BUG5692
SNMP trap: Yes
Passed parameter DTSL_IOBLK_PTR is nil. Pd. DTOB.

Action:
Severity: Minor.
BUG5693
SNMP trap: Yes
Procedure SEND_ISDN_MSG called with an invalid GW_FUNCTION

parameter.
Action:
Severity: Minor.
BUG5694
SNMP trap: Yes
Procedure SEND_IDA_MSG called with an invalid GW_FUNCTION

parameter.
Action:
Severity: Minor.
BUG5695
SNMP trap: Yes
Reception of a ROSE information different from ROSE Invoke of camp on

activation in procedure IN_FACILITY_MSG. The call is cleared down.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 446 of 2360

BUG5696
Procedure COGW_SERVICE called with an invalid GW_FUNCTION

parameter.
Action:
Severity: Minor.
BUG5697
SNMP trap: Yes
The DPN_TRY_CAMPON flag is false when it should be true in procedure

EEM_CO_GW_W_RING.
Action:
Severity: Minor.
BUG5698
SNMP trap: Yes
TNTRANS on the orig TN has failed in procedure RECV_FAC.

Action:
Severity: Minor.
BUG5699
SNMP trap: Yes
TNTRANS on the ter TN has failed in procedure CLEAR_BOTH_SIDES.

Action:
Severity: Minor.
BUG5700
SNMP trap: Yes
A Call Register can't be obtained in procedure CLEAR_BOTH_SIDES.

Action:
Severity: Minor.
BUG5701
SNMP trap: Yes
TNTRANS on the orig TN has failed in procedure COGW_SERVICE.

Action:
Severity: Minor.
BUG5702
SNMP trap: Yes
Unexpected trunk type in procedure MAP_NASTERM_CLC.

Action:
Severity: Minor.
BUG5703
SNMP trap: Yes
TNTRANS on the orig or the ter TN has failed in procedure SEND_FAC.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 447 of 2360

BUG5704
The PRA Call Register pointer should not be NIL in procedure

CLEAR_BOTH_SIDES.
Action:
Severity: Minor.
BUG5705
SNMP trap: Yes
The received CLC value in the NAM message is zero which is invalid in
procedure MAP_CLC_NASTERM.
Action:
Severity: Minor.
BUG5706
SNMP trap: Yes
A problem has occurred in ISDN_UTILITY called in procedure

MAP_NAM_ALERT.
Action:
Severity: Minor.
BUG5707
SNMP trap: Yes
Invalid SCSUBSTEPPM detected during DCH administration. The operation

has now been aborted.
Action:
Severity: Minor.
BUG5708
SNMP trap: Yes
The protected DCH block pointer is nil when a copy of the DCH block is
requested to the work area.
Action:
Severity: Minor.
BUG5712
SNMP trap: Yes
Procedure COMPLETE_TRK, MSG_CRPTR is nil. CR INFO, STATEPM:

ULTRKPTR.
Action:
Severity: Minor.
BUG5713
SNMP trap: Yes
TRK_TIMING_PTR is nil when calling SET_TIMER2(TIME,PTR) in

SET_OUTG_TIMER.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 448 of 2360

BUG5714
Unrecognized AUXPM, procedure DIAL_MAID_ID.

Action:
Severity: Minor.
BUG5725
SNMP trap: Yes
Message Call Registers out-of-range in procedure DL_DATA_CREF.

Action:
Severity: Minor.
BUG5726
SNMP trap: Yes
Invalid data during installation of the XTD units.

Action:
Severity: Minor.
BUG5728
SNMP trap: Yes
D-channel type can only be PRI or BRIT

Action:
Severity: Minor.
BUG5729
SNMP trap: Yes
TNTRANS on B-ch TN failed

Action:
Severity: Minor.
BUG5730
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Nil SS MsgCR
Action:
Severity: Minor.
BUG5731
Nil MsgCR
Action:
Severity: Minor.
BUG5732
A DSL D-channel cannot be VNS

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 449 of 2360

BUG5733
Nil BRIT traffic pointer

Action:
Severity: Minor.
BUG5734
SNMP trap: Yes
TNTRANS on DSL TN failed

Action:
Severity: Minor.
BUG5736
SNMP trap: Yes
Failure to set MISP pointers

Action:
Severity: Minor.
BUG5737
SNMP trap: Yes
Invalid parameters for procedure ISDN

Action:
Severity: Minor.
BUG5738
SNMP trap: Yes
D-channel type can only be PRI

Action:
Severity: Minor.
BUG5739
SNMP trap: Yes
D-channel type can only be BRIT

Action:
Severity: Minor.
BUG5740
SNMP trap: Yes
Only SL-1, 1TR6, Numerus are supported by BRIT

Action:
Severity: Minor.
BUG5741
SNMP trap: Yes
Passed ITEMPTR is nil in BRIT_HANDLER

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 450 of 2360

BUG5742
Passed DSL TN is invalid in BRIT_HANDLER

Action:
Severity: Minor.
BUG5743
SNMP trap: Yes
Invalid SOURCE parameter in BRIT_HANDLER

Action:
Severity: Minor.
BUG5744
SNMP trap: Yes
TNTRANS failed in GL_RLS_REFNUM

Action:
Severity: Minor.
BUG5745
SNMP trap: Yes
NO BCH STATE invalid in IBRIT

Action:
Severity: Minor.
BUG5746
SNMP trap: Yes
Database Error: remote node does not support the given capability
Action:
Severity: Minor.
BUG5760
SNMP trap: Yes
BRI Trunks not supported

Action:
Severity: Minor.
BUG5761
SNMP trap: Yes
Invalid DATA1 parameter in ISDN_TRK_UTLY (GET_DATA)

Action:
Severity: Minor.
BUG5762
SNMP trap: Yes
Nil ITEMPTR in ISDN_TRK_UTLY

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 451 of 2360

BUG5763
Nil ptr in ISDN_TRK_UTLY. SET_IO_PTRS must be called first

Action:
Severity: Minor.
BUG5764
SNMP trap: Yes
Invalid source in ISDN_TRK_UTLY

Action:
Severity: Minor.
BUG5765
SNMP trap: Yes
Invalid ISDN_TYPE in ISDN_TRK_UTLY subprocedure GET_DCH_OR_DSL

Action:
Severity: Minor.
BUG5766
SNMP trap: Yes
Invalid D-channel number or DSL TN

Action:
Severity: Minor.
BUG5771
SNMP trap: Yes
SET_BRIT_PTRS: DSL must be B1, not B2

Action:
Severity: Minor.
BUG5772
SNMP trap: Yes
SET_BRIT_PTRS: UNITTYPE {} .TRK_UNIT

Action:
Severity: Minor.
BUG5773
SNMP trap: Yes
SET_BRIT_PTRS: Trunk must be BRIT_B_CH

Action:
Severity: Minor.
BUG5774
SNMP trap: Yes
SET_BRIT_PTRS: Nil DSL pointers from TNTRANS

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 452 of 2360

BUG5775
SET_BRIT_PTRS: SET_ROUTE_PTRS failed

Action:
Severity: Minor.
BUG5777
SNMP trap: Yes
Illegal key type on key 0 used for OHAS forced out of service treatment.
Action:
Severity: Minor.
BUG5778
SNMP trap: Yes
Cannot reserve enough memory to install all the XTD units.

Action:
Severity: Minor.
BUG5779
SNMP trap: Yes
For SL-1 telephones: Emergency key thought to be on a key with no

associated lamp. For other telephones: key number returned for emergency
key is invalid.
Action:
Severity: Minor.
BUG5780
SNMP trap: Yes
Trying to load an overlay and the global procedure OVL_LINKER has been
executed for a non-linked overlay. Code in global procedure OVL_LINKER
needs to be modified to allow the overlay to run.
Action:
Severity: Minor.
BUG5782
SNMP trap: No
Failed to setup NARS_CR in INIT_NCOS. CRPTR is output.

Action:
Severity: Minor.
BUG5783
SNMP trap: Yes
In FIND_TTR, TRUNKFLAG should not be set when searching for an MF

Receiver (MFR).
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 453 of 2360

BUG5787
Pointers not set. {TERMINAL} Procedure USCR

Action:
Severity: Minor.
BUG5788
SNMP trap: Yes
Unit type not correct. {TERMINAL} Procedure USCR

Action:
Severity: Minor.
BUG5789
SNMP trap: Yes
USCR option wrong. {TERMINAL} Procedure USCR_STORE

Action:
Severity: Minor.
BUG5791
SNMP trap: Yes
Invalid lamp state for USR key programming. {TERMINAL} Procedure

USR_KEY_PRESSED
Action:
Severity: Minor.
BUG5792
SNMP trap: Yes
Invalid USCR_PM. {TERMINAL} Procedure USCR_INPUT

Action:
Severity: Minor.
BUG5803
SNMP trap: Yes
SDI port number out-of-range in procedure set_io_ptrs.

Action:
Severity: Minor.
BUG5808
SNMP trap: Yes
Procedure CH_TN_CONVERT failed to convert a loop and channel number

into a TN.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 454 of 2360

BUG5815
One of the following has taken place:

1. Invalid BRSC index number,
2. BRSC protected card pointer is nil,
3. BRSC unprotected card pointer is nil
Action:
Severity: Minor.
BUG5817
SNMP trap: Yes
Unable to write to protected data storage. Protected pointer is NIL.

Action:
Severity: Minor.
BUG5818
SNMP trap: Yes
Protected MISP Loop pointer is NIL.

Action:
Severity: Minor.
BUG5819
SNMP trap: Yes
No more Local DNA Table entries available.

Action:
Severity: Minor.
BUG5820
SNMP trap: Yes
The MSDL/MISP message handler failed to send a message for unknown

reasons.
Action:
Severity: Minor.
BUG5833
SNMP trap: Yes
Call ID in CR does not match Call ID entry in internal Table. Internal Table
entry cleared. The output data appears as follows.
{Call ID} {CUST} {CR} {MAIN & AUX PMs} {ORIGTYPE/TERTYPE}
{ORIGTN} {TERTN} {QUEUE_IN} {CR_DIALLED_DN} {DIGITLOAD}
{DIGITS...}
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 455 of 2360

BUG5834
Out-of-range Call ID found in Call Register. Call ID in CR set to zero. The

output data appears as follows:
{DIGITS...}
Action:
Severity: Minor.
BUG5835
SNMP trap: Yes
Call ID in Call Register does not have associated pointer in Call ID Table. Call
ID field in CR set to zero. The output data appears as follows:
{DIGITS...}
Action:
Severity: Minor.
BUG5836
SNMP trap: Yes
No conference exists for Call ID value in conference block. Associated entry

in internal Call ID Table is cleared. The output data appears as follows:
{U_CONF_PTR} {Call ID} {Conf Group}
Action:
Severity: Minor.
BUG5837
SNMP trap: Yes
Expected Call ID not found in conference block. Internal Table entry cleared.
The output data appears as follows: {U_CONF_PTR} {Call ID}
Action:
Severity: Minor.
BUG5838
SNMP trap: Yes
Out-of-range Call ID associated with {Conf Group} found in conference block.

Call ID field in conference block set to zero. The output data appears as
follows: {U_CONF_PTR} {Call ID} {Conf Group}
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 456 of 2360

BUG5839
Call ID in conference block associated with {Conf Group} does not have
associated pointer in Call ID Table. Call ID field in conference block set to zero.
The output data appears as follows: {U_CONF_PTR} {Call ID} {Conf Group}
Action:
Severity: Minor.
BUG5840
SNMP trap: Yes
Call ID free list head and/or tail pointers are nil. This should only happen if all
Call IDs are allocated, which is very unlikely. This may signal a problem with
the Call ID Table.
Action:
Severity: Minor.
BUG5841
SNMP trap: Yes
The internal Call ID Table cannot handle the number of Call ID entries
required. 32767 (hex 7fff) is the max. Call IDs will not be allocated.
Action:
Severity: Minor.
BUG5857
SNMP trap: Yes
Illegal case number for procedure DO_STA_UNIT.

Action:
Severity: Minor.
BUG5858
SNMP trap: Yes
Procedure STA_TO_PDATA should never be called when PC_STA_PTR is

nil.
Action:
Severity: Minor.
BUG5859
SNMP trap: Yes
Illegal case number for procedure NEXT_STA_PM.

Action:
Severity: Minor.
BUG5860
SNMP trap: Yes
Procedure TRK_DIGIT_INSERT, the passed item is not a trunk. Data

corruption was avoided.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 457 of 2360

BUG5861
TN passed should be a trunk. Procedure is called with wrong UNITTYPE.

Action:
Severity: Minor.
BUG5862
SNMP trap: Yes
TNTRANS on TERTN fails in procedure APPLY_CW.

Action:
Severity: Minor.
BUG5868
SNMP trap: Yes
In OAM SEER segment, unable to get print Call Register.

Action:
Severity: Minor.
BUG5869
SNMP trap: Yes
In OAM SEER segment, unable to unlink print Call Register.

Action:
Severity: Minor.
BUG5870
SNMP trap: Yes
In OAM SEER segment, invalid case statement.

Action:
Severity: Minor.
BUG5873
SNMP trap: Yes
Failed to update Multi-User conflict resolution resource list.

Action:
Severity: Minor.
BUG5874 tn
SNMP trap: Yes
The telephone being tested is not a digital telephone.

Action:
Severity: Minor.
BUG5875
SNMP trap: No
Feature Activation IE content error.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 458 of 2360

BUG5876
Conference disconnection failure. Infinite loop prevented. Conferee count

printed with CR information.
Action:
Severity: Minor.
BUG5878
SNMP trap: Yes
The unit is not a digital telephone in ACD_CF_TONE.

Action:
Severity: Minor.
BUG5879
SNMP trap: Yes
An invalid value is currently set for ITPP in LD 73.

Action:
Severity: Minor.
BUG5880
SNMP trap: No
End-to-End Signaling is out of Call Registers.

Action:
Severity: Minor.
BUG5881
SNMP trap: Yes
Non-key data should exist for OHAS is ASCA class of service is defined.
Action:
Severity: Minor.
BUG5882
SNMP trap: Yes
Call Register idled when SON CR with NACD process type still linked.
Action:
Severity: Minor.
BUG5884
SNMP trap: Yes
An attempt to find an application index associated with a particular MSDL or

MISP application failed. No attempt to get an index should be made before it
is configured. No attempt to find an index for the MSDL or MISP Base Code
should be made either: the Base Code has a pre-assigned index.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 459 of 2360

BUG5885
An attempt to allocate an instance of the application blocks failed. Either they

have all been used up (32 applications already configured for this card, which
is unlikely) or there is some kind of corruption such that all the blocks somehow
seem to all be allocated.
Action:
Severity: Minor.
BUG5887
SNMP trap: Yes
The number of Meridian 1 Packet Handler Digital Subscriber Loops (DSLs)

configured in the system has reached the limit.
Action:
Severity: Minor.
BUG5888
SNMP trap: Yes
Timeslot monitor turned ON.

ENL:TSxxxx JWyyyy (timeslot being built) or IDL:TSxxxx JWyyyy (timeslot
being cleared). Where: xxxx = timeslot word
yyyy = junctor word
Action:
Severity: Minor.
BUG5889
SNMP trap: Yes
RPA not supported on MFK5/MFK6 signaling.

Action:
Severity: Minor.
BUG5898
SNMP trap: No
RCFW son CR expected.

Action:
Severity: Minor.
BUG5900
SNMP trap: Yes
Could not update Voice Mailbox data.

Severity: Minor.
BUG5901
SNMP trap: Yes
There is no template entry for Voice Mailbox data block pointer.

Severity: Minor.
SNMP trap: Yes
System Messages
Page 460 of 2360

BUG5902
The Voice Mailbox data block is not configured. Remove and reconfigure the
VMB application.
Severity: Minor.
BUG5903
SNMP trap: Yes
The customer DN tree does not exist.

Severity: Minor.
BUG5904
SNMP trap: Yes
There is a bad case value received in the case statement in Voice Mailbox
Administration module.
Severity: Minor.
BUG5905
SNMP trap: Yes
The pointer to Voice Mailbox data block is NIL.

Severity: Minor.
BUG5908
SNMP trap: Yes
The Update-In-Progress list for Voice Mailbox application does not exist.
Severity: Minor.
BUG5909
SNMP trap: Yes
There is a mismatch between the number of updates in the

Update-In-Progress list and the Update-In-Progress counter.
Severity: Minor.
BUG5910
SNMP trap: Yes
The application layer association table does not exist.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 461 of 2360

BUG5911
There is a bad case value received in the case statement in the Network Layer
Handler module.
Severity: Minor.
BUG5912
SNMP trap: Yes
The network layer connection table does not exist.

Severity: Minor.
BUG5913
SNMP trap: Yes
There is a bad case value received in the case statement in the Network Layer
Handler module.
Severity: Minor.
BUG5914
SNMP trap: Yes
Could not allocate unprotected Voice Mailbox Administration application data

block. This could be due to low memory.
Severity: Minor.
BUG5915
SNMP trap: Yes
Could not allocate unprotected Voice Mailbox delete block. This could be due
to low memory.
Severity: Minor.
BUG5916
SNMP trap: Yes
Could not allocate unprotected Voice Mailbox Update-In-Progress block. This

could be due to low memory.
Severity: Minor.
BUG5919
SNMP trap: Yes
PRB_PTR = NIL in call to procedure WHICH_DNIS_DIGS.

Action:
Severity: Minor.
SNMP trap: Yes
BUG5928 {DSL #} {BUG CAUSE VALUE} Set UIPE BRIT D channel pointers failed. The
following is a list of cause values for BUG5928:
1 = Invalid DSL number
System Messages
Page 462 of 2360

2 = TNTRANS failed for the DSL number
3 = The unit type is not a trunk
4 = The DSL is nota BRIT B-channel
5 = The card type is not a BRI line card
6 = The MISP loop TN is invalid
7 = The protected MISP loop pointer is nil
8 = The ABS loop type is not a MISP loop
9 = The unprotected MISP loop pointer is nil
10 = Set route pointers for the DSL failed
11 = Set MSDLMISP pointers failed
Action:
Severity: Minor.
SNMP trap: Yes
BUG5929 {DSL #} {Request value} Invalid request for the BRIT maintenance control.
Action:
Severity: Minor.
SNMP trap: Yes
BUG5930 {DSL #} {BRIT maintenance state} Invalid BRIT maintenance timeout event {DSL #}
Action:
Severity: Minor.
BUG5931
SNMP trap: Yes
BRIT Timer T309 expired while the link was established {DSL #} {BRIT DCH
link status}
Action:
Severity: Minor.
BUG5932
SNMP trap: Yes
Invalid BRIT B-channel detected {DSL #} {Invalid B-channel TN}

Action:
Severity: Minor.
BUG5933
SNMP trap: Yes
The BRIT trunk timing pointer was found to be nil {DSL #} {Trunk timing
pointer}
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 463 of 2360

BUG5934
The BRIT message cr is nil for building messages {DSL #} {Maintenance cr

pointer}
Action:
Severity: Minor.
BUG5935
SNMP trap: Yes
The message type is invalid for the BRIT message building function. {DSL #}
{Maintenance cr pointer}
Action:
Severity: Minor.
BUG5936
SNMP trap: Yes
An invalid TN B-channel detected by the message builder {DSL #} {Invalid

B-channel TN}
Action:
Severity: Minor.
BUG5937
SNMP trap: Yes
An invalid message detected by the BRIT message decoder {DSL #} {Invalid

message}
Action:
Severity: Minor.
BUG5938
SNMP trap: Yes
A Call Register cannot be obtained for saving messages {DSL #} {Call

Register pointer}
Action:
Severity: Minor.
BUG5939
SNMP trap: Yes
Invalid number of BRIT channels found during incoming message processing

{DSL #} {Invalid number of BRIT channels value}
Action:
Severity: Minor.
BUG5940
SNMP trap: Yes
Invalid BRIt channel number found during incoming message processing

{DSL #} {Invalid number of BRIT channels value}
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 464 of 2360

BUG5941
Invalid request for the PRI maintenance control.

Action:
Severity: Minor.
BUG5942
SNMP trap: Yes
Invalid PRI maintenance state

Action:
Severity: Minor.
BUG5943
SNMP trap: Yes
The PRI maintenance timeout event is not compatible the PRI maintenance
state.
Action:
Severity: Minor.
BUG5944
SNMP trap: Yes
Invalid PRI maintenance state for timeout event.

Action:
Severity: Minor.
BUG5945
SNMP trap: Yes
T309 timeout event when the D channel is established. The T309 timer should
be cancelled when the D channel link is established.
Action:
Severity: Minor.
BUG5946
SNMP trap: Yes
Invalid request for the PRI I/O control interface.

Action:
Severity: Minor.
SNMP trap: Yes
BUG5947 {DCH#} {BUG cause value} Set UIPE PRI D-channel pointers failed. The following is
a list of cause values for BUG5947: 1 = Invalid D channel number 2 = The
log_io_ptr is nil 3 = The pra logical application is not configured
4 = The D channel block pointer is nil
5 = The D channel configured is not PRI UIPE
6 = The pointer to the physical I/O block is nil
7 = The pointer to the unprotected DCH block is nil
8 = Pointer to the protected call reference tbl is nil
9 = Pointer to the unprotected call reference tbl is nil
10 = Pointer to the unprotected message table is nil
11 = Pointer to the DCH output buffer is nil
553-3001-411
Standard 15.00
January 2006
Page 465 of 2360

12 = Pointer to the unprotected backup DCH block is nil
13 = DCH is not configured on MSDL card
14 = Set MSDL/MISP pointers failed
15 = The MSDL expediated input buffer pointer is nil
16 = The MSDL ring input buffer pointer is nil
17 = The DCH aux block pointer is nil
Action:
Severity: Minor.
BUG5948
SNMP trap: Yes
Invalid PRI layer 2 request.

Action:
Severity: Minor.
BUG5949
SNMP trap: Yes
Invalid timeout detected for UIPE layer 2.

Action:
Severity: Minor.
BUG5950
SNMP trap: Yes
SNMP trap: Yes
Invalid timeout event.

Action:
Severity: Minor.
BUG5952
Set MSDL/MSIP pointers failed.

Action:
Severity: Minor.
BUG5953
SNMP trap: Yes
Invalid request for the PRI print utility.

Action:
Severity: Minor.
BUG5954
SNMP trap: Yes
The TN of the trunk passed to the PRI maintenance control for a B-channel
restart is invalid.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 466 of 2360

BUG5955
The trunk timing pointer is nil.

Action:
Severity: Minor.
BUG5956
SNMP trap: Yes
An invalid TN is found during the PRI maintenance build message function.

Action:
Severity: Minor.
BUG5958
SNMP trap: Yes
The maintenance message builder cannot build the message requested. (See
reason codes below.) Reason codes for BUG5958: 1 = The g_msgcrptr
pointer is nil for building message.
2 = The message type is invalid for the UIPE PRI build message function.
Action:
Severity: Minor.
BUG5959
SNMP trap: Yes
The maintenance message decoder cannot decode the message requested.

(See reason codes below.) Reason codes for BUG5959 1 = The message
requested for decoding is not supported.
2 = Cannot obtain a message cr to save the message.
Action:
Severity: Minor.
BUG5960
SNMP trap: Yes
Pointer to LAPW IO block is NIL.

Action:
Severity: Minor.
BUG5961
SNMP trap: Yes
RFW key is defined but ARFW package is not equipped.

Action:
Severity: Minor.
BUG5962
SNMP trap: Yes
ACTIVE_IN_RCFW state is not valid for attempted RCFW operation.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 467 of 2360

BUG5963
Input_type into ATT_RCFW is not valid.

Action:
Severity: Minor.
BUG5964
SNMP trap: Yes
Invalid ATT_RFW_STATE for attempted operation.

Action:
Severity: Minor.
BUG5965
SNMP trap: Yes
Invalid RESULT state for attempted operation.

Action:
Severity: Minor.
BUG5966
SNMP trap: Yes
TCAP Call Register undefined in NRCFW operation.

Action:
Severity: Minor.
BUG5967
SNMP trap: Yes
Invalid return code for DN interpretation.

Action:
Severity: Minor.
BUG5968
SNMP trap: Yes
Incorrect index into digits for Forward DN.

Action:
Severity: Minor.
BUG5969
SNMP trap: Yes
Invalid RCFW_RESP_TYPE
Action:
Severity: Minor.
BUG5970
SNMP trap: Yes
Invalid RCFW_MSG_TYPE
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 468 of 2360

BUG5972
Failure of Setting Ptrs or Flags in ISAP module.

Action:
Severity: Minor.
BUG5973
SNMP trap: No
Invalid Source in ISAP module.

Action:
Severity: Minor.
BUG5974
SNMP trap: No
Invalid Interface Type in ISAP module.

Action:
Severity: Minor.
BUG5975
SNMP trap: No
Invalid request in ISAP module.

Action:
Severity: Minor.
BUG5976
SNMP trap: No
The cr pointer passed to global proc. NRPA_HANDLER is NIL (network RPA).

Action:
Severity: Minor.
BUG5977
SNMP trap: Yes
Invalid TASK passed to global proc. NRPA_HANDLER (network RPA).

Action:
Severity: Minor.
BUG5978
SNMP trap: Yes
No cr is available to allocate a RPA rose cr for network RPA.

Action:
Severity: Minor.
BUG5979
SNMP trap: Yes
Unexpected Rose component type received in proc NRPA_RECV_FAC for

network RPA.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 469 of 2360

BUG5980
Unexpected Rose operation value received in proc NRPA_RECV_FAC for

Action:
Severity: Minor.
BUG5981
SNMP trap: Yes
Failure of setting ptrs or uipe flag in ISAP module.

Action:
Severity: Minor.
BUG5982
SNMP trap: Yes
Unknown source in ISAP module.

Action:
Severity: Minor.
BUG5983
SNMP trap: Yes
Unknown interface type in ISAP module.

Action:
Severity: Minor.
BUG5984
SNMP trap: Yes
Unknown request in ISAP module.

Action:
Severity: Minor.
BUG5985
SNMP trap: Yes
FROM_ITEM (the "interworking from" tn) passed into Procedure

UIPE_INTERWORK is neither the ORIGTN nor the TERTN.
Action: Check the calling procedure to see if the correct TN has been passed in
to UIPE_INTERWORK.
Severity: Minor.
BUG5986
SNMP trap: Yes
TNTRANS failed on the "interworking to" tn in Procedure UIPE_INTERWORK

Action:
Severity: Minor.
BUG5987
SNMP trap: Yes
EVENT_TYPE passed in to Procedure UIPE_INTERWORK is invalid.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 470 of 2360

BUG5988
DCH_WO_PRIM_ID is not an application data request. Return Build Message

Initialization failed. (Procedure UIPE_BLDMSG_INIT)
Action:
Severity: Minor.
BUG5989
SNMP trap: Yes
The "interworking to" message cr (TO_MSGCR) is nil. (Procedure

MAP_TO_UNIV and Procedure MAP_TO_IFC_SPEC)
Action:
Severity: Minor.
BUG5990
SNMP trap: Yes
The "interworking to" message cr (ORIG_MSGCR) is nil in Procedure

O_SETUP_ISDNITWK
Action:
Severity: Minor.
BUG5991
SNMP trap: Yes
SETCUSTPTRS failed in Procedure GET_ISDN_CALLED.

Action:
Severity: Minor.
BUG5992
SNMP trap: Yes
Invalid request for the BRIT print utility in UPRT module.

Action:
Severity: Minor.
BUG5993
SNMP trap: Yes
Request for UIPE_UTIL is not a valid choice.

Action:
Severity: Minor.
BUG5994
SNMP trap: Yes
Invalid primitive data length or IE length in UPRT module.

Action:
Severity: Minor.
BUG6006
SNMP trap: Yes
Unable to physically change the RFW lamp status.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 471 of 2360

BUG6007
Invalid display mode for attempted operation.

Action:
Severity: Minor.
BUG6008
SNMP trap: Yes
RCFW Call Register should be defined.

Action:
Severity: Minor.
BUG6009
SNMP trap: Yes
Invalid NRCFW parameter.

Action:
Severity: Minor.
BUG6010
SNMP trap: Yes
Invalid RCFW parameter.

Action:
Severity: Minor.
BUG6012
SNMP trap: Yes
RCFW FFC expected in digits.

Action:
Severity: Minor.
BUG6013
SNMP trap: Yes
RCFW message response timeout. For Attendant RCFW operation, the

remote node requires Attendant Network Remote Call Forward package 253.
Action:
Severity: Minor.
BUG6014
SNMP trap: Yes
RCFW_TO_DN interpretation is looping.

Action:
Severity: Minor.
BUG6015
SNMP trap: No
The incoming trunk is not a DPNSS trunk when the global procedure
R2MFC_DPNSS_CALL is invoked to send back a DPNSS response
message.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 472 of 2360

BUG6016
TNTRANS on MFC_ORIGTN fails or TNTRANS on ORIGTN fails when the

global procedure R2MFC_DPNSS_CALL is invoked to send back a R2MFC
backward signal.
Action:
Severity: Minor.
BUG6017
SNMP trap: Yes
A problem occurred when attempting to recover packages during cold start

(option 81 only).
Action: Print out the list of equipped packages in LD 22. If it does not match that
on the label, restart the system. If it does, use LD 17 to configure the current
language as desired.
Severity: Minor.
BUG6018
SNMP trap: Yes
The language setup information could not be recovered from the disk.
Language is forced to English (option 81 only).
Action: Use LD 17 to configure the current language as desired.
Severity: Minor.
BUG6019
SNMP trap: Yes
Call ID free list head or tail pointers are invalid. This may be due to data
corruption. The Call ID table is reinitializing. The Call ID values in existing Call
Registers cannot be cleared, so some related BUG messages may appear in
addition to this one (particularly BUG5835).
Action:
Severity: Minor.
BUG6021
SNMP trap: Yes
CFHO - Protocol or State problem in ISDN/NAS environment.

Action:
Severity: Minor.
BUG6022
SNMP trap: Yes
ISDN_CRLINK field of the unprotected DPNSS channel block was not nil
when trying to allocate a new DPNSS ISDN CR in procedure
INIT_DPNSS_MSGCR.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 473 of 2360

BUG6023
ISDN_CRLINK field of the unprotected DPNSS channel block should not be

nil.
Action:
Severity: Minor.
BUG6024
SNMP trap: Yes
Invalid ATT_RCFW message type.

Action:
Severity: Minor.
BUG6025
SNMP trap: Yes
Main CR not linked to TCAP CR in NRCFW operation.

Action:
Severity: Minor.
BUG6026
SNMP trap: Yes
Unable to obtain attendant customer pointers.

Action:
Severity: Minor.
BUG6027
SNMP trap: Yes
No destination for RCFW response message received.

Action:
Severity: Minor.
BUG6028
SNMP trap: Yes
Invalid Orig_id in RCFW operation.

Action:
Severity: Minor.
BUG6029
SNMP trap: Yes
Incorrect RCFW_TO_DN interpretation.

Action:
Severity: Minor.
BUG6030
SNMP trap: Yes
Invalid password in CFW_CHG message.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 474 of 2360

BUG6031
Invalid RCFW_RESP_TYPE for attempted operation.

Action:
Severity: Minor.
BUG6032
SNMP trap: Yes
Unable to initialize attendant global variables.

Action:
Severity: Minor.
BUG6033
SNMP trap: Yes
TNTRANS on the attendant TN failed.

Action:
Severity: Minor.
SNMP trap: Yes
BUG6034 n ftn ttn crptr This is a standard message that applies to the universal gateways.
n = the type of problem that occurred ftn = the tn of the unit originating the
event ttn = the destination tn of the event
crptr = the crptr value when the problem occurred
Action:
Severity: Minor.
BUG6035
SNMP trap: Yes
This TSP TN cannot be located in either the DNA or the local table.
Action:
Severity: Minor.
BUG6036
SNMP trap: Yes
Number larger than 3,999,999,999 has been passed to procedure

TEN_NBLS_HEX_CNV.
Action:
Severity: Minor.
BUG6037
SNMP trap: Yes
Parameter NUM_DIGS is larger than 10.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 475 of 2360

BUG6038
A non Binary Coded Decimal has been passed into procedure

TEN_NBLS_HEX_CNV.
Action:
Severity: Minor.
BUG6039
SNMP trap: Yes
MSGCR of outgoing trunk is nil in procedure AOC_REQUEST.

Action:
Severity: Minor.
BUG6040
SNMP trap: Yes
Too many supplementary services are being requested at the same time using
the Keypad IE (AXE-10 AUS).
Action:
Severity: Minor.
BUG6041
SNMP trap: Yes
A supplementary service request is to be built, but the IE LENGTH is zero.

Action:
Severity: Minor.
BUG6042
SNMP trap: Yes
Message/State problem in global procedure ABDN, ORIGTN, TERTN, ABDN

state, ABDN task and message type are printed.
Action:
Severity: Minor.
BUG6043
SNMP trap: Yes
Feature condition error in global procedure ABDN, ORIGTN, TERTN, ABDN

state, ABDN task and ABDN parameter are printed.
Action:
Severity: Minor.
BUG6044
SNMP trap: Yes
Customer or attendant pointers could not be set in global procedure ABDN.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 476 of 2360

BUG6045
ABDN state change problem in global procedure ABDN, ORIGTN, TERTN,

ABDN state, ABDN task and new state are printed.
Action:
Severity: Minor.
BUG6051
SNMP trap: Yes
The data in the language file has an incorrect format. The translation status is
forced to NONE.
Action: First go to Load 17 and configure prompt TRNS with the desired option.
Then do a data dump.
Severity: Minor.
BUG6053
SNMP trap: Yes
General BUG for the OHOL feature. Where: nn is the case # into the global
procedure OHOL.
Action:
Severity: Minor.
BUG6057
SNMP trap: Yes
Procedure CHECK_DVG_CLEAR module DSS CPRTR is NIL. No diversion

possible.
Action:
Severity: Minor.
BUG6058
SNMP trap: Yes
A Call ID could not be allocated for a call arriving at a CDN. Since CCR cannot
control a call without a Call ID, the call is given default treatment. Under normal
circumstances, this should not happen.
Action:
Severity: Minor.
BUG6064
SNMP trap: Yes
TNTRANS failure in the VNS state handler

Action:
Severity: Minor.
BUG6065
SNMP trap: Yes
Failed to send an answer on a bearer trunk used by VNS

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 477 of 2360

BUG6068
Itemptr passed to global procedure SET_OPS_PADS is nil.

Action:
Severity: Minor.
BUG6069
SNMP trap: Yes
INITCR failed. Cannot get a new Call Register.

Action:
Severity: Minor.
BUG6070
SNMP trap: Yes
ACRL_HANDLER. Passed parameter SOURCE is invalid.

Action:
Severity: Minor.
BUG6071
SNMP trap: Yes
Pointer to Call Register is not on a valid range.

Action:
Severity: Minor.
BUG6072
SNMP trap: Yes
Target party should be on TERside of the Call Register.

Action:
Severity: Minor.
BUG6073
SNMP trap: Yes
Cannot have a route optimization attempt when there is a call on hold on the
AC15 trunk.
Action:
Severity: Minor.
BUG6074
SNMP trap: Yes
Invalid return value from TRANSFER_CALL.

Action:
Severity: Minor.
BUG6079
SNMP trap: Yes
HUNT feature data space could not be found, even though it has been found
previously. (SBA)
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 478 of 2360

BUG6080
EHT feature data space could not be found, even though it has been found
previously. (SBA)
Action:
Severity: Minor.
BUG6081
SNMP trap: Yes
FDN feature data space could not be found, even though it has been found
previously. (SBA)
Action:
Severity: Minor.
BUG6082
SNMP trap: No
EFD feature data space could not be found, even though it has been found
previously. (SBA)
Action:
Severity: Minor.
BUG6083
SNMP trap: Yes
No CFW key could be found, even though one has been found previously.
(SBA)
Action:
Severity: Minor.
BUG6084
SNMP trap: Yes
CFW key/feature data space could not be found, even though it has been
found previously. (SBA)
Action:
Severity: Minor.
BUG6085
SNMP trap: Yes
No BFS key could be found, even though one has been found previously
(SBA).
Action:
Severity: Minor.
BUG6086
SNMP trap: Yes
BFS key data space could not be found, even though it has been found
previously. (SBA)
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 479 of 2360

BUG6087
No VCC key could be found, even though one has been found previously.
(SBA)
Action:
Severity: Minor.
BUG6088
SNMP trap: No
VCC key data space could not be found, even though it has been found
previously. (SBA)
Action:
Severity: Minor.
BUG6089
SNMP trap: No
No DIG key could be found, even though one has been found previously.
(SBA)
Action:
Severity: Minor.
BUG6090
SNMP trap: No
DIG key/feature data space could not be found, even though it has been found
previously. (SBA)
Action:
Severity: Minor.
BUG6091
SNMP trap: No
No GRC key could be found, even though it has been found previously.
Action:
Severity: Minor.
BUG6092
SNMP trap: No
GRC key data space could not be found, even though it has been found
previously. (SBA)
Action:
Severity: Minor.
BUG6093
SNMP trap: No
No SSC/SSU key could be found, even though one has been found previously.
(SBA)
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 480 of 2360

BUG6094
SSC/SSU key/feature data space could not be found, even though it has been
Action:
Severity: Minor.
BUG6095
SNMP trap: No
No SCC/SCU key could be found, even though one has been found
previously. (SBA)
Action:
Severity: Minor.
BUG6096
SNMP trap: No
Neither SCC nor SCU feature is configured, even though one has been found
previously. (SBA)
Action:
Severity: Minor.
BUG6097
SNMP trap: No
SCC/SCU key/feature data space could not be found, even though it has been
Action:
Severity: Minor.
BUG6098
SNMP trap: No
No HOT L key could be found, even though one has been found previously.
(SBA)
Action:
Severity: Minor.
BUG6099
SNMP trap: No
HOT key/feature data space could not be found, even though it has been
Action:
Severity: Minor.
BUG6100
SNMP trap: No
HOT key is not configured for Hot List, even though it was previously thought
to be. (SBA)
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 481 of 2360

BUG6101
Invalid parameters passed to BRIT_DCH_HDLR or UBRIT_DCH_HDLR.

Action:
Severity: Minor.
BUG6103
SNMP trap: Yes
The number of M1 CT2 Mobility TN's configured in the system has reached the
Action:
Severity: Minor.
BUG6104
SNMP trap: No
The number of MCM TN's configured in the system has reached zero or is less
than zero.
Action:
Severity: Minor.
BUG6106
SNMP trap: No
Invalid Group Hunt List. PLDN cannot be retrieved.

<customer number, speed call list or pilot DN, bug_print_crptr>
Action:
Severity: Minor.
BUG6107
SNMP trap: Yes
A message has been received for a VNS D-Channel on an UIPE link.

Procedure LINK_MSGCR. Module UICC.
Action:
Severity: Minor.
BUG6109
SNMP trap: Yes
ICITYPE is out-of-range in procedure GET_ICI_KEYNO.

Action:
Severity: Minor.
BUG6110
SNMP trap: Yes
ISDN BRI Supplementary Services error for NI-1 Call Forward For All Calls or
ETSI Call Forwarding Unconditional.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 482 of 2360

BUG6119 yz
MPO_HANDLER has been invoked with an incorrect TASK ID for the current
state. z . Where: y = TASK_ID and z = MPO_STATE
Action:
Severity: Minor.
BUG6120
SNMP trap: Yes
An attempt was made to log out a Set Based Administration session whose
session type could not be identified.
Action:
Severity: Minor.
BUG6121
SNMP trap: Yes
A Set Based Administration block pointer was found to be nil.

Action:
Severity: Minor.
BUG6122
SNMP trap: Yes
A Set Based Administration logged-in TN is not the ORIGTN.

Action:
Severity: Minor.
BUG6123 s
SNMP trap: Yes
A multi-user login session type could not be identified. s is the hex value of the
session number.
Action:
Severity: Minor.
BUG6124
SNMP trap: Yes
Set Based Administration: The active logins counter indicates that there
should be available login sessions, however no free sessions can be found.
Action:
Severity: Minor.
BUG6125
SNMP trap: Yes
A Set Based Administration session made a request to register a TN or DN for

change, however the session already has a TN registered to it.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 483 of 2360

BUG6126
A Set Based Administration session made a request to release a TN or DN

which is not currently registered to that session.
Action:
Severity: Minor.
BUG6127 c
SNMP trap: Yes
Logging out a Set Based Administration session would have taken one of the
login counts below zero. Where: c specifies the value of the login counter.
Action:
Severity: Minor.
BUG6128
SNMP trap: Yes
A call was made to initialize the Set Based Administration restriction control
blocks but the block pointers are not nil. Initialization is not performed.
Action:
Severity: Minor.
BUG6140
SNMP trap: Yes
An MCR/MCN/PLS\R/PLN/HOT key of a BCS set TN is linked with a CR which

does not involve this TN as ORIGTN or TERTN
Action:
Severity: Minor.
BUG6141
SNMP trap: Yes
A TN is the TN list of the Wanted DN block, but the TN does not have any DN
key defined for this DN.
Action:
Severity: Minor.
BUG6142
SNMP trap: Yes
An MCR/MCN/PLS\R/PLN/HOT key of a BCS set TN is linked with a CR which

does not involve this TN as ORIGTN or TERTN
Action:
Severity: Minor.
BUG6143
SNMP trap: Yes
An event occurred during an established EI conference, but the SW could not

find the relevant Data for the conference loop contained in the current Call
Register.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 484 of 2360

BUG6144
An event occurred during an established EI conference, but the SW could not

find the relevant Data for the conference loop contained in the current Call
Register.
Action:
Severity: Minor.
BUG6145
SNMP trap: Yes
An event occurred during an established EI conference. The SW scanned the

conference data, but one of the three existing parties (Originator, Wanted,
Unwanted) was missing or there were more than three.
Action:
Severity: Minor.
BUG6147
SNMP trap: Yes
Abnormal disconnection from an established EI conference. The SW could not

identify the releasing party (Originator, Wanted, or Unwanted).
Action:
Severity: Minor.
BUG6148
SNMP trap: Yes
The party becoming idle is probably the Wanted party of an EI conference, but
is in an inconsistent state.
Action:
Severity: Minor.
BUG6150
SNMP trap: Yes
The EI Wanted set or Originating trunk was disconnected while waiting for the
Unwanted's IPL, but the EI Originating trunk is not in the expected state
Action:
Severity: Minor.
BUG6151
SNMP trap: Yes
GW_FUNCTION EI/BKI Gateway: Procedure EI_GW-SERVICE is called with

an invalid GW_FUNCTION parameter. The unexpected GW_FUNCTION is
printed.
Action:
Severity: Minor.
BUG6152
553-3001-411
SNMP trap: Yes
SUPP_SERV_STATE. Unexpected supplementary service state on the

DPNSS side of the EI/BKI Gateway:
FACILITY WITH "CAMPON allowed" or "CAMP ON not allowed" or "End User
Alert" or "End User Connect" or "Breakin Consult" or Break-in extension
Standard 15.00
January 2006
Page 485 of 2360

allowed" is received on the MCDN side, but the DPNSS side is not in the
expected supplementary state.
The unexpected supp state is printed. The supp state on the DPNSS side is
forced to the expected value.
Action:
Severity: Minor.
BUG6153
SNMP trap: Yes
SUPP_SERV_STATE. Unexpected EI supplementary service state on the

ALERT has been received on the MCDN side, but the supplementary service
state on the DPNSS side is not EI_R_RCVD as expected.
The unexpected DPNSS supp service state is printed. The ACK string is not
included in the outgoing NAM on the DPNSS side.
Action:
Severity: Minor.
BUG6154
SNMP trap: Yes
An event occurred on the Originating or the Unwanted trunk while EI was

taking place, but the SW could not retrieve all the parties involved because of
data inconsistency.
Action:
Severity: Minor.
BUG6155
SNMP trap: Yes
The SW could not find the resources required to provide the Intrusion tone to
the EI conference it was trying to set up. The EI request is consequently
rejected.
Action:
Severity: Minor.
BUG6156
SNMP trap: Yes
EI/BKI Gateway: TNTRANS failed.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 486 of 2360

BUG6157
SERVICE_STATE . Unexpected service state on the DPNSS side of the

EI/BKI Gateway: FACILITY informing Break-in Denied or Break-In Temporary
Denied is received on the MCDN side. The Service state on the DPNSS side
is not .SUPP_SERV_EI as expected. The unexpected DPNSS service state is
printed. The call is cleared.
Action:
Severity: Minor.
BUG6158
SNMP trap: Yes
SUPP_SERV_STATE. Unexpected supplementary service state on the

DPNSS side of the EI/BKI Gateway: FACILITY informing Break-in Denied or
Break-in Temporary Denied is received on the MCDN side. The EI
Supplementary Service state on the DPNSS side is not .EI_R_RCVD as
expected.
The unexpected DPNSS service state is printed. The call is cleared.
Action:
Severity: Minor.
BUG6159
SNMP trap: Yes
SUPP_SERV_STATE. Unexpected EI supplementary service state on the

Received FACILITY with "end user alert" or "end user connect" but the
DPNSS side is in an unexpected supplementary service state. The expected
supplementary service state is EI_CCM_SENT.
The FACILITY msg is ignored. The unexpected service state is printed.
Action:
Severity: Minor.
BUG6160
SNMP trap: Yes
SERVICE_STATE. Unexpected EI service state on the DPNSS side of the

EI/BKI Gateway:
Received FACILITY with "BKI cancelled" but the DPNSS side is in an
unexpected service state. The expected service state is .SUPP_SERV_EI.
The FACILITY msg is ignored. The unexpected service state is printed.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 487 of 2360

BUG6161
ID_CODE. EI/BKI Gateway:

Illegal case entry in procedure EI_GW_SND_EEM. The wrong value of
parameter ID_CODE is printed.
Action:
Severity: Minor.
BUG6162
SNMP trap: Yes
SUPP_SERV_STATE
Unexpected EI supplementary service state on the DPNSS side of the EI/BKI
Gateway: FACILITY with "BKI cancelled" is received on the MCDN side, but
the DPNSS side is not in the expected supplementary service state
.EI_CCM_SENT. The unexpected supplementary service state is printed. The
supp state on the DPNSS side is forced to .EI_CCM_SENT.
Action:
Severity: Minor.
BUG6163
SNMP trap: Yes
SUPP_SERV_STATE EI/BKI Gateway: Cannot send a NAM because value of

TRK_IS_INCOMING is FALSE: procedure EI_GW_SIMU_ALERT(). The supp
state in which the problem occurs is printed. NAM is not sent.
Action:
Severity: Minor.
BUG6164
SNMP trap: Yes
Simple call MCDN/DPNSS Gateway: TNTRANS failed in procedure

SEND_FAC-U_CNCT
Action:
Severity: Minor.
BUG6166
SNMP trap: Yes
The SW has received a CO to EI conversion request. It has found the Wanted

TN and CR we want to intrude to, but this CR is not marked as having a call
camped on to it.
Action:
Severity: Minor.
BUG6168
SNMP trap: Yes
The Wanted CR has MNABIT = .TRUE, but the Wanted DN is not a MADN
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 488 of 2360

BUG6169 W Y Z
MPO_HANDLER was unable to perform specified task.

Where:
W = MPO_STATE
Y = task identifier
Z = failure identifier
Action:
Severity: Minor.
BUG6172
SNMP trap: Yes
A potential data corruption situation is captured. Correction is attempted to

prevent the corruption.
Action: Please finish up the service change session and print out the data to
ensure the integrity before continuing..
Severity: Minor.
BUG6173
SNMP trap: Yes
In IDLECR, the Call Register CRPTR could not be removed from the
corresponding queue by calling REMOVE. As a result, this Call Register can't
be returned to the IDLE queue to prevent further corruption to the queuing
system.
Action:
Severity: Minor.
BUG6174
SNMP trap: Yes
Invalid call to NITC_ISDN_HNDLR (invalid source)

Action: If this problem persists, contact your technical support group.
Severity: Minor.
BUG6175
SNMP trap: Yes
Invalid call to NITC_ISDN_HNDLR (invalid request)

Action: If this problem persists, contact your technical support group.
Severity: Minor.
BUG6176
SNMP trap: Yes
Invalid ROSE_COMP_TAG in NITC_ISDN_HNDLR

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 489 of 2360

BUG6177
Invalid operation length in NITC_ISDN_HNDLR.

Severity: Minor.
BUG6178
SNMP trap: Yes
Invalid operation value in NITC_ISDN_HNDLR.

Severity: Minor.
BUG6179
SNMP trap: Yes
CRPTR is NIL or could not allocate new call register in NITC_ISDN_HNDLR

Severity: Minor.
BUG6180
SNMP trap: Yes
NITC_ISDN_HNDLR count not send ROSE message.

Action: If this problem persists, contact your technical support
Severity: Minor.
BUG6201
SNMP trap: Yes
SBB:message not buffered, type =, device num =.

XPEC card, type = 0
ISDLC card, type = 1
Action: Report the problem to your technical support.
Severity: Info.
BUG6202
SNMP trap: No
SBB:message discarded, type =, device num =.

XPEC card, type = 0
Severity: Info.
BUG6203
SNMP trap: No
SBB:sbbOff:turning message buffering (SBB) OFF.

Severity: Major.
SNMP trap: Yes
System Messages
Page 490 of 2360

BUG6204
SBB:XmitLinkAdd:no memory for link list.

Insufficient memory.
Severity: Major.
BUG6205
SNMP trap: Yes
SBB:Reduce sets configured on this device, type =, device nu =.

XPEC card, type = 0
Action: Reduce the number of sets on the device.
Severity: Info.
BUG6206
SNMP trap: Yes
SBB:sbbGetMsgQ:unable to create MsgQ. Insufficient memory.

Severity: Major.
BUG6207
SNMP trap: Yes
SBB:sbbGetMsgQ:unable to allocate SBB_Q_LST element. Insufficient

memory.
Severity: Major.
BUG6208
SNMP trap: Yes
SBB:sbbGetMsgQ:over SBB_MSG_Q_MAX. Reached message buffering

system limit of 20000 queues.
Severity: Major.
BUG6214
SNMP trap: Yes
Invalid bug number in all to NITC_BUG in NITC_ISDN_HNDLR

Action: If this problem persists, contact your Nortel representative.
Severity: Minor.
BUG6215 x
SNMP trap: Yes
The CDRTTA_ANS was not set up for a CDR record with a CDRTTA_ARR
stamp. The TTA information cannot be printed for this call. Where: x =
TOD2SEC . Procedures DO_TTA_RINGING and DO_TTA_QUEUEING in
module CDR.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 491 of 2360

BUG6216
Problem occurred during processing of Call Pickup operation

Action:
Severity: Minor.
BUG6227
SNMP trap: Yes
The ethUInit failed while setting up for ARP.

Action:
Severity: Minor.
BUG6228
SNMP trap: Yes
The netLibInit failed while setting up for ARP.

Action:
Severity: Minor.
BUG6229
SNMP trap: Yes
Network task does not exist while setting up for ARP.

Action:
Severity: Minor.
BUG6230
SNMP trap: Yes
The diskOsLnEnetSet failed while setting up for ARP.

Action:
Severity: Minor.
BUG6231
SNMP trap: Yes
Inattach failed while setting up for ARP.

Action:
Severity: Minor.
BUG6232
SNMP trap: Yes
The ifAddrSet failed while setting up for ARP.

Action:
Severity: Minor.
BUG6233
SNMP trap: Yes
Unable to get data for network DB for Primary.

Action: Check the network database file on /u.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 492 of 2360

BUG6234
Unable to get data for network DB for Secondary.

Action: Check the network database file on /u.
Severity: Minor.
BUG6235
SNMP trap: Yes
Network interface structure was not correctly initialized.

Action:
Severity: Minor.
BUG6236
SNMP trap: Yes
System fails to resolve the IP address conflict. Both primary and secondary
addresses are being used.
Action:
Severity: Minor.
BUG6237
SNMP trap: Yes
There has been a failure to correctly obtain network interface data.

Action:
Severity: Minor.
BUG6238
SNMP trap: Yes
There has been a failure to initialize the network interface.

Action:
Severity: Minor.
BUG6239
SNMP trap: Yes
Invalid physical address read from IOP.

Action: Check IOP's Ethernet chip.
Severity: Minor.
BUG6240
SNMP trap: Yes
There has been a failure to obtain the sub-netmask address.

Action:
Severity: Minor.
BUG6241
SNMP trap: Yes
There has been a failure to initialize the Network File System (NFS).
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 493 of 2360

BUG6242: {CODE}{IDC STEP PM}{CUST#}{TREE#}{ERROR SUB CODE} General debugging
message for Overlay 49, IDC tree. See procedure BUG_WARNING in Overlay
49.
Action:
Severity: Minor.
SNMP trap: Yes
BUG6243:{CUST#}{TREE#} In overlay 49, the INI recovery was tried and unsuccessful. Force
recovery by nilling the IDC_BR_PTR & SDID_LNKLST_PTR. It may result in
data corruption in the IDC tree.
Action:
Severity: Minor.
SNMP trap: Yes
BUG6244 Customer, TN SETCUSTPTRS failed. Customer number and terminal are printed.
Customer number is from the protected line block unless the terminal is a
DTR, which takes it from its active call register.
Action: Print TN block (except DTR) and reconfigure if customer number is not
correct.
Severity: Minor.
BUG6245
SNMP trap: Yes
An attempt is made to send a SSRM on a DASS/DPNSS channel even though

the channel state is still idle (ie., an ISRM has not been sent). The channel
state is updated so that any response received from the far end can be
handled correctly.
Action:
Severity: Minor.
BUG6246
SNMP trap: Yes
ACD TN found with its ACD CR in the main queue.

Output: ACD TN (unpacked format), ACD ID (DN format).
Action:
Severity: Minor.
BUG6253 {tn}
SNMP trap: Yes
The set indicated has a CR attached indicating that login displays are being
shown on this agent's display as if the agent were an MQA agent, but the set
has no MQA data block. The CR on the incalls key is idled and the keylink is
nilled.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 494 of 2360

BUG6254
An attempt was made to remove a Call Register from an idle agent queue for
an MQA agent, but no father CR could be found. An attempt was made to idle
any CRs in this aux cr chain, but other problems/bugs may be seen. If they
persist and service is affected, the system should be initialized.
Action:
Severity: Minor.
BUG6255
SNMP trap: Yes
Tntrans failed on the origtn for an MQA agent CR in an idle agent queue. The
Call Register was idled.
Action:
Severity: Minor.
SNMP trap: Yes
BUG6256 {tn} {acd dn} SET_ACD_PTRS failed in procedure put_in_idle_q for an MQA ACD
agent. The TN and ACD TN are given.
Action:
Severity: Minor.
BUG6257
SNMP trap: Yes
tntrans on orign:crptr failed in procedure acd_128ms_to.

Action:
Severity: Minor.
BUG6258 {tn}
SNMP trap: Yes
Unprotected ACD Position Pointer is nil for TN indicated. Data corruption may
have occurred.
Action: If the problems persist, perform a Service
Severity: Minor.
SNMP trap: Yes
BUG6259 {tn} {acd dn} The ACD DN queue this MQA ACD agent is supposed to be serving is
not in the agent's MQA data block.
Action: Logout and log back in again, respecifying the ACD DNs to be served.
Severity: Minor.
SNMP trap: Yes
BUG6260 {tn} {acd tn} SET_ACD_PTRS failed in procedure acd_agnt_login for an MQA ACD
agent. The TN and ACD DN are given.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 495 of 2360

BUG6261 {tn} {acd dn} SET_ACD_PTRS failed in procedure acd_agnt_logout for an MQA ACD
agent. The TN and ACD DN are given.
Action:
Severity: Minor.
SNMP trap: Yes
BUG6262 {tn} {acd dn} A son CR could not be defined for putting this MQA ACD agent into the
idle agent queue for the indicated ACD DN.
Action:
Severity: Minor.
BUG6263
SNMP trap: Yes
EvtEdt: Error Message lookup file is corrupted.

Action:
Severity: Minor.
BUG6268
SNMP trap: No
Bad entry to global procedure IAGT.

Severity: Minor.
BUG6269
SNMP trap: Yes
Invalid IAGT SFR feature.

Severity: Minor.
BUG6272
SNMP trap: Yes
P_IAGT_TN_BLK prt is not found for an acquired IAGT agent.

Severity: Minor.
BUG6273
SNMP trap: Yes
IAGT data pointer(s) are not found for an acquired IAGT agent.
Severity: Minor.
BUG6274
SNMP trap: Yes
Unable to create a son_cr. Procedure GET_NWK_CALLID.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 496 of 2360

BUG6277
Call failed to TNTRANS in RESERVE_TIMESLOT.

Action:
Severity: Minor.
BUG6278
SNMP trap: Yes
An invalid state of H.10 for bit 7 & 6 in TNB. Procedure IVR_GET_JUNCTOR.

Action:
Severity: Minor.
BUG6279
SNMP trap: Yes
There is no timeslot/junctor information to set up/take down the speechpath.

Procedure SETSPEECH_IVR.
Action:
Severity: Minor.
BUG6280
SNMP trap: Yes
SETONEWAY_IVR. Either the ULPXPTR was NIL or tried to enable a path

when the ULPYPTR was NIL.
Action:
Severity: Minor.
BUG6281
SNMP trap: Yes
DPNSS NS: an attempt has been made to find another termination for a call
after a night service divert request. the MAINPM returned (.NARS_CALL) is
not proper. A TERTN should already have been found for this call at this stage.
Severity: Minor.
BUG6282
SNMP trap: Yes
NS: a CCM has been received on a channel after a night service diversion.
Action: Ensure the third party complies with the BTNR.
Severity: Minor.
BUG6284
SNMP trap: Yes
During retrieval, the controlling channel in a Night Service process was not
tagged as DPNSS1.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 497 of 2360

BUG6285
There is a mismatch in the new and old call.

Severity: Major.
BUG6286
SNMP trap: Yes
Flags or pointer not properly set in a call register associated with DPNSS1
Night Service.
Severity: Minor.
BUG6291
SNMP trap: Yes
Call register idled when SON CR with CCR process type still linked.
Action:
Severity: Minor.
BUG6292
SNMP trap: Yes
ACD_TOF_CALL bit in CRPTR is set but the AUXPM is invalid. Procedure

ACD_RESTORE.
Action:
Severity: Minor.
BUG6293
SNMP trap: Yes
Incorrect input message received from the TDET when ARDL call processing.
Severity: Minor.
BUG6294
SNMP trap: Yes
Cannot spawn to reset power supply.

Action: If problem persists, contact your technical support group.
Severity: Minor.
BUG6295
SNMP trap: Yes
Cannot create semaphore for the Auxiliary Processor Interface.

Action: If the problem persists, contact your technical group.
Severity: Major.
BUG6296
SNMP trap: Yes
Cannot disable the Auxiliary Processor interrupt during initialization.

Action: If the problem persists, contact your technical support group.
Severity: Major.
SNMP trap: Yes
System Messages
Page 498 of 2360

BUG6297
Cannot install interrupt handler for Auxiliary Processor.

Severity: Major.
BUG6298
SNMP trap: Yes
Cannot enable the auxiliary processor interrupt during initialization.

Action: If a problem persists, contact your technical support group.
Severity: Major.
BUG6299
SNMP trap: Yes
Application interrupt received before ISR is installed.

Severity: Major.
BUG6300
SNMP trap: Yes
Invalid interrupt received from the AP interface.

Severity: Minor.
BUG6301
SNMP trap: Yes
Invalid application type x for installing ISR. This is caused by incorrect

software operation.
Severity: Minor.
BUG6302
SNMP trap: Yes
Security Check interrupt received without any pending action. This is caused
by incorrect software operation.
Severity: Minor.
BUG6303
SNMP trap: Yes
Invoke Security Check but AP interface is not installed. This is caused by

incorrect software operation.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 499 of 2360

BUG6304
Security Check failed. The interface is already busy. This is caused by

Severity: Minor.
BUG6305
SNMP trap: Yes
Security Check failed. Timeout waiting for response. This is caused by

Severity: Minor.
BUG6306
SNMP trap: Yes
Attempted to access an invalid CardLAN register. This is caused by incorrect

software operation.
Severity: Minor.
BUG6307
SNMP trap: Yes
Attempted to access a CardLAN register but the AP-CL is not installed.

Severity: Minor.
BUG6308
SNMP trap: Yes
Fail to install the AP-CardLAN interface.

Severity: Minor.
BUG6309
SNMP trap: Yes
Invalid data writing to the CardLAN control register. This is caused by incorrect
software operation.
Severity: Minor.
BUG6310
SNMP trap: Yes
Calling invalid intrinsic. This is caused by incorrect software operation.

Action: If the problem persists, initialize the system.
Severity: Minor.
BUG6311
SNMP trap: Yes
XCPU Invalid Message. Where eeee is the error code and uuuu is the unit #
on Card 0. Units 8-15 on Card 0 are now disabled. Error codes: 0000 - Invalid
Upper Unit Configuration Message from CP 0001 - Invalid Tone Detection
System Messages
Page 500 of 2360

Request from CP 0003 - Invalid Tone Detected by DSP 0004 - Invalid
MFC/MFE/MFK Signal Request from CP 0005 - Start/stop Detection Request
for Disabled Channel from CP
Action: To re-enable units 8-15, run ENLX 0 in LD34. If the problem persists,
contact your technical support group.
Severity: Minor.
BUG6312
SNMP trap: Yes
Invalid a31 number passed to a31 driver. This is caused by incorrect software
operation.
Severity: Minor.
BUG6313
SNMP trap: Yes
Invalid function passed to a31 driver. This is caused by incorrect software

operation.
Severity: Minor.
BUG6314
SNMP trap: Yes
Invalid a31 number passed to a31 test driver. This is caused by incorrect
software operation.
Severity: Minor.
BUG6315
SNMP trap: Yes
Invalid function passed to a31 test driver. This is caused by incorrect software
operation.
Severity: Minor.
BUG6316
SNMP trap: Yes
a31 Ready Int cannot dequeue message from queue. This may be due to
corrupted software queues.
Severity: Minor.
BUG6317
SNMP trap: Yes
a31 Input Int received interrupt from unconfigured a31.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 501 of 2360

BUG6318
a31 Input Int received interrupt without pending message in a31 FIFO.
Severity: Minor.
BUG6319
SNMP trap: Yes
Invalid polling PM detected in a31 Ready Int. This is caused by incorrect

software operation.
Severity: Minor.
BUG6320
SNMP trap: Yes
Transmit underflow detected when sending msg to a31.

Action:
Severity: Info.
BUG6321
SNMP trap: Yes
Invalid card number found in the IVD status array. This is caused by incorrect
software operation.
Severity: Minor.
BUG6322
SNMP trap: Yes
No output signaling buffers are available. The correct output message is lost.
Severity: Minor.
BUG6323
SNMP trap: Yes
Received poll response message but the PF bit is not set.

Action:
Severity: Info.
BUG6324
SNMP trap: Yes
Invalid cmdType passed to WRITE_TSIC. This is caused by incorrect software

operation.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 502 of 2360

BUG6325
Invalid function passed to 144_DRIVER. This is caused by incorrect software

operation.
Severity: Minor.
BUG6326
SNMP trap: Yes
Invalid logical ivd number passed to 144_GET_PHYS_IVD.

Severity: Minor.
BUG6327
SNMP trap: Yes
Invalid function passed to 144-SETUP. This is caused by incorrect software

operation.
Severity: Minor.
BUG6328
SNMP trap: Yes
Invalid parm passed to bo3Write. This is caused by incorrect software

operation.
Severity: Minor.
BUG6329
SNMP trap: Yes
Invalid parm passed to bo3Read. This is caused by incorrect software

operation.
Severity: Minor.
BUG6330
SNMP trap: Yes
Invalid conference loop passed to bo3TestDriver. This is caused by incorrect

software operation.
Severity: Minor.
BUG6331
SNMP trap: Yes
Auxiliary processor could not be started.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 503 of 2360

BUG6332
OS %d: CP SIO failed to create '/sio/2'.

Action: Try a manual INI. If this problem reoccurs do a cold start. If the problem
persists, contact your technical support group.
Severity: Major.
BUG6333
SNMP trap: No
OS %d: CP SIO failed to open '/sio/2'.

Action: Try a manual INI. If the problem reoccurs, do a cold start. If the problem
Severity: Major.
BUG6334
SNMP trap: No
Could not initialize PC Card ATA device driver.

Action: Try a manual INI. If the problem reoccurs, do a cold start. If the problem
Severity: Major.
BUG6335
SNMP trap: Yes
Could not mount device "%s".

Action: Try manual INI. If the problem reoccurs, do a cold start. If the problem
Severity: Major.
BUG6337
SNMP trap: Yes
Could not find file "%s".

Action: May or may not be service affecting, depending on the file. Attempt to
restore file. If this cannot be done, contact your technical support group.
Severity: Major.
BUG6338
SNMP trap: No
Error opening file "%s".

Severity: Major.
BUG6339
SNMP trap: No
Error reading file "%s".

Severity: Major.
SNMP trap: No
System Messages
Page 504 of 2360

BUG6340
Error seeking in file "%s".

Severity: Major.
BUG6341
SNMP trap: No
ssDrv: Resource acquisition error, task = %s, resource = %s, ID = %p, erno =
%s.
Action: Try a manual INI. If the problem persists contact your technical support
group.
Severity: Major.
BUG6342
SNMP trap: Yes
Resource creation error, task = %s, resource = %s, errno = %s

group.
Severity: Critical.
BUG6343
SNMP trap: Yes
ssDrv: Fatal error, unable to initialize drive.

group.
Severity: Critical.
BUG6344
SNMP trap: Yes
ssDrv: Drive space corrupted.

group.
Severity: Critical.
BUG6345
SNMP trap: Yes
ssDrv: No free tracks.

Action: Manual INI. If the problem persists contact your technical support group.
Severity: Critical.
BUG6346
SNMP trap: Yes
ssDrv: Logical block %d out of range.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 505 of 2360

BUG6347
ssDrv: Logical block %d mapping is invalid, caddr = %04X.

Severity: Minor.
BUG6348
SNMP trap: Yes
Flash write failure, task = %s, errno = %x, address = %p, data = %X, flash =
%X.
Severity: Major.
BUG6349
SNMP trap: Yes
ssDrv: Invalid chip address = %04X.

Severity: Minor.
BUG6350
SNMP trap: Yes
ssDrv: Semaphore %p held by deleted task %p.

Severity: Minor.
BUG6351
SNMP trap: Yes
ssDrv: unable to reverse map caddr = %04X.

Severity: Minor.
BUG6352
SNMP trap: Yes
ssDrv: erroneous condition detected.

Severity: Minor.
BUG6353
SNMP trap: Yes
ssDrv: Could not create admin track, write operations not possible.
Severity: Critical.
BUG6354
SNMP trap: Yes
NULL pointer
Severity: Minor.
SNMP trap: Yes
System Messages
Page 506 of 2360

BUG6355
Error accessing file %s: %s.

Severity: Minor.
BUG6360
SNMP trap: Yes
Invalid network interface address read from CS.

Action: Check CPU Ethernet chip. Contact your technical.
Severity: Major.
BUG6361
SNMP trap: Yes
SNMP trap: Yes
taskSpawn failed.
Action:
Severity: Major.
BUG6362
TOD content is wrong. Content is reset.

Severity: Major.
BUG6363
SNMP trap: Yes
Hardware interrupt is not cleared.

Action: Severity is Major only if a BUG6364 is not printed immediately after.
Severity: Major.
BUG6364
SNMP trap: Yes
Hardware interrupt is cleared.

Action: Information only, no action required.
Severity: Info.
BUG6394
SNMP trap: Yes
The VDN data structure is corrupted. Some VDN blocks may be lost.
Action: Run AUDIT to rebuild recoverable VDN blocks. Recreate VDN blocks
that have been lost.
Severity: Major.
BUG6395
SNMP trap: Yes
The call register passed to the global procedure IED_CHK is nil.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 507 of 2360

BUG6396
G_GF_MSGCRPTR is nil, cannot build call-indp msg.

Severity: Minor.
BUG6398
SNMP trap: Yes
The call register passed to the global procedure IED_CHK is nil.

Severity: Minor.
BUG6399
SNMP trap: Yes
In procedure RO_NO_CIM_RECVD, TER must be DPNSS as Route

Optimization process is in operation on this side of the CR of the new call.
Action: Run AUDIT, as there may be unreleased CR and/or wrong channel
states (new channel remains in a Route Optimization state).
Severity: Minor.
BUG6404
SNMP trap: Yes
A network call park operation is tried from one node to another node for which
the Call Park Networkwide feature is not defined.
Action: Contact your system administrator if the Call Park Networkwide
operation is desired.
Severity: Major.
BUG6405
SNMP trap: No
Unable to remove the reserved agent son cr from the main cr.
Action:
Severity: Minor.
BUG6406
SNMP trap: Yes
Agent reserved son cr cannot be linked to NSBR call.

Action:
Severity: Minor.
BUG6407
SNMP trap: Yes
NSBR call cannot be terminated to a CDN.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 508 of 2360

BUG6438
Invalid message type is passed to procedure IAGT.

Action:
Severity: Minor.
BUG6439
SNMP trap: Yes
Invalid agent resync state is found.

Action:
Severity: Minor.
BUG6440
SNMP trap: Yes
Invalid IAGT agent is found from agent link list.

Action:
Severity: Minor.
BUG6441
SNMP trap: Yes
CRPTR is out of range. Output: TERMINAL

Action:
Severity: Minor.
SNMP trap: Yes
BUG6442 {type of failure} {event/state} {parm1}{parm2}{pam3} Call Completion (CC)

Supplementary Service. Software failure detected by CC QSIG protocol
handler.
Action:
Severity: Minor.
SNMP trap: Yes
BUG6443 {cause} {source} Call Completion Supplementary Service. Error detected by CC

TERMINAL handler.
Action:
Severity: Minor.
SNMP trap: Yes
BUG6444 {type of error} {parms} Call Completion (CC) Supplementary Service. Error detected
by CC ETSI-T protocol handler.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 509 of 2360

BUG6445 {type of error} {type of gateway} {source in sscc_gateway} Call Completion (CC)
Supplementary Service. Error at a gateway node.
Action:
Severity: Minor.
SNMP trap: Yes
BUG6446 {protocol call-register pointer} Call Completion (CC) Supplementary Service.

Procedure FIND_USER_PTR failed.
Action:
Severity: Minor.
SNMP trap: Yes
BUG6447 {protocol call register pointer} Call Completion (CC) Supplementary Service.
Procedure FIND_PRA_MSG_PTR failed.
Action:
Severity: Minor.
SNMP trap: Yes
BUG6448 {protocol call register pointer} Call Completion (CC) Supplementary Service.
Procedure IDLE_PROT_CR failed.
Action:
Severity: Minor.
SNMP trap: Yes
BUG6449 {RCAP id} Call Completion (CC) Supplementary Service. Procedure HAS_RCAP
failed. Invalid RCAP id.
Action:
Severity: Minor.
SNMP trap: Yes
BUG6450 {source in sscc_utility} {int1} {int 2} {int 3} Call Completion (CC) Supplementary
Service. Invalid parameter pointer passed in SSCC-UTILITY.
Action:
Severity: Minor.
BUG6472
SNMP trap: Yes
The message header is too small.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 510 of 2360

BUG6473
Mobility virtual TN failed TNTRANS.

Action:
Severity: Minor.
BUG6474
SNMP trap: Yes
Message CR exists without a CRPTR for the specified cref on this TN.
Action: If the caller is not able to make calls, service changing the portable will
cause ForceDisconnect to clean up the lingering Message Cr.
Severity: Minor.
BUG6475
SNMP trap: Yes
Call reference flag is invalid for Setup Indication.

Action:
Severity: Minor.
BUG6476
SNMP trap: Yes
Message is less than expected length. IEs are missing.

Action:
Severity: Minor.
BUG6477
SNMP trap: Yes
Call rejected due to invalid timeslot.

Action:
Severity: Minor.
BUG6478
SNMP trap: Yes
SNMP trap: Yes
Message ID is invalid.
Action:
Severity: Minor.
BUG6479
Message received in an invalid state.

Action:
Severity: Minor.
BUG6480
SNMP trap: Yes
SNMP trap: Yes
Timeout occurred.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 511 of 2360

BUG6481
Case out of range.

Action:
Severity: Minor.
BUG6482
SNMP trap: Yes
MOB_INDATA_PTR is NIL. No incoming message is available to process.

Action:
Severity: Minor.
BUG6483
SNMP trap: Yes
Non-call processing message received when only a call processing message

was expected.
Action:
Severity: Minor.
BUG6484
SNMP trap: Yes
Failed to send message to the MSP.

Action:
Severity: Minor.
BUG6485
SNMP trap: Yes
CRPTR is out of valid range.

Action:
Severity: Minor.
BUG6486
SNMP trap: Yes
Message CR is out of range.

Action:
Severity: Info.
BUG6487
SNMP trap: Yes
Mobility data stored as non-key function does not exist.

Action:
Severity: Minor.
BUG6488
SNMP trap: Yes
Call reference is out of range.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 512 of 2360

BUG6489
Call register is out of range.

Action:
Severity: Minor.
BUG6490
SNMP trap: Yes
Call register could not be allocated for MSGCR.

Action:
Severity: Minor.
BUG6491
SNMP trap: Yes
Call reference specified is unexpectedly not being used.

Action:
Severity: Minor.
BUG6492
SNMP trap: Yes
Call reference specified is unexpectedly being used.

Action:
Severity: Minor.
BUG6493
SNMP trap: Yes
Timeout occurred in invalid state.

Action:
Severity: Minor.
BUG6494
SNMP trap: Yes
SNMP trap: Yes
Invalid Feature Event.

Action:
Severity: Minor.
BUG6495
Unable to retrieve Active Call.

Action:
Severity: Minor.
BUG6496
SNMP trap: Yes
Feature Key is not configured.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 513 of 2360

BUG6497
Two calls are in progress. Cannot activate call related features.

Action: Release on of the existing calls in order to be able to activate another
feature.
Severity: Minor.
BUG6498
SNMP trap: Yes
Existing MSGCR found while attempting to set up a new incoming or outgoing

call.
Action: MSGCR will be cleaned up when this is found. If incoming calls are ot
presented to the portable, service change the portable to cause Force Disconnect
to clean up the lingering message CR.
Severity: Minor.
BUG6499
SNMP trap: Yes
A CRPTR exists without a MSGCR for this cref.

Action: Portable will be cleaned up when this is found. If incoming calls are not
presented to the portable, service change the portable to cause Force Disconnect
to clean up portable.
Severity: Minor.
BUG6500
SNMP trap: Yes
SNMP trap: Yes
Cref check failed.

Action:
Severity: Minor.
BUG6501
Invalid input from dial pad.

Action:
Severity: Minor.
BUG6502
SNMP trap: Yes
Only one digit per message is permitted for now.

Action:
Severity: Minor.
BUG6503
SNMP trap: Yes
Unable to set up a call on this TN with the specified cref.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 514 of 2360

BUG6504
Physical TN is invalid.
Action:
Severity: Minor.
BUG6505
SNMP trap: Yes
Cref returned by MOB_GET_CREF is invalid.

Action:
Severity: Minor.
SNMP trap: Yes
BUG6506 <qmwi error no.><parm1><parm2> Error in message waiting supplementary service.

Severity: Major.
BUG7000
SNMP trap: Yes
SNMP trap: Yes
X invalid TID.
Action:
Severity: Minor.
BUG7001
Cannot spawn SKDTask. ERRNO n.

Action:
Severity: Minor.
BUG7002
SNMP trap: No
Bad TickTime Slice. Cannot start round-robin scheduling.

Action:
Severity: Minor.
BUG7011
SNMP trap: No
Checksum mismatch on page x, base address y.

Action:
Severity: Minor.
BUG7012
SNMP trap: No
Inconsistent checksum corrected on page x, base address y.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 515 of 2360

BUG7013
Attempt to change write protected memory from interrupt handler.

Action:
Severity: Minor.
BUG7014
SNMP trap: No
Register procedure not called yet.

Action:
Severity: Minor.
BUG7015
SNMP trap: No
Memory configuration problems.

Action:
Severity: Minor.
BUG7016
SNMP trap: No
MTR changed during fast mode.

Action:
Severity: Minor.
BUG7017
SNMP trap: No
MSYNC: No temporary memory available to perform memory verification.

Reinitialize the system with the MANUAL INIT button (top).
Action:
Severity: Minor.
BUG7018
SNMP trap: Yes
MSYNC: Memory mismatch corrected at addr a (loc = b; rem = c).

Action:
Severity: Minor.
BUG7019
SNMP trap: Yes
MSYNC: Sync failure at address a (local = b; remote = c).

Action: Use the TEST CP command in OVL135 to try to recover memory
shadowing.
Severity: Minor.
BUG7020
SNMP trap: Yes
Manual INIT in progress.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 516 of 2360

BUG7021
Cold start in progress because of {reason}.

Action:
Severity: Minor.
BUG7022
SNMP trap: Yes
Warm start in progress because of {reason}.

Action:
Severity: Minor.
BUG7023
SNMP trap: Yes
Task restart aborted - cannot send message to Restart task.

Action:
Severity: Minor.
BUG7024
SNMP trap: No
Task restart aborted - bad TID n.

Action:
Severity: Minor.
BUG7025
SNMP trap: No
Task table overflow on TID n.

Action:
Severity: Minor.
BUG7026
SNMP trap: No
Restart threshold exceeded in TID n.

Action:
Severity: Minor.
BUG7027
SNMP trap: Yes
Warning: task delete failed. TID = n.

Action:
Severity: Minor.
BUG7028
SNMP trap: No
Warning: unregistered task being restarted. TID = n.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 517 of 2360

BUG7029
Task being deleted. TID = n.

Action:
Severity: Minor.
BUG7030
SNMP trap: Yes
Task being restarted. TID = n.

Action:
Severity: Minor.
BUG7031
SNMP trap: Yes
Unknown request sent to Restart task. REQ = n.

Action:
Severity: Minor.
BUG7032
SNMP trap: No
Unable to create message queue.

Action:
Severity: Minor.
BUG7033
SNMP trap: No
Unable to spawn Restart task.

Action:
Severity: Minor.
BUG7034
SNMP trap: No
Manual INIT button disabled.

Action: Reload the system with the Manual reload button.
Severity: Minor.
BUG7035
SNMP trap: Yes
Unable to register protMem - bad range x to y.

Action:
Severity: Minor.
BUG7036
SNMP trap: No
Unable to register protMem - no memory available.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 518 of 2360

BUG7037
Unable to register protMem - write failure.

Action:
Severity: Minor.
BUG7038
SNMP trap: No
Checksum error found at address x.

Action:
Severity: Minor.
BUG7039
SNMP trap: No
Checksum error in Page Control Table.

Action:
Severity: Minor.
BUG7040
SNMP trap: No
Checksum error in disk OS Text segment.

Action:
Severity: Minor.
BUG7041
SNMP trap: No
Checksum error in disk OS Dynamic segment.

Action:
Severity: Minor.
BUG7042 x y
SNMP trap: No
Checksum error at address x caused by cold start.

Action: Reset the SIMM in SIMM slot y. If problem persists, replace the CP card.
Severity: Minor.
BUG7043
SNMP trap: Yes
System recovery failure. Task = n.

Severity: Minor.
BUG7044
SNMP trap: Yes
Restart subsystem failure. No automatic restart.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 519 of 2360

BUG7045
Exception caused task restart. TID = n, VEC = x, PC = y.

Action:
Severity: Minor.
BUG7058
SNMP trap: Yes
SWD: SWD watchdog timer expired on task tSL1, tid: 0x203e18fo, 5 times
pc= 0x1064b2e8, tPRI=240, tSTAT=SUSPEND
Action:
Severity: Minor.
BUG7060
SNMP trap: No
Hardware watchdog interrupt event.

Action:
Severity: Minor.
BUG7061
SNMP trap: No
Failed task restart. TID: x.

Action:
Severity: Minor.
BUG7062
SNMP trap: No
SNMP trap: No
Restarted task n TID x.

Action:
Severity: Minor.
BUG7063
Failed in CMB access. Address: n.

Action: Reset or replace CP card.
Severity: Minor.
BUG7064
SNMP trap: Yes
Failed in ISR registration. ISR number: n.

Action:
Severity: Minor.
BUG7065
SNMP trap: No
Failed to spawn "TSWD" task.

Action: Reload the system with the Manual reload button. Reinstall software
form the installation disks.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 520 of 2360

BUG7066
Broken task list. Number of tasks missing: n.

Action:
Severity: Minor.
BUG7067
SNMP trap: No
SNMP trap: No
SNMP trap: No
Invalid SWDID: x.
Action:
Severity: Minor.
BUG7068
Invalid TID: x.
Action:
Severity: Minor.
BUG7069
Failed to allocate SWD memory.

Severity: Minor.
BUG7070
SNMP trap: Yes
CP SRA unauthorized access.

Action:
Severity: Minor.
BUG7071
SNMP trap: No
CP self-configure in process.
Action:
Severity: Minor.
BUG7072
SNMP trap: No
X CP database parse error(s) occurred.

Action: Restore database from backup disks.
Severity: Minor.
BUG7073
SNMP trap: No
Power failure detected (Power Monitor).

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 521 of 2360

BUG7074
CMB detects error during DMA.

Action:
Severity: Minor.
BUG7075
SNMP trap: No
HPM detects local parity error.

Action:
Severity: Minor.
BUG7076
SNMP trap: No
BIC parity error detected: PARRERZ = x.

Action:
Severity: Minor.
BUG7077
SNMP trap: No
CP database not found.

Severity: Minor.
BUG7078
SNMP trap: No
Local fault (parity) threshold exceeded. Performing switchover.

Action: Reset or replace the CP card.
Severity: Minor.
BUG7079
SNMP trap: Yes
Local fault (parity) threshold exceeded. Switchover failed.

Action: Reset or replace the CP card.
Severity: Minor.
BUG7080
SNMP trap: Yes
Sending of enable event to ID {name} failed.

Action:
Severity: Minor.
BUG7081
SNMP trap: No
Sending of link event to ID {name} failed.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 522 of 2360

BUG7083
Local fault threshold exceeded. Performing switchover.

Action:
Severity: Minor.
BUG7100
SNMP trap: Yes
IPB database not found.

Action: Restore database from backup disk.
Severity: Minor.
BUG7101
SNMP trap: No
IPB database of an unexpected release.

Severity: Minor.
BUG7102
SNMP trap: No
IPB x database parse error(s) occurred.

Severity: Minor.
BUG7103
SNMP trap: No
IPB sending of ebanle event (ph7) to id {name} failed.

Action:
Severity: Minor.
BUG7104
SNMP trap: No
IPB sending of link event (ph5) to id {name} failed.

Action:
Severity: Minor.
BUG7105
SNMP trap: No
IPB card inserted did not fully seat IRQ disabled.

Action: Check card keying, or reseat the card.
Severity: Minor.
BUG7106
SNMP trap: Yes
SNMP trap: No
IPB datadump failed.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 523 of 2360

BUG7107
IPB parity threshold exceeded. Performing switchover.

Action:
Severity: Minor.
BUG7108
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: No
IPB switchover failed.

Action:
Severity: Minor.
BUG7109
IPB IRQ enabled.

Action:
Severity: Minor.
BUG7110
IPB Monitor failed on take of switchover prevent semaphore.

Action:
Severity: Minor.
BUG7130
SNMP trap: No
Space manager internal error at line {number}.

Action:
Severity: Minor.
BUG7160
SNMP trap: No
Connector x y unknown connection specification {name}.

Action:
Severity: Minor.
BUG7161
SNMP trap: No
Connector x y device {name} misidentified. Starting process of identification.

Action:
Severity: Minor.
BUG7180
SNMP trap: No
Network Control Bus x y ISR {name} not installed. Masking line {number}.
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 524 of 2360

BUG7181
Network Control Bus x y setting default base address to {address}.

Action:
Severity: Minor.
BUG7200
SNMP trap: No
Assert failed in file {number}, line {number}.

Action:
Severity: Minor.
BUG7201
SNMP trap: Yes
Error logged by object {name}.

Action:
Severity: Minor.
BUG7202
SNMP trap: No
Broken object in list of class: {name}.

Action:
Severity: Minor.
BUG7220
SNMP trap: No
SNMP trap: No
SNMP trap: No
Broken class list.

Action:
Severity: Minor.
BUG7221
Internal error logged.

Action:
Severity: Minor.
BUG7222
Class {name} failed in init phase.

Action: Reinitialize the system with the manual INIT button.
Severity: Minor.
BUG7224
SNMP trap: No
Corrupted HI EXEC Policy table.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 525 of 2360

BUG7225
Unknown recovery recommendation.

Action:
Severity: Minor.
BUG7226
SNMP trap: No
HI directory not known to DLO.

Action: Reinstall software from installation disk
Severity: Minor.
BUG7227
SNMP trap: No
Corrupted HI directory name: {file name}.

Severity: Minor.
BUG7228
SNMP trap: No
Cannot open directory {name}. Error number??

Severity: Minor.
BUG7229
SNMP trap: No
Failed to copy from {drive} to {drive}.

Action: Check that disk is in correct drive.
Severity: Minor.
BUG7230
SNMP trap: No
Failed to save {file name}. Error number ??

Action: Check CMDU power switch.
Severity: Minor.
BUG7231
SNMP trap: No
{Job ID} corrupted job control block.

Action:
Severity: Minor.
BUG7232
SNMP trap: No
{Job ID} stack underflow.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 526 of 2360

BUG7233
Number of servers started: {number} (out of ??).

Action:
Severity: Minor.
BUG7234
SNMP trap: No
{Job ID} failed swdCreate.

Action:
Severity: Minor.
BUG7235
SNMP trap: No
Failed to spawn procedure.

Action:
Severity: Minor.
BUG7236
SNMP trap: No
Cannot locate HI data directory.

Action: Restore the database from backup disk.
Severity: Minor.
BUG7237
SNMP trap: Yes
Bad status of {filename}.

Action:
Severity: Minor.
BUG7300
SNMP trap: No
Default resident symbol file not known to disk loader.

Action:
Severity: Minor.
BUG7301
SNMP trap: Yes
Null file name parameter to ldrLoadSymbolFile.

Action:
Severity: Minor.
BUG7302
SNMP trap: Yes
Cannot open {name} symbol file.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 527 of 2360

BUG7303
Error reading {name} symbol file.

Action:
Severity: Minor.
BUG7304
SNMP trap: Yes
{Name} invalid symbol format.

Action:
Severity: Minor.
BUG7305
SNMP trap: Yes
Error accessing {name} symbol file.

Action:
Severity: Minor.
BUG7306
SNMP trap: Yes
{Name} invalid symbol format.

Action:
Severity: Minor.
BUG7307
SNMP trap: Yes

Action:
Severity: Minor.
BUG7308
SNMP trap: Yes

Action:
Severity: Minor.
BUG7309
SNMP trap: Yes
Error processing symbols.

Action:
Severity: Minor.
BUG7310
SNMP trap: Yes

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 528 of 2360

BUG7311

Action:
Severity: Minor.
BUG7312
SNMP trap: Yes
Error adding symbol. Symbol table may be full.

Action:
Severity: Minor.
BUG7313
SNMP trap: Yes
Incorrect symbol file format. This function only loads symbol files produced by
option 81 programs.
Action:
Severity: Minor.
BUG7314
SNMP trap: Yes
Memory allocation error.

Action:
Severity: Minor.
BUG7330
SNMP trap: Yes
Kernal Init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7331
SNMP trap: Yes
I/O system Init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7332
SNMP trap: Yes
T startup spawn failed. Restarting with code x.

Action:
Severity: Minor.
BUG7333
SNMP trap: Yes
T startup gave up. Restarting with code x.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 529 of 2360

BUG7334
T startup suspended. Restarting with code x.

Action:
Severity: Minor.
BUG7335
SNMP trap: Yes
T startup deadline missed. Restarting with code x.

Action:
Severity: Minor.
BUG7336
SNMP trap: Yes
IOP search failed. Restarting with code x.

Action:
Severity: Minor.
BUG7337
SNMP trap: Yes
File system Init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7338
SNMP trap: Yes
SCSI Init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7339
SNMP trap: Yes
CMDU mount failed. Restarting with code x.

Action:
Severity: Minor.
BUG7340
SNMP trap: Yes
"Diskos" load failed. Restarting with code x.

Action:
Severity: Minor.
BUG7341
SNMP trap: Yes
"Diskos" run failed. Restarting with code x.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 530 of 2360

BUG7342
CLK connect failed. Restarting with code x.

Action:
Severity: Minor.
BUG7343
SNMP trap: Yes
CLK rate set failed. Restarting with code x.

Action:
Severity: Minor.
BUG7344
SNMP trap: Yes
EXC Init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7345
SNMP trap: Yes
EXC during attempt to reboot. Restarting with code x.

Action:
Severity: Minor.
BUG7346
SNMP trap: Yes
EXC recovery not functioning. Restarting with code x.

Action:
Severity: Minor.
BUG7347
SNMP trap: Yes
Exception. restarting with code x.

Action: Check CMDU power switch. Be sure the IP E Enable/Disable switch is
Enabled. Check both end d of the IOP SCSI cable and both CMDUs.
Severity: Minor.
BUG7360
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
LCD INIT failed.

Action:
Severity: Minor.
BUG7361
SIO driver create failed.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 531 of 2360

BUG7362
PIPE driver create failed.

Action:
Severity: Minor.
BUG7363
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Signal init failed.

Action:
Severity: Minor.
BUG7364
Standard IO Init failed.

Action:
Severity: Minor.
BUG7365
Console for log missing.

Action:
Severity: Minor.
BUG7366
Log Init failed.

Action:
Severity: Minor.
BUG7367
T startup deadline expires in 2 minutes.

Action:
Severity: Minor.
BUG7368
SNMP trap: Yes
T startup deadline expires in 1 minute.

Action:
Severity: Minor.
BUG7369
SNMP trap: Yes
T startup deadline expires in 30 seconds.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 532 of 2360

BUG7370

Action:
Severity: Minor.
BUG7371
SNMP trap: Yes
LCD failed to create lcddrv.

Action:
Severity: Minor.
BUG7372
SNMP trap: Yes
SNMP trap: Yes
LCD failed to open /lcd.

Action:
Severity: Minor.
BUG7373
CP SIO bad channel number.

Action:
Severity: Minor.
BUG7374
SNMP trap: Yes
CP SIO failed to create /sio/0.

Action:
Severity: Minor.
BUG7375
SNMP trap: Yes
CP SIO failed to create /sio/1.

Action:
Severity: Minor.
BUG7376
SNMP trap: Yes
CP SIO failed to open /sio/0.

Action:
Severity: Minor.
BUG7377
SNMP trap: Yes
CP SIO failed to open /sio/1.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 533 of 2360

BUG7378
CP SIO hardware init failed for both ports.

Action:
Severity: Minor.
BUG7379
SNMP trap: Yes
Failed to find the IOP that passed the self test.

Action: Be sure the IOP enable/disable switch is up. Reseat or replace the
security cartridge on the IOP/IODU.
Severity: Critical.
BUG7380
SNMP trap: Yes
Failed to find the IOP that passed the self test. Switchover and restart will be
attempted.
Action: Reseat or replace the IOP.
Severity: Minor.
BUG7381
SNMP trap: Yes
Failed to find IOP on both sides.

Action: Reseat or replace both IOPs. Be sure the enable/disable switched are
up.
Severity: Minor.
BUG7382
SNMP trap: Yes
Invalid state in switchover induced IOP search.

Action:
Severity: Minor.
BUG7383
SNMP trap: Yes
Reboot server init failed.

Action:
Severity: Minor.
BUG7384
SNMP trap: Yes
"Diskos" lookup index not valid.

Action:
Severity: Minor.
BUG7385
SNMP trap: Yes
"Diskos" file too small.

Action: Remove or reinstall the "diskos" from or to this directory.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 534 of 2360

BUG7386
"Diskos" file has wrong internal format.

Severity: Minor.
BUG7387
SNMP trap: Yes
"Diskos" file has wrong load address.

Severity: Minor.
BUG7388
SNMP trap: Yes
"Diskos" file truncated.

Severity: Minor.
BUG7389
SNMP trap: Yes
ROM OS x: "diskos" file truncated.

Severity: Minor.
BUG7400
SNMP trap: Yes
Protected data overlap. Cold start with code x.

Action: Increase T data parameter in "diskos" rule.
Severity: Minor.
BUG7401
SNMP trap: Yes
Warm start threshold exceeded. Cold start with code x.

Action:
Severity: Minor.
BUG7402
SNMP trap: Yes
Kernal init failed. Cold start with code x.

Action:
Severity: Minor.
BUG7410
SNMP trap: Yes
Segment init failed. Restarting with code x.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 535 of 2360

BUG7411
OS segment init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7412
SNMP trap: Yes
I/O system init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7413
SNMP trap: Yes
SWD system init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7414
SNMP trap: Yes
T startup spawn failed. Restarting with code x.

Action:
Severity: Minor.
BUG7415
SNMP trap: Yes
T startup suspended. Restarting with code x.

Action:
Severity: Minor.
BUG7416
SNMP trap: Yes
T startup deadline missed. Restarting with code x.

Action:
Severity: Minor.
BUG7417
SNMP trap: Yes
IOP search failed. Restarting with code x.

Action:
Severity: Minor.
BUG7418
SNMP trap: Yes
File system init failed. Restarting with code x.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 536 of 2360

BUG7419
SCSI init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7420
SNMP trap: Yes
CMDU mount failed. Restarting with code x.

Action:
Severity: Minor.
BUG7421
SNMP trap: Yes
Security cartridge driver failed. Restarting with code x.

Action: Restarting with code x. Reseat or replace security cartridge on
IOP/IODC.
Severity: Info.
BUG7422
SNMP trap: Yes
Security cartridge device failed.

Action:
Severity: Info.
BUG7423
SNMP trap: Yes
Security cartridge check failed.

Action:
Severity: Minor.
BUG7425
SNMP trap: Yes
CLK connect failed. Restarting with code x.

Action:
Severity: Minor.
BUG7426
SNMP trap: Yes
CLK rate set failed. Restarting with code x.

Action:
Severity: Minor.
BUG7427
SNMP trap: Yes
EXC init failed. Restarting with code x.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 537 of 2360

BUG7428
RST init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7429
SNMP trap: Yes
Exception in EXC recovery. Restarting with code x.

Action:
Severity: Minor.
BUG7430
SNMP trap: Yes
EXC during attempt to restart. Restarting with code x.

Action:
Severity: Minor.
BUG7431
SNMP trap: Yes
EXC recovery not functioning. Restarting with code x.

Action:
Severity: Minor.
BUG7432
SNMP trap: Yes
Exception. Restarting with code x.

Action: Be sure CMDU power is on. Check that IOP enable/disable switch is up.
Check both connectors of the IOP SCSI cable and both CMDUs.
Severity: Minor.
BUG7433
SNMP trap: Yes
TOD init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7434
SNMP trap: Yes
TOD midnight init failed. Restarting with code x.

Action:
Severity: Minor.
BUG7440
SNMP trap: Yes
SNMP trap: Yes
LCD init failed.

Action:
Severity: Minor.
System Messages
Page 538 of 2360

BUG7441
SIO driver create failed.

Action:
Severity: Minor.
BUG7442
SNMP trap: Yes
PIPE driver create failed.

Action:
Severity: Minor.
BUG7443
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Signal init failed.

Action:
Severity: Minor.
BUG7444
Standard I/O init failed.

Action:
Severity: Minor.
BUG7445
Log console missing.

Action:
Severity: Minor.
BUG7446
Log Init failed.

Action:
Severity: Minor.
BUG7447
Debug init failed.

Action:
Severity: Minor.
BUG7448
Symbol init failed.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 539 of 2360

BUG7449
Switchover init failed.

Action:
Severity: Minor.
BUG7450
SNMP trap: Yes
T startup suspended - restart in 10 seconds.

Action:
Severity: Minor.
BUG7451
SNMP trap: Yes
T startup suspended - restart in 5 seconds.

Action:
Severity: Minor.
BUG7452
SNMP trap: Yes
T startup deadline expires in 2 minutes.

Action:
Severity: Minor.
BUG7453
SNMP trap: Yes
T startup deadline expires in 1 minute.

Action:
Severity: Minor.
BUG7454
SNMP trap: Yes

Action:
Severity: Minor.
BUG7455
SNMP trap: Yes

Action:
Severity: Minor.
BUG7456
SNMP trap: Yes
Raw file system init failed.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 540 of 2360

BUG7457
FD raw volume init failed.

Action:
Severity: Minor.
BUG7458
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Install load failed.

Action:
Severity: Minor.
BUG7459
PTY table create failed.

Action:
Severity: Minor.
BUG7460
RPT init failed.

Action:
Severity: Minor.
BUG7461
Symbol load failed.

Action:
Severity: Minor.
BUG7462
Patch init failed.

Action:
Severity: Minor.
BUG7463
OSM init failed.

Action:
Severity: Minor.
BUG7464
Failed to find the IOP that passed the self test.

Action: Be sure the IOP enable/disable switch is up. Reseat ro replace the
security cartridge on the IOP.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 541 of 2360

BUG7465
Failed to find the IOP that passed the self test. Attempting switchover.
Severity: Minor.
BUG7466
SNMP trap: Yes
Failed to find any IOP. Attempting switchover.

Severity: Minor.
BUG7467
SNMP trap: Yes
Graceful switchover during IOP search was rejected.

Action:
Severity: Minor.
BUG7468
SNMP trap: Yes
Failed to find any IOP on this side. Switchover was rejected.

Severity: Minor.
BUG7469
SNMP trap: Yes
Failed to find IOP on both sides.

Severity: Minor.
BUG7471
SNMP trap: Yes
LCD device create failed.

Action:
Severity: Minor.
BUG7472
SNMP trap: Yes
SNMP trap: Yes
LCD device open failed.

Action:
Severity: Minor.
System Messages
Page 542 of 2360

BUG7473
CP SIO bad channel number.

Action:
Severity: Minor.
BUG7474
SNMP trap: Yes
CP SIO failed to create "/sio/0."

Action:
Severity: Minor.
BUG7475
SNMP trap: Yes
CP SIO failed to create "/sio/1."

Action:
Severity: Minor.
BUG7476
SNMP trap: Yes
CP SIO failed to open "/sio/0."

Action:
Severity: Minor.
BUG7477
SNMP trap: Yes
CP SIO failed to open "/sio/1."

Action:
Severity: Minor.
BUG7478
SNMP trap: Yes
OS x: CP SIO h/w init failed for all ports.

Action:
Severity: Minor.
BUG7481
SNMP trap: Yes
Reboot server init failed.

Action:
Severity: Minor.
BUG7482
SNMP trap: Yes
OS x failed to open y.
Action: Reinstall "diskos.sym."
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 543 of 2360

BUG7483
OS x y file too small.

Severity: Minor.
BUG7484
SNMP trap: Yes
OS x y has wrong internal format.

Severity: Minor.
BUG7485
SNMP trap: Yes
OS x failed to load y.
Severity: Minor.
BUG7486
SNMP trap: Yes
OS x y may not match "diskos" loaded from z.

Action: Check floppies in floppy drives.
Severity: Minor.
BUG7487
SNMP trap: Yes
OS x y does not match "diskos" loaded from z.

Severity: Minor.
BUG7488
SNMP trap: Yes
SEC Cartridge check failed.

Action: Check SEC Cartridge/Dongle. Proceeding without file system.
Severity: Critical.
BUG7489
SNMP trap: Yes
Attempt to select IOP/CMDU failed. File System may not be accessible.

Action: Check IOP/CMDU. Use MAN INIT when ready.
Severity: Minor.
BUG7490
SNMP trap: Yes
Failed to open a. reinstall 'diskos.sym'.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 544 of 2360

BUG7491
A file has wrong internal format. reinstall 'diskos.sym'.

Action:
Severity: Minor.
BUG7492
SNMP trap: Yes
A file has wrong internal format. reinstall 'diskos.sym'.

Action:
Severity: Minor.
BUG7493
SNMP trap: Yes
Failed to load a. reinstall 'diskos.sym'.

Action:
Severity: Minor.
BUG7494
SNMP trap: Yes
A may not match "diskos" loaded from b.

Severity: Minor.
BUG7495
SNMP trap: Yes
A does not match "diskos" loaded from b.

Severity: Minor.
BUG7496
SNMP trap: Yes
Failed to find the IOP.

Action: Reseat or replace IOP. Check that IOP enable/disable switch is enabled
(up).
Severity: Minor.
BUG7497
SNMP trap: Yes
Network interface initialization failed during the system startup because there
has been a failure to correctly obtain network interface data or a failure to
initialize the network interface.
Action: Check Network interface address and network database file.
Severity: Major.
BUG7500
SNMP trap: No
SIO failed to create siodrv.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 545 of 2360

BUG7501
SIO failed to hardware init siodrv.

Action:
Severity: Minor.
BUG7502
SNMP trap: No
SIO bad channel number x.

Action:
Severity: Minor.
BUG7503
SNMP trap: No
SIO bad address of SIO DEV x.

Action:
Severity: Minor.
BUG7504
SNMP trap: No
SNMP trap: No
SIO installing siodrv.

Action:
Severity: Minor.
BUG7505
SIO x on IOS list but not marked created.

Action:
Severity: Minor.
BUG7506
SNMP trap: No
SIO x marked created but not on IOS list.

Action:
Severity: Minor.
BUG7507
SNMP trap: No
SNMP trap: No
SNMP trap: No
SIO x failed tydevinit.

Action:
Severity: Minor.
BUG7508
SIO x failed iosdevadd.

Action:
Severity: Minor.
System Messages
Page 546 of 2360

BUG7509
SIO x is not marked created.

Action:
Severity: Minor.
BUG7510
SNMP trap: No
SIO x hardware init on side y failed.

Action:
Severity: Minor.
BUG7511
SNMP trap: No
SIO x attribute load on CP side y failed.

Action:
Severity: Minor.
BUG7512
SNMP trap: No
SIO x is not marked initialized.

Action:
Severity: Minor.
BUG7540
SNMP trap: No
Failed to install TOD ISR.

Action:
Severity: Minor.
BUG7541
SNMP trap: No
Time and data parameters are out-of-range.

Action:
Severity: Minor.
BUG7542
SNMP trap: No
Failed to create tod24 sems.

Action:
Severity: Minor.
BUG7543
SNMP trap: No
Failed to spawn tod24 task.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 547 of 2360

BUG7544
Corrupted entry x in midnight list.

Action:
Severity: Minor.
BUG7545
SNMP trap: No
Stuck in update mode. Cannot access Time and date data.

Action:
Severity: Minor.
BUG7546
SNMP trap: No
TOD 24 invalid job name.

Action:
Severity: Minor.
BUG7547
SNMP trap: No
SNMP trap: No
TOD 24 malloc.
Action:
Severity: Minor.
BUG7548
TOD 24 x bad entries in the TOD 24 list. Use TOD24Show from PDT.
Action:
Severity: Minor.
BUG7560
SNMP trap: No
SIMM out-of-range on side x.

Action:
Severity: Minor.
BUG7561
SNMP trap: No
SIMM out-of-range in slot x.

Action:
Severity: Minor.
BUG7562
SNMP trap: No
SIMM out-of-range array size x.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 548 of 2360

BUG7563
SIMM out-of-range SIMM type: b.

Action:
Severity: Minor.
BUG8021
SNMP trap: No
The is an operating system error message wrapper. If the TCP/IP

communication results in a system error during the send/receive socket
operations, the BUG08021 will be printed. There is a lot of scenarios on how
can this BUG happen: for example, not enough operating system resources to
handle the request, TCP/IP physical error occurred, packet data loss during
the transmitting, etc.
Action: 1. Check if the TCP/IP communication between the cabinets is in good
condition. This BUG can happen if CAT5 Ethernet cables are not secured in the
jacks properly. 2. Check if the Ethernet bandwidth usage is not critical. In case if
the Ethernet load exceeds 90% of the total bandwidth (10 or 100Mbit), the TCP/IP
communication between the cabinets of SIPE system can result in such a BUG
message. 3. If the problem will occurs on a regular basis, the report log entry and
stack trace is required from a site for further investigation.
Severity: Minor.
BUG8037
SNMP trap: No
Warning, incorrect value in TRANSIT_PABX. Call Processing not affected.

Action: Contact your Nortel Networks distributor.
Severity: Info.
BUG8137
SNMP trap: Yes
VNS, UVNS_DNPTR is corrupt.

Action: Contact your Nortel Networks distributor.
Severity: Info.
BUG8927
SNMP trap: No
SNMP trap: Yes
TNTRANS failed.
Action:
Severity: Minor.
BUG8928
Tone CR cannot be retrieved.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 549 of 2360

BUG8930 xxxx
GPT Integrated Digital Access. The format of the message is:

Where xxxx is one of the following codes: 2009 Invalid DTSL/DDSL timeout
2010 DTSL/DDSL pointers are already set up 2011 Invalid source in
DASS_MAINTENANCE 2012 DASS_MAINTENANCE - invalid timeout 2013
DASS_MAINTENANCE - channel configuration is not DPNSS 2014
DASS_MAINTENANCE - DTSL not in polling table 2015
DASS_MAINTENANCE - FORCEDISCONNECT failed 2016
DASS_MAINTENANCE - ENABLE-STN failed 2100 DASS_DPNSS_CALL - a
DPNSS1 input with an unrecognized message group has been received 2101
DASS_DPNSS_CALL - an undefined call control has been received 2102
DASS_DPNSS_CALL - an RM has been received in an invalid state
103 DASS_DPNSS_CALL - an unsupported message has been received
2104 DASS_DPNSS_CALL - an ISRM has been received in an invalid state
2105 DASS_DPNSS_CALL - a CCM has been received in an invalid state
2106 DASS_DPNSS_CALL - a NIM has been received in an invalid state
2107 DASS_DPNSS_CALL - a CRM has been received in an invalid state
2108 DASS_DPNSS_CALL - a NAM has been received in an invalid state
2109 DASS_DPNSS_CALL - a SSRM has been received in an invalid state
2110 DASS_DPNSS_CALL - a RRM has been received in an invalid state
2111 DASS_DPNSS_CALL - an undefined EEM has been received
2112 DASS_DPNSS_CALL - an EEM has been received in an invalid state
2113 DASS_DPNSS_CALL - a SCRM message has been received. This
message is invalid.
2114 DASS_DPNSS_CALL - a SCIM message has been received. This
message is invalid.
2115 DASS_DPNSS_CALL - an undefined LLM message has been received
2116 DASS_DPNSS_CALL - an LLM has been received in an invalid
tat 2117 DASS_DPNSS_CALL - an LLRM message has been received. This
message is invalid 2119 DASS_DPNSS_CALL - a timer has expired in an
invalid state
2120 DASS_DPNSS_CALL - a digits have been received from a set in an
invalid state
2121 DASS_DPNSS_CALL - an extension has answered in an invalid state
2123 DASS_DPNSS_CALL - an invalid input has been received in an invalid
state
2126 DASS_DPNSS_CALL - the EOD timer has expired in an invalid state
2127 DASS_DPNSS_CALL - an attempt has been made to set up both transit
channels on a non-transit connection and has failed 2129
DASS_DPNSS_CALL - CRPTR is NIL 2131 DASS_DPNSS_CALL - a
procedure has been called with an invalid source parameter
2133 DASS_DPNSS_CALL - an attempt to start an invalid timer has occurred
2134 DASS_DPNSS_CALL - a unable to set up route data pointers
2135 DASS_DPNSS_CALL - an attempt to set up an invalid CLC
System Messages
Page 550 of 2360

2137 DASS_DPNSS_CALL - invalid TNTRANS2145 DASS_DPNSS_CALL extension has been cleared during the extension clear down sequence 2147
A global procedure has been called that is not valid for a DPNSS call
2149 DASS_IO - a TNTRANS has failed in EMPTY_LLM_QUEUE
2151 A channel state is out-of-range 2152 A supplementary information string
is out-of-range 2153 An unidentified CLC string has been received. 2154
DASS_IO_DPNSS_CALL -- CRPTR is out-of-range 2155 Invalid number of
parameters in CLC2156 DASS_OUTPUT - invalid SOURCE_DATA
parameter 2158 DASS_TO_TNTRANS has failed 2159 DASS_IO_ -NO
messages to be queued 2160 DASS_IO - Message queue is full, queue has
been cleared of all messages that contain the same group and type code as
the clearout message. 2162 DASS_IO - Request to collect invalid messages
has been received messages must be EEM(I) or LLM(I) 2163 DASS_IO Character cannot be stored in queue because the queue size is zero 2164
CHK_INFO_STRINGS all to store message that is not an ISRM(I) or ISRM(C)
2165 FORMAT_DASS_MSG Invalid SOURCE parameter
2166 FORMAT_DASS_MSG ITEMPTR parameter is NIL
2167 FORMAT_DASS_MSG Supplementary information string is out of range
2168 FORMAT_DASS_MSG ITEMPTR parameter is NIL
2169 FORMAT_DASS_MSG Message size exceeds 45 bytes
2171 DASS_INUT A message has been received that is not valid for DASS2
2323 NEXT_CHARACTER An incomplete ICI/SCI has been encountered at
the end of the linked list of Call Registers
2330 DASS_DPNSS_CALL DDC called to handle a DASS2 message in an
invalid state
2331 DASS_DPNSS_CALL DDC called to handle a DASS2 message on a
channel configured as DPNSS1
2332 DASS_DPNSS_CALL Unable to set up route pointers for a DASS2
channel
2333 DASS_DPNSS_CALL REPEAT_MSG or REPEAT_ISRM called with a
DASS2 channel involved
2334 DASS_DPNSS_CALL DDC called to send a NIM on a DASS2 channel
2335 DASS_DPNSS_CALL DDC called to send an EEM on a DASS2 channel
2336 DASS_DPNSS_CALL DDC called to send an LLRM on a
DASS2channel
2337 CONFIG_ALL DTS/DDSL type is specified as being something other
than a PRIVATE or PUBLIC link
2338 SET_CHAN_FLAGS A lap with a number greater than 31 has been
started by level 3 on a PUBLIC network link
2339 SCCM_MI2_WRITE A set channel configuration message with a lap
number greater than 31 has been sent from level 3 to level 2 on a PUBLIC
network link
2340 CHAN_STARTUP A channel status change message with a lap number
553-3001-411
Standard 15.00
January 2006
Page 551 of 2360

of greater than 31 has been sent from level 2 to level 3 on a PUBLIC network
link
2341 SET_UP_CONFIG A set channel configuration message containing
DASS2 signaling channels has been sent from level 3 to level 2 on a PRIVATE
network link
2342 VALID_CHAN A lap number of greater than 31 is being started on a
PUBLIC network link
2343 CONFIG_ALL_PUB A virtual channel has been configured on a PUBLIC
network link
2456 DT_DASS_INPUT A message has been received on a DPNSS/DASS
link that is not configured for DA signaling
2521 Empty SSRM message has been sent on a none specified MERCURY
route
8000 Not a DASS2 DTSL/DDSL
8030 Invalid MAINPM returned by DIGPROC
8031 TNTRANS on ORIGTN failed
8032 Invalid TERTYPE
8033 TNTRANS on TERTN failed
8034 Invalid call without TERTYPE
8035 Conference with less than 3 parties
8036 Unable to ring member of group DN
8040 Route pointers could not be set up
8050 Invalid procedure call called with IDA TN
Action:
Severity: Minor.
BUG8937
SNMP trap: Yes
Invalid AUX_PM state. Procedure ICP_DNS_ACTION.

Action:
Severity: Minor.
BUG8938
SNMP trap: Yes
Case out-of-range in ICP task number n.

Action:
Severity: Minor.
BUG8939
SNMP trap: Yes
ICP_TASK out-of-range in global pd.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 552 of 2360

BUG8940
Invalid outgoing message for ICP. Message doesn't start with ASCII character
STX. FIrst_Char, Link Number. Procedure ICP_TRANSMIT.
Action:
Severity: Minor.
BUG8941
SNMP trap: Yes
Invalid input source to LD 51 (ICU). SOURCE. Procedure MAINY_ICU.

Action:
Severity: Minor.
BUG8942
SNMP trap: Yes
A call is made to a procedure which is used by APL and not by ICP. Output:
apl_source, invalid_type, invalid data, link_number. procedures handle_ack,
handle_nak invalid type = 3
invalid_data = 0 - send ACK0/NACK0 signal
invalid_data = 1 - send ACK1/NACK1 signal
invalid_data = 2 - send NAK procedure handle_128ms_to invalid type = 1
invalid_data = output link_status
Procedure read_and_send invalid type = 8 invalid_data = 1 - transmitted
invalid_data = 2 - retransmit link_status = 0 - down link_status = 1 - idle
link_status = 2 - APL transmit
link_status = 3 - wait ACK link_status = 4 - APL retransmit
link_status = 5 - ICP transmitpl_source = 0 - output timer has expired
apl_source = 1 - input timer has expired
apl_source = 3 - link audit
apl_source = 4 - link status pl_source = 5 - update link timerspl_source = 6 link message to output queue apl_source = 7 - remove message from output
queue apl_source = 8 - disable transmit function
apl_source = 9 - link process ID
apl_source = A - allocate Call Registers apl_source = B - send message to
application apl_source = C - send message to link
apl_source = D - receive one character
apl_source = E - enable ICP link
Action:
Severity: Minor.
BUG8943
SNMP trap: Yes
There is no Call Register available. Procedure icp_asm_packet (receive)

output: qu_aplip = 0017, link number. Procedure icp_send_msg (transmit)
output: ic_msg_type.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 553 of 2360

BUG8944
APL output queue overflow. Procedure link_apl_oq output queue_length, link

number.
Action:
Severity: Minor.
BUG8945
SNMP trap: Yes
ICP link number out of rang (0-15). Procedure icp_resources_ok output:

ic_link_no.
Action:
Severity: Minor.
BUG8946
SNMP trap: Yes
Message type out-of-range. Procedures icp_send_msg, icp_resources_ok

and icp_msg_build output: ic_msg_type.
Action:
Severity: Minor.
BUG8947
SNMP trap: Yes
APL input queue full. Procedure icp_asm_packet output: queue length.

BUG8948
Action:
Severity: Minor.
BUG8948
SNMP trap: Yes
Message too long. Procedures icp_msg_to_buf, icp_rec_input,

icp_asm_packet output: link number.
Action:
Severity: Minor.
BUG8949
SNMP trap: Yes
Invalid Intercept recipient.

Action:
Severity: Minor.
BUG8950
SNMP trap: Yes
Attempt to light change status on invalid fixed lamp.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 554 of 2360

BUG8951
Unit type other than Attn has called Console_Display.

Action:
Severity: Minor.
BUG8952
SNMP trap: Yes
Invalid Attn lamp number passed to pd AttnLamp.

Action:
Severity: Minor.
BUG8953
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Setcustptrs failed.
Action:
Severity: Minor.
BUG8954
Setattnprts failed.
Action:
Severity: Minor.
BUG8955
Invalid input from DCON (pd Handle_B5).

Action:
Severity: Minor.
BUG8956
SNMP trap: Yes

Action:
Severity: Minor.
BUG8957
SNMP trap: Yes

Action:
Severity: Minor.
BUG8958
SNMP trap: Yes

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 555 of 2360

BUG8959

Action:
Severity: Minor.
BUG8960
SNMP trap: Yes
Invalid input from DCON (pd Handle_CMD_A).

Action:
Severity: Minor.
BUG8961
SNMP trap: Yes
SPCE is activated when FFC is restricted.

Action:
Severity: Minor.
BUG8962
SNMP trap: Yes
FFC Handler was called with an invalid FFC type.

Action:
Severity: Minor.
BUG8963
SNMP trap: Yes
Electronic Lock (ELK) password length is out-of-range. Your data may be

corrupted.
Action:
Severity: Minor.
BUG8964
SNMP trap: Yes
You have entered an invalid DN type for the ELK feature, at this point.
Action:
Severity: Minor.
BUG8965
SNMP trap: Yes
The password stored is invalid (wrong length).

Action:
Severity: Minor.
BUG8967
SNMP trap: Yes
Wrong Trunk type in Periodic_Clear.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 556 of 2360

BUG8968
Wrong TN in Periodic_Clear.
Action:
Severity: Minor.
BUG8969
SNMP trap: Yes
Invalid case to Periodic_Clear.

Action:
Severity: Minor.
BUG8970
SNMP trap: Yes
A Buffered PPM with a read request still pending is being idled. The DN will
not be charged. Trunk TN, Trunk PPM, PPM_BITS and PPM_CALLED_BITS
are printed. Procedure IDLETRUNKS.
Action:
Severity: Minor.
BUG8971
SNMP trap: Yes
Attempt to write a protected bit field for the specified bit offset and bit width do
not fit within one 16 bit word. - Pd. WRITEPBITS.
Action:
Severity: Minor.
BUG8972
SNMP trap: Yes
Procedure IDLECR: The CR being IDLED still has CDR CRs Attached. PPM
module is called to print these CDR Call Register(s). For each CDR CR, the
return address stack is printed in the second line, and the CDR record number
is printed. Received pulses maybe charged to the wrong meter.
Action:
Severity: Minor.
BUG8973
SNMP trap: Yes
When the PPM trunk is involved, interpositional call is not allowed. The other
attendant CR of loop key is ignored. Procedure FIND_CHGEE_CONF
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 557 of 2360

BUG8974
Procedure PPM_XFERCDR: either CRPTR or PPM_CRPTR is found to be nil.

When attempting to transfer the CDR Call Register from one CR to another,
one of the CRs was found to be nil.
Action:
Severity: Minor.
BUG8975
SNMP trap: Yes
SNMP trap: Yes
PLMRPTR is nil.
Action:
Severity: Minor.
BUG8987
You must have the SPRE feature defined to use FFC.

Action:
Severity: Minor.
BUG8988
SNMP trap: No
DTI2_CALL_TYPE with .COS_NAP should not be making outgoing calls.

Action:
Severity: Minor.
BUG8990
SNMP trap: Yes
Invalid software DTI2 trunk state detected.

Action:
Severity: Minor.
BUG8991
SNMP trap: Yes
Invalid DTI2 signal type requested by software.

Action:
Severity: Minor.
BUG8992
SNMP trap: Yes
SNMP trap: Yes
DTI2 invalid TN.

Action:
Severity: Minor.
BUG8993
TBAR - route pointers could not be set.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 558 of 2360

BUG8994
TBAR - desired ART pointer is NIL.

Action:
Severity: Minor.
BUG8995
SNMP trap: Yes
DTI2_HANDLER source out-of-range.

Action:
Severity: Minor.
BUG8996 g loop
SNMP trap: Yes
DTI2 - CH_TN convert failed. g = group.

Action:
Severity: Minor.
BUG8998
SNMP trap: Yes
DTI2_HANDLER CONVRT_TIME_UNIT. Time unit out-of-range.

Action:
Severity: Minor.
BUG8999
SNMP trap: Yes
DTI2 - Analog procedure called for Digital Trunks. Outputs TN and Global
Number
Action:
Severity: Minor.
BUG9000
SNMP trap: Yes
Global procedure PTU, returned invalid value. Module: MFC. Procedure:

ACTV_UPF_CNI_PTU.
Severity: Minor.
BUG9001
SNMP trap: Yes
Procedure called with an invalid source. Module: MFC. Procedure: PTU.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 559 of 2360

BUG9002
Different values returned when procedure called twice in the same timeslice
with the same parameters (for early check traffic pegging purposes). Module:
NARS. Procedure: NARS_FIND_ROUTE.
Severity: Minor.
BUG9003
SNMP trap: Yes
The parameters sent are incorrect; either the unprotected route pointer is NIL,
or the value assigned to the TRK_BUSY_BIT is incorrect (must be zero or
one). Note: The parameters are printed in the BUG message. Module: TRK.
Procedure: UPD_TRK_BUSY_BIT.
Severity: Minor.
BUG9004
SNMP trap: Yes
An attempt was made to increment or decrement the idle trunk counter beyond
its allowable range (0 - 254). Procedure: UPD_TRK_BUSY_BIT.
Severity: Minor.
BUG9005
SNMP trap: Yes
Procedure is called during a PTU early check. Procedure: DIGPROC.

Severity: Major.
BUG9006
SNMP trap: Yes
Task spawn failed.

Action: If problem persists, initialize the switch. If the problem continues, contact
your technical support group.
Severity: Major.
BUG9007
SNMP trap: No
A CDR call register has timed out after 5 minutes while waiting for PPM
information from the trunk. That call register is idled.
Severity: Major.
SNMP trap: Yes
BUG9013 {list type} {cust} {list} Corruptions in MANP or DGCR list or CLIP list.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 560 of 2360

BUG9017
MMIH: Failure to create message buffer. The MMIH interface driver will not be
available for MSDL/MISP cards.
Action: Warmstart the system to recover.
Severity: Critical.
BUG9018
SNMP trap: Yes
An mCIDR return error component (see Appendix C) has been returned with
the indication 'invalidCallState'. This means that the network has received the
mCIDRequest invoke component from the called party in a state other than the
Active state (N10) or the Disconnect indication state (N12).
Action: If this is a frequent message, report the problem to your technical
support group.
Severity: Info.
BUG9019
SNMP trap: Yes
A mCIDRequest return error component (see Appendix C) has been returned

with the indication 'notIncomingCall'. This is considered a bug: mCIDRequest
is not to be sent for outgoing calls.
Action: If this message appears frequently, report the problem to your technical
support group.
Severity: Info.
BUG9020
SNMP trap: Yes
A mCIDRequest return error component (see Appendix C) has been returned

with the indication 'supplementaryServiceInteractionNotAllowed". This means
that the MCID supplementary service is invoked when another supplementary
service is already activated or has already been invoked. The Network does
not allow this MCID supplementary service invocation in combination with the
other supplementary service.
Action: Report the problem to your technical support group.
Severity: Minor.
BUG9023
SNMP trap: Yes
Path replacement: problem when switching from the old to the new
connection.
Severity: Critical.
BUG9024
SNMP trap: Yes
Path replacement protocol failure.

Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 561 of 2360

BUG9025
Path replacement: problem with the GF.

Severity: Minor.
BUG9026
SNMP trap: Yes
Path replacement: Invalid pointer.

Severity: Minor.
BUG9027
SNMP trap: Yes
Path replacement encoding/decoding problem.

Severity: Minor.
BUG9080
SNMP trap: Yes
Call Register idled still in broadcast trunk list.

Action: Contact your technical support group if the condition persists.
Severity: Minor.
BUG9081
SNMP trap: Yes
ORIGTN = 0 in a call waiting for RAN.

Action: Contact your technical support group if the condition persists.
Severity: Minor.
BUG9083
SNMP trap: Yes
Data in the TITH Call Register and the RAN Route data block does not match.
Action: Contact your technical support group if the problem persists.
Severity: Minor.
BUG9084
SNMP trap: Yes
It is not valid to send a Discard Buffer Message for APNSS configurations.

Action: Please check the configuration for D-Channel number n.
Severity: Minor.
BUG9085
SNMP trap: Yes
The Layer 2 Reset Option (prompt L2_RST) does not apply for this type of
pcakc.
Action: Please check the configuration for D-channel number n.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 562 of 2360

BUG9086
The number of DNIS digits in the passed variable is zero.

Action:
Severity: Minor.
BUG9087
SNMP trap: Yes
Call register pointer (CRPTR) passed to procedure BRDCST_UTILITY is out

of range.
Severity: Minor.
BUG9088
SNMP trap: No
Music Broadcast trunk list is broken.

Severity: Minor.
BUG9089
SNMP trap: No
The number of RAN connections available in the system is equal to less than
0.
Action: Reduce the number of RAN connections until the problem disappears.
Contact your technical support group if the problem persists.
Severity: Minor.
BUG9090
SNMP trap: Yes
The number of RAN Broadcast in route available in the system is equal to less
than 0.
Action: Remove the number of RAN connections until the problem disappears.
Contact your technical support group if the problem persists.
Severity: Minor.
BUG9091
SNMP trap: Yes
RAN waiting calls list is broken.

Severity: Minor.
BUG9092
SNMP trap: Yes
RAN trunk list is broken.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 563 of 2360

BUG9093 LISPTY_TN BRDCST_TN LISPTY_GROUP LISPTY-JUNC Invalid junctor value in
procedure BRDCST_GET_J when looking for a junctor for a RAN or Music
Broadcast call. Parameters: LISPTY_TN, BRDCST_TN, LISPTY_GROUP,
LISPTY_JUNC
Severity: Minor.
SNMP trap: Yes
BUG9094 BRDPTY_TN, LISPTY_TN, TALKSLOT_WORD, TALKJUNC_WORD Attempt to

write to NTWK memories with bad timeslot data (zero) avoided for a RAN of
Music Broadcast call in procedure BRDCST_SETSPEECH.
Parameters: BRDPTY_TN, LISPTY-TN, TALKSLOT_WORD,
TALKJUNC_WORD
Severity: Minor.
SNMP trap: Yes
BUG9095 GLOOP U_G_LOOP:PTRY Network Loop pointer corruption in

BRDCST_SETSPEECH.
Parameters: GLOOPX, U_G_LOOP: PTRY
Severity: Minor.
SNMP trap: Yes
BUG9096 TN S CHZ Terminal TN, attempted to idle the slot S used by channel CHZ on the same
loop.
Action:
Severity: Major.
SNMP trap: No
BUG9097 CH LP S RESERV_COUNT of channel CH loop LP reached maximum value while

re-using timeslot S.
Action:
Severity: Critical.
BUG9098
SNMP trap: No
BUG9098 %s Software error. %s is a short text description of the error..

Severity: Minor.
SNMP trap: No
System Messages
Page 564 of 2360

BUG9120
GDLS_CALLPROC, GDLSHTPTR is undefined. Serious software fault which

will affect system performance.
Severity: Major.
BUG9121
SNMP trap: No
GDLS_CALLPROC called with improper SOURCE value.

Severity: Major.
BUG9122
SNMP trap: No
CRPTR is NIL on entry to transmission algorithm. SOURCE is displayed. No

effect on system performance.
Action:
Severity: Minor.
BUG9123
SNMP trap: No
No port type could be assigned to the TN which was invalid in previous ERR
1 message.
Severity: Major.
BUG9124
SNMP trap: No
IDLE pads could not be sent. Invalid IDLEFLAG value.

Severity: Major.
BUG9125
SNMP trap: No
PADS column is outside specified range (0-1). The TN and the PADS values
are printed.
Action: Check the loss plan for out of range values. Contact your technical
support group.
Severity: Minor.
BUG9126
SNMP trap: No
RPAD or TPAD column is outside specified range. The TN RPAD and TPAD
are printed.
Action: Check the loss plan for out of range values. Contact your technical
support group.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 565 of 2360

BUG9127
An invalid message type was received for a TN specified to receive PAD

messaging. The TN and Message type are printed.
Action: Check card.db file used for mapping against published values in NTP
and modify through your technical support group.
Severity: Minor.
BUG9128
SNMP trap: No
An empty (NULL) value was specified in the loss plan and could not be sent.
Severity:
BUG9129
SNMP trap: No
An invalid message type was received for a TN specified to receive flexible

level messages. The TN and message type are printed.
Severity: Minor.
BUG9130
SNMP trap: No
An invalid message type was encountered when trying to retrieve the encoded
message for a specified Receive or Transmit dB value. The message type is
printed.
Action: Contact your technical support group if the
Severity: Minor.
BUG9131
SNMP trap: No
A value smaller than -12dB RX was passed to be encoded but GDLS encoding
tables start at this value. A value of -12dB was used instead.
Action: Check loss plan table for improvements.
Severity: Minor.
BUG9132
SNMP trap: No
A value greater than +14dB RX was passed to be encoded but GDLS

encoding tables finish at this value. A value of +14dB was used instead.
Action: Check the loss plan table for improvements
Severity: Minor.
BUG9133
SNMP trap: No
A value smaller than -12dB TX was passed to be encoded but GDLS encoding
tables start at this value. A value of -12dB was used instead.
Action: Check the loss plan table for improvements
Severity: Minor.
SNMP trap: No
System Messages
Page 566 of 2360

BUG9134
A value greater than +14dB TX was passed to be encoded but GDLS encoding
tables finish at this value. A value of +14dB was used instead.
Action: Check loss plan table for improvements. Note extreme values may be
beyond the capabilities of the hardware device.
Severity: Minor.
BUG9135
SNMP trap: No
The default port type for the TN passed was not allocated.
Severity: Minor.
BUG9136
SNMP trap: No
The PLOOPTR for the TN passed for default port type allocation was invalid.
Severity: Major.
BUG9137
SNMP trap: No
Bitoffset passed to the bifield algorithm GDLS_WRITEBITS was invalid.

Action:
Severity: Major.
BUG9138
SNMP trap: No
An invalid message type was encountered on transferring an updated loss

plan from overly 117 into the system. Transfer is cancelled. Can cause
memory leak.
Action:
Severity: Minor.
BUG9139
SNMP trap: No
An invalid state was found in transferring the system loss plan from overlay
117. Transfer is cancelled. Can cause minor memory leak.
Action:
Severity: Minor.
BUG9140
SNMP trap: No
Call register removed from the RAN waiting queue still in the RAN waiting call
register's list.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 567 of 2360

BUG9141
A call is connected after the RAN re-started . The beginning of the

announcement could be missed.
Action: Increase the delay between the two announcements on the RAN
machine (up to 2 seconds), or reduce the maximum number of RAN connections.
Severity: Minor.
BUG9149
SNMP trap: Yes
ACD DN was not found in agent's MQA data block whereas the TN of the
agent appears in the position list of the ACD DN. (Procedure
AUDIT_POSITIONS)
Action: Agent's TN is removed from the position list of the ACD DN. Loop
variable is adjusted so that the TN can be audited in the same place where MQA
agent's TN used to be. AGENT_ID is removed from ID_TBL if it exists, and from
P_POSITION PTR.
Severity: Major.
BUG9157
SNMP trap: Yes
A problem occurred during QSIG Diversion.

Action: Contact your technical support group and advise them of the parameters
output.
Severity: Critical.
BUG9159
SNMP trap: Yes
The broadcast speechpath was not set-up.

Severity: Minor.
BUG9160
SNMP trap: Yes
While idling a broadcast call the broadcast timeslot junctor was found to be
empty.
Severity: Minor.
BUG9161
SNMP trap: Yes
a b c d e f g h i j1 j2 j3 j4 j5 j6 j7 j8 - Procedure OUTPULSING. Digitunload is

greater than Digitload even though 32 or fewer digits have been dialed.
Where: a = Rtclock
b = Mainpm c = Auxpm d = Origtn
e = Tertn f = Origtype g = Tertype h = Digitload i = Digitunload j1 - j8 = the
dialed digits
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 568 of 2360

BUG9171
Out-of-range Call register pointer passed to procedure RO_FIND_CH_ITEM

(dnwk). RO_OTHER_ITEM is not set up.
Action:
Severity: Minor.
BUG9174
SNMP trap: Yes
The problem occurs when the VI use the GF functionalities.

Severity: Critical.
BUG9175
SNMP trap: No
Attempting to format an invalid or unsupported DPNSS NSI string. (Procedure

FORMAT_NSI. Module DIO)
Action:
Severity: Info.
BUG9176
SNMP trap: Yes
CRM received in invalid Supplementary Service State. (Procedure

MWIGW_CRM_INPUT. Module DSS).
Action:
Severity: Minor.
BUG9177
SNMP trap: Yes
Invalid GW_FUNCTION.
(Procedure MWIGW_SERVICE. Module IDAGW).
Action:
Severity: Minor.
BUG9178
SNMP trap: Yes
Could not send a Facility (Request) message.

Action: (Procedure RCVD_MWI_ISRM. Module IDAGW)
Severity: Minor.
BUG9179
SNMP trap: Yes
Could not send a Facility message (either a Facility (Acknowledge) or a

Facility (Reject). Procedure RCVD_MWI_CRM. Module IDAGW).
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 569 of 2360

BUG9180
Could not send an ISRM containing a Message Waiting NSI string. (Procedure
RCVD_MWI_FAC_REQ. Module IDAGW)
Action:
Severity: Minor.
BUG9181
SNMP trap: Yes
Could not send a CRM with a Clearing Cause of Acknowledge. (Procedure

RCVD_MWI_FAC_ACK. Module IDAGW).
Action:
Severity: Minor.
BUG9182
SNMP trap: Yes
Could not send a CRM.

Procedure RCVD_MWI_FAC_REJ. Module IDAGW).
Action:
Severity: Minor.
BUG9183
SNMP trap: Yes
Could not send a Facility Reject message.

Action:
Severity: Minor.
BUG9184
SNMP trap: Yes
Could not send a Facility Reject message. (Procedure MWIGW_FAC_PROB.

Module IDAGW).
Action:
Severity: Minor.
BUG9185
SNMP trap: Yes
Invalid direction for MCDN TCAP Diagnostic Code {-} DPNSS Clearing Cause
mapping. (Procedure MAP_DIAG_CC. Module IDAGW).
Action:
Severity: Minor.
BUG9186
SNMP trap: Yes
Invalid new call state. (Procedure MWIGW_SET_STATE. Module IDAGW).

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 570 of 2360

BUG9187
ITEMPTR is NIL.
(Procedure MWIGW_PARM_CHK. Module IDAGW).
Action:
Severity: Minor.
BUG9188
SNMP trap: Yes
MCDN Message CR pointer is invalid.

Action:
Severity: Minor.
BUG9189
SNMP trap: Yes
CRPTR is invalid.
Action:
Severity: Minor.
BUG9190
SNMP trap: Yes
Invalid GW_FUNCTION. (Procedure MWIGW_PARM_CHK. Module IDAGW).

Action:
Severity: Minor.
BUG9191
SNMP trap: Yes
Could not map the digits for the OLI of the outgoing Message Waiting ISRM.
(Procedure MWIGW_GET_OLI. Module IDAGW).
Action:
Severity: Minor.
BUG9192 x y
SNMP trap: Yes
Invalid source in Procedure IDA_TRK_UTLY

Action:
Severity: Minor.
BUG9193
SNMP trap: Yes
NIL ITEMPTR.
(Procedure IDA_TRUNK_CHK. Module GLB4).
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 571 of 2360

BUG9194
NIL Protected or Unprotected pointer.

(Procedure IDA_TRUNK_CHK. Module GLOB4)
Action:
Severity: Minor.
BUG9195 x
SNMP trap: Yes
x = Signaling type
Invalid Signaling type for an IDA trunk.
(Procedure IDA_TRUNK_CHK. Module GLB4)
Action:
Severity: Minor.
BUG9198 s m
SNMP trap: Yes
D-Channel pointers are not set in SS7.

s = SOURCE
m = MSG_EVENT_TYPE
Action:
Severity: Major.
BUG9224
SNMP trap: No
Invalid parameter to DASS_MAINTENANCE.

Action:
Severity: Minor.
BUG9225
SNMP trap: Yes
Corruption of word RINGSLOT_JUNC in the UBCS_BASICBLK has occurred.

Action:
Severity: Minor.
BUG9227
SNMP trap: Yes
Invalid Channel Number Where: CNO = Channel Number CREF = Call

Reference ESL = ESL Channel DCH = Active D-channel
Action:
Severity: Minor.
SNMP trap: Yes
BUG9229 {number} {parameter} Please contact the Switch Administrator

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 572 of 2360

BUG9232 TRKCR MUSIC_SLOT ROUTENUM TERMINAL *CRPTR *SAVECRPTR TRKCR not
in the call register range. TRKCR is set to NIL.
Where: TRKCR = The call register associated with the music trunks
conference slot.
MUSIC_SLOT = The slot used in the music conference.
ROUTENUM = The music route associated with the call
TERMINAL = TN associated with the last input message.
*CRPTR = Call register info from CALLREGPTR
*SAVECRPTR = Call register info from CRPTR
Action:
Severity: Minor.
BUG9234
SNMP trap: Yes
Wrong parameters have been passed to MEET_HANDLER,

MEET_RCV_MSG or MEET-HANDLER_NAS. Output: {x} = 1
MEET-HANDLER, 2 MEET_RCV_MSG, 3 MEET_HANDLER_NAS
{y} = REQ value, {z} = DATA1 value
Action:
Severity: Critical.
BUG9235
SNMP trap: Yes
Registration to GF of MCDN End to End Transparency has failed.

Action:
Severity: Critical.
BUG9258
SNMP trap: Yes
An invalid state for incoming TWR1 call.

Output data: trktn source tw_inc_pm.
Action:
Severity: Minor.
BUG9260
SNMP trap: Yes
Itempointer is nil in TAIWAN_HANDLER.

Action:
Severity: Info.
BUG9261
SNMP trap: Yes
The number of CR used to count the print CR used for DPNSS/DASS

incoming and outgoing messages is becoming negative.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 573 of 2360

BUG9262
This supervision type is not for Japan DID or CO.

Action:
Severity: Minor.
BUG9263
SNMP trap: No
The ACLI son call register is NIL.

Action:
Severity: Minor.
BUG9265
SNMP trap: Yes
Wireless Telephones ISM counter corruption encountered. Counter is reset to

0.
Action:
Severity: Info.
BUG9266
SNMP trap: Yes
A problem occurred during QSIG Call Transfer.

Severity: Critical.
BUG9267
SNMP trap: Yes
Procedure DV_CLEAR_FLAGS: NIL pointer passed.

Action:
Severity: Major.
BUG9271
SNMP trap: Yes
VNS_END_OF_DIAL has detected an error. If the Return code is

.VNS_SET_PTR_ERR then a System INI was prevented. The parameters are
:
Return code, TASK, CRPTP if CRPTR is valid, then
VNS_TER_INDEX:CRPTR, ORIGTN:CRPTR, TERTN:CRPTR
VNS_ITEM and VNS_ITEMPTR If VNS_ITEMPTR is not nil then
UTN:VNS_ITEMPTR, ACTIVECR:UL_PTR:VNS_ITEMPTR,
VNS_TRUNK_FLAG:UL_PTR:VNS_ITEMPTR
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 574 of 2360

BUG9280
The pointers to the list of free memory were corrupted and have been reset.
No memory is available on this page. If this message is for page 0 and is not
followed by a BUG9281 then the system is out of memory.
Parameters: page (0 for unprotected, 1 for protected), page head and page
tail.
Action: If the page is 0 and BUG9281 is not printed perform a system
initialization as soon as possible, without logging in. If the problem is on page 1
and occurs repetitively the system may run out of memory and a system reload
will be required. Report the problem to the operating company with the full text of
the error message.
Severity: Critical.
BUG9281
SNMP trap: Yes
Unused unprotected memory was not properly tracked. It has been recovered.
Parameters: page (always 0), address and size of recovered block.
Action: The problem has been corrected. No action is required for a single
occurrence. If the error message occurs repetitively data corruption is likely report the problem to the operating company with the full text of the error
message.
Severity: Major.
BUG9282
SNMP trap: Yes
Unused protected memory was not properly tracked. The memory will remain
unavailable until the next system reload. Tracking is updated to reflect the
change.
Parameters: page (always 1), address and size of the unavailable block.
Action: Report the problem to the operating company with the full error printout.
If the problem persists the system may run out of memory and a system reload
should be performed. A system initialization is unlikely to improve the memory
condition.
Severity: Major.
BUG9283
SNMP trap: Yes
A block of memory that is marked unused has been corrupted. It is discarded

to avoid possible conflicts with a persistent misuse of the memory. The
memory will be unusable until the next system initialization or reload
(depending on the page).
Parameters: page and diagnostic information.
Action: Report the problem to the operating company with the full text of the
message. If the problem persists the system may run low on memory and an
initialization or reload may be required.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 575 of 2360

BUG9284
Two memory blocks in the free memory list are detected with block sizes out
of order. The incorrect block is undetermined.
Recovery has been performed to avoid corruption, but may have caused a
loss of free memory. If memory was lost it will not
be recovered until the next system initialization or reload.
Parameters: page, first block address and size, second block address and
size, new size for first block.
Action: Report error to the operating company with the full text of the error
message.
Severity: Major.
BUG9285
SNMP trap: Yes
A pointer to a free memory list was corrupted and is corrected.

Parameters: page, corrupted address, corrupted value, expected value.
Action: The error has been recovered. If it occurs again report the full text of the
error message to the operating company.
Severity: Major.
BUG9286
SNMP trap: Yes
A data block was released that overlaps a block already free. The newly
released block is ignored to avoid duplicate
tracking of memory or possible corruption. This may cause a loss of available
memory in the system.
Parameters: page, start and end addresses of the released block, start and
end addresses of the free block.
error message.
Severity: Major.
BUG9287
SNMP trap: Yes
The free list of protected data has been determined to contain less memory
than expected. Additional protected data will be
allocated from unused unprotected data if it is available.
Parameters: memory size requested, dynamic protected data store boundary,
fixed protected store boundary, (largest
protected data store block available).
Action: Load a service change overlay and check memory availability. If memory
is low a system reload should be planned, to recover the unavailable memory.
Severity: Major.
SNMP trap: Yes
System Messages
Page 576 of 2360

BUG9288
FREE_DATA_BLK or COPY_DATA_BLK was called without data to free or

copy.
Parameters: block size and logical page, or block size and source and
destination pages and addresses.
error message, and any known actions related to the problem occurring.
Severity: Minor.
BUG9289
SNMP trap: Yes
More memory was freed on a logical page than was allocated on that page.
Either the logical pages were different for allocating and deallocating the
memory, or a block has been deallocated twice. The current block may not be
the incorrect block.
Parameters: page size, page number, block size and block address.
error message.
Severity: Minor.
BUG9889
SNMP trap: Yes
Corrupted Backward Link in the Procedure SICE_RECOVERY.

Action:
Severity: Info.
BUG9890
SNMP trap: Yes
SNMP trap: No
IPM: Set HSP_IP failed

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 577 of 2360
CCBR: Customer Configuration Backup

and Restore
Messages
CCBR0000
Program Identifier
Action:
Severity: Minor.
CCBR0001
SNMP trap: No
Invalid command.
Action: Check to make sure your data is correct and re-enter the command.
Severity: Info.
CCBR0002
SNMP trap: No
Invalid argument.
Severity: Info.
CCBR0003
SNMP trap: No
Cannot get resource (pipe) for Ovl 143.

Action: Try to load the overlay again. If the problem persists, contact your
Severity: Info.
CCBR0004
SNMP trap: No
Unexpected signal raised.

Severity: Info.
CCBR0005
SNMP trap: No
Bad answer for sysload confirmation.

Severity: Info.
SNMP trap: No
System Messages
Page 578 of 2360

CCBR0006
Invalid response.
Action:
Severity: Info.
CCBR0007
SNMP trap: No
SDI Port 0 (TTY 0) must be used for the UPGRADE command.

Action: Check that the TTY configuration is correct or use the TTY that is
configured in card 0 port 0 of the Option 11 system.
Severity: Info.
CCBR0008
SNMP trap: No
Missing argument(s) for command entered.

Action: Check input parameters match those listed in the NTPs.
Severity: Info.
CCBR0020
SNMP trap: No
A new keycode has been instantly activated.

Action:
Severity:
CCBR0021
SNMP trap: No
The new keycode cannot be validated for instant activation due to a hard drive
read error.
Action: Perform a hard drive read/write test. Replace the IODU/C if the problem
persists.
Severity: Minor.
CCBR0022
SNMP trap: No
IPMG Package (403) is not equipped; Command not applicable

Action:
Severity: Info.
CCBR0023
SNMP trap: No
Command is aborted; IPMG is not configured

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 579 of 2360
CCED: Core Common Equipment

Diagnostic (LD 135)
Messages
CCED0000
No errors detected.
Action:
Severity: Info.
CCED0001
SNMP trap: No
Invalid command.
Action: Check and reenter the command.
Severity: Minor.
CCED0002
SNMP trap: No
Invalid device name.

Action: Check and reenter the device name.
Severity: Minor.
CCED0003
SNMP trap: No
Extra arguments.
Action: Check the command and reenter it.
Severity: Minor.
CCED0004
SNMP trap: No
Insufficient arguments.
Action: Check the command and re-enter it. You may need to be more specific
(side and slot, for example).
Severity: Minor.
CCED0005
SNMP trap: No
That device is already enabled.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 580 of 2360

CCED0006
That device is already disabled.

Action:
Severity: Minor.
CCED0007
SNMP trap: No
Core side numbers can only be 0 or 1.

Action: Check and re-enter the command.
Severity: Minor.
CCED0008
SNMP trap: No
Invalid slot number. Slot numbers must be 8-12

Action: Enter a slot number 8-12.
Severity: Minor.
CCED0009
SNMP trap: No
Specified device is not configured, and not responding.

Action: Configure the device using the appropriate overlay, and re-enter the
command.
Severity: Minor.
CCED0010
SNMP trap: No
Specified device does not respond.

Action: Be sure the device exists, and reenter the command.
Severity: Minor.
CCED0011
SNMP trap: Yes
Specified device is not configured.

Action: Configure the device using the appropriate overlay, and re-enter the
command.
Severity: Minor.
CCED0012
SNMP trap: Yes
Unable to make the transition to split mode. The test is aborted.

Action:
Severity: Minor.
CCED0013
SNMP trap: Yes
Performing diagnostics.
Action: Wait for test completions before continuing.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 581 of 2360

CCED0014
Test failed because the system is unable to enter Split mode.

Action:
Severity: Minor.
CCED0015
SNMP trap: No
Operation failed because the system is only recognizing 1 CPU.

Action:
Severity: Minor.
CCED0016
SNMP trap: Yes
SNMP trap: Yes
Invalid operand.
Action:
Severity: Minor.
CCED0017
Unable to restore redundancy.

Action: Wait for test completions before continuing.
Severity: Minor.
CCED0018
SNMP trap: No
Secondary side unable to complete test. Sysload the secondary CPU. This
allows the primary CPU to re-synchronize disks.
Action:
Severity: Minor.
CCED0020
SNMP trap: Yes
Cannot enter Split mode when disks are not synchronized.

Action: Refer to LD 137 to re-synchronize disks.
Severity: Minor.
CCED0021
SNMP trap: Yes
Cannot perform SHDW command from CP running call processing.

Action:
Severity: Minor.
CCED0022
SNMP trap: No
Cannot use SHDW command without using the SPLIT command first.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 582 of 2360

CCED0023
Cannot perform TEST when primary SIMM is faulty. Switch Cores (SCPU) and
try again.
Action:
Severity: Minor.
CCED0024
SNMP trap: Yes
Cannot perform TEST when secondary SIMM is faulty.

Action: Switch Cores (SCPU) and try again.
Severity: Minor.
CCED0025
SNMP trap: Yes
Command is not applicable to single CPU system.

Action:
Severity: Minor.
CCED0026
SNMP trap: No
Geographic Redundancy feature not equipped.

Action:
Severity: Info.
CCED0027
SNMP trap: No
Expansion Cabinet 'I' does not have survivable capability

Action:
Severity: Info.
CCED0028
SNMP trap: No
Expansion Cabinet 'I' already in survivable mode.

Action:
Severity: Info.
CCED0029
SNMP trap: No
Expansion Cabinet 'i' already in slave mode.

Action:
Severity: Info.
CCED0030
SNMP trap: No
Cannot execute the command as IP link to cabinet 'I' is down.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 583 of 2360

CCED0031
Expansion Cabinet 'I' is in locked state.

Action:
Severity: Info.
CCED0032
SNMP trap: No
Expansion Cabinet 'I' is already in a locked state.

Action:
Severity: Info.
CCED0033
SNMP trap: No
Expansion Cabinet 'I' is already in a locked state.

Action:
Severity: Info.
CCED0034
SNMP trap: No
Another LOCK/UNLOCK command is in progress. Please wait.

Action:
Severity: Info.
CCED0035
SNMP trap: No
TEST GR - command intended for Primary Call Server but GPRIM package is
restricted.
Action:
Severity: Info.
CCED0036
SNMP trap: No
CLR GR - command intended for Secondary Call Server but GRSEC package
is restricted
Action:
Severity: Info.
CCED0037
SNMP trap: No
TEST GR <TN> command - unequipped/improper TN Should be the TN of an

IP set without NUID/NHTN configured.
Action: Check the TN and re-enter the command.
Severity: Info.
CCED0038
SNMP trap: No
CLR GR command is rejected.

Action:
Severity: Major.
SNMP trap: No
System Messages
Page 584 of 2360

CCED0039
TEST GR ALL/<TN> command - Total test already activated

Action:
Severity: Info.
CCED0040
SNMP trap: No
CLR GR/<TN> command - Secondary CS is already redirecting the IP sets.

Action:
Severity: Info.
CCED0041
SNMP trap: No
Command is not applicable to the redundant CPU system.

Action:
Severity: Info.
CCED0042
SNMP trap: No
Command is not applicable to the split CPU system.

Action:
Severity: Info.
CCED0103
SNMP trap: No
100 Base T hardware does not exist.

Action: Check if 100 Base T daughter board is plugged in properly.
Severity: Major.
CCED0151
SNMP trap: No
Error clearing major alarm.

Action:
Severity: Critical.
CCED0200
SNMP trap: No
CPU test failed.

Action: Check the CP card.
Severity: Critical.
CCED0201
SNMP trap: Yes
SRAM test failed.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 585 of 2360

CCED0202
HPM test failed.

Severity: Critical.
CCED0203
SNMP trap: Yes
SRA test failed.

Severity: Critical.
CCED0204
SNMP trap: Yes
BIC test failed.

Severity: Critical.
CCED0205
SNMP trap: Yes
CMB test failed.

Severity: Critical.
CCED0207
SNMP trap: Yes
DUART test failed.

Severity: Critical.
CCED0208
SNMP trap: Yes
TOD test failed.

Severity: Critical.
CCED0209
SNMP trap: Yes
PEROM test failed.

Severity: Critical.
CCED0210
SNMP trap: Yes
LCD test failed.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 586 of 2360

CCED0211
ASIC ICC test failed.

Severity: Critical.
CCED0212 x
SNMP trap: Yes
SIMM number x failed self test.

Action:
Severity: Critical.
CCED0213
SNMP trap: Yes
Operation failed because the system is in maintenance mode.

Action:
Severity: Critical.
CCED0215
SNMP trap: Yes
Unable to perform switchover.

Action:
Severity: Critical.
CCED0216
SNMP trap: Yes
Unable to lockout graceful switchover possibility.

Action: Try again.
Severity: Critical.
CCED0217
SNMP trap: No
Cannot switch Cores (SCPU) because the core shelf resource is in use. A
critical core shelf resource was being accessed when the SCPU command
was entered.
Action: Try again.
Severity: Critical.
CCED0220
SNMP trap: Yes
Cannot switch Cores (SCPU) because the system is not in redundant mode.
The system is currently running in single mode, so the SCPU command failed.
Check the standby Core, CP to CP cables, and MAINT/NORM switches.
Reset the secondary Core to restore redundancy.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 587 of 2360

CCED0221
Cannot SCPU because the memories are not synchronized.

Action: Wait a minute and try again.
Severity: Critical.
CCED0223
SNMP trap: Yes
Cannot SPCU: Local and Remote Flash ROMs mismatch; if a SCPU or STAT
CPU fails on a non-CPP.
Action:
Severity: Info.
CCED0224
SNMP trap: Yes
SNMP trap: Yes
LOCAL LED Test failed.

Action:
Severity: Info.
CCED0225
REMOTE LED Test failed.

Action:
Severity: Info.
CCED0300
SNMP trap: Yes
SNMP trap: Yes
Invalid SIMM number.

Action:
Severity: Minor.
CCED0301
Cannot disable unshadowed memory.

Action:
Severity:
CCED0302
SNMP trap: No
SNMP trap: No
SIMM failed self test

Action:
Severity:
CCED0303
SIMM cannot be tested while enabled.

Action:
Severity:
SNMP trap: No
System Messages
Page 588 of 2360

CCED0304
Memory test successful. All secondary SIMMs enabled.

Action:
Severity: Minor.
CCED0305
SNMP trap: No
Memories are not synchronized.

Action: Wait and then try again.
Severity: Minor.
CCED0400
SNMP trap: No
Port numbers can only be 0 or 1.

Action:
Severity: Critical.
CCED0401
SNMP trap: Yes
Cannot disable the CNI when is active and in service.

Action:
Severity: Critical.
CCED0403
SNMP trap: Yes
Cannot enable the port when the card is disabled.

Action:
Severity: Critical.
CCED0404
SNMP trap: Yes
Cannot enable a port that does not have a group configured.

Action: Use LD 17 to configure a group before enabling this port.
Severity: Critical.
CCED0405
SNMP trap: No
Cannot test the CNI card that is active and in service.

Action:
Severity: Critical.
CCED0406
SNMP trap: Yes
Cannot enable or disable group 5.

Action:
Severity:
CCED0407w x y z
553-3001-411
SNMP trap: No
Cannot enable CNI card/port w x y because of reason z. For CNI cards, w

=side and x = slot . For CNI ports, w =side, x = slot, and y = port. Reason z
may be one of the following 8 = Unconfigured CNI. 9 = Port has been disabled
Standard 15.00
January 2006
Page 589 of 2360

by craftsperson.
10 = Device is not accessible. 16 = CNI to 3PE cable 1 on specified card and
port lost. 17 = CNI to 3PE cable 2 on specified card and port lost. 18 = 3PE
power lost.
19 = 3PE has been manually disabled. 20 = CNI card has been manually
disabled. 21 = Card test failed. 22 = Port test failed.
23 = INI disabled network. 24 = READY interrupt is stuck for this group. 25 =
I/O interrupt is stuck for this group.26 = LINE interrupt is stuck for this group
27 = CNI maintenance interrupt is stuck for this group. 28 = CNI to 3PE cable
lost on CPP system.
Action:
Severity: Critical.
CCED0408 w x y
SNMP trap: Yes
Will attempt to enable CNI card/port at the next switchover. The CNI card or
port has been noted as enabled. Because it resides on the standby side, it
cannot actually be enabled until the standby side becomes active.
For CNI cards, w =side and x = slot. For CNI ports, w =side, x = slot, and y =
port.
Action:
Severity: Critical.
CCED0409
SNMP trap: No
Cannot disable port when board enabled on inactive core.

Action:
Severity: Critical.
CCED0410 x y z
SNMP trap: Yes
Event interrupt 0 test failed. Where: x = side (0-1), y = slot (8-12) and z = port
(0-1)
Action: Check the CNI.
Severity: Critical.
CCED0411 x y z
SNMP trap: Yes
(0-1)
Severity: Critical.
SNMP trap: Yes
System Messages
Page 590 of 2360

CCED0412 x y z
(0-1)
Severity: Critical.
CCED0413 x y z
SNMP trap: Yes
(0-1)
Severity: Critical.
CCED0414 x y z
SNMP trap: Yes
BIC test failed. Where: x = side (0-1), y = slot (8-12) and z = port (0-1)
Severity: Critical.
CCED0415 x y z
SNMP trap: Yes
Loopback address errors. Where: x = side (0-1), y = slot (8-12) and z = port
(0-1)
Severity: Critical.
CCED0416 x y z
SNMP trap: Yes
Loopback parity test failed. Where: x = side (0-1), y = slot (8-12) and z = port
(0-1)
Severity: Critical.
CCED0417 x y z
SNMP trap: Yes
Loopback address parity invert errors. Where: x = side (0-1), y = slot (8-12)
and z = port (0-1)
Severity: Critical.
CCED0420 x y z
SNMP trap: Yes
Loopback data parity errors on LSB. Where: x = side (0-1), y = slot (8-12) and
z = port (0-1)
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 591 of 2360

CCED0421 x y z
Loopback data parity errors on MSB. Where: x = side (0-1), y = slot (8-12) and
z = port (0-1)
Severity: Critical.
CCED0422 x y z
SNMP trap: Yes
Event interrupts occurring out of sequence. Where: x = side (0-1), y = slot

(8-12) and z = port (0-1)
Severity: Critical.
CCED0423 x y z
SNMP trap: Yes
Event interrupts lost. Where: x = side (0-1), y = slot (8-12) and z = port (0-1)
Severity: Critical.
CCED0424 x y z
SNMP trap: Yes
Event interrupts timeout test. Where: x = side (0-1), y = slot (8-12) and z = port
(0-1)
Severity: Critical.
CCED0425 x y z
SNMP trap: Yes
Read strobe test failed. Where: x = side (0-1), y = slot (8-12) and z = port (0-1)
Severity: Critical.
CCED0426 x y z
SNMP trap: Yes
Write strobe test failed. Where: x = side (0-1), y = slot (8-12) and z = port (0-1)
Severity: Critical.
CCED0427 x y z a
SNMP trap: Yes
CNI port x y z a incorrect. Restored. Where: x = side (0-1), y = slot (8-12), z =

port (0-1) and a = EI.

Severity: Critical.
SNMP trap: No
System Messages
Page 592 of 2360

CCED0428 x y z a
CNI port x y z is in incorrect mode. Restoring to a mode. Where: x = side (0-1),

y = slot (8-12), z = port (0-1) and a = mode.
Action:
Severity: Critical.
CCED0429 x y z
SNMP trap: No
CNI port x y z remote device (3PE) is not accessible. Where: x = side (0-1), y
= slot (8-12), and z = port (0-1).
Action: Check both connector ends of the CNI-3PE cable. Be sure the 3PE
enable/disable switch is enabled (up).
Severity: Critical.
CCED0500
SNMP trap: Yes
IPB IRQ test failed. This may indicate a failure on the CP card.
Action:
Severity: Critical.
CCED0501
SNMP trap: Yes
IPB master arbitration test failed. This may indicate a failure on the CP card.
Action:
Severity: Critical.
CCED0502
SNMP trap: Yes
IPB event interrupt failed. This may indicate a failure on the CP card.
Action:
Severity: Critical.
CCED0503 x
SNMP trap: No
IPB backplane parity test failed.

Action: Contact your technical service support.
Severity: Critical.
CCED0504
SNMP trap: Yes
Test aborted. No cards were found on standby IPB.

Action:
Severity:
CCED0505 x
SNMP trap: No
Fiber hardware does not exist.

Action: Check if Fiber Daughter Board is plugged in properly.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 593 of 2360

CCED0506
Fiber pack failed loop back test.

Action: Check if the Fiber Receiver Pack and cable are installed properly. Might
have to replace the Fiber Daughter Board.
Severity: Major.
CCED0507
SNMP trap: Yes
Cabinet has not been disabled.

Action: LD32 and DISS the cabinet
Severity: Info.
CCED0508
SNMP trap: Yes
The fiber pack has not been disabled.

Action: Disable the fiber pack.
Severity: Info.
CCED0509
SNMP trap: Yes
Cabinet is out of range.

Action: Re-enter the cabinet number
Severity: Info.
CCED0760
SNMP trap: No
Graceful switchover to side x requested.

Action:
Severity: Minor.
CCED0761
SNMP trap: Yes
Ungraceful switchover to side x requested.

Action:
Severity: Minor.
CCED0762
SNMP trap: Yes
Graceful switchover to side x completed. Previous graceful switchover at

{time}.
Action:
Severity: Minor.
CCED0999
SNMP trap: Yes
LD 135 internal error in file {name} at line {number}.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 594 of 2360

CCED1011
Operation is applicable only on the active side.

Action:
Severity: Info.
CCED1012
SNMP trap: No
Unable to get the right Memory Size.

Action:
Severity: Info.
CCED1021
SNMP trap: No
Port number out of range.

Action:
Severity: Info.
CCED1022
SNMP trap: No
IP link failed loop-back test.

Action:
Severity: Info.
CCED5021
SNMP trap: No
Not a redundant system.

Action:
Severity: Info.
CCED5022
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Can not enable : %s.

Action:
Severity: Info.
CCED5023
Cannot disable : %s.

Action:
Severity: Info.
CCED5024
Cannot Test : % s.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 595 of 2360

CCED5025
Can not Stat : %s.

Action:
Severity: Info.
CCED5026
SNMP trap: No
Object not configured: %s.

Action:
Severity: Info.
CCED5027
SNMP trap: No
CNIP %d %d:CNI-3PE Cable lost.

Action:
Severity: Info.
CCED5028
SNMP trap: No
Command is not valid when HSP is down.

Action:
Severity: Info.
CCED5029
SNMP trap: No
Redundant system is unable to execute command.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 596 of 2360
553-3001-411
Standard 15.00
January 2006
Page 597 of 2360
CDM: Call Detail Recording Diagnostic

(LD 40, LD 42)
The Call Detail Recording (CDR) feature outputs call records to a single, or
multi-port, tape drive storage system. The tapes are processed to produce
billing reports.
The CDM programs (LD 40 and LD 42) test the link and the external storage
system. The CDM messages indicate problems with the CDR storage system
and are output in response to commands issued in LD 42.
Some CDM messages contain the following output data. The hexadecimal
number must be translated into a binary number (see HEX).
Messages
CDM0000
Call Detail Recording Diagnostic Program (LD 42) identifier.

Action:
Severity: Info.
CDM0001
SNMP trap: No
Invalid command.
Action: Check the command and re-enter.
Severity: Info.
CDM0002
SNMP trap: Yes
Invalid operand, too many operands or operand out-of-range.

Action: Check command and operands; reenter.
Severity: Info.
CDM0010
SNMP trap: Yes
Invalid operand, too many operands or operand out-of-range.

Action: Check command and operands; reenter.
Severity: Info.
CDM0011 x
SNMP trap: No
Device x is not a link or it is disabled or unequipped.

Action: Use STAT N command to check state of device.
Severity: Info.
SNMP trap: Yes
System Messages
Page 598 of 2360

CDM0012 x
The echo test failed on link x. If the CDR machine is running and indicates no
unusual conditions in its maintenance display, then something in the
communication channel between the SL-1 machine and CDR is faulty. It could
be a faulty SDI, modem, cable or line, or the option plug on the SDI pack may
be in the wrong position.
Action: If modems are involved, the fault may be isolated by setting the loop
back switches (if present) and using the ECHO command to perform the echo
test. Having isolated the fault as much as possible, the remaining equipment
should be replaced one by one until the fault is cleared.
Severity: Info.
CDM0013 X
SNMP trap: Yes
Link x has timed out or it had a transmission error 3 times in a row. This
message may occur in response to a command that requires communication
between CDM and the CDR machine, or it may occur while CDM is trying to
keep the CDR machine in maintenance mode.
The command requested was not performed because of a transmission error
on the link. This will also occur if the CDR machine is not responding. Very
occasional transmission errors are acceptable and should be ignored.
Action: Reissue the command. If the problem recurs, The ECHO command
should be used to test the link. To check if CDR is responding, press the restore
button. The tape should move backwards a short distance and then forward
again.
Severity: Info.
CDM0014
SNMP trap: Yes
This command may not be issued unless the PORT command has been used
to set the port to which it applies.
Action:
Severity: Info.
CDM0015
SNMP trap: Yes
Invalid hexadecimal digit was output.

Action:
Severity: Info.
CDM0016
SNMP trap: Yes
This command is only permitted from a TTY.

Action: Login on a TTY to use the command.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 599 of 2360

CDM0017 x
Maintenance request was rejected by item at end of link x.

Action: See the description of CDR maintenance mode in LD 40,42. The
maintenance mode timed out and hence CDR is no longer in maintenance mode.
If it occurred when the GET command was issued, the device at the end of the
link is not a CDR machine. If the device is not a CDR machine, the CDM may not
be used to perform maintenance on it except for the ECHO command.
Severity: Info.
CDM0018
SNMP trap: Yes
Maintenance mode is already set. The command is ignored.

Action:
Severity: Info.
CDM0019
SNMP trap: Yes
This command cannot be issued unless maintenance mode is set.

Action: See the description of maintenance mode in LD 40, 42.
Severity: Info.
CDM0020
SNMP trap: Yes
The device is not of the type specified or the device is not equipped.
Action:
Severity: Info.
CDM0021
SNMP trap: Yes
Device is already enabled.

Action:
Severity: Info.
CDM0022
SNMP trap: Yes
The device did not respond.

Action: Check that the address switches are set correctly and that the pack is
enabled. Otherwise, the pack is faulty.
Severity: Info.
CDM0023
SNMP trap: Yes
The device has a permanent interrupt. The pack is probably faulty.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 600 of 2360

CDM0024
You have attempted to disable the TTY you are using.

Action: Log onto another TTY or use a maintenance SL-1 telephone to disable
the TTY.
Severity: Info.
CDM0025
SNMP trap: Yes
Unable to obtain CDR call register. The LINK was not enabled.
Action: Retry command. If problem persists, call registers have not been lost or
system is under-engineered.
Severity: Info.
CDM0026 x s u
SNMP trap: Yes
The tape unit is not ready, off-line or rewinding on link x.

Action: Correct the problem and retry the command. If non of the above caused
the message, a fault is indicated in the QPC130 CDR Tape Control pack, cables
or tape unit. See summary for input codes.
Severity: Info.
CDM0027 x s u
SNMP trap: Yes
The tape did not rewind correctly on link x. The fault is in the tape, QPC130
pack, cables or tape unit. See Summary for output codes.
Action:
Severity: Info.
CDM0028 x
SNMP trap: Yes
Write protect status was returned on link x.

Action: Ensure that the write enable ring is installed and that the write enable
light on the drive is lit. If the problem persists, suspect a fault in the QPC130,
cables or tape drive.
Severity: Info.
CDM0029 x s u
SNMP trap: Yes
The write ID burst function failed on link x.

Action: Retry the command. If the problem persists, suspect a fault in the
QPC130, cables or tape drive.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 601 of 2360

CDM0030 x s u
Erase gap function failed on link x. The drive may need cleaning or a fault is
indicated in the tape, QPC39, QPC130, cables or tape drive. See Summary
for output codes.
Action:
Severity: Info.
CDM0031 x s u
SNMP trap: Yes
Load point status was returned when it should not have been. This problem
could be caused by an extra or damaged load point marker on the tape.
Action: Repeat the test with a different scratch tape. If the fault persists, suspect
he QPC130, QPC39, cables or tape unit. See Summary for output codes.
Severity: Info.
CDM0032 x s u
SNMP trap: Yes
EOT status was returned by the tape unit when it should not have been. An
extraneous EOT marker may be on the tape.
Action: Retry command with a different tape. If the problem persists, Repeat the
test with a different scratch tape. If the fault persists, a fault is indicated in the
QPC130, QPC39, cables or tape unit. See Summary for output codes.
Severity: Info.
CDM0033 x s u
SNMP trap: Yes
An unexpected interrupt occurred on link x. The fault could be in the tape,

QPC39, QPC130, cable or tape drive. See Summary for output codes.
Action:
Severity: Info.
CDM0034 x s u
SNMP trap: Yes
The function timed out on link x. The fault could be in the tape, QPC39,
QPC130, cables or tape drive. See Summary for output codes.
Action:
Severity: Info.
SNMP trap: Yes
CDM0035 x p h s r This is the number of each type of error that occurred during the test command
on link x. If all the counts are zero, the test passed.
p = parity. Parity errors should almost never occur. They indicate an error in
the transmission of data between the tape unit and the interface pack.
Action: Retry the commands. If the errors persist the fault is in the QPC130, the
cables connecting the interface to the drive or the tape drive. h = hard write.
These errors should almost never occur. They indicate severe problems. Retry
the command. If the errors persist, a fault is indicated in the tape, QPC130,
System Messages
Page 602 of 2360

QPC39, cables or tape unit.
s = soft write. Occasional soft write errors are acceptable. These are usually
caused by faults on the tape or a dirty drive. If the problems persist after cleaning
the drive and ensuring that a good tape is being used, the fault is probably in the
QPC39, QPC130, cables or tape drive.
r = read. These errors are about as serious as soft write, and usually have the
same causes.
Severity: Info.
CDM0036 x s u
SNMP trap: Yes
ID burst detection failure. When the tape was read, the ID burst was not found
where it was expected.
Action: Retry the command. If the trouble persists, the fault is in the tape,
QPC39, QPC130, cables or tape drive. See summary for input codes.
Severity: Info.
CDM0037 x
SNMP trap: Yes
CDR machine attached to port x is in maintenance mode for some other SL-1
machine. The GET command will not work until the other SL-1 frees the CDR
machine from maintenance mode.
Action: Wait for the CDR machine to be freed from the maintenance mode by
the other SL-1.
Severity: Info.
CDM0038
SNMP trap: Yes
ENL SL1 M and DIS SL1 M commands are invalid for single-port CDR
machines.
Action:
Severity: Info.
CDM0039
SNMP trap: Yes
ENL SL1 M and DIS SL1 M commands are invalid for 8K CDR machines.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 603 of 2360

CDM0040
ENL SL1 M failed to enable the requested SL-1 port on the multi-port CDR
machine.
Action: Check to make sure that M corresponds to the device address switch
setting on the new QPC139 port. Check the maintenance display (if any) on the
CDR machine. The SL-1 may not be connected to the CDR port indicated on the
CDR maintenance display.
Severity: Info.
CDM0041
SNMP trap: Yes
DIS SL1 M may have failed to disable the requested SL-1 port on the multi-port
CDR machine.
Action: Retry the command. If the problem persists, there may be a software
problem.
Severity: Info.
CDM0042
SNMP trap: Yes
Use LD 37 to enable/disable TTY user of APL, CMC, HSL, or LSL.

Action:
Severity: Info.
CDM0044
SNMP trap: Yes
Use LD 37 to enable/disable PMS link.

Action:
Severity: Info.
CDM0101 x
SNMP trap: Yes
Program was unable to get diagnostic information from CDR link x. The link
timed out or had a transmission error 3 times.
Action: Use ECHO test to check link. See comments for CDM0013. Minor lamp
lit on attendant console.
Severity: Info.
CDM0102 x c e
SNMP trap: Yes
More than 5 percent of the writes that have been attempted since counts were
reset have encountered write errors. Where: c = number of blocks written; e =
number of errors occurred.
Action: If write is being successfully written, suspect the tape or intermittent
drive fault. If problem continues to occur, the tape heads should be cleaned or the
tape changed. Note that with more than 5 percent write errors on the whole tape,
System Messages
Page 604 of 2360

the tape will encounter EOT before the 90 percent indicator is set. If the tape is
not being successfully written, it may have to be unloaded. Refer to the tape fault
clearing procedures.
Severity: Info.
CDM0103 x t p r
SNMP trap: Yes
Indicates number of TM errors t, parity errors p, and RBC errors r, that have
occurred since the counts were reset. This message is printed if one of the
counts is nonzero. TM errors indicate possible drive or tape faults.
Action: Clean tape heads and change tape. If problem persists, refer to the tape
drive fault-clearing procedures. Very occasional occurrences of this message
with small numbers are acceptable. If the numbers are large or the message
occurs regularly, a fault is probably present. Parity errors and RBC errors both
indicate drive or interface faults. Replace the QPC130 Tape Interface and/or the
cables. If problem persists, tape drive is faulty.
Severity: Info.
CDM0104 x
SNMP trap: Yes
Tape is 90 percent full on link x. 11,000 blocks have been written onto the tape.
(This only occurs with 2400-foot tape reels.)
Action: Change tape.
Severity: Info.
CDM0105 x
SNMP trap: Yes
Over-temperature has been detected in the CDR cabinet on link x. The CDR
machine may be in too warm a location. Minor alarm lamp lit on attendant
console.
Action:
Severity: Info.
CDM0106 x
SNMP trap: Yes
Fan failure has been detected in the CDR cabinet on link x.

Action: Check CDR fan operation and filter. Minor alarm lit on attendant console.
Severity: Info.
CDM0107 x
SNMP trap: Yes
End-of-tape (EOT) was encountered by the drive on link x. The tape has been
Action: Change tape.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 605 of 2360

CDM0108 x
Error counts could not be reset after 3 tries, i.e., counts may not be accurate
for the next time the CDR runs.
Action: This message should be treated the same way as CDM101. Minor alarm
lamp lit on attendant console.
Severity: Info.
CDM0109 x
SNMP trap: Yes
The system ID could not be set after 3 tries on link x. The system ID on the
tape may be incorrect.
Action: Message should be treated the same way as CDM101. Minor alarm
lamp lit on attendant console.
Severity: Info.
CDM0110 t l
SNMP trap: Yes
Some call records in SL-1 machine have been lost. The total (t) is the number
of records created since the counts were reset; and lost (l) is the number that
were not recorded. If a CDR port (link or TTY) is disabled, that is probably why
the records were lost. If not, the system does not have enough call registers.
Action:
Severity: Info.
CDM0111 x t f
SNMP trap: Yes
ECHO test has failed (f) times out of tries.

Action: Message should be treated the same way as CDM012.
Severity: Info.
CDM0112 x
SNMP trap: Yes
CDR link x is disabled so that the automatic tests were not performed. Minor
alarm lamp lit on attendant console.
Action:
Severity: Info.
CDM0113 x
SNMP trap: Yes
An initialize occurred in the CDR on link x. Refer to CDM118.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 606 of 2360

CDM0114 x
CDR tape drive is in disabled state. No calls are being recorded on tape. Act
immediately to minimize number of lost call records.
Action: If drive has had a power failure or if there is a fault code on the CDR
maintenance display, see 553-2631-510. If tape is unloaded, send tape for
processing and mount new tape. Press LOAD button. Respond to any fault
codes. Attempt to make the drive ready for use by pressing RESTORE button.
Respond to any fault code.
Severity: Info.
CDM0115 x
SNMP trap: Yes
Echo test failed. Link did not finish output.

Action:
Severity: Info.
CDM0116
SNMP trap: No
Program tried to run for more than 20 min. Probably indicates software fault
but could also occur if a large number of links are equipped on the system and
have faults.
Action:
Severity: Info.
CDM0117 x r
SNMP trap: Yes
CDM was loaded automatically for fault reason r on link x. The reasons are: a)
CDR has detected a fault and requested service b) the error threshold on link
was exceeded c) LD 40 was loaded manually
Action:
Severity: Info.
SNMP trap: Yes
CDM0118 x c fp fa pg pc This message indicates that an initialize occurred in the CDR machine.
Where c is the cause: 8000 response time-out 4000 write protect violation
2000 watchdog timeout
1000 parity error
0800 software trap
0400 power reset
0000 unknown cause.
c may also contain the value of the CDR maintenance display in the right-most
2 digits. See HEX.
That there can be more than one cause for a trap resulting in a error code
which is the hexadecimal sum of those shown.
fp = fault page
553-3001-411
Standard 15.00
January 2006
Page 607 of 2360

fa = fault address
pg = page
pc = program counter.
Action:
Severity: Info.
CDM0119 x
SNMP trap: Yes
Link x is disabled and therefore the automatic diagnostics were not performed
for it. Minor alarm lamp lit on attendant console.
Action:
Severity: Info.
CDM0120 x c e
SNMP trap: Yes
Where: c = the number of blocks written, e = the number of errors that have
occurred. This message should be treated as CDM102.
Action:
Severity: Info.
SNMP trap: Yes
CDM0121 x m n t l Fault statistics on link x, where:

m = number of different messages processed n = number of messages not
correctly received by CDR t = the number of messages that timed out at the
SL-1 l = number of messages that failed the retransmissions These counts are
reset whenever Overlay 40 is loaded or when the ENL LINK N command is
used from Overlay 42. The error message is output only if n or t is nonzero.
Occasional {naks} and {time-outs} counts that do not cause lost messages are
probably the result of transient noise on the link and they may be ignored. If
messages are being lost, suspect a link fault.
Action: Use ECHO command to test the link.
Severity: Info.
SNMP trap: Yes
CDM0122 x s1 u1 f1 s2 u2 f2 s3 u3 f3 Provides statistics for the last 3 tape functions which had
errors on link x.
Action: If any other error codes are output, then respond to them. If this is the
only error code, then suspect QPC39, QPC130, connecting cables or tape unit to
be at fault. See summary for output codes s u and f.
Severity: Info.
SNMP trap: Yes
System Messages
Page 608 of 2360

CDM0123 x
The device attached to port x is not a Northern Telecom single-port or

multi-port CDR machine. If this error occurs with a standard CDR unit, a
software problem may be indicated.
Action:
Severity: Info.
CDM0124 x
SNMP trap: Yes
During the running of the midnight routines, an attempt to clear accumulated

data for this port from memory to tape failed 3 times on link x. Data may remain
in memory.
Action: This should be treated like CDM101. Minor alarm lamp lit on attendant
console.
Severity: Info.
CDM0125 x
SNMP trap: Yes
A software fault in the CDR link x has occurred. Minor alarm lamp lit on
attendant console.
Action:
Severity: Info.
CDM0126 x m
SNMP trap: Yes
Because of insufficient memory space, the CDR machine x had to discard m

data messages. The discard may occur if the tape drive spends too long not
writing. For example, replacing a tape during a period of heavy traffic could
cause some data to be lost unless the replacement is executed quickly.
Action:
Severity: Info.
CDM0202
SNMP trap: Yes
This command is not applicable to the TTY for MSDL, or CPSI cards, and
option 81 PTY type.
Action:
Severity: Info.
CDM0203
SNMP trap: Yes
Failed to setup the global pointers to the SDI data structures.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 609 of 2360

CDM0204
Failed to setup the global pointers to the MSDL data structures.

Action:
Severity: Info.
CDM0205
SNMP trap: Yes
The MSDL card is not enabled and operational. Therefore the TTY/LINK can
not be enabled.
Action: First enable the MSDL card.
Severity: Info.
CDM0213
SNMP trap: Yes
Cannot use "DIS TTY #" to disable STA administration terminal.

Action:
Severity: Info.
CDM0214
SNMP trap: Yes
Cannot use "ENL TTY #" to enable STA administration terminal.

Action:
Severity: Info.
CDM0900
SNMP trap: Yes
A software fault has occurred in CDM or CDMA.

Action: Retry the command if Overlay 42 is being used.
Severity: Info.
SNMP trap: Yes
System Messages
Page 610 of 2360
553-3001-411
Standard 15.00
January 2006
Page 611 of 2360
CDN: Control DN
Messages
CDN0001
The specified CDN was put to *** Revert to Default process *** by an
application on the Link#. The format of this message is: CDNxxxx Link# CDN#
Hour Minute Second.
Action:
Severity:
CDN0002
SNMP trap: Yes
The specified CDN was put to control mode by an application on the Link#.
The format of this message is: CDNxxxx Link# CDN# Hour Minute Second.
Action:
Severity:
CDN0003
SNMP trap: Yes
The specified CDN was put to Default mode by an application on the Link#.
The format of this message is: CDNxxxx Link# CDN# Hour Minute Second.
Action:
Severity:
SNMP trap: Yes
System Messages
Page 612 of 2360
553-3001-411
Standard 15.00
January 2006
Page 613 of 2360
CIOD: Core Input/Output Diagnostic (LD

137)
The message output format is: CIOD x y z, where: x = side, y = card and z =
port
Messages
CIOD0000
Overlay Program 137 has been loaded.

Action:
Severity: Info.
CIOD0001
SNMP trap: No
SNMP trap: No
SNMP trap: No
Invalid command.
Action:
Severity: Info.
CIOD0002
Invalid argument.
Action:
Severity: Info.
CIOD0003
The device number is out-of-range. Enter 0 or 1.

Action:
Severity: Info.
CIOD0004 x
SNMP trap: No
HDK x test failed. The hard disk on CMDU x failed the test.
Action: Try the test again. If it fails three times, the CDMU needs to be replaced.
Contact your technical service support.
Severity: Minor.
CIOD0005
SNMP trap: Yes
The requested device cannot be accessed due to a software error.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 614 of 2360

CIOD0006
That device is already enabled.

Action:
Severity: Info.
CIOD0007
SNMP trap: No
That device is already disabled.

Action:
Severity: Info.
CIOD0008 x
SNMP trap: No
FDK x failed. The floppy disk on CMDU x failed the test.

Action: Try the test again. If it fails three times, the floppy drive needs to be
replaced. Contact your technical service support.
Severity: Minor.
CIOD0009
SNMP trap: Yes
Failed to disable device.

Action:
Severity: Minor.
CIOD0010
SNMP trap: No
Related data (CMDU status) is mismatched due to a software error.

Action:
Severity: Critical.
CIOD0011
SNMP trap: No
IOP test failed. See fault reporting for the reason for the failure.
Action:
Severity: Critical.
CIOD0012 x
SNMP trap: No
Cannot access CMDU x because the system is in split mode. System must be
redundant before attempting this command.
Action:
Severity: Minor.
CIOD0013
SNMP trap: Yes
The CMDU number is required.

Action: Enter 0 or 1 to indicate which device.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 615 of 2360

CIOD0014
RDUN test failed because the disk contents are not synchronized.
Action: Be sure to synchronize disks before attempting RDUN.
Severity: Critical.
CIOD0015
SNMP trap: No
ENL command failed, and device cannot be enabled, because it cannot be

accessed.
Action: Be sure device is enabled and cables are connected.
Severity: Minor.
CIOD0016
SNMP trap: No
RDUN command failed because the disk redundancy is in disabled state.

Action: Enable the disk redundancy before using the RDUN command.
Severity: Minor.
CIOD0017
SNMP trap: No
SYNC command failed because the disk redundancy is in enabled state.

Action:
Severity: Minor.
CIOD0018
SNMP trap: No
SYNC command failed because of a software mismatch.

Severity: Minor.
CIOD0019
SNMP trap: Yes
SYNC command failed.

Action: Refer to fault reporting for the reason for the failure.
Severity: Minor.
CIOD0020
SNMP trap: No
SYNC command failed because there is no system resource available at this

time.
Action: Try again later.
Severity: Critical.
SNMP trap: No
System Messages
Page 616 of 2360

CIOD0021 xx
SYNC in progress. XX% complete. This is a status message. Synchronization

may take a long time. This message helps indicate how far along the
synchronization is.
Action:
Severity: Minor.
SNMP trap: No
CIOD0022XXXX yy CABLE yy is loose, or CMDU yy is inaccessible. The SCSI test was performed
successfully on both sides. The test failed because of a loose cable or
inaccessible CMDU. Whichever is applicable is printed.
XXXX may be CABL or CMDU: CABL yy means that a cable is loose, or the
status is unknown because both CDMUs are inaccessible. CDMU indicates
that the CDMU is inaccessible.
Action:
Severity: Critical.
CIOD0023
SNMP trap: No
Unable to switch to inactive CP. The current CP remains active. The SCSI test
was performed on the active side only, and the switchover attempt failed.
Refer to CIOD024 for active side information.
Action:
Severity: Critical.
SNMP trap: No
CIOD0024 XXXX yy This message is associated with CIOD0023 message to display the cable
status and CMDUs accessibility on the active side. The test had failed due to
either cable is loose or inaccessible CMDU(s). If CMDU on the inactive side is
inaccessible, it could be either CMDU is inaccessible or the cable between
IOPs is loose.
XXXX may be CABL or CMDU. The text string is variable in length and is
depending on the parameter list of the failure components. CABL yy indicates
cable might be loose which requires further investigation. CMDU yy indicates
which CMDU is inaccessible, if applicable.
Action:
Severity: Critical.
CIOD0025
SNMP trap: No
Unable to switch back to active CP. The SCSI test was performed on both
side, but the system cannot return to the original active CP. The inactive CP is
now active. Refer to CIOD026 for status.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 617 of 2360

CIOD0026XXXX yy This message displays cable status and CMDU accessibility for both sides
due to the inability to switch back to the original active CP.
XXXX can refer to CABL, or CMDU. Output may be one of the following:
CMDU yy indicates which CMDU is inaccessible.
CABL yy means the cable is loose, or the status in unknown.
Action:
Severity: Critical.
CIOD0027
SNMP trap: No
SCSI test failed because an invalid address was detected for SCSI address 6
or 7.
Action: Check the drive and address.
Severity: Critical.
CIOD0028
SNMP trap: No
No resource is available for overlay input processing.

Severity: Info.
CIOD0029
SNMP trap: No
Both CMDUs are disabled.

Action: Enable a CMDU.
Severity: Critical.
CIOD0030
SNMP trap: No
Disk redundancy (RDUN) file level check failed. The CMDU and/or disk
redundancy cannot be enabled.
Action:
Severity: Critical.
CIOD0031
SNMP trap: No
Abort delayed because a critical write is in progress. The abort will be delayed
until the write is complete.
Action:
Severity: Minor.
CIOD0032
SNMP trap: No
To issue this command, the IOP must be enabled.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 618 of 2360

CIOD0033
To test the IOP, it must be disabled.

Action:
Severity: Info.
CIOD0034
SNMP trap: No
To perform the Read/Write test, the CMDU must be enabled.

Action:
Severity: Info.
CIOD0035
SNMP trap: No
That response is not allowed for this prompt.

Action: Check the desired response and try again.
Severity: Info.
CIOD0036 xx
SNMP trap: No
Read test in progress. XX% complete. This is a status message output during
an exhaustive read test. This test may take a while, so this message helps
keep track of the status.
Action:
Severity: Info.
CIOD0037 xx
SNMP trap: Yes
Synchronization sector check in progress. XX% complete. This is a status

message output during the check. This test may take a while, so this message
helps keep track of the status.
Action:
Severity: Info.
CIOD0038
SNMP trap: Yes
Card ID cannot be read.

Action: Reseat or replace the card.
Severity: Critical.
CIOD0039
SNMP trap: No
SYNC command failed because both CMDUs are disabled.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 619 of 2360

CIOD0040 x
Cannot access CMDU x.

Action: Be sure it is enabled, and check cabling.
Severity: Critical.
CIOD0041 x
SNMP trap: Yes
Unexpected signal x raised, interfering with LD 137.

Action: Contact your technical service support.
Severity: Critical.
CIOD0042
SNMP trap: No
Synchronization failed because the system is in split mode.

Action:
Severity: Critical.
CIOD0045
SNMP trap: No
To issue the SWAP command, disk redundancy must be enabled.

Action:
Severity: Critical.
CIOD0046
SNMP trap: No
Unable to lockout graceful switchover possibility. The switchover was

performed while the maintenance command is in progress.
Action:
Severity: Critical.
CIOD0053
SNMP trap: No
CMDU "x" CD-ROM corrupted or missing

Action:
Severity: Major.
CIOD0056
SNMP trap: No
<test> fails : can't read local hard disk

where <test> can be TEST RDUN or DATA RDUN
Action: check local hard disk
Severity: Major.
CIOD0057
SNMP trap: No
<test> fails : can't read remote hard disk

Action: Check remote hard disk
Severity: Major.
SNMP trap: No
System Messages
Page 620 of 2360

CIOD0058
<test> fails: can't start disk sync

Action: contact your technical support
Severity: Major.
CIOD0059
SNMP trap: No
%s aborted
Action:
Severity: Minor.
CIOD0100
SNMP trap: No
Valid cable loss. Store current CMDU states.

Action:
Severity: Critical.
CIOD0101
SNMP trap: No
SCSI cable reconnected. Cannot restore CMDU states because the IOP is
disabled.
Action: Re-enable IOP in LD 137 (ENL IOP, ENLT).
Severity: Critical.
CIOD0102
SNMP trap: Yes
CMDU states previously stored when IOP was disabled.

Action:
Severity: Critical.
CIOD0103 x
SNMP trap: No
CMDU x hard disk inaccessible. Cannot restore to standby.

Action: Be sure CMDU power is on, and check IOP to IOP cables.
Severity: Critical.
CIOD0104 x
SNMP trap: Yes
CMDU x hard disk inaccessible. Cannot restore to active.

Action: Be sure CMDU power is on, and check IOP to IOP cables.
Severity: Critical.
CIOD0105 x
SNMP trap: Yes
CMDU x cannot delete hard disk test file.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 621 of 2360

CIOD0106 x
CMDU x cannot delete floppy disk test file.

Action:
Severity: Critical.
CIOD0107
SNMP trap: No
SNMP trap: Yes
No floppy disk in drive.

Action:
Severity: Critical.
CIOD0108
Floppy disk not formatted.

Action:
Severity: Critical.
CIOD0109
SNMP trap: Yes
Floppy disk is Write Protected.

Action: Be sure the write protect tab is closed.
Severity: Critical.
CIOD0110 x
SNMP trap: Yes
SCSI cable missing, both CMDUs are disabled.

Action: Check both ends of the IOP to IOP cables.
Severity: Critical.
CIOD0111 x
SNMP trap: Yes
Valid cable reconnect. Attempting to restore CMDU states.

Action:
Severity: Critical.
CIOD0112
SNMP trap: No
Invalid cable loss. Multiple loss messages, states not stored.

Action:
Severity: Critical.
CIOD0113
SNMP trap: No
Invalid cable loss. CMDU accessible, states not stored.

Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 622 of 2360

CIOD0114 x
CMDU x hard disk has insufficient memory for quick read/write test.
Action:
Severity: Critical.
CIOD0115 x
SNMP trap: No
CMDU x floppy disk has insufficient memory for quick read/write test.
Action:
Severity: Critical.
CIOD0116 x
SNMP trap: No
CMDU x hard disk cannot open file for quick read/write test.
Action:
Severity: Critical.
CIOD0117 x
SNMP trap: No
CMDU x floppy disk cannot open file for quick read/write test.
Action:
Severity: Critical.
CIOD0118 x
SNMP trap: No
CMDU x could not read card ID.

Action:
Severity: Critical.
CIOD0119 x
SNMP trap: No
CMDU x floppy disk cannot create quick test file.

Action:
Severity: Critical.
CIOD0120 x
SNMP trap: No
CMDU x hard disk cannot create quick test file.

Action:
Severity: Critical.
CIOD0121 x
SNMP trap: No
CMDU x hard disk input buffer malloc err: quick test.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 623 of 2360

CIOD0122 x
CMDU x floppy disk input buffer malloc err: quick test.

Action:
Severity: Critical.
CIOD0123 x
SNMP trap: No
CMDU x is disabled due to fault monitoring.

Action: Test and, if necessary, replace the CMDU.
Severity: Critical.
CIOD0124 x
SNMP trap: Yes
CMDU x is disabled because IOP to IOP cable loss.

Action: Check both ends of the cable.
Severity: Critical.
CIOD0125 x
SNMP trap: Yes
CMDU x is disabled because the IOP is disabled.

Action: Re-enable the IOP from LD 137 (ENL IOP, ENLT)
Severity: Critical.
CIOD0126 x
SNMP trap: Yes
CMDU x is disabled. Active CP cannot access Standby CMDU because

system is in split mode.
Action:
Severity: Critical.
CIOD0128
SNMP trap: Yes
CMDU x disabled because of a hardware/software mismatch.

Action: Re-enable CMDU from LD 137.
Severity: Critical.
CIOD0129 x
SNMP trap: Yes
CMDU x disabled because it could not access the hard disk. Be sure CMDU
power is on.
Action: Check both ends of the IOP to CMDU SCSI cable.
Severity: Critical.
CIOD0130 x
SNMP trap: Yes
CMDU x disabled because of a software mismatch.

Action: Re-enable CMDU from OVL 137 (ENL CMDU 0/1).
Severity: Critical.
SNMP trap: Yes
System Messages
Page 624 of 2360

CIOD0131 x
CMDU x restored to standby because the IOP was enabled.

Action:
Severity: Critical.
CIOD0132 x
SNMP trap: Yes
CMDU x restored to active because the IOP was enabled.

Action:
Severity: Critical.
CIOD0133 x
SNMP trap: Yes
CMDU x restored to standby.

Action:
Severity: Critical.
CIOD0134 x
SNMP trap: Yes
CMDU x restored to active.

Action:
Severity: Critical.
CIOD0135 x
SNMP trap: Yes
CMDU x is standby due to switchover.

Action:
Severity: Critical.
CIOD0136 x
SNMP trap: Yes
CMDU x is active due to switchover.

Action:
Severity: Critical.
CIOD0137 x
SNMP trap: Yes
CMDU x is standby due to warm start.

Action:
Severity: Critical.
CIOD0138 x
SNMP trap: Yes
CMDU x is active due to warm start.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 625 of 2360

CIOD0139 x
CMDU x is standby due to cold start.

Action:
Severity: Critical.
CIOD0140 x
SNMP trap: No
CMDU x is active due to cold start.

Action:
Severity: Critical.
CIOD0141 x
SNMP trap: No
CMDU x is disabled because it cannot access the hard disk due to cold start.
Action: Be sure CMDU power is on, and cables are in place.
Severity: Critical.
CIOD0142 x
SNMP trap: Yes
CMDU x is disabled because it cannot access the hard disk due to warm start.
Severity: Critical.
CIOD0143 x
SNMP trap: Yes
CMDU x is disabled because it cannot access the hard disk due to switchover.
Severity: Critical.
CIOD0144 x
SNMP trap: Yes
CMDU x is active due to cold start (was on standby).

Action:
Severity: Critical.
CIOD0145 x
SNMP trap: Yes
CMDU x is active due to warm start (was on standby).

Action:
Severity: Critical.
CIOD0146 x
SNMP trap: Yes
CMDU x is active due to switchover (was on standby).

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 626 of 2360

CIOD0147 x
CMDU x is active due to fault monitoring (was on standby).

Action:
Severity: Critical.
CIOD0148 x
SNMP trap: Yes
CMDU x is disabled because system cold started in split mode.

Action:
Severity: Critical.
CIOD0149 x
SNMP trap: Yes
CMDU x is disabled because system warm started in split mode.

Action:
Severity: Critical.
CIOD0150 x
SNMP trap: Yes
CMDU x is disabled because system has switched over into split mode.
Action:
Severity: Critical.
CIOD0151 x
SNMP trap: Yes
Cannot restore CMDU x to standby state because system is in split mode.

Action:
Severity: Critical.
CIOD0152 x
SNMP trap: Yes
Cannot restore CMDU x to active state because system is in split mode.

Action:
Severity: Critical.
CIOD0153 x
SNMP trap: Yes
CMDU x active due to IOP enabling (was standby).

Action:
Severity: Critical.
CIOD0154 x
SNMP trap: Yes
CMDU x active due to SCSI cable reconnection (was on standby).

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 627 of 2360

CIOD0155
Both CMDU hard disks are inaccessible

Action: Be sure the CMDU power is on, and cables are in place.
Severity: Critical.
CIOD0156
SNMP trap: Yes
CMDU x became active (was standby).

Action:
Severity: Critical.
CIOD0157
SNMP trap: Yes
INFO: CMDU "a" is ACTIVE, RDUN is "b".

Action:
Severity: Info.
CIOD0158
SNMP trap: Yes
CMDU x DISABLED: cannot access hard disk (warm start).

Action: Check if CMDU plugged in and powered up.
Severity: Critical.
CIOD0159
SNMP trap: Yes
CMDU x DISABLED: cannot access hard disk (cold start).

Severity: Critical.
CIOD0160
SNMP trap: Yes
CMDU was removed: automatically disabled.

Action:
Severity: Critical.
CIOD0161
SNMP trap: Yes
CMDU still disabled since it is not plugged in.

Action:
Severity: Critical.
CIOD0162
SNMP trap: Yes
CMDU x hdisk inaccessible: cannot restore to ACTIVE.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 628 of 2360

CIOD0163
CMDU reinserted: but disabled since IOP disabled.

Action:
Severity: Critical.
CIOD0164
SNMP trap: Yes
Cluster number beyond normal range: {clustNum} {filename}

Severity: Minor.
CIOD0165
SNMP trap: Yes
Cluster incorrectly terminated: {clustNum} {filename}

Severity: Minor.
CIOD0166
SNMP trap: Yes
Cluster multiply assigned: {filename}

Action:
Severity: Minor.
CIOD0167
SNMP trap: Yes
File size longer than cluster chain: {fileName}

Action:
Severity: Minor.
CIOD0168
SNMP trap: Yes
Clusters lost in the FAT = {no of lostClusters}

Action:
Severity: Minor.
CIOD0169
SNMP trap: Yes
Illegal file name {oldName}, renamed as {newName}

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 629 of 2360

CIOD0174
Directory . is corrupted. Please replace the removable media if it is corrupted.

Otherwise REINSTALL SOFTWARE on the hard disk after using TOOLS
MENU to INITIALIZE Unprotected Partition.
Action: Check the removable media for corruption and replace it if found
corrupted. Else, initialize unprotected partition using tools menu and reinstall
software.
Severity: Major.
CIOD0203
SNMP trap: Yes
Customer ID number mismatch.

Action: Be sure the correct security cartridge is on the IOP.
Severity: Critical.
CIOD0204
SNMP trap: Yes
Machine type mismatch.

Severity: Critical.
CIOD0205
SNMP trap: Yes
System type or version number mismatch.

Severity: Critical.
CIOD0206
SNMP trap: Yes
System issue number mismatch.

Severity: Critical.
CIOD0207
SNMP trap: Yes
Security cartridge data not valid.

Action:
Severity: Critical.
CIOD0208
SNMP trap: No
Failed to read security cartridge.

Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 630 of 2360

CIOD0209
Mismatch between CP/x Card and Software.

Action:
Severity: Major.
CIOD0300
SNMP trap: Yes
No IOP object can be created during HI OBJ creation phase.

Action:
Severity: Critical.
CIOD0301 x y
SNMP trap: No
IOP x in slot y is not responding.

Action: Be sure IOP is enabled. Reseat or replace IOP if necessary.
Severity: Critical.
CIOD0302 x y
SNMP trap: No
IOP x in slot y detects both CMDUs becoming inaccessible.

Action: Check both ends of the IOP to IOP cables. Check both CMDUs.
Severity: Critical.
CIOD0303
SNMP trap: Yes
IOP x in slot y detects either or both CMDUs becoming inaccessible.

Action:
Severity: Critical.
CIOD0305
SNMP trap: Yes
IOP x in slot y fails SCSI controller test.

Severity: Critical.
CIOD0306
SNMP trap: Yes
IOP x in slot y fails to program/enable IOP BIC window.

Severity: Critical.
CIOD0307
SNMP trap: Yes
IOP x in slot y cannot send message to IOP card.

Action: Reinitialize system with manual INIT button.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 631 of 2360

CIOD0308
IOP x in slot y space manager cannot allocate CSR address.

Severity: Critical.
CIOD0309
SNMP trap: Yes
IOP cannot write to IOP database file.

Action: Check CMDU power.
Severity: Critical.
CIOD0310
SNMP trap: Yes
IOP cannot create binary semaphore for IP.

Action:
Severity: Critical.
CIOD0311
SNMP trap: No
IOP cannot create IOP class.

Action:
Severity: Critical.
CIOD0312
SNMP trap: No
IOP x in slot y cannot be created.

Action:
Severity: Critical.
CIOD0313
SNMP trap: No
IOP x in slot y cannot enable IOP.

Action:
Severity: Critical.
CIOD0314 x
SNMP trap: Yes
IOP Cannot open x database file.

Action:
Severity: Critical.
CIOD0315 x
SNMP trap: Yes
IOP x database file is empty.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 632 of 2360

CIOD0316 x
IOP release number is not found in x database file.

Severity: Critical.
CIOD0317 x y
SNMP trap: Yes
IOP x in slot y security cartridge test failed.

Action: Reseat or replace security cartridge.
Severity: Critical.
CIOD0318 x y
SNMP trap: No
IOP x in slot y fails to take SCSI low level semaphore.

Action:
Severity: Critical.
CIOD0319 x y
SNMP trap: No
IOP x in slot y fails to give SCSI low level semaphore.

Action:
Severity: Critical.
CIOD0320 x y
SNMP trap: No
IOP x in slot y fails to take SCSI high level semaphore.

Action:
Severity: Critical.
CIOD0321 x y
SNMP trap: No
IOP x in slot y fails to give SCSI high level semaphore.

Action:
Severity: Critical.
CIOD0322 x y
SNMP trap: No
IOP x in slot y timeout waiting for response from control register test.
Severity: Critical.
CIOD0323 x y
SNMP trap: No
IOP x in slot y BIC test failed.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 633 of 2360

CIOD0324 x y
IOP x in slot y timeout waiting for response from BIC test.

Severity: Critical.
CIOD0325 x y
SNMP trap: No
IOP switchover graceful call failed with retCode n.

Action:
Severity: Critical.
CIOD0339 x y
SNMP trap: No
IOP x in slot y SCSI cable test failed.

Action: Check software. Check both ends of the IOP to IOP SCSI cable and both
cDMUs.
Severity: Critical.
CIOD0341 x y
SNMP trap: Yes
IOP x in slot y fails to get IOP general register.

Severity: Critical.
CIOD0343 x y
SNMP trap: Yes
IOP x in slot y fails to get general register.

Severity: Critical.
CIOD0344 x y
SNMP trap: Yes
IOP x in slot y fails to set IPB/Local T/O, EI mapping, TOC or Arb ID.
Severity: Critical.
CIOD0346 x y
SNMP trap: Yes
IOP x in slot y fails to read BIC card ID.

Severity: Critical.
CIOD0347 x y
SNMP trap: Yes
IOP x in slot y space manager cannot allocate IPB address.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 634 of 2360

CIOD0348 x y
IOP x in slot y fails to program SCSI controller.

Action: Check software.
Severity: Critical.
CIOD0349 x y
SNMP trap: Yes
IOP x in slot y installing event interrupt ISR failure on CP.

Action:
Severity: Critical.
CIOD0350 x y
SNMP trap: Yes
IOP x in slot y control register test failed.

Action: Rerun test and replace IOP if test fails again.
Severity: Critical.
CIOD0351 x y
SNMP trap: Yes
IOP x in slot y timeout waiting for response from security cartridge test.
Action: Replace or reseat security cartridge/dongle on IOP/IODU.
Severity: Critical.
CIOD0352 x y
SNMP trap: Yes
IOP x in slot y i timeout waiting for response from SCSI control test.
Action: Be sure IOP is enabled.
Severity: Critical.
CIOD0353 x y
SNMP trap: Yes
IOP x in slot y timeout waiting for response from SCSI cable test.
Action: Check both ends of the IOP to IOP cable.
Severity: Critical.
CIOD0354
SNMP trap: Yes
Hunt: Illegal response from IOP to ping test message.

Action:
Severity: Critical.
CIOD0355
SNMP trap: No
Hunt: No response from IOP to ping test message.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 635 of 2360

CIOD0356
Hunt: Recognized IOP did not complete self-test.

Action:
Severity: Critical.
CIOD0357
SNMP trap: No
Hunt: Recognized IOP failed self-test.

Action:
Severity: Critical.
CIOD0358
SNMP trap: No
Hunt: IOP x y did not pass self-test.

Action:
Severity: Critical.
CIOD0359
SNMP trap: No
Hunt: IOP x y failed ping test.

Action:
Severity: Critical.
CIOD0360
SNMP trap: No
Hunt: No IOPs recognized on side x.

Action:
Severity: Critical.
CIOD0361
SNMP trap: No
IOP x in slot y: detects CMDU becoming accessible.

Action:
Severity: Critical.
CIOD0362
SNMP trap: Yes
IOP x in slot y: detects CMDU becoming inaccessible.

Action: Check CMDU for proper backplane seating.
Severity: Critical.
CIOD0363
SNMP trap: Yes
Ethernet has been restored to ACTIVE because the IOP is enabled.

Action: Information only. If this message appears repeatedly, or is associated
with a system problem, contact your local support group.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 636 of 2360

CIOD0364
Ethernet has been disabled because the IOP is disabled.

Action: Information only if the IOP is manually disabled. If a manual disable has
not been done, investigate why the IOP is disabled.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 637 of 2360
CLKC: Clock Controller

Messages
CLKC0001
This vintage of clock controller hardware does not support the FDL option.
Action:
Severity: Minor.
CLKC0002
SNMP trap: No
Warning: This vintage of clock controller hardware does not support the FULL
option.
Action:
Severity: Minor.
CLKC0003
SNMP trap: No
Invalid RST CC command for this vintage of clock controller hardware. This
command is only supported for the CLKC card.
Action:
Severity: Minor.
CLKC0004
SNMP trap: Yes
Invalid SEFT CC command for this vintage of clock controller hardware. This
Action:
Severity: Minor.
CLKC0005
SNMP trap: Yes
Invalid IDC command for this vintage of clock controller hardware. This
Action:
Severity: Minor.
CLKC0006
SNMP trap: Yes
CLKC card is not operational. Cannot read IDC information.

Action: Enable the card and try again.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 638 of 2360

CLKC0007
CLKC card is not operational. Cannot read full status from the card.
Action: Enable the card and try again.
Severity: Minor.
CLKC0008
SNMP trap: Yes
The command entered required that information be read from or write to a

CLKC card. The specified CLKC card is not present in the system, or the
(address) switch settings do not agree with the database.
Action:
Severity: Critical.
CLKC0009
SNMP trap: Yes
Cannot reset (or execute self-tests) on the card right now since the device
enabled bit is set, meaning a message response is currently pending.
Action: Attempt the self test command again; when the response pending
condition clears, as long as the card is Manually Disabled, the reset (and self
tests) should execute.
Severity: Minor.
CLKC0010
SNMP trap: Yes
Cannot reset (or execute self tests) on the card because the card is not in
manually disabled state.
Action: Disable the card and try again.
Severity: Minor.
CLKC0011
SNMP trap: Yes
Time out waiting for the self tests to complete.

Action: Wait at least five minutes, then try again. Under certain unusual
circumstances, self tests can take approximately five minutes; however, this
should only occur when the flash EPROM on the card is new of has been
completely erased.
Severity: Critical.
CLKC0012
SNMP trap: Yes
The CLKC card was removed from its slot, or the card reset itself during the
self-tests.
Action: If the card was removed, execute the self-tests again and do not remove
the card from its slot until the tests are complete. If the card was not removed,
execute the self-tests again. If this message appears more than twice, replace the
CLKC card.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 639 of 2360

CLKC0013
MSDL functionality for CLKC (NTRB53) card did not get disabled.
Action:
Severity: Minor.
CLKC0015
SNMP trap: Yes
The number of parameters for the Clock Controller command is incorrect.

Action:
Severity: Info.
CLKC0016
SNMP trap: Yes
The card number in the command is out-of-range or invalid.

Action:
Severity: Info.
CLKC0017
SNMP trap: Yes
Cannot enable the card unless it is in Manually Disabled (MAN DSBL)

state.
Action:
Severity: Minor.
CLKC0018
SNMP trap: Yes
Cannot disable card unless it is in the Enabled (ENBL) state.

Action:
Severity: Minor.
CLKC0019
SNMP trap: Yes
No response received to the enable card command.

Action:
Severity: Minor.
CLKC0020
SNMP trap: Yes
The response message from the card to the Overlay indicates failure to
enable/disable.
Action:
Severity: Critical.
CLKC0021
SNMP trap: Yes
No response received to the disable card command. The card is set to the
Manually Disabled (MAN DSBL) state anyway.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 640 of 2360

CLKC0022
The command entered requires that a message be sent to the CLKC card.
The Meridian 1 was unable to build the message since the buffer was not
free. Try again later. If this message continues to be generated, continue with
the Action.
Action: If the card is enabled, wait for a few minutes, as the card may have
encountered a problem that warrants recovery, or if the card
is manually disabled, reset the card using the RST CC x command in OVL 60, or
execute self tests using the SEFT CC x command in OVL60.
Severity: Minor.
CLKC0023
SNMP trap: Yes
Failed enable attempt. If this message is not accompanied by any other error
message, the card may be in the process of performing self-tests or the
self-tests may have already failed.
Action: Wait a few minutes, then execute the self-tests with the SLFT MSDL x
command. If self-tests pass, try to enable the card again.
Severity: Critical.
CLKC0024
SNMP trap: Yes
The fourth parameter of the command is unrecognized or unimplemented.

Action:
Severity: Minor.
CLKC0025
SNMP trap: Yes
Began to download the CLKC basecode but stopped before finishing. There
should be an accompanying SDL error message, so refer to the information on
that message for the failure reason.
Action:
Severity: Critical.
CLKC0026
SNMP trap: Yes
Cannot enable the card because it is not present in the system.

Action: If the card in question is believed to be present, check if
the switch settings on the card agree with the device number entered in this
command.
Severity: Minor.
CLKC0027
SNMP trap: Yes
Unable to allocate data space for CLKC related MSDL structure.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 641 of 2360

CLKC0028
Bank 0 of the CLKC loadware is used for the Clock Controller card.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 642 of 2360
553-3001-411
Standard 15.00
January 2006
Page 643 of 2360
CMON: Core Monitor

The message output format is: CMON x y z, where x = side, y = card and z =
port.
Messages
CMON0400 x y z m The mask value of the CNI port on core side x, slot y, port z, mask m does not
match the software image. The hardware image is being restored.
Action:
Severity: Critical.
CMON0401
SNMP trap: No
CNI intermittent interrupt occurring.

Action:
Severity: Minor.
CMON0402 x y z
SNMP trap: No
Core side x, slot y, port z cable 1 is detected. The system is putting it into
Normal mode.
Action:
Severity: Minor.
CMON0403 x y z
SNMP trap: No
Core side x, slot y, port z cable 1 is lost. The system is putting it into Disabled
mode.
Action:
Severity: Critical.
CMON0404 x y z
SNMP trap: No
Core side x, slot y, port z cable 2 is detected. The system is putting it into
Normal mode.
Action:
Severity: Minor.
CMON0405 x y z
SNMP trap: No
Core side x, slot y, port z cable 2 is lost. The system is putting it into Disabled
mode.
Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 644 of 2360

CMON0406 x y z
Core side x, slot y, port z remote power is detected. The system is putting it
into Normal mode.
Action:
Severity: Minor.
CMON0407 x y z
SNMP trap: No
Core side x, slot y, port z remote power is lost. The system is putting it into
Disabled mode.
Action:
Severity: Critical.
CMON0408 x y z
SNMP trap: No
Core side x, slot y, port z 3PE physical switch is enabled. The system is putting
it into Normal mode.
Action:
Severity: Minor.
CMON0409 x y z
SNMP trap: No
Core side x, slot y, port z 3PE physical switch is disabled. The system is
putting it into Disabled mode.
Action:
Severity: Critical.
CMON0410 x y z
SNMP trap: No
An event interrupt has been lost on core side x, slot y, port z.

Action:
Severity: Minor.
CMON0411 x y
SNMP trap: No
Core side x, slot y CNI physical switch is enabled. The system is putting it into
Normal mode.
Action:
Severity: Minor.
CMON0412 x y
SNMP trap: No
Core side x, slot y CNI physical switch is disabled. The system is putting it into
Disabled mode.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 645 of 2360
CND: Caller's Name Display

The Caller's Name Display Feature allows the storage of the users names in
an Auxiliary computer such as a Property Management System (PMS).
Problems with the link to the PMS are indicated by CND messages.
Messages
CND0000
Program Identifier
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 646 of 2360
553-3001-411
Standard 15.00
January 2006
Page 647 of 2360
CNF: Conference Circuit Diagnostic (LD

38)
The Conference Circuit Diagnostic program is used to detect and isolate circuit
faults on the system conferencing equipment. The CNF messages are output
in response to commands issued in LD 38.
LD 38 can detect problems on conference circuits such as:
channel faults on the network card which interfaces a conference card to the
system
channel faults on the conference card
conference faults associated with conferee group numbers
switching faults controlling the attenuation feature
The program is used to:
Check the status of the channels and the conferee groups.
Clear alarms and displays.
Messages
CNF0000
Program Identifier
Action:
Severity: Minor.
CNF0001
SNMP trap: No
Invalid command.
Action: Check command format and try again.
Severity: Minor.
CNF0002
SNMP trap: Yes
Invalid argument.
Action: Check command format and try again.
Severity: Minor.
CNF0004
SNMP trap: Yes
Loop or conferee group out-of-range. Loop range is 0 to 158; conferee group

range is 1 to 15.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 648 of 2360

CNF0006
Requested loop is not defined in the system or is not a conference group.

Action: Check data and begin again.
Severity: Minor.
CNF0007
SNMP trap: Yes
Requested loop has been disabled.

Action: Use ENLL command before going further.
Severity: Minor.
CNF0008
SNMP trap: Yes
Requested conference loop is in use.

Action: Try another conference loop.
Severity: Minor.
CNF0009
SNMP trap: Yes
The CNFC STEP command requires a two-party conference. More or fewer

sets are not allowed.
Action: Ensure that only two sets are in conference. If not, use END command
to cancel the conference. Use the CNFC MAN L C command to set up two
manual conferences by dialing SPRE 93 on any two sets, where SPRE is the
customer's Special Service Prefix code.
Severity: Minor.
CNF0020 loop
SNMP trap: Yes
Conference pack failed to respond.

Action: Check enable switch on the pack. If pack still does not respond, it is
probably due to a fault on Conference pack. If fault persists after pack is replaced,
suspect Peripheral Signaling packs. Minor alarm lamp lit on Attendant Console.
Severity: Critical.
CNF0021 loop
SNMP trap: Yes
Channel fault found on Conference pack. Minor alarm lamp lit on Attendant
Console.
Action:
Severity: Critical.
CNF0022 loop
SNMP trap: Yes
Channel fault found on conference pack. Minor alarm lamp lit on Attendant
Console.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 649 of 2360

CNF0023 loop
Conference fault found with one or more conferee groups on conference pack.
May also be faulty network pack. Minor alarm lamp lit on Attendant Console.
Action:
Severity: Critical.
CNF0025 loop
SNMP trap: Yes
Listen-only feature is not working on conference pack. Minor alarm lamp lit on
Attendant Console.
Action:
Severity: Critical.
CNF0026
SNMP trap: Yes
Attenuation level 12.2 dB is faulty.

Action:
Severity: Critical.
CNF0027
SNMP trap: Yes

Action:
Severity: Critical.
CNF0028
SNMP trap: Yes

Action:
Severity: Critical.
CNF0029
SNMP trap: Yes

Action:
Severity: Critical.
CNF0030
SNMP trap: Yes

Action:
Severity: Critical.
CNF0031
SNMP trap: Yes

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 650 of 2360

CNF0032

Action:
Severity: Critical.
CNF0033
SNMP trap: Yes
TSM memory faulty. The pack is faulty and should be replaced.

Action:
Severity: Critical.
CNF0100
SNMP trap: Yes
Cannot use the ENLX (Enable) or DISX (Disable) commands on a non-XCT

card.
Action:
Severity: Minor.
CNF0101
SNMP trap: Yes
The XCT card is already enabled/disabled.

Action:
Severity: Minor.
CNF0102
SNMP trap: Yes
On ENLX (enable Conference/TDS card) did not receive the message

verifying download completion within six seconds.
Action:
Severity: Info.
CNF0103
SNMP trap: Yes
CNFC L did not receive the self test result within ten seconds.
Action:
Severity: Minor.
CNF0104
SNMP trap: Yes
Received an unexpected message from the Conference/TDS card.

Action: Use the DISX command to disable the card and retry the ENLX
command.
Severity: Minor.
CNF0107
SNMP trap: Yes
Superloop numbers must be a multiple of four.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 651 of 2360

CNF0108
Shelf parameter is out-of-range.

Action:
Severity: Minor.
CNF0109
SNMP trap: Yes
Card parameter is out-of-range.

Action:
Severity: Minor.
CNF0110
SNMP trap: Yes
Unit parameter is out-of-range.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 652 of 2360
553-3001-411
Standard 15.00
January 2006
Page 653 of 2360
CNI: Core to Network Interface

The message output format is: CNI x y z, where x = side, y = card, and z =
pfsort
Messages
CNI0000 x y z
CNIP x y z: Intermittent interrupt occurring.

Action:
Severity: Minor.
CNI0001 x y z
SNMP trap: No
CNIP x y z: CNI-3PE cable 1 (top) detected.

Action:
Severity: Minor.
CNI0002 x y z
SNMP trap: Yes
CNIP x y z: CNI-3PE cable 1 (top) lost.

Action: Check both connectors.
Severity: Critical.
CNI0003 x y z
SNMP trap: Yes
CNIP x y z: CNI-3PE cable 2 (bottom) detected.

Action:
Severity: Minor.
CNI0004 x y z
SNMP trap: Yes
CNIP x y z: CNI-3PE cable 2 (bottom) lost.

Action: Check both connector ends of the cable.
Severity: Critical.
CNI0005 x y z
SNMP trap: Yes
CNIP x y z: Remote power (3PE) detected.

Action:
Severity: Minor.
CNI0006 x y z
SNMP trap: Yes
CNIP x y z: Remote power (3PE) lost.

Action: Check Network power or cables for cross connections.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 654 of 2360

CNI0007 x y z
CNIP x y z: 3PE switch has been enabled.

Action: Check 3PE switch or cables for cross connections.
Severity: Critical.
CNI0009 x y z
SNMP trap: Yes
CNIP x y z: Event interrupt lost. Mask REG = n. Re-enabling all interrupts.

Action:
Severity: Critical.
CNI0010 x y z
SNMP trap: Yes
CNIP x y z: Faceplate switch enabled.

Action:
Severity: Minor.
CNI0012 x y z
SNMP trap: Yes
CNIP x y z: Putting port into Disabled mode.

** Warning: Attached group will be Out-of-Service **
Action:
Severity: Critical.
CNI0013 x y z
SNMP trap: No
CNIP x y z: Putting port into Normal/Enabled mode.

Action:
Severity: Minor.
CNI0016
SNMP trap: No
CNI-3PE cable detected.

Action:
Severity: Info.
CNI0020 x y z
SNMP trap: No
CNIP x y z: Failure to change port mode.

Action:
Severity: Minor.
CNI0050
SNMP trap: Yes
CNIP x y z: Failure to access CNI port hardware.

Action: Check CNI Enable/Disable switch, or replace CNI card.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 655 of 2360

CNI0051
CNIP x y z: Failure to unmask event interrupt.

Action:
Severity: Critical.
CNI0052 x
SNMP trap: Yes
CNIP x y z: Mask x does not match. Interrupt being unmasked.

Action:
Severity: Critical.
CNI0053 x
SNMP trap: Yes
CNIP x y z: Mask x does not match. Interrupt being masked.

Action:
Severity: Critical.
CNI0054
SNMP trap: Yes
CNIP x y z: Could not find the source of the interrupt.

Action:
Severity: Critical.
CNI0055 l s c
SNMP trap: Yes
CNIP x y z: Testing port l s c u.

Action:
Severity: Minor.
CNI0056
SNMP trap: Yes
CNIP x y z: Interrupt line x is stuck. Unmasking line.

Action:
Severity: Critical.
CNI0061v w x y z
SNMP trap: Yes
CNIP x y z: LBA = v, LBD = w, BERZ = x, CR = y, SR = z

Action:
Severity: Critical.
CNI0062
SNMP trap: No
CNIP x y z: The remote device is not accessible.

Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 656 of 2360

CNI0065
CNIPMon: - EILOST reported, mask = n.

Action: Turn on "cnipMaskAutoRestore" to recover.
Severity: Critical.
CNI0066
SNMP trap: No
CNIP Mon - Switchover requested; side x is deemed better.

Action: Check hardware or ENL disabled hardware or suspect side.
Severity: Critical.
CNI0070
SNMP trap: Yes
CNIP x y z: EI x register does not match. SW = n, HW = m. Restoring.

Action:
Severity: Critical.
CNI0071
SNMP trap: No
EI Unmasking line x failed. Mask Reg = n.

Action:
Severity: Critical.
CNI0073
SNMP trap: No
CNIP x y z: Maintenance Interrupt Threshold exceeded. Subsequent changes

in 3PE/cable status will be ignored.
Action: Check 3PE and CNI-3PE cable (if applicable) then re-enable CNI.
Severity: Critical.
CNI0074
SNMP trap: Yes
CNIP x y z: EI3 address repaired. EI3 address was set to: a. EI3 address
restored to: b.
Action:
Severity: Critical.
CNI0075
SNMP trap: Yes
CNIP x y z: cause for EI3 event unknown. Forcing the port into NORMAL
mode.
Action:
Severity: Critical.
CNI0200 x
SNMP trap: No
CNI card configured but not present in slot x. Database mismatch.

Action: Be sure the card is in the correct slot.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 657 of 2360

CNI0201
CNI x y : Watchdog timeout detected count = n.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 658 of 2360
553-3001-411
Standard 15.00
January 2006
Page 659 of 2360
COM: Data Communication

Messages
COM0000
Network interface driver: Device unit %d is initialized OK.

Action:
Severity: Info.
COM0001
SNMP trap: No
Network interface driver: Unit %d is being restarted.

Action:
Severity: Critical.
COM0002
SNMP trap: Yes
Network interface driver is unable to restart the broadcast threshold watchdog.

Action:
Severity: Major.
COM0003
SNMP trap: Yes
Network interface driver is temporarily shut-down due to excess broadcasts.

Action:
Severity: Major.
COM0004
SNMP trap: Yes
Network interface driver: Restarted after being shut-down (broadcast).

Action:
Severity: Info.
COM0005
SNMP trap: Yes
Network interface driver: Inattatch; error return from giaIntSet call.

Action:
Severity: Major.
COM0006
SNMP trap: Yes
Network interface driver: Device unit %d initialization failed.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 660 of 2360

COM0007
Network interface driver: No carrier detection on device unit %d.

Action:
Severity: Critical.
COM0008
SNMP trap: Yes
Network interface driver: Unit %d is being reset.

Action:
Severity: Info.
COM0009
SNMP trap: No
Network interface driver: A fatal problem was encountered and the threshold
has been reached. Attempt to switch-over form side %d.
Action:
Severity: Major.
COM0010
SNMP trap: Yes
Network interface driver: Error creating transmitter semaphore.

Action:
Severity: Major.
COM0011
SNMP trap: Yes
Network interface driver: Inattach; insufficient memory provided.

Action:
Severity: Major.
COM0012
SNMP trap: Yes
Network interface driver: Device requires cache coherent memory.

Action:
Severity: Major.
COM0013
SNMP trap: Yes
Network interface driver: System memory unavailable.

Action:
Severity: Major.
COM0014
SNMP trap: Yes
Network interface driver: Unable to create broadcast threshold.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 661 of 2360

COM0015
Network interface driver: Unable to switch-over.

Action:
Severity: Major.
COM0016
SNMP trap: Yes
Point-to-Point Protocol: Session is up.

Action:
Severity: Info.
COM0017
SNMP trap: Yes
Point-to-Point Protocol: Session is down.

Action:
Severity: Info.
COM0018
SNMP trap: Yes
Point-to-Point Protocol: Echo failed, link is down.

Action:
Severity: Info.
COM0040
SNMP trap: Yes
100 Base T driver: broadcast Restart on port x, where x is the port number
Action:
Severity: Info.
COM0041
SNMP trap: Yes
100 Base T driver: Broadcast storm on port x, where x is the port number
Action:
Severity: Info.
COM0062
SNMP trap: Yes
10 BaseT driver: Broadcast storm, broadcast messages being rejected.

Action:
Severity: Info.
COM0063
SNMP trap: Yes
10 BaseT driver: Broadcast messages being accepted.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 662 of 2360

COM0064
10 BaseT driver: Receiving Unicast messages faster than threshold limit. Last
source IP address: xx
Action:
Severity: Minor.
COM0065
SNMP trap: No
Ethernet Driver : Timeout occured in lnInit( ) for unit %d ,chip initialisation

failed.
Action: Contact Technical Support if problem persists
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 663 of 2360
CRI: Carrier Remote IPE

Messages
CRI1005
SUPL XXX Local Carrier 0 Alarm Level 0 OK

Action:
Severity: Info.
CRI1006
SNMP trap: Yes
SUPL XXX Carrier 0 MMI enabled

Action:
Severity: Info.
CRI1010
SNMP trap: No
SUPL XXX Local Carrier 0 Alarm Level 1 B.E.R. Exceeded

Action:
Severity: Info.
CRI1020
SNMP trap: Yes

Action:
Severity: Info.
CRI1030
SNMP trap: Yes

Action:
Severity: Info.
CRI1031
SNMP trap: Yes
SUPL XXX Local Carrier 0 Alarm Level 3 Frame Slip THRSH Exceeded
Action:
Severity: Info.
CRI1032
SNMP trap: Yes
SUPL XXX Local Carrier 0 Alarm Level 3 Loss of Signal

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 664 of 2360

CRI1033
SUPL XXX Local Carrier 0 Alarm Level 3 Blue Alarm

Action:
Severity: Info.
CRI1034
SNMP trap: Yes
SUPL XXX Local Carrier 0 Alarm Level 3 Out of Frame

Action:
Severity: Info.
CRI1036
SNMP trap: Yes
SUPL XXX Carrier 0 MMI disabled

Action:
Severity: Info.
CRI1105
SNMP trap: Yes

Action:
Severity: Info.
CRI1106
SNMP trap: Yes

Action:
Severity: Info.
CRI1110
SNMP trap: Yes

Action:
Severity: Info.
CRI1120
SNMP trap: Yes

Action:
Severity: Info.
CRI1130
SNMP trap: Yes

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 665 of 2360

CRI1131
Action:
Severity: Info.
CRI1132
SNMP trap: Yes

Action:
Severity: Info.
CRI1133
SNMP trap: Yes

Action:
Severity: Info.
CRI1134
SNMP trap: Yes

Action:
Severity: Info.
CRI1136
SNMP trap: Yes

Action:
Severity: Info.
CRI1205
SNMP trap: Yes

Action:
Severity: Info.
CRI1206
SNMP trap: Yes

Action:
Severity: Info.
CRI1210
SNMP trap: Yes

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 666 of 2360

CRI1220

Action:
Severity: Info.
CRI1230
SNMP trap: Yes

Action:
Severity: Info.
CRI1231
SNMP trap: Yes
Action:
Severity: Info.
CRI1232
SNMP trap: Yes

Action:
Severity: Info.
CRI1233
SNMP trap: Yes

Action:
Severity: Info.
CRI1234
SNMP trap: Yes

Action:
Severity: Info.
CRI1236
SNMP trap: Yes

Action:
Severity: Info.
CRI2005
SNMP trap: Yes
SUPL XXX Remote Carrier 0 Alarm Level 0 OK

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 667 of 2360

CRI2010
SUPL XXX Remote Carrier 0 Alarm Level 1 B.E.R. Exceeded

Action:
Severity: Info.
CRI2020
SNMP trap: Yes

Action:
Severity: Info.
CRI2030
SNMP trap: Yes

Action:
Severity: Info.
CRI2031
SNMP trap: Yes
SUPL XXX Remote Carrier 0 Alarm Level 3 Frame Slip THRSH Exceeded
Action:
Severity: Info.
CRI2032
SNMP trap: Yes
SUPL XXX Remote Carrier 0 Alarm Level 3 Loss of Signal

Action:
Severity: Info.
CRI2033
SNMP trap: Yes
SUPL XXX Remote Carrier 0 Alarm Level 3 Blue Alarm

Action:
Severity: Info.
CRI2034
SNMP trap: Yes
SUPL XXX Remote Carrier 0 Alarm Level 3 Out of Frame

Action:
Severity: Info.
CRI2105
SNMP trap: Yes

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 668 of 2360

CRI2110

Action:
Severity: Info.
CRI2120
SNMP trap: Yes

Action:
Severity: Info.
CRI2130
SNMP trap: Yes

Action:
Severity: Info.
CRI2131
SNMP trap: Yes
Action:
Severity: Info.
CRI2132
SNMP trap: Yes

Action:
Severity: Info.
CRI2133
SNMP trap: Yes

Action:
Severity: Info.
CRI2134
SNMP trap: Yes

Action:
Severity: Info.
CRI2205
SNMP trap: Yes

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 669 of 2360

CRI2210

Action:
Severity: Info.
CRI2220
SNMP trap: Yes

Action:
Severity: Info.
CRI2230
SNMP trap: Yes

Action:
Severity: Info.
CRI2231
SNMP trap: Yes
Action:
Severity: Info.
CRI2232
SNMP trap: Yes

Action:
Severity: Info.
CRI2233
SNMP trap: Yes

Action:
Severity: Info.
CRI2234
SNMP trap: Yes

Action:
Severity: Info.
CRI3301
SNMP trap: Yes
SUPL XXX External Alarm 1 cleared

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 670 of 2360

CRI3302

Action:
Severity: Info.
CRI3303
SNMP trap: Yes

Action:
Severity: Info.
CRI3311
SNMP trap: Yes
SUPL XXX External Alarm 1 Set

Action:
Severity: Info.
CRI3312
SNMP trap: Yes

Action:
Severity: Info.
CRI3313
SNMP trap: Yes

Action:
Severity: Info.
CRI4437
SNMP trap: Yes
No response or the response was too slow (software timed out to avoid INIT
within INIT) from the carrier hardware during Carrier Remote Interface
initialization update. If the message is output again with the same loop
number,
then it is an indication that there is a hardware fault in either the LCI or RCI
card.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 671 of 2360
CSA: Command and Status Link

Diagnostic (LD 48)
The Command and Status Link is an application protocol used for
communication between the system CPU and an external Value Added Server
(VAS) such as the Meridian Mail MP. The CSL uses an Enhanced Serial Data
Interface (ESDI) card.
The CSL and ESDI are maintained by the Link Diagnostic program (LD 48).
The following messages indicate status and error conditions of the CSL
software and/or the ESDI card.
With Release 19 or later, and Alarm Filtering (ALRM_FILTER) package 243
equipped, a new expanded format is used to give system message
information. When applicable, both display formats are shown.
Messages
CSA0001 n t x
CSL n cannot be brought up automatically at system time t.

Unformatted: CSA001 N T X
Formatted: CSA001 dd/mm
OPRDAT: N X
n = CSL number
t = system time (only appears when unformatted)
x = 1. ESDI is in invalid state
2. ASIM/DLC data base error.
3. DLI data base error
4. ESDI failed the test
5. ASIM/DLC not enabled
6. DLI not enabled or is in alarm condition
7. ASIM setup failed
8. ESDI HDLC link layer setup failed
9. ESDI no response to the SL-1s command.
10. Far-end did not return the polling message.
Action:
Severity: Critical.
CSA0002 n t x
SNMP trap: Yes
CSL n is out-of-service at system time t.

Unformatted: CSA002 N T X
Formatted: CSA002 dd/mm/yy 00009 MSG
OPRDAT: N X
n = CSL number
System Messages
Page 672 of 2360

x=
1. ESDI is out-of-service
2. SL-1 DLI is out-of-service
3. Protocol fault (InfoLink)
4. Polling message time out.
5. The Layer two of MSDL is down.
6. ELAN network interface is disconnected.
Action:
Severity: Critical.
CSA0003 n t
SNMP trap: Yes
CSL n is now active, at system time t.

Unformatted: CSA003 N T
Formatted: CSA003 dd/mm/yy 00009 MSG OPRDAT: N
Action:
Severity: Minor.
CSA0004 n t
SNMP trap: Yes
CSL n is now standby, at system time t.

Unformatted: CSA004 N T
Formatted: CSA004 dd/mm/yy 00009 MSG
OPRDAT: N
n = CSL number
Action:
Severity: Minor.
CSA0005 n x y
SNMP trap: Yes
The message threshold on an ISDN/AP link n has overflowed.

Where: x = OVD message sent across the link
y = number of messages received during the last time interval.
Action:
Severity: Critical.
CSA0100 q t
553-3001-411
SNMP trap: Yes
Warning: The available Call Registers in the AML queue is down to 20 percent
of total resource.
Where: q = I for input queue or O for output queue
t = the system timestamp.
The message appears in the following formats:
CSA100 {I} {timestamp}
SYS: {#CR in System msg queue}
Standard 15.00
January 2006
Page 673 of 2360

CPI: {#CR in Call Processing msg queue}
ADM: {#CR in Admin./Maint. msg queue}
CSA100 {O} {timestamp}
AML:{link#}
S: {CR in the queue for this link}
AML: {other configured output link}
S: {...} ADM: {...} S: {...} ..
Action:
Severity: Critical.
CSA0101 q t
SNMP trap: Yes
Overflow: The available Call Registers in the AML queue is down to 0 percent
of total resource.
Where:
q = I for input queue or O for output queue
t = the system timestamp.
If there are two or more CSA100 warning messages in a week, increase the
value of CSQI and CSQO in LD 17.
CSA101 {I} {timestamp} SYS:{#CR in System msg queue}
CSA101 {0} {timestamp} AML: {link#}
S: {CR in the queue for this link}
AML:{other configured output link}
S: {...} ADM:{...} S:{...} ..
Action:
Severity: Critical.
CSA0102 q time
SNMP trap: Yes
Recover: The available call registers in the AML queue has recovered to 40%
of total resource.
q = I for input queue
q = O for output queue
time = the system timestamp
If there are two or more CSA102 overflow messages in a day for one week,
the system should be re-engineered or upgraded to a faster machine type.
CSA102 {I} {timestamp}
SYS:{#CR in System msg queue}
CSA102 {0} {timestamp}AML:{link#}
System Messages
Page 674 of 2360

S:,#CR in the queue for this link}
AML:{other configured output link}
S: {...} ADM:{...} S:{...} ..
Action:
Severity: Minor.
CSA0103
SNMP trap: Yes
PROG_CR for deacquire cannot be allocated after finished revert to default

process.
Action:
Severity: Info.
CSA0104 n a t
SNMP trap: Yes
CCR READY bit set, CCR is now Active. Where

n : Link Number
t : Time Stamp
CSA104 prints when SL-1 receives Start Up or Flow Control messages, or
after SL-1 initialized.
Action:
Severity: Critical.
CSA0105 n a t
SNMP trap: Yes
CCR READY bit reset, CCR is now Disabled. Where:

n : Link Number
t : Time Stamp
CSA105 prints when system receives Shut Down, CCR died, 10 consecutive
timeout, ESDI cable being poured, or link disabled messages, and after SL-1
initialized.
Action:
Severity: Critical.
CSA0106
553-3001-411
SNMP trap: Yes
Link congestion or slow response time detection on the Application Module

Link. Cleaning up link.
The format of CSA106 is as follows: CSA### {AML link#} {hours} {minutes}
{seconds} {o} {si} {cpi}
Where:
### = 106 or 107
AML link # = the AML link number for the application
Standard 15.00
January 2006
Page 675 of 2360

o = queue length of the AML output queue for the application
si = queue length of all AML system input queues
cpi = queue length of all AML call processing input queues
Action:
Severity: Critical.
CSA0107
SNMP trap: Yes
Link cleanup completed. This message is tied directly to last CSA106

message.
The format of CSA107 is as follows: CSA### {AML link#} {hours} {minutes}
{seconds} {o} {si} {cpi}
Where:
### = 106 or 107
AML link # = the AML link number for the application
o = queue length of the AML output queue for the application
si = queue length of all AML system input queues
Action:
Severity: Minor.
CSA0108
SNMP trap: Yes

CSA0108
This CDN is being switched to default mode because:
1. CDN is unknown to the application.
2. No call script is defined for the CDN.
The Craftperson is responsible to fix the problem and reset the CDN back to
the controlled mode if desired. The format of CSA 108 is as follows: CSA108
{CDN} {cust no} {reason code}
Where reason code = (no call script is defined for the CDN.) (undefined CD)
Action:
Severity: Critical.
CSA0109
SNMP trap: Yes
Process deacquire all is in progress

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 676 of 2360

CSA0110
The overloaded CSL MSDL port needs to be disabled before it can be

enabled.
Action: Place the AML LINK in the manually disabled mode with the command
DIS AML x. Enable the Link with the command ENL AML x.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 677 of 2360
CSC: Customer Service Change

The Customer Service Change messages indicate problems and progress
within the Attendant Administration and Automatic Set Relocation features.
Messages
CSC0001
Access code (password) entered from console was incorrect.

Action:
Severity: Minor.
CSC0002
SNMP trap: No
Cannot login because currently running program refuses to leave.

Action:
Severity: Minor.
CSC0006
SNMP trap: No
Someone else has logged in and replaced the Attendant Administration user.
Action:
Severity: Minor.
CSC0007
SNMP trap: No
An error was encountered trying to load a program.

Action:
Severity: Minor.
CSC0010 x y
SNMP trap: No
The first message produced by a relocation at the point the set leaves the
system. It gives the TN the set is relocating from, and the identification code
entered. Where : x = old TN of set and y = ID code entered
Action:
Severity: Minor.
CSC0011 x y
SNMP trap: Yes
The second message produced by a set relocation at the point the set
re-enters the system. It gives the old and new TN of the set. Where : x = old
TN (l s c u) of set and y = new TN of set.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 678 of 2360

CSC0012 x
A set cannot be relocated back in. It gives the old TN of the set. Where : x =
old TN of set.
Action:
Severity: Minor.
CSC0013 x y
SNMP trap: Yes
A set reassigned back in has been de-assigned as AST for a DN. Where : x =
TN of set and y = Prime DN of set.
Action:
Severity: Minor.
CSC0100 x y
SNMP trap: Yes
Set Installation message indicating that a set or trunk has been installed using
AINS.
Action:
Severity: Minor.
CSC0101 x
SNMP trap: Yes
Set Installation message indicating that a set or trunk has been removed from
the database using AINS.
Action:
Severity: Minor.
SNMP trap: Yes
CSC0102 DN xxxx NEW MARP l s c u The DN xxxx appearance for a MARP TN has been
changed in Attendant Administration. The new MARP for DN xxxx has
defaulted to TN l s c u.
Action:
Severity: Minor.
CSC0103
SNMP trap: No
Model set cannot be installed because ISM limit would be exceeded.

Output:
x = model used for this set
y = TN (l s c u) of this set
Action: Check ISM limits in overlay 22.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 679 of 2360

CSC0104 x y z
Flexible Call Forward No Answer DN (FDN) updated through User Selectable

Call Redirection (USCR) from telephone. Where : x = tn (l s c u), y = old FDN,
and z = new FDN.
Action:
Severity: Minor.
CSC0105 x y z
SNMP trap: Yes
Hunt DN updated through User Selectable Call Redirection (USCR) from

telephone. Where : x = tn (l s c u) , y = old Hunt DN and z = new Hunt DN
Action:
Severity: Minor.
CSC0106 x y z
SNMP trap: Yes
External Call Forward No Answer DN (EFD) updated through User Selectable

Call Redirection (USCR) from telephone. Where : x = tn (l s c u), y = old EFD,
and z = new EFD.
Action:
Severity: Minor.
CSC0107 x y z
SNMP trap: Yes
External Hunt DN (EHT) updated through User Selectable Call Redirection

(USCR) from telephone. Where : x = tn (l s c u), y = old EHT, and z = new EHT.
Action:
Severity: Minor.
CSC0108 x y z
SNMP trap: Yes
Ringing Cycle Option (RCO) updated through User Selectable Call

Redirection (USCR) from telephone. Where : x = tn (l s c u), y = old Ringing
Cycle Option (RCO), and z = new RCO.
Action:
Severity: Minor.
CSC0109 x y
SNMP trap: Yes
Unacceptable Flexible Call Forward No Answer DN (FDN) dialed during User

Selectable Call Redirection (USCR) programming from telephone. Invalid data
was not stored. Where : x = tn (l s c u) and y = unacceptable FDN.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 680 of 2360

CSC0110 x y
Unacceptable Hunt DN dialed during User Selectable Call Redirection

(USCR) programming from telephone. Invalid data was not stored. Where : x
= tn (l s c u) and y = unacceptable Hunt DN.
Action:
Severity: Minor.
CSC0111 x y
SNMP trap: Yes
Unacceptable External Call Forward No Answer DN (EFD) dialed during User

Selectable Call Redirection (USCR) programming from telephone. Invalid data
was not stored. Where : x = tn (l s c u) and y = unacceptable EFD.
Action:
Severity: Minor.
CSC0112 x y
SNMP trap: Yes
Unacceptable External Hunt DN (EHT) dialed during User Selectable Call

Redirection (USCR) programming from telephone. Invalid data was not
stored. Where : x = tn (l s c u) and y = unacceptable EHT.
Action:
Severity: Minor.
CSC0113 x y
SNMP trap: Yes
Unacceptable Ringing Cycle Option (RCO) dialed during User Selectable Call
Redirection (USCR) programming from telephone. Invalid data was not
stored. Where : x = tn (l s c u) and y = unacceptable RCO.Data corruption.
Action:
Severity: Minor.
CSC0119
SNMP trap: Yes
Virtual Office - login process of a VO worker onto a Host TN has ended

successfully.
Where:
x = TN of the Host Terminal (l s c u).
y = Virtual TN Primary DN.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 681 of 2360

CSC0120
Virtual Office - logout process of a VO worker from a Host TN has ended

successfully.
Where:
x = TN of the Host Terminal (l s c u).
y = Virtual TN Primary DN.
Action:
Severity: Info.
CSC0121
SNMP trap: Yes
Virtual Office data corruption for the Logged-Off TN: Host TN must be on a
Physical loop, and Virtual TN must be on a Phantom loop.
Where:
x = TN of the Host or Virtual Terminal (l s c u).
Action:
Severity: Info.
CSC0122
SNMP trap: Yes
Virtual Office data corruption for the Logged-In TN:

Host TN must be on a Phantom loop, and Virtual TN must be on a Physical
loop.
Where:
Action:
Severity: Info.
CSC0123
SNMP trap: Yes

Invalid VO_SOURCE_TN was found in TN.
Where:
y = VO_SOURCE_TN (Hex format).
Action:
Severity: Info.
CSC0124
SNMP trap: Yes

The VO_SOURCE_TN must be a BCS unit, and
The UNIT_SUBTYPES of both TNs must be the same M3903/M3904 type,
and
VO_SOURCE_TN must be a Host or Virtual TN, and
TN and VO_SOURCE_TN must be a pair of Virtual and Host TNs.
System Messages
Page 682 of 2360

Where:
x = TN of the Logged-in Terminal (l s c u).
y = TN of VO_SOURCE_TN (l s c u).
Action:
Severity: Info.
CSC0125
SNMP trap: Yes
Virtual Office data corruption for the Logged-In VO_SOURCE_TN:

Host TN must be on a Phantom loop, and Virtual TN must be on a Physical
loop.
Where:
y = TN of VO_SOURCE_TN (l s c u)
Action:
Severity: Info.
CSC0126
SNMP trap: Yes

The VO_SOURCE_TN must be in Logged-In state, and the VO_SOURCE_TN
must contain the original TN.
Where:
y = Original TN of VO_SOURCE_TN (l s c u).
Action:
Severity: Info.
CSC0127
SNMP trap: Yes
Virtual Office swap process failure - Invalid Host TN (VO_SWAP_HOST_TN)

was found. Swapping process is aborted.
Where:
x = VO_SWAP_HOST_TN (Hex format).
y = VO_SWAT_VIRT_TN (Hex format).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 683 of 2360

CSC0128
Virtual Office swap process failure - Invalid Virtual TN (VO_SWAP_VIRT_TN)

was found. Swapping process is aborted.
Where:
Action:
Severity: Info.
CSC0129
SNMP trap: Yes
Virtual Office swap process failure - Invalid Virtual TN (VO_SWAP_VIRT_TN)

or Host TN (VO_SWAP_HOST_TN) were found. Swapping process is
aborted.
Where:
Action:
Severity: Info.
CSC0130
SNMP trap: Yes
Virtual Office swap process warning - DNTRANS2 failure during swapping

process. Swapping process continues.cc
Where:
x = TN of the swapped Terminal (l s c u).
y = Key number.
z = DN.
Action:
Severity: Info.
CSC0131 x y z
SNMP trap: Yes
Virtual Office swap process warning - process aborted due to system initialize.
Where x = First swapped TN (l s c u); y = Second swapped TN (l s c u); z =
DN key of y.
Action:
Severity: Minor.
CSC1000 x y z
SNMP trap: Yes
Flexible Call Forward No Answer DN (FDN) updated with vacant DN through

User Selectable Call Redirection (USCR) from telephone. Where : x = tn (l s c
u), y = old FDN, and z = new vacant FDN of set.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 684 of 2360

CSC1001 x y z
Hunt DN updated with vacant DN through User Selectable Call Redirection

(USCR) from telephone. Where : x = tn (l s c u), y = old Hunt DN, and z = new
vacant Hunt DN.
Action:
Severity: Minor.
CSC1002 x y z
SNMP trap: Yes
External Call Forward No Answer DN (EFD) updated with vacant DN through

User Selectable Call Redirection (USCR) from telephone. Where : x = tn (l s c
u), y = old EFD, and z = new vacant EFD.
Action:
Severity: Minor.
CSC1003 x y z
SNMP trap: Yes
External Hunt DN (EHT) updated with vacant DN through User Selectable Call
Redirection (USCR) from telephone. Where : x = tn (l s c u), y = old EHT, and
z = new vacant EHT
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 685 of 2360
DBMT: Database Media Transfer

Messages
DBMT0002
Unable to determine floppy device name.

Action:
Severity: Minor.
DBMT0003
SNMP trap: Yes
Unable to determine file names for transfer.

Action:
Severity: Minor.
DBMT0004
SNMP trap: Yes
Unable to open floppy drive.

Action: Be sure disk is properly inserted.
Severity: Minor.
DBMT0005
SNMP trap: Yes
Unable to create temporary database file.

Action:
Severity: Minor.
DBMT0006
SNMP trap: Yes
Unable to create temporary Configuration file.

Action:
Severity: Minor.
DBMT0007
SNMP trap: Yes
Unable to transfer database to hard disk.

Action:
Severity: Minor.
DBMT0008
SNMP trap: Yes
Unable to append Database and Configuration files into one file.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 686 of 2360

DBMT0009
Unable to rename Configuration file to Database file for s option.

Action:
Severity: Minor.
DBMT0010
SNMP trap: Yes
Unable to restore file to original state.

Action:
Severity: Minor.
DBMT0011
SNMP trap: Yes
Unable to rename all files correctly.

Action:
Severity: Minor.
DBMT0012
SNMP trap: Yes
Unable to read Private sector from floppy disk.

Action:
Severity: Minor.
DBMT0013
SNMP trap: Yes
Too many disks being used.

Action:
Severity: Minor.
DBMT0014
SNMP trap: Yes
SNMP trap: Yes
Incorrect disk in drive.

Action:
Severity: Minor.
DBMT0015
Unable to identify record type.

Action:
Severity: Minor.
DBMT0016
SNMP trap: Yes
Unable to read sector(s) from disk.

Action: Ensure that the disk is properly inserted. Check power and SCSI cable
on the CMDU.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 687 of 2360

DBMT0017
Unable to write database file to hard disk.

Action:
Severity: Minor.
DBMT0018
SNMP trap: Yes
Unable to write Configuration file to hard disk.

Action:
Severity: Minor.
DBMT0019 x y
SNMP trap: Yes
Incorrect database record count. Was x, should be y.

Action:
Severity: Minor.
DBMT0020 x y
SNMP trap: Yes
Incorrect Configuration record. Was x, should be y.

Action:
Severity: Minor.
DBMT0021
SNMP trap: Yes
Incorrect floppy disk in drive. Need A1.

Action:
Severity: Minor.
DBMT0022
SNMP trap: Yes
Read Private Sector: Unable to read sector from floppy disk.

Action:
Severity: Minor.
DBMT0023
SNMP trap: No
Read Private Sector: Invalid floppy disk.

Action:
Severity: Minor.
DBMT0024
SNMP trap: No
Read Private Sector: End of track 1 not found.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 688 of 2360

DBMT0026
Get Record Type: Unable to identify record type.

Action:
Severity: Minor.
DBMT0028
SNMP trap: No
Get Disk Buffer: Unable to seek on floppy disk.

Action:
Severity: Minor.
DBMT0029
SNMP trap: No
Get Disk Buffer: Unable to read from floppy disk.

Action: Check hard disk power, and SCSI cable on CMDU.
Severity: Minor.
DBMT0030
SNMP trap: No
Append Database: Unable to seek database on hard disk.

Action:
Severity: Minor.
DBMT0031
SNMP trap: No
Append Database: Unable to seek Configuration on hard disk.

Action:
Severity: Minor.
DBMT0032
SNMP trap: No
Append Database: Unable to read from hard disk.

Severity: Minor.
DBMT0033
SNMP trap: No
Append Database: Unable to write to hard disk.

Action:
Severity: Minor.
DBMT0034
SNMP trap: No
Write Database: Unable to write to hard disk.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 689 of 2360

DBMT0035
Write Database: Unable to write to hard disk.

Severity: Minor.
DBMT0036
SNMP trap: No
Write Database: Unknown database format.

Action: Be sure that the correct B disk is in the drive.
Severity: Minor.
DBMT0037
SNMP trap: No
Get Directory: Unable to read Private sector from floppy disk.

Action:
Severity: Minor.
DBMT0038
SNMP trap: No
Get Directory: Unable to read sector(s) from floppy disk.

Action: Be sure disk is inserted properly in the correct drive.
Severity: Minor.
DBMT0039
SNMP trap: No
Close Files: Unable to close floppy device.

Action:
Severity: Minor.
DBMT0040
SNMP trap: No
Close Files: Unable to close Database file.

Action:
Severity: Minor.
DBMT0041
SNMP trap: No
Close Files: Unable to close Configuration file.

Action:
Severity: Minor.
DBMT0042
SNMP trap: No
Rename All Files: Unable to rename secondary Database file to holding file.
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 690 of 2360

DBMT0043
Rename All Files: Unable to restore files to original state.

Action:
Severity: Minor.
DBMT0044
SNMP trap: No
Rename All Files: Unable to rename secondary Configuration file to holding

file.
Action:
Severity: Minor.
DBMT0045
SNMP trap: No
Rename All Files: Unable to rename primary Database file to secondary file.
Action:
Severity: Minor.
DBMT0046
SNMP trap: No
Rename All Files: Unable to rename primary Configuration file to secondary

file.
Action:
Severity: Minor.
DBMT0047
SNMP trap: No
Rename All Files: Unable to rename new Database file to primary file.
Action:
Severity: Minor.
DBMT0048
SNMP trap: No
Rename All Files: Unable to rename new Configuration file to primary file.
Action:
Severity: Minor.
DBMT0049
SNMP trap: No
Get File Names: Unable to determine primary Database file name.

Action:
Severity: Minor.
DBMT0050
SNMP trap: No
Get File Names: Unable to determine secondary Database file name.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 691 of 2360

DBMT0051
Get File Names: Unable to determine holding Database file name.

Action:
Severity: Minor.
DBMT0052
SNMP trap: No
Get File Names: Unable to determine temporary Database file name.

Action:
Severity: Minor.
DBMT0053
SNMP trap: No
Get File Names: Unable to determine primary Configuration file name.

Action:
Severity: Minor.
DBMT0054
SNMP trap: No
Get File Names: Unable to determine secondary Configuration file name.

Action:
Severity: Minor.
DBMT0055
SNMP trap: No
Get File Names: Unable to determine holding Configuration file name.

Action:
Severity: Minor.
DBMT0056
SNMP trap: No
Get File Names: Unable to determine temporary Configuration file name.

Action:
Severity: Minor.
DBMT0057
SNMP trap: No
Restore Files: Unable to restore temporary Database file.

Action:
Severity: Minor.
DBMT0058
SNMP trap: No
Restore Files: Unable to restore primary Database file.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 692 of 2360

DBMT0059
Restore Files: Unable to restore secondary Database file.

Action:
Severity: Minor.
DBMT0060
SNMP trap: No
Restore Files: Unable to restore temporary Configuration file.

Action:
Severity: Minor.
DBMT0061
SNMP trap: No
Restore Files: Unable to restore primary Configuration file.

Action:
Severity: Minor.
DBMT0062
SNMP trap: No
Restore Files: Unable to restore secondary Configuration file.

Action:
Severity: Minor.
DBMT0205
SNMP trap: No
Read Private Sector: End of track 3 not found.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 693 of 2360
DCH: D-channel Diagnostic (LD 96)

The D-channel diagnostic program (LD 96) is used to test and maintain the
D-channel link and the D-channel Interface card. Problems are reported in
DCH messages.
Complete operation of enhanced reporting requires Release 17 or later, and
QPC757 vintage E and later.
Messages
DCH0000
Program identifier.
Action:
Severity: Info.
DCH0001
SNMP trap: No
ISDN package is not equipped.

Action:
Severity: Minor.
DCH0002
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Command not allowed.

Action:
Severity: Info.
DCH0003
DCHI is disabled.
Action:
Severity: Minor.
DCH0005
Undefined link/DCHI state. There is a software/hardware mismatch.

Action: 1. Disable and re-enable the DCHI card.
2. Check DCHI status
Severity: Minor.
DCH0006
SNMP trap: Yes
DCHI not responding.

Action: 1. Disable and re-enable the DCHI card. 2.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 694 of 2360

DCH0007
Command invalid at this state.

Action:
Severity: Info.
DCH0009
SNMP trap: Yes
Invalid command entered.

Action:
Severity: Info.
DCH0010
SNMP trap: Yes
SNMP trap: Yes
Invalid parameter #1.

Action:
Severity: Info.
DCH0011
Invalid number of parameters.

Action:
Severity: Info.
DCH0012
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
DCHI is not configured.

Action:
Severity: Info.
DCH0013
Invalid message type.

Action:
Severity: Minor.
DCH0014
Invalid IE type.
Action:
Severity: Minor.
DCH0017
Invalid key entered.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 695 of 2360

DCH0018
Invalid total keys entered.

Action:
Severity: Minor.
DCH0019
SNMP trap: Yes
SNMP trap: Yes
Invalid table number.

Action:
Severity: Minor.
DCH0020
Transmit buffer is not empty.

Action:
Severity: Minor.
DCH0021
SNMP trap: Yes
Receive buffer not ready.

Action: Check DCHI status
Severity: Minor.
DCH0022
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Invalid Octet number.

Action:
Severity: Minor.
DCH0023
Unexpected loop input.

Action:
Severity: Minor.
DCH0024
Backup DCH is not configured.

Action:
Severity: Minor.
DCH0025
SNMP trap: Yes
SNMP trap: Yes
DCH is already active.

Action:
Severity: Minor.
System Messages
Page 696 of 2360

DCH0026
Specified DCH is not established.

Action: DCH must be in established state before switch command can be
carried out.
Severity: Info.
DCH0028
SNMP trap: Yes
Command only valid for D-channels on MSDL card

Action:
Severity: info.
DCH0029
SNMP trap: Yes
DCH has to be enabled first.

Action:
Severity: Info.
DCH0030
SNMP trap: Yes
DCH has to be in Test Mode first.

Action:
Severity: Info.
DCH0031
SNMP trap: Yes
Unable to enable the local loopback substate because the sub state is not idle.
Action:
Severity: Minor.
DCH0032
SNMP trap: Yes
Unable to disable the local loopback sub state because it is not in the local
loopback sub state
Action:
Severity: Minor.
DCH0033
SNMP trap: Yes
Unable to enable the remote loopback sub state because the sub state is not
idle.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 697 of 2360

DCH0035
Unable to run the local loopback test because the link is not in a local loopback
sub state.
Action:
Severity: Minor.
DCH0036
SNMP trap: Yes
Unable to run the remote loopback test because the link is not in an idle sub
state.
Action:
Severity: Minor.
DCH0037
SNMP trap: Yes
The feature specified for monitoring is invalid. Parameter #5 is not a

recognized feature.
Action:
Severity: Minor.
DCH0038
SNMP trap: Yes
Invalid DCH number for ENL command

Action:
Severity: Info.
DCH0039
SNMP trap: Yes
Invalid DCH state for enabling the link.

Action:
Severity: Info.
DCH0041
SNMP trap: Yes
Input enable command not recognized.

Action:
Severity: Info.
DCH0042
SNMP trap: Yes
MSDL card has to be in operational state

Action:
Severity: info.
SNMP trap: Yes
System Messages
Page 698 of 2360

DCH0044
Test or DCH maintenance command is not supported for D-channels

configured on the MSDL card
Action:
Severity: Info.
DCH0045
SNMP trap: Yes
SNMP trap: Yes
MSDL card is disabled

Action:
Severity: Minor.
DCH0047 {DCH #} {D-channel data} Command is not supported for UIPE D-channels.
Action:
Severity: Info.
SNMP trap: Yes
DCH0048 {DCH #} {D-channel data} Set D-channel pointers failed for Download database.
Action:
Severity: Minor.
SNMP trap: Yes
DCH0049 {DCH #} {D-channel data} D-channel has to be on MSDL card.

Action:
Severity: Minor.
SNMP trap: Yes
DCH0050 {DCH #} {D-channel data} D-channel has to be UIPE for download

database command
Action:
Severity: Minor.
SNMP trap: Yes
DCH0051 {DCH #} {D-channel data} MSDL card is not operational

Action:
Severity: Minor.
SNMP trap: Yes
DCH0052 {DCH #} {D-channel data} D-channel has to be enabled.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 699 of 2360

DCH0053
Invalid command for D-channel over IP.

Action:
Severity: Info.
DCH0054
SNMP trap: Yes
DCH0054 DCH: x EST yyyy TIME: hh:mm:ss mm/dd/yyyy

Action:
Severity: Major.
DCH0055
SNMP trap: Yes
DCH0054 DCH: x RLS yyyy TIME: hh:mm:ss mm/dd/yyyy

Action:
Severity: Major.
DCH0056
SNMP trap: Yes
DCH: x FAIL TIME: hh:mm:ss mm/dd/yyyy

Action:
Severity: Critical.
DCH0057
SNMP trap: Yes
DCH: x TEST TIME: hh:mm:ss mm/dd/yyyy

Action:
Severity: Minor.
DCH0300
SNMP trap: Yes
Test 200, interrupt handler interface, failed

Action: If test continues to fail, report software problem
Severity: Minor.
DCH0301
SNMP trap: Yes
Test 201, interrupt handler-to-link interface, failed.

Action: If test continues to fail, report software problem.
Severity: Minor.
DCH0302
SNMP trap: Yes
DCHI test 101 failed. No interrupt, but good data.

Action: Replace DCHI.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 700 of 2360

DCH0303
DCHI test 101 failed. There is interrupt, but bad data

Action: Replace DCHI
Severity: Minor.
DCH0304
SNMP trap: Yes
DCH test 101 failed. No interrupt and bad data

Action: Replace DCHI.
Severity: Minor.
DCH0305
SNMP trap: Yes
DCHI test 100 failed. Stuck interrupt

Action: Replace DCHI
Severity: Minor.
DCH0401
SNMP trap: Yes
That command is not allowed. This is a single octet information element.

Action:
Severity: Info.
DCH0402
SNMP trap: Yes
Only three message types can be specified in one command.

Action:
Severity: Info.
DCH0403
SNMP trap: Yes
Only one feature can be monitored at one time.

Action: STAT MON {DCH#} to see what is currently being monitored
Severity: Info.
DCH0404
SNMP trap: Yes
Invalid TN or no TN was entered.

Action:
Severity: Info.
DCH0405
SNMP trap: Yes
Only five TNs can be specified for incoming or outgoing messages.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 701 of 2360

DCH0406
This TN has been specified already

Action:
Severity: Info.
DCH0407
SNMP trap: Yes
TN does not associate with the selected D-channel

Action:
Severity: Info.
DCH0408
SNMP trap: Yes
Backup D-channel is not allowed; primary D-channel should be used

Action:
Severity: Info.
DCH0410
SNMP trap: Yes
The ENL SERV command cannot be executed when the primary D-channel
and, if equipped, the backup D-channel are in the established state
Action: Disable both D-channels before entering the ENL SERV command
Severity: Info.
DCH0411
SNMP trap: Yes
SDCH command is allowed only when IFC = SL-1 and RCVP = NO in LD 17

Action:
Severity: Info.
SNMP trap: Yes
DCH0421 dch# OVLD xxxx dch# is the d channel number, xxxx is the number of ISDN messages
during last time interval)
The overload control for the indicated PRI D channel is active. Any incoming
new call setup is rejected by protocol control.
Action: No action required unless this event is reported continuously on the
same D channel. In those cases, one needs to investigate the cause and
determine whether the D channel overload threshold value needs to be adjusted
in Overlay 17 for the given D channel.
Severity: Minor.
DCH1001
SNMP trap: Yes
Invalid primitive-ID.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 702 of 2360

DCH1002
Unexpected primitive
Severity: Minor.
DCH1003
SNMP trap: Yes
Protocol error.
Action: 1. If the error continues, check DCHI card status.
2. If the problem still continues, report it.
Output format:
DCH1003 DCH: w PROTOCOL: x LAYER: y ERROR: z
Where:
w = DCH device number
x = protocol used
y = layer number 1, 2 or 3
z = error condition which depends on the layer number
When y = 1, x = :
01H = illegal or unimplemented primitive
02H = no handshake signal, check link status/database
03H = invalid DCH configure table, check database
04H = invalid LRC at last download table, S/W problem
05H = data is too short, far end or SL-1 S/W problem
06H = data is too long, far end or SL-1 S/W problem
When y = 2, x = :
01H = peer initiated re-establish link, no action
02H = unsuccessful retransmission (N200 retries) for SABME, far-end problem
03H = unsuccessful retransmission (N200 retries) for DISC, far-end problem
04H = N(R) error, far-end problem
05H = received information field exceeding N201, far-end is sending bad data
06H = received non-implemented/undefined frame, far-end problem
07H = received I-frame but not allowed, far-end problem
08H = received FRMR frame
When y = 3, x = :
01H = received message with less than 4 octets far-end or SL-1 S/W problem
02H = received message with unsupported protocol discriminator, far-end or SL-1
S/W problem
03H = received message with unsupported information element, far-end or SL-1
S/W problem
04H = received undefined/unimplemented message type, check DCH download
table
05H = received message with mandatory information element, far-end or L-1 S/W
problem
553-3001-411
Standard 15.00
January 2006
Page 703 of 2360

06H = invalid call reference number, far end or SL-1 S/W problem
07H = invalid IE contents in optional IE field, far end or SL-1 S/W problem
08H = invalid IE contents in mandatory IE field, far end or SL-1 S/W problem
Severity: Critical.
DCH1004
SNMP trap: Yes
SNMP trap: Yes
PRI is out-of-service.
Action:
Severity: Critical.
DCH1005
Link release error.

Action: 1. Check DCHI status
2. Check the PRI to DCHI cable
3. Check PRI status
Severity: Critical.
DCH1006
SNMP trap: Yes
Link establishment error.

3. Check PRI status
Severity: Critical.
DCH1007
SNMP trap: Yes
Interrupt was lost.

Action: If more than ten times per day, run DCHI tests 200 and 201.
Severity: Critical.
DCH1008
SNMP trap: Yes
Output request buffer overflow.

Action: If more than five times per day, reset D-channel output buffer size in LD
17, using prompt OTBF.
Severity: Critical.
DCH1009
SNMP trap: Yes
PRI reported DCHI is out-of-service.

2. Check PRI status
Severity: Critical.
SNMP trap: Yes
System Messages
Page 704 of 2360

DCH1011
Late link establishment.

Action: 1. If the far-end is disabled, no action needed.
2. If the far-end is active, increase the timer threshold in LD 17, using prompt
T200.
Severity: Minor.
DCH1012
SNMP trap: Yes
Late link release

Action: 1. If the far-end is disabled, no action needed.
2. If the far-end is active, increase the timer threshold in LD 17, using prompt
T200.
Severity: Minor.
DCH1013
SNMP trap: Yes
Invalid DCHI status due to software/hardware mismatch.

Action: 1. Disable and re-enable the DCHI card
Severity: Minor.
DCH1014
SNMP trap: Yes
Invalid DCHI status due to software/hardware mismatch

Action: 1. Disable and re-enable the DCHI card
Severity: Minor.
DCH1015
SNMP trap: Yes
Receive buffer full

Action: If more than five times per day, disable and re-enable DCHI.
DCH1016
Severity: Minor.
DCH1016
SNMP trap: Yes
Transmit buffer full.

Action: Check the DCHI card.
Severity: Minor.
DCH1017
SNMP trap: Yes
No end-of-message
Action: Definitely a DCHI problem. Check the DCHI card.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 705 of 2360

DCH1018
No transmit buffer available.

Action: 1. Check PRI to DCHI cable
2. Check PRI status
Severity: Minor.
DCH1019
SNMP trap: Yes
DCHI is hardware disabled.

Action:
Severity: Minor.
DCH1020
SNMP trap: Yes
DCH1020 indicates the standby D-channel is not in the EST state during the
switchover.
Action:
Severity: Minor.
DCH1021
SNMP trap: Yes
The DCHI is reset because too many DCH1015 messages have occurred.
DCH1024
Action:
Severity: Info.
DCH1024
SNMP trap: Yes
The DCH port on the MSDL card could not be enabled because the MSDL
card is not in an operational state.
Action:
Severity: Minor.
DCH1025
SNMP trap: Yes
Did not receive a confirmation from Layer 2 for MSDL DCH test state event;
therefore, a timeout has occurred.
Action:
Severity: Info.
DCH1026
SNMP trap: Yes
An invalid timeout occurred for the DCH test state. No further action is required
for this event.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 706 of 2360

DCH1027
An invalid test confirmation was received from layer. No further action is

required for this event.
Action:
Severity: Info.
DCH1028
SNMP trap: Yes
The DCH has to be on the MSDL card for the maintenance task requested
Action:
Severity: Info.
DCH1029
SNMP trap: Yes
Resynchronization of the flow control counters failed when a flow control

condition was detected by the MSDL DCH Handler application.
Action:
Severity: Info.
DCH1030
SNMP trap: Yes
Output request buffer overflow for D channels on the MSDL card.

Action: 1. Check PRI to DCHI cable.
2. Check PRI status.
Severity: Info.
DCH1031 x
SNMP trap: Yes
Cannot enable DCH x because IPRA package is restricted.

Action:
Severity: Info.
DCH1039
SNMP trap: No
The feature you specified to disable has not been enabled.

Action: STAT MON {DCH#} to see what is currently being monitored.
Severity: Info.
DCH1040
SNMP trap: Yes
The requested operation does not apply to the selected interface.

Action: Attempt to enable SERV messages on an APISDN IFC.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 707 of 2360

DCH1042
DCH does not have GF capability

Action:
Severity: Info.
DCH1043
SNMP trap: Yes
Invalid call reference number.

Action:
Severity: Info.
SNMP trap: Yes
DCH2001 {DCH #} {D-channel data} DCH link established a timeout. Request to establish
D-channel link failed and DCH will be reset.
Action:
Severity: Info.
SNMP trap: Yes
DCH2002 {DCH #} {D-channel data} Unexpected primitive received.

Action:
Severity: Info.
SNMP trap: Yes
DCH2003 {DCH #} {D-channel data} Invalid link state for timeout event.
Action:
Severity: Info.
SNMP trap: Yes
DCH2004 {DCH #} {D-channel data} Invalid DCH application status in timeout event.
Action:
Severity: Info.
SNMP trap: Yes
DCH2005 {DCH #} {D-channel data} PRI reported DCH is out of service.

Action:
Severity: Info.
SNMP trap: Yes
DCH2006 {DCH #} {D-channel data} Layer2 reset timeout

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 708 of 2360

DCH2007 {DCH #} {D-channel data} Invalid check PRI timeout - no PRI loop.
Action:
Severity: Info.
SNMP trap: Yes
DCH2008 {DCH#} {D-channel data} PRI is out of service.

Action:
Severity: Info.
SNMP trap: Yes
DCH2009 {DCH #} {D-channel data} PRI is out of service.

Action:
Severity: Info.
SNMP trap: Yes
DCH2010 {DCH #} {D-channel data} Enable Request Timeout.

Action:
Severity: Info.
SNMP trap: Yes
DCH2011 {DCH #} {D-channel data} Layer2 establish timeout.

Action:
Severity: Info.
SNMP trap: Yes
DCH2012 {DCH #} {D-channel data} No confirmation received from loadware for test mode.
Action:
Severity: Info.
SNMP trap: Yes
DCH2013 {DCH #} {D-channel data} Invalid test mode timeout event.

Action:
Severity: Info.
SNMP trap: Yes
DCH2014 {DCH #} {D-channel data} DCH link release timeout error

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 709 of 2360

DCH2015 {DCH #} {D-channel data} Polling failed to release link.
Action:
Severity: Info.
SNMP trap: Yes
DCH2016 {DCH #} {D-channel data} DCH enable request denied - MSDL is not operational.
Action:
Severity: Info.
SNMP trap: Yes
DCH2017 {DCH #} {D-channel data} Invalid DCH link state - Enable request denied.
Action:
Severity: Info.
DCH2018
SNMP trap: Yes
Cannot establish link - link is in test mode

Action:
Severity: Info.
SNMP trap: Yes
DCH2023 {DCH #} {D-channel data} Maintenance request denied - DCH is not enabled.
Action:
Severity: Info.
SNMP trap: Yes
DCH2040 {DCH #} {D-channel data} PRI reported that primary D-channel is out-of-service.
Action:
Severity: Info.
DCH4001
SNMP trap: Yes
Invalid DCH number received in SSD message from Transport

Action:
Severity: Info.
DCH4283
SNMP trap: Yes
Both D-channels have been released.

Action: Establish the D-channel.
Severity: Minor.
DCH4285 {error}
SNMP trap: No
The ISPC command (EST, RLS or STAT) cannot be executed on the ISPC
slave D-channel trunk. The format of the message is: DCHxxxx {error} where
{error} is:
System Messages
Page 710 of 2360

0: Tn entered is not a valid DTI2 phantom TN.
3: The trunk must be configured with the DTN class of service.
4: Data corruption with the route pointer.7: The route is not configured with
DSEL = DTA.
8: The route must not be an ISL route.
9: The route is not configured with DLTN = Yes.
10: The route is not configured as incoming.
11: The route is not configured with PRDL = BSY.
14: The route is not configured with NEDC = ETH.
15: The route is not configured with FEDC = ETH.
16: The route is not configured with CPDC = NO.
17: DDD_PACKAGE is restricted.
18: The trunk is not configured with SDCH =YES and SMAS = NO (i.e. Slave
channel)
19: The ISPC Slave channel is not in Release state therefore the command
cannot be executed. Do a RLS ISPC command first.
Action: Check system configuration, and retry the command.
Severity: Info.
DCH4288
SNMP trap: Yes
The overloaded DCH MSDL port needs to be disabled before it can be

enabled.
Action: Place the D-channel in the manually disabled mode with the command
DIS DCH x.
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 711 of 2360
DLO: Disk Layout

Messages
DLO0001
Unable to find symbol.

Action:
Severity: Minor.
DLO0002
SNMP trap: No
Unable to read from file, error x.

Action:
Severity: Minor.
DLO0003
SNMP trap: No
Unknown error code {codename}.

Action:
Severity: Minor.
DLO0004
SNMP trap: No
Unable to get active CMDU. Cannot look up symbol.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 712 of 2360
553-3001-411
Standard 15.00
January 2006
Page 713 of 2360
DROL: Daily Routine Overlay

When daily routine runs on the system it prints a message, on the
maintenance console and/or the history file, indicating when it begins and
ends and what the overlay is that it is currently running.
The format of printing daily routine messages:
DROL000 DAILY ROUTINE BEGIN
Overlay Mnemonic LD overlay Number
DROL001 DAILY ROUTINE END
Overlay Mnemonic LD overlay Number
The different overlay mnemonics and the corresponding overlay numbers are
given below:
NPR - 30
RPD - 33
TDS - 34
CED - 35
MTRK - 36
IOD - 37
CNF - 38
CDMA - 40
DUMP - 43
AUDIT - 44
BCD - 45
MFS - 46
ACDDD - 47
ICU - 51
RPM - 53
MFD - 54
DTIM - 60
MMW - 61
CCED - 135
CIOD - 137
Messages
DROL0000
DAILY ROUTINE BEGIN

Overlay Mnemonic LD overlay number
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 714 of 2360

DROL0001
DAILY ROUTINE END

Overlay Mnemonic LD overlay number
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 715 of 2360
DSET: Digital Set Download

Digital Set downloading takes place during system reload.
Messages
DSET0000 DOWN LOAD 1 2 3 4 5 6 7 8 9 Digital Set downloading has taken place. This
information appears once during system reload. Eight additional fields are
associated with this output.
Output format is:
1 = the number of SSD messages sent
2 = the number of M3000 sets downloaded
3 = the number of Compact sets downloaded
4 = the number of Digital attendant consoles downloaded
5 = the number of M3000 sets that failed the download
6 = the number of Compact sets that failed the download
7 = the number of Digital attendant consoles that failed the download
8 = the current real time clock
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 716 of 2360
553-3001-411
Standard 15.00
January 2006
Page 717 of 2360
DSL: DSL Diagnostic (LD 32)

The DSL diagnostic program is used to test and maintain the DSL link and BRI
interface cards like MISP. Messages are sent out whenever a DSL link is
established, released or tested. Along with these messages, date and time is
also sent.
Format of these messages are below:
DSL001 DSL: w x y z EST REASON TIME: hh:mm:ss mm/dd/yyyy
DSL002 DSL: w x y z RLS REASON TIME: hh:mm:ss mm/dd/yyyy
DSL003 DSL: w x y z TEST TIME: hh:mm:ss mm/dd/yyyy
w x y z is DSL TN in l c s u format. REASON indicates why the DSL link is
established or released. There is no reason for TEST message.
Messages
DSL0001
DSL: w x y z EST REASON TIME: hh:mm:ss mm/dd/yyyy

Action:
Severity: Major.
DSL0002
SNMP trap: Yes
DSL: w x y z RLS REASON TIME: hh:mm:ss mm/dd/yyyy

Action:
Severity: Major.
DSL0003
SNMP trap: Yes
DSL: w x y z TEST TIME: hh:mm:ss mm/dd/yyyy

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 718 of 2360
553-3001-411
Standard 15.00
January 2006
Page 719 of 2360
DTA: Digital Trunk Diagnostic

The Digital Trunk Interface diagnostic program is used to maintain the
following:
QPC472 Digital Trunk Interface (DTI)
QPC536 2.0 Mb/s Digital Trunk Interface (DTI)
QPC720 Primary Rate Interface (PRI)
QPC471 and QPC775Clock Controller
NT8D72AA 2.0 Mb/s Primary Rate Interface (PRI2)
Messages
DTA0001 loop
Data block is not defined.

Action:
Severity: Minor.
DTA0002 loop
SNMP trap: Yes
Message received with wrong chip field.

Action:
Severity: Critical.
DTA0003 loop
SNMP trap: Yes
Power up message received.

Action:
Severity: Critical.
DTA0004 loop
SNMP trap: Yes
Phase Lock Loop (PLL) clear message is received without phase lock loop
alarm.
Action:
Severity: Critical.
DTA0005 loop
SNMP trap: Yes
Yellow alarm (remote alarm) has occurred.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 720 of 2360

DTA0006 loop
Yellow alarm (remote alarm) 24-hour threshold has been exceeded. Manual
intervention is required.
Action:
Severity: Critical.
DTA0007 loop
SNMP trap: Yes
Yellow alarm (remote alarm) is cleared.

Action:
Severity: Minor.
DTA0008 loop
SNMP trap: Yes
Yellow alarm (remote alarm) is disabled.

Action:
Severity: Critical.
DTA0009 loop
SNMP trap: Yes
Phase lock loop alarm has occurred.

Action:
Severity: Critical.
DTA0010 loop
SNMP trap: Yes
Phase lock loop alarm has cleared.

Action:
Severity: Critical.
DTA0011 loop
SNMP trap: Yes
Bit error rate warning threshold.

Action:
Severity: Critical.
DTA0012 loop
SNMP trap: Yes
Bit error rate out-of-service limit.

Action:
Severity: Critical.
DTA0013 loop
SNMP trap: Yes
Too many bit error rate out-of-service occurrences in 24 hours.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 721 of 2360

DTA0014 loop
Bit error rate alarm cleared.

Action:
Severity: Critical.
DTA0015 loop
SNMP trap: Yes
Frame slip-tracking-maintenance limit.

Action:
Severity: Critical.
DTA0016 loop
SNMP trap: Yes
Frame slip-tracking-out-of-service limit.

Action:
Severity: Critical.
DTA0017 loop
SNMP trap: Yes
Frame slip-free run (non-tracking)-maintenance limit.

Action:
Severity: Critical.
DTA0018 loop
SNMP trap: Yes
Frame slip-free run (non-tracking)-out-of-service limit.

Action:
Severity: Critical.
DTA0019 loop
SNMP trap: Yes
Frame alignment maintenance limit.

Action:
Severity: Critical.
DTA0020 loop
SNMP trap: Yes
Frame alignment out-of-service limit.

Action:
Severity: Critical.
DTA0021 loop
SNMP trap: Yes
Frame alignment alarm persisted for 3 seconds.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 722 of 2360

DTA0022 loop
Frame alignment alarm has cleared for at least 15 seconds.

Action:
Severity: Minor.
DTA0023 loop
SNMP trap: Yes
SNMP trap: Yes
PRI loop is up.

Action:
Severity: Minor.
DTA0024 loop
System initiated (automatic, LD 45 or LD 60) self-test on PRI loop L failed. All

channels are disabled, loop is put into red alarm (local alarm).
Action:
Severity: Critical.
DTA0025 loop
SNMP trap: Yes
System initiated (automatic, LD 45 or LD 60) self-test on PRI loop L passed.

Channels were previously disabled due to self-test fault or a loop-level
self-test. Channels are enabled and red alarm (local alarm) is removed.
Action:
Severity: Critical.
DTA0026 loop
SNMP trap: Yes
Non-tracking frame slip out of service limit is reached while monitoring frame
slip improvement. Trunks remain out-of-service and the improvement timer
(prompt SRIM in LD 73) is restarted.
Action:
Severity: Critical.
DTA0027
SNMP trap: Yes
Frame slip-free run (non-tracking)-guard timer expired. Trunks are kept out of
service. Software is checking for slip rate improvement. The improvement
criterion is the number of maintenance messages the system gets during the
guard time.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 723 of 2360

DTA0028 loop
Slip rate improvement criterion is not met. Trunks remain out-of-service,

improvement timer is reset (prompt SRIM in LD 73).
Action:
Severity: Critical.
DTA0029 loop
SNMP trap: Yes
Non-tracking frame slip rate improvement criterion is met. Trunks being

returned to service.
Action:
Severity: Minor.
DTA0030 loop
SNMP trap: Yes
Alarm status input message received from an unexpected loop.

Action:
Severity: Critical.
DTA0100 l s c u
SNMP trap: Yes
Far-end hardware corresponding to Virtual Terminal l s c u is disabled.

Action:
Severity: Critical.
DTA0101 l s c u
SNMP trap: Yes
Far-end hardware corresponding to Virtual Terminal l s c u is enabled.

Action:
Severity: Critical.
DTA0102 loop
SNMP trap: Yes
Power is up on the PRI2 board.

Action:
Severity: Minor.
DTA0103 loop
SNMP trap: Yes
Problem in loop or channel message of PRI2.

Action:
Severity: Minor.
DTA0104 loop
SNMP trap: Yes
Channel self-test report for PRI2.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 724 of 2360

DTA0105 loop
Loop self-test report for PRI2.

Action:
Severity: Minor.
DTA0106 loop
SNMP trap: Yes
PRI2 Loop is in acceptable state.

Action:
Severity: Minor.
DTA0107 loop
SNMP trap: Yes
PRI2 Loop is in G1 MNT state.

Action:
Severity: Minor.
DTA0108 loop
SNMP trap: Yes
PRI2 Loop is in G1 NNC state.

Action:
Severity: Minor.
DTA0109 loop
SNMP trap: Yes
PRI2 Loop is in G1 OOS state.

Action:
Severity: Critical.
DTA0110 loop
SNMP trap: Yes
PRI2 Loop is in G2 MNT state.

Action:
Severity: Minor.
DTA0111 loop
SNMP trap: Yes
PRI2 Loop is in G2 NNC state.

Action:
Severity: Minor.
DTA0112 loop
SNMP trap: Yes
PRI2 Loop is in G2 OOS state.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 725 of 2360

DTA0113 loop
PRI2 Loop is in OOS state with no auto-start.

Action:
Severity: Minor.
DTA0114 loop
SNMP trap: Yes
PRI2 loop is disabled, and message received is not power up.

Action:
Severity: Minor.
DTA0115 loop
SNMP trap: Yes
Unsolicited PRI2 message received.

Action:
Severity: Minor.
DTA0116 loop
SNMP trap: Yes
PRI2 loop is in G1 NNDC state.

Action:
Severity: Minor.
DTA0117 loop
SNMP trap: Yes
PRI2 loop is in G2 NNDC state.

Action:
Severity: Minor.
DTA0200 loop
SNMP trap: Yes
The DTI2 (NI and CI-1) firmware has initialized.

Action:
Severity: Minor.
DTA0201 loop
SNMP trap: Yes
The Carrier Interface (CI-1) firmware has initialized.

Action:
Severity: Minor.
DTA0202 loop
SNMP trap: Yes
The Network Interface (NI) firmware has initialized.

Action:
Severity: Minor.
DTA0203 loop e
SNMP trap: Yes
A Group 2 error has been detected by the DTI card. Error (e) = 1 to 127
(Decimal). Listed below are various error types (e) and their value in decimal.
Error Type (e);Abbreviation;Decimal Value Loss of CRC4 Multiframe
System Messages
Page 726 of 2360

Alignment;CF;1 64 kb Alarm Indication Signal;AS;2 B6 TS0 non-FAS (far-end
OOS); C3;4 Loss of Frame Alignment;LF;8 Loss of Multiframe
Alignment;LM;16 Alarm Indication Signal;AI;32 B3 TS16 Frame 0 (far-end
OOS);C6;64 To interpret any given value of (e), you must translate (e) to
binary. For example, if (e) = 24 (decimal), the translated binary value = 0 0 1
1 0 0 0. This binary value may now be interpreted as follows: 0 = C6 0 = AI 1
= LM 1 = LF 0 = C3 0 = AS 0 = CF Therefore, the errors are for LF and LM.
Action: R9
Severity: Info.
DTA0203 loop x y
SNMP trap: Yes
A Group 2 error has been detected by the PRI2 card. The error information is
decoded as follows, where x : 4 = LOS (loss of signal) 3 = AIS (alarm indication
signal)2 = LFAS (loss of frame)1 = LMAS (loss of CRC multiframe)0 = RAI
(remote alarm indication) Where y: 2 = alarm occurred1 = alarm persisted 0 =
alarm clearedExample: DTA203 7 4 2 - PRI loop 7 loss of signal occurred.
Action:
Severity: Minor.
DTA0204 loop e
SNMP trap: Yes
Incomplete or incorrect ANI was received by CDTI2/CSDTI2 FW (outgoing

trunk) which reports this fact to the main CPU by SSD messin 9 (NI problem
report).
Action: This is a "warning only" message. No additional actions are taken. The
call will be processed regularly. However, FW will use the special hardcoded in
FW value as ANI.
Severity: Minor.
DTA0205 loop e
SNMP trap: Yes
The CI-1 firmware has encountered a problem.

Action: Refer to DTI009 for CI-1 microprocessor error codes (e).
Severity: Minor.
DTA0206 loop
SNMP trap: Yes
Response to channel status poll has timed out. The channel has been
disabled.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 727 of 2360

DTA0207 loop c s
An invalid signal has been received from the DTI. Where: s = ABCD signal
received from DTI; c = channel.
Action:
Severity: Minor.
DTA0208 loop c s
SNMP trap: Yes
An invalid signal has been requested to be sent to the DTI. Where: c =

channel, s = signal type requested.
Action:
Severity: Minor.
DTA0209 loop
SNMP trap: Yes
DTI loop is in acceptable state.

Action:
Severity: Minor.
DTA0210 loop e
SNMP trap: Yes
DTI loop is in Group 1 MNT state, where error (e) is one or more of: BV Bipolar Violation FV - Frame Alignment Violation SV - Slip Violation CV - Cyclic
Redundancy Check (CRC-4) Violation CRC- CRC4 Violation (Option 11 only)
Action:
Severity: Minor.
DTA0211 loop e
SNMP trap: Yes
DTI loop is in Group 1 NNC state, where error (e) is one or more of: BV Bipolar Violation FV - Frame Alignment Violation SV - Slip Violation CV - Cyclic
Redundancy Check (CRC-4) Violation CRC-CRC4 Violation (Option 11 only)
Action:
Severity: Minor.
DTA0212 loop e
SNMP trap: Yes
DTI loop L is in Group 1 OOS state, where error (e) is one or more of: BV Bipolar Violation FV - Frame Alignment Violation SV - Slip Violation CV - Cyclic
Redundancy Check (CRC-4) Violation CRC-CRC4 Violation (Option 11 only)
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 728 of 2360

DTA0213 loop e
DTI loop is in Group 2 MNT state, where error (e) is one or more of: BV Bipolar Violation, FV - Frame Alignment Violation, SV - Slip Violation, CV Cyclic Redundancy Check (CRC-4) Violation CRC-CRC4 Violation (Option 11
only)
Action:
Severity: Minor.
DTA0214 loop e
SNMP trap: Yes
DTI loop is in voice Group 2 NNC state, where error (e) is one or more of: C3
- B3 TSO non-FAS (far-end Out-of-Service), C6 - B6 TS16 frame 0 (far-end
lost MFA signal), CF - Loss of CRC-4 Multiframe Alignment, AS - 64 kb Alarm
indication signal, AI - Alarm Indication signal, LM - Loss of Multiframe
alignment, LF - Loss of Frame alignment, CFAS - Loss of CRC4 Multiframe
Alignment (Option 11 only)
Action:
Severity: Minor.
DTA0215 loop e
SNMP trap: Yes
DTI loop is in Group 2 OOS state, where error (e) is one or more of the
following: C3 - B3 TSO non-FAS (far-end Out-of-Service), C6 - B6 TS16 frame
0 (far-end lost MFA signal), CF - Loss of CRC-4 Multiframe Alignment, AS - 64
kb Alarm indication signal, AI - Alarm Indication signal, LM - Loss of Multiframe
Action:
Severity: Critical.
DTA0216 loop e
SNMP trap: Yes
DTI loop is in Group 1 MNT state, where error (e) is one or more of: BV Bipolar Violation, FV - Frame Alignment Violation, SV - Slip Violation, CV Cyclic Redundancy Check (CRC-4) Violation, CRC- CRC4 Violation (Option
11 only)
Action:
Severity: Minor.
DTA0217 loop e
SNMP trap: No
DTI loop is in Group 1 NNC state, where error (e) is one or more of: BV Bipolar Violation, FV - Frame Alignment Violation, SV - Slip Violation, CV Cyclic Redundancy Check (CRC-4) Violation, CRC-CRC4 Violation (Option
11 only)
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 729 of 2360

DTA0218 loop e
DTI loop L is in Group 1 OOS state, where error (e) is one or more of: BV Bipolar Violation, FV - Frame Alignment Violation, SV - Slip Violation, CV Cyclic Redundancy Check (CRC-4) Violation, CRC-CRC4 Violation (Option
11 only)
Action:
Severity: Minor.
DTA0219 loop e
SNMP trap: No
DTI loop is in Group 2 MNT state, where error (e) is one or more of: C3 - B3
TSO non-FAS (far-end Out-of-Service), C6 - B6 TS16 frame 0 (far-end lost
MFA signal), CF - Loss of CRC-4 Multiframe Alignment, AS - 64 kb Alarm
Action:
Severity: Minor.
DTA0220 loop e
SNMP trap: No
DTI loop is in voice Group 2 NNC state, where error (e) is one or more of: C3
- B3 TSO non-FAS (far-end Out-of-Service), C6 - B6 TS16 frame 0 (far-end
lost MFA signal), CF - Loss of CRC-4 Multiframe Alignment, AS - 64 kb Alarm
Action:
Severity: Minor.
DTA0221 loop e
SNMP trap: No
DTI loop is in Group 2 OOS state, where error (e) is one or more of the
following: C3 - B3 TSO non-FAS (far-end Out-of-Service), C6 - B6 TS16 frame
0 (far-end lost MFA signal), CF - Loss of CRC-4 Multiframe Alignment, AS - 64
kb Alarm indication signal, AI - Alarm Indication signal, LM - Loss of Multiframe
Action:
Severity: Minor.
DTA0222 loop
SNMP trap: No
DTI loop is in OOS state with no auto-start.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 730 of 2360

DTA0223
Wrong ABCD bits change reported by proper SSD messin from CDTI2/
CSDTI2 FW.
Action: Trunk is locked out.
Severity: Critical.
SNMP trap: Yes
DTA0223 loop s ch An invalid signal has been received from the DTI. It matches CCITT fault
signal. Far-end may be disabled. Where: c= channel and s = ABCD signal
received from DTI.
Action:
Severity: Minor.
DTA0224 loop ch
SNMP trap: Yes
DTI loop audit has found channel (ch) to be in an invalid HALFDISCONNECT

state (trunk lock-up). An disconnect attempt is being made on the CHNL.
Action:
Severity: Minor.
DTA0225 loop
SNMP trap: Yes
DTI loop is in G1 NNDC (No New Data Call) grade-of-service. Where (e) is one
or more of the following: BV - Bipolar Violation, FV - Frame Alignment
Violation, SV - Slip Violation, CV - CRC-4 Violation
Action:
Severity: Minor.
DTA0226 loop
SNMP trap: Yes
DTI loop is in G2 NNDC (No New Data Call) grade-of-service. Where (e) is one
or more of the following: C3 - B3 TS0 non-FAS (far-end Out-of-Service), C6 B6 TS16 frame 0 (far-end lost MFA signal), CF - Loss of CRC-4 Multiframe
Alignment, AS - 64 kb Alarm indication signal, AI - Alarm Indication signal, LM
- Loss of Multiframe alignment, LF - Loss of Frame alignment, CFAS - Loss of
CRC4 Multiframe Alignment (Option 11 only)
Action:
Severity: Minor.
DTA0300 loop
SNMP trap: Yes
A slip repetition has occurred on PRI2 loop.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 731 of 2360

DTA0301 loop
A slip deletion has occurred on PRI2 loop.

Action:
Severity: Minor.
DTA0302 loop
SNMP trap: Yes
A slip repetition overflow has occurred on PRI2 loop.

Action:
Severity: Minor.
DTA0303 loop
SNMP trap: Yes
A slip deletion overflow has occurred on PRI2 loop.

Action:
Severity: Minor.
DTA0304 loop
SNMP trap: Yes
A BPV unavailable condition has occurred on PRI2 loop.

Action:
Severity: Minor.
DTA0305 loop
SNMP trap: Yes
A CRC unavailable condition has occurred on PRI2 loop.

Action:
Severity: Minor.
DTA0306 loop
SNMP trap: Yes
A FAP unavailable condition has occurred on PRI2 loop.

Action:
Severity: Minor.
DTA0307 loop
SNMP trap: Yes
A BPV no-new-calls condition exists on PRI2 loop.

Action:
Severity: Minor.
DTA0308 loop
SNMP trap: Yes
A CRC no-new-calls condition exists on PRI2 loop.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 732 of 2360

DTA0309 loop
A FAP no-new-calls condition exists on PRI2 loop.

Action:
Severity: Minor.
DTA0310 loop
SNMP trap: Yes
A BPV maintenance condition has occurred on PRI2 loop.

Action:
Severity: Minor.
DTA0311 loop
SNMP trap: Yes
A CRC maintenance condition exists on PRI2 loop.

Action:
Severity: Minor.
DTA0312 loop
SNMP trap: Yes
A FAP maintenance condition exists on PRI2 loop.

Action:
Severity: Minor.
DTA0320 loop
SNMP trap: Yes
DTI loop error reporting was disabled due to an overload of input messages.
Action:
Severity: Critical.
DTA0321 loop
SNMP trap: Yes
Error reporting reenabled on DTI loop after being disabled by an input

overload (DTA320).
Action:
Severity: Minor.
SNMP trap: Yes
DTA0322 l ch w x y z An invalid pulsed signal has been received from the DTI. Where:
l = DTI loop/card number
ch = channel number
w = start bits (the ABCD bit pattern before analysis of the pulse)
x = pulsed bits (the ABCD pattern which was possibly part of a pulsed signal)
y = end bits (the ABCD pattern received after the pulse)
z = duration (length of the pulse in milliseconds
Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 733 of 2360

DTA0323 loop mtype An unexpected message type. Messin 28 received is permissible for DTI2
loop on CDTI2 card only.
(mtype - message type)
Action:
Severity:
SNMP trap: Yes
DTA0324 {loop number} A Phantom DTI2 loop has been found in a disabled state and is put back
in an enabled state.
Action: None, as the cause of the data corruption has been cleared.
Severity:
SNMP trap: Yes
DTA0325 {TN1} {TN2} {N} An ISPC phantom DTI2 (or an ISPC PRI2 trunk) has been found in an
invalid state. To avoid any new problem in the system, the calls are cleared in
the following manner: 1. - The ISPC phantom DTI2 trunk is put in a disabled
state. 2. - The ISPC call active on the PRI2 trunk (which is linked with the
phantom DTI2 trunk) is cleared. Where: TN1 = TN of the phantom DTI2 trunk
TN2 = TN of the real PRI2 trunk N = Details of the problem, as follows: 1 TNTRANS of PHTN_PHANTOM failed. 2 - No ACTIVECR on the PRI2 trunk.
3 - TERTN of ACTIVERCR is not equal to PHTN_PHANTOM. 4 - No link from
phantom DTI2 trunk to the PRI2 trunk. 5 - the flag ISPC active of the PRI2 TN
is not set. 6 - PHTN_PHANTOM of PRI2 is not the TN of the DTI2 unit. 7 - The
PRI2 unit is not the orig party of the ISPC CR. 11 - TNTRANS of PHTN_REAL
failed. 12 - The real TN of the phantom DTI2 TN is not a PRI2 TN. 13 - The
flag ISPC active of the DTI2 TN is not set. 14 - The ISPC_CR of the DTI2 unit
is not valid. 15 - The DTI2 unit is not the terminating party of the ISPC CR. 16
- The field PHTN_REAL of the DTI2 trunk should be null as the trunk is
disabled. Field is corrected. 17 - The field PHTN_PHANTOM of the DTI2 trunk
should be null as the trunk is disabled. Field is corrected. 18 - The field
ISPC_ACTIVE of the DTI2 trunk should be null as the trunk is disabled. Field
is corrected. 20 - the MAINPM of the ISPC call register is not established. 21
- There are some timeslots in the ISPC call register. 22 - the ISPC_CR of the
DTI2 unit is not the ACTIVECR of the PRI2 unit. Action: Information only. If this
message appears repeatedly or is associated with a system problem, contact
Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 734 of 2360
553-3001-411
Standard 15.00
January 2006
Page 735 of 2360
DTC: Digital Trunk Clock Controller

Diagnostic (LD 60)
The Digital Trunk Interface diagnostic program (LD 60) is used to maintain the
following:
QPC472 Digital Trunk Interface (DTI) card
QPC720 Primary Rate Interface (PRI) card
QPC775 Clock Controller card
QPC471 Clock Controller card
NTAK09 1.5 Mb/s (DTI/PRI) Interface Card
NTAK10 2.0 Mb/s (DTI) Interface Card
NTAK79 2.0 Mb/s Primary Rate Interface (PRI)
NTAK20 Clock Controller
NTAK93 (PRI) D-channel Handler Interface
The DTC messages indicate problems with the Clock Controllers.
Messages
DTC0001
Clock controller tracking on primary source loop.

Action:
Severity: Minor.
DTC0002
SNMP trap: Yes
Clock controller tracking on secondary source loop.

Action:
Severity: Minor.
DTC0003
SNMP trap: Yes
Clock controller cannot be accessed.

Action:
Severity: Critical.
DTC0004
SNMP trap: Yes
Clock controller indicates clock aging error (not locked on in five seconds).
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 736 of 2360

DTC0006
Reference clock switched to free run mode from secondary or primary.

Action:
Severity: Critical.
DTC0007
SNMP trap: Yes
Active reference clock is set to retrack primary.

Action:
Severity: Minor.
DTC0008
SNMP trap: Yes
Active reference is free run or the clock controller cannot be accessed.

Action:
Severity: Critical.
DTC0009
SNMP trap: Yes
Clock controller has been switched.

Action:
Severity: Critical.
DTC0010
SNMP trap: Yes
UART error is detected. Active CC cannot contact other CC.

Action:
Severity: Critical.
DTC0011
SNMP trap: Yes
Clock controller self-test failed; error exists.

Action:
Severity: Critical.
DTC0012
SNMP trap: Yes
Clock controller has reference clock problem.

Action:
Severity: Critical.
DTC0013
SNMP trap: Yes
Clock controller has tracking problem.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 737 of 2360

DTC0014
Clock controller set to free run.

Action:
Severity: Critical.
DTC0015
SNMP trap: Yes
Clock controller set to secondary.

Action:
Severity: Critical.
DTC0016
SNMP trap: Yes
Clock controller restored from free run or secondary to tracking on primary.

Action:
Severity: Minor.
DTC0017
SNMP trap: Yes
Clock controller restored from free run to tracking on secondary.

Action:
Severity: Critical.
DTC0018
SNMP trap: Yes
Cannot switch or restore to a reference clock because automatic reference

clock switching option is disabled.
Action:
Severity: Critical.
DTC0076
SNMP trap: Yes
Clock was just switched!

You should wait one minute before doing another clock switch.
Action:
Severity: Info.
DTC0100
SNMP trap: No
An invalid error message was received from the clock controller.

Action:
Severity: Critical.
DTC0101
SNMP trap: No
Only allow to disable the secondary clock reference.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 738 of 2360

DTC0102
Only allow to enable the secondary clock reference.

Action:
Severity: Minor.
DTC0124
SNMP trap: No
Clock controller information for this cabinet is not available. Either the link is
down or the cabinet is in survival mode.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 739 of 2360
DTD: Dial Tone Detector Diagnostic (LD

34)
The Tone and Digit Switch and Digitone Receiver diagnostic program (LD 34)
tests cards are used in generating and detecting tones in the SL-1 system.
Response to commands for the Dial Tone Detector card are output as DTD
messages. Response to commands for the Tone and Digit Switch card are
output as TDS messages.
Messages
DTD0001 l s c u
Failure to detect" has exceeded the allowable limit for Dial Tone Detector
(DTD) card l s c u.
Action:
Severity: Minor.
DTD0002 l s c u
SNMP trap: Yes
The DTD specified by l s c u has failed to pass the response test.

Action:
Severity: Minor.
DTD0004
SNMP trap: Yes
Test is not specified in configuration.

Action:
Severity: Minor.
DTD0005
SNMP trap: No
Too many messages from DTD specified by TN.

Action:
Severity: Minor.
DTD0006
SNMP trap: Yes
DTD configured but not used.

Action:
Severity: Minor.
DTD0120
SNMP trap: Yes
Card is disabled unless 50 percent of the cards are already disabled.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 740 of 2360

DTD0121 10 xx
DTD card responded incorrectly to tone test. Card sent input message of xx.
Action:
Severity: Minor.
DTD0122
SNMP trap: No
Card failed Dial Tone Detector Test.

Action:
Severity: Minor.
DTD0123
SNMP trap: No
Card did not respond when DTD test was initialized.

Action:
Severity: Minor.
DTD0124
SNMP trap: No
Card did not respond when test tone was applied.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 741 of 2360
DTI: Digital Trunk Interface Diagnostic

(LD 60)
The Digital Trunk Interface diagnostic program (LD 60) is used to maintain the
following:
QPC472 Digital Trunk Interface (DTI)
QPC720 Primary Rate Interface (PRI)
QPC471 and QPC775 Clock Controller
NTAK09 1.5 Mb/s (DTI/PRI) Interface Card
NTAK10 2.0 Mb/s (DTI) Interface Card
NTAK79 2.0 Mb/s Primary Rate Interface (PRI)
NTAK20 Clock Controller
NTAK93 (PRI) D-channel Handler Interface
Messages
DTI0000
LD 60 identifier.
Action:
Severity: Info.
DTI0001
SNMP trap: No
SNMP trap: Yes
SNMP trap: Yes
Invalid input character.

Action:
Severity: Info.
DTI0002
Invalid command.
Action:
Severity: Info.
DTI0003
Incorrect number of parameters.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 742 of 2360

DTI0004
Incorrect customer number.

Action:
Severity: Info.
DTI0005
SNMP trap: Yes
SNMP trap: Yes
Invalid parameter.
Action:
Severity: Info.
DTI0006
Loop specified is not a DTI/PRI loop. System Option 11 Card specified is not
a DTI/PRI Card.
Action:
Severity: Info.
DTI0007
SNMP trap: Yes
DISI request already active.

Action:
Severity: Info.
DTI0008
SNMP trap: Yes
DISI command is complete.

Action:
Severity: Info.
DTI0009 l ch e
553-3001-411
SNMP trap: Yes
DTI/DTI2/PRI/PRI2 loop or channel failed hardware self test.

For Option 11 systems with PRI2, this message can be followed by DTA105
messages with additional error codes. For DTI/PRI/PRI2 the output data is: l
= loop (for Option 11, l = card) ch = channel e = error code for debug purposes
For DTI2 the output data is: DTI009 l m e
l = loop (for Option 11, l = card)
m = N for NI microprocessor
m = C for CI microprocessor
e = error code for debug purposes.
Error codes for NI microprocessor (m = N):
00 = NI self-test has finished
01 = Undefined messout received
02 = Problem with group 2 error handling (invalid level)
03 = NI to CI FIFO full (128 messages lost)
04 = CI-1 Micro failed to initialize on power-up
05 = NI group 1 error handling - undefined condition found
06 = Bad MESSOUT number 6 encountered
Standard 15.00
January 2006
Page 743 of 2360

07 = NI Messout queue fails
08 = NI Messin queue full
09 = NI priority Messin queue is full
10 = Bad MESSOUT number 10 encountered
11 = TN = 0 read from regular queue
12 = TN = 0 read from priority queue
14 = Bad TN associated with MESSOUT number 4
15 = Bad TN associated with MESSOUT number 15
50 = External RAM in range 880H-8EFH failed (MESSIN queue)
51 = Internal RAM test failed
52 = Pad RAM test failed
53 = External RAM test failed
54 = 8253 timer/counter test failed
55 = Slip counter test failed
56 = Loopback of TS 16 frame 0 failed
57 = Loopback of non fas TS O failed
58 = Echo test to CI-1 micro failed
255 = Loss of NI FIFO synchronization (Stop byte = 0 not found).
DTI009 error codes for CI microprocessor (m = C):
03 = A complete message was not received from NI micro
128 = Message received by CI-1 through FIFO requested an undefined task
129 = Message number 26 contained more than one bit set to indicate which
of the ABCD bits is to be used for PPM
130 = An attempt was made to set the flag to invoke the pulse timer for TS 0
131 = A request for a task defined under Messout 30 has been received with
the TN of TS 0
132 = Attempt was made to enable outpulsing TS 0 or TS 16
133 = A Messout 31 has been received for TS 0 or TS 16 with the pulse hold
time not = 0
134 = An attempt has been made to set the bit to invoke the pulse timer for TS
0 or TS 16
135 = A request for outpulsing was received, but outpulsing data was not
downloaded
137 = A request for PPM counting was received, but the was not downloaded
138 = A Messout 30 was received requesting a task to be performed for DTI
TS 16 which is not allowed
139 = The 8031 on CHIP RAM failed self-test
140 = The TS 16 signaling RAM and/or the TS 16 pick-up buffer failed self-test.
141 = The CI-1 micro external RAM failed self-test
142 = Attempt was made to set/clear the flag used to invoke PPM pulse timing
for DTI timeslot 0 or 16
143 = CI-2 micro responded to echo request message but response was in
error
System Messages
Page 744 of 2360

144 = CI-2 micro failed to respond to request echo message
145 = SL-1 TN of MESSOUT received is not 0 0 7 3 (self-test)
146 = The TN of MESSOUT 26 received was not that or TS 0
147 = The TN of MESSOUT 28 received was not that of TS 0
148 = The TN of MESSOUT 29 received was not that of TS 0
149 = Upon enabling the DTI pack, the CI-1 was unable to write Frame 0, TS
16 with 0B
150 = MESSOUT 26 was received with the PPM counting bit (abcd) all equal
to zero
151 = MESSOUT 28 was received with the outpulsing bit (abcd) equal to zero
152 = CI-2 failed to respond to the CI-1 watch dog message153 = The CI-2
failed to respond to five consecutive watchdog messages and is assumed to
be out-of-service
154 = Messout received requesting the lower nibble of MFAS pattern to be
written with something other than 0000
155 = MESSOUT received requesting 0000 to be written into an abcd state
156 = MESSOUT received with a TN outside the range shelf 0, card 8-1, unit
3-0
157 = CI-1, NI FIFO overflowed, and has been cleared. 128 messages were
lost.
159 = Cannot request complex messaging on ch 0 or ch 16
160 = Message queue for this channel is full
161 = Message queue for this channel is almost full=
163 = TN received was not that of TS 0
164 = Continuous pulse detection not allowed on channel 0
165 = Continuous pulse detection not allowed on channel 16
166 = Maximum continuous pulse time must be greater than the minimum
167 = Cannot have PPM and Continuous Pulse Detection at the same time
168 = Cannot request PPM actions when Continuous Pulse is on
DTI0009 error codes for PRI2. For some failure codes, the pack still attempts
to operate, but can give inconsistent results.
0 = All self tests passed.
1 = Selftest(s) have failed.
2 = Programming of LCAs has failed (the test retries three times).
3 = Code ROM checksum has failed.
4 = Internal RAM test has failed.
5 = External RAM test has failed.
6 = Loss PAD RAM test has failed.
7 = A07 communication test has failed.
8 = UART interface test has failed.
9 = E1 Framer test has failed.
10 = Carrier Line Driver test has failed.
11 = Carrier sync test has failed.
553-3001-411
Standard 15.00
January 2006
Page 745 of 2360

12 = (Inter)national bits test has failed.
13 = Yellow alarm test has failed.
14 = PCM channel test has failed.
15 = Per Loop RLBK test has failed.
16 = Per Chan RLBK test has failed.
Action:
Severity: Info.
DTI0010 loop c
SNMP trap: Yes
System clock c cannot be switched in to replace active clock; or another loop

is already in loopback mode.
Action:
Severity: Info.
DTI0011 c
SNMP trap: Yes
System clock c cannot be switched in because loss of service will result to the
peripheral signaling pack listed.
Action: If the problem persists contact your technical support representative.
1. Identify the GROUP(s) containing the identical PS cards.
2. Identify the IGS card(s) that supplies the clock signal from the indicated clock
to the GROUP(s).
3. Use OVL 39 to disable and re-enable that IGS card(s) (ENL/DIS IGS n).
4. Retry switching clocks (SWCK)
Severity: Info.
DTI0012 x
SNMP trap: No
Network loop/card x pack does not respond from IOTEST; loop/card x is

disabled.
Action:
Severity: Info.
DTI0013 x
SNMP trap: Yes
No channel is available on loop/card x for diagnostic test. No self-test is

performed on loop/card x
Action:
Severity: Info.
DTI0014 x
SNMP trap: Yes
Loop/Card x is in remote loop-back mode; command not allowed

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 746 of 2360

DTI0015 x
Loop/Card x is not specified as primary or secondary clock reference source.

Action:
Severity: Info.
DTI0016
SNMP trap: Yes
The DTI package is not equipped; LD 60 is not allowed to load.

Action:
Severity: Info.
DTI0017
SNMP trap: Yes
Previous command in progress; enter END to abort.

Action:
Severity: Info.
DTI0018 x
SNMP trap: Yes
DISI command for loop/card x aborted.

Action:
Severity: Info.
DTI0019
SNMP trap: Yes
The loop/channel or card/channel is not disabled for self-test or it is already in

the requested set/reset loop-back mode
Action:
Severity: Info.
DTI0020 x
SNMP trap: Yes
Loop/Card x is already disabled. No action is taken.

Action:
Severity: Info.
DTI0021
SNMP trap: Yes
Attempt was made to disable input TTY loop.

Action:
Severity: Info.
DTI0022 x
SNMP trap: Yes
Loop/Card x is already enabled.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 747 of 2360

DTI0023 x ch
Cannot disable/enable loop/card x channel ch.

Action:
Severity: Info.
DTI0024
SNMP trap: Yes
Loop/Card is enabled but no response from hardware.

Action:
Severity: Info.
DTI0025 x ch
SNMP trap: Yes
Loop/Card x channel ch is not equipped.

Action:
Severity: Info.
DTI0026 c r
SNMP trap: Yes
Invalid input parameter to LOVF command for customer c, route r.

Action:
Severity: Info.
DTI0027 x ch
SNMP trap: Yes
Loop/Card x or loop/card x channel ch is not in loopback test mode.

Action:
Severity: Info.
DTI0028 x ch
SNMP trap: Yes
No test result received before timeout from the specified loop/card x or

loop/card
Action:
Severity: Info.
DTI0029 x
SNMP trap: Yes
Loop/card x is enabled but red (local) and yellow (remote) alarms exist
Action:
Severity: Info.
DTI0030 x
SNMP trap: Yes
Loop/card x is enabled but red alarm (local alarm) exists.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 748 of 2360

DTI0031 x
Loop/card x is enabled but yellow alarm (remote alarm) exists.

Action:
Severity: Info.
DTI0032 x
SNMP trap: Yes
Loop/card x is in yellow alarm (remote alarm) state or waiting for yellow alarm
sending seized message from hardware.
Action: Do not perform the automatic/midnight self-test.
Severity: Info.
DTI0033 x
SNMP trap: Yes
Loop/card x is in red/yellow/audit state. Command not allowed.

Action:
Severity: Info.
DTI0034 loop
SNMP trap: Yes
Switching in clock controller is not allowed for this machine type.

Action:
Severity: Info.
DTI0036 x
SNMP trap: Yes
Continuity checker on loop/card x is faulty. Network loop/card x probably faulty

Action:
Severity: Info.
DTI0037 x
SNMP trap: No
Unable to read partial alarm counts from DTI hardware on loop/card x.

Following alarm counts are not complete.
Action:
Severity: Info.
DTI0038 x
SNMP trap: No
No channel is available on loop/card x for diagnostic. Self-test was not

performed.
Action:
Severity: Info.
DTI0039 x
SNMP trap: No
Continuity test failed on loop/card x.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 749 of 2360

DTI0040 x ch
Loopback test failed on loop/card x channel ch.

Action:
Severity: Info.
DTI0041 x
SNMP trap: No
Network memory test failed.

Action: Replace network loop/card x.
Severity: Info.
DTI0042 x ch
SNMP trap: No
No timeslots available for loopback test. Loopback test not tested on channel
ch. If loop/card level test, all channels greater than and including channel ch
not tested.
Action:
Severity: Info.
DTI0043
SNMP trap: No
Another channel already in loopback mode.

Action:
Severity: Info.
DTI0044 x
SNMP trap: No
Loop/card x enabled by midnight routine.

Action:
Severity: Info.
DTI0045 x
SNMP trap: No
Self-test not performed on loop/card x because loop/card x was disabled

manually.
Action:
Severity: Info.
DTI0046 x
SNMP trap: No
Self-test not performed on loop/card x. Loop/card x could not be accessed.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 750 of 2360

DTI0047 x
Self-test not performed on loop/card x since loop/card x is in remote loop back

mode.
Action:
Severity: Info.
DTI0048 x m
SNMP trap: No
DTI loop/card x, Microprocessor m failed echo message self-test.

Action:
Severity: Info.
DTI0049 x ts
SNMP trap: No
Network map in software indicates that timeslot ts of loop/card x is idle but the
connection memory word for that slot on loop/card x is not idle.
Action:
Severity: Info.
DTI0050 x
SNMP trap: No
Continuity checker on loop/card x is faulty. Network loop/card x is probably

faulty.
Action:
Severity: Info.
DTI0051
SNMP trap: No
DB (Clock Controller) is not defined.

Action:
Severity: Info.
DTI0052
SNMP trap: Yes
Tracking rejected. Reference primary is not specified.

Action:
Severity: Info.
DTI0053
SNMP trap: Yes
Unable to track on primary.

Action:
Severity: Info.
DTI0054
SNMP trap: Yes
Tracking rejected. Reference secondary is not specified.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 751 of 2360

DTI0055
Unable to track on secondary.

Action:
Severity: Info.
DTI0056
SNMP trap: Yes
Unable to access clock controller.

Action:
Severity: Info.
DTI0057
SNMP trap: Yes
SNMP trap: Yes
Unable to free run.

Action:
Severity: Info.
DTI0058
Supposed to free run but hardware is tracking on primary.

Action:
Severity: Info.
DTI0059
SNMP trap: Yes
Supposed to free run but hardware is tracking on secondary.

Action:
Severity: Info.
DTI0060
SNMP trap: Yes
Supposed to track on primary but hardware is tracking on secondary.

Action:
Severity: Info.
DTI0061
SNMP trap: Yes
Supposed to track on primary but hardware is free run.

Action:
Severity: Info.
DTI0062
SNMP trap: Yes
Supposed to track on secondary but hardware is tracking on primary

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 752 of 2360

DTI0063
Supposed to track on secondary but hardware is free run.

Action:
Severity: Info.
DTI0064
SNMP trap: Yes
Cannot determine which CPU is in use.

Action:
Severity: Info.
DTI0065
SNMP trap: Yes
System clock must be switched before proceeding.

Action:
Severity: Info.
DTI0066
SNMP trap: Yes
Idle CPU must be switched in for active CPU before proceeding.

Action:
Severity: Info.
DTI0067 c
SNMP trap: Yes
System clock generator c is already enabled.

Action:
Severity: Info.
DTI0068 c
SNMP trap: Yes
System clock generator c is not responding.

Action:
Severity: Info.
DTI0069 x
SNMP trap: Yes
Unable to track on loop/card x.

Action:
Severity: Info.
DTI0070
SNMP trap: No
Clock cannot be switched. Unable to track the reference loop/card.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 753 of 2360

DTI0071
The ENCH loop/card ch command is not allowed here because the channel is
Action:
Severity: Info.
DTI0072
SNMP trap: No
.ERROR_72 : "PRA B-Channel cannot be used as the D-Channel is not

established.'
Action:
Severity: Info.
DTI0073 loop
SNMP trap: No
If loop is a QPC720, then the pack is not responding. If loop is a QPC472, then
ignore this message.
Action:
Severity: Info.
DTI0074 n
SNMP trap: Yes
The clock controllers cannot be switched because clock controller n is

software disabled.
Action: Enable the disabled pack provided it is operational.
Severity: Info.
DTI0075
SNMP trap: No
You should wait for one minute to do another clock switch!

If you still want to switch the clock use the SWCK FRCE command.
Action:
Severity: Info.
DTI0081
SNMP trap: No
B-channel cannot be enabled until a DCH Link is established

Action:
Severity: Info.
DTI0096
SNMP trap: No
Loopback test on DTI2 is not supported on Option 11 since Release 20B.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 754 of 2360

DTI0097
Disabling of this DTI2 loop is not allowed because it is providing primary or

secondary reference clock to the system and automatic switchover of the
reference clocks has been disabled.
Action: If this loop must be disabled for maintenance, then LD60 and enter
command EREF to allow switchover of the ref clock. Afterwards, MREF can be
entered to disallow automatic switchover again.
Severity: Info.
DTI0098
SNMP trap: No
Command entered applies to 1.5 Mb DTI only.

Action:
Severity: Info.
DTI0099
SNMP trap: No
Command entered applies to 2.0 Mb DTI only.

Action:
Severity: Info.
DTI0100 x
SNMP trap: No
DTI link loop/card x is associated with an indirect command and Status Link.
Loop/card x cannot be disabled until the CSL is disabled.
Action:
Severity: Info.
DTI0101
SNMP trap: Yes
Server using channel for maintenance, cannot Remove Link.

Action:
Severity: Info.
DTI0108
SNMP trap: Yes
No clock has been found in side S. This indicates that either there is no clock
in side S or the clock installed in side S has its shelf-side switch set wrong.
Action:
Severity: Info.
DTI0200
SNMP trap: No
Warning: There is an active clock controller on the digital trunk card. If your
intent is to remove the card from the shelf, disable the clock controller before
removing the card from the shelf. (Option 11 only)
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 755 of 2360

DTI0202 l
DTI loop l with LCMT B8ZS cannot be enabled because a QPC720 card is
required.
Action:
Severity: Info.
DTI0203 l
SNMP trap: Yes
DTI loop l with ESF framing format cannot be enabled because a QPC720
card
Action:
Severity: Info.
DTI0204
SNMP trap: Yes
PRI2 card cannot be enabled because it may be in a wrong slot.

Action:
Severity: Info.
DTI0205
SNMP trap: Yes
Clock found in group G side S is different from its address found during system
initialization. No attempt to overwrite the address found during initialization.
Action:
Severity: Info.
DTI0206
SNMP trap: Yes
More than one clock has been found in side S. The information on Group of
the extra clock(s) is provided.
Action:
Severity: Info.
DTI0207
SNMP trap: Yes
No clock has been found in side S. This indicates that either there is no clock
in side S or the clock in side S has its shelf-side switch set wrong.
Action:
Severity: Info.
DTI0208
SNMP trap: Yes
The command requested by the craft person is not applicable for Phantom
DTI2 loops.
Action: Repeat the command on non-Phantom DTI2 loops.
Severity: Info.
SNMP trap: No
System Messages
Page 756 of 2360

DTI0209
Device locked by the Russian Call Monitoring feature. The command was not
executed.
Severity: Info.
DTI0210
SNMP trap: Yes
The clock should not be switched.

Action:
Severity: Info.
DTI4130
SNMP trap: Yes
Incompatible protocol between the interfaces.

Action: If this error continues, report it.
Severity: Info.
DTI4131
SNMP trap: No
Incompatible protocol between the interfaces.

Action: If this error continues, report it.
Severity: Info.
DTI4134
SNMP trap: No
No blocking on an outgoing route only.

Action: Check the configuration and then try again.
Severity: Info.
DTI4135
SNMP trap: No
Cannot enable DTI loop unless the TMDI card is operational.

Action: Ensure the card is plugged in, then enable the card.
Severity: Info.
DTI4136
SNMP trap: Yes
Attempt to enable T1E1 application or port failed.

Action: Try ENLL again, or try RST TMDI command in overlay 96.
Severity: Info.
DTI4137
SNMP trap: Yes
Attempt to enable T1E1 port failed.

Action: Try ENLL again, or try RST TMDI command in overlay 96.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 757 of 2360

DTI4138
Set MSDLMISP PTR failed during enabling of T1E1 port. Data corruption may
have occurred.
Action: Problem may be corrected by system initialization. If not contact your
Severity: Info.
SNMP trap: Yes
System Messages
Page 758 of 2360
553-3001-411
Standard 15.00
January 2006
Page 759 of 2360
DTM: Digital Trunk Maintenance (LD 75)

The DTM messages indicate problems with digital trunks detected by the
Digital Trunk Maintenance program (LD 75).
Messages
DTM0000
Program Identifier
Action:
Severity: Minor.
DTM0001
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Too many characters.

Action:
Severity: Minor.
DTM0002
Invalid character input.

Action:
Severity: Minor.
DTM0003
Invalid command.
Action:
Severity: Minor.
DTM0004
Wrong number of parameters.

Action:
Severity: Minor.
DTM0005
SNMP trap: No
SNMP trap: No
Invalid parameter.
Action:
Severity: Minor.
DTM0006
Invalid customer number.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 760 of 2360

DTM0020
Card is not configured.

Action:
Severity: Minor.
DTM0021
SNMP trap: No
Card number is not specified.

Action:
Severity: Minor.
DTM0022
SNMP trap: No
Card number is out-of-range.

Action:
Severity: Minor.
DTM0023
SNMP trap: No
Card is already enabled.

Action:
Severity: Minor.
DTM0024
SNMP trap: No
SNMP trap: No
Card does not respond.

Action:
Severity: Minor.
DTM0025
Loop is not a DTCS/DDCS.

Action:
Severity: Minor.
DTM0026
SNMP trap: No
DTSL/DDSL is disabled.
Action:
Severity: Minor.
DTM0027
SNMP trap: No
Signaling link is not available.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 761 of 2360

DTM0030
Command is not allowed.

Action:
Severity: Minor.
DTM0040
SNMP trap: No
Message output has failed.

Action:
Severity: Minor.
DTM0042
SNMP trap: No
DTCS/DDCS cannot be disabled while its DTS1/DDSL is enabled.

Action:
Severity: Minor.
DTM0043
SNMP trap: No
SNMP trap: No
Not a DTSL/DDSL.
Action:
Severity: Minor.
DTM0046
Trunk is not a DASS2 card.

Action:
Severity: Minor.
DTM0047
SNMP trap: No
DTCS/DDCS is disabled.
Action:
Severity: Minor.
DTM0048
SNMP trap: No
Channel is already disabled.

Action:
Severity: Minor.
DTM0049
SNMP trap: No
A previous DISI has not completed.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 762 of 2360

DTM0050
Message not defined by MSG.

Action:
Severity: Minor.
DTM0051
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Invalid byte.
Action:
Severity: Minor.
DTM0052
Invalid channel number.

Action:
Severity: Minor.
DTM0053
Per Sig is disabled.

Action:
Severity: Minor.
DTM0054
Action was not successful.

Action:
Severity: Minor.
DTM0055
SNMP trap: No
SNMP trap: No
DISI complete.
Action:
Severity: Minor.
DTM0300 n
DTSL/DDSL n has been stopped and is in the ENBL IDLE state.

Action:
Severity: Minor.
DTM0301 n
SNMP trap: Yes
DTSL/DDSL n has been started and is in the ENBL ACTIVE state.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 763 of 2360

DTM0302 n
DTSL/DDSL n has been started and is in the ENBL ACTIVE state but all of the
channels are in the disabled state.
Action:
Severity: Minor.
DTM0303 n
SNMP trap: Yes
DTSL/DDSL n has failed to start and is still in the ENBL STARTING state.
Action:
Severity: Minor.
DTM0304 n f
SNMP trap: Yes
DTSL/DDSL n has failed its memory test while being enabled and remains in
the disabled state. "f" indicates the reason for failure as follows: 0 test not
completed in time 1 ROM check failed 2 RAM check failed 4 HDLC test failed
Action:
Severity: Minor.
DTM0305 n
SNMP trap: Yes
DTSL/DDSL n is undergoing memory test, command has been ignored.

Action:
Severity: Minor.
DTM0306 n
SNMP trap: Yes
DTSL/DDSL n is being started, command has been ignored.

Action:
Severity: Minor.
DTM0307 n
SNMP trap: Yes
DTSL/DDSL n is being stopped, command has been ignored.

Action:
Severity: Minor.
DTM0308 n
SNMP trap: Yes
Five minutes have elapsed since DTSL/DDSL n was started and put in he
active state and no channel reset acknowledgments have been received.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 764 of 2360

DTM0309 n
DTSL/DDSL n has failed to start and will return to the idle state.
Action:
Severity: Minor.
DTM0310 n z
SNMP trap: Yes
Alarm z has been detected by DDSL/DTSL n and it persisted for a time greater
than the persistence time defined for that alarm. The alarm z is a code number
that is indicated as follows:
0 = TBF Transmit Buffer Full
1 = FAE Frame Alignment Error
2 = HER High Error Rate
3 = TSF Transmit Signaling Failure
4 = AIS Alarm Indication Signal
5 = LOI Loss of Input
6 = DAI Distant Alarm Indication
Action:
Severity: Info.
DTM0311 n z
SNMP trap: Yes
Alarm z has been detected by DTSL/DDSL n but did not persist for a period
greater than the persistence time. The alarm z is a code number that is
indicated as follows: 0 = TBF - Transmit Buffer Full 1 = FAE - Frame Alignment
Error 2 = HER - High Error Rate 3 = TSF - Transmit Signaling Failure 4 = AIS
- Alarm Indication Signal 5 = LOI - Loss of Input 6 = DAI - Distant Alarm
Indication
Action:
Severity: Minor.
DTM0312 n z
SNMP trap: Yes
Alarm repeat count threshold has been exceeded for alarm z on DTSL/DDSL
n.
The alarm z is a code number that is indicated as follows:
0 = TBF Transmit Buffer Full
1 = FAE Frame Alignment Error
2 = HER High Error Rate
3 = TSF Transmit Signaling Failure
4 = AIS Alarm Indication Signal
5 = LOI Loss of Input
6 = DAI Distant Alarm Indication
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 765 of 2360

DTM0313 n
Stop count threshold has been exceeded for DTSL/DDSL n.

Action:
Severity: Minor.
DTM0314 n
SNMP trap: Yes
DTSL/DDSL n has been disabled.

Action:
Severity: Minor.
DTM0315 n
SNMP trap: Yes
DTSL/DDSL n failed to respond to numerous "stop" messages and it will be

disabled.
Action:
Severity: Minor.
DTM0316 n z
SNMP trap: Yes
Alarm z has been detected by DTSL/DDSL n. DTSL/DDSL is not in the active

state. The alarm z is a code number that is indicated as follows: 0 = TBF Transmit Buffer Full 1 = FAE - Frame Alignment Error 2 = HER - High Error
Rate 3 = TSF - Transmit Signaling Failure 4 = AIS - Alarm Indication Signal 5
= LOI - Loss of Input 6 = DAI - Distant Alarm Indication
Action:
Severity: Minor.
DTM0317 n
SNMP trap: Yes
DTSL/DDSL n does not respond.

Action:
Severity: Minor.
DTM0318 n
SNMP trap: Yes
DTSL/DDSL n has been enabled.

Action:
Severity: Minor.
DTM0319 n
SNMP trap: Yes
DTSL/DDSL n is about to be started.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 766 of 2360

DTM0320 n c
Real channel c on DTSL/DDSL n has failed to reset and remains in the

disabled state.
Action:
Severity: Minor.
DTM0321 n c
SNMP trap: Yes
Virtual channel c on DTSL/DDSL n failed to reset and remains in the disabled

state.
Action:
Severity: Minor.
DTM0322 n c
SNMP trap: Yes
Real channel c on DTSL/DDSL n has been reset.

Action:
Severity: Minor.
DTM0323 n c
SNMP trap: Yes
Virtual channel n on DTSL/DDSL n has been reset.

Action:
Severity: Minor.
DTM0324 n
SNMP trap: Yes
Channel reset threshold has been exceeded for DTSL/DDSL n.

Action:
Severity: Minor.
DTM0325 n
SNMP trap: Yes
DTSL/DDSL n is being reset.

Action:
Severity: Minor.
DTM0326 n
SNMP trap: Yes
DTSL/DDSL n has been reset.

Action:
Severity: Minor.
DTM0329 n c
SNMP trap: Yes
Channel is not in a state where it can be reset.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 767 of 2360

DTM0330 n
Invalid command for the current state of DTSL/DDSL n.

Action:
Severity: Minor.
DTM0331 n
SNMP trap: Yes
Test message threshold has been exceeded for DTSL/DDSL n.

Action:
Severity: Minor.
DTM0332 n
SNMP trap: Yes
A level 3 to level 2 signaling test has failed for DTSL/DDSL n.

Action:
Severity: Minor.
DTM0335 n mi
SNMP trap: Yes
DTSL/DDSL n has failed to respond to a message sent to it. Mi gives the

message indicator code of the message.
Action:
Severity: Minor.
DTM0336 n mi
SNMP trap: Yes
An attempt to send a message to DTSL/DDSL n has failed. Mi gives the

message indicator code. (This is likely to be followed by a false DTM335
message.)
Action:
Severity: Minor.
DTM0337 n li mi
SNMP trap: Yes
Invalid input from DTSL/DDSL n. Li gives the length indicator. Mi gives the
message indicator code.
Action:
Severity: Minor.
DTM0338 n
SNMP trap: Yes
DTSL/DDSL n cannot be enabled because the DTCS/DDCS is disabled.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 768 of 2360

DTM0339 n x
Five minutes have elapsed since DTSL/DDSL n was started and put in the
active state. Some channel reset acknowledgments have been received, but
x channels failed to start.
Action:
Severity: Minor.
DTM0340 n
SNMP trap: Yes
Although DTSL/DDSL n is active according to level 3, a report has been

received from level 2 indicating that the link is idle.
Action:
Severity: Minor.
DTM0341 n
SNMP trap: Yes
Although DTSL/DDSL n is idle according to level 3, a report has been received

from level 2 indicating that the link is starting or active.
Action:
Severity: Minor.
DTM0342 n c p
SNMP trap: Yes
Level 2 has detected a discrepancy in the configuration of real channel c on

DTSL/DDSL n when a message was sent from level 3. The problem is
indicated by: p = 0 channel number is out-of-range p = 1 channel is not
configured p = 4 channel is not active p = 5 li is incorrect p = 6 already
configured p = 7 mi is out-of-range
Action:
Severity: Minor.
DTM0343 n
SNMP trap: Yes
Level 2 has detected a discrepancy in the configuration of virtual channel c on

DTSL/DDSL n when a message was sent from level 3. The problem is
configured p = 4 channel is not active p = 5 li is incorrect p = 6 already
configured p = 7 mi is out-of-range
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 769 of 2360

DTM0344 n c p

DTSL/DDSL n when a frame was received from the link. The problem is
configured p = 2 type (DPNSS1/DASS2) is wrong p = 3 side (A/B) is wrong p
= 4 channel is not active
Action:
Severity: Minor.
DTM0345 n c p
SNMP trap: Yes

DTSL/DDSL n when a frame was received from the link. The problem is
configured p = 2 type (DPNSS1/DASS2) is wrong p = 3 side (A/B) is wrong p
= 4 channel is not active
Action:
Severity: Minor.
DTM0346 n c p
SNMP trap: Yes

DTSL/DDSL n when a message was received from level 2. The problem is
indicated by: p = 2 type (DPNSS1/DASS2) is wrong p = 3 side (A/B) is wrong
Action:
Severity: Minor.
DTM0347 n c p
SNMP trap: Yes

DTSL/DDSL n when a message was received from level 2. The problem is
indicated by:
p = 2 type (DPNSS1/DASS2) is wrong
p = 3 side (A/B) is wrong
Action:
Severity: Info.
DTM0348 n
SNMP trap: Yes
All alarms have been cleared on DTSL/DDSL n.

Action:
Severity: Info.
DTM0349 n
SNMP trap: Yes
Flow control is set on DTSL n which is earlier than vintage G.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 770 of 2360

DTM0350
Must switch reference clock before disabling.

Action:
Severity: Minor.
DTM0400
SNMP trap: No
PBX synchronized on main.

Action:
Severity: Minor.
DTM0401
SNMP trap: Yes
PBX synchronized on main, standby failed.

Action:
Severity: Minor.
DTM0402
SNMP trap: Yes
Main synchronization input failed, system synchronized on standby.

Action:
Severity: Minor.
DTM0403
SNMP trap: Yes
Main synchronization input failed, system synchronized on standby.

Action:
Severity: Minor.
DTM0404
SNMP trap: Yes
Main synchronization input failed, standby was faulty and now attempting to
lock.
Action:
Severity: Minor.
DTM0405
SNMP trap: Yes
Main synchronization input failed, no standby exists or standby not locked on.
Action:
Severity: Minor.
DTM0406
SNMP trap: Yes
Main synchronization and standby synchronization inputs failed, PBX no

longer
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 771 of 2360

DTM0407
Main synchronization and standby synchronization inputs failed, PBX no

longer synchronized.
Action:
Severity: Info.
DTM0408
SNMP trap: Yes
Standby failed then main lost synchronization, PBX not synchronized.

Action:
Severity: Minor.
DTM0409
SNMP trap: Yes
PBX may not be synchronized; different synchronization card states detected.

Action:
Severity: Info.
DTM0410 n
SNMP trap: Yes
PBX may not be synchronized; synchronization card n is in invalid state for

configured mode.
Action:
Severity: Info.
DTM0411
SNMP trap: Yes
Synchronization card(s) being reset for synchronization purposes.

Action:
Severity: Minor.
DTM0412
SNMP trap: Yes
Maximum resets attempted on sync card(s).

Action:
Severity: Minor.
DTM0413 n
SNMP trap: Yes
Synchronization card n is disabled.

Action:
Severity: Minor.
DTM0414 n
SNMP trap: Yes
Synchronization card n is not responding.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 772 of 2360
553-3001-411
Standard 15.00
January 2006
Page 773 of 2360
DTRK: Digital Trunk Diagnostic (LD 60)

The DTRK messages indicate problems with Digital Trunks detected by the
resident Trunk Diagnostic program.
Messages
DTRK0433
Timeout when waiting for ready to outpulse.

Action:
Severity: Info.
DTRK0434
SNMP trap: Yes
Timeout when waiting for stop outpulse.

Action:
Severity: Info.
DTRK0437
SNMP trap: Yes
Failure to receive second half of OPCA or OPRC.

Action:
Severity: Info.
DTRK0438
SNMP trap: Yes
Timeout when waiting for first half of next OPCA or OPRC.

Action:
Severity: Info.
DTRK0439
SNMP trap: Yes
Timeout when waiting for second half of network call

Action:
Severity: Info.
DTRK0440
SNMP trap: Yes
Failure to receive second half of WNKS signal (GLARE

Action:
Severity: Info.
DTRK0500
SNMP trap: Yes
A Forward Release message has been sent on loop/card l

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 774 of 2360

DTRK0501 tn
A WNKS signal of invalid duration has been received.

Action:
Severity: Info.
DTRK0502 tn
SNMP trap: Yes
An unexpected seize message has been received on a disconnecting trunk.

Action:
Severity: Info.
SNMP trap: Yes
DTRK0503 loop channel An unrecognized message subtype in Messin 28 received from DTI2
loop on CDT2 card.
Action:
Severity: Minor.
SNMP trap: Yes
DTRK0504 loop channel DP digits collection report received from CDTI2 trunk which is not
defined with CLS DIPF.
Action:
Severity: Minor.
SNMP trap: Yes
DTRK0505 loop channel A recognized DP digits collection report from CTI2 trunk.
Action:
Severity: Minor.
SNMP trap: Yes
DTRK0506 loop channel A problem was discovered by CDTI2 FW during DP digits collection.
Action:
Severity: Minor.
SNMP trap: Yes
DTRK0507 loop channel An unexpected CDTI2 CIS special signaling input received. It is
permissible only for CDTI2 loops with CISFW=YES defined in LD73.
Action:
Severity: Minor.
SNMP trap: Yes
DTRK0508 loop channel An unrecognized CDTI2 CIS special signaling input received.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 775 of 2360

DTRK0509
A problem was discovered by CDT12 FW during MFS protocol performing.

Action:
Severity: Minor.
DTRK0510
SNMP trap: Yes
CIS MFS bad transmission threshold exceeded.

Action:
Severity: Info.
DTRK0511
SNMP trap: No
CIS MFS bad transmission threshold exceeded.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 776 of 2360
553-3001-411
Standard 15.00
January 2006
Page 777 of 2360
EDD: Equipment Data Dump (LD 43)

The Equipment Data Dump program is used to keep equipment data on the
system storage device up to date. When the datadump Overlay program is
invoked, data in the read/write memory is written to the storage device at the
location reserved for it. This includes any data that has been changed or
added.
The program can be invoked daily as part of the daily routines or loaded
manually. Problems with the datadump operation are indicated by EDD
messages.
Messages
EDD0000
Ready for commands.

Action:
Severity: Info.
EDD0003
SNMP trap: Yes
Storage device not ready.

Action: Check that tape cartridge or diskettes are correctly seated.
Severity: Critical.
EDD0005
SNMP trap: Yes
Tape unit has sensed an early warning mark while attempting to write a test
record. The tape is probably full.
Action: Do not attempt to dump to remaining tapes. Notify Northern Telecom.
Severity: Critical.
EDD0006
SNMP trap: Yes
Storage device read error.

Action: Attempt dump again.
Severity: Critical.
EDD0007
SNMP trap: Yes
Storage device write error.

Action: Attempt dump again.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 778 of 2360

EDD0008
Storage device disabled.

Action:
Severity: Critical.
EDD0009
SNMP trap: Yes
SNMP trap: Yes
90 minute timeout.
Action:
Severity: Critical.
EDD0010
Invalid command or incorrect parameter.

Action:
Severity: Info.
EDD0016
SNMP trap: Yes
Incorrect data. Dump is inhibited to prevent writing bad data to storage

medium.
Action: Investigate and clear any SYSxxx messages which may appear
concurrently with this message, then attempt to datadump onto a second copy of
the Storage medium.
If EDD016 is printed again, enter the EDD CLR command, then reload from the
new copy to check that data is now valid. If this is done after a reload, the only
further cause would be CED203.
On dual-memory machines, the indicated memory pack should be retested and
reenabled (data will be copied from the other memory). If this fails again (or for
single memory machines), use EDD CLR to dump data to a second copy of the
storage medium, then reload and check any SYS or INI errors for possible data
corruption.
Severity: Critical.
EDD0020 c
SNMP trap: Yes
EOF tape write fault; record count c (normally 9). X08: Tape unit not idle.
Attempt dump again.
Action:
Severity: Critical.
EDD0021
SNMP trap: Yes
Tape unit not idle. Attempt dump again.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 779 of 2360

EDD0022
Data corrupted in tree block.

Action:
Severity: Critical.
EDD0023
SNMP trap: Yes
Double density loop has single density card in upper unit.

Action:
Severity: Critical.
EDD0024
SNMP trap: Yes
Tape ID does not match system. Incorrect cartridge being used.

Action:
Severity: Critical.
EDD0025 a b t
SNMP trap: Yes
The tape unit has sensed the early-warning mark but is unable to write an
end-of-file mark. Two possible causes are:
1. Record "a" does not match record "b", and/or
2. Record "b" is not a data record (e.g., the record that was read was type t
when a data record was expected). In either case, do not dump to remaining
tapes.
Action:
Severity: Critical.
EDD0029
SNMP trap: Yes
Floppy disk is write protected.

Action:
Severity: Critical.
EDD0033
SNMP trap: Yes
Command not allowable for systems not equipped with a hard disk primary
device.
Action:
Severity: Critical.
EDD0035
SNMP trap: Yes
Configured loops exceed system loop limit.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 780 of 2360

EDD0038
"HM" option is not allowed because the BGD is not equipped.

Action:
Severity: Critical.
EDD0039
SNMP trap: Yes
Audit indicates Peripheral Controller and the superloop data do not agree. The
datadump is aborted.
Action: Redefine the Peripheral Controller or superloop data using LD 97, or use
the SA option for the EDD command.
Severity: Critical.
EDD0040 c
SNMP trap: Yes
It does not allocate storage either for ovflw_ptr_block or ovflw_Index_block.

Action: Remove all the authcodes for customer c and create new authcode for it.
Severity: Critical.
EDD0041
SNMP trap: Yes
Your GPHT data is corrupted.

Action:
Severity: Critical.
EDD0042
SNMP trap: Yes
Backup to floppy unsuccessful.

Action: Please contact technical support group.
Severity: Major.
EDD0060
SNMP trap: Yes
Not able to allocate enough unprotected data store (UDS) for authcode
conversion. Auth data block and sorted table are not converted. The required
number of words in UDS is displayed.
Action:
Severity: Critical.
EDD0074
SNMP trap: No
Conversion: number of leading digits to insert for digit manipulation table is

greater than 20. The table is lost.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 781 of 2360

EDD0075
The digit manipulation table being converted is lost. Either 256 tables already
exist or unprotected data store cannot be allocated.
Action:
Severity: Critical.
EDD0076
SNMP trap: No
The Classcode of the authcode being converted does not match any in the
Auth table. The authcode is discarded.
Action:
Severity: Critical.
EDD0100
SNMP trap: No
SNMP trap: Yes
Corruption in FFC tree.

Action:
Severity: Critical.
EDD0102
There was a data base conversion between the Source data base and the
Target Release issue. No backward datadump is allowed.
Action:
Severity: Critical.
EDD0104
SNMP trap: No
Corruption has occurred in the DN PSA tree.

Action:
Severity: Critical.
EDD0106
SNMP trap: Yes
The data of a set being moved by automatic set relocation is not dumped
because its originating TN is already occupied.
Action: The set data must be reentered.
Severity: Critical.
EDD0110
SNMP trap: No
SNMP trap: Yes
Invalid Flash selection

Action:
Severity: Critical.
System Messages
Page 782 of 2360

EDD0114
Cannot find DSL data.

Action:
Severity: Critical.
EDD0115
SNMP trap: Yes
SNMP trap: Yes
Cannot find USID map.

Action:
Severity: Critical.
EDD0116
Cannot find protected Multipurpose ISDN Signaling Processor (MISP) loop

block.
Action:
Severity: Critical.
EDD0117
SNMP trap: Yes
TN of agent key on ACD supervisor does not link to an ACD agent.

Action:
Severity: Critical.
EDD0119
SNMP trap: Yes
Corruption is detected in the data structure for TTY x. Data for TTY x is not
dumped.
Action:
Severity: Critical.
EDD0120
SNMP trap: Yes
Data dump is inhibited, since an IDC tree and its related SDID tree are found
to be inconsistent. Load Overlay 49 to correct the problem. If need to perform
the data dump regardless, use EDD CLR option.
Warning: The EDD CLR command will cause the inconsistent IDC and SDID
tree to be dumped to the storage medium.
Action:
Severity: Critical.
EDD0122
SNMP trap: Yes
Cannot create/open alarm management db file.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 783 of 2360

EDD0123
Cannot close alarm management db file.

Action:
Severity: Critical.
EDD0124
SNMP trap: No
Cannot make a backup of the existing alarm management data base.

Action:
Severity: Critical.
EDD0125
SNMP trap: No
Error occurred writing alarm management data base.

Action:
Severity: Critical.
EDD0126
SNMP trap: No
Not all patches are saved on the CPU backup flash drive.
Severity: Info.
EDD0127
SNMP trap: No
Insufficient protected data space to buffer an MWNS dump table.The MWNS

data dump has not been completed.
Severity: Major.
EDD0128
SNMP trap: Yes
Did not get data dump completion confirmation from OAM Task.
Action: Do a data dump one more time. If the problem still persists, contact your
Severity: Major.
EDD0129
SNMP trap: Yes
Cannot send messages to the Mbility task (OAMSRV) for data dump.
Action: Do a data dump one more time. If the problems still persists, contact your
Severity: Major.
EDD0150
SNMP trap: Yes
A corrupted DPNSS/DASS2 trunk is observed.

Severity: Info.
SNMP trap: No
System Messages
Page 784 of 2360

EDD0151
Invalid input format for DWL xx, SWP xx, RES xx, or RIB xx.
Action:
Severity: Info.
EDD0152
SNMP trap: Yes
Cabinet number out of range.

Action:
Severity:
EDD0153
SNMP trap: Yes
Cabinet number out of range.

Action:
Severity: Info.
EDD0154
SNMP trap: Yes
The Secondary Call Server currently does not allow the use of this EDD
command.
Action: Action: Check the Secondary Call Server status in LD 135, using
command STAT GR.
Severity: Major.
EDD0155
SNMP trap: Yes
BKR/RSR/DAT cannot be performed since the backup rule does not exist.
Action: Action: Correct the definitions or command parameter.
Severity: Info.
EDD0156
SNMP trap: Yes
BKR/RSR command: Too few parameters.

Action: Action: Re-enter the command, using correct syntax.
Severity: Info.
EDD0157
SNMP trap: Yes
30 minutes Timeout for BKR/RSR/DAT R V commands. Note: Remote (FTP)

transfer of huge Database may take more than the above mentioned 30
minutes. After the printing of this EDD message, the
administration/maintenance work can be performed even though the last
entered command in LD 43 continues. Warning: "EDD" command aborts any
running LD 43 command.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 785 of 2360

EDD9999
Horizon or Venus telephones present: Data Dump not carried out

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 786 of 2360
553-3001-411
Standard 15.00
January 2006
Page 787 of 2360
ELAN: Ethernet Local Area Network

Messages
ELAN0000
ELAN Server disabled, fail to spawn task tELAN_svr

Action:
Severity: Major.
ELAN0001
SNMP trap: No
ELAN Server disabled, fail to open socket

Action:
Severity: Major.
ELAN0002
SNMP trap: No
ELAN Server disabled, can't bind socket to local IP address

Action:
Severity: Major.
ELAN0009
SNMP trap: No
ELAN x host IP=a.b.c.d disabled, write to socket fail due to far end disconnect
or network interface problems
where x is the link number
a.b.c.d. is the IP address
Action:
Severity: Major.
ELAN0014
SNMP trap: Yes
ELAN x host IP=a.b.c.d is enabled

where x is the link number
a.b.c.d. is the IP address
Action:
Severity: Information.
ELAN0023
SNMP trap: Yes
vtServerRx: tcp Status = x, TCP rx socket error

treat it as a connection loss and send an error message to
RUDP.
Where x is equal to the following:
x = 2; tcp read fail
x = 3; tcp write fail
System Messages
Page 788 of 2360

x = 4; tcp write buffer full
x = 5; tcp write time out
x = 6; rudp link down, also tear down TCP
Action:
Severity: Major.
ELAN0024
SNMP trap: Yes
tcp write fatal error! ERRNO is <error number>.

Action: A fatal communication error has occurred with one of the systems
servers, check the status of your servers to ensure proper operation.
Severity: Major.
ELAN0025
SNMP trap: Yes
tcp error: tcp write fail too many times!! ERRNO is <error number>.
Action: A fatal communication error has closed the link with one of the systems
servers, check the status of your servers to ensure proper operation.
Severity: Major.
ELAN0026
SNMP trap: Yes
tcp error: too many msg can't be written!! ERRNO is xxx

Action:
Severity: Major.
ELAN0027
SNMP trap: Yes
Parameters: 6
IP address of card/server (4 octets)
Major and Minor version of IPL (2)
Action: Upgrade software on IP Line card and Signaling Server.
Severity: Minor.
ELAN0028
SNMP trap: No
The service failed to register their pbxLink. The service IP <ip address>, host
name <server name>, server type <server type>.
Action: Check connections and IP configurations of the server.
Severity: Major.
ELAN0029
SNMP trap: Yes
The server has registered with the CS but can not be found in the <file name>
file. IP <ip address>, hostName <server name>, hostType <server type>.
Action: Check connections and IP configurations of the server.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 789 of 2360
EMR: Emergency Key (ACD)

In the event of an emergency situation, an ACD agent can press the
Emergency (EMR) key to establish a No Hold Conference with a supervisor,
and begin recording the call. When the key is pressed an EMR message
appears on the TTY noting pertinent information.
Messages
EMR0100
This message is output to the TTY when an ACD Emergency key is pressed.
The message appears in one or more of the following formats: EMR100 RC L
S C U RR MMM; EMR100 AG XXXX YYYY; EMR100 OR L S C U RR MM
Where: RC = Recording trunk for the emergency recorder, L = Loop for the
recording trunk, S = Shelf for the recording trunk, C = Card for the recording
trunk, U = Unit for the recording trunk, RR = Recording trunk Route number,
MMM = Recording trunk Member number, AG = Agent that pressed the EMR
key, XXXX = ACD DN assigned to that agent, YYYY = Agent Position ID (POS
ID), OR = The Originator. Prior to X11 Release 14, ACD DN and Position ID
digits are shown in reverse order. The character "A" indicates a "0," and the
character "0" indicates the end of the number. For example, output "01A4"
identifies the ACD DN 401, while the Position ID 5412 would be output as
2145.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 790 of 2360
553-3001-411
Standard 15.00
January 2006
Page 791 of 2360
ERR: Error Monitor (Hardware)

This resident program monitors call processing continuously. When the call
processing software detects information that is not in the correct format, or
when invalid information is detected, an ERR message is printed.
Messages
ERR0001
No MWI NSI table corresponds to the NSI string received.

Action: Check the MWI NSI table in OVL 15.
Severity: Minor.
ERR0002
SNMP trap: Yes
The NSI string received does not match the corresponding MWI NWI table.
Action: Compare the MWI NSI table in OVL 15 to the manufacturer's
requirements.
Severity: Minor.
ERR0003
SNMP trap: Yes
A Syntax error in the MWI NSI string received.

Action: Compare the MWI NSI table in OVL 15 to the manufacturer's
requirements.
Severity: Minor.
ERR0004
SNMP trap: Yes
RAN announcement for AANN could not be given.

x = Customer
y = Route
Action: Check RAN device.
Severity: Info.
ERR0005 tn
SNMP trap: Yes
Waiting for further Information.

Action: Upgrade the firmware of the set on that tn.
Severity: Minor.
ERR0006 tn
SNMP trap: Yes
CLT or RLT key can only be used on terminals with Phase 3, or higher
firmware.
Action: Upgrade firmware of the set on that tn.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 792 of 2360

ERR0007 tn
The language selection download has been rejected by the M3900 set. The
language set on the terminal does not support the desired language.
Action: Download a new language set to the terminal, or accept the default
language on the set.
Severity: Minor.
ERR0008 tn1 tn2
SNMP trap: Yes
Call drop due to IPTN failure.

TN1 - PTN
TN2 - VTN
Action:
Severity: Major.
ERR0009
SNMP trap: Yes
There is no VTN corresponding to the DMC index.

Action:
Severity: Minor.
ERR0010 loop
SNMP trap: Yes
Input message from unequipped loop. If the loop is physically present, then
either it should not be there or the data is incorrect. If the loop is not present,
the peripheral signaling card on that shelf is suspect.
Action: Run Background Signaling and Switching Diagnostic (LD 45).
Severity: Minor.
ERR0011 l s c u
SNMP trap: Yes
Password retry failed three (3) times.

Action:
Severity: Info.
ERR0020 l s c
553-3001-411
SNMP trap: Yes
Input message received from unequipped PE pack l s c. No data exists for any
TN on this pack, which is disabled to prevent further input. If all messages from
same pack or from same PE shelf. Suspect: PE pack l s c (if present)
Peripheral buffer on loop l shelf s Network loop s, Cables connecting network
and peripheral shelves, Other PE packs on loop l shelf s connectors. If all
messages from loop L (various shelves). Suspect: 1. Network loop l or
associated cables or connectors 2. Any peripheral buffer pack on loop l. For
SL-1 XN: Messages occur only when a specific System Clock Generator
(SCG) is providing clock and loops in all groups are affected. Suspect: 1.
QPC411 SCG providing clock when messages occur 2.Any QPC412
Intergroup Switch (IGS). Messages occur only when a specific SCG is
providing clock and loops on both shelves of one group are affected. Suspect:
Standard 15.00
January 2006
Page 793 of 2360

1. QPC412 IGS associated with affected group when messages occur 2.
Cable connecting the SCG and IGS packs via the Junctor. Messages are all
from loops on the same network shelf. Suspect: 1. Peripheral signaling pack
on affected shelf 2.QPC412 IGS on affected shelf 3. Any network, conference
or TDS pack on this shelf. Messages occur only when a specific CPU is active
and only one group is affected. Suspect: CE Extender connecting CPU to
affected group, or interconnecting cables. If all messages are from the same
XMLC/XDLC, then the XMLC/XDLC is to be unplugged and reinserted (Option
11 only).
Action:
Severity: Minor.
ERR0027
SNMP trap: Yes
Too large, invalid greater than 3 auxpm out-of-range.

Action:
Severity: Minor.
ERR0028
SNMP trap: Yes
Active CR is pointing to a Call register which is already in idle queue hence

being initialized to zero.
Action:
Severity: Minor.
ERR0029
SNMP trap: Yes
Invalid State / Event in R26 PCA operation

Where A is:
1 Invalid PCA state
2 Invalid PCA Event
3 Unexpected PCA Event
Where B is: Current State
Where C is: Current Event
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 794 of 2360

ERR0030 x x tn rtclock NE-500 output buffer overflow. NE-500 set buffer may not be large
enough or is not being emptied. Where: xx represents reference numbers for
the message. These numbers normally do not concern the user. Minor alarm
lamp lit on attendance console for ERR0030 1 TN only.
Action: If the error messages are from the same TN, check the station or
500/2500 line card for defects. If the message persists, notify the operating
company. Minor alarm lamp lit on attendant console for ERR030 281 1 TN only.
Where: x x represents reference numbers for the message. These numbers
normally do not concern the user.
Severity: Minor.
ERR0031 x x
SNMP trap: Yes
Output buffer overflow (as ERR030). An RPE message lost. Where: x x

represents reference numbers for the message. These numbers normally do
not concern the user.
Action:
Severity: Minor.
ERR0032
SNMP trap: Yes
No response is received for an MCID request.

Action: Check if the local CO supports the treatment of such requests.
Severity: Minor.
ERR0033
SNMP trap: Yes
A mCIDRequest return error component (See Appendix C), has been returned
with the indication 'notSubscribed'.
Action: Check if you have subscribed to the service with the operator. If not,
disallow MCID as a Remote Capability on the corresponding D-Channel.
Severity: Minor.
ERR0034
SNMP trap: Yes
An mCIDRequest return error component (see Appendix C) has been returned

with the indication 'notAvailable'. This means that the network was not able to
register any call information.
Action: Contact the network operator.
Severity: Minor.
ERR0035
SNMP trap: Yes
Both, TPDN in LD 15 (FTR_DATA) and HOT P DN in LD 11 are blank. Can't

complete the PCA feature operation.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 795 of 2360

ERR0036
Set Based Buffering was unable to put a message into an SSD message
buffer.
Action: To fully recover from these errors, the system requires a Warm Restart
Initialization. The manual INI recovery operation may be scheduled at the
customer's convenience.
Severity: Major.
ERR0037
SNMP trap: Yes
ERR0037 <Reason Code> <TN>

Where Reason code is,
1. H.323 Virtual Trunks exceeded Limit.
2. SIP Virtual Trunks exceeded Limit.
3. Total Virtual Trunks Exceeded Limit.
TN : The Channel for which the registration failed.
4. Configure only one SS Node with SIP.
5. Note the error messages on the Call Server when the 1801s trunk attempts
to register.
Action:
Severity: Minor.
ERR0038 x
SNMP trap: No
Number of Dialed digits exceeded its limit during transformation.

Action: Change SPRE length as that SPRE + Access Code length shouldn't be
greater the FFC length for customer x.
Severity: Info.
ERR0039
SNMP trap: Yes
All 8 output timeslots are busy on loop <#>, Xnet will be flushed to retry TN:
0x%x, MSG: 0x%x, TIME: 0x%x
Severity: Info.
SNMP trap: Yes
ERR0040 x x tb rtclock SL-1 telephone output buffer overflow. SL-1 telephone buffer may not be
large enough.
Action: If the error messages are from the same TN, check the station or SL-1
line card for defects. If the message persists, notify the operating company.
Where: x x represents reference numbers for the message. These numbers
normally do not concern the user.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 796 of 2360

ERR0041
All 8 output timeslots are still busy on loop <#>, message is lost TN: 0x%x,
MSG: 0x%x, TIME: 0x%x
Severity: Critical.
ERR0042
SNMP trap: Yes
Active CR is NIL, but MSG_CRPTR is not NIL.

Action: None
Severity: Minor.
ERR0043
SNMP trap: No
The SSRC value supported by the Signaling Server is less than the SSRC
value configured for this DCIP in Overlay 17. This allows the creation of
excess Virtual Trunks that might fail to register.
Action:
Severity: Minor.
ERR0044
SNMP trap: Yes
Error occurred adding private MIB's for SNMP agent.

Action: Contact the technical support group.
Severity: Major.
ERR0045 tn
SNMP trap: No
Invalid DN stored against buzz key.

Action: If the set is equipped with a buzz key, check that the DN stored against
it is valid. Otherwise, print (using LD 20) all information for that SL-1 telephone
and notify the operating company.
Severity: Minor.
ERR0046
SNMP trap: Yes
Failed to receive the SNMP MIB2 configuration data, default values used.
Action: Contact the technical support group.
Severity: Minor.
ERR0047
553-3001-411
SNMP trap: No
Mismatch in number of configured and responding i24 KEMs.

Format: ERR0047 TN #configured and #actual where: TN - TN of i2002/i2004,
#configured - number of configured i24 KEMs (the KEM value from OVL 11),
Standard 15.00
January 2006
Page 797 of 2360

#actual - number of responding i24 KEMs.
This message is printed whenever the TPS indicates to the CS a mismatch in
the number of configured and responding i24 KEMs.
Action: Make sure that your KEM hardware configuration matches to what is
configured in OVL 11 on a CS.
Severity: Minor.
ERR0048
SNMP trap: Yes
Mismatch in number of configured and responding i24 KEMs on a VO login.

Format:ERR0048 TN #configured #actual, where:TN - TN of i2002/i2004,
#configured - number of configured i24 KEMs on the logged into TN(the KEM
value from OVL 11), #actual - number of responding i24 KEMs on the logging
in VO phone.
Action:
Severity: Info.
ERR0049
SNMP trap: No
The Terminal Number is in unplugged state (locked out), so it cannot process

a force answered call. The system puts the associated set into Make Set Busy
state.
Action: Plug in the set. If the set is still out of service, check the wiring.
Severity: Minor.
ERR0050 x x tn
SNMP trap: Yes
SL-1 telephone DN has too many appearances.

Action: For each DN on the specified SL-1 telephone, check that the DN has at
most 16 appearances. Otherwise, notify the operating company. Where: x x
represents reference numbers for the message. These numbers normally do not
concern the user.
Severity: Minor.
ERR0051
SNMP trap: Yes
Source ACD DN is not valid.

Action:
Severity: Info.
ERR0052
SNMP trap: Yes
Cannot perform call handover for IP Phone since the feature is not supported
by the LTPS associated with the IP Phone.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 798 of 2360

ERR0053
The call for IP Phone <TN> is dropped due to ACF timer time out.
Action:
Severity: Minor.
ERR0054
SNMP trap: Yes
NAS not configured for PECL. Enable NAS in LD 17.

Action:
Severity: Info.
ERR0057
SNMP trap: No
Excess invalid input messages from digital sets. Every input message is
counted. When the total count reaches a limit, this error message will be
printed and the count is reset to zero. The TN printed is the only TN that
generated the last invalid massage. Other TNs may have generated earlier
messages. If no faults are found on the reported unit then investigate other
cards.
Severity: Minor.
ERR0058
SNMP trap: Yes
Conference cannot be established because the conference loop is under

testing.
Action: No action required.
Severity: Info.
ERR0060 tn
SNMP trap: Yes
Invalid TN.
Action: Check that the Digitone receiver with the given TN is defined in data.
Severity: Minor.
ERR0070 tn x y z
SNMP trap: Yes
Input from software-idled Digitone receiver. Where: x = rtclock, y = start time

when ttr idled, z = allowed wait time before printing msg, x, y, z in half
millisecond increments
Action: Perform digital receiver diagnostic. Use DTR 1 s c (u) command in LD
34.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 799 of 2360

ERR0071
Charge_son never a main_cr.

Action:
Severity: Minor.
ERR0076
SNMP trap: Yes
Music trunk has a bad Call Register in active Call Register (CR).
Action:
Severity: Minor.
ERR0077
SNMP trap: Yes
Music CR has a bad conference TN.

Action:
Severity: Minor.
ERR0078
SNMP trap: Yes
Music CR has a bad auxpm.

Action:
Severity: Minor.
ERR0079
SNMP trap: Yes
Music on hold has improper Call Register (CR).

Action:
Severity: Minor.
ERR0080 tn key
SNMP trap: Yes
Key input from software-unequipped add-on module.

Action: Check SL-1 telephone data. Ensure that add-on module is defined and
that key number is less than last key.
Severity: Minor.
ERR0081
SNMP trap: Yes
Music source has improper Call Register (CR).

Action:
Severity: Minor.
ERR0110 tn
SNMP trap: Yes
Invalid protected trunk line data.

Action: Check trunk data and modify as required.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 800 of 2360

ERR0115 tn
Unable to locate route block indicated by trunk data.

Action: Check trunk data: Customer number, Route number.
Severity: Minor.
ERR0120 tn
SNMP trap: No
Trunk not released by far-end.

Action: Have trunk checked at central office for release failure.
Severity: Minor.
ERR0130 tn
SNMP trap: No
Invalid DN hunting data.

Action: Check that the hunt DN defined for the TN is correct.
Severity: Minor.
ERR0140 tn
SNMP trap: Yes
Invalid off-hook message.

Action: Check the card indicated and the size of the input buffer. Check traffic
statistics.
Severity: Minor.
SNMP trap: Yes
ERR0180 x x rt clock Trunk output buffer overflow. Trunk output buffer may not be large enough.
Action: If the error messages come from the same TN, check for defects on the
trunk. If the message persists, notify the operating company. Where: x x
represents reference numbers for the message. These numbers normally do not
concern the user.
Severity: Info.
SNMP trap: Yes
ERR0181 x y tn rtclock Cannot send MFC/MFE/MFK signaling message where x y represent the
reference numbers for the message.; tn - terminal number (tn is in all decimals
(l s c u)); rtclock is an internal timestamp (0.5 msec). Possible output buffer
overflow. Number of PBX output buffers may not large enough.
Action: If the error messages are from the same TN, check the card for
problems.
Severity: Minor.
ERR0182
SNMP trap: Yes
Route type has been changed to ISA.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 801 of 2360

ERR0183 dnis tn
DNIS calls cannot terminate because the IDC Translation is invalid, or the
terminating station is not an ACD-DN.
Action:
Severity: Minor.
ERR0184
SNMP trap: Yes
A Global CREF number is needed for any service message.

Action:
Severity: Minor.
ERR0187
SNMP trap: No
Mini-CDR is not supported with DNXP or CDRE.

Action:
Severity: Minor.
ERR0190
SNMP trap: No
Overload TN stack overflow.

Action: Correct the overload condition indicated by previous OVD messages.
Severity: Minor.
ERR0200 c tn
SNMP trap: Yes
Invalid customer c in unit block.

Action: Correct the data for the specified TN.
Severity: Minor.
ERR0201
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
No customer ptr set.

Action:
Severity: Minor.
ERR0203
Ulptr not set.

Action:
Severity: Minor.
ERR0205 c tn
Invalid customer c in unit block.

Action: Correct the data for the specified TN.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 802 of 2360

ERR0206
Let group data audit get rid of all pointers.

Action:
Severity: Minor.
ERR0215 r/c
SNMP trap: Yes
Recorded Announcement (RAN) route r or customer c is nonexistent.

Action: Correct RAN route or customer number in route data block or customer
data block.
Severity: Minor.
ERR0220 r c
SNMP trap: Yes
No response (control pulse) return from all trunks on route r for customer c.
Minor alarm lit on attendant console.
Action: Check RAN machine in operation. Use LD 36 to check RAN trunk and
RAN machine.
Severity: Critical.
ERR0221 r c
SNMP trap: Yes
Procedure NWK/DIGPR. Intercept treatment assigned as RAN. RAN route r

for customer c does not exist.
Action:
Severity: Minor.
ERR0225 c p
SNMP trap: Yes
The Call Detail Recording (CDR) port p for customer c is not a CDR device.
Action: Correct the data so that the port is not a CDR device, or connect the
correct CDR hardware.
Severity: Minor.
ERR0226 tn
SNMP trap: Yes
Bit was set for trunk idle. Missed operation of call transfer.
Action:
Severity: Minor.
ERR0245 tn scl
SNMP trap: No
Nonexistent or invalid speed call list number SCL.

Action: Correct speed call list number for the TN or provide the list number by
service change.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 803 of 2360

ERR0260
Incomplete calling number information. Check ANI_LDN, ANI_TRK_NO and

ANI_ATTN_NO to form complete 7-digit number.
Action:
Severity: Minor.
ERR0265 g
SNMP trap: Yes
DND key used to determine status of nonexistent group g.

Action: Print out and correct data.
Severity: Minor.
ERR0266 mg sg
SNMP trap: Yes
Secondary DND group sg was encountered during the processing of a main

group (sg) that did not exist.
Severity: Minor.
SNMP trap: Yes
ERR0267 mg sg g A secondary group (sg) contains another group number (g).

Severity: Minor.
ERR0270
SNMP trap: Yes
Overflow of OVD_TRK_LIST. The trunk identified by the accompanying

OVD003 message may not be automatically re-enabled.
Action:
Severity: Minor.
ERR0280 tn1 tn2
SNMP trap: Yes
Ring Again activated by TN1 was unable to access trunk tn2 due to trunk
access restrictions.
Action: Ensure that all trunks in the route have the same Class-of-Service.
Severity: Minor.
ERR0285 tn
SNMP trap: Yes
Voice call to invalid DN from set. Ensure that voice call key does not point to
mixed, multiple appearance or invalid DN.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 804 of 2360

ERR0290
Invalid incoming DP precedence digit.

Action:
Severity: Minor.
ERR0291
SNMP trap: No
Invalid incoming MF precedence digit.

Action:
Severity: Minor.
ERR0300 tn
SNMP trap: No
Customer has no Dial Intercom Group (DIG) defined or DIG package does not
exist.
Action: Review office data and notify operating company.
Severity: Minor.
ERR0301 tn
SNMP trap: Yes
DIG group does not exist for this terminal number.

Action: Check group number on DIG key for this set.
Severity: Minor.
SNMP trap: Yes
ERR0302 tn
Action: Check group number on DIG key on this set.
Severity: Minor.
ERR0303 tn
SNMP trap: Yes
Originating DIG group is not the same as the terminating group for this key and
DN.
Action: Check DIG group for specified TN.
Severity: Minor.
ERR0304 tn
SNMP trap: Yes
Set does not belong to the same customer as the DIG.

Action: Check DIG list for the set.
Severity: Minor.
ERR0305
SNMP trap: Yes
SNMP trap: Yes
Invalid tstl linkage.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 805 of 2360

ERR0306
Customer translation failed.

Action:
Severity: Minor.
ERR0307
SNMP trap: Yes
TNS actv.cr does not point to Call Register (CR).

Action:
Severity: Minor.
ERR0319
SNMP trap: Yes
Bad LLC blocking value found.

Action:
Severity: Minor.
ERR0367
SNMP trap: Yes
Son call register is an orphan, idle it.

Action:
Severity: Minor.
ERR0400
SNMP trap: Yes
Customer data block missing.

Action:
Severity: Critical.
ERR0403
SNMP trap: Yes
Tree pointers table missing.

Action:
Severity: Critical.
ERR0404
SNMP trap: Yes
SNMP trap: Yes
No default tree exists.

Action:
Severity: Minor.
ERR0406
NCOS not defined in procedure CODE_RESTRICTION.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 806 of 2360

ERR0418
MFC TN of active MFC S/R not.

Action:
Severity: Minor.
SNMP trap: Yes
ERR0468 <global> <1> <tn> <rt clock> Global 320 is RAN_module. TN is in Hex.
Check RAN connection for <tn>.
Action:
Severity: Info.
SNMP trap: No
ERR0468 x y tn rtclock Cannot send message to RAN card where x,y represent the reference
numbers for the message; tn - terminal number (tn is in all decimals (l s c u));
rtclock is an internal timestamp (0.5 msec). Possible output buffer overflow.
The number of PBX output buffers may not be large enough.
Action: If the error messages are form the same TN, check the card for
problems.
Severity: Minor.
ERR0510
SNMP trap: No
The number of digits used for LEC and ANI DN together do not comprise
exactly 7 digits when trying to transmit ANI information to a CIS analog/ DTI
trunk. The least significant digits of the ANI DN will be omitted.
Action: Check LEC prompt in LD 16 and ANI DN used.
Severity: Minor.
ERR0547 c g dn
SNMP trap: Yes
Invalid DN or disallowed Tenant DN for group (g) call for customer c.

Action: Check data for group and correct via service change.
Severity: Minor.
ERR0548 c g
SNMP trap: Yes
Group g for customer c does not exist or is invalid.

Action: Check group data and correct via service change.
Severity: Minor.
ERR0600
SNMP trap: Yes
Invalid supervisor TN in Automatic Call Distribution (ACD).

Action: Check ACD data for the TN.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 807 of 2360

ERR0605
Agent-ID table is full.

Action:
Severity: Minor.
ERR0606
SNMP trap: Yes
High-speed link is not defined.

Action:
Severity: Minor.
ERR0607
SNMP trap: Yes
High-speed link Serial Data Interface (SDI) is disabled.

Action:
Severity: Minor.
ERR0608
SNMP trap: Yes
High-speed link status is 'down'.

Action:
Severity: Minor.
ERR0609
SNMP trap: Yes
Low-speed link is not defined.

Action:
Severity: Minor.
ERR0623
SNMP trap: Yes
Customer pointer not valid or is missing. Between the time of origination and
the time the error was generated, the pointer to the customer data block was
corrupted. (SET CUST PTRS fails).
Action:
Severity: Minor.
ERR0624
SNMP trap: Yes
ESN data block or NTCL data block pointer invalid or missing. A

NARS/BARS/CDP DN has been dialed but the ESN or NTCL block has not
been set up.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 808 of 2360

ERR0642 xxxx <memory needed> <memory left> Insufficient memory to run Corporate
Directory.
Action:
Severity: Info.
ERR0643 n
SNMP trap: Yes
Attempt to enable remote TTY n failed. Auto-recovery will be attempted after

30 seconds.
N = Remote TTY number
Action:
Severity: Minor.
ERR0644 n
SNMP trap: Yes
Problem with remote TTY n. It is disabled and auto-recovery will be attempted

after 30 seconds. N = Remote TTY number.
Action:
Severity: Minor.
ERR0645 aa xx
SNMP trap: Yes
Attendant Announcement Table xx defined in Route aa does not exist.

Action: Please check AANN configuration.
Severity: Minor.
ERR0646 c
SNMP trap: Yes
The I44 Nail-up for the local card C has failed on the IP expansion, where c is
the local card number on the IP expansion.
Action:
Severity: Major.
ERR0648
SNMP trap: Yes
Physical TN of ITG card is nil.

Action:
Severity: Critical.
ERR0655
SNMP trap: Yes
655; % Display CR not equal to CRPTR. CRPTR has to be idled.

Segment - auditpoo.seg (COMPOOL)
Action: No action required other than printing the warning.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 809 of 2360

ERR0700 tn
MFC signaling error threshold exceeded.

Action: Use LD 54 to test MFC channels.
Severity: Minor.
ERR0901 c
SNMP trap: No
Error happened during accessing the card c. A message could not be

read from the card. The card is possibly removed from the cabinet.
Action: Insert the card into the cabinet and enable it in LD 32.
Severity: Minor.
ERR0902 c
SNMP trap: No
Error happened during accessing the card c. The card is not responding
to the read message requests. The card is possibly removed from the cabinet.
Severity: Minor.
ERR0903 c
SNMP trap: No
Error happened during accessing the card c. The card is possibly removed
from
the cabinet in the middle of card disabling.
Severity: Minor.
SNMP trap: No
ERR0999 x y tn rtclock Cannot send output message from overlay 48 or 77, where x,y represent
the reference numbers for the message; tn - terminal number (tn is in all
decimals (l s c u)); rtclock is an internal
Action: If the error messages are from the Tn, check the card fro problems.
Severity: Minor.
ERR1001
SNMP trap: No
An invalid primitive was received from the DCHI card.

Action: Use LD 54 to test MFC channels.
Severity: Minor.
ERR1502
SNMP trap: No
PROCEDURE NUM_DN_MEMBERS - Number of members are more than

MAX_TNS_PER_DN.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 810 of 2360

ERR2139
DN assignment is not allowed for this key.

Action:
Severity: Minor.
ERR2220
SNMP trap: No
Cannot access FGD block used for OLI screening. Output data: TN <tn> FGD
<fgno> where <tn>: TN of incoming trunk, <fgno> FGD block number
Action: Configure FGD block <fgno> in LD 19.
Severity: Minor.
ERR3000 x
SNMP trap: No
The buffer is not empty. Count for APL link x exceeded the system limit. The
SDI card may have hardware problem.
Action: Disable the TTY and start IOD program to test out the TTY.
Severity: Minor.
ERR3001 x
SNMP trap: Yes
APL link x is down due to transmission problems. The problem can be TTY
hardware problem, transmission line problem or AUX processor problem.
Action:
Severity: Critical.
ERR3002 x
SNMP trap: Yes
The number of NAK messages within last 30 min exceeded the

system-defined limit of 10. APL link x may have transmission problem. This
APL link has an occasional hit on the line.
Action: Check the transmission facility for foreign noise introduced to this link.
Severity: Minor.
ERR3003
SNMP trap: Yes
Remove_Apl_OQ. Message CR is not in QU_APL_OP queue.

Action:
Severity: Minor.
ERR3004 x
SNMP trap: Yes
The number of times the link has no acknowledge signal sent from the other
side exceeds the system limit of 10. APL link x may have a transmission
problem. This APL link has occasional hit on the line.
Action: Check the transmission facility for foreign noise introduced to this link.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 811 of 2360

ERR3010 dn
The DN sent from the AUX, in Message 7 is invalid for Message Waiting
Indication. The AUX DN may be invalid.
Action:
Severity: Minor.
ERR3011 ltn
SNMP trap: Yes
An invalid LTN was found. The LTN table may be wrong.

Action:
Severity: Minor.
ERR3012
SNMP trap: Yes
SNMP trap: No
Bad APL range (0-15).

Action:
Severity: Minor.
ERR3013
APL shared by another user.

Action:
Severity: Minor.
ERR3014
SNMP trap: No
APL not defined in customer data block.

Action:
Severity: Minor.
ERR3015
SNMP trap: No
Warning: some UST user may have some problem.

Action:
Severity: Minor.
ERR3016
SNMP trap: No
Bad telmsg timer range (2-15).

Action:
Severity: Minor.
ERR3017
SNMP trap: No
No to mwc not allowed, IMS defined.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 812 of 2360

ERR3018
Change CMS from yes to no, or vice versa.

Action:
Severity: Minor.
ERR3030
SNMP trap: No
Member in DND group does not exist.

Action:
Severity: Minor.
ERR3032
SNMP trap: Yes
Transfer blocked due to unavailable matching timeslots.

Action:
Severity: Minor.
ERR3033 c p
SNMP trap: Yes
A Q-record is discarded because the target CTY port p for customer c is under
maintenance testing.
Action:
Severity: Minor.
ERR3035
SNMP trap: Yes
Test line type/index out-of-range.

Action:
Severity: Minor.
ERR3036 r s j ts
SNMP trap: Yes
Continuity failure has occurred on assigning timeslots for speech paths. First
attempt failed; tries to get new path. Parameters are: r = receive loop, s = send
loop, j = junctor used to transmit to the RRR loop ID, ts = timeslot used on
transmit loop to send PCM data to the receive loop. ERR3036 and ERR3037
messages refer to one-way connections so that if both one-way connections
fail, either message may print out twice. ERR3036 also occurs if a loop on the
QPC414 Network card is not configured. This is not an error condition. To
prevent ERR3036 occurring in this case, define the loop in LD 17.
Action:
Severity: Minor.
ERR3037 r s j ts
SNMP trap: Yes
Same as ERR3036 but failed on second attempt; path is assigned anyway.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 813 of 2360

ERR3038 dn
Invalid or nonexisting intra-flow DN.

Action:
Severity: Minor.
ERR3039
SNMP trap: Yes
Process IDs do not match in AUX_KEYS. This could be due to the AUX
equipment not having a Directory Number assigned at the time of an incoming
call to that equipment.
Action:
Severity: Minor.
ERR3040
SNMP trap: Yes
Process IDs do not match in operator revert.

Action:
Severity: Minor.
ERR3041
SNMP trap: Yes
The output buffer to the DTI hardware has overflowed.

Action:
Severity: Minor.
ERR3042
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
No IETI.
Action:
Severity: Minor.
ERR3043
LOC NO SDI.
Action:
Severity: Minor.
ERR3044
Bad ITGE data.

Action:
Severity: Minor.
ERR3045
Incorrect key function defined for data TN.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 814 of 2360

ERR3046
Data TN is not defined.

Action:
Severity: Minor.
SNMP trap: No
ERR3047 c Loop tn Failure for 500/2500 set Six-Party Conference c.

Action:
Severity: Minor.
ERR3050
SNMP trap: Yes
MWD not allowed if MWK key is equipped.

Action:
Severity: Minor.
ERR3056 tn
SNMP trap: No
TN was force disconnected due to a service change (LD 10, 11 or 14)

Action:
Severity: Minor.
ERR3067
SNMP trap: Yes
The output buffer to the tone detector has overflowed.

Action:
Severity: Minor.
ERR3068 x
SNMP trap: Yes
Call Park ID (x) returned which is now invalid, usually the result of a service
change or set relocation. The invalid ID is unavailable for use as a Park ID.
Action:
Severity: Minor.
ERR3069
SNMP trap: Yes
Call is to HOT set/key but not to package.

Action:
Severity: Minor.
ERR3070
SNMP trap: Yes
Set/key is EHOT but data is defined.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 815 of 2360

ERR3071
Either the list number or the entry number for Hot key termination is invalid.
Action:
Severity: Minor.
ERR3072
SNMP trap: Yes
Failure to establish SLP conference

Action:
Severity: Minor.
ERR3073
SNMP trap: No
Failure to add tone to SLP conference.

Action:
Severity: Minor.
ERR4010 tn key f
SNMP trap: No
Predefined secondary DN key with function f on a data service ACD agent set
is not MNC, MCR, SNC, or SCR.
Action:
Severity: Minor.
ERR4011 tn ici
SNMP trap: Yes
Wrong ICI key removed.

Action:
Severity: Minor.
SNMP trap: Yes
ERR4012 in cr tn msg key Message Reference ID (MRID) mismatch between the MRID
contained in the input CSL message and the MRID stored in the call register.
This message indicates the CSL message is delayed. When this message
repeats, the most likely problem is CPU overload. Where: in = MRID contained
in the incoming CSL message (in hex); cr = MRID stored in the call register
associated with the TN of the incoming CSL message (in hex); tn = The TN of
the incoming CSL message, in packed format; msg = The message type of the
incoming CSL message; key = The function of the key message. This appears
when the message type is KEY message. Refer to Application Module Link
(AML) documents for msg and key value.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 816 of 2360

ERR4013 n t
There have been n mismatches in Message Reference ID (MRID) between the

active CR and AML message CR within t * 2 seconds.
Action: The CPU may be very busy: check total number of Call Registers,
provision of Meridian Mail ports, Meridian Mail use, and system I/O.
Severity: Minor.
ERR4016
SNMP trap: Yes
CSL indirect connect failed.

Action:
Severity: Minor.
ERR4017
SNMP trap: Yes
CLS indirect disconnect failed.

Action:
Severity: Minor.
ERR4018 dn c
SNMP trap: No
The ACD-DN for customer c is not defined for data services.

Action:
Severity: Minor.
ERR4019 dn
SNMP trap: Yes
Invalid DN was sent from a VAS when requesting Message Waiting Indicator
(MWI) update. Output: The affected DN.
Action: Check the DN. It may have been removed in the Meridian 1, but not the
VAS.
Severity: Minor.
SNMP trap: Yes
ERR4020 dn c xxx Data Service DN leaf block does not contain a valid ACD DN. Where: c =
customer; xxx block contents.
Action:
Severity: Minor.
ERR4021
SNMP trap: Yes
Meridian Mail MP alarm.{ESDI} {SEER class} {SEER cause}ESDI - ESDI port

number SEER class - Meridian Mail SEER class number Minor alarm lamp lit
on attendant console.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 817 of 2360

ERR4022 mt mst vas c dn acc An incoming CSL DATA add data service DN message has been
received, but not enough protected memory exists to allocate a DSDN_LIST
for the customer. Output in hex: mt = message type, mst = message subtype,
vas= VAS ID, c = customer number, dn = data service DN, acc = access code
Action:
Severity: Minor.
ERR4023
SNMP trap: Yes
An incoming CSL DATA add or validate data service DN message has been
received, but the data services customer option is not set. No data services
DNs will be accepted. See ERR4022 for output data.
Action:
Severity: Minor.
ERR4025
SNMP trap: Yes
An incoming CSL DATA add or delete data service DN message has been
received, but the DN could not be added or removed because not enough
unprotected memory exists to allocate a WORKAREA. See ERR4022 for
output data.
Action:
Severity: Minor.
ERR4026
SNMP trap: Yes
An incoming CSL DATA delete data service DN message has been received,
but the DN does not exist for this customer. See ERR4022 for output data.
Action:
Severity: Minor.
ERR4027
SNMP trap: Yes
An incoming CSL DATA add data service DN message has been received, but
the DN could not be added because the maximum had been reached. See
ERR4022 for output data.
Action:
Severity: Minor.
ERR4028
SNMP trap: Yes
An incoming CSL DATA delete data service DN message has been received,
but the DN was not removed because it was not a data DN. See ERR4022 for
output data.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 818 of 2360

ERR4029
received, but the DN was rejected because the access code was invalid (The
DN does not exist). See ERR4022 for output data.
Action:
Severity: Minor.
ERR4030
SNMP trap: Yes
received, but the DN was rejected because the access code was invalid (the
DN was not an ACD DN). See ERR4022 for output data.
Action:
Severity: Minor.
ERR4031
SNMP trap: Yes
ACD DN is not defined as a primary data service access code). See ERR4022
for output data.
Action:
Severity: Minor.
ERR4032
SNMP trap: Yes
DN is defined for a different VAS Server). See ERR4022 for output data.
Action:
Severity: Minor.
ERR4033
SNMP trap: Yes
DN conflicts with an existing longer or shorter DN). See ERR4022 for output
data.
Action:
Severity: Minor.
ERR4034
SNMP trap: Yes
DN already exists). See ERR4022 for output data.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 819 of 2360

ERR4048 c r idc
Conflict in data base for DRC key on SL-1 set.

Action: Check the specified customer, route, for IDC setting.
Severity: Minor.
ERR4050 data
SNMP trap: Yes
Intercept treatment DN not found.

Action: Define intercept treatment DN in the FGD data block (LD 19).TRK tn
MFR tn ID j ddd ADR j ddd Where: TRK tn = TN of the FGDT trunk (l s c u, loop
ch) MFR tn = TN of the MF receiver (l s c u, or loop ch) ID j ddd = ID field, j =
number of digits, dddd = digits ADR j ddd = Address field, j = number of digits,
dddd = digits. If the address was not received or was empty, it is not printed.
Severity: Minor.
ERR4051 data
SNMP trap: Yes
Invalid NPA in ID field. If the error repeats with the same MFR, test the MFR
card; otherwise suspect a fault on far end outpulsing mechanism. See
ERR4050 for a description of output data.
Action:
Severity: Minor.
ERR4052 data
SNMP trap: Yes
Incorrect address; cannot determine the category. If the error repeats with the
same MFR, test the MFR card; otherwise suspect a fault on far end outpulsing
mechanism. See ERR4050 for a description of output data.
Action:
Severity: Minor.
ERR4053 c h a
SNMP trap: Yes
More than 20 Attendant console Graphic Modules being updated in one time
slice. Where: c = customer number, h = hundreds group involved, a =
attendant not updated
Action:
Severity: Minor.
ERR4054
SNMP trap: Yes
Access to the trunk was disconnected due to Timed Forced Disconnect (TFD)
timeout.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 820 of 2360

ERR4055 data
This message may indicate that a caller dialed an invalid authorization code.
It can also refer to MF inter-digital or inter-field timeout. See ERR4050 for a
description of output data.
Action: Check the ID and ADR fields to see if the digits are for a phone number
or an authorization code. If it is an incomplete phone number, increase the DGTO
or IFTO parameters in the FGD block in LD19.
Severity: Minor.
ERR4056 data
SNMP trap: Yes
FGD or M911 trunk received TTR input before end of start-dial wink. Output:
trktn mfrtn trunkpm input_message
Action: Test the FGDT trunk and MFR card.
Severity: Minor.
ERR4057
SNMP trap: Yes
CFNA cannot terminate on the Forward DN (FDN) because the FDN is an

ACD-DN which is not a Message Center, or the set on which the FDN is
defined does not have Message Waiting Allowed (MWA) Class of Service
(COS).
Action: Either redefine the FDN, or give the dialed set MWA COS.
Severity: Minor.
ERR4058
SNMP trap: Yes
Undefined or invalid Attendant Alternative Answering (AAA) DN type was

found at AAA timeout. Valid types are Set DN and ACD-DN.
Action:
Severity: Minor.
ERR4059 dn
SNMP trap: Yes
Tenant to tenant access denied between the caller and the specified Attendant
Alternative Answering (AAA) DN at AAA timeout.
Action:
Severity: Minor.
SNMP trap: Yes
ERR4060 SUPL loop HW c Parameter downloading failed. Unable to send messages through
Network card message interface.
Action: Try to download to the card by using the appropriate enable command.
Where: c = NT8D01 Controller card
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 821 of 2360

ERR4061
CPG_DATA_PTR or CPG_BLK_PTR pointer is nil (DUMP module).

Action:
Severity: Minor.
ERR4067 c x
SNMP trap: Yes
No unprotected CPG data block for CPG x of customer c.

Action:
Severity: Minor.
ERR4068 c
SNMP trap: Yes
No unprotected CPG data block for CPG 0 of customer c.

Action:
Severity: Minor.
ERR4069 c
SNMP trap: Yes
No protected CPG data block for CPG 0 of customer c.

Action:
Severity: Minor.
ERR4070 c x
SNMP trap: Yes
Customer c data block exists, but there is no CPG_PTR_BLK for CPG number
x.
Action:
Severity: Minor.
ERR4071 tn
SNMP trap: Yes
The type of trunk (COT, DID, Tie, etc.) specified during the audit did not match
the trunk type stored within IPE trunk card. The trunk type stored within the
card has been set to the trunk type specified in the audit message. (The audit
process obtains trunk type from the TN block contained within the database.)
Action: If this message persists, disable and enable the offending unit with LD
32 (which causes a parameter download). If the problem persists, suspect a faulty
card.
Severity: Minor.
ERR4072 tn
SNMP trap: Yes
Impedance setting conflict found on an IPE trunk during audit parameter

download.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 822 of 2360

ERR4073 tn
Dialing speed setting conflict found on an IPE trunk during audit parameter
download.
Action:
Severity: Minor.
ERR4074 tn
SNMP trap: Yes
Carrier pad setting conflict found on an IPE trunk during audit parameter
download.
Action:
Severity: Minor.
ERR4075 tn
SNMP trap: Yes
Companding law (A-Law or Mu-Law) setting conflict found on an IPE trunk

during audit parameter download.
Action:
Severity: Minor.
ERR4076 tn
SNMP trap: Yes
10 PPS1 conflict found on IPE trunk during audit parameter download.

Action:
Severity: Minor.
ERR4077 tn
SNMP trap: Yes
10 PPS2 conflict found on the IPE trunk during audit parameter download.
Action:
Severity: Minor.
ERR4078 tn
SNMP trap: Yes
20pps conflict found on the IPE trunk during audit parameter download.
Action:
Severity: Minor.
ERR4079 tn
SNMP trap: Yes
The hardware ID (type of unit (COT, DID, etc.) and signaling (LOP,GRD, EAM,
etc.) is not supported by the card (XUT, XEM, or any other IPE trunk card). The
software configuration no longer matches the hardware configuration for the
unit. Unit is disabled.
Action: Check that correct card for desired trunks is in configured slot. Check
configuration of unit.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 823 of 2360

ERR4080
D-channel was not found for sending a facility Message. Output appears as
follows (with X11 Release 16 and later software): NTFERR a b c; DIGPR a b
c; INVDN p a b c. Where: a = originating digits, b = destination digits, c =
customer number, p = TCAP package type. X11 Release 15 messages
appear as follows: FAIL ORIG: xxx DEST: xxx CUST: xx
Action:
Severity: Minor.
ERR4081
SNMP trap: Yes
A Facility Reject message was received. Destination digits cannot be

translated. Output with message: PKG: xxx NOXLAN ORIG: xxx DEST: xxx
CUST: xx
Action:
Severity: Minor.
ERR4082
SNMP trap: No
TCAP Package type is not recognized by Network Message Center (NMC)

feature. Output with message: PKG: xxx ORIG: xxx DEST: xxx CUST: xx or
CP does not support more than 4 digit DNs. Procedure ICP_ESTABLISH and
ICP_FIND_DN
Action:
Severity: Minor.
ERR4083
SNMP trap: Yes
TCAP Component is not recognized by Network Message Center (NMC)

feature. Output with message:PKG: xxx COMP: xxx ORIG: xxx DEST: xxx
CUST: xx.
Action:
Severity: Minor.
ERR4084
SNMP trap: No
TCAP Operation is not recognized by Network Message Center (NMC)

feature. Output with message: PKG: xxx COMP: xxx OPER: xxx ORIG: xxx
DEST: xxx CUST: xx
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 824 of 2360

ERR4085
TCAP parameter is not recognized by Network Message Center (NMC)

feature. Output with message: PKG: xxx COMP: xxx OPER: xxx PARM: xxx
ORIG: xxx DEST: xxx CUST: xx
Action:
Severity: Minor.
ERR4100
SNMP trap: No
Tenant TDATAPTR or route ACCESS_ARRAY block does not exist.

Action:
Severity: Minor.
ERR4101
SNMP trap: No
PBX output buffer overflow for Digital set.

Action:
Severity: Minor.
ERR4103
SNMP trap: No
Touch set watchdog overflow.

Action:
Severity: Minor.
ERR4105
SNMP trap: Yes
An appearance of multiple appearance DN cannot answer a call. It resides

either on a set with CLS that cannot receive external calls or on a set with a
tenant that differs from the tenant of other sets that can answer the call. All the
appearances of the DN should reside on sets that belong to the same tenant.
Action:
Severity: Minor.
ERR4106
SNMP trap: Yes
TSET downloading buffer overflow.

Action:
Severity: Minor.
ERR4108 tn
SNMP trap: Yes
Possible tip and ring reversal at central office or CO trunk card problem.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 825 of 2360

ERR4109
VASID out-of-range.
Action:
Severity: Minor.
ERR4111
SNMP trap: No
Incorrect key function defined for data TN.

Action:
Severity: Minor.
ERR4112
SNMP trap: Yes
Data TN not defined. An M2317 set with without data cannot have Single Call
Ringing (SCR) on key 10.
Action:
Severity: Minor.
ERR4113
SNMP trap: Yes
Digital set has sent handsfree activated message, but does not have
Handsfree Class of Service (HFA).
Action:
Severity: Minor.
ERR4114
SNMP trap: Yes
Data DN of SL-Touch does not have two appearances.

Action:
Severity: Minor.
ERR4115
SNMP trap: Yes
The M2317 or M3000 set has requested a restart. If set has not been manually
reversed down and up and these messages consistently appear then the set,
line card channel, or power supply is bad. ORIG & TERTN will show if active
in a call.
Action:
Severity: Minor.
ERR4117
SNMP trap: Yes
SNMP trap: Yes
Incorrect tree class.

Action:
Severity: Minor.
System Messages
Page 826 of 2360

ERR4118
Tree is corrupted.
Action:
Severity: Minor.
ERR4120
SNMP trap: Yes
Invalid digit received by IDC.

Action:
Severity: Minor.
ERR4125
SNMP trap: Yes
Message CRl is not in idle queue.

Action:
Severity: Minor.
ERR4127
SNMP trap: Yes
Message CR is not in QU_CSL_OP.

Action:
Severity: Minor.
ERR4128
SNMP trap: Yes
Output message has length zero.

Action:
Severity: Minor.
SNMP trap: Yes
ERR4129 dn c t1 t2 The duration time set for the call in the Abandoned Call Waiting in the Source
queue is invalid. Output: dn = ACD-DN, c = customer, t1 = time of day, t2 =
time call arrived.
Action:
Severity: Minor.
ERR4130
SNMP trap: No
Wrong call reference flag. Incompatible Protocol between the interface.

Action: If the error continues, file a problem report.
Severity: Minor.
ERR4131
SNMP trap: No
The message received has global CREF. Incompatible protocol between the
interface.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 827 of 2360

ERR4132
Received a SERVICE, SERVICE ACK, RESTART, RESTART ACK with a

non-global CREF. Incompatible protocol between the interface.
Action:
Severity: Minor.
ERR4133
SNMP trap: No
For ISDN ESS #4 received a SERVICE, SERVICE ACK, RESTART,

RESTART ACK with the wrong call reference flag. Incompatible protocol
between the interface.
Severity: Minor.
ERR4134 data
SNMP trap: No
First digit is not KP. If the error repeats with the same MFR, test the MFR card;
otherwise suspect a fault on far end outpulsing mechanism, or noisy trunk.
See ERR4050 for a description of output data.
Action:
Severity: Minor.
ERR4135 data
SNMP trap: Yes
Illegal size of a field. If the error repeats with the same MFR, test the MFR
card. See ERR4050 for a description of output data.
Action:
Severity: Minor.
ERR4136 data
SNMP trap: Yes
Illegal MF combination. If the error repeats with the same MFR, test the MFR
card; otherwise suspect a fault on far-end outpulsing mechanism, or noisy
trunk. See ERR4050 for a description of output data.
Action:
Severity: Minor.
ERR4137 data
SNMP trap: Yes
Unexpected digit (ST', ST'', ST'''), or KP in the middle of a field. If the error
repeats with the same MFR, test the MFR card; otherwise suspect a fault on
far-end outpulsing mechanism, or noisy trunk. See ERR4050 for a description
of output data.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 828 of 2360

ERR4138 data
Call category denied. Check if CCAN definitions in LD 19 are consistent with

far end (LEC) arrangement. See ERR4050 for a description of output data.
Action:
Severity: Minor.
ERR4139 data
SNMP trap: Yes
ANI field empty when should be present. Check if CCAN definitions in LD 19

are consistent with far end (LEC) arrangement. See ERR4050 for a
Action:
Severity: Minor.
ERR4140 data
SNMP trap: Yes
ANI field present when should be empty. Check if CCAN definitions in LD 19

are consistent with far end (LEC) arrangement. See ERR4050 for a
Action:
Severity: Minor.
ERR4141 data
SNMP trap: Yes
Undefined information digit (I I) number received. This is an attempt by an

unauthorized user. The output data is: CUST c Trm hh:mm:ss dd/mm/yyyy
II-NPANXXXXX zzzzz
Action: Where: c = customer number, Trm = FGD route and member number,
II-NPANXXXX = FGD ID field information, zzzzzz = FGD field address digits
Severity: Minor.
ERR4142 data
SNMP trap: Yes
Undefined ANI number received. This is an attempt by an unauthorized user.

See ERR4141 for description of the output data.
Action:
Severity: Minor.
ERR4143 data
SNMP trap: Yes
Cannot access NARS database. Define ESN database for the customer. See
ERR4050 for a description of output data.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 829 of 2360

ERR4144 data
Cannot access FGD block. Check the value of the FGDB in the route and
check the definition of related FGD block. See ERR4050 for a description of
output data.
Action:
Severity: Minor.
ERR4145 data
SNMP trap: Yes
100 line test DN not defined.

Action: Define the 100 test line in LD 15. See ERR4050 for a description of
output data.
Severity: Minor.
ERR4147 data
SNMP trap: Yes
An invalid message while waiting for MF digits.

Action: Test the MFR card. Output data is mfrtn input_message.
Severity: Minor.
ERR4148
SNMP trap: Yes
An invalid message while waiting for DTR digits.

Action: Test the MFR card. Output data is mfrtn input_message.
Severity: Minor.
SNMP trap: Yes
ERR4149 <global no> <ref no> <tn> <rtclock> The output buffer to PRI2 pack overflowed,
where:
<global no> is always 646.
<ref no> is always 1
<tn> packed format Terminal Number
<rtclock> Real Time Clock stamp
Action:
Severity: Minor.
ERR4161
SNMP trap: Yes
Call Reference length is greater than 2.

Action:
Severity: Minor.
ERR4200
SNMP trap: No
Speed Call list check failed.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 830 of 2360

ERR4201
Speed Call list CR setup failed.

Action:
Severity: Minor.
ERR4202
SNMP trap: Yes
Speed Call indexing failed.

Action:
Severity: Minor.
ERR4203
SNMP trap: Yes
Speed Call entry pointer nil.

Action:
Severity: Minor.
ERR4204
SNMP trap: No
Speed Call digits to CR failed.

Action:
Severity: Minor.
ERR4205
SNMP trap: Yes
Pretranslation table being removed.

Action:
Severity: Minor.
ERR4222
SNMP trap: No
Auto-terminating DN defined in the trunk block for this ACD DNIS call is not an
ACD DN.
Action:
Severity: Minor.
ERR4225
SNMP trap: Yes
500/2500 Set DN cannot be defined until CPND feature is configured for that
set. DATA: 500/2500 set DN and packed TN
Action: Use LD 10 to configure CPND feature. Use LD 95 to configure ANY
Name first.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 831 of 2360

ERR4226 xx
Insufficient storage for CPND Name. Where: xx = DN or DIG group and

member numbers.
Action: Add memory or relocate CPND Logic page.
Severity: Minor.
ERR4227 xx
SNMP trap: Yes
Insufficient storage for DIG name table. Where: xx = DN or DIG group and
member numbers.
Action: Add memory or relocate CPND Logic page.
Severity: Minor.
ERR4276
SNMP trap: Yes
Maintenance message is only allowed in specific DCH interface.

Action:
Severity: Minor.
SNMP trap: No
ERR4277 c dn ifdn Invalid Interflow destination. Where: = customer, dn = ACD-DN, ifdn =

Interflow DN.
Action:
Severity: Minor.
SNMP trap: Yes
ERR4278 c dn ifdn Invalid Night Call Forward destination specified. Where: = customer, dn =
ACD-DN, ifdn = Interflow DN.
Action:
Severity: Minor.
ERR4280
SNMP trap: Yes
Use LD 92 to diagnose the ADM TN.

Action:
Severity: Minor.
ERR4281
SNMP trap: Yes
Message input received from a 64 k data module has no Call Register

available.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 832 of 2360

ERR4283
Both DCHs have been released. Establish the DCH.

Action:
Severity: Critical.
ERR4285
SNMP trap: No
1) ACNT key defined but no ADS block defined, OR 2) This agent is not an
acquired ICCM agent (Rls 13), Or 2) This agent is not an acquired ICCM
control agent. (Rls 22)
Action: 1.Either take out ACNT key or define ADS block. (Rls 13) 2. Either take
out the ACNT key or acquire the agent as a control agent. (Rls 22)
Severity: Info.
ERR4286
SNMP trap: Yes
Message count on the loop exceeds the threshold value.

Action: Refer to any OVD messages previously printed, and check the hardware
for defects that generate an overload condition. Rearrange the TNs to another
location or they may be disabled. Reconfigure the Loop.
Severity: Minor.
ERR4287
SNMP trap: Yes
Customer number greater than 31 while CDRE is not packaged.

Action: Refer to any OVD messages previously printed, and check the hardware
for defects that generate an overload condition. Rearrange the TNs to another
location or they may be disabled.
Severity: Minor.
ERR4288
SNMP trap: No
Route number is greater than 127 while CDRE is not packaged.

Action:
Severity: Minor.
ERR4289
SNMP trap: No
Route number for music route is not a music route.

Action:
Severity: Minor.
ERR4291
SNMP trap: Yes
Music route is undefined.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 833 of 2360

ERR4293
Both DCHs out-of-service.

Action: Release/Establish both DCHs.
Severity: Critical.
ERR4500
SNMP trap: No
GPT Integrated Digital Access ERR: {x x x x x} The format of the message is

ERR4500 xxxx, where xxxx is as follows: 300 d -A message has been
received from DTSL/DDSL d that is either unequipped or disabled. 311 d Message length of zero read from DTSL d - suspect faulty pack. 312 d Message length exceeding 63 bytes read from DTSL d. 313 d - DTSL d is not
responding. 314 d - Status register of DTSL d is not accessible. 315 d - Data
register of DTSL d is not accessible. 330 d - Message output to DTSL/DDSL
d has failed. 333 d - Invalid interrupt 401 d - Message length of less than 3
bytes has been received from DTSL/DDSL d. 402 d l c - Message received on
unconfigured channel c, loop l, and DTSL/DDSL d. 403 d tn - Flow control
encountered on DTSL/DDSL d. tn gives packed TN of the channel.
Action:
Severity: Minor.
ERR4501
SNMP trap: Yes
Received a PRA message with an unsupported service identifier.

Action:
Severity: Minor.
ERR4506
SNMP trap: Yes
Facility reject received. Data: Orig PNI, Orig #, Dest PNI, Dest #, Reason. The
values for "Reason" are: 0 = no transmission address of such nature, 1 = no
transmission address for this specific address, 2 = application congestion, 3 =
application failure, 4 = unequipped application, 5 = network failure, 6 = network
congestion
Action:
Severity: Minor.
ERR4507 c s
SNMP trap: No
Missing PNI number in the customer data block. Where: c = customer, s =

service ID.
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 834 of 2360

ERR4508
Received bad facility I.E.

Action:
Severity: Minor.
ERR4510
SNMP trap: No
ROSE component sent is being rejected.

Action:
Severity: Minor.
ERR5000
SNMP trap: No
Target ID is not an ACD-DN or NARS DN. Procedure: Successful

Action:
Severity: Minor.
ERR5001
SNMP trap: Yes
Target ID did not access the ISL/PRA Trunk. Procedure: SEND_CALLSETUP

Action:
Severity: Minor.
ERR5002
SNMP trap: Yes
The QPC720C PRI is required for 1.5 Mb/s GPRI; otherwise, the MU/A law
conversion and loss level adjustments will not function properly.
Action:
Severity: Minor.
ERR5017 c
SNMP trap: Yes
Customer c should have a common printer defined. Procedure

ICP_GET_PRINTER.
Action:
Severity: Minor.
ERR5018 t
SNMP trap: Yes
Tenant t should have a common printer defined. Procedure

ICP_GET_PRINTER.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 835 of 2360

ERR5019
This TN should have a printer configured. Procedure ICP_ESTABLISH and

ICP_GET_ATTN_PTR.
Action:
Severity: Minor.
ERR5024
SNMP trap: Yes
The auto-terminating number for this In-band ANI route is not an ACD-DN.
Action:
Severity: Minor.
ERR5026
SNMP trap: Yes
Multi-Tenant alone or with CPG level services is enabled. The caller is denied
access to the CPG Night DN. This is an illegal configuration. Tenants sharing
the same CPG should be allowed access to each other.
Action:
Severity: Minor.
ERR5027
SNMP trap: Yes
Stepping action is aborted. Stepping to an ISA route is not allowed.

Action: Use LD 16 to correct the stepping route number.
Severity: Minor.
ERR5028
SNMP trap: Yes
Stepping action is aborted. Stepping to an ISA SERVICE route is not allowed.

Action: Use LD 16 to correct the stepping route number.
Severity: Minor.
ERR5029
SNMP trap: Yes
Reverse call charging is not allowed. Please disregard the call charging
information received from the network.
Action:
Severity: Minor.
ERR5030
SNMP trap: Yes
Information in the TYPE field of the Information Element is invalid.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 836 of 2360

ERR5031
The network will disregard the ISDN call charging information received,
because the call was never properly established.
Action:
Severity: Minor.
ERR5032
SNMP trap: Yes
The HM_STRUCT for a set is missing in the procedure WUK_LAMP_FLASH,

or the HM_STRUCT for a set is missing or the set does not have CCSA Class
of Service procedure WUK_DARK_OR_LIT. Data corruption.
Action:
Severity: Minor.
ERR5033
SNMP trap: Yes
An invalid lamp state has occurred in the procedure WUK_DARK_OR_LIT.

Either there is a request and the Wake Up Key (WUK) lamp is not lit or there
is no request and the WUK lamp is lit.
Action:
Severity: Minor.
ERR5034
SNMP trap: Yes
aux_custptr [ ] = NIL in procedure store_awu. Data corruption

Action:
Severity: Minor.
ERR5035
SNMP trap: Yes
Unable to find a primary appearance DN to store the Wake Up call. Procedure

wuk_get_tn or ffc_find_awu_tn. Cannot proceed.
Action:
Severity: Minor.
ERR5037
SNMP trap: Yes
A restart message has been sent twice, but the far-end has not responded with
the proper RESTART ACK message. The PRA B-channels are left in a
maintenance busy state. The ISL trunks are not marked as maintenance busy
if they revert back to a conventional trunk (option enabled).
Action: Check the D-channel status for both ends in LD 96. Try to disable and
reenable the D-channels.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 837 of 2360

ERR5039 D
The Virtual Network Service (VNS) message received is discarded because

the VNS package is not equipped. Where: D = D-channel number.
Action:
Severity: Minor.
ERR5043
SNMP trap: Yes
Invalid date information element for PRA messaging.

Action:
Severity: Minor.
ERR5044
SNMP trap: Yes
No posttransl blk defined in pd. Pretranslation.

Action:
Severity: Minor.
ERR5045
SNMP trap: Yes
No RPA FFC PARM blk defined for the RPS.

Action:
Severity: Minor.
ERR5046
SNMP trap: Yes
DN does not exist in the RPA-DN tree (table).

Action:
Severity: Minor.
ERR5047
SNMP trap: Yes
RPA does not support diversion to manual RPS.

Action:
Severity: Minor.
ERR5048
SNMP trap: Yes
RPA traffic block pointer in RPA SYS PARM blk is nil.

Action:
Severity: Minor.
ERR5049
SNMP trap: Yes
Rising edge of Call Accepted signal is either too short or too long from trailing
All Digits Revd signal.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 838 of 2360

ERR5050
Rising edge of Start Talk signal is either too short or too long from trailing Call
Accepted signal. Speech path will not be provided; call can be answered in
normal manner.
Action:
Severity: Minor.
ERR5051
SNMP trap: Yes
SNMP trap: Yes
NO RPCD data defined.

Action:
Severity: Minor.
ERR5054
The ISDN call charging information exceeds the limit of 9 digits. Please
disregard the charging information message from the network.
Action:
Severity: Minor.
ERR5055
SNMP trap: Yes
Unable to generate End-to-End Signaling tone due to one or more of the

following 1. No available conference slots, 2. no available TDS slots, or 3. no
available junctor slots or time slots to establish speech paths among all
involved parties, conference, and TDS cards.
Action: This is most likely a traffic problem. Check your traffic reports for the hour
to isolate the problem. If necessary, add hardware.
Severity: Minor.
ERR5056 l s c u
SNMP trap: Yes
An invalid EES lamp state exists on the Attendant console. The TN (l s c u) is

output.
Action:
Severity: Minor.
ERR5057 A D O T
SNMP trap: Yes
The D-channel interface for routing Network Message Service (NMS) facility
messages is not an SL-1 interface. Please verify your data base configuration.
Where: A = operation code for TCAP protocol; D = the D-channel sending
FACILITY message; O = Originating digits; T = Terminating digits
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 839 of 2360

ERR5058 A O T
Please check the system registers resources. Cannot obtain call register to
simulate the configuration request for sender feature originated at remote
switch. Where: A = operation code for TCAP protocol; O = Originating digits;
T = Terminating digits
Action:
Severity: Minor.
ERR5059
SNMP trap: Yes
No DNP message is sent to the Meridian Mail server. The DNP message for
ISDN/AP is not retrieved for a conference call to the Meridian Mail server when
activated from a remote switch.
Action:
Severity: Minor.
ERR5060 tn
SNMP trap: No
This unit has and LSPK key, but the DN defined does not match with any
loudspeaker.
Action:
Severity: Minor.
ERR5061
SNMP trap: Yes
You cannot synchronize a local clock. It must be set manually.

Action:
Severity: Minor.
ERR5062
SNMP trap: Yes
That TCAP package type is not recognized by the TSYNC feature.

Action:
Severity: Minor.
ERR5063
SNMP trap: Yes
That TCAP parameter is not recognized by the TSYNC feature.

Action:
Severity: Minor.
ERR5064
SNMP trap: Yes
The local clock cannot be synchronized. The local clock must be set.
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 840 of 2360

ERR5065
The TCAP package type is not recognized by the TSYNC feature.

Action:
Severity: Minor.
ERR5066
SNMP trap: No
That TCAP parameter is not recognized by the TSYNC feature.

Action:
Severity: Minor.
ERR5068
SNMP trap: No
Corrupted NFCR structures. TREE_EXIST of Hospitality.

Action:
Severity: Minor.
ERR5069
SNMP trap: Yes
Corrupted Hospitality tree. Hospitality procedure. See LD 43.

Action:
Severity: Minor.
ERR5070
SNMP trap: Yes
Prime DN key should be SCR or SCN for a Hospitality set. HSP_FORCEDISC

of Hospitality.
Action:
Severity: Minor.
ERR5071
SNMP trap: Yes
Hospitality tree does not exist. TREE_EXIST of Hospitality.

Action:
Severity: Minor.
ERR5072
SNMP trap: Yes
Accessed tree is not a Hospitality tree. HSP_GETLEAF_PTR of Hospitality.

Action:
Severity: Minor.
ERR5073
SNMP trap: Yes
Corrupted value of TREE_DIGIT_CODE in Hospitality tree.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 841 of 2360

ERR5090 data
Could not send an activation/deactivation message to an MFR.

Action:
Severity: Minor.
ERR5094
SNMP trap: Yes
Not the same dial tone frequency range defined on the route and on the dial
tone detector.
Action:
Severity: Minor.
ERR5095 tn
SNMP trap: No
Timer value conflict found on Universal Trunk or E & M Dictation card

(NT8D14/NT8D15) during audit parameter download.
Action:
Severity: Minor.
ERR5096
SNMP trap: Yes
A TNTRANS was successful when the AWU call was linked to the attendant
queue, but is now unsuccessful when the actual VIP call was attempted.
Action:
Severity: Minor.
ERR5098
SNMP trap: Yes
Invalid Cardlan Message. Received a data message before receiving an

address type message.
Action:
Severity: Minor.
ERR5099
SNMP trap: Yes
Invalid Cardlan Message. Received a retransmit message without sending a

message.
Action:
Severity: Minor.
ERR5100
SNMP trap: Yes
Invalid Cardlan message. Received an unrecognizable message.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 842 of 2360

ERR5101
Cardlan received a message out of sequence.

Action:
Severity: Minor.
ERR5102
SNMP trap: Yes
A write to 64180 Interrupt control register failed.

Action:
Severity: Minor.
ERR5103
SNMP trap: No
A write to 64180 Data control register failed.

Action:
Severity: Minor.
ERR5104
SNMP trap: No
Invalid Cardlan Message.

Action:
Severity: Minor.
ERR5105
SNMP trap: Yes
Received a retransmit message from an XPE pack.

Action:
Severity: Minor.
ERR5106
SNMP trap: Yes
Cardlan audit has detected a stuck cardlan state.

Action:
Severity: Minor.
ERR5107
SNMP trap: Yes
An invalid 64180 message has been received.

Action:
Severity: Minor.
ERR5108
SNMP trap: Yes
Hardware type error message received from cardlan.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 843 of 2360

ERR5109
Input IVD message has been discarded.

Action:
Severity: Minor.
ERR5110
SNMP trap: Yes
Output SSD message has been discarded.

Action: If this problem reoccurs, report problem to NT.
Severity: Minor.
ERR5111
SNMP trap: Yes
Invalid sequence type has been detected in a transmit XI type message.

Action:
Severity: Minor.
ERR5112
SNMP trap: Yes
Overload condition has been detected on an XPE line card. (Signaling to the
card has been disabled.) The card will be automatically enabled after 30
seconds.
Action: If problem persists, replace the faulty line card.
Severity: Minor.
ERR5113
SNMP trap: Yes
Three consecutive overload conditions have occurred for this card. The card
will be disabled and will not be re-enabled.
Action: You must replace the card.
Severity: Minor.
ERR5114
SNMP trap: Yes
A signaling channel has been disabled. The channel will be enabled

automatically.
Action:
Severity: Info.
ERR5115
SNMP trap: No
An overload card has been enabled again. Card should be operational.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 844 of 2360

ERR5120
The 1.5 Mb/s International ISDN Gateway feature does not support the
QPC472 DTI hardware for the MU/A law conversion and loss level
adjustments. Use the QPC720C PRI hardware for DTI trunk connectivity's.
Action:
Severity: Minor.
ERR5132 data
SNMP trap: Yes
For a tandem CDP DSC call, the incoming route and outgoing route belong to
the same Route List Index (RLI). To avoid potential looping problems, the CDP
DSC database may need to be modified. The output data is: customer
number, incoming route, outgoing route, outgoing route list index, outpulsed
digits.
Action:
Severity: Minor.
ERR5133
SNMP trap: Yes
Invalid content of optional information element.

Action:
Severity: Minor.
ERR5134
SNMP trap: Yes
Invalid information element for the message type.

Action:
Severity: Minor.
ERR5135
SNMP trap: Yes
Mandatory Cause Information Element missing in Release or Release

Complete message. Procedure I_RELEASE.
Action:
Severity: Minor.
ERR5136
SNMP trap: Yes
Invalid octet 3A in Calling Party Number Information Element. Procedure

CALLING_PTY_#.
Action:
Severity: Minor.
ERR5137
SNMP trap: Yes
Protocol error. Procedure DEC_STATUS.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 845 of 2360

ERR5138
Global Call Reference not supported. Procedure GLOBAL_CREF.

Action:
Severity: Minor.
ERR5142 x y
SNMP trap: Yes
Required Configurations for TRO-CM to work is missing.

Check TRO( Overlay 16) and/or VTRO ( overlay 17) prompts.
Where: X is the customer number.
Y is the route number.
Action: Enable TRO and/or VTRO.
Severity: Minor.
ERR5144
SNMP trap: Yes
Invalid length of information element.

Action:
Severity: Minor.
ERR5145
SNMP trap: Yes
Extension bit or IE length error in Party Category IE.

Action:
Severity: Minor.
ERR5146
SNMP trap: No
Extension bit or IE length error in Transit Counter IE.

Action:
Severity: Minor.
ERR5147
SNMP trap: No
Invalid numbering type, numbering plan combination.

Action:
Severity: Minor.
ERR5148
SNMP trap: No
SNMP trap: No
Invalid restart class.

Action:
Severity: Minor.
System Messages
Page 846 of 2360

ERR5149
Receipt of a Status reporting a Cause different than response to STATUS

ENQ.
Action:
Severity: Minor.
ERR5150
SNMP trap: No
T308 timed out twice in U19 channel. Put in maint-busy state followed by INT
(MSG_CR), D-channel number, UTN, State, Call Reference.
Action:
Severity: Minor.
ERR5151
SNMP trap: No
Undesirable Interface Indicator present in Channel ID IE.

Action:
Severity: Minor.
ERR5155
SNMP trap: No
OHAS treatment not given because it is not a legal OHAS DN.

Action:
Severity: Minor.
ERR5156
SNMP trap: Yes
The input buffer for the CDR TTY is still loaded. There is not enough space for
the number of characters to be output. The last character of the field may be
lost.
Action:
Severity: Minor.
ERR5157
SNMP trap: No
BRI call in wrong state. Call is cleared.

Action:
Severity: Minor.
ERR5158
SNMP trap: Yes
Invalid BRI call reference.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 847 of 2360

ERR5159
BRI B-channel status out of sync between Meridian 1 and the MISP; call
attempt
is aborted.
Action:
Severity: Info.
ERR5160
SNMP trap: Yes
BRI calls exceeded the limit for the DSL.

Action:
Severity: Minor.
ERR5161
SNMP trap: Yes
BRI call cannot be connected because of incompatibility of the call type with
the B-channel.
Action:
Severity: Minor.
ERR5162
SNMP trap: Yes
BRI call cannot be connected because a Call Register cannot be allocated.

Action:
Severity: Minor.
ERR5163
SNMP trap: Yes
BRI call processing message has timed out.

Action:
Severity: Minor.
ERR5164
SNMP trap: Yes
The BRI B-channel is in maintenance busy state.

Action:
Severity: Minor.
ERR5165
SNMP trap: Yes
Message received from invalid loop.

Action:
Severity: Minor.
ERR5168
SNMP trap: Yes
No output buffer available to send SSD message.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 848 of 2360

ERR5169
Message problem report from BRI line card.

Action:
Severity: Minor.
ERR5231
SNMP trap: Yes
No outgoing ESDI packet allowed when the ESDI card is disabled. Output:
AML: {aml number in decimal}
Action:
Severity: Minor.
ERR5232
SNMP trap: Yes
No incoming ESDI packet allowed when the ESDI card is disabled. Output:
AML: {aml number in decimal}.
Action:
Severity: Minor.
ERR5233
SNMP trap: Yes
The MSDL AML port is disabled. Therefore the incoming AML message is
disregarded. Output: AML: {aml number in decimal}.
Action:
Severity: Minor.
ERR5234
SNMP trap: Yes
The given AML (i.e., CLS) priority is disregarded. Output: AML: {aml number
in decimal} PRIO: {msg_priority in decimal}
Action:
Severity: Minor.
ERR5235
SNMP trap: Yes
The MSDLMISP_HDLR handler failed the outgoing XDU MSDL AML request.
Output: AML: {aml number in decimal} CODE: {msdlmisp_hdlr failure code in
decimal}
Action:
Severity: Minor.
ERR5236
SNMP trap: Yes
The MSDLMISP_HDLR handler failed the outgoing DU MSDL AML request.

Output: AML: {aml number in decimal} CODE: {msdlmisp_hdlr failure code in
decimal}
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 849 of 2360

ERR5237
The GET_O_BUF procedure failed to find a free outgoing buffer to send an

outgoing AML MSDL packet. Output: AML: {aml number in decimal}.
Action:
Severity: Minor.
ERR5241
SNMP trap: Yes
NIL pointer passed in as a parameter. Unable to update the TN block with the
wake up information. Cannot proceed. Procedure WRT_AWU_TN.
Action:
Severity: Minor.
ERR5242
SNMP trap: Yes
NIL pointer to the HM_STRUCT which contains the wake up information.

Cannot update and cannot proceed. Procedure WRT_AWU_TN.
Action:
Severity: Minor.
ERR5243 tn
SNMP trap: Yes
Digit collect message received from RAN trunk unit.

Action:
Severity: Minor.
ERR5244 type tn
SNMP trap: Yes
An invalid problem type has been received in a problem report message.

Action:
Severity: Minor.
ERR5245 type tn
SNMP trap: Yes
An invalid message type has been received from a card or unit.

Action:
Severity: Minor.
ERR5252
SNMP trap: Yes
The SDI I/F Handler could not retrieve a free buffer to send an outgoing
message.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 850 of 2360

ERR5254
The SDI I/F Handler encountered a problem transmitting an expedited

message
Action:
Severity: Minor.
ERR5255
SNMP trap: Yes
The SDI I/F Handler encountered a problem transmitting a standard ring

message.
Action:
Severity: Minor.
ERR5256
SNMP trap: Yes
The SDI I/F Handler received a data.indication primitive with a length of zero.
Action:
Severity: Minor.
ERR5257
SNMP trap: Yes
The SDI I/F Handler received a data.indication primitive but could not store
incoming characters because the TTY input buffer is full. Incoming characters
were discarded.
Action:
Severity: Minor.
ERR5258
SNMP trap: Yes
The SDI I/F Handler received a data.indication primitive but could not store all
incoming characters because the TTY input buffer became full. Some
incoming characters were discarded.
Action:
Severity: Minor.
ERR5259
SNMP trap: Yes
The SDI I/F Handler received an incoming message that had an unsupported
primitive ID.
Action:
Severity: Minor.
ERR5260
SNMP trap: Yes
The SDI I/F Handler received an incoming message that was not in the correct
MSDL ring or expedited buffer.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 851 of 2360

ERR5261
The SDI Port was disabled because the number of response timeouts on a
output primitive has been exceeded.
Action:
Severity: Minor.
ERR5262
SNMP trap: Yes
The SDI I/F Handler received a message from a port that is not enabled.
Action:
Severity: Minor.
ERR5263
SNMP trap: Yes
The SDI I/F Handler received an incoming message that could not be
processed in the current SDI state.
Action:
Severity: Minor.
ERR5264
SNMP trap: Yes
The SDI I/F Handler received a data.indication message that had more
characters than the maximum size of the TTY input buffer. The message is
discarded.
Action:
Severity: Minor.
ERR5266
SNMP trap: Yes
The SDI I/F Handler received a maintenance primitive message with an invalid
data length. The primitive message is discarded.
Action:
Severity: Minor.
ERR5267
SNMP trap: Yes
The SDI I/F Handler encountered a problem when trying to resynchronize

flow-control variables with the MSDL I/F Handler.
Action:
Severity: Minor.
ERR5272 tn
SNMP trap: Yes
An invalid maintenance message has been received from a card.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 852 of 2360

ERR5275
The DCH timed out while waiting for a test mode state change.
Action:
Severity: Minor.
SNMP trap: Yes
ERR5276 DCH: {DCH NUMBER} {DCH LINK STATE} An SSD message to process the MSDL
DCH output request queue is found to be lost. No action is required by the
craftsperson.
Action:
Severity: Minor.
ERR5277
SNMP trap: Yes
An invalid DCH link state was found and corrected.

Action:
Severity: Minor.
ERR5278
SNMP trap: Yes
The DCH state was found to be disabled, while the DCH port was disabled.
Action:
Severity: Minor.
ERR5279
SNMP trap: Yes
Application state was disabled, while the port on the MSDL card was enabled.
Action:
Severity: Minor.
ERR5280
SNMP trap: Yes
Wrong Optional Information Element Length.

Action:
Severity: Minor.
ERR5281
SNMP trap: Yes
Pointer BG_TFC_TODAY_PTR or BG_TFC_YESDY_PTR is NIL because of

the low memory problem or the memory corruption.
Action: Manually INIT the system to rebuild memory blocks. If manual INIT still
does not work, you should add more memory cards or remove data from the
system.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 853 of 2360

ERR5282 c dn r
Warning: Undefined RAN route for night RAN. Where: c = customer number,
dn = ACD DN, r = route number.
Action: Define the RAN route and trunk in LD 16 and LD 14, then enter the route
number at prompt NRRT in LD 23 for the ACD DN.
Severity: Minor.
ERR5283
SNMP trap: Yes
No message sent to the ICP computer.

Action: Update the computer database manually.
Severity: Minor.
ERR5284
SNMP trap: Yes
The DCH port on the MSDL card was found to be enabled, while the MSDL
card was not operational.
Action:
Severity: Minor.
ERR5285 c dn r
SNMP trap: Yes
Warning: Undefined RAN route for first RAN. Where: c = customer number, dn
= ACD DN, r = route number.
number at prompt FRRT and connection timer at prompt FRT in LD 23 for the
ACD DN.
Severity: Minor.
ERR5286 c dn r
SNMP trap: Yes
Warning: Undefined RAN route for second RAN. Where: c = customer

number, dn = ACD DN, r = route number.
number at prompt SRRT and connection timer at prompt SRT in LD 23 for the
ACD DN.
Severity: Minor.
ERR5287
SNMP trap: Yes
Invalid routing data encountered for Network Call Pickup/TAFAS. Digits do not
indicate a valid DSC/TSC/AC1/AC2 route access code to route the Call Pickup
request.
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 854 of 2360

ERR5300
DPNSS Route Optimization, invalid message received in Route Optimization

supplementary service state. The message is ignored.
Action:
Severity: Minor.
ERR5302
SNMP trap: Yes
M911 does not support test calls for the pilot release. (This does not apply to
Release 19.) Output data: TRK trktn ANI ani_count ani_digits.
Action:
Severity: Minor.
ERR5306
SNMP trap: No
Digit dialed exceed maximum allowed. More than 10 digits received.

Action:
Severity: Minor.
ERR5309 x y
SNMP trap: Yes
No music route for telephones defined for customer x using the FTC table y
with XTT=YES.
Action:
Severity: Minor.
ERR5310 l s c u x
SNMP trap: No
No music route defined for the trunk at TN l s c u using the FTC table x with
XTT=YES.
Action:
Severity: Minor.
ERR5313
SNMP trap: No
CP to CP Cable Loss. The CP to CP cable is either disconnected or faulty.

Action:
Severity: Minor.
ERR5314
SNMP trap: No
The remote CMB has lost power.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 855 of 2360

ERR5317
IPB parity threshold exceeded.

Action:
Severity: Minor.
ERR5318
SNMP trap: No
IPB IRQ threshold exceeded. Interrupt has been disabled.

Action:
Severity: Minor.
ERR5319
SNMP trap: No
IPB IRQ interrupt has been re-enabled.

Action:
Severity: Minor.
ERR5320
SNMP trap: No
Error occurred initializing CP.

Action:
Severity: Minor.
ERR5321
SNMP trap: No
Failure occurred opening IPB database.

Action:
Severity: Minor.
ERR5322
SNMP trap: No
SNMP trap: No
SNMP trap: No
CP database I/O error.

Action:
Severity: Minor.
ERR5323
IPB database I/O error.

Action:
Severity: Minor.
ERR5324 l s c u
The message received (Barring, Busy Tone, Line Break, Polarity Change,
Seize Acknowledge) is not supported by the Class of Service defined on the
trunk unit. Trunk disabled. Mismatch between hardware and software data
base. (Feature is XFCOT/XDID.)
Action: Reenable trunk to force software download.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 856 of 2360

ERR5325 l s c
Undefined PPM ID on Card {l s c}; PPM ID unchanged on card: hardware and

software configurations no longer match. If PPM ID was invalid or undefined
before, PPM has been disabled by card for all units on Card.
Action: Reconfigure PPM ID for card.
Severity: Minor.
ERR5326 l s c
SNMP trap: Yes
Undefined Busy Tone Id on Card {l s c }; Busy Tone ID unchanged on card:

hardware and software configurations no longer match. If Busy Tone ID was
invalid or undefined before, Tone supervision is not guaranteed to work for any
unit on the card.
Action: Reconfigure Busy Tone ID for card.
Severity: Minor.
SNMP trap: Yes
ERR5327 l s c u xxx xxx ... xxx Configuration not Supported on trunk {unit TN}. Trunk is
disabled. Configurations not supported are XXX (XXX ... XXX), where xxx is
one of: BUF PPM BTS BAR BAT DGC ATG.
Action: Examine Route and Trunk Unit configuration and change the offending
configuration, where: ATG = Autoguard (defined on unit: SEIZ), BAR =
Barring/Line Break Alarm (defined on unit Class of Service), BAT = Battery
Supervision (ARF BAT LBS) (defined by STYP in LD 16 for trunk unit.), BTS =
Busy Tone Supervised: (defined by STYP in LD 16 for trunk unit), BUF = PPM
Buffered/Unbuffered: (defined on route), DGC = DID Digit Collection Type
(DIP/DTN/MFC) (defined on unit Class of Service and route), PPM = PPM
Enabled/Disabled: (defined on route)
Severity: Minor.
ERR5328 l s c u
SNMP trap: Yes
Dialing Speed downloaded is not supported on the unit. Dialing speed for the
unit is not changed on the card. Hardware and software databases no longer
match.
Action: Change the dialing speed of the unit.
Severity: Minor.
ERR5329 l s c
SNMP trap: Yes
Companding law downloaded is not supported on the card. Companding law

on the card is not changed. Hardware and software databases no longer
match.
Action: Change the companding law of the system or change the card.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 857 of 2360

ERR5330 l s c u
Configuration conflict was detected on trunk unit during an audit. The

configuration as specified for the unit has been stored on the card.
Action:
Severity: Minor.
ERR5331
SNMP trap: Yes
Seize failure on trunk to Conventional Main. CBQCM or RVQCM process was

canceled.
Action:
Severity: Minor.
SNMP trap: Yes
ERR5332 msgtype tn Unknown content in message type received from superloop unit.
Action:
Severity: Minor.
SNMP trap: Yes
ERR5333 content msg type tn Unknown content in message type received from superloop unit.
Action:
Severity: Minor.
ERR5334
SNMP trap: Yes
The SACP package is not equipped. Idle Extension Notification (IEN) or

Attendant Blocking of DN (ABDN) request received from another location.
Action:
Severity: Minor.
ERR5335 x y
SNMP trap: Yes
Route x has a nonexistent XTDT table defined (y) and therefore no XTD could
be found.
Action: Print out tables on system (LD 97) and on XTD cards (LD20) and
reconfigure route with existing XTDT table.
Severity: Minor.
ERR5336
SNMP trap: No
GPT DTSL or NT5K75AA card configured in GPT mode. Status register not
accessible. Writeio failed. Pd. DTS_CLEAR_LINT
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 858 of 2360

ERR5337
accessible. Writeio failed. Pd. DTS_READY
Action:
Severity: Minor.
ERR5339
SNMP trap: Yes
accessible. Write I/O failed. Pd. DTS_END_OF_WRITE
Action:
Severity: Minor.
ERR5340
SNMP trap: Yes
GPT DTSL or NT5K75AA card configured in GPT mode. The timer has
expired and the I bit is still raised in the status register. Pd.
DTS_END_OF_WRITE
Action:
Severity: Minor.
ERR5341
SNMP trap: Yes
GPT DTSL, NT5K35AA card or NT5K75AA card. The software wanted to send
a message to the pack. The transmit FIFO on the pack was busy and there
was no more output buffer available. The value entered to DTOB in the Ovl 17
may be too small. This may also be a hardware fault. Pd. DTOB_Q_MSG
Action:
Severity: Minor.
ERR5342
SNMP trap: Yes
NT5K35AA card or NT5K75AA in NT mode. DTS_SEND failed in pd.

SEND_DPNSS_MSG.
Action:
Severity: Minor.
ERR5343
SNMP trap: Yes
GPT DTSL or NT5K75AA card in GPT mode. DTS_SEND failed in pd.

DASS_INPUT.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 859 of 2360

ERR5344
WRITE I/O failed. Pd. LED_OFF.

Action:
Severity: Minor.
ERR5345
SNMP trap: Yes
WRITE I/O failed. Pd. LED_ON.

Action:
Severity: Minor.
ERR5346
SNMP trap: Yes
Msg received from L2 but DTIB is full. The value entered to DTIB in the Ovl 17
may be too small. This may also be a hardware fault. Pd. DTS_LONG_MSG.
Action:
Severity: Minor.
ERR5347
SNMP trap: Yes
DTS_SEND failed in pd. WRITE_SIG_LINK.

Action:
Severity: Minor.
ERR5348
SNMP trap: Yes
Some msg were still waiting in the DTOB when the DISABLE msg is sent to
the pack. DTOB has been cleared. Pd. DDSL_DIS_MSG
Action:
Severity: Minor.
ERR5349
SNMP trap: Yes
Some msg were still waiting in the DTOB when the ENABLE msg is sent to the
pack. DTOB has been cleared. Pd. REQ_ENABLE.
Action:
Severity: Minor.
ERR5350
SNMP trap: Yes
The required FR is missing in the display IE received from SwissNet CO. The
charging information is ignored.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 860 of 2360

ERR5351
A FACILITY message other than the expected Camp-On activation message

was received at the MCDN/DPNSS call offer Gateway.
Action:
Severity: Minor.
ERR5352
SNMP trap: Yes
Could not allocate memory for Call ID table. No Call ID can be allocated. More
memory may be required.
Action:
Severity: Minor.
SNMP trap: Yes
ERR5355 DCH: {DCH number} (NO XBFR) Request to get an expedited buffer by the MSDL
DCH application failed.
Action:
Severity: Minor.
SNMP trap: Yes
ERR5356 DCH: {DCH number} EXP {Fail cause} Request to send a message through the
MSDL expedited interface failed.
Action:
Severity: Minor.
SNMP trap: Yes
ERR5357 DCH: {DCH number} CAUSE {Error cause} A flow control timer was found to be
active for MSDL D channel. It has been reset. No action is required by the
craftsperson.
Action:
Severity: Minor.
SNMP trap: Yes
ERR5358 DCH: {DCH number} CAUSE {Error cause} There should be an active flow control
timer for the MSDL D-channel. The flow control state has been reset. No
action is required by the craftsperson.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 861 of 2360

ERR5359
Under/Overflow condition in converting ICCL Tandem Count to/from IDA Loop

Avoidance Count.
Action:
Severity: Minor.
ERR5360 tn
SNMP trap: Yes
Loss Plan conflict found on an IPE trunk during audit parameter download.
The Loss Plan stored in the IPE trunk firmware for the unit has been reset to
the Loss Plan specified in the audit message.
Action:
Severity: Minor.
ERR5364
SNMP trap: Yes
NPID table does not exist for the 911 route.

Action: Check RDB for the 911 route.
Severity: Minor.
ERR5365
SNMP trap: No
M911_NPID_MHPTR is Nil.
Action:
Severity: Minor.
ERR5367
SNMP trap: No
Wrong configuration for NAS Routing when the attendant is in Night Service.
The following may indicate the problem: 1. NAS table is empty 2. Night DN
cannot be defined as DSC 3. Night DN is not allowed to have any forward of
any type (CFWAC, FBA, HTA, EHTA, HBTA)
Action:
Severity: Minor.
ERR5368 n
SNMP trap: Yes
Italian CO special services: route associated to the ITXX FFC code is not
configured anymore. Where: n = is the route originally configured for ITXX.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 862 of 2360

ERR5369 l s c u i
Invalid database configuration. Assigned authcode entered is not a valid

authcode in OVL 88, where: l = loop, s = shelf, c = card, u = unit, and i = index
of the assigned authcode
Action:
Severity: Minor.
ERR5370 tn
SNMP trap: Yes
USCR being accessed, but customer SCPL is not defined.

Action:
Severity: Minor.
ERR5371 tn
SNMP trap: Yes
Set has CLS USRA but FFC package is not equipped.

Action:
Severity: Minor.
ERR5384
SNMP trap: Yes
The total number of messages in queue exceeds the predefined number

defined in LD 17. The oldest message will be discarded in order to make room
for more. The deleted messages will be displayed following this error
message.
Action:
Severity: Minor.
ERR5385
SNMP trap: Yes
The message has been retransmitted for the specified number of times. This
message will be discarded. This deleted message will be displayed following
the error message.
Action:
Severity: Minor.
ERR5386
SNMP trap: Yes
Failed to allocate a CR for PMSI outgoing message.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 863 of 2360

ERR5387 a b c d
The PMSI outgoing message is exceed the maximum length. The character
will be ignored, where: a = address of the CR contains the message, b =
AUXPM, MAINPM, c = NAK counter, timeout counter, retransmission flag, and
d = message length
Action:
Severity: Minor.
ERR5388
SNMP trap: Yes
A digit other than 1 or 0 was entered for message monitoring option from a
maintenance telephone.
Action:
Severity: Minor.
ERR5389
SNMP trap: Yes
A non-polling Call Register was found when auditing the PMSI Call Registers.
Action:
Severity: Minor.
ERR5390
SNMP trap: Yes
Failed to allocate polling Call Register during initialization.

Action:
Severity: Minor.
ERR5391
SNMP trap: Yes
The primary port is not configured. Therefore, the message monitoring

commands cannot be executed from LD 37, or from a maintenance telephone.
Action:
Severity: Minor.
ERR5394 xy
SNMP trap: Yes
The customer number in the CDR Record uploaded from the MPH (Meridian
Packet Handler) is invalid. It is possible that the data stored in the MPH is out
of sync with the switch. Where: x = Customer Number received from MPH
(decimal); y = MPH loop number (Decimal)
Action:
Severity: Minor.
ERR5396
SNMP trap: Yes
Call is dropped due to TSP database change.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 864 of 2360

ERR5397
Service operation violated.

Action:
Severity: Minor.
ERR5398
SNMP trap: Yes
One of the following has occurred: 1. The specified RAN route is not
configured. 2. The specified route is not configured as a RAN route. 3. The
RAN route is configured but no RAN member exists.
Action:
Severity: Minor.
ERR5398 c dn
SNMP trap: Yes
For customer "c", DISA RAN "dn", either the DISA RAN is defined with an
invalid RAN route, or the route has no trunk member.
Action: The system administrator should verify the data base configuration.
Severity: Minor.
ERR5399
SNMP trap: Yes
Attendant Blocking of DN (ABDN) feature is not enabled.

Action:
Severity: Minor.
ERR5400 x y z
SNMP trap: Yes
The PNI in the Route Data Block (LD 16), as noted by the dialed digits, is the
same PNI number as currently programmed in the CDB (LD 15), where: x =
customer number, y = customer PNI number, z = digits dialed (first 8 digits)
Action:
Severity: Minor.
ERR5408
SNMP trap: No
NACD logical call request received that contained more than the supported
number of DNIS digits. The DNIS information has been truncated to the
supported length.
Action:
Severity: Minor.
ERR5409 tn
SNMP trap: Yes
The OHOL unit assigned to the conference loop is not valid. The spare dealer
conference loop was used.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 865 of 2360

ERR5410 tn
The OHOL unit assigned to the conference loop is not available. The spare
dealer conference loop was either non existing or not available.
Action:
Severity: Minor.
ERR5411 tn
SNMP trap: Yes
The M2616 telephone with CLS DELA, but is not an OHOL unit has initiated a
conference.
Action:
Severity: Minor.
ERR5412
SNMP trap: No
Invalid Status Register state in Low Speed Link to Option 11 Mail.

Action:
Severity: Minor.
ERR5413 tn
SNMP trap: Yes
No charging information available from CO for an outgoing call.

Action:
Severity: Minor.
ERR5414
SNMP trap: Yes
NIL AOC pointers found in protected trunk block. A possible solution is to

switch prompt MR in LD 16 to NO and then to switch it back to current value.
(TN of the trunk to follow).
Action:
Severity: Minor.
ERR5415
SNMP trap: Yes
For customer "c", either the Authcode-last Retry RAN is defined with an invalid
RAN route, or the route has no trunk member.
Action: The system administrator should verify the data base configuration.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 866 of 2360

ERR5416 c dn
For customer "c", DISA DN "dn", an incoming call has been waiting too long
(greater than RTMR) for DISA RAN. As a result, the caller is removed from the
RAN queue and the call proceeds to the next processing step.
Action: The system administrator should check on the RAN hardware to see if
the RAN trunks are capable of handling the traffic. An alternative to decreasing
the frequency of message appearance is increasing the time defined for the RAN
timer.
Severity: Minor.
ERR5417
SNMP trap: Yes
Message received from analog line card contains invalid message type. The
message is ignored. Format: ERR5417 tttt mmmm Where: tttt = the TN the
message was sent to in internat format mmmm = the message contents
Action:
Severity: Minor.
ERR5418
SNMP trap: Yes
Reverse Charging billing ID received in an AOC-D or AOC-E message from

CO for an outgoing call. This charging information is not taken into account.
(TN of the trunk to follow).
Action:
Severity: Minor.
ERR5419
SNMP trap: Yes
The currency information received from CO in AOC-D or AOC-E message

overflows the storing area limit (4 294 967 295). This charging information will
no be taken into account. (TN of the trunk to follow).
Action:
Severity: Minor.
ERR5420
SNMP trap: Yes
Overflow during computing of AOC information received from CO. This

charging information is not to be taken into account. (TN of the trunk to follow).
Action:
Severity: Minor.
ERR5421
SNMP trap: Yes
Null time stamp found in AOC-S structure. Processing of the charging

information not possible. (TN of the trunk to follow)
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 867 of 2360

ERR5422 tn
The AOC-D or AOC-E charging information received from CO is smaller than

the previous one. This information is discarded. (TN of the trunk to follow).
Action:
Severity: Minor.
ERR5423
SNMP trap: Yes
No 500 set TN found to send Message Waiting Indication from. Define in

Overlay 10 pseudo-TN block with SMSA Class of Service, where: y - customer
number
Action:
Severity: Minor.
ERR5424
SNMP trap: Yes
Procedure DO_XALC_SETS/DO_ANALOG_SETS module LIN5 Input

received from Standalone Mail Message server. These sets should not exist
outside of the configuration.
Action:
Severity: Minor.
ERR5425
SNMP trap: Yes
Buffer to the PRI (QPC720) hardware has overflowed.

Action:
Severity: Minor.
ERR5426
SNMP trap: Yes
Unexpected event for the VNS no bearer state handler {SOURCE} and if
SOURCE is a message received: {MESSAGE_TYPE}
Action:
Severity: Minor.
ERR5427
SNMP trap: Yes
Failure on a D-ch used by VNS.

Action:
Severity: Minor.
ERR5428
SNMP trap: Yes
Failure on a bearer trunk used by VNS, VNS TASK, TERMINAL, CRPTR, and
Time and Date output.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 868 of 2360

ERR5429
Unexpected event for the VNS state handler.

{WHATS_HAPPENED}{VNS_STATEPN:UVNS_DNPTR} and if VNS state
not 0:{CUST}{INDEX}.
Action:
Severity: Minor.
ERR5430
SNMP trap: Yes
Unexpected message received on a D-ch used by VNS {message type}.

Action:
Severity: Minor.
ERR5431
SNMP trap: Yes
Invalid message to send an a D-ch used by VNS {message type}.

Action:
Severity: Minor.
ERR5433
SNMP trap: Yes
FLH timer conflict found on the EXUT, XCOT cards during audit parameter
download. The FLH timer stored on the card is different form that which is
stored in the route for the unit. TN of the unit is given. Force disconnect timer
conflict found on the CIS incoming XDID card during audit parameter
download. Unproductive timer conflict found on the CIS outgoing XDID card
during audit parameter download.
Action:
Severity: Minor.
ERR5435 {TN}
SNMP trap: Yes
A recall message is reported by the XFEM card to the software for an AC15
tie trunk but it is ignored because the trunk is not in the "answered" state.
Where: {TN} TN of the faulty trunk.
Action: Check why the system at the far end sends a recall signal when the trunk
is in this state.
Severity: Minor.
ERR5436
SNMP trap: Yes
Number of Call Registers is too low to process DASS/DPNSS calls. This can
be changed in the configuration record (Overlay 17, prompt NCR).
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 869 of 2360

ERR5437
Set is configured with DIG Member Number matching the SPRE first digit and
one single DIG digit is expected. This should never happen unless wrong
configuration manipulation. For instance, going from a two-digit table to a
single-digit table without removing the single DIG Member Number matching
the first SPRE code digit.
Action:
Severity: Minor.
ERR5439
SNMP trap: Yes
CPND/CLID message not sent to card from output buffer. Output buffer
overflow on MCMO card. MCMO set buffer may not be large enough or is not
being emptied. Output Data: ERRyy x x tn, where: yy - the error number; x x reference numbers for the message; tn - terminal number (tn is in all decimals
(l s c u)).
Action: If the error messages are from the same TN, check the station or the
MCMO card for defects.
Severity: Minor.
ERR5440 mm nn
SNMP trap: Yes
Auto Set Inst. default Model No. in LD 97 mismatches with model set defined
in the data base, where: mm = the default model type and nn = the default
number.
Action:
Severity: Minor.
ERR5441
SNMP trap: Yes
Facility message error. Incorrect Facility message is sent to the user.

Action:
Severity: Minor.
ERR5442
SNMP trap: Yes
The Set Based Administration initialization routine could not allocate enough
memory for the restriction control blocks. Login limits are set to zero.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 870 of 2360

ERR5443 Y
BTD table associated with this trunk Y has been removed using Overlay 97.
Table 0 is used.
Action: Either recreate BTD table number as configured in trunk block or remove
all trunks associated with this card and reconfigure them with BTDT to match an
existing table.
Severity: Minor.
ERR5444 l s c
SNMP trap: Yes
A mismatch between previously downloaded Busy Tone Phase 1 cadence

value and audit message has occurred.
Action: Values on card are changed to reflect audit message. If problem
continues, report problem to NT.
Severity: Minor.
ERR5445 l s c
SNMP trap: Yes
A mismatch between previously downloaded Busy Tone Phase 2 cadence

value and audit message has occurred.
Severity: Minor.
ERR5446 l s c
SNMP trap: Yes
A mismatch between previously downloaded BTD call direction support value

and audit message has occurred.
Severity: Minor.
ERR5447 l s c
SNMP trap: Yes
A mismatch between previously downloaded Busy Tone Detect Level value

and audit message has occurred.
Action:
Severity: Minor.
ERR5448
SNMP trap: No
The EI Originating party has received a CCM for the connection of the EI
conference, but this CCM does not contain any EI-I.
Action: Still accept the message.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 871 of 2360

ERR5449
The Wanted party has become free while involved in an EI process (waiting
for the Unwanted's IPL or involved is an established EI conference), but it
could not be re-rung for lack of resources or bad configuration.
Action: Send CRM (Congestion) on the Originating channel.
Severity: Minor.
ERR5450
SNMP trap: Yes
BTD Frequency 0 value mismatch.

Action:
Severity: Info.
ERR5451
SNMP trap: Yes
BTD Frequency 1 value mismatch.

Action:
Severity: Info.
ERR5452
SNMP trap: Yes
BTD Tone Tolerance value mismatch

Action:
Severity: Info.
ERR5453
SNMP trap: Yes
BTD Tone Level Maximum value mismatch.

Action:
Severity: Info.
ERR5454
SNMP trap: Yes
BTD Tone Level Minimum value mismatch.

Action:
Severity: Info.
SNMP trap: Yes
ERR5468 TN, OCB level, NFCR Tree NFCR tree being used for Outgoing Call Barring does not
exist. No calls are barred.
Action: Turn off OCB on the set indicated, or configure the required tree.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 872 of 2360

ERR5469
The number of digits used for LEC and ANI DN is more or less than 7 when
trying to transmit ANI information to a CIS analogue/DTI trunk. The least
significant digits of the ANI DN will be omitted or missing digits will be
completed with ADDG.
Action: Check LEC prompt in LD 16 and ANI DN used.
Severity: Minor.
ERR5490
SNMP trap: Yes
Could not get a temporary Group Hunt block during Speed Call controller
modification of a Group Hunt list.
Action:
Severity: Minor.
ERR5491
SNMP trap: Yes
Bad CPNW configuration. The Speed Call list specified in the CPNW data
block of Overlay 18 is invalid.
Action:
Severity: Minor.
ERR5492
SNMP trap: Yes
The PINX DN cannot be reached. Either the configuration is invalid or the

D-channel is disabled. Or local PINX DN not defined.
Action:
Severity: Minor.
ERR5493
SNMP trap: Yes
TCAP or ROSE protocol error for CPNW feature.

Action:
Severity: Minor.
ERR5494 x y z
SNMP trap: Yes
Where x = customer number, y = GPHT list number, z = dialed PLDN digits. A

user has attempted to use a PLDN with USE = SCLU (Speed Call List User)
or SCLC (Speed Call List Controller) to access a Group Hunt list. This
configuration is not supported.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 873 of 2360

ERR5511
BTD Table 0 is not defined.

Action: Use Overlay 97 to create Table 0.
Severity: Minor.
ERR5512 n
SNMP trap: Yes
ERR020 messages for loop n has been automatically turned OFF. ERR020
will be automatically turned back ON in 20 seconds.
Action:
Severity: Minor.
ERR5513 n
SNMP trap: Yes
ERR020 messages for loop n has been automatically turned ON.

Action:
Severity: Minor.
ERR5514
SNMP trap: Yes
Multiple appearances of a DN that is associated with a DTM key or with key

00 of a TN which has a DTM key is not permitted. Output data: TN location,
DN for which an illegal multiple appearance has been found.
Action: Craftsperson must either delete the multiple appearance, use another
DN, or delete the DTM key.
Severity: Info.
ERR5515
SNMP trap: Yes
Applicable when MULT = YES Configuration error. Regarding the value of the
multiplier received from the CO, the value of RURC is not correct. The RURC
value should not be greater than the multiplier.
Action: Change RURC exponent value.
Severity: Minor.
ERR5516
SNMP trap: Yes
The IDs configured on the NAS routing table must lead to a full DPNSS route,
or full MCDN routes to routes including a single MCDN to DPNSS1 gateway.
Action: Reconfigure the NAS routing table.
Severity: Minor.
ERR5517
SNMP trap: Yes
The IDs configured in the NAS routing tables must be UDP or CDP DNs.
Action: Reconfigure the NAS routing table.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 874 of 2360

ERR5521 x
Where x= Speed Call List Number. Looping has been found between Speed
Call lists. This could happen if a speed call list routes a call to itself (by having
a member which is a PLDN which accesses its own list). Speed Call list
number x was the last list call reached.
Action: Alter the configuration to avoid such looping.
Severity: Minor.
ERR5522
SNMP trap: Yes
A recall message sent by the Norstar is reported by the XFEM card for an
AC15 tie trunk but it is ignored because the trunk is already in split outgoing
mode. {TN} TN of the AC15 trunk.
Action:
Severity: Minor.
ERR5523
SNMP trap: Yes
Parsing of name information's received from QSIG failed.

Action: Inconsistent name information has been received. Contact your
Severity: Minor.
ERR5524
SNMP trap: Yes
A network call park operation is tried from one node to another for which the
Call Park Networkwide feature is not defined.
Action: Contact your system administrator if the Call Park Networkwide
operation is not defined.
Severity: Major.
ERR5525
SNMP trap: Yes
Parsing of name information received.

Action:
Severity: Info.
ERR5526
SNMP trap: Yes
Illegal multiple appearance of a DN assigned to a designated data mode key.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 875 of 2360

ERR5532
DNIS has more than 30 digits in the PCI message which is not supported by
the MMail.
Severity: Minor.
ERR5533
SNMP trap: Yes
SETUP message has been received on an Australian UIPE interface with the
request for a permanent connection to be established. The ISPC Reference
Number included in the message do not allow the link to be established for the
following reason: The format of the message is: ERR5533 -x -y where: y D-channel number; x - Detail of the problem: 1 - Unknown ISPC Reference
Number. There is no TN on any Phantom DTI2 loops configured with this ISPC
Reference Number. 2 - The ISPC Call Reference number is not delimited by a
star '*' character in Calling number field of the received SETUP message. 3 The ISPC Call Reference number is empty. 4 - The ISPC Call Reference
number is made of information other than the digits in the IA5 format. 5 - The
ISPC Call Reference number is longer than 7 digits. 6 - The TN for which the
ISPC Reference number is configured is on a Phantom DTI2 loop not on the
same group as the PRI2 trunk on which the request was received.
Action: Check the system configuration. If the configuration is correct, contact
Severity: Major.
ERR5534
SNMP trap: Yes
The ISPC Call Reference number is empty in the Calling number field of the
received SETUP message. This message is displayed when a SETUP
message has been received on request for a permanent connection to be
established.
Severity: Major.
SNMP trap: No
ERR5535 TN {cause} An improper configuration has been detected when an ISPC link is used to
convey D-channel signaling. Where: TN - ISPC D-channel slave trunk, {cause}
- represents the error cause: 0: SET_DTI22_PTRS failed with DTI2 phantom
trunk; 2: The trunk must be a TIE trunk; 3: The trunk must be configured with
the DTN class of service; 4: Data corruption with the route pointer; 5: The route
is not an ISL trunk; 6: The trunk is not a DID trunk; 7: The route is not
configured with DSEL = DTA; 8: The route must not be an ISL route; 9: The
route is not configured with DLTN = YES; 10: The route is not configured as
incoming; 11: The route is not configured with PRDL = BSY; 12: The route is
not configured with DTD = YES; 13: The route is not configured as outgoing;
System Messages
Page 876 of 2360

14: The route is not configured with NEDC = ETH; 15: The route is not
configured with FEDC = ETH; 16: The route is not configured with CPDC =
NO; 17: DDD_PACKAGE is restricted.
Action: Check the system configuration and use overlay 96 to restart the
process if required.
Severity: Major.
ERR5536
SNMP trap: Yes
The ISPC Call Reference number length is longer than 7 digits. This message
is displayed when a SETUP message has been received on an Australian
UIPE interface with the request for a permanent connection to be established.
Action: Contact the Administrative Entity of the Public Network.
Severity: Major.
ERR5537 TN DN
SNMP trap: No
The maximum number of calls to be performed on a data interface for

D-channel signaling to use an ISPD link has been reached. This manual
process has been stopped. The format of the message is: ERR5537 TN DN,
where: TN - ISPC D-channel slave trunk, DN - represents the digits received
by the Meridian 1. If no digits have been received, nothing is printed. If some
digits have been received but the DN is incomplete or invalid, the digits will be
printed.
Action: Check system configuration, and use overlay 96 to restart the process if
required. Also, check the system configuration of the far end Meridian 1.
Severity: Major.
ERR5538
SNMP trap: Yes
A SETUP message has been received on an Australian UIPE interface with

the request for a permanent connection to be established. As the ISPC
package (no 313) is not enabled, the request has been rejected.
Action: Enable Package ISPD (no 313) and reload the PBX if an ISPC link is
required.
Severity: Minor.
SNMP trap: Yes
ERR5539 {type of error} {event/state} {park1} {parm2}{parm3} Call Completion (CC)

Supplementary Service. Protocol error detected by CC QSIG protocol handler.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 877 of 2360

ERR5549 x y tn rtclock Cannot send Mobility pad message to MXC card where x,y represent the
reference numbers for the message; tn - terminal number (tn is in all decimals
(l s c u)); rtclock is an internal
Action: If the message numbers are from the same TN, check the card for
problems.
Severity: Minor.
ERR5575 tn
SNMP trap: Yes
The M3900 set has firmware that cannot use some Phase 3 features.
Action: Upgrade the firmware of the set on that tn.
Severity: Minor.
ERR5576
SNMP trap: Yes
ERR5575 is suppressed.
Action: If necessary, use the MIDN command in LD 135 to run the daily routine.
The message turns on automatically during the daily routine.
Severity: Info.
ERR5700
SNMP trap: Yes
RFC was called from LD 117 with illegal value for the "action" parameter (not
one of NEW, CHG or OUT).
Action: Please contact your system administrator
Severity: Major.
ERR5701
SNMP trap: No
RFC was called from LD 117 to create one of the following block types:
BKPR_BLK,GR_DRC_BLK or GR_S_SC_BLK but the pointer to the source
buffer is NIL.
Severity: Major.
ERR5702
SNMP trap: No
RFC was called from ld 117 to create one of the following block types:
BKPR_BLK,GR_DRC_BLK or GR_S_SC_BLK but failed to allocate protected
memory.
Severity: Major.
SNMP trap: No
System Messages
Page 878 of 2360

ERR5703
RFCwas called from ld 117 to create one of the following protected block
types: BKPR_BLK,GR_DRC_BLK or GR_S_SC_BLK but the block already
exists.
Severity: Major.
ERR5704
SNMP trap: No
RFCwas called from ld 117 to remove one of the following protected block
types: BKPR_BLK,GR_DRC_BLK or GR_S_SC_BLK but the block does not
exist.
Severity: Major.
ERR5705
SNMP trap: No
RESERVED: Number of SS_MSGCRs to be processed exceeded the limit.

Severity: Minor.
ERR8985 x y
SNMP trap: Yes
A faulty Group Hunt member has been encountered whilst terminating on a

GPHT list or altering the list. Where: x = GPHT list number, y = index number
of the faulty GPHT number
Action:
Severity: Minor.
ERR8986
SNMP trap: Yes
This TN should have CFW AC configured. Procedure icp_storecfw and

icp_act_allowed.
Action:
Severity: Minor.
ERR8987
SNMP trap: Yes
FFC cannot be used without SPRE defined.

Action:
Severity: Minor.
ERR8988
SNMP trap: Yes
Flexible dial tone detection (FDTD) table not configured.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 879 of 2360

ERR8999 x
Attempt to use a nonexisting ART x. Default for route type is used.

Action:
Severity: Minor.
ERR9000 C T A
SNMP trap: Yes
NAS routing is incorrectly configured. The routing tables should contain DNs
to reach remote attendants on the network. The configuration error was
noticed by the software while processing CUST c, customer number, TEN t,
tenant number, ALT a, alternative. The previous alternative route is probably
badly defined, for example as a local DN.
Action: Redefine the previous alternative route.
Severity: Major.
ERR9004 TN
SNMP trap: Yes
Horizon terminals must be defined with a display.

Action:
Severity: Minor.
ERR9005 TN
SNMP trap: No
Invalid input for Horizon terminal type.

Action:
Severity: Info.
ERR9006
SNMP trap: No
Invalid ESRT configuration. ACCD intercept treatment has been given to the
set.
Action: Correct the database.
Severity: Major.
ERR9007
SNMP trap: Yes
Invalid OSDN configuration, caller information is not linked.

Action: Correct the database
Severity: Major.
ERR9008
SNMP trap: Yes
Station set specified by OSDN is not configured with an OSN key. Caller
information is not linked.
Severity: Major.
SNMP trap: Yes
System Messages
Page 880 of 2360

ERR9009
Undefined CLID entry is configured for the originating DN of an ESA call.

Calling number is set to customer's DFCL.
Severity: Major.
ERR9012
SNMP trap: Yes
ESA CLID configuration error detected. Calling number for ESA call is set to
customer's DFCL.
Severity: Major.
SNMP trap: Yes
ERR9013 TN N data Parsing of QSIG Diversion Information's received failed, or QSIG Diversion
information's sent have been answered unexpectedly. Incorrect QSIG
Diversion information's are dropped. Output parameters: TN = TN from which
information is received. N = error number. data = dependant on error number
(N)
Action: Report the problem along with the output parameters.
Severity: Info.
ERR9016
SNMP trap: Yes
x NON PROVISION SERVICE y An incoming SETUP with NSF IE message

is received from the NI-2 CBC master route and the service specified in the
facility coding field cannot be found in service route associating with the
master route. The call was terminated as public call. Where: x = Master route
number, y = NSF IE in Hex format
Action: Configure a service route.
Severity: Major.
ERR9017
SNMP trap: Yes
SNMP trap: Yes
x INVALID CODING y
Action:
Severity: Major.
ERR9019
A TN was found without a defined port type. The default will be assigned. TN
and invalid port type are displayed.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 881 of 2360

ERR9020
A TN was found without a valid card index. No transmission will be applied to

this TN. The TN is printed.
Action:
Severity: Minor.
ERR9021
SNMP trap: No
Type 5A PAD messages were specified for an unknown trunk card type. The
TN is printed.
Severity: Minor.
ERR9022
SNMP trap: No
Type 5B PAD messages were specified for an unknown trunk card type. The
TN is printed.
Severity: Minor.
ERR9023
SNMP trap: No
Incorrect database configuration encountered. CNUS class of service conflicts

with CNAA class of service.
Action: Correct the database configuration in LD10.
Severity: Minor.
SNMP trap: Yes
ERR9027xxx DCH TN STATEPM Warning: Cannot use the B-channel or the ISL trunk because
the STATEPM of the trunk is not idle. The B-channel or ISL trunk is put in a
maintenance busy state.
Action: Manually restart the given B-channel or the ISL trunk.
Severity: Major.
ERR9030
SNMP trap: Yes
XMI failure. Can't send PPM message to DPI card.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 882 of 2360

ERR9031 y y y z
Where: y y y = TN, z = key number. The programming sequence has been

entered for key z on TN yyy. Programming this key's label from the set should
be allowed, but the required memory has not been allocated.
Action: To allocate the required memory, assign a PSL to key z. In LD 11, use
the CHG command. At the KEY prompt, type 'z :{psl}' where {psl} is any string up
to 10 characters.
Severity: Minor.
ERR9032 tn
SNMP trap: No
Channel is put in lockout state.

Action:
Severity: Minor.
ERR9033 tn x y
SNMP trap: Yes
An incoming SETUP was received on a busy channel. Where: tn = terminal

number, x = time, y = call reference of existing call
Action:
Severity: Critical.
ERR9034 x y z
SNMP trap: No
Cannot send an ISRM containing a Message Waiting NSI string. There is no

NORTEL message waiting NSI string configured in Overlay 15 (for Notification
(NOTI) or Cancellation (CNC)). (Procedure FORMAT_MWI_NSI. Module
DIO).
Action:
Severity: Minor.
SNMP trap: Yes
ERR9036 DO NOT PRINT The TMDI output buffer is not allocated.

Action: Ensure that some unprotected memory is available, then use LD 17 and
CHG CEQU (no real changes required, to rebuild the output buffer.
Severity: Major.
ERR9044
SNMP trap: Yes
The ANI data should be retrieved from an ANI Entry but the specified Entry
does not exist in the Customer Data Block.
Action: Configure the ANI Entry that is needed (Overlay 15).
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 883 of 2360

ERR9048
AUDIT turned on Analog CLI.

Action:
Severity: Minor.
ERR9049
SNMP trap: No
AUDIT turned off on Analog CLI.

Action:
Severity: Minor.
ERR9050
SNMP trap: No
RAN/MIRAN channel is not available.

Action:
Severity: Minor.
ERR9051
SNMP trap: Yes
The CAC conversion data must be retrieved from a CAC conversion entry but
the specified entry does not exist in the Customer Data Block. The default
table is used instead.
Action: Configure the CAC conversion entry that is needed (Overlay 15).
Severity: Minor.
ERR9052
SNMP trap: No
VNS does not support Backup D-channel signaling.

Action: VNS call made using BDCH.
Severity: Info.
ERR9056
SNMP trap: Yes
The XCT card is the only card supported by TWR1. The MFS card is not
supported. The call cannot be completed
Severity: Major.
ERR9057
SNMP trap: Yes
The length of FLEN in LD 86 and LD 90 is not configured. The call cannot be

completed.
Action: Contact your technical support group. The FLEN must be configured.
Severity: Major.
SNMP trap: No
System Messages
Page 884 of 2360

ERR9058
The supervision is not of the expected type.

Action:
Severity: Minor.
ERR9059
SNMP trap: No
The data received for INS-J is more than 128 bytes.

Action:
Severity: Minor.
ERR9060
SNMP trap: No
An invalid parameter type has been received.

Action:
Severity: Minor.
ERR9061
SNMP trap: Yes
INS-J data was not expected.

Action:
Severity: Minor.
ERR9062
SNMP trap: Yes
No DID digits were received in the INS-J data.

Action:
Severity: Info.
ERR9063
SNMP trap: Yes
An ACLI SSD message was unexpectedly received.

Action:
Severity: Minor.
ERR9064
SNMP trap: Yes
The father CR is nil for the ACLI son call register.

Action:
Severity: Minor.
ERR9065
SNMP trap: No
Parsing of QSIG Transfer information received failed.

Severity: Info.
ERR9290
553-3001-411
SNMP trap: Yes
Available unprotected memory is below acceptable levels. A system

initialization may recover memory if blocks have become unavailable or
memory is heavily fragmented. If initialization does not eliminate the error, or
Standard 15.00
January 2006
Page 885 of 2360

is not possible in the operating environment, remove some data from the
system to
free up more memory. This error will continue to be printed periodically until
the low memory condition is corrected.
Parameters: page (always 0), remaining memory
Action: Perform a system initialization as soon as possible. Do not attempt to
add data to the system until the this condition is corrected. Report the problem to
the operating company if initialization does not eliminate the problem and data
cannot be removed from the system.
Severity: Critical.
ERR9291
SNMP trap: Yes
Available protected memory is below acceptable levels. Service change

should not be attempted. If this error occurs only once it may indicate a
transient condition that has been corrected. If it occurs repeatedly a system
initialization to recover fragmented unprotected memory may free enough
memory to allow protected memory space to grow (16K required). If
initialization does not eliminate the low memory condition a system reload
may. If reload
does not help then the system is reaching it's capacity and some data may
need to be removed in order to allow other data to be created.
Parameters: page (always 1), memory available
Action: If the error occurs more than once (about 15 minutes apart) a system
initialization should be performed as soon as possible. Check the memory
available by loading a service change overlay. If memory is still low perform a
system reload. If memory remains low after a reload then remove data that is less
critical in order to create new data.
Severity: Critical.
ERR9292
SNMP trap: Yes
Corruption in TIDY values.

Action: Please configure the Route again.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 886 of 2360
553-3001-411
Standard 15.00
January 2006
Page 887 of 2360
ESA: Emergency Services Access

Messages
ESA0001
Remote Virtual Office user logged in from a site without ESA support.
Action: If this user dials the ESDN, their call will not be redirected to the PSAP
serving their current location (remote) -- It will be directed to the PSAP serving the
site local to the error message (local). The remote site signaled that it did not
support ESA for Virtual Office. To correct the issue, make sure the software
version of the remote site supports ESA for Virtual Office. Additionally, confirm
that the remote site has the ESA package and that the customer ESA data is
configured.
Severity: Info.
ESA0002
SNMP trap: Yes
Remote Virtual Office user originated ESA call to local PSAP.

Action: A user has been connected to an incorrect PSAP without their
knowledge. Verify that the emergency situation was dealt with. The
site where the user is located (remote) signaled that it did not support ESA for
Virtual Office. (see corresponding ESA0001) To correct the issue, make sure the
software version of the remote site supports ESA for Virtual Office. Additionally,
confirm that the remote site has the ESA package and that the customer ESA
data is configured.
Severity: Major.
ESA0003
SNMP trap: Yes
Active call preempted by Virtual Office ESA call

Action: When a local IP phone registers to a remote Call Server using Virtual
Office, the local TN is logged out. It is possible that a second user could use
Virtual Office to occupy the logged out local TN. If the first user makes an ESA
call, the IP phone will return to the local Call Server to place the ESA call. When
this occurs, if there is a second user occupying the local TN then that user will be
preempted. This message indicates that this has occurred to a user that had an
established call.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 888 of 2360

ESA0004
Virtual Office login preempted by Virtual Office ESA call

Action: When a local IP phone registers to a remote Call Server using Virtual
Office, the local TN is logged out. It is possible that a second user could use
Virtual Office to occupy the logged out local TN. If the first user makes an ESA
call, the IP phone will return to the local Call Server to place the ESA call. When
this occurs, if there is a second user occupying the local TN then that user will be
reempted.
This message indicates that this has occurred to a user that did not have any
established call.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 889 of 2360
ESDA: Enhanced Serial Data Interface

(LD 48)
The Enhanced Serial Data Interface card provides the LAPB protocol used for
communication between the system CPU and an external Value Added Server
such as the Meridian Mail MP. The Command and Status Link (CSL) and
ISDN Application Protocol use Enhanced Serial Data Interface (ESDI) cards.
The ESDI and related application protocols are maintained by the Link
Diagnostic program (LD 48). The following messages indicate status and error
conditions of the CSL software and/or the ESDI card.
An expanded format is used to provide system message information. When
applicable, both display formats are shown.
Messages
ESDA0001 n t x
Link n is out-of-service, where t is the system time when it occurs and x is the
cause as follows: Unformatted: ESDA001 n t x Formatted: ESDA001
dd/mm/yy 00009 MSG OPRDAT: n x Where: n = CSL number, t = system time
(only appears when unformatted), x = 1 = HDLC retransmission error
threshold reached, 2 = HDLC CRC error threshold reached, 3 = HDLC
overflow error threshold reached, 4 = HDLC abort error threshold reached, 5
= HDLC detect protocol error l, 6 = HDLC hardware failure, 7 = HDLC detected
link 3 failure, or far-end disconnect, 8 = HDLC was restarted by ESDI firmware
externally, 9 = Layer 7 not responding to polling message. The polling timer
has timed out.
Action:
Severity: Critical.
ESDA0002 n t
SNMP trap: Yes
Link (n) link layer is connected at system time (t). With X11 Release 19 or later,
and package 243 equipped, a new expanded format is displayed. Both display
formats are shown here. Unformatted: ESDA002 n t Formatted: ESDA002
dd/mm/yy 00009 MSG OPRDAT: n Where: n = CSL number and t = system
time (only appears when unformatted)Grant Link (n) link layer is connected at
system time (t). With X11 Release 19 or later, and package 243 equipped, a
new expanded format is displayed. Both display formats are shown here.
System Messages
Page 890 of 2360

Unformatted: ESDA002 n t Formatted: ESDA002 dd/mm/yy 00009 MSG
OPRDAT: n Where: n = CSL number and t = system time (only appears when
unformatted)
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 891 of 2360
ESDI: Enhanced Serial Data Interface (LD

48)
The Enhanced Serial Data Interface card provides the LAPB protocol used for
communication between the SL-1 CPU and an external Value Added Server
such as the Meridian Mail MP. The Command and Status Link (CSL) and
ISDN Application Protocol use Enhanced Serial Data Interface (ESDI) cards.
The ESDI and related application protocols are maintained by the Link
Diagnostic program (LD 48). The following messages indicate status and error
conditions of the CSL software and/or the ESDI card.
Messages
ESDI0001
The ESDI card did not respond to self test command. The card could be dead.
Action:
Severity: Minor.
ESDI0002
SNMP trap: Yes
No loop-back message received. ESDI card could be malfunctioning or dead.

Action:
Severity: Minor.
ESDI0003
SNMP trap: Yes
The ESDI link setup (HDLC handshaking) failed.

Action:
Severity: Minor.
ESDI0004
SNMP trap: Yes
The ESDI did not return any response to the START LINK SETUP command.
Action:
Severity: Minor.
ESDI0007
SNMP trap: Yes
The ESDI self test failed.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 892 of 2360

ESDI0008
Local loop back test failed.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 893 of 2360
ESN: Electronic Switched Network (LD

86, LD 87 and LD 9
The ESN messages are generated while performing service change
procedures in LD 86, 87, 88, and 90.
Messages
ESN0000
Program has loaded.

Action:
Severity: Info.
ESN0001
SNMP trap: No
SNMP trap: No
Illegal input character.

Action:
Severity: Info.
ESN0002
Digit input instead of alpha input.

Action: Enter digits.
Severity: Info.
ESN0003
SNMP trap: No
Service change not allowed from maintenance telephone.

Action:
Severity: Info.
ESN0004
SNMP trap: No
Input must be one of (NEW, OUT, CHG, PRT, END).

Action:
Severity: Info.
ESN0006
SNMP trap: No
Null input is not allowed.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 894 of 2360

ESN0007

Action:
Severity: Info.
ESN0008
SNMP trap: No
Customer number out-of-range (0-31).

Action:
Severity: Info.
ESN0009
SNMP trap: No
Unable to match input field with stored mnemonics.

Action:
Severity: Info.
ESN0010
SNMP trap: No
Conflicts with existing shorter number.

Action:
Severity: Info.
ESN0011
SNMP trap: No
Conflicts with existing number.

Action:
Severity: Info.
ESN0012
SNMP trap: No
SNMP trap: No
Error in DN translator.
Action:
Severity: Info.
ESN0013
Conflicts with existing longer number.

Action:
Severity: Info.
ESN0014
SNMP trap: No
Route list index number out-of-range (0-255 for NARS, 0-127 for BARS, 0-7
for CDP).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 895 of 2360

ESN0015
ESN data block does not exist.

Action:
Severity: Info.
ESN0016
SNMP trap: No
ESN data block already exists.

Action:
Severity: Info.
ESN0017
SNMP trap: No
Route list does not exist.

Action:
Severity: Info.
ESN0018
SNMP trap: No
Route list already exists.

Action:
Severity: Info.
ESN0019
SNMP trap: No
SNMP trap: No
Out-of-range (1-7).
Action:
Severity: Info.
ESN0020
Invalid response (digits or X only).

Action:
Severity: Info.
ESN0021
SNMP trap: No
Update route list entry one at a time.

Action:
Severity: Info.
ESN0022
SNMP trap: No
Route list entry does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 896 of 2360

ESN0023
Initial route set exceeds available entries in route list.

Action:
Severity: Info.
ESN0024
SNMP trap: No
SNMP trap: No
Out-of-range (0-31).
Action:
Severity: Info.
ESN0025
Invalid response (YES/NO).

Action:
Severity: Info.
ESN0026
SNMP trap: No
Digit manipulation index number out-of-range. (1-255 for NARS/BARS, 1-31

for CDP, 0-999 with FNP package 160).
Action:
Severity: Info.
ESN0027
SNMP trap: No
NO entry in a route list is not allowed.

Action:
Severity: Info.
ESN0028
SNMP trap: No
Network translators, route list blocks, digit manipulation tables, FCAS tables,
or CDP list still exist; cannot remove.
Action:
Severity: Info.
ESN0029
SNMP trap: No
Digit manipulation table does not exist.

Action:
Severity: Info.
ESN0030
SNMP trap: No
Route does not exist or exists but has no members.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 897 of 2360

ESN0031
Route type not allowed.

Action:
Severity: Info.
ESN0032
SNMP trap: No
Maximum number of location codes out-of-range. If range is less than 16001,

then enable LOCX package and FNP package to configure more location
codes.
Action: Increase MXLC.
Severity: Info.
ESN0033
SNMP trap: No
Maximum number of supplemental digit restriction table entries out-of-range.

Action: Check/increase the maximum size and re-enter.
Severity: Info.
ESN0034
SNMP trap: No
Maximum number of digit manipulation tables out-of-range.

Action: Increase MXDM.
Severity: Info.
ESN0035
SNMP trap: No
Maximum number of route lists out-of-range.

Action: Increase MXRI.
Severity: Info.
ESN0036
SNMP trap: No
MXLC cannot be less than defined LOC codes.

Action:
Severity: Info.
ESN0037
SNMP trap: No
MXSD cannot be less than defined SDR tables.

Action:
Severity: Info.
ESN0038
SNMP trap: No
MXDM cannot be less than defined digit manipulation tables.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 898 of 2360

ESN0039
MXRL cannot be less than defined route lists.

Action:
Severity: Info.
ESN0040
SNMP trap: No
SNMP trap: No
SNMP trap: No
Too many input fields.

Action:
Severity: Info.
ESN0041
Too few input fields.

Action:
Severity: Info.
ESN0042
TOD schedule/hour/minute out of range.

Action:
Severity: Info.
ESN0043
SNMP trap: No
TOD starting period cannot be greater than ending period.

Action:
Severity: Info.
ESN0044
SNMP trap: No
Access code out-of-range (0-99).

Action:
Severity: Info.
ESN0045
SNMP trap: No
Access code 2 cannot be same as access code 1.

Action:
Severity: Info.
ESN0046
SNMP trap: No
Access code already used.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 899 of 2360

ESN0047
Digit manipulation table entry already exists.

Action:
Severity: Info.
ESN0048
SNMP trap: No
Digit manipulation table entry does not exist.

Action:
Severity: Info.
ESN0049
SNMP trap: No
Too many digits to be deleted.

Action: Re-enter the number of digits to be deleted (between 0-19).
Severity: Info.
ESN0050
SNMP trap: No
Too many digits to be inserted.

Action: Re-enter the number of digits to be inserted (between 0-31).
Severity: Info.
ESN0051
SNMP trap: No
SNMP trap: No
Out-of-range (0-8).
Action:
Severity: Info.
ESN0052
OHQ time limit out-of-range (2-60).

Action:
Severity: Info.
ESN0053
SNMP trap: No
CBQ Call-Back time limit out-of-range (10-30).

Action:
Severity: Info.
ESN0054
SNMP trap: No
ERWT delay time out-of-range (0-10).

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 900 of 2360

ESN0055
Input not completed.

Action:
Severity: Info.
ESN0056
SNMP trap: No
CAS and NAS are mutually exclusive and cannot be configured for the same
customer.
Action: If you are configuring CAS, disable NAS in overlay 86; if you are
configuring NAS, disable CAS in overlay 15.
Severity: Info.
ESN0060
SNMP trap: No
Invalid response (AC1, AC2, SUM).

Action:
Severity: Info.
ESN0061
SNMP trap: No
Invalid response (LOC, NPA, NXX, SPN, HNPA, HLOC, ALL).

Action:
Severity: Info.
ESN0062
SNMP trap: No
No more available location codes (out or expand MXLC).

Action:
Severity: Info.
ESN0063
SNMP trap: No
A maximum of 10 digits allowed.

Action:
Severity: Info.
ESN0064
SNMP trap: No
SNMP trap: No
An LDN is required.
Action:
Severity: Info.
ESN0065
Response is out-of-range (1-4).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 901 of 2360

ESN0066
Maximum must equal or exceed the minimum.

Action:
Severity: Info.
ESN0067
SNMP trap: No
Restricted number is too long.

Action:
Severity: Info.
ESN0068
SNMP trap: No
No more restricted numbers allowed for this code.

Action:
Severity: Info.
ESN0069
SNMP trap: No
A HNPA has already been specified.

Action:
Severity: Info.
ESN0070
SNMP trap: No
The CHG command is not allowed.

Action:
Severity: Info.
ESN0071
SNMP trap: No
NPA, NXX, etc., specified, does not exist.

Action:
Severity: Info.
ESN0072
SNMP trap: No
NPA, NXX, etc., specified, already exists.

Action:
Severity: Info.
ESN0073
SNMP trap: No
Conflict with another (NPA, NXX, etc.).

Action: Enter new SPN number.
Severity: Info.
SNMP trap: No
System Messages
Page 902 of 2360

ESN0074
Response is too long.

Action:
Severity: Info.
ESN0075
SNMP trap: No
A DID number must use part of the extension number.

Action:
Severity: Info.
ESN0076
SNMP trap: No
A route list index must be entered.

Action:
Severity: Info.
ESN0077
SNMP trap: No
Error in the network (NARS/BARS) translator.

Action:
Severity: Info.
ESN0078
SNMP trap: No
First digit (or second for 1+ dialing) of NPA/NXX code is invalid.

Action:
Severity: Info.
ESN0079
SNMP trap: No
Response must be 3 or 4 digits in length.

Action:
Severity: Info.
ESN0080
SNMP trap: No
No more available SDR blocks (out or expand MXSD).

Action:
Severity: Info.
ESN0081
SNMP trap: No
X must precede number to be deleted.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 903 of 2360

ESN0082
Second digit (or third for 1+ dialing) of NPA code is invalid.

Action:
Severity: Info.
ESN0083
SNMP trap: No
This number is already restricted for this code.

Action:
Severity: Info.
ESN0084
SNMP trap: No
SUM is valid only when the PRT command is specified.

Action:
Severity: Info.
ESN0085
SNMP trap: No
Number of digits in MIN or MAX should equal the save value.

Action:
Severity: Info.
ESN0086
SNMP trap: No
TODS out-of-range (0 - 31).

Action:
Severity: Info.
ESN0090
SNMP trap: No
Input out-of-range (0-15).

Action:
Severity: Info.
ESN0091
SNMP trap: No
Invalid response (I or A for initial or extended set).

Action:
Severity: Info.
ESN0092
SNMP trap: No
SNMP trap: No
Out-of-range (0-3).
Action:
Severity: Info.
System Messages
Page 904 of 2360

ESN0093
Action:
Severity: Info.
ESN0094
SNMP trap: No
NCTL data block does not exist.

Action:
Severity: Info.
ESN0095
SNMP trap: No
NCTL data block already exists.

Action:
Severity: Info.
ESN0096
SNMP trap: No
SNMP trap: No
Action:
Severity: Info.
ESN0097
SDR information is corrupted.

Action:
Severity: Info.
ESN0098
SNMP trap: No
SDR code does not exist.

Action:
Severity: Info.
ESN0099
SNMP trap: No
Invalid response to MFRL. Allowed input range is 0-7 minutes.

Action:
Severity: Info.
ESN0100
SNMP trap: No
Referenced block does not exist.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 905 of 2360

ESN0101
FCAS index out-of-range; 1-255 with NARS, 1-127 with BARS.

Action:
Severity: Info.
ESN0102
SNMP trap: No
FCAS head table does not exist.

Action:
Severity: Info.
ESN0104
SNMP trap: No
FCAS table/block does not exist.

Action:
Severity: Info.
ESN0105
SNMP trap: No
FCAS table/block already exists.

Action:
Severity: Info.
ESN0106
SNMP trap: No
No more NPA codes allowed.

Action:
Severity: Info.
ESN0107
SNMP trap: No
{CR} is not allowed as the first NPA response for NEW command.
Action:
Severity: Info.
ESN0108
SNMP trap: No
NPA code does not exist.

Action:
Severity: Info.
ESN0109
SNMP trap: No
Not allowed to remove last NPA code in table.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 906 of 2360

ESN0110
Unable to match mnemonics: DENY, ALOW.

Action:
Severity: Info.
ESN0111
SNMP trap: No
First digit of two NXX codes should be equal.

Action:
Severity: Info.
ESN0112
SNMP trap: No
First NXX code should not be larger than second NXX code.
Action:
Severity: Info.
ESN0113
SNMP trap: No
SNMP trap: No
Invalid NXX code.

Action:
Severity: Info.
ESN0114
Not allowed to shrink FCAS head table.

Action:
Severity: Info.
ESN0115
SNMP trap: No
Too few or too many digits entered.

Action: Re-enter only 1 -4 digits per field of SPN.
Severity: Info.
ESN0116
SNMP trap: No
Not allowed to shrink CDP list.

Action:
Severity: Info.
ESN0117
SNMP trap: No
Maximum number of CDP steering codes exceeds limit.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 907 of 2360

ESN0118
Length of CDP DN out-of-range (3-7 digits).

Action:
Severity: Info.
ESN0119
SNMP trap: No
Steering code with a different length exists.

Action: To change NCDP, all the entries of steering codes should be removed
first.
Severity: Info.
ESN0120
SNMP trap: No
Not allowed to turn off CDP for the customer.

Action:
Severity: Info.
ESN0123
SNMP trap: No
The BARS package does not allow AC2.

Action:
Severity: Info.
ESN0124
SNMP trap: No
An undefined package was requested.

Action:
Severity: Info.
ESN0125
SNMP trap: No
Undefined CDP type (LSC, DSC, TSC, ALL).

Action:
Severity: Info.
ESN0126
SNMP trap: No
CDP data block (CDP-LIST) does not exist.

Action:
Severity: Info.
ESN0127
SNMP trap: No
Undefined Route List Index (RLI).

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 908 of 2360

ESN0128
Null input not allowed, a value must be entered.

Action:
Severity: Info.
ESN0129
SNMP trap: No
SNMP trap: No
Invalid input for RLI.

Action:
Severity: Info.
ESN0131
Undefined steering code (CHG command).

Action:
Severity: Info.
ESN0134
SNMP trap: No
Steering code conflicts with access code or directory number.

Action:
Severity: Info.
ESN0135
SNMP trap: No
Steering code out-of-range.

Action:
Severity: Info.
ESN0136
SNMP trap: No
CDP DN length out-of-range.

Action:
Severity: Info.
ESN0137
SNMP trap: No
Number of digits to delete out-of-range (LSC).

Action:
Severity: Info.
ESN0138
SNMP trap: No
Number of steering codes exceeds maximum number of steering codes

(MXSC) defined.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 909 of 2360

ESN0139
Number of digits to strip is out-of-range (LSC).

Action:
Severity: Info.
ESN0140
SNMP trap: No
SCC data table index out-of-range (1-7).

Action:
Severity: Info.
ESN0141
SNMP trap: No
SCC data table does not exist.

Action:
Severity: Info.
ESN0142
SNMP trap: No
SCC data table cannot be shortened.

Action:
Severity: Info.
ESN0143
SNMP trap: No
Invalid input (CC1, CC2, or TIE).

Action:
Severity: Info.
ESN0144
SNMP trap: No
Invalid input (SCC or DIAL).

Action:
Severity: Info.
ESN0145
SNMP trap: No
SCC table entry already exists.

Action:
Severity: Info.
ESN0146
SNMP trap: No
SCC table entry does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 910 of 2360

ESN0147
Even number input only.

Action:
Severity: Info.
ESN0148
SNMP trap: No
SCC and Tone detector packages not equipped.

Action:
Severity: Info.
ESN0149
SNMP trap: No
HNPA code does not support NANP format.

Action:
Severity: Info.
ESN0150
SNMP trap: No
Fourth digit of an NPA code in NANP is invalid.

Action:
Severity: Info.
ESN0151
SNMP trap: No
SDRR digits are too long.

Action: Re-enter correct type of SDRR to configure.
Severity: Info.
ESN0152
SNMP trap: No
Invalid network translation type; for NPA, NXX, and SPN only.
Action:
Severity: Info.
ESN0153
SNMP trap: No
Maximum number of ITGE tables out of range.

Action:
Severity: Info.
ESN0154
SNMP trap: No
Shrinking the ITGE head table is not allowed.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 911 of 2360

ESN0155
ITGE head table does not exist.

Action:
Severity: Info.
ESN0156
SNMP trap: No
ITGE table does not exist.

Action:
Severity: Info.
ESN0157
SNMP trap: No
ITGE table already exists.

Action:
Severity: Info.
ESN0158
SNMP trap: No
SNMP trap: No
ITGE out-of-range.
Action:
Severity: Info.
ESN0159
RTNO not defined for this ITEI.

Action:
Severity: Info.
ESN0160
SNMP trap: No
Empty ITGE table is not allowed.

Action:
Severity: Info.
ESN0161
SNMP trap: No
Cannot delete an undefined office code.

Action:
Severity: Info.
ESN0162
SNMP trap: No
Two fields are required, one for minimum and one for the maximum of a DID
range.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 912 of 2360

ESN0163
Maximum of 20 ranges already defined.

Action:
Severity: Info.
ESN0164
SNMP trap: No
Cannot define new office code without defining DID range.

Action:
Severity: Info.
ESN0165
SNMP trap: No
Cannot define overlapping or duplication of ranges in one location code.

Action:
Severity: Info.
ESN0166
SNMP trap: No
Range to be deleted must be the same as the range defined.

Action:
Severity: Info.
ESN0167
SNMP trap: No
X must be followed by an office code or a DID range.

Action:
Severity: Info.
ESN0168
SNMP trap: No
Number of save digits must be 4 for the Multiple DID feature.

Action:
Severity: Info.
ESN0169
SNMP trap: No
SDR block does not exist.

Action:
Severity: Info.
ESN0170
SNMP trap: No
Cannot delete; does not match with existing ITEI.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 913 of 2360

ESN0171
DID range to be deleted does not belong to the office code.

Action:
Severity: Info.
ESN0172
SNMP trap: No
A range must be defined. SAVE is not equal to 0 and DID is equal to YES.
Action:
Severity: Info.
ESN0174
SNMP trap: No
SDI user count exceeds 128. Use new ITEI.

Action:
Severity: Info.
ESN0175
SNMP trap: No
List number entered is not a System Speed Call List.

Action:
Severity: Info.
ESN0176
SNMP trap: No
System Speed Call List number is out-of-range.

Action:
Severity: Info.
ESN0177
SNMP trap: No
System Speed Call List does not exist.

Action:
Severity: Info.
ESN0178
SNMP trap: No
Mixing ADM/MDM Routes with other route types not allowed.

Action:
Severity: Info.
ESN0179
SNMP trap: No
STRK is applicable to SPN code with ADM/MDM Route list only.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 914 of 2360

ESN0180
ADM/MDM Route list can only be assigned to SPN.

Action:
Severity: Info.
ESN0181
SNMP trap: No
ISA Route is not allowed.

Action:
Severity: Info.
ESN0182
SNMP trap: No
Route type has been changed to ISA.

Action:
Severity: Info.
ESN0188
SNMP trap: No
LD 90 is being used to change HLOC. When changing HLOC for ESN, the
ISDN HLOC in LD 15 might require change also.
Action:
Severity: Info.
ESN0189
SNMP trap: No
Cannot define HNPA unless both AC1 and AC2 are defined in the ESN DB for
this customer.
Action:
Severity: Info.
ESN0200
SNMP trap: No
Network Attendant Service (NAS) package is not equipped.

Action:
Severity: Info.
ESN0201
SNMP trap: No
SNMP trap: No
Warning: NAS active.

Action:
Severity: Info.
ESN0202
Attendant DN block does not exist.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 915 of 2360

ESN0203
NAS schedule block already exists.

Action:
Severity: Info.
ESN0204
SNMP trap: No
NAS schedule block does not exist.

Action:
Severity: Info.
ESN0206
SNMP trap: No
Cannot out RLB which is used by FNP, VNR, RLB.

Action:
Severity: Info.
ESN0207
SNMP trap: No
Input out-of-range (DSC/LOC: 0-10, SPN/TSC: 0-24).

Action: For SPN, re-enter correct FLEN 0-24.
Severity: Info.
ESN0208
SNMP trap: No
FSNS index out-of-range (0 to MXFS).

Action:
Severity: Info.
ESN0209
SNMP trap: No
FSNS head table does not exist.

Action:
Severity: Info.
ESN0210
SNMP trap: No
TBL number out-of-range 0-63.

Action:
Severity: Info.
ESN0211
SNMP trap: No
FSNS table/block does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 916 of 2360

ESN0212
FSNS table/block already exists.

Action:
Severity: Info.
ESN0213
SNMP trap: No
Only 15 SPN are allowed.

Action:
Severity: Info.
ESN0214
SNMP trap: No
{CR} is not allowed as the first SPN response for NEW.

Action:
Severity: Info.
ESN0215
SNMP trap: No
SNMP trap: No
SPN does not exist.

Action:
Severity: Info.
ESN0216
Cannot remove last SPN in FSNS table.

Action:
Severity: Info.
ESN0217
SNMP trap: No
MBGS is not recognized. First parameter is customer number, second

parameter is MBGS number.
Action:
Severity: Info.
ESN0218
SNMP trap: No
First digit of two XXX codes should be equal.

Action:
Severity: Info.
ESN0219
SNMP trap: No
First XXX cannot be larger than the second XXX.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 917 of 2360

ESN0220
Invalid XXX code.

Action:
Severity: Info.
ESN0221
SNMP trap: No
Not allowed to shrink FSNS code.

Action:
Severity: Info.
ESN0224
SNMP trap: No
Package requirements for NAS are missing. The NAS package requires BRTE
(Pkg 14), NCOS (32), and NARS (58).
Action:
Severity: Info.
ESN0225
SNMP trap: No
That password has Print Only Class of Service.

Action:
Severity: Info.
ESN0226
SNMP trap: No
As the user, you do not have access to that data.

Action:
Severity: Info.
ESN0229
SNMP trap: No
That input is out-of-range.

Action:
Severity: Info.
ESN0230
SNMP trap: No
Those D-channels do not exist.

Action:
Severity: Info.
ESN0231
SNMP trap: No
That D-channel does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 918 of 2360

ESN0232
Warning: VNS does not apply anymore. The Virtual Network Service (VNS)
D-channel content is removed.
Action:
Severity: Info.
ESN0233
SNMP trap: No
Warning: The RL1 entry is not used as a VNS route because no Virtual
D-channel was defined.
Action:
Severity: Info.
ESN0234
SNMP trap: No
That VNS D-channel does not belong to that customer.

Action:
Severity: Info.
ESN0235
SNMP trap: No
Input out of range for OVLL( 0-24).

Action: Re-enter correct OVLL digits 0 - 24.
Severity: Info.
ESN0236
SNMP trap: No
Not enough protected memory. Notify operating company.

Action:
Severity: Info.
ESN0237
SNMP trap: No
Setting ERWT = NO will not turn off tone. Must change RLBs, and set EXP =
NO for all entries.
Action:
Severity: Info.
ESN0238
SNMP trap: No
Overlay 90 - For CLTP prompt, input must be either NONE, LOCL, NATL,
SSER, SERH, or INTL.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 919 of 2360

ESN0239
FNP functionality is disabled in LD15.

Action:
Severity: Minor.
ESN0242
SNMP trap: No
Invalid answer to the prompt BNE. BNE valid responses are Yes or No.
Action:
Severity: Info.
ESN0243
SNMP trap: No
Input out of range. Valid length of NPA/NXX is (1 - 7) digits.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 920 of 2360
553-3001-411
Standard 15.00
January 2006
Page 921 of 2360
FHW: Faulty Hardware

Messages
FHW0000 n
Loop n has been detected as faulty by the LRIP function. INI000 8000 has
been averted.
Action: The system administrator should do the following immediately: 1. Load
the appropriate maintenance overlay according to the data base configuration of
loop n: Use LD 32 when loop type is: Terminal loop, Super Loop, Remote Loop
[without RPE2 package 165 equipped], Multipurpose ISDN Signal Processor
Loop; Use LD 34 when loop type is Tone/Digit Sender Loop; Use LD 38 when
loop type is Conference Loop; Use LD 46 when loop type is Multifrequency
Sender Loop; Use LD 53 when loop type is Remote Loop [with RPE2 package
165 equipped]; Use LD 60 when loop type is Digital Loop; Use LD 75 when loop
type is either Integrated Digital Access Loop or Primary Rate Interface Loop 2.
Print the status of loop n to ensure that it is marked "faulty". Skip remaining steps
if loop n is not marked "faulty". 3. Enter the disable command for loop n. 4. Enter
the disable command for all other loops that are on the same hardware pack as
the faulty loop 5. Replace the hardware pack. 6. Enter the enable command for
all the loops that are on the newly installed hardware pack. 7. Print the status of
loop n to ensure that it is no longer marked as faulty. If the system administrator
is unable to perform steps 1 to 3, the FHWR function will disable the faulty loop
as a low priority task.
Severity: Critical.
FHW0001 n
SNMP trap: Yes
SDI device n, which is not defined as an Expanded D-channel, has been

detected as faulty by the SRIP function. INI 8000 has been averted.
the appropriate maintenance overlay according to the data base configuration of
SDI device n: Use LD 37 when SDI device is either a Terminal Port or a Printer
Port on a non-MSDL pack; Use LD 48 when SDI device is an Application Module
Link on a non-MSDL pack; Use LD 96 when SDI device is on an MSDL pack, or
when either a Backup D-channel or a D-channel is on a non-MSDL pack. 2. Print
the status of SDI device n to ensure that it is marked "faulty". Skip remaining steps
if SDI device n is not marked "faulty". 3. Enter the disable command for faulty SDI
device. 4. Enter the disable command for all other SDI devices that are on the
same hardware pack as the faulty SDI device. 5. Replace the hardware pack. 6.
Enter the enable command for all the SDI devices that are on the newly installed
System Messages
Page 922 of 2360

hardware pack. 7. Print the status of SDI device n to ensure that it is no longer
marked as faulty. If the system administrator is unable to perform steps 1 to 3, the
FHWR function will disable the faulty SDI device as a low priority task.
Severity: Critical.
FHW0002 n
SNMP trap: Yes
SDI device n, which is defined as an Expanded D-channel, has been detected

as faulty by the SRIP function. INI 8000 has been averted.
LD 75. 2. Print the status of SDI device n to ensure that it is marked "faulty" and
has been disabled. Skip remaining steps if SDI device n is not marked "faulty" 3.
Enter the disable command for the faulty SDI device.b4. Enter the disable
command for all other SDI devices that are on the same hardware pack as the
faulty SDI device. 5. Replace the hardware pack 6. Enter the enable command
for all the SDI devices that are on the newly installed hardware pack. 7. Print the
status of SDI device n to ensure that it is no longer marked as faulty. If the system
administrator is unable to perform steps 1 to 3, the FHWR function will disable the
faulty Expanded SDI device as a low priority task
Severity: Critical.
FHW0003 n
SNMP trap: Yes
Loop n has been detected as faulty by LOIP function. INI000 0006 has been
averted.
the appropriate maintenance Overlay according to the data base configuration of
[without RPE2 package 165 equipped]; Use LD 53 when loop type is Remote
Loop [with RPE2 package 165 equipped]; Use LD 60 when loop type is Digital
Loop; Use LD 75 when loop type is either an Integrated Digital Access Loop or a
Primary Rate Interface Loop; 2. Print the status of loop n to ensure that it is
marked "faulty". Skip remaining steps if loop n is not marked "faulty". 3. Enter the
disable command for loop n. 4. Enter the disable command for all other loops that
are on the same hardware pack as the faulty loop. 5. Replace the hardware pack.
6. Enter the enable command for all the loops that are on the newly installed
hardware pack. 7. Print the status of loop n to ensure that it is no longer marked
as faulty. If the system administrator is unable to perform steps 1 to 3, the FHWR
function will disable the faulty loop as a low priority task.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 923 of 2360

FHW0004 n
Loop n has been automatically disabled by the FHWR function.

[without RPE2 package (165) equipped], Multipurpose ISDN Signal Processor
Loop; Use LD 34 when loop type is Tone/Digit Sender Loop; Use LD 38 when
loop type is Conference Loop; Use LD 46 when loop type is Multifrequency
Sender Loop; Use LD 53 when loop type is Remote Loop [with RPE2 package
165 equipped]; Use LD 60 when loop type is Digital Loop; Use LD 75 when loop
type is either Integrated Digital Access Loop or Primary Rate Interface Loop. 2.
Enter the status command for loop n to ensure that it is marked "faulty" and has
been disabled. Skip remaining steps if loop n is not marked "faulty". 3. Enter the
disable command for all other loops that are on the same hardware pack as the
faulty loop. 4. Replace the hardware pack. 5. Enter the enable command for all
the loops that are on the newly installed hardware pack. 6. Print the status of loop
n to ensure that it is no longer marked as faulty. If the system administrator is
unable to perform steps 1 to 3, the FHWR function will disable the faulty loop as
a low priority task.
Severity: Critical.
FHW0005 n
SNMP trap: Yes
SDI device n, which is not an Expanded D-channel, has been automatically

disabled by the FHWR function.
SDI device n: Use LD 37 when SDI device is either a Terminal Port or a Printer
Port on a non-MSDL pack; Use LD 96 when SDI device is on an MSDL pack, or
when either a Backup D-channel or a D-channel is on a non-MSDL pack. 2. Enter
the Status command for SDI device n to ensure that it is marked "faulty" and has
been disabled. Skip remaining steps if SDI device n is not marked "faulty". 3.
Enter the disable command for all other SDI devices that are on the same
hardware pack as the faulty SDI device. 4. Replace the hardware pack. 5. Enter
the enable command for all the SDI devices that are on the newly installed
marked as faulty. If the system administrator is unable to perform steps 1 to 3, the
FHWR function will disable the faulty loop as a low priority task.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 924 of 2360

FHW0006 n
SDI device n, which is an expanded D-channel, has been automatically

disabled by the FHWR function.
LD 75. 2. Enter the status command for SDI device n to ensure that it is marked
"faulty" and has been disabled. Skip remaining steps if SDI device n is not marked
"faulty". 3. Enter the disable command for all other SDI devices that are on the
same hardware pack as the faulty SDI device. 4. Replace the hardware pack. 5.
Enter the enable command for all SDI devices that are on the newly installed
marked as faulty.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 925 of 2360
FIJI: Fiber Junctor Interface

Messages
FIJI0001
Application response timeout.

Parameter 1 = Group
Parameter 2 = Side
Action: If printed are enabling FIJI, card was enabled without alarms enabled.
Attempt to re-enable alarms:
ENL ALRM G S <cr>
If failure:
a) ARCV OFF
b) SWRG Y (Y-other side)
If success then:
c) DIS FIJI G S
d) ENL FIJI G S
e) ARCV ON
2. If message is not associated with enabling the FIJI:
a) ARCV OFF
b) SWRG Y (Y-other side)
c) If success, then:
DIS FIJI G S
ENL FIJI G S
d) ARCV ON
Severity: Minor.
FIJI0002
SNMP trap: Yes
Rings operation complete. (Ring audit/Force

disconnect/Auto-recovery/Change to Survival state.
Paramger 1 = Ring
Number
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 926 of 2360

FIJI0003
Rings are in an invalid state. The ring state is changed to 01/01 (both rings
disabled). Ring audit will attempt a recover
Action: ARCV ON
Wait for the ring audit to bring the rings to the right state or use the RSTR
command.
Severity: Critical.
FIJI0004
SNMP trap: Yes
Ring recovery thresholds is exceeded. Ring recovery will be triggered within

30 minutes.
Action: Perform actions for FIJI0005. RSET.
Severity: Critical.
FIJI0005
SNMP trap: Yes
Recover failed on Ring 0/1.

Parameter 1 = Ring Number.
Action: Check for failure reason:
1. STAT RING S
Make sure all FIJIs are up.
2. STAT ALRM S
Make sure no LOP, LOS, LOF, BER, or TXIP alarms are on and that the NEWK
and NEWZ values are correct.
(See FIJI0010-0016 messages)
3. After all alarms are cleared:
a) RSET - Wait for ring audit to bring the rings to the proper state, or
b) RSTR
Severity: Critical.
FIJI0006
SNMP trap: Yes
Recovery on both rings failed.

Action: Perform actions for FIJI0005 for both rings.
Severity: Critical.
FIJI0007
553-3001-411
Ring state has changed.

FIJI0007 NEW STATE RING 0: pl RING 1:p2
p1 = ring 0 state, p2 - ring 1 state.
States:
Standard 15.00
January 2006
SNMP trap: Yes
Page 927 of 2360

Half (DRIVES HALF or normal state)
None (Disable - DRIVES NONE)
Full (DRIVES FULL)
Action:
Severity: Critical.
FIJI0008
SNMP trap: Yes
One or more cards in the active ring are not enabled or cannot receive from all
other cards.
Parameter 1 - Ring Number
Action: Same actions as FIJI0003.
Severity: Critical.
FIJI0010
SNMP trap: Yes
FIJI0010 p1 p2 ALARM p3 RECVS_FROM data RECVS_FROM data has

changed.
Parameter 1 = Group
Parameter 2 = Side
Parameter 3 = alarm number = 0
data = RECVS_FROM data
Action: Bits in RECVS_FROM word represent 8 groups. A "0" indicates this FIJI
is unable to receive from that group. Take action only if data indicate a problem.
(Bit missing for equipped group).
RECVS_FROM alarm is almost always the result of another alarm that is turning
on or off, thus RECVS_FROM is an indication of the problem and not the problem
itself. Note that some RECVS_FROM alarms are good, especially if it shows an
improvement in group communication. Check cable connections. (STAT RING X
or STAT FIJI X Y FULL).
Severity: Critical.
FIJI0011
SNMP trap: Yes
FIJI0011 p1 p2 ALARM p3 p4 LOP

Loss of Pointer
p1=Group, p2= Side, p3=ON/OFF, p4= Alarm# = 1
Action: If LOP is seen when a card is first enabled then it is not a problem unless
the alarm stays on. Otherwise, disable cards on the ring one at a time, upstream
from the card (i.e. follow the receive path from the card with the alarm). Each time
a card is disabled, wait for 15 seconds and then stat alrm for the ring. If the alarm
turned off, replace the card just disabled. Continue disabling cards upstream until
the card with the alarm is the only one enabled. Replace the remaining FIJI card.
Note 1: LOP will definitely cause one-way speech path and/or noise in voice
System Messages
Page 928 of 2360

channel, and may cause PLL_LOL_78M and PLL_LOL_32M other FIJI cards in
the ring.
Note 2: When this alarm is present, the 360 and link tests may fail.
Severity: Info.
FIJI0012
SNMP trap: Yes
FIJI0012 p1 p2 ALARM p3 p4 LOS. Loss of Signal to the adjacent FIJI due to

FIJI or cable failure.
Loss of Signal
Action: 1. Check Rx fiber connection on FIJI.
2. Try replacing the Rx fiber cables.
3. Try replacing the FIJI card.
Note: When this alarm is present, the 360 and link tests may fail.
Severity: Critical.
FIJI0013
SNMP trap: Yes
FIJI0013 p1 p2 ALARM p3 p4 LOF

Loss of Frame
Action: If LOF is seen when a card is first enabled then it is not a problem unless
the alarm stays on. Otherwise, disable cards on the ring one at a time, upstream
from the card (i.e. follow the receive path from the card with the alarm). Each time
a card is disabled, wait for 15 seconds and then stat alrm for the ring. If the alarm
has turned off, replace the card just disabled. Continue disabling cards upstream
until the card with the alarm is the only one enabled. Replace the remaining FIJI
card.
Note 1: LOF usually causes PLL_LOL_78M and PLL_LOL_32M on other cards
in the ring.
Note 2: When this alarm is present, the 360 and link tests may fail.
Severity: Critical.
FIJI0014
SNMP trap: Yes
FIJI0014 p1 p2 ALARM p3 RX_CONN_TO data

RX_CONN_TO data has changed.
Parameter 1 = Group
Parameter 2 = Side
Parameter 3 = alarm number
data = RX_CONN_TO data
Action: RX_CONN_TO data is the group number of the FIJI which transmits to
the reporting FIJI.
Examples for a system with groups 0, 1, and 3 equipped:
RING 0 - ascending order
553-3001-411
Standard 15.00
January 2006
Page 929 of 2360

FIJI014 0 0 ALARM RX_CONN_TO 3
FIJI014 1 1 3
FIJI014 3 0 1
Make sure upstream FIJI is enabled and not being brought up by the system.
Check cable connections.
Severity: Critical.
FIJI0015
SNMP trap: Yes
FIJI0015 p1 p2 ALARM p3 p4 BER

Bit Error Rate
Action: Disable the card that transmits to it. If the alarm clears then replace the
transmitting card, otherwise replace the card reporting the alarm.
Severity: Critical.
FIJI0016
SNMP trap: Yes
FIJI0016 p1 p2 ALARM p3 p4 TX_PARE

Transmit Parity
Action: Replace card.
Severity: Critical.
FIJI0017
SNMP trap: Yes
FIJI0017 p1 p2 ALARM p3 p4 PLL_LOL_32M

Loss of Lock on 32M Clock PLL
Action: This is a transitional alarm that often happens when enabling or
disabling a FIJI card and is frequently the result of other alarms such as LOP or
LOF. If LOP or LOF alarm exists anywhere on the ring then see FIJI0011 or
FIJI0013.
In ld 39, enl ralm 0 or 1 for the card on the ring that has the problem. If the alarm
disappears then no futher action is required.
If the alarm continues to turn on and off with no presence of LOP or LOF on the
ring, then try replacing the card. If the problem persists, then it could be the
symptom of another problem (e.g. clocking).
Severity: Minor.
SNMP trap: Yes
System Messages
Page 930 of 2360

FIJI0018
FIJI0018 p1 p2 ALARM p3 p4 LOL_BIT_78M.

Loss of Lock on 78M clock PLL.
Action: See FIJI0017.
Severity: Minor.
FIJI0019
SNMP trap: Yes
FIJI0019 p1 p2 ALARM p3 p4
PLL_TV_32M data
32M clock PLL Voltage out of range
data word = TVA data
Severity: Minor.
FIJI0020
SNMP trap: Yes
PLL_TV_78M data
78M clock PLL Voltage out of range
data word = TVA data
Severity: Minor.
FIJI0022
SNMP trap: Yes
FIJI0022 p1 p2 ALARM p3 p4 FP_CLK

Face Plate Reference Clock.
Action: This alarm can only be seen on group zero. Check both sides for
FP_CLK. 1)
If only one card reports the alarm then check the faceplate connections (J3 and
J4) to ensure they are secure and running to the correct clock controller. Next, try
replacing the clock-to-FIJI cable. Lastly, try replacing the FIJI card.
If both sides report the alarm, check that each clock controller is enabled and that
all faceplate connections on both FIJIs are secure. Check that the clock-to-clock
cable is secure.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 931 of 2360

FIJI0023
FIJI0023 p1 p2 ALARM p3 p4 RECOV_CLK.

Recovered clock.
Action: If the alarm is accompanied by LOS then check that the Rx fiber cable
is securely connected. Otherwise, try replacing the Rx fiber cable.
If the alarm is not accompanied by LOS, replace the FIJI card.
Severity: Minor.
FIJI0024
SNMP trap: Yes
FIJI0024 p1 p2 ALARM p3 p4 BP_CLK.

Back Plane Clock.
Action: In ld 39, stat alrm for each ring.
The required action depends on which cards have the alarm:
1. If both FIJI cards in a group have the alarm:
a. Check that both PS cards in the group are enabled and responding.
b. Switch clocks. If the alarm turns off on the side that previously carried the
active clock then suspect the FIJI on the active clock side.
c. If the alarm follows the active clock then either both PS or both FIJI cards are
suspect.
2. If one FIJI card in a group has the alarm:
a. Check that both PS cards in the group are enabled and responding.
b. Switch clocks. If the alarm follows the active clock (i.e. turns on only for the
side that carries the active clock), check the ABCDE cable (shelf-to-shelf cable).
c. If the alarm stays on for that card regardless of which side the clock is switched
to, then the PS card or FIJI card is suspect. If the cards in that shelf still respond
then the PS card is good and the FIJI card is suspect. Check the backplane
behind the FIJI card for bent pins, otherwise replace the card.
3. For multiple groups or group zero, ensure the clock-to-FIJI cables are routed
correctly and connected to the correct faceplate ports before using steps 1 and 2
on each group.
Severity: Minor.
FIJI0025
SNMP trap: Yes
FIJI_PWR_5V data.
LM80_BIT_5V data.
5V power supply.
data = LM80 data
Action: Replace card. If the problem persists, check the shelf power supply.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 932 of 2360

FIJI0026
FIJI_PWR_33V data.
3.3 Volt power supply.
data = LM80 data
Severity: Minor.
FIJI0027
SNMP trap: Yes
FIJI_PWR_25V data.
2.5V power supply.
data = LM80 data
Severity: Minor.
FIJI0028
SNMP trap: Yes
FIJI_OV_TEMP data.
Over Temperature. (over 45C).
Upgrade, p2= Side, p3=ON/OFF, p4= Alarm# = 39
data word = LM80 data
Action: Check that fan on bottom of column is functioning properly. Replace card
and see if the alarm comes back.
Severity: Minor.
FIJI0029
SNMP trap: Yes
FIJI0029 p1 p2 ALARM p3 DRP_SPC_PARE.

Parity Error threshold reached.
Action: Disable the FIJI card that transmits to it. If the alarm turns off then
replace the transmitting card, otherwise, replace this card.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 933 of 2360

FIJI0030
OHP_DRP_PARE.
Receive Parity error.
Severity: Info.
FIJI0031
SNMP trap: Yes
DRP_ADD_PARE.
Pass thru Parity error.
Severity: Minor.
FIJI0034
SNMP trap: Yes
Bad application Response

Parameter 1 = Group
Parameter 2 = side
Action: Attempt to reenable FIJI
DIS FIJI G S
ENL FIJI G S
Severity: Critical.
FIJI0035
SNMP trap: Yes
FIJI card is not present on shelf.

Parameter 1 = Group
Parameter 2 = Side
Action: Check FIJI connection to backplane.
Severity: Critical.
FIJI0036
SNMP trap: Yes
Data corruption.
Parameter 1 = Group
Parameter 2 = Side
Severity: Critical.
SNMP trap: Yes
System Messages
Page 934 of 2360

FIJI0037
Insufficient resources to perform command.

Action:
Severity: Major.
FIJI0038
SNMP trap: Yes
Command ignored. Another task is still processing.

Action: Retry later.
Severity: Info.
FIJI0039
SNMP trap: Yes
Illegal Command (Software Bug)

Severity: Minor.
FIJI0040
SNMP trap: Yes
SNMP trap: Yes
FIJI is already enabled.

Parameter 1 = Group
Parameter 2 = Side
Action:
Severity: Info.
FIJI0041
FIJI card selftest failed.

Parameter 1 = Group
Parameter 2 = Side
Action: Swap FIJI pack with spare.
Severity: Major.
FIJI0042
SNMP trap: Yes
Unable to send BASECODE/APPL enable/disable message.

Parameter 1 = Group
Parameter 2 = Side
Action: Retry later.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 935 of 2360

FIJI0043
Card failed to perform the requested ENABLE/DISABLE command.

FIJI state changed to MAN DIS.
Parameter 1 = Group
Parameter 2 = Side
Action: Retry ENL FIJI G S. If ENL fails, check/swap FIJI pack.
Severity: Major.
FIJI0044
SNMP trap: Yes
Message timeout for Disable/Enable commands.

FIJI state change to MAN DIS.
Parameter 1 = Group
Parameter 2 = Side
Action: Retry ENL FIJI G S
If ENL fails, check/swap FIJI pack.
Severity: Major.
FIJI0045
SNMP trap: Yes
Enabling/Disabling process aborted.

Time limit exceeded.
FIJI state changed to MAN DIS.
Parameter 1 = Group
Parameter 2 = Side
Action: Retry ENL FIJI G S
If ENL fails, check/swap FIJI pack.
Severity: Major.
FIJI0046
SNMP trap: Yes
Failure on Enable FIJI BASECODE/SONET

APPL. Will retry in 0.5 seconds.
Parameter 1 = Group
Parameter 2 = Side
Action: Contact your technical services group.
Severity: Info.
FIJI0047
SNMP trap: Yes
The BASECODE/SONET APPL has been enabled/disabled.

Parameter 1 = Group
Parameter 2 = side
Severity: Info.
SNMP trap: Yes
System Messages
Page 936 of 2360

FIJI0048
FIJI0048 p1 p2 ALARM p3 p4 TX_CLK

Action: Replace this card. May be accompanied by LOP on the card it transmits
to.
Severity: Info.
FIJI0050
SNMP trap: Yes
FIJI0050 p1 p2 ALARM p3 p4 ADD_78M_FAIL

Severity: Info.
FIJI0051
SNMP trap: Yes
FIJI0051 p1 p2 ALARM p3 p4 DRP_78M_FAIL

Severity: Info.
FIJI0052
SNMP trap: Yes
FIJI0052 p1 p2 ALARM p3 p4 FRM_SHIFT

Action: Disable and enable the card. If the alarm does not clear replace the card.
Severity: Info.
FIJI0053
SNMP trap: Yes
SNMP trap: Yes
Download Failure.
Parameter 1 = Group
Parameter 2 = Side
Action: Retry
Severity: Major.
FIJI0054
Unknown Clock
Severity: Critical.
FIJI0055
SNMP trap: Yes
SNMP trap: Yes
Clock is switched.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 937 of 2360

FIJI0056
Download threshold for this has reached. Audit will make no further attempts
to download to the FIJI pack.
FIJI0056 p1 p2
p1 = Group
p2 = Side
Action: 1. ARCV OFF
2. If the ring is in DRIVES FULL or DRIVES HALF sate use SWRG Y.
3. If failure use RSTR command.
4. DIS EFIJI G S
5. ENL FIJI G S <FDL>
6. ARCV ON
If FIJI0038 is printed, wait for download to complete to all FIJI packs.
Severity: Major.
FIJI0057
SNMP trap: Yes
Cannot download all FIJIs in ring.

FIJI0057 p1
P1 = ring
p1 = 0: Ring 0
p1 = 1: Ring 0
p1 = 2: Both rings
Action: 1. Switch to other ring
a) ARCV OFF
b) SWRG Y - switch to other side.
2. Switch clock
a) SCLK
3) Disable/enable
a) DIS RING X
b) ENL RING X
c) ARCV ON
Severity: Major.
FIJI0058
SNMP trap: Yes
Clock switch fail.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 938 of 2360

FIJI0059
Auto-recovery for the Fiber Network is turned off.

Action: This is a reminder message. While auto recovery is turned off, the
system will not automatically restore the rings to the optimum state. It is
recommended that auto recovery be turned on during normal operation of the
fiber network.
Severity: Info.
FIJI0060
SNMP trap: Yes
The clock needs to be switched.

Action:
Severity: Critical.
FIJI0061
SNMP trap: Yes
RING r :Starting automatic download of FIJI.

FIJI0061 RING p1 (p1 = rng)
where:
r = ring (0 or 1)
Action:
Severity: Info.
FIJI0062
SNMP trap: Yes
FIJI g s :Enabling FIJI card.

FIJI0062 FIJI p1 p2
g = group (0-7)
s = side (0 or 1)
Action:
Severity: Info.
FIJI0063
SNMP trap: Yes
FIJI g s: Download complete. Testing FIJI card.

FIJI0063 FIJI p1 p2
g group (0-7)
s = side (0 or 1)
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 939 of 2360

FIJI0064
FIJI g s FIJI Selftest complete.

FIJI0064 FIJI p1 p2
g = group (0-7
p2 = side (0 or 1)
Action:
Severity: Info.
SNMP trap: Yes
FIJI0065 p1 p2 ALARM p3 p4 CBL_BIT. FIJI to FIJI cable missing on group p1.

p1 = Group
p2 = Side
p3 = ON/OFF,
p4 = Alarm# = 17
Action: Avoid switching clocks until FIJI to FIJI cable is connected.
Severity: Major.
FIJI0067
SNMP trap: Yes
p1 p2 ALARM
p3 p4 RX_CTRL
Loss of RX control signal
p1=Group
p2= Side
p3=ON/OFF
p4= Alarm# = 18
Action: Replace card as soon as possible.
Severity: Critical.
FIJI0068
SNMP trap: Yes
LOP alarm previously detected on FIJI x y and its history has been recorded.
Action: Due to the intermittent nature of LOP, the alarm may or
may not still be on. Stat alrm x y full to see if the
Alarm is still on. If it is then see FIJI011. If it is not then disable the ring and replace
the card that transmits to the card reporting LOP history. Enable the ring; the act
of doing so will clear the LOP history.
Stat alrm to see if LOP still exists. If the alarm still shows up on the same card
then disable the ring and replace that card. Enable the ring.
Severity: Major.
SNMP trap: Yes
System Messages
Page 940 of 2360

FIJI0069
The ring should be disabled before faceplate disabling the card.

Action: Dis ring X before faceplate disabling a card. Note: X denotes ring
number
Severity: Info.
FIJI0070
SNMP trap: No
FIJI0070 FIJI p1 p2 p3 Faulty card detected by I3 and IL tests p1=Group,

p2=side, p3=suspected area of failure.
Action: This card has a problem. Replace card as soon as possible.
P3 indicates the suspected area of failure:
1 - DRP-to-ADD path
2 - SPACE FPGA
Severity: Major.
FIJI0071
SNMP trap: Yes
FIJI0071 FIJI p1 p2
Faulty card detected by I3 and IL tests
p1=Group, p2 = side
Action: This card is likely okay however a retest (test all) is recommended after
replacing the card downstream that is reporting a SPACE FPGA failure. This will
ensure that the DRP-to-ADD path works.
Severity: Major.
FIJI0072
SNMP trap: Yes
FIJI0072 FIJI p1 p2
p1=Group, p2 = side
Action: This card or one of the adjacent cards reporting an error condition has a
problem.
Severity: Major.
FIJI0073
SNMP trap: Yes
FIJI0073 FIJI p1 p2
p1=Group, p2 = side
Action: Incomplete test results. This card is likely okay, however a retest (test
all) is recommended so that all test results may be completed and a correct
analysis given.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 941 of 2360

FIJI0074
FIJI0074 FIJI p1 p2 p3
p1=Group, p2=side, p3=suspected area of failure
Action: Incomplete test results. This card or one of the adjacent cards certainly
has a problem. A retest (test all) is recommended so that all test results may be
completed and a more accurate diagnosis made. P3 indicates the suspected area
of failure had all the test results been complete:
1 - DRP-to-ADD path
2 - SPACE FPGA
3 - This card is likely okay however a retest is recommended after replacing the
card downstream that is reporting a SPACE FPGA failure.
Severity: Major.
FIJI0075
SNMP trap: Yes
FIJI0075 FIJI p1 p2
Backplane test results not received from this group.
p1=Group, p2 = side
Action: Test results were not received for the Fiji cards on this group. Backplane
test should be performed on both.
Severity: Major.
FIJI0076
SNMP trap: Yes
FIJI0076 FIJI p1 p2
Backplane test detected failure.
p1=Group, p2=Side
Action: All loops failed on this group and side. Test results were not received for
the Fiji card on the other side. A backplane test is recommended for the other side
before solid conclusions can be drawn.
1) If the other side's test results completely fail then see FIJI078.
2) If the other side's results all pass then see FIJI079.
3) If some loops fail on the other side then it may indicate that both this Fiji card
and the loops that the other side reported are bad. Replace this Fiji card first the
retest. If both sides now agree on which loops are bad then check those loops.
Severity: Major.
FIJI0077
SNMP trap: Yes
p1=Group, p2=Side,p3=loop (range 0-31)
Action: Some loops failed on this group and side. Test results were not received
for the Fiji card on the other side. A backplane test is recommended for the other
side before solid conclusions can be drawn.
System Messages
Page 942 of 2360

1) If the other side's test results completely fail then replace the FIJI card on the
other side.
2) If the other side's results match that of this side then see FIJI0080.
3) If the other side passes all loops then see FIJI0079.
4) If the other side's result show failures on different loops, then see FIJI0081.
Severity: Major.
FIJI0078
SNMP trap: Yes
FIJI0078 GROUP p1
p1 = Group
Action: All loops on both sides of this group failed. Check both PS cards. If they
seem okay then replace each Fiji card individually. Otherwise, check the
backplane cables.
Severity: Major.
FIJI0079
SNMP trap: Yes
p1 = Group, p2 = Side, p3 = loop
Action: Only this side shows backplane failures on those loops. Replace the Fiji
card first and retest. If the same loops fail then check those loops. Otherwise,
check the Fiji card's backplane connections.
Severity: Major.
FIJI0080
SNMP trap: Yes
p1=Group, p2=Side, p3 = loop
Action: Both sides of this group show failures on those loops. If all loops from 0
to 15 fail then check the PS card on side 0. If all loops from 16 to 32 fail then check
the PS card on side 1. Otherwise, check the loops in error. If the loops do not
seem to be bad then replace each Fiji card individually. If this fails, then check the
backplane connections.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 943 of 2360

FIJI0081
p1=Group, p2=Side, p3 = loop
Action: Both sides of this group show unique loop errors. Replace both Fiji cards
and retest. If the same loops fail then check those loops. Otherwise check each
Fiji card's backplane connections.
Severity: Major.
FIJI0082
SNMP trap: Yes
FIJI p1 p2 p3 360 test detected failure p1=Group, p2=Side, p3 = loop (0-31, or

ALL)
Action: If every card in the ring fails the same link or ALL links then disable the
Fiji card in group 0 first and perform the 360 test on another card in the ring. If the
same failure occurs then repeat this for every card downstream until the card is
found that causes the failure. If individual cards have failures then replace those
cards and perform the 360 test.
Severity: Major.
FIJI0100 x
SNMP trap: Yes
The CSTAT and CSUBSTAT fields on FIJI x indicate the card is Manually
Disabled. The Meridian 1 believes the card is Enabled. The card is placed in
the System Disabled-Self-tests Passed state, and within the next few minutes,
the Meridian 1 will attempt to enable the card. (x=Group*2+Side)
Action: Wait
Severity: Critical.
FIJI0101x
SNMP trap: No
The CSTAT field on FIJI x indicates the card is no longer Enabled. The
Meridian 1 will attempt to return the card to an Enabled state within a few
minutes. Under certain conditions, this message is output at the same time as
FIJI302. (x=Goup*2+Side)
Action: Wait
Severity: Critical.
FIJI0102 x
SNMP trap: No
No response was received from FIJI x to a background polling message sent

periodically to each FIJI card. The purpose of this message is to ensure that
the card is capable of receiving and sending messages. (x=Group*2-Side)
Action: Info only
Severity: Critical.
SNMP trap: No
System Messages
Page 944 of 2360

FIJI0103x
An overlay was waiting for a message from FIJI x. Most likely, the Overlay is
no longer loaded. The message the overlay was waiting for was never
received. (x=Group*2+Side)
Action: Info only
Severity: Critical.
FIJI0104 x
SNMP trap: No
The FIJI background audit sent a message to FIJI x and did not receive a
response. (x = Group*2+side)
Action:
Severity: Info.
FIJI0105 x bbb
SNMP trap: No
x=Group*2+side
bbb=CSTAT data
The CSTAT value read from the FIJI is invalid. This indicated one of two error
conditions:
1. The card has encountered a severe hardware fault so that it is unable to
report the error to the Meridian.
2. There may be multiple cards in the system with switch settings which mark
is as the FIJI. When the CSTAT is read from the FIJI, it may not be the FIJI
card that is responding.
Action: Be sure no other cards in the system share the device number. If so,
change the device numbers. If not, replace the card.
Severity: Critical.
FIJI0106 x FIJI
SNMP trap: No
The FIJI audit detected tat there was no response to a maintenance message
originated by the FIJI application on FIJIx.
X=FIJI number=Group*2+side
Action: Info only
Severity: Critical.
FIJI0107 x FIJI y
SNMP trap: No
The Meridian 1 was unable to determine if downloading was necessary. An

SDL error message should accompany this message and describe the reason
for the failure. Three fields accompany this message:x=FIJI number
(Group*2+side), y is for design use only
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 945 of 2360

FIJI0108 x FIJI
The FIJI application on FIJI x needs to be downloaded to the card.

Downloading begins as soon as there is no Overlay loaded. Where: x =Fiji
number (group*2+side),
Action: Info only
Severity: Critical.
FIJI0112 x
SNMP trap: No
FIJI x has been reset in order to begin automatic recovery. Immediately

following this message, the card is executing self tests. When they are
finished, provided they pass, the Meridian 1 will attempt to enable the card.
Where x=FIJI number (Group*2+side).
Action: Info only
Severity: Critical.
FIJI0201 x FIJI
SNMP trap: No
FIJI x sent a message to the Meridian 1 indicating an application data space

has been corrupted. Were: x=FIJI number (group*2+side).
Severity: Critical.
FIJI0204 x FIJI
SNMP trap: No
The Meridian 1 searched the system disk to find a version of an application for
FIJI x and found none.
Where:x=FIJI number (group *2+side)
Severity: Critical.
SNMP trap: No
FIJI0205 x FIJI y z An error was encountered when searching the system disk to find a version of
an application for FIJI x. Refer to an accompanying SDL error message for the
exact error reason. This message indicates that the Meridian 1 will attempt to
enable the application in question if a version exists on the card.
Shere: x =FIJI number (Group*2+side). (y and z are for design use only.
Severity: Critical.
SNMP trap: No
System Messages
Page 946 of 2360

FIJI0206 x FIJI yz
An error was encountered when comparing a version of an application on the

system disk with the version on FIJIx
Where:x=FIJI number(Group*2+side). (y and z are for design use only)
Action: Refer to the accompanying SDL error message for the exact error
reason. This message indicates that the Meridian 1 will attempt to enable the
application if a version exists on the card
Severity: Critical.
FIJI0207 x FIJI yz
SNMP trap: No
An error was encountered when downloading the application to FIJI x

Where: FIJI number (Group*2+side). (y and z are for design only)
reason. The entire sequence has been aborted.
Severity: Critical.
FIJI0208 x
SNMP trap: No
When preparing to download the base software to FIJI x, the card indicated
that some kind of fatal error was encountered. Where: x=FIJI number
(Group*2+side).
Action: Execute self tests before attempting any other action regarding this card.
Severity: Critical.
FIJI0209 xyz
SNMP trap: No
Some memory was reclaimed within the FIJI for future use. The application on
FIJI x requested that a buffer pool be freed. When this occurred, there was at
least one outstanding buffer. The basecode waited for the buffer(s) to be
returned. The buffer pool was forcibly freed by the basecode.
Where:x=FIJI number(Group*2+side)
Action: Info only
Severity: Critical.
FIJI0210
SNMP trap: No
Failed to enable the FIJI for one of the following reasons:

The card in question is not a FIJI card. For example, there may be a card in
the system with switch settings that correspond to the FIJI , but is in fact not a
FIJI card.
There is at least one other card in the system with switch settings identical to
the FIJIs.
Action: Remove the card with the same device number as the FIJI.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 947 of 2360

FIJI0299
FIJI x sent a message to the Meridian 1 indicating an application data space

has been corrupted.
Where:x=FIJI number (Group*2+side).
Severity: Info.
FIJI0300
SNMP trap: No
The FIJI background audit has changed the state of the card. In the case
where the card was previously enabled and now is no longer enabled, another
FIJI message will indicate the reason for the state change. When making a
state transition due to a fatal error on the card, the reason for the fatal error is
displayed in this message
Output data: FIJI300 x y FROM: aaaa TO bbbb
TIME time REASON ccccc
Where:
x=Group
y=Side
aaaa=The status of the FIJI prior to the state change
bbbb= the state of the card after the state change
time= the time of the state change
cccc=reason for the error (only when TO: SYS DSBL-FATAL ERROR)
Action: This is an informational message and requires no action by the
craftsperson
Severity: Info.
FIJI0301 x y z
SNMP trap: No
An expedited data unit (XDU) was received. The Meridian 1 is not expecting
FIJI x to generate any messages in its current state. However, immediately
following a state transition to a disabled state, a pending message may cause
this message to be displayed.
Where: x= FIJI number (group*2+side).
Action: There is no specific action to be taken; however, the message indicates
that the incoming message from the card was not processed due to the state
change.
Severity: Critical.
SNMP trap: No
System Messages
Page 948 of 2360

FIJI0302 x y
Access to the memory space shared by the Meridian 1 and the FIJI (shared
Ram) has been momentarily suspended by FIJI x. There is no specific action
to be taken as a result of this message; however, it indicates that message
transfer between the Mederian 1 and the card ceased momentarily.
Where: x is FIJI number (Group*2+side) and y the reason for the suspension
Action: Currently the only reason supported is the value 1, indicating that some
kind of buffer corruption was detected.
Severity: Critical.
FIJI0303 x y
SNMP trap: No
The Meridian 1 detected corruption in either the receive ring or the transmit
ring or both, causing access to the memory space shared by the Meridian 1
CPU and FIJI x (shared RAM) to be momentarily suspended
Action: Take no action because of this message; however it indicates that
message transfer between meridian 1 and the card ceased momentarily.
Severity: Critical.
FIJI0304 x y20
SNMP trap: No
The Meridian 1 received 100 or more messages from the FIJI x within two
seconds
Where:
x=FIJI number (Group*2+side)
y=the rate of message transfer from the card to the meridian 1 in terms of
messages per second.
Action: At this level of message transfer, there may be some impact to the
overall system performance. The level of service does not warrant removing the
card from service
Severity: Major.
FIJI0305 x y
SNMP trap: No
The Meridian 1 received 200 or more messages from FIJI x within two seconds
t this level of message transfer there may be some impact to the overall
system performance. The level of message transfer does not warrant
removing the card from service.
X=FIJI number (Group*2+side)
y= the rate of message transfer from the card to the Meridian 1 in terms of
messages per second
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 949 of 2360

FIJI0306 x y
The Meridian 1 has received 300 or more messages from FIJI x within two
seconds. Card put into Lockout for overload protection
x=FIJI number (Group*2+side)
y= the rate of message transfer from the card to the meridian 1 in terms of
Action: Disable and then enable the card.
Severity: Info.
FIJI0307 x data
SNMP trap: No
FIJI x encountered a fatal error.

X=FIJI number (Group*2+side)
The data following x is information read from the card regarding the error and
is intended for design use only
Action: Contact technical support group
Severity: Critical.
SNMP trap: No
FIJI0308 x y FIJI data FIJI x reported that it received a message with an invalid (bad) socket+ID
x=3D FIJI number (Group*2+side)
y=3D the socket ID
data= up to eight words of hex data representing the message sent
Severity: Critical.
SNMP trap: No
FIJI0451 <cardAddress><CardIndex><invalidCardstate> An invalid card state change request

from the SL1 task has been detected by the MMIH dxriver.
Action: If the problem does not clear automatically, disable and then enable the
card.
Severity: Minor.
SNMP trap: No
FIJI0452<cardAdddress><cardIndex> The MMIH driver failed to send an SSD message to the

SL1 task
Action: Check the traffic reports for excessive traffic on the core CPU or check
for a system problem.
Severity: Minor.
SNMP trap: No
System Messages
Page 950 of 2360

FIJI0453<cardAddress><cardIndex> The MMIH driver failed to send and RFC message to the
SL1task.
for a system problem.
Severity: Minor.
SNMP trap: No
FIJI0454<CardAddress><CardIndex> The MMIH driver failed to place a transmit expedited

message in the expedited interface.
Action: Disable and then enable the FIJI/MSDL/MISP card.
Severity: Minor.
SNMP trap: No
FIJI0467 <cardAddress><cardIndex> The SRAM suspend message cannot be sent to the card
through the expedited interface in response to two or more no mbuffer
conditions being detected in a timespan grater than 100msec.
Action: Information only. If the problem persists disable then enable the card, or
replace the card
Severity: Minor.
SNMP trap: No
FIJI0468 <cardAddress> <cardIndex> <rtclock> <returnCode> <socketIDapplication> <'First

8 words of the msg'> The application message cannot be sent to the ring and
the reason code is other then no buffer. SocketID is the socket for the
message to be sent application ID identifies the transmitting application. The
first 8 words of the message are displaced in hex return code contains the
actual value returned by the procedure and contains on of the following values:
0- request failed
1-request succeeded
4-flow control
5- no buffer
6-socket ID is suspended
7-ring is not operational
8-invalid socketIDS
Action: Information only. If the problem persists disable and then enable the
card.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 951 of 2360

FIJI0470<cardAddress><cardIndex><rtclock> A no buffer condition occurred because the card
has not yet sent an initialization acknowledgement response.
Action: Check whether the traffic flow is excessive. If the problem persists,
disable and then enable the card.
Severity: Info.
SNMP trap: No
FIJI0471<cardAddress><cardIndex><rtclock messageSiZe A no buffer condition occurred

because a single buffer message is larger than the size of a single buffer.
Action: Contact your technical support group. The buffers data could be
corrupted.
Severity: Major.
SNMP trap: No
FIJI0472<cardAddress><cardIndex><rtclock messageSize> Insufficient buffers available in

the transmit ring for the message.
Action: Check whether the traffic flow is excessive. If the problem persists
Severity: Info.
SNMP trap: No
System Messages
Page 952 of 2360
553-3001-411
Standard 15.00
January 2006
Page 953 of 2360
FIR: Fibre Remote IPE

Messages
FIR0001 NET s1
Watchdog reset occurred at FNET.

Severity: Major.
FIR0002 NET sl
SNMP trap: No
Power-on reset occurred at FNET.

Action:
Severity: Info.
FIR0003 NET sl
SNMP trap: No
SNMP trap: No
PLL lock lost on FNET.

Action:
Severity: Info.
FIR0004 NET sl ln PLL lock regained on FNET.

Action:
Severity: Info.
SNMP trap: No
FIR0005 NET sl ln Signal Degrade declared on FNET. Switched to other link.

Action: Use the Fault Clearance Procedure to find which hardware
element is faulty.
Severity: Info.
SNMP trap: No
FIR0006 NET sl ln Signal Degrade declared on FNET, and PS not possible. No new data calls.
element is faulty.
Severity: Info.
SNMP trap: No
System Messages
Page 954 of 2360

FIR0007 NET sl ln Signal Degrade cleared on FNET.
Action:
Severity: Info.
SNMP trap: No
FIR0008 NET sl ln Signal Fail declared on FNET. Switched to other link.

element is faulty.
Severity: Info.
SNMP trap: No
FIR0009 NET sl ln Signal Fail declared by FNET, and PS not possible.

element is faulty.
Severity: Info.
SNMP trap: No
FIR0010 NET sl ln Signal Fail cleared on FNET.

Action:
Severity: Info.
SNMP trap: No
FIR0011 NET sl ln th Threshold Crossing Alert on FNET. "th" indicates threshold.

element is faulty.
Severity: Info.
FIR0012 NET sl
SNMP trap: No
Protection Switching threshold has been crossed on FNET.

Action: Use the Fault clearance Procedure to find which hardware
element is faulty.
Severity: Info.
SNMP trap: No
FIR0013 NET sl ln Packlet inserted on FNET.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 955 of 2360

FIR0014 NET sl ln Packlet removed on FNET.
Action:
Severity: Info.
SNMP trap: No
FIR0015 NET sl ln Switched to other link on FNET.

Action:
Severity: Info.
FIR0016 NET sl
SNMP trap: No
No new data calls declared.

element is faulty.
Severity: Info.
FIR0017 NET sl
SNMP trap: No
No new data calls cleared.

Action:
Severity: Info.
FIR0101 PEC pc
SNMP trap: No
Watchdog reset occurred at FPEC.

Action:
Severity: Info.
FIR0102 NET s1
SNMP trap: No
Power-on reset occurred at FNET.

Action: Information only. If this message appears repeatedly or is associated
with a system problem, contact your technical support group.
Severity: Info.
FIR0103 PEC pc
SNMP trap: No
SNMP trap: No
PLL lock lost on FPEC.

Action:
Severity: Info.
FIR0104 PEC pc ln PLL lock regained on FPEC.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 956 of 2360

FIR0105 PEC pc ln Signal degrade declared on FPEC. Switched to other link.
Action:
Severity: Info.
SNMP trap: No
FIR0106 PEC pc ln Signal degrade declared by FPEC, and PS not possible. No new data calls.
element is faulty.
Severity: Info.
SNMP trap: No
FIR0107 PEC pc ln Signal Degrade cleared on FPEC.

Action:
Severity: Info.
SNMP trap: No
FIR0108 PEC pc ln Signal Fail declared on FPEC. Switched to other link.

element is faulty.
Severity: Info.
SNMP trap: No
FIR0109 PEC pc ln Signal Fail declared by FPEC, and PS not possible.

element is faulty.
Severity: Info.
SNMP trap: No
FIR0110 PEC pc ln Signal Fail cleared on FPEC.

Action:
Severity: Info.
SNMP trap: No
FIR0111 PEC pc ln th Threshold Crossing Alert on FPEC. "th" indicates threshold.

element is faulty.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 957 of 2360

FIR0112 PEC pc
Protection Switching threshold has been crossed on FPEC.

element is faulty.
Severity: Info.
SNMP trap: No
FIR0113 PEC pc ln Packlet inserted on FPEC.

Action:
Severity: Info.
SNMP trap: No
FIR0114 PEC pc ln Packlet removed on FPEC.

Action:
Severity: Info.
SNMP trap: No
FIR0115 PEC pc ln Switched to other link on FNET.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 958 of 2360
553-3001-411
Standard 15.00
January 2006
Page 959 of 2360
FMEM: Flash Memory

Messages
FMEM0001
Bad memory address

Action:
Severity: Info.
FMEM0002
SNMP trap: No
Can't erase flash memory chip - Replace ROM

Action:
Severity: Info.
FMEM0003
SNMP trap: No
Can't erase write 00 - Try again/Replace ROM

Action:
Severity: Info.
FMEM0004
SNMP trap: No
Bus error - possibly card not exist

Action:
Severity: Info.
FMEM0005
SNMP trap: No
Invalid command - Consult Tech. Support

Action:
Severity: Info.
FMEM0007
SNMP trap: No
Can't program flash memory

Action:
Severity: Info.
FMEM0008
SNMP trap: No
SNMP trap: No
Bad file open to write

Action:
Severity: Info.
System Messages
Page 960 of 2360

FMEM0009
Bad file write

Action:
Severity: Info.
FMEM0010
SNMP trap: No
SNMP trap: No
SNMP trap: No
Bad file open to read

Action:
Severity: Info.
FMEM0011
Bad file read

Action:
Severity: Info.
FMEM0012
Failed memory allocation for File Buffer

Action:
Severity: Info.
FMEM0013
SNMP trap: No
Failed memory allocation for Chip Buffer

Action:
Severity: Info.
FMEM0014
SNMP trap: No
Buffer partition error - Should be 0, 1 or 2

Action:
Severity: Info.
FMEM0016
SNMP trap: No
Source slot can't be same as target slot

Action:
Severity: Info.
FMEM0017
SNMP trap: No
Failed loading a.out file - Check source file

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 961 of 2360

FMEM0018
Source card name not matched target card name

Action:
Severity: Info.
FMEM0019
SNMP trap: No
BIC window open error - Check subject card

Action:
Severity: Info.
FMEM0020
SNMP trap: No
BIC window enable error - Check subject card

Action:
Severity: Info.
FMEM0021
SNMP trap: No
BIC probe error - Check for card existence

Action:
Severity: Info.
FMEM0022
SNMP trap: No
Failed loading S-Rec file - Check source file

Action:
Severity: Info.
FMEM0023
SNMP trap: No
Invalid Internal Checksum - Check source file

Action:
Severity: Info.
FMEM0024
SNMP trap: No
Invalid Internal Checksum - Check data record

Action:
Severity: Info.
FMEM0025
SNMP trap: No
SNMP trap: No
External access failed

Action:
Severity: Info.
System Messages
Page 962 of 2360

FMEM0026
Relative address error

Action:
Severity: Info.
FMEM0027
SNMP trap: No
Bad slot number - Should be in range (0-31)

Action:
Severity: Info.
FMEM0028
SNMP trap: No
Flash memory write error

Action:
Severity: Info.
FMEM0029
SNMP trap: No
Can't disable BIC window - Check subject card

Action:
Severity: Info.
FMEM0030
SNMP trap: No
SNMP trap: No
Can't get BIC window

Action:
Severity: Info.
FMEM0031
Can't get BIC IPB timer - Check subject card

Action:
Severity: Info.
FMEM0032
SNMP trap: No
Can't set BIC IPB timer - Check subject card

Action:
Severity: Info.
FMEM0033
SNMP trap: No
Can't get BIC local timer - Check subject card

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 963 of 2360

FMEM0034
Can't set BIC local timer - Check subject card

Action:
Severity: Info.
FMEM0037
SNMP trap: No
Bad chip option - should be 0, 1 or 2

Action:
Severity: Info.
FMEM0038
SNMP trap: No
Bad release number, range 0-255

Action:
Severity: Info.
FMEM0039
SNMP trap: No
Bad issue number, range 0-255

Action:
Severity: Info.
FMEM0040
SNMP trap: No
Relative address out of range

Action:
Severity: Info.
FMEM0041
SNMP trap: No
Input buffer size out of range

Action:
Severity: Info.
FMEM0042
SNMP trap: No
SNMP trap: No
Not a valid input

Action:
Severity: Info.
FMEM0043
Text segment size is equal to 0! Not loaded!

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 964 of 2360

FMEM0044
Invalid Internal Checksum - Check PEROM content

Action:
Severity: Info.
FMEM0045
SNMP trap: No
SNMP trap: No
SNMP trap: No
S5 record not matched!

Action:
Severity: Info.
FMEM0046
Unknown S record!!!
Action:
Severity: Info.
FMEM0047
Slot number out of range (0-31)

Action:
Severity: Info.
FMEM0048
SNMP trap: No
Can't spawn external watchdog punch task

Action:
Severity: Info.
FMEM0049
SNMP trap: No
Card name input error - Should be CP or IOP

Action:
Severity: Info.
FMEM0050
SNMP trap: No
Input expected a number

Action:
Severity: Info.
FMEM0051
SNMP trap: No
String input error - 80 columns maximum

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 965 of 2360

FMEM0052
Chip sizes mismatched between two chips

Action:
Severity: Info.
FMEM0053
SNMP trap: No
Chip code unsupported - Consult Tech. Support

Action:
Severity: Info.
FMEM0054
SNMP trap: No
Can't read card Id register

Action:
Severity: Info.
FMEM0055
SNMP trap: No
Bad card id register or Not yet programmed

Action:
Severity: Info.
FMEM0056
SNMP trap: No
Can't find card name in card Id

Action:
Severity: Info.
FMEM0057
SNMP trap: No
Card name CP mismatched with Card Id IOP

Action:
Severity: Info.
FMEM0058
SNMP trap: No
Card name IOP mismatched with Card Id CP

Action:
Severity: Info.
FMEM0059
SNMP trap: No
PEROM content DESTROYED!!!

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 966 of 2360

FMEM0060
PEROM content CHANGED!

Action:
Severity: Info.
FMEM0061
SNMP trap: No
PEROM content INTACT

Action:
Severity: Info.
FMEM0062
SNMP trap: No
SNMP trap: No
No default command
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 967 of 2360
HTM: Hyper-text markup language

Messages
HTM0000
Incorrect input.
Display SCH code which comes from CS.
Action:
Severity: Info.
HTM0001
SNMP trap: No
Are you sure you want to delete current Trunk Member from the Call Server?
Action:
Severity: Info.
HTM0002
SNMP trap: No
Are you sure you want to delete current Route from the Call Server?
Action:
Severity: Info.
HTM0003
SNMP trap: No
The following mandatory field must be filled.

Action:
Severity: Info.
HTM0004
SNMP trap: No
Invalid new configuration for DLOP.

Action:
Severity: Info.
HTM0005
SNMP trap: No
Are you sure you want to delete current Customer from the Call Server?
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 968 of 2360

HTM0006
Are you sure you want to delete current Flexible Code Restriction
configuration from the Call Server?
Action:
Severity: Info.
HTM0007
SNMP trap: No
Are you sure you want to delete current Incoming Digit Conversion
configuration from the Call Server?
Action:
Severity: Info.
HTM0008
SNMP trap: No
Warning: Invalid Call Server information that may cause configuration failure.
Action:
Severity: Info.
HTM0010
SNMP trap: No
You cannot display the page without correct login name.

Click on OK to load the required information without the LOGNAME.
Action:
Severity: Info.
HTM0011
SNMP trap: No
You cannot display the page without correct List Trunk Member or Package
information from the Web Server.
Click on OK to load the required information without correct XML file (s).
Action:
Severity: Info.
HTM0012
SNMP trap: No
You have already removed the element.

The sub-element of current position has already been removed.
Action:
Severity: Info.
HTM0013
SNMP trap: No
You cannot display the page without correct information.

Click on OK to load listed customer information without displaying List Trunk
Member page (cust_xp.html).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 969 of 2360

HTM0014
Error: You cannot display the page without correct Route or Description
Click on OK to load the required information without route info from the CS or
route description info from the WS.
Action:
Severity: Info.
HTM0015
SNMP trap: No
Error: The file system does not have the correct package information.
This feature package can not be displayed without the package description
info on the WS.
Action:
Severity: Info.
HTM0016
SNMP trap: No
Error: Invalid value input.

Click on Help for more information.
Action:
Severity: Info.
HTM0017
SNMP trap: No
Error: Input value out of range.

Click on Help for more information.
Action:
Severity: Info.
HTM0018
SNMP trap: No
Error: You cannot display the page without correct description information
from the Web Server.
Click on OK to load the required information without correct description info on
the WS.
Action:
Severity: Info.
HTM0019
SNMP trap: No
Error: You cannot display the page without correct prompt information.
Click on OK to load the required information without correct XML file/s.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 970 of 2360

HTM0020
Error: You cannot compare two DOMs with different node order.
Action:
Severity: Info.
HTM0021
SNMP trap: No
Updating common equipment data successfully.

Click on OK to reload common equipment information.
Action:
Severity: Info.
HTM0022
SNMP trap: No
Error: This number is already exists.

Click on OK to re-enter valid number.
Action:
Severity: Info.
HTM0023
SNMP trap: No
Error: You cannot display the page without correct List Customer or Package
Click on OK to load the required information without correct XML file(s).
Action:
Severity: Info.
HTM0024
SNMP trap: No
Error: You cannot display the page without correct Code Restriction Tree
Number information from the Web Server.
Click on OK to load the required information without correct CRNO info.
Action:
Severity: Info.
HTM0025
SNMP trap: No
Error: You cannot display the page without correct description file for Code
Restriction Tree Number from the Web Server.
Click on OK to load the required information without correct description file for
CRNO info.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 971 of 2360

HTM0026
Error: Cannot display the page without correct Customer information from the
Web Server.
Click on OK to load the required information without correct list customer file.
Action:
Severity: Info.
HTM0027
SNMP trap: No
Error: Cannot display the page without correct Code Restriction Tree Number
information for current customer.
Click on OK to load the required information without correct FCR_OBJ from
previous page.
Action:
Severity: Info.
HTM0028
SNMP trap: No
A value must be entered in the first field before entering a value in the second
field.
Please see Help for more information.
Action:
Severity: Info.
HTM0029
SNMP trap: No
Error: Current Call Server doesn't have a required Package. Flexible Code
Restriction cannot be configured.
Action:
Severity: Info.
HTM0030
SNMP trap: No
Updating flexible code restriction configuration data successfully.

Click on OK to reload flexible code restriction data.
Action:
Severity: Info.
HTM0031
SNMP trap: No
Updating incoming digit conversion configuration data successfully.

Click on OK to reload incoming digit conversion data.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 972 of 2360

HTM0032
Cannot display page without correct Digit Conversion Tree Number

information for current customer.
Click on OK to load the required information.
Action:
Severity: Info.
HTM0033
SNMP trap: No
Cannot display page without correct Digit Conversion Tree Number

information from Web Server.
Action:
Severity: Info.
HTM0034
SNMP trap: No
Cannot display the page without correct description file for Digit Conversion
Tree Number from Web Server.
Action:
Severity: Info.
HTM0035
SNMP trap: No
Current Call Server does not have required Package. Incoming Digit
Conversion cannot be configured.
Action:
Severity: Info.
HTM0036
SNMP trap: No
The input value is not a numeric value.

Click on OK to re-enter.
Action:
Severity: Info.
HTM0037
SNMP trap: No
Cannot display required diagnostic information since required information on

the Web Server is either incorrect or does not exist.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 973 of 2360

HTM0038
Cannot submit request without input value for STAT command.

Action:
Severity: Info.
HTM0039
SNMP trap: No
No customer configured in the system.

To add a new customer, click on OK.
Action:
Severity: Info.
HTM0040
SNMP trap: No
Invalid arguments to create button value.

Passing argument length is not same.
Action:
Severity: Info.
HTM0041
SNMP trap: No
Invalid object ID. The object value cannot be created.

Action:
Severity: Info.
HTM0042
SNMP trap: No
Problem with loading Language String XML file.

Action:
Severity: Info.
HTM0043
SNMP trap: No
Key tag missing in the Language String XML file.

Action:
Severity: Info.
HTM0044
SNMP trap: No
New Flexible Code Restriction must be enabled.

Maximum Number of NFCR Translation Tables must be entered.
To configure the correct information, click on OK.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 974 of 2360

HTM0045
Incoming DID Digit Conversion allowed must be enabled.

Maximum number of IDC Conversion Tables must be entered.
To configure the correct information, click on OK.
Action:
Severity: Info.
HTM0046
SNMP trap: No
No D-Channel configured in the system.

To add a new D-Channel, click on OK.
Action:
Severity: Info.
HTM0047
SNMP trap: No
Are you sure you want to delete current D-Channel from the Call Server?
Action:
Severity: Info.
HTM0048
SNMP trap: No
Warning: No Customer Number information from the Call Server.

Action:
Severity: Info.
HTM0049
SNMP trap: No
Warning: No Package information from the Call Server.

Action:
Severity: Info.
HTM0050
SNMP trap: No
Warning: Invalid Call Server information (Version).

Action:
Severity: Info.
HTM0051
SNMP trap: No
Warning: Invalid Call Server information with CRNO may cause configuration
failure.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 975 of 2360

HTM0052
Warning: Invalid Call Server information with INIT may cause configuration
failure.
Action:
Severity: Info.
HTM0053
SNMP trap: No
Warning: Invalid Call Server information with ALOW may cause configuration
failure.
Action:
Severity: Info.
HTM0054
SNMP trap: No
Warning: Invalid Call Server information with DCNO may cause configuration
failure.
Action:
Severity: Info.
HTM0055
SNMP trap: No
Warning: Invalid Call Server information with DLOP GROUP may cause
configuration failure.
Action:
Severity: Info.
HTM0056
SNMP trap: No
Invalid Customer information from Call Server.

Action:
Severity: Info.
HTM0057
SNMP trap: No
Invalid Route information from Call Server.

Action:
Severity: Info.
HTM0058
SNMP trap: No
Invalid Trunk member information from Call Server.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 976 of 2360

HTM0059

Action:
Severity: Info.
HTM0060
SNMP trap: No

Action:
Severity: Info.
HTM0061
SNMP trap: No
Unexpected validation error may cause configuration failure.

Action:
Severity: Info.
HTM0062
SNMP trap: No
Cannot display page without correct Trunk Member or Description information

Action:
Severity: Info.
HTM0063
SNMP trap: No
Cannot display page without correct Customer or Description information from

the Web Server.
Action:
Severity: Info.
HTM0064
SNMP trap: No
Cannot display page without Common Equipment or Description information

Action:
Severity: Info.
HTM0065
SNMP trap: No
Invalid D-Channel information from Call Server.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 977 of 2360

HTM0066
Web Server cannot provide Help information for current page.

Action:
Severity: Info.
HTM1000
SNMP trap: No
Browser cannot handle XML file.

Action:
Severity: Info.
HTM1001
SNMP trap: No
Problem with loading an XML file.

Action:
Severity: Info.
HTM1002
SNMP trap: No
Key tag missing in the XML file.

Action:
Severity: Info.
HTM1003
SNMP trap: No
An interactive element is missing on the HTML page.

Action:
Severity: Info.
HTM1008
SNMP trap: No
The level 2 password is not correct.

Action:
Severity: Info.
HTM1009
SNMP trap: No
The confirm password does not match the new password.

Action:
Severity: Info.
HTM1010
SNMP trap: No
The password cannot be empty.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 978 of 2360

HTM1011
Does not match required format.

Action:
Severity: Info.
HTM1012
SNMP trap: No
Is less than lower boundary.

Action:
Severity: Info.
HTM1013
SNMP trap: No
Is greater than upper boundary.

Action:
Severity: Info.
HTM1014
SNMP trap: No
Do you want to perform deleting?

Action:
Severity: Info.
HTM1015
SNMP trap: No
The CGI string is too long.

Action:
Severity: Info.
HTM1016
SNMP trap: No
The link to this page was not registered.

Action:
Severity: Info.
HTM1017
SNMP trap: No
The page URI contains ".htm".

Action:
Severity: Info.
HTM1018
SNMP trap: No
No path ID defined in the HTML file.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 979 of 2360

HTM1019
No page title ID defined in the HTML file.

Action:
Severity: Info.
HTM1020
SNMP trap: No
No value in the zone number field.

Action:
Severity: Info.
HTM1030
SNMP trap: No
Warning: No Primary Rate 2 Loop Configured.

Action:
Severity: Info.
HTM1031
SNMP trap: No
Warning: No Digital Rate 2 Loop Configured.

Action:
Severity: Info.
HTM2001
SNMP trap: No
Are you Sure to Delete Current D-Channel from Call Server?

Action:
Severity: Info.
HTM2002
SNMP trap: No
Are you Sure to Delete Current D-Channel from Call Server?

Action:
Severity: Info.
HTM3000
SNMP trap: No
bootp.tab and config.ini's DESCRIPTION files are missing.

Action:
Severity: Info.
HTM3001
SNMP trap: No
bootp.tab and config.ini's Data are missing. Data-XML files are missing.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 980 of 2360

HTM3002
Codec table is missing. Codec-XML is missing.

bootp.tab and config.ini's Data are missing. Data-XML files are missing.
Action:
Severity: Info.
HTM3005
SNMP trap: No
No Card or Signaling Server has been configured.

Action:
Severity: Info.
HTM3006
SNMP trap: No
Selecting more than one codec in the same codec group is not allowed.
Action:
Severity: Info.
HTM3008
SNMP trap: No
Invalid Codec. (Codec Information may be missing.)

Action:
Severity: Info.
HTM4000
SNMP trap: No
Error reading product.xml file in /webxml/user directory.

Action:
Severity: Info.
HTM4001
SNMP trap: No
Error reading syscfg.xml file in /webxml/user directory.

Action:
Severity: Info.
HTM4002
SNMP trap: No
Error reading users.xml file in /webxml/user directory.

Action:
Severity: Info.
HTM4003
SNMP trap: No
Error reading sysdesc.xml file in /fs/des directory.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 981 of 2360

HTM5001
XML-Node Summary file is missing.

Action:
Severity: Info.
HTM5002
SNMP trap: No
SNMP trap: No
Missing Bootp XML file.

Action:
Severity: Info.
HTM5003
There are no nodes configured.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 982 of 2360
553-3001-411
Standard 15.00
January 2006
Page 983 of 2360
HWI: Hardware Infrastructure

Maintenance
These messages indicate errors within the hardware infrastructure. These
maintenance messages relate to:
Control Processor (CP) or Changeover and Memory Block (CMB)
Switch Over (SWO)
Network Control Bus (NCB)
Connectors (CON)
The message output format is: Fields x, y, z
Where: x = side, y = card and z = port
Messages
HWI0001 x
HI Init: Cold start begins on side x.

Action:
Severity: Critical.
HWI0002 x
SNMP trap: No
HI Init: Warm start begins on side x.

Action:
Severity: Critical.
HWI0003 x
SNMP trap: No
HI Init: Graceful switchover start continues on side x.

Action:
Severity: Minor.
HWI0004 x y
SNMP trap: No
HI Init: Phase x (y) begins.

Action:
Severity: Info.
HWI0005 x y
SNMP trap: No
HI Init: Cold start complete on side x, in y seconds.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 984 of 2360

HWI0006 x y
HI Init: Warm start complete on side x, in y seconds.

Action:
Severity: Minor.
HWI0007 x y
SNMP trap: No
HI Init: Switchover start complete on side x, in y seconds.

Action:
Severity: Minor.
HWI0008 x
SNMP trap: No
HI FS: Created data directory x.

Action:
Severity: Minor.
HWI0009 x
SNMP trap: No
HI FS: Saving data to directory x.

Action:
Severity: Minor.
HWI0010 x
SNMP trap: No
HI Init: Forced switchover start begin on side x.

Action:
Severity: Critical.
HWI0013 x
SNMP trap: No
NCB x y: Unmasking x interrupt.

Action:
Severity: Critical.
HWI0065
SNMP trap: Yes
SUTL: can not MASK int x: PLX chip not configured.

Action: Remove the SUTL Main card, wait for the HWI102 "disconnect" msg,
then reinsert the card. After reinsertion is detected, SUTL H/W should be
accessible.
Severity: Major.
HWI0101 x
SNMP trap: Yes
CON x y: Connected to x.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 985 of 2360

HWI0102 x
CON x y: Disconnected from x.

Action:
Severity: Minor.
HWI0103
SNMP trap: Yes
CON x y: Connected device is unknown.

Action:
Severity: Minor.
HWI0104
SNMP trap: No
CON x y: Disconnected device is unknown.

Action:
Severity: Minor.
HWI0105
SNMP trap: Yes
CON x y: Connect event. Identification starts.

Action:
Severity: Minor.
HWI0106 x
SNMP trap: No
CON x y: Connect event. Creating x.

Action:
Severity: Minor.
HWI0107 x y
SNMP trap: No
CON x y: State transition from x to y.

Action:
Severity: Minor.
HWI0108 x
SNMP trap: No
SNMP trap: No
CON x y: Created x.
Action:
Severity: Minor.
HWI0109 x
CON x y: Simulating Disconnect-Connect for x.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 986 of 2360

HWI0110 x
CON x y: x deleted.
Action:
Severity: Minor.
HWI0111 x
SNMP trap: No
CON x y: Connect event. Notifying x.

Action:
Severity: Minor.
HWI0112 x
SNMP trap: No
CON x y: Disconnect event. Notifying x.

Action:
Severity: Minor.
HWI0113 x
SNMP trap: No
CON x y: Specification of new device x.

Action:
Severity: Minor.
HWI0114 x y z
SNMP trap: No
CON x y: x destroyed. Affected objects: y z.

Action:
Severity: Minor.
HWI0115 x
SNMP trap: No
SNMP trap: No
CON x y: x destroyed.
Action:
Severity: Minor.
HWI0116 x
CON x y: Successful probe of x.

Action:
Severity: Critical.
HWI0117 x
SNMP trap: No
CON x y: Failed to probe x.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 987 of 2360

HWI0201 x
NCB x y: Enabling 3PE to support x.

Action:
Severity: Minor.
HWI0202 x
SNMP trap: No
NCB x y: Failed to enable 3PE on group x.

Action: Check that 3PE has correct switch settings. Check both connector ends
on the CNI to 3PE. Be sure the 3PE Enable/Disable switch is Enabled (up).
Severity: Critical.
HWI0203 y
SNMP trap: Yes
NCB x y: Disabling 3PE on group y.

Action:
Severity: Minor.
HWI0204 x
SNMP trap: No
NCB x y: Failed to disable 3PE on group x.

Action: Check that 3PE has correct switch settings. Check both connector ends
on the CNI to 3PE. Be sure the 3PE Enable/Disable switch is Enabled (up).
Severity: Minor.
HWI0205
SNMP trap: Yes
NCB x y: OOS testing 3PE.

Action:
Severity: Minor.
HWI0206 x
SNMP trap: No
NCB x y: No response from 3PE on group x.

Action: Check that the CPU Norm/Maint switch is in Maint (down). Check both
connector ends of the CNI to 3PE cable. Be sure the 3PE Enable/Disable switch
is Enabled (up), and the 3PE switch settings are correct.
Severity: Minor.
HWI0207
SNMP trap: Yes
NCB x y: Unable to control 3PE state.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 988 of 2360

HWI0208
NCB x y: Failed OOS test.

Action:
Severity: Critical.
HWI0209
SNMP trap: No
NCB x y: Cannot read 3PE state.

Action:
Severity: Critical.
HWI0210 x y
SNMP trap: No
NCB x y: Failed to service interrupt x. Number of ISR serviced: n.

Action:
Severity: Minor.
HWI0211 x y
SNMP trap: No
Resuming service of interrupt x. Number of ISR service failures: n.

Action:
Severity: Minor.
HWI0212 x y
SNMP trap: No
NCB = masking interrupt.

Action: Refer to STAT CNI in LD135 for recovery actions.
Severity: Minor.
HWI0214
SNMP trap: Yes
NCB x y: Unmasking all interrupts.

Action:
Severity: Minor.
HWI0215 x y
SNMP trap: No
NCB x y: Failed to unmask x, line d interrupt.

Action:
Severity: Minor.
HWI0216 x
SNMP trap: No
NCB x y: I/O interrupts from group x disabled.

Action: Remove all unconfigured I/O cards from the group. Reseat or replace
the packs. Reseat or replace the corresponding CNI board.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 989 of 2360

HWI0217 x y
NCB x y: x interrupts from group y disabled.

Action: Reseat or replace card(s) for the group, and corresponding CNI card.
Severity: Critical.
SNMP trap: Yes
HWI0218 x y z, a b c NCB x y: CNI to 3PE connection mismatch. Expected: x to 3PE y z .

Detected: a to 3PE b c .
Action: Check connection and 3PE DIP switch setting.
Severity: Critical.
HWI0219 y z
SNMP trap: Yes
NCB x y: masking interrupt "y" failed to detect source of this interrupt z times.
Action:
Severity: Critical.
HWI0306 x y
SNMP trap: Yes
SIMM x y: memory fault will impact real time capacity.

Action: The faulty CP card may need to be replaced.
Severity: Critical.
HWI0320 x
SNMP trap: Yes
SIMM x y: From side x this SIMM appears without base address.

Action:
Severity: Critical.
HWI0321 x
SNMP trap: No
SIMM x y: From side x this SIMM appears without size attributes.

Action:
Severity: Critical.
HWI0322 n
SNMP trap: No
SIMM x y: From side x this SIMM appears with unknown size: n.

Action:
Severity: Critical.
HWI0323 y z
SNMP trap: No
SIMM x: Total DRAM on side 0 : y Megabytes side 1: z megabytes. Memory

mismatch may affect switch over decision.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 990 of 2360

HWI0324 x y z
SIMM x: Total equipped DRAM on CP x : y Megabytes . Specified amount of

DRAM: z.
Action: Check SIMMs on CP side x.
Severity: Critical.
HWI0325 n x
SNMP trap: Yes
SIMM x: SIMMs on Core side n: x x x x x x . Where: x = SIMM size

Action:
Severity: Minor.
HWI0326 x
SNMP trap: Yes
SIMM x: The SIMMs on Core side x are not accessible.

Action: Check the connector ends of the CP to CP cable.
Severity: Critical.
HWI0401
SNMP trap: Yes
SWO%d: Switchover denied. System is in maintenance mode.

Action: Ensure both CP Maint/Norm switches are in Norm mode (up).
Severity: Critical.
HWI0402
SNMP trap: No
SWO x: Switchover denied. Redundancy not available.

Action: Check both connector ends of the CP to CP cable.
Severity: Critical.
HWI0403
SNMP trap: No
SWO x: Switchover attempt unsuccessful.

Action:
Severity: Critical.
HWI0404
SNMP trap: No
SWO x: Switchover denied. Other side deemed not better.

Action:
Severity: Critical.
HWI0405
SNMP trap: No
SWO x: Switchover denied. Critical resource is locked.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 991 of 2360

HWI0406
SWO x: Failure occurred attempting to suspend SL-1 task.

Action:
Severity: Critical.
HWI0407
SNMP trap: No
SWO x: Failure occurred attempting to resume SL-1 task.

Action:
Severity: Critical.
HWI0408
SNMP trap: No
SWO x: Attempted to switchover when memory not synchronized.

Action:
Severity: Critical.
HWI0409 x y
SNMP trap: No
SWO x: Switch back to side x failed. Will un-suspend SL-1 on side y.

Action:
Severity: Critical.
HWI0412
SNMP trap: No
SWO %s: Switchover requested, other side deemed better. (%d will be
replaced with Core Shelf number).
Action: No action to be taken by craftsperson.
Severity: Minor.
HWI0500
SNMP trap: Yes
CP: Remote ready deasserted.

Action:
Severity: Critical.
HWI0502
SNMP trap: No
CP: Remote power bit deasserted.

Action:
Severity: Critical.
HWI0504
SNMP trap: No
SNMP trap: No
CP: Cable time out.

Action:
Severity: Critical.
System Messages
Page 992 of 2360

HWI0505
CP: Primary parameter error.

Action:
Severity: Critical.
HWI0506
SNMP trap: No
CP: Secondary parameter error.

Action:
Severity: Critical.
HWI0507
SNMP trap: No
CP: Write without unlock.

Action:
Severity: Critical.
HWI0525
SNMP trap: No
SNMP trap: No
CP: Spurious interrupt.

Action:
Severity: Critical.
HWI0526
CP: RSC = 0 x%08x (Task level)

Action:
Severity: Critical.
HWI0528
SNMP trap: No
CP: Standby CP asserts READY. Begin Shadowing.

Action:
Severity: Minor.
HWI0529
SNMP trap: No
CP: Primary CP cannot access secondary CP.

Action: Check the cable.
Severity: Critical.
HWI0530
SNMP trap: No
CP: System split by Maint/Norm switches.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 993 of 2360

HWI0532
CP: Memory synchronization failed.

Action:
Severity: Critical.
HWI0534 x
SNMP trap: No
CP: Memory synchronization begun. CP x is master.

Action:
Severity: Minor.
HWI0536
SNMP trap: No
CMB 0: Flash ROM mismatch -- staying in Single mode. Both sides must have
the same release installed.
Action:
Severity: Minor.
HWI0601
SNMP trap: Yes
SUTL: Main Card just went *In Service*, no OOS reasons exist; interrupts
should be UNMASKED
Action:
Severity: Info.
HWI0602
SNMP trap: Yes
SUTL interrupts are also UNMASKED

Action:
Severity: Info.
HWI0603
SNMP trap: Yes
OOS reason cleared automatically by HI Fault Monitoring

Action:
Severity: Info.
HWI0604
SNMP trap: Yes

Action:
Severity: Info.
HWI0605
SNMP trap: Yes

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 994 of 2360

HWI0606

Action:
Severity: Info.
HWI0607
SNMP trap: Yes

Action:
Severity: Info.
HWI0608
SNMP trap: Yes
SUTL Main card is now configured for that slot.

Action:
Severity: Info.
HWI0609
SNMP trap: Yes
SUTL H/W should now be accessible

Action:
Severity: Info.
HWI0610
SNMP trap: Yes
SUTL:IN_TEST_MODE OOS reason cleared

Action:
Severity: Info.
HWI0611
SNMP trap: Yes
SUTL Faceplate Switch has been Flipped UP

Action:
Severity: Info.
HWI0612
SNMP trap: Yes
SUTL Card ID PROM has been read successfully

Action:
Severity: Info.
HWI0613
SNMP trap: Yes
SUTL: BAD_HW_REGISTER OOS reason cleared

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 995 of 2360

HWI0614
SUTL:NO_PCI_INT_REGISTERED OOS reason cleared.

Action:
Severity: Info.
HWI0615
SNMP trap: Yes
SUTL: can not clear OOS reasons; NO_PCI_INT_REGISTERED

Action: If condition persists, remove the SUTL Main Card wait for the HWI102
"disconnect" msg, then reinsert the card. After the reinsertion is detected, SUTL
H/W should be accessible and the PCI interrupt should be registered.
Severity: Major.
HWI0616
SNMP trap: Yes
SUTL: could not start sutlFpBackGrnd task

Action:
Severity: Info.
HWI0617
SNMP trap: Yes
SUTL: Main Card just went *Out-Of-Service*

Action:
Severity: Info.
HWI0618
SNMP trap: Yes
SUTL interrupts are MASKED out

Action:
Severity: Info.
HWI0619
SNMP trap: Yes
SUTL went OOS since there were too many switch changes in a given period.
If the switch is not faulty, the OOS reason will be cleared automatically by HI
Fault Monitoring
Action:
Severity: Info.
HWI0620
SNMP trap: Yes
SUTL went OOS since there were too many switch changes in a given period.
If the switch is not faulty, the OOS reason will be cleared automatically by HI
Fault Monitoring.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 996 of 2360

HWI0621
OOS reason set automatically by HI Fault Monitoring.

Action:
Severity: Info.
HWI0622
SNMP trap: Yes
OOS reason set automatically by HI Fault Monitoring

Action:
Severity: Info.
HWI0623
SNMP trap: Yes

Action:
Severity: Info.
HWI0624
SNMP trap: Yes
SUTL Main card is now configured for that slot

Action:
Severity: Info.
HWI0625
SNMP trap: Yes
SUTL: IN_TEST_HW_ACCESS OOS reason set

Action: If condition persists, remove the SUTL lMain card, wait for the HWI102
"disconnect"msg, then reinsert the card. After the reinsertion is detected, SUTL
H/W should be accessible.
Severity: Info.
HWI0626
SNMP trap: Yes
SUTL: IN_TEST_MODE OOS reason set

Action:
Severity: Info.
HWI0627
SNMP trap: Yes
SUTL:FP_SWITCH_DOWN OOS reason set

Action:
Severity: Info.
HWI0628
SNMP trap: Yes
SULT: CAN'T_READ_CARDID OOS reason set

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 997 of 2360

HWI0629
SUTL: BAD_HW_REGISTER OOS reason set

Action:
Severity: Info.
HWI0630
SNMP trap: Yes
SUTL H/W is not accessible.

then reinsert the card. After the reinsertion is detected, SUTL should be
accessible.
Severity: Major.
HWI0631
SNMP trap: Yes
SUTL: can not decode interrupt: PLX chip not configured

then reinsert the card. After the reinsertion is detected, SUTL H/W should be
accessible.
Severity: Major.
HWI0632
SNMP trap: Yes
SUTL: can not get proDataPtr; can not call ISR: obJID=x
Action:
Severity: Info.
HWI0633
SNMP trap: Yes
Driver level code experienced a problem:

0=OK, 1=PRAM_BAD, 2=REGISTER_BAD, 3=BOARD_MISSING
Action:
Severity: Info.
HWI0634
SNMP trap: Yes
Driver lecel code experienced a problem:

Action:
Severity: Info.
HWI0635
SNMP trap: Yes
SUTL: can not process int x:funcPtr = NULL

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 998 of 2360

HWI0636
SUTL: can not get unprotDataPtr (FpSwitchIsr): obJId=x

Action:
Severity: Info.
HWI0637
SNMP trap: Yes

O=OK, 1=PRAM_BAD, 2=REGISTER_BAD, 3=BOARD_MISSING
Action:
Severity: Info.
HWI0638
SNMP trap: Yes

Action:
Severity: Info.
HWI0639
SNMP trap: Yes
SUTL: can not create sutlFpBackGrnd task

Action:
Severity: Info.
HWI0640
SNMP trap: Yes
SUTL: can not stop sutlFpBackGrnd task: JobId=x

Action:
Severity: Info.
HWI0641
SNMP trap: Yes

0=OK, 1=PRAM_BAD, 2=REGISTER_BAD, 3=BOARD_MISSING.
Action:
Severity: Info.
HWI0642
SNMP trap: Yes
SUTL: can not UNMASK intx: PLX chip not configured

then reinsert the card. After reinsertion is detected, SUTL H/W should be
accessible.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 999 of 2360

HWI0643

SUTL will not generate any interrupts.
Action: Attempt to dis.enl the SUTL in ovl135. If that doesn't work, remove the
SUTL Main card, wait for the HWI102 "disconnect" msg, then reinsert the card.
After the reinsertion is detected, the problem should have been corrected.
Severity: Major.
HWI0644
SNMP trap: Yes

Action:
Severity: Info.
HWI0645
SNMP trap: Yes
Can't MASK int xx: PLX chip not configured.

Action:
Severity:
HWI0646
SNMP trap: Yes

Action:
Severity: Info.
HWI0647
SNMP trap: Yes

Action:
Severity: Info.
HWI0648
SNMP trap: Yes
S/W error
Action: Try warm starting system. May need to cold start
Severity: Major.
HWI0649
SNMP trap: Yes
S.W error
Action: Try warm starting system. May need to cold start.
Severity: Major.
SNMP trap: Yes
System Messages
Page 1000 of 2360

HWI0650
S/W error
Severity: Major.
HWI0651
SNMP trap: Yes
S.W error
Severity: Major.
HWI0652
SNMP trap: Yes
SUTL: can not reg SUTL ISR;Slot x not configured AND noAccess
Action: Remove the SUTL Main card, wait for the HWI102 "disconnect msg,
then reinsert the card into slot 15. After the reinsertion is detected, SUTL H/W
should be accessible.
Severity: Info.
HWI0653
SNMP trap: Yes
SUTL: can not reg SUTL ISR; Slot x configured BUT noAccess
Action: Remove the SUTL Main card, wait for the HWI102 "disconnect: msg,
then reinsert the card. After the reinsertion is detected, SUTL H.W should be
accessible.
Severity: Info.
HWI0654
SNMP trap: Yes
SUTL is probably in the wring slot. Make sure it is in slot 15.

Action:
Severity: Info.
HWI0655
SNMP trap: Yes
SUTL:L sutBackGrndTest invoke

Action:
Severity: Info.
HWI0656
SNMP trap: No
STUL: can not determine if SUTL is in the slot: slotName, x

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1001 of 2360

HWI0657

Action:
Severity: Info.
HWI0658
SNMP trap: Yes

Action:
Severity: Info.
HWI0659
SNMP trap: Yes
SUTL: can not store cardID in unprot struct

Action:
Severity: Info.
HWI0660
SNMP trap: Yes
SUTL: can not mask/ clear FP_SWITCH int: can not access H/W
Action: If condition persists, remove the SUTL Main card, wait for the HWI102
"disconnect" msg, then reinsert the card. After reinsertion is detected, STUL H/W
Severity: Info.
HWI0661
SNMP trap: Yes
SUTL: can not mask/clear ADDR_ERR int: can not access H/W
"disconnect" msg, then reinsert the card. After reinsertion is detected, SUTL H/W
Severity: Info.
HWI0662
SNMP trap: Yes
SUTL: can not mask/clear PLX int: can not access H/W
Action: If condition persists, remove the SUTL Main card wait for the HWI102
Severity: Info.
SNMP trap: Yes
System Messages
Page 1002 of 2360

HWI0663

0=OK, 1=PRAM_BAD, 2= REGISTER_BAD,3=BOARD_MISSING
Action:
Severity: Info.
HWI0664
SNMP trap: Yes
SUTL: can not unmask Main card ints: can not access H/W
Severity: Info.
HWI0665
SNMP trap: Yes
SUTL: can not unmask FP_SWITCH int: can not access H/W
Action: If conditions persists, remove the SUTL lMain card, wait for the
HWI102"disconnect" msg, then reinsert the card. After the reinsertion is detected,
SUTL H/W should be accessible.
Severity: Info.
HWI0666
SNMP trap: Yes
SUTL: can not unmask ADDR_ERR int: can not access H/W
Action: If condition persists remove the SUTL Main card, wait for the HWI102
"disconnect"mgs, then reinsert the card. After reinsertion is detected, SUTL H/W
Severity: Info.
HWI0667
SNMP trap: Yes
SUTL will not be able to generate any Interrupts.

Severity: Major.
HWI0668
SNMP trap: Yes
SUTL: can not mask Main card ints: can not access H/W
Action: If condition persists, remove the SUTL Main Card, wait for the HWI102
H/W should be accessible
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1003 of 2360

HWI0669
SUTL: can not chg faceplate LED to green: can not access H/W
Action: If condition persists, remove the SUTL lMain card, wait for the HWI102
Severity: Info.
HWI0670
SNMP trap: Yes
SUTL: WRONG slot (x): SUTL can only be in slot 15

Action: Be sure to insert the SUTL Main card in slot 15. Also, be sure the SUTL
Transition card is connected on the rear of the backplane directly behind the
SUTL Main Card (slot 15)
Severity: Minor.
HWI0671
SNMP trap: Yes
SUTL: can not perform FpBackGrnd task: can not access H/W
Severity: Info.
HWI0672
SNMP trap: Yes
SUTL H/W is not accessible.

Action: Remove the SUTL Main Card, wait for the HWI102 "disconnect" msg,
then reinsert the card. After the reinsertion is detected, SUTL H/W should be
accessible.
Severity: Info.
HWI0673
SNMP trap: Yes
Unprotected memory of the real HI objects on the ACTIVE side have been
overwritten with data from the STANDBY side. This can occur when both sides
appear to have the same side ID.
Action: First, check to see if the SUTL H/W on both sides is accessible. Do this
by performing the "test sutl: and "stat sutl" commands in OVL 135. If a SUTL card
is not accessible, try removing the card, wait for the system to detect the removal,
then reinsert the card. If both SUTL are accessible, the DIP switches on the SUTL
transition cards are probably both the same. One needs to be set to "0", the other
to "1". After taking the action described above, the switch will most likely need to
be initialized to clear up unprotected memory.
Severity: Info.
SNMP trap: Yes
System Messages
Page 1004 of 2360

HWI0676
STRN: Transition Card just went *In Service*. No OOS reason exist; interrupts
should be UNMASKED.
Action:
Severity: Info.
HWI0677
SNMP trap: Yes
STRN interrupts are also UNMASKED.

Action:
Severity: Info.
HWI0678
SNMP trap: Yes
OOS reason cleared automatically by HI Fault Monitoring.

Action:
Severity: Info.
HWI0679
SNMP trap: Yes
OOS reason cleared automatically by HI Fault Monitoring.

Action:
Severity: Info.
HWI0680
SNMP trap: Yes
STRN: NOT_SW_CONFIGURED OOS reason cleared.

Action:
Severity: Info.
HWI0681
SNMP trap: Yes
STRN H/W should now be accessible

Action:
Severity: Info.
HWI0682
SNMP trap: Yes
STRN: IN_TEST_MODE OOS reason cleared.

Action:
Severity: Info.
HWI0683
SNMP trap: Yes
Transition Card has been reinserted into the backplane.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1005 of 2360

HWI0684
STRN Card ID PROM has been read successfully

Action:
Severity: Info.
HWI0685
SNMP trap: Yes
STRN: Can not clr children's OOS rsn: can not get protDataPtr
Action:
Severity: Info.
HWI0686
SNMP trap: Yes
STRN: Transition Card just went *Out-Of-Service*

Action:
Severity: Info.
HWI0687
SNMP trap: Yes
STRN: can not set children's OOS rsn: can not get protDataPtr
Action:
Severity: Info.
HWI0688
SNMP trap: Yes
STRN interrupts are MASKED out

Action:
Severity: Info.
HWI0689
SNMP trap: Yes

Action: Check if SUTL Transition Card is connected solidly to the rear of the
backplane. If condition persists, may be bad card or connector.
Severity: Info.
HWI0690
SNMP trap: Yes
OOS reaeon set automatically by HI Fault Monitoring

Action: Check if SUTL Transmition Card is connected solidly to the rear of the
backplane. If condition persists, may be bad card or connector.
Severity: Info.
HWI0691
SNMP trap: Yes
STRN: NOT_SW_CONFIGURED OOS reason set

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1006 of 2360

HWI0692
STRN: NO_HW_ACCESS OOS reason set

Severity: Info.
HWI0693
SNMP trap: Yes
STRN: IN_TEST_MODE OOS reason set

Action:
Severity: Info.
HWI0694
SNMP trap: Yes
STRN: PACK_REMOVED OOS reason set. Transition card was removed

from
the backplane.
Action:
Severity: Info.
HWI0695
SNMP trap: Yes
STRN: CANT_READ_CARDID OOS reason set

Action:
Severity: Info.
HWI0696
SNMP trap: Yes
STRN: can not get unprotDataPtr (connectorIsr): objId=x

Action:
Severity: Info.
HWI0697
SNMP trap: Yes
STRN: Can not MASK int: can not get upstreamID

Action:
Severity: Info.
HWI0698
SNMP trap: Yes
STRN: Can not start strnConnBkGrnd task: JobId=x

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1007 of 2360

HWI0699

Action:
Severity: Info.
HWI0700
SNMP trap: Yes
STRN: can not get unprotDataPtr (strnConnBkGrnd): objId=x

Action:
Severity: Info.
HWI0701
SNMP trap: Yes
STRN: can not stop stsrnConnBkGrnd task; JobId=x

Action:
Severity: Info.
HWI0702
SNMP trap: Yes

0=OK, 1=PRAM_BAD, 2=REGISTESR_BAD, 3=BOARD_MISSIN
Action:
Severity: Info.
HWI0703
SNMP trap: Yes
STRN: can not UNMASK int x:can not get upstreamID

Action:
Severity: Info.
HWI0704
SNMP trap: Yes
SSTRN: can not register TRAN_INT with SUTL

Action:
Severity: Info.
HWI0705
SNMP trap: Yes
STRN: can not create strnConBkGrnd task

Action:
Severity: Info.
HWI0706
SNMP trap: Yes

0=OK, 1=PRAM_BAD, 2=REGISTER_BAD, 3=MISSING_BOARD
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1008 of 2360

HWI0707
STRN: Can not store cardID in unprot struct

Action:
Severity: info.
HWI0708
SNMP trap: Yes
STRN: can not mask Trans card ints: can not access H/W
lH/W should be accessible
Severity: Info.
HWI0709
SNMP trap: Yes
STRN: Can not mask/clear TRAN_INT: can not access H/W

H.W should be accessible.
Severity: Info.
HWI0710
SNMP trap: Yes
STRN: Can not unmask Trans card ints: can not access H/W
Severity: Info.
HWI0711
SNMP trap: Yes
STRN: can not unmask TRAN_INT: can not access H/W

"disconnect"msg, then reinsert the card. After the reinsertion is detected SUTL
Severity: Info.
HWI0712
SNMP trap: Yes
STRN: Can not perform ConnBkGrnd task: can not access H/W
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1009 of 2360

HWI0721
no OOS reason exist; interrupts should be UNMASKED.

Action:
Severity: Info.
HWI0722
SNMP trap: Yes
DISP interrupts are also UNMASKED

Action:
Severity: Info.
HWI0723
SNMP trap: Yes

Action:
Severity: Info.
HWI0724
SNMP trap: Yes

Action:
Severity: Info.
HWI0725
SNMP trap: Yes
SISP: NOT_SW_CONFIGURED OOS reason cleared

Action:
Severity: Info.
HWI0726
SNMP trap: Yes
DISP H/W should now be accessible

Action:
Severity: Info.
HWI0727
SNMP trap: Yes
DISP: IN_TEST_MODE OOS reason cleared

Action:
Severity: Info.
HWI0728
SNMP trap: Yes
DISP: Cable_MISSING OOS reason cleared

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1010 of 2360

HWI0729
DISP: BAD_LCD OOS reason cleared

Action:
Severity: Info.
HWI0730
SNMP trap: Yes
DISP Card ID PROM has been read successfully

Action:
Severity: Info.
HWI0731
SNMP trap: Yes
DISP: Can not start dispLedBkGrnd task: can not get unprotDataPtr: objId=x
Action:
Severity: Info.
HWI0732
SNMP trap: Yes
DISP: Can not start dispLedBkGrnd task: JobId=x

Action:
Severity: Info.
HWI0733
SNMP trap: Yes

Action:
Severity: Info.
HWI0734
SNMP trap: Yes

Action:
Severity: Info.
HWI0735
SNMP trap: Yes
DISP: Display Panel just went *Out-Of-Service*

Action:
Severity: Info.
HWI0736
SNMP trap: Yes
DISP interrupts are MASKED out

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1011 of 2360

HWI0737

Action: Check if Disp cable(s) are connected solidly from the Display Panel to
the back of the SUTL Transition card. If condition persists, may be bad cable or
connector.
Severity: Info.
HWI0738
SNMP trap: Yes
OOS reason set automatically by Hi Fault Monitoring.

Action: Check if DISP cable(s) are connected solidly from the Display Panel to
the back of the SUTL Transition card. If condition persists, may be bad cable or
connector.
Severity: Info.
HWI0739
SNMP trap: Yes
DISP: NOT_SW_CONFIGURED OOS reason set

Action:
Severity: Info.
HWI0740
SNMP trap: Yes
DISP: NO_HW_ACCESS OOS reason set

"disconnect"msg, then reinsert the card. After the reinsertions detected, SUTL
Severity: Info.
HWI0741
SNMP trap: Yes
DISP: IN_TEST_MODE OOS reason set

Action:
Severity: Info.
HWI0742
SNMP trap: Yes
DISP: CABLE_MISSING OOS reason set

Action:
Severity: Info.
HWI0743
SNMP trap: Yes
DISP: BAD_LCD OOS reason set

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1012 of 2360

HWI0744
DISP: CANT_READ_CARDID OOS reason set

Action:
Severity: Info.
HWI0745
SNMP trap: Yes

Action:
Severity: Info.
HWI0746
SNMP trap: Yes
DISP: Can not MASK int x: can not get upstramId

Action:
Severity: Info.
HWI0747
SNMP trap: Yes
DISP: Can not UNMASK int x: can not get upstreamId

Action:
Severity: Info.
HWI0748
SNMP trap: Yes

Action:
Severity: Info.
HWI0749
SNMP trap: Yes
DISP: Can not stop dispLedBkGrnd task; JobId=x

Action:
Severity: Info.
HWI0750
SNMP trap: Yes
DISP: Can not create dispLedBkGrnd task

Action:
Severity: Info.
HWI0751
SNMP trap: Yes
DISP: Can not register DSPL_CBL_INT with STRN

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1013 of 2360

HWI0752

Action:
Severity: Info.
HWI0753
SNMP trap: Yes
DISP: Cant store cardID in unprot struct

Action:
Severity: Info.
HWI0754
SNMP trap: Yes
DISP: Can't mask Disp Pnl ints: can't access H/W

Severity: Info.
HWI0755
SNMP trap: Yes
DISP: Can not chg Pnl STATUS LED to green: can not access H/W
Severity: Info.
HWI0756
SNMP trap: Yes
DISP: ChgDisplay called with CP slot num (x):illegal

Action:
Severity: Info.
HWI0757
SNMP trap: No
DISP: Can not unmask DISP ints: can not access H/W
Action: If condition persists, remove the SUTL Main card wait for the HWI0102
Severity: Info.
SNMP trap: Yes
System Messages
Page 1014 of 2360

HWI0758
DISP: Can not unmask DSPL_CBL_INT: can not access H/W

H/W Should be accessible.
Severity: Info.
HWI0759
SNMP trap: Yes
DISP: Can not mask/clear DSPL_CBL_INT: can not access H/W

Action: If condition Persists, remove the SUTL Main card, wait for the HWI0102
Severity: Info.
HWI0760
SNMP trap: Yes
DISP: Can not perform LedBkGrnd task: can not access H/W
Severity: Info.
HWI0761
SNMP trap: Yes
DISP: Can not chg LED stat for slot x: can not access H/W
Severity: Info.
HWI0762
SNMP trap: No
DISP: Can not get class ID; can not chg LEDs for slot x
Action:
Severity: Info.
HWI0763
SNMP trap: Yes
DISP: can not chg CP LED stat: can not access H/W
Action: If condition persists, remove the SUTL Main card, wait for the WHI0102
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1015 of 2360

HWI0764
DISP: Can not reinitialize objID for LED control

Action:
Severity: Info.
HWI0766
SNMP trap: Yes
No OOS reason exist, interrupts should be UNMASKED

Action:
Severity: Info.
HWI0767
SNMP trap: Yes
XSMP interrupts are also UNMASKED

Action:
Severity: Info.
HWI0768
SNMP trap: Yes

Action:
Severity: Info.
HWI0769
SNMP trap: Yes

Action:
Severity: Info.
HWI0770
SNMP trap: Yes

Action:
Severity: Info.
HWI0771
SNMP trap: Yes

Action:
Severity: Info.
HWI0772
SNMP trap: Yes
XSMP: NOT_SW_CONFIGURED OOS reason cleared

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1016 of 2360

HWI0773
H/W should now be accessible

Action:
Severity: Info.
HWI0774
SNMP trap: Yes
XSMP: IN_TEST_MODE OOS reason cleared

Action:
Severity: info.
HWI0775
SNMP trap: Yes
XSMP: CABLE_MISSING_OOS reason cleared

Action:
Severity: Info.
HWI0776
SNMP trap: Yes
XSMP: XSM Port just went *Out-Of-Service*

Action:
Severity: Info.
HWI0777
SNMP trap: Yes
XSMP interrupts are MASKED out

Action:
Severity: Info.
HWI0778
SNMP trap: Yes

Action: Check if XSM cable is connected solidly from the Xsm to the back of the
SUTL Transition card. If condition persists, may be bad cable or connector.
Severity: Info.
HWI0779
SNMP trap: Yes

Action: Check if XSM Cable is connected solidly form the XSM to the back of
the SUTL Transition card. If condition persists, may be bd cable or connector
Severity: Info.
HWI0780
SNMP trap: Yes

Action: Check if XSM cable iss connected solidly from the XSM to the back of
the SULTl Transition card. If condition persists, may be bad cable or connector
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1017 of 2360

HWI0781
OOS reason set automatically by HI Fault Monitoring.

Action: Check XSM cable is connect solidly form the XSM to the back of the
SUTL Transition card. If condition persists, bay be bad cable or connector.
Severity: Info.
HWI0782
SNMP trap: Yes
XSMP: NO_HW_ACCESS OOS reason set

Severity: Info.
HWI0783
SNMP trap: Yes
XSMP; NOT_SW_CONFIGURED OOS reason set

Action:
Severity: Info.
HWI0784
SNMP trap: Yes
XSMP: IN_TEST_MODE OOS reason set

Action:
Severity: Info.
HWI0785
SNMP trap: Yes
XSMP: CABLE_MISSING OOS reason set

Action:
Severity: Info.
HWI0786
SNMP trap: Yes

0=OK, 1=PRAM_BAD, 2=REGISTER_BAD,3=MISSING_BOARD
Action:
Severity: Info.
HWI0787
SNMP trap: Yes
Driver levcel code experienced a problem:

O=OK, 1=PRAM_BAD, 2= REGISTER_BAD, 3=BOARD_MISSING
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1018 of 2360

HWI0788
XSMP: can not MASK int x:can not get upstreamID

Action:
Severity: Info.
HWI0789
SNMP trap: Yes
XSMP: Can notUNMask int x: can not get upstreamId

Action:
Severity: Info.
HWI0790
SNMP trap: Yes
XSMP: Can not register XSM_CBL_INT with STRN

Action:
Severity: Info.
HWI0791
SNMP trap: Yes
XSMP: Can not register MAJOR_INT with STRN

Action:
Severity: Info.
HWI0792
SNMP trap: Yes
XSMP: Can not start xsmpCblBkGrnd task Jobld=x

Action:
Severity: Info.
HWI0793
SNMP trap: Yes
ZSMP: can not start zsmpMajorBkGrnd task: JobId=x

Action:
Severity: Info.
HWI0794
SNMP trap: Yes
XSMP: Can not stop xsmpCblBkGrnd task: JobId=x

Action:
Severity: Info.
HWI0795
SNMP trap: Yes
XSMP: Can not stop xsmpMajorBkGrnd tsk: JobId=x

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1019 of 2360

HWI0796
XSMP: Can not create xsmpCblBkGrnd task

Action:
Severity: Info.
HWI0797
SNMP trap: Yes
XSMP: can not create xsmpMajorBkGrnd task

Action:
Severity: Info.
HWI0798
SNMP trap: Yes
XSMP: Can not get unprotDataPtr (xsmpCableIsr):objId=x

Action:
Severity: Info.
HWI0799
SNMP trap: Yes
XSMP: can not get unprotDataPtr (xsmpMajorLineIsr): objId=x

Action:
Severity: Info.
HWI0800
SNMP trap: Yes

Action:
Severity: Info.
HWI0801
SNMP trap: Yes

0=OK, 1=PRAM_BAD, 2= REGISTER_BAD, 3=BOARD_MISSING
Action:
Severity: Info.
HWI0802
SNMP trap: Yes

0=OK, 1=PRAM_BAD, 2=REGISTER_BAD, 3=BOARD MISSING
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1020 of 2360

HWI0803

0=OK, 1=PRAM_BAD, 2=REGISTER_BAD, 3=MISSING_BORD
Action:
Severity: Info.
HWI0804
SNMP trap: Yes

0=OK, 1=PARM_BAD, 2=REGISTER_BAD, 3=BOARD_MISSING
Action:
Severity: Info.
HWI0805
SNMP trap: Yes
Driver level code experienced a problem: O=OK, 1=PRAM_BAD,

2=REGISTER_BAD, 3=BOARD_MISSING
Action:
Severity: Info.
HWI0806
SNMP trap: Yes
Driver level code experienced a problem: 0= OK, 1=PRAM_BAD,

Action:
Severity: Info.
HWI0807
SNMP trap: Yes
Driver Level code experienced a problem: 0+OK, 1=PRAM_BAD,

Action:
Severity: Info.
HWI0808
SNMP trap: Yes
XSMP: Can not mask XSM Port ints: can not access H/W
Action: If conditions persists, remove the SUTL Main card, wait for the HWI0102
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1021 of 2360

HWI0809
XSMP: can not perform MajorBkGrnd task: can not access H/W
Action: If condition persists, remove the SUTL Man card, wait for the HWI0102
Severity: Info.
HWI0810
SNMP trap: Yes
XSMP: can not perform CbllBkGrnd task: can not access H/W.
Severity: Info.
HWI0811
SNMP trap: Yes
XSMP: can not mask/clear XSM_CBL_INT: can not access H/W.

Action: If condition persists, remove theSUTL Main card, wait for the HWI0102
Severity: Info.
HWI0812
SNMP trap: Yes
XSMP: Can not mask/clear MAJOR_INT: can't access H/W

"disconnect msg, then reinsert the card. After the reinsertion is detected, SUTL
Severity: Info.
HWI0813
SNMP trap: Yes
XSMP: Cant unmask XSMP its: cant access H/W

Action: If condition persists, remove the SUTL Main card, wait fort he HWI102
Severity: Info.
HWI0814
SNMP trap: Yes
XSMP: Cannot unmask XSM_CBL_INT: cant access H/W

Action: If condition persists, remove the SULT Main card, wait for the HW1102
Severity: Info.
SNMP trap: Yes
System Messages
Page 1022 of 2360

HWI0815
XSMP: can not unmask MAJOR_INT: can not access H/W

Action: If condition persists, remove the SUTL Main card, wait for the HW1102
"disconnect" msg, then reinsert the card. After the reinsertion is detected, SUTH
Severity: Info.
HWI0820
SNMP trap: Yes
SUIO: IN_TEST_MODE OOS reason set.

Action:
Severity: Major.
HWI0821
SNMP trap: Yes
SUIO: siop2691 just went *Out-of-Service*.

Action:
Severity: Info.
HWI0822
SNMP trap: Yes
SUIO: Craftsperson DIS OOS reason set.

Action:
Severity: Major.
HWI0823
SNMP trap: Yes
SUIO: siop2691 just went *In Service*.

Action:
Severity: Major.
HWI0824
SNMP trap: Yes
SUIO: NO_HW_ACCESS OOS reason cleared.

Action:
Severity: Info.
HWI0825
SNMP trap: Yes
SUIO: HI_OOSR_BAD_PORT OOS reason cleared.

Action:
Severity: Major.
HWI0826
SNMP trap: Yes
SUIO: HI_OOSR_BAD_DONGLE_ OOS reason cleared.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1023 of 2360

HWI0827
SUIO: NOT_SW_CONFIGURED OOS reason cleared.

Action:
Severity: Major.
HWI0828
SNMP trap: Yes
SUIO: IN_TEST_MODE OOS reason cleared.

Action:
Severity: Major.
HWI0829
SNMP trap: Yes
SUIO: All OOS rsns cleared due to Craftsperson ENL.

Action:
Severity: Major.
HWI0830
SNMP trap: Yes
SUIO: Can't config serial port.

Action:
Severity: Major.
HWI0831
SNMP trap: Yes
SUIO: SUTL CARD PLX chip is not CONFIG'D.

Action:
Severity: Major.
HWI0832
SNMP trap: Yes
SUIO: NO_HW_ACCESS OOS reason set.

Action:
Severity: Major.
HWI0833
SNMP trap: Yes
SUIO: HI_OOSR_BAD_PORT OOS reason set.

Action:
Severity: Major.
HWI0834
SNMP trap: Yes
SUIO: HI_OOSR_BAD_DONGLE OOS reason set.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 1024 of 2360

HWI0835
SUIO: NOT_SW_CONFIGURED OOS reason set.

Action:
Severity: Major.
HWI0850
SNMP trap: Yes
IPB: objid = 0x%x. The given object failed o register its ISR with PCI vector
table.
Action:
Severity: Info.
HWI0851
SNMP trap: Yes
IPB failed to attach ISRs in CPs vector table for the given IRQ.
Action:
Severity: Info.
HWI0852
SNMP trap: Yes
IPB could not service interrupts for the given IRQ number.
Action:
Severity: Info.
HWI0853
SNMP trap: Yes
IPB found invalid IRQ number in given slot.

Action:
Severity: Info.
HWI0854
SNMP trap: Yes
IPB: Could not service ISRs due to invalid IRQ number.

Action:
Severity: Info.
HWI0855
SNMP trap: Yes
IPB module failed to remove ISR of given object from its table.
Action:
Severity: Info.
HWI0922
SNMP trap: Yes
IPB: The given slot x is not within IPB's slot boundary.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1025 of 2360

HWI0923
IPB: Failed to program the pci Router due to invalid IRQ number x
Action:
Severity: Major.
HWI0925
SNMP trap: Yes
BIC: bicCardAsciiGet - Failed to get CardId for the given slot.

Action:
Severity: Info.
HWI0926
SNMP trap: Yes
BIC: bicGeoSideGet returns invalid side info. Side is defaulted to 1.

Action:
Severity: Info.
HWI0927
SNMP trap: Yes
ETH: Can't create itgHealthUpdate task.

Action:
Severity: Critical.
HWI0928
SNMP trap: Yes
ETH: Can't start itgHealthUpdate task:

JobId = x
Action:
Severity: Critical.
HWI0929
SNMP trap: Yes
IPB: found unprogrammed IRQ at index[x], reprogrammed IRQ[z] x = index of

the IRQ array, z = IRQ value that has been reprogrammed
Action: Contact Technical Support
Severity: Major.
HWI0930
SNMP trap: Yes
IPB: found double IRQ programmed: index[x] and index[y] sharing IRQ[z] x,y
= indexes of the IRQ array, z = IRQ value that the two indexes are sharing.
Action: Contact Technical Support.
Severity: Major.
SNMP trap: Yes
System Messages
Page 1026 of 2360

HWI0931
ETH: No carrier detected on ELAN network interface on side <side>. Port is

Out Of Service.
Action: Check ELAN network interface on side <side>
Severity: Major.
HWI0932
SNMP trap: Yes
ETH: ELAN network interface on side <side> is In Service.

Action:
Severity: Info.
HWI1753
SNMP trap: Yes
DISP: Can not store cardID in unprot struct

Action:
Severity: Info.
HWI7694
SNMP trap: No
Transition card was removed from the backplane

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1027 of 2360
HWR: Hardware Reset

The following messages indicate command errors that are related to system
reloads on Small Systems and Succession 1000 systems.
Messages
HWR0000
Hardware reset (LED flashes).

Action:
Severity: Info.
HWR0001
SNMP trap: No
Programming failed. Card is defective, or software cartridge is not seated

properly.
Action:
Severity: Info.
HWR0002
SNMP trap: No
SNMP trap: No
SNMP trap: No
64180 RAM failed.

Action:
Severity: Info.
HWR0003
Page 2 download error.

Action:
Severity: Info.
HWR0004
Invalid interrupt occurred.

Action:
Severity: Info.
HWR0005
SNMP trap: No
SNMP trap: No
Self-test failed.
Action:
Severity: Info.
System Messages
Page 1028 of 2360

HWR0006
VLSI initialization failure

Action:
Severity: Info.
HWR0007
SNMP trap: No
Indicates that the software and the System Core for pre-Option 11C, or Small
System Controller for Option 11C, have been reset.
Action:
Severity: Info.
HWR0008
SNMP trap: No
DSP memory test failure.

Action:
Severity: Info.
HWR0010
SNMP trap: No
Test channel request failure (already in use).

Action:
Severity: Info.
HWR0011
SNMP trap: No
SDI port message out of sequence.

Action:
Severity: Info.
HWR0012
SNMP trap: No
SDI Port output overflow.

Action:
Severity: Info.
HWR0013
SNMP trap: No
SNMP trap: No
SDI Port in invalid state.

Action:
Severity: Info.
HWR0014
SDI Port message from invalid port number.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1029 of 2360

HWR0015
SDI Port output timeout.

Action:
Severity: Info.
HWR0016
SNMP trap: No
SDI Port message queue write failure.

Action:
Severity: Info.
HWR0017
SNMP trap: No
SDI Port output message queue write failure.

Action:
Severity: Info.
HWR0018
SNMP trap: No
SDI Port output buffer write failure.

Action:
Severity: Info.
HWR0019
SNMP trap: No
SDI Port output message queue read failure.

Action:
Severity: Info.
HWR0020
SNMP trap: No
Flash conversion to 2 Meg. (requested).

Action:
Severity: Info.
HWR0021
SNMP trap: No
Flash conversion to 2 Meg. (automatic).

Action:
Severity: Info.
HWR0030
SNMP trap: No
Interrupt to task communication error.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1030 of 2360

HWR0040
Pack reset due to tack errors.

Action:
Severity: Info.
HWR0041
SNMP trap: No
Operating system reset due to task errors.

Action:
Severity: Info.
HWR0042
SNMP trap: No
Suspended task restarted.

Action:
Severity: Info.
HWR0043
SNMP trap: No
Suspended task resumed.

Action:
Severity: Info.
HWR0044
SNMP trap: No
SNMP trap: No
Task time-out.
Action:
Severity: Info.
HWR0100
Real time clock failure.

Action: Replace the SSC card by following the steps in the Hardware
replacement guide.
Severity: Info.
HWR0101
SNMP trap: No
DRAM failure
Action: Use STAT MEM in LD 135 to check the memory. Replace SSC card by
following the steps in the Hardware replacement guide.
Severity: Info.
HWR0102
SNMP trap: No
SRAM failure.
replacement guide.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1031 of 2360

HWR0103
Auxiliary CPU (68020) failure.

replacement guide.
Severity: Info.
HWR0104
SNMP trap: No
Conference Circuit failure.

replacement guide.
Severity: Info.
HWR0105
SNMP trap: No
Speechpath network failure.

replacement guide.
Severity: Info.
SNMP trap: No
System Messages
Page 1032 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1033 of 2360
ICU: Intercept Computer Update (LD 51)

Messages
ICU0000
Program Identifier
Action:
Severity: Minor.
ICU0001
SNMP trap: No
SNMP trap: Yes
SNMP trap: Yes
Invalid command.
Action:
Severity: Info.
ICU0002
Too many characters.

Action:
Severity: Info.
ICU0003
Invalid number of parameters.

Action:
Severity: Info.
ICU0004
SNMP trap: Yes
Customer number does not exist.

Action:
Severity: Info.
ICU0005
SNMP trap: Yes
ICP, APL, ACD_BAS, MW, SUPP, FTC, or FFC package missing.

Action:
Severity: Info.
ICU0006
SNMP trap: Yes
SNMP trap: Yes
Invalid input.
Action:
Severity: Info.
System Messages
Page 1034 of 2360

ICU0007
ICP does not exist for this customer.

Action:
Severity: Info.
ICU0008
SNMP trap: Yes
SNMP trap: Yes
No customer to update.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1035 of 2360
INI: Initialize
The initialization program (INI) is a resident program used to build the
unprotected data blocks in system software. An occurrence of an initialization
is indicated by INI messages.
Messages
INI0000 fc hh mm ss pg pc fp fa (x y) hex An initialization has taken place. The additional fields
associated with this message are described below.
fc = fault code identifying the cause of the initialization. See "FAULT CODES"
on page 555.
hh = the hour of initialization
mm = the minute of initialization
ss = the second of initialization
pg = the program page at the time of trap ( in hexadecimal)
pc = the program xounter (in hexadecimal)
fp = the fault page (in hexadecimal)
fa = the fault address (when the fault page is on page 3). See "Page 3 fault
addresses: on page 559.
x = the active CPU, if it is known. If it is not known, a question mark (?) is
output. This field only occurs for dual CPU systems.
y = the active Clock Controller (SL - 1 XT only)
hex = the contents of the maintenance display (see HEX for interpretation)
The INI1000 message is followed by DSET000 message.
FAULT CODES
0000 Normal initialize after SYSLOAD. This
code may also appear if a fault occurs
in memory 0. In this case, the
maintenance display should be 10 with
no SYSLOAD message before the
initialize. An INI004 message may
follow.
0001 Manual initialize by attendant. If this
code appears but no attendant has
operated the manual initialize key,
check whether any attendant console
is equipped with an initialize key. If not,
probable software or data error: check
data for each console. If some consoles have an initialize key, possible
fault in:
System Messages
Page 1036 of 2360

1. Attendant console. Use LD 31 to
check each console having an INI
key.
2. Signaling path to an attendant console. Use TEST command of LD 45
to check signaling.
0002 Manual initialize from the Miscellaneous (MISC) or Interface (IF) pack. If
this code appears but the button on
the MISC pack was not pressed,
probable fault on MISC pack associated with the active CPU. The
manual initialize button will also reenable, if possible, all disabled items.
0003 PE signaling fault. INI003 message will
follow to identify the Peripheral Signaling card at fault.
004 Real-time clock (RTC) has failed (in a
system having two CPUs). Probable
fault in pack providing clock (i.e.
Peripheral Signaling pack or Control,
Interface and Memory pack) or Miscellaneous pack associated with active
CPU.
0005 A CPU changeover has taken place
due to a failure of the then-active CPU.
The faulty CPU should be identified by
a subsequent INI005 message. A fault
may exist on:
1. Miscellaneous pack
2. QPC424 CPU pack or daughter
board ROM (especially if maintenance display shows 02)
3. Function (FN), Interface (IF) or
Control and Timing pack
4. CIM pack (especially for maintenance display codes 088 and 08D)
5. CMA pack
0006 Overload detected from a particular
loop. Loop will be disabled. OVD
diagnostic message should follow. If an
OVD message identifying a faulty PE
pack appeared before the initialize,
553-3001-411
Standard 15.00
January 2006
Page 1037 of 2360

remove that pack before reenabling
the loop.
0007 Overload detected from a peripheral
signaling pack. Offending Peripheral
Signaling pack will be disabled. OVD
diagnostic message should follow.
0008 Invalid operation code (opcode). Inform
operating company.
0009 Invalid interrupt. Inform operating
company.
000A Attempt to write store using nil pointer.
Software error.
000B Main stack underflow. Software error.
000C Broken queue. Software error.
000D Response timeout in data store 0.
System should reload. Replace data
store 0.
000E Trying to idle Call Register with active
auxiliary Call Registers still linked to it.
Inform operating company.
000F Service change. Data store exceeded.
Should be preceded by a warning
message, "Equip more data store".
0010 Conversions complete.
0011 Triggered by software verification
program (used by operating company
only). If an investigation by the operating company is not currently active,
then inform the operating company.
0012 Caused by Common Equipment
Diagnostic (CED) trying to rebuild unprotected data store.
0013 All extenders disabled.
0014 Firmware fault. nCPU clock unmasked.
Same as for 0011.
0015 Firmware fault. RTC interrupt on level 7
unmasked. Same as for 0011.
0017 More than 5 NT8D04 Network or
Network/DTR packs need software
download recovery during the autorecovery or midnight audit.
Where: xxxx = cause of the initialization
0018 More than 5 NT8D01 Peripheral
System Messages
Page 1038 of 2360

Controllers need software download
recovery during the auto-recovery or
midnight audit.
0019 From Firmware: The system has
initialized after recovery from battery
backup. (Note: that the system clock
has slipped during the time that the
system was under battery power.)
001C There have been more than 10 occurences of auto-recoveries to avert
INI000 000C problems since the last
system initialization. INI000 001C was
triggered to perform system cleanup
following midnight routines.
Action: Report the problem to your support
engineer for further analysis.
001D An invalid pointer is found during
queue processing.
Action: Report the problem to your support
engineer for further analysis.
0100 Trap data blocks are not valid. No
action.
0200 SYSLOAD was caused by response
timeout of data store.
0400 Power-on reset. Power-up, manual
reload.
0800 Software trap. No action.
1000 Memory Parity error. Determine fault
page ( field 7 of INI000 message).
Suspect a faulty:
1. CMA pack
2. MISC pack
3. Memory pack
2000 Watchdog timer runlet. This is sometimes a software fault, but may also
indicate hardware faults as follows:
1. If an INI002 or INI003 message
follows, the device(s) specified may
be faulty.
2. If the maintenance display = 04,
the following packs are suspect,
(in addition to those listed in the
Maintenance Display Code
553-3001-411
Standard 15.00
January 2006
Page 1039 of 2360

interpretations):
a Ce extender packs
b Miscellaneous
c Serial Data Interface (SDI)
d Tape Interface
e Tone and Digit Switch (TDS)
3. If the maintenance display = 05, the
following packs are suspect, (in
addition to those listed in the
Maintenance Display Code
interpretations):
a Peripheral Signaling
b CE extender.
4. Affected CPU may be faulty.
5. CIM may be faulty (if equipped).
6. Also occurs if a TDS card is in
slot 5 of an SL-1 ST and configured
as loop 0. This is not a valid
configuration.
3000 Same as code 1000.
4000 Write protection violation. An attempt
was made to overwrite a protected
memory location. Possible software
fault. This code may also appear if the
affected CPU is faulty, especially the
MISC pack.
8000 Response timeout. A memory or other
device failed to respond to a read-write
request.
If an INI002, INI003 or INI004
message follows the indicated
device(s) may be faulty. If several
devices on the same shelf are indicated, the CE extender connecting the
shelf to the CPU may be faulty.
If none of the above messages appear,
this code probably indicates a software
fault, or:
1. CPU fault, especially Miscellaneous pack and, if equipped, Inter-
System Messages
Page 1040 of 2360

face (IF) pack of affected CPU.
2. Peripheral Signaling pack on
same bus as affected CPU.
3. CIM (if equipped).
4. Faulty ROM on CPU (QPC424 or
QPC425).
A000 Same as code 8000.
B000 Same as code 1000.
C000 Same as code 8000.
D000 Same as code 1000.
E000 Same as code 8000.
F000 Same as code 1000.
Page 3 fault addresses
This table is used to interpret the fault
address for page 3 faults (external devices).
To obtain the address of the faulty circuit pack, the 4-digit hexadecimal codes
must be
converted to 4-digit binary numbers (see HEX).
Outputs not covered in this table cannot be decoded to an address. However
they may indicate a Bus Fault.
0800 to 0807 CPU/Extender
1806 CMA pack
3000 to 3F7F Serial Data Inter (SDI).
Bits 4 to 7 provide card
addressing.
3FC8 Tape Interface pack
8000 to A7FF Network pack
For single Network packs:
Bits 7 to 13 for non-enhanced
network loops
Bits 11 to 13 for group.
Bits 2 to 6 determine timeslots
used.
For dual Network packs:
Bits 6 to 10 for loop
Bits 11 to 13 for group.
Bits 1 to 5 determine timeslots
used.
C000 to D3FF Peripheral Signaling (PS) pack
553-3001-411
Standard 15.00
January 2006
Page 1041 of 2360

Bits 13 to 15 give PS address.
Bits 9 to 12 give loop
address.
E000 to E8FF Multigroup Switch (X08 and
X37) or Intergroup Switch
X11). Address Bit 5 determines the odd or even switch
(i.e., 0 or 1). Address Bits 9
through 11 determine the card
affected.
F000 to FFFF QPC 157 Multigroup Switch
(X08 and X37) or Intergroup
Switch (Xll). If bit 5=0, then
card 0 is affected. If bit 5=1,
then card 1 is affected.
Action:
Severity: Critical.
INI0001
SNMP trap: Yes
Insufficient memory for this system. If maintenance display shows a defective

memory module, refer to HEX.
Action: If maintenance display does not show a memory fault, memory size must
be increased.
Severity: Critical.
INI0002xx
SNMP trap: Yes
I/O device fault, where xx is to the maintenance display code in.

Action:
Severity: Critical.
INI0003 xx
SNMP trap: Yes
Network or PE signaling fault, where xx is the maintenance display code in

HEX.
Action:
Severity: Critical.
INI0006 xx
SNMP trap: Yes
A device has been detected which is not defined in the configuration record
(LD17), where xx is the maintenance display code in HEX.
Action: The device must be removed or enabled.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1042 of 2360

INI0007 xx
Intergroup Switch (IGS) pack fault, where xx is the maintenance display code
in HEX.
Action:
Severity: Critical.
INI0008 xx
SNMP trap: Yes
I/O faults seen from the standby CPU, where xx is the maintenance display
code in HEX. This is a minor alarm.
This message only appears if the standby CPU may be used but with a
degradation of network or I/O access as shown by comparing INI0002 with
INI0008, INI0003 with INI0009, and INI0007 with INI0010.
Action:
Severity: Critical.
INI0009 xx
SNMP trap: Yes
Network faults seen from the standby CPU, where xx is the maintenance
display
code (see HEX). This is a minor alarm.
Action:
Severity: Critical.
INI0010 xx
SNMP trap: Yes
IGS or MGS faults seen from the standby CPU, where xx is the maintenance
display code in HEX.
Action:
Severity: Critical.
INI0011 xx
SNMP trap: Yes
Network shelves do not respond to clock 0 (SCG card 0), where xx is the
maintenance display code in HEX. Probable fault is on SCG, IGS or
interconnecting cables via Junctor.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1043 of 2360

INI0012 xx
Network shelves do not respond to clock1 (SCG card 1), where xx is the
maintenance display code in HEX. Probable fault is on SCG, IGS or
interconnecting cables via Junctor.
Action:
Severity: Critical.
INI0013 x
SNMP trap: Yes
Possible CPU fault: x is the number of CPU. Given CPU has been initialized
more than 5 times since the previous running of the midnight routines.
Action:
Severity: Critical.
INI0021
SNMP trap: Yes
Idle output queue was not setup.

Action:
Severity: Critical.
INI0100 0200-29F
SNMP trap: No
DDSL pack failed read/write response test. Fault codes 200-29F indicate the
DDSL number 0-159 respectively.
For Option 81 systems, the INI0100 codes have specific meanings. These
meanings are listed below:
00000021 Hardware Sanity Timeout
00000022 SWO: Failure on switchover
00000023 SWO: Too many switchovers
00000024 WARM: Disk OS Warmstart
failure
00000025 WARM: Too many Disk OS
Warmstarts.
00000026 WARM: Disk OS not loaded
00000027 RESET: Forced SWO in process
00000028 RESET: Soft Reset in progress
00000029 TASK: Unable to create msg
queue.
0000002A Protected Memory checksum
failure.
0000002B INFO: Disk OS Warmstart begins
0000002C INFOC: DRAM is uninitialized
0000002D Restart: Cannot delete safe task
0000002E RESET: Task threshold
exceeded
0000002F WARM: Exc vector threshold
exceeded
System Messages
Page 1044 of 2360

00000030 WARM: Exc total threshold
exceeded
00000031 WARM: Non-bus exc in interrupt
00000032 WARM: Exc handling already
busy
00000033 WARM: Exc Restart Task ()
failed
00000034 RESET: Manual INIT requested
00000035 SEG: Checksum failure detected
00000036 SEG: Disk OS Test segment
corrupt
00000037 SEG: Disk OS partitions corrupt
00000038 DISKOS: Unable to load SL-1
00000039 DISKOS: Unable to start SL-1
0000003A INSTALL: boot after installation
0000003B IOP Bus Error on active IOP
0000003C Parity Err on both sides
0000003D Parity Err in Split mode
0000003E Parity Err - remote SIMM: missing
0000003F Parity Err - remote SIMM: disabled
00000040 HI BER recommended action
00000041 HI BER TASK_RESTART for
safe task
00000042 HI Warm Start not possible
00000049 OS: manual (PDT) request
0000004A OS: request to reboot (sysToMon)
0000004B OS: RST initialization failed
0000004C OS: SKD initialization failed
0000004D OS: SWD initialization failed
0000004E OS: PMEM initialization failed
0000004F OS: Security Card check failed
00000050 OS: Normal recovery from BER
00000051 OS: Unable to recover from BER
00000052 OS: Unable to run "diskos"
00000053 OS: Unable to load "diskos"
00000054 OS: VOL initialization failed
00000055 OS: SCSI initialization failed
00000056 OS: DOS initialization failed
00000057 OS: IOP initialization failed
00000058 OS: EXC initialization failed
00000059 OS: IOS initialization failed
0000005A OS: Clock initialization failed
0000005B OS: Failed during Loader run
553-3001-411
Standard 15.00
January 2006
Page 1045 of 2360

0000005C OS: Failed to spawn Loader task
0000005D OS: kernel initialization failed
0000005E OS: diskos P seg overlaps U seg
0000005F Operating System level command
to coldstart
Action:
Severity: Critical.
INI0102
SNMP trap: Yes
The mass storage interface is not responding; peripheral software

downloading
was not attempted.
Action:
Severity: Critical.
INI0107 G S
SNMP trap: No
Superfluous clock (s) is found. The information on Group and Side of the
superfluous clock(s) is provided.
Action:
Severity: Critical.
INI0108 G S
SNMP trap: Yes
Only one clock has been found in the system in the Group G and Side S. This
indicates that either there is no clockin the other side or the second installed
clock has its shelf-sideswitch set wrong.
Action:
Severity: Critical.
INI0109
SNMP trap: Yes
No clock has been found in the system.

Action:
Severity: Critical.
INI0110 Z G S
SNMP trap: Yes
No clock has been found in side Z and superfluous clock(s) has been found in
the other side. The information on Group and Side of the superfluous clock(s)
is provided.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1046 of 2360

INI0111
16K of unprotected memory space cannot be allocated for INIT ACD Queue
Call Restore (ACDR).
Action:
Severity: Critical.
INI0112
SNMP trap: Yes
INIT ACD Queue Call Restore (ACDR) aborted due to multiple system
initializations.
Action:
Severity: Critical.
INI0113
SNMP trap: Yes
Unable to rebuild DCS call. Physical TN corrupted.

Action:
Severity: Critical.
INI7273
SNMP trap: No
No response or the response was too slow (software timed out to avoid INIT
within INIT) from the carrier hardware during Carrier Remote Interface
initialization update. If the message is output again with the same loop
number, then it is an indication that there is a hardware fault in either LCI or
RCI card.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1047 of 2360
INST: Installation
Messages
INST0000
FATAL, Install cannot continue.

Action:
Severity: Info.
INST0001
SNMP trap: No
The Flash Rom Caching could not be disabled. Installation will fail.
Action: Retry the installation again. If the Flash Rom Caching could not be
disabled check that the flash daughter board is on properly. Cold start the system
and try again. If the problem persists contact your technical support group.
Severity: Major.
INST0002
SNMP trap: Yes
Unable to allocate memory. There is not enough free memory to allocate.

Action: Cold start the system and try the installation again. If the problem
persists contact your technical support group
Severity: Major.
INST0003
SNMP trap: Yes
Unable to create a directory. The directory could not be created.

Action: Check that the Drive is not full. If there is space check that the directory
tree exists and is not corrupted. If the directory is corrupted, remove the corrupted
directory and try the installation again. If the problem persists contact your
Severity: Info.
INST0004
SNMP trap: No
All the undo Installation files were not saved to the Software Delivery Card.
Undo Installations will not be possible.
Severity: Info.
SNMP trap: No
System Messages
Page 1048 of 2360

INST0005
Either the Upgrade Information Block pointer or the Module Information Block
pointer is corrupted.
Action: Quit the Install and start the install again. If the problem occurs again
cold start the system and start the installation again. If the problem persists
Severity: Info.
INST0006
SNMP trap: Yes
Unable to find any db file under dir \"%s\"

Action:
Severity: Info.
INST0007
SNMP trap: No
Fail to seek to the end of split file \"%s\"

Action:
Severity: Info.
INST0008
SNMP trap: No
Fail to append to a non-existence file \"%s\"

Action:
Severity: Info.
INST0009
SNMP trap: No
Error installing Database.

Action:
Severity: Info.
INST0010
SNMP trap: No
Unable to validate Hard disk partition \"%s\"

Action:
Severity: Info.
INST0011
SNMP trap: No
Unable to process the Install control file

Action:
Severity: Info.
INST0012
SNMP trap: No
Unable to open file \"%s\"

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1049 of 2360

INST0013
Unable to access database directory \"%s\"

Action:
Severity: Info.
INST0014
SNMP trap: No
Error parsing the Install control file

Action:
Severity: Info.
INST0015
SNMP trap: No
Disk does not belong to this set of Installation diskettes.

Action:
Severity: Info.
INST0016
SNMP trap: No
Can't install database, DB files cannot be obtained.

Action:
Severity: Info.
INST0017
SNMP trap: No
Unable to open the file \"%s\"for pre-allocation

Action:
Severity: Info.
INST0018
SNMP trap: No
Unable to pre-allocate file \"%s\"

Action:
Severity: Info.
INST0019
SNMP trap: No
Unable to make directory \"%s\"

Action:
Severity: Info.
INST0020
SNMP trap: No
New directory conflicts with existing file \"%s\"

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1050 of 2360

INST0021
Unable to open file \"%s\" for checksum

Action:
Severity: Info.
INST0022
SNMP trap: No
Error reading file \"%s\" during checksum

Action:
Severity: Info.
INST0023
SNMP trap: No
Error readinf floppy disk file \"%s\"

Action:
Severity: Info.
INST0024
SNMP trap: No
Unable to open hard disk file \"%s\" for writing.

Action:
Severity: Info.
INST0025
SNMP trap: No
Unable to write to hard disk file \"%s\"

Action:
Severity: Info.
INST0026
SNMP trap: No
Software Error - Assume Quit selection

Action:
Severity: Info.
INST0027
SNMP trap: No
Error copying file \"%s\" to hard disk

Action:
Severity: Info.
INST0028
SNMP trap: No
Missing last segment of split file \"%s\"

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1051 of 2360

INST0029
Checksum of \"%s\" does not match the actual

Action:
Severity: Info.
INST0030
SNMP trap: No
Missing card-id file on IODU %d.

Action:
Severity: Info.
INST0031
SNMP trap: No
New software is larger than maximum size.

Action:
Severity: Info.
INST0032
SNMP trap: No
Software error - Return error.

Action:
Severity: Info.
INST0033
SNMP trap: No
Unable to find the activate \"%s\" slot.

Action:
Severity: Info.
INST0034
SNMP trap: No
Unable to access the activate \"%s\" card.

Action:
Severity: Info.
INST0035
SNMP trap: No
Unable to get file name using DLO: \"%s\"

Action:
Severity: Info.
INST0036
SNMP trap: No
Unable to access file \"%s\"

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1052 of 2360

INST0037
Unable to open file \"%s\" for reading

Action:
Severity: Info.
INST0038
SNMP trap: No
Unable to write to hard disk, disk is full.

Action:
Severity: Info.
INST0039
SNMP trap: No
Unable to copy file \"%s\"

Action:
Severity: Info.
INST0040
SNMP trap: No
Unable to close file \"%s\"

Action:
Severity: Info.
INST0041
SNMP trap: No
Unable to open directory \"%s\" for reading

Action:
Severity: Info.
INST0042
SNMP trap: No
Unable to read directory \"%s\"

Action:
Severity: Info.
INST0043
SNMP trap: No
Unable to close directory \%s\.

Action:
Severity: Info.
INST0044
SNMP trap: No
Unable to rename file \%s\ to \%s\.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1053 of 2360

INST0045
Unable to copy file from \%s\ to \%s\.

Action:
Severity: Info.
INST0046
SNMP trap: No
Fail to copy directory from \%s\ to \%s\.

Action:
Severity: Info.
INST0047
SNMP trap: No
Unable to initialize partition \%s\.

Action:
Severity: Info.
INST0048
SNMP trap: No
Unable to find database file \%s\.

Action:
Severity: Info.
INST0049
SNMP trap: No
Unable to access directory \%s\.

Action:
Severity: Info.
INST0050
SNMP trap: No
No partition found, Install control file is corrupted.

Action:
Severity: Info.
INST0051
SNMP trap: No
Cannot continue, System has Disk Redundancy on.

Action:
Severity: Info.
INST0052
SNMP trap: No
Error in Database install, files size unmatched.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1054 of 2360

INST0053
Unable to find symbol for %s-ROM file.

Action:
Severity: Info.
INST0054
SNMP trap: No
None of the installation disk has %s - ROM file

Action:
Severity: Info.
INST0055
SNMP trap: No
Current floppy disk does not have %s - ROM file

Action:
Severity: Info.
INST0056
SNMP trap: No
Cannot contact device on SCSI bus id %d.

Action:
Severity: Info.
INST0057
SNMP trap: No
Unable to read input form keyboard.

Action: Please try again.
Severity: Info.
INST0058
SNMP trap: No
Invalid input string. Length cannot be greater than %d.

Action:
Severity: Info.
INST0059
SNMP trap: No
Invalid option selected.

Action: Please select another option.
Severity: Info.
INST0060
SNMP trap: No
Incorrect disk in drive.

Action: Please insert the correct disk.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1055 of 2360

INST0061
Unable to reset IOP card, slot number %d.

Action:
Severity: Info.
INST0062
SNMP trap: No
Invalid date for leap year. Date cannot exceed 29.

Action:
Severity: Info.
INST0063
SNMP trap: No
Invalid date entered.

Action: Please enter again.
Severity: Info.
INST0064
SNMP trap: No
Invalid time entered.

Action: Please enter again.
Severity: Info.
INST0065
SNMP trap: No
Fatal. Failed to partition the hard drive.

Action:
Severity: Info.
INST0066
SNMP trap: No
Invalid year.
Action: Please enter from %d to %D.
Severity: Info.
INST0067
SNMP trap: No
Unable to create a PhysDev for hard disk.

Action:
Severity: Info.
INST0068
SNMP trap: No
Unable to create BlockDev for /u partition.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1056 of 2360

INST0069
Unable to create BlockDev for /p partition.

Action:
Severity: Info.
INST0070
SNMP trap: No
Unable to create BlockDev for /id partition.

Action:
Severity: Info.
INST0071
SNMP trap: No
Unable to open /u partition

Action:
Severity: Info.
INST0072
SNMP trap: No
Unable to initialize /u partition

Action:
Severity: Info.
INST0073
SNMP trap: No
Unable to open /p partition.

Action:
Severity: Info.
INST0074
SNMP trap: No
Unable to open /np partition.

Action:
Severity: Info.
INST0075
SNMP trap: No
Unable to open /id partition

Action:
Severity: Info.
INST0076
SNMP trap: No
Unable to initialize /id partition.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1057 of 2360

INST0077
System date is not correct.

Action: Please set it to the current date.
Severity: Info.
INST0078
SNMP trap: No
SNMP trap: No
Fail to erase file \"%s\"

Action:
Severity: Info.
INST0079
Fail to allocate memory for internal patch structure.

Action:
Severity: Info.
INST0080
SNMP trap: No
Unable to mark patched for retention

Action:
Severity: Info.
INST0081
SNMP trap: No
Same release and issue; new patches are ignored.

Action:
Severity: Info.
INST0082
SNMP trap: No
MDP package is not equipped. New patches are ignored.

Action:
Severity: Info.
INST0083
SNMP trap: No
Unable to obtain the Database's release and issue \"%s\"

Action:
Severity: Info.
INST0084
SNMP trap: No
Unable to find symbol for flash file %s

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1058 of 2360

INST0085
File context unmatched. \"%s\" : %s vs. \"%s\" : %s

Action:
Severity: Info.
INST0086
SNMP trap: No
Unable to access the card at slot %s

Action:
Severity: Info.
INST0087
SNMP trap: No
Target slot not in %d..%d range

Action:
Severity: Info.
INST0088
SNMP trap: No
Manual keycode insertion failed.

Action:
Severity: Info.
INST0089
SNMP trap: No
copy /p partition from other side failed

Action:
Severity: Info.
INST0090
SNMP trap: No
Unable to install software from CDROM to hard disk

Action:
Severity: Info.
INST0091
SNMP trap: No
Error reading CDROM file %s/%s

Action:
Severity: Info.
INST0092
SNMP trap: No
Error while trying to update direct.rec file

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1059 of 2360

INST0093
Security device ERROR detected

Action:
Severity: Info.
INST0094
SNMP trap: No
Keycode format ERROR

Action:
Severity: Info.
INST0095
SNMP trap: No
Keycode validation error

Action:
Severity: Info.
INST0096
SNMP trap: No
Cannot extract parameters from keycode

Action:
Severity: Info.
INST0097
SNMP trap: No
Invalid input to function instDiskPrompt

Action:
Severity: Info.
INST0098
SNMP trap: No
SNMP trap: No
Error copying %s to %s
Action:
Severity: Info.
INST0099
Could not locate \"%s\" f/w on hard-disk CDROM.

Action:
Severity: Info.
INST0100
SNMP trap: No
Invalid parameter passed to DBMT

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1060 of 2360

INST0102
unable to determine floppy device name.

Action:
Severity: Info.
INST0103
SNMP trap: No
Unable to determine file names for transfer

Action:
Severity: Info.
INST0104
SNMP trap: No
Unable to open floppy drive

Action:
Severity: Info.
INST0105
SNMP trap: No
Unable to create temporary database file.

Action:
Severity: Info.
INST0106
SNMP trap: No
Unable to create temporary config file.

Action:
Severity: Info.
INST0107
SNMP trap: No
Unable to transfer database to hard disk

Action:
Severity: Info.
INST0108
SNMP trap: No
Unable to append database and Config files into one file.

Action:
Severity: Info.
INST0109
SNMP trap: No
Unable to rename Config file to database file for -s option

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1061 of 2360

INST0110
Unable to restore files to original state.

Action:
Severity: Info.
INST0111
SNMP trap: No
Unable to rename all files correctly.

Action:
Severity: Info.
INST0112
SNMP trap: No
Unable to read Private Sector from hard disk.

Action:
Severity: Info.
INST0113
SNMP trap: No
Too many disks being used.

Action:
Severity: Info.
INST0114
SNMP trap: No
Incorrect floppy disk placed in drive.

Action:
Severity: Info.
INST0115
SNMP trap: No
Unable to identify record type.

Action:
Severity: Info.
INST0116
SNMP trap: No
Unable to read sector(s) from floppy disk.

Action:
Severity: Info.
INST0117
SNMP trap: No
Unable to write database file to hard disk.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1062 of 2360

INST0118
Unable to write config file to hard disk.

Action:
Severity: Info.
INST0119
SNMP trap: No
Incorrect database record count. Was %d should be %d.

Action:
Severity: Info.
INST0120
SNMP trap: No
Incorrect configuration record count. Was %d should be %d.

Action:
Severity: Info.
INST0121
SNMP trap: No
Incorrect floppy disk placed in file. Need A (1) disk.

Action:
Severity: Info.
INST0122
SNMP trap: No
unable to write %d sector (start sector %d), to device on scsi bus ID %d.
Action:
Severity: Info.
INST0123
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Invalid floppy disk

Action:
Severity: Info.
INST0124
End of track 1 not found

Action:
Severity: Info.
INST0125
End of track 3 not found

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1063 of 2360

INST0126
Unable to identify record type

Action:
Severity: Info.
INST0127
SNMP trap: No
Keycode file is corrupted. Check Keycode file

Action:
Severity: Info.
INST0128
SNMP trap: No
Unable to seek on floppy disk

Action:
Severity: Info.
INST0129
SNMP trap: No
Unable to read from floppy disk

Action:
Severity: Info.
INST0130
SNMP trap: No
Unable to seek DB on hard disk

Action:
Severity: Info.
INST0131
SNMP trap: No
Unable to seek Config on hard disk

Action:
Severity: Info.
INST0132
SNMP trap: No
Unable to read from hard disk

Action:
Severity: Info.
INST0133
SNMP trap: No
Unable to write to hard disk

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1064 of 2360

INST0134

Action:
Severity: Info.
INST0135
SNMP trap: No

Action:
Severity: Info.
INST0136
SNMP trap: No
Unknown Database format

Action:
Severity: Info.
INST0137
SNMP trap: No
Unable to read Private Sector from floppy disk

Action:
Severity: Info.
INST0138
SNMP trap: No
Unable to read %d sector (start sector %d), from device on scsi bus ID %d
Action:
Severity: Info.
INST0139
SNMP trap: No
Unable to close floppy device

Action:
Severity: Info.
INST0140
SNMP trap: No
Unable to close Database file

Action:
Severity: Info.
INST0141
SNMP trap: No
Unable to close Config file

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1065 of 2360

INST0142
Unable to rename secondary Database file to holding file

Action:
Severity: Info.
INST0143
SNMP trap: No
Unable to restore files to original state

Action:
Severity: Info.
INST0144
SNMP trap: No
Unable to rename secondary Config file to holding file

Action:
Severity: Info.
INST0145
SNMP trap: No
Unable to rename primary Database file to secondary file

Action:
Severity: Info.
INST0146
SNMP trap: No
Unable to rename primary Config file to secondary file

Action:
Severity: Info.
INST0147
SNMP trap: No
Unable to rename new Database file to primary file

Action:
Severity: Info.
INST0148
SNMP trap: No
Unable to rename new Config file to primary file

Action:
Severity: Info.
INST0149
SNMP trap: No
Unable to determine primary Database file name

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1066 of 2360

INST0150
Unable to determine secondary Database file name

Action:
Severity: Info.
INST0151
SNMP trap: No
Unable to determine holding Database file name

Action:
Severity: Info.
INST0152
SNMP trap: No
Unable to determine temporary Database file name

Action:
Severity: Info.
INST0153
SNMP trap: No
Unable to determine primary Config file name

Action:
Severity: Info.
INST0154
SNMP trap: No
Unable to determine secondary Config file name

Action:
Severity: Info.
INST0155
SNMP trap: No
Unable to determine holding Config file name

Action:
Severity: Info.
INST0156
SNMP trap: No
Unable to determine temporary Config file name

Action:
Severity: Info.
INST0157
SNMP trap: No
Unable to restore temporary Database file

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1067 of 2360

INST0158
Unable to restore primary Database file

Action:
Severity: Info.
INST0159
SNMP trap: No
Unable to restore secondary Database file

Action:
Severity: Info.
INST0160
SNMP trap: No
Unable to restore temporary Config file

Action:
Severity: Info.
INST0161
SNMP trap: No
Unable to restore primary Config file

Action:
Severity: Info.
INST0162
SNMP trap: No
Unable to restore secondary Config file

Action:
Severity: Info.
INST0165
SNMP trap: No
Unable to determine floppy size

Action:
Severity: Info.
INST0166
SNMP trap: No
Block device number %d on bus ID %d does not exist

Action: Restart installation
Severity: Critical.
INST0167
SNMP trap: No
Memory allocation problem

Action: Restart installation.
Severity: Critical.
SNMP trap: No
System Messages
Page 1068 of 2360

INST0168
Failed to copy the new keycode on hard disk

Action: Keycode must be checked.
Severity: Info.
INST0169
SNMP trap: No
Failed to replace the keycode with the new one

Action: Keycode must be checked.
Severity: Info.
INST0170
SNMP trap: No
CP type, specified by keycode, mismatches the actual CP type

Action: Keycode must be replaced.
Severity: Info.
INST0171
SNMP trap: No
Unable to configure system utility card

Action:
Severity:
INST0172
SNMP trap: No
Fatal. Failed to format the hard disk

Action:
Severity:
INST0173
SNMP trap: No
Fatal, hard disk test failed

Action: You can attempt to repartition and reinitialize the hard disk. This will
erase all files and directories on the hard disk and you must reinstall the software.
If the problem persists, you may have to replace your server unit. Please contact
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1069 of 2360
IOD: Input/Output Diagnostic (LD 37)

This program is used to diagnose faults with disk units, tape units,
teletypewriter (TTY) or Serial Data Interface (SDI) packs, used with modems
to remote TTY. It provides enable, disable, status indication and test functions
on these devices. Problems are indicated in IOD messages.
Messages
IOD0000
Program 37 identifier. No action.

Action:
Severity: Info.
IOD0001
SNMP trap: No
Invalid command.
Severity: Info.
IOD0002
SNMP trap: Yes
Severity: Info.
IOD0004
SNMP trap: Yes
Device number is out-of-range. Range is 0 to 7 or 0 to 15.

Severity: Info.
IOD0005
SNMP trap: Yes
Requested device is not defined in system.

Severity: Info.
IOD0006
SNMP trap: Yes
Interface pack failed to respond. A pack fault is indicated. Device cannot be

enabled until the fault is cleared.
Action: Check enable switch on pack. If pack still does not respond, a pack fault
is indicated. This information is also displayed on the maintenance display. Refer
to the Maintenance Display Codes Table.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1070 of 2360

IOD0007
Interface pack has a permanent interrupt. Device cannot be enabled until fault
is cleared. (Minor alarm.)
Action:
Severity: Critical.
IOD0009
SNMP trap: Yes
Disabling of active input device is not allowed.

Action: Go to different TTY or use SL-1 maintenance set.
Severity: Info.
IOD0012
SNMP trap: Yes
RW test not allowed on Mini-CDR tape.

Action:
Severity: Info.
IOD0021
SNMP trap: Yes
Illegal character was entered while tape data was running. Only END is
permitted while TEST is in progress.
Action:
Severity: Info.
IOD0040 n
SNMP trap: Yes
TTY or printer n is not emptying the output buffer. Output circuitry on pack is
faulty. The device is disabled. Probable fault is on pack in question. This
information is also displayed on the maintenance display. If fault persists after
pack is replaced, suspect:
1. Miscellaneous pack on active CPU
2. Other serial data interface
Action:
Severity: Critical.
IOD0041 n
SNMP trap: Yes
TTY n is producing incoherent or too much (over a defined threshold) input.

The pack has been disabled. Either the device is faulty or it is connected to a
very noisy data line. This information is also displayed on the maintenance
display.
With X11 Release 19 and later, I/O Port auto Lock out Recovery is operating.
This message indicates the TTY was left disabled because it had been locked
out and re-enabled three times in the last 30 minutes.
Action: Manually re-enable the port to bring it back to service.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1071 of 2360

IOD0050 n
MSI/Tape unit n is not ready.

Action: Check disk/tape cartridge for proper seating. With disk systems, try
operation again while watching the Mass Storage Interface display.
Severity: Critical.
IOD0051 e n
SNMP trap: Yes
Timeout or early warning on tape unit n before checking. Error codes (e): A =
read directory timeout B = check directory timeout C= check track 3 timeout D
= check track 4 timeout E = find last Overlay record timeout F = read EOF
(End-of-File) timeout G = erase fault W = tape initialization timeout X = position
check (tape read) timeout Y = early warning point reached Z= find record
timeout 1,2= timeout or early warning on MSI/tape unit 1 or 2 while reading.
Action:
Severity: Critical.
IOD0060 n
SNMP trap: Yes
MSI/Tape Interface pack fault for MSI/tape unit n. (Minor alarm)

Action:
Severity: Critical.
IOD0061 n
SNMP trap: Yes
Faulty track select on MSI/tape unit n. (Minor alarm)

Action:
Severity: Critical.
IOD0062 n
SNMP trap: Yes
Tape cartridge missing or defective bulb on tape unit n.

Action: Check cartridge and bulb. Check drive A and drive B. (Minor alarm)
Severity: Critical.
IOD0063 n
SNMP trap: Yes
Tape wound off end of reel of tape unit n or defective tape unit n. (Minor alarm)
Action: Check cartridge, or check disk on MSI unit n.
Severity: Critical.
IOD0064 n
SNMP trap: Yes
Interrupt fault on tape interface (TI) pack for unit n. (Minor alarm)
Action: Check cartridge, or check disk on MSI unit n.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1072 of 2360

IOD0065 n
Unable to position disk/tape correctly on MSI drive A/B or tape unit n due to
faulty tape or interrupt fault. (Minor alarm)
Action:
Severity: Critical.
IOD0066 n
SNMP trap: Yes
MSI/tape motion error detector on MSI/tape unit n malfunctioning. Minor alarm

Action:
Severity: Critical.
IOD0067 n
SNMP trap: Yes
Tape control electronics is allowing improper tape motion on tape unit n. Minor
alarm. MSI control not working (no alarm).
Action:
Severity: Critical.
IOD0069 n
SNMP trap: Yes
Incorrect tape speed or failure to detect tape position changes on tape unit n.
Possible defect in positioning of front cover.
Action: Remove cover and test cartridge (Minor alarm), or MSI timer not working
(no alarm).
Severity: Critical.
IOD0070 n
SNMP trap: Yes
Hardware on tape unit n failed to automatically stop motion at cartridge limits

(Minor alarm), or MSI timer not working (no alarm).
Action:
Severity: Critical.
IOD0071 n
SNMP trap: Yes
Bad data on disk/tape or defective cartridge in MSI/tape unit n. (Minor alarm)

Action:
Severity: Critical.
IOD0072 n
SNMP trap: Yes
Faulty track select or defective cartridge in MSI/tape unit n. (Minor alarm)

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1073 of 2360

IOD0074 n
Tape cartridge on tape unit U set to SAFE; test cannot continue. Test
automatically continues when cartridge is replaced, or MSI floppy disk B is
write protection is removed. (Minor alarm)
Action:
Severity: Critical.
IOD0075 e c n
SNMP trap: Yes
Erase or write fault on tape unit n.

Action:
Severity: Info.
IOD0076 n
SNMP trap: Yes
SI/tape unit n has problems reading data from disk/tape. (Minor alarm)
Action:
Severity: Critical.
IOD0077 n
SNMP trap: Yes
MSI/tape unit n has problems writing data on tape (Minor alarm)

Action:
Severity: Critical.
IOD0078 n
SNMP trap: Yes
Hardware fault on MSI/tape unit n cause momentary 'Not Ready' indication.

(Minor alarm)
Action:
Severity: Critical.
IOD0079 n
SNMP trap: Yes
Tape cartridge on tape unit n has bad directory (Minor alarm), or bad directory
in MSI system.
Action:
Severity: Critical.
IOD0111 n
SNMP trap: Yes
Tape unit n is disabled.(Minor alarm.) Enable tape unit.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1074 of 2360

IOD0112
Cannot perform TTY tests on PMS link.

Action:
Severity: Info.
IOD0280
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Use tape command.

Action:
Severity: Info.
IOD0281
Use MSI command.

Action:
Severity: Info.
IOD0300
No response received from System Monitor (NT8D22) after sending status

request message.
Action:
Severity: Critical.
IOD0301
SNMP trap: Yes
There are no master System Monitor (NT8D22) port defined.

Action: Use LD 17 to define the master System Monitor port.
Severity: Minor.
IOD0302
SNMP trap: Yes
SNMP trap: Yes
Invalid command.
Action:
Severity: Info.
IOD0306 x
Could not test TTY due to one of the following reasons (where x = port
number) : 1. Self test is not supported on type of TTY 2. TTY is not in the
correct state to run self test
Action: Put the TTY in the enable and operational state and run the test again.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1075 of 2360

IOD0307 x
The Meridian 1 timed out waiting for a response to the enable SDI application
message sent to the MSDL card. Where: x = port number
Action: If this error message is received twice in a row when attempting to
enable the TTY, be sure the MSDL is enabled and remains that way for the next
few minutes. If the problem still persists, disable and reenable the MSDL card.
Severity: Critical.
IOD0308 x
SNMP trap: Yes
The MSDL cannot enable the SDI application. Where: x = port number
Action: If this error message is received more than twice in a row when
attempting to enable the TTY, try using the FDL option so that the application is
re-downloaded to the card.
Severity: Critical.
IOD0309 x
SNMP trap: Yes
The SDI application in transient state. Where: x = port number.

Action: Try again.
Severity: Critical.
IOD0314
SNMP trap: Yes
That command does not apply to the Pseudo TTY (PTY).

Action:
Severity: Info.
IOD0315 x
SNMP trap: Yes
Failure to download the device setup. The device will still be enabled with the
current setup. X indicates the failure reason: 0 = fail to download due to device
data corruption 1= fail to change baud rate 2 = fail to change device setup such
as data bit, stop bit, or parity type 3 = fail to change control option
Action:
Severity: Critical.
IOD0316
SNMP trap: Yes
It is not possible to enable the TTY/PRT without first enabling the MSDL card.
Issue the ENL MSDL {x} command.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1076 of 2360

IOD0317
The MSI and Tape related command are not applicable to this machine.
Action: Use LD137 to issue any maintenance and diagnostic for IOPs and
CMDUs.
Severity: Info.
IOD0318 x
SNMP trap: Yes
TTY x was disabled due to invalid characters and will be automatically enabled
in 4 minutes.
Action:
Severity: Critical.
IOD0319 x
SNMP trap: Yes
TTY x was automatically enabled.

Action:
Severity: Minor.
IOD0320 x
SNMP trap: Yes
TTY x has been disabled 3 times, the maximum allowed, during the last 30
minutes. It will not be automatically enabled.
Action:
Severity: Critical.
IOD0321
SNMP trap: Yes
Cannot disable the TTY used to access non Meridian 1 task (PDT/VxWorks
Shell, for example).
Action:
Severity: Minor.
IOD0322
SNMP trap: Yes
Int detected: unconfig'd IO device; grp X at vaddr Y device has been H/W
disabled
Action:
Severity: Critical.
IOD0323
SNMP trap: Yes
Int detected: S/W disabled IO device; grp X at vaddr Y device has been H/W
disabled
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1077 of 2360

IOD0327 x
Overlay command cannot be executed due to one of the following conditions:

1. The port is not in the correct state for the command to be executed 2 The
port is already in the right state
Action: Check port state and try again. Where: x = port number
Severity: Minor.
IOD0328 x y z
SNMP trap: Yes
MSDL SDI target state has been changed. No action needed. Where: x = port
number, y = original target, and z = new target
Action:
Severity: Minor.
IOD0329 x y
SNMP trap: Yes
Event: Application download failed. Where: x = port number and y = failure

reason Where: 3 - maintenance in progress 4 - transmit xbuffer busy 6 - no
maintenance socket id 11 - force download not allowed 10, others - download
failed
Action: 3 - wait 6 - reconfigure port, then enable port again 4, 10, 11, others disable the MSDL card, reset it and then try again.
Severity: Critical.
IOD0331 x y z
SNMP trap: Yes
The port is disabled by the system. Where: x = port number; y = disable reason
Where: 1= enable application failed 2 = status errno 3 - primitive timeout ( z =
port state port substate if state is test) 4 - MSDL Handler failure 5- disable
indication received (z = 15 - bad rs232/422 switch setting; 16 - bad dte/dce
switch setting ; 17 - not enough memory) 6 - PSDL threshold exceeded 7 MSDL card is system disabled
Action: 1, 2, 3, 4, 6 - disable the MSDL card, reset it and then try again. 5 - {z}
= 15, 16 - check the MSDL card hardware setting. {z} = 17 - disable the MSDl
card, reset it and then try again. 7 - reset the MSDL card and then try again.
Severity: Critical.
IOD0332 x y
SNMP trap: Yes
The port is enabled but not ready. Where: x = port number and y = not ready
reason}Where: 0 - autobauding 1- await modem to be connected 2 - dtr is
down 3 - await terminal (vt220) verification
Action: 0 - enter {carriage return}'s to trigger port to be autobauded 1 - check
modem connection 2 - check cable connection 3 - no action needed
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1078 of 2360

IOD0333 x
The port is now operational; previously it is enabled but not ready. Where: x =
port number
Action:
Severity: Minor.
IOD0334 x
SNMP trap: Yes
The port is put into midnight recovery. Where: x = port number

Action: To enable port, disable it first and then enable it, or wait for midnight
recovery to occur.
Severity: Critical.
IOD0335 x
SNMP trap: Yes
Auto-recovery is complete. Where: x = port number

Action:
Severity: Minor.
IOD0336 x y z
SNMP trap: Yes
Auto-recovery in progress. Where: x = port number, y = recv attempt no - 1, 2,

or 3, and z = cause for recovery - {disable reason}
Action: Wait for auto-recovery to complete.
Severity: Minor.
IOD0339 x
SNMP trap: Yes
STA disable process failed because application says so. Where: x = STA
logical number
Action:
Severity: Minor.
IOD0340 x
SNMP trap: Yes
Overlay command cannot be executed. One of the following may have taken
place. Where:X = STA logical number 1. STA application is not in the correct
state for the command to be executed 2. STA application is already in the right
state
Action:
Severity: Minor.
IOD0341 x y z
553-3001-411
SNMP trap: Yes
STA application encounters operational errors and auto-recovery process is

activated to recover. Where:x = STA logical number y = Type of Operational
Errors 1: Fail to enable STA application 2: Status error 3: Primitive timeout 4:
MSDL Handler failure
5: STA loadware suicide
6: PSDL threshold failure
Standard 15.00
January 2006
Page 1079 of 2360

z = Reason for STA loadware suicide (for y = 5 only)
15: Wrong RS232/RS422 switch setting
16: Wrong DTE/DCE setting
17: Not enough memory
18: Fail to detect VT220
19: STA loadware layer 2 bug
Action:
Severity: Critical.
IOD0342 x
SNMP trap: Yes
STA application is put in midnight recovery. No more auto-recovery will be

attempted until midnight. Where: x = STA logical number
Action:
Severity: Critical.
IOD0343
SNMP trap: Yes
Cannot use "DIS TTY #" to disable STA administration terminal.

Action:
Severity: Minor.
IOD0344
SNMP trap: Yes
Cannot use "ENL TTY #" to enable STA administration terminal.

Action:
Severity: Minor.
IOD0345
SNMP trap: Yes
TTY self test is not allowed on STA administration terminal.

Action:
Severity: Minor.
IOD0346 x y z
SNMP trap: Yes
STA auto-recovery is in progress. Where: x= STA logical number y = Counts

for STA's attempt to recover. (If y is greater than or equal to 3, STA is put to
midnight recovery.) z = Operational Errors which cause auto-recovery
1: Fail to enable STA application
2: Status error
3: Primitive timeout
4: MSDL Handler failure
System Messages
Page 1080 of 2360

5: STA loadware suicide
6: PSDL threshold failure
7: MSDL system enabled
Action:
Severity: Critical.
IOD0347 x
SNMP trap: Yes
STA auto-recovery has been completed. Where: x = STA logical number.

Action:
Severity: Minor.
IOD0349
SNMP trap: Yes
SDI port is not configured for MTC and SCH.

Action: Either add MTC and SCH to SDI port or use another valid SDI port.
Severity: Critical.
IOD0350
SNMP trap: Yes
Point-to-Point Protocol interface is disabled.

Action: Issue the command "ENL PPP" in LD 117.
Severity: Minor.
IOD0351
SNMP trap: Yes
Active Point-to-Point Protocol session has been found.

Action: Wait until current PPP session is terminated.
Severity: Minor.
IOD0352
SNMP trap: Yes
Point-to-Point Protocol task has failed to start.

Action: Check system port for additional information regarding possible causes
of the failure.
Severity: Minor.
IOD0353
SNMP trap: Yes
Invalid PTY port. PTY port is not supported.

Action: Check to make sure your data is correct.
Severity: Info.
IOD0357
SNMP trap: Yes
Resume interrupt service for cabinet.

Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1081 of 2360

IOD0358
Stuck interrupt in cabinet. It may be caused by a damaged pack in the cabinet.

Action: Check for faulty cards in the cabinet.
Severity: Major.
IOD0359
SNMP trap: Yes
Failed to service interrupt for Cabinet. Cannot identify the device that is raising
the interrupt.
Severity: Info.
IOD0360
SNMP trap: Yes
Failed to service interrupt for Cabinet. Interrupt is masked.

Action: Check for faulty cards in that cabinet
Severity: Major.
IOD0361
SNMP trap: Yes
Unable to set event ISR for the cabinet.

Severity: Minor.
IOD0362
SNMP trap: Yes
Unable to install the CardLAN interface.

Severity: Major.
IOD0363
SNMP trap: Yes
The overloaded SDI MSDL port needs to be disabled before it can be enabled.
Action: Place the TTY in the manually disabled mode with the command DIS
TTY x. Enable the TTY with the command ENL TTY x.
Severity: Minor.
IOD0371
SNMP trap: Yes
Device locked by the Russian Call Monitoring feature. The TTY could not be
disabled or enabled.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1082 of 2360

IOD0372
LSECDR: File xx is available on expansion yy.

Where:
xx = c:/u/smp.db/dba.cdr or b:/dba.cdr
yy = 1 to 4
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1083 of 2360
ISR: Intergroup Switch and System Clock

Generator Diagnostic (LD 39)
The Intergroup Switch (IGS) and System Clock Generator (SGC) diagnostic
(LD 39) applies to Multi Group systems not equipped with Fiber Network
Fabric. The program is used to maintain Peripheral Signaling (PS), Intergroup
Switch (IGS) or System Clock Generator (SCG) cards.
Messages
ISR0000
Program identifier.
Action:
Severity: Info.
ISR0001
SNMP trap: Yes
Illegal character in command.

Action:
Severity: Info.
ISR0002
SNMP trap: Yes
Wrong number of input parameters.

Action:
Severity: Info.
ISR0003
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Illegal command.
Action:
Severity: Info.
ISR0004
Group out-of-range.
Action:
Severity: Info.
ISR0005
Warning: FDL Command is not supported on the clock controller equipped in

the system. However, the system will continue to process the enable clock
command.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1084 of 2360

ISR0006 n
The clock controllers cannot be switched because clock

controller n is software disabled.
Action: Enable the disabled pack provided it is operational.
Severity: Minor.
ISR0010
SNMP trap: Yes
Command ignored as an active input device would be disabled.

Action:
Severity: Info.
ISR0015 loop
SNMP trap: Yes
Loop specified does not respond. During ENPS command, an attempt is made
to reenable all loops associated with peripheral signaling card.
Action:
Severity: Info.
ISR0018
SNMP trap: Yes
Only one DISI IGS allowed at a time.

Action:
Severity: Info.
ISR0020
SNMP trap: Yes
Specified peripheral signaling card out-of-range.

Action:
Severity: Info.
ISR0021
SNMP trap: Yes
Specified peripheral signaling card does not respond.

Action:
Severity: Info.
ISR0022
SNMP trap: Yes
Specified peripheral signaling card already enabled.

Action:
Severity: Info.
ISR0025
SNMP trap: Yes
Cannot determine which CPU is active.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1085 of 2360

ISR0026 p
A peripheral signaling interrupt fault is present. p identifies the faulty card.

Action:
Severity: Info.
ISR0027
SNMP trap: Yes
A fault in the outgoing signaling circuitry has been detected on the peripheral
signaling card being examined.
Action:
Severity: Info.
ISR0033
SNMP trap: Yes
System clock must be switched before proceeding.

Action:
Severity: Info.
ISR0040
SNMP trap: Yes
Intergroup switch out-of-range.

Action:
Severity: Info.
ISR0042
SNMP trap: Yes
Intergroup switch is already enabled.

Action:
Severity: Info.
ISR0043
SNMP trap: Yes
DISI IGS command completed.

Action:
Severity: Info.
ISR0050
SNMP trap: Yes
System clock generator specified is out-of-range.

Action:
Severity: Info.
ISR0051
SNMP trap: Yes
SCG specified is not responding.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1086 of 2360

ISR0052
SCG specified is already enabled.

Action:
Severity: Info.
ISR0060 n
SNMP trap: Yes
SCG n cannot be switched in to replace the present clock.

Action: If clock controller, go to Input/Output guide, LD 60.
Severity: Info.
ISR0063
SNMP trap: Yes
You should wait one minute before doing another clock switch!
If you still want to switch the clock use the SCLK FRCE command.
Action:
Severity: Info.
ISR0075
SNMP trap: No
Supposed to track on secondary, but H/W is freerun.

Action:
Severity: Info.
ISR0080
SNMP trap: Yes
SL-1NT cannot use LD 39.

Action:
Severity: Info.
ISR0100
SNMP trap: Yes
An invalid error message was received from the clock controller.

Action:
Severity: Info.
ISR0101
SNMP trap: No
Superloop on the specified PS card, use LD 32 ENPS/DSPS commands.

Action:
Severity: Info.
ISR0102
SNMP trap: Yes
Loop is a Digital Trunk Interface or Primary Rate Interface.

Action: Use LD 60.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1087 of 2360

ISR0104
BRSC{-}PRI B-Ch connection is using the IGS being disabled. Cannot

complete DISI command.
Action: Use the DIS IGS command or disconnect the nail-up by disabling the
BRSC in LD 32 first.
Severity: Info.
ISR0105
SNMP trap: Yes
A TCON connection is using the IGS being disabled. Cannot complete DISI
command.
Action: Use the DIS IGS command or disconnect the TCON first.
Severity: Info.
ISR0106 G S
SNMP trap: Yes
Clock found in Group G side S is different from its address found during
system initialization. No attempt to overwrite the address found during
initialization.
Action:
Severity: Info.
ISR0107 S G
SNMP trap: Yes
More than one clock has been found in side S. The information on Group of
the extra clock(s) is provided.
Action:
Severity: Info.
ISR0108 S
SNMP trap: Yes
No clock has been found in side S.

Action:
Severity: Info.
ISR0200
SNMP trap: Yes
Cannot disable a FIJI while it is the active ring.

Action:
Severity: Info.
ISR0201
SNMP trap: Yes
Cannot reset the FIJI card when the card is not manually disabled. Selftest
cannot be performed.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1088 of 2360

ISR0202
Reset failure. Could not write to card. Selftest cannot be performed.

Action: Replace the FIJI pack.
Severity: Info.
ISR0203
SNMP trap: Yes
Cannot selftest. Card is enabled or waiting for a response.

Action:
Severity: Info.
ISR0204
SNMP trap: Yes
Cannot restore/switch rings because the active ring state is not valid.
1. There is no need to restore from Half Mode.
2. Switch only from Half Mode or from Full Mode on the other ring
Action:
Severity: Info.
ISR0205
SNMP trap: Yes
Invalid side (ring). Range is 0-1.

Action:
Severity: Info.
ISR0206
SNMP trap: Yes
FIJI card not present. Cannot read info.

Action:
Severity: Info.
ISR0207
SNMP trap: Yes
Cannot provide FIJI applicable info right now: block is updating.

Action: Wait.
Severity: Info.
ISR0208
SNMP trap: Yes
FIJI card not operational. Cannot read info.

Action: Enable FIJI pack.
Severity: Info.
ISR0210
SNMP trap: Yes
Upload of performance report failed.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1089 of 2360

ISR0211
Timeout waiting for selftest to complete.

Action: Replace the FIJI pack.
Severity: Info.
ISR0212
SNMP trap: Yes
Failure to switch/restore ring.

Action:
Severity: Info.
ISR0213
SNMP trap: Yes
Alarm operation (Stat/Enable/Disable) failure.

Action:
Severity: Info.
ISR0214
SNMP trap: Yes
Cannot manually enable card in system disabled state.

Action: Manually disable and enable the pack, and then replace the pack.
Severity: Info.
ISR0215
SNMP trap: Yes
System clock must be switched to Group 1 before a FIJI card in Group 0 can
be disabled.
Action:
Severity: Info.
ISR0216
SNMP trap: Yes
Alarm number is out of range.

Action:
Severity: Info.
ISR0217
SNMP trap: Yes
A 360 test is currently in progress on the corresponding group on the other

ring. Test cannot be performed until the other test is completed.
Action:
Severity: Info.
ISR0218
SNMP trap: Yes
Duration must be in the range of 1 to 150.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1090 of 2360

ISR0219
Ring must be put in Drive None state before this can be initiated.
Action:
Severity: Info.
ISR0220
SNMP trap: Yes
Auto Recovery must be turned off before this test can be initiated.
Action:
Severity: Info.
ISR0221
SNMP trap: Yes
FIJI card must be in the operational state in order to process this command.
Action:
Severity: Info.
ISR0222
SNMP trap: Yes
The clock should not be switched because the FIJI software has just switched
the clock.
Action:
Severity: Info.
ISR0223
SNMP trap: Yes
Test Fiji command cannot be used unless all cards in the ring are disabled first.
Action: Disable the ring.
Severity: Info.
ISR0225
SNMP trap: Yes
FIJI Rings are in survival mode. FIJI test routine cannot be completed at this
time.
Action:
Severity: Info.
ISR0226
SNMP trap: No
There are some disabled FIJI card(s) on the ring. FIJI test routine cannot be
completed at this time.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1091 of 2360

ISR0227
There are some other task running on the ring. FIJI test routine cannot be
Action:
Severity: Info.
ISR0228
SNMP trap: No
There are some major alarm(s) on the ring. FIJI test routine cannot be
Action:
Severity: Info.
ISR0232
SNMP trap: No
Starting FIJI test routine.

Action:
Severity: Info.
ISR0233
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Starting I3 test.
Action:
Severity: Info.
ISR0234
Completed I3 test.
Action:
Severity: Info.
ISR0235
Starting IL test.
Action:
Severity: Info.
ISR0236
Completed IL test.
Action:
Severity: Info.
ISR0237
Starting BKPL test.

Action:
Severity: Info.
System Messages
Page 1092 of 2360

ISR0238
Completed BKPL test.

Action:
Severity: Info.
ISR0239
SNMP trap: No
SNMP trap: No
SNMP trap: No
Starting 360 test.

Action:
Severity: Info.
ISR0240
Completed 360 test.

Action:
Severity: Info.
ISR0241
Completed FIJI test routine.

Action:
Severity: Info.
ISR0318
SNMP trap: No
Duration for link test must be in the range of 1 to 60.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1093 of 2360
ITG: Integrated IP Telephony Gateway

The ITG messages are generated from the Voice Gateway Media Card and
Signaling Server. ITG messages incorporate the severity category of the
message in the first digit of the four digit number. Message numbers beginning
with 0 do not follow this format.
1 = Critical
2 = Major
3 = Minor
4 = Warning
5 = Cleared (Info)
6 = Indeterminate (Info)
Error messages with a severity category of "Critical" are displayed on the
Voice Gateway Media Cards maintenance faceplate display in the form:
"Gxxx" or "Sxxx", where xxx is the last three digits of the ITG message. The
Signaling Server does not have a faceplate display. Alarms appear in the
Signaling Server's report log or by way of SNMP on an Alarm browser.
Messages
ITG0100
Successful bootup. All alarms cleared.

Action:
Severity: Info.
ITG0101
SNMP trap: Yes
Exit form QoS fallback. Normal operation restored.

Action:
Severity: Info.
ITG0102
SNMP trap: Yes
TLAN network interface voice port restored to normal operation.

Action:
Severity:
ITG0103
SNMP trap: Yes
ELAN network interface restored to normal operation.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1094 of 2360

ITG0104
DSP successfully reset.

Action:
Severity: Info.
ITG0105
SNMP trap: No
Exit form card fallback. Leader card restored.

Action:
Severity: info.
ITG0150
SNMP trap: Yes
D-channel (Link Layer) restored. Channels returned to service.

Action:
Severity: Info.
ITG0200
SNMP trap: Yes
Voice TLAN etwork interface buffer exceeded. Packet(s) discarded.

Action:
Severity: Minor.
ITG0201
SNMP trap: No
ELAN network interface buffer exceeded. Packet(s) discarded.

Action:
Severity: Minor.
ITG0202
SNMP trap: No
Card recovered from software reboot.

Action:
Severity: Minor.
ITG0203
SNMP trap: No
Fallback to PSTN activated. Bad network condition.

Action:
Severity: Minor.
ITG0204
SNMP trap: Yes
DSP device reset. A DSP failed to respond and was reset.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1095 of 2360

ITG0206
Invalid A07 message received. Message discarded.

Action:
Severity: Minor.
ITG0207
SNMP trap: No
Unknown H 323 message received. Message discarded/rejected.

Action:
Severity: Minor.
ITG0208
SNMP trap: No
Backup leader has been activated. Leader card not responding.

Action:
Severity: Minor.
ITG0250
SNMP trap: Yes
Invalid X12 message received. Message discarded.

Action:
Severity: Minor.
ITG0300
SNMP trap: No
Memory allocation failure. Indicates a dynamic memory allocation problem.

Action: Check the configuration.
Severity: Major.
ITG0301
SNMP trap: Yes
Channel not responding. Channel is disabled.

Action:
Severity: Major.
ITG0302
SNMP trap: Yes
DSP device failure. Operating on reduced capacity. DSP failed to reset

properly.
Action:
Severity: Major.
ITG0303
SNMP trap: Yes
DSP subsystem failure. Initiating card reboot.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 1096 of 2360

ITG0304
Cannot write to file. I/O write error.

Action:
Severity: Major.
ITG0305
SNMP trap: Yes
Cannot open configuration file. Using default settings.

Action:
Severity: Major.
ITG0306
SNMP trap: Yes
Meridian Messaging error threshold exceeded.

Action:
Severity: Major.
ITG0308
SNMP trap: No
Address translation failure. Call is released.

Action:
Severity: Major.
ITG0309
SNMP trap: Yes
Unexpected DSP channel closed. Channel is unusable.

Action:
Severity: Major.
ITG0310
SNMP trap: Yes
Can't open DSP channel.

Action:
Severity: Major.
ITG0311
SNMP trap: No
Unable to get response from Follower card.

Action: Check if the card is unplugged.
Severity: major.
ITG0312
SNMP trap: Yes
Unable to push BOOTP tab file to backup leader.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1097 of 2360

ITG0313
Keycode failed validation. Configuration file ignored.

Action:
Severity: Major.
ITG0350
SNMP trap: Yes
Gatekeeper RAS reject threshold exceeded.

Action:
Severity: Major.
ITG0351
SNMP trap: No
Cannot open Gatekeeper configuration file. Using default settings.

Action:
Severity: Major.
ITG0400
SNMP trap: No
Fatal self-test failure. Card is out of service.

Action:
Severity: Major.
ITG0401
SNMP trap: Yes
Reboot threshold exceeded. Manual intervention required.

Action:
Severity: Major.
ITG0402
SNMP trap: No
TLAN network interface failure. T-LAN layer 2 switch problem or cable

removed.
Action:
Severity: Major.
ITG0403
SNMP trap: Yes
ELAN network interface failure. ELAN layer 2 switch port problem or cable
removed.
Action:
Severity: Major.
ITG0404
SNMP trap: Yes
Cannot open address translation file. File does not exist or is corrupted.
Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 1098 of 2360

ITG0405
Keycode failed validation during bootup.

Action:
Severity: Major.
ITG0406
SNMP trap: Yes
Start-up memory allocation failure. Card reboot initiated.

Action:
Severity: Major.
ITG0407
SNMP trap: Yes
Unable to get response from leader card.

Action:
Severity: Major.
ITG0408
SNMP trap: No
Bad address translation file. Reverting to previous version (if any).

Action:
Severity: Major.
ITG0409
SNMP trap: Yes
Bad configuration file.Reverting to previous version (if any).

Action:
Severity: Major.
ITG0410
SNMP trap: Yes
Remote leader not responding.

Action:
Severity: Major.
ITG0411
SNMP trap: Yes
Failed to start UDP server client for intercard messaging. Card is in Fallback.
Action:
Severity: Major.
ITG0412
SNMP trap: Yes
Failed to start UDP client for intercard messaging. Card is in Fallback.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1099 of 2360

ITG0413
Failed to register with Leader card. Defaulting to Fallback mode.

Action:
Severity: Major.
ITG0414
SNMP trap: Yes
No response from Leader card.

Action:
Severity: Major.
ITG0415
SNMP trap: Yes
Task spawn failed. Attempting to reboot.

Action:
Severity: Major.
ITG0416
SNMP trap: Yes
Failed to start QOS/Network Probing Timer.

Action:
Severity: Major.
ITG0417
SNMP trap: Yes
Failed to send Fallback update to followers.

Action:
Severity: Major.
ITG0418
SNMP trap: Yes
H-323 stack failed to initialize.

Action:
Severity: Major.
ITG0450
SNMP trap: Yes
D-channel loss of signal. Associated channels busied out.

Action:
Severity: Major.
ITG0451
SNMP trap: Yes
D-channel hardware failure. Associated channels busied out.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 1100 of 2360

ITG0452
Meridian-1 messaging failure. Unable to process calls.

Action:
Severity: Major.
ITG0453
SNMP trap: No
Cannot open Gateway DN file.

Action:
Severity: Major.
ITG0454
SNMP trap: No
Cannot open Gatekeeper password file.

Action:
Severity: Major.
ITG0455
SNMP trap: No
Bad Gatekeeper configuration file. Reverting to previous version, if any.

Action:
Severity: Major.
ITG0456
SNMP trap: No
Incorrect Gateway password. Calls to/from Gateway rejected by the

Gatekeeper.
Action:
Severity: Major.
ITG1000
SNMP trap: No
Card initialized, all alarms cleared.

Action: 1. Informational message indicates successful operation, such as
initialization completion. If this operation is not expected, continue with the
following process steps:
2. Log into device and capture maintenance report log (if possible) and send the
text to Nortel support staff via email.
3. Press the Reset button on the device to restart the software. (If possible wait
for a period of low traffic to minimize risk).
4. If the alarm occurs again, install a replacement hardware device and send the
failing device to Nortel for further analysis.
5. If the alarm continues after replacement hardware has been install, contact
Nortel for assistance.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1101 of 2360

ITG1001
Task spawn failure: <taskName>.

Action: 1. Potential data configuration error. Refer to comment for each alarm.
2. If the configuration appears to be correct, continue with the following process
steps:
Severity: Critical.
ITG1002
SNMP trap: Yes
Memory allocation failure.

Action: 1. Log into device and capture maintenance report log (if possible) and
send the text to Nortel support staff via email. 2. Press the Reset button on the
device to restart the software. (If possible wait for a period of low traffic to
minimize risk). 3. If the alarm occurs again, install a replacement hardware device
and send the failing device to Nortel for further analysis. 4. If the alarm continues
after replacement hardware has been install, contact Nortel for assistance.
Severity: Critical.
ITG1003
SNMP trap: Yes
File IO error: <fileName> <opName> <fd> <errno> <errtext>.

Severity: Critical.
ITG1004
SNMP trap: Yes
Network IO error: <opName> <fd> <errno> <errtext>.

System Messages
Page 1102 of 2360

Severity: Critical.
ITG1005
SNMP trap: Yes
Message queue error: <opName> <fd> <errno> <errtext>.

Severity: Critical.
ITG1006
SNMP trap: Yes
Unexpected state encountered: <fileName> <lineNumber> <state>.

Action: 1. Alarm may indicate random occurrence that is not service impacting;
note occurrence time and date for further follow-up. If any service-impacting
problems occur at the same time, further analysis is required immediately. 2. If
alarm persists, log into device and capture maintenance report log (if possible)
and send the text to Nortel support staff via email. Follow any steps described
above for the specific alarm.
Severity: Critical.
ITG1007
SNMP trap: Yes
Unexpected message type: <fileName> <lineNumber> <msgType>.

Severity: Critical.
ITG1008
SNMP trap: Yes
Unexpected null pointer: <fileName> <lineNumber> <pointerName>.

following process steps: 2. Log into device and capture maintenance report log (if
possible) and send the text to Nortel support staff via email. Follow any steps
described above for the specific alarm.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1103 of 2360

ITG1009
Invalid data block: <fileName> <lineNumber> <blockName>.

Severity: Critical.
ITG1010
SNMP trap: Yes
Unable to locate data block: <fileName> <lineNumber> <blockName>.

Severity: Critical.
ITG1011
SNMP trap: Yes
File transfer error: <opName> <fileName> <hostName>.

steps:
Severity: Critical.
ITG1012
SNMP trap: Yes
Module initialization failure: <moduleName>.

System Messages
Page 1104 of 2360

Severity: Critical.
ITG1013
SNMP trap: Yes
Network interface receive buffer unavailable, packet(s) discarded.

Severity: Critical.
ITG1014
SNMP trap: Yes
Network interface carrier: <ifName> <carrierState>.

Severity: Critical.
ITG1015
SNMP trap: Yes
Network interface device failure: <ifName>.

Severity: Critical.
ITG1016
SNMP trap: Yes
ELAN network interface device failure.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1105 of 2360

ITG1017
Invalid or unknown SSD message: <ssdType> <tn> <msg>.

Severity: Critical.
ITG1018
SNMP trap: Yes
Invalid or unknown X12 SSD message <tn> <msg>.

Action:
Severity: Critical.
ITG1019
SNMP trap: Yes
DSP channel open failure: <channelNumber>.

Severity: Critical.
ITG1020
SNMP trap: Yes
Configuration error: <configFile> <configVar> <configValue>.

2. If the configuration appears to be correct, follow alternate corrective action
procedure specified, or contact Nortel.
Severity: Critical.
ITG1021
SNMP trap: Yes
DSP successfully reset: <dspNumber>.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 1106 of 2360

ITG1022
DSP channel not responding: <channelNumber>.

Severity: Critical.
ITG1023
SNMP trap: Yes
DSP device failure: <dspNumber> <errno> <errtext>.

Severity: Critical.
ITG1024
SNMP trap: Yes
DSP failure <dsp> <errno> <errtext>.

Action:
Severity: Critical.
ITG1025
SNMP trap: Yes
DSP download: <reason> <dspNumber>.

Severity: Critical.
ITG1026
SNMP trap: Yes
DSP download retry succeeded <dsp>.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1107 of 2360

ITG1027
DSP memory test:<reason> <dspNumber>.

Severity: Critical.
ITG1028
SNMP trap: Yes
Voice packet loss: <channelNumber> <percentagePacketLoss> <rx/tx>

<DestAddress>.
Action: 1. Network-related issues may have caused this alarm. Further analysis
is required as described below.
Severity: Critical.
ITG1029
SNMP trap: Yes
Error in DSP task: <fileName> <lineNumber> <errno> <errtext>.

Severity: Critical.
ITG1030
SNMP trap: Yes
Allocation failure in DSP memory pool.

Severity: Critical.
ITG1031
SNMP trap: Yes
Invalid codec number: <codecNumber>.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 1108 of 2360

ITG1032
Attempt to open a DSP that is already open: <channelNumber>.

Severity: Critical.
ITG1033
SNMP trap: Yes
Failed to send data to DSP channel: <channelNumber>.

Severity: Critical.
ITG1034
SNMP trap: Yes
DSP channel unexpectedly closed: <channelNumber>.

Severity: Critical.
ITG1035
SNMP trap: Yes
Encountered an unexpected open DSP channel, closed it: <channelNumber>.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1109 of 2360

ITG1036
Call server communication link: <call Server IP> <up/down>.

Action: Network-related issues (cable or ELAN IP problem) may have caused
this alarm. Further analysis is required as described below.
Severity: Critical.
ITG1037
SNMP trap: Yes
Wrong image download into the card. Target Process Type = <processType>.
Severity: Critical.
ITG1038
SNMP trap: Yes
IPL shell login protect: login <enabled/lock>.

Severity: Critical.
ITG1039
SNMP trap: Yes
Bad DSP channel <tcid>.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 1110 of 2360

ITG1040
Last Reset Reason: <resetReason>.

Severity: Critical.
ITG1041
SNMP trap: Yes
F/W file(s) not received but internet phones have registered. May have mixed
F/W versions across phones. When F/W file(s) received, internet phones will
automatically be updated.
Action:
Severity: Critical.
ITG1042
SNMP trap: Yes
Insufficient flash drive space to store F/W file.

2. If the configuration appears to be correct, may need to remove files from flash
drive or contact Nortel.
Severity: Critical.
ITG2000
SNMP trap: Yes

Severity: Major.
ITG2001
SNMP trap: Yes

steps:
553-3001-411
Standard 15.00
January 2006
Page 1111 of 2360

Severity: Major.
ITG2002
SNMP trap: Yes

Severity: Major.
ITG2003
SNMP trap: Yes

Severity: Major.
ITG2004
SNMP trap: Yes

Severity: Major.
SNMP trap: Yes
System Messages
Page 1112 of 2360

ITG2005

Severity: Major.
ITG2006
SNMP trap: Yes

Severity: Major.
ITG2007
SNMP trap: Yes

Severity: Major.
ITG2008
SNMP trap: Yes

Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1113 of 2360

ITG2009

Severity: Major.
ITG2010
SNMP trap: Yes

Severity: Major.
ITG2011
SNMP trap: Yes

steps:
Severity: Major.
ITG2012
SNMP trap: Yes

System Messages
Page 1114 of 2360

Severity: Major.
ITG2013
SNMP trap: Yes

Severity: Major.
ITG2014
SNMP trap: Yes

Severity: Major.
ITG2015
SNMP trap: Yes

Severity: Major.
ITG2016
SNMP trap: Yes

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1115 of 2360

ITG2017

Severity: Major.
ITG2018
SNMP trap: Yes

Action:
Severity: Major.
ITG2019
SNMP trap: Yes

Severity: Major.
ITG2020
SNMP trap: Yes

Severity: Major.
ITG2021
SNMP trap: Yes

Severity: Major.
SNMP trap: Yes
System Messages
Page 1116 of 2360

ITG2022

Severity: Major.
ITG2023
SNMP trap: Yes

Severity: Major.
ITG2024
SNMP trap: Yes

Action:
Severity: Major.
ITG2025
SNMP trap: Yes

Severity: Major.
ITG2026
SNMP trap: Yes

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1117 of 2360

ITG2027

Severity: Major.
ITG2028
SNMP trap: Yes

<DestAddress>.
Severity: Major.
ITG2029
SNMP trap: Yes

Severity: Major.
ITG2030
SNMP trap: Yes

Severity: Major.
ITG2031
SNMP trap: Yes

Severity: Major.
SNMP trap: Yes
System Messages
Page 1118 of 2360

ITG2032

Severity: Major.
ITG2033
SNMP trap: Yes

Severity: Major.
ITG2034
SNMP trap: Yes

Severity: Major.
ITG2035
SNMP trap: Yes

Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1119 of 2360

ITG2036

Action: Network-related issues (cable or ELAN network interface IP address
problem) may have caused this alarm. Further analysis is required as described
below.
Severity: Major.
ITG2037
SNMP trap: Yes
Severity: Major.
ITG2038
SNMP trap: Yes

Severity: Major.
ITG2039
SNMP trap: Yes

Severity: Major.
SNMP trap: Yes
System Messages
Page 1120 of 2360

ITG2040

Severity: Major.
ITG2041
SNMP trap: Yes
Action:
Severity: Major.
ITG2042
SNMP trap: Yes

Severity: Major.
ITG2047
SNMP trap: Yes
Data corruption,please restore the database

Action:
Severity: Major.
ITG2049
SNMP trap: Yes
Internal web server error, reason<num id>

Action:
Severity: Major.
ITG2061
SNMP trap: Yes
There has been a switch over of the SIP Redirect/Proxy Server.

Action: Check the status of SIP Redirect/Proxy Server in order to determine the
cause of the switch over.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1121 of 2360

ITG2064
Internal DB error, Specific info.

Action: Restart the server, restore the database, and call Nortel technical
support group.
Severity: Major.
ITG2106
SNMP trap: Yes
D-Channel failure.
Severity: Major.
ITG2107
SNMP trap: Yes
Proxy Server / Redirect Server unreachable.

Severity: Major.
ITG2108
SNMP trap: Yes
Call Server not at the required minimum release.

Action: Upgrade the Call Server to the minimum required release.
Severity: Major.
ITG3000
SNMP trap: Yes

Severity: Minor.
ITG3001
SNMP trap: Yes

steps:
System Messages
Page 1122 of 2360

Severity: Minor.
ITG3002
SNMP trap: Yes

Severity: Minor.
ITG3003
SNMP trap: Yes

Severity: Minor.
ITG3004
SNMP trap: Yes

Severity: Minor.
ITG3005
SNMP trap: Yes

553-3001-411
Standard 15.00
January 2006
Page 1123 of 2360

Severity: Minor.
ITG3006
SNMP trap: Yes

Severity: Minor.
ITG3007
SNMP trap: Yes

Severity: Minor.
ITG3008
SNMP trap: Yes

Severity: Minor.
ITG3009
SNMP trap: Yes

Severity: Minor.
SNMP trap: Yes
System Messages
Page 1124 of 2360

ITG3010

Severity: Minor.
ITG3011
SNMP trap: Yes

steps:
Severity: Minor.
ITG3012
SNMP trap: Yes

Severity: Minor.
ITG3013
SNMP trap: Yes

553-3001-411
Standard 15.00
January 2006
Page 1125 of 2360

Severity: Minor.
ITG3014
SNMP trap: Yes

Severity: Minor.
ITG3015
SNMP trap: Yes

Severity: Minor.
ITG3016
SNMP trap: Yes

Action:
Severity: Minor.
ITG3017
SNMP trap: Yes

Severity: Minor.
SNMP trap: Yes
System Messages
Page 1126 of 2360

ITG3018

Action:
Severity: Minor.
ITG3019
SNMP trap: Yes

Severity: Minor.
ITG3020
SNMP trap: Yes

Severity: Minor.
ITG3021
SNMP trap: Yes

Severity: Minor.
ITG3022
SNMP trap: Yes

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1127 of 2360

ITG3023

Severity: Minor.
ITG3024
SNMP trap: Yes

Action:
Severity: Minor.
ITG3025
SNMP trap: Yes

Severity: Minor.
ITG3026
SNMP trap: Yes

Action:
Severity: Minor.
ITG3027
SNMP trap: Yes

Severity: Minor.
SNMP trap: Yes
System Messages
Page 1128 of 2360

ITG3028

<DestAddress>.
Severity: Minor.
ITG3029
SNMP trap: Yes

Severity: Minor.
ITG3030
SNMP trap: Yes

Severity: Minor.
ITG3031
SNMP trap: Yes

Severity: Minor.
ITG3032
SNMP trap: Yes

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1129 of 2360

ITG3033

Severity: Minor.
ITG3034
SNMP trap: Yes

Severity: Minor.
ITG3035
SNMP trap: Yes

Severity: Minor.
ITG3036
SNMP trap: Yes

below.
System Messages
Page 1130 of 2360

Severity: Minor.
ITG3037
SNMP trap: Yes
Severity: Minor.
ITG3038
SNMP trap: Yes

Severity: Minor.
ITG3039
SNMP trap: Yes

Severity: Minor.
ITG3040
SNMP trap: Yes

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1131 of 2360

ITG3041
Action:
Severity: Minor.
ITG3042
SNMP trap: Yes

Severity: Minor.
ITG3046
SNMP trap: Yes
Peer <IP addr of the peer> unreachable

Action:
Severity: Minor.
ITG3048
SNMP trap: Yes
Traffic overload, some logs will be lost

Action:
Severity: Minor.
ITG3050
SNMP trap: Yes
Not enough file descriptors

Action:
Severity: Minor.
ITG3051
SNMP trap: Yes
User<TN> locked out due to possible passwork guessing

Action:
Severity: Minor.
ITG3053
SNMP trap: Yes
Internet telephone %s:%d TN %s behind symmetric NAT. Blocked from

registering to call server.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1132 of 2360

ITG3054
Internet telephone %s:%d TN %s: RTCP signaling %s. (where %s is

"unavailable" or "OK")
Action:
Severity: Minor.
ITG3055
SNMP trap: Yes
Echo Server 1 %s:%d did not respond to internet phone %s TN %s. Cannot
determine if it is behind a NAT or resolve RTCP mapping; internet phone is
registered with CS.
Action:
Severity: Minor.
ITG3056
SNMP trap: Yes
Echo Server 2 %s:%d did not respond to internet phone %s TN %s. Cannot
determine if internet phone is behind a symmetric NAT; internet phone is
registered with CS.
Action:
Severity: Minor.
ITG3057
SNMP trap: Yes
Internet phone %s:%d TN %s is behind a NAT device but has F/W that does
not support NAT. It may have media path problems.
Action:
Severity: Minor.
ITG3111
SNMP trap: Yes
The length of the correlation id in the SIP INVITE message has exceeded the
maximum allowed length of 512 characters.
Action: Please limit the length to 512 characters to avoid discrepancies in billing.
Severity: Minor.
ITG4000
SNMP trap: Yes

553-3001-411
Standard 15.00
January 2006
Page 1133 of 2360

Severity: Warning.
ITG4001
SNMP trap: Yes

steps:
Severity: Warning.
ITG4002
SNMP trap: Yes

Severity: Warning.
ITG4003
SNMP trap: Yes

Severity: Warning.
SNMP trap: Yes
System Messages
Page 1134 of 2360

ITG4004

Severity: Warning.
ITG4005
SNMP trap: Yes

Severity: Warning.
ITG4006
SNMP trap: Yes

Severity: Warning.
ITG4007
SNMP trap: Yes

Severity: Warning.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1135 of 2360

ITG4008

Severity: Warning.
ITG4009
SNMP trap: Yes

Severity: Warning.
ITG4010
SNMP trap: Yes

Severity: Warning.
ITG4011
SNMP trap: Yes

steps:
Severity: Warning.
SNMP trap: Yes
System Messages
Page 1136 of 2360

ITG4012

Severity: Warning.
ITG4013
SNMP trap: Yes

Severity: Warning.
ITG4014
SNMP trap: Yes

Severity: Warning.
ITG4015
SNMP trap: Yes

Severity: Warning.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1137 of 2360

ITG4016

Action:
Severity: Warning.
ITG4017
SNMP trap: Yes

Severity: Warning.
ITG4018
SNMP trap: Yes

Action:
Severity: Warning.
ITG4019
SNMP trap: Yes

Severity: Warning.
ITG4020
SNMP trap: Yes

Severity: Warning.
SNMP trap: Yes
System Messages
Page 1138 of 2360

ITG4021

Severity: Warning.
ITG4022
SNMP trap: Yes

Severity: Warning.
ITG4023
SNMP trap: Yes

Severity: Warning.
ITG4024
SNMP trap: Yes

Action:
Severity: Warning.
ITG4025
SNMP trap: Yes

Severity: Warning.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1139 of 2360

ITG4026

Action:
Severity: Warning.
ITG4027
SNMP trap: Yes

Severity: Warning.
ITG4029
SNMP trap: Yes

Severity: Warning.
ITG4030
SNMP trap: Yes

Severity: Warning.
ITG4031
SNMP trap: Yes

Severity: Warning.
SNMP trap: Yes
System Messages
Page 1140 of 2360

ITG4032

Severity: Warning.
ITG4033
SNMP trap: Yes

Severity: Warning.
ITG4034
SNMP trap: Yes

Severity: Warning.
ITG4035
SNMP trap: Yes

Severity: Warning.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1141 of 2360

ITG4036

below.
Severity: Warning.
ITG4037
SNMP trap: Yes
Severity: Warning.
ITG4038
SNMP trap: Yes

Severity: Warning.
ITG4039
SNMP trap: Yes

Severity: Warning.
SNMP trap: Yes
System Messages
Page 1142 of 2360

ITG4040

Severity: Warning.
ITG4041
SNMP trap: Yes
Action:
Severity: Warning.
ITG4042
SNMP trap: Yes

Severity: Warning.
ITG4045
SNMP trap: Yes
Latest election has changed the LTPS master of node <node ID> to <master's
TLAN network interface IP addr>.
Action:
Severity: Warning.
ITG4052
SNMP trap: Yes
SIP Message made too many hops through network. Source of the problem:
xx.xx.xx.xx see RFC 3261. The client/Endpoint needs to increase the max hop
number.
Action:
Severity: Warning.
ITG4065
SNMP trap: Yes
Endpoint name/IP registered.

Action:
Severity: Warning.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1143 of 2360

ITG4109 <Protocol> <Protocol> Channels exceeded the limit (where protocol is H.323 or SIP).
Action: Refer to NTPs for Virtual Trunk limits.
Severity: Warning.
SNMP trap: Yes
ITG4110 <Application> <Application> is not enabled (where application is H.323 or SIP).

Severity: Warning.
ITG5000
SNMP trap: Yes

Severity: Cleared.
ITG5001
SNMP trap: Yes

steps:
Severity: Cleared.
SNMP trap: Yes
System Messages
Page 1144 of 2360

ITG5002

Severity: Cleared.
ITG5003
SNMP trap: Yes

Severity: Cleared.
ITG5004
SNMP trap: Yes

Severity: Cleared.
ITG5005
SNMP trap: Yes

Severity: Cleared.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1145 of 2360

ITG5006

Severity: Cleared.
ITG5007
SNMP trap: Yes

Severity: Cleared.
ITG5008
SNMP trap: Yes

Severity: Cleared.
ITG5009
SNMP trap: Yes

Severity: Cleared.
SNMP trap: Yes
System Messages
Page 1146 of 2360

ITG5010

Severity: Cleared.
ITG5011
SNMP trap: Yes

steps:
Severity: Cleared.
ITG5012
SNMP trap: Yes

Severity: Cleared.
ITG5013
SNMP trap: Yes

553-3001-411
Standard 15.00
January 2006
Page 1147 of 2360

Severity: Cleared.
ITG5014
SNMP trap: Yes

Severity: Cleared.
ITG5015
SNMP trap: Yes

Severity: Cleared.
ITG5016
SNMP trap: Yes

Action:
Severity: Cleared.
ITG5017
SNMP trap: Yes

Severity: Cleared.
SNMP trap: Yes
System Messages
Page 1148 of 2360

ITG5018

Action:
Severity: Cleared.
ITG5019
SNMP trap: Yes

Severity: Cleared.
ITG5020
SNMP trap: Yes

Severity: Cleared.
ITG5021
SNMP trap: Yes

Severity: Cleared.
ITG5022
SNMP trap: Yes

Severity: Cleared.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1149 of 2360

ITG5023

Severity: Cleared.
ITG5024
SNMP trap: Yes

Action:
Severity: Cleared.
ITG5025
SNMP trap: Yes

Severity: Cleared.
ITG5026
SNMP trap: Yes

Action:
Severity: Cleared.
ITG5027
SNMP trap: Yes

Severity: Cleared.
SNMP trap: Yes
System Messages
Page 1150 of 2360

ITG5029

Severity: Cleared.
ITG5030
SNMP trap: Yes

Severity: Cleared.
ITG5031
SNMP trap: Yes

Severity: Cleared.
ITG5032
SNMP trap: Yes

Severity: Cleared.
ITG5033
SNMP trap: Yes

553-3001-411
Standard 15.00
January 2006
Page 1151 of 2360

Severity: Cleared.
ITG5034
SNMP trap: Yes

Severity: Cleared.
ITG5035
SNMP trap: Yes

Severity: Cleared.
ITG5036
SNMP trap: Yes

below.
Severity: Cleared.
SNMP trap: Yes
System Messages
Page 1152 of 2360

ITG5037
Severity: Cleared.
ITG5038
SNMP trap: Yes

Severity: Cleared.
ITG5039
SNMP trap: Yes

Severity: Cleared.
ITG5040
SNMP trap: Yes

Severity: Cleared.
ITG5041
SNMP trap: Yes
Action:
Severity: Cleared.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1153 of 2360

ITG5042

Severity: Cleared.
ITG5046
SNMP trap: Yes
Peer <IP address> is back online.

Action:
Severity: Cleared.
ITG6000
SNMP trap: Yes

Severity: Indeterminate. Critical to Monitor: No.
ITG6001
SNMP trap: Yes

steps:
SNMP trap: Yes
System Messages
Page 1154 of 2360

ITG6002

ITG6003
SNMP trap: Yes

ITG6004
SNMP trap: Yes

ITG6005
SNMP trap: Yes

553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1155 of 2360

ITG6006

ITG6007
SNMP trap: Yes

ITG6008
SNMP trap: Yes

ITG6009
SNMP trap: Yes

SNMP trap: Yes
System Messages
Page 1156 of 2360

ITG6010

ITG6011
SNMP trap: Yes

steps:
ITG6012
SNMP trap: Yes

ITG6013
SNMP trap: Yes

553-3001-411
Standard 15.00
January 2006
Page 1157 of 2360

ITG6014
SNMP trap: Yes

ITG6015
SNMP trap: Yes
Network interface failure: <ifName>.

ITG6016
SNMP trap: Yes
ELAN network interface failure.

Action:
ITG6017
SNMP trap: Yes

SNMP trap: Yes
System Messages
Page 1158 of 2360

ITG6018

Action:
ITG6019
SNMP trap: Yes

ITG6020
SNMP trap: Yes

ITG6021
SNMP trap: Yes

ITG6022
SNMP trap: Yes

553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1159 of 2360

ITG6023

ITG6024
SNMP trap: Yes

Action:
ITG6025
SNMP trap: Yes

ITG6026
SNMP trap: Yes

Action:
ITG6027
SNMP trap: Yes

SNMP trap: Yes
System Messages
Page 1160 of 2360

ITG6028

<DestAddress>.
ITG6029
SNMP trap: Yes

ITG6030
SNMP trap: Yes

ITG6031
SNMP trap: Yes

ITG6032
SNMP trap: Yes

553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1161 of 2360

ITG6033

ITG6034
SNMP trap: Yes

ITG6035
SNMP trap: Yes

ITG6036
SNMP trap: Yes

below.
System Messages
Page 1162 of 2360

ITG6037
SNMP trap: Yes
ITG6038
SNMP trap: Yes

ITG6039
SNMP trap: Yes

ITG6040
SNMP trap: Yes

553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1163 of 2360

ITG6041
Action:
ITG6042
SNMP trap: Yes

SNMP trap: Yes
System Messages
Page 1164 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1165 of 2360
ITS: Internet IP Telephony Server

The ITS messages are generated from the Internet Telephone, which are
reported through the Signaling Server. ITS messages incorporate the severity
category of the message in the first digit of the four digit number. Message
numbers beginning with 0 do not follow this format.
1 = Critical
2 = Major
3 = Minor
4 = Warning
5 = Cleared (Info)
6 = Indeterminate (Info)
Error messages with a severity category of "Critical" are displayed on the
Voice Gateway Media Cards maintenance faceplate display in the form:
"Gxxx" or "Sxxx", where xxx is the last three digits of the ITS message. The
Signaling Server does not have a faceplate display. Alarms appear in the
Signaling Server's report log or by way of SNMP on an Alarm browser.
Messages
ITS1000
VTI function call timed out.

Severity: Critical.
ITS1001
SNMP trap: No
Failed to register terminal with call server: <terminalIP> <terminalHWID>

<terminalTN> <errno> <errtext>.
Action: 1. Potential data configuration error. Ensure that the terminal id (TN) is
configured on the Call Server. Refer to comment for each alarm.
2. If the configuration appears to be correct, follow process steps below or contact
Nortel.
3. Alarm may indicate random occurrence that is not service impacting; note
occurrence time and date for further follow-up. If any service-impacting problems
occur at the same time, further analysis is required immediately.
System Messages
Page 1166 of 2360

4. If alarm persists, log into device and capture maintenance report log (if
Severity: Critical.
ITS1002
SNMP trap: No
Connect service activation: <reason>.

Severity: Critical.
ITS1003
SNMP trap: No
Duplicate node manager detected: <node> <nodeIP> <duplicateIP>.

Severity: Critical.
ITS1004
SNMP trap: No
Terminal has invalid node ID: <node> <terminalIP> <terminalHWID>.

Severity: Critical.
ITS1005
SNMP trap: No
Terminals node ID/TN configuration is corrupted: <terminalIP>

<terminalHWID>.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1167 of 2360

ITS1006
Received corrupted UNIStim message: <terminalIP> <terminalHWID>

<msg>.
Severity: Critical.
ITS1007
SNMP trap: No
Received unknown UNIStim message: <terminalIP> <terminalHWID> <msg>

Severity: Critical.
ITS1008
SNMP trap: No
Terminal connection status: <terminalIP> <ok/lost>.

Severity: Critical.
ITS1009
SNMP trap: No
Call server communication link: <Call Server IP> <up/down>.

Action: Network-related issues may have caused this alarm. Further analysis is
required as described below. 1. Log into device and capture maintenance report
log (if possible) and send the text to Nortel support staff via email. 2. Press the
Reset button on the device to restart the software. (If possible wait for a period of
low traffic to minimize risk). 3. If the alarm occurs again, install a replacement
hardware device and send the failing device to Nortel for further analysis. 4. If the
alarm continues after replacement hardware has been install, contact Nortel for
assistance.
Severity: Critical.
SNMP trap: No
System Messages
Page 1168 of 2360

ITS1010
Terminal does not support configured codec: <terminalIP> <codec>

Severity: Critical.
ITS1011
SNMP trap: No
Communication link to M1 is down.

Action:
Severity: Critical.
ITS1012
SNMP trap: No
Password check failed three times during Branch User Config: <terminalIP>
Action: Wait for the set to unlock automatically in one hour, unlock the set with
the IPL CLI command clearLockout, or power cycle the set.
Severity: Critical.
ITS2000
SNMP trap: No
VTI function call timeout.

Severity: Major.
ITS2001
SNMP trap: No

Nortel.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1169 of 2360

ITS2002

Severity: Major.
ITS2003
SNMP trap: No

Severity: Major.
ITS2004
SNMP trap: No

Severity: Major.
ITS2005
SNMP trap: No

<terminalHWID>.
Severity: Major.
ITS2006
SNMP trap: No

<msg>.
System Messages
Page 1170 of 2360

Severity: Major.
ITS2007
SNMP trap: No

Severity: Major.
ITS2008
SNMP trap: No

Severity: Major.
ITS2009
SNMP trap: No

assistance.
Severity: Major.
ITS2010
SNMP trap: No

Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1171 of 2360

ITS2011

Action:
Severity: Major.
ITS2012
SNMP trap: No
Severity: Major.
ITS3000
SNMP trap: No

Severity: Minor.
ITS3001
SNMP trap: No

Nortel.
Severity: Minor.
SNMP trap: No
System Messages
Page 1172 of 2360

ITS3002

Severity: Minor.
ITS3003
SNMP trap: No

Severity: Minor.
ITS3004
SNMP trap: No

Severity: Minor.
ITS3005
SNMP trap: No

<terminalHWID>.
Severity: Minor.
ITS3006
SNMP trap: No

<msg>.
553-3001-411
Standard 15.00
January 2006
Page 1173 of 2360

Severity: Minor.
ITS3007
SNMP trap: No

Severity: Minor.
ITS3008
SNMP trap: No

Severity: Minor.
ITS3009
SNMP trap: No

assistance.
Severity: Minor.
ITS3010
SNMP trap: No

Severity: Minor.
SNMP trap: No
System Messages
Page 1174 of 2360

ITS3011

Action:
Severity: Minor.
ITS3012
SNMP trap: No
Severity: Minor.
ITS4000
SNMP trap: No

Severity: Warning.
ITS4001
SNMP trap: No

Nortel.
Severity: Warning.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1175 of 2360

ITS4002

Severity: Warning.
ITS4003
SNMP trap: No

Severity: Warning.
ITS4004
SNMP trap: No

Severity: Warning.
ITS4005
SNMP trap: No

<terminalHWID>.
Severity: Warning.
ITS4006
SNMP trap: No

<msg>.
System Messages
Page 1176 of 2360

Severity: Warning.
ITS4007
SNMP trap: No

Severity: Warning.
ITS4008
SNMP trap: No

Severity: Warning.
ITS4009
SNMP trap: No

assistance.
Severity: Warning.
ITS4010
SNMP trap: No

Severity: Warning.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1177 of 2360

ITS4011

Action:
Severity: Warning.
ITS4012
SNMP trap: No
Severity: Warning.
ITS5000
SNMP trap: No

Severity: Cleared.
ITS5001
SNMP trap: No

Nortel.
Severity: Cleared.
SNMP trap: No
System Messages
Page 1178 of 2360

ITS5002

Severity: Cleared.
ITS5003
SNMP trap: No

Severity: Cleared.
ITS5004
SNMP trap: No

Severity: Cleared.
ITS5005
SNMP trap: No

<terminalHWID>.
Severity: Cleared.
ITS5006
SNMP trap: No

<msg>.
553-3001-411
Standard 15.00
January 2006
Page 1179 of 2360

Severity: Cleared.
ITS5007
SNMP trap: No

Severity: Cleared.
ITS5008
SNMP trap: No

Severity: Cleared.
ITS5009
SNMP trap: No

assistance.
Severity: Cleared.
ITS5010
SNMP trap: No

Severity: Cleared.
SNMP trap: No
System Messages
Page 1180 of 2360

ITS5011

Action:
Severity: Cleared.
ITS5012
SNMP trap: No
Severity: Cleared.
ITS6000
SNMP trap: No

ITS6001
SNMP trap: No

Nortel.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1181 of 2360

ITS6002

ITS6003
SNMP trap: No

ITS6004
SNMP trap: No

ITS6005
SNMP trap: No

<terminalHWID>.
ITS6006
SNMP trap: No

<msg>.
System Messages
Page 1182 of 2360

ITS6007
SNMP trap: No

ITS6008
SNMP trap: No

ITS6009
SNMP trap: No

assistance.
ITS6010
SNMP trap: No

553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1183 of 2360

ITS6011

Action:
Severity: Info.
ITS6012
SNMP trap: No
Severity: Info.
SNMP trap: No
System Messages
Page 1184 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1185 of 2360
LIS: Location Information Services

LIS provides location information for IP devices.
Messages
System Messages
Page 1186 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1187 of 2360
LNK: Link Diagnostic (LD 48)

The Link Diagnostic program is used to maintain data links used with various
special features and auxiliary data links. Link Diagnostic problems are
reported in LNK messages.
Messages
LNK0000
Program identifier.
Action:
Severity: Info.
LNK0001
SNMP trap: No
Invalid command.
Action: Check data and re-enter command.
Severity: Info.
LNK0002
SNMP trap: Yes
Invalid first parameter.

Severity: Info.
LNK0003
SNMP trap: Yes
Invalid second parameter.

Severity: Info.
LNK0004
SNMP trap: Yes
High-speed link does not exist.

Action:
Severity: Info.
LNK0005
SNMP trap: Yes
Low-speed link does not exist.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1188 of 2360

LNK0006
Incorrect number of parameters inputted for the command specified.

Severity: Info.
LNK0007
SNMP trap: Yes
Invalid data keyed in.

Action: Check data and re-enter the command.
Severity: Info.
LNK0008
SNMP trap: Yes
The SDI for the high-speed link or low-speed link is not enabled.
Action: Use the ENL command to enable the SDI and re-enter the command.
Severity: Info.
LNK0009
SNMP trap: Yes
SNMP trap: Yes
Invalid parameter 3.
Action:
Severity: Info.
LNK0010
IMS/IVMS package not equipped.

Action:
Severity: Info.
LNK0011
SNMP trap: Yes
IMS/IVMS package and ACD-D not equipped.

Action:
Severity: Info.
LNK0012
SNMP trap: Yes
ACD-D package not equipped.

Action:
Severity: Info.
LNK0013
SNMP trap: Yes
APL number out-of-range.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1189 of 2360

LNK0014
Not an APL link.

Action:
Severity: Info.
LNK0015
SNMP trap: Yes
APL Logical Unit not found.

Action:
Severity: Info.
LNK0016
SNMP trap: Yes
Attendant Logical Terminal Number (LTN) out-of-range.

Action:
Severity: Info.
LNK0017
SNMP trap: Yes
Customer number does not exist.

Action:
Severity: Info.
LNK0018
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Unknown configuration.
Action:
Severity: Info.
LNK0019
Invalid link specified.

Action:
Severity: Info.
LNK0020
Not a valid option.

Action:
Severity: Info.
LNK0021
APL is down.
Action:
Severity: Info.
System Messages
Page 1190 of 2360

LNK0022
Customer number not defined.

Action:
Severity: Info.
LNK0023
SNMP trap: Yes
Attendant LTN not defined.

Action:
Severity: Info.
LNK0024
SNMP trap: Yes
Directory Numbers (DN) not defined.

Action:
Severity: Info.
LNK0025
SNMP trap: Yes
Cannot allocate Call Register.

Action:
Severity: Info.
LNK0026
SNMP trap: Yes
Confirmation not sent. Cannot allocate Call Register.

Action:
Severity: Info.
LNK0028
SNMP trap: Yes
Cannot link to IMS/IVMS output queue.

Action:
Severity: Info.
LNK0029
SNMP trap: Yes
No APL exists in the system.

Action:
Severity: Info.
LNK0030
SNMP trap: Yes
No APL SDI exists in the system.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1191 of 2360

LNK0031
APL is up but queue is full.

Action:
Severity: Info.
LNK0032
SNMP trap: Yes
Interface pack failed to respond.

Action:
Severity: Info.
LNK0033
SNMP trap: Yes
Interface pack has permanent interrupt.

Action:
Severity: Info.
LNK0034
SNMP trap: Yes
Phantom message monitor input at application program link.

Action:
Severity: Info.
LNK0035
SNMP trap: Yes
Phantom message monitor input (AIM link).

Action:
Severity: Info.
LNK0037
SNMP trap: Yes
Phantom message from message monitor output queue at AIM link.

Action:
Severity: Info.
LNK0039
SNMP trap: Yes
Phantom message from packet monitor output at AIM link.

Action:
Severity: Info.
LNK0040
SNMP trap: Yes
Phantom message from packet monitor input at application program link.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1192 of 2360

LNK0042
Message from message monitor output at an illegal link.

Action:
Severity: Info.
LNK0043
SNMP trap: Yes
Message from message monitor input at an illegal link.

Action:
Severity: Info.
LNK0044
SNMP trap: Yes
Bad packet message received at application program link.

Action:
Severity: Info.
LNK0045
SNMP trap: No
Bad packet message received at AIM link.

Action:
Severity: Info.
LNK0046
SNMP trap: Yes
Packet received on application program link does not match with packet sent
from AIM.
Action:
Severity: Info.
LNK0047
SNMP trap: Yes
Packet received on AIM link does not match with packet sent from application
program.
Action:
Severity: Info.
LNK0048
SNMP trap: Yes
SNMP trap: Yes
Invalid password.
Action:
Severity: Info.
LNK0049
Process ID out-of-range.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1193 of 2360

LNK0050
Process ID not set.

Action:
Severity: Info.
LNK0051
SNMP trap: Yes
ESDI number is out-of-range.

Action:
Severity: Info.
LNK0052
SNMP trap: Yes
Information Services (IS) package is not equipped. Command Status Link

(CSL) is not equipped.
Action:
Severity: Info.
LNK0053
SNMP trap: No
Command is not valid for ESDI async port.

Action:
Severity: Info.
LNK0054
SNMP trap: No
Command is not valid if one of the ports is asynchronous.

Action:
Severity: Info.
LNK0055
SNMP trap: No
Command is not valid at current state (e.g., the CON ESDI n command can
only be entered if the ESDI is in the ENABLED state).
Action:
Severity: Info.
LNK0056
SNMP trap: Yes
ESDI logical unit not found.

Action:
Severity: Info.
LNK0057
SNMP trap: No
ESDI_CSL_CRPTR is nil.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1194 of 2360

LNK0058
ESDI are not in simulator loop around mode. Error message for SMLP
command.
Action:
Severity: Info.
LNK0059
SNMP trap: No
For SMLP command, both ports have to be in IDLE state. This indicates one
of the ports is not in IDLE state.
Action:
Severity: Info.
LNK0060
SNMP trap: No
ESDI hardware does not respond. The pack may not be plugged in correctly
or the device address may be incorrect.
Action:
Severity: Info.
LNK0061
SNMP trap: No
ESDI permanent interrupt.

Action:
Severity: Info.
LNK0062
SNMP trap: No
For SMLP command, ports have to be configured for loop back simulator.
Issue CNFG command first.
Action:
Severity: Info.
LNK0063
SNMP trap: No
ESDI is not in CONNECTED state. For DSC ESDI N and ENL CMS N
commands, the ESDI has to be in CONNECTED state.
Action:
Severity: Info.
LNK0064
SNMP trap: No
There is no response to the polling message.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1195 of 2360

LNK0065
For SWCH CMS N1 N2 command, N1 should be in ACTIVE state.

Action:
Severity: Info.
LNK0066
SNMP trap: No
For SWCH CMS N1 N2 command, N2 should be in STANDBY state.

Action:
Severity: Info.
LNK0067
SNMP trap: No
For SWCH CMS N1 N2 command, both links should belong to the same
external Server address (VASID).
Action:
Severity: Info.
LNK0068
SNMP trap: No
Invalid ESDI state for the given port or its pair when self test (SLFT) command
is issued.
Action:
Severity: Info.
LNK0080
SNMP trap: No
CSL simulator command is not valid until SIM command has been entered.
Action:
Severity: Info.
LNK0081
SNMP trap: Yes
CSL IO data block not built. This port is defined as CSL port, but no TTY IO
block exists.
Action: To correct this, either: 1. manually init, or 2. go through LD 17 entering
{cr} to every prompt.
Severity: Info.
LNK0082
SNMP trap: Yes
This port is not defined as a CSL link

Action: To configure it as a CSL link, in LD 17 1. add "USER" "CMS" under
"IOTB" prompt 2. add port to "CMS" under "VAS" prompt.
Severity: Info.
SNMP trap: Yes
System Messages
Page 1196 of 2360

LNK0083
This CSLSIM message could not be sent because it could not be linked to the
CSL output queue.
Action:
Severity: Info.
LNK0084
SNMP trap: Yes
SNMP trap: Yes
Input out-of-range.
Action:
Severity: Info.
LNK0085
Current CSLSIM message has a message length of zero.

Action:
Severity: Info.
LNK0086
SNMP trap: Yes
Incoming CSL message does not match the stored one.

Action:
Severity: Info.
LNK0087
SNMP trap: Yes
CSL message type is not defined.

Action:
Severity: Info.
LNK0088
SNMP trap: Yes
SNMP trap: Yes
CSl link is not active.

Action:
Severity: Info.
LNK0089
Comm TN failed TN translation.

Action:
Severity: Info.
LNK0090
SNMP trap: Yes
SNMP trap: Yes
Comm TN out-of-range.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1197 of 2360

LNK0092
Invalid HEX input.

Action:
Severity: Info.
LNK0100
SNMP trap: Yes
Loop number out of range for ENIT/ENXT commands.

Action:
Severity: Info.
LNK0101
SNMP trap: Yes
Incorrect loop type. Depending on the command, the loop must be TERM, DTI,
DLI or MISP.
Action:
Severity: Info.
LNK0102
SNMP trap: Yes
Shelf number out-of-range.

Action:
Severity: Info.
LNK0103
SNMP trap: Yes
Card number out-of-range.

Action:
Severity: Info.
LNK0104
SNMP trap: Yes
SNMP trap: Yes
Card is not configured.

Action:
Severity: Info.
LNK0105
Unit number is out-of-range.

Action:
Severity: Info.
LNK0106
SNMP trap: Yes
Maximum number of links configured for selection criteria.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1198 of 2360

LNK0107
Maximum number of TNs stored for link.

Action:
Severity: Info.
LNK0108
SNMP trap: Yes
All priorities or message types are out-of-range.

Action:
Severity: Info.
LNK0109
SNMP trap: Yes
Input/Output block does not exist.

Action:
Severity: Info.
LNK0132
SNMP trap: Yes
Superloop number must be a multiple of 4.

Action:
Severity: Info.
LNK0133
SNMP trap: No
Incorrect password for MISP message monitor.

Action:
Severity: Info.
LNK0201
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
This is not a CCR link.

Action:
Severity: Info.
LNK0202
This is not a CSL link.

Action:
Severity: Info.
LNK0203
This is not an APL link.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1199 of 2360

LNK0204
ICP package not equipped.

Action:
Severity: Info.
LNK0205
SNMP trap: Yes
No ICP links exist in the system.

Action:
Severity: Info.
LNK0206
SNMP trap: Yes
There is no MCR available for ICPM.

Action:
Severity: Info.
LNK0207
SNMP trap: Yes
Message type out-of-range: 0-3, 50-61.

Action:
Severity: Info.
LNK0210
SNMP trap: Yes
Failed to execute the ENL AML # MDL command.

Action: Try the command again.
Severity: Info.
LNK0211
SNMP trap: Yes
AML number is out-of-range.

Action:
Severity: Info.
LNK0212
SNMP trap: Yes
Failed to execute the DIS AML # MDL command.

Severity: Info.
LNK0213
SNMP trap: Yes
The command cannot be executed. The input command is illegal.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1200 of 2360

LNK0214
The command cannot be executed because the CSL package is not equipped.
Action:
Severity: Info.
LNK0215
SNMP trap: Yes
The command cannot be executed because illegal number of parameters was

typed.
Action:
Severity: Info.
LNK0216
SNMP trap: Yes
The command cannot be executed because the AML number is not valid.
Action:
Severity: Info.
LNK0217
SNMP trap: Yes
The command cannot be executed because of a syntax error in the command

line.
Action:
Severity: Info.
LNK0218
SNMP trap: Yes
The command cannot be executed because logical AML I/O pointer cannot be
setup.
Action:
Severity: Info.
LNK0219
SNMP trap: Yes
The card type on which the AML is configured is not an MSDL card.
Action:
Severity: Info.
LNK0220
SNMP trap: Yes
The command cannot be executed because the MSDL card is disabled.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1201 of 2360

LNK0221
The AML command cannot be processed when the link is disabled or is in

process of being disabled.
Action:
Severity: Info.
LNK0222
SNMP trap: Yes
The command can only be executed when the MSDL AML is in the establish
state.
Action:
Severity: Info.
LNK0223
SNMP trap: Yes
Failed to execute the ENL AML # MON command.

Severity: Info.
LNK0224
SNMP trap: Yes
Command not executed. AML application layer (i.e., layer 7) is already

enabled or is in process of being enabled.
Action:
Severity: Info.
LNK0225
SNMP trap: Yes
Command not executed. AML application layer (i.e., layer 7) is already

disabled.
Action:
Severity: Info.
LNK0226
SNMP trap: Yes
Failed to execute the DIS AML # MON command.

Severity: Info.
LNK0227
SNMP trap: Yes
Failed to execute the UPLD AML # TBL# command.

Severity: Info.
SNMP trap: Yes
System Messages
Page 1202 of 2360

LNK0228
The AML is in process of link reset.

Action: Wait until the process is finished, then execute the command again.
Severity: Info.
LNK0229
SNMP trap: Yes
The command can not be executed because the given card type is not ESDI.
Action:
Severity: Info.
LNK0230
SNMP trap: Yes
STA number is either out of range or does not exist.

Action:
Severity: Info.
LNK0231
SNMP trap: Yes
STA package is not equipped.

Action:
Severity: Info.
LNK0232
SNMP trap: Yes
MSDL card is not operational.

Action:
Severity: Info.
LNK0233
SNMP trap: Yes
Overlay command failed.

Action:
Severity: Info.
LNK0234
SNMP trap: Yes

Action:
Severity: Info.
LNK0235
SNMP trap: Yes
Cannot set up MSDL pointers.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1203 of 2360

LNK0236
Cannot set up STA related pointers.

Action:
Severity: Info.
LNK0237
SNMP trap: Yes
STA application is enabled, but the administration terminal is not.

Action:
Severity: Info.
LNK0238
SNMP trap: Yes
STA application is disabled, but the administration terminal is not.

Action:
Severity: Info.
LNK0239
SNMP trap: Yes
STAT STA command failed.

Action:
Severity: Info.
LNK0241
SNMP trap: Yes
You cannot disable that STA application from the STA administration terminal.
Action:
Severity: Info.
LNK0266
SNMP trap: Yes
The Voice Mailbox Administration package is not equipped.

Action:
Severity: Info.
LNK0267
SNMP trap: Yes
Cannot set up Voice Mailbox Administration application related pointers.

Action: Be sure the application is configured.
Severity: Info.
LNK0268
SNMP trap: Yes
The Voice Mailbox Administration application is already enabled.

Action: Get the status of VMBA in LD 48. It may be necessary to disable then
reenable the application.
CAUTION: Prior to disabling the application, be sure no audits, uploads, or
updates are in process. These will be lost when the application is disabled.
Severity: Info.
SNMP trap: Yes
System Messages
Page 1204 of 2360

LNK0269
A mailbox database audit or upload is in progress. Only one process at a time

can be activated.
Action: Use the STAT command in LD 48 to get application status information.
Severity: Info.
LNK0270
SNMP trap: Yes
Cannot activate an upload or audit while the Voice Mailbox Administration

application is inactive.
Action: Enable the application prior to performing an audit, or upload.
Severity: Info.
LNK0271
SNMP trap: Yes
The Voice Mailbox Administration application is already disabled.

Action:
Severity: Info.
LNK0272
SNMP trap: Yes
When the Voice Mailbox Administration application is disabled, the audit,

upload, and update function are also disabled.
Action:
Severity: Info.
LNK0273
SNMP trap: Yes
Invalid DN type for the audit or upload command. The DN type must be SCR,
SCN, MCR, or MCN.
Action:
Severity: Info.
LNK0274
SNMP trap: Yes
That DN is not configured with a Voice Mailbox, and cannot be audited.

Action:
Severity: Info.
LNK0275
SNMP trap: Yes
Invalid password for UIPE BRIT debug option (Overlay 48).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1205 of 2360

LNK0277
Access database error.

Action: Check if CMDU is enabled.
Severity: Info.
LNK0278
SNMP trap: No
ENL or DIS operation failed.

Action: Check the network and the link status.
Severity: Info.
LNK0279
SNMP trap: No
Set subnet mask operation failed.

Action:
Severity: Info.
LNK0283
SNMP trap: No
STAT SDI LOW, ENL SDI LOW and DIS SDI LOW are invalid commands on
Option 11C.
Action: Use LD 37.
Severity: Info.
LNK0290
SNMP trap: Yes
Server Task cannot be disabled when the elan link is active.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1206 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1207 of 2360
MAT: Meridian Administration Tools

Messages
MAT0001
Successful login.
Action:
Severity: Info.
MAT0002
SNMP trap: Yes
SNMP trap: Yes
Successful logout.
Action:
Severity: Info.
MAT0003
Login denied: too many sessions.

Action: Retry later when existing user logs out or is forced off by an
administrator.
Severity: Minor.
MAT0004
SNMP trap: Yes
Login denied: authentication fails. (For example, the wrong password)

Action: Retry with a correct LAPW user name or password. User has to have
MAT=3DYes. MAT package has to be enabled.
Severity: Minor.
MAT0006
SNMP trap: Yes
Forced logout by another user.

Action:
Severity: Info.
MAT0007
SNMP trap: Yes
Forced logout by the system

Action: Check for network failure or PC crash
Severity: Info.
SNMP trap: Yes
System Messages
Page 1208 of 2360

MAT0010
Inventory card generation complete.

Action:
Severity: Info.
MAT0011
SNMP trap: Yes
Inventory sets generation complete.

Action:
Severity: Info.
MAT0012
SNMP trap: Yes
Inventory card generation aborted.

Action:
Severity: Info.
MAT0013
SNMP trap: Yes
Inventory sets generation aborted

Action:
Severity: Info.
MAT0014
SNMP trap: Yes
Error writing to card inventory file; generation aborted.

Action: Try again.
Severity: Minor.
MAT0015
SNMP trap: Yes
Error writing to sets inventory file; generation aborted.

Action: Try again.
Severity: Minor.
MAT0016
SNMP trap: Yes
Unable to rename inventory card file; generation aborted.

Action: Try again.
Severity: Minor.
MAT0017
SNMP trap: Yes
Unable to rename inventory sets file; generation aborted.

Action: Try again.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1209 of 2360

MAT0018
Queue error; card inventory generation aborted.

Action: Try again.
Severity: Minor.
MAT0019
SNMP trap: Yes
Queue error; sets inventory generation aborted.

Action: Try again.
Severity: Minor.
MAT0020
SNMP trap: Yes
Card inventory record(s) lost; generation aborted.

Action: Try again.
Severity: Minor.
MAT0021
SNMP trap: Yes
Set inventory record(s) lost; generation aborted.

Action: Try again.
Severity: Minor.
MAT0022
SNMP trap: Yes
Unable to close inventory card file; generation aborted.

Action: Try again.
Severity: Minor.
MAT0023
SNMP trap: Yes
Unable to close inventory sets file; generation aborted.

Action: Try again.
Severity: Minor.
MAT0024
SNMP trap: Yes
Inventory cannot create 'inv' directory!

Action:
Severity: Major.
MAT0025
SNMP trap: Yes
Warning: ESN, MIN, DSPL, and DSPT are not transmitted to the switch if VISI
= YES.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1210 of 2360

MAT0026
Transmitted to the switch if VISI = YES.

Action:
Severity: Info.
MAT0027
SNMP trap: No
If short hunt is configured (HUNT = 0000), then Key 1 must be configured as

an SCR with the same DN as Key 0.
Action:
Severity: Info.
MAT0028
SNMP trap: No
Location referenced by CPND Name entry not found in station.

Action:
Severity: Info.
MAT0029
SNMP trap: No
ERROR!!! DECT is only valid for WRLS = YES.

Action:
Severity: Info.
MAT0030
SNMP trap: No
DECT is only supported only on a DMC or DMCE card.

Action:
Severity: Info.
MAT0031
SNMP trap: No
Non-default values (CNUA, CNUS, and CNAA) of Calling Number and Name
Delivery are not allowed for a DIG set.
Action:
Severity: Info.
MAT0032
SNMP trap: No
Loop number must be 2,4,6,12,14,or 16.

Action:
Severity: Info.
MAT0033
SNMP trap: No
Loop number must be 1,3,5,7,8,9,11,13,15,17,18,or 19.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1211 of 2360

MAT0034
Lopp number must be 1,3,5,7,8,9,10,11,13,15,17,18, or 19.

Action:
Severity: Info.
MAT0035
SNMP trap: No
VMA and card slot #10 are only applicable to M2008 or SL1 sets. In addition,
VMA required the set to be configured on card slot #10
Action:
Severity: Info.
MAT0036
SNMP trap: No
Card slot #10 must have unit 0,1,2,3,8,9,10 or 11.

Action:
Severity: Info.
MAT0037
SNMP trap: No
Key RLS requires CLS VMA.

Action:
Severity: Info.
MAT0038
SNMP trap: No
If MWUN = 32, then CDEN must have octal density.

Action:
Severity: Info.
MAT0039
SNMP trap: No
Loop number must be 2,4,6,12,14,16,22,24, or 26.

Action:
Severity: Info.
MAT0040
SNMP trap: No
Loop number must be between 1 - 30.

Action:
Severity: Info.
MAT0041
SNMP trap: No
If MMA and FLX, then DTMK must be default.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1212 of 2360

MAT0042
CLSs VCE, UNR and WTA are required for CLS MMA.
Action:
Severity: Info.
MAT0045
SNMP trap: No
If MWUN = 16, then CDEN must be Quad density.

Action:
Severity: Info.
MAT0048
SNMP trap: No
XMWK and RMWK are not configurable for MMT sets.

Action:
Severity: Info.
MAT0049
SNMP trap: No
SCH1961/SCH1962 - For M3905, key 05 must be NUL in order for the

application key to be operational. The Application key is required in order to
access Corporate Directory or User configuration for Set-to-Set messaging.
Action:
Severity: Info.
MAT0050
SNMP trap: No
If CFTA = CFTD, then delete EHT and EFD entries.

Action:
Severity: Info.
MAT0051
SNMP trap: No
If AGRA is denied, then MOAA must not be allowed.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1213 of 2360
MCT: Malicious Call Trace

Messages
MCT0604
Test case number does not match its test data.

Action:
Severity: Minor.
MCT0606
SNMP trap: No
It is not applicable to Network/DTR card.

Action:
Severity: Minor.
MCT0652
SNMP trap: No
MISP expediated buffer not available.

Action:
Severity: Minor.
MCT0653
SNMP trap: No
MCT results received of an unknown test.

Action:
Severity: Minor.
MCT0654
SNMP trap: No
Cannot do loopback on a non-BRI line card.

Action:
Severity: Minor.
MCT0655
SNMP trap: No
SNMP trap: No
Data corruption.
Action:
Severity: Critical.
MCT0656
The BRI line card is not assigned to the MISP.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1214 of 2360

MCT0657
No line cards defined at the given TN.

Action:
Severity: Minor.
MCT0658
SNMP trap: No
SNMP trap: No
Not an MISP card.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 1215 of 2360
MFC: Multifrequency Compelled

Signaling (LD 54)
Multifrequency Compelled Signaling (MFC) or Multifrequency Signaling (MFE)
provides a handshaking facility between the Nortel Networks system and the
Central Office or Public Exchange (CO/PE) or between other PBXs over
network Tie trunks.
The format of an MFC message is MFCxxx MFCTN TRKTN X1-X5
Where:
MFCTN = MFC register TN (packed format)
TRKTN = Trunk TN of the CMFTN (packed format)
X1-X5 = the first six words of the unprotected MFC block for the
unit used.
Messages
MFC0000
Program 54 identifier.
Action:
Severity: Info.
MFC0007
SNMP trap: No
Invalid DOD trunk (X08). Undefined error (hardware) (X11).

Action:
Severity: Info.
MFC0008
SNMP trap: Yes
Trunk is busy or disabled (X08). Software timeout (software) (X11).

Action:
Severity: Info.
MFC0009
SNMP trap: Yes
Invalid TN. Shelf out-of-range (0 to 3) (X08). Not ready to send (software)

(X11).
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1216 of 2360

MFC0010
Invalid TN. Card out-of-range (1 to 10) (X08). Undefined function/signal

(software) (X11).
Action:
Severity: Info.
MFC0020
SNMP trap: Yes
No MFC incoming table defined for route (software) (X11).

Action:
Severity: Info.
MFC0021
SNMP trap: Yes
No MFC outgoing table defined for route (software) (X11).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1217 of 2360
MFD: Multifrequency Signaling

Diagnostic (LD 54)
Multifrequency Compelled Signaling (MFC) or Multifrequency Signaling (MFE)
provides a handshaking facility between the Nortel Networks system and the
Central Office or Public Exchange (CO/PE), or between other PBXs over
network Tie trunks.
The MFD Overlay program is used to diagnose, display or change the status
of the MFC or MFE send/receive (S/R) cards. The program resets all available
MFC or MFE cards (both channels idle) and performs loop-back tests during
the midnight routines. After every SYSLOAD or power-up, all available MFC
or MFE cards are initialized.
Messages
MFD0001
Invalid input. Number of characters in one field is greater than four.

Action: Check input. Reenter command.
Severity: Info.
MFD0002
SNMP trap: Yes
Invalid input. Wrong data type.

Severity: Info.
MFD0003
SNMP trap: Yes
Invalid input. Command field unknown.

Severity: Info.
MFD0004
SNMP trap: Yes
Invalid input. Too many parameters.

Action: Check input Reenter command.
Severity: Info.
MFD0005
SNMP trap: Yes
Previous command still in progress.

Severity: Info.
SNMP trap: Yes
System Messages
Page 1218 of 2360

MFD0007
Wrong argument/invalid parameters.

Severity: Info.
MFD0008
SNMP trap: Yes
Invalid TN. Loop out-of-range 0 to 159.

Action: Re-enter the command.
Severity: Info.
MFD0009
SNMP trap: Yes
Invalid TN. Shelf out-of-range (0 to 3).

Action: Reenter command.
Severity: Info.
MFD0010
SNMP trap: Yes
Invalid TN. Card out-of-range (1 to 10).

Severity: Info.
MFD0011
SNMP trap: Yes
Invalid TN. Unit out-of-range (0 to 1).

Severity: Info.
MFD0012
SNMP trap: Yes
Wrong Argument. Digit out-of-range (1 to 30).

Severity: Info.
MFD0013
SNMP trap: Yes
Wrong Argument. Level out-of-range (0 to 7).

Severity: Info.
MFD0014
SNMP trap: Yes
Specified TN is not equipped to be MFC or MFE channel.

Action: Check input. Re-enter the command.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1219 of 2360

MFD0015
MFC or MFE channel is busy. No action.

Action:
Severity: Info.
MFD0017
SNMP trap: Yes
MFC or MFE channel found faulty and has been disabled. Given after ATST
command or in response to test initiated by system. TN and failed digit are
both output.
Action: For repeated failures, replace card.
Severity: Minor.
MFD0019
SNMP trap: Yes
MFC or MFE channel found faulty and has been disabled. Given after MTST
command. TN, failed digit, and signal level received are all output.
Severity: Minor.
MFD0021
SNMP trap: Yes
Timeout, no response. Channel is disabled. Given after ATST, MDST

commands and midnight test.
Severity: Minor.
MFD0024
SNMP trap: Yes
MFC cordage restricted, Overlay not loaded.

Action:
Severity: Minor.
MFD0030
SNMP trap: Yes
Corrupted data, loop density out-of-range (0 to 2).

Action:
Severity: Minor.
MFD0031
SNMP trap: Yes
Corrupted data, unit information out-of-range (0 to 15).

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1220 of 2360

MFD0032
Self-test failed. Channel is not disabled.

Action:
Severity: Minor.
MFD0033
SNMP trap: Yes
Self-test failed, channel is disabled

Action:
Severity: Minor.
MFD0034 tn yy
SNMP trap: No
Self-test failed, and XMFC/XMFE card disabled (all units) Where: tn= loop,
shelf and card, yy = result. 00- Self-test O.K. 01- DS-30X Toggle Fail 02- DSP
EPROM Low Fail 03- DSP EPROM High Fail 04- DSP RAM 0 Low Fail 05DSP RAM 0 High Fail 06- DSP RAM 1 Low Fail 07- DSP RAM 1 High Fail 08DSP RAM 2 Low Fail 09- DSP RAM 2 High Fail 0A- DSP DS-30X RAM 0 Fail
0B- DSP DS-30X RAM 1 Fail 0C- DSP Latch Timeout 0D- DSP Invalid
Configuration 0F- DSP General Fail 10- 80C31 AROM Fail 11- 80C31 RAM
Fail 12- 80C31 MPU Fail 13- DSP Timeout Fail 14- A07 Register Fail 15Card-Lan Fail 16- EEPROM Fail 17- Invalid Message from Meridian SL-1 2xDID Loopback Fail (x = digit) 3x- DOD loopback Fail (x = digit)
Action:
Severity: Critical.
MFD0035 l s c
SNMP trap: Yes
Timeout due to no response. The XMFC/XMFE card missing or disabled (all

units), where: l s c = TN information (loop, shelf, card)
Action:
Severity: Critical.
MFD0038
SNMP trap: Yes
Invalid TN. Unit out of range (0-31).

Action:
Severity: Minor.
MFD0039
SNMP trap: No
Wrong argument. Level out of range (0-15).

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1221 of 2360

MFD0040
Corrupted data. Loop density out of range.

Action:
Severity: Major.
MFD0041
SNMP trap: No
Invalid TN. Card out of range (0-15).

Action:
Severity: Minor.
MFD0042
SNMP trap: No
This command is supported in Overlay 32.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1222 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1223 of 2360
MFE: Multifrequency Signaling

Diagnostic (LD 54)
The MFE messages identify software/hardware errors during call processing.
Output is in the format of: MFExxx MFETN TRKTN,
Where:
xxx is the Error code number
MFETN is the MFE register TN (packed format).
TRKTN is the Trunk TN associated with the MFETN (packed format).
Messages
MFE0001
Noisy Multifrequency Signaling (MFE) pack hardware.

Action:
Severity: Minor.
MFE0002
SNMP trap: No
SNMP trap: No
Large twist (hardware).

Action:
Severity: Minor.
MFE0003
Three frequencies (hardware).

Action:
Severity: Minor.
MFE0004
SNMP trap: No
No inter-digit pause (hardware).

Action:
Severity: Minor.
MFE0005
SNMP trap: No
Invalid decision (hardware).

Action:
Severity: Minor.
MFE0006
SNMP trap: No
MFE pack firmware fault (hardware).

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1224 of 2360

MFE0007
Illegal signal 11 to 15 not supported (hardware).

Action:
Severity: Minor.
MFE0008
SNMP trap: No
Signal sent is invalid at this time (hardware).

Action:
Severity: Minor.
MFE0009
SNMP trap: No
Software timeout (software).

Action:
Severity: Minor.
MFE0010
SNMP trap: Yes
Undefined/invalid signal received (software).

Action:
Severity: Minor.
MFE0011
SNMP trap: Yes
Signal not expected (software).

Action:
Severity: Minor.
MFE0012
SNMP trap: Yes
Undefined function (software).

Action:
Severity: Minor.
MFE0013
SNMP trap: Yes
Outgoing calls not allowed (software).

Action:
Severity: Minor.
MFE0014
SNMP trap: No
MFE table not defined (software).

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1225 of 2360

MFE0015
Not ready to send (software).

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1226 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1227 of 2360
MFK: Multifrequency Signaling for KD3

Messages
MFK0001
Noisy MFK pack

Action:
Severity: Info.
MFK0002
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Large twist
Action:
Severity: Info.
MFK0003
Three frequencies
Action:
Severity: Info.
MFK0004
No interdigit pause
Action:
Severity: Info.
MFK0005
Invalid decision
Action:
Severity: Info.
MFK0006
MFK pack firmware fault

Action:
Severity: Info.
MFK0007
SNMP trap: No
SNMP trap: No
Illegal signal
Action:
Severity: Info.
System Messages
Page 1228 of 2360

MFK0008
Signal sent is invalid at this time

Action:
Severity: Info.
MFK0009
SNMP trap: No
SNMP trap: Yes
Software timeout
Action:
Severity: Info.
MFK0010
Undefined signal received

Action:
Severity: Info.
MFK0011
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Signal not expected

Action:
Severity: Info.
MFK0012
Undefined function
Action:
Severity: Info.
MFK0014
MFK table not defined

Action:
Severity: Info.
MFK0015
Not ready to send

Action: Contact your technical-support group.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1229 of 2360
MFR: Multifrequency Receiver

The Multifrequency Receiver card receives multifrequency signals for the
Feature Group D package.
Messages
MFR0001 l s c u
MFR unit did not respond. The specified MFR unit has been disabled.
Action: Replace the indicated card.
Severity: Critical.
MFR0002 l s c n
SNMP trap: Yes
Self-test of MFR card failed, where: n is the failure description. 1 = EPROM

failed 2 = Processor failed 3 = Invalid result The specified MFR card has been
disabled.
Action: Replace the indicated card.
Severity: Critical.
SNMP trap: Yes
MFR0003 tn n1 n2 nn MFR unit failed MF tones test, where n1, n2, etc. is the list of input
messages received by the MFR. In a successful test, 30 input messages are
received, corresponding to KP, 0-9, ST, ST', ST'' and ST'''. Each tone input
messages is followed by an interdigit silence input message. The specified
card has been disabled.
Action: Replace the indicated card. Suspect faulty MFS if fault persists or if MFR
units on more than one card are shown faulty.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1230 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1231 of 2360
MFS: Multifrequency Sender Diagnostic

for ANI (LD 46)
The Multifrequency Sender card provides multifrequency signals of Automatic
Number Identification (ANI) digits over Centralized Automatic Message
Accounting (CAMA) trunks to a toll switching CAMA, Traffic Operator Position
System (TOPS) or Traffic Service Position System (TSPS).
The MFS diagnostic program is used to maintain the MFS cards. Problems are
identified in MFS messages.
Messages
MFS0000
Program identifier. No action required.

Action:
Severity: Minor.
MFS0001
SNMP trap: No
Invalid command. Only the commands listed are allowed.

Action:
Severity: Minor.
MFS0002
SNMP trap: Yes
Incorrect use of command.

Action: Refer to command table for correct parameters.
Severity: Minor.
MFS0004
SNMP trap: Yes
Loop specified is out-of-range.

Action:
Severity: Minor.
MFS0005
SNMP trap: Yes
This command is only allowed to be used from an SL-1 maintenance set.

Action: Abort program and reload from an SL-1 telephone designated as a
maintenance device.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1232 of 2360

MFS0006
Could not establish a channel connection between the SL-1 maintenance

telephone and the MF sender.
Action: Run a signaling diagnostic to find the cause.
Severity: Minor.
MFS0020 loop
SNMP trap: Yes
MF sender failed to respond. Minor alarm lamp lit on attendant console.

Action: Ensure that faceplate switch is set to ENABLE and that pack is inserted
properly. If MF Sender still fails to respond, the pack is faulty.
Severity: Minor.
MFS0023 loop d
SNMP trap: Yes
MF sender does not outpulse for the digits d listed. Only applications with NT
or XT machine types can disregard this message. Operation of the MFS card
is unaffected.
Action: Replace pack.
Severity: Info.
MFS0024 loop
SNMP trap: Yes
MF sender has a fault in the FIFO stack memory. This fault is not service
affecting.
Action: Replace pack.
Severity: Critical.
MFS0100
SNMP trap: Yes
On ENLX (enable Conference/TDS/MFS card) did not receive the message

verifying download completion within six seconds.
Action: Disable the card (DISX) and retry the Enable (ENLX) command.
Severity: Critical.
MFS0101
SNMP trap: Yes
Timeout on Digit Interrupt for Conference/TDS/MFS card.

Action:
Severity: Critical.
MFS0102
SNMP trap: Yes
Cannot use the ENLX (Enable) or DISX (Disable) commands on a

non-Conference/TDS/MFS card.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1233 of 2360

MFS0103
The Conference/TDS/MFS card is already enabled/disabled

Action:
Severity: Critical.
MFS0104
SNMP trap: Yes
Received an unexpected message from a Conference/TDS/MFS card.

Action:
Severity: Critical.
MFS0105
SNMP trap: Yes
This Command is not available for VXCT components, please use LD 34

commands
Action: Action: Please check the parameters used
Severity: Info.
SNMP trap: Yes
System Messages
Page 1234 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1235 of 2360
MISP: Multi-purpose ISDN Signaling

Processor
The MISP messages report problems with the MISP card and its applications.
Messages
MISP0100 x
The CSTAT and CSUBSTAT fields on MISP x indicate that the card is
Manually Disabled. The Meridian 1 believes the card is Enabled. The card is
placed in the System Disabled - Selftests Passed state, and within the next
few minutes, the Meridian 1 will attempt to enable the card. Where: x = loop
number
Action:
Severity: Critical.
MISP0101 x
SNMP trap: No
The CSTAT field on MISP x indicates that the card is no longer Enabled. The
MISP302. Where: x = loop number
Action:
Severity: Critical.
MISP0102 x
SNMP trap: No
No response was received from MISP x to a background polling message sent

periodically to each MISP. The purpose of this message is to ensure that the
card is capable of receiving and sending messages. Where: x = loop number
Action:
Severity: Critical.
MISP0103 x
SNMP trap: No
An Overlay was waiting for a message from MISP x. Most likely, the Overlay
is no longer loaded. The message the Overlay was waiting for was never
received. Where: x = loop number
Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 1236 of 2360

MISP0104 x
The MISP background audit sent a message to MISP x and did not receive a
response. Where: x = loop number
Action:
Severity: Critical.
MISP0106 x appl
SNMP trap: No
The MISP audit detected that there was no response to a maintenance

message originated by application "appl" on MISP x. Where: x = loop number;
appl = the application name
Action:
Severity: Critical.
SNMP trap: No
MISP0107x appl y The Meridian 1 was unable to determine if downloading was necessary. Three
fields accompany this message: x = the MISP loop number, appl = the
application name. The third field (y) contains a value for design use only. An
for the failure.
Action:
Severity: Critical.
MISP0108 x appl
SNMP trap: No
Application "appl" on MISP x needs to be downloaded to the card.

Downloading begins as soon as there is no overlay loaded. Where: x = loop
number
Action:
Severity: Critical.
MISP0112 x
SNMP trap: No
MISP x has been reset in order to begin automatic recovery. Immediately

finished, provided they pass, the Meridian1 will attempt to enable the card.
Where: x = loop number
Action:
Severity: Critical.
MISP0201 x appl
SNMP trap: No
MISP x sent a message to the Meridian 1 indicating application "appl" data

space has been corrupted. Where: x = loop number and appl = the application
name.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1237 of 2360

MISP0202 x appl
MISP x sent a message to the Meridian 1 indicating that application "appl" on

the card unexpectedly disabled itself (performed a "close"). Where: x = loop
number and appl = the application name.
Action:
Severity: Critical.
MISP0204 x appl
SNMP trap: No
The Meridian 1 searched the system disk to find a version of an application

"appl" for MISP x, and found none. Where: x = loop number and appl = the
application name.
Action:
Severity: Critical.
SNMP trap: No
MISP0205 x appl y z An error was encountered when searching the system disk to find a version
of application "appl" for MISP x. Where: x = loop number, appl = the application
name. y and z are for design use only.
Action: Refer to an accompanying SDL error message for the exact error
application in question if a version exists on the card.
Severity: Critical.
SNMP trap: No
MISP0206 x appl y z An error was encountered when comparing a version of application "appl"
on the system disk with a version on MISP x. Where: x = loop number and appl
= the application name. y and z are for design use only.
application in question if a version exists on the card.
Severity: Critical.
SNMP trap: No
MISP0207 x appl y z An error was encountered when downloading application "appl" to MISP x.
Where: x = loop number and appl = the application name. y and z are for
design use only.
reason. The entire enable sequence has been aborted.
Severity: Critical.
SNMP trap: No
System Messages
Page 1238 of 2360

MISP0208 x
When preparing to download the base software to MISP x, the card indicated
that some kind of fatal error was encountered. Where: x = loop number.
Action: Execute selftests before attempting any other action regarding this card.
Severity: Critical.
MISP0209 x y z
SNMP trap: No
Some memory was reclaimed within the MSDL for future use. An application
on MSDL x requested that a buffer pool be freed. When this occurred, there
was at least one outstanding buffer. The basecode waited for the buffer(s) to
be returned to the pool before freeing the buffers, but it never returned. The
buffer pool was forcibly freed by the basecode. Where: x = MISP loop number.
y and z are for design use only.
Action:
Severity: Critical.
MISP0300 data
SNMP trap: No
The MISP background audit has changed the state of the card. In the cases
where the card was previously enabled and now is no longer enabled, another
MISP message will indicate the reason for the state change. When making a
state transition due to a fatal error on the card, the reason for the fatal error is
displayed in this message. This is an informational message and requires no
action by the craftsperson. Output data: MISP300 x FROM: aaaa TO: bbbb
TIME time REASON cccc Where: x = MISP loop number (in decimal), aaaa =
the status of the MISP prior to the state change, bbbb = the state of the card
after the state change, time = the time of the state change, cccc = reason for
the error (only when "TO: SYS DSBL - FATAL ERROR")
Action:
Severity: Critical.
MISP0301 x y z
SNMP trap: No
An expedited data unit (XDU) was received. The Meridian 1 is not expecting
MISP x to generate any messages in its current state. However, immediately
following a state transition to a disabled state, a pending message may cause
this message to be displayed. There is no specific action to be taken; however,
the message indicates that the incoming message from the card was not
processed due to the state change.
Action:
Severity: Critical.
MISP0302 x y
553-3001-411
SNMP trap: No
Access to the memory space shared by the Meridian 1 and the MISP (Shared
RAM) has been momentarily suspended by MISP x. There is no specific action
to be taken as a result of this message; however, it indicates that message
Standard 15.00
January 2006
Page 1239 of 2360

transfer between the Meridian 1 and the card ceased momentarily. Where: x
= loop number and y = the reason for the suspension. Currently the only
reason supported is the value 1, indicating that some kind of buffer corruption
was detected.
Action:
Severity: Critical.
MISP0303 x y
SNMP trap: No
The Meridian 1 detected corruption in the receive ring, or the transmit ring, or
both, causing access to the memory space shared by the Meridian 1 and MISP
x (Shared RAM) to be momentarily suspended. There is no specific action to
be taken as a result of this message; however, it indicates that message
transfer between the Meridian 1 and the card ceased momentarily. Where: x
= loop number and y = a decimal number indicating where the corruption was
detected. 1 = receive ring 2 = transmit ring 3 = both receive and transmit rings.
Action:
Severity: Critical.
MISP0305 x y
SNMP trap: No
The Meridian 1 has received 100 or more messages from MISP x within two
seconds. At this level of message transfer, there may be some impact to the
overall system performance. The level of message transfer does not warrant
removing the card from service. Where: x = loop number and y = the rate of
message transfer from the card to the Meridian 1 (in terms of messages per
second).
Action:
Severity: Critical.
MISP0306 x y
SNMP trap: No
The Meridian 1 has received 100 or more messages from the MISP x within
one second. At this level of message transfer, there may be some impact to
the overall system performance. The level of message transfer warrants
removing the card from service. Where: x = loop number and y = the rate of
message transfer from the card to the Meridian 1 (in terms of messages per
second).
Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 1240 of 2360

MISP0307 x data
MISP x encountered a fatal error. Where: x = loop number. The output data is
information read from the card regarding the error and is intended for design
use only.
Action:
Severity: Critical.
SNMP trap: No
MISP0308 x y appl da MISP x reported that it received a message with an invalid (bad) Socket
ID. Where: x = loop number y = socket ID appl = application name data = up
to eight words of hex data representing the message sent
Action:
Severity: Critical.
SNMP trap: No
MISP0451 <cardAddress> <cardIndex> <invalidCardstate> An invalid card state change

request from the SL1 task has been detected by the MMIH driver.
card.
Severity: Minor.
SNMP trap: No
MISP0452 <cardAddress> <cardIndex> The MMIH driver failed to send an SSD message to the
SL1 task.
for a system problem. If the condition persists contact your technical support
group.
Severity: Minor.
SNMP trap: No
MISP0453 <cardAddress> <cardIndex> The MMIH driver failed to send an RFC message to the
SL1 task.
group.
Severity: Minor.
SNMP trap: No
MISP0454 <cardAddress> <cardIndex> The MMIH driver failed to place a transmit expedited
Action: Disable and then enable the MSDL/MISP card. If the problem persists,
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1241 of 2360

MISP0455 <cardAddress> <cardIndex> The MMIH driver failed to send the Start UIPE Call
Rebuild message through RFC to the SL1 task.
Action: The call rebuild operation for that MSDL will fail. If necessary disable and
then enable the MSDL/MISP card. If the problem persists, contact your technical
support group.
Severity: Major.
SNMP trap: No
MISP0456 <blockSize> The MMIH driver failed when it allocated memory of the size blockSize
for the buffer pool. The system is probably out of memory and cannot
communicate with the MSDL/MISP cards.
Severity: Critical.
SNMP trap: No
MISP0457 <first 16 words of msg> the MMIH has found a buffer in the Rx Ring message queue
with an expired timestamp. The SL1 application has not processed the
buffer's content promptly or the SSD message to the SL1 task was lost. The
buffer's timestamp is reset and the buffer is returned as a free buffer. The first
16 words (32 bytes) of the discarded message are printed, 8 words to a line.
Action: Check the traffic report. Excessive traffic can cause a delay in the core
CPU.
Severity: Minor.
SNMP trap: No
MISP0458 <first 16 words of msg> The MMIH has found a buffer in the Tx Exp message queue
with an expired timestamp. The message timed out while being sent to the
card. The buffer is overwritten with the new message data. The first 16 words
(32 bytes) of the discarded message are printed, 8 words to a line.
Action: Disable and then enable the card. If the problem persists replace the
card.
Severity: Minor.
MISP0459
SNMP trap: No
The MMIH has found a null physical I/O block pointer. The I/O pointer is
corrupted and will prevent the system from communicating with the
MSDL/MISP cards.
Severity: Critical.
SNMP trap: No
System Messages
Page 1242 of 2360

MISP0460 <cardIndex> The MMIH driver has found that the card index is out of range. The card
index is corrupted and will prevent the system from communicating with the
MSDL/MISP card.
Severity: Major.
SNMP trap: No
MISP0461 <cardAddress> <rtclock> <maintenancePegs> A query base code message was

sent by the MMIH after finding the SRAM suspended. maintenancePegs is a
list of peg counts kept by the card's maintenance task.
card.
Severity: Info.
SNMP trap: No
MISP0462 <cardAddress> <rtclock> <msl1Pegs> This message is printed in series with

MISP0461. msl1Pegs is a list of peg counts kept by the card's SL1 messaging
interface task.
card.
Severity: Info.
SNMP trap: No
MISP0463 <cardAddress> <rtclock> <debugPegs> This message is printed in series with

MISP0462. debugPegs is a list of peg counts kept by the card's debug task.
card.
Severity: Info.
SNMP trap: No
MISP0464 <cardAddress> <rtclock> <utilityPegs> This message is printed in series with

MISP0463. utilityPegs is a list of pegs kept by the card's Layer 1 task.
card.
Severity: Info.
SNMP trap: No
MISP0465 <cardAddress> <rtclock> <returnCode> This message is printed in series with

MSDL0464. utilityPegs is a list of pegs kept by the card's utility task.
Action: Information only. If the problem persists, disable and then enable the
card.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1243 of 2360

MISP0466 <cardAddress> <rtclock> <returnCode> The Interface Audit's polling message
cannot be sent to the card's ring interface. The returnCode is the reason why
the message has not been sent. The following returnCode values can appear:
0 - request failed (null message pointer , empty data socket) 1 - request
succeeded 2 - no operation (invalid card state) 4 - flow control 5 - no buffer 6
- socket ID is suspended 7 - ring is not operational 8 - invalid socket ID
card.
Severity: Minor.
SNMP trap: No
MISP0467 <cardAddress> <cardIndex> <rtclock> The SRAM Suspend message cannot be

sent to the card through the expedited interface in response to two or more no
buffer conditions being detected in a timespan greater than 100 msec.
card or replace the card.
Severity: Minor.
SNMP trap: No
MISP0468 <cardAddress> <cardIndex> <rtclock> <returnCode> <socketId> <applicationID

'First 8 words of the msg'> The application's message cannot be sent to the
ring and the reason code is other than no buffer. socketID is the socket for the
message to be sent. applicationID identifies the transmitting application. The
first 8 words of the message are displayed in hex. ReturnCode contains the
actual value returned by the procedure and contains one of the following
values. 0 - request failed (null message pointer, empty data socket). 1 request succeeded 4 - flow control 5 - no buffer 6 - socket ID is suspended 7
- ring is not operational 8 - invalid socket ID
card.
Severity: Minor.
SNMP trap: No
MISP0469 <cardAddress> <cardIndex> <rtclock> A no buffer condition occurred because the

transmit ring is in the interface full state.
Severity: Info.
SNMP trap: No
System Messages
Page 1244 of 2360

MISP0470 <cardAddress> <cardIndex> <rtclock> A no buffer condition occurred because the
card has not yet sent an initialization acknowledgement response.
Severity: Info.
SNMP trap: No
MISP0471 <cardAddress> <cardIndex> <rtclock> <messageSize> A no buffer condition

occurred because a single buffer message is larger than the size of a single
buffer.
Action: Contact your technical support group. The buffer's data could be
corrupted.
Severity: Major.
SNMP trap: No
MISP0472 <cardAddress> <cardIndex> <rtclock> <messageSize> Insufficient buffers

available in the transmit ring for the message.
Severity: Info.
SNMP trap: No
MISP0474 <cardAddress> <cardIndex> <rtclock> <socketId> <applicationId> <'First 8 words

of the msg'> A no buffer condition has been encountered while attempting to
send a message to the transmit ring. The first 8 words of the message are
displayed in hex. The socketID is the socket for the message to be transmitted.
The applicationID is the application sending the message.
Severity: Info.
SNMP trap: No
MISP0475 <cardAddress> <cardIndex> <rtclock> <tempNoBufferCount totalNoBufferCount

rtclockOfFirstNoBuffer> <'60 Tx descriptor words'> This message is
printed when the first line of corrective action (suspending the transmit ring) is
taken. It displays the contents of the error detection variables and the
descriptor words of all buffers in the transmit ring. It is printed in series with
MSDL0476 and MSDL0477. The variables are:
tempNoBuffercount - number of consecutive no buffer occurrences since the
last successful write to the transmit ring.
totalNoBufferCount - total number of no buffer occurrences for the card.
553-3001-411
Standard 15.00
January 2006
Page 1245 of 2360

rtclockOfFirstNoBuffer - rtclock value at the time of the first no buffer
occurrence following the last successful write to the transmit ring.
descriptor words - all 60 descriptor words are printed (in hex), six to a line.
Action: Information for debugging only. The problem will clear automatically. If
this does not happen, disable and then enable the card.
Severity:
SNMP trap: No
MISP0476 <cardAddress> <cardIndex> <rtclock> <currentIndex descriptorBlockAddress>

<bufferSize> <numberOfBuffers> <transmitRingAddress> This message
displays pertinent variables kept by the MMIH driver for the transmit ring. It is
printed in series with MSDL0475 and MSDL0477. The variables printed are:
currentIndex - the MMIH's current index into the transmit ring's buffers (head
pointer) descriptorBlockAddress - offset of the descriptor block in the SRAM.
bufferSize - size of the buffers in the transmit ring. numberOfBuffers - number
of buffers in the transmit ring. transmitRingAddress - address of the transmit
ring in the card's SRAM. transmitRingState - current state of the transmit ring.
Action: Information for debugging only. Problem will clear automatically. If this
does not happen, disable and then enable the card.
Severity: Minor.
SNMP trap: No
MISP0477 <cardAddress> <cardIndex> <rtclock> <'44 SRAM configuration block words'>

This message displays the contents of the SRAM configuration block. It is
printed in series with MSDL0457 and MSDL0476. configuration words - all 44
descriptor words are printed (in hex), four to a line.
Action: Information for debugging only. Problem will clear automatically. If this
does not happen disable and then enable the card.
Severity: Minor.
SNMP trap: No
System Messages
Page 1246 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1247 of 2360
MPH: Meridian Packet Handler

Messages
MPH0000
No error on interface operation.

Action:
Severity: Info.
MPH0001
SNMP trap: No
Invalid info pointer passed to MPH_MAINT.

Action:
Severity: Minor.
MPH0003
SNMP trap: Yes
SNMP trap: Yes
Invalid loop.
Action:
Severity: Minor.
MPH0004
Invalid protected loop pointer.

Action:
Severity: Minor.
MPH0005
SNMP trap: Yes
Invalid unprotected loop pointer.

Action:
Severity: Minor.
MPH0006
SNMP trap: Yes
Invalid unprotected interface pointer.

Action:
Severity: Minor.
MPH0007
SNMP trap: Yes
SNMP trap: Yes
No MPH application.
Action:
Severity: Minor.
System Messages
Page 1248 of 2360

MPH0008
Invalid interface type.

Action:
Severity: Minor.
MPH0009
SNMP trap: Yes
SNMP trap: Yes
Invalid interface index.

Action:
Severity: Minor.
MPH0010
Invalid interface timeslot.

Action:
Severity: Minor.
MPH0011
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Invalid message ID.

Action:
Severity: Minor.
MPH0012
MPH Loop is disabled.

Action:
Severity: Minor.
MPH0013
MPH application is disabled.

Action:
Severity: Minor.
MPH0014
SNMP trap: Yes
MPH interface maintenance activity in progress.

Action:
Severity: Minor.
MPH0015
SNMP trap: Yes
Unable to obtain a Call Register for MPH maintenance.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1249 of 2360

MPH0016
Invalid MPH maintenance progress marker.

Action:
Severity: Minor.
MPH0017
SNMP trap: Yes
Time out: MPH maintenance activity has taken too long.

Action:
Severity: Minor.
MPH0021
SNMP trap: Yes
No buffer available to send message.

Action:
Severity: Minor.
MPH0022
SNMP trap: Yes
Unable to send message.

Action:
Severity: Minor.
MPH0023
SNMP trap: Yes
Interface is not in manual disabled state.

Action:
Severity: Minor.
MPH0024
SNMP trap: Yes
Invalid MPH maintenance sub-progress marker.

Action:
Severity: Minor.
MPH0025
SNMP trap: Yes
Interface is in manual disabled state.

Action:
Severity: Minor.
MPH0030
SNMP trap: Yes
The interface TN is undefined.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1250 of 2360

MPH0031
Invalid interface state change.

Action:
Severity: Minor.
MPH0032
SNMP trap: Yes
Build interface dedicated connection failed.

Action:
Severity: Minor.
MPH0033
SNMP trap: Yes
MPH maintenance message timeout.

Action:
Severity: Minor.
MPH0035
SNMP trap: Yes
Invalid interface maintenance request.

Action:
Severity: Minor.
MPH0036
SNMP trap: Yes
Unable to send message to MISP.

Action:
Severity: Minor.
MPH0037
SNMP trap: Yes
Error indication received: interface enable/disable failed.

Action:
Severity: Minor.
MPH0041
SNMP trap: Yes
Download interface data failed.

Action:
Severity: Minor.
MPH0042
SNMP trap: Yes
Download interface data timeout.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1251 of 2360

MPH0043
Unable to download.
Action:
Severity: Minor.
MPH0045
SNMP trap: Yes
Download TSP data failed.

Action:
Severity: Minor.
MPH0046
SNMP trap: Yes
Download TSP data timeout.

Action:
Severity: Minor.
MPH0047
SNMP trap: Yes
Download DNA Table failed.

Action:
Severity: Minor.
MPH0048
SNMP trap: Yes
Download DNA Table timeout.

Action:
Severity: Minor.
MPH0049
SNMP trap: Yes
Download D-ch TSP data timeout.

Action:
Severity: Minor.
MPH0050
SNMP trap: Yes
Download D-ch TSP data failed.

Action:
Severity: Minor.
MPH0061
SNMP trap: Yes
D-ch interface enable timeout.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1252 of 2360

MPH0062
D-ch interface enable failed.

Action:
Severity: Minor.
MPH0063
SNMP trap: Yes
D-ch interface disable timeout.

Action:
Severity: Minor.
MPH0064
SNMP trap: Yes
D-ch interface disable failed.

Action:
Severity: Minor.
MPH0200
SNMP trap: Yes
Unsolicited response for DCH/BCH term state update.

Action:
Severity: Minor.
MPH0201
SNMP trap: Yes
Indication message received for maintenance pending message.

Action:
Severity: Minor.
MPH0202
SNMP trap: Yes
Conference message received for maintenance pending message.

Action:
Severity: Minor.
MPH0203
SNMP trap: Yes
Indication message received for clear maintenance pending message.

Action:
Severity: Minor.
MPH0204
SNMP trap: Yes
Conference message received for clear maintenance pending message.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1253 of 2360

MPH0205
Response message for state update message for undefined IF.

Action:
Severity: Minor.
MPH0206
SNMP trap: Yes
Response message for status request message for undefined IF.

Action:
Severity: Minor.
MPH0207
SNMP trap: Yes
Indication message for status request message.

Action:
Severity: Minor.
MPH0208
SNMP trap: Yes
Conference message for status request message.

Action:
Severity: Minor.
MPH0209
SNMP trap: Yes
Response message for error log upload request.

Action:
Severity: Minor.
MPH0210
SNMP trap: Yes
Unsolicited response for NWIF, SAPI16 IF state change.

Action:
Severity: Minor.
MPH0215
SNMP trap: Yes
Received indication message for audit request message.

Action:
Severity: Minor.
MPH0300
SNMP trap: Yes
MPH application data has downloaded.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1254 of 2360

MPH0301
L2 protocol has downloaded.

Action:
Severity: Minor.
MPH0302
SNMP trap: Yes
L3 protocol has downloaded.

Action:
Severity: Minor.
MPH0303
SNMP trap: Yes
Interface Data has downloaded.

Action:
Severity: Info.
MPH0304
SNMP trap: Yes
MPH TSP data has downloaded.

Action:
Severity: Minor.
MPH0305
SNMP trap: Yes
PVC data has downloaded.

Action:
Severity: Minor.
MPH0306
SNMP trap: Yes
DNA data has downloaded.

Action:
Severity: Minor.
MPH0307
SNMP trap: Yes
TFC data has uploaded.

Action:
Severity: Minor.
MPH0308
SNMP trap: Yes
Indication message received for DSL LAPD table number change message.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1255 of 2360
MRB: Message Registration Block

MRB messages are output in response to commands or prompts/responses
related to the Message Registration feature.
Messages
System Messages
Page 1256 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1257 of 2360
MSDL: Multi-purpose Serial Data Link

The MSDL provides four ports for applications such as
ISDN Primary Rate D-channel (DCH)
Application Module Link (AML)
Input/output devices (TTY)
The MSDL messages report problems with the MSDL card and its
applications. MSDL commands are provided in LD 37, LD 48, and LD 96.
Messages
MSDL0001
The number of parameters for the MSDL command is incorrect.

Action:
Severity: Info.
MSDL0002
SNMP trap: Yes
The card number in the command is out-of-range or invalid.

Action:
Severity: Info.
MSDL0003
SNMP trap: Yes
Since this command is only valid for use on the MSDL card in this Overlay, the
first parameter must be MSDL.
Action:
Severity: Info.
MSDL0004
SNMP trap: Yes
Cannot reset the card (or execute self-tests) right now because the card is not
in Manually Disabled state (MAN DSBL).
Action:
Severity: Info.
MSDL0005
SNMP trap: Yes
Failed to reset; could not write command to card. Card is probably not present,
or the (address) switch settings on the card do not agree with the database.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1258 of 2360

MSDL0006
Cannot enable the card unless it is in Manually Disabled (MAN DSBL) state.
Action:
Severity: Minor.
MSDL0007
SNMP trap: Yes
Cannot disable card unless it is in the Enabled (ENBL) state.

Action:
Severity: Minor.
MSDL0008
SNMP trap: Yes
Cannot reset the card (or execute self-tests) on the card right now since the
device enabled bit is set, meaning a message response is currently pending.
Action: Attempt the self test command again; when the response pending
condition clears, as long as the card is Manually Disabled, the reset (and self
tests) should execute.
Severity: Minor.
MSDL0011
SNMP trap: Yes
No response received to the enable card command.

Action:
Severity: Minor.
MSDL0012
SNMP trap: Yes
The response message from the card to the Overlay indicates failure to
enable/disable.
Action:
Severity: Critical.
MSDL0014
SNMP trap: Yes
No response received to the disable card command. The card is set to the
Manually Disabled (MAN DSBL) state anyway.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1259 of 2360

MSDL0015
The command entered requires that a message be sent to the MSDL. The
Meridian 1 was unable to build the message since the buffer was not free. Try
again later. If this message continues to be generated, then:
Action: If the card is enabled, wait for a few minutes, as the card may have
encountered a problem that warrants recovery, or if the card is manually disabled,
reset the card using the RST MSDL x command, or execute self tests using the
SLFT MSDL x command.
Severity: Minor.
MSDL0016
SNMP trap: Yes
Failed enable attempt. If this message is not accompanied by any other error
message, the card may be in the process of performing self-tests or the
self-tests may have already failed.
Action: Wait a few minutes, then execute the self-tests with the SLFT MSDL x
command. If self-tests pass, try to enable the card again.
Severity: Critical.
MSDL0017
SNMP trap: Yes
At least one of the ports on the MSDL is currently enabled. Disabling the card
is disallowed when ports are enabled unless the DIS MSDL x ALL command
is used.
Action:
Severity: Minor.
MSDL0018
SNMP trap: Yes
The fourth parameter of the command is unrecognized or unimplemented.

Action:
Severity: Minor.
MSDL0019
SNMP trap: Yes
The command entered required that information be read from the MSDL. The
specified MSDL is not present in the system, and the information could not be
read.
Action:
Severity: Minor.
MSDL0020
SNMP trap: Yes
The command entered required that the application information block on the
MSDL be read by the Meridian 1. The block is currently being updated by the
MSDL, and the system could not read the block.
Action: Try again.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1260 of 2360

MSDL0021
Began to download the MSDL basecode but stopped before finishing. There
should be an accompanying SDL error message, so refer to the information on
that message for the failure reason.
Action:
Severity: Critical.
MSDL0022
SNMP trap: Yes
The rest of the information output in response to this command is resident on

the card. The card is not enabled, and the information cannot be read.
Action:
Severity: Minor.
MSDL0024
SNMP trap: Yes
The Meridian 1 began to download an MSDL application but stopped before

finishing.
Action: There should be an accompanying SDL error message, so refer to the
information on that message for the failure reason.
Severity: Critical.
MSDL0025
SNMP trap: Yes
There is currently maintenance activity on the application in question.

Action: Wait a few minutes and try again.
Severity: Minor.
MSDL0026
SNMP trap: Yes
Disabling the MSDL when the active TTY is supported by it is not allowed.
Action:
Severity: Minor.
MSDL0027
SNMP trap: Yes
Time out waiting for the self tests to complete.

Action: Wait at least five minutes, then try again. Under certain unusual
circumstances, self-tests can take approximately five minutes; however, this
should only occur when the flash EPROM on the card is new or has been
completely erased.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1261 of 2360

MSDL0028
Cannot enable the card because it is not present in the system.

Action: If the card in question is believed to be present, check if the switch
settings on the card agree with the device number entered in this command.
Severity: Minor.
MSDL0029
SNMP trap: Yes
Incorrect password entered in response to the ENL MSDL x DBG command.

Action:
Severity: Minor.
MSDL0030
SNMP trap: Yes
The debug option for this card has already been turned on.
Action:
Severity: Minor.
MSDL0031
SNMP trap: Yes
The ENL MSDL x ALL command is only valid when the MSDL is in the ENBL
or MAN DSBL state.
Action:
Severity: Minor.
MSDL0032
SNMP trap: Yes
The MSDL card was removed from its slot, or the card reset itself during the
self-tests.
Action: If the card was removed, execute the self-tests again and do not remove
the card from its slot until the tests are complete. If the card was not removed,
execute the self-tests again. If this message appears more than twice, replace the
MSDL card.
Severity: Critical.
MSDL0033
SNMP trap: Yes
Device locked by the Russian Call Monitoring feature. The MSDL card cannot
be enabled or disabled.
Severity: Minor.
MSDL0034
SNMP trap: Yes
Group number in command is out of range or invalid.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1262 of 2360

MSDL0035
Unequipped physical I/O address in the specified network group.

Action:
Severity: Info.
MSDL0036
SNMP trap: Yes
The network group number must be specified.

Action:
Severity: Info.
MSDL0100 x
SNMP trap: Yes
The CSTAT and CSUBSTAT fields on MSDL x indicate the card is Manually
the System Disabled - Self- tests Passed state, and within the next few
minutes, the Meridian 1 will attempt to enable the card.
Action:
Severity: Critical.
MSDL0101 x
SNMP trap: Yes
The CSTAT field on MSDL x indicates the card is no longer Enabled. The
MSDL302.
Action:
Severity: Critical.
MSDL0102 x
SNMP trap: Yes
No response was received from MSDL x to a background polling message

sent periodically to each MSDL card. The purpose of this message is to ensure
that the card is capable of receiving and sending messages.
Action:
Severity: Critical.
MSDL0103 x
SNMP trap: Yes
An Overlay was waiting for a message from MSDL x. Most likely, the Overlay
is no longer loaded. The message the Overlay was waiting for was never
received.
Action:
Severity: Critical.
MSDL0105
553-3001-411
SNMP trap: Yes
The CSTAT value read from the MSDL is invalid. This indicated one of two
error conditions: 1. The card has encountered a severe hardware fault so that
it is unable to report the error to the Meridian 1.
Standard 15.00
January 2006
Page 1263 of 2360

2. There may be multiple cards in the system with the same device number
(switch settings) as the MSDL. When the CSTAT is read from the MSDL, it
may not be the MSDL card that is responding.
Action: Be sure no other cards in the system share the device number. If so,
change the device numbers. If not, replace the card.
Severity: Critical.
MSDL0106 x appl
SNMP trap: Yes
The MSDL audit detected that there was no response to a maintenance

message originated by an application (appl) on MSDL x.
Action:
Severity: Critical.
SNMP trap: Yes
MSDL0107 x appl y The Meridian 1 was unable to determine if downloading was necessary. An
for the failure. Three fields accompany this message: x = device number (LD
17 DNUM), appl = the application name, and y is for design use only.
Action:
Severity: Critical.
MSDL0108 x appl
SNMP trap: Yes
An application on MSDL x needs to be downloaded to the card. Downloading

begins as soon as there is no Overlay loaded. Where: x = device number (LD
17 DNUM) and appl = the application name.
Action:
Severity: Critical.
MSDL0112 x
SNMP trap: Yes
MSDL x has been reset in order to begin automatic recovery. Immediately

finished, provided they pass, the Meridian 1 will attempt to enable the card.
Where: x = device number (LD 17 DNUM).
Action:
Severity: Critical.
MSDL0201 x appl
SNMP trap: Yes
MSDL x sent a message to the Meridian 1 indicating an application data space

has been corrupted. Where: x = device number (LD 17 DNUM) and appl = the
application name.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1264 of 2360

MSDL0202 x appl
MSDL x sent a message to the Meridian 1 indicating that an application on the

card unexpectedly disabled itself (performed a "close"). Where: x = device
number (LD 17 DNUM) and appl = the application name.
Action:
Severity: Critical.
MSDL0204 x appl
SNMP trap: Yes
MSDL x and found none. Where: x = device number (LD 17 DNUM) and appl
= the application name.
Action:
Severity: Critical.
SNMP trap: Yes
MSDL0205 x appl y z An error was encountered when searching the system disk to find a version
of an application for MSDL x. Refer to an accompanying SDL error message
for the exact error reason. This message indicates that the Meridian 1 will
attempt to enable the application in question if a version exists on the card.
Where: x = device number (LD 17 DNUM) and appl = the application name. (y
and z are for design use only)
Action:
Severity: Critical.
SNMP trap: Yes
MSDL0206 x appl y z An error was encountered when comparing a version of an application on

the system disk with the version on MSDL x. Where: x = device number (LD
17 DNUM) and appl = the application name. (y and z are for design use only)
application if a version exists on the card.
Severity: Critical.
SNMP trap: Yes
MSDL0207 x appl y z An error was encountered when downloading an application to MSDL x.

Where: x = device number (LD 17 DNUM) and appl = the application name. (y
and z are for design use only)
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1265 of 2360

MSDL0208 x
When preparing to download the base software to MSDL x, the card indicated
that some kind of fatal error was encountered. Where: x = device number (LD
17 DNUM).
Action: Execute self-tests before attempting any other action regarding this
card.
Severity: Critical.
MSDL0209 x y z
SNMP trap: Yes
on MSDL x requested that a buffer pool be freed. When this occurred, there
was at least one outstanding buffer. The basecode waited for the buffer(s) to
be returned to the pool before freeing the buffers, but it never returned. The
buffer pool was forcibly freed by the basecode. Where: x = device number (LD
17 DNUM) (y and z are for design use only).
Action:
Severity: Critical.
MSDL0210
SNMP trap: Yes
Failed to enable the MSDL for one of the following reasons:

The card in question is not an MSDL card. For example, there may be a card
in the system with switch settings that correspond to the MSDL, but is in fact
not an MSDL card.
There is at least one other card in the system with switch setting identical to
the MSDLs.
Action: Remove the card with the same device number as the MSDL.
Severity: Critical.
SNMP trap: Yes
MSDL0211 DO NOT PRINT An attempt to enable the T1E1 application during ENLL, timed out.
Action: RST TMDI in overlay 96 and then try again.
Severity: Info.
SNMP trap: No
MSDL0212 DO NOT PRINT The TMDI card could not enable the T1E1 application.
Severity: Info.
SNMP trap: No
MSDL0213 DO NOT PRINT The T1E1 application is in a transient stte and could note be enabled.
Action: Wait and then try ENLL again.
Severity: Info.
SNMP trap: No
System Messages
Page 1266 of 2360

MSDL0214 DO NOT PRINT A request to enable the DTI port has failed.
Severity: Info.
SNMP trap: No
MSDL0215 DO NOT PRINT A request to disable the DTI port on the TMDI failed.
Severity: Info.
MSDL0300 data
SNMP trap: No
The MSDL background audit has changed the card state. In the cases where
the card was previously enabled and now is no longer enabled, another MSDL
message will indicate the reason for the state change. When making a state
transition due to a fatal error on the card, the reason for the fatal error is
displayed in this message. This is an informational message and requires no
action by the craftsperson.
Output data: MSDL300 x FROM: aaaa TO: bbbb TIME time REASON cccc
Where:
x = MSDL card number (in decimal)
aaaa = the status of the MSDL prior to the state change
bbbb = the state of the card after the state change
time = the time of the state change
cccc = reason for the error (only when "TO: SYS DSBL - FATAL ERROR")
Action:
Severity: Critical.
MSDL0303 x y
SNMP trap: Yes
ring or both, causing access to the memory space shared by the Meridian 1
CPU and MSDL x (Shared RAM) to be momentarily suspended.
Take no action because of this message; however, it indicates that message
transfer between the Meridian 1 and the card ceased momentarily.
Where: x = device number (LD 17 DNUM) and y = a decimal number indicating
where the corruption was detected. 1 means receive ring, 2 means transmit
ring, and 3 means both receive and transmit rings.
Action:
Severity: Critical.
MSDL0304 x y
553-3001-411
SNMP trap: Yes
The Meridian 1 received 100 or more messages from MSDL x within two
overall system performance. The level of service does not warrant removing
Standard 15.00
January 2006
Page 1267 of 2360

the card from service. Where: x = device number (LD17 DNUM) y = the rate
of message transfer from the card to the Meridian 1, in terms of messages per
second.
Action:
Severity: Major.
MSDL0305 x y
SNMP trap: Yes
The Meridian 1 received 200 or more messages from MSDL x within two
removing the card from service.
Where:
x = device number (LD 17 DNUM)
y = the rate of message transfer from the card to the Meridian 1, in terms of
Action:
Severity: Critical.
MSDL0306 x y
SNMP trap: Yes
The Meridian 1 has received 300 or more messages from MSDL x within two
seconds. Card put into Lockout for overload protection.
Where x = device number (LD 17 DNUM) y = the rate of message transfer
from the card to the Meridian 1, in terms of messages per second.
Action:
Severity: Critical.
MSDL0307 x data
SNMP trap: Yes
MSDL x encountered a fatal error. Where: x = device number (LD 17 DNUM).

is intended for design use only.
Action:
Severity: Critical.
SNMP trap: Yes
MSDL0308 x y appl data MSDL x reported that it received a message with an invalid (bad) socket
ID. Where:
y = the socket ID
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1268 of 2360

MSDL0309 DO NOT PRINT The TMDI output buffer is still in queue.
Action: Try the operation again, or RST TMDI in overlay 96.
Severity: Info.
SNMP trap: No
MSDL0310 DO NOT PRINT The TMDI output has not been sent to the card.
Action: Try the operation again or RST TMDI in overlay 96.
Severity: Info.
MSDL0450
SNMP trap: No
When an SDI port is configured on an MSDL and the Meridian 1 initializes, it

may be discovered, during initialization, that the MSDL basecode or SDI
application needs to be downloaded. If so, there will be a period of time
following the INIT (1 to 5 minutes) where the SDI port will not function. The port
automatically enables itself once downloading has completed.
Action:
Severity: Critical.
SNMP trap: No
MSDL0451 <cardAddress> <(cardIndex)> <invalidCardstate> An invalid card state change

request from the SL1 task has been detected by the MMIH dxriver.
card.
Severity: Minor.
SNMP trap: Yes
MSDL0452 <cardAddress> <cardIndex> The MMIH driver failed to send an SSD message to
the SL1 task.
group.
Severity: Minor.
SNMP trap: Yes
MSDL0453 <cardAddress> <cardIndex> The MMIH driver failed to send an RFC message to
the SL1 task.
group.
Severity: minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1269 of 2360

MSDL0454 <cardAddress> <cardIndex> The MMIH driver failed to place a transmit expedited
Action: Disable and then enable the MSDL/MISP card. If the problem persists
Severity: Minor.
SNMP trap: Yes
MSDL0455 <cardAddress> <cardIndex> The MMIH driver failed to send the Start UIPE Call
Action: The call rebuild operation for that MSDL will fail. If necessary, disable
and then enable the MSDL/MISP card. If the problem persists contact your
Severity: Major.
SNMP trap: Yes
MSDL0456 <blockSize> The MMIH driver failed when it allocated memory of the size blockSize
for the buffer pool. The system is probably out of memory and cannot
communicate with the FIJI/MSDL/MISP cards.
Severity: Critical.
SNMP trap: Yes
MSDL0457 <first 16 words of msg> The MMIH has found a buffer in the Rx Ring message
queue with an expired timestamp. The SL1 application has not processed the
buffer's content promptly or the SSD message to the SL1 task was lost. The
buffer's timestamp is reset and the buffer is returned as a free buffer. The first
16 words (32 bytes) of the discarded message are printed, 8 words to a line.
Action: Check the traffic reports. Excessive traffic can cause a delay in the core
CPU.
Severity: Minor.
SNMP trap: Yes
MSDL0458 <first 16 words of msg> The MMIH has found a buffer in the Tx Exp message queue
card. The buffer is overwritten with the new message data. The first 16 words
card.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1270 of 2360

MSDL0459
corrupted and will prevent the system from communicating with the
FIJI/MSDL/MISP cards.
Severity: Critical.
SNMP trap: Yes
MSDL0460 <cardIndex> The MMIH driver has found that the card index is out of range. The card
FIJI/MSDL/MISP cards.`
Severity: Major.
SNMP trap: Yes
MSDL0461<cardAddress rtclock maintenancePegs> A query base code message was sent by

the MMIH after finding the SRAM suspended. maintenancePegs is a list of peg
counts kept by the card's maintenance task.
Action: Information only. If the problem persists, disable and the enable the
card.
Severity: Info.
SNMP trap: Yes
MSDL0462 <cardAddress rtclock Msl1Pegs> This message is printed in series with

MSDL0461. msl1Pegs is a list of peg counts kept by the card's SL1 messaging
interface task.
card.
Severity: Info.
SNMP trap: Yes
MSDL0463 <cardAddress rtclock debugPegs> This message is printed in series with

MSDL0462. debugPegs is a list of peg counts kept by the card's debug task.
card.
Severity: Info.
SNMP trap: Yes
MSDL0464 <cardAddress rtclock utilityPegs> This message is printed in series with

MSDL0463. utilityPegs is a list of pegs kept by the card's utility task
card.
Severity: info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1271 of 2360

MSDL0465 <cardAddress rtclock layer1Pegs> This message is printed in series with
MSDL0464. layer1Pegs is a list of pegs kept by the card's Layer 1 task.
card.
Severity: Info.
SNMP trap: Yes
MSDL0466 <cardAddress rtclock returnCode> The Interface Audit's polling message cannot
be sent to the card's ring interface. The returnCode is the reason why the
message has not been sent. The following returnCode values can appear:
0-request failed (null message pointer, empty data socket) 1-request
succeeded 2-no operation (invalid card state) 4-flow control 5-no buffer
6-socket ID is suspended 7-ring is not operational 8-invalid socket ID
card.
Severity: Minor.
SNMP trap: Yes
MSDL0467 <cardAddress> <cardIndex> <rtclock> The SRAM Suspend message cannot be

sent to the card through the expedited interface in response to two or more no
buffer conditions being detected in a timespan greater than 100 msec.
card, or replace the card.
Severity: Minor.
SNMP trap: Yes
MSDL0468 <cardAddress> <cardIndex> <rtclock> <returnCode> <socketId application>

<'First 8 words of the msg'> The application's message cannot be sent to the
ring and the reason code is other than no buffer. SocketID is the socket for the
message to be sent
applicationID identifies the transmitting application The first 8 words of the
message are displayed in hex return code contains the actual value returned
by the procedure and contains one of the following values:0-request failed
(null message pointer, empty data socket)1-request succeeded 4-flow control
5-no buffer
-socket ID is suspended 7-ring is not operational
-invalid socket ID
card.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1272 of 2360

MSDL0469 <cardAddress> <cardIndex> <rtclock> A no buffer condition occurred because the
transmitting ring is in the interface full state.
Severity: Info.
SNMP trap: Yes
MSDL0470 <cardAddress> <cardIndex> <rtclock> A no buffer condition occurred because the

Severity: Info.
SNMP trap: Yes
MSDL0471 <cardAddress> <cardIndex> <rtclock messageSize> A no buffer condition

occurred because a single buffer message is larger than the size of a single
buffer.
corrupted.
Severity: Major.
SNMP trap: Yes
MSDL0472 <cardAddress> <cardIndex> <rtclock messageSize> Insufficient buffers available

in the transmit ring for the message.
Severity: Info.
SNMP trap: Yes
MSDL0474 <cardAddress> <cardIndex> <rtclock> <socketId application> <'First 8 words of

the msg'> A no buffer condition has been encountered while attempting to send
a message to the transmit ring. The first 8 words of the message are displayed
in hex.
The socketID is the socket for the message to be transmitted.
The applicationID is the application ID of the application sending the message.
Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1273 of 2360

MSDL0475 <cardAddress><cardIndex><rtclock> <tempNoBufferCount>
<rtclockOfFirstNoBuffer> Six to a line.
Action: Information for debugging only. If the problem does not clear
automatically disable and then enable the card. Minor 10/16/98 00/00/00
Severity: Info.
SNMP trap: Yes
MSDL0476 <cardAddress> <cardIndex>< rtcloc>k currentIndex>

<descriptorBLockAddress> <bufferSize> <numberOfBuffers>
<transmitRing Address> <transmitRingState> This message displays
pertinent variables kep by the MMIH driver for the transmit ring. It is printed in
series with MSDL0475 and MSDL0477. The variables printed are:
6currentIndex - the MMIH's current index into the transmit ring's buffers (head
pointer)
descriptorBlock Address - offset of the descriptor block in the SRAM
bufferSize - size of the buffers in the transmit ring
numberOfBuffers - number of buffers in the transmit ring
transmitRingAddress - address of the transmit ring in the card's SRAM
transmitRingState - current state of the transmit ring
automatically, disable and then enable the card.
Severity: Minor.
SNMP trap: Yes
MSDL0477 <cardAddress> <cardIndex> rtclock '44SRAM configuration Block words' This

message displays the contents of the SRAM configuration block. It is printed
in series with MSDL0475 and MSDL0476. - configuration words - all 44
descriptor words are printed (in hex), four to a line.
Severity: Minor.
MSDL0485
SNMP trap: Yes
The Meridian1 received 200 or more messages from the MSDL port. Port put
into Lockout for overload protection.
Action: Identify the cause of the problem. Manually disable the AML, SDI or DCH
configured on the MSDL port with one of the following commands: DIS AML x; for
an AML Link, DIS TTY x; for an SDI or DIS DCH x; for a D channel. Enable the
port with one of the following commands: ENL AML x; for an AML Link, ENL TTY
x; for an SDI or ENL DCH x; for a D channel.
Severity: Major.
SNMP trap: No
System Messages
Page 1274 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1275 of 2360
MWL: Message Waiting Lamps Reset (LD

61)
The Message Waiting Lamps Reset program (LD 61) can be invoked
automatically by the system as part of the daily routines or manually from an
input device. It is used to deactivate all active Message Waiting lamps on user
stations and reset the associated status in the system. Problems are identified
in MWL messages.
The program does not reset lamp status unless all message center sets are
out-of-service. For instance, the message center is closed and attendants are
in Night Service.
This program cannot be applied to digital sets.
When LD 61 is loaded manually, 'G' is entered to initiate the task.
Messages
MWL0000
Program has been loaded.

Action:
Severity: Info.
MWL0001
SNMP trap: Yes
Invalid command.
Action: Re-enter the command.
Severity: Info.
MWL0002
SNMP trap: Yes
Cannot deactivate MW lamps until all MC agents out-of-service.

Action: Take all MC out-of-service if possible.
Severity: Info.
MWL0003
SNMP trap: Yes
Cannot deactivate MW lamps until all attendants in Night Service.

Action: Take all MC attendants out-of-service. Operate night key.
Severity: Info.
SNMP trap: Yes
System Messages
Page 1276 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1277 of 2360
NACD: Network Automatic Call

Distribution
The NACD messages are output in the following format: NACDxxx c d t r
Where:
c = customer number
d = source ACD-DN for which the request was made
t = 0 for the Night table; t = 1 for the Day table
r = Remote target ID
Messages
NACD0001
No memory available for the Source Tables. A data base request was received
that could not be honored because of insufficient memory.
Action: Memory capacity can be increased in LD 29.
Severity: Minor.
NACD0002 c d t r
SNMP trap: Yes
Timeout occurred while attempting the data base request.Link failure between
nodes. Network congestion during peak traffic time. Target DN does not exist
Request messages have been lost.
Action:
Severity: Minor.
NACD0003 c d t r
SNMP trap: Yes
Transaction successful. The Remote Target ACD-DN can now receive

rerouted calls, depending on the queue status at the Target node.
Action:
Severity: Minor.
NACD0004 c d t r
SNMP trap: Yes
Transaction denied. The ACD network application is not supported at the

Target node specified.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1278 of 2360

NACD0005 c d t r
Transaction denied. The Target does not have enough memory, or does not
exist.
Action:
Severity: Minor.
NACD0006 c d t r
SNMP trap: Yes
Transaction denied. Protocol failed at the far-end. Possible that the system
has Initialized.
Action:
Severity: Minor.
NACD0007 c d t r
SNMP trap: Yes
Transaction aborted. Cannot find the proper D-channel to send the request.
Action:
Severity: Minor.
NACD0008 c d t r
SNMP trap: Yes
Transaction aborted. Cannot find the transaction number for the system.
Action:
Severity: Minor.
NACD0009 c d t r
SNMP trap: Yes
Transaction aborted. The system cannot build the origination number.
Action:
Severity: Minor.
NACD0010 c d t r
SNMP trap: Yes
Transaction failed. The system cannot send the required messages.
Action:
Severity: Minor.
NACD0012 c d t r
SNMP trap: Yes
A data base Delete message was received.
Action:
Severity: Minor.
NACD0013 c d t r
SNMP trap: Yes
A data base request was sent.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1279 of 2360

NACD0014 c d t r
This node is unable to communicate with the Source node. This ACD-DN's
Target entry is not registered at the Source node's routing table.
Action: Remove this entry and re-enter the correct Target ACD-DN in the
Source node's routing table.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1280 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1281 of 2360
NCT: Network Call Trace

The Network Call Trace feature traces network calls and diagnoses network
problems. When a network call is blocked, trace data is output indicating the
reason the call was blocked and the software procedure responsible.
A network call can be traced by dialing a SPRE code and the NCT feature
code (9912) before the network number. When this is done, call setup and
status information is output to the system terminal as the call tandems through
the network. The trace information is output to the all system terminals
designated in LD 17 as ADAN = TTY and USER = MTC.
NCT provides the following types of information:
the route used
the facility accessed
the routing control imposed
the call-blocked location
There are two Network Call Trace functions: 01 and 02. They output different
information as shown in the following sections.
Messages
NCT0001
Procedure INIT_NARS_FEATUR fails (i.e., return value is .FALSE). Module:

NARS. Procedure: NARS_MODULE.
Action:
Severity: Info.
NCT0002
SNMP trap: No
Procedure NARS_TIMESLICE fails (i.e., return value is .FALSE). Module:

NARS. Procedure: NARS_MODULE.
Action:
Severity: Info.
NCT0003
SNMP trap: No
Invalid NARS translation - case 0 of CASE statement. Module: NARS.

Procedure: NARS_TRANS.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1282 of 2360

NCT0004
Number of digits >= maximum level of translator - case 2 of CASE statement.

Module: NARS. Procedure: NARS_TRANS.
Action:
Severity: Info.
NCT0005
SNMP trap: No
Incomplete translation but # has been dialed - case 2 of CASE statement.

Module: NARS. Procedure: NARS_TRANS.
Action:
Severity: Info.
NCT0006
SNMP trap: No
# has been dialed before all the expected digits have been received.
Module: NARS. Procedure: NARS_GET_EXP_DGT.
Action:
Severity: Info.
NCT0007
SNMP trap: No
# has been dialed in the middle of all the expected digits received. Module:
NARS. Procedure: NARS_GET_EXP_DGT.
Action:
Severity: Info.
NCT0008
SNMP trap: No
Invalid translation type - case 0 of CASE statement. Module: NARS.

Procedure: NARS_EXAM_DATA.
Action:
Severity: Info.
NCT0009
SNMP trap: No
Translation type is Local Steering Code - case 8 of CASE statement. Module:

NARS. Procedure: NARS_EXAM_DATA.
Action:
Severity: Info.
NCT0010
SNMP trap: No
Translation type 12 is not defined - case 12 of CASE statement. Module:

NARS. Procedure: NARS_EXAM_DATA.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1283 of 2360

NCT0011
HNPA was dialed in a previous translation. Module: NARS. Procedure:

NARS_LOC_RTE_IND.
Action:
Severity: Info.
NCT0012
SNMP trap: No
LOCATION LDN block does not exist. Module: NARS. Procedure:

NARS_LOC_RTE_IND.
Action:
Severity: Info.
NCT0013
SNMP trap: No
The SDR block does not exist. Module: NARS. Procedure:

NARS_LOC_RTE_IND.
Action:
Severity: Info.
NCT0014
SNMP trap: No
Incoming trunk group exclusion (ITGE) has blocked the call. Module: NARS.
Procedure: NARS_LOC_RTE_IND.
Action:
Severity: Info.
NCT0015
SNMP trap: No
A match of the restricted code was not found, but ITGE blocked the call.
Module: NARS. Procedure: NARS_DGT_RESTR.
Action:
Severity: Info.
NCT0016
SNMP trap: No
A match of the restricted code was not found, but STRK blocked the call.
Action:
Severity: Info.
NCT0017
SNMP trap: No
A match of the restricted code was found. Module: NARS. Procedure:

NARS_DGT_RESTR.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1284 of 2360

NCT0018
A match of distant recognized DID code was found, but ITGE blocked the call.
Action:
Severity: Info.
NCT0019
SNMP trap: No
A match of distant recognized DDD code was found, but ITGE blocked the call.
Action:
Severity: Info.
NCT0020
SNMP trap: No
A match of incoming trunk group exclusion digits was found, but ITGE blocked
the call. Module: NARS. Procedure: NARS_DGT_RESTR.
Action:
Severity: Info.
NCT0021
SNMP trap: No
A match of incoming trunk group exclusion digits was found, but there is no
ITEI. Module: NARS. Procedure: NARS_DGT_RESTR.
Action:
Severity: Info.
NCT0022
SNMP trap: No
LDID with incorrect SDR type. Module: NARS. Procedure:

NARS_DGT_RESTR.
Action:
Severity: Info.
NCT0023
SNMP trap: No
No SDRR entry, but ITGE blocked the call. Module: NARS. Procedure:
NARS_DGT_RESTR.
Action:
Severity: Info.
NCT0024
SNMP trap: No
NARS_HNPA_FLAG is set which implies that translation tables have been

switched previously. Module: NARS. Procedure: NARS_BARS_HNPA.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1285 of 2360

NCT0025
NARS_HNPA_FLAG is set which implies that translation tables have been

switched previously. Module: NARS. Procedure: NARS_HLOC_CODE.
Action:
Severity: Info.
NCT0026
SNMP trap: No
Accessing a network speed call list is not allowed or the speed call list is not a
valid one. Module: NARS. Procedure: NARS_SPEED_CALL.
Action:
Severity: Info.
NCT0027
SNMP trap: No
DNTRANS is incomplete, but NARS_EOD_FLAG is set. Module: NARS.

Procedure: NARS_CDP_HOME.
Action:
Severity: Info.
NCT0028
SNMP trap: No
Route type is not TIE/ADM/MOD 500 - a sub-procedure of

NARS_CDP_HOME. Module: NARS. Procedure: CHECK_FOR_CO.
Action:
Severity: Info.
NCT0029
SNMP trap: No
Invalid DNTRANS for CDP home code - a sub-procedure of

NARS_CDP_HOME. Module: NARS. Procedure: BLOCK_THE_CALL.
Action:
Severity: Info.
NCT0030
SNMP trap: No
Redirection counter has exceeded the threshold for ISDN call. Module: NARS.
Procedure: INITIAL_ROUT_SEL.
Action:
Severity: Info.
NCT0031
SNMP trap: No
Network Authcode Last has been activated. Module: NARS. Procedure:

INITIAL_ROUT_SEL.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1286 of 2360

NCT0032
TCAP cannot find a D-channel in any of the routes. Module: NARS.

Procedure: TCAP_ROUTE_SEL.
Action:
Severity: Info.
NCT0033
SNMP trap: No
TRO_FIND_RTE failed for initial set of routes. Module: NARS. Procedure:

TRO_ROUTE_SEL.
Action:
Severity: Info.
NCT0034
SNMP trap: No
TRO_FIND_RTE failed for the extended set of routes. Module: NARS.

Procedure: TRO_ROUTE_SEL.
Action:
Severity: Info.
NCT0035
SNMP trap: No
TRO_FIND_RTE shows all trunks are busy. Module: NARS. Procedure:

TRO_ROUTE_SEL.
Action:
Severity: Info.
NCT0036
SNMP trap: No
AMP_MOD failed for data calls. Module: NARS. Procedure:

ROUTE_SELECTION.
Action:
Severity: Info.
NCT0037
SNMP trap: No
A data call tries to access an analog trunk without AMP package, or an analog
trunk being accessed via AMP non-ADCP or no ADM trunk route in the route
list. Module: NARS. Procedure: ROUTE_SELECTION.
Action:
Severity: Info.
NCT0038
SNMP trap: No
An ADM route is accessed but the call is forwarded. Module: NARS.

Procedure: ROUTE_SELECTION.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1287 of 2360

NCT0039
Call is queued on the initial set of the routes in the route list. Module: NARS.
Action:
Severity: Info.
NCT0040
SNMP trap: No
Call is waiting for EOD on the I-set of the routes in the route list. Module:
NARS. Procedure: ROUTE_SELECTION.
Action:
Severity: Info.
NCT0041
SNMP trap: No
Call is waiting for more digits for FCAS on the I-set of the routes in the route
list. Module: NARS. Procedure: ROUTE_SELECTION.
Action:
Severity: Info.
NCT0042
SNMP trap: No
No routes are available on the extended set of the routes in the route list.
Module: NARS. Procedure: ROUTE_SELECTION.
Action:
Severity: Info.
NCT0043
SNMP trap: No
Call has been queued on the extended set of the routes in the route list.
Action:
Severity: Info.
NCT0044
SNMP trap: No
Call is waiting for EOD on the extended set of the routes in the route list.
Action:
Severity: Info.
NCT0045
SNMP trap: No
Call is waiting for more digits for FCAS on the extended set of the routes in the
route list. Module: NARS. Procedure: ROUTE_SELECTION.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1288 of 2360

NCT0046
ETN trunk has not received enough digits. Module: NARS. Procedure:
ROUTE_SELECTION.
Action:
Severity: Info.
NCT0047
SNMP trap: No
INIT_RL_PTR fails - cannot set up route list pointers. Module: NARS.

Action:
Severity: Info.
NCT0048
SNMP trap: No
TNTRANS fails on ORIGTN. Module: NARS. Procedure:

ROUTE_SELECTION.
Action:
Severity: Info.
NCT0049
SNMP trap: No
INIT_RL_PTR fails. Module: NARS. Procedure: OHQ_TIMEOUT.

Action:
Severity: Info.
NCT0050
SNMP trap: No
SET_RL_ENTRY_PTR fails. Module: NARS. Procedure:

NARS_TRK_SEIZED.
Action:
Severity: Info.
NCT0051
SNMP trap: No
INIT_RL_PTR fails. Module: NARS. Procedure: NARS_TRK_SEIZED.

Action:
Severity: Info.
NCT0052
SNMP trap: No
NARS_LDN_CONV fails for LOC. Module: NARS. Procedure:

TERMINATION.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1289 of 2360

NCT0053
To conventional main and recognized DID to dumb main and digit

manipulation fails. Module: NARS. Procedure: TERMINATION.
Action:
Severity: Info.
NCT0054
SNMP trap: No
Digit manipulation fails. Module: NARS. Procedure: TERMINATION.

Action:
Severity: Info.
NCT0055
SNMP trap: No
INIT_ENTRY_PTRS fails. Module: NARS. Procedure: TDET_TERMINATION.

Action:
Severity: Info.
NCT0056
SNMP trap: No
The pointer to the TDET entry for SCC type of calls is NIL. Module: NARS.
Procedure: TDET_TERMINATION.
Action:
Severity: Info.
NCT0057
SNMP trap: No
NARS_PM=.NARS_ACCESS, but NARS_OCTO_FLAG is not set. Module:

NARS. Procedure: NARS_EOD_TO.
Action:
Severity: Info.
NCT0058
SNMP trap: No
NARS_PM=.NARS_TRANS, not all digits have been received but the timeout
has occurred or it is an ETN call. Module: NARS. Procedure: NARS_EOD_TO.
Action:
Severity: Info.
NCT0059
SNMP trap: No
Redirection counter has exceeded the threshold for ISDN call. Module:
DIGPR. Procedure: TRUNKTER.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1290 of 2360

NCT0060
Satellite history call cannot access another satellite route. Module: DIGPR.
Procedure: TRUNKTER.
Action:
Severity: Info.
NCT0061
SNMP trap: No
An incoming ISDN PRA/ISL call failed B.C. compatibility checking. Module:

Action:
Severity: Info.
NCT0062
SNMP trap: No
Invalid AMP call. Module: DIGPR. Procedure: TRUNKTER.

Action:
Severity: Info.
NCT0063
SNMP trap: No
To access an ISA route directly is not allowed. Module: DIGPR. Procedure:

TRUNKTER.
Action:
Severity: Info.
NCT0064
SNMP trap: No
64kbps data call cannot access a non-PRA facility. Module: DIGPR.

Action:
Severity: Info.
NCT0065
SNMP trap: No
DTI2 VOD call type is not allowed on the route dialed. Module: DIGPR.
Action:
Severity: Info.
NCT0066
SNMP trap: No
Data call is not allowed on the route accessed. Module: DIGPR. Procedure:
TRUNKTER.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1291 of 2360

NCT0067
Voice call is not allowed on the route accessed. Module: DIGPR. Procedure:
TRUNKTER.
Action:
Severity: Info.
NCT0068
SNMP trap: No
Attendant has busied out the RAN route - call is intercepted to attendant.
Module: DIGPR. Procedure: TRUNKTER.
Action:
Severity: Info.
NCT0069
SNMP trap: No
TGAR restriction on the RAN route. Module: DIGPR. Procedure: TRUNKTER.

Action:
Severity: Info.
NCT0070
SNMP trap: No
AWR trunk is not a mntdevice or AWR route is not in the CDB. Module:
Action:
Severity: Info.
NCT0071
SNMP trap: No
Route is not an outgoing route or an AWR route. Module: DIGPR. Procedure:

TRUNKTER.
Action:
Severity: Info.
NCT0072
SNMP trap: No
Trunk list block does not exist or URDATA block does not exist. Module:
Action:
Severity: Info.
NCT0073
SNMP trap: No
ALL_RTS_DENIED for the route with ISA option. Module: DIGPR. Procedure:
TRUNK_HUNT.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1292 of 2360

NCT0074
ALL_RTS_DENIED for B-channel route or ISL route. Module: DIGPR.

Procedure: TRUNK_HUNT.
Action:
Severity: Info.
NCT0075
SNMP trap: No
NCRD blocked the trunk to trunk access for CFNA/CFB to a network DN.
Module: DIGPR. Procedure: TRUNK_HUNT.
Action:
Severity: Info.
NCT0076
SNMP trap: No
SEARCH_ROUTE found one idle trunk but it is blocked. Module: DIGPR.

Action:
Severity: Info.
NCT0077
SNMP trap: No
SEARCH_ROUTE found two idle trunks but both are blocked. Module:
DIGPR. Procedure: TRUNK_HUNT.
Action:
Severity: Info.
NCT0078
SNMP trap: No
SEARCH_ROUTE found no idle trunks. Module: DIGPR. Procedure:

TRUNK_HUNT.
Action:
Severity: Info.
NCT0079
SNMP trap: No
SEARCH_ROUTE found attendant has busied out the route. Module: DIGPR.
Action:
Severity: Info.
NCT0080
SNMP trap: No
SEARCH_ROUTE found access is denied on the route. Module: DIGPR.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1293 of 2360

NCT0081
Unprotected route data block does not exist. Module: GLOB4. Procedure:
SEARCH_ROUTE.
Action:
Severity: Info.
NCT0082
SNMP trap: No
Service route pointer is NIL for the ISA route. Module: GLOB4. Procedure:
SEARCH_ROUTE.
Action:
Severity: Info.
NCT0083
SNMP trap: No
ISA route pointer is NIL for the service route. Module: GLOB4. Procedure:
SEARCH_ROUTE.
Action:
Severity: Info.
NCT0084
SNMP trap: No
Trunk list block pointer is NIL (i.e., block does not exist). Module: GLOB4.
Procedure: SEARCH_ROUTE.
Action:
Severity: Info.
NCT0085
SNMP trap: No
SET_PRI2_PTRS fails. Module: GLOB4. Procedure: GET_TRUNK.

Action:
Severity: Info.
NCT0086
SNMP trap: No
(PRI2_NNC_STATE) or (PRI2_NNDC_STATE and data call). Module:

GLOB4. Procedure: GET_TRUNK.
Action:
Severity: Info.
NCT0087
SNMP trap: No
SET_DTI2_PTRS fails. Module: GLOB4. Procedure: GET_TRUNK.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1294 of 2360

NCT0088
(DTI2_NNC_STATE) or (DTI2_NNDC_STATE and data Call). Module:

Action:
Severity: Info.
NCT0089
SNMP trap: No
Far-end is maintenance busy or disabled for B-channel/ISL trunk. Module:

Action:
Severity: Info.
NCT0090
SNMP trap: No
B-channel/ISL trunk is in restart or forced disconnect state. Module:

Action:
Severity: Info.
NCT0091
SNMP trap: No
ADM/MODEM pair is busy. Module: GLOB4. Procedure: GET_TRUNK.

Action:
Severity: Info.
NCT0092
SNMP trap: No
Number of data calls has exceeded the limit specified in the DLOOP.Module:
Action:
Severity: Info.
NCT0093
SNMP trap: No
Access to the trunk is not allowed - check ACCESS_ALLOWED. Module:

Action:
Severity: Info.
NCT0094
SNMP trap: No
ANI_NO_CR_TONE. Module: GLOB4. Procedure: GET_TRUNK.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1295 of 2360

NCT0095
SPEECHPATH failed (i.e., no network timeslot available). Module: GLOB4.

Procedure: GET_TRUNK.
Action:
Severity: Info.
NCT0096
SNMP trap: No
Have tried searching for idle trunks twice and still was blocked. Module:
Action:
Severity: Info.
NCT0097
SNMP trap: No
Have tried searching for idle trunks once and was blocked. Module: GLOB4.
Procedure: GET_TRUNK.
Action:
Severity: Info.
NCT0098
SNMP trap: No
Trunk is busy (i.e., active cr is non-NIL). Module: GLOB4. Procedure:

GET_TRUNK.
Action:
Severity: Info.
NCT0099
SNMP trap: No
MAINT_TNTRANS failed on the trunk TN. Module: GLOB4. Procedure:

GET_TRUNK.
Action:
Severity: Info.
NCT0100
SNMP trap: No
No idle trunks are found. Module: GLOB4. Procedure: GET_TRUNK.

Action:
Severity: Info.
NCT0101
SNMP trap: No
Code restriction blocks the call from a TLD set. Module: GLOB4. Procedure:
INITIATE_B_CH.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1296 of 2360

NCT0102
Call is blocked for CDR_OUT_TOLL in RDB from a non-TLD set. Module:

GLOB4. Procedure: INITIATE_B_CH.
Action:
Severity: Info.
NCT0103
SNMP trap: No
ISDN (.REQ_CALL_INIT) failed. Module: GLOB4. Procedure:

INITIATE_B_CH.
Action:
Severity: Info.
NCT0104
SNMP trap: No
GET_TTR_TRK_PATH failed. Module: GLOB4. Procedure:

TTR_SATISFIED.
Action:
Severity: Info.
NCT0105
SNMP trap: No
NARS call and no access. Module: GLOB4. Procedure:

ALL_BSY_THIS_RTE.
Action:
Severity: Info.
NCT0106
SNMP trap: No
Huntsteps is neither 30 nor 31 and no access. Module: GLOB4. Procedure:

ALL_BSY_THIS_RTE.
Action:
Severity: Info.
NCT0107
SNMP trap: No
SECOND_SEARCH=.ATTN_BUSY_ROUTE and NOT_ATTN_BUSY.

Module: GLOB4. Procedure: ALL_BSY_THIS_RTE.
Action:
Severity: Info.
NCT0108
SNMP trap: No
NOT_ATTN_BUSY. Module: GLOB4. Procedure: ALL_BSY_THIS_RTE.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1297 of 2360

NCT0109
Not NOT_ATTN_BUSY (i.e., Attendant busied out the route). Module: GLOB4.
Procedure: ALL_BSY_THIS_RTE.
Action:
Severity: Info.
NCT0110
SNMP trap: No
ANI has lost its SON CR after calling ANI module. Module: GLOB4.
Procedure: TRUNK_SEIZE_INIT.
Action:
Severity: Info.
NCT0111
SNMP trap: No
ESN signaling failed - SIGNAL_MODULE. Module: ISDN. Procedure:

OUTG_CALL_INIT.
Action:
Severity: Info.
NCT0112
SNMP trap: No
DCH not established or DCH_L_WAIT non-zero and DCH not in polling state.
Module: ISDN. Procedure: OUTG_CALL_INIT.
Action:
Severity: Info.
NCT0113
SNMP trap: No
No channel number. Module: ISDN. Procedure: OUTG_CALL_INIT.

Action:
Severity: Info.
NCT0114
SNMP trap: No
INIT_MSG_CR failed - return value is .FALSE. Module: ISDN. Procedure:

OUTG_CALL_INIT.
Action:
Severity: Info.
NCT0115
SNMP trap: No
ASSIGN_REFNUM failed - return value is .FALSE. Module: ISDN. Procedure:

OUTG_CALL_INIT.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1298 of 2360

NCT0116
No MSGCR can be allocated. Module: ISDN. Procedure: INIT_MSG_CR.

Action:
Severity: Info.
NCT0117
SNMP trap: No
Incoming PRA/ISL does not have a MSGCR. Module: ISDN. Procedure:

INIT_MSG_CR.
Action:
Severity: Info.
NCT0118
SNMP trap: No
Incompatible bearer capability for PRA/ISL incoming call. Module: ISDN.

Procedure: INIT_MSG_CR.
Action:
Severity: Info.
NCT0119
SNMP trap: No
Incompatible bearer capability for non-PRA/ISL incoming call. Module: ISDN.

Action:
Severity: Info.
NCT0120
SNMP trap: No
TNTRANS failed on ORIGTN (TRK). Module: ISDN. Procedure:

INIT_MSG_CR.
Action:
Severity: Info.
NCT0121
SNMP trap: No
Bearer capability is not allowed for the terminating switch. Module: ISDN.
Action:
Severity: Info.
NCT0122
SNMP trap: No
NSF is not supported for the trunk type - CCSA, DID, CO to DMS. Module:
ISDN. Procedure: INIT_MSG_CR.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1299 of 2360

NCT0123
SET_ROUTE_PTRS failed. Module: ISDN. Procedure: ENBLOC_DIALING.

Action:
Severity: Info.
NCT0124
SNMP trap: No
Not all expected number of digits have been received, but PRA_EOD_FLAG
is set. Module: ISDN. Procedure: ENBLOC_DIALING.
Action:
Severity: Info.
NCT0125
SNMP trap: No
Not all expected number of digits have been received, but PRA_EOD_FLAG
is set. Module: ISDN. Procedure: PROC_NOT_SURE.
Action:
Severity: Info.
NCT0126
SNMP trap: No
Service route (associated with ISA route) pointer is NIL. Module: ISDN.
Procedure: DO_DGT_ANALYSIS.
Action:
Severity: Info.
NCT0127
SNMP trap: No
No digit has been dialed, but PRA_EOD_FLAG is set - # dialed. Module:

ISDN. Procedure: DO_DGT_ANALYSIS.
Action:
Severity: Info.
NCT0128
SNMP trap: No
PRA_EOD_FLAG is set, but the single digit is not 0. Module: ISDN.

Procedure: ONE_DIGIT.
Action:
Severity: Info.
NCT0129
SNMP trap: No
PRA_EOD_FLAG is set, but digit translation is not .EXACT#_KNOWN.

Module: ISDN. Procedure: TWO_DIGITS.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1300 of 2360

NCT0130
PRA_EOD_FLAG is set, the first digit is 0 but digit translation is

not.EXACT#_KNOWN. Module: ISDN. Procedure: THREE_DIGITS.
Action:
Severity: Info.
NCT0131
SNMP trap: No
PRA_EOD_FLAG is set, the first digit is 1 but digit translation is not

.CANT_DETERM. Module: ISDN. Procedure: THREE_DIGITS.
Action:
Severity: Info.
NCT0132
SNMP trap: No
PRA_EOD_FLAG is set, but not all expected number of digits are received.
Action:
Severity: Info.
NCT0133
SNMP trap: No
An invalid interface ID is encountered in the route data block. Module: ISDN.

Procedure: INV_IFC_PRBPTR.
Action:
Severity: Info.
NCT0134
SNMP trap: No
SET_ROUTE_PTRS failed. Module: ISDN. Procedure: TERMINATE.

Action:
Severity:
NCT0135
SNMP trap: No
NCT is not invoked to the next node due to (1) it is not an SL-1 switch, or (2)
an SL-1 switch does not have NCT software. Module: NETT. Procedure:
RCAP_NCT.
Action:
Severity: Info.
NCT0136
SNMP trap: No
SEARCH_ROUTE has found one idle trunk, but it was blocked. Module: ISDN.
Procedure: TERMINATE.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1301 of 2360

NCT0137
SEARCH_ROUTE has found two idle trunks, but both were blocked. Module:
ISDN. Procedure: TERMINATE.
Action:
Severity: Info.
NCT0138
SNMP trap: No
SEARCH_ROUTE found no idle trunks. Module: ISDN. Procedure:

TERMINATE.
Action:
Severity: Info.
NCT0139
SNMP trap: No
SEARCH_ROUTE found that attendant has busied out the route. Module:
ISDN. Procedure: TERMINATE.
Action:
Severity: Info.
NCT0140
SNMP trap: No
SEARCH_ROUTE returned that access to the route is denied. Module: ISDN.

Procedure: TERMINATE.
Action:
Severity: Info.
NCT0141
SNMP trap: No
SET_ROUTE_PTRS failed. Module: ISDN. Procedure: ENBLOC_TIMEOUT.

Action:
Severity: Info.
NCT0142
SNMP trap: No
Second dialtone timeout or barge-in timeout has occurred. Module: ISDN.

Procedure: ENB_EVENTS_TO.
Action:
Severity: Info.
NCT0143
SNMP trap: No
Second timeout has occurred and the expected number of digits are not
collected. Module: ISDN. Procedure: EXACT_#_TO.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1302 of 2360

NCT0144
Timer expires, but not all expected number of digits are collected. Module:
ISDN. Procedure: NOT_SURE_TO.
Action:
Severity: Info.
NCT0145
SNMP trap: No
Procedure ISA_TRK_CHECK returned a .FALSE value. Module: ISDN.

Procedure: RCV_SETUP.
Action:
Severity: Info.
NCT0146
SNMP trap: No
MIN_MAX_CHK returned a .FALSE value for NSF =YES. Module: ISDN.

Procedure: RCV_SETUP.
Action:
Severity: Info.
NCT0147
SNMP trap: No
SET_ROUTE_PTRS failed for ISA route. Module: ISDN. Procedure:

ISA_TRK_CHECK.
Action:
Severity: Info.
NCT0148
SNMP trap: No
Service route is not applicable to AXE-10, SYS-12 interfaces. Module: ISDN.

Procedure: ISA_TRK_CHECK.
Action:
Severity: Info.
NCT0149
SNMP trap: No
Service route is not applicable to an invalid interface ID. Module: ISDN.

Action:
Severity: Info.
NCT0150
SNMP trap: No
SVC_RTE_OK failed. Module: ISDN. Procedure: ISA_TRK_CHECK.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1303 of 2360

NCT0151
Service route has not been configured - ISA_SERV_RTE = H.FFFF. Module:

ISDN. Procedure: ISA_TRK_CHECK.
Action:
Severity: Info.
NCT0152
SNMP trap: No
SRV_RTE_PTR is NIL. Module: ISDN. Procedure: ISA_TRK_CHECK.

Action:
Severity: Info.
NCT0153
SNMP trap: No
DMS_ISA_TRK_COMP returned a .FALSE value. Module: ISDN. Procedure:

ISA_TRK_CHECK.
Action:
Severity: Info.
NCT0154
SNMP trap: No
No trunk compare and MIN/MAX check for invalid interface ID. Module: ISDN.
Action:
Severity: Info.
NCT0155
SNMP trap: No
SID table does not exist. Module: ISDN. Procedure: FIND_DMS_SVC_RTE.

Action:
Severity: Info.
NCT0156
SNMP trap: No
ISA service route pointer = NIL in the SID table. Module: ISDN. Procedure:
FIND_DMS_SVC_RTE.
Action:
Severity: Info.
NCT0157
SNMP trap: No
ISA service route number does not exist (= .NULL_ROUTE_NO). Module:

ISDN. Procedure: FIND_DMS_SVC_RTE.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1304 of 2360

NCT0158
The numbering plan of the Called Party Number is unknown for non-NSF.
Module: ISDN. Procedure: FIND_DMS_SVC_RTE.
Action:
Severity: Info.
NCT0159
SNMP trap: No
The service route block pointer is NIL. Module: ISDN. Procedure:

FIND_ESS_SVC_RTE.
Action:
Severity: Info.
NCT0160
SNMP trap: No
ISA service route number does not exist (=.NULL_ROUTE_NO). Module:

ISDN. Procedure: FIND_ESS_SVC_RTE.
Action:
Severity: Info.
NCT0161
SNMP trap: No
ESN signaling module failed. Module: ISDN. Procedure: INC_TERMINATE.

Action:
Severity: Info.
NCT0162
SNMP trap: No
64kc Bearer Capability call tries to terminate to a non-data DN/non-SL-1

DN/non-Trunk DN/non-NARS DN/non-DISA DN. Module: ISDN. Procedure:
BC_COMPATIBLE.
Action:
Severity: Info.
NCT0163
SNMP trap: No
64kr Bearer Capability call tries to terminate to a non-data DN/non-SL-1

BC_COMPATIBLE.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1305 of 2360

NCT0164
56kBearer Capability call tries to terminate to a non-data DN/non-SL-1

BC_COMPATIBLE.
Action:
Severity: Info.
NCT0165
SNMP trap: No
At the originating switch, only trunk calls can be accessed by Network Call
Trace. Module: DIGPR. Procedure: DNTRANS.
Action:
Severity: Info.
NCT0167
SNMP trap: No
Procedure BC_COMPATIBLE failed. Module: ISDN. Procedure:

IN_SETUP_MSG.
Action:
Severity: Info.
NCT0168
SNMP trap: No
Incoming call termination, mainpm = .IDLE. Module: ISDN. Procedure:

IN_SETUP_MSG.
Action:
Severity: Info.
NCT0169
SNMP trap: No
Incoming call termination, mainpm = .READY. Module: ISDN. Procedure:

IN_SETUP_MSG.
Action:
Severity: Info.
NCT0170
SNMP trap: No
Incoming call termination, mainpm = .BUSY. Module: ISDN. Procedure:

IN_SETUP_MSG.
Action:
Severity: Info.
NCT0171
SNMP trap: No
Incoming call termination, mainpm = .REORDER. Module: ISDN. Procedure:

IN_SETUP_MSG.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1306 of 2360

NCT0172
Incoming call termination, mainpm = .DELAY_DIALING. Module: ISDN.

Procedure: IN_SETUP_MSG.
Action:
Severity: Info.
NCT0173
SNMP trap: No
Incoming call termination, mainpm = .WINKON. Module: ISDN. Procedure:

IN_SETUP_MSG.
Action:
Severity: Info.
NCT0174
SNMP trap: No
Incoming call termination, mainpm = .HALFDISCONNECT. Module: ISDN.

Action:
Severity: Info.
NCT0175
SNMP trap: No
Incoming call termination, mainpm =.SPECIAL. Module: ISDN. Procedure:

IN_SETUP_MSG.
Action:
Severity: Info.
NCT0176
SNMP trap: No
Incoming call termination, mainpm =.CDR. Module: ISDN. Procedure:

IN_SETUP_MSG.
Action:
Severity: Info.
NCT0177
SNMP trap: No
Incoming call termination, mainpm = .CAS_INFO_TONE. Module: ISDN.

Action:
Severity: Info.
NCT0178
SNMP trap: No
Incoming call termination, mainpm = .RLA_CONF_DISC. Module: ISDN.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1307 of 2360

NCT0179
Incoming call termination, mainpm = .CAS_HOLD. Module: ISDN. Procedure:

IN_SETUP_MSG.
Action:
Severity: Info.
NCT0180
SNMP trap: No
Incoming call termination, mainpm = .OBSERVE_PM. Module: ISDN.

Action:
Severity: Info.
NCT0181
SNMP trap: No
Incoming call termination, mainpm = .AAB_DISCONNECT. Module: ISDN.

Action:
Severity: Info.
NCT0182
SNMP trap: No
Incoming call termination, mainpm is greater than .MAX_MAINPM. Module:

ISDN. Procedure: IN_SETUP_MSG.
Action:
Severity: Info.
NCT0183
SNMP trap: No
Terminating side is not a trunk. Module: ISDN. Procedure: PRA_DIALING.

Action:
Severity: Info.
NCT0184
SNMP trap: No
Source = .PRA_DISC, but MSG_CR is NIL. Module: PRA. Procedure:

PRA_HANDLER.
Action:
Severity: Info.
NCT0185
SNMP trap: No
Procedure SET_DCH_PTRS failed. Module: PRA. Procedure:

PRA_HANDLER.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1308 of 2360

NCT0186
DCH is not the active one, or DCH is in switchover waiting state and not polling
state. Module: PRA. Procedure: DL_DATA_CREF.
Action:
Severity: Info.
NCT0187
SNMP trap: No
Protocol Discriminator is not 00001000. Module: PRA. Procedure:

DL_DATA_CREF.
Action:
Severity: Info.
NCT0188
SNMP trap: No
Message type is a SETUP message but reference flag is 0 (for all interfaces
other than ESS4 and ESS5). Module: PRA. Procedure: DL_DATA_CREF.
Action:
Severity: Info.
NCT0191
SNMP trap: No
The channel is either MBSY, or far-end is out-of-service and no channel

negotiation. Module: PRA. Procedure: SL1_CH_CHK.
Action:
Severity: Info.
NCT0192
SNMP trap: No
Alternate channel was found, but TNTRANS failed. Module: PRA. Procedure:
INC_CH_NEGO.
Action:
Severity: Info.
NCT0193
SNMP trap: No
Alternate channel was not found. Module: PRA. Procedure: INC_CH_NEGO.

Action:
Severity: Info.
NCT0196
SNMP trap: No
The trunk is neither a B-channel nor it is an ISL trunk. Module: PRA.

Procedure: LINK_MSGCR.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1309 of 2360

NCT0197
Cannot assign a call reference number in the call reference table. Module:
PRA. Procedure: LINK_MSGCR.
Action:
Severity: Info.
NCT0198
SNMP trap: No
TNTRANS failed and PRA_CH_NO = 0 and CLEAR_GLARE_CH. Module:

PRA. Procedure: LINK_MSGCR.
Action:
Severity: Info.
NCT0199
SNMP trap: No
TNTRANS failed, PRA_CH_NO - 0 and PRA STATEPM = NULL STATE.

Module: PRA. Procedure: LINK_MSGCR.
Action:
Severity: Info.
NCT0200
SNMP trap: No
TNTRANS failed, PRA_CH_NO - 0 and PRA STATEPM - NULL STATE.

Module: PRA. Procedure: LINK_MSGCR.
Action:
Severity: Info.
NCT0201
SNMP trap: No
SET_ROUTE_PTRS failed on the ISA route. Module: PRA. Procedure:

MIN_MAX_CHK.
Action:
Severity: Info.
NCT0202
SNMP trap: No
ISA active calls ISA maximum allowed. Module: PRA. Procedure:

MIN_MAX_CHK.
Action:
Severity: Info.
NCT0203
SNMP trap: No
ISA active calls ISA B-channels reserved. Module: PRA. Procedure:

MIN_MAX_CHK.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1310 of 2360

NCT0204
MSG length 261 octets. Module: PRAUT. Procedure: I_SETUP.

Action:
Severity: Info.
NCT0205
SNMP trap: No
IE length = 0. Module: PRAUT. Procedure: BEARER_CAP.

Action:
Severity: Info.
NCT0206
SNMP trap: No
Coding standard is not CCITT standard (octet 3). Module: PRAUT. Procedure:
BEARER_CAP.
Action:
Severity: Info.
NCT0207
SNMP trap: No
Extension bit is not set in octet 3. Module: PRAUT. Procedure:

BEARER_CAP.
Action:
Severity: Info.
NCT0208
SNMP trap: No
Xfer mode - 00, or Information Xfer Rate - 10000 (octet 4). Module: PRAUT.
Procedure: I_BC_SPEECH.
Action:
Severity: Info.
NCT0209
SNMP trap: No
Xfer mode - 00, or Information Xfer Rate - 10000 (octet 4). Module: PRAUT.
Procedure: I_BC_3_1KHZ.
Action:
Severity: Info.
NCT0210
SNMP trap: No
Octet 5 - Mu Law or - G.711 A Law (for SYS-12, AXE-10). This is applicable

to Speech or 3.1k Hz Bearer Capability only. Module: PRAUT. Procedure:
CHECK_LAW.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1311 of 2360

NCT0211
Xfer mode - 00, or Information Xfer Rate - 10000 in octet 4. Module: PRAUT.
Procedure: I_BC_64K.
Action:
Severity: Info.
NCT0212
SNMP trap: No
Coding error for 64KR for DMS/ SL1/SL100, 64KC for ESS4/ESS5, 56K for
SYS-12/AXE-10. Module: PRAUT. Procedure: I_BC_64K.
Action:
Severity: Info.
NCT0213
SNMP trap: No
Protocol ID - Rate Adaption (00001) for 56K (octet 5). Module: PRAUT.
Procedure: I_BC_64K.
Action:
Severity: Info.
NCT0214
SNMP trap: No
Layer ID - Layer 1 (001) for 56K (octet 5). Module: PRAUT. Procedure:
I_BC_64K.
Action:
Severity: Info.
NCT0215
SNMP trap: No
Extension bit is set for octet 5. Module: PRAUT. Procedure: I_BC_64K.

Action:
Severity: Info.
NCT0216
SNMP trap: No
Rate is not 0001111 - octet 5a. Module: PRAUT. Procedure: I_BC_64K.

Action:
Severity: Info.
NCT0217
SNMP trap: No
Extension bit is not set. Module: PRAUT. Procedure: I_BC_64K.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1312 of 2360

NCT0218
Extension bit is not set on DMS/ SL1/SL100 interfaces. Skip 4a, 4b and
extension bit is not set for the next IE on ESS4/ESS5 interface. Error on
SYS-12/AXE-10. Module: PRAUT. Procedure: ALLOW_EXT_4A_4B.
Action:
Severity: Info.
NCT0219
SNMP trap: No
Bearer Capability is not supported. Module: PRAUT. Procedure:

BC_CAP_ERROR.
Action:
Severity: Info.
NCT0220
SNMP trap: No
IE length = 0. Module: PRAUT. Procedure: CHANNEL_ID.

Action:
Severity: Info.
NCT0221
SNMP trap: No
Octet 3 coding error - not 101001 for DMS, not 100001 for SYS-12/ AXE-10.
Module: PRAUT. Procedure: CHANNEL_ID.
Action:
Severity: Info.
NCT0222
SNMP trap: No
Extension bit is not set in octet 3. Module: PRAUT. Procedure: CHANNEL_ID.

Action:
Severity: Info.
NCT0223
SNMP trap: No

Action:
Severity: Info.
NCT0224
SNMP trap: No
Channel type - 0011 (B-channel units) in octet 5. Module: PRAUT. Procedure:

CHANNEL_ID.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1313 of 2360

NCT0225

Action:
Severity: Info.
NCT0226
SNMP trap: No
Extension bit is not set in octet 6 - applicable to ESS4/ESS5/SYS-12. Module:

PRAUT. Procedure: CHANNEL_ID.
Action:
Severity: Info.
NCT0227
SNMP trap: No
PRA_CH_NO in MSGCR - the Calculated channel number. Module: PRAUT.

Procedure: CHANNEL_ID.
Action:
Severity: Info.
NCT0228
SNMP trap: No
IE length = 0. Module: PRAUT. Procedure: PROGRESS_IND.

Action:
Severity: Info.
NCT0229
SNMP trap: No
Coding standard - CCITT Std, or National Std (for SYS-12) in octet 3. Module:
PRAUT. Procedure: PROGRESS_IND.
Action:
Severity: Info.
NCT0230
SNMP trap: No
Failed General Location checking in octet 3. Module: PRAUT.

Procedure:PROGRESS_IND.
Action:
Severity: Info.
NCT0231
SNMP trap: No

PROGRESS_IND.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1314 of 2360

NCT0232
Failed Progress Description checking in octet 4. Module: PRAUT. Procedure:

PROGRESS_IND.
Action:
Severity: Info.
NCT0233
SNMP trap: No

PROGRESS_IND.
Action:
Severity: Info.
NCT0234
SNMP trap: No
IE length = 0. Module: PRAUT. Procedure: NTWK_SPEC_FAC.

Action:
Severity: Info.
NCT0235
SNMP trap: No
Total length of IE greater than IE length received in the IE itself. Module:

PRAUT. Procedure: NTWK_SPEC_FAC.
Action:
Severity: Info.
NCT0236
SNMP trap: No
IE length = 0. Module: PRAUT. Procedure: CALLING_PTY_#.

Action:
Severity: Info.
NCT0237
SNMP trap: No
Extension bit is not set in octet 3a. Module: PRAUT. Procedure:

CALLING_PTY_#.
Action:
Severity: Info.
NCT0238
SNMP trap: No

PRAUT. Procedure: CALLING_PTY_#.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1315 of 2360

NCT0239
IE length = 0. Module: PRAUT. Procedure: CALLED_PTY_#.

Action:
Severity: Info.
NCT0240
SNMP trap: No

CALLED_PTY_#.
Action:
Severity: Info.
NCT0241
SNMP trap: No
IE length = 0. Module: PRAUT. Procedure: ORIG_CALLED_#.

Action:
Severity: Info.
NCT0242
SNMP trap: No
Extension bit is not set in octet 3c. Module: PRAUT. Procedure:

ORIG_CALLED_#.
Action:
Severity: Info.
NCT0243
SNMP trap: No

PRAUT. Procedure: ORIG_CALLED_#.
Action:
Severity: Info.
NCT0244
SNMP trap: No
IE length = 0. Module: PRAUT. Procedure: REDIRECTING_#.

Action:
Severity: Info.
NCT0245
SNMP trap: No
Extension bit is not set in octet 3b. Module: PRAUT. Procedure:

REDIRECTING_#.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1316 of 2360

NCT0246

PRAUT. Procedure: REDIRECTING_#.
Action:
Severity: Info.
NCT0247
SNMP trap: No
IE length = 0. Module: PRAUT. Procedure: TRANS_NTWK_SEL.

Action:
Severity: Info.
NCT0248
SNMP trap: No
IE length = 0. Module: PRAUT. Procedure: FACILITY_IE.

Action:
Severity: Info.
NCT0249
SNMP trap: No
BRIT Channel Id IE has a null length.

Action:
Severity: Info.
NCT0250
SNMP trap: No
Wrong value of extension bit in BRIT Channel Id IE.

Action:
Severity: Info.
NCT0251
SNMP trap: No
Invalid encoding in BRIT Channel Id IE.

Action:
Severity: Info.
NCT0252
SNMP trap: No
Message received with a Channel Id different from the expected value.

Action:
Severity: Info.
NCT0253
SNMP trap: No
ISDN call can only be flagged as PRI or BRIT call.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1317 of 2360

NCT0254
Source = .PRA_DISC, but MSG_CR is NIL. Module: BRIT. Procedure:

BRIT_HANDLER
Action:
Severity: Info.
NCT0255
SNMP trap: No
Protocol Discriminator is not 00001000. Module: BRIT. Procedure:

DL_DATA_CREF.
Action:
Severity: Info.
NCT0256
SNMP trap: No
Message type is a SETUP message but reference flag is 0. Module: BRIT.

Procedure: DL_DATA_CREF.
Action:
Severity: Info.
NCT0257
SNMP trap: No
The channel is either MBSY, or far end is out of service and no channel
negotiation. Module: BRIT. Procedure: SL!_CHK.
Action:
Severity: Info.
NCT0258
SNMP trap: No
Alternate channel was found, but TNTRANS failed. Module: BRIT. Procedure:
INC_CH_NEGO
Action:
Severity: Info.
NCT0259
SNMP trap: No
The trunk is not a B-channel. Module: BRIT. Procedure: LINK_MSGCR.

Action:
Severity: Info.
NCT0260
SNMP trap: No
TNTRANS failed and PRA_CH_NO = 0. Module: BRIT. Procedure:

LINK_MSGCR.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1318 of 2360

NCT0261
TNTRANS failed, PRA_CH_NO = 0 and PRA_STATEPM = NULL STATE.

Module: BRIT. Procedure: LINK_MSGCR.
Action:
Severity: Info.
NCT0262
SNMP trap: No
NTRANS failed, PRA_CH_NO = 0 and PRA_STATEPM = NULL STATE.

Module: BRIT. Procedure: LINK_MSGCR.
Action:
Severity: Info.
NCT0263
SNMP trap: No
Code restriction blocks the call from a TLD set. Module CLOB4. Procedure:
TTR_SATISFIED.
Action:
Severity: Info.
NCT0274
SNMP trap: No
In PTU_CHECK_OK, no trunks available for non-priority users. Procedure:

GET_TRUNK in SEARCH_ROUTE.
Severity: Minor.
NCT0275
SNMP trap: No
No trunks available. Module: PTU. Procedure: ACOD_FIRST_CHECK.

Severity: Minor.
NCT0276
SNMP trap: No
No trunks available for non-priority users. Module: PTU. Procedure:

ACOD_SECOND_CHECK.
Severity: Minor.
NCT0277
SNMP trap: No
No trunks available; ATB bit set. Module: NARS. Procedure:

EARLY_SEARCH_ROUTE.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1319 of 2360

NCT0278
No trunks available; idle trunk counter = 0 . Module: NARS. Procedure:

EARLY_SEARCH_ROUTE.
Severity: Minor.
NCT0279
SNMP trap: No
No trunks available; route is attendant busied. Module: NARS. Procedure:

EARLY_SEARCH_ROUTE.
Severity: Minor.
NCT0280
SNMP trap: No
No trunks available; no trunks are defined on the route. Module: NARS.

Procedure: EARLY_SEARCH_ROUTE.
Severity: Minor.
NCT0281
SNMP trap: No
No trunks available for non-priority users. Module: NARS. Procedure:

EARLY_SEARCH_ROUTE.
Severity: Minor.
NCT0282
SNMP trap: No
Incoming VNS - no VDN available.

Severity: Minor.
NCT0283
SNMP trap: No
Incoming VNS - no CR available.

Severity: Minor.
NCT0284
SNMP trap: No
Incoming VNS - problem is assigning a reference number

Severity: Minor.
SNMP trap: No
System Messages
Page 1320 of 2360

NCT0285
Incoming VNS - problem to set the customer data pointers

Severity: Minor.
NCT0286
SNMP trap: No
Outgoing VNS - problem to set the customer data pointers.

Severity: Minor.
NCT0287
SNMP trap: No
Outgoing VNS - no VDN available.

Severity: Minor.
NCT0288
SNMP trap: No
Outgoing VNS - the maximum number of VNS calls for the route list entry has
been reached.
Severity: Minor.
NCT0289
SNMP trap: No
Outgoing VNS - the maximum number of VNS calls for the VNS D-channel has
been reached.
Severity: Minor.
NCT0290
SNMP trap: No
VNS NWQ call - something wrong at the creation of the NARS CR.
Severity: Minor.
NCT0291
SNMP trap: No
VNS NWQ call - no CR available for NARS.

Severity: Minor.
NCT0292
SNMP trap: No
VNS call fails to terminate to the NACD agent reserved.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1321 of 2360

NCT0400
Busy or overflow tone received by the monitoring terminal as defined in LD 80.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1322 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1323 of 2360
NPR: Network and Peripheral Equipment

Diagnostic(LD 32)
Messages
NPR0000
LD 32 program identifier.
Action:
Severity: Info.
NPR0001
SNMP trap: No
Illegal character in command.

Severity: Minor.
NPR0002
SNMP trap: No
Wrong number of input parameters for command.

Severity: Minor.
NPR0003
SNMP trap: Yes
Illegal command.
Severity: Minor.
NPR0004
SNMP trap: Yes
Loop or group parameter out-of-range.

Severity: Minor.
NPR0005
SNMP trap: Yes
Shelf parameter out-of-range. Unit 0 to 3 only are allowed.

Severity: Minor.
NPR0006
SNMP trap: Yes
Card parameter out-of-range.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1324 of 2360

NPR0007
Unit parameter out-of-range.

Action:
Severity: Minor.
NPR0008
SNMP trap: Yes
Command is valid from SL-1 maintenance set only. Cannot outpulse from a
TTY. See trunk diagnostic program or use SL-1 maintenance set.
Action:
Severity: Minor.
NPR0009
SNMP trap: Yes
Unit requested is not a trunk.

Action: Check data tables for terminal device. Input command STAT L S C.
Severity: Minor.
NPR0010
SNMP trap: Yes
Command ignored since an active input device would be disabled.

Action: Abort program and input again from TTY.
Severity: Minor.
NPR0011
SNMP trap: Yes
Requested pack is no longer busy and has been disabled. Indication that the
DISI L S C command has been completed.
Action:
Severity: Minor.
NPR0012
SNMP trap: Yes
Requested trunk is busy.

Severity: Minor.
NPR0013
SNMP trap: Yes
A serious data error has been detected.

Action: Contact supplier for further assistance.
Severity: Minor.
NPR0014
SNMP trap: Yes
Seizure of a RAN or AIOD trunk is not allowed by this program.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1325 of 2360

NPR0015
Specified loop not responding.

Action: Check enable switch on pack. If fault exists, suspect network, CPU,
network extender or PS packs.
Severity: Minor.
NPR0016
SNMP trap: Yes
Loop already enabled. No action.

Action:
Severity: Minor.
NPR0017
SNMP trap: Yes
Specified loop is a tone and digit switch.

Action: Use LD 34 to enable/disable it.
Severity: Minor.
NPR0018
SNMP trap: Yes
A DISI command is still pending. Only one request allowed at a time.

Action: Enter END to cancel last DISI and enter new DISI command.
Severity: Minor.
NPR0019
SNMP trap: Yes
Carrier Remote superloop (LCI) did not respond to the request to

disable/enable the RTE superloop.
Action: Ensure that the LCI is installed and that the H / W disabled switch on its
faceplate is in the enabled position.
Severity: Minor.
NPR0020
SNMP trap: No
Specified PS card out of range. Cards 1 to 10 only are allowed.

Action:
Severity: Minor.
NPR0024
SNMP trap: Yes
Specified PS card is being used by the active CPU for clock.

Action: Load program 35. Input SCPU. Abort and reload 32. This switches to
alternate CPU.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1326 of 2360

NPR0029
The unit specified is either maintenance busy or busy.

Action:
Severity: Minor.
NPR0031 loop
SNMP trap: Yes
Loop is a remote loop. ENLL and DISL not allowed.

Action: Use LD 53 (2.0 Mb/s RPE) to bring loop L up and down.
Severity: Minor.
NPR0034
SNMP trap: Yes
DISU command is blocked because the unit being disabled is experiencing a

flash download.
Action:
Severity: Minor.
NPR0035
SNMP trap: No
The flash download for the following TN is terminated due to the 'disable
command'.
Action: The flash download for the affected TN might need to be reactivated
after the unit is enabled.
Severity: Minor.
NPR0037
SNMP trap: Yes
TNTRANS FAILED for Taurus TN and UNIT POINTER IS NIL

Action:
Severity: Minor.
NPR0038
SNMP trap: No
Unit specified is not Taurus downloadable.

Action:
Severity: Minor.
NPR0039
SNMP trap: No
There is a response timeout from the Taurus set.

Action:
Severity: Minor.
NPR0040
SNMP trap: No
The set unit type does not match the version type in the set.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1327 of 2360

NPR0041
Unit has already the latest software.

Action:
Severity: Minor.
NPR0042
SNMP trap: No
Unit is not idle or system application is active.

Action:
Severity: Minor.
NPR0043
SNMP trap: No
Invalid parameters for FDLS command.

Action:
Severity: Minor.
NPR0044
SNMP trap: No
No XPEC in the system.

Action:
Severity: Minor.
NPR0045
SNMP trap: No
SNMP trap: No
Taurus invalid state.

Action:
Severity: Minor.
NPR0046
Midnight download initiated already. Cannot initiate another one.

Action:
Severity: Minor.
NPR0047
SNMP trap: No
This command is not valid on virtual superloops, since virtual superloops do

not physically exist.
Action:
Severity: Minor.
NPR0048
SNMP trap: Yes
IDU command on non-registered Etherset is not valid.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1328 of 2360

NPR0049
Cannot retrieve Etherset IP or TPS IP address.

Action:
Severity: Info.
NPR0050
SNMP trap: No
That command is only valid for superloops.

Action:
Severity: Minor.
NPR0051
SNMP trap: No
That command is not valid for superloops.

Action:
Severity: Minor.
NPR0052
SNMP trap: No
No virtual trunk was found for entered customer number or route number.
Action:
Severity: Minor.
NPR0053
SNMP trap: No
No virtual trunk was found in the given range of route members.

Action:
Severity: Minor.
NPR0054
SNMP trap: No
FDLC command completed. Download to sets will continue until complete.

Action:
Severity: Info.
NPR0055
SNMP trap: No
H.323 virtual trunks can not be enabled when H323_VTRK is restricted.

Action:
Severity: Info.
NPR0056
SNMP trap: No
SNMP trap: No
Route out-of-range.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 1329 of 2360

NPR0080
Peripheral Controller number is out-of-range (1-95).

Action:
Severity: Minor.
NPR0081
SNMP trap: Yes
Peripheral Controller requested is not defined.

Action:
Severity: Minor.
NPR0082
SNMP trap: No
Peripheral Controller is already enabled.

Action:
Severity: Minor.
NPR0083
SNMP trap: No
Cannot find an enabled Network Card that is connected to the Controller.

Action: Enable one or both of the Network Cards and try again.
Severity: Minor.
NPR0084
SNMP trap: No
Cannot send message to Network Card.

Action: Wait and retry the command later. If this error occurs again check the
Network Card and associated cabling.
Severity: Minor.
NPR0085
SNMP trap: Yes
That command is not valid for Network/DTR Card (NT8D18).

Action: Use the DISL/ENLL commands instead.
Severity: Minor.
NPR0086
SNMP trap: No
Superloop numbers must be a multiple of 4.

Action:
Severity: Minor.
NPR0087
SNMP trap: Yes
The NT8D PE shelf is either unoccupied by superloops or contains bad

superloop numbers. There is a possible data corruption in the Controller block.
Action: Contact the supplier for assistance.
Severity: Minor.
SNMP trap: No
System Messages
Page 1330 of 2360

NPR0209
Customer nonexistent.
Action: Verify data. Command CMIN ALL will clear all minor alarms.
Severity: Minor.
NPR0300 l s c (u)
SNMP trap: Yes
The specified loop, shelf, card and/or unit cannot be tested because it is
disabled.
Action:
Severity: Minor.
NPR0302
SNMP trap: Yes
SNMP trap: No
Conference loop.
Action: Use LD 38.
Severity: Minor.
NPR0303
An unrecognizable status code has been sent. Undefined Link/DCHI state.

Action:
Severity: Minor.
NPR0310
SNMP trap: No
Receive micro of ISDLC memory fault.

Action:
Severity: Minor.
NPR0317
SNMP trap: Yes
SNMP trap: Yes
ISDLC card reset.

Action:
Severity: Minor.
NPR0318
No response from ISDLC card.

Action:
Severity: Minor.
NPR0319
SNMP trap: Yes
All units on the card are enabled. Self test of ISDLC card is not performed as
one or more units on the ISDLC card are busy.
Action: If self test is mandatory, disable the card first.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1331 of 2360

NPR0320
This command is only allowed for ISDLC card.

Action:
Severity: Minor.
NPR0321
SNMP trap: Yes
That command is only allowed for M3000 sets.

Action:
Severity: Minor.
NPR0325
SNMP trap: Yes
Cannot perform card self test because one or more units are busy.
Action:
Severity: Minor.
NPR0326
SNMP trap: Yes
No response from card. Retry the command.

Action:
Severity: Minor.
NPR0327
SNMP trap: No
No response from the Network Card. Retry the command several times.
Action: If the problem persists, check the Network Card and associated cabling.
Severity: Minor.
NPR0328
SNMP trap: Yes
The superloop must be disabled before using that command.

Action:
Severity: Minor.
NPR0329
SNMP trap: No
The card self test failed. The card was not enabled.
Action: Try to enable the card again. If the problem persists, replace the card.
Severity: Minor.
NPR0330
SNMP trap: No
No acknowledgment returned for a message sent to the Network

Card/Controller (NT8D04/NT8D01). The command has been terminated.
Action: Retry the command later. If the problem persists, contact supplier.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1332 of 2360

NPR0331
Timeout waiting for Peripheral Software Download (PSDL) to complete the

download function.
Action: Check SDL messages.
Severity: Minor.
NPR0332
SNMP trap: No
Specified Peripheral Software (PSW) version number is out of range (1-99).

Action:
Severity: Minor.
NPR0333
SNMP trap: Yes
Specified Peripheral Software (PSW) version (1-99) not found on the mass
storage device.
Action: Use LD 22 to determine the available PSW versions.
Severity: Minor.
NPR0334
SNMP trap: Yes
Peripheral Software Download (PSDL) failure.

Action:
Severity: Minor.
SNMP trap: Yes
NPR0500dn l s c u The unit has failed the PBXT test. There are several set states that would
prevent successful completion of the test, e.g., ringing, set is off-hook.
Action: Check for ERR500 messages that indicate the same unit. If ERR500
messages do not indicate this unit to be in trouble, try the test again. If the fault
indicates:
1. only one unit, suspect a faulty lamp in the set
2. all units on one card, suspect a faulty line card.
Severity: Minor.
NPR0501
SNMP trap: Yes
Cannot print telephone ID because the TN is not equipped, or the TN is not a

voice TN on a Meridian Modular set.
Action:
Severity: Minor.
NPR0503
SNMP trap: Yes
Response timeout from IDU (2 seconds).

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1333 of 2360

NPR0504
Command not allowed for Conference/TDS/MFS cards. For TDMF loops use
LD 34, or LD 46. For conference loops, use LD 38.
Action:
Severity: Minor.
NPR0505
SNMP trap: Yes
Superloop Network or Controller card has some problems.

Action: Check the card and its associated cable and repeat the command. If the
problem persists, pull the card and plug it back in. If the problem persists on the
same command again, replace the card.
Severity: Minor.
NPR0508
SNMP trap: No
APNSS virtual loops can not be disabled.

Action:
Severity: Minor.
NPR0509
SNMP trap: No
DSL configuration download failed.

Action:
Severity: Minor.
NPR0510
SNMP trap: Yes
SNMP trap: No
DSL is already enabled.

Action:
Severity: Minor.
NPR0511
Since this shelf contains at least one BRI line card, one must wait 45 seconds
before enabling the shelf/loop.
Action:
Severity: Minor.
NPR0514
SNMP trap: Yes
The software failed to enable the unit.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1334 of 2360

NPR0515
The BRI line card did not send an activation acknowledgment for the DSL(s).
Action:
Severity: Minor.
NPR0516
SNMP trap: Yes
The BRI line card selftest failed to be invoked.

Action:
Severity: Minor.
NPR0517
SNMP trap: No
Line card selftest failed. Line card enabling sequence is aborted. (Same as
NPR329).
Action:
Severity: Minor.
NPR0519
SNMP trap: No
No response from the ISDN BRI line card.

Action:
Severity: Minor.
NPR0522
SNMP trap: Yes
MISP not responding. Aborting command.

Action:
Severity: Minor.
NPR0533
SNMP trap: No
The MISP application did not acknowledge the requested "Line Card State
Change".
Action:
Severity: Minor.
NPR0534
SNMP trap: Yes
The MISP application did not acknowledge the requested "DSL State
Change".
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1335 of 2360

NPR0551
Invalid message or invalid environment in which to send the message to the

MISP.
Action:
Severity: Minor.
NPR0555
SNMP trap: Yes
Expedited output queue is full.

Action:
Severity: Minor.
NPR0556
SNMP trap: Yes
The MISP output buffer is not available, (possibly because the MISP has not
read off the previous output message yet).
Action:
Severity: Minor.
NPR0561
SNMP trap: Yes
Only valid for MISP and superloops.

Action:
Severity: Minor.
NPR0562
SNMP trap: No
Cannot send message to the line card.

Action:
Severity: Minor.
NPR0570
SNMP trap: Yes
Cannot read the applications' information blocks from the MISP card.
Action:
Severity: Minor.
NPR0600
SNMP trap: No
Peripheral Signaling card cannot be disabled if DTCS is enabled.

Action:
Severity: Minor.
NPR0601
SNMP trap: No
Cannot convert a non-terminal loop TN. This command is intended for terminal
loops only.
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1336 of 2360

NPR0605
That application is not configured on this MISP.

Action:
Severity: Minor.
NPR0606
SNMP trap: Yes
DSL needs to be in RELEASED state.

Action:
Severity: Minor.
NPR0607
SNMP trap: No
DSL needs to be in ESTABLISHED state.

Action:
Severity: Minor.
NPR0608
SNMP trap: No
DSL needs to be in TEST mode.

Action:
Severity: Minor.
NPR0609
SNMP trap: No
DSL needs to be in REMOTE LOOPBACK mode.

Action:
Severity: Minor.
NPR0611
SNMP trap: No
DSL configuration is not TIE trunk type, or Meridian 1 interface type.

Action:
Severity: Minor.
NPR0620
SNMP trap: No
SNMP trap: No
SNMP trap: No
Not a BRI Line Card.

Action:
Severity: Minor.
NPR0621
Not a valid Trunk DSL.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 1337 of 2360

NPR0623
Trunk DSL is enabled but released (Is in code already).

Action:
Severity: Minor.
NPR0624
SNMP trap: No
A command in LD 32 is pending completion.

Action: Wait for it to finish, or enter two asterisks (**) to abort the Overlay
completely.
Severity: Minor.
NPR0626
SNMP trap: No
Invalid case value (e.g. INTPM, PARPM,...).

Action:
Severity: Minor.
NPR0627
SNMP trap: Yes
Failed to get Interface Type.

Action:
Severity: Minor.
NPR0628
SNMP trap: Yes
Failed to get Interface TN.

Action:
Severity: Minor.
NPR0629
SNMP trap: Yes
SNMP trap: Yes
MPH OVL PTR is NIL.

Action:
Severity: Minor.
NPR0630
Protected loop PTR is NIL.

Action:
Severity: Minor.
NPR0631
SNMP trap: Yes
MPH NET IFC PTR is NIL.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1338 of 2360

NPR0632
USID number out-of-range (enter 0-15).

Action:
Severity: Minor.
NPR0633
SNMP trap: Yes
B-channel number out-of-range (enter 1 or 2).

Action:
Severity: Minor.
NPR0634
SNMP trap: Yes
Protected card PTR is NIL.

Action:
Severity: Info.
NPR0635
SNMP trap: Yes
That must be a BRI line card.

Action:
Severity: Minor.
NPR0636
SNMP trap: Yes
Protected line PTR is NIL.

Action:
Severity: Minor.
NPR0637
SNMP trap: Yes
That must be a digital telephone.

Action:
Severity: Minor.
NPR0638
SNMP trap: Yes
FUNC DATA PTR returned NIL PTR.

Action:
Severity: Minor.
NPR0639
SNMP trap: Yes
BRI USID MAPPTR is NIL.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1339 of 2360

NPR0640
That must be an MISP loop.

Action:
Severity: Minor.
NPR0641
SNMP trap: Yes
SNMP trap: Yes
Invalid MISP TN.

Action:
Severity: Minor.
NPR0642
BRI USID TSPTR is NIL.

Action:
Severity: Minor.
NPR0643
SNMP trap: Yes
Invalid MPH terminal type.

Action:
Severity: Minor.
NPR0645
SNMP trap: Yes
SNMP trap: Yes
Invalid channel type.

Action:
Severity: Minor.
NPR0646
TOD2SEC Timeout waiting for message.

Action:
Severity: Minor.
NPR0663
SNMP trap: Yes
Cannot enable or disable this ISDN BRI line card or DSL because the line card
is not associated with a BRSC or MISP.
Action:
Severity: Minor.
NPR0664
SNMP trap: No
BRSC Cards do not have units associated with them.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1340 of 2360

NPR0665
This command is not valid on phantom loops, since phantom loops do not
physically exist.
Action:
Severity: Minor.
NPR0666
SNMP trap: Yes
Loop must be configured as MISP.

Action: Re-enter command with a valid MISP loop number.
Severity: Minor.
NPR0667
SNMP trap: No
MISP basecode must be enabled.

Action: Enable the MISP card using the ENLL 111 command.
Severity: Minor.
NPR0668
SNMP trap: No
The BRIE Application is not configured on the MISP.

Action: Re-enter command with an MISP loop that has the BRIE application
configured.
Severity: Minor.
NPR0669
SNMP trap: No
There was no downloadable Interface defined on the MISP.

Action: Configure a UIPE Trunk DSL in Overlay 27 and then try again.
Severity: Minor.
NPR0670
SNMP trap: No
All Interfaces are "active", i.e. there are enabled DSLs of each Interface type.
An Interface must be "inactive" before the data can be downloaded.
Action: Disable the corresponding DSLs, or disable the BRIE application by the
DISL BRIE 111 command. Enter the command again.
Severity: Minor.
NPR0671
SNMP trap: No
Invalid selection.
Action: Enter one of the choices.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1341 of 2360

NPR0672
Interfaces is "active", i.e. there are enabled DSLs of this Interface type. An
Interface must be "inactive" before the data can be downloaded.
Action: Disable the corresponding DSLs, or disable the BRIE application by the
DISL BRIE 111 command. Enter the command again.
Severity: Minor.
NPR0673
SNMP trap: No
UIPE BRI Trunk DSL/Line Card is expected for this command.

Action: Re-enter command with UIPE BRI Trunk DSL/Line Card TN.
Severity: Minor.
NPR0674
SNMP trap: No
The specified unit is Out of Service, or may be a console power unit.

Action: It cannot be enabled or disabled. To change the unit, you must remove
it OUT and reenter it New.
Severity: Minor.
NPR0675
SNMP trap: No
DSL is not of the correct application type or Linecard does not have a DSL of
the correct application type for this command.
Action: Check configuration in LD 27 and re-enter command with DSL/Linecard
of the correct application.
Severity: Minor.
NPR0676
SNMP trap: No
The M1 Companion card must be disabled on the Companion before the card
can be removed from the M1.
Action:
Severity: Minor.
NPR0678
SNMP trap: No
DSL does not have GF capability.

Severity: Minor.
NPR0679
SNMP trap: No
Invalid call reference number.

Severity: Minor.
SNMP trap: No
System Messages
Page 1342 of 2360

NPR0681
EIMC/MXC related maintenance commands are not allowed from overlay 32.
Action: Use the Mobility Mat platform.
Severity: Info.
NPR0686
SNMP trap: No
XCMC hardware pack self-test failed.

Action: Replace the XCMC hardware pack.
Severity: Info.
NPR0688
SNMP trap: No
Device locked by the Russian Call Monitoring feature. The command was not
executed.
Severity: Minor.
NPR0705
SNMP trap: No
IDC/IDU is busy with another request.

Action:
Severity: Minor.
NPR0706
SNMP trap: No
This command is not available for specified

IPMG DTR devices, please use LD 34 to enable
these DTRs
Action:
Severity: Info.
NPR0707
SNMP trap: No
This command is not valid for IPMG loops

Action: Please check the parameters used
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1343 of 2360
NWS: Network and Signaling Diagnostic

(LD 30)
The Network and Signaling Diagnostic program, (LD 30), is used to maintain
Network loops. It may be run in background, loaded during the daily routines
or loaded manually to enter commands. Problems are reported in NWS
messages.
Messages
NWS0000
Program 30 has been loaded.

Action:
Severity: Info.
NWS0001
SNMP trap: Yes
The flash download for the following TN is terminated due to the 'disable
command'. It may need to be redone after the TN is enabled.
Action:
Severity: Minor.
NWS0002
SNMP trap: Yes
Invalid command was entered.

Action: Check and reenter command.
Severity: Minor.
NWS0003
SNMP trap: Yes
The command contained an invalid parameter. The problem may be: 1. the
loop, shelf or customer number is out-of-range 2. the loop or shelf specified is
disabled or unequipped 3. the customer number specified does not
Action: Check all command parameters and reenter command. If NWS003 is
output again, the loop or shelf specified is unequipped or disabled.
Severity: Minor.
NWS0004
SNMP trap: Yes
Yellow alarm is set or loop is being audited.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1344 of 2360

NWS0005
No free channel for signaling test.

Action:
Severity: Minor.
NWS0006
SNMP trap: Yes
Loop is being audited or there is no channel equipped.

Action:
Severity: Minor.
NWS0007
SNMP trap: Yes
Attempted to enter a command other than END, while the previous command
was still being executed.
Action: Enter END to abort the current command.
Severity: Minor.
NWS0008
SNMP trap: Yes
A serious data error has been detected.

Severity: Critical.
NWS0009
SNMP trap: Yes
Issued an ENLL to an already enabled network loop or to a network loop

associated with a disabled PS card. Command ignored by the system.
Action: If the PS card was disabled, re-enable using LD 32 before enabling loop.
Severity: Info.
NWS0010
SNMP trap: Yes
No response from Network card or no acknowledgment returned for previous

message sent to the Network or Controller card (NT8D04/NT8D01).
Action:
Severity: Critical.
NWS0013
SNMP trap: Yes
A serious data error has been detected by NWS.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1345 of 2360

NWS0019
Carrier Remote superloop (LCI) did not respond to the request to

disabling/enabling of the RTE superloop.
Action: Ensure that the LCI is installed and that the H / W disabled switch on its
faceplate is in the enabled position.
Severity: Minor.
NWS0020
SNMP trap: No
During execution of the signaling test, an input buffer overflow was detected
and some input messages were lost. The signaling test was terminated. No
fault is implied by this message.
Action: Retry test later.
Severity: Critical.
NWS0023 loop
SNMP trap: Yes
During execution of the signaling test, a large number of line faults were
detected, but storing the fault information required too much memory space.
Testing of the PS card associated with this loop was terminated.
Action: Beginning with the specified loop, test each of the remaining loops on
the associated PS card separately. This message does not necessarily imply a
fault on the specified loop.
Severity: Critical.
NWS0024
SNMP trap: Yes
Network Card fault list is full.

Action:
Severity: Critical.
NWS0025
SNMP trap: Yes
A serious data error has been detected by Network Card fault list management
routines. The test is terminated.
Action:
Severity: Critical.
NWS0030
SNMP trap: Yes
Clock switching function not performed; could not determine which clock was
active. Fault may be: 1. QPC411 SCG 2. CE EXT connecting active CPU to
network shelf 3. cables connecting the above cards via the Junctor 4. if you
have no DTI hardware, ignore this message.
Action: 1. QPC411 SCG
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1346 of 2360

NWS0031
Clock switching function not performed. One or both of the QPC411 SCG
cards are disabled. No fault implied.
Action:
Severity: Critical.
NWS0042
SNMP trap: Yes
Network Card interface test failed. The PE continuity test was not performed.
Action:
Severity: Critical.
NWS0043
SNMP trap: Yes
The requested PE cannot be tested because: 1. Peripheral Controller is

disabled, or 2. the PE is not defined for the superloop, or 3. the PE shelf space
occupied by the superloop is empty.
Action:
Severity: Critical.
SNMP trap: Yes
NWS0101ps l1 l2 ln Two or more loops (L1, L2, etc.) on Peripheral Signaling card ps failed the
signaling test. Error code NWS201 is implied for these loops. Probable fault on
PS card.
Action: Try the tests again. If fault persists after the card is replaced, suspect: 1.
MISC card on active CPU 2. network cards L1, L2, etc. 3. CE EXT between active
CPU and affected network shelf, network, conference and TDS cards in the same
group 4. CPU cards. Loops may be tested separately using the LOOP L
command.
Severity: Critical.
NWS0103 ps
SNMP trap: Yes
Fault detected in outgoing signaling on Peripheral Signaling card ps. The

system is still able to signal using the bad card but the outgoing signaling rate
may be reduced.
Action: Repeat the LOOP ALL test, or test any terminal loop associated with the
PS card several times. If this message reappears, probable fault is on the PS card
or, if the fault indication appears when one CPU is active but not when the other
is active and the fault affects all groups, on: 1. either CE EXT connecting the
affected network shelf to the active CPU, or in the cable between the extenders;
or other PS cards or the MISC of the CPPU which is active when the fault
indication appears. 2. other PS cards or the MISC of the CPPU which is active
when the fault indication appears.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1347 of 2360

NWS0141 c
IGS card c failed to respond. Probable fault in: 1. IGS card c 2. CE EXT
connecting active CPU to network shelf 3. other IGS card, or 4. associated
cables
Action:
Severity: Critical.
NWS0142 c
SNMP trap: Yes
Could not switch clocks when System Clock Generator (SCG) card c was
providing clock. Fault may be: 1. either SCG 2. cables connecting SCG cards
via Junctor 3. CE EXT connecting active CPU to network shelf.
Action:
Severity: Critical.
NWS0143 n
SNMP trap: Yes
You cannot switch the clock controllers because the standby clock controller
n is software disabled.
Action: Enable it in LD 60 provided is operational.
Severity: Critical.
SNMP trap: Yes
NWS0201 loop s1 s2 sn Two or more shelves (s1, s2, etc.) on the loop failed the signaling test.
All cards failed the test on each shelf.
Action: See NWS301. If the loop is an RPE loop, go to LD 33. The fault may be
in 1. network card for the loop 2. loop cable to PE shelves 3. faults on shelves s1
to s4 (depending on card density) 4. network, conference and TDS cards in same
group 5. network extenders 6. CPU cards
Severity: Critical.
SNMP trap: Yes
NWS0202 loop s1 s2 Continuity test failed on this loop, shelves s1, s2. Signaling test was
completed in spite of the fault. The fault may be:
1. peripheral buffer or controller on shelves
2. interconnecting cable to PE shelves
3. network card
4. peripheral signaling cards
5. network, conference and TDS cards in the same group
6. network extenders
7. CPU cards
Note: ERR3036 can also occur if a loop on the QPC414 Network card is not
System Messages
Page 1348 of 2360

configured. This is not an error condition. To prevent ERR3036 occurring in
this
case, define the loop in LD17. Disable the unused loop.
Action:
Severity: Info.
NWS0203 loop
SNMP trap: Yes
Memory test on this loop failed. Timeslots associated with faulty memory
locations are disabled. The network card is probably faulty. If a LOOP L
command produces this response only on one the CPUs, the fault may be in
1. the CE EXT connecting the network group (in which loop is located) to the
CPU which is active when this message appears, or 2. in the cable connecting
these extenders
Action:
Severity: Critical.
NWS0204 loop
SNMP trap: Yes
The network circuit for this loop failed to respond to an ENLL, DISL, LOOP or
SHLF command.
Action: Check whether the network card is missing or disabled through the
faceplate switch. If a fault exists, then suspect the following: 1. the network card
2. the peripheral signaling card 3.the network, conference and TDS cards in the
same group 4. the network extenders 5. the CPU card
Severity: Critical.
SNMP trap: Yes
NWS0211 loop s1 s2 s One or more shelves (s1, s2, etc.) failed the signaling test. At least one
unit passed the signaling test. See message NWS301. If loop is an RPE loop,
go to LD 33. The fault may be: 1. network card 2. loop cable to PE shelves 3.
faults on shelves s1 to s4 4. network, Conference and TDS cards in same
group 5. network extenders 6. CPU cards
Action:
Severity: Critical.
SNMP trap: Yes
NWS0301 ls c1 c2 cn Two or more PE cards c1, c2, etc. on loop l shelf s failed the signaling test,
or the results of the shelf test varied. LD 30 automatically tests each shelf two
ways. If a card number is preceded by a minus sign, one or more units on that
553-3001-411
Standard 15.00
January 2006
Page 1349 of 2360

card were disabled. The fault may be: 1. one or more of cards c1, c2, etc. 2.
peripheral buffer or controller for shelf 3. loop cable to PE shelf 4. network card
the loop. If only one card is listed, an intermittent PE card fault is possible.
Action:
Severity: Critical.
NWS0302 l s
SNMP trap: Yes
More than half of the cards on specified shelf S could not be tested because
they were either busy or disabled, or there were no SL-1 telephones on shelf.
This is not a fault condition.
Action: Repeat test if desired.
Severity: Critical.
SNMP trap: Yes
NWS0401 l s c: u1 u2 un A fault has been detected on: 1. PE card L s c (u1, u2, do not appear in
the message), or 2. PE unit L s c u1u2. If a card or unit number is preceded by
a minus sign, the card or unit was disabled. The fault may be: 1. PE card l s c
peripheral buffer on the shelf 2. SL-1 or Digital sets associated with units u1,
u2, etc.
Action:
Severity: Critical.
NWS0501 l s c u
SNMP trap: Yes
The telephone at L s c u failed the signaling test. If the unit number is preceded
by a minus sign, the set was disabled. The fault may be: 1. PE card 2. the
telephone set
Action:
Severity: Minor.
NWS0502
SNMP trap: Yes
The network loop is not configured.

Action: Re-enter command.
Severity: Info.
NWS0601 loop
SNMP trap: No
The loop requested is a Digital Trunk Interface (DTI) or Digital Link Interface
(DLI).
Action: Use the DTI diagnostic instead (LD 60).
Severity: Info.
SNMP trap: No
System Messages
Page 1350 of 2360

NWS0602
DTI/DLI loop failed signaling test.

Action:
Severity: Critical.
NWS0603
SNMP trap: No
A previously faulty DTI/DLI loop passed the signaling test.

Action:
Severity: Minor.
NWS0604
SNMP trap: No
DTI loop is in a waiting state. A reset red alarm message has been sent.
Action:
Severity: Critical.
NWS0608
SNMP trap: No
Peripheral Software Download (PSDL) failure.

Action: Check the SDL messages.
Severity: Critical.
NWS0609
SNMP trap: Yes
The XNET/XPND network card has a problem.

Action: Check the card and its associated cable and repeat the command. If the
problem persists, pull the card and plug it back in. If the problem persists on the
same command again, replace the card.
Severity: Critical.
NWS0611
SNMP trap: Yes
You cannot use this command when the card is in an overload condition.
Action:
Severity: Info.
NWS0612
SNMP trap: No
Command parameter error; for NT8D02 Digital Line Card use: UNTT l s c u,
for all others use: UNTT l s c.
Action:
Severity: Info.
NWS0613
SNMP trap: No
The proper card is not equipped.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1351 of 2360

NWS0614
That command can not be completed. For NT8D02 Digital Line Card:
1. the unit is busy
2. the unit is manually disabled, or
3. the unit is not defined.
For all others:
1. the card is manually disabled, or
2. no unit is defined on the card.
Action:
Severity: Info.
NWS0615
SNMP trap: No
Loop must be a superloop.

Action:
Severity: Info.
NWS0620
SNMP trap: No
Express output queue full, CPU can not send the message to the MISP.
Action:
Severity: Info.
NWS0621
SNMP trap: Yes
The MISP output buffer is not available, possibly because the MISP has not
read
off the previous output message yet.
Action:
Severity: Info.
NWS0622
SNMP trap: Yes
Invalid message or invalid environment in which to send the message to the

MISP.
Action:
Severity: Info.
NWS0623
SNMP trap: Yes
Cannot send message to the line card.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1352 of 2360

NWS0624
Since this shelf contains at least one BRI line card, one must wait 45 seconds
before enabling the shelf/loop.
Action:
Severity: Info.
NWS0625
SNMP trap: Yes
Database error. Protected pointers missing.

Action:
Severity: Info.
NWS0626
SNMP trap: Yes
Self-test command only applies to the MISP network cards and BRI line cards.
Make sure you specify correct card.
Action:
Severity: Info.
NWS0627
SNMP trap: Yes
The MISP card must be in MANUAL DISABLED state to perform the selftest.
Action:
Severity: Info.
NWS0628
SNMP trap: No
Line card must be disabled to invoke the self-test.

Action:
Severity: Info.
NWS0630
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Loop is unequipped.
Action:
Severity: Info.
NWS0631
Loop is not responding.

Action:
Severity: Info.
NWS0632
553-3001-411
Selftest failed. With X11 Release 19 and later, the following text will be
appended
to the message depending on the failure cause.
68020 CPU = The microprocessor is faulty.
DRAM = The DRAM is faulty.
DRAM PARITY ERROR = Parity was detected on the DRAM.
Standard 15.00
January 2006
Page 1353 of 2360

AO7 CHIP = The AO7 is faulty.
MFP = The MFP is faulty.
INTERNAL LPBK = The internal loopback has failed.
R75 1 = The first R75 chip failed.
R75 2 = The second R75 chip failed
R75 3 = The third R75 chip failed.
R75 4 = The fourth R75 chip failed.
S01 1 = The first S01 chip failed.
S01 2 = The second S01 chip failed.
S01 3 = The third S01 chip failed.
S01 4 = The fourth S01 chip failed.
NOT RESPONDING = The Meridian 1 software cannot communicate with the
BRSC card, or the BRSC card cannot send the self-test results to the Meridian
1
software.
Action: For all failures, replace the BRSC card.
Severity: Info.
NWS0633
SNMP trap: Yes
MISP status is undefined (MISP SLSTAT bit combination).

Action:
Severity: Info.
NWS0635
SNMP trap: Yes
No response from the line card.

Action:
Severity: Info.
NWS0636
SNMP trap: Yes
Cannot invoke MISP selftest.

Action:
Severity: Info.
NWS0637
SNMP trap: Yes
SNMP trap: Yes
SNMP trap: Yes
Selftest passed.
Action:
Severity: Info.
NWS0638
Unit is not equipped.

Action:
Severity: Info.
System Messages
Page 1354 of 2360

NWS0639
TEI test could not be performed.

Action:
Severity: Info.
NWS0640
SNMP trap: Yes
No response from the MISP.

Action:
Severity: Info.
NWS0641
SNMP trap: Yes
Cannot execute command on MISP. Use LD 32.

Action:
Severity: Info.
NWS0650
SNMP trap: No
Command not allowed for XCT loops.

Action:
Severity: Info.
NWS0652
SNMP trap: No
This command is not valid on phantom loops, since phantom loops do not
physically exist.
Action:
Severity: Info.
NWS0653
SNMP trap: No
Cannot execute command on BCS Phantom loop. Use Overlay 32.

Action:
Severity: Info.
NWS0654
SNMP trap: No
No Memory Test on BCS Phantom Loop.

Action:
Severity: Info.
NWS0800
SNMP trap: Yes
The timeslot or junctor is busy. The test was not completed.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1355 of 2360

NWS0801
The continuity test failed.

Action:
Severity: Info.
NWS0802
SNMP trap: No
Network Card (NT8D04) failed to respond.

Action:
Severity: Info.
NWS0803
SNMP trap: Yes

Action:
Severity: Info.
NWS0805
SNMP trap: No
Cannot send message to Network Card (NT8D04).

Action:
Severity: Info.
NWS0888
SNMP trap: Yes
Invalid input. The loop or junctor number is out-of-range; the command is not
allowed on superloops; or the terminating or transmitting party is disabled.
Action:
Severity: Info.
NWS0927
SNMP trap: No
Network Card (NT8D04) failed to respond within 10 seconds after sending a

request to read or clear a Peripheral Controller (NT8D01) maintenance
display.
Action: If the command fails a second time, check the status of the Network and
Controller Card.
Severity: Info.
NWS0928
SNMP trap: Yes
Superloop number must be multiple of 4.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1356 of 2360

NWS0929
Shelf number is not equipped.

Action:
Severity: Info.
NWS0930
SNMP trap: Yes
Cannot send CPED or RPED message to Network Card (NT8D04).

Action: Make sure the Network Card is installed and enabled.
Severity: Info.
NWS0931
SNMP trap: Yes
Cannot determine if the XTRUNK value is a Universal Trunk or E&M/Dictation

Trunk (NT8D14/NT8D15).
Action:
Severity: Info.
NWS0948
SNMP trap: Yes
Specified Peripheral Software (PSW) version number is out-of-range (1-99).

Action: Try again.
Severity: Info.
NWS0960
SNMP trap: Yes
This command is not valid on virtual superloops since virtual superloops do not
physically exist.
Action:
Severity: Minor.
NWS0961
SNMP trap: No
This command is not valid for IPMG loops

Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1357 of 2360
OHAS: Off-Hook Alarm Security

Messages
OHAS0000 dn l s c u hh:mm:ss Off-Hook Alarm has occurred due to dial tone or interdigit
timeout.
Action:
Severity: Minor.
SNMP trap: No
OHAS0001 dn l s c u hh:mm:ss Off-Hook Alarm has occurred due to forced out-of-service call
treatment.
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1358 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1359 of 2360
OSM: Operating System Messaging

Messages
OSM0000
Example message for {string}.

Action:
Severity: Info.
OSM0001
SNMP trap: No
Cannot create pipe, errno x.

Action:
Severity: Minor.
OSM0002
SNMP trap: No
Cannot open pipe for read/write, errno x.

Action:
Severity: Minor.
OSM0003
SNMP trap: No
Cannot create OSM File semaphore, errno x.

Action:
Severity: Minor.
OSM0004
SNMP trap: No
Cannot open OSM file for appending, errno x.

Action:
Severity: Minor.
OSM0005
SNMP trap: No
Cannot open save file for writing, errno x.

Action:
Severity: Minor.
OSM0006
SNMP trap: No
Cannot get OSM Save file semaphore errno x.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1360 of 2360

OSM0007
Cannot save OSM file (copy failed), errno x.

Action:
Severity: Minor.
OSM0008
SNMP trap: No
Cannot get OSM write file semaphore, errno x.

Action:
Severity: Minor.
OSM0009
SNMP trap: No
Cannot fprintf to osm File, errno x.

Action:
Severity: Minor.
OSM0010
SNMP trap: No
Cannot read from pipe, errno x.

Action:
Severity: Minor.
OSM0011
SNMP trap: No
SNMP trap: No
OsmTask has died.

Action:
Severity: Minor.
OSM0012
Cannot spawn osm Task, errno x.

Action:
Severity: Minor.
OSM0013
SNMP trap: No
Cannot spawn period task, errno x.

Action:
Severity: Minor.
OSM0014
SNMP trap: No
Daily log file save failed. Check CMDU power on/off switch.
Action: Be sure the IOP enable/disable switch is enabled (up).
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1361 of 2360

OSM0015
Disk getting full. Only x bytes remain.

Action: Contact your technical service representative.
Severity: Minor.
OSM0016
SNMP trap: Yes
X byte log file size limit exceeded. Disk getting full, only y bytes remain.
Action: Contact technical support.
Severity: Minor.
OSM0017
SNMP trap: No
Cannot flush to log file errno {x}.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1362 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1363 of 2360
OSN: On-Site Notification

Messages
OSN0000
On site notification record for an ESA call.

Action:
Severity: Critical.
OSN0001
SNMP trap: Yes
ESA caller information is not linked to the OSN key because it already has a
caller information linked.
Action: Obtain the call record from the OSN output device.
Severity: Major.
OSN0002
SNMP trap: Yes
ESA caller information is not linked because the OSN set is found to be
disabled.
Action: Obtain the call record from the OSN output device.
Severity: Major.
SNMP trap: Yes
System Messages
Page 1364 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1365 of 2360
OVD: Overload Monitor

The Overload Monitor program is resident in the system and is loaded if:
excessive input messages from a particular PE card have been detected, or
the system input buffer overflows for a predetermined period of time (1.5 to 2
min).
In either case, an attempt is made to determine whether the overload is due to
a hardware fault; if so, the faulty device is disabled and an OVD message is
output.
Messages
OVD0001 l s c (u)
A 500/2500 card or unit has been disabled.
Action:
Severity: Critical.
OVD0002 l s c (u)
SNMP trap: Yes
An SL-1 line card or unit has been disabled.
Action:
Severity: Critical.
OVD0003 l s c (u)
SNMP trap: Yes
A trunk card or unit has been disabled.
Action:
Severity: Critical.
OVD0004 l s c (u)
SNMP trap: Yes
A Digital set line card or unit has been disabled. Unterminated or unequipped
units on QPC578 or NT8D02AA line cards may produce erroneous OVD004
messages.
Action: To avoid this condition, configure and disable these units.

Severity: Critical.
OVD0005 l s c (u)
SNMP trap: Yes
A Digitone Receiver card or unit has been disabled.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1366 of 2360

OVD0008 loop
Overload detected from Local Carrier Buffer (LCB) card on specified loop. The
carrier status monitoring function on the LCB has been disabled.
Action:
Severity: Critical.
OVD0010 l s c (u)
SNMP trap: Yes
An RAN trunk card or unit has been disabled.
Action:
Severity: Critical.
OVD0013 l s c (u)
SNMP trap: No
A MFC Sender/Receiver card or unit (QPC327 or NT5K21AA) has been

disabled.
Action:
Severity: Critical.
OVD0021 loop
SNMP trap: No
Excessi e input has been detected from specified loop. The loop was disabled.
A minor alarm indication is given to all customers served by the loop. This
message indicates a probable fault in: 1. Network card for the loop 2.
Peripheral Buffer or Controller for the loop3. interconnecting cables 4. any PE
card
Action:
Severity: Critical.
OVD0022 loop
SNMP trap: Yes
A large number of invalid input messages were received from more than one
PE shelf on the loop. The loop has been disabled. Probable fault on: 1.
Network card for the loop 2. Peripheral Buffer or C 3. PE cabling any PE card
Action:
Severity: Critical.
OVD0023 l s
SNMP trap: Yes
A large number of invalid input messages was received from shelf s. Attempts
to disable the offending PE card(s) failed; the loop has been disabled.
Probable fault on: 1. Peripheral Buffer or Controller on the shelf 2. any PE card
on indicated shelf 3. Network card for the loop 4. PE cabling
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1367 of 2360

OVD0024 l s
Shelf s has been disabled due to overload. Probable fault in: 1. Peripheral
Buffer or Controller on the shelf 2. any PE card on that shelf
Action:
Severity: Critical.
OVD0031 ps
SNMP trap: Yes
Excessive or invalid input has been detected from Peripheral Signaling card.
The card was disabled. A minor alarm indication is given to all customers. This
message indicates a probable fault in: 1. PS card 2. one of the network card
associated with the PS 3. conference card or its network cable
Action:
Severity: Critical.
OVD0032 loop
SNMP trap: Yes
Too many messages from loop DTI2 loop. Loop is disabled.

Action:
Severity: Critical.
OVD0033 loop ch
SNMP trap: Yes
Channel ch of a DTI loop is disabled due to overload. Probable fault: 1. DTI

card 2. carrier 3. cables
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1368 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1369 of 2360
OVL: Overlay Loader

The Overlay Loader manages the Overlay area in memory that is used to load
administration and maintenance programs.
The facility to disable the primary tape unit, if the unit is faulty, is included in
the Overlay Loader. The commands to disable the tape unit will be issued only
when no other Overlay activity is in progress; for instance, when an abort
command is issued preceding the disable command.
Problems and status of the Overlay Loader are indicated in OVL messages.
Messages
OVL0000
This is the Program identifier which indicates that the user has already logged
into the system.
Action:
Severity: Info.
OVL0001
SNMP trap: Yes
Loading already in progress.

Action: Wait for completion of loading or enter **** to halt loading.
Severity: Info.
OVL0003 xx
SNMP trap: Yes
Requested program xx is not in the tape directory.

Action: Check if desired program should be in directory. If program should be
present, inform manufacturer of defective tape.
Severity: Minor.
OVL0009
SNMP trap: Yes
Tape contains software generic different from that resident in system memory.
The programs are not compatible, Overlay program requested was not loaded.
Action: Replace tape in drive with one used when system was loaded.
Severity: Minor.
OVL0011 xx MID
SNMP trap: Yes
System is automatically executing maintenance Overlay xx.

Action: DO NOT login until these tasks are completed, they may be essential to
maintain system integrity. After a few minutes, press the carriage return to
recheck system status.
Severity: Minor.
SNMP trap: No
System Messages
Page 1370 of 2360

OVL0014
Incorrect parameters.
Action: Check the command and re-enter the code.
Severity: Minor.
OVL0015
SNMP trap: Yes
SNMP trap: Yes
Password is incorrect.
Action:
Severity: Minor.
OVL0016
Allowed limits of password exceeded.

Action:
Severity: Major.
OVL0017
SNMP trap: No
Overlay cannot be loaded from a TTY.

Action:
Severity: Minor.
OVL0020
SNMP trap: Yes
System has aborted the current overlay program because:

1. another TTY has successfully logged in
2. the overlay area is required because of a system alarm, a system audit or
daily
routine.
Action:
Severity: Info.
OVL0021 aaa
SNMP trap: Yes
System requires the Overlay area one of the following tasks (aaa): 1. MID daily midnight routines are scheduled 2. ALRM - system alarm has been
triggered 3. AUD - system requires software audit 4. CDR - system requires
test of CDR facility 5. SMFR - soft memory failure recovery 6. PBXT - PBXT
message waiting lamp tests are scheduled
Action: Complete present work as soon as possible and enter **** followed by
LOGO.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1371 of 2360

OVL0022
Manual loading of this program is prohibited.

Action:
Severity: Info.
OVL0023
SNMP trap: Yes
Loading Overlay program from this TTY is not allowed.

Action:
Severity: Minor.
OVL0024
SNMP trap: Yes
Taurus download pointer NIL.

Action:
Severity: Minor.
OVL0111
SNMP trap: Yes
The Overlay area is being used. The data output with the OVL111 are defined
below. 1. OVL111 00 IDLE = System is idle. A login will result in a ">" prompt.
2. OVL111 xx BKGD = Overlay area is currently executing background task
(Overlay nn). A login will result in a ">" prompt indicating that background task
has been aborted and the Overlay loader is ready for further commands. 3.
OVL111 00 TTY x = TTY. x has control of the Overlay area. No Overlay
program is loaded. 4. OVL111 nn TTY x = TTY. x or maintenance set has
control of the Overlay area. Overlay program nn is loaded. DO NOT load in
until user has been identified and given a chance to complete his task or to
stop. 5. OVL111 00 SL-1= maintenance set has control of the Overlay area.
No Overlay program is loaded. 6. OVL111 nn yyy = System is automatically
executing a maintenance task. DO NOT login unless absolutely necessary,
until these tasks are completed. They may be essential to maintain system
integrity. Recheck system status by pressing the carriage return key again
after a few minutes.
Action:
Severity: Info.
OVL0202
SNMP trap: Yes
Route member does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1372 of 2360

OVL0305
Bad message received from the System Monitor (NT8D22).

Action: Use STAT XSM command in LD 37 to check the System Monitor
status.
Check the cabling between the System Monitor and the SDI port.
Severity: Info.
OVL0306
SNMP trap: Yes
This Overlay can not be active during Peripheral Software Download (PSDL).
Action: 1. Wait until PSDL is complete.
2. Use the SUSP command to suspend the PSDL and load the required program
(LD xx SUSP). Use SUSP with caution.
Severity: Info.
OVL0309
SNMP trap: Yes
You do not have access to that Overlay.

Action:
Severity: Info.
OVL0310
SNMP trap: Yes
With LAPW enabled, maintenance sets are not allowed to load this Overlay.
Action:
Severity: Info.
OVL0352
SNMP trap: Yes
List requested is not system speed call list (network speed call).
Action:
Severity: Info.
OVL0353
SNMP trap: No
The security cartridge cannot be read, or the cartridge ID does not match the
ID
in the directory file. LD 135 and LD 137 can still be accessed.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1373 of 2360

OVL0354
Tape ID does not match system ID. Incorrect tape or disk is being used, or
there
is a system ID cartridge malfunction on MSI. LD 135 and LD 137 can still be
accessed.
Action:
Severity: Info.
OVL0355
SNMP trap: Yes
The directory file cannot be read to obtain the ID for comparison to security
and
system IDs. LD 135 and LD 137 can still be accessed.
Action:
Severity: Info.
OVL0400
SNMP trap: Yes
Failed log on attempts by incorrect password (PWD1 or PWD2).Output data

may
be any of the following:
Where:
x = TTY x is locked out. Too many invalid passwords
x y = x failed logins on TTY y
TTYx y = TTYx was locked out y times
Action:
Severity: Info.
OVL0401
SNMP trap: Yes
The Audit Trail buffer is full. It will now start to wrap.

Action:
Severity: Info.
OVL0402
SNMP trap: Yes
There is not enough memory for the Audit Trail. It will now start to wrap.
Action:
Severity: Info.
OVL0403 x
SNMP trap: Yes
You have logged on in HOST mode on TTY port x. Other ports will not receive
any messages (CDR, BUG, ERR, MTC, SCH or TRF) output to this port.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1374 of 2360

OVL0404 x aaa bbb TTY port x is in HOST mode and this TTY will not receive message types:
aaa bbb. Where messages types can be one or more of CDR, BUG, ERR,
MTC,
SCH or TRF. MTC represents all maintenance messages.
Action:
Severity: Info.
OVL0405 xx
SNMP trap: No
Attempt to load an Overlay program xx on A2 disk.

Action: You must restore disks to the hard disk before using the Overlay
programs on the A2 disk.
Severity: Info.
OVL0407 xx yy
SNMP trap: Yes
Requested number of cache buffers cannot be allocated. Protected data store

is
below safety limit. Increase the memory before more cache buffers can be
allocated. Where: xx = # buffers requested and yy = # buffers allocated.
Action:
Severity: Info.
OVL0408 xx
SNMP trap: No
Too many priority Overlays. Where: xx = number of priority Overlays which

have
been removed automatically.
Action:
Severity: Info.
OVL0409
SNMP trap: No
Initialization of OVL pipe failed.

Action:
Severity: Info.
OVL0410
SNMP trap: Yes
No pipe is available for use.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1375 of 2360

OVL0414
Send character to Overlay task through pipe failed.

Action:
Severity: Info.
OVL0415
SNMP trap: Yes
Displayed after a successful login if the Last Login Identification feature is

enabled. It contains the time and date of the last login and the number of failed
login attempts. The format is:
TTYxx nn PWD yyy mm/dd hh:mm
Where:
xx = the TTY port number
nn = number of failed login attempts count since the last login at this port
yyy = password identification = 1 for PWD1 or 2 for PWD2
00-99 = indicates LAPW password number between 00 and 99
mm/dd = last login date hh:mm = last login time
Action:
Severity: Info.
OVL0416
SNMP trap: Yes
You cannot monitor this port.

Action: Try another port.
Severity: Info.
OVL0417
SNMP trap: Yes
Password level is incorrect.

Action: Login with PWD2 password, or a LAPW password that allows the
command.
Severity: Info.
OVL0418
SNMP trap: Yes
The monitor feature is already in use.

Action: Use MON OFF to turn the monitoring feature off before using it on
another port.
Severity: Info.
OVL0419
SNMP trap: Yes
Send print (SPRT) is already in use.

Action: Use SPRT OFF to turn the feature off, then use SPRT xx to turn it on
another port.
Severity: Info.
SNMP trap: Yes
System Messages
Page 1376 of 2360

OVL0420
That port is busy, or already logged in.

Action:
Severity: Info.
OVL0421
SNMP trap: Yes
That port does not physically exist.

Action:
Severity: Info.
OVL0422
SNMP trap: Yes
That TTY port type is not SCH or MTC.

Action:
Severity: Info.
OVL0423
SNMP trap: Yes
This is not a logged in port.

Action:
Severity: Info.
OVL0424
SNMP trap: Yes
The maximum number of users are already logged in.

Action:
Severity: Info.
OVL0425
SNMP trap: Yes
You cannot force logout yourself.

Action: Check the port number when using the FORC command.
Severity: Info.
OVL0426
SNMP trap: Yes
There is not enough memory available for the Overlay data area.
Action:
Severity: Info.
OVL0428
SNMP trap: Yes
Login name and password combination is invalid.

Action: Check the password and login name and try again.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1377 of 2360

OVL0429
Overlay memory space is in use.

Action:
Severity: Info.
OVL0430
SNMP trap: Yes
Send message command is already turned off.

Action:
Severity: Info.
OVL0431
SNMP trap: Yes
PWD1 password has expired.

Action: Please log into Call Server through a serial port to change your
password.
Severity: Major.
OVL0432
SNMP trap: No
PWD2 password has expired.

Action: Please log into Call Server through a serial port to change your
password.
Severity: Major.
OVL0434
SNMP trap: No
Unable to initialize system message lookup.

Action:
Severity: Info.
OVL0435 n
SNMP trap: Yes
Invalid lookup type received by help task: n.

Action:
Severity: Info.
OVL0436 n m
SNMP trap: No
B-tree read failed for language n, rrn = m

Action:
Severity: Info.
OVL0437 n
SNMP trap: Yes
Unable to open message file for language n.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1378 of 2360

OVL0438 n
Could not open B-tree index file for language n.

Action:
Severity: Info.
OVL0439 n
SNMP trap: Yes
Unable to read B-tree root page for language n.

Action:
Severity: Info.
OVL0440 n
SNMP trap: Yes
B-tree initialization failed for language n.

Action:
Severity: Info.
OVL0441
SNMP trap: Yes
Help text could not be found for the specified error code.
Action:
Severity: Info.
OVL0442
SNMP trap: Yes
The error code specified is not a valid error code.

Action:
Severity: Info.
OVL0443
SNMP trap: Yes
SNMP trap: Yes
Unable to send request.

Action:
Severity: Info.
OVL0444
Unable to create help task queue.

Action:
Severity: Info.
OVL0446
SNMP trap: No
The LON and LOF commands are not applicable to MSDL TTY.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1379 of 2360

OVL0447
Use LD 135 for Option 81 Core Common Equipment Diagnostic. LD 35 does

not
apply.
Action:
Severity: Info.
OVL0448
SNMP trap: Yes
System message lookup is temporarily unavailable.

Action: Wait 30 seconds and repeat request.
Severity: Info.
OVL0451
SNMP trap: Yes
TTY is not a low speed link.

Action:
Severity: Info.
OVL0700
SNMP trap: Yes
Resident debug package is not equipped.

Action:
Severity: Info.
OVL0777
SNMP trap: No
Resident debug package is already loaded.

Action:
Severity: Info.
OVL0779
SNMP trap: No
There is more than one LSL configured in the system.

Action: Use AX n, where n is the TTY number of the LSL to be connected to.
Severity: Info.
OVL0781
SNMP trap: Yes
This overlay is not allowed for IP expansion cabinet.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1380 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1381 of 2360
PCH: System Patch reports

Messages
PCH0100
Cannot create semaphore.

Action:
Severity: Minor.
PCH0101
SNMP trap: No
Invalid semaphore ID or task timed out.

Action:
Severity: Minor.
PCH0102
SNMP trap: No
Warning: failed to add symbol n to symbol table.

Action:
Severity: Minor.
PCH0103
SNMP trap: No
Warning: failed to remove symbol n from symbol table.

Action:
Severity: Minor.
PCH0104
SNMP trap: No
Unable to create loadware status file %s.

Action:
Severity: Info.
PCH0107
SNMP trap: No
Cannot write back activate memory list. Patch data inconsistency might have
occurred.
Action:
Severity: Minor.
PCH0108
SNMP trap: No
Program corruption. Restore memory list if null.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1382 of 2360

PCH0109
Program corruption. Activate memory list if null.

Action:
Severity: Minor.
PCH0110
SNMP trap: No
PATCH x ACTIVATED. Name=a, Ref#=b, PRS#=c, File=d.

Action:
Severity: Minor.
PCH0111
SNMP trap: No
PATCH x DEACTIVATED. Name=a, Ref#=b, PRS#=c, File=d.

Action:
Severity: Minor.
PCH0113
SNMP trap: No
Cannot restore back memory. Patch data inconsistency might have occurred.
Action:
Severity: Minor.
PCH0115
SNMP trap: No
Error activating patch x. buildMemLists call failed.

Action:
Severity: Minor.
PCH0116
SNMP trap: No
Error writing memory. Cannot activate patch x.

Action:
Severity: Minor.
PCH0117
SNMP trap: No
Error writing memory. Cannot deactivate patch x.

Action:
Severity: Minor.
PCH0119
SNMP trap: No
Cannot load patch. System contains the maximum number of patches already.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1383 of 2360

PCH0120
Error writing to retention file. Retention info might be out of synch.

Action:
Severity: Minor.
PCH0123
SNMP trap: No
Error loading patch from n.

Action:
Severity: Minor.
PCH0124
SNMP trap: No
Internal error, cannot get summary patch status at this time.

Action: Check the report log file for further information.
Severity: Minor.
PCH0125
SNMP trap: No
Internal error, cannot deactivate patch at this time.

Severity: Minor.
PCH0126
SNMP trap: No
Internal error, cannot activate patch at this time.

Severity: Minor.
PCH0129
SNMP trap: No
Internal error, cannot get detailed patch status at this time.

Severity: Minor.
PCH0130
SNMP trap: No
Internal error, cannot remove patch at this time.

Severity: Minor.
PCH0131
SNMP trap: No
Error deleting patch status record. Record not found.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1384 of 2360

PCH0132
Patch status tail pointer is null.

Action:
Severity: Minor.
PCH0134
SNMP trap: No
Full patch path length exceeded.

Action:
Severity: Minor.
PCH0136
SNMP trap: No
Patch filename empty in patchload.

Action:
Severity: Minor.
PCH0137
SNMP trap: No
Patch filename is not a full path in patchload.

Action:
Severity: Minor.
PCH0138
SNMP trap: No
Patch handle out-of-range in patchload

Action:
Severity: Minor.
PCH0139
SNMP trap: No
Cannot allocate memory for patchload.

Action:
Severity: Minor.
PCH0141
SNMP trap: No
Error reading patch file during patchload.

Action:
Severity: Minor.
PCH0142
SNMP trap: No
Patch Release x does not match the system Release y.

Action: Recreate the patch for the system release.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1385 of 2360

PCH0143
Cannot determine default patch directory from DLO.

Action:
Severity: Minor.
PCH0144
SNMP trap: No
Patch retention array not initialized.

Action:
Severity: Minor.
PCH0179
SNMP trap: No
Could not retrieve reten.pch from IPMG.

Action:
Severity:
PCH0181
SNMP trap: No
Warning error reactivating patch. Memory patch memory mismatch. Manual

Intervention required.
Severity: Major.
PCH0187
SNMP trap: Yes
mdp Refresh: xxxxx on Cabinet n

Action: See reports logs for more information
Severity:
PCH0188
SNMP trap: No
mdp Uninstall: xxxxx on Cabinet n

Severity:
PCH0189
SNMP trap: No
mdp Install: xxxxx on Cabinet n

Severity:
PCH0190
SNMP trap: No
ACPD Failed on Cabinet: n, Reason: x

Reason:
0 - IPMG could not get the IP address of the Call Server
1 - IPMG could not copy the retention file from the CS
2 - IPMG could not read the retention file into memory
3 - IPMG could not copy required pathc files form the CS
4 - IPMG could not synchronize all of its patches to the CS retention file
System Messages
Page 1386 of 2360

5 - IPMG could not update the deplist directory or clean up the patch directory
6 - Link went down between the IPMG and the CS
7 - Invalid return value on CS
8 - There is a software mismatch between the IPMG and the CS
9 - Poll message failed, failure on IPMG
Severity:
PCH0191
SNMP trap: No
ACPD: "Information about ACPD such as Successfully completed, Stopped

etc..." on cabinet: n
Action:
Severity:
PCH0192
SNMP trap: No
ACPD Failed: reason of failure

Severity:
PCH0193
SNMP trap: No
Information about ACPD such as Successfully completed, Stopped etc

Action:
Severity:
PCH0200
SNMP trap: No
Cannot initialize patch semaphore.

Action:
Severity: Minor.
PCH0201
SNMP trap: No
Warning: cannot initialize patch retention. Patch retention will not be possible.
Action:
Severity: Minor.
PCH0202
SNMP trap: No
Warning: patch retention at diskos level failed. Some or all diskos patches may
not have been retained.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1387 of 2360

PCH0203
Unable to open patch file n.

Action:
Severity: Minor.
PCH0204
SNMP trap: No
Cannot allocate protected memory for patch

Action:
Severity: Minor.
PCH0205
SNMP trap: No
Error in reading patch file n.

Action:
Severity: Minor.
PCH0206
SNMP trap: No
Memory patch from n to m is out-of-range.

Action: Remake and retry the patch.
Severity: Minor.
PCH0207
SNMP trap: No
Memory patch mismatch between expected and actual. Either the patch was
created incorrectly or it is the wrong patch for this software release.
Action:
Severity: Minor.
PCH0208
SNMP trap: No
Error accessing patch file n.

Action:
Severity: Minor.
PCH0210
SNMP trap: No
Error reading patch file n.

Action:
Severity: Minor.
PCH0211
SNMP trap: No
Patch corrupted. Address to patch is out-of-range.

Severity: Minor.
SNMP trap: No
System Messages
Page 1388 of 2360

PCH0212
Address of patch code (x) is out-of-range.

Action: Take the patch out, then try to load and activate it again.
Severity: Minor.
PCH0213
SNMP trap: No
Failed to find start of WORKSHED loop near x.

Action:
Severity: Minor.
PCH0214
SNMP trap: No
System error. Patcher cannot be initialized.

Action:
Severity: Minor.
PCH0215
SNMP trap: No
Invalid patch file format.

Severity: Minor.
PCH0216
SNMP trap: No
Unexpected code at start of SL-1 global procedure n. The patch might not
match the release that is loaded.
Action:
Severity: Minor.
PCH0217
SNMP trap: No
Unexpected code in SL-1 patch global procedure n.

Severity: Minor.
PCH0219
SNMP trap: No
Unexpected code in SL-1 global procedure n.

Severity: Minor.
PCH0220
SNMP trap: No
NULL filename passed to readInPatch.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1389 of 2360

PCH0221
Unexpected code at start of C function n at x. The patch might not match the
release that is loaded.
Action:
Severity: Minor.
PCH0222
SNMP trap: No
Checksum of patch read into memory x. does not match expected checksum x
Action:
Severity: Minor.
PCH0223
SNMP trap: No
Error reading patch file to compute checksum.

Action:
Severity: Minor.
PCH0224
SNMP trap: No
Error writing checksum to patch file.

Action:
Severity: Minor.
PCH0300
SNMP trap: No
Handle n out-of-range in writeRetenRec.

Action:
Severity: Minor.
PCH0301
SNMP trap: No
Retention structure not initialized. Patcher is most likely unusable.

Action:
Severity: Minor.
PCH0302
SNMP trap: No
Cannot open patch retention file n.

Action:
Severity: Minor.
PCH0303
SNMP trap: No
Error accessing patch retention file n.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1390 of 2360

PCH0304
Error writing to patch retention file n.

Action:
Severity: Minor.
PCH0305
SNMP trap: No
Error closing patch retention file n.

Action:
Severity: Minor.
PCH0307
SNMP trap: No
Cannot get patch retention directory from DLO.

Action:
Severity: Minor.
PCH0308
SNMP trap: No
Error remaining patch retention file from n to m. Patch retention may not be
performed properly.
Action:
Severity: Minor.
PCH0309
SNMP trap: No
Error creating patch retention file n.

Action:
Severity: Minor.
PCH0310
SNMP trap: No
Patch retention array re-initialized.

Action:
Severity: Minor.
PCH0311
SNMP trap: No
Patch retention file re-created.

Action:
Severity: Minor.
PCH0312
SNMP trap: No
Cannot allocate protected memory for patch retention.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1391 of 2360

PCH0313
Cannot initialize patch retention.

Action:
Severity: Minor.
PCH0314
SNMP trap: Yes
Internal error, unknown patch retention level.

Action:
Severity: Minor.
PCH0315
SNMP trap: No
Cannot allocate Diskos memory for patch retention.

Action:
Severity: Minor.
PCH0316
SNMP trap: Yes
Error reading temporary patch retention file n. Retention may not be performed
properly.
Action:
Severity: Minor.
PCH0317
SNMP trap: Yes
Internal error, bad patch retention record.

Action:
Severity: Minor.
PCH0318
SNMP trap: Yes
Cannot get semaphore fro patch retention.

Action:
Severity: Minor.
PCH0319
SNMP trap: No
Error regaining patch from n.

Action:
Severity: Minor.
PCH0320
SNMP trap: Yes
Cannot retain patch from n. It is already loaded.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1392 of 2360

PCH0321
Retention data inconsistency, patch handle = x.

Action:
Severity: Minor.
PCH0322
SNMP trap: No
Cannot activate retained patch.

Action:
Severity: Minor.
PCH0323
SNMP trap: Yes
Error initializing patch retention data. Patcher inoperable.

Action:
Severity: Minor.
PCH0400
SNMP trap: Yes
Internal error, invalid parameter memSpec.

Action:
Severity: Minor.
PCH0401
SNMP trap: No
Internal error, invalid empty memSpec.

Action:
Severity: Minor.
PCH0402
SNMP trap: No
Internal error, invalid memlist elements.

Action:
Severity: Minor.
PCH0403
SNMP trap: No
Internal error, invalid argument to patch fix hits.

Action:
Severity: Minor.
PCH0404
SNMP trap: No
Cannot get task n priority, errno x.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1393 of 2360

PCH0405
Cannot restore task n priority back to y, errno z.

Action:
Severity: Minor.
PCH0406
SNMP trap: No
Internal error, null mempec.

Action:
Severity: Minor.
PCH0407
SNMP trap: No
Warning: patchMemWrite task list full.

Action:
Severity: Minor.
PCH0408
SNMP trap: No
Cannot suspend task x, errno y.

Action:
Severity: Minor.
PCH0409
SNMP trap: No
Could not write memory because it is being accessed by a task.

Action:
Severity: Minor.
PCH0410
SNMP trap: No
Warning: cannot resume task n, errno y.

Action:
Severity: Minor.
PCH0411
SNMP trap: No
Internal error, null memList.

Action:
Severity: Minor.
PCH0412
SNMP trap: No
PatchMemWrite request is out of range.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1394 of 2360

PCH0500
Cannot get semaphore for patch sanity check.

Action:
Severity: Minor.
PCH0501
SNMP trap: No
Cannot deactivate patch suspected to be bad.

Action:
Severity: Minor.
PCH0502
SNMP trap: No
Deactivating patch suspected of causing sysload.

Action:
Severity: Minor.
PCH0503
SNMP trap: Yes
Cannot update patch days-in-service at midnight.

Action:
Severity: Minor.
PCH0504
SNMP trap: No
Deactivating patch suspected to be causing initializations.

Action:
Severity: Minor.
PCH0510
SNMP trap: Yes
Link errors. Report errors that occurred either during socket creation or data
transmission.
Action:
Severity: Info.
PCH0511
SNMP trap: No
Patch corruption. Errors regarding patch corruption, such as patch data

corrupt or null pointers.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1395 of 2360

PCH0512
Semaphore
The patch data cannot be accessed at this moment. This is certainly due to the
fact that patch data is being accessed for another patch command. This
should be a temporary problem.
Action:
Severity: Info.
PCH0513
SNMP trap: No
Unable to write to retention file. The patch operation has been performed, but
it was not possible to update the retention file. Thus, patch status (ins, loaded)
will not be recovered after an initialization.
Action:
Severity: Info.
PCH0514
SNMP trap: No
File error. Regarding errors about patch file (for example, wrong format, file
does not exist).
Action:
Severity: Info.
PCH0515
SNMP trap: No
Unable to load patch. An unknown error occurred that keeps patch file from
being loaded.
Action:
Severity: Info.
PCH0516
SNMP trap: No
System limit reached. Too many patches are currently loaded on the switch.
Action:
Severity: Info.
PCH0517
SNMP trap: No
Release mismatch. The patch and system releases do not match. Both
release are given away..
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1396 of 2360

PCH0518
Memory problems. A memory problem occurred (for command cpins.) Patch

cannot be activated.
Action:
Severity: Major.
PCH0519
SNMP trap: No
Patch conflict. A conflict has been detected between two patches. Patch
names are given away.
Action:
Severity: Info.
PCH0520
SNMP trap: No
Error in patch code.

The code contained within the patch could not be executed (for cpins). This
may be due to a release problem.
Action:
Severity: Info.
PCH0521
SNMP trap: No
Server's task not spawned.

Action:
Severity: Info.
PCH0522
SNMP trap: No
Tftp directly adding failed. It was not possible to add the default patch directory
to the tftp daemon. Task is aborted.
Action:
Severity: Major.
PCH0523
SNMP trap: No
Socket error. It was not possible to perform basic socket operation to

communicate with the main cabinet. Task is aborted.
Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1397 of 2360
PMS: Property Management System

Interface
The Property Management System Interface (PMSI) is an optional feature.
The PMSI program monitors call processing continuously and outputs
problems in the form of PMS messages.
Messages
PMS0610
PMS input/output block pointer does not exist.

Action:
Severity: Minor.
PMS0611
SNMP trap: Yes
PMS link does not exist. For example, no unprotected data.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1398 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1399 of 2360
PRI: Primary Rate Interface Diagnostic

(LD 60)
The Primary Rate Interface (PRI) diagnostic program is used to maintain the
following:
QPC472 Digital Trunk Interface (DTI) card
QPC720 Primary Rate Interface (PRI) card
The PRI messages provide information concerning the following:
Responses to commands entered in LD 60
Database errors relevant to PRI interfaces
Protocol errors associated with a PRI link
Messages
PRI0000 loop v
No problem. Correct version ID (s) was received from PRI loop.

Action:
Severity: Info.
PRI0005 loop v
SNMP trap: Yes
Incorrect version ID (v) was received from PRI loop. The SL-1 software
release is not compatible with the PRI hardware vintage.
Action:
Severity: Critical.
PRI0006 loop
SNMP trap: Yes
Response timeout, no version ID received.

Action: 1. Be sure QPC720 is being used, not QPC472.
2. Be sure PRI hardware and software are correctly installed.
3. Check PRI status.
Severity: Critical.
PRI0007
SNMP trap: Yes
Protocol Error: Mandatory IPNWK IE data is missing in incoming ALERTing or

PROGRESSing when Network Bandwidth Management call restriction flag is
set. The call will be blocked until enough bandwidth is available for the IP call.
Output data: DCH: x DATA: y . Where: x = D-channel number and y = NONE.
Action: Contact your technical support group if the problem persists
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1400 of 2360

PRI0008
UUI IE length exceeded the maximum allowed.

Action:
Severity: Minor.
PRI0010 loop
SNMP trap: Yes
Disabling of this loop not allowed. Associated DCHI must be disabled first.
Action:
Severity: Info.
PRI0011 loop
SNMP trap: Yes
DCH port number mismatch between PDCH block and PPRI loop block.
Action: This is a software problem. Report it to the technical assistance center.
Severity: Critical.
PRI0100 loop ch
SNMP trap: Yes
The B-channel indicated in the outgoing SETUP is locked out because the
far-end is using an alternate B-channel.
Action:
Severity: Critical.
SNMP trap: Yes
PRI0101 loop ch c The B-channel (ch) is locked out because a RELCOMP or RELEASE
message has been received with one of the following cause (c) values: 82 =
channel does not exist 44 = requested channel is not available
6 = alternate channel not acceptable
Action:
Severity: Critical.
PRI0200
SNMP trap: Yes
Protocol Error: A Global CREF number is needed for any service message.
Format: DCH: x DATA: y . Where: x = D-channel number and y = Message
type
Action: Report problem if condition persists.
Severity: Critical.
PRI0201
SNMP trap: Yes
Protocol Error: Invalid maintenance state in the service message. Output data:
DCH: x DATA: y . Where: x = D-channel number and y = Message type.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1401 of 2360

PRI0202
Protocol Error: Incorrect value for extension bit. Output data: DCH: x DATA: y
z.
Severity: Critical.
PRI0203
SNMP trap: Yes
Protocol Error: Mandatory Notification description invalid. Output data: DCH:

x DATA: y z . Where: x = D-channel number, y = Message type, and z =
Information Element (IE).
Severity: Critical.
PRI0204
SNMP trap: Yes
Database Error: Feature is not allowed for this interface. Output data: DCH: x
DATA: y z . Where: x = D-channel number, y = D-channel interface ID and z =
ESL or ISA.
Action: Verify data is correct in the configuration record and the route data block.
Severity: Critical.
PRI0205
SNMP trap: Yes
Protocol Error: NSF IE is missing from the SETUP message received from the
far end. Output data: DCH: x DATA: y . Where: x = D-channel number and y =
Message type.
Action: Check the database in the far-end switch to ensure the NSF IE is
included as part of the call origination.
Severity: Critical.
PRI0206
SNMP trap: Yes
Protocol Error: The length of the incoming call reference value was incorrect.
The length allowed in North America is 1 or 2. For some other interfaces only
a length of 2 is allowed. There may be a compatibility problem with the far end.
Output data: DCH: x DATA: y . Where: x = D-channel number and y = Call
reference length.
Severity: Critical.
PRI0207
SNMP trap: Yes
Protocol Error: Wrong message type. Output data: DCH: x DATA: y . Where:
x = D-channel number and y = Message type.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1402 of 2360

PRI0208
Protocol Error: Wrong information element (IE) for message type. Output data:
DCH: x DATA: y . Where: x = D-channel number and y = Message type.
Severity: Critical.
PRI0209
SNMP trap: Yes
Protocol Error: Undefined information element (IE) for message type. Output
data: DCH: x DATA: y . Where: x = D-channel number and y = Message type.
Severity: Critical.
PRI0210
SNMP trap: Yes
Protocol Error: Wrong coding standard. Output data: DCH: x DATA: y . Where:
x = D-channel number and y = Coding standard.
Severity: Critical.
PRI0211
SNMP trap: Yes
Protocol Error: Incorrect extension bit. Output data: DCH: x DATA: y . Where:
x = D-channel number and y = Message type.
Severity: Critical.
PRI0212
SNMP trap: Yes
Protocol Error: Bearer capability (BC) - Information transfer not supported.

Output data: DCH: x DATA: y . Where: x = D-channel number and y = Transfer
capability.
Severity: Critical.
PRI0213
SNMP trap: Yes
Protocol Error: Bearer capability (BC) - Information transfer rate/mode not

supported. Output data: DCH: x DATA: y . Where: x = D-channel number and
y = Transfer rate.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1403 of 2360

PRI0214
Protocol Error: Bearer capability (BC) - Layer 1 protocol ID not correct. Output
data: DCH: x DATA: y . Where: x = D-channel number and y = Protocol ID.
Severity: Critical.
PRI0215
SNMP trap: Yes
Protocol Error: Bearer capability (BC) - Rate is not correct. Output data: DCH:
x DATA: y . Where: x = D-channel number and y = Message type.
Severity: Critical.
PRI0216
SNMP trap: Yes
Protocol Error: Bearer capability (BC) - Rate is not correct. Output data: DCH:
x DATA: y . Where: x = D-channel number and y = Rate.
Severity: Critical.
PRI0217
SNMP trap: Yes
Protocol Error: General location not supported. Output data: DCH: x DATA: y
. Where: x = D-channel number and y = General location number.
Severity: Critical.
PRI0218
SNMP trap: Yes
Protocol Error: Cause value not supported. Output data: DCH: x DATA: y .
Where: x = D-channel number and y = Cause information element (IE).
Severity: Critical.
PRI0219
SNMP trap: Yes
Protocol Error: Channel ID octet 3 error. Output data: DCH: x DATA: y . Where:
x = D-channel number and y = Octet 3.
Severity: Critical.
PRI0220
SNMP trap: Yes
Protocol Error: Channel ID octet 5 error. Output data: DCH: x DATA: y . Where
: x = D-channel number and y = Message type.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1404 of 2360

PRI0221
Protocol Error: Channel ID octet 5 error. Incorrect BCH standard. Output data:
DCH: x DATA: y . Where: x = D-channel number and y = B-channel standard
Severity: Critical.
PRI0222
SNMP trap: Yes
Protocol Error: Channel number does not exist. Output data: DCH: x DATA: y
. Where: x = D-channel number and y = B-channel number.
Severity: Critical.
PRI0223
SNMP trap: Yes
Protocol Error: CREF flag in SETUP message is incorrect. Output data: DCH:
x DATA: y . Where: x = D-channel number and y = Call reference number.
Severity: Critical.
PRI0224
SNMP trap: Yes
Protocol Error: State message error, protocol violation. The state IE is not
appropriate for the current state. Output data: DCH: x DATA: a b c d e . Where
x = D-channel number
a = Pointer to PRI message call register b = UTN c = StatePM d = Message
type
e = Call reference number
Severity: Critical.
PRI0225
SNMP trap: Yes
Protocol Error: State message error, protocol violation. Release complete

received in U11 or U31 state. Output data: DCH: x DATA: y . Where: x =
D-channel number and y = Message type.
Severity: Critical.
PRI0226
SNMP trap: Yes
Protocol Error: No RESTart ACK message received. Output data: DCH: x

DATA: y . Where: x = D-channel number and y = UTN.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1405 of 2360

PRI0227
Protocol Error: Message received in NULL state. Output data: DCH: x DATA:
y . Where: x = D-channel number and y = Message type.
Severity: Critical.
PRI0228
SNMP trap: Yes
Protocol Error: Mandatory Channel ID missing in ALERTing. Output data:

DCH: x DATA: y . Where: x = D-channel number and y = NONE.
Severity: Critical.
PRI0229
SNMP trap: Yes
Protocol Error: Mandatory Channel ID missing in incoming CONNect

message. Output data: DCH: x DATA: y . Where: x = D-channel number and
y = NONE.
Severity: Critical.
PRI0230
SNMP trap: Yes
Protocol Error: Incoming NSF contains a mismatch between the route defined
by the SID and the call type defined for that route. Output data: DCH: x DATA:
a b c . Where :
a = Facility value
b = ISA service type
c = Route number
Severity: Critical.
PRI0231
SNMP trap: Yes
Database Error: NSF error. Invalid service or feature type. Output data: DCH:
x DATA: y . Where: x = D-channel number and y = Message type.
Action: Coordinate fields with far end switch.
Severity: Critical.
PRI0232
SNMP trap: Yes
Protocol Error: PROGRESS INDICATOR not supported. Output data: DCH: x

DATA: y . Where: x = D-channel number and y = Message type.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1406 of 2360

PRI0233
Protocol Error: ZERO length for mandatory information element (IE). Output
data: DCH: x DATA: y . Where: x = D-channel number and y = Information
element (IE) identifier.
Severity: Critical.
PRI0234
SNMP trap: Yes
Protocol Error: ZERO length for optional information element (IE). Output data:
DCH: x DATA: y . Where: x = D-channel number and y = Information element
(IE) identifier.
Severity: Critical.
PRI0235
SNMP trap: Yes
Protocol Error: Bearer capability (BC) - Layer ID is not correct. Output data:
DCH: x DATA: y . Where: x = D-channel number and y = Layer ID.
Severity: Critical.
PRI0236
SNMP trap: Yes
Protocol Error: Incorrect Transit Network Selection (TNS) Network ID. Output
data: DCH: x DATA: y . Where: x = D-channel number and y = Message type.
Severity: Critical.
PRI0237
SNMP trap: Yes
Protocol Error: Message length exceeds buffer size. Output data: DCH: x
DATA: y . Where: x = D-channel number and y = Message type.
Severity: Critical.
PRI0238
SNMP trap: Yes
Protocol Error: Protocol discriminator is not compatible with the message

received. Output data: DCH: x DATA: y . Where: x = D-channel number and y
= Protocol discriminator.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1407 of 2360

PRI0239
Protocol Error: Maintenance message is not allowed for this DCH interface.
Output data: DCH: x DATA: y . Where: x = D-channel number and y =
Message type.
Severity: Critical.
PRI0240
SNMP trap: Yes
Protocol Error: No SERVice ACKnowledge message received. Output data:

DCH: x DATA: y . Where: x = D-channel number and y = UTN.
Severity: Critical.
PRI0241
SNMP trap: Yes
Protocol Error: No response from far end to this PRI call. Output data: DCH: x
DATA: y . Where: x = D-channel number and y = B-channel number.
Severity: Critical.
PRI0242
SNMP trap: Yes
Protocol Error: Received a PRI message with an unsupported service

identifier. Output data: DCH: x DATA: y . Where: x = D-channel number and y
= Service identifier.
Severity: Critical.
PRI0243
SNMP trap: Yes
Protocol Error: Service discriminator is not supported by PRI. Output data:

DCH: x DATA: y . Where: x = D-channel number and y = Service discriminator.
Severity: Critical.
PRI0244
SNMP trap: Yes
Protocol/Database Error: Facility reject message received. Output data: DCH:

x DATA: a b c d e . Where: x = D-channel number a = Originating PNI b =
Originating number c = Destination PNId = Destination number e = Reason
Action: Verify that the PNI values are correct in the customer and route data
blocks and are consistent with the switch on the other end of the link.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1408 of 2360

PRI0245
Database Error: Missing PNI number in the customer data block. Output data:
DCH: x DATA: y z . Where:
x = D-channel number y = Customer number
z = Service ID
Action: Look into the customer data block to configure the PNI.
Severity: Critical.
PRI0246
SNMP trap: Yes
Protocol Error: Received bad facility information element (IE). Output data:
DCH: x DATA: y . Where: x = D-channel number and y = Error indication.
Severity: Critical.
PRI0247
SNMP trap: Yes
Database Error: PNI missing in Route Data Block. Output data: DCH: x DATA:
y . Where: x = D-channel number and y = Service identifier.
Action: Configure the PNI in the route data block.
Severity: Critical.
PRI0248
SNMP trap: Yes
Protocol Error: ROSE component sent is being rejected. Output data: DCH: x
DATA: y . Where: x = D-channel number and y = Service identifier.
Severity: Critical.
PRI0249
SNMP trap: Yes
Protocol Error: ISDN: Received a Status message with CAUSE = 30. This is
normally received in response to a Status Enquiry but the Meridian 1 did not
send out a Status Enquiry message. The Status message is ignored. Output
data: DCH: x DATA: y . Where: x = D-channel number and y = D-channel
interface ID.
Severity: Critical.
PRI0250
SNMP trap: Yes
Protocol Error: Received information element (IE) is in the wrong

codeset.Output data: DCH: x DATA: y . Where: x = D-channel number and y
= Information element (IE) identifier.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1409 of 2360

PRI0251
Protocol Error: The Presentation Method of Protocol Profile (PMPP) is wrong

in the High Layer Compatibility IE. Output data: DCH: x DATA: y . Where: x =
D-channel number and y = High Layer Compatibility PMPP.
Severity: Critical.
PRI0252
SNMP trap: Yes
Protocol Error: The Interpretation of High Layer Characteristics ID is wrong in

the High Layer Compatibility IE. High Layer Compatibility INTERPRT
Severity: Critical.
PRI0253
SNMP trap: Yes
Protocol Error: The High Layer Characteristic ID is wrong in the High Layer
Compatibility IE.Output data: DCH: x DATA: y . Where: x = D-channel number
and y = High Layer Compatibility CHAR ID.
Severity: Critical.
PRI0254
SNMP trap: Yes
Database Error: The DCH is interfacing with a software issue not supported by
the application. Output data: DCH: x DATA: y z . Where:
x = D-channelnumber y = Release ID
z = Service identifier
Action: Verify that the release ID in the configuration record is the same as the
software release running on the far end switch.
If available, turn on the Alarm Filtering Package (#243) or Upgrade all the ISDN
MCDN switches to the same software Release.
Severity: Critical.
PRI0255
SNMP trap: Yes
Protocol Error: Information request type is not supported. A message error or

a protocol error will be generated depending on whether the I.E. is mandatory
or not. Output data: DCH: x DATA: y z . Where: x = D-channel number, y =
Message type, and z = Information element (IE) identifier.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1410 of 2360

PRI0256
Protocol Error: Wrong length for information request I.E. The length on the
received I.E. is beyond the range. A message error or a protocol error will be
generated depending on whether the I.E. is mandatory or not.
Output data: DCH: x DATA: y z . Where: x = D-channel number, y = Message
type, and z = Information element (IE) identifier.
Severity: Critical.
PRI0257
SNMP trap: Yes
Protocol Error: Information request specific is not supported. A message error

or a protocol error will be generated depending on whether the I.E. is
mandatory or not.
Action:
Severity: Info.
PRI0258
SNMP trap: Yes
Protocol/Database Error: An attempt is being made to insert more that 8 digits

in the calling party number for a call originating or tandeming through this
switch. Only eight (8) digits can be included in the calling party number, or the
digits are truncated to the right (AXE-10 Australia interface only). Output data:
DCH: x DATA: TANDEM or ORIG . Where: x = D-channel number.
Action: For originating calls, modify LD 15 PFX1 and PFX2 so that
PFX1+PFX2+DN is less than 8 digits. For tandeming calls, notify far end of
incoming trunk that more than 8 digits are being sent.
Severity: Critical.
PRI0259
SNMP trap: Yes
Protocol Error: Mandatory Channel ID missing in CALL PROC message.

Output data: DCH: x DATA: y . Where: x = D-channel number and y = NONE.
Severity: Critical.
PRI0261
553-3001-411
SNMP trap: Yes
Database Error: The D-channel interface for routing Network Message

Service (NMS) facility messages is not an Meridian 1 interface. Output data:
DCH: x DATA: a b c d . Where:
a = Operation code for TCAP protocol
Standard 15.00
January 2006
Page 1411 of 2360

b = Originating digits
c = Terminating digits
d = Customer number
Action: Verify database configuration.
Severity: Critical.
PRI0262
SNMP trap: Yes
Protocol Error: Invalid value for the interface identifier field of channel ID
information element from an incoming message. Output data: DCH: x DATA:
y . Where: x = D-channel number and y = Message type.
Severity: Critical.
PRI0263
SNMP trap: Yes
Protocol Error: Invalid value for the class field of restart indicator information
element from an incoming message. Output data: DCH: x DATA : y. Where: x
= D-channel number and y = Message type.
Severity: Critical.
PRI0264
SNMP trap: Yes
Protocol Error: Received an invalid call reference from far-end switch. Output
data: DCH: x DATA: y. Where: x = D-channel number and y = Message type.
Severity: Critical.
PRI0265
SNMP trap: Yes
Database Error: A Facility Reject message was received. Destination digits

cannot be translated. Output data: DCH: x DATA: a b c d e.
Where: x = D-channel number
a = TCAP package type
b = Problem (NOXLAN/NONMS)
c = Originating digits d = Destination digits e = Customer number
Action: Verify numbering plan databases are consistent between the near and
far end switches.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1412 of 2360

PRI0266

Center (NMC) feature. Output data: DCH: x DATA: a b c d e f.
Where: x = D-channel number a = TCAP package type
b = TCAP component type
c = Problem
Action:
Severity: Info.
PRI0267
SNMP trap: Yes

Center (NMC) feature. Output data: DCH: x DATA: a b c d .
Where:
b = Originating digits
c = Destination digits
d = Customer number
Severity: Critical.
PRI0268
SNMP trap: Yes
Protocol Error: TCAP Component is not recognized by Network Message

Center (NMC) feature. Output data: DCH: x DATA: a b c d e .
Where:
c = Originating digits
d = Destination digits
e = Customer number
Severity: Critical.
PRI0269
553-3001-411
SNMP trap: Yes
Protocol Error: TCAP Operation is not recognized by Network Message

Center (NMC) feature. Output data: DCH: x DATA: a b c d e f.
Where:
c = Operation
Standard 15.00
January 2006
Page 1413 of 2360

d = Originating digits
e = Destination digits
f = Customer number
Severity: Critical.
PRI0270
SNMP trap: Yes
Protocol Error: TCAP parameter is not recognized by Network Message

Center (NMC) feature. Output data: DCH: x DATA: a b c d e f g.
Where:
c = Operation
d = Parameter
e = Originating digits
f = Destination digits
g = Customer number
Severity: Critical.
PRI0271
SNMP trap: Yes
Database Error: LDN0 must be defined for the customer for ISDN DID calls in
order to determine the number of digits expected for successful call
termination. Output data: DCH: x DATA: y . Where: x = D-channel number and
y = Customer number.
Action: Configure LDN0 in the customer data block.
Severity: Critical.
PRI0272
SNMP trap: Yes
Message is ping-pong between 2 nodes.

Action:
Severity: Critical.
PRI0274
SNMP trap: Yes
Network Message Service, TCAP Return Error message.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1414 of 2360

PRI0275
Network Message Service, TCAP Reject error message.

Action:
Severity: Critical.
PRI0276
SNMP trap: Yes
Network Message Service, DN in ORIG IE invalid.

Action:
Severity: Critical.
PRI0277
SNMP trap: Yes
Invalid call state (Layer 3 protocol error).

Action:
Severity: Critical.
PRI0278 x
SNMP trap: Yes
Unable to enable DCH x because the IPRA package is restricted, and is a

prerequisite for this interface.
Action:
Severity: Critical.
PRI0279
SNMP trap: Yes
Enabling channels on a secondary loop (nB plus D, where the loop is entered
for the PRI2 prompt in LD 17) is blocked if the INBD package is restricted.
Action:
Severity: Critical.
PRI0280
SNMP trap: Yes
Enabling a Backup DCH is not allowed. Not supported by IFC.

Action:
Severity: Critical.
PRI0281
SNMP trap: Yes
Display IE length exceeds 32 digits.

Action:
Severity: Critical.
PRI0282
SNMP trap: Yes
Facility ID received is not supported.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1415 of 2360

PRI0283
Facility ID received is invalid.

Action:
Severity: Critical.
PRI0284
SNMP trap: Yes
Control Code received is not supported.

Action:
Severity: Critical.
PRI0285
SNMP trap: Yes
Control Code received is invalid.

Action:
Severity: Critical.
PRI0286
SNMP trap: Yes
AOC Information contains non-numerical (0-9) characters.

Action:
Severity: Critical.
PRI0287
SNMP trap: Yes
AOC Charge Count field contains more than 8 digits.

Action:
Severity: Critical.
PRI0288
SNMP trap: Yes
AOC Info field had no characters contained within it.

Action:
Severity: Critical.
PRI0289
SNMP trap: Yes
AOC Info field contains leading zero.

Action:
Severity: Critical.
PRI0290
SNMP trap: Yes
AOC Charge per Charge Count field contains more than 2 digits.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1416 of 2360

PRI0291
AOC Request contained invalid Control Code.

Action:
Severity: Critical.
PRI0292
SNMP trap: Yes
AOC Requested but customer not Subscribed to service.

Action:
Severity: Critical.
PRI0293
SNMP trap: Yes
Missing '#' in Facility Info String.

Action:
Severity: Critical.
PRI0294
SNMP trap: Yes
Display IE contains non-ASCII characters.

Action:
Severity: Critical.
PRI0295
SNMP trap: Yes
Expected more characters in Display IE.

Action:
Severity: Critical.
PRI0296
SNMP trap: Yes
Diagnostic missing from Cause IE when Cause equals Facility Rejected.

Action:
Severity: Critical.
PRI0297
SNMP trap: Yes
Diagnostic field of Cause IE contains invalid characters.

Action:
Severity: Critical.
PRI0298
SNMP trap: Yes
Advice of Charge at end of call has been requested, but the request was
rejected by the Central Office.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1417 of 2360

PRI0299
A facility has been requested that is not supported by the Central Office.
Action:
Severity: Critical.
PRI0300
SNMP trap: Yes
Only AOC Total Charge is supported.

Action:
Severity: Critical.
PRI0301
SNMP trap: Yes
AOC IE contains unsupported characters

Action:
Severity: Critical.
PRI0302
SNMP trap: Yes
AOC IE contains a decimal point in the wrong position.

Action:
Severity: Critical.
PRI0303
SNMP trap: Yes
Advice of Charge IE length exceeds 12 digits (Japan D70).

Action:
Severity: Critical.
PRI0304
SNMP trap: Yes
The MCT FACILITY identifier is not recognized by the AXE10 CO.

Action:
Severity: Critical.
PRI0305
SNMP trap: Yes
The MCT control code is not recognized by the AXE10 CO.

Action:
Severity: Critical.
PRI0306
SNMP trap: Yes
The user is not subscribed for the MCT request at the CO.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1418 of 2360

PRI0307
CLID length exceeds maximum allowed for the Australian interface.

Action: Configure billing number to maximum allowed.
Severity: Critical.
PRI0308
SNMP trap: Yes
Unsolicited Return Result / Return Reject for TOA was received from far-end
switch.
Action: Monitor the incoming Facility IE sent by the far-end switch and report to
Administration
Severity: Critical.
PRI0309
SNMP trap: No
CALL ID in Invoke for third party interaction has already been sent.
Action: Monitor the outgoing Facility IE and report to Administration
Severity: Critical.
PRI0310
SNMP trap: Yes
Far-end does not recognize Calling Party # . Output data: DCH: x DATA: y.
Where: x = D-channel number and y = Information Element (IE).
Action: Check PRFX,LDN in CDB
Severity: Critical.
PRI0311
SNMP trap: Yes
CALL ID in Return Result has already been received

Administration
Severity: Critical.
PRI0312
SNMP trap: Yes
INVOKE for TOA received from far-end switch has incorrect format.
Administration.
Severity: Info.
PRI0350
SNMP trap: Yes
Trunk requested for a restart is not PRI B channel.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1419 of 2360

PRI0351
The maintenance message decoder found an IE which it does not recognize.

Action:
Severity: Info.
PRI0352
SNMP trap: Yes
An invalid call state is passed for call clearing case.

Action:
Severity: Minor.
PRI0353
SNMP trap: Yes
Unable to get a maintenance call register.

Action:
Severity: Info.
PRI0355
SNMP trap: Yes
Invalid primitive received from Layer 2.

Action:
Severity: Info.
PRI0356
SNMP trap: Yes
Invalid primitive received during MSDL ring test.

Action:
Severity: Info.
PRI0357
SNMP trap: Yes
Invalid primitive received during MSDL expd. Test.

Action:
Severity: Info.
PRI0358
SNMP trap: Yes
Output request buffer overflow.

Action: Check the OTBF configuration in LD17 and the MSDL
Severity: Major.
PRI0359
SNMP trap: Yes
Resynch of DCH socket id failed.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1420 of 2360

PRI0360
Request to obtain an expediated buffer failed.

Action:
Severity: Info.
PRI0361
SNMP trap: Yes
PRI DCH link is not established when layer 3 requested message is output.
Action:
Severity: Info.
PRI0362
SNMP trap: Yes
Invalid timeout event detected.

Action:
Severity: Critical.
PRI0363
SNMP trap: Yes
Invalid service message progress mark found.

Action:
Severity: Critical.
PRI0364
SNMP trap: Yes
The message type received by the backup D-channel handler is not

recognized.
Action:
Severity: Critical.
PRI0365
SNMP trap: Yes
The backup D-channel maintenance state is invalid to process the service

message.
Action:
Severity: Critical.
PRI0366
SNMP trap: Yes
The backup D-channel maintenance state is invalid to process the received

service acknowledge message.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1421 of 2360

PRI0367
The D-channel link has to be established in order to send out service or service
acknowledge message.
Action:
Severity: Critical.
PRI0368
SNMP trap: Yes
The D-channel link has to be established and in service in order for a call
processing message to be sent out.
Action:
Severity: Critical.
PRI0369
SNMP trap: Yes
A layer 3 message has been received on a D-channel which is not in service.

Action:
Severity: Critical.
PRI0370
SNMP trap: Yes
An invalid loop number is given for PRI interface restart.

Action:
Severity: Critical.
PRI0371
SNMP trap: Yes
Audit - The primary D-channel (D1) state should be disabled.

Action:
Severity: Critical.
PRI0372
SNMP trap: Yes
Audit - The backup D-channel (D2) state should be disabled.

Action:
Severity: Critical.
PRI0373
SNMP trap: Yes
Audit - The D-channel should not be in service.

Action:
Severity: Critical.
PRI0374
SNMP trap: Yes
Audit - The D-channel should not be in standby state.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1422 of 2360

PRI0375
Audit - Invalid state detected for backup DCH, as the D-channel is enabled the state is changed to out-of-service(OOS).
Action:
Severity: Critical.
PRI0376
SNMP trap: Yes
Audit - the D-channel is in the Wait state but the link is not established.
Action:
Severity: Critical.
PRI0377
SNMP trap: Yes
Audit - The D-channel is in the Wait state but no timer is running.

Action:
Severity: Critical.
PRI0381
SNMP trap: Yes
Database Error: TCAP Is unable to route the message using the digits in
DIGIT_WORD of the call register.
Output data: DCH: x DATA: y z z1
Where: x = D-channel number, y= DIGIT_WORDS
Action:
Severity: Info.
PRI0382
SNMP trap: Yes
The UIPE layer 3 loadware INIT Rebuild Timer has expired. The BRIE INIT
rebuild process has been aborted. Transient call will not be rebuilt. Output
data: DCH: x DATA: y. Where: x= D-channel number and y= message type.
Severity: Major.
PRI4501
SNMP trap: Yes
"Invalid Service identifier". This service identifier which defines a

supplementary service is currently either "INVALID" or is not supported by M1.
Action:
Severity: Info.
PRI5029
SNMP trap: No
Reverse charging is not allowed.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1423 of 2360

PRI5030 {PRI2 TN} {phantom DTI2 TN} A PRI2 trunk used by the ISPC feature has been found
in an invalid state. The call active on the ISPC phantom DTI2 trunk (which is
linked with the PRI2 trunk) is cleared. The phantom DTI2 trunk is put in
disabled state. The ISPC call active on the PRI2 trunk is cleared.
Severity: Major.
SNMP trap: No
PRI5032 DH: n DATA: id DCHI does not have expanded firmware so cannot support this service
ID; or if the pack installed has the expanded firmware, the pack needs to be
reseated.
Action: Disable all ports on the card, then remove and reseat the card.
Re-enable the ports. The error message should not recur.
Severity: Minor.
PRI5033
SNMP trap: Yes
An application has requested to send on a QSIG a non-call related message

received on MCDN but the QSIG RCAP is not configured on the outgoing link
or the service is not supported on QSIG. The message is rejected.
Output: DCH or DSL number, PRI/BRIT type, Service identifier. The following
service identifiers are defined:
1. Network ring again
2. Network ACD
3. Network Attendant Service
4. Network Message Center
5. Trunk Route Optimization
6. Network Call Trace
7. Remote Virtual Queuing
8. VNS service
9. Network Remote Call Forward
10. Network Radio Paging
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1424 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1425 of 2360
PWR: Power and System Monitor

PWR messages are received from the System Monitor. They indicate power
and temperature status or failures. The output format for all PWR messages is:
PWRxxxx HW SM UEM U
Where:
HW = hardware type, possible values are:
CRBK = Circuit Breaker
DCSP = DC power supply
FANU = Fan unit
PFTC = Power Fail Transfer Card
PWSP = Power Supply including the ringing generator
THSW = Thermal Switch
UPSA = Uninterruptible Power Supply Alarm
XSMC = System Monitor Card
SM = System Monitor (0-63), 0 = the master System Monitor
UEM = Universal Equipment Module, possible values are:
0 = bottom UEM or not applicable
1 = second UEM
2 = third UEM
3 = top UEM
U = power unit number, possible values are:
0 = not applicable
1 = power unit 1
2 = power unit 2
Messages
PWR0000 hw
System Monitor or power supply is OK. Output may be:PWR0000 XSMC

System Monitor is OK PWR0000 PWSP Power unit is OK
Action:
Severity: Minor.
PWR0001
SNMP trap: Yes
Partial failure on power supply.

Action: Replace the indicated power supply.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1426 of 2360

PWR0002
Complete failure on power supply.

Action: Replace the indicated power supply.
Severity: Critical.
PWR0003
SNMP trap: Yes
Power supply not installed or has been removed.

Action:
Severity: Critical.
PWR0004
SNMP trap: Yes
Circuit breaker has tripped. System has overheated.

Action: Check the blower unit, air filter, air ventilation and room air conditioning.
Severity: Critical.
PWR0005
SNMP trap: Yes
One or more fans has failed in the Blower unit. Some DC powered blower
units, NT8D52DD, will display PWR0005 followed by PWR0006 and
PWR0045, indicating loss of power in the blower module
Action: Replace the unit. This message occurs when the NT7D17AC or
NT7D17DC fan shelf in Option 21 systems is turned on. This is not an error
condition if PWR0005 is followed by PWR0046 (sensor alarm cleared) and
PWR0045 (fan functioning).
Severity: Critical.
PWR0006
SNMP trap: Yes
Blower air probe temperature sensor alarm. This indicates one of the
following: 1. Blower air probe temperature sensor has reached 2. 55 degrees
C (131 degrees F). 3. Blower unit has lost power. 4. Blower unit air probe
temperature sensor is faulty or disconnected.
Severity: Critical.
PWR0007
SNMP trap: Yes
Column temperature has reached 70 degrees C (158 degrees F). If the blower
has reached 55 degrees C (PWR0006 message) then the circuit breaker will
trip in 30 seconds.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1427 of 2360

PWR0010 hw
For PWR010 UPSA: Uninterruptible Power Supply (UPS) alarm condition 1.

The meaning depends on the UPS manufacture Best Inc. UPS inverter is
ON Lorain UPS inverter is ON Exide UPS AC power failed Alpha UPS
inverter is ON For PWR010 DCSP: DC trip alarm is ON (circuit breaker has
tripped).
Action:
Severity: Critical.
PWR0012 hw
SNMP trap: Yes
For PWR012 UPSA: Uninterruptible Power Supply (UPS) Summary alarm

(condition 2). The meaning depends on the UPS manufacturer. Best Inc. UPS
Summary alarm is ON Lorain UPS bypass is ON Exide UPS bypass is
ON Alpha UPS low battery For PWR012 DCSP: DC alarm is ON.
Action:
Severity: Critical.
PWR0013
SNMP trap: Yes
Slave System Monitor is not responding.

Action: Check the serial link cable or replace the System Monitor.
Severity: Critical.
PWR0014
SNMP trap: Yes
System Monitor failed self test.

Action: Replace the System Monitor.
Severity: Critical.
PWR0015
SNMP trap: Yes
SL-1 NT, RT, ST or XT cabinet has an alarm condition.

Action:
Severity: Critical.
PWR0016
SNMP trap: Yes
Power fail transfer has been activated.

Action:
Severity: Critical.
PWR0017
SNMP trap: Yes
DCON 0 alarm is ON.

Action: Check DC power supply.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1428 of 2360

PWR0018
DCON 1 alarm is ON.

Severity: Critical.
PWR0019
SNMP trap: Yes
DCON 2 alarm is ON.

Severity: Critical.
PWR0020
SNMP trap: Yes
DCON 3 alarm is ON.

Severity: Critical.
PWR0044
SNMP trap: Yes
Circuit breaker had been reset.

Action:
Severity: Critical.
PWR0045
SNMP trap: Yes
Fans have returned to normal speed.

Action:
Severity: Minor.
PWR0046
SNMP trap: Yes
Blower unit air probe temperature sensor is now less than 55 degrees C (131
degrees F).
Action:
Severity: Minor.
PWR0047
SNMP trap: Yes
Column temperature now less than 70 degrees C (158 degrees F). Circuit
breaker trip signal is released.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1429 of 2360

PWR0050 hw
For PWR050 UPSA: Uninterruptible Power Supply (UPS) alarm condition 1

has been cleared. For PWR050 DCSP: DC trip alarm is OFF (circuit breaker
has been reset).
Action:
Severity: Minor.
PWR0052 hw
SNMP trap: Yes
For PWR052 UPSA: Uninterruptible Power Supply (UPS) alarm condition 2

has been cleared. For PWR050 DCSP: DC alarm is OFF.
Action:
Severity: Minor.
PWR0053
SNMP trap: Yes
Slave System Monitor is now responding.

Action:
Severity: Minor.
PWR0054
SNMP trap: Yes
System Monitor passed self test.

Action:
Severity: Minor.
PWR0055
SNMP trap: Yes
SL-1 NT, RT, ST or XT cabinet alarm condition has been cleared.

Action:
Severity: Minor.
PWR0056
SNMP trap: Yes
Power fail transfer deactivated.

Action:
Severity: Minor.
PWR0057
SNMP trap: Yes
DCON 0 alarm has been cleared.

Action:
Severity: Minor.
PWR0058
SNMP trap: Yes

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1430 of 2360

PWR0059

Action:
Severity: Minor.
PWR0060
SNMP trap: Yes

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1431 of 2360
QoS: Quality of Service

PVQ Monitoring assists administrators to monitor the performance of their
Succession system and to make informed decisions for capacity planning and
Quality of Service (QoS) network engineering. PVQ Monitoring also assists
crafts persons to diagnose, isolate, and correct networking problems that
cause deterioration in voice quality.
Messages
QOS0001
QoS packet loss: [packet loss value that exceeds warning threshold],
[sourceIP:source port], [source TN], [source zone], [destination IP:destination
port], [destination TN], [destination zone]. where:
packet loss value = percentage of packets not received
source TN = originating sets TN in l s c u format (large system) or c u format
(small system)
destination TN = terminating sets TN in l s c u format (large system) or c u
format (small system)
Note: This alarm is reported on the Call Server.
Action: IP Voice Quality degradation has been detected. Check your IP network
or contact your technical support group.
Severity: Info.
QOS0002
SNMP trap: Yes
QoS latency: [latency value that exceeds warning threshold], [sourceIP:source

port], [source TN], [source zone], [destination IP:destination port], [destination
TN], [destination zone].where:
latency = the (round trip delay)/2 in milliseconds
(small system)
Severity: Info.
QOS0003
SNMP trap: Yes
QoS jitter: [jitter value that exceeds warning threshold], [sourceIP:source port],
[source TN], [source zone], [destination IP:destination port], [destination TN],
[destination zone]. where:
jitter = jitter in milliseconds
System Messages
Page 1432 of 2360

(small system)
Action: detected. Check your IP network or contact your technical support
group.
Severity: Info.
QOS0004
SNMP trap: Yes
IP Voice Quality degradation has been detected.

QoS report gathering temporarily disabled [End Point: source IP + port
number/Server: IP Address/All].
Action: Check your IP network or contact your technical support group.
Severity: Critical.
QOS0005
SNMP trap: Yes
QoS R factor: [R value that exceeds warning threshold], [sourceIP:source

TN], [destination zone]. where:
source TN = originating set's TN in l s c u format (large system) or c u format
(small system)
Severity: Info.
QOS0007
SNMP trap: Yes
QoS packet loss: [packet loss value that exceeds unacceptable threshold],
(small system)
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1433 of 2360

QOS0008
QoS latency: [latency value that exceeds unacceptable threshold],

(small system)
Severity: Minor.
QOS0009
SNMP trap: Yes
QoS jitter: [jitter value that exceeds unacceptable threshold], [sourceIP:source

TN], [destination zone]. where:
(small system)
Severity: Minor.
QOS0010
SNMP trap: Yes
QoS R factor: [R value that exceeds unacceptable threshold],

(small system)
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1434 of 2360

QOS0012
QoS warning latency [latency value that exceeds warning threshold] in zone:
[zone]. where:
Severity: Minor.
QOS0013
SNMP trap: Yes
QoS warning jitter [jitter value that exceeds warning threshold] in zone: [zone].
where:
Severity: Minor.
QOS0014
SNMP trap: Yes
QoS warning packet loss [packet loss value that exceeds warning threshold]
in zone: [zone]. where:
Severity: Minor.
QOS0015
SNMP trap: Yes
QoS warning R factor [R value that exceeds warning threshold] in zone:

[zone].
Severity: Minor.
QOS0017
SNMP trap: Yes
QoS unacceptable latency [latency value that exceeds unacceptable

threshold] in zone: [zone]. where:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1435 of 2360

QOS0018
QoS unacceptable jitter [jitter value that exceeds unacceptable threshold] in

zone: [zone]. where:
Severity: Critical.
QOS0019
SNMP trap: Yes
QoS unacceptable packet loss [packet loss value that exceeds unacceptable
threshold] in zone: [zone]. where:
Severity: Critical.
QOS0020
SNMP trap: Yes
QoS unacceptable R factor [R value that exceeds unacceptable threshold] in

zone: [zone].
Note: This alarm is not currently reported, but is planned to be issued from the
Call Server in future. At this time only a single R value threshold is supported,
and QOS0015, R value zone warning, is issued.
Severity: Critical.
QOS0022
SNMP trap: Yes
Voice packet loss Warning threshold exceeded: [packet loss value], [rx/tx],
[near end TN], [near end IP:near end port], [far end IP:far end port], [tcid].
where:
near end TN = the reporting sets packed TN, or channel + port number
near end IP = the originating set IP address or channel
far end IP = the terminating set IP address or channel
tcid = the channel ID (if a DSP is reporting)
Note: This alarm is reported on the Signaling Server or VGMC.
Severity: Warning.
SNMP trap: Yes
System Messages
Page 1436 of 2360

QOS0023
Clear Voice packet loss warning threshold exceeded: [packet loss value],
[rx/tx], [near end TN], [near end IP:near end port], [far end IP:far end port],
[tcid] where:
Severity: Cleared.
QOS0024
SNMP trap: Yes
Latency Warning threshold exceeded: [latency], [near end TN], [near end
IP:near end port], [far end IP:far end port], [tcid] where:
Severity: Warning.
QOS0025
SNMP trap: Yes
Clear Latency warning threshold exceeded: [latency], [near end TN], [near end
IP:near end port],[far end IP:far end port], [tcid] where:
Action: IP Voice Quality degradation has been detected. Check your network
configuration to ensure proper operation.
Severity: Cleared.
QOS0026
553-3001-411
SNMP trap: Yes
Jitter Warning threshold exceeded: [jitter], [near end TN], [near end IP:near
end port], [far end IP:far end port], [tcid] where:
Standard 15.00
January 2006
Page 1437 of 2360

near TN = the reporting sets packed TN, or channel + port number
Severity: Warning.
QOS0027
SNMP trap: Yes
Clear Jitter warning threshold exceeded: [jitter], [near end TN], [near end
near end TN = the reporting sets packed TN ,or channel + port number
Severity: Cleared.
QOS0028
SNMP trap: Yes
R Factor warning threshold exceeded: [listening R value],near end TN [near

end TN],near end IP [near end IP:near end port],far end IP [far end IP:far end
port],tcid [tcid],cT [cT],nLR [nLR],dR [dR],bD [bD],bL [bL],gD [gD],gL [gL],eSD
[eSD],aNL [aNL],aSP [aSP], rTT [rTT]
where:
near end TN = the reporting set packed TN, or channel + port number
tcid = the channel ID (if a DSP is reporting, otherwise -1)
*cT = Codec Type, Vocoder type used on this call
*nLR = Network Loss Rate, rate of network packet loss (percentage, scaled by
256, e.g., 354 = 1.4%)
*dR = average Discard Rate, average rate of discards due to jitter (percentage,
scaled by 256)
*bD = Burst Loss Density, the percentage of packets lost or discarded during
burst periods (percentage, scaled by 256)
*bL = Burst Length, average length of bursts (milliseconds)
*gD = Gap Loss Density, the percentage of loss and discarded packets during
gap periods (percentage, scaled by 256)
System Messages
Page 1438 of 2360

*gL = average length of gaps (milliseconds)
*eSD = average End System Delay on call (milliseconds)
*aNL = Noise Level, measured received silent period noise level (dBm)
*aSP = Average Signal Level, measured received signal level during
talkspurts (dBm)
*rTT = average Local Round Trip Time on call (units of 1/65536 of a second)
* These fields will be set to zeroes if the information is not available
Note: this alarm is reported on the Signaling Server or VGMC.
Action: Call quality degradation occurred. Analyze network loss rate and discard
rate to determine if packets are being dropped from the network or due to jitter.
Packet loss is reflected in burst and gap metrics. A burst is defined as a period
where a high proportion of packets are lost or discarded in a consecutive manner
and a gap is defined as a period where a small proportion of packets are lost or
discarded in a consecutive manner. The burst length metric provides an
indication as to how long, in milliseconds, these intermittent periods of no audio
are occurring. Gap periods are the inverse of burst periods. The end system delay
represents additional delay due to the codec being used and the length of the jitter
buffer. Also, codec selection will impact call quality; the higher the compression,
the lower the maximum quality that can be achieved.
Severity: Warning.
QOS0029
SNMP trap: Yes
Clear R factor warning threshold exceeded: [listening R value], [near end TN],
[near end IP:near end port], [far end IP:far end port], [tcid] where:
Severity: Cleared.
QOS0030
553-3001-411
SNMP trap: Yes
Packet loss Unacceptable threshold exceeded: [packet loss value], [rx/tx],

[near end TN], [near end IP:near end port], [far end IP:far end port], [tcid]
where:
Standard 15.00
January 2006
Page 1439 of 2360

Severity: Minor.
QOS0031
SNMP trap: Yes
Clear Packet loss unacceptable threshold exceeded: [packet loss value],

[rx/tx], [near end TN], [near end IP:near end port], [far end IP:far end port],
[tcid] where:
Severity: Cleared.
QOS0032
SNMP trap: Yes
Latency Unacceptable threshold exceeded: [latency value], [near end TN],

[near end IP:near end port],[far end IP:far end port], [tcid] where:
latency value = (round trip delay)/2 in milliseconds
Severity: Minor.
QOS0033
SNMP trap: Yes
Clear Latency unacceptable threshold exceeded: [latency value], [near end

TN], [near end IP:near end port], [far end IP:far end port], [tcid] where:
latency value = (round trip delay)/2 in milliseconds
System Messages
Page 1440 of 2360

Severity: Cleared.
QOS0034
SNMP trap: Yes
Jitter Unacceptable threshold exceeded: [jitter value], [near end TN], [near end
jitter value = jitter in milliseconds
Severity: Minor.
QOS0035
SNMP trap: Yes
Clear Jitter unacceptable threshold exceeded: [jitter value], [near end TN],
[near end IP:near end port], [far end IP:far end port], [tcid] where:
jitter value = jitter in milliseconds
near end TN = the reporting sets packed TN or channel + port number
Severity: Warning.
QOS0036
SNMP trap: Yes
R Factor unacceptable threshold exceeded: [listening R value],near end TN

[near end TN],near end IP [near end IP:near end port],far end IP [far end IP:far
end port],tcid [tcid],cT [cT],nLR [nLR],dR [dR],bD [bD],bL [bL],gD [gD],gL
[gL],eSD [eSD],aNL [aNL],aSP [aSP], rTT [rTT]
where:
near end TN = the reporting set packed TN, or channel + port number
553-3001-411
Standard 15.00
January 2006
Page 1441 of 2360

tcid = the channel ID (if a DSP is reporting, otherwise -1)
*cT = Codec Type, Vocoder type used on this call
*nLR = Network Loss Rate, rate of network packet loss (percentage, scaled by
256, e.g., 354 = 1.4%)
*dR = average Discard Rate, average rate of discards due to jitter (percentage,
scaled by 256)
*bD = Burst Loss Density, the percentage of packets lost or discarded during
burst periods (percentage, scaled by 256)
*bL = Burst Length, average length of bursts (milliseconds)
*gD = Gap Loss Density, the percentage of loss and discarded packets during
gap periods (percentage, scaled by 256)
*gL = average length of gaps (milliseconds)
*eSD = average End System Delay on call (milliseconds)
*aNL = Noise Level, measured received silent period noise level (dBm)
*aSP = Average Signal Level, measured received signal level during
talkspurts (dBm)
*rTT = average Local Round Trip Time on call (units of 1/65536 of a second)
* These fields will be set to zeroes if the information is not available
Note: this alarm is not currently reported, but is planned to be supported in
future on the Signaling Server or VGMC. Only one level of R value threshold
is supported, reported as QOS0028, R value warning threshold violation.
Action: Call quality degradation occurred. Analyze network loss rate and discard
rate to determine if packets are being dropped from the network or due to jitter.
Packet loss is reflected in burst and gap metrics. A burst is defined as a period
where a high proportion of packets are lost or discarded in a consecutive manner
and a gap is defined as a period where a small proportion of packets are lost or
discarded in a consecutive manner. The burst length metric provides an
indication as to how long, in milliseconds, these intermittent periods of no audio
are occurring. Gap periods are the inverse of burst periods. The end system delay
represents additional delay due to the codec being used and the length of the jitter
buffer. Also, codec selection will impact call quality; the higher the compression,
the lower the maximum quality that can be achieved.
Severity: Minor.
QOS0037
SNMP trap: Yes
Clear R factor Unacceptable threshold exceeded: [listening value], [near end

TN], [near end IP:near end port], [far end IP:far end port], [tcid] where:
System Messages
Page 1442 of 2360

Severity: Cleared.
QOS0038
SNMP trap: Yes
Insuficient Bandwidth detected between <zone 1> and <zone 2>

Action:
Severity:
QOS0039
SNMP trap: Yes
Alternate Route has been chosen due to insufficient bandwidth or due to

configuration.
Action:
Severity:
QOS0040
SNMP trap: Yes
QoS Warning QoS factor between near end VPNI/ZONE:[] and far end
VPNI/ZONE:[]. QoS factor []%%. Sliding Maximum []kbps.
Action:
Severity: Minor.
QOS0041
SNMP trap: Yes
QoS Critical QoS factor between near end VPNI/ZONE:[] and far end
VPNI/ZONE:[]. QoS factor []%%. Sliding Maximum []kbps.
Action: Check the QoS of the network between these two zones
Severity: Critical.
QOS0042
SNMP trap: Yes
Sliding Maximum has now returned to configured value of [%d]kbps between

near end VPNI/ZONE:[] and far end VPNI/ZONE:[].
Action:
Severity: Info.
QOS0043
SNMP trap: Yes
Sliding Maximum is now at zero between near VPNI/ZONE:[] and far

VPNI/ZONE:[].
Action: Check the QoS of the network between these two zones
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1443 of 2360
RCV: Recovery Messages

The system has the capability to avert system initializations with code 000C
through an auto-recovery mechanism. When an error condition is detected
that can lead to an INI000C, the auto-recovery mechanism will analyze the
problem to determine whether it could be resolved locally without triggering a
system initialization.
If the error condition can be resolved, a Recovery Messages (RCV) will be
printed on the maintenance TTY, indicating the nature of the problem and the
fact that an INI000C has been averted.
If the error condition cannot be resolved, an INI000C will be invoked in the
current operation. If multiple RCV messages are received, the system will
trigger an initialization to ensure system integrity. However, the initialization
will be deferred until after the midnight routines to avoid impact to call
processing. The INI001C message will appear to identify the deferred
initializations.
If RCV messages have occurred multiple times within a 24-hour period, report
the error conditions to your support engineer.
Prior to Release 19.30, the INI000C codes also cover scenarios other than
those identified in RCV messages. The INI001D code is produced to identify
scenarios in which the auto-recovery mechanism cannot be applied.
Messages
RCV0000
An invalid queue block type was found.

Action: Report the problem to your support engineer for further analysis.
Severity: Major.
RCV0001
SNMP trap: No
Invalid queue information was found. The auto-recovery mechanism has

taken care of the problem.
Action: If the problem persists report it to the operating company.
Severity: Major.
RCV0002
SNMP trap: No
A broken queue problem was detected.

Severity: Major.
SNMP trap: No
System Messages
Page 1444 of 2360

RCV0003
Invalid information was found in the queue header block. The auto-recoverey
mechanism has taken care of the problem.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1445 of 2360
RLC: Reach Line Card

The Reach Line Card (RLC) error messages provide notification at the PBX of
alarms being generated by the Reach Line Card, 9110, 9115, or 9150. This
enables alarms to be monitored at the PBX level, rather than at the Display
Log level at the Remote Office.
Messages
RLC0005
The QoS of the IP network degraded for [Remote Office unit ID] and the
system transitioned to the PSTN.
Action: Investigate why the IP network was determined to be below VoIP quality.
Review the Engineering Guidelines.
Severity: Info.
RLC0006
SNMP trap: No
The QoS of the IP network recovered for [Remote Office unit ID] and the
system transitioned to the IP network.
Action: Investigate why the IP network had previously been determined to be
below VoIP quality. Review the Engineering Guidelines.
Severity: Info.
RLC0011
SNMP trap: No
Failed to read database from flash: [Reason]. Flash may be corrupted. System
has started with default configuration.
Action: 1. Reconfigure the system and then save it to flash. The system
suspends new call processing for approximately 30 seconds while saving
configuration changes to flash.
2. Restart the system, log in, and check the configured parameters.
3. If the problem persists, contact your vendor.
Severity: Critical.
RLC0022
SNMP trap: Yes
Link to Remote Site [Remote Office unit ID] is down.

Action: 1. Check the connectivity and configuration of the transport medium (IP
or PSTN).
2. If the medium is PSTN, check BRI status on the PBX.
3. If transport medium connectivity is OK but the problem continues, reboot the
RLC and the remote unit.
4. If the problem persists, contact your vendor
Severity: Major.
SNMP trap: Yes
System Messages
Page 1446 of 2360

RLC0029
DSP resource allocation failed on port [port #].

Action: 1. All the DSP channels on the system are in use. Wait for calls to be
dropped.
2. To avoid blocking, either distribute calls onto additional RLCs and 9150s, or
add DSP application modules to existing equipment, provided there is space
available for additional modules. Otherwise, action # 1 applies.
Severity: Minor.
RLC0035
SNMP trap: Yes
Failed to register to Remote Site [Remote Office unit ID].

Action: 1. Check IP/PSTN connectivity.
2. Check status of the remote host.
3. Check that configuration is correct and units are enabled.
Severity: Major.
RLC0037
SNMP trap: Yes
Not able to connect to Remote Site [Remote Office unit ID] on [transport
medium] medium, where transport medium = IP or PSTN.
Action: Verify the following.
1. correct configuration
2. proper network connections
3. status of the remote board
Severity: Major.
RLC0039
SNMP trap: Yes
Attempt to bring up additional trunk failed: Remote Site [Remote Office unit
ID], PSTN number attempted [number], flag [flag],
where the flag can have one of the following values:
1 = attempt was made by local board
2 = attempt was made by remote board
Action: 1. Ensure the PSTN numbers shown in Trunk Configuration are correct
on both the RLC and Remote Office 9150 unit.
2. Ensure the trunk route to that Remote Office unit is not busy.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1447 of 2360

RLC0040
Transition to PSTN failed for Remote Site [Remote Office unit ID].
Action: 1. Verify primary PSTN number. If PSTN is disabled, ignore the
message.
2. If messages RLC0042 or RLC0056 also display, the IP network may be down.
Refer to the actions for those messages.
3. Trunk route might be busy to that remote.
Severity: Minor.
RLC0042
SNMP trap: Yes
Abrupt failure of IP network. Remote Site: [Remote Office unit ID].

Action: Check the IP network for intact connection and other problems.
Severity: Major.
RLC0043
SNMP trap: Yes
Abrupt failure of a non-primary trunk. Remote Site: [Remote Office unit ID].
Action: 1. Verify PSTN connections.
2. Link might have failed somewhere in the PSTN.
Severity: Major.
RLC0044
SNMP trap: Yes
Abrupt failure of primary signaling to Remote Site [Remote Office unit ID].
Action: 1. Check IP and trunk connections (physical connections).
2. Link might have failed somewhere in the PSTN.
Severity: Critical.
RLC0056
SNMP trap: Yes
Call of [bandwidth] BW dropped to Remote Site [Remote Office unit ID] on

[transport medium] medium.
Action: Look for error messages RLC0042, RLC0043, or RLC0044 to ascertain
the reason active calls were dropped.
Severity: Major.
RLC0074
SNMP trap: Yes
Status change to [status] detected for BRI module [BRI module number].
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1448 of 2360

RLC0076
Incompatible software in ROU [Remote Office unit ID]. Communication with

Remote Site is not possible.
Action: Verify software versions on both units.
Severity: Critical.
RLC0081
SNMP trap: Yes
Connectivity failure to Remote Site [Remote Office unit ID] on [transport

medium] medium.
Action: Check for the following on the specified medium.
1. Network connectivity both at RLC and the remote site.
2. Any problem on the network between RLC and the remote site.
3. Whether any of the units got reset for any reason.
Severity: Major.
RLC0085
SNMP trap: Yes
DSP load attempt failed: DSP module # [module number], DSP device #
[device number].
Action: 1. Swap DSP module slot positions to see if the failure follows one DSP
module. Report failures to on-board DSPs (Module 0) to Nortel Networks.
2. Check DSP status in Configuration Manager Alarms/Stats/Logs, DSP
Statistics screen.
Severity: Major.
RLC0087
SNMP trap: Yes
DSP taken out of service: DSP module # [module number], DSP device #
[device number].
Action:
Severity: Major.
RLC0093
SNMP trap: Yes
Emergency Access Code dialed from port [port #], DN [DN #].
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1449 of 2360
RPD: 1.5 Mb/s Remote Peripheral

Equipment Diagnostic (LD 33)
This program is loaded manually or as one of the daily maintenance (midnight)
routines. It must be included in the midnight routines for any system having
Remote Peripheral Equipment (RPE).
Problems are reported in RPD messages.
Messages
RPD0000
Program identifier.
Action:
Severity: Info.
RPD0001
SNMP trap: No
SNMP trap: Yes
SNMP trap: Yes

Action: Check input.
Severity: Info.
RPD0002
Invalid command.
Severity: Info.
RPD0003
Incorrect number of parameters for command.

Action:
Severity: Info.
RPD0004
SNMP trap: Yes
Invalid customer number for CMIN.

Severity: Info.
RPD0005
SNMP trap: No
Invalid parameter value or option for command.

Severity: Info.
SNMP trap: Yes
System Messages
Page 1450 of 2360

RPD0006
Loop specified is not an RPE loop. Command was not executed.

Action: Use LRPE command to determine which loops are equipped RPE loops.
Severity: Info.
RPD0007
SNMP trap: Yes
ENLL command specified loop which was already enabled or test was
requested on disabled loop. Command not executed.
Action: Use ENLL or DISL as required.
Severity: Info.
RPD0008
SNMP trap: Yes
ENLL command not executed.

Action: Use LD 32 to enable PS.
Severity: Info.
RPD0009
SNMP trap: Yes
A DISI request is already active.

Action: Enter the END command to terminate the current request, if required.
Severity: Info.
RPD0010
SNMP trap: Yes
Command execution is in progress.

Action: Enter END to terminate, if required.
Severity: Info.
RPD0011
SNMP trap: Yes
Attempt to disable primary carrier. Command not executed.

Action: Use SCAR command to make the other carrier primary.
Severity: Info.
RPD0012 loop c
SNMP trap: Yes
The current command has cancelled an active DISI request for carrier c. This
is not an error condition.
Action:
Severity: Info.
RPD0013
SNMP trap: Yes
Carrier enabled when ENLC command given or carrier disabled when DISI or
DISC command given. Command not executed.
Action: Use ENLC or DISC.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1451 of 2360

RPD0014
Current non-primary carrier disabled or DISI active on carrier. If this condition

is detected during the midnight routines, the loop number is also output. SCAR
command not executed.
Action: Use ENLC to enable secondary carrier if required.
Severity: Info.
RPD0015
SNMP trap: Yes
Cannot switch carriers due to faults on secondary carrier.

Action: Disable, then re-enable the secondary carrier to clear fault indications
for the carrier. This procedure should be used only if it is essential to switch
carriers or if it is believed that the fault on the carrier has been cleared.
Severity: Minor.
RPD0016
SNMP trap: Yes
Command not available.

Action: Use LD 62.
Severity: Info.
RPD0017
SNMP trap: Yes
Continuity test not done. All channels were busy.

Action: Test later. No fault implied.
Severity: Info.
RPD0018 loop c
SNMP trap: Yes
Carrier c disabled per DISI request.

Action:
Severity: Info.
RPD0019
SNMP trap: Yes
Cannot switch carriers. Carrier status monitoring is disabled. If this condition

is detected during midnight run, loop number is also output.
Action: Use the ENLM command to re-enable status monitoring.
Severity: Info.
RPD0020
SNMP trap: Yes
Attempt to disable a loop to which the active maintenance set is connected.

Command is not executed.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1452 of 2360

RPD0021 loop
An input buffer overflow occurred during an RPS test of the loop. Some
signaling messages were lost. The memory test was terminated. No fault is
implied.
Action: Repeat test later.
Severity: Minor.
RPD0022
SNMP trap: Yes
A STAT command was entered to check the status of the current DISI
command but no DISI command was active.
Action:
Severity: Info.
RPD0030
SNMP trap: Yes
Program was loaded automatically to check carrier which had been

automatically re-enabled. All RPE loops are tested and faults are indicated by
output codes.
Action:
Severity: Minor.
SNMP trap: Yes
RPD0202 loop: s1 s2 sn Continuity test failed for shelves s1, s2, etc. If all shelves on the loop
failed, treat as RPD240. If at least one shelf is not in the list, probable fault in:
1. Peripheral Buffer or Controller
2. cable connecting network card to PE shelves
Action:
Severity: Critical.
RPD0203 loop: n
SNMP trap: Yes
Test of connection memory of network card failed, n channels are disabled.

Network card probably faulty. If multiple network cards in the same group
show this fault, it may be a fault in the CE extender connected to the group.
Action:
Severity: Critical.
RPD0204 loop
SNMP trap: Yes
Loop failed to respond to ENLL. Check that the network card is present and
enabled at the faceplate switch. If so, the card may be faulty. If other loops on
the same shelf fail to respond, it may be a fault in the CE extender to the group.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1453 of 2360

RPD0205 loop
The continuity checker is faulty. Possible fault in the network card.

Action:
Severity: Critical.
RPD0208 loop ts
SNMP trap: Yes
Network map indicates timeslot is idle but network memory is not idle.
Action:
Severity: Critical.
RPD0211 loop c
SNMP trap: Yes
Outgoing carrier c has failed. Timeslots using this carrier have been busied
out. Use LD 62 LOCL command to check local end. If RPE211 is output from
this command, then the fault may be:
1. QPC62 1.5Mb/s Baud Converter at local end
2. other local RPE cards
3. Network card
Action:
Severity: Critical.
RPD0214 loop c
SNMP trap: No
Incoming carrier c has failed. Timeslots using this carrier have been busied
out. Use LD 62 LOCL command to check local end. If RPD214 or RPD215 is
output from this command, then the fault may be:
1. QPC99 Carrier Interface at local end
2. QPC63 Local Carrier Buffer
3. Network card
If RPD214 or RPD215 is not output from the LOCL command, then the fault
may be in the incoming line from the remote site, or the QPC62 at the remote
site.
Action:
Severity: Critical.
RPD0215 loop c
SNMP trap: No
SNMP trap: No
See RPD214.
Action:
Severity: Critical.
RPD0220 loop
Local carrier buffer card does not respond. Fault may be: 1. QPC63 Local
Carrier Buffer 2. Network car 3. cable connecting the above cards
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1454 of 2360

RPD0221 loop
Local carrier buffer card failed signaling test. See RPD220 for possible faults.
Action:
Severity: Critical.
RPD0230 loop
SNMP trap: Yes
The QPC65 Remote Peripheral Switch failed to respond. Use LD 62 STAT

command to determine which carrier is primary, then use the LOCL loop c ALL
command to test that carrier's local equipment. If the test shows no fault at the
local end, the fault may be in the remote end:
1. QPC63 Local Carrier Buffer
2. Network card
3. cable connecting the above cards
Action:
Severity: Critical.
RPD0231 loop x
SNMP trap: Yes
The QPC65 Remote Peripheral Switch failed the memory connection test, x
speech channels have been disabled. Fault may be the QPC65 Remote
Peripheral Switch.
Action:
Severity: Critical.
RPD0232 loop x
SNMP trap: Yes
Same as RPD230 except all tested channels failed.

Action:
Severity: Critical.
SNMP trap: Yes
RPD0240 loop c x Continuity test failed with carrier c, x speech channel have been disabled. Use
LD 62 LDIS command for each carrier on the loop to determine which
channels failed.
Action:
Severity: Info.
RPD0250 loop
553-3001-411
SNMP trap: Yes
Carriers did not switch with SCAR command or in the midnight routines. This
fault, by itself is not service affecting. Fault may be:
1. QPC63 Local Carrier Buffer local or remote
2. QPC99 Carrier Interface at local end
Standard 15.00
January 2006
Page 1455 of 2360

3. QPC66 2 Mb/s Baud Converter local or remote
4. QPC99 Carrier Interface remote end
5. QPC62 1.5 Mb/s Baud Converter remote end
Action:
Severity: Critical.
RPD0261 loop c
SNMP trap: Yes
High error rate on carrier c. See RPD211 and RPD214.

Action:
Severity: Critical.
RPD0300
SNMP trap: No
Card did not respond to command/query (response timed out).

Action: Ensure that the card is plugged in correctly, and the faceplate switch is
in the enable position. If the card is still not responding a download is necessary.
Severity: Minor.
RPD0301
SNMP trap: Yes
Response to DSOP: Disabling this link would bring down service; command
refused.
Action: Use LD 32 to disable FNET and FPEC and then try again.
Severity: Minor.
RPD0302
SNMP trap: Yes
Response to ENOP: packlet does not exist. Can not enable this link.
Action: Insert packlet on both cards (FNET and FPEC) or stop the transmission
test.
Severity: Minor.
RPD0303
SNMP trap: Yes
Response to MNSN/MNSP: other link is faulty or disabled. Command refused.

Action: Enable the link using the ENOP command and then try again.
Severity: Minor.
RPD0304
SNMP trap: Yes
Response to MNSN/MNSP: other link is under transmission test. Command

refused.
Action: Stop transmission test using the 'FSTP' command and try again.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1456 of 2360

RPD0305
Response to FTST: only one test can be performed. Command refused.

Action: Use FSTA command for test status, or stop the test and try again. If the
link is disabled then use the 'ENOP' command and try again.
Severity: Minor.
RPD0306
SNMP trap: Yes
Response to FSTA/FSTP: there is no running test; Command refused.

Action: Use the 'FSTA' command for starting a test and try again.
Severity: Minor.
RPD0307
SNMP trap: Yes
Cannot send message to Fibre Network Card.

Action: Wait and retry the command layer. If this error occurs again check the
FNET card and associated cabling (equivalent of NPR084).
Severity: Minor.
RPD0308
SNMP trap: Yes
Response to PRPM: message with wrong Performance Monitoring interval

number received.
Action: Wait and retry the command later.
Severity: Minor.
RPD0309
SNMP trap: Yes
Remote IPE Package (286) is restricted.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1457 of 2360
RPE: 2.0 Mb/s Remote Peripheral

Equipment Alarm Handler (LD 53)
The RPE Alarm Handler monitors and reports alarm signals generated for the
2.0 Mb/s Remote Peripheral Equipment feature. To test RPE, use LD 53.
This Overlay is not provided on Small Systems and Succession 1000
systems,, since Remote Peripheral Equipment (RPE) is not used on these
systems.
The following alarm conditions and responses are reported by the resident
RPE alarm handler:
RPE0xxindicates occurrence of processor-detected faults
RPE1xxindicates counter threshold violations on processor detected faults.
Sparing will be attempted if the loop is not under maintenance control.
RPE2xxindicates timer threshold violations on processor-detected faults.
Sparing will be attempted if the loop is not under maintenance control.
RPE3xxindicates problems associated with sparing. Sparing will be
aborted.
RPE4xxindicates problems encountered during initialization of RPE loops.
Messages
RPE0000
Program Identifier
Action:
Severity: Minor.
RPE0001 loop
SNMP trap: No
Frame alignment signal error rate exceeded at remote site of loop. Message
is printed for each occurrence.
Action:
Severity: Critical.
RPE0002 loop
SNMP trap: Yes
PCM error rate exceeded at remote end of RPE loop. Message is printed for
each occurrence.
Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 1458 of 2360

RPE0003 loop
Customer-specified alarm 3 for RPE loop.

Action: Refer to customer records.
Severity: Critical.
RPE0004 loop
SNMP trap: Yes

Action:
Severity: Critical.
RPE0005 loop
SNMP trap: Yes
Remote controller failed on RPE loop.

Action: Test remote RPC.
Severity: Critical.
RPE0006 loop
SNMP trap: No

Action:
Severity: Critical.
RPE0007 loop
SNMP trap: Yes
Loss of carrier clock at the local site for RPE loop. Probable carrier fault.
Action: Use loop-around test to isolate.
Severity: Critical.
RPE0008 loop
SNMP trap: Yes
Path switch missing faulty or disabled on RPE loop.

Action: Check path switch for shelf. Enable if disabled or replace if faulty.
Severity: Critical.
RPE0010 loop
SNMP trap: Yes
Loss of frame alignment at the remote site of RPE loop. Message printed for
each occurrence.
Action:
Severity: Critical.
RPE0011 loop
SNMP trap: Yes
Loss of frame alignment at the local site of RPE loop. Message printed for
each occurrence.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1459 of 2360

RPE0012 loop
PCM error rate exceeded at local site of RPE loop. Message printed for each
occurrence.
Action:
Severity: Critical.
RPE0013 loop
SNMP trap: Yes
Frame alignment signal error rate exceeded at local site for RPE loop.
Message printed for each occurrence.
Action:
Severity: Critical.
RPE0014 loop
SNMP trap: Yes
Local controller outgoing messages buffer of loop overflowed. Message

printed for each occurrence. Probable network fault.
Action: Test network.
Severity: Critical.
RPE0015 loop
SNMP trap: Yes
Local controller incoming messages buffer of loop overflowed. Message

printed for each occurrence.
Action: Perform loop-around test on loop.
Severity: Critical.
RPE0016 loop
SNMP trap: Yes
Local controller of RPE loop initialized. Probable local RPC fault.

Action: Test RPC.
Severity: Critical.
RPE0017 loop
SNMP trap: Yes
SSD failure on peripheral buffer of RPE loop.

Action: Check peripheral buffers.
Severity: Critical.
RPE0023 loop
SNMP trap: Yes
Customer specified alarm 3 has been cleared.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 1460 of 2360

RPE0024 loop

Action:
Severity: Minor.
RPE0025 loop
SNMP trap: Yes
Warning: Customer specified alarm has not been cleared.

Action:
Severity: Minor.
RPE0026 loop
SNMP trap: No

Action:
Severity: Minor.
RPE0101 loop
SNMP trap: Yes
Counter threshold of alarm condition RPE001 exceeded. Probable carrier

fault.
Severity: Minor.
RPE0102 loop
SNMP trap: No

fault.
Severity: Minor.
RPE0105 loop
SNMP trap: No
Counter threshold of alarm condition RPE005 exceeded.

Action: Test and repair remote RPC.
Severity: Minor.
RPE0110 loop
SNMP trap: No
Counter threshold of alarm condition RPE010 exceeded. Probable carrier or

Carrier Interface (CI) pack fault.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1461 of 2360

RPE0111 loop
Counter threshold of alarm condition RPE011 exceeded. Probable remote

RPC or CI card failure.
Action:
Severity: Minor.
RPE0112 loop
SNMP trap: No

fault.
Action: Use loop-around tests to isolate the fault.
Severity: Minor.
RPE0113 loop
SNMP trap: No

fault.
Severity: Minor.
RPE0116 loop
SNMP trap: No
Counter threshold of alarm condition RPE016 exceeded.

Action: Test and repair RPC card.
Severity: Minor.
RPE0201 loop
SNMP trap: No
Alarm RPE001 has exceeded timer threshold. Probable carrier fault.

Severity: Minor.
RPE0202 loop
SNMP trap: No
Alarm RPE002 has exceeded timer threshold. Probable carrier fault.

Severity: Minor.
RPE0205 loop
SNMP trap: No
Alarm RPE005 has exceeded timer threshold.

Action: Test and repair remote RPC.
Severity: Minor.
RPE0210 loop
SNMP trap: No
Alarm RPE010 has exceeded timer threshold. Probable CI or carrier fault.

Severity: Minor.
SNMP trap: No
System Messages
Page 1462 of 2360

RPE0211 loop
Timer threshold of alarm condition RPE011 exceeded. Probable remote RPC

or CI failure.
Action:
Severity: Minor.
RPE0212 loop
SNMP trap: No
Timer threshold of alarm condition RPE012 exceeded. Probable carrier fault.

Severity: Minor.
RPE0213 loop
SNMP trap: No
Timer threshold of alarm condition RPE013 exceeded. Probable carrier fault.

Severity: Minor.
RPE0300 l1 l2 l3
SNMP trap: No
Request to spare loop l1 with l2 has failed. l1 was switched to L3 loop instead.
Path switch or spare loop faulty.
Action: Test and repair.
Severity: Minor.
RPE0301 loop
SNMP trap: Yes
Loop cannot be spared because it is a spare loop. Spare loop may be

disabled; check status.
Action:
Severity: Minor.
RPE0302 loop
SNMP trap: Yes
Loop does not have a spare. Sparing aborted.

Action:
Severity: Minor.
RPE0303 g
SNMP trap: Yes
Group g is out of range or data corruption.

Action:
Severity: Minor.
RPE0304 loop s
SNMP trap: Yes
Loop l cannot be spared by s because spare is in use.

Action: Test and clear fault on loop already spared.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1463 of 2360

RPE0305 loop s
Loop cannot be spared by s because spare is faulty.

Action: Test and clear fault on spare loop.
Severity: Minor.
RPE0306 l1 l2
SNMP trap: Yes
Loop l1 cannot be spared by l2 because path switch is disabled or

unequipped.
Action: If path switch is equipped, enable and try again.
Severity: Minor.
RPE0307 l1 l2
SNMP trap: Yes
Loop l1 sparing by l2 aborted because of bad response from remote RPE in

spare loop.
Action: Test RPC of spare loop.
Severity: Minor.
RPE0308 l1 l2
SNMP trap: Yes
Loop l1 sparing by l2 aborted because of bad response from remote RPC in

spare loop.
Action: Test and repair RPC of spare loop.
Severity: Minor.
RPE0309 l1 l2
SNMP trap: Yes
Loop l1 sparing by l2 aborted because of bad response from spare loop.

Action: Test and repair spare loop.
Severity: Minor.
RPE0310 loop
SNMP trap: Yes
Loop cannot be spared because spare loop is disabled.

Action: Test and enable spare loop.
Severity: Minor.
RPE0311 l1 l2
SNMP trap: Yes
Software problem. Loop l2 should not have loop L1 assigned.

Severity: Minor.
RPE0312 loop
SNMP trap: No
Loop cannot be spared because loop is disabled.

Action: Test and enable the loop.
Severity: Minor.
SNMP trap: No
System Messages
Page 1464 of 2360

RPE0313
A PSW response message has been received from a prime loop, while it was
expecting from the spare loop. (Loop the message comes from and spare loop
numbers to follow.)
Action:
Severity: Minor.
RPE0400 loop
SNMP trap: Yes
A PE shelf cannot be enabled after an RPC initialize.

Action: Test local and remote RPC.
Severity: Minor.
RPE0401 loop
SNMP trap: Yes
Bad response received from RPC card.

Action: Test RPC.
Severity: Minor.
RPE0402 loop
SNMP trap: Yes
Bad response from RPC card.

Action: Test RPC.
Severity: Minor.
RPE0403 loop
SNMP trap: Yes
Bad response from RPC card.

Action: Test RPC.
Severity: Minor.
RPE0404 loop
SNMP trap: Yes
No protected RPE group data block has been defined for this loop. Loop has
been disabled.
Action:
Severity: Minor.
RPE0500 loop
SNMP trap: Yes
SNMP trap: Yes
Loop has been spared.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 1465 of 2360
RPL: 1.5 Mb/s Remote Peripheral

Equipment Local End Diagnostic (LD 62)
The 1.5 Mb/s Remote Peripheral Equipment Diagnostic, Local End program
(LD 62) is loaded manually to test the local equipment associated with a
particular carrier going to a remote site. Problems are reported in RPL
messages.
Messages
RPL0000
Action:
Severity: Info.
RPL0001
SNMP trap: No
SNMP trap: Yes
SNMP trap: Yes

Action:
Severity: Info.
RPL0002
Invalid command.
Action:
Severity: Info.
RPL0003

Action:
Severity: Info.
RPL0005
SNMP trap: Yes
Invalid parameter value or option.

Action:
Severity: Info.
RPL0006
SNMP trap: Yes
Loop is not an RPE loop. LRPE command of LD 33 will give equipped RPE
loops.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1466 of 2360

RPL0007
Loop is disabled.
Action: Use ENLL command of LD 33.
Severity: Info.
RPL0009
SNMP trap: Yes
DISI command already active.

Action: Use END to cancel DISI.
Severity: Info.
RPL0010
SNMP trap: Yes
Command execution already in progress.

Action: Enter END to terminate, if desired.
Severity: Info.
RPL0011
SNMP trap: Yes
DISC or DISI specified primary carrier. Command not executed.

Action: Use SCAR to make the other carrier primary.
Severity: Info.
RPL0012 loop c
SNMP trap: Yes
The current command has canceled the active DISI command on carrier c.
This is not an error condition, message is for information only.
Action:
Severity: Info.
RPL0013
SNMP trap: Yes
Carrier enabled when ENLC, LPBK or LOCL command given; or carrier was
disabled when DISI or DISC given. Command not executed; use ENLC or
DISC.
Action:
Severity: Info.
RPL0014
SNMP trap: Yes
Current secondary carrier is disabled or DISI active on carrier. SCAR

Action: Use ENLC to enable secondary carrier.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1467 of 2360

RPL0015
Cannot switch carriers because of faults on secondary carrier.

Action: If fault has been found and cleared or if it is essential to switch carriers,
disabling then re-enabling the secondary carrier will clear the fault indications. A
complete test using LD 33 should be made to avoid the use of faulty timeslots by
call processing functions.
Severity: Info.
RPL0018 loop c
SNMP trap: Yes
DISI command completed for carrier c. This is not an error condition.

Action:
Severity: Info.
RPL0019
SNMP trap: Yes
Cannot switch carriers: carrier status monitoring disabled. Use ENLM

command of LD 33 to re-enable status monitoring.
Action:
Severity: Info.
RPL0022
SNMP trap: Yes
STAT command given when no DISI command was active.

Action:
Severity: Info.
RPL0023
SNMP trap: Yes
During execution of the LOCL test with the ALL option, the channel required
for testing the signaling channel was busy.
Action: This is not a fault condition; retry test later.
Severity: Info.
RPL0203 loop n
SNMP trap: No
Test of connection memory of network for loop failed, n channels are disabled.
Network card probably faulty. See also RPD203.
Action:
Severity: Critical.
RPL0205 loop
SNMP trap: Yes
Continuity checker on loop is faulty. Network card probably faulty.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1468 of 2360

RPL0208 loop ts
Network map in software indicates that timeslot ts is idle but connection

memory word for that slot is not idle. Probable software fault, similar to
BUG365. The timeslot will be marked busy.
Action:
Severity: Critical.
RPL0211 loop c
SNMP trap: Yes
Outgoing carrier c has failed. If this message appears in response to the LOCL
command, probable fault in: 1. 1.5 Mb/s Converter at local end 2. Other local
RPE pack; Local Carrier Buffer, 2 Mb/s Converter or Carrier Interface. 3.
Network cad
Action:
Severity: Critical.
RPL0214 loop c
SNMP trap: Yes
Incoming carrier c has failed. If this message appears in response to the LOCL
command, probable fault in:
1. Carrier Interface at local end.
2. Local Carrier Buffer.
3. Network card.
Action:
Severity: Critical.
RPL0215 loop c
SNMP trap: Yes
Incoming carrier c has failed. If this message appears in response to the LOCL
command, probable fault in:
1. Carrier Interface at local end
2. Local Carrier Buffer
3. Network card
Action:
Severity: Critical.
RPL0220 loop
SNMP trap: Yes
LCB card does not respond. Probable fault on:

1. Local Carrier Buffer
2. Network card
3.Cable connecting the above packs
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1469 of 2360

RPL0221 loop
Scan and Signal Distributor (SSD) on LCB pack failed the signaling test. Same
as for RPL220.
Action:
Severity: Critical.
RPL0241 n
SNMP trap: Yes
During the LOCL test, n speech channels which are always carried by the
carrier being tested, failed continuity test. Probable fault at local end on 2 Mb/s
Converter, 1.5 Mb/s Converter or LCB.
Action:
Severity: Critical.
RPL0242 n
SNMP trap: Yes
During the LOCL test with the ALL option, n speech channels which are
carried by the carrier (only when it is the primary carrier) being tested, failed
the continuity test. See RPL241.
Action:
Severity: Critical.
RPL0243
SNMP trap: Yes
Local loop-around test of signaling channel failed. See RPL241.

Action:
Severity: Critical.
RPL0250 loop
SNMP trap: Yes
Carriers failed to switch. Faulty LCB, Carrier Interface or 2 Mb/s Converter at

local end.
Action:
Severity: Critical.
RPL0251
SNMP trap: Yes
During the LOCL test with the ALL option, carrier not being tested could not be
made primary. See RPL250.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1470 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1471 of 2360
RPM: 2.0 Mb/s Remote Peripheral

Equipment Diagnostic (LD 53)
The 2.0 Mb/s Remote Peripheral Equipment Diagnostic program (LD 53) is
loaded as part of the daily routines, or manually to enter commands. Problems
are reported in RPM messages.
Messages
RPM0000
Action:
Severity: Info.
RPM0001
SNMP trap: No
SNMP trap: Yes
SNMP trap: Yes

Severity: Minor.
RPM0002
Invalid command.
Severity: Info.
RPM0003

Severity: Info.
RPM0005
SNMP trap: Yes
Invalid parameter value or option.

Severity: Info.
RPM0006
SNMP trap: Yes
Loop specified is not an RPE loop. LRPE will give equipped RPE loops.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 1472 of 2360

RPM0007
Loop already enabled (ENLL) or loop already disabled (DISL/DISI).

Action:
Severity: Info.
RPM0008
SNMP trap: Yes
Peripheral Signaling (PS) pack associated with given loop is disabled. ENLL
Action: Use LD 32 to enable PS pack.
Severity: Info.
RPM0009
SNMP trap: Yes
DISI command already active. Command may be canceled via END.

Action:
Severity: Info.
RPM0010
SNMP trap: Yes
Command already in progress.

Action:
Severity: Info.
RPM0011
SNMP trap: Yes
ENLS command, shelf already enabled.

Action:
Severity: Info.
RPM0012 loop
SNMP trap: No
Active DISI command. This is not an error condition.

Action:
Severity: Info.
RPM0013
SNMP trap: Yes
ENLL, REML specified enabled loop. Disabled loop in DISI command.

Action:
Severity: Info.
RPM0017
SNMP trap: No
Continuity test not done because channels were busy.

Action: This is not a fault condition; retry test later.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1473 of 2360

RPM0018 loop
DISI command. This is not an error condition.

Action:
Severity: Minor.
RPM0019
SNMP trap: Yes
RPE group is not equipped.

Action:
Severity: Minor.
RPM0020
SNMP trap: No
Attempt to disable a loop to which an active maintenance set is connected.

Command was not executed.
Action:
Severity: Minor.
RPM0022
SNMP trap: Yes
STAT command without DISI command active. DISI command is completed.

See DISI command.
Action:
Severity: Minor.
RPM0041 loop
SNMP trap: Yes
Command failed because of wrong response or invalid message. Message

passed to alarm handler.
Action:
Severity: Minor.
RPM0042 loop
SNMP trap: Yes
Cannot do remote loopback because local loopback already active.

Action:
Severity: Minor.
RPM0044 loop
SNMP trap: Yes
Loop is not in loop-back mode. Use LBKL or LBKR to put it in loopback mode.
Action:
Severity: Minor.
RPM0046 loop
SNMP trap: Yes
Network does not respond.

Action: Check network for enable/disable status.
Severity: Minor.
SNMP trap: No
System Messages
Page 1474 of 2360

RPM0047 loop
Command aborted, loop is not disabled.

Action:
Severity: Minor.
RPM0048 loop
SNMP trap: Yes
Command aborted, loop is in loop-back mode.

Action: Remove loop from loop-back mode (OLBL or OLBR).
Severity: Minor.
RPM0049 g
SNMP trap: Yes
Group number out-of-range or invalid.

Action: Check data and try again.
Severity: Minor.
RPM0050 g
SNMP trap: Yes
RPE group number not defined as an RPE group.

Action:
Severity: Minor.
RPM0051 loop
SNMP trap: Yes
Continuity test: Data pattern received is not the same as sent during loopback.
Action:
Severity: Minor.
RPM0052 loop
SNMP trap: Yes
Continuity test: Timeout when waiting for sent data pattern to come back
during loopback.
Action:
Severity: Minor.
RPM0054 loop
SNMP trap: Yes
Wrong message received when reading status register or incorrect path switch
status.
Action:
Severity: Minor.
RPM0055 loop
SNMP trap: Yes
Timeout when reading status register after sending unsparing message.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1475 of 2360

RPM0056 loop
Group which loop belongs to is not spared.

Action:
Severity: Minor.
RPM0057 loop
SNMP trap: Yes
UNSP command was not successful in its attempt to disable the spare loop in
software to prevent new calls from taking place.
Action:
Severity: Minor.
RPM0058 loop
SNMP trap: Yes
Cannot unspare group because loop is not enabled.

Action:
Severity: Minor.
SNMP trap: Yes
RPM0202 loop: s1 s2 Continuity test failed for shelves s1, s2, etc. If all shelves on the loop failed,
treat as RPM240. At least one shelf is not in the list, probable fault in:
1. Peripheral Buffer in shelves listed
2. Shelf or shelves listed
3. Cable between PE shelves
Action:
Severity: Critical.
RPM0203 loop: n
SNMP trap: Yes
Connection memory test failed; n channels are disabled. Network card

probably faulty. If multiple network cards in the same exhibit show this fault,
CE extender card connected to the group is probably faulty.
Action:
Severity: Critical.
RPM0204 loop
SNMP trap: Yes
Loop failed to respond.

Action: Check that network is present and enabled by faceplate switch; if so,
card may be faulty. If other loops on the same shelf also fail to respond, a fault in
the CE extender connected to the group is possible.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1476 of 2360

RPM0205 loop
Continuity checker is faulty. Network card probably faulty.

Action:
Severity: Critical.
RPM0208 loop: ts
SNMP trap: Yes
Network map in software indicates that timeslot ts is idle but the connection
memory word for that slot on network card is not idle. The slot will be marked
busy. Probably a software fault similar to BUG365.
Action:
Severity: Critical.
RPM0240 loop: n
SNMP trap: Yes
Continuity test phase of loop test failed, n speech timeslots are disabled due
to this fault.

Severity: Critical.
RPM0241 n
SNMP trap: Yes
During the LOCL test, n speech channels failed continuity test. Probable fault
at local end.
Action: Test CI or Remote Peripheral Carrier (RPC).
Severity: Critical.
RPM0242 n
SNMP trap: Yes
During the REML test, n speech channels failed continuity test. Probable fault
at local end CI/RPC or carrier.
Action: Test and repair.
Severity: Critical.
RPM0250 loop
SNMP trap: Yes
Local RPC processor failed.

Action:
Severity: Critical.
RPM0251 loop
SNMP trap: Yes
Remote RPC processor failed.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1477 of 2360

RPM0307 loop
Time-out or wrong message when reading control register during closing or

opening of loopback.
Action:
Severity: Critical.
RPM0308 loop
SNMP trap: Yes
Loop down (LPDN) status does not verify. Probable fault in local RPC.
Action:
Severity: Critical.
RPM0309 loop
SNMP trap: Yes
Timeout when reading data pattern written to control or status register during
loopback.
Action:
Severity: Critical.
RPM0310 loop
SNMP trap: Yes
Wrong data pattern returned when reading control or status register during
loopback.
Action:
Severity: Critical.
RPM0315 loop
SNMP trap: Yes
Timeout when reading control register.

Action:
Severity: Critical.
RPM0316 loop
SNMP trap: Yes
Wrong or unexpected message received when reading control register.

Action:
Severity: Critical.
RPM0317 loop
SNMP trap: Yes
Timeout when reading shelf enable register.

Action:
Severity: Critical.
RPM0318 loop
SNMP trap: Yes
Wrong or unexpected message received when reading shelf enable register.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 1478 of 2360

RPM0319 loop
Timeout when reading status register.

Action:
Severity: Critical.
RPM0320 loop
SNMP trap: Yes
Wrong or unexpected message received when reading status register.

Action:
Severity: Critical.
RPM0323 loop
SNMP trap: Yes
Loop number out-of-range (RCNT).

Action:
Severity: Critical.
RPM0324 loop
SNMP trap: Yes
SNMP trap: Yes
TRPL interrupted.
Action:
Severity: Critical.
RPM0325 loop
Loop is not spared (UNSP).

Action:
Severity: Critical.
RPM0326 loop
SNMP trap: Yes
Spare loop cannot be unspared (USNP).

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1479 of 2360
RPT: System Reporting

Messages
RPT0001
Begin suppression of {filename}.

Action:
Severity: Info.
RPT0002
SNMP trap: Yes
End suppression of {filename}.

Action:
Severity: Info.
RPT0003
SNMP trap: Yes
Unknown report (not in database). cat x, report y.

Action:
Severity: Info.
RPT0004
SNMP trap: Yes
X reports missing in log test before x.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1480 of 2360
553-3001-411
Standard 15.00
January 2006
Page 1481 of 2360
SCH: Service Change

The SCH messages indicate invalid responses, or service change problems
caused by a system condition (for example, the time and date is not set). SCH
messages are also output when corrupt or invalid data is detected.
Messages
SCH0000
Invalid input.
Action:
Severity: Minor.
SCH0001
SNMP trap: No
TNTRANS failed on remove from core. Corrupted data in memory.

Action: System should be reloaded. If fault persists, contact your technical
support group.
Severity: Info.
SCH0002
SNMP trap: No
TNTRANS failed on recover workspace.

Action: System should be reloaded. If fault System should be reloaded. If the
fault persists, contact your technical support group.
Caution: Call processing will be interrupted during reload.
Severity: Info.
SCH0003
SNMP trap: No
TNTRANS passes on recover out workspace Caution: Call processing will be

interrupted during reload.
Action:
Severity: Info.
SCH0004
SNMP trap: No
TNTRANS passes on work to core.

Action:
Severity: Info.
SCH0005
SNMP trap: No
RDB translator passes and fails. Corrupted data in memory.

Action: System should be reloaded. If fault persists, contact your technical
support group
Severity: Info.
SNMP trap: No
System Messages
Page 1482 of 2360

SCH0006
The maximum number of MWI NSI tables (32) has been reached.
Action: Contact your technical support group if 32 tables are insufficient.
Severity: Major.
SCH0007
SNMP trap: No
Character out of the range B, E, H, K, N, Q, T, W, Z, b, e, h, k, n, q, t, w, or z.

SUFF is re-prompted.
Action: Enter a character inside the valid range or {CR} if CHG command.
Severity: Info.
SCH0008
SNMP trap: No
Not an alphanumeric character.

Action: Enter character(s) inside the valid range or {CR} if the command is CHG
or it the prompt is PRMT.
Severity: Info.
SCH0009
SNMP trap: No
Too many characters for the NSI parameters already entered. MFID is
re-prompted.
Action: Enter a maximum of 126 characters for the total of the MWI NSI
parameters.
Severity: Info.
SCH0010
SNMP trap: No
DNXLBLOCK has a pointer flag but no pointer. Corrupted data in memory.

Action: System should be reloaded. If the fault persists, contact your technical
support group.
Severity: Info.
SCH0011
SNMP trap: No
TN in DNBLOCK fails TNTRANS.

Action:
Severity: Info.
SCH0012
SNMP trap: No
TN in DNBLOCK produces illegal TN type. Corrupted data in memory.

Action: System should be reloaded. If the fault persists, contact your technical
support group.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1483 of 2360

SCH0013
Terminal cannot be moved to a card with different XTRK field (XUS versus
non-XUS).
Action:
Severity: Minor.
SCH0014
SNMP trap: No
Invalid trunk type for XUS.

Action:
Severity: Minor.
SCH0015
SNMP trap: No
XUS trunk unit must belong to an XUS route only, and vice-versa.
Action:
Severity: Minor.
SCH0016
SNMP trap: No
In XUS RAN, only LVL and AUD route types are allowed.
Action:
Severity: Minor.
SCH0017
SNMP trap: No
If HLPA/HRLA then must IHA. (Individual hold allowed, OPT IHA in CDB,
Overlay 15).
Action: Configure the IHA in the CDB by using Overlay 15.
Severity: Info.
SCH0018
SNMP trap: No
Facility number out of range.

Action: Input a facility number from 1 to 99999
Severity: Info.
SCH0019
SNMP trap: No
Facility number is already defined for that service.

Action: Check the subscription parameters with the local CO and input the
correct subscribed facility number.
Severity: Info.
SCH0020
SNMP trap: No
Illegal attempt to modify existing data.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1484 of 2360

SCH0028
Attempt to configure RCAP with a QSIG Diversion remote capability when one
is already configured.
Action: Remove the already configured RCAP before entering a new one.
Severity: Info.
SCH0029
SNMP trap: No
BCOT initialized due to one of the following conditions: TKTP = ISA, DGTP ^=
PRI, MODE ^= PRA, IFC ^= D100 or D250 or ESS4 or ESS5 or NI2
Action:
Severity: Info.
SCH0031
SNMP trap: No
Autoline key should have a DN associated with it.

Action:
Severity: Info.
SCH0032
SNMP trap: No
IADN cannot be Attendant Overflow DN.

Action:
Severity: Info.
SCH0033
SNMP trap: No
IADN cannot be a System Night DN.

Action:
Severity: Info.
SCH0034
SNMP trap: No
The RCAP PRI (or PRO) is only allowed for QSIG interface type.
Action:
Severity:
SCH0035
SNMP trap: No
Attempt to configure RCAP to PRI when PRO is already configured.

Action: Remove the RCAP PRO first.
Severity:
SCH0036
SNMP trap: No
Attempt to configure RCAP to PRO when PRI is already configured.

Action: Remove the RCAP PRI first.
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1485 of 2360

SCH0037
Autoline key should have a DN associated with it.

Action:
Severity: Info.
SCH0038
SNMP trap: No
IADN cannot be Attendant Overflow DN.

Action:
Severity: Info.
SCH0040
SNMP trap: No
ROA/MOH does not exist for specified customer.

Action:
Severity: Info.
SCH0041
SNMP trap: No
Invalid range. Not enough digits.

Action:
Severity: Info.
SCH0048
SNMP trap: No
Not enough memory to allocate a DPNSS1 MWI or MWNS table.

Severity: Major.
SCH0049
SNMP trap: No
Priority buzz cadence is out of range (2-16 seconds).

Action:
Severity:
SCH0050
SNMP trap: No
ROA/MOH data block already exists.

Action:
Severity: Info.
SCH0051
SNMP trap: No
Attempt made to change a non broadcasting RAN route to broadcasting with

an insufficient number of available ISM RAN connections.
Action: Contact your technical support group and request an increase to
the ISM limit.
Severity: Info.
SNMP trap: No
System Messages
Page 1486 of 2360

SCH0052
Attempt was made to change a RAN route to broadcasting or non

broadcasting with active calls.
Action: Customer must take an action to not have any more active calls to any
of the trunk members. Trunks may be disabled or the RAN route may be replaced
by another one during the change. This last option will not disconnect any call.
Severity: Info.
SCH0053
SNMP trap: No
Attempt made to change the maximum number of connections to a

broadcasting trunk of a RAN route in overlay 16, but such a change would
exceed broadcast RAN connection ISM limit.
Action: Request your technical support group to increase theISM limit.
Severity: Info.
SCH0054
SNMP trap: No
Attempt was made to define a RAN route as a broadcast route with an

insufficient number of available ISM broadcasting RAN routes.
Action: Request your technical support group to increase theISM limit.
Severity: Info.
SCH0055
SNMP trap: No
Invalid console type for Individual Attendant DN.

Action:
Severity:
SCH0057
SNMP trap: No
Reduce the MAX value of NI-2 CBC service routes before removing
B-channels/trunks.
Action: Check the MAX value of service routes.
Severity: Minor.
SCH0060
SNMP trap: No
Insufficient data entered.

Action:
Severity: Info.
SCH0061
SNMP trap: No
The executed operation requires the QSIG-SS package which is restricted.

The executed operation is ignored.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1487 of 2360

SCH0062
The change of a Music broadcast route to a non broadcasting route, is not

allowed.
Action:
Severity: Info.
SCH0063
SNMP trap: No
Change of a Music route to a broadcasting route with active calls, is not

allowed.
Action: Replace the route with another music route. Wait for active calls to be
released before doing the change. Action:
Severity: Info.
SCH0064
SNMP trap: No
The TITH value is out of range (0-300).

Action: Enter a value that is in range.
Severity: Info.
SCH0065
SNMP trap: No
The NCTH value is out of range (0-100).

Action: Enter a value that is in range.
Severity: Info.
SCH0066
SNMP trap: No
The CONN value is out of range (4-48).

Action: Enter a value in the range (4-48).
Severity: Info.
SCH0067
SNMP trap: No
The LGTH value is out of range (4-7200).

Action: Enter a value in the range.
Severity: Info.
SCH0097
SNMP trap: No
The MWI NSI tables for this customer have reached the maximum size
allowable.
Action: Contact your technical support group if 512 words are not enough for the
MWI NSI tables of a customer.
Severity: Major.
SNMP trap: No
System Messages
Page 1488 of 2360

SCH0098
Request to add CMOD unit is rejected. System already has 255 CMOD units
configured.
Action:
Severity: Info.
SCH0099
SNMP trap: No
This message appears when the invalid input is detected by the machine. The
actual output may vary, according to the input received.
Action: Refer to the following examples for possible output.
Severity: Info.
SCH0099 XXX
SNMP trap: No
XXX is an invalid response. System does not recognize XXX.

Action: Try again.
Severity: Info.
SNMP trap: No
SCH0099 XXX : AAA XXX is an invalid response. System does not recognize XXX. Where: AAA
= the system suggestion of a possible match
Action:
Severity: Info.
SNMP trap: No
SCH0099 XXX : BBB CCC DDD... Abbreviated response XXX has more than 1 match. Where
XXX = a non-unique abbreviated response AAA, BBB, and CCCC =
responses that match XXX
Up to 3 matches are listed and "..." indicates more than 3 matches found.
Action:
Severity: Info.
SNMP trap: No
SCH0099 XXX? {MIN} - {MAX} {TYPE} Response XXX is out-of-range. Valid range is specified
by {MIN} - {MAX} , where response type is specified by the following:
{TYPE} = Characters for character string input
{TYPE} = DigitsS for digit string input
No {TYPE} specifies numeric input
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1489 of 2360

SCH0099 n?: 0 - 9999999 Input number n out-of-range (0-9999999) for LEC.
Action:
Severity: Info.
SCH0099 n?: 0-7
SNMP trap: No
Input number n out-of-range (0-7) for RDNL

Action:
Severity: Info.
SCH0099 n?: 0-9
SNMP trap: No
Input number n out-of-range (0-9)

Action: Choose a number 0 - 9.
Severity: Info.
SCH0100
SNMP trap: No
Wrong number of input fields for prompt REQ.

Action:
Severity: Info.
SCH0101
SNMP trap: No
Unable to match input fields with stored mnemonics.

Action:
Severity: Info.
SCH0102
SNMP trap: No
Repeat count out-of-range (2-255).

Action:
Severity: Info.
SCH0103
SNMP trap: No
ROA or MOA package not provided.

Action:
Severity: Info.
SCH0104
SNMP trap: No
AWU package not provided.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1490 of 2360

SCH0105

Action: Re-enter input.
Severity: Info.
SCH0106
SNMP trap: No
SNMP trap: No
Wrong parameter type.

Action:
Severity: Info.
SCH0107
There are no available busy lamp fields.

Action:
Severity: Info.
SCH0108
SNMP trap: No
Lamp field array is not included in OPT.

Action:
Severity: Info.
SCH0109
SNMP trap: No
TN is already assigned as an LFTN.

Action:
Severity: Info.
SCH0110
SNMP trap: No
Wrong number of input fields.

Action: Prompt MTAR is reprompted. Either press carriage return for default
entry of 'NO', or enter one of the responses 'YES' or 'NO'.
Severity: Info.
SCH0111
SNMP trap: No
You have entered an invalid response for that prompt. The system is unable
to match the field input with the stored mnemonics.
Action: Enter NEW, OLD, or {CR}.
Severity: Info.
SCH0112
SNMP trap: No
Invalid customer number.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1491 of 2360

SCH0113
The CISMFS package is not equipped.

Action: Equip the CIS MFS package or choose another answer.
Severity: Info.
SCH0114
SNMP trap: No
An attempt to define the CFMS class of service in LD14 for a digital trunk on
CDT/CSDT12 loop without CISFW=MFS. Define in LD73.
Action:
Severity: Info.
SCH0115
SNMP trap: No
An attempt to define the CMFS class of service in LD14 when MFS is not
defined in the Route Data Block.
Action:
Severity: Info.
SCH0116
SNMP trap: No
An attempt was made to remove the CMFS or MFS definitions from the Route
Data Block, when there are some trunks defined within the route.
Action:
Severity: Info.
SCH0117
SNMP trap: No
Band value for banded OUTWATS is out of range.

Action: Input Band value between 0-99.
Severity: Info.
SCH0118
SNMP trap: No
Band value for banded OUTWATS is already defined.

Action: Check with the local CO for the correct Band value.
Severity: Info.
SCH0119
SNMP trap: No
Overlap package (OVLP_ PACKAGE) is not equipped hence OVLS/ OVLR is

set to .FALSE from .TRUE.
Action: Install NI-2 CBC package.
Severity: Info.
SNMP trap: No
System Messages
Page 1492 of 2360

SCH0120
Wrong number of input fields for prompt TN.

Action:
Severity: Info.
SCH0121
SNMP trap: No
Loop not specified in configuration as terminal loop.

Action:
Severity: Info.
SCH0122
SNMP trap: No
Loop out-of-range (0-159).

Action:
Severity: Info.
SCH0123
SNMP trap: No
Shelf out-of-range (0-3 single density, 0-1 double density, 0 quadruple

density).
Action:
Severity: Info.
SCH0124
SNMP trap: No
Card out-of-range (1-10).

Action:
Severity: Info.
SCH0125
SNMP trap: No
Unit out-of-range 0-3 (SD), 0-7 (DD) or 0-15 (QD), 0-31 (OD)
Action: Re-enter TN within valid unit range for card.
Severity: Info.
SCH0126
SNMP trap: No
Station type conflicts with existing card.

For example: In LD 11, the craftperson has attempted to provision a digital set
in the same IPE slot as an existing ITG card.
Action:
Severity: Info.
SCH0127
SNMP trap: No
SNMP trap: No
Terminal already exists.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1493 of 2360

SCH0128
Terminal does not exist.

Action:
Severity: Info.
SCH0129
SNMP trap: No
Trunk type given is not the same as that in the TN block.

Action:
Severity: Info.
SCH0130
SNMP trap: No
Terminal has conflicting station type.

Action:
Severity: Info.
SCH0131
SNMP trap: No
Terminal is not primary TN.

Action:
Severity: Info.
SCH0132
SNMP trap: No
ADM must terminate on unit 1 or 3.

Action:
Severity: Info.
SCH0133
SNMP trap: No
Too many digits entered for NFCR condition.

Action:
Severity: Info.
SCH0134
SNMP trap: No
Value entered for CRCS is out-of-range.

Action:
Severity: Info.
SCH0136
SNMP trap: No
More general condition exists for NFCR.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1494 of 2360

SCH0137
NFCR linkage not built for customer.

Action:
Severity: Info.
SCH0138
SNMP trap: No
NFCR tree does not exist.

Action:
Severity: Info.
SCH0139
SNMP trap: No
Cannot add ADM or MDM to existing card unless ADM or MDM already exists
on the card.
Action:
Severity: Info.
SCH0140
SNMP trap: No
Frequency between 350 and 665 Hz, in 5 Hz increments.

Action:
Severity: Info.
SCH0141
SNMP trap: No

Action:
Severity: Info.
SCH0142
SNMP trap: No
SNMP trap: No

Action:
Severity: Info.
SCH0143
Terminal does not exist or has conflicting station type.

Action:
Severity: Info.
SCH0144
SNMP trap: No
Disabling FNP functionality.

Disabling FNP functionality.
Action: FNP data setup must be removed.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1495 of 2360

SCH0145
Too many parameters for FRL prompts.

Action:
Severity: Info.
SCH0146
SNMP trap: No
A larger MAXT value already exists. Once defined a lower value cannot be
entered for MAXT.
Action:
Severity: Info.
SCH0147
SNMP trap: No
MAXT value out-of-range (maximum 255).

Action:
Severity: Info.
SCH0148
SNMP trap: No
A value for MAXT is expected.

Action:
Severity: Info.
SCH0149
SNMP trap: No
NFCR blocks not cleared. Cannot out CDB.

Action:
Severity: Info.
SCH0150
SNMP trap: No
Wrong number of input fields for prompt CUST.

Action:
Severity: Info.
SCH0151
SNMP trap: No
Customer number out-of-range. In Release 15, the customer number is 0-99

for NT, RT, STE, XN and XT machines and system Options 21E, 51, 61, 71
and 81. It remains 0-31 for all other supported machines and system options.
Action:
Severity: Info.
SCH0152
SNMP trap: No

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1496 of 2360

SCH0153
Customer data block already exists.

Action:
Severity: Info.
SCH0154
SNMP trap: No
No group list exists for customer N.

Action:
Severity: Info.
SCH0155
SNMP trap: No
Background terminal must be removed before removing customer.

Action:
Severity: Info.
SCH0156
SNMP trap: No
An MWI NSI table already exists for this manufacturer.

Action: Do not use the command NEW for an MWI NSI
Severity: Info.
SCH0157
SNMP trap: No
Frequency delta between 10 and 315 Hz, in 5 Hz increments.

Action:
Severity: Info.
SCH0158
SNMP trap: No
Frequency level maximum between 0 db and -15 db, in 5 db increments. Enter

absolute value: 0, 5, 10 or 15.
Action: Enter absolute value: 0, 5, 10 or 15.
Severity: Info.
SCH0159
SNMP trap: No
Frequency level minimum between -20 db and -35 db, in 5 db increments.

Action: Enter absolute value: 20, 25, 30 or 35.
Severity: Info.
SCH0160
SNMP trap: No
Wrong number of input fields for prompt ROUT.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1497 of 2360

SCH0161
Route number out-of-range (0-127).

Action:
Severity: Info.
SCH0162
SNMP trap: No
Route data block already exists.

Action:
Severity: Info.
SCH0163
SNMP trap: No
Route data block does not exist.

Action:
Severity: Info.
SCH0164
SNMP trap: No
Cannot remove route data block while trunks still attached.

Action:
Severity: Info.
SCH0165
SNMP trap: No
Code restriction block already exists.

Action:
Severity: Info.
SCH0166
SNMP trap: No
Code restriction block does not exist.

Action:
Severity: Info.
SCH0167
SNMP trap: No
SNMP trap: No
Route type is not AIOD.

Action:
Severity: Info.
SCH0168
FNP data exists. FNP cannot be set to NO.

Action: FNP data must be removed. In LD15, set VNR to NO.
Severity: Major.
SNMP trap: No
System Messages
Page 1498 of 2360

SCH0169
Illegal digit in DN.

Action:
Severity: Info.
SCH0170
SNMP trap: No
Wrong number of input fields for prompt STEP.

Action:
Severity: Info.
SCH0171
SNMP trap: No
Step route number out-of-range (0-31).

Action:
Severity: Info.
SCH0172
SNMP trap: No
Invalid step route number/or route number not defined. Dataport, can only step
to similar data route.
Action:
Severity: Info.
SCH0173
SNMP trap: No
IFC type has to be NI-2 in order to configure NI-2 CBC master route.
Action: Input NI-2.
Severity: Minor.
SCH0174
SNMP trap: No
NI-2 CBC Master Route is not defined.

Action: Configure a NI-2 CBC Master Route.
Severity: Minor.
SCH0175
SNMP trap: No
Route is not NI-2 CBC Master Route.

Action: Use NI-2 CBC Master Route number.
Severity: Minor.
SCH0176
SNMP trap: No
Need to specify NI-2 CBC Master Route number.

Action: Input NI-2 CBC Master Route number.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1499 of 2360

SCH0177
NI-2 CBC Master Route has no trunks (channels).

Action: Assign trunks (channels) to NI-2 CBC Master Route.
Severity: Minor.
SCH0178
SNMP trap: No
The MAX value exceeds the number of trunks configured for the NI-2 CBC
Master Route.
Action: Check the maximum number of trunks (channels) configured on NI-2
CBC Master Route.
Severity: Minor.
SCH0179
SNMP trap: No
In the DGCR list ATDN must be an ACD-DN or a DISA-DN.

Action:
Severity: Major.
SCH0180
SNMP trap: No
Wrong number of input fields for prompt EXTN.

Action:
Severity: Info.
SCH0181
SNMP trap: No
Directory number already exists.

Action:
Severity: Info.
SCH0182
SNMP trap: No
Directory number conflicts with existing number.

Action:
Severity: Info.
SCH0183
SNMP trap: No
Shorter directory number already exists.

Action:
Severity: Info.
SCH0184
SNMP trap: No
Loop number conflicts with existing DN loop.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1500 of 2360

SCH0185
Longer directory number already exists.

Action:
Severity: Info.
SCH0186
SNMP trap: No
Station type conflicts with existing DNTYPE.

Action:
Severity: Info.
SCH0187
SNMP trap: No
DN call arrangement conflicts with existing call arrangement.

Action:
Severity: Info.
SCH0188
SNMP trap: No
DNSZ and SSL are mutually exclusive for CIS MFS. (OVL 16)
Action:
Severity: Info.
SCH0189
SNMP trap: No
Either DNSZ or SSL is needed for CIS MFS. (OVL 16)

Action:
Severity: Info.
SCH0190
SNMP trap: No
Wrong number of input fields for prompt ACOD.

Action:
Severity: Info.
SCH0191
SNMP trap: No

Action:
Severity: Info.
SCH0192
SNMP trap: No

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1501 of 2360

SCH0193
Number of DNs defined exceeds MNAC.

Action:
Severity: Info.
SCH0194
SNMP trap: No
Attempt to exceed MNAC.

Action:
Severity: Info.
SCH0195
SNMP trap: No
DID routes not allowed for customer in SATT mode.

Action:
Severity: Info.
SCH0196
SNMP trap: No
A key 0 DN key is required on a mobility set.

Action: Configure key 0 as a DN key.
Severity: Info.
SCH0197
SNMP trap: No
Attendant's primary and secondary TN must be on same card.

Action:
Severity: Info.
SCH0198
SNMP trap: No
DNSZ and SSL are mutually exclusive for CIS MFS.

Action: Set DNSZ = 0 or remove the SSL Table.
Severity: Info.
SCH0199
SNMP trap: No
Either DNSZ or SSL is needed for CIS MFS.

Action: Enable the CIST package and reload the system.
Severity: Info.
SCH0200
SNMP trap: No
Wrong number of input fields for prompt KLS.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1502 of 2360

SCH0201
Number of key/lamp strips out-of-range (1-7).

Action:
Severity: Info.
SCH0202
SNMP trap: No
SNMP trap: No
5 digit dialing.
Action:
Severity: Info.
SCH0203
Input format is incorrect.

Action:
Severity: Info.
SCH0204
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Entry is not defined.

Action:
Severity: Info.
SCH0205
Input out-of-range.
Action:
Severity: Info.
SCH0206
Too many table entries.

Action:
Severity: Info.
SCH0207
OPTM requires a YES response.

Action:
Severity: Info.
SCH0208
SNMP trap: No
Cannot optimize because entry is used.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1503 of 2360

SCH0209
DN out-of-range (LDID/11).
Action:
Severity: Info.
SCH0210
SNMP trap: Yes
Wrong number of input fields for prompt LHK.

Action:
Severity: Info.
SCH0211
SNMP trap: No
Prime directory number out-of-range (0-9 per key/lamp strip).

Action:
Severity: Info.
SCH0212
SNMP trap: No
Input is too long. Input is rejected.

Action: Enter a shorter string for the prompt.
Severity: Info.
SCH0213
SNMP trap: No
Invalid set type for OSN key. Input is rejected.

Action: Define the OSN key on an ARIES 2616 set that is equipped with display.
Severity: Info.
SCH0214
SNMP trap: No
Invalid route type. Input is rejected.

Action: Enter a valid route number.
Severity: Info.
SCH0215
SNMP trap: No
RAN route, RAN trunk, or RAN customer does not exist.

Action:
Severity: Info.
SCH0217
SNMP trap: No
CLS ONDA/ONDD applies only to sets of type MPORTBL.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1504 of 2360

SCH0218
No device number available for History File, 16 devices used.

Action:
Severity: Info.
SCH0219
SNMP trap: No
Temporary History File buffer is full. No new messages will be added.

Action:
Severity: Info.
SCH0220
SNMP trap: No
Wrong number of input fields for prompt RTMB.

Action:
Severity: Info.
SCH0221
SNMP trap: No

Action:
Severity: Info.
SCH0222
SNMP trap: No
Route data block does not exist.

Action:
Severity: Info.
SCH0223
SNMP trap: No
Member number out-of-range (1-126).

Action:
Severity: Info.
SCH0224
SNMP trap: No
Member number already in use.

Action:
Severity: Info.
SCH0225
SNMP trap: No
Route type/station type conflict.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1505 of 2360

SCH0226
Illegal member number.

Action:
Severity: Info.
SCH0227
SNMP trap: No
Repeat count out-of-range (2-126).

Action:
Severity: Info.
SCH0228
SNMP trap: No
DN size is out-of-range (0-7).

Action:
Severity: Info.
SCH0230
SNMP trap: No
Wrong number of input fields for prompt PRDN.

Action:
Severity: Info.
SCH0231
SNMP trap: No
Directory number does not exist.

Action:
Severity: Info.
SCH0232
SNMP trap: No

Action:
Severity: Info.
SCH0233
SNMP trap: No
Directory number conflicts with attendant.

Action:
Severity: Info.
SCH0234
SNMP trap: No
Number conflicts with shorter DN already in translator.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1506 of 2360

SCH0235
Number conflicts with longer DN already in translator.

Action:
Severity: Info.
SCH0236
SNMP trap: No
Number already assigned to another private member.

Action:
Severity: Info.
SCH0238
SNMP trap: No
Directory has conflicting type.

Action:
Severity: Info.
SCH0240
SNMP trap: No
Wrong number of input fields for prompt.

Action:
Severity: Info.
SCH0241
SNMP trap: No

Action:
Severity: Info.
SCH0242
SNMP trap: No

Action:
Severity: Info.
SCH0243
SNMP trap: No
SETN or SL-1 telephone TN associated with lamp field array must be entered.
Action:
Severity: Info.
SCH0244
SNMP trap: No
SNMP trap: No
TN entered is invalid
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1507 of 2360

SCH0245
Both thresholds must be given.

Action:
Severity: Info.
SCH0246
SNMP trap: No
Lower threshold must not exceed upper threshold.

Action:
Severity: Info.
SCH0247
SNMP trap: No
Number of calls out-of-range (0-255).

Action:
Severity: Info.
SCH0248
SNMP trap: No
Waiting time out-of-range (0-511).

Action:
Severity: Info.
SCH0249
SNMP trap: No
Only Y or N allowed for CWBZ.

Action:
Severity: Info.
SCH0250
SNMP trap: No
Wrong number of input fields for prompt HUNT.

Action:
Severity: Info.
SCH0251
SNMP trap: No
Hunt number conflicts with existing number.

Action:
Severity: Info.
SCH0252
SNMP trap: No
Invalid DN type for HUNT.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1508 of 2360

SCH0253
Digit display Class of Service. is required for CLS CDCA and/or the CSD key.
NDD is mutually exclusive.
Action:
Severity: Info.
SCH0254
SNMP trap: No
Hunt number defined for hunting not allowed CLS.

Action:
Severity: Info.
SCH0255
SNMP trap: No
SNMP trap: No
Illegal Hunt DN.

Action:
Severity: Info.
SCH0256
Input is out of range. Input is rejected.

Action: Enter a valid number for the prompt.
Severity: Info.
SCH0257
SNMP trap: No
Input requires the ESA package. Input is rejected.

Action: Contact your technical support group if the system packaging
is incorrect.
Severity: Info.
SCH0258
SNMP trap: No
OSN key must be on a key-lamp pair key. Input is rejected.

Action: Define the OSN key on a key-lamp pair key.
Severity: Info.
SCH0259
SNMP trap: No
Undefined route. Input is rejected.

Action: Define the route first.
Severity: Info.
SCH0260
SNMP trap: No
Wrong number of input fields for prompt NITE, ATDN.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1509 of 2360

SCH0261
NITE, ATDN, MNDN number conflicts with existing number.

Action:
Severity: Info.
SCH0262
SNMP trap: No
NITE, ATDN, MNDN number conflicts with shorter DN.

Action:
Severity: Info.
SCH0263
SNMP trap: No
Either the NITE, ATDN, MNDN number conflicts with a longer DN, or the DN
is not defined.
Action:
Severity: Info.
SCH0264
SNMP trap: No
ATDN: null input not permitted.

Action:
Severity: Info.
SCH0265
SNMP trap: No
SNMP trap: No
DN is not defined.
Action:
Severity: Info.
SCH0266
RLDN: number conflicts with existing number.

Action:
Severity: Info.
SCH0268
SNMP trap: No
Two or more non-zero digits are prompted.

Action:
Severity: Info.
SCH0270
SNMP trap: No
Wrong number of input fields for prompt TYPE.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1510 of 2360

SCH0271

Action:
Severity: Info.
SCH0272
SNMP trap: No
Number of inputs CFLP.

Action:
Severity: Info.
SCH0273
SNMP trap: No
SNMP trap: No
SNMP trap: No
Not a conference loop.

Action:
Severity: Info.
SCH0274
Null input not allowed.

Action:
Severity: Info.
SCH0275
Loop number out-of-range 0-159.

Action:
Severity: Info.
SCH0276
SNMP trap: No
Attempt to assign 2 trunks to one conference.

Action:
Severity: Info.
SCH0278
SNMP trap: No
The DN entered is not a valid OSDN. Input is rejected.

Action: Enter a valid OSDN.
Severity: Info.
SCH0279
SNMP trap: No
Input requires the ESA_SUPP package. Input is rejected.

is incorrect.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1511 of 2360

SCH0280
Wrong number of input fields for prompt ICOG.

Action:
Severity: Info.
SCH0281
SNMP trap: No

Action:
Severity: Info.
SCH0282
SNMP trap: No
I/O device cannot be an OSN user due to user conflict. Input is rejected.
Action: Remove all the conflicting users before configuring the I/O device
as an OSN user.
Severity: Info.
SCH0283
SNMP trap: No
Input requires the ESA_CLMP package. Input is rejected.

Action: Remove all the conflicting users before configuring the I/O device
as an OSN user.
Severity: Info.
SCH0284
SNMP trap: No
ESA database must be removed before the customer database can be

removed.
Action: Remove the customer's ESA database before removing the
customer database.
Severity: Info.
SCH0285
SNMP trap: No
VCC DN should be single appearance on SL-1 telephone.

Action:
Severity: Info.
SCH0290
SNMP trap: No
Wrong number of input fields for prompt TGAR.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1512 of 2360

SCH0291
Trunk group access restriction out-of-range (0-15).

Action:
Severity: Info.
SCH0298
SNMP trap: No
JAPAN TTC package not equipped

Action:
Severity: Info.
SCH0299
SNMP trap: No
LD 16 - Invalid Privacy Override Indicator entered for DTPO or DPPO prompt.

Action:
Severity: Info.
SCH0300
SNMP trap: No
Wrong number of input fields for prompt RNPG.

Action:
Severity: Info.
SCH0301
SNMP trap: No
Ringing number pickup group number out-of-range (0-255).

Action:
Severity: Info.
SCH0302
SNMP trap: No
Input requires CNUMB package.

is incorrect.
Severity: Info.
SCH0303
SNMP trap: No
Input requires CNAME package.

is incorrect.
Severity: Info.
SCH0304
SNMP trap: No
Input requires either the CNUMB or the CNAME package.

is incorrect.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1513 of 2360

SCH0305
Invalid input for a DIG set.

Action: Enter a valid input.
Severity: Info.
SCH0307
SNMP trap: No

Action:
Severity: Info.
SCH0308
SNMP trap: No
RPE must be removed from data block before OUT or CHG to terminal loop.
Action:
Severity: Info.
SCH0310
SNMP trap: No
Wrong number of input fields for prompt SIGL.

Action:
Severity: Info.
SCH0311
SNMP trap: No

Action: Refer to the Admin Guide for correct response to this mnemonic.
Severity: Info.
SCH0312
SNMP trap: No
Unacceptable signaling for trunk type.

Action:
Severity: Info.
SCH0313
SNMP trap: No
Wrong number of input fields for prompt ANTK.

Action:
Severity: Info.
SCH0314
SNMP trap: No
SNMP trap: No
Invalid number.
Action:
Severity: Info.
System Messages
Page 1514 of 2360

SCH0315
CED (LD 35) cannot be deleted from midnight routines for SL-1 MS.
Action:
Severity: Info.
SCH0320
SNMP trap: No
Wrong number of input fields for prompt STAR.

Action:
Severity: Info.
SCH0321
SNMP trap: No
Only applies to RLR trunks.

Action:
Severity: Info.
SCH0324
SNMP trap: No
MSDL block for the DTI loop cannot be allocated. System memory could be
low.
Action: Out the DTI loop, free some additional data blocks and try again.
Severity: Major.
SCH0330
SNMP trap: No
Wrong number of input fields for prompt SUPN.

Action:
Severity: Info.
SCH0334
SNMP trap: No
Incompatible units have been provisioned on the same linecard.

Action: Enter the service change data again.
Severity: Minor.
SCH0335
SNMP trap: No
Wrong number of input fields for prompt CMF.

Action:
Severity: Info.
SCH0336
SNMP trap: No
A Service route is needed for routing incoming public network calls.

Action: Input a service route number.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1515 of 2360

SCH0337
Has to be a NI-2 CBC service route with TYPE=COT/DID and SRVC=0.

Action:
Severity: Major.
SCH0338
SNMP trap: No
LND is not defined for this customer.

Action:
Severity: Info.
SCH0339
SNMP trap: No
SNA cannot be specified without LNA.

Action:
Severity: Info.
SCH0340
SNMP trap: No
Class of Service is not allowed for this TRK type.

Action: TIE trunks must be IMM start.
Severity: Info.
SCH0341
SNMP trap: No

Action:
Severity: Info.
SCH0342
SNMP trap: No
A group number is not defined for PUA.

Action:
Severity: Info.
SCH0343
SNMP trap: No
VNL cls is acceptable with EAM signaling types only.

Action: Set CLS to TRC or NTC.
Severity: Info.
SCH0344
SNMP trap: No
FNA is not allowed unless hunting is defined.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1516 of 2360

SCH0345
Class of Service not allowed.

Action:
Severity: Info.
SCH0346
SNMP trap: No
DTN not valid for this trunk type.

Action:
Severity: Info.
SCH0347
SNMP trap: No
MFR valid only for CAMA, FGD and M911 trunks.

Action:
Severity: Info.
SCH0348
SNMP trap: No
CAMA (DIP) not valid with route signaling specified.

Action:
Severity: Info.
SCH0349
SNMP trap: No
HTA is not allowed unless Hunting is defined.

Action: HNT DN and EHT DN must be defined for HTA
Severity: Info.
SCH0350
SNMP trap: No
Wrong number of input fields for prompt ANUM.

Action:
Severity: Info.
SCH0351
SNMP trap: No
Attendant number out-of-range (1-15).

Action:
Severity: Info.
SCH0352
SNMP trap: No
Attendant number already in use.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1517 of 2360

SCH0353
Attendant DN must be defined.

Action:
Severity: Info.
SCH0355
SNMP trap: No

Action:
Severity: Info.
SCH0356
SNMP trap: No
CFW or ADL DN size out-of-range.

Action: Enter DN length of 4 -31 digits.
Severity: Info.
SCH0358
SNMP trap: No
Input is not PAG trunk group access code.

Action:
Severity: Info.
SCH0359
SNMP trap: No
ADL/CFW number exceeds specified length.

Action: Enter ADL/CFW DN within configured ADL/CF
Severity: Info.
SCH0360
SNMP trap: No
Wrong number of input fields for prompt KEY.

Action:
Severity: Info.
SCH0361
SNMP trap: No
Key number is not valid on this set type

Action:
Severity: Info.
SCH0362
SNMP trap: No

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1518 of 2360

SCH0363
Key function requires lamp key.

Action:
Severity: Info.
SCH0364
SNMP trap: No
Key function requires 5 state lamp: 0 for busy verify.

Action:
Severity: Info.
SCH0365
SNMP trap: No
Speed Call List number out-of-range (0-253).

Action:
Severity: Info.
SCH0366
SNMP trap: No
Speed Call List does not exist, or Hot Line list is not defined for TYPE = HTL.
Action:
Severity: Info.
SCH0367
SNMP trap: No
Member number out-of-range (0-127).

Action:
Severity: Info.
SCH0368
SNMP trap: No
No RNPU group defined for RNP key.

Action:
Severity: Info.
SCH0369
SNMP trap: No
Function conflicts with existing call arrangement.

Action:
Severity: Info.
SCH0370
SNMP trap: No
Directory number conflicts with DIAL 0.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1519 of 2360

SCH0371
Shorter directory number already exists.

Action:
Severity: Info.
SCH0372
SNMP trap: No
Function not allowed on MIXED directory number.

Action:
Severity: Info.
SCH0373
SNMP trap: No
Loop number does not match DN loop. Multiple loop DN restricted in LD 17.
Creation or expansion restricted.
Action:
Severity: Info.
SCH0374
SNMP trap: No
Longer directory number already exists.

Action:
Severity: Info.
SCH0375
SNMP trap: No
DN type conflicts with input DN type.

Action:
Severity: Info.
SCH0376
SNMP trap: No
Function not allowed on private CO line.

Action:
Severity: Info.
SCH0377
SNMP trap: No
VCC or SIG not allowed on multiple appearance DN.

Action:
Severity: Info.
SCH0378
SNMP trap: No
DN already has maximum number (30) of stations attached.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1520 of 2360

SCH0379
Group number out-of-range (0-99).

Action:
Severity: Info.
SCH0380
SNMP trap: No
AWU requires digit display.

Action:
Severity: Info.
SCH0381
SNMP trap: No
Absorption digit or TDG entry out-of-range (0-9).

Action:
Severity: Info.
SCH0382
SNMP trap: No
Key 0 or key 1 may not be used for AWU.

Action:
Severity: Info.
SCH0383
SNMP trap: No
Number out-of-range (0-3).

Action:
Severity: Info.
SCH0384
SNMP trap: No
Incorrect number of digits (0-999).

Action:
Severity: Info.
SCH0385
SNMP trap: No

Action:
Severity: Info.
SCH0386
SNMP trap: No
Number is out-of-range (0-2).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1521 of 2360

SCH0389
Incorrect number of input fields.

Severity: Info.
SCH0390
SNMP trap: No
Invalid input for new CRB.

Action:
Severity: Info.
SCH0391
SNMP trap: No
Code restriction number out-of-range (200-999).

Action:
Severity: Info.
SCH0392
SNMP trap: No
Timer not required in this route.

Action:
Severity: Info.
SCH0393
SNMP trap: No
Unable to match input with stored mnemonics.

Action: Choose either NO, B1, B2 or B3.
Severity: Info.
SCH0395
SNMP trap: No
Input overflow. Number greater than 16383.

Action:
Severity: Info.
SCH0397
SNMP trap: No
Input out-of-range (0-512) (dial delay option).

Action:
Severity: Info.
SCH0398
SNMP trap: No

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1522 of 2360

SCH0400
Wrong number of input fields for prompt SPRE.

Action:
Severity: Info.
SCH0401
SNMP trap: No

Action:
Severity: Info.
SCH0402
SNMP trap: No

Action:
Severity: Info.
SCH0403
SNMP trap: No

Action:
Severity: Info.
SCH0404
SNMP trap: No

Action:
Severity: Info.
SCH0405
SNMP trap: No
SNMP trap: No
Wrong parameter type.

Action:
Severity: Info.
SCH0406
Ran route (or trunk) does not exist.

Action:
Severity: Info.
SCH0407
SNMP trap: No

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1523 of 2360

SCH0408

Action:
Severity: Info.
SCH0409
SNMP trap: No
Parameter out-of-range (0-30).

Action:
Severity: Info.
SCH0410
SNMP trap: No
SNMP trap: No
Not equipped for RAN.

Action:
Severity: Info.
SCH0411

Action:
Severity: Info.
SCH0412
SNMP trap: No

Action:
Severity: Info.
SCH0413
SNMP trap: No

Action:
Severity: Info.
SCH0416
SNMP trap: No

Action:
Severity: Info.
SCH0417
SNMP trap: No
SNMP trap: No
Illegal input number.

Action:
Severity: Info.
System Messages
Page 1524 of 2360

SCH0418
Illegal input number.

Action:
Severity: Info.
SCH0419
SNMP trap: No

Action:
Severity: Info.
SCH0420
SNMP trap: No

Action:
Severity: Info.
SCH0421
SNMP trap: No
SNMP trap: No
Timer out-of-range.
Action:
Severity: Info.
SCH0422

Action: Input expects one parameter.
Severity: Info.
SCH0425
SNMP trap: No

Action:
Severity: Info.
SCH0426
SNMP trap: No

Action:
Severity: Info.
SCH0427
SNMP trap: No
Parameters out-of-range (0-7) or (0-15).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1525 of 2360

SCH0428
This port is not a CDR device.

Action: LD 17 should be used to define the proper device.
Severity: Info.
SCH0429
SNMP trap: No
SNMP trap: No
Illegal number of digits.

Action:
Severity: Info.
SCH0430
Invalid directory number entered for ACD NCFW or IFDN.

Action: Try another DN.
Severity: Info.
SCH0431
SNMP trap: No
ICI appearance out-of-range (0-9 or 0-19).

Action:
Severity: Info.
SCH0432
SNMP trap: No
SNMP trap: No
Invalid ICI keyword.

Action:
Severity: Info.
SCH0433
CAT is out-of-range (0-99).

Action:
Severity: Info.
SCH0434
SNMP trap: No
SNMP trap: No
SNMP trap: No
ID is out-of-range (0-9).
Action:
Severity: Info.
SCH0435
Not equipped for ANI.

Action:
Severity: Info.
System Messages
Page 1526 of 2360

SCH0436

Action:
Severity: Info.
SCH0437
SNMP trap: No
Unable to identify parameter to given prompt.

Action:
Severity: Info.
SCH0438
SNMP trap: No
M3C allowed only if signaling is NT5.

Action:
Severity: Info.
SCH0439
SNMP trap: No
ICOG not valid for this trunk type.

Action:
Severity: Info.
SCH0440
SNMP trap: No
Wrong number of input fields for prompt LSNO.

Action:
Severity: Info.
SCH0441
SNMP trap: No
List number out-of-range, or the number of speed call lists is out-of-range.

Prior to Release 17 the range is 0-253. With Release 17 and later, the range
is 0-8191.
Action:
Severity: Info.
SCH0442
SNMP trap: No
List number already exists.

Action:
Severity: Info.
SCH0443
SNMP trap: No
SNMP trap: No
List does not exist.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1527 of 2360

SCH0444
Route number for ICI does not exist, or route contains no members.
Action:
Severity: Info.
SCH0445
SNMP trap: No
The group member number is out-of-range.

Action: Enter 0-5 for Option 11. Enter 0-19 for all other machines.
Severity: Info.
SCH0446
SNMP trap: No
DN size is out-of-range (4-31).

Action:
Severity: Info.
SCH0448
SNMP trap: No
New DN size is smaller than current size.

Action:
Severity: Info.
SCH0449
SNMP trap: No
List cannot be service changed while active, try later.

Action:
Severity: Info.
SCH0450
SNMP trap: No
Wrong number of input fields for prompt SIZE.

Action:
Severity: Info.
SCH0451
SNMP trap: No
Speed call (Group Hunt) list size illegal [1-1000 (1-96)].

Action:
Severity: Info.
SCH0453
SNMP trap: No
New list size is smaller than current size.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1528 of 2360

SCH0454
Customer list for group n does not exist.

Action:
Severity: Info.
SCH0455
SNMP trap: No
SNMP trap: No
SNMP trap: No
Group is not defined.

Action:
Severity: Info.
SCH0456
Group already exists.

Action:
Severity: Info.
SCH0457
Wrong number of input fields for GRNO.

Action:
Severity: Info.
SCH0458
SNMP trap: No

Action:
Severity: Info.
SCH0459
SNMP trap: No
Group member does not exist.

Action:
Severity: Info.
SCH0460
SNMP trap: No
Wrong number of fields in input.

Action:
Severity: Info.
SCH0461
SNMP trap: No
Key number out-of-range (0-size).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1529 of 2360

SCH0463
Attempted to enter a RAN route that was not previously defined as AWR in the
AUX_CUST_DATA_BLOCK.
Action:
Severity: Info.
SCH0464
SNMP trap: No
RAN or Conference loop cannot be removed or changed while Wake Up calls

are in progress.
Action:
Severity: Info.
SCH0465
SNMP trap: No
Wrong number in input field for AWU.

Action:
Severity: Info.
SCH0466
SNMP trap: No
Unable to match input with stored mnemonics (YES/NO, {CR}, X).

Action:
Severity: Info.
SCH0467
SNMP trap: No
RANF and RAN1 must be defined for all cases.

Action: RAN2 must be defined if R2BN is different from R2ED.
Severity: Info.
SCH0469
SNMP trap: No
Second RAN hr/min value out-of-range.

Action:
Severity: Info.
SCH0470
SNMP trap: No
Wrong number of fields for 2nd RAN (begin or end).

Action:
Severity: Info.
SCH0471
SNMP trap: No

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1530 of 2360

SCH0472

Action:
Severity: Info.
SCH0473
SNMP trap: No
SL-1 telephones cannot be moved between loops.

Action:
Severity: Info.
SCH0474
SNMP trap: No
Sets cannot be moved between loops.

Action:
Severity: Info.
SCH0475
SNMP trap: No
Trunk units cannot be moved between loops.

Action:
Severity: Info.
SCH0476
SNMP trap: No
Cannot move a unit from one loop to another.

Action:
Severity: Info.
SCH0477
SNMP trap: No
Both values must be given.

Action:
Severity: Info.
SCH0478
SNMP trap: No
Lower value must not exceed upper value.

Action:
Severity: Info.
SCH0479
SNMP trap: No
Flash timer must be less than PBX_DISC_TO.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1531 of 2360

SCH0480
Timer value out-of-range (45-768).

Action:
Severity: Info.
SCH0481
SNMP trap: No

Action:
Severity: Info.
SCH0482
SNMP trap: No
Route data block already exists.

Action:
Severity: Info.
SCH0483
SNMP trap: No
Code restriction block does not exist.

Action:
Severity: Info.
SCH0484
SNMP trap: No
Code restriction block already exists.

Action:
Severity: Info.
SCH0485
SNMP trap: No
No ROA is provided on this RICI key.

Action:
Severity: Info.
SCH0486
SNMP trap: No
Wrong number of input fields for prompt PHDT.

Action:
Severity: Info.
SCH0487
SNMP trap: No
Input field is out-of-range.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1532 of 2360

SCH0488
ROA package not equipped.

Action:
Severity: Info.
SCH0489
SNMP trap: No
Second RAN time out-of-range (2-2044).

Action:
Severity: Info.
SCH0490
SNMP trap: No
Wrong number of input fields for prompt TOCU.

Action:
Severity: Info.
SCH0492
SNMP trap: No
Customer data block already exists.

Action:
Severity: Info.
SCH0493
SNMP trap: No
Customer number out-of-range.

Action:
Severity: Info.
SCH0494
SNMP trap: No
NFCR tree already exists.

Action:
Severity: Info.
SCH0495
SNMP trap: No
Null not allowed for NFCR tree number except for PRT.
Action:
Severity: Info.
SCH0496
SNMP trap: No
NFCR tree number is outside range (above MAXT).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1533 of 2360

SCH0497
NFCR cannot be active for RLS.

Action:
Severity: Info.
SCH0498
SNMP trap: No
Entered digit too large for NFCR count field.

Action:
Severity: Info.
SCH0499
SNMP trap: No
Another parameter expected for FRL/CRCS prompt.

Action:
Severity: Info.
SCH0501
SNMP trap: No
Speed Call list number out-of-range (0-254).

Action:
Severity: Info.
SCH0502
SNMP trap: No
Speed Call list already exists.

Action:
Severity: Info.
SCH0503
SNMP trap: No
Wrong number of input fields for TOGR.

Action:
Severity: Info.
SCH0504
SNMP trap: No
Group Call list number out-of-range.

Action:
Severity: Info.
SCH0505
SNMP trap: No
This group may already be defined as a SL-1 GRC key.

Action: Check SL-1 sets for this customer.
Severity: Info.
SNMP trap: No
System Messages
Page 1534 of 2360

SCH0506
Maximum of 24 characters allowed for the EBLN name.

Action:
Severity: Info.
SCH0507
SNMP trap: No
Invalid character entered. Only ASCII characters with hexadecimal values

between H.20 and H.7E (inclusive) are supported in the string input. (For
example, alphanumeric or punctuation characters.)
Action:
Severity: Info.
SCH0508
SNMP trap: No
Invalid character entered. Only ASCII characters with hexadecimal values

between H.20 and H.7F (inclusive) or between H.A0 and H.FF (inclusive) are
supported.
Action:
Severity: Info.
SCH0509
SNMP trap: No
Input format is incorrect. Only ASCII characters with hexadecimal values

between H.20 and H.7F (inclusive) or between H.A0 and H.FF (inclusive) are
supported.
Action: Enter 1 character or its hexadecimal value.
Severity: Info.
SCH0510
SNMP trap: No

Action:
Severity: Info.
SCH0511
SNMP trap: No
Increment out-of-range.
Action: Up to Release 15, enter 0-15 or 0-7 for SST. For Release 16 and later,
enter 0-31, or 0-7 for SST.
Severity: Info.
SCH0512
SNMP trap: No
Decrement out-of-range.
Action: Up to Release 15, enter 0-15 or 0-7 for SST. For Release 16 and later,
enter 0-31, or 0-7 for SST.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1535 of 2360

SCH0513
Minimum waiting time out-of-range (0-127).

Action:
Severity: Info.
SCH0514
SNMP trap: No
The loop does not exist in LD 73.

Action:
Severity: Info.
SCH0515
SNMP trap: No

Action:
Severity: Info.
SCH0516
SNMP trap: No
Wrong type of parameters.

Action:
Severity: Info.
SCH0517
SNMP trap: No
Parameters out-of-range (1-15).

Action:
Severity: Info.
SCH0518
SNMP trap: No
SNMP trap: No
Not equipped for RAN.

Action:
Severity: Info.
SCH0519
Response for RTYP must be AUD.

Action:
Severity: Info.
SCH0520
SNMP trap: No
NI-2 basic call only supports COT/DID route.

When CBCR = NO and IFC = NI2, route type has to be either COT or DID,
TKTP = COT/DID.
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1536 of 2360

SCH0521
Unable to match input field with stored mnemonics. The RCAP prompt in
overlay 16 has been answered NDS when QSUr QSIG GF are not accessible
or with an inappropriate interface configured (e.g. SL 1).
Action: Reconfigure accordingly.
Severity: Info.
SCH0522
SNMP trap: No
Input for DNRO/DNRI out-of-range (0-4).

Action: Re-enter in the range (0-4).
Severity:
SCH0523
SNMP trap: No
Wrong number of input fields or digits for PWD number.

Action:
Severity: Info.
SCH0524
SNMP trap: No
Warning: The active password will be changed.

Action:
Severity: Info.
SCH0525
SNMP trap: No
Illegally entered password.

Action: Make sure you enter uppercase letters. When using lower case letters,
use at least 4 numbers in the password.
Severity: Info.
SCH0526
SNMP trap: No
Password does not match stored password.

Action:
Severity: Info.
SCH0527
SNMP trap: No
Program number does not exist.

Action:
Severity: Info.
SCH0528
SNMP trap: No
Attempt to remove an unlisted program or add a listed program.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1537 of 2360

SCH0529
Attempt to remove an unlisted customer or add a listed customer.

Action:
Severity: Info.
SCH0533
SNMP trap: No
The AML application object cannot be created.

Action:
Severity: Info.
SCH0534
SNMP trap: No
The AML application object cannot be removed.

Action:
Severity: Info.
SCH0535
SNMP trap: No
Attempted to remove non-existing loop or add existing loop.

Action:
Severity: Info.
SCH0537
SNMP trap: No
Memory modules 0 to 1 are required.

Action:
Severity: Info.
SCH0539
SNMP trap: No
Module number already defined as spare.

Action:
Severity: Info.
SCH0541
SNMP trap: No
Attempt to add memory already in system.

Action:
Severity: Info.
SCH0542
SNMP trap: No
Attempt to remove memory not in system.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1538 of 2360

SCH0543
Illegal module number for spare.

Action:
Severity: Info.
SCH0544
SNMP trap: No
Module does not exist on this CPU bus.

Action:
Severity: Info.
SCH0545
SNMP trap: No

Action:
Severity: Info.
SCH0547
SNMP trap: No

Action:
Severity: Info.
SCH0548
SNMP trap: No
Messages already suppressed.

Action:
Severity: Info.
SCH0549
SNMP trap: No
Messages already allowed.

Action:
Severity: Info.
SCH0550
SNMP trap: No

Action:
Severity: Info.
SCH0551
SNMP trap: No
Program number out-of-range (30-45).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1539 of 2360

SCH0552
Attempt to remove multi-group extender.

Action:
Severity: Info.
SCH0553
SNMP trap: No
System ID number 0-999 out-of-range.

Action:
Severity: Info.
SCH0555
SNMP trap: No
Time and date package must be equipped.

Action:
Severity: Info.
SCH0556
SNMP trap: No
MMCS and IVR packages must be equipped.

Action:
Severity: Info.
SCH0557
SNMP trap: No
VPA class of service allowed on for 2616 set.

Action:
Severity: Info.
SCH0558
SNMP trap: No
The card has to be manually disabled before the user can issue the MOV
command.
Action: Manually disable the card in LD 96 before re-issuing the MOV command.
Severity: Warning.
SCH0560
SNMP trap: No

Action:
Severity: Info.
SCH0561
SNMP trap: No

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1540 of 2360

SCH0562
Duplicate defined loop.

Action:
Severity: Info.
SCH0563
SNMP trap: No
Loop must be disabled before removing.

Action:
Severity: Info.
SCH0564
SNMP trap: No
Attempt to remove a loop with data still on it.

Action:
Severity: Info.
SCH0565
SNMP trap: No
Group number is out-of-range: 0-4, 15.

Action:
Severity: Info.
SCH0566
SNMP trap: No

Action:
Severity: Info.
SCH0567
SNMP trap: No
Unable to match input to stored mnemonics.

Action:
Severity: Info.
SCH0568
SNMP trap: No
Illegal extender arrangements.

Action:
Severity: Info.
SCH0569
SNMP trap: No
Remove/addition of loop during same Overlay pass not allowed.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1541 of 2360

SCH0570
Incorrect number of input fields (3).

Action:
Severity: Info.
SCH0571
SNMP trap: No
First field was not one of (NEW, OUT, CHG).

Action:
Severity: Info.
SCH0572
SNMP trap: No
Second field was not one of (PRT, TTY, TAP) for machines other than SL-1
MS.
Action:
Severity: Info.
SCH0573
SNMP trap: No
Device number out-of-range.

Action:
Severity: Info.
SCH0574
SNMP trap: No
Device specified does not exist.

Action:
Severity: Info.
SCH0575
SNMP trap: No
Device must be disabled before removing or changing. This is applicable on

all phases.
Action:
Severity: Info.
SCH0576
SNMP trap: No
SNMP trap: No
Device already exists.

Action:
Severity: Info.
SCH0577
Device specified is not a printer.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1542 of 2360

SCH0578
Device does not exist.

Action: Action
Severity: Info.
SCH0579
SNMP trap: No
Unable to match input with stored mnemonics. Mnemonic is invalid.

Action:
Severity: Info.
SCH0580
SNMP trap: No
Mnemonic CDL is not acceptable if other users are specified.

Action:
Severity: Info.
SCH0581
SNMP trap: No
Device must be enabled to permit CDL change.

Action:
Severity: Info.
SCH0582
SNMP trap: No
SNMP trap: No
Input out-of-range.
Action:
Severity: Info.
SCH0583
Cannot remove this ACD terminal. One of the following is true for this TTY: It
has been defined as an ACD printer for ACD C reports for a customer, or it has
been defined as an input/output device for ACD queue status displays.
Action: No changes are allowed until a TTY is no longer defined as either of the
above.
Severity: Info.
SCH0584
SNMP trap: No
Mnemonic ACD is not acceptable if other users are specified.

Action:
Severity: Info.
SCH0585
SNMP trap: No
Cannot assign own terminal to ACD.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1543 of 2360

SCH0586
Customer does not exist.

Action:
Severity: Info.
SCH0587
SNMP trap: No
Input is not YES or NO for the CCB and CCBA prompt in the RDB.
Action:
Severity: Info.
SCH0588
SNMP trap: No
ACD terminal cannot be both a senior supervisor and printer.

Action:
Severity: Info.
SCH0589
SNMP trap: No
Customer has more than one senior supervisor/load manager.

Action:
Severity: Info.
SCH0590
SNMP trap: No
SNMP trap: No
Package not equipped.

Action:
Severity: Info.
SCH0591
Loop number increment out-of-range (0-159).

Action:
Severity: Info.
SCH0592
SNMP trap: No
Directory number increment out-of-range (4 digits).

Action:
Severity: Info.
SCH0593
SNMP trap: No
Member number increment out-of-range (0-126).

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1544 of 2360

SCH0594
Unable to recover old TN block.

Action:
Severity: Info.
SCH0595
SNMP trap: No
Unable to remove TN block.

Action:
Severity: Info.
SCH0596
SNMP trap: No
PMS user type coexists with BGD only.

Action:
Severity: Info.
SCH0597
SNMP trap: No
No new messages were added to history file since last printing.

Action:
Severity: Info.
SCH0598
SNMP trap: No
SNMP trap: No
History File is empty.

Action:
Severity: Info.
SCH0599
Invalid user. Cannot access History File.

Action:
Severity: Info.
SCH0600
SNMP trap: No
SNMP trap: No
Illegal input character.

Action:
Severity: Info.
SCH0601
Warning: The system may Initialize, and data corruption may occur. Out of
unprotected data store.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1545 of 2360

SCH0602
Out of Protected Data (PDATA) storage.

Action: Increase memory before doing any service change. (A sysload can
reduce memory fragmentation and increase usable protected memory.)
Severity: Info.
SCH0603
SNMP trap: No
Warning: Unprotected data store below safety limit.

Action: Increase memory before making any service change.
Severity: Info.
SCH0604
SNMP trap: No
Warning: Protected data store below safety limit.

Action: Increase memory before making any service change.
Severity: Info.
SCH0606
SNMP trap: No
LND option package restricted.

Action:
Severity: Info.
SCH0607
SNMP trap: No
Remove DTI clock controller loop first.

Action:
Severity: Info.
SCH0609
SNMP trap: No
The response NI22N is not allowed if the MMCS or Master Mode or NI-2
packages are not equipped. IFC is reprompted.
Action: Equip packages 309, 317 or 291 and re-load.
Severity: Info.
SCH0610
SNMP trap: No
Multi-customer option package restrict.

Action:
Severity: Info.
SCH0611
SNMP trap: No
Option package not equipped.

Action: Enable System Speed Call package.
Severity: Info.
SNMP trap: No
System Messages
Page 1546 of 2360

SCH0612
AIOD package restricted.

Action:
Severity: Info.
SCH0613
SNMP trap: No
{CR} is an invalid input for this prompt.

Action:
Severity: Info.
SCH0614
SNMP trap: No
Use OUT to remove all users.

Action:
Severity: Info.
SCH0615
SNMP trap: No
DES input out-of-range (6-digit alphanumeric).

Action:
Severity: Info.
SCH0616
SNMP trap: No
DES input contains an invalid character.

Action:
Severity: Info.
SCH0617
SNMP trap: No
DES must be entered if LD 10 or LD 11 is new.

Action:
Severity: Info.
SCH0618
SNMP trap: No
SNMP trap: No
No system date exists.

Action:
Severity: Info.
SCH0620
Input number out-of-range. (Overlay 15)

Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1547 of 2360

SCH0621
Service change not allowed from maintenance set.

Action:
Severity: Info.
SCH0622
SNMP trap: No
Wrong number of parameters given.

Action:
Severity: Info.
SCH0623
SNMP trap: No
Not enough internal workspace to process this request.

Action:
Severity: Info.
SCH0624
SNMP trap: No
Not equipped for MUSIC.

Action:
Severity: Info.
SCH0625
SNMP trap: No
Route specified is not a MUSIC route.

Action:
Severity: Info.
SCH0626
SNMP trap: No
Key assignment conflicts with CLS (LND or SND).

Action:
Severity: Info.
SCH0630
SNMP trap: No

Action:
Severity: Info.
SCH0631
SNMP trap: No
SNMP trap: No
Invalid command.
Action:
Severity: Info.
System Messages
Page 1548 of 2360

SCH0632
System conversion error message.

Action: Contact the manufacturer.
Severity: Info.
SCH0633
SNMP trap: No

Severity: Info.
SCH0634
SNMP trap: No

Severity: Info.
SCH0635
SNMP trap: No

Severity: Info.
SCH0636
SNMP trap: No

Severity: Info.
SCH0637
SNMP trap: No

Severity: Info.
SCH0640
SNMP trap: No

Action:
Severity: Info.
SCH0643
SNMP trap: No
Loop shelf not defined in the configuration.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1549 of 2360

SCH0645

Action:
Severity: Info.
SCH0647
SNMP trap: No
Shelf number out-of-range (0-3).

Action:
Severity: Info.
SCH0648
SNMP trap: No
Card number out-of-range (1-10).

Action:
Severity: Info.
SCH0649
SNMP trap: No
Attempt to move card more than once.

Action:
Severity: Info.
SCH0650
SNMP trap: No
Mnemonic TO not entered.

Action:
Severity: Info.
SCH0651
SNMP trap: No
Message Waiting package not equipped.

Action:
Severity: Info.
SCH0652
SNMP trap: No
MCD key must be assigned to key 0.

Action:
Severity: Info.
SCH0653
SNMP trap: No
Key 0 must be defined as MCD to assign MIK/MCK.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1550 of 2360

SCH0654
MIK/MCK cannot be assigned to key 0.

Action:
Severity: Info.
SCH0655
SNMP trap: No
SNMP trap: No
MWK cannot be key 0.

Action:
Severity: Info.
SCH0656
MWK cannot be assigned because telephone has MCD key.

Action:
Severity: Info.
SCH0657
SNMP trap: No
Message center option must be enabled in LD 15.

Action:
Severity: Info.
SCH0658
SNMP trap: No
Invalid DN type for MC DN.

Action:
Severity: Info.
SCH0659
SNMP trap: No
MWK key already defined for this station.

Action:
Severity: Info.
SCH0660
SNMP trap: No
Group DND package restriction.

Action:
Severity: Info.
SCH0661
SNMP trap: No

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1551 of 2360

SCH0663

Action:
Severity: Info.
SCH0664
SNMP trap: No
SNMP trap: No
SNMP trap: No
Group does not exist.

Action:
Severity: Info.
SCH0665
Group already exists.

Action:
Severity: Info.
SCH0666
The loop entered is not a DTI/PRI loop (LD 73).

Action:
Severity:
SCH0668
SNMP trap: No
Group already has maximum number of items (127).

Action:
Severity: Info.
SCH0669
SNMP trap: No
Group contains secondary group.

Action:
Severity: Info.
SCH0670
SNMP trap: No
SNMP trap: No
SNMP trap: No
DN does not exist.

Action:
Severity: Info.
SCH0671
DN is not a station.
Action:
Severity: Info.
System Messages
Page 1552 of 2360

SCH0672
Sub-group does not exist.

Action:
Severity: Info.
SCH0673
SNMP trap: No
DN or sub-group to be removed is not found.

Action:
Severity: Info.
SCH0674
SNMP trap: No
Group cannot contain itself as a member.

Action:
Severity: Info.
SCH0675
SNMP trap: No
Group cannot contain itself as a member.

Action:
Severity: Info.
SCH0676
SNMP trap: No
Group cannot be it's own subgroup.

Action:
Severity: Info.
SCH0677
SNMP trap: No
FWA package #338 is not equipped.

Action:
Severity:
SCH0678
SNMP trap: No
CLS DIP not allowed for Remote Subscriber Set.

Action:
Severity:
SCH0679
SNMP trap: No
Missing DPI L/W from disk.

Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1553 of 2360

SCH0680
Invalid terminal type for a DMSX superloop.

Action:
Severity:
SCH0681
SNMP trap: No
Invalid response to REQ prompt.

Action:
Severity: Info.
SCH0682
SNMP trap: No
No customer has route selection for ANI yet.

Action:
Severity: Info.
SCH0683
SNMP trap: No
Protected memory is running low.

Action:
Severity: Info.
SCH0684
SNMP trap: No
The response to a TYPE prompt must be RSA.

Action:
Severity: Info.
SCH0685
SNMP trap: No
CUST may be null only when request is PRT.

Action:
Severity: Info.
SCH0686
SNMP trap: No
Response to CUST out-of-range 0-31.

Action:
Severity: Info.
SCH0687
SNMP trap: No
NEW request made for a customer who already has RS-ANI.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1554 of 2360

SCH0688
Specified customer does not have RS-ANI.

Action:
Severity: Info.
SCH0689
SNMP trap: No
RS-ANI access code (RSAC) may not begin with digit 0.

Action:
Severity: Info.
SCH0690
SNMP trap: No
Given RSAC conflicts with another existing access code.

Action:
Severity: Info.
SCH0691
SNMP trap: No
RSAC response null during a NEW request.

Action:
Severity: Info.
SCH0692
SNMP trap: No
Invalid null response to 0-RT, 0+RT, 1RT, or CORT prompt.

Action:
Severity: Info.
SCH0693
SNMP trap: No
No such trunk route access code exists.

Action:
Severity: Info.
SCH0694
SNMP trap: No
Special purpose trunks cannot be used for RS-ANI.

Action:
Severity: Info.
SCH0695
SNMP trap: No
Too many digits in access code.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1555 of 2360

SCH0696
Access code must specify a local (CO) trunk group.

Action:
Severity: Info.
SCH0697
SNMP trap: No
Unable to get protected memory. DN tree may become bad.

Action:
Severity: Info.
SCH0698
SNMP trap: No
Illegal attempt to modify existing data.

Action:
Severity: Info.
SCH0699
SNMP trap: No
RS-ANI package not present.

Action:
Severity: Info.
SCH0700
SNMP trap: No
ACD can only be for key 0.

Action:
Severity: Info.
SCH0701
SNMP trap: No
Input must be one of (NEW, OUT, CHG, PRT, END).

Action:
Severity: Info.
SCH0702
SNMP trap: No

Action:
Severity: Info.
SCH0703
SNMP trap: No
SNMP trap: No
Null input not permitted.

Action:
Severity: Info.
System Messages
Page 1556 of 2360

SCH0704
Input should be ACD/SCB.

Action:
Severity: Info.
SCH0705
SNMP trap: No
Unable to find an ACD block.

Action:
Severity: Info.
SCH0706
SNMP trap: No
Shorter Directory Number already exists.

Action:
Severity: Info.
SCH0707
SNMP trap: No
DN conflicts with existing number.

Action:
Severity: Info.
SCH0708
SNMP trap: No
DN conflicts with existing longer number.

Action:
Severity: Info.
SCH0709
SNMP trap: No
ACD DN must exist for NEW,CHG, OUT, PRT commands.

Action:
Severity: Info.
SCH0710
SNMP trap: No
SNMP trap: No
ACD list is full.

Action:
Severity: Info.
SCH0711
ACD DN must not exist for NEW command.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1557 of 2360

SCH0712
ACD LIST does not exist. Data corrupted.

Action: Perform SYSLOAD.
Severity: Info.
SCH0713
SNMP trap: No
ACD block must exist. Data corrupted.

Severity: Info.
SCH0714
SNMP trap: No
ACD DN and ACD block already exist for this customer.

Action:
Severity: Info.
SCH0715
SNMP trap: No
Unable to locate ACD data for this customer. Data corrupted.

Severity: Info.
SCH0716
SNMP trap: No
SNMP trap: No
SNMP trap: No
ACD DN conflict.
Action:
Severity: Info.
SCH0717
ACD DN does not exist.

Action:
Severity: Info.
SCH0718
ACD-ID (DN) already exists.

Action:
Severity: Info.
SCH0719
SNMP trap: No
ACD positions are full. Cannot add more.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1558 of 2360

SCH0720
Logical unit is not of required type.

Action:
Severity: Info.
SCH0721
SNMP trap: No
SCB must exist for CHG, OUT, or PRT command.

Action:
Severity: Info.
SCH0722
SNMP trap: No
SCB must not exist for NEW command.

Action:
Severity: Info.
SCH0723
SNMP trap: No
Maximum ACD positions out-of-range. Range is 1-120 on Small Systems and

1-1200 on Large Systems.
Action:
Severity: Info.
SCH0724
SNMP trap: No
Route input out-of-range (0-30).

Action:
Severity: Info.
SCH0725
SNMP trap: No
Cannot remove ACD data when ACD positions are active.

Action:
Severity: Info.
SCH0726
SNMP trap: No
First RAN time input out-of-range (0-2044).

Action:
Severity: Info.
SCH0727
SNMP trap: No
ACD-NITE-CFWD Interflow DN exceeds 16 digits.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1559 of 2360

SCH0728
ACD positions list cannot be decreased in size without removing agents.

Action:
Severity: Info.
SCH0729
SNMP trap: No
SNMP trap: No
ACD list is full.

Action:
Severity: Info.
SCH0730
DN conflicts with existing number.

Action:
Severity: Info.
SCH0731
SNMP trap: No
SNMP trap: No
Null input not permitted.

Action:
Severity: Info.
SCH0732

Action:
Severity: Info.
SCH0733
SNMP trap: No

Action:
Severity: Info.
SCH0734
SNMP trap: No

Action:
Severity: Info.
SCH0735
SNMP trap: No
Hold Recall timer value out-of-range (0-512).

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1560 of 2360

SCH0736
Cannot remove CAS while CAS keys are present.

Action:
Severity: Info.
SCH0737
SNMP trap: No
CAS does not exist for this customer.

Action:
Severity: Info.
SCH0738
SNMP trap: No
No further CAS keys allowed for this customer.

Action:
Severity: Info.
SCH0739
SNMP trap: No
CAS key data corrupted. Perform SYSLOAD.

Action:
Severity: Info.
SCH0740
SNMP trap: No
Incorrect option for chosen route type.

Action:
Severity: Info.
SCH0741
SNMP trap: No
RLR, RLM trunk types must be digitone.

Action:
Severity: Info.
SCH0742
SNMP trap: No
SNMP trap: No
Agent ID out-of-range.
Action:
Severity: Info.
SCH0743
Extended ACD package not equipped.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1561 of 2360

SCH0744
Invalid date.
Action:
Severity: Info.
SCH0745
SNMP trap: No
Telephone must be declared as ACD supervisor.

Action:
Severity: Info.
SCH0746
SNMP trap: No
Insufficient parameters given.

Action:
Severity: Info.
SCH0747
SNMP trap: No
Agent DN does not exist.

Action:
Severity: Info.
SCH0748
SNMP trap: No
Cannot supervise a telephone declared as a supervisor.

Action:
Severity: Info.
SCH0749
SNMP trap: No
Key data for ACD key cannot be found for DN specified.

Action:
Severity: Info.
SCH0750
SNMP trap: No
Agent already has a supervisor.

Action:
Severity: Info.
SCH0751
SNMP trap: No
ACD package is not equipped.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1562 of 2360

SCH0752
Key zero cannot be used for this function.

Action:
Severity: Info.
SCH0753
SNMP trap: No
TN specified must be an ACD set.

Action:
Severity: Info.
SCH0754
SNMP trap: No
SNMP trap: No
ACD DN must be given.

Action:
Severity: Info.
SCH0755
ACD DN given is not defined.

Action:
Severity: Info.
SCH0756
SNMP trap: No
Queue for the ACD DN given is full.

Action:
Severity: Info.
SCH0757
SNMP trap: No
Logical Unit not assigned as an ACD device.

Action:
Severity: Info.
SCH0758
SNMP trap: No
ACD data for specified ACD DN cannot be found.

Action:
Severity: Info.
SCH0759
SNMP trap: No
Digit display package must be equipped.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1563 of 2360

SCH0760
Display Class of Service must be specified.

Action:
Severity: Info.
SCH0761
SNMP trap: No
Key function not valid on ACD supervisor position.

Action:
Severity: Info.
SCH0762
SNMP trap: No
Associated DWC key must be previously defined.

Action:
Severity: Info.
SCH0763
SNMP trap: No
Another supervisor position has ENI key for specified ACD-DN.

Action:
Severity: Info.
SCH0764
SNMP trap: No
Threshold value is out-of-range (0-2047).

Action:
Severity: Info.
SCH0765
SNMP trap: No
Valid response to this prompt is YES or NO.

Action:
Severity: Info.
SCH0766
SNMP trap: No
Specified route number already exists and is not of the appropriate type.
Action:
Severity: Info.
SCH0767
SNMP trap: No
Supervisor's AGT key must be removed before removing agent.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1564 of 2360

SCH0768
No ACD devices assigned.

Action:
Severity: Info.
SCH0769
SNMP trap: No
Specified ACD device already assigned (to another customer).

Action:
Severity: Info.
SCH0770
SNMP trap: No
TGAR value is out-of-range (0-15).

Action:
Severity: Info.
SCH0771
SNMP trap: No
SNMP trap: No
COS value is invalid.

Action:
Severity: Info.
SCH0772
Wrong number of parameters given.

Action:
Severity: Info.
SCH0773
SNMP trap: No
Error in the DISA LIST connections.

Action:
Severity: Info.
SCH0774
SNMP trap: No
Incorrect value for TYPE (DIS, AUB, AUT allowed).

Action:
Severity: Info.
SCH0775
SNMP trap: No
DISA package not equipped.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1565 of 2360

SCH0777
Password given is not correct.

Action:
Severity: Info.
SCH0779
SNMP trap: No
SNMP trap: No
DN already exists.
Action:
Severity: Info.
SCH0780
DN conflicts with an existing DN.

Action:
Severity: Info.
SCH0781
SNMP trap: No
DN is required. Response must be given.

Action:
Severity: Info.
SCH0782
SNMP trap: No
DN exists but is not a DISA DN.

Action:
Severity: Info.
SCH0783
SNMP trap: No
The security code is out-of-range (0-8 digits).

Action:
Severity: Info.
SCH0791
SNMP trap: No
SNMP trap: No
out-of-range (0-15).
Action:
Severity: Info.
SCH0793
No DISA DNs are defined for this customer.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1566 of 2360

SCH0801
TYPE is invalid.
Action:
Severity: Info.
SCH0802
SNMP trap: No
Specified loop has no valid TN.

Action:
Severity: Info.
SCH0803
SNMP trap: No
Specified loop-shelf has no valid TN.

Action:
Severity: Info.
SCH0804
SNMP trap: No
Specified loop-shelf-card has no valid TN.

Action:
Severity: Info.
SCH0805
SNMP trap: No
SNMP trap: No
Specified TN is invalid.
Action:
Severity: Info.
SCH0806
CLI in CLS requires Analog CLI package to be equipped.

Action: Equip the Analog CLI package #349.
Severity: Major.
SCH0807
SNMP trap: No
TN is valid but unable to match type.

Action:
Severity: Info.
SCH0808
SNMP trap: No
SNMP trap: No
TYPE is invalid.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1567 of 2360

SCH0809
Too many parameters for LUC.

Action:
Severity: Info.
SCH0810
SNMP trap: No
Incompatible wireless card density.

Action: Service change is not allowed. If MWUN needs to be changed, remove
all units on the line card and reconfigure. If the new units are being configured, all
units must have the same value of MWUN as the existing units. MWUN can be
changed from 16 to 32, to cause all units to change. MWUN can be changed from
32 to 16 only if no units have a unit number <15. If any units exist with >15, an
SCH0810 message will be generated for the changed unit.
Severity: Minor.
SCH0811
SNMP trap: No
System has no unused cards.

Action:
Severity: Info.
SCH0812
SNMP trap: No
Specified loop has no unused cards.

Action:
Severity: Info.
SCH0813
SNMP trap: No
Specified loop-shelf has no unused cards.

Action:
Severity: Info.
SCH0814
SNMP trap: No
Specified loop-shelf-card is not unused.

Action:
Severity: Info.
SCH0815
SNMP trap: No
Specified loop-shelf-card-unit is not unused.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1568 of 2360

SCH0816
Invalid month in response to prompt.

Action:
Severity: Info.
SCH0817
SNMP trap: No
Invalid day (from) or (to).

Action:
Severity: Info.
SCH0818
SNMP trap: No
Invalid date for History File. Must be mmdd, LAST or ALL.

Action:
Severity: Info.
SCH0821
SNMP trap: No
System has no unused units.

Action:
Severity: Info.
SCH0822
SNMP trap: No
Specified loop has no unused units.

Action:
Severity: Info.
SCH0823
SNMP trap: No
Specified loop-shelf has no unused units.

Action:
Severity: Info.
SCH0824
SNMP trap: No
Specified loop-shelf-card has no unused units.

Action:
Severity: Info.
SCH0825
SNMP trap: No
Specified TN is not unused.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1569 of 2360

SCH0826
History File buffer not defined.

Action:
Severity: Info.
SCH0827
SNMP trap: No
TN (or part) is valid but no unused units of the requested type were found.
Action:
Severity: Info.
SCH0828
SNMP trap: No
History File must be output before erasing file.

Action:
Severity: Info.
SCH0829
SNMP trap: No
Invalid date range for History File.

Action:
Severity: Info.
SCH0830
SNMP trap: No
Data entry invalid dd (day 1-31) mm (month 1st 3 letters of month) yy (year
xxxx).
Action:
Severity: Info.
SCH0831
SNMP trap: No
SNMP trap: No
No system date exists.

Action:
Severity: Info.
SCH0832
Incorrect response to PAGE (YES/NO).

Action:
Severity: Info.
SCH0833
SNMP trap: No
DES must be 1-6 alphanumeric characters.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1570 of 2360

SCH0834
All associated service routes must be deleted before the NI-2 CBC master
route can be removed.
Action:
Severity: Minor.
SCH0835
SNMP trap: No
The trunk route type and the service type, mismatch.

Action: Input the correct decimal value of the service.
Severity: Minor.
SCH0836
SNMP trap: No
The NI-2 package is not equipped.

Action: Install the NI-2 package.
Severity: Minor.
SCH0837
SNMP trap: No
The service has been configured in this NI-2 CBC master route.
Action: Use other service type.
Severity: Minor.
SCH0838
SNMP trap: No
The Backup D-channel is not supported for VNS.

Action: Invalid DCH number entered for PDCH.
Severity: Info.
SCH0839
SNMP trap: No
A 3 digit or 4 digit input is expected.

Action: Use the correct input.
Severity: Minor.
SCH0840
SNMP trap: No
NI-2 CBC IntraLATA OUTWATS are already defined.

Action:
Severity: Minor.
SCH0841
SNMP trap: No
NI-2 CBC InterLATA OUTWATS are already defined.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1571 of 2360

SCH0842
Interface type not supported. ISA does not support NI-2.

Action:
Severity: Minor.
SCH0843
SNMP trap: No
NDS valid only for NI-2 interface.

Action:
Severity: Info.
SCH0844
SNMP trap: No
NI-2 name display package not equipped.

Action:
Severity: Info.
SCH0853
SNMP trap: No
CAC Conversion Entry is not defined in the ANI Block of the Customer Data
Block. The CAC Conversion Entry is stored in the database.
Action: Define a CAC Conversion Entry in the customer data bock.
Severity:
SCH0854
SNMP trap: No
The entry is not configured. The CACC entry cannot be deleted.

Action:
Severity:
SCH0855
SNMP trap: No
Access code does not exist or is invalid.

Action:
Severity: Info.
SCH0856
SNMP trap: No
Null line not allowed for customer.

Action:
Severity: Info.
SCH0857
SNMP trap: No
Customer has no data blocks of correct type.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1572 of 2360

SCH0858
Route number does not exist.

Action:
Severity: Info.
SCH0859
SNMP trap: No
Route number out-of-range.

Action:
Severity: Info.
SCH0860
SNMP trap: No
No restricted (or allowed) codes found. Block is clear.

Action:
Severity: Info.
SCH0861
SNMP trap: No
No route data block or members for the specified route number.

Action:
Severity: Info.
SCH0862
SNMP trap: No
No code restriction block for the specified route number or access code.
Action:
Severity: Info.
SCH0871
SNMP trap: No
The Mobility package is not present.

Severity: Info.
SCH0872
SNMP trap: No
A Phantom loop is not available.

Action: Configure a Phantom loop from Overlay 97.
Severity: Info.
SCH0873
SNMP trap: No
The CAC Conversation table entry already exists.

Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1573 of 2360

SCH0874
When creating a new customer, only default tables (number 0) are

configurable for prompt R_ENTRY, MFC_ENT and CIS_ENT.
Action: Answer 0 or {CR} to the prompt.
Severity:
SCH0875
SNMP trap: No
There are still EIMC/MXC card(s) associated with this MISP.

Action: In order to remove the MISP/MOBILITY application, remove all
EIMC/MXC cards from the MISP using Mobility MAT platform.
Severity: Info.
SCH0877
SNMP trap: No
Invalid DN. Zeros not allowed.

Action:
Severity: Info.
SCH0878
SNMP trap: No
Invalid DN. Null line not allowed.

Action:
Severity: Info.
SCH0879
SNMP trap: No
No TN hunt to specified DN.

Action:
Severity: Info.
SCH0880
SNMP trap: No
Valid DN found but of wrong type.

Action:
Severity: Info.
SCH0881
SNMP trap: No
No valid DN can be found starting with specified digits.

Action:
Severity: Info.
SCH0882
SNMP trap: No
Invalid DN. Zeroes not allowed.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1574 of 2360

SCH0883
Invalid DN type in DN block.

Action:
Severity: Info.
SCH0884
SNMP trap: No
Loop entered is not a DTI/PRI loop. (LD 73)

Action:
Severity:
SCH0885
SNMP trap: No
ICS data associated with the loop is removed (LD 17) and the default value
of FF (UNASSIGNED PCM CODE) is sent to the remote end.
Action:
Severity:
SCH0886
SNMP trap: No
Shorter DN number exists.

Action:
Severity: Info.
SCH0888
SNMP trap: No
No customer data block can be found.

Action:
Severity: Info.
SCH0889
SNMP trap: No
No route blocks can be found for this customer.

Action:
Severity: Info.
SCH0890
SNMP trap: No
ACD DN conflict. Data blocks not correctly set up for this ACD DN.
Action:
Severity: Info.
SCH0891
SNMP trap: No
Low speed link already assigned.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1575 of 2360

SCH0892
High speed link already assigned.

Action:
Severity: Info.
SCH0893
SNMP trap: No
Low speed link device must be disabled before changes.

Action:
Severity: Info.
SCH0894
SNMP trap: No
High speed link device must be disabled before changes.

Action:
Severity: Info.
SCH0895
SNMP trap: No
No other user is allowed for an existing low speed link.

Action:
Severity: Info.
SCH0896
SNMP trap: No
No other user is allowed for an existing high speed link.

Action:
Severity: Info.
SCH0897
SNMP trap: No
AUX processor package not equipped.

Action:
Severity: Info.
SCH0898
SNMP trap: No
NOO cannot be used with CDL, CAM, ACD, HSL, or LSL.

Action:
Severity: Info.
SCH0899
SNMP trap: No
NOO must be used with one or more of MTC, TRF, SCH, CTY, or BUG.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1576 of 2360

SCH0900
Group number exceeds customer maximum group number.

Action:
Severity: Info.
SCH0901
SNMP trap: No
SL-1 ring option conflicts with group option.

Action:
Severity: Info.
SCH0902
SNMP trap: No
DIG group number conflicts with existing DIG group number.

Action:
Severity: Info.
SCH0903
SNMP trap: No
DIG list block does not exist.

Action:
Severity: Info.
SCH0904
SNMP trap: No
Null input for DIG group number.

Action:
Severity: Info.
SCH0905
SNMP trap: No
DIG group out-of-range (0-253).

Action:
Severity: Info.
SCH0906
SNMP trap: No
DIG member number conflicts with existing DIG member number.

Action:
Severity: Info.
SCH0907
SNMP trap: No
Undefined DIG member number.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1577 of 2360

SCH0908
Null input for DIG member number.

Action:
Severity: Info.
SCH0909
SNMP trap: No
DIG member number out-of-range (0-99).

Action:
Severity: Info.
SCH0910
SNMP trap: No
Null input for DIG ring option.

Action:
Severity: Info.
SCH0911
SNMP trap: No
DIG ring/voice (R/V) option out-of-range. Must be specified.

Action:
Severity: Info.
SCH0912
SNMP trap: No
Bad TN assigned as DIG member number.

Action:
Severity: Info.
SCH0913
SNMP trap: No
Total DIG group number cannot be reduced as members are assigned to

groups to be removed.
Action:
Severity: Info.
SCH0914
SNMP trap: No
Conflict between DIG member number and special prefix DN.

Action:
Severity: Info.
SCH0915
SNMP trap: No
CDR port number conflicts with existing CDR port number.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1578 of 2360

SCH0916
Illegal use of CHG.

Action: Disable port in LD 35 and use OUT to remove all users.
Severity: Info.
SCH0918
SNMP trap: No
Maximum number of ACD-ADS customers per system is exceeded.

Action:
Severity: Info.
SCH0919
SNMP trap: No
Maximum number of ACD-ADS agents per system is exceeded.

Action:
Severity: Info.
SCH0920
SNMP trap: No
Translation list number not in LD 15.

Action:
Severity: Info.
SCH0921
SNMP trap: No
Attempt to configure RCAP with a QSIG Name Display remote capability when
one is already configured.
Action: Remove the existing RCAP before entering a new one.
Severity:
SCH0922
SNMP trap: No
Attempt to configure RCAP with a QSIG Call Completion to Busy Subscriber

remote capability when one is already configured.
Severity:
SCH0923
SNMP trap: No
Attempt to configure RCAP with a QSIG Call Completion on No Response

remote capability when one is already configured.
Severity:
SCH0924
SNMP trap: No
Agent ID lower or upper bound conflicts with existing data.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1579 of 2360

SCH0925
New request is invalid for AD/SCB prompt if the customer has been assigned
as an ACD package D customer.
Action:
Severity: Info.
SCH0926
SNMP trap: No
PRT/CHG/OUT request is invalid for ADS prompt if the customer is not an

ACD package D customer.
Action: Use 'NEW' request if the customer is ACD D.
Severity: Info.
SCH0927
SNMP trap: No
The numbered key is less than the total number of agents logged in at this
instant.
Action:
Severity: Info.
SCH0928
SNMP trap: No
NULL input for LOG prompt is invalid under the NEW request for ADS prompt.
Action:
Severity: Info.
SCH0929
SNMP trap: No
Points to the agent ID table is NIL.

Action: Try again.
Severity: Info.
SCH0930
SNMP trap: No
More than one parameter given for ARSQ.

Action:
Severity: Info.
SCH0931
SNMP trap: No
ARSQ must be null or in the range 0-3.

Action:
Severity: Info.
SCH0932
SNMP trap: No
ARSR must be YES or NO, or null.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1580 of 2360

SCH0933
More than one parameter given for ARSR.

Action:
Severity: Info.
SCH0934
SNMP trap: No
More than one parameter given for SPRI.

Action:
Severity: Info.
SCH0935
SNMP trap: No
SPRI must be null or in the range 0-3.

Action:
Severity: Info.
SCH0936
SNMP trap: No
More than one parameter given for MPRI.

Action:
Severity: Info.
SCH0937
SNMP trap: No
MPRI must be null or in the range SPRI to 3.

Action:
Severity: Info.
SCH0938
SNMP trap: No
MPRI cannot be null because SPRI is greater than current value of MPRI.
Action:
Severity: Info.
SCH0939
SNMP trap: No
More than one parameter given for PROM.

Action:
Severity: Info.
SCH0940
SNMP trap: No
PROM must be null or in the range 1-999.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1581 of 2360

SCH0941
PROM was given as null but must now be changed because currently PROM
is undefined and SPRI is less than MPRI.
Action:
Severity: Info.
SCH0942
SNMP trap: No
More than one parameter given for ERWT.

Action:
Severity: Info.
SCH0943
SNMP trap: No
ERWT must be NO, null, or in the range 0-999.

Action:
Severity: Info.
SCH0945
SNMP trap: No
Invalid Template type. Should be SL-1 or 500.

Action:
Severity: Info.
SCH0946
SNMP trap: No
SNMP trap: No
Invalid unit type.

Action:
Severity: Info.
SCH0947
Illegal INFO response. Should be FRM, DEF, USE, or USS.

Action:
Severity: Info.
SCH0948
SNMP trap: No
TEMPLATE Number is out-of-range.

Action:
Severity: Info.
SCH0949
SNMP trap: No
MMT sets cannot modify CLS EXRO-4, if CLS DRDA is configured.

Action: Change CLS DRDA to CLS DRDD and then modify CLS EXRO-4.
Severity:
SNMP trap: No
System Messages
Page 1582 of 2360

SCH0950
Prime DN must be a single appearance DN for Automatic Answerback. The

AAK key is removed or the AAA class of service is reset to AAD.
Action:
Severity: Info.
SCH0951
SNMP trap: No
COS cannot be AAA if AAK key is already assigned.

Action:
Severity: Info.
SCH0952
SNMP trap: No
AAK key cannot be assigned if COS is AAA.

Action:
Severity: Info.
SCH0953
SNMP trap: No
Current DN appears elsewhere and thus may interfere with AAB operation.
Action:
Severity: Info.
SCH0954
SNMP trap: No
AAB package not equipped.

Action:
Severity: Info.
SCH0955
SNMP trap: No
Cannot remove customer data block before removing associated route data
blocks.
Action:
Severity: Info.
SCH0956
SNMP trap: No
Command is OUT CDB, but units are not all removed.

Action:
Severity: Info.
SCH0960
SNMP trap: No
Number of Park DN out-of-range.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1583 of 2360

SCH0961
Active park DN cannot be deleted.

Severity: Info.
SCH0962
SNMP trap: No
Mobility package is not equipped.

Severity: Info.
SCH0963
SNMP trap: No
Service change for EIMC/MXC card(s) is not allowed from overlay 27.
Action: Use the Mobility Mat platform.
Severity: Info.
SCH0964
SNMP trap: No
A problem has occurred when configuring EIMC/MXC from Mobility MAT

platform.
Severity: Info.
SCH0965
SNMP trap: No
Only one MISP can have the Mobility application defined.

Action:
Severity: Info.
SCH0966
SNMP trap: No
The MISP card is not in the Manual Disabled state.

Action: Use Overlay 32 to disable the MISP card.
Severity: Info.
SCH0967
SNMP trap: No
Warning: For the Set to Set Messaging feature, in order to receive a call log
indicator, you must have CNDA also.
Action:
Severity: Info.
SCH0970
SNMP trap: No
ICI key/lamp not assigned in customer data for this station category.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1584 of 2360

SCH0971
MR terminal assignment out-of-range (0-7).

Action:
Severity: Info.
SCH0972
SNMP trap: No
SL-1 station must have CLS = MWA before assigning MR key.

Action:
Severity: Info.
SCH0979
SNMP trap: No
DN entered for ROA is not a station DN.

Action:
Severity: Info.
SCH0980
SNMP trap: No

Action:
Severity: Info.
SCH0981
SNMP trap: No
SNMP trap: No
Threshold out-of-range.
Action:
Severity: Info.
SCH0982
Threshold must be greater or equal to the previous threshold.

Action:
Severity: Info.
SCH0983
SNMP trap: No
SNMP trap: No
TN not existing in CDB.

Action:
Severity: Info.
SCH0984
Route number is not a RAN/MUS route.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1585 of 2360

SCH0985
Timing threshold not entered.

Action:
Severity: Info.
SCH0986
SNMP trap: No
Timing out-of-range (15-500).

Action:
Severity: Info.
SCH0987
SNMP trap: No
DN assigned out-of-range; maximum 10 for ROA.

Action:
Severity: Info.
SCH0988
SNMP trap: No
SNMP trap: No
Action:
Severity: Info.
SCH0989
No Speed Call Lists in existence.

Action:
Severity: Info.
SCH0990
SNMP trap: No
Dialing group number out-of-range (0-7).

Action:
Severity: Info.
SCH0991
SNMP trap: No
Warning: No DN translator set up for customer.

Action:
Severity: Info.
SCH0992
SNMP trap: No
Warning: No attendant DN block setup.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1586 of 2360

SCH0993
No value assigned to attendant access code.

Action:
Severity: Info.
SCH0994
SNMP trap: No
Speed Call List number out-of-range.

Action:
Severity: Info.
SCH0995
SNMP trap: No
Speed Call List not available to be used as translation list.

Action: Use LD 18. Speed Calls in 18 must DNSZ4 and SIZE10.
Severity: Info.
SCH0996
SNMP trap: No
An attempt has been made to remove, change or reassign an attendant

supervisory console while in-service observation mode.
Action:
Severity: Info.
SCH0997
SNMP trap: No
Prime TN of attendant console must be on line (unit) zero of card.

Action:
Severity: Info.
SCH0998
SNMP trap: No
May not allocate console on any cards which have any valid stations.
Action:
Severity: Info.
SCH0999
SNMP trap: No
May not allocate SL-1 sets on any card having an attendant console.
Action:
Severity: Info.
SCH1000
SNMP trap: No
Secondary TN must be the second unit which is contiguous to the prime TN

(which is on the first line).
Action: Enter the prime and secondary TN again.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1587 of 2360

SCH1001
TNTRANS failed on remove from core. Corrupted data in memory.

Action: System should be reloaded. If the fault persists, call your technical
support group.
Severity: Info.
SCH1003
SNMP trap: No
CNUA/CNAA Class of Service needs to be defined in Overlay 10 before GXPA

is defined.
Action:
Severity: Info.
SCH1009
SNMP trap: No
XMWK and RMWK keys are supported only on MMT sets.

Action: Configure on MMT sets.
Severity:
SCH1014
SNMP trap: No
The Australia TS014 protocol is not meant to support this functionality.

Severity: Info.
SCH1030
SNMP trap: No
Port name specified could not be found. PTTP reprompted.

Action:
Severity: Minor.
SCH1031
SNMP trap: No
Route member port type will not be recorded. Memory allocation failed.
Action:
Severity: Minor.
SCH1032
SNMP trap: No
Route member port type assignment performed without previous stored

default port type status information.
Action:
Severity: Minor.
SCH1033
SNMP trap: No
Invalid number of responses to the LSPN prompt. Only one is allowed.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1588 of 2360

SCH1034
Specified loss plan is not available.

Action:
Severity: Minor.
SCH1035
SNMP trap: No
Response required for RESTORE prompt.

Action:
Severity: Minor.
SCH1036
SNMP trap: No
Response to RESTORE prompt must be either YES or NO.

Action:
Severity: Minor.
SCH1037
SNMP trap: No
Wrong number of response parameters to the HEAD prompt.

Action:
Severity: Minor.
SCH1038
SNMP trap: No
Response to HEAD prompt was not YES, NO or {CR}.

Action:
Severity: Minor.
SCH1039
SNMP trap: No
A unit being modified has been previously assigned the port type that was not
the default for the configuration, and will not be assigned the default port type
for the new configuration.
Action:
Severity: Minor.
SCH1098
SNMP trap: No
The VID7 supplementary service needs voice and data configuration.

Action: Configure the supported call type for voice and data.
Severity:
SCH1099
SNMP trap: No
The VMWI message is lost and no retry will be attempted.

Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1589 of 2360

SCH1100
Response to EMG must be one of CON, MEM, or NO.

Action:
Severity: Info.
SCH1101
SNMP trap: No
Input does not match stored mnemonics.

Action:
Severity: Info.
SCH1102
SNMP trap: No
Group number is out-of-range (0-9).

Action:
Severity: Info.
SCH1103
SNMP trap: No
Invalid response to prompt GRP.

Action:
Severity: Info.
SCH1104
SNMP trap: No
Controller already exists for this group.

Action:
Severity: Info.
SCH1105
SNMP trap: No
Group is full (10 members, 1 controller).

Action:
Severity: Info.
SCH1106
SNMP trap: No
CFNA and BFSE recall cannot be allowed at the same time.

Action:
Severity: Info.
SCH1107
SNMP trap: No
CTL for this customer exists already.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1590 of 2360

SCH1108
Trace data does not exist for this customer.

Action:
Severity: Info.
SCH1109
SNMP trap: No
Invalid request for call trace data.

Action:
Severity: Info.
SCH1110
SNMP trap: No
A DN must be entered for prompt NITE. A night DN cannot be removed, but

can be changed.
Action:
Severity: Info.
SCH1111
SNMP trap: No
A valid response = YES, NO, or {CR}.

Action:
Severity: Info.
SCH1112
SNMP trap: No
TN block already exists and is not another bell.

Action:
Severity: Info.
SCH1113
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Not a valid Trace DN.

Action:
Severity: Info.
SCH1114
DN is already in list.
Action:
Severity: Info.
SCH1115
DN is not in list.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1591 of 2360

SCH1136
The given prefix table already exists.

Action: The number entered for the prefix table must be changed.
Severity: Info.
SCH1137
SNMP trap: No
Cannot remove non-existing table.

Severity: Info.
SCH1138
SNMP trap: No
Invalid entry for NPI.

Action: Give any one of the following valid NPI values UNKN, E164, PRIV, E163,
TELX, X121, NATL.
Severity: Info.
SCH1139
SNMP trap: No
Invalid entry for TON.

Action: Give any one of the following valid TON values UNKN, INTL, NATL,
ECPN, LOCL, ELOC, ECDP.
Severity: Info.
SCH1140
SNMP trap: No
Invalid entry for PREF.

Action: Maximum of four digit Access Prefix value can have allowed digit enter
as either numerals 0 - 9 or character "#".
Severity: Info.
SCH1141
SNMP trap: No
Table number specified is not configured or is out-of-range.

Action: Table number must be configured with value range 0-16.
Severity: Info.
SCH1191
SNMP trap: No
The RCAP MQC is only allowed if the MEET package is equipped.

Action:
Severity: Info.
SCH1192
SNMP trap: No
The RCAP MQC is only allowed for QSIG GF interface type.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1592 of 2360

SCH1193
This entry is not allowed for MQC_FEAT prompt as the corresponding

package is restricted.
Action:
Severity: Info.
SCH1194
SNMP trap: No
Alternate day out-of-range.

Action: Enter in the range 1-7.
Severity:
SCH1195
SNMP trap: No
The response to DAY0-3 or HOL_OPT prompt cannot be deleted as it is not

included.
Action: Enter an existing alternate day for DAY0_3
Severity:
SCH1196
SNMP trap: No
Holidays cannot be changed or deleted (CRHOL_CHG/OUT) while creating a

new CDB.
Action: Add holidays with CRHOL = NEW.
Severity: Info.
SCH1197
SNMP trap: No
Holiday list is full (20 entries). Cannot add anymore holidays.

Action:
Severity:
SCH1198
SNMP trap: No
Holiday list is empty. No holiday to delete.

Action:
Severity: Info.
SCH1199
SNMP trap: No
Invalid date.
Action: Enter in the format dd mm [yyyy].
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1593 of 2360

SCH1200
The holiday entered should exist when trying to change or delete a new
holiday. When adding a new holiday, it should be already present in the list.
Action: For an existing holiday, CRHOL = CHG/OUT. For a new holiday,
CRHOL = New.
Severity:
SCH1205
SNMP trap: No
XMWK key cannot be associated with PDNs.

Action: Configure XMWK key for a non-PDN.
Severity:
SCH1206
SNMP trap: No
DN to be associated with XMWK key is not configured on this set.

Action: Configure the DN as non-PDN.
Severity:
SCH1207
SNMP trap: No
XMWK key is already configured for this DN.

Action: Do not try to configure more than one XMWK
Severity:
SCH1208
SNMP trap: No
XMWK key cannot be on key 0.

Action: Configure the XMWK key on a non-zero key.
Severity:
SCH1209
SNMP trap: No
RMWK key cannot be on key 0.

Action: Configure RMWK key on a non-zero key.
Severity:
SCH1210
SNMP trap: No
Only 0, 1 and 2 are accepted as inputs for the number of AOMs (KBA or KEM).
Action: Enter the valid number 0, 1 or 2. Press <CR> to skip the prompt.
Severity: Info.
SCH1211
SNMP trap: No
Invalid DN type for Mailbox DN.

Action: Configure a valid DN.
Severity:
SNMP trap: No
System Messages
Page 1594 of 2360

SCH1212
On the M3901 and M3902, if SCR, SCN, PVN, PVR, MCN or MCR is
configured, it must be configured only on key 0. These mnemonics will be
blocked from being assigned to keys 1 through 5.
Action:
Severity: Info.
SCH1213
SNMP trap: No
DN cannot be deleted until the associated XMWK key is deleted.

Action: Delete the XMWK key first.
Severity:
SCH1214
SNMP trap: No
VMBA package #246, is not equipped.

Action: Enable the VMBA package.
Severity:
SCH1215
SNMP trap: No
GZPA Class of service needs to be defined before GPTA or GZBA is defined.

This SCH is for Overlay 11.
Action:
Severity: Info.
SCH1216
SNMP trap: No
ANI Entry is not defined in the ANI Block of the Customer Data Block. The ANI
Entry is stored in the data base.
Action: Define an ANI Entry in the Customer Data Block.
Severity:
SCH1217
SNMP trap: No
Cannot decrease ANI Table size. Entries to be removed are not empty.
Action: Remove the unneeded ANI entries first. Then decrease the ANI table
entry size.
Severity:
SCH1218
SNMP trap: No
ANI Entry or Entries are not deleted since the entry or entries are not
configured.
Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1595 of 2360

SCH1219
Zone number has to be between 1 and 9. This SCH is for Overlay 18.
Action:
Severity: Info.
SCH1220
SNMP trap: No
The ANI entry already exists.

Action: If the user does not want to modify an existing entry, enter {CR} for the
next four subprompts.
Severity:
SCH1222
SNMP trap: No
Cannot remove non-existing table.

Severity: Info.
SCH1223
SNMP trap: No
Invalid entry for NPI

Action: Give any one of the following valid NPI values, UNKN, E164, PRIV,
E163, TGELX, X121, NATL.
Severity: Info.
SCH1224
SNMP trap: No
Invalid entry for TON

Action: Give any one of the following valid TON values, UNKN, INTL, NATL,
ESPN, LOCL, ELOC, ECDP.
Severity: Info.
SCH1225
SNMP trap: No
Invalid entry for PREF.

Action: Maximum of four digit Access Prefix value can have allowed digit entry
as either numerals 0 -9 or character "#".
Severity: Info.
SCH1226
SNMP trap: No
Table number specified is not configured or is out-of-range.

Action: Table number must be configured with a value range 0 - 16.
Severity: Info.
SNMP trap: No
System Messages
Page 1596 of 2360

SCH1227
ISDN package is not equipped.

Action: Feature DAPC is part of the ISDN package #145.
Severity: Info.
SCH1228
SNMP trap: No
Prefix table zero cannot be removed.

Action: Valid input value for prefix table removal is 1 -15.
Severity: Info.
SCH1229
SNMP trap: No
No reviving zone page allowed on a TN associated with this DN. The TN has
to define as BCS or Analog set with speaker. This SCH is for Overlay 18.
Action:
Severity: Info.
SCH1230
SNMP trap: No
Taiwan R1 trunk has to be incoming only or outgoing only. Response IAO is

not allowed for ICOG. Valid responses are ICT or OGT.
Action:
Severity:
SCH1231
SNMP trap: No
The Zone package 218 is not equipped.

Action:
Severity: Info.
SCH1238
SNMP trap: No
The class of service cannot be changed from BFEA to BFED, when an existing
BFS key has the same TN configuration as the configuring set.
Action: Make the corresponding key null and then change the class of service
to BFEA.
Severity: Info.
SCH1239
SNMP trap: No
The class of service is BFED. The TN of the BFS key and the TN of the
configuring set, must not be the same.
Action: Before you configure a BFS key against a TN that is the same as the
configuring set, change the class of service to BFEA.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1597 of 2360

SCH1240
Invalid response to YES/NO question.

Action:
Severity: Info.
SCH1241
SNMP trap: No
Invalid response to YES/NO question).

Action:
Severity: Info.
SCH1242
SNMP trap: No
Invalid entry. Out-of-range (0-15).

Action:
Severity: Info.
SCH1243
SNMP trap: No
Entry out-of-range (maximum 4 fields).

Action:
Severity: Info.
SCH1244
SNMP trap: No
Entry out-of-range (minimum 4 fields).

Action:
Severity: Info.
SCH1245
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Only one cadence.

Action:
Severity: Info.
SCH1246
Action:
Severity: Info.
SCH1247
Action:
Severity: Info.
System Messages
Page 1598 of 2360

SCH1250
Cadence value of 0 is invalid.

Action:
Severity: Info.
SCH1251
SNMP trap: No
First Cadence Element Max Exceeded (31).

Action:
Severity: Info.
SCH1252
SNMP trap: No
Second Cadence Element Max Exceeded (511).

Action:
Severity: Info.
SCH1253
SNMP trap: No
Third Cadence Element Max Exceeded (127).

Action:
Severity: Info.
SCH1254
SNMP trap: No
Fourth Cadence Element Max Exceeded (511).

Action:
Severity: Info.
SCH1256
SNMP trap: No
Tones and Cadence already exist.

Action:
Severity: Info.
SCH1257
SNMP trap: No
Tones and Cadences do not exist.

Action:
Severity: Info.
SCH1258
SNMP trap: No
TRB password does not match CDB PSWD or LEVEL2 PSWD.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1599 of 2360

SCH1259
First digit must be 0, and second must be less than or equal to 3 for TDS card
message compatibility.
Action:
Severity: Info.
SCH1260
SNMP trap: No
Input is out-of-range (0-255).

Action:
Severity: Info.
SCH1277
SNMP trap: No
Another FDID IDC tree already exists for this customer.

Action: Only one FDID tree allowed per customer. Out this tree or configure new
tree or modify existing FDID IDC tree.
Severity:
SCH1278
SNMP trap: No
Tree table 0 is not allowed for FDID IDC tree.

Action: Use a different number for FDID table.
Severity:
SCH1279
SNMP trap: No
All branches must be released prior to OUT A FDID IDC tree.

Action: Release the branches.
Severity:
SCH1284
SNMP trap: No
SUPP package or ESA PAGE package is required for Special Service Lists.
Action: Equip at least one of the packages and try again.
Severity: Info.
SCH1285
SNMP trap: No
Automatic Wake-Up Controller is only allowed on Option 11C Compact

systems with the AWU package equipped.
Action: If the system is Compact, equip the AWU package.
Severity: Info.
SCH1286
SNMP trap: No
Digit Display must be equipped for a set with AWCA.

Action: Configure the AWCA on a set with a digit display.
Severity: Info.
SNMP trap: No
System Messages
Page 1600 of 2360

SCH1287
The number of wireless telephones in the system exceeds the maximum

number of wireless telephones allowed.
Action:
Severity:
SCH1288
SNMP trap: No
The new MIN or ESN entered is a duplicate of the MIN or ESN configured for
the specified TN. Enter a unique value.
Action:
Severity:
SCH1289
SNMP trap: No
Unable to match the input with the stored mnemonics. Valid responses for the
PUTYP prompt are PRIV and IS41.
Action:
Severity:
SCH1299
SNMP trap: No
No Virtual TNs available on phantom loops.

Action:
Severity: Minor.
SCH1300
SNMP trap: No
MFC/MFE signal number out-of-range.

Action:
Severity: Info.
SCH1301
SNMP trap: No
Invalid MFC/MFE function mnemonic.

Action:
Severity: Info.
SCH1302
SNMP trap: No
SNMP trap: No
Function already exists.

Action:
Severity: Info.
SCH1303
Attempt to enter Forward Called Number Digit in illegal location.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1601 of 2360

SCH1304
Wrong number of input fields for GNPO.

Action:
Severity: Info.
SCH1305
SNMP trap: No
MFC/SS/MFE head table does not exist.

Action:
Severity: Info.
SCH1306
SNMP trap: No
MFC Timer out-of-range (1-24 sec.).

Action:
Severity: Info.
SCH1307
SNMP trap: No
MFC Automatic Digits out-of-range (1-4).

Action:
Severity: Info.
SCH1308
SNMP trap: No
Entry for MFL out-of-range.

Action:
Severity: Info.
SCH1309
SNMP trap: No
Remove tables not needed before lesser MAXT.

Action:
Severity: Info.
SCH1310
SNMP trap: No
Maximum number of MFC/MFE tables out-of-range.

Action:
Severity: Info.
SCH1311
SNMP trap: No
MFC/SS/MFE table number out-of-range.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1602 of 2360

SCH1312
MFC/SS/MFE table already exists.

Action:
Severity: Info.
SCH1313
SNMP trap: No
MFC/SS/MFE table does not exist.

Action:
Severity: Info.
SCH1314
SNMP trap: No
Conflicting MFC/MFE route types.

Action:
Severity: Info.
SCH1315
SNMP trap: No
MFC End-to-End Signaling code out-of-range.

Action:
Severity: Info.
SCH1316
SNMP trap: No
Invalid MFC/MFE signaling level.

Action:
Severity: Info.
SCH1317
SNMP trap: No
MFC/MFE/MFC package not equipped.

Action:
Severity: Info.
SCH1318
SNMP trap: No
MFC DID/MFE package not equipped.

Action:
Severity: Info.
SCH1320
SNMP trap: No
MFC/SS/MFE table linked to a route cannot be removed.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1603 of 2360

SCH1321
Route ICOG must be incoming and MFC table defined.

Action:
Severity: Info.
SCH1322
SNMP trap: No
Null response not allowed.

Action:
Severity: Info.
SCH1323
SNMP trap: No
MFC/MFE level 1 does not exist.

Action:
Severity: Info.
SCH1324
SNMP trap: No
Cannot remove MFC/MFE level 1.

Action:
Severity: Info.
SCH1325
SNMP trap: No
MFC/MFE level not defined.

Action:
Severity: Info.
SCH1326
SNMP trap: No
Incomplete response for RECVor RFUN.

Action:
Severity: Info.
SCH1327
SNMP trap: No
Incomplete response for XMIT or RFUN.

Action:
Severity: Info.
SCH1328
SNMP trap: No
SNMP trap: No
Invalid input type

Action:
Severity: Info.
System Messages
Page 1604 of 2360

SCH1329
Invalid function for this table/level/type.

Action:
Severity: Info.
SCH1330
SNMP trap: No
Table not deleted in route data.

Action:
Severity: Info.
SCH1331
SNMP trap: No
Response must be either ICT or OGT.

Action:
Severity: Info.
SCH1332
SNMP trap: No
Outgoing MFC table exists in a DID route.

Action:
Severity: Info.
SCH1333
SNMP trap: No
Incoming MFC table does not exist in this route.

Action:
Severity: Info.
SCH1334
SNMP trap: No
Only incoming MFE tables allowed.

Action:
Severity: Info.
SCH1335
SNMP trap: No
Only DID routes allowed for MFE tables.

Action:
Severity: Info.
SCH1336
SNMP trap: No
The loop number to be entered must be for a DTI2 loop.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1605 of 2360

SCH1337
An invalid TN.
Action:
Severity: Minor.
SCH1339
SNMP trap: No
Group Listening is not allowed on this set.

Action:
Severity: Info.
SCH1340
SNMP trap: No
Invalid response to prompt SCL.

Action:
Severity: Info.
SCH1341
SNMP trap: No
500 set assigned as DIP. Cannot be speed call controller.

Action:
Severity: Info.
SCH1345
SNMP trap: No
Attempt to configure RCAP CTO or ECTO without BNE package equipped..

Action:
Severity:
SCH1346
SNMP trap: No
Attempt to configure RCAP with an EuroISDN Explicit Call Transfer remote

capability. (CTO or ECTO) when one is already configured.
Action: Remove the already configured RCAP before entering a new one.
Severity:
SCH1356
SNMP trap: No
Only MSB, NRD, AAG, AMG, DWC and ASP are allowed on these keys.
Action:
Severity: Info.
SCH1357
SNMP trap: No
On the M3902, key 4 will only accept NUL or TRN or AO3 or AO6 as possible
mnemonics.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1606 of 2360

SCH1358
On the M3902, key 5 will only accept NUL or MWK as possible mnemonics.
Action:
Severity: Info.
SCH1359
SNMP trap: No
On the M3903, keys 4 - 15 are not supported.

Action:
Severity: Info.
SCH1360 Key
SNMP trap: No
On the M3903, M3904, M3905, i2001, i2002, i2004 and i2050 sets, key 17 is
reserved for the TRN mnemonic. No other mnemonic except NUL can be
configured on that key.
Action:
Severity: Info.
SCH1361
SNMP trap: No
reserved for the AO3 or AO6 mnemonic. No other mnemonic except NUL can
be configured on that key.
Action:
Severity: Info.
SCH1362
SNMP trap: No
reserved for the CFW mnemonic. No other mnemonic except NUL can be
Action:
Severity: Info.
SCH1363
SNMP trap: No
reserved for the RGA mnemonic. No other mnemonic except NUL can be
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1607 of 2360

SCH1364
reserved for PRK mnemonic. No other mnemonic except NUL, can be
Action:
Severity: Info.
SCH1365
SNMP trap: No
reserved for the RNP mnemonic. No other mnemonic except NUL can be
Action:
Severity: Info.
SCH1366
SNMP trap: No
reserved for SCU/SCC/SSU or SSC. No other mnemonic except NUL can be
Action:
Severity: Info.
SCH1367
SNMP trap: No
reserved for the PRS mnemonic. No other mnemonic except NUL can be
Action:
Severity: Info.
SCH1368
SNMP trap: No
reserved for the CHG mnemonic. No other mnemonic except NUL can be
Action:
Severity: Info.
SCH1369
SNMP trap: No
reserved for the CPN mnemonic. No other mnemonic except NUL can be
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1608 of 2360

SCH1370
On the M3903, M3904 and M3905, keys 29-31 are reserved.

Action:
Severity: Info.
SCH1371
SNMP trap: No
On the M3903, M3904, and M3905 MWK is reserved for key 16. No other
mnemonic except NUL can be configured on this key.
Action:
Severity: Info.
SCH1372
SNMP trap: No
Key 7 is blocked on this set.

Action:
Severity: Info.
SCH1373
SNMP trap: No
Key number entered exceeds the maximum number of keys allowed with 2
KBAs.
Action:
Severity: Info.
SCH1374
SNMP trap: No
On the M3904 and M3905, KBAs and DBAs are mutually exclusive. If 1 or 2
was entered at KBA prompt, 0 or carriage return must be entered at DBA
prompt.
Action:
Severity: Info.
SCH1375
SNMP trap: No
Keys 12-15 are not supported on M3904 or M3905.

Action:
Severity: Info.
SCH1376
SNMP trap: No
Only NUL or PROG can be assigned to key 7 on the M3905.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1609 of 2360

SCH1377
On the M3903, the maximum key number supported is 31.

Action:
Severity: Info.
SCH1378
SNMP trap: No
DTA Class of Service is not allowed for units 0-15 on 24 Port DLC.
Action:
Severity: Minor.
SCH1379
SNMP trap: No
DCS no supported package #350 restricted.

Action:
Severity: Minor.
SCH1380
SNMP trap: No
Index already used by another VTN.

Action:
Severity: Minor.
SCH1381
SNMP trap: No
Virtual TNs can only be copied to phantom loops.

Action:
Severity: Minor.
SCH1382
SNMP trap: No
Mixing concentrated and non-concentrated DECT unit on same card.

Action:
Severity: Minor.
SCH1384
SNMP trap: No
HMDN must be entered for a ViSITor.

Action:
Severity: Minor.
SCH1385
SNMP trap: No
Entered HMDN is not a valid network DN.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 1610 of 2360

SCH1387
CTR1 and CTR2 are mutually exclusive.

Action: Use XCTR to remove either CTR1 or CTR2 before entering the new
mnemonic at PR_TRIGS prompt.
Severity: Minor.
SCH1388
SNMP trap: No
The CCOS or SAR package is restricted.

Action:
Severity: Info.
SCH1389
SNMP trap: No
MOV command is not applicable to DCS sets.

Action:
Severity: Info.
SCH1390
SNMP trap: No
CLS CCSA is required for CLS SLKA.

Action:
Severity: Info.
SCH1391
SNMP trap: No
All appearances of MADN must be defined with CLS FXSP.

Action: Correct in LD 11.
Severity: Info.
SCH1393
SNMP trap: No
List is full.
Action: Delete any unused entries.
Severity: Info.
SCH1394
SNMP trap: No
Cannot accept CLS AGRA: No AGP MADN defined in Customer Data Block.
Action: Enter in LD 15 first.
Severity: Info.
SCH1395
SNMP trap: No
On the M3903, M3904 and M3905, key 28 is reserved for the RLT mnemonic.
No other mnemonic except NUL can be configured on that key
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1611 of 2360

SCH1412
Unit type must be 2616 for this CLS.

Action:
Severity: Info.
SCH1413
SNMP trap: No
KEY mnemonic must be MCR .

Action:
Severity: Info.
SCH1414
SNMP trap: No
An appearance of this agent DN has CLS FXSP.

Action: Out the appearance in LD 11.
Severity: Info.
SCH1415
SNMP trap: No
No CORPDIR*.CVS files found in c:/u/db. Corporate Directory feature cannot

be used.
Action:
Severity: Info.
SCH1417
SNMP trap: No
Cannot remove last port while FXS_DN still defined in customer data block.
Action: Configure a flexible services port and retry.
Severity: Minor.
SCH1420
SNMP trap: No
Attendant is in conflict with existing DN or special service prefix.

Action:
Severity: Info.
SCH1425
SNMP trap: No
The CLT or RLT mnemonic can only be used on the M3903, M3904 or M3905
terminals.
Action:
Severity: Info.
SCH1426
SNMP trap: No
Default CLT or RLT key has been deleted as a same function key was
configured on a Programmable Feature Key.
Action: Configure the default key if necessary.
Severity: Info.
SNMP trap: No
System Messages
Page 1612 of 2360

SCH1427
Predefined set-to-set message file for the selected language cannot be loaded
from the disk.
Action: Select another language and report the problem to the vendor.
Severity: Major.
SCH1428
SNMP trap: No
On the M3903, M3904 and M3905, key 27 is reserved for the CLT mnemonics.
No other mnemonic except NUL can be configured on that key.
Action:
Severity: Info.
SCH1429
SNMP trap: No
On the M3903, M3904 and M3905 key 28 is reserved for the RLT mnemonic.
No other mnemonic except NUL can be configured on that key.
Action:
Severity: Info.
SCH1430
SNMP trap: No
The route must have an IDC table associated when SDID is enabled.
Action:
Severity: Info.
SCH1431
SNMP trap: No
The M3900 Phase III Virtual Office Enhancement package is not equipped.
Action:
Severity: Info.
SCH1432
SNMP trap: No
The M3900 Phase III Productivity Enhancement package is not equipped.

Action:
Severity: Info.
SCH1433
SNMP trap: No
SCB cannot be configured when the number of queues with RPRT = Yes
exceeds 240. ADS cannot be configured when RPRT = Yes exceeds 240 and
MAX is using a protocol <=.RLS23_PROTOCOL.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1613 of 2360

SCH1434
RPRT cannot be made Yes for more than 240 queues if:
a) SCB is configured
b) ADS is configured and MAX is using a protocol <=.RLS23_PROTOCOL.
Action:
Severity: Info.
SCH1435
SNMP trap: No
RPRT cannot be made Yes when both ADS and SCB are configured and the
total number of queues with RPRT = Yes is already equal to 240. One of the
blocks has to be removed.
Action: Out ADS if C- Report is required. Out SCB if MAX reporting is required.
Severity: Info.
SCH1436
SNMP trap: No
Key cannot be configured when CLS (FDSA/NOVA) is denied.

Action:
Severity: Info.
SCH1437
SNMP trap: No
PONW_PACKAGE is restricted. CLS is not allowed.

Action: Enable the package.
Severity: Info.
SCH1438
SNMP trap: No
The number of Wireless Visitors in the system exceeds the maximum number
of Wireless Visitors defined in the ISM parameters.
Severity: Info.
SCH1439 l s c u
SNMP trap: No
The set at this TN is a Digital Cordless Set. The MC32 package (350) is
restricted. Digital Cordless Sets required the MC32 package. The data block
for this set is not loaded.
Action: Reload with package enabled, or with a database not containing DCSs.
Severity: Critical.
SCH1440
SNMP trap: No
The CLT or RLT key can only be configured on the main terminal, not on a
DBA or KBA.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1614 of 2360

SCH1441
Missing software for CLKC card (NTRB53) on disk.

Severity: Info.
SCH1442
SNMP trap: No
XTRK type does not match the TN entered. The TN has to be in a Virtual Loop
for VTRK.
Action:
Severity: Info.
SCH1443
SNMP trap: No
The SPDC card is not supported in small systems.

Action: Use the DCHI instead.
Severity: Info.
SCH1444
SNMP trap: No
MOV cmd not supported for D-channel over IP.

Action:
Severity: Info.
SCH1445
SNMP trap: No
Unit type configured on PBX card is not defined.

Action:
Severity: Major.
SCH1446
SNMP trap: No
The Virtual Office package for IP phones is not equipped.

Action:
Severity: Info.
SCH1447
SNMP trap: No
You are configuring key 6 to a mnemonic other than NUL (for the Directory
Key) on this 3905 telephone. Redefining this key overrides the user's access
to Directory.
Action:
Severity: Minor.
SCH1449
SNMP trap: No
CLS VOLA/VOLD and VOUA/VOUD are for IP phones.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1615 of 2360

SCH1450
This type of TN is not valid for Set based D-Channel monitoring.

Action:
Severity: Info.
SCH1451
SNMP trap: No
OVLP_PACKAGE is restricted hence OVLS/OVLR cannot be configured as

YES.
Action:
Severity: Info.
SCH1452
SNMP trap: No
SNMP trap: No
TBCT is not configured.

Action:
Severity: Info.
SCH1453
Cannot change data while route still enabled.

Action:
Severity: Info.
SCH1454
SNMP trap: No
The size of high-priority and/or low-priority input buffers are not big enough for
this specific configuration.
Action: Change the LPIB and HPIB to at least 1000 in LD17. Warm start the
system to put the change into effect.
Severity: Info.
SCH1455
SNMP trap: No
Attempting to configure RCAP as MQC when RCAP is already configured as

QMWI/QMWO or vice-versa.
Action:
Severity: Minor.
SCH1456
SNMP trap: No
Warning: The country code, national access code and international access
code have not been entered in overlay 15.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1616 of 2360

SCH1457
Attempt to configure RCAP UUI without UUI package.

Action:
Severity: Minor.
SCH1458
SNMP trap: No
RCAP UUI only allowed for ESS4/ESS5 interfaces.

Action:
Severity: Minor.
SCH1459
SNMP trap: No
Attempt to configure ICON without ICON package.

Action:
Severity: Minor.
SCH1460
SNMP trap: No
OAS Package is not equipped.

Action:
Severity: Minor.
SCH1461
SNMP trap: No
Either the Customer Number is not same as the set under service change
configuration or the first entry of the SCL is not a position ID.
Action:
Severity: Warning.
SCH1462
SNMP trap: No
For Service request CHG of Class Of Service OUSD to OUSA an SCL number
needs to be associated with OBV key.
Action:
Severity: Warning.
SCH1463
SNMP trap: No
PCA ISM exhausted / insufficient

Action:
Severity: Minor.
SCH1464
SNMP trap: No
PCA package not equipped

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1617 of 2360

SCH1465
Target DN in Customer Data Block and Target DN in HOT key cannot both be
blank. A minimum of one DN must be defined.
Action: Make sure that at least one of the target DN is not Blank
Severity: Minor.
SCH1466
SNMP trap: No
Removal of TPDN may affect the R26 PCA functionality.

Action:
Severity: Warning.
SCH1467
SNMP trap: No
PCA configuration requires that Key 1 be configured as a HOT P Key.

Action:
Severity: Minor.
SCH1468
SNMP trap: No
Call Pickup is not allowed on telephones in group zero.

Action:
Severity: Info.
SCH1469
SNMP trap: No
Loop/Shelf/Card/Unit you are trying to access is disabled because the support

to this hardware has been stopped. No further operations on these TNs are
possible. Please use overlay 81 to list all the components that are affected on
your system.
Action:
Severity: Minor.
SCH1470
SNMP trap: No
Hebrew is supported only on M3904 sets.

Action: Select another language for this set.
Severity:
SCH1471
SNMP trap: No
SCB/ADS Block is not configured for this customer.

Action: No action other than printing the error messages.
Severity: Warning.
SNMP trap: No
System Messages
Page 1618 of 2360

SCH1472
Observe Password Table already exist.

Action: No action other than printing the error messages.
Severity: Warning.
SCH1473
SNMP trap: No
The combination of signaling and trunk type is not acceptable in United

Kingdom (Package 190).
Action: Enter a valid input acceptable in United Kingdom. Or if Package 190
(UK) is equipped by mistake, delete the package.
Severity: Info.
SCH1474
SNMP trap: No
Supervisor ID already exists.

Action:
Severity: Minor.
SCH1475
SNMP trap: No
Password required for the Supervisor ID entered in ADPD prompt.

Action:
Severity: Minor.
SCH1476
SNMP trap: No
Observe Password Table does not exist.

Action:
Severity: Major.
SCH1477
SNMP trap: No
Not enough PDS available to create Observe Password Table.

Action:
Severity: Critical.
SCH1478
SNMP trap: No
Pointer to Observe Password Table does not exist.

Action:
Severity: Major.
SCH1479
SNMP trap: No
LST is not a valid request for OBVP prompt in LD 23.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1619 of 2360

SCH1480
Upper flash out-of-range.

Action:
Severity: Info.
SCH1481
SNMP trap: No
ACD is not allowed for i2001.

Action:
Severity:
SCH1482
SNMP trap: No
Maximum allowed entries for OBVP table is 240.

Action: No action other than printing error.
Severity: Minor.
SCH1483
SNMP trap: No
Entry does not exist in OBVP table.

Action: No action other than printing error.
Severity: Minor.
SCH1484
SNMP trap: No
Invalid XTRK type. Enter MC8, MC32, ITG8, ITGP or VTRK.

Action:
Severity: Info.
SCH1485
SNMP trap: No
VTRK is not a valid XTRK type for VGW tn types.

Action:
Severity: Info.
SCH1486
SNMP trap: No
Invalid input. Enter MC8 or MC32.

Action:
Severity: Info.
SCH1487
SNMP trap: No
Invalid input, Enter ITG8 or ITGP.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1620 of 2360

SCH1488
IP Peer SIP Trunks ISM Exhausted/Insufficient.

Severity: Info.
SCH1489
SNMP trap: No
H.323 Virtual Trunk package not equipped.

Action:
Severity: Minor.
SCH1490
SNMP trap: No
The number of IP Peer H.323 Trunks in the system exceeds the maximum
number of IP Peer H.323 Trunks defined in the ISM parameter.
Severity: Info.
SCH1491
SNMP trap: No
For DCH on IP Channel, numbers from 383 to 682 are invalid.

Action:
Severity: Minor.
SCH1492
SNMP trap: No
OBVP table has reached maximum limit.

Action:
Severity: Minor.
SCH1493
SNMP trap: No
AAA and AFNA are mutually exclusive and cannot be configured for the same
customer.
Action: If you are configuring AAA, disable AFNA in overlay 15, if you are
configuring AFNA, disable AAA in overlay 15.
Severity: Info.
SCH1494
SNMP trap: No
CAS and NAS are mutually exclusive and cannot be configured for the same
customer.
Action: If you are configuring CAS, disable NAS in overlay 86; if you are
configuring NAS, disable CAS in overlay 15.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1621 of 2360

SCH1495
The TN "## ##" not configured

Action:
Severity: Info.
SCH1496
SNMP trap: No
No IP sets associated with the IP address "###.###.###.###"

Action:
Severity: Info.
SCH1497
SNMP trap: No
No IP sets associated with the DN "###"

Action:
Severity: Info.
SCH1498
SNMP trap: No
The customer number "##" is invalid.

Action:
Severity: Info.
SCH1499
SNMP trap: No
rfcCall in function "function_name" failed.

Action:
Severity: Info.
SCH1500
SNMP trap: No
DN is used elsewhere and cannot be used as an attendant access code.

Action:
Severity: Info.
SCH1501
SNMP trap: No
SNMP trap: No
Invalid DN.
Action:
Severity: Info.
SCH1502
No value is assigned to attendant value code.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1622 of 2360

SCH1503
Conflict between special function prefix and night number.

Action:
Severity: Info.
SCH1505
SNMP trap: No
Customer data block may be removed: attached data = route, flexible tones
and ringing data, Flexible Feature Code, attendant DN and/or NFCR data.
Action:
Severity: Info.
SCH1506
SNMP trap: No
The IP Address "###.###.###.###" is invalid.

Action:
Severity: Info.
SCH1507
SNMP trap: No
The MAP command wasn't processed completely.

Action: Please try again. If the case repeats, contact your technical support
group.
Severity: Info.
SCH1508
SNMP trap: No
CFW must be entered for DCS sets.

Action: Enter CFW at the FTR prompt.
Severity: Minor.
SCH1509
SNMP trap: No
Cannot MOV/OUT acquired TN. First De-acquire the TN and then proceed
with MOV/OUT request
Action: De-acquire the TN and then proceed with MOV/OUT operation.
Severity: Minor.
SCH1510
SNMP trap: No
SNMP trap: No
Invalid CLS input.

Action:
Severity: Minor.
SCH1511
CLS FEDA/FEDD applies to DCS sets only.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1623 of 2360

SCH1512
Input out of range.

Action: Enter a valid value.
Severity: Minor.
SCH1513
SNMP trap: No
The entered SSRC value exceeds the value supported by the Signaling Server
in this release. This might result in failure of registration of some Virtual
Trunks.
Action:
Severity: Warning.
SCH1514
SNMP trap: No
The ISL Trunks still exist. Decreasing the SSRC below the existing value is not
allowed.
Action:
Severity: Minor.
SCH1515
SNMP trap: No
The SSRC limit has been exhausted. No further Trunks can be configured.
Action:
Severity: Minor.
SCH1516
SNMP trap: No
MCA card supports only keys 0-7.

Action: Move the key functions of the voice set in the range 0-7 if you intend to
use MCA.
Severity: Minor.
SCH1517
SNMP trap: No
DEFAULT has been entered, however, the values of NAV_SITE_NAME,

NAV_SYSTEM_NAME and HOSTNAME are all empty values.
Action: Configure one of the values prior to using the CHG SNMP_SYSNAME
command with a value of DEFAULT.
Severity: Info.
SCH1518
SNMP trap: No
The import of the EPT file was not successful.

Action: Check to ensure that a PC Card/floppy disk is inserted and a valid EPT
file exists on that media.
Severity: Info.
SNMP trap: No
System Messages
Page 1624 of 2360

SCH1519
The export of the EPT file was not successful.

Action: Check to ensure that a PC Card/floppy disk is inserted.
Severity: Info.
SCH1520
SNMP trap: No
Swap command is not applicable to PRA loops.

Action:
Severity: Minor.
SCH1521
SNMP trap: No
IFC type of the D-channel on the source loop has to match to one on the
destination loop.
Action:
Severity: Minor.
SCH1522
SNMP trap: No
D-channel has been moved from the source loop to the destination loop.
Action: Please check the GRP (group #) and DEV (device #) of the D-channel
and modify in LD 17 if necessary.
Severity: Info.
SCH1523
SNMP trap: No
Unequipped IPMG package is required for IPMG superloop configuration.

Action: Contact your Nortel representative if IPMG package is required.
Severity: Info.
SCH1524
SNMP trap: No
Loop for VXCT0/VXCT1 is invalid; must be the first of two consecutive VXCT
loops and not be associated with another IPMG.
Action: Configure loop as VXCT loop in LD 17.
Severity: Info.
SCH1525
SNMP trap: No
Cannot delete VXCT0/VXCT1 for new superloop or existing superloop with no

VXCT0/VXCT1 configured.
Action: Press ENTER to skip the prompt.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1625 of 2360

SCH1526
Number of VCNF loops is out of range or included loops are not VXCT loops.
Action: Enter valid number of VCNF loops to include unused VXCT loops.
Severity: Info.
SCH1527
SNMP trap: No
Number of ENET loops out of range or included loops are not ENET loops.
Action: Enter a valid number.
Severity: Info.
SCH1528
SNMP trap: No
Attempt to configure CLS CDMO or CDMV on PCA.

Action:
Severity: Info.
SCH1529
SNMP trap: No
The Signaling Server for this DCIP has not established its pbxLink to the Call
Server. SSRC value supported by the Signaling Server is currently
unavailable.
Action:
Severity: Info.
SCH1530
SNMP trap: No
FTC block already exists.

Action:
Severity: Info.
SCH1531
SNMP trap: No
FTC block does not exist.

Action:
Severity: Info.
SCH1532
SNMP trap: No
Cannot have code restriction data on TIE trunks.

Action:
Severity: Info.
SCH1533
SNMP trap: No
Cannot delete IPR0 or IPR1 for new superloop.

Action: Press ENTER to skip the prompt.
Severity: Info.
SNMP trap: No
System Messages
Page 1626 of 2360

SCH1534
IP address for IPR0 or IPR1 is invalid format.

Action: IP address in nnn.nnn.nnn.nnn format.
Severity: Info.
SCH1535
SNMP trap: No
Duplicate IP address, already assigned to another IPMG.

Action: Enter a different IP address.
Severity: Info.
SCH1536
SNMP trap: No
Failed to save IPR0, ZONE0, IPR1, or ZONE1.

Action: Reconfigure IPR0, ZONE0, IPR1, and ZONE1.
Severity: Info.
SCH1537
SNMP trap: No
Outing VXCT loops associated with an IPMG not allowed.

Action: Dissociate VXCT loop from the IPMG in Overlay 97.
Severity: Info.
SCH1538
SNMP trap: No
One or more loops of the two VXCTs are enabled

Action: Disable all loops in both VXCTs
Severity: Info.
SCH1539
SNMP trap: No
Input is invalid for this prompt

Action:
Severity: Info.
SCH1540
SNMP trap: No
FTC class one data already exists.

Action:
Severity: Info.
SCH1541
SNMP trap: No
FTC class two data already exists.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1627 of 2360

SCH1542
FTC class three data already exists.

Action:
Severity: Info.
SCH1543
SNMP trap: No
FTC class one data does not exist.

Action:
Severity: Info.
SCH1544
SNMP trap: No
FTC class two data does not exist.

Action:
Severity: Info.
SCH1545
SNMP trap: No
FTC class three data does not exist.

Action:
Severity: Info.
SCH1546
SNMP trap: No
Response to prompt MTHD must CNT or ANL.

Action:
Severity: Info.
SCH1547
SNMP trap: No
A valid method must be entered.

Action:
Severity: Info.
SCH1548
SNMP trap: No
A maximum must be entered.

Action:
Severity: Info.
SCH1549
SNMP trap: No
Response to prompt REQ must be NEW, OUT, CHG, REM or END.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1628 of 2360

SCH1550
Input zone is not configured

Action: Configure zone in Overlay 117
Severity: Info.
SCH1551
SNMP trap: No
Response to REQ was NEW. Response to FTC REQ must be NEW

Action:
Severity: Info.
SCH1552
SNMP trap: No
Response to prompt REQ must be NEW, OUT, CHG, REM or END.

Action:
Severity: Info.
SCH1553
SNMP trap: No
Illegal character entered for Username .Must be A-Z,a-z or 0-9

Action: Enter an alphanumeric word.
Severity: Info.
SCH1554
SNMP trap: No
User name already exists.

Action: Try another one or delete an existing account
Severity: Info.
SCH1555
SNMP trap: No
Response to CLS TYPE must be one of ONE, TWO, or THREE.

Action:
Severity: Info.
SCH1556
SNMP trap: No
Invalid access code (4 digits maximum).

Action:
Severity: Info.
SCH1557
SNMP trap: No
Too many access codes (maximum 15).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1629 of 2360

SCH1558
Response to BYPS must be YES or NO.

Action:
Severity: Info.
SCH1559
SNMP trap: No
Response to CLR must be ALOW or DENY.

Action:
Severity: Info.
SCH1560
SNMP trap: No
Code length out-of-range (must be 3 digits).

Action:
Severity: Info.
SCH1561
SNMP trap: No
Code cannot be restricted. Does not match a previously entered access code.
Action:
Severity: Info.
SCH1562
SNMP trap: No
Code cannot be removed. Does not exist in data.

Action:
Severity: Info.
SCH1563
SNMP trap: No
All the available lapw blocks are full.

Action: Delete an existing lapw account and try again
Severity: Info.
SCH1564
SNMP trap: No
Invalid response to CONG. Must be one of BUSY, OVFL, or {CR}.

Action:
Severity: Info.
SCH1565
SNMP trap: No
Changing the SNMP MIB2 data was not successful.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1630 of 2360

SCH1566
Invalid response to PAGEOFST prompt.

Action: Enter valid number 0 or 1. Press <CR> to skip the prompt.
Severity: Info.
SCH1567
SNMP trap: No
Invalid response to KEMOFST prompt.

Action: Enter valid number 1 or 2. Press <CR> to skip the prompt.
Severity: Info.
SCH1568
SNMP trap: No
Invalid KEM KEY number was entered.

Action: Enter valid number in the range of 0 to 23.
Severity: Info.
SCH1569
SNMP trap: No
Enbloc route being configured as an alternative for an overlap route or an

Overlap route being configured as an alternative for an Enbloc route. Alternate
routing may not work.
Action: All of the routes configured in one RLI must all be either overlap or
enbloc.
Severity: Info.
SCH1570
SNMP trap: No
Invalid time of day: [0-23]:[0-59].

Action:
Severity: Info.
SCH1571
SNMP trap: No
Software error.
Action: Contact manufacturer.
Severity: Info.
SCH1572
SNMP trap: No
% Invalid Repeat Counter for this type of trunk, MAX is 255.

Action:
Severity:
SCH1573
SNMP trap: No
% Member number increment out-of-range (0-511).

Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1631 of 2360

SCH1574
Member Number out of Range. For Virtual Trunks the limit is 1-4000. For all
other trunks the limit is 1-510.
Action:
Severity: Minor.
SCH1575
SNMP trap: No
The set with CDMO/CDMV cannot be Tenant Service Allowed, and vice versa.
Action:
Severity: Info.
SCH1576
SNMP trap: Yes
NEW BKPR command - Backup rule <rule number> already exists

Action: Re-enter the command, using a free rule number
Severity: Info.
SCH1577
SNMP trap: No
CHG/PRT/OUT BKPR command - Backup rule <rule number> does not exist.
Action: Re-enter the command, using the correct rule number
Severity: Info.
SCH1578
SNMP trap: No
Geographic Redundancy feature not equipped

Action: Equip GRPRIM or GRSEC package
Severity: Info.
SCH1579
SNMP trap: No
ELAN Links less than 32 cannot be associated with VAS IDs greater than or
equal to 32 and vice versa.
Action:
Severity: Minor.
SCH1580
SNMP trap: No
SIP Package is restricted.

Action:
Severity: Critical.
SCH1581
SNMP trap: No
Unacceptable IP address. Each Echo Server must have a unique IP address.

Action: Assign a unique IP address.
Severity: Info.
SNMP trap: No
System Messages
Page 1632 of 2360

SCH1582
OUT BKPR command - Rule <rule number> in use in the GRDRC block
Action:
Severity: Info.
SCH1583
SNMP trap: No
NEW GRDRC command -GRDRC block already configured

Action:
Severity: Info.
SCH1584
SNMP trap: No
CHG/PRT/OUT GRDRC command - GRDRC block does not exist

Action:
Severity: Info.
SCH1585
SNMP trap: No
NEW GRSC command - GRSC block already configured

Action:
Severity: Info.
SCH1586
SNMP trap: No
CHG/PRT/OUT GRSC command - GRSC block does not exist

Action:
Severity: Info.
SCH1587
SNMP trap: No
NEW/CHG BKPR command - Wrong number of parameters

Action:
Severity: Info.
SCH1588
SNMP trap: No
Permanent Call Hold feature is not supported for DECT sets in concentrated
mode or in non-concentrated mode.
Action:
Severity: Info.
SCH1589
SNMP trap: No
Permanent Call Hold feature has been removed from the configured set, since
the feature is not supported for DECT sets in concentrated mode or in
non-concentrated mode.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1633 of 2360

SCH1590
Attempted to enable the Adaptive Bandwidth Management feature on a Virtual

Trunk (VTRK) zone.
Action: Cannot enable the virtual trunk zone as part of the Adaptive Bandwidth
Management feature.
Severity: Info.
SCH1591
SNMP trap: No
The adaptive bandwidth management feature cannot be enabled for zone 0.

Action: Use a non-zero (0) zone for the adaptive bandwidth management
feature.
Severity: Info.
SCH1592
SNMP trap: No
Warning: RCAP RLTI requires the RCAP TAT. System is turning on RCAP
TAT to enable the RLTI capability.
Action: If RLTI is desired, no corrective action required. If it is not, disable RLT
and TAT.
Severity: Info.
SCH1593
SNMP trap: No
Warning: RCAP XRLT may make RCAP TAT un-necessary. The user may
wish to disable TAT as well.
Action: If RLTI is desired, add RCAP RLTI. If it is not, and TAT is not needed,
use RCAP XTAT. Otherwise, do nothing.
Severity: Info.
SCH1594
SNMP trap: No
Warning: RCAP RLTI requires the RCAP TAT. System is turning off RLTI to
match the new TAT settings.
Action: If RLTI is not required, no action required. If it is required, re-enable RLTI
and TAT.
Severity: Info.
SCH1595
SNMP trap: No
Unable to match input fields for ACCOUNT REQ prompt.

Action: Enter NEW,CHG or OLD.
Severity: Info.
SNMP trap: No
System Messages
Page 1634 of 2360

SCH1596
Unable to match input fields for PSWD_COMP prompt.

Action: Valid inputs are ON/OFF. Default is OFF.
Severity: Info.
SCH1597
SNMP trap: No
You have entered an invalid response for the prompt PSWD_TYPE.

The system is unable to match the field input with the stored mnemonics.
Action: Enter PWD1,PWD2 or LAPW
Severity: Info.
SCH1598
SNMP trap: No
Entered Password doesn't match with the previous one.Password should be

same in both PASSWORD/NEWPASSWORD prompt and CONFIRM prompt.
Action: Enter the password again.
Severity: Info.
SCH1599
SNMP trap: No
The CRA Class of Service is applied to an IP phone only.

Action:
Severity: Info.
SCH1600
SNMP trap: No
TN 252 1 15 31 is reserved to indicate the Network Home is CS 2100/2000.

It must not be used if the Main Office or Network Home is CS 1000.
Action: If the Main Office or Network Home is CS 1000, choose a different TN.
Severity: Info.
SCH1601
SNMP trap: No
ACCNEW API is not successful

Action:
Severity: Info.
SCH1602
SNMP trap: No
ACCTSTYPES API is not successful

Action:
Severity: Info.
SCH1603
SNMP trap: No
ACCTSROLES API is not successful

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1635 of 2360

SCH1604
Password complexity check failed. Password Rules are: must be at least 8

characters long; must not contain the user name in forward or reverse order;
must not have a keyboard trail; must not repeat; must not have 4 or more
consecutive characters of the same type (character types are: lower case
alpha, upper case alpha and numeric); must not have 5 or more consecutive
alpha characters.
Action: Please try another password.
Severity: Info.
SCH1605
SNMP trap: No
Failed to access the account database, password change aborted. Please try
again.
Severity: Info.
SCH1606
SNMP trap: No
Failed to access the account database, requested changes have been

discarded. Please try again.
Severity: Info.
SCH1607
SNMP trap: No
Failed to access the account database, requested delete has been aborted
Please try again.
Severity: Info.
SCH1608
SNMP trap: No
Failed to change the lock-out duration. Please try again.

Severity: Info.
SCH1609
SNMP trap: No
Failed to change the failed login threshold. Please try again.

Severity: Info.
SCH1610
SNMP trap: No
Failed to change the password complexity setting. Please try again.

Severity: Info.
SNMP trap: No
System Messages
Page 1636 of 2360

SCH1611
IMPORTANT! Network Bandwidth Management does not support zone 0.

Action:
Severity: Info.
SCH1612
SNMP trap: No
Virtual Trunk zone is not allowed to be assigned to IP or DSP.

Action: Check Zone Intent in the LD 117.
Severity: Minor.
SCH1613
SNMP trap: No
Only Virtual Trunk zone is allowed.

Action: Check Zone Intent in the LD 117.
Severity: Minor.
SCH1614
SNMP trap: No
Branch Office Zone cannot be assigned to DSP channels on Main Office and
vice versa.
Action: Check Zone Intent in LD 117.
Severity: Minor.
SCH1615
SNMP trap: No
TN 252 1 15 31 is reserved to indicate the Network Home is CS 2100/2000.

i2050 SoftPhone is not supported by CS2100/CS2000.
Action: If the Main Office or Network Home is CS 1000, choose a different TN.
Severity: Info.
SCH1616
SNMP trap: No
% print an error if i2001, i2050 or CPVIP tries to access KEM3/KEM2 cls.

Action:
Severity:
SCH1617
SNMP trap: No
% print an error if IP Phone 2005 tries to use KEM2 cls.

Action:
Severity:
SCH1618
SNMP trap: No
% max KEM value does not match with the reqd cls criteria. Changing KEM
value to the max value allowed for the given cls.
Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1637 of 2360

SCH1619
User name does not exist

Action: Please ensure you are using correct username
Severity: Info.
SCH1620
SNMP trap: No
"Automatic BKPS <schedule number> already exists " Attempt to define more
than one auto backup schedule.
Action:
Severity: Info.
SCH1621
SNMP trap: No
"Bkpr <rule number> is used by bkps <schedule number>" Attempt to remove

backup rule used by backup schedule.
Action:
Severity: Info.
SCH1622
SNMP trap: No
"Bkps refers to an unexisting bkpr <rule number>" Attempt to add/change bkps

referring to unexisting bkpr.
Action:
Severity: Info.
SCH1623
SNMP trap: No
"Auto bkps and auto GRDRC are mutually exclusive" Attempt to define auto
bkps and auto grdrc at the same time.
Action:
Severity: Info.
SCH1624
SNMP trap: No
"Bkps <schedule number> already exists" Attempt to add an already existing

bkps.
Action:
Severity: Info.
SCH1625
SNMP trap: No
"Bkps <schedule number> does not exist" Attempt to remove/change bkps

which does not exist.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1638 of 2360

SCH1626
"The type of rule <rule number> is <rule type> instead of SCS" Attempt to
define GRDRC with rule which type is not SCS.
Action:
Severity: Info.
SCH1649
SNMP trap: No
Password for PDT2/PDT1 cannot be changed through LD 17.

Action: Use "passwd" cmd at pdt prompt.
Severity: Info.
SCH1650
SNMP trap: No
CLSs CDMR and MCDA are mutually exclusive.

Action: Configure CDMO or CDMV CLS.
Severity: Info.
SCH1651
SNMP trap: No
The number of Converged Desktop sets has reached the allowed ISM limit.
Action:
Severity: Minor.
SCH1652
SNMP trap: No
The number of Microsoft Convergence Gold Level sets has reached the
allowed ISM limit.
Action:
Severity: Minor.
SCH1653
SNMP trap: No
Microsoft Convergence package is restricted.

Action:
Severity: Minor.
SCH1677
SNMP trap: No
Service change is not allowed on unit currently involved in a CPCI call.

Severity: Info.
SCH1699
SNMP trap: No
SCL (Command/Status Link Base) package is restricted.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1639 of 2360

SCH1700
Threshold data must be defined prior to group data.

Action:
Severity: Info.
SCH1701
SNMP trap: No
Threshold block does not exist.

Action:
Severity: Info.
SCH1702
SNMP trap: No
Threshold block already exists.

Action:
Severity: Info.
SCH1703
SNMP trap: No
Threshold value out-of-range.

Action:
Severity: Info.
SCH1704
SNMP trap: No
All groups must be removed before the threshold block may be removed.
Action:
Severity: Info.
SCH1705
SNMP trap: No
Loop to be removed for member x does not match data for member x.
Action:
Severity: Info.
SCH1706
SNMP trap: No
Invalid loop number (i.e. loop is already a member, loop is not disabled or is
not an RPE loop).
Action:
Severity: Info.
SCH1707
SNMP trap: No
Group number is out-of-range (SL-1A and LE 1-5, VLE 1-31).

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1640 of 2360

SCH1708
Loop number (address) is out-of-range.

Action:
Severity: Info.
SCH1709
SNMP trap: No
RPE2 package not present on tape.

Action:
Severity: Info.
SCH1866
SNMP trap: No
NMCE package not equipped.

Action:
Severity: Info.
SCH1867
SNMP trap: No
Warning: The ISA master route cannot have any RLI pointing towards itself.
Action: Check whether this route is associated with any RLI. Remove all RLI's
associated with this route.
Severity: Info.
SCH1868
SNMP trap: No
Class of service being changed to SPCD as the class of service has been
changed to MID.
Action:
Severity: Info.
SCH1869
SNMP trap: No
SPCA Class of service only allowed for IPE, TIE, E&M trunks with MIA class
of service.
Action:
Severity:
SCH1870
SNMP trap: No
The number of digital telephones in the system exceeds the maximum number
of digital telephones allowed.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1641 of 2360

SCH1871
The number of analog telephones in the system exceeds the maximum

number of analog telephones allowed.
Action:
Severity: Info.
SCH1872
SNMP trap: No
Warning: Do not configure a non-CallPilot CDN as AODN.

Action: The CDN you have entered will be accepted if you continue through the
Overlay. However, if you have entered a non-CallPilot CDN please leave the
overlay (****) and re-enter, or re-start the overlay (**).
Severity: Major.
SCH1873
SNMP trap: No
Key 7 is blocked on this set.

Action:
Severity: Info.
SCH1874
SNMP trap: No
Attempt to configure RCAP UUS1 without BNE package equipped.

Action:
Severity: Info.
SCH1875
SNMP trap: No
RCAP UUS1 only allowed for EURO/E403.

Action:
Severity:
SCH1876
SNMP trap: No
Attempt to configure RCAP with a EuroISDN diversion remote capability

whereas the BNE package is restricted.
Action: Do not configure the unexpected remote capability as it has no effect
without the missing package.
Severity:
SCH1877
SNMP trap: No
Model sets can not have SIP CTI TR87 (T87A) CLS.
Severity: Minor.
SNMP trap: No
System Messages
Page 1642 of 2360

SCH1878
CLS T87A is not allowed unless AST is defined.

Severity: Minor.
SCH1879
SNMP trap: No
CLS T87A needs at least one AST defined.

Severity: Minor.
SCH1880
SNMP trap: No
The number of ISDN B Channel TNs in the system exceeds the maximum
number allowed.
Action:
Severity: Info.
SCH1881
SNMP trap: No
The number of DTI Channel TNs in the system exceeds the maximum number
allowed.
Action:
Severity: Info.
SCH1882
SNMP trap: No
The number of Analog Trunk Tns in the system exceeds the maximum number
allowed.
Action:
Severity: Info.
SCH1883
SNMP trap: No
The number of Data Port TNs in the system exceeds the maximum number
allowed.
Action:
Severity: Info.
SCH1884
SNMP trap: No
The number of Phantom Port TNs in the system exceeds the maximum
number allowed.
Action:
Severity: info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1643 of 2360

SCH1885
The number of CLASS Telephone TNs in the system exceeds the maximum
number allowed.
Action:
Severity: Info.
SCH1886
SNMP trap: No
The number of Attendant Consoles TNs in the system exceeds the maximum
number allowed.
Action:
Severity: Info.
SCH1887
SNMP trap: No
Attempt to configure QMWI when QMWO is already configured (or vice versa).
Action: Remove the existing MWI RCAP first.
Severity: Minor.
SCH1888
SNMP trap: No
QMWI/QMWO response to RCAP is not allowed for interfaces other than

ESGF, ISGF or EGF4.
Action:
Severity: Minor.
SCH1889
SNMP trap: No
Attempt to configure QMWI/QMWO when MQC FEAT NMS is configured or

vice-versa.
Action: Remove either of the above.
Severity: Minor.
SCH1890
SNMP trap: No
TBCT Package is not equipped.

Action: Enable TBCT Package
Severity: Info.
SCH1891
SNMP trap: No
TBCT/XTBC valid only for NI-2 interface.

Action: Enable NI-2 name display package.
Severity: Info.
SNMP trap: No
System Messages
Page 1644 of 2360

SCH1892
Corporate Directory not allowed without corporate Directory Package.

Action:
Severity: Info.
SCH1893
SNMP trap: No
Corporate Directory not allowed for this set type.

Action:
Severity: Info.
SCH1894
SNMP trap: No
Set to Set Messaging not allowed without Set to Set Messaging Packages.
Action:
Severity: info.
SCH1895
SNMP trap: No
Set to Set Messaging not allowed for this set type.

Action:
Severity: Info.
SCH1896
SNMP trap: No
No default cab type allowed when entering the first tty for each expansion cab.
Action:
Severity: Info.
SCH1897
SNMP trap: No
MOV PAIR command is not allowed across different card types (CTYP:
XDLC/EDLC).
Action:
Severity: Minor.
SCH1898
SNMP trap: No
Invalid AST keys defined, CLS T87D is set. CLS T87A is not allowed unless
valid AST is defined.
Severity: Minor.
SCH1900
SNMP trap: No
Warning: The daughterboard type is not 100BaseT or 100BaseF in the cabinet

you configured your card.
Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1645 of 2360

SCH1921
A corrupted DPNSS/DASS2 trunk is observed.

Severity: Info.
SCH1922
SNMP trap: No
Specified port not an IP port.

Action:
Severity: Info.
SCH1923
SNMP trap: No
ISM limit for survivable expansion cabinets exceeded.

Action:
Severity: Info.
SCH1924
SNMP trap: No
Not possible to set survivable capability to NO when IP expansion cabinet is

in survival mode.
Action:
Severity: Info.
SCH1925
SNMP trap: No
Not possible to set survivable capability to NO when IP link is down.

Action:
Severity: Info.
SCH1937
SNMP trap: No
The number of ITG ISDN Trunks in the system exceeds the maximum number
allowed.
Action:
Severity: Info.
SCH1938
SNMP trap: No
Last RCFA FFC cannot be deleted while FOLM and FWDT FFCs are
configured.
Action: Remove existing FOLM and FWDT FFCs.
Severity: Info.
SNMP trap: No
System Messages
Page 1646 of 2360

SCH1939
Last ERCFW (FOLM or FWDT) FFC cannot be deleted while sets are
configured with CLS = ERCA.
Action: Ensure CLS = ERCD for all sets in the customer.
Severity: Info.
SCH1940
SNMP trap: No
CLS = ERCA not accepted. Neither FOLM nor FWDT FFC configured.
Action: Configure at least one of FOLM or FWDT FFC in LD 57.
Severity: Info.
SCH1941
SNMP trap: No
Warning: Only one of FOLM or FWDT configured.

Action:
Severity: Info.
SCH1942
SNMP trap: No
Virtual Terminal must be defined on a phantom loop (Overlay 11).

Action:
Severity: Info.
SCH1943
SNMP trap: No
Virtual Terminal is not allowed to be copied (CPY) or moved (MOV), (Overlay

11).
Action:
Severity: Info.
SCH1944
SNMP trap: No
Virtual and Host Terminals are not allowed to be changed (CHG), removed
(OUT), copied (CPY) or moved (MOV) when the VO Worker is logged in
(Overlay 11).
Action:
Severity: Info.
SCH1945
SNMP trap: No
The primary DN of a Virtual Terminal is not allowed to be a primary DN for any

other TN and must be defined as the MARP DN (Overlay 11).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1647 of 2360

SCH1946
Virtual Office package is not equipped (Overlay 11, 20).

Action:
Severity: Info.
SCH1947
SNMP trap: No
Feature (Key or CLS) is not configurable on Host or Virtual Terminals (Overlay

11).
Action:
Severity: Info.
SCH1948
SNMP trap: No
Host or Virtual Terminals cannot be monitored by the BFS key (Overlay 11).
Action:
Severity: Info.
SCH1949
SNMP trap: No
Service change (CHG, OUT, CPY or MOV) is not allowed on Host or Virtual
Terminals during Virtual Office Swap process on them (Overlay 11).
Action:
Severity: Info.
SCH1950
SNMP trap: No
Service change is not allowed on Host or Virtual Terminals (Set Base

Administration, Attendant Administration).
Action:
Severity: Info.
SCH1952
SNMP trap: No
Physical I/O address already in use in the specified network group; physical
I/O address already in use for this Option 11C cabinet.
Action:
Severity: Info.
SCH1953
SNMP trap: No
Physical I/O address already used by a non-MSDL device in a different

network group/cabinet. This address can be used, in the specified group, only
for an MSDL running only DCH.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1648 of 2360

SCH1954
Physical I/O address already used by an MSDL device (running an application

different from DCH) in a different network group/cabinet, only for an MSDL
running only DCH.
Action:
Severity: Info.
SCH1955
SNMP trap: No
Error in request. Either the software is not IP equipped or command can only
be used on main cabinet.
Action:
Severity: Info.
SCH1956
SNMP trap: No
You are attempting to configure DBA with a KBA attached to the set.
Action: First input 0 with KBA prompt and then configure 1 with DBA prompt.
Severity: Info.
SCH1957
SNMP trap: No
You are attempting to configure KBA with a DBA attached to the set.
Action: First input 0 with DBA prompt and then configure 1 or 2 with KBA prompt.
Severity: Info.
SCH1958
SNMP trap: No
Command is blocked since Midnight download is triggered for the Taurus set
type.
Action:
Severity: Minor.
SNMP trap: No
SCH1960 <link#>, ABORT OVERLAY <##> NOW! Application's action on link# requires the
specified overlay to terminate immediately.
Action: Craftsperson must terminate the overlay service change activities by **
or ****.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1649 of 2360

SCH1961
You are configuring key 5 to a mnemonic other than NUL (for the Application
key) on this 3905 set. Redefining this key overrides the user's access to
remote applications.
Action: First change STSA to STSD or CRPA to CRPD and then configure key
5 to a non-NUL feature.
Severity: Info.
SCH1962
SNMP trap: No
You are enabling either Corporate Directory or Set Messaging when key 5 is
not NUL on the M3905.
Action: Please NUL key 5 first and then input STSA or CRPA at the CLS prompt.
Severity: Info.
SCH1963
SNMP trap: No
Only 16 serial I/O and DCH devices are allowed per cabinet. (CPU TTYs are
not counted against this count of 16 devices.)
Action:
Severity: Minor.
SCH1964
SNMP trap: No
Virtual Office terminals (Host and Virtual) can not be defined as Data TN.
Action:
Severity: Minor.
SCH1965
SNMP trap: No
DN of Virtual terminal can not be defined on

a Host terminal and vice versa.
Action:
Severity: Minor.
SCH1966
SNMP trap: No
i2004 sets have to be defined on virtual superloops.

Action:
Severity: Info.
SCH1967
SNMP trap: No
I2004 unit type only is allowed on virtual superloops.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1650 of 2360

SCH1968
Key 0 must be a DN key on an i2004 set (I.e. one of SCR, SCN, MCR, MCN,
PLN, PLR, ACD DN).
Action:
Severity: Info.
SCH1969
SNMP trap: No
Autodial keps (ADL) must be defined on keys 17 to 20 on an Etherset.

Action:
Severity: Info.
SCH1970
SNMP trap: No
Message Waiting Key (MWK) must be defined on key 16 on an Internet

Telephone set.
Action:
Severity: Info.
SCH1971
SNMP trap: No
TAD key is not supported on an Etherset.

Action:
Severity: Info.
SCH1972
SNMP trap: No
type 2002 and 2004 and IP Softphones type 2050 allowed to be configured in
the system. The telephone is not configured.
Action: (Recommended) Purchase additional IP User Licenses.
Severity: Info.
SCH1973
SNMP trap: No
Cannot move a virtual superloop in a non virtual superloop (or vice-versa).

Action:
Severity: Info.
SCH1974
SNMP trap: No
Cannot accept this unit as ITG cards list has reached the limit.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1651 of 2360

SCH1975
Can only create virtual loops on vacant loops.

Action:
Severity: Info.
SCH1976 <data>
SNMP trap: No
Basic IP User License counter has reached its maximum value. IP User
License was used to configure <data> basic IP Phone(s) type 2001.
Action: (Recommended) Purchase additional Basic IP User Licenses for IP
Phones type 2001, instead of using higher-priced IP User Licenses.
Severity: Info.
SCH1977
SNMP trap: No
Basic IP User License and IP User License counters have reached maximum
values. The IP Phone type 2001 is not configured.
Action: (Recommended) Purchase additional Basic IP User Licenses.
Severity: Info.
SCH1978
SNMP trap: No
Cannot OUT customer when GRP call lists still exist.

Action:
Severity: Info.
SCH1979
SNMP trap: No
DFCL is the last option for specifying CLID for an emergency call (i.e. other
mechanisms for composing a CLID have not succeeded). If DFCL is left blank
then CLID could be vacant.
Action: Enter a CLID that can be used as the last option for CLID for an
emergency call.
Severity: Warning.
SCH2000
SNMP trap: No
An attempt was made to assign a mini CDR tape unit to a customer for which
the tape was not assigned in configuration data.
Action: Assign the tape in LD 17 and return to LD 15 to assign the tape to a
customer.
Severity: Info.
SCH2002
SNMP trap: No
No CDP list exists for this CDP steering code.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1652 of 2360

SCH2003
ESN data block does not exist for this CDP steering code.
Action:
Severity: Info.
SCH2004
SNMP trap: No
No customer data block exists for this CDP steering code.

Action:
Severity: Info.
SCH2005
SNMP trap: No
Invalid CDP steering code.

Action:
Severity: Info.
SCH2006
SNMP trap: No
Wrong number of input fields for prompt NCOS.

Action:
Severity: Info.
SCH2007
SNMP trap: No
NCOS number out-of-range (0-15 for NARS, 0-3 for BARS/CDP, 0-7 for
NFCR).
Action:
Severity: Info.
SCH2008
SNMP trap: No
NCOS package must be equipped if ESN is entered.

Action:
Severity: Info.
SCH2009
SNMP trap: No
NARS package must be equipped if ETN is entered.

Action:
Severity: Info.
SCH2010
SNMP trap: No
Signaling type inconsistent with card density.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1653 of 2360

SCH2011
New unit number is too high for the new card.

Action:
Severity: Info.
SCH2012
SNMP trap: No
Off-premise extension for single density card only.

Action:
Severity: Info.
SCH2013
SNMP trap: No
Attempt to increase card density while OPX units are equipped.

Action:
Severity: Info.
SCH2014
SNMP trap: No
Existing card density too high for move/swap.

Action:
Severity: Info.
SCH2015
SNMP trap: No
Attempt to move/swap loops while upper shelves exist in the loop with lower
density.
Action:
Severity: Info.
SCH2016
SNMP trap: No
The DNIS Route must be defined as auto-terminating or IDC.

Action:
Severity: Info.
SCH2017
SNMP trap: No
This value represents a change for the CDR with Outpulsed Digits (OPD). The
change does not take effect until after the next initialization.
Action:
Severity: Info.
SCH2019
SNMP trap: No
Frame formats must be the same when moving or swapping DTI loops.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1654 of 2360

SCH2020
Moving a trunk between different loops is not permitted.

Action:
Severity: Info.
SCH2021
SNMP trap: No
DTI package not equipped.

Action:
Severity: Info.
SCH2022
SNMP trap: No
Cannot delete a non-DTI loop or add a DTI loop which is not undefined, or
make changes to a non-DTI loop.
Action:
Severity: Info.
SCH2023
SNMP trap: No
Odd loop numbers for DTI card slot not allowed.

Action:
Severity: Info.
SCH2024
SNMP trap: No
Digital trunk loop must be a DTI2, JDMI, or PRI2 loop.

Action:
Severity: Info.
SCH2025
SNMP trap: No
Primary reference loop number and secondary reference loop number cannot
be the same.
Action:
Severity: Info.
SCH2026
SNMP trap: No
Illegal input for trunk type.

Action:
Severity: Info.
SCH2027
SNMP trap: No
NCOS package and/or DTI package is restricted.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1655 of 2360

SCH2028
Digital TIE auto must be VCE or DTA only.

Action:
Severity: Info.
SCH2029
SNMP trap: No
TN to channel conversion failure.

Action:
Severity: Info.
SCH2030
SNMP trap: No
Digital data block does not exist.

Action:
Severity: Info.
SCH2031
SNMP trap: No
Digital data block already exists.

Action:
Severity: Info.
SCH2032
SNMP trap: No
Configuration loop number must be a DTI card slot.

Action:
Severity: Info.
SCH2033
SNMP trap: No
A DTI loop can only be moved to another DTI loop.

Action:
Severity: Info.
SCH2034
SNMP trap: No
A digital route is required.

Action:
Severity: Info.
SCH2035
SNMP trap: No
{CR} is allowed only if a DTI card does not exist on the network shelf.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1656 of 2360

SCH2036
Framing format has been changed from D2 to D3 or vice versa.

Action: For X11 Release 16, framing format cannot be changed while trunks
exist on the loop. Trunks associated with that loop must first be removed from the
configuration before changing the framing format.
Severity: Info.
SCH2038
SNMP trap: No
Channel to TN conversion failure.

Action:
Severity: Info.
SCH2040
SNMP trap: No
Cannot remove a digital data block while DTI loops still exist.
Action:
Severity: Info.
SCH2041
SNMP trap: No
Framing format data corruption has occurred.

Action:
Severity: Info.
SCH2042
SNMP trap: No
Protected terminal digital loop block pointer has been corrupted.

Action:
Severity: Info.
SCH2043
SNMP trap: No
LFTN must be TN with the same customer number.

Action:
Severity: Info.
SCH2044
SNMP trap: No
LUC not permitted for DTI loops.

Action:
Severity: Info.
SCH2045
SNMP trap: No

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1657 of 2360

SCH2046
Departmental LDN out-of-range.

Action:
Severity: Info.
SCH2047
SNMP trap: No
Invalid input. Attendant number is either out-of-range or an invalid input was

encountered.
Action:
Severity: Minor.
SCH2048
SNMP trap: No

Action:
Severity: Info.
SCH2049
SNMP trap: No
Cannot add existing attendant or delete non-existing attendant.

Action:
Severity: Info.
SCH2050
SNMP trap: No
Outing an existing DND group is not allowed unless the GND key is
deactivated on the attendant console.
Action:
Severity: Info.
SCH2051
SNMP trap: No
Unable to match input field with stored mnemonics for prompt CNVT.
Action:
Severity: Info.
SCH2052
SNMP trap: No
ESN digit manipulation index out-of-range (0-255).

Action:
Severity: Info.
SCH2053
SNMP trap: No
ESN digit manipulation table does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1658 of 2360

SCH2054

Action:
Severity: Info.
SCH2055
SNMP trap: No
Wrong number of input fields for prompt ATDN.

Action:
Severity: Info.
SCH2056
SNMP trap: No
Only FDN is allowed for 500 telephone.

Action:
Severity: Info.
SCH2057
SNMP trap: No
WTA not allowed for CLS DTA.

Action:
Severity: Info.
SCH2058
SNMP trap: No
Null input not allowed for prompt NEW.

Action:
Severity: Info.
SCH2059
SNMP trap: No
Wrong number of input fields for prompt MTN.

Action:
Severity: Info.
SCH2060
SNMP trap: No
Release 8 L MSI configured in SCC FN. Prompt incoming default not allowed.
Action:
Severity: Info.
SCH2061
SNMP trap: No
Too many ranges defined for this location code (20 ranges maximum).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1659 of 2360

SCH2062
Overlapping or duplication of ranges.

Action:
Severity: Info.
SCH2063
SNMP trap: No
XRA or XFA not allowed when CLS = MNL.

Action:
Severity: Info.
SCH2064
SNMP trap: No
The desired key is already defined.

Action: Only one CSD key is allowed for each set.
Severity: Info.
SCH2065
SNMP trap: No
PBX ring option conflicts with group option.

Action:
Severity:
SCH2066
SNMP trap: No
Wrong key number to TAD.

Action:
Severity:
SCH2067
SNMP trap: No
The Call Park option must be allowed (CPA) in CDB.

Action:
Severity:
SCH2070
SNMP trap: No
Cannot OUT customer when ESN, NCTL or AUTH blocks still exist.
Action:
Severity: Info.
SCH2071
SNMP trap: No
Cannot OUT customer when ACD still exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1660 of 2360

SCH2072
Cannot OUT customer when DISA blocks still exist.

Action:
Severity: Info.
SCH2073
SNMP trap: No
Cannot OUT customer when Call Park blocks still exist.

Action:
Severity: Info.
SCH2074
SNMP trap: No
Input AOS for CLS = ignored when command is NEW.

Action:
Severity: Info.
SCH2075
SNMP trap: No
EFD allowed only with CFTA COS.

Action:
Severity: Info.
SCH2076
SNMP trap: No
EHT allowed only with CFTA COS.

Action:
Severity: Info.
SCH2077
SNMP trap: No
Unable to match input with mnemonics.

Action:
Severity: Info.
SCH2078
SNMP trap: No
SNMP trap: No
CFCT not allowed.

Action:
Severity: Info.
SCH2079
BGD user type cannot coexist with ACD, APL, CDL, CMC, CMS, HSL, LSL.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1661 of 2360

SCH2080
BGD customer number must be specified for BGD or PMS Link device.
Action:
Severity: Info.
SCH2081
SNMP trap: No
BGD/PMSI package not equipped.

Action:
Severity: Info.
SCH2084
SNMP trap: No
SNMP trap: No
SFA not defined.

Action:
Severity: Info.
SCH2085
CPND cannot exist with DTA on.

Action:
Severity: Info.
SCH2086
SNMP trap: No
SNMP trap: No
SNMP trap: No
SFA not defined.

Action:
Severity: Info.
SCH2087
SFA not allowed.

Action:
Severity: Info.
SCH2088
ACD-DNIS package is restricted.

Action:
Severity: Info.
SCH2089
SNMP trap: No
APL number expected when LINK = YES.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1662 of 2360

SCH2090
Customer option cannot be changed to DNX with DNIS routes defined.

Action:
Severity: Info.
SCH2092
SNMP trap: No
DNIS routes cannot be configured with CHG request.

Action:
Severity: Info.
SCH2093
SNMP trap: No
Not a valid APL. Define in the Configuration Record.

Action:
Severity: Info.
SCH2094
SNMP trap: No
APL package not equipped.

Action:
Severity: Info.
SCH2097
SNMP trap: No
DN must be ACD DN when trunk is a DNIS route.

Action:
Severity: Info.
SCH2098
SNMP trap: No
TDET package is restricted.

Action:
Severity: Info.
SCH2099
SNMP trap: No
Class Transfer Allowed (XFA) or 3-Party Service Allowed (TSO) Class of

Service is required for C6A and MBXA. XFA is also required when feature
(FTR) = Permanent Hold (PHD).
Action:
Severity: Info.
SCH2101
SNMP trap: No
MXLN cannot be reduced once defined.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1663 of 2360

SCH2102
CPND data block does not exist.

Action:
Severity: Info.
SCH2103
SNMP trap: No
Invalid command for stand alone CPND.

Action:
Severity: Info.
SCH2104
SNMP trap: No
Response to TYPE must be NAME.

Action:
Severity: Info.
SCH2105
SNMP trap: No
CPND data block already exists.

Action:
Severity: Info.
SCH2106
SNMP trap: No
Invalid CPND configuration.

Action:
Severity: Info.
SCH2107
SNMP trap: No
Cannot change CPND configuration.

Action:
Severity: Info.
SCH2108
SNMP trap: No
MXLN out-of-range (5-27).

Action:
Severity: Info.
SCH2109
SNMP trap: No
Only YES or NO allowed.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1664 of 2360

SCH2110
Response to STAL must be YES with BGD package.

Action:
Severity: Info.
SCH2111
SNMP trap: No
SNMP trap: No
DFLN out-of-range.
Action:
Severity: Info.
SCH2112
Cannot remove CPND data block while names exist for DN.
Action:
Severity: Info.
SCH2113
SNMP trap: No
Cannot remove CPND data base while names exist.

Action:
Severity: Info.
SCH2114
SNMP trap: No
Invalid response to DIG.

Action:
Severity: Info.
SCH2115
SNMP trap: No
CPND name does not exist.

Action:
Severity: Info.
SCH2116
SNMP trap: No
CPND name already exists.

Action:
Severity: Info.
SCH2117
SNMP trap: No
Invalid character for Name. If the NAME prompt will not accept any characters
and PKG 211 is configured, verify that the input terminal is configured to send
8 bit characters.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1665 of 2360

SCH2118
Too many input characters.

Action:
Severity: Info.
SCH2119
SNMP trap: No
SNMP trap: No
Invalid response to DN.

Action:
Severity: Info.
SCH2120
Digit display cannot be removed because RMK/MRK key configured.

Action:
Severity: Info.
SCH2121
SNMP trap: No
Invalid input to MR prompt.

Action:
Severity: Info.
SCH2122
SNMP trap: No
PSP/PIP CLS only allowed for loop start trunks with disconnect super.
Action:
Severity: Info.
SCH2123
SNMP trap: No
MRA/MRD not allowed unless Message Registration (MR) package is

enabled. PSP is mutually exclusive with JCO/LST.
Action:
Severity: Info.
SCH2125
SNMP trap: No
MRK key set must have digit display assigned.

Action:
Severity: Info.
SCH2126
SNMP trap: No
Manual and Hot Line telephones can have LLCN COS only.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1666 of 2360

SCH2127
XPLN out-of-range; from entered Name's length to MXLN.

Action:
Severity: Info.
SCH2128
SNMP trap: No
TOFT value must be from 2 to 1800 at OVDN prompt.

Action:
Severity: Info.
SCH2129
SNMP trap: No
All ACD DNs specified for OVDN must be unique.

Action:
Severity: Info.
SCH2130 dn
SNMP trap: No
ACD DN cannot answer TOF calls for this source ACD DN because it already
services 6 source ACD DNs. dn = target ACD DN.
Action:
Severity: Info.
SCH2131 dn
SNMP trap: No
When deleting the Target ACD DN (dn) from a source with TOFT defined,
could not find the source TOF queue address within the target's unprotected
block. Possible data corruption which may result in BUG688 and source TOF
calls not terminating to target agents.
Action: Manual INIT. or run Audit recommended. If this persists, inform
operating company.
Severity: Info.
SCH2132
SNMP trap: No
Prior to Release 16, PSP CLS is mutually exclusive with LST and JCO CLS.
For Release 16 and later, PSP CLS is mutually exclusive with JDID and JCO
CLS.
Action:
Severity: Info.
SCH2133
SNMP trap: No
Cannot use X to delete EFD/EHT. Consult your user manual.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1667 of 2360

SCH2134
SFA requires FNA and MWD COS.

Action:
Severity: Info.
SCH2135
SNMP trap: No
Power down and power up, or enable, or service change the M2317 telephone
that is using this speed/system call list after this Speed Call List is changed.
Action:
Severity: Info.
SCH2137
SNMP trap: No
Wrong set type, cannot assign maintenance set class.

Action:
Severity: Info.
SCH2138
SNMP trap: No
This is a data set TN. It cannot have MTC class.

Action:
Severity: Info.
SCH2139
SNMP trap: No
DN assignment not allowed on this key.

Action:
Severity: Info.
SCH2140
SNMP trap: No
Must set or change the SID value when the IFC or NSF of the route is
changed.
Action:
Severity: Info.
SCH2141
SNMP trap: No
Max value must be specified when the NSF or IFC or the route is changed.
Action:
Severity: Info.
SCH2142
SNMP trap: No
Priority is out-of-range. The Range is from 1 to the Maximum Priority for the
ACD-DN of the defined agent.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1668 of 2360

SCH2143
DNIS route must either auto-terminate or IDC.

Action:
Severity: Info.
SCH2144
SNMP trap: No
Cannot move an IPMG loop to a non-IPMG loop or Cannot move a non-IPMG

loop to an IPMG loop.
Action: Use the appropriate loop type.
Severity: Info.
SCH2145
SNMP trap: No
Cannot remove CDB while Scheduled Access Restriction data block exists.
Action: Remove the SAR data block for this customer in LD88.
Severity: Minor.
SCH2146
SNMP trap: No
RLTI is only applicable for CTYP = DCIP and IFC = SL1.

Action: Change CTYP to DCIP and/or IFC to SL1.
Severity: Info.
SCH2501
SNMP trap: No
An attempt was made to change a telephone that is in the process of

relocating.
Action:
Severity: Info.
SCH2502
SNMP trap: No
A request other than NEW or OUT was used in conjunction with type CARD.
Action:
Severity: Info.
SCH2503
SNMP trap: No
An attempt was made to service change a telephone that SET-RELOCATE

was working on.
Action:
Severity: Info.
SCH2506
SNMP trap: No
An attempt was made to change a set that belongs to a different customer.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1669 of 2360

SCH2507
An attempt was made to change a set that is busy.

Action:
Severity: Info.
SCH2508
SNMP trap: No
ALOW or DENY was expected as an input but was not received.

Action:
Severity: Info.
SCH2509
SNMP trap: No
An invalid Prime DN has been entered. It is not unique or is not a Prime DN.
Action:
Severity: Info.
SCH2510
SNMP trap: No
Attendant Administration Package is not equipped.

Action:
Severity: Info.
SCH2511
SNMP trap: No
History File feature package restricted.

Action:
Severity: Info.
SCH2512
SNMP trap: No
Not enough PDS to allocate History File of requested size. Followed by

(allocated size) and (requested size).
Action:
Severity: Info.
SCH2513
SNMP trap: No
Invalid user for History File.

Action:
Severity: Info.
SCH2514
SNMP trap: No
History, traffic or TTY file is empty.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1670 of 2360

SCH2515
No new messages added to History File since last printout.

Action:
Severity: Info.
SCH2517
SNMP trap: No
Attendant Overflow Position package restricted.

Action:
Severity: Info.
SCH2521
SNMP trap: No
Not enough digits entered.

Action:
Severity: Info.
SCH2522
SNMP trap: No
Invalid entry for prompt CFW (not DENY or CFW).

Action:
Severity: Info.
SCH2523
SNMP trap: No
Invalid entry for prompt SPC (not DENY, SCC, or SCU).

Action:
Severity: Info.
SCH2524
SNMP trap: No
An attempt was made to assign an ACD or MC key to an SL-1 set.

Action:
Severity: Info.
SCH2525
SNMP trap: No
Mini-CDR package is not equipped.

Action:
Severity: Info.
SCH3000
SNMP trap: No
IMS package not equipped.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1671 of 2360

SCH3001
LTN table pointer not defined. Data corrupted.

Action:
Severity: Info.
SCH3002
SNMP trap: No
APL user cannot share TTY. APL user already defined.

Action:
Severity: Info.
SCH3003
SNMP trap: No
APL user cannot share TTY. Other user already defined.

Action:
Severity: Info.
SCH3004
SNMP trap: No
Cannot remove APL TTY without first removing all users using this TTY.
Action:
Severity: Info.
SCH3006
SNMP trap: No
The APL TTY is not defined in Configuration Record

Action:
Severity: Info.
SCH3007
SNMP trap: No
The APL TTY is already defined.

Action:
Severity: Info.
SCH3008
SNMP trap: No
The APL TTY is out-of-range (0-15).

Action:
Severity: Info.
SCH3009
SNMP trap: No
The APL TTY is previously removed.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1672 of 2360

SCH3010
Invalid APL link.

Action:
Severity: Info.
SCH3011
SNMP trap: No
Response of NO not allowed. IMA, UST, or UMG is active.

Action:
Severity: Info.
SCH3012
SNMP trap: No
The APL TTY is out-of-range (0-15).

Action:
Severity: Info.
SCH3013
SNMP trap: No
The APL link is shared by other user.

Action:
Severity: Info.
SCH3014
SNMP trap: No
The specified APL is not defined in customer data block.

Action:
Severity: Info.
SCH3015
SNMP trap: No
Caution: This command will remove all UST key users using this ACD (use
ODAS to print all UST key users). If no UST key users, ignore the error
message.
Action:
Severity: Info.
SCH3016
SNMP trap: No
Telephone message timer (UMT) is out-of-range (2-15).

Action:
Severity: Info.
SCH3017
SNMP trap: No
Response NO not allowed. IMS option is defined.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1673 of 2360

SCH3018
If any of the IMA, UST or UMG features are ON, then the CSL option (CMS)
may not be changed.
Action:
Severity: Info.
SCH3019
SNMP trap: No
Trunk CLS must be MFR if the trunk is a member of the CAMA route using Bell
M2B signaling.
Action:
Severity: Info.
SCH3020
SNMP trap: No
IMA Class of Service is not allowed for this customer.

Action:
Severity: Info.
SCH3021
SNMP trap: No
Carriage return in LTN field with APL link undefined.

Action:
Severity: Info.
SCH3022
SNMP trap: No
TN number is already defined.

Action:
Severity: Info.
SCH3023
SNMP trap: No
LTN number is out-of-range (1-253).

Action:
Severity: Info.
SCH3024
SNMP trap: No
LTN link number is not defined in customer data block.

Action:
Severity: Info.
SCH3025
SNMP trap: No
IMA Class of Service requires key 0 to be an ACD key.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1674 of 2360

SCH3026
UST key desired, but UST is restricted.

Action:
Severity: Info.
SCH3027
SNMP trap: No
UST key desired, but UST ALLOWED bit not set in CDB.
Action:
Severity: Info.
SCH3028
SNMP trap: No
All members of the CAMA Route using Bell Signaling M2B need to have MFR
Class of Service.
Action:
Severity: Info.
SCH3030
SNMP trap: No
Only Digitone sending/receiving allowed with ESN signaling arrangement.

Action:
Severity: Info.
SCH3031
SNMP trap: No
Trunk members must have Digitone sending/receiving.

Action:
Severity: Info.
SCH3032
SNMP trap: No
Invalid TN in trunk route trunk list.

Action:
Severity: Info.
SCH3033
SNMP trap: No
Wrong number of input fields for prompt FDN.

Action:
Severity: Info.
SCH3034
SNMP trap: No
Flexible DN conflicts with existing DN.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1675 of 2360

SCH3035
Invalid DN type for CFNA DN.

Action:
Severity: Info.
SCH3036
SNMP trap: No
Cannot remove IMS with IMA UST or UMG allowed.

Action:
Severity: Info.
SCH3037
SNMP trap: No
Cannot remove IMA with APL defined.

Action:
Severity: Info.
SCH3038
SNMP trap: No
Cannot remove UST with APL defined.

Action:
Severity: Info.
SCH3039
SNMP trap: No
Cannot remove UMG with APL defined.

Action:
Severity: Info.
SCH3040
SNMP trap: No
Cannot remove APL with user defined in ACD block.

Action:
Severity: Info.
SCH3041
SNMP trap: No
Cannot remove MCX with IMA, UST, or UMG allowed.

Action:
Severity: Info.
SCH3042
SNMP trap: No
SNMP trap: No
MCI option not enabled.

Action:
Severity: Info.
System Messages
Page 1676 of 2360

SCH3044
CLS IMA defined requires that the IMA option in ACD block be defined.
Action:
Severity: Info.
SCH3045
SNMP trap: No
LTN link is not the same as APL defined in this ACD block.
Action:
Severity: Info.
SCH3046
SNMP trap: No
UST key desired, but FDN, or HUNT is not an ACD DN.

Action:
Severity: Info.
SCH3047
SNMP trap: No
UST key desired, but UST not allowed in ACD block.

Action:
Severity: Info.
SCH3048
SNMP trap: No
UST key desired, but APL link not defined in ACD block.
Action:
Severity: Info.
SCH3049
SNMP trap: No
Key type already defined on this telephone. More than one key of this type per
telephone not permitted.
Action:
Severity: Info.
SCH3050
SNMP trap: No
MWD is invalid when telephone has MWK/XMWK/RMWK assigned.

Action: Delete MWK/XMWK/RMWK keys before changing the CLS option to
MWD.
Severity: Info.
SCH3051
SNMP trap: No
Repeat command not allowed for music trunks.

Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1677 of 2360

SCH3052
Existing card type conflicts with this overlay program.

Action:
Severity: Info.
SCH3053
SNMP trap: No
Wrong set type to assign this Class of Service.

Action:
Severity: Info.
SCH3054
SNMP trap: No
Wrong set type to assign this key mnemonic.

Action: The CSD key is only applicable to Aries set
Severity: Info.
SCH3055
SNMP trap: No
The Digital telephone package is not equipped.

Action:
Severity: Info.
SCH3056
SNMP trap: No
Hot line package not equipped.

Action:
Severity: Info.
SCH3058
SNMP trap: No

Action:
Severity: Info.
SCH3059
SNMP trap: No
DN length out-of-range (1-31).

Action: Enter DN length of 1 -31 digits.
Severity: Info.
SCH3060
SNMP trap: No
Class of Service must be MNL.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1678 of 2360

SCH3061
This feature not allowed for Hot Lines.

Action:
Severity: Info.
SCH3062
SNMP trap: No
SNMP trap: No
Invalid Hot Line DN.

Action:
Severity: Info.
SCH3063
AUTOVON preemptable trunk route must be DTMF.

Action:
Severity: Info.
SCH3064
SNMP trap: No
ICF or OGF timer for AUTOVON route out of range.

Action:
Severity: Info.
SCH3065
SNMP trap: No
Start arrangement for AUTOVON trunks must be WNK.

Action:
Severity: Info.
SCH3066
SNMP trap: No
AUTIOVON package is not equipped.

Action:
Severity: Info.
SCH3067
SNMP trap: No
Signal destination timer is out-of-range (384-2048).

Action:
Severity: Info.
SCH3069
SNMP trap: No
Last preference key number is out-of-range.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1679 of 2360

SCH3070
Line selection package is not equipped.

Action:
Severity: Info.
SCH3071
SNMP trap: No
A restart is caused if anything other than YES or {CR} is entered.

Action:
Severity: Info.
SCH3072
SNMP trap: No
Deluxe Hold package is not equipped.

Action:
Severity: Info.
SCH3073
SNMP trap: No
LFTN/TN customer conflicts with customer to be changed.

Action:
Severity: Info.
SCH3075
SNMP trap: No
A list number of this type does not exist.

Action:
Severity: Info.
SCH3080
SNMP trap: No
Hot Line lists need to be defined in LD 18.

Action:
Severity: Info.
SCH3081
SNMP trap: No
Hot Line list length out-of-range.

Action:
Severity: Info.
SCH3082
SNMP trap: No
Flexible Hot Line not allowed by list entry method.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1680 of 2360

SCH3083
Invalid DN; already assigned to non-enhanced Hot Line set.

Action:
Severity: Info.
SCH3085
SNMP trap: No
Hot Line list number mismatch.

Action:
Severity: Info.
SCH3086
SNMP trap: No
List already defined as Hot Line list.

Action:
Severity: Info.
SCH3087
SNMP trap: No
Set has EHTA COS; need to define Hot Line at FTR.

Action:
Severity: Info.
SCH3088
SNMP trap: No
Conflict with EHTA COS; telephone has either LNA, LLC1, LLC2, LLC3, MNL,
or Permanent Hold features enabled.
Action:
Severity: Info.
SCH3089
SNMP trap: No
EHTD not allowed. DN is shared with another defined Hot Line set.
Action: User must OUT and re-create the telephone.
Severity: Info.
SCH3090
SNMP trap: No
DN already defined as Enhanced Hot Line or two-way Hot Line key.

Action:
Severity: Info.
SCH3091
SNMP trap: No
SNMP trap: No
Illegal digit for list entry.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1681 of 2360

SCH3106
Unable to match input with stored mnemonics (trunk group option ESN.
Action:
Severity: Info.
SCH3107
SNMP trap: No
Only WNK start allowed with ESN signaling arrangement.

Action:
Severity: Info.
SCH3108
SNMP trap: No
Trunk group has non-wink-start members. Trunk arrangement must be wink

start for ESN.
Action:
Severity: Info.
SCH3109
SNMP trap: No
Duplicate Routing Controls key assigned to attendant console.

Action:
Severity: Info.
SCH3110
SNMP trap: No
Speed Call List does not exist.

Action:
Severity: Info.
SCH3111
SNMP trap: No
Wrong number of input fields for RNGE.

Action:
Severity: Info.
SCH3112
SNMP trap: No
Attempted to assign a System Speed Call List number to a Speed Call List key
or attempted to assign a Speed Call List number to a System Speed Call key.
Action:
Severity: Info.
SCH3113
SNMP trap: No
Low or high range must not exceed number of valid entries.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1682 of 2360

SCH3114
Answer and disconnect supervision required for ESN proprietary signaling.

Action:
Severity: Info.
SCH3115
SNMP trap: No
Trunk does not have answer and disconnect supervision.

Action:
Severity: Info.
SCH3116
SNMP trap: No
Expensive route cannot be assigned to an ESN trunk group.

Action:
Severity: Info.
SCH3117
SNMP trap: No
Cannot configure any odd loop adjacent to an even service loop in the same
card slot.
Action:
Severity: Info.
SCH3118
SNMP trap: No
Service loops must be even numbered loops.

Action:
Severity: Info.
SCH3119
SNMP trap: No
Cannot configure even service loops adjacent to another odd loop in the same
card slot.
Action:
Severity: Info.
SCH3120
SNMP trap: No
Extender group number not in range 0-4.

Action:
Severity: Info.
SCH3121
SNMP trap: No
No logical TN (LTN) can be found.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1683 of 2360

SCH3122
The number of ACD Agents requested exceeds the number of positions left for
this group.
Action:
Severity: Info.
SCH3123
SNMP trap: No
The Source TN cannot be a Dial Intercom set.

Action:
Severity: Info.
SCH3124
SNMP trap: No
The Source TNs Data DN key is not copied.

Action:
Severity: Info.
SCH3125
SNMP trap: No
CLS = MWD is not valid when the set has UST assigned.
Action:
Severity: Info.
SCH3126
SNMP trap: No
You cannot assign more than two (2) AST keys on a single SL-1 set.
Action:
Severity: Info.
SCH3127
SNMP trap: No
Invalid AST key type. Only ACD, MCR, MCN, SCR and SCN key are
supported.
Action:
Severity: Info.
SCH3128
SNMP trap: No
Two (2) AST key are defined for the same DN on this SL-set with ICRD CLS.
Action:
Severity: Info.
SCH3129
SNMP trap: No
This DN already has AST assigned and this TN is configured with CLS ICRD.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1684 of 2360

SCH3135
The ACD NSVC key already exists for this ACD-DN.

Action:
Severity: Info.
SCH3136
SNMP trap: No
NIGHT DN: define the associated minute with the hour defined.
Action:
Severity: Info.
SCH3137
SNMP trap: No
NIGHT DN: define the associated hour with the Night DN defined.
Action:
Severity: Info.
SCH3138
SNMP trap: No
Night service times are not in ascending order.

Action:
Severity: Info.
SCH3139
SNMP trap: No
Cannot copy a digital voice TN to a digital data TN. Also, you cannot copy a
digital data TN to a digital voice TN.
Action:
Severity: Info.
SCH3140
SNMP trap: No
Set-type of the new TN does not match with the set-type of the corresponding
voice/data TN.
Action:
Severity: Info.
SCH3141
SNMP trap: No
Customer number of the new TN does not match the customer number for the
corresponding voice/data TN.
Action:
Severity: Info.
SCH3142
SNMP trap: No
Tree digits input are invalid.

Action: Re-input the proper and valid tree digits.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1685 of 2360

SCH3146
Trunk type of a route cannot be changed.

Action:
Severity: Info.
SCH3147
SNMP trap: No
Primary Rate Access (PRA) package not equipped.

Action:
Severity: Info.
SCH3148
SNMP trap: No
ISDN Signaling Link (ISL) package not equipped.

Action:
Severity: Info.
SCH3149
SNMP trap: No
Neither ESL, PRA nor PRA2 package not equipped.

Action:
Severity: Info.
SCH3150
SNMP trap: No
A value between 1-382 must be entered for all shared and ESL D-channels.
{CR} not allowed for new ESL.
Action:
Severity: Info.
SCH3151
SNMP trap: No
The ISL trunk still exists. Changing mode; decreasing the ISLM below the
existing CHIDs or removing DCHI is not allowed.
Action:
Severity: Info.
SCH3152
SNMP trap: No
Mode or DCHI change is only allowed if trunks have been removed.

Action:
Severity: Info.
SCH3153
SNMP trap: No
SNMP trap: No
No default allowed.
Action:
Severity: Info.
System Messages
Page 1686 of 2360

SCH3154
Route mode does not match DCHI user in the Configuration Editor.
Action:
Severity: Info.
SCH3155
SNMP trap: No
Maximum number of PNI are already assigned.

Action:
Severity: Info.
SCH3156
SNMP trap: No
PNI is assigned to a different customer.

Action:
Severity: Info.
SCH3157
SNMP trap: No
Primary Rate Interface (PRI) hardware is required.

Action:
Severity: Info.
SCH3158
SNMP trap: No
ISDN B-channel trunk parameters cannot be changed when the trunk is busy.
Action:
Severity: Info.
SCH3159
SNMP trap: No
Wrong number of input fields for CHID.

Action:
Severity: Info.
SCH3160
SNMP trap: No
CHID is out-of-range.
Action: Check ISL MAX in the Configuration Record
Severity: Info.
SCH3161
SNMP trap: No
IFC type of D250 or ESS4 requires IEC package.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1687 of 2360

SCH3162
In LD 14 a duplicate CHID has been entered. This CHID already exists.

Action:
Severity: Info.
SCH3171
SNMP trap: No
IFC for ISA route must be changed to ESS4 first and then the IFC for the
service route can be changed to ESS4.
Action:
Severity: Info.
SCH3172
SNMP trap: No
D-CH block pointer is NIL.

Action:
Severity: Info.
SCH3173
SNMP trap: No
Must provide COT route number.

Action:
Severity: Info.
SCH3174
SNMP trap: No
ISA route can be deleted if ISDN service routes do not step to it.
Action:
Severity: Info.
SCH3175
SNMP trap: No
Warning: IFC for service route does not match IFC for route. Changing IFC
between ESS4/ESS5 and D100/D250/S100/SL1 is not allowed.
Action:
Severity: Info.
SCH3176
SNMP trap: No
Only one service route with a specific service type can be assigned to an ISA
route (IFC = ESS4).
Action:
Severity: Info.
SCH3177
SNMP trap: No
SID value must be unique.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1688 of 2360

SCH3178
If a CO route exists, enter route number for prompt COTR. If a WATS route
exists, enter route number for prompt WATR. If a TIE route exists, enter route
number for prompt TIER. Otherwise, the ISA route is inoperative and overflow
tone is given.
Action:
Severity: Info.
SCH3179
SNMP trap: No
Trunk(s) cannot be removed if the remaining number of trunks are less than
the sum of the minimum number of reserved trunks.
Action:
Severity: Info.
SCH3180
SNMP trap: No
The MAX value exceeds the number of trunks configured for the ISA route.
Action:
Severity: Info.
SCH3181
SNMP trap: No
Zero (0) is not allowed for IEC.

Action:
Severity: Info.
SCH3182
SNMP trap: No
B-channel(s) on a PRI loop must be moved to a PRI loop configured with a

D-channel.
Action:
Severity: Info.
SCH3183
SNMP trap: No
Incorrect number of digits entered.

Action:
Severity: Info.
SCH3184
SNMP trap: No
At least one route is using this block; FGNO of that route must be changed
before removing FGD block. A list of routes using this block is printed.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1689 of 2360

SCH3185
Too many Service Access Codes (maximum is 8).

Action:
Severity: Info.
SCH3186
SNMP trap: No
Information digit (II) numbers are not in ascending order.

Action:
Severity: Info.
SCH3187
SNMP trap: No
There are spaces in the Information digits (II) table.

Action:
Severity: Info.
SCH3188
SNMP trap: No
Up to 255 MFR units may be defined.

Action:
Severity: Info.
SCH3190
SNMP trap: No
FGD package is not equipped.

Action:
Severity: Info.
SCH3191
SNMP trap: No
Wrong input parameters.

Action:
Severity: Info.
SCH3192
SNMP trap: No
DN is assigned to another function.

Action:
Severity: Info.
SCH3193
SNMP trap: No
DN is assigned to a different test line.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1690 of 2360

SCH3194
The DN for the associated Loop Reference trunk is not assigned. Printed in
response to TST DN.
Action:
Severity: Info.
SCH3195
SNMP trap: No
Directory number conflict of input parameters.

Action:
Severity: Info.
SCH3196
SNMP trap: No
Not enough memory available.

Action:
Severity: Info.
SCH3197
SNMP trap: No
Mini-CDR tape + History File and number of TTYs is greater than 16.
Action:
Severity: Info.
SCH3198
SNMP trap: No
STRI and STRO must be WNK for FGDT trunks.

Action:
Severity: Info.
SCH3199
SNMP trap: No
FGDT and M911 trunks must have MFR COS.

Action:
Severity: Info.
SCH3200
SNMP trap: No
SNMP trap: No
FGNO out-of-range.
Action:
Severity: Info.
SCH3201
Specified FGD block has not been defined.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1691 of 2360

SCH3202
MOV is invalid for TYPE FGDB or ANI.

Action:
Severity: Info.
SCH3203
SNMP trap: No
PRT is invalid for TYPE CRB.

Action:
Severity: Info.
SCH3204
SNMP trap: No
Requested FGD block does not exist.

Action:
Severity: Info.
SCH3205
SNMP trap: No
Music trunk does not exist.

Action:
Severity: Info.
SCH3206
SNMP trap: No
Call Park package not equipped.

Action:
Severity: Info.
SCH3207
SNMP trap: No
Call Park not activated for the customer.

Action:
Severity: Info.
SCH3208
SNMP trap: No
Call Park data block already exists.

Action:
Severity: Info.
SCH3209
SNMP trap: No
Call Park data block does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1692 of 2360

SCH3210
System park DN input not allowed.

Action:
Severity: Info.
SCH3211
SNMP trap: No
FDN not allowed unless COS is FNA or MWA.

Action:
Severity: Info.
SCH3212
SNMP trap: No
Loop assignment exceeds system loop limit (Flexible Pricing).

Action:
Severity: Info.
SCH3213
SNMP trap: No
SNMP trap: No
Warning: STOR again.

Action:
Severity: Info.
SCH3214
IMM response forced for STAR if DN exist for ATDN or MNDN.

Action:
Severity: Info.
SCH3215
SNMP trap: No
If AUTO is set and TKTP is TIE, SIG cannot be ESN3.

Action:
Severity: Info.
SCH3218
SNMP trap: No
ISA package is restricted.

Action:
Severity: Info.
SCH3219
SNMP trap: No
PRI mode cannot be changed when associated with DCHI.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1693 of 2360

SCH3220
No toll digits are specified for outgoing toll calls.

Action:
Severity: Info.
SCH3221
SNMP trap: No
Unable to match input with mnemonic (for density).

Action:
Severity: Info.
SCH3222
SNMP trap: No
Card density greater than loop density.

Action:
Severity: Info.
SCH3223
SNMP trap: No
Card density too low for entered unit number.

Action:
Severity: Info.
SCH3224
SNMP trap: No
New card density too low for configured units.

Action:
Severity: Info.
SCH3225
SNMP trap: No
Entered density greater then MPED.

Action:
Severity: Info.
SCH3226
SNMP trap: No
New MPED value lower then configured loop density.

Action:
Severity: Info.
SCH3227
SNMP trap: No
R2/MFC signaling (MFC) required to have CNA Class of Service.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1694 of 2360

SCH3228
CNA or CND Class of Service allowed only for DID trunks.

Action:
Severity: Info.
SCH3229
SNMP trap: No
New MPED value lower than default card densities.

Action:
Severity: Info.
SCH3230
SNMP trap: No
Default card density greater than the loop density.

Action:
Severity: Info.
SCH3231
SNMP trap: No
Odd numbered DTR units not supported.

Action:
Severity: Info.
SCH3232
SNMP trap: No
Unit number in response to TOTN higher than card density.

Action:
Severity: Info.
SCH3233
SNMP trap: No
Card densities on source loop incompatible with destination loop.

Action:
Severity: Info.
SCH3234
SNMP trap: No
Equipped shelf numbers on source loop incompatible with destination loop.

Action:
Severity: Info.
SCH3235
SNMP trap: No
An attempt was made to increment the max tn(s).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1695 of 2360

SCH3236
FFC block already exists.

Action:
Severity: Info.
SCH3237
SNMP trap: No
FFC block does not exist.

Action:
Severity: Info.
SCH3238
SNMP trap: No
FFC package unequipped.

Action:
Severity: Info.
SCH3239
SNMP trap: No
SNMP trap: No
SNMP trap: No
Invalid password.
Action:
Severity: Info.
SCH3240
Entry out-of-range.
Action:
Severity: Info.
SCH3241
External source number out-of-range.

Action:
Severity: Info.
SCH3242
SNMP trap: No
SNMP trap: No
Invalid FFC mnemonic.

Action:
Severity: Info.
SCH3243
64K clear can be selected only when LCMT is B8S.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1696 of 2360

SCH3244
DTD package not equipped.

Action:
Severity: Info.
SCH3245
SNMP trap: No
Minimum DTD delay out-of-range.

Action:
Severity: Info.
SCH3246
SNMP trap: No
Parameter out-of-range (0-15).

Action:
Severity: Info.
SCH3247
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Null input not accepted.

Action:
Severity: Info.
SCH3248
Entry should be 0 or 1.
Action:
Severity: Info.
SCH3249
Dial tone not specified.

Action:
Severity: Info.
SCH3250
Input field is greater than 4.

Action:
Severity: Info.
SCH3251
SNMP trap: No
Announcement package not equipped.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1697 of 2360

SCH3252
Input out-of-range (0-15 for internal) (0-7 for external).

Action:
Severity: Info.
SCH3253
SNMP trap: No
Invalid tone or source number.

Action:
Severity: Info.
SCH3254
SNMP trap: No
Loop number not associated with DCHI number/BCHI number.

Action:
Severity: Info.
SCH3255
SNMP trap: No
Analog route cannot be PRA.

Action:
Severity: Info.
SCH3256
SNMP trap: No
Yellow alarm was changed to DG2 because the frame format was changed to
other than ESF.
Action:
Severity: Info.
SCH3257
SNMP trap: No
Cannot configure DCH when the other port on the card is not configured as
TTY
Action:
Severity: Info.
SCH3258
SNMP trap: No
Loop number must be given with the sequence number.

Action:
Severity: Info.
SCH3259
SNMP trap: No
Loop can be removed only when none of its channels are configured for
B-channel signaling.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1698 of 2360

SCH3260
The TTY Port must be configured ASYNC when the other port on the same
card is a DCHI or BCHI.
Action:
Severity: Info.
SCH3261
SNMP trap: No
BCHI must have different value from DCHI.

Action:
Severity: Info.
SCH3262
SNMP trap: No
There is at least one ISDN route. PRA = NO is not allowed.

Action:
Severity: Info.
SCH3263
SNMP trap: No
HNPA, HLOC, and HNXX must be given for new customer.

Action:
Severity: Info.
SCH3264
SNMP trap: No
Radio paging system does not exist.

Action:
Severity: Info.
SCH3265
SNMP trap: No
Radio paging block already exists.

Action:
Severity: Info.
SCH3266
SNMP trap: No
Not a Radio paging system route.

Action:
Severity: Info.
SCH3267
SNMP trap: No
STEP to ISA route is not allowed.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1699 of 2360

SCH3268
PSA length out-of-range, (1-4).

Action:
Severity: Info.
SCH3269
SNMP trap: No
Mode digit out-of-range, (0-9).

Action:
Severity: Info.
SCH3270
SNMP trap: No
Radio paging system number out-of-range (0-15).

Action:
Severity: Info.
SCH3271
SNMP trap: No
SNMP trap: No
SNMP trap: No
DN out-of-range.
Action:
Severity: Info.
SCH3272
PSA out-of-range.
Action:
Severity: Info.
SCH3273
Invalid system type for CO trunk.

Action:
Severity: Info.
SCH3274
SNMP trap: No
Radio Paging data must be removed before changing system type.

Action:
Severity: Info.
SCH3275
SNMP trap: No
Higher station group number exists.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1700 of 2360

SCH3276
SGRP out-of-range (1-127).

Action:
Severity: Info.
SCH3277
SNMP trap: No
Out-of-range (1 to MAXN).
Action:
Severity: Info.
SCH3278
SNMP trap: No
MAX cannot be reduced below existing PRXL/GRNO number.

Action:
Severity: Info.
SCH3279
SNMP trap: No
PRXL table/entry already exists.

Action:
Severity: Info.
SCH3280
SNMP trap: No
PRXL table does not exist.

Action:
Severity: Info.
SCH3281
SNMP trap: No
Pretranslation package restricted.

Action:
Severity: Info.
SCH3282
SNMP trap: No
Input number out-of-range (0-9).

Action:
Severity: Info.
SCH3283
SNMP trap: No
Input must be 0-9999, or ABS, OVF, X.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1701 of 2360

SCH3284
Pretranslation table size must be either 10 or 100.

Action:
Severity: Info.
SCH3285
SNMP trap: No
Pretranslation data of this customer does not exist.

Action:
Severity: Info.
SCH3286
SNMP trap: No
Indices x1-x9 of XLTI, x not allowed.

Action:
Severity: Info.
SCH3287
SNMP trap: No
Invalid command; must be one of NEW/CHG/OUT/END.

Action:
Severity: Info.
SCH3288
SNMP trap: No
Trunk TYPE = not allowed with PRI loop.

Action:
Severity: Info.
SCH3289
SNMP trap: No
PRI loop can be moved to PRI loop only.

Action:
Severity: Info.
SCH3290
SNMP trap: No
Invalid maximum PE density keyword.

Action:
Severity: Info.
SCH3291
SNMP trap: No
Attempted to configure PE as being SD while some DD terminals still exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1702 of 2360

SCH3292
Invalid card density keyword.

Action:
Severity: Info.
SCH3293
SNMP trap: No
Card density is higher than ICCP density.

Action:
Severity: Info.
SCH3294
SNMP trap: No
Entered card density is too low for the new unit.

Action:
Severity: Info.
SCH3295
SNMP trap: No
Attempted to lower card density while upper units were still equipped.
Action:
Severity: Info.
SCH3296
SNMP trap: No
Card is already equipped.

Action:
Severity: Info.
SCH3297
SNMP trap: No
SNMP trap: No
Card is not equipped.

Action:
Severity: Info.
SCH3298
Card density is higher than maximum PE density.

Action:
Severity: Info.
SCH3299
SNMP trap: No
Change is not allowed for single density loop at card level.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1703 of 2360

SCH3300
The DN or Position ID is invalid, it must be unique.

Action:
Severity: Info.
SCH3301
SNMP trap: No
The conditions for entering this item have not been met.
Action:
Severity: Info.
SCH3302
SNMP trap: No
Copy count is out-of-range.

Action:
Severity: Info.
SCH3303
SNMP trap: No
Cannot copy the TN to a DLI loop.

Action:
Severity: Info.
SCH3304
SNMP trap: No
Last Hunt key number is out-of-range.

Action:
Severity: Info.
SCH3305
SNMP trap: No
The Source TN cannot be a Virtual Agent.

Action:
Severity: Info.
SCH3306
SNMP trap: No
The Source TN cannot be an ACD Supervisor.

Action:
Severity: Info.
SCH3307
SNMP trap: No
CLS = IMA, but there is no LTN or APL defined.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1704 of 2360

SCH3308
Cannot copy to a relocating set TN.

Action:
Severity: Info.
SCH3309
SNMP trap: No
CLS = TENA, but there is no tenant number defined.

Action:
Severity: Info.
SCH3310
SNMP trap: No
Must have MWA for UST key operation.

Action:
Severity: Info.
SCH3400
SNMP trap: No
Digital loop mode may not be defaulted when configuring a new loop.
Action:
Severity: Info.
SCH3401
SNMP trap: No
Data calls and frame format fields ignored for DLI loops (digital loops in the link
mode).
Action:
Severity: Info.
SCH3402
SNMP trap: No
The DLI loop may not be removed if still defined for a VAS (PTE).
Action:
Severity: Info.
SCH3403
SNMP trap: No
There is no protected DLI loop block for DLI loop N.

Action:
Severity: Info.
SCH3404
SNMP trap: No
There are no defined VAS servers (PTE).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1705 of 2360

SCH3405
VAS server (PTE) already defined.

Action:
Severity: Info.
SCH3406
SNMP trap: No
VAS server (PTE) is not defined.

Action:
Severity: Info.
SCH3407
SNMP trap: No
The VAS server (PTE) may not be removed when CSL links are still defined
for that VAS (PTE).
Action: To remove a CSL link, enter: X before the CSL link number, to the CMS
sub-prompt of the VAS (PTE) prompt.
Severity: Info.
SCH3408
SNMP trap: No
Loop type must be DLI (digital loop in the link mode).

Action:
Severity: Info.
SCH3409
SNMP trap: No
DLI loop must be disabled when adding to VAS server (PTE).

Action:
Severity: Info.
SCH3410
SNMP trap: No
Maximum CSL links that may be defined for a VAS (PTE) has already been
reached.
Action:
Severity: Info.
SCH3411
SNMP trap: No
CSL link exists and belongs to a different VAS server (PTE).

Action:
Severity: Info.
SCH3412
SNMP trap: No
DLI loop is assigned to a different VAS server (PTE).

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1706 of 2360

SCH3413
All DLI loops assigned to a VAS server (PTE) must be disabled before the VAS
server (PTE) can be removed.
Action:
Severity: Info.
SCH3414
SNMP trap: No
Port number must correspond to a synchronous ESDI port, defined as ESDI

YES and SYNC YES under the ADAN TTY prompt.
Action:
Severity: Info.
SCH3415
SNMP trap: No
CSL link must be disabled before modifications can be made.

Action:
Severity: Info.
SCH3416
SNMP trap: No
Both the CSL Basic and DTI packages must be equipped for the CMSA Class
of Service.
Action:
Severity: Info.
SCH3417
SNMP trap: No
Class of Service of CMSA is not accepted if class is not also DTA.

Action:
Severity: Info.
SCH3418
SNMP trap: No
Station category number out of acceptable range (0-7).

Action:
Severity: Info.
SCH3419
SNMP trap: No
CSL is not defined for this VAS server (PTE).

Action:
Severity: Info.
SCH3420
SNMP trap: No
CSL configuration type may not be defaulted when adding a new CSL link.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1707 of 2360

SCH3423
CSL Basic package is not equipped.

Action:
Severity: Info.
SCH3429
SNMP trap: No
LINK mode is accepted only if both the DTI and the CSL Basic packages are
equipped.
Action:
Severity: Info.
SCH3431
SNMP trap: No
SNMP trap: No
The loop does not exist.

Action:
Severity: Info.
SCH3434
Invalid TN (DLI channel TN or maintenance TN x 0 9 0).

Action:
Severity: Info.
SCH3445
SNMP trap: No
Cannot remove an SADM/Data Line Card TN while it is still defined for an

indirect CSL link.
Action:
Severity: Info.
SCH3446
SNMP trap: No
Default SADM/data line card or DLI loop is not allowed for new indirect CSL.
Action:
Severity: Info.
SCH3447
SNMP trap: No
SADM/data line card entered is not in SL-1 data base.

Action:
Severity: Info.
SCH3448
SNMP trap: No
SADM/data line card is already assigned to a different indirect CSL.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1708 of 2360

SCH3449
TN does not have CMSA Class of Service.

Action:
Severity: Info.
SCH3452
SNMP trap: No
Cannot remove DLI loop when defined for an indirect CSL.

Action:
Severity: Info.
SCH3453
SNMP trap: No
DLI loop entered is already assigned to a different indirect CSL.

Action:
Severity: Info.
SCH3455
SNMP trap: No
VAS ID out-of-range (0-15).

Action:
Severity: Info.
SCH3456
SNMP trap: No
VAS ID may not be defaulted for new data service access code.
Action:
Severity: Info.
SCH3457
SNMP trap: No
Overflow DN for data service access code must be data service access code.
Action:
Severity: Info.
SCH3458
SNMP trap: No
Cannot remove IS/data services option before data service DNs and their
access codes are removed.
Action:
Severity: Info.
SCH3459
SNMP trap: No
Cannot remove data service access option if agents are still defined for this
ACD DN.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1709 of 2360

SCH3460
Ring Again for internal calls must be YES for data service access code.
Action:
Severity: Info.
SCH3461
SNMP trap: No
Call forcing option must be NO for data service access code.

Action:
Severity: Info.
SCH3462
SNMP trap: No
Data services customer option is not set (OPT DSI in LD 15).

Action:
Severity: Info.
SCH3463
SNMP trap: No
If class is DSI, class must also be DTA.

Action:
Severity: Info.
SCH3464
SNMP trap: No
SNMP trap: No
TYPE must be SL1

Action:
Severity: Info.
SCH3465
Cannot remove customer block before IS/data service DNs are removed.
Action:
Severity: Info.
SCH3466
SNMP trap: No
Data service access code may not be a message center.

Action:
Severity: Info.
SCH3467
SNMP trap: No
If class is DSI, then key 0 must be an in-calls key for an ACD DN of a Data
service access group (DSAC YES in LD 23).
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1710 of 2360

SCH3468
If key 0 is an in-calls key for an ACD DN of a data service access group, then
class must be DSI.
Action:
Severity: Info.
SCH3469
SNMP trap: No
Data services customer option is not turned on (OPT DSI in LD 15).

Action:
Severity: Info.
SCH3470
SNMP trap: No
The DLI loop must be assigned to a VAS Server (PTE) (in LD 17, DLOP under
VAS prompt).
Action:
Severity: Info.
SCH3475
SNMP trap: No
Not enough Call Registers to send the CSL DATA message to the server
(PTE). This means that the server (PTE) was not notified of the data base
change or validation request.
Action: To ensure compatibility of the shared data bases (when the CSL link is
up), try either:
1. Removing the TN (if in LD 11), or DN (if in Ld 23) (OUT) and adding it back in
(NEW), or 2. Running Audit.
Severity: Info.
SCH3476
SNMP trap: No
No active CSL link was found for the VAS Server (PTE) to which the M4020
terminal access TN or access code is assigned. If an M4020 terminal is being
service changed, then this is the VAS server (PTE) to which the DLI loop of
the M4020 terminal voice TN is assigned (DLOP under VAS prompt in LD 17).
If an access code or TN is being service changed, then this is the VAS server
(PTE) to which the access code is assigned (VSID in LD 23).
This means that the server (PTE) was not notified of the data base change or
validation request.
Action: To ensure compatibility of the shared data (when the CSL lins is up), try
either:
1. Removing the TN (if in LD 11) or DN (if in LD 23) (OUT) and adding it vack in
(NEW), or 2. Running audit.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1711 of 2360

SCH3477
The CSL DATA message could not be sent to the VAS Server (PTE) for
unspecified reasons.
Action: Try removing the data and adding it back in, or running Audit LD 44.
Severity: Info.
SCH3483
SNMP trap: No
TNs on a DLI loop must be one of a data service access TN (TYPE of SL-1
and CLS of DSI) or a VMS access TN (TYPE of SL-1 and CLS of VMA).
Action:
Severity: Info.
SCH3484
SNMP trap: No
No response was received from the VAS Server (PTE) for the CSL DATA
message sent. This could mean that the server (PTE) was not notified of the
data base change or validation request.
up), try either:
1. RemAction: removing the TN (if in Ld 11) or DN (if in LD 23) (OUT) and adding
it back in (NEW), or 2. Running Audit.
Severity: Info.
SCH3485
SNMP trap: No
Class of Service of DTA is not allowed for the M4020 voice TN. These Classes
of Service belong to the M4020 terminal voice TN.
Action:
Severity: Info.
SCH3486
SNMP trap: No
If Key 0 is an in-calls key for an ACD DN of a VMS access group, then Class
of Service must be VMA.
Action:
Severity: Info.
SCH3487
SNMP trap: No
If Class of Service is VMA, then key 0 must be an in-calls key for an ACD DN
of a VMS access group.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1712 of 2360

SCH3492
Cannot remove the primary data service access code option if there are
agents still defined for the DN.
Action:
Severity: Info.
SCH3493
SNMP trap: No
A primary data service access code may not be used as an overflow DN.
Action:
Severity: Info.
SCH3494
SNMP trap: No
Cannot change the VAS ID for a primary data service access code or VMS
access code with agents still defined for the DN.
Action:
Severity: Info.
SCH3496
SNMP trap: No
The data service or primary data service access code option may not be
removed if the ACD DN is defined as the primary access code for a data
service DN.
Action:
Severity: Info.
SCH3497
SNMP trap: No
An overflow DN for a primary data service access code must belong to the
same VAS server (PTE) as the primary access code.
Action:
Severity: Info.
SCH3498
SNMP trap: No
The data service access option or the primary data service access option may
not be set if there agents still defined for the existing ACD DN.
Action:
Severity: Info.
SCH3499
SNMP trap: No
A data service access code may not be an overflow DN for a DN that is not
also a data service access code.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1713 of 2360

SCH3500
ATM package not equipped on this system.

Action:
Severity: Info.
SCH3501
SNMP trap: No
ATM data block already exists.

Action:
Severity: Info.
SCH3502
SNMP trap: No
ATM data block does not exist.

Action:
Severity: Info.
SCH3503
SNMP trap: No
This route TYPE is 3515 not allowed for ATM testing.

Action:
Severity: Info.
SCH3504
SNMP trap: No
Cannot out ATM, route still scheduled for ATM.

Action:
Severity: Info.
SCH3505
SNMP trap: No
Number of DN digits exceeds 10.

Action:
Severity: Info.
SCH3506
SNMP trap: No
ATM DN must be two or more digits long.

Action:
Severity: Info.
SCH3507
SNMP trap: No
PAD value out-of-range.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1714 of 2360

SCH3508
LOSS value out-of-range.

Action:
Severity: Info.
SCH3509
SNMP trap: No
NOISE limit out-of-range.

Action:
Severity: Info.
SCH3510
SNMP trap: No
PERCENT out-of-range.
Action:
Severity: Info.
SCH3513
SNMP trap: No
Customer has no SCH data for this hour, use NEW to create SCH data for this
customer.
Action:
Severity: Info.
SCH3514
SNMP trap: No
Customer already has SCH data for this hour.

Action: Use CHG to change SCH data or OUT to delete the customer's SCH
data from given hour.
Severity: Info.
SCH3515
SNMP trap: No
Cannot OUT RDB; ATM data still associated with RDB.

Action:
Severity: Info.
SCH3516
SNMP trap: No
Hour for SCH data is out-of-range.

Action:
Severity: Info.
SCH3517
SNMP trap: No
Out of service limit is less than maintenance limit.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1715 of 2360

SCH3518
MXTI value is out-of-range.

Action:
Severity: Info.
SCH3519
SNMP trap: No
SNMP trap: No
DN Digit out-of-range.
Action:
Severity: Info.
SCH3520
ATM cannot be performed on this route because FEDC is equal to FEC.

Action:
Severity: Info.
SCH3521
SNMP trap: No
SCI package is not provided.

Action:
Severity: Info.
SCH3522
SNMP trap: No
CCOS package is not implemented.

Action:
Severity: Info.
SCH3523
SNMP trap: No
DN specified is not BCS or PBX DN.

Action:
Severity: Info.
SCH3524
SNMP trap: No
Invalid CCOS restriction level.

Action:
Severity: Info.
SCH3526
SNMP trap: No
This route has not been scheduled for ATM test.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1716 of 2360

SCH3527
This route has already been scheduled for ATM test.

Action:
Severity: Info.
SCH3530
SNMP trap: No
Pad Value must be input (0-63 dB).

Action:
Severity: Info.
SCH3532
SNMP trap: No
Loss value must be input (0-15 dB).

Action:
Severity: Info.
SCH3533
SNMP trap: No
Noise value must be input (27-90 dBrn).

Action:
Severity: Info.
SCH3534
SNMP trap: No
lll ch, B-channel ch of loop lll can be removed when it is idle. ISL channels
need to be idled also.
Action:
Severity: Info.
SCH3545
SNMP trap: No
Threshold set is already deleted.

Action:
Severity: Info.
SCH3546
SNMP trap: No
Cannot remove TSET until all DTI/DLIs assigned to it are removed.

Action:
Severity: Info.
SCH3547
SNMP trap: No
The VAS ID of a data service access code that is defined as the primary
access code for a data service DN may not be changed.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1717 of 2360

SCH3548
If Class of Service is VMA, class must also be VCE.

Action:
Severity: Info.
SCH3549
SNMP trap: No
Server cannot remove access code. It still has agents defined.

Action:
Severity: Info.
SCH3550
SNMP trap: No
VAS Server (PTE) cannot add the access TN because it already exists in the
Server (PTE) data base. This could mean that the data bases do not match.
up), try either:
1. Removing the TN and adding it back in, or 2. Running Audit.
Severity: Info.
SCH3551
SNMP trap: No
VAS Server (PTE) cannot remove the access TN because the access TN does
not exist in the Server (PTE) data base. This could mean that the data bases
do not match.
Action: Ensure compatibility of the shared data bases (when the CSL link is up),
try either:
1. Removing the TN and then removing it, or 2. Running Audit.
Severity: Info.
SCH3552
SNMP trap: No
VAS Server (PTE) cannot add the access code because it already exists in the
Server (PTE) data base. This could mean that the data bases do not match.
up), try either:
1. Removing the DN and adding it back in, or 2. Running Audit.
Severity: Info.
SCH3553
SNMP trap: No
VAS Server (PTE) cannot remove the access code because it does not exist
in the Server (PTE) data base. This could mean that the data bases do not
match.
up), try running Audit.
Severity: Info.
SNMP trap: No
System Messages
Page 1718 of 2360

SCH3554
Server cannot add/remove the voice/data access code because it is a

data/voice access code.
Action:
Severity: Info.
SCH3555
SNMP trap: No
VAS Server (PTE) cannot remove the access TN because it is not in the
Server (PTE) list of TNs belonging to the specified access code. This could
mean that the data bases do not match.
up), try either:
1. Adding the TN back in and then removing it, or 2. Running Audit.
Severity: Info.
SCH3556
SNMP trap: No
VAS Server (PTE) cannot add the access code (if in LD 23) or the access TN
(if in LD 11) because the disk save failed. This could mean that the data bases
do not match.
up), try either:
1. Removing the TN (if in LD 11) or DN (if in LD 23) (OUT) and adding it back in
(NEW), or 2. Running Audit.
Severity: Info.
SCH3557
SNMP trap: No
VAS Server (PTE) cannot remove the access code (if in LD 23) or the access
TN (if in LD 11) because the disk delete failed. This could mean that the data
bases do not match.
up), try either:
1. Adding the TN back in (if in LD 11) or DN (if in LD 23) (OUT) and then removing
it (NEW), or 2. Running Audit.
Severity: Info.
SCH3558
SNMP trap: No
SCD DB LD 73 - No DTI threshold set defined.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1719 of 2360

SCH3559
TRSH may not be defaulted when configuring a new digital loop.

Action:
Severity: Info.
SCH3560
SNMP trap: No
The threshold set is not defined.

Action:
Severity: Info.
SCH3561
SNMP trap: No
If Class of Service is VMA, class must also be IMA.

Action:
Severity: Info.
SCH3562
SNMP trap: No
If Class of Service is IMA, class must also be VCE.

Action:
Severity: Info.
SCH3566
SNMP trap: No
The VMS option (CMS, IMA and IVMS = YES) may not be removed if agents
are still defined for this DN.
Action:
Severity: Info.
SCH3567
SNMP trap: No
An existing ACD DN may not be set up as a VMS access code (CMS, IMA,
and IVMS = YES) if agents are still defined for that DN.
Action:
Severity: Info.
SCH3568
SNMP trap: No
The TN defined as the SADM TN for the indirect CSL (CLS = CMSA) must be
a normal SL-1 set TN (i.e., it cannot be a digital set or a virtual TN; e.g. TYPE
cannot be 4020, CLS = DSI or VMA)
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1720 of 2360

SCH3570
The VAS ID of the Server (PTE) for which the access code is defined (VSID
prompt for either the data service or VMS access code in LD 23) must match
the VAS ID of the Server (PTE) for which the access TN is defined (i.e., the
VAS Server (PTE) for which the DLI loop is defined - DLOP under the VAS
prompt in LD 17).
Action:
Severity: Info.
SCH3571
SNMP trap: No
The TN defined as the SADM TN for the indirect CSL (CLS = CMSA), must not
be a virtual TN on a DLI loop.
Action:
Severity: Info.
SCH3572
SNMP trap: No
IMA may not be turned off if the CSL option is set (CMS = YES) and there are
agents defined for this ACD DN. This is because agents require a special
Class of Service for IMA.
Action:
Severity: Info.
SCH3574
SNMP trap: No
If a DLI loop is specified, then TYPE must be TNB (for LUU).

Action:
Severity: Info.
SCH3575
SNMP trap: No
Invalid CONFIRM return code.

Action:
Severity: Info.
SCH3576
SNMP trap: No
The server has software error. Cannot complete the service change.
Action:
Severity: Info.
SCH3577
SNMP trap: No
The server has data base error. Cannot complete the service change.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1721 of 2360

SCH3579
OPR trunk members not on private line routes, must have DTN COS.
Action:
Severity: Info.
SCH3580
SNMP trap: No
To be OPR allowed, all members must have DTN COS.

Action:
Severity: Info.
SCH3581
SNMP trap: No
ICDR package required.

Action:
Severity: Info.
SCH3582
SNMP trap: No
SLP package not equipped.

Action:
Severity: Info.
SCH3583
SNMP trap: No
PRMA requires WTA COS.

Action:
Severity: Info.
SCH3584
SNMP trap: No
PHTA requires HTA COS.

Action:
Severity: Info.
SCH3586
SNMP trap: No
SNMP trap: No
Invalid CPAS DN.

Action:
Severity: Info.
SCH3587
MCT package not equipped.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1722 of 2360

SCH3588
ACD stations not allowed MCTA COS with X11 Release 18 and earlier.
Action:
Severity: Info.
SCH3589
SNMP trap: No
TRC key is not allowed when telephone is MCTD.

Action:
Severity: Info.
SCH3590
SNMP trap: No
LLC package not equipped.

Action:
Severity: Info.
SCH3591
SNMP trap: No
Only digits 0-9 considered as valid input for the digit count field.
Action:
Severity: Info.
SCH3592
SNMP trap: No
XFA required for MCTA.

Action:
Severity: Info.
SCH3593
SNMP trap: No
OVFL not allowed for PFAN/PFNA.

Action:
Severity: Info.
SCH3594
SNMP trap: No
PRMA not allowed on ACD sets.

Action:
Severity: Info.
SCH3595
SNMP trap: No
PCWA COS requires Call Waiting (CWT) key.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1723 of 2360

SCH3596
This list number was not assigned to this PBX set.

Action:
Severity: Info.
SCH3597
SNMP trap: No
Cannot move an ACD DN with calls store in the queue.

Action:
Severity: Info.
SCH3600
SNMP trap: No
If class is "VMA", class must also be "VCE"(duplicate of 3548).

Action:
Severity: Info.
SCH3601
SNMP trap: No
Directed Call Pickup not equipped.

Action:
Severity: Info.
SCH3603
SNMP trap: No
Value entered is greater than NSCL currently defined.

Action:
Severity: Info.
SCH3604
SNMP trap: No
Cannot allocate memory for SCL header table.

Action:
Severity: Info.
SCH3605
SNMP trap: No
List number entered for SCL is greater than MSCL in the Configuration
Record.
Action:
Severity: Info.
SCH3606
SNMP trap: No
SSCL number is out-of-range.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1724 of 2360

SCH3607
Dialed Name Display cannot exist if CNDA is not configured.

Action:
Severity: Info.
SCH3609
SNMP trap: No
Notification Key Lamp (NKL) already exists for this DN. The set will be
configured without it.
Action:
Severity: Info.
SCH3617
SNMP trap: No
Account key already exists for this ACD set.

Action:
Severity: Info.
SCH3618
SNMP trap: No
Non-ACD sets cannot have an Account key.

Action:
Severity: Info.
SCH3619
SNMP trap: No
Account key cannot be assigned to a Virtual Agent.

Action:
Severity: Info.
SCH3620
SNMP trap: No
ACD Account Code package is not enabled.

Action:
Severity: Info.
SCH3621
SNMP trap: No
Either ACD Package D is not equipped or the agent is not an ICCM acquired
control agent.
Action:
Severity: Info.
SCH3622
SNMP trap: No
SNMP trap: No
Entry is out-of-range.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1725 of 2360

SCH3623
External source number out-of-range.

Action:
Severity: Info.
SCH3624
SNMP trap: No
Flexible Incoming Tones customer options turned off.

Action:
Severity: Info.
SCH3625
SNMP trap: No
PBX Templates have exceeded 255.

Action: Run the Template Audit program.
Severity: Info.
SCH3626
SNMP trap: No
The asterisk * and octothorpe # are not allowed for IDC.

Action: Re-enter the characters.
Severity: Info.
SCH3627
SNMP trap: No
This customer does not have the IDC option enabled.

Action: Use LD 15 to enable IDC for the customer.
Severity: Info.
SCH3628
SNMP trap: No
An IDC tree exists for this customer, as defined in LD 49.

Action: Delete the IDC Tree.
Severity: Info.
SCH3629
SNMP trap: No
System Speed Call List number out-of-range.

Action:
Severity: Info.
SCH3630
SNMP trap: No
THF package is not equipped.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1726 of 2360

SCH3631
THF key and DTA Class of Service are mutually exclusive.

Action:
Severity: Info.
SCH3632
SNMP trap: No
FLH timer out-of-range (256-1536 milliseconds).

Action:
Severity: Info.
SCH3633
SNMP trap: No
THF Class of Service not allowed for this trunk type

Action:
Severity: Info.
SCH3634
SNMP trap: No
Request for deleting IDGT is not in IDC table.

Action: Do PRT to confirm the existence.
Severity: Info.
SCH3635
SNMP trap: No
Conference Hot Line key can only be one-way (i.e., No DN assigned to key.)
reenter.
Action:
Severity: Info.
SCH3636 x y
SNMP trap: No
Longer DN's hundreds group conflict with a shorter hundreds group.

Action: Select a new DN group, where x is the conflicting hundreds group; y is
the shorter existing hundreds group. See Busy Lamp Field feature requirements
in X11 features and services ( 553-3001-305).
Severity: Info.
SCH3637 x y
SNMP trap: No
A shorter existing DN's hundreds group conflict with a longer hundreds.

Action: Select a new DN group, where x is the conflicting hundreds group; y is
the longer existing hundreds group. See Busy Lamp Field feature requirements
in X11 features and services (553-3001-305).
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1727 of 2360

SCH3639
Input expected for Do Not Disturb route.

Action:
Severity: Info.
SCH3640
SNMP trap: No
Private DN conflicts with existing DN.

Action:
Severity: Info.
SCH3641
SNMP trap: No
Cannot step to Private route.

Action:
Severity: Info.
SCH3642
SNMP trap: No
Invalid input for the Agent Observe Tone prompt.

Action: Valid attempts are NO, AGT or ALL. (The default = NO).
Severity: Info.
SCH3643
SNMP trap: No
NCOS, NFCR and IDC packages must be equipped.

Action:
Severity: Info.
SCH3644
SNMP trap: No
SNMP trap: No
DC feature is not active.

Action:
Severity: Info.
SCH3645
DRC route is out-of-range (0-511).

Action:
Severity: Info.
SCH3646
SNMP trap: No
DRC route does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1728 of 2360

SCH3647
DRC route must be DID.

Action:
Severity: Info.
SCH3648
SNMP trap: No
DRC route IDC feature is not active.

Action:
Severity: Info.
SCH3649
SNMP trap: No
DRC route is controlled by a BSC set.

Action: Remove BSC set DRC key that controls the NKDM feature.
Severity: Info.
SCH3650
SNMP trap: No
Input for the maximum redirection counter value out-of-range (0-5).

Action:
Severity: Info.
SCH3651
SNMP trap: No
Pretranslation block does not exist.

Action: Set up pretranslation data block on LD 18
Severity: Info.
SCH3652
SNMP trap: No
The Data Agent Login option = YES. The Virtual Agent option is invalid when
DAL = YES.
Action: Respond to DAL prompt with NO.
Severity: Info.
SCH3653
SNMP trap: No
Pretranslation data block already exists.

Action:
Severity: Info.
SCH3654
SNMP trap: No
Pretranslation data block cannot be removed if PREO = 1.

Action: Set PREO = 0 in LD 15.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1729 of 2360

SCH3655
MOV command is not allowed.

Action:
Severity: Info.
SCH3656
SNMP trap: No
Pretranslation package is restricted.

Action: Enable Pretranslation package.
Severity: Info.
SCH3657
SNMP trap: No
Must set PREO in LD 15 to have pretranslation block printout.

Action:
Severity: Info.
SCH3658
SNMP trap: No
CS key requires that the Speed call or System Speed Call package is
equipped.
Action:
Severity: Info.
SCH3659
SNMP trap: No
Cannot remove CDB if pretranslation block pointer not Nil.

Action: Remove pretranslation data block (LD 18).
Severity: Info.
SCH3662
SNMP trap: No
CFXD has been enabled while the set has an external DN configured for the
CFW key.
Action: Remove the external CFW DN before setting the CFXD Class of
Service.
Severity: Info.
SCH3663
SNMP trap: No
Another SL-1 set already controls DRC route. New DRC key must control a
DID route not currently controlled by a SL-1 set.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1730 of 2360

SCH3664
Another KEY already controls the same DRC route. Only one DRC key is
allowed per DID route.
Action:
Severity: Info.
SCH3665
SNMP trap: No
IDC option was changed from ON to OFF. Route IDC option cannot be turned
off because a BSC set controls it (a DRC key has been configured for a set).
Action: Use LD 81 to find and Release the TN with the TRC key. Use LD 11 to
NUL the key.
Severity: Info.
SCH3666
SNMP trap: No
PR12 loop can only be moved to another PRI loop.

Action:
Severity: Info.
SCH3667
SNMP trap: No
International PRA (PRA2) package is not equipped.

Action:
Severity: Info.
SCH3668
SNMP trap: No
Loop number entered is not a PR12 loop.

Action:
Severity: Info.
SCH3669
SNMP trap: No
ABCD applies only if the DT12 package is equipped.

Action:
Severity: Info.
SCH3670
SNMP trap: No
User either tried to configure ISDN on a CCB route or tried to configure CCB
on an ISDN route.
Action: Either disable CCB on the route and try configuring ISDN again or set
ISDN to NO before setting CCB to Yes.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1731 of 2360

SCH3671
Attempt to out a PRI2 loop from DLOP prompt.

Action: Use a PRI2 prompt to out a PRI2 loop.
Severity: Info.
SCH3672
SNMP trap: No
Attempt to configure an ISDN route without the customer configured for ISDN,
or without DCH configured.
Action: Configure customer with ISDN in LD 15.
Severity: Info.
SCH3673
SNMP trap: No
Customer IDC option cannot be disabled because SL-1 sets control DID route
Day/Night mode.
Action: First NUL all DRC keys on customer SL-1 sets.
Severity: Info.
SCH3674
SNMP trap: No
Cannot out an MCAD entry.

Action:
Severity: Info.
SCH3675
SNMP trap: No
MCAD entry does not exist.

Action:
Severity: Info.
SCH3676
SNMP trap: No
MCAD entry already exists.

Action:
Severity: Info.
SCH3678
SNMP trap: No
Null MCAD entry is not allowed. MCAD entry 0 is already defined as a

continuous tone.
Action:
Severity: Info.
SCH3679
SNMP trap: No
Meridian digital set package not equipped.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1732 of 2360

SCH3680
AOM input is out-of-range.

Action:
Severity: Info.
SCH3681
SNMP trap: No
Corresponding data TN is defined. Cannot assign key 7, its local program now.
Action:
Severity: Info.
SCH3682
SNMP trap: No
Digit display Class of Service (ADD, DDS) is on. Cannot assign key 7 its local
program now.
Action:
Severity: Info.
SCH3683
SNMP trap: No
For 2X16 set, handsfree Class of Service is defined. Cannot assign key 15 as
it is now a handsfree key.
Action:
Severity: Info.
SCH3684
SNMP trap: No
The M2006 does not support the Digit Display Class of Service.
Action:
Severity: Info.
SCH3685
SNMP trap: No
The M2008, M2616, and M2216 sets with key 7 defined as a feature key
already cannot assign Digit Display COS.
Action:
Severity: Info.
SCH3689
SNMP trap: No
The M2000 series data TN key 7 (or key 5 for M2006) of the corresponding
voice TN is defined.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1733 of 2360

SCH3691
TOV input out-of-range.

Action:
Severity: Info.
SCH3692
SNMP trap: No
Wrong OPE input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3693
SNMP trap: No
Wrong TRAN input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3694
SNMP trap: No
Wrong PAR input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3695
SNMP trap: No
Wrong DTR input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3696
SNMP trap: No
Wrong DUP input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3697
SNMP trap: No
Wrong HOT input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3698
SNMP trap: No
Wrong AUT input. Cannot match mnemonics.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1734 of 2360

SCH3699
Wrong BAUD input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3700
SNMP trap: No
Wrong DCD input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3701
SNMP trap: No
Wrong PRM input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3702
SNMP trap: No
Wrong VLL input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3703
SNMP trap: No
Wrong MOD input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3704
SNMP trap: No
Wrong INT input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3705
SNMP trap: No
Wrong CLK input. Cannot match mnemonics.

Action:
Severity: Info.
SCH3706
SNMP trap: No
MPDA/ADATA is either not equipped or response timeout.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1735 of 2360

SCH3707
M2016 cannot be configured as data TN.

Action:
Severity: Info.
SCH3709
SNMP trap: No
PRI2 data does not exist.

Action:
Severity: Info.
SCH3710
SNMP trap: No
The specified ANI data block has configured already (for command NEW).
Action:
Severity: Info.
SCH3711
SNMP trap: No
Incorrect NPA format. It should be N = 2-9, P = 0/1, A = 0-9.

Action:
Severity: Info.
SCH3712
SNMP trap: No
The specified ANI data block has not configured yet (for PRT, CHG, and OUT).
Action:
Severity: Info.
SCH3713
SNMP trap: No
The input value is out-of-range.

Action:
Severity: Info.
SCH3714
SNMP trap: No
The specified input data has been configured already (for command NEW).
Action:
Severity: Info.
SCH3715
SNMP trap: No
Range input is not allowed for SUB response.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1736 of 2360

SCH3716
Ending digit is smaller than the starting digit for range input.
Action:
Severity: Info.
SCH3717
SNMP trap: No
The specified input data has not configured yet.

Action:
Severity: Info.
SCH3718
SNMP trap: No
Timers for this feature are defined in increments of 30 seconds. The timer
value will increase to the next 30 second increment.
Action:
Severity: Info.
SCH3719
SNMP trap: No
SFA not allowed unless FNA is defined.

Action:
Severity: Info.
SCH3720
SNMP trap: No
The Speed Call List for the default (0) Pretranslation Calling Group does not
exist.
Action:
Severity: Info.
SCH3721
SNMP trap: No
Device must be disabled to permit PMS link change.

Action: Disable the link in LD 37.
Severity: Info.
SCH3722
SNMP trap: No
Added loops must be of the same type as DCHL.

Action:
Severity: Info.
SCH3723
SNMP trap: No
ATIM out-of-range (0-126).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1737 of 2360

SCH3724
Invalid Attendant Alternative Answering (AAA) DN type. Valid types are Set
DN (PBX, SL-1, and Digital) and ACD DN.
Action:
Severity: Info.
SCH3725
SNMP trap: No
Invalid card type specified for prompt FDLC. Possible types are XNET
(Network Card), XPEC (Controller), XNPD (Network/DTR Card), ALL.
Action:
Severity: Info.
SCH3726
SNMP trap: No
Invalid download option specified for prompt FDLC.

Action: Enter F for forced download or C for conditional download.
Severity: Info.
SCH3727
SNMP trap: No
Invalid Peripheral Software (PSW) version type specified for prompt FDLC.
Possible values are: L = Latest, C = Current (default), S = specified (1-99).
Action:
Severity: Info.
SCH3728
SNMP trap: No
Invalid Peripheral Software (PSW) version number (1-99) specified for prompt
FDLC.
Action:
Severity: Info.
SCH3729
SNMP trap: No
Download parameter missing or invalid.

Action:
Severity: Info.
SCH3730
SNMP trap: No
Since L (latest) or C (current) has been entered for download type, a version
number cannot be entered.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1738 of 2360

SCH3731
Invalid FDCT pointer found: possible memory corruption.

Action:
Severity: Info.
SCH3732
SNMP trap: No
Missing software for Network Card (NT8D04) on disk.

Severity: Info.
SCH3733
SNMP trap: No
Missing software for Controller (NT8D01) on disk.

Severity: Info.
SCH3734
SNMP trap: No
Error in Mass Storage Unit.

Action: Check Mass Storage Unit.
Severity: Info.
SCH3736
SNMP trap: No
Wrong number of inputs.

Action:
Severity: Info.
SCH3737
SNMP trap: No
SNMP trap: No
Input out-of-range.
Action:
Severity: Info.
SCH3738
Cannot delete Controller defined for the new Network/DTR loop.

Action:
Severity: Info.
SCH3739
SNMP trap: No
The M2006 DN is only allowed on key 0.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1739 of 2360

SCH3740
A PRI2 TN can only be associated with a PRI2 route.

Action:
Severity: Info.
SCH3741
SNMP trap: No
The International Primary Rate Access (IPRA) package is not equipped.

Action:
Severity: Info.
SCH3743
SNMP trap: No
The Load Management (LMAN) package is not equipped.

Action:
Severity: Info.
SCH3744
SNMP trap: No
The Send Message (SMSG) and Get Message (GMSG) keys are only allowed
on ACD sets.
Action:
Severity: Info.
SCH3745
SNMP trap: No
The Send Message (SMSG) and Get Message (GMSG) keys are only allowed
on M2000 series sets with a digit display.
Action:
Severity: Info.
SCH3755
SNMP trap: No
SNMP trap: No
SNMP trap: No
Input out-of-range.
Action:
Severity: Info.
SCH3756
Table does not exist.

Action:
Severity: Info.
SCH3757
Invalid Target. The Target identifiers must be part of the Coordinated Dialing
Plan (CDP) or Uniform Dialing Plan (UDP).
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1740 of 2360

SCH3758
Do not define a Time Overflow Timer (TOFT) if a Day Table for Network ACD
is to be created. Delete TOFT and create the Day Table.
Action:
Severity: Info.
SCH3759
SNMP trap: No
Do not define a Night Call Forward (NCFW) DN if a Night Table for Network
ACD is to be created.
Action: Delete NCFW DN and create the Night Table.
Severity: Info.
SCH3760
SNMP trap: No
Network ACD Target Table is full.

Action:
Severity: Info.
SCH3761
SNMP trap: No
SNMP trap: No
Table already exists.

Action:
Severity: Info.
SCH3762
A Table must be specified for the NEW, CHG, and PRT commands.
Action:
Severity: Info.
SCH3763
SNMP trap: No
Timer for the Target is expected.

Action:
Severity: Info.
SCH3765
SNMP trap: No
An ACD DN cannot be deleted if it has Target Tables assigned to it.

Action: Remove these Tables first.
Severity: Info.
SCH3766
SNMP trap: No
The Network ACD package 178 must be equipped to enter TYPE = NACD.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1741 of 2360

SCH3767
No Target Table of that type exists for this ACD DN.

Action:
Severity: Info.
SCH3768
SNMP trap: No
Too many digits entered for this ACD DN.

Action:
Severity: Info.
SCH3769
SNMP trap: No
Not enough PDS available for that Target Table.

Action:
Severity: Info.
SCH3770
SNMP trap: No
The Network Services package 148, Enhanced Overflow package 178 and
Network ACD package 207, are required for all remote targets.
Action:
Severity: Info.
SCH3771
SNMP trap: No
Network ACD package 178 is not equipped.

Action:
Severity: Info.
SCH3775
SNMP trap: No
Cannot assign an ICI key to a route belonging to a different CPG.

Action:
Severity: Info.
SCH3776
SNMP trap: No
This Listed Directory Number (LDN) belongs to a different CPG and cannot be
reused.
Action:
Severity: Info.
SCH3777
SNMP trap: No
CPG basic package is not equipped.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1742 of 2360

SCH3778
You cannot disable the Multi-Tenant (TENS) feature because some Console
Presentation Groups (CPGs) still exist. For CPG 1-63, when TYPE = CPGP
Action:
Severity: Info.
SCH3779
SNMP trap: No
This customer has CPG Level Services feature enabled already.

Action:
Severity: Info.
SCH3780
SNMP trap: No
You cannot enable Console Presentation Group (CPG) Level services for this
customer, because they have Departmentally Listed DNs (DLDNs) allowed.
The CPG and DLDN features are mutually exclusive.
Action: Go to LD 15 and set DLDN to NO before enabling CPG.
Severity: Info.
SCH3781
SNMP trap: No
Cannot disable the CPG Level Services feature when CPG data blocks (1-63)
still exist.
Action:
Severity: Info.
SCH3782
SNMP trap: No
The basic attendant parameter block of the customer (CPG 0) does not exist.
Action:
Severity: Info.
SCH3783
SNMP trap: No
Shared Tenant Service is not allowed because the CPGs defined for Tenant
Services overlap.
Action: Print out all the CPG Attendant definitions and verify that all Attendants
belong to only one CPG at a time.
Severity: Info.
SCH3784
SNMP trap: No
CPG number is out-of-range (1-63).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1743 of 2360

SCH3785
That CPG data block already exists.

Action:
Severity: Info.
SCH3786
SNMP trap: No
Cannot configure a CPG data block for a CPG without any attendants.
Action:
Severity: Info.
SCH3787
SNMP trap: No
CPG data block does not exist.

Action:
Severity: Info.
SCH3788
SNMP trap: No
Cannot delete a CPG data block when the CPG is still used by tenants/routes.
Action:
Severity: Info.
SCH3789
SNMP trap: No
Cannot remove a CPG while it's associated CPG data block still exists.
Action:
Severity: Info.
SCH3790
SNMP trap: No
Cannot remove the last Attendant from the CPG definition while it's CPG data
block exists.
Action:
Severity: Info.
SCH3792
SNMP trap: No
You cannot remove a Customer Data Block (CDB) while CPG data blocks still
exist.
Action: Remove the CPG data blocks in LD93.
Severity: Info.
SCH3793
SNMP trap: No
The CPG Level Services must be enabled before configuring a CPG data
block.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1744 of 2360

SCH3794
This customer has CPG Level Services feature enabled and therefore cannot
enable the Department Listed DN (DLDN) feature.
Action:
Severity: Info.
SCH3795
SNMP trap: No
The CPG_DEFS/RTE_CPG ORDF block does not exist. Severe data

corruption has occurred. Cannot proceed.
Action:
Severity: Info.
SCH3797
SNMP trap: No
That attendant number belongs to another CPG.

Action:
Severity: Info.
SCH3800
SNMP trap: No
Level 4 can only be removed by removing level 3.

Action:
Severity: Info.
SCH3801
SNMP trap: No
Level 2 cannot be removed for L1 labels.

Action:
Severity: Info.
SCH3802
SNMP trap: No
MFC level 2 does not exist.

Action:
Severity: Info.
SCH3803
SNMP trap: No
Incoming table still exists in an own_nic_blk.

Action:
Severity: Info.
SCH3804
SNMP trap: No
Outgoing table still exists in an nic_blk.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1745 of 2360

SCH3805
Levels 3 and 4 must both be defined.

Action:
Severity: Info.
SCH3806
SNMP trap: No
During call processing may cause problems.

Action:
Severity: Info.
SCH3807
SNMP trap: No
Translation type not tab for customer.

Action:
Severity: Info.
SCH3808
SNMP trap: No
No DN-PSA translation table.

Action:
Severity: Info.
SCH3809
SNMP trap: No
Entries still in DN-PSA translation table.

Action:
Severity: Info.
SCH3810
SNMP trap: No
SNMP trap: No
SNMP trap: No
DN already in table.
Action:
Severity: Info.
SCH3811
DN not in table.
Action:
Severity: Info.
SCH3812
More than one Radio Paging System exists. Table entries must be removed
before resetting to single system.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1746 of 2360

SCH3813
EXOP not allowed without FFC package equipped.

Action:
Severity: Info.
SCH3814
SNMP trap: No
Input for CDTO prompt is out-of-range (0-10).

Action:
Severity: Info.
SCH3815
SNMP trap: No
No ASEQ currently defined.

Action:
Severity: Info.
SCH3816
SNMP trap: No
ASEQ input is out-of-range (0-9).

Action:
Severity: Info.
SCH3817
SNMP trap: No
FFC state is being set to zero due to conflict with the new ASEQ.
Action:
Severity: Info.
SCH3818
SNMP trap: No
FFC conflicts with another FFC's numeric equivalent.

Action:
Severity: Info.
SCH3819
SNMP trap: No
Numeric equivalent conflicts in the DN translator.

Action:
Severity: Info.
SCH3820
SNMP trap: No
FFC and/or equivalent conflicts with an already existing DN.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1747 of 2360

SCH3821
The Scheduled Access Restriction package is not equipped.

Action:
Severity: Info.
SCH3822
SNMP trap: No
Attempting to create a new Authcode when the number of digits for the
Authcode ALEN, is zero.
Action:
Severity: Info.
SCH3823
SNMP trap: No
Maximum Scheduled Access Restriction Group is out-of-range (0-127).

Action:
Severity: Info.
SCH3824
SNMP trap: No
The number of digits of the Authorization code to be validated is outside of the

range (0, ALEN), where ALEN is the number of digits in the Authorization code
itself.
Action:
Severity: Info.
SCH3825
SNMP trap: No
The response is other than YES or NO.

Action:
Severity: Info.
SCH3826
SNMP trap: No
The CRCS value is outside of the range (0-7).

Action:
Severity: Info.
SCH3827
SNMP trap: No
The TGAR value is outside of the range (0-15).

Action:
Severity: Info.
SCH3828
SNMP trap: No
Unable to match the input with the Stored Service Mnemonics.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1748 of 2360

SCH3829
Cannot create aut block when ALEN = 0.

Action:
Severity: Info.
SCH3830
SNMP trap: No
There is no room in the AUTH Pointer Table.

Action:
Severity: Info.
SCH3831
SNMP trap: No
{CR} is not allowed when AUTH Block SARG number for GRP is expected.
Action:
Severity: Info.
SCH3832
SNMP trap: No
The SARG number is outside of the range (1, SMAX) where SMAX is the
maximum SARG number allowed.
Action:
Severity: Info.
SCH3833
SNMP trap: No
The SAR Block does not yet exist for this customer.
Action:
Severity: Info.
SCH3834
SNMP trap: No
No AUTH Blocks exist for this customer.

Action:
Severity: Info.
SCH3835
SNMP trap: No
The hour and/or minute entered for the off-period Start/Stop times is
out-of-range.Where: HH= Hour, MM= Minute, and HH is greater than or equal
to 0, and less than or equal to 23;
MM is greater than or equal to 0 and less than or equal to 59
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1749 of 2360

SCH3836
Higher SAR group number exists.

Action:
Severity: Info.
SCH3837
SNMP trap: No
{CR} is not allowed for the lock request.

Action:
Severity: Info.
SCH3838
SNMP trap: No
The lock number must be either 1 or 2, to correspond to one of the two

off-periods.
Action:
Severity: Info.
SCH3839
SNMP trap: No
Attempting to print a non-existing service code corresponding to the

authorization code entered.
Action:
Severity: Info.
SCH3840
SNMP trap: No
ATD is not allowed on input. Enter ATA or either CUS or GRP. For the latter
two, ATD is implied.
Action:
Severity: Info.
SCH3841
SNMP trap: No
Attempting to remove or change a non-existent SARG entry.

Action:
Severity: Info.
SCH3843
SNMP trap: No
{CR} is not allowed for SMAX prompt.

Action:
Severity: Info.
SCH3844
SNMP trap: No
{CR} is not allowed for AVAL prompt.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1750 of 2360

SCH3845
Attempting to lock onto an unusual off-period time (both START and STOP
times are zero).
Action:
Severity: Info.
SCH3846
SNMP trap: No
The Authcode entry pointer does not point to the start of the storage
corresponding to the Authcode entered (This should never occur).
Action:
Severity: Info.
SCH3847
SNMP trap: No
Attempting to enter extra information on the same line as the service data
which must appear by itself.
Action:
Severity: Info.
SCH3848
SNMP trap: No
{CR} is not allowed for services which the command is not a change.
Action:
Severity: Info.
SCH3849
SNMP trap: No
Requesting to print a single Authcode which does not exist.

Action:
Severity: Info.
SCH3850
SNMP trap: No
Attempting to insert the Authcode data when it's location is unknown.

Action:
Severity: Info.
SCH3851
SNMP trap: No
SS table number is out-of-range.

Action:
Severity: Info.
SCH3852
SNMP trap: No
SS head table does not exist.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1751 of 2360

SCH3853
Entry does not exist in table.

Action:
Severity: Info.
SCH3854
SNMP trap: No
Receive section of table is full.

Action:
Severity: Info.
SCH3855
SNMP trap: No

Action:
Severity: Info.
SCH3856
SNMP trap: No

Action:
Severity: Info.
SCH3857
SNMP trap: No
Invalid function for this table.

Action:
Severity: Info.
SCH3858
SNMP trap: No
Network package denied.

Action:
Severity: Info.
SCH3859
SNMP trap: No
Attempt to assign more than one CPR key on a SL-1 set.

Action:
Severity: Info.
SCH3860
SNMP trap: No
Digit display is required for CPR feature.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1752 of 2360

SCH3861
More than 4 characters were entered.

Action:
Severity: Info.
SCH3862
SNMP trap: No
ASCII count variable is less than zero.

Action:
Severity: Info.
SCH3864
SNMP trap: No
Remove NWK ACOD when changing to 11.

Action:
Severity: Info.
SCH3889
SNMP trap: No
Response to SUPN INC was RVBD.

Action: Response to SUPN OUT must be RVBD.
Severity: Info.
SCH3890
SNMP trap: No
DN length conflicts with DNs already existing in DN-PSA translation table.

Action:
Severity: Info.
SCH3891
SNMP trap: No
Protected block length for station input not accepted.

Action:
Severity: Info.
SCH3900
SNMP trap: No
Multi-Tenant Service package is restricted.

Action:
Severity: Info.
SCH3901
SNMP trap: No
Only ALOW or DENY can be entered.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1753 of 2360

SCH3902
Only one input field allowed.

Action:
Severity: Info.
SCH3903
SNMP trap: No
SNMP trap: No
Null input not allowed.

Action:
Severity: Info.
SCH3904
Tenant Service is not enabled for this customer.

Action:
Severity: Info.
SCH3905
SNMP trap: No
Not all attendant console groups have been removed.

Action:
Severity: Info.
SCH3906
SNMP trap: No
NEW or OUT is not allowed for this TYPE.

Action:
Severity: Info.
SCH3907
SNMP trap: No
CHG is not allowed for this TYPE.

Action:
Severity: Info.
SCH3908
SNMP trap: No
Not all Route ACCESS_ARRAY blocks have been removed.

Action:
Severity: Info.
SCH3909
SNMP trap: No
Not all Tenant ACCESS_ARRAY blocks have been removed.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1754 of 2360

SCH3910
Tenant number out-of-range.

Action:
Severity: Info.
SCH3911
SNMP trap: No
Route number out-of-range.

Action:
Severity: Info.
SCH3912
SNMP trap: No
Attendant Console Presentation Group number out-of-range.

Action:
Severity: Info.
SCH3913
SNMP trap: No
Cannot OUT Multi-Tenant. There are still sets which belong to a tenant (have
Class of Service TENA).
Action:
Severity: Info.
SCH3914
SNMP trap: No
Attendant Console number out-of-range.

Action:
Severity: Info.
SCH3915
SNMP trap: No
Attendant Console Presentation Group cannot be removed while it is specified

for a Tenant or a Route.
Action:
Severity: Info.
SCH3916
SNMP trap: No
Attendant Console Presentation Group Definitions block, CPG_DEFS, is

missing.
Action:
Severity: Info.
SCH3917
SNMP trap: No
Tenant Ordinals block, TEN_CPG_ORDLS, is missing.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1755 of 2360

SCH3918
Route Ordinals block, RTE_CPG_ORDLS, is missing.

Action:
Severity: Info.
SCH3919
SNMP trap: No
Invalid response to ALOW or DENY.

Action:
Severity: Info.
SCH3920
SNMP trap: No
Attendant Console Presentation Group 0 is not service changeable.

Action:
Severity: Info.
SCH3921
SNMP trap: No
Tenant Service is already configured for this Customer.

Action:
Severity: Info.
SCH3922
SNMP trap: No
Attendant Console Presentation Group is already configured.

Action:
Severity: Info.
SCH3923
SNMP trap: No
Attendant Console Presentation Group is not configured.

Action:
Severity: Info.
SCH3924
SNMP trap: No
A Tenant cannot be denied access to itself.

Action:
Severity: Info.
SCH3925
SNMP trap: No
Response to AUTR is invalid.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1756 of 2360

SCH3926
Digital set package is unequipped.

Action:
Severity: Info.
SCH3927
SNMP trap: No
Touchphone set package is unequipped.

Action:
Severity: Info.
SCH3928
SNMP trap: No
TN type does not match with the corresponding voice or data TN.
Action:
Severity: Info.
SCH3929
SNMP trap: No
Loop must be quadruple density loop for Touchphone or Digital set.

Action:
Severity: Info.
SCH3930
SNMP trap: No
Maximum number of keys is either 9, 11, or 18 for compact sets.

Action:
Severity: Info.
SCH3931
SNMP trap: No
No default for MXKY if defining a new compact set.

Action:
Severity: Info.
SCH3932
SNMP trap: No
Keys 6-16 are reserved for future key expansion on Touchphone.

Action:
Severity: Info.
SCH3933
SNMP trap: No
Default keys for Touchphone are not allowed if a new set is being defined
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1757 of 2360

SCH3934
This key feature only applicable on SL-1 sets.

Action:
Severity: Info.
SCH3935
SNMP trap: No
1. For M3000 Data PDN must match DN of key 17 for the voice TN.
2. For M2317: Data PDN must match DN of key 10 for the voice TN.
Action: 1. Change key 17 of the Voice TN to null, then change the data PDN to
the appropriate PDN and define key 17 for the voice TN once again. 2. Change
key 10 of the Voice TN to null, then change the data PDN to the appropriate PDN
and define key 10 for the voice TN once again.
Severity: Info.
SCH3936
SNMP trap: No
Cannot delete the data TN until key 10 of the M2317, or key 17 of the M3000
is changed to NUL.
Action:
Severity: Info.
SCH3938
SNMP trap: No
TN types for voice and data ports of a Digital set do not match.
Action:
Severity: Info.
SCH3939
SNMP trap: No
For M3000: Key 17 of voice TN must be NULL before changing PDN of data
TN. For M2317: Key 10 of voice TN must be NULL before changing PDN of
data TN.
Action:
Severity: Info.
SCH3941
SNMP trap: No
For Touchphone, key 0-5 can only be SCR/N, MCR/N, PLR/N and DIG.
Action:
Severity: Info.
SCH3942
SNMP trap: No
For Touchphone and M2000 series digital sets, this feature cannot be defined
for this key number (17-35).
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1758 of 2360

SCH3943
Only Digital sets, M3000 sets, ISDLC cards or Digitone Receivers can be
quadruple density.
Action:
Severity: Info.
SCH3944
SNMP trap: No
Cannot have CMSA Class of Service for digital telephones.

Action:
Severity: Info.
SCH3945
SNMP trap: No
VCE is used for voice TNs, DTA is used for data TNs. For digital line cards the
TN unit range is: VCE = 0-7, DTA 8-15. For NT8D02: VCE = 0-15, DTA =
16-31.
Action:
Severity: Info.
SCH3946
SNMP trap: No
Cannot move a digital voice TN to a data TN or vice versa.

Action:
Severity: Info.
SCH3947
SNMP trap: No
The corresponding voice/data TN of the moved digital telephone TN should

also
Action:
Severity: Info.
SCH3948
SNMP trap: No
The telephone type of the moving TN does not match with the set type of the
corresponding voice/data TN of the TOTN.
Action:
Severity: Info.
SCH3949
SNMP trap: No
Cannot change double density card (BCS card) to quadruple density card
(ISDLC card).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1759 of 2360

SCH3953
The modem TN must be in the same customer group as the ADM trunk.
Action:
Severity: Info.
SCH3954
SNMP trap: No
The Touchphone data DN can have only two members, the voice TN and the
data TN.
Action:
Severity: Info.
SCH3955
SNMP trap: No
2009, 2018, and 2112 cannot be ACD sets.

Action:
Severity: Info.
SCH3956
SNMP trap: No
RANF, RAN1, RAN2 must be assigned a different route number. With the
Multiple Language Wake Up (MLWU) feature, RANF, RAN1 and RAN2 must
be different from language routes (LA11 through LA52 in LD 15).
Action:
Severity: Info.
SCH3959
SNMP trap: No
A non-PRI loop number was specified in the TN, but the route member is PRA
mode.
Action:
Severity: Info.
SCH4000
SNMP trap: No
Number of characters specified for a block identification line is out-of-range.

Action:
Severity: Info.
SCH4001
SNMP trap: No
The maximum number of block IDs is out-of-range.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1760 of 2360

SCH4002
An attempt was made to increase the RIT but there is not enough protected
storage.
Action: Remove and copy manually.
Severity: Info.
SCH4003
SNMP trap: No
RANF, RAN1, RAN2 must be assigned to different routes.

Action:
Severity: Info.
SCH4021
SNMP trap: No
Cannot remove Speed Call List which is used as a pretranslation list in the
speed call data block.
Action:
Severity: Info.
SCH4022
SNMP trap: No
Response AONW is out-of-range (3-32768).

Action:
Severity: Info.
SCH4023
SNMP trap: No
FFW key is already defined.

Action:
Severity: Info.
SCH4024
SNMP trap: No
Private Line routes are not applicable.

Action:
Severity: Info.
SCH4025
SNMP trap: No
Route entered cannot be a RAN Route.

Action:
Severity: Info.
SCH4050
SNMP trap: No
ALEN must be in the range ({AVAL}, 16).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1761 of 2360

SCH4061
Before Release 10: VNET route has changed to a Non-VNET route. After
Release 10: VNET route has changed to a Non-VNET route. CMFI has been
zeroed.
Action: Use LD 14 or manual initialize to allocate extra memory for CPN trunks.
Severity: Info.
SCH4062
SNMP trap: No
Before Release 10: NON-VNET route has changed to a VNET route. After
Release 10: VNET route has changed to a Non-VNET route. ISST has been
zeroed.
Action: Use LD 14 or manual initialize to allocate extra memory for CPN trunks.
Severity: Info.
SCH4063
SNMP trap: No
SNMP trap: No
Private line route.

Action:
Severity: Info.
SCH4064
No CAS keys defined for this CUST.

Action:
Severity: Info.
SCH4065
SNMP trap: No
Conference loop increase out-of-range (larger than 79).

Action:
Severity: Info.
SCH4066
SNMP trap: No
Different Multifrequency signaling method defined for this route.

Action:
Severity: Info.
SCH4067
SNMP trap: No
Trunks must be removed before changing MF signaling type.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1762 of 2360

SCH4068
MFE Signaling allowed on incoming trunks only.

Action:
Severity: Info.
SCH4069
SNMP trap: No
DN size for pretranslation table must be less than 5.

Action:
Severity: Info.
SCH4070
SNMP trap: No
Incoming non-VNET routes using L1 MFC cannot be assigned tables which

contain more than 2 levels of signaling.
Action:
Severity: Info.
SCH4071
SNMP trap: No
Route entered does not exist.

Action:
Severity: Info.
SCH4072
SNMP trap: No
MAXN must be greater than 0 for TYPE = ACG.

Action:
Severity: Info.
SCH4073
SNMP trap: No
Value for MAXN out-of-range (1-63).

Action:
Severity: Info.
SCH4074
SNMP trap: No
Only two input fields allowed.

Action:
Severity: Info.
SCH4075
SNMP trap: No
Only NITE or an AGNO accepted for second option.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1763 of 2360

SCH4076
NTNO cannot be greater than 4 digits.

Action:
Severity: Info.
SCH4077
SNMP trap: No
DN entered must be an LDN.

Action:
Severity: Info.
SCH4078
SNMP trap: No
Route must be outgoing for RACC and incoming for RACG.

Action:
Severity: Info.
SCH4079
SNMP trap: No
Attendant Console Groups exist greater than MAXN.

Action:
Severity: Info.
SCH4080
SNMP trap: No
Loop density must be 4D or DD.

Action:
Severity: Info.
SCH4081
SNMP trap: No
Local tone out-of-range (0-3).

Action:
Severity: Info.
SCH4082
SNMP trap: No
HFA/HFD only allowed for M2018 sets.

Action:
Severity: Info.
SCH4083
SNMP trap: No
DTA only allowed for Digital sets.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1764 of 2360

SCH4084
Invalid card type for Digital set TN.

Action:
Severity: Info.
SCH4085
SNMP trap: No
Single density not allowed for Digital sets.

Action:
Severity: Info.
SCH4086
SNMP trap: No
Cannot change DTA/VCE Class of Service.

Action:
Severity: Info.
SCH4100
SNMP trap: No
LDN has a Tenant Number cannot be deleted or changed.

Action:
Severity: Info.
SCH4101
SNMP trap: No
ALDN Group cannot be used at a satellite node.

Action:
Severity: Info.
SCH4102
SNMP trap: No

Action:
Severity: Info.
SCH4103
SNMP trap: No
A LDN number higher than input value for MAXN is defined.

Action:
Severity: Info.
SCH4104
SNMP trap: No
Input for prompt ICIM must be one of NON, LDN0, LDN1, LDN2, LDN3 or
{CR}.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1765 of 2360

SCH4105
Input not accepted - Tenant Data Defined.

Action:
Severity: Info.
SCH4106
SNMP trap: No
A tenant number which is higher than input value for MXTN is defined in
protected data.
Action:
Severity: Info.
SCH4107
SNMP trap: No
No package that uses station group data is equipped.

Action:
Severity: Info.
SCH4108
SNMP trap: No
Tenant number must be in the range 0 to MXTN in LD 15.

Action:
Severity: Info.
SCH4109
SNMP trap: No
Station Group already defined.

Action:
Severity: Info.
SCH4110
SNMP trap: No
Attendant number defined in a console group.

Action:
Severity: Info.
SCH4111
SNMP trap: No
Cannot remove route mapped to an ACG.

Action:
Severity: Info.
SCH4112
SNMP trap: No
Cannot accept OGT for route mapped to ACG.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1766 of 2360

SCH4113
Station group not defined.

Action:
Severity: Info.
SCH4115
SNMP trap: No
Warning: Counting edge of PPM pulse bit(s) for the DTI loop is not compatible
with the incoming CONN(s) signal in the signaling category table entered.
Metering will not be performed on this channel.
Action:
Severity: Info.
SCH4116
SNMP trap: No
Warning: Route entered for DTI channel has battery reversal type of metering.
Metering will not be performed on this channel.
Action:
Severity: Info.
SCH4117
SNMP trap: No
Warning: DTI loop has PPM pulse bit(s) defined but entered route does not
have PPM type of metering. Metering will not be performed on this channel.
Action:
Severity: Info.
SCH4118
SNMP trap: No
Warning: Entered route has PPM type of metering, but DTI loop does not have
PPM pulse bit(s) defined. Metering will not be performed on this channel.
Action:
Severity: Info.
SCH4119
SNMP trap: No
SNMP trap: No
SNMP trap: No
No DTI TNs exist.

Action:
Severity: Info.
SCH4120
Entry out-of-range.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1767 of 2360

SCH4121
Invalid loop type entered.

Action: For JDMI and DTI2, you must enter JDMI loop. For pR12, a PR12 loop
is required.
Severity: Info.
SCH4122
SNMP trap: No
SNMP trap: No
DTI data does not exist.

Action:
Severity: Info.
SCH4123
Timers cannot be created.

Action:
Severity: Info.
SCH4124
SNMP trap: No
SNMP trap: No
SNMP trap: No
Channel out-of-range.
Action:
Severity: Info.
SCH4125
DTI loop is not defined.

Action:
Severity: Info.
SCH4126
Signaling/pad category does not exist.

Action:
Severity: Info.
SCH4127
SNMP trap: No
Signaling/pad category table cannot be removed because there are no

references to the table.
Action:
Severity: Info.
SCH4128
SNMP trap: No
Signaling/pad category already exists.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1768 of 2360

SCH4129
Invalid abcd code.

Action:
Severity: Info.
SCH4130
SNMP trap: No
Non-compatible loops (digital and analog).

Action:
Severity: Info.
SCH4131
SNMP trap: No
DTI2 package is not equipped.

Action:
Severity: Info.
SCH4132
SNMP trap: No
Timers cannot be removed.

Action:
Severity: Info.
SCH4133
SNMP trap: No
Timer values must be in a descending order.

Action:
Severity: Info.
SCH4134
SNMP trap: No
SNMP trap: No
Non-analog loop.
Action:
Severity: Info.
SCH4136
Destination loop is not the same type as source loop.

Action:
Severity: Info.
SCH4137
SNMP trap: No
Not allowed for a DTI loop.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1769 of 2360

SCH4138
Channel-TN conversation failed.

Action:
Severity: Info.
SCH4139
SNMP trap: No
Signaling category can accept no more TNs.

Action:
Severity: Info.
SCH4140
SNMP trap: No
Device must be disabled to permit end link change.

Action:
Severity: Info.
SCH4141
SNMP trap: No
CND package restricted.

Action:
Severity: Info.
SCH4142
SNMP trap: No
CND user should be only user of physical unit.

Action:
Severity: Info.
SCH4143
SNMP trap: No
CND name length exceeds maximum allowed.

Action:
Severity: Info.
SCH4144
SNMP trap: No
SNMP trap: No
Illegal ASCII character.

Action:
Severity: Info.
SCH4145
Attempt to remove name in command NEW.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1770 of 2360

SCH4146
Cannot find CND data in line block.

Action:
Severity: Info.
SCH4147
SNMP trap: No
YES or NO only legal response to the prompt.

Action:
Severity: Info.
SCH4148
SNMP trap: No
Entry out-of-range (0-127).

Action:
Severity: Info.
SCH4149
SNMP trap: No
Attempt to remove display in command YES.

Action:
Severity: Info.
SCH4150
SNMP trap: No
Display is not configured.

Action:
Severity: Info.
SCH4151
SNMP trap: No
Display is not assigned to this customer.

Action:
Severity: Info.
SCH4152
SNMP trap: No
Entry out-of-range (0-63).

Action:
Severity: Info.
SCH4153
SNMP trap: No
Attempt to remove display group in command NEW.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1771 of 2360

SCH4154
Group is not configured.

Action:
Severity: Info.
SCH4155
SNMP trap: No
Unable to change name due to name block overflow.

Action:
Severity: Info.
SCH4156
SNMP trap: No
Display is already configured.

Action:
Severity: Info.
SCH4157
SNMP trap: No
Invalid CND display type.

Action:
Severity: Info.
SCH4158
SNMP trap: No
CND display type conflict.

Action:
Severity: Info.
SCH4159
SNMP trap: No
SNMP trap: No
SCTRNTRANS failed.
Action:
Severity: Info.
SCH4160
ICI key is already assigned to area.

Action:
Severity: Info.
SCH4161
SNMP trap: No
Legal ICI key is assigned to area.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1772 of 2360

SCH4162
Illegal response to area.

Action:
Severity: Info.
SCH4163
SNMP trap: No
Input to area out-of-range.

Action:
Severity: Info.
SCH4164
SNMP trap: No
CND display group does not exist.

Action:
Severity: Info.
SCH4165
SNMP trap: No
CND display group must be entered except PRT.

Action:
Severity: Info.
SCH4166
SNMP trap: No
CND display group out-of-range (0-63).

Action:
Severity: Info.
SCH4167
SNMP trap: No
CND display number must be entered.

Action:
Severity: Info.
SCH4168
SNMP trap: No
CND display number out-of-range (0-127).

Action:
Severity: Info.
SCH4169
SNMP trap: No
CND display group already exists.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1773 of 2360

SCH4170
Maximum 10 groups entered in one pass.

Action:
Severity: Info.
SCH4171
SNMP trap: No
CND display is not assigned to this customer.

Action:
Severity: Info.
SCH4172
SNMP trap: No
CND display is already assigned.

Action:
Severity: Info.
SCH4173
SNMP trap: No
CND display must be entered except PRT.

Action:
Severity: Info.
SCH4174
SNMP trap: No
Request for CND name memory is too large.

Action:
Severity: Info.
SCH4175
SNMP trap: No
CND link is not configured.

Action:
Severity: Info.
SCH4176
SNMP trap: No
CNDGROUPTBL BLK cannot be created, NIL PTR returns from

GET_PDATA_BLK, DISI will not be created.
Action:
Severity: Info.
SCH4177
SNMP trap: No
CND_DISPLAYS BLK cannot be created, NIL PTR returns from

GET_PDATA_BLK, DISI will not be created.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1774 of 2360

SCH4178
CNDMONITORAREA BLK cannot be created, NIL PTR returns from

GET_UDATA_BLK, DISI will not be created.
Action:
Severity: Info.
SCH4179
SNMP trap: No
CND display must be disabled to be removed from configuration.

Action:
Severity: Info.
SCH4180
SNMP trap: No
Display is already assigned to attendant.

Action:
Severity: Info.
SCH4181
SNMP trap: No
CND must be removed before CND TTY.

Action:
Severity: Info.
SCH4193
SNMP trap: No
AC15B trunk is still attached.

Action:
Severity: Info.
SCH4194
SNMP trap: No
CMF must be entered for GEC NLC class.

Action:
Severity: Info.
SCH4195
SNMP trap: No
Input value must be EM4.

Action:
Severity: Info.
SCH4196
SNMP trap: No
SNMP trap: No
Input must be A15B.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1775 of 2360

SCH4197
The NLC trade mark is not GEC.

Action:
Severity: Info.
SCH4198
SNMP trap: No
SNMP trap: No
CLS must be CMF.

Action:
Severity: Info.
SCH4199
Input must be NT or GEC.

Action:
Severity: Info.
SCH4200
SNMP trap: No
CLS of AAA and FNA conflict.

Action:
Severity: Info.
SCH4201
SNMP trap: No
No Authcode table defined for this customer.

Action:
Severity: Info.
SCH4202
SNMP trap: No
VNET route has changed to NON-VNET route. CMFI contained greater than
2 levels of signaling, so it was zeroed.
Action:
Severity: Info.
SCH4203
SNMP trap: No
VNET route has changed to NON-VNET route. ISST has been zeroed.
Action:
Severity: Info.
SCH4204
SNMP trap: No
60 or 70 ms is not supported when TDSO = NO, or 50 ms is not supported

when TDSO = YES.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1776 of 2360

SCH4206
TTY 15 is reserved for HIST file.

Action:
Severity: Info.
SCH4209
SNMP trap: No
BGD or PMS not allowed for user prompt if device is PRT.

Action:
Severity: Info.
SCH4211
SNMP trap: No
Auto and R2 mode cannot be configured at the same time. Auto takes
precedence and R2 mode feature will be turned off.
Action:
Severity: Info.
SCH4212
SNMP trap: No
Empty block is not allowed.

Action:
Severity: Info.
SCH4213
SNMP trap: No
This package cannot be enabled without the Enhanced QoS package (401)
being enabled.
Action:
Severity: Major.
SCH4365
SNMP trap: No
This conference loop is used for AWU.

Action:
Severity: Info.
SCH4500
SNMP trap: No
You must first define the LSC in LD15 before using the TIDY prompt.
Action:
Severity: Info.
SCH4501
SNMP trap: No
Two entries are required for table.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1777 of 2360

SCH4502
Calling number is out-of-range.

Action:
Severity: Info.
SCH4503
SNMP trap: No
Speed Call List number is out-of-range.

Action:
Severity: Info.
SCH4504
SNMP trap: No
SNMP trap: No
No table SCL pointer.

Action:
Severity: Info.
SCH4505
128 blocks are already configured (for command NEW).

Action:
Severity: Info.
SCH4506
SNMP trap: No
SNMP trap: No
PREO is out-of-range.
Action:
Severity: Info.
SCH4507
Invalid response entered.

Action:
Severity: Info.
SCH4508
SNMP trap: No
Invalid number of parameters entered.

Action:
Severity: Info.
SCH4515
SNMP trap: No
JCO/LST/LNT applies to CO loopstart non-digital trunk only.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1778 of 2360

SCH4516
M2317 set requires DLT2 package (91).

Action:
Severity: Info.
SCH4517
SNMP trap: No
Package for Caller's Name Display not equipped.

Action:
Severity: Info.
SCH4518
SNMP trap: No
Wrong telephone type.

Action: Set must have a digit display for CNDA/DNDA Class of Service.
Severity: Info.
SCH4519
SNMP trap: No
M2317: invalid feature for specified key number.

Action:
Severity: Info.
SCH4520
SNMP trap: No
Delta II, soft key feature may not be assigned to programmable keys (0
through 10).
Action:
Severity: Info.
SCH4521
SNMP trap: No
M2317 sets with the data option must have key 10 defined as an SCR DN.
Action: If the data option is being specified for this set (CLS = DTA), key 10 must
be defined on the voice TN as an SCR key with the same DN as Data Prime DN
(key 0). You cannot assign a feature to this key.
Severity: Info.
SCH4522
SNMP trap: No
M2317 key is hardwired for handsfree and is not allowed to be defined.

Action:
Severity: Info.
SCH4523
SNMP trap: No
Data DN key cannot be changed in Attendant Administration.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1779 of 2360

SCH4524
This key feature cannot be defined in Attendant Administration.

Action:
Severity: Info.
SCH4525
SNMP trap: No
Package for Digit Display not equipped, which is required for Caller's Name
Display or Dialed Name Display; or NDD Class of Service is not allowed with
CNDA or DNDA Class of Service.
Action:
Severity: Info.
SCH4526
SNMP trap: No
Supervisory Console package equipped. BCS stations cannot be allocated to

card with attendant assigned.
Action:
Severity: Info.
SCH4527
SNMP trap: No
Supervisory Console package equipped.

Action: Attendant prime TN must be on unit 0 for single density cards. For
double density cards, the jprime DN must be on unit 0 or unit 4.
Severity: Info.
SCH4528
SNMP trap: No
Supervisory Console package equipped. Attendant console cannot share card

with other stations.
Action:
Severity: Info.
SCH4529
SNMP trap: No
Supervisory Console package equipped. Prime and secondary TN must be

consecutive.
Action:
Severity: Info.
SCH4530
SNMP trap: No
Threshold out-of-range (1-255).

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1780 of 2360

SCH4531
Threshold must be greater than or equal to previous threshold.

Action:
Severity: Info.
SCH4532
SNMP trap: No
TN does not exist in LD 15.

Action:
Severity: Info.
SCH4533
SNMP trap: No
Supervisory Console is in Service Observation mode.

Action:
Severity: Info.
SCH4534
SNMP trap: No
SNR package not equipped.

Action:
Severity: Info.
SCH4535
SNMP trap: No
Last Number Redial (LNR) has not been defined in the Customer data block
(LD 15).
Action:
Severity: Info.
SCH4536
SNMP trap: No
The size entry for Last Number Redial (LNR) is invalid.

Action:
Severity: Info.
SCH4537
SNMP trap: No
The Class of Service for Last Number Redial (LNR) has not been specified for
this set.
Action:
Severity: Info.
SCH4538
SNMP trap: No
This type of Alpha terminal, M2317, or M3000 is not supported by the LNR
feature.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1781 of 2360

SCH4541
The attendant console being assigned as Supervisor is out-of-range (1-63).

Action:
Severity: Info.
SCH4542
SNMP trap: No
Both Busy Lamp Field (BLF) arrays of the customer are already assigned.
Action:
Severity: Info.
SCH4543
SNMP trap: No
The Lamp Field Array option is not assigned.

Action:
Severity: Info.
SCH4549
SNMP trap: No
(SWA) Class of Service cannot be defined without having a Call Waiting key/
lamp pair defined for SL-1 sets.
Action:
Severity: Info.
SCH4550
SNMP trap: No
For 500/2500 sets with Station Loop Preemption (SLP), sets with SWA Class
of Service must have Call Waiting Allowed (CWA). Also, SWA is mutually
exclusive with Call Waiting Denied (CWD) and Precedence Call Waiting
Denied (PCWD).
Action:
Severity: Info.
SCH4552
SNMP trap: No
OUT or NEW not valid for unit 0.

Action:
Severity: Info.
SCH4553
SNMP trap: No
For M2317 sets, the COS for Message Waiting is denied if the Message
Waiting Key (MWK) has not been assigned, since the common audible
signaling is not supported.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1782 of 2360

SCH4555
A source cannot be a target for itself.

Action:
Severity: Info.
SCH4556
SNMP trap: No
CPND data block must be removed before the customer data block.
Action:
Severity: Info.
SCH4560
SNMP trap: No
Number of trees must be input (LD 15).

Action:
Severity: Info.
SCH4561
SNMP trap: No
Tree number is out-of-range for LD 15 (0-254).

Action:
Severity: Info.
SCH4562
SNMP trap: No

Action:
Severity: Info.
SCH4563
SNMP trap: No
SNMP trap: No
Tree does not exist.

Action:
Severity: Info.
SCH4565

Action:
Severity: Info.
SCH4566
SNMP trap: No
SNMP trap: No
Illegal range requested.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1783 of 2360

SCH4567
Code value out-of-range, range is 100 - 9999.

Action:
Severity: Info.
SCH4568
SNMP trap: No
Internal DN is out-of-range.
Action:
Severity: Info.
SCH4575
SNMP trap: No
Display on Manual Signaling package not equipped.

Action:
Severity: Info.
SCH4576
SNMP trap: No
Invalid response to AC2 prompt in LD 15; HLOC is prompted again.

Action: Enter numeric input between 100 and 9999.
Severity: Info.
SCH4577
SNMP trap: No
LSC should be between 100 and 9999.

Action:
Severity: Info.
SCH4578
SNMP trap: No
Four inputs are required for the Busy or OVBU prompts.

Action:
Severity: Info.
SCH4579
SNMP trap: No
Invalid input entered. Invalid Interflow treatment or Busy Tone treatment for
originating type. In X11 Release 17, BSY is not accepted for CO, FX trunks.
Action:
Severity: Info.
SCH4580
SNMP trap: No
Cannot change user mode to ISL while B-channels are still configured on
associated DCH loops.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1784 of 2360

SCH4581
Repeat NEW of an ESL TN table in LD 14. CHID is not assigned for ESL trunks
using NEW number only first CHID is accepted. Others must be added
individually.
Action:
Severity: Info.
SCH4597
SNMP trap: No
Template space for assigned authcode cannot be allocated.

Action:
Severity: Info.
SCH4598
SNMP trap: No
The assigned number entered is not within the valid range.

Action:
Severity: Info.
SCH4599
SNMP trap: No
The assigned authcode entered is invalid.

Action:
Severity: Info.
SCH4600
SNMP trap: No
The ICDR package is restricted.

Action:
Severity: Info.
SCH4601
SNMP trap: No
An ACD station is not allowed an ICDR COS.

Action:
Severity: Info.
SCH4602
SNMP trap: No
MCT package is not equipped.

Action:
Severity: Info.
SCH4603
SNMP trap: No
ACD stations are nor allowed to have MCT feature.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1785 of 2360

SCH4605
EHTA or EHTD not allowed with MNL COS.

Action:
Severity: Info.
SCH4606
SNMP trap: No
Hot Line package not equipped.

Action:
Severity: Info.
SCH4607
SNMP trap: No
If the station has EHTA COS, then HOT must be entered in response to the
FTR prompt.
Action:
Severity: Info.
SCH4608
SNMP trap: No
Hot Line keys disallowed if Hot Line package is not equipped.

Action:
Severity: Info.
SCH4609
SNMP trap: No
EHTA conflicts with LLC1, LLC2, and LLC3. Hot Line keys cannot be assigned
to telephones with LLC enabled.
Action:
Severity: Info.
SCH4630
SNMP trap: No
LLC COS cannot be assigned, LLC package not enabled.

Action:
Severity: Info.
SCH4631
SNMP trap: No
Invalid response to LLC prompt (YES or NO).

Action:
Severity: Info.
SCH4632
SNMP trap: No
Invalid threshold value for LLC level (0-100).

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1786 of 2360

SCH4635
Warning: Available UDS is less than 4KW.

Action:
Severity: Info.
SCH4636
SNMP trap: No
Input is not one of PRT, TTY, HDK, FDK.

Action:
Severity: Info.
SCH4640
SNMP trap: No
Billable limits must be within system maximum and minimum.

Action:
Severity: Info.
SCH4641
SNMP trap: No
Billable limits cannot be reduced below current TN to total.

Action:
Severity: Info.
SCH4642
SNMP trap: No
Number of TNs must be between system minimum and billable limits.

Action:
Severity: Info.
SCH4643
SNMP trap: No
Number of loops must be between zero and loop limit.

Action:
Severity: Info.
SCH4644
SNMP trap: No
Customer Night DN cannot be Pilot DN.

Action:
Severity: Info.
SCH4652
SNMP trap: No
ENP package is not equipped.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1787 of 2360

SCH4653
Display DN does not start with a pilot DN.

Action:
Severity: Info.
SCH4654
SNMP trap: No
DN must not exceed six characters.

Action:
Severity: Info.
SCH4655
SNMP trap: No
NSO number entered is not defined.

Action:
Severity: Info.
SCH4656
SNMP trap: No
PRXL must be equipped.

Action:
Severity: Info.
SCH4657
SNMP trap: No
SNMP trap: No
SNMP trap: No
NGA must be defined.

Action:
Severity: Info.
SCH4658
Out-of-range (0-7).
Action:
Severity: Info.
SCH4660
PRIM/SEC source has already been defined for the clock controller.
Action:
Severity: Info.
SCH4662
SNMP trap: No
Repeat count out-of-range for Signaling Category table; the table would be too
full if allowed to proceed.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1788 of 2360

SCH4664
Removing non-existing Limited Access Password (LAPW).

Action:
Severity: Info.
SCH4665
SNMP trap: No
Attempted loop move between GEC & NT loops.

Action:
Severity: Info.
SCH4667
SNMP trap: No
AFA Class of Service not allowed unless COS FNA.

Action:
Severity: Info.
SCH4668
SNMP trap: No
SARG period 1 start and stop times are undefined.

Action:
Severity: Info.
SCH4669
SNMP trap: No
Private line cannot be used with FTC.

Action:
Severity: Info.
SCH4670
SNMP trap: No
ABCD package is not equipped

Action:
Severity: Info.
SCH4671
SNMP trap: No
ABCD table does not exist

Action:
Severity: Info.
SCH4672
SNMP trap: No
ABCD table already exists

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1789 of 2360

SCH4673
Higher ABCD table number exists.

Action:
Severity: Info.
SCH4674
SNMP trap: No
Input must be 1, 2, 3 or {CR}.

Action:
Severity: Info.
SCH4677
SNMP trap: No
Undesired default function should be mapped to another existing signal.

Action:
Severity: Info.
SCH4678
SNMP trap: No
Cannot change ENA, END, LKA, LKD, UNA, UND, DSA, DSD, or invalid abcd
code for send signal.
Action:
Severity: Info.
SCH4679
SNMP trap: No
Receive and send signal inputs do not match.

Action:
Severity: Info.
SCH4680
SNMP trap: No
Already 16 LOG units are configured. No more new devices can be added.
Action:
Severity: Info.
SCH4681
SNMP trap: No
PVR or PVN cannot be assigned as primed DN.

Action:
Severity: Info.
SCH4684
SNMP trap: No

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1790 of 2360

SCH4685

Action:
Severity: Info.
SCH4687
SNMP trap: No
Option not defined for this feature.

Action:
Severity: Info.
SCH4688
SNMP trap: No
INST digits conflict with ATCD.

Action:
Severity: Info.
SCH4700
SNMP trap: No
FTC package is not equipped. SRC1-SRC8 not allowed.

Action:
Severity: Info.
SCH4701
SNMP trap: No
{CR} only allowed for print.

Action:
Severity: Info.
SCH4702
SNMP trap: No
Table 0 cannot be removed.

Action:
Severity: Info.
SCH4703
SNMP trap: No
Input must be between 256 and 1024.

Action:
Severity: Info.
SCH4705
SNMP trap: No
SNMP trap: No
No tone tables found.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1791 of 2360

SCH4706
Input must be 4 or 8.
Action:
Severity: Info.
SCH4707
SNMP trap: No
96 or 128 must be input.

Action:
Severity: Info.
SCH4708
SNMP trap: No
Input must be 50, 60, 70, or 100.

Action:
Severity: Info.
SCH4709
SNMP trap: No
SNMP trap: No

Action:
Severity: Info.
SCH4710
Duplicate key assigned to attendant console.

Action:
Severity: Info.
SCH4712
SNMP trap: No
Warning: MFC outgoing table will be cleared. Route members should not have
MFC Class of Service if there is no incoming MFC table.
Action:
Severity: Info.
SCH4713
SNMP trap: No
Warning: MFC incoming table will be cleared. Route members should not have
MFC Class of Service if there is no outgoing MFC table.
Action:
Severity: Info.
SCH4726
SNMP trap: No
If AUTO is set and TKTP is TIE, SIG cannot be ESN3.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1792 of 2360

SCH4727
Pointer for shown PRI loop is NIL.

Action:
Severity: Info.
SCH4728
SNMP trap: No
Minimum value must be specified when the NSF or IFC of the ISA is changed.
Action:
Severity: Info.
SCH4730
SNMP trap: No
Unable to allocate memory for new DCH.

Action:
Severity: Info.
SCH4731
SNMP trap: No
Unable to allocate memory to change DCH.

Action:
Severity: Info.
SCH4732
SNMP trap: No
Cannot remove the D-channel when B-channel is still defined for loops
associated with this D-channel.
Action:
Severity: Info.
SCH4733
SNMP trap: No
Unable to allocate memory for new backup DCH.

Action:
Severity: Info.
SCH4734
SNMP trap: No
Cannot out backup DCH while the backup D-channel loop (BCHL) still has B
channels configured.
Action:
Severity: Info.
SCH4735
SNMP trap: No
Cannot out backup DCH. There was a problem with memory allocation.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1793 of 2360

SCH4736
ISL trunks still exist. Cannot out DCH.

Action:
Severity: Info.
SCH4737
SNMP trap: No
A D-channel which has a backup DCH configured is not allowed to execute the
move command.
Action:
Severity: Info.
SCH4738
SNMP trap: No
Only DCH in PRA mode are allowed to be moved.

Action:
Severity: Info.
SCH4740
SNMP trap: No
All DCH and PRI loops must be disabled for the move.
Action:
Severity: Info.
SCH4741
SNMP trap: No
The IO card type is not allowed for the backup D-channel.

Action:
Severity: Info.
SCH4742
SNMP trap: No
Loop cannot be deleted when configured with DCH.

Action:
Severity: Info.
SCH4743
SNMP trap: No
Warning: Frame format should not be changed when the loop is associated
with a DCH link.
Action:
Severity: Info.
SCH4745
SNMP trap: No
Warning: Parameter should not be changed when the loop is configured with
a DCH.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1794 of 2360

SCH4746
Cannot select the loop for DCHL or BCHL because the D-channel (24 for PRI,
31 for PRI2) is set as a B or A/B channel.
Action:
Severity: Info.
SCH4747
SNMP trap: No
BCHI is defined as DCHI.

Action:
Severity: Info.
SCH4748
SNMP trap: No
Cannot remove undefined DCH channel (DCHI or BCHI).

Action:
Severity: Info.
SCH4750
SNMP trap: No
64K clear can be selected only when LCMT is B8S.

Action:
Severity: Info.
SCH4751
SNMP trap: No
DCHL must be defined for DCHI when USR=PRA/SHA.

Action: Start over to define DCHI. DCHL must not be removed while
corresponding DCHI exists; start over to remove DCHL by entering X at DCHI,
then on the same pass enter X at DCHL..
Severity: Info.
SCH4752
SNMP trap: No
Warning: IFC should not be changed when any of the channels of the
configured loops (DCHL, BCHL and/or PRIs) are configured.
Action:
Severity: Info.
SCH4753
SNMP trap: No
Loop configured as DCHL or BCHL.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1795 of 2360

SCH4756
Selected loop is not configured as a PRI or PRI2 loop.

Action:
Severity: Info.
SCH4757
SNMP trap: No
PRI sequence number is not available.

Action:
Severity: Info.
SCH4758
SNMP trap: No
Loop is already configured with a DCH link.

Action:
Severity: Info.
SCH4759
SNMP trap: No
DCHL must be defined for new link.

Action:
Severity: Info.
SCH4760
SNMP trap: No
DCHL, BCHL or PRI loop is not defined.

Action:
Severity: Info.
SCH4761
SNMP trap: No
Loop number not associated with DCHI number/BCHI number.

Action:
Severity: Info.
SCH4762
SNMP trap: No
Analog route cannot be PRA.

Action:
Severity: Info.
SCH4763
SNMP trap: No
Yellow alarm was changed to DG2 because the frame format was changed to
other than ESF.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1796 of 2360

SCH4765
Loop number must be given with the sequence number.

Action:
Severity: Info.
SCH4766
SNMP trap: No
Loop can be removed only when none of its channels are configured for
B-channel signaling.
Action:
Severity: Info.
SCH4767
SNMP trap: No
The loop number has already been used by this DCH.

Action:
Severity: Info.
SCH4769
SNMP trap: No
There is at least one ISDN route. PRA = NO is not allowed.

Action:
Severity: Info.
SCH4771
SNMP trap: No
Code value out-of-range (100-999).

Action:
Severity: Info.
SCH4772
SNMP trap: No
Customer need to be equipped with PRA (LD 15) to configure ISDN route.
Action:
Severity: Info.
SCH4773
SNMP trap: No
Cannot set ISDN to NO while ISAR = YES or B-Channels are configured for
the route.
Action:
Severity: Info.
SCH4774
SNMP trap: No
STEP to ISA route is not allowed.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1797 of 2360

SCH4775
Warning: IFC must be changed for service route in conjunction with ISA routes
and IFC for the DCH link.
Action: IFC must be changed for the DCH first and then changed for the ISA
routes which have channels from the PRI loops of the DCH. Finally, change the
IFC for the service routes.
Severity: Info.
SCH4776
SNMP trap: No
SNMP trap: No
SNMP trap: No
ISA route is not defined.

Action:
Severity: Info.
SCH4777
Route type is not ISA.

Action:
Severity: Info.
SCH4778
ISA route must be defined first.

Action:
Severity: Info.
SCH4779
SNMP trap: No
Warning: Must define LDN0: required for ISDN PRI DID service The length of
LDN0 determines the number of trailing digits translated as the dialed DN on
PRI DID routes.
Action:
Severity: Info.
SCH4780
SNMP trap: No
To change NSF, all routes associated with the ISA route must be service
changed to update the NSF parameters (i.e. MIN and MAX) associated with
them.
Action:
Severity: Info.
SCH4781
SNMP trap: No
Minimum number of calls must be specified.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1798 of 2360

SCH4782
Maximum number of calls must be specified.

Action:
Severity: Info.
SCH4783
SNMP trap: No
The minimum value is greater than the maximum value.

Action:
Severity: Info.
SCH4784
SNMP trap: No
SNMP trap: No
Expecting 3 digits.
Action:
Severity: Info.
SCH4785
ISA route has no trunks (channels).

Action:
Severity: Info.
SCH4786
SNMP trap: No
The sum of the MIN for all routes which access the ISA route exceed the
number of configured trunks for the ISA route. If outing ISA trunks, the service
route minimum/maximum values must be re-entered.
Action:
Severity: Info.
SCH4787
SNMP trap: No
DSI is not applicable for ISDN routes.

Action:
Severity: Info.
SCH4788
SNMP trap: No
PRI loop is not configured with D-channel (DCHI) to provide B-channels.

Action:
Severity: Info.
SCH4789
SNMP trap: No
ISA route may not be selected.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1799 of 2360

SCH4790
DTI loop channels cannot be configured for ISA routes or digital ISDN routes
with B-Channel signaling for the channels (trunks).
Action:
Severity: Info.
SCH4791
SNMP trap: No
D-CH master header part is NIL.

Action:
Severity: Info.
SCH4792
SNMP trap: No
IFC for DCH/PRA does not match IFC of the route.

Action:
Severity: Info.
SCH4793
SNMP trap: No
Selected Channel is configured for D-channel signaling.

Action:
Severity: Info.
SCH4794
SNMP trap: No
IFC for service route do not match IFC for ISA route.
Action:
Severity: Info.
SCH4795
SNMP trap: No
Trunk TYPE is not allowed with PRI loop.

Action:
Severity: Info.
SCH4797
SNMP trap: No
TDET cannot be defined in a superloop.

Action:
Severity: Info.
SCH4800
SNMP trap: No
Input source or destination shelf number is not defined in the NT8D shelf
configuration.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1800 of 2360

SCH4801
Invalid starting target unit (STUN) input.

Action:
Severity: Info.
SCH4802
SNMP trap: No
Source and destination card types are not the same.

Action:
Severity: Info.
SCH4803
SNMP trap: No
Cannot move or swap different source Controllers (NT8D01) to the same

destination Controller.
Action:
Severity: Info.
SCH4804
SNMP trap: No
Cannot move different source SD/DD/QD cards to the same destination

Controller (NT8D01) with the same starting target unit (STUN) more than
once.
Action:
Severity: Info.
SCH4805
SNMP trap: No
Cannot move or swap the same source segment more than once.
Action:
Severity: Info.
SCH4806
SNMP trap: No
Cannot move or swap different source segments to the same destination

segment.
Action:
Severity: Info.
SCH4808
SNMP trap: No
Too many cards are currently configured on the source or destination shelf.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1801 of 2360

SCH4809
Too many shelves are currently configured on the source or destination loop.
Action:
Severity: Info.
SCH4810
SNMP trap: No
Cannot move or swap shelf from SD/DD/QD to superloop shelf.

Action:
Severity: Info.
SCH4811
SNMP trap: No
Starting segment input does not belong to the destination superloop shelf.
Action:
Severity: Info.
SCH4812
SNMP trap: No
No non-service card is defined on the source or destination segment.

Action:
Severity: Info.
SCH4813
SNMP trap: No
Too many cards are configured on the source segment for a move or swap
operation.
Action:
Severity: Info.
SCH4814
SNMP trap: No
The input segment number does not belong to the given superloop shelf.
Action:
Severity: Info.
SCH4815
SNMP trap: No
Cannot move off-premise extension (OPX) data to Controller (NT8D01).

Action:
Severity: Info.
SCH4816
SNMP trap: No
Cannot move or swap SD/DD/QD loop data to superloop.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1802 of 2360

SCH4817
No shelf is defined for both superloops.

Action:
Severity: Info.
SCH4818
SNMP trap: No
No shelf is defined for destination superloop.

Action:
Severity: Info.
SCH4819
SNMP trap: No
No shelf is defined for source superloop.

Action:
Severity: Info.
SCH4820
SNMP trap: No
No shelf is defined for the source or destination superloop.

Action:
Severity: Info.
SCH4821
SNMP trap: No
Cannot move data from Digital Link Interface (DLI) loop to superloop.
Action:
Severity: Info.
SCH4823
SNMP trap: No
Source card is empty, nothing to move.

Action:
Severity: Info.
SCH4824
SNMP trap: No
Invalid shelf number for Network/DTR (NT8D18) loop.

Action:
Severity: Info.
SCH4825
SNMP trap: No
For Network/DTR (NT8D18 card) loop. Slot 15 is reserved for Digitone

Receiver
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1803 of 2360

SCH4826
Cannot move or swap data from superloop to SD/DD/4D loop.

Action:
Severity: Info.
SCH4827
SNMP trap: No
Cannot move or swap SD/DD/QD loop to superloop.

Action:
Severity: Info.
SCH4828
SNMP trap: No
Cannot move or swap card and shelf data of superloop to another superloop
in the same move/swap operation.
Action:
Severity: Info.
SCH4829
SNMP trap: No
Cannot move SD/DD/QD card data other than PBX and ISDLC to controller.
Action:
Severity: Info.
SCH4860
SNMP trap: No
The Announcement table cannot be changed, printed or removed if it is not

configured.
Severity: Info.
SCH4861
SNMP trap: No
AANN table already exists.

Severity: Info.
SCH4862
SNMP trap: No
AANN does not exist.

Severity: Info.
SCH4863
SNMP trap: No
The PSTN option is valid on MCDN trunk routes only.

Action: Check if this route is an ISDN route and IFC type is type os SL1.
Severity: Info.
SNMP trap: No
System Messages
Page 1804 of 2360

SCH4864
ATAN cannot be enabled when no Attendant Announcement profiles are

configured in OL 56.
Action: Load OVL 56 and configure AANN section.
Severity: Info.
SCH4865
SNMP trap: No
AANN Table is not configured or is out of range.

Action: Check range type and enter again.
Severity: Info.
SCH4866
SNMP trap: No
Call Answer Forced has been activated on this route.

Action:
Severity: Info.
SCH4867
SNMP trap: No
AANN profile cannot be changed when pkg is restricted.

Action:
Severity: Info.
SCH5001
SNMP trap: No
Must respond YES to NFCR prompt before responding YES to IDCA prompt.
Action:
Severity: Info.
SCH5002
SNMP trap: No
This feature is not applicable to New Meridian Modular Telephones.

Action:
Severity: Info.
SCH5003
SNMP trap: No
Message waiting key (MWK/XMWK/RMWK) requires Message Waiting

Allowed (MWA) Class of Service.
Action: Define CLS MWA before configuring MWK/XMWK
Severity: Info.
SCH5004
SNMP trap: No
Message Intercept (MIN) package not equipped.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1805 of 2360

SCH5005
Cannot OUT a Frequency Cadence (FCAD) entry.

Action:
Severity: Info.
SCH5006
SNMP trap: No
Cannot change an FCAD table without a Conference/TDS/MFS card

(NT8D17)
Action:
Severity: Info.
SCH5007
SNMP trap: No
FCAD table entry already exists.

Action:
Severity: Info.
SCH5008
SNMP trap: No
FCAD table entry has not yet been defined.

Action:
Severity: Info.
SCH5009
SNMP trap: No
{CR} is not allowed for new FCAD tables.

Action:
Severity: Info.
SCH5010
SNMP trap: No
A cycle defined to repeat was not defined as a cycle in the cadence field. No
changes were made to the FCAD entry as the result of this error.
Action:
Severity: Info.
SCH5011
SNMP trap: No
The number of Tone Codes must match the number of defined cycles in the
cadence field. No changes were made to the FCAD entry.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1806 of 2360

SCH5012
FCAD entries 1 to 15 are reserved for ring tones and can be changed only
though MCAD entries 1 to 15.
Action:
Severity: Info.
SCH5013
SNMP trap: No
ACD keys and CCSA Class of Service are incompatible. A set is not allowed
to have both.
Action:
Severity: Info.
SCH5014
SNMP trap: No
Your MCAD ON phases must be greater than 13, for the 128 ms ROM
configuration. The 96 ms ROM configuration must have a value greater than 9.
Action:
Severity: Info.
SCH5015
SNMP trap: No
The Network/DTR Card software not found on disk.

Action: Get the disk with the proper Network/DTR
Severity: Info.
SCH5016
SNMP trap: No
The Timed Forced Disconnect timer is not applicable to this route type.
Action:
Severity:
SCH5018
SNMP trap: No
Cannot move or swap data into TN 0 (loop, shelf, card and unit all equal to 0).
Action:
Severity: Info.
SCH5019
SNMP trap: No
Automatic Answerback (AAK) key or Automatic Answerback Allowed (AAA)

Class of Service can only be assigned to digital sets with Hands Free Allowed
(HFA) Class of Service. Hands Free Denied (HFD) Class of Service is not
allowed when AAA Class of Service or AAK key is defined.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1807 of 2360

SCH5020
EOD string does not match the length defined in STRL.

Action:
Severity: Info.
SCH5021
SNMP trap: No
Requires IPE package number 203.

Action: Configure IPE package 203.
Severity: Info.
SCH5022
SNMP trap: No
Maximum Peripheral Equipment density is not octal (8D).

Action:
Severity: Info.
SCH5023
SNMP trap: No
BOSS is not an acceptable response when set is already a Secretary set.

Action:
Severity: Info.
SCH5024
SNMP trap: No
SEC is not an acceptable response when set is already a BOSS set.

Action:
Severity: Info.
SCH5025
SNMP trap: No
Too many input fields in response to SFDN prompt.

Action:
Severity: Info.
SCH5026
SNMP trap: No
The Superloop RAN trunk support only Audichron machine types.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1808 of 2360

SCH5027
The AUTOVON feature, Station Loop Preemption (SLP) and Console

Presentation Groups (CPG) level services are mutually exclusive. LD93: CPG
is not allowed if any member of the group is an AUTOVON route D16: With
CPG enabled, AUTOVON routes cannot be configured. D10/11: Class of
Service PRMA, PHTA, PCWA are not allowed with CPG.
Action:
Severity: Info.
SCH5030
SNMP trap: No
DIG cannot be defined for this set. Set is already defined with AGTA Class of
Service or is configured as an ACD agent set.
Action:
Severity: Info.
SCH5031
SNMP trap: No
Enhanced Hotline Allowed (EHTA) cannot be defined for this set. Set is
already configured with AGTA Class of Service.
Action:
Severity: Info.
SCH5032
SNMP trap: No
CCSA cannot be defined for this set. Set is already configured with AGTA
Class of Service.
Action:
Severity: Info.
SCH5033
SNMP trap: No
AGTA Class of Service cannot be defined unless ACD package A is equipped.

Action:
Severity: Info.
SCH5034
SNMP trap: No
AGTA cannot be defined for this set. Set is already configured with DIG.
Action:
Severity: Info.
SCH5035
SNMP trap: No
AGTA cannot be defined for this set. Set is already configured with CCSA
Class of Service.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1809 of 2360

SCH5036
AGTA cannot be defined for this set. Set is already configured with EHTA
Class of Service.
Action:
Severity: Info.
SCH5037
SNMP trap: No
Define AGTA Class of Service to make set eligible for ACD

Action:
Severity: Info.
SNMP trap: No
SCH5038 {D-channel} {list of interface numbers} Set not defined for ACD.
Action:
Severity: Info.
SCH5039
SNMP trap: No
Already configured with AGTA service. Set can only be defined as a single
appearance DN.
Action:
Severity: Info.
SCH5040
SNMP trap: No
Already configured as a multiple appearance DN; set cannot have AGTA

defined
Action:
Severity: Info.
SCH5041
SNMP trap: No
The ACD Agent set cannot be changed to an ACD Supervisor set.

Action: To change an ACD Agent set into an ACD Supervisor set:
1. Remove the supervisor reference for that
set.
2. Remove the SPID for that Agent.
3. OUT the corresponding AGT key on the Supervisor's set.
Severity: Info.
SCH5042
SNMP trap: No
The ISDN Signaling Link can only be configured with ISA or TIE routes.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1810 of 2360

SCH5043
You are not allowed to set up a QTHM for an Inter Attendant call.
Action:
Severity: Info.
SCH5044
SNMP trap: No
Action: Use COPY command in LD 10 to define more than one 500/2500 set
as an ACD station.
Action:
Severity: Info.
SCH5045
SNMP trap: No
500/2500 sets cannot be used as Virtual Agents.

Action:
Severity: Info.
SCH5046
SNMP trap: No
The In-Band Automatic Number Identification (IANI) route needs to be an

auto-terminating route.
Action:
Severity: Info.
SCH5047
SNMP trap: No
A route cannot be defined as both IANI and DNIS.

Action:
Severity: Info.
SCH5048
SNMP trap: No
This ISDN route cannot be configured for In-Band ANI.

Action:
Severity: Info.
SCH5049
SNMP trap: No
An In-Band ANI route cannot support digit insertion.

Action:
Severity: Info.
SCH5051
SNMP trap: No
In-Band ANI routes are STD routes only.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1811 of 2360

SCH5052
POVR package must be equipped.

Action:
Severity: Info.
SCH5053
SNMP trap: No
CPTA must have WTA (Warning Tone Allowed) Class of Service.

Action:
Severity: Info.
SCH5055
SNMP trap: No
Set already configured for AGTA service; cannot be configured for XHA Class
of Service.
Action:
Severity: Info.
SCH5056
SNMP trap: No
Set already configured for AGTA service; cannot be defined with PRMA.
Action:
Severity: Info.
SCH5057
SNMP trap: No
Set already configured with XHA service; cannot be defined with AGTA.
Action:
Severity: Info.
SCH5058
SNMP trap: No
Set already configured with PRMA service; cannot be defined with AGTA.
Action:
Severity: Info.
SCH5060
SNMP trap: No
An analog route is required.

Action:
Severity: Info.
SCH5061
SNMP trap: No
Warning: The ITG Option was not turned on. It is turned on here.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1812 of 2360

SCH5062
Stepping to an ISA SERVICE route is not allowed.

Action:
Severity: Info.
SCH5063
SNMP trap: No
The ISAR option cannot be changed to YES, because the trunk has dedicated
routes.
Action: Remove all dedicated routes from that trunk.
Severity: Info.
SCH5064
SNMP trap: No
Dedicated trunks cannot be assigned to an ISA SERVICE route unless the

ISAR option is turned off first.
Action:
Severity: Info.
SCH5065
SNMP trap: No
SCL was not the response to the TYPE prompt when REQ was COMP. Only
Speed Call lists are estimated. Use SCL for both regular and system speed
call.
Action:
Severity: Info.
SCH5066
SNMP trap: No
Disk record availability estimation cannot be performed.

Action: Ensure that a data dump has been executed
Severity: Info.
SCH5067
SNMP trap: No
CDN cannot be allowed to have agents.

Action:
Severity: Info.
SCH5068
SNMP trap: No
500/2500 PBX sets used as ACD sets can only have single appearance
regular DN.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1813 of 2360

SCH5069
The number of TNs in the system is greater than the limit. You may need new
disks with new TN limits.
Action:
Severity: Info.
SCH5070
SNMP trap: No
The number of ACD Agents/Supervisors in the system is greater than the limit.
You may need new disks with new ACD Agent/Supervisor limits.
Action:
Severity: Info.
SCH5071
SNMP trap: No
The number of ACD DNs and CDNs in the system is greater than the limit. You
may need new disks with new ACD DN limits.
Action:
Severity: Info.
SCH5072
SNMP trap: No
The number of AST sets in the system is greater than the limit.
Action: To expand, you will need to order new disks with new AST set limits.
Severity: Info.
SCH5073
SNMP trap: No
CDN cannot be defined for NSV key.

Action:
Severity: Info.
SCH5074
SNMP trap: No
BIMP and TIMP are mismatched. See prompt TIMP in LD 14 for allowed
combinations of BIMP/TIMP.
Action:
Severity: Info.
SCH5075
SNMP trap: No
Service not implemented in this IFC.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1814 of 2360

SCH5076
Warning: Templates are at the limit.

Action: Contact the service representative before proceeding.
Severity: Info.
SCH5077
SNMP trap: No
Out WATS band number is invalid (only 0 - 9 are valid).

Action:
Severity: Info.
SCH5078
SNMP trap: No
Key 0 cannot be configured as a Wake Up key.

Action:
Severity: Info.
SCH5079
SNMP trap: No
Invalid DN type on key 0 for a Wake Up key. Valid DN types include MCR,
SCR, MCN, SCN, PVR, and PVN.
Action:
Severity: Info.
SCH5080
SNMP trap: No
A Wake Up key cannot be configured on a data set. CLS must be for a VCE
data terminal.
Action:
Severity: Info.
SCH5081
SNMP trap: No
CLS must be CCSA to configure a Wake Up key.

Action:
Severity: Info.
SNMP trap: No
SCH5082 DO NOT PRINT A Wake-Up Key is configured, so the class cannot be set to CCSD and
AWCD.
Action: Remove the WUK Key or set class to CCSA or set class to CCSA or
AWCA.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1815 of 2360

SCH5083
Input out-of-range 1 - 3 for TAWU (the number of tries for an unanswered

Wake Up call.
Action:
Severity: Info.
SCH5084
SNMP trap: No
Peripheral equipment exists on the loop.

Action:
Severity: Info.
SCH5086
SNMP trap: No
The responses EXR0/EXR1/EXR2/EXR3/EXR4 are not allowed if the

Executive Distinctive Ringing Package #185 is not equipped. CLS is
reprompted. The response DRDA/DRDD for MMT sets are not allowed if the
Executive Distinctive Ringing Package #185 is not equipped. CLS is
reprompted.
Action: Equip Package 185 and re-load if Executive Distinctive Ringing or
Distinctive Ringing by DN is required.
Severity: Info.
SCH5087
SNMP trap: No
Do not use MOV or SWP commands when PRI/PRI2 loops are configured with
backup DCH.
Action:
Severity: Info.
SCH5088
SNMP trap: No
SDAL option in LD 15 is only allowed when PRETRNS and SUPP packages

are equipped.
Action: Set up SDAC data in LD 18.
Severity: Info.
SCH5091
SNMP trap: No
CLS ECA is only used on 4-wire E & M trunks.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1816 of 2360

SCH5092
Flexible attendant Call Waiting Threshold (FCWT) values on the tenant level
are set equal to the customer level values.
Action:
Severity: Info.
SCH5093
SNMP trap: No
This trunk does not have MFC Class of Service (LD 16).
Action:
Severity: Info.
SCH5094
SNMP trap: No
The outgoing table's signaling type does not match the incoming signal l type
(LD 16).
Action:
Severity: Info.
SCH5095
SNMP trap: No
L1 levels 1 through 6 do not exist (LD 94).

Action:
Severity: Info.
SCH5096
SNMP trap: No
You cannot remove the L1 levels 1, 2, or 3 (LD 94).

Action:
Severity: Info.
SCH5097
SNMP trap: No
L1 levels 4, 5, and 6 have been removed (LD 94).

Action:
Severity: Info.
SCH5098
SNMP trap: No
You are trying to use an invalid L1 signaling level (LD 94).

Action:
Severity: Info.
SCH5099
SNMP trap: No
You cannot do that with the L1 package because it is restricted (LD 94).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1817 of 2360

SCH5100
You cannot allocate PDS for an SS table (LD 94).

Action:
Severity: Info.
SCH5101
SNMP trap: No
L1 levels 1 and 2 must be defined in order to create an L1 table (LD 94).

Action:
Severity: Info.
SCH5102
SNMP trap: No
L1 levels 4, 5, and 6 must be defined (LD 94).

Action:
Severity: Info.
SCH5103
SNMP trap: No
Conflicting table types encountered (LD 94).

Action:
Severity: Info.
SCH5104
SNMP trap: No
That input (CNA, CND) is ignored because it does not match the CCNI in the
L1 route block (LD 14).
Action:
Severity: Info.
SCH5105
SNMP trap: No
Removing the MGC Class of Service also removes the L1 CNI option for this
trunk (LD 14).
Action:
Severity: Info.
SCH5106
SNMP trap: No
There is no unprotected memory available for changing the UTRKBLK for

CCNI.
Action:
Severity: Info.
SCH5113
SNMP trap: No
Language number entered is out-of-range (0) - 5.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1818 of 2360

SCH5114
Input must be "256" or "384."

Action:
Severity: Info.
SCH5115
SNMP trap: No
Force Disconnect has failed.

Severity: Info.
SCH5116
SNMP trap: No
Remove Wake Up key before changing to a data set.

Action:
Severity: Info.
SCH5117
SNMP trap: No
DRPA/DRPD can only be configured on 2.0 Mb/s DID if SUPP and DTI2 are
enabled.
Action:
Severity: Info.
SCH5118
SNMP trap: No
The Virtual Network Services (VNS) package is not equipped.

Action:
Severity: Info.
SCH5120
SNMP trap: No
That VNS data block does not exist.

Action:
Severity: Info.
SCH5122
SNMP trap: No
That DN is out-of-range.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1819 of 2360

SCH5123 c rl rli
That D-channel is already being used by the previous customer in Virtual

Network Services. Where:
c = Customer number
rl = Route List
rli = Route List index
Action:
Severity: Info.
SCH5125
SNMP trap: No
The customer has no D-channel IDs for Virtual Network Services (VNS).
Action:
Severity: Info.
SCH5127
SNMP trap: No
You are not allowed to put data TNs on a Voice Only ISDLC card.
Action:
Severity: Info.
SCH5128
SNMP trap: No
You are attempting to move a pair of TNs on a Voice Only ISDLC card.
Action:
Severity: Info.
SCH5129
SNMP trap: No
You are attempting to move a pair of TNs on a Voice Only ISDLC card.
Action:
Severity: Info.
SCH5130
SNMP trap: No
The customer number for that Data TN is not the same as the customer
number for the Voice TN.
Action:
Severity: Info.
SCH5131
SNMP trap: No
Entering the {CR} is not allowed in response to the PRT or TASK prompts.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1820 of 2360

SCH5132
The Maintenance threshold must be greater than or equal to the

Out-of-Service threshold.
Action:
Severity: Info.
SCH5133
SNMP trap: No
The Maintenance threshold must be less than or equal to the Out-of-Service

threshold.
Action:
Severity: Info.
SCH5134
SNMP trap: No
RPA package 187 is not equipped.

Action:
Severity: Info.
SCH5135
SNMP trap: No
Invalid input; RPCD/RPS/RPAX/TBL expected.

Action:
Severity: Info.
SCH5136
SNMP trap: No
Cannot end input with space.

Action:
Severity: Info.
SCH5137
SNMP trap: No
TBL only valid with command CHG/PRT.

Action:
Severity: Info.
SCH5138
SNMP trap: No
RPCD only valid with command NEW/CHG/PRT.

Action:
Severity: Info.
SCH5139
SNMP trap: No
No RPA data exists for this customer.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1821 of 2360

SCH5140
This system number is used for PSA code(s).

Action:
Severity: Info.
SCH5141
SNMP trap: No
RPCD data already exists.

Action:
Severity: Info.
SCH5142
SNMP trap: No
SNMP trap: No
SNMP trap: No
No RPCD data exists.

Action:
Severity: Info.
SCH5143
No DN-PSA data exists.

Action:
Severity: Info.
SCH5145
System number out-of-range (0-15).

Action:
Severity: Info.
SCH5146
SNMP trap: No
RPS data already exists.

Action:
Severity: Info.
SCH5147
SNMP trap: No
SNMP trap: No
No RPS data exists.

Action:
Severity: Info.
SCH5148
CR only valid for command PRT with RPS/RPAX/TBL.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1822 of 2360

SCH5149
Invalid input, SPCH, DIAL, or NONE expected.

Action:
Severity: Info.
SCH5150
SNMP trap: No
Cannot change to single if more than system 0 exists.

Action:
Severity: Info.
SCH5151
SNMP trap: No
Invalid input; TAB,TWO,THR, FOR, or NO expected.

Action:
Severity: Info.
SCH5152
SNMP trap: No
Warning: no RPS data found.

Action:
Severity: Info.
SCH5153
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Action:
Severity: Info.
SCH5154
Action:
Severity: Info.
SCH5155
Action:
Severity: Info.
SCH5156
Out-of-range (1-7).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1823 of 2360

SCH5157
Cannot change PSAL when DN-PSA tree exists.

Action:
Severity: Info.
SCH5158
SNMP trap: No
{CR} only valid for CHG command.

Action:
Severity: Info.
SCH5159
SNMP trap: No
SNMP trap: No
SNMP trap: No
Action:
Severity: Info.
SCH5160
Action:
Severity: Info.
SCH5161
Warning: no PSA defined for this system.

Action:
Severity: Info.
SCH5162
SNMP trap: No
SNMP trap: No
Not an FFC DN.

Action:
Severity: Info.
SCH5163
All digits in the DN are not used.

Action:
Severity: Info.
SCH5164
SNMP trap: No
SNMP trap: No
Not an RPAX FFC.

Action:
Severity: Info.
System Messages
Page 1824 of 2360

SCH5165
No RPA data for this FFC.

Action:
Severity: Info.
SCH5166
SNMP trap: No
RPA data already exists.

Action:
Severity: Info.
SCH5167
SNMP trap: No
Out-of-range (0-127/511).
Action:
Severity: Info.
SCH5168
SNMP trap: No
Non-existing route number.

Action:
Severity: Info.
SCH5169
SNMP trap: No
Route not set up for RPA.

Action:
Severity: Info.
SCH5170
SNMP trap: No
Route not set up as RAN.

Action:
Severity: Info.
SCH5171
SNMP trap: No
Invalid input; MANU or AUTO expected.

Action:
Severity: Info.
SCH5172
SNMP trap: No
SNMP trap: No
Out-of-range (0-9).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1825 of 2360

SCH5173
Out-of-range (0-7).
Action:
Severity: Info.
SCH5174
SNMP trap: No
Invalid input; NONE, SPCH, or RNGB expected.

Action:
Severity: Info.
SCH5175
SNMP trap: No
Invalid input; BOTH/INT expected.

Action:
Severity: Info.
SCH5176
SNMP trap: No
Only four characters allowed as RPAX FFC replacement.

Action:
Severity: Info.
SCH5177
SNMP trap: No
Invalid characters, A-Z or 1-9 expected.

Action:
Severity: Info.
SCH5178
SNMP trap: No
Too many digits in PSA code.

Action:
Severity: Info.
SCH5179
SNMP trap: No
No PSA code has been entered.

Action:
Severity: Info.
SCH5180
SNMP trap: No
Too few digits have been entered for the PSA code.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1826 of 2360

SCH5181
The DN does not exist in the DN-PSA tree.

Action:
Severity: Info.
SCH5182
SNMP trap: No
Invalid input; DNP, UPS, or NPS expected.

Action:
Severity: Info.
SCH5183
SNMP trap: No
Second DN has to be larger than the first DN.

Action:
Severity: Info.
SCH5184
SNMP trap: No
RPS block does not exist.

Action:
Severity: Info.
SCH5185
SNMP trap: No
Warning: no customer with RPCD data.

Action:
Severity: Info.
SCH5186
SNMP trap: No
Warning: no customer with RPS data.

Action:
Severity: Info.
SCH5187
SNMP trap: No
Warning: no RPAX FFC found.

Action:
Severity: Info.
SCH5188
SNMP trap: No
Warning: no RPAX data found.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1827 of 2360

SCH5189
Warning: no customer with DN-PSA tree.

Action:
Severity: Info.
SCH5190
SNMP trap: No
Warning: no system number found.

Action:
Severity: Info.
SCH5191
SNMP trap: No
Warning: the specified DN was not found.

Action:
Severity: Info.
SCH5192
SNMP trap: No
Warning: no DN found for this system.

Action:
Severity: Info.
SCH5193
SNMP trap: No
Customer not set up to use DN-PSA tree.

Action:
Severity: Info.
SCH5194
SNMP trap: No
No FFC tree for this customer.

Action:
Severity: Info.
SCH5195
SNMP trap: No
Leading space is not allowed.

Action:
Severity: Info.
SCH5196
SNMP trap: No
Corruption in the FFC/DN-PSA tree.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1828 of 2360

SCH5197
Not allowed to run LD 58 as midnight routine.

Action:
Severity: Info.
SCH5198
SNMP trap: No
This system number is used for RPAX FFC(s).

Action:
Severity: Info.
SCH5199
SNMP trap: No
An invalid internal DN has been entered for the CFW key. The entered DN is
either a normal DN, or FFC+DN. The validation is done for both CFXD and
CFXA classes of service.
Action:
Severity: Info.
SCH5205
SNMP trap: No
You are trying to include an undefined KLS in the Ringing Change KLS range.
Action:
Severity: Info.
SCH5207
SNMP trap: No
IAMA and IRGA Class of Service cannot coexist.

Action:
Severity: Info.
SCH5208
SNMP trap: No
The COPY command is not allowed for IAMA class telephone sets.
Action:
Severity: Info.
SCH5209
SNMP trap: No
The OUT command is not allowed when IRGA or IAMA Class of Service is
defined.
Action:
Severity: Info.
SCH5210
SNMP trap: No
Require EES package 10 to configure a key on an Attendant Console.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1829 of 2360

SCH5211
Cannot disable AWU feature when RANF trunks are still defined.
Action: Remove trunks and try again.
Severity: Info.
SCH5212
SNMP trap: No
Cannot disable AWU feature when RAN1 trunks are still defined.
Severity: Info.
SCH5213
SNMP trap: No
Cannot disable AWU feature when RAN2 trunks are still defined.
Severity: Info.
SCH5218
SNMP trap: No
The On Hold On Loudspeaker (OHOL) package 196 is not equipped.

Action:
Severity: Info.
SCH5219
SNMP trap: No
The DN assigned here must be an OHOL unit.

Action:
Severity: Info.
SCH5220
SNMP trap: No
OHOL DN can only have one 2/500 set appearance in DN group.

Action:
Severity: Info.
SCH5221
SNMP trap: No
Set with CLS = SPKA must enter valid Conference loop number on prompt
DCLP.
Action:
Severity: Info.
SCH5222
SNMP trap: No
ADL/CFW exceeds the maximum length of the template.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1830 of 2360

SCH5223
Ringing Change and ACD are not allowed on the same set.
Action:
Severity: Info.
SCH5224
SNMP trap: No
Cannot move or swap 0L1_loop equipment to RPE2_remote_loop.

Action:
Severity: Info.
SCH5225
SNMP trap: No
CDN cannot be defined for ENI key.

Action:
Severity: Info.
SCH5226
SNMP trap: No
RPE2 loop must be disabled.

Action:
Severity: Info.
SCH5227
SNMP trap: No
Unit types R232 and R422 are only allowed on Superloops.

Action: Define R232 and R422 on a Superloop.
Severity: Info.
SCH5228
SNMP trap: No
Data port number is out-of-range.

Action: Define R232 and R422 units as 0 - 5.
Severity: Info.
SCH5229
SNMP trap: No
Invalid feature key assignment.

Action: Refer to key definitions for LD 11.
Severity: Info.
SCH5230
SNMP trap: No
Data port interface mode does not match the database configuration.
Action: Check data port jumper selection against the data base configuration.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1831 of 2360

SCH5231
Invalid input for this operational parameter. Corrective action depends on the
operation attempted.: AUTB, DEM, DLNG, KBD, WIRE or PBDO.
Action:
Severity: Info.
SCH5232
SNMP trap: No
Key 7 is reserved for MSB feature. PBDO feature is currently enabled.

Action:
Severity: Info.
SCH5233
SNMP trap: No
Call Pickup not allowed on Data Access Card (DCA) ports.

Action:
Severity: Info.
SCH5235
SNMP trap: No
Cannot move Superloop data on a customer basis.

Action:
Severity: Info.
SCH5236
SNMP trap: No
Not allowed to move non-Data Access Card units to a Data Access Card.
Action:
Severity: Info.
SCH5237
SNMP trap: No
The characters entered for the ID prompt exceed the range allowed.
Action: Limit the string to no more than 16 characters.
Severity: Info.
SCH5238
SNMP trap: No
Group list does not exist.

Action:
Severity: Info.
SCH5239
SNMP trap: No
Group list already assigned.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1832 of 2360

SCH5240
Group Call DN in FFC must be removed first.

Action:
Severity: Info.
SCH5242
SNMP trap: No
In the ICP block, you are trying to remove a TN that does not exist.
Action:
Severity: Info.
SCH5243
SNMP trap: No
Setting the increment value to zero does not change the threshold counter.
Your system operation may not tolerate this event.
Action: It is recommended that the increment value be set to a value other than
zero.
Severity: Info.
SCH5244
SNMP trap: No
Setting the decrement value to zero does not change the threshold counter.
Your system operation may not tolerate this event.
Action: It is recommended that the decrement value other than zero.
Severity: Info.
SCH5245
SNMP trap: No
Warning: Only the spare loop is left in RPE2 group.

Action:
Severity: Info.
SCH5246
SNMP trap: No
Hospitality package not equipped.

Action:
Severity: Info.
SCH5247
SNMP trap: No
Class of Service MRA required for HSPA.

Action:
Severity: Info.
SCH5248
SNMP trap: No
Class of Service CCSA required for HSPA.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1833 of 2360

SCH5249
Class of Service HSPA and XFA are exclusive.

Action:
Severity: Info.
SCH5250
SNMP trap: No
Class of Service HSPA and Conference are exclusive.

Action:
Severity: Info.
SCH5251
SNMP trap: No
Class of Service HSPA and multiple appearance directory numbers are

exclusive.
Action:
Severity: Info.
SCH5252
SNMP trap: No
Hospitality room set data cannot be modified (or removed) while the room is
occupied.
Action:
Severity: Info.
SCH5253
SNMP trap: No
CLS AOS/DOS/OUSA/OUSD only available to CLS SPV.

Action:
Severity: Info.
SCH5254
SNMP trap: No
Hospitality primary DN key must be SCR or SCN.

Action:
Severity: Info.
SCH5255
SNMP trap: No
DTN is required for Fax Server operation.

Action:
Severity: Info.
SCH5256
SNMP trap: No
CAW,FBA, and FNA are not compatible with Fax Server operation.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1834 of 2360

SCH5257
CFW is not compatible with Fax Server operation.

Action:
Severity: Info.
SCH5260
SNMP trap: No
Length of Hospitality Authcode is limited to 4 digits.

Action:
Severity: Info.
SCH5261
SNMP trap: No
DID-DN conflicts with existing one in Hospitality tree.

Action:
Severity: Info.
SCH5262
SNMP trap: No
Another Hospitality tree already exists for this customer.

Action:
Severity: Info.
SCH5263
SNMP trap: No
Data modification is denied while patient is in the room.

Action:
Severity: Info.
SCH5264
SNMP trap: No
MOV command is denied for a Hospitality tree.

Action:
Severity: Info.
SCH5265
SNMP trap: No
All tree branches must be released before an OUT or RPL request can be
processed for an Hospitality tree.
Action:
Severity: Info.
SCH5266
SNMP trap: No
Hospitality Authcode must be defined in Authcode table first.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1835 of 2360

SCH5267
Tree table 0 is not allowed for a Hospitality tree.

Action:
Severity: Info.
SCH5268
SNMP trap: No
The International Supplementary Features (SUPP) package 131 is not

equipped.
Action:
Severity: Info.
SCH5269
SNMP trap: No
The UK package 190 is not equipped.

Action:
Severity: Info.
SCH5270
SNMP trap: No
That is an invalid trunk type for XCOT, XDID, or XFEM. Valid trunk types are
listed here: XCOT = CO trunks; XDID = DID trunks; XFEM = MUS, PAG, RAN,
and TIE trunks.
Action:
Severity: Info.
SCH5272
SNMP trap: No
XUTJ does not support 900 or 1200 Ohm termination.

Action:
Severity: Info.
SCH5273
SNMP trap: No
Input out-of-range for make-break ratio (50 - 70).

Action:
Severity: Info.
SCH5274
SNMP trap: No
Both ND1 and ND2 were included in the capability list for the remote switch.
ND1 and ND2 specify the protocol to be used for Network Name Delivery. Only
one protocol can be used per interface.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1836 of 2360

SCH5276
RANF, RAN1, RAN2, LA11 through LA52 cannot be changed during an AWU
call. Updates not saved.
Action: Try again after AWU call is finished.
Severity: Info.
SCH5280
SNMP trap: No
In procedure init_levelblk or traverse_idctree of sccndse2, value of global

variable idc_cur_level is invalid. IDC_cur_level must be greater than -1 and
less than .idcmaxsize (4 or 7).
Action:
Severity: Info.
SCH5283
SNMP trap: No
In procedure in_dcno of sccndse3, idc_no_trees: cdataptr[sccustno] = nil. Use

LD 15 and specify the maximum number of idc tree in the customer data block
(CDB) in order to create any idc tree in this load.
Action:
Severity: Info.
SCH5285
SNMP trap: No
In procedure in_dcno of sccndse3, input for idc tree number is out-of-range.

Action:
Severity: Info.
SCH5286
SNMP trap: No
SNMP trap: No
Invalid DN type.
Action:
Severity: Info.
SCH5288
In procedure traverse_idctree of sccndse2, a CPND name for idc is found, and

therefore the CPND data block cannot be removed.
Action:
Severity: Info.
SCH5289
SNMP trap: No
In procedure in_dcno of sccndse3, the current idc tree is not yet created.
Action: Create an idc tree in LD 49 (scfcr).
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1837 of 2360

SCH5290
In procedure a_or_save_1stdgt, L_or_save_dn, check_idc_type, in_dc_idc,

range_or_done, or save_dn of sccnd3, invalid or undefined idc input is
detected.
Action:
Severity: Info.
SCH5291
SNMP trap: No
In procedure intype of scfcrse2, command rls (release) and rpl (replace) are
blocked for idc type.
Action:
Severity: Info.
SCH5292
SNMP trap: No
Type CDN cannot be selected without the EAR package being equipped.
Action:
Severity: Info.
SCH5293
SNMP trap: No
CDN must exist for CHG, OUT or PRT command.

Action:
Severity: Info.
SCH5294
SNMP trap: No
Unable to find a CDN block.

Action:
Severity: Info.
SCH5295
SNMP trap: No
SNMP trap: No
CDN already exists.

Action:
Severity: Info.
SCH5296
ACD data block for CDN must exist. Data corrupted. Do a sysload.
Action:
Severity: Info.
SCH5297
SNMP trap: No
Specify an ACD-DN for the default DN of CDN.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1838 of 2360

SCH5298
CDN conflict.
Action:
Severity: Info.
SCH5299
SNMP trap: No
A valid local ACD DN must exist for the default ACD DN of the CDN.
Action:
Severity: Info.
SCH5300
SNMP trap: No
Invalid DN type. Must specify an ACD-DN for the default DN of the CDN.
Action:
Severity: Info.
SCH5301
SNMP trap: No
TSFT value is out-of-range (0-510).

Action:
Severity: Info.
SCH5302
SNMP trap: No
This ACD-DN cannot be deleted because it is used as the default DN for some
CDNs.
Action:
Severity: Info.
SCH5303
SNMP trap: No
Invalid DN type. Must specify a CDN for the CDN type and an ACD-DN for the
ACD or NACD type.
Action:
Severity: Info.
SCH5304
SNMP trap: No
Cannot remove a CDN with calls still in queue.

Action:
Severity: Info.
SCH5305
SNMP trap: No
Cannot define a CDN as OVDN.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1839 of 2360

SCH5306
Cannot have a Target DN as CDN.

Action:
Severity: Info.
SCH5307
SNMP trap: No
Cannot remove a CDN if a supervisor has a DWC key defined for the CDN.
Action:
Severity: Info.
SCH5313
SNMP trap: No
Warning: CNTA CLS is only allowed for ACD sets with DN on key 0. CNTD is
used.
Action:
Severity: Info.
SCH5314
SNMP trap: No
A six-digit or 10-digit level screening data is required for a newly defined NPA
or NXX, respectively.
Action:
Severity: Info.
SCH5316
SNMP trap: No
The peripheral buffer card is bad, but there is no active call, so the trunk is
allowed to be removed.
Action: Replace the peripheral buffer card.
Severity: Info.
SCH5317
SNMP trap: No
Outing the DCHI used for DPNSS is not allowed until the DDSL block is
removed first.
Action:
Severity: Info.
SCH5318
SNMP trap: No
MBG out-of-range 0-65535

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1840 of 2360

SCH5319
MBG1 is reserved for Public Network

Action:
Severity: Info.
SCH5320
SNMP trap: No
BSGC out-of-range 0-65535

Action:
Severity: Info.
SCH5322
SNMP trap: No
MBGS out-of-range 0-65535

Action:
Severity: Info.
SCH5323
SNMP trap: No
SNMP trap: No
NTBL out-of-range 0-63

Action:
Severity: Info.
SCH5324
The addition of the list being created would overflow/fill the estimated
remaining disk space. The list is not stored.
Action: Create a smaller (DN or length) list, or delete other PDS equipment, or
data dump to reduce the number of records estimated.
Severity: Info.
SCH5326
SNMP trap: No
1.5 Mb/s DTI/PRI pad category table does not exist.

Action: Create a pad category table using LD 73.
Severity: Info.
SCH5327
SNMP trap: No
PRI2 pad category tables cannot be used with DTI2 trunks.

Action: Enter a DTI2 pad category table.
Severity: Info.
SCH5328
SNMP trap: No
Port classification PRI is only allowed for 1.5 Mb/s PRI routes.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1841 of 2360

SCH5329
International 1.5/2.0 Mb/s Gateway (GPRI) package 167 is restricted.

Action:
Severity: Info.
SCH5330
SNMP trap: No
Code value entered is not allowed for DTI2 trunks. Valid values are:
0,1,2,3,4,5,6,8,10,15,16,17,18,20,25, and 26.
Action:
Severity: Info.
SCH5331
SNMP trap: No
The pad category table specified cannot be used with PRI2 trunks because
DTI2 trunks are currently using this pad category table.
Action:
Severity: Info.
SCH5332
SNMP trap: No
Valid DN required for AUDN.

Action:
Severity: Info.
SCH5334
SNMP trap: No
Not allowed to configure different member of the same group or same member
of the same group on different keys for same TN.
Action:
Severity: Info.
SCH5336
SNMP trap: No
Invalid input for the trunk model option.

Action:
Severity: Info.
SCH5337
SNMP trap: No
Invalid input character for selecting the trunk model option. Not allowed with
autodial DN.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1842 of 2360

SCH5338
Null input is not allowed for MODL prompt.

Action:
Severity: Info.
SCH5339
SNMP trap: No
Model number is out-of-range (1-127).

Action:
Severity: Info.
SCH5340
SNMP trap: No
Space is not allowed after input is entered.

Action:
Severity: Info.
SCH5341
SNMP trap: No
Space is not allowed before input.

Action:
Severity: Info.
SCH5342
SNMP trap: No
The entered number has been used to define a model trunk.

Action:
Severity: Info.
SCH5345
SNMP trap: No
No default value for new device.

Action:
Severity: Info.
SCH5347
SNMP trap: No
SNMP trap: No
Baud rate invalid.

Action:
Severity: Info.
SCH5348
Analog Private Network Switching System (APNSS) channel ID has reached

its limit.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1843 of 2360

SCH5349
Call forward features are not compatible with FAXS feature. FTR CFW has
been removed and/or CLS FNA, FBA, CWA, CFTA, CFXA have been set to
FND, FBD, CWD, CFTD, CFXD.
Action:
Severity: Info.
SCH5350
SNMP trap: No
FAXS package is not equipped.

Action:
Severity: Info.
SCH5351
SNMP trap: No
Cannot remove a CDN when it has default calls in its default ACD-DN.
Action:
Severity: Info.
SCH5352
SNMP trap: No
Model ACD sets cannot have a POS ID assigned to a key.

Action:
Severity: Info.
SCH5353
SNMP trap: No
Model sets cannot have a DN assigned to a key.

Action:
Severity: Info.
SCH5354
SNMP trap: No
Model sets cannot be defined with the AINS package unequipped.

Action:
Severity: Info.
SCH5355
SNMP trap: No
Models cannot be defined for this type.

Action:
Severity: Info.
SCH5356
SNMP trap: No
Model sets cannot be moved or copied.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1844 of 2360

SCH5357
Model number is out-of-range.

Action:
Severity: Info.
SCH5358
SNMP trap: No
Model set already exists.

Action:
Severity: Info.
SCH5359
SNMP trap: No
Model set does not exist.

Action:
Severity: Info.
SCH5360
SNMP trap: No
First Number DN conflicts with an existing DN.

Action:
Severity: Info.
SCH5361
SNMP trap: No
Too many digits in the First Number DN.

Action:
Severity: Info.
SCH5362
SNMP trap: No
Cannot remove an ACD-DN when the ICPM is monitoring it for statistics.

Action:
Severity: Info.
SCH5363
SNMP trap: No
Invalid Attendant Overflow DN type. CDN can not be allowed to be an AODN.

Action:
Severity: Info.
SCH5366
SNMP trap: No
Protocol group already exists.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1845 of 2360

SCH5367
Protocol group does not exist.

Action:
Severity: Info.
SCH5368 x
SNMP trap: No
Protocol group x cannot be removed.

Action: Remove the DSL associated with this protocol and try again.
Severity: Info.
SCH5369
SNMP trap: No
Multi-purpose ISDN Signaling Processor (MISP) has already been enabled.

Action:
Severity: Info.
SCH5370
SNMP trap: No
Multi-purpose ISDN Signaling Processor (MISP) does not exist.

Action:
Severity: Info.
SCH5371
SNMP trap: No
Not a PRI/PRI2 loop or card.

Action:
Severity: Info.
SCH5372
SNMP trap: No
SNMP trap: No
I/O polling table is full.

Action:
Severity: Info.
SCH5373
Cannot obtain MSDL/MISP index, table is full.

Action:
Severity: Info.
SCH5374
SNMP trap: No
Warning: B-channel is not configured for packet data transmission.

Action:
Severity: Info.
SCH5375 l ch
SNMP trap: No
This PRI/PRI2 loop or card channel cannot be used for the BD nailed-up
connection. The next line can be in a format of either:1. NO CH AVAIL IN
LOOP l, or2. TRY xIf output is format 1, there are no more B-channels
System Messages
Page 1846 of 2360

available for a nailed-up connection on PRI loop. PRI is re-prompted and
another loop can be entered. If output is format 2, channel x is available (enter
x at the CH prompt to use this channel).
Action:
Severity: Info.
SCH5376
SNMP trap: No
The number of DSL in the system exceeded the limit.

Action:
Severity: Info.
SCH5377
SNMP trap: No
Card must be disabled for the change request or this is not an MISP card.
Action:
Severity: Info.
SCH5378
SNMP trap: No
This is not an MISP loop.

Action:
Severity: Info.
SCH5379
SNMP trap: No
Maximum of 4 cards allowed per MISP.

Action:
Severity: Info.
SCH5380
SNMP trap: No
Warning: You will not be able to configure DSL7 of this card because
D-channel is configured for packet handler.
Action:
Severity: Info.
SCH5381
SNMP trap: No
SNMP trap: No
Must be a superloop.
Action:
Severity: Info.
SCH5382
Card must be disabled and all DSLs must be removed to out the card.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1847 of 2360

SCH5383
BRI line card already exists.

Action:
Severity: Info.
SCH5384
SNMP trap: No
BRI line card does not exist.

Action:
Severity: Info.
SCH5385
SNMP trap: No
Non BRI card is not allowed.

Action:
Severity: Info.
SCH5386
SNMP trap: No
SNMP trap: No
Must be a DSL TN.

Action:
Severity: Info.
SCH5387
Disable the BRI line card to before configuring its DSL.

Action:
Severity: Info.
SCH5388
SNMP trap: No
All DSLs must be removed to change the card type.

Action:
Severity: Info.
SCH5389
SNMP trap: No
SNMP trap: No
DSL out-of-range (0-7).

Action:
Severity: Info.
SCH5390
DSL data block does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1848 of 2360

SCH5391
DSL data block already exists.

Action:
Severity: Info.
SCH5393
SNMP trap: No
Warning: Make sure the call type matches the DN and TSP.
Action:
Severity: Info.
SCH5394
SNMP trap: No
At least one call type must be defined (VCE, DTA, or PMD).

Action:
Severity: Info.
SCH5395
SNMP trap: No
System contains additional LETIs.

Action:
Severity: Info.
SCH5396
SNMP trap: No
Remove all TSPs before removing the DSL.

Action:
Severity: Info.
SCH5397
SNMP trap: No
Enter three values: LTG, LTN and TEI.

Action:
Severity: Info.
SCH5398
SNMP trap: No
The number of LTIDs in the system exceeded the limit.

Action:
Severity: Info.
SCH5399
SNMP trap: No
Input exceeded the maximum LTEI allowed for this DSL.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1849 of 2360

SCH5400
The LTEI pair does not exist.

Action:
Severity: Info.
SCH5401
SNMP trap: No
Warning: Make sure MCAL value does not exceed the maximum number of
calls for a DSL specified in TSP.
Action:
Severity: Info.
SCH5402
SNMP trap: No
System contains additional TSPs.

Action:
Severity: Info.
SCH5403
SNMP trap: No
SNMP trap: No
BRI DN is not allowed.

Action:
Severity: Info.
SCH5404
MISP loop is not allowed.

Action:
Severity: Info.
SCH5405
SNMP trap: No
BRI SILC/UILC card not allowed. (Monitored set cannot be a BRI set).
Action:
Severity: Info.
SCH5406
SNMP trap: No
Cannot configure this DSL because D-channel is configured for packet

handler.
Action:
Severity: Info.
SCH5407
SNMP trap: No
LTID TEI block does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1850 of 2360

SCH5408
Must enter TEI to delete.

Action:
Severity: Info.
SCH5409
SNMP trap: No
Must enter call type to delete.

Action:
Severity: Info.
SCH5410
SNMP trap: No
Address translation failed.

Action:
Severity: Info.
SCH5411
SNMP trap: No
This is not a DSL line. Enter the TN of a valid DSL line.

Action:
Severity: Info.
SCH5412
SNMP trap: No
USID map is not defined.

Action:
Severity: Info.
SCH5413
SNMP trap: No
Number of TSPs defined has reached the limit.

Action:
Severity: Info.
SCH5414
SNMP trap: No
SNMP trap: No
SNMP trap: No
TSP is already defined.

Action:
Severity: Info.
SCH5415
TSP does not exist.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1851 of 2360

SCH5416
USID has not been removed.

Action:
Severity: Info.
SCH5417
SNMP trap: No
SNMP trap: No
TSP does not exist.

Action:
Severity: Info.
SCH5418
At least one SPID must be defined.

Action:
Severity: Info.
SCH5419
SNMP trap: No
SPID has not been defined.

Action:
Severity: Info.
SCH5420
SNMP trap: No
Input has exceeded the maximum allowed SPIDs per TSP.

Action: Specify a maximum of eight SPIDs.
Severity: Info.
SCH5421
SNMP trap: No
SNMP trap: No
DN input is required.
Action:
Severity: Info.
SCH5422
DNs exceed the allowed limit.

Action:
Severity: Info.
SCH5424
SNMP trap: No
DN does not exist in this TSP.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1852 of 2360

SCH5425
DN has already been deleted.

Action:
Severity: Info.
SCH5426
SNMP trap: No
SNMP trap: No
Invalid input.
Action:
Severity: Info.
SCH5427
Call Type is not defined in the DSL.

Action:
Severity: Info.
SCH5428
SNMP trap: No
Default DN must be entered.

Action:
Severity: Info.
SCH5429
SNMP trap: No
Warning: No current default DN is defined.

Action:
Severity: Info.
SCH5430
SNMP trap: No
SNMP trap: No
SNMP trap: No
Insufficient memory.
Action:
Severity: Info.
SCH5431
DN tree corrupted.
Action:
Severity: Info.
SCH5432
DN exists and is not a BRI DN.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1853 of 2360

SCH5433
DN is defined in other TN. Cannot have multiple appearance for BRI DN.
Action:
Severity: Info.
SCH5434
SNMP trap: No
SNMP trap: No
USID does not exist.

Action:
Severity: Info.
SCH5435
SPID has been defined in TSP number.

Action:
Severity: Info.
SCH5436
SNMP trap: No
Input SPID is too long (maximum of 20 characters).

Action:
Severity: Info.
SCH5437
SNMP trap: No
There is no TSP defined with the specified SPID.

Action:
Severity: Info.
SCH5438
SNMP trap: No
Card does not exist in MISP block.

Action:
Severity: Info.
SCH5439
SNMP trap: No
BRI package not equipped.

Action:
Severity: Info.
SCH5440
SNMP trap: No
Loop/Card has already been assigned.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1854 of 2360

SCH5441
Cannot remove MISP because at least one BRI line card is associated with it.
Action:
Severity: Info.
SCH5442
SNMP trap: No
Cannot move/swap BRI SILC/UILC line card.

Action: Make sure all the DSLs have been removed from the card first.
Severity: Info.
SCH5443
SNMP trap: No
Customer night DN cannot be BRI DN.

Action:
Severity: Info.
SCH5444
SNMP trap: No
Loop pair is used by an MISP.

Action:
Severity: Info.
SCH5445
SNMP trap: No
BRI DN cannot be a Hot Line DN.

Action:
Severity: Info.
SCH5446
SNMP trap: No
BRI DN cannot be night DN.

Action:
Severity: Info.
SCH5447
SNMP trap: No
Attendant Overflow DN cannot be BRI DN.

Action:
Severity: Info.
SCH5448 x
SNMP trap: No
Disconnect dedicated D-channel connection command for the specified MISP

has failed. Where: x = loop number for non-Option 11 or card number for
Option 11.
Action: Check MISP status.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1855 of 2360

SCH5449 x
Send DSL or line card status command for the specified MISP has failed.
Where: x = loop number for non-Option 11 or card number for Option 11.
Severity: Info.
SCH5450 x
SNMP trap: No
Parameter download procedure for the specified MISP has failed. Where: x =
loop number for non-Option 11 or card number for Option 11.
Severity: Info.
SCH5451 x
SNMP trap: No
B-channel dedicated connection to PRI/PRI2 has failed.

Action:
Severity: Info.
SCH5452 x
SNMP trap: No
Disconnect B-channel dedicated connection to PRI/PRI2 command has failed.

Action:
Severity: Info.
SCH5453 x
SNMP trap: No
Send maintenance pending message to MISP failed. Where: x = loop number

for non-Option 11 or card number for Option 11.
Action:
Severity: Info.
SCH5454
SNMP trap: No
Invalid Logical Terminal IDentifier (LTID) input. The combination of both

Logical Terminal Group (LTG) and Logical Terminal Number (LTN) having
their maximum values (LTG = 15 and LTN = 1023) is not valid.
Action: Use a smaller value for either LTG or LTN
Severity: Info.
SCH5455
SNMP trap: No
SNMP trap: No
DSL already exists.

Action:
Severity: Info.
System Messages
Page 1856 of 2360

SCH5456
DSL does not exist.

Action:
Severity: Info.
SCH5457
SNMP trap: No
Multi-purpose ISDN Signaling Processor (MISP) must be disabled.

Action:
Severity: Info.
SCH5458
SNMP trap: No
TSP parameters downloading to the MISP failed.

Action:
Severity: Info.
SCH5460
SNMP trap: No
Group Call group number cannot be a BRI DN.

Action:
Severity: Info.
SCH5461
SNMP trap: No
DN does not exist or is not a PBX or BCS type.

Action:
Severity: Info.
SCH5462
SNMP trap: No
Build D-channel nailed up to MISP loop failed.

Action:
Severity: Info.
SCH5463
SNMP trap: No
B-channel cannot be used for both packet mode data and voice/data.
Action:
Severity: Info.
SCH5491
SNMP trap: No
Bad CPNW configuration: the speed call list specified in the CPNW data block
of LD18 is invalid.
Action: Change CPNW block in LD18.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1857 of 2360

SCH5492
The PINX DN cannot be reached due to one of the following: 1. The

configuration is invalid. 2. The D-channel has been disabled 3. The local PINX
DN is not defined
Action: Check that the network numbering plan is valid.
Severity: Info.
SCH5493
SNMP trap: No
TCAP or ROSE protocol error for CPNW feature.

Severity: Info.
SCH5496
SNMP trap: No
An ACD DN defined for data service access may not be a default ACD DN or
a CDN.
Action:
Severity: Info.
SCH5497
SNMP trap: No
Unable to define a new BCHI with IFC=SL1.

Action: To define a new BCHI with IFC=SL1, default at RCVP on the first pass.
Enter SL1 at IFC. Make a second pass from DCHI and enter YES at RCVP.
Severity: Info.
SCH5498
SNMP trap: No
RCVP is set to "yes", which is only allowed for SL-1 interfaces.

Action:
Severity: Info.
SCH5499
SNMP trap: No
Cannot change. There are Automatic Wake Up calls during this interval which
must use this route data block.
Action: Wait until there are no more Wake Up calls before changing this route.
If the background terminal is equipped, do a "PR Wa MA" command to determine
the next free five minute time interval. Note that this command does not list AWU
re-tries for the interval.
Severity: Info.
SCH5500
SNMP trap: No
Input value out of range 0-3.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1858 of 2360

SCH5501
There can only be one Wake Up Key (WUK) per set. Before moving the WUK
key, the existing WUK must be removed (NUL).
Action:
Severity: Info.
SCH5502
SNMP trap: No
MAXT + DCMX cannot be greater than 255.

Action:
Severity: Info.
SCH5503
SNMP trap: No
Response to CTRQ must have 4 digits.

Action:
Severity: Info.
SCH5504
SNMP trap: No
First field of the response to CTAL cannot be longer than 16 digits.

Action:
Severity: Info.
SCH5505
SNMP trap: No
Second field of the response to CTAL is out-of-range (0-1023).

Action:
Severity: Info.
SCH5506
SNMP trap: No
Third field of the response to CTAL is out-of-range (0-4).

Action:
Severity: Info.
SCH5507
SNMP trap: No
ACD stations not allowed MCTA Class of Service unless the EMCT package
is equipped.
Action:
Severity: Info.
SCH5508
SNMP trap: No
Same card and port number has been used.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 1859 of 2360

SCH5509
Warning: The entered DCH port may not be supported on your current Option
11 configuration.
Acceptable DCH port numbers are AK79 (PR12) card - one DCHI on port #1
is available NTAK93 (PRI) card - one DCHI on port #1 is available NTAK02
(DCHI/SDI) card - two DCHIs on ports #1 and #3 are available.
Action: If using one of the above cards, restart the overlay and enter an
acceptable port number from the above list. If using other cards, proceed only
after checking related documentation to confirm that the entered port number is
acceptable.
Severity: Info.
SCH5511
SNMP trap: Yes
The loop type is out-of-range or not supported.

Action:
Severity: Info.
SCH5512
SNMP trap: No
Warning: the DWC key is defined for a CDN which is not in controlled mode.
DWC for a CDN in default mode is meaningless.
Action:
Severity: Info.
SCH5514
SNMP trap: No
This APL-TTY port is configured for the intercept computer feature.

Action:
Severity: Info.
SCH5516
SNMP trap: No
Incorrect response for RGTP. Enter 8 or 16.

Action:
Severity: Info.
SCH5518
SNMP trap: No
BGD package is restricted.

Action:
Severity:
SCH5519
SNMP trap: No
Incorrect TYPE entered when REQ is CHG or PRT.

Action: Re-enter a correct type.
Severity: Info.
SNMP trap: No
System Messages
Page 1860 of 2360

SCH5522
The specified TN is not defined.

Action:
Severity: Info.
SNMP trap: No
SCH5524 DN xxxx NEW MARP l s c u The current TN is no longer the MARP TN for DN xxxx.
The new MARP for DN xxxx has defaulted to TN l s c u.
Action:
Severity: Info.
SCH5525
SNMP trap: No
New TN(s) copied from a TN template with new DNs for the prime DN
appearances. The new TNs are MARPs for the new prime DNs. Secondary
DNs are copied without retaining MARP designations.
Action:
Severity: Info.
SCH5526
SNMP trap: No
Warning: In printing the DN block for a DN, no MARP or more than one MARP
TN was found in the database. Only one MARP should be defined for a DN.
Action: Changing the database is recommended.
Severity: Info.
SCH5527
SNMP trap: No
X3W trunk requires DID trunk type.

Action:
Severity: Info.
SCH5528
SNMP trap: No
OHAS DN must be a Single Appearance, Multiple Appearance or ACD DN.

Action:
Severity: Info.
SCH5530
SNMP trap: No
The Set Relocation table does not exist; therefore, no operation may be
performed on it. The Set Relocation package 53 may not be equipped.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1861 of 2360

SCH5531
Exactly eight characters must be entered at prompt NTCD.

Action:
Severity: Info.
SCH5532
SNMP trap: No
Exactly six characters must be entered at prompt SER.

Action:
Severity: Info.
SCH5533
SNMP trap: No
Exactly two characters must be entered at prompt COLR and RLS.

Action:
Severity: Info.
SCH5534
SNMP trap: No
Input must be a valid hexadecimal digit (0-9, A-F).

Action:
Severity: Info.
SCH5535
SNMP trap: No
That TN cannot be found in the Set Relocation table.

Action: Print the relocation table to see the valid TNS.
Severity: Info.
SCH5536
SNMP trap: No
Autodial Timeout (ADLD) cannot be greater than dial tone interdigit timeout for
500 telephones (DIND) or 2500 telephones (DIDT).
Action:
Severity: Info.
SCH5537
SNMP trap: No
SNMP trap: No
Invalid autodial DN.

Action:
Severity: Info.
SCH5538
Invalid response to prompt PSEL.

Action: Enter DMDM or TLNK.
Severity: Info.
SNMP trap: No
System Messages
Page 1862 of 2360

SCH5539
Invalid response to prompt PSDS.

Action: Enter YES or NO.
Severity: Info.
SCH5540
SNMP trap: No
Invalid response to prompt V25.

Action: Enter YES or NO.
Severity: Info.
SCH5541
SNMP trap: No
Only OUT or CHG is allowed for TYPE = MTRT.

Action:
Severity: Info.
SCH5542
SNMP trap: No
TRAN must be SYN if PSDS = YES. Enter SYN to TRAN or set PSDS = NO
before setting TRAN to ASYN.
Action:
Severity: Info.
SCH5543
SNMP trap: No
No customer or no customer with PREO option set.

Action:
Severity:
SCH5544
SNMP trap: No
Illegal key word. Should be R232 or R422.

Action:
Severity: Info.
SCH5545
SNMP trap: No
The group number must be input when a configuring a new device. No {cr}
without input is allowed.
Action:
Severity: Info.
SCH5546
SNMP trap: No
Illegal key word. Should be DTE or DCE.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1863 of 2360

SCH5547
Out of memory. Cannot allocate unprotected AML data store.

Action: To free some memory, deallocate I/O devices no longer in use, if they
exist.
Severity: Info.
SCH5548
SNMP trap: No
Out of memory. Cannot allocate protected AML data store.

exist.
Severity: Info.
SCH5549
SNMP trap: No
At least one user type must be defined.

Action:
Severity: Info.
SCH5550
SNMP trap: No
Out of memory. Cannot allocate required SDI memory.

exist.
Severity: Info.
SCH5552
SNMP trap: No
Warning: To use the changed download parameters, must disable and enable
the SDI port just modified.
Action:
Severity: Info.
SCH5553
SNMP trap: No
Warning: Max of CSQI/CSQO is 25% of NCR. Increase NCR to be able to

configure greater CSQI/CSQO.
Action:
Severity: Warning.
SCH5554
SNMP trap: No
Invalid I/O progress marker detected.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1864 of 2360

SCH5555
Invalid input for ADAN prompt.

Action:
Severity: Info.
SCH5556
SNMP trap: No
Wrong action entered for ADAN prompt.

Action:
Severity: Info.
SCH5557
SNMP trap: No
Invalid device type for ADAN.

Action:
Severity: Info.
SCH5558
SNMP trap: No
Invalid device type for ADAN.

Action:
Severity: Info.
SCH5559
SNMP trap: No
AML cannot be configured due to package restriction.

Action:
Severity: Info.
SCH5560
SNMP trap: No
DCH cannot be configured due to package restriction.

Action:
Severity: Info.
SCH5561
SNMP trap: No
SNMP trap: No
Invalid I/O device.

Action:
Severity: Info.
SCH5562
No logical number entered for ADAN prompt.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1865 of 2360

SCH5563
Invalid logical number or invalid I/O device. Example: OUT BDCH x to remove
backup D-channel.
Action:
Severity: Info.
SCH5564
SNMP trap: No
Primary DCH must be specified.

Action:
Severity: Info.
SCH5565
SNMP trap: No
Backup DCH already configured for this primary DCH.

Action:
Severity: Info.
SCH5566
SNMP trap: No
SNMP trap: No
No card type given.

Action:
Severity: Info.
SCH5567
Invalid card type for TTY device.

Action:
Severity: Info.
SCH5568
SNMP trap: No
Invalid card type for AML device.

Action:
Severity: Info.
SCH5569
SNMP trap: No
Invalid card type for DCH device.

Action:
Severity: Info.
SCH5570
SNMP trap: No
Backup DCH must be on the same card type as primary DCH.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1866 of 2360

SCH5571
No device number entered.

Action:
Severity: Info.
SCH5572
SNMP trap: No
No port number entered.

Action:
Severity: Info.
SCH5573
SNMP trap: No
Specified port not available, other ports are available.

Action:
Severity: Info.
SCH5574
SNMP trap: No
No port is available on the specified MSDL card.

Action:
Severity: Info.
SCH5575
SNMP trap: No
Invalid MSDL physical address.

Action:
Severity: Info.
SCH5576
SNMP trap: No
Invalid device number - may conflict with already existing ADAN device
number.
Action:
Severity: Info.
SCH5577
SNMP trap: No
Incorrect number of parameters for ADAN prompt.

Action:
Severity: Info.
SCH5578
SNMP trap: No
Logical application must be disabled.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1867 of 2360

SCH5579
Physical I/O block pointer corruption.

Action:
Severity: Info.
SCH5580
SNMP trap: No
TTY cannot be configured.

Action:
Severity: Info.
SCH5581
SNMP trap: No
TTY cannot be changed.

Action:
Severity: Info.
SCH5584
SNMP trap: No
SNMP trap: No
TTY cannot be outed.

Action:
Severity: Info.
SCH5586
Device must be disabled to be outed.

Action:
Severity: Info.
SCH5587
SNMP trap: No
SNMP trap: No
TTY error.
Action:
Severity: Info.
SCH5589
Cannot out application from MSDL/TMDI card, as this is the last application.
Action: Disable the MSDL card.
Severity: Info.
SCH5590
SNMP trap: No
The number of new logical applications (AML or DCH) has exceeded its
allowable system limit.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1868 of 2360

SCH5591
History File cannot be configured due to package restriction.

Action:
Severity: Info.
SCH5592
SNMP trap: No
History File cannot be configured due to no entry available in the I/O table.
Action:
Severity: Info.
SCH5593
SNMP trap: No
History File does not exist; therefore, cannot use the chg or del command.
Action:
Severity: Info.
SCH5594
SNMP trap: No
Data port out-of-range for MCU. Enter 8-15 on ISDLC cards, 16-31 on DAC
cards.
Action:
Severity: Info.
SCH5596
SNMP trap: No
TRAN must be SYNC if PSDS = YES.

Action:
Severity: Info.
SCH5597
SNMP trap: No
BAUD must be 11 or 12 for PSDS = YES.

Action:
Severity: Info.
SCH5598
SNMP trap: No
Operating and system parameters may not be set properly for data option.
Action: Change PSEL or OPE if needed.
Severity: Info.
SCH5599
SNMP trap: No
Operating and system parameters may not be set properly for data option.
Action: Change PSEL or OPE if needed.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1869 of 2360

SCH5600
Invalid input for DTAO. Enter MPDA or MCA.

Action:
Severity: Info.
SCH5601
SNMP trap: No
Invalid input for PSEL. Enter DMDM or TLNK.

Action:
Severity: Info.
SCH5602
SNMP trap: No
Invalid input for PSDS. Enter YES or NO.

Action:
Severity: Info.
SCH5605
SNMP trap: No
Invalid input for HDLC. Enter YES or NO.

Action:
Severity: Info.
SCH5606
SNMP trap: No
MBGS number already assigned to another tenant.

Action: If necessary, use temporary value "MBGS 0" to switch the MBGS.
Severity: Info.
SCH5607
SNMP trap: No
The route entered is not yet configured; cannot add to a customized CPG.
Defaulted to CPG 0.
Action: First configure the route and then re-enter.
Severity: Info.
SCH5609
SNMP trap: No
Clock controller must be disabled first. (For System Option 11 only.)

Action:
Severity: Info.
SCH5610
SNMP trap: No
The slot number is not a valid DTI/PRI slot. It must be defined in Overlay 17
first. (For System Option 11 only.)
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1870 of 2360

SCH5611
Input is conflict with the existing slot defined for secondary clock reference.
(For System Option 11 only.)
Action:
Severity: Info.
SCH5612
SNMP trap: No
Wrong input field for AUXR prompt. It must be YES/NO or {CR}. (For System
Option 11 only.)
Action:
Severity: Info.
SCH5613
SNMP trap: No
Invalid input for AUXR prompt. (For System Option 11 only.)

Action:
Severity: Info.
SCH5616
SNMP trap: No
Primary/secondary clock reference loop must set equal to freerun before

changes AUXR prompt to YES. (For System Option 11 only)
Action:
Severity: Info.
SCH5617
SNMP trap: No
Clock slot number out-of-range. (For System Option 11 only)

Action:
Severity: Info.
SCH5618
SNMP trap: No
Must disable the existing clock controller and remove the clock data before
doing any clock controller changes. (For System Option 11 only)
Action:
Severity: Info.
SCH5619
SNMP trap: No
Must remove the clock controller data first before delete the digital loop. (For
System Option 11 only)
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1871 of 2360

SCH5625
Multiple Appearance data DN is not allowed.

Action:
Severity: Info.
SCH5628
SNMP trap: No
Attendant Forward No Answer (AFNA) package 134 is not equipped.

Action:
Severity: Info.
SCH5629
SNMP trap: No
{CR} not allowed for the prompt NFNA when OPT is changed from DNCA to
DNCS, or from DNCS to DNCA.
Action:
Severity: Info.
SCH5630
SNMP trap: No
Must be a DID/TIE DTI trunk.

Action:
Severity: Info.
SCH5631
SNMP trap: No
RVQ feature only applies to SL-1 interface (Release 18 and later).

Action:
Severity: Info.
SCH5633
SNMP trap: No
Input out-of-range: 2-(10)-30 seconds.

Action:
Severity: Info.
SCH5634
SNMP trap: No
Input out-of-range: 4-(5)-10 retries.

Action:
Severity: Info.
SCH5635
SNMP trap: No
DTAD data does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1872 of 2360

SCH5636
DTAD data already exists.

Action:
Severity: Info.
SCH5637
SNMP trap: No
Maximum number of digits reached, max is 5.

Action:
Severity: Info.
SCH5638
SNMP trap: No
Maximum number of sequences reached, max is 20.

Action:
Severity: Info.
SCH5639
SNMP trap: No
DTAD sequence does not exist. Cannot remove.

Action:
Severity: Info.
SCH5640
SNMP trap: No
Multi-purposeSerial Data Link (MSDL) package 222 is restricted.

Action:
Severity: Info.
SCH5641
SNMP trap: No
HDTI trunk must have DTN CLS.

Action:
Severity: Info.
SCH5642
SNMP trap: No
There are no FGD blocks configured (for command PRT).

Action:
Severity: Info.
SCH5647
SNMP trap: No
MSDL RCAP capability only applies to SL-1 interface and on Release 18 and
later.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1873 of 2360

SCH5648
History file is already configured.

Action:
Severity: Info.
SCH5649
SNMP trap: No
Must enter user type if new D-channel.

Action:
Severity: Info.
SCH5650
SNMP trap: No
Invalid primary D-channel number.

Action:
Severity: Info.
SCH5651
SNMP trap: No
Invalid response for RTS. Enter ON or OFF.

Action:
Severity: Info.
SCH5652
SNMP trap: No
Cannot OUT or CHG that TN. Only entries which resulted from a Modular
telephone relocation are eligible for manipulation in LD 50 TYPE = MTRT.
Action:
Severity: Info.
SCH5653
SNMP trap: No
Overlay 45 is not supported for Option 11.

Action:
Severity: Info.
SCH5654
SNMP trap: No
Before setting the SIAA option, you must define the intrusion tone in LD 56.
Action:
Severity: Info.
SCH5655
SNMP trap: No
A value greater than 25 has been entered for the TNDM prompt when the
DPNSS package is equipped. The value 25 is used for DPNSS calls.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1874 of 2360

SCH5656
Invalid user types for this device.

Action:
Severity: Info.
SCH5657
SNMP trap: No
Missing software for DSDL/MSIP or application running on it. Could be MISP,

MSDL, BRI, SDI, DCH, or AML.
Action:
Severity: Info.
SCH5658
SNMP trap: No
The card type entered is not valid for MSDL/MISP or application running on it.
Valid types are MISP, MSDL, BRIl, SDI, DCH, or AML.
Action:
Severity: Info.
SCH5659
SNMP trap: No
Cannot add D-channel packet data option because DSL 7 of the last card
associated with the MISP is configured.
Action:
Severity: Info.
SCH5661
SNMP trap: No
Cannot remove D-channel packet data option because at least one associated
DSL has a LTEI pair defined.
Action:
Severity: Info.
SCH5662
SNMP trap: No
For the Meridian 911 package, the TN for the CWNT must be a
500/2500 telephone.
Action:
Severity: Info.
SCH5663
SNMP trap: No
Entered DN does not exist.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1875 of 2360

SCH5664
Invalid DN type for Nite LDN.

Action:
Severity: Info.
SCH5665
SNMP trap: No
This Nite LDN is not defined.

Action:
Severity: Info.
SCH5666
SNMP trap: No
NO is only allowed when all Nite DN's are cleared.

Action:
Severity: Info.
SCH5667
SNMP trap: No
When configuring an MCU trunk, a corresponding voice TN must be

configured.
Action: Either "out" the unit in the voice TN or put the MCU trunk on a TN where
the corresponding voice TN is empty.
Severity: Info.
SCH5668
SNMP trap: No
A route used for the BRI packed handler (BRIP = YES) must be a PRI or PRI2
route.
Action:
Severity: Info.
SCH5670
SNMP trap: No
For Primary loop, the slot must be set equal to the clock controller slot number.
For secondary loop, the slot must not set equal to the clock controller slot
number.
Action:
Severity: Info.
SCH5671
SNMP trap: No
The loop must be set to free run mode or switch the tracking to another
reference before entering the changes.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1876 of 2360

SCH5672
Start arrangement for M911 trunk must be WNK.

Action:
Severity: Info.
SCH5673
SNMP trap: No
For M911 trunks, signaling must be EAM, EM4 or LDR.

Action:
Severity: Info.
SCH5674
SNMP trap: No
For M911 trunks, AUTO DN must be a CDN.

Action:
Severity: Info.
SCH5675
SNMP trap: No
Cannot change a non-Meridian 911 route to a Meridian 911 route.

Action:
Severity: Info.
SCH5676
SNMP trap: No
SNMP trap: No
ACD listptr is nil.

Action:
Severity: Info.
SCH5677
The primary D-channel cannot be removed, unless the backup D-channel is

removed first.
Action:
Severity: Info.
SCH5679
SNMP trap: No
Not allowed to change the user from ISLD to PRA or SHA if the D-channel is
equipped with backup D-channel.
Action: First remove the backup D-channel. Then change the user from ISLD to
PRA or SHA and add the backup D-channel.
Severity: Info.
SCH5680
SNMP trap: No
The NEW MISP's application must be disabled for the change request.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1877 of 2360

SCH5681
Send line card status to MISP failed.

Action:
Severity: Info.
SNMP trap: No
SCH5682 tn l s c u Cannot update MARP TN designation: TN l s c u failed TNTRANS.

Action: Check the status of the TN. MARP TN assignment in the database
needs correction later.
Severity: Info.
SCH5683
SNMP trap: No
MOV or OUT not allowed on a telephone being used as a CWNT of an ACD

Action:
Severity: Info.
SCH5684
SNMP trap: No
Cannot remove a CDN if it is being used as an Auto-terminate DN (LD 23).

Action:
Severity: Info.
SCH5685
SNMP trap: No
The device must be disabled to change a group number.

Action:
Severity: Info.
SCH5686
SNMP trap: No
Cannot remove a CDN if it is being used as an CWNT. Counter should never

be negative. Design error has occurred
Action:
Severity: Info.
SCH5687
SNMP trap: No
Wrong extender. Enter 3PE.

Action:
Severity: Info.
SCH5688
SNMP trap: No
Card slot out-of-range (1-13).

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1878 of 2360

SCH5689
CNI port number out-of-range (0-1).

Action:
Severity: Info.
SCH5690
SNMP trap: No
Network group out-of-range (0-4).

Action:
Severity: Info.
SCH5693
SNMP trap: No
HDK/FDK device types to the ADAN are not permitted on this system type.
Action:
Severity: Info.
SCH5694
SNMP trap: No
Service change is not allowed on this TN since it is currently active on an M911

Action:
Severity: Info.
SCH5695
SNMP trap: No
The flow control option is not available for this user type.
Action:
Severity: Info.
SCH5696
SNMP trap: No
Invalid input entered for this prompt(ALOW/DENY expected).

Action:
Severity: Info.
SCH5698
SNMP trap: No
Equal Access call restriction was specified for this route (EQAR Yes), but a
restriction type was not selected (GCR and SCR are both No).
Action: Either set EQAR to No, or set one, or both of the restriction types (GCR
and SCR) to Yes.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1879 of 2360

SCH5699
Equal Access call restriction was specified for this route (EQAR Yes), but a
restriction type was not selected. (General Carrier Restriction was not
activated (GCR No) and Selective Carrier Restriction (SCR) is not available
because the NFCR package is not enabled).
Action: Either set EQAR to No, or set GCR to Yes.
Severity: Info.
SCH5700
SNMP trap: No
Warning: Table 0 has been configured for this card by default. Verify Table 0
in LD 97 contains the desired parameters for dial tone detection.
Action:
Severity: Info.
SCH5701
SNMP trap: No
XTD Table has not yet been defined in LD 97.

Action:
Severity: Info.
SCH5702
SNMP trap: No
Tone and cadence table download already in progress.

Action:
Severity: Info.
SCH5703
SNMP trap: No
Configure a DCH block for DPNSS in the LD 17 first.

Action:
Severity: Info.
SCH5704
SNMP trap: No
A maximum of 16 characters are allowed for DES.

Action:
Severity: Info.
SCH5705
SNMP trap: No
Input does not match the existing value of DES. Existing DES is not changed.
Action: To remove a DES, enter "X" followed by the exact characters of the
existing DES.
Severity: Info.
SNMP trap: No
System Messages
Page 1880 of 2360

SCH5706
Input number of characters does not match the existing value of DES. Existing
DES is not changed.
Action: To remove a DES, enter "X" followed by the exact characters of the
existing DES.
Severity: Info.
SCH5707
SNMP trap: No
DES value already exists.

Action: To change a DES, you must remove the current DES first. To remove a
DES, enter
"X" followed by the exact characters of the existing DES.
Severity: Info.
SCH5708
SNMP trap: No
This Primary Rate Interface B-channel is used for a connection between Basic
Rate Interface and a packet handler.
Action: Remove the relationship in LD 27.
Severity: Info.
SCH5709
SNMP trap: No
Memory error. Tone and cadence table download failed.

Action:
Severity: Major.
SCH5710
SNMP trap: No
XSM is not allowed to be enabled for an active TTY.

Action:
Severity: Info.
SCH5711
SNMP trap: No
Default XTD Table (Table 0) cannot be removed.

Action:
Severity: Info.
SCH5712
SNMP trap: No
Table cannot be removed because it is configured for an XTD card.

Action: Change XTD card configuration in LD 13 before removing Table.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1881 of 2360

SCH5713
Warning: Make sure that this XTD Table is not defined in any Route Data
Blocks.
Action:
Severity: Info.
SCH5716
SNMP trap: No
Warning: ARF is not allowed with BAT or LBS. Class of Service has been
changed to ARF XBAT XLBS.
Action:
Severity: Info.
SCH5717
SNMP trap: No
Warning: BAT is not allowed with ARF or LBS. Class of Service has been
changed to BAT XARF XLBS.
Action:
Severity: Info.
SCH5718
SNMP trap: No
Warning: LBS is not allowed with BAT or ARF. Class of Service has been
changed to LBS XBAT XARF.
Action:
Severity: Info.
SCH5719
SNMP trap: No
The XDID/EAM parameters may not be changed while the unit is busy.
Action:
Severity: Info.
SCH5720
SNMP trap: No
Service loop (CONF, MFS, TDS, or XCT) cannot be added because the
maximum number of service loops already exists. To add an XCT one of the
TDS, MFS, or CONF loop service limits may be exceeded. In Release 14 the
maximum number of service loops allowed is 15. In Release 17 the maximum
number is 16. In Release 18 the maximum number is 64.
Action:
Severity: Info.
SCH5725
SNMP trap: No
Invalid Controller number (out-of-range or undefined).

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1882 of 2360

SCH5726
Cannot print an undefined Controller.

Action:
Severity: Info.
SCH5727
SNMP trap: No
Cannot delete an undefined Controller.

Action:
Severity: Info.
SCH5728
SNMP trap: No
Cannot delete a Controller that is not empty.

Action: Remove TN assigned to superloops associated with the Controller first.
Severity: Info.
SCH5729
SNMP trap: No
No free Controller available.

Action:
Severity: Info.
SCH5730
SNMP trap: No
Location cannot have more than 6 characters.

Action:
Severity: Info.
SCH5735
SNMP trap: No
Remove all TNs assigned first.

Action:
Severity: Info.
SCH5738
SNMP trap: No
Superloop number must be multiple of 4.

Action:
Severity: Info.
SCH5739
SNMP trap: No
Cannot define that superloop. Some internal loops already exist as regular
loops.
Action: Remove all TNs and route numbers for the four loops higher than the
new superloop. For example, to add superloop 4, old 4, 5, 6, and 7 must be
undefined.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1883 of 2360

SCH5740
Cannot print a new superloop.

Action:
Severity: Info.
SCH5741
SNMP trap: No
Cannot delete a new superloop.

Action:
Severity: Info.
SCH5742
SNMP trap: No
Superloop number is out-of-range (x-y).

Action:
Severity: Info.
SCH5743
SNMP trap: No
Cannot remove a superloop that is not empty.

Action: Remove all TNs assigned to this superloop first.
Severity: Info.
SCH5744
SNMP trap: No
Wrong number of input fields for the prompt SLOT.

Action: Enter LEFT or RIGHT.
Severity: Info.
SCH5745
SNMP trap: No
Invalid keyword for the prompt SLOT.

Action:
Severity: Info.
SCH5746
SNMP trap: No
Cannot delete XPE0 for a new superloop. XPE0 does not exist.
Action:
Severity: Info.
SCH5747
SNMP trap: No
Cannot remove undefined XPE0.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1884 of 2360

SCH5748
Cannot remove XPE0 that is not empty.

Action: Remove all TNs assigned to this Controller.
Severity: Info.
SCH5749
SNMP trap: No
Wrong number of inputs for the prompt XPE0.

Action: Enter Controller number (0-95), starting segment (0 - 3), and ending
segment (0 - 3).
Severity: Info.
SCH5750
SNMP trap: No
Peripheral number is not defined or out-of-range.

Action:
Severity: Info.
SCH5751
SNMP trap: No
XPE0 cannot have the same number as XPE1.

Action: Remove XPE1 first.
Severity: Info.
SCH5752
SNMP trap: No
Existing XPE0 is not empty.

Action: Remove all information in order to change the Controller number.
Severity: Info.
SCH5753
SNMP trap: No
Input segment number is out-of-range (0-3).

Action:
Severity: Info.
SCH5754
SNMP trap: No
Another superloop already exists within the segments.

Action:
Severity: Info.
SCH5755
SNMP trap: No
Starting segment number must be smaller than ending segment number.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1885 of 2360

SCH5756
Cannot remove segments that are not empty.

Action: Remove all TNs assigned to this superloop.
Severity: Info.
SCH5757
SNMP trap: No
{CR} is not allowed for the input. XPE0 has been deleted and XPE1 does not
exist.
Action:
Severity: Info.
SCH5758
SNMP trap: No
Define XPE0 or XPE1 for a superloop.

Action:
Severity: Info.
SCH5759
SNMP trap: No
Cannot remove XPE1 from a new superloop. XPE1 does not exist.
Action:
Severity: Info.
SCH5760
SNMP trap: No
Cannot remove undefined XPE1.

Action:
Severity: Info.
SCH5761
SNMP trap: No
Cannot remove XPE1. XPE0 has been removed. Need information for XPE0
or XPE1.
Action:
Severity: Info.
SCH5762
SNMP trap: No
SNMP trap: No
Cannot remove XPE1.

Action:
Severity: Info.
SCH5763
Wrong number of input field for the prompt XPE1.

Action: Enter Controller number (0-95), starting segment (0-3), and ending
segment (0-3).
Severity: Info.
SNMP trap: No
System Messages
Page 1886 of 2360

SCH5764
XPE1 cannot be the same as XPE0.

Action:
Severity: Info.
SCH5765
SNMP trap: No
Existing XPE1 is not empty.

Action: Remove all information in order to change the Controller number.
Severity: Info.
SCH5767
SNMP trap: No
Input value is out-of-range.

Action:
Severity: Info.
SCH5768
SNMP trap: No
Invalid input for prompt DTMF.

Action:
Severity: Info.
SCH5769
SNMP trap: No
Invalid input for prompt P10P.

Action:
Severity: Info.
SCH5770
SNMP trap: No
Invalid input for prompt S10P.

Action:
Severity: Info.
SCH5771
SNMP trap: No
Invalid input for prompt 20PP.

Action:
Severity: Info.
SCH5772
SNMP trap: No
Invalid input for INTN. Enter YES for A-law, NO for -law.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1887 of 2360

SCH5773
Allowed values for quiet code are 0-3.

Action:
Severity: Info.
SCH5774
SNMP trap: No
Input out-of-range for maintenance thresholds, Allowed values are 1-65532.

CONT is the number of continuity faults per timeslot and CRCF is the number
of CRC failures per cable.
Action:
Severity: Info.
SCH5775
SNMP trap: No
Input out-of-range for flash timer. FLSH can be 45-768 ms.

Action:
Severity: Info.
SCH5779
SNMP trap: No
Both destination TNs must be unoccupied.

Action:
Severity: Info.
SCH5780
SNMP trap: No
SNMP trap: No
TN cannot be 0 0 0 0.
Action:
Severity: Info.
SCH5781
Card number for this superloop is invalid.

Action:
Severity: Info.
SCH5782
SNMP trap: No
Cannot change card density for superloops.

Action:
Severity: Info.
SCH5783
SNMP trap: No
SL-1 set cannot be located in a superloop.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1888 of 2360

SCH5784
Cannot move a pair when source TN is not a digital set.

Action:
Severity: Info.
SCH5785
SNMP trap: No
Cannot move a pair when one of the TNs does not exist.
Action:
Severity: Info.
SCH5786
SNMP trap: No
Superloop does not exist.

Action:
Severity: Info.
SCH5787
SNMP trap: No
Invalid trunk for Universal Trunk or E & M Dictation Trunk. Conflict with one
trunk type has already been defined.
Action:
Severity: Info.
SCH5788
SNMP trap: No
1200 Ohm termination impedance applies only to RAN trunks.

Action:
Severity: Info.
SCH5789
SNMP trap: No
LST is not allowed for JCO in XTRK.

Action:
Severity: Info.
SCH5790
SNMP trap: No
1200 Ohm termination impedance should be used for RAN trunks in Universal
Trunk.
Action:
Severity: Info.
SCH5791
SNMP trap: No
10 PPS2 is for Universal Trunk or E & M Dictation Trunk only.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1889 of 2360

SCH5794
Cards 10 to 14 are invalid for Network/DTR/XMFC Card array.

Action:
Severity: Info.
SCH5796
SNMP trap: No
TN 0 0 0 0 is not allowed. Use this TN for DTR/XMFC.

Action:
Severity: Info.
SCH5797
SNMP trap: No
TDET cannot be defined in a superloop.

Action:
Severity: Info.
SCH5798
SNMP trap: No
Card density (DENS) must be defined.

Action: Enter SDENS for single SDI ports (on CPU cards), DDEN for two port
SDI cards (QPC139), QDEN for four port SDI cards (QPC841/NT8D41).
Severity: Info.
SCH5799
SNMP trap: No
Superloop must be disabled before removing.

Action:
Severity: Info.
SCH5803
SNMP trap: No
CPU number out-of-range (0-1).

Action:
Severity: Info.
SCH5804
SNMP trap: No
The specified CNI port is in-service.

Action: Disable the CNI port before changing it.
Severity: Info.
SCH5805
SNMP trap: No
The specified group is configured for other CNI port.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1890 of 2360

SCH5806
The specified slot is configured other than as CNI.

Action:
Severity: Info.
SCH5807
SNMP trap: No
Slot already exists for other card.

Action:
Severity: Info.
SCH5808
SNMP trap: No
Error occurred in printing CINV.

Action:
Severity: Info.
SCH5809
SNMP trap: No
TSA and ASA class of services are mutually exclusive.

Action:
Severity: Info.
SCH5810
SNMP trap: No
Yellow alarm pattern of FDL can only be specified for ESF framing format. The
software automatically enters YALM = DG2.
Action:
Severity: Info.
SCH5812
SNMP trap: No
Cannot delete DNCO, still in use.

Action:
Severity: Info.
SCH5813
SNMP trap: No
A USR key cannot be configured on a data set (CLS DTA).

Action:
Severity: Info.
SCH5814
SNMP trap: No
A set cannot have USR key with USRD Class of Service.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1891 of 2360

SCH5815
Terminal's Ringing Cycle Option (RCO) was reset from {old RCO} to default
value 0, because the CLS was changed to FND and MWD.
Action:
Severity: Info.
SCH5816
SNMP trap: No
Warning: PBXT test scheduled for automatic execution in the daily routines
Action:
Severity: Info.
SCH5817
SNMP trap: No
CONF loops can only be defined on loops 29, 30 & 31 for Option 11.
Action:
Severity: Info.
SCH5818
SNMP trap: No
Cannot define CONF loop on loop 31 if only 1 cabinet defined.

Action:
Severity: Info.
SCH5819
SNMP trap: No
The VAS is in use in the customer data block under the VSID prompt.
Action: Delete the VAS from LD 15, then remove it from LD17. To clear the VAS,
use LD 15, and go to the VSID prompt.
Severity: Info.
SCH5820
SNMP trap: No
The VAS ID is in use by a CCR, Meridian Link, or Data application.

Action: Remove the VAS by using LD 23, then delete the VAS from LD 17.
Severity: Info.
SCH5821
SNMP trap: No
The VAS ID is in use by the teleset-messaging.

Action: Remove it in LD 23, then delete it from LD 17.
Severity: Info.
SCH5822
SNMP trap: No
The VAS ID is in use by the teleset-status.

Action: Remove it in LD 23, then delete it from LD 17.
Severity: Info.
SNMP trap: No
System Messages
Page 1892 of 2360

SCH5823
The VAS ID is in use by the CCR, or the Meridian Link application.

Action: Remove it in LD 23, then delete it from LD17.
Severity: Info.
SCH5824
SNMP trap: No
The VAS does not exist.

Action: First create the VAS in the LD 17, then use it in LD 15.
Severity: Info.
SCH5825
SNMP trap: No
This loop cannot be removed until its associated DDSL has been removed
first.
Action:
Severity: Info.
SCH5826
SNMP trap: No
Cannot change or print the Class of Service MREA/MRED in the TN block

without the option enabled in LD 15.
Action: Enable NMDR/DMDR in LD 15 before attempting the change.
Severity: Info.
SCH5827
SNMP trap: No
Cannot assign a greater value to NMDR than to CFNA. Cannot assign a

greater value to DMDR than to DFNA. Need to assign a value that is less than
the value of CFNA or DFNA.
Action:
Severity: Info.
SCH5828
SNMP trap: No
ARP only authorized for CO Trunks.

Action:
Severity: Info.
SCH5829
SNMP trap: No
Maximum Dial Pulse time has to be greater than Minimum Dial Pulse time.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1893 of 2360

SCH5830
You cannot delete, add, and change a loop at the same time.
Action:
Severity:
SCH5831
SNMP trap: No
TSA not allowed while FTR = PHD. XFA prerequisite.

Action:
Severity: Info.
SCH5832
SNMP trap: No
BPO type not allowed for XEM.

Action:
Severity: Info.
SCH5833
SNMP trap: No
ARP only authorized for COT trunk.

Action:
Severity: Info.
SCH5834
SNMP trap: No
Maximum Dial Pulse Time has to be greater than the minimum Dial Pulse
Time.
Action:
Severity: Info.
SCH5835
SNMP trap: No
Minimum Hook Flash Time has to be greater than the minimum Dial Pulse
Time.
Action:
Severity: Info.
SCH5836
SNMP trap: No
Access code contains an invalid character.

Action:
Severity: Info.
SCH5837
SNMP trap: No
XPE package 203, SUPP package 131 or both packages are restricted.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1894 of 2360

SCH5838
No predefined table or customized table has yet been built for B34 Static Loss
Plan. This is a prerequisite for B34 Dynamic Loss Switching.
Action: Configure a table for B34 Static Loss Plan (TTYP = STAT) before
configuring a table for B#$Dynamic Load Switching.
Severity: Info.
SCH5839
SNMP trap: No
Action: Contact system distributor to request the LAPW package; otherwise,

log into the system using appropriate password which is authorized for
changes to "configuration data", or contact system distributor to have this data
updated.
Action:
Severity: Info.
SCH5840
SNMP trap: No
When entering a customized Static Loss Plan Table (Base Level Table) or a
customized Dynamic Loss Plan Table (Alternative Level Table), {cr} will not be
allowed if a table has not been previously installed.
Action: Enter all values for Rx and Tx or begin the command over and install a
standard Predefined table, then customize a few values as required.
Severity: Info.
SCH5841
SNMP trap: No
Wrong number of parameters have been entered.

Action: Enter two values, one for Rx, and the second for Tx (or enter {cr} only)
for all port types except RANR and PAGT. Enter one value for RANR (Rx) and
PAGT (Tx), or enter {cr} only.
Severity: Info.
SCH5842
SNMP trap: No
B34 Dynamic Loss Switching is disabled. B34 Codec Static Loss Downloading
is now in effect.
Action: Enter two values, one for Rx, and the second for Tx (or enter {cr} only)
for all port types except RANR and PAGT. Enter one value for RANR (Rx) and
PAGT (Tx), or enter {cr} only.
Severity: Info.
SCH5843
SNMP trap: No
The Table Number value entered is out-of-range.

Action: Enter a Table Number within the range, [1-25] for STYP, and [1-2] for
DTYP.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1895 of 2360

SCH5844
The coded Relative Input/Output Level (Rx or Tx) value is out-of-range.

Action: Enter correct ranges as follows:
Rx - (0 - 31)Tx - (8 - 39).
Severity: Info.
SCH5845
SNMP trap: No
Cannot change number of AOMs (KBA or KEM) because it deletes the BFS
key.
Action: Remove BFS key first.
Severity: Info.
SCH5846
SNMP trap: No
You answered YES to the DITI prompt, but the DID to TIE package 176 is
equipped. DID to TIE calls are restricted by the DID to TIE package.
Action:
Severity: Info.
SCH5847
SNMP trap: No
CNI slot 8, port 0 cannot be changed or deleted.

Action:
Severity: Info.
SCH5848
SNMP trap: No
The specified application is not configured on this MISP.

Action:
Severity: Info.
SCH5849
SNMP trap: No
BRI trunk types can only be TIE, COT, and DID.

Action:
Severity: Info.
SCH5850
SNMP trap: No
Cannot change these parameters without disabling all associated BRI trunk
members.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1896 of 2360

SCH5851
Interface type not valid for Basic Rate. This message indicates that the IFC
trunk entered does not support Basic Rate trunks.
Action:
Severity: Info.
SCH5852
SNMP trap: No
Cannot out BRIL application without disabling the application.

Action:
Severity: Info.
SCH5853
SNMP trap: No
Cannot out BRIL application without outing all the associated DSLs.
Action:
Severity: Info.
SCH5854
SNMP trap: No
The specified route is not a BRI route.

Action:
Severity: Info.
SCH5855
SNMP trap: No
BRIT package is not equipped.

Action:
Severity: Info.
SCH5856
SNMP trap: No
The new MISP for this card does not have BRIL configured, but there is a BRIL
DSL on this card.
Action:
Severity: Info.
SCH5857
SNMP trap: No
BRI route is not allowed if a BRI Route Packet Handler exists.

Action:
Severity: Info.
SCH5859
SNMP trap: No
A DSL trunk in NT mode must be associated with a route on NET side.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1897 of 2360

SCH5860
Protocol group cannot be removed. Remove the route(s) associated with this
protocol and try again.
Action:
Severity: Info.
SCH5861
SNMP trap: No
Cannot out BRIT application without disabling the application.

Action:
Severity: Info.
SCH5862
SNMP trap: No
Cannot out BRIT application without outing all the associated DSLs.
Action:
Severity: Info.
SCH5863
SNMP trap: No
The new MISP for this card does not have BRIT configured, but there is a BRIT
DSL on this card.
Action:
Severity: Info.
SCH5864
SNMP trap: No
BRIL package is not equipped.

Action:
Severity: Info.
SCH5865
SNMP trap: No
ISDN option needs to be configured in the Customer Data Block before a BRI
route can be configured.
Action:
Severity: Info.
SCH5866
SNMP trap: No
Either the BRIL or the BRIT package needs to be equipped.

Action:
Severity: Info.
SCH5867
SNMP trap: No
Line card is not a BRI SILC line card.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1898 of 2360

SCH5868
{CR} is not allowed at TNUM prompt.

Action: Enter a Table Number within the range,
[1-25] for STYP, and [1-2] for DTYP.
Severity: Info.
SCH5869
SNMP trap: No
Line card must be SILC for Numeris DSL.

Action:
Severity: Info.
SCH5870
SNMP trap: No
Warning: Another device is configured on the same card.

Action: Change the group number as well.
Severity: Info.
SCH5871
SNMP trap: No
Warning: There may be other devices on the QSDI card.

Action: Be sure the group number corresponds.
Severity: Info.
SCH5872
SNMP trap: No
NPID table does not exist.

Action:
Severity: Info.
SCH5873
SNMP trap: No
The NPID type cannot be entered because M911 package 224 is not
equipped.
Action:
Severity: Info.
SCH5874
SNMP trap: No
NPID table already exists.

Action: Use CHG command.
Severity: Info.
SCH5875
SNMP trap: No
NPID table does not exist.

Action: Use NEW command.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1899 of 2360

SCH5876
M911_NPID_MHPTR is Nil.
Action:
Severity: Info.
SCH5877
SNMP trap: No
NPID table out-of-range (0-7).

Action:
Severity: Info.
SCH5878
SNMP trap: No
All applications on the MSDL card are affected by the group number change.
Action:
Severity: Info.
SCH5889
SNMP trap: No
Entered a number outside of the range allowed for the parameter for NEW and
CPY commands in LD 18. The valid range is 1-100.
Action: Re-enter the NEW or CPY command with a new parameter between 1
and 100.
Severity: Info.
SCH5890
SNMP trap: No
Available memory is below the minimum allowed when trying to add multiple
speed call lists at once using the NEW and CPY commands in LD 18.
Minimum is 2048 words.
Action: Create the Speed Call lists one at a time, or free up additional memory.
Severity: Info.
SCH5891
SNMP trap: No
With X11 Release 19 and later, use one of the following formats for DN block
printing . multiple DNs may be printed by listing them at the DN prompt using
commas to separate the individual DNs
2. a range of DNs may be entered using a dash between the starting and
ending DNs
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1900 of 2360

SCH5892
Tried to disable B34 Static Loss Plan Download (SLPD) feature while B34
Dynamic Loss Switching (DLS) is still enabled. B34 SLPD not disabled.
Action: Disable B34 DLS before disabling B34 SLPD.
Severity: Info.
SCH5894
SNMP trap: No
1200 OHM termination impedance does not apply to EXUT.

Action:
Severity: Info.
SCH5896
SNMP trap: No
DWC key's DN does not match the ACD DN of the queue the agent is in.
Action:
Severity: Info.
SCH5897
SNMP trap: No
AWC key is already defined for this agent.

Action:
Severity: Info.
SCH5898
SNMP trap: No
DWC key is already defined for this agent.

Action:
Severity: Info.
SCH5899
SNMP trap: No
The appropriate DSL on this card (DSL #0 for PREF or DSL #1 for SREF) must
be a trunk DSL.
Action:
Severity: Info.
SCH5900
SNMP trap: No
The appropriate DSL on this card (DSL #0 for PREF or DSL #1 for SREF) is
not provisioned for a clock source.
Action:
Severity: Info.
SCH5901
SNMP trap: No
Either no card exists in this slot, or the slot must be a DTI2, JDMI, or PRI2 slot.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1901 of 2360

SCH5902
Either the card in this slot is not a BRI SILC line card, or the slot must be a
DTI2, JDMI, or PRI2 slot.
Action:
Severity: Info.
SCH5903
SNMP trap: No
Either DSL #1 in this slot is not a trunk DSL, or the slot must be a DTI2, JDMI,
or PRI2 slot.
Action:
Severity: Info.
SCH5904
SNMP trap: No
Either DSL #1 in this slot is not provisioned for a clock source, or the slot must
be a DTI2, JDMI, or PRI2 slot.
Action:
Severity: Info.
SCH5905
SNMP trap: No
The appropriate DSL on this card (DSL #0 for PREF or DSL #1 for SREF) is
not configured.
Action:
Severity: Info.
SCH5906
SNMP trap: No
Either DSL #1 in this slot is not configured, or the slot must be a DTI2, JDMI,
or PRI2 slot.
Action:
Severity: Info.
SCH5907
SNMP trap: No
The clock on this DSL is referenced in the Digital Data Block.

Action: This reference must be removed in LD 73 before the mode can be
changed to NT.
Severity: Info.
SCH5908
SNMP trap: No

Action: This reference must be removed in LD 73 before the CLOK can be
changed to NO on this DSL.
Severity: Info.
SNMP trap: No
System Messages
Page 1902 of 2360

SCH5909
The asterisk (*) is not a valid entry for this prompt.

Action:
Severity: Info.
SCH5910
SNMP trap: No
Cannot remove or change a 500 telephone if its DN is equal to ALDN of the

CDB.
Action: You must remove or change ALDN first.
Severity: Info.
SCH5911
SNMP trap: No
The Move function for the entered card input is temporarily denied due to
SET/TRK installation/relocation in process. The Move function will be
permitted as soon as the installation/relocation process is completed.
Action:
Severity: Info.
SCH5912
SNMP trap: No
NPD ID out-of-range (0-9).

Action:
Severity: Info.
SCH5913
SNMP trap: No
SNMP trap: No
Invalid NPA format.

Action:
Severity: Info.
SCH5914
Invalid response to TRMT prompt. Valid responses are NONE, TEST, FAIL,
NPA, or {CR}.
Action:
Severity: Info.
SCH5916
SNMP trap: No
{CR} not allowed as valid input for IDTB prompt for NEW command.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1903 of 2360

SCH5919

Action: This reference must be removed in LD 17 before the DSL can be outed.
Severity: Info.
SCH5923
SNMP trap: No
LAPW is not allowed without Multi-User Login (MULTI_USER) package 242.

Action:
Severity: Info.
SCH5924
SNMP trap: No
Duplicate login name entered.

Action:
Severity: Info.
SCH5925
SNMP trap: No
Username is mandatory prompt.

Action: Have to enter a valid user name.
Severity: Info.
SCH5926
SNMP trap: No
The clock on this DSL is referenced by the DTI2/PRI2 system data.

Action: This reference must be removed in LD 73 before the mode can be
changed to NT.
Severity: Info.
SCH5927
SNMP trap: No

Action: This reference must be removed in LD 73 before the CLOK can be
changed to NO on this DSL.
Severity: Info.
SCH5928
SNMP trap: No

Action: This reference must be removed in LD 73 before the DSL can be outed.
Severity: Info.
SCH5929
SNMP trap: No
DTI package is restricted.

Action: If the BRIT package is equipped, enter TYPE = DT12 or TYPE = PR12.
Severity: Info.
SNMP trap: No
System Messages
Page 1904 of 2360

SCH5930
The slot number is not a valid DTI/PRI/MISP slot.

Action:
Severity: Info.
SCH5931
SNMP trap: No
The slot number is not a valid DTI2/PRI2/MISP slot.

Action:
Severity: Info.
SCH5932
SNMP trap: No
This MISP is referenced as a clock controller in the Digital Data Block.

Action: This reference must be removed in LD 73 before the MISP can be outed.
Severity: Info.
SCH5933
SNMP trap: No
This MISP is referenced as a clock controller in the DTI2/PRI2 system data.

Action: This reference must be removed in LD 73 before the MISP can be outed.
Severity: Info.
SCH5936
SNMP trap: No
The CWNT package must be enabled to assign CWNA Class of Service to a

telephone.
Action:
Severity: Info.
SCH5937
SNMP trap: No
The M911 Package must be enabled to assign USMA Class of Service to a

telephone.
Action:
Severity: Info.
SCH5938
SNMP trap: No
The requested change cannot be processed because the route would be

changed to USR side, but there are NT mode DSL members on this route.
Action: NT mode DSLs must be on NET side.
Severity: Info.
SCH5939
SNMP trap: No
This is not an SILC card. This slot is valid input only for SILC clock references.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1905 of 2360

SCH5941
That feature is not included in this package.

Action:
Severity: Info.
SCH5942
SNMP trap: No
Autobaud overwrites configured baud rate.

Action:
Severity: Info.
SCH5943 x y
SNMP trap: No
MSDl SDI function conflicts with user type, the PARM setting or the BITL
setting. The first conflicting pair is shown. Where:
x = user type (e.g. APL, PMSI); DCE if MOD is specified; BITL if LME is
specified
y = MSDL SDI function (e.g. LME, ABD)
Action:
Severity: Info.
SCH5944
SNMP trap: No
DTE must be specified for a PRT device.

Action:
Severity: Info.
SCH5945
SNMP trap: No
MSDL SDI package is not equipped.

Action: Redefine the TTY/PRT on a non-MSDL SDI port.
Severity: Info.
SCH5952
SNMP trap: No
Cannot have more than one CSL for CCR VAS ID.
Action:
Severity: Info.
SCH5953
SNMP trap: No
Cannot take out CSL link that has a reverted DN.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1906 of 2360

SCH5957
At least one TRF user must be defined for a TTY or the History File.
Action:
Severity: Info.
SCH5958
SNMP trap: No
The primary PMSI port was removed in LD 17 (ADAN OUT xx). The
re-transmission, polling, and message monitoring will not be serviced.
Action:
Severity: Info.
SCH5959
SNMP trap: No
That port number is either undefined, or not a PMSI port.

Action:
Severity: Info.
SCH5960
SNMP trap: No
The input is beyond the allowed range for the PMCR prompt. The allowed
range is 5 to 250 or 25 percent of total system Call Registers, whichever is
less.
Action:
Severity: Info.
SCH5961
SNMP trap: No
Either the Ack timer (XTMR), or Polling timer (PTMR) is outside the range.
Action: Enter ranges XTMR = 0-6 and PTMR = 0-31.
Severity: Info.
SCH5962
SNMP trap: No
The number of re-transmission (XNUM) is outside the allowed range.

Action: Enter range of 0-4.
Severity: Info.
SCH5963
SNMP trap: No
The polling Call Register was not allocated during wrap-up time in LD 17.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1907 of 2360

SCH5964
The number of PMCRs will be recalculated because the number of system

Call Registers was reduced.
Action:
Severity: Info.
SCH5970
SNMP trap: No
MFX Class of Service requires a DID trunk.

Action:
Severity: Info.
SCH5971
SNMP trap: No
MFX Class of Service requires a IAO trunk.

Action:
Severity: Info.
SCH5973
SNMP trap: No
A link is removed from a Vas ID that is defined for one or more CDN.
Action: Provide a new link.
Severity: Info.
SCH5974
SNMP trap: No
Timer T2 should be smaller than T1.

Action:
Severity: Info.
SCH5975
SNMP trap: No
Timer T3 should be greater than T1 when T3 is not zero.

Action:
Severity: Info.
SCH5976
SNMP trap: No
Cannot remove the protocol group because at least one MPH network
interface or TSP refers to it.
Action: Remove the association of the protocol group from the MPH network
interface or the TSP.
Severity: Info.
SCH5977
SNMP trap: No
Meridian 1 Packet Handler package not included.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1908 of 2360

SCH5978
DNA/NTN does not exist in the table.

Action:
Severity: Info.
SCH5979
SNMP trap: No
DNA/NTN already exists in the system.

Action:
Severity: Info.
SCH5980
SNMP trap: No
The input TN has been used by another network interface.

Action:
Severity: Info.
SCH5981
SNMP trap: No
MPH maintenance B channel time slot request failed.

Action:
Severity: Info.
SCH5983
SNMP trap: No
DNA table does not exist.

Action:
Severity: Info.
SCH5984
SNMP trap: No
DNA table already exists.

Action:
Severity: Info.
SCH5986
SNMP trap: No
DNA/NTN has too many digits. NTN maximum size is 10 digits, or DNA
maximum is 14 digits.
Action:
Severity: Info.
SCH5987
SNMP trap: No
Local DNA tables overflow. NTN of TSP (USID) DSL (TN) will not be in the
local tables.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1909 of 2360

SCH5988
NTN does not exist in any DNA table associated with the MPH, or MPH
network interface.
Action:
Severity: Info.
SCH5989
SNMP trap: No
SNMP trap: No
DNA table overflows.

Action:
Severity: Info.
SCH5990
Only MPHI and OPE can be easy changed when MPHI = Yes.
Action:
Severity: Info.
SCH5991
SNMP trap: No
The input TN is used by D-channel packet data.

Action:
Severity: Info.
SCH5992
SNMP trap: No
The input MPH loop does not exist.

Action:
Severity: Info.
SCH5993
SNMP trap: No
Invalid entries for the LCN range

Action: Enter the lowest LCN first, then the highest.
Severity: Info.
SCH5994
SNMP trap: No
Invalid order of LCN range selection. The lowest LCN has to be larger than the
highest LCN of any configured LCN ranges.
Action:
Severity: Info.
SCH5995
SNMP trap: No
Cannot use this NTN because it is associated with a TSP.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1910 of 2360

SCH5996
The input DNA table is used by another MPH network interface or another
MISP.
Action:
Severity: Info.
SCH5997
SNMP trap: No
Exceed the maximum number if B-channel connections.

Action: Enter another available MPH loop number.
Severity: Info.
SCH5998
SNMP trap: No
DSL B channel call type is not IPD.

Action:
Severity: Info.
SCH6000
SNMP trap: No
NTN is not associated with a TSP.

Action:
Severity: Info.
SCH6001
SNMP trap: No
This LCN is not within the PVC range defined for the MPH network interface.
Action: Check the range again and re-enter an available LCN.
Severity: Info.
SCH6002
SNMP trap: No
The network interface is not configured for this MPH.

Action:
Severity: Info.
SCH6003
SNMP trap: No
SNMP trap: No
Not a MPH loop.

Action:
Severity: Info.
SCH6004
PVC connection does not exist.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1911 of 2360

SCH6005
Cannot remove this MISP because there is a PVC associated with it.
Action:
Severity: Info.
SCH6006
SNMP trap: No
The PVC connection is enabled only if the associated TSPs and network
interfaces are enabled.
Action:
Severity: Info.
SCH6008
SNMP trap: No
The DNIC of the table is different from the MPH DNIC.

Action: Enter another DNA table number.
Severity: Info.
SCH6009
SNMP trap: No
The input MCU has been used by another MISP.

Action:
Severity: Info.
SCH6010
SNMP trap: No
Cannot change the DNIC of a DNA table.

Action:
Severity: Info.
SCH6011
SNMP trap: No
The MPH application does not exist.

Action:
Severity: Info.
SCH6012
SNMP trap: No
Send maintenance pending message to the MPH application of loop X failed.

Action:
Severity: Info.
SCH6013
SNMP trap: No
The MPH application must be disabled.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1912 of 2360

SCH6015
The MCU had been referenced by another network interface.

Action:
Severity: Info.
SCH6016
SNMP trap: No
The input MCU has no MPHI option.

Action:
Severity: Info.
SCH6017
SNMP trap: No
Cannot change the IPD call type because a TSP is using B channel for MPH.
Action:
Severity: Info.
SCH6018
SNMP trap: No
Superloop must be entered as a multiple of 4.

Action:
Severity: Info.
SCH6020
SNMP trap: No
Exceed the maximum number of supported DNA tables for a network

interface.
Action:
Severity: Info.
SCH6024
SNMP trap: No
Invalid operation for TCON.

Action:
Severity: Info.
SCH6025
SNMP trap: No
Cannot change the TSP NTN because it is associated with a PVC connection.
Action:
Severity: Info.
SCH6026
SNMP trap: No
The tandem connection does not exist.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1913 of 2360

SCH6027
The MPH network interface does not exist.

Action:
Severity: Info.
SCH6028
SNMP trap: No
Cannot change the DNIC because the MISP is associated with a TSP.
Action:
Severity: Info.
SCH6029
SNMP trap: No
The input TN is not an MCU.

Action:
Severity: Info.
SCH6030
SNMP trap: No
The MPH network interface must be disabled.

Action:
Severity: Info.
SCH6031
SNMP trap: No
The input TN is not an M2008 telephone.

Action:
Severity: Info.
SCH6032
SNMP trap: No
A Meridian Packet Handler interface with MCU cannot be changed to a

non-MPHI MCU if the connection still exists in the software.
Action: Remove the connection in LD 27.
Severity: Info.
SCH6033
SNMP trap: No
The DSL must be disabled before changing the call type IPD or PMD.
Action:
Severity: Info.
SCH6034
SNMP trap: No
The terminal must be disabled.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1914 of 2360

SCH6035
Cannot remove the TSP because it is part of an existing PVC connection.

Action: Remove the PVC connection and try again.
Severity: Info.
SCH6036
SNMP trap: No
TN TRANS fails on MCU.

Action:
Severity: Info.
SCH6037
SNMP trap: No
Cannot add or change TSP for B-channel. The call type is not IPD, or the
associated DSL has TSPs configured for all B-channel packet data with MPH.
Action:
Severity: Info.
SCH6041
SNMP trap: No
Exceed the maximum number of nailed-up connections with BRSC and/or

MPH.
Action:
Severity: Info.
SCH6042
SNMP trap: No
Old NTN is not defined in local or DNA table.

Action:
Severity: Info.
SCH6043
SNMP trap: No
The selected LAPB protocol set group does not exist.

Action:
Severity: Info.
SCH6044
SNMP trap: No
The selected X25P protocol set group does not exist.

Action:
Severity: Info.
SCH6045
SNMP trap: No
Only two input fields are allowed.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1915 of 2360

SCH6046
Must enter a number to delete.

Action:
Severity: Info.
SCH6047
SNMP trap: No
Illegal shelf entry for the MCU.

Action:
Severity: Info.
SCH6048
SNMP trap: No
Input exceed the maximum limit of the D-channel TSP for the associated MPH.
Action:
Severity: Info.
SCH6049
SNMP trap: No
This TEI has been used by another TSP of the DSL.

Action:
Severity: Info.
SCH6050
SNMP trap: No
DNIC must have four digits.

Action:
Severity: Info.
SCH6052
SNMP trap: No
Must enter NTN number to delete.

Action:
Severity: Info.
SCH6053
SNMP trap: No
The DNA table is empty. It requires at least one NTN number.

Action:
Severity: Info.
SCH6054
SNMP trap: No
The application option must be BRI Line.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1916 of 2360

SCH6055
The DSL must be disabled in order to change the MPH loop.

Action:
Severity: Info.
SCH6056
SNMP trap: No
The NTN range is 2 to 32.

Action:
Severity: Info.
SCH6058
SNMP trap: No
Disconnect BCH nailed-up connection failed.

Action:
Severity: Info.
SCH6059
SNMP trap: No
The highest NTN input has more than 10 digits.

Action:
Severity: Info.
SCH6061
SNMP trap: No
Cannot change the state of the network interface(s).

Action:
Severity: Info.
SCH6062
SNMP trap: No
MCU cannot be a BRI card.

Action:
Severity: Info.
SCH6063
SNMP trap: No
Illegal card entry for MCU.

Action:
Severity: Info.
SCH6064
SNMP trap: No
Illegal unit entry for MCU.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1917 of 2360

SCH6065
This MISP has associated network interface(s).

Action:
Severity: Info.
SCH6066
SNMP trap: No
The old MPH link interface is not disabled.

Action:
Severity: Info.
SCH6067
SNMP trap: No
This MISP has associated D-channel terminal(s).

Action:
Severity: Info.
SCH6068
SNMP trap: No
Cannot add MPH application to this MISP. There is an associated BRSC.

Action:
Severity: Info.
SCH6069
SNMP trap: No
This MISP has an associated B-channel terminal(s).

Action:
Severity: Info.
SCH6070
SNMP trap: No
This MISP has dedicated connection(s) with BRSC and/or MPH.

Action:
Severity: Info.
SCH6071
SNMP trap: No
The input DNA table does not exist in any network interface.
Action:
Severity: Info.
SCH6072
SNMP trap: No
Cannot remove this DNA table because it is referenced by a PVC.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1918 of 2360

SCH6073
The reference DNA table does not exist.

Action:
Severity: Info.
SCH6074
SNMP trap: No
Cannot remove link from a Vas ID that is defined for one or more CDN at the
ADAN prompt.
Action:
Severity:
SCH6075
SNMP trap: No
Cannot add a Vas ID that has no link to a Control DN.

Action:
Severity:
SCH6076
SNMP trap: No
You cannot use an international interface for the ISA route.

Action:
Severity: Info.
SCH6077
SNMP trap: No
No TTY logical # is entered for STA administration terminal.

Action:
Severity: Info.
SCH6078
SNMP trap: No
No TTY logical # is entered for STA administration terminal.

Action:
Severity: Info.
SCH6079
SNMP trap: No
The STA administration terminal is not on MSDL.

Action:
Severity: Info.
SCH6080
SNMP trap: No
Disable the TTY before configuring as the STA administration terminal.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1919 of 2360

SCH6081
User types PMS, ACD, APL, HSL & PRT are not allowed on the TTY as the
STA administration terminal.
Action:
Severity: Info.
SCH6082
SNMP trap: No
One of the ports allocated for STA application is already used by other MSDL
application.
Action:
Severity: Info.
SCH6083
SNMP trap: No
The TTY is configured with an STA application. It cannot be removed until the
STA is removed.
Action:
Severity: Info.
SCH6084
SNMP trap: No
STA administration port cannot be removed using x.

Action:
Severity: Info.
SCH6085
SNMP trap: No
Unable to use changed parameters.

Action: To use the changed parameters, enable the STA application modified to
download.
Severity: Info.
SCH6086
SNMP trap: No
Cannot allocate protected or unprotected memory for STA configuration.

Action:
Severity: Info.
SCH6087
SNMP trap: No
The TTY has already been configured with another STA application.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1920 of 2360

SCH6088
Remove nonexistent port(s)

Action:
Severity: Info.
SCH6089
SNMP trap: No
The MSDL package, BRIL package or, BRIT package needs to be equipped.
Action:
Severity: Info.
SCH6090
SNMP trap: No
The system has automatically reset DLTN to NO because AUTO is equal to

YES (auto terminated).
Action:
Severity: Info.
SCH6092
SNMP trap: No
The M911 Package 224 must be equipped to accept USMA/USMD Class of

Service.
Action:
Severity: Info.
SCH6093
SNMP trap: No
The CWNT Package 225 must be equipped to accept CWNA/CWND Class of

Service.
Action:
Severity: Info.
SCH6094
SNMP trap: No
CDR NEW package is not equipped.

Action:
Severity: Info.
SCH6097
SNMP trap: No
A digital telephone must have CWNA Class of Service to be used as a Call

Waiting Notification TN.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1921 of 2360

SCH6098
The MPH application of the input MPH loop is in waiting state.

Action: Wait for the application to be uploaded or download. Disable the MPH
application.
Severity: Info.
SCH6100
SNMP trap: No
SNMP trap: No
Failed TN TRANS.
Action:
Severity: Info.
SCH6101
Protected loop pointer is NIL.

Action:
Severity: Info.
SCH6102
SNMP trap: No
SNMP trap: No
Not a valid PRI loop.

Action:
Severity: Info.
SCH6103
Either that channel is already used, or it is not a Packet Data channel.

Action:
Severity: Info.
SCH6104
SNMP trap: No
The route is not configured for Packet Data.

Action:
Severity: Info.
SCH6105
SNMP trap: No
Not configured for TCON.

Action:
Severity: Info.
SCH6106
SNMP trap: No
The outgoing TN is the same as the incoming TN.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1922 of 2360

SCH6107
The system nailed-up list is full.

Action:
Severity: Info.
SCH6108
SNMP trap: No
The BRI application running on this MISP can only support 3 line cards.
Action:
Severity: Info.
SCH6109
SNMP trap: No
There is more than 1 B-channel configured in the system. Non-dedicated

Meridian Packet Handlers can only support 1 B-channel interface.
Action:
Severity: Info.
SCH6110
SNMP trap: No
Cannot change this MISP to a dedicated MPH because there is (are) line
card(s) associated with it.
Action:
Severity: Info.
SCH6115
SNMP trap: No
The new MISP cannot accommodate all D-channel numbers from the
associated line card.
Action:
Severity: Info.
SCH6116
SNMP trap: No
The new MISP has different characteristics than the old MISP.
Action: Check DPSD and MPHC prompts.
Severity: Info.
SCH6117
SNMP trap: No
The dedicated MPH can not associated with any line card(s).
Action:
Severity: Info.
SCH6118
SNMP trap: No
SNMP trap: No
PVC connection exists.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1923 of 2360

SCH6119
DNAT database download failed.

Action:
Severity: Info.
SCH6120
SNMP trap: No
This LCN has been used.

Action:
Severity: Info.
SCH6121
SNMP trap: No
CHG request is not allowed for PVC connection.

Action:
Severity: Info.
SCH6122
SNMP trap: No
This LCN is not defined for the associated TSP.

Action:
Severity: Info.
SCH6123
SNMP trap: No
SNMP trap: No
PVC download failed.

Action:
Severity: Info.
SCH6124
MPH maintenance D-channel time slot request failed.

Action:
Severity: Info.
SCH6125
SNMP trap: No
B-channel TN cannot be located in MPH block.

Action:
Severity: Info.
SCH6126
SNMP trap: No
Free B-channel slot cannot be located in MPH block.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1924 of 2360

SCH6127
Cannot change the MPH loop because TSP still associated with this MPH.
Action:
Severity: Info.
SCH6128
SNMP trap: No
SNMP trap: No
Cannot get NWIF state.

Action:
Severity: Info.
SCH6129
MPH maintenance network interface time slot request failed.

Action:
Severity: Info.
SCH6130
SNMP trap: No
Previous B-channel must be disabled in order to change.

Action:
Severity: Info.
SCH6131
SNMP trap: No
Warning: All active calls that use the changed X25P group will be dropped.
Action:
Severity: Info.
SCH6132
SNMP trap: No
Failed to send Customer Data Block Call Data Recording message.

Action:
Severity: Info.
SCH6133
SNMP trap: No
MPH interface database download failed.

Action:
Severity: Info.
SCH6134
SNMP trap: No
Send MPH TSP disable message failed.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1925 of 2360

SCH6135
MPH maintenance B channel interface change state failed.

Action:
Severity: Info.
SCH6136
SNMP trap: No
Cannot change the TSP terminal type because the MPH DNIC are not the
same.
Action:
Severity: Info.
SCH6137
SNMP trap: No
The MPH is configured with more than 3 dedicated connections with BRSC
and/or MISP.
Action:
Severity: Info.
SCH6138
SNMP trap: No
The associated BRSC is not set up for D-channel packet data with MPH.
Action:
Severity: Info.
SCH6139
SNMP trap: No
The associated MISP is not set up for D-channel packet data with MPH.
Action:
Severity: Info.
SCH6140
SNMP trap: No
Cannot find SAPI16 TN in the MPH loop block.

Action:
Severity: Info.
SCH6141
SNMP trap: No
All keys on the MCU are removed when MPHI is changed to YES.
Action:
Severity: Info.
SCH6155
SNMP trap: No
Cannot configure BRSC on this IPE shelf because the total number of DPSD
TSPs on this shelf will exceed the limit that an MPH can handle.
Action: Delete some DPSD TSPs first.
Severity: Info.
SNMP trap: No
System Messages
Page 1926 of 2360

SCH6156
Cannot associate the BRSC with this MPH because the total number of DPSD
TSPs the MPH will handle will exceed the limit.
Action: Delete some DPSD TSPs first or use another MPH.
Severity: Info.
SCH6157
SNMP trap: No
Cannot NEW/CHG DSL or TSP of this ISDN BRI line card because it has no
MISP/BRSC association.
Action: Configure a BRSC in the IPE shelf or perform a CHG CARD command
to associate the line card with a MISP first.
Severity: Info.
SCH6158
SNMP trap: No
User type FIL excludes MTC, SCH, BUG, and CSC User types.
Action: Remove the conflicting user types before configuring FIL.
Severity:
SCH6161
SNMP trap: No
Using CHG or MOV command is not permitted when the application type is
DPNSS.
Action: Use LD 74 to modify any DPNSS protocol or transmission parameter.
Severity: Info.
SCH6162
SNMP trap: No
This logical port number is already used by another DPNSS1, DASS2 or

APNSS link defined with a non MSDL card.
Action: Find a vacant logical port number.
Severity: Info.
SCH6163
SNMP trap: No
This DPNSS logical port number does not exist.

Action:
Severity: Info.
SCH6164
SNMP trap: No
DTSL data structures still exist. Remove the DTSL data structures in LD 74
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1927 of 2360

SCH6166
There is no digital trunk output buffer defined.

Action: Load LD 17 and define the number of digital trunk output buffers.
Initialize the system to effect the change.
Severity: Info.
SCH6167
SNMP trap: No
The following hardware modifications cannot be done by using this command:

DCHI to MSD, MSDL to DCH, DCHX to MSDL, MSDL to DCHX.
Action: Remove the existing data structures and reconfigure the link with the
desired hardware type.
Severity: Info.
SCH6168
SNMP trap: No
This logical port number (dpnss link number) has not been defined in LD 74.
Action:
Severity: Info.
SCH6169
SNMP trap: No
The DPNSS link number entered is already used by a DPNSS link on a nonMSDL card.
Action: Change the link number to a vacant one.
Severity: Info.
SCH6174
SNMP trap: No
The TN is currently being used as a Call Waiting Notification TN, and therefore
CWND Class of Service is not allowed.
Action:
Severity: Info.
SCH6178
SNMP trap: No
Feature is not defined in TSP (FEATID) database.

Action:
Severity: Info.
SCH6179
SNMP trap: No
Feature input is invalid or not recognized.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1928 of 2360

SCH6180
No FA/FI IDs input.

Action:
Severity: Info.
SCH6181
SNMP trap: No
Feature ID is out-of-range.
Action:
Severity: Info.
SCH6182
SNMP trap: No
FI ID input conflicts with FI ID of another feature.

Action:
Severity: Info.
SCH6183
SNMP trap: No
FA ID input conflicts with FA ID of another feature.

Action:
Severity: Info.
SCH6184
SNMP trap: No
Warning: the feature input is already defined in the database. The input FA/FI
IDs will overwrite the existing FA/FI IDs for the feature.
Action:
Severity: Info.
SCH6185
SNMP trap: No
Wrong number of input fields. Only two or three input fields are expected.
Action:
Severity: Info.
SCH6187
SNMP trap: No
There are Feature IDs defined in the TSP(s) of this DSL.

Action: Delete the Feature IDs before changing the Protocol ID to other
protocols.
Severity: Info.
SCH6191
SNMP trap: No
BRSC card TN cannot be 0.

Action: Configure the BRSC at slot 1 to 15 of loop 0 shelf 0.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1929 of 2360

SCH6193
Application(s) are not configured on the MISP.

Action: Select an MISP with the application or configure the MISP with the
application.
Severity: Info.
SCH6194
SNMP trap: No
Invalid LTID: LTG and LTN cannot be both 0.

Action: Re-enter with LTG or LTN greater than 0.
Severity: Info.
SCH6195
SNMP trap: No
BRSC-MPH interface must be disabled first.

Action: Disable the SAPI16 interface between the BRSC and the MPH MISP in
LD 32.
Severity: Info.
SCH6196
SNMP trap: No
Cannot add or change the card type UILC because there are 8 UILCs
configured on this IPE shelf already.
Action: Configure the card as SILC, or put it in another shelf.
Severity: Info.
SCH6197
SNMP trap: No
Cannot add or change the card type SILC because there are 15 SILCs
configured on this IPE shelf already.
Action: Configure the card as UILC, or put it in another shelf.
Severity: Info.
SCH6198
SNMP trap: No
Cannot Move or Swap a BRSC card.

Action: Enter an appropriate TN.
Severity: Info.
SCH6199
SNMP trap: No
BRSC card is not EI & USI allowed for this command.

Action: Enter an appropriate TN.
Severity: Info.
SNMP trap: No
System Messages
Page 1930 of 2360

SCH6200
The BRSC must be disabled first.

Action: Disable the BRSC in LD 32.
Severity: Info.
SCH6201
SNMP trap: No
Input is not a BRSC card TN.

Action: Enter a BRSC card TN. For PRT command, you can enter {cr}, loop, or
loop shelf.
Severity: Info.
SCH6202 slot
SNMP trap: No
Card slot is configured. Where: slot = all available slots in the IPE shelf.
Action: Configure the BRSC in one of the slots listed.
Severity: Info.
SCH6203 tn
SNMP trap: No
A BRSC (tn) is configured in the IPE shelf.

Action: Configure the BRSC in another IPE shelf.
Severity: Info.
SCH6204 tn
SNMP trap: No
Disable BRI line cards (tn) first before adding a BRSC or removing.
Action: Disable all line cards listed in LD 32.
Severity: Info.
SCH6205
SNMP trap: No
Cannot use MPH for DPSD because at least one DSL on the same IPE shelf
has a LTEI pair defined.
Action: Remove all LTIDs or use a PRI B channel for accessing the Packet
Switched Data Network(PSDN).
Severity: Info.
SCH6206
SNMP trap: No
Cannot use PRI Channel for DPSD connection because at least one DSL on
the same IPE shelf has a DPSD TSP defined.
Action: Remove all DPSD TSPs or use MPH for accessing the Packet Switched
Data Networking (PSDN).
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1931 of 2360

SCH6207
Cannot add a BRSC to this MISP. MISP has MPH application configured.
Action: Pick another MISP without MPH application or remove the application.
Severity: Info.
SCH6208
SNMP trap: No
Cannot add a BRSC to this MISP. MISP has maximum number of BRSCs
configured.
Action: Pick another MISP.
Severity: Info.
SCH6209
SNMP trap: No
Cannot add a BRSC to this MISP. MISP has too many LC configured.
Action: Pick another MISP, or remove some line cards and disable the MISP.
Severity: Info.
SCH6210
SNMP trap: No
The MISP must be disabled first. It was programmed to handle 4 line cards.
Action: Disable the MISP in LD 32.
Severity: Info.
SCH6211
SNMP trap: No
The MISP must be disabled first. It was programmed to handle 3 line cards and
1 BRSC.
Severity: Info.
SCH6212
SNMP trap: No
The MISP must be disabled first. It was programmed to handle 2 line cards and
8 BRSCs.
Severity: Info.
SCH6213
SNMP trap: No
Cannot add a BRSC to this MISP because it does not have MPH application
configured.
Action: Pick another MISP with MPH application, or configure the MISP with
MPH application first.
Severity: Info.
SNMP trap: No
System Messages
Page 1932 of 2360

SCH6214
Cannot add a BRSC to this MPH MISP because it has the maximum number
of SAPI16 connections configured.
Action: Pick another MPH MISP or remove one SAPI 16 connection from this
MPH MISP first.
Severity: Info.
SCH6215
SNMP trap: No
There are DSLs with both LTIDs and TSPs for D-channel PSD configured.
Action: If D-channel PSD is going to be provided and MPH is used, remove all
configured LTIDs. If D channel PSD is going to be provided and an external
packet handler is used, remove all configured TSPs for D-channel PSD.
Otherwise, remove all LTID pairs and TSPs for D-channel PSD.
Severity: Info.
SCH6216
SNMP trap: No
There are DSLs with TSPs for D-channel PSD configured.

Action: Remove the TSPs for DPSD first.
Severity: Info.
SCH6217
SNMP trap: No
There are DSLs with LTIDs for D-channel PSD configured.

Action: Remove the LTIDs first.
Severity: Info.
SCH6218
SNMP trap: No
Cannot remove the MISP because at least one BRSC is associated with it.
Action: Disassociate the BRSCs by deleting them or change their Layer 3 MISP.
Severity: Info.
SCH6219
SNMP trap: No
Cannot add BRI line card to this MISP because it has the maximum number
of line cards configured.
Action: Add a BRSC to the IPE shelf, delete some line cards, or use another
MISP.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1933 of 2360

SCH6220
Cannot remove or modify a BRSC because background maintenance task is

in progress.
Action: Wait until the task is done or disable the BRSC in LD 32, then repeat the
command.
Severity: Info.
SCH6222
SNMP trap: No
The USR key must be removed before changing the telephone's Class of
Service to DTA.
Action:
Severity: Info.
SCH6224
SNMP trap: No
Another user is already accessing that TN.

Action:
Severity: Info.
SCH6225
SNMP trap: No
Another user is already accessing that DN.

Action:
Severity: Info.
SCH6226
SNMP trap: No
A telephone with an ACD key cannot be assigned CCSA Class of Service.

Action:
Severity: Info.
SCH6227
SNMP trap: No
A telephone with CCSA Class of Service, or non-zero SCI cannot be assigned

an ACD key.
Action:
Severity: Info.
SCH6228
SNMP trap: No
ITPP=YES and METR=XPXX are incompatible.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1934 of 2360

SCH6229
ARFW package is not equipped.

Action:
Severity: Info.
SCH6230
SNMP trap: No
Input is not a valid RAN route.

Action: When reprompted for RANR, a valid RAN route should be entered.
Severity: Info.
SCH6231
SNMP trap: No
Too many digits entered for DGTS.

Action: When reprompted for DGTS, the correct number of digits should be
entered.
Severity: Info.
SCH6232
SNMP trap: No
The interface type entered is incompatible with a CTYP of DCHI or SPDC. The
CTYP must be MSDL. (To replace current version)
Action:
Severity: Info.
SCH6233
SNMP trap: No
The OHAS DN index is illegal. There is no ODN defined for it in LD 15.

Action: Check and enter a legal index.
Severity: Info.
SCH6234
SNMP trap: No
A legal OHID index must be defined to have ASCA Class of Service.

Action:
Severity: Info.
SCH6235
SNMP trap: No
A legal FSVC index must be defined to have ASCA Class of Service.

Action:
Severity: Info.
SCH6236
SNMP trap: No
No legal ODNs are defined in LD 15.

Action: Define the ODN before assigning indices.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1935 of 2360

SCH6240
A telephone cannot use an ODN that is to be deleted.

Action: Be sure the deleted ODN is not used by any telephone.
Severity: Info.
SCH6242
SNMP trap: No
Signaling must be standard when Equal Access toll call restrictions have been
enabled for this route. (EQAR = Yes).
Action: Remove the Equal Access toll call restrictions have bee enabled for this
route. (EQAR = Yes).
Severity: Info.
SCH6243
SNMP trap: No
DTI TIE routes must be voice only when Equal Access toll call restrictions
have been enabled for this route. (EQAR = Yes).
Action: Remove the Equal Access toll call restrictions for this route by setting
EQAR to No prior to changing the voice and data calls type.
Severity: Info.
SCH6245
SNMP trap: No
That TN is not available.

Action: Use another one.
Severity: Info.
SCH6246
SNMP trap: No
Cannot build/tear down the tandem connection.

Action: Check the PRI status.
Severity: Info.
SCH6247
SNMP trap: No
Cannot remove this TIE trunk because there is a tandem connection

associated with it.
Action: Remove the tandem connection, then remove the trunk.
Severity: Info.
SCH6252
SNMP trap: No
The MOV DCH command is not supported by Option 11.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1936 of 2360

SCH6253
ISLD/VNS/VNSA user modes are not supported by the option 11

downloadable D-channel feature. Only shared modes SHA and SHAV can be
used, as well as PRA and PRI.
Action:
Severity: Info.
SCH6261
SNMP trap: No
The PNI number just entered is the same PNI number as currently
programmed
Action:
Severity: Info.
SCH6262
SNMP trap: No
% Maximum of 100 steps are allowed only.

Action:
Severity: Info.
SCH6264
SNMP trap: No
The ISA service route cannot be removed because there are calls active on
that route.
Action:
Severity: Info.
SCH6265
SNMP trap: No
Digits for insertion may be an invalid DN.

Action:
Severity: Info.
SCH6266
SNMP trap: No
This DN cannot be removed from the Group Hunt list as it belongs to a set
being relocated; moreover, the list cannot be outed, or resized down as to
exclude this DN.
Action:
Severity: Info.
SCH6267
SNMP trap: No
This DN cannot be added to a Group Hunt list as it also belongs to a set being
relocated.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1937 of 2360

SCH6268
The response entered is not valid for the current ISDN IFC.
Action:
Severity: Info.
SCH6269
SNMP trap: No
IFC (CNTY) does not correspond to the given DGTP.

Action:
Severity: Info.
SCH6270
SNMP trap: No
Incorrect PWD2 password entered. Access to Loss Planning Data is not

allowed.
Action:
Severity: Info.
SCH6271
SNMP trap: No
DLSA is disabled. If any B34/B39 cards in the system, SLPD installation

procedures must follow.
Action:
Severity: Info.
SCH6272
SNMP trap: No
Start Arrangement for L1 signaling must be SEZA or PTSD.

Action:
Severity: Info.
SCH6273
SNMP trap: No
Start Arrangement for RON/TRON signaling must be RT.

Action:
Severity: Info.
SCH6274
SNMP trap: No
Only LDR signaling is allowed for TIE trunk on XDID.

Action:
Severity: Info.
SCH6275
SNMP trap: No
The number of Meridian 1 Packet Handler Digital Subscriber Loops (DSLs) in

the system has reached the limit.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1938 of 2360

SCH6276
Warning: External DN of IDC tree not stored in corresponding SDID tree to

prevent overwriting existing value. This inconsistency occurs in the SDID tree
when more than one external DN terminates on the same internal DN in the
IDC tree.
Action:
Severity: Info.
SCH6278
SNMP trap: No
Value out-of-range for TABL prompt. Accepted values are 0-15

Action: Check the customer documentation on TDS tone tables.
Severity: Info.
SCH6279
SNMP trap: No
Overlay code is compressed, but the decoding table does not exist.
Action:
Severity: Info.
SCH6280
SNMP trap: No
Class of Service HSPA and TSA are exclusive.

Action:
Severity: Info.
SCH6281
SNMP trap: No
KD3 package not equipped.

Action:
Severity: Info.
SCH6282
SNMP trap: No
CLS cannot be configured as MFK TN is DID and DTI2.

Action:
Severity: Info.
SCH6283
SNMP trap: No
Overlay 16 - Warning - MFK Outgoing table will be cleared. Route members

should not have MFK CLS if there is no incoming MFK table.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1939 of 2360

SCH6284
Overlay 16 - Warning - MFK Incoming table will be cleared. Route members

should not have MFK CLS if there is no outgoing MFK table.
Action:
Severity: Info.
SCH6285
SNMP trap: No
Overlay 16 - Attempt to mark a non-digital, non-DID route as MFK5 or MFK6

type of signaling.
Action:
Severity: Info.
SCH6290
SNMP trap: No
The CLS DPDT or DTDP can be configured on routes with ICOG IAO only.
Action: Check trunk configuration.
Severity: Info.
SCH6291
SNMP trap: No
The CLS DPDT or DTDP can be configured on analog DID or TIE trunks only.
Action: Check trunk configuration.
Severity: Info.
SCH6303
SNMP trap: No
Password must be entered, cr is not a valid input.

Action:
Severity: Info.
SCH6304
SNMP trap: No
Password entered is too long. Maximum length is 8 digits.

Action:
Severity: Info.
SCH6305
SNMP trap: No
Attendant RCFW password can only consist of digits between 0 and 9.

Action:
Severity: Info.
SCH6307
SNMP trap: No
The Voice Mailbox Administration application block does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1940 of 2360

SCH6308
The Voice Mailbox already exists.

Action:
Severity: Info.
SCH6309
SNMP trap: No
The Voice Mailbox does not exist.

Action:
Severity: Info.
SCH6310
SNMP trap: No
The Voice Mailbox Administration package is not equipped.

Action:
Severity: Info.
SCH6311
SNMP trap: No
The VAS block cannot be removed because the application is configured.

Action:
Severity: Info.
SCH6312
SNMP trap: No
Warning: Delete is full. Failed to send delete message to Meridian Mail or

Voice Mailbox was not deleted on Meridian Mail.
Action:
Severity: Info.
SCH6313
SNMP trap: No
SNMP trap: No
Package is restricted.
Action:
Severity: Info.
SCH6314
Unexpected input type.

Action: Check input type for the prompt.
Severity: Info.
SCH6315
SNMP trap: No
Inaccessible data for CFPD user.

Action: User is allowed to enter CFN or PWD as input for this type prompt.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1941 of 2360

SCH6316
VMB is already configured on VAS VASID.

Action:
Severity: Info.
SCH6321
SNMP trap: No
There are still Voice Mailboxes configured.

Action:
Severity: Info.
SCH6322
SNMP trap: No
The Voice Mailbox Administration application is already configured.

Action:
Severity: Info.
SCH6323
SNMP trap: No
The Voice Mailbox Administration application is not yet configured.

Action:
Severity: Info.
SCH6324
SNMP trap: No
The Voice Mailbox Administration application must be disabled before it can

be removed.
Action:
Severity: Info.
SCH6325
SNMP trap: No
The Voice Mailbox Administration application has already been configured on

another VAS link.
Action:
Severity: Info.
SCH6336
SNMP trap: No
Out-of-Service unit only valid for NEW and OUT commands.

Action:
Severity: Info.
SCH6337
SNMP trap: No
The specified card does not exist, so the unit cannot be marked
Out-of-Service.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1942 of 2360

SCH6338
Invalid card density on a superloop.

Action:
Severity: Info.
SCH6339
SNMP trap: No
ECHG of TIMP/BIMP only supported on XOPS card. In addition, TIMP/BIMP

are not supported on the XOPS card when the CHINA package is equipped.
Action:
Severity: Info.
SCH6340
SNMP trap: No
Invalid combination of TIMP/BIMP specified. Supported combinations are:

600/600 (only when CLS = ONS) 900/900 600/3COM 900/3COM
600/3CM 900/3CM2
Action:
Severity: Info.
SCH6341
SNMP trap: No
You do not have access to Loss Planning data.

Action:
Severity: Info.
SCH6355
SNMP trap: No
Loop cannot be added to the DCH because the maximum number of loops is
already defined.
Action:
Severity: Info.
SCH6357
SNMP trap: No
Interface change is not allowed for UIPE D-channels.

Action:
Severity: Info.
SCH6358
SNMP trap: No
Interface change is not allowed for UIPE D-channels.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1943 of 2360

SCH6359
Backup DCH is not supported by the primary D-channel.

Action:
Severity: Info.
SCH6360
SNMP trap: No
DCH move is not supported for UIPE D-channels.

Action:
Severity: Info.
SCH6372
SNMP trap: No
MR value cannot be changed.

Action: Disable all trunks of the route first.
Severity: Info.
SCH6374
SNMP trap: No
This response is only allowed when CDRX = NO in LD 16.

Action:
Severity: Info.
SCH6375
SNMP trap: No
This DN is an OHOL DN. Only one 2/500 set can exist, and all other members
must be M2616 sets and have CLS DELA.
Action:
Severity: Info.
SCH6376
SNMP trap: No
Set must be M2616 with CLS DELA.

Action:
Severity: Info.
SCH6377
SNMP trap: No
CLS DELD is invalid when set has LSPK key configured or a DN or HOT KEY
configured with an OHOL DN (mixed appearance with 2/500 set with CLS
SPKA).
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1944 of 2360

SCH6379
Attempt to configure a non conference or non XCT loop as a dealer or spare

dealer loop.
Action:
Severity: Info.
SCH6380
SNMP trap: No
Spare dealer conference loop already configured in the system. Only one
spare dealer loop can exist per system.
Action:
Severity: Info.
SCH6382
SNMP trap: No
SLPD or DLS tables have to removed before setting NATP prompt to YES.
Action:
Severity: Info.
SCH6383
SNMP trap: No
NATP is disable and another pad functionality (static pad downloading, DLS
or SLPD) has to be enable for XFEM, XFCOT or XDID cards on the system.
Action:
Severity: Info.
SCH6386
SNMP trap: No
Input TN cannot mix route type with TCNZ interface.

Action:
Severity: Info.
SCH6387
SNMP trap: No
Cannot get enough protected memory to build Advice of Charge Start of Call
(AOCS) structures. AOCS supplementary service may not work properly.
Action: A possible solution is to remove some metered trunks, or to switch to
AOCD or, AOCE supplementary services. If the messages output in LD 16, the
member number of the first trunk for which the problem occurred is printed out.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1945 of 2360

SCH6388
ALT language database could not be loaded during previous disk OS start-up.
Only help messages will be displayed in the alternate language (Option 81
only).
Action: Refer to messages issued during the previous restart for the reason why
the alternate language database was not loaded. Correct the errors and do a
warm start.
Severity: Info.
SCH6389
SNMP trap: No
Cannot get enough protected memory to build Advice of Charge During the
Call (AOCD) structures. AOCD supplementary service may not work properly.
Action: A possible solution is to remove some metered trunks, or to switch to
AOCE supplementary services. If the message is output in LD 16, the member
number of the first strnk for which the problem occurred is printed out.
Severity: Info.
SCH6390
SNMP trap: No
Cannot get enough protected memory to build Advice of Charge End of Call
(AOCE) structures. AOCE supplementary service may not work properly.
Action: A possible solution is to remove some metered trunks. If the message is
output in LD 16, the member number of the first trunk for which the problem
occurred is printed out.
Severity: Info.
SCH6391 lll
SNMP trap: No
Only PBX TNs can be configured on a phantom loop using Overlay 10.
Action:
Severity: Info.
SNMP trap: No
SCH6392 lll mmm Do not copy, move, or swap between phantom and non-phantom loops.
Action:
Severity: Info.
SCH6393
SNMP trap: No
Phantom DNs must be defined and unique.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1946 of 2360

SCH6394
This prompt, Class of Service, or feature cannot be configured on a phantom

TN.
Action:
Severity: Info.
SCH6395
SNMP trap: No
This prompt, Class of Service, or feature cannot be configured on a

non-phantom TN.
Action:
Severity: Info.
SCH6396
SNMP trap: No
Warning: A Phantom TN has been configured without a CFW or DCFW DN.

Action:
Severity: Info.
SCH6398
SNMP trap: No
There are PVCs configured associated with the BRI line cards.
Action: Remove PVCs in order to change line cards, BRSC or MPH data.
Severity: Info.
SCH6399
SNMP trap: No
MTRO Keyword table is corrupted.

Action:
Severity: Info.
SCH6400
SNMP trap: No
XOPS can only be configured on XOPS card or unconfigured card. This is due
to wiring differences between XOPS and other analog line cards.
Action:
Severity: Info.
SCH6401
SNMP trap: No
Companding law chosen in INTN prompt to download to Peripheral Equipment

in LD 97 is different from the PCML setting in the configuration record in LD 17.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1947 of 2360

SCH6402
This NTN does not associate to the PVC MPH.

Action:
Severity: Info.
SCH6403
SNMP trap: No
The SCDR package is not equipped.

Action:
Severity: Info.
SCH6404
SNMP trap: No
No other user types can be entered with MTC while XSM is yes.
Action: Due to the XSM hardware requirement, remove the XSM TTY
configuration before you configure new users.
Severity: Info.
SCH6405
SNMP trap: No
Class of service only valid for WRLS=YES.

Action: Change WRLS to YES.
Severity: Info.
SCH6406
SNMP trap: No
WRLS only available on superloop (IPE) shelf.

Action: Make sure that the CMRC and/or CMCC are on an IPE shelf.
Severity: Info.
SCH6407
SNMP trap: No
CLS DTN must be used if WRLS=YES.

Action: Change CLS to DTN if WRLS is YES.
Severity: Info.
SCH6409
SNMP trap: No
A protocol engine active (inactive) interface type is only allowed to be changed

to another protocol engine inactive (active) interface type only if there is no
DSL associated with the route (Overlay 16).
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1948 of 2360

SCH6410
The route entered for BRIE APPL must have the protocol engine active; the
route entered for BRIT APPL should not have the protocol engine active
(Overlay 27).
Action:
Severity: Info.
SCH6411
SNMP trap: No
MPH application doesn't co-exist any other applications in a MISP card

(Overlay 27).
Action:
Severity: Info.
SCH6412
SNMP trap: No
The new MISP for this card does not have BRIE configured, but there is a
BRIE DSL on this card (Overlay 27).
Action:
Severity: Info.
SCH6413
SNMP trap: No
Cannot have IPE shelf with BRSC and trunk DSLs. When command is NEW
BRSC, TN of Line Card with Trunk DSLs is printed. When command is NEW
DSL, TN of BRSC is printed (Overlay 27).
Action:
Severity: Info.
SCH6414
SNMP trap: No
ITNA option cannot be disabled when DGRP is defined.

Action:
Severity: Info.
SCH6415
SNMP trap: No
DGRP is out-of-range. Valid DGRP is from 1-5.

Action:
Severity: Info.
SCH6416
SNMP trap: No
Last AST key cannot be deleted when ITNA=YES.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1949 of 2360

SCH6417
ITNA option must be enabled and DGRP must be defined if a TN is configured

on a BCS phantom loop.
Action:
Severity: Info.
SCH6418
SNMP trap: No
ITNA option is not supported for an ACD agent or supervisor.

Action:
Severity: Info.
SCH6419
SNMP trap: No
A BCS TN with ITNA=YES is not allowed to be copied to another TN.

Action:
Severity: Info.
SCH6420
SNMP trap: No
Only BCS TN can be configured on BCS Phantom Loop via Overlay 11.
Action:
Severity: Info.
SCH6428
SNMP trap: No
Cannot delete this Call Forwarding unconditional service because it is

activated now.
Action:
Severity: Info.
SCH6429
SNMP trap: No
Cannot subscribe Call Forwarding unconditional for this call type because DN
does not subscribe this call type.
Action:
Severity: Info.
SCH6430
SNMP trap: No
ACD Agent or Supervisor cannot be configured on a BCS Phantom Loop.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1950 of 2360

SCH6431
Data block cannot be moved or swapped because either the source or

destination loop is a BCS phantom loop.
Action:
Severity: Info.
SCH6432
SNMP trap: No
CSL package is not equipped.

Action:
Severity: Info.
SCH6433
SNMP trap: No
Standalone Mail Package is not equipped.

Action:
Severity: Info.
SCH6434
SNMP trap: No
Could not add Standalone Meridian Mail server TN to server table.

Action:
Severity: Info.
SCH6435
SNMP trap: No
Supplementary service is not defined in the database.

Action:
Severity: Info.
SCH6436
SNMP trap: No
Invalid supplementary service.

Action:
Severity: Info.
SCH6437
SNMP trap: No
There are supplementary services defined in the TSP (s) of this DSL.
Action:
Severity: Info.
SCH6439
SNMP trap: No
To enable force, set RTQT to 0. To enable RTQT, set force to no.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1951 of 2360

SCH6440
Can only create phantom superloops on vacant superloops.

Action:
Severity: Info.
SCH6441
SNMP trap: No
Cannot change an existing phantom superloop since there is no data

associated to a phantom superloop to be changed.
Action:
Severity: Info.
SCH6442
SNMP trap: No
SBR package 281 is required.

Action:
Severity: Info.
SCH6443
SNMP trap: No
Must have SBRA Class of Service defined.

Action:
Severity: Info.
SCH6450
SNMP trap: No
3wt requires DID trunk type.

Action:
Severity: Info.
SCH6451
SNMP trap: No
Reminder: The lampaudit has been turned off. The message will be printed
once every hour until the lampaudit is turned on.
Action:
Severity: Info.
SCH6453
SNMP trap: No
VNS information still used, cannot be removed.

Action:
Severity: Info.
SCH6454
SNMP trap: No
PSP not allowed for an XUT or EXUT.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1952 of 2360

SCH6455
BAT/ARF/LBS were entered at the same time.

Action:
Severity: Info.
SCH6456
SNMP trap: No
PIP/PSP/BST STYP entered for an XCOT.

Action:
Severity: Info.
SCH6457
SNMP trap: No
BBTS is not supported by this card type.

Action:
Severity: Info.
SCH6458
SNMP trap: No
JCO was entered for a trunk that that was not configured as a loop start, an
XUT/EXUT, or the Japan Central Office Trunks (JPN) package 97 was not
enabled.
Action:
Severity: Info.
SCH6459
SNMP trap: No
No parameters entered for SYTP when SUPN was changed from NO to YES.
Action:
Severity: Info.
SCH6460
SNMP trap: No
Warning: An SCPW must be defined for this set.

Action:
Severity: Info.
SCH6461
SNMP trap: No
The ADMINSET package must be equipped.

Action:
Severity: Info.
SCH6462
SNMP trap: No
Service not allowed for this set type.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1953 of 2360

SCH6463
Invalid character.
Action: SBA passwords must consist of digits only.
Severity: Info.
SCH6464
SNMP trap: No
At least one option must be allowed.

Action:
Severity: Info.
SCH6465
SNMP trap: No
Option not allowed for this access level.

Action:
Severity: Info.
SCH6466
SNMP trap: No
Warning: Disallowed Installer level options have been cleared.

Action:
Severity: Info.
SCH6467
SNMP trap: No
DRA is only allowed for DTI2 routes (DGTP=DTI2 in LD 16)

Action:
Severity: Info.
SCH6469
SNMP trap: No
Warning: Equal Access toll call restriction was specified for this route, but no
Equal Access toll calls were restricted.
Action: Either set EQAR to NO, or set one of the Equal Access toll call
sequences to Deny (NTOL or ITOL).
Severity: Info.
SCH6471
SNMP trap: No
No trailing blanks/spaces can be entered after the DN.

Action: Re-enter the DN correctly followed by carriage return.
Severity: Info.
SCH6473
SNMP trap: No
Cannot access the MARP TN for the current "MARP on TN l s c u" message
when adding or changing a DN.
Action: Check the DN block and try the DN change again later.
Severity: Info.
SNMP trap: No
System Messages
Page 1954 of 2360

SCH6474
This TYPE not allowed a repeat count for NEW input.

Action:
Severity: Info.
SCH6475
SNMP trap: No
Warning: The route being removed is the recorder route for Malicious Call
Trace. Removing this route will cause the recorder to not be conferenced into
the call when Malicious Call Trace is activated (unless a new recorder route is
defined and MCRT in Overlay 15 is changed).
Action: Define a new recorder route and redefine MCRT in LD 15, or set RECD
to NO in LD 15.
Severity: Info.
SCH6477
SNMP trap: No
Events: BRI Supplementary Service is using this CallType.

Action: Delete the BRI Supplementary Service that is using this CallType in this
DN before CallType can be changed.
Severity: Info.
SCH6478
SNMP trap: No
AHNT DN can be defined only if CLS=RTDA, or RBDA or RBHA.

Action: Define CLS= RTDA, RBDA or RBHA before defining AHNT.
Severity: Info.
SCH6479
SNMP trap: No
AEHT DN can be defined only if CLS=CFTA and at least one or RTDA or

RBDA or RBHA.
Action: Define CLS = CFTA and at least of RTDA or RBDA or RBHA before
defining AEHT.
Severity: Info.
SCH6480
SNMP trap: No
You cannot configure a CHG key without the Charge Account for CDR (CHG)
package 23.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1955 of 2360

SCH6481
The card density of the source card (TN) and the destination card (TOTN) are
different. The density of the destination card is used for the unit being moved.
Action:
Severity: Info.
SCH6482
SNMP trap: No
CIST package 221 should be equipped. (Used for CLS= DNAA or DNAD,
when package is not equipped).
Action: Equip CIST package 221 or choose another answer.
Severity: Info.
SCH6483
SNMP trap: No
The number of M1 CT2 Mobility TNs in the system exceeded the number
defined in the tape directory.
Action:
Severity: Info.
SCH6484
SNMP trap: No
Do not remove ACD DN when DN still exists on some supervisor's NSVC key.
Action:
Severity: Info.
SCH6486
SNMP trap: No
AFD can be defined only if CLS=RTDA or RBDA or RBHA.

Action: Define CLS RTDA or RBDA or RBHA before defining AFD.
Severity: Info.
SCH6487
SNMP trap: No
AEFD DN can be defined only if CLS=CFTA and at least one of RTDA or

RBDA or RBHA.
Action: Define CLS = CFTA RTDA, or RDBA, or RBHA before defining AEFD.
Severity: Info.
SCH6488
SNMP trap: No
If CLS=HTA and RTDA or RBDA or RBHA, then AHNT must be defined.

Action: Define AHNT for the TN.
Severity: Info.
SNMP trap: No
System Messages
Page 1956 of 2360

SCH6489
If CLS=HTA CFTA and any one of RTDA or RBDA or RBHA then AEHT must
be defined.
Action: Define AEHT for the TN.
Severity: Info.
SCH6490
SNMP trap: No
Cannot use "X" to delete AFD/AHNT/AEFD/AEHT DN.

Action: Change to CLS RTDD to remove AFD/AHNT/AEFD/AEHT.
Severity: Info.
SCH6491
SNMP trap: No
Start minute or end/hour/minute for alternate time option not defined.

Action: Define all 4 fields that include the start hour, minute, and hour and end
minute for the CRT x prompt.
Severity: Info.
SCH6494
SNMP trap: No
List number already defined as Group Hunt list.

Action:
Severity: Info.
SCH6495
SNMP trap: No
Warning: 0 means the Station Control Passwords will no longer be required for
User Level Access to Set Based Administration
Action:
Severity: Info.
SCH6496
SNMP trap: No
Overlay 35 is no longer supported for this machine type.

Action: Replace Overlay 35 with Overlay 135.
Severity: Info.
SCH6497
SNMP trap: No
TYPE = PWR only allowed for REQ=NEW or OUT.

Action:
Severity: Info.
SCH6498
SNMP trap: No
PVR, PVN do not allow multiple appearance DN.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1957 of 2360

SCH6504
Illegal billing number length change.

Action: If length is changed, a new billing number is required.
Severity: Info.
SCH6505
SNMP trap: No
FFC and NFCR packages must be equipped.

Action:
Severity: Info.
SCH6507
SNMP trap: No
CDTI2 prompt was answered with YES but this causes some discrepancy - the
type of adjacent loop on the same common equipment shelf's card slot is
unsuitable (it may be only DTI2 or undefined). CDTI2 is reprompted. This case
is not relevant for Option 11. DCE1 is reprompted.
Action: Check the adjacent loop type (by CFN printing in LD 22) and, perhaps,
precise loop definitions in LD 17.
Severity: Info.
SCH6508
SNMP trap: No
An attempt to define an unsuitable loop on the common equipment shelf's card

slot, on which there is already a CIS DTI or CDTI2 card defined.
Action: The second loop to be defined on such a card slot must be DT12 only.
Severity: Info.
SCH6509 cnty
SNMP trap: No
Invalid IFC/CNTY combination. This message may indicate that a user has
entered an APISDN CNTY for EURO IFC, or an EURO CNTY for the APISDN
IFC.
Action:
Severity: Info.
SCH6510
SNMP trap: No
The Collect Call Blocking (CCB) package 290 is not enabled.

Action: Equip CCB package and reload if CCB is required.
Severity: Info.
SCH6511
SNMP trap: No
Route changed to OGT. CCB is set to NO.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1958 of 2360

SCH6512
Route type changed to ICT. CCBA is set to NO.

Action:
Severity: Info.
SCH6514
SNMP trap: No
NFCR must = YES in the customer data block.

Action:
Severity: Info.
SCH6515
SNMP trap: No
At attempt to define a digital trunk on CDTI2 with CISFW = YES in a route

which is neither ICOG = OGT (and TYPE = COT) nor ICOG = ICT (and
TKTP=DID).
Action: Check the route data block definition and change it if necessary in LDs
21 and 16.
Severity: Info.
SCH6516
SNMP trap: No
An attempt to define SIGL = CIS in LD 14 for analog trunk on IPE CIS three
wire trunks card in the route which is neither ICOG = OGT nor ICOG = ICT
(and TYPE = DID).
Action: Check the route data block definition and change it if necessary by LDs
21 and 16.
Severity: Info.
SCH6517
SNMP trap: No
An attempt to define a signaling related CLS's other than DIP/DIPF in LD 14

for a digital trunk on CDTI2/CSDTI2 with CISFW= YES.
Action: Enter CLS = DIP / DIPF or check CDTI2 prompt in Ld 73 for given loop.
Severity: Info.
SCH6520
SNMP trap: No
Valid BTD Table is in the range from 0 to 7.

Action: Enter a number from 0 to 7.
Severity: Info.
SCH6521
SNMP trap: No
Valid Cadence Phase length is in the range from 0 to 1500 milliseconds.

Action: Enter a number from 0 to 1500.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1959 of 2360

SCH6522
Two BTD Phases must be entered to describe the cadence.

Action: Enter values for two phases.
Severity: Info.
SCH6523
SNMP trap: No
If the first BCAD phase is 0, both phases must be 0.

Action: Enter 0 for both phases.
Severity: Info.
SCH6524
SNMP trap: No
BTD package must be equipped.

Action: Add Busy Tone Detection Tone (BTD) package 294.
Severity: Info.
SCH6525
SNMP trap: No
BTD table 0 cannot be removed

Action:
Severity: Info.
SCH6526
SNMP trap: No
BTD table must be defined in Overlay 97.

Action: Configure table in overlay 97 first.
Severity: Info.
SCH6527
SNMP trap: No
Required BTD table does not exist.

Action: Check if correct BTD number has been entered.
Severity: Info.
SCH6528
SNMP trap: No
NI2 is entered at the IFC prompt in LD 16 or LD 17. However, North America

National ISDN Class II Equipment (N12) package 291 is not equipped.
Action: Equip package 291 and reload if NI2 Primary Rate interface is required.
Severity: Info.
SCH6529
SNMP trap: No
Digital Trunk Type (DGTP) must be PRI for NI2 interface.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1960 of 2360

SCH6533
DN is already defined.
Action: The PINX DN should be a nonexisting DN selected in the customer's
numbering plan.
Severity: Info.
SCH6534
SNMP trap: No
The Speed Call list specified is not defined.

Action: Define the Speed Call list in LD 18 or input an existing Speed Call list
number.
Severity: Info.
SCH6535
SNMP trap: No
BAT/ARF/LBS STYP requires an XCOT.

Action:
Severity: Info.
SCH6536
SNMP trap: No
The response TAT is not allowed if Trunk Antitromboning (TAT) package 312
is not equipped. RCAP is reprompted.
Action: Equip Package 312 and reload to enter TAT feature.
Severity: Info.
SCH6537
SNMP trap: No
The response TAT is allowed for only D100 / SL-1 / S100 / D250 and Release
21 or higher for SL-1.
Action: Check the IFC and RLS prompts.
Severity: Info.
SCH6538
SNMP trap: No
The response TAT is not allowed if the card type (CTYP) is non-MSDL. RCAP
is re-prompted.
Action: In LD 22, check the CTYP prompt.
Severity: Info.
SCH6542
SNMP trap: No
ADL feature must be equipped for BNRA Class of Service. Class of Service is
changed to BNRD.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1961 of 2360

SCH6543
FFC and ADL packages must be equipped.

Action:
Severity: Info.
SCH6544
SNMP trap: No
Two-star (**) and/or four-star (****) abort is not allowed during the critical
sessions of adding (NEW), changing (CHG) or deleting (OUT) the data.
Action: To abort the session, enter carriage return for each prompt, except SLV3
and SLV6 prompts. For SLV3 and SLV6 prompts, enter NXX and SUB responses
respectively.
Severity: Info.
SCH6548
SNMP trap: No
Invalid Privacy Indicator entered for DTPI or DPPI prompt.

Action:
Severity: Info.
SCH6549
SNMP trap: No
CLBA/CLBD is not allowed if Calling Party Privacy (CCP) package 301 is not
equipped.
Action:
Severity: Info.
SCH6550
SNMP trap: No
CPNW list already exists for this customer

Action:
Severity: Info.
SCH6551
SNMP trap: No
CPNW list does not exist for this customer

Action:
Severity: Info.
SCH6552
SNMP trap: No
ISDN package 145 is needed for CPNW feature

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1962 of 2360

SCH6553
Warning: Adjacent loop is a DTI2 loop defined as being on a CDTI2 card. This
loop must be defined in LD 73 as CDTI2=YES or the adjacent loop must be
changed to CDTI2=NO.
Action:
Severity: Info.
SCH6554
SNMP trap: No
Warning: Adjacent loop is DTI2 loop with CDTI2 prompt defined differently
from this loop. Such a discrepancy must be removed by defining the same
CDTI2 value for the adjacent loop.
Action:
Severity: Info.
SCH6575
SNMP trap: No
.REMOTE_IPE_I is not equipped.

Action:
Severity: Info.
SCH6576
SNMP trap: No
Missing LCRI S/W from disk.

Action:
Severity: Info.
SCH6577
SNMP trap: No
Cannot change SUPT in the defined superloop.

Action:
Severity: Info.
SCH6578
SNMP trap: No
File I/O: error string - database access error.

Action:
Severity: Info.
SCH6579
SNMP trap: No
Conf: error string - configuration error.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1963 of 2360

SCH6583
China Attendant Monitor Package (CHINA) package 285 is not equipped.

Options AMA/AMD/TOA/TOD cannot be entered in LD 15.
Action: Equip package 285 and re-load if Attendant Monitor is required.
Severity: Info.
SCH6592
SNMP trap: No
Warning: Table has been removed. Using Overlay 20, ensure that this BTD
table is not assigned to any trunk card.
Action: Print out blocks using Overlay 20 and check BTDT number.
Severity: Info.
SCH6593
SNMP trap: No
BTS is not supported on Japan trunks and is no longer required.

Action:
Severity: Info.
SCH6594
SNMP trap: No
BTS is only supported on CO trunks with loopstart signaling.

Action:
Severity: Info.
SCH6595
SNMP trap: No
IFC type and Loop type mismatch. This message may indicate that a user has
entered a PRI loop as DCHL for a PRI2 IFC, or visa-versa.
Action:
Severity: Info.
SCH6596
SNMP trap: No
When updating SDID tree after the change in the IDC tree, a SDID tree branch
is found missing, which indicates there was an inconsistency between the
SDID and the IDC tree.
Action: Process as normal. The inconsistency is removed automatically.
Severity: Info.
SCH6597
SNMP trap: No
Invalid input for NATP.

Action: 1. Enter YES for North American Transmission Plan. 2. Enter NO for
other transmission plans.
Severity: Info.
SNMP trap: No
System Messages
Page 1964 of 2360

SCH6598
FLEN must not be less than the length of the longest SDRR plus the length of
the SPN.
Action:
Severity: Info.
SCH6601
SNMP trap: No
The ALRM_FILTER package is restricted.

Action: The requested action is denied.
Severity: Info.
SCH6602
SNMP trap: No
System Event List is empty.

Action:
Severity: Info.
SCH6605
SNMP trap: No
SNMP trap: No
Duplicate event.
Action:
Severity: Info.
SCH6606
Escalate must be less than suppress.

Action:
Severity: Info.
SCH6607
SNMP trap: No
Event not in Event Preference Table.

Action:
Severity: Info.
SCH6608
SNMP trap: No
SNMP trap: No
SNMP trap: No
Invalid escalate.
Action:
Severity: Info.
SCH6609
Invalid event id.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 1965 of 2360

SCH6610
Invalid new size; out of valid range.

Action:
Severity: Info.
SCH6611
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Invalid severity.
Action:
Severity: Info.
SCH6612
Log resize aborted.

Action:
Severity: Info.
SCH6613
Log resize failed.

Action:
Severity: Info.
SCH6614
Missing event id.

Action:
Severity: Info.
SCH6615
New suppress threshold is out of valid range.

Action:
Severity: Info.
SCH6616
SNMP trap: No
Suppress must be greater than the maximum escalate value in the event
preference table (EPT).
Action:
Severity: Info.
SCH6617
SNMP trap: No
Timer value is out of valid range.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1966 of 2360

SCH6618
Event Preference Table (EPT) is full.

Action:
Severity: Info.
SCH6619
SNMP trap: No
Call Park data block number out of range. The valid range is 1-5.
Action: Enter valid input.
Severity: Info.
SCH6620
SNMP trap: No
Trying to create a Call Park Block that already exists.

Action: Enter a Call Park Block that has not been
Severity: Info.
SCH6621
SNMP trap: No
Trying to change/out/print a data block that does not exist.

Action: Enter a Call Park Block that is defined in the customer database.
Severity: Info.
SCH6622
SNMP trap: No
Mutually exclusive supervision types entered.

Action:
Severity: Info.
SCH6623
SNMP trap: No
Must create data block 0 before creating other data blocks.

Action:
Severity: Info.
SCH6624
SNMP trap: No
Trying to remove the Primary Call Park Block before all the Secondary Call
Park Blocks have been removed.
Action: Remove all the Secondary Call Park Blocks first.
Severity: Info.
SCH6627
SNMP trap: No
ARDL package is not equipped (Overlay 11, 16, 81).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1967 of 2360

SCH6628
ARDL feature is not allowed for SL-1 and ARIES sets only (Overlay 11).
Action:
Severity: Info.
SCH6634
SNMP trap: No
This DN cannot be used as it would create an illegal multiple appearance of

the data DN of a dynamic voice/data TN.
Action:
Severity: Info.
SCH6635
SNMP trap: No
DTM key could not assigned with current set configuration. The DTM key has
been removed.
Action:
Severity: Info.
SCH6636
SNMP trap: No
Only one DTM key is allowed per TN.

Action:
Severity: Info.
SCH6638
SNMP trap: No
PGND/PGNA is not a valid input. The PAGENET package is not equipped.

Severity: Info.
SCH6639
SNMP trap: No
PTU Package not equipped.

Action: Equip PTU package and reload if PTU package is required.
Severity: Info.
SCH6640
SNMP trap: No
Cannot change agent ID mode (AID) to "no" if MQA option is enabled. MQA
option must be disabled first.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1968 of 2360

SCH6641
Cannot remove an ADS block if the MQA option is enabled first, which requires
the MAX HSL to be disabled.
Action:
Severity: Info.
SCH6642
SNMP trap: No
The MQA option cannot be changed ("yes" to "no" or "no" to "yes") if the High
Speed is up.
Action:
Severity: Info.
SCH6643
SNMP trap: No
The Report Control OPtion cannot be disabled if MQA agents belong to the
queue.
Action:
Severity: Info.
SCH6644
SNMP trap: No
An MQA agent has logged into this queue since the Report Control option
(RPRT) was changed. Since this option cannot be disabled when MQA agents
are serving the queue, the option is reset to its original value ("yes").
Action:
Severity: Info.
SCH6645
SNMP trap: No
Only one ADS block per system can have MQA enabled.
Action:
Severity: Info.
SCH6646
SNMP trap: No
A pilot DN of USE=SLCU (Speed Call List User) cannot be a member of the

Speed Call list it accesses.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1969 of 2360

SCH6647
The ACD DN specified is not compatible with MQA. Specifically, one of the
following is true for the ACD DN specified: IVMS, IMS, IVR, or DAL is enabled,
or RPRT is disabled. This message is just a warning. The ACD DN specified
will be assigned to the agent, but the agent set can no longer be an MQA ACD
agent.
Action:
Severity: Info.
SCH6649
SNMP trap: No
Cause: VNS DN ALREADY DEFINED

The response cannot be accepted because at least one VDN is already
defined in another VDN block, Impact: the response is not accepted and
VNDN is prompted again. Output data: no output data.
Action: Check which VDNs are already defined and configure blocks of DNs
without them.
Severity: Info.
SCH6650
SNMP trap: No
Missing FNET L/W/ from disk.

Action:
Severity: Info.
SCH6651
SNMP trap: No
Missing FPEC L/W from disk.

Action:
Severity: Info.
SCH6652
SNMP trap: No
The superloop specified is not configured as a Fiber Remote superloop.

Action:
Severity: Info.
SCH6653
SNMP trap: No
TN on Phantom DTI2 loop must be TIE or DID.

Action: Restart LD 14 and answer TIE to the prompt TYPE, or answer the
prompt TN by choosing a loop which is not defined as a Phantom DT12 loop.
Severity: Info.
SNMP trap: No
System Messages
Page 1970 of 2360

SCH6654
Cannot move a TN located on a Phantom DTI2 loop.

Action: Restart the LD14 and answer NEW to the prompt REQ, or answer the
jprompt TN by choosing a loop which is not defined as a Phantom DT12 loop.
Severity: Info.
SCH6655 n
SNMP trap: No
Error during the ISPC trunk configuration.

Where n = the error cause -1. ISPC Reference number already exists. In
Overlay 14, in answer to the prompt SREF, an ISPC reference number which
is already configured for the system, is not allowed.
2. The trunk must be a TIE trunk.
3. The trunk must be configured with the DTN class of service.
4. Data corruption with the route pointer.
5. The route is not an ISL route 6. The trunk is not a DID trunk. 7. The route
is not configured with DSEL=DTA.
8. The route must not be an ISL route.
9. The route is not configured with DLTN=YES
10. The route is not configured as incoming.
11. The route is not configured with PRDL=BSY
12. The route is not configured with DTD=YES
13. The route is not configured as outgoing.
14. The route is not configured with NEDC+ETH
15. The route is not configured with FEDC=ETH
16. The route is not configured with CPDC=NO
17. DDD_PACKAGE is restricted.
Action: Check the validity of the SPC reference number provided by the
telecommunication administration.
Severity: Info.
SCH6656
SNMP trap: No
The ISPC package 313 is mandatory to configure a Phantom DTI2 loop.

Action: Enable the ISPC Package 313 and reload thPBX if Phantom DT12 loop
is required.
Severity: Info.
SCH6657
SNMP trap: No
You are not allowed to create more than one TN at the time on a Phantom
DTI2 loop.
Action: To configure more than one TN on a Phantom DT12 loop, complete the
command sequence in LD 14 for each additional TN.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1971 of 2360

SCH6658
Service change is not allowed on unit currently involved in a Broadcast call.

Action:
Severity: Info.
SCH6659
SNMP trap: No
CLID entry no defined for the customer.

Action:
Severity: Info.
SCH6660
SNMP trap: No
Service change is not allowed on this TN since it is currently pending for a login
or logout event.
Action:
Severity: Info.
SCH6661
SNMP trap: No
Request to create a DISA block for the customer is not allowed because the
customer already has 240 DISA Blocks defined.
Action:
Severity: Info.
SCH6662
SNMP trap: No
This set type cannot have the FLXA class of service.

Action:
Severity: Info.
SCH6663
SNMP trap: No
A DTM key cannot be on key 00.

Action:
Severity: Info.
SCH6664
SNMP trap: No
The FLXA class of service is required for a voice TN on a high unit or a data
TN on a low unit.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1972 of 2360

SCH6665
The VDN block does not exist. In overlay 79, the VDN entered at the prompt
VNDN is not accepted when the request is OUT, DIS, or ENL.
Action: Enter a correct value, which must be the first VDN of an existing VDN
block.
Severity: Info.
SCH6666
SNMP trap: No
The maximum number of VDN's for a customer has been exceeded. The
FLXA class of service is required for a voice TN on a high unit or a data TN on
a low unit.
Action: Re-enter a number for your VDN block which does not exceed your
customer limit.
Severity: Info.
SCH6667
SNMP trap: No
The change is not accepted because VNS calls are still using this D-channel.
Action: All calls using this D-channel must be cleared before VNS parameters
of the D-channel can be modified.
Severity: Info.
SCH6668
SNMP trap: No
Card 0 not supported in this overlay.

Action:
Severity: Info.
SCH6670
SNMP trap: No
QSIGGF package is restricted.

Action:
Severity: Info.
SCH6672
SNMP trap: No
Master Mode package is restricted.

Action:
Severity: Info.
SCH6678
SNMP trap: No
Supervised DIDs: JDID requires Japan Trunk Package (97), loop start
signaling and XUTJ pack.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1973 of 2360

SCH6679
Warning: Key 0 is assigned to be SCR by default in model set data.

Action:
Severity: Info.
SCH6680
SNMP trap: No
Only JDID and BTS CLS are allowed for Loopstart DID trunks.
Action:
Severity: Info.
SCH6681
SNMP trap: No
CPK is not a legal response because the release ID at the far end is below Rls
22 or the interface type of the D-channel is not SL1.
Action: Change the release ID or change the interface type.
Severity: Info.
SCH6682
SNMP trap: No
CPK is not a legal response because the package, CPRKNET, is not

equipped.
Action: Change the package restriction.
Severity: Info.
SCH6683
SNMP trap: No
The position ID cannot be changed while this agent is acquired.

Action:
Severity: Info.
SCH6685
SNMP trap: No
NAC is not a valid RCAP; BRI route IFC configuration is not SL1.
Action:
Severity: Info.
SCH6686
SNMP trap: No
RCAP is changed to XNAC due to incompatible IFC configuration.

Action:
Severity: Info.
SCH6687
SNMP trap: No
NAC is not a valid RCAP. The D-channel IFC configuration is not SL1; or RLS
configuration is less than 22.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1974 of 2360

SCH6688
RCAP is changed to XNAC due to incompatible RLS configuration.

Action:
Severity: Info.
SCH6689
SNMP trap: No
Customer option is changed to CPD due to Call Park database

memory allocation problem.
Action:
Severity: Info.
SCH6690
SNMP trap: No
FLXA class of service is allowed only on Aries sets connected to XDLC cards.
Action:
Severity: Info.
SCH6691
SNMP trap: No
The associated DSLs must be removed before changing the BRIT route
interface type to ISGF or ESGF.
Action:
Severity: Info.
SCH6698
SNMP trap: No
There is a conflict in the configuration of RCAP and NASA, ie. if RCAP's CPK
is set, then NASA is not allowed to be defined as "NO".
Action: Change either configuration as needed.
Severity: Info.
SCH6699
SNMP trap: No
CAB number out of range.

Action:
Severity: Info.
SCH6700
SNMP trap: No
SNMP trap: No
Invalid TTY_TYPE.
Action:
Severity: Info.
SCH6701
Only 1 TTY allowed per fibre expansion cabinet.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1975 of 2360

SCH6704
Only 3 TTYs with TTY_TYPE LSL may be configured.

Action:
Severity: Info.
SCH6705
SNMP trap: No
SNMP trap: No
Invalid FLOWTYPE.
Action:
Severity: Info.
SCH6706
Invalid FLOWTYPE for Low Speed Link on Card 0.

Action:
Severity: Info.
SCH6707
SNMP trap: No
LSL and XLSL not valid on Option 11C.

Action:
Severity: Info.
SCH6708
SNMP trap: No
Low speed link not allowed on Card 0 Port 0.

Action:
Severity: Info.
SCH6709
SNMP trap: No
CLID block is not defined in the Customer Data Block.

Action:
Severity: Info.
SCH6710
SNMP trap: No
A warning message. CLID Entry is not defined n the CLID block of the
Customer Data Block. The CLID Entry is stored in the database.
Action:
Severity: Info.
SCH6711
SNMP trap: No
No trailing blanks/spaces can be entered after the CLID entry.

Action: Enter {CR} after the CLID entry.
Severity: Info.
SNMP trap: No
System Messages
Page 1976 of 2360

SCH6712
The input for the CLID entry should be an integer or a "D" .

Action:
Severity: Info.
SCH6713
SNMP trap: No
Cannot decrease CLID table size. Entries to be removed are not empty.
Action: Remove the unnecessary CLID entries first. Then decrease the CLID
table entry size.
Severity: Info.
SCH6714
SNMP trap: No
CLID Entry or Entries are not defined since the entry or entries are not
configured.
Action:
Severity: Info.
SCH6720
SNMP trap: No
One or more of the packages to operate the OPEN_ALARM feature is missing.

This feature requires the following packages MAT, ALARM_FILTER and
OPEN_ALARM.
Action:
Severity: Info.
SCH6721
SNMP trap: No
The value of the ZQUAT (QoS Unnacceptable Alarm Threshold) must be

lower than the ZQWAT (QoS Warning Alarm Threshold).
Action: Enter a lower value for ZQUAT or a higher value for ZQWAT.
Severity: Info.
SCH6722
SNMP trap: No
Digit Insertion function does not support SPRE/FFC digits.

Action: Users may dial manually.
Severity: Info.
SCH6723
SNMP trap: No
Cannot out a DCH/DSL while there are call-independent connections on the

DCH/DSL interface.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1977 of 2360

SCH6755
CLID entry D is not allowed to be assigned to all the DN keys on the set.
Action: Assign a non-D CLID entry to the DN key of the BCS set.
Severity: Info.
SCH6756
SNMP trap: No
WARNING: you have defined an IP set without NUID, directly on Secondary

CS. This set must be defined also on Primary CS, otherwise the phone will be
registered on Secondary CS and will affect Secondary CS state transition.
Action: Define the set on Primary. CS also.
Severity: Info.
SCH8782
SNMP trap: No
PIP/PSP not available without MR or SUPP. (This message only applies to

X11 Release 19 and earlier)
Action:
Severity: Info.
SCH8783
SNMP trap: No
The monitored or monitoring set cannot be moved or copied.

Action:
Severity: Info.
SCH8785
SNMP trap: No
An invalid TN has been entered for the Busy/Forward Status (BSF) key.
Action:
Severity: Info.
SCH8786
SNMP trap: No
The monitored set is on a different customer.

Action:
Severity: Info.
SCH8788
SNMP trap: No
The monitored set may not have an ACD-DN.

Action:
Severity: Info.
SCH8790
SNMP trap: No
The telephone is already monitored by 16 other telephones.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1978 of 2360

SCH8791
Monitored telephone cannot be BRI.

Action:
Severity: Info.
SCH8796
SNMP trap: No
SAR data does not exist.

Action:
Severity:
SCH8798
SNMP trap: No
RPE2 data block has not been created by LD 52.

Action:
Severity: Info.
SCH8799
SNMP trap: No
Operation not allowed.

Action: Remove loop from RPE2 group. Use LD 52.
Severity: Info.
SCH8802
SNMP trap: No
Illegal answer to prompt TASK.

Action:
Severity: Info.
SCH8803
SNMP trap: No
SNMP trap: No
Group is spared.
Action:
Severity: Info.
SCH8804
Command is NEW and group exists.

Action:
Severity: Info.
SCH8805
SNMP trap: No
Command is CHG or OUT and group does not exist.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1979 of 2360

SCH8806
{CR} only allowed for PRT on GRP prompt.

Action:
Severity: Info.
SCH8807
SNMP trap: No
Command is not NEW and RPE2 data does not exist.

Action:
Severity: Info.
SCH8811
SNMP trap: No
CORP/CORX can only be configured on 2.0 Mb digital CO trunks if the

International Supplementary Features (SUPP) package 131 and the DTI2
package 129 are equipped.
Action:
Severity: Info.
SCH8813
SNMP trap: No
Group Hunt pilot DN function is not supported.

Action:
Severity:
SCH8814
SNMP trap: No
PLDN entered is invalid.

Action:
Severity:
SCH8815
SNMP trap: No
PLDN size is out-of-range.

Action:
Severity:
SCH8816
SNMP trap: No
SNMP trap: No
Customer is undefined.
Action:
Severity:
SCH8817
PLDN package is unequipped.

Action:
Severity:
SNMP trap: No
System Messages
Page 1980 of 2360

SCH8818
TN translation has failed.

Action:
Severity:
SCH8819
SNMP trap: No
Unable to obtain a PDS/UDS.

Action:
Severity:
SCH8820
SNMP trap: No
The DN entered is not valid for the GHT list.

Action:
Severity:
SCH8821
SNMP trap: No
The LIST TYPE does not match REQ TYPE.

Action:
Severity:
SCH8822
SNMP trap: No
The associated PLDN must be removed first.

Action:
Severity:
SCH8824
SNMP trap: No
The PLDN and GHT customer numbers do not match.

Action:
Severity:
SCH8825
SNMP trap: No
The DN must first be removed from the GHT list.

Action:
Severity:
SCH8826
SNMP trap: No
The GHT list is already associated with another PLDN.

Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1981 of 2360

SCH8827
PLDN USE and LIST TYPE do not match.

Action:
Severity:
SCH8830
SNMP trap: No
The LAPW account was found to be corrupt and cannot be used.

Action: Get the system administrator to remove the account and re-enter it.
Severity: Info.
SCH8831
SNMP trap: No
A corrupt LAPW account was removed.

Severity: Info.
SCH8832
SNMP trap: No
Cannot remove logged on password.

Action:
Severity: Info.
SCH8833
SNMP trap: No
Only administrator is allowed to print audit trail.

Action:
Severity: Info.
SCH8834
SNMP trap: No
The occupied buffer area is larger than the requested size and therefore
cannot be reduced.
Action: Print buffer first.
Severity: Info.
SCH8835
SNMP trap: No
Invalid LAPW password option selected.

Action:
Severity: Info.
SCH8836
SNMP trap: No
Password has print-only Class of Service.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1982 of 2360

SCH8837
Audit Trail buffer size must be 50-1000 and divisible by 50.

Action:
Severity: Info.
SCH8839
SNMP trap: No
User is restricted from printing Speed Call List.

Action:
Severity: Info.
SCH8840
SNMP trap: No
Feature is not available without LAPW package.

Action:
Severity: Info.
SCH8841
SNMP trap: No
User does not have access to this data.

Action:
Severity: Info.
SCH8842
SNMP trap: No
Valid password must be entered.

Action:
Severity: Info.
SCH8843
SNMP trap: No
Only 32 CUSTOMER TENANT combinations are allowed.

Action:
Severity: Info.
SCH8844
SNMP trap: No
This tenant is already allowed/denied for this customer.

Action:
Severity: Info.
SCH8845
SNMP trap: No
Password conflicts with existing passwords.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1983 of 2360

SCH8846
Illegal character entered for password. Must be 0-9, A-Z, or a-z.

Action:
Severity: Info.
SCH8847
SNMP trap: No
Warning: Display DN does not start with an ENP pilot DN.

Action:
Severity: Info.
SCH8848
SNMP trap: No
ICP cannot co-exist with anything else.

Action:
Severity: Info.
SCH8849 xxxx
SNMP trap: No
This is an X20 error message. Where xxxx = 139 : Channel number

out-of-range 219 : Cannot configure analog trunk in digital route 279 : Unable
to match input field with stored mnemonics 597 : Required number of TN
blocks not configured or removed because maximum channel number was
reached 969 : Burst parameter cannot have a value less than that of the
replenishment parameter 970 : Unable to match input field with stored
mnemonics 971 : Invalid response
972 : Input out-of-range 974 : DTSL/DDSL specified is not configured as a
public network link 1300 : Wrong number of input fields for prompt
DTSL/DDSL (DPNSS) 1301 : DTSL/DDSL number out-of-range (0-159)
(DPNSS) 1302 : DTSL/DDSL block already exists (DPNSS)1303 :
DTSL/DDSL block does not exist (DPNSS) 1304 : No DTSL/DDSL blocks exist
(DPNSS)
1305 : Signaling link still in service (DPNSS)
1306 : DTSL/DDSL still enabled (DPNSS)
1307 : DTSL number does not belong to a DASS signaling card (DPNSS)
1308 : DTIB/DTOB must be set up in LD 17. Digital trunk input/output buffers
are zero. (DPNSS)
1310 : Wrong number of input fields in response to LTYP prompt (DPNSS)
1311 : Unable to match input with stored mnemonics (DPNSS)
1315 : Unable to match input with stored mnemonics (DPNSS)
1316 : Wrong number of input fields (DPNSS)
1317 : Number out-of-range (DPNSS)
1320 : Wrong number of input fields in response to DDCS prompt (DPNSS)
1321 : DDCS number out-of-range (DPNSS)
1322 : DDCS not configured (DPNSS)
1329 : Cannot out a DTSL/DDSL if a channel is configured
1330 : Wrong number of input fields for prompt DTSL/DDSL (APNSS)
System Messages
Page 1984 of 2360

1331 : DTSL/DDSL number out-of-range (0-159) (APNSS)
1332 : DTSL/DDSL block already exists (APNSS) 1333 : DTSL/DDSL block
does not exist (APNSS)
1334 : No DTSL/DDSL blocks exist (APNSS)
1335 : Signaling link still in service (APNSS)
1336 : DTSL/DDSL still enabled (APNSS)
1338 : DTIB/DTOB must be set up in LD 17. Digital trunk input/output buffers
are zero. (APNSS)
1340 : Wrong number of input fields in response to LTYP prompt (APNSS)
1341 : Unable to match input with stored mnemonics (APNSS)
1345 : Unable to match input with stored mnemonics (APNSS)
1346 : Wrong number of input fields (APNSS)
1347 : Number out-of-range (APNSS)
1350 : Wrong number of input fields in response to DDCS prompt (APNSS)
1351 : DDCS number out-of-range (APNSS)
1352 : DDCS not configured (APNSS)
1355 : DDSL mismatch
2071 : Package not configured
2073 : IDA route cannot be changed to non-IDA and vice versa
5703 : Define first a DCH block for DPNSS in LD 17
8000 : PBX Reference Number does not begin with Location Reference
Number (Warning only-entry as accepted)
8001 : NCOP transmission must be used.
Action:
Severity: Info.
SCH8850
SNMP trap: No
Route List Block (RLB) does not exist.

Action:
Severity: Info.
SCH8851
SNMP trap: No

Action:
Severity: Info.
SCH8852
SNMP trap: No

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1985 of 2360

SCH8853
Input out-of-range (1-10) for CDP

Input out-of-range (1-19) for UDP
Action:
Severity: Info.
SCH8854
SNMP trap: No
SNMP trap: No

Action:
Severity: Info.
SCH8860
Tenant number out-of-range (0-511).

Action:
Severity: Info.
SCH8861
SNMP trap: No
Link used by other customer.

Action:
Severity: Info.
SCH8862
SNMP trap: No
Cannot change set with IRGA CLS from AAPBX.

Action:
Severity: Info.
SCH8863
SNMP trap: No
Cannot change set with IPNA CLS from AABCS.

Action:
Severity: Info.
SCH8864
SNMP trap: No
Cannot use IRGA/IRGD together with NEW X command.

Action:
Severity: Info.
SCH8866
SNMP trap: No
ICP cannot be removed with agents still defined.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1986 of 2360

SCH8867
ICP cannot be set up for an ACD DN with agents.

Action:
Severity: Info.
SCH8868
SNMP trap: No
Response NO not allowed when ICP is defined.

Action:
Severity: Info.
SCH8869
SNMP trap: No
Cannot remove a tenant which is owner of ICP.

Action:
Severity: Info.
SCH8870
SNMP trap: No
Cannot remove MC when ICP is allowed.

Action:
Severity: Info.
SCH8871
SNMP trap: No
SNMP trap: No
ICDN must be entered.

Action:
Severity: Info.
SCH8872
Maintenance message out-of-range (0-9).

Action:
Severity: Info.
SCH8873
SNMP trap: No
Maintenance message must be entered (0-9).

Action:
Severity: Info.
SCH8874
SNMP trap: No
APL not defined for ICP in LD 17.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1987 of 2360

SCH8875
APL number must be entered (0-15).

Action:
Severity: Info.
SCH8876
SNMP trap: No
Cannot decrease NIPN when higher IPN/IRG defined.

Action:
Severity: Info.
SCH8877
SNMP trap: No
Cannot remove ICP when ACD group defined for APL.

Action:
Severity: Info.
SCH8878
SNMP trap: No
Cannot remove ICP when IPN/IRG sets exist.

Action:
Severity: Info.
SCH8879
SNMP trap: No
Terminal/printer number must be entered (0-{NIPN}).

Action:
Severity: Info.
SCH8880
SNMP trap: No
Both DSET and DCON packages must exist.

Action:
Severity: Info.
SCH8881
SNMP trap: No
Must be quad loop for digital console.

Action:
Severity: Info.
SCH8882
SNMP trap: No
LANG number out-of-range (0-15) for digital console.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1988 of 2360

SCH8883
Primary and secondary TNs must be on the same Loop, Shelf and Card.
Action:
Severity: Info.
SCH8884
SNMP trap: No
Unit number out-of-range for digital consoles.

Action:
Severity: Info.
SCH8885
SNMP trap: No
Warning: The active password length is changed only if new configuration data
is dumped, and a complete data load and program load takes place.
Action:
Severity: Info.
SCH8886
SNMP trap: No
Cannot remove customer while Flexible Feature Code tree exists.

Action:
Severity: Info.
SCH8887
SNMP trap: No
An invalid value for the Electronic Lock password was entered.

Action:
Severity: Info.
SCH8888
SNMP trap: No
The Station Control Password can only use digits 0-9.

Action:
Severity: Info.
SCH8889
SNMP trap: No
CEPT default does not match the password length defined in LD 15.
Action:
Severity: Info.
SCH8890
SNMP trap: No
Digit entered for REP causes replacement CEPT code to conflict with existing
DN.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1989 of 2360

SCH8891
Maximum number of FFCs outed in this pass.

Action:
Severity: Info.
SCH8892
SNMP trap: No
FFC was defined earlier in this program.

Action:
Severity: Info.
SCH8893
SNMP trap: No
Specified DN conflicts with an existing DN.

Action:
Severity: Info.
SCH8894
SNMP trap: No
Package is not equipped.

Severity: Info.
SCH8895
SNMP trap: No
FFC code does not exist.

Action:
Severity: Info.
SCH8896
SNMP trap: No
FFC data does not exist.

Action:
Severity: Info.
SCH8897
SNMP trap: No
FFC data already defined for a customer.

Action:
Severity: Info.
SCH8898
SNMP trap: No
FFC package is not enabled.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1990 of 2360

SCH8899
511 is an invalid entry for a ring cadence.

Action:
Severity: Info.
SCH8900
SNMP trap: No
No FDTD table configured.

Action:
Severity: Info.
SCH8901
SNMP trap: No
COOP package is not equipped.

Action:
Severity: Info.
SCH8902
SNMP trap: No
Pointer to COOP_CPG_ICCOUNT array not defined.

Action:
Severity: Info.
SCH8904
SNMP trap: No
Cannot define a non-terminal loop as a GEC loop.

Action:
Severity: Info.
SCH8905
SNMP trap: No
Cannot set subtype if TYPE = TIE.

Action:
Severity: Info.
SCH8907
SNMP trap: No
Cannot use OUT command on console with ICP.

Action:
Severity: Info.
SCH8908
SNMP trap: No
Cannot use OUT command on a set with IPNA CLS.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1991 of 2360

SCH8909
ICP already configured for this customer.

Action:
Severity: Info.
SCH8910
SNMP trap: No
Packages 35 (IMS), 40 (BACD), 46 (MWC), 109 (APL), 131 (SUPP), and 139
(FFC) must be included.
Action:
Severity: Info.
SCH8911
SNMP trap: No
Terminal/printer number is already used.

Action:
Severity: Info.
SCH8912
SNMP trap: No
Terminal/printer number out-of-range (0-99).

Action:
Severity: Info.
SCH8913
SNMP trap: No
ICP is not configured for this customer or tenant.

Action:
Severity: Info.
SCH8914
SNMP trap: No
FDTD table does not exist.

Action:
Severity: Info.
SCH8915
SNMP trap: No
Trying to remove a nonexistent digit sequence.

Action:
Severity: Info.
SCH8916
SNMP trap: No
Table full, no more sequences allowed.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1992 of 2360

SCH8917
FDTD digit sequence already exists in table.

Action:
Severity: Info.
SCH8918
SNMP trap: No
FDTD table does not exist (REQ = OUT/CHG).

Action:
Severity: Info.
SCH8919
SNMP trap: No
FDTD table exists (REQ = NEW).

Action:
Severity: Info.
SCH8920
SNMP trap: No
OPCB package is restricted.

Action:
Severity: Info.
SCH8921
SNMP trap: No
Invalid entry for ALDN. ALDN can only be configured on a CHG command.
Action:
Severity: Info.
SCH8922
SNMP trap: No
SNMP trap: No
DN conflicts with ALDN.

Action:
Severity: Info.
SCH8923
Input number is out-of-range (0 - 10).

Action: Choose a number 0 - 9.
Severity: Info.
SCH8924
SNMP trap: No
Category code out-of-range (1-10).

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1993 of 2360

SCH8925
No current entry in list.

Action:
Severity: Info.
SCH8926
SNMP trap: No
At least one of call types CDPC/TOLL/ALRM/TNDM/SSUC/NDGT must be

set.
This error message may appear if the NDGT prompt is answered with 0
(NDGT is now the last prompt among SSDG's call type marks).
This error message may appear if SSUC is answered with NO (SSUC is now
the last prompt among SSDG's call type marks).
Action: Set at least one of the call types
CDPC/TOLL/ALRM/NDM/SSUC/NDGT.
Severity: Info.
SCH8927
SNMP trap: No
SSL not applicable to move command.

Action:
Severity: Info.
SCH8928
SNMP trap: No
SSL list already full (100 entries).

Action:
Severity: Info.
SCH8929
SNMP trap: No
SSL entry out-of-range (0-9999).

Action:
Severity: Info.
SCH8930
SNMP trap: No
SSL entry does not exist.

Action:
Severity: Info.
SCH8931
SNMP trap: No
Category code out-of-range.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1994 of 2360

SCH8932
List number out-of-range (0-15)

Action:
Severity: Info.
SCH8933
SNMP trap: No
SNMP trap: No
SSL list does not exist

Action:
Severity: Info.
SCH8934
HWTT input out-of-range (0-600).

Action:
Severity: Info.
SCH8936
SNMP trap: No
Same digit cannot be assigned to two programmable control digits.

Action:
Severity: Info.
SCH8948
SNMP trap: No
LAPW - Print Speed Call List is not allowed.

Action:
Severity: Info.
SCH8949
SNMP trap: No
Digital set cannot have LVXA Class of Service.

Action:
Severity: Info.
SCH8950
SNMP trap: No
ACD set cannot have LVXA Class of Service.

Action:
Severity: Info.
SCH8951
SNMP trap: No
Cannot have MTA and LVXA Class of Service.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1995 of 2360

SCH8952
CMOP - Package is not equipped.

Action:
Severity: Info.
SCH8953
SNMP trap: No
TVT - Volume key may not be changed using Attendant Administration.

Action:
Severity: Info.
SCH8954
SNMP trap: No
TVT - Only one of Volume Up/Down keys are configured.

Action:
Severity: Info.
SCH8955
SNMP trap: No
TVT - Attempt to define a non-terminal loop as a TVT loop.

Action:
Severity: Info.
SCH8956
SNMP trap: No
TVT - Before changes to OGTPECL/DCTI must be reset.

Action:
Severity: Info.
SCH8957
SNMP trap: No
SNMP trap: No
ICP data is not copied.

Action:
Severity: Info.
SCH8958
This set does not have IPNA CLS.

Action:
Severity: Info.
SCH8959
SNMP trap: No
This set does not have IRGA CLS.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1996 of 2360

SCH8960
ICP package 143 not equipped.

Action:
Severity: Info.
SCH8961
SNMP trap: No
PPM - Input value out-of-range (0-9999 inclusive).

Action:
Severity: Info.
SCH8962
SNMP trap: No
PPM - Input value out-of-range (0-15 inclusive).

Action:
Severity: Info.
SCH8963
SNMP trap: No
Warning: Port has been configured as a background terminal.

Action:
Severity: Info.
SCH8964
SNMP trap: No
PPM - Input value out-of-range. Value must be (0-3).

Action:
Severity: Info.
SCH8965
SNMP trap: No

Action:
Severity: Info.
SCH8966
SNMP trap: No

Action:
Severity: Info.
SCH8967
SNMP trap: No

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1997 of 2360

SCH8968
PPM - Input not allowed; only allowed for daily print.

Action:
Severity: Info.
SCH8969
SNMP trap: No
PPM - No space allowed after second hour input.

Action:
Severity: Info.
SCH8970
SNMP trap: No
PPM - No prime DN specified. MRA CLS changed to MRD.

Action:
Severity: Info.
SCH8971
SNMP trap: No
MR/PPM package must be enabled and Overlay 17 prompt MTRO set to PPM.
Action:
Severity: Info.
SCH8972
SNMP trap: No
PPM - Meter associated with this set/route is being deleted.

Action:
Severity: Info.
SCH8973
SNMP trap: No
ALP - Input is out-of-range (0-7) for APAD in CDB.

Action:
Severity: Info.
SCH8974
SNMP trap: No
DTI2 - Route is not a 2.0 Mb/s digital route.

Action:
Severity: Info.
SCH8975
SNMP trap: No
DTI2 - PAD category does not exist.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 1998 of 2360

SCH8976
DTI2 - JDMI package not equipped.

Action:
Severity: Info.
SCH8977
SNMP trap: No
DTI2 - Route is not a JDMI route.

Action:
Severity: Info.
SCH8979
SNMP trap: No
DTI2 - DTA is an invalid DSEL for RML and RLT routes.

Action:
Severity: Info.
SCH8985
SNMP trap: No
TBAR - Invalid group hunt member encountered all routes are assigned ART
# O.
Action:
Severity: Info.
SCH8986
SNMP trap: No
SUPP package 131 not equipped.

Action:
Severity: Info.
SCH8987
SNMP trap: No
TBAR - ARTs do not exist.

Action:
Severity: Info.
SCH8988
SNMP trap: No
TBAR - out-of-range (1-63).

Action:
Severity: Info.
SCH8989
SNMP trap: No
TBAR - ART already exists.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 1999 of 2360

SCH8990
RAN, MUSIC, AWU, and CAS routes cannot be barred.

Action:
Severity: Info.
SCH8991
SNMP trap: No
AFBT cannot be greater than AFNT.

Action:
Severity: Info.
SCH8992
SNMP trap: No
MPO package is not equipped.

Action:
Severity: Info.
SCH8993
SNMP trap: No
AFBT is greater than AFNT, AFBT has been set to.

Action:
Severity: Info.
SCH8994
SNMP trap: No
Cannot delete ART as it is used as default.

Action:
Severity: Info.
SCH8995
SNMP trap: No
MCT & MFC packages must be equipped.

Action:
Severity: Info.
SCH8996
SNMP trap: No
RART, REQ = NEW, or OUT is disallowed. New routes are created/removed

using LD 16.
Action:
Severity: Info.
SCH8997
SNMP trap: No
0, 1, and 2 are the only inputs allowed for RVDL.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2000 of 2360

SCH8998
RCDT, REQ = NEW, or OUT is disallowed.

Action:
Severity: Info.
SCH8999
SNMP trap: No
ART not defined for ART number entered.

Action:
Severity: Info.
SCH9002
SNMP trap: No
CDN cannot be allowed as nite DN.

Action:
Severity: Info.
SCH9949
SNMP trap: No
GPT Integrated Digital Access Service Change x x x x x.

Action:
Severity: Info.
SCH9952
SNMP trap: No
Call Forward All Calls DN size exceeds M2317 or M3000 maximum length of
23 digits.
Action: Enter the correct number of digits between 4 - 23.
Severity: Info.
SCH9953
SNMP trap: No
Class of service FLXA/VCE is required for a DTM key.

Action:
Severity: Info.
SCH9954
SNMP trap: No
This set cannot be copied as ir contains a DTM key. The DTM key must first
be deleted before copying to prevent a multiple appearance of a data DN.
Action:
Severity: Info.
SCH9955
SNMP trap: No
It is not allowed to configure a phanyom DTI2 loop as tracking for the clock
controller.
Action: Enter another loop number.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2001 of 2360

SCH9962
In Overlay 25, the commands MOVE and SWAP are not allowed on a phantom
DTI2 loop.
Action:
Severity: Info.
SCH9981
SNMP trap: No
MMSN data is in use and cannot be cleared.

Action: Remove all mportbl sets defined with VISI = YES before removing
MMSN.
Severity: Minor.
SCH9982
SNMP trap: No
A mportbl set defined as Visiting may not be assigned a multiple appearance

DN.
Action: Assign a unique DN on key 0.
Severity: Minor.
SCH9996
SNMP trap: No
This MWI NSI table does not exist

Action: Enter the Manufacturer Identifier of the M
Severity: Info.
SCH9997
SNMP trap: No
Character out of range A to Z. MFID is re-prompted.

Action: Enter a character inside the valid range o
Severity:
SCH9998
SNMP trap: No
An attempt has been made to set FNP to NO, in LD 15. If SCH9998 is followed
by SCH0168 the request has been rejected.
Action: WARNING - All data associated with FNP must be deleted prior to
setting FNjP to NO. In LD 15, set VNR to NO. In LD 87 and LD 90 set all FLEN to
0. In LD 86 set FSNI and MXFS to 0, MXDM and MXRL to 0-256, AC1 and AC2
to 0-99. In LD 24, set DFCL to a 7 or 10 digit length value.
Severity: Major.
SNMP trap: No
System Messages
Page 2002 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2003 of 2360
SCR: System Clock Reference

Messages
SCR2000 XYZ
System Clock Reference for cabinet X switched from old source Y to new
source Z, where Y and Z can have the following values:
0 (Clock Controller or CPU clock)
1-4 (IP Daughterboard ports 1-4, respectively)
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 2004 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2005 of 2360
SCSI: Small Computer System Interface

SCSI messages appear when problems are encountered relating to the SCSI
low level software.
Messages
SCSI0001
Unable to initialize Interrupts for SCSI.

Action:
Severity: Critical.
SCSI0002
SNMP trap: Yes
Unable to initialize floppy drive x.

Action:
Severity: Critical.
SCSI0003
SNMP trap: No
Unable to initialize SCSI controller on IOP.

Action: Be sure IOP is in place and enabled.
Severity: Critical.
SCSI0004 x
SNMP trap: Yes
File system initialization failed for floppy x.

Action:
Severity: Critical.
SCSI0006
SNMP trap: No
Floppy Disk INIT: Block device INIT failed for CMDU x.

Action:
Severity: Critical.
SCSI0008 x
SNMP trap: No
Floppy Disk: Unknown floppy controller in CMDU x not supported.

Action:
Severity: Critical.
SCSI0009 x
SNMP trap: Yes
Hard disk in CMDU x is not responding.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2006 of 2360

SCSI0010 x y
Hard Disk Test: Partition x in CMDU y is not initialized.

Action: Reinstall software from installation disks.
Severity: Critical.
SCSI0011 w x y z
SNMP trap: Yes
Read Test: Read failed near sector w, errNo x, sense y, addSense z.
Action: Refer to Table 10 starting on page 788 for a listing of x, y and z values
and value descriptions.
Severity: Critical.
SCSI0012 x
SNMP trap: Yes
Floppy drive in CMDU x is not responding. Check CMDU power, and IOP to
IOP cables.
Action:
Severity: Critical.
SCSI0013
SNMP trap: Yes
Floppy Disk Test: Floppy disk is not initialized.

Action:
Severity: Critical.
SCSI0014 x y
SNMP trap: No
CMDU x is not active, using CMDU y. Check CMDU power, and IOP to IOP
cables.
Action:
Severity: Critical.
SCSI0016 x
SNMP trap: Yes
File system initialization failed for x. Reinstall software from installation disks.
Action:
Severity: Critical.
SCSI0017 w x y z
SNMP trap: Yes
Error writing to floppy disk, sector w, errNo x, sense y, addSense z.
Action:
Severity: Critical.
SCSI0018 w x y z
SNMP trap: Yes
Error reading from floppy disk, sector w,errNo x, sense y, addSense z.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2007 of 2360

SCSI0020
No response from hard disk in both CMDUs, or hard disks were incorrectly
initialized. Be sure the CMDU power is on, and cables are in place. Reinstall
software from installation disks if necessary.
Action:
Severity: Critical.
SCSI0021 x
SNMP trap: Yes
Active shelf x has no active CMDU. Be sure there is a CMDU on active core
shelf.
Action:
Severity: Critical.
SCSI0022 x
SNMP trap: Yes
Controller self test failed.

Action:
Severity: Critical.
SCSI0023
SNMP trap: Yes
No active CMDU present.

Action: Ensure the CMDU is enabled, power is on, and cables are in place.
Severity: Critical.
SCSI0026 w x y z
SNMP trap: Yes
Error writing to active hard disk, sector w, errNo x, sense y, addSense z.
Action:
Severity: Critical.
SCSI0027 w x y z
SNMP trap: Yes
Error writing to standby hard disk, sector w, errNo x, sense y, addSense z.
Action:
Severity: Critical.
SCSI0028 w x y z
SNMP trap: No
Error reading from active hard disk, sector w, errNo x, sense y, addSense z.
Action:
Severity: Critical.
SCSI0029 x
SNMP trap: Yes
Error reading from standby hard disk, sector x.

Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 2008 of 2360

SCSI0030 x
Hard disk synchronization error. CMDU x is not the active disk.

Action:
Severity: Critical.
SCSI0031
SNMP trap: No
Synchronization failed because one or both hard disks are disabled. Check
standby CMDU power and cables.
Action:
Severity: Critical.
SCSI0032
SNMP trap: No
Synchronization failed because one or both hard disks are not initialized.
Action:
Severity: Critical.
SCSI0034
SNMP trap: No
Active drive partition bigger than standby.

Action:
Severity: Critical.
SCSI0036
SNMP trap: No
Comparison failed between Active and Standby hard disks for x.

Action:
Severity: Critical.
SCSI0037
SNMP trap: No
Synchronization called with invalid CMDU number x.

Action:
Severity: Critical.
SCSI0038
SNMP trap: No
Synchronization failed for x.

Action:
Severity: Critical.
SCSI0039
SNMP trap: No
No standby CMDU present. Be sure standby CMDU power is on, and cables
are in place.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2009 of 2360

SCSI0040
Timeout before writing active hard disk sector x.

Action:
Severity: Critical.
SCSI0041
SNMP trap: No
Timeout before writing standby hard disk sector x.

Action:
Severity: Critical.
SCSI0042
SNMP trap: No
Timeout before reading active hard disk sector x.

Action:
Severity: Critical.
SCSI0043
SNMP trap: No
Timeout before reading standby hard disk sector x.

Action:
Severity: Critical.
SCSI0044
SNMP trap: No
Watchdog timeout while accessing disk.

Action:
Severity: Critical.
SCSI0100
SNMP trap: Yes
CMDU Y, Error Reading from Hard Disk, sector X, errNo Z, sense W, add
Sense V.
Action:
Severity: Critical.
SCSI0101
SNMP trap: Yes
CMDU Y, Error Writing to Hard Disk, sector X, errNo Z, sense W, addSense V

Action:
Severity: Critical.
SCSI0102
SNMP trap: Yes
CMDU X, Timeout before Reading from Hard Disk sector Y

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2010 of 2360

SCSI0103
CMDU X, Timeout before Writing to Hard Disk sector Y

Action:
Severity: Critical.
SCSI0104
SNMP trap: Yes
CMDU X, Filename F Date D Time T Size S

Action:
Severity: Critical.
SCSI0105
SNMP trap: Yes
Files that are different in Dir: X

Action:
Severity: Critical.
SCSI0106
SNMP trap: Yes
Files that are different in Partition: P.

Action:
Severity: Critical.
SCSI0107
SNMP trap: Yes
This message is printed when list items exceed the allowable parameters.
Action:
Severity: Critical.
SCSI0108 x
SNMP trap: Yes
Partition X: Sector number %d does not match

Action:
Severity: Info.
SCSI0109 x y
SNMP trap: Yes
CMDU x in Active Side is not latest, using CMDU y.

Action:
Severity: Critical.
SCSI0110
SNMP trap: Yes
Partition parameters of the Active and Standby drives are different

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2011 of 2360

SCSI0111
Cannot decide latest CMDU, going with CMDU X

Action:
Severity: Critical.
SCSI0112 x y z
SNMP trap: Yes
Partition X: reporting Y sectors to sync. This is greater than partition size Z, so

Sync will complete partition. Reinstall software from installation diskettes if
required.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2012 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2013 of 2360
SDL: Peripheral Software Download

The Peripheral Software Download (PSDL) feature stores Peripheral Software
(PSW) on disk for:
Network Cards (NT8D04)
Network/DTR (NT8D16)
Controllers cards (NT8D01)
The PSW is downloaded to the peripheral cards when:
system initialization occurs
the card is enabled via ENLL and ENXP commands in LD 30 and LD 32
the card undergoes power up reset
Control of initialization downloaded is defined in LD 97.
Messages
SDL0000 text
Peripheral Software Download has occurred. The output format is: SDL000
device, VERSION x, mode Where device is : XNET loop = NT8D08 Network
card loop number XNPD loop = NT8D16 Network/DTR card loop number
XPEC xpec# (loop shelf) = NT8D01 Controller card Where VERSION x =
Peripheral Software version (0-99) Where mode is : FAST MODE (from
initialization) MAINT MODE (by ENLL command in LD30/LD32) BKGD MODE
(second attempt after initialization)
Action:
Severity: Minor.
SNMP trap: No
SDL0001tttt cc dddddd ll s cc vv Beginning of the Flashdownload for the considered TN.

Where: TYPE = tttt, CUST = cc, PDN = dddddd, TN = ll s cc uu, FW = vv.
Action:
Severity: Info.
SDL0002
SNMP trap: Yes
M3900 download completed.

Action:
Severity: Info.
SDL0003
SNMP trap: Yes
M3900 download suspended for midnight.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 2014 of 2360

SDL0004
M3900 download restarted after midnight.

Action:
Severity: Info.
SDL0005
SNMP trap: Yes
M3900 download stopped

Action:
Severity: Info.
SDL0100 status
SNMP trap: Yes
Current status of the Peripheral Software Download process.Status can be :

BUSY (download in process) IDLE SUSP (user loading a program with SUSP
option) ABRT (aborting)
Action:
Severity: Minor.
SDL0101
SNMP trap: Yes
Maintenance bit is not ON for the TN.

Action:
Severity: Minor.
SDL0102
SNMP trap: Yes
TNTRANS failed for the download TN.

Action:
Severity: Minor.
SDL0103
SNMP trap: Yes
Bad sub packet data length.

Action:
Severity: Minor.
SDL0104
SNMP trap: Yes
First data byte in the packet is not H.0B.

Action:
Severity: Minor.
SDL0105
SNMP trap: Yes
SNMP trap: Yes
Bad packet data length.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
Page 2015 of 2360

SDL1301
Failure in starting the PSW download process.

Action: Do a manual initialization and try the download again. If still
unsuccessful, do a manual SYSLOAD. CAUTION: Initialization and SYSLOAD
will interrupt call processing.
Severity: Minor.
SDL1302
SNMP trap: Yes
Failure in continuing the PSW download process.

Action: Do a manual initialization and try the download again. If still
unsuccessful, do a manual SYSLOAD. CAUTION: Initialization and SYSLOAD
Severity: Minor.
SDL2100
SNMP trap: Yes
Cannot allocate memory for PSDL output buffers.

Action:
Severity: Minor.
SNMP trap: Yes
SDL2110 e hw a v m Failed to download software to device. Where: e (cause of the error) can be:
1 = Acknowledgment timeout error 2 = Peripheral Software (PSW) version or
checksum error 3 = PSW record checksum error 4 = PSW record format error
5 = Card firmware state error hw (card name) can be: XNET (Network Card)
XPEC (Peripheral Controller), etc.a (card address) can be:
Loop for Network Card, Network/DTR Card
XPEC # (loop shelf) for Peripheral Controller
v is the PSW version
m can be:
FAST MODE (from initialization)
MAINT MODE (by ENLL command in LD 30)
BKGD MODE (second attempt after initialization from background program)
Hw (3902,3903,3904,3905) for Taurus flash download, e (cause of the error
for Taurus SDL cards) can be:
1- Timeout (Taurus TN did not respond)
2- Error detected in overall checksum
3- Error detected in packet data checksum
4- Error detected in the format of the specified record.
5- Invalid page number received.
17- Flash memory cannot be erased. In this case the memory page will always
be 1.
18- Error detected while programming flash memory device. The record
number will reflect the record number that was being programmed into the
flash when the error occurred.
System Messages
Page 2016 of 2360

19- An application is currently active. Download cannot proceed at this time.
20- Verification byte is incorrect.
other, ?, 50 (where ? means the reason number is less than 0) = unknown
Action: Try to download to the card by using the appropriate enable command.
Severity: Minor.
SDL2115 t tn
SNMP trap: Yes
Three attempts to recover Flash download failed.

- t - set type (3902, 3903, 3904 or 3905
tn - TN of the set in (l s c u) or (s u)
Action: Force download flash firmware to specified set manually.
Severity: Major.
SDL2116 t tn
SNMP trap: Yes
Flash download failed during download recovery.

- t set type (3902, 3903, 3904 or 3905)
tn - TN of the set in ( l s c u) or (s u)
Action: Force download flash firmware to specified set, manually.
Severity: Major.
SDL2401
SNMP trap: Yes
Failed to allocate a Call Register for Peripheral Software Download (PSDL).

Action: Do a manual initialization and try the download again. CAUTION:
Initialization will interrupt call processing.
Severity: Minor.
SDL4200
SNMP trap: Yes
All target devices in the current Peripheral Software Download (PSDL) list
failed download.
Action: Do the following in order: 1. Do a manual SYSLOAD and try download
again. CAUTION: this will interrupt call processing. 2. Use a different set of
system disks. 3. Replace all cards involved.
Severity: Minor.
SDL5201
SNMP trap: Yes
Invalid SL-1 software version.

Action: Check the software version on disk.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2017 of 2360

SDL5202
Peripheral Software (PSW) is not configured on the disk.

Action:
Severity: Minor.
SDL5301
SNMP trap: Yes
Insufficient memory for the Peripheral Software (PSW) subdirectory.

Action: Try manual initialization and retry the command. CAUTION: Initialization
Severity: Minor.
SDL5302 v
SNMP trap: Yes
The Peripheral Software (PSW) version v cannot be found on the disk.

Action:
Severity: Minor.
SDL5303 t
SNMP trap: Yes
The Peripheral Software (PSW) Type cannot be found on the disk. Where t =
the requested device Type, where: XNET = Network card XPND =
Network/DTR card XPEC = Controller card
Action:
Severity: Minor.
SDL7111 loop
SNMP trap: Yes
Failure in writing Peripheral Software (PSW) data to a loop.

Action: Check the network card.
Severity: Minor.
SDL7112 loop
SNMP trap: Yes
The Peripheral Controller, Network or Network/DTR card has requested an

SDL download. The PSDL is waiting to recover the bad cards; but, they can
also be recovered by the Midnight SDL Audit.
Action: If the program was loaded manually, exit the activity by entering "****" or
"END" as soon as possible.
Severity: Minor.
SDL7113
SNMP trap: Yes
Trying to put the Peripheral Controller, Network or Network/DTR card into the
PSDL tree has failed five (5) times. These cards will not be recovered by SDL.
Action: Initialize manually.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2018 of 2360

SDL7114
The SDL recovery request for this Peripheral Controller has been ignored,
because of more than ten (10) requests so far today.
Action:
Severity: Minor.
SDL7115 loop
SNMP trap: Yes
The SDL recovery request for this Network or Network/DTR card has been
ignored, because of more than ten (10) requests so far today.
Action:
Severity: Minor.
SDL7116
SNMP trap: Yes
The request for SDL auto-recovery has not been queued or processed. The
system cannot get a three-word data block.
Action:
Severity: Minor.
SDL7117 x y z
SNMP trap: Yes
An error occurred when downloading PSW records to the MSDL/MISP card.

Meridian 1 was not able to send messages to MSDL/MISP card.
Where: x = card type that was being downloaded Values for x are: H.1: XNET
card type, H.2: LCRI card type, H.3: XNPD card type, H.4 : XPEC card type,
H.5 : MISP basecode loadware, H.6: MISP BRI Line application, H.7: MISP
BRI Trunk application, H.8: MISP MPH application loadware, H.9: MSDL base
PSW, H.10: MSDL ASYN. Application PSW, H.11: MADL DCH application
PSW, H.12: MSDL MLNK application PSW, H.13: BRSC base code H.14 :
BRSC BRI application H.15: UIPE PRI loadware application, H.16: UIPE BRIT
loadware application, H.17: NI2 TR1268 data file.
Where: y = card address to which download was done (INDEX number of
MSDL/MISP). Where: z = Return value from MSDLMISP_HDLR H.0 : Request
to send message failed H.2 : MSDL/MISP card is not operational H.5 : No
buffer available to send message to MSDL/MISP card
Action:
Severity: Minor.
SDL7118 x y z
553-3001-411
SNMP trap: Yes
An error occurred when downloading PSW records to the MSDL/MISP card.

Meridian 1 was not able to send messages to MSDL/MISP card.
Where: x = card type that was being downloaded Values for x are: H.1: XNET
card type, H.2: LCRI card type, H.3: XNPD card type, H.4 : XPEC card type,
H.5 : MISP basecode loadware, H.6: MISP BRI Line application, H.7: MISP
BRI Trunk application, H.8: MISP MPH application loadware, H.9: MSDL base
PSW, H.10: MSDL ASYN. Application PSW, H.11: MADL DCH application
Standard 15.00
January 2006
Page 2019 of 2360

PSW, H.12: MSDL MLNK application PSW, H.13: BRSC base code H.14 :
BRSC BRI application H.15: UIPE PRI loadware application, H.16: UIPE BRIT
loadware application, H.17: NI2 TR1268 data file.
Where: y = card address to which download was done (INDEX number of
MSDL/MISP). Where: z = Return value from MSDLMISP_HDLR H.0 : Request
to send message failed H.2 : MSDL/MISP card is not operational H.5 : No
buffer available to send message to MSDL/MISP card
Action: Check the state of the MSDL card. Try to disable and enable
MSDL/MISP card from the software. If the problem persists, contact your
technical support.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2020 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2021 of 2360
SECA: Security Administration Alarm

Messages
SECA0001
Authcode violation has been detected.

Action: Refer to the Operator Data for information regarding origination.
Severity: Minor.
SECA0002
SNMP trap: Yes
A calling user dialed a service number that the user is not allowed to reach.
The call has been intercepted for access denied,
Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 2022 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2023 of 2360
SEC: Security Notification Monitor

The Security Notification Monitor program monitors the system activities
relating to security items. When an activity relating to a security item is
detected (i.e. invalid login) the security monitor program generates a SEC
code. Some SEC codes are information based, while others are warnings that
may require an action to be taken.
Messages
SEC0014
PWD2 has been reset to default.

Action: Login as PWD2 user and change the password.
Severity: Major.
SEC0015
SNMP trap: Yes
Attempt to reset the PWD2 failed. System must be in password over-ride

mode.
Action: Place system in password over-ride mode before issuing password reset
command.
Severity: Warning.
SEC0022
SNMP trap: Yes
Insecure shells have been disabled.

Action: None
Severity: Info.
SEC0023
SNMP trap: Yes
Insecure shells have been enabled.

Action: None
Severity: Info.
SEC0024
SNMP trap: Yes
Secure shells have been disabled.

Action: None
Severity: Info.
SEC0025
SNMP trap: Yes
Secure shells have been enabled.

Action: None
Severity: Info.
SNMP trap: Yes
System Messages
Page 2024 of 2360

SEC0026
Password override mechinism was used to gain access to the switch.

Action: None
Severity: Info.
SEC0027
SNMP trap: Yes
Failed to load the account database, all system accounts are locked out.
Action: None
Severity: Major.
SEC0028
SNMP trap: Yes
Pre release 4 PDT account is corrupt, conversion of PDT accounts ignored.

Severity: Info.
SEC0029
SNMP trap: Yes
Security Warning: This system contains insecure passwords, notify your

system administrator.
Action: None
Severity: Info.
SEC0030
SNMP trap: Yes
Corrupt Password Database detected. Unable to reset passwords to default.

Severity: Major.
SEC0031
SNMP trap: Yes
Failed to reset all account passwords.

Severity: Info.
SEC0032
SNMP trap: Yes
System accounts have been reset to default.

Severity: Info.
SEC0033
SNMP trap: Yes
Failed to reset system accounts, internal error.

Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2025 of 2360

SEC0034
Failed to save system accounts, internal error.

Severity: Major.
SEC0040
SNMP trap: Yes
Host IP address pointer is NULL.

Severity: Minor.
SEC0041
SNMP trap: Yes
Invalid source type: <source numeric type>.

Severity: Minor.
SEC0042
SNMP trap: Yes
Invalid destination type: <destination numeric type>.

Severity: Minor.
SEC0043
SNMP trap: Yes
Failed to allocate memory to store host IP address.

Severity: Major.
SEC0044
SNMP trap: Yes
Failed to spawn <name of task> task.

Severity: Major.
SEC0045
SNMP trap: Yes
Failed to abort <name of task> task in order to spawn again.

Severity: Major.
SEC0046
SNMP trap: Yes
nfcAPI failed to retrieve account from call server.

Severity: Major.
SNMP trap: Yes
System Messages
Page 2026 of 2360

SEC0047
Failed to send message to INACTIVE CORE.

Severity: Major.
SEC0048
SNMP trap: Yes
Invalid machine type for the given device.

Severity: Minor.
SEC0049
SNMP trap: Yes
Failed to create the accounts directory: <path of directory>.

Severity: Major.
SEC0050
SNMP trap: No
Failed to close the accounts directory: <path of directory>.

Severity: Major.
SEC0051
SNMP trap: Yes
Failed to create the accounts file: <name of file>.

Severity: Major.
SEC0052
SNMP trap: Yes
Invalid PWD2 password.

Action: Retype the password.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2027 of 2360
SRPT: System Reports

The System Reports messages, appear during normal system operation.
Some are warning messages and indicate an action must be taken. Others are
information messages that indicate system activity and progress.
Messages
SRPT0008 xxxx
FTP access locked out. Too many bad login attempts. Last source IP address:
xx (All FTP ports locked out for 10 minutes)
Action:
Severity: Minor.
SRPT0009
SNMP trap: No
SNMP trap: No
FTP access re-enabled.

Action:
Severity: Info.
SRPT0010 xxxx
PDT: access locked out. Too many bad logging attempts. (PDT access locked
out for 10 minutes)
Action:
Severity: Minor.
SRPT0011 yyyy
SNMP trap: No
PDT: access re-enabled.

Action:
Severity: Info.
SRPT0012 xxxx
SNMP trap: No
FTP access locked out. Too many bad login attempts. Last source IP address:
xx (All FTP ports locked out for 10 minutes)
Action:
Severity: Minor.
SRPT0013 yyyy
SNMP trap: No
SNMP trap: No
FTP access re-enabled.

Action:
Severity: Info.
System Messages
Page 2028 of 2360

SRPT0014 xxxx
PDT: access locked out. Too many bad login attempts. (PDT access locked
out for 10 minutes)
Action:
Severity: Minor.
SRPT0015 xxxx
SNMP trap: No
PDT: access re-enabled.

Action:
Severity: Info.
SRPT0016
SNMP trap: Yes
OMM: IP link is DOWN between cab <#> and cab <#>.

Action:
Severity: Major.
SRPT0017
SNMP trap: Yes
OMM: IP link is UP between cab x and cab y.

Action:
Severity: Info.
SRPT0018
SNMP trap: Yes
LCS: Graceful switchover not executed. Local health is better than remote
health.
Action:
Severity: Info.
SRPT0019
SNMP trap: Yes
LCS: redundancy state changed from %s to %s.

Action:
Severity: Info.
SRPT0020
SNMP trap: Yes
LCS: Active state changed from %s to %s.

Action:
Severity: Info.
SRPT0021
SNMP trap: Yes
LCS: HSP state changed from %s to %s.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2029 of 2360

SRPT0022
DR: Successfully recovered drMsgQId.

Action:
Severity: Info.
SRPT0023
SNMP trap: Yes
CPM: CPM completed protected memory sync.

Action:
Severity: Major.
SRPT0024
SNMP trap: Yes
CPM: CPM started protected memory sync.

Action:
Severity: Info.
SRPT0025
SNMP trap: Yes
CPM received stop update message from LCS.

Action:
Severity: Info.
SRPT0026
SNMP trap: Yes
HB: remote side health change. %d.

Action:
Severity: Major.
SRPT0027
SNMP trap: Yes
HB: Cannot detect heartbeat from remote core

Action: Check the connections to the remote core are good, ensure the remote
core is operational. Otherwise contact your technical support group
Severity: Major.
SRPT0028
SNMP trap: Yes
HB: Heartbeat detected from remote core.

Action:
Severity: Info.
SRPT0029
SNMP trap: Yes
Disk Partition: all partitions successfully initialized.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 2030 of 2360

SRPT0030
Disk Partition: format request received.

Action:
Severity: Info.
SRPT0031 x y
SNMP trap: Yes
Disk Redundancy: dosFsChk() returned ERROR on partition x.

Error value = y
Action: Please re-install software.
Severity: Major.
SRPT0032
SNMP trap: Yes
DR: Received Start Sync. Switching to Slave

Action:
Severity: Info.
SRPT0033
SNMP trap: Yes
Disk Redundancy: Master is starting disk sync.

Action:
Severity: Info.
SRPT0034
SNMP trap: Yes
LCS: Join command not valid in %s state.

Action:
Severity: Info.
SRPT0035
SNMP trap: Yes
LCS: Cutover command no valid in %s state.

Action:
Severity: Info.
SRPT0036
SNMP trap: Yes
LCS: Graceful switchover command not valid on %s state.

Action:
Severity: Info.
SRPT0037
SNMP trap: Yes
LCS: Split command not valid in %s state.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2031 of 2360

SRPT0038
LCS: Split command successful.

Action:
Severity: Info.
SRPT0039
SNMP trap: Yes
LCS: Join command successful.

Action:
Severity: Info.
SRPT0040
SNMP trap: Yes
LCS: Cutover command successful.

Action:
Severity: Info.
SRPT0041
SNMP trap: Yes
LCS: Graceful switchover command successful.

Action:
Severity: Info.
SRPT0042
SNMP trap: Yes
LCS: SWO can't proceed. Failed to send SWO message to <s>Where <s>:
module name : LCS, SWO
Severity: Critical.
SRPT0043
SNMP trap: Yes
LCS: Protected memory and disk synchronization complete.

Action:
Severity: Info.
SRPT0044
SNMP trap: Yes
LCS: Join denied. Incompatible software releases. Both sides must have the
same release installed.
Action:
Severity: Info.
SRPT0045
SNMP trap: Yes
LCS: Disk has not finished sync, set it to split.

Action: An error occurred during last disk sync, system will be in split mode.
Severity: Info.
SNMP trap: Yes
System Messages
Page 2032 of 2360

SRPT0046
LCS: Cannot Join, the redundant partition is not synced, try CUTOVER first.
Action: Do a CUTOVR and Join from the other side
Severity: Info.
SRPT0047
SNMP trap: Yes
Disk Redundancy: Master asked to stop disk sync.

Action:
Severity: Info.
SRPT0048
SNMP trap: Yes
Disk Redundancy: Master asked to stop updates and flush file system.
Action:
Severity: Info.
SRPT0049
SNMP trap: Yes
Disk Redundancy: Master asked to stop updates.

Action:
Severity: Info.
SRPT0050
SNMP trap: Yes
Disk Redundancy: Disk sync completed.

Action:
Severity: Info.
SRPT0051
SNMP trap: Yes
PDT: PDT passwords set to default.

Action:
Severity: Info.
SRPT0052
SNMP trap: Yes
PDT: Could not PDT password file.

Action: Try to reset the PDT passwords using the PASSWD command.
If the PASSWD command fails or cannot be executed then:
- for an Option 11C enable the magic switch. Enter PDT using the systems
SECURITY ID. Enter the PASSWD command and use the SECURITY ID as the
old PDT Level 2 Password.
- for all other systems, enter the install disk in the floppy drive off the active core.
Enter PDT using the system TAPE ID. Enter the PASSWD command and use the
TAPE ID as the old PDT Level 2 Password.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2033 of 2360

SRPT0053
PDT: Could not save PDT passwords.

old PDT Level 2 Password.
- for all other systems, enter the install disk in the floppy drive of the active core.
Enter PDT using the systems TAPE ID. Enter the PASSD command and use the
TAPE ID as the old PDT Level 2 Password.
Severity: Minor.
SRPT0054
SNMP trap: Yes
PDT: Passwords cannot be changed from a remote cabinet.

Action:
Severity: Info.
SRPT0055
SNMP trap: Yes
PDT: Password changes have been stored.

Action:
Severity: Info.
SRPT0056
SNMP trap: Yes
PDT: Passwords can only be changed from the active side.

Action: Check the cores state using LD 135 stat CPU. Ensure the core is the
active core. Try to change the passwords using the PASSWD command again.
Severity: Info.
SRPT0057
SNMP trap: Yes
PDT: Problem detected with password synchronize.

Action: For an Option 11C, check the connection between the main cabinet and
remote cabinets. Ensure that the main cabinet and remote cabinets have
completed their boot cycle. Try to change the passwords using the PASSWD
command again. If this fails contact your technical support group.
For Thor systems, check that both cores are available, synchronized and are
joined. Try to change the passwords using the PASWD command again. If this
fails contact your technical support group.
For CPP systems, check that the HSP is up, the systems joined and the disk are
synchronized. Try to change the passwords using the PASSWD command. If this
fails contact your technical support group.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2034 of 2360

SRPT0058
PDT: Corrupt password detected.

old PDT Level 2 Password. If this fails contact your technical support group.
Enter PDT using the systems TAPE ID. Enter the PASSWD command and use
the TAPE ID as the old PDT Level 2 Password. If this fails contact your technical
support group.
Severity: Minor.
SRPT0059
SNMP trap: Yes
PDT: Invalid password entered.

Action:
Severity: Info.
SRPT0060
SNMP trap: Yes
PDT: Unexpected error occurred during PDT password changes.

Action: Try to change the passwords again using the PASSWD command.
old PDT 2 Level Password. If this fails contact your technical support group.
Enter PDT using the systems TAPE ID. Enter the PASSWD command and use
the TAPE ID as the old PDT Level 2 Password.
If this fails contact your technical support group.
Severity: Minor.
SRPT0061
SNMP trap: Yes
LCS: JOIN denied. Incompatible memory sizes.

Action: Install the same memory in both sides.
Severity: Info.
SRPT0062
SNMP trap: Yes
Request to register TN rejected.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2035 of 2360

SRPT0063
A major error was encountered while performing the remote upgrade. A

description of the
event is contained in the error message.
Action: A manual intervention of the software upgrade process may be required.
Contact your
Severity: Major.
SRPT0064
SNMP trap: Yes
FBF: Failed to run FBF task because %s at %s.No. of Restarts = %d.

Severity: Minor.
SRPT0065
SNMP trap: Yes
FBF: FBF: FBF could not receive message because %s.

Severity: Minor.
SRPT0066
SNMP trap: Yes
FBF: could not process incoming message for application ID %d because %s .

Severity: Minor.
SRPT0067
SNMP trap: Yes
FBF: Unable to send message to the other side because %s Intended

Message destination is =%d.
Severity: Minor.
SRPT0068
SNMP trap: Yes
FBF: Could not send <f> file to the remote node for <a> Application because
<s> (error no =<n>). Problem occurred while sending message type <d>.
Where:<f>: file that cant be send<a>: application<s>: error<d>: message type
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2036 of 2360

SRPT0069
FBF: Unable to receive the complete file(s) [%s] from the remote node
because %s (error no. = 0x%x). Problem occurred on receiving %d message
type.
Severity: Minor.
SRPT0070
SNMP trap: Yes
IISM: Could not reset file [%s] because %s fd = %d, Error Number = %d.
Severity: Minor.
SRPT0071
SNMP trap: Yes
IISM: IISM could not be initialized because %s Dir. Pointer for [%s] is
0x%x,File Desc. For file [%s] is %d and open error number is 0x%x.
Severity: Minor.
SRPT0072
SNMP trap: Yes
IISM: Retransmission limit reached for file [%s]. File size acknowledged by the
remote node = %d.
Severity: Minor.
SRPT0073
SNMP trap: Yes
A problem was detected while performing the Centralized Software Upgrade.

A description of the event is
contained in the error message.
Action: The Centralized Software Upgrade feature is trying to recover from the
event, if the event repeats
itself, a manual intervention of the Centralized Software Upgrade process may be
required. Contact your
Severity: Minor.
SRPT0074
SNMP trap: Yes
IISM: IISM could not send the message to the remote node because %s.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2037 of 2360

SRPT0075
IISM: IISM failed to move all files. Some files may not have been copied
properly.
Action: Repeat the operation in Overlay 143. If this fails, contact your technical
support group.
Severity: Minor.
SRPT0076
SNMP trap: Yes
IFBF: Failed to initialize FBF because %s FBF task ID = 0x%x and Application
= %s.
Severity: Minor.
SRPT0077
SNMP trap: Yes
Progress information for the Centralized Software Upgrade feature.

Action:
Severity: Info.
SRPT0078
SNMP trap: Yes
IISM: Unable to %s [%s] file for error = 0x%x.

Severity: Minor.
SRPT0079
SNMP trap: Yes
IISM: File transfer failed. Retry. FBF failed to send file for App ID %d
parameter = %d, srcFile = [%s], tarFile = [%s].
Severity: Minor.
SRPT0080
SNMP trap: Yes
ISM: Operation on [%s] file failed because %s Error Number = 0x%x, action =
%d, parm = %d, write value = %d, file size = %d.
Severity: Minor.
SRPT0082
SNMP trap: Yes
FBF: Checksum failed for file [%s] because %s Errno = %d.

Severity: Minor.
SNMP trap: Yes
System Messages
Page 2038 of 2360

SRPT0083
IISM:LCS could not send IISM Sync message. CM primary link maybe down.
Severity: Minor.
SRPT0091
SNMP trap: Yes
HB: remote side ELAN health change: <n>

Action:
Severity: Info.
SRPT0092
SNMP trap: Yes
AML: remote side AML connection <nr> to <ip> health change: <n>
Action:
Severity: Info.
SRPT0093
SNMP trap: Yes
AML: local side AML connection <nr> to <ip> health change: <n>
Action:
Severity: Info.
SRPT0094
SNMP trap: Yes
LCS: Cannot switchover: ELAN health better on remote side but hardware
better on local.
Action:
Severity: Info.
SRPT0095
SNMP trap: Yes
HIREM: <object> on remote side <side> is Out Of Service.

Action:
Severity: Info.
SRPT0096
SNMP trap: Yes
HIREM: <object> on remote side <side> is In Service.

Action:
Severity: Info.
SRPT0098
SNMP trap: Yes
Read from side <n> hard disk failed.

Read from remote side <n> successful.
where <n> local/remote side number [0..1]
Action: The local hard disk has bad sectors and should be replaced.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2039 of 2360

SRPT0099
Read from side <n> hard disk failed.

Read from remote side <n> unsuccessful.
where <n> local/remote side number [0..1]
Action: The local hard disk has bad sectors and should be replaced.
Severity: Critical.
SRPT0100
SNMP trap: Yes
CMDU on side <s> is Out Of Service. Please check CMDU where s = 0,1.
Action: Check CMDU on side <s>.
Severity: Critical.
SRPT0101
SNMP trap: Yes
LCS: CMDU on inactive side <s> is Out Of Service. Going to split mode where
s = 0,1
Action: Check CMDU on side <s>.
Severity: Critical.
SRPT0102
SNMP trap: Yes
CMDU on side <s> is Out Of Service. Please check CMDU where s = 0,1
Action: Check CMDU on side <s>
Severity: Critical.
SRPT0103
SNMP trap: Yes
DR: Core side %d cannot continue to send disk updates to inactive side.
Severity: Critical.
SRPT0104
SNMP trap: Yes
DR: Cannot send disk update messages to %s, errno [0x%x]. Queue is full.
Disk resync will be attempted.
Action: If resync does not complete, try restart disk sync manually by INI the
inactive side. Contact your technical support
Severity: Major.
SRPT0105
SNMP trap: Yes
Sync was requested, but CPM has continued to perform update.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 2040 of 2360

SRPT0106
LCS: Join denied. Incompatible IRQ order between both sides.

Severity: Major.
SRPT0108
SNMP trap: Yes
VO login Password retry failed 3 times. Tried to login as TN: 0x%x on the set
TN: 0x%x.
Action: Let the login lock expire in one hour, or disable/enable the set to login
through LD 32.
Severity: Minor.
SRPT0109
SNMP trap: Yes
LCS: Join Operation Aborted Due To CNI Objects Mismatch Between Core 0
And Core 1.Use stat cni command in overlay 135 to see CNI objects.
Action: Check that both sides have the same number of CNIs configured
Severity: Info.
SRPT0110
SNMP trap: Yes
CM: Primary client connection established.

Action:
Severity: Info.
SRPT0111
SNMP trap: Yes
DR: Recovered the message queue (%s) and disk resynchronization has been
initiated.
Severity: Major.
SRPT0115
SNMP trap: Yes
HIREM: Can't prevent graceful SWO while adding network groups.

Severity: Critical.
SRPT0116
SNMP trap: Yes
CM: Primary server restarted

Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2041 of 2360

SRPT0117
CM: Server connection established.

Action:
Severity: Info.
SRPT0118
SNMP trap: Yes
CM: Server connection lost.

Severity: Major.
SRPT0119
SNMP trap: Yes
CM: Retrying server initialization.

Severity: Critical.
SRPT0120
SNMP trap: Yes
CM: Primary client recovery failed.

Severity: Critical.
SRPT0121
SNMP trap: Yes
CM: Secondary server recovery failed.

Severity: Critical.
SRPT0122
SNMP trap: Yes
CM: Secondary client recovery failed.

Severity: Critical.
SRPT0123
SNMP trap: Yes
MIDN: Starting graceful SWO from side <a> to side <b>Where <a>,<b> : 0 , 1
Action:
Severity: Info.
SRPT0124
SNMP trap: Yes
MIDN: Can't start graceful SWO. RDUN tests returned error.

Action: Check local and remote Hard drive
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2042 of 2360

SRPT0125
MIDN: Can't start graceful SWO. Local health is better than remote health.
Action:
Severity: Info.
SRPT0126
SNMP trap: Yes
DR: Not allowed to sync while already syncing.

Action:
Severity: Info.
SRPT0127
SNMP trap: Yes
LCS: Graceful switchover unsuccessful. Stop&Copy failed.

Severity: Critical.
SRPT0129
SNMP trap: Yes
LCS: Graceful switchover can't be performed. SWO is locked.

Severity: Major.
SRPT0130
SNMP trap: Yes
LCS: Graceful switchover successful. LcsSCDone message lost.

Action:
Severity: Minor.
SRPT0131
SNMP trap: Yes
CM: Primary client can't connect to the other side

Action: Check HSP connection
Severity: Major.
SRPT0134
SNMP trap: Yes
DPSDL: Received Null Message In dpsdlProcess\n

Action:
Severity: Info.
SRPT0135
SNMP trap: Yes
DPSDL: sendMsg is Null in dpsdlSend \n

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2043 of 2360

SRPT0136
DPSDL: cmPrimarySend failed for the Message Type %d \n

Action:
Severity: Info.
SRPT0137
SNMP trap: Yes
DPSDL: FTP failed for three attempts\n

Action:
Severity: Info.
SRPT0138
SNMP trap: Yes
DPSDL: dpsdlSendMessage failed for Message type %d\n

Action:
Severity: Info.
SRPT0139
SNMP trap: Yes
DPSDL: The file [%s] cannot be found, ErrNo is %d \n

Action:
Severity: Info.
SRPT0140
SNMP trap: Yes
DPSDL : Null pointer generated from making the network file copy key.
Action:
Severity: Major.
SRPT0141
SNMP trap: Yes
DPSDL : Cannot set task delay for network file copy.

Action:
Severity: Minor.
SRPT0142
SNMP trap: Yes
DPSDL : Network file copy result: TOTAL SUCCESS.

Action:
Severity: Info.
SRPT0143
SNMP trap: Yes
DPSDL : Network file copy result: PARTIAL SUCCESS.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 2044 of 2360

SRPT0144
DPSDL : Network file copy result: TOTAL FAILED.

Action:
Severity: Info.
SRPT0145
SNMP trap: Yes
DPSDL: Unable to open or create the file %s, ErrNo is %d\n

Action:
Severity: Info.
SRPT0146
SNMP trap: Yes
DPSDL: Unable to remove the file [%s], ErrNo is %d\n.

Action:
Severity: Info.
SRPT0147
SNMP trap: Yes
DPSDL: Unable to rename the file [%s] as [%s], ErrNo is %d\n.

Action:
Severity: Info.
SRPT0148
SNMP trap: Yes
DPSDL: During the next join the Psdl Files will be Synced to the other side \n.
Action:
Severity: Info.
SRPT0149
SNMP trap: Yes
DPSDL: Unable to Backup the PSDL Files on the Inactive side.

Action:
Severity: Info.
SRPT0150
SNMP trap: Yes
DPSDL: Started Syncing the PSDL Files to the other side.

Action:
Severity: Info.
SRPT0151
SNMP trap: Yes
DPSDL: PSDL Sync is completed \n.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2045 of 2360

SRPT0152
DPSDL: Please use the command 'dpsdlSync' to sync the PSDL files \n.
Action:
Severity: Info.
SNMP trap: Yes
SRPT0153 RST <d1> WARM START IN PROGRESS - Reason <d2>.Trap Data Block not saved.
where d = CPU side [0..1]
d2 = Reason for restart
Action:
Severity: Info.
SRPT0154
SNMP trap: Yes
Disk synchronization has failed. The remote core side %d has a better disk
image.
Action: Switch to core side %d before joining the cores. Contact your technical
support.
Severity: Major.
SRPT0155
SNMP trap: Yes
Disk synchronization has been aborted. Core side %d has a better disk image.
Action: Switch to core side %d before joining the cores. Contact your technical
support.
Severity: Major.
SRPT0156
SNMP trap: Yes
DPSDL : Network file copy result: UNKNOWN.

Action:
Severity: Major.
SRPT0158
SNMP trap: Yes
DPSDL : Error in setting up file for network file copy.

Action:
Severity: Major.
SRPT0159
SNMP trap: Yes
DPSDL : Cannot free the allocated memory.

Action:
Severity: Major.
SNMP trap: Yes
System Messages
Page 2046 of 2360

SRPT0160
PDT: TTY device name get error, fd, errno.

Severity: Minor.
SRPT0161
SNMP trap: Yes
PDT: TTY device write error, fd, errno, nbytes, wbytes.

Severity: Minor.
SRPT0162
SNMP trap: Yes
PDT: TTY device read error, fd, errno, nbytes, rbytes.

Severity: Minor.
SRPT0163
SNMP trap: Yes
PDT: TTY device read/write flush error, fd, errno.

Severity: Minor.
SRPT0164
SNMP trap: Yes
PDT: Task (task name) being deleted, tid.

Action:
Severity: Info.
SRPT0165
SNMP trap: Yes
PDT: Task (task name) being restarted, tid.

Action:
Severity: Info.
SRPT0166
SNMP trap: Yes
PDT: Task (task name) is in suspended status, tid.

Action:
Severity: Info.
SRPT0167
SNMP trap: Yes
PDT: Network peer information (description) get error, fd, errno, parm1.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2047 of 2360

SRPT0168
PDT: Network socket read error, fd, errno, nbytes, rbytes.

Severity: Minor.
SRPT0169
SNMP trap: Yes
PDT: Network socket write error, fd, errno, nbytes, wbytes.

Severity: Minor.
SRPT0170
SNMP trap: Yes
Detected file operation error.

Severity: Major.
SRPT0171
SNMP trap: Yes
Detected invalid server IP address [x.x.x.x], ignoring entry.

Action: Verify node configuration of server entries is correct.
Severity: Minor.
SRPT0172
SNMP trap: Yes
STARTUP: MAIN_CAB rejects the request for configuration data.

Action:
Severity: Info.
SRPT0173
SNMP trap: Yes
STARTUP: Unable to request configuration data from MAIN_CAB.

Action:
Severity: Info.
SRPT0174
SNMP trap: Yes
STARTUP: EXP_CABregistration denied. Unconfigured IP address

nnn.nnn.nnn.nnn.
Action:
Severity: Info.
SRPT0175
SNMP trap: Yes
STARTUP: EXP_CAB n registration denied. Unauthorized ID. Serial No.

xxxxx.
Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 2048 of 2360

SRPT0176
SSD: Out of memory to accept connection from EXP_CABn IP

nnnn.nnnn.nnnn.nnn.
Action:
Severity: Info.
SRPT0177
SNMP trap: Yes
STARTUP: "EXP_CAB" [%d] registration has been granted. IP a and Serial

Nos
Action:
Severity: Info.
SRPT0178
SNMP trap: Yes
STARTUP: Failed to initialize the IPMG Controller task. Errno=n

Action:
Severity: Info.
SRPT0179
SNMP trap: Yes
STARTUP: IPMG Controller task completed successfully.

Action:
Severity: Info.
SRPT0180
SNMP trap: Yes
STARTUP: Failed to initialize the CPU status display task. Errno=n

Action:
Severity: Info.
SRPT0181
SNMP trap: Yes
XSM: Alarm signal detected - check the Power/Fan module or the System
Monitor module (XSM).
Action:
Severity: Info.
SRPT0182
SNMP trap: Yes
QOS rating for link X is POOR.

Action: Check the overall TLAN subnet or adjust the PDV buffer size.
Severity: Minor.
SRPT0183
SNMP trap: Yes
XSM: Alarm signal cleared.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2049 of 2360

SRPT0184
STARTUP: Received incorrect configuration data. Data is for cabinet

n.Assigned cabinet number is m.
Action:
Severity: Info.
SRPT0185
SNMP trap: Yes
STARTUP: Pointer passed to get IPMG configuration data is null.

Action:
Severity: Info.
SRPT0186
SNMP trap: Yes
STARTUP: Failed to get IPMG configuration data from SL1 for cabinet %d.
Action:
Severity: Info.
SRPT0187
SNMP trap: Yes
IPMG VXCT parameter download error.

Action: Restart IPMG. Contact Nortel representatives if occuring repeatedly.
Severity: Minor.
SRPT0188
SNMP trap: Yes
IPMG: FCAD table download error.

Action: Restart IPMG. Contact Nortel representatives if occuring repeatedly.
Severity: Major.
SRPT0189
SNMP trap: No
Not enough BW for call between <origTN> and <termTN>

Action: Check how much bandwidth is actually used.
Severity: Info.
SRPT0190
SNMP trap: Yes
Health update message was not sent to MC/SS (line xx of yy, connectID: zz).
Memory (malloc) failure" where xx is connection entry number, yy is the
number of connections and zz is connection ID
Action: If this problem reoccurs, report the problem to Nortel.
Severity: Info.
SRPT0191
SNMP trap: Yes
Near end VPNI and Zone are the same as Far end VPNI and Zone.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2050 of 2360

SRPT0192
AML link number (%d) failed to respond to ping, n (%d) times.

Action: Check the AML link connectivity to the call server.
Severity: Info.
SRPT0194
SNMP trap: Yes
Default Password Warning : ww, xx

Action:
Severity: Major.
SRPT0195
SNMP trap: Yes
Force Password Change activated

Action: The system passwords must be changed on the next log on
Severity: Major.
SRPT0196
SNMP trap: Yes
Expired Password(s) ww xx yy zz
Action: Change the expiring password(s) to continue the session.
Severity: Major.
SRPT0197
SNMP trap: Yes
Function s is not implemented in DRAMOS

Action:
Severity: Info.
SRPT0200
SNMP trap: Yes
Received power monitor status from IPMG [%d] - status register [0x%x]
Action: Please check the power supply in the IPMG. However, if problem
persists, please contact Nortel support.
Severity: Major.
SRPT0201
SNMP trap: Yes
File and/or directory operation errors detected

Action: Verify the insecure shell login access settings are correct.
Severity: Major.
SRPT0202
SNMP trap: Yes
Problem detected with insecure shell access setting synchronization between

the CPP system cores.
Action: Check that the HSP is up, the systems are joined and the disks are
synchronized.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2051 of 2360

SRPT0203
Release Link Trunks Provisioning mismatch detected between the CS 1000

and the CS 2000 or CS 2100.
Action: Either disable RLT on the side where it is enabled, or enabled on the
side where it is disabled.
Severity: Info.
SRPT0730 x y z
SNMP trap: No
OS x cold start. Release y. Created z.

Action:
Severity: Minor.
SRPT0731 x y z
SNMP trap: Yes
OS x warm start. Release y. Created z. Last cold start: date. Last warm start:
date
Action:
Severity: Minor.
SRPT0750
SNMP trap: Yes
INI x: on side x due to cold start.

Action:
Severity: Minor.
SRPT0751
SNMP trap: Yes
INI x: on side x due to {reason}. Previous INI: {side} due to {reason}. INIs since
switchover: x . INIs since cold start: x
Action:
Severity: Minor.
SRPT0752
SNMP trap: Yes
INI x: INI completed in y seconds.

Action:
Severity: Minor.
SRPT0754
SNMP trap: Yes
INI due to "x". Previous INI: "y". INIs since cold start: z
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2052 of 2360

SRPT0770
TOD x: Midnight job server starts on side x. Number of jobs to do: y.

Action:
Severity: Minor.
SRPT0772
SNMP trap: No
TOD x: Skipping midnight job {name}.

Action:
Severity: Minor.
SRPT0773
SNMP trap: No
TOD x: Starting midnight job {name}.

Action:
Severity: Minor.
SRPT0774
SNMP trap: No
TOD x: Midnight jobs completed on side x.

Action:
Severity: Minor.
SRPT0781
SNMP trap: No
RST x: Warm Start in progress. Reason: {x}

Action:
Severity: Minor.
SRPT0785
SNMP trap: Yes
RST x: Task being deleted. Task ID {name}.

Action:
Severity: Minor.
SRPT0790
SNMP trap: No
RS x: SL-1 requested warm start - INIT reason {x}.

Action:
Severity: Major.
SRPT1000
SNMP trap: No
Incorrect security device.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2053 of 2360

SRPT1020
CardLAN: connection x closed.

Action:
Severity: Info.
SRPT1021
SNMP trap: No
CardLAN: Server socket x created.

Action:
Severity: Info.
SRPT1022
SNMP trap: No
CardLAN: Connection x accepted with socket x.

Action:
Severity: Info.
SRPT1023
SNMP trap: No
100 BaseT: Configuration is provided from iprem.db database in the reported

directory.
Action:
Severity: Info.
SRPT1024
SNMP trap: No
100 BaseT: Configuration is from defaulted values.

Action:
Severity: Info.
SRPT4500 x
SNMP trap: Yes
Skipping slot X. Cannot calculate address to check for CP with cable.

Action:
Severity: Minor.
SRPT4501 x
SNMP trap: Yes
Skipping slot X. Cannot get card ID.

Action:
Severity: Minor.
SRPT4502
SNMP trap: Yes
CP Single Mode: Timeout waiting for response from remote CP.

Action: Check that both CPs have the same number of SIMMs.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2054 of 2360

SRPT4503
CP Single Mode: Remote processor is not CP.

Action: Be sure remote processor is CP.
Severity: Minor.
SRPT4504
SNMP trap: Yes
CP Single Mode: CP redundancy impossible. No CP to CP cable.

Action:
Severity: Minor.
SRPT4505
SNMP trap: Yes
CP Single Mode: CP redundancy impossible. There is no remote power.

Action: Check CE power supply on remote Core module. Be sure the CP to CP
cable is properly connected.
Severity: Minor.
SRPT4506
SNMP trap: Yes
CP Single Mode: CP redundancy impossible. Both shelves have the same ID.
Action: Set the JB4 jumper on the backplane so both sides match.
Severity: Minor.
SRPT4507
SNMP trap: Yes
CP Single Mode: CP redundancy impossible. Both switches are in MAINT.

Action: Check that at least one of the CP Norm/Maint switches in Norm mode
(up).
Severity: Minor.
SRPT4508
SNMP trap: Yes
CP Single Mode: could not synchronize CSA space.

Action:
Severity: Minor.
SRPT4509
SNMP trap: Yes
Could not set CP semaphore bit (side x).

Action:
Severity: Minor.
SRPT4510
SNMP trap: Yes
CP Single Mode: memory shadow test failed.

Action: Reseat or replace the Standby CP.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2055 of 2360

SRPT4511 x
Cannot open BIC window (slot x). Cannot check for CP cable.
Action:
Severity: Minor.
SRPT4512 x
SNMP trap: Yes
Cannot close BIC window (slot x).

Action:
Severity: Minor.
SRPT4513 x
SNMP trap: Yes
Could not get CP semaphore bit (side x).

Action:
Severity: Minor.
SRPT4514 x
SNMP trap: Yes
Skipping slot x, cannot calculate address to see if CP bit is set.

Action:
Severity: Minor.
SRPT4517 x
SNMP trap: Yes
CP: Switching from CPU x to preferred side.

Action:
Severity: Minor.
SRPT4538
SNMP trap: Yes
LDR: Inconsistencies in boundaries of previous sl1 load.

Action:
Severity: Minor.
SRPT4539
SNMP trap: Yes
LDR: Inconsistencies in boundaries of previous ovl load.

Action:
Severity: Minor.
SRPT4540
SNMP trap: Yes
LDR: Error loading SL-1 file into memory.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2056 of 2360

SRPT4541
LDR: Error loading overlay file into memory.

Action:
Severity: Minor.
SRPT4542
SNMP trap: Yes
LDR: Error in loading, last address {n}.

Action:
Severity: Minor.
SRPT4543
SNMP trap: Yes
LDR: Error returned from segInit2{n}.

Action:
Severity: Minor.
SRPT4544
SNMP trap: Yes
LDR: Error getting dloPathFileName for ovlres.

Action: Reload the system with the Manual Reload button. Reinstall software
from installation disks.
Severity: Minor.
SRPT4545
SNMP trap: Yes
LDR: Unable to open {file name}.

Severity: Minor.
SRPT4546
SNMP trap: Yes
LDR: Error sl1_start_addr {n}, last sl1_prot_address {x}.

Action:
Severity: Minor.
SRPT4547
SNMP trap: Yes
LDR: Error initializing SL-1 pool and data area.

Action:
Severity: Minor.
SRPT4548
SNMP trap: Yes
LDR: Error getting dloPathFileName for ovlres.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2057 of 2360

SRPT4549
LDR: Unable to open {file name}.

Severity: Minor.
SRPT4550
SNMP trap: Yes
LDR: Error in loading, last SL-1 address {n}.

Action:
Severity: Minor.
SRPT4551
SNMP trap: Yes
LDR: Overlay start address {n} overlaps end of SL-1 area {x}.
Action:
Severity: Minor.
SRPT4552
SNMP trap: Yes
LDR: Error ovl_start_addr {n}, last_ovl_prot_addr {x}.

Action:
Severity: Minor.
SRPT4553
SNMP trap: Yes
LDR: Error initializing overlay data area.

Action:
Severity: Minor.
SRPT4554
SNMP trap: Yes
LDR: Error calling ovlres entry.

Action:
Severity: Minor.
SRPT4555
SNMP trap: Yes
LDR: Invalid parameter to ldrNextPage, address {n}.

Action:
Severity: Minor.
SRPT4556
SNMP trap: Yes
LDR: Seek error while loading (OVL or INSTALL) code file.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2058 of 2360

SRPT4557
LDR: Error reading a_out header from file (OVL or INSTALL).

Severity: Minor.
SRPT4558
SNMP trap: Yes
LDR: Invalid a_out header in file.

Action:
Severity: Minor.
SRPT4559
SNMP trap: Yes
Error reading link header.

Severity: Minor.
SRPT4560
SNMP trap: Yes
LDR: Invalid link header in file.

Action:
Severity: Minor.
SRPT4561
SNMP trap: Yes
LDR: IModule not linked to page boundary.

Action:
Severity: Minor.
SRPT4562
SNMP trap: Yes
LDR: Seek error while loading (OVL or INSTALL) code file.

Severity: Minor.
SRPT4563
SNMP trap: Yes
LDR: Error reading a_out header into memory (OVL or INSTALL).

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2059 of 2360

SRPT4564
LDR: Error reading text segment from disk into memory (OVL or INSTALL).
Severity: Minor.
SRPT4565
SNMP trap: Yes
LDR: Error reading data segment from disk into memory (OVL or INSTALL).
Severity: Minor.
SRPT4566
SNMP trap: Yes
LDR: Seek error while loading SL-1 code.

Severity: Minor.
SRPT4567
SNMP trap: Yes
LDR: Error reading a_out file from SL-1 file.

Severity: Minor.
SRPT4568
SNMP trap: Yes
LDR: Invalid a_out header in SL-1 file.

Action:
Severity: Minor.
SRPT4569
SNMP trap: Yes
Error reading link header from file.

Severity: Minor.
SRPT4570
SNMP trap: Yes
LDR: Invalid link header in file.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2060 of 2360

SRPT4571
Module not linked to page boundary.

Action:
Severity: Minor.
SRPT4572
SNMP trap: Yes
LDR: Seek error while loading code. Reload the system with the Manual
Reload button.
Severity: Minor.
SRPT4573
SNMP trap: Yes
LDR: Error reading a_out header from disk into memory.

Severity: Minor.
SRPT4574
SNMP trap: Yes
LDR: Error reading text segment from disk into memory.

Severity: Minor.
SRPT4575
SNMP trap: Yes
LDR: Invalid data segment in SL-1 module.

Action:
Severity: Minor.
SRPT4576
SNMP trap: Yes
Error access in code file. Reload the system with the Manual Reload button.
Severity: Minor.
SRPT4577
SNMP trap: Yes
LDR: IError reading data segment from disk into memory.

Action: Reload the system with the Manual Reload button.
Severity: Minor.
SRPT4578
SNMP trap: Yes
LDR: Invalid a_out header in memory (OVL or INSTALL).

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2061 of 2360

SRPT4579
LDR: Invalid link header in memory (OVL or INSTALL).

Action:
Severity: Minor.
SRPT4580
SNMP trap: Yes
LDR: End of Protected data = x (OVL or INSTALL).

Action:
Severity: Minor.
SRPT4581
SNMP trap: Yes
LDR: Unprotected data start x overlaps Unprotected data end at y (OVL or

INSTALL).
Action:
Severity: Minor.
SRPT4582
SNMP trap: Yes
LDR: Error copying data from Protected memory to Unprotected memory for
static modules.
Action: Reinitialize the system with the INIT button.
Severity: Minor.
SRPT4583
SNMP trap: Yes
LDR: Invalid a_out header in memory.

Action:
Severity: Minor.
SRPT4584
SNMP trap: Yes
LDR: Invalid link header in memory.

Action:
Severity: Minor.
SRPT4585 x
SNMP trap: Yes
LDR: End of Protected data = x.

Action:
Severity: Minor.
SRPT4586 x y
SNMP trap: Yes
LDR: Unprotected data start x overlaps Protected data end at y.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2062 of 2360

SRPT4587
LDR:Error copying data from Protected memory to Unprotected memory for

SL-1 modules.
Action: initialize the system with the INIT button.
Severity: Minor.
SRPT4588
SNMP trap: Yes
Auxiliary processor has been reset.

Severity: Major.
SRPT4589
SNMP trap: Yes
System security device is not functioning or has been removed.

Action:
Severity: Major.
SRPT4590
SNMP trap: Yes
System security device problem has been resolved.

Severity: Info.
SRPT4591
SNMP trap: Yes
PDT: password reset successful.

Severity: Info.
SRPT4592
SNMP trap: Yes
PDT: password reset attempt failed.

Severity: Major.
SRPT4593
SNMP trap: Yes
PDT: password file restored from backup.

Severity: Info.
SRPT4594
SNMP trap: No
Unable to mount device because of Database Upgrade Tool or an

incompatible PC Card card has been inserted on device a: or b:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2063 of 2360

SRPT4595
Failed to read IOP Card Id on Core Side x.

Action:
Severity: Major.
SRPT4596
SNMP trap: Yes
IOP card are not identical

Action:
Severity: Major.
SRPT4599
SNMP trap: Yes
"KC x: " "n" " does not match the direct record. Keycode value = x, direct.rec
value = y".
Action:
Severity: Major.
SRPT4601
SNMP trap: Yes
KC: The new Keycode has been enabled.

Action:
Severity: Major.
SRPT4602
SNMP trap: Yes
KC: The new Keycode has been rejected. Use KSHO in LD 143 to check it.
Action:
Severity: Major.
SRPT4613
SNMP trap: Yes
"KC: Error. " "x" " returns with error code: y. " "z" " error".
Action:
Severity: Major.
SRPT4615
SNMP trap: No
Security Device on Core Side is missing.

Action: Check and reseat the security device.
Severity: Major.
SRPT4616
SNMP trap: Yes
Security Device on Core Side x is corrupted.

Severity: Major.
SNMP trap: Yes
System Messages
Page 2064 of 2360

SRPT4617
Security Device on Core Side x is invalid.

Severity: Major.
SRPT4619
SNMP trap: Yes
Last Archive Procedure failed. No archives were completed since last month
day hour: minute:second year.
Action: Use LD143 to perform Attended Backup (ABKO)
Severity: Info.
SRPT4620
SNMP trap: Yes
Error x while y status of last archive.

Action:
Severity: Major.
SRPT4621
SNMP trap: Yes
Results of the last Backup are not available. Reason: x.

Action:
Severity: Major.
SRPT4622
SNMP trap: Yes
Security Device on Core Side x is missing.

Action: Check and reseat security device.
Severity: Major.
SRPT4623
SNMP trap: Yes
Security Device on Core Side is corrupted.

Action: Check and reseat security device.
Severity: Major.
SRPT4624
SNMP trap: Yes
Security Device on Core Side is invalid.

Severity: Major.
SRPT4628
SNMP trap: Yes
Keycode file {file name} has wrong format.

Action: Check that the correct keycode is used.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2065 of 2360

SRPT4631
Secondary Call Server in INACTIVE state.

Action:
Severity: Info.
SRPT4632
SNMP trap: Yes
Secondary Call Server in ACTIVATING state.

Action:
Severity: Minor.
SRPT4633
SNMP trap: Yes
Secondary Call Server in CALMDOWN state.

Action:
Severity: Info.
SRPT4634
SNMP trap: Yes
Secondary Call Server in ACTIVE state.

Action:
Severity: Major.
SRPT4635
SNMP trap: Yes
Secondary Call Server in DEACTIVATING state.

Action:
Severity: Info.
SRPT4636
SNMP trap: Yes
Secondary Call Server in OUTOFLICENSE state.

Action: Contact your technical support group to reinstall the software.
Severity: Major.
SRPT4637
SNMP trap: Yes
Error writing to Secondary Call Server state file.

OUTOFLICENSE, contact your technical support group to reinstall the software.
Severity: Major.
SRPT4638
SNMP trap: Yes
Error closing Secondary Call Server state file.

OUTOFLICENSE, contact your technical support group to reinstall the software.
Severity: Major.
SNMP trap: Yes
System Messages
Page 2066 of 2360

SRPT4639
FTP to <IP address> failed on <command>, code=xxx,

attempt=xx, errno=0xXXXX."
Where Command may be:
bin
put <file name> <remote file name>
rename <old file name> <new file name>
open session
The specified FTP operation
to the specified IP address
failed.
Action: Verify FTP connection / remote hard disk accessibility
Severity: Info.
SRPT4640
SNMP trap: Yes
Attempt to perform remote Backup to another CS failed.

Action: Verify FTP connection / remote hard disk accessibility
Severity: Major.
SRPT4641
SNMP trap: Yes
Data to be restored has SW version <data version> which is newer than

<current software version>. An attempt to restore data from newer S/W
version was made. Restore is rejected.
Action: Verify the database used for restore and the current software version of
the switch.
Severity: Major.
SRPT4642
SNMP trap: Yes
Data to be restored has SW version <data version> which is older than

<current software version>. Data from older SW version is restored
Action: None
Severity: Info.
SRPT4643
SNMP trap: Yes
New backup data file arrived at hh:mm on mm dd, yyyy. A new backup data
arrived from the Primary CS at specified time and date
Action: None
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2067 of 2360

SRPT4644
Can not read/change Secondary Call server state file attributes

Action: Verify hard disk accessibility; if the call server went out of license,
reinstall the software
Severity: Major.
SRPT4645
SNMP trap: Yes
The system will automatically be restarted forData Endorsement

The system will automatically be restarted for the restored Data Endorsement
Action: None
Severity: Info.
SRPT4646
SNMP trap: Yes
The system will automatically be restarted for Data Stepback.

Data Endorsement failed. The system will automatically SWAP for stepback to
the previous data and then will automatically restart.
Action: None
Severity: Major.
SRPT4647
SNMP trap: Yes
FTP Client operation timed out (xx seconds expired).

Action: See the following SRPT4639 error report for more details.
Severity: Info.
SRPT4648
SNMP trap: Yes
Attempt to perform Backup to remote FTP server failed.

Action: Verify FTP connection / remote hard disk accessibility.
Severity: Minor.
SRPT4649
SNMP trap: Yes
Attempt to perform incremental backup to local Fix Media Device failed.

Action: Verify Fix Media Device accessibility.
Severity: Minor.
SRPT4650
SNMP trap: Yes
Attempt to perform incremental backup to local Removable Media Device

failed.
Action: Verify Removable Media Device accessibility.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2068 of 2360

SRPT4651
Attempt to perform Restore from remote FTP server failed

Action: Verify FTP connection / remote hard disk accessibility.
Severity: Major.
SRPT4652
SNMP trap: Yes
System Memory Low <number> Bytes Remaining

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2069 of 2360
SYS: System Loader

This program is loaded into memory whenever a complete program and data
load is required. SYSLOAD occurs when:
The system is powered-on.
The system RESET button is pressed.
The RELOAD buttons on the Changeover and Memory Arbitrator cards are
pressed simultaneously.
A CE fault or power failure has caused some of the system memory contents
to be destroyed.
This program loads all call processing programs and office data from the
storage device into system memory. During this procedure, it diagnoses all
memory faults and presents fault information on any TTY which is equipped.
When the loading is complete (5 to 25 minutes):
this program is erased from memory
the initialize program (INI) is run
call processing commences
Format of SYS messages
SYS messages are formatted as SYSxxx to indicate a warning message and
SYSxxx FATAL to indicate a fatal error requiring hardware replacement.
Warning messages may be followed by an additional field indicating program
number, terminal number (TN), customer data block (CDB) number, route data
block (RDB) number, etc., of the data block in error.
The general format of Generic X11 SYSLOAD SYSLOAD Error error
messages is:
SYSxxx dsid dsindex
where:
dsid = the data structure identifier
dsindex = the data structure index number.
Messages
SYS0000
SYSLOAD has taken place. For Omega machines, output may be one of:
1. SYS0000 0500 = Machine may have been switched on with a tape or disk
in place.
2. SYS0000 CPU x = SYSLOAD controller switch from one CPU to the other,
subsequent to SYS0000 {source} {...(see below).
3. SYS0000 {source} {page} {addr} {dis} code {prev} CPU x.
4. SYS0000 {source} {addr} {dis} CODE {prev} CPU x
Where: {source} = cause of SYSLOAD. Given only if a fault is detected.
{source} may be one of:
0400 = Power-on reset
System Messages
Page 2070 of 2360

0803 = Network disconnected from CPU (faulty connection from SBE to
network or defective or disabled SBE; SL-1 XN only)
0805 = Soft switch
1000 = Parity error
2000 = Watchdog
4000 = Write-protect violation
8000 = Response timeout
{page} = Fault page (4-digits hexadecimal)
{addr} = Fault address (4 to 6 digits hexadecimal)
{dis} = Last maintenance code digit display (2-digits hexadecimal) CODE
{prev} = previous history fault.
May be one of:
001X-Extender-generated bus fault
002X-Page 0 memory test fault
003X-Memory page decoding fault
004X-Switch CPU fault
CPU x = CPU number used for SYSLOAD
For C types machines (81, 81C, 61C and 51C) machines, output is as follows:
Format of the message is: xxyy 0 {addr} {dis} CPU z
Where: xx = cause of SYSLOAD. Given only if a fault is detected. xx is one the
following HEX numbers:
04 = Hardware reset (i.e. Powerupt or manual reset)
08 = Software reset (i.e. not a hardware reset and not a sanity reset)
20 = Sanity reset (i.e. Hardware watchdog timer timed out)
Where: yy = is the most recent trap source, set to one of the following HEX
codes:
21 Hardware Sanity Timeout
22 SWO: Failure on switchover
23 SWO: Too many switchovers
24 WARM: Disk OS Warmstart failure
25 WARM: Too many Disk OS Warmstarts
26 WARM: Disk OS not loaded
27 RESET: Forced Switchover in progress
28 RESET: Soft Reset in progress
29 TASK: Unable to create msg queue
2A Protected Memory checksum failure
2B INFO: Disk OS Warmstart begins
2C INFO: DRAM is uninitialized
2D Restart: Can't delete safe task
2E RESET: Task threshold exceeded
2F WARM: Exception vector threshold exceeded
30 WARM: total Exception threshold exceeded
31 WARM: Non-bus error exception in interrupt
553-3001-411
Standard 15.00
January 2006
Page 2071 of 2360

32 WARM: Exception handling already busy
33 WARM: Exception call to RestartTask() failed
34 RESET: Manual INIT requested
35 SEG: Checksum failure detected
36 SEG: Disk OS Text segment corrupted
37 SEG: Disk OS partitions corrupted
38 DISKOS: Unable to load SL1
39 DISKOS: Unable to start SL1
3A INSTALL: reboot after installation
3B IOP Bus Error on active IOP
3C Parity Error on both sides
3D Parity Error in Split mode
3E Parity Error - remote SIMM: missing
3F Parity Error - remote SIMM: disabled
40 HI: bus error recommended action
41 HI: bus error TASK_RESTART for safe task
42 HI: Warm Start not possible
43 SWD expired for task with Warmstart option
{44 - 48 unused}
49 OS: manual (PDT) request (TRP)
4A OS: request to reboot (sysToMon) (reboot x)
4B OS: Reset task initialization failed
4C OS: Scheduler initialization failed
4D OS: S/W watchdog initialization failed
4E OS: Protected Memory initialization failed
4F OS: Security Cartridge check failed
50 OS: Normal recovery from bus error
51 OS: Unable to recover from bus error
52 OS: Unable to run "diskos"
53 OS: Unable to load "diskos"
54 OS: Disk volume initialization failed
55 OS: SCSI initialization failed
56 OS: DOS file system initialization failed
57 OS: IOP initialization failed
58 OS: Exception handlers initialization failed
59 OS: IO subsystem initialization failed
5A OS: Clock initialization failed
5B OS: Failed during Loader run
5C OS: Failed to spawn Loader task
5D OS: kernel initialization failed
5E OS: diskos Prot mem seg overlaps Unprot mem seg
5F Operating System level command to coldstart.
System Messages
Page 2072 of 2360

{addr} - Fault address (4 to 8 digits hexadecimal)
{dis} = Last maintenance code digit display (2 digits hexadecimal)
CPU z = CPU number used for SYSLOAD
Action:
Severity: Critical.
SYS0002 FATAL
SNMP trap: Yes
Configuration record not found. The system is not able to load with this storage
medium. Replace active storage medium with backup.
Action: Press RESET button (or both RELOAD button (or both RELOAD buttons
simultaneously) to restart the SYSLOAD.
Severity: Critical.
SYS0012
SNMP trap: Yes
TBAR Package is not equipped. FTOP in CDB reset to FRES.

Action:
Severity: Info.
SYS0013
SNMP trap: No
% Cannot load UIPE JTTC data when JTTC package (#335) is restricted.
Action:
Severity: Info.
SYS0014
SNMP trap: No
Existing data removed because FCDR package is restricted.

Action:
Severity: Info.
SYS0015
SNMP trap: Yes
JTTC Package is not equipped; data lost.

Action:
Severity: Critical.
SYS0016
SNMP trap: Yes
DMWI package removed since neither MW, IDA or DPNSS package is

equipped.
Action: Equip with the appropriate package.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2073 of 2360

SYS0017
Only digital consoles can have an IADN.

Action:
Severity: Minor.
SYS0022
SNMP trap: Yes
The Path Replacement RCAP (PRI/PRO) is removed because the QSIG SS

package #316 is restricted.
Action:
Severity: Minor.
SYS0023
SNMP trap: Yes
All QSIG Supplementary services RCAP are removed since the GF package
is not equipped.
Action: Equip package 305. Sysload and reconfigure the QSIG RCAP for
supplementary services.
Severity: Critical.
SYS0025
SNMP trap: Yes
A loss plan structure was found in illegal state.

Action: Call the manufacturer.
Severity: Major.
SYS0026
SNMP trap: No
No cards were specified in transfer of the data from card.db file. Transmission
will be adversely affected.
Severity: Major.
SYS0027
SNMP trap: No
Invalid message type detected when transferring an attribute (attr) file data.
Transmission will be adversely affected.
Severity: Major.
SYS0028
SNMP trap: No
Too many GTDs were specified in the attr.db file loaded.

Action: Call the manufacturer
Severity: Major.
SNMP trap: No
System Messages
Page 2074 of 2360

SYS0029
The starting GTD specified in the attr.db file was beyond the limit in the
system.
Severity: Major.
SYS0030
SNMP trap: No
No GTD definitions were supplied. Transmission will be adversely affected.

Severity: Major.
SYS0031
SNMP trap: No
The ending GTD specified in the attr.db file was beyond the limit in the system.
Action: Call the manufacturer
Severity: Major.
SYS0032
SNMP trap: No
Memory could not be allocated for storing TNs for GDLS default port type
allocation.
Severity: Major.
SYS0033
SNMP trap: No
No list of TNs for default port type allocation was found.

Severity: Minor.
SYS0034
SNMP trap: Yes
A problem occurred during the reading of the GDLS loss plan files.
Severity: Major.
SYS0036
SNMP trap: No
CNAME package has been automatically turned off because the system is not
equipped with the CPND package.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2075 of 2360

SYS0037
CMOD unit data is discarded because the system is CNUMB AND CNAME
package restricted.
Severity: Major.
SYS0039
SNMP trap: Yes
ICS MFS package equipped and CIST package not equipped.

Action: Enable the CIST package and reload the system.
Severity: Critical.
SYS0040
SNMP trap: Yes
I/O device number 0 is incorrect type. An error has been made in the data on
the storage medium.
Action:
Severity: Critical.
SYS0041
SNMP trap: Yes
I/O device number 1 is incorrect type. An error has been made in the data on
the storage medium.
Action:
Severity: Critical.
SYS0042
SNMP trap: Yes
CMOD list is not created due to a lack of memory.

Action: Contact the distributor and request the expansion of the system memory
size.
Severity: Major.
SYS0043
SNMP trap: Yes
Invalid CMOD unit number (i.e. >31) is encountered. CMOD unit is not added
into the system CMOD list.
Action: A system memory corruption might have occurred. Contact your
Severity: Major.
SYS0050
SNMP trap: No
CPU has no spare memory module.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2076 of 2360

SYS0051
DMI entry has been discarded due to a missing FNP (160) package
Severity: Info.
SYS0052
SNMP trap: Yes
SIDE is defined on a DASS2 route but the MMCS package is not equipped.
Action:
Severity: Critical.
SYS0053
SNMP trap: Yes
Microcellular packages restricted. Mobility related data will be removed from

database.
Action: For Microcellular/Mobility, packages 302 (.MOSR) and 303 (.MMO) are
required. Contact your technical support group.
Severity: Major.
SYS0054
SNMP trap: Yes
Mobility related data blocks are removed. Possibly, superloop does not exist.
Severity: Major.
SYS0055
SNMP trap: Yes
Invalid value in the EBLN ISM parameter.

Action:
Severity: Minor.
SYS0060
SNMP trap: Yes
CPU has no spare memory module. Too many logical units, TDS or MFSD
loops for I/O table.
Action:
Severity: Critical.
SYS0061
SNMP trap: Yes
RCAP CTO or ECTO is removed during sysload because BNE package is not
equipped.
Action:
Severity:
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2077 of 2360

SYS0062
MSMN Package unrestricted with MC32 package #350 restricted.

Action:
Severity: Minor.
SYS0063
SNMP trap: Yes
Invalid data found while building DMC Index table for DCS units.
Action:
Severity: Major.
SYS0064
SNMP trap: Yes
Invalid data found while building DMC Index table for DCS units.
Action:
Severity: Major.
SYS0065
SNMP trap: Yes
Unable to allocate the FDL_STRUCT.

Action:
Severity: Info.
SYS0066
SNMP trap: No
FXS info is present, but the FXS package is not equipped.

Action: Sysload again with FXS package #152 equipped.
Severity: Critical.
SYS0067
SNMP trap: Yes
Survivability ISM exceeds Survivability ISM limit.

Action:
Severity: Info.
SNMP trap: No
SYS0068 <Key#> TN <TN#> BCS data block limits have caused some keys above <key#> on TN
<TN#> to be discarded.
Action:
Severity: Info.
SYS0069
SNMP trap: Yes
BCS block overflow. Some keys will be deleted.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2078 of 2360

SYS0070 FATAL
Primary storage medium fault. Storage medium not ready or head fault
detected.
Action:
Severity: Critical.
SYS0071
SNMP trap: Yes
A record could not be read from storage medium. A storage medium fault is
indicated. System may still load, even though data or programs are missing.
Action:
Severity: Critical.
SYS0072
SNMP trap: Yes
A storage device function timed out. A fault in the storage device interface (TI
or MSI) or storage device (TU or MSU) is indicated. System may still load even
though data or programs are missing.
Action:
Severity: Critical.
SYS0073
SNMP trap: Yes
Data could not be accessed from one tape track or disk address. A fault in the
storage device interface (TI or MSI) or storage device (TU or MSU) is
indicated. System may still load even though data or programs are missing.
Action:
Severity: Critical.
SYS0074
SNMP trap: Yes
Predefined set-to-set messages for the selected language cannot be loaded

from the disk.
Action: Select another language and report the problem to the vendor.
Severity: Major.
SYS0075
SNMP trap: Yes
Unable to allocate protected memory for predefined set-to-set messages.

Severity: Major.
SYS0076
SNMP trap: Yes
Either the Set-to-Set message package, or the M3900 Phase III Productivity
Enhancement package is not equipped.
Action: Turn on package 380 or 386 if the feature is required.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2079 of 2360

SYS0077
The customer data block number read from the tape record header, was found
to be greater than the customer pointer array size.
Severity: Major.
SYS0078
SNMP trap: Yes
An STS_MSG data structure was loaded from tape, but a corresponding

customer data block to reference this structure does not exist.
Severity: Major.
SYS0107
SNMP trap: Yes
An STS_MSG data structure was loaded from tape, but the STS_MSG data
block does not exist for the corresponding customer.
Severity: Major.
SYS0108
SNMP trap: Yes
Fatal error .ACDE_Package has been disabled. Only 240 queues can be
loaded.
Action: Load the switch with the default database of 240 ACD DNs/CDNs or
enable ACDE_PKG.
Severity: Critical.
SYS0109
SNMP trap: Yes
The number of Wireless Visitors exceeds the Wireless Visitors limit and no
further Wireless Visitors can be sysloaded.
Severity: Info.
SYS0110 l s c u
SNMP trap: Yes
The set at this TN is a Digital Cordless Set. The MC32 package (350) is
restricted. Digital Cordless Sets require the MC32 package. The data block for
this set is not loaded.
Action: Reload with package enabled, or with a database that does not contain
DCSs.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2080 of 2360

SYS0111
Unable to allocate protected MSDL/MISP block for CLKC.

Action:
Severity: Info.
SYS0112
SNMP trap: Yes
CLKC index out-of-range (238-239).

Action:
Severity: Info.
SYS0113
SNMP trap: Yes
Unable to allocate protected space for CLKC P_MSDLMISP_PTR.

Action:
Severity: Info.
SYS0114
SNMP trap: Yes
Unable to allocate protected space for CLKC P_SID_BLK_PTR.

Action:
Severity: Info.
SYS0115
SNMP trap: Yes
Unable to allocate space for CLKC Physical IO Block.

Action:
Severity: Info.
SYS0116
SNMP trap: Yes
The Zone database is corrupt. One or more entries have not been loaded.
Action: Verify zones in Overlay 117. Zones that did not load could be out of
service. If the problem persists, re-enter the zone configuration or restore the
zone table from backups.
Severity: Info.
SYS0117
SNMP trap: Yes
User define feature kiey label data block tn=0.

Action:
Severity: Critical.
SYS0118
SNMP trap: Yes
User define feature key label data block pointer is nil.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2081 of 2360

SYS0119
Overlap Package (.OVLP_PACKAGE) is not equiped hence OVLS/OVLR is

set to .FALSE from .TRUE.
Action:
Severity: Info.
SYS0120
SNMP trap: Yes
There is a previous version of PDCA table15. No new table generated. This

table is reserved for IP gateways. If it does not contain correct values. IP call's
quality will be affected seriously. Action: If table 15 is used for other purposes
now, move it to another index and modify table 15 PAD values according to
NTPs for IP gateway PADs.
Action: If table 15 is used for other purposes now, move it to another index and
modify table 15 PAD values according to NTPs for IP gateway PADs.
Severity: Info.
SYS0121
SNMP trap: Yes
UUI RCAP removed and/or UUI prompt for CDN removed, since UUI package
is not equipped.
Action:
Severity: Minor.
SYS0122
SNMP trap: Yes
No CIS ANI reception table found in customer datablock. Default table is

created.
Action:
Severity: Info.
SYS0123
SNMP trap: No
No CIS/MFC CACC table found in customer datablock. Default table with one
entry is created.
Action:
Severity: Info.
SYS0124
SNMP trap: No
No protected data storage available for default CIS ANI reception table.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2082 of 2360

SYS0125
No protected data storage available for default CIS/MFC CACC table.

Severity: Critical.
SYS0126
SNMP trap: Yes
Warning. Illegal RGA program key found on M3903 - M3905 telephone.

May cause undesirable set display/soft key updates if key is used. Prompted
if ARDL (304) or M3900_RGA_PROG (396) packages are not equipped.
Action: Add missing packages or manually remove Programmable RGA keys
from M3903-M3905 sets.
Severity: Info.
SYS0127
SNMP trap: Yes
ICON PACKAGE NOT ENABLED

Action:
Severity: Minor.
SYS0128
SNMP trap: Yes
The number of PCAs configured exceeds the PCA ISM Limit and no further
PCAs can be sysloaded.
Action:
Severity: Critical.
SYS0129
SNMP trap: Yes
Existing M3900 language is changed from Hebrew to English since the

HEBREW package is restricted.
Action:
Severity: Info.
SYS0130
SNMP trap: Yes
The number of IP Peer H.323 Trunks exceeds the Limit or H323_VTRK

package is restricted. No further H.323 Trunks can be sysloaded.
Severity: Info.
SYS0131
SNMP trap: Yes
The number of IP Peer SIP Trunks exceeds the IP Peer SIP Trunk ISM limit
and no additional IP Peer SIP Trunks can be sysloaded.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2083 of 2360

SYS0132
An IPMG superloop is found, but the IPMG package is not equipped. IPMG
related data are not loaded.
Action: Verify if correct database has been loaded. Reload the system with the
correct database or contact your Nortel representative.
Severity: Info.
SYS0133
SNMP trap: Yes
Template offset change result. Telephone set template data does not begin at
the correct offset. Conversion for template data is not correct, or was not
correct in the past. The template data and corresponding set data are
corrected, as possible.
Parameters: template is the template number. See the BCS TEMPLATE or
PBX TEMPLATE printout preceding to determine the template type. Offset is
the starting data offset in this template prior to conversion. Change is the
amount that the starting template offset is calculated to need to change by
during the current conversion to match the "result". Result is the correct offset
at which the template data should begin for the current software.
Action: Report the problem to technical support.
Use overlay 20 to print the list of sets using the affected template and then print
those sets to insure that the data is correct. If it is then LD 43 and perform EDD
CLR to accept the changed data. If the data is not correct disable the sets. They
may need to be rebuilt.
Severity:
SYS0137
SNMP trap: No
The OVLP_PACKAGE or H323_VTRK_PKG is restricted, hence OVLR,

OVLS prompt for H.323 is set to False from True.
Action: Enable the required package.
Severity: Minor.
SYS0138
SNMP trap: No
Endorsing GR data just restored.

Action:
Severity: Info.
SYS0139
SNMP trap: No
Database Replication Endorsement failed.

The system will automatically be restarted for Data Stepback
Action: Call your system administrator for assistance
Severity: Major.
SNMP trap: No
System Messages
Page 2084 of 2360

SYS0140
SIP Package is restricted, therefore the SIP trunks cannot be sysloaded.

Action:
Severity: Critical.
SYS0141
SNMP trap: Yes
D-channel was provisioned with RCAP RLTI, even though the TAT RCAP is
not provisioned. Clearing the RLTI RCAP provisioning.
Action: Verify that this is the correct provisioning for this D channel. If RLTI is
required, enable TAT and RLTI RCAPs. This may require the TAT package to be
made available. If TAT is restricted and RLTI is required, have the package
enabled.
Severity: Minor.
SYS0142
SNMP trap: Yes
The D channel was provisioned with RCAP RLT, but is either not an SL1
interface, or is not card type DCIP. Since RLTI is only supported with CTYP
DCIP and IFC SL1, clearing the RLTI RCAP provisioning.
Action: Confirm that the D channel is of the correct type.
Severity: Minor.
SYS0191
SNMP trap: Yes
Invalid TN is in the DN block; TN is rejected from DN block.

Action:
Severity: Critical.
SYS0201
SNMP trap: No
Data block length error. Output data depends on software as follows: X11:
xxxx yyyy (data structure identifier & index number) X08: TN l s c u : terminal
number
Action:
Severity: Critical.
SNMP trap: Yes
SYS0202 TN l s c u Station type does not match card type.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2085 of 2360

SYS0203 TN l s c u Secondary attendant block forces out TN already loaded. See "Corrupted
data structures" in the SYS introduction.
Action:
Severity: Critical.
SNMP trap: Yes
SYS0204 TN l s c u Unit number of Digitone receiver not zero. See "Corrupted data structures" in
the SYS introduction.
Action:
Severity: Critical.
SNMP trap: Yes
SYS0205 TN l s c u Unit number of trunk not zero or one. See "Corrupted data structures" in the
SYS introduction.
Action:
Severity: Critical.
SYS0206
SNMP trap: Yes
Loop number out of range.

Action: See "Corrupted data structures" in the SYS introduction.
Severity: Critical.
SYS0207
SNMP trap: Yes
Shelf not in configuration record (local or remote). See "Corrupted data

structures" in the SYS introduction.
Action:
Severity: Critical.
SNMP trap: Yes
SYS0208 TN l s c u Invalid pointer to station data. Program error. See "Corrupted data structures"
in the SYS introduction.
Action:
Severity: Critical.
SYS0209
SNMP trap: Yes
Identical data block encountered twice.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 2086 of 2360

SYS0212
SCL DND template number exceeds length of list allocated. EDD error.
Severity: Critical.
SYS0214
SNMP trap: Yes
SNMP trap: No
SNMP trap: No
Conversion error.
Action:
Severity: Critical.
SYS0216
Patch block error.

Action:
Severity: Critical.
SYS0227
Unable to allocate enough PDS for converted SL-1 station.

Action:
Severity: Critical.
SYS0229
SNMP trap: No
SNMP trap: No
Same as SYS0227.
Action:
Severity: Critical.
SYS0230
Customer Data Block (CDB) does not exist when loading Automatic Call
Distribution (ACD) blocks.
Severity: Critical.
SYS0231
SNMP trap: Yes
Number of ACD blocks exceeds list size.

Severity: Critical.
SNMP trap: Yes
SYS0232 key cust dn ACD-DN does not exist in DN tree.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2087 of 2360

SYS0233
Data assigned to SL-1 ACD key is invalid, or the data assigned can not be
used with 500/2500 sets as ACD stations.
Severity: Critical.
SYS0234
SNMP trap: Yes
Number of stations assigned to ACD group exceeds maximum.

Severity: Critical.
SYS0236
SNMP trap: Yes
Authorization code data block does not exist.

Severity: Critical.
SYS0240
SNMP trap: No
CDB does not exist for Direct Inward System Access (DISA) data block.
Severity: Critical.
SYS0241
SNMP trap: Yes
Too many DISA data blocks in DISA list.

Severity: Critical.
SYS0242
SNMP trap: Yes
Number of dial intercom groups exceeds maximum allowed in customer data

block.
Severity: Critical.
SYS0246
SNMP trap: Yes
LOC entry has been discarded due to missing LOCX package. Value of
MAX_LOC_CODES truncated to 999.
Action: Enable LOCX package and FNP package.
Severity: Info.
SYS0250
SNMP trap: No
Tree data blocks corrupted. Tree will be released.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2088 of 2360

SYS0251
Unable to locate New Flexible Code Restriction (NFCR) pointers table.

Action:
Severity: Critical.
SYS0252
SNMP trap: Yes
Unable to locate tree block pointers table.

Action:
Severity: Critical.
SYS0253 <tn>
SNMP trap: Yes
SPCA Class of Service only allowed for IPE, TIE, E&M, trunks with MIA class
of service. Class of service changed to SPCD.
Action: DO NOT DATADUMP.
Severity: Critical.
SYS0254
SNMP trap: Yes
The number of digital telephones exceeds the Digital Telephones limit and no
further digital telephones can be sysloaded.
Action:
Severity: Critical.
SYS0255
SNMP trap: Yes
The number of analog TNs exceeds the Analog TN limit and no further analog
TNs can be sysloaded.
Action:
Severity: Info.
SYS0256
SNMP trap: Yes
Unable to allocate memory for PLUGIN data block

Action:
Severity: Info.
SYS0257
SNMP trap: Yes
PLUGIN pkg not equipped, PLUGIN data cleared.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2089 of 2360

SYS0258 x
Plugin x is disabled. PLUGIN x performs a different function in the current

release with respect to the previous release.
Action:
Severity: Info.
SYS0260
SNMP trap: No
RCAP UUS1 is removed during sysload because BNE package is not

equipped.
Action:
Severity: Minor.
SYS0262
SNMP trap: Yes
Existing EuroISDN diversion remote capability is removed since the BNE

Action: Enable the BNE package and sysload the machine again.
Severity: Critical.
SYS0263
SNMP trap: No
Existing EuroISDN diversion remote capability is removed since the BNE

Action: Enable the BNE package and sysload the machine again.
Severity: Critical.
SYS0264
SNMP trap: Yes
The number of ISDN B Channels exceeds the ISDN Channel limit and no
further TNs can be sysloaded.
Action:
Severity: Critical.
SYS0265
SNMP trap: No
The number of DTI Channel TNs exceeds the DTI Channel limit and no further
TNs can be sysloaded.
Action:
Severity: Critical.
SYS0266
SNMP trap: No
The number of Analog Trunk TNs exceeds the Analog Trunk TN limit and no
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2090 of 2360

SYS0267
The number of Data Port TNs exceeds the Data Ports limit and no further TNs
can be sysloadec.
Action:
Severity: Critical.
SYS0268
SNMP trap: Yes
The number of Phantom Port TNs exceeds the Phantom Ports limit and no
Action:
Severity: Critical.
SYS0269
SNMP trap: Yes
The number of CLASS Telephine TNs exceeds the CLASS Telephines limit
and no further TNs can be sysloaded.
Action:
Severity: Info.
SYS0270
SNMP trap: Yes
The number of Attendant Console TNs exceeds the Attendant Consoles limit
and no further TNs can be sysloaded.
Action:
Severity: Critical.
SYS0271
SNMP trap: Yes
The OAS package is disabled.

Action:
Severity: Major.
SYS0273
SNMP trap: Yes
Observe Password Table is not loaded.

Action:
Severity: Major.
SYS0277
SNMP trap: Yes
The number of ITG ISDN Trunks exceeds the ITG ISDN Trunks limit and no
further trunks can be sysloaded.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2091 of 2360

SYS0278
FFC package restricted. Changing CLS from ERCA to ERCD.

Action:
Severity: Info.
SYS0279
SNMP trap: No
Virtual and Host Terminal data block cannot be loaded when the
VIRT_OFFICE_PKG is not equipped.
Action:
Severity: Info.
SYS0285
SNMP trap: Yes
TN is removed because no more ITG cards can be added to the list.

Action:
Severity: Critical.
SYS0286
SNMP trap: Yes
The number of IP Phones type 2002 and 2004 and IP Softphones type 2050
exceeds the IP User License limit. No further IP User TNs can be loaded from
the database.
Action: (Recommended) Purchase additional IP User Licenses.
Severity: Critical.
SYS0287
SNMP trap: Yes
The number of IP Phones type 2001 exceeds the Basic IP User License limit.
No further Basic IP User TNs can be loaded from the database.
Action: (Recommended) Purchase additional Basic IP User Licenses.
Severity: Critical.
SYS0300 tn
SNMP trap: Yes

Severity: Critical.
SYS0301
SNMP trap: No
ACD supervisor key assigned to an agent station.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 2092 of 2360

SYS0302
ACD display queue key has invalid ACD DN.

Severity: Critical.
SYS0303
SNMP trap: Yes
More than 8 supervisors are assigned to a simple ACD DN.

Severity: Critical.
SYS0304
SNMP trap: Yes
Agent key assigned but agent does not exist.

Severity: Critical.
SYS0305
SNMP trap: Yes
Agent key identifies agent who already has another supervisor.

Severity: Critical.
SYS0306
SNMP trap: Yes
Agent key assigned identifies a supervisor station.

Severity: Critical.
SYS0307
SNMP trap: Yes
Attempt to assign an ACD agent function to a non-ACD set.

Severity: Critical.
SYS0308
SNMP trap: Yes
Attempt to assign a 'call supervisor' key to the supervisor.

Severity: Critical.
SNMP trap: Yes
SYS0310 key cust dn Illegal digits in DN.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2093 of 2360

SYS0311
Not-ready-key is assigned to a non-ACD station.

Severity: Critical.
SYS0312
SNMP trap: Yes
CAS key assigned to SL-1 telephone but CAS data blocks do not exist.
Severity: Critical.
SYS0315
SNMP trap: Yes
A function requiring an LED is assigned to a non-LED key.

Severity: Critical.
SYS0316
SNMP trap: Yes
CAS key assigned to SL-1 telephone but CAS data blocks do not exist.
Severity: Critical.
SYS0317
SNMP trap: No
More than 10 CAS keys have been assigned to SL-1 telephones.

Severity: Critical.
SNMP trap: Yes
SYS0330TN l s c u Shorter DN already exists. For SYS033XXXX, XXXX is the DN concerned.

Severity: Critical.
SNMP trap: Yes
SYS0340 TN l s c u Longer or equal length DN already exists.

Severity: Critical.
SYS0350 N l s c u
SNMP trap: Yes
Mixed Appearance DN block is corrupted.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 2094 of 2360

SYS0360 TN l s c u Trunk member number out-of-range.
Severity: Critical.
SNMP trap: Yes
SYS0370 TN l s c u Route data block does not exist.

Severity: Critical.
SNMP trap: Yes
SYS0380 TN l s c u Attendant member number out of range or in use.

Severity: Critical.
SYS0385
SNMP trap: Yes
TN of the terminal is not the prime DN of attendant.

Severity: Critical.
SNMP trap: Yes
SYS0390 TN l s c u Attendant Directory Number block of wrong type.

Severity: Critical.
SYS0391
SNMP trap: Yes
Invalid TN for attendant.

Severity: Critical.
SNMP trap: Yes
SYS0400 TN l s c u Assigned DN has more than 30 stations.

Action:
Severity: Critical.
SNMP trap: Yes
SYS0410 TN l s c u DN call type in conflict, i.e., single vs multiple.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2095 of 2360

SYS0420
Network loop in configuration record conflicts with existing loop.

Action:
Severity: Critical.
SYS0421
SNMP trap: No
Tone loop in configuration record conflicts with existing loop.

Action:
Severity: Critical.
SYS0422
SNMP trap: Yes
Conference loop in configuration record conflicts with existing loop.

Action:
Severity: Critical.
SYS0423
SNMP trap: No
MF Sender in configuration record conflicts with existing loop.

Action:
Severity: Critical.
SYS0430
SNMP trap: No
Private DN in trunk data block conflicts with existing DN.

Action:
Severity: Critical.
SYS0500
SNMP trap: No
CPU test failed on nonactive CPU.

Action:
Severity: Critical.
SYS0510
SNMP trap: No
Changeover and Memory Arbitrator (CMA) pack failed to respond. Faulty CMA
pack.
Action:
Severity: Critical.
SYS0514
SNMP trap: No
The loop does not exist in LD 73.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2096 of 2360

SYS0520
Unable to find data for other CPU after switchover.

Action:
Severity: Critical.
SYS0600
SNMP trap: No
Emergency conference group out-of-range (0 to 9).

Action: Check data.
Severity: Critical.
SYS0601
SNMP trap: No
Emergency conference member out-of-range (1 to 10).

Action: Check data.
Severity: Critical.
SYS0602
SNMP trap: No
Software problem.
Action: If message persists, call manufacturer.
Severity: Critical.
SYS0603
SNMP trap: No
Two TNs assigned as the same member of the same group.

Action: Check data.
Severity: Critical.
SYS0606 id index
SNMP trap: No
Customer data block number read from the storage medium record header
greater than the size of the customer data block pointer array. The output data
is defined as follows: Where: ID = Structure Identifier INDEX = Index number
definition 1. ESN-Customer number = error occurred while loading ESN data
block (ESN_DATA_BLK). 2. ESNS-Data block index = error occurred while
loading supplementary digit block (ESN_SDR_BLK). 3. ESNL-Customer
number = error occurred while loading location route block
(ESN_LOC_RTE_BLK). 4. ESNR-Data block index = error occurred while
loading route list (ESN_RTE_LIST_BLK). 5. ESND-Data block index = error
occurred while loading digit manipulation block (ESN_DM_BLK).
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2097 of 2360

SYS0607 id index
Electronic Switched Network (ESN) data structure was loaded from storage
medium but a corresponding customer data block to reference this structure
does not exist.
Action: See SYS606 for output data.

Severity: Critical.
SYS0608 id index
SNMP trap: Yes
More than one ESN data block was loaded from storage medium for the same
customer.

Severity: Critical.
SYS0609 id index
SNMP trap: Yes
One of the ESN data structures which are referenced from the ESN data block
was loaded but the ESN data block does not currently exist for the
corresponding customer.

Severity: Critical.
SYS0610 id index
SNMP trap: Yes
Insufficient protected data store for supplementary digit pointer block.

Severity: Critical.
SYS0611 id index
SNMP trap: Yes
The supplementary digit restriction index read from the storage medium record
header is greater than the maximum value, which is stored in the ESN data
block.

Severity: Critical.
SYS0612 id index
SNMP trap: Yes
More than one supplementary digit restriction block was found on storage
medium for the same customer and index.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 2098 of 2360

SYS0613 id index
Insufficient protected data store memory space to set up the route list pointer
block.

Severity: Critical.
SYS0614 id index
SNMP trap: Yes
Route list index read from the storage medium record header greater than the
maximum value, which is stored in the ESN data block.

Severity: Critical.
SYS0615 id index
SNMP trap: Yes
More than one route list block was found on storage medium for the same
customer and index.

Severity: Critical.
SYS0616 id index
SNMP trap: Yes
Insufficient protected data store memory space to set up the digit manipulation
pointer block.

Severity: Critical.
SYS0617 id index
SNMP trap: Yes
Digit manipulation index read from the storage medium record header is
greater than the maximum value, which is stored in the ESN data block.

Severity: Critical.
SYS0618 id index
SNMP trap: Yes
More than one digit manipulation block was found on storage medium for the
same customer and index.

Severity: Critical.
SYS0619 id index
SNMP trap: Yes
More than one location route block was found on storage medium for the same
customer and index.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2099 of 2360

SYS0620 id index
Insufficient protected data store memory space to set up a block in the network
translation tree.

Severity: Critical.
SYS0621 id index
SNMP trap: Yes
One of the translation table digits read from the storage medium is
out-of-range.

Severity: Critical.
SYS0622 id index
SNMP trap: Yes
The same sequence of digits has been read from storage medium for the
specified network translation table.

Severity: Critical.
SYS0626
SNMP trap: Yes
SNMP trap: No
NARS is not available.

Action:
Severity: Critical.
SYS0627
Translation data is corrupted.

Action:
Severity: Critical.
SYS0628
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Route list pointer.

Action:
Severity: Critical.
SYS0629
Trunk route data.

Action:
Severity: Critical.
SYS0630
Location route data.

Action:
Severity: Critical.
System Messages
Page 2100 of 2360

SYS0631
Route list entry data.

Action:
Severity: Critical.
SYS0632
SNMP trap: No
Insufficient protected data store memory space to set up the Free Calling Area
Screening (FCAS) pointer block.
Action:
Severity: Critical.
SYS0633
SNMP trap: Yes
More than one FCAS NXX block was found on storage medium for the same
customer, index and NPA.
Action:
Severity: Critical.
SYS0634
SNMP trap: Yes
The FCAS index read from the storage medium record header is greater than
the maximum value, which is stored in the ESN data block.
Action:
Severity: Critical.
SYS0638
SNMP trap: Yes
SNMP trap: No
NARS-Invalid NXX.
Action:
Severity: Critical.
SYS0639
NARS-FCAS data cannot be accessed.

Action:
Severity: Critical.
SYS0640
SNMP trap: No
Cannot perform data conversion for this generic/release/version of storage

medium.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2101 of 2360

SYS0641
The value of the variable 'BLOCKTYPE' was out-of-range. This variable is set
to the storage medium header word 'TAPEBLOCKTYPE'.
Action:
Severity: Critical.
SYS0642
SNMP trap: Yes
The customer data block number read from the storage medium record header
is greater than the customer data block pointer size.
Action:
Severity: Critical.
SYS0643
SNMP trap: Yes
No customer data block exists to which authcode can be attached.

Action:
Severity: Critical.
SYS0644
SNMP trap: Yes
The block number read from the storage medium record header does not
match the expected block number.
Action:
Severity: Critical.
SYS0645
SNMP trap: Yes
More than one block was read from storage medium with the same block
identification.
Action:
Severity: Critical.
SYS0646
SNMP trap: Yes
The authcode header table (AUTH_TABLE_BLK) does not exist to which the
remaining authcode data blocks may be attached.
Action:
Severity: Critical.
SYS0647
SNMP trap: Yes
Authcode conversion can occur only in conjunction with the BAUT package
and not the NAUT package.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2102 of 2360

SYS0648
During conversion, more different class codes were read from storage medium
than there is room in the new class code table.
Action:
Severity: Critical.
SYS0649
SNMP trap: No
Attempt to allocate protected data store memory space failed.

Action:
Severity: Critical.
SYS0650
SNMP trap: Yes
During conversion, two authcodes which contained identical digits were

loaded.
Action:
Severity: Critical.
SYS0653
SNMP trap: No
Cannot allocate space for NCTL block which should be split from the ESN data
block.
Action:
Severity: Critical.
SYS0654
SNMP trap: No
More than one Coordinated Dialing Plan (CDP) list was found on storage
medium for the same customer.
Action:
Severity: Critical.
SYS0655
SNMP trap: Yes
The index for the TDET block was 0 or greater than the maximum size.
Action:
Severity: Critical.
SYS0667 c
SNMP trap: Yes
PRA option for customer c was turned off because ISA is restricted.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2103 of 2360

SYS0668 x
Cannot load data block for DCH x when the ISA and/or DTI packages are
restricted.
Action:
Severity: Critical.
SYS0669 loop
SNMP trap: No
Cannot load data block for PRI loop when the ISA and/or DTI packages are
restricted.
Action:
Severity: Critical.
SYS0670 r c
SNMP trap: Yes
Cannot load route r for customer c when the ISA package is restricted and the
route is configured to have B- channels.
Action:
Severity: Critical.
SYS0671 r c
SNMP trap: Yes
SDN option for route r in customer c is turned off because ISA is restricted.
Action:
Severity: Critical.
SYS0700 xx
SNMP trap: Yes
This message indicates self-test results, and call processing status. xx refers
to appended numbers that follow the SYS700 message itself. Each set of
numbers is associated with a specific call processing or self-test activity. They
appear as the activity takes place. 00 = Begin CP board reset 01 = Begin
SRAM self- test 02 = ROM created on {date} 03 = Beginning DRAM self-test;
DRAM being configured 04 = Booting ROM Operating System
Action:
Severity: Critical.
SYS0701 xx
SNMP trap: No
appear as the activity takes place. 01 = ASIC ICC failure 02 = SRAM test
failure 03 = CP test failure 04 = HPM test failure 05 = PEROM checksum
System Messages
Page 2104 of 2360

failure 06 = SRA ASIC failure 07 = CMB ASIC failure 08 = BIC ASIC failure 09
= Duarte test failure 10 = Time of day clock failure 11 = No DRAM available 12
= LCD display test failure
Action:
Severity: Critical.
SNMP trap: No
SYS0702 x x x x x x DRAM size (in megabytes). Each x indicates a bank populated, with a
maximum of 6 banks available.
Action:
Severity: Critical.
SYS0703 xxxx
SNMP trap: No
Self-tests completed. xxxx refers to the test flags. 0FFF indicates that all the
tests passed.
Action:
Severity: Critical.
SYS0704
SNMP trap: No
SNMP trap: No
Soft reset completed.

Action:
Severity: Critical.
SYS0705 xx
appear as the activity takes place. 00 = CPU speed unknown 01 = CPU speed
less than 25 Mhz 02 = CPU speed at 25 Mhz 03 = CPU speed between 25 Mhz
and 33 Mhz 04 = CPU speed at 33 Mhz 05 = CPU speed between 33 Mhz and
40 Mhz 06 = CPU speed at 40 Mhz 07 = CPU speed greater than 40 Mhz
Action:
Severity: Info.
SYS0720 x
SNMP trap: No
Running VxWorks Boot OS. X11 Release x.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2105 of 2360

SYS0722 x
Cannot load {filename} to x.

Action:
Severity: Critical.
SYS0723 x
SNMP trap: No
Boot OS restart reason x.

Action:
Severity: Critical.
SYS0724
SNMP trap: No
SNMP trap: No
Boot OS exception.
Action:
Severity: Critical.
SYS0800
Unable to allocate Peripheral Signaling (PS) polling table.

Action: Clear memory fault or add memory.
Severity: Critical.
SYS0802 i t n
SNMP trap: Yes
Unable to allocate protected memory for data block.

Parameters: blocktype and identifying data.
Action: Clear memory fault or add memory
Severity: Critical.
SYS0803
SNMP trap: Yes
Unable to allocate protected directory block.

Severity: Critical.
SYS0804
SNMP trap: Yes
Unable to allocate protected loop block.

Severity: Critical.
SYS0805
SNMP trap: Yes
Unable to allocate dial intercom group block.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 2106 of 2360

SYS0808
Unable to allocate memory for Group data link.

Action:
Severity: Critical.
SYS0810
SNMP trap: Yes
Unable to allocate 'do not disturb' block.

Severity: Critical.
SYS0811
SNMP trap: Yes
Ext DIG5 block without Basic block.

Action:
Severity: Critical.
SYS0812
SNMP trap: No
Ext MR block without Basic block.

Action:
Severity: Critical.
SYS0813
SNMP trap: Yes
Aux Customer block without Basic block.

Action:
Severity: Critical.
SYS0826
SNMP trap: Yes
Unable to allocate protected DTI block.

Action:
Severity: Critical.
SYS0900
SNMP trap: Yes
Unable to allocate memory for the overlay area.

Action: Clear memory faults or add memory.
Severity: Critical.
SYS0905
SNMP trap: No
Unable to transfer program to memory other than page 2.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2107 of 2360

SYS0910
Memory map for active memories invalid. Program error.

Action:
Severity: Critical.
SYS0999 FATAL
SNMP trap: No
Major alarm (power fail transfer) tripped by software because of insufficient

protected memory.
Severity: Critical.
SYS1000
SNMP trap: Yes
Card density greater than loop density.

Action:
Severity: Critical.
SYS1026
SNMP trap: No
CMF_TIE_PACKAGE not equipped.

Action:
Severity: Critical.
SYS1057
SNMP trap: Yes
MFE package not equipped.

Action:
Severity: Critical.
SYS1058
SNMP trap: Yes
SNMP trap: Yes
MFE data corruption.

Action:
Severity: Critical.
SYS1588
Automatic BKPS %d already exists. Attempt to define more than one auto
backup schedule.
Action:
Severity: Info.
SYS1589
SNMP trap: No
Bkpr %d is used by bkps %d.

Attempt to remove backup rule used by backup schedule.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2108 of 2360

SYS1590
Bkps refers to an unexisting bkpr %d.

Attempt to add/change bkps referring to unexisting bkpr.
Action: Verify Removable Media Device accessibility.
Severity: Info.
SYS1591
SNMP trap: No
Auto bkps and auto GRDRC are mutually exclusive.

Attempt to attempt to define auto bkps and auto grdrc at the same time.
Action:
Severity: Info.
SYS1592
SNMP trap: No
Bkps %d already exists

Attempt to add an already existing bkps.
Action:
Severity: Info.
SYS1593
SNMP trap: No
Bkps %d does not exist

Attempt to remove/change bkps which does not exist.
Action:
Severity: Info.
SYS1594
SNMP trap: No
The type of rule %d is %4s instead of SCS

Attempt to define GRDRC with rule which type is not SCS.
Action:
Severity: Info.
SYS3000 c
SNMP trap: No
Customer c missing from Call Park block. Cannot load block.

Action:
Severity: Critical.
SYS3001 c
SNMP trap: Yes
Cannot build DN because DN information is missing from Call Park block for
customer c.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2109 of 2360

SYS3002 c dn
Cannot build the remainder of the Call Park DNs for Customer c. dn is failed
DN.
Action:
Severity: Critical.
SYS3003
SNMP trap: Yes
Speed call list is partially missing.

Action:
Severity: Critical.
SYS3004
SNMP trap: Yes
Cannot build DN for ESN test maintenance lines.

Action:
Severity: Critical.
SYS3005
SNMP trap: Yes
Fatal. Conversion was not done properly. Wrong generic/release.

Action:
Severity: Critical.
SYS3006
SNMP trap: No
SNMP trap: No
Conversion flag not set.

Action:
Severity: Critical.
SYS3007
SCC data table is required.

Action:
Severity: Critical.
SYS3008
SNMP trap: No
Card density on storage medium is greater than configured loop density.

Action:
Severity: Critical.
SYS3009
SNMP trap: Yes
Card density in protected card block does not equal the card density on
storage
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2110 of 2360

SYS3010
Encountered card block with wrong card type.

Action:
Severity: Critical.
SYS3011
SNMP trap: Yes
The expected number of card records not received from storage medium.
Action:
Severity: Critical.
SYS3012
SNMP trap: Yes
A higher density loop has a lower density card record for upper units.
Action:
Severity: Critical.
SYS3013
SNMP trap: Yes
ADM trunk type not supported. Route or trunk data block discarded.
Action:
Severity: Critical.
SYS3015
SNMP trap: No
Unable to allocate Protected Data Store (PDS) for set relocation.

Action:
Severity: Critical.
SYS3016
SNMP trap: Yes
Unable to allocate PDS for History File.

Action:
Severity: Critical.
SYS3017
SNMP trap: Yes
Unable to allocate PDS for tone detector block.

Action:
Severity: Critical.
SYS3019
SNMP trap: Yes
Multiple Office Code/DID ranges block found with no location code.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2111 of 2360

SYS3020
There is a Multiple Office Code and DID ranges block for a location code that
does not have a MNXX block defined. MNXXX was allocated anyway.
Action:
Severity: Critical.
SYS3021
SNMP trap: Yes
The pointer to MNXXX block was not nil (possibly two MNXXX blocks for this
location code).
Action:
Severity: Critical.
SYS3022
SNMP trap: No
There is a Multiple Office Code and DID ranges block for a location code but
the length is zero.
Action:
Severity: Critical.
SYS3024
SNMP trap: Yes
Data block can only be loaded when DTI package is selected. On code but the
length is zero.
Action:
Severity: Critical.
SYS3025
SNMP trap: Yes
Data block can only be loaded when AMP package is selected.

Action:
Severity: Critical.
SYS3026
SNMP trap: Yes
Attempt to allocate pds for Tenant Data Block failed.

Action:
Severity: Critical.
SYS3027
SNMP trap: Yes
Block header customer number too large.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2112 of 2360

SYS3028
Block header route number too large.

Action:
Severity: Critical.
SYS3029
SNMP trap: Yes
Block header tenant number too large.

Action:
Severity: Critical.
SYS3030
SNMP trap: Yes
Tenant data blocks out of order, presumed missing.

Action:
Severity: Critical.
SYS3031
SNMP trap: Yes
Essential tenant data blocks are missing, Sysload disabled tenant service.
Action:
Severity: Critical.
SYS3032
SNMP trap: Yes
Tenant service package restricted but tenant data block detected.

Action:
Severity: Critical.
SYS3033
SNMP trap: Yes
Tenant service should not be packaged with AUTOVON.

Action:
Severity: Critical.
SYS3034
SNMP trap: No
Tenant service should not be packaged with mini-CDR.

Action:
Severity: Critical.
SYS3035
SNMP trap: Yes
Digital set data block cannot be loaded when digital set package is not
equipped.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2113 of 2360

SYS3036
M3000 data block cannot be loaded when M3000 package is not equipped.
Action:
Severity: Critical.
SYS3038
SNMP trap: Yes
MSI Hardware register fault.

Action:
Severity: Critical.
SYS3039
SNMP trap: Yes
BG TIME/CATEGORY block without AUX CUST BLK.

Action:
Severity: Critical.
SYS3040
SNMP trap: Yes
AWU time on the TN has been erased.

Action:
Severity: Critical.
SYS3042
SNMP trap: Yes
Two supervisors have a NSVC key assigned for this ACD-DN.

Action:
Severity: Critical.
SYS3043
SNMP trap: Yes
The ACD NSVC key is assigned to an invalid ACD-DN.

Action:
Severity: Critical.
SYS3044
SNMP trap: Yes
The ACD NSVC key is assigned to an agent's station.

Action:
Severity: Critical.
SYS3045
SNMP trap: Yes
The NSVC key is assigned to an illegal DN lamp key.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2114 of 2360

SYS3046
Cannot allocate memory space for Speed Call List header table.
Action:
Severity: Critical.
SYS3047
SNMP trap: Yes
Automatic conversion is not available for a given data base. Data base on tape
is not updated to minimum release.
Action:
Severity: Critical.
SYS3048
SNMP trap: Yes
Expecting an extension block on tape which is not there.

Action:
Severity: Critical.
SYS3049
SNMP trap: Yes
An illegal extension block is read by the tape. Block that has been read is not
an extension of the previous block.
Action:
Severity: Critical.
SYS3050
SNMP trap: Yes
The primary block is missing from the tape. The extension block read from the
tape needs a primary block.
Action:
Severity: Critical.
SYS3051
SNMP trap: Yes
Cannot load FTC data block if FTC is not packaged.

Action:
Severity: Critical.
SYS3053
SNMP trap: No
Cannot get Protected Data Block for creating Table 0.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2115 of 2360

SYS3054
Mini CDR module is entered when either DNXP or CDRE is present. Mini CDR
is not supported when either DNXP or CDRE (or both) are present.
Action:
Severity: Critical.
SYS3056
SNMP trap: Yes
Customer ID for given Prexl_block is out-of-range.

Action:
Severity: Critical.
SYS3057
SNMP trap: Yes
Customer data block does not exist for given prexl_block.

Action:
Severity: Critical.
SYS3060 c zz ss
SNMP trap: Yes
DN's hundreds group conflict with a shorter hundreds group. Where: c =

customer number zz = conflicting hundreds group ss = is the shorter existing
group
Action:
Severity: Critical.
SNMP trap: Yes
SYS3061 c xx yyyy This DN's hundreds group conflicts with a different hundreds group within this
data base. Where: c = customer number xx = conflicting hundreds group yyyy
= is the longer existing group
Action:
Severity: Critical.
SYS3062
SNMP trap: Yes
Private DN has already been defined as non-private DN line set up fail.

Action:
Severity: Critical.
SYS3065
SNMP trap: Yes
Unit number of MFVE receiver not zero or one.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2116 of 2360

SYS3066
Unit number of MFR receiver is not zero.

Action:
Severity: Critical.
SYS3067
SNMP trap: Yes
Cannot allocate P_NKDM_TABLE for given customer.

Action: Remove unnecessary configuration, make sure customer really needs
IDC.
Severity: Critical.
SYS3068
SNMP trap: Yes
Fatal error: no space for the conversion program.

Action:
Severity: Critical.
SNMP trap: No
SYS3071 CPND NAME dn A CPND name associated with the given DN was not loaded into
memory because it was too long, invalid or there was not enough protected
data store available. Re-enter the name in LD 95.
Action: Re-enter the name in LD 95. If there are many of these messages then
evaluate the available protected data store.
Severity: Critical.
SYS3072
SNMP trap: Yes
Block index is out-of-range for given ovflw_index_block.

Action:
Severity: Critical.
SYS3073
SNMP trap: Yes
Block index does not correspond with given ovflw_index_block. Block index is
within range but it does not match with given ovflw_index_block.
Action:
Severity: Critical.
SYS3074
SNMP trap: Yes
Ran out of memory. Cannot allocate PDS for AUTH_TABLE_block.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2117 of 2360

SYS3076
No more PDS. Cannot allocate PDS for ATM_Sch_Blk.

Action:
Severity: Critical.
SYS3077
SNMP trap: Yes
No more PDS. Cannot allocate PDS for Cust_ATM_MHT block

Action:
Severity: Critical.
SYS3078
SNMP trap: Yes
Cust ID out-of-range. ATM_Sch_Blk customer ID is out-of-range of cDataPtr.

Action:
Severity: Critical.
SYS3079
SNMP trap: Yes
Customer Data is missing. No customer data exist for given cust ID for
ATM_Sch_Blk.
Action:
Severity: Critical.
SYS3080
SNMP trap: Yes
Hour given is out-of-range. ATM_Sch_Blk number of hours out-of-range of 24

hours.
Action:
Severity: Critical.
SYS3084
SNMP trap: Yes
Unable to allocate head/sub-head table block for FGD ANI data

Action:
Severity: Critical.
SYS3085
SNMP trap: Yes
No NPA block exists to which Nxx block can attached.

Action:
Severity: Critical.
SYS3086
SNMP trap: Yes
No NXX block exists to which SUB block can be attached.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2118 of 2360

SYS3087
The block number read is greater than expected.

Action:
Severity: Critical.
SYS4007
SNMP trap: Yes
LLC data block found but feature is not packaged. Data block not loaded into
the system.
Action:
Severity: Critical.
SYS4008
SNMP trap: Yes
AUTOVON feature not packages. LLC level set to "OFF".

Action:
Severity: Critical.
SYS4009
SNMP trap: Yes
Cannot allocate memory for PNI Table.

Action: Check the Memory card.
Severity: Critical.
SYS4010
SNMP trap: Yes
Cannot allocate memory for PNI customer table.

Action: Check the Memory card.
Severity: Critical.
SYS4013
SNMP trap: Yes
SNMP trap: Yes
Patch block error.

Action:
Severity: Critical.
SYS4014
Aries set data block cannot be loaded when Aries set package is not equipped.
Action:
Severity: Critical.
SYS4015
SNMP trap: Yes
SYS custno out-of-range. The cust ID of ICI Table Block is bigger than the size
of cDataPtr.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2119 of 2360

SYS4016
No customer data block exists for given cust ID, of ICI Table block.
Action:
Severity: Critical.
SYS4036
SNMP trap: Yes
Page 5 option set, bug logical Page 509 not on Page 5. No memory
enhancement performed (XN and L only).
Action:
Severity: Critical.
SYS4100
SNMP trap: No
The ICDR data exists on the system tape but the ICDR package is disabled
for the software active on the switch. All telephone sets and attendant
console's ICDR options are removed.
Action:
Severity: Critical.
SYS4101
SNMP trap: No
The MCT data exists on the system tape but the MCT packages is disabled for
the software active on the switch. MCT options have been reset.
Action:
Severity: Critical.
SYS4102
SNMP trap: No
Tape contains Enhanced Hot Line data but EHOT package is not equipped.
Action:
Severity: Critical.
SYS4103
SNMP trap: No
Hot Line Package must exist for EHOT package to be enabled.

Action:
Severity: Critical.
SYS4200
SNMP trap: No
Network Attendant Service (NAS) schedule block found on disk, but the NAS
package is restricted. NAS data was not loaded.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2120 of 2360

SYS4201
One of NARS, NCOS or BRTE package required by Network Attendant

Service (NAS) is restricted. NAS data was not loaded.
Action:
Severity: Critical.
SYS4203
SNMP trap: Yes
P_AUX_CDB is missing for the Network Attendant Service (NAS) schedule

block to be loaded. NAS data was not loaded.
Action:
Severity: Critical.
SYS4204
SNMP trap: Yes
The SDI_RECORD cannot be loaded or allocated during SYSLOAD.

Action:
Severity: Critical.
SYS4205
SNMP trap: No
Data can only be loaded when PRI2 package is selected.

Action:
Severity: Critical.
SYS4206
SNMP trap: Yes
Data can only be loaded when PRI2 or DTI2 package is selected.

Action:
Severity: Critical.
SYS4209
SNMP trap: Yes
BKGD Port ID of "IS" changed to its ASCII equivalent "01". This was done
because the previously defined BKGD port of "IS" conflicts with a new
message type in the Hospitality Voice Services (HVS) feature.
Action: Continue to use the new port ID or "01", or change it to another valid ID.
This error does not inhibit a subsequent data dump.
Severity: Critical.
SYS4210 xxx
SNMP trap: Yes
Where xxxx can be one of the following codes: 1. 216 DDSL number exceeds
length of list allocated 2. 563 Bad DPNSS channel block (data is lost) These
codes correspond to SYS216 and SYS563 on SLX systems.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2121 of 2360

SYS4211
CPG number is out-of-range (1-63).

Action:
Severity: Critical.
SYS4212
SNMP trap: Yes
Customer number for CPG data block is out-of-range (0-99).

Action:
Severity: Critical.
SYS4213
SNMP trap: Yes
CPG (1-63) data block found but the CPG basic package
(CPG_BAS_PACKAGE) is not equipped.
Action:
Severity: Critical.
SYS4214
SNMP trap: Yes
No Protected Data Store (PDS) to allocate the CPG data block.

Action:
Severity: Critical.
SYS4215
SNMP trap: Yes
No Protected Data Store (PDS) to for CPG0 data block at SYS2 wrap up time.
Action:
Severity: Critical.
SYS4216
SNMP trap: Yes
The protected CPG pointer block is nil (DNXL module) for a configured
customer.
Action:
Severity: Critical.
SYS4217
SNMP trap: Yes
Customer configured, no CPG0 data block SYS2 will recover with the default
values.
Action:
Severity: Critical.
SYS4218
SNMP trap: Yes
ATL package not equipped.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2122 of 2360

SYS4219
Cannot find the ACD Block for this Target Table.

Action:
Severity: Critical.
SYS4220
SNMP trap: Yes
Invalid DN for this NACD Target Table.

Action:
Severity: Critical.
SYS4221
SNMP trap: Yes
l s c u find the ACD Block for this Source Table.

Action:
Severity: Critical.
SYS4222
SNMP trap: Yes
Invalid DN for this NACD Source Table

Action:
Severity: Critical.
SYS4223
SNMP trap: Yes
Not enough Protected Data Store to set up FSNS pointer block.

Action:
Severity: Critical.
SYS4224
SNMP trap: Yes
More than one FSNS XXX block was found for the same customer, index and
NPA.
Action:
Severity: Critical.
SYS4225
SNMP trap: Yes
The FSNS index record header was found to greater than the maximum value
which is stored in the ESN data block.
Action:
Severity: Critical.
SYS4301
SNMP trap: Yes
Aries data block cannot be loaded unless the Aries Package is equipped.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2123 of 2360

SYS4304
The system has found some corrupted LAPW data.

Action:
Severity: Critical.
SYS4305
SNMP trap: Yes
The root pointer is not set. The LAPW data will not be loaded.
Action:
Severity: Critical.
SYS4306
SNMP trap: Yes
The LAPW package is not equipped. The LAPW data will not be loaded.
Action:
Severity: Critical.
SYS4307
SNMP trap: Yes
PLDN package is not equipped; data has been cleared.

Action:
Severity: Critical.
SYS4308
SNMP trap: Yes
Bad data encountered while loading DN_GHBLK.

Action:
Severity: Critical.
SYS4309
SNMP trap: Yes
Unable to allocate PDS GPHT data block.

Action:
Severity: Critical.
SYS4310
SNMP trap: Yes
Bad data encountered while loading SCL_P_GHBLK.

Action:
Severity: Critical.
SYS4311 l s c u
SNMP trap: Yes
The key template for the SL-1 set at this TN is missing. The data block cannot
be loaded.
Action: The set must be redefined.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2124 of 2360

SYS4313
When a disk with IMS data and packages has been dumped to disk, and an
IMS package is missing, then two SYS4313 messages are output on
SYSLOAD instead of SYS0802.
Action:
Severity: Critical.
SYS4315
SNMP trap: Yes
The Automatic Number Identification package (ANI) package 12 is not

equipped. The data has been lost.
Action:
Severity: Critical.
SYS4316
SNMP trap: Yes
The AUTOVON package (Defense Switched Network -- DSN, pkg. 68) is not
equipped. That data has been lost.
Action:
Severity: Critical.
SYS4317
SNMP trap: Yes
Use another data base. The data base on tape is developmental, before the
final issue.
Action:
Severity: Critical.
SYS4318
SNMP trap: No
1.5 and 2.0 REP cannot co-exist, 2.0 is removed.

Action:
Severity: Critical.
SYS4319
SNMP trap: Yes
No RPE2 package. RPE2 not loaded.

Action:
Severity: Critical.
SYS4322
SNMP trap: Yes
Dedicated trunks can not be assigned to an ISA service route.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2125 of 2360

SYS4323
The step flag is turned off. Stepping to an ISA route is not allowed.
Action:
Severity: Critical.
SYS4324
SNMP trap: Yes
The step flag is turned off. Stepping to an ISA service route is not allowed.
Action:
Severity: Critical.
SYS4325
SNMP trap: Yes
The step flag is turned off. Stepping to a non-existing route is not allowed.
Action:
Severity: Critical.
SYS4326 l s c
SNMP trap: Yes
A card number has been found during SYSLOAD which is out-of-range. Valid
card numbers are listed here: ENET: 1 - 10 Network/DTR card (NT8D18): 0-9
and 15 Network (NT8D04) card: 0-15
Action:
Severity: Critical.
SNMP trap: Yes
SYS4327 DO NOT DATADUMP This TN is greater than the limit and cannot SYSLOAD. SYSTEM
INFORMATION WILL BE LOST.
Action: Order new disks with expanded limits.
Severity: Critical.
SNMP trap: Yes
SYS4328 DO NOT DATADUMP This ACD Agent/Supervisor is greater than the limit and cannot
SYSLOAD. DO NOT DATADUMP. SYSTEM INFORMATION WILL BE LOST.
Severity: Critical.
SNMP trap: Yes
SYS4329 DO NOT DATADUMP This ACD DN is greater than the limit and cannot SYSLOAD. DO
NOT DATADUMP. SYSTEM INFORMATION WILL BE LOST.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2126 of 2360

SYS4330 DO NOT DATADUMP This AST set is greater than the limit and cannot sysload. If you
datadump, system information will be lost.
Severity: Critical.
SYS4332
SNMP trap: Yes
The IFC type of the ISA service route and the ISA route do not match.
Action:
Severity: Critical.
SYS4333
SNMP trap: Yes
The ISDN package is restricted in this event. You cannot load the DCH
number.
Action:
Severity: Critical.
SYS4334
SNMP trap: Yes
The PRA package is restricted. You cannot load the DCH number.
Action:
Severity: Critical.
SYS4335
SNMP trap: Yes
The DCH mode is dedicated in the ESL mode, and the ESL package is
restricted. You cannot load the DCH number.
Action:
Severity: Critical.
SYS4336
SNMP trap: Yes
This telephone set is declared incorrectly as an ACD Agent station.

Action:
Severity: Critical.
SYS4337
SNMP trap: Yes
The ACD_POS_LST_PTR for the ACD-DN is not set correctly.

Action:
Severity: Critical.
SYS4339
SNMP trap: Yes
The Virtual Network Service (VNS) data block cannot be loaded.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2127 of 2360

SYS4340
The DNs cannot be built because the DN information is missing from the
Virtual Network Services (VNS) data block.
Action:
Severity: Critical.
SYS4341
SNMP trap: Yes
The rest of those DNs cannot be built because there is no valid Customer
Block existing.
Action:
Severity: Critical.
SYS4342
SNMP trap: Yes
RPA data lost; RPA package is not equipped.

Action:
Severity: Critical.
SYS4343
SNMP trap: Yes
RPA data lost; nil cust_no/ffc/rpa_dn pointer.

Action:
Severity: Critical.
SYS4345
SNMP trap: Yes
This customer lost the SDAC data because neither the SUPP nor PRTRANS
packages are equipped.
Action:
Severity: Critical.
SYS4346
SNMP trap: Yes
The ISDN International package is restricted from that operation. The TSYNC
data is not loaded.
Action:
Severity: Critical.
SYS4347 c
SNMP trap: Yes
The DN information for this customer is missing. The system cannot build a
DN in the data base. Where: c = Customer number
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2128 of 2360

SYS4348
The Time Synchronization (TSYNCH) package has been found, but the
International ISDN supplemental features are restricted from its use. The
TSYNCH data is not loaded.
Action:
Severity: Critical.
SYS4349 c
SNMP trap: No
You cannot build a TSYNCH DN, because the DN information for that
customer (c) is missing.
Action:
Severity: Critical.
SYS4350
SNMP trap: No
Hospitality IDC tree block not loaded since Hospitality package is unequipped
Action:
Severity: Critical.
SYS4351
SNMP trap: Yes
Hospitality IDC tree block is not loaded.

Action:
Severity: Critical.
SYS4352
SNMP trap: Yes
Hospitality package is removed since some of the packages it requires are

missing.
Action:
Severity: Critical.
SYS4353
SNMP trap: Yes
Hospitality Authcode block is not allowed.

Action:
Severity: Critical.
SYS4356
SNMP trap: Yes
Mini-CDR is not allowed on Option 11 machines. The package has been

disabled.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2129 of 2360

SYS4357
The Remote Peripheral Equipment (RPE) package is not allowed on Option

11 machines. The package has been disabled.
Action:
Severity: Critical.
SYS4358
SNMP trap: Yes
The RPE2 package is not allowed on Option 11 machines. The package has
been disabled.
Action:
Severity: Critical.
SYS4365
SNMP trap: Yes
Fatal error: DNXL program not found on the storage medium.

Action:
Severity: Critical.
SYS4366
SNMP trap: No
Fatal error: SYS4 program not found on the storage medium. SYS4366 is only
on the X81 stream at this time.
Action:
Severity: Critical.
SYS4367
SNMP trap: No
FATAL ERROR: If any of the packages listed below are equipped, the
QPC948B ROM must be used. This message will always be given in
conjunction with a SYS0088 message. The packages are: IDA, DPNSS, and
DASS. This message applies to the ST machine only.
Action:
Severity: Critical.
SYS4370
SNMP trap: No
FATAL ERROR: You must use QPC948B ROM if any of the following
packages are equipped: IDA, DPNSS and DASS.
Action:
Severity: Critical.
SYS4371
SNMP trap: No
RPA data lost: in proc rpax_parm_blk; dnxlptr is nil.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2130 of 2360

SYS4372
rpa data lost; in proc rpax_parm_blk; rpa_ffc_parm_ptr already exists.

Action:
Severity: Critical.
SYS4373
SNMP trap: Yes
RPA data lost; in proc rpax_parm_blk; not enough memory for rpax parameter
blk.
Action:
Severity: Critical.
SYS4374
SNMP trap: Yes
RPA data lost; in proc rpasys_head_blk; rpa_system_ptr: p_aux_cust_hdr not

nil, data already exists.
Action:
Severity: Critical.
SYS4375
SNMP trap: Yes
RPA data lost, in proc rpasys_head_blk, not enough memory for

rpa_system_blk or system parameter block.
Action:
Severity: Critical.
SYS4376
SNMP trap: Yes
RPA data lost; in proc rpasys_parm_blk, rpa_system_ptr: p_aux_cust_hdr is

nil.
Action:
Severity: Critical.
SYS4377
SNMP trap: Yes
RPA data lost; in proc rpasys_parm_blk,

Action:
Severity: Info.
SYS4379
SNMP trap: Yes
RPA data lost; in proc rpa_dnpsa_tree, not enough memory for rpa dn block
or dn-psa block.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2131 of 2360

SYS4380
RPA data lost; in proc rpa_dnpsa_tree, digit should not be 0.

Action:
Severity: Critical.
SYS4381
SNMP trap: Yes
RPA data lost; in proc rpa_dnpsa_tree, result from rpa_trans is

not.rpa_invalid_dn.
Action:
Severity: Critical.
SYS4382
SNMP trap: Yes
RPA data lost; in proc rpa_trans, dnxlptr is nil or digit_count is greater than the
maximum size of digit corruption in dn psa tree.
Action:
Severity: Critical.
SYS4383
SNMP trap: Yes
RPA data lost; in proc valid_ffc, wrong data type.

Action:
Severity: Critical.
SYS4384
SNMP trap: Yes
PGIP and PGSP FFCs will not be rebuilt when loading phase 6.65 and up.
Action:
Severity: Critical.
SYS4387
SNMP trap: Yes
Cannot get pds for the idc name block.

Action:
Severity: Critical.
SYS4391
SNMP trap: Yes
1.5 Mb/s DTI/PRI pad category table data can only be loaded when GPRI
package (167) is equipped.
Action:
Severity: Critical.
SYS4392
SNMP trap: Yes
SCART/SCORE site ID different.

Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 2132 of 2360

SYS4393 x
Due to the Security Cartridge feature Flash ROM on device x has failed
checksum: x = 4 indicates cartridge Flash ROM x = 8 indicates SCORE Flash
ROM
Action:
Severity: Critical.
SYS4394 x
SNMP trap: No
Cannot find a directory record on device x. x = 4 indicates cartridge Flash ROM

x = 8 indicates SCORE Flash ROM
Action: If x is not shown, then system should not load. Contact your technical
support group.
Severity: Critical.
SYS4395
SNMP trap: No
Unable to read control record.

Action:
Severity: Critical.
SYS4397
SNMP trap: No
Both Flash ROMs failed checksum.

Action:
Severity: Critical.
SYS4398
SNMP trap: No
SNMP trap: No
SNMP trap: Yes
Flash interface not idle.

Action:
Severity: Critical.
SYS4399
Security check failed.

Action:
Severity: Critical.
SYS4400
Could not post-process Digital DPNSS Signaling Link (DDSL).

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2133 of 2360

SYS4401
Analog Private Network Signaling System (APNSS) TN lost.

Action:
Severity: Critical.
SYS4402
SNMP trap: Yes
FAXS package is removed because EES package is not equipped.

Action:
Severity: Critical.
SYS4405
SNMP trap: Yes
AMP package 78 is not allowed on this machine type.

Action:
Severity: Critical.
SYS4406
SNMP trap: Yes
MFC package 128 is not allowed on this machine type.

Action:
Severity: Critical.
SYS4407
SNMP trap: No
MFE package 135 is not allowed on this machine type.

Action:
Severity: Critical.
SYS4408
SNMP trap: No
L1 package 188 is not allowed on this machine type.

Action:
Severity: Critical.
SYS4411
SNMP trap: No
Prerequisite package is missing during a sysload with EMCT package. EMCT

Action:
Severity: Critical.
SYS4413
SNMP trap: No
The number of DSLs has reached the limit. No further DSLs can be loaded.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2134 of 2360

SYS4414
Cannot allocate protected storage.

Action:
Severity: Critical.
SYS4415
SNMP trap: Yes
Cannot find Digital Subscriber Loop (DSL) data.

Action:
Severity: Critical.
SYS4416
SNMP trap: Yes
Basic Rate Interface (BRI) package restricted.

Action:
Severity: Critical.
SYS4418
SNMP trap: Yes
MISP cannot be associated with line card because protected card data block
for the card does not exist.
Action:
Severity: Critical.
SYS4419
SNMP trap: Yes
SNMP trap: Yes
Cannot find USID map.

Action:
Severity: Critical.
SYS4420 dn
Warning: Multiple TNs associated with BRI DN.

Action:
Severity: Critical.
SYS4421
SNMP trap: Yes
The number of Logical Terminal IDs has reached the limit. No further LTIDs
can be loaded.
Action:
Severity: Critical.
SYS4422
SNMP trap: Yes
JDMI package 136 is not supported on this machine type.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2135 of 2360

SYS4423 CUST x DN xxxx TN l s c u During DN translation in sysload, no MARP or more than
one MARP was found in the database for DN "nnnn" in customer "x". Only one
MARP should be defined for a DN. The MARP database information for TN "l
s c u" has been corrected and a default MARP TN selected for the DN. This
corrected database can be saved or altered further by service change before
saving with a data dump.
Action:
Severity: Critical.
SYS4426
SNMP trap: Yes
MSDL/MISP master table does not exist or cannot be allocated. Output:

MSDL/MISP {msdlmisp index in decimal}.
Action:
Severity: Critical.
SYS4427
SNMP trap: Yes
MSDL/MISP index is invalid. Output: SYS4427 MSDL/MISP {msdlmisp index

in decimal}.
Action:
Severity: Critical.
SYS4428
SNMP trap: Yes
MSDL/MISP MSDL_MISP_BLOCK does not exist. Output: SYS4428 SID BLK

{msdlmisp index in decimal}.
Action:
Severity: Critical.
SYS4429
SNMP trap: Yes
Conv: No memory is available. Cannot allocate the phy_dump_array

structure.
Action:
Severity: Critical.
SYS4430
SNMP trap: Yes
Conv: No memory is available. Cannot allocate the p_async_block structure.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2136 of 2360

SYS4431
SYS4431 = Conv: The conversion of ESDI asynchronous data block failed,

because the corresponding P_ASYNC_BLOCK cannot be found, due to a
database corruption.
Action:
Severity: Critical.
SYS4432
SNMP trap: Yes
Conversion of CSL failed: The ESDI parameter download data block is

missing from the database.
Action:
Severity: Critical.
SYS4433
SNMP trap: Yes
SYS4433 = Conversion of CSL failed: The ESDI parameter download data

block is not set up for the synchronous mode.
Action:
Severity: Critical.
SYS4434
SNMP trap: Yes
Conv: The required entry in DUMP_CARD_TYPE structure is not free and is

in use by another IO unit. Output: INDX: {occupied physical address in
decimal} . CARD: {card type in decimal. This is the card type occupying the
entry, which we assumed to be free.}
Action:
Severity: Critical.
SYS4435
SNMP trap: Yes
Conv: The XSM is lost because the SDI data block was not previously created,
due to an earlier error.
Action:
Severity: Critical.
SYS4436
SNMP trap: Yes
The block PHY_ARRAY is missing. It must exist and should have been loaded
from tape. Therefore this is a database corruption.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2137 of 2360

SYS4437 SDI x
The P_SDI_BLK_PTR pointer is nil for the given logical SDI number in
decimal. This indicates one of the following: 1. Corruption in the configuration
record 2. Corruption in the P_SDI_BLK_PTR To be consistent,
CONFIGTTYOP is zeroed out for the specific device.
Action:
Severity: Critical.
SYS4438
SNMP trap: Yes
Corrupt database. Bad card type. Only SDI, SDI2, XSDI, SDI4, DCHI and
MSDL cards are allowed for asynchronous IO. Output: CARD: {card type in
decimal} SDI: {sdi number in decimal}
Action:
Severity: Critical.
SYS4439 SDI x
SNMP trap: Yes
The P_SDI_BLK_PTR pointer is nil for the given SDI number in decimal. This
indicates one of the following: 1. Corruption in the configuration record. 2.
Corruption in the P_SDI_BLK_PTR To be consistent, CONFIGTTYOP is
zeroed out for the specific device.
Action:
Severity: Critical.
SYS4440
SNMP trap: Yes
Procedure GET_PHY_BLK failed: dev_no is not valid. Output: LU TYPE:

{logical application type in decimal} LOG NUM: {logical application number in
decimal} DEV NUM: {physical device number in decimal} PRIO NUM: {IO
polling table priority number in decimal} OPTION: {optional parameter in
decimal}
Action:
Severity: Critical.
SYS4441
SNMP trap: Yes
Procedure GET_PHY_BLK failed: port_no is not valid. Output: LU TYPE:

{logical application type in decimal} LOG NUM: {logical application number in
decimal} DEV NUM: {physical device number in decimal} PRIO NUM: {IO
polling table priority number in decimal} OPTION: {optional parameter in
decimal}
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2138 of 2360

SYS4442
Procedure GET_PHY_BLK failed: Too many TTY, printer, DCH, AML or

MSDL units. Output: LU TYPE: {logical application type in decimal} LOG NUM:
{logical application number in decimal} DEV NUM: {physical device number in
decimal} PRIO NUM: {IO polling table priority number in decimal} OPTION:
{optional parameter in decimal}
Action:
Severity: Critical.
SYS4443
SNMP trap: Yes
Procedure GET_PHY_BLK failed: Undefined logical application type. Output:

LU TYPE: {logical application type in decimal} LOG NUM: {logical application
number in decimal} DEV NUM: {physical device number in decimal} PRIO
NUM: {IO polling table priority number in decimal} OPTION: {optional
parameter in decimal}
Action:
Severity: Critical.
SYS4444
SNMP trap: Yes
Procedure GET_PHY_BLK failed: Cannot allocate PDS for the physical IO

block. LU TYPE: {logical application type in decimal} LOG NUM: {logical
application number in decimal} DEV NUM: {physical device number in
Action:
Severity: Critical.
SYS4445
SNMP trap: Yes
Procedure GET_PHY_BLK failed: Too many loop devices and serial card
devices. Output: LU TYPE: {logical application type in decimal} LOG NUM:
{logical application number in decimal}= DEV NUM: {physical device number
in decimal} PRIO NUM: {IO polling table priority number in decimal} OPTION:
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2139 of 2360

SYS4446
Procedure GET_PHY_BLK failed: Cannot find the physical IO block previously

allocated. Output: LU TYPE: {logical application type in decimal} LOG NUM:
Action:
Severity: Critical.
SYS4447
SNMP trap: Yes
Procedure GET_PHY_BLK failed: The port is already in use by another

application. Output: LU TYPE: {logical application type in decimal} LOG NUM:
Action:
Severity: Critical.
SYS4448
SNMP trap: Yes
The MSDLMISP socket ID data structures do not exist.

Action:
Severity: Critical.
SYS4449
SNMP trap: Yes
Database corruption. The P_ESDI_TBL_HDR is nil. Output: CSL {esdi

number in decimal}.
Action:
Severity: Critical.
SYS4450
SNMP trap: Yes
Database corruption. The content of pointer

P_ESDI_BLK_PTR[ESDI_PORT_NO]: P_ESDI_TBL_HDR is nil. Output:
CSL {esdi number in decimal}.
Action:
Severity: Critical.
SYS4451
SNMP trap: Yes
The given AML number is removed from the VAS list belonging to the given
VAS number, since the protected AML data block belonging to the given AML
number, does not exist. Output: VAS {vas number in decimal}.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2140 of 2360

SYS4452
Corruption: The ESDI block number 49 is removed from X11 Release 18. It is
not allowed to exist in X11 Release 18 and later, databases. Output: ESDI
{esdi number in decimal}.
Action:
Severity: Critical.
SYS4453
SNMP trap: Yes
Corruption: The CSL block number 50 is removed from X11 Release 18. It is
not allowed to exist in X11 Release 18 and later, databases. Output: AML {aml
number in decimal}.
Action:
Severity: Critical.
SYS4454
SNMP trap: Yes
Corruption. The PHY_BLK_PNTR is nil. The pointer should point to

PHY_ARRAY and must have been loaded from tape previously. As a result
the given AML block is disregarded. Output: AML {aml number in decimal}.
Action:
Severity: Critical.
SYS4455 x
SNMP trap: Yes
Warning: AML x is not loaded because the address is occupied by a previously

loaded device. X11 Release 17 and earlier can configure an unused ESDI
AML on top of an existing port. X11 Release 18 and later removes the unused
ESDI.
Action:
Severity: Critical.
SYS4456
SNMP trap: Yes
The logical IO table header for csl_log_appli type for the given logical AML
number cannot be set up. As a result the given AML block is disregarded.
Output: AML {aml number in decimal}.
Action:
Severity: Critical.
SYS4457
SNMP trap: Yes
The X25 block type (i.e., block 75) is no longer supported. Output: X25 {X25
number (i.e., esdi number) in decimal}.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2141 of 2360

SYS4458
The logical master head IO tables cannot be allocated due to lack of memory.
As a result the given DCH block is disregarded. Output: DCH {dch number in
decimal}.
Action:
Severity: Critical.
SYS4459
SNMP trap: Yes
The AML number is out-of-range. Output: AML {aml number in decimal}.

Action:
Severity: Critical.
SYS4460
SNMP trap: Yes
The SDI number is out of range. Output: SDI {sdi number id decimal}.
Action:
Severity: Critical.
SYS4461
SNMP trap: Yes
Warning: Since the physical dump array block is not loaded from tape then it
is created blindly. The reasons that the block is missing from the tape are: 1.
Conversion from Release 17 to 18 failed. 2. The tape has only the minimum
database (i.e., only the configuration record and no other database). This last
case is not a database conversion or loading corruption and is normal.
Action:
Severity: Critical.
SYS4462
SNMP trap: Yes
Failed to allocate memory for logical master head I/O table, or failed to allocate
memory for the physical DUMP_CARD_TYPE structures.
Action:
Severity: Critical.
SYS4463
SNMP trap: Yes
Failed to allocate memory for P_ASYNC_BLOCK structure. Output: INDX: {sdi

number in decimal}.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2142 of 2360

SYS4464
The asynchronous application type is not allowed on the ESDI card type
starting from RLS 18. Output: INDX: {sdi number in decimal}.
Action:
Severity: Critical.
SYS4465
SNMP trap: Yes
Warning: Since the card type for the given SDI application type was bad, the
memory previously allocated for the given SDI application type, is released.
Output: INDX: {sdi number in decimal}.
Action:
Severity: Critical.
SYS4466
SNMP trap: Yes
Warning: Since user types are defined but their logical SDI data structures do
not exist, due to a corruption, the user types are cleared from the configuration
record data structure. Output: INDX: {sdi number in decimal}.
Action:
Severity: Critical.
SYS4467 XSDI
SNMP trap: Yes
Block type number 93 is no longer supported starting from X11 Release 18.
Action:
Severity: Critical.
SYS4468 XSDI
SNMP trap: Yes
Out of PDS to allocate SDI_MHT_BLK block type.

Action:
Severity: Critical.
SYS4469
SNMP trap: Yes
The History File cannot be allocated, because of package restriction, or

because there is no more space in the I/O polling table.
Action:
Severity: Critical.
SYS4470
SNMP trap: Yes
ISM limit for the D-channel is reached. The total D-channels configured on the
existing database, is more than the number the customer is allowed to have.
Output: DCH {dch number in decimal}.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2143 of 2360

SYS4471
ISM limit for the AML is reached. The total AML links configured on the existing
database, is more than the number the customer is allowed to have. Output:
AML {aml number in decimal}.
Action:
Severity: Critical.
SYS4472
SNMP trap: Yes
Both MSDL and BRI packages are restricted, so the data associated with the
MSDl or MISP cards is not loaded.
Action:
Severity: Critical.
SYS4474
SNMP trap: Yes
Corrupt database. Bad card type. Only DCHI and MSDL cards are allowed for
DCH links. Output: CARD: {card type in decimal} DCHI {dch number in
decimal}
Action:
Severity: Critical.
SYS4475
SNMP trap: Yes
Corrupt database. Bad card type. Only ESDI and MSDL cards are allowed for
AML links. Output: CARD: {card type in decimal} AML {aml number in decimal}
Action:
Severity: Critical.
SYS4476
SNMP trap: Yes
FNP package not equipped, cannot load DTAD data.

Action:
Severity: Critical.
SYS4477
SNMP trap: Yes
FC68 package 223 and Japan Trunk package 97 are mutually exclusive. FC68
package is turned off automatically.
Action:
Severity: Critical.
SYS4480
SNMP trap: Yes
Cannot allocate memory for a group I/O table.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2144 of 2360

SYS4481
The Network Call Pickup package has been restricted because some or all of
its prerequisite packages are not equipped.
Action:
Severity: Critical.
SYS4500 x
SNMP trap: No
Skipping slot x. Cannot calculate address to check for CP with cable.

Action:
Severity: Critical.
SYS4501 x
SNMP trap: No
Skipping slot x. Cannot get card ID.

Action:
Severity: Critical.
SYS4502
SNMP trap: No
Timeout waiting for response from remote CP.

Action: Check that both CPs have the same number of SIMMs.
Severity: Critical.
SYS4503
SNMP trap: No
Remote processor is not CP.

Action: Be sure remote processor is CP.
Severity: Critical.
SYS4504
SNMP trap: No
CP redundancy impossible. No CP to CP cable.

Action:
Severity: Critical.
SYS4505
SNMP trap: No
CP redundancy impossible. There is no remote power.

Action: Check CE power supply on remote Core module. Be sure the CP to CP
cable is properly connected.
Severity: Critical.
SYS4506
SNMP trap: No
CP redundancy impossible. Both shelves have the same ID.

Action: Set the JB4 jumper on the backplane so both sides match.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2145 of 2360

SYS4507
CP redundancy impossible. Both switches are in MAINT.

Action: Check that at least one of the CP Norm/Maint switches is in Norm mode
(up).
Severity: Critical.
SYS4508
SNMP trap: No
CP single mode: could not synchronize CSA space.

Action:
Severity: Critical.
SYS4509
SNMP trap: No
Could not set CP semaphore bit (side x).

Action:
Severity: Critical.
SYS4510
SNMP trap: No
CP single mode: memory shadow test failed.

Action: Reseat or replace the Standby CP.
Severity: Critical.
SYS4511 x
SNMP trap: No
Cannot open BIC window (slot x). Cannot check for CP cable.
Action:
Severity: Critical.
SYS4512 x
SNMP trap: No
Cannot close BIC window (slot x).

Action:
Severity: Critical.
SYS4513 x
SNMP trap: No
Could not get CP semaphore bit (side x).

Action:
Severity: Critical.
SYS4514 x
SNMP trap: No
Skipping slot x, cannot calculate address to see if CP bit is set.

Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 2146 of 2360

SYS4515
Unable to find the active CMDU.

Action:
Severity: Critical.
SYS4516
SNMP trap: No
Unable to find the diskos.sym file.

Action:
Severity: Critical.
SYS4517 x
SNMP trap: No
Switching from CPU x to preferred side.

Action:
Severity: Critical.
SYS4520
SNMP trap: No
Cannot get available memory for SL-1 Memory Control from Memory
management. Sysload fails due to lack of memory.
Action:
Severity: Critical.
SYS4521
SNMP trap: Yes
Cannot turn on memory protection. Input address is invalid.

Action:
Severity: Critical.
SYS4522
SNMP trap: Yes
Cannot turn off memory protection. Input address is invalid.

Action:
Severity: Critical.
SNMP trap: Yes
SYS4523 yyyy mm dd hh:mm:ss HD0 Database data dumped yyyy/mm/dd hh:mm:ss.

Action:
Severity: Critical.
SNMP trap: No
SYS4525 yyyy mm dd hh:mm:ss HD0 Database data dumped yyyy/mm/dd hh:mm:ss.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2147 of 2360

SYS4527 iiii dd/mm/yyyy hh:mm:ss rr This message refers to the X11 release and issue (iiii),
date and time (dd/mm/yyyy hh:mm:ss) and size (rr) of the database to be
sysloaded. The date and time indicate when the file was last written.
Action:
Severity: Critical.
SNMP trap: No
SYS4528 yyyy mm dd hh:mm:ss HD Database data dumped yyyy/mm/dd hh:mm:ss.

Action:
Severity: Critical.
SNMP trap: No
SYS4529 yyyy mm dd hh:mm:ss FD0 Database data dumped yyyy/mm/dd hh:mm:ss.

Action:
Severity: Critical.
SNMP trap: No
SYS4530 yyyy mm dd hh:mm:ss FD1 Database data dumped yyyy/mm/dd hh:mm:ss.

Action:
Severity: Critical.
SYS4531
SNMP trap: No
During conversion, XTD and/or RDB DFQ has been changed to XTDT.
Action: Consult NTPs and LD 97, LD 20 and LD 21 to ensure that configuration
is as desired for XTD operation.
Severity: Critical.
SYS4532
SNMP trap: Yes
The CPSI entry cannot be allocated; the limit for SIO devices has been
reached.
Action:
Severity: Critical.
SYS4533
SNMP trap: Yes
Cannot allocate protected data store for XTD table. Table not loaded.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2148 of 2360

SYS4534
Warning: IEN package or SACP package not equipped. Configured IEN ICI
keys are removed. Procedure REMOVE_IEN_ICI (module SYSPP).
Action:
Severity: Critical.
SYS4535
SNMP trap: Yes
Warning: IEN Block Timer is reset to its default value because SACP or NAS
package is not equipped.
Action:
Severity: Critical.
SYS4538
SNMP trap: Yes
Inconsistencies in boundaries of previous SL1 load.

Action:
Severity: Critical.
SYS4539
SNMP trap: No
Inconsistencies in boundaries of previous Overlay load.

Action:
Severity: Critical.
SYS4540
SNMP trap: No
Error loading SL-1 file into memory.

Action:
Severity: Critical.
SYS4541
SNMP trap: No
Error loading overlay file into memory.

Action:
Severity: Critical.
SYS4542
SNMP trap: No
Error in loading, last address {n}.

Action:
Severity: Critical.
SYS4543
SNMP trap: No
Error returned from segInit2{n}.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2149 of 2360

SYS4544
Error getting dloPathFileName for ovlres.

Severity: Critical.
SYS4545
SNMP trap: No
Unable to open {file name}.

Severity: Critical.
SYS4546
SNMP trap: No
Error sl1_start_addr {n}, last sl1_prot_address {x}.

Action:
Severity: Critical.
SYS4547
SNMP trap: No
Error initializing SL-1 pool and data area.

Action:
Severity: Critical.
SYS4548
SNMP trap: No
Error getting dloPathFileName for ovlres.

Severity: Critical.
SYS4549
SNMP trap: No
Unable to open {file name}.

Severity: Critical.
SYS4550
SNMP trap: No
Error in loading, last SL-1 address {n}.

Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 2150 of 2360

SYS4551
Overlay start address {n} overlaps end of SL-1 area {x}.

Action:
Severity: Critical.
SYS4552
SNMP trap: No
Error ovl_start_addr {n}, last_ovl_prot_addr {x}.

Action:
Severity: Critical.
SYS4553
SNMP trap: No
Error initializing overlay data area.

Action:
Severity: Critical.
SYS4554
SNMP trap: No
Error calling ovlres entry.

Action:
Severity: Critical.
SYS4555
SNMP trap: No
Invalid parameter to ldrNextPage, address {n}.

Action:
Severity: Critical.
SYS4556
SNMP trap: No
Seek error while loading (OVL or INSTALL) code file.

Action:
Severity: Critical.
SYS4557
SNMP trap: No
Error reading a_out header from file (OVL or INSTALL).

Severity: Critical.
SYS4558
SNMP trap: No
Invalid a_out header in file.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2151 of 2360

SYS4559
Error reading link header.

Severity: Critical.
SYS4560
SNMP trap: No
Invalid link header in file.

Action:
Severity: Critical.
SYS4561
SNMP trap: No

Action:
Severity: Critical.
SYS4562
SNMP trap: No
Seek error while loading (OVL or INSTALL) code file.

Severity: Critical.
SYS4563
SNMP trap: No
Error reading a_out header into memory (OVL or INSTALL).

Severity: Critical.
SYS4564
SNMP trap: No
Error reading text segment from disk into memory (OVL or INSTALL).
Severity: Critical.
SYS4565
SNMP trap: No
Error reading data segment from disk into memory (OVL or INSTALL). Reload
the system with the Manual Reload button.
Severity: Critical.
SNMP trap: No
System Messages
Page 2152 of 2360

SYS4566
Seek error while loading SL-1 code.

Severity: Critical.
SYS4567
SNMP trap: No
Error reading a_out file from SL-1 file.

Severity: Critical.
SYS4568
SNMP trap: No
Invalid a_out header in SL-1 file.

Action:
Severity: Critical.
SYS4569
SNMP trap: No
Error reading link header from file.

Severity: Critical.
SYS4570
SNMP trap: No
Invalid link header in file.

Action:
Severity: Critical.
SYS4571
SNMP trap: No

Action:
Severity: Critical.
SYS4572
SNMP trap: No
Seek error while loading code.

Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2153 of 2360

SYS4573
Error reading a_out header from disk into memory.

Severity: Critical.
SYS4574
SNMP trap: No
Error reading text segment from disk into memory.

Severity: Critical.
SYS4575
SNMP trap: No
Invalid data segment in SL-1 module.

Action:
Severity: Critical.
SYS4576
SNMP trap: No
Error access in code file.

Severity: Critical.
SYS4577
SNMP trap: No
Error reading data segment from disk into memory.

Action: Reload the system with the Manual Reload button.
Severity: Critical.
SYS4578
SNMP trap: No
Invalid a_out header in memory (OVL or INSTALL).

Action:
Severity: Critical.
SYS4579
SNMP trap: No
Invalid link header in memory (OVL or INSTALL).

Action:
Severity: Critical.
SYS4580 x
SNMP trap: No
End of Protected data = x (OVL or INSTALL).

Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 2154 of 2360

SYS4581 x y
Unprotected data start x overlaps Unprotected data end at y (OVL or

INSTALL).
Action:
Severity: Critical.
SYS4582
SNMP trap: No
Error copying data from Protected memory to Unprotected memory for static
modules.
Severity: Critical.
SYS4583
SNMP trap: No
Invalid a_out header in memory.

Action:
Severity: Critical.
SYS4584
SNMP trap: No
Invalid link header in memory.

Action:
Severity: Critical.
SYS4585 x
SNMP trap: No
End of Protected data = x.

Action:
Severity: Critical.
SYS4586 x y
SNMP trap: No
Unprotected data start x overlaps Protected data end at y.

Action:
Severity: Critical.
SYS4587
SNMP trap: No
Error copying data from Protected memory to Unprotected memory for SL-1
modules.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2155 of 2360

SYS4589
Customer n has DITI = YES in LD15 but the DID to TIE package 176 is
equipped, DID to TIE calls will be restricted by the DID to TIE package.
Action:
Severity: Critical.
SYS4590
SNMP trap: Yes
BRIT package restricted.

Action:
Severity: Critical.
SYS4592
SNMP trap: Yes
BRIL package restricted.

Action:
Severity: Critical.
SYS4593
SNMP trap: Yes
Either the BRIL or the BRIT package needs to be equipped.

Action:
Severity: Critical.
SYS4594
SNMP trap: Yes
BRIL application will not be configured on any MISP because the BRIL
Action:
Severity: Critical.
SYS4595
SNMP trap: Yes
BRIT application will not be configured on any MISP because the BRIT
Action:
Severity: Critical.
SYS4596 xx yy
SNMP trap: Yes
PEMD data in the route datablock was erased due to PEMD package
restriction. Where: xx = customer number yy = route number
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2156 of 2360

SYS4600
The DTI package is restricted and either the BRIT package is restricted or the
DTI2 package is equipped or the PRI2 package is equipped.
Action:
Severity: Critical.
SYS4601
SNMP trap: Yes
M911 package is restricted, therefore NPID block cannot be loaded in

memory.
Action:
Severity: Critical.
SYS4602
SNMP trap: Yes
NPID block exceeds length of block allocated.

Action:
Severity: Critical.
SYS4605 xx
SNMP trap: Yes
SICA Table xx is erased due to PEMD package restriction.

Action:
Severity: Critical.
SYS4606 x
SNMP trap: Yes
That CDR Link port has been removed.

Action:
Severity: Critical.
SYS4607 x
SNMP trap: Yes
That Low speed Link port has been removed.

Action:
Severity: Critical.
SYS4608
SNMP trap: Yes
The port allocated for STA is being used by another application.

Action:
Severity: Critical.
SYS4609
SNMP trap: Yes
STA logical number is out-of-range.

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2157 of 2360

SYS4610
STA logical number is out-of-range.

Action:
Severity: Critical.
SYS4613
SNMP trap: Yes
Protected loop block does not exist.

Action:
Severity: Critical.
SYS4614
SNMP trap: Yes
Cannot update card pointers to BRSC data block because card data blocks
exist.
Action:
Severity: Critical.
SYS4615
SNMP trap: Yes
Cannot associate BRSC with line card because protected card data block
does not exist.
Action:
Severity: Critical.
SNMP trap: Yes
SYS4616 xxxx yyyy Unable to allocate protected data storage for DCH call reference table.
Where: xxxx = mnemonic of feature affected yyyy = name of data structure
affected
Action:
Severity: Critical.
SYS4617
SNMP trap: Yes
Unable to allocate protected data storage for limited access to Overlays

(LAPW). The LAPW package has been restricted.
Action:
Severity: Critical.
SYS4620
SNMP trap: Yes
Attendant Blocking of Extension feature turned off because SACP package is

not equipped.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2158 of 2360

SYS4623
IPRA package is restricted, but there is an international interface. The

interface cannot be enabled with the current software packaging.
Action:
Severity: Critical.
SYS4624
SNMP trap: Yes
The number of Meridian 1 Packet Handler Digital Subscriber Loops (DSLs)

reached the limit. No further MPH DSLs can be sysloaded.
Action:
Severity: Critical.
SYS4625
SNMP trap: Yes
B Channel TN not in MPH loop data block.

Action:
Severity: Critical.
SYS4626
SNMP trap: Yes
LAPB data block does not exist.

Action:
Severity: Critical.
SYS4627
SNMP trap: Yes
X25P data block does not exist.

Action:
Severity: Critical.
SYS4628
SNMP trap: Yes
Resident code is compressed, but the decoding table does not exist.
Action:
Severity: Critical.
SYS4629
SNMP trap: No
Meridian 1 packet handler (MPH) package is restricted.

Action:
Severity: Critical.
SYS4630
SNMP trap: Yes
The MPH application cannot be configured on an MISP because the MPH

Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2159 of 2360

SYS4631
KD3 Package unequipped - Data is discarded.

Action:
Severity: Critical.
SYS4632
SNMP trap: Yes
MFK5/MFK6 data corruption.

Action:
Severity: Critical.
SYS4633 n
SNMP trap: Yes
Cannot load data block for PRI loop n when INBD package is restricted.
Action:
Severity: Critical.
SYS4634 n
SNMP trap: Yes
Backup D-channel n is not loaded for this interface.

Action:
Severity: Critical.
SYS4635
SNMP trap: Yes
Cannot allocate Protected Data Store for AOC parsing tables.

Action:
Severity: Critical.
SYS4636
SNMP trap: Yes
The Voice Mailbox Administration data block exists without the feature
configured.
Action: Contact your technical support personnel.
Severity: Critical.
SYS4637
SNMP trap: Yes
The Voice Mailbox Administration data block contains invalid TNs.

Severity: Critical.
SYS4638
SNMP trap: Yes
There is no memory available to build the Voice Mailbox data block.

Severity: Critical.
SNMP trap: Yes
System Messages
Page 2160 of 2360

SYS4639
Voice Mailbox data exists without the feature package configured. The
mailbox data has been discarded.
Severity: Critical.
SYS4640
SNMP trap: Yes
Voice Mailbox Administration application data exists with the feature package
restricted. The application data is discarded.
Severity: Critical.
SYS4641
SNMP trap: Yes
Superloops 32, 36, 40, 48 have been added to the configuration. This only
occurs when upgrading to the Option 11E CPU and these loops do not already
exist. No action required. Standard message for the auto-configuration of
superloop data.
Action:
Severity: Critical.
SYS4642
SNMP trap: Yes
Superloops 32, 36, 40, 48 have NOT been added to the configuration. This
message only occurs when upgrading to the Option 11E CPU and one of
these loops is already configured.
Action: Check that the configuration is as desired. If a third box is being added
to the system then superloops 32, 36, 40, and 48 must exist.
Severity: Critical.
SYS4643
SNMP trap: Yes
M2317 data block cannot be loaded when package is not equipped.

Action:
Severity: Critical.
SYS4645
SNMP trap: Yes
Only one of the language packages may be equipped. The MLMS feature has
been disabled.
Action: Reinstall the system.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2161 of 2360

SYS4646
Mismatch between language pkg read at cold start and during SYSLOAD.
Action: Print out the list of equipped packages in LD 22. If the list does not match
that on the label,
Severity: Info.
SYS4648 lll
SNMP trap: Yes
Phantom loop {lll} is found, but the PHTN package is restricted. Phantom loop
{lll} is not loaded. All phantom TNs configured on this loop will not be loaded
and existing SYS messages will be given. OUTPUT: lll = phantom loop
number
Action:
Severity: Critical.
SYS4649
SNMP trap: Yes
MCT data exists without the MCT package. The data is cleared.
Action:
Severity: Critical.
SYS4650
SNMP trap: Yes
SCDR data exists without the SCDR package. The data is cleared.
Action:
Severity: Critical.
SYS4651
SNMP trap: Yes
CDR link and the MCT packages are mutually exclusive. The CDR link
package is turned off.
Action:
Severity: Critical.
SYS4653
SNMP trap: Yes
A BCS Phantom loop is found, but either the phantom or csl package is not
equipped.
Action: Remove the loop and all associated data.
Severity: Critical.
SYS4654
SNMP trap: Yes
Procedure SAMM_PBX_SRVR . Standalone Meridian Mail server not loaded

- out of PDATA
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2162 of 2360

SYS4655
Procedure SAMM_PBX_SRVR . Too many Standalone Meridian Mail servers

loaded, not included in the table, TN not loaded.
Action:
Severity: Critical.
SYS4656
SNMP trap: Yes
Cannot allocate protected data store for xpec. This error message will be
called from new proc SETUP_INIT_XPEC in MODULE SYS4XXX.
Action:
Severity: Critical.
SYS4657
SNMP trap: Yes
Warning. Existing CIST data are removed because CIST package 221 is
restricted.
Action:
Severity: Critical.
SYS4658
SNMP trap: Yes
Existing ACRL data is removed because the ACRL package is restricted.

Enable the ACRL package and reload the system.
Action:
Severity: Critical.
SYS4663
SNMP trap: Yes
TN 0 0 0 0 is not valid. TN is rejected

Action:
Severity: Critical.
SYS4664
SNMP trap: Yes
LAPW password nn is removed because it is a Set Based Administration

password and the ADMINSET package is restricted.
Action:
Severity: Critical.
SYS4665
SNMP trap: Yes
Set Based Administration login limits are set to zero because the ADMINSET
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2163 of 2360

SYS4667
On sysload, CCB data exists, but the CCB package is restricted.

Action: CCB data is cleared.
Severity: Critical.
SYS4668
SNMP trap: Yes
Call Pickup Network Wide cannot be loaded as ISDN package 145 is

restricted.
Action: Load with ISDN package equipped.
Severity: Critical.
SYS4669
SNMP trap: Yes
The DPNSS_ES package is equipped, but the DPNSS package is not.

Action: Since DPNSS is a pre-requisite for DPNSS_ES, DPNSS_ES is forced
unequipped.
Severity: Critical.
SYS4679
SNMP trap: Yes
CAC defined for BCS, PBX or route exceeds the CIS maximum range for CAC
(9). CAC is set to CIS default value for CAC (3).
Action:
Severity: Critical.
SYS4680
SNMP trap: Yes
AANN block cannot be loaded: data has been cleared.

Action:
Severity: Critical.
SYS4681
SNMP trap: Yes
AANN block cannot be loaded due to package restriction: the data has been
cleared.
Action:
Severity: Critical.
SYS4682
SNMP trap: Yes
AANN data in route data block has been disabled due to package restriction:
the data has been cleared.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2164 of 2360

SYS4690
China Attendant Monitor Package (CHINA) package 285 is not equipped but
the Attendant Monitor option is allowed, then the options are reset to disable
the China Attendant Monitor feature.
Action:
Severity: Critical.
SYS4691
SNMP trap: Yes
BTD package is not equipped, the BTD tables have been removed.
Action:
Severity: Critical.
SYS4692
SNMP trap: Yes
Unable to allocate protected memory for BTD Table 0.

Action:
Severity: Critical.
SNMP trap: Yes
SYS4694 (CDB cc and/or RDB rr) Due to unequipped IDC package, IDC data has been lost in
customer cc or IDC data has been lost in Route rr of Customer cc.
Action:
Severity: Critical.
SYS4695
SNMP trap: Yes
The mnemonic, filter and exception tables have been removed. NOTE: Their
functionality has been replaced by the new Event Default and Preference
Tables for Option 81 switches.
Severity: Info.
SYS4696
SNMP trap: Yes
Auto-configuration of conference loop 62, 94 or 95 could not be done. Loop

62, 94 or 95 has already been defined.
Action: Use LD 22 to check your configuration record and use LD 17 to redefine
the conference loop.
Severity: Major.
SYS4697
SNMP trap: Yes
Auto-configuration of conference loop 62, 94 or 95 has performed

successfully.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2165 of 2360

SYS4698
If package 46 is not equipped and the feature is, it indicates that package 46
is not equipped and that the TMAR bit for customer y is cleared.
Action: To ensure that all the packages you have ordered are on the disk, refer
to the administration input/output guide and use LD 22 PRT, PKG. Check to
ensure there are no extra packages on the disk. Have your technical support
group contact Northern Telecom Customer Service for replacement software.
Severity: Minor.
SYS4699
SNMP trap: Yes
Warning: Existing ARDL data is reset to its default values, because ARDL
Severity: Major.
SYS4700
SNMP trap: Yes
A Secondary Call Park Block has been discarded due to CPRKNET package
missing.
Severity: Major.
SYS4701
SNMP trap: Yes
Customer Call Park option changed from CPN to CPA due to CPRKNET
package missing.
Severity: Major.
SNMP trap: Yes
System Messages
Page 2166 of 2360

SYS4702
A Secondary Call Park Block has been discarded since the customer does not
have a Primary Call Park Block.
Severity: Major.
SYS4706
SNMP trap: Yes
Warning: Clear CPP or TCPP for a non-ISDN trunk route if the OPOA package
is equipped.
Action:
Severity: Critical.
SYS4707 x
SNMP trap: Yes
A Sysload Warning Message indicates that the TAT database has been
removed due to the TAT package not being equipped in the M1 switch.
Action:
Severity: Critical.
SYS4708 x
SNMP trap: Yes
A Sysload Warning Message indicates that the TAT database has been
removed from the D-channels associated with the DCHI cards.
Action:
Severity: Critical.
SYS4712 cust
SNMP trap: Yes
PTU or MFC package not equipped; PTU data cleared in customer data block.
Action: Equip PTU and MFC packages and reload if PTU is required.
Severity: Critical.
SNMP trap: Yes
SYS4713 cust route PTU or MFC package not equipped; PTU data cleared in route data block.
Severity: Critical.
SNMP trap: Yes
SYS4714 cust table-number PTU and MFC packages are not equipped. PTU data cleared in
incoming R2MF table.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2167 of 2360

SYS4715
FFC or AWU package not equipped. WUD and STE data are cleared.
Action:
Severity: Critical.
SYS4716
SNMP trap: Yes
The VDN block cannot be loaded during SYSLOAD. The VNS database
cannot
Action:
Severity: Info.
SYS4717
SNMP trap: Yes
The ARDL package (304) and the OPOA package (104) are mutually
exclusive. ARDL package is automatically turned off.
Severity: Major.
SYS4718
SNMP trap: No
Cannot load EuroISDN Network Mode data when Master Mode package is
restricted.
Action: To ensure that all the packages you have ordered are on the disk refer
to the administration input/output guide and use LD 22 PRT, PKG . Check to
ensure that there are no extra packages on the disk. Have your technical support
Severity: Info.
SNMP trap: Yes
SYS4719 table-number PTU and MFC packages are not equipped. PTU data cleared in outgoing
R2MF table.
Severity: Info.
SYS4720
SNMP trap: Yes
Either the Speed Call or System Speed Call package is restricted and the data
exists.
Severity: Info.
SNMP trap: Yes
System Messages
Page 2168 of 2360

SYS4722
Customer Call Park data is lost due to Call Park database memory allocation
problems.
Severity: Major.
SYS4723
SNMP trap: Yes
Customer option is changed to CPD due to Call Park database memory

allocation problem.
Severity: Major.
SYS4729 xx
SNMP trap: Yes
xx = %DNIS MMCS information's were found and MMCS package is

restricted, the fields are set to default value INDGT, PRDL, INDI, DTIM, DIG#,
DIIE).
Severity: Info.
SYS4730
SNMP trap: No
Phantom DTI2 loop {lll} is found, but either the ISPC package or the DTI2
package is restricted. Phantom DTI2 loop {lll} is not loaded. All pahntom DTI2
TNs configured on this loop will not be loaded and existing SYS messages will
be given. OUTPUT: lll = phantom loop
Action: Unrestrict the ISPC package and the DTI2 package and then reload the
PBX if necessary.
Severity: Major.
SYS4731
SNMP trap: Yes
Unable to allocate protected memory for CLID Block or CLID table. Some
CLID entries may be lost.
Action: Use Overlay 21 to print the CLID entries. Configure the entries that are
needed.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2169 of 2360

SYS4732 {TN} x
MFC/MFE/MFK5/MFK6 trunk: the MF digi5t transmit level (MFL) for this trunk
has been changed to an MF transmit level identifier (MFLI) and has been given
a default value of 0. x is the former MFL, value for the TN.
Action: Use LD 97 to change the system transmit levels (MFTL0 and MFTL1)
and LD 14 to change the MFLI for each trunk.
Severity: Info.
SYS4733
SNMP trap: Yes
The GRDRC block is defined but no backup rules were found.

Action: The system removes the GRDRC block.
Severity: Minor.
SYS4734
SNMP trap: Yes
The backup rule defined in BKPS block was not found. The Backup Schedule
is removed.
Action:
Severity: Minor.
SYS5714
SNMP trap: Yes
Cannot allocate protected data store for XTD Table.

Action:
Severity: Critical.
SYS6692 x1
SNMP trap: No
x1 = %Invalid input when the MMCS package is not equipped.

Severity: Info.
SYS6693 x2
SNMP trap: No
x2 = %DTIM should be defined to have PRDL=DNIS.

Action:
Severity: Minor.
SYS8980
SNMP trap: No
Data block can only be loaded when STIE package is equipped.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2170 of 2360

SYS8981
ICP Package not equipped.

Action:
Severity: Critical.
SYS8982
SNMP trap: Yes
Attempt to write a protected bit field for a specific bit offset and bit width which
do not fit in a 16 bit word.
Action:
Severity: Critical.
SYS8983
SNMP trap: Yes
CLED package not equipped, data cleared.

Action:
Severity: Critical.
SYS8985
SNMP trap: Yes
SNMP trap: Yes
FFC code corruption.

Action:
Severity: Critical.
SYS8986
Flexible Feature Code is out of Protected Data (PDATA) storage.

Action:
Severity: Critical.
SYS8987
SNMP trap: Yes
FFC customer pointer is missing. The FFCs are not ready.

Action:
Severity: Critical.
SYS8988
SNMP trap: Yes
FFC package 139 is not equipped. FFCs have been removed.

Action:
Severity: Critical.
SNMP trap: Yes
SYS8989 mmmm ddd ppp Package not equipped, FFC will not be loaded. Where: mmmm =
mnemonic of FFC not loaded ddd = digits of FFC not loaded ppp = package
not equipped
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2171 of 2360

SYS8990
OPCB package not equipped, data cleared.

Action:
Severity: Critical.
SYS8991
SNMP trap: No
SUPP package not equipped, special service list data cleared.

Action:
Severity: Critical.
SYS8992
SNMP trap: Yes
MPO package is restricted but MPO data is found. MPO data is cleared.
Action:
Severity: Critical.
SYS8993
SNMP trap: No
DTI2 - DTI2 package not equipped, data cleared.

Action:
Severity: Critical.
SYS8994
SNMP trap: Yes
DTI2 - JDMI package not equipped, data cleared.

Action:
Severity: Critical.
SYS8995
SNMP trap: Yes
ART head table not found, data lost.

Action:
Severity: Critical.
SYS8996
SNMP trap: Yes
Unable to allocate protected data store for TBAR.

Action:
Severity: Critical.
SYS8997
SNMP trap: Yes
Duplicate Art # found, date lost.

Action:
Severity: Critical.
SNMP trap: No
System Messages
Page 2172 of 2360

SYS8998
ART # out-of-range, data lost.

Action:
Severity: Critical.
SYS8999
SNMP trap: Yes
TBAR package not equipped, data not loaded.

Action:
Severity: Critical.
SNMP trap: Yes
SYS9012 {cust} {table} {sequence} No protected memory available. DGCR data is lost.
Action:
Severity: Critical.
SYS9026
SNMP trap: Yes
DPNSS1 MWI: an NSI table cannot be restored.

Action: Redefine the MWI NSI table.
Severity: Major.
SYS9027
SNMP trap: Yes
Existing MFS data is removed because the CISMFS package is restricted.

Action:
Severity: Critical.
SYS9028
SNMP trap: Yes
System is not ESA packaged. ESA data has been discarded.

Severity: Info.
SYS9029
SNMP trap: Yes
ESA data is for an undefined customer. ESA data has been discarded.
Severity: Major.
SYS9030
SNMP trap: Yes
System is not ESA_CLMP packaged. ESA_APDN has been reset to YES.

Action: Contact your distributor if the system packaging is incorrect.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2173 of 2360

SYS9031
Invalid DFCL configuration is encountered in the ESA block.

Action:
Severity: Info.
SYS9032
SNMP trap: Yes
NI-2 CBC package not equipped. NI-2 CBC data lost.

Action: Install NI-2 CBC package.
Severity: Critical.
SYS9033
SNMP trap: No
Diversion remote capability is removed since the QSIG-SS package is

restricted.
Action: Enable the QSIG-SS package and Sysload the system again.
Severity: Critical.
SYS9034
SNMP trap: Yes
The RCAP MQC is removed because the MEET package is restricted.

Action:
Severity: Critical.
SYS9037
SNMP trap: Yes
Customer has configured a RAN route with data requesting the RAN
broadcast package but RAN broadcast package restricted. Broadcast
capability removed from route, ringback tone provided while waiting and new
RAN machine types changed.
Action: Enable RAN Broadcast package. DO NOT DATADUMP, system
information will be lost.
Severity: Major.
SYS9038
SNMP trap: Yes
Number of broadcasting routes exceeds ISM limit. Broadcast capability

removed from route.
Action: Customer must contact distributor to increase ISM limit. DO NOT
DATADUMP, system information will be lost.
Severity: Major.
SYS9039
SNMP trap: Yes
Number of broadcast RAN connections exceeds ISM limit.

Action: Customer must contact distributor to increase ISM limit. DO NOT
DATADUMP, system information will be lost.
Severity: Major.
SNMP trap: Yes
System Messages
Page 2174 of 2360

SYS9040
Customer has broadcasting music route configured but music Broadcast

package restricted.
Action: Enable music Broadcast package. DO NOT DATADUMP, system
information will be lost.
Severity: Major.
SYS9041
SNMP trap: Yes
TBAR Package is not equipped. FTOP in CDB reset to FRES.

Action:
Severity: Info.
SYS9063
SNMP trap: Yes
Invalid trunk type encountered in trunk TN block.

Action:
Severity: Critical.
SYS9070
SNMP trap: No
CPP//CPPO database defined for the route is discarded because CPP/CPPO

is not equipped.
Action:
Severity: Major.
SYS9073
SNMP trap: No
7SGF data cannot be loaded because the following packages are not present:
SS7(320) MMCS (317) QSIGGF (305) INBD (255)
Action:
Severity: Info.
SYS9106
SNMP trap: No
Data has been lost.

Action: Do not use data dump. Please contact the Switch Administrator.
Severity: Info.
SYS9107
SNMP trap: Yes
Data has been lost.

Action: Do not use data dump. Contact the Switch Administrator.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2175 of 2360

SYS9108
Data has been lost

Action: Please contact the Switch Administrator
Severity: Info.
SYS9115
SNMP trap: Yes
Unable to allocate protected memory for ANI block or ANI Table. Some ANI
Entries could be lost.
Action: User Overlay 21 to print the ANI Entries. Try to configure the
entries that are needed, or contact your technical support group.
Severity: Major.
SYS9116
SNMP trap: Yes
The PRA package is restricted in the System.

Action:
Severity: Minor.
SYS9117
SNMP trap: No
Taiwan R1 data in RDB but package is off. Data is lost.

Action: Equip TWR1 package and reload. Contact your technical support group.
Severity: Critical.
SYS9118
SNMP trap: Yes
Taiwan R1 data in the trunk data block but the package is off. Data is lost.
Action: Equip TWR1 package and reload. Contact your technical support group.
Severity: Critical.
SYS9123
SNMP trap: Yes
Unable to allocate memory for the access prefix block or access prefix table.
Action: A memory fault must be cleared or more memory must be equipped.
Severity: Critical.
SYS9124
SNMP trap: No
Access prefix data cannot be loaded as ISDN package #145 is restricted.

Action: Feature DAPC is part of the ISDN package #145.
Severity: Critical.
SYS9125
SNMP trap: No
The ACLI package is not equipped.

Action: Equip the ACLI package.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2176 of 2360

SYS9126
System is PRA package restricted. ICS data is discarded while sysloading.

Action:
Severity: Minor.
SYS9127
SNMP trap: No
System is DTI package restricted. ICS data is discarded while sysloading.

Action:
Severity: Info.
SYS9128
SNMP trap: No
Package #350 unrestricted with package #240 restricted.

Action:
Severity: Minor.
SYS9129
SNMP trap: Yes
Package #350 restricted with MWUN set to 32.

Action:
Severity: Minor.
SYS9130
SNMP trap: Yes
Incompatible units have been configured on the same line card.

Action:
Severity: Minor.
SYS9131
SNMP trap: Yes
FDID IDC tree block not loaded since FDID package (362) is not equipped.
Action: Equip package 362 and re-load.
Severity: Info.
SYS9132
SNMP trap: Yes
One or more of the following packages required for FDID (362) is missing:
NFCR (49), CCOS (81), BGD (99), RMS (100), IDC (113).
Action: Check the package dependencies for this feature, equip the necessary
packages, and reload.
Severity: Info.
SYS9134
SNMP trap: Yes
Unable to allocate memory for access prefix block or access prefix table.
Action: A memory fault must be cleared or more memory must be equipped.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2177 of 2360

SYS9135
Access prefix data cannot be loaded as the ISDN package #145 is restricted.
Action: The feature DAPC is part of the ISDN package #145.
Severity: Critical.
SYS9137
SNMP trap: Yes
The prompts related to the BSFE feature are set to default values as the BFS
Action:
Severity: Info.
SYS9138
SNMP trap: Yes
The number of wireless telephones exceeds the Wireless Telephones limit

and no further wireless telephones can be sysloaded.
Action:
Severity:
SYS9150
SNMP trap: Yes
Phantom TN superloops are moved to current loop +32 and Phantom TN

cards are moved to current card +20 (for Option 11C only).
Action:
Severity: Info.
SYS9160
SNMP trap: Yes
Both GRPRIM and GRSEC packages are equipped.

Action: The system restricts the GRPRIM package.
Severity: Info.
SYS9161
SNMP trap: Yes
Incorrect BKPR index (the system detected a backup rule having number
greater than 100).
Severity: Major.
SYS9162
SNMP trap: Yes
Memory allocation failed for BKPR block.

Severity: Major.
SNMP trap: Yes
System Messages
Page 2178 of 2360

SYS9163
GRDRC block read from tape, but both GRPRIM and

GRSEC packages are restricted.
The system removes the block.
Action:
Severity: Major.
SYS9164
SNMP trap: Yes
GRSC block read from tape, but both GRPRIM and GRSEC packages are
restricted.
The system removes the block.
Action:
Severity: Major.
SYS9280
SNMP trap: Yes
The pointers to the list of free memory were corrupted and have been reset.
No memory is available on this page. If this message is for page 0 and is not
followed by a BUG9281 then the system is out of memory.
Parameters: page (0 for unprotected, 1 for protected), page head and page
tail.
Action: If the page is 0 and BUG9281 is not printed perform a system
initialization as soon as possible, without logging in. If the problem is on page 1
and occurs repetitively the system
may run out of memory and a system reload will be required. Report the problem
to the operating company with the full text of the error message.
Severity: Critical.
SYS9281
SNMP trap: Yes
Unused unprotected memory was not properly tracked. It has been recovered.
Parameters: page (always 0), address and size of recovered block.
Action: The problem has been corrected. No action is required for a single
occurrence. If the error message occurs repetitively data corruption is likely report the problem to the operating company with the full text of the error
message.
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2179 of 2360

SYS9282
Unused protected memory was not properly tracked. The memory will remain
unavailable until the next system reload. Tracking is updated to reflect the
change.
Parameters: page (always 1), address and size of the unavailable block.
Action: Report the problem to the operating company with the full error printout.
If the problem persists the system may run out of memory and a system reload
should be performed. A system initialization is unlikely to improve the memory
condition.
Severity: Major.
SYS9283
SNMP trap: Yes
A block of memory that is marked unused has been corrupted. It is discarded

to avoid possible conflicts with a persistent misuse of the memory. The
memory will be unusable until the next system initialization or reload
(depending on the page).
Parameters: page and diagnostic information.
message. If the problem persists the system may run low on memory and an
initialization or reload may be required.
Severity: Major.
SYS9284
SNMP trap: Yes
Two memory blocks in the free memory list are detected with block sizes out
of order. The incorrect block is undetermined.
Recovery has been performed to avoid corruption, but may have caused a
loss of free memory. If memory was lost it will not
be recovered until the next system initialization or reload.
Parameters: page, first block address and size, second block address and
size, new size for first block.
Action: Report error to the operating company with the full text of the error
message.
Severity: Major.
SYS9285
SNMP trap: Yes
A pointer to a free memory list was corrupted and is corrected.

Parameters: page, corrupted address, corrupted value, expected value.
Action: The error has been recovered. If it occurs again report the full text of the
error message to the operating company.
Severity: Major.
SNMP trap: Yes
System Messages
Page 2180 of 2360

SYS9286
A data block was released that overlaps a block already free. The newly
released block is ignored to avoid duplicate
tracking of memory or possible corruption. This may cause a loss of available
memory in the system.
Parameters: page, start and end addresses of the released block, start and
end addresses of the free block.
error message.
Severity: Major.
SYS9290
SNMP trap: Yes
Available unprotected memory is below acceptable levels. A system

initialization may recover memory if blocks have become unavailable or
memory is heavily fragmented. If initialization does not eliminate the error, or
is not possible in the operating environment, remove some data from the
system to
free up more memory. This error will continue to be printed periodically until
the low memory condition is corrected.
Parameters: page (always 0), remaining memory
Action: Perform a system initialization as soon as possible. Do not attempt to
add data to the system until the this condition is corrected. Report the problem to
the operating company if initialization does not eliminate the problem and data
cannot be removed from the system.
Severity: Critical.
SYS9291
SNMP trap: Yes
Available protected memory is below acceptable levels. Service change

should not be attempted. If this error occurs only once it may indicate a
transient condition that has been corrected. If it occurs repeatedly a system
initialization to recover fragmented unprotected memory may free enough
memory to allow protected memory space to grow (16K required). If
initialization does not eliminate the low memory condition a system reload
may. If reload
does not help then the system is reaching it's capacity and some data may
need to be removed in order to allow other data to be created.
Parameters: page (always 1), memory available
Action: If the error occurs more than once (about 15 minutes apart) a system
initialization should be performed as soon as possible. Check the memory
available by loading a service change overlay. If memory is still low perform a
system reload. If memory remains low after a reload then remove data that is less
critical in order to create new data.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2181 of 2360
TDS: Tone and Digit Switch Diagnostic

(LD 34)
The Tone and Digit Switch and Digitone Receiver diagnostic program (LD 34)
tests packs used in generating and detecting tones in the system. Response
to commands for the Dial Tone Detector card are output as DTD messages.
Response to commands for the Tone and Digit Switch card are output as TDS
messages.
Messages
TDS0000
Program identifier indicating that the program has been loaded.

Action:
Severity: Info.
TDS0001 loop
SNMP trap: Yes
TDS loop has incorrect Digitone cycle. Outpulsing from that TDS may be
faulty, or 100 ms Digitone burst is being used in a system defined for a 50 ms
operation or vice versa.
Action:
Severity: Critical.
TDS0002 loop
SNMP trap: Yes
TDS loop is transmitting erroneous Digitone frequencies. Digitone outpulsing

from that TDS will be faulty. Minor lamp is lit on attendant console.
Action:
Severity: Critical.
TDS0003 loop
SNMP trap: Yes
20 pps outpulser on TDS loop L has bad timing or is not producing the correct
number of pulses per request. 20 pps outpulsing is faulty.
Action:
Severity: Critical.
TDS0004 loop
SNMP trap: Yes
10 pps outpulser on TDS loop has bad timing or is not producing the correct
number of pulses per request. 10 pps outpulsing is faulty.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2182 of 2360

TDS0005 loop
An outpulser on TDS loop did not complete a digit. 10 or 20 pps outpulsing is

faulty.
Action:
Severity: Critical.
TDS0006 loop
SNMP trap: Yes
All outpulsers on TDS loop have been disabled due to a system I/O interface
fault. Minor alarm lamp lit on attendant console.
Action:
Severity: Critical.
TDS0008 loop
SNMP trap: Yes
The Digitone pulse on TDS loop did not complete cycle. Digitone outpulsing is
faulty. Minor alarm lamp is lit on attendant console.
Action:
Severity: Critical.
TDS0010 loop
SNMP trap: Yes
Channel errors. Bad channels are disabled. Capacity of TDS is reduced.

Outpulsing and/or tone faults may occur.
Action:
Severity: Critical.
TDS0011 loop x
SNMP trap: Yes
The Tone Detector is unable to detect tone x generated by TDS loop L. Where
x =: 1 for Dial Tone 2 for Busy Tone 3 for Overflow Tone 4 for Ringback Tone
5 for Test Tone
Action:
Severity: Critical.
TDS0012
SNMP trap: Yes
Card is not a tone and digit switch.

Action:
Severity: Major.
TDS0013 loop
SNMP trap: Yes
TDS not allowed in that loop.

Action: Use LD 17 to change system configuration.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2183 of 2360

TDS0014 loop
Tone path could not be established to tone and digit loop.

Action: Check for disabled slots on pack (STAT L). If none disabled, try later
when traffic is reduced.
Severity: Critical.
TDS0015 loop
SNMP trap: Yes
TDS loop is not responding. Minor alarm lamp is lit on attendant console.
Action: Replace card. If fault persists, suspect: 1. other tone and digit switch 2.
Peripheral Signaling (PS)
Severity: Critical.
TDS0016
SNMP trap: Yes
SNMP trap: Yes
TDS is already enabled.

Action:
Severity: Info.
TDS0017
No TDS available for Digitone receiver testing.

Action:
Severity: Minor.
TDS0018 xx yy
SNMP trap: Yes
Bad timing on Fast TDS.

Action:
Severity: Critical.
TDS0019
SNMP trap: Yes
Outpulsing not completed on FAST TDS.

Action:
Severity: Critical.
TDS0020
SNMP trap: Yes
Digits sent do not match digits received or the number of digits entered for
TABL is incorrect.
Action:
Severity: Minor.
TDS0021
SNMP trap: Yes
Invalid unit used with DTR, ENLR or DISR command.

Action: Use even number unit only. Each Digitone Receiver uses TN pair.
Severity: Info.
SNMP trap: No
System Messages
Page 2184 of 2360

TDS0022
Requested loop is not defined in the system or is not the first VXCT loop in
IPM.
Action: Use first VXCT loop in IPMG and begin again
Severity: Minor.
TDS0032 loop
SNMP trap: Yes
SNMP trap: No
Card not responding.

Action:
Severity: Critical.
TDS0100 l s c
The specified Digitone receiver has been disabled due to lack of response or
faulty operation.
Action: Replace indicated card. Suspect faulty TDS if fault persists or if more
than one Digitone receiver is shown faulty. Minor alarm lamp lit on attendant
console.
Severity: Info.
TDS0102
SNMP trap: Yes
Digitone receiver requested is busy.

Severity: Critical.
TDS0103
SNMP trap: Yes
TN specified is not equipped to be a Digitone receiver.

Action: Check data.
Severity: Info.
TDS0104
SNMP trap: Yes
No Digitone Receiver found.

Action:
Severity: Critical.
TDS0105 l s c
SNMP trap: No
The specified Digitone Receiver has been disabled due to a failure to detect
A, B, C, D digits. Minor alarm lit on attendant console. Card is disabled only if
50 percent of system Digitone Receivers have not already been disabled. This
failure rate always leaves 50 percent of Digitone Receivers enabled.
Action: Suspect faulty TDS if fault persists or if more than one DTR is faulty.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2185 of 2360

TDS0120
The ANN command cannot be used.

Action:
Severity: Info.
TDS0121
SNMP trap: Yes
The source number is out-of-range (1-8).

Action:
Severity: Info.
TDS0124
SNMP trap: No
The specified XTD unit has failed to detect dial tone.

Action: Retest all units on the card using Overlay 34: DTD {loop} {shelf} {card}
{unit}. Disable any units which failed. If all units fail, replace the XTD card.
Severity: Major.
TDS0201
SNMP trap: Yes
The last request is not finished executing. Only END is allowed. The END will
terminate the execution.
Action: Wait until test execution has finished.
Severity: Info.
TDS0202
SNMP trap: Yes
Invalid parameter. Wrong number of parameters for this command.

Action:
Severity: Info.
TDS0203
SNMP trap: Yes
SNMP trap: Yes
Invalid command.
Action:
Severity: Info.
TDS0204
Loop is out-of-range. Loops 0 to 159 only are allowed.

Action:
Severity: Info.
TDS0205
SNMP trap: Yes
SNMP trap: Yes
Shelf is out-of-range.
Action:
Severity: Info.
System Messages
Page 2186 of 2360

TDS0206
Card is out-of-range.
Action:
Severity: Info.
TDS0207
SNMP trap: Yes
Unit is out-of-range (0 to 1).

Action:
Severity: Info.
TDS0208
SNMP trap: Yes
Command requested is allowed only from an SL-1 telephone. Tones or

outpulsing cannot interact with a TTY.
Action: Use SL-1 maintenance set telephone to enter command.
Severity: Info.
TDS0210
SNMP trap: Yes
Card does not exist in data base.

Action:
Severity: Info.
TDS0212
SNMP trap: Yes
Requested trunk type that uses the desired outpulser is not available.
Action: Be sure the system contains the desired trunks. If they exist, all trunks
in that category may be busy or unequipped.
Severity: Info.
SNMP trap: Yes
TDS0301 l s c (u) x y The specified tone detector has been disabled due to faulty operation or
lack of response, where x and y indicate the mode and test it has failed. The
rest of the testing is aborted.
X Y Mode
0004, 0001, Mode I Precise Tone
0004, 0003, Mode I Tone Duration is greater than 50 ms
0004, 0005, Mode I Tone Duration is greater than 300 ms
0004, 0005, Mode I Tone Duration is greater than 300 ms, Tone is turned off
at 256 ms
0005, 0001, Mode I Precise Busy Tone
0005, 0003, Mode I Non-Precise Busy Tone
0006, 0001, Mode I Precise Overflow Tone
0006, 0003, Mode I Non-Precise Overflow Tone
0006, 0005, Mode I Tone Duration is less than 300 ms
0007, 0001, Mode I Ringback Tone
553-3001-411
Standard 15.00
January 2006
Page 2187 of 2360

0007, 0003, Mode I Any Tone
0008, 0001, Mode I Special Common Carrier Dial Tone
0009, 0001, Mode I Unidentified Tone
0009, 0003, Mode II Unidentified Tone
0009, 0005, Mode IV Test Tone
0009, 0007, Mode III Test Tone
0009, 0009, Mode III Test Tone (Tone is turned off at 5.5 s)
000A, 0001, Mode V Single Frequency Tone
000A, 0003, Mode V Dual Frequency Tone
Action:
Severity: Critical.
TDS0302 l s c (u)
SNMP trap: Yes
The specified tone detector has been disabled; unable to perform self-test.
Action:
Severity: Critical.
TDS0303 l s c (u)
SNMP trap: Yes
Terminal number specified is not designated as a tone detector.

Action:
Severity: Critical.
TDS0304
SNMP trap: Yes
No TDS is available for tone detector testing.

Action:
Severity: Critical.
TDS0310
SNMP trap: Yes
Tone detector (TDET) package is restricted.

Action:
Severity: Critical.
TDS0311 l s c (u)
SNMP trap: Yes
Specified TN is not an MFR.

Action:
Severity: Critical.
TDS0312
SNMP trap: Yes
No MFR units are configured.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2188 of 2360

TDS0313
Some units of MFR card are busy, test not done.

Action:
Severity: Critical.
TDS0314
SNMP trap: No
No MFS available for MFR test.

Action:
Severity: Critical.
TDS0315 l s c u
SNMP trap: Yes
MFR unit is busy. Test not performed.

Action:
Severity: Critical.
TDS0316
SNMP trap: Yes
MFR is disabled due to faulty operation.

Action:
Severity: Critical.
TDS0317
SNMP trap: No
Digitone Receiver's (NT8D16) Peripheral Controller (NT8D01) is disabled,

nothing is performed.
Action: Use LD 32 to enable Peripheral Controller.
Severity: Critical.
TDS0318
SNMP trap: Yes

Action:
Severity: Critical.
TDS0319
SNMP trap: Yes
Digitone Receiver (NT8D16) failed self test.

Action: Replace the Digitone Receiver.
Severity: Critical.
TDS0320
SNMP trap: Yes
Digitone Receiver (NT8D16) does not respond.

Action: Check Digitone Receiver and the Network Card/Peripheral Controller
(NT8D04/NT8D01) communication path to the card for a fault.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2189 of 2360

TDS0400
FTC Table 0 used for tone tests.

Action:
Severity: Critical.
TDS0411
SNMP trap: Yes
Dialtone Detector package is not equipped.

Action:
Severity: Critical.
TDS0412
SNMP trap: Yes
Dialtone Detector and Tone Detector packages are not equipped.

Action:
Severity: Critical.
TDS0500
SNMP trap: Yes
ANN command cannot be used because the Message Intercept (MINT)

package 163 is not equipped.
Action:
Severity: Critical.
TDS0501
SNMP trap: Yes
Source number out-of-range. Only 8 external sources (1 to 8) can be defined

for testing.
Action:
Severity: Critical.
TDS0502
SNMP trap: Yes
ENLX (Enable) or DISX (Disable) commands are only used on

Conference/TDS/MFS cards.
Action:
Severity: Critical.
TDS0503
SNMP trap: Yes
The Conference/TDS/MFS card is already enabled/disabled.

Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2190 of 2360

TDS0504
Received an unexpected message from the Conference/TDS/MFS card.

Action: Use the DISX command to disable the card and retry the ENLX
command to enable the card.
Severity: Critical.
TDS0505
SNMP trap: Yes
The Enable command (ENLX) did not receive the down-load complete
message within 6 seconds.
Action:
Severity: Critical.
TDS0506
SNMP trap: Yes
Tone or cadence number is out-of-range.

Action:
Severity: Critical.
TDS0507
SNMP trap: Yes
The TLP Supplementary package is not equipped.

Action:
Severity: Critical.
TDS0508
SNMP trap: Yes
The SSD scanning message received no response from the DTR/XDTR.

Action: The faulty DTR is disabled.
Severity: Critical.
TDS0511 l s c u x
SNMP trap: Yes
DTR/XDTR fails to respond to SSD scanning message for "x" times prior to the
DTMF tone detection test.
Action:
Severity: Critical.
SNMP trap: Yes
TDS0512 l s c u x d DTR/XDTR fails to detect the "d" digit for "x" times prior to the DTMF tone
detection test is testing.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2191 of 2360

TDS0513 l s c u x
DTR/XDTR fails to detect all the digits for "x" times when the DTMF tone
detection test with the fast TDS is testing.
Action:
Severity: Critical.
TDS0514 l s c u x
SNMP trap: Yes
DTR/XDTR fails to pass the digit through for "x" times when continuity test is
testing.
Action:
Severity: Critical.
TDS0827
SNMP trap: Yes
Multiple SSD messages of the same DTMF digit are received from the same
NT8D16 Digitone Receiver during a DTR or TDS test in LD 34.
Action: If this problem occurs every time, replace the card.
Severity: Critical.
TDS0828 loop
SNMP trap: Yes
Attempting to enable Conference/TDS card during midnight routines.

Action:
Severity: Critical.
TDS0829
SNMP trap: No
A command with the same functionality is supported in Overlay 32.

Action:
Severity: Info.
TDS0830 l s c
SNMP trap: No
A designated DTR pack has failed the continuity test.

Action: This test result could be faulty. Use Overlay 34 to disable/enable the
pack.
If the pack cannot be enabled, replace the pack. Otherwise ignore the message.
Severity: Minor.
TDS0832
SNMP trap: Yes
This command is not available for specified IPMG DTR devices

Severity: Info.
SNMP trap: Yes
System Messages
Page 2192 of 2360

TDS0834
This command is not available for specified VXCT device.

Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2193 of 2360
TEMU: Tape Emulation

Messages
TEMU0001
Failure during initialization of tape emulation.

Action:
Severity: Minor.
TEMU0002
SNMP trap: Yes
Errno 0x%x: Failure giving command semaphore.

Action:
Severity: Minor.
TEMU0003
SNMP trap: Yes
x Invalid command sent to tape emulation.

Action:
Severity: Minor.
TEMU0004
SNMP trap: Yes
Errno 0x%x: Semaphone creation failed

Action:
Severity: Minor.
TEMU0005
SNMP trap: Yes
Errno 0x%x: Take task init failed

Action:
Severity: Minor.
TEMU0006
SNMP trap: No
Errno 0x%x: Tape task activation failed

Action:
Severity: Minor.
TEMU0007
SNMP trap: No
Failure creating tape emulation task.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2194 of 2360

TEMU0008
Errno 0x%x: Failure taking command semaphore.

Action:
Severity: Minor.
TEMU0009
SNMP trap: Yes
x Unknown command sent to tape task.

Action:
Severity: Minor.
TEMU0010
SNMP trap: Yes
Error occurred writing HI database.

Action:
Severity: Minor.
TEMU0011
SNMP trap: Yes
Error occurred backing up database.

Action: Ensure that the Floppy Diskette is properly inserted.
Severity: Minor.
TEMU0012
SNMP trap: Yes
Error occurred restoring database.

Action: Ensure that the Floppy Diskette is properly inserted.
Severity: Minor.
TEMU0013
SNMP trap: Yes
Error occurred swapping primary/secondary databases.

Action:
Severity: Minor.
TEMU0014
SNMP trap: Yes
TEMU task timeout, where: cmd= x, data= y, stat= z.

Action:
Severity: Minor.
TEMU0015
SNMP trap: Yes
IO Error: %s file is corrupted, IP configuration failed.

Action: Reboot the system and commence the IP configuration.
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2195 of 2360

TEMU0016
Failure: retrieve the file x from the main cabinet.

Severity: Minor.
TEMU0020
SNMP trap: Yes
Errno 0x%x: Failure opening file %s

Action:
Severity: Minor.
TEMU0021
SNMP trap: Yes
Errno 0x%x: Failure obtaining size of file %s

Action:
Severity: Minor.
TEMU0022
SNMP trap: Yes
Errno 0x%x: Failure renaming file %s to %s

Action:
Severity: Minor.
TEMU0023
SNMP trap: Yes
Errno 0x%x: WARNING - failure opening file %s

Action:
Severity: Minor.
TEMU0028
SNMP trap: Yes
Failure opening database files for reading.

Action:
Severity: Minor.
TEMU0029
SNMP trap: Yes
Failure closing database files after reading.

Action:
Severity: Minor.
TEMU0030
SNMP trap: Yes
Errno 0x%x: Failure opening file %s for writing

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2196 of 2360

TEMU0032
Failure opening database files for writing.

Action:
Severity: Minor.
TEMU0037
SNMP trap: Yes
Failure closing database files after writing.

Action:
Severity: Minor.
TEMU0038 x y
SNMP trap: Yes
Error skipping x records.

Action:
Severity: Minor.
TEMU0040
SNMP trap: Yes
Invalid read in write sequence.

Action:
Severity: Minor.
TEMU0041
SNMP trap: Yes
Failure reading record from x file.

Action:
Severity: Minor.
TEMU0042
SNMP trap: Yes
Errno 0x%x: Failure reading from %s file during Query

Action:
Severity: Minor.
TEMU0043
SNMP trap: Yes
Errno 0x%x: Failure reading from fd %d

Action:
Severity: Minor.
TEMU0044
SNMP trap: Yes
Errno 0x%x: Failure writing to fd %d

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2197 of 2360

TEMU0045
Errno 0x%x: Failure seeking to %d for %s in file

Action:
Severity: Minor.
TEMU0046 x y
SNMP trap: Yes
Errno 0x%x: Failure at %d %s in file

Action:
Severity: Minor.
TEMU0047
SNMP trap: Yes
Attempt to write x record.

Action:
Severity: Minor.
TEMU0048
SNMP trap: Yes
Database disk volume is full.

Action:
Severity: Minor.
TEMU0049
SNMP trap: Yes
Warning: record no mismatch, curr=x, rec=y.

Action:
Severity: Minor.
TEMU0050
SNMP trap: Yes
Begin write not at 1st data rec, curr=x, rec=y.

Action:
Severity: Minor.
TEMU0051
SNMP trap: Yes
Failure writing record to x file.

Action:
Severity: Minor.
TEMU0053
SNMP trap: Yes
Attempt to write unknown record type x.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2198 of 2360

TEMU0056
DB x request illegal during write sequence.

Action:
Severity: Minor.
TEMU0059
SNMP trap: Yes
Errno 0x%x: WARNING - failure closing %sfile

Action:
Severity: Minor.
TEMU0061
SNMP trap: Yes
Failure copying dir x contents to y.

Action:
Severity: Minor.
TEMU0062
SNMP trap: Yes
Database x removable media failed.

Action:
Severity: Minor.
TEMU0071
SNMP trap: Yes
Failure during database query.

Action:
Severity: Minor.
TEMU0072
SNMP trap: Yes
Errno 0x%x: Failure moving dir %s contents to %s

Action:
Severity: Minor.
TEMU0073
SNMP trap: Yes
Failure swapping primary database with secondary.

Action:
Severity: Minor.
TEMU0074
SNMP trap: Yes
Errno 0x%x: Failure copying %s file to %s file.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2199 of 2360

TEMU0075
Errno 0x%x: Failure %s dir %s for copy.

Action:
Severity: Minor.
TEMU0076
SNMP trap: Yes
Copy source dir x is empty.

Action:
Severity: Minor.
TEMU0077
SNMP trap: Yes
Failure copying dir file x to y.

Action:
Severity: Minor.
TEMU0079
SNMP trap: Yes
Errno 0x%x: Failure to %s diskette vol during formatting.

Action:
Severity: Minor.
TEMU0080
SNMP trap: Yes
Errno 0x%x: No diskette in active CMDU drive %s

Action:
Severity: Minor.
TEMU0081
SNMP trap: Yes
Errno 0x%x: Failure formatting diskette in active CMDU drive %s

Action:
Severity: Minor.
TEMU0082
SNMP trap: Yes
Errno 0x%x: Open failure for hi dir %s on active CMDU diskette.

Action:
Severity: Minor.
TEMU0083
SNMP trap: Yes
Diskette on active CMDU drive x is write protected.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2200 of 2360

TEMU0084
Errno 0x%x: Failure %s dir %s for rename

Action:
Severity: Info.
TEMU0085
SNMP trap: No
x Failure y dir z for rename.

Action:
Severity: Minor.
TEMU0086
SNMP trap: Yes
Rename source dir x is empty.

Action:
Severity: Minor.
TEMU0087
SNMP trap: Yes
x Failure renaming dir file y to z.

Action:
Severity: Minor.
TEMU0088
SNMP trap: Yes
Warning: x file was not preallocated on disk.

Action:
Severity: Minor.
TEMU0100
SNMP trap: Yes
Failure obtaining file/dir name "x" from DLO.

Action:
Severity: Minor.
TEMU0101
SNMP trap: Yes
The version of the language database is higher than the S/W current issue.
The configuration is defaulted to none.
Action: Reconfigure the data and do a data dump.
Severity: Minor.
TEMU0102
SNMP trap: Yes
The language database's issue number could not be retrieved. The

configuration is defaulted to none.
Action: Reconfigure the data and do a data dump.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2201 of 2360

TEMU0103
The complete filename is too long.

Action:
Severity: Minor.
TEMU0104
SNMP trap: Yes
The language data could not be written to the disk. Refer to previous
messages to determine what caused the situation.
Action: Restart the data dump after clearing the originating problems.
Severity: Minor.
TEMU0105
SNMP trap: Yes
Errno 0x%x: Failure to open/create dir %s on PC Card

Action: Check whether the PC Card card is inserted. Contact your technical
support group if the problem persists.
Severity: Info.
TEMU0106
SNMP trap: Yes
Unable to get PSDL files from the system.

Action: Depends on the feature set. Some systems do not require the presence
of the PSDL file.
Severity: Info.
TEMU0107
SNMP trap: Yes
PSDL file cannot be opened or does not exist in the system.

Action: Depends on the feature set. Some systems do not require the presence
of the PSDL file.
Severity: Info.
TEMU0108
SNMP trap: Yes
Config/Database file cannot be found in the system.

Severity: Critical.
TEMU0109
SNMP trap: Yes
Unable to get config/database file path.

Action: Contact your technical support group. Check for the existence of the
disk.sys file in the system.
Severity: Major.
SNMP trap: Yes
System Messages
Page 2202 of 2360

TEMU0110
Error occurred while restoring internal database.

Action: Some files may be not restored or re-named properly. Contact your
Severity: Minor.
TEMU0111
SNMP trap: Yes
Error occurred while backing up internal database.

Action: Might lose the internal backup capacity. Contact your technical support
group.
Severity: Major.
TEMU0112
SNMP trap: Yes
Error occurred while backing up external database.

Action: Check that PC Card data drive is properly inserted. Some files might not
be backed up. Contact your technical support group.
Severity: Minor.
TEMU0113
SNMP trap: Yes
Error occurred restoring external database.

Action: Check that PC Card data drive is properly inserted. Contact your
Severity: Info.
TEMU0114
SNMP trap: Yes
Restore from internal backup drive failed.

Action: Try again. If the problem persists contact NT support.
Severity: Info.
TEMU0115
SNMP trap: Yes
zdrv: Drive full, file %s not backed up, where s is the file name.
Severity: Major.
TEMU0116
SNMP trap: Yes
zdr: Error back up file %s, where s is the file name.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2203 of 2360

TEMU0117
zdrv: Error creating internal backups, retrying. Some files might not be backed
up.
Severity: Major.
TEMU0118
SNMP trap: Yes
zdr: Unable to create internal backups.

Severity: Major.
TEMU0120
SNMP trap: Yes
zdr: Failed to install zdrv driver.

Severity: Major.
TEMU0121
SNMP trap: Yes
zdr: Drive ID %X%X differs from system ID

Severity: Info.
TEMU0122
SNMP trap: Yes
zdrv: x and y have differing time stamps.

Action: The database cannot be restored from the SSC to the software
daughterboard using RIB because a database already exists on the software
daughterboard. Use the Software Installation Program Utilities menu to restore
the database.
Severity: Info.
TEMU0123
SNMP trap: Yes
zdrv: Restoring s, where s is the file name.

Action:
Severity: Info.
TEMU0124
SNMP trap: Yes
zdrv: Failed to restore s, where s is the file name.

Severity: Info.
SNMP trap: Yes
System Messages
Page 2204 of 2360

TEMU0146
Errno 0x%x: Error reading from file %s

Action:
Severity: Info.
TEMU0147
SNMP trap: Yes
Errno 0x%x: Can't get file info for file %s

Action:
Severity: Info.
TEMU0148
SNMP trap: Yes
Errno 0x%x: Can't open directory %s

Action:
Severity: Info.
TEMU0151
SNMP trap: Yes
Errno 0x%x: Error Compression file %s

Action:
Severity: Info.
TEMU0152
SNMP trap: Yes
Errno 0x%x: Compression error: %s %s

Action:
Severity: Info.
TEMU0154
SNMP trap: Yes
Errno 0x%x: UnCompression file error: %s %s

Action:
Severity: Info.
TEMU0171 xx
SNMP trap: Yes
Failure giving command semaphore on Expansion Cabinet xx.

Action:
Severity: Major.
TEMU0172 xx
SNMP trap: Yes
Failure getting command from main cabinet on expansion cabinet xx.

Action:
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2205 of 2360

TEMU0173 xx
Failure receiving a message from tape task on expansion cabinet xx.

Action:
Severity: Major.
TEMU0174
SNMP trap: Yes
Message queue creation failed.

Action:
Severity: Critical.
TEMU0175 xx
SNMP trap: Yes
Failure obtaining file/dir name xx from DLO.

Action:
Severity: Major.
TEMU0176 xx yy
SNMP trap: Yes
Failure transferring the file xx to expansion cabinet yy.

Action:
Severity: Critical.
TEMU0177 xx
SNMP trap: Yes
Failure sending command on expansion cabinet xx.

Action:
Severity: Info.
TEMU0178 xx
SNMP trap: Yes
Failure connecting to expansion cabinet xx.

Action:
Severity: Info.
TEMU0179 xx
SNMP trap: Yes
Failure getting reply from expansion cabinet xx.

Action:
Severity: Info.
TEMU0180 xx
SNMP trap: Yes
Timeout waiting reply from expansion cabinet xx.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 2206 of 2360

TEMU0181 xx
Cannot determine address of expansion cabinet xx.

Action:
Severity: Critical.
TEMU0182
SNMP trap: Yes
Software Release not compatible on expansion cabinet xx.

Action:
Severity: Minor.
TEMU0184
SNMP trap: Yes
Database synchronization failed on cab xx. Tape Task status is yy.

Action:
Severity: Minor.
TEMU0185
SNMP trap: Yes
Failure obtaining file/dir name form DLO on cabin xx.

Action:
Severity: Major.
TEMU0186
SNMP trap: Yes
Failure renaming file on cabinet xx.

Action:
Severity: Major.
TEMU0187
SNMP trap: Yes
Unsupported command on cab xx.

Action:
Severity: Info.
TEMU0190
SNMP trap: Yes
Backup data set version does not exist.

The data version provided in the command entered, does not exist.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2207 of 2360

TEMU0191
"<mode> Backup according to rule <n> failed.

Where n - the number of the backup rule that was used, and mode of the
Backup may be "Automatic", "GR Manual" or "Manual"
Action: See previously issued SRPT andTEMUreports to clarify the actual
reason of the failure.
Verify hard disk accessibility / FTP connection.
Severity: Major.
TEMU0192
SNMP trap: Yes
"<mode> Data Restore according to rule <n> failed."

Restore may be "Automatic", "GR Manual" or "Manual"
Action: See previously issued SRPT andTEMUreports to clarify the actual
reason of the failure.
Verify hard disk accessibility / Primary CS - Secondary CS SW version match
Severity: Major.
TEMU0193
SNMP trap: Yes
"<mode> Backup according to rule <n> ended successfully."

Backup may be "Automatic", "GR Manual" or "Manual"
Action:
Severity: Info.
TEMU0194
SNMP trap: Yes
<mode> Data Restore according to rule <n> ended successfully."

Restore may be "Automatic", "GR Manual" or "Manual"
Action:
Severity: Info.
TEMU0195
SNMP trap: Yes
"Create directory <dir path> failed; errno=0xXXXX"

Attempt to create directory on the hard disk failed
Action: Verify hard disk accessibility
Severity: Major.
TEMU0196
SNMP trap: Yes
"Erase directory <dir path> failed; errno=0xXXXX."

Attempt to erase directory on the hard disk failed
Severity: Major.
SNMP trap: Yes
System Messages
Page 2208 of 2360

TEMU0197
"Create file <file path> failed; errno=0xXXXX"

Attempt to create a file on the hard disk failed
Severity: Major.
TEMU0198
SNMP trap: Yes
"Write %d bytes to file '%s' failed=%d; errno=0x%x."

Attempt to write to a file on the hard disk failed
Severity: Major.
TEMU0199
SNMP trap: Yes
"Read %d bytes from file '%s' failed=%d; errno=0x%x."

Attempt to read from a file on the hard disk failed
Severity: Major.
TEMU0200
SNMP trap: Yes
"Archive to '%s' failed; errno=0x%x."

Attempt to archive to the hard disk failed
Severity: Major.
TEMU0201
SNMP trap: Yes
"Restore from '%s' failed; errno=0x%x."

Attempt to restore from the hard disk failed
Severity: Major.
TEMU0202
SNMP trap: Yes
"TAR Archive '%s' failed; errno=0x%x."

Attempt to tar the specified directory on the hard disk failed
Severity: Major.
TEMU0203
SNMP trap: Yes
"TAR Extract '%s' failed; errno=0x%x."

Attempt to untar the specified archive on the hard disk failed
Severity: Major.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2209 of 2360

TEMU0204
"GZIP Compress '%s' failed; errno=0x%x."

Attempt to compress (by means of GZIP) the specified file failed
Severity: Major.
TEMU0205
SNMP trap: Yes
"GZIP Uncompress '%s' failed; errno=0x%x."

Attempt to uncompress (by means of GZIP) the specified file failed
Severity: Major.
SNMP trap: Yes
System Messages
Page 2210 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2211 of 2360
TFC: Traffic Control (LD 2)

Messages
TFC0000
Program identifier
Action:
Severity: Info.
TFC0001
SNMP trap: No
QoS packet loss: [value of exceeded threshold], [source IP + port number],

[source TN], [source zone], [destination IP], [destination TN], [destination
zone]. [DSP Channel]
Action: IP Voice quality degradation has been detected, please check your IP
network or contact you technical support group.
Severity: Warning.
TFC0002
SNMP trap: No
QoS latency: [value of exceeded threshold], [source IP + port number], [source

TN], [source zone], [destination IP], [destination TN], [destination zone] [DSP
Channel]
Severity: Warning.
TFC0003
SNMP trap: No
QoS jitter: [value of exceeded threshold], [source IP + port number], [source

TN], [source zone], [destination IP], [destination TN], [destination zone] [DSP
Channel]
Severity: Warning.
TFC0004
SNMP trap: No
QoS Report gathering temporary disable [ End Point: source IP + port number
/ Server: IP Address / All].
Severity: Minor.
SNMP trap: No
System Messages
Page 2212 of 2360

TFC0200
Syntax error. Illegal character has been input.

Action:
Severity: Info.
TFC0201
SNMP trap: No
The parameter specified is out-of-range.

Action:
Severity: Info.
TFC0202
SNMP trap: No
The loop specified is not equipped.

Action:
Severity: Info.
TFC0203
SNMP trap: No
The card specified is either not equipped, or is of a different density.

Action: Check the PBX card. Ensure that the correct density has been
configured.
Severity: Info.
TFC0204
SNMP trap: Yes
The unit specified is not equipped.

Action:
Severity: Info.
TFC0205
SNMP trap: No
Program bug - should never happen.

Action:
Severity: Info.
TFC0206
SNMP trap: No
Customer specified is not equipped.

Action:
Severity: Info.
TFC0207
SNMP trap: No
Traffic Print program is busy with scheduled output.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2213 of 2360

TFC0208
Traffic Control program cannot be invoked from a maintenance set.

Action:
Severity: Info.
TFC0209
SNMP trap: No
The Network Traffic (NTRF) feature is not equipped.

Action:
Severity: Info.
TFC0210
SNMP trap: No
There is no ESN customer data block.

Action:
Severity: Info.
TFC0212
SNMP trap: No
The NCOS data block does not exist in the system.

Action:
Severity: Info.
TFC0213
SNMP trap: No
IMS or Command and Status Link (CSL) package not equipped.

Action:
Severity: Info.
TFC0214
SNMP trap: No
Channel specified is not equipped.

Action:
Severity: Info.
TFC0215
SNMP trap: No
Invalid input for Digital Trunk Interface (DTI) loop.

Action:
Severity: Info.
TFC0216
SNMP trap: No
Command and Status Link (CSL) package not equipped.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2214 of 2360

TFC0220
System cannot allocate space for Line Load Control (LLC) data block.
Action:
Severity: Info.
TFC0221
SNMP trap: No
Invalid command: Line Load Control (LLC) is not enabled.

Action:
Severity: Info.
TFC0222
SNMP trap: No
Invalid command: AUTOVON is not enabled.

Action:
Severity: Info.
TFC0223
SNMP trap: No
The ISA package is not equipped.

Action:
Severity: Info.
TFC0400
SNMP trap: No
The user does not have access to system commands.

Action:
Severity: Info.
TFC0401
SNMP trap: No
The user does not have access to this customer.

Action:
Severity: Info.
TFC0402
SNMP trap: No
The user does not have access to Line Load Control commands.
Action:
Severity: Info.
TFC0403
SNMP trap: No
NAS package is not equipped.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2215 of 2360

TFC0404
ISDN INTL SUP package (30B+D) is not equipped.

Action:
Severity: Info.
TFC0405
SNMP trap: No
SNMP trap: No
Invalid DN entered.
Action:
Severity: Info.
TFC0406
The time synchronization DN has to be set for the new customer.

Action:
Severity: Info.
TFC0408
SNMP trap: No
No BRI package equipped.

Action:
Severity: Info.
TFC0409
SNMP trap: No
Failed to request information from the MISP.

Action:
Severity: Info.
TFC0410
SNMP trap: No
Calculation for the next Daylight Savings Time and Standard Time change
cannot be done, because the system clock is not set.
Action: Set the system clock in LD 2.
Severity: Info.
SNMP trap: No
TFC0411 FWTM AT {time} {date} The system clock has been changed forward one hour for
Daylight Savings Time change.
Action:
Severity: Info.
SNMP trap: No
TFC0412 BWTM AT {time} {date} The system clock has been changed backward one hour for
Standard Time change.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2216 of 2360

TFC0413
FWTM and BWTM setting cannot be identical.

Action:
Severity: Info.
TFC0414
SNMP trap: No
The Meridian 1 Packet Handler package is not configured. You cannot

schedule TFS015 if this package is not equipped.
Action:
Severity: Info.
TFC0415
SNMP trap: No
Failed to request BRSC traffic information from MISP. MISP loop number and
BRSC TN are printed.
Action: Check MISP and BRSC states.
Severity: Info.
TFC0416
SNMP trap: No
Use TCFT/SCFT commands (OV 2) to find out/change what customer you are
collecting features for. Currently, it is not the same customer you have just
entered in the INVC command. If no previous SCFT, default is customer 0.
Action:
Severity: Info.
TFC0419
SNMP trap: No
A conference loop was overflowing. There may not be enough available slots
on the loop.
Action:
Severity: Info.
TFC0420
SNMP trap: No
ISDN Semi Permanent Connection (ISPC) package is not equipped. In

Overlay 2, a request to set/clear Customer Traffic Report for ISPC links
establishment (type=10) has been done using SOPC or COPC command but
the ISPC package is not enabled.
Action: Select a different report type or Unrestrict the ISPC package and reload
PBX if necessary.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2217 of 2360

TFC0421
ISDN Semi Permanent package is not equipped. In Overlay 2, a request to

set/clear the Customer Traffic Report for ISPC links established (type=10) was
attempted using the SOPC or COPC command.
Action: Select a different report type, or Unrestrict the ISPC package and reload
the PBX if necessary.
Severity: Minor.
SNMP trap: No
System Messages
Page 2218 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2219 of 2360
TFN: Customer Network Traffic

Messages
TFN0401
Routing control has been invoked from an attendant console; the time (hh mm
ss) and termination number (TN) of the console are included in the
message.Info01/27/95 00/00/00
Action:
Severity: Info.
TFN0402
SNMP trap: No
Routing control has been deactivated from an attendant console; the time and
TN of the console are included in the message. Info 00/00/00 00/00/00
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2220 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2221 of 2360
TFS: Traffic Measurement

Messages
TFS0000
Indicates the commencement of a traffic study printout.

Action:
Severity: Info.
TFS0001
SNMP trap: No
A broadcast call between junctures was blocked.

Action: Spread the broadcast routes across the groups. If the problem still
Severity: Minor.
TFS0002
SNMP trap: No
No free port was found at the required moment to play an agent's greeting.
Action: If this TFS message is generated regularly, it is recommended that you
increase FXS port capacity.
Severity: Major.
TFS0003
SNMP trap: No
Lack of conference resources on the system for current call, so that agents
greeting cannot be played.
Action:
Severity: Major.
TFS0004
SNMP trap: No
An attempt was made to answer a set

Action:
Severity: Info.
TFS0301
SNMP trap: No
SNMP trap: No
First since initialization.

Action:
Severity: Info.
System Messages
Page 2222 of 2360

TFS0302
Traffic schedule for system or customer has been changed.

Action:
Severity: Info.
TFS0303
SNMP trap: No
There has been more than one hour since the last traffic output.
Action:
Severity: Info.
TFS0401
SNMP trap: No
A connection was held for greater than or equal to 36 ccs, but less than 50 ccs.
Usage and peg count are still accumulated.
Action:
Severity: Minor.
TFS0402
SNMP trap: No
A connection was held for greater than 50 ccs. Usage and peg count are not
accumulated. However, if either TFCE options are enabled, usage and peg
count are accumulated if TFS403 messages do not appear.
Action:
Severity: Minor.
TFS0403
SNMP trap: No
A trunk was held for greater than or equal to 50 ccs without having its traffic
accumulated while one or both of the Trunk Traffic Reporting Enhancements
options are enabled.
Note that if the TFS403 message appears at the end of a traffic period and the
"traffic period option" is enabled, then only the usage is not accumulated. If the
TFS403 message appears at disconnect time, then both usage and peg count
are not accumulated.
Action:
Severity: Minor.
TFS0411
SNMP trap: No
Large ccs if TFS401/402 cannot be printed immediately.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2223 of 2360

TFS0412 calls ccs Traffic totals: number of calls and total ccs.
Action:
Severity: Info.
TFS0500 tn 1 to 2
SNMP trap: No
A unit tn2 could not enter conference tn1; no slots available.
Action:
Severity: Minor.
TFS0501 loop
SNMP trap: No
Audit (LD 44) found time slot x on a loop incorrectly identified as busy. The
time slots have been idled. Since these time slots were not used by the
system, they represented higher blocking probability. This will affect traffic
analysis.
Action:
Severity: Minor.
TFS0502 j x
SNMP trap: Yes
Audit (LD 44) found time slot x on juncture j incorrectly identified as busy. The
time slots have been idled. Since these time slots were not used by the
system, they represented higher blocking probability. This will affect traffic
analysis.
Action:
Severity: Minor.
TFS0503 {TN}
SNMP trap: Yes
Music connection could not be connected since the ISM limit has been
reached.
Action: If the condition persists then increase the ISM limit for Music Broadcast.
Severity: Info.
TFS0999
SNMP trap: Yes
Indicates the completion of a traffic study printout.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2224 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2225 of 2360
TMDI: T1 Multi Purpose Digital Interface

Messages
TMDI0100 x
The CSTAT and CSUBSTAT fields on TMDI x indicate the card is Manually
the
System Disabled - Self- tests Passed state, and within the next few minutes,
the
Meridian 1 will attempt to enable the card.
Action:
Severity: Info.
TMDI0101 x
SNMP trap: No
The CSTAT field on TMDI x indicates the card is no longer Enabled. The
Meridian
1 will attempt to return the card to an Enabled state within a few minutes.
Under
certain conditions, this message is output at the same time as TMDI302.
Action:
Severity: Info.
TMDI0102 x
SNMP trap: No
No response was received from TMDI x to a background polling message sent

periodically to each TMDI card. The purpose of this message is to ensure that
the
card is capable of receiving and sending messages.
Action:
Severity: Info.
TMDI0103 x
SNMP trap: Yes
An Overlay was waiting for a message from TMDI x. Most likely, the Overlay
is no
longer loaded. The message the Overlay was waiting for was never received.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2226 of 2360

TMDI0104 x
The TMDI background audit sent a message to TMDI x, and did not receive a
response.
Action:
Severity: Info.
TMDI0106 x appl
SNMP trap: No
The TMDI audit detected that there was no response to a maintenance

message originated by an application (appl) on TMDI x.
Action:
Severity: Info.
SNMP trap: No
TMDI0107 x appl y The Meridian 1 was unable to determine if downloading was necessary. An
for
the failure. Three fields accompany this message: x = device number (LD 17
DNUM), appl = the application name, and y is for design use only.
Action:
Severity: Info.
TMDI0108 x appl
SNMP trap: No
An application on TMDI x needs to be downloaded to the card. Downloading

begins as soon as there is no Overlay loaded. Where: x = device number (LD
17
DNUM) and appl = the application name.
Action:
Severity: Info.
TMDI0112 x
SNMP trap: No
TMDI x has been reset in order to begin automatic recovery. Immediately

finished,
provided they pass, the Meridian 1 will attempt to enable the card. Where: x =
device number (LD 17 DNUM).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2227 of 2360

TMDI0201 x appl
TMDI x sent a message to the Meridian 1 indicating an application data space

has been corrupted. Where: x = device number (LD 17 DNUM) and appl = the
application name.
Action:
Severity: Info.
TMDI0202 x appl
SNMP trap: No
TMDI x sent a message to the Meridian 1 indicating that an application on the

card unexpectedly disabled itself (performed a close). Where: x = device
number (LD 17 DNUM) and appl = the application name.
Action:
Severity: Info.
TMDI0204 x appl
SNMP trap: No
TMDI x and found none.
Where: x = device number (LD 17 DNUM)
appl = the application name.
Action:
Severity: Info.
SNMP trap: No
TMDI0205 x appl y z An error was encountered when searching the system disk to find a version
of an application for TMDI x. Refer to an accompanying SDL error message for
the exact error reason. This message indicates that the Meridian 1 will attempt
to
enable the application in question if a version exists on the card.
(y and z are for design use only)
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2228 of 2360

TMDI0206 x appl y z An error was encountered when comparing a version of an application on
the system disk with the version on TMDI x.
application if a version exists on the card.
Severity: Info.
SNMP trap: No
TMDI0207 x appl y z An error was encountered when downloading an application to TMDI x.

Severity: Info.
TMDI0208 x
SNMP trap: No
When preparing to download the base software to TMDI x, the card indicated
that
some kind of fatal error was encountered. Where: x = device number (LD 17
DNUM).
Action: Execute self-tests before attempting any other action regarding this
card.
Severity: Info.
TMDI0209 x y z
SNMP trap: Yes
on
MSDL x requested that a buffer pool be freed. When this occurred, there was
at
least one outstanding buffer. The basecode waited for the buffer(s) to be
returned
to the pool before freeing the buffers, but it never returned. The buffer pool was
forcibly freed by the basecode.
(y and z are for design use only).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2229 of 2360

TMDI0300 data
The TMDI background audit has changed the card state. In the cases where
the
card was previously enabled and now is no longer enabled, another TMDI
message will indicate the reason for the state change. When making a state
transition due to a fatal error on the card, the reason for the fatal error is
displayed
in this message. This is an informational message and requires no action by
the
craftsperson.
Output data: TMDI300 x FROM: aaaa TO: bbbb TIME time REASON cccc
Where:
x = TMDI card number (in decimal)
aaaa = the status of the TMDI prior to the state change
bbbb = the state of the card after the state change
time = the time of the state change
cccc = reason for the error (only when TO: SYS DSBL - FATAL ERROR)
Action:
Severity: Info.
TMDI0301 x y z
SNMP trap: No
An expedited data unit was received. The Meridian 1 is not expecting TMDI x
to
generate any messages in its current state. However, immediately following a
state transition to a disabled state, a pending message may cause this
message
to be displayed. This informational message indicates that the incoming
message
from the card was not processed due to the state change. No action is
required.
Action:
Severity: Info.
TMDI0302 x y
SNMP trap: No
Access to the memory space shared by the Meridian 1 and the TMDI (Shared
RAM) has been momentarily suspended by TMDI x. There is no specific action
to
be taken as a result of this message; however, it indicates that message
transfer
between the Meridian 1 and the card ceased momentarily.
Where: x = device number (LD 17 DNUM) and y = the reason for the
System Messages
Page 2230 of 2360

suspension.
Currently the only reason supported is the value 1, which indicates that some
kind of buffer corruption was detected.
Action:
Severity: Info.
TMDI0303 x y
SNMP trap: No
ring
or both, causing access to the memory space shared by the Meridian 1 CPU
and
TMDI x (Shared RAM) to be momentarily suspended.
Take no action because of this message; however, it indicates that message
transfer between the Meridian 1 and the card ceased momentarily.
Where: x = device number (LD 17 DNUM) and y = a decimal number indicating
where the corruption was detected. 1 means receive ring, 2 means transmit
ring,
and 3 means both receive and transmit rings.
Action:
Severity: Info.
TMDI0304 x (y) z
SNMP trap: No
The Meridian 1 received 100 or more messages from TMDI x within two
removing the card from service. Where: x = card number (LD 17 CARD). y =
the Meridian 1 index intended for design use only. z = the time in milliseconds
to receive the previous 100 messages.
Action:
Severity: Info.
TMDI0305 x y
553-3001-411
SNMP trap: No
The Meridian 1 received 200 or more messages from TMDI x within two
seconds.
At this level of message transfer, there may be some impact to the overall
system
performance. The level of message transfer does not warrant removing the
card
from service.
Standard 15.00
January 2006
Page 2231 of 2360

y = the rate of message transfer from the card to the Meridian 1 (in terms of
messages per second)
Action:
Severity: Info.
TMDI0306 x y
SNMP trap: No
The Meridian 1 has received 300 or more messages from TMDI x within one
second. At this level of message transfer, there may be some impact to the
overall
system performance. The level of message transfer warrants removing the
card
from service.
y = the rate of message transfer from the card to the Meridian 1 (in terms of
messages per second)
Action:
Severity: Info.
TMDI0307 x data
SNMP trap: No
TMDI x encountered a fatal error. Where: x = device number (LD 17 DNUM).

is
intended for design use only.
Action:
Severity: Info.
SNMP trap: Yes
TMDI0308 x y appl data TMDI x reported that it received a message with an invalid (bad)
socket ID.
Where:
y = the socket ID appl = the application name
data = up to eight words of hex data representing the message sent
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2232 of 2360

TMDI0451 <cardAddress> <(cardIndex)> <invalidCardstate> An invalid card state change
request from the SL1 task has been detected by the MMIH driver.
card.
Severity: Info.
SNMP trap: No
TMDI0452 <cardAddress> <cardIndex> The MMIH driver failed to send an SSD message to the
SL1 task.
group.
Severity: Info.
SNMP trap: No
TMDI0453 <cardAddress> <cardIndex> The MMIH driver failed to send an RFC message to the
SL1 task.
group.
Severity: Info.
SNMP trap: No
TMDI0454 <cardAddress> <cardIndex> The MMIH driver failed to place a transmit expedited
Action: Disable and then enable the MSDL/MISP/TMDI card. If the problem
persists contact your technical support group.
then enable the MSDL/MISP/TMDI card. If the problem persists contact your
Severity: Info.
SNMP trap: No
TMDI0455 <cardAddress> <cardIndex> The MMIH driver failed to send the Start UIPE Call
Action: The call rebuild operation for that MSDL will fail. If necessary, disable
and
then enable the MSDL/MISP/TMDI card. If the problem persists contact your
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2233 of 2360

TMDI0456 <blockSize> The MMIH driver failed when it allocated memory of the size blockSize for
the buffer pool. The system is probably out of memory and cannot
communicate
with the MSDL/MISP/TMDI cards.
Severity: Info.
SNMP trap: No
TMDI0457 <first 16 words of msg> The MMIH has found a buffer in the Rx Ring message queue
with an expired timestamp. The SL1 application has not processed the buffer's
content promptly or the SSD message to the SL1 task was lost. The buffer's
timestamp is reset and the buffer is returned as a free buffer. The first 16 words
Action: Check the traffic reports. Excessive traffic can cause a delay in the core
CPU.
Severity: Info.
SNMP trap: No
TMDI0458 <first 16 words of msg> The MMIH has found a buffer in the Tx Exp message queue
card.
The buffer is overwritten with the new message data. The first 16 words (32
bytes)
of the discarded message are printed, 8 words to a line.
card.
Severity: Info.
TMDI0459
SNMP trap: No
corrupted
and will prevent the system from communicating with the MSDL/MISP/TMDI
cards.
Severity: Info.
SNMP trap: No
TMDI0460 <cardIndex> The MMIH driver has found that the card index is out of range. The card
MSDL/MISP/TMDI cards.
Severity: Info.
SNMP trap: No
System Messages
Page 2234 of 2360

TMDI0461<cardAddress rtclock maintenancePegs> A query base code message was sent by
the
MMIH after finding the SRAM suspended. maintenancePegs is a list of peg
counts kept by the card's maintenance task.
Action:
Severity: Info.
SNMP trap: No
TMDI0462 <cardAddress rtclock Msl1Pegs> This message is printed in series with TMDI0461.
msl1Pegs is a list of peg counts kept by the card's SL1 messaging interface
task.
card.
Severity: Info.
SNMP trap: No
TMDI0463 <cardAddress rtclock debugPegs> This message is printed in series with

TMDI0462.
debugPegs is a list of peg counts kept by the card's debug task.
card.
Severity: Info.
SNMP trap: No
TMDI0464 <cardAddress rtclock utilityPegs> This message is printed in series with TMDI0463.
utilityPegs is a list of pegs kept by the card's utility task
card.
Severity: Info.
SNMP trap: No
TMDI0465 <cardAddress rtclock layer1Pegs> This message is printed in series with

TMDI0464.
layer1Pegs is a list of pegs kept by the card's Layer 1 task.
card.
Severity: Info.
SNMP trap: No
TMDI0466 <cardAddress rtclock returnCode> The Interface Audit's polling message cannot be
sent to the card's ring interface. The returnCode is the reason why the
message
has not been sent. The following returnCode values can appear:
553-3001-411
Standard 15.00
January 2006
Page 2235 of 2360

0-request failed (null message pointer, empty data socket)
1-request succeeded
2-no operation (invalid card state)
4-flow control
5-no buffer
8-invalid socket ID
card.
Severity: Info.
SNMP trap: No
TMDI0467 <cardAddress> <cardIndex> <rtclock> The SRAM Suspend message cannot be

sent
to the card through the expedited interface in response to two or more no
buffer
conditions being detected in a timespan greater than 100 msec.
card, or replace the card.
Severity: Info.
SNMP trap: No
TMDI0468 <cardAddress> <cardIndex> <rtclock> <returnCode> <socketId application>

<'First 8 words of the msg'> The application's message cannot be sent to the
ring and
the reason code is other than no buffer.
socketID is the socket for the message to be sent
applicationID identifies the transmitting application
The first 8 words of the message are displayed in hex
returncode contains the actual value returned by the procedure and contains
one
of the following values:
0-request failed (null message pointer, empty data socket)
1-request succeeded
4-flow control
5-no buffer
System Messages
Page 2236 of 2360

8-invalid socket ID
card.
Severity: Info.
SNMP trap: No
TMDI0469 <cardAddress> <cardIndex> <rtclock> A no buffer condition occurred because the

transmitting ring is in the interface full state.
Severity: Info.
SNMP trap: No
TMDI0470 <cardAddress> <cardIndex> <rtclock> A no buffer condition occurred because the

Severity: Info.
SNMP trap: No
TMDI0471 <cardAddress> <cardIndex> <rtclock messageSize> A no buffer condition

occurred
because a single buffer message is larger than the size of a single buffer.
corrupted.
Severity: Info.
SNMP trap: No
TMDI0472 <cardAddress> <cardIndex> <rtclock messageSize> Insufficient buffers available

in
the transmit ring for the message.
Severity: Info.
SNMP trap: No
TMDI0474 <cardAddress> <cardIndex> <rtclock> <socketId application> <'First 8 words of

the msg'> A no buffer condition has been encountered while attempting to send
a
message to the transmit ring. The first 8 words of the message are displayed in
553-3001-411
Standard 15.00
January 2006
Page 2237 of 2360

hex.
The socketID is the socket for the message to be transmitted
The applicationID is the application ID of the application sending the message
Severity: Info.
SNMP trap: No
TMDI0475 <cardAddress><cardIndex><rtclock> <tempNoBufferCount>

<rtclockOfFirstNoBuffer> This message is printed when the first line of
corrective action (suspending the transmit ring) is taken. It displays the
contents
of the error detection variables and the descriptor words of all buffers in the
transmit ring. It is printed in series with TMDI0476 and TMDI0477. The
variables
are:
tempNoBufferCount - number of consecutive no buffer occurrences since the
last
successful write to the transmit ring.
totalNoBufferCount - total number of no buffer occurrences for the card.
rtclockOfFirstNoBuffer - rtclock value at the time of the first no buffer
occurrence
following the last successful write to the transmit ring.
descriptor words - all 60 descriptor words are printed (in hex), six to a line.
Severity: Info.
SNMP trap: No
TMDI0476 <cardAddress> <cardIndex>< rtclock> <currentIndex>

<descriptorBLockAddress> <bufferSize> <numberOfBuffers>
<transmitRing Address> <transmitRingState> This message displays
pertinent variables kept by the MMIH driver for the transmit ring. It is printed in
series with TMDI0475 and TMDI0477. The variables printed are: currentIndex
- the MMIH's current index into the transmit ring's buffers (head pointer),
descriptorBlock Address - offset of the descriptor block in the SRAM,
bufferSize - size of the buffers in the transmit ring, numberOfBuffers - number
of buffers in the transmit ring, transmitRingAddress - address of the transmit
ring in the card's SRAM, transmitRingState - current state of the transmit ring
Severity: Info.
SNMP trap: No
System Messages
Page 2238 of 2360

TMDI0477 <cardAddress> <cardIndex> rtclock '44SRAM configuration Block words' This
message displays the contents of the SRAM configuration block. It is printed in
series with TMDI0475 and TMDI0476.
- configuration words - all 44 descriptor words are printed (in hex), four to a
line.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2239 of 2360
TMF: Test Multifrequencies

Messages
TMF0000
Program Identifier
Action:
Severity: Minor.
TMF0001
SNMP trap: No
Invalid input, number of chars in one field are greater than 4.

Action:
Severity: Info.
TMF0002
SNMP trap: No
Invalid input, garbage datatype.

Action:
Severity: Info.
TMF0003
SNMP trap: No
Invalid input, command field unknown.

Action:
Severity: Info.
TMF0004
SNMP trap: No
Invalid input, too many parameters.

Action:
Severity: Info.
TMF0005
SNMP trap: No
Last command is still in progress.

Action:
Severity: Info.
TMF0006
SNMP trap: No
SNMP trap: No
Invalid TN.
Action:
Severity: Info.
System Messages
Page 2240 of 2360

TMF0007
Invalid DOD trunk.

Action:
Severity: Info.
TMF0008
SNMP trap: No
Trunk is busy or disabled.

Action:
Severity: Info.
TMF0009
SNMP trap: No
Invalid TN. SHLF out-of-range (0 to 3).

Action:
Severity: Info.
TMF0010
SNMP trap: No
Invalid TN. Card out-of-range (1 to 10).

Action:
Severity: Info.
TMF0011
SNMP trap: No
SNMP trap: No
Invalid set TN.

Action:
Severity: Info.
TMF0012
Defined set is busy or disabled.

Action:
Severity: Info.
TMF0013
SNMP trap: No
Package restricted, Overlay not allowed to load.

Action:
Severity: Info.
TMF0014
SNMP trap: No
Signaling type not defined.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2241 of 2360

TMF0015
Signaling type already defined.

Action:
Severity: Info.
TMF0016
SNMP trap: No
Command not valid for MFE signaling.

Action:
Severity: Info.
TMF0017
SNMP trap: No
Trunk Busy - DSI Timing.

Action:
Severity: Info.
TMF0018
SNMP trap: No
Use loop and channel for digital loop TN.

Action:
Severity: Info.
TMF0019
SNMP trap: No
SNMP trap: No
Invalid Digital Loop TN.

Action:
Severity: Info.
System Messages
Page 2242 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2243 of 2360
TRA: Call Trace (LD 80)

The Call Trace program (LD 80) provides a means of tracing a call by looking
at a snap shot of the transient data (such as Call Register contents) associated
with the call.
The program has three basic commands:
TRAT for tracing attendant consoles
TRAC for tracing sets and trunks
TRAD for tracing calls through Computer PBX Interface (CPI), Digital Trunk
Interface (DTI), Primary Rate Interface, or Digital Link Interface (DLI) loops
The TRAC command can be used to print the tone detector TN if a tone
detector is used at the time of the call trace.
Additional information on the NARS/BARS/CDP and Ring Again (RGA)
features can be retrieved by adding DEV to any of the TRAC commands.
Example: TRAC L S C U DEV
BRI DNs can be traced with the TRAC C DN command. For TRAC L S C U,
enter U = DSL0 to DSL7 for Digital Subscriber Loops.
The command results are reported in TRA messages.
Messages
TRA0000
Program identifier.
Action:
Severity: Info.
TRA0100
SNMP trap: No
SNMP trap: No
SNMP trap: No
Illegal command.
Action:
Severity: Info.
TRA0101
Illegal input parameters.

Action:
Severity: Info.
TRA0105
Input DN is special prefix.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2244 of 2360

TRA0106
Illegal input parameters.

Action:
Severity: Info.
TRA0108
SNMP trap: No
Illegal digits stored in Call Register.

Action:
Severity: Info.
TRA0110
SNMP trap: No
Fails TNTRANS (or loop disabled).

Action:
Severity: Info.
TRA0111
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Fails TNTRANS.
Action:
Severity: Info.
TRA0112
Fails TNTRANS.
Action:
Severity: Info.
TRA0113
Fails TNTRANS.
Action:
Severity: Info.
TRA0120
Fails DNTRANS.
Action:
Severity: Info.
TRA0121
Call trace fails.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
Page 2245 of 2360

TRA0122
Call trace fails.

Action:
Severity: Info.
TRA0130
SNMP trap: No
SNMP trap: No
Call trace fails.

Action:
Severity: Info.
TRA0142
Attendant number exceeds the maximum number defined.

Action:
Severity: Info.
TRA0150
SNMP trap: No
Digitone Receiver (TTR/DTR) cannot be traced.

Action: Input * and carriage return to stop printout.
Severity: Info.
TRA0160
SNMP trap: No
Specified key does not exist.

Action:
Severity: Info.
TRA0180
SNMP trap: No
Loop is not a Digital Trunk loop.

Action:
Severity: Info.
TRA0181
SNMP trap: No
Channel to TN conversion failed.

Action:
Severity: Info.
TRA0182
SNMP trap: No
Loop is a DTI loop, use TRAD.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2246 of 2360

TRA0190
TN cannot be traced.
Action:
Severity: Info.
TRA0191
SNMP trap: No
SNMP trap: No
DN cannot be traced.
Action:
Severity: Info.
TRA0201
Route member out-of-range.

Action:
Severity: Info.
TRA0202
SNMP trap: No
Route member does not exist.

Action:
Severity: Info.
TRA0300
SNMP trap: No
A Local Steering Code (LSC) without an associated DN cannot be traced.

Action:
Severity: Info.
TRA0301
SNMP trap: No
Your TNTRANS:TDET_TN has failed. Your PRINT_TDET may be corrupted

by the procedure RGAT_INSERT_TIME.
Action:
Severity: Info.
TRA0304
SNMP trap: No
Invalid digit stored in BRI message Call Register.

Action:
Severity: Info.
TRA0305
SNMP trap: No
The Multi-User Login feature is not active.

Action: Be sure the package is enabled, and MULTI_USER = YES in LD 17.
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2247 of 2360

TRA0306
The time duration is out-of-range.

Action: The correct time format is: hh = 00-23, mm = 00-59.
Severity: Info.
TRA0307
SNMP trap: No
Illegal digit(s) in stored M911 auxiliary Call Register.

Action:
Severity: Info.
TRA0308
SNMP trap: No
Illegal digit(s) stored in DN field.

Action:
Severity: Info.
TRA0309
SNMP trap: No
More than three ENTC/ENTD commands have been entered. You cannot
enter the commands again.
Action:
Severity: Info.
TRA0310
SNMP trap: No
The Trace has been stopped because the traced TN or Digital trunk has been
relocated or removed.
Action:
Severity: Info.
TRA0311
SNMP trap: No
More than one GOTR has been entered. You cannot enter the command
again.
Action:
Severity: Info.
TRA0312
SNMP trap: No
The same TN or Digital trunk has been entered more than once. The same TN
or Digital trunk cannot be traced simultaneously by the enhanced trace
commands.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2248 of 2360

TRA0313
You must enter ENTC/ENTD before entering GOTR.

Action:
Severity: Info.
TRA0314
SNMP trap: No
You must enter the STPT command before entering DALL ENTC or DALL
ENTD.
Action:
Severity: Info.
TRA0317
SNMP trap: No
Cannot use Enhanced trace on a phantom TN/DN.

Action: Use the regular trace commands.
Severity: Info.
TRA0319
SNMP trap: No
An illegal digit is stored in the TWR1 CLID field.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2249 of 2360
TRK: Trunk Diagnostic (LD 36)

Insufficient space in the Overlay area requires the trunk diagnostic to be split
into two programs. LD 41 is an extension of LD 36.
The programs allow trunks to be tested from either the SL-1 site or a remote
test center. Problems are reported in TRK messages.
LD 36 can perform tests on XDID, XCOT and XFEM cards also. These cards
will be recognized in relevant commands.
Messages
TRK0000
Program Identifier
Action:
Severity: Minor.
TRK0001
SNMP trap: Yes
Invalid command.
Action: Check command format and begin again.
Severity: Info.
TRK0002
SNMP trap: Yes
Action: Check command format and begin again.
Severity: Info.
TRK0003
SNMP trap: Yes
Invalid or out-of-range TN.

Action:
Severity: Info.
TRK0004
SNMP trap: Yes
Too many digits in the DN.

Action:
Severity: Info.
TRK0005
SNMP trap: Yes
Unit requested is not a trunk.

Action:
Severity: Info.
SNMP trap: Yes
System Messages
Page 2250 of 2360

TRK0006
Unit requested or all trunks busy.

Action: Wait until idle.
Severity: Info.
TRK0007
SNMP trap: Yes
Command not valid unless a monitor link exists, i.e., a trunk link between the
SL-1 system and the test center.
Action: Use CALL command if at test center or abort and reload from SL-1
location.
Severity: Info.
TRK0008
SNMP trap: Yes
No CO trunk defined in the system. Cannot use command.

Action: Change to SL-1 telephone.
Severity: Info.
TRK0009
SNMP trap: Yes
No maintenance SL-1 telephone available for the call. SL-1 telephone may be
busy.
Action: Wait until idle.
Severity: Info.
TRK0010
SNMP trap: Yes
Trunk must be a CO trunk.

Action: Check terminal numbers and begin again.
Severity: Info.
TRK0011
SNMP trap: Yes
Call command not allowed from a SL-1 telephone.

Action: Use trunk command directly.
Severity: Info.
TRK0012
SNMP trap: Yes
Customer or route does not exist or is out-of-range.

The Format is: customer (range 0-99), route; (range 0-127).
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2251 of 2360

TRK0013
The unit requested is not an incoming trunk.

Action: Check data. Command is allowed only for incoming trunks.
Severity: Info.
TRK0014
SNMP trap: Yes
Unexpected call status change, e.g., disconnect from far-end.

Action: Input request again. If still same, try another test number.
Severity: Info.
TRK0016
SNMP trap: Yes
Trunk command not valid for AIOD and RLT-main trunks.

Action:
Severity: Info.
TRK0017
SNMP trap: Yes
Seize failure or failure to acknowledge seizing. Also occurs when LD 36 is

used with a remote maintenance phone to dial an ISL TIE line. BUG3068
occurs at the far-end.
Action:
Severity: Minor.
TRK0018
SNMP trap: Yes
STAT, DISC and ENLC commands can only be used with trunk cards.
Action:
Severity: Info.
TRK0030
SNMP trap: Yes
ANI trunks seizure failure, or wink start signal (REQ-N1) not received or not
properly received from far-end. Also wrong number of digits dialed or ANI
access code (0/1) is missing.
Action:
Severity: Minor.
TRK0031
SNMP trap: Yes
ANI trunks calling number identification request (REQ-N2) not received or not
properly received from far-end.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2252 of 2360

TRK0032
LD 36 Invalid command for modem-type trunks. Add-on Module (ADM) or

Modem trunks cannot be tested by this program. Use LD 32.
Action:
Severity: Info.
TRK0033
SNMP trap: Yes
SNMP trap: Yes
TN is not a PPM trunk.

Action:
Severity: Info.
TRK0034
Pulses on E&M trunk are either bad or not received.

Action:
Severity: Minor.
TRK0035
SNMP trap: Yes
SNMP trap: Yes
Route has no member.

Action:
Severity: Minor.
TRK0036
PPM read request is pending on this card.

Action:
Severity: Minor.
TRK0040 c r
SNMP trap: Yes
No recorded announcement (RAN), music (MUS) or Automatic Wake Up

(AWK) device exists for the customer and route specified.
Action:
Severity: Minor.
TRK0041 c r
SNMP trap: Yes
The RAN, MUS or AWK device specified for customer c and route r is not
operable.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2253 of 2360

TRK0043 c r tn1 tn2 The RAN, MUS or AWR device specified has RAN trunks associated with it
that are not in the trunk list specified for that route. TNs specified are
connected physically to a RAN, MUS or AWR device but trunk data does not
reflect this.
Action: Change customer data or wiring.
Severity: Minor.
SNMP trap: Yes
TRK0044 c r tn1 tn 2 The RAN, MUS or AWR device specified has RAN trunks listed in its trunk
list but the TNs are not physically connected to RAN, MUS or AWR device.
(This is the inverse of TRK043).
Action: Change trunk data or wiring.
Severity: Minor.
TRK0045 c r
SNMP trap: Yes
Too many trunks connected to RAN, MUS or AWR device for this customer
and route. Limit is 100 trunks.
Action:
Severity: Minor.
TRK0100 tn
SNMP trap: Yes
WATS trunk- Short Hold. Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0101 tn
SNMP trap: Yes
WATS - Seizure failure (SEIZ). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0102 tn
SNMP trap: Yes
WATS - Ringing on Seized Trunk (ILLR). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0103 tn
SNMP trap: Yes
WATS - Ring or Ground Detection failure (RGFL). Refer to "Trunk Failures"

section.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2254 of 2360

TRK0104 tn
WATS - Supervision failure (SUPV). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0105 tn
SNMP trap: Yes
WATS - Repetitive messages (REPT). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0106 tn
SNMP trap: Yes
WATS - Release failure. Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0110 tn
SNMP trap: Yes
FEX trunk, TWR1 trunk - Short hold

Action:
Severity: Minor.
TRK0111 tn
SNMP trap: Yes
FEX - Seizure failure (SEIZ). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0112 tn
SNMP trap: Yes
FEX - Ringing on Seized Trunk (ILLR). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0113 tn
SNMP trap: Yes
FEX - Ring or Ground Detection failure (RGFL). Refer to "Trunk Failures"

section.
Action:
Severity: Minor.
TRK0114 tn
SNMP trap: Yes
FEX - Supervision failure (SUPV). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2255 of 2360

TRK0115 tn
FEX - Repetitive messages (REPT). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0116 tn
SNMP trap: Yes
FEX - Release failure. Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0120 tn
SNMP trap: Yes
CCSA trunk- Short Hold. Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0121 tn
SNMP trap: No
CCSA - Seizure failure (SEIZ). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0122 tn
SNMP trap: Yes
CCSA - Ringing on Seized Trunk (ILLR). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0123 tn
SNMP trap: Yes
CCSA - Ring or Ground Detection failure (RGFL).

Action:
Severity: Info.
TRK0124 tn
SNMP trap: Yes
CCSA - Supervision failure (SUPV). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0125 tn
SNMP trap: Yes
CCSA - Repetitive messages (REPT). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2256 of 2360

TRK0126 tn
CCSA - Release failure. Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0130 tn
SNMP trap: Yes
DID trunk- Short Hold. Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0131 tn
SNMP trap: Yes
DID - Seizure failure (SEIZ). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0132 tn
SNMP trap: Yes
DID - Ringing on Seized Trunk (ILLR). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0133 tn
SNMP trap: Yes
DID - Ring or Ground Detection failure (RGFL). Refer to "Trunk Failures"

section.
Action:
Severity: Minor.
TRK0134 tn
SNMP trap: Yes
DID - Supervision failure (SUPV). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0135 tn
SNMP trap: Yes
DID - Repetitive messages (REPT). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0136 tn
SNMP trap: Yes
Release failure on incoming DID trunk. Disconnect supervision timer (DSI)

was exceeded.
Action: Trunk state is changed to lockout. Refer to "Trunk Failures" section.
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2257 of 2360

TRK0137 tn
Partial dial timeout on DID trunk.

Action:
Severity: Minor.
TRK0139 tn
SNMP trap: Yes
No response from Universal Trunk or E&M/Dictation Trunk.

Action: Try the command again. If the problem persists, check the Network Card
or Controller (NT8D04/NT8D01) and cable path to the Universal Trunk or
E&M/Dictation Trunk card.
Severity: Minor.
TRK0150 tn
SNMP trap: Yes
PTRS/CO trunk - Short Hold. Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0151 tn
SNMP trap: Yes
PTRS/CO - Seizure failure (SEIZ). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0152 tn
SNMP trap: Yes
PTRS/CO - Ringing on Seized Trunk (ILLR). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0153 tn
SNMP trap: Yes
PTRS/CO - Ring or Ground Detection failure (RGFL). Refer to "Trunk Failures"

section.
Action:
Severity: Minor.
TRK0154
SNMP trap: Yes
Tip and ring reversal, or other trunk wiring problem threshold (LD 16 RSVD)
has been reached.
Action: Check the trunk wiring.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2258 of 2360

TRK0155 tn
PTRS/CO - Repetitive messages (REPT). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0156 tn
SNMP trap: Yes
Release failure on outgoing CO trunk. Disconnect supervision timer (DSI) was

exceeded. Refer to "Trunk Failures" section.
Action:
Severity: Minor.
TRK0157 tn
SNMP trap: Yes
PPM read failure. An attempt to read the contents of the trunk register failed.
Action:
Severity: Minor.
TRK0160 tn
SNMP trap: Yes
TIE trunk- Short Hold. Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0161 tn
SNMP trap: Yes
TIE - Seizure failure (SEIZ). Refer to "Trunk Failures" section.

Action:
Severity: Minor.
TRK0162 tn
SNMP trap: Yes
TIE - Ringing on Seized Trunk (ILLR).

Action: Refer to "Trunk Failures" section.
Severity: Minor.
TRK0163 tn
SNMP trap: Yes
TIE - Ring or Ground Detection failure (RGFL).

Severity: Minor.
TRK0164 tn
SNMP trap: Yes
TIE - Supervision failure (SUPV).

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2259 of 2360

TRK0165 tn
TIE - Repetitive messages (REPT).

Severity: Minor.
TRK0166 tn
SNMP trap: Yes
TIE - Release failure.

Severity: Minor.
TRK0170 tn
SNMP trap: Yes
Paging trunk- Short Hold.

Severity: Minor.
TRK0171 tn
SNMP trap: No
Paging - Seizure failure (SEIZ).

Severity: Minor.
TRK0172 tn
SNMP trap: No
Paging - Ringing on Seized Trunk (ILLR).

Severity: Minor.
TRK0173 tn
SNMP trap: No
Paging - Ring or Ground Detection failure (RGFL).

Severity: Minor.
TRK0174 tn
SNMP trap: No
Paging - Supervision failure (SUPV).

Severity: Minor.
TRK0175 tn
SNMP trap: No
Paging - Repetitive messages (REPT).

Severity: Minor.
SNMP trap: No
System Messages
Page 2260 of 2360

TRK0176 tn
Paging - Release failure.

Severity: Minor.
TRK0177
SNMP trap: No
MFR holding time has timed out on incoming TWR1 call.

Action:
Severity: Minor.
TRK0180 tn
SNMP trap: Yes
Dictation trunk- Short Hold.

Severity: Minor.
TRK0181 tn
SNMP trap: Yes
Dictation - Seizure failure (SEIZ).

Severity: Minor.
TRK0182 tn
SNMP trap: No
Dictation - Ringing on Seized Trunk (ILLR).

Severity: Minor.
TRK0183 tn
SNMP trap: No
Dictation - Ring or Ground Detection failure (RGFL).

Severity: Minor.
TRK0184 tn
SNMP trap: No
Dictation - Supervision failure (SUPV).

Severity: Minor.
TRK0185 tn
SNMP trap: No
Dictation - Repetitive messages (REPT).

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2261 of 2360

TRK0186 tn
Dictation - Release failure.

Severity: Minor.
TRK0191 tn
SNMP trap: No
No control signal (CNTL) returned. A control signal indicating the status of

Code-a-Phone or Audichron has not been received by the processor in the last
5 minutes for Code-a-Phone or 32 seconds for Audichron.
Action:
Severity: Minor.
TRK0192 tn
SNMP trap: Yes
Start failure (STRT). To start Code-a-Phone machine, a start pulse is sent

from any one of the trunks connected to the machine.
Action:
Severity: Minor.
TRK0193 tn
SNMP trap: Yes
Illegal messages from trunk (ILLM). Any messages received from RAN trunk
are considered illegal if they are out of sequence of duration or control signal
that remains open is less than 2 s.
Action:
Severity: Minor.
TRK0202 tn
SNMP trap: Yes
Failure to acknowledge transmit bit (TRAC). Before actual transmission of

data can occur, a bid or request to begin transmission is sent to the CO.
Failure to acknowledge such a request within 4 s is considered a failure.
Action:
Severity: Minor.
TRK0210 tn
SNMP trap: No
CCSA-ANI trunk- Short Hold.

Severity: Minor.
TRK0211 tn
SNMP trap: No
CCSA-ANI - Seizure failure (SEIZ).

Severity: Minor.
SNMP trap: No
System Messages
Page 2262 of 2360

TRK0212 tn
CCSA-ANI - Ringing on Seized Trunk (ILLR).

Severity: Minor.
TRK0213 tn
SNMP trap: No
CCSA-ANI - Ring or Ground Detection failure (RGFL).

Severity: Minor.
TRK0214 tn
SNMP trap: No
CCSA-ANI - Supervision failure (SUPV).

Severity: Minor.
TRK0215 tn
SNMP trap: No
CCSA-ANI - Repetitive messages (REPT).

Severity: Minor.
TRK0216 tn
SNMP trap: No
CCSA-ANI - Release failure.

Severity: Minor.
TRK0220 tn
SNMP trap: No
CAMA trunk- Short Hold.

Severity: Minor.
TRK0221 tn
SNMP trap: No
CAMA - Seizure failure (SEIZ).

Severity: Minor.
TRK0222 tn
SNMP trap: No
CAMA - Ringing on Seized Trunk (ILLR).

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2263 of 2360

TRK0223 tn
CAMA - Ring or Ground Detection failure (RGFL).

Severity: Minor.
TRK0224 tn
SNMP trap: No
CAMA - Supervision failure (SUPV).

Severity: Minor.
TRK0225 tn
SNMP trap: No
CAMA - Repetitive messages (REPT).

Severity: Minor.
TRK0226 tn
SNMP trap: No
CAMA - Release failure.

Severity: Minor.
TRK0230 tn
SNMP trap: No
RLT-main, CAS system - Short Hold.

Severity: Minor.
TRK0231 tn
SNMP trap: No
RLT-main, CAS systems - Seizure failure (SEIZ).

See Note 1.
Action:
Severity: Minor.
TRK0232 tn
SNMP trap: No
RLT-main, CAS systems - Ringing on Seized Trunk (ILLR).

Severity: Minor.
TRK0233 tn
SNMP trap: No
RLT-main, CAS systems - Ring or Ground Detection failure (RGFL).

Severity: Minor.
SNMP trap: No
System Messages
Page 2264 of 2360

TRK0234 tn
RLT-main, CAS systems - Supervision failure (SUPV).

Severity: Minor.
TRK0235 tn
SNMP trap: No
RLT-main, CAS systems - Repetitive messages (REPT).

Severity: Minor.
TRK0236 tn
SNMP trap: No
RLT-main, CAS systems - Release failure.

Severity: Minor.
TRK0237 tn
SNMP trap: No
Failure of far-end response to near end seizure. The near-end did not
recognize the wink signal from the far end because:
1. the wink signal was not received within 5 seconds because of transmission
delays or hardware failure, or
2. the wink signal was not within specification.
Action:
Severity: Minor.
TRK0238 tn
SNMP trap: No
Far-end dialing failure. The near-end did not receive sufficient digits to be able
to complete the call. This is because:
1. the far-end remained off-hook without sending any digits (faulty hardware
caused a false seizure), or
2. a sender was stuck, causing the inter-digital interval to exceed a threshold.
Action:
Severity: Minor.
TRK0239 tn
SNMP trap: No
Unable to monitor incoming preemption waveforms. Due to a shortage of

system resources, the current call on the indicated trunk cannot be monitored
to detect the preemption waveform coming from the AUTOVON switching
centre.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2265 of 2360

TRK0240 tn
RLT-remote - Short Hold.

Severity: Minor.
TRK0241 tn
SNMP trap: No
RLT-remote - Seizure failure (SEIZ).

Severity: Minor.
TRK0242 tn
SNMP trap: No
RLT-remote - Ringing on Seized Trunk (ILLR).

Severity: Minor.
TRK0243 tn
SNMP trap: No
RLT-remote - Ring or Ground Detection failure (RGFL).

Severity: Minor.
TRK0244 tn
SNMP trap: No
RLT-remote - Supervision failure (SUPV).

Severity: Minor.
TRK0245 tn
SNMP trap: No
RLT-remote - Repetitive messages (REPT).

Severity: Minor.
TRK0246 tn
SNMP trap: No
RLT-remote - Release failure.

Severity: Minor.
TRK0250 tn
SNMP trap: No
Modem - Short Hold.

Severity: Minor.
SNMP trap: No
System Messages
Page 2266 of 2360

TRK0251 tn
Modem - Seizure failure (SEIZ).

Severity: Minor.
TRK0252 tn
SNMP trap: No
Modem - Ringing on Seized Trunk (ILLR).

Severity: Minor.
TRK0253 tn
SNMP trap: No
Modem - Ring or Ground Detection failure (RGFL).

Severity: Minor.
TRK0254 tn
SNMP trap: No
Modem - Supervision failure (SUPV).

Severity: Minor.
TRK0255 tn
SNMP trap: No
Modem - Repetitive messages (REPT).

Severity: Minor.
TRK0256 tn
SNMP trap: No
Modem - Release failure.

Severity: Minor.
TRK0300 tn
SNMP trap: No
Link/DCHI state is not yet defined.

Action:
Severity: Minor.
TRK0301 loop
SNMP trap: Yes
The loop requested is the Digital Trunk Interface (DTI) or Primary Rate
Interface (PRI); use the DTI Diagnostic instead (LD 60).
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2267 of 2360

TRK0302
Trunk card failed selftest.

Action:
Severity: Minor.
TRK0303
SNMP trap: Yes

Action:
Severity: Info.
TRK0304
SNMP trap: Yes
Shelf number is undefined.

Action:
Severity: Info.
TRK0306
SNMP trap: Yes
Unit number is out-of-range.

Action:
Severity: Info.
TRK0431 tn
SNMP trap: Yes
Seizure acknowledgment expected on DID-DOD or NWK trunk but not

received.
Action:
Severity: Minor.
TRK0432 tn
SNMP trap: Yes
Seizure acknowledgment not expected on DID-DOD or NWK trunk but

received.
Action:
Severity: Minor.
TRK0433 tn
SNMP trap: Yes
Timeout when waiting for ready to outpulse.

Action:
Severity: Minor.
TRK0434 tn
SNMP trap: No
Timeout when waiting for stop to outpulse.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 2268 of 2360

TRK0481 tn
A seizure acknowledgment was expected on dictation trunk but was not

received.
Action:
Severity: Minor.
TRK0482 tn
SNMP trap: No
A seizure acknowledgment was not expected on dictation trunk but was

received.
Action:
Severity: Minor.
TRK0483 tn
SNMP trap: No
An Off-Hook from a TIE trunk was received instead of a Number_Received

signal.
Action:
Severity: Minor.
TRK0501 tn
SNMP trap: Yes
If the trunk is IPE, then Barring is applied to trunk {tn}; otherwise, the trunk has
been made busy due to Line Break Alarm Signal. Feature is XDID Barring or
DID Trunk Failure Monitor.
Action:
Severity: Minor.
TRK0502 tn
SNMP trap: Yes
DID trunk has been idled after a Line Break Alarm Signal correction
Action:
Severity: Minor.
TRK0503 tn
SNMP trap: Yes
TIE trunk has been made busy by a Line Break Alarm Signal.
Action:
Severity: Minor.
TRK0504 tn
SNMP trap: Yes
Tie trunk has been idled after a Line Break Alarm Signal correction.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2269 of 2360

TRK0505 tn
If the trunk is IPE, then Barring is no longer applied to trunk {tn}; otherwise, the
trunk has been idled after Line Break Alarm Signal problem correction.
Feature is XDID Barring or DID Trunk Failure Monitor.
Action:
Severity: Minor.
TRK0506
SNMP trap: Yes
Expected signal not received from Radio Paging equipment. Call abandoned.
Action:
Severity: Minor.
TRK0509
SNMP trap: Yes
Answer expected from XCOT trunk but not received.

Action:
Severity: Minor.
TRK0511
SNMP trap: Yes
An invalid trunk signal was received on an X3W trunk. The signal was ignored.
Action:
Severity: Minor.
TRK0512
SNMP trap: No
Shelf number out-of-range.

Action:
Severity: Minor.
TRK0513
SNMP trap: Yes
Card number out-of-range.

Action:
Severity: Minor.
TRK0514 tn
SNMP trap: Yes
XFCOT Barring is applied to the trunk {unit}. (Barring is applied to the trunk unit
identified by tn. )
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2270 of 2360

TRK0515 tn
XFCOT Barring is no longer applied to the trunk {unit}. (Barring is no longer

applied to trunk unit identified by tn.)
Action:
Severity: Minor.
TRK0516 l s c tn
SNMP trap: Yes
Partial failure of metering on card {lsc}. This is a hardware failure that may
have affected metering activities on one or more calls on the card.
Action:
Severity: Info.
TRK0517 l s c
SNMP trap: Yes
Fatal failure of metering on card {lsc}. his is a hardware failure that affects
metering activities on the card. If PPM is configured, then PPM has been
affected, with the result that further PPM reporting is disabled until either the
pack is disabled and re-enabled or pulled out and reinserted. The CDR
records for calls in progress are incorrect. If Busy Tone Supervision is
configured, then tone supervision can no longer be performed.
Action: Try disabling and re-enabling the card. If the message appears again, it
is probably a hardware fault. Replace the card.
Severity: Minor.
TRK0518 tn
SNMP trap: Yes
The enable command attempted on a XDID/EAM OR XDID/CIS OR XFCOT

unit is cancelled because the unit is in barred state.
Action: Disable and then enable the unit.
Severity: Minor.
TRK0519 tn
SNMP trap: No
Warning: the XDID/EAM or XDID/CIS or XFCOT unit in barred state is

changed to the disable state after a disable command.
Action:
Severity: Minor.
TRK0520 tn
SNMP trap: No
No far-end release message is received from the XDID/EAM unit after a call
blocking sequence. The disable command on this unit is stopped. The unit is
in lockout state.
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2271 of 2360

TRK0521 tn
The disable command has been aborted while waiting for a far-end release
message on a XDID/EAM unit. As soon as the far-end release message is
received, the XDID/EAM unit will still be disabled.
Action:
Severity: Minor.
TRK0522
SNMP trap: No
A barring message is received in an invalid state from a XDID/XFCOT unit.

Action:
Severity: Minor.
TRK0524
SNMP trap: Yes
ISA service route is not allowed for the command.

Action:
Severity: Info.
TRK0526
SNMP trap: Yes
DP digit collection problem was revealed and reported by CDTI2/ CSDTI2 FW

(incoming trunk).
Action: Trunk is locked out.
Severity: Minor.
TRK0527
SNMP trap: No
Outgoing CIS E3W pack requested CIS ANI download by means of TDS or
XCT service loop, but TERNTN fails TNTRANS or FTDS package not
equipped.
Action: Outgoing CIS E3W call will be released; trunk will be idled. Check FTDS
package installed.
Severity: Minor.
TRK0528
SNMP trap: Yes
Outgoing CIS E3W pack requested CIS ANI download by means of TDS or
XCT service loop, but TDS/XCT path request failed.
Action: Outgoing CIS E3W call will be released; trunk will be idled. Check TDS/
XCT and traffic of these service loops.
Severity: Minor.
TRK0529
SNMP trap: Yes
Outgoing CIS E3W pack fails to request CIS ANI download.

Action: Outgoing CIS E3W call will be released; trunk will be idled
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2272 of 2360

TRK0530
Outgoing CIS E3W pack fails to acknowledge CIS ANI already downloaded by
means of TDS or XCT
Action: Outgoing CIS E3W call will be released; trunk will be idled
Severity: Minor.
TRK0531 tn
SNMP trap: Yes
An error has been detected on ISL E&M Tie, Unit will be put to MBSY.
Action:
Severity: Minor.
TRK0532 tn
SNMP trap: Yes
Error condition on ISL E&M Tie removed, Unit in IDLE state.

Action:
Severity: Minor.
TRK0533 tn
SNMP trap: Yes
The enable command is cancelled on this unit because an error exists on the
ISL E&M TIE trunk.
Action:
Severity: Minor.
TRK0843 tn
SNMP trap: No
Off hook from TIE trunk instead of number received signal.

Action:
Severity: Minor.
TRK1120
SNMP trap: No
SNMP trap: Yes
CCSA-Short hold.
Action:
Severity:
TRK3031
Trunk member in a route's trunk list does not exist.

Action:
Severity: Minor.
TRK3108
SNMP trap: No
A trunk does not have wink start arrangement.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2273 of 2360

TRK3115
Trunk does not have answer supervision.

Action:
Severity: Minor.
TRK3116
SNMP trap: No
A command with the same functionality is supported in Overlay 32.

Action:
Severity: Info.
TRK3117
SNMP trap: No
MF input timeout on incoming TWR1 call. Output data: trktn mfrtn tw_inc_pm
clid/address information.
Action:
Severity: Minor.
TRK3118
SNMP trap: Yes
Invalid input received on incoming TWR1 call. Output data: trktn MFR tn
tw_inc_pm clid/address information.
Action:
Severity: Minor.
SNMP trap: Yes
TRK3119 <mm/dd/yyy hh:mm:ss> MNDN <aaaa> TN <TN> SPC call disconnected.

Action: If the condition persists, check the semi-permanent connection.
Severity: Info.
SNMP trap: No
TRK3120 <mm/dd/yyy hh:mm:ss> MNDN <aaaa> TN <TN> The SPC call is connected.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2274 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2275 of 2360
TTY: Teletype Error Reports

Messages
TTY0000
Failure installing the SDI TTY driver.

Action:
Severity: Minor.
TTY0001 x y
SNMP trap: Yes
Cannot create SDI TTY device number x, group y because the TTY driver has
not been installed.
Action:
Severity: Minor.
TTY0002 x y
SNMP trap: Yes
Cannot create TTY device number x, group y because there is not enough
memory.
Action: Manually INIT, then use LD 17 to delete and recreate this TTY.
Severity: Minor.
TTY0003 x y
SNMP trap: Yes
Data corruption on TTY device number x.

Action: Manually INIT.
Severity: Minor.
TTY0004 x y z
SNMP trap: Yes
Invalid FDx with SDI device number y, group z.

Action:
Severity: Minor.
TTY0005
SNMP trap: No
Cannot create pseudo TTY FD table because there is not enough memory.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2276 of 2360

TTY0006 x y
Cannot create CPSI TTY device number x, group y because there is not
enough memory.
Action: Manually INIT, then use LD 17 to delete and recreate this TTY.
Severity: Minor.
TTY0007 x y
SNMP trap: Yes
MSDL TTY device number x, group y cannot be created because there is no

memory for the device descriptor.
Action:
Severity: Minor.
TTY0008 x y
SNMP trap: No
MSDL TTY device number x, group y cannot be created because there is no

memory for the TTY buffers.
Action:
Severity: Minor.
TTY0009 x y z
SNMP trap: No
Invalid FDx with MSDL device number y, group z.

Action:
Severity: Minor.
TTY0010
SNMP trap: No
Cannot create Pseudo TTY (PTY) FD table because there is not enough
memory.
Action:
Severity: Minor.
SNMP trap: No
TTY0011 ch subfunc data Problem sending remote TTY message to pipe: ch = remote TTY
channel #, subfunc = function sent to remote TTY, data = extra data.
Action:
Severity: Minor.
TTY0012
SNMP trap: Yes
PTYxx is busy. Connection closed.

Action: Try again at a later time
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2277 of 2360

TTY0017
Access to unsupported device. DevType: %d DevFd: %d

Action: Report to your technical support group.
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2278 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2279 of 2360
VAS: Value Added Server

Value Added Servers (VAS), such at the Meridian Mail MP are connected to
the system through a Command and Status (CSL) Link. Problems and status
of these links are reported in VAS messages.
Messages
VAS0001 vasid cust A CSL DATA data service access TN message has been sent to the Server,
and a timer has been set up for the response.
Action:
Severity: Minor.
SNMP trap: Yes
VAS0002 vasid cust A CSL DATA VMS access TN message has been sent to the Server, and a
timer has been set up for the response.
Action:
Severity: Minor.
SNMP trap: Yes
VAS0004 vasid cust A CSL DATA primary data service access code message has been sent to
the Server, and a timer has been set up for the response.
Action:
Severity: Minor.
SNMP trap: Yes
VAS0005 vasid cust A CSL DATA VMS access code message has been sent to the Server, and
a timer has been set up for the response.
Action:
Severity: Minor.
SNMP trap: Yes
VAS0006 vasid cust time dn A CSL DATA add data service DN message has been received
from VAS Server. Data service DN has been added to the DN tree.
Action:
Severity: Minor.
SNMP trap: Yes
System Messages
Page 2280 of 2360

VAS0007 vasid cust time dn A CSL DATA delete data service DN message has been received
from VAS Server. Data service DN has been removed from the DN tree.
Action:
Severity: Minor.
VAS0008 vasid
SNMP trap: Yes
The CO Admin audit of VAS-ID Server has begun.

Action:
Severity: Minor.
VAS0010
SNMP trap: Yes
This message indicates that the application was successfully enabled on an

AML link. The information is displayed in the following expanded format when
alarm filtering is configured (package 243). VAS010 mm/dd/yy hr:min:sec
00000 MSG APPLICATION ENABLED OPRDAT: VSID xx APPL yyyy The
reduced format shown below appears when package 243 is not enabled.
Action:
Severity: Info.
VAS0011
SNMP trap: Yes
This message indicates that the application previously established on an AML

link was disabled. The information is displayed in the following expanded
format when alarm filtering is configured (package 243). VAS011 mm/dd/yy
hr:min:sec 00000 MSG APPLICATION DISABLED? OPRDAT: VSID xx APPL
yyyy REASON zzz Where: 1. xx = VAS ID 2. yyyy = application name 3. zzz =
the reason the application failed 4. LINK OUT OF SERVICE = The application
was disabled because the link was removed from service. Restore the link
before enabling the application. The link must be restored before the
application can be reenabled. 5. MANUALLY DISABLED = The application
was disabled in LD 48. Reenable the application. 6. UNKNOWN = The reason
the application failed is unknown. Contact your technical support personnel.
Action:
Severity: Minor.
VAS0012
553-3001-411
SNMP trap: Yes
This message indicates that the application could not be enabled. The
information is displayed in the following expanded format when alarm filtering
is configured (package 243). VAS012 mm/dd/yy hr:min:sec 00000 MSG
FAILED TO ENABLE APPLICATION OPRDAT: VSID xx APPL yyyy REASON
zzz. The reduced format shown below appears when package 243 is not
enabled. VAS012 VSID xx APPL yyyy REASON zzz Where: xx = VAS ID yyyy
= application name zzz = the reason the application failed 1. LINK OUT OF
SERVICE = The application could not be enabled because the link to the
Standard 15.00
January 2006
Page 2281 of 2360

application processor is out of service. The link must be enabled before the
application. Restore the link before enabling the application. 2. REQUEST
REJECTED = The application is not ready or is unequipped on the application
processor. Be sure all the required packages are equipped and ready. 3.
INVALID STATE = The association with the application processor is in an
invalid state. Disable and re-enable the link before enabling the application. 4.
AS EXISTS = A link error exists. Disable and re-enable the link prior to
enabling the application.5. MSG NOT SENT = The message to enable the
application could not be sent to the application processor. Disable and
re-enable the link prior to enabling the application. 6. UNKNOWN = Unknown
cause for failure. Contact your technical support personnel.
Action:
Severity: Minor.
VAS0013
SNMP trap: Yes
This message indicates that the application processor received a badly

structured message from the Meridian 1. Repeat the task performed when this
message was received. The information is displayed in the following expanded
format when alarm filtering is configured (package 243). VAS013 mm/dd/yy
hr:min:sec 00000 MSG APPLICATION PROTOCOL ERROR OPRDAT: VSID
xx APPL yyyy DATA zzz. The reduced format shown below appears when
package 243 is not enabled. VAS013 VSID xx APPL yyyy DATA zzz Where:
xx = VAS ID yyyy = application name zzz = is intended for technical support
personnel only
Action: Contact your technical support group if this message is repeated.
Severity: Minor.
VAS0020
SNMP trap: Yes
This message indicates that the Voice Mailbox (VMB) database audit has
been invoked either manually in LD 48, or by the periodic 5 day audit. The
is configured (package 243). VAS020 mm/dd/yy hr:min:sec 00000 MSG VMB
ADIT INITIATED
Action:
Severity: Minor.
VAS0021
SNMP trap: Yes
This message indicates that the Voice Mailbox (VMB) database audit has
been completed. If DATA_CORRECT = ON in LD 17. No action is necessary.
If DATA_CORRECT = OFF, any reported mismatches must be corrected
manually. The information is displayed in the following expanded format when
00000 MSG VMB AUDIT COMPLETED OPRDAT: x AUDITED y
System Messages
Page 2282 of 2360

MISMATCHES FOUND z ERRORS VAS021 mm/dd/yy hr:min:sec 00000
MSG VMB AUDIT COMPLETED? OPRDAT: x AUDITED y MISMATCHES
CORRECTED z ERRORS. The reduced format shown below appears when
package 243 is not enabled.VAS021 x AUDITED y MISMATCHES FOUND z
ERRORS VAS021 x AUDITED y MISMATCHES CORRECTED z ERRORS
Where: x = the number of VMBs audited y = the number of mismatches found
or corrected z = the number of transaction errors
Action:
Severity: Minor.
VAS0022
SNMP trap: Yes
This message indicates that the Voice Mailbox (VMB) database audit that was
running has been aborted. The information is displayed in the following
expanded format when alarm filtering is configured (package 243). VAS022
mm/dd/yy hr:min:sec 00000 MSG VMB AUDIT ABORTED OPRDAT: x
AUDITED y MISMATCHES FOUND z ERRORS VAS022 mm/dd/yy
hr:min:sec 00000 MSG VMB AUDIT ABORTED OPRDAT: x AUDITED y
MISMATCHES CORRECTED z ERRORS. The reduced format shown below
appears when package 243 is not enabled. VAS022 x AUDITED y
MISMATCHES FOUND z ERRORS VAS022 x AUDITED y MISMATCHES
CORRECTED z ERRORS Where: x = the number of VMBs audited y = the
number of mismatches found or corrected z = the number of transaction errors
with Meridian Mail
Action:
Severity: Minor.
VAS0023
SNMP trap: Yes
This message indicates that a mismatch was found by the VMB database
audit. This message appears when DATA_CORRECT = OFF in LD 17. The
Voice Mailbox data must be compared between the Meridian 1 and Meridian
Mail. The data can be corrected on either the Meridian 1 or Meridian Mail. The
MISMATCH FOUND OPRDAT: CUST x DN yyyy. The reduced format shown
below appears when package 243 is not enabled. VAS023 CUST x DN yyyy
Where: x = the customer number yyyy = the Directory Number with
mismatched Voice Mailbox data
Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2283 of 2360

VAS0024
This message indicates that a mismatch was found by the VMB database
audit, and corrected. This message appears when DATA_CORRECT = ON in
LD 17. The information is displayed in the following expanded format when
00000 MSG MB MISMATCH FOUND OPRDAT: CUST x DN yyyy. The
VAS024 CUST x DN yyyy Where: x = the customer number yyyy = the
Directory Number
Action:
Severity: Minor.
VAS0025
SNMP trap: Yes
This message indicates that the VMB database upload was invoked from LD
48. The information is displayed in the following expanded format when alarm
filtering is configured (package 243). VAS025 mm/dd/yy hr:min:sec 00000
MSG VMB UPLOAD INITIATED
Action:
Severity: Minor.
VAS0026
SNMP trap: Yes
This message indicates that the VMB upload completed. The information is
displayed in the following expanded format when alarm filtering is configured
(package 243). VAS026 mm/dd/yy hr:min:sec 00000 MSG VMB UPLOAD
COMPLETED OPRDAT: x UPLOADED y DELETED z ERRORS. The
VAS026 x UPLOADED y DELETED z ERRORS Where: x = the number of
VMBs uploaded y = the numbers of VMBs deleted on the Meridian 1 (note that
Meridian 1 Voice Mailboxes are deleted if a mailbox is not configured on
Meridian Mail z = the number of transaction errors with Meridian Mail
Action:
Severity: Minor.
VAS0027
SNMP trap: Yes
This message indicates that a VMB upload that was running was aborted. The
UPLOAD ABORTED OPRDAT: x UPLOADED y DELETED z ERRORS The
VAS027 x UPLOADED y DELETED z ERRORS Where: x = the number of
System Messages
Page 2284 of 2360

VMBs uploaded y = the numbers of VMBs deleted on the Meridian 1 (note that
Meridian 1 Voice Mailboxes are deleted if a mailbox is not configured on
Meridian Mail) z = the number of transaction errors with Meridian Mail
Action:
Severity: Minor.
VAS0028
SNMP trap: Yes
The Voice Mailbox on the Meridian 1 has been deleted during an upload
because a corresponding upload because the corresponding Voice Mailbox
does not exist on Meridian Mail. The information is displayed in the following
expanded format when alarm filtering is configured (package 243). VAS028
mm/dd/yy hr:min:sec 00000 MSG VMB DELETED OPRDAT: CUST x DN
yyyy. The reduced format shown below appears when package 243 is not
enabled. VAS028 CUST x DN yyyy Where: x = the customer number yyyy =
the Directory Number that had the voice mailbox deleted
Action:
Severity: Minor.
VAS0030
553-3001-411
SNMP trap: Yes
A Voice Mailbox operation failed. The reasons and actions are listed below.
The information is displayed in the following expanded format when alarm
filtering is configured (package 243). VAS030 mm/dd/yy hr:min:sec 00000
MSG VMB OPERATION FAILED OPRDAT: CUST x DN yyyy OPR zzzz
REASON aaaaa. The reduced format shown below appears when package
243 is not enabled. VAS030 CUST x DN yyyy OPR zzzz REASON aaaaa
Where: x = customer number yyyy = Directory Number zzzz = the operation
that failed (ADD, CHG, DEL, AUDT, UPLD) aaaaa = the failure reasons and
actions are listed below 1. GENERAL ERROR = A non-specific error has
occurred while processing the transaction. 2. VMB NOT FOUND = A Voice
Mailbox does not exist for the specified DN. If DATA_CORRECT = ON, the
user will be automatically created. 3. BAD DIGIT IN VMB DN = Meridian Mail
received a VMB DN with a bad digit. 4. COS NOT DEFINED = The Class of
Service specified is not configured for Meridian Mail. 5. BAD CHAR IN FNAME
= Meridian Mail received a bad character in the First Name IE. 6. BAD CHAR
IN LNAME = Meridian Mail received a bad character in the Last Name IE. 7.
BAD DIGIT IN 2ND DN = Meridian Mail received a bad digit in the Second DN
IE. 8. BAD DIGIT IN 3RD DN = Meridian Mail received a bad digit in the
Second DN IE. 9. ENTRY CORRUPT = More than one user was found with
the same mailbox number. This may indicate a database corruption error. 10.
DATA LOCKED = The Meridian 1 requested an operation that is currently in
use by Meridian Mail maintenance or administration. 11. INVALID VMB DN =
A mailbox cannot be configured for that DN because it has special significance
for Meridian mail. 12. INVALID 2ND DN = A mailbox cannot be configured for
Standard 15.00
January 2006
Page 2285 of 2360

that DN because it has special significance for Meridian mail. 13. INVALID
3RD DN = A mailbox cannot be configured for that DN because it has special
significance for Meridian mail. 14. MSG TIMEOUT = Meridian Mail did not
respond to the request within the timeout period, possibly due to heavy traffic
on the link. 5. NO COS FROM MMAIL = Meridian Mail did not provide a Class
of Service in the upload response message. 16. VMB UPLOAD FAILED = A
Voice Mailbox could not be built on the core, possibly due to low memory on
the Meridian 1. 17. NAME UPLOAD FAILED = A name could not be built on
the core, possibly due to low memory on the Meridian 1. 18. SEND REQUEST
FAILED = The request could not be sent to Meridian Mail for an unspecified
reason. 19. UNKNOWN = Unknown cause for failure.
Action: 1. Take the appropriate action for the SEER report on Meridian Mail. 2.
If it is off, you must create the VMB manually. 3. Re-enter the DN. 4. Either specify
a different Class of Service, or configure the desired Class of Service. 5. Modify
the name on the Meridian 1 so that it uses only characters supported by Meridian
Mail. 6. Modify the name on the Meridian 1 so that it uses only characters
supported by Meridian Mail. 7. Re-enter the DN to be sure the problem is not due
to a transmission error on the AML link. If this appears again, contact you
technical support personnel. 8. Re-enter the DN to be sure the problem is not due
to a transmission error on the AML link. If this appears again, contact you
technical support personnel. 9. Check for database corruption error. 10. If
necessary to perform the task immediately, remove the Meridian Mail user and
resend the request.11. Use another DN. 12. Use another DN.13. Use another
DN. 14. Resend the request. 15. Resend the upload request. 16. Resend the
upload request.17. Resend the upload request.18. Resend the upload request.
19. Contact your technical support group.
Severity: Info.
SNMP trap: Yes
System Messages
Page 2286 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2287 of 2360
VTN: Voice Port TN

Messages
VTN0001
The specified Voice port (Loop Shelf Card Unit) was acquired by an
application
on the Link#. The format of this message is: VTNxxxx Link# Loop# Shelf#
Card#
Unit# Hour Minute Second.
Action:
Severity: Info.
VTN0002
SNMP trap: No
The specified Voice port (Loop Shelf Card Unit) was de-acquired by an
application on the Link#.
Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2288 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2289 of 2360
WEB: Web Server

WEB messages are generated between the Succession CSE 1000 web
server, RPC Server and Call Server. WEB messages have three ranges,
depending on which element is generating the WEB message:
WEB0000 to WEB2099 - WEB Server
WEB3000 to WEB3999 - RPC
WEB4000 to WEB4999 - Call Server
Messages
WEB0001
A user with the same username is already logged in.

Action:
Severity: Minor.
WEB0002
SNMP trap: No
User not logged in, access to the web server is denied.

Action:
Severity: Minor.
WEB0003
SNMP trap: No
SNMP trap: No
User timed out.

Action:
Severity: Minor.
WEB0004
Send data to Call server failed.

Action:
Severity: Minor.
WEB0005
SNMP trap: No
Receive data from Call server failed.

Action:
Severity: Minor.
WEB0006
SNMP trap: No
Invalid username or password, please try again.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 2290 of 2360

WEB0007
The incoming CGI query string is invalid.

Action:
Severity: Minor.
WEB0008
SNMP trap: No
The XML file received is invalid or incomplete.

Severity: Minor.
WEB0009
SNMP trap: No
SNMP trap: No
Out of memory.
Action:
Severity: Minor.
WEB0010
User identification error. Requestor id and original login id are not the same.
Severity: Minor.
WEB0011
SNMP trap: No
Failure occurred in creating directory.

Action:
Severity: Minor.
WEB0012
SNMP trap: No
Failure occurred in creating file.

Action:
Severity: Minor.
WEB0013
SNMP trap: No
Error Text not found.

Severity: Minor.
WEB0014
SNMP trap: No
Failure occurred in file open.

Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2291 of 2360

WEB0015
Failure occurred in starting a new task.

Severity: Minor.
WEB0016
SNMP trap: No
Failure occurred in opening a directory.

Severity: Minor.
WEB0017
SNMP trap: No
Failure occurred in removing a file on the disk.

Severity: Minor.
WEB0018
SNMP trap: No
SNMP trap: No
File transfer is started.

Action:
Severity: Info.
WEB0019
Access to the web server is denied.

Action:
Severity: Info.
WEB0021
SNMP trap: No
SNMP trap: No
Unknown command.
Action:
Severity: Info.
WEB0022
Failure occurred in File copy.

Action:
Severity: Info.
WEB0023
SNMP trap: No
SNMP trap: No
Duplicated Node ID.

Action:
Severity: Info.
System Messages
Page 2292 of 2360

WEB0024
File does NOT exist.

Action:
Severity: Info.
WEB0025
SNMP trap: No
Failure occurred in reading file.

Action:
Severity: Info.
WEB0026
SNMP trap: No
User does not have authority to access this resource.

Action:
Severity: Info.
WEB0027
SNMP trap: No
Invalid HTM file.

Severity: Minor.
WEB0028
SNMP trap: No
Invalid bootp.tab file.

Severity: Major.
WEB0029
SNMP trap: No
SNMP trap: No
Invalid IP Address.
Action:
Severity: Info.
WEB0030
The login page has been inactive for too long, or an invalid browser action was
used, such as Refresh or Back. Please enter the web server IP address again,
and relogin.
Action:
Severity: Info.
WEB0031
SNMP trap: No
Session ID is already in use, please enter the web server IP address again and
relogin.
Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2293 of 2360

WEB1000
Destination IP : %s Node ID : %d\n\%s\n

Action:
Severity: Info.
WEB2501
SNMP trap: No
Error FTPing the BOOTP.TAB file from the leader.

Action:
Severity: Minor.
WEB2502
SNMP trap: No
Error FTPing the CONFIG.INI file from the leader.

Action:
Severity: Minor.
WEB2503
SNMP trap: No
Initial RPC failed. The leader could be presently down, or if the leader is an
ITG-P card it may not be running IPL 3.x software.
Action:
Severity: Minor.
WEB2504
SNMP trap: No
Node files for this node already exist on the Call Server.
Action:
Severity: Minor.
WEB2510
SNMP trap: No
Error opening the BOOTP.TAB file.

Action:
Severity: Minor.
WEB2511
SNMP trap: No
Error opening the CONFIG.INI file.

Action:
Severity: Minor.
WEB2512
SNMP trap: No
Error opening the CFGDFLT.INI file.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 2294 of 2360

WEB2520
Memory allocation error.

Action:
Severity: Minor.
WEB2521
SNMP trap: No
Not enough memory allocated to read CONFIG.INI file.

Action:
Severity: Minor.
WEB2522
SNMP trap: No
Not enough memory allocated for Card IP section parameters.

Action:
Severity: Minor.
WEB2523
SNMP trap: No
Not enough memory allocated for Application Server section parameters.

Action:
Severity: Minor.
WEB2530
SNMP trap: No
SNMP trap: No
Unknown leader type.

Action:
Severity: Minor.
WEB2531
Unknown card type or card role.

Action:
Severity: Minor.
WEB2532
SNMP trap: No
Empty node ID in BOOTP.TAB file.

Action:
Severity: Minor.
WEB2533
SNMP trap: No
Invalid node ID in BOOTP.TAB file.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2295 of 2360

WEB2534
Empty call server IP in CONFIG.INI file.

Action:
Severity: Minor.
WEB2535
SNMP trap: No
Call server IP in CONFIG.INI file of the leader, is not the same as the active
call server IP.
Action:
Severity: Minor.
WEB2536
SNMP trap: No
No valid elements in BOOTP.TAB file.

Action:
Severity: Minor.
WEB2537
SNMP trap: No
BOOTP.TAB file is too long.

Action:
Severity: Minor.
WEB2538
SNMP trap: No
CONFIG.INI file is too long.

Action:
Severity: Minor.
WEB2539
SNMP trap: No
Too many errors during retrieve and upgrade.

Action:
Severity: Minor.
WEB2540
SNMP trap: No
All elements in BOOTP.TAB file are of unknown type or role.

Action:
Severity: Minor.
WEB3001
SNMP trap: No
SNMP trap: No
RPC error
Action:
Severity: Minor.
System Messages
Page 2296 of 2360

WEB3002
Invalid server IP address.

Action:
Severity: Minor.
WEB3003
SNMP trap: No
SNMP trap: No
SNMP trap: No
SNMP trap: No
Initial RPC failed.

Action:
Severity: Minor.
WEB3004
RPC call timed out.

Action:
Severity: Minor.
WEB3005
Invalid parameters.
Action:
Severity: Minor.
WEB3006
The file does not exists on server.

Action:
Severity: Minor.
WEB3100
SNMP trap: No
RPC error issued by Transaction Server.

Action:
Severity: Minor.
WEB3101
SNMP trap: No
SNMP trap: No
Input XML file overflow.

Action:
Severity: Minor.
WEB3120
Set single node configure files failed because of version mismatch.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2297 of 2360

WEB3140
Upgrade bootp.tab file failed.

Action:
Severity: Minor.
WEB3141
SNMP trap: No
Upgrade config.ini file failed.

Action:
Severity: Minor.
WEB3142
SNMP trap: No
Upgrade both config and bootp files failed.

Action:
Severity: Minor.
WEB3150
SNMP trap: No
CS could not open the node directory.

Action:
Severity: Minor.
WEB3151
SNMP trap: No
CS could not open the bootp file.

Action:
Severity: Minor.
WEB3152
SNMP trap: No
The bootp file saved on CS is invalid.

Action:
Severity: Minor.
WEB3153
SNMP trap: No
There are too many bootp files on Call Server.

Action:
Severity: Minor.
WEB3160
SNMP trap: No
Function return error for general command.

Action:
Severity: Minor.
SNMP trap: No
System Messages
Page 2298 of 2360

WEB3170
Could not get login name and password of Call Server.

Action:
Severity: Minor.
WEB3180
SNMP trap: No
Could not get IP address of Signaling Server.

Action:
Severity: Minor.
WEB3181
SNMP trap: No
Could not get login name and password of Signaling Server.

Action:
Severity: Minor.
WEB3182
SNMP trap: No
Could not ftp the file to Call Server.

Action:
Severity: Minor.
WEB3190
SNMP trap: No
Could not open OM directory on destination element.

Action:
Severity: Minor.
WEB3191
SNMP trap: No
Could not open OM file on destination element

Action:
Severity: Minor.
WEB3203
SNMP trap: No
New config file is invalid.

Action:
Severity: Minor.
WEB3204
SNMP trap: No
New bootp file is invalid.

Action:
Severity: Minor.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2299 of 2360

WEB3210
Destination element can't open given file.

Action:
Severity: Minor.
WEB4001
SNMP trap: No
XML output buffer overflowed.

Action:
Severity: Info.
WEB4002
SNMP trap: No
Prompt Information is missing.

Action:
Severity: Info.
WEB4003
SNMP trap: No
Error occurs when the Transaction Server sends message to Call Server.
Action:
Severity: Info.
WEB4004
SNMP trap: No
Memory allocation failed.

Action:
Severity: Info.
WEB4005
SNMP trap: No
Data updated, please refresh.

Action:
Severity: Info.
WEB4006
SNMP trap: No
Please check current printout first.

Action:
Severity: Info.
WEB4007
SNMP trap: No
Input XML format incorrect.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2300 of 2360

WEB4008
No idle TTY channel available.

Action:
Severity: Info.
WEB4009
SNMP trap: No
Can't load this overlay in the Call Server.

Action:
Severity: Info.
WEB4010
SNMP trap: No
Time out waiting for message response from the Call Server.
Action:
Severity: Info.
WEB4011
SNMP trap: No
Message receiving error in Transaction Server.

Action:
Severity: Info.
WEB4012
SNMP trap: No
Message Queue removal failed in the Transaction Server.

Action:
Severity: Info.
WEB4013
SNMP trap: No
Missing Login Name in input XML file.

Action:
Severity: Info.
WEB4014
SNMP trap: No
Missing Overlay Number in input mol file.

Action:
Severity: Info.
WEB4015
SNMP trap: No
Missing Password in input mol file.

Action:
Severity: Info.
553-3001-411
Standard 15.00
January 2006
SNMP trap: No
Page 2301 of 2360

WEB4016
Web Client can't access current overlay.

Action:
Severity: Info.
WEB4017
SNMP trap: No
Unknown Transaction Type.

Action:
Severity: Info.
WEB4018
SNMP trap: No
SNMP trap: No
Web Client Login failed.

Action:
Severity: Info.
WEB4019
Output content from the Call Server is too large.

Action:
Severity: Info.
WEB4020
SNMP trap: No
Output tag from the Call Server is too large.

Action:
Severity: Info.
WEB4021
SNMP trap: No
Transaction Server can't create edd output xml file.

Action:
Severity: Info.
SNMP trap: No
System Messages
Page 2302 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2303 of 2360
XCT: Conference, Tone and Digit Switch,

and Multifrequency
The XCT card provides conference, Tone and Digit Switch (TDS) and
Multifrequency Sender (MFS) circuits. XCT messages indicate hardware
status and problems.
Messages
XCT0001 loop x
The Conference/TDS/MFS Card failed the self test. Where: x = self test result
message.
Action: If the test fails a second time, replace the card.
Severity: Critical.
XCT0002 loop x
SNMP trap: Yes
The Conference/TDS/MFS Card failed the Input/Output test. Where: x = I/O

result message.
Action: If the test fails a second time, replace the card.
Severity: Critical.
XCT0003 loop
SNMP trap: Yes
Failed download process to the Conference/TDS/MFS Card. This may

indicate communication trouble or checksum problems or the card is busy.
Severity: Critical.
XCT0004 loop x y
SNMP trap: Yes
The CPU received a message invalid to the current state of the

Conference/TDS/MFS Card. Where: x = message type received; y = the state
of the card.
Action:
Severity: Critical.
XCT0005 loop x
SNMP trap: Yes
The CPU received an unrecognized message from the Conference/ TDS/MFS

Card. Where: x = message received.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2304 of 2360

XCT0006 loop x
The Conference/TDS/MFS Card received an illegal message from the CPU.

Where: x = message received.
Action:
Severity: Critical.
XCT0007 loop x
SNMP trap: Yes
Time-out waiting for response from the Conference/TDS/MFS Card. Where: x

= the state of the XCT.
Action:
Severity: Critical.
XCT0008 loop n
SNMP trap: Yes
Failed download process to the Conference/TDS/MFS Card because the CPU

could not write to the card. This may indicate a removed card or hardware
fault. Where: n = the FCAD table entry number which failed to download. If n
= 0, the failure occurred downloading system parameters.
Action:
Severity: Critical.
XCT0009 loop tn
SNMP trap: Yes
The Conference/TDS/MFS Card sent a message to the CPU with an invalid

Terminal Number.
Action:
Severity: Critical.
XCT0010 g
SNMP trap: Yes
The CPU was unable to obtain a Call Register to perform a timing task. Where:
g = Group loop number.
Action:
Severity: Critical.
XCT0011 loop r
SNMP trap: Yes
The Conference/TDS/MFS Card has been reset. Where: r = hardware reset

message.
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2305 of 2360

XCT0100 loop x
The Conference/TDS/MFS Card failed to respond to a read or write. Where: x

= outgoing message.
Action:
Severity: Critical.
XCT0101 loop x
SNMP trap: Yes
The Conference/TDS/MFS Card is disabled and needs download. This occurs

when the two loops on the card are enabled separately. Where: x = "XCT
DNLD NEEDED USED ENLX CMD"
Action: Enable the card using the ENLX command in LD 34, LD 38 or LD 46.
Severity: Critical.
XCT0102 loop x
SNMP trap: Yes
The conference loop on Conference/TDS/MFS Card is in use. The Time Slot

Memory (TSM) was not tested. Where: x = "XCT IN USE NO TSM TEST"
Action: Wait until the loop is idle.
Severity: Critical.
XCT0103
SNMP trap: Yes
Downloading of DTR or XTD parameters to slot 0 failed. In LD 34 disabled and

reenable the slot using commands DISX 0 and ENLX 0.
Severity: Critical.
XCT0104
SNMP trap: Yes
Downloading of the tone parameters for the TDS on slot 0 has failed. In LD 34
disable and reenable the slot using commands DISX 0 and ENLX 0.
Action: If this message appears repeatedly or is associated with a system
problem, contact your technical support group.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2306 of 2360
553-3001-411
Standard 15.00
January 2006
Page 2307 of 2360
XMI: Network to Controller Message

Interface
The XMI messages indicate problems with the communication between the
NT8D04 Network Card and the NT8D01 Controller card.
Messages
XMI0000 aaaa
Message "aaaa" received from a Network Card (NT8D04). The possible

messages are: 1. PLL UNLOCK EVENT. The Network card lost synch with the
system clock. 2. MSG FROM SHELF x: XPEC ERROR 0001. This error is
usually self correcting. If may indicate a double timeslot problem or invalid call
teardown. 3. TN READ UNBLOCKED: CNT=x. A number of SSD messages
were sent to the PS card but not acknowledged. In order to prevent the locking
of the message path, the Network card assumed the message was received.
4. Any of the following three messages: XNET POLLING FAILURE ON PORT
x RSIG LINK LOST ON PORT #x - REINITIALIZED R71 DISASTER;
CANNOT ALIGN TRANSCEIVERS. These messages indicate that the
Controller is not responding to the Network card polling messages.
Action: 1. a. Ignore if message occur when clocks are switched.
b. If it occurs periodically, switch the clocks.
c. If it occurs often, replace Network card or clocks. Random XMI000 messages
may be generated if excessive Electrostatic Discharges (ESD) are allowed to
enter the system. These messages may be safely ignored. Refer to General
Maintenance Information (553-3001-500) for ESD avoidance practices.
2. a If message occurs rarely, ignore it.
b. If it occurs often, replace the Controller.
3. a. If message occurs rarely, ignore it.
b. If it occurs often, replace the PS or Network card.
4. a. Check cabling between Controller and Network.
b. Replace the Controller.
c. Replace the Network. In X11 Release 15 and 16, "FRw APx SQy TPz" is output
before the text, where "w" is the loop number. This data is not output in X11
Release 17 and later. Messages without text indicate that the Network or
Controller card have requested software download.
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2308 of 2360

XMI0002 XFIL 1
Main fiber interface (MFI) local is operational.

Action:
Severity: Critical.
XMI0002 XFIR 2
SNMP trap: Yes
Expansion fiber interface (EFI) remote is operational in first expansion cabinet.

Action:
Severity: Critical.
XMI0002 XFIR 3
SNMP trap: Yes
Expansion fiber interface (EFI) remote is operational in second expansion

cabinet.
Action:
Severity: Critical.
XMI0002 l s c
SNMP trap: Yes
Card polling re-established.

Action:
Severity: Critical.
XMI0003 l s ts
SNMP trap: Yes
Continuity failed on timeslot ts.

Action:
Severity: Critical.
XMI0004 loop
SNMP trap: Yes
Loop generated too many XMI messages. Output of XMI000 has been
stopped.
Action:
Severity: Critical.
XMI0005 L A S T t
SNMP trap: Yes
No message registers available in the idle queue. The printing this message
is disabled for one hour. Where: L = Loop or superloop number A = Application
number for this message S = Sequence field for this message T = Type of
message t = time of this message: hh:mm:ss dd/mm/yy format
Action:
Severity: Critical.
553-3001-411
Standard 15.00
January 2006
SNMP trap: Yes
Page 2309 of 2360

XMI0006 loop
Five or more write attempts to Network Card L failed.

Action: Check the Network Card status.
Severity: Critical.
XMI0007
SNMP trap: Yes
Card type does not match the data base.

Action:
Severity: Critical.
XMI0008
SNMP trap: Yes
Card is not defined in the data base.

Action:
Severity: Minor.
XMI0100
SNMP trap: Yes
The loop specified in the query request is invalid; that is, it is not a superloop,
nor is it XI_LOOP_NONE.
Action:
Severity: Info.
XMI0101
SNMP trap: Yes
Trying to read/write to a disabled XNET/non-XNET loop.

Action:
Severity: Critical.
XMI0103
SNMP trap: Yes
The number of TNs created has exceeded the number of TNs allowed.
Action:
Severity: Critical.
XMI0110
SNMP trap: Yes
In LD 11 for the prompt CTYP (DLC Card Type), the configured value is XDLC,
but the card plugged in is a EDLC card.
Action:
Severity: Critical.
XMI0111
SNMP trap: Yes
In LD 11 for the prompt CTYP (DLC Card Type), the configured value is EDLC,
but the card plugged in is an EDLC card.
Action:
Severity: Critical.
SNMP trap: Yes
System Messages
Page 2310 of 2360
553-3001-411
Standard 15.00
January 2006
2358
HEX
Page 2311 of 2360
Faceplate LED codes

NT8D01 Controller faceplate codes
The NT8D01 Controller faceplate has a two digit hexadecimal display. The
display has two modes of operation: normal operation and power on reset
self-test.
Note: For information on hexadecimal conversion of terminal number
formats see Appendix A: Hexadecimal conversion on page 2359.
Normal operation
During normal operation the display alternately shows
1
The Controller number (1-95) in hexadecimal.
The port on which the Controller clock is tracking. The tracking is

indicated by the decimal points before and after the digit. The possible
tracking modes are:
C0 - Controller tracking to the network connected to port 0.
CF - Controller not tracking any network.
See also LD 30 for the following commands:

CPED: clear Peripheral Controller maintenance displays
RPED: read Peripheral Controller maintenance displays
System Messages
Page 2312 of 2360
Faceplate LED codes
Self-tests
During the self-tests, the display quickly shows the self-tests listed below. If
a test fails, the display shows the number of the failed test for 0.5 seconds
before continuing the remaining tests. The self-test sequence is repeated until
all tests pass.
553-3001-411
Standard 15.00
January 2006
Faceplate LED codes
Page 2313 of 2360
Table 2
Controller self-test codes
Code
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
11
12
13
14
15
16
17
18
19
1A
1B
1C
1D
1E
1F
20
21
22
23
24
25
26
27
EE
Definition
A31 #1 external buffer test.
A31 #1 internal context memory test, phase A.
A31 #1 internal context memory test, phase B.
A31 #1 internal TXVM memory test.
A31 #1 configuration memory test.
A31 #1 external FIFO test.
A31 #2 external buffer test.
A31 #2 internal context memory test, phase A.
A31 #2 internal context memory test, phase B.
A31 #2 internal TXVM memory test.
A31 #2 configuration memory test.
A31 #2 external FIFO test.
peripheral side W72 loopback test using A31 #1.
peripheral side W72 loopback test using A31 #2.
R72 #1 N-P switching control memory test.
R72 #1 320 x 8 NIVD buffer test.
R72 #1 N-P quiet-code register test.
R72 #1 P-N switching control memory test.
R72 #1 640 x 8 XIVD buffer test.
R72 #1 640 x 8 XIVD loopback buffer test.
R72 #1 P-N quiet-code register test.
R71 #1 register test.
R71 #1 continuity test, peripheral side.
R71 #1 continuity test, network side.
R71 #1 simulation packet transmission test.
DUART port A self-test.
DUART port B self-test.
R72 #2 N-P switching control memory test.
R72 #2 320 x 8 NIVD buffer test.
R72 #2 N-P quiet-code register test.
R72 #2 P-N switching control memory test.
R72 #2 640 x 8 XIVD buffer test.
R72 #2 640 x 8 XIVD loopback buffer test.
R72 #2 P-N quiet-code register test.
R71 #2 register test.
R71 #2 continuity test, peripheral side.
R71 #2 continuity test, network side.
R71 #2 simulation packet transmission test.
Bus error, exception errors, etc.
System Messages
Page 2314 of 2360
Faceplate LED codes
Mass Storage Interface (MSI) faceplate codes

The Mass Storage Interface (MSI) card is located on the CPU shelf of systems
equipped with disk drives. Table applies to QPC584E and earlier versions. If
the faceplate cable is disconnected, the MSI displays AF for about 7 seconds
then flashes 55 followed by 10, the idle state. IOD050 and OVL005
messages are output. The meaning of the code depends on whether the display
is alternating, counting, flashing or steady.
Table 3
Mass Storage Interface (MSI) Faceplate Codes (Part 1 of 6)
Display Status
Code
Meaning
Alternating
Ax
Counting
00-50
During the restore command in LD 43, the MSI display counts

from 0 to 32 hex as the floppies are being copied to hard disk.
Each count corresponds to a block of data being transferred. It
also counts down when a second copy of the floppy is made on
the hard disk.
55-00
During the running of LD 37 I/O Diagnostic commands:
The MSI is reading disk records.
During execution of the MSI 0 command, the display shows a

pattern counting down from 55 to 00 on two separate occasions.
Each count occurs in approximately 1 second intervals. This
simulates the fast forward and reverse tape motion which takes
about 85 seconds each.
During execution of the MSI RW 0 command, after the A1-AF
pattern indicating records are being read, there is an occasional
'8B' indicating records are being written. When writing to a floppy
with the write protect tab on, the display flashes 97 and IOD075 is
output.
Flashing
Flashing
553-3001-411
00
Hard disk or floppy disk is not formatted (QPC584A to D). For

QPC584E or later, 00 indicates missing information from disk.
01
No Index/Sector signal (hardware/disk error).
02
No seek complete on the floppy disk (hardware/disk error).
03
Write fault.
Standard 15.00
January 2006
Faceplate LED codes
Page 2315 of 2360
Table 3
Display Status
Code
Meaning
04
Addressed disk drive is not ready. Check that the floppy disks are
in place and that they are properly seated. Be sure that the floppy
disks are not upside down or backwards in their drives.
05
Addressed disk drive is not selected. Check that the drive is

present. and the cables to the controller are correct. If the MSU
has just been powered on, the MSI must be initialized. This is
done by turning the MSI switch from ENL to DIS and back to ENL.
06
No Track Zero found (hardware error).
07
Multiple Drives selected (hardware error).
0D
A command is still executing and a new command is issued.
10
Check Sum Error (hardware/medium error).
11
Read Error (medium error).
12
No address mark found in ID field on disk (medium error).
13
No address mark found in data field on disk (medium error).
14
No record found (disks) (medium error).
15
Seek error (hardware error).
1A
Too many parameters (illegal request).
20
Invalid Command (illegal request).
21
Illegal parameters were sent to the controller. For QPC584E; 21

indicates invalid address on disk.
22
Switching from hard disk to floppy disk for normal operation.
23
Disk capacity overflow (illegal request).
24
Illegal field in command (illegal request).
25
Invalid drive selection (illegal request).
26
Invalid field in parameter list (illegal request).
27
Write protected (also see 97).
28
Disk changed.
System Messages
Page 2316 of 2360
Faceplate LED codes
Table 3
Display Status
Flashing
553-3001-411
Code
Meaning
29
Power on reset occurred.
2A
Drive parameters changed.
2B
Floppy disk controller error.
31
Drive format is corrupted (medium error).
33
Switching from floppy disk to hard disk for normal operation.
40
RAM failure (hardware error).
41
ECC diagnostic failure (hardware error).
91
Uncorrectable error in data field of diskette. Replace the floppy

disk that was being accessed when the error occurred.
92
Controller did not detect the address mark in the Identification (ID)
field.
94
Controller could not find the requested record.
95
Seek error. The Controller could not find the specified track.
97
Attempting to write on a write-protected disk. Floppy disk B has a

write-protect tab.
BA
Write error.
BC
A diskette write error occurred during the write of a record.
BD
Logical Record Count (LRC) mismatch during disk write. The LRC
calculated by the MSI does not agree with the LRC sent by the
system.
BE
Record Number (RN) mismatch during disk write. The current RN

in the MSI does not agree with the RN sent by the system.
BF
Illegal Record Type (RT) during disk write. The record requested
by SL-1 to be written onto diskette is neither a configuration record
(RT8) nor data record (RT7).
CA
Beginning to copy data from floppy disk A to hard disk.
CA
Beginning to copy data from floppy disk B to hard disk.
Standard 15.00
January 2006
Faceplate LED codes
Page 2317 of 2360
Table 3
Display Status
Flashing
Code
Meaning
CC
Copy (restore) from floppy disk to hard disk is complete.
CD
Hard disk has been positioned to shipping zone.
D0
Attempting to do a data base back up when there are no data

records on the hard disk. Do a data dump to the hard disk before
doing the backup to the floppy disks.
D1
Attempting to do a data base back up when MSI switch settings

have not been set for operation from a hard disk.
D6
Read error of hard disk private sector.
DD
Data dump (back-up) to floppy disk B is beginning.
DC
Data dump (back-up) to floppy disk is complete.
E1
Cartridge time-out because MSI data cartridge is not present.

Install a data cartridge.
E2
Illegal MSI data cartridge. Check that the data cartridge is properly
installed (proper orientation with all pins inserted), or replace data
cartridge.
E3
Disk ID on floppy does not match ID in data cartridge. Replace

floppy or cartridge.
E4
Mismatch in System Version Number (SVN). SVN on disk does

not match SVN in MSI data cartridge. Replace floppy disks or
cartridge. SVN indicates the SL-1 machine type. For example the
SVN for SL-1 XN it is 911.
E5
Mismatch in System Issue Number (SIN). SIN release number on

disk does not match SIN release number in MSI data cartridge.
Replace floppy disks or data cartridge.
SIN consists of two parts: a release number and an issue number.
The release number is the most significant (decimal) digit of the
SIN and the issue number is the lease two significant digits. For
example, a SIN of 855 means a release number of 8 and an issue
number of 55. The MSI only compares the release portion of the
SIN.
System Messages
Page 2318 of 2360
Faceplate LED codes
Table 3
Display Status
Flashing
Steady
553-3001-411
Code
Meaning
E6
Diskette read error encountered during attempted read of the

private sector. Check that the floppy disk is present.
E7
Diskette write error encountered during attempted write to the

private sector. Check that the write-protect tab has been removed
from the floppy disk in drive B.
E8
Illegal attempt to write onto floppy disk A. This is not allowed.
E9
Illegal attempt to write to track 1 or track 2 space on the hard disk.

This is not allowed.
EA
Illegal value was written into track register. The value written was
not 1, 2, 4 or 8.
EC
Conversion error in computing logical sector number for hard disk.
EE
Maximum record number was exceeded during a database write

to disk.
FA
Fault in floppy drive A. Self-test failed. Check cabling to drive A,

check drive DIP switches or replace drive.
FB
Fault in floppy drive B. Self-test failed. If code 97 was displayed

before FB, the write-protect tab is in place and the write test could
not be completed. Remove the write-protect tab on floppy disk B.
Otherwise, check cabling to drive B, check drive DIP switches or
replace drive.
FC
Fault in hard disk drive C. Self-test failed. Check cabling to drive

C, check drive DIP switches or replace drive.
FD
Wrong floppy disks in drives.
FE
Read error.
FF
Floppy disk is in the wrong drive. Floppy disk A is in drive B and

floppy disk B is in drive A. Drive A must contain a Track 1 floppy,
Drive B a Track 3 floppy.
00
Mass Storage Interface (MSI) power-up completed.
10
Mass Storage Interface (MSI) in idle state.
Standard 15.00
January 2006
Faceplate LED codes
Page 2319 of 2360
Table 3
Display Status
Code
Meaning
2F
Unknown command from CPU.
81-8F
Codes 81 to 8F indicate the MSI is simulating tape functions.

81 = Slow forward with Inter-record Gap (IRG)
82 = Slow reverse with Inter-record Gap (IRG)
83 = Fast forward with Inter-record Gap (IRG)
84 = Fast reverse with Inter-record Gap (IRG)
85 = Rewind
89 = Set timer (to a maximum of 64 ms)
8A = Read disk
8B = Write disk
8C = Diagnostic write
8D = Diagnostic fast forward
8E = Diagnostic fast reverse
8F = Unrecognized command
Steady
A1
MSI has completed reading a record from disk and is transferring

the data to the CPU.
A2
MSI has completed writing a record from its write buffer onto a
diskette.
AD
during restore and backup for hard disk, the Mass Storage
Interface (MSI) is waiting for the disk controller to indicate that it
has completed execution of the command.
AE
MSI has sent a status request to the Disk Controller.
AF
MSI has issued a command to the Disk Controller.
C2
Copying track 1 to track 2 on hard disk.
C4
Copying track 3 to track 4 on hard disk.
FE
Read error.
FF

floppy disk B is in drive A. Drive A must contain a Track 1 floppy,
Drive B a Track 3 floppy.
System Messages
Page 2320 of 2360
Faceplate LED codes
Floppy Drive Interface (FDI) pack faceplate codes

The codes listed in this table appear on the Floppy Disk Interface (FDI) circuit
pack located on the CPU shelf of systems equipped with disk drives. The
meaning of the code depends on whether the display is alternating, counting,
flashing or steady.
Table 4
Floppy Drive Interface (FDI) Pack Faceplate Codes (Part 1 of 5)
Display Status
Code
Meaning
Alternating
A1-70
FDI is reading disk records.
Counting
55-00
Display counts down in hexadecimal from 55 to 00 in

approximately 1 second intervals. This display will run through two
cycles. This is to simulate fast-forward and fast-reverse tape
motion during diagnostics.
Flashing
44
Sanity timer has timed-out. Extraordinary situation.
55
Floppy Disk Unit (FDU) or CPU not responding. The FDU may
have no power. Check FDI to FDU cable. This message is also
displayed if the CPU does not respond to the FDI after giving it a
command.
60
Missing address mark. The Floppy Disk Controller (FDC) cannot

detect the ID address mark after encountering the index hole
twice. Check the cable or replace the diskette (disk error).
61
Not able to write. The Floppy Disk Controller (FDC) has detected a
write protect signal from the addressed drive. Remove the write
protect tab on floppy disk B and try again.
62
No data. Floppy Disk Controller (FDC) cannot find the sector

specified (disk error).
63
Overrun. Floppy Disk Controller (FDC) is not being serviced fast

enough by the CPU (FDC/hardware error).
64
Data error. A checksum error in the ID field or the data field was
detected (disk error).
65
End of cylinder. An attempt has been made to access beyond the

final sector of a cylinder (FDC/hardware error).
553-3001-411
Standard 15.00
January 2006
Faceplate LED codes
Page 2321 of 2360
Table 4
Display Status
Code
Meaning
Flashing
66
Missing address mark in data field. In conjunction with (60), this

specifies the missing address mark to have occurred in a data
field (disk error).
67
Bad cylinder. The cylinder address as read from the disk does not
match the cylinder address loaded into the Floppy Disk Controller
(FDC), and the disk cylinder address equals FFH (FDC/hardware
error).
68
Wrong cylinder. The cylinder address as read from the disk does
not match the cylinder address loaded into the Floppy Disk (FDC)
(FDC/hardware error).
69
Data error in data field. A checksum error was detected in the data
field (disk error).
6A
Control mark. A sector with a deleted data address mark was

encountered (disk error).
72
Abnormal termination. Command execution started but not be

successfully completed.
74
Interrupt module error. An error was detected during execution of

interrupt module.
75
Read2s module error.
76
Write2s module error.
77
Initctrl module error.
78
Command interface error. Incorrect hand shaking between Floppy

Disk Controller (FDC) and CPU during attempt to load command
block.
79
Result interface error. Incorrect handshaking between Floppy Disk

Controller (FDC) and CPU during attempt to read result bytes.
7A
RXRSLT module error.
7C
Addressed drive not ready.
7D
Invalid hard disk operation attempted.
System Messages
Page 2322 of 2360
Faceplate LED codes
Table 4
Display Status
Flashing
553-3001-411
Code
Meaning
7E
Logical sector number out-of-range.
BA
Write error.
BC
A disk write error occurred during the write of a tape record.
BD
Checksum mismatch during disk write. The checksum calculated

by the MSI does not agree with the checksum sent by the system.
BE
Record Number (RN) mismatch during disk write. The current RN

in the MSI does not agree with the RN sent by the system.
BF
System has requested that a record be written to a disk. The

record is neither a configuration record nor a data record.
E1
Cartridge timeout because MSI data cartridge is not present.

Install a data cartridge.
E2
Illegal MSI data cartridge. Check that the data cartridge is properly
installed (proper orientation with all pins inserted), or replace data
cartridge.
E3
Disk ID on floppy disk does not match disk ID in data cartridge.

E4
Mismatch in System Version Number (SVN). SVN on disk does

not match SVN in MSI data cartridge. Replace floppy disks or
cartridge.
E5
Mismatch in System Issue Number (SIN). SIN release number on

disk does not match SIN release number in MSI data cartridge.
E6
Diskette read error encountered during attempted read of the

private sector. Check that the floppy disk is present.
E7
Diskette write error encountered during attempted write to the

private sector. Check that the write-protect tab has been removed
from the floppy disk in drive B.
E8
Illegal attempt to write onto floppy disk A. This process is not

allowed.
Standard 15.00
January 2006
Faceplate LED codes
Page 2323 of 2360
Table 4
Display Status
Flashing
Steady
Code
Meaning
EA
Illegal value was written into track register. The value written was
not 1, 2, 4 or 8.
EE
Maximum record number was exceeded during database write to

disk.
FA
Fault in floppy drive A. Self-test failed. Check cabling to drive A or

replace drive.
FB
Fault in floppy drive B. Self-test failed. If code 61 was displayed

before FB, the write-protect tab is in place and the write test could
not be completed. Remove the write-protect tab on floppy disk B.
Otherwise, check cabling to drive B or replace drive.
FD
Wrong floppy disks in drives.
FE
Read error.
FF

floppy disk B is in drive A. Insert disks in the proper drives.
00
Floppy Disk Interface (FDI) power-up completed.
10
Floppy Disk Interface (FDI) in idle state.
2F
Unknown command from CPU.
70
Invalid command. Floppy Disk Controller (FDC) has received an

unrecognizable command. This code also signals the successful
completion of all asynchronous processing.
71
Asynchronous command complete.
73
Ready status change.
7B
Synchronous command complete.
81-8F
Codes 81 to 8F indicate the FDI is simulating tape functions.
System Messages
Page 2324 of 2360
Faceplate LED codes
Table 4
Display Status
Code
Meaning
81 = Slow forward with Inter-record Gap (IRG)
82 = Slow reverse with Inter-record Gap (IRG)
83 = Fast forward with Inter-record Gap (IRG)
84 = Fast reverse with Inter-record Gap (IRG)
85 = Rewind
89 = Set timer (to a maximum of 64 ms)
8A = Read disk
8B = Write disk
8C = Diagnostic write
8D = Diagnostic fast forward
8E = Diagnostic fast reverse
8F = Unrecognized command
Steady
553-3001-411
A1
Floppy Disk Interface (FDI) has completed reading a record from a

disk into its read buffer and is transferring the data to the CPU.
A2
Floppy Disk Interface (FDI) has completed writing a record from its
write buffer onto a disk.
CC
Data transfer from cartridge is complete.
Standard 15.00
January 2006
Faceplate LED codes
Page 2325 of 2360
Maintenance Display Codes

The maintenance display indicates status and error conditions. The display is
located on the Interface or Miscellaneous card in the CPU.
Note: Small Systems and Succession 1000 systems do not have a
maintenance display, the HEX codes are displayed on the maintenance
terminal during Initialization or Sysload.
Note: For Option 81 systems, the maintenance display on the NT6D66
Call Processor (CP) Card shows two lines of information, with up to 16
characters per each line. The hexadecimal code and its definition are
shown on the display.
Each new code shown on a maintenance display overwrites the one before it.
However:
All codes received on common equipment displays are recorded.

You can review them by printing the History File (if equipped).
The most recent 16 codes displayed on a controller card stay in

memory. You can review them and reset the counter through the
Network and Signaling Diagnostic (LD 30).
For Option 51C, 61C, 81, and 81C, the most recent 64 displays on a
CP card stay in memory. You can review the displays on the active
CP card through the Core Common Equipment Diagnostic (LD 135).
Table 5 on page 2325 lists the cards with maintenance displays and the type
of information indicated by the codes on each card.
Table 5
Circuit cards with maintenance displays (Part 1 of 2)
Display indication
(for all related cards)
System options
Circuit card
51, 61, 71
QPC580 CPU Interface Card
51C, 61C, 81, 81C
NT6D66, NT9D19, NT5D10,

NT5D03 Call Processor Card
Common equipment
hardware faults
System Messages
Page 2326 of 2360
Faceplate LED codes
Table 5
Circuit cards with maintenance displays (Part 2 of 2)
System options
Circuit card
51, 61
QPC742 Floppy Disk

Interface Card
51, 61, 71
QPC584 Mass Storage

Interface Card
61C (NT9D11), 81
NT6D63 I/O Processor Card

(release 19 and 20)
51C, 61C, 81, 81C
NT5D61 IODU/C Card

(release 23 and later)
NT5D20 IOP/CMDU Card
release 21 and later)
51, 51C, 61, 61C, 71, 81,

81C
NT8D01 Controller Card
51, 51C, 61, 61C, 71, 81,

81C
NT7R52 Remote Carrier

Interface Card
553-3001-411
Standard 15.00
NT1P62 Fibre Controller
January 2006
Display indication
(for all related cards)
Faults on the disk drive unit
Faults on the disk drive
interface card
During normal operation,

display shows self-test codes
and port number on which
Controller Clock is tracking
During normal operation,
display shows self-test codes
and port number on which
Controller Clock is tracking
Faceplate LED codes
Page 2327 of 2360
System element abbreviations

Some error conditions indicate hardware faults. In these cases, try to isolate
the fault by replacing the cards in the order listed. The following
abbreviations are used:
CIMControl Interface and Memory
CMAChangeover and Memory Arbitrator
CPUCentral Processing Unit
CT Control and Timing
FN Function
IF Interface
MEMMemory
MFSMulti frequency Sender
MISCMiscellaneous
PS Peripheral Signaling
ROMRead Only Memory
SDI Serial Data Interface
TDSTone and Digit Switch
TT Tone Transmitter
TD Tone Detector
PRI Primary Rate Interface
MISPMeridian ISDN Signalling Processor
Note: The following 3 digit Hex codes do not apply to Option 11.
System Messages
Page 2328 of 2360
Faceplate LED codes
Maintenance display codes (Part 1 of 18)

Code
01
Description
Manual interrupt or Power Monitor interrupt.
For system Options NT, RT, XT, 51 and 61, replace: IF, FN.
For system Options XN and 71, replace: FN, CT, MISC.
For all other system Options, replace: CPU, MISC, PS.
02
Peripheral Signal ROM checksum error.

For system Options NT, RT, XT, 51 and 61, replace IF.
For system Options XN and 71, replace: CIM.
For system Option 11, replace: CPU.
For all other system Options, replace: ROM.
03
Real-time Control (RTC) interrupt fault.

For system Options NT, RT, XT, 51 and 61, replace: IF.
For system Option 11, replace: CPU.
For system Options XN and 71, replace: CT.
04
Input Output (I/O) interrupt fault.

For system Options NT, RT, XT, 51 and 61, replace: FN.
For system Options XN and 71, replace: MISC.
For system Option 11, replace: CPU, TT/TD/SDI, SDI, card option mail, PRI, MISP.
For all other system Options, replace: MISC, SDI, TDS, MFS.
05
For system Option 11, replace: CPU. For all other system Options, replace:PS.
06
For system Option 11, replace: CPU. For all other system Options, replace:MISC, PS,
MFS.
07
Real-time Control (RTC) interrupt fault.

For system Options NT, RT, XT, 51 and 61, replace: IF.
For system Options XN and 71, replace: CIM.
For system Option 11, replace: CPU. For all other system Options, replace: ROM.
08
Too many initializes on this CPU.
09
CMA transmission error. Replace: primary CMA, secondary CMA, Memory.
553-3001-411
Standard 15.00
January 2006
Faceplate LED codes
Page 2329 of 2360

Code
Description
0A
CMA transmission error secondary, Memory Trouble Register (MTR) primary is

disabled. Replace: primary CMA, secondary CMA.
0B
CMA transmission error secondary, Memory Trouble Register (MTR) secondary is

disabled. Replace: secondary MEM, secondary CMA, primary CMA.
0C
PS ROM response timeout. Replace: CIM, IF.
0D
Parity error at non-memory address. Replace: IF, CMA.
0E
Parity error in PS ROM. Replace: IF, FN.
0F
Trap with no known cause.
10
Replace Memory 00.
11
Replace Memory 01.
12
Replace Memory 02.
18
Replace Memory 10.
19
Replace Memory 11.
1A
Replace Memory 12.
20
Primary memory parity error on read or write.

For system Options NT, RT, XT, 51 and 61, replace: CMA, IF. For system Option 11,
replace: CPU. For all other system Options, replace: CMA, MISC.
21
Memory parity error - primary and/or secondary.

For system Options XN and 71, replace: prime CMA, secondary CMA, MISC. For all
other system Options, replace: prime CMA, secondary CMA, IF.
22
Cannot clear CMA interrupt.

For system Options XN and 71, replace: prime CMA, secondary CMA, MISC. For all
other system Options, replace: primary CMA, secondary CMA.
23
CMA fault. Replace: CMA0, CMA1.
System Messages
Page 2330 of 2360
Faceplate LED codes

Code
Description
24
Data store failed to respond when reading trap data block. Replace: Memory, CMA, IF,
FN.
25
Checksum failed. For system Option 11, replace: CPU. Replace: Memory, CMA, IF,
FN.
4x
Peripheral Signaling card failure, where x is the PS number.
5x
Replace Intergroup Switch, where x is the IGS number in hex. (0-F = 0-15).
During SYSLOAD the following codes appear:
5B = loading firmware
5C = loading program
5D = loading data
5E = initializing data store (protected and unprotected)
5F = loading process successful
60
Replace Intergroup Switch 16.
61
62
63
6E
Replace Clock Controller 0.
6F
Replace Clock Controller 1.
7x
Replace TAPE or MSI x.
8x
Replace Serial Data Interface x, where x is the port number in hex. (0-F = 0-15). For
Option 11, x is card number in Hex.
553-3001-411
Standard 15.00
January 2006
Faceplate LED codes
Page 2331 of 2360

Code
9x
Description
Replace network, conference or TDS loop for group 0, where x is the loop number in
hex (0-F = 0-15).
Group 0
90
91
92
93
94
95
96
97
98
99
9A
9B
9C
9D
9E
9F
Loop Number
loop 0
loop 1
loop 2
loop 3
loop 4
loop 5
loop 6
loop 7
loop 8
loop 9
loop 10
loop 11
loop 12
loop 13
loop 14
loop 15
System Messages
Page 2332 of 2360
Faceplate LED codes

Code
Ax
Description
hex (0-F = 16-31).
Group 0
A0
A1
A2
A3
A4
A5
A6
A7
A8
A9
AA
AB
AC
AD
AE
AF
553-3001-411
Loop Number
loop 16
loop 17
loop 18
loop 19
loop 20
loop 21
loop 22
loop 23
loop 24
loop 25
loop 26
loop 27
loop 28
loop 29
loop 30
loop 31
Standard 15.00
January 2006
Faceplate LED codes
Page 2333 of 2360

Code
Bx
Description
hex (0-F = 32-47).
Group 1
B0
B1
B2
B3
B4
B5
B6
B7
B8
B9
BA
BB
BC
BD
BE
BF
Loop Number
loop 32
loop 33
loop 34
loop 35
loop 36
loop 37
loop 38
loop 39
loop 40
loop 41
loop 42
loop 43
loop 44
loop 45
loop 46
loop 47
System Messages
Page 2334 of 2360
Faceplate LED codes

Code
Cx
Description
hex (0-F = 48-63).
Group 1
C0
C1
C2
C3
C4
C5
C6
C7
C8
C9
CA
CB
CC
CD
CE
CF
553-3001-411
Loop Number
loop 48
loop 49
loop 50
loop 51
loop 52
loop 53
loop 54
loop 55
loop 56
loop 57
loop 58
loop 59
loop 60
loop 61
loop 62
loop 63
Standard 15.00
January 2006
Faceplate LED codes
Page 2335 of 2360

Code
Dx
Description
hex (0-F = 64-79).
Group 2
D0
D1
D2
D3
D4
D5
D6
D7
D8
D9
DA
DB
DC
DD
DE
DF
Loop Number
loop 64
loop 65
loop 66
loop 67
loop 68
loop 69
loop 70
loop 71
loop 72
loop 73
loop 74
loop 75
loop 76
loop 77
loop 78
loop 79
System Messages
Page 2336 of 2360
Faceplate LED codes

Code
Ex
Description
Replace extender.
Note: Ex codes are also used to define network, conference, or TDS loops. Check the
INI message to determine whether the HEX code is associated with an extender or
loop.
Where x is:
E0: Local Extender CPU 0 to Group 0
E8: Remote Extender Group 0 to CPU 0
E9: Remote Extender Group 1 to CPU 0
EA: Remote Extender Group 2 to CPU 0
EB: Remote Extender Group 3 to CPU 0
EC: Remote Extender Group 4 to CPU 0
ED: Remote Extender Group 5 to CPU 0
EE: Remote Extender Group 6 to CPU 0
EF: Remote Extender Group 7 to CPU 0
553-3001-411
Standard 15.00
January 2006
Faceplate LED codes
Page 2337 of 2360

Code
Fx
Description
Replace extender, where x is:
F0: Local Extender CPU 1 to Group 0
F8: Remote Extender Group 0 to CPU 1
F9: Remote Extender Group 1 to CPU 1
FA: Remote Extender Group 2 to CPU 1
FB: Remote Extender Group 3 to CPU 1
FC: Remote Extender Group 4 to CPU 1
FD: Remote Extender Group 5 to CPU 1
FE: Remote Extender Group 6 to CPU 1
FF: Remote Extender Group 7 to CPU 1
FFF: All extenders disabled
010
Sequence, status flag, conditional jump problems.

For system Options XN and 71, replace: CT, FN, IF, MISC, CIM. For all other system
Options, replace: FN, IF.
011
Call, return, micro return address stack problems.

012
JNI to jump over to next page in ROM failed. Replace: CT, FN, IF, MISC, CIM.
013
Micro-store parity.
Options, replace IF.
020
Slice register arithmetic, logic problem.

For system Options XN and 71, replace: FN, CT, IF, MISC, CIM. For all other system
System Messages
Page 2338 of 2360
Faceplate LED codes

Code
021
Description
16-bit barrel shifter problems.
022
16-bit barrel shifter problems with micro-store data.

023
Write to background while at interrupt level.

For system Options XN and 71, replace: FN, MISC, CT, IF, CIM. For all other system
024
Interrupt level did not write its bases.

025
Bad data written to some interrupt level bases.

026
Bad base fetch via BN at some interrupt level.

027
24-bit ALU shifter problem. Replace: FN, IF.
042
CPU write protect failed Replace: MISC, IF, FN, CIM.
080
Stuck bits in Y-registers.

081
Bad PSW register.

For system options XN and 71, replace: IF, MISC, CT, FN, CIM. For all other system
options, replace: IF.
553-3001-411
Standard 15.00
January 2006
Faceplate LED codes
Page 2339 of 2360

Code
082
Description
Bad FSI register.
For system Options XN and 71, replace: IF, MISC, CT, FN, CIM. For all other system
083
RAM addressing failure.

For system Options XN and 71, replace: FN, IF, CT, MISC, CIM. For all other system
084
Bad stack access at interrupt level.

085
Faulty FAR register.

For system Options XN and 71, replace: IF, CT, FN, MISC, CIM. For all other system
086
Faulty FSR register Replace: IF, CT, FN, MISC, CIM.
087
Read/Write failure on Miscellaneous registers.

For system Options XN and 71, replace: MISC, IF, FN, CT, CIM. For all other system
088
Fault during read/write operation while doing CPU tests.

089
PC auto-increment failure.
08A
PS fetch using BIR, not blocked.

For system Options XN and 71, replace: MISC, IF, FN, CT, CIM. For all other system
System Messages
Page 2340 of 2360
Faceplate LED codes

Code
08B
Description
RTC did not tick or clear.
For system Options XN and 71, replace: CIM, MISC, IF, FN, CT. For all other system
options, replace: FN, IF.
08C
Bad response timeout in FSI.

For system Options XN and 71, replace: IF, CT, FN, MISC, CIM. For all other system
08D
Bad data in program store fetch.

0FF
Ex
Bad CIM. Replace: CIM, IF, MISC, FN, CT.

Replace network, conference or TDS loop for group 2
Note: Ex codes are also used to replace extenders. Check the INI message to
determine whether the HEX code is associated with an extender or loop.
Where x is the loop number in hex (0-F = 80-95):
Group 2
E0
E1
E2
E3
E4
E5
E6
E7
E8
E9
EA
EB
EC
ED
EE
553-3001-411
Standard 15.00
Loop Number
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
January 2006
Faceplate LED codes
Page 2341 of 2360

Code
FFx
Description
hex (0-F = 96-111).
Group 3
10x
Loop Number
FF0
96
FF1
97
FF2
98
FF3
99
FF4
100
FF5
101
FF6
102
FF7
103
FF8
104
FF9
105
FFA
106
FFB
107
FFC
108
FFD
109
hex (0-F = 112-127).
Group 3
100
101
102
103
104
105
106
107
108
109
10A
10B
10C
10D
Loop Number
112
113
114
115
116
117
118
119
120
121
122
123
124
125
System Messages
Page 2342 of 2360
Faceplate LED codes

Code
11x
Description
hex (0-F = 128-143).
Group 4
12x
Loop Number
110
128
111
129
112
130
113
131
114
132
115
133
116
134
117
135
118
136
119
137
11A
138
11B
139
11C
140
11D
141
hex (0-F = 144-159).
Group 4
Loop Number
120
121
122
123
124
125
126
127
128
129
12A
12B
12C
12D
553-3001-411
Standard 15.00
144
145
146
147
148
149
150
151
152
153
154
155
156
157
January 2006
Faceplate LED codes
Page 2343 of 2360

Code
13x
Description
hex (0-F = 160-175).
Group 5
14x
Loop Number
130
160
131
161
132
162
133
163
134
164
135
165
136
166
137
167
138
168
139
169
13A
170
13B
171
13C
172
13D
173
hex (0-F = 176-191).
Group 5
140
141
142
143
144
145
146
147
148
149
14A
14B
14C
14D
Loop Number
176
177
178
179
180
181
182
183
184
185
186
187
188
189
System Messages
Page 2344 of 2360
Faceplate LED codes

Code
15x
Description
hex (0-F = 192-207).
Group 6
16x
Loop Number
150
192
151
193
152
194
153
195
154
196
155
197
156
198
157
199
158
200
159
201
15A
202
15B
203
15C
204
15D
205
hex (0-F = 208-223).
Group 6
Loop Number
160
161
162
163
164
165
166
167
168
169
16A
16B
16C
16D
553-3001-411
Standard 15.00
208
209
210
211
212
213
214
215
216
217
218
219
220
221
January 2006
Faceplate LED codes
Page 2345 of 2360

Code
17x
Description
hex (0-F = 224-239).
Group 7
18x
Loop Number
170
224
171
225
172
226
173
227
174
228
175
229
176
230
177
231
178
232
179
233
17A
234
17B
235
17C
236
17D
237
hex (0-F = 240-255).
Group 7
180
181
182
183
184
185
186
187
188
189
18A
18B
18C
18D
Loop Number
240
241
242
243
244
245
246
247
248
249
250
251
252
253
System Messages
Page 2346 of 2360
Faceplate LED codes
CDR Maintenance Display codes (CDR systems)

The codes provided below appear on the QPC41 MISC card maintenance
display of the CDR CPU. Codes with ** after them apply only to Multi-port
CDR machines. Refer to CDR Maintenance (553-2631-510).
CDR maintenance display codes (Part 1 of 6)

00
Trap caused by system power reset. This code is provided for information only.
01
The CDR CPU failed the CPU test. If CDR is not running, suspect one or more of
the following packs:
Arithmetic Logic Unit (ALU) - QPC40
Miscellaneous (MISC) - QPC41
Sequencer (SEQ) - QPC42
Read-only-memories (ROMs)
If CDR is running then an intermittent fault is present. Use LD 42 to clear the CDR
maintenance display or press the MAN INT button on multi-port CDR machines. If
the problem recurs, suspect the packs listed above.
02, 03
The ROM failed to checksum correctly. Suspect ROM packs. If CDR is not running,
suspect the following packs:
02 = CDR ROM 1 QPC131 (single port), QPC234 (multi-port)
03 = CDR ROM 2 QPC132 (single port), QPC235 (multi-port)
If neither of these packs clear the fault, suspect a processor fault. Respond as if 01
were in the display. If CDR is running, an intermittent fault is present. Use LD 42 to
clear the CDR maintenance display. If the problem reappears, suspect the packs
listed above. If the problem reappears and persists, treat it as a code 01.
05
Trap caused by response time-out. A device suddenly failed to respond. This could
happen if an SDI card was removed without first using CDM to disable the card. If
this problem is intermittent, a card may not be securely enough plugged into the
CDR machine or may be faulty. If the problem still occurs, respond as for code 01.
06
Trap caused by write protection violation.
07
Trap caused by watchdog time-out. These codes probably indicate a CPU

problem. Suspect cards in the same order as for code 01.
08
Trap caused by memory parity error. If this recurs after clearing the maintenance
display, respond as for code 10.
553-3001-411
Standard 15.00
January 2006
Faceplate LED codes
Page 2347 of 2360

09
Trap for indeterminable causes. This code probably indicates a CPU problem.
Suspect packs in the same order as for code 01.
10
The read/write memory failed the memory test. If CDR is not running, suspect the
memory pack.
If CDR is running then an intermittent fault exists. Use LD 42 to clear the CDR
maintenance display. If the fault recurs, suspect the packs listed above followed by
the packs listed for code 01.
20, 21
CDR timing problem:

20 = CDR timing did not respond.
21 = CDR timing had a stuck interrupt.
For both 20 or 21 case suspect CDR Timing pack.
If CDR is not running, see 553-2631-510. If CDR is running, the an intermittent
fault exists. Use LD 42 to clear the CDR maintenance display. If the problem
recurs, suspect the packs listed above followed by all the packs listed for code 01.
30
The requested sequence is already being performed. Wait for it to complete.
31
The requested function can not be performed because another request is still
pending. Wait for the pending function to complete or press the UNLOAD button to
terminate it.
32
The requested function (RESTORE or LOAD) cannot be performed because CDM

has been loaded and has put the CDR machine in maintenance mode.
See the discussion of maintenance mode in LD 42. If it is required to terminate the
maintenance mode, UNLOAD may be pressed to unload the tape. Note that this
may disturb the tests being performed by CDM.
33
RESTORE cannot be performed because a LOAD or UNLOAD sequence is in

progress; wait for the sequence to complete.
34
LOAD can not be performed because the drive is not disabled or another function
is in progress. If another function is being performed, wait for it to complete, then
try again. If the drive is not disabled, you must UNLOAD the tape before you can
LOAD it.
CAUTION: LOAD will destroy any data already written on the tape.
System Messages
Page 2348 of 2360
Faceplate LED codes

35
LOAD can not be performed because the tape is not at load point. UNLOAD and
remount the tape.
CAUTION: LOAD will destroy any data already on the tape.
40
Cabinet over-temperature has been detected. Take appropriate temperature

lowering measures.
41
Fan failure has been detected in CDR cooling unit. Clean filters and/or replace fan
assembly.
50
LOAD cannot be performed because the tape is write protected. CDR will unload
the reel of tape. Install a write enable ring in the supply reel and remount the tape.
51
LOAD cannot be performed because the tape unit is not ready. This may be
because it is rewinding. Wait for rewind to complete and make unit ready. Retry
request.
52
LOAD failed after 10 tries. CDR will unload the tape. Retry the request with a
different tape. If the problem persists then:
Clean the tape head path.
The tape unit may require calibration or be faulty.
Suspect QPC130 (Tape Control), QPC39 (Timing) or cables.
53
553-3001-411
UNLOAD failed after 10 tries. CDR gives up.
Standard 15.00
January 2006
Faceplate LED codes
Page 2349 of 2360

54
The RESTORE function failed after 4 tries. CDR will wait 8 h and then try again.
This code indicates that the error recovery attempt has failed.
Attempt to RESTORE the tape. If restore is successful, use LD 42 to clear the
maintenance display or press MAN INT on a multi-port CDR machine. If the
RESTORE fails, try cleaning the tape heads and path. Try RESTORE again. If it
fails, try Loading a new tape. If this is successful, send the old tape for processing.
If the LOAD fails, suspect one or more of the following items:
tape drive - may require calibration or repair
QPC130 Tape Interface
QPC39 Timing
cables
If the problem is intermittent suspect the items listed above.
Since CDR will try the RESTORE again after an 8 h wait, the CDR machine may
be recording data if more than 8 h has elapsed since the code was originally put in
the display. This would indicate that the fault is intermittent.
55
End-of-tape encountered while doing a RESTORE. CDR will UNLOAD the tape.
The tape cannot be RESTORED since the tape mark at the end of the data cannot
be found. If the tape has data on it, it should be sent for processing and a new tape
mounted and LOADED to collect new data. If the problem persists, a faulty tape
unit is suspected. This problem can also be caused by trying to RESTORE a blank
tape.
56
Write protect was encountered while doing a RESTORE. Ensure that the write
enable ring is installed. If the problem persists, suspect a tape reel or tape drive.
57
End-of-tape encountered while writing. CDR will UNLOAD the tape. Mount a new
tape and LOAD it. Send the tape that was removed for processing. Depending on
the period of time since the end of tape occurred, data may or may not have been
lost.
70
CDR tape control pack did not respond.
System Messages
Page 2350 of 2360
Faceplate LED codes

71
CDR tape control has a stuck interrupt. In either case suspect CDR Tape Control.
If the CDR is not running see 553-2631-510. If the CDR is running, an intermittent
fault exists. Use LD 42 to clear the CDR maintenance display or press MAN INT on
a multi-port CDR machine. If the problem recurs, suspect the packs listed above
followed by all packs listed for code 01.
8x
SDI problem, where:

80 = SDI response time-out.
81 = SDI has permanent interrupt.
82 = SDI line is not ready.
83 = SDI lost an output interrupt.
For 80 to 83 suspect the SDI pack. Ensure that the speed select, address select
and programming plugs are properly set. If the CDR is not running, see
553-2631-510. If CDR is running, an intermittent fault exists. Use LD 42 to clear
the CDR maintenance display or press MAN INT on a multi-port CDR machine. If
the problem recurs, suspect the packs listed above followed by all packs listed for
code 01.
Code 82 can also be caused by a faulty modem or cable.
Regarding Codes Ax through Dx:

The following display codes (Ax through Dx) identify a problem in port x (0 to 15), where x is
indicated as a hexadecimal device number in the range 0 to F. See hexadecimal conversion
table in the first part of this practice.
Ax
TTY x does not exist. This code will be displayed if the parameter on an ENL SL1
command refers to an SDI port which does not exist. Either the parameter was
mis-specified or the address switches on the SDI card were set incorrectly. This
error can also occur with a faulty SDI card.
Bx
TTY x is not getting output interrupts. The SDI pack should be replaced. If this
does not cure the problem, act as for code 01.
553-3001-411
Standard 15.00
January 2006
Faceplate LED codes
Page 2351 of 2360

Cx
EIA Device Not Ready status on TTY x. Unless the SDI card is faulty, this error
indicates:
1. There is no connector attached to the faceplate of the SDI, or
2. A plug on the SDI pack is in the wrong position, or
3. A plug on the SDI pack is missing.
Dx
Stuck interrupt on TTY x. Replace the SDI card. If this proves to be of no avail,
treat the problem the same as for code 01.
System Messages
Page 2352 of 2360
Faceplate LED codes
I/O Processor (IOP) card displays

System Options 51C, 61C, 81, and 81C machines, the NT6D63 I/O Processor
(IOP) card provides hexadecimal displays to indicate various phases of
operation and the states the card is in during those phases.
Assembly level initialization and basic card self-tests are noted on the HEX
display by decimal points appearing to the left of the HEX code.
High level code initialization and card self-tests have the decimal point to the
right of the code to indicate they are taking place.
Card operation is indicated by the alternating decimal points.
Table 6
Assembly level initialization and basic card self-tests
Event
Hex code
LED state
Power up
Self-test 1
Self-test 1 fails
.0.
.1
.1/.E.
ON
ON
ON
Self-test 2
Self-test 2 fails
.2
.2/.E.
ON
ON
Debug initialization
Debug initialization failed
.3.
.3./.E.
ON
ON
Self-test 3
Self-test 3 fails
.3
.3/.E.
ON
ON
Self-test 4
Self-test 4 fails
.4
.4/.E.
ON
ON
.8
ON
Set up
553-3001-411
Standard 15.00
January 2006
Note
Bootstrap code
ROM checksum self-test
ROM checksum self-test failed
(alternates 3 times)
SRAM self-test
SRAM self-test failed (alternates 3
times)
IOP debugger initialization
IOP debugger initialization failed
Processor self-test
Processor self-test failed
BIC Initial Condition Check
BIC Initial Condition Check failed
Assembly level copying ROM to
RAM, and miscellaneous
initialization
Faceplate LED codes
Page 2353 of 2360
Table 7
High level initialization and card self-tests
Event
Hex
code
LED
state
Debug
.D.
ON
Set up
Self-test a
Self-test a fails
8.
1.
1./ E
OFF
OFF
ON
Self-test b
Self-test b fails
Self-test c
Self-test c failed
Self-test e
Self-test 3 fails
2.
2./ E
3.
3./ E
5.
5./ E
OFF
ON
OFF
ON
OFF
ON
Self-test f
Self-test f fails
6.
6./ E
OFF
ON
Note
3 second window to enter the debugger by
typing ^B, or in debugger
Initialization and set up in C
IOP registers self-test
IOP registers self-test failed (alternates 3
times)
BIC self-test
BIC self-test failed (alternates 3 times)
SCSI self-test
SCSI self-test failed (alternates 3 times)
Security cartridge self-test
Security cartridge self-test failed
Duart self-test
Duart self-test failed (alternates 3 times)
System Messages
Page 2354 of 2360
Faceplate LED codes
Table 8
Operational states
Hex
code
LED
state
Ping
Disabled
Enabled
Maintenance
message
.9 / 9.
.A / A.
.A / A.
.B / B.
ON
ON
OFF
OFF
SCSI interrupt
message
.F / F.
OFF
Debugger enabled
.D / D.
OFF
Debugger disabled
.D / D.
ON
Debugger active
Error enabled
Error disabled
Reset
D
.E / E.
.E / E.
.E.
ON
OFF
ON
ON
Event
553-3001-411
Standard 15.00
January 2006
Note
IOP hunt cp/IOP test in progress
Operational and disabled, or waiting to hunt
Operational and enabled
Maintenance message sent
(persists for about 1 second)
SCSI interrupt message sent
(persists for about 1 second)
Operational, enabled and duart polled for ^B
to enter
Operational, disabled and duart polled for ^B
to enter.
In debugger
Soft reset occurred, enabled
Soft reset occurred, disabled
Hard reset initiated
Faceplate LED codes
Page 2355 of 2360
Call Processor (CP) card displays

The NT6D66 Call Processor (CP) card in the Options 51C, 61C, 81, and 81C
utilizes plain text messages as well as Hex for system maintenance, status,
and errors. Table 9 lists the different LCD messages that appear on the CP
card faceplate. The standard Hex messages also appear on this LCD display
Table 9
NT6D66 CP card displays
Display output
Meaning
pack is AP: IDLE
Checking to determine if the system can be Split.
Type CTRL-B to run

CP-BUG debugger
Option 81 start-up. Output to CP port prior to loading the

operating system.
In CP-BUG
The debug program was entered.
Exit CP-BUG
The debug program is being exited.
BOOT ERROR: RPT. Init
System failed to initialize correctly
SIOx No Drv
No device driver associated with CP serial port x.
SIOx Created
CP serial port x already exists
SIOx Init Fail
CP serial port x failed to initialize the device specific database.
ITG card displays

The ITG Line 2.0 card faceplate four character display provides feedback to
the craftperson on the diagnostic status of the card during power-up and on its
System Messages
Page 2356 of 2360
Faceplate LED codes
operational state when in service. Table 10 gives a list of the Hex messages.
Table 10
ITG faceplate maintenance display codes (Part 1 of 2)
Hex Display code
Message
T:00
Initialization
T:01
Testing Internal RAM
T:02
Testing ALU
T:03
Testing address mode
T:04
Testing Boot ROM
T:05
Testing timers
T:06
Testing watchdog
T:07
Testing external RAM
T:08
Testing Host DPRAM
T:09
Testing DS30 DPRAM
T:10
Testing Security Device
T:11
Testing Flash memory
T:12
Programming PCI FPGA
T:13
Programming DS30 FPGA
T:14
Programming CEMUX FPGA
T:15
Programming DSP FPGA
T:16
Testing CEMUX interface
T:17
Testing EEPROM
T:18
Booting processor, waiting for response with self-test

information
T:19
Waiting for application start-up messages from processor.
553-3001-411
Standard 15.00
January 2006
Faceplate LED codes
Page 2357 of 2360
Table 10
ITG faceplate maintenance display codes (Part 2 of 2)
Hex Display code
Message
T:20
CardLAN enabled, transmitting bootp requests.

If this display persists, then the ITG 2.0 card is running in BIOS
ROM mode due to card software failure.
T:21
CardLAN operational, A07 enabled, display now under host

control.
Card is looking for an active leader by sending bootp requests
on the management LAN. If no bootp response is received on
the management LAN, Leader 0 times out first and starts
active leader tasks. Leader1 has a longer time out and
normally starts backup leader, otherwise Leader 1 times out
and starts active leader tasks.
A follower card send bootp requests on the management LAN
continuously and never times out. Enter +++ to escape from
bootp request mode and start ITG shell.
T:22
The ITG Line 2.0 card is attempting to start the application.
LDR
Card is running active leader tasks.
BLDR
Card has detected existing active leader, and is running

backup leader tasks.
FLR
Card has detected the active leader, and is running Follower

tasks.
System Messages
Page 2358 of 2360
553-3001-411
Faceplate LED codes
Standard 15.00
January 2006
2360
HEX
Page 2359 of 2360
Appendix A: Hexadecimal conversion

Convert hexadecimal to binary and decimal
It is sometimes necessary to convert hexadecimal numbers (HEX) output in
a message into decimal. The LD 32 CONV command can be used to convert
TNs between hex and decimal.
Example: a single density terminal number is output as 081A hexadecimal.
To find the decimal equivalent:
1. Convert each HEX digit into binary. See Table 11.
hex: 081A
binary: 0000 1000 0001 1010
2. Decode the binary number using the formats shown in Figure 1 on
page 2360. In this example, the TN is single density.
Group: 000 = 0 decimal
Loop:
01000 = 8 decimal
Shelf:
00 = 0 decimal
Card:
0110 = 6 decimal
Unit:
10 = 2 decimal
TN in decimal = 8 0 6 2.
Table 11
Convert hex to binary and decimal
HEX
Binary
Decimal
0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111
10
11
12
13
14
15
System Messages
Page 2360 of 2360
Appendix A: Hexadecimal conversion
Figure 1
Terminal number formats
Loop Density = Single (SD)
Card Density = SD
15
14
13
12
11
10
G2 G1 G0 L4
L3
L2
L1
L0
S1 S0
Group
Loop
0-4
0-31
C3 C2 C1
Shelf
C0 U1 U0
Card
0-3
Unit
1-10
0-3
Loop Density = Double (DD)

Card Density = DD, SD
15
14
13
12
11
10
G2 G1 G0 L4
L3
L2
L1
L0
S0 U2
Group
0-4
C3 C2 C1
Loop
Card
0-31
1-10
C0 U1 U0
Unit 0-7
Shelf 0-1
Loop Density = Quad (4D)
Card Density = 4D, DD, SD
15
14
13
12
11
10
G2 G1 G0 L4
L3
L2
L1
L0 U3 U2 C3
C2 C1
Group
Loop
Card
0-4
0-31
1-10
553-1053
Unit 0-15
553-3001-411
Standard 15.00
January 2006
C0 U1 U0
Family Product Manual Contacts Copyright FCC notice Trademarks Document

number Product release Document release Date Publish
Nortel Communication Server 1000
System Messages
Copyright Nortel Networks Limited 2006

All Rights Reserved
Information is subject to change without notice.
Nortel Networks reserves the right to make changes in design
or components as progress in engineering and manufacturing
may warrant.
Nortel, Nortel (Logo), the Globemark, This is the Way, This is
Nortel (Design mark), SL-1, Meridian 1, and Succession are
trademarks of Nortel Networks.
Publication number: 553-3001-411
Document release: Standard 15.00
Date: January 2006
Produced in Canada

553-3001-411 - 15.00 Mensajes

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

553-3001-411 - 15.00 Mensajes

Загружено:

Авторское право:

Доступные форматы

Title page

Nortel Communication Server 1000

Year Publish FCC TM

Finding the latest updates

How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About this document . . . . . . . . . . . . . . . . . . . . . . .

ACD: Automatic Call Distribution

SNMP trap: ADD: Automatic Call

SNMP trap: AMH: Auxiliary Message Handler . . .

SNMP trap: AML: Application

SNMP trap: AMLM: Application

SNMP trap: ATM: Automatic Trunk

SNMP trap: AUD: Software Audit (LD 44) . . . . . . .

SNMP trap: AUTH: Authorization Code (LD88) . . 119

SNMP trap: CMON: Core Monitor . . . . . . . . . . . . . 643

SNMP trap: DTD: Dial Tone Detector

SNMP trap: FIJI: Fiber Junctor Interface . . . . . . . . 925

SNMP trap: MAT: Meridian

SNMP trap: NACD: Network Automatic

SNMP trap: QoS: Quality of Service . . . . . . . . . . 1431

SNMP trap: SRPT: System Reports . . . . . . . . . . . 2027

SNMP trap: XMI: Network to Controller Message

Standard15.00. This document is up-issued to include system message

Standard14.00. This document is up-issued for Communication Server 1000

Standard 13.00. This document is up-issued for Communication Server 1000

Standard 12.00. This document is up-issued to support Succession 3.0

Standard 11.00. This global document is up-issued to include system

Standard 10.00. This global document is up-issued to include messages

Standard 9.00. This global document is up-issued to include messages

Standard 8.00. This document is issued to include content required for

Standard 7.00. This document is issued to include updates and changes

Standard 6.00. This document is issued to include updates and changes

Standard 5.00. This document is issued to include updates and changes

Standard 4.00. This document is issued to include updates and changes

Standard 3.00. This document is issued to include updates and changes

Standard 2.00. This document is up-issued to include updates and changes

Standard 1.00. This document is issued to include updates and changes

Finding the latest updates

Takes you directly to the Nortel

Takes you directly to the Nortel

Finding the latest updates on the Nortel web site

How to get help

Getting help from the Nortel Web site

download software, documentation, and product bulletins

sign up for automatic notification of new software and documentation for

open and manage technical support cases

Getting help over the telephone from a Nortel Solutions

How to get help

Getting help from a specialist by using an Express Routing

Getting help through a Nortel distributor or reseller

About this document

Communication Server 1000S (CS 1000S)

Communication Server 1000M Chassis (CS 1000M Chassis)

Communication Server 1000M Cabinet (CS 1000M Cabinet)

Communication Server 1000M Half Group (CS 1000M HG)

Communication Server 1000M Single Group (CS 1000M SG)

Communication Server 1000M Multi Group (CS 1000M MG)

About this document

Communication Server 1000E (CS 1000E)

Meridian 1 PBX 11C Chassis

Meridian 1 PBX 11C Cabinet

Meridian 1 PBX 51C

Meridian 1 PBX 61C