Mensajes 553-3001-411_18.00

Title page

Nortel Communication Server 1000 Nortel Communication Server 1000 Release 4.5

Software Input/OutputSystem MessagesDocument Number: 553-3001-411 Document Release: Standard 18.00 Date: August 2006

Year Publish FCC TM Copyright 2006 Nortel Networks. All rights reserved. Produced in Canada

The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks. Nortel, Nortel (Logo), the Globemark, SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.

6

Page 3 of 2464

Revision historyAugust 2006

Standard 18.00. This document is up-issued to include text changes to message SCSI0011 (CR Q01297135).July 2006

Standard 17.00. This document is up-issued to include system messages BUG0302, BUG0303, and BUG0304 (CR Q01275359).July 2006

Standard 16.00. This document is up-issued for changes in technical content.January 2006

Standard15.00. This document is up-issued to include system message number BUG9098 (CR Q01135699-02) . See page 591 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.

Software Input/Output

System Messages

Page 4 of 2464 January 2002

Revision history

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

Standard 6.00. This document is issued to include updates and changes required for X11 Release 24.2x.March 1999

Standard 5.00. This document is issued to include updates and changes required for X11 Release 24.0x.October 1997

Standard 4.00. This document is issued to include updates and changes required for X11 Release 23.0x.August 1996

Standard 3.00. This document is issued to include updates and changes required for X11 Release 22.0x.December 1995

Standard 2.00. This document is up-issued to include updates and changes required for X11 Release 21.1x.July 1995

Standard 1.00. This document is issued to include updates and changes required for X11 Release 21.0x.

553-3001-411

Standard 18.00

August 2006

Revision history

Page 5 of 2464

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.


System Messages

Page 6 of 2464

Revision history

553-3001-411

Standard 18.00

August 2006

14

Page 7 of 2464

ContentsContents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding the latest updates on the Nortel web site . . . . . . . . . . . . . . . . . . . . . . . How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this document . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ACD: Automatic Call Distribution Load Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: ADD: Automatic Call Distribution Data Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: AMH: Auxiliary Message Handler . . . . . . . . . . . . SNMP trap: AML: Application Module Link (LD 48) . . . . . . . . SNMP trap: AMLM: Application Module Link Maintenance (LD 48) . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: ATM: Automatic Trunk Maintenance (LD 92) . . . SNMP trap: AUD: Software Audit (LD 44) . . . . . . . . . . . . . . . .

7 15 17 19 2527

43 47 51

53 59 69

SNMP trap: AUTH: Authorization Code (LD88) . . . . . . . . . . . 123


System Messages

Page 8 of 2464

Contents

SNMP trap: BERR: Bus Error Monitor . . . . . . . . . . . . . . . . . . SNMP trap: BIC: Bus Interface Circuit . . . . . . . . . . . . . . . . . SNMP trap: BKP: Remote Backup (Small Systems and Succession 1000 systems) . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: BRI: Basic Rate Interface . . . . . . . . . . . . . . . . . . SNMP trap: BRIT: BRI Trunks . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: BSD: Background Signaling Diagnostic (LD 45) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: BUG: Software Error Monitor . . . . . . . . . . . . . . . SNMP trap: CCBR: Customer Configuration Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: CCED: Core Common Equipment Diagnostic (LD 135) . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: CDM: Call Detail Recording Diagnostic (LD 40, LD 42) . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: CDN: Control DN . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: CIOD: Core Input/Output Diagnostic (LD 137) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: CLKC: Clock Controller . . . . . . . . . . . . . . . . . . . SNMP trap: CMON: Core Monitor . . . . . . . . . . . . . . . . . . . . . SNMP trap: CND: Caller's Name Display . . . . . . . . . . . . . . . SNMP trap: CNF: Conference Circuit Diagnostic (LD 38) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

127 137

139 143 167

179 193

605

607

625 639

641 665 671 675

677

553-3001-411

Standard 18.00

August 2006

Contents

Page 9 of 2464

SNMP trap: CNI: Core to Network Interface . . . . . . . . . . . . . . 683 SNMP trap: COM: Data Communication . . . . . . . . . . . . . . . . . 689 SNMP trap: CRI: Carrier Remote IPE . . . . . . . . . . . . . . . . . . . 693 SNMP trap: CSA: Command and Status Link Diagnostic (LD 48) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701 SNMP trap: CSC: Customer Service Change . . . . . . . . . . . . . 707 SNMP trap: DBMT: Database Media Transfer . . . . . . . . . . . . 715 SNMP trap: DCH: D-channel Diagnostic (LD 96) . . . . . . . . . . 723 SNMP trap: DLO: Disk Layout . . . . . . . . . . . . . . . . . . . . . . . . . 743 SNMP trap: DROL: Daily Routine Overlay . . . . . . . . . . . . . . . 745 SNMP trap: DSET: Digital Set Download . . . . . . . . . . . . . . . . 747 SNMP trap: DSL: DSL Diagnostic (LD 32) . . . . . . . . . . . . . . . 749 SNMP trap: DTA: Digital Trunk Diagnostic . . . . . . . . . . . . . . 751 SNMP trap: DTC: Digital Trunk Clock Controller Diagnostic (LD 60) . . . . . . . . . . . . . . . . . . . . . . . . . 767 SNMP trap: DTD: Dial Tone Detector Diagnostic (LD 34) . . . 771 SNMP trap: DTI: Digital Trunk Interface Diagnostic (LD 60) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773 SNMP trap: DTM: Digital Trunk Maintenance (LD 75) . . . . . . 791 SNMP trap: DTRK: Digital Trunk Diagnostic (LD 60) . . . . . . . 805 SNMP trap: EDD: Equipment Data Dump (LD 43) . . . . . . . . . 809


System Messages

Page 10 of 2464

Contents

SNMP trap: ELAN: Ethernet Local Area Network . . . . . . . . . SNMP trap: EMR: Emergency Key (ACD) . . . . . . . . . . . . . . . SNMP trap: ERR: Error Monitor (Hardware) . . . . . . . . . . . . . SNMP trap: ESA: Emergency Services Access . . . . . . . . . . SNMP trap: ESDA: Enhanced Serial Data Interface (LD 48) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: ESDI: Enhanced Serial Data Interface (LD 48) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: ESN: Electronic Switched Network (LD86, LD 87 and LD 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP trap: FHW: Faulty Hardware . . . . . . . . . . . . . . . . . . . . SNMP trap: FIJI: Fiber Junctor Interface . . . . . . . . . . . . . . . . SNMP trap: FIR: Fibre Remote IPE . . . . . . . . . . . . . . . . . . . . SNMP trap: FMEM: Flash Memory . . . . . . . . . . . . . . . . . . . . .

819 823 825 927

929

931

933 961 965 993 999

SNMP trap: HTM: Hyper-text markup language . . . . . . . . . . 1007 SNMP trap: HWI: Hardware Infrastructure Maintenance . . . 1023 SNMP trap: HWR: Hardware Reset . . . . . . . . . . . . . . . . . . . . 1069 SNMP trap: ICU: Intercept Computer Update (LD 51) . . . . . 1075 SNMP trap: INI: Initialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077 SNMP trap: INST: Installation . . . . . . . . . . . . . . . . . . . . . . . . . 1091 SNMP trap: IOD: Input/Output Diagnostic (LD 37) . . . . . . . . 1113

553-3001-411

Standard 18.00

August 2006

Contents

Page 11 of 2464

SNMP trap: ISR: Intergroup Switch and System Clock Generator Diagnostic (LD 39) . . . . . . . . . . . . . . . . . . . . 1127 SNMP trap: ITG: Integrated IP Telephony Gateway . . . . . . . . 1139 SNMP trap: ITS: Internet IP Telephony Server . . . . . . . . . . . . 1211 SNMP trap: LIS: Location Information Services . . . . . . . . . . 1231 SNMP trap: LNK: Link Diagnostic (LD 48) . . . . . . . . . . . . . . . 1233 SNMP trap: MAT: Meridian Administration Tools . . . . . . . . . 1253 SNMP trap: MCT: Malicious Call Trace . . . . . . . . . . . . . . . . . . 1259 SNMP trap: MFC: Multifrequency Compelled Signaling (LD 54) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1261 SNMP trap: MFD: Multifrequency Signaling Diagnostic (LD 54) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1263 SNMP trap: MFE: Multifrequency Signaling Diagnostic (LD 54) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269 SNMP trap: MFK: Multifrequency Signaling for KD3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1273 SNMP trap: MFR: Multifrequency Receiver . . . . . . . . . . . . . . 1275 SNMP trap: MFS: Multifrequency Sender Diagnostic for ANI (LD 46) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1277 SNMP trap: MISP: Multi-purpose ISDN Signaling Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281 SNMP trap: MPH: Meridian Packet Handler . . . . . . . . . . . . . . 1293 SNMP trap: MRB: Message Registration Block . . . . . . . . . . . 1301


System Messages

Page 12 of 2464

Contents

SNMP trap: MSDL: Multi-purpose Serial Data Link . . . . . . . 1303 SNMP trap: MWL: Message Waiting Lamps Reset (LD 61) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323 SNMP trap: NACD: Network Automatic Call Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1325 SNMP trap: NCT: Network Call Trace . . . . . . . . . . . . . . . . . . 1329 SNMP trap: NPR: Network and Peripheral Equipment Diagnostic(LD 32) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1373 SNMP trap: NWS: Network and Signaling Diagnostic (LD 30) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1395 SNMP trap: OHAS: Off-Hook Alarm Security . . . . . . . . . . . . 1411 SNMP trap: OSM: Operating System Messaging . . . . . . . . . 1413 SNMP trap: OSN: On-Site Notification . . . . . . . . . . . . . . . . . 1417 SNMP trap: OVD: Overload Monitor . . . . . . . . . . . . . . . . . . . 1419 SNMP trap: OVL: Overlay Loader . . . . . . . . . . . . . . . . . . . . . 1423 SNMP trap: PCH: System Patch reports . . . . . . . . . . . . . . . . 1435 SNMP trap: PMS: Property Management System Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1453 SNMP trap: PRI: Primary Rate Interface Diagnostic (LD 60) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1455 SNMP trap: PWR: Power and System Monitor . . . . . . . . . . . 1483 SNMP trap: QoS: Quality of Service . . . . . . . . . . . . . . . . . . . 1489 SNMP trap: RCV: Recovery Messages . . . . . . . . . . . . . . . . . 1503

553-3001-411

Standard 18.00

August 2006

Contents

Page 13 of 2464

SNMP trap: RLC: Reach Line Card . . . . . . . . . . . . . . . . . . . . . 1505 SNMP trap: RPD: 1.5 Mb/s Remote Peripheral Equipment Diagnostic (LD 33) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1509 SNMP trap: RPE: 2.0 Mb/s Remote Peripheral Equipment Alarm Handler (LD 53) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517 SNMP trap: RPL: 1.5 Mb/s Remote Peripheral Equipment Local End Diagnostic (LD 62) . . . . . . . . . . . . . . . 1527 SNMP trap: RPM: 2.0 Mb/s Remote Peripheral Equipment Diagnostic (LD 53) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1533 SNMP trap: RPT: System Reporting . . . . . . . . . . . . . . . . . . . . 1543 SNMP trap: SCH: Service Change . . . . . . . . . . . . . . . . . . . . . . 1545 SNMP trap: SCR: System Clock Reference . . . . . . . . . . . . . . 2089 SNMP trap: SCSI: Small Computer System Interface . . . . . . 2091 SNMP trap: SDL: Peripheral Software Download . . . . . . . . . 2099 SNMP trap: SECA: Security Administration Alarm . . . . . . . . 2107 SNMP trap: SEC: Security Notification Monitor . . . . . . . . . . . 2109 SNMP trap: SRPT: System Reports . . . . . . . . . . . . . . . . . . . . 2113 SNMP trap: SYS: System Loader . . . . . . . . . . . . . . . . . . . . . . 2157 SNMP trap: TDS: Tone and Digit Switch Diagnostic (LD 34) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2275 SNMP trap: TEMU: Tape Emulation . . . . . . . . . . . . . . . . . . . . 2287 SNMP trap: TFC: Traffic Control (LD 2) . . . . . . . . . . . . . . . . . 2305


System Messages

Page 14 of 2464

Contents

SNMP trap: TFN: Customer Network Traffic . . . . . . . . . . . . . 2313 SNMP trap: TFS: Traffic Measurement . . . . . . . . . . . . . . . . . 2315 SNMP trap: TMDI: T1 Multi Purpose Digital Interface . . . . . 2319 SNMP trap: TMF: Test Multifrequencies . . . . . . . . . . . . . . . . 2335 SNMP trap: TRA: Call Trace (LD 80) . . . . . . . . . . . . . . . . . . . 2339 SNMP trap: TRK: Trunk Diagnostic (LD 36) . . . . . . . . . . . . . 2345 SNMP trap: TTY: Teletype Error Reports . . . . . . . . . . . . . . . 2371 SNMP trap: VAS: Value Added Server . . . . . . . . . . . . . . . . . 2375 SNMP trap: VTN: Voice Port TN . . . . . . . . . . . . . . . . . . . . . . . 2383 SNMP trap: WEB: Web Server . . . . . . . . . . . . . . . . . . . . . . . . 2385 SNMP trap: XCT: Conference, Tone and Digit Switch, and Multifrequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2399 SNMP trap: XMI: Network to Controller Message Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2403

FaceplateLED codes . . . . . . . . . . . . . . . . . . . . . . . 2407

553-3001-411

Standard 18.00

August 2006

16

Page 15 of 2464

Finding the latest updates on the Nortel web siteThe 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. Takes you directly to the Nortel page for CS 1000 Release 4.5 documentation.

Latest Documentation


System Messages

Page 16 of 2464

Finding the latest updates on the Nortel web site

553-3001-411

Standard 18.00

August 2006

18

Page 17 of 2464

How to get helpThis section explains how to get help for Nortel products and services.

Getting help from the Nortel Web siteThe 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 CenterIf 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 2464

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 CodeTo 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 resellerIf 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 18.00

August 2006

24

Page 19 of 2464

About this documentThis 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.

SubjectThis 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 systemsThis 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 2464

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 18.00

August 2006

About this document

Page 21 of 2464

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... 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 Maps to this CS 1000M system CS 1000M Chassis CS 1000M Cabinet CS 1000M Half Group CS 1000M Single Group CS 1000M Multi Group 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 2464

About this document

Intended audienceThis document is intended for individuals responsible for installing, administering and maintaining Communication Server 1000 and Meridian 1 systems.

ConventionsTerminology 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) Meridian 1 PBX 11C Chassis Meridian 1 PBX 11C Cabinet

The following systems are referred to generically as Large System: 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

553-3001-411

Standard 18.00

August 2006

About this document

Page 23 of 2464

Related informationThis 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 2464

About this document

553-3001-411

Standard 18.00

August 2006

26

Page 25 of 2464

IntroductionThis 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 2464

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 18.00

August 2006

2406

Page 27 of 2464

ACD: Automatic Call Distribution Load ManagementThe 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.

MessagesACD0000

Program IdentifierAction: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0001

Noisy ACD terminal; disabled since noise threshold exceeded.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0002

Too many invalid characters entered on ACD terminal; disabled since invalid character threshold was exceeded.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0003

Invalid character entered.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No


System Messages

Page 28 of 2464 ACD0004

Cannot transfer the reported agent to another queue.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0005

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. Critical to Monitor: No. SNMP trap: No

ACD0006

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. Critical to Monitor: No. SNMP trap: No

ACD0007

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 persists, perform a system reload or parallel reload. Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0008

No call register available at this moment.Action: If message persists, increase the number of call registers for the customer. Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0010

Invalid input character; only blanks allowed.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0011

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

553-3001-411

Standard 18.00

August 2006

Page 29 of 2464 ACD0012

Unknown command.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0013

Invalid day; valid range 1 to 31.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0014

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

ACD0015

Invalid day-month combination.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0016

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

ACD0017

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

ACD0018

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

ACD0019

Same day cannot be reentered.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No


System Messages

Page 30 of 2464 ACD0020

Too many digits supplied for DN.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0021

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

ACD0022

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

ACD0023

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

ACD0024

Invalid RAN time threshold or time-out.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0025

Invalid RAN route.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0026

Invalid threshold values.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0027

Queue overflow destination cannot be itself.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

553-3001-411

Standard 18.00

August 2006

Page 31 of 2464 ACD0028

Invalid value of 'T' in TSF.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0029

Same report option cannot be reentered.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0030

Invalid report option.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0031

DN supplied is not a valid trunk route access code.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0032

Route does not auto-terminate (for SRTA command), or no members for this route (for SRTA & SPRI commands).Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0033

Member number out of range.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0034

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. Critical to Monitor: No. SNMP trap: No


System Messages

Page 32 of 2464 ACD0035

Invalid priority value.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0036

No empty position for agent in new queue.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0037

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

ACD0038

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

ACD0039

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

ACD0040

Invalid key number.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0041

Key number not reserved for agent position on supervisor's telephone.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

553-3001-411

Standard 18.00

August 2006

Page 33 of 2464 ACD0042

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

ACD0043

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

ACD0044

Only a list command (LAPA, LATS, LRTA) can be stored in the library.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0045

No message (MSG) call registers are available for sending a library command.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0046

Invalid parameter list for library command.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0047

Too many parameters for storage.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0048

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


System Messages

Page 34 of 2464 ACD0049

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

ACD0050

Data not available because of initialization.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0051

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

ACD0052

Unable to fulfill request - another report is running.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0053

Invalid input for report number.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0054

No reports requested for DTOT/STOT.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0055

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

ACD0056

High speed link does not exist.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

553-3001-411

Standard 18.00

August 2006

Page 35 of 2464 ACD0057

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

ACD0058

Invalid directory number.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0100

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

ACD0101

TLDD value must be from 10 to 1800.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0102

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

ACD0103 DN

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. Critical to Monitor: No. SNMP trap: No

ACD0104 DN

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. Critical to Monitor: No. SNMP trap: No


System Messages

Page 36 of 2464 ACD0105

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. Critical to Monitor: No. SNMP trap: No

ACD0106

Valid only for ACD Package D services.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0107

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

ACD0108

This command is only valid with the Load Management package equipped.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0109

Agent Priority is out of range. Ranges: NT and XT = 1-48 All others = 1-32 (This includes RT.)Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0115

Command is only valid when ACD Package B is equipped.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0116

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

553-3001-411

Standard 18.00

August 2006

Page 37 of 2464 ACD0117

The STOR command was not completed successfully.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0211

Call is in the TOF queue, but the TOF call bit is not set.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0212

Call is not in the TOF queue, but the TOF bit is set.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0213

A Ring Again (RGA) call is in the TOF queue.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0214

A Call Party Recall call is in the TOF queue.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0300

Package for M2216 sets is not equipped.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0301

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

ACD0302

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


System Messages

Page 38 of 2464 ACD0303

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

ACD0304

Allocate block failed.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0310

Command not available without the NACD package 178.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0311

You cannot use the NITE command with Night Tables defined in NACD.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0312

You cannot use the TLDD command with Day Tables defined in NACD.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0313

Invalid Table name. Only D (Day) and N (Night) are valid.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0314

Input value is out-of-range.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0315

The specified Target table is full.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

553-3001-411

Standard 18.00

August 2006

Page 39 of 2464 ACD0319

The Advance Network package 148 and Network ACD package 178 are required for Targets across the Network.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0320

No Night Table has been defined for this ACD-DN.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0321

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

ACD0322

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

ACD0323

Only the Senior Supervisor can execute this command.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0324

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

ACD0325

You do not have enough memory left to allocate for this routing table.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No


System Messages

Page 40 of 2464 ACD0326

You cannot define a new Day Table when this ACD-DN still has a TOFT defined.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0327

You cannot define a new Night Table when the NCFW DN is defined for this ACD-DN.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0328

The CWLF or CWLW thresholds cannot be defined or changed unless the NCWL option is set in LD 23.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0329

Commands only accepted when RPRT = Yes.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0330

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

ACD0331

Commands only valid if CCR package is equipped.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0332

That DN is not a valid Control DN.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

553-3001-411

Standard 18.00

August 2006

Page 41 of 2464 ACD0333

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

ACD0334

Commands not valid for a CDN.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0336

Cannot change the CNTL option from NO to YES if the VSID for the CDN is not defined.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0337

Cannot change the TSFT option for a CDN with CNTL set to NO.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0338

An ACD DN defined for data service access may not be used as a default ACD DN.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0339

Cannot change the TLDA option for a CDN with CNTL set to NO.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0340

Cannot change the TLDB option for a CDN with CNTL set to NO.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No


System Messages

Page 42 of 2464 ACD0341

Cannot change the TLDC option for a CDN with CNTL set to NO.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0342

Default ACD DN must be a valid ACD DN.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: No

ACD0343

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

ACD0344

RTQT must be set in range 0-30Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

ACD0345

To enable FORC please set RTQT to 0 or to enable RTQT please set FORC to no.Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

ACD0346

DN entered is not a valid MQA ACD DN.Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

ACD0347

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

ACD0348

Not valid for MQA agent.Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

553-3001-411

Standard 18.00

August 2006

Page 43 of 2464

ADD: Automatic Call Distribution Data DumpAutomatic 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.

MessagesADD0000

ADD Program is running.Action: Severity: Info. Critical to Monitor: Yes. SNMP trap: No

ADD0009

Program aborted.Action: Severity: Minor. Critical to Monitor: Yes. SNMP trap: Yes

ADD0099

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

ADD0100

High-speed link is down.Action: Severity: Minor. Critical to Monitor: Yes. SNMP trap: Yes


System Messages

Page 44 of 2464 ADD0101

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. Critical to Monitor: No. SNMP trap: Yes

ADD0102 C

ACD list cannot be found for customer c.Action: Severity: Minor. Critical to Monitor: Yes. SNMP trap: Yes

ADD0103 L S C U

Terminal Number translation failed.

Action: Severity: Minor. ADD0104 L S C U Critical to Monitor: Yes. SNMP trap: Yes

Key 0 of the set is not an ACD-DN.

Action: Severity: Minor. ADD0105 L S C U Critical to Monitor: Yes. SNMP trap: Yes

TN is not equipped.

Action: Severity: Minor. ADD0150 C Critical to Monitor: Yes. SNMP trap: Yes

No route for customer c.Action: Severity: Minor. Critical to Monitor: Yes. SNMP trap: Yes

ADD0151

No trunk number.Action: Severity: Minor. Critical to Monitor: Yes. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 45 of 2464 ADD0160

Enqueuing to send message failed. Data associated with the high-speed link may be corrupted.Action: Remove the high-speed link in software, then redefine it. If problem persists, perform a system reload or parallel reload. Severity: Minor. Critical to Monitor: Yes. SNMP trap: Yes

ADD0170

AUX did not respond to AUX_M_SIN message.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: Yes

ADD0180

The chosen release protocol by the AUX is not within the range specified by SL-1.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: Yes


System Messages

Page 46 of 2464

553-3001-411

Standard 18.00

August 2006

Page 47 of 2464

AMH: Auxiliary Message HandlerThe 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.

MessagesAMH0000

Program Identifier.Action: Severity: Info. Critical to Monitor: Yes. SNMP trap: No

AMH0001

Output buffer not empty; counter limit exceeded.Action: Check Serial Data Interface (SDI) associated with the high-speed link (see LD 48). Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

AMH0002

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. Critical to Monitor: Yes. SNMP trap: Yes

AMH0003

Cumulative Negative Acknowledgment (NAK) count exceeded due to noisy high-speed link.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes


System Messages

Page 48 of 2464 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. Critical to Monitor: Yes. SNMP trap: Yes

AMH0005

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. Critical to Monitor: Yes. SNMP trap: Yes

AMH0006

TTY I/O block pointer for high-speed link is nil. Take same action as for ADD160.Action: Remove the high-speed link in software, then redefine it. If problem persists, perform a system reload or parallel reload Severity: Minor. Critical to Monitor: Yes. SNMP trap: Yes

AMH0007

Pointer to high-speed link data 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. Critical to Monitor: Yes. SNMP trap: Yes

AMH0008

No call register available at this moment.Action: If message persists, increase the number of call registers for the customer. Severity: Minor. Critical to Monitor: Yes. SNMP trap: Yes

AMH0010

The SL-1 System ID does not match the AUX ACD_D disk directory.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 49 of 2464 AMH0011

The AUX could not select a release protocol from the high and low specified by the SL-1.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: Yes

AMH0012

MAX using protocol 31) is encountered. CMOD unit is not added into the system CMOD list.Action: A system memory corruption might have occurred. Contact your technical support group. Severity: Major. Critical to Monitor: No. SNMP trap: No

SYS0050

CPU has no spare memory module.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0051

DMI entry has been discarded due to a missing FNP (160) packageAction: Contact your technical support group. Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0052

SIDE is defined on a DASS2 route but the MMCS package is not equipped.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0053

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. Critical to Monitor: No. SNMP trap: Yes

SYS0054

Mobility related data blocks are removed. Possibly, superloop does not exist.Action: Contact your technical support group. Severity: Major. Critical to Monitor: No. SNMP trap: Yes

SYS0055

Invalid value in the EBLN ISM parameter.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 2165 of 2464 SYS0060

CPU has no spare memory module. Too many logical units, TDS or MFSD loops for I/O table.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0061

RCAP CTO or ECTO is removed during sysload because BNE package is not equipped.Action: Severity: Critical to Monitor: No. SNMP trap: Yes

SYS0062

MSMN Package unrestricted with MC32 package #350 restricted.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: Yes

SYS0063

Invalid data found while building DMC Index table for DCS units.Action: Severity: Major. Critical to Monitor: No. SNMP trap: Yes

SYS0064

Invalid data found while building DMC Index table for DCS units.Action: Severity: Major. Critical to Monitor: No. SNMP trap: Yes

SYS0065

Unable to allocate the FDL_STRUCT.Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

SYS0066

FXS info is present, but the FXS package is not equipped.Action: Sysload again with FXS package #152 equipped. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes


System Messages

Page 2166 of 2464 SYS0067

Survivability ISM exceeds Survivability ISM limit.Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

SYS0068 TN BCS data block limits have caused some keys above on TN

to be discarded.Action: Severity: Info. SYS0069 Critical to Monitor: No. SNMP trap: Yes

BCS block overflow. Some keys will be deleted.Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

SYS0070 FATAL

Primary storage medium fault. Storage medium not ready or head fault detected.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0071

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. Critical to Monitor: Yes. SNMP trap: Yes

SYS0072

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. Critical to Monitor: Yes. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 2167 of 2464 SYS0073

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. Critical to Monitor: Yes. SNMP trap: Yes

SYS0074

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. Critical to Monitor: No. SNMP trap: Yes

SYS0075

Unable to allocate protected memory for predefined set-to-set messages.Action: Contact your technical support group. Severity: Major. Critical to Monitor: No. SNMP trap: Yes

SYS0076

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. Critical to Monitor: No. SNMP trap: Yes

SYS0077

The customer data block number read from the tape record header, was found to be greater than the customer pointer array size.Action: Contact your technical support group. Severity: Major. Critical to Monitor: No. SNMP trap: Yes

SYS0078

An STS_MSG data structure was loaded from tape, but a corresponding customer data block to reference this structure does not exist.Action: Contact your technical support group. Severity: Major. Critical to Monitor: No. SNMP trap: Yes


System Messages

Page 2168 of 2464 SYS0107

An STS_MSG data structure was loaded from tape, but the STS_MSG data block does not exist for the corresponding customer.Action: Contact your technical support group. Severity: Major. Critical to Monitor: No. SNMP trap: Yes

SYS0108

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. Critical to Monitor: No. SNMP trap: Yes

SYS0109

The number of Wireless Visitors exceeds the Wireless Visitors limit and no further Wireless Visitors can be sysloaded.Action: Contact your technical support group. Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0110 l s c u

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. Critical to Monitor: Yes. SNMP trap: Yes

SYS0111

Unable to allocate protected MSDL/MISP block for CLKC.Action: Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0112

CLKC index out-of-range (238-239).Action: Severity: Info. Critical to Monitor: No. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 2169 of 2464 SYS0113

Unable to allocate protected space for CLKC P_MSDLMISP_PTR.Action: Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0114

Unable to allocate protected space for CLKC P_SID_BLK_PTR.Action: Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0115

Unable to allocate space for CLKC Physical IO Block.Action: Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0116

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. Critical to Monitor: No. SNMP trap: Yes

SYS0117

User define feature kiey label data block tn=0.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0118

User define feature key label data block pointer is nil.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0119

Overlap Package (.OVLP_PACKAGE) is not equiped hence OVLS/OVLR is set to .FALSE from .TRUE.Action: Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0120

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


System Messages

Page 2170 of 2464

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 Critical to Monitor: No. SNMP trap: Yes

UUI RCAP removed and/or UUI prompt for CDN removed, since UUI package is not equipped.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: Yes

SYS0122

No CIS ANI reception table found in customer datablock. Default table is created.Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

SYS0123

No CIS/MFC CACC table found in customer datablock. Default table with one entry is created.Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

SYS0124

No protected data storage available for default CIS ANI reception table.Action: Contact technical support. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0125

No protected data storage available for default CIS/MFC CACC table.Action: Contact technical support. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 2171 of 2464 SYS0126

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. Critical to Monitor: No. SNMP trap: Yes

SYS0127

ICON PACKAGE NOT ENABLEDAction: Severity: Minor. Critical to Monitor: No. SNMP trap: Yes

SYS0128

The number of PCAs configured exceeds the PCA ISM Limit and no further PCAs can be sysloaded.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0129

Existing M3900 language is changed from Hebrew to English since the HEBREW package is restricted.Action: Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0130

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.Action: Contact your technical support group. Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0131

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.Action: Contact your Nortel Networks Technical Support Group. Severity: Info. Critical to Monitor: No. SNMP trap: No


System Messages

Page 2172 of 2464 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. Critical to Monitor: No. SNMP trap: Yes

SYS0133

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: Critical to Monitor: No. SNMP trap: No

SYS0137

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. Critical to Monitor: No. SNMP trap: No

SYS0138

Endorsing GR data just restored.Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

553-3001-411

Standard 18.00

August 2006

Page 2173 of 2464 SYS0139

Database Replication Endorsement failed. The system will automatically be restarted for Data StepbackAction: Call your system administrator for assistance Severity: Major. Critical to Monitor: No. SNMP trap: No

SYS0140

SIP Package is restricted, therefore the SIP trunks cannot be sysloaded.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0141

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. Critical to Monitor: No. SNMP trap: Yes

SYS0142

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. Critical to Monitor: No. SNMP trap: Yes

SYS0191

Invalid TN is in the DN block; TN is rejected from DN block.Action: Severity: Critical. Critical to Monitor: No. SNMP trap: No

SYS0201

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 numberAction: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes


System Messages

Page 2174 of 2464 SYS0202 TN l s c u Station type does not match card type. Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

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. Critical to Monitor: Yes. 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. Critical to Monitor: Yes. 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 Critical to Monitor: Yes. SNMP trap: Yes

Loop number out of range.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: No. SNMP trap: Yes

SYS0207

Shelf not in configuration record (local or remote). See "Corrupted data structures" in the SYS introduction.Action: Severity: Critical. Critical to Monitor: Yes. 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. Critical to Monitor: Yes. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 2175 of 2464 SYS0209

Identical data block encountered twice.Action: Contact your technical support group. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0212

SCL DND template number exceeds length of list allocated. EDD error.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0214

Conversion error.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0216

Patch block error.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0227

Unable to allocate enough PDS for converted SL-1 station.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0229

Same as SYS0227.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0230

Customer Data Block (CDB) does not exist when loading Automatic Call Distribution (ACD) blocks.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0231

Number of ACD blocks exceeds list size.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes


System Messages

Page 2176 of 2464 SYS0232 key cust dn ACD-DN does not exist in DN tree. Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. SYS0233 Critical to Monitor: Yes. SNMP trap: Yes

Data assigned to SL-1 ACD key is invalid, or the data assigned can not be used with 500/2500 sets as ACD stations.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0234

Number of stations assigned to ACD group exceeds maximum.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0236

Authorization code data block does not exist.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0240

CDB does not exist for Direct Inward System Access (DISA) data block.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0241

Too many DISA data blocks in DISA list.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0242

Number of dial intercom groups exceeds maximum allowed in customer data block.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 2177 of 2464 SYS0246

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. Critical to Monitor: No. SNMP trap: No

SYS0250

Tree data blocks corrupted. Tree will be released.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0251

Unable to locate New Flexible Code Restriction (NFCR) pointers table.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0252

Unable to locate tree block pointers table.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0253

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. Critical to Monitor: Yes. SNMP trap: Yes

SYS0254

The number of digital telephones exceeds the Digital Telephones limit and no further digital telephones can be sysloaded.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0255

The number of analog TNs exceeds the Analog TN limit and no further analog TNs can be sysloaded.Action: Severity: Info. Critical to Monitor: No. SNMP trap: Yes


System Messages

Page 2178 of 2464 SYS0256

Unable to allocate memory for PLUGIN data blockAction: Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0257

PLUGIN pkg not equipped, PLUGIN data cleared.Action: Severity: Info. Critical to Monitor: No. SNMP trap: Yes

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. Critical to Monitor: No. SNMP trap: No

SYS0260

RCAP UUS1 is removed during sysload because BNE package is not equipped.Action: Severity: Minor. Critical to Monitor: No. SNMP trap: Yes

SYS0262

Existing EuroISDN diversion remote capability is removed since the BNE package is restricted.Action: Enable the BNE package and sysload the machine again. Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0263

Existing EuroISDN diversion remote capability is removed since the BNE package is restricted.Action: Enable the BNE package and sysload the machine again. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0264

The number of ISDN B Channels exceeds the ISDN Channel limit and no further TNs can be sysloaded.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

553-3001-411

Standard 18.00

August 2006

Page 2179 of 2464 SYS0265

The number of DTI Channel TNs exceeds the DTI Channel limit and no further TNs can be sysloaded.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0266

The number of Analog Trunk TNs exceeds the Analog Trunk TN limit and no further TNs can be sysloaded.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0267

The number of Data Port TNs exceeds the Data Ports limit and no further TNs can be sysloadec.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0268

The number of Phantom Port TNs exceeds the Phantom Ports limit and no further TNs can be sysloaded.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0269

The number of CLASS Telephine TNs exceeds the CLASS Telephines limit and no further TNs can be sysloaded.Action: Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0270

The number of Attendant Console TNs exceeds the Attendant Consoles limit and no further TNs can be sysloaded.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0271

The OAS package is disabled.Action: Severity: Major. Critical to Monitor: No. SNMP trap: Yes


System Messages

Page 2180 of 2464 SYS0273

Observe Password Table is not loaded.Action: Severity: Major. Critical to Monitor: No. SNMP trap: Yes

SYS0277

The number of ITG ISDN Trunks exceeds the ITG ISDN Trunks limit and no further trunks can be sysloaded.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0278

FFC package restricted. Changing CLS from ERCA to ERCD.Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

SYS0279

Virtual and Host Terminal data block cannot be loaded when the VIRT_OFFICE_PKG is not equipped.Action: Severity: Info. Critical to Monitor: No. SNMP trap: Yes

SYS0285

TN is removed because no more ITG cards can be added to the list.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0286

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. Critical to Monitor: Yes. SNMP trap: Yes

SYS0287

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. Critical to Monitor: Yes. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 2181 of 2464 SYS0300 tn

Customer data block does not exist.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0301

ACD supervisor key assigned to an agent station.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0302

ACD display queue key has invalid ACD DN.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0303

More than 8 supervisors are assigned to a simple ACD DN.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0304

Agent key assigned but agent does not exist.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0305

Agent key identifies agent who already has another supervisor.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0306

Agent key assigned identifies a supervisor station.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0307

Attempt to assign an ACD agent function to a non-ACD set.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes


System Messages

Page 2182 of 2464 SYS0308

Attempt to assign a 'call supervisor' key to the supervisor.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0310 key cust dn Illegal digits in DN. Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. SYS0311 Critical to Monitor: Yes. SNMP trap: Yes

Not-ready-key is assigned to a non-ACD station.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0312

CAS key assigned to SL-1 telephone but CAS data blocks do not exist.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0315

A function requiring an LED is assigned to a non-LED key.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0316

CAS key assigned to SL-1 telephone but CAS data blocks do not exist.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0317

More than 10 CAS keys have been assigned to SL-1 telephones.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0330TN l s c u Shorter DN already exists. For SYS033XXXX, XXXX is the DN concerned. Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 2183 of 2464 SYS0340 TN l s c u Longer or equal length DN already exists. Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. SYS0350 N l s c u Critical to Monitor: Yes. SNMP trap: Yes

Mixed Appearance DN block is corrupted.

Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0360 TN l s c u Trunk member number out-of-range. Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0370 TN l s c u Route data block does not exist. Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0380 TN l s c u Attendant member number out of range or in use. Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. SYS0385 Critical to Monitor: Yes. SNMP trap: Yes

TN of the terminal is not the prime DN of attendant.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0390 TN l s c u Attendant Directory Number block of wrong type. Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. SYS0391 Critical to Monitor: Yes. SNMP trap: Yes

Invalid TN for attendant.Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes


System Messages

Page 2184 of 2464 SYS0400 TN l s c u Assigned DN has more than 30 stations. Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0410 TN l s c u DN call type in conflict, i.e., single vs multiple. Action: See "Corrupted data structures" in the SYS introduction. Severity: Critical. SYS0420 Critical to Monitor: Yes. SNMP trap: Yes

Network loop in configuration record conflicts with existing loop.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0421

Tone loop in configuration record conflicts with existing loop.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0422

Conference loop in configuration record conflicts with existing loop.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0423

MF Sender in configuration record conflicts with existing loop.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0430

Private DN in trunk data block conflicts with existing DN.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0500

CPU test failed on nonactive CPU.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

553-3001-411

Standard 18.00

August 2006

Page 2185 of 2464 SYS0510

Changeover and Memory Arbitrator (CMA) pack failed to respond. Faulty CMA pack.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0514

The loop does not exist in LD 73.Action: Severity: Info. Critical to Monitor: No. SNMP trap: No

SYS0520

Unable to find data for other CPU after switchover.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0600

Emergency conference group out-of-range (0 to 9).Action: Check data. Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0601

Emergency conference member out-of-range (1 to 10).Action: Check data. Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0602

Software problem.Action: If message persists, call manufacturer. Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0603

Two TNs assigned as the same member of the same group.Action: Check data. Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0606 id index

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


System Messages

Page 2186 of 2464

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. SYS0607 id index Critical to Monitor: Yes. SNMP trap: Yes

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 Critical to Monitor: Yes. SNMP trap: Yes

More than one ESN data block was loaded from storage medium for the same customer.


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.


Insufficient protected data store for supplementary digit pointer block.


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.

Action: See SYS606 for output data. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 2187 of 2464 SYS0612 id index

More than one supplementary digit restriction block was found on storage medium for the same customer and index.


Insufficient protected data store memory space to set up the route list pointer block.


Route list index read from the storage medium record header greater than the maximum value, which is stored in the ESN data block.


More than one route list block was found on storage medium for the same customer and index.


Insufficient protected data store memory space to set up the digit manipulation pointer block.


Digit manipulation index read from the storage medium record header is greater than the maximum value, which is stored in the ESN data block.

Action: See SYS606 for output data. Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes


System Messages

Page 2188 of 2464 SYS0618 id index

More than one digit manipulation block was found on storage medium for the same customer and index.


More than one location route block was found on storage medium for the same customer and index.


Insufficient protected data store memory space to set up a block in the network translation tree.


One of the translation table digits read from the storage medium is out-of-range.


The same sequence of digits has been read from storage medium for the specified network translation table.

Action: See SYS606 for output data. Severity: Critical. SYS0626 Critical to Monitor: Yes. SNMP trap: Yes

NARS is not available.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0627

Translation data is corrupted.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

553-3001-411

Standard 18.00

August 2006

Page 2189 of 2464 SYS0628

Route list pointer.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0629

Trunk route data.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0630

Location route data.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0631

Route list entry data.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0632

Insufficient protected data store memory space to set up the Free Calling Area Screening (FCAS) pointer block.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0633

More than one FCAS NXX block was found on storage medium for the same customer, index and NPA.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0634

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. Critical to Monitor: Yes. SNMP trap: Yes


System Messages

Page 2190 of 2464 SYS0638

NARS-Invalid NXX.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0639

NARS-FCAS data cannot be accessed.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0640

Cannot perform data conversion for this generic/release/version of storage medium.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

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. Critical to Monitor: Yes. SNMP trap: Yes

SYS0642

The customer data block number read from the storage medium record header is greater than the customer data block pointer size.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0643

No customer data block exists to which authcode can be attached.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0644

The block number read from the storage medium record header does not match the expected block number.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

553-3001-411

Standard 18.00

August 2006

Page 2191 of 2464 SYS0645

More than one block was read from storage medium with the same block identification.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0646

The authcode header table (AUTH_TABLE_BLK) does not exist to which the remaining authcode data blocks may be attached.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0647

Authcode conversion can occur only in conjunction with the BAUT package and not the NAUT package.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

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. Critical to Monitor: Yes. SNMP trap: No

SYS0649

Attempt to allocate protected data store memory space failed.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: Yes

SYS0650

During conversion, two authcodes which contained identical digits were loaded.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No

SYS0653

Cannot allocate space for NCTL block which should be split from the ESN data block.Action: Severity: Critical. Critical to Monitor: Yes. SNMP trap: No


System Messages

Page 2192 of 2464 SYS0654

More than one Coordinated Dialing Plan (CDP) list was found on stora

Documents

Mensajes 553-3001-411_18.00