Lucent Technologies Home Theater Server 555 233 119 User Manual
DEFINITY®  
Enterprise Communications Server  
Release 8.2  
Maintenance for R8.2csi  
555-233-119  
Comcode 108678665  
Issue 1  
April 2000  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
iii  
Contents  
Contents  
iii  
About This Book  
xv  
■ Purpose  
xv  
■ Intended Audience  
xv  
■ Organization  
xvi  
■ Typographic conventions  
■ Admonishments  
xvii  
xvii  
xviii  
xviii  
xix  
■ Safety Precautions  
■ Security Issues  
■ Standards Compliance  
■ Electromagnetic Compatibility Standards  
■ Trademarks and Service Marks  
■ Related Documents  
xix  
xxi  
xxii  
xxii  
xxiv  
xxiv  
xxv  
■ Federal Communications Commission Statement  
■ How to Order Documentation  
■ How to Comment on This Document  
■ Where to Call for Technical Support  
1
Maintenance for csi systems  
■ What’s new for R8csi  
1-1  
1-1  
■ How to use the Maintenance book  
■ csi design  
1-6  
1-11  
1-14  
1-14  
1-15  
1-15  
1-18  
1-20  
1-24  
1-26  
1-38  
1-39  
1-40  
1-42  
■ Circuit Packs  
■ Maintenance Objects  
■ Alarm and Error Reporting  
■ Maintenance Testing  
■ Preventive Maintenance Procedures  
■ Initialization and Recovery  
■ Set Neon Voltage (Ring Ping)  
■ Logging On/Off  
■ Procedure for SPE-Down Mode  
■ Reseating/Replacing Circuit Packs  
■ Removing Power  
■ Restoring Power  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
iv  
■ System Backup  
1-43  
1-47  
1-71  
1-84  
1-90  
1-98  
1-101  
1-102  
1-132  
■ Troubleshooting Features  
■ Install DS1 CPE Loopback Jack (T1 Only)  
■ LED Interpretation  
■ Multimedia Call Handling  
■ TN760D Tie Trunk Option Settings  
■ TN464E/F Option Settings  
■ ATM Tips  
■ Unusual ATM trouble conditions  
■ Troubleshooting Multimedia Call Handling  
(MMCH)  
1-135  
2
Maintenance Commands  
■ System Command Structure  
■ busyout access-endpoint  
■ busyout board  
2-1  
2-1  
2-2  
2-3  
■ busyout cdr-link  
2-5  
■ busyout data-module  
■ busyout journal-printer  
■ busyout link  
2-6  
2-7  
2-9  
■ busyout mis  
2-10  
2-11  
2-12  
2-13  
2-15  
2-15  
2-16  
2-17  
2-18  
2-20  
2-20  
2-22  
2-24  
2-24  
2-36  
2-37  
■ busyout pms-link  
■ busyout port  
■ busyout pri-endpoint  
■ busyout sp-link  
■ busyout station  
■ busyout tdm  
■ busyout tone-clock  
■ busyout trunk  
■ cancel hardware-group  
■ change circuit-packs  
■ change synchronization  
■ change system-parameters customer-options  
■ change system-parameters maintenance  
■ clear audits  
■ clear errors  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
v
■ clear interface  
2-37  
2-38  
2-38  
2-39  
2-39  
2-39  
2-39  
2-40  
2-40  
2-41  
2-41  
2-41  
2-47  
2-58  
2-59  
2-60  
2-61  
2-67  
2-69  
2-72  
2-73  
2-75  
2-76  
2-77  
2-79  
2-88  
2-91  
2-92  
2-95  
2-95  
2-95  
2-96  
2-97  
2-97  
2-97  
■ clear isdn-testcall  
■ clear link  
■ clear mst  
■ clear pkt  
■ clear port  
■ disable administered-connection  
■ disable mst  
■ disable suspend-alm-orig  
■ disable synchronization-switch  
■ disable test-number  
■ display alarms  
■ display capacity  
■ display communication-interface hop-channels  
■ display communication-interface links  
■ display disabled-tests  
■ display errors  
■ display events  
■ display initcauses  
■ display memory-configuration  
■ display node-names  
■ display port  
■ display synchronization  
■ display system-parameters duplication  
■ display system-parameters maintenance  
■ display test-schedule  
■ display time  
■ download update-file  
■ enable administered-connection  
■ enable mst  
■ enable suspend-alm-orig  
■ enable synchronization-switch  
■ enable test-number  
■ format card-mem  
■ get vector  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
vi  
■ list communication-interface processor-channel  
■ list configuration  
■ list configuration software-version  
■ list disabled-mos  
■ list external-device alarm  
■ list history  
2-99  
2-101  
2-104  
2-109  
2-110  
2-111  
2-114  
2-115  
2-116  
2-117  
2-119  
2-121  
2-125  
2-149  
2-150  
2-151  
2-156  
2-157  
2-161  
2-164  
2-165  
2-171  
2-173  
2-174  
2-175  
2-179  
2-179  
2-180  
2-181  
2-182  
2-183  
2-185  
2-186  
2-187  
2-188  
■ list ip-route  
■ list isdn-testcall  
■ list marked-ports  
■ list measurements clan ethernet  
■ list measurements clan ppp  
■ list measurements ds-1  
■ list mst  
■ list suspend-alm-orig  
■ list sys-link  
■ list testcalls  
■ mark port  
■ monitor bcms  
■ monitor health  
■ monitor security-violations  
■ monitor system  
■ monitor traffic  
■ monitor trunk  
■ netstat ip-route  
■ ping  
■ recycle carrier  
■ release access-endpoint  
■ release board  
■ release cdr-link  
■ release data-module  
■ release journal-printer  
■ release link  
■ release mis  
■ release modem-pool  
■ release pms-link  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
vii  
■ release port  
2-189  
2-190  
2-191  
2-192  
2-193  
2-194  
2-195  
2-196  
2-197  
2-197  
2-198  
2-198  
2-199  
2-199  
2-200  
2-202  
2-203  
2-204  
2-205  
2-211  
2-212  
2-212  
2-213  
2-214  
2-214  
2-216  
2-217  
2-218  
2-219  
2-228  
2-234  
2-237  
2-239  
2-239  
2-275  
■ release pri-endpoint  
■ release sp-link  
■ release station  
■ release tdm  
■ release tone-clock  
■ release trunk  
■ reset board  
■ reset io-processor  
■ reset interface  
■ reset packet-interface  
■ reset switch-control  
■ reset system  
■ reset translation-id  
■ restore announcements  
■ resume hardware-group  
■ save announcements  
■ save translation  
■ set options  
■ set signaling-group  
■ set synchronization  
■ set tdm  
■ set time  
■ set tone-clock  
■ set vector  
■ status access-endpoint  
■ status administered-connection  
■ status attendant  
■ status audits  
■ status bri-port  
■ status card-mem  
■ status cdr-link  
■ status cleared-alarm-notif  
■ status conference  
■ status data-module  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
viii  
■ status esm  
2-276  
2-277  
2-279  
2-282  
2-283  
2-284  
2-285  
2-290  
2-291  
2-292  
2-294  
2-296  
2-298  
2-299  
2-301  
2-302  
2-304  
2-308  
2-311  
2-312  
2-314  
2-315  
2-320  
2-323  
2-325  
2-328  
2-330  
2-331  
2-333  
2-335  
2-337  
2-340  
2-346  
2-348  
2-349  
■ status hardware-group  
■ status health  
■ status interface  
■ status isdn-testcall  
■ status journal-link  
■ status link n  
■ status packet-interface  
■ status pms-link  
■ status pri-endpoint  
■ status processor-channel  
■ status signaling-group  
■ status sp-link  
■ status station  
■ status synchronization  
■ status sys-link  
■ status system  
■ status trunk  
■ status tsc-administered  
■ status tti  
■ test access-endpoint  
■ test alarms  
■ test analog-testcall  
■ test board  
■ test card-mem  
■ test cdr-link  
■ test customer-alarm  
■ test data-module  
■ test ds1-loop  
■ test eda-external-device-alrm  
■ test environment  
■ test hardware-group  
■ test inads-link  
■ test interface  
■ test isdn-testcall  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
ix  
■ test journal-printer  
■ test led  
2-351  
2-353  
2-354  
2-357  
2-359  
2-360  
2-362  
2-365  
2-367  
2-369  
2-371  
2-372  
2-374  
2-376  
2-378  
2-381  
2-383  
2-385  
2-387  
2-388  
2-390  
■ test memory  
■ test network-control  
■ test pkt  
■ test packet-interface  
■ test pms-link  
■ test port  
■ test pri-endpoint  
■ test processor  
■ test signaling-group  
■ test sp-link  
■ test station  
■ test synchronization  
■ test sys-link  
■ test tdm  
■ test tone-clock  
■ test trunk  
■ test tsc-administered  
■ traceroute  
■ upgrade software  
3
Maintenance Objects  
3-1  
■ 12V-PWR (12 Volt Power Supply)  
■ ADM-CONN (Administered Connection)  
■ ADX8D-BD (AUDIX Circuit Pack)  
■ ADX8D-PT (AUDIX Digital Port)  
■ ADX16D-B (16 Port AUDIX Circuit Pack)  
■ ADX16A-BD (AUDIX Circuit Pack)  
■ ADX16D-P (16-Port AUDIX Digital Port)  
■ ADX16A-PT (AUDIX Analog Line/Control Link)  
■ ALARM-PT (ALARM PORT)  
3-1  
3-5  
3-9  
3-10  
3-17  
3-18  
3-19  
3-27  
3-34  
3-35  
3-51  
■ ANL-24-L (24-Port Analog Line)  
■ ANL-BD (Analog Line Circuit Pack)  
■ ANL-LINE (8-Port Analog Line),  
ANL-NE-L (8-Port Neon Analog Line)  
3-52  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
x
■ AN-LN-PT (Analog Line  
Port)  
3-72  
■ ANN-BD (Announcement Circuit Pack)  
■ ANN-PT (Announcement Port)  
■ ANNOUNCE (Announce)  
3-92  
3-110  
3-121  
3-125  
3-139  
3-142  
3-187  
3-190  
■ ATM-BCH (ATM B-Channel Trunk)  
■ ATM-DCH (ATM D-Channel Port)  
■ ATM-EI (Expansion Interface Circuit Pack)  
■ ATM-INTF (TN2305/6)  
■ ATM-NTWK (ATM Network Error)  
■ ATM PNC-DUP  
(ATM PNC Duplication)  
3-198  
3-209  
3-220  
■ ATM-SGRP (ATM Signaling Group)  
■ ATM-SYNC (ATM Synchronization)  
■ ATM-TRK (Circuit Emulation Service  
Circuit Pack)  
3-227  
3-258  
■ AXA12-BD/ADX8D-BD/AXD12-BD (AUDIX  
Circuit Packs)  
■ AXA12-RS/ADX8D-RS/AXD12-RS (AUDIX  
Reserve Slots)  
3-259  
3-260  
3-267  
■ BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack)  
■ BRI-DAT (ISDN-BRI)  
■ BRI-PORT (ISDN-BRI Port),  
ABRI-PORT (ASAI ISDN-BRI Port)  
3-268  
3-290  
3-318  
3-324  
3-327  
3-347  
3-365  
3-366  
3-372  
3-373  
3-389  
3-415  
3-416  
3-419  
■ BRI-SET, ASAI-ADJ, BRI-DAT  
■ CABINET (Cabinet Sensors)  
■ CAP-MEM (Memory Card Capacity)  
■ CARD-MEM (Memory Card)  
■ CLAN-BD (Control LAN Circuit Pack)  
■ CLSFY-BD (Call Classifier Circuit Pack)  
■ CLSFY-PT (Call Classifier Port)  
■ CO-BD (Central Office Trunk Circuit Pack)  
■ CO-DS1 (DS1 CO Trunk)  
■ CO-TRK (CO Trunk)  
■ CONFIG (System Configuration)  
■ CUST-ALM (Customer-Provided Alarming Device)  
■ DATA-BD (Data Channel Processor Circuit Pack)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
xi  
■ DATA-CHL (Data Channel)  
■ DATA-CON (Network Control Driver)  
■ DAT-LINE (Data Line)  
3-424  
3-449  
3-451  
3-459  
3-460  
3-461  
3-472  
3-489  
3-490  
3-498  
3-523  
■ DETR-BD (International Version)  
■ DID-BD (Direct Inward Dial Trunk Circuit Pack)  
■ DID-DS1 (DS1 DID Trunk)  
■ DID-TRK (DID Trunk)  
■ DIG-BD (Digital Line Circuit Pack)  
■ DIG-IP-STN (Digital IP Station)  
■ DIG-LINE (Digital Line)  
■ DIOD-DS1 (DS1 DIOD Trunk)  
■ DIOD-TRK (DIOD Trunk), DIOD-BD  
(DIOD Circuit Pack)  
3-534  
3-535  
3-545  
3-548  
3-622  
3-623  
3-628  
3-630  
3-640  
3-643  
3-644  
3-655  
3-662  
3-665  
■ DIOD-TRK (DIOD Trunk)  
■ DLY-MTCE (MO-DAILY)  
■ DS1-BD (DS1 Interface Circuit Pack)  
■ DT-LN-BD (Data Line Circuit Pack)  
■ DTMR-PT [Dual Tone Multifrequency Port (TTR)]  
■ E-DIG-BD (Multi Application Platform Board)  
■ E-DIG-STA (Emulated Digital Line)  
■ EMG-XFER  
■ ERR-LOG (Error Log)  
■ ETH-PT (Control LAN Ethernet)  
■ ETR-PT (Enhanced Tone Receiver Port)  
■ EXT-DEV ADMIN? N (External Device Alarm)  
■ EXT-DEV ADMIN? Y (External Device Alarm)  
■ GPTD-PT [General Purpose Tone  
Detector Port (CPTR)]  
3-668  
3-669  
3-671  
3-677  
3-683  
3-684  
3-705  
3-708  
3-711  
■ H323-BCH (H.323 B-Channel)  
■ H323-SGRP (H.323 Signaling Group)  
■ H323-STN (H.323 IP Station)  
■ HYB-BD (Hybrid Line Circuit Pack)  
■ HYB-LINE (Hybrid Line)  
■ INADS (INADS Link)  
■ IO-PROCR (I/O Processor)  
■ ISDN-PLK (ISDN-PRI Signaling Link Port)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
xii  
■ ISDN-SGR (ISDN-PRI Signaling Group)  
■ ISDN-TRK (DS1 ISDN Trunk)  
■ LOG-SVN (Login Security Violation)  
■ JNL-PRNT (Journal Printer Link)  
■ MAPD-BD (MAPD Interface Circuit Pack TN802)  
■ MEDPRO (Media Processor MAPD Circuit Pack)  
■ MEDPROPT (TN802 MED PRO DSP PORT)  
■ MET-BD (MET Line Circuit Pack)  
■ MET-LINE (MET Line)  
3-717  
3-733  
3-760  
3-763  
3-764  
3-794  
3-806  
3-812  
3-813  
3-832  
3-833  
3-842  
3-845  
3-851  
3-853  
3-865  
3-885  
3-894  
3-914  
3-922  
3-928  
3-941  
3-954  
3-961  
3-968  
3-975  
3-976  
3-980  
3-981  
3-994  
3-995  
3-1003  
3-1010  
3-1015  
3-1021  
■ MIS (Management Information System)  
■ MMI-BD  
■ MMI-LEV (Multimedia Interface Resource Level)  
■ MMI-PT  
■ MMI-SYNC  
■ OPS-LINE (DS1 OPS Line)  
■ PE-BCHL (PRI Endpoint Port)  
■ PKT-BUS (Packet Bus)  
■ PKT-INT (Packet Interface)  
■ PMS-LINK (Property Management System Link)  
■ PMS-PRNT/JNL-PRNT (PMS Printer Link)  
■ PPP-PT (Control LAN Packet/Port)  
■ PR-MAINT (Maintenance Processor)  
■ PR-MEM (RISC Memory)  
■ PRI-CDR/SEC-CDR (PRI-CDR Link)  
■ PROCR (RISC Processor Circuit Pack TN798)  
■ PROC-SAN (Process Sanity Audits)  
■ RING-GEN (Analog Ring Generator)  
■ S-SYN-BD (Speech Synthesis Circuit Pack)  
■ S-SYN-PT (Speech Synthesis Port)  
■ SEC-CDR (SEC-CDR Link Maintenance)  
■ SW-CTL (Switch Control)  
■ SYNC (Synchronization)  
■ SYS-LINK (System Links)  
■ SYS-PRNT (System Printer)  
■ SYSTEM (System)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
xiii  
■ TBRI-BD (TN2185  
ISDN Trunk-Side BRI)  
3-1023  
3-1031  
■ TBRI-PT (TN2185  
ISDN Trunk-Side BRI Port)  
■ TBRI-TRK (TN2185  
ISDN Trunk-Side BRI)  
3-1051  
3-1062  
3-1063  
3-1079  
3-1089  
3-1090  
3-1106  
3-1128  
3-1139  
3-1147  
■ TDMODULE (Trunk Data Module)  
■ TDM-BUS (TDM Bus)  
■ TDM-CLK (TDM Bus Clock)  
■ TIE-BD (Tie Trunk Circuit Pack)  
■ TIE-DS1 (DS1 Tie Trunk)  
■ TIE-TRK (Tie Trunk)  
■ TONE-BD (Tone-Clock Circuit Pack)  
■ TONE-PT (Tone Generator)  
■ TRANS-ID (Translation-ID)  
■ TR-LN-BD (Trunk Line  
Board)  
3-1152  
■ TSC-ADM (Administered Temporary  
Signaling Connections)  
3-1153  
3-1159  
3-1163  
3-1257  
3-1261  
■ TTR-LEV (TTR Level)  
■ UDS1-BD (UDS1 Interface Circuit Pack)  
■ VC-BD  
■ VC-DSPPT  
■ VC-LEV (Voice Conditioner  
DSP Port Level)  
3-1270  
3-1273  
3-1278  
3-1285  
■ VC-SUMPT  
■ WAE-PORT (Wideband Access Endpoint Port)  
■ XXX-BD (Common Port Circuit Pack)  
IN Index  
IN-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Contents  
xiv  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
Purpose  
xv  
About This Book  
Purpose  
This book contains the information needed to monitor, test, and maintain  
DEFINITY® Enterprise Communications Server (ECS) csi system and covers  
many of the faults and troubles that can occur in the system. Most maintenance  
requirements are simple procedures due to the modular, self-testing nature of the  
system.  
Simple, traditional troubleshooting methods are sometimes sufficient to locate  
and clear faults. The traditional methods include terminal substitution, visual  
inspections, continuity checks, and clarification of operating procedures with  
users.  
Intended Audience  
The information in this book is intended for use by:  
■
A maintenance technician dispatched to a DEFINITY System site in  
response to a trouble alarm or a user trouble report  
■
■
A maintenance technician located at a remote maintenance facility  
The user’s assigned maintenance technician. The technician is expected  
to have a knowledge of telecommunications fundamentals and of the  
DEFINITY Enterprise Communications Server systems to the extent that  
the procedures in this book can be performed, in most cases, without  
assistance.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
Organization  
xvi  
Each DEFINITY System has a user-designated System Manager who is  
responsible for system administration and with whom the maintenance  
technician should work closely.  
This book is not intended to solve all levels of troubles. It is limited to troubles that  
can be solved by using the Alarm Log, Error Log, trouble-clearing procedures,  
maintenance tests, and traditional troubleshooting methods. If the trouble still has  
not been resolved, it is the responsibility of the maintenance technician to  
escalate the problem to a higher level of technical support. Escalation should  
conform to the procedures in the Technical and Administration Escalation Plan.  
Organization  
This book consists of two volumes: Volume 1 contains Chapters 1 and 2; Volume  
2 contains Chapter 3.  
■
Chapter 1, ‘‘Maintenance for csi systems’’ describes the system’s design  
and maintenance strategy, including circuit packs, how power is supplied  
to the system, the various reset and reboot processes (and how these  
processes are used to perform maintenance and to recover systems or  
subsystems that are out of service), common maintenance tasks  
(including removing and installing circuit packs, removing and restoring  
power, system backups, upgrading software, and various testing and  
troubleshooting procedures), and interpreting circuit pack LEDs.  
■
■
Chapter 2, ‘‘Maintenance Commands’’ explains how to use the  
maintenance commands including specific command syntax, typical  
forms, and display output.  
Chapter 3, ‘‘Maintenance Objects’’ has specific troubleshooting and repair  
instructions for every maintenance component in the system. This chapter  
also contains repair procedures for system-alarmed and user- reported  
troubles. For each Maintenance Object (MO), a table lists the alarm level,  
hardware error associated with the MO, the associated test that caused  
the error, the test sequences and the specific command line entry  
required to run the tests, and a brief description of each test. Explanations  
of error codes associated with each test are given along with specific  
maintenance procedures used to resolve each problem.  
The individual maintenance objects are labeled with the name of the MO  
exactly as the name appears in the Alarm Log; for example, MAINT (for  
Maintenance circuit pack). The only exception is the Common Port Circuit  
Pack that uses “XXX-BD” for its maintenance name. The XXX-BD section  
contains a set of common tests used by certain circuit packs listed in the  
section. The common portion of these circuit packs is the generic  
hardware that interfaces with the Time Division Multiplex (TDM) Bus.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
Typographic conventions  
xvii  
Typographic conventions  
This document uses the following typographic conventions:  
■
■
■
Information you type at the management terminal is shown in the following  
typeface: list system-parameters maintenance.  
Information displayed on the management terminal screen is shown in the  
following typeface: login.  
Keyboard keys are shown in the following typeface: Enter.  
The following conventions describe the systems referred to in this document.  
■
The word “system” generally refers to the DEFINITY Enterprise  
Communications Server.  
■
Circuit pack codes (such as TN798 or TN2182B) are shown with the  
minimum acceptable alphabetic suffix (like the “B” in the code TN2182B).  
Generally, an alphabetic suffix higher than that shown is also acceptable.  
However, not every vintage of either the minimum suffix or a higher suffix  
code is necessarily acceptable.  
NOTE:  
Refer to Technical Monthly: Reference Guide for Circuit Pack  
Vintages and Change Notices, for current information about the  
usable vintages of specific circuit pack codes (including the suffix).  
The term “ASAI” is synonymous with the newer CallVisor ASAI.  
■
DEFINITY Enterprise Communications Server is abbreviated as DEFINITY  
ECS.  
Admonishments  
Admonishments used in this book have the following meanings:  
!
!
!
CAUTION:  
This sign is used to indicate possible harm to software, possible loss  
of data, or possible service interruptions.  
WARNING:  
This sign is used where there is possible harm to hardware or  
equipment.  
DANGER:  
This sign is used to indicate possible harm or injury to people.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
Safety Precautions  
xviii  
Safety Precautions  
When performing maintenance or translation procedures on the system, users  
must observe certain precautions. Observe all caution, warning, and danger  
admonishments to prevent loss of service, possible equipment damage, and  
possible personal injury. In addition, the following precautions regarding  
electromagnetic interference (EMI) and static electricity must be observed:  
Electromagnetic Interference  
This equipment generates, uses, and can radiate radio frequency energy.  
Electromagnetic fields radiating from the switch may cause noise in the  
customer’s equipment. If the equipment is not installed and used in accordance  
with the instruction book, radio interference may result.  
!
WARNING:  
To maintain the EMI integrity of the system, maintenance personnel must  
ensure that all cabinet panels, covers, and so forth, are firmly secured  
before leaving the customer’s premises.  
Static Electricity  
To prevent or reduce electrostatic discharge (ESD), maintenance personnel must  
always attach wrist grounding straps before working on switch components or  
handling circuit packs.  
!
CAUTION:  
Electrostatic discharge can damage or destroy circuit packs containing  
integrated circuits (ICs).  
The ESD wrist strap, cable assembly, and spare fuses are packed in a plastic  
bag and placed in the top of the system cabinet. Use the ESD wrist strap when  
troubleshooting, performing maintenance, or handling any circuit packs  
associated with the system.  
Security Issues  
A number of matters concerning maintenance are affected by security issues.  
For details, be sure to consult the BCS Products Security Handbook,  
555-025-600.  
!
CAUTION:  
Login security is an attribute of the DEFINITY® Enterprise Communications  
Server (ECS) Release 8.2 software.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
Standards Compliance  
xix  
Standards Compliance  
The equipment presented in this document complies with the following (as  
appropriate):  
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
ITU-T (Formerly CCITT)  
ECMA  
ETSI  
IPNS  
DPNSS  
National ISDN-1  
National ISDN-2  
ISO-9000  
ANSI  
FCC Part 15 and Part 68  
EN55022  
EN50081  
EN50082  
CISPR22  
Australia AS3548 (AS/NZ3548)  
Australia AS3260  
IEC 825  
IEC950  
UL 1459  
UL1950  
CSA C222 Number 225  
TS001  
Electromagnetic Compatibility  
Standards  
This product complies with and conforms to the following:  
■
Limits and Methods of Measurements of Radio Interference  
Characteristics of Information Technology Equipment, EN55022  
(CISPR22), 1993  
■
EN50082-1, European Generic Immunity Standard  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
Electromagnetic Compatibility Standards  
xx  
■
■
FCC Parts 15 and 68  
Australia AS3548  
NOTE:  
The system conforms to Class A (industrial) equipment; voice  
terminals meet Class B requirements.  
■
■
■
■
■
■
■
Electrostatic Discharge (ESD) IEC 1000-4-2  
Radiated radio frequency field IEC 1000-4-3  
Electrical Fast Transient IEC 1000-4-4  
Lightning effects IEC 1000-4-5  
Conducted radio frequency IEC 1000-4-6  
Mains frequency magnetic field IEC 1000-4-8  
Low frequency mains disturbance  
The system conforms to the following:  
■
Electromagnetic compatibility General Immunity Standard, part 1;  
residential, commercial, light industry, EN50082-1, CENELEC, 1991  
■
Issue 1 (1984) and Issue 2 (1992), Electrostatic discharge immunity  
requirements (EN55024, Part 2) IEC 1000-4-2  
■
■
Radiated radio frequency field immunity requirements IEC 1000-4-3  
Electrical fast transient/burst immunity requirements IEC 1000-4-4  
European Union Standards  
Lucent Technologies Business Communications Systems declares that the  
DEFINITY equipment specified in this document bearing the “CE” mark conforms  
to the European Union Electromagnetic Compatibility Directives.  
The “CE” (Conformité Europeénne) mark indicates conformance to the:  
■
■
■
■
European Union Electromagnetic Compatibility Directive (89/336/EEC)  
Low Voltage Directive (73/23/EEC)  
Telecommunication Terminal Equipment (TTE) Directive (91/263/EEC)  
i-CTR3 Basic Rate Interface (BRI) and i-CTR4 Primary Rate Interface (PRI)  
as applicable.  
The “CE” mark is applied to the following products:  
■
■
■
Global AC powered Multi-Carrier Cabinet (MCC)  
DC powered Multi-Carrier Cabinet (MCC) with 25-Hz ring generator  
AC powered Single-Carrier Cabinet (SCC) with 25-Hz ring generator  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
Trademarks and Service Marks  
xxi  
■
■
AC powered Compact Single-Carrier Cabinet (CSCC) with 25-Hz ring  
generator  
Enhanced DC Power System  
Trademarks and Service Marks  
The following are trademarks or registered trademarks of Lucent Technologies:  
■
■
■
■
■
■
■
■
■
■
5ESS™, 4ESS™  
®
AUDIX  
®
Callvisor  
®
Callmaster  
CentreVu™  
®
CONVERSANT  
®
DEFINITY  
®
DIMENSION  
®
MERLIN  
®
VOICE POWER  
The following are trademarks or registered trademarks of AT&T:  
®
■
■
■
■
■
ACCUNET  
®
DATAPHONE  
®
MEGACOM  
®
MULTIQUEST  
®
TELESEER  
The following are trademarks or registered trademarks of other companies:  
®
■
■
■
■
■
■
■
Ascend (registered trademark of Ascend, Inc.)  
®
Audichron (registered trademark of the Audichron Company)  
®
MS-DOS (registered trademark of the Microsoft Corporation)  
®
MicroChannel (registered trademark of IBM Systems)  
®
MULTIQUEST (registered trademark of Telecommunications Service)  
®
PagePac (trademark of the Dracon Division of the Harris Corporation)  
®
UNIX (trademark of the Novell Corporation)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
Related Documents  
xxii  
Related Documents  
DEFINITY ECS Release 8.2 — Installation and Test for Compact Modular  
Cabinets, 555-233-118  
Provides procedures and information for hardware installation and initial testing  
of compact modular cabinets.  
DEFINITY ECS Release 8.2— Installation for Adjuncts and Peripherals,  
555-233-116  
Provides procedures and information for hardware installation and initial testing  
of ECS adjunct and peripheral systems and equipment.  
BCS Products Security Handbook, 555-025-600  
Provides information about the risks of telecommunications fraud and measures  
for addressing those risks and preventing unauthorized use of BCS products.  
This document is intended for telecommunications managers, console operators,  
and security organizations within companies.  
Federal Communications Commission  
Statement  
Part 68: Statement  
Part 68: Answer-Supervision Signaling. Allowing this equipment to be operated in  
a manner that does not provide proper answer-supervision signaling is in  
violation of Part 68 rules. This equipment returns answer-supervision signals to  
the public-switched network when:  
■
■
■
Answered by the called station  
Answered by the attendant  
Routed to a recorded announcement that can be administered by the CPE  
user  
This equipment returns answer-supervision signals on all DID calls forwarded  
back to the public-switched telephone network, with these exceptions:  
■
■
■
A call is unanswered  
A busy tone is received  
A reorder tone is received  
This equipment is capable of providing users access to interstate providers of  
operator services through the use of access codes. Modification of this  
equipment by call aggregators to block access dialing codes is a violation of the  
Telephone Operator Consumers Act of 1990.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
Federal Communications Commission Statement  
xxiii  
This equipment complies with Part 68 of the FCC Rules. On the rear of this  
equipment is a label that contains, among other information, the FCC registration  
number and ringer equivalence number (REN) for this equipment. If requested,  
this information must be provided to the telephone company. The REN is used to  
determine the number of devices connected to the telephone line. Excessive  
RENs on the telephone line may result in devices not ringing in response to an  
incoming call. In most, but not all areas, the sum of RENs should not exceed 5.0.  
To be certain of the number of devices that can be connected to a line, as  
determined by the total RENs, contact the local telephone company.  
NOTE:  
REN is not required for some types of analog or digital facilities.  
Means of Connection  
Connection of this equipment to the telephone network is shown in the following  
table.  
Manufacturer’s Port  
Identifier  
SOC/REN/  
A.S. Code Network Jacks  
FIC Code  
OL13C  
Off/On Premises Station  
9.0F  
RJ2GX, RJ21X,  
RJ11C  
DID Trunk  
02RV2-T  
02GS2  
0.0B  
0.3A  
0.3A  
9.0F  
6.0P  
RJ2GX, RJ21X  
RJ21X  
CO Trunk  
CO Trunk  
02LS2  
RJ21X  
Tie Trunk  
TL31M  
RJ2GX  
1.544 Digital Interface  
1.544 Digital Interface  
120A2 Channel Service Unit  
04DU9-B, C  
RJ48C, RJ48M  
RJ48C, RJ48M  
RJ48C  
04DU9-BN, KN 6.0P  
04DU9-DN 6.0P  
If the terminal equipment (DEFINITY® System) causes harm to the telephone  
network, the telephone company may notify you in advance that temporary  
discontinuance of service is be required. But if advance notice is not practical,  
the telephone company may notify the customer as soon as possible. Also, you  
will be advised of your right to file a complaint with the FCC if you believe it is  
necessary.  
The telephone company may make changes in its facilities, equipment,  
operations, or procedures that could affect the operation of the equipment. If this  
happens, the telephone company will provide advance notice so you can make  
the necessary modifications to maintain uninterrupted service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
How to Order Documentation  
xxiv  
If trouble is experienced with this equipment or for repair or warranty information,  
please contact the Technical Service Center at 1-800-248-1234. If the equipment  
causes harm to the telephone network, the telephone company may request that  
you disconnect the equipment until the problem is resolved.  
It is recommended that repairs be performed by Lucent Technologies-certified  
technicians.  
The equipment cannot be used on public coin phone service provided by the  
telephone company. Connection to party line service is subject to state tariffs.  
Contact the state public utility commission, public service commission, or  
corporation commission for information.  
This equipment, if it uses a telephone receiver, is hearing aid compatible.  
How to Order Documentation  
In addition to this book, other description, installation and test, maintenance, and  
administration books are available. A complete list of DEFINITY books can be  
found in the Business Communications System Publications Catalog,  
555-000-010.  
This document and any other DEFINITY documentation can be ordered directly  
from the Lucent Technologies Business Communications System Publications  
Fulfillment Center toll free at 1-800-457-1235 (voice) and 1-800-457-1764 (fax).  
International customers should use 317-322-6791 (voice) and 317-322-6849  
(fax).  
How to Comment on This Document  
Lucent Technologies welcomes your feedback. Please fill out the reader  
comment card found at the front of this manual and return it. Your comments are  
of great value and help improve our documentation.  
If the reader comment card is missing, FAX your comments to 1-303-538-1741 or  
to your Lucent Technologies representative, and mention this document’s name  
and number, DEFINITY Enterprise Communication Server Maintenance for csi,  
555-230-129.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
Where to Call for Technical Support  
xxv  
Where to Call for Technical Support  
Use the following telephone number for the region in which the system is  
installed.  
Telephone  
Organization  
Number  
Streamlined Implementation (for missing  
equipment)  
1-800-772-5409  
USA/Canada Technical Service Center  
1-800-248-1234  
1-800-248-1111  
Technical Service Center (INADS Database  
Administration)  
Asia/Pacific Regional Support Center  
Western Europe/South Africa/Middle East  
Business Communications Europe  
Eastern/Central Europe  
65-872-8686  
441-242-774-800  
441-242-391-789  
361-345-4334  
ITAC  
1-303-804-3777  
1-303-804-3778  
1-800-225-7585  
1-800-643-2353  
1-800-242-2121  
1-800-822-9009  
Latin/Central America & Caribbean  
DEFINITY Helpline  
Lucent Technologies Toll Fraud Intervention  
Lucent Technologies Technical Service Center  
Lucent Technologies Corporate Security  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
About This Book  
Where to Call for Technical Support  
xxvi  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
What’s new for R8csi  
1
1-1  
Maintenance for csi systems  
1
The maintenance subsystem is a part of the software that initializes and  
maintains the system. The software continuously monitors system health and  
keeps a record of errors detected in the system. The maintenance subsystem  
also provides a user interface for on-demand testing. This chapter provides a  
brief description of the maintenance strategy and background information on the  
system’s overall functions.  
What’s new for R8csi  
The following sections introduce new features in the Maintenance manuals:  
■
■
■
■
■
■
■
■
■
■
‘‘H323-BCH’’  
‘‘H323-SGRP’’  
‘‘H323-STN’’  
‘‘DIG-IP-STN’’  
‘‘MEDPRO’’  
‘‘MEDPROPT’’  
‘‘AN-LN-PT (and TR-LN-BD)’’  
‘‘Administrable Loss Plan’’  
‘‘Traceroute’’  
‘‘Incomplete Command Timeout’’  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
What’s new for R8csi  
1
1-2  
H323-BCH  
H.323 signaling is very similar to ISDN Q.931 signaling. In order to take  
advantage of existing Definity ISDN call processing software, H.323 trunk call  
processing includes H.323 signaling groups, H.323 D-channels and H.323  
B-channels. H.323 Signaling groups are similar in concept to ISDN PRI signaling  
groups. H.323 D-channels are an artificial fabrication created only to allow  
maximum re-use of system ISDN code. H.323 B-channels are also an artificial  
fabrication.  
H323-SGRP  
The H.323 Signaling Group (H323-SGRP) maintenance object supports a  
signaling channel for H.323 Trunk connections. The Media Processor (MedPro)  
TN802B circuit pack provides audio connectivity, working in concert with a  
C-LAN (TN799B) circuit pack that provides control signaling to support an H.323  
connection.  
The H.323 signaling group (323-SGRP) is a signaling channel that physically  
rides on a C-LAN ethernet port (socket) and the IP network. Unlike ISDN  
D-channels, the H.323 channel may actually come up and down on a call by call  
basis. The H.323 channel is actually a TCP/IP signaling channel. Layers 1 and 2  
of this signaling channel are monitored by IP PING testing.  
H323-STN  
This maintenance object covers implementation of the maintenance for native  
mode H.323 endpoints. Native mode H.323 applications such as NetMeeting or  
Proshare only provide what is needed to support the H.323 standard. There is  
very little that Definity can invoke in the maintenance area. Definity will report  
errors as they are detected via the RAS registration and keep-alive mechanism.  
Definity will PING the endpoint both via the signaling path (i.e. via C-LAN) and via  
the media path (i.e. via Medpro).  
This station type is not attached to a port board. Insertion of the station is not  
driven by board insertion, rather it is driven by successful registration of the  
endpoint. It is maintained via a set of explicit TCP/IP ping requests and errors  
reported by the switch software, which terminates the H.323 signaling portion of  
each endpoint. The MO follows standard maintenance methodology and  
supports test, busyout, release and status commands.  
DIG-IP-STN  
This maintenance object covers implementation of the maintenance for  
Lucent-provided IP Softphone or the Centre-Vu Remote IP Agent. The  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
What’s new for R8csi  
1
1-3  
Lucent-provided endpoint consists of a service provider, an application layer  
called the Telephony Manager, and a registration application. The service  
provider terminates DCP signaling carried over TCP. The Telephony Manager  
provides the GUI emulating the DCP set. The registration application handles  
H323.RAS and is used to register and authenticate the endpoint with DEFINITY.  
This group of modules is called Vphone. Note that the Vphone does not include  
any type of audio path of bearer channel. The Vphone provides a DCP control  
plane for an alternate bearer channel. Tha alternate bearer channel is provided  
by either a native H.323 station or a POTS line or trunk. The Vphone is used only  
in a dual-connect arrangement.  
The Vphone supports some level of existing DCP maintenance in the form of  
audits and updates.  
This station type is not attached to a port board. Insertion of the station is not  
driven by board insertion, rather it is driven by successful registration of the  
endpoint. It is maintained via a set of explicit TCP/IP ping requests and errors  
reported by the User Manger software, which terminates the H.323 signaling  
portion of each endpoint. The MO follows standard mtce methodology and  
supports test, busyout, release and status commands.  
MEDPRO  
The TN802B MedPro circuit board is used by the DOLAN (Definity on the LAN)  
feature to provide voice over IP connectivity. The TN802B can run either:  
■
R8.1 IP Trunk application — allows the TN802B to emulate a DS1 circuit  
pack. In this mode, the circuit pack is maintained as a standard DS1  
board with its associated Tie trunk ports. The TN802B operates as an  
integrated Internet Telephony Server. It communicates with other ITS  
boxes or IP trunk boards.  
■
the Media Processor (MedPro) application — allows the TN802B to act as  
a service circuit to terminate generic RTP streams used to carry  
packetized audio over an IP network. As part of the overall H.323  
implementation, the TN802B or later circuit pack handles the audio  
streams while the TN799 C-LAN handles the TCP/IP signaling channels.  
This maintenance plan applies only to a TN802B MedPro running the  
Media Processor application.  
The MedPro hardware combines an angel complex, a Windows NT PC and a  
TAP802 DSP card in a 3-slot package. When operating as an IP trunk circuit  
pack, the MedPro emulates a DS1 Tie Trunk circuit pack and blindly responds to  
DS1 trunk maintenance requests. Actual maintenance is accomplished via the  
windows NT interface and the ITS software diagnostics.  
The Media Processor application is built upon the existing ITS software, and as  
such is not administered in DEFINITY as a DS1 trunk, and does not emulate a  
DS1 for maintenance purposes.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
What’s new for R8csi  
1
1-4  
MEDPROPT  
The MEDPROPT maintenance object monitors the health of the MEDPRO digital  
signal processors (DSPs).  
The TN802B MAPD (Multi-Application Platform for DEFINITY) Media Processor  
circuit pack provides the audio bearer channels for H.323 voice over IP calls.  
One TN802B circuit pack has one MEDPROPT media processing resource.  
Based on system administration of audio codecs, a MEDPROPT can handle  
either 31 or 22 simultaneous channels of H.323 audio processing. If the  
ip-parameters form specifies only G.711 Mulaw or G.711 Alaw as the audio  
codecs, the MEDPROPT can service 31 channels. If any other codec type  
(G.723-5.3K, G.723-6.3K, or G.729) is administered, the MEDPROPT can only  
service 22 channels.  
The MEDPROPT is physically made up of 11 individual DSPs, but is treated  
logically as one port. If individual DSPs on the TN802B MAPD fail, the  
MEDPROPT remains in-service at lower capacity.  
The MEDPROPT is a shared service circuit. It is shared between H.323 trunk  
channels and H.323 stations. An idle channel is allocated to an H.323  
trunk/station on a call-by-call basis.  
AN-LN-PT (and TR-LN-BD)  
The TN793B/TN2793B Analog Line circuit pack (w/ Caller ID), and the TN797  
Analog Trunk and Line circuit pack both support this Maintenance Object.  
The TN793B/TN2793B Analog Line circuit pack (w/ Caller ID) provides 24 ports  
for voice terminals and supports both on-premises and off-premises analog  
voice terminals.  
The TN797 Analog Trunk and Line circuit pack provides 8 ports, each of which  
may be administered in any of several ways, as described in maintenance object  
TR-LN-BD.  
NOTE:  
The TN793B/TN2793B analog line circuit pack supports analog data  
modules. When assigned, analog data modules provide access to the  
NetPkt (TN794 circuit pack) data ports. To activate an analog data module  
you must assign the port location on the data form and connect a modem  
to the port. The analog data module can be used for connection to a CDR  
output, or other adjuncts as needed. These ports are tested the same as all  
other analog ports on the circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
What’s new for R8csi  
1
1-5  
Administrable Loss Plan  
The administrable Loss Plan feature provides the user with the capability to  
administer the loss or gain applied on calls. This plan provides for dynamic  
administration of loss levels per station, using 2- party loss tables, and an  
algorithm that calculates 3, 4, 5, and 6-party conference loss plans. Such a  
feature can be used to provide additional gain, for example, on connections  
involving station sets whose users have hearing impairments.  
Implementation of this plan involves the addition of a new field, Digital Loss  
Plan Modifications: on the system-parameters customer options form.  
Traceroute  
This command provides the ability to trace the route of packets originated from  
DEFINITY IP boards through the LAN. The output shows the ip address of each  
router or host (hop) that the packets encounter and the time elapsed between  
each hop. If a DEFINITY IP board has trouble communicating with a far-end  
device, the traceroute command can determine “how far” packets get toward  
the destination.  
DEFINITY IP boards include:  
■
TN799B (or later suffix) CLAN board  
TN802B Medpro board  
■
The output form lists:  
■
■
■
Hops traversed from source to destination  
IP addresses of the hop points and the final destination  
Observed round-trip delay from the source to each hop point  
If no reply is received from a potential hop point, the IP Addressfield contains  
stars (*), which indicates a timeout condition.  
The primary use of this command is to determine quickly and unambiguously if  
the fault lies within Lucent-provided equipment or if the fault is with the LAN or  
LAN administration to which the DEFINITY ECS switch is connected.  
Incomplete Command Timeout  
A time-out feature has been added to the MAINTENANCE-RELATED SYSTEM  
PARAMETERS form (accessed by the command change system parameters  
maintenance). This feature improves the operation of daily maintenance by  
allowing maintenance routines to run that might otherwise not run. It also helps to  
prevent the loss of translations that were not saved by the save translation  
command, and were also not saved because daily maintenance was prevented  
from running prior to the system reset. Highlights of the feature include:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
How to use the Maintenance book  
1-6  
■
■
■
Options for blank, 1, 2, 3, 4, 5, or 6 hours (the default is 2 hours)  
The blank option indicates that the feature is not active  
Only commands that block the running of daily maintenance (add,  
change, duplicate, remove, and set) are affected  
■
■
All logins will time-out if any of these commands are active for the  
prescribed time (except for the “blank” option)  
The feature applies to all logins, regardless of type (init, dadmin, craft,  
inads) or permissions granted to the specific login ID of an administration  
or maintenance user  
The corresponding “time-out” entry is appended to the list history log.  
How to use the Maintenance book  
This procedure begins with the system raising an alarm against a Maintenance  
Object (MO), a software module that monitors the components of a circuit pack.  
These components can include:  
■
■
■
■
Hardware  
System (processor) availability and conditions  
Presence of and physical connections (copper, fiber) to other components  
Presence of certain signals (synchronization, DS1) within specific  
parameters  
■
Environment (power, cabinet temperature sensors)  
Table 1-1. Alarm levels, reporting conditions and action to take  
Reported Reported  
Alarm  
level  
to  
to  
Description  
INADS?  
console?  
What action to take?  
MAJOR  
MINOR  
Critical service  
degradation  
Y
Y
Yes, after 4  
attempts to  
call INADS  
Immediate attention  
Some service  
Same as  
above  
Check to see what service  
is affected  
degradation but does not  
render the system  
inoperable.  
1
WARNING Failure that causes no  
significant service  
N
N
Monitor the situation. May  
be service or equipment  
interruption or failure  
outside the switch.  
degradation  
1. Some system-downgraded Warning alarms are reported to INADS.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
How to use the Maintenance book  
1-7  
Alarms are further classified as:  
■
On-board problems originate in the circuitry on the alarmed circuit pack.  
■
Off-board problems originate in a process or component that is external to  
the circuit pack.  
To clear system alarms using the appropriate maintenance book:  
1. Type display alarms and press Enter.  
2. A query screen displays next (Screen 1-1), asking you if you want to see  
all alarms or if you want to restrict the list to certain kinds of errors.  
ALARM REPORT  
The following options control which alarms will be displayed.  
ALARM TYPES  
Active? y  
Resolved? n  
Major? y  
Minor? y  
Warning? y  
REPORT PERIOD  
Interval: m  
From:  
/ / :  
To:  
/ / :  
EQUIPMENT TYPE ( Choose only one, if any, of the following )  
Cabinet:  
Port Network:  
Board Number:  
Port:  
Category:  
Screen 1-1. Alarm Report query screen  
a. The report can be restricted by typing either y (yes) or n (no) in  
these fields (shown above in bold):  
■
■
■
■
Active  
Major  
Minor  
Warning  
!
CAUTION:  
If you choose n for major alarms and y for minor and warning  
alarms, you will not see the macro-level information that you  
may need to determine what is wrong with the system.  
b. The Cabinet, Port Network Board Number, Port and Category fields  
are described in the ‘‘Field descriptions’’ section.  
3. After you have made your choices to tailor the report, press Enter.  
4. The alarm log displays.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
How to use the Maintenance book  
1-8  
ALARM REPORT  
Port  
Maintenance On  
Alt  
Alarm  
Type  
Svc  
State 1 2  
Ack? Date  
Alarmed  
Date  
Resolved  
Name  
Brd? Name  
01C1008  
DID-TRK  
y
MAJOR  
03/09/00:30 00/00/00:00  
Screen 1-2. Alarm Report screen  
A DID trunk port in slot 10, carrier C has a MAJOR alarm.  
5. Note the value in the Portfield (01C1008). This is the alarmed port  
address.  
6. Type display errors and press Enter.  
7. A query screen displays next, asking if you want to see all the errors or if  
you want to restrict the list to certain kinds of errors. Except for warning  
levels (Major, Minor, Warning), the screen is the same as Screen 1-1.  
Generally, unless you suspect a problem occurred within a certain time  
frame or with a particular component of the system, simply pressing Enter  
at the query screen displays the accumulated system errors (Screen 1-3).  
HARDWARE ERROR REPORT - ACTIVE ALARMS  
Port  
Mtce  
Name  
DID-TRK  
Alt  
Name  
Err  
Type Data  
1547  
Aux  
First  
Occur  
Last  
Occur  
Err Err Rt/ Al Ac  
Cnt Rt Hr St  
01C1008  
03/09/00:20 03/15/01:18 255 1  
7
a y  
Screen 1-3. Hardware Error Report - Active Alarms  
8. Note the Error Type (Err Typefield) value (1547) and the Aux Data  
value if present.  
9. Find the DID-TRK MO in the Maintenance Object chapter of the  
appropriate maintenance book.  
10. In the first table look up the initial command to run in the MAJOR row of the  
table (Step 4 indicated that a DID trunk in slot 10, carrier C has a MAJOR  
alarm).  
MO Name (in  
Alarm Log)  
1
Alarm Level  
MAJOR2  
Initial Command to Run  
test port UUCSSpp long  
test port UUCSSpp long  
test port UUCSSpp  
Full Name of MO  
DID Trunk  
DID-TRK  
DID-TRK  
DID-TRK  
MINOR  
DID Trunk  
DID Trunk  
WARNING  
1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs), C is the carrier designation (A, B,  
C, D, or E), SS is the number of the slot in which the circuit pack resides (01 to 21), and pp is the  
two digit port number (01, 02, ...).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
How to use the Maintenance book  
1-9  
2. A MAJORalarm on a truk indicates that alarms on these trunks are downgraded by the set options  
command and that at least 75% of the trunks in this trunk group are alarmed.  
11. Type test port 01C1008 long and press Enter.  
“01C1008” is the address of the alarmed port (see Screen 1-2 and Screen  
1-3)  
12. While the port test is running, look up the Error Type (1537 from Screen  
1-3) in the DID Trunk Error Log Entries table (example below).  
Table 1-2. DID Trunk Error Log entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1537  
Port Diagnostic  
(#35)  
MAJ/MIN/  
WRN  
OFF  
test port UUCSSpp sh r 1  
3840 (k) 40965  
None  
13. Since the Test to Clear Value (test port 01C1008 sh r 1) is very similar to the  
initial test you ran in Step 11, wait for the results of the port test.  
14. When the port test finishes, the following display appears (Screen 1-4):  
TEST RESULTS  
Port  
01C1008  
Maintenance Name Alt. Name Test No. Result  
DID-TRK 35 FAIL  
Error Code  
61472  
Screen 1-4. Test Results screen  
15. Find the Port Diagnostic Test (#35) [from the Test No.field) in the  
DID-TRK section of the Maintenance book. Note the Error Code  
(61472).  
16. Look in Table 1-3 for Test #35 and then find “61472” in the Error Code  
column and “FAIL” in the Test Result column read the  
Description/Recommendation column.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
How to use the Maintenance book  
1-10  
Table 1-3. TEST #35 Port Diagnostic Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
61472  
FAIL  
Battery feed test failed. A problem with the incoming CO line was  
detected.  
1. Check the incoming CO line for proper operation. If warranted, refer  
the problem to the CO.  
2. If the CO line checks out Ok, the failure must be on the DID port.  
Replace the circuit pack.  
17. Perform both steps in the Description/Recommendation column.  
18. Test the port (test port 01C1008 long and press Enter.) again after all of  
the recommendations are exhausted.  
19. If all tests pass, wait approximately 3-5 minutes for the Alarm and Error  
logs to clear.  
20. Type display alarms and press Enter twice.  
21. Check that the DID-TRK alarm does not appear in the log.  
Field descriptions  
Error type  
Error List  
Interval  
Enter error type, or blank  
active-alarms, errors, or cleared-errors  
h(our), d(ay), w(eek), m(onth), a(ll)  
Specify time interval by date and time  
Enter cabinet number (1 - 44)  
From:/To:  
Cabinet  
Port Network  
Board Number  
Enter port network number (1 - 44)  
Enter 5-character board number in UUCSS format:  
cabinet (1-44), carrier (A-E), slot (0-20)  
Port  
Enter 7-character port address in UUCSSss format:  
cabinet (1-44), carrier (A-E), slot (0-20), circuit  
(01-31)  
Category  
Enter category name (choose 1 from the list below:  
adm-conn  
detector  
generatr  
announce  
dup-spe  
bri/asai  
environ  
infc  
cdr  
data-mod  
ext-dev  
exp-intf  
maint  
inads-link  
mass-st  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
csi design  
1
1-11  
mbus  
memory  
mssnet  
pnc-peer  
stabd  
misc  
pkt  
mmi  
mnt-test  
pnc  
modem  
pncmaint  
spe  
pms/jrnl  
quick-st  
stations  
tone  
procr  
stacrk  
tdm  
vc  
s-syn  
sys-link  
trkbd  
sys-prnt  
trkcrk  
tape  
trunks  
vsp  
wideband  
wireless  
Extension  
Trunk  
Enter assigned extension, or blank  
Group  
Enter group number between 1-666  
Member  
Enter group member between 1-255, or blank  
csi design  
The csi 10-slot Compact Modular Cabinet (CMC) has a few design features that  
can affect the system technician’s approach to troubleshooting:  
■
The CMC cabinet has 2 shelves of 5 slots each (1-5, 6-10) as shown in  
Figure 1-1. This means that slots 5 and 6 are not contiguous like they are  
in other DEFINITY cabinet types and that Multi-Function boards such as  
the TN566 and the MAPD boards (TN800, TN801, and TN802) must be  
installed in specific slots. For example:  
— AUDIX, if present, requires 4 slots (slots 6-9 on the top row): the  
TN566 board in slot 8 with the two previous and 1 next slot reserved  
for AUDIX.  
— MAPD requires 2 slots if administered in slot 7, otherwise,  
installation requires 3 slots. See ‘‘change circuit-packs’’ in Chapter  
2, ‘‘Maintenance Commands’’ for more details.  
■
The TN798 Processor circuit pack incorporates the RISC processor  
complex, the TN777B NETCON (including PCM flash card interface), and  
TN765 Processor Interface functions and is always found in slot 1 of the A  
carrier. (See Figure 1-1)  
— The TN798 has 16 Mbytes of FLASH PROM for software text and 16  
Mbytes of DRAM for translations and other data. The TN798 is the  
only processor circuit pack compatible in the CMC.  
— The processor does not have either an amber WARNING LED nor a  
green ACK LED. If there is a warning, consult the alarm log with the  
display alarms command. More details on the processor LEDs can  
be found in the ‘‘TN798 Processor Circuit Pack LEDs’’ on page  
1-86.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
csi design  
1
1-12  
— Four administerable netcon channels are accessible through the  
TN798 processor and can be used for such asynchronous adjuncts  
as the G3 Management Terminals (SAT), Terranova family of  
Windows-based applications, BCMS terminals, BCMS VU, system  
printers, PMS links, and CDR devices.  
— The TN798 has separate RS232 ports for the external modem and  
CDR port.  
■
The AC Power Supply Unit (650A) provides:  
— Multiple DC outputs: ± 5.1 VDC, -48 VDC, +8-14 VDC (fan speed  
control), and -150 to -115 VDC (Neon bus).  
— Three switch-selectable AC ring outputs: 85 VAC @20 Hz (North  
America), 72 VAC @25 Hz (international), and two 28 VAC @50 Hz  
(France).  
— For LED indicators and interpretation, see ‘‘Power Supply LEDs’’ on  
page 1-90.  
■
There is no battery backup in this switch. If power is interrupted for more  
than 50 milliseconds, all calls are dropped and memory is lost. The only  
remedy for maintaining service without interruptions is to have a dedicated  
uninterruptable power supply (UPS) between the AC source and the  
switch.  
■
■
■
The system does not support either High or Critical Reliability duplication  
or expansion options.  
The maximum configuration is 3 cabinets (A-C) and a total of 28 slots (2  
slots are reserved for the processor and tone clock circuit packs).  
The csi uses an external modem for alarm reporting to INADS and remote  
access, rather than the built-in modem on the processor circuit pack. The  
U. S. Robotics Model 839 Sportster 33.6 Fax Modem is the external  
modem recommended for use with csi. This modem has a slightly different  
initialization string from other modems used with other DEFINITY products.  
Refer to the ‘‘change system-parameters maintenance’’ section in Chapter  
2, ‘‘Maintenance Commands’’ for administration and initialization details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
csi design  
1
1-13  
6
1
5
scdmlft2 KLC 070397  
Figure 1-1. Compact Modular Cabinet (CMC) slot configuration  
■
■
■
The RISC-based TN798 Processor circuit pack must be located slot 1.  
Figure 1-1 also shows the Flash Memory Card slot for translations.  
TN2182 Tone-Clock must be installed in slot 2. This is the only Tone-Clock  
circuit pack allowed in the CMC.  
Service circuit packs the only packs allowed in the CMC. These  
“universal” service packs can be located in any slot numbered 3-10.  
■
■
AUDIX, if present, requires 4 slots (slots 6-9 on the top row).  
MAPD requires 2 slots if administered in slot 7, otherwise, installation  
requires 3 slots.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Circuit Packs  
1
1-14  
Circuit Packs  
All circuit pack slots in the Compact Modular Cabinet (CMC) are “universal  
slots.” That is, any slot can contain any type of circuit pack (port, control, or  
service), hence the absence of the purple and white slot coding found on other  
DEFINITY products. The only requirements for slot allocation are:  
■
The TN798 Processor must be installed in slot 1  
The TN2182 Tone-Clock must be installed in slot 2  
■
NOTE:  
The TN2182 is the only Tone-Clock circuit pack allowed in the CMC.  
■
A TN744D Call Classifier/Tone Detector circuit pack may be required in  
systems with heavy traffic. This circuit pack can be installed into any port,  
although slot 1 of Cabinet B is preferred.  
Maintenance Objects  
The maintenance subsystem is partitioned into separate entities called  
Maintenance Objects (MOs). Each MO is referred to by an upper-case,  
mnemonic-like name that serves as an abbreviation for the MO. For example,  
“CO-TRK” stands for “Central Office TRunK.” Each MO is monitored by the  
system and has its own maintenance strategy. Although most MOs are individual  
circuit packs, some MOs are hardware components that reside on part of a  
circuit pack, for example, the TDM bus clock circuits reside on the Tone/Clock  
circuit pack. Other MOs, such as cabinet environmental sensors, represent  
larger subsystems or sets of monitors. Finally, some MOs, such as  
SYNChronization, represent processes or a combination of processes and  
hardware.  
“Maintenance names” are recorded in the Error and Alarm logs. Individual copies  
of an MO are assigned an address that defines the MO’s physical location in the  
system. These locations display as the Portfield in the Alarm and Error logs and  
as output of various commands such as test board, busy tdm-bus, and so forth.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Alarm and Error Reporting  
1
1-15  
Alarm and Error Reporting  
During normal operations, software or firmware may detect error conditions  
relevant to specific MOs. The system attempts to either fix or circumvent these  
problems automatically. However, if a hardware component incurs too many  
errors, an alarm is raised. Errors are detected in two ways:  
■
For “in-line” errors, firmware on the component detects the  
occurrence of an error during ongoing operations.  
■
For other types of errors, a “periodic test” or a “scheduled test”  
started by the software detects the error. The technician can run  
these tests on demand by using the maintenance commands  
described in Chapter 2, ‘‘Maintenance Commands’’, and the  
maintenance objects in Chapter 3, ‘‘Maintenance Objects’’.  
When an error is detected, the maintenance software puts the error in the Error  
Log and increments the error counter for that error. When an error counter is  
“active” (greater than zero), there is a maintenance record for the MO.  
Alarms are classified depending on their effect on system operation:  
— MAJOR alarms identify failures that cause a critical degradation of  
service. These alarms require immediate attention.  
— MINOR alarms identify failures that cause some service degradation but  
that do not render a crucial portion of the system inoperable. MINOR  
alarms require attention. However, typically a MINOR alarm affects only a  
few trunks or stations or a single feature.  
— WARNING alarms identify failures that cause no significant degradation of  
service or equipment failures external to the switch. These failures are not  
reported to INADS or to the attendant console.  
— ON-BOARD problems originate in the circuitry on the alarmed circuit  
pack.  
— OFF-BOARD problems originate in a process or component that is  
external to the circuit pack.  
Maintenance Testing  
Most troubles are reduced to the circuit pack level and can be identified by LEDs  
on the circuit packs and software reports generated by the system. The  
background maintenance tests in the system are divided into three groups:  
■
■
Periodic tests are usually performed hourly by maintenance software.  
These tests are nondestructive and can be run during high-traffic periods  
without interfering with calls.  
Scheduled tests are usually performed daily and are generally more  
thorough than periodic testing. These tests are considered destructive  
and are run only during off-hours to avoid service disruptions.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Maintenance Testing  
1
1-16  
■
Fixed interval tests are performed at regular time intervals that cannot be  
administered. These tests run concurrently with periodic maintenance.  
The following table lists the MOs that run fixed interval testing.  
Maintenance Object Interval (min)  
POWER  
60  
60  
10  
10  
SPE-SELEC  
TDM-BUS  
TONE-PT  
Demand tests are also run by the system when it detects a need or by  
maintenance personnel in trouble-clearing activities. Using the management  
terminal, maintenance personnel can “demand” the same tests that the system  
initiates in periodic or background testing. Demand tests include periodic tests  
plus other tests required only when trouble occurs. Some nonperiodic demand  
tests are destructive (service-disrupting) tests, and are identified in boldface  
type.  
Layers  
The Open System Interconnect (OSI) model for data communications contains  
seven layers, each with a specific function. Communications to and through the  
system concern themselves only with layers 1 and 2 of the model.  
Layer 1, or the physical layer, covers the physical interface between devices and  
the rules by which bits are passed. Among the physical layer protocols are  
RS-232, RS-449, X.21, DCP, DS1, and others.  
Layer 2, or the data-link layer, refers to code created and interpreted by the DCE.  
The originating equipment can send blocks of data with the necessary codes for  
synchronization, error control, or flow control. With these codes, the destination  
equipment checks the physical-link reliability, corrects any transmission errors,  
and maintains the link. When a transmission reaches the destination equipment,  
it strips any layer-2 information the originating equipment may have inserted. The  
destination equipment only passes to the destination DTE equipment the  
information sent by the originating DTE equipment. The originating DTE  
equipment can also add layer-2 code to be analyzed by the destination DTE  
equipment. The DCE equipment treats this layer as data and passes it along to  
the destination DTE equipment as it would any other binary bits.  
Layers 3 to 7 (and the DTE-created layer 2) are embedded in the transmission  
stream and are meaningful only at the destination DTE equipment. Therefore,  
they are shown in the figure as “user-defined,” with no state changes until the  
transmission stream reaches its destination.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Maintenance Testing  
1
1-17  
ORIGINATING  
DCE  
SYSTEM  
DESTINATION  
DCE  
D
I
D
I
G
I
T
A
L
P
O
R
T
P
O
R
T
G
I
T
A
L
DATA  
MODULE  
DATA  
MODULE  
DTE  
DTE  
D
I
G
I
T
A
L
D
I
G
I
T
A
L
P
O
R
T
P
O
R
T
DATA  
MODULE  
DATA  
MODULE  
DTE  
1
2
RS232C  
ASCII  
DCP  
RAW BITS  
DMI  
DCP  
RS232C  
ASCII  
3-7  
USER DEFINED  
A
N
A
L
O
G
P
MODEM  
O
R
T
MODEM  
POOLING  
CABLE  
PCM  
A
N
A
L
O
G
A
N
A
L
O
G
T
L
I
N
E
P
O
R
T
P
R
U
N
K
O
R
T
DTE  
MODEM  
MODEM  
DTE  
1
2
RS232C  
ASCII  
ANALOG  
PCM  
ANALOG  
RS232C  
VOICE GRADE DATA  
USER DEFINED  
ASCII  
3-7  
P
P
E
I
A
E
I
A
DTE  
ADU  
ADU  
DTE  
O
R
T
O
R
T
1
2
RS232C  
ADU PROT  
RAW BITS  
DMI  
ADU PROT  
RS232C  
ASYNCH ASCII  
ASYNCH ASCII  
3-7  
USER DEFINED  
D
I
G
I
T
A
L
P
P
DATA  
MODULE  
DS1  
PORT  
D
S
1
O
R
T
DTE  
1
O
R
T
RS232C  
ASCII  
DCP  
RAW BITS  
DS1 FORMAT  
2
DMI  
3-7  
USER DEFINED  
Figure 1-2. Data Transmission States  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Preventive Maintenance Procedures  
1-18  
Preventive Maintenance Procedures  
The following preventive maintenance procedures should be followed and  
logged when visiting customer sites:  
Preventive Maintenance Log  
The sample below shows the DEFINITY Preventive Maintenance Log. Whenever  
you complete any of the preventive maintenance procedures described in this  
section, be sure to fill in the requested information on the log form before leaving  
the customer’s premises.  
DEFINITY csi Preventive Maintenance Log  
Date System Installed: _________________________  
Component  
(Comcode)  
Scheduled  
Date  
Completed  
Date  
Completed  
By  
Scheduled  
Date  
Completed  
Date  
Completed  
By  
Air Filter1  
(407745009)  
1. Inspect annually; see ‘‘Air Filters’’ below for cleaning/replacement details.  
Air Filters  
Air filters should be inspected annually. If a filter is dirty or clogged, first tap it on  
the ground. If the filter is still dirty or clogged, then wash it with warm water and a  
mild detergent. A vacuum cleaner can be used if one is available. If there is no  
facility for washing or vacuuming the air filter, then replace the filter (Comcode  
407745009). Refer to ‘‘Fan and Filter Removal/Replacement’’ below for more  
information on air filters and fans.  
Fan and Filter Removal/Replacement  
1. Remove the left door.  
2. Remove the fan/filter access panel. See Figure 1-3.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Preventive Maintenance Procedures  
1-19  
Filter  
Fan  
scdmfltr RPY 072297  
Figure 1-3. Fan/Filter Removal  
Fan Assembly Removal/Replacement  
1. Pull (unplug) the fan assembly from the chassis. The power for the fan  
automatically disconnects when the assembly is unplugged.  
2. Plug in the new fan assembly. The power for the fan automatically  
connects when the fan assembly in plugged in.  
Replace the fan/filter access panel and the left door.  
Fan Filter Removal/Replacement  
1. Remove the fan access panel from the left side of the cabinet.  
2. Pull the fan filter from the chassis.  
3. Clean (vacuum or wash with water) or replace the filter as needed and  
slide the filter back into the chassis.  
4. Replace the fan access panel.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Initialization and Recovery  
1
1-20  
Initialization and Recovery  
When the system is initially powered up, or when an existing system experiences  
a catastrophic fault that interrupts its basic functions, the system either initializes  
or reboots.  
Initialization  
Upon initialization, no forms (not even Customer Options) are available until the  
Offer Category is set. (The remote INADS channel is available.) To set the  
customer options (INADS password only), do the following:  
1. Enter change system-parameters offer-options (init and inads logins  
only) and the following form displays:  
change system-parameters offer-options  
OFFER OPTIONS FORM  
Offer Category: _  
Activate Offer? _  
WARNING: Need to save translations and reboot to make the change permanent.  
Field descriptions  
Offer category  
Activate offer?  
Type either A or B.  
Type y if the entry for Offer categoryis correct and press Tab .  
Type n if there is an error in the Offer categoryfield and press  
Tab . Re-enter the correct Offer Category.  
2. After these two fields are filled and you press Enter, the system displays:  
WARNING: Activating Offer Category may set unchangeable  
limits.  
This is to let you know that the Offer Category along with the model  
determine the system capacities (limits) and allowable hardware.  
3. Select the Submit option to submit the form.  
4. Use the save translations command to make the changes permanent.  
!
CAUTION:  
To avoid potential loss of service, ensure that your system’s  
translations are protected by saving them to the PCM/CIA card.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Initialization and Recovery  
1
1-21  
Recovery  
There are several less severe resets available to the system that allow it to  
recover from disrupting errors. The user can initiate these resets by using the  
reset system n commands (where n is the reset level). These commands are  
used to manually restart the system at various levels, depending on the required  
test activity. The reset system commands are discussed below.  
A system is reset due to a loss of power, or through:  
■
Reset commands at the administration terminal.  
■
Maintenance software, from which the system can reset itself. (This  
process starts when certain software and hardware errors are detected by  
the software.)  
!
WARNING:  
When the system is rebooted or reset at level 2, 3, 4, or 5, all voice  
terminal and attendant console features are adversely affected.  
Users should be advised of services that are lost and that, as a  
result, must be reactivated. See ‘‘Removing Power’’ in this chapter.  
The administration terminal display and circuit pack LEDs indicate the progress  
of the recovery process. See ‘‘LED Interpretation’’ in this chapter for more  
information.  
The sections that follow discuss successful system resets. For each level of  
reset, a typical administration terminal display is provided. Note that any  
hexadecimal numbers shown in parentheses, such as (=8B89), are only  
examples and are subject to change.  
NOTE:  
If any of the diagnostic tests fail, the system may or may not function  
properly, and the LMM may or may not proceed with the restart. If the LMM  
does not proceed with the restart, the system goes into SPE-Down Mode. In  
failure cases, the appropriate part (for example, the Processor circuit pack)  
should be replaced.  
NOTE:  
Use and check the results of the set/get vector commands found in  
Chapter 2, ‘‘Maintenance Commands’’, to determine how much time should  
be added for the recovery levels. Also, if an update file is applied on a  
system reset, add from 30 seconds to one minute to the recovery time for  
that reset.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Initialization and Recovery  
1
1-22  
Reset System 1 (System Warm Start)  
This recovery takes about 30 seconds. All stable phone calls remain up.  
In-progress calls are dropped. No new calls can be made during this time.  
In this restart, all software (Oryx/Pecos, drivers, maintenance, and so forth.) is  
reset and the following displays:  
RESET 1 (WARM) PERFORMED  
Reset System 2 (System Cold Start  
Without Translations Loading)  
In this restart, all software (Oryx/Pecos, drivers, maintenance, and so forth) is  
reset. In addition, the TDM Bus and all port circuit packs are reset. All Port circuit  
packs are reset. All telephone sessions are dropped. Telephones begin to  
reconnect to the switch within 30 seconds. In a large system, reconnection of all  
telephones may take up to five minutes. Typical displays are:  
INTERNAL REGISTER TEST  
LOCAL BUS TEST  
ROM CHECKSUM TEST  
CONTROL STATUS TEST  
DCACHE TEST  
ICACHE TEST  
WRITE BUFFER TEST  
BTO TEST  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
TIMER TEST  
RESET 2 (COLD_2)PERFORMED  
Reset System 3 (System Cold Start  
With Translations Loading)  
In this restart, all software (Oryx/Pecos, drivers, maintenance, and so forth) is  
reset. After the software is reset, all translations load from translation card. In  
addition, the TDM Bus and all port circuit packs are reset. Emergency Transfer is  
invoked. Translations reload from translation card. Depending on the translations,  
the reloading process could take from five to 30 seconds. Thereafter, all port  
circuit packs are reset, and all telephone sessions drop. Telephones begin to  
reconnect to the switch within 30 seconds. In a large system, reconnection of all  
telephones may take up to five minutes. Typical displays are as follows:  
INVOKING EMERGENCY TRANSFER  
INTERNAL REGISTER TEST  
LOCAL BUS TEST  
ROM CHECKSUM TEST  
CONTROL STATUS TEST  
DCACHE TEST  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
ICACHE DToEwSnTload from Www.Somanuals.com. All Manuals Search And Download.  
PASSED  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Initialization and Recovery  
1
1-23  
WRITE BUFFER TEST  
BTO TEST  
TIMER TEST  
PASSED  
PASSED  
PASSED  
RESET 3 (COLD_1)PERFORMED  
Reset System 4 (System Reboot)  
In this reset Emergency Transfer is invoked. The boot image is already in the  
flash ROM memory. The system reboots immediately after the LMM performs a  
series of diagnostics on the processor and memory. Translations reload from the  
translation card. Depending on the translation, the reloading process takes from  
five to 30 seconds. Thereafter, all port circuit packs are reset, and all telephone  
sessions drop. Telephones begin to reconnect to the switch within 30 seconds. In  
a large system, reconnection of all telephones may take up to five minutes.  
Typical displays are:  
INVOKING EMERGENCY TRANSFER  
INTERNAL REGISTER TEST  
LOCAL BUS TEST  
ROM CHECKSUM TEST  
CONTROL STATUS TEST  
DCACHE TEST  
ICACHE TEST  
WRITE BUFFER TEST  
BTO TEST  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
MEM CONFIG TEST  
MEMORY FUNCTIONAL TEST  
MEMORY MODULE A STUCK BIT TEST PASSED  
MEMORY MODULE A PARITY TEST  
MEMORY MODULE A BURST TEST  
VIRTUAL MEMORY TEST  
EXCEPTION TEST  
PASSED  
PASSED  
PASSED  
PASSED  
TIMER TEST  
PASSED  
MTP TEST  
PASSED  
SANITY TIMER TEST  
ADDRESS MATCHER TEST  
FLASH TEXT CHECKSUM TEST  
DECOMPRESSING IDATA  
2080768  
PASSED  
PASSED  
PASSED  
in_cnt = 550368, out_cnt =  
RAM DATA CHECKSUM TEST  
MILLISEC TIMER TEST  
IOP SHARED RAM TEST  
RESET 4 (REBOOT)PERFORMED  
PASSED  
PASSED  
PASSED  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Set Neon Voltage (Ring Ping)  
1
1-24  
Reset System 5 (System Reboot and  
Run All 24-Hour Tests)  
In this reset Emergency Transfer is invoked. The LMM performs a series of  
diagnostics on the processor, on memory, and on memory card. Some  
diagnostics perform twice. This takes less than three minutes. The boot image is  
already in the flash ROM memory. The system reboots immediately after the LMM  
performs a series of diagnostics on the processor and memory. Translations  
reload from the translation card. Depending on the translation, the reloading  
process takes from five to 30 seconds. Thereafter, all port circuit packs are reset,  
and all telephone sessions drop. Telephones begin to reconnect to the switch  
within 30 seconds. In a large system, reconnection of all telephones may take up  
to five minutes. Finally, scheduled maintenance is initiated. Typical displays are:  
INVOKING EMERGENCY TRANSFER  
INTERNAL REGISTER TEST  
LOCAL BUS TEST  
ROM CHECKSUM TEST  
CONTROL STATUS TEST  
DCACHE TEST  
ICACHE TEST  
WRITE BUFFER TEST  
BTO TEST  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
MEM CONFIG TEST  
MEMORY FUNCTIONAL TEST  
MEMORY MODULE A STUCK BIT TEST PASSED  
MEMORY MODULE A PARITY TEST  
MEMORY MODULE A BURST TEST  
MEMORY MODULE A COUPLE TEST  
VIRTUAL MEMORY TEST  
EXCEPTION TEST  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
TIMER TEST  
PASSED  
MTP TEST  
PASSED  
SANITY TIMER TEST  
PASSED  
ADDRESS MATCHER TEST  
FLASH TEXT CHECKSUM TEST  
DECOMPRESSING IDATA  
2080768  
PASSED  
PASSED  
in_cnt = 550368, out_cnt =  
RAM DATA CHECKSUM TEST  
MILLISEC TIMER TEST  
IOP SHARED RAM TEST  
RESET 5 (EXT REBOOT)PERFORMED  
PASSED  
PASSED  
PASSED  
Set Neon Voltage (Ring Ping)  
NOTE:  
If the ringing option is set to 50 Hz, neon voltage is not available. If 25 Hz is  
selected, the maximum voltage is 120 volts.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Set Neon Voltage (Ring Ping)  
1
1-25  
If LED message lamps are used, or there are no neon message waiting lamps, or  
if the 50-Hz ring option is selected, use this step.  
didmt1 KLC 053097  
Figure 1-4. Setting the Neon Voltage  
1. Call a telephone with a neon message indicator and leave a message.  
2. Check for “ring ping” (single ring pulse) each time the lamp flashes  
(approximately every 3 seconds).  
3. Adjust the neon voltage control clockwise in small increments until the ring  
ping stops. See Figure 1-4. Be sure that the message lamp still lights  
when the adjustment is finished.  
4. Enter logoff and press Enter to logoff the system and to prevent  
unauthorized changes to data.  
5. Set the left and right doors onto the hinge pins and close the doors. The  
doors must be closed to prevent EMI emissions. Tighten the door screws.  
6. Set the cover panel onto the right panel and secure.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-26  
Logging On/Off  
System Login Procedure  
1. Verify the screen displays: Login:  
2. Type craft and press Enter.  
3. Verify the screen displays: password:  
4. Type crftpw and press Enter. For security reasons, the password is not  
displayed as it is typed. The screen displays the software version.  
5. Verify the screen display is similar to:  
Terminal Type (513, 715, 4410, 4425, VT220): [513]  
6. Enter the type of management terminal and press Enter.  
NOTE:  
If you are logging in remotely to the csi, you may need to disable your local  
modem’s error correction feature before attempting to establish connection  
with the switch’s external modem. For most modems, the AT\N0 [“zero”]  
command should disable error correction.  
Forced Password Aging and Administrable  
Logins  
This feature provides enhanced login/password security by adding a security  
feature that allows users to define their own logins/passwords and to specify a  
set of commands for each login. The system allows up to 11 customer logins.  
Each login name can be customized and must be made up of from 3 to 6  
alphabetic/numeric characters, or a combination of both. A password must be  
from 4 to 11 characters in length and contain at least 1 alphabetic and 1 numeric  
symbol. Password aging is an optional feature that the super-user administering  
the logins can activate.  
NOTE:  
If several users are logging in and out at the same time, a user may see the  
message: Transient command conflict detected; please try  
later. After the “users” have completed logging in or out, the terminal is  
available for use.  
The password for each login can be aged starting with the date the password  
was created, or changed, and continuing for a specified number of days (1 to  
99). The user is notified at the login prompt, 7 days before the password  
expiration date, that the password is about to expire. When the password expires  
the user is required to enter a new password into the system before logging in. If  
a login is added or removed, the “Security Measurement” reports are not  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-27  
updated until the next hourly poll, or a clear measurements security-violations  
command is entered. Once a non-super-user has changed the password, the  
user must wait 24 hours to change the password again.  
Security is enhanced by providing a logoff notification screen to a system  
administrator at log off while either the facility test call or remote access features  
are still administered. The administrator can be required to acknowledge the  
notification before completing the logoff process. Logoff notification is  
administered on the Login Administration screen.  
Software releases are delivered to the customer with one customer “super-user”  
login/password defined. The customer is required to administer additional  
login/passwords as needed. The super-user login has full customer permissions  
and can customize any login created.  
Login permissions for a specified login can be set by the super-user to block any  
object that may compromise switch security. Up to 40 administration or  
maintenance objects commands can be blocked for a specified login in.  
System-wide commands are grouped into three command categories. Each of  
the three command categories has a group of command subcategories listed  
under them, and each command subcategory has a list of command objects that  
the commands acts on. A super-user can set a users permissions to restrict or  
block access to any command in these categories. These categories are  
displayed on the Command Permissions Categories form.The three main  
categories are:  
■
Common Commands  
— Display Administrative and Maintenance Data  
— System Measurements  
Administration Commands  
— Administer Stations  
■
— Administer Trunks  
— Additional Restrictions  
— Administer Features  
— Administer Permissions  
Maintenance Commands  
— Maintain Stations  
■
— Maintain Trunks  
— Maintain Systems  
— Maintain Switch Circuit Packs  
— Maintain Process Circuit Packs  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-28  
If your password has expired, you see the message:  
Login: telmgr  
Password:  
Your Password has expired, enter a new one.  
Reenter Current Password:  
New Password:  
Reenter New Password:  
Figure 1-5. Password Expiration Screen  
If your password is within 7 days of the expiration date, you see:  
WARNING: Your password will expire in X days  
To Logoff  
To logoff, enter logoff at the command prompt. You will receive a logoff screen if  
any of the following is true from the list below. If either a or b is true and an  
acknowledgment is required, or if any of c, d, or e is true, you need to respond to  
the Proceed with Logoff?prompt on the logoff screen (default is n; enter y  
to override) as shown in Figure 1-6.  
1. If Facility Test Call Notification has been enabled for your login (see  
‘‘Adding Customer Logins and Assigning Initial Password’’).  
2. If Remote Access Notification has been enabled for your login (see  
‘‘Adding Customer Logins and Assigning Initial Password’’).  
3. If Alarm Origination is disabled.  
4. If any active major or minor alarm is active.  
5. If any resource is busied out.  
!
CAUTION:  
To leave the Facility Test Call administered after you logoff poses a  
significant security risk that unauthorized individuals may connect to the  
telecommunications network through the use of test call features.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-29  
To remove the Facility Test Calls Access Code, do the following:  
1. Enter change feature-access-codes to display the Feature Access Code  
screen.  
2. Leave the Facility Test Calls Access Codefield blank.  
!
!
CAUTION:  
No alarms report through the INADS interface if Alarm Origination is  
disabled.  
CAUTION:  
A busied out resource is one that is out of service. Be sure to verify if a  
busied resource needs to be released or if the resource should remain  
busied out.  
Facility Test Call Administered  
Remote Access Administered  
Alarm Origination is currently disabled.  
Active major or minor alarm detected; be sure to resolve it.  
*** Busied out resource detected; verify if release is needed! ****  
Proceed With Logoff: [n]  
Figure 1-6. Logoff Screen  
To Display a Login  
1. Enter the command display login [login name] and press Enter.  
The system displays the requested login’s:  
■
■
■
■
■
■
■
■
Name  
Login type  
Service level  
Disable following a security violation value  
Access to INADS Port value  
Password aging cycle length  
Facility test call notification and acknowledgment  
Remote access notification and acknowledgment  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-30  
To List Logins  
1. Enter the command list logins.  
The system displays the following information for all current logins:  
■
■
■
■
Name  
Service level  
Status (active, inactive, disabled, svn-disabled, void)  
Password aging cycle length  
The system displays only those logins with the same, or lower, service  
level as the requestor.  
To Remove a Login  
1. Enter the command remove login [login name].  
The system displays the Login Administration form.  
2. Press the Enter key to remove the login, or press Cancel to exit the remove  
login procedure without making a change.  
To Test a Login  
1. Enter your login name at the login prompt.  
2. After the user enters the correct login name and password and the login is  
administered correctly, the system displays the command line interface.  
Administering Customer Logins and Forced  
Password Aging  
Adding Customer Logins and Assigning Initial  
Password  
To add a customer login you must have administrative permissions:  
1. Enter the add login [name] command to access the Login Administration  
form.  
2. Enter your super-user password in the Password of Login Making  
Changefield on the Login Administration form.  
The 3- to 6-character login name (characters 0-9, a-z, A-Z) entered with  
the add login [name] command is displayed in the Login’s Name field.  
3. Enter customer in the Login Typefield. The system default for the  
Login Typefield is “customer.” The maximum number of customer  
logins of all types is 11.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-31  
4. Enter super-user or non-super-user in the Service Levelfield. Default is  
non-super-user.  
■
“super-user” gives access to the add, change, display, list, and  
remove commands for all customer logins and passwords. The  
super-user can administer any mix of super-user/non-super-user  
logins up to a total of ten additional system logins.  
■
“non-super-user” permissions are limited by restrictions specified  
by the super-user when administering the non-super-user login. A  
non-super-user can change his/her password with permission set  
by the super-user, however once a password has been changed  
the non-super-user must wait 24 hours before changing the  
password again. A non-super-user cannot change other user  
passwords, login characteristics, or permissions.  
5. Enter y in the Disable Following a Security Violationfield to  
disable a login following a login security threshold violation. This field is a  
dynamic field and only appears on the Login Administration form when the  
SVN Login Violation Notification feature is enabled. The system default for  
the Disable Following a Security Violationfield is y.  
6. Enter y in the Access to INADS Port?field to allow access to the  
remote administration port. This field only displays if Acct. has first  
enabled customer super-user access to the INADS Remote Administration  
Port. Default is n.  
7. Enter a password for the new login in the Login’s Passwordfield. A  
password must be from 4 to 11 characters in length and contain at least 1  
alphabetic and 1 numeric symbol. Valid characters include numbers,  
and!&*?;’^ (),.:- (the system does not echo the password to the screen as  
you type).  
8. Re-enter the password in the Login’s Passwordfield. The system does  
not echo the password to the screen as you type.  
9. Enter the number of days (1 to 99) from the current day, that you want the  
password to expire, in the Password Aging Cycle Lengthfield. If a  
you enter a blank in this field, password aging does not apply to the login.  
10. Decide whether or not to leave the default of yes in the Facility Test  
Call Notification?field. If y is selected, the user receives  
notification at logoff that the facility test call feature access code is  
administered. If you do not want the notification to appear, set the field to  
n.  
!
CAUTION:  
Leaving The facility Test Call administered after logging off poses a  
significant security risk.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-32  
To remove the Facility Test Calls Access Code, do the following:  
a. Enter change feature-access-codes to display the Feature Access  
Code screen.  
b. Leave the Facility Test Calls Access Codefield blank.  
11. Decide whether or not to leave the default of yes in the Facility Test  
Call Notification Acknowledgment Requiredfield. If y is  
selected, the user is required to acknowledge that they wish to logoff while  
Facility Test Call is still administered. If you do not want to force the user to  
acknowledge, set the field to n. This field appears only if the Facility  
Test Call Notificationfield is set to y.  
12. Decide whether or not to leave the default of yes in the Remote Access  
Notification?field. If y is selected, the user receives notification at  
logoff that remote access is still administered. If you do not want the  
notification to appear, set the field to n.  
!
CAUTION:  
To Leave Remote Access feature administered after logging off  
poses a significant security risk if you are using the feature in  
conjunction with the Facility Test Call feature.  
13. Decide whether or not to leave the default of yes in the Remote Access  
Acknowledgment Required?field. If y is selected, the user is required  
to acknowledge that they wish to logoff while remote access is still  
administered. If you do not want to force the user to acknowledge, set the  
field to n. This field appears only if the Facility Test Call  
Notificationfield is set to y.  
LOGIN ADMINISTRATION  
Password of Login Making Change:  
LOGIN BEING ADMINISTERED  
Login’s Name:xxxxxxx  
Login Type:  
Service Level:  
Disable Following a Security Violation?  
Access to INADS Port?  
LOGIN’S PASSWORD INFORMATION  
Login’s Password:  
Reenter Login’s Password:  
Password Aging Cycle Length:  
LOGOFF NOTIFICATION  
Facility Test Call Notification? y  
Remote Access Notification? y  
Acknowledgment Required? y  
Acknowledgment Required? y  
Screen 1-5. Login Administration  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-33  
Changing a Login’s Attributes  
To change a customer login’s attributes you must be a super-user, have  
administrative permissions (specifically, the Administration Permission  
field must be set to y for the super-user), and:  
1. Enter the change login name command to access the Login  
Administration form.Enter your super-user password in the Password of  
Login Making Changefield on the Login Administration form. The 3- to  
6-character login name (characters 0-9, a-z, A-Z) entered with the change  
login name command is displayed in the Login’s Namefield.  
2. Enter customer in the Login Typefield.  
3. Enter super-user or non-super-user in the Service Level field.  
NOTE:  
You cannot change your own service level.  
4. To disable a login following a login security threshold violation, enter y in  
the Disable Following a Security Violationfield. This field is a  
dynamic field and only appears on the Login Administration form when the  
SVN Login Violation Notification feature is enabled.  
5. To allow access to the remote administration port, enter y in the Access  
to INADS Port?field. This field will only display if Lucent Technologies  
has first enabled customer super-user access to the INADS Remote  
Administration Port.  
6. Enter a password for the new login in the Login’s Passwordfield. A  
password must be from 4 to 11 characters in length and contain at least 1  
alphabetic and 1 numeric symbol. Valid characters include numbers,  
and!&*?;’^ (),.:- (the system does not echo the password to the screen as  
you type).  
7. Re-enter the password in the Login’s Passwordfield. The system does  
not echo the password to the screen as you type.  
8. Enter the number of days (1 to 99) from the current day when you wish the  
password to expire in the Password Aging Cycle Lengthfield. If a  
blank is entered in this field, password aging does not apply to the login.  
Administering Login Command Permissions  
Users with super-user permissions can set the permissions of the logins they  
create. The Command Permissions Categories form displays fields to which a  
user with super-user permissions can give or limit access. These commands are  
divided into three categories:  
■
■
■
Common Command  
Administration Commands  
Optional Maintenance Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-34  
Each of the three main categories have subcategories listed under them that  
when set to y give permission to use the command sets associated with that  
category. When the Command Permissions Categories form is displayed for a  
login, the subcategories fields appear with the fields set to give the login full  
permissions for that login type. The super-user administering login permissions  
can set any of these field to deny access to a command category for the  
specified login. If the super-user making the assignments has full super-user  
permissions and would like to limit permissions for a category, the super-user  
can do so by entering y in the Additional Restrictionsfield located under  
the Administration Category section of the Command Permissions Categories  
form.  
Refer to the Command Permissions Form Entries Tables at the end of this section  
for a list of command Objects and Actions by:  
■
■
■
■
■
Display Administration and Maintenance  
Administer Features  
Administer Permissions  
Administer Stations  
Administer Trunks  
The information in these tables can help you to establish command permissions  
for user logins.  
To administer command permissions, log in as super-user and:  
1. Access the Command Permissions Categories form by entering change  
permissions login login name. When the form is displayed for a login,  
the default permissions for that “login type” are shown. The super-user  
administering the login can change a yto n for each subcategory field.  
2. Select a category for the login and enter y in each field where permission  
to perform an administrative or maintenance action is needed. The  
command object you select must be within the permissions for the login  
type you are administering.  
If the Maintenanceoption is set to y on the Customer Options form, the  
super-user can enter y in the Maintain Switch Circuit Packs?or  
Maintain Process Circuit Packsfields.  
3. A super-user with full super-user permissions (super-user administering  
the login cannot have the Additional Restrictionsfield set to y for  
his/her own login) can restrict additional administrative or maintenance  
actions for a specified login by entering y in the Additional  
Restrictionsfield on the Command Permission Categories form. Enter  
the additional restrictions for a login in the Restrictedobject list fields  
on the Command Permission Categories Restricted Object List form. You  
can enter up to 40 command names (object names) to block actions  
associated with a command category for a specified login.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-35  
Page 1 of 3  
COMMAND PERMISSION CATEGORIES  
Login Name:  
COMMON COMMANDS  
Display Admin. and Maint. Data? y  
System Measurements? _  
ADMINISTRATION COMMANDS  
Administer Stations? y  
Administer Trunks? y  
Administer Features? y  
Administer Permissions? y  
Additional Restrictions? n  
MAINTENANCE COMMANDS  
Maintain Stations? n  
Maintain Trunks? n  
Maintain Systems? n  
Maintain Switch Circuit Packs? n  
Maintain Process Circuit Packs? n  
Figure 1-7. Command Permission Categories (Page 1 of 3)  
Page 2 of 3  
COMMAND PERMISSION CATEGORIES  
RESTRICTED OBJECT LIST  
_______________________  
_______________________  
_______________________  
_______________________  
_______________________  
_______________________  
_______________________  
_______________________  
_______________________  
_______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
Figure 1-8. Command Permissions Categories (Page 2 of 3)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-36  
Page 3 of 3  
COMMAND PERMISSION CATEGORIES  
RESTRICTED OBJECT LIST  
_______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
______________________  
_______________________  
_______________________  
_______________________  
_______________________  
_______________________  
_______________________  
_______________________  
_______________________  
_______________________  
Figure 1-9. Command Permissions Categories (Page 3 of 3)  
Testing a Login  
1. Enter your login name at the login prompt.  
After the user enters the correct login name and password and the login is  
administered correctly, the system displays the command line interface.  
2. Turn on the administration terminal. Verify that the screen displays:  
login:  
3. Enter your login name, then press Enter. Verify that the screen displays:  
password:  
4. Enter your password, then press Enter.  
For security reasons, the password is not displayed as you type it. The  
system verifies that a valid login and password name were entered. If an  
invalid login or password name was entered, the screen displays:  
login incorrect:, and you must repeat the procedure.  
If the system recognizes the login and password name, verify that the  
screen displays the software version.  
5. For your terminal type, complete one of the following:  
a. If the terminal is a 513 BCT, press Enter. The 513 in brackets [513] is  
the system default terminal.  
b. If the terminal is a 610 BCT or a 615 MT that has a 513 emulation  
cartridge, press Enter.  
c. If the terminal is a 610 BCT or a 615 MT that does not have a 513  
emulation cartridge, enter 4410 and press Enter.  
d. If the terminal is any other of the types listed, enter the terminal type  
and press Enter.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Logging On/Off  
1
1-37  
6. You can deactivate INADS alarm origination whenever you log in as craft.  
After you supply the terminal type information requested, the system  
displays the following if alarm origination is activated on the Maintenance  
System-Parameters screen:  
NOTE:  
Unless you are in a special situation, please reduce unnecessary  
trouble tickets by always answering y to the Suppress Alarm  
Origination: [y]prompt.  
The default answer is yes. If you do NOT wish to suppress alarm  
origination, enter n. Any other entry defaults to yes. The test inads-link  
command works regardless of whether you have overridden INADS alarm  
origination.  
7. Verify that the screen displays: enter command:  
You may enter the desired command, such as display station xxxx or  
press Help to obtain the list of permissible commands.  
System Logoff Procedure  
The system logoff procedure should be done any time the terminal is not being  
used. This assures that system translations are not accidentally corrupted. The  
monitor system command, when canceled, automatically causes a terminal  
user to be logged off and, thus, prevents unauthorized use of the terminal. Use  
the following procedure to log off the system:  
1. Verify that the screen displays: enter command:  
2. Enter logoff and press Enter. The screen displays: login:  
If after either logging on as system technician or issuing a system technician  
command no additional command is issued for 30 minutes, an automatic  
time-out and logoff occurs. At that time, any alarms in the system previously  
unreported to INADS are reported. If you are logged in at two separate  
administration terminals, the system waits until the second terminal times out or  
until you log off before reporting such alarms to INADS.  
Logoff Notification alerts system administrators if features that present a  
significant security risk are enabled. A message displays on the system  
administration/maintenance interface. Additionally, the user can be required to  
acknowledge the notification before the logoff is completed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Procedure for SPE-Down Mode  
1
1-38  
Procedure for SPE-Down Mode  
Due to fatal hardware and software problems, it is possible for a system to go into  
SPE-Down Mode. In this mode, the system invokes emergency transfer and does  
not provide any other service. Moreover, while in this mode, the software cannot  
run at all. However, there are two limited interfaces to the system:  
■
The Processor circuit pack is responsible for maintenance and serves as  
interface to the system.  
■
The administration terminal, which connects directly to the processor,  
provides a very limited interface to the system. Technicians can display  
alarms or restart the system. Only a subset of control complex alarms  
displays.  
The following are sample displays for SPE-Down mode and the alarms  
displayed.  
**************SPE DOWN MODE*************  
You can display alarms and reset system(4).  
SPE_DOWN->  
Figure 1-10 shows all possible SPE-Down alarms.  
DISPLAY ALARMS:  
Physical  
Logical  
Name  
On  
Board?  
Alternate  
Name  
Alarm  
Type  
Date  
Alarmed  
Date  
Resolved  
Name  
------  
------  
------  
------  
PROC_BD  
MEM_BD_0 y  
M_BUS  
MAINT*  
y
-----  
-----  
-----  
-----  
MAJOR  
MAJOR  
MAJOR  
MAJOR  
------  
------  
------  
------  
------  
------  
------  
------  
y
y
Figure 1-10. Display Alarms command  
* The “MAINT” designation is used for PR-MAINT.  
The first step is to determine the location of the problem. It is possible for two or  
more circuit packs to have failed. It is also possible for a fatal problem with one  
circuit pack to affect another circuit pack, especially the Processor circuit pack.  
All three of the following methods should be employed to determine where the  
fatal fault lies.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Reseating/Replacing Circuit Packs  
1-39  
1. Use display alarms command:  
Issuing the display alarms command at the administration terminal shows  
where maintenance thinks the problem lies. The alarms are a good  
indication of why the system went down. They should be used along with  
the following two methods.  
2. Observe red LEDs on the circuit pack to determine where software or  
processor firmware (LMM) had a problem.  
3. Use the reset command:  
Observe all the diagnostics on the screen, and note if the LMM has a  
problem with any of the diagnostics, as this information should give a  
good indication of where the problem lies.  
The procedure to get a system out of SPE-Down mode follows.  
NOTE:  
This is important! If you cannot complete the first step or have problems  
with the maintenance interface, then the first step should be to replace the  
Processor circuit pack.  
1. Determine which circuit pack is defective by displaying alarms and  
observing the red LEDs (as discussed previously).  
The following general purpose maintenance procedures may be used with other  
repair strategies to clear system-alarmed and user-reported troubles.  
Reseating/Replacing Circuit Packs  
!
WARNING:  
It is NOT recommended that you reseat circuit packs unless the  
documentation specifically instructs you to do so. If it is required to reseat a  
circuit pack, follow the instructions below which explain how to unseat,  
reseat, and replace circuit packs.  
The procedures for unseating, reseating, and replacing control circuit packs vary  
depending on the system configuration. Therefore, before performing these  
maintenance activities, refer to the appropriate procedure below.  
Control Circuit Packs  
To unseat a control circuit pack:  
1. Remove power from the PPN using the procedure provided in ‘‘Removing  
Power’’.  
2. Slide the latch pin upward to unlock the locking lever.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Removing Power  
1
1-40  
3. Pull down on the locking lever until the circuit pack disconnects from its  
socket.  
4. Pull the circuit pack just enough to break contact with the backplane  
connector, but do not remove it from the cabinet.  
To reseat a circuit pack:  
1. Push the unseated circuit pack back into the backplane connector.  
2. Lift the locking lever until the pin engages.  
3. Restore power to the PPN using the procedure provided in ‘‘Restoring  
Power’’  
To replace Control circuit packs:  
1. Remove power from the PPN using the procedure in the ‘‘Removing  
Power’’  
1. Unseat the circuit pack.  
2. Slide the circuit pack out of the slot.  
3. Replace the circuit pack as per the following procedure:  
NOTE:  
If a new circuit pack does not correct the problem, install the original  
circuit pack.  
To install a new circuit pack or return the original one to service:  
1. Carefully insert the circuit pack and push it all the way into its mounting  
slot.  
2. Lift the locking lever until the latch pin engages.  
3. Restore power to the PPN using the procedure in ‘‘Restoring Power’’.  
4. Verify that the circuit pack LED indications are correct.  
5. Test the replaced control circuit pack by issuing the system technician  
commands after power has been restored.  
Removing Power  
When power is removed, the following features deactivate:  
■
■
■
■
Attendant Trunk Group Control  
Automatic Callback  
Call Park  
Make Busy for Direct Department Calling (DDC) and Uniform Call  
Distribution (UCD)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Removing Power  
1
1-41  
The procedures for removing power vary depending on the system configuration.  
Before performing these activities, refer to the following appropriate procedure.  
!
WARNING:  
Before powering down a carrier that contains DEFINITY AUDIX circuit  
packs (TN566), first power down the AUDIX unit to avoid damaging the  
AUDIX disk. Instructions for powering down this unit are in the ‘‘Power  
Down AUDIX System’’ section below, on the circuit pack, and in DEFINITY  
AUDIX documentation.  
Power Down AUDIX System  
A yellow caution sticker on the system’s power unit notifies technicians to shut  
down the DEFINITY AUDIX System prior to powering down the system.  
1. Long into the AUDIX System as craft.  
2. Enter the reset system shutdown command. Press Enter.  
3. Press Enter again to start the shutdown process.  
4. The “SHUTDOWN Completed” message appears when the AUDIX is  
successfully shutdown. This takes about 2 minutes.  
5. The AUDIX System can now be removed for service.  
!
!
WARNING:  
If a translation card alarm is present, or if a translation card problem is  
suspected, do not save translations to the translation card.  
CAUTION:  
Check that the translation card is present in the TN798 Processor circuit  
pack.  
6. At the administration terminal, enter the save translation command.  
7. Set the Emergency Transfer switch on the Processor circuit pack to “ON.”  
!
CAUTION:  
When removing power, Error Log information is lost. If the data is to  
be retained, enter the reset system 4 command. This command  
restarts the system and may take several minutes. Wait for the login  
prompt before proceeding.  
8. Remove power from the cabinet by pulling the power cord from the AC  
appliance connector at the rear of the cabinet.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Restoring Power  
1
1-42  
Restoring Power  
The procedures you need to restore power depend on the system configuration.  
Before performing these activities, refer to the appropriate procedure. Restore  
power as follows:  
1. Plug in power cords in port cabinets first.  
2. Make sure that the translation card is properly inserted into the slot.  
3. The system now goes through the rebooting process.The translations are  
loaded from the translation card, and rebooting takes about 3 minutes.  
4. When system power is restored, the appropriate display is shown on the  
administration terminal.  
The display is the same as a reset system 4.  
5. Reset the time using the set time command. Use display time command  
to verify.  
Power Up the AUDIX System  
If the AUDIX was removed from the cabinet:  
1. Re-install the AUDIX and allow it to boot up automatically.  
2. Check fro SUCIX System errors.  
If the AUDIX remained in the cabinet, but power was removed from the cabinet:  
1. Power up the cabinet. The AUDIX reboots automatically.  
2. Check fro AUDIX System errors.  
If the AUDIX remained in the cabinet and the cabinet was not powered down:  
1. At the AUDIX console, hold the crtl key down and enter cc.  
2. Enter 5 at the prompt. In about 2 minuted the AUDIX boots up.  
3. When the system initialization is complete, log in as craft.  
4. Check for AUDIX System errors.  
Replacing the Power Supply  
1. Pull on the latch for the 650A Power Supply.  
2. Replace the power supply and secure the latch.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
System Backup  
1
1-43  
System Backup  
System translations can be restored by using the data on the system or on the  
backup translation card.  
Save Translation  
To ensure that the translation card contains the most recent copy of the  
translation data, the system can automatically save the translation data onto the  
translation card every 24 hours. Automatic daily backup of the system translation  
data is controlled by an entry in the system parameters that defaults to “daily.”  
If many translation data changes are made, it is recommended that you save the  
translation data using the save translation command. This action saves the new  
changes to the translation card without having to wait for the next automatic daily  
translation backup.  
NOTE:  
The save translation command blocks all maintenance commands.  
!
!
CAUTION:  
It is recommended that “save translation” be performed after business  
hours so that dial tone delays are not encountered.  
CAUTION:  
Do not issue the “save translation” command when alarm conditions are  
present.  
Translation Card Backup  
In case of a power failure, the system translations can be restored using the  
translation card. Translation data can be saved during the daily scheduled  
maintenance. However, if the translation data changes frequently, translations  
should be saved frequently to ensure that the most up-to-date information is kept.  
Note that only one translation card is provided with the system. It is  
recommended that the customer purchase additional translation cards to serve  
as backup or replacement. Translation cards should be alternated periodically.  
It is also recommended that backup copies of the translation data be made  
weekly, or after many changes have been made to the translation data. This  
minimizes the loss of recent translation data changes if the translation card in the  
system becomes damaged.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
System Backup  
1
1-44  
Save announcements  
Enter the save announcements command to save the recorded announcements  
in the system on the translation card.  
NOTE:  
This command is not necessary for the TN750C Announcement circuit  
pack.  
NOTE:  
A 10 MByte or larger translation card formatted for announcements (and/or  
translations) is required to save and restore announcements. For more  
information on formatting the translation card, see ‘‘format card-mem’’ in  
Chapter 2, ‘‘Maintenance Commands’’.  
The system takes about 40 minutes to complete this task. Because the terminal is  
unavailable during this time, it is recommended that this command be used after  
business hours. During this time period, the terminal cannot be used to  
administer the system until the save is complete; however, all other terminals (if  
provided) are allowed to perform administration procedures.  
Enter the restore announcements command to restore the recorded  
announcements from the translation card back into system memory. The system  
takes about 40 minutes to complete this task. After completing the task, the  
system performs an audit to make sure that the announcements on the  
announcement circuit pack match the announcements administered in the  
system.  
The working copy of the announcements is stored on the announcement circuit  
pack. A backup copy should be made on a 10 MByte or larger translation card.  
The following procedure is used to make a backup translation card:  
1. Remove the translation card from the Processor circuit pack.  
2. Insert the backup translation card into the Processor circuit pack.  
3. Enter the save announcement command and press Enter. This instructs  
the system to take all announcement information in memory and transfer it  
to the translation card. When finished, the following display appears:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
System Backup  
1
1-45  
save translation  
SAVE TRANSLATION  
Processor  
SPE-A  
Command Completion Status  
Success  
Error Code  
0
Command successfully completed  
Command:  
Figure 1-11. Save Translation screen  
4. Verify that the command successfully completes. If not, an error message  
appears. In such a case, refer to the “Translation Card Errors” section.  
5. If the system is equipped with a TN750 Announcement circuit pack, the  
recorded announcements can be saved using the save announcement  
commands. Enter the command and press Enter. The following display  
appears:  
save announcements  
SAVE ANNOUNCEMENTS  
Processor  
SPE-A  
Command Completion Status  
Success  
Error Code  
0
Command successfully completed  
Command:  
Figure 1-12. Save Announcements screen  
6. Verify that the command successfully completes. If not, an error message  
appears. In such a case, refer to the ‘‘Translation Card Errors’’ section that  
follows.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
System Backup  
1
1-46  
7. Remove the backup translation card and insert the original translation  
card.  
8. Label the backup translation card with the date and time it was updated. A  
special notation on the card clearly distinguishes it from other cards.  
9. Store the backup translation card in a secure place.  
Translation Card Errors  
Translation card-related failures may occur for two reasons: the card is at fault, or  
the Processor circuit pack is at fault. The following is a list of the error messages  
and recommended responses to each.  
1. Cannot access file storage area—Implies that the wrong  
translation card may be installed.  
Response: Check to see which translation card is installed. If the correct  
one is installed, test it by using the test card-mem command.  
2. Cannot turn on 12 volt power supply—Implies that something  
may be wrong with the Processor circuit pack that contains the power  
supply.  
Response: Test the 12-volt power supply by entering the test card-mem  
command from the terminal. Executing this command causes the system  
to run Test 701 (12 Volt Power Supply Test). If the power supply test fails,  
replace the Processor circuit pack. Then repeat whichever command  
failed.  
3. Invalid directory on Card-Mem— The translation card needs  
refreshing. Run test card-mem and be sure all tests pass.  
4. Card-Mem is unusable— Something is wrong with the translation  
card. Replace the translation card.  
5. Could not write to Card-Mem— Something is wrong with the  
translation card. Test the translation card.  
6. Request is incompatible with currently running  
operations— The storage system is in use. Try again later.  
7. Card-Mem is not inserted in the system— Insert the translation  
card.  
8. Cannot access file; wrong type of Card-Mem is inserted  
— The correct translation card for the desired operation has not been  
inserted. Load the appropriate translation card.  
9. File size exceeded— There is no more file space. Call your Lucent  
Technologies representative.  
10. Upgrade Memory Card inserted— The system upgrade translation  
card may have been inserted instead of the translations card. Insert the  
translation card.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-47  
11. Card-Mem is write-protected— The switch on the top side of the  
translation card is incorrectly set. Move the switch to the down position.  
12. Transmission problem; please try later— There is a problem  
communicating with the announcement circuit pack. Check to see that the  
announcement circuit pack has been correctly administered. Use the  
change data extension-number command. Verify that the announcement  
circuit pack is in the correct slot in the processor. If so, wait and retry.  
13. Command has been aborted; please try later— The command  
was pre-empted. Try again later.  
14. Saved copy of translations is unusable— The copy of the  
translations on your translation card is faulty. Re-enter the save  
translation command.  
Troubleshooting Features  
In addition to the various maintenance and test commands that are available, the  
following system features may also be useful in troubleshooting certain system  
resources:  
■
■
■
■
■
■
■
■
■
■
‘‘Automatic Circuit Assurance’’  
‘‘Busy Verification of Terminals and Trunks’’  
‘‘Trunk Group Busy/Warning Indicators to Attendant’’  
‘‘Trunk Identification by Attendant’’  
‘‘Facility Test Calls’’  
‘‘Analog Tie Trunk Back-to-Back Testing’’  
‘‘Terminating Trunk Transmission Testing’’  
‘‘Troubleshooting ISDN-PRI Problems’’  
‘‘Troubleshooting PRI Endpoint Problems’’  
‘‘Troubleshooting ISDN-PRI Test Call Problems’’  
Automatic Circuit Assurance  
A display-equipped voice terminal (may be nondisplay type if the Voice Message  
Retrieval feature is provided) or an attendant console is required. An “ACA  
activate/deactivate” button (one per system) is required on the voice terminal or  
attendant console.  
Automatic Circuit Assurance (ACA) assists users in identifying possible trunk  
malfunctions. The system maintains a record of the performance of individual  
trunks relative to short and long holding time calls. The system automatically  
initiates a referral call to an attendant console or display-equipped voice terminal  
when a possible failure is detected.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-48  
Holding time is the elapsed time from when a trunk is accessed to the time a  
trunk is released. When ACA is enabled through administration, the system  
measures the holding time of each call.  
A short holding time limit and a long holding time limit are preset by the System  
Manager for each trunk group. The short holding time limit can be from 0 to 160  
seconds. The long holding time limit can be from 0 to 10 hours. The measured  
holding time for each call is compared to the preset limits for the trunk group  
being used.  
Measurements are not made on personal CO lines, out-of-service trunks, or  
trunks undergoing maintenance testing.  
Busy Verification of Terminals and Trunks  
A multi-appearance voice terminal or attendant console equipped with a “verify”  
button is required.  
Busy Verification of Terminals and Trunks allows a user at a voice terminal or  
attendant console to make test calls to trunks, voice terminals, and hunt groups  
(DDC/UCD). These test calls check the status of an apparently busy resource.  
This provides an easy method to distinguish between a voice terminal or  
resource that is truly busy and one that only appears busy because of a trouble  
condition.  
Trunk Group Busy/Warning Indicators to  
Attendant  
An attendant console is required.  
Trunk Group Busy/Warning Indicators to Attendant provides the console user  
with a visual indication of the trunk group status for each trunk group associated  
with the 12 Trunk Group Select buttons located on the console. Trunk groups with  
busy indications during nonbusy periods should be checked to ensure that the  
trunks are busy and not out-of-service. Use the Busy Verification of Terminals and  
Trunks feature to test the suspected faulty trunks.  
Trunk Identification by Attendant  
A display-equipped voice terminal or an attendant console equipped with a  
“trunk id” button is required.  
Trunk Identification by Attendant allows a voice terminal or attendant console  
user to identify a specific trunk being used on a call. This is useful when a user  
experiences noise or poor transmission on a trunk call. The trunk identification  
(access code and group number) is displayed when the “trunk id” button is  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-49  
pressed while on a trunk call. Use of this feature is denied if there are more than  
two trunks on a call. If the call is trunk-to-trunk, the identification displayed is of  
the last trunk added to the call.  
Facility Test Calls  
The Facility Test Calls feature provides a voice terminal user the capability of  
placing test calls to access specific trunks, touch-tone (DTMF) receivers, time  
slots, and system tones. The test call can be made by a local voice terminal user  
by dialing an access code.  
NOTE:  
For the ISDN-PRI Test Call feature, see ‘‘Troubleshooting the Outgoing  
ISDN-Testcall Command’’ later in this chapter.  
The following Facility Test Calls are described below:  
■
■
■
■
‘‘Trunk Test Call’’  
‘‘Touch-tone (DTMF) Receiver Test Call’’  
‘‘Time Slot Test Call’’  
‘‘System Tone Test Call’’  
Trunk Test Call  
The trunk test call accesses specific Tie or CO trunks. DID trunks cannot be  
accessed.  
To place a call:  
1. Dial the Facility Test Call Feature Access Code (for example, 197, see  
Note), and listen for dial tone.  
NOTE:  
The Facility Test Call Access Code (FAC) is administered on the  
Feature Access Codes Form. The 197 FAC code used here is an  
example.  
2. Dial the 6-digit port number PCSSpp  
P
=
=
=
=
Port network number (1)  
Carrier number (A=1, B=2, C=3)  
Slot number (01-10)  
C
SS  
pp  
Port number  
The channels on a DS1 trunk are addressed by using the channel number  
for the port number.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-50  
3. Listen for one of the following tones:  
■
Dial Tone or Silence—trunk is connected. Go to Step 4. If you hear  
a dial tone, it is coming from the far end. If the far end has been  
disabled, you do not hear dial tone. However, depending on far-end  
administration, you may still be able to dial digits. All digits dialed  
after the port number are transmitted using end-to-end DTMF  
signaling; therefore, if the trunk being tested is a rotary trunk, it is  
not possible to break dial tone.  
■
■
Reorder Tone—trunk is busy or maintenance busy.  
Intercept Tone— a trunk or touch-tone (DTMF) receiver has not  
been accessed.  
4. Place a call. Even if you do not hear a dial tone, you may still be able to  
dial digits, depending on the administration of the far-end switch.  
All digits dialed after the port number are transmitted using end-to-end  
DTMF signaling; therefore, if the trunk being tested is a rotary trunk, it is  
not possible to break dial tone.  
If the call does not go through (that is, no ringing), determine if the trunk  
circuit pack has been removed.  
!
CAUTION:  
To leave the Facility Test Call administered after you logoff poses a  
significant security risk that unauthorized individuals may connect to  
the telecommunications network through the use of test call features.  
To remove the Facility Test Calls Access Code, do the following:  
a. Enter change feature-access-codes to display the Feature Access  
Code screen.  
b. Leave the Facility Test Calls Access Codefield blank.  
Touch-tone (DTMF) Receiver Test Call  
The touch-tone (DTMF) receiver call accesses and tests the four touch-tone  
(DTMF) receivers located on the TN744D Tone Detector circuit pack. To place the  
call:  
1. Dial the Facility Test Call Feature Access Code (for example, 197, see  
Note), and listen for dial tone.  
NOTE:  
The Feature Access Code (FAC) is administered on the Feature  
Access Codes Form. The 197 FAC code used here is an example.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-51  
2. Dial the 6-digit port number PCSSpp:  
P
=
=
=
=
Port network number (1)  
C
Carrier number (A=1, B=2, C=3)  
Slot number (01-10)  
SS  
pp  
Touch-tone (DTMF) Receiver Port number (01, 02, 05, or 06)  
3. Listen for one of the following tones:  
■
Confirmation Tone—touch-tone (DTMF) receiver is connected. Go  
to Step 4.  
■
■
Reorder Tone—touch-tone (DTMF) receiver is busy.  
Intercept Tone—a touch-tone (DTMF) receiver or trunk has not been  
accessed.  
4. Dial 1234567890*# and listen for Confirmation tone (test passed) or  
intercept tone (test failed). The test fails if the touch-tone (DTMF) receiver  
does not recognize all the touch-tone (DTMF) signals.  
5. To test another touch-tone (DTMF) receiver, repeat Steps 2 through 4.  
6. To terminate the test call, hang up the station set used for testing.  
Time Slot Test Call  
The time slot test call connects the voice terminal user to a specific time slot  
located on the TDM Buses (A or B) or out-of-service time slots. Specific Time  
Slots To place the call:  
1. Dial the Facility Test Call Feature Access Code (for example, 197, see  
Note), and listen for dial tone.  
NOTE:  
The Feature Access Code (FAC) is administered on the Feature  
Access Codes Form. The 197 FAC code used here is an example.  
2. Dial port network number (1), then press # and the 3-digit time slot number  
“sixty,” where:  
xxx  
=
Time slot number (000 through 255 on Bus A and 256  
through 511 on Bus B)  
3. Listen for one of the following tones:  
■
■
■
Confirmation Tone—time slot is idle or maintenance busy  
Reorder Tone—time slot is busy  
Dedicated Tone—One of the following tones is heard (see Table  
1-4)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-52  
Table 1-4. TDM Bus Time Slot Numbers  
TDM Bus A  
TDM Bus B  
time slot  
time slot  
000  
001  
002  
003  
004  
005  
006  
007  
008  
009  
010  
011  
012  
013  
014  
015  
Tone Heard  
256  
257  
258  
259  
260  
261  
262  
263  
264  
265  
266  
267  
268  
269  
270  
271  
272  
273  
274  
275  
276  
277  
278-509  
510  
511  
Reorder  
Reorder  
Reorder  
Reorder  
Reorder  
Touch Tone 1 - 697Hz  
Touch Tone 2 - 770 Hz  
Touch Tone 3 - 852Hz  
Touch Tone 4 - 941 Hz  
Touch Tone 5 - 1209 Hz  
Touch Tone 6 - 1336Hz  
Touch Tone 7 - 1447 Hz  
Touch Tone 8 - 1633 Hz  
Dial Tone  
Reorder Tone  
Alert Tone  
016  
Busy Tone  
017  
018  
019  
020  
021  
022-253  
254  
255  
Ringback Tone  
Special Ringback Tone  
2225 Hz Tone  
Music  
Tone on Hold  
Confirmation (used for calls)  
Reorder  
Confirmation  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-53  
Out-of-Service Time Slots to place the call:  
1. Dial the Facility Test Call Feature Access Code (for instance, 197, see  
Note), and listen for dial tone.  
NOTE:  
The Feature Access Code (FAC) is administered on the Feature  
Access Codes Form. The 197 FAC code used here is an example.  
2. Dial port network number (1), then dial ** and listen for the following tones:  
■
Confirmation Tone—Connection is made. Go to Step 3.  
Reorder Tone—No time slots are out-of-service.  
■
3. Repeat from Step 1 to alternate between out-of-service time slots on TDM  
Bus A and B.  
System Tone Test Call  
The system tone test call connects the voice terminal user to a specific system  
tone. To place the call:  
1. Dial the Facility Test Call Feature Access Code (for instance, 197, see  
Note), and listen for dial tone.  
NOTE:  
The Facility Test Call Access Code (FAC) is administered on the  
Feature Access Codes Form. The 197 FAC code used here is an  
example.  
2. Dial port network number (1), then dial *, followed by the two-digit tone  
identification number listed in Table 1-5.  
NOTE:  
For a definition of Call Progress Tones see DEFINITY Enterprise  
Communications Server Administration and Feature Description.  
Table 1-5. System Tone Identification Numbers  
Number  
00  
Description  
Null tone  
01  
Dial tone  
02  
Reorder tone  
Alert tone  
Busy tone  
03  
04  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-54  
Table 1-5. System Tone Identification Numbers — Continued  
Description  
Number  
05  
06  
07  
08  
09  
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
27  
28  
29  
30  
31  
32  
33  
34  
Recall dial tone  
Confirmation tone  
Internal call waiting tone  
Ringback tone  
Special ringback tone  
Dedicated ringback tone  
Dedicated special ringback tone  
Touch tone 1  
Touch tone 2  
Touch tone 3  
Touch tone 4  
Touch tone 5  
Touch tone 6  
Touch tone 7  
Touch tone 8  
Chime  
350 Hz  
440 Hz  
480 Hz  
620 Hz  
2025 Hz  
2225 Hz  
Counter  
External call waiting  
Priority call waiting  
Busy verification  
Executive override/intrusion tone  
Incoming call identification  
Dial zero  
Attendant transfer  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-55  
Table 1-5. System Tone Identification Numbers — Continued  
Description  
Number  
35  
36  
37  
38  
39  
40  
41  
42  
43  
44  
45  
46  
47  
48  
49  
50  
51  
52  
53  
54  
55  
56  
57  
58  
59  
60  
61  
62  
63  
64  
Test calls  
Recall on don’t answer  
Audible ring  
Camp-on recall  
Camp-on confirmation  
Hold recall  
Hold confirmation  
Zip tone  
2804 Hz  
1004 Hz (-16dB)  
1004 Hz (0 dB)  
404 Hz  
Transmission test sequence 105  
Redirect tone  
Voice signaling tone  
Digital milliwatt  
440 Hz + 480 Hz  
Music  
Transmission test sequence 100  
Transmission test sequence 102  
Laboratory test tone 1  
Laboratory test tone 2  
Disable echo supervision dial tone  
7 seconds of answer tone  
4 seconds of answer tone  
Restore music (or silence)  
Warning tone  
Forced music tone  
Zip tone (first of 2 sent)  
Incoming call ID (first of 2 sent)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-56  
Table 1-5. System Tone Identification Numbers — Continued  
Number  
Description  
65  
66  
67  
68  
Tone on hold  
CO dial tone  
Repetitive confirmation tone  
Conference/bridging tone  
Analog Tie Trunk Back-to-Back Testing  
The TN760B circuit pack can be configured for back-to-back testing (also known  
as connectivity testing) by making translation and cross-connect changes. This  
testing configuration allows for the connection of Tie Trunks back-to-back in the  
same switch to verify the operation of Tie Trunk ports. The tests can be  
performed in either the E & M or simplex modes.  
E & M Mode Test Procedure  
The procedures to perform the Analog Tie Trunk port test in the E & M mode are  
as follows:  
1. At the administration terminal, enter list configuration trunks command  
to determine which ports are assigned on the Tie Trunk circuit pack.  
2. Enter display dialplan command to determine the Trunk Access Code  
(TAC) format.  
3. Enter display port xx command for all ports defined in Step 1. This action  
displays the trunk groups to which the ports belong (that is, of which the  
ports are members).  
NOTE:  
See the ‘‘Control Circuit Packs’’ section in this chapter for details on  
how to remove and replace port circuit packs.  
4. Insert the circuit pack back into the slot.  
5. Enter display trunk xx p command for each trunk group identified in Step  
3. This command displays the specified trunk group on the administration  
terminal screen and prints a hard copy on the printer. Save this data for  
later use.  
6. Remove all members defined by these ports from the trunk group(s) using  
the ch trunk xx command.  
7. RemovDeotwhneloaTdiefroTmruWnwkwc.Sirocmuaintupalas.ccokmf.roAlml MtahneuaclsaSreraiercrhsAlondt.Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-57  
8. Set the dip (option) switches for each of the two ports to be tested on the  
Tie Trunk circuit pack to “E & M mode” and “unprotected.”  
9. Enter add trunk n command to add a new (test) trunk group. Then enter  
the following information:  
■
■
■
■
■
■
Group Type — tie  
TAC — (use trunk access code obtained from dial plan)  
Trunk Type (in/out) — wink/wink  
Port — assign two of the ports from the tie trunk  
Mode — E & M  
Type — specify one port as t1 standard and other port as t1  
compatible  
Examples of the Trunk Group forms are shown in Figure 1-13 and Figure  
1-14.  
display trunk-group 10  
Page 1 of 5  
TRUNK GROUP  
Group Type: tie  
COR: 1  
Outgoing Display? n  
Group Number: 10  
Group Name: tr 10  
Direction: two-way  
MIS Measured? n  
Dial Access? y  
CDR Reports? y  
TAC: 110  
Data Restriction? n  
Busy Threshold: 60  
Internal Alert? n  
Auth Code? n  
Night Service:  
Incoming Destination:  
Queue Length: 0  
Comm Type: voice  
TRUNK PARAMETERS  
Trunk Type (in/out): wink/wink  
Outgoing Dial Type: tone  
Incoming Rotary Timeout(sec): 5  
Incoming Dial Type: tone  
Disconnect Timing(msec): 500  
Digits:  
Digit Treatment:  
Used for DCS? n  
ACA Assignment? n  
Baud Rate: 1200  
Incoming Dial Tone? y  
Answer Supervision Timeout:  
Synchronization: async  
Maintenance Tests? y  
Suppress # Outpulsing? n  
Duplex: full  
Figure 1-13. Trunk Group Form  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-58  
Page 2 of 5  
TRUNK GROUP  
GROUP MEMBER ASSIGNMENTS  
Port  
Name  
Mode  
Type  
Answer Delay  
1: B1901  
2: B1902  
3:  
E & M  
E & M  
t1 stan  
t1 comp  
4:  
5:  
6:  
7:  
8:  
9:  
10:  
11:  
12:  
13:  
14:  
15:  
Figure 1-14. Trunk Group Form — E & M Mode (Page 2 of 2)  
10. Locate the Tie Trunk port terminal connections at the cross-connect field.  
See Table 1-6.  
Table 1-6. Carrier Lead Appearances at  
110 Cross-Connect Field  
110 Connecting  
Block Terminals  
CO Trunk TN747B  
Tie Trunk TN760B  
1
2
3
4
5
6
7
8
T1  
R1  
T1  
R1  
T11  
R11  
E1  
M1  
T2  
T2  
R2  
R2  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-59  
Table 1-6. Carrier Lead Appearances at  
110 Cross-Connect Field — Continued  
110 Connecting  
Block Terminals  
CO Trunk TN747B  
Tie Trunk TN760B  
9
T12  
R12  
E2  
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
27  
28  
29  
30  
31  
32  
32  
33  
34  
36  
37  
M2  
T3  
T3  
R3  
R3  
T13  
R13  
E3  
M3  
T4  
T4  
R4  
R4  
T14  
R14  
E4  
M4  
T5  
R5  
T6  
R6  
T7  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-60  
Table 1-6. Carrier Lead Appearances at  
110 Cross-Connect Field — Continued  
110 Connecting  
Block Terminals  
CO Trunk TN747B  
Tie Trunk TN760B  
38  
39  
40  
41  
42  
43  
44  
45  
46  
47  
48  
49  
50  
R7  
T8  
R8  
11. At the cross-connect field, disconnect outside trunk facilities from the Tie  
Trunk ports and mark the disconnected wires for later reconnecting the Tie  
Trunk ports back to normal operation. The D Impact Tool (AT-8762) is  
required to perform this step.  
12. Use jumper wires (DT 24M-Y/BL/R/G and DT 24P-W/BRN) and the D  
Impact Tool to connect wiring between the two ports assigned in Step 9 at  
the cross-connect field. For example, if the two ports on the Analog Tie  
Trunk circuit pack are port 1 and 2, connect the wirings as shown below:  
Port  
1
Port  
2
T1  
R1  
T11  
R11  
E1  
T12  
R12  
T2  
R2  
M2  
E2  
M1  
t1 stan  
E&M  
t1 comp  
E&M  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-61  
13. Check all wiring to verify good connections between the two test ports.  
14. Place a call from one voice terminal to another voice terminal using the Tie  
Trunk ports assigned. Dial TAC and extension. For example, if TAC of Tie  
Trunk group is 110 and station number is 5012, then dial 110 5012. If the  
call cannot be made, either one of these ports could be defective. There  
are four ports on TN760B (port 1, 2, 3, and 4), try different combinations to  
determine defective ports.  
15. If there is a defective port on the circuit pack, try to switch to an unused  
port. However, if all ports are normally used, then replace the circuit pack.  
16. Disconnect the jumpers between two ports. Then use administration  
terminal and trunk printouts to restore all trunk group changes to normal  
values.  
Analog Tie Trunk Port Test Procedure  
The procedures to perform the Analog Tie Trunk Port Test in the simplex mode  
are as follows:  
1. Repeat Steps 1 through 7 of the E & M Mode Test Procedure.  
2. Set the dip (option) switches for each of the two ports to be tested on the  
Tie Trunk circuit pack to simplex mode.  
3. Enter add trunk n command to add a new (test) trunk group. Then enter  
the following information:  
■
■
■
■
■
■
Group Type — tie  
TAC — (use trunk access code obtained from dial plan)  
Trunk Type (in/out) — wink/wink  
Port — assign two of the ports from the tie trunk  
Mode — simplex  
Type — type 5  
An example of the Trunk Group Form Page 2 is shown in Figure 1-15.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-62  
Page 2 of 5  
TRUNK GROUP  
GROUP MEMBER ASSIGNMENTS  
Port  
Name  
Mode  
Type  
Answer Delay  
1: B1901  
2: B1902  
3:  
simplex  
simplex  
type 5  
type 5  
4:  
5:  
6:  
7:  
8:  
9:  
10:  
11:  
12:  
13:  
14:  
15:  
Figure 1-15. Trunk Group Form — Simplex Mode (Page 2 of 5)  
4. Locate the Tie Trunk port terminal connections at the cross-connect field.  
See Table 1-6.  
5. At the cross-connect field, disconnect outside trunk facilities from the  
Analog Tie Trunk ports and mark the disconnected wires for later when the  
Tie Trunk ports are placed back into normal operation. The D Impact Tool  
(AT-8762) is required to perform this step.  
6. Use jumper wires (DT 24M-Y/BL/R/G) and the D Impact Tool to connect  
wiring between the two ports assigned in Step 4 at the cross-connect field.  
For example, if the two ports on the Analog Tie Trunk circuit pack are ports  
1 and 2, connect the wirings as shown below:  
Port  
1
Port  
2
T1  
R1  
T11  
R11  
T12  
R12  
T2  
R2  
type  
5
type  
5
simplex  
simplex  
7. Repeat Steps 13 through 16 of the E & M Mode Test Procedure.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-63  
Terminating Trunk Transmission Testing  
The Terminating Trunk Transmission (TTT) (noninteractive) feature provides for  
extension number access to three tone sequences that can be used for trunk  
transmission testing from the far end of the trunks.  
The three test types should have extension numbers assigned on the  
Maintenance-Related System Parameters Form.  
Test Type 100:_____ Test Type 102:_____ Test Type 105:_____  
Test Type 100 provides:  
1. 5.5 seconds of 1004 Hz tone at 0dB  
2. Quiet until disconnect; disconnect is forced after one minute  
Test Type 102 provides:  
1. 9 seconds of 1004 Hz tone at 0dB  
2. 1 second of quiet  
3. This cycle is repeated until disconnect; disconnect is forced after 24  
hours.  
Test Type 105 provides:  
1. nine seconds of 1004 Hz at -16dB  
2. one second of quiet  
3. nine seconds of 404 Hz at -16dB  
4. one second of quiet  
5. nine seconds of 2804 Hz at -16dB  
6. 30 seconds of quiet  
7. one half second of Test Progress Tone (2225 Hz)  
8. approximately five seconds of quiet  
9. forced disconnect  
Troubleshooting ISDN-PRI Problems  
The following flowchart, Figure 1-16 and Figure 1-17, defines a layered approach  
when troubleshooting ISDN-PRI problems. Since a problem at a lower layer  
affects upper layers, layers are investigated from low to high. In the flowchart, the  
DS1 facility is layer 1, the TN765 Processor Interface is layer 2, and the ISDN  
trunks are layer 3. Transient problems are diagnosed on Page 2 of the flowchart,  
Figure 1-17.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-64  
START  
ARE THERE  
ALARMS OR  
DETERMINE PRESENT  
STATUS OF DS-1 FACILITY  
VIA DS1-BD MO SECTION.  
FOLLOW REPAIR PROCEDURES  
YES  
ERRORS AGAINST  
DS1-BD  
NO  
IF MULITPLE ALARMS EXIST,  
INVESTIGATE IN FOLLOWING  
ARE THERE  
ALARMS OR  
ORDER:  
PI-BD  
PI-PT  
YES  
ERRORS AGAINST  
PI-BD, PI-PT, PI-SCI,  
PI-LINK, OR  
PI-SCI  
PI-LINK  
ISDN-LINK  
ISDN-LINK  
FOLLOW REPAIR PROCEDURE  
FOR APPROPRIATE MO  
NO  
ARE THERE  
ALARMS OR  
YES  
FOLLOW REPAIR  
ERRORS AGAINST  
ISDN-TRK  
PROCEDURE FOR ISDN-TRK  
NO  
END  
TO  
A
PAGE  
2
Figure 1-16. Processing of ISDN-PRI Problems (Page 1 of 2)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-65  
COMPARE INDICATED  
FACILITY TO RECORD  
OF PREVIOUS PROBLEMS  
FROM  
A
PAGE  
PERFORM AN IN-DEPTH  
ANALYSIS OF T1  
1
FACILITY INCLUDING:  
TRANSMISSION FACILITY,  
EXTERNAL EQUIPMENT  
(DACS, CSUs, ETC.,)  
AND ANY OTHER  
ARE  
THERE  
ARE BIT  
TRANSIENT  
PROBLEMS MAKING  
ISDN-PRI  
ERRORS OCCURRING  
MORE FREQUENTLY  
THAN PREVIOUS  
HISTORY  
NO  
YES  
NOISE-PRODUCING  
EQUIPMENT.  
CALLS  
REFER TO AT&T PRACTICE  
855-351-101 ISSUE 8,  
JANUARY 1987. THIS  
DESCRIBES T1 CABLING TO  
CSUs, ETC, IN DETAIL  
END  
YES  
NO  
ARE  
THERE BIT  
ERRORS OVER  
THE TI FACILITY?  
USE LIST  
YES  
RECORD INDICATED  
FACILITY AND, IF THIS  
CONTINUES TO OCCUR,  
CONTACT FACILITY OR  
EXTERNAL EQUIPMENT  
PROVIDER. THEN ESCALATE  
MEASUREMENTS  
COMMAND  
END  
NO  
HAS A  
SYNCHRONIZATION  
SOURCE BEEN  
UNSTABLE?  
SEE DS1-BD MO FOR  
REPAIR PROCEDURES IF  
SYNC PROBLEM IS DUE  
TO SLIPS. OTHERWISE,  
FOLLOW REPAIR  
YES  
SYSTEM SWITCHING  
AWAY FROM IT?  
SEE SYNC MO  
PROCEDURES FOR  
SYNC MO  
NO  
IF PROBLEMS  
STILL EXIST,  
THEN ESCALATE  
Figure 1-17. Processing of ISDN-PRI Problems (Page 2 of 2)  
Troubleshooting PRI Endpoint Problems  
The following flowchart, Figure 1-18 and Figure 1-19, defines a layered approach  
when troubleshooting PRI endpoint problems. Since a problem at a lower layer  
affects upper layers, layers are investigated from low to high. In the flowchart, the  
DS1 facility is layer 1, the TN765 Processor Interface is layer 2, and the ISDN  
trunks are layer 3.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-66  
The troubleshooting procedure described here diagnoses faults between the  
switch and the line-side PRI terminal adapter/ISDN-PRI endpoint equipment.  
Problems encountered on the network-side of a wideband connection or  
problems with end-to-end equipment compatibility are outside the scope of this  
manual.  
START  
Are there  
YES  
alarms or  
errors against  
DS1-BD?  
FOLLOW REPAIR PROCEDURE  
IN THE DS1-BD MO SECTION  
NO  
Are there  
alarms or  
IF MULTIPLE ALARMS EXIST,  
INVESTIGATE IN THE  
FOLLOWING ORDER: PI-BD,  
PI-PT, PI-SCI, PI-LINK,  
ISDN-LNK, AND ISDN-SGR.  
FOLLOW REPAIR PROCEDURE  
FOR APPROPRIATE MO.  
YES  
errors against  
PI-BD, PI-PT,  
PI-SCI, PI-LINK,  
ISDN-SGR, or  
ISDN-  
LNK?  
NO  
YES  
Are there  
alarms or  
FOLLOW REPAIR PROCEDURE  
IN THE PE-BCHL MO SECTION  
errors against  
PE-BCHL?  
NO  
Does  
the  
PRI Terminal  
Adapter or the  
ISDN endpoint  
equipment  
YES  
FOLLOW REPAIR PROCEDURE  
RECOMMENDED BY THE PRI  
TERMINAL ADAPTER  
VENDOR  
indicate alarms or  
errors? Check the  
endpoint equipment  
for status - not  
the  
OR ISDN ENDPOINT  
EQUIPMENT VENDOR  
SAT  
NO  
Is the  
administration  
NO  
between the endpoint  
equipment and the  
switch consistent?  
(for example, port  
boundary,  
FIX ADMINISTRATION  
MISMATCH  
END  
width, etc.)  
YES  
TO  
PAGE 2  
A
Figure 1-18. Processing of PRI Endpoint Problems (Page 1 of 2)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-67  
A
FROM  
PAGE 1  
Does  
every  
call fail or  
are the  
failings  
transient?  
TRANSIENT FAILURES  
ALWAYS FAIL  
CHECK THE HEALTH OF THE  
APPLICATION EQUIPMENT  
(FOR EXAMPLE, VIDEO CODEC)  
AND THE HEALTH OF THE  
DEFINITY NETWORK  
Are there  
bit errors  
Perform an in-depth  
analysis of DS1  
over the DS1  
interface between the  
switch and the PRI  
Terminal Adapter or  
the ISDN endpoint  
equipment. Use  
‘‘list measurement’’  
command.  
YES  
interface between the  
switch and the  
endpoint equipment,  
including the premise  
distribution wiring,  
endpoint equipment,  
and any other noise-  
producing equipment.  
IF THE PROBLEM STILL EXISTS,  
THEN ESCALATE  
NO  
END  
Has a  
synchronization  
source been unstable?  
System switching away  
from it? Check  
for alarms and  
errors against  
YES  
FOLLOW REPAIR  
PROCEDURE FOR  
SYNC MO  
SYNC.  
NO  
IF PROBLEM STILL  
EXISTS, THEN  
ESCALATE  
Figure 1-19. Processing of PRI Endpoint Problems (Page 2 of 2)  
Troubleshooting ISDN-PRI Test Call Problems  
An ISDN-PRI test call is a diagnostic call placed across an ISDN-PRI  
user-network interface to a previously-designated number. An ISDN-PRI test call  
is also a maintenance procedure concerned with the identification and  
verification ISDN-PRI user-network interface problems. The ISDN-PRI test call  
can access ISDN-PRI trunks only.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-68  
Placing an Outgoing ISDN-PRI Test Call  
NOTE:  
An ISDN-PRI test call can be placed only if the circuit translates to an  
ISDN-PRI trunk.  
An ISDN-PRI test call can be originated via either the synchronous or the  
asynchronous method. Each method is described below.  
Synchronous Method  
One command is used in this method to start, stop and query an ISDN-PRI test  
call. In the synchronous method, an outgoing ISDN-PRI test call may be part of a  
system technician-demanded long test sequence to test a circuit pack, port, or  
trunk. Therefore, the command line entry can be any of the following:  
test trunk <grp>/<mbr> long [repeat #]  
test port PCSSpp long [repeat #]  
test board PCSS long [repeat #]  
The “long” qualifier must be entered in the above commands in order for the  
ISDN test call to run. The repeat number (#) can be any number from 1 through  
99 (default = 1).  
The following information is displayed in response to the above commands:  
■
■
■
■
■
Port: The port address (PCSSpp) of the maintenance object under test.  
Maintenance Name: The type of maintenance object tested.  
Test Number: The actual test that was run.  
Test Results: Indicates whether the test passes, fails, or aborts.  
Error Code: Additional information about the results of the test. (See the  
ISDN Trunk Maintenance documentation for details.)  
Asynchronous Method  
NOTE:  
The asynchronous method requires a Maintenance/Test circuit pack to be  
physically present in the system.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-69  
In this method, four commands are used to start, stop, query, and list an outgoing  
ISDN-PRI test call. These commands are as follows:  
clear isdn-testcall <grp>/<mbr> (stop)  
list isdn-testcall (list)  
status isdn-testcall <grp>/<mbr> (query)  
test isdn-testcall <grp>/<mbr> [minutes] (start)  
NOTE:  
Before placing an outgoing ISDN-PRI test call, verify that the FAC on the  
System Features Form has been administered as well as the Far End Test  
Line No and TestCall Bearer Capability Class (BCC) on the Trunk Group  
Administration Form. Furthermore, if the ISDN-PRI trunk is of the “cbc” (call  
by call) service type, then the Testcall Servicefield on Trunk Group  
Administration Form must have been administered also.  
To initiate an outgoing ISDN-PRI test call in the asynchronous method, issue the  
following command:  
test isdn-testcall <grp>/<mbr> [minutes]  
This command enables you to specify a specific the trunk on which to originate  
the ISDN-PRI test call.  
NOTE:  
The optional qualifier can also be used that specifies in minutes the  
duration of the test call. If no duration is specified, the default duration is  
used which is 8.4 or 9.6 seconds. The qualifier “minutes” accepts the  
numeric values one through 120 (that is, two hours = 120 minutes).  
Figure 1-20 shows a typical response to the test isdn-testcall command:  
test isdn-testcall  
Port  
Maintenance Name  
Test Number  
258  
Test Result Error Code  
PASS  
1B1501 ISDN-TRK  
Figure 1-20. Typical Response to Test ISDN-Testcall Command  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Troubleshooting Features  
1
1-70  
Field descriptions  
Port  
Port address: PCSSpp (cabinet-carrier-slot-circuit)  
Name of maintenance object  
Maintenance Name  
Test Number  
Test Result  
Error Code  
The actual test that was run.  
Test result: Pass, Fail, Abort  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO or see  
the ISDN Trunk Maintenance documentation for details.  
The functions of the clear, list, and status commands associated with the ISDN  
Testcall are summarized in the following list. For more detailed information, refer  
to the appropriate sections as directed.  
■
■
■
Clear isdn-testcall <grp>/<mbr> enables you to cancel an in-progress  
ISDN-PRI test call and allow another test call to start. For details on this  
command, refer to the ‘‘clear isdn-testcall’’ command in Chapter 2,  
‘‘Maintenance Commands’’.  
List isdn-testcall <grp>/<mbr> enables you to list all the ISDN-PRI trunks  
in use for an ISDN-PRI test call in the system. For details on this command,  
refer to the ‘‘list testcalls’’ command in Chapter 2, ‘‘Maintenance  
Commands’’.  
Status isdn-testcall <grp>/<mbr no> [minutes] enables you to check on  
the progress of an outgoing test call. When an outgoing ISDN-PRI test call  
completes in a specific port network, another ISDN-PRI trunk from the  
same port network is available for testing (regardless of whether the  
status information has been displayed). For details on this command,  
refer to the ‘‘status isdn-testcall’’ command description in Chapter 2,  
‘‘Maintenance Commands’’.  
Troubleshooting the Outgoing ISDN-Testcall  
Command  
If the TestCall BCC field appears on the Trunk Group Administration Form, make  
sure the TestCall BCC field indicates the correct BCC for the service provisioned  
on the ISDN-PRI trunk. The TestCall BCC values are defined as follows:  
■
■
■
0—Voice  
1—Digital Communications Protocol Mode 1  
2—Mode 2 Asynchronous  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-71  
■
■
3—Mode 3 Circuit  
4—Digital Communications Protocol Mode 0 (usually the default).  
NOTE:  
If the ISDN-PRI trunk is of type “cbc,” make sure the TestCall Service field  
on the Trunk Group Administration Form indicates the correct service so  
that a network facility message can be sent across the ISDN-PRI network  
If the outgoing ISDN-PRI test call keeps aborting, please make sure that the  
far-end device can handle DCP Mode 0 or DCP Mode 1.  
NOTE:  
Before attempting to make an ISDN-PRI test call to the public network (that  
is, the network is the far-end), make sure that test call service is provisioned  
by the network. The user must subscribe to Test Type 108 service and have  
the correct far-end test call number administered on the trunk group form  
for the call to be allowed.  
Install DS1 CPE Loopback Jack (T1  
Only)  
Using the DS1 CPE Loopback Jack (apparatus code 700A, comcode  
107988867), a technician can test the DS1 span between the system and the  
network interface point. The 700A can quickly isolate DS1 problems to either the  
customer premises or to the external DS1 span.  
The 700A loopback jack is required when DC power appears at the interface to  
the ICSU. The loopback jack isolates the ICSU from the DC power and properly  
loops the DC span power. The 700A is also used when no smart jack is installed  
by the local phone company.  
NOTE:  
The loopback jack operates with any vintage of TN767E (or later) or  
TN464F (or later) DS1 circuit packs. The loopback jack operates with the  
120A2 (or later) Integrated Channel Service Unit (ICSU) only; not the 31xx  
series of CSUs, other external CSUs, or earlier ICSUs.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-72  
Loopback Jack Installation  
Configurations Using a Smart Jack  
The preferred location of the loopback jack is at the interface to the Smart Jack.  
This provides maximum coverage of CPE wiring when remote tests are run using  
the loopback jack. If the Smart Jack is not accessible, install the loopback jack at  
the extended demarcation point.  
1. If there is no extended demarcation point, install the loopback jack directly  
at the network interface point as shown in Figure 1-21.  
2. If there is an extended demarcation point and the Smart Jack is not  
accessible, install the loopback jack as shown in Figure 1-22.  
3. If there is an extended demarcation point, but the Smart Jack is  
accessible, install the loopback jack as shown in Figure 1-23.  
Configurations Without a Smart Jack  
1. Install the loopback jack at the point where the cabling from the ICSU  
plugs into the “dumb” block. If there is more than one “dumb” block,  
choose the one that is closest to the Interface Termination feed or the fiber  
MUX. This provides maximum coverage for loopback jack tests. Refer to  
Figure 1-24 and Figure 1-25.  
Installation  
1. To install the loopback jack, simply disconnect the RJ-48 (8-wide)  
connector (typically an H600-383 cable) at the appropriate interface point  
and connect the loopback jack in series with the DS1 span. See Figure  
1-21 through Figure 1-25.  
2. Plug the H600-383 cable from the ICSU into the female connector on the  
loopback jack.  
3. Plug the male connector on the loopback jack cable into the network  
interface point.  
NOTE:  
Do not remove the loopback jack after installation. This is not a test  
tool and should always be available to remotely test a DS1 span.  
Administration  
1. At the management terminal, enter change ds1 <location>. The  
“location” is the DS1 interface circuit pack for which the loopback jack  
was installed.  
2. Be sure the “near-end CSU type” is set to integrated.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-73  
3. On page 2 of the form, change the supply CPE loopback jack  
powerfield to y.  
NOTE:  
Setting this field to y informs the technician that a loopback jack is  
present on the facility. This allows a technician to determine that the  
facility is available for remote testing.  
4. Enter save translation to save the new information.  
DS1 Span Test  
This test should only be performed after the DS1 circuit pack and the 120A2 (or  
later) ICSU have been successfully tested using appropriate maintenance  
procedures. The DS1 span test consists of 2 sequential parts. Each part provides  
a result indicating if there is a problem in the CPE wiring. CPE wiring may be  
considered problem-free only if the results of both parts are successful.  
The first part of the span test powers-up the loopback jack and attempts to send  
a simple code from the DS1 board, through the wiring and loopback jack, and  
back to the DS1 board. Maintenance software waits about 10 seconds for the  
loopback jack to loop, sends the indication of the test results to the management  
terminal, and proceeds to the second part of the test.  
The second part of the test sends the standard DS1 3-in-24 stress testing pattern  
from the DS1 board, through the loopback jack, and back to a bit error detector  
and counter on the DS1 board. The bit error rate counter may be examined at will  
via the management terminal, and provides the results of the second part of the  
test. The test remains in this state until it is terminated so that the CPE wiring may  
be bit error rate tested for as long as desired.  
1. Busy out the DS1 circuit pack by entering busyout board UUCCSS  
(where UUCCSS is the cabinet, carrier, and slot number of the DS1  
board).  
2. At the management terminal, enter change ds1 <location> and verify the  
near-end csu typeis set to integrated.  
3. Change to page 2 of the DS1 administration form and confirm that the TX  
LBO field is 0dB. If not, record the current value and change it to 0dB for  
testing. Press Enter to implement the changes or press Cancel to change  
nothing.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-74  
4. Enter test ds1-loop <location> cpe-loopback-jack. This turns on simplex  
power to the loopback jack and waits about 20 seconds for any active  
DS1 facility alarms to clear. A “PASS” or “FAIL” displays on the terminal.  
This is the first of the 2 results. A “FAIL” indicates a fault is present in the  
wiring between the ICSU and the loopback jack. The loopback jack may  
also be faulty. A “PASS” only indicates that the loopback jack looped  
successfully, not that the test data contains no errors. If a “PASS” is  
obtained, continue with the following steps.  
NOTE:  
The loss of signal (LOS) alarm (demand test #138) is not processed  
during this test while the 3-in-24 pattern is active.  
5. Enter clear meas ds1 loop <location> to clear the bit error count.  
6. Enter clear meas ds1 log <location> to clear the performance  
measurement counts.  
7. Enter clear meas ds1 esf <location> to clear the ESF error count.  
8. Enter list meas ds1 sum <location> to display the bit error count. Refer  
to Table 1-7 for troubleshooting information.  
Table 1-7. DS1 Span Troubleshooting  
Displayed  
Field  
Function  
Indication  
Test: cpe-  
Pattern 3-in-24 The loopback jack test is active.  
loopback-jack  
Synchronized  
Y or N  
If “y” displays, the DS1 circuit pack has  
synchronized to the looped 3-in-24 pattern and is  
accumulating a count of the bit errors detected in  
the pattern until the test has ended. If ndisplays,  
retry the test 5 times by ending the test per Step  
11 and re-starting the test per Step 4. If the circuit  
pack never synchronizes, substantial bit errors in  
the 3-in-24 pattern are likely. This could be  
intermittent connections or a broken wire in a  
receive or transmit pair in the CPE wiring.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-75  
Table 1-7. DS1 Span Troubleshooting — Continued  
Displayed  
Field  
Function  
Indication  
Bit Error Count  
Cumulative  
count of  
detected  
errors  
If there are no wiring problems, the counter  
remains at 0.  
A count that pegs at 65535 or continues to  
increment by several hundred to several  
thousand on each list meas command execution  
indicates intermittent or corroded connections,  
severe crosstalk, or impedance imbalances  
between the two conductors of the receive pair or  
the transmit pair. Wiring may need replacement.  
Note that “ESF error events” counter and the ESF  
performance counter summaries (“errored  
seconds”, “bursty errored seconds”, and so forth)  
will also increment. These counters are not used  
with the loopback jack tests. However, they will  
increment if errors are occurring. Counters should  
be cleared following the test.  
9. Repeat Steps 5 through 8 as desired to observe bit error rate  
characteristics. Also, wait 1 to 10 minutes between Steps 5 through 7. One  
minute without errors translates to better than a 1 in 10 to the eighth error  
rate. Ten minutes without errors translates to better than a 1 in 10 to the  
ninth error rate.  
10. If the test runs for 1 minute with an error count of 0, confirm that the 3-in-24  
pattern error detector is operating properly by entering test ds1-loop  
<location> inject-single-bit-error. This causes the 3-in-24 pattern  
generator on the DS1 circuit pack to inject a single-bit error into the  
transmit pattern. A subsequent list meas ds1 summary <location>  
command displays the bit error count. If a count greater than 1 is  
displayed, replace the ICSU and retest. If the problem continues, replace  
the DS1 circuit pack.  
11. Terminate the test by entering test ds1-loop <location> end  
cpe-loopback-jack-test. Wait about 30 seconds for the DS1 to re-frame  
on the incoming signal and clear DS1 facility alarms.  
Loopback termination fails under the following conditions:  
a. The span is still looped somewhere. This could be at the loopback  
jack, at the ICSU, or somewhere in the network. This state is  
indicated by a fail code of 1313. If the red LED on the loopback  
jack is on, replace the ICSU. Re-run the test and verify that the  
loopback test terminates properly. If not, replace the DS1 circuit  
pack and repeat the test.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-76  
b. The DS1 cannot frame on the incoming span’s signal after the  
loopback jack is powered down. This means that there is  
something wrong with the receive signal into the loopback jack from  
the “dumb” block or the Smart Jack. If the service provider  
successfully looped and tested the span, up to the Smart Jack, this  
condition isolates the problem to the wiring between the loopback  
jack and the Smart Jack. Refer to ‘‘Loopback Jack Fault Isolation  
Procedures’’ for information on how to proceed in this case. The  
test cannot be successfully terminated until a good signal is  
received. To properly terminate the test before a good receive  
signal is available, enter reset board <location>.  
12. Restore the TX LBOfield to the original value recorded in Step 2.  
13. Release the DS1 circuit pack using the release board PCSSpp  
command.  
14. Leave the loopback jack connected to the DS1 span.  
Loopback Jack Fault Isolation Procedures  
This section describes the possible DS1 configurations in which the loopback  
jack may be used. These configurations are: when the DS1 provider includes a  
Smart Jack, when no Smart Jack is provided at all, and when sites use fiber  
multiplexers.  
Configurations Using a Smart Jack  
The addition of the loopback jack and the presence of a Smart Jack divides the  
DS1 span into 3 separate sections for fault isolation. These sections are shown in  
Figure 1-21 through Figure 1-23 for the different span configurations. They are:  
Section 1:  
Section 2:  
Between the 120A2 (or later) ICSU and the loopback jack.  
Between the loopback jack and the Smart Jack (network  
interface point).  
Section 3:  
From the Smart Jack to the CO. It is necessary to contact  
the DS1 provider to run this test.  
A problem can exist in 1 or more of the 3 sections. The field technician is  
responsible for finding and correcting problems in the first 2 sections. The DS1  
service provider is responsible for finding and correcting problems in the third  
section. Testing is divided into 3 steps.  
■
Test customer premises wiring (section 1 in the following 3 figures) from  
the ICSU to the loopback jack as described in “DS1 Span Test.”  
■
Test the CO-to-network interface wiring (section 3 in Figure 1-21) using the  
Smart Jack loopback (CO responsibility). Coordinate this test with the DS1  
provider.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-77  
■
Test the short length of customer premises wiring (section 2 in the  
following 3 figures) between the loopback jack and the Smart Jack. This  
can be done using a loopback that “overlaps” section 2 of the cable. Any  
of the following loopbacks can do this:  
a. The local ICSUs line loopback, which is typically activated, tested,  
and then deactivated by the DS1 service provider at the CO end.  
b. The local DS1 interface’s payload loopback, activated and tested  
by the DS1 service provider at the CO end.  
c. The far-end ICSU’s line loopback. This test is activated at the  
management terminal by entering test ds1-loop <location>  
far-csu-loopback-test-begin. The test is terminated by entering  
test ds1-loop <location> end-loopback/span-test. Bit error  
counts are examined as described in “DS1 Span Test.” This test  
method is the least preferable because it covers wiring that is not in  
the local portion of the span. This test only isolates problems to  
section 2 wiring if there are no problems in the wiring between the  
far-end CO and the far-end ICSU. Coordinate this test with the DS1  
service provider.  
If any of the above tests (a, b, or c) fail, a problem is indicated in section 2  
as long as the tests for section 1 and section 3 pass. Since section 2  
includes the network interface point, it is necessary to work with the  
service provider to isolate the fault to the loopback jack cable, the “dumb”  
block, or the Smart Jack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-78  
Figure Notes:  
1. Span Section 1  
2. Span Section 2  
3. Span Section 3  
5. RJ-48 to Network Interface (Up to 1000  
Feet) (305 m)  
6. Loopback Jack  
7. Network Interface Smart Jack  
8. Interface Termination or Fiber MUX  
9. Central Office  
4. 120A2 (or later) Integrated  
Channel Service Unit (ICSU)  
Figure 1-21. Network Interface at Smart Jack  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-79  
Figure Notes:  
1. Span Section 1  
2. Span Section 2  
3. Span Section 3  
6. Loopback Jack  
7. “Dumb” Block (Extended Demarcation)  
8. Network Interface Smart Jack  
9. Interface Termination or Fiber MUX  
10. Central Office  
4. 120A2 (or later) Integrated  
Channel Service Unit (ICSU)  
5. RJ-48 to Network Interface  
(Up to 1000 Feet) (305 m)  
Figure 1-22. Network Interface at Extended Demarcation Point (Smart Jack  
Inaccessible)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-80  
Figure Notes:  
1. Span Section 1  
2. Span Section 2  
3. Span Section 3  
6. “Dumb” Block (Extended Demarcation)  
7. Loopback Jack  
8. Network Interface Smart Jack  
9. Interface Termination or Fiber MUX  
10. Central Office  
4. 120A2 (or later) Integrated  
Channel Service Unit (ICSU)  
5. RJ-48 to Network Interface  
(Up to 1000 Feet) (305 m)  
11. “Dumb” Block to Smart Jack RJ-48  
Figure 1-23. Network Interface at Extended Demarcation Point (Smart Jack  
Accessible)  
Configurations Without a Smart Jack  
When the loopback jack is added to a span that does not contain a Smart Jack,  
the span is divided into 2 sections. See Figure 1-24 and Figure 1-25.  
1. ICSU to the loopback jack.  
2. Loopback jack to the Central Office (CO).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-81  
Figure Notes:  
1. Span Section 1  
2. Span Section 2  
5. Loopback Jack  
6. “Dumb” Block (Demarcation Point)  
7. Interface Termination or Fiber MUX  
8. Central Office  
3. 120A2 (or later) Integrated  
Channel Service Unit (ICSU)  
4. RJ-48 to Network Interface  
(Up to 1000 Feet) (305 m)  
Figure 1-24. Network Interface at “Dumb” Block  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-82  
Figure Notes:  
1. Span Section 1  
2. Span Section 2  
5. Loopback Jack  
6. “Dumb” Block (Demarcation Point)  
7. Repeater  
3. 120A2 (or later) Integrated  
Channel Service Unit (ICSU)  
8. Fiber MUX  
4. RJ-48 to Network Interface  
(Up to 1000 Feet) (305 m)  
9. Central Office  
Figure 1-25. Network Interface at “Dumb” Block with Repeater Line to Fiber  
MUX  
Section 2 includes the short cable from the loopback jack to the “dumb” block  
demarcation point (part of the loopback jack). This is the only portion o f section  
2 that is part of customer premises wiring but is not covered in the loopback  
jack’s loopback path.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Install DS1 CPE Loopback Jack (T1 Only)  
1-83  
A problem can exist in 1 or both of the 2 sections. The field technician is  
responsible for finding and correcting problems in section 1 and the loopback  
cable portion of section 2. The DS1 service provider is responsible for finding  
and correcting problems in the majority of section 2. Testing is divided into 2  
steps.  
1. Test customer premises wiring (section 1 in Figure 1-24) from the ICSU to  
the loopback jack as described in the “DS1 Span Test” section.  
2. Test the loopback jack-to-”dumb” block and ”dumb” block-to-CO wiring  
(section 2 in Figure 1-24). This can be done using a loopback that  
“overlaps” the section of the span. Any of the following loopbacks can do  
this:  
a. The local ICSUs line loopback, which is typically activated, tested,  
and then deactivated by the DS1 service provider at the CO end.  
b. The local DS1 interface’s payload loopback, activated and tested  
by the DS1 service provider at the CO end.  
c. The far-end ICSU’s line loopback. This test is activated at the  
management terminal by entering test ds1-loop <location>  
far-csu-loopback-test-begin. The test is terminated by entering  
test ds1-loop <location> end-loopback/span-test. Bit error  
counts are examined as described in the “DS1 Span Test” section.  
This test only isolates problems to section 2 wiring if there are no  
problems in the wiring between the far-end CO and the far-end  
ICSU. Coordinate this test with the DS1 service provider.  
If any of the above tests (a, b, or c) fail, a problem is indicated in  
section 2. This could mean bad loopback jack -to-”dumb” block  
cabling, but is more likely to indicate a problem somewhere  
between the “dumb” block and the CO. This is the responsibility of  
the DS1 service provider. If the DS1 Span Test confirms that there  
are no problems in section 1, the technician should proceed as  
follows to avoid unnecessary dispatch.  
■
Identify and contact the DS1 service provider  
■
Inform the DS1 provider that loopback tests of the CPE  
wiring to the “dumb” block (section 1) showed no problems  
■
■
If the far-end ICSU line loopback test failed, inform the DS1  
provider  
Request that the DS1 provider perform a loopback test of  
their portion of the section 2 wiring by sending someone out  
to loop section 2 back to the CO at the “dumb” block.  
If this test fails, the problem is in the service provider’s  
wiring.  
If the test passes, the problem is in the cable between the  
loopback jack and the “dumb” block. Replace the loopback  
jack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
LED Interpretation  
1
1-84  
Configurations Using Fiber Multiplexers  
Use the loopback jack when customer premises DS1 wiring connects to an  
on-site fiber multiplexer (MUX) and allows wiring to the network interface point on  
the MUX to be remotely tested. This requires that ICSUs be used on DS1 wiring  
to the MUX.  
Fiber MUXes can take the place of Interface termination feeds as shown in  
Figure 1-21, Figure 1-22, Figure 1-23, and Figure 1-24. Test these spans using  
the same procedures as metallic spans. Note the following points:  
1. Fiber MUXes may have loopback capabilities that can be activated by the  
service provider from the CO end. These may loop the signal back to the  
CO or back to the DS1 board. If the MUX provides the equivalent of a line  
loopback on the “problem” DS1 facility, this may be activated following a  
successful loopback jack test and used to isolate problems to the wiring  
between the loopback jack and the MUX.  
2. Be aware that there are installations that use repeatered metallic lines  
between the MUX and the “dumb” block. Theses lines require DC power  
for the repeaters and this DC power is present at the “dumb” block  
interface to the CPE equipment. A loopback jack is required in this  
configuration to properly isolate and terminate the DC power.  
To check for the presence of DC, make the following 4 measurements at the  
network interface jack:  
1. From Transmit Tip (T, Pin 5) to Receive Tip (T1, Pin 2)  
2. From Transmit Ring (R, Pin 4) to Receive Ring (R1, Pin 4)  
3. From Transmit Tip (T, Pin 5) to Transmit Ring (R, Pin 4)  
4. From Receive Tip (T1, Pin 2) to Receive Ring (R1, Pin 4)  
All measurements should read 0 (zero) volts DC. For pin numbers and pin  
designations, refer to Integrated Channel Service Unit (ICSU) Installation and  
Operation, 555-230-193.  
LED Interpretation  
The lighting and unlighting of LEDs indicates to the system user the status of  
various maintenance components in the system. LEDS are located on the  
attendant console, on all circuit packs in the switch cabinets and, optionally, on  
customer-designated voice terminals. The following LEDS are included in the  
system:  
■
‘‘TN798 Processor Circuit Pack LEDs’’  
‘‘Attendant Console LEDs’’  
■
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
LED Interpretation  
1
1-85  
■
■
‘‘Control and Port Circuit Pack Status LEDs’’  
‘‘Power Supply LEDs’’  
Terminal Alarm Notification  
Terminal Alarm Notification is an optional feature which displays several types of  
alarms on voice terminals with administered feature buttons or the attendant  
console. A maximum of ten digital and/or hybrid voice terminals may be used.  
When an alarm occurs, the green status LED associated with the assigned  
button will be in a steady state. The lamp may be turned off by pressing the  
button associated with the lighted alarm lamp. If the lamp is turned off, and the  
alarm has not been resolved by the time maintenance reschedules testing, the  
green status LED will resume its steady state. The following alarms are  
displayed:  
ac-alarm  
Administered Connection Alarm: a locally administered  
connection (ADM-CONN) has a Major, Minor, or Warning  
alarm active.  
pr-awu-alm  
off-bd-alarm  
Auto Wakeup Journal Printer Alarm: the automatic wakeup  
journal printer has a Major, Minor, or Warning alarm active.  
DS1 or ATM Facility Alarm: an off-board Major, Minor, or  
Warning alarm is active on a DS1-BD, UDS1-BD, or  
ATM-TRK board.  
trk-ac-alm  
Facility Access Alarm: The facility access trunk test feature  
is activated.  
major-alrm  
mj/mn-alrm  
Major Alarm: The system has logged a Major Alarm.  
Major/Minor Alarm: The system has logged a Major or Minor  
Alarm.  
pr-pms-alm  
PMS Printer: The Property Management System printer has  
a Major, Minor, or Warning alarm active.  
rs-alert  
Reset-Alert: reset system 2 or 3 has been performed.  
cdr1-alrm  
Call Detail Recording Alarm: The Primary CDR Link has a  
Major, Minor, or Warning alarm active.  
cdr2-alrm  
pr-sys-alm  
pms-alarm  
Call Detail Recording Alarm: The Secondary Link has a  
Major, Minor, or Warning alarm active.  
System Printer Alarm: The System Printer (SYS-PRNT) has a  
Major, Minor, or Warning alarm active.  
The Property Management System has a Major, Minor or  
Warning alarm active.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
LED Interpretation  
1
1-86  
TN798 Processor Circuit Pack LEDs  
The front panels of the Processor circuit pack and the Maintenance circuit pack  
are identical. Each has two groups of LEDs. One group indicates the status of the  
pack, and the other group (which includes the Major, Minor, and Warning alarms  
described in the ‘‘Alarm and Error Reporting’’ section) reflects maintenance  
conditions in the entire system. See Figure 1-26.  
■
Red (alarm)—the system has detected a fault in this circuit pack.  
NOTE:  
Alarms on the PROCR, PR-MAINT, MEMORY, and PR-MEM MOs are  
indicated by the red LED on the Processor circuit pack.  
■
■
■
■
■
Green (test)—the system is running tests on this circuit pack.  
Yellow (b usy)—this circuit pack is in use.  
MAJOR ALARMS (red)  
MINOR ALARMS (red)  
EMERGENCY TRANSFER (red)—indicates emergency transfer has been  
invoked  
NOTE:  
If the AC power cord is unplugged, the emergency transfer feature  
invokes, however the EMERGENCY TRANSFER LED (red) is not lit  
due to loss of AC power.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
LED Interpretation  
1
1-87  
Alarm (Red  
Test (Green)  
Busy (Amber)  
Major alarms (Red)  
Minor alarms (Red)  
MAJ  
MIN  
Emergency transfer  
control switch  
Memory  
card slot  
ckdmt798 RPY 072297  
Figure 1-26. LED Indicators on the TN798 Processor Circuit Pack  
NOTE:  
If the LED just above the Memory Card Slot is alternating red and amber,  
this indicates both card in use and emergency transfer.  
Attendant Console LEDs  
The console has two red LEDs, labeled ALM and ACK, on the left side of the dial.  
The left LED lights steadily when there is a Major or Minor alarm at the switch  
cabinet. The right LED lights steadily if the alarm has been successfully reported  
to INADS. If the system is unable to report the alarm to INADS, the LED flashes;  
signaling the attendant to call INADS and report the alarm.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
LED Interpretation  
1
1-88  
Control and Port Circuit Pack Status LEDs  
Each circuit pack has three LEDs on the front panel visible at the front of the  
carrier. On all circuit packs, except the 650A Power Unit, the LEDs indicate:  
1. Red (alarm) — If the circuit pack is communicating with the system, the  
system has detected a fault in this circuit pack. An on-board alarm for this  
circuit pack is displayed in the Alarm Log.  
The circuit pack also lights this LED when either the circuit pack has not  
yet initialized communication with the system or when the circuit pack  
loses contact with the system and stops functioning (circuit pack is said to  
be “in reset”). In these cases, there may not be an alarm in the Alarm Log.  
To determine if the red LED is lit because the circuit pack is not in contact  
with the system, issue the list configuration board PCSS command,  
where PCSS refers to the slot containing this circuit pack. If the system  
does not detect the circuit pack, this command returns Identifier not  
assignedor no board.  
If the circuit pack has just been inserted, the system may still be initializing  
the circuit pack. If, after 5 minutes, the circuit pack still has not initialized  
communications with the system, check the MO for any special  
instructions (for example, EPN Maintenance circuit pack can stop  
EXP-INTF circuit pack from initializing). If the MO does not provide the  
needed information, perform the following steps:  
■
Check the Error Log for TONE-BD and TDM-BUS errors. Enter test  
tdm P where P is the port network containing the relevant slot.  
Refer to ‘‘Restarting Nonfunctioning Port Circuit Packs’’ in the  
general description of the ‘‘TDM-BUS (TDM Bus)’’. Enter test  
tone-clock PC, where P is the network containing the relevant slot,  
and C is the carrier containing the relevant slot. Follow appropriate  
sections for any TONE-BD and TDM-BUS errors.  
■
Reseat the suspect circuit pack.  
!
WARNING:  
Reseating some circuit packs may be very destructive (for example,  
Control Carrier circuit packs.)  
Wait 5 minutes. Then issue the list configuration board PCSS  
command. If the result indicates that the system still has not  
registered the circuit pack, go to next step.  
■
■
Try to insert the circuit pack into a different slot and try to insert a  
different circuit pack into the suspect slot (provided the  
maintenance documentation for this circuit pack does not warn  
against either of these actions).  
If the system seems to be functioning correctly, but the circuit pack  
does not start communicating with the system, replace the circuit  
pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
LED Interpretation  
1
1-89  
2. Green (test)—the system is running tests on this circuit pack.  
3. Yellow (busy)—indicates that the circuit pack is in use.  
NOTE:  
A port circuit pack also lights its red LED when it performs  
initialization tests (for example, when the circuit pack is initially  
inserted into the system). If all initialization tests pass, the red LED is  
turned off. If any initialization tests fail, the red LED remains lighted  
and the circuit pack is not placed into service.  
During the various states of operation (start-up testing, normal operation,  
circuit failure, and so forth) circuit pack status LED indications appear as  
shown in Table 1-8.  
Table 1-8. Control and Port Circuit Pack Status LEDs  
Equipment  
Type  
LED  
Description  
Port Circuit  
Packs  
Red  
On briefly during power up, circuit pack reseating,  
resetting, and system reset. Steadily on if circuit  
pack fails start-up test or fails while in use. Off  
during normal operation.  
Green  
Briefly on during circuit pack testing following  
power up, circuit pack reseating, and system  
reset. On during periodic, scheduled, and system  
technician demanded testing. Off during normal  
operation.  
Yellow  
Red  
On when any port in the circuit pack is in use,  
otherwise, off.  
Control Circuit  
Packs  
On briefly during power up and system reset.  
Steadily on if circuit pack fails start-up test or fails  
while in use. Off during normal operation.  
Green  
Yellow  
On briefly during board testing following power up  
and system reset. Also on during periodic,  
scheduled, and system technician-demanded  
testing. Off during normal operation.  
Processor  
■ Lit during processor initialization.  
■ Lit during system initialization (stays lit until  
Emergency Transfer is turned off).  
Tone Detector/Generator  
■ Slow blinking when clock is in use; otherwise,  
off.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Multimedia Call Handling  
1
1-90  
Power Supply LEDs  
Table 1-9 shows the LED and alarm conditions for the 650A Power Supply. Ring  
voltage and neon bus output do not activate alarm status.  
Table 1-9. LED and Alarm Conditions  
Condition  
LED Status  
Alarm State  
Fan Alarm  
Normal  
Red off;  
Open  
Normal  
Yellow on  
No input power  
Red off;  
Yellow off  
Closed  
Closed  
Closed  
No input power  
DC output not present  
(except Neon)  
Red on;  
Yellow off  
DC output not present  
(except Neon)  
Fan alarm  
Red on;  
Fan alarm  
Yellow on  
Multimedia Call Handling  
■
‘‘Expansion Services Module’’  
‘‘Troubleshooting MMCH’’  
■
Expansion Services Module  
The Expansion Services Module (ESM) shown in Figure 1-27 provides T.120 data  
sharing capability on a MMCH multipoint H.320 video conference. Each  
conference participant must have endpoints administered and a personal  
computer with the H.320 video application installed. The DEFINITY ECS must  
have the expansion service module installed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Multimedia Call Handling  
1
1-91  
6
2
1
3
7
5
4
cydf012 RPY 100697  
Figure Notes  
1. Port B Y-cable connector to a TN787  
Multimedia Interface (MMI) circuit pack  
5. D8W cord connected to 356A  
adapter port 1  
2. Port A Y-cable connector to a TN2207 PRI  
circuit pack  
6. Expansion Service Module (ESM)  
7. Port B on compatible primary rate  
interface (PRI) card  
3. 25-pair Y-cable  
4. 356A adapter  
Figure 1-27. Typical ESM connections  
!
CAUTION:  
The TN2207 circuit pack is the only pack allowing connection of an ESM to  
the DEFINITY ECS switch.  
Troubleshooting MMCH  
■
■
■
■
■
■
■
■
■
■
■
‘‘64 Kbps Calls Terminate but Far End Receives 56 Kbps Indication’’  
‘‘Calls Terminate with No Audio’’  
‘‘Some Parties Cannot Be Heard by Others (Audio Subsetting)’’  
‘‘Calls Terminate with No Video’’  
‘‘Calls Terminate Correctly but Are Unstable’’  
‘‘Synchronization’’  
‘‘Voice-Activated Switching Problems’’  
‘‘No Switching, Full Motion Video’’  
‘‘Video Never Switches to a Particular Party’’  
‘‘Audio Echo’’  
‘‘Endpoint or I-MUX in Loopback Mode’’  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Multimedia Call Handling  
1
1-92  
Before troubleshooting any problems associated with the DEFINITY MMCH,  
always be sure that the endpoint is operating correctly (audio, video, and data)  
by making point-to-point test calls. If possible, make the test calls over the  
network to test the connectivity and routing of network calls from the endpoint.  
This eliminates problems such as disconnected audio or video cables and  
network troubles.  
64 Kbps Calls Terminate but Far End Receives  
56 Kbps Indication  
Description  
Some 2x64 Kbps conferences on the DEFINITY MMCH do not establish because  
of framing, audio, or video problems.  
For calls that are routed in the network through a Lucent Technologies/LEC  
interface, the originating equipment may launch a 64 Kbps call attempt, and the  
far end receives either a 56 Kbps or 64 Kbps indication. If the far end receives a  
64 Kbps indication, the call may have used 56 Kbps facilities. If so, the call may  
exhibit any of the following conditions:  
■
■
■
No handshaking in one direction or both (call disconnects after timeouts)  
Call connects, but audio or video is corrupted (audio noise or no video)  
Call succeeds without disruption (this is the least likely since one endpoint  
must be aware that the call is really 56 Kbps to connect)  
If any of the above conditions occur, then 64 Kbps calls from the site are  
blocked.  
Solution  
Administer the conference for connection at 56 Kbps.  
Calls Terminate with No Audio  
Description  
To support endpoints that do not support Multipoint Command Conference  
(MCC), the DEFINITY MMCH changes its capability set and initiates a capability  
set exchange with the endpoint when the Selected Communications Mode (SCM)  
changes. If the endpoint does not follow the SCM audio mode, the MCU may  
include the endpoint as a secondary (audio only) endpoint. If the endpoint sends  
an unknown or unsupported audio mode, then the TN788B decoder port mutes  
the endpoint from the conference. The user may hear the conference but may not  
be heard by other parties in the conference.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Multimedia Call Handling  
1
1-93  
Solution  
1. Use the Status Conference x form and check the Audio Mode field for the  
current operating mode of the conference.  
2. Another indication of the audio modes is in the “Incoming Mode  
Commands from Endpoint and Outgoing Commands from MMI” on page  
3 of the Status Conference x Endpoint y form. Check the Audiofields  
under the Mode Commands/Communication Modes section of the form.  
Some Parties Cannot Be Heard by Others (Audio  
Subsetting)  
Description  
Problems where varying subsets of the conference hear different things may  
have problems with the various summing resources/groups that are in use.  
Traditionally theses faults are caused by the SPE not cleaning up the connections  
properly. Isolation and diagnosis should focus on the VC resources in use by that  
conference.  
Solution  
1. Use the status conference command to list the VC resources in use by  
this conference. Try a hot replacement of any VC boards in use, which  
refreshes the VC translations and move all of the audio connections to  
different VC ports.  
2. If the problem still exists, try dropping the conference and then bringing  
the conference back up again. Not only does this refresh VC translations,  
but uses different timeslots as well.  
3. If the problem still exists, suspect a hardware problem. If practical, wait for  
the DEFINITY MMCH to be idle (no active conferences), and then check  
the circuit packs for active (yellow) LEDs. If any of these are unexpected,  
such as on a VC board, try replacing the board and then bringing the  
conference up again.  
Calls Terminate with No Video  
Description  
Generally, loss of video can be divided into 2 types. The first occurs when the  
DEFINITY MMCH switches to the endpoint, but nobody sees them. The receivers  
see either “black” video or a frozen image of the previous speaker depending on  
the codec of the manufacturer. The type occurs when the DEFINITY MMCH does  
not switch to an endpoint.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Multimedia Call Handling  
1
1-94  
Solution  
In the first type described above, wiring problems, power to the camera, or video  
encoder circuit pack problems in the codec are typical causes.  
In the second type, no video from an endpoint typically occurs because it is not a  
valid video source. This can be checked by looking at page 1 of the Status  
Conference x Endpoint y Vid form under the Capability section. In this section, a  
“y” or “c” suggests that the endpoint has video. An “e” means ept has not  
declared any video capability in cap set, “n” is audio only, and “blank” means  
audio add-on.  
Also check page 1 of the Status Conference x Endpoint y Vs form for indication of  
the video state for the endpoint values.  
Calls Terminate Correctly but Are Unstable  
Description  
A number of conditions will lead to some or all endpoints having stability  
problems during the course of a conference. A lack of stability from an endpoint  
is noticeable by a lack of a video switching while the party is the only talker or  
excessive disconnects from that endpoint.  
Synchronization  
Generally, the most common problem is a mismatch in synchronization sources  
between the endpoint and the DEFINITY MMCH. This typically causes low-level  
(Px64) handshake problems that can trigger the endpoint/MMCH to disconnect  
the call. The MCCH’s timers are set to sufficiently high values so that, normally,  
the endpoint will timeout and disconnect first. If installed in a customer network, it  
is a good idea to perform an audit of the path synchronization is being supplied.  
If there are different clock sources between endpoints and the DEFINITY MMCH,  
some problems are sure to occur. The severity of these problems can range from  
a handshake failure every few seconds to one per day. Depending on the type of  
endpoint, this can cause the endpoint to disconnect or just freeze video until the  
main problem is resolved.  
Specifically, PictureTel System 4000 endpoints seem to be the most sensitive to  
instability. The Lucent Technologies Vistium also disconnects fairly infrequently.  
Last, the CLI Rembrandt II VP freezes video and waits for framing to be  
recovered.  
Network Configuration Concerns with Synchronization  
When auditing a network for synchronization, avoid unnecessary hops. Thus, a  
switch providing star-configuration synchronization is preferred over a  
daisy-chain configuration. Additionally, if there are DEFINITY PBXs that have  
EPNs, synchronization should be provided to sub nodes from the same port  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Multimedia Call Handling  
1
1-95  
network through which the PBX receives its synchronization. Passing  
synchronization through the PBX Expansion Interface adds an unnecessary hop  
to the path and creates another potential point of failure.  
Expansion Interface Duplication  
If a customer’s network uses PBX EPNs with duplicated Expansion Interfaces,  
scheduled switching of the Expansion Interface links should be disabled on the  
PBX via change system-parameters maintenance. When scheduled  
maintenance runs and switches the links, there is a brief corruption of the data  
path. If endpoints have active calls when the switch occurs, this corruption of the  
data path causes Px64 handshake problems, which lead to the endpoints losing  
video source status, and sometimes disconnecting as described above.  
Disabling the EI switching is in the customer’s best interest to prevent the  
disruption of the Px64 data stream. The customer will get the same level of alarm  
indications and maintenance on the EI links, regardless of the status of  
scheduled switching.  
PRI D-Channel Backup  
A somewhat unlikely source of call stability problems occur where the  
translations for PRI D-channel Backup between two non-MCU switches were  
incorrect. As an example, on switch A, DS1 1A10 was designated as the primary  
source, and on switch B, the corresponding DS1 was designated as the  
secondary source. When scheduled maintenance was run on the switch that had  
an active standby D-channel, an audit disconnected some calls using the link.  
The problem was corrected when the D-channel primary/secondary assignments  
matched.  
Processor Duplication on the PBX  
Do not enable the PI link switch on scheduled maintenance. This can cause link  
stability problems on the Accunet Bandwidth Controller (ABC).  
Voice-Activated Switching Problems  
Voice-activated switching on the DEFINITY MMCH does not follow the loudest  
talker. The MMCH queues all speaking parties and selects a new video  
broadcaster (the second-oldest speaking party) when the oldest speaking party  
has stopped talking. The new broadcaster will see the last speaker as its video.  
The system can also “learn” about the noise coming from an endpoint to help  
prevent false switches, adapting both to noise level and repetitive sounds such  
as a fan. This adaptation occurs over approximately 10 seconds.  
No Switching, Full Motion Video  
If a room is excessively noisy, the DEFINITY MMCH may receive sufficient audio  
signal to conclude that there is a speaker present. Use the Status Conference x  
form to determine if the MMCH thinks an endpoint is talking. The MMCH sets the  
Tsfield to tfor each endpoint if there is voice energy detected. This endpoint  
may have to mute when nobody at the site is speaking to allow the conference to  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Multimedia Call Handling  
1
1-96  
proceed normally. Remind the customer that it may be necessary to mute if a  
side conversation is going on in the background, just as one would do in an  
audio conference. If the system does not switch broadcasters even after the  
current broadcaster has muted, check the conference administration using the  
display conference X command to ensure that the conference is in  
voice-activated mode. Also verify that parties who were speaking are valid video  
sources as described in the “Calls Terminate with No Video” section above.  
The See-Me feature (MCV) can also cause VAS to “lock-up.” An endpoint can  
activate MCV to force their site to become the broadcaster. If they do not disable  
the feature when finished, the system remains in this mode indefinitely. Beginning  
with Release 3.0, the status conference X command shows that MCV is in effect  
by displaying avin the Video Status (Vs) column. Page 3 of the Status  
Conference X Endpoint Y form also has a Broadcasterfield that indicates MCV  
is in effect with (SEE-ME) as the broadcaster. The same scenario can occur in a  
CHAIR or UCC-controlled conference with a designated broadcaster. In this  
situation the CHAIR/UCC has not released the designated broadcaster and  
returned to VAS mode. If there is a UCC-designated broadcaster, status  
conference X indicates a Video Status of u. Also, for UCC rollcall the return  
video may appear to be stuck. Check the Video Status for an “R,” indicating  
rollcall.  
If none of the examples above appears to be the cause, and if the room was  
quiet, all speakers are valid video sources, the conference is voice-activated,  
and the speaker can be heard, then escalate the problem.  
Video Never Switches to a Particular Party  
Description  
Verify that the endpoint is a valid video source as described in the “Calls  
Terminate with No Video” section above. If it is, then the audio from the endpoint  
may not have sufficient voice signal for the hardware to determine the parties at  
the endpoint are speaking. Check the Talkfield on page three of the Status  
Conference X Endpoint Y form to see if the talking bitis y. Next, check the  
audio by standing adjacent to the microphone and speaking at a normal level.  
Solution  
If the audio is not muffled:  
1. Use the status conference command to determine which port on the  
TN788B (VC board) is connected to this endpoint.  
2. Check the VC (TN788B) board using the test board xxyy long command.  
3. Drop the call.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Multimedia Call Handling  
1
1-97  
4. Find another available port, then:  
a. Busyout the port to which the endpoint was connected.  
b. Make another call to the same conference. If the problem corrects  
itself, then the previous port may be bad. If there are other VC  
boards with sufficient available ports to replace calls on the current  
VC, then pull the board that has the bad endpoint on it (the status  
conference command displays the encoder port associated with  
the call). The system will automatically reestablish the VC  
connections without dropping the call. If this fixes the problem, then  
replace the board, as it has at least one bad port. Reseating the  
board may temporarily fix the problem due to the hard reset done to  
the board.  
Audio Echo  
Echo in conference calls, particularly those with large delay characteristics, is  
totally disruptive. When Voice Activated Switching is taken into account, the  
effects are disastrous. Various arrangements of the microphone(s) and room  
speaker(s) may be needed.  
For some Lucent Technologies Vistium endpoints, if an external speaker is  
attached or was attached when the system was last rebooted, this endpoint will  
cause audio echo throughout the conference. First, isolate the offending  
endpoint by asking each endpoint to mute, one at a time, until the echo  
disappears.  
If the input from an endpoint is located too close to the speakers of an endpoint,  
then acoustic echo is created. The microphone must be moved away from the  
speakers.  
Normally, if any microphone in the room is moved relative to the speakers, that  
site will cause echo until the echo canceller in the codec retrains itself, some will  
require a manual reset. If a PictureTel keypad is configured with external  
microphones connected to the keypad, then the internal microphone and  
external microphone(s) “sing” to each other if the “ext mic” bat switch is set to  
“int mic” on the back of the keypad. In this configuration, VAS locked on that site,  
and the acoustic “singing” was inaudible.  
Rate Adaptation  
Because of a lack of a clear explanation in standards, sometimes endpoints do  
not work well with each other and the DEFINITY MMCH. The MMCH will only  
allow a conference to downgrade from 64kbps to 56 kbps operation on  
conferences that have the Rate Adaptationflag set to y.  
When a downgrade does occur, information on the Status Conference form  
indicates the success or failure of the 64kbps-endpoints that are participants to  
properly rate adapt to 56kbps. As a general indication that the conference has  
rate adapted,DtohwenlCoaodnfrfoemrWewnwc.SeomTarnuaanlss.cfome.rAllRMaantuealsaSnedarEchfAfnedcDtowinvloead.Transfer  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
TN760D Tie Trunk Option Settings  
1-98  
Ratefields show initial and current transfer rates, respectively. For each 64-kbps  
endpoint the column that indicates Rate Adaptshows an nif the endpoint did  
not follow the procedures as specified by the H.221. If an endpoint shows y, it did  
successfully rate adapt. If an endpoint shows c, it joined the conference at  
56kbps.  
Once the conference rate adapts, the endpoints that do not properly follow suit,  
will become audio-only endpoints. A conference will not rate adapt from 56 kbps  
back to 64 kbps until all endpoints disconnect from the conference and it idles.  
The PictureTel 1000 Release 1.1C, PictureTel 6.01 software, and the Vistium 2.0  
software successfully rate adapt with the MCU. External rate adaptation  
techniques used by VTEL and CLI are known to cause problems with the  
endpoint when used with this feature.  
Endpoint or I-MUX in Loopback Mode  
Some endpoints have a loopback enable feature. This makes DEFINITY MMCH  
data loopback at the MMCH when a connection is in progress. The loopback can  
be enabled prior to or during a connection.  
The MMCH does not detect the loop and continues to VAS. In most scenarios,  
the switch occurs, but within a few seconds, the broadcaster’s return video  
becomes its own image. Once the broadcaster stops speaking, the system  
“false” switches to an apparently random port that was not speaking.  
TN760D Tie Trunk Option Settings  
The TN760D Tie Trunk circuit pack interfaces between 4 tie trunks and the TDM  
bus. Two tip and ring pairs form a 4-wire analog transmission line. An E and M  
pair are DC signaling leads used for call setup. The E-lead receives signals from  
the tie trunk and the M-lead transmits signals to the tie trunk.  
To choose the preferred signaling format (Table 1-10 and Table 1-11), set the  
switches on the TN760D and administer the port using Figure 1-28 and Table  
1-12.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
TN760D Tie Trunk Option Settings  
1-99  
Table 1-10. Signaling Formats for TN760D  
Mode  
Type  
Type I Standard (unprotected)  
Type I Compatible (unprotected)  
Type I Compatible, Type I Standard  
Type V  
E & M  
E & M  
Protected  
Simplex  
E & M  
Type V  
E & M  
Type V Revised  
Table 1-11. Signaling Type Summary  
Transmit (M-Lead)  
On-Hook Off-Hook  
Receive (E-Lead)  
On-Hook Off-Hook  
ground  
Signaling Type  
Type I Standard  
Type I Compatible  
Type V  
1
ground  
battery  
ground  
ground  
open  
open /battery  
1
1
open /battery  
ground  
open  
open /battery  
1
open /battery  
ground  
open  
Type V Reversed  
ground  
ground  
1. An open circuit is preferred instead of battery voltage.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
TN760D Tie Trunk Option Settings  
1-100  
UNPROT  
SMPLX  
E&M  
SMPLX  
E&M  
SMPLX  
E&M  
SMPLX  
E&M  
4 3 2 1  
PROT  
PORT 1  
PORT 4  
PORT 3  
PORT 2  
r758183 RBP 050896  
Figure 1-28. TN760D Tie Trunk Circuit Pack (Component Side)  
Table 1-12. TN760D Option Switch Settings and Administration  
E&M/SMPLX  
Switch  
Prot/Unprot  
Switch  
Administered  
Port  
Installation Situation  
Preferred Signaling Format  
Circumstance  
To  
System  
Far-End  
Co-Located  
DEFINITY  
E&M Type 1  
Compatible  
E&M Type 1  
Standard  
E&M  
Unprotected  
Protected  
Type 1  
Compatible  
Type 1  
Inter-Building  
DEFINITY  
Protected  
Type 1  
Protected  
Type 1  
E&M  
Compatible  
Standard  
Plus  
Compatible  
Protection  
Unit  
Co-Located  
Net  
Integrated  
E&M Type 1  
Standard  
Any PBX  
E&M  
Unprotected  
Type 1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
TN464E/F Option Settings  
1
1-101  
TN464E/F Option Settings  
The TN464E/F DS1/E1 Interface - T1/E1 circuit pack interfaces between a 24- or  
32-channel Central Office/ISDN or tie trunk and the TDM bus.  
Set the switches on the circuit pack to select bit rate and impedance match. See  
Table 1-13 and Figure 1-29.  
Table 1-13. Option Switch Settings on TN464E/F  
120 Ohms  
75 Ohms  
Twisted pair  
Coaxial requiring 888B adapter  
32 Channel 2.048 Mbps  
24 Channel 1.544 Mbps  
10  
4
9
1
2
3
7
8
5
6
Figure Notes  
1. Backplane Connectors  
2. 24/32 Channel Selector  
3. 75/120 Ohm Selector  
4. Faceplate  
6. 120 Ohm (shown selected)  
7. 24 Channel (shown selected)  
8. 75 Ohm  
9. Connector  
5. 32 Channel  
10. TN464E/F  
Figure 1-29. TN464E/F Option Settings  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-102  
ATM Tips  
This section provides tips for DEFINITY ATM PNC when interfacing with the ATM  
switch. Throughout this section, refer to Figure 1-30, using TN2238 for R6.3  
systems, and TN230X for Release 7 and later.  
DEFINITY  
PPN  
DEFINITY  
EPN  
AX500  
ATM call control  
Q.93B  
Q.93B  
CaPro  
1
Switch  
processor  
Q.SAAL  
Q.SAAL  
ATM  
ATM  
Switch  
fabric  
SONET  
Physical  
SONET  
Physical  
Fiber  
Fiber  
TN2238  
TN2238  
Port boards  
iodftrb LJK 021398  
Figure 1-30. ATM troubleshooting schematic  
NOTE:  
The CaPro element (Note 1 in Figure 1-30) is a software module within the  
DEFINITY PPN.  
Initial LED inspection  
Visually inspect the LEDs on both the TN230X (Table 1-14) and the ATM switch  
(Table 1-15) for a high-level status of the system.  
Table 1-14. TN230X LED reference  
LED color  
Green  
Interpretation  
Red  
Off  
Yellow  
Steady on  
Off  
Off  
Normal state for active ATM EI board on PPN.  
Off  
Off  
Normal state for standby ATM EI board on PPN and  
EPN.  
Off  
Off  
2 sec on /  
2 sec off  
Normal state for active PNC archangel ATM EI board  
on EPN.  
Download from Www.Somanuals.com. All Manuals SearcCh AonndtDinouwendloaodn. next page  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-103  
Table 1-14. TN230X LED reference — Continued  
LED color  
Interpretation  
Red  
Green  
Yellow  
-
-
100ms on /  
100ms off  
Loss of signal on the OC-3 fiber. Either the  
TN230X-receive (top) or TN230X-transmit (bottom)  
fibers are not working.  
N/S  
Fast blink  
-
Running DSP diagnostics or downloading code to  
DSPs (typical during boot process).  
-
-
Slow blink  
Steady on  
-
-
Board insertion has not yet completed.  
Running maintenance tests. May appear to be blinking  
if several short tests are run one after another.  
Steady on  
-
-
Hardware alarm. Does not necessarily take the TN230X  
out of service, for example, if one of the 24 DSPs fails  
diagnostics.  
Table 1-15 shows the various LEDs on the A500 ATM switch and the meanings of  
the different states.  
Table 1-15. A500 LED Quick Reference  
Component  
Label  
Color  
State  
Meaning  
Switch  
LK  
Green Intermittent Normal state. Traffic is being sent or received  
Processor  
Board  
blink  
over the Ethernet LAN link.  
RX  
Green Steady on  
Normal state. Carrier is received over the  
Ethernet LAN link.  
DIAG  
NBOOT  
MGT  
Green Off  
Normal state.  
Normal state.  
Normal state.  
Green Off  
Green Off  
RUN  
Green Steady on  
Normal state. The switch processor is  
running.  
PWR  
Green Steady on  
Normal state. The switch processor board is  
powered up.  
VOLT  
TEMP  
FAN  
Yellow Off  
Yellow Off  
Yellow Off  
Normal state  
Normal state  
Normal state  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-104  
Table 1-15. A500 LED Quick Reference — Continued  
Component  
Label  
Color  
State  
Meaning  
SYSERR Yellow Off  
Normal state  
Normal state  
FAULT  
PWR  
Yellow Off  
Switch Fabric  
Board  
Green Steady on  
Normal state. The switch fabric board is  
powered up.  
FAULT  
PWR  
Yellow Off  
Normal state  
Port Board  
Green Steady on  
Yellow Off  
Normal state. The port board is powered up.  
Normal state  
FAULT  
RX  
Port Board  
Per Port  
Green Off  
No ATM cells are being received. This is not a  
normal state if the terminating port network is  
supposed to be up and running.  
RX  
Green Intermittent ATM cells are being received intermittently.  
blink  
This is a typical pattern for DEFINITY if only  
Variable Bit Rate (VBR) signaling connections  
are present but no talk paths are up, perhaps  
because no calls are in progress.  
RX  
CD  
CD  
Green Steady on  
Green Off  
ATM cells are being received frequently  
enough that the LED is lit constantly. This is a  
typical pattern for DEFINITY if Constant Bit  
Rate (CBR) talk paths are present.  
Loss of carrier on the fiber. The A500 detects  
only if the A500-receive (right-hand) fiber is  
not working. The state of the A500-transmit  
(left hand) fiber is not detected.  
Green Steady on  
Normal state. There is a optical carrier  
detected on the fiber from the TN230X.  
RPRD  
Yellow Off  
Normal state  
Power Supply  
AC OK  
DC OK  
Green Steady on  
Green Steady on  
Normal state. AC power is okay.  
Normal state. DC power is okay.  
Cajun A500 Diagnostics  
The first step in any diagnostic procedure involving the A500 is to identify the  
OC-3 ports on the A500 that have DEFINITY port networks attached.  
■
Be aware that customers may use other ports on the A500 for applications  
unrelated to DEFINITY (LAN traffic or multimedia applications, for  
examples).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-105  
■
These other applications may manifest themselves in the output of the  
troubleshooting commands you run on the A500. DEFINITY port networks  
must be identified by their A500 port numbers.  
NOTE:  
The following examples show DEFINITY port networks connected to A500  
ports A1.1 and A1.2.  
Has the A500 been installed and configured correctly?  
Diagnostics  
■
■
Is the A500 powered up?  
If you are administering the A500 through a locally-attached console, is  
there a local console terminal connected to the console port on the A500  
switch processor board with the correctly-pinned RS232 serial cable?  
■
If you are administering the A500 through telnet over the Ethernet, is there  
an 10BaseT Ethernet drop plugged into the Ethernet port on the A500  
switch processor board? (Note that a few A500 commands are only  
permitted over the local console terminal.)  
■
■
Has the A500 been booted using either the recessed reset button or by  
turning the power off, then on again?  
Did the A500 go through a normal power up sequence, including testing  
all of the LEDs?  
■
■
■
Are any A500 yellow fault LEDs lit?  
Are the remaining A500 LEDs in a normal state (Table 1-15 above)?  
Can you log into the A500 console using the diagnostic account root from  
the local console terminal or through telnet? (See Figure 1-31 below.)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-106  
A500 System Console  
(c) 1997 Lucent Technologies  
login: root  
password: XXXXXX  
********** New System Alarms **********  
[1] Failed to fetch configuration files  
******* Hit any key to continue *******  
A500:  
Figure 1-31. A500 login screen  
5. Enter status at the A500:prompt. Figure 1-32 shows the output from the  
status command.  
System Status  
A500 System, Ace_200.01  
Copyright 1996, 1997 Lucent Technologies  
Built Tue Dec 2 08:45:26 EST 1997  
by jdoe in view cm_ace_200  
__________________________________________________  
System name  
--  
System time/date  
System Uptime  
-- Wednesday, December 3, 1997 15:59:07p  
-- days 1,  
-- hours 1,  
-- minutes 1  
Ethernet IP address  
Ethernet IP mask  
LEC IP address  
LEC IP mask  
-- 123.1.123.12  
-- 255.255.255.0  
-- 0.0.0.0  
-- 0.0.0.0  
IP default router  
TFTP server  
-- 123.1.123.123  
-- 123.1.123.234  
base MAC address  
ATM address  
-- 12:34:56:78:9a:bc  
-- 45.0000.00000123456789abcdef.123456789abc.00  
Figure 1-32. A500 screen output for status command  
a. If the customer is providing an Ethernet connection to the A500,  
does the Ethernet IP addressfield have the  
customer-provided Internet address (configured using the admin  
address command)?  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-107  
If you are administering the A500 through a telnet connection over  
the Ethernet, this works, but it is worthwhile making sure the  
Ethernet address is correct anyway.  
b. If the customer is providing an Ethernet connection to the A500,  
does the Ethernet IP maskfield have the customer-provided  
mask (typically something like 255.255.255.0, although other  
values are valid), as configured with the admin address  
command?  
c. If the customer is providing an Ethernet connection to the A500,  
does the IP default routerfield have the customer-provided  
Internet address, as configured using the admin gateway  
command?  
d. If the customer is providing an Ethernet connection to the A500 and  
intends to upload to or download from a TFTP server, does the  
TFTP serverfield have the customer-provided Internet address,  
as configured using the tftp setserver command?  
e. Does the ATM addressfield have the customer- or  
Lucent-provided network prefix (the first thirteen bytes and set by  
using the modify atmprefix command)?  
DEFINITY Administration  
Is ATM PNC administered correctly?  
1. Enter list atm pnc on the DEFINITY SAT. The cabinet, carrier and slot  
positions of each administered TN230X board display as shown in Figure  
1-33. Ensure that each board’s physical location matches the display.  
list atm pnc  
Page  
1
SPE A  
ATM PNC  
PNC  
A-PNC  
LOC  
B-PNC  
LOC  
Connection #  
1
2
01B02  
02A01  
Figure 1-33. Screen output for list atm pnc command  
Alternatively, use the list configuration UUC command (non-control  
cabinets) to confirm the PPN and EPN board locations and correct  
insertion.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-108  
2. Enter status pnc at the DEFINITY SAT. This display tells you which  
TN230X board is active in a duplicated system and how many alarms (if  
any) of each severity level have been logged for the board. Figure 1-34  
shows the output from this command.  
status pnc  
PORT NETWORK CONNECTIVITY  
Duplicated? no  
Software Locked?  
Standby Busied?  
Standby Refreshed?  
Interchange Disabled?  
A-PNC  
B-PNC  
Mode: active  
State of Health:  
Inter PN Index:  
Mode:  
State of Health:  
Inter PN Index:  
Major Alarms: 0  
Minor Alarms: 0  
Warning Alarms: 0  
Major Alarms:  
Minor Alarms:  
Warning Alarms:  
Figure 1-34. Screen output for status pnc command  
3. Enter either list configuration UUC (for the carrier in which the ATM-EI  
packs reside) or display circuit-packs cabinet (non-control cabinet) at  
the DEFINITY SAT. This command tells you in more detail what boards are  
in which slots in each cabinet and carrier. Verify that the TN230Xs are  
physically located in the slots indicated on the display. Figure 1-35 shows  
the output for the display circuit-packs 1 command; Figure 1-36 shows  
the output for the display circuit-packs 2 command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-109  
display circuit-packs 1  
CIRCUIT PACKS  
Cabinet: 1  
Cabinet Layout: five-carrier  
Carrier: A  
Carrier Type: processor  
*** PROCESSOR BOARDS NOT ADMINISTERABLE IN THIS SCREEN ***  
CIRCUIT PACKS  
Cabinet: 1  
Carrier: B  
Cabinet Layout: five-carrier  
Carrier Type: port  
Slot Code Sfx Name  
Slot Code Sfx Name  
00:  
01:  
11: TN464 C  
12: TN464 F  
DS1 INTERFACE  
DS1 INTERFACE  
02: TN2305 ATM PNC EI  
03:  
13: TN767 F  
DS1 INTERFACE  
14: TN767 C  
15: TN760 D  
16: TN760 D  
17:  
DS1 INTERFACE  
TIE TRUNK  
TIE TRUNK  
04: TN754 C  
05: TN746 B  
06: TN753  
DIGITAL LINE  
ANALOG LINE  
DID TRUNK  
07: TN771 D  
08: TN747 B  
09: TN556 B  
10: TN767 C  
MAINTENANCE/TEST  
CO TRUNK  
BRI LINE  
18:  
19:  
20:  
DS1 INTERFACE  
’#’ indicates circuit pack conflict.  
Figure 1-35. Screen output for display circuit-packs 1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-110  
display circuit-packs 2  
Cabinet: 2  
CIRCUIT PACKS  
Carrier: A  
Cabinet Layout: single-carrier-stack  
Carrier Type: expansion-control  
Slot Code Sfx Name  
Slot Code Sfx Name  
11: TN746 B  
ANALOG LINE  
01: TN2305 ATM PNC EI  
12:  
02:  
03:  
04:  
05:  
06:  
07:  
08:  
13:  
14:  
15:  
16:  
17: TN754 C  
DIGITAL LINE  
09: TN767 E  
10: TN754 B  
DS1 INTERFACE  
DIGITAL LINE  
’#’ indicates circuit pack conflict.  
Figure 1-36. Screen output for display circuit-packs 2  
4. Enter display atm pnc portnetwork on the DEFINITY SAT.  
This display tells you the ATM addresses that have been administered for  
each TN230X. Verify that each ATM address (the concatenation of the five  
displayed hexadecimal fields) is correct and match those administered in  
the A500. See ‘‘A500 Administration’’ for more information.  
Administered with hard coded PNNI routes  
If the port networks are addressed using hard coded PNNI routes in the  
A500, the display looks like Figure 1-37 (pnc 1) and Figure 1-38 (pnc 2).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-111  
display atm pnc 1  
ATM PNC  
Connection Number: 1  
Location: 01B02  
Name:  
Address Format: ICD ATM  
AFI: 47  
ICD: 0005  
HO-DSP: 80FFE1000000F2071B02  
ESI: 000000000000  
SEL: 00  
Figure 1-37. Screen output for display atm pnc 1  
display atm pnc 2  
ATM PNC  
Connection Number: 2  
Location: 02A01  
Name:  
Address Format: ICD ATM  
AFI: 47  
ICD: 0005  
HO-DSP: 80FFE1000000F2072A01  
ESI: 000000000000  
SEL: 00  
Figure 1-38. Screen output for display atm pnc 2  
Administered with End System Identifiers  
If the port networks are addressed using End System Identifiers, the  
display looks like Figure 1-39 (pnc 1) and Figure 1-40 (pnc 2).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-112  
display atm pnc 1  
ATM PNC  
Connection Number: 1  
A - PNC  
Location: 01B02  
Name:  
Address Format: E.164 ATM Private  
AFI: 45  
E.164: 0001013035381053  
HO-DSP: 00000000  
ESI: 000000000011  
SEL: 00  
Figure 1-39. Screen output for display atm pnc 1 with End System Identifiers  
display atm pnc 2  
ATM PNC  
Connection Number: 2  
A - PNC  
Location: 02A01  
Name:  
Address Format: E.164 ATM Private  
AFI: 45  
E.164: 0001013035381053  
HO-DSP: 00000000  
ESI: 000000000012  
SEL: 00  
Figure 1-40. Screen output for display atm pnc 2 with End System Identifiers  
A500 Administration  
Is the A500 administered correctly?  
1. Enter show signaling summary on the A500 console. Figure 1-41 shows  
the screen output.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-113  
A500:show signaling summary  
Port  
------ -------  
A1.1  
A1.2  
loc VCI  
SAP  
---  
1
IntType  
-------  
Network  
Network  
Signaling  
ILMI SAP State  
State  
----------- ---- ------------ -----  
UNI3.1  
UNI3.1  
1
2
No  
No  
UP  
UP  
UP  
UP  
2
Figure 1-41. Screen output for the show signaling summary command  
a. If an A500 port to which a DEFINITY port network is attached is not  
listed in this display, it is likely that the port was administered  
incorrectly as having no UNI signaling (admin link command).  
Ensure that fields listed have the values indicated below.  
Field  
Value  
IntType  
Network  
If it is User, links will not come up between the PPN and  
the EPN.  
Signaling UNI3.1  
If it is UNI3.0, links will not come up between the PPN  
and the EPN.  
ILMI  
Preferred value of is No, however this alone does not  
prevent links from coming up between the PPN and an  
EPN.  
SAP State May or may not be UP. Their values depend on more than  
just whether the port was marked as UP. (See  
highlighted data for SAP State in Figure 1-41.)  
2. If the A500 was administered using hard-coded PNNI routes to identify  
each endpoint, enter show signaling routes on the A500 console. Figure  
1-42 shows the screen output from the command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-114  
A500:show signaling routes  
Number of Local Static Routes Allowed: 30  
Current number of Local Static Routes: 2  
Address: 47.00.05.80.ff.e1.00.00.00.f2.07.2a.01.00.00.00.00.00.00.00  
mask:152 cost:  
0 node:self port:A1.2 state:UP  
Address: 47.00.05.80.ff.e1.00.00.00.f2.07.1b.02.00.00.00.00.00.00.00  
mask:152 cost: 0 node:self port:A1.1 state:UP  
Figure 1-42. Screen output from the show signaling routes command  
Check that the Addressfield (administered using the admin signaling  
route add command) matches those administered in DEFINITY.  
3. If the A500 was administered using End System Identifiers, enter show  
signaling esi on the A500 console. Figure 1-43 shows the command  
output.  
A500:show signaling esi  
Addresses registered on A1.1  
----------------------------  
* 45.0001.01303538105300000000.000000000011.00  
Addresses registered on A1.2  
----------------------------  
* 45.0001.01303538105300000000.000000000012.00  
( * - configured )  
Figure 1-43. Screen output A500: show signaling esi command  
Check that the Addresses registered(use the admin signaling esi  
add command) match those administered in DEFINITY.  
■
If an address or End System Identifier is missing or incorrect on the  
A500 port associated with the PPN, the EAL and PACL links will  
come up, but one-way talk paths may result. (The ATM network can  
route from the PPN to the EPN, which creates the bidirectional EAL  
and PACL signaling channels and one side of the talk path.)  
■
If an address or End System Identifier is missing or incorrect on the  
A500 port associated with the EPN, the links will not come up  
between the PPN and the EPN.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-115  
4. Enter show sys interfaces on the A500 console. Figure 1-44 shows the  
screen output.  
Device  
Oper  
Status  
Admin  
Status  
State  
Type  
_________________________________________________________________  
A1.1  
A1.2  
A1.3  
A1.4  
A1.5  
A1.6  
A1.7  
A1.8  
A2.1  
A2.2  
A2.3  
A2.4  
A2.5  
A2.6  
A2.7  
A2.8  
A3.1  
A3.2  
A3.3  
A3.4  
A3.5  
A3.6  
A3.7  
A3.8  
A4.1  
A4.2  
A4.3  
A4.4  
A4.5  
A4.6  
A4.7  
A4.8  
Self  
Self  
E1.1  
up  
up  
up  
up  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
present  
present  
present  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
PROPVIRTUAL  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
up  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
up  
up  
up  
up  
up  
SAR  
TenBaseT  
Figure 1-44. A500 screen output for show sys interfaces command  
■
For each administered port used by a DEFINITY port network, the  
Admin Statusshould be up(using the admin up command).  
■
The state of Oper Statusis not pertinent to administration of the  
A500 and is discussed in a later section.  
■ Stateshould be present, indicating that A500 port board  
insertion was successful. If Stateis invalid, then the A500  
believes that the corresponding port board slot is empty or the port  
board is not recognized.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-116  
It may be necessary to re-administer the A500 port boards. Refer to  
the Cajun A500 Quick Reference for further information.  
■
If Admin Statusor Stateis incorrect, the links will not come up  
between the PPN and the EPN.  
TN230X  
Did the TN230X come up correctly?  
1. Review the LED conditions for the TN230X:  
■
Do the TN230X LEDs (see Table 1-14) indicate a normal  
operational state (any of the following):  
— Active in the PPN  
— Standby in the PPN  
— Archangel mode in the EPN  
— Standby in the EPN?  
2. If after board insertion or a demand reset:  
■
■
■
Do the TN230X LEDs indicate that it is booting?  
Do the TN230X LEDs indicate it is downloading its DSPs?  
Do the TN230X LEDs indicate that board insertion has not yet  
occurred?  
■
Do the TN230X LEDs indicate a maintenance alarm?  
3. Enter list configuration carrier cabinetcarrier on the DEFINITY SAT. See  
Figure 1-45 (1b) and Figure 1-46 (2a) below.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-117  
list configuration carrier 1b  
Board  
SYSTEM CONFIGURATION  
Assigned Ports  
Number  
Board Type  
Code  
Vintage  
u=unassigned t=tti p=psa  
01B02  
01B04  
01B05  
ATM PNC EI  
DIGITAL LINE  
ANALOG LINE  
TN2305 000001  
TN754C 000002  
TN746B 000010  
u u u u u u u u  
u u u u u 06 u u  
u u u u u u u u  
u u u u u u u u  
u 02 03 04  
u u u u u u u u  
u u u u u u u u  
u u u u u u u u  
u u u u u u u u  
u u u u u u u u  
u u u u u u u u  
u u u u u u u u  
01B06  
01B07  
01B08  
01B09  
DID TRUNK  
MAINTENANCE/TEST  
CO TRUNK  
TN753  
000021  
TN771D 000006  
TN747B 000018  
TN556B 000003  
BRI LINE  
01B10  
DS1 INTERFACE  
TN767C 000003  
Figure 1-45. List configuration carrier 1b screen  
list configuration carrier 2a  
SYSTEM CONFIGURATION  
Board  
Assigned Ports  
Number  
Board Type  
Code  
Vintage  
u=unassigned t=tti p=psa  
02A01  
02A09  
ATM PNC EI  
DS1 INTERFACE  
TN2305 000001  
TN767E 000004  
u u u u u u u u  
u u u u u u u u  
u u u u u u u u  
u u u u u u u u  
01 u u u u u u u  
u u u u u u u u  
u u u u u u u u  
02A10  
02A11  
DIGITAL LINE  
ANALOG LINE  
TN754B 000016  
TN746B 000010  
02A17  
DIGITAL LINE  
TN754C 000002  
Figure 1-46. List configuration carrier 2a screen  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-118  
■
■
The TN230X board should be shown in the correct slot.  
Fields should have values as indicated below:  
Field  
Value  
Board Type ATM PNC EI  
Vintage  
The TN230X vintage. If Vintageis no board, then  
either the board is in the incorrect slot or board insertion  
was not completed correctly. Refer to  
‘‘Reseating/Replacing Circuit Packs’’ in this chapter.  
4. If the TN230X is inserted and shows a vintage number, enter test board  
cabinetcarrierslot for this board on the DEFINITY SAT, as shown in Figure  
1-47 (1b02) and Figure 1-48 (2a01).  
test board 1b02  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
Error Code  
01B02  
01B02  
01B02  
01B02  
01B02  
01B02  
ATM-EI  
ATM-EI  
ATM-EI  
ATM-EI  
ATM-EI  
ATM-EI  
316  
598  
1258  
241  
304  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
1259  
Figure 1-47. Screen output for the test board 1b02 command  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-119  
test board 2a01  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
02A01  
02A01  
02A01  
02A01  
02A01  
02A01  
ATM-EI  
ATM-EI  
ATM-EI  
ATM-EI  
ATM-EI  
ATM-EI  
316  
598  
1258  
241  
304  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
1259  
Figure 1-48. Screen output for the test board 2a01 command  
■
The Resultshould be PASSfor each test number. If the any of the  
tests fail, refer to ‘‘ATM-BCH (ATM B-Channel Trunk)’’.  
Possible Causes  
1. The TN230X board is in a slot different from the DEFINITY administration.  
2. The TN230X did not complete board insertion.  
Physical Layer  
Is there an optical signal between the TN230X and the A500?  
1. Does the TN230X’s yellow LED flash 100ms on/100ms off, indicating a loss  
of signal on the fiber? Recall that the TN230X detects continuity problems  
with either the Transmit (bottom) or the Receive (top) fibers.  
2. Is the A500 port’s CD LED off, indicating a loss of signal on the fiber? Note  
that the A500 detects continuity problems only with the Receive  
(right-hand) fiber; the state of the Transmit (left-hand) fiber is not detected.  
3. Enter show signaling summary on the A500 console. Figure 1-49 shows  
the screen output.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-120  
A500:show signaling summary  
Port  
------ -------  
A1.1  
A1.2  
loc VCI  
SAP  
---  
1
IntType  
-------  
Network  
Network  
Signaling  
ILMI SAP State  
State  
----------- ---- ------------ -----  
UNI3.1  
UNI3.1  
1
2
No  
No  
UP  
UP  
UP  
UP  
2
Figure 1-49. A500: show signaling summary screen  
Ensure that the fields have the values indicated below.  
SAP State Up  
If it is PHY_DOWNor DOWN, then there is probably a loss of signal  
on the port in question. This command detects a continuity  
problem only with the Receive (right-hand) fiber; it does not  
detect the state of the Transmit (left-hand) fiber.  
State  
The value of may be UPor DOWN, depending on the  
administration of the port. It may be necessary to  
re-administer the A500 port boards. Refer to the Cajun  
A500 Quick Reference for further information.  
4. Enter show system interfaces on the A500 console. Figure 1-50 shows  
an example of the screen output.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-121  
Device  
Oper  
Admin  
State  
Type  
Status  
Status  
_________________________________________________________________  
A1.1  
A1.2  
A1.3  
A1.4  
A1.5  
A1.6  
A1.7  
A1.8  
A2.1  
A2.2  
A2.3  
A2.4  
A2.5  
A2.6  
A2.7  
A2.8  
A3.1  
A3.2  
A3.3  
A3.4  
A3.5  
A3.6  
A3.7  
A3.8  
A4.1  
A4.2  
A4.3  
A4.4  
A4.5  
A4.6  
A4.7  
A4.8  
Self  
Self  
E1.1  
up  
up  
up  
up  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
present  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
invalid  
present  
present  
present  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
STS_3c (MultiMode)  
PROPVIRTUAL  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
up  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
down  
up  
up  
up  
up  
up  
SAR  
TenBaseT  
Figure 1-50. A500: show sys interfaces  
— Oper Statusshould be up. If it is down, there is likely a loss of  
signal on the port in question (Stateof present), or the A500  
does not recognize the port board (Stateof invalid). This  
command detects a continuity problem only with the Receive  
(right-hand) fiber; it does not detect the state of the Transmit  
(left-hand) fiber.  
Possible Causes  
■
The fiber is disconnected from the A500 and/or the TN230Xs.  
■
The Transmit and Receive fibers are swapped at the A500 or the TN230X  
(but not both).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-122  
■
■
There is a break in the fiber.  
The TN230X is not transmitting a carrier (not inserted, not powered, or not  
administered). See ‘‘ATM-BCH (ATM B-Channel Trunk)’’.  
■
■
Hardware safety interlocks on optical transceivers may cut transmitter  
power if no carrier is received, so lack of a receive carrier could indicate a  
transmitter problem at the same end.  
The A500 does not recognize that there is a port board in the slot. It may  
be necessary to re-administer the A500 port boards. Refer to the Cajun  
A500 Quick Reference for further information.  
Recommended Action  
1. Plug in, swap, repair, or replace the fiber as necessary.  
2. Verify that the port board is inserted.  
SONET Layer  
Are SONET frames reaching the A500?  
Is the A500 port’s green RX LED solid off, indicating no cell traffic?  
1. Enter show stats sonet port on the A500 console. Figure 1-51 shows the  
screen output.  
NOTE:  
The following examples point to port A1.2 as the port of interest.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-123  
Sonet per Port Statistics  
---------------------------------  
Receive Cell Count:  
Transmit Cell Count:  
80654  
79555  
Section Level Bit Err:  
Line Bit Err:  
1
1
Line FEB Err:  
Path Bit Err:  
168  
1
Path FEB Err:  
98  
0
0
1
0
Correctable HCS Err:  
Uncorrectable HCS Err:  
Loss of Frame Err:  
Loss of Signal Err:  
Out of Frame Err:  
0
Path Signal Label:  
19  
Figure 1-51. A500: show stats sonet a1.2 screen  
Ensure that the fields have the values indicated below.  
Receive Cell  
Count  
Each field’s values should be increasing if the TN230X is  
actively sending and receiving cells with the A500. (Even if  
a TN230X did not achieve board insertion, it will still try to  
talk to the A500.)  
Transmit  
Cell Count  
If neither field is increasing, the A500 port may have been  
marked down using the admin down command. Use the  
show system interfaces command to verify that the Admin  
Statusis up.  
If the Receive Cell Countis increasing but the  
Transmit Cell Countis not increasing, this may be  
because the port was administered with no UNI signaling  
(admin link command). Use the show signaling summary  
command to ensure that Signalingis UNI3.1.  
The error counters may not be zero, but should not be large  
either compared to the receive and transmit cell counters. If  
the counters are large and increasing, check the fiber  
integrity. Make sure the fiber pairs are securely plugged into  
both the TN230X and the A500.  
If the fiber has been pulled and reinserted as part of fault  
diagnosis, the non-zero Loss of Signal Errcounter  
may be correct.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-124  
Q.SAAL (Data Link) Layer  
Are ATM signaling messages reaching A500 Call Control?  
1. Enter show signaling stats port qsaal on the A500 console. Figure 1-52  
shows the screen output.  
A500: show signaling stats a1.2 qsaal  
------------------------Q.SAAL Statistics------------------------  
Port A1.2:  
----------  
Type: UNI3.1  
VPI: 0x00, VCI: 0x05  
Tx  
Rx  
--------  
--------  
BGN PDUs:  
BGAK PDUs:  
END PDUs:  
0
1
0
1
0
0
ENDAK PDUs:  
RS PDUs:  
0
0
0
0
RSAK PDUs:  
BGREJ PDUs:  
SD PDUs:  
0
0
81  
0
0
78  
SDP PDUs:  
Supported only for UNI 3.0  
ER PDUs:  
0
0
POLL PDUs:  
STAT PDUs:  
USTAT PDUs:  
ERAK PDUs:  
Discarded PDUs:  
Errored PDUs:  
Buffers in use:  
High buffer mark:  
6259  
5720  
5720  
6259  
0
0
0
0
0
3
0
0
0
0
0
0
Figure 1-52. A500: show signaling stats a1.2 qsaal screen  
NOTE:  
If there is no connection between the TN230X and the A500 at the Q.SAAL  
protocol layer, then no report is displayed.  
— If Port A1.2(or the port of interest) is not configured for  
UNI signaling, then the port was administered for no UNI  
signaling (admin link command). Use the show signaling  
summary command to verify that Signalingis UNI3.1.  
— The Supported only for UNI 3.0line for the SDP PDUs:  
field means that the port was administered for UNI3.0 signaling  
(admin link command). Use the show signaling summary  
command to verify that Signalingis UNI3.1.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-125  
— The POLL PDUsand STAT PDUscounters should be increasing if  
the TN230X is actively sending and receiving Q.SAAL Protocol  
Data Units with the A500. This occurs even if the TN230X did not  
achieve board insertion.  
Q.93B (Network) Layer  
Are connection requests being received by A500 Call Control?  
1. Enter show signaling stats port q93b (or the port of interest) on the A500  
console. Figure 1-53 shows the screen output.  
A500:show signaling stats a1.2 q93b  
-------------------------Q.93B Statistics------------------------  
Port A1.2:  
----------  
Tx  
Rx  
--------  
--------  
Connect Messages:  
Setup Messages:  
15  
18  
18  
15  
Release Messages:  
Rel Cmplt Messages:  
Add Party Messages:  
Add Party Acks:  
17  
13  
0
0
13  
17  
0
0
Add Party Rejects:  
Drop Party Messages:  
Drop Party Acks:  
Last Cause Code:  
Last Diag Code:  
0
0
0
31  
0
0
0
31  
0. 0. 0  
71. 0.29  
Total Connections:  
Current Connections:  
33  
3
Figure 1-53. A500:show signaling stats A1.2 q93b  
NOTE:  
If there is no connection between the TN230X and the A500 at the  
Q93B protocol layer, then no report displays.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-126  
Ensure that the fields have the values indicated below.  
Port  
If this field is not configured for UNI signaling,  
A1.2  
then the port was administered for no UNI signaling  
(admin link command). Use the show signaling  
summary command to verify that Signalingis UNI3.1.  
(or the  
port of  
interest)  
Connect  
These counters should be non-zero if the A500 is  
Messages handling Q.93B protocol layer messages sent by the PPN  
and EPN. They may not increase during troubleshooting  
Setup  
unless calls are being made, since the PPN initially sets  
Messages  
up control connections to the PPN and then sets up talk  
Release  
path connections as needed.  
Messages  
2. If connections are being rejected, the Last Cause Codemay give a clue  
to why. The Cause Code (Table 1-16 below) indicating the error may be on  
the PPN port even though the EPN port is the one misbehaving, and vice  
versa.  
Enter show signaling cause causecode on the A500 console. Figure  
1-54 shows the screen output for this command.  
A500:show signaling cause 31  
Cause 31: Normal, unspecified  
Figure 1-54. A500:show signaling cause 31  
3. At the DEFINITY SAT type display errors and press Enter.  
Set the Error Listto errors and Categoryto PNC on the input screen  
(Figure 1-55) and press Enter to display any Cause Codes (see Table 1-16  
below) returned from the ATM network to a TN230X on the PPN (and to a  
TN230X on an EPN). This is successful only if the links between the PPN  
and the EPN remain up so that the message from the EPN is logged.  
Refer to ‘‘ATM-BCH (ATM B-Channel Trunk)’’ for detailed information  
regarding Cause Codes for this Maintenance Object.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-127  
display errors  
Page 1 of 1 SPE A  
ERROR REPORT  
The following options control which errors will be displayed.  
ERROR TYPES  
Error Type:  
Error List: errors  
REPORT PERIOD  
Interval: a  
From:  
/ / :  
To:  
/ / :  
EQUIPMENT TYPE ( Choose only one, if any, of the following )  
Cabinet:  
Port Network:  
Board Number:  
Port:  
Category: PNC  
Extension:  
Trunk ( group/member ):  
/
Figure 1-55. DEFINITY display errors Input Screen  
Figure 1-56 shows the screen output for the display errors command.  
display errors  
Page 9 SPE A  
HARDWARE ERROR REPORT  
Port  
Mtce  
Name  
Alt  
Name  
Err Aux  
Type Data  
First  
Occur  
Last  
Occur  
Err Err Rt/ Al Ac  
Cnt Rt Hr St  
AT01A  
AT01A  
AT02A  
AT02A  
AT01B  
AT01A  
ATM-NTWK  
ATM-NTWK  
ATM-NTWK  
ATM-NTWK  
ATM-NTWK  
ATM-NTWK  
41  
31  
0
31  
31  
3
1
0
0
0
0
1
11/12/16:59 12/09/15:10 14 0 0 n n  
11/13/18:27 11/20/20:02 5 0 0 n n  
11/13/18:45 11/13/18:45 1 0 0 n n  
11/15/14:40 11/15/14:41 2 120 0 n n  
11/16/17:39 11/16/17:39 1 0 0 n n  
11/16/18:19 11/26/13:13 12 0 0 n n  
Figure 1-56. Screen output for display errors command  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-128  
In this example the errors that have ATM-NTWKfor Nameand 1for Data  
indicate an error returned to the TN230X from the ATM network. In this  
case, Typeindicates the Cause Code returned by the ATM network (see  
Table 1-16 below). In the example above, two Cause Codes (41 and 3)  
are reported from the ATM network. For more information about these  
Cause Codes and repair information see ‘‘ATM-NTWK (ATM Network  
Error)’’.  
Table 1-16. Observed Cause Codes  
Cause  
Code  
Definition  
Observed Cause  
3
No route to destination  
The ATM addresses administered in the ATM switch  
(show signaling routes or show signaling esi) or in  
DEFINITY (display atm pnc) are incorrect.  
31  
41  
Normal, unspecified  
Temporary failure  
This is a normal return.  
This "try again later" Cause Code has been observed  
when the source of the problem is on another port (for  
example, a routing problem on another port that  
displays Cause Code 3).  
47  
63  
Resources unavailable,  
unspecified  
DEFINITY call volume is too high for the available  
resources in the ATM network.  
Service or option unavailable,  
unspecified  
DEFINITY call volume is too high for the available  
resources in the ATM network.  
ATM Call Control  
Are ATM signaling connections being setup to A500 Call Control?  
1. Enter show switch circuittable on the A500 console. Figure 1-57 shows  
the screen output.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-129  
A500:show switch circuittable  
_______________________________________________________  
|
Input  
|
Output  
|
Connection  
|
| port vpi vci| port vpi vci| type class parameters |  
|______________|______________|_________________________|  
A1.1  
A1.1  
A1.1  
0
0
0
5 Self  
32 A1.2  
35 A1.2  
0
0
0
1 pp  
32 pp  
35 pmp CBR  
UBR  
ppd on  
VBRnrt pcr=5729 /scr=5729 /mbs=17187  
pcr=173  
ppd on  
A1.2  
A1.2  
A1.2  
0
0
0
5 Self  
32 A1.1  
34 A1.1  
0
0
0
2 pp  
32 pp  
34 pmp CBR  
UBR  
VBRnrt pcr=5729 /scr=5729 /mbs=17187  
pcr=173  
Self  
Self  
0
0
1 A1.1  
2 A1.2  
0
0
5 pp  
5 pp  
UBR  
UBR  
ppd on  
ppd on  
_________________________________________________________  
Figure 1-57. A500: show switch circuittable screen  
■
The pp UBRvirtual circuits between A500 ports A1.1 (PPN) and Self  
(A500) and between A1.2(EPN) and Self(A500) are ATM signaling  
channels between the port network and the A500.  
■
■
■
They are used to request connection setups and releases to other end  
points such as another port network.  
These are established by each TN230X when it comes up, independent of  
DEFINITY Call Processing.  
Other UBR virtual circuits may exist between A500 ports that are not  
associated with DEFINITY port networks and may be signaling channels  
for other applications (for example, data network traffic).  
CaPro Layer  
Are control channels being established from the PPN to the EPN?  
Diagnostics  
■
Do you get a dial tone on a set on the port network in question?  
Can you ring a set on the EPN dialing from the PPN and vice versa?  
■
1. Enter list sys-link on the DEFINITY SAT. Figure 1-58 shows the screen  
output.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-130  
list sys-link  
SYSTEM LINKS INFORMATION  
Location Link Type/  
Channel  
State  
Current  
Path  
Faulted  
Path  
Last Fault  
Recorded  
02A0101  
01B0202  
02A0102  
EAL  
PACL  
PACL  
up  
up  
up  
present  
present  
present  
present  
present  
present  
12/06/1997 16:20  
12/06/1997 16:17  
12/06/1997 16:20  
Figure 1-58. List sys-link screen  
Ensure that the fields have the values indicated below.  
Link Type/  
Channel  
One PACLto each TN230X in either a PPN or an EPN, and  
one EALto each TN230X in an EPN.  
State  
up  
2. Enter show switch circuittable on the A500 console. Figure 1-59 shows  
the screen output.  
A500:show switch circuit  
_______________________________________________________  
Input Output Connection |  
|
|
|
| port vpi vci| port vpi vci| type class parameters |  
|______________|______________|_________________________|  
A1.1  
A1.1  
A1.1  
0
0
0
5 Self  
32 A1.2  
35 A1.2  
0
0
0
1 pp  
32 pp  
35 pmp CBR  
UBR  
ppd on  
VBRnrt pcr=5729 /scr=5729 /mbs=17187  
pcr=173  
ppd on  
A1.2  
A1.2  
A1.2  
0
0
0
5 Self  
32 A1.1  
34 A1.1  
0
0
0
2 pp  
32 pp  
34 pmp CBR  
UBR  
VBRnrt pcr=5729 /scr=5729 /mbs=17187  
pcr=173  
Self  
Self  
0
0
1 A1.1  
2 A1.2  
0
0
5 pp  
5 pp  
UBR  
UBR  
ppd on  
ppd on  
_________________________________________________________  
Figure 1-59. A500: show switch circuit screen  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
ATM Tips  
1
1-131  
■
The pp VBRnrt (Variable Bit Rate) virtual circuits between A500 ports A1.1  
(PPN) and A1.2 (EPN) are used for signaling between the PPN and each  
EPN.  
■
These are established once upon initialization under control of DEFINITY  
Call Processing. They represent the ATM Control Link (ACL) and  
Expansion Archangel Link (EAL).  
■
■
VBRnrt virtual circuits are also be used for ISDN channels between  
Definity port networks.  
Other VBRnrt virtual circuits may exist between A500 ports that are not  
associated with DEFINITY port networks. A common use of VBRnrt circuits  
is multimedia and video-conferencing systems.  
CaPro Layer  
Are talk paths being established between port networks?  
Diagnostics  
■
Can you talk both ways on a set on one port network dialed from another  
port network and vice versa?  
1. Enter show switch circuit on the A500 console. Figure 1-60 shows the  
screen output.  
A500:show switch circuit  
_______________________________________________________  
Input Output Connection |  
|
|
|
| port vpi vci| port vpi vci| type class parameters |  
|______________|______________|_________________________|  
A1.1  
A1.1  
A1.1  
0
0
0
5 Self  
32 A1.2  
35 A1.2  
0
0
0
1 pp  
32 pp  
35 pmp CBR  
UBR  
ppd on  
VBRnrt pcr=5729 /scr=5729 /mbs=17187  
pcr=173  
ppd on  
A1.2  
A1.2  
A1.2  
0
0
0
5 Self  
32 A1.1  
34 A1.1  
0
0
0
2 pp  
32 pp  
34 pmp CBR  
UBR  
VBRnrt pcr=5729 /scr=5729 /mbs=17187  
pcr=173  
Self  
Self  
0
0
1 A1.1  
2 A1.2  
0
0
5 pp  
5 pp  
UBR  
UBR  
ppd on  
ppd on  
_________________________________________________________  
Figure 1-60. A500:show switch circuit screen  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Unusual ATM trouble conditions  
1
1-132  
— The pmp CBR (Constant Bit Rate) virtual circuits (VCs) between  
A500 port A1.1 (PPN) and A500 port A1.2 (EPN) are used for talk  
paths between port networks (PPN to EPN, EPN to PPN, or EPN to  
EPN).  
— They are established when calls are first setup between port  
networks. Each virtual circuit represents one party of a complete  
multiparty talk path.  
— The report above shows one complete talk path: one unidirectional  
point-to-multipoint virtual circuit from A1.1 to A1.2, and another from  
A1.2 to A1.1.  
— These virtual circuits may persist beyond the duration of a phone  
call. The DEFINITY Call Processing software saves virtual circuits  
for a few seconds after the end stations have hung up in case the  
VC can be used again for another call between the same two port  
networks.  
— In early version of the Release 2 A500 firmware, these connections  
incorrectly identified as pmp UBR.  
— There may be other CBR virtual circuits between A500 ports that  
are not associated with DEFINITY port networks. A common CBR  
application is Circuit Emulation, in which T-1, T-3, etc. circuits are  
carried over ATM.  
Unusual ATM trouble conditions  
There are a few failure modes in the DEFINITY/A500 combination that are  
particularly difficult to diagnose. One example might be that you can’t make a  
completely successful call, even though most indications from DEFINITY and the  
A500 look pretty good. This section documents some hints and clues that may  
help diagnose the following failure modes:  
■
Incorrectly typed or omitted EPN Route or End System Identifier (A500)  
■
Swapped Routes, End System Identifiers, or Fiber between a PPN and an  
EPN  
■
■
Swapped Routes, End System Identifiers, or Fiber between A and B side  
TN230Xs on an EPN  
Swapped Routes, End System Identifiers, or Fiber between two EPNs  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Unusual ATM trouble conditions  
1
1-133  
Incorrectly typed or omitted EPN Route or End  
System Identifier (A500)  
Symptoms  
Talk paths are one-way, from the PPN to the EPN: you can hear tones from the  
PPN end station to the EPN end station but not vice versa. Because the signaling  
channels are bidirectional virtual circuits (VCs) established from the PPN to the  
EPN, these can be routed correctly and come up just fine. Talk paths are two  
unidirectional virtual circuits, so a single call has one VC from the PPN to the EPN  
(which is routed correctly) and one VC from the EPN to the PPN (which cannot be  
routed).  
Diagnostics  
1. At the A500 use the show signaling routes or show signaling esi  
command(s) as appropriate to check the ATM addresses.  
2. Use show signaling stats port q93b on the EPN port and look for Cause  
Code 3 (No route to destination).  
Action  
1. Correct the ATM address translations in the A500.  
Swapped Routes, End System Identifiers, or Fiber  
between a PPN and an EPN  
Symptoms  
■
■
An incorrectly-connected EPN TN230X does not complete board insertion.  
Dial tone is present on end stations on the PPN and on  
correctly-connected EPNs, but no dial tone is present on the affected EPN  
end stations.  
■
Calls cannot be made between the PPN and the correctly connected  
EPNs, because talk paths cannot be routed correctly.  
Diagnostics  
1. The show switch circuittable command on the A500 shows VBR control  
channels from the A500 port intended for the incorrectly-connected EPN  
(but actually connected logically or physically to the PPN) that should not  
exist.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
Unusual ATM trouble conditions  
1
1-134  
Action  
1. Correct the ATM addresses (or swap fibers) on the A500 between the  
incorrectly-connected PPN and EPN.  
Swapped Routes, End System Identifiers, or Fiber  
between two EPNs  
Symptoms  
■
■
■
All TN230Xs complete board insertion.  
The PPN cold starts both incorrectly connected EPNs as usual.  
Both EPNs log many WRONG BOARD INSERTEDerrors (use list  
configuration all or display circuit-packs <carrier>) providing the EPNs  
actually do have different boards configured in the same slots.  
■
■
Some end stations may work if they are connected to the correct board in  
the same slot on both EPNs. Otherwise, end stations on the PPN have dial  
tone, while end stations on the EPNs do not.  
All A500 diagnostic commands look good.  
Diagnostics  
Action  
1. Check log for WRONG BOARD INSERTEDerrors (use list configuration all  
or display circuit-packs <carrier>).  
1. Correct the ATM addresses (or swap fibers) on the A500 between the  
incorrectly connected EPNs.  
Swapped Routes, End System Identifiers, or Fiber  
between A and B side TN230Xs on an EPN  
Symptoms  
■
■
The PPN establishes links to what it thinks is the active TN230X on the  
EPN.  
As normal, it reboots this TN230X, and when complete, it resets the EPN.  
When this happens, the active (instead of the standby) TN230X reboots,  
dropping the links.  
■
To recover, the PPN re-establishes links to what it thinks is the active  
TN230X and the cycle repeats indefinitely.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Troubleshooting Multimedia Call Handling (MMCH)  
1-135  
Diagnostics  
1. The status pnc command on the DEFINITY SAT shows both the A-side  
and B-side State of Healthfield as partially functional.  
Action  
1. Correct the ATM addresses (or swap fibers) on the A500 between the A  
and B side of the EPN.  
Troubleshooting Multimedia Call  
Handling (MMCH)  
Before troubleshooting any problems associated with the DEFINITY MMCH,  
always be sure that the endpoint is operating correctly (audio, video, and data)  
by making point-to-point test calls. If possible, make the test calls over the  
network to test the connectivity and routing of network calls from the endpoint.  
This eliminates problems such as disconnected audio or video cables and  
network troubles.  
64 Kbps Calls Terminate but Far End Receives  
56 Kbps Indication  
Description  
Some 2x64 Kbps conferences on the DEFINITY MMCH do not establish because  
of framing, audio, or video problems.  
For calls that are routed in the network through a Lucent Technologies/LEC  
interface, the originating equipment may launch a 64 Kbps call attempt, and the  
far end receives either a 56 Kbps or 64 Kbps indication. If the far end receives a  
64 Kbps indication, the call may have used 56 Kbps facilities. If so, the call may  
exhibit any of the following conditions:  
■
■
■
No handshaking in one direction or both (call disconnects after timeouts)  
Call connects, but audio or video is corrupted (audio noise or no video)  
Call succeeds without disruption (this is the least likely since one endpoint  
must be aware that the call is really 56 Kbps to connect)  
If any of the above conditions occur, then 64 Kbps calls from the site are  
blocked.  
Solution  
Administer the conference for connection at 56 Kbps.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Troubleshooting Multimedia Call Handling (MMCH)  
1-136  
Calls Terminate with No Audio  
Description  
To support endpoints that do not support Multipoint Command Conference  
(MCC), the DEFINITY MMCH changes its capability set and initiates a capability  
set exchange with the endpoint when the Selected Communications Mode (SCM)  
changes. If the endpoint does not follow the SCM audio mode, the MCU may  
include the endpoint as a secondary (audio only) endpoint. If the endpoint sends  
an unknown or unsupported audio mode, then the TN788B decoder port mutes  
the endpoint from the conference. The user may hear the conference but may not  
be heard by other parties in the conference.  
Solution  
1. Use the Status Conference x form and check the Audio Mode field for the  
current operating mode of the conference.  
2. Another indication of the audio modes is in the “Incoming Mode  
Commands from Endpoint and Outgoing Commands from MMI” on page  
3 of the Status Conference x Endpoint y form. Check the Audiofields  
under the Mode Commands/Communication Modes section of the form.  
Some Parties Cannot Be Heard by Others (Audio  
Subsetting)  
Description  
Problems where varying subsets of the conference hear different things may  
have problems with the various summing resources/groups that are in use.  
Traditionally theses faults are caused by the SPE not cleaning up the connections  
properly. Isolation and diagnosis should focus on the VC resources in use by that  
conference.  
Solution  
1. Use the status conference command to list the VC resources in use by  
this conference. Try a hot replacement of any VC boards in use, which  
refreshes the VC translations and move all of the audio connections to  
different VC ports.  
2. If the problem still exists, try dropping the conference and then bringing  
the conference back up again. Not only does this refresh VC translations,  
but uses different timeslots as well.  
3. If the problem still exists, suspect a hardware problem. If practical, wait for  
the DEFINITY MMCH to be idle (no active conferences), and then check  
the circuit packs for active (yellow) LEDs. If any of these are unexpected,  
such as on a VC board, try replacing the board and then bringing the  
conference up again.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Troubleshooting Multimedia Call Handling (MMCH)  
1-137  
Calls Terminate with No Video  
Description  
Generally, loss of video can be divided into 2 types. The first occurs when the  
DEFINITY MMCH switches to the endpoint, but nobody sees them. The receivers  
see either “black” video or a frozen image of the previous speaker depending on  
the codec of the manufacturer. The type occurs when the DEFINITY MMCH does  
not switch to an endpoint.  
Solution  
In the first type described above, wiring problems, power to the camera, or video  
encoder circuit pack problems in the codec are typical causes.  
In the second type, no video from an endpoint typically occurs because it is not a  
valid video source. This can be checked by looking at page 1 of the Status  
Conference x Endpoint y Vid form under the Capability section. In this section, a  
“y” or “c” suggests that the endpoint has video. An “e” means ept has not  
declared any video capability in cap set, “n” is audio only, and “blank” means  
audio add-on.  
Also check page 1 of the Status Conference x Endpoint y Vs form for indication of  
the video state for the endpoint values.  
Calls Terminate Correctly but Are Unstable  
Description  
A number of conditions will lead to some or all endpoints having stability  
problems during the course of a conference. A lack of stability from an endpoint  
is noticeable by a lack of a video switching while the party is the only talker or  
excessive disconnects from that endpoint.  
Synchronization  
Generally, the most common problem is a mismatch in synchronization sources  
between the endpoint and the DEFINITY MMCH. This typically causes low-level  
(Px64) handshake problems that can trigger the endpoint/MMCH to disconnect  
the call. The MCCH’s timers are set to sufficiently high values so that, normally,  
the endpoint will timeout and disconnect first. If installed in a customer network, it  
is a good idea to perform an audit of the path synchronization is being supplied.  
If there are different clock sources between endpoints and the DEFINITY MMCH,  
some problems are sure to occur. The severity of these problems can range from  
a handshake failure every few seconds to one per day. Depending on the type of  
endpoint, this can cause the endpoint to disconnect or just freeze video until the  
main problem is resolved.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Troubleshooting Multimedia Call Handling (MMCH)  
1-138  
Specifically, PictureTel System 4000 endpoints seem to be the most sensitive to  
instability. The Lucent Technologies Vistium also disconnects fairly infrequently.  
Last, the CLI Rembrandt II VP freezes video and waits for framing to be  
recovered.  
Network Configuration Concerns with  
Synchronization  
When auditing a network for synchronization, avoid unnecessary hops. Thus, a  
switch providing star-configuration synchronization is preferred over a  
daisy-chain configuration. Additionally, if there are DEFINITY PBXs that have  
EPNs, synchronization should be provided to sub nodes from the same port  
network through which the PBX receives its synchronization. Passing  
synchronization through the PBX Expansion Interface adds an unnecessary hop  
to the path and creates another potential point of failure.  
Expansion Interface Duplication  
If a customer’s network uses PBX EPNs with duplicated Expansion Interfaces,  
scheduled switching of the Expansion Interface links should be disabled on the  
PBX via change system-parameters maintenance. When scheduled  
maintenance runs and switches the links, there is a brief corruption of the data  
path. If endpoints have active calls when the switch occurs, this corruption of the  
data path causes Px64 handshake problems, which lead to the endpoints losing  
video source status, and sometimes disconnecting as described above.  
Disabling the EI switching is in the customer’s best interest to prevent the  
disruption of the Px64 data stream. The customer will get the same level of alarm  
indications and maintenance on the EI links, regardless of the status of  
scheduled switching.  
PRI D-Channel Backup  
A somewhat unlikely source of call stability problems occur where the  
translations for PRI D-channel Backup between two non-MCU switches were  
incorrect. As an example, on switch A, DS1 1A10 was designated as the primary  
source, and on switch B, the corresponding DS1 was designated as the  
secondary source. When scheduled maintenance was run on the switch that had  
an active standby D-channel, an audit disconnected some calls using the link.  
The problem was corrected when the D-channel primary/secondary assignments  
matched.  
Processor Duplication on the PBX  
Do not enable the PI link switch on scheduled maintenance. This can cause link  
stability problems on the Accunet Bandwidth Controller (ABC).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Troubleshooting Multimedia Call Handling (MMCH)  
1-139  
Voice-Activated Switching Problems  
Voice-activated switching on the DEFINITY MMCH does not follow the loudest  
talker. The MMCH queues all speaking parties and selects a new video  
broadcaster (the second-oldest speaking party) when the oldest speaking party  
has stopped talking. The new broadcaster will see the last speaker as its video.  
The system can also “learn” about the noise coming from an endpoint to help  
prevent false switches, adapting both to noise level and repetitive sounds such  
as a fan. This adaptation occurs over approximately 10 seconds.  
No Switching, Full Motion Video  
If a room is excessively noisy, the DEFINITY MMCH may receive sufficient audio  
signal to conclude that there is a speaker present. Use the Status Conference x  
form to determine if the MMCH thinks an endpoint is talking. The MMCH sets the  
Tsfield to tfor each endpoint if there is voice energy detected. This endpoint  
may have to mute when nobody at the site is speaking to allow the conference to  
proceed normally. Remind the customer that it may be necessary to mute if a  
side conversation is going on in the background, just as one would do in an  
audio conference. If the system does not switch broadcasters even after the  
current broadcaster has muted, check the conference administration using the  
display conference X command to ensure that the conference is in  
voice-activated mode. Also verify that parties who were speaking are valid video  
sources as described in the “Calls Terminate with No Video” section above.  
The See-Me feature (MCV) can also cause VAS to “lock-up.” An endpoint can  
activate MCV to force their site to become the broadcaster. If they do not disable  
the feature when finished, the system remains in this mode indefinitely. Beginning  
with Release 3.0, the status conference X command shows that MCV is in effect  
by displaying avin the Video Status (Vs) column. Page 3 of the Status  
Conference X Endpoint Y form also has a Broadcasterfield that indicates MCV  
is in effect with (SEE-ME) as the broadcaster. The same scenario can occur in a  
CHAIR or UCC-controlled conference with a designated broadcaster. In this  
situation the CHAIR/UCC has not released the designated broadcaster and  
returned to VAS mode. If there is a UCC-designated broadcaster, status  
conference X indicates a Video Status of u. Also, for UCC rollcall the return  
video may appear to be stuck. Check the Video Status for an “R,” indicating  
rollcall.  
If none of the examples above appears to be the cause, and if the room was  
quiet, all speakers are valid video sources, the conference is voice-activated,  
and the speaker can be heard, then escalate the problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Troubleshooting Multimedia Call Handling (MMCH)  
1-140  
Video Never Switches to a Particular Party  
Description  
Verify that the endpoint is a valid video source as described in the “Calls  
Terminate with No Video” section above. If it is, then the audio from the endpoint  
may not have sufficient voice signal for the hardware to determine the parties at  
the endpoint are speaking. Check the Talkfield on page three of the Status  
Conference X Endpoint Y form to see if the talking bitis y. Next, check the  
audio by standing adjacent to the microphone and speaking at a normal level.  
Solution  
If the audio is not muffled:  
1. Use the status conference command to determine which port on the  
TN788B (VC board) is connected to this endpoint.  
2. Check the VC (TN788B) board using the test board xxyy long command.  
3. Drop the call.  
4. Find another available port, then:  
a. Busyout the port to which the endpoint was connected.  
b. Make another call to the same conference. If the problem corrects  
itself, then the previous port may be bad. If there are other VC  
boards with sufficient available ports to replace calls on the current  
VC, then pull the board that has the bad endpoint on it (the status  
conference command displays the encoder port associated with  
the call). The system will automatically reestablish the VC  
connections without dropping the call. If this fixes the problem, then  
replace the board, as it has at least one bad port. Reseating the  
board may temporarily fix the problem due to the hard reset done to  
the board.  
Audio Echo  
Echo in conference calls, particularly those with large delay characteristics, is  
totally disruptive. When Voice Activated Switching is taken into account, the  
effects are disastrous. Various arrangements of the microphone(s) and room  
speaker(s) may be needed.  
For some Lucent Technologies Vistium endpoints, if an external speaker is  
attached or was attached when the system was last rebooted, this endpoint will  
cause audio echo throughout the conference. First, isolate the offending  
endpoint by asking each endpoint to mute, one at a time, until the echo  
disappears.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Troubleshooting Multimedia Call Handling (MMCH)  
1-141  
If the input from an endpoint is located too close to the speakers of an endpoint,  
then acoustic echo is created. The microphone must be moved away from the  
speakers.  
Normally, if any microphone in the room is moved relative to the speakers, that  
site will cause echo until the echo canceller in the codec retrains itself, some will  
require a manual reset. If a PictureTel keypad is configured with external  
microphones connected to the keypad, then the internal microphone and  
external microphone(s) “sing” to each other if the “ext mic” bat switch is set to  
“int mic” on the back of the keypad. In this configuration, VAS locked on that site,  
and the acoustic “singing” was inaudible.  
Rate Adaptation  
Because of a lack of a clear explanation in standards, sometimes endpoints do  
not work well with each other and the DEFINITY MMCH. The MMCH will only  
allow a conference to downgrade from 64kbps to 56 kbps operation on  
conferences that have the Rate Adaptationflag set to y.  
When a downgrade does occur, information on the Status Conference form  
indicates the success or failure of the 64kbps-endpoints that are participants to  
properly rate adapt to 56kbps. As a general indication that the conference has  
rate adapted, the Conference Transfer Rateand Effective Transfer  
Ratefields show initial and current transfer rates, respectively. For each 64-kbps  
endpoint the column that indicates Rate Adaptshows an nif the endpoint did  
not follow the procedures as specified by the H.221. If an endpoint shows y, it did  
successfully rate adapt. If an endpoint shows c, it joined the conference at  
56kbps.  
Once the conference rate adapts, the endpoints that do not properly follow suit,  
will become audio-only endpoints. A conference will not rate adapt from 56 kbps  
back to 64 kbps until all endpoints disconnect from the conference and it idles.  
The PictureTel 1000 Release 1.1C, PictureTel 6.01 software, and the Vistium 2.0  
software successfully rate adapt with the MCU. External rate adaptation  
techniques used by VTEL and CLI are known to cause problems with the  
endpoint when used with this feature.  
Endpoint or I-MUX in Loopback Mode  
Some endpoints have a loopback enable feature. This makes DEFINITY MMCH  
data loopback at the MMCH when a connection is in progress. The loopback can  
be enabled prior to or during a connection.  
The MMCH does not detect the loop and continues to VAS. In most scenarios,  
the switch occurs, but within a few seconds, the broadcaster’s return video  
becomes its own image. Once the broadcaster stops speaking, the system  
“false” switches to an apparently random port that was not speaking.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance for csi systems  
1
Troubleshooting Multimedia Call Handling (MMCH)  
1-142  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
System Command Structure  
2-1  
Maintenance Commands  
2
This chapter provides additional trouble-clearing information for resolving both  
system-alarmed and user-reported troubles. This chapter supplements the  
information found in Chapter 3, ‘‘Maintenance Objects’’. The maintenance  
commands are used to control, test, and obtain information associated with  
maintenance objects (MOs). The commands require the use of the administration  
terminal or remote Initialization and Administration System (INADS) interface and  
a valid login and password.  
For Maintenance Objects and Maintenance Commands for the DEFINITY  
Wireless Business System (DWBS), refer to the appropriate maintenance  
documentation that accompanies the DWBS.  
System Command Structure  
System commands are standard words and phrases instructing the system to  
perform a specific function. The commands are arranged in a hierarchy of  
keywords; that is, enter 1 command to go to a different level. The commands  
contain 3 parts: ACTION, OBJECT, and QUALIFIER.  
■
ACTION is the first part of the command. When command:appears on the  
screen. The ACTION specifies the operation desired. Examples include  
add, duplicate, change, remove, display, list, and save.  
■
OBJECT is the second part of the command and specifies the particular  
object to be administered. Some typical entries are hunt-group,  
coverage path, and station.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout access-endpoint  
2
2-2  
■
QUALIFIER is the last part of the command. It is 1 or more words or digits  
used to further identify or complete the OBJECT. For example, hunt group  
15 or station 3600, where 15 and 3600 are qualifiers.  
NOTE:  
Qualifiers are printed in this typeface.  
An example of the command line required to add a station with extension number  
1234 is add station 1234. In this example, add is the ACTION, station is the  
OBJECT, and 1234 is the QUALIFIER. In the command line, spaces are required  
between the ACTION, OBJECT, and QUALIFIER.  
To save time, enter enough letters for each part of the command to make it  
unique. For example, if you want to enter the command change  
system-parameters country-options, typing cha sys coun is sufficient.  
NOTE:  
The craft login may not be allowed to perform some of the steps needed to  
initialize the system. If access is denied to some of these procedures,  
contact your Lucent Technologies representative for assistance.  
Getting Help  
Use the Help key for a list of options and the Cancel key to back out of any  
command.  
busyout access-endpoint  
This command is destructive. This command is used to busyout a specified  
access endpoint.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
busyout  
access-  
endpoint  
extension  
Extension number of access  
endpoint (per dial-plan)  
init  
none  
See below  
inads  
craft  
nms  
Examples:  
busyout access-endpoint 25012  
busyout access-endpoint 77868  
Feature Interactions  
■
If there is an active call on the specified access endpoint, the call to drop.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout board  
2
2-3  
Output  
The following example shows the output for the busyout access-endpoint  
22502 command and assumes that access endpoint ports for extension 22502  
are in cabinet 1, carrier C, slot 11, circuit 1 to 6. The responses display on a  
test-by-test basis with one line of data for each test result.  
busyout access-endpoint 22502  
COMMAND RESULTS  
Maintenance Name Alt. Name  
SPE A  
Port  
Result  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
Error Code  
01C1101  
01C1102  
01C1103  
01C1104  
01C1105  
01C1106  
WAE-PORT  
WAE-PORT  
WAE-PORT  
WAE-PORT  
WAE-PORT  
WAE-PORT  
22502  
22502  
22502  
22502  
22502  
22502  
Command Successfully Completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
Maintenance Name  
Name of maintenance object (WAE-PORT = wideband access  
endpoint; TIE-DS1 = single port access endpoint)  
Alt. Name  
The alternate way of identifying the maintenance object, in this  
case, the extension number of the access endpoint.  
Result  
Test result: Pass, Fail, Abort  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
busyout board  
This command puts all the ports associated with the specified access endpoint  
in a maintenance busy (craft busy) state. No periodic or scheduled tests are  
performed on the busied out access endpoint ports until they are released. When  
the access endpoint ports are maintenance busy, the access endpoint is  
removed from active service on the switch, meaning that no call processing  
activity can include the busied objects because terminals on the administered  
ports do not receive dial-tone. Warning alarms are generated on each busied out  
port in the access endpoint. The release access-endpoint command returns all  
the ports associated with the specified access endpoint to operation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout board  
2
2-4  
!
WARNING:  
This command is service disrupting and may cause extraneous alarms.  
Feature  
Action/Object  
busyout board  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
location  
Board address (PCSSpp)  
init  
none  
None  
inads  
craft  
Examples:  
busyout board 01c11  
busyout board 02c15  
Output  
The following example shows the output from the busyout board 1c07  
command, and assumes that board in cabinet 1, carrier c, slot 7 is an analog  
board with three administered ports. The responses display on a test-by-test  
basis with one line of data for each test result.  
busyout board 01C07  
SPE A  
COMMAND RESULTS  
Port  
01C07  
Maintenance Name Alt. Name  
ANL-BD  
Result  
PASS  
Error Code  
01C0702  
01C0701  
01C0703  
ANL-LINE  
ANL-LINE  
ANL-LINE  
PASS  
PASS  
PASS  
51001  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
The name of maintenance object  
Maintenance Name  
Alt. Name  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout cdr-link  
2
2-5  
Result  
Test result: Pass, Abort, or Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
busyout cdr-link  
This command will busyout a maintenance object associated with the specified  
call detail recording (cdr) link.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout  
cdr-link  
link-id  
Link identifier (primary or  
secondary)  
init  
inads  
craft  
Primary  
None  
Examples:  
busyout cdr-link primary  
busyout cdr-link secondary  
nms  
Output  
The following example shows the output from the busyout cdr-link primary  
command.  
busyout cdr-link primary  
SPE A  
COMMAND RESULTS  
Port  
1
Maintenance Name Alt. Name  
CDR-LNK  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit);  
1 = primary, 2 = secondary link  
Maintenance Name  
Alt. Name  
The name of maintenance object  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout data-module  
2
2-6  
Result  
Test result: Pass, Abort, or Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
busyout data-module  
This command puts the specified data module in a maintenance busy state, even  
uninstalled data modules. No periodic or scheduled tests is performed on the  
busied out data module or data channel until it is released and no call  
processing can be executed on the data modules or over the data channels.  
Warning alarms are generated (error type 18) on each maintenance object  
busied out, so that INADS can access the state of the objects. The release data  
module command returns the specified data module (or data channel) to  
operation.  
On a system with the duplication option, a busyout of a Network Control Data  
Channel (DATA-CHL) or a Processor Interface Port Data Channels (PI-PT) are  
preserved across SPE interchanges. The data channel extension must be  
released before the data channel can be brought back into service.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout  
data-module  
extension  
Extension number (per  
dial-plan)  
init  
None  
None  
inads  
craft  
nms  
Example:  
busyout data-module 31300  
Output  
The following example shows the output from the busyout data-module 300  
command.  
busyout data-module 300  
SPE A  
COMMAND RESULTS  
Port  
01C1103  
Maintenance Name Alt. Name  
DIG-LINE 300  
Result  
PASS  
Error Code  
Command successfully completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout journal-printer  
2
2-7  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit) or the data channel  
number  
Maintenance Name  
Alt. Name  
The name of maintenance object  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Result  
Test result: Pass, Abort, or Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
busyout journal-printer  
This command puts the maintenance object associated with a specified pms-log  
or wakeup-log link in a maintenance busy state. No periodic or scheduled tests  
are performed on the busied out maintenance object until it is released. Also, no  
activity occurs over the links (that is, no data transferred to the printer) and the  
link is dropped. Warning alarms are generated (error type 18) on each  
maintenance object busied out, so that INADS can access the state of the  
objects. The release journal-printer command returns the object to operation.  
A link is comprised of several components: a far end data module, a simulated  
data channel on the processor board, a manager that initiates and maintains the  
link, and a controller/protocol that services the link. A controller/protocol is  
usually a transient process that exists for as long as the link is up. A link is  
considered up if a physical connection is established. A link can be considered  
to be up while no useful work can be performed over it, in this case the link is  
insane and should be torn down. These links provide asynchronous data  
connections from the switch to peripherals.  
For general information on journal printer links, see the description of the  
‘‘busyout pms-link’’ command.  
For information on what a journal printer is and does, see the description of the  
‘‘status journal-link’’ command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout journal-printer  
2
2-8  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout  
journal-printer  
pms-log  
Link to pms (in output, port name for  
pms link =1)  
init  
None  
See below  
inads  
craft  
nms  
wakeup-  
log  
Link to the wakeup logging facility (in  
output, port name = 0)  
Examples:  
busyout journal-printer pms-log  
busyout journal-printer wakeup-log  
Feature Interactions  
Maintenance of a particular component on a link sometimes interferes with the  
maintenance of the link itself. For example, maintenance can put a link  
component in a busy state causing link set-up to fail. Frequent attempts at  
re-setup of a link may delay the recovery of a faulty component, due to the  
maintenance test of a component only taking place when the component is idle.  
Therefore, disable the attempted re-setup of a link with the busyout command  
and the link will remain intact. If the link is already down, the busyout command  
stops periodic re-setup attempts on the link.  
Output  
The following example shows the output for the busyout journal-printer  
wakeup-log command.  
busyout journal-printer wakeup-log  
COMMAND RESULTS  
SPE A  
Port  
0
Maintenance Name Alt. Name  
JRNL-LINK  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Physical object port address: 0= wakeup log, 1= pms log  
The name of the maintenance object  
Not applicable  
Maintenance Name  
Alt. Name  
Result  
Test result: Pass, Abort, Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout link  
2
2-9  
busyout link  
This places maintenance objects associated with a specified link in a  
maintenance busy state. No periodic or scheduled tests are performed on the  
busied out maintenance objects until they are released. The link is marked out of  
service and is inaccessible to call processing. Warning alarms (error type 18) are  
generated on each busied out maintenance object, so that INADS can determine  
the state of the objects. The release link command reactivates the objects.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout link  
link-id  
Processor Interface circuit pack  
init  
none  
none  
1a1 or 1b1 = 1 – 4  
inads  
craft  
Processor Interface circuit pack  
1a2 or 1b2 = 5 – 8  
Examples  
busyout link 1  
Output  
The following example shows the output from the busyout link 1 command. The  
responses display on a test-by-test basis with one line of data for each test result.  
busyout link 1  
SPE A  
COMMAND RESULTS  
Port  
01C0301  
Maintenance Name Alt. Name  
PI-LINK  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Port address/link-id  
Maintenance Name  
The name of the busied out maintenance object  
Not applicable  
Alt. Name  
Result  
Test result: Pass, Abort, Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout mis  
2
2-10  
busyout mis  
This command places a management information system in the maintenance  
busy state. No periodic or scheduled maintenance is performed on the busied  
out mis until it is released. When the object is busied out no call processing  
activity may be performed over the link. A warning alarm (error type 18) is  
generated on the busied out mis, so that INADS can determine its state. The  
command, release mis, reactivates the busied out mis.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout mis  
Example:  
init  
None  
None  
busyout mis  
inads  
craft  
cust  
rcust  
Output  
The following example shows the output from the busyout mis command. The  
responses display on a test-by-test basis with one line of data for each test result.  
busyout mis  
SPE A  
COMMAND RESULTS  
Port  
Maintenance Name Alt. Name  
MIS  
Result  
PASS  
Error Code  
Command Successfully Completed  
Field descriptions  
Port  
Not applicable  
Maintenance Name  
Name of busied out maintenance object: MIS  
Not applicable  
Alt. Name  
Result  
Test result: Pass, Abort, Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout pms-link  
2
2-11  
busyout pms-link  
This command places all maintenance objects associated with a property  
management system link in the maintenance busy state. No periodic or  
scheduled maintenance is performed on the busied out maintenance objects  
until they are released. When the object is maintenance busy the object is  
deactivated (no call processing activity may include the busied object) and the  
link is dropped. Warning alarms (error type 18) are generated on each busied out  
maintenance object, so that INADS can determine the state of the objects. The  
command, release pms link, reactivates the busied out objects on the link.  
These links provide asynchronous data connections from switches to  
peripherals; they are composed of a:  
■
■
■
■
Far-end data module  
Simulated data channel  
Manager that initiates and maintains the link  
Controller/protocol that services the link  
For information on PMS, see the description of the ‘‘status pms-link’’ command.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout  
pms-link  
Example:  
busyout pms-link  
init  
inads  
craft  
none  
See below  
Feature Interactions  
Maintenance of a particular component on a link sometimes interferes with the  
maintenance of the link itself. For example, maintenance can put a link  
component in a busy state causing link set-up to fail. Frequent attempts at  
re-setup of a link may delay the recovery of a faulty component, due to the  
maintenance test of a component only taking place when the component is idle.  
Therefore, disable the attempted re-setup of a link with the busyout command  
and the link will remain intact. If the link is already down, the busyout command  
stops periodic re-setup attempts on the link.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout port  
2
2-12  
Output  
The following example is a display of the busyout pms-link command.  
busyout pms-link  
SPE A  
COMMAND RESULTS  
Port  
Maintenance Name Alt. Name  
PMS-LINK  
Result  
PASS  
Error Code  
Command Successfully Completed  
Field descriptions  
Port  
Always blank  
Maintenance Name  
Name of maintenance object: PMS-LINK  
Not applicable.  
Alt. Name  
Result  
Test result: Pass, Abort, Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
busyout port  
This command places the specified port on a circuit pack in a maintenance busy  
state. No periodic or scheduled tests are performed on the busied out port until it  
is released. When the object is maintenance busy, it is deactivated (no call  
processing activity may include the busied object). Warning alarms (error type  
18) are generated on each busied out maintenance object, so that INADS can  
determine the state of the objects. The command, release port, reactivates the  
administered port on a circuit pack at a specified location.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout port  
location  
Port address: PCSS  
init  
none  
see below  
marked port: PPSSpp  
inads  
craft  
Examples:  
busyout port 01c1101  
busyout port 02c1501  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout pri-endpoint  
2
2-13  
Output  
The following example is a display of the busyout port command.  
busyout port 01C0701  
SPE A  
COMMAND RESULTS  
Port  
01C0701  
Maintenance Name Alt. Name  
ANL-LINE  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
Alt. Name  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO lineP/xxx (where xxx = private CO line group number)  
Type of busied out maintenance object.  
Maintenance Name  
Result  
Test result: Pass, Abort, Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
busyout pri-endpoint  
This command places all PRI endpoint ports (B-channels) associated with the  
specified PRI endpoint in a maintenance busy (system technician busy) state. No  
periodic or scheduled tests are performed on the busied out PRI endpoint ports  
until they are released. When the PRI endpoint port is maintenance busy it is  
deactivated (no call processing activity may include the busied object). Warning  
alarms (error type???) are generated on each busied out port. The command,  
release pri-endpoint, reactivates all ports (B-channels) associated with the  
specified PRI endpoint extension and the switch attempts to negotiate with the  
far-end PRI terminal adapter to reactivate each PRI endpoint port (B-channel).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout pri-endpoint  
2
2-14  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout  
pri-endpoint  
extension  
PRI endpoint  
extension number  
init  
none  
If active calls resides  
on specified PRI  
endpoints, the busyout  
command drops the  
call.  
inads  
craft  
nms  
Examples:  
busyout pri-endpoint  
25012  
busyout pri-endpoint  
77868  
Once the PRI endpoint  
is maintenance-busy,  
call attempts from  
far-end PRI terminal  
adapters are denied  
with a cause value 17.  
Output  
busyout pri-endpoint 22501  
SPE A  
COMMAND RESULTS  
Maintenance Name Alt. Name Result  
Port  
Error Code  
01B2001  
01B2002  
01B2003  
01B2004  
01B2005  
01B2006  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
22501  
22501  
22501  
22501  
22501  
22501  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
Type of busied out maintenance object: PE-BCHL  
Extension number of PRI endpoint  
Maintenance Name  
Alt. Name  
Result  
Test result: Pass, Fail, Abort  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout sp-link  
2
2-15  
busyout sp-link  
This command places the system printer link into a maintenance busy state. No  
periodic or scheduled maintenance is performed on the busied out system  
printer link until it is released. Warning alarms (error type 18) are generated on  
each busied out maintenance object, so that INADS can determine the state of  
the object. Placing the system printer link in a busyout state blocks access to the  
system printer. The release sp-link command reactivates the system printer link.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout  
sp-link  
Examples:  
busyout sp-link  
init  
inads  
craft  
none  
none  
Output  
busyout sp-link  
SPE A  
COMMAND RESULTS  
Port  
Maintenance Name Alt. Name  
SYS-PRNT  
Result  
PASS  
Error Code  
Command Successfully Completed  
Field descriptions  
Port  
Not applicable  
Maintenance Name  
Type of maintenance object that is busied out: SYS-PRNT  
Not applicable  
Alt. Name  
Result  
Test result: Pass, Abort, Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
busyout station  
This command places the installed and uninstalled administered voice terminal  
extension (station) in a maintenance busy state. No periodic or scheduled tests  
are performed on the busied out station until it is released. When the object is  
maintenance busy it is deactivated (no call processing activity may include the  
busied object). Warning alarms (error type 18) are generated on each busied out  
maintenance object, so that INADS can determine the state of the objects. The  
command, reDleoawsnleoasdtfarotmioWnw, wre.Saocmtaivnauatelss.cotmhe. AsllpMeacnuifaielsdSevaorcihceAntdeDrmowinnlaoalde.xtension.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout tdm  
2
2-16  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout  
station  
extension  
Extension number (per  
dial-plan)  
init  
inads  
craft  
none  
none  
Examples:  
busyout station 10020  
busyout station 32770  
Output  
The following example is a display of the busyout station command.  
busyout station 1002  
SPE A  
COMMAND RESULTS  
Port  
01C1102  
Maintenance Name Alt. Name  
DIG-LINE  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
Type of busied out maintenance object  
Maintenance Name  
Alt. Name  
Alternate means to identify maintenance object: extension  
number  
Result  
Test result: Pass, Fail, Abort  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
busyout tdm  
The busyout tdm command places the specified tdm bus in a maintenance  
busy state. No periodic or scheduled tests are performed on the busied out bus  
until it is released. When the object is maintenance busy it is deactivated (no call  
processing activity may include the busied object). Warning alarms (error type  
18) are generated on each busied out tdm bus, so that INADS can determine the  
state of the objects. The command, release tdm, reactivates the specified tdm  
bus.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout tone-clock  
2
2-17  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout tdm  
pn  
number  
pn number = TDM bus Port  
Network number to be busied  
out.  
init  
inads  
craft  
none  
If a bus is busied  
out, no calls are  
torn down. and  
no new calls are  
set up.  
bus  
bus = a (default control bus) or b  
(default tone bus) specifies  
desired half of TDM bus. Each  
512 time slot TDM bus  
configures as two duplicate 256  
time slot buses. This division  
allows duplication of control  
channels and dedicated tone  
time slots.  
Dedicated tone  
time slots must  
be moved to  
another bus (the  
other half of the  
duplicated bus)  
before a busyout  
of a particular  
bus is allowed.  
Examples:  
busyout tdm 1a  
Output  
The following example is a display of the busyout tdm command.  
busyout tdm port-network 1 bus a  
COMMAND RESULTS  
SPE A  
Port  
PN 01A TDM-BUS  
Maintenance Name Alt. Name  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Port address and associated TDM number and bus (PNA or PNB)  
Not applicable  
Alt. Name  
Maintenance Name  
Result  
Type of busied out maintenance object: TDM-BUS  
Test result: Pass, Abort, Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
busyout tone-clock  
The busyout tone-clock command places the specified tone/clock in a  
maintenance busy state. No periodic or scheduled tests are performed on the  
busied out object until it is released. When the object is maintenance busy it is  
deactivated (no call processing activity may include the busied object). Warning  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout trunk  
2
2-18  
alarms (error type 18) are generated on each tone clock circuit pack busied out,  
so that INADS can determine the state of the objects. The command, release  
tone-clock, reactivates the specified tone/clock.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout  
location  
Physical location (PCC)  
init  
1 (one)  
none  
tone-clock  
inads  
craft  
Examples:  
busyout tone-clock 01c  
busyout tone-clock 03d  
Output  
The following example is a display of the busyout tone-clock command.  
busyout tone-clock 1a  
SPE A  
COMMAND RESULTS  
Port  
Maintenance Name Alt. Name  
Result  
PASS  
PASS  
Error Code  
01A  
01A  
01A  
TONE-PT  
TDM-CLK  
TONE-BD  
PASS  
Command successfully completed  
Field descriptions  
Port  
Tone/clock board address (cabinet-carrier)  
Circuit pack name: TONE-PT, TDM-CLK, TONE-BD  
Not applicable  
Maintenance Name  
Alt. name  
Result  
Test result: Pass, Abort, Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer to  
the detailed list of the codes by test number for each MO.  
busyout trunk  
The busyout trunk command places the specified installed or uninstalled trunk  
group or trunk group member in a maintenance busy state. No periodic or  
scheduled tests are performed on the busied out trunk groups or trunk group  
members until they are released. When the object is maintenance busy it is  
deactivated (no call processing activity may include the busied object). A single  
group member can be busied out by specifying the group and member number.  
All members in a trunk group can be busied out by specifying the trunk group  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
busyout trunk  
2
2-19  
number. Warning alarms (error type 18) are generated on each busied out  
maintenance object, so that INADS can access the state of the objects. The  
release trunk command reactivates the specified trunk group or group member.  
NOTE:  
If the user enters busyout trunk <group number>/, the lowest  
port-location in the group is busied out. This s NOT recommended.  
Feature  
Action/Object  
Qualifier  
group  
Qualifier Description  
Permissions  
Defaults  
Interactions  
busyout trunk  
Trunk group number (1–99)  
init  
none  
none  
inads  
craft  
member  
Number of a particular trunk within  
a trunk group (1 – 99)  
Examples:  
busyout trunk 78  
busyout trunk 78/1  
Output  
The following example is a display of the busyout trunk command.  
busyout trunk 78/1  
SPE A  
COMMAND RESULTS  
Port  
01C1505  
Maintenance Name Alt. Name  
CO-TRK 78/01  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
Type of busied out maintenance object.  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
Maintenance Name  
Alt. Name  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
cancel hardware-group  
2
2-20  
Result  
Test result: Pass, Abort, Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
cancel hardware-group  
This command temporarily or permanently aborts the execution of a test  
hardware-group command. To resume testing, enter resume hardware-group  
or test hardware-group.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
cancel  
Examples:  
init  
none  
See below  
hardware-group  
cancel hardware-group  
inads  
Feature Interactions  
Scheduled and Periodic Maintenance  
■
When a test hardware-group is entered, all activity related to scheduled  
background maintenance, periodic background maintenance, and data  
audits suspends for the duration of the test hardware-group command.  
All activity related to scheduled background maintenance, periodic  
background maintenance, and data audits restarts if the test  
hardware-group command is canceled.  
■
Status Hardware-group  
The status hardware-group command displays the state of a canceled  
test hardware-group command as canceled.  
change circuit-packs  
This command allows users to administer circuit packs that are inserted into the  
system port, expansion control, and switch node carriers. It is used to configure  
the system when circuit packs are not physically inserted.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
change  
circuit-packs  
cabinet  
number  
Cabinet number of circuit packs to  
change  
init  
1 (one)  
none  
inads  
craft  
cust  
nms  
Examples:  
change circuit-packs 1  
change circuit-packs 2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
change circuit-packs  
2
2-21  
Output  
The following example is a display of page 1 of the change circuit-packs 1  
command when DEFINITY AUDIX is Administered by entering TN566 in slot 8.  
change circuit-packs 1  
Page  
1 of  
5
CIRCUIT PACKS  
Cabinet: 1  
Carrier: A  
Carrier Type: processor  
Slot Code Sfx Name  
Slot Code Sfx Name  
01: TN798  
02: TN2182  
03:  
04:  
05:  
06: ADX8D  
07: ADX8D  
08: TN566  
09: ADX8D  
10:  
PROCESSOR  
TONE/CLOCK  
11:  
12:  
13:  
14:  
15:  
16:  
17:  
18:  
19:  
20:  
RESERVED-AUDIX-8D  
RESERVED-AUDIX-8D  
MULTI-FUNCTION  
RESERVED-AUDIX-8D  
’#’ indicates circuit pack conflict.  
If TN566 is entered for slot 8 and any of the 2 slots before it or 1 slot after it are  
occupied, the following error message displays:  
Remove installed equipment from reserved 2 previous and 1  
next slots  
The following is an example of page 1 of the change circuit-packs form when  
MAPD is administered by entering TN800, TN801, or TN802 in slot 7.  
change circuit-packs 1  
Page  
1 of  
5
CIRCUIT PACKS  
Cabinet: 1  
Carrier: A  
Carrier Type: processor  
Slot Code Sfx Name  
Slot Code Sfx Name  
01: TN798  
02: TN2182  
03:  
04:  
05:  
06: ADX8D  
07: TN800  
08: TN769  
09: TN769  
10: TN769  
PROCESSOR  
TONE/CLOCK  
11:  
12:  
13:  
14:  
15:  
16:  
17:  
18:  
19:  
20:  
RESERVED-AUDIX-/CON  
MAPD  
ANALOG LINE  
ANALOG LINE  
ANALOG LINE  
’#’ indicates circuit pack conflict.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
change synchronization  
2
2-22  
Field descriptions  
Cabinet  
Administered cabinet number  
Cabinet Layout  
Type of cabinet (single-carrier)  
Carrier  
Carrier Type  
Slot  
In-use cabinet carrier  
Carrier function (port, processor, or expansion control)  
Slot numbers (0 - 21).  
Code  
Circuit pack code (TN number) to identify the circuit pack type  
Lists the suffix, if applicable  
Sfx  
Name  
Alphanumeric circuit pack name  
change synchronization  
Each system contains a hierarchy of sources used for timing synchronization.  
DS1 inputs to the external stratum 3 clock affect stratum 3 synchronization  
hierarchy. Primary and secondary fields reflect Stratum 4 synchronization. If all  
fields are blank, the tone clock board within each PN provides timing for that PN.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
change  
synchronization  
Examples:  
change  
synchronization  
change synch  
init  
none  
DS1 interface, BRI  
trunk, or UDS1 board  
selected as either a  
primary or secondary  
synch source cannot  
be removed on the DS1  
circuit pack  
inads  
craft  
cust  
rcust  
bcms  
administration form or  
the regular circuit pack  
administration form.  
Output/Input  
The following example shows the output for the change synchronization  
command. “4” was entered in the stratum field.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
change synchronization  
2
2-23  
change synchronization  
Page  
1 of  
1
SYNCHRONIZATION PLAN  
SYNCHRONIZATION SOURCE (circuit pack location)  
Stratum: 4  
Primary: _____  
Location Name Slip  
Secondary: _____  
Location Name  
Slip  
NOTE: DS1 and BRI trunk sources will result in stratum 4, type II  
synchronization  
The following example shows the output for the change synchronization  
command. “3” was entered in the stratum field.  
change synchronization  
SYNCHRONIZATION PLAN  
Page  
1 of  
1
SYNCHRONIZATION SOURCE (DS1 circuit pack location)  
Stratum: 3  
Port Network: 1  
Field descriptions  
Stratum:  
Primary:  
Current synchronization stratum (3, 4)  
First choice system synchronization source (blank entry = no  
synchronization); field valid only if stratum 4 synchronization is  
specified.  
Secondary:  
Location:  
Name:  
Second choice system synchronization source (blank = no  
synchronization); valid if stratum 4 synchronization selected  
Circuit pack location of all administered DS1 circuit packs (port  
network, carrier and board slot)  
User-defined name for the DS1 circuit pack (blank = no user-defined  
name assigned)  
Slip:  
If DS1 circuit pack has slip alarm, y; if not, n.  
Port  
Network:  
Display-only field specifying the port network that supplies  
synchronization through the tone clock circuit pack (valid for stratum 3  
synchronization)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters customer-options  
2-24  
change system-parameters  
customer-options  
The init password is required to change any administration of the Customer  
Options form. Access Security Gateway challenges all init passwords.  
Feature  
Action/ Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
change  
Example:  
init  
none  
none  
system-parameters  
customer-options  
change system-parameters  
customer-options  
inads  
craft  
Output  
The following example shows the output from the change system-parameters  
customer-options command.  
Page  
2 of  
5
OPTIONAL FEATURES  
ISDN Feature Plus? n  
ISDN-BRI Trunks? n  
ISDN-PRI? n  
Restrict Call Forward Off Net? n  
Secondary Data Module? y  
Station and Trunk MSP? n  
Tenant Partitioning? n  
Malicious Call Trace? n  
Mode Code Interface? n  
Terminal Trans. Init. (TTI)? n  
Time of Day Routing? n  
Multifrequency Signaling? y  
Uniform Dialing Plan? n  
Multimedia Appl. Server Interface (MASI)? n  
Multimedia Call Handling (Basic)? n  
Multimedia Call Handling (Enhanced)? n  
Personal Station Access (PSA)? n  
PNC Duplicaton? n  
Usage Allocation Enhancements? n  
Wideband Switching? n  
Wireless? n  
Processor and System MSP? n  
Private Networking?n  
Screen 2-1. Customer Options form (page 2 of 5)  
change system-parameters  
maintenance  
This command specifies and displays scheduled maintenance operations and  
maintenance support functions. It also activates and deactivates INADS alarm  
origination during repairs. To deactivate alarm origination:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters maintenance  
2-25  
1. Make a note of the current entries in the Alarm Origination and CPE Alarm  
fields so you can restore them later.  
2. Change the Alarm Origination to OSS Numbersfield to neither.  
3. Change the CPE Alarm Activation Levelfield to none.  
4. If daily scheduled maintenance must remain idle during a maintenance  
procedure, set the Start Timefield to a time after the session ends. If  
daily Scheduled Maintenance is running and needs to be deactivated, set  
the Stop Time field to one minute after the current time.  
5. Press Enter and verify that the screen displays the message:  
Command successfully completed  
NOTE:  
For earlier releases of system software, disable Cleared Alarm  
Notification and Restart Notification before submitting the form.  
NOTE:  
When finished working on the switch be sure to return all fields to  
their original settings.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
change  
Examples:  
init  
none  
none  
system-parameters  
maintenance  
change system-parameters  
maintenance  
inads  
craft  
cust  
rcust  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters maintenance  
2-26  
Output (Page One)  
The following output example shows a display of Page 1 of the change  
system-parameters maintenance command.  
change system-parameters maintenance  
MAINTENANCE-RELATED SYSTEM PARAMETERS  
Page  
1 of 3  
OPERATIONS SUPPORT PARAMETERS  
Product Identification: 1000000000  
First OSS Telephone Number: 5551212  
Second OSS Telephone Number: 5551213  
Alarm Origination to OSS Numbers: both  
Cleared Alarm Notification? y  
Restart Notification? y  
Abbrev Alarm Report? y  
Abbrev Alarm Report? n  
Suspension Threshold: 5_  
Test Remote Access Port? n  
CPE Alarm Activation Level: none  
Packet Bus Activated? n  
Customer Access to INADS Port? n  
Repeat Dial Interval (mins): 7  
SCHEDULED MAINTENANCE  
Start Time: 22: 00  
Stop Time: 04: 00  
Daily Maintenance: daily  
Save Translation: daily  
Command Time-out (hours): 2  
System Clocks Interchange: no  
EXP-LINK Interchange: no  
Control Channel Interchange: no  
SPE Interchange: no  
Field Descriptions (Page One)  
Operations Support Parameters  
Product  
Identification  
Identifies switch to an Operations Support System (OSS): 10-digit  
number starting with 1.  
First OSS  
Telephone  
Number  
Switch reports alarms first to the First OSS telephone number (for  
example, INADS or Trouble Tracker). The number must be obtained  
from the National Customer Support Center (NCSC) or the TSC. (#  
and * are not allowed in the telephone number.)  
Abbrev Alarm  
Report  
Enables the Abbreviated Alarm Report feature for the first OSS. (yes)  
Second OSS  
Telephone  
Number  
The switch reports alarms secondly to the second OSS telephone  
number. For example, INADS or DEFINITY SNMP. The number must  
be obtained from the National Customer Support Center (NCSC) or  
the TSC. (# and * are not allowed in the telephone number.)  
Abbrev Alarm  
Report  
Enables the Abbreviated Alarm Report feature for the second OSS.  
(no)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters maintenance  
2-27  
Alarm  
Origination to  
OSS Numbers  
Indicates one of four options for alarm origination (neither):  
both= Major and Minor alarms result in an automatic call to both  
administered OSS telephone numbers.  
first-only= Major and Minor alarms result in an automatic call to  
the first administered OSS number.  
neither= alarm origination does not occur; reports are not sent to  
either number.  
second no-backup= Major and Minor alarms result in an  
automatic call to the first administered OSS telephone number. If  
calling the first OSS telephone number fails four times, the switch  
calls the second administered OSS telephone number until calling  
the first OSS telephone number is successful.  
If Alarm Origination is deactivated, Cleared Alarm Notification and  
Restart Notification deactivate, even though they may still be activate  
in the administration.  
Cleared Alarm  
Notification  
The switch originates calls to the OSS and sends an alarm resolution  
message once all previously-reported Major and Minor alarms are  
resolved. Activate Alarm Origination to enable Cleared Alarm  
Notification. (no)  
Restart  
Notification  
Enables the switch to originate calls to the OSS and report any  
system restarts caused by switch problems. Activate Alarm  
Origination to enable Restart Notification.  
Suspension  
Threshold  
Some problems cause alarms to be generated and resolved  
repeatedly. To detect these problems, the switch suspends Cleared  
Alarm Notification when it has reported the specified number of  
Cleared Alarm notifications in a 24 hour period. A suspended  
Cleared Alarm Notification reactivates with a successfully-completed  
“logoff” command, a system reset, or when the threshold is  
changed. This field is irrelevant if Cleared Alarm Notification  
or Alarm Originationare disabled. (1–15)  
Test Remote  
Access Port  
Indicates if remote access testing on the SYSAM circuit pack is  
active. This field should be set to yes when an INADS line is  
connected to the switch and a maintenance contract is in effect to  
maintain alarm origination capability.  
If no equipment is connected to the remote access port, or if a trunk  
for remote access and alarm origination is not provided, running tests  
on the remote access port on the SYSAM results in test failures. This  
causes unnecessary maintenance alarms and allows potentially  
destructive tests to be run. To prevent this, set this field to no.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters maintenance  
2-28  
CPE Alarm  
Activation  
Level  
Indicates the minimum level (Major, Minor or Warning) to activate  
Customer-Provided Equipment (CPE) alarm. If the level is none, the  
CPE does not activate for any alarm.  
NOTE:  
When the switch goes into Emergency Transfer, the CPE alarm  
activates regardless of the CPE Alarm Activation Level setting.  
Packet Bus  
Activated  
If this field is set to yes, maintenance software assumes that a  
Packet Control circuit pack is installed. If packet endpoints (for  
example, ASAI, and/or BRI) are administered, and maintenance  
testing runs on both the Packet Control circuit pack and Packet Bus,  
set this field to yes after a packet control circuit pack is installed. If a  
Packet Control circuit pack is not installed in the system, a major  
alarm is raised against the PKT-CTRL MO.  
Change this field to no if no packet endpoints are administered, to  
ensure that no packet endpoints can be administered if the packet  
bus deactivated.  
If a Packet Control circuit pack is not installed, then this field should  
be set to no (the only exception is system translations that do not  
have all required hardware).  
CustomerAccess  
to INADS Port  
To prevent customer login ID access to system administration and  
maintenance interface control, set this field to no. Lucent  
Technologies services has sole access to this field.  
Repeat Dial  
Interval (MMS)  
Number of minutes that the system must wait before attempting  
another call origination to an OSS. Lack of a far-end  
acknowledgment triggers the timer.  
Scheduled Maintenance  
Start Time  
Hour and minute (24-hour notation) when daily scheduled maintenance  
starts  
Stop Time  
The hour and minute when scheduled daily maintenance ceases. If any  
daily maintenance operations are not completed by this time, the  
system notes its stopped sequence location and includes those  
operations during the next scheduled daily maintenance.  
Daily  
Maintenance  
This display-only field lists the standard test series run by maintenance  
software during daily maintenance.  
Save  
Translation  
Indicates days that translation data in memory automatically saves to  
the Mass Storage System disk and/or tape devices during scheduled  
maintenance. The operation saves to disk, then completes a backup to  
tape. Translation data saves to both SPEs, if systems have duplicated  
SPEs. (daily, days of the week, or no - prevents automatic saves)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters maintenance  
2-29  
Control  
Channel  
Interchange  
Each port network has a pair of TDM busses (A and B). Each has a set  
of time slots dedicated to the control channel. One bus at a time carries  
the control channel in each PN. (daily, days of the week, or no -  
prevents interchanges). (no)  
SystemClocks  
Interchange  
For High and Critical Reliability systems, this option initiates a  
Tone-Clock interchange in each port network possessing duplicated  
Tone-Clock circuit packs. Each port network interchanges into the  
standby Tone-Clock for 20 seconds and then back to the  
originally-active Tone-Clock. This field indicates the days that  
interchanges occur. (daily, days of the week, or no). “No” prevents  
interchanges. (no)  
The system performs a Tone-Clock interchange, activating the stand by  
Tone-Clock. After the newly-active Tone-Clock circuit pack is tested, it  
provides system clocks for its native port network. Then the system  
interchanges to the originally active Tone-Clock circuit pack.  
SPE  
Interchange  
This field indicates the days SPE interchanges execute during  
scheduled maintenance, for duplicated SPE systems. (daily, days of  
the week, or no). No prevents scheduled interchanges. (no)  
EXP-LINK  
Interchange  
This field indicates if expansion links between port-networks  
interchange as part of scheduled maintenance. The value daily  
means that EXP-LINK interchanges automatically occur everyday. The  
value no means that EXP-LINK interchanges do not automatically  
occur as part of scheduled maintenance. Values represented by the  
days of the week mean that EXP-LINK interchanges automatically  
occur automatically on specified days. Since EXP-LINK interchanges  
apply to duplicated systems, simplex systems do not display this field.  
(no)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters maintenance  
2-30  
Output (Page Two)  
The following example shows the output from page 2 of the change  
system-parameters maintenance command.  
change system-parameters maintenance  
Page 2 of 3  
MAINTENANCE-RELATED SYSTEM PARAMETERS  
MINIMUM MAINTENANCE THRESHOLDS ( Before Notification )  
TTRs: 4  
MMIs: 0  
CPTRs: 2  
VCs: 0  
Call Classifier Ports: _  
TERMINATING TRUNK TRANSMISSION TEST (Extension)  
Test Type 100:  
Test Type 102:  
Test Type 105:  
ISDN MAINTENANCE  
ISDN-PRI TEST CALL Extension: _____  
ISDN BRI Service SPID: _____  
DS1 MAINTENANCE  
DSO Loop-Around Test Call Extension: ____  
SPE OPTIONAL BOARDS  
Packet Intf1? y  
Packet Intf2? n  
Packet Intf3? n  
Bus Bridge:____ Inter-Board Link Timeslots Pt0:_ Pt1:_ Pt2:_  
Field Descriptions (Page Two)  
Minimum Maintenance Thresholds (Before Notification)  
TTRs  
When the number of touch tone receivers (TTRs) in service falls  
below this number (4 to 200), a WARNING alarm is raised against  
TTR-LEV. These are also known as dual-tone multifrequency  
receivers (DTMRs). There are 4 TTRs on each TN748, TN718,  
TN420, or TN756; TN2182 and TN744 (suffix C or later) each  
have 8 TTRs. To alarm the first occurrence of a TTR being taken  
out of service, set this field to the total number of TTRs in the  
switch.  
CPTRs  
When the number of call progress tone receivers in service falls  
below this number (2 to 100), a WARNING alarm is raised against  
TTR-LEV. These are also known as general purpose tone  
detectors (GPTDs). There are 2 CPTRs on each TN748, TN718,  
TN420, or TN756; TN2182 and TN744 (suffix C or later) each  
have 8 CPTRs. To alarm the first occurrence of a CPTR being  
taken out of service, set this field to the total number of CPTRs in  
the switch.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters maintenance  
2-31  
Call Classifier  
Ports  
When the number of call classifier ports (CLSFY-PTs) in service  
falls below this number, a WARNING alarm is raised against  
TTR-LEV. Valid entries are 1 to 200. There are 8 ports on each  
TN744 or TN2182 circuit pack. To alarm the first occurrence of a  
CLSFY-PT being taken out of service, set this field to the total  
number of CLSFY-PTs. If there are no TN744 or TN2182 circuit  
packs in the system, leave this field blank.  
MMIs  
The MMIs field contains the minimum number of MMI ports  
needed for the Multimedia Call Handling (MMCH) feature to run  
efficiently. The MMCH feature must be enabled on the  
System-Parameters Customer-Options form before the MMIs field  
can be changed to a number greater than zero. If the number of  
in-service Multimedia Interface (MMI) ports falls below the  
minimum port capacity (valid entries between 0-128), a MMI-LEV  
error is logged. Each MMI circuit pack contains a maximum of 32  
ports. To alarm the first occurrence of an MMI being taken out of  
service, set this field to the total number of MMI ports. If this  
outage continues for 15 minutes, a MAJOR alarm is raised.  
VCs  
The VCs field contains the minimum number of VC ports needed  
for the Multimedia Call Handling (MMCH) feature. The MMCH  
feature must be enabled on the System-Parameters  
Customer-Options form before the VCs field can be changed to a  
number greater than 0. Each VC circuit pack contains 16  
physical ports: 8 ports are reserved for VC-DSPPT ports, and the  
remaining 8 ports are designated as VC-SUMPT ports. The 8  
DSP ports are made up of 4 encoder and 4 decoder resources  
that encode and decode audio formats. Thus, one VC circuit  
pack is required for every 8 ports of MMCH port capacity. If the  
number of in-service VC ports falls below the MMCH port  
capacity (valid entries between 0 and 128), a VEC-LEV error is  
logged. To alarm the first occurrence of a VC port being taken  
out of service, set this field to the total number of VC ports. If this  
outage continues for 15 minutes a MAJOR alarm is raised.  
Terminating Trunk Transmission Test (Extension)  
Test Type 100  
This field specifies extensions assigned to receive tie-trunk calls  
from other switches that have test line origination capability. The  
system responds by sending a sequence of test tones. Test Type  
100 tests far end to near end loss and C-message by sending:  
■ 5.5 seconds of 1004 Hz tone at 0 dB  
■ Quiet until disconnect; disconnect is forced after one minute  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters maintenance  
2-32  
Test Type 102  
Test Type 102 tests far end to near end loss by sending:  
■ 9 seconds of 1004 Hz tone at 0 dB  
■ 1 second of quiet  
■ This cycle is repeated until disconnect; disconnect is forced  
after 24 hours.  
Test Type 105  
Test Type 105 tests 2-way loss, gain slope, and C-message and  
C-notch noise by sending:  
■ nine seconds of 1004 Hz at -16 dB  
■ one second of quiet  
■ nine seconds of 404 Hz at -16 dB  
■ one second of quiet  
■ nine seconds of 2804 Hz at -16 dB  
■ 30 seconds of quiet  
■ one-half second of Test Progress Tone (2225 Hz)  
■ approximately five seconds of quiet  
■ forced disconnect  
ISDN Maintenance  
ISDN-PRI Test  
Call Extension  
This field indicates the extension used by far-end ISDN nodes to  
place calls to the system, for testing ISDN-PRI trunks between  
the far-end and the system.  
ISDN-BRI Service  
SPID  
This field shows if the link associates with the Service SPID. If the  
link is associated with the Service SPID. This number is the test  
SPID (0 – 99999) (under BRI-SET MO). Otherwise, this field is  
blank. Service SPID is a feature used by the system technician to  
check building wiring between the switch and the BRI endpoint.  
DS1 Maintenance  
DSO Loop-Around  
Test Call  
Extension  
The extension used to set up a DSO loop around connection for  
testing non-ISDN DS1 trunks. The DSO Loop-Around Test Call  
feature is used primarily for testing DSO channels associated  
with non ISDN-PRI trunks. The loop-around is activated by dialing  
the test extension number; multiple DSO Loop-Around  
connections can be established by placing multiple calls to the  
loop-around extension.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters maintenance  
2-33  
SPE Optional Boards  
Packet Intfl?  
These fields indicate if a Disk circuit pack is present, and identify  
administered Packet Interface slots. If a Packet Interface circuit  
pack is present, the corresponding Packet Interface field is set to  
y when the system boots. No change to that field is allowed. If the  
system is equipped with duplicated SPEs, the Packet  
Interfacefield is set to y if either SPE carrier contains a Packet  
Interface circuit pack in the corresponding position. If a Packet  
Interface circuit pack is not present, the value for the Packet  
Interfacefield is read from translation data, and stored on disk  
or tape. If the field is set to n, a Packet Interface circuit pack may  
be administered by changing the corresponding Packet  
Interfacefield to y.  
This field identifies the presence of Packet Interface 1  
(always set to y for csi and si models).  
Packet Intf2?  
This field identifies the presence of Packet Interface 2  
(always set to y for the si model). It is changeable for the csi  
model. If set to y for the csi model, the Bus Bridgeand  
Inter-Board Link Timeslotsfields display. Default is n.  
Packet Intf3?  
Bus Bridge  
This field identifies the presence of Packet Interface 3  
(Unavailable in the si and csi models). It is changeable in the r  
model. Default is n.  
(If Packet Intf2set to y) This field gives the location of the  
C-LAN circuit pack performing the bus bridge functionality when  
the packet bus is activated. Enter the 5-character circuit pack  
number (CCcss, where CC = cabinet number 1-3, c = carrier  
A-E, ss = slot number 0-20). Default is blank.  
Inter-Board Link  
Timeslot Pt0  
The number of timeslots to be used for port 0 on the Inter-Board  
Link. Displays only if the switch model type is csi and the Packet  
Intf2field is y. Enter the number of timeslots (1-9) to be used by  
this Inter-Board Link port. Default is 6.  
Inter-Board Link  
Timeslot Pt1  
The number of timeslots to be used for port 1 on the Inter-Board  
Link. Displays only if switch model type is csi and the Packet  
Intf2field is y. Enter the number of timeslots (1-3) to be used by  
this Inter-Board Link port. Default is 1.  
Inter-Board Link  
Timeslot Pt2  
The number of timeslots to be used for port 2 on the Inter-Board  
Link. Displays only if switch model type is csi and the Packet  
Intf2field is y. Enter the number of timeslots (1-3) to be used by  
this Inter-Board Link port. Default is 1.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters maintenance  
2-34  
Output (Page Three)  
The following example shows the output from page 3 of the change  
system-parameters maintenance command.  
change system-parameters maintenance  
MAINTENANCE-RELATED SYSTEM PARAMETERS  
Page 3 of 3  
Modem Connection: external  
Data Bits: 8  
Parity: none  
Modem Name: _______  
RTS/CTS Enabled: \Q3  
Asynchronous Data Mode: &M0&Q0  
DTE Auto-Data Speed: ______  
Disable Data Compression: ______  
Enable Error Control: ______  
Auto Answer Ring Count (rings): S0=10  
Dial Type: T  
Adjustable Make/Break Ratio:  
Dial Command: D  
No Answer Time-out: S7=255  
Misc. Init. Param: ______________  
Help/Error Message Line  
Field descriptions (Page Three)  
Modem Connection  
On page 3 of the example forms, 11 fields disappear when the Modem  
Connection?field is set to internal. In this example the Modem Connection  
field is set to external, revealing the 11 fields.  
The first 2 fields on page 3 establish the data format for transmitting serial data  
from the switch to the modem. The two valid combinations for these 2 fields are:  
■
Data Bits = 8, Parity = None  
■
Data Bits = 7, Parity = (odd, even, mark, or space)  
Modem Connection  
Modem Name  
Valid entries are internal(default) or external.  
This field is 20 characters long and will permit alpha-numeric  
characters to provide a unique qualifier for a given modem. ( )  
RTS/CTS Enabled  
This field will inform the modem that communication with the data  
source UART will be driven with RTS/CTS flow control. This field is  
6 characters long and is case in-sensitive. (\Q3)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
change system-parameters maintenance  
2-35  
Asynchronous  
Data Mode  
This field will configure the modem as an asynchronous  
communications device. This field is 8 characters long and is  
case in-sensitive. (&M0&Q0)  
DTE Auto-Data  
Speed  
This option will adjust the speed of the data source (DTE) UART to  
the outgoing (modem-to-modem) data rate. So, at maximum this  
speed would be 9600 baud. This field is 6 characters long and is  
case in-sensitive.  
Note that this field sets the link speed between the switch and the  
modem. It does not set the speed of the modem. It is not  
desirable to have the serial data fill the modem buffer faster than  
the outgoing data rate especially because data compression is  
disabled. ( )  
Disable Data  
Compression  
This field will turn off the default data compression algorithms that  
are in use by most consumer modems. This field is 6 characters  
long and is case in-sensitive. ( )  
Enable Error  
Control  
This field will turn on the V.42 LAPM and MNP error control  
protocols, if available on the modem. This field is 6 characters  
long and is case in-sensitive.  
This V.42/MNP/Buffer mode first attempts to negotiate V.42 error  
control with the remote modem. If this fails, then the modem  
transitions to MNP, and if this fails then no error control is used. ( )  
Misc. Init.  
Param  
This field supports any initialization parameters that are not  
already specified. The AT commands specified in this free-form  
field will be always the last initialization parameters to be sent to  
the external modem. This field is 20 characters long and is case  
in-sensitive. ( )  
Auto-Answer Ring  
Count  
This field controls the number of rings required before the modem  
automatically answers an incoming call, if and only if the switch  
doesn’t answer first. (If the switch is healthy, it answers an  
incoming within the first few rings.) This field is 6 characters long  
and is case insensitive. Typically, the maximum permissible value  
for this register is 255. The values 1-255 denote the number of  
incoming ring cycles. (S0=10)  
NOTE:  
The number of rings is optimally set above 5, and if at all  
possible, keep the default of S0=10.  
Dial Type  
This field controls the type of inter-register signaling to be used  
between the modem and the Central Office. Use “T” for tone  
dialing and “P” for pulse dialing. The field length is be 3  
characters long and is case in-sensitive. This field will be  
concatenated with the dial string. (T)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
clear audits  
2
2-36  
Adjustable  
Make/Break Ratio  
This field can be of particular importance when using a modem  
that may be transferable from country to country. The intent of this  
field is to control the make/break ratios of pulses and DTMF  
dialing. The Intel product information has support for the different  
make/break options for pulse dialing only.  
Intel uses the option “&P0” to select a ratio of 39% make and 61%  
break for communication within the U.S. and Canada. The option  
“&P1” sets a ration of 33% make and 67% break for the U.K. and  
Hong Kong.  
This field is 5 characters long and is case in-sensitive. ( )  
Dial Command  
This field simply denotes the dialing command of the modem.  
This is a fairly standard command. (D)  
No Answer  
Time-Out  
Most off-the-shelf external modems provide a timer that abandons  
any outbound data call after a predetermined interval. Some  
modems provide for this timer to be disabled, thus allowing an  
outbound call to ring indefinitely. AT&T Paradyne does not  
provide this capability with their modem line, because it is  
generally undesirable to have an outbound call attempt ring  
indefinitely.  
The internal modem must have this parameter disabled or set to  
at least 255 seconds.  
This is a non-administrable parameter. For the external modem  
connection, this parameter will be the first initialization string to be  
transmitted to the external modem. This field will be visible on the  
administration form in display mode only.  
This hardcoded constant can be overridden for type approval  
applications, specifically in the U.K and other Western European  
nations, by the use of the “Misc. Init. Param:” field. (S7=255)  
clear audits  
The clear audits command clears cumulative and/or peak hour’s data collected  
for each data relation audit. This command clears old data to display data  
collected since the last clear audits command when the status audits  
command is invoked. Refer to the status audits manual page for more  
information).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
clear errors  
2
2-37  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
clear audits  
cumulative  
Clears data collected about the  
peak hour since the last reboot  
or clear audits cumulative  
command  
init  
inads  
none  
See below  
peak-hour  
Clears peak hour data  
Examples:  
clear audits cumulative  
clear audits peak-hour  
Feature Interactions  
Status audits displays data cleared by the clear audits command. After clear  
audits executes successfully, the display audits cumulative and/or display  
audits peak-hour commands display information collected since the last clear  
audits command. The start date displays on the status audits screen reflecting  
the time that clear audits executed.  
clear errors  
The clear errors command moves errors and resolved alarms to cleared-error  
lists, making room for new incoming error messages. This command does not  
clear active alarms from the alarm log. This command must be used with care to  
prevent overwriting cleared entries. When additional entries are needed to log  
new errors, the system clears error entries first. Use the display errors command  
to list the cleared errors.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
clear errors  
Examples:  
init  
none  
none  
clear errors  
inads  
craft  
clear interface  
The clear interface command reintializes counter values maintained by the  
Processor Interface (PI) circuit pack. The status interface command, used in the  
development environment, displays the counters. The PI circuit pack, a front end  
processor, implements the packet and link layers of the BX.25 protocol, and the  
ISDN procedure-D protocol.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
clear isdn-testcall  
2
2-38  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
clear interface  
location  
Processor interface address  
(cabinet-carrier-position):  
init  
inads  
craft  
none  
none  
1 = first processor  
2 = second processor  
Examples:  
clear interface 01a1  
clear interface 01a2  
clear interface a2  
clear isdn-testcall  
The clear isdn-testcall command cancels in-progress ISDN-PRI test calls. Once  
a running test call is cleared, another can begin.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
clear  
group  
Trunk group number.  
init  
none  
none  
isdn-testcall  
number  
inads  
craft  
member  
number  
Member within the trunk group.  
Examples:  
clear isdn-testcall 80/1  
clear isdn-testcall 78/2  
clear link  
The clear link command clears the hardware error counters associated with  
ports on the Processor Interface circuit pack (displayed with the status link  
command) or a numbered PPP C-LAN link. The clear clan-port command  
accomplishes the same thing. The statistical counters cannot be cleared for an  
Ethernet C-LAN link.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
clear link  
link-id  
Link number (1-8) assigned  
throughcommunication-interface  
links form.  
init  
inads  
craft  
none  
none  
Examples:  
clear link 1  
clear link 8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
clear mst  
2
2-39  
clear mst  
The clear mst command precedes a trace. If this command is active during a  
trace, it clears unwanted data.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
clear mst  
Examples:  
init  
none  
none  
clear mst  
inads  
clear pkt  
The clear pkt command resolves packet bus problems and sends a forced  
packet bus clear stimuli command over the packet bus.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
clear pkt  
port  
network  
location  
Physical position of the packet bus  
(1 - 3)  
init  
inads  
craft  
none  
none  
Examples:  
clear pkt port-network 1  
clear port  
The clear port works with the mark port command. This command removes  
marks from ports frees them for service.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
clear port  
location  
Port location (PCSSpp)  
init  
none  
none  
inads  
cust  
nms  
Examples:  
clear port 01c1102  
disable administered-connection  
The disable administered connection command stops both scheduled and  
periodic testing and stops processing of in-line errors for all or selected  
administered connections.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
disable mst  
2
2-40  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
disable  
administered-  
connection  
ac  
number  
Number of the administered  
connection  
init  
none  
none  
inads  
craft  
cust  
rcust  
mis  
all  
Selects all administered connections  
Examples:  
disable administered-connection all  
disable administered-connection 1  
disable administered-connection 128  
disable mst  
The disable mst command stops the message trace facility. If the trace was not  
already disabled, the command inserts a GAP marker into the trace. The user  
should execute the disable mst command when the trace is complete. If left  
enabled, the trace continues to use CPU time until the time limit expires. Entering  
disable mst command has no effect on the system if the trace is already  
disabled. To view the results of the trace, enter the list mst command.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
disable mst  
Example:  
init  
none  
none  
disable mat  
inads  
disable suspend-alm-orig  
The disable suspend-alm-orig command stops entries from the active Suspend  
Alarm Origination table. This command disables all board entries that match a  
specific physical board location.  
NOTE:  
This command does not disable port entries.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
disable  
suspend-  
alm-orig  
board  
location  
Physical location of the replaced or  
corrected board (does not support  
port location)  
init  
none  
none  
inads  
craft  
cust  
rcust  
Examples:  
disable suspend-alm-orig 1C03  
disable suspend-alm-orig 1E07  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
disable synchronization-switch  
2-41  
disable synchronization-switch  
This command stops the automatic clock switching capability of the maintenance  
subsystem. The clock refers to the oscillator on a tone/ clock or DS1 interface.  
The synchronization subsystem (TDM bus clock, DS1 trunk board, and  
maintenance and administration software) provides error-free digital  
communication between the switch and other PBXs, COs, or customer  
equipment.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
disable  
init  
none  
none  
synchronization-  
switch  
inads  
craft  
disable test-number  
The disable test-number command prohibits selected maintenance tests from  
running. To run a disabled test number, enter the enable test-number command.  
Feature  
Action/Object  
Qualifier  
number  
print  
Qualifier Description  
Maintenance test number  
Report sent to printer  
Permissions  
Defaults  
Interactions  
disable  
test-number  
init  
inads  
none  
none  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue  
and is executed at the specified  
time. The information displayed  
by the command is sent to the  
system printer instead of the  
1
screen.  
Examples:  
disable test-number 710  
disable test-number 710 print  
disable test-number 510  
schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
display alarms  
The display alarms command creates an Alarm Report. The user completes an  
option screen to select the parameters for the report.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display alarms  
2
2-42  
The system creates the reports from the logs of the maintenance subsystem. The  
subsystem monitors the system hardware and logs problems as errors or alarms.  
The type of alarm indicates the impact of the problem, as defined below:  
Warning alarm—A minor interference which does not noticeably impair service.  
Minor alarm—A problem which could disable a local area of the system and  
noticeably impair service.  
Major alarm—A problem which widely degrades the system and seriously  
impairs service. The system automatically calls INADS to report major alarms.  
Resolved alarm—A problem which has been corrected, and the system is  
correctly functioning. The system stamps resolved alarms with the date and time  
the problem was corrected. The system handles any errors associated with the  
alarms as “resolved.”  
System Reboots and the Alarm Logs  
The system saves the Alarm and Error logs to the memory card if any of the  
following events occur:  
— The save translation command is executed.  
— Translations are saved as part of scheduled maintenance.  
— A reboot takes place.  
— The PPN is about to lose all power after having been on battery backup.  
The attempt to save the alarm and error logs may be unsuccessful if the MSS is  
not available.  
Whenever the system reboots, the logs are restored from the SPE disk that  
becomes active with the reboot. Since the logs are saved to the disk on the SPE  
that was active before the reboot, the versions restored at reboot time may not be  
current. This condition occurs if:  
— The attempt to save at reboot did not succeed.  
— The SPE disk that is rebooted is not the same disk to which the logs were  
last saved.  
In such a case, the logs will not contain the most recent errors and alarms. To  
determine if the restored logs are complete, look for indications that would have  
preceded the reboot.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display alarms  
2
2-43  
System resets, that are less severe than a reboot, rarely affect the error and alarm  
logs.  
NOTE:  
If the error and alarm logs contain SYSTEM errors, then use the display  
initcauses command to search for information that system could not log  
during reset operation.  
Feature  
Action/Object  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
display alarms  
Report sent to printer  
init  
inads  
craft  
all alarms  
displayed  
See below  
schedule  
Command is validated and then  
a scheduling form displays to  
schedule execution of the  
cust  
rcust  
bcms  
browse  
command. The command is then  
placed in the command queue  
and is executed at the specified  
time. The information displayed  
by the command is sent to the  
system printer instead of the  
1
screen.  
Examples:  
display alarms  
display alarms print  
display alarms schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Feature Interactions  
If the user disables the alarm origination with the change  
■
system-parameters maintenance command, then the Ack?  
(Acknowledged) field on the Alarm Report is blank regardless of the true  
acknowledged state of the alarm.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display alarms  
2
2-44  
Options screen  
When you enter the display alarms command, the system first displays the  
options screen. Select the options you want to view on the report. The figure  
below is an example of the options screen for Alarm Reports.  
display alarms  
Page 1 of 1  
ALARM REPORTS  
The following options control which alarms will be displayed.  
ALARM TYPES  
Active? y_  
Major? y_  
Resolved? n_  
Minor? y_  
Warning? y_  
REPORT PERIOD  
Interval: m_  
From: __/__/__:__ To: __/__/__:__  
EQUIPMENT TYPE ( Choose only one, if any, of the following )  
Cabinet: ____  
Port Network: __  
Board Number: _______  
Port: ________  
Category: ________  
Extension: _____  
Trunk ( group/member ): ___/___  
Field descriptions  
ALARM TYPES  
Interval  
Enter y (yes) or n (no) in any of the 5 alarm type fields  
Enter one of the codes below:  
m = last month  
h = last hour  
d = last day  
w = last week  
a = all (default)  
From  
To  
Month/day/year (example: 01/01/97); if the Fromdate is blank, the  
report contains all the active alarms for the month prior to the current  
date.  
Month/day/year (example: 01/15/97); if the Todate is not entered,  
the report contains all the active alarms starting with the Fromdate  
to the current date.  
Cabinet  
Administered cabinet number (1-3)  
1-3  
Port Network  
Board  
Board address (PCSS); example: 01A20  
Number:  
Port  
Port address (PCSSpp); example: 01A2031  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display alarms  
2
2-45  
Category  
Object code for the equipment category. Press HELP in this field to  
view a list of the object codes.  
Extension  
Trunk  
Extension number (per dial-plan)  
Enter a group number or a group and member number:  
■ Enter only the group number (01-99) to display all members in  
the group. Example: 01/__  
■ Enter both the group number (01-99) and member number  
(01-99) to display a specific member in a group.Example: 01/99  
Output  
After you complete the options screen, the system displays a 1- or 2-page Alarm  
Report. To toggle between the pages and to exit the report, use the keys  
described below:  
■
■
■
For 513 and 715 terminals, use F8 for NEXT PAGE and PREV PAGE commands  
For all other terminals, use F7 for NEXT PAGE and PREV PAGE commands  
Use Esc for the CANCEL command.  
The screen below shows an example of an Alarm Report.  
display alarms  
ALARM REPORT  
Port  
Maintenance On  
Alt  
Name  
Alarm  
Type  
Svc  
State 1 2  
Ack? Date  
Alarmed  
Date  
Resolved  
Name  
Brd?  
01C07  
ANL-BD  
y
n
n
n
n
n
n
MINOR  
n n 05/22/20:26 00/00/00:00  
05/22/20:26 00/00/00:00  
05/22/20:26 00/00/00:00  
05/22/20:26 00/00/00:00  
05/22/20:26 00/00/00:00  
05/22/20:26 00/00/00:00  
05/23/14:53 00/00/00:00  
01C0702 ANL-LINE  
01C0701 ANL-LINE  
01C0703 ANL-LINE  
01C1505 CO-TRK  
01C1505 CO-TRK  
PN 02B TDM-BUS  
311  
1051  
1053  
WARNING IN  
WARNING IN  
WARNING IN  
78/01 WARNING OUT  
78/01 WARNING OUT  
WARNING  
Command successfully completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display alarms  
2
2-46  
Field descriptions  
Port  
Lists the location codes for the alarmed object, as follows:  
■ Circuit packs locations display as:  
cabinet-carrier-[slot]-[circuit]. Example: 01C0702.  
■ Port network locations display as: port network number-bus.  
Example: PN 02B. PN 02 = Port Network (PN) number and A  
or B = bus.  
■ Fiber link locations display as: fiber link number-PNC side.  
Example: x A-PNC. “X” = fiber link number and “A” = PNC  
side [A or B].  
Maintenance  
Name  
Lists the logical name of the maintenance object with the alarm.  
On Brd  
A y (yes) indicates the fault was found on the associated circuit  
pack. A n (no) indicates the fault is not connected to the circuit  
pack.  
Alt Name  
Identifies the location of maintenance object, as follows:  
■ Station = extension number  
■ Trunk = Group number (78/__) or group and member  
numbers (78/01)  
■ Private CO Line = private CO line (P) and group number.  
(P/xxx)  
Alarm Type  
Alarm level: MAJOR, MINOR, or WARNING  
Service state of the station and trunk ports:  
■ RDY = ready for service  
Service State  
■ OUT = out of service  
■ IN = in service  
■ [Blank] = No associated service state  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display capacity  
2
2-47  
Ack?  
Headings 1 and 2 identify the first and second OSS telephone  
numbers, respectively. The entries below indicate the  
acknowledged alarm state:  
■ y (yes) = alarm has been acknowledged  
■ n (no) = alarm has not been acknowledged  
■ c (cleared) = alarm was first acknowledged, then resolved  
and cleared  
[Blank] = no attempt was made to report the alarm  
NOTE:  
If the user disables the alarm origination with the change  
system-parameters maintenance command, then the  
Ack? field will be blank regardless of the true  
acknowledged state of the alarm.  
Date Alarmed  
Date Resolved  
Month, day, hour, and minute of the alarm.  
Month, day, hour, and minute of the resolution (active alarms =  
zeros)  
display capacity  
This form describes how you have administered your system and provides a  
"snapshot" status of the switch resources.  
Feature  
Action/Object  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
display capacity  
Report sent to printer  
init  
none  
none  
inads  
craft  
cust  
rcust  
schedule  
Command validated first, then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue  
and is executed at the specified  
time. The information displayed is  
sent to the system printer instead  
1
of the screen.  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
The screen below shows the output from the display capacity command.  
NOTE:  
The capacities listed may not coincide with your system. The figures that  
follow are included to help explain the command and the field values, not to  
provide capacity information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display capacity  
2
2-48  
display capacity  
Page 1 of 9  
SYSTEM CAPACITY  
Current System Memory Configuration: G3rV6  
System  
Used Available Limit  
- - - - - - - - - - - - -  
AAR/ARS  
AAR/ARS Patterns:  
Inserted Digit Strings:  
17  
6
623  
2994  
640  
3000  
ABBREVIATED DIALING (AD)  
AD Entries Per System:  
AD Personal Lists Per System:  
10  
1
99990  
4999  
100000  
5000  
ADJUNCT SWITCH APPLICATION INTERFACE (ASAI)  
Active Controlling Associations:  
Notification Requests:  
Simultaneous Active Adjunct Controlled Calls:  
0
0
0
6000  
10000  
3000  
6000  
10000  
3000  
Field descriptions (page 1)  
AAR/ARS  
AAR/ARS  
The number of route patterns. For further information, see  
Patterns  
DEFINITY Enterprise Communications Server Administration and  
Feature Description.  
Inserted Digit  
Strings  
Number of 12-character inserted-digit strings available for  
AAR/ARS preferences. For further information, see DEFINITY  
Enterprise Communications Server Administration and Feature  
Description.  
Abbreviated Dialing (AD)  
AD Entries Per  
System  
The number of abbreviated dialing entries (for both group and  
personal lists).  
AD Personal  
Lists Per  
System  
The number of abbreviated dialing personal lists. For further  
information, see DEFINITY Enterprise Communications Sever  
Administration and Feature Description.  
Adjunct Switch Application Interface (ASAI)  
Active  
The number of station domain controls that ASAI adjuncts can  
Controlling  
Associations  
request.  
Notification  
Requests  
The number of requests ASAI can make to monitor call activity at  
a split or VDN.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display capacity  
2
2-49  
Simultaneous  
Active Adjunct  
Controlled  
Calls  
The number of calls that can be controlled by ASAI adjuncts.  
Page 2 of 9  
SYSTEM CAPACITY  
System  
Used Available Limit  
- - - - - - - - - - - - -  
ATTENDANT SERVICE  
Attendant Positions:  
Queue Length:  
2
0
26  
300  
28  
300  
Authorization Codes:  
0
90000  
90000  
BASIC CALL MANAGEMENT SYSTEM (BCMS)  
Measured Agents Per System:  
Measured Splits/Skills:  
VDNs:  
0
0
0
2000  
600  
512  
2000  
600  
512  
Figure 2-1. System Capacity form (page 2 of 9)  
Field descriptions (page 2)  
Attendant Service  
Attendant  
Positions  
The number of administered attendants.  
Queue Length  
A real-time snapshot of the number of calls waiting for all  
attendants.  
Authorization  
Codes  
The number of authorization codes used for security purposes.  
For further information, see DEFINITY Enterprise Communications  
Server Administration and Feature Description.  
Basic Call Management System (BCMS)  
Measured  
Agents Per  
System  
The number of agents the Basic Call Management System  
(BCMS) is measuring.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display capacity  
2
2-50  
Measured  
The number of hunt groups BCMS is measuring.  
Splits/Skills  
VDNs  
The number of vector directory numbers BCMS is measuring.  
Page 3 of 9  
SYSTEM CAPACITY  
System  
Used Available Limit  
- - - - - - - - - - - - -  
CALL COVERAGE  
Coverage Answer Groups:  
0
7
750  
9992  
750  
9999  
Coverage Paths:  
Call Pickup Groups:  
Call Records:  
0
-
5000  
-
5000  
7712  
CALL VECTORING/CALL PROMPTING  
Vector Directory Numbers:  
Vectors Per System:  
BSR Application-Location Pairs Per System:  
2
3
0
19998  
509  
1000  
20000  
512  
1000  
Figure 2-2. System Capacity form (page 3 of 9)  
Field descriptions (page 3)  
Call Coverage  
Coverage  
Answer Groups  
The number of Coverage Answer Groups. For further information,  
see DEFINITY Enterprise Communications Server Administration  
and Feature Description.  
Coverage Paths  
Coverage Paths — The number of coverage paths which is a  
path taken when a call goes to coverage. For further information,  
see DEFINITY Enterprise Communications Server Administration  
and Feature Description.  
Call Pickup  
Groups  
The number of call pickup groups have been administered. For  
further information, see DEFINITY Enterprise Communications  
Server Administration and Feature Description.  
Call Records  
The maximum number of active calls at a given time. This field  
does not display real-time data, just the system limit and is not  
administerable.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display capacity  
2
2-51  
Call Vectoring/Call Prompting  
Vector  
Directory  
Numbers  
The number of system VDNs. For further information, see  
DEFINITY Call Vectoring/Expert Agent Selection.  
Vectors Per  
System  
The number of vectors per system. For further information, see  
DEFINITY Call Vectoring/Expert Agent Selection.  
BSR  
The number of mappings administered in a multisite network. The  
maximum number of application-location pairs per system is  
1000. For example, for a network of 10 locations, you can  
assign100 applications; with 50 locations, you can assign 20  
applications. For further information, see DEFINITY Call  
Vectoring/Expert Agent Selection.  
Application -  
Location Pairs  
Per System  
Page 4 of 9  
SYSTEM CAPACITY  
System  
Used Available Limit  
- - - - - - - - - - - - -  
DATA PARAMETERS  
Administered Connections:  
5
0
123  
1250  
128  
1250  
Alphanumeric Dialing Entries:  
DIAL PLAN  
Extensions:  
Miscellaneous Extensions:  
UDP Extension Records:  
104  
25  
15  
35961  
20292  
49985  
36065  
20317  
50000  
Digital Data Endpoints:  
Expansion Port Networks:  
Facility Busy Indicators:  
50  
2
7450  
41  
7500  
43  
10  
9990  
10000  
Figure 2-3. System Capacity form (page 4 of 9)  
Field descriptions (page 4)  
Data Parameters  
Administered  
Connections  
The number of connections between two access or data  
endpoints. For further information, see DEFINITY Enterprise  
Communications Server Administration and Feature Description.  
Alphanumeric  
Dialing  
For further information, see DEFINITY Enterprise Communications  
Server Administration and Feature Description.  
Entries  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display capacity  
2
2-52  
Dial Plan  
Extensions  
This includes stations, data endpoints, hunt groups,  
announcements, TEGs, VDNs, common shared extensions, and  
code calling IDs.  
Miscellaneous  
Extensions  
Anything that is not a station, trunk, data module, or attendant.  
This includes, but is not limited to, PCOL groups, common shared  
extensions, access endpoints, administered TSCs, code calling  
IDs, VDNs, LDNs, hunt groups, announcements, and TEGs.  
UDP Extension  
Records  
The number of 4- or 5-digit extension numbers that allow a user to  
call from one PBX to another using that number.  
Digital Data  
Endpoints  
The number of digital serial communication devices that permit  
the asychronous transfer of data. This also includes the number  
of analog adjuncts.  
Expansion Port  
Networks  
The number of port networks connected to the TDM bus and  
packet bus of a process port network.  
Facility Busy  
Indicators  
The number of visual indicators of the busy/idle status of any  
particular trunk group, hunt group member, or station user. For  
further information, see DEFINITY Enterprise Communications  
Server Administration and Feature Description.  
Page 5 of 9  
SYSTEM CAPACITY  
System  
Used Available Limit  
- - - - - - - - - - - - -  
HUNT GROUPS, SPLITS, OR SKILLS  
Groups/Splits/Skills:  
9
0
17  
0
2
0
591  
5200  
9983  
10000  
14998  
2000  
600  
5200  
10000  
10000  
15000  
2000  
Logged-In ACD Agents:  
Group Members Per System:  
CMS Measured ACD Members:  
Queue Slots Per System:  
Queue Status Buttons:  
Intercom Groups Per System:  
Modem Pool Groups Per System:  
0
0
0
256  
63  
256  
63  
Personal CO Line (PCOL) Trunk Groups:  
200  
200  
Screen 2-2. System Capacity form (page 5 of 9)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display capacity  
2
2-53  
Field descriptions (page 5)  
Hunt Groups, Splits, or Skills  
Groups/Splits/  
Skills  
The number of ACD hunt groups.  
Logged-In ACD  
Agents  
A real-time field displaying the number of agents actually logged  
in. For example, if an agent is logged into 4 skills (and there are  
no other agents), then the Logged-In ACD Agentsfield is 1  
and the Group Members Per Systemfield is 4.  
Group Members  
Per System  
The number of agent/group pairs.  
CMS Measured  
ACD Members  
The number of agent pairs being measured by CMS.  
The number of hunt group queue positions.  
Queue Slots  
Per System  
Queue Status  
Buttons  
The number of hunt group queue status buttons administered on  
stations. There are four types of queue status buttons; attendants  
use the last two queue status buttons:  
■ q-calls (Queue Calls)  
■ q-time (Queue Time)  
■ atd-qcalls (ATD - Queue Calls)  
■ atd-qtime (ATD - Queue Time)  
The number of intercom groups set up within your organization.  
Intercom  
Groups Per  
System  
Modem Pool  
Groups Per  
System  
The number of modem pool groups. For further information, see  
DEFINITY Enterprise Communications Server Administration and  
Feature Description.  
Personal CO  
Line (PCOL)  
Trunk Groups  
The number of PCOL trunk groups. For further information, see  
DEFINITY Enterprise Communications Server Administration and  
Feature Description.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display capacity  
2
2-54  
Page 6 of 9  
SYSTEM CAPACITY  
System  
Used Available Limit  
- - - - - - - - - - - - -  
Recorded Announcement Analog Queue Slots:  
0
1256  
1256  
TEMPORARY SIGNALING CONNECTIONS (TSC)  
Administered TSCs:  
0
0
128  
256  
128  
256  
NCA-TSC Calls:  
TRUNKS  
DS1 Circuit Packs:  
ICHT For ISDN Trunks:  
ISDN CBC Service Selection Trunks:  
Trunks Groups:  
9
0
1
29  
86  
157  
576  
199  
637  
3914  
166  
576  
200  
666  
4000  
Trunks Ports:  
Figure 2-4. System Capacity form (page 6 of 9)  
Field descriptions (page 6)  
Recorded  
The number of calls in queue for the system’s analog  
announcements.  
Announcement  
Analog Queue  
Slots  
Temporary Signaling Connections (TSC)  
Administered  
TSCs  
The number of allowed Temporary Signaling Connections (TSCs).  
NCA-TSC Calls  
The number of allowed Non-Call Associated TSCs.  
Trunks  
DS1 Circuit  
Packs  
The number of allowed DS1 circuit packs.  
ICHT For ISDN  
Trunks  
The number of Incoming Call Handling Table (ICHT) entries  
administered for trunk groups.  
ISDN CBC  
Service  
Selection  
Trunks  
The number of call-by-call trunk groups.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display capacity  
2
2-55  
Trunk Groups  
Trunk Ports  
The number of trunk groups administered.  
The number of trunk ports administered.  
Page 7 of 9  
SYSTEM CAPACITY  
System  
Used Available Limit  
- - - - - - - - - - - - -  
VOICE TERMINALS  
Station Button Memory (units):  
Station Records:  
Stations:  
0 %  
35  
29  
29  
0
100 %  
24965  
5260000  
25000  
-
-
-
-
-
-
-
-
-
-
Stations With Port:  
Stations Without Port:  
Other Stations:  
6
0
TTI Ports:  
TOTAL SUBSCRIBED PORTS  
ISDN BRI Ports:  
3
6997  
7000  
Station and Trunk Ports:  
119  
13881  
14000  
Figure 2-5. System Capacity form (page 7 of 9)  
Field descriptions (page 7)  
Voice Terminals  
Station Button  
Memory (units)  
The percentage of memory being consumed by all administered  
buttons.  
Station  
Records  
The number of resources being used by regular stations,  
announcements, and music on hold.  
Stations  
The number of voice terminals.  
Stations With  
Port  
The number of connected voice terminals (stations with specific  
administered ports).  
Stations  
Without Port  
The number of voice terminals not having an administered port,  
such as AWOH.  
Other Stations  
The number of ports used as conversion resources, agent login  
ID, MASI, and analog announcements.  
TTI Ports  
The number of ports assigned by TTI features.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display capacity  
2
2-56  
Total Subscribed Ports  
ISDN BRI Ports  
The number of ISDN-BRI ports.  
Station and  
Trunk Ports  
The number of stations with ports and assigned trunk ports.  
Page 8 of 9  
SYSTEM CAPACITY  
CURRENT SYSTEM INFORMATION  
Software Load: G3V6r.03.0.211.0  
Memory Configuration: G3rV6  
Offer Category: A  
LAST TRANSLATION LOADED INFORMATION:  
Software Load: G3V4r.06.0.075.0  
Memory Configuration: G3r (large)  
Offer Category: unknown  
Figure 2-6. System Capacity form (page 8 of 9)  
Field descriptions (page 8)  
Current System Information  
Software Load  
The current software load on which the system is running.  
Memory  
The system platform.  
Configuration  
Offer Category  
The system’s offer category.  
Last Translation Loaded Information  
Software Load The software load translations saved before upgrade or reboot.  
Can also be unknown/no transif no flash card is present.  
Also, if load translations were upgraded from one prior to G3V4  
load 71 or early G3V5 loads, unknown/no transdisplays.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display capacity  
2
2-57  
Memory  
The platform on which the translations were saved. Can also be  
Configuration  
unknownif no flash card is present or translations made on old  
load. This is important because platforms are not always  
compatible.  
Offer Category  
The offer category that was set when the last save translation was  
done before upgrade or reboot. Can also be unknownif no flash  
card is present or translations made on old load.  
Page 9 of 9  
SYSTEM CAPACITY  
System  
Used Available Limit  
- - - - - - - - - - - - -  
TOTAL SUBSCRIBED PORTS  
WIRELESS:  
Radio Controllers:  
Wireless Terminals:  
0
0
0
0
0
0
Figure 2-7. System Capacity form (page 9 of 9)  
Field descriptions (page 9)  
Total Subscribed Ports  
Radio  
The number of subscribed radio controller circuit packs.  
Controllers  
Wireless  
The number of subscribed wireless terminals.  
Terminals  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display communication-interface hop-channels  
2-58  
display communication-interface  
hop-channels  
This command displays the translation data for hop channels. A hop channel is a  
bi-directional network channel between two interface links for DCS message  
hopping. A hop channel is used to tandem DCS messages from one interface  
link to another interface link. See ‘‘status link n’’ for more details.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
display  
communication-  
interface  
hop-  
channels  
Number of the local processor  
channel  
init  
none  
none  
inads  
craft  
cust  
rcust  
print|  
Report sent to printer  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue  
and is executed at the specified  
time. The information displayed  
by the command is sent to the  
system printer instead of the  
1
screen.  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output for Hop-channels qualifier  
When you enter the command display comm hop, the systems displays the Hop  
Channel Assignment screen, similar to the screen below. The number of the local  
processor channel, used to hop the interface link channels, is not shown.  
display communication-interface hop-channels  
HOP CHANNEL ASSIGNMENT  
Link/Chan Priority Link/Chan  
12  
Page  
1 of  
4
Link/Chan Priority  
Link/Chan Priority  
3
1
4
Field descriptions  
Link/Channel A  
First of the two link/channels joined by the hop channel. Links  
range from 1 to 16. Channels range from 1 to 64. The  
link/channel must not be assigned to a local processor channel  
or to a PRI local processor channel.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display communication-interface links  
2-59  
Link/Channel B  
Second of the two link/channels joined by the hop channel.  
Links range from 1 to 16. Channels range from 1 to 64. The  
link/channel pair must not be assigned to a local processor  
channel or to a PRI local processor channel.  
display communication-interface links  
Feature  
Action/ Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list  
links  
Example:  
init  
none  
None  
communication-  
interface  
list  
inads  
craft  
communication-interface  
links  
Output  
The following example shows the output from the list/display  
communication-interface links command.  
display communication-interface links  
INTERFACE LINKS  
Destination DTE Conn Name  
Number DCE Mod.  
Page  
1 of  
2
Link Enable Est Ext  
Conn  
Type  
1: y  
2: n  
3: n  
4: n  
5: n  
6: n  
7: n  
8: n  
9: n  
10: n  
11: n  
12: n  
13: n  
14: n  
15: n  
16: n  
17: n  
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
2991 ETHERNET  
ethernet on link 1  
Screen 2-3. Interface links screen  
Field descriptions  
Link  
Number of the administered link (data module form).  
Enable  
Yes (y) or no (n) depending upon data module administration  
(Processor Interface, X.25, Ethernet, and PPP).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display disabled-tests  
2
2-60  
Est. Conn.  
Establish Connection data from the data module forms  
(Processor Interface, X.25, and PPP).  
Ext  
Extension number of the local data module for this link.  
Type  
Protocol for this link:  
■ bx.25(Processor Interface and X.25)  
■ ppp  
■ ethernet  
Destination Number  
DTE/DCE  
Destination of the link as administered on the data module forms  
(Processor Interface, X.25 and PPP).  
Processor Interface administration from data module form  
(Processor Interface only).  
Conn. Mod.  
Name  
Connected Data Module administration from data module form  
(Processor Interface and X.25 only)  
Administered name from the data module forms (Processor  
Interface, X.25, Ethernet, and PPP)  
display disabled-tests  
This command lists the numbers for all maintenance tests that have been  
disabled by INADS. These tests will not be available for background or demand  
testing.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
display  
[print |  
Report sent to printer  
init  
none  
none  
disabled-tests  
schedule]  
inads  
craft  
cust  
rcust  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue  
and is executed at the specified  
time. The information displayed  
by the command is sent to the  
system printer instead of the  
1
screen.  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display errors  
2
2-61  
Output  
The following examples shows the output from the display disabled-tests  
command.  
display disabled-tests  
SPE A  
DISABLED TEST INFORMATION  
Test Number  
710  
Command successfully completed  
display errors  
The display errors command creates an Alarm Report. The user completes an  
option screen to select the parameters for the report.  
The system creates the reports from the logs of the maintenance subsystem. The  
subsystem monitors the system hardware and logs problems as errors or alarms.  
Errors can result from in-line firmware errors, periodic tests, failures detected  
while executing a test command, software inconsistency, or a data audit  
discrepancy.  
System Reboots and the Error Logs  
The system saves the alarm and error logs to the memory card if any of the  
following events occur:  
— The save translation command is executed.  
— Translations are saved as part of scheduled maintenance.  
— A reboot takes place.  
— The PPN is about to lose all power after having been on battery backup.  
The attempt to save the alarm and error logs may be unsuccessful if the MSS is  
not available.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display errors  
2
2-62  
Whenever the system reboots, the logs are restored from the SPE disk that  
becomes active with the reboot. Since the logs are saved to the disk on the SPE  
that was active before the reboot, the versions restored at reboot time may not be  
current. This condition occurs if:  
— The attempt to save at reboot did not succeed.  
— The SPE disk that is rebooted is not the same disk to which the logs were  
last saved.  
In such a case, the logs do not contain the most recent errors and alarms. To  
determine if the restored logs are complete, look for indications that would have  
preceded the reboot.  
System resets, less severe than a reboot, rarely affect the error and alarm logs.  
NOTE:  
If the error and alarm logs contain SYSTEM errors, then use the display  
initcauses command to search for information that system could not log  
during reset operation.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
display  
errors  
high  
resolution  
Highlights the time stamps on the Error  
Report for the first and last occurrences  
of the error.  
init  
all errors  
displayed  
none  
inads  
craft  
cust  
print  
Report sent to printer  
nms  
schedule  
Command is validated and then a  
scheduling form displays to schedule  
execution of the command. The  
command is then placed in the  
browse  
command queue and is executed at  
the specified time. The information  
displayed by the command is sent to  
the system printer instead of the  
1
screen.  
Examples:  
display errors  
display errors print  
display errors schedule  
display errors high-resolution print  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Input form  
When you enter the display errors command, the system first displays the  
options screen. You select the options you want to view on the report. The figure  
below is an example of the options screen for an Error Report.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display errors  
2
2-63  
display errors  
Page  
1 of  
1
ERROR REPORT  
The following options control which errors will be displayed.  
ERROR TYPES  
Error Type: _____  
REPORT PERIOD  
Error List: active-alarms  
Interval: _  
From: __/__/__:__ To: __/__/__:__  
EQUIPMENT TYPE ( Choose only one, if any, of the following )  
Cabinet: __  
Port Network: __  
Board Number: ____  
Port: ______  
Category: ________  
Extension: _____  
Trunk ( group/member ): ___/___  
Field descriptions  
Error Type  
Error List  
Enter a specific error type. If the field is blank, the system displays  
all errors. Press HELP in this field to view a list of codes.  
Enter one of the error lists below:  
active-alarms (default)  
errors  
cleared-errors  
The title for the Hardware Error Report will include the name of the  
selected error list.  
Interval  
Enter one of the codes below:  
m = last month  
h = last hour  
d = last day (default)  
w = last week  
a = all  
From  
To  
Enter 2-digit numbers for the month/day/year (Example: 01/01/97).  
The default is the earliest time of the existing error records in the log.  
Enter 2-digit numbers for the month/day/year (Example: 01/01/97).  
The default is the current date.  
Cabinet  
Enter 1  
Port Network  
Enter 1  
Board  
Board address: PCSS  
Number:  
Port  
Port location: PCSSpp  
Category  
Enter the object code for the equipment category. Press HELP in this  
fieldDtoowvniloeawd faromlisWt wowf .tShoemoanbujaelsc.ctocmo.dAell Msanuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display errors  
2
2-64  
Extension  
Trunk  
Enter the extension number  
Enter a group number or a group and member number:  
■ Enter only the group number (01-99) to display all members in  
the group. Example: 01/__  
■ Enter both the group number (01-99) and member number  
(01-99) to display a specific member in a group. Example:  
01/99.  
Form output  
After completing the options screen, the system displays a 1- or 2-page  
Hardware Error Report. To toggle between the pages and to exit the report, use  
the keys described below:  
■
■
■
For 513 and 715 terminals, use F8 for NEXT PAGE and PREV PAGE commands  
For all other terminals, use F7 for NEXT PAGE and PREV PAGE commands  
Use Esc for the CANCELcommand  
The screen below is an example of an Hardware Error Report -- Active Alarms,  
without the high-resolution qualifier in the command line.  
display errors  
Page 1  
SPE A  
HARDWARE ERROR REPORT - ACTIVE ALARMS  
Port  
Mtce  
Name  
ANL-LINE 311  
ANL-LINE 1051  
ANL-LINE 1053  
TDM-CLK  
Alt  
Name  
Err  
Type Data  
257  
257  
257  
Aux  
First  
Occur  
Last  
Occur  
Err Err Rt/ Al Ac  
Cnt Rt Hr St  
01C0702  
01C0701  
01C0703  
01A  
01C1505  
01C1505  
01/31/09:20 01/31/20:26 255 256 255 a y  
01/31/20:26 01/31/20:26 4  
01/31/20:26 01/31/20:26 4  
01/31/20:34 01/31/20:34 1  
0
0
0
4
4
1
a y  
a y  
a n  
a y  
a y  
0
0
CO-TRK  
CO-TRK  
078/001 3329 57408 01/31/20:26 01/31/20:27 5  
078/001 1537 01/31/20:26 01/31/20:28 5  
300 5  
150 5  
Command successfully completed  
Field descriptions  
Port  
Lists the location codes for the alarmed object, as follows:  
■ Circuit packs locations display as:  
cabinet-carrier-[slot]-[circuit]. Example: 01C702.  
■ Port network locations display as: port network number-bus.  
Example: PN 01B. PN 01 = Port Network (PN) number and A  
or B = bus.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display errors  
2
2-65  
Maintenance  
Name  
Lists the logical name of the maintenance object with an error  
logged against it.  
Alt Name  
Identifies the location of maintenance object, as follows:  
■ Station = extension number  
■ Trunk = Group number (78/__) or group and member  
numbers (78/01)  
■ Private CO Line = private CO line (P) and group number  
(P/xxx)  
Error Type  
Aux Data  
Lists the error number for the type of problem encountered for  
this maintenance object. The technician must use this error  
number in conjunction with the logical name information to  
determine the exact nature of the error.  
Lists additional information concerning the maintenance object  
error condition. Like the error type, this data will be specific to the  
maintenance object type. However, unlike the error code, only  
the most recent value of the auxiliary data will be retained for  
each error record.  
First Occur  
Seq Cnt  
Displays the month, day, hour, and minute (and second if the  
high-resolution command line option is used) that the error was  
first recorded.  
Sequence Count - This number indicates the order of errors  
logged within a second for the time stamps associated with the  
first occurrence and last occurrence of an error. This information  
is displayed only if the high-resolution command line option is  
entered. There may be gaps for the sequence numbers within a  
given second since the last occurrence of an error may replace  
an existing entry that had been assigned the missing sequence  
number. Gaps may also appear in the numbers since sequence  
counts are also used with software event information not shown in  
the hardware error log.  
Last Occur  
Err Cnt  
Displays the month, day, hour, and minute (and second if the  
high-resolution command line option is used) of the most recent  
error. Note: if the system is unable to retrieve the time of day  
when the error occurred, a ‘dummy’ date will be stamped in the  
log and appears as: 00/00/01:07.  
Error Count - The total number of times that the error type has  
occurred for this maintenance object. If the number of errors  
exceeds 3 digits, the system enters the number 256, which  
indicates that a larger number of errors occurred, but could not  
be displayed correctly.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display errors  
2
2-66  
Err Rt  
Error Rate - The average rate at which the errors have occurred  
from the first occurrence to the present. If the number of errors  
exceeds 3 digits, the system enters the number 256, which  
indicates that a larger number of errors occurred, but could not  
be displayed correctly.  
Rt/Hr  
Al St  
Rate per Hour - An approximation of the rate that this error  
occurred in the last hour.If the number of errors exceeds 3 digits,  
the system enters the number 256, which indicates that a larger  
number of errors occurred, but could not be displayed correctly.  
Alarm Status - A character indicating the status of this MO in the  
error and alarm logs. The allowed values are:  
a = Active alarm entry  
r = Resolved alarm entry  
c = Resolved alarm entry as a result of the long “clear” option  
of the test command  
s = Resolved alarm entry as a result of a software requested  
(non-demand) system restart  
t = Resolved alarm entry as a result of a technician requested  
system restart  
n = Not alarmed.  
Ac  
Active? - A y (yes) entry indicates the maintenance object is still  
active. A n (no) entry indicates the object is no longer a problem.  
The screen below is an example of an Hardware Error Report -- Active Alarms,  
with the high-resolution qualifier in the command line.  
When you enter the command display errors high-resolution, the system adds  
the Seq Cnt(sequence count) column. The number in the column indicates the  
order of errors logged within a second for the time stamps associated with the  
first occurrence and the last occurrence of an error. Refer to the field description  
above for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display events  
2
2-67  
display errors high-resolution  
Page 1  
SPE A  
HIGH RESOLUTION HARDWARE ERROR REPORT - ACTIVE ALARMS  
Port  
Mtce  
Name  
Alt  
Name  
Err  
Type Data  
257  
257  
257  
Aux  
First  
Occur  
Seq  
Cnt  
Last  
Occur  
Seq Err Al  
Cnt Cnt St  
01C0702 ANL-LINE 311  
01C0701 ANL-LINE 1051  
01C0703 ANL-LINE 1053  
01/31/09:20:21 1 01/31/20:26:05 1 255 a  
01/31/20:26:18 1 01/31/20:26:18 7 4  
01/31/20:26:18 2 01/31/20:26:18 8 4  
01/31/20:34:35 1 01/31/20:34:35 1 1  
a
a
a
a
a
01A  
TDM-CLK  
0
0
01C1505 CO-TRK  
01C1505 CO-TRK  
078/001 3329 57408 01/31/20:26:07 1 01/31/20:27:28 1 5  
078/001 1537 01/31/20:26:52 1 01/31/20:28:41 1 5  
Command successfully completed  
display events  
A vector event is the occurrence of something unexpected during a  
vector-routed call due to resource exhaustion or faulty vector programming. For  
example, route-step failures are typically due to the programming of an invalid  
extension. These types of failures are not due to faulty hardware or system  
software error and do not constitute incorrect feature operation. This command  
allows you to diagnose and correct vectoring problems due to the  
above-mentioned causes. See DEFINITYCommunications System Generic 3 Call  
Vectoring and Expert Agent Selection (EAS) Guide, 555-230-520, for information  
on how to interpret this report.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
display events  
init  
none  
none  
inads  
craft  
cust  
rcust  
Input form  
The following entry form is displayed to allow limiting the report to events of a  
certain type or from a defined time period.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display events  
2
2-68  
display events  
Page 1 of 1  
SPE B  
EVENT REPORT  
The following options control which events will be displayed.  
EVENT CATEGORY  
Category: vector  
REPORT PERIOD  
Interval: _a_  
SEARCH OPTIONS  
From: __/__/__:__ To: __/__/__:__  
Vector Number: ___  
Event Type: _____  
Field descriptions  
Category  
Vectorspecifies the type of event report to display and is the only  
valid entry.  
Report Period  
The fields in this section allow you to view only those vector events that  
occurred within a specific time period. If these are left blank, all vector  
events recorded are displayed.  
Interval:  
This field specifies a display of all events within the last time period of  
the type Enter the first letter of one of the following selections: all,  
month, day, hour, minute.  
Start/Stop  
Time  
The starting and ending times of the interval to be reported in 24-hour  
notation.  
Vector Number  
The number of the vector (1-256) for which events will be reported. If  
this field is left blank, events for all vectors are reported.  
Event Type  
Specific types of vector events are associated with numbers from  
50000 to 50999. Entering one of these numbers limits the report to  
events of this type. If this field is left blank, events for all types of  
vectors are reported.  
Output  
See DEFINITY Communications System Generic 3 Call Vectoring and Expert  
Agent Selection (EAS) Guide, 555-230-520, for more information on how to  
interpret this report. In particular, the Event Data 2field is associated with  
possible causes and repair strategies for the event.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display initcauses  
2
2-69  
The following example shows a typical vector event report.  
display events  
Page 1  
SPE B  
EVENTS REPORT  
Event Event  
Type Description  
Event  
Data 1  
Event  
Data 2 Occur  
First  
Last  
Occur  
Evnt  
Cnt  
50020 Call not queued  
256/5  
B
09/28/13:43 09/28/13:43 1  
50541 Not a messaging split Split 89 4C 09/28/13:43 09/28/13:43 1  
Field descriptions  
Event Type  
A number from 50000 to 50999 that identifies what type of vector event  
occurred.  
Event  
A text string describing the event.  
Description  
Event Data 1  
If in the format number/number such as “200/10”, this indicates the  
vector number and step number associated with the event. If in the  
format “Split number” such as “Split 2”, this indicates the split number.  
Event Data 2  
First Occur  
Last Occur  
Evnt Cnt  
Additional data concerning the event encoded as a hex number.  
The date and time when the vector event first occurred.  
The date and time when the vector event last occurred.  
The total number of times, up to 255, that vector events of this type  
have occurred.  
display initcauses  
The display initcauses command displays a history of recovery steps taken by  
the system. Each time the system performs some type of recovery (due to user  
request or a hardware or software problem), the recovery information is stored.  
The software error log also contains information pertaining to restarts. If a reset 4  
(reboot) occurs, the software error log is also be stored. Information in the  
software error log should be used in conjunction with information in the initcauses  
log.  
The history of the last 16 restarts performed by the system will be recorded to the  
initcauses buffer in chronological order. This buffer fills an entire screen with  
information if it is completely full. Power failures in the processor complex wipe  
out the entire initcauses buffer.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display initcauses  
2
2-70  
Feature  
Action/Object  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
display  
Report sent to printer  
init  
none  
none  
initcauses  
inads  
craft  
nms  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
display initcauses  
display initcauses print  
display initcauses schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
The following example shows the output from the display initcauses command.  
display initcauses  
INITIALIZATION CAUSES  
Cause  
Action  
Escalated  
Carrier  
Time  
System Technician Request  
Upgrade Software  
Software Request  
4
2
1
no  
no  
no  
1A  
1A  
1A  
08/05 9:15  
08/05 9:29  
08/09 2:34  
Command successfully completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display initcauses  
2
2-71  
Field descriptions  
Cause  
■ Bad Memory: A defective memory circuit pack generating too many  
errors caused a restart.  
■ System Technician Request: The restart was performed  
because of system technician demand. A system  
technician-requested reset system 4 command entry should always  
precede an upgrade software command entry.  
■ Failed Interchange: A “hot-start” interchange (system  
technician-demanded, scheduled, or software-requested) failed  
because shadowing was disabled.  
■ Initialized: This is always the first entry in the history and is  
present until more than 15 restarts have been performed.  
■ LMM Request: A sanity time-out was requested by the LMM  
firmware. The three processor circuit pack LEDs blink until the sanity  
timer goes off. The LMM requests a restart like this when it gets into  
trouble, usually with memory.  
■ Maintenance Reset: This refers to resets of the SPE by  
maintenance in SPE Down mode in which maintenance periodically  
tries to awaken the SPE.  
■ Oryx Request: A sanity time-out was requested by the Oryx  
operating system. The three processor circuit pack LEDs blink until  
the sanity timer goes off. Oryx requests a restart like this when it gets  
into trouble, usually with software.  
■ Sanity Timer Reset: The sanity timer on the processor timed out  
and reset the system. This event usually indicates a software fault.  
■ Software Request: Software requested the system restart.  
■ Unknown: A restart that could not be classified. The Software Error  
Log may contain more information about the restart.  
■ LMM Put Fail: This initcause occurs when the LMM has failed to  
place the request for initcause message in the DPR. This could occur  
if the MTP does not respond to the DPR handshake. Level of Restart:  
Warm (escalation turned on).  
■ LMM Get Fail: This initcause occurs when the LMM does not  
receive a response to the request for initcause message from the  
MTP. This could occur if the MTP is not taking messages out of the  
DPR. Level of Restart: Warm (escalation turned on).  
■ MTP Reset Unknown: This initcause occurs when the LMM has  
reset the MTP during the process of trying to get initcause from the  
MTP. Level of Restart: Warm (escalation turned on).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display memory-configuration  
2-72  
Action  
The level of recovery performed by the system. The recovery levels  
follow:  
Reset system 1 (Warm)  
Reset system 2 (Cold-2)  
Reset system 3 (Cold-1)  
Reset system 4 (Reboot)  
Reset system 5 (Extended Reboot)  
Escalated  
Whether the restart was escalated to a higher level to clear the problem.  
There is a software escalation strategy that can cause a higher level  
restart than the one previously performed to be executed if the need  
arises.  
Carrier  
Time  
Indicates the carrier on which the recovery was performed (1A).  
The date (month and day) and time of the restart.  
display memory-configuration  
This command indicates the total memory available for the active processor.  
Feature  
Action/ Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
display  
memory-  
configuration  
long  
short  
Option required to display the SPE  
Flash ROM and DRAM  
configuration.  
init  
none  
none  
inads  
craft  
cust  
1
print  
Report sent to printer  
browse  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
display memory-configuration  
display memory-configuration  
long  
1
2
The long and short options are the same.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display node-names  
2
2-73  
Output  
The following example shows the output from the display memory command.  
display memory-configuration  
PROCESSOR MEMORY-CONFIGURATION  
(M bytes)  
SPE_A  
Flash ROM:  
Total DRAM:  
16  
16  
Command successfully completed  
Command:  
display node-names  
This command displays a list of the administered node names.  
Feature  
Action/ Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
display  
print  
Example:  
init  
none  
none  
node-names  
schedule  
display node-names  
inads  
craft  
Output  
The following example shows the output from the display node-names  
command.  
Page 1  
page 1 of 6  
NODE NAMES  
MSA Names  
Audix Name  
1. _______  
IP address  
IP Address  
___.___.___.___ 1. _______  
___.___.___.___ 2. _______  
___.___.___.___ 3. _______  
___.___.___.___ 4. _______  
___.___.___.___ 5. _______  
___.___.___.___ 6. _______  
___.___.___.___ 7. _______  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
2. _______  
3. _______  
4. _______  
5. _______  
6. _______  
7. _______  
8. _______  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display node-names  
2
2-74  
Field descriptions (page 1)  
Audix Name  
Identifies the name of the adjunct or switch node. Enter 1-7  
characters for audix or msa; 1-20 characters for others. Default is  
blank.  
IP Address  
IP address for the adjunct or switch. Enter 0 - 255 or leave blank  
(default).  
MSA Names  
MSA node name (up to 7 characters)  
IP Address  
IP address for the adjunct or switch. Enter 0 - 255 or leave blank  
(default).  
Page 2  
Page 2 of 6  
NODE NAMES  
Name  
IP Address  
Name  
IP Address  
1. Default  
0. 0. 0. 0. 17. _______________  
___.___.___.___ 18. _______________  
___.___.___.___ 19. _______________  
___.___.___.___ 20. _______________  
___.___.___.___ 21. _______________  
___.___.___.___ 22. _______________  
___.___.___.___ 23. _______________  
___.___.___.___ 24. _______________  
___.___.___.___ 25. _______________  
___.___.___.___ 26. _______________  
___.___.___.___ 27. _______________  
___.___.___.___ 28. _______________  
___.___.___.___ 29. _______________  
___.___.___.___ 30. _______________  
___.___.___.___ 31. _______________  
___.___.___.___ 32. _______________  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
___.___.___.___  
2. _______________  
3. _______________  
4. _______________  
5. _______________  
6. _______________  
7. _______________  
8. _______________  
9. _______________  
10. _______________  
11. _______________  
12. _______________  
13. _______________  
14. _______________  
15. _______________  
16. _______________  
Field descriptions (page 2)  
Name  
Non-specific node name (up to 15 characters each) for CMS  
nodes, DCS nodes, and so forth. Valid entries are alpha-numeric  
and/or special characters for identification.  
IP Address  
IP address for the adjunct or switch. Enter 0 - 255 or leave blank  
(default).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display port  
2
2-75  
display port  
This command displays the port location, the equipment connected to the port,  
and the means by which the port can be identified (for example, an extension  
number, the trunk group and member, and so on).  
Action/  
Object  
Feature  
Interactions  
Qualifier  
location  
print  
Qualifier Description  
Port address (PCSSpp)  
Report sent to printer  
Permissions  
Defaults  
display port  
init  
none  
none  
inads  
craft  
cust  
schedule  
Command is validated and then a  
scheduling form displays to  
browse  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
display port 1c0801  
display port 1c0802 print  
display port 2c1504 schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
The following example shows the output for the display port 1c0801 command.  
display port 1c0801  
SPE A  
PORT INFORMATION  
Port: 01C0801  
Equipment Type: Station  
Identification: 1021  
Field descriptions  
Port:  
Port address (cabinet-carrier-slot-circuit)  
Equipment Type:  
Hardware that is physically connected to the specified port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display synchronization  
2
2-76  
Depends on the hardware that is physically connected to the port:  
Identification:  
If hardware is  
The field contains  
station  
station extension  
trunk  
modem pool  
trunk group and member number)  
modem pool group number  
display synchronization  
This command calls up the synchronization form where the administered  
synchronization stratum and reference sources are displayed. (No changes can  
be made to the system synchronization with this command.)  
Action/  
Object  
Feature  
Interactions  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
display  
Report sent to printer  
init  
none  
See below  
synchron-  
ization  
inads  
craft  
cust  
rcust  
bcms  
browse  
schedule  
Command is validated and then a  
scheduling form displays to schedule  
execution of the command. The  
command is then placed in the  
command queue and is executed at the  
specified time. The information  
displayed by the command is sent to the  
1
system printer instead of the screen.  
Examples:  
display synchronization  
display synchronization print  
display synchronization schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Feature Interactions  
■
A DS1 interface or a UDS1 board that has been selected as either a  
primary or secondary synchronization source cannot be removed on the  
DS1 circuit pack administration form or the regular circuit pack  
administration form.  
Output  
The following example shows the output for the display synchronization  
command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display system-parameters duplication  
2-77  
display synchronization  
Page 1 of 2  
SYNCHRONIZATION SOURCE (Synchronization Plan circuit pack location)  
Stratum: 4  
Primary:  
Secondary:  
DS1 CIRCUIT PACKS  
Location  
Name  
Slip  
Location  
Name  
Slip  
01C10 D92D1 ds1 1c10  
01C11 D92D1 ds1 1c11  
n
n
NOTE: DS1 and BRI Trunk sources result in stratum 4, type II synchronization  
Field descriptions  
Stratum:  
Synchronization stratum that is used (3 or 4)  
Primary:  
Secondary:  
Location:  
Name:  
First choice system synchronization source (blank = no  
synchronization); valid only if stratum 4 synchronization specified  
Second choice system synchronization source (blank = no  
synchronization); valid only if stratum 4 synchronization specified  
Circuit pack location (cabinet-carrier-slot) of all administered DS1 circuit  
packs are listed here.  
User-defined name administered for the DS1 circuit pack. Blank means  
no user-defined name administered.  
Slip:  
If the DS1 circuit pack has slip alarm, field shows y; otherwise, n.  
Port  
Network:  
Stratum 3 only; specifies the port network supplying synchronization  
through the tone clock circuit pack.  
display system-parameters duplication  
This command displays the status (enabled or disabled) of Switch Processing  
Element (SPE) and Port Network Connectivity (PNC) duplication. The following  
must be duplicated:  
■
Each switch node record and every switch node with its duplicate (cabinet  
administration is a prerequisite)  
■
Every fiber link containing either an expansion interface circuit pack as an  
endpoint, or a DS1-C (fiber link administration is a prerequisite; circuit  
pack administration then follows duplication administration)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display system-parameters duplication  
2-78  
All nonduplicated switch node interfaces (SNI) to SNI fiber links are automatically  
duplicated.  
NOTE:  
You must enable (y) the PNC Duplicationfield on the customer options  
form (change system-parameters customer-options) before you can do  
any duplication administration.  
PNC Duplication cannot be enabled until all pnc-a and pnc-b boards are  
released from the “busyout” state.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
display  
duplication  
SPE or PNC duplication  
init  
none  
none  
system-  
parameters  
inads  
craft  
Examples:  
display system-parameters  
duplication  
Output  
The following example shows the output from the display system-parameters  
duplication command.  
Page 1 of 1  
DUPLICATION-RELATED SYSTEM PARAMETERS  
Enable Operation of SPE Duplication? y  
Enable Operation of PNC Duplication? y  
Screen 2-4. Duplication-Related System Parameters form (page 1 of 1)  
Field descriptions  
Enable Operation  
of SPE  
Status of SPE duplication: y is enabled; n (default) is disabled  
Duplication?  
Enable Operation  
of PNC  
Duplication?  
Status of PNC duplication: y is enabled; n (default) id disabled.  
This field appears only if PNC Duplicationhas been enabled on  
the System-Parameters Customer-Options form.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display system-parameters maintenance  
2-79  
display system-parameters  
maintenance  
This command displays the translation data for maintenance-related system  
parameters.  
Feature  
Action/Object  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
display  
Report sent to printer  
init  
none  
none  
system-  
parameters  
maintenance  
inads  
craft  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
super-user  
Maintain  
Switch  
Circuit  
Packs  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
permissions  
1
printer instead of the screen.  
Examples:  
display system-parameters  
maintenance  
display system-parameters  
maintenance print  
display system-parameters  
maintenance schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
The following display shows a typical result when display system-parameters  
maintenance is entered.  
display system-parameters maintenance  
MAINTENANCE-RELATED SYSTEM PARAMETERS  
Page  
1 of 3  
OPERATIONS SUPPORT PARAMETERS  
Product Identification: 1000000000  
First OSS Telephone Number: 5551212  
Second OSS Telephone Number: 5551213  
Alarm Origination to OSS Numbers: both  
Cleared Alarm Notification? y  
Restart Notification? y  
Abbrev Alarm Report? y  
Abbrev Alarm Report? n  
Test Remote Access Port? n  
CPE Alarm Activation Level: none  
Customer Access to INADS Port? n  
Repeat Dial Interval (mins): 7  
SCHEDULED MAINTENANCE  
Start Time: 22: 00  
Stop Time: 04: 00  
Daily Maintenance: daily  
Save Translation: daily  
Control Channel Interchange: no  
SPE Interchange: no  
System Clocks Interchange: no  
EXP-LINK Interchange: no  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display system-parameters maintenance  
2-80  
display system-parameters maintenance  
MAINTENANCE-RELATED SYSTEM PARAMETERS  
MAINTENANCE THRESHOLDS ( Before Notification )  
Page 2 of 3  
Minimum Threshold for TTRs: 4  
Minimum Threshold for CPTRs: 1  
Minimum Threshold for Call Classifier Ports: _  
TERMINATING TRUNK TRANSMISSION TEST (Extension)  
Test Type 100:  
Test Type 102:  
Test Type 105:  
ISDN MAINTENANCE  
ISDN-PRI TEST CALL Extension: _____  
ISDN BRI Service SPID: _____  
DS1 MAINTENANCE  
DSO Loop-Around Test Call Extension: 1001  
LOSS PLAN (Leave Blank if no Extra Loss is Required)  
Minimum Number of Parties in a Conference Before Adding Extra Loss: _____  
SPE OPTIONAL BOARDS  
Disk? y  
Packet Intf1? y  
Packet Intf2? n  
Packet Intf3? n  
display system-parameters maintenance  
Page 3 of 3  
MAINTENANCE-RELATED SYSTEM PARAMETERS  
Modem Connection: external  
Data Bits: 8  
Parity: none  
Modem Name:  
RTS/CTS Enabled: &H1  
Asynchronous Data Mode:  
DTE Auto-Data Speed:  
Auto Answer Ring Count (rings): S0=10  
Dial Type: T  
Adjustable Make/Break Ratio:  
Dial Command: D  
Disable Data Compression: &K0  
Enable Error Control:  
No Answer Time-out: S7=255  
Misc. Init. Param:  
Help/Error Message Line  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display system-parameters maintenance  
2-81  
Field descriptions  
Defaults for data entry fields are listed in parentheses.  
Product  
Identification  
10-digit number (starting with 1) that identifies the switch to an  
Operations Support System (OSS), for example, INADS.  
First OSS Telephone  
Number  
First telephone number that the switch dials to report alarms;  
must be obtained from the National Customer Support Center  
(NCSC) or the TSC. (# and * are not allowed in the telephone  
number.)  
Abbrev Alarm Report  
Enables the Abbreviated Alarm Report feature for the first OSS.  
(yes)  
Second OSS Telephone  
Number  
Second telephone number that the switch dials to report alarms;  
must be obtained from the National Customer Support Center  
(NCSC) or the TSC. (# and * are not allowed in the telephone  
number.)  
Abbrev Alarm Report  
Enables the Abbreviated Alarm Report feature for the second  
OSS. (no)  
Alarm Origination to  
OSS Numbers  
One of four options for alarm origination (neither):  
■ If both, all Major and Minor alarms result in an automatic  
call to both OSS telephone numbers. Both OSS telephone  
numbers must be administered.  
■ If first-only, all Major and Minor alarms result in an  
automatic call to the first OSS number only. The switch does  
not call the second OSS telephone number even if the  
number is administered. The first OSS telephone number  
must be administered  
■ If neither, alarm origination does not take place. Warning  
alarms are not reported to either numbers.  
■ If second-as-backup, all Major and Minor alarms result in  
an automatic call to the first OSS telephone number. If  
calling the first OSS telephone number fails four attempts,  
the switch starts to call the second OSS telephone number  
as a backup until calling the first OSS telephone number  
becomes successful. Both OSS telephone numbers must be  
administered.  
Before Release 5, the name of this field is Alarm  
Origination Activated. If Alarm Origination is deactivated,  
both Cleared Alarm Notification and Restart Notification are  
disabled, even though they may still be activated in the  
administration.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display system-parameters maintenance  
2-82  
Cleared Alarm  
Notification  
Enables the switch to originate a call to the OSS and send an  
alarm resolution message whenever all previously-reported  
Major and Minor alarms are resolved. Alarm Origination must be  
activated in order for Cleared Alarm Notification to work. (no)  
Restart Notification  
Suspension Threshold  
Enables the switch to originate a call to the OSS and report any  
system restarts caused by problems with the switch.  
The threshold for suspending Cleared Alarm Notification (1-15).  
Some problems may cause alarms to be generated and then  
resolved repeatedly. To detect these problems (by not sending  
additional Cleared Alarm notifications to indicate a problem-  
free system), the switch suspends Cleared Alarm Notification  
when it has reported this administrable number of Cleared  
Alarm notifications in a 24-hour period. A suspended Cleared  
Alarm Notification is only enabled again with a successfully  
completed “logoff” command, a system reset, or when the  
threshold is changed. This field is irrelevant if Cleared Alarm  
Notification or Alarm Origination is disabled.  
Test Remote Access  
Port  
Specifies whether testing of the remote access port on the  
SYSAM circuit pack is enabled. This field should read yes  
whenever there is an INADS line connected to the switch and  
there is a maintenance contract in effect so that alarm  
origination capability is maintained.  
CPE Alarm Activation  
Level  
Indicates the minimum level (Major, Minor or Warning) at which  
the Customer-Provided Equipment (CPE) alarm is activated. If  
the level is none, the CPE does is not activated for any alarm.  
(none)  
NOTE:  
The CPE alarm is always activated when the switch goes  
into Emergency Transfer, regardless of the CPE Alarm  
Activation Level setting.  
Customer Access to  
INADS Port  
Provides the capability to prohibit access to system  
administration and maintenance interface, via the INADS port  
when using customer login ID’s. This field can only be activated  
by Lucent services through system-parameters maintenance  
administration.(no)  
Repeat Dial Interval  
(MMS)  
Indicates the number of minutes that the system must wait  
before attempting another call origination to an OSS. This timer  
is triggered by the lack of a far-end acknowledgment. (7)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display system-parameters maintenance  
2-83  
Scheduled Maintenance  
A series of maintenance tests and operations runs automatically every day  
according to the schedule and settings specified in the following fields.  
Start Time  
Stop Time  
The hour and minute (24-hour notation) at which daily scheduled  
maintenance begins. (22:00)  
Time (hour and minute) when scheduled daily maintenance stops.  
If any daily maintenance operations are not completed by this time,  
the system notes where in the sequence it stopped and perform  
those operations during the next scheduled daily maintenance.  
Daily  
Maintenance  
This display-only field simply represents the series of tests that are  
always run by maintenance software as part of daily maintenance.  
Save Translation  
This field indicates on which days translation data in memory will  
automatically be saved to the Mass Storage System disk and/or  
tape devices during scheduled maintenance. The save operation is  
first made to disk, followed by a disk backup to tape. On systems  
with duplicated SPEs, translation data is saved on both SPEs. Valid  
entries are daily, days of the week, or no. “No” specifies that no  
automatic saves are to be executed. (daily)  
Control Channel  
Interchange  
Each port network has a pair of TDM busses called A and B, each  
of which has a set of time slots dedicated to use by the control  
channel. At any one time, the control channel in each PN is carried  
on only one of the two busses. This field indicates on which days  
the control channel in each port network will be switched from one  
of the paired TDM busses to the other. Valid entries are daily, days  
of the week, or no. “No” specifies that no interchange be executed.  
(no)  
EXP-LINK  
Interchange  
This field indicates whether or not the expansion links between  
port-networks are interchanged as part of scheduled maintenance.  
The value “daily'' means that EXP-LINK interchange occurs  
automatically everyday. The value “no'' means that EXP-LINK  
interchange is not done automatically as part of scheduled  
maintenance. Values represented by the days of the week mean  
that EXP-LINK interchange occurs automatically on the specified  
day only. Since EXP-LINK interchange only applies to duplicated  
systems, simplex systems do not display this field. (no)  
Minimum  
Threshold for  
TTRs  
When the number of touch tone receivers (TTRs) in service falls  
below this number (4 to 200), a WARNING alarm is raised against  
TTR-LEV. These are also known as dual-tone multifrequency  
receivers (DTMRs). There are 8 TTRs on each TN2182. To alarm  
the first occurrence of a TTR being taken out of service, set this  
field to the total number of TTRs in the switch.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display system-parameters maintenance  
2-84  
Minimum  
Threshold for  
CPTRs  
When the number of call progress tone receivers in service falls  
below this number (2 to 100), a WARNING alarm is raised against  
TTR-LEV. These are also known as general purpose tone detectors  
(GPTDs). There are 8 CPTRs on each TN2182. To alarm the first  
occurrence of a CPTR being taken out of service, set this field to  
the total number of CPTRs in the switch.  
Minimum  
When the number of call classifier ports (CLSFY-PTs) in service falls  
below this number, a WARNING alarm is raised against TTR-LEV.  
Valid entries are 1 to 200. There are 8 ports on each TN2182 circuit  
pack. To alarm the first occurrence of a CLSFY-PT being taken out  
of service, set this field to the total number of CLSFY-PTs.  
Threshold for  
Call Classifier  
Ports  
Test Type 100,  
Test Type 102,  
Test Type 105  
An extension assigned to receive tie-trunk calls from other switches  
with test line origination capability. The system responds by  
sending a sequence of test tones. Test Type 100 tests far-end to  
near-end loss and C-message by sending:  
■ 5.5 seconds of 1004 Hz tone at 0dB  
■ Quiet until disconnect; disconnect is forced after one minute  
ISDN-PRI Test  
Call Extension  
The extension used by a far-end ISDN node to place a call to the  
system to test the ISDN-PRI trunks between the far-end and the  
system.  
ISDN-BRI Service  
SPID  
This field shows whether or not the link is associated with the  
Service SPID. If the link is associated with the Service SPID, this  
field contains a “yes” and the extension field is blank; otherwise,  
this field is blank. Service SPID is a feature used by the system  
technician to check building wiring between the switch and the BRI  
endpoint.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display system-parameters maintenance  
2-85  
DSO Loop-Around  
Test Call  
Extension  
Extension number for the test call. This test extension number is  
used to establish a loop-around connection on the selected trunk.  
The DSO Loop-Around Test Call feature is used primarily for testing  
DSO channels associated with non-ISDN-PRI trunks. The  
loop-around is activated by dialing the test extension number.  
Multiple DSO Loop-Around connections can be set up by placing  
multiple calls to the loop-around extension.  
The DS0 Loop Around feature provides a loop around connection  
for incoming non-ISDN DS1 trunk data calls. This feature is similar  
to the far-end loop around connection provided for the ISDN Test  
Call feature. This DS0 loop around is provided primarily to allow a  
network service provider to perform facility testing at the DS0 level  
before video teleconferencing terminals are installed at the PBX.  
The feature is activated on a call-by-call basis by dialing a test call  
extension specified on the second page of the System Parameters  
Maintenance form. No special hardware is required. When the test  
call extension is received by the PBX, a non-inverting, 64 kbps  
connection is set up on the PBX’s Time Division Multiplexed bus.  
More than one loop around call can be active at the same time.  
For calls routed over the public network using the ACCUNET  
Switched Digital Service (SDS) or Software Defined Data Network  
(SDDN), the data transmission rate is 56 Kbps, since robbed bit  
signaling is used. For calls established over a private network using  
common channel signaling, the full 64 kbps data rate is available.  
When the incoming trunk group is used only for data calls (SDS),  
the Communications Type on the associated Trunk Group form  
should be set to “data.” When the incoming trunk group is used for  
robbed bit alternate voice and/or data (SDN/SDDN), the  
Communications Type on the Trunk Group form should be set to  
rbavd (robbed bit alternate voice data). For private network trunks  
using common channel signaling, the Communications Type on the  
associated Trunk Group form can be set to “avd.”  
Loss Plan  
Use only when extra loss is required to maintain quality of  
transmission on conference calls. Leave this field blank if no extra  
loss is required. If extra loss is required, enter digits as shown  
below.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display system-parameters maintenance  
2-86  
No. of Parties to Be  
Conferenced  
Enter Digit  
3
4
5
6
7
2
3
4
5
6
SPE Optional  
Boards:  
These fields indicate whether a Disk circuit pack is present in the  
system, and which Packet Interface slots are administered. If a  
Packet Interface circuit pack is physically present, the  
corresponding Packet Interface field is set to y when the system  
boots, and no change to that field is allowed. If the system is  
equipped with duplicated SPEs, a Packet Interface field is set to y  
when either SPE carrier contains a Packet Interface circuit pack in  
the corresponding position. If a Packet Interface circuit pack is not  
present, then the value for the Packet Interface field is read from  
translation data stored on disk or tape. If the field is set to n, a  
Packet Interface circuit pack may be administered by changing the  
corresponding Packet Interface field to y.  
Modem Connection  
On page 3 of the example forms shown below, there are 11 fields that are hidden  
when the Modem Connection?field is set to none. In this example the Modem  
Connectionfield is set to external, and these additional 11 fields are visible.  
The first 2 fields on page 3 help setup the data format for the serial data from the  
switch to the modem.There are only two valid combinations for these 2 fields:  
■
Data Bits = 8, Parity = None  
■
Data Bits = 7, Parity = (odd, even, mark, or space)  
The remaining fields are listed below:  
Modem Connection  
None or external (none)  
Modem Name  
This field is 20 characters long and will permit alpha-numeric  
characters to provide a unique qualifier for a given modem. ( )  
RTS/CTS Enabled  
This field will inform the modem that communication with the data  
source UART will be driven with RTS/CTS flow control. This field is 6  
characters long and is case in-sensitive. (&H1)  
Asynchronous  
Data Mode  
This field will configure the modem as an asynchronous  
communications device. This field is 8 characters long and is case  
in-sensitive. ( )  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
display system-parameters maintenance  
2-87  
DTE Auto-Data  
Speed  
This option will adjust the speed of the data source (DTE) UART to  
the outgoing (modem-to-modem) data rate. So, at maximum this  
speed would be 9600 baud. This field is 6 characters long and is  
case in-sensitive.  
Note that this field sets the link speed between the switch and the  
modem. It does not set the speed of the modem. It is not desirable  
to have the serial data fill the modem buffer faster than the outgoing  
data rate especially because data compression is disabled. ( )  
Disable Data  
Compression  
This field will turn off the default data compression algorithms that  
are in use by most consumer modems. This field is 6 characters  
long and is case in-sensitive. (&K0)  
Enable Error  
Control  
This field will turn on the V.42 LAPM and MNP error control  
protocols, if available on the modem. This field is 6 characters long  
and is case in-sensitive.  
This V.42/MNP/Buffer mode first attempts to negotiate V.42 error  
control with the remote modem. If this fails, then the modem  
transitions to MNP, and if this fails then no error control is used. ( )  
Misc. Init.  
Param  
This field supports any initialization parameters that are not already  
specified. The AT commands specified in this free-form field will be  
always the last initialization parameters to be sent to the external  
modem. This field is 20 characters long and is case in-sensitive. ( )  
Auto-Answer Ring  
Count  
This field controls the number of rings required before the modem  
automatically answers an incoming call, if and only if the switch  
doesn’t answer first. (If the switch is healthy, it answers an  
incoming within the first few rings.) This field is 6 characters long  
and is case insensitive. Typically, the maximum permissible value  
for this register is 255. The values 1-255 denote the number of  
incoming ring cycles. (S0=10)  
NOTE:  
The number of rings is optimally set above 5, and if at all  
possible, keep the default of S0=10.  
Dial Type  
This field controls the type of inter-register signaling to be used  
between the modem and the Central Office. Use “T” for tone dialing  
and “P” for pulse dialing. The field length is be 3 characters long  
and is case in-sensitive. This field will be concatenated with the dial  
string. (T)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display test-schedule  
2
2-88  
Adjustable  
Make/Break Ratio  
This field can be of particular importance when using a modem that  
may be transferable from country to country. The intent of this field  
is to control the make/break ratios of pulses and DTMF dialing. The  
Intel product information has support for the different make/break  
options for pulse dialing only.  
Intel uses the option “&P0” to select a ratio of 39% make and 61%  
break for communication within the U.S. and Canada. The option  
“&P1” sets a ration of 33% make and 67% break for the U.K. and  
Hong Kong.  
This field is 5 characters long and is case in-sensitive. ( )  
Dial Command  
This field simply denotes the dialing command of the modem. This  
is a fairly standard command. (D)  
No Answer  
Time-Out  
Most off-the-shelf external modems provide a timer that abandons  
any outbound data call after a predetermined interval. Some  
modems provide for this timer to be disabled, thus allowing an  
outbound call to ring indefinitely. AT&T Paradyne does not provide  
this capability with their modem line, because it is generally  
undesirable to have an outbound call attempt ring indefinitely.  
The internal modem must have this parameter disabled or set to at  
least 255 seconds.  
This is a non-administrable parameter. For the external modem  
connection, this parameter will be the first initialization string to be  
transmitted to the external modem. This field will be visible on the  
administration form in display mode only.  
This hardcoded constant can be overridden for type approval  
applications, specifically in the U.K and other Western European  
nations, by the use of the “Misc. Init. Param:” field. (S7=255)  
display test-schedule  
Automatic Transmission Measurement System (ATMS) provides advanced  
maintenance procedures for monitoring system trunk facilities. This system  
performs transmission tests on system trunks to determine if trunks are  
performing satisfactorily. These tests can be initiated in two ways:  
demand  
user enters command at the System Administration  
Terminal (SAT) to initiate a test immediately  
scheduled  
schedules tests through a schedule form to automatically  
initiate tests at a predetermined time  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display test-schedule  
2
2-89  
Output  
The following is the output from the display test-schedule n command.  
Page 1 of 1  
ATMS TRUNK TEST SCHEDULE  
Schedule No: __  
Schedule Time: __:__  
Schedule Date: __/__/__  
OTL Throttle: _  
Schedule Test Days  
SU: _ TU: _ TH: _ SA: _  
MO: _ WE: _ FR: _  
Interval: __  
Duration: __  
Test Type: ______  
Trk Bgn End  
Grp Mem Mem  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
Trk Bgn End  
Grp Mem Mem  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
Trk Bgn End  
Trk Bgn End  
Grp Mem Mem  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
Trk Bgn End  
Grp Mem Mem  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
Grp Mem Mem  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
___ ___ ___  
Field descriptions  
Schedule  
The current schedule number.  
Schedule Time  
The hour and minute that the test begins (24-hour time, with "00:00"  
being midnight). This time must be greater than the current time.  
Schedule Date  
Month (1 to 12), day (1 to 31), and year on which testing begins  
(default is the system date). This date must be equal to or greater  
than the current date.  
Schedule Test  
Days  
A y next to the days of the week indicates which days of the week  
this test runs.  
Interval  
The length of this schedule in weeks. If this field is 0 (default), the  
schedule runs on the specified days only once.  
OTL Throttle  
The number of concurrent tests run within a schedule. This  
guarantees that all trunk members within a schedule are tested  
serially or if multiple trunk members are tested from the same  
schedule.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display test-schedule  
2
2-90  
Test Type  
One of the following types of test to be performed on the trunk  
group/members in this schedule:  
■ full (default) runs the most comprehensive test and collects all  
associated measurements for each TTL type.  
■ supv performs a supervision test and only confirms the  
presence of the test set at the far end. No measurements are  
taken for this test.  
■ no-st runs the "full" test, but skips any self-test sequences. This  
saves about 20 seconds on the type 105 test and does not  
have any effect on type 100 or 102 tests.  
■ no-rl runs the "full" test, but skips any return loss sequences.  
This saves about 20 seconds on the type 105 test and does not  
have any effect on type 100 or 102 tests.  
■ no-st/rl runs the "full" test, but skips all self-test and return loss  
sequences. This saves about 40 seconds on the type 105 test  
and does not have any effect on type 100 or 102 tests.  
Duration  
Trk Trp  
The maximum number of hours (1 to 24) a schedule can remain  
active. Schedules continue to run until all trunk group/members for  
that particular schedule are tested or until the schedule duration is  
reached. If the duration is reached before all trunk  
groups/members can be tested, the schedule stops.  
The trunk group numbers to be tested when this schedule runs.  
There is no limit to the number of times that a trunk group can  
appear on any particular schedule, or to the number of different  
schedules in which a trunk group can appear. Default is blank.  
Bgn Mbr  
End Mbr  
The beginning member number of the trunk group to be tested;  
default is 1.  
The ending member number of the trunk group to be tested. This  
value must be greater than or equal to the value of the beginning  
member field.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
display time  
2
2-91  
display time  
This command displays the system time but does not allow for any changes to  
the system time.  
Feature  
Action/Object  
display time  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
Report sent to printer  
init  
none  
Date and time  
are generally  
used by the  
switch.  
inads  
craft  
cust  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
browse  
1
printer instead of the screen.  
Examples:  
display time  
display time print  
display time schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
The following example shows the output for the display time command.  
display time  
DATE AND TIME  
DATE  
Day of the Week: Sunday  
Day of the Month: 1  
Month: January  
Year: 1990  
TIME  
Hour: 6  
Second: 20  
Minute: 8  
WARNING! Changing the date or time will impact BCMS, CDR and MEASUREMENTS.  
Field descriptions  
Day of the Week  
The day of the week that the system has stored.  
Day of the Month  
The numerical day of the month.  
Month  
The month of the year stored by the system.  
Year  
The current year stored by the system.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
download update-file  
2
2-92  
Hour  
The hour of the current day.  
Minute  
Second  
The number of minutes into the hour.  
The number of seconds into the minute stored by the system.  
download update-file  
The update file is transferred to the switch asynchronously from either an INADS  
host or a personal computer (PC) using the XMODEM protocol.  
Remote download  
Remote users can dial into the switch by either using the “call” command (from  
an INADS host) or by dialing the switch directly with a modem. Once the  
connection has been established, the user logs into the switch as a remote  
system access terminal (SAT) using the inads login.  
NOTE:  
Only the INADS and INIT logins have the necessary permission to send an  
update file to the switch.  
1. Type the download update-file command and press ENTER. “Please  
wait..."displays on the screen.  
After completing some initialization, "Please start file  
transmission now..."displays.  
2. Start an XMODEM session on the remote end and send the update file.  
a. INADS host: enter ~dload <file_name> to start the file  
transmission.  
b. PC: follow the instructions in the emulator’s manual for invoking an  
XMODEM session to send the update file.  
Each block is written to tape or flash card as it is received by the switch. The link  
level of XMODEM provide error detection and retransmission. Additional  
protection is provided within the application level. After the entire file has been  
written to tape or flash card, it is read back and each update file block is  
validated, and the file checksum is also checked. If the file appears to be sound,  
the status word in the header block is changed to indicate that it is a valid update  
file.  
There may be a delay between the end of the file transmission and command  
completion. This delay is caused by the patch application of any immediate  
sub-patches.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
download update-file  
2
2-93  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
download  
update-file  
init  
inads  
none  
See below  
Feature Interactions  
■
The form displayed for the list configuration software-vintage command  
has been modified to reflect the changes imposed by the flash  
architecture. The list configuration software command allows INADS to  
determine with one query the hardware configuration, software vintage,  
and patch identifier.  
■
■
There is no interaction with routine periodic or scheduled maintenance,  
because patches are only applied on restarts before the system is in  
normal operation.  
The flash checksum test acts as a backup check to ensure that the entire  
field update file was applied correctly. It can fail because of a bad  
checksum update from a poorly constructed update file or because the  
patching operation has aborted. When the flash Checksum Test fails, a  
MAJOR on-board alarm is raised on the processor/memory circuit pack.  
■
When checking the software, the test compares the memory resident  
software version and patch identifier. It also checks for the presence of a  
field update file and, if found, compares the old and new patch identifiers  
to make sure the same patch file id loaded on each processor. If the  
software or update files are inconsistent, the list configuration software  
command can be used to display the status of the patch file.  
Recovery procedures  
In the event of a failure encountered during the download and application of the  
update file, follow the recommended recovery procedures.  
Error on the download transmission  
If the error displayed on the terminal indicates that the download step in the  
process failed, there are several culprits:  
1. The transmission line could have been noisy. Retry after making all the  
following checks. Failed attempts take up room in the hard patch file and  
may require a warm start to clear the file.  
2. The user may have downloaded the tape/MIPS version of the patch  
instead of the flash version.  
3. The vintage of the update file may not match the vintage of software  
currently running in the system. Check the customer’s vintage using list  
configuration software and patch vintage provided in the  
documDeonwtnaltoiaodnf.rom Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
download update-file  
2
2-94  
4. The switch may have had difficulty in writing to the hard patch file. Check  
the hardware error log for processor/memory board failures.  
5. The hard patch file may be full. Issue a reset system 1. This should cause  
valid files to be applied and invalid ones to be erased.  
Error on Application of the Patch  
A patch may not have been applied for the following reasons:  
1. The memory card is write-protected. Remove this protection and issue a  
reset system x command  
2. The patch identifiers are inconsistent. Run list configuration software  
and compare the old_patch identifier with the values in the update file.  
3. The LMM encountered a problem with the patch file. This is unlikely  
because the same checks (and more) were performed when the file was  
downloaded, prior to marking the file valid. This implies that the memory  
that stored the update file was corrupted.  
a. Apply the back out file immediately to back out the changes.  
b. Run the flash checksum test to make sure the system is back to its  
prepatch state.  
c. Check the validity of the file again  
d. Try redownloading and applying the patch immediately.  
4. The LMM reports a hard error. Symptoms of this are an entry in the  
hardware error log for the processor/memory board (if you’re lucky), or  
extremely odd switch behavior followed by SPE down mode (if you’re not).  
The problem is that the LMM cannot complete the programming of  
memory with the result that memory is in a corrupted state. The only  
recovery is to get or order new software and processor/ memory circuit  
packs.  
Good application - bad patch  
This error is not caused by a failure in the download or application, but by a fault  
in the patch file itself. To recover from this type of problem, the back out file that  
backs out the patch should be downloaded and applied. This requires that the  
system be sane enough to receive the file correctly and be able to apply it.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
enable administered-connection  
2-95  
enable administered-connection  
This command restarts scheduled and periodic maintenance for a single or all  
administered connections and can be used to track the maintenance processing  
of administered connections without interference from other maintenance  
processing. This command also restarts the processing of in-line errors for all or  
the selected administered connection.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
enable  
administered-  
connection  
ac number  
The number of the administered  
connection  
init  
none  
none  
inads  
craft  
cust  
rcust  
mis  
all  
All administered connections are  
enabled.  
Examples:  
enable administered-connection 128  
enable administered-connection all  
enable mst  
Enables the message trace that is controlled according to the parameters  
created with the change mst command. If executed while the trace is enabled,  
the command has no effect and returns a screen message indicating that the  
command was successful.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
enable mst  
init  
none  
none  
inads  
enable suspend-alm-orig  
This command enables Suspend Alarm Origination for a board (including all  
ports and endpoints on the board) or for a port (including all endpoints on the  
port) for both on- and off-board alarms or for off-board alarms only. Many control  
circuit packs do not have a board location, so this command cannot support all  
circuit packs. Each enable command becomes a new entry or replaces an  
existing entry in the Suspend Alarm Origination table. A new entry that matches  
both the physical location and off-only, on-, and off-board specifications of an  
active entry replaces the active entry in the Suspend Alarm Origination table.  
On the command line, specify a time-out duration of 1 - 72 hours. The  
off-board-only is optional; if the keyword is not specified, the entry suspends  
Alarm Origination for both on-and off-board alarms.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
enable synchronization-switch  
2-96  
This command may be particularly useful for:  
■
■
Improved control over customer requests. For example, to suspend  
off-board DS1 alarms temporarily for customers that periodically  
disconnect DS1 trunks for testing or other business-related purposes.  
Improved control over external (non-Lucent) problems such as  
suspending off-board DS1 alarms before a customer resolves facility  
problems (for example, a T1 trunk that has developed an off-board  
condition).  
■
Improved control over internal (Lucent) problems that cannot be resolved  
immediately. For example, the command can be used to suspend Alarm  
Origination for a bad circuit pack detected late Friday night and dispatch  
personnel cannot respond until Monday.  
NOTE:  
Also see other Suspend Alarm Origination related commands, including  
disable suspend-alm-orig and list suspend-alm-orig.  
Action/  
Object  
Feature  
Interactions  
Qualifiers  
Qualifier Description  
Permissions  
Defaults  
enable  
suspend-  
alm- orig  
board/port  
location  
Physical location of the hardware  
init  
Both on- and  
none  
inads  
craft  
cust  
rcust  
off-board alarms  
if the off-board-  
only keyword is  
not specified  
optional; if not specified, both  
on-and off-board alarms suspended  
off-board-  
only  
No. of hours (1-72)  
Examples:  
enable suspend-alm-orig 1B03  
expires-in-hrs 3  
expires-in-  
hrs  
enable suspend-alm-orig 1B0701  
expires-in-hrs 72  
enable suspend-alm-orig 1B07  
off-board-only expires-in-hrs 24  
enable synchronization-switch  
This command re-enables automatic clock switching or returns the maintenance  
subsystem back to the normal state. The synchronization subsystem consists of  
the TDM bus clock, DS1 trunk board, and SPE-resident maintenance and  
administration software and provides error free digital communication between  
the switch and other PBXs, COs, or customer-premise equipment (CPE).  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
enable synchronization-switch  
init  
none  
none  
inads  
craft  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
enable test-number  
2
2-97  
enable test-number  
This command enables a previously disabled test number. At the next request by  
maintenance or the technician, this test number will run.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
enable  
test-number  
number  
The specific test number  
to re-enable  
init  
inads  
craft  
none  
The display  
disabled-tests  
command gives  
a list of all  
Example:  
enable test-number 102  
disabled tests.  
format card-mem  
This command erases and formats the active processor Flash Read-Only  
Memory card before writing translation, announcements, coredump, and  
firmware data.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
format  
card-mem  
Erases and formats the memory  
card for:  
init  
inads  
craft  
cust  
browse  
system  
none  
none  
translation  
announcements  
coredump  
translations only  
translations and announcements  
translations, announcements, and  
coredump  
firmware  
translations, announcements  
coredump, and firmware  
get vector  
This command displays the conditions and the Switch Processing Element (SPE)  
associated with a core dump of memory to tape or memory card. The dump  
occurs on the tape or disk of the previously active SPE or the SPE previously  
specified using the set vector command in systems with duplicated SPEs.  
!
CAUTION:  
The vector is cleared when a system restart of the proper level is performed  
regardless of whether the core is actually dumped.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
get vector  
2
2-98  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
get vector  
long  
Core dump timestamps printed; if  
SPEs are duplicated, timestamps  
are printed for both SPEs.  
init  
inads  
craft  
none  
none  
print  
Prints report on system printer.  
Examples:  
get vector  
get vector print  
get vector long  
get vector long print  
Output  
get vector  
GET RESULTS  
Core Dump Vector  
0
Set Vector Command Option  
spe-active  
Core Dump Time  
SPE_A  
SPE_B  
Command successfully completed  
Field descriptions  
Core Dump Vector  
A hexadecimal value representing the condition(s) that cause(s) a  
core dump. This hexadecimal value is a bit map of the four reset  
conditions (from least to most significant bit):  
■ warm start  
■ cold 2 restart  
■ cold 1 restart  
■ reboot.  
A value of 0 indicates that the vector is cleared or not set. See the  
Vector-Condition Mapping table that follows.  
Vector-Condition Mapping  
value warm-start cold-2 cold-1 reboot  
0
1
n
y
n
n
n
n
n
n
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
list communication-interface processor-channel  
2-99  
Vector-Condition Mapping  
value warm-start cold-2 cold-1 reboot  
2
3
4
5
6
7
8
9
a
b
c
d
e
f
n
y
n
y
n
y
n
y
n
y
n
y
n
y
y
y
n
n
y
y
n
n
y
y
n
n
y
y
n
n
y
y
y
y
n
n
n
n
y
y
y
y
n
n
n
n
n
n
y
y
y
y
y
y
y
y
SetVectorCommand  
Option  
The user-specified SPE prior to the core dump. For simplex SPE  
systems this field is always spe-activeunless the vector is  
cleared or not set.  
Core Dump Time  
The time of the core dump for SPE A. If the system has a simplex  
SPE, a timestamp for SPE A is displayed for SPE B. If the core  
dump cannot be accessed, can’t accessdisplays for the  
corresponding SPE. If the MSS device storing the core dump  
timestamp is busy for any reason, device busydisplays at the  
terminal.  
list communication-interface  
processor-channel  
Feature  
Action/ Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list  
number  
Example:  
init  
none  
none  
communication-  
interface  
processor-channel  
list  
inads  
craft  
communication-interface  
processor channel 125  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
list communication-interface processor-channel  
2-100  
Output  
The following example shows the output from the list/display  
communication-interface processor-channel command.  
Page 1 of X  
PROCESSOR CHANNEL ASSIGNMENT  
Proc  
Gtwy  
Interface  
Destination  
Node  
Session  
Port Local/Remote ID  
Mach  
Chan Enable Appl. To Mode Link/Chan  
1:  
2:  
3:  
4:  
5:  
6:  
7:  
8:  
9:  
10:  
11:  
12:  
13:  
14:  
15:  
16:  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_ ________ ___  
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
__ _____ _________ 0____ ___  
___  
___  
___  
___  
___  
___  
___  
___  
___  
___  
___  
___  
___  
___  
___  
___  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
Screen 2-5. Processor Channel Assignment  
Field descriptions  
Proc Chan  
Displays the BX.25 virtual channel number or the TCP/IP listen  
port channel to carry this processor (virtual) channel.  
Enable  
Appl.  
Typ e y to enable a processor channel. Type n (default) to disable  
a processor channel.  
Identifies the switch application used over this link. The  
application gateway is used for conversion between ISDN and  
either TCP/IP or BX.25. Use the gtwy-tcp entry for conversion  
between BX.25 and TCP/IP. Valid entries are: audix, dcs, fp-mwi,  
gateway, gtwy-tcp, mis, msaamwl, msaclk, msahlwc, msallwc,  
msamcs, qs-mwi, blank (default)  
Gtwy To  
Mode  
Identifies which processor channel the given processor channel is  
serving as a gateway to. Valid entries are a number between  
1-(maximum number of processor channels), or blank (default).  
Identifies whether the IP session is passive (client) or active  
(server). This field must be blank if the type of interface link is x.25  
(r model) or procr-intf (si model). This field cannot be blank if the  
type of interface link is ethernet or ppp. Valid entries are client,  
server, or blank (default).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list configuration  
2
2-101  
Interface Link  
Interface Chan  
Identifies the physical link carrying this processor (virtual)  
channel. Links numbered 1 through (4 times the number of PI  
circuit packs) for the si model can be either x.25 or tcp/ip. The  
rest of the links (up to 25) must be tcp/ip.  
Identifies the BX.25 virtual channel number or the TCP/IP listen  
port channel to carry this processor (virtual) channel. The channel  
number 0 means any port can be used. Valid entries for link type  
x.25 are 1-64; for Ethernet or ppp, 0, 5000-64500.  
Destination Node  
Destination Port  
Identifies the switch or adjunct at the far end of this link. Enter an  
adjunct name, switch name, far end IP address, node ID, or leave  
blank (default) for services local to this switch.  
Identifies the port number of the destination. The number 0 means  
any port can be used. Valid entries are 0 (default), 5000-64500.  
Session Local  
Session Remote  
Mach ID  
Field ported forward from R6.  
Field ported forward from R6.  
Field ported forward from R6.  
list configuration  
This command generates a report listing the group specified, the type, code,  
suffix, and vintage of the requested circuit packs as installed in the switch, and  
all ports assigned to the circuit pack.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list  
hardware-  
group  
See Hardware Groups below.  
init  
none  
none  
configuration  
inads  
craft  
cust  
rcust  
print  
Report sent to printer.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
list configuration carrier 1c  
schedule  
list configuration port-network 1  
list configuration stations print  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list configuration  
2
2-102  
NOTE:  
The list configuration software-version command is discussed  
separately under its own heading.  
Hardware Groups  
Enter one of the following hardware groups:  
carriers all  
board PCSS  
carrier c  
Displays all circuit packs administered and/or physically inserted  
in the port, switch node, and control carriers on the system.  
Displays all assigned ports on the circuit pack specified by  
cabinet, carrier, and slot.  
Displays all circuit packs and assigned ports on a specified  
carrier.  
control  
ds1  
Displays all circuit packs in the control complex.  
Displays all the DS1 (TN722, TN767, and TN464) port circuit  
packs administered and/or physically inserted.  
port-network pn#  
Displays all circuit packs located in a specified port network. (List  
cabinet gives the port network number(s) associated with a  
particular cabinet.) Circuit packs on switch node carriers are not  
displayed when the port-network qualifier is entered. To display  
switch node circuit packs, use the all, carrier or board qualifiers.  
stations  
trunks  
Displays all circuit packs that can be assigned stations, including  
DS1 circuit packs for remote stations.  
Displays all circuit packs that can be used for administering  
trunks.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list configuration  
2
2-103  
Output  
The following display shows the output from the list configuration all command.  
list configuration all  
Page  
1
SYSTEM CONFIGURATION  
Board  
Number  
01A01  
01A02  
Assigned Ports  
u=unassigned t=tti  
01 u u 04  
Board Type  
PROCESSOR  
TONE/CLOCK  
Code  
TN798  
TN2182  
Vintage  
000001  
000003  
mj nm  
01 02 03 04 05 06 07 08  
01A03  
01A04  
01A05  
01A06  
no board  
no board  
no board  
TN767  
DS1 INTERFACE  
000011  
u u u u u u u  
u u u u u u u  
u u u u u u u  
01B05  
01B06  
01B07  
01C07  
01C08  
01C09  
01C10  
RESERVED-IP  
RESERVED-IP  
MAPD BOARD  
ANALOG LINE  
HYBRID LINE  
ANALOG LINE  
DIGITAL LINE  
TN802  
TN802  
TN802B  
TN742  
TN762B  
TN742  
TN754  
mapd  
mapd  
HW01 FW001 01  
000010  
000004  
000010  
000004  
u u u u u u u  
u u u u u u u  
u u u u u u u  
u u u u u u u  
press CANCEL to quit -- press NEXT PAGE to continue  
Field descriptions  
Board Number  
Code  
The functional name of the circuit pack  
The TN or UN code and suffix of the circuit packs  
The vintage number of the circuit pack  
Vintage  
no board  
conflict  
The circuit pack is administered but not physically installed  
The circuit pack administered to the slot differs from the circuit pack  
that is physically installed  
no link  
The T1 link is down to a DS1 circuit pack  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
list configuration software-version  
2-104  
The following display shows output from the list configuration ds1 command.  
list configuration ds1  
SYSTEM CONFIGURATION - DS1 Circuit Packs  
Location  
Code  
Vintage  
Signaling  
Name  
CSU MOD  
01B05  
01B06  
01B10  
01B11  
01B12  
01C06  
01C13  
01C16  
01C18  
TN464F 000002  
TN464D 000002  
TN767C 000003  
TN767E 000003  
TN767E conflict  
no board  
TN464E 000003  
TN767D 000024  
TN464F 000002  
isdn-pri  
isdn-pri  
none  
robbed-bit  
none  
120A1  
n/a  
n/a  
120A1  
<blank>  
<blank>  
unknown  
unkonwn  
none  
none  
common-channel  
robbed-bit  
isdn-pri  
Field descriptions  
Signaling  
Name  
This field is displayed only when list configuration ds1 is entered. The  
contents of the field are the same as the signaling mode administered for  
the ds1 circuit pack or noneif the circuit pack is not administered.  
This field is displayed only when list configuration ds1 is entered. The  
contents of the field are the same as the signaling mode administered for  
the ds1 circuit pack or noneif the circuit pack is not administered.  
CSU MOD  
This field is displayed only when list configuration ds1 option is  
selected. The field contains the identification number of the Integrated  
CSU module present on the DS1 circuit pack (TN767E or later / TN464F  
or later) or none. If the circuit pack is a TN464E or TN767D, unknown  
displays. If the circuit pack is a TN464D or TN767C or earlier suffix DS1  
board, then n/adisplays.  
list configuration software-version  
This command displays  
■
Software version numbers and compatibility indexes of the software load  
modules stored in system memory (RAM) and on the Mass Storage  
System devices (tape).  
■
■
The dates and times when translation and announcement data were last  
saved to the MSS.  
Information about any software update files that have been applied to the  
system. See “Software Upgrade” in Chapter 1, ‘‘Maintenance for csi  
systems’’ for an explanation of software versions and compatibility  
indexes.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
list configuration software-version  
2-105  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
listconfiguration  
software-version  
memory-resident  
Data for the active SPE,  
RAM-resident files only.  
init  
inads  
craft  
none  
none  
print  
Report sent to printer.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
If the memory card contains a core dump file, fields for tape or memory card data  
display coredump. When a core dump is present, all other files on the device are  
marked invalid.  
If the memory card cannot be read at the time the command is entered, the  
relevant fields display no tape or memory card. (This does not indicate that  
the system does not recognize the presence of the device.)  
The following display shows the output from the list configuration  
software-version command.  
list configuration software-version  
SOFTWARE VERSIONS  
Page  
1
SPE-A  
SPE-B  
UPDATE FILE  
Creation (GMT) Date: none  
Old Version Tape: none  
Old Identifier Tape: none  
New Identifier Tape: none  
Update State: none in memory  
SOFTWARE VERSION  
Memory Resident: G3V6i.00.1.017.0  
Mem Card Resident: none  
Update Identifier: none  
TRANSLATION DATE  
Memory Resident: 1:01 pm THU AUG 28, 1997  
Mem Card Resident: 1:01 pm THU AUG 28, 1997  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
list configuration software-version  
2-106  
Field descriptions, page 1  
Update File Section  
Displays information pertaining to software field-update files  
or “patches.”  
Creation (GMT)  
Tape and (GMT)  
Disk  
When the update file was originally created, in Greenwich  
Mean Time (GMT). Note that this is not the time at which the  
update file was written to the MSS device.  
Old-Version  
The software version for which the update was created.  
Tape and Disk  
Old-Identifier  
Tape and Disk  
Which previous update file this update file expected to find  
stored in the MSS when it was applied.  
New-Identifier  
Tape and Disk  
Uniquely identifies the current update file.  
Displays information related to the current software-load  
module stored in memory and in the MSS.  
Software Version  
Memory Resident  
Mem Card Resident  
Version number of the RAM-resident load module.  
Version of memory card resident load module. If a memory  
card is not installed, this field will display “no card”.  
Update-identifier  
(Patch Identifier)  
This uniquely identifies the update file, if any, that has been  
applied to memory.  
Update-state (Patch  
State)  
The status of the software field-update (“patch”) file id is  
displayed.  
Displays information related to the translation files as stored  
in memory and the MSS.  
Translation Date  
Memory Resident  
Date and time when translation data was last read from the  
MSS into memory. This is stored in SPE memory and is not  
modified by changes to translation data. A save translation  
command updates this date. If Date invalidis displayed,  
the timestamp does not contain the expected information.  
Mem Card Resident  
The date and time when translation data was last saved to  
the memory card. If a memory card is not installed, this field  
will display no card.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
list configuration software-version  
2-107  
list configuration software-version  
Page  
2
SOFTWARE VERSIONS  
SPE-A  
PI FW VERSION  
PI 1 Resident: 000162  
PI 2 Resident: none  
Flash Resident: 000162  
ANNOUNCEMENT DATE  
Mem Card Resident: none  
PKT-CTRL FW VERSION  
Pkt-Ctrl Resident: n/a  
Flash Resident: 000021  
Field descriptions, page 2  
Displays information related to the Processor Interface (PI)  
circuit pack (resident copy and corresponding tape file)  
firmware.  
P1 FW Version  
PI 1 Resident  
The version of firmware in the first PI circuit pack in the control  
carrier.  
PI 2 Resident  
Flash Resident  
The version of firmware in the second PI circuit pack in the  
control carrier.  
The version of PI firmware residing on the system flash memory.  
Displays information related to the announcement files.  
Information is displayed for the memory resident copy as well as  
the corresponding MSS file  
Announcement  
Date  
Mem Card Resident  
The last date and time that announcement data was saved to the  
memory card. If the memory card is not installed, this field  
displays no card.  
displays information related to the Packet Control firmware.  
Information is displayed for the Packet Control circuit pack  
resident copy as well as the corresponding tape file  
PKT-CTRL FW  
Version  
Pkt-ctrl Resident  
The version of firmware in the Packet Control circuit pack.  
Flash Resident  
The version of the Packet Control circuit pack residing on the  
system flash memory.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
list configuration software-version  
2-108  
Some things to note when using the list configuration software-version  
command are:  
1. For simplex systems, the fields under column “SPE_B are always blank  
and the optional Long qualifier is not part of the command line.  
2. If the memory card contains a core dump file system, fields for the tape or  
memory card will contain coredump. This is because in a coredump file  
system, all files other than the coredump file are marked as invalid.  
3. If for any reason, MSS cannot be read when the command is issued, the  
string no tape or none for no memory card will be placed in the  
appropriate fields on the screen. This does not mean that the system  
thinks there is no tape, only that the software was unable to read the  
appropriate information when requested.  
4. If the command is issued using the memory-resident option, the fields on  
the form associated with the tape will contain the string n/a.  
5. When the status of the update field is displayed, the following strings will  
be used (for more information refer to step c of this list):  
a. none in memory— no update has been applied to memory.  
b. immediate partially applied— an error condition that is  
valid only when an update that is in the process of being applied  
fails. Check the validity of the update file that was sent, and then  
check the hardware error log for tape errors, and follow standard  
maintenance procedures.  
c. all immediate applied deferred pending— a valid  
update file was received by the switch, and all the immediate  
sub-patches were applied. This state indicates that there are  
deferred sub-patches in the update file, and a system reset of the  
proper level has not occurred since the update file was received.  
d. deferred partially applied— an error condition that is  
valid only when a update that is in the process of being applied  
fails. Check the validity of the update file that was sent, and then  
check the hardware error log for tape errors, and follow standard  
maintenance procedures.  
e. entirely applied to memory— the update associated with  
the memory-resident identifier has been completely applied to  
memory.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list disabled-mos  
2
2-109  
list disabled-mos  
This command displays all the MOs that have been maintenance disabled in the  
system.  
Feature  
Action/Object  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list  
Report sent to printer.  
init  
none  
none  
disabled-mos  
inads  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
list disabled-MOs  
list disabled-MOs print  
list disabled-MOs schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
The following example shows the output from the list disabled-MOs command.  
list disabled-MOs  
DISABLED MAINTENANCE OBJECT INFORMATION  
Maintenance Name  
ALL  
DIG-LINE  
Location  
01A1203  
Status  
Enabled  
Disabled  
Command successfully completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list external-device alarm  
2
2-110  
Field descriptions  
Maintenance  
Name  
The type of maintenance object (or group of maintenance objects) that  
have been disabled. Allis also valid.  
Location  
The physical location of the disabled maintenance object that has  
been disabled. This field displays blanks if all maintenance objects  
have been disabled (disable all) or all MOs of a specific type have  
been disabled (disable MO-all).  
Status  
Whether the maintenance object or group of maintenance objects is  
Enabledor Disabled.  
list external-device alarm  
This command identifies any administered external devices, including the:  
port identification  
external device connected to the port  
■
■
■
alarm level (major, minor, or warning) assigned to the external device  
NOTE:  
You must enable the External Device Alarm Admin? field (y) on the  
System-Parameters Customer-Options form (change system-parameters  
customer-options; init login required) before you can administer External  
Device Alarm commands.  
Output  
The following example shows the output from the list eda-external-device-alrm  
command.  
list eda-external-device-alrm  
Page 1 of 1 SPE A  
EXTERNAL DEVICE ALARM PORTS  
Port  
Alarm  
Type  
Alt  
Name  
Description  
Product  
Identifier  
01c1201 minor  
01c1202 major  
01major minor  
01minor minor  
03a2101 warning  
03a2102 major  
03major major  
03minor minor  
UPSI  
Audix1  
UPSI  
UPSI  
CC temp  
CMS2  
DC battery discharged  
Main Audix main equipment  
DC rectifier alarm  
7000000001  
8123456790  
7000000001  
7000000001  
DC overvoltage alarm  
Computer Center Temperature  
Call management adjunct  
Call management adjunct  
Audix 2 remote equipment  
6222222222  
6111111111  
8123456791  
CMS1  
Audix2  
Screen 2-6. External Device Alarm Ports report  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list history  
2
2-111  
Field descriptions  
Port address1  
Port  
Alarm Type  
The alarm level for this external device alarm port. Entries are  
major, minor (default), or warning.  
Alt. Name  
7-character adjunct short name for this external device alarm  
40 character adjunct description for the external device alarm  
Description  
Product  
Identifier  
10-digit product identifier of the external device alarm (leading  
zeroes are significant and retained). If the field is blank (default),  
alarms associated with the connected adjunct use the switch  
product identifier administered on the Change System-Parameters  
Maintenance screen.  
Building  
Address  
A 40-character description of the external device alarm’s building  
location  
A 40-character building address  
1
The special locations UUmajorand UUminor(see Screen 2-6) designate the name of the major  
or minor maintenance circuit pack alarm connection for cabinet UU (depends upon the auxiliary  
connector of the Port Network). Thus, both a “major” and “minor” port can be administered with  
major, minor, or warning alarms.  
list history  
This command generates a log listing of the most recently completed “data  
affecting” administration and maintenance commands. Data commands are  
those administration and maintenance commands that change the data state  
associated with any object and qualifier in the system. Administration data  
commands affect translation data, while maintenance data commands affect  
state information. For example, change station is a data command, whereas  
display station is not.  
All information in the transaction log is saved on tape as translation data when  
the save translation command is performed (LIFO order). When the switch  
COLD I starts or reboots, the saved translation, and thus the transaction log, is  
loaded from tape. In this way, the translation data and the data in the transaction  
log remain compatible.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list history  
2
2-112  
Feature  
Action/Object  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list history  
Report sent to printer.  
init  
none  
See below  
inads  
craft  
cust  
browse  
nms  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
list history  
list history print  
list history schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Feature Interactions  
The translation log is written to the memory card as translation data when the  
save translation command is executed. The translation data is time stamped  
when saved. This time stamp is noted when translation is loaded from the  
memory card and included in all recent change history reports.  
When a user requests a recent change history report, there could be other users  
concurrently issuing data commands and altering the contents of the transaction  
log. Therefore, if the user pages the entire way through the report, the oldest  
entries in the transaction log (maximum 250 commands) may have been  
overwritten by data commands issued by these other users. Should this occur,  
the final entries of the report show the data commands issued by the other users  
since the recent change history report was originally requested.  
Also, use of the set time command to alter the system clock could make it look  
as if the recent change history report is not in true LIFO order.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list history  
2
2-113  
Output  
list history  
Page  
1
SPE A  
HISTORY  
Date of Loaded Translation: 11:34am Mon Apr 20, 1997  
Date Time Port Login Actn Object Qualifier  
4/20 17:23 SYSAM-LCL init  
4/20 11:34 SYSAM-LCL init  
4/20 11:25 SYSAM-LCL init  
4/20 11:25 SYSAM-LCL init  
4/20 11:25 SYSAM-LCL init  
4/18 17:59 SYSAM-LCL init  
4/18 17:59 SYSAM-LCL init  
4/18 17:58 SYSAM-LCL init  
4/18 17:58 SYSAM-LCL init  
4/18 17:58 SYSAM-LCL init  
4/18 17:58 SYSAM-LCL init  
4/18 17:57 SYSAM-LCL init  
4/18 17:57 SYSAM-LCL init  
4/18 17:57 SYSAM-LCL init  
go  
tcm  
cha  
add  
cha  
add  
clea mst  
test board  
clea mst  
enab mst  
cha  
disa mst  
test board  
clea mst  
test board  
trunk-group 100  
trunk-group 100  
circuit-pack 9  
cabinet  
9
2e01  
mst  
2e01  
2e01  
press CANCEL to quit -- press NEXT PAGE to continue  
Field descriptions  
Date  
The date the command was issued in (mm/dd format)  
Time  
The time the command was issued (in hh:mm format)  
Port  
The port type to which the user was connected when the command  
was issued.  
Port  
Number  
List History  
Display  
Board  
0 - 30  
31 - 40  
41  
EPN Maintenance Board Port  
System Access Port  
MAINT  
SYS-PORT  
Maintenance Board Port  
SYSAM-LCL  
42  
Remote Maintenance Board Port SYSAM-RMT  
Login  
Actn  
User login  
The first word (verb) of the command, specifying the operation to be  
performed. This field is truncated after four characters to allow enough  
space for objects and qualifiers. Four characters is enough to uniquely  
identify each action.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list ip-route  
2
2-114  
Object  
The qualifier, or second phrase of the command, specifying the  
particular thing being acted upon by the command. Twelve characters  
is enough to uniquely identify each object.  
NOTE:  
Where the object is multiple words in length, only the first word  
will be displayed in the object field. All succeeding words will be  
treated as qualifiers. This field is truncated after twelve  
characters to allow enough space for qualifiers.  
Qualifier  
One or more qualifiers describing the characteristics of the  
action/object pair. This field is truncated after 31 characters to keep  
information for a command on a single line.  
list ip-route  
This command displays a list of the IP routes from DEFINITY ECS out to the LAN.  
You may enter the “board” parameter and specify which C-LAN circuit pack for  
which to show the IP routes (for example, list ip-route board UUCss).  
Feature  
Action/ Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list ip-route  
board UUCss  
Board Location  
init  
none  
none  
inads  
craft  
Example:  
list ip-route board 01A03  
Output  
The following example shows the output from the list ip-route command.  
list ip-route  
IP ROUTING  
Route  
Number  
Destination  
Node  
C-LAN  
Port  
Route Accepted  
Gateway  
Metric Type  
by C-LAN  
xxx  
xxx  
xxx  
xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxx x  
xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxx x  
xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxx x  
xxxx  
xxxx  
xxxx  
xxxxxx  
xxxxxx  
xxxxxx  
Field descriptions  
Route Number  
IP-route number  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list isdn-testcall  
2
2-115  
Destination Node  
Gateway  
Destination of the route. The destination is a name administered  
on the Node Name form that can include the keyword Default  
indicating the default route.  
The node name of the Gateway through which the destination is  
to be reached. The Gateway is a name administered on the  
Node Name form.  
C-LAN Port  
Metric  
Indicates the C-LAN port location that provides the interface for  
the route.  
Specifies the desirability of the IP route in terms of the efficiency  
of data transmission over the route. Valid entries are 0(a simple  
route) and 1(a complex route). A metric value of 1is used only  
when the switch has more than one C-LAN board installed. A  
metric-1 route diverts usage of the route to a metric - 0 route, if  
available.  
Route Type  
A non-administrable field that specifies whether this is a network  
or host route. A network route is a route to all nodes on the  
(sub)network specified in the Destination Nodefield. A host  
route is a route to the single node specified in the Destination  
Nodefield.  
Accepted by CLAN  
Indicates whether a C-LAN circuit pack has accepted the  
administered IP-route. Routes for a link are downloaded to the  
C-LAN circuit pack when the link comes into service. Possibilities  
include:  
■ accepted– the route has been accepted by the C-LAN  
circuit pack  
■ rejected– the route has been rejected by the C-LAN circuit  
pack. The Gateway may not be on the attached ethernet  
subnet or may not be the IP address of the far end of the PPP  
link.  
■ pending– the route has not been sent to the C-LAN circuit  
pack, or it has been sent but no reply has been received.  
Typically, this status changes to acceptedor rejected  
when some condition changes, such as a link coming up.  
■ obsolete– the route is no longer needed (some host routes  
were needed in R7 but are no longer needed in subsequent  
releases, or are duplicates of existing routes)  
list isdn-testcall  
This command displays the ISDN-PRI trunks in use for ISDN-PRI test calls. This  
command is useful to determine which trunk is in use for an outgoing ISDN-PRI  
test call.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list marked-ports  
2
2-116  
Feature  
Action/Object  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list  
Report sent to printer.  
init  
none  
none  
isdn-testcall  
inads  
craft  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
list isdn-testcall  
list isdn-testcall print  
list isdn-testcall schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
list isdn-testcall  
ISDN-PRI TESTCALLS  
B-Channel Start Time Duration M/T Port  
078/001 25/12:36 120 1B1102  
Command successfully completed  
Field descriptions  
B-Channel  
Trunk in use for the ISDN-PRI test call (trunk group number/ member  
number).  
Start Time  
Duration  
M/T Port  
Time the test call started (dd/hh:mm format).  
Expected duration of the test call.  
The TN771 Maintenance/Test circuit pack’s digital port address (in  
cabinet/carrier/slot/circuit format) in use for the outgoing asynchronous  
ISDN-PRI test call.  
list marked-ports  
This command lists all the ports that have been marked unusable with the mark  
port command (maximum of fifteen marked ports per page).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
list measurements clan ethernet  
2-117  
Feature  
Action/Object  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list  
Report sent to printer.  
init  
none  
none  
marked-ports  
inads  
craft  
cust  
rcust  
bcms  
browse  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
list marked-ports  
list marked-ports print  
list marked-ports schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
list marked-ports  
MARKED-PORT INFORMATION  
Port  
Board-Type  
DIG-BD  
1C0101  
1C0601  
1C0702  
DIG-BD  
Command successfully completed  
Field descriptions  
Port  
The port address (cabinet-carrier-slot-circuit) of the marked port.  
The type of circuit pack containing the marked port. If this circuit pack  
Board-Type  
information is no longer available because the circuit pack was  
removed after the port was marked, the Board-Typefield is blank.  
list measurements clan ethernet  
This command provides a 24-hour history of important packet-level statistics  
from which you can infer some LAN performance characteristics. For example,  
■
high collision counts could indicate high traffic on the LAN segment  
(congestion on the bus).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
list measurements clan ethernet  
2-118  
■
high Cyclic Redundancy Check (CRC—detects and corrects errors on  
every frame) errors could suggest that  
— the LAN connection may be “noisy”  
— a wire connection is loose  
— a wire is frayed or broken.  
The 24-hour history gives the ability to look back at these measures if the trouble  
cleared.  
The data is collected at 15-minute intervals over 24 hours for the Cyclic  
Redundancy Check (CRC) and collisions for ethernet connections. If the data  
cannot be retrieved for the 15-minute interval, N/Adisplays in the field. The delta  
(the change from the last inquiry) and the total are provided for each error count.  
After the occurrence of “N/A” (not available), the delta equals the total.  
The primary use of this command is to quickly and unambiguously determine if  
the fault lies within the Lucent-provided equipment or if the fault is with the LAN  
or LAN administration to which the DEFINITY ECS switch is connected.  
Feature  
Action/Object  
Qualifier Qualifier Description  
Permissions  
Defaults Interactions  
list  
clan  
Designates ethernet  
connection  
init  
inads  
craft  
measurements ethernet  
UUCss  
Cabinet-carrier-slot  
address of the C-LAN  
circuit pack  
customer  
print  
Report sent to printer  
schedule Command is validated  
and then a scheduling  
form displays to  
schedule execution of  
the command. The  
command is then  
placed in the command  
queue and is executed  
at the specified time.  
The information  
displayed by the  
command is sent to the  
system printer instead  
1
of the screen.  
Examples:  
list measurements  
clan ethernet 1A05  
list measurements  
clan ethernet 1A05  
print  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list measurements clan ppp  
2
2-119  
Output  
The following example shows the output from the list measurements ethernet  
command.  
list measurements clan ethernet 1C1017  
Switch Name: sierra  
Page 1 of x  
Date:4:07pm MON AUG 01,1999  
C-LAN ETHERNET PERFORMANCE MEASUREMENT DETAILED REPORT  
Date  
Time  
CRC Check  
total  
650  
600  
N/A  
Collision Count  
total  
650  
delta  
50  
600  
N/A  
delta  
250  
400  
N/A  
20  
08/01  
08/01  
08/01  
08/01  
08/01  
0308  
0253  
0238  
0223  
0208  
400  
N/A  
1000000570  
1000000550 10000000550 10000000550  
20 10000000570  
10000000550  
Field descriptions  
Date  
The date that the data was collected.  
Time  
The current 15-minute interval in which the action was performed  
The error count for CRC errors  
CRC Check  
Total  
The total value of the counter on the board  
NOTE:  
The counter value can be up to 11 digits long because of the  
32-bit counter on the board. After the occurrence of an “N/A,”  
the delta equals the total. Busyout or release of a board or a  
port, the reset board command, and reseating the board all  
clear the firmware counters.  
Delta  
The difference between the current and the previous sample  
The error count for collisions on the ethernet  
Collision Count  
list measurements clan ppp  
This command provides a 24-hour history of important packet-level statistics  
from which you can infer some LAN performance characteristics. For example,  
■
Invalid frames—the number of frames that are misaligned  
■
CHAP failures—Challenge Handshake Authentication Protocol—the  
number of attempts for ppp authentication that failed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list measurements clan ppp  
2
2-120  
■
High Cyclic Redundancy Check (CRC)—detects and corrects errors on  
every frame) errors could suggest that the connection may be “noisy”  
The 24-hour history gives the ability to look back at these measures if the trouble  
cleared.  
Data is retrieved for 15-minute intervals for 24 hours for CRC, Invalid Frame and  
Chap Failures for PPP connections. If the data cannot be retrieved for the 15  
minute interval, N/Adisplays in the field. The delta (the change from the last  
inquiry) and the total are provided for each error count. After the occurrence of  
an “N/A,” the delta equals the total.  
Feature  
Action/Object  
Qualifier  
Qualifier Description Permissions  
Defaults  
Interactions  
list  
clan ppp  
Link identifier (primary  
or secondary)  
init  
inads  
craft  
Primary  
measurements  
UUCCSS  
pp  
Port Address  
customer  
print  
Report sent to printer  
schedule  
Command is validated  
and then a scheduling  
form displays to  
schedule execution of  
the command. The  
command is then  
placed in the  
command queue and  
is executed at the  
specified time. The  
information displayed  
by the command is  
sent to the system  
printer instead of the  
1
screen.  
Examples:  
list measurements  
clan ppp  
list measurements  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
The following example shows the output from the list measurements clan ppp  
command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list measurements ds-1  
2
2-121  
list measurements clan ppp 1C1001  
Switch Name: sierra  
Page 1 of x  
Date:02/02/1999  
C-LAN PPP PERFORMANCE MEASUREMENT DETAILED REPORT  
Date  
Time  
CRC Check  
Total Delta  
Invalid Frame  
CHAP Failures  
Total  
Delta  
Total  
‘Delta  
02/01  
02/01  
02/01  
02/01  
02/01  
03:08  
02:53  
02:38  
02:23  
02:08  
85  
60  
N/A  
25  
60  
N/A  
185  
100  
N/A  
85  
100  
N/A  
10  
5
5
N/A  
25  
20  
0
5
N/A  
5
1000060  
1000050  
10 1000090  
1000050 1000080 1000080  
20  
Field descriptions  
Date  
The date that the data was collected  
Time  
The current 15-minute interval in which the action was performed  
The error count for CRC errors  
CRC Check  
Total  
Total value of the board counter.  
NOTE:  
The counter value can be up to 7 digits long because the 16-  
bit counter on the board. After the occurrence of an “N/A” the  
delta equals the total. Busyout or release of a board or a port,  
the reset board command, and reseating the board all clear  
the firmware counters.  
Delta  
The difference between the current and the previous sample  
Invalid Frame  
The number of invalid frames detected. Invalid frames are the  
frames that are misaligned.  
CHAP Failures  
The number of failed attempts for ppp authentication  
list measurements ds-1  
This command lists performance measurements of a DS-1 link indicating the  
quality of the DS-1 physical interface between the system and a far end system.  
The ds1 summary option provides a summary report while the ds1 log option  
provides a detailed report.  
NOTE:  
The list measurements command has many more options than  
documented here. Only those options dealing with DS1 board are  
documented below.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list measurements ds-1  
2
2-122  
Feature  
Action/Object  
Qualifier  
log  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list  
Detailed report generated  
Summary report generated  
init  
none  
none  
measurements  
inads  
craft  
cust  
rcust  
browse  
nms  
summary  
ds1_location  
The physical location of a DS1  
circuit pack entered as  
cabinet-carrier-slot.  
print  
Report sent to printer.  
bcms  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
list measurements ds1 log 2a18  
list measurements ds1 summary  
2a18 print  
list measurements ds1 summary  
2a18 schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
list measurements ds1 summary 2a19  
SPE A  
Switch Name:  
Date: 1:25 pm THU APR 16, 1992  
DS-1 Link Performance Measurements Summary Report  
Counted Since: 1:20 pm THU APR 16, 1992  
Number of Seconds Elapsed Into Current 15-min Interval: 323  
Total of Valid 15-min Intervals in Past 24-hr Period:  
0
Total of Current  
Worst_15-Min_Interval  
24-hr  
15-Min Interval  
Category  
Errored Seconds  
Bursty Err Secs  
Severely Err Secs 4/16  
Failed Seconds 4/16  
Date  
4/16  
4/16  
Time  
Count  
Count  
Count  
13:20  
13:20  
13:20  
13:20  
0
0
0
0
0
0
0
0
4
4
0
0
Command successfully completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list measurements ds-1  
2
2-123  
Field descriptions (list measurements  
ds1-summary)  
Counted  
Since:  
The start time and date when the associated measurement counters  
were cleared or the DS1 circuit pack was administered.  
Number of  
Seconds  
Elapsed Into  
Current  
The number of seconds from the beginning of the current 15-minute  
interval (0 - 900).  
15-min  
Interval:  
Total of  
The total number of 15-minute intervals in the past 24-hour period that  
contain valid data (0 - 96).  
Valid 15-min  
Intervals in  
Past 24-hr  
Period:  
Category  
The four categories correspond to four measurement error counters:  
■ Errored Seconds: the value of the errored seconds counter for  
the specified 15-minute interval (0 - 900 or N/A if data for the  
15-minute interval is invalid).  
■ Bursty Err Secs: the value of the bursty errored seconds  
counter for the specified 15-minute interval (0 - 900 or N/A if data  
for the 15-minute interval is invalid).  
■ Severely Err Secs: the value of the severely errored seconds  
counter for the specified 15-minute interval(0 - 900 or N/A if data  
for the 15-minute interval is invalid).  
■ Failed Seconds: the value of the failed seconds counter for the  
specified 15-minute interval (0 - 900 or N/A if data for the  
15-minute interval is invalid).  
Worst_15-Min_  
Interval  
The date(Date), end time(Time), and error count (Count; from 0 to 900  
in increments of four) of the 15-minute interval in the previous 24-hour  
period that contains the maximum value for each of the four error  
categories.  
Total of  
24-Hour Count  
The sum of all valid 15-minute counts for the previous 24-hour period  
for each of the four error categories (0 - 65535).  
Current  
15-Minute  
Interval  
The error count for the current (incomplete) 15-minute interval for each  
of the four error categories (0 - 900 or N/A if data for the 15-minute  
interval is invalid).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list measurements ds-1  
2
2-124  
list measurements ds1 log 2a19  
Switch Name:  
SPE A  
Date: 1:26 pm THU APR 16, 1992  
DS-1 Link Performance Measurements Detailed Log Report  
Counted Since: 1:20 pm THU APR 16, 1992  
ERRORED BURSTY  
SEVERELY  
FAILED  
VALID  
DATE TIME SECOND ERR SECS ERR SECS  
SECONDS  
INTERVAL  
4/16  
4/16  
13:05  
13:20  
0
0
0
0
0
0
0
0
y
y
Command successfully completed  
Field descriptions (list measurements ds1 log)  
Counted  
Since:  
The start time and date when the associated measurement counters  
were cleared or the DS1 circuit pack was administered.  
DATE  
TIME  
The date of the 15-minute interval.  
The time of the 15-minute interval.  
ERRORED  
SECONDS  
The value of the errored seconds counter for the specified 15-minute  
interval (0 - 900 or N/A if data for the 15-minute interval is invalid).  
BURSTY ERR  
SECS  
The value of the bursty errored seconds counter for the specified  
15-minute interval (0 - 900 or N/A if data for the 15-minute interval is  
invalid).  
SEVERELY ERR  
SECS  
The value of the severely errored seconds counter for the specified  
15-minute interval (0 - 900 or N/A if data for the 15-minute interval is  
invalid).  
FAILED  
SECONDS  
The value of the failed seconds counter for the specified 15-minute  
interval (0 - 900 or N/A if data for the 15-minute interval is invalid).  
VALID  
INTERVAL  
This field indicates whether the data for the specified 15-minute interval  
is valid. Data is considered valid when a count for that 15-minute  
interval. If the field has a value of y, the data for the four error  
categories is valid; otherwise, the data is invalid.  
Data is considered valid when a count for that 15-minute interval is  
retrieved and none of the following invalid conditions occur:  
— If a system warm start or a system cold start occurred during the  
interval  
— If the DS1 circuit pack was not inserted during the interval  
— If the system time was changed during the interval  
— If the system was too busy to respond to a poll request for the  
interval.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-125  
list mst  
This command displays the messages in the trace buffer and can be used when  
the trace is disabled or active, but if active, older messages may be sporadically  
omitted if wraparound is selected and the message rate is high. The command  
can be used repeatedly without destroying the integrity of the buffer.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list mst  
from message  
number  
Message number to start the  
display; if the number is not in  
the buffer, then that is indicated  
on the display, and no additional  
messages are displayed.  
init  
inads  
FIFO order  
See below  
Omitting this qualifier causes  
messages to be displayed  
starting with the oldest FIFO and  
continuous messages.  
count number  
continuous  
Message count; can be used to  
limit the trace  
Display updates as new  
messages enter the trace buffer  
(FIFO). This option is most useful  
in conjunction with “auto-page.”  
The command terminates only  
when canceled by the user.  
LIFO  
FIFO  
Newest message displayed first.  
Messages displayed in the order  
received.  
auto-page  
The screen will automatically  
page when full. Used in  
combination with continuous  
(above), provides a way to  
“watch” as messages arrive.  
print  
Report sent to printer.  
schedule  
Command is validated and then  
a scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue  
and is executed at the specified  
time. The information displayed  
by the command is sent to the  
system printer instead of the  
1
screen.  
Examples:  
list mst continuous  
list mst continuous auto-page  
list mst LIFO  
list mst from 222 count 7  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-126  
Feature Interactions  
See documentation on the system printer feature.  
Output  
list mst  
Message Sequence Trace Data  
Type Message  
Number Date/Time  
1
12/21/90  
14:30:21.220 62 00 00 74 17 08 02 00 11 05 04 03 80 90 a2 18  
03 a1 83 86 70 01 80 96 28 0d 73 74 61 74 69  
6f 6e 20 35 31 30 30 31  
2
3
4
5
14:30:22.420 60 00 00 74 17 08 02 80 11 02 18 03 a9 83 86  
14:30:23.420 60 00 00 74 17 08 02 80 11 03 1e 02 81 81  
14:30:25.420 60 00 00 74 17 08 02 80 11 01  
14:30:25.820 60 00 00 74 17 08 02 80 11 07 96 28 0d 73 74 61  
74 69 6f 6e 20 35 31 30 30 34  
6
7
8
14:30:28.020 62 00 00 74 17 08 02 00 11 0f  
14:50:25.820 71 01  
14:52:26.020 56 00 00 70 00 08 01 04 64 96 1c 13 91 a1 10 02  
01 03 02 01 c4 40 08 96 49 05 83 31 30 30 b4  
14:52:26.020 57 00 00 70 00 08 01 84 64 96 1c 0d 91 a2 0a 02  
01 03 30 05 02 01 c4 40 00  
9
Command Successfully Completed  
Field descriptions  
Number  
The sequence number for the message.  
Date/Time  
Type  
The Date/Time.  
MST message type:  
60 = ISDN uplink  
62 = ISDN downlink,  
6C = ISDN level 2 primitive  
Message  
Message text in hexadecimal (ISDN or X.25). See Table 2-1 for an  
explanation of the numeric codes.  
Table 2-1. Summary of MST Message Types  
Code  
0x10  
0x11  
Description  
Vector Trace message  
Vector Event message  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-127  
Table 2-1. Summary of MST Message Types — Continued  
Code Description  
0x21  
0x22  
0x23  
0x24  
0x25  
0x26  
0x27  
0x30  
0x31  
0x32  
0x33  
0x40  
IMT proc_errs  
IMT crec  
IMT miscellaneous hooks (dbug)  
Hardware error log  
PREC message  
CMS outgoing (individual)  
CMS incoming (individual)  
CCMS uplink message  
CCMS downlink message  
Packet uplink message  
Packet downlink message  
IMT internal-message trace for call_p, conn_m, grp_m, serv_d,  
suser_m  
0x50  
0x51  
0x52  
0x53  
0x54  
0x55  
0x56  
0x57  
0x58  
0x60  
0x62  
0x64  
0x66  
0x68  
0x6A  
0x6C  
0x6D  
0x6E  
ASAI level 2 primitive uplink  
ASAI level 2 primitive downlink  
ASAI maintenance uplink  
ASAI maintenance downlink  
ASAI unrecognized uplink  
ASAI unrecognized downlink  
ASAI association uplink  
ASAI association downlink  
ASAI error uplink  
ISDNPRI uplink  
ISDNPRI downlink  
ISDNBRI uplink  
ISDNBRI downlink  
ISDNBRI level 2 primitive uplink  
ISDNBRI level 2 primitive downlink  
ISDNPRI level 2 primitive uplink  
ISDNPRI level 2 primitive downlink  
ISDNPRI unrecognized message  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-128  
Table 2-1. Summary of MST Message Types — Continued  
Code  
Description  
ISDNBRI unrecognized message  
0x6F  
0x71  
0x72  
0xA0  
0xA1  
0xA2  
0xB0  
0xB1  
0xCF  
0xD0  
0xD1  
0xD2  
0xD3  
0xE2  
0xF0  
0xF1  
0xF2  
0xF9  
0xFA  
GAP marker  
Time changed while trace enabled  
X.25 Outgoing application data message  
X.25 Incoming application data message  
X.25 Application error message  
X.25 Outgoing session layer control message  
X.25 Incoming session layer control message  
X.25 Message confirmation  
X.25 Outgoing processor channel control message  
X.25 Incoming processor channel control message  
X.25 Link control message  
X.25 Link status message  
X.25 Session Timer Expirations  
X.25 Error Message (Outgoing Message Lost)  
X.25 Unrecognized Messages  
X.25 Error Message (DIP ICOM Record Aborted) (R2 Only)  
Snapper instrumentation message  
Snapper continuation message (for large msgs)  
Detailed description of Messages  
The terminology Message[n] used below refers to the byte at offset n in the  
message being displayed.  
MST message types contain a version number. Whenever the structure of the  
MST message changes, the version field in the MST buffer will be changed.  
Version 1 (default) displays a blank in the version field which is immediately after  
the MST message type field. Subsequent versions display the version number  
after the MST message type field and are connected with a hyphen (-). For  
example: Version 2 of the X.25 Application error/notification message has added  
the text of the pm state table stimulus which was ignored.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-129  
Version 1 of MST message type 0xA2 would appear on the ’list mst’ output:  
Number Date/Time  
Type Message  
17 10  
1
11:41:22:425 A2  
Version 2 of MST message type 0xA2 would appear on the list mst output:  
Number Date/Time  
Type Message  
90 12:41:14:112 A2-02 17 10 21 03 32 05 01 80  
Vector Trace  
Message type: 0x10  
Message format:  
Message[1-4]  
Message[5-6]  
Message[7]  
Message[8]  
Message[9]  
= call identifier (CID) (defined in $BASEPJ/hdrs/capro.h)  
= vector number (defined in $BASEPJ/hdrs/dpm_calls.h)  
= step number (defined in $BASEPJ/hdrs/callr.h)  
= step type (defined in $BASEPJ/hdrs/dpm_calls.h)  
= step state (defined in $BASEPJ/hdrs/dpm_calls.h)  
Message[10-12] = VDN  
Message[13]  
Message[14]  
Message[15]  
Message[16]  
= port network number  
= endpoint number  
= angel number  
= circuit number  
Message[17-20] = trunk number  
Message[21+]  
= auxiliary data (based on step type)  
Vector Event Trace (D92 Only)  
Message type:  
0x11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-130  
Message format:  
Message[1-4] = cid (defined in $BASEPJ/hdrs/capro.h)  
Message[5-6] = event  
Message[7+] = auxiliary data (based on event)  
Events are defined in $BASEPJ/hdrs/evnt_defs.h. Events based on the call_p will  
have the following auxiliary data:  
Message[7-8]  
= vector number  
Message[9-10] = step number  
Events based on the grp_m will have the following auxiliary data:  
Message[7-10] = hunt group number  
IMT (D92)  
The messages described in this section cannot be controlled directly through  
any of the MST screens. They are enabled/disabled through TCM but their output  
goes to the MST buffer. See [IMT] for details on these messages.  
A read-only field in the “change mst” screen, “Other Tracing?”, alerts the user  
that one or more of these types of messages is enabled.  
0x21 - IMT proc_errs  
Message format:  
Message[1-4]  
Message[5-8]  
= process number(lname)  
= sequence number (defined in *.p/hdrs/main_err.h, for  
example: $BASEPJ/gmtce.ss/hmm.p/hdrs/main_err.h)  
Message[9-12]  
= data 1  
Message[13-17] = data 2  
0x22 - IMT crec  
Message format:  
Message[1+] = call record (defined as CALLR typedef in  
$BASEPJ/hdrs/callr.h)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-131  
0x23 - MT_IMT (miscellaneous IMT hooks)  
This message type is for miscellaneous IMT hooks. The only sub-type currently  
available is for a debug button (dbut). The button number is provided in the  
debug button MST message so that more than one button can be administered  
(through IMT) to convey different meanings. For example, depression of button N  
could signify the start of the problem symptoms, while depression of button N + X  
could signify the end of the problem symptoms. Note that the button number  
being logged represents the position of a button on a particular set type, and will  
be different depending on set type and module type (feature, coverage, display,  
and so forth). The mapping of the button number stored in the IMT_BUT_DEBUG  
MST message to a position on the set is not trivial, however, the debug buttons  
can be administered through TCM, debug button filtering enabled through TCM  
and MST enabled using the ‘enable mst’ command and the resultant messages  
sent to MST when each button is depressed can be examined for the button data  
and noted.  
Message format:  
Message[1]  
= 0x01 (debug button sub-type, IMT_BUT_DEBUG)  
Message[2-3] = button number  
Message[4-7] = user id  
0x40 - internal message tracing of call_p, conn_m,  
grp_m, serv_d, suser_m  
Message formats: conn_m, grp_m, and suser_m:  
Message[1-4] = user identifier  
Message[5-6] = hook identifier (defined in $BASEPJ/hdrs/mstencode.h)  
Message[7+]  
= standard message (depends on hook type)  
serv_d (map-type messages):  
Message[1-4]  
Message[5-6]  
Message[7]  
= user identifier  
= hook identifier (defined in $BASEPJ/hdrs/mstencode.h)  
= STIM type  
Message[8-11] = service identifier  
Message[12]  
Message[13]  
Message[14]  
Message[15]  
Message[16+]  
= port network number  
= endpoint number  
= angel number  
= circuit number  
= message  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-132  
serv_d (other serv_d messages):  
Message[1-4]  
Message[5-6]  
Message[7]  
= user identifier  
= hook identifier (defined in $BASEPJ/hdrs/mstencode.h)  
= STIM type  
Message[8-11]  
= service identifier  
Message[12-13] = interpreted STIM  
Message[14-17] = aux data 0  
Message[18-21] = aux data 1  
Message[22-25] = aux data 2  
Message[26-29] = aux data 3  
Message[30]  
Message[31]  
= hwtype field  
= hwdata field  
call_p:  
Message[1-4] = call identifier  
Message[5-6] = hook identifier (defined in $BASEPJ/hdrs/mstencode.h)  
Message[7]  
Message[8]  
Message[9+]  
= supervisor  
= digit prep  
= message  
CCMS  
Message types:  
0x30 uplink  
0x31 downlink  
Message format:  
Message[1]  
Message[2]  
Message[3]  
Message[4]  
= port network number  
= endpoint number  
= angel number  
= circuit number  
Message[5-6] = hook identifier (defined in $BASEPJ/hdrs/mstencode.h)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-133  
Message[7]  
Message[8]  
Message[9+]  
= message length  
= angel id  
= standard CCMS message  
Packet (D92)  
Message type:  
0x32 uplink  
Message format:  
Message[1-4]  
Message[5-6]  
Message[7-10]  
= user identifier  
= hook identifier (defined in $BASEPJ/hdrs/mstencode.h)  
= link identifier  
Message[11-12] = message type (defined in $BASEPJ/hdrs/pcd_calls.h)  
Message[13+]  
= standard packet message  
Message type:  
0x33 downlink  
Message format:  
Message[1]  
Message[2]  
Message[3]  
Message[4]  
Message[5-6]  
= port network number  
= endpoint number  
= angel number  
= circuit number  
= hook identifier (defined in $BASEPJ/hdrs/mstencode.h)  
Message[7-10] = link identifier  
Message[11+]  
= standard packet message  
ASAI  
ASAI messages listed on the MST screen consist of a 4 octet header and a  
variable length body. The header contains the ASAI port address encoded with 8  
hexadecimal digits. This same encoding is also used for BRI and PRI.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-134  
In message types other than 50 and 51 (Level 2 Primitives), following the port  
address is a one octet field called the qualifier. The meaning of the qualifier  
varies according to the type (as specified by the MST encode) of ASAI message  
traced. The body which is a real ASAI message (except for Level 2 Primitives)  
follows the qualifier.  
When the display is administered for abbreviated format, the body contains only  
the initial part of the ASAI message (all information in beginning of message up  
to and including the Q.931 IE tag) plus the cause IE (if present).  
0x50 - ASAI level 2 uplink primitive  
Message[1] = Port Network Number of ASAI port  
Message[2] = reserved  
Message[3] = Carrier Address of ASAI port  
Message[4] = Port number of ASAI port  
Message[5] = SAPI  
Message[6] = TEI  
R1:  
Message[7,8] = Link ID  
Message[9]  
= Uplink encode  
0x01 - ASAI Link State  
0x02 - TEI Management Message  
0x03 - XID Message  
Message[10]  
= R1/R3 Link States:  
0x00 - the link has gone down  
0x01 - the link has come up  
0x02 - the link id has changed  
0x03 - the link has gone hyperactive  
0x04 - the link has recovered  
0x05 - the audit recovery stim  
0x06 - the link has been reset  
0x07 - link state hyper (too many SABMEs) disconnect  
0x08 - broadcast link audit  
= R1/R3 TEI Management Message  
0x01 - Identity request  
0x05 - Identity Check Response  
0x07 - Identity Verify Request  
= R1/R3 XID Messages  
0x01 - XID Request  
0x02 - XID Response  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-135  
R3:  
Message[7-10] = Link ID  
Message[11]  
= Uplink encode  
0x01 - ASAI Link State  
0x02 - TEI Management Message  
0x03 - XID Message  
Message[12]  
= ASAI Link State:  
0x00 - the link has gone down  
0x01 - the link has come up  
0x02 - the link id has changed  
0x03 - the link has gone hyperactive  
0x04 - the link has recovered  
0x05 - the audit recovery stim  
0x06 - the link has been reset  
0x07 - link state hyper (too many SABMEs)  
disconnect  
0x08 - broadcast link audit  
= TEI Management Message  
0x01 - Identity request  
0x05 - Identity Check Response  
0x07 - Identity Verify Request  
= XID Messages  
0x01 - XID Request  
0x02 - XID Response  
0x51 - ASAI level 2 downlink primitive  
Message[1] = Port Network Number of ASAI port  
Message[2] = Reserved  
Message[3] = Carrier Address of ASAI port  
Message[4] = Port number of ASAI port  
Message[5] = SAPI  
Message[6] = TEI  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-136  
R1:  
Message[7,8]  
= Link ID  
NOTE:  
The Link ID has no meaning for the link establish request, therefore the Link  
ID field will contain 0xff 0x.ff  
Message[9]  
= Downlink encode  
0x01 - ASAI Link Events  
0x02 - TEI Management Message  
0x03 - XID Message  
Message[10] = ASAI Link Events:  
0x02 - link release request  
0x0f - link establish request sent to and received by the lower  
level  
= TEI Management Message  
0x02 - Identity Assigned  
0x04 - Identity Check Request  
0x06 - Identity Remove  
= XID Messages  
0x01 - XID Request  
0x02 - XID Response  
Message[11] = 0xCA - Cancel Byte  
NOTE:  
The cancel byte will only be present if the message was built, but could not  
be sent.  
R3:  
Message[7-10]  
= Link ID  
NOTE:  
The Link ID has no meaning for the link establish request, therefore the Link  
ID field will contain 0xff 0xff 0xff 0x.ff  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-137  
Message[11]  
Message[12]  
= Downlink encode  
0x01 - ASAI Link Events  
0x02 - TEI Management Message  
0x03 - XID Message  
= ASAI Link Events:  
0x02 - link release request  
0x0f - link establish request sent to and received by  
the lower level  
= TEI Management Message  
0x02 - Identity Assigned  
0x04 - Identity Check Request  
0x06 - Identity Remove  
= XID Messages  
0x01 - XID Request  
0x02 - XID Response  
Message[13]  
= 0xCA - Cancel Byte  
NOTE:  
The cancel byte will only be present if the message was built, but could not  
be sent.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-138  
0x52 - ASAI maintenance uplink  
Message[1]  
Message[2]  
Message[3]  
Message[4]  
Message[5]  
= Port Network Number of ASAI port  
= Reserved  
= Carrier Address of ASAI port  
= Port number of ASAI port  
= 0  
Message[6+] = standard or abbreviated ASAI message format  
0x53 - ASAI maintenance downlink  
Message[1]  
Message[2]  
Message[3]  
Message[4]  
Message[5]  
= Port Network Number of ASAI port  
= Reserved  
= Carrier Address of ASAI port  
= Port number of ASAI 3 port  
= 0  
Message[6+] = standard or abbreviated ASAI message format  
0x54 - ASAI unrecognized uplink  
Message[1] = Port Network Number of ASAI port  
Message[2] = Reserved  
Message[3] = Carrier Address of ASAI port  
Message[4] = Port number of ASAI port  
Message[5] = failure cause  
Failure causes  
0x2a (42.) - Overload Controls in Effect  
0x32 (50.) - Requested Feature Not Administered  
0x45 (69.) - Requested Feature Not Implemented  
0x51 (81.) - Invalid CRV  
0x5f (95.) - Invalid Message  
0x60 (96.) - Mandatory Information Element Missing  
0x61 (97.) - Message Non-Existent/Not Implemented  
0x63 (99.) - Information Element non-existent  
0x64 (100.) - Invalid Information Element Contents  
0x6f (111.) - Protocol Error  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-139  
Message[6+] = standard or abbreviated ASAI message format  
NOTE:  
An unrecognized message displayed in abbreviated format may be  
missing information (such as cause) because the message was not able to  
be parsed.  
0x55 - ASAI unrecognized downlink  
Message[1] = Port Network Number of ASAI port  
Message[2] = Reserved  
Message[3] = Carrier Address of ASAI port  
Message[4] = Port number of ASAI port  
Message[5] = failure reason  
Failure reasons  
1 - link flow controlled  
2 - internal software error - see software error log  
3 - packet interface problem - see error log  
Message[6+] = standard or abbreviated ASAI message format  
0x56 - ASAI association uplink  
Message[1] = Port Network Number of ASAI port  
Message[2] = Reserved  
Message[3] = Carrier Address of ASAI port  
Message[4] = Port number of ASAI port  
Message[5] = association type  
Association Type  
0 - unknown  
1 - call control  
2 - domain control  
3 - notification  
4 - adjunct routing  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-140  
5 - set value  
6 - value query  
7 - request feature  
Message[6+] = standard or abbreviated ASAI message format  
0x57 - ASAI Association downlink  
Message[1]  
Message[2]  
Message[3]  
Message[4]  
Message[5]  
= Port Network Number of ASAI port  
= Reserved  
= Carrier Address of ASAI port  
= Port number of ASAI port  
= association type  
Message[6+] = standard or abbreviated ASAI message format  
0x58 - ASAI error uplink  
Message[1] = Port Network Number of ASAI port  
Message[2] = Reserved  
Message[3] = Carrier Address of ASAI port  
Message[4] = Port number of ASAI port  
Message[5] = failure cause  
Failure causes  
1 - 127 are code standard zero cause values  
128 - 255 are code standard three cause values (+ 128)  
Message[6+] = standard or abbreviated ASAI message format  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-141  
ISDN  
0x60 - ISDN PRI uplink  
Message[1]  
Message[2]  
Message[3]  
Message[4]  
= Port Network Number of D-channel port  
= Reserved  
= Carrier Address of D-channel port  
= Port number of D-channel port  
Message[5+] = standard ISDNPRI format  
NOTE:  
In abbreviated format, the header of the Q.931 message, the cause IE (if  
present) and the channel id Information Element (IE) (if present) are the  
only IEs present.  
0x62 - ISDN PRI downlink  
Message[1]  
Message[2]  
Message[3]  
Message[4]  
= Port Network Number of D-channel port  
= Reserved  
= Carrier Address of D-channel port  
= Port number of D-channel port  
Message[5+] = standard ISDNPRI format  
NOTE:  
In abbreviated format, the header of the Q.931 message, the cause IE (if  
present) and the channel id IE (if present) are the only IEs present.  
0x64 - ISDN BRI uplink  
Message[1] = Port Network Number of BRI port  
Message[2] = Reserved  
Message[3] = Carrier Address of BRI port  
Message[4] = Port number of BRI port  
Message[5] = SAPI  
Message[6] = TEI  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-142  
R1:  
Message[7,8] = Link ID  
Message[9+] = standard ISDNBRI format  
R3:  
Message[7-10]  
Message[11+]  
= Link ID  
= standard ISDNBRI format  
NOTE:  
In abbreviated format, the header of the Q.931 message, the cause IE (if  
present) and the channel id Information Element (IE) (if present) are the  
only IEs present.  
0x66 - ISDN BRI downlink  
Message[1] = Port Network Number of BRI port  
Message[2] = Reserved  
Message[3] = Carrier Address of BRI port  
Message[4] = Port number of BRI port  
Message[5] = SAPI  
Message[6] = TEI  
R1:  
Message[7,8] = Link ID  
Message[9+] = standard ISDNBRI format  
R3:  
Message[7-10] = Link ID  
Message[11+]  
= standard ISDNBRI format  
NOTE:  
In abbreviated format, the header of the Q.931 message, the cause IE (if  
present) and the channel id IE (if present) are the only IEs present.  
An additional cancel byte (0xCA) may be present after the standard  
ISDNBRI formatted message if the message was not sent. The cancel byte  
will not be appended if the abbreviated format is selected.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-143  
0x68 - ISDN BRI level 2 uplink primitive  
Message[1] = Port Network Number of BRI port  
Message[2] = Reserved  
Message[3] = Carrier Address of BRI port  
Message[4] = Port number of BRI port  
Message[5] = SAPI  
Message[6] = TEI  
R1:  
Message[7,8] = Link ID  
Message[9]  
= Uplink encode  
0x01 - BRI Link State  
0x02 - TEI Management Message  
0x03 - XID Message  
Message[10]  
= R1/R3 Link States:  
0x00 - the link has gone down  
0x01 - the link has come up  
0x02 - the link id has changed  
0x03 - the link has gone hyperactive  
0x04 - the link has recovered  
0x05 - the audit recovery stim  
0x06 - the link has been reset  
0x07 - link state hyper (too many SABMEs)  
disconnect  
0x08 - broadcast link audit  
= R1/R3 TEI Management Message  
0x01 - Identity request  
0x05 - Identity Check Response  
0x07 - Identity Verify Request  
= R1/R3 XID Messages  
0x01 - XID Request  
0x02 - XID Response  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-144  
R3:  
Message[7-10] = Link ID  
Message[11]  
= Uplink encode  
0x01 - BRI Link State  
0x02 - TEI Management Message  
0x03 - XID Message  
Message[12]  
= BRI Link State:  
0x00 - the link has gone down  
0x01 - the link has come up  
0x02 - the link id has changed  
0x03 - the link has gone hyperactive  
0x04 - the link has recovered  
0x05 - the audit recovery stim  
0x06 - the link has been reset  
0x07 - link state hyper (too many SABMEs)  
disconnect  
0x08 - broadcast link audit  
= TEI Management Message  
0x01 - Identity request  
0x05 - Identity Check Response  
0x07 - Identity Verify Request  
= XID Messages  
0x01 - XID Request  
0x02 - XID Response  
0x6A - ISDN BRI level 2 downlink primitive  
Message[1] = Port Network Number of BRI port  
Message[2] = Reserved  
Message[3] = Carrier Address of BRI port  
Message[4] = Port number of BRI port  
Message[5] = SAPI  
Message[6] = TEI  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-145  
R1:  
Message[7,8]  
= Link ID  
NOTE:  
The Link ID has no meaning for the link establish request, therefore the Link  
ID field will contain 0xff 0xff  
Message[9]  
= Downlink encode  
0x01 - BRI Link Events  
0x02 - TEI Management Message  
0x03 - XID Message  
Message[10] = BRI Link Events:  
0x02 - link release request  
0x0f - link establish request sent to and received by  
the lower level  
= TEI Management Message  
0x02 - Identity Assigned  
0x04 - Identity Check Request  
0x06 - Identity Remove  
= XID Messages  
0x01 - XID Request  
0x02 - XID Response  
Message[11] = 0xCA - Cancel Byte  
NOTE:  
The cancel byte will only be present if the message was built, but could not  
be sent.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-146  
R3:  
Message[7-10]  
= Link ID  
NOTE:  
The Link ID has no meaning for the link establish request, therefore the Link  
ID field will contain 0xff 0xff 0xff 0x.ff  
Message[11] = Downlink encode  
0x01 - BRI Link Events  
0x02 - TEI Management Message  
0x03 - XID Message  
Message[12] = BRI Link Events:  
0x02 - link release request  
0x0f - link establish request sent to and received by  
the lower level  
= TEI Management Message  
0x02 - Identity Assigned  
0x04 - Identity Check Request  
0x06 - Identity Remove  
= XID Messages  
0x01 - XID Request  
0x02 - XID Response  
Message[13] = 0xCA - Cancel Byte  
NOTE:  
The cancel byte will only be present if the message was built, but could not  
be sent.  
0x6C - ISDN PRI level 2 uplink primitive  
Message[1] = Port Network Number of D-channel port  
Message[2] = Reserved  
Message[3] = Carrier Address of D-channel port  
Message[4] = Port number of D-channel port  
Message[5] = change type  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-147  
R1/R3 change types:  
0x01 - session up notification  
0x02 - Session down notification  
0x6D - ISDN PRI level 2 downlink primitive (not implemented)  
Message[1] = Port Network Number of D-channel port  
Message[2] = Reserved  
Message[3] = Carrier Address of D-channel port  
Message[4] = Port number of D-channel port  
Message[5] = change type  
R1/R3 change types:  
0x01 - link establish request  
0x02 - link release request  
0x6E - ISDN PRI Unrecognized Messages  
Message[1] = Port Network Number of D-channel port  
Message[2] = Reserved  
Message[3] = Carrier Address of D-channel port  
Message[4] = Port number of D-channel port  
Message[5] = type of failure  
Types of failure:  
0x01 - outgoing ISDNPRI  
0x02 - incoming ISDNPRI  
Message[6+] = standard ISDN format  
0x6F - ISDN BRI Unrecognized Messages  
Message[1] = Port Network Number of BRI port  
Message[2] = Reserved  
Message[3] = Carrier Address of BRI port  
Message[4] = Port number of BRI port  
Message[5] = SAPI  
Message[6] = TEI  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list mst  
2
2-148  
R1:  
Message[7,8]  
Message[9]  
= Link ID  
= type of failure  
Types of failure:  
0x01 - outgoing ISDN  
0x02 - incoming ISDN  
Message[10+] = standard ISDNBRI format  
R3:  
Message[7-10]  
Message[11]  
= Link ID  
= type of failure  
Types of failure:  
0x01 - outgoing ISDN  
0x02 - incoming ISDN  
NOTE:  
In abbreviated format, the header of the Q.931 message, the cause IE (if  
present) and the channel id IE (if present) are the only IEs present.  
An additional cancel byte (0xCA) may be present after the standard  
ISDNBRI formatted message if the message was not sent. The cancel byte  
will not be appended if the abbreviated format is selected.  
General  
0x71 - GAP marker  
Message[1] = GAP reason  
Message[2] = GAP count (since last clear - high byte)  
Message[3] = GAP count (since last clear - low byte)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list suspend-alm-orig  
2
2-149  
GAP reasons:  
0x01 - disabled, disable mst command executed  
0x02 - disabled, mst timer expired  
0x03 - disabled, buffer full on no-wrap  
0x04 - disabled, restart occurred  
0x05 - disabled, by stop trigger or count  
0x06 - disabled, audit error  
0x07 - not disabled, stopped by stop trigger or count  
0x72 - Time changed while trace enabled  
Message[1] = 0x00  
Message[2] = timestamp indication  
timestamp indication:  
0x00 - MST timestamp is old time  
0x01 - MST timestamp is new time  
list suspend-alm-orig  
This command lists active entries in the Suspend Alarm Origination table. Even  
though this command only lists active entries, an entry that expires during the list  
process still appears in the output. If the Suspend Alarm Origination table is  
empty, the output contain only the title and field headings.  
Feature  
Action/Object  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list  
Report sent to printer.  
init  
none  
none  
suspend-alm-  
orig  
inads  
craft  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
list suspend-alm-orig  
list suspend-alm-orig print  
list suspend-alm-orig schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list sys-link  
2
2-150  
Output  
list suspend-alm-orig  
Suspend Alarm Origination Entries  
Physical  
Board  
Expires At  
01C03  
01E0407  
01E0406  
off-only  
on-and-off  
on-and-off  
06/11/15:06  
06/11/17:26  
06/12/45:34  
list sys-link  
This command displays all of the system links, including the location, link type  
and channel number, link state, current path status, faulted path status, and last  
recorded fault, if any. See ‘‘SYS-LINK (System Links)’’ for details.  
Feature  
Action/Object  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
list sys-link  
Report sent to printer  
init  
none  
none  
inads  
craft  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
list sys-link print  
list sys-link schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list testcalls  
2
2-151  
Output  
The following examples shows the output from the list sys-link command.  
list sys-link  
Page  
1
SPE A  
SYSTEM LINKS INFORMATION  
Location Link Type/ State Current  
Faulted  
Path  
Last Fault  
Recorded  
Channel  
Path  
01A0516  
PRI  
up  
present  
present  
12/30/1996 14:18  
press CANCEL to quit -- press NEXT PAGE to continue  
Field descriptions  
Location  
Physical location of the port associated with the system link  
(cabinet-carrier-slot-circuit)  
Link  
Type/Channel  
Type of system-link and the processor channel number of the link (if  
there is one): for TN798, link type is PRI (PRI).  
State  
System link state: upor down  
Current Path  
Status of the current path: noneif the link is down; presentif the  
current path is valid  
Faulted Path  
Specifies the faulted path status: presentif the link has been  
faulted at least once, noneif the link has never gone down, and  
defaultif the default faulted path is being used  
Last Fault  
Recorded  
Date and time of the most recent fault  
list testcalls  
This command generates an Automatic Transmission Measurement System  
(ATMS) report. The ATMS allows the voice and data trunk facilities to be  
measured for satisfactory transmission performance. The performance of the  
trunks is evaluated according to measurements produced by a series of analog  
tests and are compared against user-defined threshold values. The purpose of  
the report is to provide measurement data to help determine the quality of trunk  
lines. The measurement report contains data on trunk signal loss, noise, singing  
return loss, and echo return loss.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list testcalls  
2
2-152  
The measurements are produced by a set of analog trunk tests. The tests are  
initiated by a maintenance demand test or by a set of scheduled tests. The  
largest portion of these measurements are generated through scheduled testing  
during system quiet hours (hours where the traffic volume is low). Each trunk test  
performed by the system stores the results in a database. The trunk  
measurements in this database reflect the state of each trunk at the time of its last  
test.  
Action/Object  
Qualifiers/Options  
Qualifier/Option Description  
list testcalls  
detail  
summary  
Detailed measurement report displayed  
Summary measurement report displayed  
grp group number  
Measurements for a specific trunk group displayed. When used  
with the to-grp option, this option is the starting trunk group in a  
range of user-specified trunk groups.  
to-grp group number  
Measurements for all trunk groups from 1 to the specified  
“to-grp” trunk group are displayed. When used with the grp  
option, this option is the ending trunk group in a range of  
user-specified trunk groups.  
mem member number  
Measurements for a specific trunk group member displayed.  
When used with the to-mem option, this option is the starting  
trunk group member in a range of user-specified trunk group  
members.  
to-mem member number  
Measurements for all trunk group members from 1 to the  
specified “to-mem” trunk group member displayed. When used  
with the mem option, this option is the ending trunk group  
member in a range of user-specified trunk group members.  
port location  
Measurements for a specific trunk circuit (port) displayed  
result result identifier  
This option is used to filter out all measurement results that do  
not match the user-specified result, that is, only measurement  
results that match the user specified result are displayed.  
Examples of results are pass, marg, fail, etc.  
not-result result identifier  
count count number  
This option is used to filter out all measurement results that do  
match the user-specified result, that is, only measurement  
results that do not match the user specified result are displayed.  
Examples of results are pass, marg, fail, etc.  
This option is used to specify (limit) the number of records  
displayed.  
print  
Report sent to printer  
schedule  
Command is validated and then a scheduling form displays to  
schedule execution of the command. The command is then  
placed in the command queue and is executed at the specified  
time. The information displayed by the command is sent to the  
1
system printer instead of the screen.  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list testcalls  
2
2-153  
Examples  
list testcalls detail  
list testcalls detail print  
list testcalls detail grp 78  
list testcalls detail grp 78 result marg count 3 schedule  
list testcalls detail grp 78 to-grp 80  
list testcalls detail grp 78 to-grp 80 mem 1 print  
list testcalls detail grp 78 to-grp 80 mem 1 not-result pass  
list testcalls detail grp 78 to-grp 80 mem 1 count 2 schedule  
list testcalls detail grp 78 to-grp 80 mem 1 to-mem 5  
list testcalls detail grp 78 to-grp 80 mem 1 to-mem 5 count 3 print  
list testcalls detail grp 78 to-grp 80 mem 1 to-mem 5 count 3 result pass  
list testcalls detail mem 1 count 3 result pass  
list testcalls detail to-grp 78 to-mem 4 count 3 result pass  
list testcalls detail to-mem 3 result pass  
list testcalls detail port 1c1504  
list testcalls detail port 1c1504 count 5 schedule  
list testcalls detail port 1c1504 count 5 not-result marg print  
list testcalls summary  
list testcalls summary grp 78  
list testcalls summary grp 78 print  
list testcalls summary grp 78 count 5  
list testcalls summary grp 78 count 5 schedule  
list testcalls summary grp 78 to-grp 80  
list testcalls summary grp 78 to-grp 80 count 3  
list testcalls summary to-grp 78  
list testcalls summary to-grp 78 count 7 schedule  
Output  
The following example is of the output for the list testcalls detail grp 80  
command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list testcalls  
2
2-154  
list testcalls detail grp 80  
Page  
1
SPE A  
ATMS MEASUREMENT REPORT  
Vendor: TTL Type: 105-w-rl  
Loss dev at  
1004Hz-loss 404Hz 2804Hz C-msg C-ntch SRL SRL  
Group: 80  
Type: co  
THRESHOLD VALUES  
Min  
-2  
-2  
Max  
21  
21  
- + - +  
9 9 9 9  
9 9 9 9  
Noise Noise LO HI  
ERL  
0
0
Marginal  
Unacceptable  
55  
55  
74  
74  
0
0
0
0
Trk Test Test Test -16dBm 0dBm  
Mem Date Time Rslt NE FE NE FE NE FE NE FE NE FE NE FE NE FE NE FE NE FE  
1
2
3
4
5
6
7
8
9
press CANCEL to quit -- press NEXT PAGE to continue  
Detail report field descriptions  
Group  
The trunk group number selected.  
Type  
The trunk group type.  
Vendor  
The vendor of this trunk group.  
The kind of test line for this trunk group.  
TTL Type  
Threshold Values  
The list of marginal and unacceptable threshold values defined  
on the trunk group form.  
The following fields appear on the lower section of the form. Many  
of the column headings contain the abbreviations “FE” for far end  
and “NE” for near end. These abbreviations define which end  
took the measurements.  
Trk Mem  
The trunk member within the trunk group.  
The month and day this trunk was tested.  
The time of day this trunk was tested.  
Test Date  
Test Time  
Tst Rslt  
This field describes the results of the trunk transmission test.  
1004Hz-loss Min  
Far-to-near and near-to-far measurements of 1004-Hz loss from  
low-level tone.  
1004Hz-loss Max  
Far-to-near and near-to-far measurements of 1004-Hz loss at 0  
dDBomwn.load from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
list testcalls  
2
2-155  
Loss dev at 404Hz  
Loss dev at 2804Hz  
C-msg Noise  
Transmission tests at low frequency. These tests measure a  
maximum positive and negative deviation of +9 and -9 dB from  
the 1004-Hz loss measurements.  
Transmission tests at high frequency. These tests measure a  
maximum positive and negative deviation of +9 and -9 dB from  
the 1004-Hz loss measurements.  
Maximum noise interference (in dBrnC: decibels above reference  
noise, which is B(EQ)10 sup -12E(EQ) watts) terminating on a  
voice terminal within the voice-band frequency range (500 to  
2500 Hz) between 15 and 55 dBrnC.  
C-ntch Noise  
SRL-LO  
Maximum signal-dependent noise interference on a line between  
34 and 74 dBrnC.  
Singing return loss from 0 to 40 dB between the sum of the circuit  
(repeater) gains and the sum of the circuit losses. SRL-LO occurs  
most often in the frequency range of 200 to 500 Hz.  
SRL-HI  
ERL  
Singing return loss from 0 to 40 dB between the sum of the circuit  
(repeater) gains on a circuit and the sum of the circuit losses.  
SRL-HI occurs most often in the frequency range of 2500 to 3200  
Hz.  
Echo return loss from 0 to 40 dB between the level of signal  
strength transmitted and the level of signal strength reflected.  
ERL occurs most often in the frequency range of 500 to 2500 Hz.  
The following example is the output from the list testcalls summary grp 80  
command.  
list testcalls summary grp 80  
SPE A  
ATMS MEASUREMENT SUMMARY REPORT  
Trunks Trunks  
Last Passed Failed  
Test Transm Marginal Unaccept In- Not  
Trunks  
Failed  
Trk Num  
Grp Of  
Last  
Test  
Trks Trks Busied  
Out  
Num Trks Date  
Time  
Test  
0
Threshld Threshld Use Test Trunks  
80 19  
0
0
0
19  
19  
Command successfully completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
mark port  
2
2-156  
Summary report field descriptions  
Trk Grp Num  
The trunk group number which is being summarized. Only  
outgoing or two-way analog trunks will be listed.  
Num Of Trks  
The total number of members per trunk group.  
Last Test Date  
Last Test Time  
The date of the oldest measurement in the trunk group.  
The time of the oldest measurement in the trunk group.  
Trunks Passed  
Transm Test  
The number of trunks that have passed the trunk transmission  
tests.  
Trunks Failed  
Marginal Threshld  
The number of trunks that failed a marginal threshold, but not an  
unacceptable threshold according to the threshold values defined  
on the trunk group form.  
Trunks Failed  
Unaccept Threshld  
This is taken from the unacceptable threshold administered on the  
Trunk group form.  
Trks In-Use  
The number of trunks that were in-use at the time of testing.  
Trks Not Test  
Busied Out Trunks  
The number of trunks that were not tested due to error conditions.  
The number of trunks that were busied out at the time. This could  
be due to hardware problems, incorrect threshold values, etc.  
mark port  
This command marks faulty ports as defective to prevent their use in other  
administrative operations (for example, adding a data-module or station). Ports  
on any type of circuit pack may be marked except for installed circuit packs that  
are administered automatically (for example, Tone Detector, Tone Generator,  
Announcement, Speech Synthesizer, Call Classifier and Maintenance/Test circuit  
packs). If the port can be administered manually, and it is unassigned, the port is  
marked as faulty. The clear port command reactivates the port. The list  
marked-ports command displays marked ports in list format. All marked port  
information is saved as part of translations.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
mark port  
location  
Location of the port to be marked:  
init  
none  
none  
PCSSpp  
inads  
craft  
Examples:  
mark port 1c0208  
mark port 2a1001  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor bcms  
2
2-157  
monitor bcms  
This command displays output for agents and splits and summarizes the bcms  
condition. This on-line status report automatically updates every 30 seconds (or  
by pressing the UPDATE key) until the command is canceled by pressing the  
CANCEL key. Three display options are available: skill, split, and system.  
Qualifier  
Feature  
Action/Object  
Qualifier  
Description  
Permissions  
Defaults  
Interactions  
monitor bcms  
split  
init  
none  
none  
split number  
system  
inads  
craft  
system number  
skill  
skill number  
cust  
rcust  
bcms  
browse  
Qualifier Description  
split  
Specifies that the command display status information for a specified  
split number (an ACD hunt group).  
split  
number  
The split’s identity to the switch and BCMS; an ACD hunt group  
number (split number). This parameter is entered only when the “split”  
parameter is entered.  
system  
This specifies that the command display split queue status as well as  
cumulative split information for all the BCMS measured splits.  
system  
number  
ACD hunt group numbers (split numbers) separated by spaces and/or  
split number ranges separated by a hyphen (-).  
skill  
This specifies that the command display status information for a  
specified skill number.  
skill  
number  
The skill’s identity to the switch and BCMS; an ACD hunt group  
number (skill number). This parameter is entered only when the “skill”  
parameter is entered.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor bcms  
2
2-158  
Output  
The following examples shows the output from the monitor bcms system  
command.  
monitor bcms system  
Page  
BCMS SYSTEM STATUS  
1 of  
1
Date:  
AVG  
ANSW AVAIL  
SPEED AGENT ABAND  
14:02 THU OCT 17 1991  
AVG  
AVG  
AFTER  
CALL  
CALLS OLDEST  
#
ABAND  
TIME  
:30  
#
AVG  
TALK  
SPLIT  
Service  
Sales  
WAIT  
CALL  
1:03  
:33  
ACD  
20  
36  
3
5
:45  
:15  
0
0
3
2:30 1:25  
1:32 :35  
11  
:45  
Field descriptions  
Date:  
SPLIT  
The current date and time which is updated every 30 seconds or  
when the UPDATE key is pressed.  
The name of the split being reported, if no name is administered  
then the split extension is displayed in the form “EXTxxxxx”.  
Splits are displayed in split number order. This field is translation  
data.  
CALLS WAIT  
The number of calls currently waiting in this split’s queue. If any  
of these calls are Direct Agent Calls, the field will be preceded  
by an asterisk. This field is real-time status data.  
OLDEST CALL  
The amount of time that the oldest call has waited in queue. This  
field is real-time status data.  
AVG ANSW SPEED  
The average speed of answer for this split during the current  
period. This includes time in queue and time ringing at the  
agent’s voice terminal. Calls that intraflow (calls that overflow  
from one ACD split to another split) will not have queue time from  
previous splits included in the average. The calculation is Total  
Answer Time/Total Automatic Call Distribution (ACD) Calls. This  
field is measurement data and includes only those calls that have  
completed (terminated).  
AVAIL AGENT  
# ABAND  
The number of agents in this split currently available to receive  
an Automatic Call Distribution (ACD) call from this split. This field  
is real-time status data.  
The number of calls that have abandoned during the current  
period. This field is measurement data.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor bcms  
2
2-159  
AVG ABAND TIME  
The average time abandoned calls waited in queue before  
abandoning during the current period. The calculation is Total  
Abandon Time/Total Calls Abandoned. This field is measurement  
data and includes only those calls that have completed  
(terminated).  
# ACD  
The number of Automatic Call Distribution (ACD) calls handled  
by this split during the current period. This includes calls that  
intraflow into the split. This field is measurement data.  
AVG TALK  
The average talk time for Automatic Call Distribution (ACD) calls  
handled by this split during the current period. This does not  
include ring time at the agents’ voice terminal. The calculation is  
Total ACD Talk Time/Number of ACD Calls. This field is  
measurement data and includes only those calls that have  
completed (terminated).  
AVG AFTER CALL  
The average After Call Work (ACW) time for Automatic Call  
Distribution (ACD) calls handled by this split during the current  
period. ACD calls with no ACW time are included in the average.  
Time spent on direct incoming or outgoing calls while in ACW will  
not be included in the average. The calculation is (Total ACW  
Time - Total ACW Incoming Time - Total ACW Outgoing  
Time)/Total ACD Calls. This field is measurement data and  
includes only those calls that have completed (terminated).  
The following example shows the output from the monitor bcms split 1  
command.  
monitor bcms split 1  
Page  
1 of  
1
SPE A  
BCMS SPLIT (AGENT) STATUS  
Split: 1  
Split Name: hunt group 1  
Calls Waiting: 0  
Oldest Call: 0:00  
Date:  
9:02 TUE OCT 22 1991  
0=Staffed  
AGENT  
0=Avail  
EXT STATE  
0=ACD  
0=ACW  
TIME  
0=AUX  
0=Extn  
0=OtherSplit  
ACD  
EXTN IN EXTN OUT  
CALLS  
CALLS  
CALLS  
Field descriptions  
Split:  
The number of the split requested. This field is translation data.  
Split Name:  
The name of the split requested. If no name exists the split  
extension is displayed in the form “EXT xxxxx”. This field is  
translation data.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor bcms  
2
2-160  
Date:  
The current date and time which is updated every 30 seconds or  
when the UPDATE key is pressed.  
Calls Waiting:  
The number of calls currently waiting in this split’s queue. If any of  
these calls are Direct Agent Calls, the field will be preceded by an  
asterisk. This field is real-time status data.  
Oldest Call:  
Staffed  
The time in minutes:seconds that the current oldest call has  
waited in this split’s queue. This field is real-time status data.  
The number of agents currently logged into this split. This field is  
real-time status data.  
Avail  
The number of agents currently available to receive an Automatic  
Call Distribution (ACD) call in this split. Agents are in either the  
Auto-in or Manual-in work modes and are not currently on a call. If  
the agent is on another split’s call or in After Call Work (ACW) for  
another split, this agent is not considered available and will not be  
recorded here. This field is real-time status data.  
ACD  
The number of agents in this split currently on an Automatic Call  
Distribution (ACD) call for this split. This includes ACD calls that  
are being handled by this split that arrive as coverage from  
another split. This field also includes outbound calls (Outgoing  
Call Manager) that are distributed through the ACD. Note that if  
an agent puts an ACD call on hold, but does not enter another  
state (for example, the agent does not enter the AVAIL state), the  
agent will still be seen as in the ACD state. This field is real-time  
status data.  
ACW  
AUX  
The number of agents in this split currently in After Call Work  
(ACW) for this split. This field is real-time status data.  
The number of agents in this split currently in AUX work for this  
split. If an agent is on another split’s call or in After Call Work  
(ACW) for another split, this agent is not considered in AUX work  
and will not be recorded here. This field is real-time status data.  
Extn  
The number of agents in this split currently on non-ACD  
(Automatic Call Distribution) calls, either incoming or outgoing  
directly to or from their extensions. If the agents are also in After  
Call Work (ACW) or AUX they will be recorded as Extn rather than  
ACW or AUX. This field is real-time status data.  
Other Split  
The number of agents in this split on another split’s call or in After  
Call Work (ACW) for another split. Only used if agents belong to  
multiple splits. This field is real-time status data.  
AGENT  
EXT  
The name of the agent associated with the extension. If no name  
exists this field will be left blank. This field is translation data.  
The extension of the agent. This field is translation data.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor health  
2
2-161  
STATE  
The current state of the agent for this split. This possible states  
are Avail, ACD, ACW, AUX, Extn In, Extn Out, OtherSplit, and  
Unstaff. If an agent is staffed, the agent must also be in one of the  
above states. This field is real-time status data.  
TIME  
The clock time that the agent entered the current state in  
hours:minutes. This field is real-time status data.  
ACD CALLS  
The number of Automatic Call Distribution (ACD) calls (inbound  
and outbound), that the agent has completed for this split during  
the current period (half hour or hour). The maximum number of  
calls is 255, and if this maximum is exceeded, 255 is displayed.  
This field is measurement data.  
EXTN IN CALLS  
The number of non-ACD (Automatic Call Distribution) calls that  
the agent has received (incoming) and completed during the  
current period. The maximum number of calls is 255, and if this  
maximum is exceeded, 255 is displayed. This field is  
measurement data.  
EXTN OUT CALLS  
The number of non-ACD (Automatic Call Distribution) calls that  
the agent has made (outgoing) and completed during the current  
period. The maximum number of calls is 255, and if this maximum  
is exceeded, 255 is displayed. This field is measurement data.  
monitor health  
This command displays the current system alarm summary, maintenance busy  
summary, user summary, critical system status, and cabinet status, that are  
updated every minute.  
After this command is terminates, users are logged off.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
monitor health  
init  
none  
If standby SPE  
inads  
craft  
cust  
nms  
browse  
Emergency Transfer  
Select Switches change  
and handshakes are  
down, the displayed  
Emerg Trans field is  
incorrect until handshake  
reintializes.  
When the monitor health  
command terminates,  
users are logged off of  
the system.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor health  
2
2-162  
Output  
The following example is a display of the monitor system health command.  
status health  
ALARM SUMMARY  
CABINET STATUS  
Major: 0  
Minor: 9  
Emerg Alarms  
Warning: 4  
Cab Trans Mj Mn Wn PNC  
1
2
3
4
off  
off  
0| 7| 0 up  
0| 0| 4 up  
BUSY-OUT SUMMARY  
Trunks: 0  
Stations: 0  
n.a. 0| 2| 0 up  
off 0| 0| 0 up/up  
Others: 0  
PROCESSOR OCCUPANCY STATUS  
Static:  
3%  
SM:  
6%  
CP: 10%  
Idle: 81%  
CRITICAL SYSTEM STATUS  
Active SPE: A/auto  
Duplicated? SPE:n  
SPE Power: commercial  
Time Source: external  
9:33 TUE JAN 29 1991  
- Press CANCEL to quit -  
# Logins: 2  
Field descriptions  
Major  
The number of logged major alarms (0 – 200).  
The number of logged minor alarms (0 – 200).  
Number of warnings logged in the alarm file (0 – 200).  
Number of busied out maintenance trunks.  
Number of busied out maintenance stations.  
Minor  
Warning  
Trunks  
Stations  
Others  
Combined number of busied out maintenance objects excluding  
trunks and stations.  
Static  
SM  
Proportion of the CPU currently dedicated to high priority items. This  
percentage is rounded to the nearest integer, therefore 0 percent  
means that the occupancy is less than one half of a percent.  
Proportion of the CPU currently dedicated to system management or  
periodic and scheduled maintenance. If large amounts of periodic or  
scheduled maintenance testing performs, this occupancy percentage  
can be high without affecting service. This percentage is rounded to  
the nearest integer, therefore 0 percent means that the occupancy is  
less than one half of a percent.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor health  
2
2-163  
CP  
Proportion of the CPU currently dedicated to call processing. This  
occupancy has priority over SM and IDLE occupancy categories and  
takes processor time away from these occupancy categories, if  
needed. This percentage is rounded to the nearest integer, therefore 0  
percent means that the occupancy is less than one half of a percent.  
Idle  
Proportion of the CPU currently available. This percentage is rounded  
to the nearest integer, therefore 0 percent means that the occupancy  
is less than one half of a percent.  
Active SPE  
Currently-active processor complex. When the active processor  
complex is locked on-line with lock switching on DUPINT, the “lock”  
option displays; otherwise, “auto” displays.  
Duplicated?  
SPE Power  
Duplication status of the SPE (n).  
Current power source for the processor complex. The normal state is  
“commercial”. When commercial power is unavailable, in-use battery  
backup is indicated with “backup”.  
Time Source  
Current timing source is displayed. The display values for this field  
vary according to timing sources selected. If the site administers the  
optional Stratum-3 hardware, “external” displays and “internal”  
displays when an internal source, such as a tone clock, is used.  
Primary and secondary timing sources must be administered when  
using the Stratum-4 option.  
“primary” = primary administered source is in use  
“secondary” = secondary administered source is in use.  
“local” = neither the primary or secondary sources are in use.  
Number of current users.  
# Logins  
Cab  
Assigned cabinet number, ranging from 1 to the highest cabinet  
number in the system.  
Emerg Trans  
Current setting of the emergency transfer switch for each cabinet. Five  
options are available: auto-on (“auto+” or “a+”), auto-off (“auto-” or  
“a-*, “on”, “off”, and “n.a.”. If “auto+” or “auto-” option are enabled,  
emergency transfers automatically activate when cabinets fail (“+”  
indicates that emergency transfer is activated, while “-” indicates that  
emergency transfer is inactive). When “on” is displayed, emergency  
transfer automatically activates. The “off” option shows that cabinets  
cannot activate emergency transfers. In duplicated SPE systems,  
switch settings for both processors of the PPN (cabinet 1) display. In  
this case, “auto+” is abbreviated “a+”, “auto-” is d “a-”, and “off” is  
“of”. “on” does not changed. If “n.a.” displays, emergency transfer  
switch settings are not available.  
Mj  
Mn  
Number of major alarms associated with the cabinet. An asterisk fills  
the field when the number exceeds 99.  
Number of minor alarms associated with the cabinet. An asterisk fills  
the fielDdowwnhloeand ftrhome Wnuwmw.bSoemraenxuacles.ecodms. A9l9l M. anuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor security-violations  
2
2-164  
Wn  
Number of Wn associated with the cabinet. An asterisk fills the field  
when the number exceeds 99.  
PNC  
Displays current Port Network Connectivity (PNC) status for each port  
network within a cabinet. When multiple port networks exist within a  
cabinet, a slash separates Carriers A, B, and C (listed first) from  
Carriers D and E (up/up). Availability of the Expansion Archangel Link  
(EAL) determines the PNC status of a port network. “Up” denotes EAL  
availability. When the EAL is not available, then “dn” (down) displays.  
Time of Day  
Displays current time of day acquired from the system.  
monitor security-violations  
This command displays information about failed attempts to access the system,  
including the time of the violation, the login entered, and the port accessed  
during the failed login attempt. The system logs trunk group numbers, members,  
and extensions for remote access violations. The system logs remote and local  
invalid access attempts with a total of 16 entries maintained for each access  
type. This online status report automatically updates every 30 seconds until the  
command is canceled by pressing the CANCEL key.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
monitor  
security-violations  
print  
Reports print to SAT-linked  
printers.  
init  
inads  
craft  
none  
none  
cust  
rcust  
bcms  
browse  
Output  
The following example shows the output from the monitor security-violations  
command.  
monitor security-violations  
SECURITY VIOLATIONS STATUS  
SPE A  
Date:  
9:12 MON DEC 30 1991  
SYSTEM MANAGEMENT VIOLATIONS  
REMOTE ACCESS VIOLATIONS  
Date  
Time Login Port  
Ext  
Date  
Time  
TG No.  
Mbr Ext  
1111  
12/30 09:12 init  
12/30 09:12 init  
12/30 09:12 init  
MGR1  
MGR1  
MGR1  
12/30 12:42 80  
1
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor system  
2
2-165  
Field descriptions  
Date:  
Date  
Current date and time.  
Date of the logged security violation shown as MM/DD (where MM =  
month and DD = day).  
Time  
Time of the logged security violation shown as HH:MM (where HH =  
the hour and MM = minute of the invalid access attempt).  
Login  
Port  
Login ID entered for the login violation attempt.  
Type of port used when login violation occurred. The following is a  
table of valid port types:  
MGR1  
Ext  
MGR1 represents a connection to a system SAT port. Connections are  
either hardwired or dialed-up.  
Extension assigned to the data module that failed during “logging in”  
session. If a data module is not used, this field is blank.  
Date  
Time  
TG No.  
Mbr  
Date of the logged security violation shown as MM/DD (where MM =  
month and DD = day).  
The time of the logged security violation shown as HH:MM (where HH  
= the hour and MM = the minute).  
The trunk group number associated with the trunk from the failed  
remote access attempt (remote access violations only).  
The trunk group member number associated with the trunk from the  
failed remote access attempt (remote access violations only).  
Ext  
Extension that interfaces with remote access features (remote access  
violations only).  
monitor system  
This command summarize the system’s condition. This on-line status report  
automatically updates every minute (or by pressing the UPDATE key) until the  
command is canceled by pressing the CANCEL key. For security reasons, the  
cancel command automatically logs off technicians.  
Overall system status is available with either view option. “View1” displays  
attendant, maintenance, and traffic status. Attendant and maintenance status  
update every minute and traffic status updates hourly. “View2” displays all  
“View1” items, except hunt group measurements that are omitted from traffic  
status portions. These screens contain simplified high-level information about the  
system’s health. The monitor system conn command displays connection’s  
status in the connection manager process. Data is collected frequently in the  
connection manager for key information items used to create this report.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor system  
2
2-166  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
monitor  
system  
view 1  
view 2  
conn  
pnn ###  
pnn ###  
pnn ###  
see below  
init  
none  
none  
inads  
craft  
cust  
nms  
browse  
Qualifier Description  
view1  
This screen displays attendant status, maintenance status, last hour’s  
measurement of trunk groups, hunt groups, attendant groups, and the  
time of day.  
view2  
conn  
This screen displays a subset of view1 form entries. It includes view1  
forms except the last hour’s hunt group measurements.  
This option displays the connection monitor output for key information.  
entering no  
options  
Omitting “pnn # # #” arguments on the command line displays the  
default configuration of Pnn’s 1, 2 and 3.  
pnn # # #  
Entering “pnn # # #” (where a pnn number from 1 to 3 replaces “#”, and  
displays data for specified pnns.  
entering no  
options  
Omitting the “pnn # # #” argument on the command line displays  
default configurations of Pnn’s 1, 2 and 3.  
pnn # # #  
Entering “pnn # # #”, where “#” is replaced by a pnn number from 1 to  
3, displays data for specified pnns.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor system  
2
2-167  
Output  
Below are displays of monitor system view 1 and monitor system view 2.  
monitor system view1  
ATTENDANT STATUS  
MAINTENANCE STATUS  
Console no.  
Activated: 1 2 3 4 5 6  
# of alarms for trunks: 4  
# of alarms for stations: 2  
# of alarms for other res: 1  
Deactivated: 7 8  
First OSS number has been informed? n  
TRAFFIC STATUS  
Measurement Hour: 1800  
Trunk Group Measurement  
(4 grps with highest %time ATB)  
Grp no: 78  
Hunt groups Measurement  
(4 grps with highest # of qued calls)  
Grp no: 16  
Grp dir:  
Calls qued: 2  
Calls qued: 1  
%Out blkg:  
Calls aban: 1  
Attendant Group Measurement  
%Time ATB:  
Calls qued: 1  
Calls aban: 0  
16:06 WED MAR 6 1996  
- press CANCEL to quit -  
monitor system view2  
ATTENDANT STATUS  
MAINTENANCE STATUS  
Console no.  
Activated: 1 2 3 4 5 6  
# of alarms for trunks: 4  
# of alarms for stations: 2  
# of alarms for other res: 1  
Deactivated: 7 8  
First OSS number has been informed? n  
TRAFFIC STATUS Measurement Hour: 1800  
Trunk Group Measurement  
(4 grps with highest %time ATB)  
Grp no: 78  
Grp dir:  
Calls qued: 1  
%Out blkg:  
%Time ATB:  
Attendant Group Measurement  
Calls qued: 1  
Calls aban: 0  
16:08 WED MAR 6 1996  
- press CANCEL to quit -  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor system  
2
2-168  
Field descriptions  
Console #  
A list of console numbers that are activated or deactivated.  
The attendant console is active. An attendant console activated if:  
Activated:  
■ its handset/headset is plugged in  
■ it is not busied out, and the system is in day service and the  
console is a day or day/night or principle console, or the system is  
in night service and the console is a night or day/night console.  
Deactivated:  
The attendant console is inactive. The attendant console deactivated if  
it does not meet activated conditions.  
# of alarms  
for trunks  
The number of existing minor and major trunk port alarms.  
# of alarms  
for other  
resources  
The number of existing minor and major alarms on all maintainable  
objects in the system, except trunks and stations.  
First OSS  
number has  
been  
Questions if the first OSS telephone number reports and  
acknowledges alarms. If “Alarm Origination” is disabled or there are  
no active alarm, the field is “n”.  
informed?  
Measurement  
Hour  
The starting time for taking measurements. For example, if the  
measurement hour is shown as 1800, traffic status data display is the  
time period from 6 PM to 7 PM (The measurement is taken hourly).  
Grp no  
A number between 1 and the maximum trunk or hunt group number.  
Group direction: incoming, outgoing or two way.  
Grp dir  
Calls qued  
Calls aban  
%Out blkg:  
Total calls that arrive and are placed in the trunk group queue.  
Total abandoned calls by the caller.  
The ratio of outgoing calls that are not carried (due to overload  
conditions) on a trunk group to outgoing calls offered.  
% Time ATB:  
Time of day  
The percentage of time within polling intervals that all trunks in the  
trunk group are unavailable for use.  
The current time of day acquired from the system.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor system  
2
2-169  
The following example is a display of the monitor system conn command.  
Time Slot Status  
Bus State *Idle Count  
Bus Status  
Pnn Bus State  
Pnn  
10  
10  
10  
10  
22  
22  
22  
22  
1
0
Maint  
0
10  
10  
22  
22  
1
0 Avail  
1 Avail  
0 Avail  
1 Avail  
0 Avail  
1 Avail  
1
0
1
0
1
0
1
0
1
0
1
Normal  
Maint  
Normal  
Maint  
Normal  
Maint  
Normal  
Maint  
233  
0
233  
0
233  
0
233  
0
1
*Callrate: 20  
*Interval: 60  
*Max_callrate:45  
*Next_hour: 70  
1
1
1
Normal  
Maint  
Normal  
233  
0
233  
tot_ts_req :0F24 0000 3CE2 ts_count :0010 0920 0200 Requests-TN748 TTRs :0014  
ts_denied :0E46 3CE2 0000 ts_total :0000 0090 0028 Requests-TN748 CPTRs:0041  
tot_fts_req:0000 53D2 2231 fts_count:02E0 0910 0784 Requests-TN744 CPTRs:0082  
fts_total:0320 0192 7048 Requests-TN744 TTRs :0082  
Requests-TN744 MFCs :0082  
Note: * Denotes Base 10, All Other Figures are in Base 16  
Field descriptions  
Time Slot  
Status  
4 numbers are associated with time slot status for each specified pnn;  
the two buses (0 and 1) have a maintenance and a normal state, and a  
number of idle counts. These fields represent real-time status data.  
Bus Status  
Two numbers are associated with the two buses for each pnn. Shown  
are the pnn number; the associated bus (0 or 1); and the bus’s state  
(avail or unavail). These fields represent real-time status data.  
Callrate  
The callrate field represents call rates currently executing on the  
switch. This is a counter that is bumped for each call attempt. This field  
represents real-time status data.  
Interval  
This field represents the interval applied to the call rate. It is normally a  
36 second time period. This field represents constant status data.  
Max_callrate  
This field represents the maximum call rate achieved since the last  
hour. If, at 20 minutes past 12:00, the system executes this command,  
the maximum call rate obtained during the past 20 minutes displays.  
This field represents real-time status data.  
Next_hour  
This field contains a value of 0 or 1 depending related to  
measurements taken this hour or the next. This hour reflects maximum  
call rates. When this flag is set, statistics accumulate for the next hour  
and shortly thereafter.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor system  
2
2-170  
tot_ts_req  
This field holds the total time slots in use during the time period elapsed  
since the top of the last hour. Data is internally collected every 100  
seconds. When the timer fires and the data collection occurs, a check  
is made as to how many time slots are currently in use. That’s where the  
total comes from. There are three numbers displayed for this field on  
the form; one for each of the pnns requested. This field represents  
real-time status data.  
ts_denied  
tot_fts_req  
ts_count  
This field records total time slots requests denied since the beginning  
of the last hour. Data is collected internally every 100 seconds. Three  
numbers display for this field; one for each requested pnn. This field  
represents real-time status data.  
This field represents the total number of requested fiber time slots. This  
field increments each time a fiber time slots is allocated since the last  
top of the hour measurement polling. Three values display; one for  
each requested pnn. This field represents real-time status data.  
The value in this field represents the requests for time slots during the  
last 100 second interim. An internal timer initiates polling every 100  
seconds. Three numbers display for this field on the form; one for each  
requested pnn. This field represents real-time status data.  
ts_total  
This field represents the total number of time slots requested since the  
top of the last hour. This field represents real-time status data.  
fts_count  
The value in this field represents the requests for fiber time slots during  
the last 100 second interim. An internal timer initiates polling every 100  
seconds. Three numbers display for this field; one for each requested  
pnn. This field represents real-time status data.  
fts_total  
This field indicates the total number of fiber time slots during the last  
100 second interim. This field represents real-time status data.  
Requests-TN74  
8 TTRs  
This field reflects the total number of requested touch tone receivers  
that are currently-active. It decrements when tone receivers are freed  
and increments when they are requested. This field applies strictly to  
the TN748 board. This field represents real-time status data.  
Requests-TN74  
8 CPTRs  
This field reflects the total number of requested call progress tone  
receivers that are currently active. It decrements when call progress  
tone receivers are freed and increments when they are requested. This  
field applies strictly to the TN748 board. This field represents real-time  
status data.  
Requests-TN74  
4 CPTRs  
This field reflects the total number of requested call progress tone  
receivers that are currently active. It decrements when call progress  
tone receivers are freed and increments when they are requested. This  
field applies strictly to the TN744 board. This field represents real-time  
status data.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor traffic  
2
2-171  
Requests-TN74  
4 TTRs  
This field reflects the total number of requested touch tone receivers  
that are currently active. It decrements when tone receivers are freed  
and increments when they are requested. This field applies strictly to  
the TN744 board. This field represents real-time status data.  
Requests-TN74  
4 MFC  
This field reflects the total number of requested multi-frequency  
receivers that are currently active. It decrements when multi-frequency  
receivers are freed and increments when they are requested. Note that  
this field applies strictly to the TN744 board. This field represents  
real-time status data.  
monitor traffic  
This command provides information on the number of trunk group and hunt  
group calls waiting to be serviced, and the time the oldest call in the group has  
been waiting for service.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
monitor traffic  
trunk-groups  
hunt-groups  
see below  
init  
inads  
craft  
none  
none  
cust  
rcust  
bcms  
browse  
Qualifier Description  
trunk-groups  
The number of trunk group calls waiting to be serviced, members in the  
group, and number of members that are active on calls in the group.  
This field displays up to 60 administered trunk groups. Technicians  
specify the starting trunk group. If technicians enter 5, the displayed  
trunks start at 5. Numbers 1-4 do not appear.  
hunt-groups  
This field displays the waiting time for oldest call in each hunt group.  
Screen data updates every minute; only changed fields refresh.  
Unadministered hunt groups have blank values.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor traffic  
2
2-172  
Output  
The following output example is a display of the monitor traffic hunt-groups  
command.  
monitor traffic hunt-groups  
HUNT GROUP STATUS  
22:49 SAT DEC 31 1988  
#
1
2
3
4
5
6
7
S
A
Q
W
LCIQ  
20  
#
S A  
Q
W LCIQ  
15 10 10 0  
17  
18  
19  
20  
21  
22  
23  
8
9
24 10  
25  
5
0
0
10  
10  
11  
12  
13  
14  
15  
16  
26  
27  
28  
29  
30  
31  
32  
(#: Group; S: Grp Size; A: Active Members; Q: Q Length; W: Calls Waiting)  
(LCIQ: Longest Call In Queue in seconds)  
Field descriptions  
#
Group number for trunk group or hunt group.  
S
Number of members administered for each trunk or hunt group.  
A
Number of group members that are active on a call. This does not include  
busied out members.  
Q
The length of queues administered for groups.  
W
Number of calls waiting in group queues to be serviced.  
LCIQ  
The longest call in queue (LCIQ) indicates the time in seconds the oldest call in  
the hunt group queue has been waiting to be serviced.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
monitor trunk  
2
2-173  
The following output example is a display of the monitor traffic trunk-groups  
command.  
monitor traffic trunk-groups  
TRUNK GROUP STATUS  
22:49 SAT DEC 311988  
# S A Q W # S A Q W # S A Q W # S A Q W  
1 15 10 0 0  
2 22 21 10 10  
9 31 12 20 0  
65 5 5 10 8  
99 12 0 0 0  
(#: Group; S: Grp Size; A: Active Members; Q: Q Length; W: Calls Waiting)  
monitor trunk  
This command displays internal software status information. This command  
helps to locate facilities to which the trunk is communicating. If a trunk group  
number is entered without a member number, and with or without “/”, it is member  
1. If a trunk group and member number are both entered, status for specified  
members displays.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
monitor trunk  
group  
1 – 99. If a group number is  
init  
1 (one)  
none  
entered without a member number,  
the member number defaults to 1.  
inads  
craft  
cust  
rcus  
bcms  
browse  
member  
1 – 99. If a member number is  
entered, the member status  
displays.  
Output  
The following example shows the output from the monitor trunk 78/1 command.  
monitor trunk 78/1  
TRUNK STATUS  
Service State: in-service/idle  
Trunk Group/Member: 078/001  
Port: 01C1505  
Signaling Group ID:  
Connected Ports:  
Maintenance Busy? no  
CA-TSC State:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
netstat ip-route  
2
2-174  
Field descriptions  
Trunk  
Group/Member  
Trunk group and group member number. (1-99/1-99).  
The port location (cabinet-carrier-slot-circuit) for trunks.  
Port  
Signaling Group  
ID  
If the trunk is ISDN, this field contains the number of the ISDN  
Signaling Group. Otherwise, this field is blank. ( )  
Connected Ports  
Service State  
Port locations (cabinet-carrier-slot-circuit) connected to the trunk.  
In-service/active, in-service/idle, out-of-service, out-of-service-NE  
(Near End), out-of-service-FE (Far End), maint-NE/active,  
maint-FE/active, maint-NE/idle, maint-FE/idle, pending-in-service,  
pending-maint, or disconnected. NE (Near End) and FE (Far End)  
refer to the “end” of the trunk that has placed the facility in its current  
state.  
Maintenance  
Busy  
This field identifies maintenance testing that occurs on the trunk.  
CA-TSC State  
The state of temporary signaling connections. (connection set up to  
pass call information over PRI signaling links).  
netstat ip-route  
This command displays the routing tables that are resident in the C-LAN circuit  
pack. With the “board” option, the command netstat ip-route board UUCss  
displays the routing tables that are resident on the specified C-LAN circuit pack.  
Feature  
Action/ Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
netstat ip-route  
board  
Example:  
init  
none  
none  
UUCss  
netstat ip-route board 01A03  
inads  
craft  
Output  
The following example shows the output from the netstat ip-route command.  
netstat ip-route  
page 1 of xxx  
IP ROUTING - C-LAN  
Gateway  
1:___.___.___.___ ___.___.___.___  
2:___.___.___.___ ___.___.___.___  
3:___.___.___.___ ___.___.___.___  
Destination  
C-LAN Bd/Pt  
Interface  
ppp13  
cmp0  
01C0514  
01C0517  
01C0518  
lo03  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
ping  
2
2-175  
Field descriptions  
Destination  
Fixed field giving the destination of the route. The destination is a  
name administered on the Node Name form which can include the  
keyword “Default,” indicating the default route.  
Gateway  
The node name of the Gateway by which the Destination can be  
reached. The Gateway must be a name administered on the  
Node Name form.  
C-LAN Board/Pt  
Interface  
The circuit pack location for the circuit pack that provides the  
interface for the route.  
■ pppnrepresents one of the PPP interfaces on the C-LAN,  
which is administered as port n+1.  
■ cpm0represents the ethernet interface on the C-LAN which is  
administered as port 17.  
■ lo0represents the loopback interface on the C-LAN which  
does not need to be administered.  
ping  
When debugging connectivity problems, a ping only indicates low-level  
connectivity. If an external ping works but higher-level applications such as DCS,  
CMS, or INTUITY do not, then you can only assume that there is connectivity to  
the board. Interrogate the switch for other clues as to why the higher-level  
application is not working.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
ping  
2
2-176  
Action/  
Object  
Feature  
Interactions  
1
Qualifier  
Qualifier Description  
Permissions  
Defaults  
ping  
ip-address  
The IP address of the device to  
ping in the following format:  
www.xxx.yyy.zzz  
init  
inads  
craft  
packet  
length =  
64 bytes  
customer  
node-name  
board  
Administered node name (use  
display node-names)  
The location of the C-LAN circuit  
pack (UUCSS)  
packet-  
length  
Range: 64-1,500 bytes  
repeat  
1-100  
Examples:  
ping ip-address 192.68.3.26  
ping ip-address 192.68.3.26  
board 1C05  
ping ip address 168.24.3.66  
packet-length 1500  
1
You can place additional restrictions on the command by selecting the object “ip-address” on the Restricted  
Object List:  
Typ e change permissions loginid (an administered login such as inads), and press Enter.  
Set the Additional Restrictionsfield to y in the Administration Commands section of the form.  
Go to the second or third page of the form.  
Enter ip-address in the list of Restricted Objects and press Enter.  
The ping command has 4 qualifiers:  
■
■
■
■
‘‘ping ip-address’’  
‘‘ping node-name’’  
‘‘ping board’’  
‘‘ping packet-length’’  
ping ip-address  
This command “pings” the given IP address of the destination to ping. The  
command returns  
■
■
■
■
the port used to perform the test  
the pass/fail results of the test  
the round-trip delay time for successful tests  
the error code on tests that failed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
ping  
2
2-177  
ping node-name  
This command pings an administered node. Look the “node-name” up with the  
display node-names command).  
ping board  
The board qualifier specifies which C-LAN circuit pack from which to ping. By  
adding the board UUCSS qualifier to the command, you can also specify which  
C-LAN circuit pack (in the case of multiple C-LAN circuit packs). If only one  
C-LAN circuit pack is present, the board qualifier is optional.  
ping packet-length  
The packet-length qualifier specifies the packet length of the ping packet.  
Packet lengths of from 64 to 1500 bytes can be specified. The packet-length  
qualifier is optional, and if not used, the default packet length is 64 bytes.  
Specifying a longer packet length in the command line can show  
■
if a router or host has a problem fragmenting or reassembling transferred  
packets  
■
a more complete indication of the link status  
If the packet length is not specified, the default is 64 bytes. You can add the  
packet-length qualifier and the packet size (64-1500 bytes) to the other ping  
commands. Some examples include:  
■
■
■
ping node-name packet-length 800  
ping ip-address 24.103.5.7 packet-length 100  
ping board UUCSS packet-length 1000  
Output  
The following example shows the output from the ping ip-address  
packet-length command.  
ping ip-address 192.68.3.26 packet-length 1500  
TEST RESULTS  
End-pt IP  
192.68.3.26  
Port  
01C0202  
Port Type Result  
PPP-PT PASS  
Time(ms) Error Code  
221 XXXX  
Screen 2-7. ping ip-address report  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
ping  
2
2-178  
Field descriptions  
End-pt IP  
Port  
The TCP/IP destination address of the ping command.  
Location of the C-LAN circuit pack (UUCSS).  
Port Type  
Can be either PPP-PTfor PPP ports (ports 1-16) or ETH-PTfor  
the Ethernet port (port 17).  
Result  
PASS or FAIL  
Time (ms)  
Error Code  
The round-trip time (in milliseconds) of the ping.  
Identifies problems associated with the circuitry in the data path  
for a peer-to-peer IP layer connection  
Error messages  
The system returns error messages listed in Table 2-2.  
Table 2-2. Ping command error messages  
Message  
Interpretation  
www.xxx.yyy.zzz Internet  
address not assigned  
The system cannot find the IP address.  
Internet address not  
The IP address is not in the route table of  
reachable from this board the specified board.  
More than one default  
route exists, specify  
board  
The IP address is not in the route table,  
and more than 1 C-LAN circuit pack has  
a default route.  
Invalid internet address  
Invalid Internet address parameter  
“CCcss” is an invalid  
identifier; please press  
HELP  
Invalid board location (when using the  
“board” option).  
Error encountered, could  
not complete request  
The internal error of not being able to find  
the port through which the IP address is  
reached.  
Out of range  
The packet size is greater than 1500 or  
less than 64 bytes in length or if there are  
invalid or unrecognized parameters  
WARNING Default packet  
length of 64 bytes used  
for TN799  
Indicates that the default packet length of  
64 bytes is used for a TN799 board  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
recycle carrier  
2
2-179  
recycle carrier  
This command recycles power for specified carriers. When power units are  
replaced in carriers, this command recycles that carrier’s power. No Compact  
Modular Cabinet (CMC) can be recycled.  
release access-endpoint  
This command removes all ports associated with the specified access endpoint  
from a maintenance busy state. Periodic and scheduled tests subsequently  
resume on the released ports. Maintenance completes background initialization  
testing on the released ports. For details of the test sequence, refer to [3].  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release  
access-endpoint  
extension  
number associated with  
desired access endpoint.  
init  
none  
none  
inads  
craft  
nms  
Output  
The following example shows the output from the release access-endpoint  
22502 command and assume that the access endpoint ports for extension 22502  
are in cabinet 1, carrier C, slot 11, circuit 1 to 6.  
release access-endpoint 22502  
COMMAND RESULTS  
Port Maintenance Name Alt. Name Result  
page 1 of 1  
Error Code  
01C1101 WAE-PORT  
01C1102 WAE-PORT  
01C1103 WAE-PORT  
01C1104 WAE-PORT  
01C1105 WAE-PORT  
01C1106 WAE-PORT  
22502  
22502  
22502  
22502  
22502  
22502  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
Command Successfully Completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release board  
2
2-180  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit) of released maintenance.  
Maintenance Name  
The type of released maintenance object. (wideband access point  
=WAE-PORT, single port access endpoint = TIE-DS1.  
Alt. Name  
Alternate way to identify maintenance objects. This field contains  
the extension number of the access endpoint.  
Result  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
release board  
This command activates administered maintenance objects on the circuit pack at  
specified locations.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release board  
location  
Board location: PCSS  
init  
none  
none  
inads  
craft  
nms  
Output  
The following output example is a display of the release board 1c07 command  
and assumes that the board in cabinet 1, carrier c, slot 7 is an analog board with  
three administered ports.  
release board 01C07  
COMMAND RESULTS  
Port  
Maintenance Name Alt. Name Result Error Code  
01C07  
ANL-BD  
PASS  
PASS  
PASS  
PASS  
01C0702  
01C0701  
01C0703  
ANL-LINE  
ANL-LINE  
ANL-LINE  
51001  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot) of released maintenance object.  
Maintenance Name  
TheDotywpnleoaodffrmomaWinwtewn.Saonmcaneuoalbs.jceocmt. AthllaMtainsuablseSinegarcrheAlenadsDeodwn.load.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release cdr-link  
2
2-181  
Alt. Name  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Result  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
release cdr-link  
This command removes maintenance objects associated with specified call  
detail recording (cdr)-links from a maintenance busy state. These links provide  
asynchronous data connections from switches to peripherals; they are  
composed of a:  
■
■
■
■
Far end data module  
Simulated data channel on a PKTINT board  
Manager that initiates and maintains the link  
Controller/protocol that services the link  
For information on what a CDR link is and does, see the description of the ‘‘status  
cdr-link’’ command.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
primary  
Permissions  
Defaults  
Interactions  
release  
cdr-link  
link-id  
init  
inads  
craft  
none  
none  
secondary  
Output  
The following example shows the output from the release cdr-link primary  
command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release data-module  
2
2-182  
release cdr-link primary  
COMMAND RESULTS  
Port Maintenance Name Alt. Name Result  
Error Code  
PRI-CDR  
PASS  
Command successfully completed  
Field descriptions  
Port  
Not applicable. ( )  
Maintenance Name  
Type of released maintenance object. (primary cdr-link =  
PRI-CDR, secondary cdr-link = SEC-CDR)  
Alt. Name  
Result  
Not applicable. ( )  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
release data-module  
This command activates the specified data module (or data channel). Hardware  
tests are executed to verify that the equipment is functioning.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release  
data-module  
extension  
Extension number associated  
with desired data module or data  
channel.  
init  
none  
none  
inads  
craft  
cust  
nms  
Output  
The following example shows the output from the release data-module 300  
command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release journal-printer  
2
2-183  
release data-module 310  
COMMAND RESULTS  
Port  
01C1103  
Maintenance Name Alt. Name  
DIG-LINE  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit) of the maintenance object  
that is busied out or released, or the number of the data channel.  
Maintenance Name  
Alt. Name  
The type of maintenance object that is being busied out or  
released.  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Result  
Test result: Pass, Abort, Fail  
Error Code  
System-generated description of a command failure.  
release journal-printer  
This command activates maintenance objects associated with a specified  
pms-log or wakeup-log link. Hardware tests are executed to verify that the  
equipment is functioning. For general information on journal printer links, see the  
description of the ‘‘busyout pms-link’’ command. For information on journal  
printers, see the description of the ‘‘status journal-link’’ command.  
Feature  
Action/Object  
Qualifier  
pms-log  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release  
journal-printer  
releases links to pms printers.  
(1)  
init  
none  
see below  
inads  
craft  
nms  
wakeup-log  
Releases links to wakeup  
logging facilities. (0)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release journal-printer  
2
2-184  
Feature Interactions  
Specific component maintenance performed on a link sometimes conflicts with  
link maintenance, itself (busied out objects create link setup failure). Frequent  
link re-setup attempts may delay faulty component recovery. For best results,  
technicians should use busyout to disable attempted link re-setup.  
Output  
The following example shows the output from the release journal-printer  
wakeup-log command.  
release journal-printer wakeup-log  
COMMAND RESULTS  
Port  
0
Maintenance Name  
JRNL-LINK  
Alt. Name  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit) of busied out or  
released maintenance object. (wakeup log = 0; pms log = 1)  
Maintenance Name  
Alt. Name  
Type of busied out or released maintenance object.  
Not applicable.  
Result  
Test result: Pass, Abort, or Fail.  
Error Code  
System-generated description of a command failure.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release link  
2
2-185  
release link  
This command activates MOs associated with a specified link. Hardware tests  
verify that equipment is functioning properly.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release link  
link-id  
Number associated with each link  
init  
none  
none  
(1–8).  
inads  
craft  
1through 4 reside on Processor  
Interface circuit packs “1a1” or  
“1b1”  
5 through 8 reside on Processor  
Interface circuit pack “1a2” or  
“1b2.”  
Output  
The following example shows the output from the release link 1 command.  
release link 1  
COMMAND RESULTS  
Port  
Maintenance Name Alt. Name Result Error Code  
01C0301  
PI-LINK  
PASS  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit) of the busied out or  
released maintenance object. Port address represents the link-id.  
Maintenance Name  
Alt. Name  
The type of maintenance object that is being released.  
Not applicable.  
Result  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release mis  
2
2-186  
release mis  
This command activates management information systems. Hardware tests are  
executed to verify that equipment is functioning properly.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release mis  
init  
none  
none  
inads  
craft  
cust  
rcust  
Output  
The following example shows the output from the release mis command.  
release mis  
COMMAND RESULTS  
Alt. Name  
Port  
Maintenance Name  
MIS  
Result  
PASS  
Error Code  
Command Successfully Completed  
Field descriptions  
Port  
Not applicable.  
Maintenance  
Name  
MIS  
Alt. Name  
Not applicable.  
Result  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release modem-pool  
2
2-187  
release modem-pool  
This command deactivates specified modem pool groups or group members.  
Specifying group numbers, member numbers releases single group members.  
Specifying modem pool group numbers releases members in a modem pool  
group.  
Feature  
Action/Object  
Qualifier  
group  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release  
1-5.  
init  
none  
none  
modem-pool  
inads  
craft  
member  
pair of analog and digital line ports  
(or two pair for the Integrated  
modem-pool case). 1-32.  
Output  
The following example shows the output from the release modem-pool 1  
command.  
release modem-pool 1  
SPE B  
COMMAND RESULTS  
Port  
Maintenance Name  
Alt. Name Result  
Error Code  
01C0701  
01C0703  
MODEM-PT  
MODEM-PT  
PASS  
PASS  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit) of busied out  
maintenance object.  
Maintenance Name  
Alt. Name  
MODEM-PT.  
This field is not applicable to this command.  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Result  
Error Code  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release pms-link  
2
2-188  
release pms-link  
This command deactivates MOs that are associated with a property  
management system link. These links provide asynchronous data connections  
from switches to peripherals; they are composed of a:  
■
■
■
■
Far end data module  
Simulated data channel on a NETCON board  
Manager that initiates and maintains the link  
Controller/protocol that services the link  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release  
init  
none  
see below  
pms-link  
inads  
craft  
Feature Interactions  
Specific component maintenance performed on a link sometimes conflicts with  
link maintenance, itself (busied out objects create link setup failure). Frequent  
link re-setup attempts may delay faulty component recovery. For best results,  
technicians should use busyout to disable attempted link re-setup.  
Output  
The following example shows the output from the release pms-link command.  
release pms-link  
COMMAND RESULTS  
Alt. Name  
Port  
Maintenance Name  
PMS-LINK  
Result  
PASS  
Error Code  
Command Successfully Completed  
Field descriptions  
Port  
This field is left blank.  
Maintenance Name  
Alt. Name  
PMS-LINK  
Not applicable.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release port  
2
2-189  
Result  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
release port  
This command deactivates specified ports on circuit packs.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release port  
location  
Physical location of the port: PCSS  
init  
none  
none  
inads  
craft  
Output  
The following example shows the output from the release port 1c0701 command  
and assumes that the port in cabinet 1, carrier c, slot 7, circuit 1 is an analog  
port.  
release port 01C0701  
COMMAND RESULTS  
Alt. Name  
Port  
01C0701  
Maintenance Name  
ANL-LINE  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
The type of maintenance object that is being released.  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
Maintenance Name  
Alt. Name  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Result  
Success status of a busied out object (PASS, ABORT, FAIL)  
Error Code  
System-generated description of a command failure.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release pri-endpoint  
2
2-190  
release pri-endpoint  
This command removes PRI endpoint ports (B-channels) associated with  
specified PRI endpoint from maintenance busy states. Periodic and scheduled  
tests resume on released ports. The switch attempts to negotiate with the far-end  
PRI terminal adapter activating PRI endpoint port (B-channel). Maintenance  
does background initialization testing on released ports. For details of the test  
sequence, refer to [3].  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release  
pri-endpoint  
extension  
extension number associated with  
desired PRI endpoint.  
init  
none  
none  
inads  
craft  
nms  
Output  
The following example shows the output from the release pri-endpoint 22501  
command and assumes that the PRI endpoint ports for extension 22501 are in  
cabinet 1, carrier B, slot 20, circuit 1 to 6.  
release pri-endpoint 22501  
page 1 of 1  
COMMAND RESULTS  
Maintenance Name Alt. Name Result  
Port  
Error Code  
01B2001  
01B2002  
01B2003  
01B2004  
01B2005  
01B2006  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
22501  
22501  
22501  
22501  
22501  
22501  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit) of released maintenance object.  
PE-BCHL.  
Maintenance Name  
Alt. Name  
Result  
Alternate way to identify maintenance objects. (PRI endpoint extension)  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release sp-link  
2
2-191  
release sp-link  
This command reactivates busied out system printer links and resolves active  
alarms for system printer links. The system printer link is a link from the switch to  
an external printer. Adminstering system printer extensions to call system printers  
creates the links.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release sp-link  
init  
none  
none  
inads  
craft  
Output  
The following example shows the output from the release sp-link command.  
release sp-link  
SPE A  
COMMAND RESULTS  
Port  
Maintenance Name  
SYS-PRNT  
Alt. Name  
Result  
PASS  
Error Code  
Command Successfully Completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit) of busied out  
maintenance objects. ( )  
Maintenance Name  
Alt. Name  
The type of maintenance object that is being busied out.  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Result  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release station  
2
2-192  
release station  
This command removes specified administered voice terminal extensions from a  
maintenance busy state.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release station  
extension  
Extension number (see dial-plan)  
init  
none  
none  
inads  
craft  
cust  
Output  
The following example shows the output from the release station 1002  
command.  
release station 1002  
COMMAND RESULTS  
Port  
01C1102  
Maintenance Name  
DIG-LINE  
Alt. Name  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit) of the released  
maintenance object.  
Maintenance Name  
Alt. Name  
Type of released maintenance object.  
Alternate way to identify maintenance objects. This field contains  
an extension when the object is a station.  
Result  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release tdm  
2
2-193  
release tdm  
This command removes specified tdm buses from a maintenance busy state.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release tdm  
port-net  
work pn  
number  
Port network number of the TDM  
bus  
init  
inads  
craft  
none  
see below  
bus bus  
(“a” or “b”) specifies desired half of  
the TDM bus. Each 512 time slot  
TDM bus is configured as two  
duplicate 256 time slot buses. This  
division allows for duplication of  
control channels and dedicated  
tone time slots. The default control  
bus (carrying the control channel)  
is the “a” bus, while the default  
tone bus (carrying dedicated  
tones) is the “b” bus. (1 - 3)  
Feature Interactions  
■
The system tears down busied out buses. No new calls can be  
administered on busied out buses.  
■
To prevent busyouts of particular buses, technicians should move  
dedicated tone time slots to another bus (the other half of the duplicated  
bus).  
Output  
The following example shows the output from the release tdm port-network 1  
bus a command.  
release tdm port-network 1 bus a  
COMMAND RESULTS  
Alt. Name  
Port  
Maintenance Name  
TDM-BUS  
Result  
PASS  
Error Code  
PN 01A  
Command successfully completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release tone-clock  
2
2-194  
Field descriptions  
Port  
Port network number (preceded by “PN”) and bus (“A” or “B”)  
associated with the TDM bus.  
Maintenance Name  
Alt. Name  
TDM-BUS  
Not applicable  
Result  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
release tone-clock  
This command removes specified tone/clocks from maintenance busy states.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release  
location  
Physical location of the tone/clock:  
init  
1 (one)  
none  
tone-clock  
PC  
inads  
craft  
Output  
The following example shows the output from the release tone-clock 1a  
command.  
release tone-clock 1a  
COMMAND RESULTS  
Alt. Name Result  
Port  
01A  
01A  
01A  
Maintenance Name  
TONE-PT  
Error Code  
PASS  
PASS  
PASS  
TDM-CLK  
TONE-BD  
Command successfully completed  
Field descriptions  
Port  
The tone clock circuit pack maintenance object displays the  
cabinet and carrier of the specified tone/clock board.  
Maintenance Name  
Alt. Name  
TONE-PT, TDM-CLK and TONE-BD  
Not applicable.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
release trunk  
2
2-195  
Result  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
release trunk  
This command removes specified trunk groups or trunk group members from a  
maintenance busy state. Specifying the group number releases a single group  
member and the member number; specifying the trunk group number releases  
members in a trunk group.  
Feature  
Action/Object  
Qualifier  
group  
Qualifier Description  
Permissions  
Defaults  
Interactions  
release trunk  
1–99.  
1–99  
init  
inads  
craft  
none  
none  
member  
Output  
The following example shows the output from the release trunk 78/1 command.  
release trunk 78/1  
COMMAND RESULTS  
Port  
01C1505  
Maintenance Name  
CO_TRK  
Alt. Name  
78/01  
Result  
PASS  
Error Code  
Command successfully completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit) of the released  
maintenance object.  
Maintenance Name  
Alt. Name  
The type of maintenance object that is being released.  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
reset board  
2
2-196  
Result  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Error Code  
reset board  
This command performs a soft reset of every specified, administered port on the  
port circuit pack. Ports must be busied out before the port circuit pack resets.  
!
WARNING:  
This command is service disrupting and may cause extraneous alarms.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
reset board  
location  
Physical location of board:  
init  
carrier = 1  
none  
PCSS  
inads  
craft  
nms  
repeat  
number = 1  
repeat  
number  
Number of times command  
repeats (1– 99)  
Output  
The following example shows the output from the reset board 1c07 command  
and assumes that the board in port network 1, carrier c, slot 7 is an analog board  
with three administered ports.  
reset board 1C07  
TEST RESULTS  
Port  
01C07  
Maintenance Name  
ANL-BD  
Alt. Name Test No. Result  
Error Code  
53  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot) of the reset maintenance object.  
Type of reset maintenance object.  
Maintenance Name  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
reset io-processor  
2
2-197  
Alt. Name  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group number)  
Success status of a busied out object (PASS, ABORT, FAIL)  
System-generated description of a command failure.  
Result  
Error Code  
reset io-processor  
This command resets and initializes the IO-Processor hardware and firmware.  
The IO-Processor supports the packet interface and Data Channel data  
scanners. The IO-Processor is simply reset. Failure of the reset can lead to the  
processor being placed in the out-of-service state.  
!
CAUTION:  
Resetting the IO-Processor (which also resets the packet interface and  
Data Channel data scanner) is disruptive. ISDN call service throughout the  
system is disrupted, and some data may be lost on Data Channel  
communications during the reset interval.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
reset  
none  
none  
init  
none  
io-processor  
inads  
craft  
nms  
reset interface  
This command resets the Processor Interface circuit pack, reads its associated  
software from tape, restarts applications processes, re-establishes permanent  
switched calls, and sets up each enabled link. If the interface cannot be  
established, a Major alarm raises on the interface and all enabled links  
deactivate. When the Message Server Adjunct (MSA), Distributed  
Communications System (DCS), Audio Information Exchange (AUDIX), or Call  
Management System (CMS) are initially administered, links for these applications  
and submitting the form restarts the interface. Before Processor Interface circuit  
packs are replaced, technicians must power down the switch and restart it.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
reset packet-interface  
2
2-198  
For troubleshooting, see ‘‘status interface’’, ‘‘status link n’’, and ‘‘status  
processor-channel’’ commands to locate problems before performing a reset  
interface (link traffic is interrupted).  
!
WARNING:  
The interface command interrupts operation of the AP, DCS, AUDIX, CMSor  
ISDN-PRI.  
Feature  
Action/Object  
reset interface  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
location  
(cabinet-carrier-position) of the  
processor interface (PI board). The  
position determines cleared  
init  
inads  
craft  
none  
none  
processor interface circuit pack.  
first processor interface = 1  
second processor interface = 2  
reset packet-interface  
The IO-Processor controls the one and only Packet-Interface. To reset the  
Packet-Interface for R6csi, use the reset io-processor command. Because this  
command is not used in this software release, the following error message  
displays on the status line:  
Command unavailable; use ‘reset io-processor’  
reset switch-control  
This command resets and initializes the switch control hardware and firmware.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
reset  
none  
none  
init  
none  
switch-control  
inads  
craft  
nms  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
reset system  
2
2-199  
reset system  
This command resets the system beginning with the corresponding vector bit  
set, a core dump is written to memory card, only if the memory card is the special  
core dump card), the vector is cleared, and the requested restart is performed.  
NOTE:  
All successful reset system commands log users off.  
Feature  
Interactions  
1
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
reset system  
level  
1 = Warm Restart  
2 = Cold 2  
3 = Cold1  
init  
inads  
craft  
none  
see below  
4 = Reboot  
1
Descriptions of all reset levels are in the ‘‘Initialization and Recovery’’ section of Chapter 1,  
‘‘Maintenance for csi systems’’.  
Feature Interactions  
■
■
The reset command invokes system initialization like low-level  
maintenance. Software never escalates requested reset levels;  
technicians determine the levels.  
Two hardware switches are associated with active SPEs. These hardware  
switches override demand maintenance activities requested by system  
technicians.  
reset translation-id  
This command resets the translation-ID on the translation card(s) to match the  
processor(s), saves translations to the memory card, and restores use of the add,  
change, remove, and duplicate commands.  
NOTE:  
This command can be executed only by Lucent Services.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
reset  
translation-id  
Example:  
reset translation-id  
Lucent  
Services  
only  
See ‘‘Error  
message’’  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
restore announcements  
2
2-200  
Error message  
In duplicated systems, the message,  
Cannot reset translation-ID without standby SPE being  
accessible  
means that both processors must be sane and operational.  
■
A standby SPE that has been busied out must be released (release  
standby-spe).  
■
Check that the SPE-select switches on the DUPINT circuit pack are in the  
AUTO position.  
restore announcements  
This command copies announcement data from the active MSS devices to  
announcement boards.  
Feature  
Action/ Object  
Qualifier  
print  
Qualifier Description  
Permissions  
Defaults  
Interactions  
restore  
Report sent to printer  
init  
Tape-based:  
see below  
announcements  
inads  
craft  
cust  
rcust  
announcement  
copies from active  
processor’s tape to  
the announcement  
board.  
schedule  
Command is validated  
and then a scheduling  
form displays to  
schedule execution of  
the command. The  
command is then  
Card-mem based:  
Announcement  
data copies from  
active processor’s  
to the  
placed in the  
command queue and  
is executed at the  
specified time. The  
information displayed  
by the command is  
sent to the system  
printer instead of the  
announcement  
board.  
1
screen.  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Feature Interactions  
!
WARNING:  
Manager I is blocked for other activities until the command completes (up  
to 45 minutes).  
■
If no announcement data module and no NETCON data module are  
administered, the system denies the command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
restore announcements  
2
2-201  
■
If the announcement data module port is out of service or active (for  
example, performing an announcement playback), the system denies the  
command.  
■
■
If users are in integrated announcements sessions, the system denies the  
command.  
If the board is currently uploading or downloading, the system denies the  
command. Users cannot save or restore announcement after the restore  
announcements command commences.  
■
■
■
■
If no tape is in the tape drive when users attempt a copy, the command  
aborts.  
If the MSS is in use by another user or maintenance, the restore  
announcements command is not allowed.  
Unsaved or corrupted announcement files on the MSS, disallow the  
restore announcements command.  
To prepare for a failure, users should copy announcement files to  
announcement boards. If errors result from hardware or firmware failures,  
MSS software logs hardware errors with maintenance. When errors occur,  
the system continually attempts to download boards in 10-minute intervals  
until a download succeeds, announcements record, or downloads initiate  
from the SAT. Then, error messages display indicating corrective action. If  
errors result from hardware or firmware failure, MSS software logs a  
hardware error with maintenance. Maintenance software invokes tests to  
diagnose and attempt to correct the problem. If maintenance software fails  
to correct problems, alarms raise indicating additional corrective action.  
■
When the system crashes and/or a spontaneous processor interchange  
occurs, the restore operation fails. Valid announcement files do not appear  
on the announcement board. To copy the announcements from the active  
processor’s MSS device to the announcement board, restart the command  
on the newly- active processor. When announcements completely copy to  
announcement boards, calls do not connect to announcements on the  
ANN board.  
■
When announcement boards are plugged in or reset, maintenance  
performs a series of tests, including a DRAM Checksum test. Tests fail due  
to power losses to boards, resulting in an automatic download of  
announcement files.  
Output  
The following example shows the output from the restore announcements  
command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
resume hardware-group  
2
2-202  
restore announcements  
Page 1 of 1 SPE A  
RESTORE ANNOUNCEMENTS  
Processor Command Completion Status  
SPE-A Success  
Error Code  
0
Field descriptions  
Processor  
Displays the processor that houses the MSS device used to  
copy announcement data.  
Command Completion  
Status  
Specifies successful completion of the command.  
Error Code  
System-generated description of a command failure.  
resume hardware-group  
This command resumes the previous test hardware-group command its  
canceled position. Entering another test hardware-group disables the resume  
hardware-group command.  
A canceled test hardware-group command appears as canceledon the  
status hardware-group screen. A resumed test hardware-group command  
appears as activeon the status hardware-group screen.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
resume  
none  
init  
none  
none  
hardware-group  
inads  
Feature Interactions  
■
Cancelling a test hardware-group command deactivates the test  
command. The status hardware-group screen displays the state as  
canceled.  
■
When the resume hardware-group command is entered to resume a  
previously-canceled test hardware-group command, the state of the test  
command will be changed to activeon the status hardware-group  
screen.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
save announcements  
2
2-203  
save announcements  
This command copies announcement data from the announcement board to the  
MSS. The Card-Mem stores announcements for the system. By default,  
announcement data writes to the MSS device in a simplex processor (SPE)  
system.  
If there integrated announcement boards exist, this command is allowed. The  
system denies the save announcement command if no announcement data  
modules and no NETCON data modules are administered.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
save  
announcements  
spe-active  
Forces the system to write  
announcement data to  
specified devices.  
init  
none  
See below  
inads  
craft  
cust  
rcust  
Feature Interactions  
!
WARNING:  
Manager I is blocked for other activities until the command completes. (up  
to 45 minutes).  
■
■
If no announcement data module is administered, the system denies the  
command.  
If the announcement data module port is out of service or active  
(performing an announcement playback), the system denies the  
command.  
■
■
If no announcements are on the board or a user is in an integrated  
announcements session, the system denies the command.  
If the board is currently uploading or downloading, the system denies the  
command. Users cannot record integrated announcements after the save  
announcements command commences even though 15 channels are  
available for announcement playback (one is reserved for uploading and  
downloading).  
■
The save announcements command will not be allowed if the Mass  
Storage System (MSS) is in use. The MSS may be in use by either another  
user or by maintenance.  
■
■
The standby processor must be in service with shadowing enabled, so  
that the system can save announcements to the standby processor.  
In case of a failure, technicians make announcement files consistent  
across both MSS devices. Files become inconsistent due to hardware  
failures or spontaneous processor interchanges. If announcement files are  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
save translation  
2
2-204  
inconsistent due to hardware failures that occur during the save  
announcements command, error messages display indicating corrective  
action. Maintenance software that monitors hardware logs hardware errors  
to maintenance. Then, maintenance software invokes tests to diagnose  
and attempt corrective action. If maintenance software fails to correct the  
problem, an alarm raises displaying corrective action.  
■
■
The save announcements command writes two time-stamped, identical  
copies of announcement data to selected devices. The time-stamp for  
both copies is the same. Each copy contains a timestamp and the state of  
the copy. (good or bad)  
If good copies of announcement files are not available, the restore  
announcements command cannot execute until the save  
announcements command completes. Announcements on the board are  
still usable.  
Output  
The following example shows the output from the save announcements  
command.  
save announcements  
Page 1 of 1 SPE A  
SAVE ANNOUNCEMENTS  
Processor Command Completion Status  
SPE-A Success  
Error Code  
0
Field descriptions  
Processor  
Displays processors when announcement data writes  
to its devices. (SPE-A and SPE-B)  
Command Completion Status  
Error Code  
Whether the command succeeded or aborted.  
0 = save was successful  
1 = unable to save to the active spe device  
2 = unable to save to the standby spe device  
save translation  
All translation data is kept in memory during system operation, and if the switch  
goes down, the system loses all data. This command allows users to save the  
in-memory translation data to the memory card. This command runs as part of  
scheduled maintenance and/or on demand by the technician.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
set options  
2
2-205  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
save  
translations  
spe-active  
Translations saved on the  
active processor’s MSS  
device.  
init  
none  
If translation  
data changes  
due to  
administrative  
commands,  
save  
inads  
craft  
cust  
translation  
cannot be  
performed.  
Output  
The following example shows the output from the save translation command.  
Error Codes are as follows:  
■
■
■
0 - save successful  
1 - could not write to the active device  
2 - could not write to the standby device  
save translation  
SAVE TRANSLATION  
Processor  
SPE-A  
Command Completion Status  
Success  
Error Code  
0
Command Successfully Completed  
Field descriptions  
Processor  
Identifies the processor carrier where translation data is  
saved. (SPE-A)  
Command  
Completion Status  
Displays a variety of messages, identifying the success  
or failure of the command.  
set options  
This command enables a remote user with INADS permission to select which  
types of maintenance categories report alarms automatically and which types  
require customer call-in. Judicious use of this command can reduce the number  
of ineffective alarms to the TSC. For effective results, technicians should use the  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
set options  
2
2-206  
set options command default settings specified in this section. Technicians  
should not change these settings. Special circumstances (for example, special  
studies) may require temporary changes under the guidance of Tiers 3 and 4.  
NOTE:  
Alarms do not upgrade.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
set options  
none  
init  
see  
none  
inads  
below  
Form Input  
The following example is a display of the set options command.  
set options  
Page 1 of 8  
ALARM REPORTING OPTIONS  
Major Minor  
On-board Station Alarms: w  
Off-board Station Alarms: w  
w
w
y
w
w
w
w
w
w
w
w
w
w
w
w
y
On-board Trunk Alarms (Alarm Group 1): y  
Off-board Trunk Alarms (Alarm Group 1): w  
On-board Trunk Alarms (Alarm Group 2): w  
Off-board Trunk Alarms (Alarm Group 2): w  
On-board Trunk Alarms (Alarm Group 3): w  
Off-board Trunk Alarms (Alarm Group 3): w  
On-board Trunk Alarms (Alarm Group 4): w  
Off-board Trunk Alarms (Alarm Group 4): w  
On-boar Adjunct Alarms: w  
Off-board Alarms: w  
Off-board DS1 Alarms: w  
Off-board PI-LINK Alarms: w  
Off-board Alarms (Other): w  
Memory Card Capacity Alarms:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
set options  
2
2-207  
set options  
Page 2 of 8  
TRUNK GROUP ALARM OPTIONS  
(Alarm Group)  
01: 1 11: 1 21: 1 31: 1 41: 1 51: 1 61: 1 71: 1 81: 1 91: 1  
02: 1 12: 1 22: 1 32: 1 42: 1 52: 1 62: 1 72: 1 82: 1 92: 1  
03: 1 13: 1 23: 1 33: 1 43: 1 53: 1 63: 1 73: 1 83: 1 93: 1  
04: 1 14: 1 24: 1 34: 1 44: 1 54: 1 64: 1 74: 1 84: 1 94: 1  
05: 1 15: 1 25: 1 35: 1 45: 1 55: 1 65: 1 75: 1 85: 1 95: 1  
06: 1 16: 1 26: 1 36: 1 46: 1 56: 1 66: 1 76: 1 86: 1 96: 1  
07: 1 17: 1 27: 1 37: 1 47: 1 57: 1 67: 1 77: 1 87: 1 97: 1  
08: 1 18: 1 28: 1 38: 1 48: 1 58: 1 68: 1 78: 1 88: 1 98: 1  
09: 1 19: 1 29: 1 39: 1 49: 1 59: 1 69: 1 79: 1 89: 1 99: 1  
10: 1 20: 1 30: 1 40: 1 50: 1 60: 1 70: 1 80: 1 90: 1  
NOTE:  
Remaining Trunk Group information displays on pages 3-8, and is not  
documented in this Manual.  
The first page of the Alarm Reporting Options Form, provides the following alarm  
options: the four trunk alarm severity groups, the adjunct alarms, off-board DS1  
alarms, and PI-LINK alarms, memory card translation capacity alarms, and other  
off-board alarms. The second page, known as the Alarm Reporting Options  
Form, provides alarm severity groups to each trunk group.  
The following alarm options are available:  
■
Minor: Maintenance testing discovers raised alarms, downgrades them to  
minor alarms, and deactivates alarmed resources. LEDs on the port board  
and maintenance board follow standard minor alarm LED protocol and  
call receiving OSSs.  
■
Warning: Maintenance testing discovers raised alarms, downgrades them  
to warnings and deactivates alarmed resources. The Alarm Log pinpoints  
customer-reported trunk or station problems. Alarm LEDs light on the port  
circuit pack and Maintenance circuit pack as before, but no attendant  
LEDs or stations reporting alarms are affected. No call is placed to INADS.  
■
Report: The report option treats alarms the same as warnings with one  
exception: alarms report to INADS with a special WARNING category.  
When this type of alarm is received, INADS logs the occurrence and  
creates a trouble ticket or closes it immediately. Retry strategy for this type  
of call is similar to normal Major or Minor alarm reports. However, the  
acknowledgment LED on the attendant console or alarm reporting station  
does not reflect the status of the call.  
■
Yes: Alarms raise normally without filtering alarm data.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
set options  
2
2-208  
■
No: Alarms that raise on trunks, stations, or adjuncts in this category drop.  
Error information displays as before, but alarm is evident. LED is inactive  
and calls are not sent to INADS. Because resources are deactivated  
without any record, this option is recommended only when other options  
do not provide desired results.  
Technicians can administer alarm options on a system-wide basis for the  
following categories:  
■
■
■
■
Major on-board station alarms  
Minor on-board station alarms  
Major off-board station alarms  
Minor off-board station alarms  
Trunk alarms have four alarm severity groups with administrable alarm options in  
the categories listed below. For G1, technicians can administer alarm options on  
a system-wide basis for the following categories:  
■
■
■
■
Major on-board trunk alarms  
Minor on-board trunk alarms  
Major off-board trunk alarms  
Minor off-board trunk alarms  
Technicians assign alarm severity options to the following Adjunct categories:  
■
■
■
■
Major on-board adjunct alarms  
Major off-board adjunct alarms  
Minor on-board adjunct alarms  
Minor of-board adjunct alarms  
Technicians can administer options for Minor off-board DS1 Interface circuit pack  
alarms and Minor off-board Memory Card Capacity Alarms on a system-wide  
basis.  
The system inspects alarm reporting options information in the Alarm Reporting  
Options Form as translation data and preserves it through all restart levels.  
This command affects the MO alarming listed below. Neither the trunk nor the  
station category applies to alarms raised on the common portion of the circuit  
pack.  
If the option associated with the alarm type is set to “n,” the system drops the  
alarm report. Alarm error information remains intact, but no records of alarms and  
no LEDs light on the port circuit pack, the Maintenance circuit pack, the  
attendant console, or alarm reporting station to indicate a problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
set options  
2
2-209  
If technicians set the option “warning” or “report,” port circuit pack LEDs and  
LEDs on the Maintenance circuit pack are affected the same as warning alarms.  
Default parameters are:  
■
■
The system downgrades all station, trunk (except on-board trunk alarms),  
and Minor DS1-BD alarms to warning alarms.  
On-board Major and Minor trunk alarms, and the Memory Card Capacity  
alarm continue to raise alarms and report to INADS.  
Station MOs Affected By This Command  
NOTE:  
Although alarms on some MOs appear as warnings, they should be  
investigated with user-reported problems.  
■
■
■
■
■
Analog Lines (ANL-LINE, ANL-NE-L, ANL-16-L)  
Digital Lines (DIG-LINE)  
Hybrid Lines (HYB-LINE)  
MET Lines (MET-LINE)  
ISDN-BRI Lines (BRI-PORT, BRI-SET)  
If more than 75% of the members of the trunk group alarm, minor arms escalate  
to major alarms. If the trunk category option is set to “warning,” “minor,” “report,”  
or “no,” this no longer happens. Maintenance reactivates individual trunk  
members according to Major and Minor alarm criteria.  
Trunk MOs Affected By This Command  
NOTE:  
Although alarms on these MOs may appear as warnings, the alarms should  
be investigated with user-reported problems.  
■
■
■
■
■
■
■
■
■
Auxiliary Trunks (AUX-TRK)  
Central Office Trunks (CO-TRK)  
Direct Inward Dialing Trunks (DID-TRK)  
Direct Inward and Outward Dial Trunks (DIOD-TRK)  
DS1 Central Office Trunks (CO-DS1)  
DS1 Direct Inward Dialing Trunks (DID-DS1)  
DS1 Tie Trunks (TIE-DS1)  
ISDN Trunks (ISDN-TRK)  
Tie Trunks (TIE-TRK)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
set options  
2
2-210  
Circuit Pack MOs affected by this Command  
NOTE:  
Although alarms on some MOs appear as warnings, the alarms should be  
investigated with user-reported problems.  
NOTE:  
The alarm severity of group one downgrades trunks that are not members  
of Trunk Groups, (for example, PCOLs).  
■
DS1 Interface Circuit Pack (DS1-BD)  
Adjunct-Related MOs affected by this Command  
NOTE:  
Although alarms on some MOs appear as warnings, the alarms should be  
investigated with user-reported problems.  
■
■
■
■
■
■
■
ASAI Adjunct (ASAI-ADJ)  
Lucent Adjunct Port (ATT-PORT)  
Ethernet ASAI Port (LGATE-PT)  
Ethernet ASAI Adjunct (LGATE-AJ)  
Ethernet Lucent Port (ATTE-PT)  
Ethernet Lucent Adjunct (ATTE_AJ)  
ISDN-BRI Ports connected to Adjuncts (ABRI-PORT)  
Adjuncts are administered as stations; however, the administration of alarm  
severity for the station alarm group does not affect alarm severity levels for  
adjuncts. Similarly, the administration of alarm severity for the adjunct alarm  
group does not affect the alarm severity levels for other stations.  
PI-Link and associated Link MOs affected by this  
Command  
NOTE:  
Although alarms on some MOs appear as warnings, the alarms should be  
investigated with user-related problems.  
■
See Processor Interface Link [“PI-LINK (Processor Interface Link)”] for  
other associated Link Maintenance Objects.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
set signaling-group  
2
2-211  
Memory Card MOs Affected by This Command  
NOTE:  
While this option does not automatically downgrade CAP-MEM alarms,  
changes to this options may downgrade alarms to warnings. This alarm  
raises when memory card translation capacity exceeds 98% and is  
intended to alert Services that larger flash cards may be required.  
■
Memory Card Capacity (CAP-MEM)  
Other MOs Affected by This Command  
NOTE:  
Although alarms on some MOs appear as warnings, the alarms should be  
investigated with user-related problems.  
■
■
■
■
■
■
■
■
■
■
■
■
■
EPN Maintenance Circuit Pack (MAINT)  
ISDN-PRI Signaling Group (ISN-SGR)  
Journal Printer (JNL-PRNT)  
PMS Link (PMS-LINK)  
PMS log printer (PMS-LOG)  
Primary CDR Link (PRI-CDR)  
Secondary CDR Link (SEC-CDR)  
SPE Select Switches (SPE-SELEC)  
Synchronization (SYNC)  
System Communication Interface (PI-SCI)  
System Printer (SYS-PRNT)  
TDM Clock (TDM-CLK)  
Tone Generator Circuit Pack (TONE-BD)  
set signaling-group  
This command upgrades secondary D-channel in specified signaling groups to  
primary D-channels. Current primary D-channel then revert to secondary  
D-channels. A signaling group is a collection of B-channels that designate single  
D-channels or a set of D-channels signals over an ISDN-PRI.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
set  
group  
identifier  
administered number associated  
with each signaling group.  
init  
inads  
craft  
none  
none  
signaling-group  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
set synchronization  
2
2-212  
set synchronization  
This command sets DS1 trunks or active tone/clock circuit packs that supply  
references for synchronization. The set synchronization command works after  
the disable synchronization command disables synchronization. Technicians  
may administer DS1 trunks or active tone/clocks with the set synchronization  
command. DS1 or tone/clocks remain synchronization references until the set  
synchronization command runs with another board or until the enable  
synchronization command runs.  
After the enable synchronization command runs, administered primary or  
secondary synchronization sources become synchronization references. If no  
primary or secondary source is administered, synchronization uses active  
tone/clock boards as synchronization references after synchronization is  
enabled.  
The synchronization subsystem provides error-free digital communication  
between the switch and other PBXs, COs, or customer premise equipment.  
System components involved in synchronization include: TDM bus clock, DS1  
trunk board, and maintenance and administration software resident in the SPE.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
set  
location  
Physical position of the DS1 trunk or  
init  
none  
none  
synchronization  
active tone/clock: PCSS  
inads  
craft  
set tdm  
The set tdm command establishes the TDM bus on a port network that houses  
control channels and dedicated tones.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
set tdm  
port  
network  
Port network number of the TDM  
bus  
init  
inads  
craft  
none  
See below  
pn  
number  
bus  
(“a” or “b”) specifies desired half of  
the TDM bus. Configure each 512  
time slot TDM bus as two duplicate  
256 time slot buses, allowing  
duplication of control channels and  
dedicated tone time slots. A port  
network number (1 - 3)  
bus  
override  
Forces the setting of a deactivated  
bus or a bus whose dedicated  
tone time slots are active  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
set time  
2
2-213  
Feature Interactions  
New calls go to time slots reserved for tones on the bus that have not other time  
slots when:  
■
Time slots on a specified bus are in use  
■
Dedicated tone time slots are on the other half of the bus  
A set command to buses that have calls on dedicated tone time slots drops  
these calls.  
set time  
This command allows changes to the day of the week, the day of the month, the  
month, year, hour, and minute. The second field resets to zero (0) whenever the  
time on the clock is altered, but cannot be modified by the technician. The day of  
the week, entered as a text string, translates to an integer for internal storage.  
The system clock time remains the same if no changes are entered on the form.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
set time  
none  
init  
inads  
craft  
System  
Date and time are  
available to software  
from a system  
primitive.  
assigns a  
time if the  
system clock  
is never set  
cust  
rcust  
bcms  
browse  
Output  
The following example shows the output for the set time command.  
set time  
Page 1 of 1  
DATE AND TIME  
DATE  
Day of the Week: _________ Month: _________  
Day of the Month: __ Year: ____  
TIME  
Hour: __  
Second:  
Minute: __  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
set tone-clock  
2
2-214  
Field descriptions  
Day of the Week:  
Day of the Month:  
Month:  
Monday through Sunday  
1-31; the system also checks for leap year.  
January through December  
Year:  
1970-2999  
0-23  
Hour:  
Minute:  
0-59  
Second:  
The system sets this field to zero when the time of day clock is set.  
set tone-clock  
This command sets the active tone/clock for a PN that has a duplicated  
tone/clock circuit pack. Technicians should reset the default active tone clock in  
each PN after using the set tone-clock command. If it is not in use, a single  
failure can cause an unnecessary service outage. The schedule maintenance  
tone-clock switch option does not reset the tone-clock to the default active if it  
was not active at the beginning of the test.  
Feature  
Action/Object  
Qualifier  
location  
override  
Qualifier Description  
Permissions  
Defaults  
Interactions  
set tone-clock  
Tone/clock location: PC  
init  
inads  
craft  
1 (one)  
none  
Forces the set command into  
effect regardless of the tone/clock  
circuit pack’s health.  
set vector  
This command specifies restart levels for core dumps and places core dumps on  
primary Mass Storage System (a tape in a tape system and core dump memory  
cards in a memory card system) devices for later examination. The set vector  
command allows technicians to tailor restart levels that copy memory to primary  
Mass Storage System devices.  
NOTE:  
Software never requests an extended reboot.  
To force an immediate core dump, set the appropriate bit using this command,  
then enter the reset system command at a level that forces core dumps  
corresponding to set vector bits.  
When a system restart occurs in a simplex system with the corresponding vector  
bit set, the core dump writes to secondary storage (the primary MSS device).  
Once the core dump writes, the vector clears and the restart executes.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
set vector  
2
2-215  
!
WARNING:  
This command disrupts service in a simplex system.  
The active SPE executes a core dump when:  
■
A system restart occurs on the active SPE with the corresponding vector  
bit set.  
■
■
■
The active SPE-active option is selected when the vector bit is set.  
The SPE-standby option is selected when the vector bit is set.  
The active SPE-maint option is selected when the vector bit is set.  
The vector clears after all core dumps.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
set vector  
vector value  
See Vector Condition  
Mapping values below  
init  
inads  
craft  
none  
none  
Vector-Condition Mapping  
Value  
Warm  
Cold II  
Cold I  
Reboot  
0
1
2
3
4
5
6
7
8
9
a
b
c
d
e
f
n
y
n
y
n
y
n
y
n
y
n
y
n
y
n
y
n
n
y
y
n
n
y
y
n
n
y
y
n
n
y
y
n
n
n
n
y
y
y
y
n
n
n
n
y
y
y
y
n
n
n
n
n
n
n
n
y
y
y
y
y
y
y
y
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status access-endpoint  
2
2-216  
status access-endpoint  
This command displays the status of an access endpoint and can be helpful in  
locating facilities with which access endpoints communicate.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
access-  
endpoint  
extension  
Extension number of the access  
endpoint  
init  
none  
none  
inads  
craft  
cust  
print  
Report sent to printer  
nms  
browse  
Output  
The following example shows the output for the status access-endpoint 22502  
command. The command assumes that access endpoint ports for extension  
22502 are in cabinet 1, carrier C, slot 11, circuit 1 to 6 — that access endpoints  
are connected on an active call to ports 7 to 12 of the board in location 1B19  
(cabinet 1, carrier B, slot 19). This means that port 01C1101 connects to  
01B1907, port 01C1102 connects to 01B1908, and port 01C1103 connects to  
01B1909.  
status access-endpoint 22502  
ACCESS-ENDPOINT STATUS  
page 1 of 1  
Extension: 22502  
(Starting) Port: 01C1101  
Communication Type: wideband  
Width: 6  
Service State: in-service/active  
Connected Ports: 01B1907 01B1908 01B1909  
01B1910 01B1911 01B1912  
Command Successfully Completed  
Field descriptions  
Extension  
Extension of the access endpoint  
(Starting)  
Port  
Port locations of the access endpoint. For wideband access endpoint,  
the location shown is that of the starting port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
status administered-connection  
2-217  
Communication  
Type  
The valid voice and data communication type that the access  
endpoint is administered. The options are: 56k-data, 64k-data,  
voice-grade-data, and wideband.  
Width  
For 56k-data, 64k-data, and voice-grade data, the width value is 1. For  
wideband, this field displays the number of DS0s that make up the  
access endpoint.  
Service State  
in-service/active, in-service/idle, and out-of-service  
Connected  
Ports  
Port location connected to the access endpoint for an active call. For  
wideband, all ports connected to the wideband access endpoint are  
listed.  
status administered-connection  
This command provides automatic end-to-end connections between two  
access/data endpoints.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
administered-  
connection  
ac  
number  
Administered connection number  
Report sent to printer.  
init  
inads  
craft  
none  
none  
print  
cust  
rcust  
bcms  
browse  
Output  
The following example shows the output from the status  
administered-connection 3 command.  
status administered-connection 3  
ADMINISTERED-CONNECTION STATUS  
page 1 of 1  
Connection Number:  
Enabled?  
Originator:  
Destination:  
Connection State:  
Failure Cause:  
Number of Retries:  
Auto Restorable?  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status attendant  
2
2-218  
Field descriptions  
Connection Number:  
Enabled?  
Number assigned to the administered connection.  
Is administered connection enabled? (y or n).  
Extension of originating access/data endpoint.  
Originator:  
Destination:  
Connection State:  
Destination address used to route administered connections.  
Current status of the administered connection. (connected,  
restored, failed, waiting to retry, attempting to restore, attempting  
to connect, not scheduled, and disabled.  
Failure Cause:  
Reason that the administered connection is attempting to  
connect, to restore, or failed to restore. If the administered  
connection was scheduled to be active but is disconnected, this  
field shows the most recent failure reason.  
Number of Retries:  
Auto Restorable?  
Number of consecutive failed establishment attempts.  
When an administered connection is connected, this field  
indicates if auto restoration attempts when a failure occurs.  
status attendant  
This command diagnoses internal software. This command help to locate  
facilities to which the attendant console communicates.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
attendant  
console  
number  
Assigned attendant number  
(1 –16).  
init  
inads  
craft  
none  
none  
print  
Report sent to printer  
cust  
rcust  
bcms  
browse  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status audits  
2
2-219  
Output  
The following example shows the output from the status attendant 1 command.  
status attendant 1  
ATTENDANT STATUS  
Console Number: 1  
Port: 01C1106  
Connected Ports:  
Service State: in-service/night service  
Download Status: no  
Command successfully completed  
Field descriptions  
Console Number  
Port  
Number assigned to the attendant (1-16).  
Port location of the attendant (cabinet-carrier-slot-circuit).  
Service State  
In-service/idle, in-service/active, out of service, or  
disconnected.  
Usage State  
Idle or active.  
Maintenance Busy State  
Connected Ports  
Is maintenance testing the object? (y or n)  
Port locations to which the attendant is communicating  
(cabinet-carrier-slot-circuit).  
status audits  
This command displays results of Data Relation Audits that are built into the  
switch. Data Relation Audits check for inconsistencies between selected data  
items in the switch, and report inconsistencies. Data Relation Audits are useful  
during development and testing phases of projects to uncover software errors. In  
the field they help the switch to recover from data corruption before service is  
interrupted.  
This command displays the date and time that the requested interval begins, the  
number of times that the full sequence of audits executes (audit cycles), and  
status information about each audit that detected a problem or aborted during  
the interval. The status information contains:  
■
■
■
■
The name of the audit  
The number of times that an audit ran and corrected an error  
The number of times that an audit ran and detected an irreparable error  
The nuDmobwnelroaodffrtoimmeWswtwh.Saotmaannuaaulsd.ciotmra. Anll aMnadnuaalsbSoeratercdh And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status audits  
2
2-220  
■
The date and time that the audit first detected a problem (only for  
cumulative)  
■
The time of the most recent error detected by the audit (only for  
cumulative)  
Audit data information cumulates from the last reboot or the last clear audits  
cumulative command, and for peak hours since the last reboot or the last clear  
audits peak-hour or clear audits cumulative commands.  
NOTE:  
Single process restarts, warm starts, cold 2 restarts, cold 1 restarts, or  
processor interchanges do not clear this data.  
Audits can execute directly using the test MO command. For example, test MO l  
8192 p 512 t 0 executes the Station Connections Audits, audit lnames and  
numbers (pnames) included in the Table Of Audits. When the “test MO”  
command executes an audit, report results display on the screen. In general,  
errors discovered from a demand tests are not logged in the error logs. To be  
consistent with other error logging, and to avoid confusion, errors that are  
discovered from a demand test that executes an audit are not displayed.  
The screen does not automatically update, but reflects the system at the time of  
the request.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
status audits  
peak-hour  
data collected since the last reboot  
or since the last execution of the  
clear audits cumulative  
command.  
init  
inads  
none  
see below  
cumulative  
Data for the peak hour since the  
last reboot or since the last  
execution of the clear audits  
cumulative or clear audits  
peak-hour command.  
print  
Report sent to printer  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status audits  
2
2-221  
Output  
The following example shows the output from the status audits command.  
status audits cumulative  
AUDIT STATUS INFORMATION  
Start Date: 13:00 MON MAR 19 1997 # of Audit Cycles Completed: 67532  
Audit  
Name  
# Cycles  
Fixed Data  
# Cycles Could  
Not Fix Data  
# Cycles  
Audit Aborted  
First  
Error  
Most Recent  
Error  
HTLK  
0
135  
2
1
1
1
1
1
0
*****  
0
0
0
1
0
0
0
0
0
0
0
0
0
03/22/10:14 06/24/16:03  
03/22/10:12 06/10/19:17  
03/22/10:12 03/22/10:20  
03/22/10:13 03/22/19:14  
05/01/02:17 05/01/02:17  
05/01/02:16 05/01/02:16  
03/22/10:12 03/22/10:12  
04/05/13:05 04/05/13:05  
03/22/10:12 03/22/10:12  
03/22/10:12 03/22/10:12  
03/22/10:13 03/22/10:13  
04/05/15:05 04/05/15:05  
03/22/10:14 03/22/10:14  
CR-AUDIT  
HU-CALLS  
SE-CALLS  
TTR-SID  
CO-CALLS  
DE-CALLS  
TR-QUE  
CTRK  
0
0
0
0
0
0
0
1
0
0
0
0
AT-ADM  
CO-ADM  
PC-ADM  
1
1
1
PRI-USR (SCH) 1  
Command successfully completed  
status audits peak-hour  
AUDIT STATUS INFORMATION  
Start Date: 10:00 MON MAR 22 1997 # of Audit Cycles Completed: 25  
Audit  
# Cycles  
# Cycles Could  
# Cycles  
Name  
Fixed Data  
Not Fix Data  
Audit Aborted  
HTLK  
0
2
1
1
0
1
1
0
25  
0
0
0
1
0
0
0
0
0
0
0
0
0
0
1
0
HU-CALLS  
CR-AUDIT  
DE-CALLS  
CTRK  
AT-ADM  
CO-ADM  
SE-CALLS  
PRI-USR (SCH)  
1
0
Command successfully completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status audits  
2
2-222  
Audit information displays with one line of data displayed audit that has detected  
an error or aborted. Audits that did not detect any errors or aborted do not  
display. The output sorts in descending order, based on the sum of the values in  
the # Cycles Fixed Data, # Cycles Could Not Fix Data, and  
# Cycles Audit Abortedfields.  
Field descriptions  
Start Date  
Date and time that interval begins. “cumulative” = date and time of  
the last reboot or execution of the “clear audits cumulative”  
command.  
“peak-hour” = date and time of the beginning of the peak hour  
since the last reboot or execution of a “clear audits cumulative” or  
“clear audits peak-hour” command.  
# of Audit Cycles  
Completed  
Number of audit cycles completed in the specified interval  
(0 – 999999). Asterisks indicate numbers that exceed 999999. The  
switch executes audits in a set order. After all audits execute, the  
switch restarts the sequence.  
NOTE:  
Since this field shows the number of completed audit cycles,  
it is possible that individual audit values, can be larger than  
the values described below (if the switch is partially through  
another audit cycle). Audit Cycles numbers do not apply to  
these audits that execute as part of scheduled maintenance.  
Audit Name  
Audit’s name that detected an error or aborted. A few audits do not  
run in the normal audit sequence. Instead, they execute as part of  
scheduled maintenance and are marked with “(SCH)” following the  
audit name.  
# Cycles Fixed  
Data  
Number of times that the audit ran, in the specified interval, and  
found a fixable problem. (0–65534) Asterisks are used form  
numbers that exceed 65534.  
# Cycles Could  
Not Fix Data  
Number of times that the audit ran, in the specified interval, and  
found an unfixable problem. The audited switch data is  
inconsistent when this happens. (0–65534) Asterisks are used for  
numbers that exceed 65534.  
# Cycles Audit  
Aborted  
Number of times that the audit ran, in the specified interval, and  
aborted due to an internal error. (0–65534) Asterisks are for  
numbers that exceed 65534.  
First Error  
Date and time that the audit first detected fixed data, could not fix  
data or audit aborted problems since the last clear audits  
cumulative command. Example: 03/27/14:31 for 2:31 pm, March  
27th. This field appears with the status audits cumulative display.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status audits  
2
2-223  
Most Recent Error  
Date and time that the audit last detected fixed data, could not fix  
data or audit aborted problems since the last "clear audits  
cumulative" command. Example: 03/27/14:31 for 2:31 pm, March  
27th. This field appears with the status audits cumulative display.  
Feature Interactions  
The clear audits command affects the data displayed by status audits  
cumulative and status audits peak-hour. The clear audits cumulative  
command clears data collected to date, resets the start time kept for that data,  
and clears peak hour data. The clear audits peak-hour command clears data  
kept for the peak hour so that a new peak hour can be established.  
When the schedule option is specified, a scheduling form is displays allowing  
the technician to schedule command execution. Refer to the Report Scheduler  
and System Printer feature specification [3] for details about the scheduling form.  
Table of audits  
The following table shows the names of the audits that are run as part of time  
available maintenance, the audit number (pname) and a short description of  
each audit. These audits execute using lname MO_DR_AUDIT (8192). These  
audits may execute using the test MO command with lname 8192, pname “audit  
number,” and test number 0 (for example, test MO l 8192 p 607 t 0 executes the  
AC state audit).  
Audit  
Audit Name Number  
Description  
AC-ISG  
607  
595  
559  
589  
574  
572  
577  
545  
606  
605  
558  
AC state audit  
ADJUSR  
ADMTRM  
ANUR-A  
AN-ADM  
AN-CALLS  
AN-QUE  
AQSA  
Adjunct user record audit  
Administration terminal audit  
Announcement user record audit  
Announcement group administration audit  
Announcement group calls audit  
Announcement group queue audit  
ACB queue slot allocation audit  
ASAI link status audit  
ASLINK  
ASYLED  
ATACT  
ASAI yellow LED audit  
Attendant active audit  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status audits  
2
2-224  
Audit  
Audit Name Number  
Description  
Attendant availability audit  
ATAV  
557  
576  
529  
515  
523  
540  
596  
614  
617  
629  
560  
569  
527  
624  
600  
528  
530  
516  
585  
623  
601  
586  
513  
544  
512  
526  
583  
584  
531  
517  
ATDRCNT  
AT-ADM  
AT-CALLS  
AT-QUE  
AUR-A  
Attendant resource count audit  
Attendant group administration audit  
Attendant group calls audit  
Attendant group queue audit  
Attendant user record audit  
AU-CIDP  
AWOH-UR  
B2B-TAB  
BR-CALLS  
BUTLK  
Announcement user cid/port audit  
Admin Without Hardware Split User Record Audit  
Board-to-Board Link Audit  
Bridged extensions audit  
Button lock audit  
CALK  
Coverage answer member lock audit  
Attendant connections audit  
Call Classifier Tone Receiver Table Audit  
Call classifier tone receiver audit  
Data module connections audit  
Coverage group administration audit  
Coverage group calls audit  
CATT  
CCTRTAB  
CCTR-SID  
CDM  
CO-ADM  
CO-CALLS  
CPROC  
Call process/call record audit  
Call Progress Tone Receiver Table Audit  
Call progress tone receiver audit  
Wake up call process audit  
CPTRTAB  
CPTR-SID  
CPWAKEUP  
CR-AUDIT  
CSR-A  
Call processing data audit  
Connection service record audit  
Station connections audit  
CSTAT  
CTRK  
Trunk connections audit  
DA-CALLS  
DA-MSG  
DE-ADM  
DE-CALLS  
DAP call record audit  
DAP message buffer audit  
Data extension group administration audit  
Data extension group calls audit  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status audits  
2
2-225  
Audit  
Audit Name Number  
Description  
Data module lock audit  
DMLK  
563  
543  
567  
554  
553  
552  
593  
609  
568  
532  
518  
524  
590  
591  
579  
604  
594  
570  
580  
561  
587  
575  
573  
582  
549  
546  
588  
555  
550  
599  
DUR-A  
Data user record audit  
DXLK  
Data extension member lock audit  
Facility status hundreds table audit  
Facility status tracked user audit  
Facility tracking user audit  
Fiber time-slot record allocation audit  
GIP Timer Audit  
FHT  
FTED  
FTING  
FTSRA  
GIP-TIMER  
HTLK  
Hunt member lock audit  
HU-ADM  
HU-CALLS  
HU-QUE  
IAP-CALLS  
IAP-URB  
IM-HMM  
INST-LNK  
ISGR-A  
Hunt group administration audit  
Hunt group calls audit  
Hunt group queue audit  
IAP call record audit  
IAP user record audit  
HMM image table audit  
Instigator/down-link user link audit  
ISG call record audit  
LOG-A  
MDM error/alarm log audit  
HMM map status table audit  
Malicious call trace administration audit  
MIS facility state audit  
MAP-HMM  
MCT-ADM  
MIS-FAC  
MP-ADM  
MP-CALLS  
MSGQ-HMM  
MST-LOG  
MST-STATE  
MS-CALLS  
MUV  
Modem pool group administration audit  
Modem pool group calls audit  
HMM map request queue audit  
MST Logging Buffer Audit  
MST State Audit  
MISAP call record audit  
Message user verification audit  
Message waiting indicator audit  
Message waiting lamp no AP audit  
MWIA  
MWL-NOAP  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status audits  
2
2-226  
Audit  
Audit Name Number  
Description  
Paging group administration audit  
Paging group calls audit  
PA-ADM  
PA-CALLS  
PCLK  
533  
519  
566  
535  
521  
612  
PCOL member lock audit  
PC-ADM  
PC-CALLS  
PINC-TAB  
Personal CO line group administration audit  
Personal CO line group calls audit  
Packet Inter-Port Network Connection Sub-Table  
audit  
PI-ADM  
PLIP-LNK  
PN-HMM  
PRI-CR  
534  
602  
578  
598  
592  
541  
581  
571  
538  
537  
562  
539  
611  
Pickup group administration audit  
LIP link audit  
HMM pname table audit  
PRI call record audit  
PRI-TBUF  
PUR-A  
TSCUUI buffer audit  
Phantom user record audit  
Service dispatcher stim buffer audit  
Service dispatcher SID audit  
Terminating extension group administration audit  
Terminating extension group calls audit  
Station lock audit  
SDSBUF  
SDSID  
SE-ADM  
SE-CALLS  
STNLK  
SUR-A  
Station user record audit  
S-INC-TAB  
Service Inter-Port Network Connection Sub-Table  
audit  
S-PT-TAB  
S-TAB  
610  
620  
565  
564  
608  
536  
522  
525  
520  
547  
Service-Port Connection Sub-Table audit  
Service Table Audit  
TEGLK  
TEG member lock audit  
TKLK  
Trunk lock audit  
TONE-TS  
TR-ADM  
TR-CALLS  
TR-QUE  
TSC-PRI  
TSRA  
Tone Time Slot Subtable Audit  
Trunk group administration audit  
Trunk group calls audit  
Trunk group queue audit  
ISDN-PRI TSC resource audit  
Time slot record allocation audit  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status audits  
2
2-227  
Audit  
Audit Name Number  
Description  
TTI-STATE  
TTI-TRANS  
TTR-SID  
618  
619  
514  
622  
542  
613  
551  
603  
548  
615  
616  
TTI State Audit  
TTI Translation Audit  
Touch tone receiver audit  
Touch Tone Receiver Table Audit  
Trunk user record audit  
TTR-TAB  
TUR-A  
T-TS-TAB  
UGMA  
Tone Time Slot Connection Sub-Table Audit  
User group membership audit  
Up-link user link record audit  
User record maintenance busy audit  
X.25 Channel Status Audit  
UPUSR-LNK  
URMB  
X25-CHAN  
X25-LINK  
X.25 Link Status Audit  
The following table shows the names of audits that run as part of scheduled  
maintenance, the audit number (pname) and a short description of each audit.  
These audits execute using lname MO_SCH_AUDIT (8193). These audits may  
execute using the test MO command with lname 8193, pname “audit number,”  
and test number 0 (for example, test MO l 8193 p 556 t 0 executes the Message  
Waiting Lamp Audit audit).  
Audit  
Audit Name  
MWL  
Number  
Description  
556  
Message Waiting Lamp Audit  
PRI user record audit  
PRI-USR  
SUR-FREE  
597  
625  
Station User Record Free List Audit  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status bri-port  
2
2-228  
status bri-port  
This command displays the service state, maintenance state and layer 1 state of  
an ISDN-BRI port. This form also displays information about point-to-point  
signaling links that transport over the port.  
Feature  
Action/Object  
Qualifier  
location  
print  
Qualifier Description  
Port location: PCSSpp  
Report sent to printer  
Permissions  
Defaults  
Interactions  
status bri-port  
init  
none  
none  
inads  
craft  
cust  
nms  
browse  
Output  
For the following example shows the output from the status bri-port 1c1701  
command.  
status bri-port 1c1701  
Page 1 of 1 SPE A  
STATUS BRI-PORT  
Port: 01C1701  
Service State: in-service  
Maintenance Busy?: no  
Layer 1 State: activated  
TEI Value Layer2 State  
Endpt Extension  
Endpt SPID  
1010  
Service SPID?  
Link1  
Link2  
Link3  
64  
13-established 1010  
Field descriptions  
Port:  
ISDN-BRI port address.  
ISDN-BRI port is “in-service” or “out-of-service.”  
Service State:  
Maintenance Busy?:  
specifies if maintenance testing is executing on the ISDN-BRI  
port (“yes” or “no”).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status bri-port  
2
2-229  
Layer 1 State:  
BRI Layer 1 (physical) state on the port. Valid states are  
“activated,” “pend-activation,” and “deactivated.”  
■ “activated” state = layer 1 frames are passing between the  
port and BRI endpoints.  
■ “pend-activation” state = the port is in-service, the layer 1  
interface device is on, layer 1 frames are sending to the BRI  
endpoints connected to this port, but BRI endpoints are not  
responding.  
■ “deactivated” state = the layer 1 interface device on the BRI  
is off, because the port goes out-of-service.  
TEI Value  
Layer 2 addressing parameter used by the switch to exchange  
information over point-to-point signaling links between BRI  
endpoints. Each point-to-point signaling link has an associated  
TEI. This field displays the addressing parameter value. (0–127)  
Layer2 State:  
Point-to-point signaling link layer 2 state. Valid states are  
“un-assigned,” “assigned,” “established,” “l3-established” or  
“hyperactive.”  
■ “un-assigned” = the link is in TEI-UNASSIGN state at Layer 2.  
■ “assigned” state = the link is in the AWAIT_EST (Await  
Establish) state at layer 2. (If BRI endpoints support TEI  
allocation procedures, they successfully execute and a TEI is  
assigned to the endpoint by the switch.  
■ “established” = the link is in the MF_EST_NORM (Multi-Frame  
Established Normal) state at layer 2. The switch successfully  
initiates the link can now exchange layer 3 frames with the  
endpoint. If the endpoint does not support SPID initialization  
procedures, the endpoint extension associated with the link  
also displays. This is the normal state for the link in the  
point-to-point wiring configuration.  
■ “l3-established” = link is in the MF_EST_NORM state at layer  
2 and SPID initialization procedures successfully complete.  
The endpoint extension associated with the link also displays.  
This is the normal state for the link in the multi-point wiring  
configuration.  
■ “hyperactive” = traffic on this link goes over threshold. The  
link suspends and is deemed hyperactive.  
Endpt Extension  
Voice/data endpoint extension associated with the link if the link  
is in the “established” (point-to-point configuration) or  
“l3-established” (multipoint configuration) layer 2 state.  
Otherwise, this field is blank.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status bri-port  
2
2-230  
Endpt SPID  
This field displays the SPID administered on the voice/data  
endpoint associated with the link. Note that this information is  
displayed only if the link is in either the “established”  
(point-to-point configuration) or the “13-established” (multipoint  
configuration) layer 2 state. Otherwise this field is blank.  
Service SPID  
Indicates if the link is associated with the Service SPID. If the link  
is associated with Service Spuds, the field contains a “yes” and  
the endpoint extension field is blank; otherwise, this field is blank.  
Service SPID checks building wiring between the switch and the  
BRI endpoint.  
Status bri-port interpretation  
Table 2-3 provides information on the status bri-port form.  
Table 2-3. Status BRI-Port Command Interpretation  
Endpoint  
Types  
TEI  
Range  
Voice  
Extension  
Service  
SPID  
Layer 2 State  
Description / Recommendation  
ASAI, BRI 0-126  
Assigned  
blank  
blank  
Transitory state for BRI endpoints  
and ASAI adjuncts. The switch  
attempts link establishment.  
1. Check endpoints and wiring by  
following SPID Facility Test  
Procedures described in the  
BRI-SET (ISDN-BRI Set/ASAI  
Adjunct) Maintenance  
documentation.  
2. Verify repairs with status  
bri-port PCSSpp. Determine  
that L2 state of the signaling link  
is “L3-Established” for ASAI  
adjuncts and BRI endpoints  
supporting MIM (management  
information messages)  
initialization and “Established”  
for fixed TEIBRI endpoints and  
automatic TEIBRI endpoints not  
supporting MIM initialization.  
NOTE:  
A MIM is a level-3 message  
that conveys management  
and maintenance information  
between communications  
systems and BRI terminals.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status bri-port  
2
2-231  
Table 2-3. Status BRI-Port Command Interpretation — Continued  
Endpoint  
Types  
TEI  
Range  
Voice  
Extension  
Service  
SPID  
Layer 2 State  
Description / Recommendation  
ASAI  
0-63  
Established  
blank  
blank  
Transitory state for ASAI adjuncts.  
ASAI signaling is connects at Layer  
2. Layer 3 Restart procedure does  
not complete between switch and  
adjunct.  
1. Check the adjunct by following  
the manufacturer’s  
recommended repair  
procedures.  
2. Verify repairs by executing the  
status bri-port PCSSpp  
command. Determine that the  
L2 state of the signaling link is  
L3-Established.  
BRI  
0-126  
Established  
ext  
blank  
blank  
Normal state for non-MIM initializing,  
fixed and automatic TEIBRI  
endpoints.  
BRI, ASAI 64-126 Established  
blank  
Transitory state for automatic TEIBRI  
endpoints which support MIM  
initialization.  
1. Verify that SPID administration  
on the switch and endpoint are  
consistent. Verify the repair by  
executing the status bri-port  
PCSSpp command. Determine  
that the L2 state of the signaling  
link is L3-Established.  
Otherwise, proceed to Step 2.  
2. Try to replace the endpoint.  
Verify the repair by executing  
the status bri-port PCSSpp  
command. Determine that the  
L2 state of the signaling link is  
L3-Established.  
BRI  
64-126 L3-Established ext  
blank  
Normal state for automatic TEIBRI  
endpoints supporting MIM  
initialization.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status bri-port  
2
2-232  
Table 2-3. Status BRI-Port Command Interpretation — Continued  
Endpoint  
Types  
TEI  
Range  
Voice  
Extension  
Service  
SPID  
Layer 2 State  
Description / Recommendation  
BRI, ASAI 64-126 L3-Established blank  
yes  
Technicians conduct SPID  
facilitation tests on the port. Links  
are not associated with BRI port  
endpoints. See description of SPID  
Facility Test Procedures in the  
‘‘BRI-SET, ASAI-ADJ, BRI-DAT’’  
maintenance documentation.  
BRI  
BRI  
64-126 L3-Established ext  
yes  
Technicians conduct SPID  
facilitation tests on the port. Links  
are associated with port endpoints.  
See description of SPID Facility Test  
Procedures in the ‘‘BRI-SET,  
ASAI-ADJ, BRI-DAT’’  
maintenance documentation.  
0-126  
L3-Established blank  
blank  
Invalid SPID assigned to link.  
1. Change the SPID value in the  
BRI endpoint to match the SPID  
administered to the BRI  
endpoint on the port. Verify the  
repair by executing the status  
bri-port PCSSpp command.  
Determine that the L2 state of  
the BRI endpoint is  
L3-Established.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status bri-port  
2
2-233  
Table 2-3. Status BRI-Port Command Interpretation — Continued  
Endpoint  
Types  
TEI  
Range  
Voice  
Extension  
Service  
SPID  
Layer 2 State  
Description / Recommendation  
BRI  
(cont’d)  
0-126  
L3-Assigned  
ext  
blank  
Transitory state for BRI endpoints  
which support MIM initialization.  
2. Wait for five seconds and repeat  
the command. If the state has  
not changed, continue with Step  
2.  
3. Make sure SPID administration  
on the switch and endpoint are  
consistent. Verify the repair by  
executing the status bri-port  
PCSSpp command. Determine  
that the L2 state of the signaling  
link is L3-Established.  
Otherwise, go to Step 3.  
4. Try to replace the endpoint.  
Verify the repair by executing  
the status bri-port PCSSpp  
command. Determine that the  
L2 state of the signaling link is  
L3-Established.  
BRI  
(cont’d)  
0-126  
L3-Assigned  
ext  
yes  
Transitory state for BRI endpoints  
which support MIM initialization  
when SPID Facility Test initializes  
the station.  
5. Wait for five seconds and repeat  
the command. If the state has  
not changed, continue with Step  
2.  
6. Make sure SPID administration  
on the switch and endpoints are  
consistent. Verify the repair by  
executing the status bri-port  
PCSSpp command. Determine  
that the L2 state of the signaling  
link is L3-Established.  
Otherwise, go to Step 3.  
7. Try to replace the endpoint.  
Verify the repair by executing  
the status bri-port PCSSpp  
command. Determine that the  
L2 state of the signaling link is  
L3-Established.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status card-mem  
2
2-234  
Table 2-3. Status BRI-Port Command Interpretation — Continued  
Endpoint  
Types  
TEI  
Range  
Voice  
Extension  
Service  
SPID  
Layer 2 State  
Description / Recommendation  
ASAI  
0-126  
Hyperactive  
ignore  
ignore  
Link has sent too many messages  
per unit time.  
BRI  
Signaling suspends. System  
timeouts in 60 seconds and  
attempts reactivate the link. If links  
remain in this state while no activity  
occurs at BRI endpoints:  
1. Ensure that SPID switch  
administration and endpoints  
are consistent. Verify repairs by  
executing the status bri-port  
PCSSpp command. Determine  
that the L2 state of the signaling  
link is L3-Established.  
2. Replace the endpoint. Verify  
repairs by executing the status  
bri-port PCSSpp command.  
Determine that the L2 state of  
the signaling link is  
L3-Established.  
ASAI  
ASAI  
0-126  
0-126  
L3-Restarting  
L3-Restarted  
ext  
ext  
The switch sends a Restart  
message to the adjunct but has not  
received a Restart Acknowledgment  
message from the adjunct.  
After receiving a Restart  
Acknowledgment message, the  
switch sends a Heartbeat message  
to the adjunct and awaits a  
response.  
ASAI  
0-126  
L3-Established ext  
Normal state for ASAI adjunct.  
status card-mem  
Memory cards are portable, compact memory cards that contain banks of flash  
EPROM chips. Non-volatile memory cards are eraseable and randomly  
programmed with user data. Main memory stores system software in its “flash”  
section. Memory cards that save translations do not contain copies of the system  
software. During system reboot or system power down conditions, in-core system  
maintenance hardware error logs temporarily save in memory cards before the  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status card-mem  
2
2-235  
system goes down. Then, the error logs file reads back when the system restarts.  
The Hard Patch feature also uses the memory card as temporary storage when  
LMM applies patched files to the system software.  
The status card-mem command displays the following memory card information  
located at active or standby SPEs:  
■
■
■
■
■
■
■
Is a valid memory card in place?  
Is the memory card write-protected?  
What is the capacity of the inserted memory card?  
What kind of system configuration - small or medium?  
What is the number of pulses counted in the last erase operation?  
What is the percentage of translation storage space used?  
What are the names of files stored in the memory card, and what is date  
and time (if available) when it was saved?  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
location  
Physical carrier position of memory  
init  
none  
see below  
card-mem  
card: PC (1A).  
inads  
craft  
cust  
print  
Report sent to printer  
rcust  
nms  
bcms  
browse  
Feature Interactions  
■
If the Announcement feature is unavailable in the system features  
configuration, the Data Presentfield is always nfor the announcements  
file. The Announcement feature requires a memory card with a minimum  
capacity of 4 MB. If the memory card is less than 4 MB, Announcements  
cannot be save in the memory card.  
■
Core Dump features require 10 MB memory cards for saving core dumps.  
If the memory card has a capacity less than 10 MB, the core dump  
operation fails.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status card-mem  
2
2-236  
Output  
The following example shows the output from the status card-mem command.  
status card-mem  
MEMORY CARD STATUS  
Location: 01A  
Write Protection: off  
Capacity (MB): 4 Series 1  
Number of Erase Pulses: 78  
Card Format: G3v5 Translation Storage Space Used (%): 21  
Status: inserted  
System Size: Medium  
File Name  
translation  
announcements  
Data Present  
Date  
2/17/97  
2/15/97 20:30  
Time  
9:00  
y
y
Command successfully completed  
Field descriptions  
Location  
Physical location (carrier) of the memory card = PC (always 1A).  
System Size  
System configuration (Smallor Medium). This information catches  
errors such as an incorrectly-sized memory card.  
Capacity  
Memory card capacity and the series number (a 3-digit format for the  
memory card size and a 1-digit format for the series number). Memory  
card file contents are described below.  
Capacity of Memory Card  
Card  
Size  
User  
Customer File Names  
1 Mb  
Small w/o Announcements  
Medium w/o Announcements  
translation  
4 Mb  
4 Mb  
translation  
Small and Medium with  
Announcements  
translation  
announcements  
10 Mb  
20 Mb  
Maintenance (core dump)  
translation  
announcements  
core_dump  
System Upgrade  
system_software  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status cdr-link  
2
2-237  
Status  
inserted= valid card is in the memory card slot, and the switch can  
perform I/O operations to the memory card.  
no card= no card is inserted, or the card has a bad connection.  
unformatted= the card is unformatted, or the switch cannot  
recognized it.  
Write-  
Protection  
on= the write-protection toggle on the memory card is on; off= the  
write-protection toggle on the memory card is off. If the  
Write-Protectionfield is on, the switch cannot store files to the  
memory card.  
Number of  
Erase Pulses  
A decimal integer indicating the "wear" condition of the memory card.  
An erase failure indicates that the software-defined threshold has been  
reached and the card should be replaced.  
Translation  
StorageSpace  
Used (%)  
Percentage of reserved storage space for translation files in the  
memory card.  
NOTE:  
This percentage is valid for the specific memory card used in the  
most recent save translation operation (implemented with the  
save translation command or with scheduled maintenance and  
save translation enabled). If the memory card is replaced with  
another card or if no save translation is performed on the new  
memory card, the percentage does not indicate the translation  
storage space used in the new card.  
File Name  
Filename (see “Capacity of Memory Card” table above)  
Data Present  
Date Time  
If the file contains valid data, then ydisplays; otherwise, n.  
This field shows the date and time when the file was saved into the  
memory card. For the “Software Upgrade” type of memory card, this  
field contains the system software release number instead of the time  
stamp. Due to a restriction of “core dump” file formats, the year  
information is not available in the date/time string.  
status cdr-link  
This command displays the status of call detail recording (CDR) links. Link up or  
down status displays. If a link is down, the system displays the number of times  
the switch attempts link setup.  
Call detail recording (CDR) links physically link SPEs to a recording device (for  
example, printer) for sending CDR call records. CDR link are composed of a data  
channel on the NETCON board or EIA port on the processor circuit pack, a  
digital port and a data module. Two CDR links can exist in the system.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status cdr-link  
2
2-238  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status cdr-link  
print  
Report sent to printer.  
init  
none  
none  
inads  
craft  
cust  
rcust  
nms  
bcms  
browse  
Output  
The following example shows the output from the status cdr-link command.  
status cdr-link  
CDR LINK STATUS  
Primary  
Link State: up  
Secondary  
extension not administered  
Number of Retries: 0  
Maintenance Busy? no  
Field descriptions  
Link State  
up= link is up and available to the application. (normal state)  
down= link is physically down.  
Extension not administered= administer system cdr  
feature form.  
Number of Retries  
Maintenance Busy  
The number of times the switch tried to initialize the link.  
yes= maintenance object is busied out; no= not busied out.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status cleared-alarm-notif  
2
2-239  
status cleared-alarm-notif  
Expert Systems use this command to detect chronic alarming conditions. If this  
command displays Feature is suspended, Expert Systems can identify open  
trouble tickets as chronic problems for special consideration.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
cleared-alarm-  
notif  
1
First OSS telephone number  
status of Cleared Alarm  
Notification.  
init  
First OSS  
telephone  
number for  
the Cleared  
Alarm  
none  
inads  
craft  
cust  
rcust  
2
Second OSS telephone number  
status of Cleared Alarm  
Notification.  
Notification  
status.  
status conference  
Use this command to solve the following multimedia problems:  
1. A user cannot join or remain connected to a conference.  
2. Automatic algorithms — audio AUTO mode and the Px64 video picture  
specifications downgrade the conference, causing poor video quality.  
3. A user does not receive full service.  
4. An audio add-on user cannot join or remain connected to a conference.  
5. A conferee is not seen by other users due to interworking problems.  
6. Users cannot participate in Multipoint Communications Service  
conferences.  
7. Continuous conferences do not move endpoints in or out of quadrants.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
conference  
status  
conference  
Stored conference data.  
init  
inads  
craft  
Conference-  
ID = all (all  
stored data).  
none  
status  
conference  
2 print  
Conference 2 data (current  
or last completed). Sends  
report to printer.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-240  
Output  
Screen 2-8. status conference: page 1 of 2  
It is possible for several records to display. Active conferences display first (in  
order of conference-ID), followed by completed conferences (most recently  
completed first). Conferences that have not begun have no data or information.  
Conference data displays in 2 parts: the first screen describes the status of the  
conference and indicates the modes and levels of the conference. It also  
identifies in-use endpoints that cause conference operating modes to change.  
This screen is similar to the administration screens. The remainder of the screens  
display endpoint level data (up to 8 endpoints per screen), revealing ports and  
drop reasons.  
Screen 2-8 shows page 1 of a typical administration screen. The first screen  
appears when status conference is entered and at least 1 valid conference is  
found.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-241  
Field descriptions (status conference, page 1)  
status  
Current status of the conference (active, in-use, complete)  
conference  
name  
(MMCH DYNAMIC)  
conference  
mode  
(Voice-activated)  
password  
Not Applicable  
Not Applicable  
password  
scope  
cascade mode Conference cascade mode (blank)  
audio mode  
class  
Current operating audio mode (G.711-A, G.711-mu, G.728. G.722)  
Conference type (dedicated)  
data mode  
MLP rate  
Conference data mode capability (none, any-mlp, ww-pcs)  
Conference MLP Data Rate (blank).  
start  
Conference start time in 24-hour notation with month and day.  
time/date  
stop  
time/date  
End of conference in 24-hour notation with month and day. It is the  
actual end time if Status is complete; otherwise, it is blank.  
admin  
bandwidth  
Channel bandwidth administered on the Conference Record form.  
(64k)  
no of  
Number of channels required for each Px64 endpoint (2)  
channels  
Chair  
Current chair token holder. ( )  
conf  
bandwidth  
Current operating channel conference bandwidth. Different from the  
administered bandwidth because of Rate Adaptation.  
Rate  
Does this conference support Rate Adaptation? (n, y)  
adaptation  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-242  
Format  
The video format for single-screen conferences: CIF, QCIF,  
(in/out)  
QCIF/CIF, H.CTS, H.CTX+, and SG4.  
non-H.261 conferences = input and output formats are always  
symmetric and the mode is the same for input and output. (H.CTX,  
H.CTX+, and SG4).  
H.261 mode non-continuous presence conferences = symmetric  
format (CIF and QCIF).  
Non-presentation, continuous presence conference in single-screen  
= symmetric format (CIF and QCIF).  
Presentation mode H.261 single screen continuous presence capable  
conferences = symmetric input and output formats QCIF/CIF  
(displayed as CIF) or asymmetric QCIF/CIF, if the administered format  
is upgradable.  
For quad-screen conferences = the format is QCIF/CIF to reflect the  
QCIF input from all participants and output of CIF to all participants.  
For presentation mode quad-screen conference = the format is  
QCIF/CIF to reflect the input/output of all participants except the  
presenter. In quad-screen mode, presenter input is always CIF.  
FPS  
The CIF frame rate (frames per second) - ‘-‘, 30, 15, 10, 7.5. FPS  
indicates the rate that endpoints can receive frames. The MCU cannot  
detect maximum transmit frame rates or current frame rates. Frame  
rates change due to the amount of motion in the input image.  
QFPS  
The ACIF frame rate (frames per second) (‘ -‘, 30, 15, 10, 7.5). The  
rate that an endpoint can generate/receive frames.  
Quad-screen VAS conferences = QFPS reflects the highest common  
QCIF frame rate of all endpoints and the video mixer board rate, that  
is lower than the rest of the participants. QCIF calculation accounts for  
the highest common CIF frame rate declared by all conference  
participants, since the QCIF rate cannot be greater than that of the  
highest common CIF rate.  
Quad-screen presentation conferences = QFPS reflects the highest  
common QCIF frame rate of all participants and the video mixer board  
rate. QFPS cannot be greater than the CIF frame rate that is  
announced by the presenter.  
QFPS field is blankfor proprietary modes.  
lo/hi  
Does this conference support Low Speed/High Speed Interworking?  
interworking  
This field defaults to n.  
Type  
The type of conferee — Audio/Video (P64), Audio Add-on (AUD),  
Cascade Link (CAS), BONDing Call (BOND), BONDing Cascade Link  
(BCAS), UCC Controller (UCC), or Dedicated Access (DA). BONDing  
calls use up to 12 channels to form a single multimedia pipe.  
Ext  
Administered endpoint extension. ( ).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-243  
Meet-me  
number  
The Meet-Me Number administered for the Meet-Me Extension. ( )  
Dial Type  
“in” = dial-in to join endpoint to conference.  
“out” = dial-out to join endpoint to conference.  
In Use  
“y” =the endpoint is in use and is fully-connected on all media in an  
active conference.  
“c” = the endpoint is in use and is fully-connected; however, the  
endpoint has changed conference audio or video capability or  
conference rate due to rate adaptation. This condition requires  
analysis of this endpoint’s capabilities and mode fields to identify  
reduced capability.  
“e” = the endpoint is in use but has capability problems. The endpoint  
lacks one of the required capabilities (Vid, Bhl, MLP) to fully  
participate. For MLP capabilities, see the “T120” field. This condition  
requires analysis of this endpoint’s capabilities and mode field to  
identify the missing capability.  
“f” = the endpoint is in use but not connected to all media. The  
endpoint declared all required capabilities (channel/video/  
audio/data) but is not fully connected to all conference media. This  
endpoint may be connecting, failed to connect, or is not a valid video  
source. This condition requires analysis of this endpoint’s capabilities  
and mode fields to identify the problem.  
“n” = the endpoint disconnected during a conference or  
unsuccessfully attempted to connect to a conference.  
“blank” = the field is blank until the first call from or to the endpoint.  
“y” = the endpoint has the required number of channels.  
Chl  
“e” = the endpoint does not declare support for the correct number of  
channels and cannot participate fully in the conference.  
“n” = the endpoint declares the correct number of channels, but not  
all join the conference, due to a network or endpoint problem.  
“blank” = Audio add-on endpoints set the Chlfield to blank.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-244  
Aud  
“y” = the endpoint has the required audio capability. Audio add-on  
endpoints always set the Aud field to y when the endpoint joins the  
conference.  
“c” = the endpoint is PCM only and it changes the conference video  
quality by changing the operating audio from G.728 to G.711. If  
administered audio modes are auto and the administered bandwidth  
is 112 kbps (56 k/channel) or 128 kbps (64 k/channel), the system  
initiates with the highest common audio, G.728. When the  
administered bandwidth is greater than 128 kbps, the system initiates  
with the highest common bandwidth, 7 kHz.  
“e”= A PCM-only endpoint that could not support the administered  
audio mode, G.728 (such as a data conference), or G. 278/G.711  
endpoint that could not support the administered audio mode, 7 kHz.  
Such endpoints operate with PCM audio and interwork with current  
operating audio modes.  
blank = blank until the first call from or to the endpoint.  
Vid  
“y” = the endpoint has the required video capability and should be  
receiving video if the Chl, Aud, and Dat fields are y.  
“c” = downgraded conference video quality from changing CIF to  
ACIF or by decreasing the frame rate. The conference video mode  
defaults to CIF If QCIF-only endpoints join the conference, the entire  
conference operates in QCIF, with downgraded video clarity. The  
conference frame rate is initially set to the highest frame rate that can  
be reduced by any endpoint. If the conference video mode is not  
administered with upgrade capability, the video parameters for a  
conference are “downgraded.” They are not “upgraded” until all  
endpoints disconnect from the conference.  
“e” = the endpoint doe not declare video capability in its cap-set.  
“n” = audio only, not receiving video, due to audio or data problems.  
“blank” = Audio add-on endpoint defaults the Vid field to blank.  
Mlp  
Gx  
Control Link to the ESM (T.120 stack terminator) status, the endpoint  
MLP data capability, and the state of the data connection in the T.120  
stack. This field defaults to blank, indicating that the Data Mode for  
the conference is none.  
“y” = This endpoint has Still Frame Graphics capability.  
e = This endpoint does not have Still Frame Graphics capability. The  
conference retains still frame graphics capability when non-compliant  
endpoints join the conference.  
blank = This endpoint never joined the conference.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-245  
Rate Adpt  
Rate adaptation/Interworking indicator (5, 6, y, c, e, n, blank). 5 and  
“6” apply to Low Speed/High Speed Interworking. All other values  
apply to Rate Adaptation.  
“5” = 56-kbps (Low Speed) endpoint joins a High Speed (128 kbps or  
above) conference. This endpoint connects with audio only capability  
but is not a valid video source and destination.  
“6” = 64-kbps (Low Speed) endpoint joins a High Speed (128 kbps or  
above) conference. This endpoint connects with audio only capability  
but is not a valid video source and destination.  
“y” = Endpoint joins the conference at 64 kbps, but because rate  
adaptation to 56 kbps is triggered by another endpoint, this endpoint  
rate adapts to 56 kbps.  
“c “ = The administered conference bandwidth is 64 kbps. This  
endpoint joins the conference at 56 kbps. The first 56 kbps endpoint  
that joins 64 kbps rate adaptable conferences triggers rate adaptation  
(see Join Timebelow).  
“n” = Another endpoint triggers a 64-kbps conference to rate adapt to  
56 kbps. This endpoint joins the conference at 64 kbps, but  
encounters problems in rate adapting to 56 kbps. This endpoint may  
have audio and may be receiving video, but is not a valid video  
source.  
“blank” Rate adaptation was not triggered by any endpoint. If this  
endpoint is in use and connected, it joins the conference at the  
administered bandwidth.  
Bond Mode  
Ts  
BONDing Mode = blank for calls that are unrelated to bonding.  
“t” = The endpoint detects voice energy (talking).  
“m” = The endpoint indicates to the MCU that it is muted. It is possible  
for an endpoint to mute, but not send any indication to the MCU. In  
this situation the MCU does not display a mute indication.  
“M” = UDD/CRCS Agent interface mutes the endpoint’s audio. Both  
the endpoint and the UCC/CRCS Agent must mute the endpoint  
audio.  
“S” = The solo-audio state set by UCC/CRCS Agents mutes the  
endpoint’s audio. While in solo-audio state, new endpoints that join  
the conference automatically mute.  
“blank” = Voice energy (talking) is not detected from the endpoint.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-246  
Vs  
MCU endpoint video state (a, b, B, c, i, r, R, s, S, u, U, v, blank).  
Quad-screen conferences = an *appears before the Vs value  
indicating that an endpoint belongs to the mixed image. #appears  
before Vs values indicating that an endpoint is set to be in the mixed  
image (via administration or UCC/CRCS Agent), but instead, Fill  
video displays in its place. This occurs when videos of an endpoint  
that are set in a quadrant cannot be used as a video sources,  
because the endpoint is not joined to the conference, suppresses its  
video, or has invalid video for its video source. Up to four endpoints  
may have an *or #before the Vs field value.  
Quad-screen conferences in VAS mode = Mixed images broadcast to  
all endpoints.  
Quad-screen conferences in presentation mode = Mixed images are  
return videos to the presenter.  
Vs  
a = Applies to quad-screen conferences. *a indicates that an  
endpoint belongs to the mixed image and is administered to one of  
the quadrants, but is not currently connected (Fill image displays).  
(cont’d.)  
b = Applies to full-screen conferences. This endpoint’s video  
broadcasts to other sites. This conference is in VAS, broadcast, or  
presentation mode. Quad-screen VAS conferences are prefix with an  
* indicating that this endpoint’s video belongs to the mixed image.  
Quad-screen presentation conferences, (b without an asterisk)  
identify the presenter as the broadcaster.  
B = The UCC roll call feature causes the endpoint’s video to  
broadcast to other sites. The UCC roll call feature performs in  
full-screen mode.  
“c” = This endpoint’s video broadcasts to other sites. The conference  
is in chair mode and the chair designates the broadcaster. Chair  
features perform in full-screen mode.  
“i” = The endpoint is not a valid video source. #i represents  
continuous presence conferences with endpoints that are set in  
particular quadrants.  
“r” = For full-screen conferences, the endpoint’s video is the return  
video to the broadcaster. For continuous presence conference in  
presentation mode, *r represents a VAS quadrant that belongs to the  
mixed image.  
“R” = The UCC browse feature causes the endpoint’s video to return  
video to the broadcaster. UCC Browse feature perform in full-screen  
mode.  
“s” = The endpoint suppresses this endpoint’s video. For continuous  
presence conference with fixed quadrant participants, #s represents  
endpoints that are fixed in a particular quadrant.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-247  
Vs  
“S” = UCC/CRCS Agent interface suppresses this endpoint’s video.  
(cont’d)  
For continuous presence conference with fixed quadrant participants,  
#S represents endpoints that are fixed in a particular quadrant S  
displays when both the endpoint and the UCC/CRCS Agent suppress  
the endpoint video.  
“u” = For full-screen conferences, this endpoint’s video broadcasts to  
other sites. The conference is in VAS mode and the UCC/CRSCS  
Agent interface designates the broadcaster. For quad-screen  
conferences, UCC/CRCS Agents designate this endpoint as set in a  
quadrant. An *u represents endpoints that belong to the quad image,  
and #U represents disconnected endpoints.  
“U” = For quad-screen conferences UCC/CRCS Agents designate  
quadrants as VAS. *Uindicates that this endpoint belongs to the  
quad image.  
“v” This endpoint’s video broadcasts to other sites. The conference is  
in VAS mode but the endpoint asks to be a broadcaster with the  
“See-Me” request and is granted a MCV (Multipoint Command  
Visualize) token. The See-Me feature performs in full-screen mode.  
“blank” = The endpoint’s video is not broadcast, return, video, or part  
of the mixed-image, but it is a valid video source.  
status conference  
page 2 of 2  
STATUS OF CONFERENCE:  
Sum Grp: Group1 Group2 Group3 Group 4  
L1:  
L2:  
Join  
Time  
Drop  
Time  
Drop  
Reason  
AC --------Ports--------- Sum  
Num Trunk Video Aud/Esm Grp Software  
Ext  
1:  
2:  
3:  
4:  
5:  
6:  
Screen 2-9. status conference: page 2 of 2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-248  
Field descriptions (status conference, page 2)  
Sum Grp  
The VD audio Level 1 (L1) and Level 2 (L2) summer group parts for  
each assigned group (1-4). Summer parts are assigned only for  
conferences with over 6 participants. When a conference operates at an  
audio mode of 7 kHz (administered audio mode is 7 kHz, or auto with  
the bandwidth greater than 128 kbps), the system allocates “primary”  
and “secondary” L1 and L2 summer parts. Primary and secondary parts  
are allocated as adjacent port slots on the same board. Status  
conferences display primary summer ports. Secondary summer ports  
are one slot higher than displayed primary summer ports.  
Join Time  
Drop Time  
Time (in 24-hour notation) when the channel joins the conference.  
Time (in 24-hour notation) when the channel disconnects. If the first  
channel has a drop time, the endpoint is inactive. If a drop time exists  
without a join time, the call disconnects without joining the conference.  
Drop Reason  
Channel’s disconnect because:  
“2-pri” = Administration errors cause mismatches in primary-secondary  
designation for cascade linking. This mismatch indicates that both  
MCUs are administered as primaries (see “Cascading” for a description  
of primary-secondary compatibility).  
“2-sec” = Administration errors cause mismatches in primary-secondary  
designation for a cascade link. This mismatch indicates that both MCUs  
are administered as secondaries (see “Cascading” for a description of  
primary-secondary compatibility).  
“Agent” = The reservation agent causes the call to disconnect.  
“Bandwidth” = A mismatch occurs between a call and the conference it  
attempts to join.  
“BondHshake” = Information channel parameters are unsupported or  
invalid, parameter negotiations terminate out of sequence, timers expire  
because secondary channels do not establish, or BONDing framing is  
undetected for one of the other channels.  
“Busy” = MCU detects that the conferee’s terminal equipment is busy.  
This drop reason is detected by ISDN cause values (for example h0).  
See “Dial-out” for a description of CPTR usage.  
“Chair” = Chair Command Disconnect (CCD) or Chair Command Kill  
(CCK) signals disconnects the endpoint.  
“Conf End” = The conference ends when it reaches the stop time for a  
reserved conference or an active conference converts to file.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-249  
Drop Reason  
Endpoint Clearing received from DS1. The endpoint causes the  
disconnect. The endpoint notifies the MCU that it intends to disconnect.  
(cont’d)  
Far-end Clearing received from DS1. The network or endpoint cause the  
disconnect.  
“Handshake” = Framing is not located or is lost for over 40 seconds and  
the endpoint disconnects. (The endpoint cannot complete initialization  
due to problems with finding Frame Alignment Signal (FAS), Multi Frame  
Alignment (MFA) and getting a corrected coded cap-set.)  
“IDtimeout” = The H.320 sends three unsuccessful responses to the  
MCU regarding the UIN/password Query. Timeout periods exist for each  
period.  
“Internal” = MCU cannot allocate the necessary trunk resources to route  
the dial-out call for the specified dial-numbers. This problem can be  
associated with routing patterns or trunk associated translations, or it  
can indicate insufficient trunk resources.  
“Network” = Clearing received from DS1. The network causes the  
disconnect. The endpoint with disconnect notification capability  
disconnects without notifying the MCU.  
“Not-MCU” = The dial-out destination number(s) of the “CAS” extension  
terminates to a number that is not a dial-in cascade MCU extension.  
“No-ring” = Calls are up for 30 seconds without ringing.  
“Reorder” = The MCU CPTR resources detects that no network trunks  
are available to place the call. See “Dial-out” for a description of CPTR  
usage.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-250  
Drop Reason  
“Pre-AnsDrop” = The call disconnects before an endpoint answers. The  
network, an endpoint, or a terminal adapter may cause the disconnect.  
This drop reason differs from ‘No-answer,’ which indicates that a  
60-second timeout occurs during alerting. In this case, the call drops  
before the 60-second timer expires. Some busy endpoints connected  
through terminal adapters display this behavior.  
(cont’d)  
“Resource” = MCU cannot provide resources (VC or MMI) when the call  
arrives or loses the resources during the call. This can occur when they  
are Out of Service, busied out by craft, or in use by system  
maintenance. This drop reason can also occur if the DS1/MMI cable  
disconnects. If a resource problem exists when the call arrives, it gets a  
reorder (fast busy) and the MCU does not disconnected it.  
“Password” =The user entered a wrong password or the audio add-on  
user did not enter it within the specified time period. The audio add-on  
user has one attempt to enter a correct password and has about 10  
seconds between digits (inter-digit timing).  
“System” = MCU restarts (level 2) disconnect all calls.  
“UIN-Inv” The user enters an invalid User Identification Number.  
“Unknown” = The system cannot determine the disconnect cause.  
“Wrong Num” The MCPTR resources SDN cause value detects an  
incorrectly-dialed destination number. See “Dial-out” for details.  
“UCC” = The controller intentionally disconnects the endpoint.  
AC Num  
Administered Connection Number. (1–128) AC numbers further  
diagnose problems by combining status conference information with the  
status administered connection command, and data stored in error  
and alarm logs.  
Ports Trunk  
Ports Video  
Ports Aud  
The data endpoint used by the channel.  
The MMI port for the channel.  
If the endpoint type is not “UCC,” the VC audio encoder port (which is  
always paired to a decoder port) for the channel (only the first channel).  
appears together with the ESM data port in the endpoint’s channel 1  
port slot position of the Port Aud/ESMcolumn. For “UCC” endpoints,  
channel 1 port slot positions display allocated Call Classifier resources.  
Ports ESM  
Sum Grp  
Expansion Service Module MMI data port. This field defaults to blank.  
Endpoint’s assigned summer group number. The summer group port  
assignments are on screen 1.  
software  
For Lucent Technologies use only.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-251  
Field descriptions (status conference endpoint)  
The status conference x endpoint y command specifies that the conference is  
found. Data relevant for each endpoint displays in 6 pages. If technicians use the  
endpoint-ID all, every specified endpoint displays.  
Page 1 - Status Conference Endpoint  
status conference endpoint  
STATUS OF CONFERENCE ___  
Ext: _____ Type: ____  
page 1 of 6  
Status: ________  
Product: _____  
ENDPOINT: __  
Manufacturer/Country: ____/____  
Terminal Name: _______________  
Admin Bandwidth: ____  
Data Mode: _________ MLP Rate: ____  
Rate Adaptation: _  
Conf Bandwidth: ____  
Lo/Hi Interworking: _  
Meet-Me Number: ____________________  
Sum Grp: _ L1: ______ L2: ______  
Quadrature: ______ ________  
Dial Out #1: _______________________  
#2: _______________________  
ENDPOINT STATES/CAPABILITIES/MODES  
In Enh ----Capability---- Rate Bond  
Use BAS Chl Aud Vid Mlp Gx Adpt Mode Ts Vs  
-
-
-
-
-
- -  
-
-
-
-
Help line  
enter command:  
Screen 2-10. Page 1 of 6: status conference x endpoint y  
Field descriptions  
Endpoint  
Product  
Slot number associated with the endpoint on the conference forms.  
Product identification number obtained from the endpoint.  
Manufacturer/ Manufacturer identification number and manufacturer’s country code  
Country  
obtained from the endpoint.  
Terminal Name Blank.  
Sum Grp  
Endpoints belong to this Summer group number and the VC Audio  
Level (L1) and Level 2 (L2) summer ports for this group. These fields  
supply entries for conferences with over 6 participants.  
Dial Out #1  
Dial Out #2  
Blank  
Blank  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-252  
In Use  
Is the endpoint participating in the conference or connecting to the  
conference? - y, c, e, f, n, blank.  
“y” = The endpoint is in use and fully-connected on all media in an  
active conference.  
“c” = The endpoint is in use and fully-connected; however, the  
endpoint changes the conference audio or video capability, or the rate  
of the conference due to rate adaptation. This condition requires  
analysis of this endpoint’s capabilities and mode fields to identify the  
reduced capability.  
“e” = The endpoint active, but has capability problems. The endpoint  
lacks one of the required capabilities (Vid, Bhl, MLP) to be a full  
participant. For MLP capabilities, see the “T120” field. This condition  
requires analysis of this endpoint’s capabilities and mode field to  
identify the missing capability.  
“f” = The endpoint is active, but is not connected to all media. The  
endpoint declared all required capabilities (channel/video/  
audio/data) but is not fully-connected to all conference media. This  
endpoint may be connecting, failed to connect, or is not a valid video  
source. This condition requires analysis of this endpoint’s capabilities  
and mode fields to identify the problem.  
“n” = The endpoint connects then disconnects in a conference, or  
unsuccessfully attempts to connect to a conference.  
“blank” = Blank until the first call is made from or to the endpoint.  
Enh BAS  
Chl  
Enhanced Basic Service Flag - n, y  
“y” = The endpoint supports the enhanced BAS commands/caps;  
“n” = The endpoint supports the basic BAS commands/caps.  
Data on the quantify and quality of channels (transfer rate)? - y, e, n,  
blank  
“y” = The endpoint has the required number of channels.  
“e” = The endpoint does not declare support for the correct number of  
channels and cannot participate fully in the conference.  
“n” = The endpoint declares the correct number of channels, but not  
all channels join the conference, due to network or endpoint problems.  
“blank” = Audio add-on endpoints set the Chlfield to blank.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-253  
Aud  
Does it have the required audio capability? - y, c, e, blank  
“y” = The endpoint has the required audio capability. Audio add-on  
endpoints set the Aud field y when the endpoint joins the conference.  
“c” = This PCM-only endpoint changes conference video quality by  
changing the operating audio from G.728 to G.711. If the administered  
audio mode is auto and the administered bandwidth is 112 kbps (56  
k/channel) or 128 kbps (64 k/channel), the system begins with the  
highest common audio, G.728. When the administered bandwidth is  
greater than 128 kbps, the system begins with the highest common  
bandwidth, 7 kHz.  
“e” = A PCM-only endpoint that could not support the administered  
audio mode, G.728 (such as a data conference), or G. 278/G.711  
endpoint that could not support the administered audio mode, 7 kHz.  
Such endpoints operate with PCM audio and interwork with operating  
audio modes.  
“blank” = Blank until the first call is made from or to the endpoint.  
Vid  
Does it have required video capability and is it receiving video? - y, c,  
e, n, blank  
“y” = The endpoint has the required video capability and receives  
video if the Chl, Aud, and Dat fields are y.  
“c” = The endpoint downgrades the conference’s video quality from  
CIF to ACIF, or by decreasing the frame rate. The conference video  
mode defaults to CIF, and if a QCIF-only endpoint joins the  
conference, the entire conference operates in QCIF, with downgraded  
video clarity. The conference frame rate is initially set to the highest  
frame rate that can be reduced by any endpoint. If the conference  
video mode is not administered with upgrade capability, the video  
parameters for a conference downgrade. They do not upgraded until  
all endpoints disconnect from the conference.  
“e” = The endpoint does not declare video capability in its cap-set.  
“n” = Audio only, not receiving video, due to an audio or data problem.  
“blank” = Audio add-on endpoints set the Vid field to blank.  
Mlp  
Gx  
The relationship between the Control Link and the ESM (T.120 stack  
terminator), the endpoint MLP data capability, and the state of the  
data connection in the T.120 stack. This field defaults to blank,  
indicating that the Data Mode for the conference is none.  
“y” This endpoint has Still Frame Graphics capability.  
“e” = This endpoint did not have Still Frame Graphics capability. The  
conference retains still frame graphics capability when a  
non-compliant endpoint joins the conference.  
“blank” = This endpoint never joins the conference.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-254  
Rate Adpt  
Rate adaptation/Interworking indicator = 5, 6, y, c, e, n, blank. 5 and  
6 apply to Low Speed/High Speed Interworking. All other values apply  
to Rate Adaptation.  
“5”= 56-kbps (Low Speed) endpoints join High Speed (128 kbps or  
above) conferences. This endpoint connects with audio only  
capability, but is not a valid video source and destination.  
“6” = 64-kbps (Low Speed) endpoints join High Speed (128 kbps or  
above) conferences. This endpoint connects with audio only  
capability, but is not a valid video source and destination.  
“y” = This endpoint joins the conference at 64 kbps, but because  
another endpoint triggers rate adaptation to 56 kbps, this endpoint  
rate adapts to 56 kbps.  
“c” = 64 kbps endpoints join the conference at 56 kbps. The first 56  
kbps endpoint that joins 64 kbps rate adaptable conferences triggers  
rate adaptation (see Join Timebelow).  
“n” = Another endpoint triggers a 64-kbps conferences to rate adapt  
to 56 kbps. This endpoint joins the conference at 64 kbps, but  
encounters problems with rate adapting to 56 kbps. This endpoint  
may have audio and may be receiving video, but is not a valid video  
source.  
“blank” = No endpoint triggers rate adaptation. If this endpoint is  
active, it joins the conference at the administered bandwidth.  
Bond Mode  
Ts  
BONDing Mode - blank. This field is blank for calls that are not related  
to bonding.  
The talking state of the endpoint - t, m, M, S, blank.  
“t” = The endpoint detects voice energy (talking).  
“m” = The endpoint indicates that it is muted to the MCU. Endpoints  
may mute, but not send an indication to the MCU.  
“M” = UDD/CRCS Agent interface mutes the endpoint’s audio. M  
displays when both the endpoint and the UCC/CRCS Agent mute the  
endpoint audio.  
“S” = the solo-audio state set by UCC/CRCS Agent mutes the  
endpoint’s audio. While in solo-audio state, new endpoints joining the  
conference automatically mute.  
“blank” = The endpoint does not detect voice energy (talking).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-255  
Vs  
The MCU video state for this endpoint. a, b, B, c, i, r, R, s, S, u, U, v,  
blank.  
Quad-screen conferences = *appears before V values indicating that  
an endpoint belongs to the mixed image. A #appears before the V  
values indicating that an endpoint belongs to the mixed image (by  
administration or UCC/CRCS Agent). Instead, a Fillvideo displays  
in its place. This occurs when an endpoint’s video that is set in a  
quadrant cannot be used as a video source because the endpoint is  
not connected to the conference, suppresses its video, or has invalid  
video for its video source. Up to four endpoints have an *or #before  
the Vs field value.  
Quad-screen conference in VAS mode = The mixed image broadcasts  
to all endpoints. For quad-screen conference in presentation mode,  
the mixed image is return video to the presenter.  
“a” = This value applies to quad-screen conferences. *a indicates that  
an endpoint belongs to the current mixed image and is administered  
to one of the quadrants. *aindicates that the endpoint is fixed in a  
quadrant, but is not currently connected (Fill image displays).  
“b” = For full-screen conferences, this endpoint’s video broadcasts to  
other sites. This conference is in VAS, broadcast, or presentation  
mode. For quad-screen VAS conference are prefixed an asterisk  
indicating that this endpoint’s video is part of the mixed image  
because of VAS. For quad-screen presentation conferences, b  
identifies the presenter as the broadcaster.  
“B” = The UCC roll call feature causes the endpoint’s video to  
broadcast to other sites. The UCC roll call feature performs in  
full-screen mode.  
“c” = This endpoint’s video broadcasts to other sites. The conference  
was in chair mode and the chair designates the broadcaster. Chair  
features perform in full-screen mode.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-256  
Vs  
“i” = The endpoint is not a valid video source. For continuous  
presence conference, #i represents endpoints that are is fixed in a  
particular quadrant.  
(cont’d.)  
“r” For full-screen conferences, t he endpoint’s video is the return  
video to the broadcaster. For continuous presence conferences in  
presentation mode, *r represents a VAS quadrant that is part of the  
mixed image.  
“R” = The UCC browse feature causes the endpoint’s video to be the  
return video to the broadcaster. UCC Browse feature performs in  
full-screen mode.  
“s” = The endpoint suppresses its video. For continuous presence  
conferences with fixed quadrant participants, #s represents an  
endpoint that is fixed in a particular quadrant.  
“S” = UCC/CRCS Agent interface suppresses the endpoint’s video.  
For continuous presence conference with fixed quadrant participants,  
#s represents an endpoint that is fixed in a particular quadrant. S  
displays when both the endpoint and the UCC/CRCS Agent suppress  
the endpoint video.  
“u” = For full-screen conferences, this endpoint’s video broadcasts to  
other sites. The conference is in VAS mode and the UCC/CRSCS  
Agent interface designates the broadcaster. For quad-screen  
conferences, the UCC/CRCS Agent designates this endpoint as fixed  
in a quadrant. *u represents an endpoint that is part of the quad  
image, and #u represents a disconnected endpoint.  
“U” = For quad-screen conferences, UCC/CRCS Agents designate a  
quadrant as VAS. *Uindicates that this endpoint is part of the current  
quad image.  
“v” = This endpoint’s video broadcasts to other sites. The conference  
was in VAS mode, but the endpoint asks to be a broadcaster with the  
“See-Me” request and is granted a MCV (Multipoint Command  
Visualize) token. The See-Me feature performs in full-screen mode.  
“blank” = The endpoint’s video is not broadcast, return, video, or part  
of the mixed-image, but it is a valid video source.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-257  
Page 2 - Endpoint Channel Information  
This section describes fields specific to endpoint-level command output.  
status conference endpoint  
page 2 of 6  
ENDPOINT CHANNEL INFORMATION  
Chan. Join Drop ----Drop---- AC ------------Ports---------- Fr  
No. Time Time Reason Code Num Trunk Video Aud/ESM BONDng Err Software  
1: _____ _____ _________ __ ___ ______ ______ ______ ______ ___ ________  
2: _____ _____ _________ __ ___ ______ ______ ______ ______ ___ ________  
3: _____ _____ _________ __ ___ ______ ______  
4: _____ _____ _________ __ ___ ______ ______  
5: _____ _____ _________ __ ___ ______ ______  
6: _____ _____ _________ __ ___ ______ ______  
7: _____ _____ _________ __ ___ ______ ______  
8: _____ _____ _________ __ ___ ______ ______  
9: _____ _____ _________ __ ___ ______ ______  
10: _____ _____ _________ __ ___ ______ ______  
11: _____ _____ _________ __ ___ ______ ______  
12: _____ _____ _________ __ ___ ______ ______  
______ ___ ________  
______ ___ ________  
______ ___ ________  
______ ___ ________  
______ ___ ________  
______ ___ ________  
______ ___ ________  
______ ___ ________  
______ ___ ________  
______ ___ ________  
Help line  
enter command:  
Screen 2-11. Page 2 of 6: status conference x endpoint y  
Field descriptions  
Join Time  
Drop Time  
Time (in 24-hour notation) when the channel joins the conference.  
Time (in 24-hour notation) when the channel disconnects. If the first  
channel has a drop time, the endpoint is inactive. If a drop time occurs  
without a join time, the call disconnects without joining the conference.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-258  
Drop Reason  
Channels disconnect because:  
“2-pri” = Administration errors cause mismatches in primary-  
secondary designations for cascade links. This mismatch indicates that  
both MCUs are administered as primaries (see “Cascading” for a  
description of primary-secondary compatibility).  
“2-sec” = Administration errors cause mismatches in primary-  
secondary designations for cascade links. This mismatch shows that  
both MCUs are administered as secondaries (see “Cascading” for a  
description of primary-secondary compatibility).  
“Agent” = Reservation agents cause calls to disconnect (for example,  
agents change connected dial-out destination numbers).  
“Bandwidth” = Mismatches occur when bandwidths of calls and the  
conferences they attempt to join are inconsistent.  
“BondHshake” = Unsupported Information channel parameters or  
invalid, parameter negotiations that terminate out of sequence, timers  
that expire because secondary channels do not establish, or BONDing  
framing that goes undetected for another channels.  
“Busy” = The MCU detects that the conferee’s terminal equipment is  
busy. An ISDN cause value detects this drop reason (for example h0).  
See “Dial-out” for a description of CPTR usage.  
“Chair” = Chair Command Disconnect (CCD) or Chair Command Kill  
(CCK) signals disconnect the endpoint.  
“Conf End” = The conference ends when the stop time is reached for a  
reserved conference or an active conference converts to file.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-259  
Drop Reason  
“Endpoint” = Clearing received from DS1. The endpoint initiates the  
disconnect. The endpoint notifies the MCU that it intends to disconnect.  
(cont’d)  
“Far-end” = Clearing received from DS1. The network or endpoint  
initiate the disconnect.  
“Handshake” = Framing is never found or is lost for over 40 seconds  
and the endpoint is disconnected. (the endpoint could not complete  
initialization due to problems with finding Frame Alignment Signal  
(FAS), Multi Frame Alignment (MFA) and corrected coded cap-sets)  
“IDtimeout” = The H3.20 user unsuccessfully (three times) sends MCU  
responses regarding the UIN/password Query. Each timeout period is  
administered.  
“Internal” = MCU has a problem allocating the necessary trunk  
resources to route dial-out calls for specified dial-numbers. This  
problem is associated with routing patterns or trunk-associated  
translation (for example, TAC specified in the dial-out number or routing  
pattern points to a trunk group without members), or indicates a lack of  
trunk resources (for example, all trunk members are maintenance busy  
or all in-service members are busy on a call).  
“Network” = Clearing received from DS1. The disconnects the  
endpoint. The endpoint with the disconnect notification capability  
disconnects without notifying the MCU.  
“Not-MCU” = The dial-out destination numbers of the “CAS” extensions  
terminate to numbers that are not dial-in cascade MCU extensions.  
“No-ring” = The is up for 30 seconds and no ringing is detected.  
“Reorder” The MCU CPTR resources detect that no network trunks are  
available to place the call. See “Dial-out” for a description of CPTR  
usage.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-260  
Drop Reason  
“Pre-AnsDrop” = The call disconnects an endpoint answers. The  
(cont’d)  
network, an endpoint, or a terminal adapter may cause the disconnect.  
This drop reason differs from ‘No-answer,’ which indicates that a  
60-second timeout occurs during alerting. In this case, the call drops  
before the 60-second timer expires. Some busy endpoints that are  
connected through terminal adapters display this behavior.  
“Resource” = MCU cannot provide resources (VC or MMI) when calls  
arrive or lose their resources during the call. Calls can lose resources  
when they are Out of Service, busied out by craft, or in use by system  
maintenance. If the DS1/MMI cable is disconnected, this drop reason  
can also occur. If a resource problem exists when the call arrives, it  
gets reorder (fast busy) and is not disconnected by the MCU.  
“Password” = The user enters a wrong password or the audio add-on  
user does not enter it within the specified time period. The audio  
add-on user gets one attempt to enter a correct password and has  
about 10 seconds between digits (inter-digit timing).  
“System” = MCU restarts (level 2) disconnect all calls.  
“UIN-Inv” = Users enter invalid User Identification Numbers.  
“Unknown” = The system cannot determine the disconnect cause.  
“Wrong-num” = The MCU CPTR resources SDN cause values detect an  
incorrectly-dialed destination number. See “Dial-out” for details.  
“UCC” = The controller intentionally disconnects the endpoint.  
Drop Code  
AC Num  
A detail code complementing the Drop Reason. Additional  
bonding-related information is available from the supplementary  
BONDing Drop Codes described above.  
Administered Connection Numbers. (1–128) AC numbers can further  
diagnose problems by combining status conference information with  
the status administered connection command, and data stored in the  
error and alarm logs.  
Ports Trunk  
Ports Video  
Ports Aud  
The data endpoint that the channel is using.  
The MMI port for the channel.  
If the endpoint type is not “UCC,” the VC audio encoder port (which is  
always paired to a decoder port) for the channel (only the first channel).  
appears together with the ESM data port in the endpoint’s channel 1  
port slot position of the Port Aud/ESMcolumn. For “UCC” endpoints,  
the channel 1 port slot position displays allocated Call Classifier  
resources.  
Ports ESM  
Ports BONDng  
Fr Err  
Expansion Service Module MMI data port. This field is always blank.  
The MMI port used for channel BONDing.  
Frame error counter. A circular hex counter (0-FF) to indicates framing  
error occurrences.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-261  
Page 3 - Conference Information  
This section describes fields that are specific to endpoint-level command output.  
status conference endpoint  
page 3 of 6  
CONFERENCE INFO: Broadcaster: xx (See-Me)  
Return Vid: xx  
---------- MODE COMMANDS/COMMUNICATION MODES ------| EPT MISC  
| ------- FAW --  
CMD STAT  
CONF  
EPT-IN  
EPT-OUT  
|------ I O |  
CH1 CH2  
--- ---  
----- ---- ------------ ------------- -------------| AIM: y n |  
XRATE: y  
AUDIO: n  
56/64: y  
VIDEO: n  
MLP: y  
H-MLP: y  
LSD: y  
HSD: y  
384  
G728  
384  
384  
G728  
| VIS y n | A-OUT: y  
n
n
n
n
n
n
neutral  
derestrict  
H.261  
MLP-off  
H-MLP-off  
LSD-off  
HSD-off  
| MIS:  
| MCV: n  
n | A-IN: y  
| M-FRM: y  
derestrict  
H.261  
MLP-off  
H-MLP-off  
LSD-off  
HSD-off  
derestrict  
H.261  
MLP-off  
H-MLP-off  
LSD-off  
HSD-off  
|-------------|  
| TALK: y 05 |  
| VFCV: y 01 |  
MFA: y  
MFN: y  
FAS: y  
| BCTK: n 02 |MCUFAL: 00 00  
| RTTK: y 01 | FEFAL: 00 00  
CRYPT: y  
S/M: y  
encrypt-off encrypt-off  
N-comp-6B-H0 N-comp-6B-H0 N-comp-6B-H0 | RTLS: n  
encrypt-off | BCLS: n  
|
|
| HYPR: n 00 |  
|DMUTE: n 00 |  
|H.261: n 00 |  
| VFMT: n 00 |  
Help line  
enter command:  
Screen 2-12. Page 3 of 6: status conference x endpoint y  
Conference Info. This information primarily applies to full-screen conferences.  
The Broadcasterfield applies to quad-screen presentation mode conferences.  
Field descriptions  
Broadcaster  
The current broadcaster endpoint number. The following keywords  
qualify the broadcaster:  
“Broadcast” = A broadcast mode broadcaster.  
“Chair” = The chair designates the broadcaster.  
“See-Me” = The endpoint initiates a MCV broadcaster request.  
“Presenter” = A presentation mode broadcaster.  
“Rollcall” = The UCC designates the broadcaster by the Rollcall  
feature.  
“UCC” = The UCC designates the broadcaster.  
“VAS” = A Voice Activated Switching broadcaster.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-262  
Next  
The endpoint number that is selected to be the next broadcaster.  
Broadcaster  
Return Vid  
The endpoint number that is the current return video. The return video  
is qualified with the following keywords:  
“blank” = VAS, Chair action, UCC action, or endpoint MCV requests  
force the previous broadcaster to be the return video. The  
broadcaster qualifier identifies the action that forced this endpoint to  
become return video.  
“Autoscan” = Auto scan return video, when conference mode  
broadcasts with auto scan.  
“Browse” = The UCC designates the return video with the Browse  
feature.  
“VAS” = A Voice Activated Switching return video.  
Next Return  
Vid  
Indicates the endpoint number selected to be the next return video.  
Mode Commands/Communication Modes. This is a collection of incoming and  
outgoing bandwidth allocations for the multiplex. The Incoming data is the rate at  
which the MCU thinks the endpoint is communicating based on the Bit-rate  
Allocation Signal (BAS) codes received from the endpoint/codec and the  
capabilities the MCU has declared. The Outgoing data is the rate from the MCU  
toward the endpoint. The following are column definitions for this section of  
page 3.  
Field descriptions  
CONF  
The desired conference operating mode. This may differ from the  
endpoint in (EPT-IN) or endpoint out (EPT-OUT) modes.  
CMD  
Labels for the various types of mode commands  
STAT  
Conference and incoming mode compatibility.  
“y” = mode compatibility  
“n” = modes incompatibility.  
EPT-IN  
defines the communication modes coming in from an endpoint.  
EPT-OUT  
Defines the communication modes sent to an endpoint based on the  
number of connected channels and the endpoint’s capabilities.  
The following are field definitions for the Mode Commands/Communication  
Modes section of Page 3.  
XRATE  
One of the supported rates in Table 2-4:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-263  
Table 2-4. Supported Transfer Rates s  
XRATE  
2x64  
128  
Bandwidth of the Call  
2B (2x56 or 2x64)  
112kbps or 128kbps  
168kbps or 196kbps  
224kbps or 256kbps  
280kbps or 320kbps  
336kbps or 384kbps  
512kbps  
196  
256  
320  
384  
512  
768  
768kbps  
1472  
1536  
1920  
1472kbps  
1536kbps‘  
1920kbps  
XRATE  
XRATE may be 64 when the endpoint dials in, or in the event that  
problems occur. It implies that only one B channel is in use.  
(cont’d.)  
AUDIO  
Conference and endpoint Audio rates (kbps bandwidth) must be the  
same. Their modes are not necessarily the same. When the audio  
rate of the conference and the endpoint differ, the endpoint’s audio  
interworks, but the endpoint’s video is invalid. MCU may or may not  
send video to such an endpoint.  
Table 2-5 summarizes expected endpoint audio modes with different  
transfer rate configurations, facility bandwidths, and conference  
modes. It includes endpoints that support the highest common audio  
mode (HC audio) when the administered mode is auto. The highest  
common conference mode depends on the administered bandwidth.  
A ‘-’ in the table indicates ‘does not apply.’  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-264  
Table 2-5. Audio Mode Configurations  
All  
Admin Mode  
(HC Audio)  
Support  
HC Audio  
Xfer  
Rate  
Facility  
BW  
Conf Mode  
G.728  
Expected Endpoint Mode  
auto (G.728)  
auto (G.728)  
auto (G.728)  
auto (G.722)  
auto (G.722)  
G.728  
yes  
<=128k  
-
G.728  
no  
no  
-
<=128k  
64k  
56k  
64k  
56k  
G.711-A-56k  
G.711-A-48k  
G.722-56k  
G.722-48k  
G.728  
G.711-A-56k B.711-Mu-56k  
<=128k  
G.711-A-48k G.711-MU-48k  
G.722-56k G.711-A-56k G.711-Mu-56k  
G.722-48k G.711-A-48k G.711-Mu-48k  
G.728  
>128k  
-
>128k  
-
-
-
-
-
-
G.711  
-
64k  
56k  
64k  
56k  
G.711-A-56k  
G.711-A-48k  
G.722-56k  
G.722-48k  
G.711-A-56k G.711-Mu-56k  
G.711-A-48k G.711-Mu-48k  
G.722-56k G.711-A-56k G.711-mu-56k  
G.722-48k G.711-A-48k G.711-Mu-48k  
G.711  
-
G.722  
-
G.722  
-
AUDIO  
(cont’d.)  
Other possible AUDIO mode values include neutral(neutralized  
I-channel), Au-off, and Frm(no audio signal) which never match  
conference modes and are unsupported by MCU.  
56/64  
The 65/64field derestricts when operating at 64kbps, 128kbps,  
192kbps, 256kbps, 320kbps, 384kbps, 512kbps, 768 kbps,  
1472kbps, 1536kbps, or 1920kbps per channel speeds; it  
restrictswhen operating at 56kbps, 112kbps, 168kbps, 224kbps,  
280kbps, 336kbps, 448kbps, and 672kbps per channel speeds.  
If technicians configure the conference for Nx56kbs operations,  
endpoint may signal by capabilities or modes that operate at the  
proper rate. In such a case, when technicians receive derestrict  
commands while they are in the restrictmode, that do not match  
conference communication modes, (MISCcapability has restrict  
displayed on Page 4) the STAT 56/64is yindicating 56/64  
compatibility between the conference and the endpoint.  
VIDEO  
The Video mode: H.261(recommended), H.CTX(proprietary),  
H.CTX+ (proprietary), or SG4(proprietary) indicate that video is on in  
the direction indicated; and video-offwhen the video is off.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-265  
MLP  
Multi Layer Protocol data mode. When technicians administer Data  
Modesas any-mlpor ww-pcs, MLP modes should be var-MLP.  
Other values affect video status.  
MLPmodes should be MLP-offwhen technicians administer Data  
Modes as none. Other values in this mode affect video status.  
H_MLP  
LSD  
The High Speed MLP mode. The HMLP mode should be H-MLP-off.  
Other values in this mode will affect video status.  
Low Speed Data mode. The LSD mode should be LSD-off. Other  
values in this mode affect video status.  
HSD  
High Speed Data mode. The HSD mode should be HSD-off. Other  
values in this mode affect video status.  
CRYPT  
S/M  
Encryption mode. The CRYPT mode should be encrypt-off. Other  
values in this mode affect video status.  
Single/Multi channel interoperability mode. 6B-H0-compindicates  
that the sender is interoperating multiple channels and a single  
channel (for example, 6B and H0). Not-comp-6B-H0indicates that  
the sender is not interoperating between 6B and H0. Normally this  
value is Not-comp-6B-H0. Other values in this mode affect video  
status.  
Endpoint Miscellaneous (EPT MISC) Information. EPT MISC contains  
miscellaneous states and counters for an endpoint. Flags can yor n. Counters  
start with 0x00, increment to 0xff, and wrap around to 0x01. AIMand VISare  
BAS commands that can be sent as input to MCU from an endpoint or as output  
from MCU to an endpoint  
Field descriptions  
AIM  
Audio Indicate Mutes.  
“y” = For input, this endpoint mutes its audio. MCU does not VAS to an  
endpoint displaying mute. For output, all other endpoints in the  
conference mute their audio (have sent AIM to MCU). MCU in turn tells  
this endpoint (by sending it AIM) that there is no audio output from  
MCU.  
“n” = For input, this endpoint does not mute (only if endpoint audio  
mode is turned on). For output, an audio path opens across the bridge.  
VIS  
Video Indicate Suppressed.  
“y” = For input, this endpoint suppresses its video (video is muted). For  
output, the MCU is not sending video to this endpoint because there is  
no video broadcaster (broadcaster does not join or broadcaster’s video  
is invalid).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-266  
MIS  
Multipoint Indicate Secondary-status.  
“n” = For output, the endpoint is a valid source (not necessarily at this  
moment). n is the correct state for the video.  
“y” = MIS was sent to an endpoint considered to be a secondary  
endpoint. The endpoint is included in the audio, but not video portion of  
the conference. Video is not sent.  
MCV  
Multipoint Command Visualize.  
“y” = For input, an endpoint requests to become a broadcaster. This is  
used during Still Frame Graphics and to force “presentation” mode.  
TALK  
VRCV  
“y” = The VC board detects voice energy from the endpoint. The TALK  
counter indicates the number of starts or stops.  
“y” = The endpoint is receiving video (MCU is sending video to the  
endpoint). The VRCV counter counts the number of times video sends  
or does not send to this endpoint.  
BCTK  
RTTK  
Single screen and quad-screen presentation mode conferences.  
“y” = The endpoint is the video broadcast source. The BCTK counter  
tallies the number of times this endpoint is the video broadcast source.  
Single screen conferences.  
“y” = The endpoint is the return video source. The RTTK counter tallies  
the number of times this endpoint is the return video source.  
BCLS  
RTLS  
HYPR  
Single and quad-screen presentation mode conferences.  
“y” = The endpoint is watching the video of the broadcast source.  
Single screen conferences.  
“y” = The endpoint is watching the video of the return source.  
“y” = Endpoint hyperactivity (MCU isolates endpoints from the MMCH  
conference due to “thrashing” behavior) affects the endpoint’s status as  
a video source (for 5 seconds of hyperactivity timer). The HYPR counter  
tallies the number of times this endpoint is hyperactive.  
DMUTE  
“y” = The VC board or the software in the MCU mute the decoder. VC  
boards mutes the decoder when it loses MMI or endpoint framing, when  
it receives invalid audio code words, and when endpoints are  
hyperactive. MCU software mutes the endpoint decoder of all  
endpoints besides the broadcaster. (when a mode of a conference is  
“broadcastw/scan”,broadcast with auto scan) The DMUTE counter  
tallies the number of times the VC board mutes this endpoint’s decoder.  
VFMT  
Quad-screen conferences. This field always defaults to n, indicating  
QCIF format.  
H.261  
“y” = Video framing loss. The H.261 counter tallies the number of times  
framing is lost.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-267  
Frame Alignment Word (FAW) Information. The FAW section of page 3  
provides channel Frame Alignment Word information for the communication  
paths labeled CHL 1 and 2. For 2B calls, both CHL 1 and 2 are used. For  
1-channel calls (112,bps, 128kbps, 168kbps, 196kbps, 224kbps, 256kbps,  
280kbps, 320kbps, 336kbps, 384kbps, 768kbps, 1472kbps, 1536kbps, and  
1920kbps) only CHL 1 is used. A-OUT, A-IN, M-FRM, MFA, and MFNare flags with  
yor n.  
Field descriptions  
A-OUT  
A-IN  
M-FRM  
MFA  
MCU has endpoint framing.  
Endpoint has MCU framing  
Multichannel frame alignment of both channels in 2B is present.  
Multiframe alignment word is present (required in 2B call).  
Multiframe numbering is present (required in 2B call).  
MFN  
FAS  
Frame Alignment Signal (FAS) channel number (1 or 2). This number  
should match the column header.  
MCUFAL  
MCU Frame Alignment Loss (MCUFAL). Counts the number of times  
the MCU reports lost endpoint FAW or multichannel synchronization  
(M-FRM) to the endpoint. The MCU a-bit toggles when the MCU gains  
or loses endpoint multichannel synchronization. This counter starts with  
0x00, increments to 0xff, then wraps around to 0x01. The MCUFAL  
count also displays in the Fr Errfield on Page 2  
FEFAL  
Far End Frame Alignment Loss (FEFAL). Counts of the number of  
changes the MCU detects in the endpoint’s a-bit (A-OUT). The  
endpoint a-bit toggles when an endpoint gains or loses MCU framing.  
This counter starts with 0x00, increments to 0xff, then wraps around to  
0x01.  
Page 4 - Endpoint Capability Information  
This section describes fields specific to endpoint-level command output.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-268  
status conference endpoint  
page 4 of 6  
ENDPOINT CAPABILITY INFORMATION  
--------------------------------------------------------------------------------  
VID | vfmt: QCIF  
| da_sfg  
cmpi: 30  
qmpi: 7.5  
H.CTX  
H.CTX+  
SG4  
SG4_sfg  
imp  
-----|--------------------------------------------------------------------------  
MISC | derestrict S/M mbe dcomp cic  
-----|--------------------------------------------------------------------------  
XR | 64 64x2 64x3 64x4 64x5 64x6  
384  
384x2  
384x3  
1536  
384x4  
1920  
384x5  
|
128 192 256 320 512 768 1152 1472  
-----|--------------------------------------------------------------------------  
AUD | ntrl 711m 711a g728 g722_64 g722_48  
-----|--------------------------------------------------------------------------  
LSD | var 300 1200 4800 6400 8000 9600 14.4k 16k 24k 32k 40k 48k 56k 62.4k 64k  
-----|--------------------------------------------------------------------------  
HSD | var 64k 128k 192k 256k 320k 348k 512k 768k 1152k 1536k  
-----|--------------------------------------------------------------------------  
MLP | var 4k 6.4k 14.4k 16k 22.4k 24k 30.4k 32k 38.4k 40k 46.4k  
-----|--------------------------------------------------------------------------  
HMLP | var 62.4k 68k 128k 192k 256k 320k 384k  
--------------------------------------------------------------------------------  
62.4k  
Screen 2-13. Page 4 of 6: status conference x endpoint y  
Endpoint Capability Information. Fields on this page display if an endpoint  
declares specific capability. For example, if an endpoint does not declare VID  
H.CTX capability, the H.CTXfield does not display.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-269  
Field descriptions  
VID  
Video and frame rate types that the endpoint supports.  
“vfmt” = Does not display if the endpoint has no video capability. All  
values are blank if an active call or audio-only endpoint exists.  
Otherwise, values for this field include:  
■ FCIFfor full CIF  
■ QCIFfor quarter CIF. CIF support implies QCIF support. For  
larger screens, CIF typically displays sharper resolution video,  
ZCIF is blocked, but may run at higher frame rates with less  
clarity. Differences are less observable on very small displays.  
■ cfpsand qfpsare maximum frame rates (frames/second) that  
the endpoint can receive video for CIF and QCIF operating  
modes. CIF frame rate values are 30fps, 15fps, 10fps, and 7.4fps.  
If the endpoint does not support CIF (that is, the vfmt field is  
QCIF), the cfpsvalue should be blank.  
■ da_sfgindicates support for H.261 Still Frame Graphics  
transfers.  
■ H.CTX, H.CTX+and SG4are proprietary video format  
capabilities.  
■ SG4_sfgindicates support for SG4 Still Frame Graphics  
MISC  
The restrictfield and the 56/64command mode with a  
restrictvalue indicate that endpoints operate at 56 kbps per  
channel. Endpoints on 56 kbps conferences must send one or both 2  
indications that they are operating at 56 kbps before they become a  
video source in a 56 kbps conference. If they signal that they are  
operating at 56 kbps in a 64 kbps or 384 kbps conference, they  
become an audio-only source, but the MCU continues to send  
Selected Communication Mode (SCM) toward them when possible.  
A MISC capability of derestrictand a 56/64 command of  
derestricttogether indicate that an endpoint operates at 64 kbps.  
If either is restrict, the conference operates at 56 kbps. Other field  
values include:  
■ dcompindicates support for WorldWorx PCS data compliance.  
■ mbeindicates support for Multi Byte Extension. MBE exchanges  
passwords, terminal names, and other special capabilities, such  
as, WorldWorx PCS specific features support.  
■ cic(Chair Indicate Capability) indicates chair control capability.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-270  
XR  
Transfer rate capabilities. Endpoint speeds over current connections  
and Px64 Multiplexes.  
For 384 kbps (H0) calls, endpoints indicate 384 kbps support, that  
displays as 384. On 336 kbps calls, endpoints must signal 384 kbps  
support. If an endpoint does not indicate support for 384 kbps on a  
384/336 kbps conference, the MCU provides Audio Only  
Communications Mode (ACOM). For a 2B conference, the MCU sets  
the rate to 2x64, expecting the endpoints to do likewise (64x2  
displays; if this is not displayed, no 64x2 capability exists). Endpoints  
may remove 2x64 (or the current channel rate: 384, 768, 1472, 1536)  
from their capability. This is Mode 0 forcing and is a normal  
procedure. The MCU provides AOCM if the endpoint does not signal  
support that matches the conference configuration.  
AUD  
Audio. Audio protocols that the endpoint supports. 711mand 711a  
are PCM (G.711) and support Mu and A-law, respectively. Endpoints  
require at least one. The g728 field indicates if G.728 is supported  
(LB_CELP). This value depends upon the endpoint type and  
configuration. The g722_48 field indicates endpoint support for G.722  
(7 kHz) at both 48 kbps and 56 kbps. The g722_64field indicates  
endpoint support for G.722 at 64 kbps in an unframed (unsupported  
by the MCU) mode.  
LSD  
HSD  
MLP  
Low Speed Data conferencing capabilities.  
High speed Data conferencing capabilities.  
Multi Layer Protocol Data capabilities.  
HMLP  
High Speed MLP data conferencing capabilities.  
Page 5 - Endpoint Call Status Information  
This page summarizes call-related status for per-channel join counts, join/drop  
times, drop reasons, drop codes, and auxiliary bonding drop codes. In addition,  
it contains drop codes and software fields from the previous call. The data on the  
page is retained. The Endpoint Call Status Information section groups all  
call-related fields. The only new field in this section is Join Count; all other  
fields are described in Screen 2-10 and Screen 2-11.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-271  
status conference endpoint  
page 5 of 6  
ENDPOINT CALL STATUS INFORMATION  
Join  
Join Drop  
-------------- Drop --------  
--- Previous -----  
DropCode Software  
Chan Count Time Time  
Reason  
Code  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
BondCode  
__  
1: __  
2: __  
3: __  
4: __  
5: __  
6: __  
7: __  
8: __  
9: __  
10: __  
11: __  
12: __  
_____ _____ __________  
_____ _____ __________  
_____ _____ __________  
_____ _____ __________  
_____ _____ __________  
_____ _____ __________  
_____ _____ __________  
_____ _____ __________  
_____ _____ __________  
_____ _____ __________  
_____ _____ __________  
_____ _____ __________  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
________  
________  
________  
________  
________  
________  
________  
________  
________  
________  
________  
________  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
Screen 2-14. Page 5 of 6: status conference x endpoint y  
Field descriptions  
Join Count  
Tallies the number of times this endpoint joins this conference during  
this session. This counter starts with 0, increments to 64, and wraps  
around back to 1.  
Page 6 - Administered Connections  
This page summarizes information for administered connections associated with  
this endpoint. This data can be viewed while the conference is active.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-272  
status conference endpoint  
page 6 of 6  
ADMINISTERED CONNECTIONS INFORMATION  
AC  
Retry  
Count  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
Failure  
Cause  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
__  
Chan Num Dial-out Number  
1: ___ _____________________  
2: ___ _____________________  
3: ___ _____________________  
4: ___ _____________________  
5: ___ _____________________  
6: ___ _____________________  
7: ___ _____________________  
8: ___ _____________________  
9: ___ _____________________  
10: ___ _____________________  
11: ___ _____________________  
12: ___ _____________________  
Connection State  
_____________________  
_____________________  
_____________________  
_____________________  
_____________________  
_____________________  
_____________________  
_____________________  
_____________________  
_____________________  
_____________________  
_____________________  
__  
__  
Screen 2-15. Page 6 of 6: status conference x endpoint y  
Field descriptions  
Dial-out number  
Numbers that are dialed out by administered connections for each  
channel in the call. The dial Out #1 and #2 on page 1 of the forms  
display the DCP endpoint number. This is particularly useful with  
bonding dial-out calls.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-273  
Connection  
State  
The call state of the AC. The following are connection states  
associated with dial-out ACs:  
“enabled” = Transient in nature indicating that an AC is about to  
enter the “attempting to connect” state.  
“disabled” = one of three options:  
■ The AC reaches an administered retry threshold, and all retries  
are stopped. To verify this, check the Error Log to see if an error  
type of 9is logged against the AC.  
■ The AC is in a connected state with the far end disconnected.  
■ The initial channel call is not connected. No dial out call attempt  
is made for the additional channels until the initial channel has  
reaches a connected state.  
“not scheduled” = Transient in nature, indicating that an AC is about  
to enter the “attempting to connect” state.  
“waiting to retry” = The AC is inactive, waiting for the retry timer to  
expire. Once the timer expires, the AC sends a dial out call and  
enters the “attempting to connect” state. In this state, dial out calls  
fail at least once.  
“attempting to connect” = The AC is active, but has not connected.  
“connected” = The call associated with the AC is answered and joins  
cut-thru to the conference.  
Retry Count  
Tallies the attempted retries for this AC during join attempts and does  
not clear when the AC connects. However, it clears when the Redial  
feature attempts a new join. This differs from the Join Countwhich  
counts the number of times the channel joins the conference during  
this conference session.  
Failure Cause An ISDN or CPTR cause value (values lower than 0x7f) records when  
the last dial out call drops. Values above 0x7f are generated  
internally. Table 2-6 lists all possible failure cause values displayed  
by this field and its associated description. The Failure Cause  
value logs in the Error Log and displays with the display errors  
command. (Err Typeis normally displayed as a decimal.)  
Table 2-6. Status AC - Failure Cause Values  
Failure Cause  
(hexadecimal)  
0x00 (0t0)  
Description  
N/A  
0x01 (0t1)  
Incorrect destination address  
Reason unknown  
0x02 (0t2)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status conference  
2
2-274  
Table 2-6. Status AC - Failure Cause Values — Continued  
Failure Cause  
(hexadecimal)  
Description  
Reason unknown  
0x06 (0t6)  
0x10 (0t16)  
0x11 (0t17)  
0x12 (0t18)  
0x15 (0t21)  
0x12 (0t22)  
0x1C (0t28)  
0x1D (0t29)  
0x1F (0t31)  
0x22 (0t34)  
0x26 (0t38)  
0x29 (0t41)  
0x2A (0t42)  
0x2C (0t44)  
0x32 (0t50)  
0x34 (0t52)  
0x36 (0t54)  
0x3A (0t58)  
0x41 (0t65)  
0x42 (0t66)  
0x45 (0t69)  
0x51 (0t81)  
0x52 (0t82)  
0x58 (0t88)  
0x60 (0t96)  
0x61 (0t97)  
0x62 (0t98)  
0x64 (0t100)  
0x66 (0t102)  
0x7f (0t127)  
Normal call clearing  
Endpoint not available  
ISDN timer expired  
Reason unknown  
Destination address changed  
Bad destination or access denied  
Access denied  
Reason unknown  
Trunks unavailable  
Temporary or facility failure  
Temporary or facility failure  
Resources unavailable  
Resources unavailable  
Access denied  
Access denied  
Access denied  
Resources unavailable  
Required capability not implemented  
Required capability not implemented  
Required capability not implemented  
ISDN protocol error  
Required capability not implemented  
Incorrect destination number  
ISDN protocol error  
ISDN protocol error  
ISDN protocol error  
ISDN protocol error  
ISDN timer expired  
Reason unknown  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status data-module  
2
2-275  
Table 2-6. Status AC - Failure Cause Values — Continued  
Failure Cause  
(hexadecimal)  
Description  
Ring no answer  
0xC2 (0t194)  
0xC8 (0t200)  
0xC9 (0t201)  
0xCA (0t202)  
Hi and dry - no feedback detected  
Cascade link administered wrong  
CPTR not available to detect failure  
status data-module  
This command displays internal software state information that can help locate  
facilities to which the data module is communicating.  
Feature  
Action/Object  
Qualifier  
extension  
print  
Qualifier Description  
Data module extension  
Report sent to printer  
Permissions  
Defaults  
Interactions  
busyout mis  
init  
inads  
craft  
none  
none  
cust  
rcust  
bcms  
browse  
Output  
The following example shows the output from the status data-module 301  
command.  
status data-module 301  
DATA-MODULE STATUS  
Data Ext/Stn Ext for Stn DM: 301  
Port/Channel Number: 01C1103  
CF Destination Ext:  
Service State: out-of-service  
Maintenance Busy? no  
Connected Ports:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status esm  
2
2-276  
Field descriptions  
Data Ext/Sta Ext  
for Stn DM  
The data module extension number. The DTDM is an exception: the  
connected station extension is shown.  
Port/Channel  
Number  
The port location of the data module (cabinet-carrier-slot-circuit). If  
the data module specified is a data channel, the channel number  
will be shown instead.  
Service State  
This entry displays the status of the data module; valid states are:  
— In-service/idle  
— The data module is present but not in use.  
— In-service/active  
— The data module is present and is in use.  
— Out-of-service  
— The data module has been removed from service  
— Disconnected  
— The data module no longer appears to be present  
CF Destination Ext  
This entry displays the call forwarding destination, if any, of the  
station.  
Maintenance Busy?  
Connected Ports  
Whether maintenance is testing the object, “yes” or “no”.  
Port locations to which the data module is connected  
(cabinet-carrier-slot-circuit).  
status esm  
This command displays the link status and equipment and software revision  
identifiers for the Expansion Service Module (ESM). See in for more information.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status esm  
init  
none  
none  
inads  
craft  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status hardware-group  
2
2-277  
Output  
The following output example is a display of the status esm command.  
status esm  
page 1 of 1  
SYSTEM STATUS ESM  
Link Status: up  
VINTAGE  
RMB Product ID: NA  
MSM Interface Card Vintage: 5.3.d  
UNIX System Revision SNumber: 1.1.4  
ESM Software Revision Number: ESM.4.2.07  
State of ESM Process Manager: 1  
status hardware-group  
This command displays summary information for the active or last hardware  
group test. This display includes the number and percentage of tested  
maintenance objects, the percentage of tests passed, failed, and aborted, the  
time elapsed since initiating the hardware group test, the specific hardware  
group test command (see ‘‘test hardware-group’’ command) initiated, and the  
state (active/canceled/complete) of the hardware-group test.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
print  
Report sent to printer  
init  
none  
none  
hardware-group  
inads  
craft  
cust  
rcust  
bcms  
browse  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status hardware-group  
2
2-278  
Output  
The following example shows the output from the status hardware-group  
command.  
status hardware-group  
HARDWARE GROUP STATUS  
page 1 of 1  
Hardware Group Command State:  
Number of MOs Tested:  
Total Number of MOs to be Tested:  
Percent Complete:  
active  
11070  
12300  
90%  
Elapsed Test Time (hr:min:sec): 0:15:30  
Repetition Number:  
Percentage of Tests Passed:  
Percentage of Tests Failed:  
Percentage of Tests Aborted:  
1
82%  
11%  
7%  
ENTERED HARDWARE GROUP COMMAND  
Command: test hardware-group system  
Test sequence: short  
Test repetition: repeat 3  
Output Options: failures  
Hardware Options: SPE-interchange  
Field descriptions  
Hardware Group Command  
State:  
“active” = testing in progress, “canceled” = testing canceled,  
“complete” = command completed; no testing occurring.  
Number of MOs Tested:  
Number of MOs in the specified group (refer to test  
hardware-group command) that the hardware-group command  
tests, including MOs that were tested or aborted due to resource  
contention.  
Total Number of MOs to be  
Tested:  
Number of MOs in the group specified in the test  
hardware-group command.  
Percent Complete:  
Elapsed Test Time:  
Ratio of the completed MOs to the MOs to test in the command.  
Tracks completion time for the hardware-group command. If a  
test cancels and then restarts, the time for the cancel period is  
excluded. (HH:MM:SS)  
Repetition Number  
Number of completed iterations that correspond to the ’repeat’ or  
’continuously’ option.  
Percentage of Tests  
Passed:  
Percentage of tests that passed.  
Percentage of Tests  
Failed:  
Percentage of tests that failed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status health  
2
2-279  
Percentage of Tests  
Aborted:  
Percentage of aborted tests  
Command:  
Hardware-group action objects and qualifiers.  
Short or long.  
Test sequence:  
Test repetition:  
Displays continuously or the keyword repeats with the entered  
repeat value.  
Output options:  
Selections that were chosen on the input form: auto-page,  
background, or failures.  
Hardware options:  
Selections that were chosen on the input form: all-ports, or  
SPE-interchange.  
status health  
This command displays the current system alarm summary, maintenance busy  
summary, user summary, critical system status, and cabinet status. This same  
page displays with the monitor health command, except that the status health  
output page does not update periodically.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status health  
print  
Report sent to printer  
init  
none  
none.  
inads  
craft  
cust  
nms  
browse  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status health  
2
2-280  
Output  
The following example shows the output from the status health command.  
status health  
ALARM SUMMARY  
CABINET STATUS  
Major:  
Minor:  
Warning:  
0
2
0
Emerg Alarms  
Cab Trans Mj Mn Wn PNC  
1 auto- 0| 2| 0 up  
BUSY-OUT SUMMARY  
Trunks:  
2 n.a.  
3 n.a.  
0| 0| 0 dn  
0| 0| 0 dn  
0
0
0
Stations:  
Others:  
PROCESSOR OCCUPANCY STATUS  
Static:  
CP:  
1%  
SM:  
1%  
97%  
1% Idle:  
CRITICAL SYSTEM STATUS  
Active SPE: A/auto  
Duplicated? SPE:n  
SPE Power: commercial  
Time Source: primary  
# Logins: 3  
11:12 THU APR 3, 1997  
Command:  
Field descriptions  
Major  
Number of logged major alarms. (0–200)  
Number of logged minor alarms. (0–200)  
Number of warnings logged in the alarm file. (0–200)  
Number of maintenance busied out trunks.  
Number of maintenance busied out stations.  
Minor  
Warning  
Trunks  
Stations  
Others  
Combined number of maintenance busied out objects excluding trunks  
and stations.  
Static  
Proportion of the CPU that is dedicated to high priority items (for  
example, the operating system). This percentage is rounded to the  
nearest integer, therefore a percentage of 0 means that the occupancy  
is less than one half of a percent.  
SM  
Proportion of the CPU that is dedicated to system management or  
periodic and scheduled maintenance. If many periodic or scheduled  
maintenance tests perform, this occupancy percentage can be high  
without affecting service. This percentage rounds to the nearest integer;  
therefore, a percentage of 0=the occupancy is less than one half of a  
percent (for example, an 89.6% occupancy displays as 90%).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status health  
2
2-281  
CP  
Proportion of the CPU that is dedicated to call processing. This  
occupancy has priority over SM and IDLE occupancy categories, and if  
needed, takes processor time from these occupancy categories. This  
percentage is rounded to the nearest integer.  
Idle  
Available proportion of the CPU. This percentage is rounded to the  
nearest integer.  
Active SPE  
A or B indicate the active processor complex. When the active  
processor complex is locked on-line with lock switching on DUPINT, the  
“lock” option displays; otherwise, “auto” displays.  
Duplicated?  
SPE Power  
Duplication status of the SPE component. “y” = duplication;  
“n” = no duplication.  
Power source for the processor complex. (commercial) When  
commercial power is unavailable, battery backup is in use and is  
indicated with “backup”.  
Time Source  
The current timing source. Display values for this field vary according to  
timing sources selected. “external” = For Stratum-3 hardware, “internal”  
= an internal source, such as a tone clock.  
Primary and secondary timing sources must be administered for the  
Stratum-4 option. “primary”= the primary administered source is in use,  
“secondary” = the administered secondary source is in use. “local” =  
neither the primary or secondary sources are in use.  
# Logins  
Cab  
Number of current users.  
Assigned cabinet number (1 to the highest system cabinet number).  
Emerg Trans  
Settings for emergency transfer switches on the maintenance board for  
each cabinet. Available options are: auto-on (“auto+” or “a+”), auto-off  
(“auto-” or “a-”), “on”, “off”, and “n.a.”. The system defaults to “auto+” or  
“auto-”. In this state, emergency transfer activate automatically if the  
cabinet fails (“+”=emergency transfer is activate, “-” = emergency  
transfer is inactive). “on” = emergency transfer automatically activates.  
“off”=the cabinet cannot activate emergency transfers. Duplicated SPEs  
systems = switch settings for both processors of the PPN (cabinet 1)  
display. In this case, “auto+” is abbreviated “a+”, “auto-” is abbreviated  
“a-”, and “off” is abbreviated “of”. “on” does not change. “n.a.” = the  
emergency transfer switch setting is unavailable.  
Mj  
Mn  
Wn  
Number of major alarms associated with the cabinet. Asterisks are used  
to fill fields when numbers exceed 99.  
Number of minor alarms associated with the cabinet. Asterisks are used  
to fill fields when numbers exceed 99.  
Number of warnings associated with the cabinet. Asterisks are used to  
fill fields when numbers exceed 99.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status interface  
2
2-282  
PNC  
Port Network Connectivity (PNC) status for each port networks within a  
cabinet. When multiple port networks exist, Carriers A, B, and C are  
listed first and separated from Carriers D and E by a slash (for example,  
up/up).  
Time of Day  
Current time of day acquired from the system.  
status interface  
This command displays the number of counters maintained by the PI (a front end  
processor implementing packet layers and link layers of the BX.25 protocol and  
the ISDN procedure-D protocols).  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
interface  
location  
Location of processor interface (PI)  
board: (cabinet-carrier-position)  
1 = first processor interface  
init  
inads  
craft  
1 (one)  
none  
cust  
2 = second processor interface  
Report sent to printer  
rcust  
bcms  
browse  
print  
Output  
The following example shows the output from the status interface a1 command.  
status interface a1  
PROCESSOR INTERFACE STATUS  
Base Level Occupancy(low): 10  
Base Level Occupancy(high): 25  
Primary Queue Audit Error: 4  
Secondary Queue Audit Error: 10  
Translation Audit Error: 12  
Protocol Timer Audit Error: 0  
Hardware Sanity Timeout: 1  
Hardware Resource Error: 12  
Hardware Overload Error: 8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status isdn-testcall  
2
2-283  
status isdn-testcall  
This command displays the progress of an outgoing ISDN-PRI test call. The  
status form displays the tested ISDN-PRI B-channel port number, bit error rate,  
number of bits transmitted, block error rate, number of blocks transmitted, start  
time, duration specified, duration of test call and reason of termination.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
group  
Administered trunk group number  
init  
none  
see below  
isdn-testcall  
number  
inads  
craft  
group  
member  
number  
Administered group number (trunk  
within a trunk group)  
print  
Report sent to printer  
Feature Interactions  
If the bit error rate or block error rate is greater than zero, the ISDN-PRI trunk may  
be in trouble. The statistical information displayed on the terminal may deactivate  
the ISDN trunk. This is subjective because the ISDN trunk may be used for data  
or voice. If the trunk is used for data and the rates are high, the trunk should be  
deactivated. If the trunk is used for voice, the trunk may not be deactivated. Also,  
high rates be at risk for some type of power hit.  
Output  
The following example shows the output from the status idsn-testcall 80/1  
command.  
status isdn-testcall 80/1  
Page 1 of  
ISDN TESTCALL STATUS  
Number Block Number Duration  
1
SPE A  
Bit  
Reason  
Error Of  
Error Of  
Start  
Duration Of  
Of  
Port  
Rate Bits  
Rate Blocks Time  
Specified Test  
Termination  
1B1401  
0EE0 4EE7  
0EE0 6EE2  
25/12:36 120  
100  
in progress  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status journal-link  
2
2-284  
Field descriptions  
Port  
(cabinet/carrier/slot/circuit) of the ISDN-PRI B-channel.  
Bit Error Rate  
The measured bit error count based on the comparison between  
sent and received bit patterns. (Number displays in scientific  
notation)  
Number of Bits  
Number of bits generated. (Number displays in scientific notation)  
Block error Rate  
The measured block error count based on the comparison  
between sent and received bit patterns. (Number displays in  
scientific notation).  
Number of Blocks  
Number of blocks generated. (Number displays in scientific  
notation)  
Start Time  
Test call start time. (dd/hh:mm).  
Duration Specified  
Specified run time for the test call. (1-120 minutes, or blank =  
default of 10 seconds).  
Duration of Test  
Run time for the test call, listed in minutes. “blank” = a default time.  
Reason of Termination  
Reason that the test call terminates: “finished,” “canceled,”  
“overflow,” “no bits,” “transmission,” “internal fail,” “data corrupt,”  
“call dropped,” “call rejected,” and “in progress.” “finished” = the  
test finishes in the specified time. “canceled” = the test call  
cancels with the clear isdn-testcall command. “overflow” = the  
transmitted bits overflow buffer allocation. “no bits” = no bits are  
received because the ISDN-PRI test call circuit connection is bad.  
“transmission” = a data transmission interrupts, probably from a  
power hit. “call dropped” = the call drops due to an abnormal  
termination, or inability to cut-through to the other side. “call  
rejected” = the originating call is not set up properly. “internal fail”  
= an internal error on the Maintenance/Test circuit pack. “in  
progress” = the test is still running; “data corrupt” = any other error  
condition.  
status journal-link  
This command displays if the link is up or down. If the link is down, the system  
displays the number of times the switch tries to initialize the link. A journal printer  
documents automatic wake-up events, emergency access to attendant events,  
and housekeeping events when the property management system is not  
functional. A journal printer may also generate reports for automatic wake-up  
events and emergency access events at a scheduled time. If system  
configuration includes two printers, one is for housekeeping events only and the  
other is for automatic wake-up events and emergency access events.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status link n  
2
2-285  
For general information on journal printer links, see the description of the  
‘‘busyout journal-printer’’ section.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
journal-link  
wakeup-  
log  
printer that handles automatic  
wakeup and emergency access to  
attendant events and scheduled  
reports.  
init  
inads  
craft  
none  
none  
cust  
rcust  
bcms  
browse  
pms-log  
print  
printer that handles pms down  
events.  
Reports print to SAT-linked printer.  
Output  
The following example shows the output from the status journal-link  
wakeup-log command.  
status journal-link wakeup-log  
JOURNAL LINK STATUS  
Link State: up  
Maintenance Busy? no  
Field descriptions  
Link State  
If extensions are administered in the System Parameters  
Hospitality form, wakeup-logs or pms-log links are considered to  
be administered only.  
Maintenance Busy  
Is maintenance testing performing on the link?  
status link n  
This command applies to systems with a C-LAN circuit pack using Ethernet  
connections. See ‘‘Output (with PI circuit pack)’’ for the screen display for  
systems administered with Processor Interface (PI) circuit packs.  
This command displays:  
■
static information about the link  
■
the modem used, connect speed, and protocol information  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status link n  
2
2-286  
■
■
a counter of CHAP failures for PPP links  
time information for PPP and Ethernet links (includes the time of the last  
reset, the last hour start time, and end time for the error counter statistics).  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status link  
n
Number of the administered link.  
init  
none  
none  
inads  
craft  
Example:  
status link 1  
Output (C-LAN with Ethernet)  
The following example shows page 1 of the output from the status link n  
command (si w/ TN794 Net Packet/Packet Interface circuit pack).  
Link/Port Status form (page 1)  
status link 1  
Page  
1 of  
3
LINK/PORT STATUS  
Link Number: 1  
Link Status: connected  
Link Type: ethernet  
Link Name: ethernet on link 1  
Service Port Location: 01A0917  
Service Port Data Extension: 2991  
Service State: in-service/idle  
Node Name: ber1  
Source IP Address: 192.168.10.11  
Subnet Mask: 255.255.255.0  
Broadcast Address: 255.255.255.255  
Physical Address: 00:00:00:00:00:00  
Enabled? yes  
Maintenance Busy? no  
Active Channels: 0  
Field descriptions (page 1)  
Link Number  
Link Status  
Link Type  
Administered link number (assigned by add/change  
data-module command)  
Displays no, yes, unavail, connected, disconnected, enabled,  
out-of-service, or restarting  
The type of interface according to the physical/link protocol(s)  
immediately “below” the network layer in the protocol stack  
(ethernet, ppp, bx.25)  
Link Name  
Administered link name (assigned by add/change  
data-module command)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status link n  
2
2-287  
Service Port Location  
Administered port location (assigned by add/change  
data-module command)  
Service Port Data  
Extension  
Administered extension number (assigned by add/change  
data-module command)  
Service State  
Displays: in-service/idle, in-service/active, disconnected,  
out-of-service, maintenance busy, in-service, inactive, active,  
idle  
Node Name  
Administered node name (assigned by add/change  
data-module command)  
Source IP Address  
Subnet Mask  
Administered IP address (assigned with change node-name or  
add/change data-module commands)  
Administered subnet mask address (assigned by add/change  
data-module command)  
Broadcast Address  
Physical Address  
Administered broadcast address (assigned by add/change  
data-module command)  
The interface’s address (CLAN circuit pack) at the protocol  
layer immediately “below” the network layer in the protocol  
stack.  
Enabled  
y (yes) or n (no)  
Maintenance Busy?  
Active Channels  
y (yes) or n (no)  
Number of active channels  
Error Counters form (page 2)  
status link 1  
Page  
2 of  
3
ERROR COUNTERS  
Reset Time: 04/08 14:46  
Last Hour Start Time:  
Incoming Received:  
Since Reset  
Last Hour  
Incoming Dropped:  
Since Reset  
Last Hour  
Outgoing Transmitted:  
Since Reset  
Last Hour  
Outgoing Dropped:  
Since Reset  
End Time:  
Multicast Pkts  
Unicast Pkts  
Error Pkts  
Octets  
Discard Pkts  
Multicast Pkts  
Discard Pkts  
Unicast Pkts  
Error Pkts  
Octets  
Last Hour  
CRC Check: 0  
Collision Count: 0  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status link n  
2
2-288  
Field descriptions, page 2  
Incoming  
The number of subnetwork-unicast packets delivered to a higher-layer  
receivedUnicast  
packets  
protocol.  
Incoming  
received  
multicast  
packets  
The number of non-unicast (subnetwork-broadcast or  
subnetwork-multicast) packets delivered to a higher-layer protocol.  
Incomingdropped  
octets  
The total number of octets received on the interface, including framing  
characters.  
Incomingerrored  
packets  
The number of inbound packets that contained errors preventing them  
from being deliverable to a higher-layer protocol.  
Incomingpackets  
discarded  
The number of inbound packets which were chosen to be discarded even  
though no errors had been detected to prevent their being deliverable to  
a higher-layer protocol. One possible reason for discarding such a  
packet could be to free up buffer space.  
Outgoing  
Transmitted  
unicast packets  
The total number of packets that higher-level protocols requested be  
transmitted to a subnetwork-unicast address, including those that were  
discarded or not sent.  
Outgoing  
multicast  
packets  
The total number of packets that higher-level protocols requested be  
transmitted to a non- unicast (subnetwork-broadcast or  
subnetwork-multicast) address, including those that were discarded or  
not sent.  
Outgoing  
transmitted  
octets  
The total number of octets transmitted out of the interface, including  
framing characters.  
Outgoingerrored  
packets  
The number of outbound packets that could not be transmitted because  
of errors.  
Outgoingpackets  
discarded  
The number of outbound packets which were chosen to be discarded  
even though no errors had been detected to prevent their being  
transmitted. One possible reason for discarding such a packet could be  
to free up buffer space.  
Processor Channel Status form (page 3)  
The example below is for processor channels (page 3 of the form). Information  
about administered hop channels displays on page 4 of the form.  
The processor or hop channel status information can take either 1 or 2 pages on  
this form, depending on the number of links being reported and their condition.  
Hop channel information (shown only for BX.25 links using the Processor  
Interface or PGATE circuit packs) uses only 1 page.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status link n  
2
2-289  
status link 1  
Page  
3 of  
3
PROCESSOR CHANNEL STATUS  
UP: 001, 007, 010-115  
199, 300:310  
DN: 001-002  
PND: 003, 216-220, 299  
Field descriptions, page 3  
NOTE:  
A dash (-) or a colon (:) between numbers indicates all numbers including  
and between the indicated numbers.  
UP:  
Channels are up.  
DN:  
Channels are down.  
PND:  
Channels are in a pending state from the down to the up state  
(processor channels only)  
Output (with PI circuit pack)  
The following example shows the output from the status link 1 command.  
Page  
1 of  
4
LINK / PORT STATUS  
Link Number: 1  
Link Status: disconnected  
Link Type: proc-intf  
Link Name: audixa  
Service Port Location: 01A0301  
Service Port Data Extension: 4011  
Service State: in service/idle  
Enabled: y  
Maintenance Busy? n  
Active Channels: 0  
CONNECTED TO:  
Destination: TDMODULE  
Destination Status: in-service/active  
AC: 1 Connected/Orig  
Destination Port: 1C0303  
Destination Extension: 4002  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status packet-interface  
2
2-290  
Field descriptions, page 1  
Only those fields that are different from ‘‘status link n’’ are listed here.  
Destination  
Name of the destination (assigned with the add/change  
data-module command)  
Destination Status  
in-service/idle, in-service/active, disconnected, out-of-service,  
in-service, inactive, active, idle  
AC  
Active channel  
Destination Port  
Administered port location (assigned with the add/change  
data-module command)  
Destination  
Extension  
Administered destination extension number (assigned with the  
add/change data-module command). This may be replaced by  
Trk/Mem data (like the PI status line form) depending upon the  
type of destination.  
status packet-interface  
This command displays the status of the packet-interface portion of the TN798  
processor circuit pack along with link information. Link status information  
including total, active, and failed links also display. When the packet-interface is  
out-of-service or uninstalled, it is not used to establish and maintain links; when it  
returns to in-service status, new links are again assigned to it.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status packet-  
interface  
print  
Report sent to printer  
init  
inads  
craft  
none  
none  
Output  
The following example shows the output from the status packet-interface  
command.  
status packet-interface  
PACKET INTERFACE STATUS  
Location:  
01A  
Service State:  
in-service  
Total Links:  
Active Links:  
Failed Links:  
32  
32  
0
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status pms-link  
2
2-291  
Field descriptions  
Location  
Location: (cabinet-carrier-circuit pack)  
Service State standby is used in place of in-servicefor the standby  
packet-interface.  
Total links  
Active links  
Failed links  
Total number of links  
Number of links in use  
Number of failed links (equals # of total links - # of active links)  
status pms-link  
This command displays the status of the property management system interface  
link. If the link displays even when a data base swap occurs between the switch  
and PMS. If the link is down, the display indicates the number of times the switch  
tried to set up the link.  
A property management system (PMS) is a stand-alone computer system which  
can be integrated with the switch to enhance the service capability for a  
hotel/motel.  
For general information on PMS links, see the description of the ‘‘busyout  
pms-link’’ command.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
print  
Report sent to printer.  
init  
none  
none  
pms-link  
inads  
craft  
cust  
browse  
Output  
The following example shows the output from the status pms-link command.  
status pms-link  
PMS LINK STATUS  
Physical Link State: down  
Protocol State: down  
Number of Retries: 3  
Maintenance Busy? no  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status pri-endpoint  
2
2-292  
Field Description  
Physical Link  
State  
Up, down, or extension not administered displays. The PMS link is  
considered administered only if an extension is given in the  
System Hospitality form.  
Protocol State  
"up", "down", or blank if not administered.  
Number of Retries  
Number of times the switch has tried to set up the link. Displays  
when the link is down. (1–999)  
Maintenance Busy  
"yes", or "no" (that is, system technician has or has not busied out  
the link). Blank if PMS link not administered.  
status pri-endpoint  
This command displays internal software state information for diagnosis and can  
help locate facilities with which a PRI endpoint is communicating. Status  
information for each of the B-channels making up the PRI endpoint display in  
addition to some overall PRI endpoint information.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
status  
pri-endpoint  
extension  
PRI endpoint extension to be  
displayed (see dial-plan).  
init  
none  
none  
inads  
craft  
nms  
print  
Report sent to printer  
Examples:  
browse  
status pri-endpoint 25012  
status pri-endpoint 77868  
status pri-endpoint 66078 print  
Output  
The following example shows the output for the status pri-endpoint 22501  
command and assumes the following:  
■
PRI endpoint ports for extension 22501 are in cabinet 1, carrier B, slot 20,  
circuit 1 to 6.  
■
The ports 1 to 3 of the specified PRI endpoint are connected on an active  
call to ports 13 to 15 of board in location 1B19 (cabinet 1, carrier B, slot  
19).  
■
Ports 4 and 5 of the specified PRI endpoint are idle.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status pri-endpoint  
2
2-293  
■
Port 6 of the specified PRI endpoint is out of service, and background  
maintenance testing is being performed on the port.  
NOTE:  
A PRI endpoint can initiate and receive a call on any one or more of the  
B-channels making up the PRI endpoint.  
status pri-endpoint 22501  
page 1 of 1  
PRI-ENDPOINT STATUS  
Extension: 22501  
Signaling Group ID: 3  
Originating Auto Restoration? n  
Width: 6  
B-Channels Active: 3  
B-Channels Idle: 2  
Port  
Service State  
Test In Progress Connected Port  
01B2001 in-service/active  
01B2002 in-service/active  
01B2003 in-service/active  
01B2004 in-service/idle  
01B2005 in-service/idle  
01B2006 out-of-service-NE  
n
n
n
n
n
y
01B1913  
01B1914  
01B1915  
Command Successfully Completed  
Note that the line listing of each B-channel’s status may continue onto the next  
page. The user is prompted to press the NxtPg key to continue the display.  
Field descriptions  
Extension  
Width  
PRI endpoint extension  
Administered number of B-channels associated with the specified  
PRI endpoint  
Signaling Group  
ID  
ID number of the signaling group that handles the signaling for the  
ports in the specified PRI endpoint  
Originating Auto  
Restoration  
Administered option for the auto restore feature (restores calls  
originated from this PRI endpoint in the case of network failure):  
y= restoration option enabled  
n= restoration option disabled  
B-Channels Active  
B-Channels Idle  
Port  
The number of B-channels active on a call  
The number of B-channels in the in-service/idle state  
Port locations (cabinet-carrier-slot-circuit) for each of the  
B-channels making up the PRI endpoint.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status processor-channel  
2
2-294  
Service State  
Service state of the B-channels:  
in-service/active, in-service/idle, out-of-service-NE,  
out-of-service-FE, maint-NE/active, maint-FE/active, maint-NE/idle,  
and maint-FE/idle.  
NE (Near End) and FE (Far End) refer to which “end” of the  
B-channel has placed the facility in the current state. NE refers to  
the switch and FE refers to the PRI terminal adapter (or any device  
that terminates the D-channel signaling on the facility).  
Test In Progress  
Connected Port  
Whether or not there is any current maintenance testing on the  
port.  
Connected port location (cabinet-carrier-slot-circuit) for each of  
the B-channels active on a call.  
status processor-channel  
This command displays the status of the specified processor channel and the  
values of its various counters. A processor channel is 1 of 64 logical channels  
associated with an SCI link. Each processor channel terminates in the switch  
processing element with a session.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
status  
processor-  
channel  
channel  
number  
Processor channel number (1-64).  
init  
inads  
craft  
none  
none  
print  
Report sent to printer  
cust  
Examples:  
rcust  
bcms  
browse  
status processor-channel 1  
status processor-channel 10  
status processor-channel 64  
status processor-channel 64 print  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status processor-channel  
2
2-295  
Output  
The following example shows the output from the status processor-channels 1  
command.  
status processor-channels 1  
PROCESSOR CHANNEL STATUS  
Channel Number: 1  
Channel Status: 6: In data transfer state  
Reset Count: 3  
Message Buffer Number: 1  
Link Number: 4  
Retransmission Count: 5  
Field descriptions  
Channel Number  
Channel Status  
The processor channel number 1-64.  
State the channel is in:  
1. Channel is not administered.  
2. Channel is administered but not used.  
3. Channel is in a state entering “wait session accept” (WSA).  
4. Channel is in a state waiting for a “session accept” message  
from the far end.  
5. Channel is waiting for action.  
6. Channel is in data transfer state (channel up and running).  
7. Channel is in resynchronization state.  
8. Channel is waiting for acknowledge of disconnect message.  
9. ISDN-PRI Channel is currently down.  
10. ISDN-PRI Channel is in the data transfer state (that is, channel  
is up and running).  
Reset Count  
Number of times reset has been issued for this channel  
MessageBuffer  
Number  
Number of message buffers currently used for communication on  
this channel.  
Link Number  
Physical SCI link (1-8) associated with the channel  
Retransmission  
Count  
Number of times that message retransmission has occurred  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status signaling-group  
2
2-296  
status signaling-group  
This command displays the state, type, port location, and state of the Primary  
and Secondary D-channels within the group. A signaling group is a collection of  
B-channels signaled for by a designated single D-channel or set of D-channels  
over an ISDN-PRI.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
signaling-  
group  
group  
identifier  
Administered group identifier  
number (1-8)  
init  
none  
none  
inads  
craft  
cust  
print  
Report sent to printer  
Examples:  
browse  
status signaling-group 1  
status signaling-group 2 print  
Output  
The following output example shows the output from the status  
signaling-group 1 command.  
status signaling-group 1  
Page 1 of  
1
SPE A  
STATUS SIGNALING-GROUP  
Group ID: 1  
Type: facility associated signaling  
Group State: in-service  
Primary D-Channel  
Link: 1  
Link:  
Port: 01C1924 Level 3 State: in-service  
Secondary D-Channel  
Port:  
Level 3 State:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status signaling-group  
2
2-297  
Field descriptions  
Group ID:  
Type:  
Numerical ID of the signaling group (1-8)  
facility associated signaling: all members are on a single  
DS-1 facility. Facility associated signaling groups support only the  
simplex D-channel configuration.  
non-facility associated signaling: members can be carried  
by multiple DS-1 facilities.  
The DS-1 facility is identified across the ISDN-PRI using an explicit  
facility identifier. In a simplex configuration one D-channel is used to  
signal for B-channel members.  
Group State:  
in-service: one of the D-channels signaling for the group is in  
service  
out-of-service: neither D-channel in the group is in service  
NOTE:  
If there is no D-channel backup and the primary D-channel is  
out-of-service, then the signaling group is in an out-of-service  
state.  
Link:  
Port:  
Link transporting the D-channel  
Address of the port transporting either the primary or secondary  
D-channel  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status sp-link  
2
2-298  
Level 3  
State:  
State of the primary or secondary D-channels:  
in-service: a D-channel is “in-service” when it is in the  
multiple-frame-established state at layer 2 carrying normal call-control  
signaling at layer 3.  
standby: a D-channel is “standby” when it is in the  
multiple-frame-established state at layer 2, and not carrying any layer 3  
call-control messages on logical link 0,0.  
wait: a D-channel is in a “wait” state when an attempt has been made  
by one side of the interface to establish layer 3 peer communications as  
part of the process of going to the “in-service” state, which is  
transitional in nature. Only when the ISDN SERVICEmessage is sent  
over the interface, and the far end of the interface responds with a  
SERVICE ACKnowledge message is the D-channel placed in the  
“in-service” state.  
maintenance-busy: a D-channel is “maintenance-busy” when it is not  
in the multiple-frame-established state at layer 2. This state is entered  
automatically when an active D-channel is declared failed. A D-channel  
that has been placed in the “maintenance-busy” state may be placed in  
the “out-of-service” state without system technician intervention.  
manual-out-of-service: a D-channel is “manual-out-of-service”  
when system technician intervention has caused it to be placed in the  
TEI-assigned state at layer 2. System Technician intervention is  
required to retrieve a D-channel from this state.  
out-of-service: a D-channel is “out-of-service” when it is in the  
TEI-assigned state at layer 2, but is periodically requested by layer 3 to  
attempt to establish the link.  
no-link: no link is administered for the D-channel  
status sp-link  
This displays a page of output summarizing the operational status of the system  
printer link: its link state, number of retries, and whether the link is maintenance  
busy.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status sp-link  
print  
Report sent to printer  
init  
none  
none  
inads  
craft  
cust  
rcust  
bcms  
browse  
Examples:  
status sp-link  
status sp-link print  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status station  
2
2-299  
Output  
The following example shows the output for the status sp-link command.  
status sp-link  
SPE A  
SYSTEM PRINTER LINK STATUS  
Link State: up  
Number of Retries:  
Maintenance Busy? no  
Field descriptions  
Link State:  
Operational mode of the link:  
up: the link is administered and a call is setup between the switch  
and the system printer.  
down: the link is administered, but a call is not setup between the  
switch and the system printer.  
extension not administered: the link (no system printer  
extension) is not administered  
Number of  
Retries:  
Number of times the switch has tried to set up the link since a  
request to set up the link was received (1-999); if more than 999  
retries have occurred, 999still displays. (This field displays only if  
the Link State:field is down.)  
Maintenance  
Busy?  
Whether any maintenance testing is being performed on the  
system printer link:  
yesand no: system printer link is administered  
blank: system printer link is not administered.  
status station  
This command displays the internal software state information for diagnosis and  
to help locate the facilities to which the station is communicating.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
extension  
print  
Qualifier Description  
Permissions  
Defaults  
status  
station  
Station extension (per dial-plan)  
Report sent to printer  
init  
none  
none  
inads  
craft  
cust  
Examples:  
status station 10020  
status station 83277  
status station 83277 print  
browse  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status station  
2
2-300  
Output  
The following example shows the output for the status station 1002 command.  
status station 1002  
GENERAL STATUS  
Type: 7405D  
Extension: 1002  
Port: 01C0702  
Service State: in-service/on-hook  
Download Status: not-applicable  
SAC Activated? no  
Call Parked? no  
User Cntrl Restr: none  
Ring Cut Off Act? no  
Active Coverage Option: 1  
Group Cntrl Restr: none  
CF Destination Ext:  
Message Waiting:  
Connected Ports:  
ACD STATUS  
HOSPITALITY STATUS  
Grp/Mod Grp/Mod Grp/Mod Grp/Mod Grp/Mod  
AWU Call At:  
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
User DND: not activated  
Group DND: not activated  
Room Status: non-guest room  
On ACD Call? no  
Command:  
Field descriptions  
Type  
Administered station type  
Extension  
Port  
Station or attendant extension  
Port location: cabinet-carrier-slot-circuit  
Call Park  
Whether the station has a call parked (yesor no)  
Whether ring cut off is activated (yesor no)  
Ring Cut Off  
Activated  
CF  
Call forwarding destination extension, if any.  
Destination  
Ext  
Message  
Waiting  
Whether there is a message waiting for the station. “AP-SPE”,  
“AUDIX”, “PMS” or blank if no messages are waiting.  
Connected  
Ports  
Port locations of the facilities to which the station is connected:  
cabinet-carrier-slot-circuit  
Agent Logged  
In  
Displays (underneath) the hunt groups (up to 3) that the agent is  
logged into  
On ACD Call?  
Whether the agent is on an ACD call currently (yesor no).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status synchronization  
2
2-301  
Work Mode  
Work mode of each hunt group that an agent is logged into  
Service State  
In service/on-hook, in service/off-hook, in-service/in-tsa (Terminal  
Self Administration), out of service, or disconnected.  
Maintenance  
Busy State  
Whether maintenance is testing the object (yesor no)  
SAC Activated  
Whether send all calls is activated (yesor no)  
User Cntrl  
Restr  
One or two of the following: none, total, stat-stat, outward  
or terminate.  
Group Cntrl  
Restr  
One or two of the following: none, total, stat-stat, outward  
or terminate.  
AWU Call at  
User DND  
Time that Automatic Wakeup Call is scheduled  
Status of the do not disturb feature.  
Group DND  
Room Status  
Status of the group do not disturb feature.  
Whether a room is occupied or not (non-guest room, vacant, or  
occupied).  
status synchronization  
This command displays the location of the DS1 or tone-clock circuit pack that is  
used for an on-line synchronization reference. The synchronization subsystem  
provides error free digital communication between the switch and other PBXs,  
COs, or customer premise equipment. The subsystem is made up of: TDM bus  
clock, DS1 trunk board, maintenance and administration software resident in the  
SPE.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status  
print  
Report sent to printer  
init  
none  
none  
synchronization  
inads  
craft  
cust  
Examples:  
status synchronization  
status synchronization print  
browse  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status sys-link  
2
2-302  
Output  
The following example shows the output for the status synchronization  
command.  
status synchronization  
SYNCHRONIZATION STATUS  
Stratum Level:4  
Maintenance Name: TONE-BD  
Switching Capability: Enabled  
Physical Location: 01A  
Excessive Reference Switching: No  
Field descriptions  
Stratum Level  
Synchronization stratum level (3 or 4)  
Maintenance  
Name:  
Either TONE-BD, DS1-BD, or STRAT-3.  
Physical  
Location  
Board location of the selected DS1 or tone-clock circuit pack  
(cabinet-carrier-slot for a DS1; cabinet-carrier for a tone-clock)  
Switching  
Whether the on-line reference for synchronization can be switched  
Capability  
(Enabledor Disabled)  
Excessive  
Reference  
Switching  
High-level description of how many times the synchronization  
reference has been switched. If excessive reference switching is  
taking place (sync error 1793 is at threshold), this field displays  
Yes; otherwise Nodisplays.  
status sys-link  
This command displays status data for a specified system link. The report  
includes the type and operational state of the link, the associated processor  
channel (if any), active alarms and path status, and a list of all hardware  
components making up the link’s path.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status sys-link  
location  
Port location: PCSSpp  
init  
none  
none  
inads  
craft  
Example:  
status sys-link 1b0201  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status sys-link  
2
2-303  
Output  
The following example shows the output from the status sys-link 01a0516  
command.  
status sys-link 01a0516  
Location: 01a0516  
Current Path: present  
State: up  
Page  
Alarms: none  
Last Fault: 04/30/1997 14:18  
1 of  
2
Type/Chan: PRI  
Faulted Path: present  
Current Hardware Path  
Maintenance  
Maintenance  
Location  
Name  
Alarms  
Location  
Name  
Alarms  
01A  
PN 01  
PKT-INT  
TDM-BUS  
major  
none  
If a faulted path exists in addition to the current path, the components making up  
the faulted path display on page 2 of the report:  
status sys-link 01a0516  
Location: 01a0516  
Current Path: present  
State: up  
Page  
Alarms: none  
Last Fault: 04/30/1997 14:18  
2 of  
2
Type/Chan: PRI  
Faulted Path: present  
Faulted Hardware Path  
Maintenance  
Maintenance  
Location  
Name  
Alarms  
Location  
Name  
Alarms  
Field descriptions  
Location  
Type/Chan  
Alarms  
Port location (cabinet-carrier-slot-circuit)  
Type of system-link: PRI (ISDN-PRI signaling link)  
Highest alarm level currently logged against the components  
making up the link.  
Current Path  
Faulted Path  
Operational status of the current path:  
none: link is down.  
present: current path displayed is valid.  
The status of the faulted path, if any:  
present: path of the link has been faulted at least once.  
none: no record of the link having gone down  
default: default faulted path is being used  
Last Fault  
State  
Date and time at which the most recent fault occurred  
Whether the system link is upor down  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status system  
2
2-304  
Current  
Hardware Path  
Location, maintenance name, and alarm information for each  
hardware component making up the current path of the link. The  
path begins at the Packet Interface in the SPEand terminates at the  
circuit path terminating the other end of the link.  
Faulted  
Hardware Path  
If the link encounters a fault, the system reroutes it (if possible) over  
an alternate route. If this has taken place, the faulted path is  
displayed on page 2 of the report. The location, maintenance  
name, and alarm information for each hardware component making  
up the most recent faulted path is shown.  
status system  
This command displays the status, mode, and operational attributes of the  
SPE(s), TDM and Packet busses, tone-clock circuit pack(s), and emergency  
transfer switch of single or all cabinets in the system.  
!
CAUTION:  
The purpose of this command is to provide general information about the  
cabinet status. This information may not display correctly when the cabinet  
is in a transient period. In this case, wait for 1 minute and enter the  
command again.  
Feature  
Action/Object  
status system  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
cabinet  
1st-cabinet: PPN  
init  
none  
none  
Examples:  
status system 1st-cabinet  
status system all-cabinets  
inads  
craft  
cust  
rcust  
bcms  
browse  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status system  
2
2-305  
Output  
The following example shows the output from the status system all-cabinets  
command.  
status system all-cabinets  
Page 1 of 3  
SPE B  
SYSTEM STATUS CABINET 1  
SELECT SPE ALARMS  
SWITCH MAJOR MINOR  
TONE/ SERVICE SYSTEM SYSTEM  
CLOCK STATE CLOCK TONE  
1A in  
SPE MODE  
1A active  
0
2
active active  
SERVICE  
CONTROL DEDICATED  
SERVICE BUS ALARMS  
BUS OPEN BUS  
TDM STATE  
CHANNEL  
TONES  
n
y
PKT  
1
STATE MAJOR MINOR FAULTS LEADS  
1A  
1B  
in  
in  
y
n
in  
n
n
EMERGENCY  
TRANSFER  
1A  
SELECT  
SWITCH  
auto-off  
SERVICE  
STATE  
CABINET  
TYPE  
EXP-LINK  
-
MODE  
CMC  
1B  
Field descriptions  
SPE  
Switch Process Element (SPE) identifier (1Aor 1B)  
MODE  
SPE modes are different for simplex systems than for duplicated  
systems. See SPE Modes section that follows.  
SELECT SWITCH  
SPE select switch position:  
■ auto: the switch is in the middle position and automatically  
switches SPE depending upon conditions  
■ <blank> always appears for the 1A SPE in a simplex system.  
PE ALARMS -  
MAJOR  
Number of Major alarms associated with the SPE complex that  
affect the fault severity level of this SPE.  
SPE ALARMS -  
MINOR  
Number of Minor alarms associated with the SPE complex that  
affect the fault severity level of this SPE.  
TONE/CLOCK  
Location of the tone-clock circuit pack (1Aand 1B).  
SERVICE STATE  
■ in: Tone-Clock is installed and is in-service  
■ out: Tone-Clock failed certain maintenance tests and has been  
removed from service  
■ <blank> In simplex systems there is no B-carrier Tone-Clock,  
and this field displays blank.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status system  
2
2-306  
SYSTEM CLOCK  
Shows which Tone-Clock supplies the system clock for the cabinet  
displayed:  
■ active: Tone-Clock active and supplying system clock  
■ down: Tone-Clock failed some maintenance activity and cannot  
supply the system clock for this cabinet.  
■ <blank> If simplex, then the 1B Tone-Clock for the PPN displays  
blank; if no EPN, then both the 1A and 1B Tone-Clock for this  
EPN display blank.  
SYSTEM TONE  
Shows which Tone-Clock circuit pack supplies the system tones for  
the cabinet being displayed.  
■ active: Tone-Clock active and supplying system tones  
■ down: Tone-Clock failed some maintenance activity and cannot  
supply the system tones for this cabinet.  
■ <blank> If simplex, then the 1B Tone-Clock for the PPN displays  
blank. If the system does not have an EPN, then both the 1A  
and 1B Tone-Clock for this EPN display blank.  
TDM  
The TDM Bus identifier (1Aand 1B)  
SERVICE STATE  
Operational state of the TDM Bus circuit pack:  
■ in: TDM Bus installed and is in-service  
■ out: TDM Bus failed certain maintenance tests and has been  
removed from service  
CONTROL  
CHANNEL  
IWhether the control channel is on this TDM Bus (yor n)  
DEDICATED  
TONES  
Whether the dedicated tones are on this TDM Bus (yor n)  
PKT  
Packet Bus identifier (1). Refer to Packet Bus Maintenance  
descriptions for more information.  
SERVICE STATE  
The operational state of the Packet Buses:  
■ in: Packet Bus in-service and operating normally.  
■ out: Packet Bus failed certain maintenance tests and has been  
removed from service.  
■ <blank> System does not have the Packet Bus feature.  
BUS  
Whether Major alarms exist for packet bus components (yor n)  
ALARMS-MAJOR  
BUS  
Whether Minor alarms exist for packet bus components (yor n)  
ALARMS-MINOR  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status system  
2
2-307  
BUS FAULTS  
Number of faulty bus leads (defined as shorted to another lead,  
stuck at some value, or an open lead: 0 - 24). This field may take on  
any integer between 0 and 24. This field displays blank if:  
■ Maintenance/Test circuit pack not present  
■ Packet Bus port of the Maintenance/Test circuit pack has been  
taken out-of-service  
■ System does not have the Packet Bus feature  
OPEN BUS  
LEADS  
Number of open bus leads between the Maintenance/Test circuit  
pack and bus terminator (0 - 24). This could mean physical damage  
to the backplane or its connectors or a missing bus terminator. This  
field displays blank if:  
■ Maintenance/Test circuit pack is not present  
■ System does not have the Packet Bus feature.  
EMERGENCY  
TRANSFER  
Location of the Processor or EPN Maintenance circuit pack  
containing the Emergency Transfer Select Switch (1Aand 1B)  
SELECT SWITCH  
Emergency Transfer Switch position on the Processor(s) or the EPN  
maintenance circuit pack and the state of Emergency Transfer in  
the cabinet display:  
■ on: Designated analog phones in this cabinet are cut through to  
CO trunk lines only in an emergency situation.  
■ off: Emergency Transfer is off and cannot be invoked. The  
switch should only be in this state when a service technician is  
on site.  
■ auto-on: The switch is in the or auto position, however,  
because of a serious system fault, system software has invoked  
Emergency Transfer.  
■ auto-off: Switch in the auto position; because system has no  
serious faults, system software has not invoked Emergency  
Transfer  
■ <blank> If the system is Simplex, then the 1B Emergency  
Transfer indication for the PPN will display a blank. If the system  
does not have an EPN, then both the 1A and 1B Emergency  
Transfer indications for the EPN will display a blank.  
EXP-LINK  
The Expansion Link does not exist in the system; a dash (-)  
displays.  
SERVICE STATE  
MODE  
■ <blank> Expansion Interface Link does not exist  
■ <blank> Expansion Interface Link does not exist  
■ CMC(Compact Modular Cabinet)  
CABINET TYPE  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status trunk  
2
2-308  
SPE Modes  
Simplex SPE Modes  
active  
1A SPE in a simplex system is always the active SPE  
No 1B SPE in a simplex system  
blank  
Busyout Modes  
busyout/idle  
SPE busied out and there is no current maintenance activity.  
The active SPE can be either active or selected.  
busyout/entering  
SPE busied out and in the process of restarting the switch  
software on this SPE. After the switch software finishes its  
initialization, the standby SPE is available for maintenance  
functions on the standby SPE.  
busyout/testing  
SPE busied out, however, the switch software on this SPE has  
been restarted and is currently in the process of executing a  
test command.  
busyout/  
not-refreshed  
SPE busied out, however, the busyout spe-standby  
command was executed at a time when the standby memory  
was not refreshed. The standby SPE is not able to perform any  
maintenance or SAT-requested activities until a successful  
refresh spe-standby command is executed.  
busyout/  
list-config  
SPE busied out, however, the switch software on this SPE has  
been restarted and is currently executing a list configuration  
command.  
busyout/status  
SPE busied out, however, the switch software on this SPE has  
been restarted and is currently in the process of executing a  
status card-mem command.  
status trunk  
This command displays internal software state information for diagnosis and can  
help locate facilities to which the trunk is communicating. If a trunk group number  
is entered without a member number, a list showing the status for each member  
in the specified group displays. If a both the trunk group and member numbers  
are entered, the status for only the specified member displays.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status trunk  
2
2-309  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status trunk  
group  
Administered group number  
(1 - 99). If group number entered  
without a member number, a list  
showing the status of each  
init  
inads  
craft  
none  
none  
cust  
member in the group displays.  
rcust  
bcms  
browse  
member  
print  
Administered member number  
within a trunk group (1 - 99)  
Report sent to printer.  
Examples:  
status trunk 78  
status trunk 80  
status trunk 78/1  
status trunk 80/2  
status trunk 80/2 print  
Output  
The following example shows the output for the status trunk 78/1 (trunk  
group/member) command.  
status trunk 78/1  
TRUNK STATUS  
Trunk Group/Member: 078/001  
Port: 01C1505  
Signaling Group ID:  
Service State: in-service/idle  
Maintenance Busy? no  
CA-TSC State:  
Connected Ports:  
Field descriptions (group/member)  
Trunk  
Group/Member  
Trunk group number/group member number (1-99/1-99)  
Port location (cabinet-carrier-slot-circuit)  
Port  
Signaling  
Group ID  
If trunk is ISDN, then this field displays the number of the ISDN  
Signaling Group to which this group belongs; otherwise, the field is  
blank.  
Connected  
Ports  
Port locations (cabinet-carrier-slot-circuit) connected to the trunk  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status trunk  
2
2-310  
Service State  
Trunk service state:  
in-service/active, in-service/idle, out-of-service-NE,  
out-of-service-FE, maint-NE/active, maint-FE/active, maint-NE/idle,  
and maint-FE/idle.  
NE (Near End; switch) and FE (Far End; PRI terminal adapter or any  
device that terminates the D-channel signaling) refer to which  
“end” of the B-channel has placed the facility in the current state.  
Maintenance  
Busy  
Whether any maintenance testing is being performed  
CA-TSC State  
State of the temporary signaling connection (used to pass call  
information over PRI signaling links)  
Group only  
The following example shows the output from the status trunk 78 (trunk group  
only) command.  
status trunk 78  
TRUNK GROUP STATUS  
Member  
Port  
Service State  
Mtce Connected Ports  
Busy  
078/001 01C1505 in-service/idle no  
078/002 01C1506 in-service/idle no  
Field descriptions  
Member  
Trunk group number/group member number (1-99/1-99).  
Port  
Port location (cabinet-carrier-slot-circuit)  
Service State  
Trunk service state:  
in-service/active, in-service/idle, out-of-service-NE, out-of-service-FE,  
maint-NE/active, maint-FE/active, maint-NE/idle, and maint-FE/idle.  
NE (Near End; switch) and FE (Far End; PRI terminal adapter or any  
device that terminates the D-channel signaling) refer to which “end”  
of the B-channel has placed the facility in the current state.  
Mtce Busy  
Whether any maintenance testing is being performed  
Connected  
Ports  
Port locations (cabinet-carrier-slot-circuit) connected to the trunk  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status tsc-administered  
2
2-311  
status tsc-administered  
The status tsc-administered command displays the operational status of TSC’s  
administered for an administered signaling group. The status represents the  
state of the TSC according to switched services.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
status tsc-  
administered  
signaling  
group  
Administered signaling group  
number  
init  
inads  
craft  
none  
none  
#/tsc  
index  
Number associated with each TSC  
in a signaling group  
print  
Report sent to printer  
Examples:  
status tsc-administered 1  
status tsc-administered 1/1  
status tsc-administered 1/2 print  
Output  
The following example shows the output for the status tsc-administered 1/1  
command.  
status tsc-administered 1/1  
ADMINISTERED NON-CALL-ASSOCIATED TSC STATUS  
TSC  
Index  
1
TSC  
State  
inactive  
Establish  
as-needed  
Enabled  
yes  
Congested  
no  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status tti  
2
2-312  
Field descriptions  
TSC Index  
TSC State  
The administered TSC index (1-64).  
State of the administered TSC:  
■ inactive: the administered TSC is not functioning (for example,  
D-channel out-of-service, or disabled)  
■ active: indicates that the administered TSC is up and user  
information can be exchanged end-to-end.  
■ pending-inactive: shows that the TSC is being released.  
■ pending-active: the TSC is about to come up  
Establish  
The switch responsible for the origination of the administered TSC:  
■ as-needed: TSC is established on an as needed basis  
■ permanent: TSC is permanently established  
Enabled  
Indicates if the administered TSC’s have been enabled (“yes” or “no”).  
Congested  
Administered TSC congestion history (whether or not the network can  
handle the receipt of USER INFORMATION messages for the  
administered TSC):  
■ yes: TSC is congested  
■ no: TSC is not congested  
■ clear: TSC congestion was cleared during its active period  
status tti  
This command displays the status (active/not active) of the tti background  
maintenance task, and, if it is active, it displays whether tti ports are being  
generated or removed, the number of tti-supported boards that have processed,  
and the number of tti-supported boards that have not yet been processed. The  
display also includes the elapsed time since the background maintenance task  
started.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
status tti  
print  
Report sent to the printer  
init  
none  
TTI background  
inads  
craft  
cust  
nms  
browse  
maintenance task is  
activated by enabling the  
TTI system parameter on  
the System-parameters  
Features form.  
Examples:  
status tti  
status tti print  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
status tti  
2
2-313  
Output  
The following example shows the output for the status tti command.  
status tti  
Page 1 of 1  
TTI STATUS  
TTI Background Task State: generating tti ports  
TTI State: voice  
# of Boards Completed: 30  
# of Boards Left to Process: 120  
Percent Complete: 25  
Elapsed Time since Task Started: 0:15  
Field descriptions  
TTI  
Background  
Task State:  
State of the tti background maintenance task:  
■ generating tti ports:  
■ removing tti ports:  
■ suspended:  
■ not active:  
■ completed - all ports translated: the last execution  
of the background task completed normally  
■ completed - some ports not translated: the task  
completed due to resource exhaustion with some ports left  
untranslated  
TTI State:  
The tti state: displays off(TTI feature not enabled for the system),  
or if enabled, then the field displays what kind of tti ports are being  
generated or removed (voice, data).  
# of Boards  
Completed:  
Number of TTI-supported boards that have been processed by the  
background maintenance task:  
■ completed: board has either had all its unadministered ports  
translated as TTI ports or its TTI ports have been removed and  
are now unadministered ports. This depends on whether the  
TTI background task is generating or removing tti ports.  
# of Boards  
Left to  
Number of TTI-supported boards that have not yet been  
processed by the background maintenance task.  
Process:  
Percent  
Ratio of the of number of boards completed compared to the  
Complete:  
number of boards left to process.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test access-endpoint  
2
2-314  
Elapsed Time  
since Task  
Started:  
Elapsed time since the TTI background task was started. If the task  
is “not active”, then this field is blank. If the task is “completed” it  
will indicate the length of time (hh:mm format) it took to complete  
the task. If the task is “suspended”, then it will display the elapsed  
time at the point the task was suspended.  
test access-endpoint  
This command performs hardware diagnostic tests on all port circuits that are  
associated with the specified access endpoint extension.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
test  
access-  
endpoint  
extension  
Access endpoint extension (# of digits  
determined by dial-plan)  
init  
Test  
none  
inads  
craft  
nms  
sequence  
= short;  
repeat =  
1
short  
long  
Option for a brief series of nondestructive  
diagnostic tests.  
Option for a longer, more comprehensive  
test series (includes a destructive test)  
repeat  
number  
How many times each test in the sequence  
is repeated (1-100)  
clear  
This option causes the test sequence (short  
or long) to repeat until the alarm (if any) is  
cleared or a single test in the sequence  
1
fails.  
schedule  
Command is validated and then a  
scheduling form displays to schedule  
execution of the command. The command is  
then placed in the command queue and is  
executed at the specified time. The  
information displayed by the command is  
sent to the system printer instead of the  
2
screen.  
Examples:  
test access-endpoint 25012  
test access-endpoint 45002 sh  
test access-endpoint 45892 l  
test access-endpoint 24389 sh r 4  
test access-endpoint 34899 l r 6  
test access-endpoint 34912 l r 5 schedule  
test access-endpoint 93483 r 2  
test access-endpoint 10022 c  
test access-endpoint 92349 schedule  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear  
option forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears  
alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test alarms  
2
2-315  
Output  
The following example shows the output for the test access-endpoint 22502  
command, and assumes the access endpoint ports for extension 22502 are in  
cabinet 1, carrier C, slot 11, circuit 1 to 6. The responses are displayed on a  
port-by-port and test-by-test basis with one line of data for each test result.  
test access-endpoint 22502 short  
page 1 of 1  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01C1101  
01C1102  
01C1103  
01C1104  
01C1105  
01C1106  
WAE-PORT  
WAE-PORT  
WAE-PORT  
WAE-PORT  
WAE-PORT  
WAE-PORT  
22502  
22502  
22502  
22502  
22502  
22502  
36  
36  
36  
36  
36  
36  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
Maintenance  
Name  
The name of maintenance object (wideband access endpoint =  
WAE-PORT; single port access endpoint = TIE-DS1)  
Alt. Name  
Test No  
The extension number of the access endpoint  
The test being executed  
Result  
Test result: Pass, Abort, Fail, No Board, Disabled  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test alarms  
This command allows automatic testing all of the hardware associated with the  
active alarms in the alarm log. This command provides an initial query form to  
help the user narrow the selection of alarmed objects. After submitting the query  
form, the system tests the hardware associated with the selected alarm log  
entries. The results display in standard test output and status information display  
on the message line as the command progresses.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test alarms  
2
2-316  
Several alarms may be logged against a single maintenance object, each alarm  
representing a different problem. Even if there are multiple entries in the alarm  
log for a single object, the test alarms command only tests each physical object  
once.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
test alarms  
auto-  
page  
New screen displays when current  
screen fills  
init  
Test  
See below  
1
inads  
craft  
nms  
sequence  
= short;  
repeat = 1  
failures  
Only the failures (hardware, aborts,  
conflicts, EPN-down) display  
step  
Allows “stepping” to the next or  
previous alarm (current alarm not  
tested)  
2
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive test series  
(includes a destructive test)  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
3
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
4
printer instead of the screen.  
Examples:  
test alarms  
test alarms step failures  
test alarms long clear auto-page  
test alarms long failures  
1
2
If auto-page option is not specified, the screen does not refresh once filled, and testing stops until the user  
presses PAGE (continue) or CANCEL (halts testing).  
Press CANCEL to abort the command, ENTER to test the currently displayed alarm, NEXT ALARM (function  
key) to move to the next alarm, and PREV ALARM (function key) to move to the previous alarm without testing  
the currently displayed alarm. If this option is entered, then the NEXT ALARM (function key) or PREV ALARM  
(function key) can be pressed at any time during the command, even during test results. If NEXT ALARM or  
PREV ALARM is pressed during a test, the test is aborted, testing of the current alarm stops, and the next or  
previous alarm displays. If the first alarm is displayed and PREV ALARM is pressed, then the last alarm is  
displayed. If the last alarm is currently displayed and the NEXT ALARM is requested, then the first alarm  
displays. The only way to terminate this command is to press CANCEL.  
3
4
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence. SEE WARNINGS BELOW.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test alarms  
2
2-317  
!
WARNING:  
Executing a clear with short option may not clear all alarms, even if all tests  
pass.  
!
WARNING:  
Since the “clear long” options clear all counters if tests pass, it is possible  
for firmware counters to be cleared even when a problem exists. In some  
cases customer service might degrade since calls may be routed over  
defective equipment.  
Feature Interactions  
With the enhancement of multiple maintenance users, there may be a possibility  
of two users attempting to test the same physical hardware (for example, one  
using the test alarms command and another using the test board command). If  
this command attempts to test a board that is currently being tested by another  
user, a error message displays.  
Options form  
After entering the test alarms command, you are presented with an options form  
for alarm selection.  
test alarms repeat 1  
HARDWARE TEST ALARM QUERY  
The following options control which alarms will be tested.  
ALARM TYPES  
Major? y_  
Minor? y_  
Warning? y_  
REPORT PERIOD  
Interval: m_ From: __/__/__:__ To: __/__/__:__  
EQUIPMENT TYPE ( Choose only one, if any, of the following )  
Cabinet: __  
Port Network: __  
Board Number: ____  
Port: ______  
Category: ________  
Extension: _____  
Trunk ( group/member ): __/__  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test alarms  
2
2-318  
Field descriptions (Hardware Test Alarm Query)  
Alarm Types  
Interval  
From  
The type of alarm to be tested: put y or n in the field(s) to selects one  
or a combination of alarms.  
Tests alarms for the last hour (h), last day (d), last week (w) or all (a)  
[default].  
Test alarm from the specified time specified (mm/dd/hh/mm). If no  
fromdate is entered, then no checking is done and the alarms active  
since a month prior to the current time are reported.  
To  
Test alarms associated with records to the specified time specified  
(mm/dd/hh/mm). If no todate is entered, any alarm active after the  
fromdate is selected.  
Equipment  
Type  
The technician can choose from five different equipment types. If  
there is no input to any of these fields, the system defaults to all the  
equipment. The user can select one of the following fields:  
■ Cabinet: tests alarms associated with a particular cabinet (1-3).  
■ Port Network: tests all alarms associated with a particular port  
network (1-3).  
■ Board Number: tests all alarms associated with a particular  
circuit pack (PCSS, default cabinet = 1).  
■ Port: tests all alarms associated with a particular port on a  
circuit pack (PCSSpp, default cabinet = 1).  
■ Category: Alarms for a particular equipment category  
■ Extension: Alarms associated with an extension number  
■ Trunk(group/member): tests all alarms associated with a  
particular trunk group or trunk group member, XX/YY, where the  
group identifier tests all alarms associated with a trunk group  
(XX/__), and the group identifier and member identifier are both  
entered to test all alarms associated with a specific trunk group  
member (XX/YY).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test alarms  
2
2-319  
Output  
The following example shows the output from the test alarms command (query  
form left empty by pressing ENTER). The responses display on a test-by-test basis  
with one line of data for each test result.  
test alarms  
Page  
1
ALARM ENTRY  
Alarm  
Port  
01C03  
Port  
Maintenance On  
Alt  
Svc  
State 1 2  
Ack? Date  
Alarmed  
Alarm  
Count  
Name  
Brd? Name  
Type  
UDS1-BD  
n
WARNING  
03/06/16:48 1/4  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Error Code  
01C03  
01C03  
01C03  
01C03  
01C03  
01C03  
01C03  
01C03  
01C03  
UDS1-BD  
UDS1-BD  
UDS1-BD  
UDS1-BD  
UDS1-BD  
UDS1-BD  
UDS1-BD  
UDS1-BD  
UDS1-BD  
138  
139  
140  
141  
142  
143  
144  
145  
146  
NO BOARD  
NO BOARD  
NO BOARD  
NO BOARD  
NO BOARD  
NO BOARD  
NO BOARD  
NO BOARD  
NO BOARD  
Testing completed for this object.  
press CANCEL to quit -- press NEXT PAGE to continue  
Field descriptions  
When encountering errors in preparing a particular object to be tested (not  
inserted, contention, etc.), an error message display in the TEST RESULTS  
section of the output form.  
ALARM ENTRYsection  
Port  
Port location of alarmed object (cabinet-carrier-slot-circuit); same  
identifier as alarm log  
Maintenance  
Name  
The name of the maintenance object  
On Board  
Fault detected is on the associated circuit pack (y) or off board  
(o).  
Alt Name  
Terminal extension numbers or trunk group numbers  
Major, Minor, or Warning  
Alarm Type  
Service State  
Current service state of the station and trunk ports: RDY(ready for  
service), OUT(out of service), or IN(in service).  
Ack  
Whether alarm has been acknowledged by the first and second  
OSS telephone numbers, respectively.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test analog-testcall  
2
2-320  
Date Alarmed  
Alarm Count  
Day, hour, and minute of alarm.  
Count of the current alarm entry versus the total number of alarms  
to be tested.  
Test results section  
Port address (cabinet-carrier-slot-circuit)  
The name of maintenance object  
Port  
Maintenance  
Name  
Alt. Name  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Test No  
Result  
The test being executed  
Test result: Fail, Pass, Abort, or No Board. If this field has conflict,  
another user may be testing this hardware.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test analog-testcall  
This command performs facility diagnostic tests on an entire trunk group, an  
individual trunk group member, an individual trunk port, or on all trunks on a  
board, depending on the options entered. The type of test call, the far-end test  
line number, and the various other parameters must be administered on the trunk  
group form before executing the command. Normally, the user should only  
invoke the full or supervision test. The other options are provided primarily for  
testing when setting up an ATMS schedule.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test analog-testcall  
2
2-321  
Action/  
Feature  
Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
analog-  
testcall  
full  
Executes the most comprehensive test call  
available using the administered test set type.  
init  
Test  
sequence  
= long;  
See below  
inads  
craft  
cust  
no super-  
vision  
Executes a supervision-only test call (approx.  
10 sec.) and confirms the presence of the test  
set at the far end.  
repeat = 1  
no-selftest  
Executes the “full” test (skips any self-test  
sequences), saving about 20 seconds on the  
type 105 transmission test and has no effect on  
type 100 or 102 transmission tests.  
no-return-  
loss  
Executes the “full” test (skips any return loss  
sequences), saving about 20 seconds on the  
type 105 transmission test and does not have  
any effect on type 100 or 102 transmission  
tests.  
no-st-or-rl  
Executes the “full” test (skips all self test and  
return loss sequences), saving about 40  
seconds on the type 105 transmission test and  
does not have any effect on type 100 or 102  
transmission tests.  
repeat  
number  
How many times each test in the sequence is  
repeated (1-100)  
schedule  
Command is validated and then a scheduling  
form displays to schedule execution of the  
command. The command is then placed in the  
command queue and is executed at the  
specified time. The information displayed by the  
command is sent to the system printer instead  
1
of the screen.  
Examples:  
test analog-testcall trunk 78 f  
test analog-testcall trunk 78 f schedule  
test analog-testcall trunk 80/1 s r 2  
test analog-testcall trunk 80/1 s r 2 schedule  
test analog-testcall trunk 78/2 no-selftest r 10  
test analog-testcall trunk 78/2 no-selftest r 10  
schedule  
test analog-testcall trunk 78 r 4  
test analog-testcall trunk 78 r 4 schedule  
test analog-testcall port 2a1505 no-st-or-rl r 4  
test analog-testcall port 2a1505 no-st-or-rl r 4  
schedule  
test analog-testcall board 2a15  
test analog-testcall board 2a15 schedule  
test analog-testcall port 2a1505  
no-return-loss  
test analog-testcall port 2a1505  
no-return-loss schedule  
te an t 80  
te an t 80 schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test analog-testcall  
2
2-322  
Feature Interactions  
■
Additional data is available after running a test. See the ‘‘list  
measurements ds-1’’ command with the test-call option for details on how  
to access the additional data.  
■
■
If the trunk is in use by call processing, the test aborts.  
If the trunk is in use by maintenance, the test queues and runs when the  
current maintenance activity finishes.  
Output  
The following example shows the output for the test analog-testcall trunk 78  
command. The responses display on a test-by-test basis with one line of data for  
each test result.  
test analog-testcall trunk 78  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01C1505  
01C1507  
CO-TRK  
CO-TRK  
78/1  
78/2  
845  
845  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
The port address (cabinet-carrier-slot-circuit) of the maintenance  
object that is being tested.  
Maintenance  
Name  
The type of maintenance object that is being tested.  
Alt. Name  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
trunk  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
Test No.  
Result  
The test being executed  
Test result: Pass, Fail, Abort, Disabled, No Board, or Extra Board.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test board  
2
2-323  
test board  
This command performs a set of hardware diagnostic tests on a specified circuit  
pack. The system first validates that the board exists at the specified location.  
Then, based on the logical type of board (for example, Analog, Digital, Hybrid,  
and others), a series of tests perform diagnostics on the board and then returns  
results of the test along with any possible error codes. Some of the tests can be  
disabled by administration.  
For the R6csi system, the test board 01A01 command tests all of the  
components associated with the processor circuit pack except for environmental  
components and system links, which require the test environment and test  
sys-link commands, respectively. The processor components are tested in the  
following order: PROCR, PR-MEM, SW-CTL, PKTINT, DATA-BD, DATA-CHL,  
12V-PWR, CARD-MEM, and PR-MAINT.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
test board  
location  
Physical location of the board  
init  
Test  
none  
PCSS  
inads  
craft  
nms  
sequence  
= short;  
repeat = 1  
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive test series  
(includes a destructive test)  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test board 01c11 l  
test board 01c11 l schedule  
test board 02b15 sh r 2  
test board 01c08  
test board 02d12 r 4  
test board 02d12 c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence. SEE WARNING BELOW.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test board  
2
2-324  
!
WARNING:  
Since the “clear long” options clear all counters if tests pass, it is possible  
for firmware counters to be cleared even when a problem exists. In some  
cases customer service might degrade since calls may be routed over  
defective equipment.  
Feature Interactions  
Destructive long tests on a Switch Node Interface (SNI) board are not allowed  
unless the board has first been busied out.  
Output  
The following example shows the output from the test board 1c07 short  
command. The responses display on a test-by-test basis with one line of data for  
each test result.  
test board 01C07 short  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01C07  
01C07  
ANL-BD  
ANL-BD  
51  
52  
35  
48  
36  
35  
48  
36  
35  
48  
36  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
01C0703  
01C0703  
01C0703  
01C0701  
01C0701  
01C0701  
01C0702  
01C0702  
01C0702  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
Command Successfully Completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test card-mem  
2
2-325  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
The name of maintenance object  
Maintenance  
Name  
Alt. Name  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Test No  
Result  
The test being executed  
Test result: Pass, Fail, Abort, Disabled, No Board, or Extra Board.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test card-mem  
This command executes a sequence of tests on the memory card in the  
specified switch processor element. The test sequences in order for both long  
and short options are listed in the following table:  
Test  
Short  
Long  
X
12 Volt Power Supply Test (#701)  
X
X
X
X
X
X
Memory Card Insertion Test (#695)  
X
Memory Card Format and Read Test (#696)  
Memory Card Match Test (#697)  
X
X
Memory Card Write-Protected Test (#698)  
Memory Card Directory Recovery Test (#699)  
Memory Card Translation Data Integrity Test (#694)  
Memory Card Erase/Write/Read Test (#693)  
Memory Card Capacity Test (#1014)  
X
X
X
X
X
These tests verify the sanity of the memory card device, the basic  
read/erase/write operations to the memory card, the integrity of the translation  
data stored in the memory card, the function of 12-volt power supply used for  
memory card erase/write operations, and the translation capacity of the memory  
card. This command can also help troubleshoot the following hardware errors:  
CARD-MEM, 12V-PWR, CAP-MEM, and FL-DATA.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test card-mem  
2
2-326  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test card-mem  
location  
Carrier location where memory  
init  
Test  
See below  
card resides: (a)  
inads  
craft  
sequence  
= short;  
repeat = 1  
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive test series  
(includes a destructive test)  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test card-mem  
test card-mem a l  
test card-mem b sh r 2  
test card-mem a sch  
test card-mem a c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear  
option forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears  
alarms pertinent to tests in the short sequence. SEE WARNING BELOW.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
!
WARNING:  
Since the “clear long” option clears all counters if tests pass, it is possible  
for firmware counters to be cleared even when a problem exists. In some  
cases customer service might degrade since calls may be routed over  
defective equipment.  
Feature Interactions  
The test card-mem long command invokes the Memory Card Erase/Write/Read  
Test. This means that the save translation and save announcement commands  
are rejected while the write-to-memory-card operation is active. This test also  
invokes the Memory Card Capacity Test which determines whether the memory  
card is more than 98% full. This test is also invoked after the save translation  
command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test card-mem  
2
2-327  
Output  
The following example shows the output from the test card-mem a long  
command. The responses display on a test-by-test basis with one line of data for  
each test result.  
test card-mem a long  
SPE A  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01A  
01A  
01A  
01A  
01A  
01A  
01A  
01A  
01A  
12V-PWR  
701  
695  
696  
697  
698  
699  
694  
693  
1014  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
CARD-MEM  
CARD-MEM  
CARD-MEM  
CARD-MEM  
CARD-MEM  
CARD-MEM  
CARD-MEM  
CAP-MEM  
Command successfully completed  
Field descriptions  
Port  
Port address (1A). The slot and circuit fields in the port address  
for the 12V-PWR, CAP-MEM, and CARD-MEM maintenance  
objects are always blank.  
Maintenance  
Name  
The name of maintenance object being tested:  
■ CARD-MEM for the memory card  
■ 12V-PWR for 12-volt power supply in TN777B NETCON board  
■ CAP-MEM for memory card capacity  
■ FL-DATA for the data consistency stored in memory cards  
(duplicated switch)  
Test No  
Result  
The test being executed  
Test result: Pass, Fail, or Abort  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test cdr-link  
2
2-328  
test cdr-link  
This command first validates that the Call Detail Recording (CDR) link has been  
administered and exists in the switch. Then individual diagnostic tests run on the  
link and return results of the test along with any possible error codes. For more  
information on the CDR link, see the description for the ‘‘status cdr-link’’  
command.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
link-id  
short  
Qualifier Description  
Permissions  
Defaults  
test cdr-link  
Link-id = primary or secondary  
init  
inads  
craft  
Test  
none  
sequence  
= short;  
repeat = 1  
Option for a brief series of  
nondestructive diagnostic tests.  
long  
Option for a longer, more  
comprehensive test series  
(includes a destructive test)  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test cdr-link primary l  
test cdr-link secondary sh r 2  
test cdr-link primary  
test cdr-link secondary  
test cdr-link secondary c  
test cdr-link primary schedule  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test cdr-link  
2
2-329  
Output  
The following example shows the output for the test cdr-link primary command.  
The responses display on a test-by-test basis with one line of data for each test  
result.  
test cdr-link primary short  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
PRI-CDR 215 PASS  
Error Code  
Command Successfully Completed  
Field descriptions  
Port  
Not applicable (always blank)  
Maintenance  
Name  
The type of MO being tested: primary cdr-link= PRI-CDR; secondary  
cdr-link = SEC-CDR  
Alt. Name  
Test No  
Not applicable (always blank)  
The test being executed  
Result  
Test result: Pass, Abort, Fail, Disabled  
Error Code  
Numeric code explaining why the release failed or aborted. Refer to the  
detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test customer-alarm  
2
2-330  
test customer-alarm  
This command performs hardware diagnostic tests on the leads of the Processor  
and EPN maintenance circuit packs, used for customer-provided alarms by  
closing the appropriate relay for 1 minute. Failure is verified by checking the  
customer alarm attached to the specified circuit pack.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
location  
Extension of the data module or  
data channel to be tested (per  
dial-plan)  
init  
inads  
craft  
See  
below  
none  
customer-alarm  
short  
long  
Runs test number 115  
Runs test number 115 (same as  
short test option)  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test customer-alarm  
test customer-alarm schedule  
test customer-alarm 02 r 2  
test customer-alarm 01b r 25  
test customer-alarm 01b r 25  
schedule  
test customer-alarm 2a  
test customer-alarm 2a sh  
test customer-alarm 01b l  
schedule  
test customer-alarm 3 c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear  
option forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears  
alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Defaults  
The default cabinet is cabinet 1, and the default carrier is “a.” The default for the  
remaining parameter is a repeat of 1.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test data-module  
2
2-331  
Output  
The following example shows the output from the test customer-alarm 02a  
command.  
test customer-alarm 02A  
TEST RESULTS  
Port  
02A  
Maintenance Name Alt. Name Test No. Result  
CUST-ALM 115 PASS  
Error Code  
Command Successfully Completed  
Field Definitions  
Port  
The port address (cabinet-carrier-slot)  
Maintenance  
Name  
The maintenance name (always CUST-ALM)  
Alt. Name  
Test No.  
Result  
Not applicable  
The test number (always 115)  
Test result: Pass, Abort, or Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test data-module  
This command performs hardware diagnostic tests on a data module or data  
channel. Test results are determined by the interface to the digital switch-data  
line port, digital line port, or network control data channel.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test data-module  
2
2-332  
Action/  
Feature  
Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
data-module  
extension  
Extension of the data module or  
data channel to be tested (per  
dial-plan)  
init  
Test  
none  
inads  
craft  
cust  
nms  
sequence  
= short;  
repeat = 1  
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive test series  
(includes a destructive test)  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test data-module 30000 l  
test data-module 30000  
test data-module 32000 sh r 2  
test data-module 33000 l r 25  
test data-module 33000 l r 25  
schedule  
test data-module 30000 c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence. SEE WARNING BELOW.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
!
WARNING:  
Since the “clear long” options clear all counters if tests pass, it is possible  
for firmware counters to be cleared even when a problem exists. In some  
cases customer service might degrade since calls may be routed over  
defective equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test ds1-loop  
2
2-333  
Output  
The following example shows the output from the test data-module 300  
command. The responses display on a test-by-test basis with one line of data for  
each test result.  
test data-module 300  
TEST RESULTS  
Port  
01C1103  
Maintenance Name Alt. Name Test No. Result  
Error Code  
PDMODULE  
17  
PASS  
Command successfully completed  
Field Definitions  
Port  
Port address (cabinet-carrier-slot-circuit)  
The name of maintenance object  
Maintenance  
Name  
Alt. Name  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Test No  
Result  
The test being executed  
Test result: Pass, Fail, Abort, No Board  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test ds1-loop  
This command validates that the board exists at the specified location and that  
the board is a TN464F or TN767E or later suffix DS1 Interface board.  
Long-duration loopback tests execute for an extended period of time until  
manually terminated. Short-duration loopback tests return the result of the test to  
the screen after executing. The list measurements ds1 summary command  
can be used to monitor the status of a long-duration loopback/span test.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test ds1-loop  
2
2-334  
Action/  
Feature  
Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
ds1-loop  
location  
Physical location of board  
(PCSS)  
init  
inads  
craft  
super-user  
other  
ds1/csu-  
loopbac  
k-tests  
See below  
cpe-loopback-  
jack-test-begin  
Long-duration loopback test  
setup through the Customer  
Premises Equipment (CPE)  
Loopback Jack. Allows user to  
specify a loop-up code for the  
CPE loopback jack if it differs  
from the default (0x47F). The  
loop-up code is entered by  
specifying the number of bits in  
the loop-up code as well as the  
3
1
actual hexadecimal bit-pattern.  
far-csu-loopback-  
test-begin  
Long-duration loopback test  
setup through the far-end  
Channel Service Unit (CSU)  
one-way-span-  
test-begin  
Long-duration one-way span  
test  
end-loopback/  
span-test  
Terminates long-duration  
one-way span and loopback  
testing  
inject-single-bit-  
error  
Single bit error sent within an  
active framed 3-in-24 test  
pattern used in long-duration  
loopback and span testing  
ds1/csu-  
Sequentially executes the  
loopback-tests  
following loopback tests: DS1  
Board LoopBack, CSU Module  
Equipment LoopBack, and CSU  
2
Module Repeater LoopBack.  
Examples:  
test ds1-loop 01c08  
test ds1-loop 1-3c03  
cpe-loopback-jack  
test ds1-loop 1-3c03 cpe  
test ds1-loop 10c03 end  
test ds1-loop 02d12 fa  
test ds1-loop 02d12 inj  
1
For TN464F or TN767E or later suffix DS1 boards only. The test aborts if the board has not been taken out of  
service with the busyout command.  
2
3
For TN464F or TN767E or later suffix DS1 boards  
Logins with Maintain Switch Circuit Packspermissions enabled.  
Feature Interactions  
■
Loopback or span tests are not allowed on DS1 boards unless the board  
has been busied out.  
■
Only one of the CPE Loopback Jack, far-end CSU, one-way span, or  
DS1/CSU loopback tests may be active at any given time on a DS1 span.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
test eda-external-device-alrm  
2-335  
Output  
The following example shows the output for the test ds1-loop 1c07 command,  
and assumes that the board in cabinet 1, carrier c, slot 7 is a TN767E DS1 board.  
The responses display on a test-by-test basis with one line of data for each test  
result.  
test ds1-loop 01C07 ds1/csu-loopback-tests  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01C07  
01C07  
01C07  
DS1-BD  
DS1-BD  
DS1-BD  
1209  
1210  
1211  
PASS  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
The name of maintenance object  
Maintenance  
Name  
Alt. Name  
Test No  
The alternate means of identifying the maintenance object.  
The test being executed  
Result  
Test result: Pass, Abort, Fail, No Board, Disabled, or Extra Bd  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test eda-external-device-alrm  
This command performs a hardware diagnostic test on all or specific port’s  
administered external device alarms. The test PASSES if the external device is  
not reporting an external device alarm and FAILS if the external device is  
reporting an external device alarm. If you are entering a specific port, it must  
already be administered as an external device alarm port on a maintenance or  
an analog line port carrier board.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
2
test eda-external-device-alrm  
2-336  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
eda-external-  
device-alrm  
physical  
location  
In addition to the word physical,  
you must enter the physical  
location (PCSSpp for an  
init  
inads  
craft  
Repeat  
= 1  
none  
administered external device  
1
alarm analog line port).  
all  
Tests all administered external  
device alarm ports on analog line  
and maintenance boards.  
repeat  
clear  
How many times each test in the  
sequence is repeated (1-100)  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
2
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
3
printer instead of the screen.  
Examples:  
test eda-external-device-alrm all  
test eda-external-device-alrm all  
schedule  
test eda-external-device-alrm  
physical 1major r 10  
test eda-external-device-alrm  
physical 2c1101 c  
1
Since the “maintenance board” alarm connections connect to control carrier boards that are in unnumbered  
slots, the standard port format cannot be used to designate these alarm connections. The special ports Pmajor  
and Pminor are used designate the major or minor maintenance board alarm connection for cabinet P. The  
major/minor designation specifies the pair of wires, not the alarm level associated with the connection (the  
“major” port can be administered as a major, minor or warning alarm and the “minor” port can be administered  
as a major, minor or warning alarm).  
2
3
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test environment  
2
2-337  
Output  
The following example shows the output for the test external-device-alarm all  
command. The responses display on a test-by-test basis with one line of data for  
each test result.  
test eda-external-device-alarm all  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01major  
01minor  
01c1201  
01c1202  
EXT-DEV  
EXT-DEV  
EXT-DEV  
EXT-DEV  
UPS1  
UPS1  
UPS1  
Audix1  
120  
120  
120  
120  
PASS  
PASS  
PASS  
PASS  
Command successfully completed  
Field definitions  
Port  
Port address (cabinet-carrier-slot-circuit)  
The name of the maintenance object  
Maintenance Name  
Alt. Name  
The alternate means of identifying the maintenance object, in  
this case, the administered (descriptive) name of the external  
device alarm.  
Test No  
Result  
The test being executed  
Test result: Pass, Abort, Fail, No Board, Disabled, or Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted.  
Refer to the detailed list of the codes by test number for each  
MO.  
test environment  
This command performs hardware diagnostic tests of the environment  
monitoring and control, and emergency transfer functions of the Processor Port  
Network (PPN) cabinet. Circuit packs involved are the Processor (PPN simplex  
systems) and the Duplication Interface circuit packs. The tone/clock circuit pack  
is involved in tests of the ring generator.  
There are 8 Maintenance Objects involved in this testing:  
1. CABINET tests air flow and temperature  
2. EMG-XFER tests emergency transfer status  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test environment  
2
2-338  
3. EXT-DEV tests external (AUDIX, for example) alarm status for both the  
SCC and MCC cabinet systems.  
4. RING_GEN tests ringing voltage are tested in MCC cabinets only.  
NOTE:  
The processor carrier is not be recycled. All port carriers are recycled, and  
service is interrupted for each port carrier. If a carrier containing an active  
tone-clock board is recycled, all ports in the cabinet or port network will  
have service disrupted.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test environment  
location  
Cabinet 1 = PPN  
init  
inads  
craft  
Cabinet = 1;  
test sequence  
= short; repeat  
= 1  
See below  
Option for a brief series of  
nondestructive diagnostic tests.  
short  
long  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
How many times each test in the  
sequence is repeated (1-100)  
repeat  
number  
This option causes the test  
clear  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
a single test in the sequence fails.  
1
Command is validated and then a  
scheduling form displays to  
schedule  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test environment  
test environment schedule  
test environment 1 sh  
test environment 1 l r 25  
test environment 01 l r 25  
test environment 01 l r 25  
schedule  
test environment 2 l c  
test environment 3 c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear option  
forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears alarms pertinent  
to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test environment  
2
2-339  
Feature Interactions  
■
The long test recycles power in some specified cabinet on non-SPE and  
maintenance board carriers and is destructive. Specifically, the ’a’ carrier  
of PPNs does not have power recycled.  
■
■
All port carriers are recycled, and service is interrupted for each port  
carrier.  
If a carrier containing an active tone-clock board is recycled, all ports in  
the cabinet or port network will have service disrupted.  
Output  
The following example shows the output for the test environment 1 command to  
test a PPN cabinet. The responses display on a test-by-test basis with one line of  
data for each test result.  
test environment 1  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
Error Code  
01  
01  
01  
01  
01  
01  
CABINET  
EMG-XFER  
EXT-DEV  
EXT-DEV  
RING-GEN  
RING-GEN  
122  
124  
120  
120  
117  
118  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
Port address (cabinet-carrier)  
Maintenance  
Name  
The name of maintenance object  
Alt. Name  
Test No.  
Result  
Not applicable  
The test being executed.  
Test result: Pass, Abort, Fail, Disabled  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test hardware-group  
2
2-340  
test hardware-group  
This command allows a user to perform a set of hardware diagnostic tests on the  
whole system, a carrier, cabinet, spe, or board. The tests vary according to the  
configuration of the system and the specified command options. Each test  
exercises diagnostics on all the hardware in the specified hardware group and  
reports results of the test along with any possible error codes. Concurrent testing  
is done to enhance performance, therefore, test results display on the SAT in the  
order they are received. Consequently, test results of one maintenance object  
may be intermixed with test results of other maintenance objects.  
Because the tests for this command are not destructive, the tests performed on a  
particular maintenance object with either the short or the long option may not be  
the same as the corresponding demand tests.  
A hardware-group command executing in the foreground may be cancelled by  
either pressing the CANCEL key or by entering the cancel hardware-group  
command at a different SAT. However, if the technician wants to cancel a test  
hardware-group command running in the background, the cancel  
hardware-group command can be entered on any SAT. A canceled test  
hardware-group command can be resumed at the point it left off by entering the  
resume hardware-group command. Restarts are not allowed for test  
hardware-group commands entered with either the all-ports option or the  
spe-interchange option.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test hardware-group  
2
2-341  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test hardware-group  
system  
System-wide test of all  
hardware-groups  
init  
inads  
Test  
See below  
sequence  
= short;  
repeat = 1  
carrier  
location  
Carrier address: cabinet (1), carrier  
1
(A)  
2
cabinet  
location  
Cabinet address (1)  
3
board  
Board location: PCSS  
location  
print  
Output sent to printer  
schedul  
e
Command validated and then a  
scheduling form displays to  
schedule execution of the command.  
The command is then placed in the  
command queue and is executed at  
the specified time. The information  
displayed by the command is sent to  
the system printer instead of the  
4
screen.  
Examples:  
test hardware-group system  
test hardware-group system print  
test hardware-group carrier 1a  
test hardware-group carrier 1a  
schedule  
test hardware-group board 01c07  
test hardware-group board 01c07  
schedule  
test hardware-group spe  
test hardware-group spe print  
test hardware-group spe schedule  
1
2
The type of carrier may be port, or processor. In the case of a port carrier, all universal port and tone-clock boards (see  
note 4) and its affiliated MOs residing in the specified carrier are tested. For a processor carrier, all SPE complex and  
tone-clock boards and affiliated MOs are tested.  
All PN and PNC related MOs plus cabinet specific MOs, including maintenance boards and environment (ring generator,  
battery, power, emergency transfer, external alarms, fans, and temperature) are tested if they reside in the specified  
cabinet location.  
3
All MOs on the specified ’board location’ including ports are tested.  
4
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test hardware-group  
2
2-342  
Feature Interactions  
test  
Only one test hardware-group command can be active at any  
hardware-group  
given time.  
TTI  
If the test hardware-group command is issued with the all-ports  
option when the TTI background task is active, some  
unadministered ports may not be tested. In addition, active alarms  
on line ports may be cleared by this task. The status tti command  
can be used to determine the state of the TTI background task.  
Add Station  
If a add station command is entered for an untranslated port at the  
same time as it is being tested as part of the test hardware-group  
command with the all-ports option, the error message, Object in  
use; please try laterdisplays, and the request fails.  
Trunk  
administration  
If an attempt is made to add an unadministered trunk port to a trunk  
group at the same time as it is being tested as part of the test  
hardware-group with the all-ports option, the error message,  
Object in use; please try laterdisplays, and the request fails.  
Save translation  
Hardware alarms  
If the test hardware-group with the all-ports option while a  
translation save operation is active, some unadministered ports  
may not be tested. All other hardware will be tested normally.  
When a hardware error is detected by the test hardware-group  
command, the hardware goes through the standard escalation  
strategy. Alarms are raised on hardware that manifest ’hard’ errors.  
This alarming strategy is the same, regardless of whether the ports  
are translated or not.  
System interaction  
The performance of test hardware-group is affected by call  
processing traffic, administration activity, choice of the short or  
long option, whether the all-ports option is chosen, whether the  
spe-interchange option is chosen, and other demand maintenance  
activity.  
Scheduled and  
periodic  
maintenance  
While executing the test hardware-group command, all scheduled  
background maintenance, periodic background maintenance, and  
data audits activity is suspended until the command completes.  
When the test hardware-group command is canceled or  
completes, all suspended periodic, scheduled, and data audits  
background maintenance activity will be restarted where it left off.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test hardware-group  
2
2-343  
Setting the Test Parameters  
Once the user has entered the desired action (test hardware-group) and the  
object (board, carrier, etc.), then an options form displays.  
test hardware-group system  
Page 1 of 1  
TEST HARDWARE-GROUP SELECTIONS  
Select the desired options for the specified test.  
Test sequence: short  
Test repetition: repeat  
count: 1  
Output OPTIONS:  
Auto-page? n  
HARDWARE OPTIONS:  
All-ports? n  
Background? n  
Failures? n  
SPE-interchange? n  
Field descriptions  
Test  
Short (nondestructive) or long (more comprehensive, still  
sequence  
nondestructive) test sequence  
Test  
repeat - (1-99) each test is executed the number of times specified on  
Repetition  
each physical object.  
continuously -all tests on all the specified hardware run until  
cancelled by either pressing the CANCEL key or by executing the  
cancel hardware-group command.  
count:  
Repeat test sequence value (1-99). If the Test sequencefield is set  
to continuously, then this field disappears from the screen; if this field  
is set to repeat, then the field appears.  
Auto-page?  
Provides a new screen every time the SAT screen fills with test results.  
(n / y). The screen does not scroll to accommodate new results;  
instead a new screen is provided after the current screen fills up.  
If the auto-page option is not selected, the SAT screen does not  
refresh once it is filled, and testing stops until the user enters the PAGE  
key to continue or the CANCEL key to cancel the testing.  
This option is not allowed if the background option is selected.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test hardware-group  
2
2-344  
Background?  
Run the command in the background, thus freeing the SAT (n / y). The  
error results are tabulated in the error log, but no results display on the  
terminal.  
This option cannot be used if either the continuously or the  
auto-page options are selected.  
Failures?  
Only failing test results display (n / y). Test results that pass or abort  
are not displayed. The failures option has no effect if entered with the  
background option.  
All-ports?  
Tests all customer translated line and trunk ports as well as a set of  
untranslated line and trunk ports for boards listed in Table 2-7 (n / y).  
Table 2-7. Test of ‘all ports’ option for the following boards:  
Board  
Board  
Number  
Description  
Digital Line  
Number  
Description  
16 port Analog Line  
TN413  
TN417  
TN429  
TN746  
TN747B  
TN753  
Auxiliary Trunk  
Central Office Trunk  
Direct Inward/ Outward Dialing  
Trunk  
Direct-Inward-Dial Trunk  
TN436  
TN437  
TN438  
TN439  
TN447  
TN458  
TN459  
TN464C  
TN465  
TN467  
TN468  
TN479  
TN497  
TN556  
TN722B  
TN726B  
Direct Inward Dialing Trunk  
Tie Trunk  
TN754  
Digital Line  
TN760C  
TN762B  
TN763C  
TN767  
Tie Trunk  
Central Office Trunk  
Tie Trunk  
Hybrid Line  
Auxiliary Trunk  
Central Office Trunk  
Tie Trunk  
DS1 Interface  
TN769  
Analog Line with Message Waiting  
Digital Line  
Direct Inward Dialing Trunk  
Universal DS1  
TN784  
TN785  
16 port Analog Line  
Italian 16 Port Analog Line  
Digital Line  
Central Office Trunk  
8 port Analog line  
16 port Analog line  
16 port Analog line  
Tie Trunk  
TN2135  
TN2136  
TN2138  
TN2139  
TN2140  
TN2144  
TN2146  
TN2147  
International Central Office Trunk  
Direct Inward Dialing Trunk  
Tie Trunk  
ISDNBRI Line  
Analog Line  
DS1 Tie Trunk  
Direct Inward Dialing Trunk  
Central Office Trunk  
Data Line  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test hardware-group  
2
2-345  
Table 2-7. Test of ‘all ports’ option for the following boards: — Continued  
Board  
Board  
Number  
Description  
Number  
Description  
Analog Line  
16 port Analog line  
TN735  
TN742  
MET Line  
8 port Analog Line  
TN2149  
TN2180  
SPE-interchange?  
Allow for planned interchange of duplicated SPEs and  
subsequent testing of both the active and standby SPEs.  
Output  
The following example shows the output for the test hardware-group system  
command and assumes that the board in port network 1, carrier c, slot 7 is an  
analog board with three administered ports and test sequence repeat = 3.  
Responses to this command running in the foreground display on a test-by-test  
basis with one line of data for each test result.  
test hardware-group system  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01C07  
01C07  
ANL-BD  
ANL-BD  
51  
52  
35  
35  
48  
35  
48  
36  
36  
48  
36  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
01C0703  
01C0702  
01C0703  
01C0701  
01C0702  
01C0703  
01C0702  
01C0701  
01C0701  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
ANL-LINE  
Testing system, 11070 of 12300 (90%) MOs tested for repetition 1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test inads-link  
2
2-346  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
The name of maintenance object  
Maintenance  
Name  
Alt. Name  
Alternate way to identify maintenance objects.  
If the Object is The field contains  
station  
trunk  
extension  
xxx/yyy (where xxx = trunk group number  
and yyy = member number)  
private CO line P/xxx (where xxx = private CO line group  
number)  
Test No.  
Result  
The test being executed  
Test result: No Board, Extra Bd, Disabled, or Skipped  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
The following example shows the output for the test hardware-group system  
with the background option selected.  
test hardware-group system  
Command started in background mode  
test inads-link  
This command attempts to make a call over the inads port on the maintenance  
board to verify the INADS alarm notification process. In the default settings, the  
system test the link to the first OSS telephone number. If there is an alarm  
pending to be reported or the call is in progress or up, then the test aborts. If the  
alarm origination to the OSS telephone number to be tested is disabled, then the  
test generates an informative error and the test continues. The test waits 2  
minutes before dialing the call to allow the remote maintenance technician to  
logoff, thus freeing the line. A local SAT user entering the test inads-link  
command does not need to log off for the system to place the call, but the  
two-minute delay still exists.  
Once the call is answered by INADS, the system sends a message with a test  
alarm type. INADS acknowledges receipt of the message and creates a trouble  
ticket. The trouble ticket is closed immediately and has a “INADS LINK TEST”  
message entered in the description field. If an alarm is raised while the test call is  
up, the system does not send an alarm message over the existing link. The  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test inads-link  
2
2-347  
normal retry mechanism is followed, which means an attempt to make a call to  
INADS to report the error takes place 7 minutes later. An INADS trouble ticket is  
created only if the connection is successfully established and a message is sent  
to the system acknowledging that INADS received the system message.  
The Maintain Process Circuit Packsfield must be set to yes on the inads  
and technician permission forms. This will provide permissions to execute the  
test inads-link command. This field can be changed by executing a change  
permission login command.  
No alarms are raised on the system and attendant alarm and acknowledgment  
lamp states are not changed as a result of the test inads-link command. The test  
does not run during periodic or scheduled maintenance.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test inads-link  
1
2
First OSS telephone number  
Second OSS telephone number  
init  
1st OSS  
number  
none  
inads  
craft  
nms  
Examples:  
test inads-link  
test inads-link 1  
test inads-link 2  
Output  
Command successfully completed  
Command failed  
Test passed  
Link was up, there was an active alarm that  
the switch needs to report, or there was a  
problem with the call.  
NOTE:  
An entry is made in the error log  
describing why the inads-link test failed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test interface  
2
2-348  
test interface  
This command performs hardware diagnostic tests on the specified processor  
interface circuit pack. In addition to testing the PI board, the tests examine the  
protocol and link interface that is transmitted over the board.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test interface  
location  
Location (cabinet-carrier-position)  
of the processor interface (position  
1 = first processor interface in the  
carrier, 2 = second)  
init  
Test  
none  
inads  
craft  
nms  
sequence  
= short;  
repeat = 1  
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
Number of times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test interface 01a1 l  
test interface 01b2 s r 2  
test interface 01b2 s r 2 schedule  
test interface b1 l r 25  
test interface a2  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence. SEE WARNING BELOW.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
!
WARNING:  
Since the “clear long” options clear all counters if tests pass, it is possible  
for firmware counters to be cleared even when a problem exists. In some  
cases customer service might degrade since calls may be routed over  
defective equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test isdn-testcall  
2
2-349  
Output  
The following example shows the output for the test interface a1 command. The  
responses display on a test-by-test basis with one line of data for each test result.  
test interface a1  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
Error Code  
01A1  
01A1  
PI-SCI  
PI-BD  
231  
52  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
Port address: cabinet-carrier-slot (the carrier associated with the  
particular processor interface board)  
Maintenance  
Name  
The name of maintenance object  
Alt. Name  
Test No  
Not applicable.  
The test being executed  
Result  
Test result: Pass, Abort, Fail, No Board, Disabled, or Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test isdn-testcall  
This command starts an outgoing, asynchronous ISDN-PRI test call in the  
asynchronous method from a specified trunk. If the test results are PASS, the test  
call is started. A test result of ABORT means that a resource wasn’t available, for  
example, B-channel or a Maintenance/Test circuit pack. A test result of FAIL  
denotes that the outgoing ISDN-PRI test call was not established.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test isdn-testcall  
2
2-350  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
isdn-testcall  
group  
number  
The administered group number  
associated with each trunk group  
init  
inads  
craft  
duration  
= 8.4 or  
9.6 sec  
See below  
member  
number  
The administered member number  
identifying a particular trunk within  
a trunk group.  
minute  
number  
Duration of the test call in minutes  
(1-120)  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
test isdn-testcall 80/1  
test isdn-testcall 80/1 schedule  
test isdn-testcall 78/2 minutes 10  
test isdn-testcall 78/3 minutes  
100 schedule  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Feature Interactions  
■
Use the status isdn-testcall command for details on how to access the  
additional data available after running the test.  
■
Only one ISDN trunk can be tested per port network at a time. Once  
testing is completed, another ISDN trunk can be tested in that port  
network.  
■
The maximum number of asynchronous outgoing test calls running  
depends upon the number of Maintenance/Test circuit packs in the  
system.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test journal-printer  
2
2-351  
Output  
The following example shows the output for the test isdn-testcall 80/1 command.  
The responses display on a test-by-test basis with one line of data for each test  
result.  
test isdn-testcall 77/1  
SPE A  
TEST RESULTS  
Port  
01B1501  
Maintenance Name Alt. Name Test No. Result  
ISDN-TRK 077/001 258 PASS  
Error Code  
Command Successfully Completed  
Field descriptions  
Port  
Port address: cabinet-carrier-slot-circuit  
Maintenance  
Name  
The name of the maintenance object being tested.  
Alt. Name  
Alternate means of identifying the maintenance object: trunk  
object xxx/yyy, where xxx= trunk group number, yyy=  
member number  
Test No  
Result  
The test being executed  
Test result: Pass, Abort, Fail, No Board, Disabled, or Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test journal-printer  
This command performs hardware diagnostics on the link between the switch  
and one of the specified journal printer links. There are two types of journal  
printer links: pms-log and wakeup-log. For general information on journal printer  
links, see the description of the ‘‘busyout pms-link’’ command. For information on  
what a journal printer is and does, see the description of the ‘‘status journal-link’’  
command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test journal-printer  
2
2-352  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
journal-printer  
pms-log  
Tests the link to the pms logging  
printer (maintenance name =  
PMS-PRNT)  
init  
inads  
craft  
Test  
See below  
sequence  
= short;  
repeat = 1  
wakeup-  
log  
Tests the link to the wakeup logging  
printer (maintenance name =  
JNL-PRNT)  
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
Number of times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test sequence  
(short or long) to repeat until the alarm  
(if any) is cleared or a single test in the  
1
sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to schedule  
execution of the command. The  
command is then placed in the  
command queue and is executed at  
the specified time. The information  
displayed by the command is sent to  
the system printer instead of the  
2
screen.  
Examples:  
test journal-printer pms-log l  
test journal-printer pms-log l  
schedule  
test journal-printer wakeup-log r 2  
test journal-printer wakeup-log r 2  
schedule  
test journ pm r 3  
test journ pm r 3 schedule  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear  
option forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears alarms  
pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Feature Interactions  
The maintenance of a particular component on a link sometimes interferes with  
the maintenance of the link itself. Maintenance can put a link component in a  
busy state causing link set-up to fail. Frequent attempts at re-setup of a link may  
delay the recovery of a faulty component due to the maintenance test of a  
component only taking place when the component is idle. Therefore, the  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test led  
2
2-353  
technician needs to be able to disable the attempted re-setup of a link. Use of  
the busyout command causes the link to be torn down. If the link is already down,  
the busyout command will stop periodic re-setup trys on the link.  
Output  
The following example shows the output for the test journal-printer pms-log  
command. The responses display on a test-by-test basis with one line of data for  
each test result.  
test journal-printer pms-log short  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
JRNL-LINK 215 PASS  
Error Code  
Command Successfully Completed  
Field descriptions  
Port  
Not applicable (always blank)  
Maintenance  
Name  
The name of maintenance object being tested:  
PMS-PRINT for testing the pms-log printer link  
JNL-PRNT for testing the wakeup-log printer link  
Alt. Name  
Test No  
Not applicable (always blank)  
The test being executed  
Result  
Test result: Pass, Abort, Fail, Disabled  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test led  
This command performs a test on all the LEDs in a specified cabinet. Once the  
cabinet is validated and the range of circuit packs determined, the test led  
command turns on all LEDs on the circuit packs contained in each carrier until all  
affected carriers are lit. Once all the LEDs are on, there is a 2-second pause, and  
then all the LEDs are turned off in the same order. Once all of the repeat cycles  
are completed, all affected LEDs are restored to the current status.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test memory  
2
2-354  
The following LEDs are NOT lighted by the test led command:  
■
Power Unit LEDs  
■
Yellow (amber) LED on the tape drive  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test led  
all  
All LEDs in all carriers are tested  
init  
inads  
craft  
all; repeat  
= 1; test  
sequence  
= short in a  
duplex  
none  
cabinet  
number  
Cabinet number (each carrier  
tested sequentially)  
short  
Simplex: short and long option are  
identical and turn on and off all  
leds in the specified port network.  
system  
long  
Short and long option are identical  
and turn on and off all leds in the  
specified port network.  
repeat  
number  
Number of times each test in the  
sequence is repeated (1-100)  
Examples:  
test led  
test led all r 2  
test led cabinet 1  
test led c 1  
test led 1 long  
test memory  
This command performs hardware diagnostic tests on any or all memory circuit  
packs in the specified carrier. Both short and the long test are nondestructive  
when testing memory.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test memory  
2
2-355  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test memory  
location  
Physical location of the memory  
circuit pack: PC (cabinet number  
(optional) and carrier letter (a).  
init  
See  
below  
none  
inads  
craft  
nms  
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive test series (all  
nondestructive for this command).  
repeat  
number  
Number of times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test memory  
test memory a  
test memory a schedule  
test memory 1a2  
test memory b1 sh  
test memory b l r 25  
test memory a l c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Defaults  
The cabinet default is always 1. For SPE simplex systems, the default carrier is  
the “a” carrier. The defaults for the remaining parameters are short with a repeat  
of 1.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test memory  
2
2-356  
Output  
The following example shows the output for the test memory 1b command. The  
responses display on a test-by-test basis with one line of data for each test result.  
test memory 1b  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
Error Code  
01B  
01B  
MEM-BD  
MEM-BD  
87  
631  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
The port address (cabinet-carrier)  
Maintenance  
Name  
The name of maintenance object being tested is MEMORY.  
Alt. Name  
Test No.  
Result  
Not applicable.  
The test being executed  
The result of the test: Pass, Abort, or Fail  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test network-control  
2
2-357  
test network-control  
This command performs hardware diagnostic tests on a specified network  
control circuit pack.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
location  
Network control board carrier  
location (a)  
init  
inads  
craft  
Cabinet 1,  
carrier a,  
test  
sequence  
repeat = 1.  
none  
network-control  
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
Number of times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test network-control  
test network-control a l  
test network-control b sh r 2  
test network-control b l r 25  
test network-control a  
test network-control a c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear  
option forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears  
alarms pertinent to tests in the short sequence. SEE WARNING BELOW  
Refer to the Report Scheduler and System Printer feature specification for more details.  
!
WARNING:  
Since the “clear long” options clear all counters if tests pass, it is possible  
for firmware counters to be cleared even when a problem exists. In some  
cases customer service might degrade since calls may be routed over  
defective equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test network-control  
2
2-358  
Output  
The following example shows the output from the test network-control a  
command. The responses display on a test-by-test basis with one line of data for  
each test result.  
test network-control a  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
Error Code  
01A  
DATA-BD  
DATA-CHL  
DATA-CHL  
DATA-CHL  
SW-CTL  
SW-CTL  
SW-CTL  
SW-CTL  
12V-PWR  
CARD-MEM  
CARD-MEM  
CARD-MEM  
CARD-MEM  
CARD-MEM  
52  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
01A0101  
01A0101  
01A0101  
01A  
01A  
01A  
01A  
01A  
01A  
01A  
4001  
4001  
4001  
109  
110  
111  
95  
92  
94  
324  
701  
695  
696  
697  
698  
699  
01A  
01A  
01A  
Command Successfully Completed  
Field descriptions  
Port  
Port address: cabinet (always 1)-carrier-slot-circuit. For the  
DATA-BD, SW-CTL, 12V-PWR, and CARD-MEM maintenance  
objects, the slotand circuitfields of port address are blank.  
DATA-CHL (administered data channel) uses XXas the slot  
address and has a circuit number between 01 and 04. The carrier  
field has a value Afor the control carrier A in a simplex system.  
Maintenance  
Name  
The name of the maintenance object  
Alt. Name  
Extension number of the DATA-CHL, if administered. For other  
maintenance objects, this field is not applicable and, therefore,  
empty.  
Test No  
Result  
The test being executed  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test pkt  
2
2-359  
test pkt  
The test pkt runs a series of tests on the Packet bus of the specified PPN.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test pkt  
pn  
The Packet bus to be tested: nn (1)  
init  
Test  
none  
port-network  
number  
inads  
craft  
Sequence  
= short;  
Repeat =  
1
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test sequence  
(short or long) to repeat until the alarm  
(if any) is cleared or a single test in the  
1
sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to schedule  
execution of the command. The  
command is then placed in the  
command queue and is executed at  
the specified time. The information  
displayed by the command is sent to  
the system printer instead of the  
2
screen.  
Examples:  
test pkt port-network 1 l  
test pkt port-network 1 sh r 2  
test pkt port-network 1 sh schedule  
test pkt port-network 1 l r 25  
test pkt port-network 1  
test pkt port-network 1 c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear  
option forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears  
alarms pertinent to tests in the short sequence. SEE WARNING BELOW.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
!
WARNING:  
Since the “clear long” options clear all counters if tests pass, it is possible  
for firmware counters to be cleared even when a problem exists. In some  
cases customer service might degrade since calls may be routed over  
defective equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test packet-interface  
2
2-360  
Output  
The following example is the output for the test pkt port-network 1 command.  
The responses display on a test-by-test basis with one line of data for each test  
result.  
test pkt port-network 1  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
Error Code  
PN 01  
PN 01  
PN 01  
PKT-BUS  
PKT-BUS  
PKT-BUS  
571  
572  
573  
PASS  
PASS  
PASS  
Command successfully completed  
Field descriptions  
Port  
Port network number (1)  
Maintenance  
Name  
The name of maintenance object being tested.  
Alt. Name  
Test No  
Not applicable.  
The test being executed  
Result  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test packet-interface  
This command performs hardware diagnostic tests on the packet interface circuit  
packs in a specified carrier. Tests performed include local memory checksum  
tests and checks of failure counters.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test packet-interface  
2
2-361  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
pkt-interface  
location  
The packet interface to be tested: nn  
(cabinet 1-3 + carrier letter)  
init  
inads  
craft  
test  
see below  
sequence  
= short;  
repeat  
number =  
1
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test sequence  
(short or long) to repeat until the alarm  
(if any) is cleared or a single test in the  
1
sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to schedule  
execution of the command. The  
command is then placed in the  
command queue and is executed at  
the specified time. The information  
displayed by the command is sent to  
the system printer instead of the  
2
screen.  
Examples:  
test packet-interface 01a  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear  
option forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears  
alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Feature Interactions  
If the packet-interface circuit pack is in the “out-of-service” or “uninstalled”  
states, no demand, scheduled, periodic, or error tests can run. See also ‘‘reset  
packet-interface’’ and ‘‘status packet-interface’’.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test pms-link  
2
2-362  
Output  
The following example is the output for the test packet-interface 1a1 command.  
The responses display on a test-by-test basis with one line of data for each test  
result.  
test packet-interface 1a1  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01A  
01A  
PKT_INT  
PKT_INT  
887  
888  
PASS  
PASS  
Command Successfully Completed  
test pms-link  
This command performs the specified property management system link tests on  
the specified pms link by checking to see if the link is accessible and then  
performing a reset on the link (long test only). For general information on PMS  
links, see the description in the ‘‘busyout pms-link’’ section. For information on  
what a PMS is and does, see the description in the ‘‘status pms-link’’ section.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test pms-link  
2
2-363  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test pms-link  
short  
Option for a brief series of  
init  
Test  
See below  
nondestructive diagnostic tests.  
inads  
craft  
Sequence  
= short;  
Repeat =  
1
long  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test pms-link sh r 5  
test pms-link l  
test pms-link  
test pms-link c  
test pms-link c sch  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear  
option forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears  
alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Feature Interactions  
The maintenance of a particular component on a link may interfere with the  
maintenance of the link itself. Maintenance can put a link component in a busy  
state causing link set-up to fail. Frequent attempts at re-setup of a link may delay  
the recovery of a faulty component due to the maintenance test of a component  
only taking place when the component is idle. Therefore, the technician needs to  
be able to disable the attempted re-setup of a link. The busyout command is  
used to do this and causes the link to be torn down. If the link is already down,  
the busyout command stops periodic re-setup tries on the link.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test pms-link  
2
2-364  
Output  
The following example shows the output from the test pms-link l command. The  
responses display on a test-by-test basis with one line of data for each test result.  
test pms-link long  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
Error Code  
PMS-LINK  
214  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
Always blank  
Maintenance  
Name  
Always PMS-LINK  
Alt. Name  
Test No  
Not applicable.  
The test being executed  
Result  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test port  
2
2-365  
test port  
This command performs hardware diagnostic tests on an individual port circuit.  
In most cases, tests are performed on hardware connected to the port.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
location  
short  
Qualifier Description  
Permissions  
Defaults  
test port  
PCSSpp  
init  
inads  
craft  
Test  
none  
Sequence  
= short;  
Repeat =  
1
Option for a brief series of  
nondestructive diagnostic tests.  
long  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test port 01c1101 l  
test port 01c1101 l schedule  
test port 02e1502 sh r 2  
test port 02d1201 r 4  
test port 01c1101 c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence. SEE WARNING BELOW.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
!
WARNING:  
Since the “clear long” options clear all counters if tests pass, it is possible  
for firmware counters to be cleared even when a problem exists. In some  
cases customer service might degrade since calls may be routed over  
defective equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test port  
2
2-366  
Output  
The following example is the output for the test port command and assumes that  
the port in cabinet 1, carrier c, slot 7, circuit 1 is an analog port. The responses  
display on a test-by-test basis with one line of data for each test result.  
test port 01c0701 short  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01C0701  
01C0701  
01C0701  
ANL-LINE  
ANL-LINE  
ANL-LINE  
35  
48  
36  
PASS  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
Port address (cabinet-carrier-slot-circuit)  
The name of maintenance object.  
Maintenance  
Name  
Alt. Name  
The alternate means of identifying the maintenance object.  
If the Object is a The field contains  
station  
trunk  
extension  
xxx/yyy (xxx = trunk group number and yyy =  
member number)  
private CO line  
P/xxx (xxx = private CO line group number)  
Test No  
Result  
Test being executed.  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test pri-endpoint  
2
2-367  
test pri-endpoint  
This command performs hardware diagnostic tests on all port circuits  
(B-channels) that are associated with the specified PRI endpoint.  
Action/Objec  
Feature  
t
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
extension  
PRI endpoint extension to be  
init  
Test  
none  
pri-endpoint  
tested (must conform to dial-plan)  
inads  
craft  
nms  
Sequence  
= short;  
Repeat =  
1
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test pri-endpoint 25012  
test pri-endpoint 45002 sh  
test pri-endpoint 45892 l  
test pri-endpoint 24389 sh r 4  
test pri-endpoint 34899 l r 6  
test pri-endpoint 34912 l r 5  
schedule  
test pri-endpoint 93483 r 2  
test pri-endpoint 10022 c  
test pri-endpoint 92349 schedule  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test pri-endpoint  
2
2-368  
Output  
The following output example is for the test pri-endpoint 22501 command and  
assumes that the PRI endpoint ports for extension 22501 are in cabinet 1, carrier  
B, slot 20, circuits 1 to 3. The responses display on a port-by-port and  
test-by-test basis with one line of data for each test result.  
test pri-endpoint 22501 short  
page 1 of 1  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01B2001  
01B2001  
01B2001  
01B2001  
01B2002  
01B2002  
01B2002  
01B2002  
01B2003  
01B2003  
01B2003  
01B2003  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
PE-BCHL  
22501  
22501  
22501  
22501  
22501  
22501  
22501  
22501  
22501  
22501  
22501  
22501  
36  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
255  
256  
257  
36  
255  
256  
257  
36  
255  
256  
257  
Command Successfully Completed  
Field descriptions  
Port  
The port address (cabinet-carrier-slot-circuit)  
The maintenance object name (PE-BCHL)  
Maintenance  
Name  
Alt. Name  
Test No  
The specified extension number of the PRI endpoint.  
The actual test being executed  
Result  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test processor  
2
2-369  
test processor  
This command performs hardware diagnostic tests on a specified processor  
circuit pack.  
Feature  
Action/Object  
Qualifier  
location  
short  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
processor  
Cabinet number (a)  
init  
inads  
craft  
See  
below  
none  
Option for a brief series of  
nondestructive diagnostic tests.  
long  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test processor  
test processor schedule  
test processor a  
test processor 1a  
test processor a sh  
test processor a l c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Defaults  
■
■
For SPE simplex systems, the location is optional and defaults to cabinet  
1, carrier a.  
Defaults for the remaining parameters are short with a repeat of 1.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test processor  
2
2-370  
Output  
The following output example is for the test processor a command. The  
responses display on a test-by-test basis with one line of data for each test result.  
test processor a  
SPE B  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01A  
01A  
01A  
01A  
01A  
01A  
01A  
01A  
01A  
01A  
PROCR  
PROCR  
PROCR  
PR-MAINT  
PR-MAINT  
PR-MAINT  
PR-MAINT  
PR-MAINT  
MEMORY  
77  
80  
82  
102  
103  
106  
228  
229  
87  
PASS  
PASS  
PASS  
ABORT  
ABORT  
PASS  
PASS  
ABORT  
PASS  
PASS  
1018  
1018  
1018  
MEMORY  
631  
Command successfully completed  
Field descriptions  
Port  
The port address (cabinet-carrier)  
Maintenance  
Name  
Maintenance object being tested is MEMORY.  
Alt. Name  
Test No.  
Result  
Not applicable.  
Test being executed  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test signaling-group  
2
2-371  
test signaling-group  
This command validates that the specified signaling group is administered and  
runs a series of diagnostic tests that return results of the test along with possible  
error codes. A signaling group is a collection of B-channels signaled for by a  
designated single D-channel or set of D-channels over an ISDN-PRI.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
group  
identifier  
The station extension (must  
conform to dial-plan)  
init  
inads  
craft  
Test  
See below  
signaling-group  
Sequence  
= short;  
Repeat =  
1
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test signaling-group 1  
test signaling-group 1 repeat 10  
test signaling-group 2 short  
test signaling-group 4 long  
test signaling-group 4 long clear  
test signaling-group 2 schedule  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear  
option forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears  
alarms pertinent to tests in the short sequence. SEE WARNING BELOW.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
!
WARNING:  
Since the “clear long” options clear all counters if tests pass, it is possible  
for firmware counters to be cleared even when a problem exists. In some  
cases customer service might degrade since calls may be routed over  
defective equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test sp-link  
2
2-372  
Feature Interactions  
Additional data is available after running a test. See the status signaling-group  
command for how to access the additional data.  
Output  
The following output example is for the test signaling-group 1 command. The  
responses display on a test-by-test basis with one line of data for each test result.  
test signaling-group 1  
SPE A  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
1
1
1
ISDN-SGR  
ISDN-SGR  
ISDN-SGR  
636  
639  
637  
PASS  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
The signaling group number (1-8) of the signaling group that is  
being tested.  
Maintenance  
Name  
The type of maintenance object that is being tested.  
Alt. Name  
Test No  
Not Applicable.  
Test being executed  
Result  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test sp-link  
The test sp-link command validates that the system printer link is administered  
and runs a series of diagnostic tests that return results of the test along with  
possible error codes.  
The system printer link is a link from the switch to an external printer over which  
jobs can be printed. This link is created by administering the system printer  
extension and setting up a call to the system printer.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test sp-link  
2
2-373  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test sp-link  
short  
Option for a brief series of  
init  
short  
none  
nondestructive diagnostic tests.  
inads  
craft  
long  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
Examples:  
test sp-link  
test sp-link sh  
test sp-link l  
test sp-link schedule  
test sp-link sh sch  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
The following output example is for the test sp-link command. The responses  
display on a test-by-test basis with one line of data for each test result.  
test sp-link  
SPE A  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
SYS-PRNT  
SYS-PRNT  
215  
213  
PASS  
PASS  
Command Successfully Completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test station  
2
2-374  
Field descriptions  
Port  
Not applicable; always blank  
Maintenance  
Name  
The name of the maintenance object  
Alt. Name  
Alternate means of identifying the maintenance object. This field  
contains the extension when the object is a data module.  
Test No  
Result  
Test being executed  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test station  
This command performs hardware diagnostic tests on an individual port circuit  
assigned to that extension. The technician must specify the extension and a  
translation is automatically done to the physical port location.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test station  
2
2-375  
Action/  
Feature  
Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test station  
extension  
The station extension (must  
conform to dial-plan)  
init  
Test  
none  
inads  
craft  
cust  
nms  
Sequence  
= short;  
Repeat =  
1
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test station 81709 l  
test station 85136 s r 2  
test station 85036 l r 25  
test station 85036 l r 25 schedule  
test station 84297 r 4  
test station 81709 c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence. SEE WARNING BELOW.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
!
WARNING:  
Since the “clear long” options clear all counters if tests pass, it is possible  
for firmware counters to be cleared even when a problem exists. In some  
cases customer service might degrade since calls may be routed over  
defective equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test synchronization  
2
2-376  
Output  
The following screen is an example of the output from the test station 81902  
short command with the assumptions that port in cabinet 1, carrier c, slot 7,  
circuit 1 is an analog port and extension 81902 is connected to that port. The  
responses display on a test-by-test basis with one line of data for each test result.  
test station 81902 short  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01C0701  
01C0701  
01C0701  
ANL-LINE  
ANL-LINE  
ANL-LINE  
35  
48  
36  
PASS  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
The port address: cabinet-carrier-slot-circuit  
Maintenance  
Name  
The type of maintenance object that is being tested.  
Alt. Name  
Alternate means of identifying the maintenance object. This field  
contains the extension when the object is a station.  
Test No  
Result  
Test being executed  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test synchronization  
This command updates all the boards with the correct synchronization source  
and parameters. The system sends a downlink message to the tone clock and  
DS1 boards to place them in the correct synchronization configuration, providing  
error-free digital communication between the switch and other PBXs, COs, or  
customer premise equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test synchronization  
2
2-377  
Action/  
Feature  
Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test synch  
short  
Option for a brief series of  
init  
Test  
none  
nondestructive diagnostic tests.  
inads  
craft  
Sequence  
= short;  
Repeat =  
1
long  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test synchronization r 3  
test synchronization sh r 1  
test synchronization sh r 1  
schedule  
test synchronization l  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option  
only clears alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test sys-link  
2
2-378  
Output  
The following screen is an example of the output for the test synchronization  
short command. The responses are displayed on a test-by-test basis with one  
line of data for each test result.  
test synchronization short  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
SYNC 417 PASS  
Error Code  
Command Successfully Completed  
Field descriptions  
Port  
Not applicable  
Maintenance  
Name  
Maintenance object name  
Alt. Name  
Test No.  
Result  
Not applicable  
Test being executed  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
test sys-link  
This command validates the specified link and runs diagnostic tests on the  
hardware objects that comprises the system link. If the current or faulted options  
are specified, tests are run on all hardware objects that comprise the specified  
link. If current or faulted is not specified, only the end-to-end sys-link connection  
is tested.  
The hardware path that comprises a system link consists of up to 21 hardware  
components that affect the behavior of the link. The number of components of a  
given system link hardware path depends on the system configuration and type  
of system link.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test sys-link  
2
2-379  
Action/  
Feature  
Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
sys-link  
location  
Port location associated with the system  
link.  
init  
inads  
craft  
none  
current  
faulted  
Current hardware path tested  
Tests the hardware path of the system  
link as it was constituted when a fault  
last caused the link to go down.  
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test sequence  
(short or long) to repeat until the alarm (if  
any) is cleared or a single test in the  
1
sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to schedule  
execution of the command. The  
command is then placed in the  
command queue and is executed at the  
specified time. The information  
displayed by the command is sent to the  
2
system printer instead of the screen.  
Examples:  
test sys-link 2e0201 current schedule  
test sys-link 2e0201 faulted r 10  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long  
clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test sys-link  
2
2-380  
Output  
The following example shows the output from the test sys-link 01A0516 current  
command.  
test sys-link 01A0516 current  
Page  
1
SPE A  
TEST RESULTS  
Maintenance Name Alt. Name Test No. Result  
Port  
Error Code  
01A0516  
01A  
01A  
PN 01A  
PN 01A  
SYS-LINK  
PKT-INT  
PKT-INT  
TDM-BUS  
TDM-BUS  
PRI  
985  
886  
887  
294  
296  
PASS  
PASS  
PASS  
PASS  
PASS  
press CANCEL to quit -- press NEXT PAGE to continue  
Field descriptions  
Port  
Port address  
Maintenance  
Name  
Maintenance object name  
Alt. Name  
Test No.  
Result  
Alternate means of identifying the link  
Test being executed  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test tdm  
2
2-381  
test tdm  
This command tests all the time slots on a bus associated with a PPN or an EPN.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
test tdm  
pn number  
nn = number of the port network to  
have its TDM bus tested. Both  
halves (“a” and “b”) of the TDM  
bus are tested.  
init  
inads  
craft  
Test  
none  
Sequence  
= short;  
Repeat = 1  
short  
long  
Option for a brief series of  
nondestructive diagnostic tests.  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat number  
clear  
How many times each test in the  
sequence is repeated (1-100)  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test tdm port-network 1 l  
test tdm port-network 2 sh r 2  
test tdm port-network 2 sh sch  
test tdm port-network 1 l r 25  
test tdm port-network 2  
test tdm port-network 1 c  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear  
option forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears  
alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test tdm  
2
2-382  
Output  
The following example shows the output for the test tdm port-network 1  
command. The responses display on a test-by-test basis with one line of data for  
each test result.  
test tdm port-network 1  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
Error Code  
PN 01A TDM-BUS  
PN 01A TDM-BUS  
PN 01A TDM-BUS  
PN 01B TDM-BUS  
PN 01B TDM-BUS  
PN 01B TDM-BUS  
294  
296  
297  
294  
296  
297  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
For TDM-BUS maintenance object the port network number and  
the bus (A or B) is displayed.  
Maintenance  
Name  
Maintenance object name  
Alt. Name  
Test No  
Not applicable.  
Test being executed  
Result  
Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test tone-clock  
2
2-383  
test tone-clock  
The test tone/clock command performs hardware diagnostic tests on a specified  
tone or clock circuit pack.  
Feature  
Action/Object  
Qualifier  
location  
short  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
tone-clock  
PCSS  
init  
inads  
craft  
Test  
none  
Sequence  
= short;  
Repeat =  
1
Option for a brief series of  
nondestructive diagnostic tests.  
long  
Option for a longer, more  
comprehensive series of both  
destructive and nondestructive  
diagnostic tests.  
repeat  
number  
How many times each test in the  
sequence is repeated (1-100)  
clear  
This option causes the test  
sequence (short or long) to repeat  
until the alarm (if any) is cleared or  
1
a single test in the sequence fails.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
2
printer instead of the screen.  
Examples:  
test tone-clock 01a l  
test tone-clock 01b l schedule  
1
2
If no alarms are registered against the maintenance object then the test sequence is run only once. The long clear  
option forces a clear of all alarms if no errors are encountered during testing. The short clear option only clears  
alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test tone-clock  
2
2-384  
Output  
The following is the output for the test tone-clock 1a command. The responses  
display on a test-by-test basis with one line of data for each test result.  
test tone-clock 1a  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
Error Code  
01A  
01A  
01A  
01A  
01A  
01A  
01A  
01A  
01A  
TONE-BD  
TONE-BD  
TONE-PT  
TONE-PT  
TDM-CLK  
TDM-CLK  
TDM-CLK  
TDM-CLK  
TDM-CLK  
46  
52  
40  
41  
148  
149  
150  
151  
574  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
The port address: cabinet-carrier-slot-circuit  
Maintenance  
Name  
Maintenance object name: TONE-BD, TONE-PT, and TDM-CLK.  
Alt. Name  
Test No  
Not applicable.  
Test being executed  
Result  
Test result: Pass, Abort, Fail, No Board, Disabled, or Extra Bd.  
Error Code  
Numeric code explaining why the release failed or aborted. Refer  
to the detailed list of the codes by test number for each MO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test trunk  
2
2-385  
test trunk  
This command performs hardware diagnostic tests on an entire trunk group or an  
individual trunk group member, depending on the options entered.  
Action/  
Object  
Feature  
Interactions  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
test trunk  
group  
number  
Administered group number (1-99)  
init  
Test Seq. =  
short;  
Repeat = 1  
none  
inads  
craft  
cust  
member  
number  
Administered number identifying a  
particular trunk within a trunk group (1-99).  
short  
long  
Command executes a series of  
nondestructive diagnostic tests.  
Command executes a more  
comprehensive and longer version of the  
both destructive and nondestructive  
diagnostic tests.  
repeat  
number  
How many times each test in the sequence  
is repeated (1-100)  
clear  
This option causes the test sequence (short  
or long) to repeat until the alarm (if any) is  
cleared or a single test in the sequence  
1
fails.  
schedule  
Command is validated and then a  
scheduling form displays to schedule  
execution of the command. The command  
is then placed in the command queue and  
is executed at the specified time. The  
information displayed by the command is  
sent to the system printer instead of the  
2
screen.  
Examples:  
test trunk 78 l  
test trunk 80/1 sh r 2  
test trunk 78/2 l r 25  
test trunk 78/2 l r 25 schedule  
test trunk 80  
test trunk 80 schedule  
test trunk 78 r 4  
test trunk 78 c  
1
2
If no alarms are registered against the maintenance object then the test sequence will be exercised only once. The  
long clear option forces a clear of all alarms if no errors are encountered during testing. The short clear option only  
clears alarms pertinent to tests in the short sequence.  
Refer to the Report Scheduler and System Printer feature specification for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test trunk  
2
2-386  
Output  
The following screen is an example of the output for the test trunk 78 command.  
The responses display on a test-by-test basis with one line of data for each test  
result.  
test trunk 78  
TEST RESULTS  
Port  
Maintenance Name Alt. Name Test No. Result  
Error Code  
01C1505  
01C1505  
CO-TRK  
CO-TRK  
078/001  
078/001  
3
36  
PASS  
PASS  
Command Successfully Completed  
Field descriptions  
Port  
The port address: cabinet-carrier-slot-circuit  
The name of maintenance object being tested.  
Maintenance  
Name  
Alt. Name  
The alternate means of identifying the maintenance object. If the  
object is a trunk, the field contains xxx/yyy(where xxx = trunk  
group number, yyy = member number). If the object is a private  
CO line, the field contains P/xxx(where xxx = private CO line  
group number).  
Test No  
Result  
The test number being executed  
The result of the individual test: PASS, ABORT, FAIL, NO BOARD,  
DISABLED, and EXTRA BD.  
Error Code  
A system-generated number indicating the reason that the test for  
the named MO failed or aborted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
test tsc-administered  
2
2-387  
test tsc-administered  
This command submits a switched services request to run the Temporary  
Signaling Connection’s heartbeat test for all administered TSCs on a signaling  
group.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
test  
signaling  
group  
number/  
Signaling group number (1–8)  
init  
inads  
craft  
repeat =  
1
Additional  
data  
available  
after  
running the  
test. See  
status  
tsc-admini  
stered for  
how to  
tsc-administered  
tsc index  
The number associated with each  
TSC in a signaling group.  
repeat  
number  
The number of times each test in  
sequence is repeated.  
schedule  
Command is validated and then a  
scheduling form displays to  
schedule execution of the  
access  
additional  
data.  
command. The command is then  
placed in the command queue and  
is executed at the specified time.  
The information displayed by the  
command is sent to the system  
1
printer instead of the screen.  
1
Refer to the Report Scheduler and System Printer feature specification for more details.  
Output  
The following is an example of the output from the test tsc-administered 1/1  
command. The responses display on a test-by-test basis with one line of data for  
each test result.  
test tsc-administered 1/1  
TEST RESULTS  
Port  
1/1  
Maintenance Name Alt. Name Test No. Result  
Error Code  
TSC-ADM  
604  
PASS  
Command Successfully Completed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
traceroute  
2
2-388  
Field descriptions  
Port  
Port address of the administered temporary signaling connection  
(format = signaling group no./tsc index)  
Maintenance  
Name  
The name of the maintenance object  
Alt. Name  
Test No.  
Result  
Not applicable  
The test number being executed  
Test result: Pass, Abort, Fail, No Board, Disabled, or Extra Bd.  
Error Code  
A system-generated number indicating the reason that the test  
for the named MO failed or aborted.  
traceroute  
This command provides the ability to trace the route of packets originated from  
DEFINITY IP boards through the LAN. The output shows the ip address of each  
router or host (hop) that the packets encounter and the time elapsed between  
each hop. If a DEFINITY IP board has trouble communicating with a far-end  
device, the traceroute command can determine “how far” packets get toward  
the destination.  
DEFINITY IP boards include:  
■
TN799B (or later suffix) CLAN board  
TN802B Medpro board  
■
The output form lists:  
■
■
■
Hops traversed from source to destination  
IP addresses of the hop points and the final destination  
Observed round-trip delay from the source to each hop point  
If no reply is received from a potential hop point, the IP Addressfield contains  
stars (*), which indicates a timeout condition.  
The primary use of this command is to determine quickly and unambiguously if  
the fault lies within Lucent-provided equipment or if the fault is with the LAN or  
LAN administration to which the DEFINITY ECS switch is connected.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
traceroute  
2
2-389  
Action/  
Feature  
Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
traceroute  
ip-address  
where IP address is  
www.xxx.yyy.zzz  
init  
inads  
craft  
Primary  
None  
node-name from node-name form  
customer  
board  
cabinet-carrier-slot  
address of the IP circuit  
pack  
clan-port  
port 1-17  
Example:  
traceroute ip-address  
123.4.56.789  
board 1C14  
Output  
The following shows an example output for the C-LAN traceroute command. For  
Medpro or Prowler boards, the clan-port (1-17) qualifier does not appear.  
traceroute ip-address 135.9.1.22 board 1C14 clan-port (1-17)  
TRACE ROUTE RESULTS  
Hop  
Time(ms)  
IP Address  
0
1
2
3
4
from address  
03,10,05  
11,20,03  
22,01,25  
22,01,25 !N  
135.9.1.22  
134.9.14.23  
134.9.5.103  
106.245.27.205  
106.245.27.205  
Field descriptions  
clan-port  
This CLAN entry identifies the port on the CLAN board from which  
the traceroute command is issued. This field appears only if the  
board is a CLAN board.  
Hop  
The node number (in sequence). The first node (0) is the address  
from which the traceroute command is issued.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
upgrade software  
2
2-390  
Time (ms)  
Time from the board to each intermediate destination in  
milliseconds. If an error occurs at a node, the entry is repeated  
with an error code immediately following the time. Error codes and  
their meanings are:  
■ !  
Unable to reach port  
■ !N  
■ !H  
■ !P  
■ !F  
■ !S  
■ !X  
Unable to reach network  
Unable to reach host  
Failure between endpoints  
Need fragmentation of data packet  
Source return failure  
Packet blocked by filter  
IP Address  
The 32-bit network address.  
upgrade software  
This command upgrades the software text image, the flash component of the  
LMM firmware, the MTPfirmware, and the Processor Interface (PI) firmwares. In a  
simplex system, the command verifies that a software card-mem is present and  
then, if present, proceeds to reprogram the flash memory and perform a level-4  
restart. During the restart of the system, the system technician is prompted to  
replace the software card-mem with the translation card-mem. Service is  
provided upon completion of the system restart. Service down time is 5-12  
minutes.  
!
WARNING:  
Be sure to save translations before this executing this command. It may  
also be helpful to read the Feature Interactions for this command before  
upgrading the system software.  
Feature  
Action/Object  
Qualifier  
Qualifier Description  
Permissions  
Defaults  
Interactions  
upgrade  
software  
none  
init  
inads  
craft  
none  
See below  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
upgrade software  
2
2-391  
Feature Interactions  
System Restarts  
An upgrade causes a system restart: simplex systems perform a Level-4 restart,  
and duplex systems perform a Level-2 SPE-interchange after the standby is  
upgraded through a Level-4 restart.  
Initcauses  
Executing display initcauses shows the software upgrade and the system reset  
level.  
Multi-User Contention  
When this command is executing, all other maintenance commands are blocked.  
Exceptions to these are most of the status or display commands. All  
administration commands are not blocked. It is the user’s responsibility to make  
sure that no new translations are added between the last save translation  
operation and the completion of the upgrade software command.  
Recent Change History Log  
The upgrade software command will not be logged for both simplex and duplex  
systems. This is due to the clearing of memory during the level 4 reset.  
Periodic and Scheduled Maintenance  
Periodic and scheduled maintenance is suspended during the upgrade.  
Error and Alarm Log  
Error and alarm logs before the software upgrade are lost.  
Demand Busyout Objects  
Maintenance objects that have been demand busyout are released when the  
processor reboots or interchanges during the software upgrade. If the command  
is cancelled before the actual reboot or interchange starts, then all demand  
busyout objects status are preserved.  
Data Consistency between SPEs  
Data consistency alarms are generated if the software in the active and standby  
SPE are not consistent.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
upgrade software  
2
2-392  
Disabled Objects  
All disabled objects retain their “disabled” status after a software upgrade  
according to the status recorded in the last save translation command.  
Output  
The following is the output from the upgrade software command and a  
successful simplex upgrade.  
INITIATING SOFTWARE UPGRADE  
MEM-CARD CHECKSUM  
PASSED  
PASSED  
PASSED  
PASSED  
PASSED  
REPROGRAMMING MTP  
ERASING MEMORY  
REPROGRAMMING SPE  
FLASH TEXT CHECKSUM  
UPGRADE COMPLETE  
<beep>  
REPLACE SOFTWARE MEM-CARD WITH TRANSLATION MEM-CARD  
<beep>  
Explanations and error recoveries to the above steps follow:  
INITIATING SOFTWARE  
UPGRADE:  
The system is upgrading the software.  
MEM-CARD CHECKSUM:  
If the card-mem checksum fails, the system reboots  
without performing the upgrade. Retry the command with  
another software card-mem.  
REPROGRAMMING MTP:  
If the MTP programming fails, the Manager I will not be  
functional anymore, meaning that the rest of the upgrade  
(if it occurs) will not be visible and the MTP will not be  
present to monitor the health of the processor. The only  
recovery procedure is to power down and power up the  
system, since the presence of a software card-mem will  
cause a software upgrade.  
ERASING MEMORY:  
The rest of the memory is being erased.  
REPROGRAMMING SPE:  
This shows the status of the reprogramming. A total of 7  
Mbytes has to be reprogrammed. If the reprogramming  
fails in the midst of upgrade, it will take the system into  
SPE-down mode. In this mode, the system technician can  
only reset the system or display alarms. The system  
should be reset and another upgrade attempted due to  
the detection of a software card-mem in the system.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
upgrade software  
2
2-393  
FLASH TEXT CHECKSUM:  
If the checksum fails, the software may or may not be  
healthy, but it will try to run for as long as it can until further  
system reset through system technician intervention.  
REPLACE SOFTWARE  
MEM-CARD WITH  
TRANSLATION  
The system technician is prompted by a beep and this text  
string on the Manager I to replace the software card-mem  
with the translation card-mem. The system boots without  
translation if the replacement is not done within 2 minutes.  
The only way to recover from this is to replace the  
card-mem and issue a reset system 3 to read in the  
translations again.  
MEM-CARD:  
UPGRADE COMPLETE:  
The software upgrade is complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Commands  
upgrade software  
2
2-394  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
12V-PWR (12 Volt Power Supply)  
3-1  
Maintenance Objects  
3
NOTE:  
This document is not intended to solve all troubles. When the limits of these  
procedures are reached and the problem is not resolved, escalate the  
problem to a higher level of technical support. Escalation must conform to  
the procedures in the Technical and Administration Plan.  
12V-PWR (12 Volt Power Supply)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
Run  
Full Name of MO  
12 Volt Power Supply  
12 Volt Power Supply  
12V-PWR  
12V-PWR  
MINOR  
WARNING  
test card-mem sh  
test card-mem sh  
The 12 Volt Power Supply unit in the Processor circuit pack is required for  
programming the on-board flash memory devices and the removable translation  
card. During the erase and write operations of a flash memory or translation card,  
the 12 volt power supply must be turned on by the software. For the read-only  
operation, the 12 volt power supply is not required.  
If the 12-volt power supply cannot be turned on, all the erase and write  
operations to a flash device fail. Commands such as save translation and save  
announcements and features such as system upgrade, hard patching, and core  
dump always fail in this case.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
12V-PWR (12 Volt Power Supply)  
3-2  
Error Log Entries and Test to Clear Values  
Table 3-1. 12 Volt Power Supply Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Test to Clear  
Associated Test  
Alarm Level  
Any  
Value  
1
0
1
0
Any  
Any  
ON  
test card-mem  
test card-mem  
2
Any  
12 Volt Power Supply Test  
(#701)  
MINOR  
3
257  
Any  
12 Volt Power Supply Test  
(#701)  
WARNING  
ON  
test card-mem  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Software cannot turn on the 12 volt power supply to provide 12 volt power to the flash memory or to  
the translation card.  
3. Software can turn on the 12 volt power supply, and 12 volt power is available. However, the software  
cannot turn the power supply off after operations are completed. The 12 volt power remains on. This  
error does not affect the normal operations involved in accessing the memory or the translation  
card.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following table. By clearing  
error codes associated with the 12 Volt Power Supply Test for example, you may  
also clear errors generated from other tests in the testing sequence. The 12 Volt  
Power Supply Test can be initiated through either the test card-mem command  
or the test network-control command.  
Table 3-2. System Technician-Demanded Tests: 12-V PWR  
Short Test  
Sequence  
Long Test  
Sequence  
Reset Board  
Sequence  
1
Order of Investigation  
12 Volt Power Supply Test (#701)  
Memory Card Insertion Test (#695)  
D/ND  
ND  
X
X
X
X
X
X
X
X
X
X
2
ND  
2
Memory Card Format and Read Test (#696)  
ND  
2
Memory Card Match Test (#697)  
ND  
2
Memory Card Write-Protected Test (#698)  
ND  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
12V-PWR (12 Volt Power Supply)  
3-3  
Table 3-2. System Technician-Demanded Tests: 12-V PWR — Continued  
Short Test  
Sequence  
Long Test  
Sequence  
Reset Board  
Sequence  
1
Order of Investigation  
D/ND  
Memory Card Directory Recovery Test  
(#699)  
X
X
X
X
ND  
ND  
ND  
2
Memory Card Translation Data Integrity Test  
2
(#694)  
2
Memory Card Erase/Write/Read Test (#693)  
1. D = Destructive; ND = Nondestructive  
2. Refer to ‘‘CLAN-BD (Control LAN Circuit Pack)’’ information for a description of this test.  
12 Volt Power Supply Test (#701)  
This test is nondestructive. The purpose of the test is to diagnose the 12 volt  
power supply unit in the TN798 Processor circuit pack. No erase and  
write-to-memory operations are started or verified during the test. The contents of  
flash memory and of the memory card should not be changed.  
The test turns on the power supply and verifies that 12 volt power appears by  
reading the control register in the Processor circuit pack. After the power supply  
is turned on, the maintenance software waits for three seconds before verifying  
the appearance of 12 volt power. After the 12 volt power supply can be turned on  
and verified, the test turns the power supply off and then verifies that the power is  
off. The control register is read again for the verification.  
If, while this test is running, an application attempts to erase or write a flash  
memory or a memory card, this test remains active, and the application is barred.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
12V-PWR (12 Volt Power Supply)  
3-4  
Table 3-3. 12 Volt Power Supply Test  
Error  
Code  
Test Result  
Description/Recommendation  
1192  
ABORT  
12 volt power supply is being used by other applications or by  
maintenance.  
1. The 12 volt power supply is in use. Retry the test card-mem  
command after the maintenance operation application is completed.  
2106  
2114  
109  
ABORT  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The 12 volt power supply unit in the TN798 cannot be turned on by the  
software.  
1. Retry the test card-mem command one more time to verify the  
operation of the 12 volt power supply in the TN798.  
2. If the failure indicated by Error Code 109 persists, the TN798 must  
be replaced. Follow the standard procedure for replacing the  
TN798.  
3. After the new Processor circuit pack is inserted, enter the test  
card-mem command to verify the operations of the 12 volt power  
supply.  
110  
FAIL  
The 12 volt power supply unit in the TN798 cannot be turned off by the  
software.  
1. Retry the test card-mem command one more time to verify the  
operation of the 12 volt power supply.  
2. If the failure indicated by Error Code 110 persists, the TN798 should  
be scheduled for replacement during the next regular maintenance  
visit. This failure does not cause any service disruption.  
PASS  
The 12 volt power supply unit in the TN798 is functioning correctly.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADM-CONN (Administered Connection)  
3-5  
ADM-CONN (Administered  
Connection)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
Full Name of MO  
Administered Connection  
Administered Connection  
Administered Connection  
ADM-CONN  
ADM-CONN  
ADM-CONN  
MAJOR  
MINOR  
status administered-connection N  
status administered-connection N  
status administered-connection N  
WARNING  
1. Where N is an appropriate Administered Connection number determined via the PORT field from the  
Alarm or Error Log.  
An Administered Connection provides an end-to-end connection between two  
access endpoints or data modules. This connection is automatically established  
when the administered connection is administered and is due to be active. An  
error is logged when an administered connection cannot be established or when  
an established administered connection fails. An alarm is logged when a  
connection cannot initially be established or fails and cannot be reestablished.  
An alarming strategy is supported on a per administered connection basis. An  
alarm is raised for a connection when either the number of consecutive failed  
attempts to establish the connection reaches the alarm threshold or it can be  
determined that a failed attempt to establish was due to an administered error.  
The alarm raised ("major," "minor," "warning," or "none") is specified in the "Alarm  
Type" field of the Administered Connection Administration Form.  
Error Log Entries and Test to Clear Values  
Table 3-4. Administered Connection Error Log Entries  
Associated  
Test  
Alarm  
Level  
On/Off  
Board  
Test to Clear  
Value  
Error Type  
0 (a)(b)(c)(k)  
1 (a)(b)(c)(d)(e)  
2 (a)(b)(c)(f)  
Aux Data  
Any  
None  
None  
None  
None  
None  
None  
None  
None  
Any  
OFF  
None  
None  
None  
None  
None  
None  
None  
None  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
Any  
6 (a)(b)(c)(g)  
16 (a)(b)(c)(k)  
17 (a)(c)(h)  
Any  
Any  
Any  
18 (a)(b)(c)(i)  
21 (a)(b)(c)(g)  
Any  
Any  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADM-CONN (Administered Connection)  
3-6  
Table 3-4. Administered Connection Error Log Entries — Continued  
Associated  
Test  
Alarm  
Level  
On/Off  
Board  
Test to Clear  
Value  
Error Type  
22 (a)(b)(c)(d)(j)  
28 (a)(b)(c)(d)(e)  
29 (a)(b)(c)(k)  
31 (a)(b)(c)(g)  
34 (a)(b)(c)(l)  
Aux Data  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
Any  
OFF  
None  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
38 (a)(b)(c)(m)  
40 (a)(b)(c)(l)  
41 (a)(b)(c)(m)  
42 (a)(b)(c)(l)  
43 (a)(b)(c)(q)  
44 (a)(b)(c)(l)  
50 (a)(b)(c)(d)(n)  
52 (a)(b)(c)(d)(o)  
54 (a)(b)(c)(o)  
58 (a)(b)(c)(l)  
65 (a)(b)(c)(d)(p)  
66 (a)(b)(c)(d)(p)  
69 (a)(b)(c)(d)(p)  
81 (a)(b)(c)(q)  
82 (a)(b)(c)(r)  
88 (a)(b)(c)(d)(s)  
91 (a)(b)(c)(q)  
95 (a)(b)(c)(q)  
96 (a)(b)(c)(q)  
97 (a)(b)(c)(q)  
98 (a)(b)(c)(q)  
99 (a)(b)(c)(q)  
100 (a)(b)(c)(q)  
102 (a)(b)(c)(i)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADM-CONN (Administered Connection)  
3-7  
Table 3-4. Administered Connection Error Log Entries — Continued  
Associated  
Test  
Alarm  
Level  
On/Off  
Board  
Test to Clear  
Value  
Error Type  
111 (a)(b)(c)(q)  
127 (a)(b)(c)(g)  
Aux Data  
Any  
None  
None  
Any  
Any  
OFF  
OFF  
None  
None  
Any  
Notes:  
a. These errors have no specific test associated with them. Refer to Notes b  
through p for an explanation and appropriate action.  
b. These errors are valid only for administered connection established over  
ISDN facilities; only error 127 is valid for administered connection  
established over non-ISDN facilities (or between two endpoints on the  
same switch).  
■
Aux Data 1—Administered connection establishment failed  
■
Aux Data 2—Active administered connection failed; attempting  
reestablishment via auto restoration  
■
■
Aux Data 3—Auto restoration failed  
Aux Data 4—Active administered connection failed; attempting  
reestablishment via fast retry  
■
Aux Data 5—Fast retry failed  
c. These errors are typically associated with administrative problems and are  
not expected to be of a temporary nature. Therefore, the administered  
connection is not retried and the failure is alarmed immediately (the alarm  
threshold specified by the customer is ignored).  
d. The address of the destination endpoint is: an unassigned number (1);  
has an invalid number format (28); or is restricted form terminating calls  
("Access Denied") [due to COR (Class of Restriction)]. Verify that the  
destination address is correct and that the destination endpoint is  
administered. The destination endpoint is not administered on the switch  
where this error is logged.  
e. A request has been made to use a transit network or common carrier that  
cannot be accessed. Check the routing pattern used by this Administered  
Connection and verify that the inter-exchange carrier specified is correct.  
f. The exact failure cause is unknown or has been mapped to one of these  
values. If this is not a temporary condition, try reversing the direction of the  
Administered Connection (that is, originate the Administered Connection  
from the destination switch). This may yield another failure cause.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADM-CONN (Administered Connection)  
3-8  
g. The destination endpoint is not available. Check the status of the  
destination endpoint (using status access-endpoint or status  
data-module) and verify that the endpoint is not busy or otherwise  
unavailable (for example, out-of-service). The status for the destination  
endpoint is not available on the switch where this error is logged.  
h. This switch sent an ISDN message to another switch, which either did not  
respond (18) or did not respond within the allotted time (102). This could  
be due to link failure or congestion or outage at the other switch.  
i. The address of the destination endpoint has changed. Verify that the new  
address is correct and change the Administered Connection accordingly.  
The destination endpoint is not administered on the switch logging this  
error.  
j. Indicate that a resource (for example, a circuit or bearer capability)  
required by the administered cConnection is not presently available.  
k. A network failure (38) or temporary failure (41) has occurred. Error Log  
entries for other maintenance objects (for example, DS1-BD or ISDN-LNK)  
may indicate a local problem.  
l. A request to use a network service has been denied because the service  
has not been purchased. Check the routing pattern used by this  
Administered Connection and verify that the service type is correct. If the  
service type appears correct, check with the customer or network provider  
or both to determine what services have been purchased by the customer.  
m. Indicate that outgoing calls may be barred on the originating switch (52)  
or that incoming calls may be barred on the destination switch (54). To  
restore an administered connection failure, issue the status administered  
connection command for current administered connection state (observe  
the retry count). If the administered connection state is "failed," then verify  
and correct the Administered Connection Administration Form.  
n. The requested bearer capability (65), channel type (66), or facility (69) is  
not implemented or is unknown to the network. Check the address of the  
destination endpoint and the routing pattern used by this Administered  
Connection, and verify that they are correct and available.  
o. These errors indicate that an ISDN protocol error has occurred.  
p. The destination endpoint (or some intermediate facility) is not compatible  
with the originating endpoint. Check the BCC fields of the routing pattern  
used by this Administered Connection. Also, check if the originating and  
destination endpoints are compatible (for example, the originating access  
endpoint is voice-grade data, and the destination access endpoint is 64k  
data).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX8D-BD (AUDIX Circuit Pack)  
3-9  
ADX8D-BD (AUDIX Circuit Pack)  
MO Name (in  
Alarm Log)  
1
Alarm Level  
Initial Command To Run  
Full Name of MO  
ADX8D-BD  
MINOR or  
test board PCSS sh  
AUDIX Circuit Pack  
WARNINGS  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example,  
A, B,or C); SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02, ..., etc.).  
The ADX8D-BD maintenance object represents a TN566/TN2169 DEFINITY  
AUDIX circuit pack (sometimes called Embedded AUDIX) operating in  
digital-port (DP) mode. For circuit pack problems, see “XXX-BD (Common Port  
Circuit Pack)”. Port level problems are covered by ADX8D-PT.  
DEFINITY AUDIX consists of 2 circuit packs that occupy 4 slots in a port cabinet.  
The tests described in this manual apply only to switch-side maintenance which  
tests circuit pack components related to the TDM bus interface. The AUDIX  
system has an extensive maintenance strategy that is described in DEFINITY  
AUDIX System Maintenance, 585-300-110.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX8D-PT (AUDIX Digital Port)  
3-10  
ADX8D-PT (AUDIX Digital Port)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command To Run  
test port PCSSpp l  
Full Name of MO  
AUDIX Digital Port  
AUDIX Digital Port  
ADX8D-PT  
ADX8D-PT  
MINOR  
WARNING  
test port PCSSpp sh  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); SS is the address of the slot in the carrier where the circuit pack  
is located (for example, 01, 02, ..., etc.); and pp is the 2-digit port number (for  
example, 01).  
The ADX8D-PT maintenance object represents a port on a TN566/TN2169  
DEFINITY AUDIX circuit pack (sometimes called Embedded AUDIX) operating in  
digital-port (DP) mode. The maintenance strategy for ports on the TN566  
operating in control-link mode is described in ADX16A-PT.  
The tests described in this section apply only to switch-side maintenance which  
tests circuit pack components related to the TDM bus interface. The AUDIX  
system has an extensive maintenance strategy that is described in DEFINITY  
AUDIX System Maintenance, 585-300-110.  
AUDIX resides on a combined pair of circuit packs: the TN566 Multifunction  
Board (MFB) and the TN2169 Alarm Board (ALB). Because of its size this  
combination occupies 4 slots, but only 1 slot is functional as far as the switch is  
concerned. The other 4 slots are seen by the switch as ‘‘AUDIX-reserved’’ slots  
(or ADXDP-RS/ADX8D-RS.)  
In DP mode the TN566 pack supports up to 8 voice ports, each with a primary  
information channel and a secondary information channel. Ports are  
administered in increments of 2. When a call to a station with an AUDIX login is  
not answered, AUDIX answers the call using 1 of the available voice ports.  
Unlike other AUDIX systems, DEFINITY AUDIX is not an adjunct.  
!
CAUTION:  
Never do any of the following without first shutting down AUDIX. Follow  
instructions in the ‘‘Power Down AUDIX System’’ section in Chapter 1,  
‘‘Maintenance for csi systems’’.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX8D-PT (AUDIX Digital Port)  
3-11  
Error Log Entries and Test to Clear Values  
Table 3-5. DEFINITY AUDIX Digital Port Error Log Entries  
Error  
Type  
Aux  
On/Off  
Board  
Data  
Associated Test  
Any  
40987 None  
Alarm Level  
Any  
Test to Clear Value  
1
0
0
Any  
test port PCSSpp sh r 1  
1 (a)  
1 (b)  
WARNING  
WARNING  
OFF  
OFF  
1 to  
20  
None  
15 (c)  
18 (d)  
Any  
0
None  
busyout port  
PCSSpp  
WARNING  
OFF  
release port PCSSpp  
test port PCSSpp sh  
23 (e)  
0
None  
None  
WARNING  
WARNING  
OFF  
ON  
130 (f)  
257 (g)  
513 (h)  
1537 (i)  
1793  
40971 None  
Any None  
40968 None  
Voice & Ctrl. Local  
WARNING  
OFF  
ON  
2
MIN/WRN  
test port PCSSpp l r 3  
test port PCSSpp l r 3  
Loop Test (#13)  
2
2049  
NPECrosstalk Test  
(#9)  
MIN/WRN  
ON  
2305 (j)  
3840 (k)  
3840 (l)  
40967 None  
40965 None  
41029 None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the  
set options command.  
Notes:  
a. The user may experience a noisy port or link. This is an off-board problem  
that is detected by the port circuit. If this problem exists, replace the  
circuit pack (see caution at the beginning of this section). Once the  
problem is resolved, the alarm is retired after a predetermined time.  
b. At least 15 off-board problems have been detected with the link to the  
voice port. When an error with the link is detected, an on-board counter is  
incremented. Also see Note (a).  
c. This is an internal type error that occurs when an audit request fails.  
d. The port is busied-out by command. You can release the port via the  
release port PCSSpp command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX8D-PT (AUDIX Digital Port)  
3-12  
e. The circuit pack is administered but not physically installed. The alarm will  
clear when a circuit pack is inserted.  
f. The circuit pack has been removed or has been insane for more than 21  
minutes. To clear the error, reinsert or replace the AUDIX circuit pack (see  
caution at the beginning of this section).  
g. Something is interfering with transmitting to the voice port. This is usually  
an on-board problem and can be ignored if no user complaints are  
received.  
h. AUDIX is not available to the switch, possibly due to a busyout on the  
AUDIX system. Check out the AUDIX system referring DEFINITY AUDIX  
System Maintenance, 585-300-110, if necessary.  
i. An in-line maintenance error has generated an off-board warning due to  
some problem with the link to the voice port. This can be ignored if no user  
complaints are received. If the problem persists, replace the circuit pack  
(see caution at the beginning of this section). Once the problem is  
resolved, the alarm is retired after a certain period of time.  
j. The link between the circuit pack and the voice port is successfully reset.  
No craft action is necessary.  
k. No voice ports are connected to the DEFINITY AUDIX circuit pack. No  
maintenance action is required.  
l. The message buffer in the circuit pack is full.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when you are  
inspecting errors in the system. By clearing error codes associated with the  
Voice and Control Channel Local Loop Around Test for example, you may also  
clear errors generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Voice and Control Channel Local Loop Around Test (#13)  
NPE Crosstalk Test (#9)  
D/ND  
ND  
X
X
ND  
1. D = Destructive; ND = Nondestructive  
NO-OP Tests  
The maintenance strategy for DEFINITY AUDIX emulates the one for DIG-LINE.  
The tests listed below apply only to DIG-LINE and not to DEFINITY AUDIX. These  
are referred to as NO-OP tests, and they always return PASS.  
■
ElectroDnoicwnPlooawd ferormFWeewdw.SToemsatn(u#a1ls1.c)om. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX8D-PT (AUDIX Digital Port)  
3-13  
■
■
Station Lamp Updates Test (#16)  
Station (Digital) Audits Test (#17)  
NPE Crosstalk Test (#9)  
This test verifies that this port’s NPE channel talks on the selected time slot and  
that it never crosses over to time slots reserved for other connections. If the NPE  
is not working correctly, one-way and noisy connections may be observed. This  
test is part of a port’s Long Test Sequence, and it takes about 20 to 30 seconds to  
complete.  
Crosstalk testing is performed on both the primary information channel (voice)  
and on the secondary information channel (data) associated with each DEFINITY  
AUDIX port. If this test fails on either channel, the voice port is taken  
out-of-service.  
Table 3-6. TEST #9 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1
ABORT  
During testing of the primary information channel, system resources may not  
have been available. Also, the port may have been busy during the test.  
1. Check the port status. Use the display port PCSSpp command to  
determine the voice port extension of the port. Use the status station  
command to determine the service state of the port. If the service state  
indicates that the port is in use, you must wait until the port is idle.  
2. When the port is idle, retry the command at 1-minute intervals a  
maximum of 5 times.  
2
ABORT  
ABORT  
System resources may not have been available, or the port may have been  
busy during the test.  
1. Retry the command at 1-minute intervals a maximum of 5 times  
1000  
System resources required to run this test are not available. The port may be  
in use.  
1. Use the display port PCSSpp command to determine the voice port  
extension of the port. Use the status station command to determine the  
service state of the port. If the service state indicates that the port is in  
use, you must wait until the port is idle before retesting.  
2. When the port is idle, retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
ABORT  
System resources required to run this test are not available  
1. Retry the command at 1-minute intervals a maximum of 5 times..  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX8D-PT (AUDIX Digital Port)  
3-14  
Table 3-6. TEST #9 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1002  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions, or it may have time slots out-of-service due to  
TDM-BUS errors. Refer to “TDM-BUS” to diagnose any active TDM-BUS  
errors.  
1. If system has no TDM-BUS errors, and if it is not handling heavy traffic,  
retry the command at 1-minute intervals a maximum of 5 times.  
1003  
1004  
ABORT  
The system could not allocate a tone receiver for the test. The system may be  
oversized for the number of Tone Detectors present, or some Tone Detectors  
may be out-of-service.  
1. Resolve any “TTR-LEV” errors.  
2. Resolve any “TONE-PT” errors. Retry the command at 1-minute intervals  
a maximum of 5 times.  
ABORT  
The port was put in use during the test. The test has been aborted. Use the  
display port PCSSpp command to determine the voice port extension of the  
port. Use the status station command to determine the service state of the  
port. If the port is in use, wait until the port is idle before testing.  
1020  
2000  
ABORT  
ABORT  
Test disabled by background testing. Use the status station command to  
determine when the voice port is available for testing.  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1
2
FAIL  
The NPE of the tested port is transmitting in error. This causes noisy and  
unreliable connections. Failure code 1 indicates that the Crosstalk test failed  
on the primary channel. Failure code 2 indicates that the Crosstalk test failed  
on the secondary channel.  
1. Replace the circuit pack.  
PASS  
The port is using its allocated time slots correctly.  
1. To be sure that this is not an intermittent problem, repeat this test up to a  
maximum of 10 times to make sure it continues to pass.  
2. If complaints still exist, examine the connections.  
Voice and Control Channel Local Loop Test (#13)  
This test checks the information and control channels between the Switch  
Processing Element (SPE) and the DEFINITY AUDIX port circuit. First, the  
primary information (voice) channel loop back test is run.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX8D-PT (AUDIX Digital Port)  
3-15  
While the primary information channel is still looped around, the Control Channel  
Loop Around Test is performed. The Loop Around Test for the secondary  
information (data) channel is then performed. This test is the same as the primary  
information channel loop around test.  
Next, a Conference Test is implemented for the primary information channel. This  
test is the same as Conference Test #6.  
Only one value (Pass, Fail, or Abort) is generated as a result of the four tests run.  
If any test fails or aborts, the sequence is stopped.  
Table 3-7. TEST #13 Voice and Control Channel Local Loop Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may be in  
use. Use the display port PCSSpp command to determine the voice port  
extension of the port. Use the status station command to determine the  
service state of the port. If the service state indicates that the port is in use, you  
must wait until the port is idle before retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
System resources required for this test are not available.  
1001  
1002  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be under  
heavy traffic conditions, or may have time slots that are out-of-service due to  
TDM-BUS errors.  
1. If the system has no TDM-BUS errors, and is not handling heavy traffic,  
retry the command at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may be  
oversized for the number of Tone Detectors present, or some Tone Detectors  
may be out-of-service.  
1. Resolve any “TTR-LEV” errors.  
2. Resolve any “TONE-PT” errors.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was put in use during the test. Use the display port PCSSpp to  
determine the voice port extension of the port. Use the status station  
command to determine the service state of the port. If the service state  
indicates that the port is in use, you must wait until the port is idle before  
retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX8D-PT (AUDIX Digital Port)  
3-16  
Table 3-7. TEST #13 Voice and Control Channel Local Loop Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
2000  
2100  
ABORT  
ABORT  
Response to the test was not received within the allowable time period.  
Could not allocate the necessary system resources for this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
7
FAIL  
Conference Test failed on the primary channel. Some users may not notice a  
disruption in service. In extreme cases, the conferencing feature may not work  
at all.  
14  
15  
FAIL  
FAIL  
The primary voice channel is not transmitting properly. User impact may range  
from no noticeable effect to loss of use of this port.  
The control channel between the processor and DEFINITY AUDIX circuit pack  
is not transmitting properly. User impact may range from no noticeable effect to  
loss of use of this port. This failure could also be disruptive to other users.  
16  
FAIL  
FAIL  
The secondary voice channel is not transmitting properly. User impact may  
range from no noticeable effect to loss of use of this port.  
None  
The test failed for reasons external to the DEFINITY AUDIX circuit pack.  
1. Run circuit pack tests to check the Tone Generator circuit pack and the  
Tone Detector circuit pack by using the test board PCSS s command.  
2. Resolve any problems that are detected on the Tone Generator circuit pack  
or Tone Detector circuit pack.  
3. If the Tone Generator and Tone Detector circuit packs are functioning  
properly, and if the test still fails, replace the AUDIX circuit pack (see  
precaution at the beginning of this section).  
PASS  
Voice and Control Channel Local Loop test passed. All channels are  
transmitting properly.  
1. To be sure that this is not an intermittent problem, repeat this test up to 10  
times and see if it continues to pass.  
2. If complaints still exist, examine the connections.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16D-B (16 Port AUDIX Circuit Pack)  
3-17  
ADX16D-B (16 Port AUDIX Circuit  
Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command To Run  
test board PCSS sh  
Full Name of MO  
AUDIX Circuit Pack  
AUDIX Circuit Pack  
ADX16D-B  
ADX16D-B  
MINOR  
WARNING  
test board PCSS sh  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); SS is the address of the slot in the carrier where the circuit pack is  
located (for example, 01, 02, ..., etc.).  
The ADX16D-BD maintenance object represents a TN566/TN2169 DEFINITY  
AUDIX circuit pack combination operating in 16 port mode digital (DP). For  
circuit-pack-level problems, see “XXX-BD (Common Port Circuit Pack)”.  
Port-level maintenance is covered by ADX16D-PT.  
DEFINITY AUDIX consists of 2 circuit packs that occupy 4 slots on a port carrier.  
The tests described in this manual apply only to switch-side maintenance which  
tests circuit pack components related to the TDM bus interface. The AUDIX  
system has an extensive maintenance strategy of its own that is described in  
DEFINITY AUDIX System Maintenance, 585-300-110.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16A-BD (AUDIX Circuit Pack)  
3-18  
ADX16A-BD (AUDIX Circuit Pack)  
MO Name (in  
Alarm Log)  
Initial Command To  
1
Alarm Level  
Run  
Full Name of MO  
ADXCL-BD or  
\ADX16A-BD  
MINOR, or  
WARNINGS  
test board PCSS sh  
AUDIX Circuit Pack  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); SS is the address of the slot in the carrier where the circuit pack is  
located (for example, 01, 02, ..., etc.).  
The ADX16A-BD maintenance object represents a TN566/TN2169 DEFINITY  
AUDIX circuit pack combination operating in control-link (CL) mode. For  
circuit-pack-level problems, see “XXX-BD (Common Port Circuit Pack)”.  
Port-level maintenance is covered by ADX16A-PT.  
DEFINITY AUDIX consists of 2 circuit packs that occupy 4 slots on a port carrier.  
The tests described in this manual apply only to switch-side maintenance which  
tests circuit pack components related to the TDM bus interface. The AUDIX  
system has an extensive maintenance strategy that is described in DEFINITY  
AUDIX System Maintenance, 585-300-110.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16D-P (16-Port AUDIX Digital Port)  
3-19  
ADX16D-P (16-Port AUDIX Digital  
Port)  
MO Name (in  
Alarm Log)  
1
Alarm Level  
Initial Command To Run  
Full Name of MO  
AUDIX Digital Port  
ADX16D-P  
MINOR or WARNINGS test port PCSSpp l  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B,  
or C); SS is the address of the slot in the carrier where the circuit pack is located (for example,  
01, 02, ..., etc.); and pp is the 2-digit port number (for example, 01).  
!
CAUTION:  
Never do any of the following without first shutting down AUDIX. Follow  
instructions in the ‘‘Power Down AUDIX System’’ section in Chapter 1,  
‘‘Maintenance for csi systems’’.  
The ADX16D-P maintenance object represents a port on a TN566/TN2169  
DEFINITY AUDIX circuit pack operating in digital-port (DP) mode. The  
maintenance strategy for ports on the TN566 operating in control-link mode is  
described in ADX16A-PT.  
The tests described in this section apply only to switch-side maintenance which  
tests circuit pack components related to the TDM bus interface. The AUDIX  
system has an extensive maintenance strategy that is described in DEFINITY  
AUDIX System Maintenance, 585-300-110.  
AUDIX resides on a combined pair of circuit packs: the TN566 Multifunction  
Board (MFB) and the TN2169 Alarm Board (ALB). Because of its size this  
combination occupies 5 slots, but only 1 slot is functional as far as the system is  
concerned. The other 4 slots are seen by the switch as ‘‘AUDIX-reserved’’ slots  
(or ADX16-RES/ADX16D-RS).  
In 16 Port DP mode, the TN566 pack supports up to 16 voice ports, each with a  
primary information channel and a secondary information channel. Ports are  
administered in increments of two. When a call to a station with an AUDIX login is  
not answered, AUDIX answers the call using one of the available voice ports.  
Unlike other AUDIX systems, DEFINITY AUDIX is not an adjunct.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16D-P (16-Port AUDIX Digital Port)  
3-20  
Error Log Entries and Test to Clear Values  
Table 3-8. DEFINITY AUDIX Digital Port Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test port PCSSpp sh r 1  
1(a)  
40987  
1 to 20  
Any  
0
None  
None  
None  
WARNING  
WARNING  
OFF  
OFF  
1(b)  
15(c)  
18(d)  
23(e)  
130(f)  
257(g)  
513(h)  
1537(i)  
1793  
busyout port PCSSpp WARNING  
OFF  
OFF  
ON  
release port PCSSpp  
test port PCSSpp sh  
0
None  
None  
None  
None  
None  
WARNING  
WARNING  
40971  
Any  
40968  
WARNING  
OFF  
ON  
2
Voice and Control  
Local Loop TEST  
(#13)  
MIN/ WRN  
test port PCSSpp l r 3  
test port PCSSpp l r 3  
2
2049  
NPE Crosstalk Test  
(#9)  
MIN/ WRN  
ON  
2305(j)  
3840(k)  
3840(l)  
40967  
40965  
41029  
None  
None  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
2. Minor alarms may be downgraded to Warning alarms based on the values used in the set options  
command.  
Notes:  
a. The user may experience a noisy port or link. This is an off-board problem  
that is detected by the port circuit. If this problem exists, replace the  
circuit pack (see caution at the beginning of this section). Once the  
problem is resolved, the alarm is retired after a predetermined time.  
b. At least 15 off-board problems have been detected with the link to the  
voice port. When an error with the link is detected, an on-board counter is  
incremented. Also see Note a, above.  
c. This is an internal type error that occurs when an audit request fails.  
d. The port is busied-out by command. Release the port with the release  
port PCSSpp command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16D-P (16-Port AUDIX Digital Port)  
3-21  
e. The circuit pack is administered but not physically installed. The alarm will  
clear when a circuit pack is inserted.  
f. The circuit pack has been removed or has been insane for more than 21  
minutes. To clear the error, reseat or replace the AUDIX circuit pack (see  
caution at the beginning of this section).  
g. Something is interfering with transmitting to the voice port. This is usually  
an on-board problem and can be ignored if no user complaints are  
received.  
h. AUDIX is not available to the switch, possibly due to a busyout on the  
AUDIX system. Refer to DEFINITY AUDIX System Maintenance,  
585-300-110, if necessary.  
i. An in-line maintenance error has generated an off-board warning due to  
some problem with the link to the voice port. This can be ignored if no user  
complaints are received. If the problem persists, replace the circuit pack  
(see caution at the beginning of this section). Once the problem is  
resolved, the alarm is retired after a certain period of time.  
j. The link between the circuit pack and the voice port is successfully reset.  
No craft action is necessary.  
k. No voice ports are connected to the DEFINITY AUDIX circuit pack. No  
maintenance action is required.  
l. The message buffer in the circuit pack is full.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the Voice and Control Channel Local Loop Around  
Tes t for example, you may also clear errors generated from other tests in the  
testing sequence.  
ShortTest  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Voice and Control Channel Local Loop Around Test (#13)  
NPE Crosstalk Test (#9)  
D/ND  
ND  
X
X
ND  
1. D = Destructive; ND = Nondestructive  
NO-OP Tests  
The maintenance strategy for DEFINITY AUDIX emulates the one for DIG-LINE.  
The tests listed below apply only to DIG-LINE and not to DEFINITY AUDIX. These  
tests always return PASS.  
■
ElectroDnoicwnPlooawd ferormFWeewdw.SToemsatn(u#a1ls1.c)om. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16D-P (16-Port AUDIX Digital Port)  
3-22  
■
■
■
Station Lamp Updates Test (#16)  
Station (Digital) Audits Test (#17)  
Digital Terminal Remote Loop Around Test (1201)  
NPE Crosstalk Test (#9)  
This test verifies that this port’s NPE channel talks on the selected time slot and  
that it never crosses over to time slots reserved for other connections. If the NPE  
is not working correctly, one-way and noisy connections may be observed. This  
test is part of a port’s Long Test Sequence, and it takes about 20 to 30 seconds to  
complete.  
Crosstalk testing is performed on both the primary information channel (voice)  
and on the secondary information channel (data) associated with each DEFINITY  
AUDIX port. If this test fails on either channel, the voice port is taken  
out-of-service.  
Table 3-9. TEST #9 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1
ABORT  
During testing of the primary information channel, system resources may  
not have been available. Also, the port may have been busy during the  
test.  
1. Check the port status. Use the display port PCSSpp command to  
determine the voice port extension of the port. Use the status station  
command to determine the service state of the port. If the port is in  
use, it is unavailable for this test. Wait until the port is idle.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
2
ABORT  
ABORT  
System resources may not have been available, or the port may have been  
busy during the test.  
1. Check if port is being used, retry the command at 1-minute intervals a  
maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use. Use the display port PCSSpp command to determine the voice  
port extension of the port. Use the status station command to determine  
the service state of the port. If the port is in use, it is unavailable for certain  
tests. Refer to “Status” commands in Chapter 8, "Maintenance Commands  
and Trouble-Clearing Aids", for a full description of all possible states. Wait  
until the port is idle before testing.  
1. If the port status is idle, retry the command at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16D-P (16-Port AUDIX Digital Port)  
3-23  
Table 3-9. TEST #9 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1001  
ABORT  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
1003  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions, or it may have time slots out-of-service due  
to TDM-BUS errors.  
1. If system has no TDM-BUS errors, and if it is not handling heavy traffic,  
retry the command at 1-minute intervals a maximum of 5 times.  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present, or some tone  
detectors may be out-of-service.  
1. Resolve any “TTR-LEV” errors in the Error Log.  
2. Resolve any “TONE-PT” errors in the Error Log.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
1004  
ABORT  
The port was put in use during the test. The test has been aborted. Use the  
display port PCSSpp command to determine the voice port extension of  
the port. Use the status station command to determine the service state of  
the port. If the port is in use, it is unavailable for certain tests. Refer to  
“Status” commands in Chapter 8 for explanations of all possible states.  
Wait until the port is idle before testing.  
1020  
2000  
ABORT  
ABORT  
Test disabled via background testing. Use the status station command to  
determine when the voice port is available for testing.  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1
2
FAIL  
The NPE of the tested port was found to be transmitting in error. This  
causes noisy and unreliable connections. Failure code 1 indicates that the  
Crosstalk test failed on the primary channel. Failure code 2 indicates that  
the Crosstalk test failed on the secondary channel.  
1. Replace the circuit pack (see caution at the beginning of this section).  
The port is using its allocated time slots correctly.  
PASS  
1. To be sure that this is not an intermittent problem, repeat this test up to  
a maximum of 10 times to make sure it continues to pass.  
2. If complaints still exist, examine the connections.  
Note:  
a. Retry the command at 1-minute intervals a maximum of 5 times.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16D-P (16-Port AUDIX Digital Port)  
3-24  
Voice and Control Channel Local Loop Test (#13)  
This test checks the information and control channels between the Switch  
Processing Element (SPE) and the DEFINITY AUDIX port circuit. The SPE sends  
a message to loop around both the information and control channels for the port.  
First, the primary information (voice) channel loop back test is run.  
While the primary information channel is still looped around, the Control Channel  
Loop Around Test is performed. The Loop Around Test for the secondary  
information (data) channel is then performed. This test is the same as the primary  
information channel loop around test.  
Next, a Conference Test is implemented for the primary information channel. This  
test is the same as Conference Test #6.  
Only one value (Pass, Fail, or Abort) is generated as a result of the four tests run.  
If any test fails or aborts, the sequence is stopped.  
Table 3-10. TEST #13 Voice and Control Channel Local Loop Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use. Use the display port PCSSpp command to determine the voice  
port extension of the port. Use the status station command to determine  
the service state of the port. If the port is in use, it is unavailable for certain  
tests. Refer to “Status” commands in Chapter 8, "Maintenance Commands  
and Trouble-Clearing Aids" for explanations of all possible states.  
1. Wait until the port is idle before retesting, then retry the command at  
1-minute intervals a maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions, or it may have time slots that are  
out-of-service due to TDM-BUS errors. Refer to “TDM-BUS” to diagnose  
TDM-BUS errors.  
1. If the system has no TDM-BUS errors and if it is not handling heavy  
traffic, retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16D-P (16-Port AUDIX Digital Port)  
3-25  
Table 3-10. TEST #13 Voice and Control Channel Local Loop Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present, or some tone  
detectors may be out-of-service.  
1. Resolve any “TTR-LEV” errors.  
2. Resolve any “TONE-PT” errors.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
1004  
ABORT  
The port was put in use during the test. The test has been aborted. Use the  
display port PCSSpp to determine the voice port extension of the port.  
Use the status station command to determine the service state of the  
port. If the port is in use, it is unavailable for certain tests. Wait until the port  
is idle before retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources for this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16D-P (16-Port AUDIX Digital Port)  
3-26  
Table 3-10. TEST #13 Voice and Control Channel Local Loop Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
7
FAIL  
Conference Test failed on the primary channel. In some cases, users may  
not notice a disruption in service. In extreme cases, the conferencing  
feature may not work at all.  
14  
15  
FAIL  
FAIL  
The primary voice channel is not transmitting properly. User impact may  
range from no noticeable effect to loss of use of this port.  
The control channel between the processor and AUDIX is not transmitting  
properly. User impact may range from no noticeable effect to loss of use of  
this port. This failure could also be disruptive to other users.  
16  
FAIL  
FAIL  
The secondary voice channel is not transmitting properly. User impact  
may range from no noticeable effect to loss of use of this port.  
None  
The test failed for reasons external to the AUDIX.  
1. Run circuit pack tests to check the tone generator circuit pack and the  
tone detector circuit pack by using the test board PCSS s command.  
2. Resolve any problems detected on the tone generator circuit pack or  
tone detector circuit pack.  
3. If the tone generator and tone detector circuit packs are functioning  
properly, and if the test still fails, replace the AUDIX (see caution at the  
beginning of this section).  
PASS  
Voice and Control Channel Local Loop test passed. All channels are  
transmitting properly.  
1. To be sure that this is not an intermittent problem, repeat this test up to  
10 times and see if it continues to pass.  
2. If complaints still exist, examine the connections.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16A-PT (AUDIX Analog Line/Control Link)  
3-27  
ADX16A-PT (AUDIX Analog  
Line/Control Link)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command To  
1
Run  
Full Name of MO  
ADXCL-PT or  
ADX16A-PT  
MINOR  
test port PCSSpp l  
AUDIX Analog Line/ Control Link  
ADXCL-PT or  
ADX16A-PT  
WARNING  
test port PCSSpp sh  
AUDIX Analog Line/ Control Link  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B,  
or C); SS is the address of the slot in the carrier where the circuit pack is located (for example, 01,  
02, ..., etc.); and pp is the 2-digit port number (for example, 01).  
!
CAUTION:  
Never do any of the following without first shutting down AUDIX. Follow  
instructions in the ‘‘Power Down AUDIX System’’ section in Chapter 1,  
‘‘Maintenance for csi systems’’.  
The ADX16A-PT maintenance object represents a port on a TN566/TN2169  
DEFINITY AUDIX circuit pack that is operating in control-link (CL) mode. For  
circuit-pack-level problems (ADX16A-BD or ANL-16-BD), see “XXX-BD (Common  
Port Circuit Pack)”. For port-level problems with AUDIX operating in digital-port  
mode, see ADXDP-PT/ADX8D-PT.  
The tests described in this section apply only to switch-side maintenance which  
tests circuit pack components related to the TDM bus interface. The AUDIX  
system has an extensive maintenance strategy that is described in DEFINITY  
AUDIX System Maintenance, 585-300-110.  
AUDIX resides on a combined pair of circuit packs: the TN566 Multifunction  
Board (MFB) and the TN2169 Alarm Board (ALB). Because of its size this  
combination occupies 5 slots, but only 1 slot is functional as far as the switch is  
concerned. The other 4 slots are seen by the switch as ‘‘AUDIX-reserved’’ slots.  
In CL mode the TN566 pack supports up to 16 voice ports. When a call to a  
station with an AUDIX login is not answered, AUDIX answers the call using one of  
the available voice ports.  
Unlike other AUDIX systems, DEFINITY AUDIX is not an adjunct.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16A-PT (AUDIX Analog Line/Control Link)  
3-28  
Error Log Entries and Test to Clear Values  
Table 3-11. DEFINITY AUDIX Analog Line/Control Link Error Log Entries  
Error  
Type  
1
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
0
0
Any  
Any  
Any  
test port PCSSpp sh r 1  
1 (a)  
18  
40977  
0
None  
busyout station  
<extension>  
WRN  
ON  
release station extension  
23 (b)  
0
None  
None  
None  
None  
WRN  
WRN  
OFF  
ON  
130 (c)  
257 (d)  
513 (e)  
1025 (f)  
test port PCSSpp sh  
40973  
Any  
Loop Around Test  
(#161)  
MIN/  
WRN  
ON  
ON  
ON  
test port PCSSpp l r 2  
test port PCSSpp l r 2  
test port PCSSpp l r 2  
2
2
2
1281  
1537  
Conference Test (#7)  
MIN/  
WRN  
NPE Crosstalk Test (#6)  
MIN/  
WRN  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the  
set options command.  
Notes:  
a. This is an in-line error and can only be resolved over time. This indicates  
that no terminal equipment was present when ringing was attempted.  
Execute the short test port PCSSpp command.  
b. The circuit pack has been logically administered but not physically  
installed. The alarm will be cleared when the circuit pack is installed.  
c. The circuit pack has been removed or has been insane for more than 11  
minutes. To clear the error, reseat or replace the circuit pack.  
d. This is an in-line error and can only be resolved over time. This error  
indicates that ringing voltage is absent. If only 1 analog circuit pack in the  
system has this problem, replace the circuit pack. If all analog circuit  
packs have this error, check the ringing generator.  
e. AUDIX is not available to the switch. Check the AUDIX system, referring to  
DEFINITY AUDIX System Maintenance, 585-300-110.  
f. The TDM bus is out of service. See the “TDM-BUS” section.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16A-PT (AUDIX Analog Line/Control Link)  
3-29  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the Loop Around Test #161 for example, you may  
also clear errors generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Loop Around Test (#161)  
Conference Test (#7)  
D/ND  
ND  
X
X
X
ND  
NPE Crosstalk Test (#6)  
ND  
1. D = Destructive; ND = Nondestructive  
NO-OP Tests  
The maintenance strategy for DEFINITY AUDIX emulates the one for ANL-16-L.  
The tests listed below apply only to ANL-16-L and not to DEFINITY AUDIX. These  
tests always return PASS.  
■
■
■
Battery Feed Test (#35)  
Audits and Updates Test (#36)  
Station Present Test (#48)  
Tests 36 and 48 ABORT when AUDIX is not running.  
NPE Crosstalk Test (#6)  
This test verifies that this port’s NPE channel talks on the selected time slot and  
never crosses over to time slots reserved for other connections. If the NPE is not  
working correctly, one-way and noisy connections may be observed. This test is  
part of the long test sequence and takes about 25 seconds to complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16A-PT (AUDIX Analog Line/Control Link)  
3-30  
Table 3-12. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources for this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension. Use the status station command to  
determine the service state of the port. If the port is in use, it is unavailable  
for certain tests. Wait until the port is idle before testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS Maintenance documentation to  
diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
then retry the command at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present or some tone  
detectors may be out-of-service.  
1. Resolve any “TTR-LEV” errors.  
2. Resolve any “TONE-PT” errors. Then, retry the command at 1-minute  
intervals a maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension. Use the status station command to determine the service state  
of the port. If the port is in use, it is unavailable for certain tests. Wait until  
the port is idle before testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1005  
1018  
ABORT  
ABORT  
This condition indicates that the test is not applicable when the analog port  
is used in a combined modem pool. This error can be ignored.  
Test disabled via administration.  
1. To enable the test for the particular analog station being tested, enter  
the change station <extension> command and change the ‘‘Test?’’  
field on the Station Form from ‘‘n’’ to ‘‘y.’’  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16A-PT (AUDIX Analog Line/Control Link)  
3-31  
Table 3-12. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
2012  
2100  
ABORT  
ABORT  
System could not respond to this request.  
Could not allocate the necessary system resources for this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Any  
FAIL  
The NPE of the tested port was found to be transmitting in error. This  
causes noisy and unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated by using other port tests, by examining  
station wiring, or by examining the station.  
Conference Circuit Test (#7)  
This test verifies that the NPE channel for the port being tested can correctly  
perform the conferencing function.  
Table 3-13. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test. (a)  
1000  
System resources required to run test are not available. The port may be busy  
with a valid call. Use the display port PCSSpp command to determine the  
station extension. Use the status station command to determine the service  
state of the port. If the port is in use, wait until it is idle before retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been aborted.  
Use the display port PCSSpp command to determine the station extension.  
Use the status station command to determine the service state of the port. If  
the port is in use, wait until it is idle before testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16A-PT (AUDIX Analog Line/Control Link)  
3-32  
Table 3-13. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1018  
ABORT  
Test disabled by administration. This only applies to analog stations.  
1. To enable the test for the analog station being tested, enter the change  
station <extension> command and change the ‘‘Test?’’ field on the  
Station Form from ‘‘n’’ to ‘‘y.’’  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time period.  
Could not allocate the necessary system resources for this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Any  
FAIL  
The NPE of the tested port did not conference the tones correctly. This causes  
noisy and unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port can correctly conference multiple connections. User-reported  
troubles on this port should be investigated by using other port tests and by  
examining station, trunk, or external wiring.  
Loop Around Test (#161)  
This test is designed to check the on-board transmission capabilities of the NPE  
on the analog port.  
Table 3-14. TEST #161 Loop Around Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources for this test. Try (a).  
1000  
1002  
System resources required to run this test are not available. The port may be  
busy with a valid call. Use the display port PCSSpp command to determine  
the station extension. Use the status station command to determine the  
service state of the port. If the port is in use, wait until it is idle before testing.  
1. If the port status is idle, retry the command at 1-minute intervals a  
maximum of 5 times.  
ABORT  
The system could not allocate time slots for the test. The system may be under  
heavy traffic conditions or it may have time slots out-of-service due to  
TDM-BUS errors. Refer to “TDM-BUS” to diagnose TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic, try (a).  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ADX16A-PT (AUDIX Analog Line/Control Link)  
3-33  
Table 3-14. TEST #161 Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may be  
oversized for the number of tone detectors present or some tone detectors may  
be out-of-service.  
1. Resolve any “TTR-LEV” errors.  
2. Resolve any “TONE-PT” errors.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
1018  
ABORT  
ABORT  
The port was seized by a valid call during the test. The test has been aborted.  
Use the display port PCSSpp command to determine the station extension.  
Use the status station command to determine the service state of the port. If  
the port is in use, wait until the port is idle before testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Test disabled by administration. To enable the test for the particular analog  
station being tested, enter the change station <extension> command and  
change the ‘‘Test?’’ field on the Station Form from ‘‘n’’ to ‘‘y.’’  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time period.  
Could not allocate the necessary system resources for this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
The reflective Loop Around Test failed. This causes noisy or unreliable  
connections or other users calling this port may hear an echo.  
1. Replace the circuit pack.  
PASS  
The port is able to provide an analog transmission path to the station  
equipment. User-reported troubles on this port should be investigated by using  
other port tests, by examining station wiring, or by examining the station.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ALARM-PT (ALARM PORT)  
3-34  
ALARM-PT (ALARM PORT)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
Alarm-Port  
ALARM-PT  
ALARM-PT  
MIN  
WRN  
test port PCSSpp l  
test port PCSSpp sh  
Alarm-Port  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); SS is the address of the slot in the carrier where the circuit  
pack is located (for example, 01, 02, ..., etc.); and pp is the 2-digit port number  
(for example, 01).  
The Alarm Port maintenance object provides on-board maintenance for an  
analog line port that is administered as an external device alarm port. Tests are  
provided to verify the analog line port’s ability to detect an external device alarm.  
The External Device Alarm (EXT-DEV) maintenance object is used for the  
off-board external device alarm.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-35  
ANL-24-L (24-Port Analog Line)  
MO Name (in  
Alarm Log)  
Initial Command to  
Alarm Level  
Full Name of MO  
1
Run  
ANL-24-L  
ANL-24-L  
MIN  
WRN  
test port PCSSpp l  
test port PCSSpp sh  
24-Port Analog Line  
24-Port Analog Line  
1. Where Pis the port network number (1 for PPN); C is the carrier designation (for example,  
A, B, or C); SS is the address of the slot in the carrier where the circuit pack is located  
(for example, 01, 02, ..., etc.); and pp is the 2-digit port number (for example, 01).  
The 24-Port Analog Line circuit pack (TN793) provides 24 ports for voice  
terminals and supports both on-premises and off-premises analog voice  
terminals.  
No maintenance of the terminal connected to the 24-Port Neon Analog Line  
circuit pack is performed, except to determine whether or not the terminal is  
connected. Failures of the neon message waiting lamp power and the common  
ringing application circuitry are reported as part of common port circuit pack  
errors. See errors 1281 and 1793 in the “XXX-BD (Common Port Circuit Pack)”  
section.  
NOTE:  
This analog line circuit pack supports analog data modules. When  
assigned, analog data modules provide access to the Net Pkt (TN794) data  
ports. To activate an analog data module you must assign the port location  
on the data form and connect a modem to the port. (The analog data  
module may be used for connection to a CDR output or other adjuncts as  
needed.) These ports are tested the same as all other analog ports on the  
circuit pack.  
Ringing Caused by Maintenance Testing  
Test #48 may cause some terminal equipment to ring briefly during daily  
maintenance. If this ringing is disturbing the customer or the terminal equipment,  
it should be disabled in the Testsfield of the change station extension form. Be  
aware that this action also disables Tests #6, 7, 161, and 35.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-36  
Error Log Entries and Test to Clear Values  
Table 3-15. 24-Port Analog Line Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test port PCSSpp sh r 1  
1(a)  
40960  
40975  
40977  
none  
15(b)  
18  
Any  
Audits and  
Updates Test (#36)  
0
busy-out station  
extension  
WRN  
WRN  
ON  
ON  
release station <extension>  
test port PCSSpp sh  
130(c)  
257(d)  
513(e)  
None  
none  
40973  
Station Present  
Test (#48)  
WRN  
OFF  
ON  
ON  
ON  
ON  
test port PCSSpp sh r 2  
test port PCSSpp sh r 2  
test port PCSSpp l r 2  
test port PCSSpp l r 2  
test port PCSSpp l r 2  
769  
Battery Feed Test  
(#35)  
MIN/  
WRN  
2
2
2
2
1025  
1281  
1537  
Looparound Test  
(#161)  
MIN/  
WRN  
Conference Test  
(#7)  
MIN/  
WRN  
NPE Crosstalk Test  
(#6)  
MIN/  
WRN  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the set  
options command.  
Notes:  
a. These are in-line errors and can only be resolved over time.  
■
40960 indicates that too many simultaneous incoming ringing  
attempts were made on this board. Only 4 ports on a board may  
ring simultaneously. A 5th incoming call will cause an inline error  
from the board.  
■
40975 indicates that the terminal equipment was on-hook when  
ring-tip was detected during ringing. This usually indicates a failure  
in the terminal equipment or the type of terminal has a low ringer  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-37  
impedance. Call the terminal equipment and verify that the terminal  
rings. If the terminal does not ring, then replace it. Otherwise, issue  
the test port PCSSpp command, and follow the procedure for  
Test #48.  
■
40977 indicates that no terminal equipment was connected when  
ringing was attempted. Run the short test via the test port PCSSpp  
command, and follow the procedure for the results of Test #48.  
b. This is a software audit error that does not indicate any hardware  
malfunction. Run Short Test Sequence and investigate associated errors.  
c. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11-minutes. To clear the error, reseat or replace  
the circuit pack.  
d. This is an in-line error and can only be resolved over time. This error  
indicates that ringing voltage is absent. If only 1 analog circuit pack in the  
system has this problem, then replace the circuit pack. If only analog  
circuit packs on a particular carrier have this error, then the ringing  
generator may not be connected to this carrier. If analog circuit packs on  
many carriers have this error, then it is probably a problem with the ringing  
generator.  
e. Test #48 may cause some terminal equipment to ring briefly during daily  
maintenance. If this disturbs the customer or the terminal equipment,  
disable it by setting the Testsfield on the change station extension form  
to n. On some software releases, this will also disable Tests #6, 7, 161,  
and 35.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Battery Feed Test, for example, you may also clear errors generated from other  
tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-38  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Battery Feed Test (#35)  
Station Present Test (#48)  
Looparound Test (#161)  
Conference Test (#7)  
X
X
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
ND  
NPE Crosstalk Test (#6)  
Station Status and Translation Audits and Updates  
Test (#36)  
X
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
This test verifies that this port’s NPE channel talks on the selected time slot and  
never crosses over to time slots reserved for other connections. If the NPE is not  
working correctly, one-way and noisy connections may be observed. This test is  
usually part of the long test sequence and takes about 20 to 30 seconds to  
complete.  
Table 3-16. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run test are not available. The port may be  
busy with a valid call. This result is also reported for the system’s  
Music-On-Hold port when it is off-hook, which it usually is.  
1. Enter display port PCSSpp to determine the station’s extension.  
2. Enter status station extension to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle. Retry the command at  
1-minute intervals a maximum of 5 times.  
1001  
ABORT  
System resources required to run test are not available. This could be due  
to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-39  
Table 3-16. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1002  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or have time slots out-of-service due to  
TDM-BUS errors. Refer to “TDM-BUS” to diagnose any active TDM-BUS  
errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
retry the command at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present or some tone  
detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to “TTR-LEV”.  
2. Look for TONE-PT errors in the Error Log. If present, refer to  
“TONE-PT”.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension. Use the status station command to determine the service state  
of the port. If the port is in use, wait until the port is idle before testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1005  
1018  
ABORT  
ABORT  
The test was aborted due to a configuration problem. This test may not be  
applicable, or it may be disruptive to terminal equipment other than a voice  
terminal (for example, the modem pool member or Music On Hold).  
The test has been disabled by administration. The default for the Testfield  
on the station form is y. Determine why this field has been set to non this  
station (this may be due to the ringing application test 48, that can be  
customer or terminal disturbing).  
1. To enable the test for a particular station being tested, enter change  
station extension and set the Test?field on the station from nto y.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run test are not available. This could be due  
to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-40  
Table 3-16. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
Any  
FAIL  
This test can fail due to on-board or off-board problems. Off-board  
problems include EXP-PN and EXP-INTF faults, TDM-BUS faults, and faults  
associated with the tone detectors/tone generators. Clear all off-board  
problems before replacing the board. A TDM-BUS problem is usually the  
result of a faulty board connected to the backplane, or bent pins on the  
backplane.  
1. Look for EXP-PN and/or EXP-INTF errors in the error log. If present,  
refer to “EXP-PN” and “EXP-INTF”.  
2. Look for TDM-BUS errors in the error log. If present, refer to  
“TDM-BUS”.  
3. Look for TONE-BD and/or TONE-PT errors in the error log. If present,  
refer to “TONE-BD” and “TONE-PT”.  
4. Test the board when the faults from Steps 1, 2, and 3 are cleared.  
Replace the board only if the test fails.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated by using other port tests, by examining  
station wiring, or by examining the station.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
Conference Circuit Test (#7)  
This test verifies that the NPE channel for the port being tested can correctly  
perform the conferencing function.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-41  
Table 3-17. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may be  
busy with a valid call. This result is also reported for the system’s  
Music-On-Hold port when it is off-hook, which it usually is.  
1. Enter display port PCSSpp to determine the station’s extension.  
2. Enter status station extension to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle and retry the command at  
1-minute intervals a maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted.  
1. Use the display port PCSSpp command to determine the station  
extension.  
2. Use the status station command to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle and retry the command at  
1-minute intervals a maximum of 5 times.  
1005  
1018  
ABORT  
ABORT  
The test was aborted due to a configuration problem. This test may not be  
applicable, or it may be disruptive to terminal equipment other than a voice  
terminal (for example, the modem pool member or Music On Hold).  
The test has been disabled via administration. The default for the Testfield  
on the station form is y. Determine why this field has been set to non this  
station (this may be due to the ringing application test 48, that can be  
customer or terminal disturbing).  
1. To enable the test for a particular station being tested, enter change  
station extension and set the Test?field on the station from nto y.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run this test are not available.  
1. Look for TONE-PT errors in the error log. If present, refer to “TONE-PT”.  
2. If there are no TONE-PT errors in the error log, retry the command at  
1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-42  
Table 3-17. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
Any  
FAIL  
The NPE of the tested port did not conference the tones correctly. This will  
cause noisy and unreliable connections.  
1. Issue the display port and the status station commands to determine  
if the station is idle. If the station is idle, issue the test port command for  
this port.  
2. If the test continues to fail, issue the busyout port and the release port  
commands, and then retest.  
3. If the test still fails, replace the board.  
PASS  
The port can correctly conference multiple connections. User-reported  
troubles on this port should be investigated by using other port tests and by  
examining station, trunk, or external wiring.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
Battery Feed Test (also called Port Diagnostic  
Test) (#35)  
The battery feed chip provides power to the telephone equipment, signaling,  
rotary dial pulsing, transmission, and balance. This test checks the signaling and  
switchhook capabilities of the battery feed chip by terminating the port, applying  
battery and detecting the resulting current.  
For the TN746B, Test #35 does not actually run and instead always returns PASS.  
Test #35 operates in the normal manner for TN746.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-43  
Table 3-18. TEST #35 Battery Feed Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may be  
busy with a valid call. This result is also reported for the system’s  
Music-On-Hold port when it is off-hook, which it usually is.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted.  
1. Use the display port PCSSpp command to determine the station  
extension.  
2. Use the status station command to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle and retry the command at  
1-minute intervals a maximum of 5 times.  
1005  
1018  
ABORT  
ABORT  
The test was aborted due to a configuration problem. This test may not be  
applicable, or it may be disruptive to terminal equipment other than a voice  
terminal (for example, the modem pool member or Music On Hold).  
The test has been disabled via administration. The default for the Testfield  
on the station form is y. Determine why this field has been set to non this  
station (this may be due to the ringing application test 48, that can be  
customer or terminal disturbing).  
1. To enable the test for a particular station being tested, enter change  
station extension and set the Test?field on the station from nto y.  
1392  
ABORT  
This port is currently a TTI port and the test will not execute on it.  
1. Verify that the port is a TTI port using either the display port command  
(the display shows that the port is a TTI port) or the list config  
command (the display shows a tfor the port).  
2. If the port is not a TTI port, escalate the problem. If both commands  
indicate that the port is a TTI port, the abort is correct for the test, and  
no action is necessary.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-44  
Table 3-18. TEST #35 Battery Feed Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
FAIL  
The port’s battery feed chip is unable to supply sufficient power to the  
terminal equipment. This could be a marginal test, and the terminal  
equipment may be operating satisfactorily.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, determine whether the customer is  
experiencing problems on this line. If so, replace the circuit pack.  
PASS  
The port’s battery feed chip is able to provide power to the station  
equipment to detect on-/off-hook, but may not be able to supply power for  
touch-tones. If touch-tones are inoperative on this station, then replace the  
circuit pack because this port is inoperative. User-reported troubles on this  
port should be investigated by using other port tests, by examining station  
wiring, or by examining the station.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
Station Status and Translation Audits and  
Updates Test (#36)  
This test updates the analog port’s message lamp state (if it has one) and  
translations with information in the software.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-45  
Table 3-19. Test #36 Station Status and Translation Audits and Updates  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1004  
The port was seized by a valid call during the test. The test has been  
aborted.  
1. Use the display port PCSSpp command to determine the station  
extension.  
2. Use the status station command to determine the service state of the  
port.  
3. If the port is in use, wait until port is idle and retry the command at  
1-minute intervals a maximum of 5 times.  
1005  
1006  
ABORT  
ABORT  
The test was aborted due to a configuration problem. This test may not be  
applicable, or it may be disruptive to terminal equipment other than a voice  
terminal (for example, the modem pool member or Music On Hold).  
This port has been busied out by command, or taken out-of-service by the  
failure of the NPE Crosstalk Test.  
1. Look in the Error Log for error type 18 (port busied out) for this port. If  
this error is present, release the port with the release station  
extension command, and run the test again.  
2. Check the Error Log for error type 1025 (NPE crosstalk test failed) for  
this port. If this error is present, investigate the errors associated with  
the NPE Crosstalk Test #6.  
3. Make sure that the terminal is connected and in service, and then  
retest.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1
FAIL  
This does not indicate a hardware problem. The switchhook audit failed.  
The other updates were not performed because of this failure. This may  
occur when the audit is performed at the same time the terminal equipment  
goes off-hook.  
1. Use the status station command to determine when the port is  
available and retry the command at 1-minute intervals a maximum of 5  
times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-46  
Table 3-19. Test #36 Station Status and Translation Audits and Updates — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
5
FAIL  
This may be an internal software error. The message waiting lamp update  
failed. The translation and ringer updates were not performed because of  
this failure.  
7
8
FAIL  
FAIL  
The translation update failed. There may be an internal software error. The  
ringer update was not performed because of this failure.  
This does not indicate a hardware problem. There may be an internal  
software error. The ringer update failed.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
The software and the port processor have the same status. User-reported  
troubles on this port should be investigated by using other port tests, by  
examining station wiring, or by examining the station.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure the board translations are correct. Use the list config  
command and resolve problems.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
Station Present Test (also called Ringing  
Application Test) (#48)  
This test applies momentary ringing voltage to the terminal equipment and  
monitors resulting current flow to determine whether terminal equipment is  
connected to the port. This test may cause some terminal equipment to ring  
briefly during daily maintenance. If this ringing disturbs the customer or the  
terminal equipment, you can disable it via the Tests field on the change station  
form. However, on some software releases, Tests #6, 7, 161, and 35 are disabled.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-47  
Table 3-20. TEST #48 Station Present Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call.  
1004  
The port was seized by a valid call during the test. The test has been  
aborted.  
1. Use the display port PCSSpp command to determine the station  
extension.  
2. Use the status station command to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle and retry the command at  
1-minute intervals a maximum of 5 times.  
1005  
1008  
ABORT  
ABORT  
The test was aborted due to a configuration problem. This test may not be  
applicable or it may be disruptive to terminal equipment other than a voice  
terminal (for example, the modem pool member or Music On Hold).  
Could not allocate a ringing circuit. Either all the ringing circuits are in use  
or the ringing generator is defective or it is not wired correctly.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort, look for RING-GEN errors in the Error Log.  
If an ABORT 1008 occurs for this test on other circuit packs as well,  
then the ringing generator may be defective or is not wired correctly  
(see errors for RING-GEN). If it does not occur on other ports, then all  
four ring phases are in use.  
1018  
ABORT  
The test has been disabled by administration.The default for the Testfield  
on the station form is y. Determine why this field has been set to non this  
station (this may be due to the brief ringing disturbance that this test may  
cause).  
1. To enable the test for a particular station being tested, enter change  
station extension and set the Test?field on the station from nto y.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-48  
Table 3-20. TEST #48 Station Present Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
FAIL  
The terminal equipment is not connected to the circuit pack. Some terminal  
equipment, such as modems, may fail even when connected properly.  
1. Remotely test the equipment.  
2. If the test fails again, look for RING-GEN errors in the error log. If  
present, refer to “RING-GEN”.  
3. Check all of the wiring between the station equipment and the switch.  
Then, run the test again.  
4. If the test still fails, the set may be defective. Check the set, and replace  
it, if necessary.  
5. Some terminal equipment could fail even when it is connected properly.  
If this is the case, disable the test using the change station extension  
command (enter n into the Testfield). Note that this action also  
disables tests 6, 7, 161, and 35 on this port.  
PASS  
The station is connected properly to the switch. This test may also pass if no  
terminal equipment is connected and the terminal is located very far from  
the switch. User-reported troubles on this port should be investigated by  
using other port tests, by examining station wiring, or by examining the  
station.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
Looparound Test (#161)  
This test checks the on-board transmission capabilities of the NPE, the codec,  
and the battery feed chip of the analog port. The test passes if the signal  
measured by the tone detector is within acceptable limits.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-49  
Table 3-21. TEST #161 Looparound Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may be  
busy with a valid call.  
1. Use the display port PCSSpp command to determine the station  
extension.  
2. Use the status station command to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle and retry the command at  
1-minute intervals a maximum of 5 times.  
1002  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due to  
TDM-BUS errors. Refer to “TDM-BUS” to diagnose TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic, retry  
the command at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present or some tone  
detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to “TTR-LEV”.  
2. Look for TONE-PT errors in the Error Log. If present, refer to “TONE-PT”.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted.  
1. Use the display port PCSSpp command to determine the station  
extension.  
2. Use the status station command to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle and retry the command at  
1-minute intervals a maximum of 5 times.  
1005  
1018  
ABORT  
ABORT  
This test is not run on ports administered as External Alert, Announcement  
or combined modem pool ports. This error can be ignored.  
The test has been disabled by administration. The default for the Testfield  
on the station form is y. Determine why this field has been set to non this  
station (this may be due to the ringing application test 48, that can be  
customer or terminal disturbing).  
1. To enable the test for a particular station being tested, enter change  
station extension and set the Test?field on the station from nto y.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-24-L (24-Port Analog Line)  
3-50  
Table 3-21. TEST #161 Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
The reflective loop around test failed. This could cause noisy or unreliable  
connections, or users calling this port may hear an echo. The problem can  
also be off-board.  
1. Since the test may be affected by a line seizure, repeat the test at  
1-minute intervals for a maximum of 5 times.  
2. Run circuit pack tests to check the tone generator circuit pack and the  
tone detector circuit pack by using the test board PCSS short  
command.  
3. Resolve any problems on the tone generator circuit pack or the tone  
detector circuit pack.  
4. If the tone generator and tone detector circuit packs are functioning  
properly, a voice terminal is connected and wired properly and the test  
still fails, replace the analog line circuit pack.  
PASS  
The port is able to provide an analog transmission path to the station  
equipment. User-reported troubles on this port should be investigated by  
using other port tests, by examining station wiring, or by examining the  
station.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command and resolve any problems.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-BD (Analog Line Circuit Pack)  
3-51  
ANL-BD (Analog Line Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board PCSS sh  
test board PCSS sh  
test board PCSS sh  
test board PCSS sh  
test board PCSS sh  
test board PCSS sh  
Full Name of MO  
8-Port Analog Line Circuit Pack  
8-Port Analog Line Circuit Pack  
ANL-BD  
ANL-BD  
ANL-BD  
ANL-BD  
ANL-BD  
ANL-BD  
MIN  
WRN  
MIN  
8-Port Neon Analog Line Circuit Pack  
8-Port Neon Analog Line Circuit Pack  
16-Port Neon Analog Line Circuit Pack  
16-Port Neon Analog Line Circuit Pack  
WRN  
MIN  
WRN  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B,  
or C); and SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02, ..., etc.).  
Refer to "XXX-BD (Common Port Circuit Pack)" Maintenance documentation for  
circuit pack level errors. See also "ANL-LINE (8-Port Analog Line), ANL-NE-L  
(8-Port Neon Analog Line)", and "ANL-16-L (16-Port Neon Analog Line)"  
Maintenance documentation for related line information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-52  
ANL-LINE (8-Port Analog Line),  
ANL-NE-L (8-Port Neon Analog Line)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
8-Port Analog Line  
ANL-LINE  
ANL-LINE  
ANL-NE-L  
ANL-NE-L  
MIN  
test port PCSSpp l  
test port PCSSpp sh  
test port PCSSpp l  
test port PCSSpp sh  
WRN  
MIN  
8-Port Analog Line  
8-Port Neon Analog Line  
8-Port Neon Analog Line  
WRN  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); SS is the address of the slot in the carrier where the circuit pack  
is located (for example, 01, 02, ..., etc.); and pp is the 2-digit port number (for  
example, 01).  
The 8-Port Analog Line circuit packs are:  
■
■
■
TN742  
TN769  
TN467  
These circuit packs provide 8 ports for single line on-premises or off-premises  
analog endpoints such as analog voice terminals, queue warning level lamp,  
recorded announcements, dictation machines, PagePac™ paging equipment,  
external alerting devices, modems, facsimile machines, and AUDIX voice ports.  
The TN769 supports a neon message waiting lamp. The other 8-port analog lines  
do not support the lamp.  
Test #48 may cause some terminal equipment to ring briefly during daily  
maintenance. If this ringing is disturbing the customer or the terminal equipment,  
it should be disabled using the Tests field of the station administration screen.  
However, on some releases of the software, this action disables Tests #6, #47,  
and #35 as well as Test #48. Test #47 may cause a false alarm when the port is  
connected to off-premises equipment, some non-voice terminal equipment, and  
some loop equipment. If this is the case, then the test should be disabled using  
the Tests field of the change station <extension> command.  
No maintenance of the terminal connected to the 8-Port Analog Line circuit pack  
or 8-Port Neon Analog Line circuit pack is performed, except to determine  
whether or not the terminal is connected. Failures of the neon message waiting  
lamp power (for ANL-NE-L only) and the common ringing application circuitry are  
reported as part of the Common Port Circuit Pack errors (see errors 1281 and  
1793 in the XXX-BD (Common Port Circuit Pack) Maintenance documentation).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-53  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-22. 8-Port Analog Line Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test port PCSSpp sh r 1  
1 (a)  
40960  
40975  
40977  
None  
15 (b)  
18  
Any  
Audits and Updates  
Test (#36)  
0
busyout station  
<extension>  
WRN  
OFF  
release station <extension>  
130 (c)  
257 (d)  
None  
WRN  
WRN  
ON  
test port PCSSpp sh  
Station Present Test  
(#48)  
OFF  
test port PCSSpp sh r 3  
513  
Battery Feed Test  
(#35)  
MIN/  
WRN  
ON  
ON  
test port PCSSpp sh r 2  
test port PCSSpp l r 3  
test port PCSSpp l r 3  
2
769 (e)  
1025  
Loop Around and  
Conference Test(#47)  
NPE Crosstalk Test  
(#6)  
MIN/  
WRN  
2
1281 (f)  
1793 (f)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Major or Minor alarms on this MO may be downgraded to Warning alarms based on the values used  
in the set options command.  
Notes:  
a. These are in-line errors and can only be resolved over time.  
■
40960—indicates that too many simultaneous incoming ringing  
attempts were made on this board. Only four ports on a board may  
be ringing simultaneously. A fifth incoming call will cause an inline  
error from the board.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-54  
■
40975—indicates that the terminal equipment was on-hook when  
ring-tip was detected during ringing. This usually indicates a failure  
in the terminal equipment or the type of terminal has a low ringer  
impedance. Call the terminal equipment and verify that the terminal  
rings. If the terminal doesn’t ring, then replace it. Otherwise, issue  
the test port PCSSpp command, and follow the procedure for Test  
#48.  
■
40977—indicates that no terminal equipment was connected when  
ringing was attempted. Run the Short Test via the test port  
PCSSpp command, and follow the procedure for the results of Test  
#48.  
b. This is a software audit error that does not indicate any hardware  
malfunction. Run Short Test Sequence and investigate errors (if any).  
c. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
d. Test #48 may cause some terminal equipment to ring briefly during daily  
maintenance. If this ringing is disturbing the customer or the terminal  
equipment, it should be disabled via the change station <extension>  
command. However, on some releases of the software, this disables Tests  
#6, #47, and #35 as well as Test #48.  
e. Test #47 may cause a false alarm when the port is connected to  
off-premises equipment, some non-voice terminal equipment, and some  
loop equipment. If this causes a false alarm, then disable the test by  
changing the Tests field of the change station command to "no."  
f. Refer to "XXX-BD (Common Port Circuit Pack)" Maintenance  
documentation.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Battery Feed Test, for example, you may also clear errors generated from other  
tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-55  
Table 3-23. System Technician-Demanded Tests: ANL-LINE  
ShortTest  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Battery Feed Test (#35)  
D/ND  
X
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
Station Present Test (#48)  
NPE Crosstalk Test (#6)  
Loop Around and Conference Test (#47)  
Station Status and Translation Audits and Updates Test (#36)  
X
1. D = Destructive, ND = Non-destructive  
NPE Crosstalk Test (#6)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per-port basis. The NPECrosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is usually only part of a port’s Long Test Sequence  
and takes about 20 to 30 seconds to complete.  
Table 3-24. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension. Use the status station command to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. (Refer to the  
"Status Commands" section in Chapter 8, "Maintenance Commands and  
Trouble-Clearing Aids", for a full description of all possible states.) You  
must wait until the port is idle before retesting.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-56  
Table 3-24. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1001  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to "TDM-BUS (TDM Bus)" Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to "TTR-LEV  
(TTR Level)" Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to "TONE-PT  
(Tone Generator)" Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension. Use the status station command to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. (Refer to the  
"Status Commands" section in Chapter 8, "Maintenance Commands and  
Trouble-Clearing Aids", for a full description of all possible states.) You  
must wait until the port is idle before retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1005  
ABORT  
The test was aborted due to a configuration problem. This code will result  
under either of the following conditions:  
1. This test may not be applicable, or it may be disruptive to terminal  
equipment other than a voice terminal (for example, the modem pool  
member or music on hold).  
2. The circuit pack is one of the following:  
— TN742 vintages 13, 14 and 15  
— TN769 vintages 3, 4 and 5  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-57  
Table 3-24. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1018  
ABORT  
Test disabled via administration. The default for the ’Test’ field on the  
’Station’ form is ’y’; thus, you may want to determine why this field has  
been set to ’n’ on this station (this may be due to the ringing application  
test 48, which can be customer or terminal disturbing).  
1. To enable the test for a particular station, enter change station  
extension and set the ‘Test?’ field on the ‘Station Form’ to ‘y.’  
1020  
ABORT  
The test did not run due to a previously existing error on the specific port  
or a more general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit  
pack and attempt to diagnose the previously existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run this test are not available. Either a  
system allocation to get information about the port or to put the port into a  
service state failed or the attempt to put the port in connection with a tone  
source failed (this could be a tone-clock problem). The tone-clock and  
tone detectors could be having a communication problem, for example,  
the companding modes could be out of synchronization.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Any  
FAIL  
This test can fail due to on-board or off-board problems. Off-board  
problems of concern include EXP-INTF faults, TDM-BUS faults, and faults  
associated with the tone detectors/tone generators. Clear all off-board  
problems before replacing the board. Keep in mind that a TDM-BUS  
problem is usually the result of a faulty board connected to the backplane  
or bent pins on the backplane.  
1. Look for EXP-INTF errors in the error log. If present, refer to the  
EXP-INTF Maintenance documentation.  
2. Look for TDM-BUS errors in the error log. If present, refer to the  
TDM-BUS Maintenance documentation.  
3. Look for TONE-BD and/or TONE-PT errors in the error log. If present,  
refer to the TONE-BD Maintenance documentation and the TONE-PT  
Maintenance documentation.  
4. Test the board when the faults from steps 1, 2, and 3 are cleared.  
Replace the board only if the test fails.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-58  
Table 3-24. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated by using other port tests, by examining  
station wiring, by examining the station, and by ensuring that the terminal  
is correctly translated as off-premises or on-premises.  
NOTE:  
This test always passes for Analog circuit packs TN742 prior to  
Vintage 4.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command and resolve any problems.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Battery Feed Test (also called Port Diagnostic  
Test) (#35)  
The battery feed chip provides power to the telephone equipment, signaling,  
rotary dial pulsing, transmission, and balance. This test checks the signaling and  
switchhook capabilities of the battery feed chip by terminating the port, applying  
battery, and trying to detect a current.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-59  
Table 3-25. TEST #35 Battery Feed Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension. Use the status station command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. (Refer to the  
"Status Commands" section in Chapter 8, "Maintenance Commands and  
Trouble-Clearing Aids", for a full description of all possible states.) You  
must wait until the port is idle before retesting.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension. Use the status station command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. (Refer to the  
"Status Commands" section in Chapter 8, "Maintenance Commands and  
Trouble-Clearing Aids", for a full description of all possible states.) You  
must wait until the port is idle before retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1005  
ABORT  
The test was aborted due to a configuration problem. This code will result  
under either of the following conditions:  
1. This test may not be applicable, or it may be disruptive to terminal  
equipment other than a voice terminal (for example, the modem pool  
member or music on hold).  
2. The circuit pack is one of the following:  
— TN742 vintages 13, 14 and 15  
— TN769 vintages 3, 4 and 5  
1018  
ABORT  
Test disabled via administration. The default for the 'Test' field on the  
'Station' form is 'y'; thus, you may want to determine why this field has been  
set to 'n' on this station (this may be due to the ringing application test 48,  
which can be customer or terminal disturbing).  
1. To enable the test for a particular station, enter change station  
extension and set the ‘Test?’ field on the ‘Station Form’ to ‘y.’  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-60  
Table 3-25. TEST #35 Battery Feed Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
2100  
System resources required to run this test are not available. Either a system  
allocation to get information about the port or to put the port into a service  
state failed or the attempt to put the port in connection with a tone source  
failed (this could be a tone-clock problem). The tone-clock and tone  
detectors could be having a communication problem, for example, the  
companding modes could be out of synchronization.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
The port’s battery feed chip is unable to supply sufficient power to the  
terminal equipment. This may occur when the test is performed at the same  
time that the terminal equipment goes off-hook.  
1. Use status station to determine when the port is available for testing.  
When the port becomes available for testing, retry the command at  
1-minute intervals a minimum of 5 times.  
2. If the test continues to fail, determine whether the customer is  
experiencing problems on this line. Replace the circuit pack only if the  
customer is experiencing problems.  
PASS  
The port’s battery feed chip is able to provide power to the station  
equipment to detect on-/off-hook. However, the battery feed chip may still  
be unable to provide power for touch-tones. If tones are heard when  
buttons are pressed, then the battery feed chip is functioning correctly;  
otherwise, replace the circuit pack because this port is defective.  
User-reported troubles on this port should be investigated by using other  
port tests, by examining station wiring, by examining the station, and by  
ensuring that the terminal is correctly translated as off-premises or  
on-premises.  
NOTE:  
This test always passes for TN742 Analog circuit packs prior to  
Vintage 6.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-61  
Table 3-25. TEST #35 Battery Feed Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Station Status and Translation Audits and  
Updates Test (#36)  
This test updates the analog port’s message lamp state (if it has one) and  
translations (such as station type, dial type, network connection) with information  
kept in the software. The software is updated with the switchhook state reported  
by the port processor. When the ringer is in the off state, this test also turns off the  
station’s ringer to prevent constant ringing caused by defective hardware.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-62  
Table 3-26. TEST #36 Station Status and Translation Audits and Updates Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1004  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension. Use the status station command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. (Refer to the  
"Status Commands" section in Chapter 8, "Maintenance Commands and  
Trouble-Clearing Aids", for a full description of all possible states.) You  
must wait until the port is idle before retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1005  
ABORT  
The test was aborted due to a configuration problem. This code will result  
under either of the following conditions:  
1. This test may not be applicable, or it may be disruptive to terminal  
equipment other than a voice terminal (for example, the modem pool  
member or music on hold).  
2. The circuit pack is one of the following:  
— TN742 vintages 13, 14 and 15  
— TN769 vintages 3, 4 and 5  
1006  
ABORT  
This port has been busied out by command or taken out-of-service by the  
failure of the NPE Crosstalk Test.  
1. Look in the Error Log for Error Type 18 (port busied out) for this port. If  
this error is present, then release the port with the release station  
extension command and run the test again.  
2. Look in the Error Log for Error Type 1025 (NPE Crosstalk Test failed) for  
this port. If this error is present, then investigate the errors associated  
with the NPE Crosstalk Test (#6) first.  
3. Make sure that the terminal is connected and in service, and then  
retest.  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
2000  
2100  
Response to the test request was not received within the allowable time  
period.  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-63  
Table 3-26. TEST #36 Station Status and Translation Audits and Updates Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
FAIL  
This does not indicate a hardware problem. The switchhook audit failed,  
and the other updates were not performed because of this failure. This  
condition may occur when the audit is performed at the same time that the  
terminal equipment goes off-hook. Use the status station command to  
determine when the port is available for testing.  
1. When the port becomes available for testing, retry the command at  
1-minute intervals a maximum of 5 times.  
5
7
8
FAIL  
FAIL  
FAIL  
This does not indicate a hardware problem but may indicate an internal  
software error. The message waiting lamp update failed. The translation  
and ringer updates were not performed because of this failure.  
The translation update failed. The ringer update was not performed  
because of this failure. This does not indicate a hardware problem but may  
be an internal software error.  
This does not indicate a hardware problem but may be an internal software  
error. The ringer update failed.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
The software and the port processor have the same status. User-reported  
troubles on this port should be investigated by using other port tests, by  
examining station wiring, by examining the station, and by ensuring that the  
terminal is correctly translated as off-premises or on-premises.  
NOTE:  
This test always passes for TN742 Analog circuit packs prior to  
Vintage 6.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-64  
Loop Around and Conference Test (#47)  
Each Analog Port consists of:  
■
■
■
an NPE for port connectivity and gain, and conferencing functionality  
a code that converts the digital signals of the TDM Bus to analog signals  
a battery feed chip that provides power to the telephone set for signaling,  
dial pulsing, transmission, and balance  
This test is designed to check the on-board transmission capabilities of the NPE,  
the code, and the battery feed chip of the Analog Port. A Tone Detector and a  
Tone Generator talk and listen on the same pair of time slots as the Analog Port.  
The Analog Port is then instructed to go into loop around mode (see Figure 10-2).  
The test passes if the signal measured by the Tone Detector is within acceptable  
limits.  
The Conference Circuit Test verifies that the NPE channel for the port being  
tested can correctly perform the conferencing function. As part of Test #47, the  
operation of the port conference circuits in the NPE for three and four parties is  
also tested. In addition, a test is run to measure noise. The NPE is instructed to  
listen to several different tones and conference the tones together. The resulting  
signal is then measured by a Tone Detector port. If the level of the tone is within a  
certain range, the test passes.  
The noise test is performed by filtering out the tone and then measuring inherent  
port noise.  
NOTE:  
This Loop Around Test is sensitive to the length of the loop, the equipment  
in the loop, or the equipment terminating the loop, such as off-premises  
stations. If this test is causing a false alarm, then disable the test by  
changing the Tests field to "no" using the change station command for this  
station.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-65  
BFC*  
CODEC  
NPE*  
TN742,  
TN769,  
ETC.  
PORT  
TONE  
TONE  
LEVEL  
SOURCE  
MEASUREMENT  
TDM BUS  
* BFC - BATTERY FEED AND HYBRID CHIP  
NPE - NETWORK PROCESSING ELEMENT  
Figure 3-1. Analog Loop Around and Conference Test  
Table 3-27. TEST #47 Loop Around and Conference Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The port was seized by a user for a valid call.  
7
1. Enter display port PCSSpp to determine the station’s extension. Enter  
status station extension to determine the service state of the port. If  
the port is in use, it will be unavailable for certain tests. Wait until the  
port is idle before retesting.  
2. If the port is idle, retry the command at 1-minute intervals up to 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-66  
Table 3-27. TEST #47 Loop Around and Conference Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test were not available. The port may  
be busy with a valid call. (This could be a Music-on-Hold port.)  
1. Enter display port PCSSpp to determine the station’s extension. Enter  
status station extension to determine the service state of the port. If  
the port is in use, it will be unavailable for certain tests. Wait until the  
port is idle before retesting.  
2. If the port is idle, retry the command at 1-minute intervals up to 5 times.  
1002  
1003  
ABORT  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to "TDM-BUS (TDM Bus)" Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to "TTR-LEV  
(TTR Level)" Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to "TONE-PT  
(Tone Generator)" Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port has been seized for a valid call during the conference or noise  
test. Use the status station command to determine when the port is  
available for testing.  
1. If the circuit pack is a TN742 with vintage 10 or less, this test is not  
valid. Otherwise, proceed with #2.  
2. When the port is available for testing, retry the command at 1-minute  
intervals a maximum of 5 times.  
1005  
ABORT  
The test was aborted due to a configuration problem. This code will result  
under either of the following conditions:  
1. This test may not be applicable, or it may be disruptive to terminal  
equipment other than a voice terminal (for example, the modem pool  
member or music on hold).  
2. The circuit pack is one of the following:  
— TN742 vintages 13, 14 and 15  
— TN769 vintages 3, 4 and 5  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-67  
Table 3-27. TEST #47 Loop Around and Conference Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1018  
ABORT  
Test disabled via administration. The default for the ’Test’ field on the  
’Station’ form is ’y’; thus, you may want to determine why this field has been  
set to ’n’ on this station (this may be due to the ringing application test 48,  
which can be customer or terminal disturbing).  
1. To enable the test for a particular station, enter change station  
extension and set the ‘Test?’ field on the ‘Station Form’ to ‘y.’  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run this test are not available. Either a system  
allocation to get information about the port or to put the port into a service  
state failed or the attempt to put the port in connection with a tone source  
failed (this could be a tone-clock problem). The tone-clock and tone  
detectors could be having a communication problem, for example, the  
companding modes could be out of synchronization.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
7
FAIL  
The conference test or the noise test failed. This could cause noisy or  
unreliable connections, or users calling this port may hear an echo. The  
problem can also be off-board, as described below.  
13  
14  
The reflective loop around with gain set to low and the 600-ohm balance  
failed. This will cause noisy or unreliable connections.  
The reflective loop around test (with the gain set to high, using RC balance)  
failed. This could cause noisy or unreliable connections. The problem can  
also be off-board, as described below.  
15  
The nonreflective loop around test failed. This could cause noisy or  
unreliable connections, or users calling this port may hear an echo. The  
problem can also be off-board, as described below.  
More information follows.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-68  
Table 3-27. TEST #47 Loop Around and Conference Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
7
13  
FAIL  
(cont’d.)  
1. Disconnect the terminal equipment from the circuit pack at the  
cross-connect and run the test again.  
14  
15  
2. If the test fails again, replace the circuit pack and reconnect the  
terminal equipment. If the test passes the second time, then the test  
results were affected by the terminal equipment connected to the port;  
in this case, ignore the results of this test if all other tests pass or abort  
and the station is operating properly. Failure of test 47 does not cause  
an alarm. If there are failures of other tests, then investigate those  
errors. User reported troubles with this port should be investigated by  
using other port tests, by examining station wiring, and by examining  
the station to ensure that it is correctly translated as off-premises or  
on-premises.  
(cont’d.)  
NOTE:  
If the loop around and conference circuit test fails for all ports on a  
circuit pack, a -5 volt power problem is indicated.  
PASS  
The port is able to provide an analog transmission path to the station  
equipment. User-reported troubles on this port should be investigated by  
using other port tests, by examining station wiring, by examining the  
station, and by ensuring that the terminal is correctly translated as  
off-premises or on-premises.  
NOTE:  
This test always passes for TN742 Analog circuit packs prior to  
Vintage 6.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-69  
Station Present Test (also called Ringing  
Application Test) (#48)  
This test provides a burst of ringing current to the terminal equipment and  
detects that current flows. This test is to ascertain whether or not terminal  
equipment is connected to the port.  
This test may cause some terminal equipment to ring briefly during daily  
maintenance. If this ringing is disturbing the customer or the terminal equipment,  
it should be disabled using the Tests field of the station administration screen.  
However, on some releases of the software, this action disables Tests #6, #47,  
and #35 as well as Test #48.  
Table 3-28. TEST #48 Station Present Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test were not available. The port may  
be busy with a valid call.  
Use the display port PCSSpp to determine the station’s extension. Enter  
status station extension to determine the service state of the port. If the  
port is in use, it will be unavailable for certain tests. Wait until the port is idle  
before retesting.  
1. If the port is idle, retry the command at 1-minute intervals up to 5 times.  
2. Check for phone left off-hook or for wiring problems.  
1004  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension. Use the status station command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. (Refer to the  
"Status Commands" section in Chapter 8, "Maintenance Commands and  
Trouble-Clearing Aids", for a full description of all possible states.) You  
must wait until the port is idle before retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-70  
Table 3-28. TEST #48 Station Present Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1005  
ABORT  
The test was aborted due to a configuration problem. This code will result  
under either of the following conditions:  
1. This test may not be applicable, or it may be disruptive to terminal  
equipment other than a voice terminal (for example, the modem pool  
member or music on hold).  
2. The circuit pack is one of the following:  
— TN742 vintages 13, 14 and 15  
— TN769 vintages 3, 4 and 5  
1008  
ABORT  
Could not allocate a ringing circuit for one of the following reasons:  
■ All the ringing circuits are in use, or  
■ The ringing generator is defective, or  
■ It is not wired correctly.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort, look for RING-GEN errors in the Error Log.  
If an ABORT 1008 occurs for Test #48 on other circuit packs as well,  
then the ring generator may be defective. If it does not occur on other  
ports, then that circuit pack is currently using all 4 ringing phases.  
1018  
ABORT  
The test was disabled via administration. The default for the 'Test' field on  
the 'Station' form is 'y'; thus, you may want to determine why this field has  
been set to 'n' on this station (this may be due to the ringing application test  
48, which can be customer or terminal disturbing).  
1. To enable the test for a particular station, enter change station  
<extension> and set the Test?field on the station form to y.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run this test are not available. Either a system  
allocation to get information about the port or to put the port into a service  
state failed or the attempt to put the port in connection with a tone source  
failed (this could be a tone-clock problem). The tone-clock and tone  
detectors could be having a communication problem, for example, the  
companding modes could be out of synchronization.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line)  
3-71  
Table 3-28. TEST #48 Station Present Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
The terminal equipment is not connected to the circuit pack or the ringing  
generator may have failed.  
1. Remotely test the equipment.  
2. If the test fails again, look for RING-GEN errors in the error log. If  
present, refer to the RING-GEN (analog ring generator) Maintenance  
documentation.  
3. Check all of the wiring between the station equipment and the switch.  
Then, run the test again.  
4. If the test still fails, the set may be defective. Check the set, and  
replace it, if necessary.  
5. Some terminal equipment (such as a modem) could fail even when it is  
connected properly. If this is the case, disable the test using the  
change station extension command (enter ’n’ into the ’Test’ field).  
Note that this action also disables tests 6, 7, 161, and 35 on this port.  
PASS  
The station is connected properly to the switch. This test may also pass if  
no terminal equipment is connected and the terminal is located far from the  
switch (that is, it is off-premises). User-reported troubles on this port should  
be investigated by using other port tests, by examining station wiring, by  
examining the station, and by ensuring that the terminal is correctly  
translated as off-premises or on-premises.  
NOTE:  
This test always passes for TN742 Analog circuit packs prior to  
Vintage 6.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-72  
AN-LN-PT (Analog Line  
Port)  
MO Name (in  
Initial Command to  
Run  
1
Alarm Log)  
AN-LN-PT  
AN-LN-PT  
Alarm Level  
MIN  
Full Name of MO  
Analog Line Port  
Analog Line Port  
test port UUCSSpp l  
test port UUCSSpp sh  
WRN  
1. UU is the universal cabinet number (1 for PPN, 2 -44 for EPNs). C is the carrier  
designation (A, B, C, D, or E). SSis the number of the slot in which the circuit pack resides  
(01 to 21). pp is the two digit port number (01, 02, ...).  
The TN793B/TN2793B Analog Line circuit pack (w/ Caller ID), and the TN797  
Analog Trunk and Line circuit pack both support this Maintenance Object.  
The TN793B/TN2793B Analog Line circuit pack (w/ Caller ID) provides 24 ports  
for voice terminals and supports both on-premises and off-premises analog  
voice terminals.  
The TN797 Analog Trunk and Line circuit pack provides 8 ports, each of which  
may be administered in any of several ways, as described in maintenance object  
TR-LN-BD.  
NOTE:  
The TN793B/TN2793B analog line circuit pack supports analog data  
modules. When assigned, analog data modules provide access to the  
NetPkt (TN794 circuit pack) data ports. To activate an analog data module  
you must assign the port location on the data form and connect a modem  
to the port. The analog data module can be used for connection to a CDR  
output, or other adjuncts as needed. These ports are tested the same as all  
other analog ports on the circuit pack.  
Ringing caused by maintenance testing  
Test #48 may cause some terminal equipment to ring briefly during daily  
maintenance. If this ringing disturbs the customer or the terminal equipment,  
disable it in the Testsfield of the change station extension form. Be aware that  
this action also disables Tests #6, 7, 161, and 35 on some software releases.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-73  
Error log entries and test to clear values  
Table 3-29. Analog line error log entries  
Error  
Type  
Aux  
Data  
Associated  
Test  
Alarm  
Level  
On/Off  
Board  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
test port UUCSSpp sh r 1  
1(a)  
15(b)  
18  
40960  
40975  
40977  
none  
Any  
Audits and  
Updates Test  
(#36)  
0
busy station  
extension  
WRN  
WRN  
ON  
ON  
release station extension  
130(c)  
257(d)  
513(e)  
None  
none  
test port UUCSSpp sh  
40973  
Station  
WRN  
OFF  
test port UUCSSpp sh r 2  
Present Test  
(#48)  
769  
Battery Feed  
Test (#35)  
MIN/  
WRN  
ON  
ON  
ON  
ON  
test port UUCSSpp sh r 2  
test port UUCSSpp l r 2  
test port UUCSSpp l r 2  
test port UUCSSpp l r 2  
2
1025  
1281  
1537  
Looparound  
Test (#161)  
MIN/  
WRN  
2
Conference  
Test (#7)  
MIN/  
WRN  
2
NPE  
MIN/  
2
CrosstalkTest WRN  
(#6)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the  
set options command.  
Notes:  
a. Error Type 1: these are in-line errors and can only be resolved over time.  
■
Aux Data 40960 indicates that too many simultaneous incoming  
ringing attempts were made on this board. Only 4 ports on a board  
may ring simultaneously. A 5th incoming call will cause an inline  
error from the board.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-74  
■
Aux Data 40975 indicates that the terminal equipment was on-hook  
when ring-tip was detected during ringing. This usually indicates a  
failure in the terminal equipment or the type of terminal has a low  
ringer impedance.  
1. Call the terminal equipment and verify that the terminal rings.  
2. If the terminal does not ring, then replace it.  
3. Otherwise, issue the test port UUCSSpp command, and  
follow the procedure for Test #48.  
■
40977 indicates that no terminal equipment was connected when  
ringing was attempted.  
1. Run the short test via the test port UUCSSpp command,  
and follow the procedure for the results of Test #48.  
b. Error Type 15: this is a software audit error that does not indicate any  
hardware malfunction.  
1. Run the Short Test Sequence and investigate any associated  
errors.  
c. Error Type 130: this error type indicates that the circuit pack has been  
removed or has been insane for more than 11 minutes.  
1. To clear the error, reseat or replace the circuit pack.  
d. Error Type 257: this is an in-line error and can only be resolved over time.  
This error indicates that ringing voltage is absent.  
1. If only 1 analog circuit pack in the system has this problem, replace  
the circuit pack.  
2. If only analog circuit packs on a particular carrier have this error,  
the ringing generator may not be connected to this carrier.  
3. If analog circuit packs on many carriers have this error, it is  
probably a problem with the ringing generator.  
e. Error Type 513:Test #48 can cause some terminal equipment to ring  
briefly during daily maintenance.  
1. If this disturbs the customer or the terminal equipment, disable it by  
setting the Testsfield on the change station extension form to n.  
On some software releases, this also disables Tests #6, 7, 161, and  
35.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-75  
System technician-demanded tests: descriptions  
and error codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Battery Feed Test, for example, you may also clear errors generated from other  
tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
Order of Investigation  
Battery Feed Test (#35)  
Station Present Test (#48)  
Looparound Test (#161)  
Conference Test (#7)  
D/ND1  
ND  
X
X
X
X
X
X
X
X
ND  
ND  
ND  
NPE Crosstalk Test (#6)  
ND  
Station Status and Translation Audits and  
Updates Test (#36)  
X
ND  
1. D = Destructive; ND = Nondestructive  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-76  
NPE Crosstalk Test (#6)  
This test verifies that the port’s NPE channel talks on the selected time slot and  
never crosses over to time slots reserved for other connections. If the NPE is not  
working correctly, one-way and noisy connections may be observed. This test is  
usually part of the long test sequence and takes about 20 to 30 seconds to  
complete.  
Table 3-30. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
Necessary system resources could not be allocated to run this test.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
1000  
ABORT  
System resources are unavailable. The port may be busy with a valid call.  
This result is also reported for the system’s Music-On-Hold port when it is  
off-hook, which it usually is.  
1. Enter display port UUCSSpp to determine the station’s extension.  
2. Enter status station extension to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle. Retry the command at  
1-minute intervals no more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1001  
1002  
ABORT  
ABORT  
System resources required to run test are not available. This could be due  
to a failure to seize the port.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or have time slots out-of-service due to  
TDM-BUS errors.  
1. Refer to “TDM-BUS” to diagnose any active TDM-BUS errors.  
2. If the system has no TDM-BUS errors and is not handling heavy traffic,  
retry the command at 1-minute intervals no more than 5 times.  
3. If the test continues to abort, escalate the problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-77  
Table 3-30. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present or some tone  
detectors may be out-of-service.  
1. Resolve any TTR-LEV errors in the Error Log.  
2. Resolve any TONE-PT errors in the Error Log.  
3. If neither condition exists, retry the command at 1-minute intervals no  
more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1004  
ABORT  
A valid call seized the port during the test and aborted the test.  
1. Use the display port UUCSSpp command to determine the station  
extension.  
2. Use the status station extension command to determine the service  
state of the port.  
3. If the port is in use, wait until the port is idle before testing. Retry the  
command at 1-minute intervals no more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1005  
1018  
ABORT  
ABORT  
This test was aborted due to a configuration problem. The test is not  
applicable for this type of analog port. This error can be ignored.  
Administration has disabled the test. The default for the Test?field on the  
station form is y. Determine why this field has been set to n on this station  
(this may be due to the ringing application Test #48, which can be  
disturbing to customer or terminal equipment).  
1. To enable the test for a particular station being tested, enter change  
station extension.  
2. Change the Test?field on the station form to y.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run test are not available. This could be due  
to a failure to seize the port.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-78  
Table 3-30. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
Any  
FAIL  
This test can fail due to on-board or off-board problems. Off-board  
problems include TDM-BUS faults, EXP-PN and EXP-INTF faults, and faults  
associated with the tone detectors/tone generators. Clear all off-board  
problems before replacing the board.  
1. A TDM-BUS problem is usually the result of a faulty board connection  
to the backplane, or bent pins on the backplane. Resolve any  
TDM-BUS errors in the error log.  
2. Resolve any EXP-PN and/or EXP-INTF errors in the error log.  
3. Resolve any TONE-BD and/or TONE-PT errors in the error log.  
4. Test the board when the faults from Steps 1, 2, and 3 are cleared.  
Replace the board only if the test fails.  
PASS  
The port is correctly using its allocated time slots. Investigate user-reported  
troubles on this port by running other port tests, by examining station  
wiring, or by inspecting the station.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This result  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to make sure that the board translations are correct. Use the list  
configuration command, and resolve any problems.  
2. If the board is correctly inserted, issue the busy board UUCSS  
command.  
3. Issue the reset board UUCSS command.  
4. Issue the release board UUCSS command.  
5. Issue the test board UUCSS long command. This re-establishes the  
link between the internal ID and the port.  
6. If this is not the case, check to make sure that a valid board is inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-79  
Conference Circuit Test (#7)  
This test verifies that the NPE channel for the port being tested correctly  
performs the conferencing function.  
Table 3-31. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
Necessary system resources could not be allocated to run this test.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
1000  
ABORT  
System resources are unavailable. The port may be busy with a valid call.  
This result is also reported for the system’s Music-On-Hold port when it is  
off-hook, which it usually is.  
1. Enter display port UUCSSpp to determine the station’s extension.  
2. Enter status station extension to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle. Retry the command at  
1-minute intervals no more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1004  
ABORT  
A valid call seized the port during the test and aborted the test.  
1. Use the display port UUCSSpp command to determine the station  
extension.  
2. Use the status station extension command to determine the service  
state of the port.  
3. If the port is in use, wait until the port is idle before testing. Retry the  
command at 1-minute intervals no more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1005  
1018  
ABORT  
ABORT  
This test was aborted due to a configuration problem. The test is not  
applicable for this type of analog port. This error can be ignored.  
Administration has disabled the test. The default for the Test?field on the  
station form is y. Determine why this field has been set to n on this station  
(this may be due to the ringing application Test #48, which can be  
disturbing to customer or terminal equipment).  
1. To enable the test for a particular station being tested, enter change  
station extension.  
2. Change the Test?field on the station form to y.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-80  
Table 3-31. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
2000  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
2100  
System resources required to run this test are not available.  
1. Resolve any TONE-PT errors in the error log.  
2. If there are no TONE-PT errors, retry the command at 1-minute  
intervals no more than 5 times.  
3. If the test continues to abort, escalate the problem.  
Any  
FAIL  
The NPE of the tested port did not conference the tones correctly. This  
causes noisy and unreliable connections.  
1. Issue the display port UUCSSpp and the status station extension  
commands to determine if the station is idle.  
2. If the station is idle, issue the test port UUCSSpp command for this  
port.  
3. If the test continues to fail, issue the busy port UUCSSpp and the  
release port UUCSSpp commands, and then retest.  
4. If the test still fails, replace the board.  
PASS  
The port can correctly conference multiple connections. Investigate  
user-reported troubles on this port by running other port tests; by  
examining station, trunk, or external wiring; or by inspecting the station.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This result  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to make sure that the board translations are correct. Use the  
list configuration command, and resolve any problems.  
2. If the board is correctly inserted, issue the busy board UUCSS  
command.  
3. Issue the reset board UUCSS command.  
4. Issue the release board UUCSS command.  
5. Issue the test board UUCSS long command. This re-establishes the  
link between the internal ID and the port.  
6. If this is not the case, check to make sure that a valid board is  
inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-81  
Battery Feed Test (also called Port Diagnostic  
Test) (#35)  
The battery feed chip provides power to the telephone equipment, signaling,  
rotary dial pulsing, transmission, and balance. This test checks the signaling and  
switchhook capabilities of the battery feed chip by terminating the port, applying  
battery power, and detecting the resulting current.  
Table 3-32. TEST #35 Battery Feed Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
Necessary system resources could not be allocated to run this test.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
1000  
ABORT  
System resources are unavailable. The port may be busy with a valid call.  
This result is also reported for the system’s Music-On-Hold port when it is  
off-hook, which it usually is.  
1. Enter display port UUCSSpp to determine the station’s extension.  
2. Enter status station extension to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle. Retry the command at  
1-minute intervals no more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1004  
ABORT  
A valid call seized the port during the test and aborted the test.  
1. Use the display port UUCSSpp command to determine the station  
extension.  
2. Use the status station extension command to determine the service  
state of the port.  
3. If the port is in use, wait until the port is idle before testing. Retry the  
command at 1-minute intervals no more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1005  
1018  
ABORT  
ABORT  
This test was aborted due to a configuration problem. The test is not  
applicable for this type of analog port. This error can be ignored.  
Administration has disabled the test. The default for the Test?field on the  
station form is y. Determine why this field has been set to n on this station  
(this may be due to the ringing application Test #48, which can be  
disturbing to customer or terminal equipment).  
1. To enable the test for a particular station being tested, enter change  
station extension.  
2. Change the Test?field on the station form to y.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-82  
Table 3-32. TEST #35 Battery Feed Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1392  
ABORT  
This port is currently a TTI port and the test does not execute on it.  
1. Verify that the port is a TTI port:  
■
Enter the display port UUCSSpp command (the display shows  
that the port is a TTI port).  
■
Enter the list configuration command (the display shows a tfor  
the port).  
2. If both commands indicate that the port is a TTI port, the abort is  
correct for the test, and no action is necessary.  
3. If either command indicates that the port is not a TTI port, escalate the  
problem.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
FAIL  
The port’s battery feed chip is unable to supply sufficient power to the  
terminal equipment. This test result might be marginal, and the terminal  
equipment may be operating satisfactorily.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to fail, determine whether the customer is  
experiencing problems on this line. Replace the circuit pack only if  
the customer is experiencing problems.  
PASS  
The port’s battery feed chip is able to provide sufficient power to the  
station equipment to detect on-/off-hook, but may not be able to supply  
power for touch-tones.  
1. If touch-tones are inoperative on this station, replace the circuit pack  
because this port is inoperative.  
2. Investigate user-reported troubles on this port by running other port  
tests, by examining station wiring, or by inspecting the station.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-83  
Table 3-32. TEST #35 Battery Feed Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This result  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to make sure that the board translations are correct. Use the  
list configuration command, and resolve any problems.  
2. If the board is correctly inserted, issue the busy board UUCSS  
command.  
3. Issue the reset board UUCSS command.  
4. Issue the release board UUCSS command.  
5. Issue the test board UUCSS long command. This re-establishes the  
link between the internal ID and the port.  
6. If this is not the case, check to make sure that a valid board is  
inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-84  
Station Status and Translation Audits and  
Updates Test (#36)  
This test updates the analog port’s message lamp state (if it has one) and  
translations with information in the software.  
Table 3-33. Test #36 Station Status and Translation Audits and Updates  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Necessary system resources could not be allocated to run this test.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
A valid call seized the port during the test and aborted the test.  
1004  
ABORT  
1. Use the display port UUCSSpp command to determine the station  
extension.  
2. Use the status station extension command to determine the  
service state of the port.  
3. If the port is in use, wait until the port is idle before testing. Retry the  
command at 1-minute intervals no more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1005  
1006  
ABORT  
ABORT  
This test was aborted due to a configuration problem. The test is not  
applicable for this type of analog port. This error can be ignored.  
The port is out-of-service. The busy station extension command has  
been given to this port, or it has been taken out-of-service by the failure of  
the NPE Crosstalk Test.  
1. Look for error type 18 (port busied out) for this port. If this error is  
present, release the port (release station extension), and run the  
test again.  
2. Check for error type 1537 (NPE Crosstalk Test failed) for this port. If  
this error is present, investigate the errors associated with the NPE  
Crosstalk Test (#6).  
3. Make sure that the terminal is connected and in service, and then  
retest.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-85  
Table 3-33. Test #36 Station Status and Translation Audits and Updates — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
FAIL  
The switchhook audit failed. This result does not indicate a hardware  
problem. The other updates were not performed because of this failure.  
This may occur if the audit is performed at the same time the terminal  
equipment goes off-hook.  
1. Use the status station extension command to determine when the  
port is available.  
2. Retry the command at 1-minute intervals no more than 5 times.  
3. If the test continues to fail, escalate the problem.  
5
FAIL  
The message waiting lamp update failed. This may be an internal  
software error. The translation and ringer updates were not performed  
because of this failure.  
7
8
FAIL  
FAIL  
The translation update failed. There may be an internal software error.  
The ringer update was not performed because of this failure.  
The ringer update failed. There may be an internal software error.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to fail, escalate the problem.  
PASS  
The software and the port processor have the same status. Investigate  
user-reported troubles on this port by running other port tests, by  
examining station wiring, or by inspecting the station.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This result  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to make sure that the board translations are correct. Use the  
list configuration command, and resolve any problems.  
2. If the board is correctly inserted, issue the busy board UUCSS  
command.  
3. Issue the reset board UUCSS command.  
4. Issue the release board UUCSS command.  
5. Issue the test board UUCSS long command. This re-establishes the  
link between the internal ID and the port.  
6. If this is not the case, check to make sure that a valid board is  
inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-86  
Station Present Test (also called Ringing  
Application Test) (#48)  
This test applies momentary ringing voltage to the terminal equipment and  
monitors resulting current flow to determine whether terminal equipment is  
connected to the port. This test may cause some terminal equipment to ring  
briefly during daily maintenance. If this ringing disturbs the customer or the  
terminal equipment, you can disable it via the Testsfield on the change station  
extension form. However, on some software releases, Tests #6, 7, 161, and 35  
also are disabled.  
Table 3-34. TEST #48 Station Present Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
Necessary system resources could not be allocated to run this test.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
1000  
ABORT  
System resources are unavailable. The port may be busy with a valid call.  
This result is also reported for the system’s Music-On-Hold port when it is  
off-hook, which it usually is.  
1. Enter display port UUCSSpp to determine the station’s extension.  
2. Enter status station extension to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle. Retry the command at  
1-minute intervals no more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1004  
ABORT  
A valid call seized the port during the test and aborted the test.  
1. Use the display port UUCSSpp command to determine the station  
extension.  
2. Use the status station extension command to determine the service  
state of the port.  
3. If the port is in use, wait until the port is idle before testing. Retry the  
command at 1-minute intervals no more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1005  
ABORT  
This test was aborted due to a configuration problem. The test is not  
applicable for this type of analog port. This error can be ignored.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-87  
Table 3-34. TEST #48 Station Present Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1008  
ABORT  
A ringing circuit could not be allocated. Either all of the ringing circuits are  
in use, the ringing generator is defective, or it is not wired correctly.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, look for RING-GEN errors in the Error  
Log.  
3. If ABORT 1008 occurs for this test on other circuit packs as well, the  
ringing generator may be defective or is not wired correctly (see  
RING-GEN).  
4. If an ABORT 1008 does not occur on other ports, then all four ring  
phases are in use.  
1018  
ABORT  
Administration has disabled the test. The default for the Test?field on the  
station form is y. Determine why this field has been set to n on this station  
(this may be due to the ringing application Test 48, which can be  
disturbing to customer or terminal equipment).  
1. To enable the test for a particular station being tested, enter change  
station extension.  
2. Change the Test?field on the station form to y.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period. .  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
FAIL  
The terminal equipment is not connected to the circuit pack. Some  
terminal equipment, such as modems, may fail even when connected  
properly.  
1. Remotely test the terminal equipment.  
2. If the test fails again, resolve any RING-GEN errors in the error log, if  
present.  
3. Check all of the wiring between the station equipment and the switch.  
Then, run the test again.  
4. If the test still fails, the terminal equipment may be defective. Check  
and replace it, if necessary.  
5. Some terminal equipment might fail even when it is connected  
properly. If this is the case, disable the test using the change station  
extension command (enter n into the Testfield). Note that this action  
also disables Tests 6, 7, 35, and 161 on this port.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-88  
Table 3-34. TEST #48 Station Present Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
PASS  
The station is connected properly to the switch. Investigate user-reported  
troubles on this port by running other port tests, by examining station  
wiring, or by inspecting the station.  
NOTE:  
This test may also pass if no terminal equipment is connected and  
the terminal is located very far from the switch.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This result  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to make sure that the board translations are correct. Use the  
list configuration command, and resolve any problems.  
2. If the board is correctly inserted, issue the busy board UUCSS  
command.  
3. Issue the reset board UUCSS command.  
4. Issue the release board UUCSS command.  
5. Issue the test board UUCSS long command. This re-establishes the  
link between the internal ID and the port.  
6. If this is not the case, check to make sure that a valid board is  
inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-89  
Looparound Test (#161)  
This test checks the on-board transmission capabilities of the NPE, the codec,  
and the battery feed chip of the analog port. The test passes if the signal  
measured by the tone detector is within acceptable limits.  
Table 3-35. TEST #161 Looparound Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
Necessary system resources could not be allocated to run this test.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
1000  
ABORT  
System resources are unavailable. The port may be busy with a valid call.  
This result is also reported for the system’s Music-On-Hold port when it is  
off-hook, which it usually is.  
1. Enter display port UUCSSpp to determine the station’s extension.  
2. Enter status station extension to determine the service state of the  
port.  
3. If the port is in use, wait until the port is idle. Retry the command at  
1-minute intervals no more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1002  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or have time slots out-of-service due to  
TDM-BUS errors.  
1. Refer to “TDM-BUS” to diagnose any active TDM-BUS errors.  
2. If the system has no TDM-BUS errors and is not handling heavy traffic,  
retry the command at 1-minute intervals no more than 5 times.  
3. If the test continues to abort, escalate the problem.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present or some tone  
detectors may be out-of-service.  
1. Resolve any TTR-LEV errors in the Error Log.  
2. Resolve any TONE-PT errors in the Error Log.  
3. If neither condition exists, retry the command at 1-minute intervals no  
more than 5 times.  
4. If the test continues to abort, escalate the problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-90  
Table 3-35. TEST #161 Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1004  
ABORT  
A valid call seized the port during the test and aborted the test.  
1. Use the display port UUCSSpp command to determine the station  
extension.  
2. Use the status station extension command to determine the service  
state of the port.  
3. If the port is in use, wait until the port is idle before testing. Retry the  
command at 1-minute intervals no more than 5 times.  
4. If the test continues to abort, escalate the problem.  
1005  
1018  
ABORT  
ABORT  
This test was aborted due to a configuration problem. The test is not  
applicable for this type of analog port. This error can be ignored.  
Administration has disabled the test. The default for the Test?field on the  
station form is y. Determine why this field has been set to n on this station  
(this may be due to the ringing application Test 48, which can be  
disturbing to customer or terminal equipment).  
1. To enable the test for a particular station being tested, enter change  
station extension.  
2. Change the Test?field on the station form to y.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals no more than 5 times.  
2. If the test continues to abort, escalate the problem.  
FAIL  
The reflective Looparound Test failed. This could cause noisy or unreliable  
connections, or users calling this port may hear an echo. The problem can  
also be off-board.  
1. Since a line seizure may affect the test, repeat the test at 1-minute  
intervals for no more than 5 times.  
2. Using the test board UUCSS short command, run circuit pack tests  
to check the tone generator and the tone detector circuit packs.  
3. Resolve any problems on the tone generator or the tone detector  
circuit packs.  
4. If the tone generator and tone detector circuit packs are functioning  
properly, determine if a voice terminal is connected and wired  
properly. Resolve any problems found.  
5. If the test still fails, replace the analog line circuit pack.  
PASS  
The port provides an analog transmission path to the station equipment.  
Investigate user-reported troubles on this port by running other port tests,  
by examining station wiring, or by inspecting the station.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AN-LN-PT (Analog Line Port)  
3-91  
Table 3-35. TEST #161 Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This result  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to make sure that the board translations are correct. Use the  
list configuration command, and resolve any problems.  
2. If the board is correctly inserted, issue the busy board UUCSS  
command.  
3. Issue the reset board UUCSS command.  
4. Issue the release board UUCSS command.  
5. Issue the test board UUCSS long command. This re-establishes the  
link between the internal ID and the port.  
6. If this is not the case, check to make sure that a valid board is  
inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-92  
ANN-BD (Announcement Circuit  
Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
Announcement Circuit Pack  
Announcement Circuit Pack  
ANN-BD  
ANN-BD  
MINOR  
WRN  
test board PCSS l  
test board PCSS l  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example,  
A, B,or C); and SS is the address of the slot in the carrier where the circuit pack is located  
(for example, 01, 02, ..., etc.).  
The TN750 Announcement circuit pack is a service circuit which provides an  
integrated means for recording announcements that can be played back on  
demand by call processing as part of a calling feature (for example,  
announcements on hunt group calls). There are 16 Announcement Ports on the  
Announcement circuit pack. Each port can play any integrated announcement,  
independently of the other ports. In addition to the 16 Announcement Ports, the  
Announcement circuit pack also has one Data Line Circuit Port (port 17). The  
Data Line Circuit Port is used for uploading/downloading the announcement  
memory to/from the memory card. If there are any errors associated with port 17,  
refer to ‘‘DAT-LINE (Data Line)’’ Maintenance documentation. If there are any  
errors associated with any other port, refer to ‘‘ANN-PT (Announcement Port)’’  
Maintenance documentation.  
NOTE:  
TN750C is required if your system has multiple announcement boards (up  
to ten are allowed). Only one TN750A/B may be present in the system when  
a TN750C is used. The announcements from a TN750A/B can be saved  
and restored to a TN750C — but once the announcements are recorded  
onto a TN750C, they are not backward compatible with the TN750A/B.  
The Announcement circuit pack has two processors on it. The first processor, or  
Angel, controls the circuit pack and communicates with the switch via the control  
channel on the TDM Bus. The second processor, or Speech Processor (SP),  
controls the speech memory and announcements. Digital speech is converted  
from its TDM Bus form to an internal storage form (for recording) and vice versa  
(for playbacks) by the 140AY device on the circuit pack, which has 16 channels  
(one for each Announcement Port).  
General Notes  
Here are a few very important general notes that apply to any problem on the  
Announcement circuit pack. The user should read this before attempting to work  
on the TN750 Announcement circuit pack or Announcement Ports, especially if  
the circuit pack needs to be replaced.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-93  
1. The TN750 Announcement circuit pack retains all integrated  
announcements as long as the circuit pack has power. For this reason,  
whenever there is a problem with either the Announcement circuit pack or  
an Announcement Port that may require the circuit pack to be reset, it is  
always best to try to reset the circuit pack via the reset board PCSS  
command first. If that does not work, replace the circuit pack.  
Announcements are preserved through a software reset, but they are  
lost when the circuit pack is reseated.  
2. If a customer has announcements on the Announcement circuit pack,  
then announcements must be saved on the memory card to ensure  
that they are not lost. This should be done as soon as the  
announcements are recorded on the circuit pack (or whenever they are  
changed), assuming that the circuit pack is in proper working order (see  
Note).  
NOTE:  
Unlike translations, announcements are NEVER automatically saved  
to the memory card.  
3. The save announcements command replaces the announcement file on  
the memory card. Care must be taken not to mistakenly enter this  
command and, as a result, destroy a valid file on the memory card.  
4. The restore announcements command replaces the Announcement  
circuit pack speech memory with the announcement file on the memory  
card. Care must be taken not to mistakenly enter this command,  
destroying valid speech memory, especially if the memory card does not  
have a valid announcement file on it.  
5. Whenever the Announcement circuit pack is replaced, announcements  
must always be rerecorded or downloaded to the new circuit pack.  
Otherwise, call processing is not able to use the pack.  
6. If announcement speech memory is corrupted, announcements should  
not be saved [that is, if the Announcement Checksum Test (#209) fails, or  
if the speech sounds corrupted on playback]. This can ruin a good  
announcement file on the memory card and potentially cause  
errors/alarms on any circuit pack to which the new file is downloaded.  
However, if the customer does not have a valid announcement file on the  
memory card, announcements can be saved in an effort to try to retain  
some of them (all of the announcements recorded may not be corrupted).  
7. Due to a hardware fault in the TN750 announcement board, the following  
sequence of events my cause the announcement file to become corrupted  
and unusable:  
■
■
■
Fill the board with recorded announcements.  
Delete the last few announcements recorded.  
Re-record the announcements deleted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-94  
If the announcement file becomes corrupted, the only solution is to  
re-record all announcements. To do this, follow these steps:  
a. Remove the announcement board.  
b. Remove the tape cartridge from the tape drive. Do this so that  
announcements are not automatically restored from tape.  
c. Re-insert the announcement board.  
d. Re-record all announcements.  
e. Insert the tape cartridge in the tape drive.  
f. Issue the save announcements command to save all the  
announcements on the tape.  
This hardware fault is fixed in the TN750B announcement board. However,  
the TN750B board will not automatically correct an announcement file  
which has previously been corrupted by a TN750 board. The only way to  
correct an announcement file corrupted by the TN750 board is to follow  
the steps above.  
Announcement Administration  
A brief description of the integrated announcement administration is given here  
to aid in troubleshooting the Announcement circuit pack and its ports. In many  
cases, it is necessary to record, play back, and/or delete announcements to  
resolve an alarm. It may also be necessary to save and restore announcements  
as part of the maintenance procedures. For a complete description of integrated  
announcement administration, please refer to DEFINITY Enterprise  
Communications Server Administrator’s Guide.  
Announcement Session  
Announcements can be recorded, played back, and deleted from an  
announcement session. A station’s COS needs to include console permissions in  
order for that station to be able to enter an announcement session. To enter an  
announcement session, go off-hook on a station that has console permissions  
and enter the appropriate Feature Access Code (FAC), administered as  
Announcement access code on the FACs form. Dial tone should be returned at  
this point. Enter the extension of the announcement that needs to be recorded,  
deleted, or played back. Again, dial tone should be heard. To record an  
announcement, press station keypad digit 1, record after the tone, and hang up  
when done. To play back an announcement, press 2. To delete an  
announcement, press 3 (confirmation tone is given if the delete worked).  
Announcements can also be played back by simply calling the announcement  
extension associated with them.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-95  
Uploading/Downloading Announcements  
Integrated announcements on the TN750 Announcement circuit pack can be  
uploaded to the memory card with the administration terminal save  
announcements command. Likewise, integrated announcements can be  
downloaded to the Announcement circuit pack with the restore announcements  
command. Both of these commands require a free data module of NETCON type  
to be administered, a data module of announcement type (on the Announcement  
circuit pack) to be administered, and a memory card. These commands are  
useful in maintaining the customer’s recorded announcements. Depending on  
system traffic, announcement uploads and/or downloads take between 30 and  
45 minutes.  
The system automatically tries to download the Announcement circuit pack five  
minutes after it is inserted. This automatic download procedure is aborted if:  
1. An announcement is recorded within 10 minutes of circuit pack insertion.  
2. An announcement download is invoked sooner with the administration  
terminal restore announcements command.  
3. No announcement and/or NETCON data module is administered.  
4. Either the announcement data module is busy or all the administered  
NETCON data modules are busy.  
5. No memory card is in the system.  
6. The memory card in the system does not have a valid announcement file  
saved on it.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-36. Announcement Circuit Pack Error Log Entries  
Alarm Level (See  
Error  
Type  
Aux  
Data  
WARNING  
message below)  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
0
Any  
MINOR  
Any  
ON  
test board PCSS sh r 1  
1 (a)  
Circuit pack  
removed or SAKI  
Test (#53)  
2 (p)  
None  
14 (b)  
1 to 64  
Announcement  
Checksum Test  
(#209)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-96  
Table 3-36. Announcement Circuit Pack Error Log Entries — Continued  
Alarm Level (See  
Error  
Type  
Aux  
Data  
WARNING  
message below)  
On/Off  
Board  
Associated Test  
Test to Clear Value  
18  
0
0
busyout board  
PCSS  
WARNING  
OFF  
release board PCSS  
23 (c)  
125 (d)  
170 (e)  
217 (f)  
257  
None  
None  
None  
None  
WARNING  
MINOR  
OFF  
ON  
0
0
MINOR  
ON  
WARNING  
MINOR  
OFF  
ON  
65535  
Control Channel  
Test (#52)  
test board PCSS l r 20  
257 (g)  
267 (f)  
513 (h)  
1025 (i)  
Any  
0
None  
None  
None  
WARNING  
OFF  
Any  
4363  
NPE Audit Test  
(#50)  
test board PCSS l  
1281 (j)  
1538 (k)  
1793  
17699  
Any  
None  
None  
MINOR  
MINOR  
ON  
ON  
Angel-SP  
Handshake Test  
(#208)  
test board PCSS l r 3  
test board PCSS sh r 3  
17680  
17674  
In-line Error  
2049 (l)  
(m)  
Clock Match  
Inquiry Test (#212)  
MINOR  
ON  
In-line Error  
2305  
2561  
140AY Loop  
Around Test (#210)  
MINOR  
MINOR  
ON  
ON  
test board PCSS sh r 3  
test board PCSS sh r 3  
Super Frame  
Match Inquiry Test  
(#211)  
17676  
17682  
In-line Error  
2817 (l)  
Announcement  
Checksum Test  
(#209)  
MINOR  
ON  
test board PCSS sh r 3  
In-line Error  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-97  
Table 3-36. Announcement Circuit Pack Error Log Entries — Continued  
Alarm Level (See  
Error  
Type  
Aux  
Data  
WARNING  
message below)  
On/Off  
Board  
Associated Test  
Test to Clear Value  
17699  
(m)  
In-line Error  
3840 (n)  
3999 (o)  
Any  
Any  
None  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
!
WARNING:  
All alarms are upgraded to MAJOR when the BASE Tone Generator is set to  
12 (France).  
Notes:  
a. Error Type 1  
This error indicates the circuit pack totally stopped  
functioning or it was physically removed from the system.  
NOTE:  
The alarm is logged about 11 minutes after the circuit pack has been  
removed and/or SAKI Test (#53) fails.  
If the circuit pack is not in the system, insert a circuit pack (in the same  
slot as the error indicates) to resolve this error. Or, if the circuit pack is in  
the system and the red LED is on, follow the instructions for "Red (alarm)"  
in the "Control and Port Circuit Pack Status LEDs" section in Chapter 7,  
"LED Interpretation".  
NOTE:  
The alarm is logged about 11 minutes after the circuit pack has been  
removed and/or SAKI Test (#53) fails.  
!
WARNING:  
Reseating and/or replacing the circuit pack results in loss of  
integrated announcements (TN750/B only). See ‘‘General Notes’’  
near the beginning of this Maintenance procedure.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-98  
b. Error Type 14 Whenever the Announcement Checksum Test (#209)  
fails, this error is logged. The Aux Data indicates the number of the first  
defective announcement found. This number corresponds to the  
announcement numbers on the announcement form. The extension  
relating to the announcement can be determined by the display  
announcement command. This error only appears in the Error Log in  
conjunction with Error Type 2817. Follow the procedures for Error Type  
2817 to troubleshoot Error Type 14.  
c. Error Type 23 The circuit pack has been logically administered but not  
physically installed. The alarm is cleared when the circuit pack is installed.  
d. Error Type 125 A wrong circuit pack is inserted in the slot where this  
circuit pack is logically administered. To resolve this problem, either  
remove the wrong circuit pack and insert the logically administered circuit  
pack OR use the change circuit-pack command to readminister this slot  
to match the circuit pack inserted.  
e. Error Type 217 and 267  
Indicate that there is more than one TN750  
Announcement circuit pack inserted in the system. Remove the alarmed  
circuit pack.  
f. Error Type 257 This error indicates transient communication problems  
with this circuit pack. This error is not service-affecting and no action is  
required.  
g. Error Type 513 This error, when reported with Aux Data in the range of  
4352 to 4358, indicates the circuit pack has reported a hardware failure on  
the circuit pack. The circuit pack should be replaced.  
!
WARNING:  
Replacing the circuit pack results in loss of integrated  
announcements (TN750/B only). See ‘‘General Notes’’ near the  
beginning of this Maintenance procedure.  
h. Error Type 1025 This error is not service-affecting and no action is  
required.  
i. Error Type 1281 The SP found a fault in the speech main memory (SMM)  
(that is, it found one or more faulty memory locations). Whenever this error  
is logged, error 2817 is also logged [see Note (j)], which causes the  
maintenance system to run the Announcement Checksum Test (#209) to  
determine if the bad memory location was being used by an  
announcement.  
j. Error Type 1538 The hyperactive circuit pack is out-of-service and may  
exhibit one or more of the following symptoms:  
1. The tests run on the ports of this circuit pack are returning with a  
NO-BOARD.  
2. A busyout/release of the circuit pack has no effect on test results.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-99  
3. A list configuration command shows that the circuit pack and  
ports are properly installed.  
The system tries to restore the circuit pack within 15 minutes. If the error  
recurs after 15 minutes, replace the circuit pack. (Refer to Chapter 5,  
"Routine Maintenance Procedures".)  
k. Error Type 2049 and 2817 These errors are logged in conjunction with  
Error Type 1281, Aux Data 17699. Since that error [see Note (i)] means  
that a defective speech memory location was found, the announcement  
checksum error is also logged. This causes the Announcement Checksum  
Test (#209) to run, which determines if the defective memory location has  
corrupted any recorded announcements. If the Checksum Test passes,  
the faulty memory location is currently not being used, and the SP marks  
the location as faulty to ensure that future announcements do not attempt  
to use it.  
NOTE:  
As memory locations are marked faulty, the amount of available  
memory decreases, which decreases the total amount of  
announcement time available on the circuit pack.  
l. Error Type 2049 A transient error that does not cause an alarm can  
occasionally occur during a SPE, TDM BUS, or Tone Clock interchange. It  
is possible for a marginal Tone-Clock circuit pack to cause this error  
against the ANN-BD without alarming the TONE-BD. If this error occurs  
again, replacing the Tone-Clock circuit pack may clear up this error. See  
the FAIL case in the Clock Match Inquiry Test (#212).  
m. Error Type 3840 This error is not service-affecting and no action is  
required.  
n. Error type 3999 Indicates that the circuit pack sent a large number of  
control channel messages to the switch within a short period of time. If  
error type 1538 is also present, then the circuit pack was taken  
out-of-service due to hyperactivity. If error type 1538 is not present, then  
the circuit pack has not been taken out-of-service, but it has generated  
50% of the messages necessary to be considered hyperactive. This may  
be completely normal during heavy traffic periods. However, if this error  
type is logged when the circuit pack is being lightly used, it may indicate a  
problem with the circuit pack or the equipment attached to it.  
o. Error Type 2 Check the Class of Restriction (COR) administered for the  
Data Line extension assigned to the TN750 for uploading and  
downloading announcements. The extension can be found by using list  
data-module.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-100  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in Table 3-37 when inspecting  
errors in the system. By clearing error codes associated with the Control Channel  
Loop Around Test, for example, you may also clear errors generated from other  
tests in the testing sequence.  
Table 3-37. System Technician-Demanded Tests: ANN-BD  
Reset  
Short Test  
Sequence  
Long Test  
Sequence  
Board  
Sequence D/ND  
1
Order of Investigation  
Control Channel Loop Around Test (#52) (a)  
X
X
ND  
ND  
Angel-Speech Processor (SP) Handshake Test  
(#208)  
Clock Match Inquiry (#212)  
X
X
X
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
Super Frame Match Inquiry (#211)  
140AY Loop Around Test (#210)  
Announcement Checksum Test (#209)  
Network Processor Element (NPE) Audit Test  
(#50) (a)  
SAKI Test (#53) (a)  
X
D
Continued on next page  
1. D = Destructive, ND = Non-destructive  
Note:  
a. For a complete description of these tests, refer to the "XXX-BD (Common  
Port Circuit Pack)" Maintenance documentation.  
Angel-Speech Processor (SP) Handshake Test  
(#208)  
This test checks the integrity of the communication link between the two  
processors on the Announcement circuit pack.  
!
WARNING:  
Failure of this test indicates that the Speech Processor is insane and  
results in the loss of all integrated announcements on the circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-101  
Table 3-38. TEST #208 Angel-Speech Processor (SP) Handshake Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period. If Error Type 1538 is present in the Error Log, follow the  
maintenance strategy recommended for this Error Type.  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
Test failed. Circuit pack cannot be used. Announcement speech  
memory is cleared when this test fails. Therefore, when the problem  
has been resolved, announcements must be rerecorded or  
downloaded to the circuit pack.  
1. Reset the circuit pack via the reset board PCSS command and then  
run this test again. If the test continues to fail, replace the circuit pack  
and then run this test again.  
2. If there are recurring alarms on this circuit pack caused by this test  
failing, replace the circuit pack even if Step 1 works.  
!
WARNING:  
Replacing the circuit pack results in loss of integrated  
announcements. See ‘‘General Notes’’ near the beginning of this  
Maintenance documentation.  
PASS  
The communications link between the two processors on the  
Announcement circuit pack is functioning properly. User-reported troubles  
on this circuit pack should be investigated using other circuit pack and  
port tests. Refer to "ANN-PT (Announcement Port)" Maintenance  
documentation for a description of the port tests.  
Announcement Checksum Test (#209)  
Associated with every recorded announcement is a checksum. In this test, the  
SP checks a stored global checksum covering all recorded announcements  
against a calculated one and returns the results to the maintenance system. If the  
global checksum failed, maintenance requests the SP to check each individual  
announcement’s checksum.  
If the test fails, then it returns the total number of defective announcements  
found. In addition, associated with each failure is an error in the Error Log (Error  
Type 14). The Aux Data indicates the number of the first defective announcement  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-102  
found. This number corresponds to the announcement numbers on the  
announcement form. The extension relating to the announcement can be  
determined by the display announcement command.  
Table 3-39. TEST #209 Announcement Checksum Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
ABORT  
An error code of 0 indicates that the announcement file has been  
corrupted due to a hardware fault in the TN750 board. Follow step #7  
under ‘‘General Notes’’ at the beginning of this section.  
1023  
1024  
ABORT  
ABORT  
There are no announcements currently recorded on the circuit pack.  
This abort code is given for the following reasons:  
1. An announcement upload or download is in progress.  
2. An announcement upload or download is requested when this test is  
running.  
3. A record is in progress.  
4. A record request comes in when this test is running.  
If an announcement upload or download is in progress, a status  
data-module <announcement data extension> command should show  
that the announcement data port is connected to a NETCON data channel,  
and the "card-in-use" LED for the memory card is on (to determine the  
extension of the announcement data module, use the list data-module  
command).  
See Note (a) at end of table for more information.  
1. Wait until the blocking event is finished, and then run this test again.  
An upload or download could take up to 45 minutes to complete, and  
a recording session is finished as soon as the station that was making  
the recording is placed on-hook.  
2. If the test continues to abort, and a record or upload/download is not  
in progress, escalate the problem.  
2000  
2100  
ABORT  
Response to the test request was not received within the allowable time  
period. If Error Type 1538 is present in the Error Log, follow the  
maintenance strategy recommended for this Error Type.  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-103  
Table 3-39. TEST #209 Announcement Checksum Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0-256  
FAIL  
Test failed. The error code indicates the total number of defective  
announcements that were found.  
When TEST #209 fails with error code 0, the Global Checksum failed on  
the board, but no individual Checksum failed.  
NOTE:  
Since the announcements are recorded digitally, it is possible for the  
Announcement Checksum Test to fail but still have all the  
announcements sound uncorrupted. When an individual  
announcement fails the Checksum Test, always listen to the  
announcement first before taking any action (an announcement can  
be played back by dialing the announcement extension associated  
with the announcement number). If the announcement sounds  
corrupted, then rerecord it or delete it.  
1. Look in the Error Log to determine the number of the first defective  
announcement. Play back the announcement. If the announcement  
sounds defective, rerecord it or delete it. If the error code was greater  
than one (indicating that there is more than one defective  
announcement), run this test again and repeat this step.  
2. If after deleting and rerecording all defective announcements, the  
checksum test still fails, reset the circuit pack using the reset board  
PCSS command and run this test again.  
3. If the test still continues to fail, reseat the circuit pack and restore all  
announcements with an appropriate time estimate (for example, 40  
minutes.) Then rerecord the lost announcements (that is, those  
recorded since the last save operation) and run this test again.  
4. If the test still continues to fail, replace the circuit pack, and run this  
test again.  
!
WARNING:  
Replacing the circuit pack results in loss of integrated  
announcements. See ‘‘General Notes’’ near the beginning of this  
Maintenance procedure.  
PASS  
All recorded announcements checksum correctly, indicating that the  
speech main memory is functioning properly. User-reported troubles on  
this circuit pack should be investigated using other circuit pack and port  
tests. Refer to ‘‘ANN-PT (Announcement Port)’’ Maintenance  
documentation for a description of the port tests.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-104  
Notes:  
a. The Announcement circuit pack can exhibit a condition that does not allow  
recording.  
If the circuit pack gets locked into this state (this is an extremely rare  
condition), two of the Announcement Ports on the circuit pack will be  
unusable by software, one of which is the record port. Also, save/restore  
announcements will not work, since the record port looks busy to the  
circuit pack. Note that software does not have any way of knowing this,  
and attempts to use the ports.  
If the circuit pack is locked into this state, the following symptoms are  
observed:  
1. When attempting to record an announcement, users hear the  
proper record tone, but the announcement do not record (they do  
not know it until the announcement is played back).  
2. Performing a test board long when the circuit pack is in this state  
yield the following abort codes:  
■
■
■
Ports 1 AND 9 abort Test #206 with code 1024  
Ports 1 AND 9 abort Test #205 with code 2000  
Board level Tests #209 and #210 abort with code 1024  
3. The save/restore announcements command times out with:  
Error encountered, can’t complete request  
The Announcement circuit pack lock-up can be cleared remotely by  
performing a soft reset to the circuit pack:  
■
busyout board PCSS (this command drops all calls in progress on  
the Announcement circuit pack)  
■
■
reset circuit pack using the reset board PCSS command  
release circuit pack using the release board PCSS command  
140AY Loop Around Test (#210)  
This test checks the integrity of the record channel on the Announcement circuit  
pack (Announcement Port 1). The main function of the 140AY device is to accept  
Pulse Code Modulation (PCM)/Adaptive Differential Pulse Code Modulation  
(ADPCM) samples and compress/expand the samples using ADPCM. This test  
connects a Tone Generator to one port (Announcement Port 1, the recording  
port), and a Tone Detector to another port (Announcement Port 9). A tone is  
generated by the Tone Generator on the first port and looped through the 140AY  
device to the second port. The Tone Detector then responds with a tone  
present/absent message. The 140AY Loop Around Test is repeated at three  
different speech compression rates.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-105  
Since this test involves sending a tone through two different ports, the Playback  
Speech Memory Array (PSMA) Test (#206) is run on the two ports first to make  
sure that they are working properly. See ‘‘ANN-PT (Announcement Port)’’ for a  
description of this test.  
Table 3-40. TEST #210 140AY Loop Around Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1-3  
ABORT  
Response to the test request was not received within the allowable time  
period. The error code indicates at which speech compression rate the test  
aborted (one being the first rate tested, three being the last).  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The PSMA Test (#206) failed on Announcement Port 1.  
The PSMA Test (#206) failed on Announcement Port 9.  
10  
90  
ABORT  
ABORT  
1. Refer to ‘‘ANN-PT (Announcement Port)’’ Maintenance documentation,  
Test #206.  
1000  
ABORT  
System resources required to run this test are not available. This test needs  
Announcement Ports 1 and 9 to run. One of the ports may be in use on a  
valid call.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort and Ports 1 and 9 are not in use, escalate  
the problem.  
1002  
1003  
ABORT  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to ‘‘TDM-BUS (TDM Bus)’’ Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to the  
‘‘TTR-LEV (TTR Level)’’ Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to the  
‘‘TONE-PT (Tone Generator)’’ Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1007  
ABORT  
The Announcement circuit pack thinks that Port 1 or Port 9 is busy.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort, follow the Announcement Port  
maintenance procedures for Ports 1 and 9.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-106  
Table 3-40. TEST #210 140AY Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1024  
ABORT  
Announcement circuit pack blocked the test because an announcement  
download is in progress. If an announcement download is in progress, a  
status data-module <announcement data extension> command should  
show that the announcement data port is connected to a NETCON data  
channel, and the "card-in-use" LED for the memory card should be on (to  
determine the extension of the announcement data module, use the list  
data-module command). See Note (a) at end of table for more information.  
1. Wait until download is finished (can take up to 45 minutes), and then  
run the test again.  
2. If the test continues to abort and there is no download in progress,  
escalate the problem.  
2000  
2007  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period. If Error Type 1538 is present in the Error Log, follow the  
maintenance strategy recommended for this error type.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The Announcement circuit pack thinks that Port 1 or Port 9 is busy.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort, follow the Announcement Port  
maintenance procedures for Ports 1 and 9.  
2100  
1-3  
ABORT  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Test failed. The error code indicates at which speech compression rate the  
test actually failed (one being the first rate tested, three being the last).  
1. Reset the circuit pack via the reset board PCSS command and then  
run this test again. If the test still fails, replace the circuit pack (see  
Warning) and run this test again.  
2. If there are recurring alarms on this circuit pack caused by this test  
failing, replace the circuit pack even if Step 1 works (see Warning).  
!
WARNING:  
Replacing the circuit pack results in loss of integrated  
announcements. See ‘‘General Notes’’ near the beginning of this  
Maintenance procedure.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-107  
Table 3-40. TEST #210 140AY Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The record channel on the Announcement circuit pack is functioning  
properly. User-reported troubles on this circuit pack should be investigated  
using other circuit pack and port tests. Refer to ‘‘ANN-PT (Announcement  
Port)’’ Maintenance documentation for a description of the port tests.  
Notes:  
a. The Announcement circuit pack can exhibit a condition that does not allow  
recording.  
If the circuit pack gets locked into this state (this is an extremely rare  
condition), two of the Announcement Ports on the circuit pack will be  
unusable by software, one of which is the record port. Also, save/restore  
announcements will not work since the record port looks busy to the  
circuit pack. Note that software does not have any way of knowing this,  
and attempts to use the ports.  
If the circuit pack is locked into this state, the following symptoms are  
observed:  
1. When attempting to record an announcement, users hear the  
proper record tone, but the announcement does not record (they  
do not know it until the announcement is played back).  
2. Performing a test board long when the circuit pack is in this state  
yields the following abort codes:  
■
■
■
Ports 1 AND 9 abort Test #206 with code 1024  
Ports 1 AND 9 abort Test #205 with code 2000  
Board level Tests #209 and #210 abort with code 1024  
3. The save/restore announcements command times out with:  
Error encountered, can’t complete request  
The Announcement circuit pack lock-up can be cleared remotely by  
performing a soft reset to the circuit pack:  
■
busyout board PCSS (this command drops all calls in progress on  
the Announcement circuit pack)  
■
■
reset circuit pack using the reset board PCSS command  
release circuit pack using the release board PCSS command  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-108  
Super Frame Match Inquiry Test (#211)  
The super frame is a means by which the SP synchronizes with the 140AY device  
on the Announcement circuit pack. If the super frame is not synchronized, the SP  
is not able to properly process record/playback requests. Both the SP and the  
hardware generate a super frame pulse. When these two pulses are out of synch,  
the SP sets a flag to indicate the mismatch. When this test is run, the state of this  
flag is returned.  
Table 3-41. TEST #211 Super Frame Match Inquiry  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period. If Error Type 1538 is present in the Error Log, follow the  
maintenance strategy recommended for this Error Type.  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Test failed. Announcement playbacks should sound corrupted.  
FAIL  
1. Reset the circuit pack via the reset board PCSS command and then  
run this test again. If the test continues to fail, replace the circuit pack  
(see Warning).  
2. If there are recurring alarms on this circuit pack caused by this test  
failing, replace the circuit pack even if Step 1 works (see Warning).  
!
WARNING:  
Replacing the circuit pack results in loss of integrated  
announcements. See ‘‘General Notes’’near the beginning of this  
Maintenance procedure.  
PASS  
The SP can properly process record/playback requests. User-reported  
troubles on this circuit pack should be investigated using other circuit pack  
and port tests. Refer to ‘‘ANN-PT (Announcement Port)’’ Maintenance  
documentation for a description of the port tests.  
Clock Match Inquiry Test (#212)  
This test is supported to determine the state of the clock generation circuitry on  
the Announcement circuit pack. This circuitry is used for controlling various  
pieces of the hardware, like the 140AY device. It is also used to synchronize the  
Announcement circuit pack with the clock that is on the backplane.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-BD (Announcement Circuit Pack)  
3-109  
Table 3-42. TEST #212 Clock Match Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period. If Error Type 1538 is present in the Error Log, follow the  
maintenance strategy recommended for this Error Type.  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
Test failed. Announcements recorded or played back while the clock  
circuitry is not functioning properly sound distorted. The ANN-BD may be  
defective or the Active Tone-Clock circuit pack (TONE-BD) may be  
marginal and is causing this test to fail.  
1. Reset the circuit pack via the reset board PCSS command and then  
run this test again. If the test continues to fail, proceed to Step 2 or 3  
as applicable.  
!
WARNING:  
Replacing the circuit pack results in loss of integrated  
announcements. See ‘‘General Notes’’ near the beginning of this  
Maintenance procedure.  
FAIL  
(cont’d.)  
2. Replace the ANN-BD. Rerun the test. If the test continues to fail,  
replace the Tone-Clock circuit pack.  
!
WARNING:  
Replacing the TONE-BD causes a COLD 2 reset. See the "How to  
Replace a Tone-Clock Circuit Pack" section in the "TONE-BD  
(Tone-Clock Circuit Pack)" Maintenance documentation. Replacing  
the ANN-BD results in loss of integrated announcements. See  
‘‘General Notes’’ near the beginning of this Maintenance procedure.  
3. If there are recurring alarms on this circuit pack caused by this test  
failing, replace the ANN-BD even if the previous steps were  
successful.  
PASS  
Announcement record/playbacks should have clear sound quality.  
User-reported troubles on this circuit pack should be investigated using  
other circuit packs and port tests. Refer to "ANN-PT (Announcement Port)"  
Maintenance documentation for a description of the port tests.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-PT (Announcement Port)  
3-110  
ANN-PT (Announcement Port)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test port PCSSpp l  
Full Name of MO  
Announcement Port  
Announcement Port  
ANN-PT  
ANN-PT  
MINOR  
WRN  
test port PCSSpp l  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); and SS is the address of the slot in the carrier where the  
circuit pack is located (for example, 01, 02, ..., etc.).  
The TN750 Announcement circuit pack is a service circuit pack that provides an  
integrated means for recording announcements that can be played back on  
demand by call processing as part of a calling feature (that is, announcements  
on hunt group calls). There are 16 Announcement Ports on the Announcement  
circuit pack. Each port can play any integrated announcement, independently of  
the other ports. If there are any errors associated with the circuit pack, refer to  
"ANN-BD (Announcement Circuit Pack)" Maintenance documentation.  
The Announcement circuit pack has two processors on it. The first processor, or  
Angel, controls the circuit pack, and communicates with the switch via the control  
channel on the TDM Bus. The second processor, or SP, controls the speech  
memory and announcements. Digital speech is converted from its TDM Bus form  
to an internal storage form (for recording) and vice versa (for playbacks) by the  
140AY device on the circuit pack, which has 16 channels (one for each  
Announcement Port).  
General Notes  
Here are a few very important general notes that apply to any problem on the  
Announcement circuit pack. The user should read this before attempting to work  
on the TN750 Announcement circuit pack or Announcement Ports, especially if  
the circuit pack needs to be replaced.  
1. The TN750/B Announcement circuit pack retains all integrated  
announcements as long as the circuit pack has power. For this reason,  
whenever there is a problem with either the Announcement circuit pack or  
an Announcement Port that may require the circuit pack to be reset, it is  
always better to try to reset the circuit pack via the reset board PCSS  
command first and, if that does not work, then try to reseat it.  
Announcements are preserved through a software reset, but they are  
lost when the circuit pack is reseated.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-PT (Announcement Port)  
3-111  
2. If a customer has announcements on the Announcement circuit pack,  
then announcements must be saved on the system tape to ensure  
that they are not lost. This should be done as soon as the  
announcements are recorded on the circuit pack (or whenever they are  
changed), assuming that the pack is in proper working order (see Note).  
NOTE:  
Unlike translations, announcements are NEVER automatically saved  
to the memory card.  
3. The save announcements command replaces the announcement file on  
the card with the Announcement circuit pack speech memory. Care must  
be taken not to mistakenly enter this command, thereby destroying a valid  
file on tape.  
4. The restore announcements command replaces the Announcement  
circuit pack speech memory with the announcement file on the card. Care  
must be taken not to mistakenly enter this command, thereby destroying  
valid speech memory (especially if the card does not have a valid  
announcement file on it).  
5. Whenever the Announcement circuit pack is replaced, announcements  
must always be re-recorded or downloaded to the new circuit pack.  
Otherwise, call processing is not able to use the circuit pack.  
6. If announcement speech memory is corrupted, announcements should  
not be saved, that is, if the Announcement Checksum Test (#209) fails or  
if the speech sounds corrupted on playback. This can ruin a good  
announcement file and potentially cause errors/alarms on any circuit pack  
to which the new file is downloaded. However, if the customer does not  
have a valid announcement file, then announcements can be saved in an  
effort to try to retain some of them (all of the announcements recorded may  
not be corrupted).  
7. Although Announcement Port 5 and Data Line Circuit Port 17 on the  
Announcement circuit pack are logically two separate ports, they are  
physically the same port. Therefore, if one of the ports is in use, the other  
one will be busy. Also, if Announcement Port 5 is out-of-service, the Data  
Line Circuit Port is taken out-of-service. However, if the Data Line Circuit  
Port is out-of-service, the Announcement Port remains in-service.  
Announcement Administration  
A brief description of the integrated announcement administration is given here  
to aid in the troubleshooting of the Announcement circuit pack and its ports. In  
many cases, it is necessary to record, play back, and/or delete announcements  
to resolve an alarm. It may also be necessary to save and restore  
announcements as part of the maintenance procedures. For a complete  
description of integrated announcement administration, please refer to DEFINITY  
Enterprise Communications Server Administrator’s Guide.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-PT (Announcement Port)  
3-112  
Announcement Session  
Announcements can be recorded, played back, and deleted from an  
announcement session. A station’s COS needs to include console permissions in  
order for that station to be able to enter an announcement session. To enter an  
announcement session, go off-hook on a station that has console permissions  
and enter the appropriate FAC (administered as Announcement access code on  
the FACs form). Dial tone should be returned at this point. Enter the extension of  
the announcement that needs to be recorded, deleted or played back. Again,  
dial tone should be heard. To record an announcement, press station keypad  
digit 1, record after the tone, and hang up when done. To play back an  
announcement, press station keypad digit 2. To delete an announcement, press  
station keypad digit 3 (confirmation tone is given if the delete worked).  
Announcements can also be played back by simply calling the announcement  
extension associated with them.  
Uploading/Downloading Announcements  
Integrated announcements on the TN750 Announcement circuit pack can be  
uploaded to the memory card with the save announcements command.  
Similarly, integrated announcements can be downloaded to the Announcement  
circuit pack with the restore announcements command. Both of these  
commands require a free data module of NETCON type to be administered, a  
data module of announcement type (on the Announcement circuit pack) to be  
administered, and a memory card. These commands are useful in maintaining  
the customer’s recorded announcements. Depending on system traffic,  
announcement uploads/downloads take between 30 and 45 minutes.  
The system automatically tries to download the Announcement circuit pack five  
minutes after it is inserted. This automatic download procedure is aborted if:  
1. An announcement is recorded within 10 minutes of circuit pack insertion.  
2. An announcement download is invoked sooner with the administration  
terminal restore announcements command.  
3. There is no announcement and/or NETCON data module administered.  
4. Either the announcement data module is busy or all the administered  
NETCON data modules are busy.  
5. There is no memory card in the system.  
6. The memory card in the system does not have a valid announcement file  
saved on it.  
NOTE:  
Unlike translations, there is no provision in the system for automatically  
saving announcements to the memory card.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-PT (Announcement Port)  
3-113  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-43. Announcement Port Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
test port PCSSpp sh r 1  
test port PCSSpp sh r 3  
1
0
1
0
0
Any  
Any  
Playback Speech  
Memory Array  
(PSMA) Test (#206)  
MINOR  
ON  
18  
The port was  
busied out  
WARNING  
WARNING  
OFF  
ON  
release port PCSSpp  
test port PCSSpp sh  
130 (a)  
None  
Channel  
Administration  
Memory Array  
(CAMA) Test  
(#205)  
257  
MINOR  
MINOR  
ON  
ON  
test port PCSSpp l r 3  
test port PCSSpp sh r 3  
17667  
17684  
In-line error  
140AY Channel  
Sanity Inquiry Test  
(#222)  
513  
In-line error  
None  
769 (b)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
Notes:  
a. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
b. This error is logged and the port is alarmed when an alarm is raised on the  
Announcement circuit pack because of a faulty condition with a common  
circuit pack resource. Any one of the following alarmed errors on the  
Announcement circuit pack causes this error to be logged against the  
Announcement Port: 1793, 2049, 2305, 2561. Follow the ANN-BD  
(Announcement Circuit Pack) Maintenance documentation to resolve  
these alarms. When the corresponding circuit pack alarm is cleared, this  
alarm clears.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-PT (Announcement Port)  
3-114  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Channel Administration Memory Array (CAMA) Test, for example, you may also  
clear errors generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
ND  
Channel Administration Memory Array (CAMA) Test (#205)  
Playback Speech Memory Array (PSMA) Test (#206)  
140AY Channel Sanity Inquiry Test (#222)  
X
X
X
X
X
ND  
ND  
1. D = Destructive; ND = Nondestructive  
Channel Administration Memory Array (CAMA)  
Test (#205)  
This test is a memory device that stores information used to control the 140AY  
device. The Angel asynchronously feeds the CAMA with the control information.  
During the CAMA test, the Angel writes patterns into the CAMA, reads them  
back, and verifies that they match. If the patterns do not match, the test fails. This  
test is run periodically by the switch maintenance and by the Announcement  
circuit pack in the background.  
Table 3-44. TEST #205 Channel Administration Memory Array (CAMA) Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be in use on a valid call.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
2100  
ABORT  
Response to the test request was not received within the allowable time  
period. See Note (a) at end of table for more information.  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-PT (Announcement Port)  
3-115  
Table 3-44. TEST #205 Channel Administration Memory Array (CAMA) Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
Test failed. Announcements played back on this port may sound  
corrupted.  
1. Reset the circuit pack via the reset board PCSS command and then  
run this test again. If the test continues to fail, replace the circuit pack  
(see Warning).  
2. If there are recurring alarms on this port caused by this test failing,  
replace the circuit pack even if Step 1 works (see Warning).  
!
WARNING:  
Replacing the circuit pack results in loss of integrated  
announcements. Refer to "‘‘General Notes’’near the beginning of this  
Maintenance procedure.  
PASS  
This test verifies that the Angel processor can properly set up this port for  
playbacks. User-reported troubles on this circuit pack should be  
investigated using other port and circuit pack tests. (Refer to "ANN-BD  
(Announcement Circuit Pack)" Maintenance documentation for a  
description of the circuit pack tests.)  
Notes:  
a. The Announcement circuit pack can exhibit a condition that does not allow  
recording.  
If the circuit pack gets locked into this state (this is an extremely rare  
condition), two of the Announcement Ports on the circuit pack (one of  
which is the record port) will be unusable by software. Also, save/restore  
announcements will not work since the record port looks busy to the  
circuit pack. Note that software does not have any way of knowing this and  
attempts to use the ports.  
If the circuit pack is locked into this state, the following symptoms are  
observed:  
1. When attempting to record an announcement, users hear the  
proper record tone, but the announcement does not record (they  
do not know it until the announcement is played back).  
2. Performing a test board long when the circuit pack is in this state  
yields the following abort codes:  
■
Ports 1 AND 9 abort Test #206 with code 1024  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-PT (Announcement Port)  
3-116  
■
■
Ports 1 AND 9 abort Test #205 with code 2000  
Board level Tests #209 and #210 abort with code 1024  
3. The save/restore announcements command times out with:  
Error encountered, can’t complete request  
The Announcement circuit pack lock-up can be cleared remotely by  
performing a soft reset to the circuit pack:  
■
busyout board PCSS (this command drops all calls in progress on  
the Announcement circuit pack)  
■
■
reset circuit pack using the reset board PCSS command  
release circuit pack using the release board PCSS command  
Playback Speech Memory Array (PSMA) Test  
(#206)  
The PSMA test checks the integrity of a playback channel’s interface to the  
speech memory and the TDM Bus. The SP has an internal buffer that contains a  
specific 256-byte sequence. During this test, the byte sequence is "played"  
through the 140AY device onto the TDM Bus. A General Purpose Tone Detector is  
used to confirm that the proper sequence was played. This test is very  
important. It is the only test that actually checks an Announcement Port’s ability  
to play back an announcement on the TDM Bus. If the test fails, the Tone  
Detector returns the number of bytes that did not match the expected sequence.  
The larger the number, the more severe the problem with that port. If this test  
fails, announcements played over this port should sound corrupted.  
It is the only test that actually checks an Announcement Port’s ability to play back  
an announcement on the TDM Bus. If the test fails, the Tone Detector returns the  
number of bytes that did not match the expected sequence. The larger the  
number, the more severe the problem with that port. If this test fails,  
announcements played over this port should sound corrupted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-PT (Announcement Port)  
3-117  
Table 3-45. TEST #206 Playback Speech Memory Array (PSMA) Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be in use on a valid call.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
1003  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to "TDM-BUS (TDM Bus)" Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat the test at 1-minute intervals a maximum of 5 times.  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to "TTR-LEV  
(TTR Level)" Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to "TONE-PT  
(Tone Generator)" Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1024  
ABORT  
Announcement circuit pack blocked the test because an announcement  
download is in progress. If an announcement download is in progress, a  
status data-module <announcement data extension> command should  
show that the announcement data port is connected to a NETCON data  
channel, and the memory card should be active. (To determine the  
extension of the announcement data module, use the list data-module  
command.)  
See Note (a) at end of table for more information.  
1. Wait until download is finished (could take a maximum of 45 minutes),  
and then run the test again.  
2. If the test continues to abort and there is no download in progress,  
escalate the problem.  
2000  
2100  
ABORT  
Response to the test request was not received within the allowable time  
period.  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-PT (Announcement Port)  
3-118  
Table 3-45. TEST #206 Playback Speech Memory Array (PSMA) Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1 to 254  
FAIL  
Test failed. The error code indicates the number of byte count errors found  
by the Tone Detector.  
1. Reset the circuit pack via the reset board PCSS command and then  
run this test again. If the test continues to fail, replace the circuit pack  
(see Warning).  
2. If there are recurring alarms on this port caused by this test failing,  
replace the circuit pack even if Step 1 works (see Warning).  
!
WARNING:  
Replacing the circuit pack results in loss of integrated  
announcements. Refer to ‘‘General Notes’’ near the beginning of this  
Maintenance procedure.  
255  
FAIL  
Test failed. The Announcement Port and the Tone Detector never  
synchronized. Check for active GPTD-PT errors, and refer to "GPTD-PT  
[General Purpose Tone Detector Port (CPTR)]" Maintenance  
documentation to diagnose them first.  
1. If there are no active GPTD-PT errors, reset the circuit pack via the  
reset board PCSS command and then run this test again. If the test  
continues to fail, replace the circuit pack (see Warning).  
2. If there are recurring alarms on this port caused by this test failing,  
replace the circuit pack even if Step 1 works (see Warning).  
!
WARNING:  
Replacing the circuit pack results in loss of integrated  
announcements. Refer to ‘‘General Notes’’near the beginning of this  
Maintenance procedure.  
PASS  
This port can cleanly play announcements. User-reported troubles on this  
pack should be investigated using other port and circuit pack tests. Refer  
to ‘‘ANN-BD (Announcement Circuit Pack)’’ Maintenance documentation  
for a description of the circuit pack tests.  
Notes:  
a. The Announcement circuit pack can exhibit a condition that does not allow  
recording.  
If the circuit pack gets locked into this state (this is an extremely rare  
condition), two of the Announcement Ports on the circuit pack (one of  
which is the record port) will be unusable by software. Also, save/restore  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-PT (Announcement Port)  
3-119  
announcements will not work, since the record port looks busy to the  
circuit pack. Note that software does not have any way of knowing this and  
attempts to use the ports.  
If the circuit pack is locked into this state, the following symptoms are  
observed:  
1. When attempting to record an announcement, users hear the  
proper record tone, but the announcement does not record (they  
do not know it until the announcement is played back).  
2. Performing a test board long when the circuit pack is in this state  
yields the following abort codes:  
■
■
■
Ports 1 and 9 abort Test #206 with code 1024  
Ports 1 and 9 abort Test #205 with code 2000  
Board level Tests #209 and #210 abort with code 1024  
3. The save/restore announcements command times out with:  
Error encountered, can’t complete request  
The Announcement circuit pack lock-up can be cleared remotely by  
performing a soft reset to the circuit pack:  
■
busyout board PCSS (this command drops all calls in progress on  
the Announcement circuit pack)  
■
■
reset circuit pack using the reset board PCSS command  
release circuit pack using the release board PCSS command  
140AY Channel Sanity Inquiry Test (#222)  
The Angel keeps a sanity status bit for each of the 16 channels on the 140AY  
device. This test queries the Angel to determine the status for a particular  
channel. If a channel is insane, that implies that announcements cannot be  
played back on that channel.  
Table 3-46. TEST #222 140AY Channel Sanity Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANN-PT (Announcement Port)  
3-120  
Table 3-46. TEST #222 140AY Channel Sanity Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
Test failed. Announcements cannot be played back over this port.  
1. Reset the circuit pack via the reset board PCSS command and then  
run this test again. If the test continues to fail, replace the circuit pack  
(see Warning).  
2. If there are recurring alarms on this port caused by this test failing,  
replace the circuit pack even if Step 1 works (see Warning).  
!
WARNING:  
Replacing the circuit pack results in loss of integrated  
announcements. Refer to ‘‘General Notes’’ near the beginning of this  
Maintenance procedure.  
PASS  
Announcements can be played back over this port. User-reported troubles  
on this pack should be investigated using other port and circuit pack tests.  
Refer to the ‘‘ANN-BD (Announcement Circuit Pack)’’ Maintenance  
documentation for a description of the circuit pack tests.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANNOUNCE (Announce)  
3-121  
ANNOUNCE (Announce)  
MO Name (in  
Alarm Log)  
Initial Command to  
Run  
Alarm Level  
none  
Full Name of MO  
ANNOUNCE  
none  
ANNOUNCEMENT  
The ANNOUNCE MO logs an error in the hardware error log if at least one of the  
following is true:  
■
The save announcements or restore announcements command does  
not complete successfully, or the  
■
System fails to restore announcements from the memory card at boot time.  
Figure 3-2 shows the connection of the Announcement Circuit Pack to the  
system. To save or restore announcements, an ANNOUNCEMENT Data  
Extension must be administered, and at least one DATA-CHL (Network Control  
Data Channel) must be in the in-service/idle state.  
TN798 Processor  
Switch Software Applications  
PR-MAINT  
Data-CHL  
Software  
Data-CHL  
Software  
Data-CHL  
Software  
Data-CHL  
Software  
Network Control  
CARD-MEM  
DATA  
CHL1  
DATA  
CHL2  
DATA  
CHL3  
DATA  
CHL4  
TDM bus  
Announcement  
Circuit Pack  
cydmacps RPY 062397  
Figure 3-2. Connection of announcement circuit pack to the system  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANNOUNCE (Announce)  
3-122  
Hardware Error Log Entries  
Table 3-47. ANNOUNCE Error Log Entries  
Associated  
Alarm  
Level  
On/Off  
Board  
Error Type  
Aux Data  
Test  
Test to Clear Value  
1(a)(d)  
any  
any  
0
None  
257(d)  
None  
None  
None  
None  
513(b)(d)  
769(d)  
0
1025(d)  
any  
Notes:  
a. Error occurred while saving announcements. (See Table 3-48 in the next  
section for an explanation of Aux Data and for recommended repair  
actions.)  
b. User pressed cancel while announcements were being saved.  
c. Error occurred while restoring announcements. (See Table 3-48 in the next  
section for an explanation of Aux Data and for recommended repair  
actions.)  
d. The port field for this error contained the active PE complex when the error  
occurred.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANNOUNCE (Announce)  
3-123  
Aux Data Error Codes and Recommended Repair  
Procedures  
Table 3-48. Aux Data Error Codes and Recommended Repair Procedures  
Aux  
Data  
Description/ Recommendation  
9000  
CARD-MEM errors  
through  
9031  
Check and resolve CARD-MEM errors and alarms.  
32001  
Internal system error.  
1. Check other ANNOUNCE errors and take corrective action. If there are no other  
ANNOUNCE errors, do the following:  
2. Retry the command at 2-minute intervals a maximum of 3 times.  
3. If the save/restore announcements command fails, escalate the problem.  
Announcement circuit pack is in use.  
32002  
32003  
1. Retry the command at 2-minute intervals a maximum of three times.  
2. If the save/restore announcements command fails, escalate the problem.  
Announcement port is in use.  
1. Wait for all Announcement ports to become available.  
2. Enter the save/restore announcements command.  
32004  
32005  
There are no announcements recorded on the Announcement Circuit Pack. The save  
announcements command is not allowed to prevent the destroying of the  
announcement file on tape [286 systems] or on the memory card [386 systems].  
Integrated announcement circuit pack is not present. The Announcement Circuit Pack  
is not inserted, or it is defective.  
1. Enter the list config command to check for the presence of the circuit pack in the  
system.  
2. If the Announcement Circuit Pack is present, use the test board PCSS command  
to check the status of the Announcement Circuit Pack.  
32006  
32007  
32008  
Announcement Data Module not available.  
1. Use the status command to check the status of the Announcement Data Module.  
Announcement Data Module out of service.  
1. Use the status command to check the status of the Announcement Data Module.  
Announcement data is being saved or loaded.  
1. Retry the command at 2-minute intervals a maximum of three times.  
2. If the save/restore announcements command fails, escalate the problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ANNOUNCE (Announce)  
3-124  
Table 3-48. Aux Data Error Codes and Recommended Repair Procedures — Continued  
Aux  
Data  
Description/ Recommendation  
32009  
Required DATA-CHL is not administered or out of service. (A DATA-CHL is required to  
save or restore announcements.)  
1. Add a DATA-CHL if none is administered.  
2. If a DATA-CHL is administered, use the status command to check the status of all  
DATA-CHLs. At least one DATA-CHL should be in the in-service/idle state.  
32010  
32013  
DATA-CHL is not administered, or it is unavailable. (A DATA-CHL is required to save or  
restore announcements.)  
1. Add a DATA-CHL if none is administered.  
2. If a DATA-CHL is administered, use the status command to check the status of all  
DATA-CHLs. At least one DATA-CHL should be in the in-service/idle state.  
32012  
32015  
32016  
Required Announcement Data Module is not administered.  
1. Add an Announcement Data Module and repeat the command.  
Time of day not set.  
1. Set the time of day, and reenter the save/restore announcements command.  
Internal system errors.  
Check for any other ANNOUNCE errors and take corrective action.If there are no other  
announcements errors, do the following:  
1. Retry the command at 2-minute intervals a maximum of three times.  
2. If the save/restore announcements command fails, escalate the problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-125  
ATM-BCH (ATM B-Channel Trunk)  
MO Name (in  
Alarm Log)  
Initial Command to  
1
Alarm Level  
Run  
Full Name of MO  
2
3
ATM-BCH  
MAJOR  
test port UUCSSppp l  
test port UUCSSppp l  
test port UUCSSppp sh  
ATM B-Channel Trunk  
ATM B-Channel Trunk  
ATM B-Channel Trunk  
ATM-BCH  
ATM-BCH  
MINOR  
WARNING  
1. UU is the universal cabinet number (1 for PPN, 2-44 for EPNs). C is the carrier designation (A, B,  
C, D, or E). SS is the number of the slot where the circuit pack resides (01-21). ppp is the 3-digit  
port number (9-256).  
2. For additional repair information, see also ‘‘ATM-DCH (ATM D-Channel Port)’’, ‘‘ATM-SGRP (ATM  
Signaling Group)’’ and PKT-BUS.  
3. A MAJOR alarm on a trunk means that alarms on these trunks are not downgraded by the set  
options command, and at least 75% of the trunks in this trunk group are alarmed.  
This maintenance object explains how you test and repair TN230x ATM Interface  
circuit packs (TN2305 and TN2306) that have been administered as ATM  
B-channel trunks for ATM Circuit Emulation Service (CES).  
For maintenance instructions for TN230x circuit packs that are administered as  
Expansion Interfaces for ATM network connectivity, see the ATM-EI (Expansion  
Interface Circuit Pack) maintenance object.  
ATM Circuit Emulation Service  
Under ATM Circuit Emulation Service, you simulate ISDN-PRI circuits by  
assigning ATM ports to signaling groups. Each signaling group represents a PRI  
circuit, and the ports in the group represent the D-channel and B-channels of that  
circuit. TN230x circuit packs support up to 248 ports per circuit pack.  
Signaling group components  
Bearer (B) channels (ATM-BCH) transmit digitized voice or data, while a separate  
D-channel (ATM-DCH) handles call-control signaling. One D-channel handles  
signaling for a group of B-channels that combine to form a signaling group  
(ATM-SGRP).  
B-channel service states  
The ISDN specification defines 2 service state categories for B-channels as  
listed in Table 3-49.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-126  
Table 3-49. ATM ISDN service states  
Category  
Description  
Service states  
Active  
Idle  
A call is connected over  
the B-channel.  
B-channel is in normal  
operating state  
In-Service (INS)  
There is no call on the  
B-channel.  
Out-of-Service/Far-en  
d (OOS/FE)  
The switch has not successfully negotiated B-channel connection as of  
yet. Calls cannot be placed or received.  
When you first administer a B-channel, the switch initializes the B-channel  
to this state while it tries to negotiate a connection to the far end. If the  
request times out with no response from the far end, the switch leaves the  
B-channel in the OOS/FE state.  
Out-of-Service/Near-E The NPE Crosstalk Test has failed or the trunk is busied out. Calls cannot  
nd (OOS/NE)  
be placed or received.  
Maintenance/Far-End  
(MTC/FE)  
A request has timed out with no response from the far end after signaling  
is in place and B-channels are in service. Calls can be received but not  
placed, and stable calls are unaffected.  
Maintenance/Near-En  
d (MTC/NE)  
The signaling channel (ISDN-LNK) has been busied out, possibly after a  
test trunk grp#/mbr# long command. Calls cannot be placed or  
received, but stable calls are unaffected.  
1
Pending states  
Pending-in-Service  
The near-end is waiting for a response to a transition-to-service request.  
Pending-Maintenance The near-end is waiting for a transition-to-maintenance-service request  
(US and other country-protocol-1 systems).  
1. The switch is waiting for a reply from the far-end. Pending service states remain in effect until the  
near end receives a response or times out.  
B-channel alarms  
The Maintenance/Far-End and Out-Of-Service/Far-End states generate warning  
alarms displayed with status trunk grp#/mbr#.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-127  
Table 3-50. ATM-BCH alarms by service state  
1
Service state  
Alarm  
Possible cause  
Possible solution  
Warning  
Trunk busied out  
Release the port (release trunk  
grp#/mbr#).  
Minor  
None  
NPECrosstalk Test (#6)  
failed  
Replace ATM circuit pack.  
Out-of-Service/NE  
ATM circuit pack lost  
signal or there is a  
circuit pack problem.  
Install circuit pack or cable. Check  
circuit pack using procedures in  
ATM-BCH. Check far-end switch  
status.  
Warning  
Warning  
Unadministered far-end Administer the corresponding trunk  
on the far-end switch.  
Out-of-Service/FE  
Far-end busied out  
Check the status of the far-end  
switch.  
Pending/In-Service None  
Pending/Maint  
Maintenance message  
timed out waiting for  
reply  
Wait 2 minutes after the pending  
state clears, and check the service  
state.  
None  
ISDN test call in  
progress (test trunk  
long)  
Wait for the test to finish and  
recheck.  
Maint/NE  
None  
System link busied out  
Check link status. Run release link  
link#.  
Warning  
Signaling channel  
See ATM-SGRP or ATM-DCH.  
down for over 90 sec.  
Warning  
Repeated lack of  
response to messages  
sent to the far end  
Wait. Maintenance software resends  
messages periodically. Or run test  
trunk grp#/mb# or test  
Maint/FE  
signaling-grp grp#.  
Warning  
None  
The far-end trunk is  
being tested.  
Check status of the far-end switch.  
Wait for testing to finish.  
In-Service  
Normal operating state  
1. ATM-BCH alarms; alarms against other maintenance objects may also be present.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-128  
Error Log Entries and Test to Clear Values  
Table 3-51. ATM-BCH Error Log entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
test port UUCSSppp  
test port UUCSSppp  
release trunk grp/mbr  
test port UUCSSppp  
test port UUCSSppp  
test port UUCSSppp  
1(a)  
Any  
0
None  
18  
busyout trunk grp/mbr  
None  
129 (b)  
130 (c)  
257(d)  
WNG  
OFF  
Any  
Service State Audit (Test  
#256)  
513(e)  
769(f)  
Any  
Any  
None  
WNG  
WNG  
OFF  
OFF  
test port UUCSSppp  
test port UUCSSppp  
Service State Audit (Test  
#256)  
1793(g)  
3073(h)  
3585(i)  
3841(j)  
Any  
Any  
Any  
Any  
None  
test port UUCSSppp  
test port UUCSSppp  
none  
Service State Audit (#256)  
None  
None  
none  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. Error Type 1: the two ends of the ATM trunk do not agree on the ISDN call  
state. Possible causes:  
■
■
■
■
Received a DISConnect or RELease COMplete message with  
cause value 52 (outgoing calls barred)  
Received a DISConnect or RELease COMplete message with  
cause value 54 (incoming calls barred)  
Outgoing call renegotiated by the far end to another B-channel in  
the absence of SETUP message glare  
Near end attempted a call on a B-channel that the far end has  
marked OOS  
When running the Short Test Sequence, pay close attention to the results  
of the Call State Audit Test (#257).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-129  
b. Error Type 129: the far-end switch changed its ISDN service state to either  
out-of-service or maintenance. This may be a temporary condition  
because the far-end is testing that trunk or a hardware problem with the  
trunk. Outgoing calls may not be allowed over that trunk.  
1. Investigate the trunk status (status trunk grp#/mbr#).  
c. Error Type 130: the circuit pack has been removed or has been insane for  
more than 11 minutes.  
1. Reinsert or replace the circuit pack to clear the error.  
d. Error Type 257: SETUP received for a B-channel that is in an invalid  
service state. Service states may be incompatible at the two ends of the  
trunk. A normal call was received while the B-channel was MTC/FE,  
MTC/NE, OOS/FE, or OOS/NE or a test call was received while the  
B-channel was OOS/FE or OOS/NE.  
e. Error Type 513: RELease COMplete message received with cause value  
82 (nonexistent channel). The B-channel may not be administered at the  
far end. The trunk has been placed in the OOS/FE state.  
f. Error Type 769: inconsistent SERVice or SERVice ACKnowledge  
message. Possible causes:  
■
SERVice or SERVice ACKnowledge message received containing a  
change status that is more available than the previously-transmitted  
SERVice message.  
■
Unsolicited SERVice ACKnowledge message received containing a  
change status that does not match the current B-channel state.  
ISDN-PRI service-state negotiation rules have been violated and may  
indicate that a pending service-state audit is failing. The system  
■
■
■
cancels the maintenance timer  
increments the Service State Audit counter  
attempts a Service State Audit  
When running the Short Test Sequence, pay close attention to the results  
of the Service State Audit Test (#256).  
g. Error Type 1793: TN230x circuit pack has failed. The maintenance system  
■
places the trunk in the OOS/NE state  
■
sends a SERvice message to the far-end (if possible) containing a  
change status of OOS for the B-channel  
■
returns the trunk to service when the ATM trunk circuit pack reports  
the failure cleared  
h. Error Type 3073: Service State Audit attempt failed (see Test #256). Calls  
can be received but not placed until the test passes and the trunk state  
returns to In-Service.  
1. Check the trunk status (status trunk grp#/mbr#).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-130  
i. Error Type 3585: ISDN RESTART message received. Active calls have  
been dropped.  
The following Aux Data values (Error Type 3585 only) below represent the  
trunk’s ISDN call state at the time Error 3585 occurred. This information  
can be useful if users report dropped calls on the ISDN-PRI trunks.  
Aux  
Data  
Description  
An idle trunk received a restart.  
0
10  
An ISDN RESTART from the far-end has unexpectedly cleared a  
call in the ACTIVE state (call stable, parties talking).  
4
7
8
An ISDN RESTART from the far-end has unexpectedly cleared a  
RINGING call.  
260 263  
1
3
An ISDN RESTART from the far-end has unexpectedly cleared a  
call before the call entered the RINGING state.  
6
9
265  
11  
12  
An ISDN RESTART from the far-end has unexpectedly cleared a  
call that was already in the process of clearing.  
19  
If this condition occurs frequently, the far-end may be trying to  
clear trunks that appear to be in the “hung” state.  
531 267 268  
j. Error Type 3841: the far-end rejected an ATM CES trunk selected by the  
near-end 10 times. The ATM CES trunk may not be administered on the  
far-end.  
1. Get the physical name of the ATM trunk by noting the decimal  
number in the Aux Datafield.  
2. Check administration for the named trunk on the far-end.  
3. If problems persist, then busyout the ATM trunk to take it out of the  
hunt group.  
The WARNING alarm retires automatically whenever a called endpoint  
answers an outgoing or incoming call that uses the alarmed trunk.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-131  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate problems in the order presented in the table below. When you  
clear one of the error codes associated with a given test, you clear errors  
generated by other tests in the testing sequence. If you clear errors out of order,  
you can lose important information.  
Table 3-52. System Technician-Demanded Tests: ATM-BCH  
Short Test  
Sequence  
Long Test  
Sequence  
Destructive or  
Non-destructive  
Order of Investigation  
Signaling Link State Check Test (#255)  
Service State Audit Test (#256)  
Call State Audit Test (#257)  
X
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ISDN Test Call Test (#258)  
Signaling Link State Audit Test (#255)  
This non-destructive test checks the status of the TN230x ATM-CES Interface  
circuit pack and the ATM D-channel (ATM-DCH) trunk, which are both important  
elements to the health of the ATM-BCH trunk.  
Table 3-53. TEST #255 Signaling Link State Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
None  
0
ABORT  
ABORT  
ABORT  
Internal system error  
1114  
Signaling link in transitional state  
1. Retry the command up to 5 times at 1-minute intervals.  
Maintenance disabled  
1018  
ABORT  
1. Enable maintenance. Enter y in the Maintenance Tests?field on  
page 2 of the change trunk-group form.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-132  
Table 3-53. TEST #255 Signaling Link State Audit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Signaling channel problem  
4
FAIL  
1. Look for errors or alarms against the ‘‘ATM-SGRP (ATM Signaling  
Group)’’ and ‘‘ATM-DCH (ATM D-Channel Port)’’ maintenance objects.  
8
FAIL  
TN230x circuit pack failed  
1. See the ‘‘ATM-INTF (TN2305/6)’’ maintenance object.  
Signaling link OK.  
PASS  
Service State Audit (#256)  
This test checks the service state of the trunk.  
Country protocol 1. If the interface uses country protocol 1 (includes USA), the  
service-state audit executes in all trunk service states. It queries the service state  
on the far end and waits 2 minutes for a reply. If the first request times out, the  
service-state audit asks again. If the request times out again, it logs error 3073  
and resends the request every 15 minutes. It places in-service trunks in the  
MAINTENANCE/FAR-END state (outgoing calls blocked, incoming calls  
accepted). Incoming calls trigger an immediate service-state audit without  
waiting for the end of a 15-minute cycle.  
Any other country protocol. If the interface uses some other country protocol,  
the service-state audit executes only on trunks that are in the  
OUT-OF-SERVICE/FAR-END state. It asks the far-end switch to bring the trunk  
back into the IN-SERVICE state and waits 2 minutes for a reply. If the first request  
times out, the service-state audit asks again. If the request times out again, it  
leaves the trunk in the OUT-OF-SERVICE/FAR-END state and tries again in 1 hour.  
NOTE:  
PASS for this test only means that a message to the far-end was  
successfully sent.  
To check the service state of the ATM-BCH trunk, run status trunk grp#/mbr#.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-133  
Table 3-54. TEST #256 Service State Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Needed resources not available, port on a call or initializing  
1. Run status trunk grp#/mbr#.  
1000  
ABORT  
1. Check the results of Test #255.  
1018  
1113  
ABORT  
ABORT  
Maintenance disabled  
1. Enable maintenance by entering y in the Maintenance Tests?field  
on page 2 of the change trunk-group form.  
Signaling link failed  
1. Run status trunk grp#/mbr#.  
2. Check the results of Test #255.  
3. See the ‘‘ATM-SGRP (ATM Signaling Group)’’ maintenance object.  
Signaling link in transitional state  
1114  
ABORT  
1. Retry the command up to 5 times at 1-minute intervals.  
Trunk not in Out-of-Service/Far-end state and country protocol other than 1  
Service-state audit message outstanding  
1. Wait 2 minutes, then try again.  
1116  
1117  
ABORT  
ABORT  
2100  
1113  
ABORT  
FAIL  
Could not allocate needed resources  
1. Retry the command up to 5 times at 1-minute intervals.  
Signaling link failed  
1. See the ‘‘ATM-SGRP (ATM Signaling Group)’’ and ISDN-LNK (ISDN  
Signaling Link Port) maintenance objects.  
FAIL  
Internal system error  
1. Retry the command up to 5 times at 1-minute intervals.  
1. Wait 4 minutes, then check the Error Log for any new Error Type 3073.  
PASS  
■
If there are none, both sides of the ISDN connection agree on the  
service state. The negotiation succeeded.  
■
If there is a new 3073 error, then the negotiation failed (the request  
timed out).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-134  
Call State Audit Test (#257)  
This test audits the internal call state by asking the far-end switch for the ISDN  
call state. The test is particularly useful when you are trying to clear a hung call. If  
the internal call state on the near-end differs from that on the far-end, the call is  
torn down.  
The ISDN specification allows up to 2 minutes for a reply. If a reply is not received  
within the 2 minute window, the test logs a protocol time-out violation against the  
associated signaling channel (ATM-DCH, Error Type 1).  
NOTE:  
PASS simply means that an appropriate message was composed and sent  
to the far-end switch.  
Table 3-55. TEST #257 Call State Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1018  
ABORT  
Maintenance disabled  
1. Enable maintenance by entering y in the Maintenance Tests?field on  
page 2 of the change trunk-group form.  
1019  
1113  
1114  
1116  
2100  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
FAIL  
Audit already in progress  
1. Wait 2 minutes, and try again.  
Signaling link failed  
1. Check the results of Test #255 (Signaling Link State Check).  
Signaling link in transitional state  
1. Retry the command up to 5 times at 1-minute intervals.  
Trunk out-of-service  
1. Check the trunk service state (status trunk grp#/mbr#).  
Could not allocate needed resources  
1. Retry the command up to 5 times at 1-minute intervals.  
Internal system error  
1. Retry the command up to 5 times at 1-minute intervals.  
PASS  
1. Wait 4 minutes, then check the Error Log for call-state mismatches. If a  
call state mismatch is found, the call is torn down.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-135  
ISDN Test Call Test (#258)  
This non-destructive test performs a far-end looparound test over an ATM-BCH  
trunk if  
■
the trunk is IN-SERVICE, MAINTENANCE/NEAR-END, or  
OUT-OF-SERVICE/NEAR-END  
■
■
no calls are active on the trunk  
the system uses country protocol 1 (including US) or the far-end has  
looparound capability  
The test sets up a call to a far-end switch over the ATM-BCH trunk. Then the  
digital port on a TN711D Maintenance/Test circuit pack sends a bit pattern to the  
far-end and back. If the received pattern matches that sent, the test passes. If  
there are differences, it fails.  
Synchronous Test Calls  
You can initiate a synchronous outgoing test call (including a test call for  
ISDN-PRI trunks) with these commands:  
■
■
■
test trunk grp#/mbr# long [repeat #]  
test board UUCSS long [repeat #]  
test port UUCSSpp long [repeat #]  
Table 3-56. TEST #258 ISDN Test Call  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Signaling channel problem  
4
ABORT  
1. Look for errors or alarms against the ‘‘ATM-SGRP (ATM Signaling  
Group)’’ and ‘‘ATM-DCH (ATM D-Channel Port)’’ maintenance objects.  
8
ABORT  
ABORT  
TN230x circuit-pack problem  
1. See the ‘‘ATM-INTF (TN2305/6)’’ maintenance object.  
B-channel in use.  
1004  
1. See if a call is active. Run status trunk grp#/mbr# command.  
2. If the service state is In-Service/Idle, retry the test.  
Bad configuration (for example, no Maintenance/Test circuit pack)  
1. Make sure that the Maintenance/Test Circuit Pack is inserted.  
2. Repeat the test.  
1005  
1018  
ABORT  
ABORT  
Test call disabled  
1. Enable Maintenance on the Trunk Group form.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-136  
Table 3-56. TEST #258 ISDN Test Call — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
TN230x circuit-pack problem  
1020  
ABORT  
1. See the ‘‘ATM-INTF (TN2305/6)’’ maintenance object.  
1024  
ABORT  
Maintenance/Test Digital Port in use  
1. Wait until yellow and green LEDs on the Maintenance/Test circuit pack  
are OFF.  
2. Rerun the test.  
3. If the problem persists, see the M/T-DIG (Maintenance/Test Digital Port)  
maintenance object.  
1113  
1116  
ABORT  
ABORT  
Signaling link failed  
1. Check the results of Test #255 (Signaling Link State Check Test).  
Switch could not change the service state  
1. See if calls are active. Run status trunk grp#/mbr#.  
2. If a call is active. proceed as for Error Code 1119.  
3. If not, check the Error and Alarm Logs and refer to the ATM-TRK (Circuit  
Emulation Service Circuit Pack) maintenance object.  
1117  
1118  
ABORT  
ABORT  
ISDN service message outstanding  
1. Wait 2 minutes. Then try again.  
Far-end not administered  
1. Check the administration of the far-end of the ATM trunk. Run status  
trunk grp#/mbr#.  
2. Try the test again.  
1119  
1120  
ABORT  
ABORT  
Test call aborted, normal call attempted  
1. Wait for the call to terminate normally or drop it by running busyout  
trunk grp#/mbr#.  
2. When the trunk is idle, retry the test.  
Trunk OUT-OF-SERVICE/FAR-END  
1. Try to change the service state via Test #256 (Service State Audit Test).  
2. Try the test again.  
1122  
1123  
ABORT  
ABORT  
No test-line number for the far-end switch  
1. Check the Trunk Group Administration form.  
No Feature Access Code administration for this Facility Test  
1. Check the Dial Plan and Feature Administration forms.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-137  
Table 3-56. TEST #258 ISDN Test Call — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
2012  
None  
ABORT  
Internal system error  
1. Retry the command up to 5 times at 1-minute intervals.  
2035  
ABORT  
ABORT  
ABORT  
Call timed out  
1. Wait 1 minute, and try again.  
2036-  
2037  
Internal system error  
1. Retry the command up to 5 times at 1-minute intervals.  
Problem reading test data  
2038-  
2039  
1. Wait 1 minute, and then try again.  
2. If the test aborts again, there is a serious internal problem.  
Internal system error  
2040  
2041  
2066  
2067  
2074  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
1. Retry the command up to 5 times at 1-minute intervals.  
Call timed out  
1. Wait 1 minute, and try again.  
Could not establish test call  
1. Retry the command up to 5 times at 1-minute intervals.  
Call timed out  
1. Wait 1 minute, and try again.  
Bit and Block Error query failed  
1. Retry the command up to 5 times at 1-minute intervals.  
2. If the test continues to abort, there may be a serious internal problem in  
the Maintenance/Test Digital Port. See the M/T-DIG (Maintenance/Test  
Digital Port) maintenance object.  
2075  
2100  
ABORT  
ABORT  
ABORT  
ABORT  
Internal system error  
1. Retry the command up to 5 times at 1-minute intervals.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
2201-  
2205  
1. Retry the command up to 5 times at 1-minute intervals.  
Could not allocate needed resources  
2206  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-BCH (ATM B-Channel Trunk)  
3-138  
Table 3-56. TEST #258 ISDN Test Call — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2208  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Could not allocate needed resources  
1. Follow recommendations for ABORT code 2100.  
Internal system error.  
2209-  
2210  
2211  
2212  
2213  
2214  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Call terminated by unexpected disconnect  
1. Wait 1 minute and then try again.  
Call timed out  
1. Wait 1 minute, and try again.  
Call terminated by unexpected disconnect  
1. Wait 1 minute and then try again.  
2215-  
2219  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Call terminated prematurely  
2220  
1. Wait 1 minute, and try again.  
2221-  
2226  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Could not allocate needed resources  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Test data corrupt  
2227  
2042  
FAIL  
PASS  
Test pattern intact. If the synchronous test call was performed (long test  
sequence), the communications path is operating properly.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-DCH (ATM D-Channel Port)  
3-139  
ATM-DCH (ATM D-Channel Port)  
MO Name (in  
Alarm Log)  
Initial System Technician  
Command to Run  
1
Alarm Level  
MINOR  
Full Name of MO  
ATM D-Channel  
ATM D-Channel  
2
ATM-DCH  
test port UUCSSpp l  
ATM-DCH  
WARNING  
test port UUCSSpp sh  
1. pp is administered as a port in the range of 9 through 32.  
2. For additional related information, see ‘‘ATM-TRK (Circuit Emulation Service Circuit Pack)’’.  
NOTE:  
TN230x circuit packs are not interchangeable. Always replace an ATM  
circuit pack with the same type.  
This MO (ATM-DCH) utilizes the existing ISDN-PLK or D-channel maintenance  
strategy with modifications. The ATM circuit pack can be administered for up to 8  
Circuit Emulation Service (CES) or signaling groups, each with its own  
D-channel, as opposed to one D-channel for an entire DS1 circuit pack.  
NOTE:  
Due to the dual personalities and the number of D channels the ATM board  
can possess, the in-line errors and signaling port LAN loopback test have  
been moved to the maintenance object ATM-TRK. When an in-line error is  
sent due to PACKET BUS errors, the ATM circuit pack maintenance object  
receives the error, not ATM-DCH.  
The D-channel ISDN-PRI interface, which is emulated for ATM-CES, uses  
out-of-band signaling to transmit control messages between two endpoints. User  
information or bearer channels (B-channels) carry digitized voice and digital  
data and are assigned to DS1 ISDN trunks or PRI endpoints. Call control  
signaling for the B-channels is combined and carried over the separate  
ISDN-PRI Signaling Link Port D-channel.  
Problems with ATM-DCH affects all of the associated B-channels, since call  
control signaling cannot reach the far-end switch or terminal adapter. Stable calls  
may remain operational, but no new calls can be made. ATM-DCH in turn  
depends on the TN230X ATM Trunk circuit pack it resides on and the packet bus  
which provides the link to the processor.  
When working ATM-DCH alarms or errors, also investigate  
■
‘‘ATM-TRK (Circuit Emulation Service Circuit Pack)’’  
PKT-BUS  
■
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-DCH (ATM D-Channel Port)  
3-140  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-57. ATM D-channel Error Log entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1
2
0
0
Any  
Any  
Any  
OFF  
ON  
test port UUCSSpp  
18 (a)  
0
busyout port UUCSSpp  
None  
WARNING  
WARNING  
release port UUCSSpp  
test port UUCSSpp  
test board UUCSS l  
130 (b)  
1793 (c)  
Signaling Link Board  
Check (#643)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. pp is for ports 9-32.  
Notes:  
a. Error Type 18: D-channel busied out; no calls possible over this  
D-channel.  
b. Error Type 130: circuit pack removed or has been insane for more than 11  
minutes. To clear the error, reinsert or replace the circuit pack.  
c. Error Type 1793: ATM Trunk circuit pack failed the Signaling Link Board  
Check (#643). Resolve any ATM-TRK errors in the Error Log.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
The command to test the ATM-DCH maintenance object is test port UUCSSpp,  
where pp is for ports 9-32.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-DCH (ATM D-Channel Port)  
3-141  
Table 3-58. System Technician-Demanded Tests: ATM-DCHL  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Signaling Link Board Check (#643)  
X
X
ND  
1. D = Destructive, ND = Non-destructive  
Signaling Link Board Check (#643)  
This nondestructive test checks the health of the ATM TN230X Trunk circuit pack  
hardware. The test runs on a periodic or scheduled basis, during initialization  
testing, and upon demand.  
NOTE:  
The board-level maintenance is handled independently of the ATM-CES  
signaling link maintenance, raising the possibility of inconsistent states.  
Table 3-59. TEST #643 Signaling Link Board Check  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
FAIL  
Internal System Error  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
The TN230X circuit pack is not in-service.  
8
1. Check the Error Log for ATM-TRK errors and resolve any using ‘‘ATM-TRK  
(Circuit Emulation Service Circuit Pack)’’.  
PASS  
The ATM TN230X circuit pack is in-service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-142  
ATM-EI (Expansion Interface Circuit  
Pack)  
MO Name  
(in Alarm  
Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
ATM-EI  
ATM-EI  
ATM-EI  
MAJOR  
MINOR  
test board UUCSS  
test board UUCSS  
test board UUCSS  
ATM Expansion Interface Circuit Pack  
ATM Expansion Interface Circuit Pack  
ATM Expansion Interface Circuit Pack  
WARNING  
1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation (A, B,  
C, D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21).  
This maintenance object covers the ATM circuit pack administered as an  
ATM-Port Network Connectivity (PNC) Expansion Interface (ATM-EI). The ATM-EI  
provides PNC between a DEFINTY PPN and all the EPNs through the ATM  
switch.  
The circuit packs listed in Table 3-60 are ATM-EI boards if they are administered  
to serve the ATM Port Network Connectivity (ATM-PNC) for DEFINITY.  
Table 3-60. ATM-EI circuit packs for R8  
Echo  
Circuit pack  
TN2305  
TN2306  
Fiber  
Multi mode  
Single mode  
cancellation  
Y
Y
NOTE:  
TN230x circuit packs are not interchangeable. Always replace an ATM  
circuit pack with the same type.  
NOTE:  
ATM switch maintenance is not covered in this section. When DEFINTY ECS  
maintenance software suspects the ATM switch connections, it raises  
appropriate DEFINITY alarms.  
To clear any ATM switch faults, refer to the particular ATM switch’s  
documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-143  
LEDs  
The ATM Interface circuit pack has three LEDs:  
■
■
■
red indicates some alarm condition  
green indicates maintenance testing in progress  
yellow provides useful visual information regarding the operating mode of  
the ATM-EI and possible error conditions.  
The possible LED states are in Table 3-61.  
Table 3-61. ATMInterface LED codes  
LED  
LED status  
Steady on  
Never on  
Condition  
Red  
Board is not healthy  
Normal conditions  
Red and  
Green  
Red LED solid on  
Green LED 200 ms on; 200 ms off  
Board is in the processes of booting  
1
Green  
Steady on  
Maintenance is running tests on the board  
No links to the board  
100 ms on - 100 ms off  
100 ms on -100 ms off  
Yellow  
Fiber Loss of Signal (LOS), LOF, MS_RDI,  
MS_AIS, LCD, HP_RDI, HP_AIS, LOP, PSC  
(See Table 3-65)  
Yellow  
Yellow  
Yellow  
Yellow  
500 ms on; 500 ms off  
2 s on; 0.2 s off  
Steady on  
Signal to the ATM switch is down  
ATM-EI is Expansion Archangel (EAA)  
ATM-EI active (PPN)  
Never on  
ATM-EI standby  
1. The green LED flashes between tests.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-144  
ATM-EI-related commands  
The following commands may be helpful in resolving ATM-EI problems:  
add atm pnc  
list measurements atm  
remove atm pnc  
reset board  
busyout/release atm pnc  
busyout/release board  
change system-parameters  
customer-options (atm pnc)  
status atm-pnc  
change atm pnc  
(pnc duplication)  
status cabinet  
display atm pnc  
list atm oam-statistics  
list atm pnc  
status port-network  
test board  
Replacing an ATM-EI circuit pack  
Standard Reliability  
1. Enter busyout atm-pnc # (this will affect service) at the DEFINITY SAT.  
2. Replace the ATM-PNC circuit pack and re-connect the fiber.  
3. Enter release atm-pnc.  
4. Wait 2.5 minutes for board insertion.  
5. Enter list sys-link to verify that the links are up.  
6. Enter test board UUCSS and verify that all tests pass.  
High Reliability  
There are 2 ATM-EI circuit packs in the PPN, 1 in the EPN.  
1. Enter busyout atm pnc # at the DEFINITY SAT.  
NOTE:  
If the ATM-EI is in an EPN, this will affect service.  
2. Replace the circuit pack.  
3. Enter release atm pnc.  
4. Wait 2.5 minutes for board insertion.  
5. Enter list sys-link to verify that the links are up.  
6. Enter test board UUCSS and verify that all tests pass.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-145  
Critical Reliability  
There are 2 ATM-EI circuit packs in the PPN, 2 in the EPN.  
1. Enter status pnc at the DEFINITY SAT. If the board is on the active side,  
enter reset pnc interchange to switch the active ATM-EI board to the  
standby side.  
2. Enter busyout pnc-standby.  
3. Enter busyout atm-pnc # a-pnc or b-pnc.  
4. Replace the circuit pack.  
5. Enter release atm pnc #.  
6. Enter release pnc-standby.  
7. Wait 2.5 minutes for board insertion.  
8. Enter test board UUCSS and verify that all tests pass.  
Basic ATM PNC administration  
NOTE:  
This section contains basic administration information only. Refer to  
DEFINITY ECS Installation, Upgrade, and Administration for ATM for more  
detailed information.  
ATM PNC connections involve administering  
■
■
■
1 ATM-EI board in each Port Network (Standard Reliability)  
2 ATM-EI boards in the PPN; 1 in each EPN (High Reliability)  
2 ATM-EI boards in every Port Network (Critical Reliability)  
Adding ATM PNC connections  
Standard Reliability  
1. If the ATM-EI circuit pack is not present or if the circuit pack is present but  
is in an EPN, use the change circuit-pack command to add circuit pack  
translation.  
2. Enter add atm pnc n (connection number), and administer the circuit  
pack location and ATM address.  
Critical Reliability  
1. Enter change system-parameters duplication and change the Enable  
Operation of PNC Duplicationfield to n.  
2. If the ATM-EI circuit pack is not present or is present but it is in an EPN that  
does not yet have PNC connectivity to it, use the change circuit-pack  
command to add circuit pack translation for the missing circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-146  
3. Enter add atm pnc n (connection number), and administer the circuit  
pack location and ATM address.  
4. Enter change system-parameters duplication and change the Enable  
Operation of PNC Duplicationfield to y.  
Removing ATM PNC connections  
Standard Reliability  
NOTE:  
Standard Reliability systems are not equipped with PNC duplication.  
1. Enter busyout atm-pnc n (connection number)  
2. Enter remove atm-pnc n (connection number)  
Critical Reliability  
1. Enter status pnc and ensure that the A-PNC is active. If it is not active,  
request a PNC interchange using the reset pnc interchange command.  
2. Enter busyout pnc-standby.  
3. Enter change system-parameters duplication and change the Enable  
Operation of PNC Duplicationfield to n.  
4. Enter busyout atm-pnc n (port network number).  
5. Enter remove atm pnc n (port network number) to remove both ATM-EI  
boards, or enter change atm pnc to remove the B-side ATM-EI board.  
6. Enter change system-parameters duplication and change the Enable  
Operation of PNC Duplicationfield to y.  
Changing circuit pack location or ATM address  
Standard Reliability  
NOTE:  
Standard Reliability systems are not equipped with PNC duplication.  
1. Remove the ATM PNC connection (see ‘‘Removing ATM PNC  
connections’’ above).  
2. Add an ATM PNC connection (see ‘‘Adding ATM PNC connections’’  
above).  
A-side ATM-EI — Critical Reliability  
1. Remove the ATM PNC connection (see ‘‘Removing ATM PNC  
connections’’ above).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-147  
2. Add an ATM PNC connection (see ‘‘Adding ATM PNC connections’’  
above).  
B-side ATM-EI — Critical Reliability  
1. Enter status pnc and ensure that the A-PNC is active.  
If it is not active, request a pnc interchange using the reset pnc  
interchange command.  
2. Enter busyout pnc-standby.  
3. Enter list config car and verify that an ATM circuit pack is administered  
for the new location. If it is not, add the ATM circuit pack translations.  
4. Enter busyout atm pnc n (connection number) b-pnc.  
5. Enter change atm pnc n (connection number) and change circuit pack  
location for the B side.  
6. Enter release pnc-standby.  
Changing ATM address of a Standby ATM-PNC EI — Critical  
Reliability  
1. Enter busy pnc-standby.  
2. Enter change atm pnc n (connection number) and change the ATM  
address for the standby side.  
3. Enter release pnc-standby.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-148  
Error Log Entries and Test to Clear Values  
Table 3-62. ATM-EI Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
ON  
test board UUCSS  
2 (a)  
None  
MIN  
WAR  
WAR  
MIN  
MIN  
MAJ  
18 (b)  
23 (c)  
0
0
busy out board UUCSS  
OFF  
OFF  
ON  
release board UUCSS  
None  
None  
None  
125 (d)  
131 (e)  
257-9 (f)  
ON  
Any  
Expansion Interface  
Control Channel Test  
(#316)  
ON  
test board UUCSS r 2  
513 (g)  
769 (h)  
770 (h)  
771 (h)  
Any  
34, 35  
31  
ATM Crosstalk Test  
(#1298)  
MIN  
ON  
test board long UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
ATM Board Error Query  
Test (#1259)  
WRN  
WRN  
WRN  
OFF  
OFF  
OFF  
ON  
ATM Board Error Query  
Test (#1259)  
26  
ATM Board Error Query  
Test (#1259)  
1024 -  
1151 (i)  
Any  
None  
WRN/  
MIN  
1153 (j)  
1281 (k)  
None  
WRN  
MAJ  
ON  
test board UUCSS  
ATM Board Error Query  
Test (#1259)  
OFF  
test board UUCSS r 1  
1537 (l)  
1538 (m)  
1793 (n)  
2049 (o)  
2050 (o)  
12  
0
None  
None  
None  
None  
MIN  
MIN  
MIN  
MIN  
MIN  
ON  
ON  
13  
15  
ON  
OFF  
OFF  
test board UUCSS r 4  
test board UUCSS r 4  
Expansion Interface Lock  
Query test (#304)  
2305 (p)  
2309 (p)  
None  
MIN  
MIN  
ON  
ON  
Packet interface test  
(#598)  
test board UUCSS r 2  
test board UUCSS r 3  
test board UUCSS  
2561 (q)  
2817 (r)  
Expansion Interface 2-way  
Transmission test (#241)  
MAJ  
MIN  
OFF  
ON  
Any  
ATM Board DSP test  
(#1293)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-149  
Table 3-62. ATM-EI Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
None  
Test to Clear Value  
2818 (r)  
3329 (s)  
3585 (t)  
Any  
3
MIN  
MAJ  
MAJ  
ON  
OFF  
ON  
test board UUCSS  
LANHO critical error  
ATM Framer Looparound  
Test (#1260)  
test board UUCSS l  
test board UUCSS l  
3586 (t)  
ATM Framer Looparound  
Test (#1260)  
MAJ  
ON  
3841 (u)  
3842 (v)  
3999 (w)  
Any  
Any  
None  
None  
2
32767  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Aux Data 32767 for any error log entry indicates that an alarmed ATM-EI was busied out and then  
released. When this occurs, existing service-affecting alarms must be preserved. Typically, all  
alarms are resolved when the ATM-EI is released. Therefore, the Alarm and Error Logs must be  
repopulated with the alarms present at time of busyout. This Aux Data indicates that existing Error  
Type and Error Log time stamps are no longer valid because they were lost when the circuit pack  
was released.  
Notes:  
a. Error Type 2: on-board DUART chip failed. This results in communication  
failure between the port network’s maintenance board and the ATM-EI  
board. The Maintenance circuit pack should have a red LED lit, because  
the link to the ATM-EI is down in this EPN.  
1. Reset the board with the reset board UUCSS command.  
2. If the board does not recover, replace the board.  
b. Error Type 18: the ATM-EI circuit pack has been busied out.  
1. Release the circuit pack (release board UUCSS).  
c. Error Type 23: an ATM-EI circuit pack has been administered with the add  
atm-pnc n command, but the circuit pack has not been inserted into the  
system.  
1. Insert an ATM-EI circuit pack at this location.  
d. Error Type 125: a wrong circuit pack is located in the slot where the  
ATM-EI circuit pack is logically administered.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-150  
1. Either remove the wrong circuit pack and insert the ATM-EI circuit  
pack or remove the ATM-EI administration (see ‘‘Basic ATM PNC  
administration’’).  
2. Remove the ATM-INTF administration and re-administer the slot  
(change circuit-pack) to match the circuit-pack that is physically  
present in this slot.  
e. Error Type 131: an ATM-EI circuit pack has been removed from the slot for  
5 minutes.  
1. Insert the ATM-EI circuit pack into its administered slot.  
2. Another way to resolve or prevent this alarm is to remove the  
ATM-EI administration (see ‘‘Basic ATM PNC administration’’), then  
remove the ATM-INTF administration (change circuit-pack).  
It is possible that the ATM-EI could be held in reset by the EPN  
Maintenance board and is not inserted in the system.  
1. Try issuing the test maint P long command on the maintenance  
board in the same port network.  
f. Error Type 257: Expansion Interface Control Channel Test #316 failed  
(board cannot communicate on the TDM bus control channel). Follow the  
suggested test procedures.  
Error Type 258: The archangel is out of sequence (Aux Data indicates  
angel number).  
Error type 259: the expansion archangel link (EAL) to the active ATM-EI  
board is down. See SYS-LINK.  
g. Error Type 513: ATM Crosstalk test failed. The board is either writing to or  
reading from a TDM time slot that is not allocated to the board.  
1. Test the board (test board UUCSS) and follow the test procedures  
suggested for this test. In random tests of a single DSP during low  
or high traffic, the same DSP may be tested more than once.  
h. Error Type 769 and 770 (Error Type 771 below): board-degraded alarm  
errors that result when the ATM switch is sending corrupted cells or  
excessive AAL/LAPD retransmissions (off-board ATM cell corruption  
errors). These errors indicate the detection of a problem in handling ATM  
cells that are received from the fiber interface.  
Aux Data:  
Error  
Type  
Aux  
Data  
Description  
769  
769  
770  
771  
34  
35  
25  
26  
AAL5 Excessive: retransmission requests  
LAPD Excessive: retransmission requests  
ATM Uncorrectable cell headers - threshold  
VPI,VCI pair unknown  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-151  
The problem is most likely not on the ATM-EI circuit pack reporting the  
errors, but it could be due to one or more of the following reasons:  
■
■
■
The fiber is not snugly connected to either the board or the ATM  
switch.  
The PN packet bus is corrupting the cells. See Packet maintenance  
objects (Aux Data 35 only).  
The fiber between the ATM switch and the ATM-EI is too long  
(greater than 2km for multimode fiber). Use loopback to see if the  
fiber is corrupting the cells.  
■
■
Some other ATM-EI board is not receiving the cells properly.  
The intervening ATM switch is dropping the ATM cells due to a  
shortage of bandwidth, or the DEFINITY is using more than the  
subscribed bandwidth.  
Error Type 771: the ATM switch is sending cells with unknown VPI and VCI  
address (wrong connection).  
1. Ensure that the ATM-EI board address on the ATM switch matches  
the ATM-EI (ATM) address on the DEFINITY side.  
i. Error Type 1024-1151: These errors represent problems detected by the  
ATM-EI board in response to SETUP and ADDPARTY requests from  
software.  
■
The Error Types and descriptions are in Table 3-63:  
■
Aux Data values represent port network and angel numbers and  
are in Table 3-64.  
Table 3-63. ATM Error Types 1024 - 1151  
Error  
Type  
1024  
1056  
Description  
General problem  
Next node unreachable  
DTL Transit not my node ID  
ATM protocol stack on  
ATM-EI circuit pack  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-152  
Table 3-63. ATM Error Types 1024 - 1151 — Continued  
Error  
Type  
Description  
General problem  
1088 or  
1104  
ATM-EI circuit pack received a request with an  
invalid connection identifier.  
1089 or  
1105  
ATM-EI circuit pack received a request with a  
reference to an unknown VC token.  
1090 or  
1106  
ATM-EI circuit pack did not have enough  
resources (memory) for the requested operation.  
1091 or  
1107  
Internal failure in the local protocol stack. This  
can occur when the connection to the ATM  
switch failed, perhaps because the:  
■
■
ATM switch rebooted  
Firmware-detected  
fiber between the ATM switch and the  
ATM-EI circuit pack disconnected  
problems on the ATM-EI  
circuit pack. Note: Error  
Types 1088-1103 are  
reported by the board  
that is originating the  
connection. Error Types  
1104-1119 are reported  
by the board that is  
terminating the  
1092 or  
1108  
ATM-EI circuit pack received a request for which  
the referenced VC was in the wrong call state.  
1093 or  
1109  
ATM-EI circuit pack received a request for which  
the VPI/VCI pair was invalid or out of range.  
1094 or  
1110  
ATM-EI circuit pack received a request to add a  
party to an existing VC. The add party request  
failed, and a retry was not possible.  
connection. In most  
cases, when the  
1095 or  
1111  
ATM-EI circuit pack in link recovery after the  
lower ATM layer (Q.SAAL portion of the protocol  
stack) failed. This can occur when the connection  
to the ATM switch failed, perhaps because the:  
teminating board reports  
one of these errors, the  
originating board will also  
report an ATM-NTWK  
error for the same event  
(usually with Error Type  
21).  
■
■
ATM switch rebooted  
fiber between the ATM switch and the  
ATM-EI circuit pack disconnected  
1096 or  
1112  
ATM-EI circuit pack received an error from the  
local protocol stack for which no more detailed  
cause was specified.  
1102  
1103  
ATM-EI circuit pack asked to create more  
connections that it was capable of creating.  
ATM-EI circuit pack detected an illegal message  
from software.  
1. Check the Error Log for CONN-M proc errors  
for more information.  
1113  
Problems detected by the  
board terminating the  
connection  
1. Test the ATM-EI circuit pack (test board UUCSS) and investigate  
further based on each test’s results. If all tests pass, the error was a  
transient problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-153  
Aux Data values: For each connection request failure type, the port  
network and the angel number of the destination ATM-EI circuit pack are  
logged Aux Data values in the form XXYYY, where  
■
port network number = XX  
angel number = YYY  
■
Since you need to know the slot number also, Table 3-64 converts the Aux  
Data to slot numbers.  
Table 3-64. Error Type 1024-1151 Aux Data values (XXYYY) converted to slot number  
Carrier  
A
B
C
D
E
Failure type  
Failure type  
Failure type  
Failure type  
Failure type  
Add  
Add  
Add  
Add  
Add  
Slot  
1
Setup  
28  
29  
30  
31  
56  
57  
58  
59  
60  
61  
62  
63  
88  
89  
90  
91  
92  
93  
94  
95  
NA  
NA  
Party  
528  
529  
530  
531  
556  
557  
558  
559  
560  
561  
562  
563  
588  
589  
590  
591  
592  
593  
594  
595  
NA  
Setup  
66  
67  
68  
69  
70  
71  
72  
73  
74  
75  
76  
77  
78  
79  
80  
81  
82  
83  
84  
85  
86  
87  
Party  
566  
567  
568  
569  
570  
571  
572  
573  
574  
575  
576  
577  
578  
579  
580  
581  
582  
583  
584  
585  
586  
587  
Setup  
98  
Party  
598  
599  
600  
601  
602  
603  
604  
605  
606  
607  
608  
609  
610  
611  
612  
613  
614  
615  
616  
617  
618  
619  
Setup  
34  
35  
36  
37  
38  
39  
40  
41  
42  
43  
44  
45  
46  
47  
48  
49  
50  
51  
52  
53  
54  
55  
Party  
534  
535  
536  
537  
538  
539  
540  
541  
542  
543  
544  
545  
546  
547  
548  
549  
550  
551  
552  
553  
554  
555  
Setup  
02  
03  
04  
05  
06  
07  
08  
09  
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
Party  
502  
503  
504  
505  
506  
507  
508  
509  
510  
511  
512  
513  
514  
515  
516  
517  
518  
519  
520  
521  
522  
523  
2
99  
3
100  
101  
102  
103  
104  
105  
106  
107  
108  
109  
110  
111  
112  
113  
114  
115  
116  
117  
118  
119  
4
5
6
7
8
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
NA  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-154  
j. Error type 1153: the ATM connection audit found some discrepancy in the  
firmware’s VC token numbers and live VCs. The problem is rectified in  
firmware and no action is needed.  
k. Error Type 1281: loss of high-level signal indicating operational problems  
of equipment located outside of the circuit pack and the fiber connected  
to the board. Aux Data values are listed in Table 3-65.  
Table 3-65. Error type 1281 Aux Data and repair procedures  
Aux  
Alarm  
Data  
Description  
Repair procedure  
15  
SYSCLOCK failed  
The board is not locked to the TDM backplane clock signal. This is  
probably due to a Tone Clock problem.  
1. Check for TDM-BUS or TONE-BD errors in the Error Log.  
2. If no other problems are present, reset the circuit pack (reset  
board UUCSS)  
16  
Loss of Signal:  
LOS  
The fiber is not connected properly to the ATM-TRK board or ATM  
switch (or to the multiplexer section [MUX] if present).It is possible  
that the board transceivers are not functioning properly.  
1. Run test board UUCSS command.  
2. If Test #1259 fails, connect a fiber back-to-back in a looped  
mode (one strand of fiber connecting the transmit transceiver  
to the receive transceiver of the board) and see if the yellow  
LED flash goes away. If it does the problem is off-board.  
3. If the yellow LED continues to flash, replace the circuit pack.  
The fiber signal cannot obtain or maintain STM-1/OC-3 framing.  
17  
18  
Loss of Frame:  
LOF  
1. Try to move the fiber on the ATM switch side to a different port.  
This may require administration on the ATM switch.  
2. If the problem persists, reset the circuit pack (reset board  
UUCSS).  
Multiplexer  
There is a major problem on the far end (between multiplexer  
section [MUX] and the switch) that prohibits the circuit pack from  
sending a valid signal.  
Section Alarm  
Indication Signal:  
MS_AIS  
1. See if the ports at the MUX and/or the ATM switch are  
connected snugly.  
2. Run test board UUCSS command  
3. If Test #1259 fails with Error Code 18, connect a fiber  
back-to-back in a looped mode (one strand of fiber connecting  
the transmit transceiver to the receive transceiver of the board)  
and see if the yellow LED flash goes away.  
4. If it does the problem is off-board.  
5. If the yellow LED continues to flash, replace the circuit pack; if  
the error persists, escalate the problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-155  
Table 3-65. Error type 1281 Aux Data and repair procedures — Continued  
Aux  
Alarm  
Data  
Description  
Repair procedure  
19  
Multiplexer  
The far-end is detecting a major problem with the signal that this  
board is transmitting.  
Section Remote  
Defect Indicator:  
MS_RDI  
1. Make sure the ATM switch port (or a MUX port, if present  
between ATM switch and the ATM-TRK board) is the same as  
the ATM-TRK circuit pack’s cable interface  
2. Run test board UUCSS command.  
3. If Test #1259 fails with Error Code 19, connect a fiber  
back-to-back in a looped mode (one strand of fiber connecting  
the transmit transceiver to the receive transceiver of the board)  
and see if the yellow LED flash goes away.  
4. If it does the problem is off-board.  
5. If the yellow LED continues to flash, replace the circuit pack; if  
the error persists, escalate the problem.  
20  
21  
Loss of pointer:  
LOP  
ATM framer chip is unable to access the payload part of the signal.  
1. Reset the board (reset board UUCSS).  
2. If the error persists replace the board.  
Path Signal Error  
(PSL)  
The incoming signal payload is not set up for transmission of ATM  
data.  
(STM1/SONET)  
1. Make sure the ATM switch port (or a MUX port, if present  
between ATM switch and the ATM-TRK board) is the same as  
the ATM-TRK circuit pack’s cable interface.  
22  
High-level Path  
Alarm Indication  
Signal:  
The payload is invalid.  
1. Make sure the ATM switch port (or a MUX port, if present  
between ATM switch and the ATM-TRK board) is the same as  
the ATM-TRK circuit pack’s cable interface.  
HP_AIS  
2. Run test board UUCSS.  
3. If Test #1259 fails with Error Code 22, connect a fiber  
back-to-back in a looped mode (one strand of fiber connecting  
the transmit transceiver to the receive transceiver of the board)  
and see if the yellow LED flash goes away.  
4. If it does the problem is off-board.  
5. If the yellow LED continues to flash, replace the circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-156  
Table 3-65. Error type 1281 Aux Data and repair procedures — Continued  
Aux  
Alarm  
Data  
Description  
Repair procedure  
23  
High-level path  
Remote defect  
Indicator: HP_RDI  
The far-end is detecting a major problem with the signal that this  
board is transmitting. The transmitted payload is invalid.  
1. Make sure the ATM switch port (or a MUX port, if present  
between ATM switch and the ATM-TRK board) is the same as  
the ATM-TRK circuit pack’s cable interface.  
2. Run test board UUCSS command; if the Test #1259 fails with  
Error Code 23, connect a fiber back-to-back in a looped mode  
(one strand of fiber connecting the transmit transceiver to the  
receive transceiver of the board) and see if the yellow LED  
flash goes away.  
3. If it does the problem is off-board.  
4. If the yellow LED continues to flash, replace the circuit pack.  
24  
27  
Loss of cell  
delineation (LCD)  
On board ATM framer chip is not able to frame cells based on the  
cell header.  
1. Reset the board (reset board UUCSS).  
2. If the error persists, replace the board.  
The board cannot communicate with the ATM switch.  
1. Busyout the board (busyout board UUCSS).  
2. Test the board (test board long UUCSS).  
3. If Test #1260 fails, replace the board.  
SIGCON_DOWN  
ATM switch high  
level signal.  
4. If Test #1260 passes, make sure the ATM address on both the  
DEFINITY and the ATM switch sides are the same for this  
board.  
5. If the address is the same, change the port on the ATM switch  
side. This may require administration on the ATM switch.  
6. If the error is resolved, the problem is on the ATM switch port.  
l. Error Type 1537: LAN bus time out. The circuit pack is transmitting a  
packet larger than 1,024 bytes. Replace the circuit pack.  
m. Error Type 1538: A hyperactive ATM-EI circuit pack is generating an  
abnormal amount of control messages to the processor. When this error is  
generated, the system automatically resets the ATM-EI.  
Duplicated PNC? Then:  
Y
service to the EPN is disrupted  
N
the system switches to the standby PNC  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-157  
1. Enter the reset board UUCSS command for this ATM-EI circuit  
pack.  
2. If the same error persists, replace the ATM-EI circuit pack.  
n. Error Type 1793: LANHO transmit FIFO overflow error (the transmit FIFO  
RAM buffers on the circuit pack overflowed). This most likely indicates a  
hardware problem on the circuit pack, because the speed of the  
LAN/Packet Bus is much higher than the speed of the link connected to  
the port.  
1. Test this ATM-EI circuit pack (test board UUCSS).  
2. If Test #598 fails again, replace the ATM-EI circuit pack.  
o. Error Type 2049, 2050: the ATM-EI is out of lock with the backplane system  
clock.  
1. Test this ATM-EI circuit pack (test board UUCSS).  
2. If Test #304 fails, follow the repair procedures suggested for this  
test.  
p. Error Type 2305: too many parity errors on data received from the  
LAN/Packet Bus (could be due to packet bus problems).  
1. Test the ATM-EI circuit pack (test board UUCSS).  
2. If Test #598 fails, follow the repair procedures suggested for this  
test.  
3. If the test passes, look for and resolve any PKT-BUS (Packet Bus)  
alarms/errors.  
4. If there are no PKT-BUS errors and the problem persists, escalate  
the problem.  
Error Type 2309: packet interface chip (LANHO) malfunctioning.  
1. Test the ATM-EI circuit pack (test board UUCSS).  
2. If Test #598 fails, follow the repair procedures suggested for this  
test.  
q. Error Type 2561: ATM-EI 2-way Transmission Failure (circuit pack is having  
problems creating connections to other port networks in the system).  
1. Test the ATM-EI circuit pack (test board UUCSS).  
2. Follow the repair procedures suggested for Test #241.  
r. Error Type 2817, 2818: DSP test failure detected along the circuit path of  
the ATM-EI circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-158  
Error  
Type  
Description  
Aux Data indicates  
2817  
DSP test failure  
The Aux Datafield contains the  
following information about the failed  
DSPs:  
■ X is the number of talker DSPs  
■ Y is the number of listener DSPs  
■ Z is the number of  
echo-cancelling DSPs  
2818  
One or more DSPs failed  
DSP number that has failed  
1. Test the ATM-EI circuit pack (test board UUCSS).  
2. Follow the repair procedures suggested for Test #1258.  
s. Error Type 3329: on-board LANHO chip is insane, possibly due to a  
problem in Packet Bus arbitration, the transmission line frame, or the  
circuit pack itself. The circuit pack cannot talk to the packet bus.  
If the packet bus is alarmed:  
1. Resolve PKT-BUS errors, if any. The probability of this error being  
related to Packet bus problem increases with the number of other  
circuit packs using the Packet bus that are also displaying this  
error.  
If the Packet Bus is not alarmed:  
1. Reset the circuit pack (reset board UUCSS).  
2. If the problem persists, replace the ATM-EI circuit pack.  
If the system has a duplicated PNC, and the in-line error received is from  
an active ATM-EI, the system switches to the standby PNC.  
!
CAUTION:  
If the system does not have duplicated PNC, services to the EPN  
could be disrupted.  
t. Error Type 3585, 3586 (Major board alarm): failure of critical components  
involved in the operation of the circuit pack, and the switch may no longer  
recognize the circuit pack. If the system has a duplicated PNC and the  
in-line error received is from an active ATM-EI, the system switches to  
standby PNC.  
!
CAUTION:  
If the system does not have duplicated PNC, services to the EPN  
could be disrupted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-159  
Error Type 3585:  
Aux Data (Error Type 3585 only):  
Aux  
Data Description  
1
2
4
5
6
7
8
ATM framer failure  
NCE failed (only from ATM-EIs in EPN)  
TDM_PLD_FAILED  
DSP_ALL FAILED  
Receive Network Processor (RNP) failure  
Transmit Network Processor (TNP) failure  
MEMORY read/write failure  
1. If the board is in a PPN, or if the system has duplicated PNC:  
a. Test the ATM-EI (test board UUCSS l).  
b. If Error 3585 is detected again, or if the board is not  
recognized anymore, replace the ATM-EI circuit pack.  
2. If the system does not have duplicated PNC, and the circuit pack is  
in an EPN:  
a. Replace the ATM-EI circuit pack.  
Error Type 3586: Framer Looparound Test #1260 failed.  
Aux Data (Error Code 3586 only):  
Aux  
Data Description  
2
3
4
5
Packet path failed  
Circuit path failed  
TDM loop cannot be created  
Packet loop cannot be created  
1. If Error Type 3586 is detected again, replace the circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-160  
u. Error Type 3841: the board received a message from the switch that it  
does not recognize, and the board responded with an inconsistent down  
link error message. This error does not affect service, and no action is  
required.  
v. Error type 3842: the circuit pack received data from the Packet Bus faster  
than it could distribute the data to its endpoint. This circuit pack should be  
able to recover by itself, and no action is necessary.  
w. Error Type 3999: circuit pack sent a large number of control channel  
messages to the switch within a short period of time.  
If  
Then  
Error Type 1538 is also  
present  
Circuit pack is taken out of service  
If Error Type 1538 is not  
present  
Circuit pack is not taken out of service, but has  
generated 50% of the messages necessary to  
be considered hyperactive.  
■ This may be normal during heavy traffic.  
■ If the error is logged during light traffic, it  
may indicate a problem with the circuit pack  
or the equipment attached to it.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-161  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in Table 3-66 when inspecting the  
errors in the system. By clearing error codes associated with the Expansion  
InterfaceTest, for example, you may also clear errors generated from other tests  
in the testing sequence.  
Table 3-66. System Technician-Demanded Tests: ATM-EI  
Short Test Long Test Reset Board  
1
Order of Investigation  
Sequence  
Sequence  
Sequence  
D/ND  
Expansion Interface 2way-Transmission Test  
(#241)  
X
X
ND  
ATM Board Framer Looparound Test (#1260)  
Expansion Interface Lock Query Test (#304)  
ATM Board Error Query Test (#1259)  
X
X
X
D
X
X
ND  
ND  
D
ATM Expansion Interface Reset (#1256)  
X
ATM board DSP test(#1293) for TN2305 and  
TN2306 circuit packs.  
X
X
X
ND  
ATM Cross Talk test(#1298) for TN2305 and  
TN2306 circuit packs  
ND  
Continued on next page  
1. D = Destructive, ND = Non-destructive  
NOTE:  
To get a better indication of a problem’s location, test both ATM-EI circuit  
packs on the associated fiber link, whether the circuit packs are both  
ATM-EI circuit packs or not.  
Expansion Interface 2-way Transmission Test  
(#241)  
This test is non-destructive and applies to all ATM-EIs, both active and standby. It  
is run as part of craft short and long testing, periodic, scheduled, initialization,  
and error analysis testing. The test sets up a connection between a Tone/Clock in  
one cabinet and a Tone Detector in a separate cabinet and transmits a digital test  
count between the port networks. The ATM-EIs used to set up this connection are  
chosen by maintenance, not call processing. After the connection is checked for  
dial-tone, the connection is torn down and re-established in the opposite  
direction.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-162  
In this test the second ATM-EI may be in any port network outside the port  
network of the ATM-EI under test. Therefore if the test should fail in any direction,  
the test is repeated with a different port network, if available, which aids the fault  
isolation procedure.  
The test results indicate if the test failed in one or both directions. The test aborts  
if the ATM-EIs do not exist on both ends (for example, the EIs are not  
administered correctly). If the test passes, the TDM and ATM framer interfaces of  
both ATM-EIs are functioning properly. If the test fails, a series of tests are run on  
the board. Figure 3-3 shows a schematic of this test.  
ATM  
circuit  
pack  
ATM  
circuit  
pack  
TDM bus  
(PN X)  
TDM bus  
(PN Y)  
Tone  
detector  
Tone  
clock  
ATM  
switch  
Tone  
clock  
Tone  
detector  
PNC mode  
PNC mode  
iodf2way AWF 040699  
Figure 3-3. Expansion Interface 2-Way Transmit Test #241  
PN X and PN Y represent any of 43 possible port networks.  
Table 3-67. Expansion Interface 2-way Transmission Test (#241)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
1002  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out of service due  
to TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
retry the command at 1-minute intervals a maximum of 3 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-163  
Table 3-67. Expansion Interface 2-way Transmission Test (#241) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system  
may be oversized for the number of tone detectors present, or some tone  
detectors may be out of service.  
1. Resolve any TTR-LEV errors. Even if there are not TTR-LEV errors,  
there may not be a tone detector available on the network that  
contains the circuit pack being tested. Verify that there is at least one  
tone detector on this network. If not, this test always aborts for this  
ATM-EI circuit pack, but does not harm the system.  
NOTE:  
DEFINITY Systems require that Tone Clock circuit packs (TN2182)  
must be of vintage “B” or newer. If older Tone Detector circuit  
packs are installed in the system, this test always aborts with this  
abort code.  
2. Resolve any TONE-PT errors.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 3 times.  
1033  
ABORT  
The test cannot run because either the ATM-EI board is not  
administered, or there were no other PNs administered that had its  
ATM-EI board in-service.  
1. Ensure that the board is administered as ATM PNC Expansion  
Interface circuit pack.  
If the board is administered as ATM-EI circuit pack, then there has  
been some change in the ability of the ATM-EI circuit pack in the  
other PNs to communicate with the ATM-EI on the other end of its  
connection.  
2. Using status port x (the port-network number in which the board is  
administered), see if both ACL and EAL are up to this board. If they  
are not, see the service procedure for SYS-LINK.  
3. Check the Error Log for Error Type 1281 with Aux Data 27 (board  
cannot talk to the ATM switch). See Table 3-65 for repair procedures.  
If present, check both the ATM switch and the DEFINITY  
administrations for consistent ATM addresses. Reset the board and  
see if the problem resolves.  
4. Repeat Test #241. If it continues to abort with this abort code,  
replace the board.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-164  
Table 3-67. Expansion Interface 2-way Transmission Test (#241) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1394  
ABORT  
1. See Table 3-65 (Error Type 1281) with Aux Data 27 (board cannot  
talk to the ATM switch), and if present, check both the ATM switch  
and the DEFINITY administrations for consistent ATM addresses.  
2. Reset the board and see if the problem resolves.  
3. Repeat the test.  
1395  
ABORT  
This test cannot run on an ATM-EI circuit pack if it is part of the B-side  
PNC and Duplicated PNC is not enabled.  
1. If this test needs to run on this ATM-EI circuit pack, enable PNC with  
the change system-parameters duplication command.  
2. Prevent the system from doing a PNC interchange by executing the  
set PNC lock command.  
3. Repeat this test.  
1413  
ABORT  
This test requires the use of a Tone/Clock circuit pack in each of the port  
networks (PN) used in this test. This abort code indicates that a  
Tone/Clock circuit pack is not present in one of the PNs.  
1. Make sure that there is a Tone/Clock circuit pack located in the PN in  
which the ATM PNC Expansion Interface circuit pack under test is  
located.  
2. In ATM PNC configurations, make sure that there is at least one other  
PN besides the PN where the ATM-EI circuit pack under test resides  
that contains a Tone/Clock circuit pack.  
1414  
ABORT  
The active Tone/Clock circuit pack in one of the port networks being  
used for the test has a MAJOR or MINOR alarm logged against it.  
1. Enter display alarms and resolve any TONE-BD and TONE-PT  
alarms.  
1956  
2000  
ABORT  
ABORT  
ACL to the board is not up. See ACL status with the list sys-link  
command and follow the repair procedures for SYS-LINK.  
Response to the test request was not received within the allowable time  
period.  
2100  
2500  
ABORT  
ABORT  
System resources required to run this test are not available.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
The test tone was not detected correctly in either direction.  
FAIL  
1. Test the active Tone/Clocks on the Port Networks for which the  
ATM-EI circuit pack under test provides a link. This determines if the  
dial tone is supplied.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-165  
Table 3-67. Expansion Interface 2-way Transmission Test (#241) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
10MM FAIL  
The failure codes only apply to a system equipped with an ATM Switch.  
The letters “MM” refer to the distant or far-end port network (PN), and  
“NN” to the near-end ATM-EI under test.  
The test tone was detected correctly in forward direction (data sent from  
the PN in which the circuit pack under test resides and detected  
correctly in port network MM), but not the opposite direction.  
1. Test the active Tone/Clocks on the “MM” PN and the PN in which the  
ATM-EI under test resides (test tone-clock UUCSS). This determines  
if a dial tone is supplied.  
2. Ensure that the ATM address of the ATM-EI circuit pack under test  
matches the ATM address on the ATM switch for the port to which  
this circuit pack is connected. Refer to the ‘‘ATM Tips’’ section in  
Chapter 1 for the procedure to check the ATM port address on the  
ATM switch.  
3. Run this Test #241 on the active ATM-EI in port network MM. If this  
test fails with Error Code 10NN or 30NN, go back to Step 2.  
If the address was the same, replace the active ATM-EI circuit pack  
on port network MM.  
If this test fails with Error Code 20NN or 40NN, replace ATM-EI circuit  
pack that had the initial problem.  
20MM FAIL  
The failure codes only apply to a system equipped with an ATM Switch.  
The letters “MM” refer to the distant or far-end port network (PN), and  
“NN” to the near-end ATM-EI under test.  
The test tone was detected correctly in reverse direction (data sent from  
the MM port network was detected correctly in the port network in which  
the circuit pack under test resides, but not the opposite direction).  
1. Test the active Tone/Clock on the “MM” PN and the PN in which the  
ATM-EI under test resides (test tone-clock UUCSS). This determines  
if dial tone is supplied.  
2. Ensure that the ATM address of the active ATM-EI circuit pack under  
test matches the ATM address on the ATM switch for the port to  
which this circuit pack is connected. Refer to the ‘‘ATM Tips’’ section  
in Chapter 1 for the procedure to check the ATM port address on the  
ATM switch.  
3. Run this Test #241 on the active ATM-EI in port network MM. If this  
test fails with Error Code 20NN or 40NN, go back to Step 2.  
If the address was the same, replace the active ATM-EI circuit pack  
on port network MM.  
If this test fails with Error Code 10NN or 30NN, replace ATM-EI circuit  
pack with the initial problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-166  
Table 3-67. Expansion Interface 2-way Transmission Test (#241) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
30MM FAIL  
The failure codes only apply to a system equipped with an ATM Switch.  
The letters “MM” refer to the distant or far-end port network (PN), and  
“NN” to the near-end ATM-EI under test.  
The test failed for the first connection from the ATM-EI board under test  
to another EPN, and the test tone was detected correctly in the forward  
direction (data sent from the port network in which the circuit pack under  
test resides was detected correctly in port network MM, but not the  
opposite direction).  
1. Test the active Tone/Clock on the “MM” PN and the PN in which the  
ATM-EI under test resides (test tone-clock UUCSS). This determines  
if dial tone is supplied.  
2. Ensure that the ATM address of the ATM-EI circuit pack under test  
matches the ATM address on the ATM switch for the port to which  
this circuit pack is connected. Refer to the ‘‘ATM Tips’’ section in  
Chapter 1 for the procedure to check the ATM port address on the  
ATM switch.  
3. Run this Test #241 on the active ATM-EI in port network MM. If this  
test fails with Error Code 10NN or 30NN, go back to Step 2.  
If the address was the same, replace the active ATM-EI circuit pack  
on port network MM.  
If this test fails with Error Code 20NN or 40NN, replace ATM-EI circuit  
pack with the initial problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-167  
Table 3-67. Expansion Interface 2-way Transmission Test (#241) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
40MM FAIL  
Failure code only applies to a system equipped with an ATM Switch. The  
letters “MM” refer to the distant or far-end port network (PN), and “NN” to  
the near-end ATM-EI under test.  
The test failed for the first connection from the ATM-EI board under test  
to another EPN, and the test tone was detected correctly in the reverse  
direction (data sent from the MM port network was detected correctly in  
the port network in which the circuit pack under test resides), but not the  
opposite direction.  
1. Test for the Active Tone-Clocks on the MM PN and the PN in which  
the ATM-EI under test resides. This determines if dial tone is  
supplied.  
2. Ensure that the ATM address of the active ATM-EI circuit pack in port  
network MM matches the ATM address on the ATM switch for the  
port to which this circuit pack is connected. Refer to the ‘‘ATM Tips’’  
section in Chapter 1 for the procedure to check the ATM port  
address on the ATM switch.  
3. Run this Test #241 on the active ATM-EI in port network MM. If this  
test fails with Error Code 20NN or 40NN, go back to Step 2.  
If the address was the same, replace the active ATM-EI circuit pack  
on port network MM.  
If this test fails with Error Code 10NN or 30NN, replace ATM-EI circuit  
pack with the initial problem.  
PASS  
Tone successfully transmitted in both directions. Both ATM-EI boards  
and their lightwave transceivers are functioning properly.  
0
NO  
No board was detected by the test.  
BOARD  
1. Resolve either wrong board (Error 125) or no board (Error 131)  
issues.  
2. Check that the board is properly translated and inserted. If so, check  
for hyperactivity (Error 1538). If hyperactive, use the reset board  
UUCSS command.  
3. Run the test again. If it fails, the ID chip on board may be bad.  
Replace the board and retest.  
Expansion Interface Lock Query Test (#304)  
This test is non-destructive and is used to query the ATM and EI circuit packs  
(both active and standby) for its status concerning lock to the backplane system  
clock. It is run as part of periodic, scheduled, initialization, and error analysis  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-168  
testing. When an in-line, “out-of-lock” report comes in, this test is run to check the  
circuit pack’s status. The ATM-EI responds with “in lock” or “out of lock.” If the  
response is “in lock,” the test passes; if the response is “out of lock,” the test fails.  
Table 3-68. TEST #304 Expansion Interface Lock Query Test (#304)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
2100  
2500  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
FAIL  
The ATM-EI circuit pack responded incorrectly or if it is the EPN active  
ATM-EI circuit pack, it could not talk to EPN circuit packs.  
1. If the active ATM-EI circuit pack in the EPN is failing and duplicated  
PNC is enabled, attempt to switch to the standby PNC using the  
reset PNC interchange command.  
2. Repeat the short test sequence.  
3. If test continues to fail, reset the ATM-EI circuit pack with the reset  
board UUCSS command.  
4. If the ATM-EI circuit pack in the EPN is failing, enter display errors  
and display alarms and follow the associated repair procedures for  
TDM-CLK, TONE-BD, or SYNC alarms/errors and repeat the Short  
Test Sequence.  
5. If test continues to fail, replace the circuit pack or transceiver.  
PASS  
Communication from software to the ATM-EI circuit pack is functioning  
correctly.  
0
NO  
No board was detected by the test.  
BOARD  
1. Check the error log for wrong board (error 125) or no board (error  
131). Resolve either of these issues.  
2. Check that the board is properly translated and inserted. If so, check  
for hyperactivity (error 1538). If hyperactive, use the reset board  
UUCSS command.  
3. Run the test again. If it fails, the NCE chip on board may be bad.  
Replace the board and retest.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-169  
Expansion Interface Control Channel Test (#316)  
This test is non-destructive. If an ATM-EI circuit pack is an active ATM-EI in the  
EPN (yellow LED on long/off short), the Expansion Interface Control Channel test  
checks to see if the ATM-EI circuit pack can communicate with other circuit  
packs in the EPN using the EPN TDM bus.  
If the circuit pack is a standby ATM-EI (yellow LED off) or if the ATM PNC  
Expansion Interface is in the PPN (yellow LED on), this test queries the ATM PNC  
Expansion Interface circuit pack for its circuit pack type and vintage information.  
Table 3-69. Expansion Interface Control Channel Test #316  
Error  
Code  
Test Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test request was not received within the allowable  
time period.  
2100  
2500  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
FAIL  
The ATM-EI circuit pack responded incorrectly or if it is the EPN  
active ATM-EI circuit pack, it could not talk to EPN circuit packs.  
1. If the active ATM-EI circuit pack in the EPN is failing and  
duplicated PNC is enabled, attempt to switch to the standby PNC  
using the reset PNC interchange command.  
2. Repeat the short test sequence.  
3. If test continues to fail, reset the ATM-EI circuit pack with the  
reset board UUCSS command.  
4. If the ATM-EI circuit pack in the EPN is failing, enter display  
errors and display alarms and resolve any TDM-CLK, TONE-BD,  
or SYNC alarms/errors and repeat the Short Test Sequence.  
5. If test continues to fail, replace the circuit pack or transceiver.  
PASS  
The ATM-EI circuit pack did respond correctly to test. Communication  
from software to the ATM-EI circuit pack is functioning.  
1. Refer to other ATM-EI circuit pack tests if the link is not  
functioning correctly.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-170  
Table 3-69. Expansion Interface Control Channel Test #316 — Continued  
Error  
Code  
Test Result  
Description/ Recommendation  
No board was detected by the test.  
0
NO BOARD  
1. Resolve any wrong board (Error 125) or no board (Error 131)  
issues.  
2. Check that the board is properly translated and inserted. If so,  
check for hyperactivity (Error 1538). If hyperactive, use the reset  
board UUCSS command.  
3. Run the test again. If it fails, the NCE chip on board may be bad.  
Replace the board and retest.  
Packet Interface Test (#598)  
This test is non-destructive and attempts to send a data packet from the TN1655  
Packet Interface circuit pack through any ATM PNC Expansion Interface circuit  
packs. The path the data packet takes depends on the location of the ATM-PNC  
Expansion Interface circuit pack being tested and whether the system has  
duplicate Port Network Connectivity.  
The Packet Interface Looparound test checks the Packet Bus interface circuitry  
on this board. The on-board LANHO chip sends a data stream to the bus,  
retrieves it back, and checks for its consistency. If the data is consistent, the test  
passes; otherwise, it fails. The test aborts if the Packet Bus in the specified port  
network has a minor alarm active, is out of service, or if the Packet Bus in the PPN  
is out of service. This test runs as a part of initialization, periodic, scheduled,  
error analysis, and demand test sequences. Figure 3-4 shows a schematic of the  
test.  
ATM  
circuit  
pack  
LAN bus  
(PN X)  
LANHO  
chip  
PNC mode  
iodfchip AWF 040699  
Figure 3-4. Packet Interface Test (#598)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-171  
Table 3-70. Packet Interface Test (#598)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals for a maximum of 3 retries.  
2. If the test fails repeatedly, attempt to reset the circuit pack.  
3. If the test continues to fail, replace the circuit pack.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ANY  
FAIL  
The transmitted data packet was not received correctly by the Packet  
Interface circuit pack. The failure may be in the ATM-EI under test, the  
DS1 CONV circuit packs, or the intervening Center Stage components.  
1. Retry the command at 1-minute intervals a maximum of five times  
2. If the test continues to fail, replace the circuit pack.  
The Packet Interface Test passed.  
PASS  
ATM Board Error Query Test (#1259)  
This test is non-destructive. The ATM circuit pack firmware maintains counters for  
some of the on-board and off-board errors. The maintenance software queries  
the board for its health information to do error analysis. These alarms have  
assigned priority: if a higher priority alarm occurs, the remaining alarms are not  
reported to the software (through the inline errors), avoiding unnecessary up-link,  
in-line error message traffic. This is run as a part of a craft demand test sequence  
periodic testing, initialization, and error analysis.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-172  
Table 3-71. ATM Board Error Query Test (#1259)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
2100  
2500  
ABORT  
ABORT  
ABORT  
Response to the test was not received within the allowable time period.  
System resources required to run this test are not available.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
XXYY  
FAIL  
On-board hardware or off-board signalling errors on the board. XX  
indicates the on-board hardware error, and YY indicates the off-board  
errors on the as shown in Table 3-72.  
1. Resolve any errors in error logs.  
PASS  
No service effecting errors or alarms were detected on the circuit pack.  
No board was detected by the test.  
0
NO  
BOARD  
1. Check the Error Log for wrong board (Error Type 125) or no board  
(Error Type 131). Resolve either of these issues, if applicable.  
2. Check that the board is properly translated and inserted. If so,  
check for hyperactivity (Error Type 1538). If hyperactive, use the  
reset board UUCSS command.  
3. Run the test again. If it fails, the NCE chip on board may be bad.  
Replace the board and retest.  
Table 3-72. XXYY Error Codes for Test #1259  
(ATM Board Error Query Test)  
XX Aux Data Description  
1
2
3
4
5
6
7
8
ATM framer chip failed  
NCE chip failed  
LANHO critical error  
TDM Prog. logic device failed  
All on-board DSPs failed  
Receive network processor failed  
Transmit network processor failed  
Memory read failed  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-173  
Table 3-72. XXYY Error Codes for Test #1259  
(ATM Board Error Query Test) — Continued  
XX Aux Data Description  
9
Dual UART chip failed  
10  
11  
12  
13  
14  
LANHO receive parity error  
LANHO FIFO overflow error  
LAN Bus timeout  
LANHO Xmit FIFO overflow  
One or more on-board DSPs failed  
YY Aux Data Description  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
Backplane clock failed  
Loss of signal  
Loss of frame  
Multiplexer Section Alarm indication signal error  
Multiplexer Section remote defect indicator error  
Loss of pointer  
Path signal level mismatch  
High level path alarm indication signal  
High level path remote defect indicator  
Loss of cell delineation  
Uncorrectable headers sent by the ATM switch  
Too many cells with invalid Virtual Path Indicator (VPI)/Virtual Circuit  
Indicator (VCI) combination  
27  
28  
34  
35  
The signalling link between the board and the ATM switch is down.  
Board to the ATM switch connection is down  
AAL5 (ATM signalling protocol) excessive retransmission requests  
LAPD excessive retransmission requests  
ATM Board Framer Looparound Test (#1260)  
This test is destructive.  
NOTE:  
This test can be run on the standby PNC only if the board is busied out.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-174  
This test places the ATM circuit pack in ATM framer looparound mode. Once the  
board receives this message, it creates a dummy virtual circuit that originates  
and ends on the same board, without leaving the board. This test verifies both  
the TDM path and the Packet Path. If the TDM test path passes, then the packet  
path is tested. Definitions of each test path are:  
— The circuit (TDM) path: one of the tone generators sends a bit pattern  
through a TDM bus time slot to the ATM framer. The pattern is converted  
into ATM cells and looped back to the ATM-EI board, which converts the  
cell back into the bit pattern and puts it on a pre-determined time slot. A  
tone detector tests for the bit pattern and reports the test result. This test  
verifies that a large portion of the ATM-EIs circuit paths are functioning  
correctly. Figure 3-5 shows a diagram of the test.  
ATM  
circuit  
pack  
ATM  
framer  
looped  
TDM bus  
(PPN)  
Tone clock  
Tone detector  
Packet  
Interface  
Packet bus  
(PPN)  
PNC mode  
iodftone AWF 040699  
Figure 3-5. ATM Board Framer Looparound Test (#1260)  
— Packet path: the Packet Interface circuit pack sends packet data to the  
ATM framer interface, where it is mapped into ATM cells and then looped  
around internally. The cells are converted back to packet data after it has  
been looped. This portion of the test verifies correct operation of the  
ATM-EI’s Packet bus interface and a large portion of the ATM-EI's packet  
paths. Figure 3-6 shows the packet switched signal path for the ATM  
circuit pack.  
This test verifies the operation of a large portion of the ATM-EI circuit and  
packet paths, but does not verify the optical portion of the lightwave  
transceiver. If this test passes, the ATM-EI circuit pack is functioning  
correctly, but faults may exist in the lightwave transceiver. If the test fails,  
the fault may lie on the board. After the test results are reported, the ATM  
framer is taken out of loopback.  
NOTE:  
This test may be run on active or standby ATM-EIs, but it is not  
allowed if an ATM-EI is the Expansion Archangel.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-175  
ATM  
circuit  
pack  
TDM bus  
(EPN X)  
Tone clock  
Tone detector  
ATM  
framer  
looped  
PNC mode  
ATM  
circuit  
pack  
ATM  
circuit  
(PPN)  
pack  
Packet bus  
ATM  
expansion  
archangel  
Packet  
interface  
ATM  
switch  
Packet bus  
(EPN X)  
PNC mode  
PNC mode  
iodfpak AWF 040699  
Figure 3-6. ATM Board Framer Looparound Test (#1260)  
(non-EAA, Packet Path)  
Table 3-73. ATM Board Framer Looparound Test (#1260)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1002  
ABORT  
The system could not allocate timeslots for the test. The system may be  
under heavy traffic conditions or it may have timeslots out of service due  
to TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
retry the command at 1-minute intervals a maximum of 3 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-176  
Table 3-73. ATM Board Framer Looparound Test (#1260) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system  
may be oversized for the number of Tone Detectors present or some  
Tone Detectors may be out of service.  
1. Resolve any TTR-LEV errors. Even if there are no TTR-LEV errors,  
there may not be a Tone Detector available on the network that  
contains the circuit pack being tested. Verify that there is at least one  
Tone Detector on this network. If there is not at least one Tone  
Detector, this test always aborts for this ATM-EI board. This will not  
harm the system.  
NOTE:  
DEFINITY Systems require that Tone Clock circuit packs (TN2182)  
must be of vintage “B” or newer. If older Tone Detector circuit  
packs are installed in the system, this test always aborts with this  
abort code.  
2. Resolve any TONE-PT errors.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 3 times.  
1015  
1031  
ABORT  
ABORT  
The ATM-EI circuit pack has not been busied out.  
1. Busyout the ATM-Expansion Interface circuit pack, then repeat the  
test board UUCSS long command.  
If the ATM Expansion Interface circuit pack is in an EPN and is on the  
active PNC, this test cannot be executed.  
1. If PNC Duplication is enabled, attempt to make the standby PNC  
active with the reset pnc interchange command.  
2. If the PNC Interchange is successful, rerun the test.  
The ATM-EI circuit pack is not present.  
1033  
1139  
ABORT  
ABORT  
1. Issue the list atm-pnc command to verify that switch recognizes the  
circuit pack.  
2. Retry the command.  
The packet bus in the EPN where this ATM-EI board is located has a  
major alarm against it. This test needs to use the alarmed port network’s  
Packet Bus.  
1. Resolve any PKT-BUS problems.  
2. Retry the command.  
1141  
ABORT  
The Packet Interface circuit pack is out of service.  
1. Resolve any PKT-INTF problems.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-177  
Table 3-73. ATM Board Framer Looparound Test (#1260) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1144  
ABORT  
The Packet Bus in the PPN has a major alarm against it. This test needs  
to use the alarmed PPN packet bus.  
1. Resolve any PKT-BUS problems.  
2. Retry the command.  
1394  
ABORT  
The ATM-EI board is out of service and the test cannot be run. This  
condition is due to a change in the ATM-EI board’s ability to  
communicate with the ATM switch.  
1. Run Test #241. If it does not pass, refer to repair procedures for  
‘‘Expansion Interface 2-way Transmission Test (#241)’’.  
1395  
ABORT  
This test cannot be run on an ATM-EI circuit pack if it is part of the B-side  
PNC and duplicated PNC is not enabled.  
1. If this test needs to run on this ATM-EI circuit pack, enable PNC  
duplication with the change system-parameters duplication  
command.  
2. Prevent the system from doing a PNC interchange by executing the  
set PNC lock command.  
3. Repeat this test.  
1407  
ABORT  
This test cannot be run on an ATM-EI board that is on the active PNC  
because it cannot be busied out. This error code indicates that PNC  
duplication is enabled.  
1. Attempt to perform a PNC interchange with the reset pnc  
interchange command.  
2. If the PNC interchange is successful, busy out the original  
ATM-Expansion Interface circuit pack with the busyout board  
UUCSS (address of the original ATM-EI board) command.  
3. Retry the command.  
2000  
2060  
ABORT  
ABORT  
Response to the test was not received in the allowable time period.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
The link on the packet bus being used to perform the test has failed.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
2. If the test continues to abort, resolve any PKT-INTF errors.  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
2100  
2500  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-178  
Table 3-73. ATM Board Framer Looparound Test (#1260) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
FAIL  
The test did not detect the test tone through the looparound connection.  
NOTE:  
The packet portion of this test was not run since the circuit portion  
failed.  
1. Test the active Tone/Clock (test tone-clock UUCSS) on the PN that  
contains the defective ATM-EI circuit pack to verify that dial tone is  
being supplied.  
2. If the Tone/Clock is healthy, test the ATM-EI circuit pack (test board  
UUCSS long).  
3. If this test continues to fail, replace the ATM-EI circuit pack or  
transceiver.  
4. Test the new ATM-EI circuit pack (test board UUCSS long).  
2
FAIL  
The test tone was transmitted and detected correctly, but the correct  
data packet was not detected by the Packet Interface circuit pack.  
1. Test the Packet Interface circuit pack to verify that it is functioning  
properly. If any tests fail, investigate those tests and repair the  
Packet Interface circuit pack.  
2. If the Packet Interface circuit pack is OK, resolve any DS1 CONV-BD  
alarms or errors (if so equipped).  
3. Test the ATM-EI circuit pack (test board UUCSS long).  
4. If this test continues to fail, replace the ATM-EI board.  
5. Test the new ATM-EI circuit pack (test board UUCSS long).  
3
4
FAIL  
FAIL  
The test tone was transmitted correctly, but the returned tone was  
distorted.  
1. If the Tone/Clock is healthy, test the ATM-EI circuit pack (test board  
UUCSS long).  
2. If this test continues to fail, replace the ATM-EI circuit pack.  
3. Test the new ATM-EI circuit pack (test board UUCSS long).  
Unable to create loop for TDM path for this test.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
2. If this test continues to fail, replace the ATM-EI circuit pack.  
3. Test the new ATM-EI circuit pack (test board UUCSS long).  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-179  
Table 3-73. ATM Board Framer Looparound Test (#1260) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
5
FAIL  
Unable to create loop for packet path for this test.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
2. If this test continues to fail, replace the ATM-EI circuit pack.  
3. Test the new ATM-EI circuit pack (test board UUCSS long).  
A previously-established looparound was not released.  
1. Issue the reset board UUCSS command.  
6
FAIL  
2. Retry the command at 1-minute intervals a maximum of 3 times.  
3. If this test continues to fail, replace the ATM-EI circuit pack.  
4. Test the new ATM-EI circuit pack (test board UUCSS long).  
The ATM-EI board is functioning properly, however this test does not  
PASS  
verify that the optical portion of the lightwave transceiver is functioning.  
0
NO  
No board was detected by the test.  
BOARD  
1. Resolve either wrong board (Error 125) or no board (Error 131)  
issues, if applicable.  
2. Check that the board is properly translated and inserted. If so, check  
for hyperactivity (Error 1538). If hyperactive, use the reset board  
UUCSS command.  
3. Run the test again. If it fails, the NCE chip on board may be bad.  
Replace the board and retest.  
ATM Board Time Of Day Update (#1261)  
This test is non-destructive. The ATM circuit pack requires a reference time to do  
SDH/SONET performance monitoring. This test updates the system time to the  
board and synchronizes the board with the DEFINITY system clock during  
initialization, scheduled maintenance, and craft long test.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-180  
Table 3-74. ATM Board Time Of Day Update (#1261)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2031  
FAIL  
The attempt to send the message to the ATM-EI circuit pack was not  
successful.  
2500  
FAIL  
Did not send the time of day information to the board.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
The ATM-EI circuit pack is successfully updated with system time.  
PASS  
1. If the status port-network command still indicates that this link is  
down, it is possible that one or both of the ATM-EI circuit packs have  
been busied out.  
2. If the link still does not come up, reset one or both ATM-EI circuit  
packs on the link.  
0
NO  
No board detected.  
BOARD  
1. Resolve either wrong board (Error 125) or no board (Error 131)  
issues, if applicable.  
2. Check that the board is properly translated and inserted. If so, check  
for hyperactivity (Error 1538). If hyperactive, use the reset board  
UUCSS command.  
3. Run the test again. If it fails, the NCE chip on the circuit pack may be  
bad. Replace the pack and retest.  
ATM Board Reset (#1256)  
This test is destructive. If the ATM-EI board is in the PPN or is a standby in the  
EPN, the reset is done through the SAKI reset interface. If the ATM-EI is an  
Expansion Arch Angel (active ATM-EI board in the EPN) a special message is  
sent to the board over the EAL if the EAL is present.  
Table 3-75. ATM Board Reset (#1256)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1386  
ABORT  
No Active EAL to the board. This error applies only if the board under  
test is in EPN. Check the error logs for SYS-LINK errors against the port  
network in which the ATM-EI is residing and take appropriate diagnostic  
action for the SYS-LINK.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-181  
Table 3-75. ATM Board Reset (#1256) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1015  
ABORT  
This test cannot be run because the ATM-TRK circuit pack has not been  
busied out.  
1. Busyout the ATM circuit pack, then repeat the test board UUCSS  
long command.  
1407  
None  
ABORT  
ABORT  
1. Perform a PNC Interchange  
2. Try to reset the board again.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort escalate the problem.  
Did not receive the SANITY response in the given time.  
2000  
ABORT  
1. Wait for 5 minutes and see if board is visible to the system by using  
list config all command.  
2. If the board is visible, run the test again. If same abort code results,  
escalate the problem.  
3. If the board is not visible to the system via list config all command,  
re-seat the board.  
4. If the board is still not recognized by the system, replace the board.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
2100  
2500  
ABORT  
ABORT  
1. Try to reset the board again.  
1
2
FAIL  
FAIL  
The circuit pack failed to reset  
The circuit pack failed to restart.  
1. Execute command again.  
2. If the problem persists, replace the circuit pack.  
The ATM-EI circuit pack is successfully reset.  
PASS  
1. If the status port-network command still indicates that this link is  
down, it is possible that one or both of the ATM-EI circuit packs are  
busied out.  
2. If the links do not come up after reset, review the error logs and take  
appropriate diagnostic action.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-182  
ATM Cross Talk Test (#1298)  
This test is non-destructive. The ATM board Cross Talk test verifies that the  
selected TDM bus time slot never crosses over to time slots reserved for other  
connections. The test also checks for cross connections, where the board talks  
to time slots other than those specified. Since this test uses many system  
resources (TDM time slots, tone generator, tone detector, and others), it runs as a  
part of demand test only.  
This test fails if either the TDM programmable logic and/or the interface to the  
DSP is not operating properly. Failure of these components may result in one-way  
or noisy connections. Refer to Figure 3-7 for a schematic of this test.  
NOTE:  
Note: This test takes approximately 12 minutes and applies only to TN2305  
and TN2306 circuit packs.  
TDM bus  
(PN X)  
ATM  
circuit  
pack  
Tone detector  
DSP Talker  
PNC mode  
iodfatcr AWF 040699  
Figure 3-7. ATM Cross Talk Test #1298 schematic  
Table 3-76. ATM Crosstalk Test (#1298)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5  
times.  
1002  
ABORT  
The system could not allocate time slots for the test. The system may  
be under heavy traffic conditions or it may have time slots  
out-of-service due to TDM-Bus errors. Refer to TDM-BUS to diagnose  
these errors.  
1. If system has no TDM-Bus errors and is not handling heavy  
traffic, repeat test at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-183  
Table 3-76. ATM Crosstalk Test (#1298) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system  
may be oversized for the number of tone detectors present or some  
tone detectors may be out-of-service.  
1. Resolve any TTR-LEV errors in the Error Log.  
2. Resolve any TONE-PT errors in the Error Log.  
3. If neither condition exists, retry the test at 1-minute intervals for a  
maximum of 5 times.  
2000  
2100  
ABORT  
ABORT  
Response to the test was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5  
times.  
1962  
2302  
ABORT  
ABORT  
All the TALKER DSPs are busy (an unlikely event).  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
Inconsistent uplink message from the ATM-EI board. This is a very  
unlikely event.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
The circuit pack in this location is not a TN230X.  
2752  
ABORT  
FAIL  
1-8,  
None  
The board is writing to unauthorized TDM time slots. The error code  
indicates the number of faulted TALKER DSPs.  
1. Retry the command a maximum of 3 times.  
2. If the failure persists, replace the circuit pack.  
1-8  
PASS  
The board is not talking to unauthorized time slots on the TDM Bus.  
The error code indicates the number of TALKER DSPs that were  
tested.  
ATM Board DSP Test (#1293)  
This test is non-destructive and is designed to test the board’s interface to the  
TDM bus and the functions of all 24 on-board DSPs (Digital Signal Processors).  
There are three functional types of DSPs:  
■
■
■
talkers - put data on the TDM bus  
listeners - take data off the TDM bus  
echo cancelers - as implied  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-184  
Listener and echo cancelers are tightly coupled because firmware allocates sets  
of DSPs. Since there are a total of 24 DSPs on the board, there may be up to 8  
triplets allocated.  
If the test fails for all DSPs, a MAJOR alarm is raised against the board. If the test  
fails for one or more DSPs, a MINOR alarm is raised. If a DSP is “busy,” the test  
for that particular DSP is considered passed. The test aborts if the system  
resources (for example, the TDM time slots, tone generator, and others) are not  
available.  
This test applies to TN2305 and TN2306 ATM-EIs, both active and standby, and  
is run as part of craft short and long testing, periodic, scheduled, initialization,  
and error analysis testing. Refer to Figure 3-8 for a diagram of this looparound  
test.  
TDM bus  
ATM  
(PN X)  
circuit  
pack  
Tone clock  
DSP listener  
CCMS  
CCMS  
DSP echo  
Tone detector  
DSP talker  
iodfatmd AWF 040699  
Figure 3-8. ATM Board DSP Test (#1293)  
Table 3-77. ATM Board DSP Test (#1293)  
Test  
Error Code  
Result  
Description/ Recommendation  
1002  
ABORT  
The system could not allocate time slots for the test. The system  
may be under heavy traffic conditions or it may have time slots  
out of service due to TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy  
traffic, retry the command at 1-minute intervals a maximum of  
3 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-185  
Table 3-77. ATM Board DSP Test (#1293) — Continued  
Test  
Error Code  
Result  
Description/ Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The  
system may be oversized for the number of tone detectors  
present, or some tone detectors may be out of service.  
1. Resolve any TTR-LEV errors.  
Even if there are no TTR-LEV errors, there may not be a tone  
detector available on the network that contains the circuit  
pack being tested. Verify that there is at least one tone  
detector on the network. If not, this test always aborts for this  
ATM-EI circuit pack and does not harm the system.  
2. Resolve any TONE-PT errors.  
3. If neither condition exists, retry the command at 1-minute  
intervals a maximum of 3 times.  
1962  
2000  
ABORT  
ABORT  
All DSPs are busy (an unlikely event).  
1. Retry the command at 1-minute intervals a maximum of 3  
times.  
Response to the test was not received within the allowable time  
period for some of the DSPs.  
1. If the board is in standby, reset the board and run the test  
again.  
2. Look into the Error Log for Error Type 1218 (bad DSP). If  
Error Type 1218 is not logged against this board, run the  
DSP test again and see if the error persists.  
2100  
2302  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this  
test.  
Inconsistent uplink message from the ATM-EI board (an unlikely  
event).  
1. Retry the command at 1-minute intervals a maximum of 3  
times.  
2500  
2752  
ABORT  
ABORT  
Internal system error  
The circuit pack in this location is not a TN230X.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-EI (Expansion Interface Circuit Pack)  
3-186  
Table 3-77. ATM Board DSP Test (#1293) — Continued  
Test  
Error Code  
Result  
Description/ Recommendation  
XYZ  
FAIL  
A device on the circuit pack is failing. There is at least one bad  
DSP on the board. Values are as follows:  
■ The X value indicates the number of talker DSPs  
■ Y indicates the number of listener DSPs  
■ Z indicates the number of Echo Canceler DSPs that have  
failed the test.  
1. Run the tests for the active Tone-Clock on the PN that  
contains the indicted ATM-EI circuit pack to verify that  
dial-tone is supplied.  
2. If the tone-clock is healthy, repeat the short test on the  
ATM-EI board.  
3. If this test continues to fail, replace the ATM-EI circuit pack.  
XYZ  
PASS  
The test passed for some or all DSPs depending on XYZ values.  
XYZ indicates the number of talker, listener and echo-canceler  
DSPs for which the test passed, respectively. In the DSPs that  
passed the test, the test tone was correctly detected by the DSP  
Listener and by tone-detector for the DSP Talkers on both  
busses, and the Echo Canceler DSPs are working properly.  
0
NO  
No board was detected by the test.  
BOARD  
1. Check the Error Log for wrong board (Error Type 125) or no  
board (Error Type 131). Resolve either of these issues, if  
applicable.  
2. Check that the board is properly translated and inserted. If  
so, check for hyperactivity (Error Type 1538). If hyperactive,  
use the reset board UUCSS command.  
3. Run the test again. If it fails, the circuit pack may be bad.  
Replace the circuit pack and retest.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
ATM-INTF (TN2305/6)  
3
3-187  
ATM-INTF (TN2305/6)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
ATM-INTF  
WARNING  
test board UUCSSpp  
ATM interface board  
The TN2305/6 is recognized by the system as an ATM Interface board  
(ATM-INTF) if it has not been assigned a personality through the add atm-pnc  
command or add atm trunk command. ATM-INTF does not have a maintenance  
strategy associated with it, although the Control Channel test can be run on  
demand by using the test board command, and the board can be reset by using  
the reset board command. The board is visible through the list config and  
change circuit-pack commands.  
The circuit packs listed in Table 3-78 are ATM-EI boards if they are administered  
to serve the ATM Port Network Connectivity (ATM-PNC).  
Table 3-78. ATM-EI circuit packs for ATM-PNC  
Echo  
Circuit pack  
TN2305  
TN2306  
Fiber  
Multi mode  
Single mode  
cancellation  
Release  
7.1  
Y
Y
7.1  
NOTE:  
Always replace an ATM-EI circuit pack with the same type.  
LED states  
The ATM-INTF circuit pack has the standard red, green and yellow LEDs. The red  
and green LEDs have the traditional use: red indicates an alarm condition, green  
means maintenance testing in progress. The yellow LED is not used. The  
possible LED states are listed below:  
LED  
Condition  
LED  
Red  
Board is not healthy  
Solid on never off  
Red  
Board is in the processes of booting  
Red: solid on  
Green  
Green: 200 ms on 200 ms off  
Green  
Maintenance is running tests on the  
board  
Solid on (off when  
maintenance completed)  
Yellow  
Yellow  
Fiber LOS  
100 ms on, 100ms off  
500 ms on, 500 ms off  
Signal to the ATM switch is down  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
ATM-INTF (TN2305/6)  
3
3-188  
Error Log Entries and Test to Clear Values  
Table 3-79. ATM-INTF Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Test to Clear Value  
Associated Test  
None  
23(a)  
0
WAR  
MIN  
OFF  
ON  
125(b)  
217(c)  
None  
0
None  
WAR  
OFF  
Notes:  
a. Error Type 23: ATM Expansion Interface circuit pack is administered  
through a change circuit-pack command, but has not been inserted into  
the system. Insert the circuit pack.  
b. Error Type 125: A wrong circuit pack is located in the slot where this circuit  
pack is logically administered. To resolve this problem, either remove the  
wrong circuit pack or insert the logically administered circuit pack.  
c. Error Type 217: The ATM circuit pack is physically present but has not  
been given a personality. Remove the circuit pack or administer it using  
the add atm pnc command or add atm trunk command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
ATM-INTF (TN2305/6)  
3
3-189  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Failure of this test is not logged in the Error Log.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Control Channel Loop Around Test (#52)  
X
X
N
1. D = Destructive, ND = Non-destructive  
)
Control Channel Loop-Around Test (#52)  
This test is non-destructive. This test queries the circuit pack for its circuit pack  
code and vintage and verifies its records.  
Table 3-80. TEST #52 Control Channel Loop-Around Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
2100  
2500  
ABORT  
ABORT  
System resources required to run this test are not available.  
Internal system error  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
The circuit pack failed to return the circuit pack code or vintage.  
1. Retry the command a few times for a maximum of 5 times.  
2. If the problem continues to fail, reset the circuit pack.  
3. Retry the command a few times for a maximum of 5 times.  
Communication with this circuit pack is successful.  
This is normal if the test is being done when:  
FAIL  
PASS  
Any  
NO  
BOARD  
■ the board is not physically in the system.  
■ the system is booting up.  
Otherwise, there is some inconsistency in the data kept in the system.  
1. Verify that the board is physically in the system.  
2. Verify that the system is not in the process of booting up.  
3. Retry the command at 1-minute intervals for a maximum of 5 times.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-NTWK (ATM Network Error)  
3-190  
ATM-NTWK (ATM Network Error)  
MO Name  
(in Alarm  
Log)  
Physical Name in  
Error Logs1  
Alarm Level Full Name of MO  
WARNING ATM Network Error  
ATM-NTWK  
ATUUP  
1. AT indicates it is an ATM switch related address, UU is the connection number. The  
connection number can be converted into a board location by the command display atm  
pnc UU, which shows the translations for the board that reported the ATM network error. P  
indicates if the ATM-EI board (reporting the ATM network error) is the A side or the B side  
of the PNC. If the system is simplex, only A is valid.  
In the ATM PNC configuration, the proprietary Center Stage Switch (CSS) is  
replaced by the ATM network. Since the CSS switch nodes are replaced by the  
ATM network in the ATM PNC configuration, the SNI boards are no longer  
needed. In place of SNI board, the ATM EI boards are connected to an ATM  
switch port over a fiber optic cable. The port on the ATM switch is under the  
control of ATM switch maintenance software. Refer to Figure 1-30 in the ‘‘ATM  
Tips’’ section in Chapter 1 for a schematic of these connections.  
An error against this MO indicates a problem in the ATM network (including the  
ATM switch) that is affecting the service quality. These error events are reported  
by the ATM network to the ATM EI board or are detected by the ATM EI board.  
Since these errors are not related to the ATM EI board, these errors are not  
reported against the ATM-EI Maintenance Object. However, some of these errors  
invoke alarms that require action by DEFINITY maintenance, while other log-only  
errors require no action.  
Error Codes and Aux Data values  
The Cause Code/Error Type information is shown inTable 3-81. These are the  
possible errors that can be logged against the ATM-NTWK MO.  
If the ATM-NTWK Maintenance Object receives more than 6 errors, the most  
recent errors are discarded.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-NTWK (ATM Network Error)  
3-191  
Table 3-81. Error Codes and Aux Data values ATM-NTWK  
Cause Code/  
Error Type  
Aux  
Data  
Cause Codes Description  
NORMAL EVENTS  
0
1
(a)  
(a)  
Network unreachable  
Unallocated (unassigned) number. This cause indicates that the  
called party cannot be reached because, although the number is in a  
valid format, it is not currently assigned (allocated).  
2
(a)  
No route to specified transit network. This cause indicates that the  
equipment sending this cause has received a request to route the call  
through a particular network which it does not recognize, either  
because the transit network does not exist or because that particular  
transit network does not serve the equipment which is sending this  
cause. This cause is supported on a network-dependent basis.  
3
(a)  
No route to destination. This cause indicates that the called party  
cannot be reached because the network through which the call has  
been routed does not serve the destination desired. This cause is  
supported on a network-dependent basis.  
10  
16  
(a)  
(a)  
VPCI/VCI unacceptable. This cause indicates that the virtual channel  
most recently identified is not acceptable to the sending entity for use  
in this call.  
Normal call clearing. This cause indicates that the call is being  
cleared because one of the users involved in the call has requested  
that the call be cleared. Under normal situations, the source of this  
cause is not the network.  
17  
(a)  
User busy. This cause indicates that the called party is unable to  
accept another call because the user busy condition has been  
encountered. This cause value may be generated by the called user  
or by the network.  
18  
21  
(a)  
(a)  
No user responding. This cause is used when a called party does not  
respond to a call establishment message with a connect indication  
within the prescribed period of time allocated.  
Call rejected. This cause indicates that the equipment sending this  
cause does not wish to accept this call, although it could have  
accepted the call because the equipment sending this cause is  
neither busy nor incompatible.  
NOTE:  
If the call was rejected by the far-end ATM-EI board, there may  
also be additional information about this rejection in an ATM-EI  
error log entry. Look for and ATM-EI error with an Error Type  
between 1104 and 1119 inclusive, with approximately the same  
time stamp as this error.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-NTWK (ATM Network Error)  
3-192  
Table 3-81. Error Codes and Aux Data values ATM-NTWK — Continued  
Cause Code/  
Error Type  
Aux  
Data  
Cause Codes Description  
22  
(a)  
Number changed. This cause is returned to a calling party when the  
called party number indicated by the calling user is no longer  
assigned. The new called party number may optionally be included in  
the diagnostic field. If a network does not support this capability,  
cause number 1 “unassigned (unallocated) number” is used.  
23  
27  
(a)  
(a)  
User rejects all calls with calling line identification restriction (CLIR).  
This cause is returned by the called party when the call is offered  
without calling party number information and the called party requires  
this information.  
Destination out of order. This cause indicates that the destination  
indicated by the user cannot be reached because the interface to the  
destination is not functioning correctly. The term “not functioning  
correctly” indicates that a signalling message was unable to be  
delivered to the remote user; for example, a physical layer or SAAL  
failure at the remote user or user equipment off-line.  
28  
30  
(a)  
(a)  
Invalid number format (address incomplete). This cause indicates that  
the called user cannot be reached because the called party number  
is not in a valid format or is not complete.  
Response to STATUS ENQUIRY. This cause is included in the  
STATUS message when the reason for generating the STATUS  
message was the prior receipt of a STATUS ENQUIRY message.  
31  
32  
(a)  
(a)  
Normal, unspecified. This cause is used to report a normal event only  
when no other cause in the normal class applies.  
DTL transit not-my-node ID  
RESOURCE UNAVAILABLE  
35  
(a)  
Requested VPCI/VCI not available. This cause indicates that the  
requested VPCI/VCI is not available. This can be caused by  
mismatched VCI ranges on different ATM switches.  
36  
37  
38  
(a)  
(a)  
(a)  
VPCI/VCI assignment failure  
User Cell Rate not available  
Network out of order. This cause indicates that the network is not  
functioning correctly and that the condition is likely to last a relatively  
long period of time; for example, immediately re-attempting the call is  
not likely to be successful.  
41  
(a)  
Temporary failure. This cause indicates that the network is not  
functioning correctly and that the condition is not likely to last a long  
period of time; for example, the user may wish to try another call  
attempt immediately.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-NTWK (ATM Network Error)  
3-193  
Table 3-81. Error Codes and Aux Data values ATM-NTWK — Continued  
Cause Code/  
Error Type  
Aux  
Data  
Cause Codes Description  
43  
(a)  
Access information discarded. This cause indicates that the network  
could not deliver access information to the remote user as requested;  
that is, ATM adaptation layer parameters, Broadband low layer  
information, Broadband high layer information, or sub-address as  
indicated in the diagnostic.  
45  
47  
(a)  
(a)  
No VPCI/VCI available. This cause indicates that there is no  
appropriate VPCI/VCI presently available to handle the call.  
Resource unavailable, unspecified. This cause is used to report a  
resource unavailable event only when no other cause in the resource  
unavailable class applies.  
SERVICE OR OPTION UNAVAILABLE  
49  
51  
57  
(a)  
(a)  
(a)  
Quality of Service unavailable. This cause is used to report that the  
requested Quality of Service cannot be provided.  
User cell rate not available. This cause is used to report that the  
requested ATM Traffic Descriptor is unobtainable.  
Bearer capability not authorized. This cause indicates that the user  
has requested a bearer capability which is implemented by the  
equipment which generated this cause but the user is not authorized  
to use.  
58  
63  
65  
73  
78  
(a)  
(a)  
(a)  
(a)  
(a)  
Bearer capability not presently available. This cause indicates that the  
user requested a bearer capability implemented by the equipment  
that generated the cause but is not available at this time.  
Service or option not available, unspecified. This cause is used to  
report a service or option not available event only when no other  
cause in the service or option not available class applies.  
Bearer capability not implemented. This cause indicates that the  
equipment sending this cause does not support the bearer capability  
requested.  
Unsupported combination of traffic parameters. This cause indicates  
that the combination of traffic parameters contained in the ATM traffic  
descriptor information element is not supported.  
AAL parameters cannot be supported.  
INVALID MESSAGES  
81  
82  
(a)  
(a)  
Invalid call reference value. This cause indicates that the equipment  
sending this cause has received a message with a call reference  
which is not currently in use on the user-network interface.  
Identified channel does not exist. This cause indicates that the  
equipment sending this cause has received a request to use a  
channel not activated on the interface for a call.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-NTWK (ATM Network Error)  
3-194  
Table 3-81. Error Codes and Aux Data values ATM-NTWK — Continued  
Cause Code/  
Error Type  
Aux  
Data  
Cause Codes Description  
88  
(a)  
Incompatible destination. This cause indicates that the equipment  
sending this cause has received a request to establish a call which  
has Broadband low layer information, Broadband high layer  
information, or other compatibility attributes which cannot be  
accommodated.  
89  
(a)  
Invalid endpoint reference value. This cause indicates that the  
equipment sending this cause has received a message with an  
endpoint reference that is currently not in use on the user-network  
interface.  
91  
92  
(a)  
(a)  
Invalid transit network selection. This cause indicates that a transit  
network identification was received in an incorrect format as defined  
in Annex D.  
Too many pending add party requests. This cause indicates a  
temporary condition when the calling party sends an add party  
message, but the network is unable to accept another add party  
message because its queues are full.  
93  
(a)  
AAL parameters cannot be supported. This cause indicates that the  
equipment sending this cause has received a request to establish a  
call with ATM adaptation layer parameters that cannot be  
accommodated.  
PROTOCOL ERROR  
96  
(a)  
Mandatory information element is missing. This cause indicates that  
the equipment sending this cause has received a message that is  
missing an information element.  
97  
(a)  
Message type non-existent or not implemented. This cause indicates  
that the equipment sending this cause has received a message with a  
message type it does not recognize either because this is a message  
not defined or defined but not implemented by the equipment sending  
this cause.  
99  
(a)  
Information element non-existent or not implemented. This cause  
indicates that the equipment sending this cause has received a  
message that includes information element(s) not recognized  
because the information element identifier(s) are not defined or are  
defined but not implemented by the equipment sending the cause.  
This cause indicates that the information element was discarded.  
However, the information element is not required to be present in the  
message in order for the equipment sending this cause to process the  
message.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-NTWK (ATM Network Error)  
3-195  
Table 3-81. Error Codes and Aux Data values ATM-NTWK — Continued  
Cause Code/  
Error Type  
Aux  
Data  
Cause Codes Description  
100  
(a)  
Invalid information element contents. This cause indicates that the  
equipment sending this cause has received and implemented an  
information element. However, one or more of the fields in the  
information element are coded in such a way that has not been  
implemented by the equipment sending this cause.  
101  
102  
(a)  
(a)  
Message not compatible with call state. This cause indicates receipt  
of a message that is incompatible with the call state.  
Recovery on timer expiration. This cause indicates that a procedure  
has been initiated by the expiration of a timer in association with error  
handling procedures.  
104  
111  
(a)  
(a)  
Incorrect message length  
Protocol error, unspecified. This cause is used to report a protocol  
error event only when no other cause in the protocol error class  
applies.  
257 to 300  
(b)  
(b)  
ATM Impaired Paths  
Examine the error log (‘display errors’), atm setup-events log (‘list measure-  
ments atm svc-setup’), and atm pnc-latency (‘list measurements atm latency’)  
screens to help diagnose the problem -- it is possible the switch is operating  
normally. In this case, you should consider raising the Activation threshold  
and/or increasing the Timeout value on the ATM-RELEATED System Param-  
eters form. (‘change system atm’).  
You can use the list measurements atm svc-setup command to  
provide information about errors associated with connection numbers.  
After entering the above command, make note of the time stamps  
displayed in the list measurements atm setup-events screen. Execute  
the above command periodically and note the time stamps. If the time  
stamps have changed for a particular ‘From Conn’ ‘To Conn’ pair, this  
indicates there are still setup failures/delays for that connection.  
After verifying that all associated ATM end-points are operating  
correctly, and if errors are still occurring, contact your local service  
provider.  
301 (c)  
ANY  
System wide ATM Impaired Paths.  
See the suggestions listed above to trouble shoot these errors.  
Note:  
a. Aux Data values (XX = Port Network, YYY = location code).  
Table 3-82 is a list of UNI 3.1 location codes:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-NTWK (ATM Network Error)  
3-196  
Table 3-82. Location codes from Aux Data values  
Setup  
Add Party  
(Location (Location  
Code)  
Code)  
500  
501  
502  
503  
504  
505  
507  
510  
Location Code Meaning  
User  
0
1
Private network serving the local user  
Public network serving the local user  
Transit network  
2
3
4
Public network serving the remote user  
Private network serving the remote user  
International network  
5
7
10  
Network beyond interworking point  
b. Error Type 257 to 300: These error type numbers are used to determine the  
destination PNC connection number of an ATM Network connection that is  
experiencing an impaired path. The connection number is obtained by subtracting  
256 from number that is displayed in the Error Type field. See the following  
example:  
ERROR TYPE field= 263  
Subtract  
-256  
PNC destination connection # =  
7
The AUX DATA field contains the originating and destination PN number  
(XXYY). Where XX = the originating PN #, and YY = the destination PN # for  
example:  
1. Example AUX DATA = 302  
3 = orig  
2 = dest  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-NTWK (ATM Network Error)  
3-197  
2. Example AUX DATA = 1510  
15 = orig  
10 = dest  
c. Error Type 301: This error indicates that there is a system wide impaired  
path network problem.  
NOTE:  
Under certain circumstances network errors can be against the ATM EI  
board.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM PNC-DUP (ATM PNC Duplication)  
3-198  
ATM PNC-DUP  
(ATM PNC Duplication)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
Run  
Full Name of MO  
PNC-DUP  
NA  
status pnc  
PNC duplication  
The PNC-DUP maintenance object tracks the health of the active and standby  
PNCs, controls planned and spontaneous interchanges, and manages related  
functions such as double call refresh and unrefresh, antithrashing, and so on.  
The main responsibility of PNC-DUP is to recover the system to full service in the  
event of a fault. In the event of multiple faults, PNC-DUP does its best to  
maximize service continuity.  
NOTE:  
PNC-DUP behaves differently when the system is running the ATM PNC  
feature. While not a separate maintenance object, this discussion explains  
the unique behavior of PNC-DUP under the ATM PNC feature.  
In systems with the Critical Reliability option, the following components, which  
together comprise the Port Network Connectivity (PNC), are duplicated:  
■
ATM-Expansion Interface (ATM-EI) circuit packs in the port networks (PNs)  
■
Fiber-optic cables connecting the above circuit packs to the ATM Switch  
Interface Modules  
■
ATM Switch  
Although not part of the PNC, Tone-Clock circuit packs are also duplicated in  
each PN. All systems have one Processor Port Network (PPN). ATM PNC systems  
can have up to 43 EPNs.  
PNC duplication architecture utilizes an active/standby duplication scheme in  
which one complete set of PNC components supports call processing, while the  
duplicate PNC is held in reserve. All calls on the active PNC are simultaneously  
set up, or shadowed, on the standby PNC in order for it to be capable of instantly  
assuming active status when necessary, allowing for interchanges without  
service disruption (in the case of single faults).  
PNC duplication does not introduce any additional types of hardware or  
hardware faults, and there are no tests associated with the PNC-DUP MO.  
Instead, its error log entries contain useful information about the occurrence and  
causes of interchanges in order to facilitate diagnosis of problems, which can  
then be addressed by using the documentation for the individual maintenance  
object involved.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM PNC-DUP (ATM PNC Duplication)  
3-199  
PNC-DUP-related commands  
The following PNC-duplication commands can be useful for troubleshooting.  
status pnc  
Displays information about the operational status of both  
PNCs including state of health, alarms, busyouts and locks,  
and so on.  
reset pnc  
interchange  
Used to initiate a demand PNC interchange. If the standby  
is healthy (state of health indexes all zero), there is no  
effect on service. Otherwise, calls may be dropped.  
set pnc  
Used to lock or unlock the active PNC, preventing  
interchanges. It does not interfere with double call setup.  
busyout pnc  
Removes the standby PNC from service. See also the  
following section on busyout of PNC components.  
Busyouts and PNC-DUP  
Busyout pnc puts the standby PNC in the busyout state. In this condition:  
■
Double call set up is turned off.  
■
The standby PNC is unrefreshed; existing duplicate call connections are  
removed.  
■
PNC interchanges are prevented.  
Upon release, interchanges are re-enabled and a global refresh of double call  
setup on the standby is performed.  
When PNC duplication is in effect:  
■
An active PNC component cannot be busied-out.  
■
A standby PNC component can only be busied-out when the standby  
PNC is first busied-out.  
■
The standby PNC cannot be released unless all standby PNC  
components are released.  
Enabling and removing PNC duplication  
To enable PNC duplication, perform the following sequence of steps:  
1. Enable administration of PNC-DUP on the change system-parameters  
customer-options form.  
2. Fully administer duplicate fiber link connectivity. Verify by list atm-pnc.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM PNC-DUP (ATM PNC Duplication)  
3-200  
3. Activate PNC-DUP through the change system-parameters duplication  
form. This is not allowed if any component of either PNC (A or B) is busied  
out.  
4. The system must insert all connectivity-related components for both  
standby and active PNC, a process that takes up to 5 minutes, depending  
upon circuit pack insertion. The process is complete when the first  
terminal login prompt appears.  
5. The PNC-DUP initialization anti-thrashing timer must expire (this occurs 5  
minutes after completion of board insertion, PNC interchange, or system  
reset of level 2 or higher).  
To disable PNC duplication perform the following sequence of steps:  
1. Verify that the A-PNC is active. A forced interchange may be required.  
2. Busyout the standby PNC (B-PNC).  
3. Turn off the system parameter for PNC-DUP through change  
system-parameters duplication.  
4. Remove the B-PNC connectivity by removing the Board Locations on the  
change fiber form for ATM-PNC.  
5. Remove the B-PNC circuit packs (ATM-EI boards). Use change circuit  
pack UUC.  
6. Disable administration of PNC duplication on the change  
system-parameters customer-options form by changing the PNC  
Duplicationfield to n.  
NOTE:  
Alterations to PNC that involve only the addition of connectivity can be done  
with PNC-DUP operational.  
Alterations requiring the removal of connectivity must be done with  
PNC-DUP removed.  
PNC-DUP must be removed and translations should be saved before  
making any hardware changes.  
Steady State LEDs  
The LEDs of PNC components in a stable duplicated system should appear as  
follows:  
■
The active ATM-EIs in the EPNs are functioning as Archangels. Their  
yellow LED flash pattern is 2 seconds on/200 ms off.  
The EPN standby EIs yellow LEDs are off.  
The PPN active EI yellow LED is on steady.  
The PPN standby EI yellow LED is off.  
■
■
■
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM PNC-DUP (ATM PNC Duplication)  
3-201  
PNC state of health  
PNC-DUP software monitors the health of the two PNCs as determined by their  
state of health (SOH) vectors, and initiates an interchange when the health of the  
active falls below that of the standby (unless prevented from doing so by a PNC  
lock, busyout, or antithrashing mechanism). Potentially service-disrupting faults  
that occur in PNC components are reported to PNC-DUP and incorporated in the  
state of health for the affected PNC. The SOHs of both PNCs are displayed on the  
status pnc screen, as shown in Figure 3-9.  
status pnc  
page 1 of 1  
PORT NETWORK CONNECTIVITY  
Duplicated? yes  
Software Locked? no  
Standby Busied? no  
Standby Refreshed? yes  
Interchange Disabled? no  
A-PNC  
B-PNC  
Mode: active  
Mode: standby  
State of Health: functional  
State of Health: functional  
Inter PN Index: 00.00.00  
Inter PN Index: 00.00.00  
Major Alarms: 0  
Minor Alarms: 0  
Warning Alarms: 0  
Major Alarms: 0  
Minor Alarms: 0  
Warning Alarms: 0  
Figure 3-9. Status PNC screen with standby PNC fully In-Service  
PNC state of health indexes  
The Inter-PN Index form the state of health vector is used to track and compare  
the states of health of both PNCs. The fields making up the indexes are two-digit  
numbers separated by periods (.), with each field representing a different class  
of faults. The fault class fields are arranged in order of decreasing importance  
from left to right. In other words, each field in the index supersedes the following  
fields in determining which PNC is healthiest. A fault class drives an interchange  
only when all of the higher priority fault classes are equal. A zero entry indicates  
no faults present for that class. Increasing numbers indicate increasingly higher  
numbers of faults present in that class.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM PNC-DUP (ATM PNC Duplication)  
3-202  
The Inter-PN Index contains 3 fields (XX.XX.XX). The Inter-PN Index reports faults  
in connectivity between port networks.  
■
■
■
■
■
The meaning of each fault class field is given in Table 3-83.  
A zero entry indicates that there are no faults reported.  
Higher numbers indicate increasing number of faults.  
All zeros indicates perfect state of health.  
Unless the PNCs are locked, the active PNC’s state of health should  
always be equal to or better than the standby’s, otherwise, the system  
performs a spontaneous interchange.  
After a PNC-related alarm is cleared, the system performs a partial refresh of the  
standby PNC. The corresponding fault class field is not updated to reflect the  
improved state of health until the refresh is done. The state of health indexes do  
not agree with the current alarm status during this period.  
Table 3-83. PNC State of Health Fault Classes  
Fault Class  
FC_EAL  
Priority  
Description  
MOs  
1
2
Number of PNs with EALs down  
EXP-PN  
EXP-PN  
FC_PACL  
Number of PNs with LINL, RINL, or EI-SNI  
neighbor link faults  
FC_HW  
3
Number of PNs affected by hardware faults in a  
link having an EI as an endpoint. (Endpoints can  
be determined with list atm-pnc.)  
ATM-EI  
Resolving poor state of health  
When the SoHs for both PNCs are not all zeros (perfect health), use the following  
steps to identify and repair the problem.  
1. Look for PNC component alarms (major or minor) for the PNC side whose  
SOH is not all zero. The standby PNC should be repaired first.  
2. Busy-out the standby PNC.  
3. Follow the appropriate diagnostic and repair procedures for the alarmed  
PNC components just as with a simplex PNC. Both the alarm and error  
logs should be examined to isolate the fault.  
4. Verify that the related PNC SOH is restored to all zeros.  
5. Release the standby PNC.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM PNC-DUP (ATM PNC Duplication)  
3-203  
Refresh and unrefresh of the standby PNC  
In a fully-functional PNC with healthy standby and active sides, the standby PNC  
has a complete set of call connections corresponding to those in the active PNC.  
If, however, the state of health of the standby PNC degrades, a selective  
unrefresh of those connections that utilize the faulted component(s) is performed.  
If the health of the standby PNC improves, a selective refresh of connections on  
the affected route is performed so that call setup is consistent between the active  
PNC and the healthy parts of the standby PNC.  
The Standby Refreshed?field on the status pnc screen does not refer to the  
selective type of refresh. It refers only to a global refresh that is performed when:  
■
■
■
■
The system is initialized and PNC duplication is enabled.  
There has been a spontaneous PNC interchange.  
The standby PNC has been released from busy-out.  
A system reset of level 2 or higher has taken place.  
The refreshed field may display yes when in fact the standby is partially  
unrefreshed. An interchange into an incompletely refreshed standby results in  
dropped calls. This can happen when a more severe fault occurs on the active  
PNC or when reset pnc interchange is used with the override option.  
PNC interchanges  
PNC spontaneous interchanges occur when PNC duplication software  
determines that the State of Health (SOH) of the standby PNC is better than that  
of the active PNC.  
■
PNC-DUP executes a spontaneous interchange in response to a message  
from a PNC component maintenance object indicating that either a fault  
has occurred on the active PNC or a fault has been resolved on the  
standby PNC.  
■
■
The PNC SOH is compared to the standby PNC, and an interchange  
occurs if the state of health of the standby PNC is now better than that of  
the active PNC.  
A corresponding Major or Minor alarm is logged by the reporting MO,  
stimulating an alarm report.  
When the resolution of a fault on the standby renders it more healthy than a  
simultaneously-faulted active PNC, the error message indicates the type and  
location of the improved component.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM PNC-DUP (ATM PNC Duplication)  
3-204  
Once the interchange completes, the failed component is on the standby PNC. A  
demand interchange can be requested in the presence or absence of standby  
PNC faults. The following sequence of actions can be observed during a  
fault-free interchange:  
1. The ATM-Expansion Interfaces currently acting as archangels in the EPNs  
are deactivated as indicated by the yellow LEDs going from flashing to on  
solid.  
2. The PPN ATM-EIs are interchanged, indicated by the new standby ATM-EI  
yellow LED off and the new active ATM-EI yellow LED on steady.  
3. One by one the EPN ATM-EIs are interchanged as indicated by new  
standby ATM-EI yellow LED turning off and the new active ATM-EI yellow  
LED flashing (2 seconds on/200 milliseconds off). At this point the  
interchange is functionally complete.  
Certain conditions may interfere with the normal execution of the interchange:  
1. In a faulted spontaneous interchange, it is possible the EPN/EPNs directly  
affected by the fault will be the last to interchange.  
2. A user directly affected by the single fault instigating a PNC interchange  
can experience a momentary voice path outage during the switch.  
3. If faults exist on both the standby and active PNC, it is possible to have  
some EPNs go out of service while others are returned to service.  
In any multifault situation, rely on status pnc to determine which is the active  
PNC.  
PNC duplication informs Timing Synchronization maintenance when a PNC  
interchange has been completed and indicates which PNC is active. This causes  
Synchronization to audit and ensure that the primary source for synchronization  
of Tone-Clocks in each PN is supplied by a path associated with the active PNC.  
Antithrashing and PNC interchanges  
Following a spontaneous PNC interchange, subsequent PNC interchanges are  
prevented for 5 minutes. This condition is indicated by yin the Interchange  
Disabled?field of the status pnc screen. After 5 minutes, the antithrashing,  
timer expires, interchange decisions are re-enabled, and the field displays n.  
Should a catastrophic failure occur on the active PNC during the period when the  
Interchange Disabled?field is set to “yes,” there will be no spontaneous  
PNC interchange.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM PNC-DUP (ATM PNC Duplication)  
3-205  
Demand PNC interchanges also invoke anti-thrashing, but only for a period of 30  
seconds. During antithrashing mode, demand interchanges are also prevented  
unless the override option is specified.  
!
CAUTION:  
Use of this option may cause a service disruption.  
Repairs on the standby PNC components  
!
CAUTION:  
If there is a TDM-CLK alarm, system timing may be routed through part of  
the standby PNC, and circuit switched data may be affected by the  
following repair procedures. This can happen, for example, when a slave  
tone/clock circuit pack experiences a loss of signal and switches to receive  
timing from the standby ATM-EI. In this case TDM-CLK 2305 error is logged,  
and the clock problem should be addressed first, if possible.  
To repair PNC components in a duplicated PNC proceed as follows:  
1. Most repairs involve fixing a single fault on the standby PNC. Use set pnc  
lock or busy-out pnc to prevent an interchange into the PNC being  
repaired.  
2. If a faulty component exists on the active PNC, this also means that the  
standby PNC is more severely faulted. Normally, the standby PNC is  
repaired first, since it is the most severely impaired.  
To repair the active PNC (standby is already repaired), issue the set pnc  
unlock command, which generates a spontaneous interchange. In a PNC  
demand interchange with reset pnc interchange use the  
override-and-lock qualifier for the active PNC. The override-and-lock  
option ensures that no subsequent interchange can occur during the  
repair of the standby PNC. A demand interchange may not be necessary  
if the following conditions drive a spontaneous interchange:  
■
■
■
The anti-thrashing period from the last interchange has expired.  
The global refresh from releasing the standby PNC has completed.  
The standby PNC State of Health is better than the active PNC.  
At this point, the faulty component is on the standby PNC, and the PNCs  
are locked in their current active/standby state.  
3. Busyout the PNC with the busyout pnc command.  
4. Use fault isolation and component testing procedures for the individual  
PNC components, just as for a simplex PNC. Replacement of components  
does disrupt operation of the active PNC.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM PNC-DUP (ATM PNC Duplication)  
3-206  
5. Once the failed component is replaced, use the status pnc command to  
check the health standby PNC component.  
6. When confident that the problem has been resolved, as indicated by a  
state of health with all zeros, unlock (set pnc unlock) and release  
(release pnc) the PNC. Note that no further PNC interchange is required  
since you can test the standby PNC as thoroughly as the active.  
Interactions: SPE resets and PNC interchanges  
■
■
After a reset system 4 (reboot), the A PNC is always the active.  
A system reset of level 1 (warm), 2 (cold2) or 3 (cold1) does not change  
which PNC is active. If a PNC interchange was in progress when the reset  
took place, the PNC interchange continued until completion.  
■
If a reset system 1 (warm) takes place during a PNC interchange, the  
reset is escalated to level 2 (cold2).  
Fault isolation using Duplicated PNC  
In some cases, PNC duplication can aid in the fault isolation procedure. PNC  
interchanges can be used to help isolate the faulty hardware. Two examples  
demonstrating this technique follow:  
1. There is a fault that can occur in either the PPN ATM-EI or the PKT-INT  
which cannot be readily attributed to one board or the other. If the packet  
bus transceivers on either the PKT-INT or ATM-EI fail, the two boards  
cannot communicate, but it will not be clear which board is at fault. In this  
case, a planned interchange of the PNC can be used to indicate which of  
the two boards.  
— If the interchange cures the problem, the ATM-EI was at fault.  
— If the interchange does not cure the problem, the PKT-INT is  
suspect, provided there are no PKT-BUS faults.  
2. A similar relationship exists for the EPN Archangel (EAA - the active  
ATM-EI) and certain TDM bus problems. If the EAA is unable to  
communicate with a port board over the TDM bus, either the EAA has a  
fault, the port board has a fault, or there is a problem with the TDM bus  
itself. If TDM bus maintenance tests find no problems with the bus, then it  
is either the port board or the EAA. It may be simpler to replace the port  
board than to request a PNC interchange. However, if it is not clear which  
port board may be at fault or maintenance is being performed remotely,  
verify that the EAA is not at fault by executing a PNC interchange. If the  
interchange solves the problem, then the EAA is faulty. If the problem  
persists after the interchange, but TDM bus maintenance finds no  
problem, then the port board is faulty.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM PNC-DUP (ATM PNC Duplication)  
3-207  
Error Log entries  
Whenever a PNC interchange takes place, an error is logged against PNC-DUP  
with a code that conveys information about the cause of the interchange and  
which PNC became active. There are no alarms associated with PNC-DUP  
errors, but there should be an alarm against the PNC component that caused the  
interchange. There are no PNC-DUP test sequences, but status pnc provides  
information regarding the status of the PNCs. The information in Table 3-84 and  
Table 3-85 can help to identify which areas of the Alarm Log to investigate to find  
the source of the problem.  
Table 3-84. Error Code descriptions and Aux Data correlations  
Error  
1
Code  
00000  
1cxpp  
2cxpp  
51000  
52000  
53000  
60801  
60800  
Description  
Aux Data  
None  
Error in generating error code  
Spontaneous Interchange in response to a constraint for A-PNC  
Spontaneous Interchange in response to a constraint for B-PNC  
Spontaneous Interchange at expiration of SOH validation timer  
Spontaneous Interchange upon PNC UNLOCK  
Active PNC  
Active PNC  
Active PNC  
Active PNC  
Active PNC  
Active PNC  
Active PNC  
Spontaneous Interchange at completion of Global Refresh  
PNC Demand Interchange  
PNC Demand Interchange with override  
1. The Aux Data indicates which PNC became active after the PNC interchange: “0” denotes PNC-A;  
“1” denotes PNC-B.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM PNC-DUP (ATM PNC Duplication)  
3-208  
Table 3-85. Error Log Encode Field Decoding  
Field  
Variable Name  
Values  
Description  
c
Alarm Type  
0
1
Alarm retired  
MAJOR or MINOR alarm on any PNC component  
x
0
EAL (Expansion Archangel Link - EXP-PN) carries  
CCMS messages  
Fault class; see  
description for  
contributing MOs  
1
PACL (ATM-EI) carries ATM signaling commands  
from Call Processing to the remote ATM-EI circuit  
packs.  
2
PNC hardware (providing connectivity of PPN or EPN  
to EPN or ATM-EI)  
pp  
Port Network number  
0-43  
0-2 for constraint class (this is an internal number;  
add 1 for external port number)  
Error Log Entries and Test to Clear Values  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Alarm Level  
Test to Clear Value  
18  
None  
busy PNC-DUP  
WARNING  
ON  
release pnc-dup  
NOTE:  
The list config port-network command gives the cabinet number  
associated with a port network.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SGRP (ATM Signaling Group)  
3-209  
ATM-SGRP (ATM Signaling Group)  
MO Name (in  
Alarm Log)  
Initial Command to  
1
Alarm Level  
MINOR  
Run  
Full Name of MO  
ATM-SGRP  
ATM-SGRP  
test sig-group grp#  
test sig-group grp#  
ATM-CES Signaling Group  
ATM-CES Signaling Group  
WARNING  
1. grp# is the signaling group number (1-166); the test sequence can be either short or long.  
This Maintenance Object (ATM-SGRP) applies when there are administered ATM  
signaling groups on the ATM circuit pack.  
Table 3-86 outlines the differences between ATM interface circuit packs:  
Table 3-86. R7 ATM-SGR circuit packs  
Circuit  
pack  
Echo  
cancellation  
Channel types  
Interface  
Fiber  
TN2305  
TN2306  
B and D channels 24 or 32 channel Multimode  
B and D channels 24 or 32 channel Single mode  
Y
Y
The TN2305 and TN2306 ATM Interface circuit boards are referred to as TN230X  
for the remainder of this MO.  
An ATM Signaling Group is a collection of B-channels for which a given ISDN-PRI  
Signaling Channel Port (ATM D-channel) carries signaling information. ATM  
B-channels (ATM-BCH) carry voice or data and are assigned to ISDN trunks. For  
more information see ‘‘ATM-TRK (Circuit Emulation Service Circuit Pack)’’.  
The operation of the entire ATM signaling group depends on several other  
entities:  
■
■
■
the ATM-DCH signaling channel port  
the TN230X Interface circuit pack on which the D-channels reside  
the system link that is carried over the packet bus to the processor  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SGRP (ATM Signaling Group)  
3-210  
When there are problems with ATM-SGRP (ATM signaling group), also  
investigate:  
■
■
■
■
‘‘ATM-DCH (ATM D-Channel Port)’’  
‘‘ATM-BCH (ATM B-Channel Trunk)’’  
SYS-LINK  
PKT-BUS  
Error Log Entries and Test to Clear Values  
Table 3-87. ATM-SGRP Signaling Group Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
0
0
Any  
Any  
test sig-group grp#  
1 (a)  
Any  
None  
18 (b)  
257 (c)  
769 (d)  
MO busied out  
None  
Any  
Any  
test sig-group grp#  
test sig-group grp#  
Primary Signaling Link  
Hardware Check (#636)  
1281 (e)  
Any  
Secondary Signaling Link  
Hardware Check (#639)  
test sig-group grp#  
1793 (f)  
2305 (g)  
Any  
Any  
Layer 2 Status (Test #647)  
WNG  
OFF  
OFF  
test sig-group grp#  
test sig-group grp#  
Remote Layer 3 Query  
(Test #637)  
MINOR  
3585 (h)  
Port  
None  
number  
3840 -  
Port  
None  
3928 (i)  
number  
Notes:  
a. Error Type 1: switch sent a message to the far-end switch or terminal  
adapter, and the far-end did not respond in the allotted time. Possible  
causes include link failure and congestion or outage at the far-end. The  
Aux Data field contains Layer 3 protocol information used by internal  
counters.  
If no other symptoms are present, no action is required. If Layer 3  
communication is down:  
1. Check for alarms and errors against link components  
2. Check out other errors against ATM-SGRP, ATM-TRK, and other  
hardware components on the link.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SGRP (ATM Signaling Group)  
3-211  
There is no test to clear these errors. The error counter is decremented by  
1 every 15 minutes.  
b. Error Type 18: the ATM circuit pack has been busied out (either busyout  
atm sig-grp or busyout board UUCSS).  
1. Release the ATM signaling group (release atm sig-grp) or the  
circuit pack (release board UUCSS).  
c. Error Type 257: the primary signaling channel connection has been lost for  
more than 90 seconds.  
■
■
■
The associated B-channels are placed in the ISDN  
Maintenance/Far-End state.  
The B-channels are not usable for outgoing calls, although  
incoming calls can be accepted.  
The switch automatically attempts to recover the signaling link.  
1. Pay particular attention to the results of Test #636 (Primary  
Signaling Link Hardware Check) in the test sequence.  
■
When the link does recover, the B-channels are negotiated back to  
the In-Service state and their alarms are retired.  
2. When this error occurs, the state of the Signaling Group is changed  
to out-of-service (verify using the status sig-group command).  
d. Error Type 769: signaling link hardware error.  
Service-affecting failures of the hardware used to transport the D-Channel  
are reported to the ATM CES Signaling Group MO. Maintenance logs this  
error, places the D-Channel into the OOS state, and raises a board-level  
alarm. The D-Channel is returned to service and the alarm is retired once  
the hardware failure condition clears.  
e. Error Type 1281: Degraded PVC Alarms indicate that a particular  
Permanent Virtual Circuit, or signaling group, has encountered sufficient  
errors to exceed firmware thresholds. Operations can continue but at a  
lower level of reliability or performance. Firmware filters these alarms so  
that only one is reported active at a given time. The following in-line error is  
considered a Degraded PVC Alarm:  
■
Excessive AAL - The AAL layer is experiencing an excessive  
number of errors in trying to reconstruct Service Data Unit (SDUs).  
Possible causes:  
— Something may be wrong with the ATM switch.  
— The communication paths on the other side of the ATM  
switch may be noisy.  
— The sending node might not be healthy.  
— Could be a problem with congestion on the ATM switch.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SGRP (ATM Signaling Group)  
3-212  
f. Error Type 1793: failure of the Layer 2 Query Test for the primary signaling  
channel.  
■
Excessive AAL - The AAL layer is experiencing an excessive  
number of errors in trying to reconstruct Service Data Unit (SDUs).  
Possible causes:  
— Something may be wrong with the ATM switch.  
— The communication paths on the other side of the ATM  
switch may be noisy.  
— The sending node might not be healthy. It could also be a  
problem with congestion on the ATM switch.  
g. Error Type 2305: the Remote Layer 3 Query Test (#637) failed. A specific  
message was sent to the far-end switch, and it did not respond within the  
allotted time.  
1. Investigate elements of the ATM D-channel(s) (ATM-DCH) for both  
this switch and the Far-end switch.  
If Test #637 fails twice in a row, the B-channels are alarmed and made  
unavailable for outgoing calls (although incoming calls are still accepted).  
When Test #637 succeeds and the Far-end switch starts responding  
properly, the ATM Trunk (B-channels) are placed back into normal  
operation and their alarms retired.  
h. Error Type 3585: A SERV or SERV ACK ISDN D-channel message has  
been received by a non-US-type interface (country option other than 1on  
the DS1 administration form). However, these messages are used only for  
duplex NFAS signaling, which is supported by country protocol 1.  
Thus, there may be a mismatch in administration between the local and  
far-end switches.  
1. Consult with the customer’s network provider to determine whether  
the D-channel is set up correctly on the far-end switch.  
i. Error Type 3840-3928: These error types are used to report certain error  
messages received by the ATM-SGRP Signaling Group for one of its  
associated B-channels. The Aux Data field is the port number of the  
B-channel from which the message was received.  
The error code generated equals 3840+x, where x is a Cause Value  
defined by the ISDN PRI Specification. Note that there is no Test to Clear  
Value for these error types; selected ISDN cause values are placed in the  
log when they are received, but no direct action or alarming is performed  
solely in response to receiving them. They provide added data that may  
prove useful when tracking down obscure networking and routing  
problems. Table 3-88 provides more information about this range of Error  
Codes:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SGRP (ATM Signaling Group)  
3-213  
Table 3-88. Descriptions and repair recommendations (Error Types 3840-3928)  
Error  
Code  
Description  
Recommendation  
3842  
A request has been made  
to use a transit network or  
common carrier that cannot  
be accessed.  
From the circuit pack and port number (in the Aux Data  
field), determine the trunk group against which the error  
was reported.  
1. Check all routing patterns containing this trunk group  
for validity of interexchange carriers requested (IXC  
field).  
3846  
The far-end switch has  
indicated that the  
B-channel (trunk) is not  
acceptable for use in the  
call for which it was  
requested.  
This could indicate  
■ an administration problem (for example, the local  
switch and the far-end switch have different  
B-channels administered)  
■ a normal race condition (for example, the local switch  
has requested use of a B-channel which the far-end  
switch had just reserved for use on another call).  
1. From the circuit pack and port number (in the Aux  
Data field), determine the trunk group against which  
the error was reported.  
2. Issue the status trunk command for the indicated  
trunk.  
3. Refer to Table 3-49 in ‘‘ATM-BCH (ATM B-Channel  
Trunk)’’ for recovery suggestions.  
3858  
3878  
Similar to Error Type 1. The  
switch sent an ISDN  
message to the far-end  
switch or terminal adapter  
which did not respond in  
the allotted time.  
1. Check for alarms and errors against link components  
2. Check out other errors against ‘‘ATM-SGRP (ATM  
Signaling Group)’’, ‘‘ATM-TRK (Circuit Emulation  
Service Circuit Pack)’’, and other hardware  
components on the link.  
The far-end switch has  
indicated that the network  
is not functioning correctly  
and that the condition may  
last a relatively long period  
of time (for example,  
immediately re-attempting  
the call may not be  
successful).  
1. From the circuit pack and port number (in the Aux  
Data field, determine the trunk group against which  
the error was reported.  
2. Consult with the network provider to determine the  
nature and expected duration of the out of service  
condition.  
3. Consider modifying all routing patterns containing  
this trunk group, to route calls around the network  
which is out of service.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SGRP (ATM Signaling Group)  
3-214  
Table 3-88. Descriptions and repair recommendations (Error Types 3840-3928) — Continued  
Error  
Code  
Description  
Recommendation  
3890  
A request to use a network  
service (for example, SDN)  
has been denied.  
This could indicate  
■ a local administration problem  
■ a mismatch between the local administration and that  
Administration somewhere  
on the network has  
of the network provider.  
indicated that the  
1. From the circuit pack and port number (in the Aux  
Data field), determine the trunk group against which  
the error was reported.  
requested service has not  
been subscribed to or  
purchased for this trunk.  
2. Display the trunk group form.  
If the trunk group is Call-by-Call (the Service Type  
field is cbc), check all routing pattern forms  
containing this trunk group to see if the  
Service/Feature fields contain the correct network  
services purchased for this trunk.  
If the trunk group is not Call-by-Call, check that the  
Service Typefield contains the single network  
service purchased for this trunk.  
3. If local administration appears correct, consult with  
the customer and/or the network provider to  
determine the services that the customer has  
subscribed to for this trunk group.  
3892  
3894  
Protocol detail; may offer a  
clue if customer is having  
ISDN calls denied with an  
unexpected intercept tone.  
1. If customer is complaining of unexpected intercept  
tones when accessing ISDN trunks or PRI endpoints  
and no other cause can be found, escalate the  
problem and provide the next tier with this Error Log  
information.  
Protocol detail; may offer a  
clue if customer is having  
ISDN calls denied with an  
unexpected intercept tone.  
1. Eliminate any transitory state mismatch problems  
(test port UUCSSpp for the trunk port shown in the  
Aux Data field). Test #256 (Service State Audit) is the  
important test in the sequence.  
2. If Test #256 passes yet the customer continues to  
complain of unexpected intercept tones when  
accessing ISDN trunks or PRI endpoints and no other  
cause can be found, escalate the problem and  
provide the next tier with this Error Log information.  
3905  
Protocol detail; may offer a  
clue if customer is having  
ISDN calls denied with an  
unexpected intercept tone.  
1. If customer is complaining of unexpected intercept  
tones when accessing ISDN trunks or PRI endpoints  
and no other cause can be found, escalate the  
problem and provide the next tier with this Error Log  
information.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SGRP (ATM Signaling Group)  
3-215  
Table 3-88. Descriptions and repair recommendations (Error Types 3840-3928) — Continued  
Error  
Code  
Description  
Recommendation  
3906  
Protocol detail; may offer a  
clue if customer is having  
ISDN calls denied with an  
unexpected intercept tone.  
1. If customer is complaining of unexpected intercept  
tones when accessing ISDN trunks or PRI endpoints  
and no other cause can be found, escalate to the  
problem and provide the next tier with this Error Log  
information.  
3909  
3928  
A request to use a network  
service has been made,  
but the network has  
rejected the request  
because the requested  
service is not implemented.  
1. Follow the recommendations listed above for Error  
Type 3890.  
A call was denied because  
of a basic incompatibility  
between the type of call  
and either the facilities  
selected by the routing  
pattern or the called user  
itself.  
This error might be helpful as a clue if the customer  
complains of receiving unexpected intercept tone after  
accessing ISDN trunks or PRI endpoints.  
1. Determine the trunk group from the circuit pack and  
port number (in the aux data field)  
2. check the BCC fields of the pertinent routing  
patterns.  
3. Also, investigate whether or not the calling and called  
endpoints are compatible (for example, some ISDN  
switches may not allow a voice station to call a data  
extension).  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Primary Signaling Link Hardware Check, for example, you may also clear errors  
generated from other tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SGRP (ATM Signaling Group)  
3-216  
Table 3-89. System Technician-Demanded Tests: ATM-SGRP  
ShortTest  
Long Test  
Sequence  
1
Order of Investigation  
Primary Signaling Link Hardware Check (#636)  
Layer 2 Status Test (#647)  
Sequence  
D/ND  
ND  
X
X
X
X
X
X
ND  
Remote Layer 3 Query Test (#1291)  
ND  
1. D = Destructive, ND = Non-destructive  
Primary Signaling Link Hardware Check (#636)  
The ATM-SGRP Signaling Group D-Channel port depends on the health of the  
TN230X interface circuit pack on which it resides. This test fails if there are  
problems with either the ATM-DCH (D-channel port) maintenance object or the  
TN230X circuit pack. Investigate the ATM TN230X circuit pack (ATM-TRK)  
anytime there are problems with the ATM D-channel port (ATM-DCH).  
Table 3-90. Primary Signaling Link Hardware Check (#636)  
Test  
Error Code  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
Retry the command at 1-minute intervals a maximum of 5 times.  
8
FAIL  
There is a problem with the ATM TN230X Circuit Pack or the ATM  
Signaling Channel (D-Channel), preventing any ISDN trunk calls until  
the problem is resolved.  
1. Consult the procedures for the TN230X Circuit Pack (ATM-TRK)  
and the ATM D-channel (ATM-DCH).  
PASS  
The basic physical connectivity of the D-channel is intact and  
functional.  
1. Try this test repeatedly to ensure the link is up and to uncover  
any transitory problems.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SGRP (ATM Signaling Group)  
3-217  
Layer 2 Status Test (#647)  
The Layer 2 Status Test checks the layer 2 status of the ATM-SRG Signaling  
Channel (D-channel). This test fails when:  
■
■
■
there is a hardware failure  
there is a facility problem  
the D-channels are not administered correctly  
The Signaling Link Hardware Check (Test #637) and the Remote Layer 3 Query  
Test (#1291) detects most problems caused by hardware failures or incorrect  
administration.  
Table 3-91. TEST #647 Layer 2 Status Query Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1132  
1134  
ABORT  
Internal system error. The port location for the D-channel is not known. This  
condition should not be possible since an administered ATM circuit pack  
must be specified when a Signaling Group is administered:  
1. Retry the command at one minute intervals a maximum of five times.  
ABORT  
Internal system error. The associated ATM circuit pack is not administered.  
This condition should not be possible, since an administered ATM circuit  
pack must be specified when administering a Signaling Group.  
1. Retry the command at one minute intervals a maximum of three times.  
Internal system error  
2500  
1
ABORT  
FAIL  
1. Retry the command at one minute intervals a maximum of five times.  
Layer 2 of the signaling channel is down  
1. Examine the results of the Signaling Test (#636) and follow  
recommendations provided there.  
2. If Test #636 (Primary Signaling Link Hardware Check) passes, the Layer  
2 Query test may still fail if the Signaling Channel at the far end has not  
been administered correctly or if the Signaling Channel has been  
busied out.  
3. Verify that the Signaling Channel (D-channel) at the far end has been  
administered correctly.  
4. Verify that the ATM-DCH port used for the D-channel has not been  
busied out at the far end.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SGRP (ATM Signaling Group)  
3-218  
Table 3-91. TEST #647 Layer 2 Status Query Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The D-Channel is down.  
3
FAIL  
1. Examine the results of the Primary Signaling Link Hardware Check  
(#636) and follow recommendations provided there.  
2. If Test #636 (Primary Signaling Link Hardware Check) passes, the Layer  
2 Query test may still fail if the Signaling Channel at the far end has not  
been administered correctly or if the Signaling Channel has been  
busied out.  
3. Verify that the Signaling Channel (D-channel) at the far end has been  
administered correctly.  
4. Verify that the ATM-DCH port used for the Primary and Secondary  
D-channels has not been busied out at the far end.  
PASS  
The Primary Signaling Channel is up.  
Remote Layer 3 Query (#1291)  
This test queries the far-end switch or terminal adapter to determine if the  
signaling connection is functioning properly at Layer 3. It selects a B-channel in  
the in-service or maintenance service state and sends an ISDN Layer 3 SERVice  
message, which requires a response from the far end (similar to performing Test  
#256 on an ISDN trunk). The test is not performed if there are no B-channels in an  
appropriate ISDN service state (for example, when none are administered or they  
are all out of service).  
NOTE:  
The service state can be displayed by using the status trunk <trunk  
group/trunk member> or status pri-endpoint command.  
As is the case with Test #256 for an ISDN trunk, a PASS only indicates that a  
message was composed and sent to the far-end switch or terminal adapter. The  
ISDN PRI Specification allows up to 2 minutes for a response. Check the Error  
Log for ATM-SGRP errors of type 2305 for evidence of a Remote Layer 3 Query  
failure.  
Test #636 checks the health of the D-channels and ATM Interface Circuit Packs.  
This test goes one step further by checking the communication path from the  
processor, through the TDM/Packet Bus and ATM Interface circuit pack, and on  
to the far-end switch or terminal adapter. A special ISDN message is sent to the  
far-end switch or terminal adapter, which must respond within a specified amount  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SGRP (ATM Signaling Group)  
3-219  
of time. This test is designed to ensure that the communication path between the  
switch and the far-end is up and operational, and that the two endpoints can  
properly exchange ISDN control messages.  
Table 3-92. TEST #1291 Remote Layer 3 Query  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1006  
ABORT  
There are no associated B-channels in an ISDN “in-service” or  
“maintenance” service state. This is a NORMAL ABORT.  
1. Administer or release an ISDN trunk or PRI endpoint before retrying the  
test. For an ATM trunk, use the status trunk grp#/mbr# command to  
verify the ISDN trunk state.  
2. Retry this test when at least one B-channel is in the “in-service” or  
“maintenance” states.  
1113  
2100  
ABORT  
The signaling channel is down. Therefore, no messages can be sent to the  
far-end switch or terminal adapter.  
1. Examine the results of Tests #636 and follow recommendations provided  
there.  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error or administration problem  
2500  
or  
none  
1. Determine if any B-channels are administered.  
2. If there are none, then this is a normal ABORT, since this test cannot run  
unless at least one B-channel is administered.  
3. If at least one B-channels is administered, there is an internal system  
error. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
Internal system error  
1. See description of ABORT with Error Code 2500.  
PASS  
A message was sent to the far-end switch or terminal adapter. The ISDN PRI  
specification allows up to 2 minutes for a reply.  
1. Check the Error Log for ATM-SGRP errors of type 2305 for evidence of a  
Remote Layer 3 Query failure.  
2. If no new errors were logged since this test was run, then this switch and  
the far-end switch can exchange call control messages.  
3. If there is still a problem with a particular ATM trunk, busyout the trunk  
and run the long test sequence, paying particular attention to the results  
of Test #258 (ISDN Test Call).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SYNC (ATM Synchronization)  
3-220  
ATM-SYNC (ATM Synchronization)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
display errors  
Full Name of MO  
ATM-SYNC  
ATM-SYNC  
MINOR  
ATM Synchronization  
ATM Synchronization  
WARNING  
test synchronization  
This section discusses intra-switch synchronization maintenance and the  
hardware and software components that provide a common reference frequency  
for reliable digital communication among the G3r system, the ATM switch, and  
other PBXs, Central Offices (COs) or Customer-Premises Equipment (CPE).  
Circuit packs involved in synchronization include:  
■
■
■
TN768, TN780, or TN2182 Tone/Clock  
TN722, TN767, and TN464 DS1 Interfaces (all suffixes)  
TN2305/6 ATM Expansion Interface (multimode fiber)  
Synchronization is achieved between the Processor Port Network (PPN) and the  
Expansion Port Networks (EPNs) through the ATM port network connectivity (ATM  
PNC) between the networks. Depending on the network synchronization plan  
and the status of synchronization sources, the system timing reference may be:  
■
The clock circuit pack on the ATM switch  
■
A DS1 or UDS1 interface circuit pack-tapped T1 input signal connected to  
the ATM switch clock circuit  
■
An OC-3 interface circuit pack on the ATM switch  
Stratum 4 synchronization extracts timing information directly from  
■
■
■
A DS1 or UDS1 reference  
An OC3 reference  
The ATM switch clock  
For further information about synchronization including network synchronization,  
see AT&T Network and Data Connectivity.  
Stratum 4 Synchronization  
Systems may have primary and secondary synchronization references  
(DS1/UDS1 interface circuit packs or ATM-Switch) when using Stratum 4  
synchronization.  
If the primary synchronization reference in Figure 3-10 is providing a valid timing  
signal, then the flow of system synchronization would travel from the DS1  
interface circuit pack in the EPN to the ATM switch. The primary DS1 interface  
circuit pack pDroowvindloeasd faromtimWiwnwg.Ssoimgannaulaflso.crotmh.eAAll MTManusawlsiStceharcchloAcndkDcoiwrcnluoiatdr.y.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SYNC (ATM Synchronization)  
3-221  
This synchronization source is then distributed to all of its OC3 Interface  
Modules. Each ATM Expansion Interface circuit pack uses the received data  
stream from the ATM switch to generate a timing signal. The Tone-Clock circuit  
packs in the EPNs use this signal to generate timing for all the circuit packs in  
their respective EPNs. All PNs, in the above mentioned scenario are designated  
the slave port networks. The ATM switch is the master that contains the system  
synchronization source. If the primary synchronization reference does not  
provide a valid timing signal, ATM synchronization maintenance infers a switch to  
the secondary reference.  
If the primary synchronization reference is not providing a valid timing signal, the  
system automatically switches to the secondary synchronization reference. If the  
primary synchronization reference is invalid, and if the secondary reference does  
not provide a valid timing signal or is not administered as a synchronization  
reference, the switch infers that the local oscillator of the ATM switch provides the  
system timing source. If the system is using the local oscillator of the ATM switch  
as the system timing source because the primary and secondary references are  
providing invalid timing signals, when either the primary or secondary reference  
becomes valid again, the system switches back to the primary or secondary  
source. When both the primary and secondary source become valid, the system  
switches to the primary source, since the primary source is always preferred over  
the secondary source when both sources are equally healthy.  
Figure 3-10 depicts a simplex ATM PNC with T1/OC3 synchronization reference  
into the ATM switch.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SYNC (ATM Synchronization)  
3-222  
External T1/E1  
primary  
Clock  
External T1/E1  
secondary  
ATM switch fabric  
ATM timing distribution  
Interface  
module  
Interface  
module  
Interface  
module  
ATM PNC  
OC3  
OC3  
DEFINITY  
EPN  
DEFINITY  
PPN  
ATM-EI  
ATM-EI  
Tone clock  
DS1 DS1  
Tone clock  
DS1 DS1  
T1-splitter  
T1-primary  
T1-secondary  
iodfst4 LJK 011998  
Figure 3-10. Stratum 4 synchronization with simplex ATM PNC  
NOTE:  
The TN722 DS1 Interface circuit pack does not provide a synchronization  
reference as reliably as the TN767 or TN464C circuit packs. Therefore,  
administer the TN767 or TN464C circuit packs as the primary or secondary  
sources.  
Stratum 3 Synchronization  
Stratum 3 synchronization is not supported in DEFINITY with ATM PNC.  
Synchronization troubleshooting  
A significant part of the Synchronization Recovery Strategy for a DEFINITY with  
ATM PNC resides in the ATM switch’s clock hardware, firmware, and software.  
DEFINITY monitors synchronization performance and alarms faulty components  
within DEFINITY.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SYNC (ATM Synchronization)  
3-223  
ATM-SYNC commands  
Use the following commands to help troubleshoot ATM-SYNC problems:  
change  
synchronization  
Allows primary and secondary references to be  
administered for the Stratum 4 option, or ATM-Switch,  
indicating that the synchronization references are input  
directly to the ATM switch  
status  
Shows the current inferred synchronization reference  
synchronization  
status  
synchronization  
Shows the administered primary and secondary  
synchronization references  
list timing-source  
Displays all DS1 and UDS1 locations that are allowed to  
be administered as primary or secondary references  
with the change synchronization command  
disable/enable  
synchronization-  
switch  
Prevents or allows switching to another synchronization  
source  
test  
Tests the administered synchronization source  
synchronization  
Error Log Entries and Test to Clear Values  
Table 3-93. Synchronization Error Log Entries  
Aux  
Data  
Associated  
Test  
On/Off  
Board  
Error Type  
Alarm Level  
Test to Clear Value  
test synchronization  
None  
1
0
0
Any  
Any  
Any  
1 (a) (g)  
None  
WARNING/  
MINOR  
OFF  
257 (b) (g)  
513 (c) (g)  
None  
None  
WARNING/  
MINOR  
OFF  
OFF  
None  
None  
WARNING/  
MAJOR  
2
1537 (d)  
None  
None  
None  
WARNING  
NONE  
OFF  
OFF  
OFF  
None  
None  
None  
2
1793 (e)  
0-50  
0
2
2049 (f)  
WARNING  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. It may take up to 1 hour for these alarms to clear via the “leaky bucket” strategy.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SYNC (ATM Synchronization)  
3-224  
Notes:  
a. Error Type 1: problem with the primary DS1 reference. It is cleared when  
the primary reference is restored. The following steps should give an  
indication of the source of the problem:  
1. Check if the primary DS1 interface circuit pack is inserted in the  
carrier with the list configuration board UUCSS command.  
2. Verify that the administered primary reference matches the DS1  
reference from the network synchronization plan.  
3. Test the primary DS1 interface circuit pack with the test board  
UUCSS long command. Check the Error Log for DS1-BD or  
UDS1-BD errors and refer to the DS1-BD or UDS1-BD (DS1  
Interface Circuit Pack or UDS1 Interface Circuit Pack) Maintenance  
documentation to resolve any errors associated with the primary  
DS1 (DS1 or UDS1) interface circuit pack. If the only errors against  
DS1-BD or UDS1-BD are slip errors, then follow the procedures  
described in the troubleshooting section above. If no errors are  
listed in the Error Log for the primary DS1 interface circuit pack,  
continue with the following steps.  
4. Test the active Tone-Clock circuit pack in the master port network  
with the test tone-clock UUC long command. Check the Error Log  
for TDM-CLK errors and verify that TDM Bus Clock Test #148 (TDM  
Bus Clock Circuit Status Inquiry Test) passes successfully. If Test  
#148 fails with an Error Code 2 through 32, refer to the TDM-CLK  
(TDM Bus Clock) Maintenance documentation to resolve the  
problem.  
b. Error Type 257: problem with the secondary DS1 reference. It is cleared  
when the secondary reference is restored. Refer to note (a) to resolve this  
error substituting secondary for primary in the preceding resolution  
steps.  
c. Error Type 513: the ATM switch clock is inferred to be providing the timing  
source for the system. The primary and secondary (if administered) are  
not providing a valid timing signal. Investigate errors 1 and 257 to resolve  
this error.  
d. Error Type 1537: over half of the DS1s that are administered with slip  
detection enabled through the Slip Detection?field set to y are  
experiencing slips.  
e. Error Type 1793: inferred excessive switching of system synchronization  
references has occurred. When this error occurs, it is inferred that the ATM  
switch clock has become the synchronization reference for the system.  
1. Check for timing loops and resolve any loops that exist.  
2. Test the active Tone-Clock circuit pack in the master port network  
with the test tone-clock UUC long command. Check the Error Log  
for TDM-CLK errors and verify that TDM Bus Clock Test #148 (TDM  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SYNC (ATM Synchronization)  
3-225  
Bus Clock Circuit Status Inquiry test) passes successfully. If Test  
#148 fails with an Error Code 2 through 32, refer to TDM-CLK to  
resolve the problem. If not, continue with the following steps.  
3. For Duplicated Tone-Clock circuit packs in the master port network:  
Switch Tone-Clock circuit packs on the master port network with the  
set tone-clock UUC command.  
For Simplex Tone-Clock circuit packs in the master port network:  
replace the primary and secondary (if administered) DS1 Interface  
circuit packs.  
4. Investigate any other SYNC errors.  
f. Error Type 2049: the ATM Expansion Interface circuit packs have errors  
that affect synchronization. Test the ATM Expansion Interface circuit pack  
with the test board UUCSS command.  
This error is cleared by a “leaky bucket” strategy and takes up to one hour  
to clear (leak away) the error counter once it is cleared.  
g. Error Types 1, 257, and 513: noise on the DS1 line can cause transient  
alarms on synchronization. Therefore, when a synchronization problem  
occurs on Error Types 1, 257, or 513, a WARNING alarm is first raised for  
15 to 20 minutes before the alarm is upgraded to a MINOR or MAJOR  
alarm.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented below when inspecting errors in  
the system.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Test Synchronization Test (#417)  
X
X
ND  
1. D = Destructive, ND = Non-destructive  
Test Synchronization Test (#417)  
This test updates all the Synchronization Maintenance component circuit packs  
with the correct information regarding their role in providing synchronization for  
the system. All the Tone-Clock, ATM Expansion Interface, DS1 Interface, and  
UDS1 Interface circuit packs in the system are updated through this test. This  
test either passes or aborts.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-SYNC (ATM Synchronization)  
3-226  
Table 3-94. TEST #417 Test Synchronization Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
Could not allocate the necessary system resources to run this test.  
Internal system error  
1000  
ABORT  
1115  
2500  
ABORT  
ABORT  
PASS  
The synchronization maintenance component circuit pack parameters have  
been successfully updated. The system should be synchronized after  
successful execution of this test.  
1. If synchronization problems still exist, refer to the Error Log to obtain  
information regarding the source of the problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-227  
ATM-TRK (Circuit Emulation Service  
Circuit Pack)  
MO Name  
(in Alarm  
Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
ATM-TRK  
ATM-TRK  
ATM-TRK  
MAJOR  
test board UUCSS  
test board UUCSS  
test board UUCSS  
ATM TRUNK (ATM Circuit Emulation  
Service)  
MINOR  
ATM TRUNK (ATM Circuit Emulation  
Service)  
WARNING  
ATM TRUNK (ATM Circuit Emulation  
Service)  
1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation (A, B,  
C, D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21).  
This maintenance object explains how you test and repair TN230x ATM Interface  
circuit packs (TN2305 and TN2306) that have been administered as virtual  
ISDN-PRI trunks for ATM Circuit Emulation Service (CES). The maintenance  
instructions for TN230x circuit packs that have been administered as Expansion  
Interfaces for WAN connectivity are in the ATM-EI (Expansion Interface Circuit  
Pack) maintenance object.  
Description  
The TN2305 and TN2306 (Table 3-95) are dual-purpose ATM circuit packs that  
can be administered as either personality:  
■
‘‘ATM Circuit Emulation Service’’ or virtual ISDN-PRI signaling trunks.  
■
Expansion Interfaces (ATM-EI) for Port Network Connectivity (ATM-PNC)  
between the PPN and the EPNs.  
Either circuit pack “personality” requires SONET OC-3 or SDH STM-1 fiber cable  
connections between the circuit pack and the ATM switch. As a trunk board, it  
supports direct connection between ATM CES circuit packs without an  
intervening ATM switch.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-228  
Table 3-95. R7 ATM-TRK circuit packs  
Echo  
Circuit pack  
Channel types  
Interface  
Fiber  
cancellation  
TN2305  
B and D  
channels  
24 or 32  
channel  
Multi mode  
Y
Y
TN2306  
B and D  
channels  
24 or 32  
channel  
Single mode  
NOTE:  
TN230x circuit packs are not interchangeable.  
ATM Circuit Emulation Service  
Under ATM Circuit Emulation Service (CES), you simulate ISDN-PRI circuits by  
assigning ports to signaling groups. Each signaling group represents a PRI  
circuit, and the ports in the group represent the D-channel and B-channels of that  
circuit. TN230x circuit packs support up to 248 ports per circuit pack.  
Virtual D-channels. Non-facility associated signaling is not supported under  
ATM-CES, so you must reserve one port in each signaling group for use as a  
D-channel (channel 24 when emulating a T-1 ISDN facility, channel 16 when  
emulating an E-1 facility). The D-channel can be any physical port from 9 to 32.  
Virtual circuits. The TN230x can support a varied number of virtual circuits,  
depending on the switch and the administration of the circuit pack. Table 3-96  
lists the possibilities for various DEFINITY models.  
Table 3-96. Circuit and channel capacities, for each DEFINITY model  
Emulated  
circuits  
(signaling  
groups)  
Virtual  
Virtual  
Model  
R6csi  
R6si  
Ports  
248  
248  
248  
Channels/circuit D-channels B-channels  
1 to 8  
1 to 8  
1 to 8  
24 (T1), 31 (E1)  
24 (T1), 31 (E1)  
24 (T1), 31 (E1)  
1-8  
1-8  
1-8  
6-240  
6-240  
6-240  
R6r  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-229  
Virtual trunk groups. You cannot bundle physical DS1 ISDN-PRI circuits and  
virtual ATM-CES circuits into the same trunk groups. Virtual circuits can only be  
assigned to all-virtual, all-ATM trunk groups. Table 3-97 lists the possible  
trunk-group capacities for various DEFINITY models.  
Table 3-97. ATM CES capacities by DEFINITY model  
Ports per  
trunk group  
Model (max)  
Trunk groups per  
switch (max)  
Trunks per  
switch (max)  
R6csi  
R6si  
R6r  
99  
99  
400  
400  
400  
99  
99  
255  
666  
Table 3-98 shows the ATM CES capacities for both T1 and E1 circuits.  
Table 3-98. Ports available for trunking, for each ISDN facility type  
Channels per  
signaling  
Type group (trunk)  
Max. signaling  
groups (trunks)  
per circuit pack  
Max.  
available  
ports  
Reserved Total  
ports  
ports  
T1:  
E1:  
24  
31  
8
8
192  
248  
ports 1-8  
ports 1-8  
256  
256  
LEDs  
The ATM circuit pack LEDs give you a visual indication of the condition of the  
TN230x circuit pack (Table 3-99).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-230  
Table 3-99. ATM-TRK LED interpretation  
LEDs  
Condition  
LED status  
Red  
Error (alarm logged)  
On  
Red and Booting (LEDs being tested)  
Green  
Blinking (on 200 ms, off 200 ms)  
Green  
Yellow  
Test/maintenance in progress  
On  
Fiber Loss of Signal (LOS), LOF, MS_RDI,  
MS_AIS, LCD, HP_RDI, HP_AIS, LOP, PSC  
Blinking fast (100 ms on, 100 ms off)  
Yellow  
Yellow  
Signal to ATM switch down  
Blinking slowly (500 ms on, 500 ms off)  
On  
One or more CES signaling groups  
administered  
Yellow  
CES signaling group not administered or  
not reporting to firmware  
Off  
ATM-TRK-related commands  
Table 3-100 lists some commands that can be useful in troubleshooting ATM  
errors and alarms.  
Table 3-100. ATM CES troubleshooting commands  
Command  
Description  
display circuit-packs  
cabinet  
Displays the circuit packs in the cabinet, identifying ATM Trunk as well  
as ATM-EI boards. “ATM Interface” boards have not been  
administered as CES or PNC.  
display atm ports  
UUCSSppp  
Displays the 256 ports on the ATM board with the corresponding  
signaling and trunk group.  
list configuration  
atm  
Lists the ATM boards, identifying equipment location, board code,  
type, and vintage.  
list configuration  
trunks  
Lists boards identifying assigned ports. While the ATM board is listed,  
the 256 ports are not.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-231  
Table 3-100. ATM CES troubleshooting commands — Continued  
Command  
Description  
busyout/release atm  
signaling-group  
Busyout or release of an ATM signaling group within a trunk group.  
status atm  
Show current status of an ATM signaling group.  
signaling-group  
status trunk-group  
Shows status of the trunk group (ATM signaling groups are part of  
trunk groups).  
Error Log Entries and Test to Clear Values  
Table 3-101. ATM-TRK Error Log entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
0
0
Any  
Any  
test board UUCSS  
1(a)  
None  
MIN  
MIN  
MIN  
MIN  
MIN  
ON  
ON  
ON  
ON  
ON  
18(b)  
23(c)  
125(d)  
257(e)  
0
0
busy out board UUCSS  
release board UUCSS  
None  
None  
Any  
Any  
35  
Control Channel Loop  
Test (#52)  
test board UUCSS r 2  
test board UUCSS l r 1  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS r 1  
513(f)  
ATM Cross talk Test  
(#1298)  
MIN  
ON  
769(g)  
770(g)  
771(h)  
1281(i)  
1537(j)  
1538(k)  
ATM Error Query Test  
#1259  
WRN  
WRN  
WRN  
OFF  
OFF  
OFF  
OFF  
ON  
25  
ATM Error Query Test  
#1259  
26  
ATM Error Query Test  
#1259  
ATM Board Error Query  
Test (#1259)  
WRN/  
MIN  
12  
0
None  
WRN/  
MIN  
None  
WRN/  
MIN  
ON  
reset board UUCSS  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-232  
Table 3-101. ATM-TRK Error Log entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
None  
Test to Clear Value  
1794(l)  
13  
MIN  
ON  
2049(m)  
2306(n)  
2561(o)  
15  
None  
None  
WRN  
MIN  
OFF  
test board UUCSS  
Packet interface test  
(#598)  
ON  
ON  
ON  
test board UUCSS r 2  
test board UUCSS  
test board UUCSS  
2817(p)  
2818(p)  
1-24  
1-24  
3
ATM Board DSP test  
(#1293)  
WRN/  
MIN  
WRN/  
MIN  
3330(q)  
3585(r)  
MIN  
OFF  
ON  
ATM Board Error Query  
test (#1259)  
WRN/  
MIN  
test board UUCSS l  
3841(s)  
3842(t)  
3999(u)  
Any  
11  
None  
None  
None  
Any  
Notes:  
a. Error Type 1: the ATM-TRK circuit pack does not appear to be in its  
assigned slot.  
1. Make sure that the ATM-TRK circuit pack is installed correctly  
seated in the slot administered for the ATM trunk.  
b. Error Type 18: the ATM circuit pack is busied out.  
1. Run release board UUCSS.  
c. Error Type 23: an ATM trunk is administered, but the corresponding  
ATM-TRK circuit pack does not appear to be physically installed.  
1. Make sure the ATM-TRK circuit pack is installed and correctly  
seated in the slot.  
d. Error Type 125: an ATM trunk is administered but a non-ATM-TRK circuit  
pack is installed in the corresponding slot. You have two options:  
■
Replace the incorrect circuit pack with an ATM-TRK circuit pack.  
■
Or re-administer the slot for the circuit pack that is physically  
present, locate the slot where the ATM-TRK circuit pack is actually  
installed, and re-administer the ATM trunk.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-233  
e. Error Type 257: Control Channel Loop Test #52 failed. The circuit pack is  
not properly connected with the control channel on the TDM bus.  
1. Take the corrective action specified by Test #52?.  
f. Error Type 513: ATM Crosstalk Test (#1298) failed. The board is writing to  
or reading from a TDM time slot that is not allocated to the board, or the  
Digital Signal Processor (DSP) selected for this test has malfunctioned.  
1. Run test board UUCSS.  
2. Take the corrective action specified for Test #1298.  
g. Error Type 769, 770: the ATM switch is requesting too many LAPD  
retransmissions (off-board ATM cell corruption errors).  
Error Aux  
Type Data Description  
769  
770  
35  
25  
LAPD excessive retransmission requests  
ATM uncorrectable cell headers - threshold  
1. Check the connections between the fiber cable, the ATM-TRK  
circuit pack, and the ATM switch.  
2. See the PKT-BUS for test and corrective procedures (Aux Data 35  
only).  
3. Determine what type of fiber is installed between the ATM-TRK  
circuit pack and the ATM switch.  
If  
Then  
There is multimode fiber  
Check the length of the fiber. If the cable  
is longer than 2 km, it is probably causing  
the errors.  
There is single-mode fiber  
or the length of the  
multimode fiber is less  
than 2 km  
The source of the errors may lie in the  
ATM facility, the ATM-TRK circuit pack, or  
the far-end circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-234  
4. Perform ATM loopback tests on the near-end ATM-TRK circuit pack  
and on the far-end circuit pack or ATM switch.  
If  
Then  
The ATM-TRK circuit pack  
fails the loopback test.  
The problem is in the ATM-TRK circuit  
pack. Replace the circuit pack.  
The far-end circuit pack or  
ATM switch fails the  
loopback test.  
The problem is in the far-end circuit pack  
or ATM switch. Consult the circuit-pack  
or ATM switch documentation for advice.  
The equipment at each  
end of the ATM span  
passes the loopback test  
The problem is somewhere in the ATM  
span. Lack of bandwidth may be forcing  
an intermediate ATM switch to drop cells.  
5. Check capacity and peak bandwidth consumption for the ATM  
span.  
If  
Then  
The capacity of the  
span is inadequate or  
bandwidth consumption  
is too high.  
Reduce traffic on the DEFINITY switch to  
ensure that it is using no more that its  
subscribed bandwidth.  
h. Error Type 771: the ATM switch is sending cells with unknown Virtual  
Path-Identifier (VPI) and Virtual Channel-Identifier (VCI) addresses.  
1. Make sure that the ATM-TRK circuit-pack address is administered  
identically on the ATM switch and the DEFINITY ECS.  
i. Error Type 1281: Board major signals error (loss of high-level signal). The  
far-end has detected a major problem in transmissions originating from  
the ATM-TRK circuit pack. The possible Aux Data values for this software  
counter are listed in Table 3-102.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-235  
Table 3-102. Error type 1281 Aux Data and repair procedures  
Aux  
Alarm  
Data  
Description  
Repair procedure  
15  
SYSCLOCK failed  
The board is not locked to the TDM backplane clock signal. This is  
probably due to a Tone Clock problem.  
1. Check for TDM-BUS or TONE-BD errors in the Error Log.  
2. If no other problems are present, reset the circuit pack (reset  
board UUCSS)  
16  
Loss of Signal:  
LOS  
The fiber is not connected properly to the ATM-TRK board or ATM  
switch (or to the multiplexer section [MUX] if present).It is possible  
that the board transceivers are not functioning properly.  
1. Run test board UUCSS command.  
2. If Test #1259 fails with Error Code 16, connect a fiber  
back-to-back in a looped mode (one strand of fiber connecting  
the transmit transceiver to the receive transceiver of the board)  
and see if the yellow LED flash goes away. If it does the  
problem is off-board.  
3. If the yellow LED continues to flash, replace the circuit pack.  
The fiber signal cannot obtain or maintain STM-1/OC-3 framing.  
1. Try to more the fiber on the ATM switch side to a different port.  
17  
18  
Loss of Frame:  
LOF  
2. If the problem persists, reset the circuit pack (reset board  
UUCSS).  
Multiplexer  
There is a major problem on the far end (between multiplexer  
section [MUX] and the switch) that prohibits the circuit pack from  
sending a valid signal.  
Section Alarm  
Indication Signal:  
MS_AIS  
1. See if the ports at the MUX and/or the ATM switch are  
connected snugly.  
2. Run test board UUCSS command  
3. If Test #1259 fails with Error Code 18, connect a fiber  
back-to-back in a looped mode (one strand of fiber connecting  
the transmit transceiver to the receive transceiver of the board)  
and see if the yellow LED flash goes away.  
4. If it does the problem is off-board.  
5. If the yellow LED continues to flash, replace the circuit pack; if  
the error persists, escalate the problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-236  
Table 3-102. Error type 1281 Aux Data and repair procedures — Continued  
Aux  
Alarm  
Data  
Description  
Repair procedure  
19  
Multiplexer  
The far-end is detecting a major problem with the signal that this  
board is transmitting.  
Section Remote  
Defect Indicator:  
MS_RDI  
1. Make sure the ATM switch port (or a MUX port, if present  
between ATM switch and the ATM-TRK board) is the same as  
the ATM-TRK circuit pack’s cable interface  
2. Run test board UUCSS command.  
3. If Test #1259 fails with Error Code 19, connect a fiber  
back-to-back in a looped mode (one strand of fiber connecting  
the transmit transceiver to the receive transceiver of the board)  
and see if the yellow LED flash goes away.  
4. If it does the problem is off-board.  
5. If the yellow LED continues to flash, replace the circuit pack; if  
the error persists, escalate the problem.  
20  
21  
Loss of pointer:  
LOP  
ATM framer chip is unable to access the payload part of the signal.  
1. Reset the board (reset board UUCSS).  
2. If the error persists replace the board.  
Path Signal Error  
(PSL)  
The incoming signal payload is not set up for transmission of ATM  
data.  
(STM1/SONET)  
1. Make sure the ATM switch port (or a MUX port, if present  
between ATM switch and the ATM-TRK board) is the same as  
the ATM-TRK circuit pack’s cable interface.  
22  
High-level Path  
Alarm Indication  
Signal:  
The payload is invalid.  
1. Make sure the ATM switch port (or a MUX port, if present  
between ATM switch and the ATM-TRK board) is the same as  
the ATM-TRK circuit pack’s cable interface.  
HP_AIS  
2. Run test board UUCSS.  
3. If Test #1259 fails with Error Code 22, connect a fiber  
back-to-back in a looped mode (one strand of fiber connecting  
the transmit transceiver to the receive transceiver of the board)  
and see if the yellow LED flash goes away.  
4. If it does the problem is off-board.  
5. If the yellow LED continues to flash, replace the circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-237  
Table 3-102. Error type 1281 Aux Data and repair procedures — Continued  
Aux  
Alarm  
Data  
Description  
Repair procedure  
23  
High-level path  
Remote defect  
Indicator: HP_RDI  
The far-end is detecting a major problem with the signal that this  
board is transmitting. The transmitted payload is invalid.  
1. Make sure the ATM switch port (or a MUX port, if present  
between ATM switch and the ATM-TRK board) is the same as  
the ATM-TRK circuit pack’s cable interface.  
2. Run test board UUCSS command; if the Test #1259 fails with  
Error Code 23, connect a fiber back-to-back in a looped mode  
(one strand of fiber connecting the transmit transceiver to the  
receive transceiver of the board) and see if the yellow LED  
flash goes away.  
3. If it does the problem is off-board.  
4. If the yellow LED continues to flash, replace the circuit pack.  
24  
27  
Loss of cell  
delineation (LCD)  
On board ATM framer chip is not able to frame cells based on the  
cell header.  
1. Reset the board (reset board UUCSS).  
2. If the error persists, replace the board.  
The board cannot communicate with the ATM switch.  
1. Busyout the board (busyout board UUCSS).  
2. Test the board (test board long UUCSS).  
3. If Test #1260 fails, replace the board.  
SIGCON_DOWN  
ATM switch high  
level signal.  
4. If Test #1260 passes, make sure the ATM address on both the  
DEFINITY and the ATM switch sides are the same for this  
board.  
5. If the address is the same, change the port on the ATM switch  
side.  
6. If the error is resolved, the problem is on the ATM switch port.  
j. Error Type 1537: LANHO bus timeout. The circuit pack is transmitting too  
many bytes on the LAN bus for a single frame. This may be due to:  
■
on-board fault  
■
faulty data received on one of the circuit pack’s external ports  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-238  
If the error occurs 3 times in 10 minutes, the board is isolated from the  
Packet Bus and the board is alarmed. To clear the alarm:  
1. Restore this circuit pack to the Packet Bus with this command  
sequence:  
a. busyout board UUCSS  
b. reset board UUCSS  
c. test board UUCSS long  
d. release board UUCSS  
2. If the problem persists and there are no PKT-BUS or port alarms,  
replace the circuit pack.  
k. Error Type 1538: The ATM-TRK circuit pack is hyperactive (sending an  
abnormal number of control messages to the processor). Use the  
following command sequence for this ATM-TRK circuit pack:  
1. busyout board UUCSS  
2. reset board UUCSS  
3. test board UUCSS long  
4. release board UUCSS  
5. If this error persists, replace the circuit pack.  
l. Error Type 1794: LANHO transmit FIFO overflow. The circuit pack’s  
transmit buffers have overflowed.  
1. Run test board UUCSS r 5.  
If  
Then  
Test #598 fails  
Replace the circuit pack.  
m. Error Type 2049: ACL Link Failure (link is down). The ATM Control Link  
(ACL) has failed, communication has been interrupted between the SPE  
and the ATM-TRK circuit packs on the system, and signaling-group  
parameters are not communicated across the packet bus.  
1. Check the PKT-BUS (Packet Bus) and SYS-LINK (System Link)  
maintenance objects, and follow the repair procedures indicated.  
2. Run test board UUCSS against the ATM-TRK circuit pack.  
If  
Then  
Test 598 fails.  
Follow the repair procedures suggested for that  
test.  
n. Error Type 2306: too many parity errors in data received from the  
LAN/packet bus.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-239  
1. Run test board UUCSS.  
If  
Then  
Follow the repair procedures suggested for that  
Test 598 fails.  
test  
Test 598 passes.  
See the PKT-BUS (Packet Bus) maintenance  
object, and perform the specified repair.  
There are no errors  
against the packet  
bus maintenance  
object.  
This may be a transient condition. Do nothing  
now, but escalate if the error occurs repeatedly.  
o. Error Type 2561: Packet Interface Loop Around Test (598) Failure. The  
ATM-TRK circuit pack has failed, the packet bus has a minor alarm active,  
or the packet bus is out of service.  
1. Run test board UUCSS.  
If  
Then  
Test 598 fails.  
Follow the repair procedures suggested for that  
test  
Test 598 passes.  
See the PKT-BUS (Packet Bus) maintenance  
object, and perform the specified repair.  
There are no errors  
against the packet  
bus maintenance  
object.  
This may be a transient condition. Do nothing  
now, but escalate if the error occurs repeatedly.  
p. Error Type 2817, 2818: DSP failure detected along the circuit path.  
1. Run test board UUCSS.  
2. Follow the repair procedures suggested for Test #1293.  
Error Type  
Description  
2818  
One or more DSPs failed. The Aux Data field contains  
the ID number of DSP that failed  
2817  
DSP test failure. The Aux Datafield contains the  
following information about the failed DSPs:  
■ X is the number of talker DSPs  
■ Y is the number of listener DSPs  
■ Z is the number of echo-cancelling DSPs  
q. Error Type 3330: LANHO critical error. The circuit pack reports that the  
on-board LANHO chip is insane (possibly due to a problem in Packet Bus  
arbitration, in the transmission line frame, or in the circuit pack itself). The  
circuit pack cannot talk to the Packet Bus.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-240  
1. Check for PKT-BUS alarms.  
If  
Then  
There is a  
packet-bus  
alarm.  
There is probably a packet-bus problem,  
particularly if other circuit packs on the packet bus  
report the same error. See the PKT-BUS (Packet  
Bus) maintenance object and the packet-bus  
fault-isolation and recovery sections of the  
maintenance manual for repair procedures.  
There are no  
packet-bus  
alarms.  
Run the following command sequence:  
busyout board UUCSS  
reset board UUCSS.  
test board UUCSS long  
release board UUCSS  
The problem  
persists.  
Replace the ATM-TRK circuit pack.  
r. Error Type 3585: Major board alarm; failure of critical components involved  
in the operation of the circuit pack. The circuit pack has failed, and the  
switch may no longer recognize it.  
Aux  
Data Description  
1
2
4
5
6
7
8
9
ATM framer chip failure  
NCE failed  
TDM PLD failed  
All DSPs on the circuit pack have failed  
Receive Network Processor (RNP) failed  
Transmit Network Processor (TNP) failed  
MEMORY read/write failure  
DUART failure  
1. Run test board UUCSS long.  
If  
Then  
Test #1259 fails with Error  
Code XXYY and XX is an  
AUX value in the  
Replace the ATM-TRK circuit pack.  
preceding table  
The system does not  
Replace the ATM-TRK circuit pack.  
recognize the circuit pack  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-241  
s. Error Type 3841: the ATM-TRK circuit pack received an unrecognized  
message from the switch and responded with an inconsistent down-link  
error message.  
1. Do nothing. This error does not affect service.  
t. Error Type 3842: LANHO Receive FIFO Overflow error; the packet bus is  
delivering data to the ATM-TRK circuit pack faster than the circuit pack  
can distribute it to the endpoint.  
1. Do nothing. The circuit pack can recover by itself.  
u. Error Type 3999: circuit pack sent a large number of control channel  
messages to the switch within a short period of time.  
If  
Then  
Error Type 1538 is also  
present  
Circuit pack is taken out of service  
If Error Type 1538 is not  
present  
Circuit pack is not taken out of service,  
but has generated 50% of the messages  
necessary to be considered hyperactive.  
■ This may be normal during heavy  
traffic.  
■ If the error is logged during light  
traffic, it may indicate a problem with  
the circuit pack or the equipment  
attached to it.  
System Technician-Demanded Tests: Descriptions  
and error codes  
Always investigate problems in the order presented. When you clear one of the  
error codes associated with a given test, you clear errors generated by other  
tests in the testing sequence. If you clear errors out of order, you can lose  
important information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-242  
Table 3-103. System Technician-Demanded Tests: ATM-TRK  
Reset  
Board  
Sequence  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
ATM Board Time Of Day Update (#1261)  
Connection Audit Test (#50)  
D/ND  
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
D
Control Channel Loop Test (#52)  
Packet Interface Loop Around Test (#598)  
ATM DSP Test (#1293)  
X
X
ATM Board Framer Looparound Test  
(#1260)  
ATM Board Error Query Test (#1259)  
ATM Cross Talk Test (#1298)  
ATM Board Reset (#1256)  
X
X
X
ND  
ND  
D
X
1. D = Destructive, ND = Non-destructive  
Connection Audit Test (#50)  
Non-destructive (in a sane switch environment).  
The Connection Audit test updates TDM time slots. It sends network-update  
Control Channel Message Set (CCMS) messages that tell the ATM-TRK circuit  
pack to listen to, talk to, or disconnect particular time slots.  
The test passes if software successfully sends the downlink network-update  
messages. It aborts otherwise.  
!
CAUTION:  
Though normally non-destructive, this test might unintentionally tear down  
an active call if the connection-manager software’s tables are corrupt.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-243  
Table 3-104. TEST #50 Connection Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
System resources required for this test are not available.  
1. Retry the command up to 5 times at 1-minute intervals.  
The test aborted because a test was already running on the port.  
1. Retry the command up to 5 times at 1-minute intervals.  
Internal system error  
None  
2100  
ABORT  
ABORT  
FAIL  
1019  
1. Retry the command up to 5 times at 1-minute intervals.  
The circuit pack has been updated with its translation.  
PASS  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check the board translations.  
2. If the ATM-TRK circuit pack is not administered, run add atm trunk  
UUCSS.  
3. If the ATM-TRK circuit pack is administered correctly, check the error log.  
4. If ATM-TRK circuit pack is hyperactive, shut down, and reseat the circuit  
pack to force re-initialization.  
5. If the ATM-TRK circuit pack is correctly inserted, run busyout board.  
6. Run reset board.  
7. Run release busy board.  
8. Run test board long to re-establish the linkage between the internal ID  
and the port.  
Control Channel Loop Test (#52)  
The non-destructive Control Channel Loop Test is part of the maintenance  
subsystem’s Common Port Board Testing feature. The Common Port Board test  
sends board vintage queries to a port circuit pack and checks the responses.  
CCMS downlink notifications tell the circuit pack which TDM Bus (A or B) carries  
the control channel and which carries the touch tones.  
The test passes if the port circuit pack responds. The test aborts if the circuit  
pack does not respond. The test fails otherwise.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-244  
Table 3-105. Control Channel Test #52  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Test request timed out.  
2000  
2100  
2500  
ABORT  
ABORT  
ABORT  
Could not allocate needed system resources.  
Internal system error  
1. Retry the command up to 3 times at 1-minute intervals.  
The ATM circuit pack responded incorrectly.  
1. Retry the command up to 3 times at 1-minute intervals.  
FAIL  
2. If the test continues to fail, reset the ATM-TRK circuit pack (reset board  
UUCSS).  
3. If test continues to fail, replace the circuit pack or transceiver.  
The ATM-TRK circuit pack is communicating correctly with the software.  
Circuit pack not detected.  
PASS  
0
NO  
BOARD  
1. Check the error log for Error 125 (wrong board) or Error 131 (no board),  
and correct any errors found.  
2. Make sure that the ATM-TRK circuit pack is properly translated and  
inserted.  
3. Check for Error 1538 (hyperactivity). If hyperactive, run reset board  
UUCSS.  
4. Run the test again. If it fails, replace the ATM-TRK circuit pack, and retest.  
Packet Interface Loop Around Test (#598)  
This nondestructive test checks the ATM-TRK circuit pack’s packet-bus interface.  
The LANHO chip sends data through the bus and back to itself. Figure 3-170  
describes this test, substituting “CES mode” for “PNC mode.”  
If the data received is consistent with the data sent, the test passes; otherwise it  
fails. The test does not run if the packet bus in the specified port network has a  
minor alarm, or is out of service, or if the packet but in the PPN is out of service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-245  
Table 3-106. Packet Interface Loop Around Test (#598)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The packet bus in the PPN has a major alarm against it.  
1. Run display alarms and display errors.  
1144  
ABORT  
2. Perform the PKT-BUS repair procedures associated with the alarms.  
3. Retry the command.  
2000  
ABORT  
Test request timed out.  
1. Retry the command up to 3 times at 1-minute intervals.  
2. If the test fails repeatedly, run reset board UUCSS.  
3. If the test continues to fail, replace the ATM-TRK circuit pack.  
Internal system error.  
2012  
2100  
ABORT  
ABORT  
Could not allocate needed system resources.  
1. Retry the command up to 5 times at 1-minute intervals.  
Data packet not received correctly by the ATM Interface circuit pack.  
1. Retry the command up to 5 times at 1-minute intervals.  
2. If the test continues to fail, replace the ATM-TRK circuit pack.  
The Packet Interface Test passed.  
ANY  
FAIL  
PASS  
ATM Board Reset (#1256)  
This test is destructive.  
This test checks the sanity of the angel processor using the Sanity and Control  
Interface (SAKI) test (Common Port Board test #53). It resets the circuit pack if  
the SAKI test fails and runs the test again.The ATM Board Reset test passes if  
SAKI can successfully reset and retest the board.  
Before running the SAKI test, you must:  
■
Move synchronization off the ATM-TRK circuit pack  
Busyout the ATM-TRK circuit pack  
■
The test aborts if the ATM-TRK circuit pack is supplying synchronization.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-246  
Table 3-107. ATM Board Reset (#1256)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1005  
ABORT  
Wrong circuit pack configuration to run this test. The ATM CES Trunk  
Interface circuit pack provides timing for the system and cannot be reset  
without major system disruptions.  
1. Set synchronization to another ATM CES trunk circuit pack or to the  
Tone-Clock circuit pack and test again.  
1015  
ABORT  
Test cannot be run because the ATM-TRK circuit pack has not been busied  
out.  
1. Busyout out the circuit pack (busyout board UUCSS).  
2. Repeat the test (test board UUCSS long).  
Could not allocate the required system resources  
1. Retry the command up to 5 times at 1-minute intervals.  
2. If the test continues to abort escalate the problem.  
Sanity test timed out.  
None  
2000  
ABORT  
ABORT  
1. Wait 5 minutes. Then see if ATM-TRK circuit pack is visible to the system  
by running list config all.  
2. If the ATM-TRK circuit pack is visible (list configuration all), run the test  
again, and escalate if the problem recurs.  
3. If the ATM-TRK circuit pack is not visible to the system (list  
configuration all), re-seat the ATM-TRK circuit pack, and retest.  
4. If the ATM-TRK circuit pack is still not recognized by the system, replace  
the board.  
2100  
2500  
ABORT  
ABORT  
Could not allocate required system resources  
1. Retry the command up to 5 times at 1-minute intervals.  
Internal system error.  
1. Try to reset the circuit pack (reset board UUCSS).  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-247  
Table 3-107. ATM Board Reset (#1256) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The circuit pack failed to reset  
1
FAIL  
2
FAIL  
The circuit pack failed to restart.  
1. Retry command.  
2. If the problem persists, replace the ATM-TRK circuit pack.  
The ATM-TRK circuit pack is successfully reset.  
No board detected.  
PASS  
0
NO  
BOARD  
1. Check the error log for Error 125 (wrong board) or Error 131 (no board),  
and perform the appropriate repair, if needed.  
2. Ensure that the board is properly translated and inserted.  
3. Check for Error 1538 (hyperactivity). If hyperactive, run reset board  
UUCSS.  
4. Run the test again. If it fails, replace the ATM-TRK circuit pack, and  
retest.  
ATM Board Error Query Test (#1259)  
This non-destructive ATM Error Query Test retrieves the most severe, active, on-  
and off-board problem from the ATM-TRK circuit pack’s firmware and increments  
error counts in the Error Log.  
The test passes if there are no errors and fails otherwise. A passing test clears  
the software counters; a failure increments the counter associated with the  
problem that caused the failure and clears the others.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-248  
Table 3-108. ATM Board Error Query Test (#1259)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Test request timed out.  
2000  
2031  
2100  
2500  
ABORT  
ABORT  
ABORT  
ABORT  
SCD failure. Unable to sent down-link message.  
Could not allocate needed system resources.  
Internal system error  
1. Retry the command up to 3 times at 1-minute intervals.  
XXYY  
FAIL  
On-board error XX (Table 3-109) and/or off-board error YY (Table 3-110).  
1. Examine the error logs and repair any errors found.  
PASS  
The ATM circuit pack has passed this test. No service effecting  
errors/alarms have been detected on board.  
0
NO  
ATM-TRK circuit pack not found  
BOARD  
1. Check the error log, and correct Error 125 (wrong board) or Error 131  
(no board), if found.  
2. Make sure that the board is properly translated and inserted.  
3. Check for hyperactivity (Error 1538). Run reset board UUCSS if  
hyperactive.  
4. Run the test again. If it fails, replace the board, and retest.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-249  
Aux Data XX  
Table 3-109. Aux Data XX for ATM Board Error Query Test (#1259)  
If XX= Then  
1
ATM framer chip failed  
2
NCE chip failed  
3
LANHO critical error  
4
TDM Programmable Logic Device Failed  
All on-board DSPs failed  
Receive Network Processor failed  
Transmit Network Processor failed  
Memory read failed  
5
6
7
8
9
Dual UART chip failed  
10  
11  
12  
13  
14  
LANHO receive parity error  
LANHO FIFO over flow error  
LAN bus time out.  
LANHO Xmit FIFO overflow error  
One or more on-board DSPs failed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-250  
Aux Data YY  
Table 3-110. Aux Data YY for ATM Board Error Query Test (#1259)  
If YY=  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
27  
28  
34  
35  
Then  
Back plane clock failed  
Loss of signal  
Loss of frame  
MS alarm indication signal error  
MS remote defect indicator error  
Loss of Pointer  
Path Signal Level mismatch  
High-level Path alarm indication signal  
High-level Path remote defect indicator  
Loss of Cell Delineation  
Uncorrectable headers sent by the ATM switch.  
Too may cells with invalid VPI/VCI combination.  
The signalling link between the board and the ATM switch is down.  
Board to ATM switch connection is down  
AAL5 Excessive retransmission requests -per VC  
LAPD Excessive retransmission requests - per VC  
ATM Board Framer Looparound Test (#1260)  
Destructive  
This test verifies the board’s circuit (Time Division Multiplexing) and packet paths  
using an on-board, dummy virtual circuit. Before running the test, you must  
■
busyout the ATM-TRK circuit pack (busyout board UUCSS) and  
■
switch synchronization (change synchronization) from the ATM-TRK  
circuit pack  
If the ATM-TRK circuit pack is supplying synchronization, the test aborts.  
The test sends a digital counter from one of the tone generators via one of the  
TDM bus time slots. The ATM framer interface converts this digital counter to ATM  
cells and loops them back internally. The ATM-TRK circuit pack converts the cells  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-251  
back to a digital counter and sends it to the tone receiver for verification. If the  
circuit pack passes the circuit check, the software checks the packet path by  
sending a packet from the packet-interface circuit pack to the ATM-TRK circuit  
pack via the ATM protocol stack.  
Figure 3-174 and Figure 3-175 show a diagrams of this two-part test, substituting  
“CES mode” for “PNC mode.”  
Table 3-111. ATM Board Framer Looparound Test (#1260)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1002  
ABORT  
Time slots could not be allocated. Traffic may be heavy or time slots may be  
out-of-service.  
1. Run display errors, and perform repairs associated with TDM-BUS  
errors.  
2. Retry the command up to 3 times at 1-minute intervals.  
Tone receiver could not be allocated.  
1003  
ABORT  
1. Run display errors, and perform the repairs associated with TTR-LEV  
and TONE-PT errors.  
The test cannot run unless there is at least one Tone Detector available on  
the network that holds the ATM-TRK circuit pack.  
2. Retry the command up to 3 times at 1-minute intervals.  
ATM-TRK circuit pack not busied out  
1. Busyout the ATM circuit pack.  
1015  
1033  
1139  
ABORT  
ABORT  
ABORT  
2. Rerun the command.  
ATM-TRK circuit pack not found  
1. See if the switch can see the circuit pack. Run status Trunk Group.  
2. Retry the command.  
Major alarm on the EPN packet bus  
1. Run display alarms, and perform the repairs associated with PKT-BUS  
errors.  
2. Run display errors, and perform the repairs associated with PKT-BUS  
errors.  
3. Retry the command.  
1141  
ABORT  
Packet-interface circuit pack out of service  
1. See PKT-INTF.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-252  
Table 3-111. ATM Board Framer Looparound Test (#1260) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Major alarm on the PPN packet bus  
1144  
ABORT  
1. Run display alarms, and perform the repairs associated with PKT-BUS.  
2. Run display errors, and perform the repairs associated with PKT-BUS.  
3. Retry the command.  
1394  
2000  
2060  
ABORT  
ABORT  
ABORT  
ATM-TRK circuit pack out of service  
1. Run ATM Board Reset Test #1256.  
Request timed out.  
1. Retry the command up to 3 times at 1-minute intervals.  
Packet-bus link has failed.  
1. Retry the command up to 3 times at 1-minute intervals.  
2. If the test continues to abort, run display errors, and perform the repairs  
associated with PKT-INT errors.  
2100  
2500  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Internal system error  
1. Retry the command up to 3 times at 1-minute intervals.  
Test tone not detected over the looparound; packet-path test aborted.  
1
FAIL  
1. Test the active tone clock on the port network, and verify that a tone is  
reaching the ATM-TRK circuit pack. If not, correct the condition.  
2. Run test board UUCSS long.  
3. If the test continues to fail, replace the ATM-TRK circuit pack or  
transceiver.  
4. Rerun test board UUCSS long.  
2
FAIL  
TN1655 Packet Interface circuit pack could not detect the correct data  
packet.  
1. Test the TN1655 Packet Interface circuit pack to verify that it is functioning  
properly. If not, correct the condition.  
2. Run display errors, and perform the repairs associated with DS1  
CONV-BD errors, if applicable.  
3. Run display alarms, and perform the repairs associated with DS1  
CONV-BD alarms, if applicable.  
4. Run test board UUCSS long.  
5. If this test continues to fail, replace the ATM-TRK circuit pack.  
6. Run test board UUCSS long.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-253  
Table 3-111. ATM Board Framer Looparound Test (#1260) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
3
FAIL  
Distorted tone returned  
1. Test the active tone clock on the port network, and verify that a tone is  
reaching the ATM-TRK circuit pack. If not, correct the condition.  
2. Run test board UUCSS long.  
3. If the test continues to fail, replace the ATM-TRK circuit pack.  
4. Run test board UUCSS long.  
4
5
6
FAIL  
FAIL  
FAIL  
Unable to create TDM-path loop.  
1. Retry the command up to 3 times at 1-minute intervals.  
2. If this test continues to fail, replace the ATM-TRK circuit pack.  
3. Run test board UUCSS long.  
Unable to create packet-path loop.  
1. Retry the command up to 3 times at 1-minute intervals.  
2. If this test continues to fail, replace the ATM-TRK circuit pack.  
3. Rerun test board UUCSS long.  
A previously established looparound was not released.  
1. Run reset board UUCSS.  
2. Retry the command up to 3 times at 1-minute intervals.  
3. If this test continues to fail, replace the ATM-TRK circuit pack.  
4. Rerun test board UUCSS long.  
PASS  
The non-optical parts of the ATM-TRK circuit pack are functioning properly.  
ATM-TRK circuit pack not found  
0
NO  
BOARD  
1. Check the error log for Error 125 (wrong board) or Error 131 (no board),  
and correct as necessary.  
2. Check that the board is properly translated and inserted.  
3. Check for Error 1538 (hyperactivity), and run reset board UUCSS if  
necessary.  
4. Rerun test board UUCSS long.  
5. If the test fails, replace the board, and rerun test board UUCSS long.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-254  
ATM Board Time Of Day Update (#1261)  
This non-destructive test updates the system time that the ATM-TRK circuit pack  
uses for SDH/SONET performance monitoring and synchronizes the ATM-TRK  
circuit pack with the DEFINITY system clock. The test is run during initialization,  
scheduled maintenance, and craft long tests.  
Table 3-112. ATM Board Time Of Day Update (#1261)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2031  
FAIL  
The attempt to send the message to the ATM-TRK circuit pack was not  
successful.  
2500  
FAIL  
Internal system error. Did not send the time of day information to the board.  
1. Retry the command up to 3 times at 1-minute intervals.  
2. If the test aborts with the same error code, escalate the problem.  
The ATM-TRK circuit pack is successfully updated with system time.  
PASS  
1. If the status port-network command still indicates that this link is down, it  
is possible that one or both of the ATM-TRK circuit packs have been  
busied out.  
2. If the link still does not come up, reset one or both ATM-TRK circuit packs  
on the link.  
0
NO  
No board detected.  
BOARD  
1. Check the error log for wrong board (Error 125) or no board (Error 131).  
Resolve either of these issues, if applicable.  
2. Check that the board is properly translated and inserted. If so, check for  
hyperactivity (Error 1538). If hyperactive, use the reset board UUCSS  
command.  
3. Run the test again. If it fails, the board may be bad. Replace the board  
and retest.  
ATM Board DSP Test (#1293)  
Non-destructive  
There are three kinds of digital signal processors (DSPs): talkers, listeners, and  
echo cancelers.Talkers put data on the TDM bus, listeners take data off the TDM  
bus, and echo cancelers filter out echoes of the main transmission. Firmware  
allocates DSPs in sets of three (one of each type), up to a maximum of 8 sets.  
This has three parts, one for each type of DSP. If the test fails for all DSPs, a  
MAJOR alarm is raised. If the test fails for one or more DSPs, a MINOR alarm is  
raised. If a DSP is busy, the test passes for that DSP. The test aborts if system  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-255  
resources are not available. Each part of the test returns the number of DSPs that  
passed or failed. The test is run during initialization, error analysis testing,  
periodic, scheduled, and craft short and long testing.  
Table 3-113. ATM Board DSP Test (#1293)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1002  
ABORT  
Could not allocate time slots. Traffic may be heavy or time slots may be  
out-of-service  
1. Run display errors, and follow associated repair procedures for  
TDM-BUS.  
2. Retry the command up to 3 times at 1-minute intervals.  
1003  
ABORT  
Could not allocate a tone detector. Too few tone detectors present or tone  
detectors out-of-service.  
1. Run display errors, and follow the repair procedures associated with  
any TTR-LEV errors that appear.  
2. Make sure that there is at least one tone detector on the network that  
holds the ATM-TRK circuit pack.  
3. Resolve any TONE-PT errors listed in the Error Log.  
4. Retry the command up to 3 times at 1-minute intervals.  
All DSPs are busy. This is a very unlikely event.  
1. Retry the command up to 3 times at 1-minute intervals.  
Test timed out.  
1962  
2000  
ABORT  
ABORT  
1. If the ATM-TRK circuit pack is in standby, reset the board and run the  
test again after the ATM-TRK circuit pack is inserted.  
2. Examine the Error Log for Error 1218 (bad DSP).  
3. Run the test again.  
2100  
2302  
2500  
ABORT  
ABORT  
ABORT  
Could not allocate required system resources.  
Inconsistent uplink message from the ATM-TRK circuit pack.  
Internal system error  
1. Retry the command up to 5 times at 1-minute intervals.  
Circuit pack not a TN2305A/2306A.  
2752  
ABORT  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-256  
Table 3-113. ATM Board DSP Test (#1293) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
XYZ  
FAIL  
There is at least one bad DSP on the board. The X value indicates the  
number of bad talker DSPs, Y indicates the number of bad listener DSPs  
and Z indicates the number of bad echo canceler DSPs.  
1. Test the Active Tone-Clock on the port network that contains the  
ATM-TRK circuit pack for dial-tone. Repair as needed.  
2. Repeat the short test on the ATM-TRK circuit pack.  
3. If the test continues to fail, check for service-affecting MINOR alarms. If  
a MINOR alarm is raised for Error Type 2817 or 1818, replace the circuit  
pack.  
4. If a WARNING alarm is raised, this is a non-service-affecting error, and  
the circuit pack can still process calls.  
XY8  
PASS  
The test passed for some or all DSPs. XY8 indicates the number of talker,  
listener, and echo-canceler DSPs for which the test passed (the rest of the  
DSPs were skipped). The X value indicates the number of good talker DSPs,  
Y indicates the number of good listener DSPs and Z indicates the number of  
good echo canceler DSPs.  
0
NO  
No board detected.  
BOARD  
1. Check the Error Log for wrong board Error 125 (wrong board) or Error  
131 (no board). Replace or insert the circuit pack if necessary.  
2. Check that the board is properly translated and inserted.  
3. If Error 1538 (hyperactivity) is listed in the Error Log, and run reset  
board UUCSS.  
4. Run the test again, and, if it fails, replace the ATM-TRK circuit pack.  
5. Retest.  
ATM Cross Talk Test (#1298)  
This nondestructive ATM Cross Talk test makes sure that TDM time slots are  
correctly allocated to connections. It is useful for diagnosing one-way or noisy  
connections. The test fails if the TDM programmable logic and/or the interface to  
the DSP is not operating properly. The test can take more than 10 minutes.  
Figure 3-182 shows a diagram of this test, substituting “CES mode” for “PNC  
mode.”  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ATM-TRK (Circuit Emulation Service Circuit Pack)  
3-257  
Table 3-114. ATM Crosstalk Test (#1298)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT Could not allocate required system resources.  
1. Retry the command up to 5 times at 1-minute intervals.  
1002  
ABORT Could not allocate time slots. Traffic may be heavy or time slots may be  
out-of-service.  
1. Identify and correct TDM-bus errors (if any) using the procedures in the  
TDM-BUS maintenance object.  
2. Repeat the test up to 5 times at 1-minute intervals.  
1003  
ABORT Could not allocate a tone receiver. Too few tone detectors installed or tone  
detectors out-of-service.  
1. Identify and correct any TTR-LEV errors listed in the Error Log.  
2. Resolve any TONE-PT errors listed in the Error Log.  
3. Retry the test up to 5 times at 1-minute intervals a maximum.  
ABORT Test timed out.  
2000  
2100  
ABORT Could not allocate required system resources  
1. Retry the command 5 times at 1-minute intervals.  
ABORT All TALKER DSPs are busy.  
1962  
2302  
ABORT Inconsistent uplink message from the ATM-TRK circuit pack.  
1. Retry the command up to 3 times at 1-minute intervals.  
ABORT The circuit pack in this location is not a TN2305A/2306A.  
2752  
1-8,  
None  
FAIL  
ATM-TRK circuit pack writing on unauthorized TDM time slots. The error  
code indicates the number of TALKER DSPs that are at fault. These DSPs  
cannot be used again until this test of the ATM DSP Test (#1293) tells the  
circuit pack to use them again.  
1. Retry the command up to 3 times at 1-minute intervals.  
2. If the failure persists, replace the circuit pack.  
1-8  
PASS  
ATM-TRK circuit pack not talking to un-authorized time slots on the TDM  
bus. The error code indicates the number of TALKER DSPs tested.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AXA12-BD/ADX8D-BD/AXD12-BD (AUDIX Circuit Packs)  
3-258  
AXA12-BD/ADX8D-BD/AXD12-BD  
(AUDIX Circuit Packs)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
Run  
Full Name of MO  
AUDIX Circuit Pack  
AUDIX Circuit Pack  
AUDIX Circuit Pack  
AUDIX Circuit Pack  
AUDIX Circuit Pack  
AUDIX Circuit Pack  
1
AXA12-BD  
AXA12-BD  
ADX8D-BD  
ADX8D-BD  
AXD12-BD  
AXD12-BD  
MINOR  
test board UUCSS sh  
WARNING  
MINOR  
test board UUCSS sh  
test board UUCSS sh  
test board UUCSS sh  
test board UUCSS sh  
test board UUCSS sh  
WARNING  
MINOR  
WARNING  
1
UU is the universal cabinet number (1 for PPN; 2-22 for EPNs). C is the carrier designation (A,  
B, C, D, or E). SS is the number of the slot in which the circuit pack resides )(01 to 21).  
The TN 568 is a DEFINITY AUDIX circuit pack that occupies 2 slots on a port  
carrier. The tests below apply only to switch-side maintenance, which tests circuit  
pack components related to the TDM bus interface. The AUDIX system has an  
extensive maintenance strategy of its own that is described in DEFINITY AUDIX  
System Maintenance, 585-300-110.  
AXA12-BD:  
On G3r V7 systems, TN568 DEFINITY AUDIX circuit packs (sometimes called  
Embedded AUDIX) operating in control-link mode appear to the system as  
TN746 Analog Line circuit packs with vintage greater than 50. For  
circuit-pack-level problems, see XXX-BD. The maintenance strategy for ports on  
the TN568 operating in control-link mode is described in ADXCL-PT.  
ADX8D-BD:  
On G3r V7 systems, TN568 DEFINITY AUDIX circuit packs operating in 8-port  
digital mode appear to the system as TN754 Digital Line circuit packs with  
vintage greater than 50. For circuit-pack-level problems, see XXX-BD. The  
maintenance strategy for ports on the TN568 operating in 8-port digital mode is  
described in ADXDP-PT.  
ADX12-BD:  
The ADX12-BD maintenance object represents a TN568 DEFINITY AUDIX circuit  
pack operating in 12-port digital (DP) mode. On G3r V7 systems, TN568  
DEFINITY AUDIX circuit packs operating in 12-port digital mode appear to the  
system as TN2181 Digital Line circuit packs with vintage greater than 50. For  
circuit-pack-level problems, see XXX-BD. Port-level problems are covered by  
ADX12D-PT.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
AXA12-RS/ADX8D-RS/AXD12-RS (AUDIX Reserve Slots)  
3-259  
AXA12-RS/ADX8D-RS/AXD12-RS  
(AUDIX Reserve Slots)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
Run  
Full Name of MO  
AXA12-RS  
ADX8D-RS  
AXD12-RS  
NONE  
NONE  
NONE  
NONE  
NONE  
NONE  
TN568 12-port analog  
reserve slot  
TN568 8-port digital reserve  
slot  
TN568 12-port digital  
reserve slot  
There are no tests associated with these MOs. Both the test board and busy out  
board commands abort when either is attempted on a reserved slot. An error  
message indicates that the slot is associated with the circuit pack that the TN568  
is emulating, but the requested operation is not valid. If there are errors logged  
against these maintenance objects, see XXX-BD.  
The TN568 circuit pack connects to the switch through a single slot in the  
backplane; however, the number of slots physically occupied by the circuit pack  
is supplied by the board when inserted. The TN568 is 2 slots wide: the functional  
slot and a reserve slot. The reserve (blank) slot to the left of the functional slot is a  
place holder on the switch and has no interaction with the switch.  
These MOs are place holders for the extra slot needed for the DEFINITY AUDIX  
board. Each instance of these MOs represents a reserve slot associated with the  
respective circuit pack mode in which the TN568 (DEFINITY AUDIX) is working.  
They are used for embedded AUDIX and emulation of respective port types.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack)  
3-260  
BRI-BD/LGATE-BD (ISDN-BRI Line  
Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
BRI-BD  
MAJOR  
MINOR  
test board PCSS l  
test board PCSS l  
test board PCSS sh  
test board PCSS l  
test board PCSS l  
test board PCSS sh  
ISDN-BRI Line Circuit Pack  
ISDN-BRI Line Circuit Pack  
ISDN-BRI Line Circuit Pack  
DEFINITY Lan Gateway  
DEFINITY Lan Gateway  
DEFINITY Lan Gateway  
BRI-BD  
BRI-BD  
WARNING  
MAJOR  
LGATE-BD  
LGATE-BD  
LGATE-BD  
MINOR  
WARNING  
1. Where P is the port network number (1 for PPN); C is the carrier designation (A, B, or  
C); and SS is the address of the slot in the carrier where the circuit pack is located  
(01, 02, ..., etc.).  
NOTE:  
Some of the information in this section is reserved for future use.  
ISDN-BRI Line is a packet port circuit pack that provides access to ISDN-BRI  
endpoints. The ISDN-BRI Line circuit pack supports 12 ports, each of which  
provides access to ISDN stations. Voice and circuit-switched data from the ISDN  
stations are carried on the Time Division Multiplex (TDM) Bus.  
LEDS  
The ISDN-BRI Line circuit pack performs extensive initialization tests and lights  
both the red and green LEDS during the initialization testing. See ‘‘LED  
Interpretation’’ in Chapter 1, ‘‘Maintenance for csi systems’’, for more details on  
circuit pack status LEDs.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack)  
3-261  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-115. BRI-BD Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test board PCSS sh r 1  
1(a)  
Any  
0
None  
MINOR  
ON  
18(b)  
busyout board  
PCSS  
WARNING  
OFF  
release board PCSS  
test board PCSS r 20  
23(c)  
0
None  
WARNING  
MINOR  
OFF  
ON  
257(d)  
65535  
Control Channel  
Loop Test (#52)  
513(e)  
4352 to  
4357  
769(f)  
4358  
4363  
1025(g)  
NPE Audit Test  
(#50)  
1293  
to  
1294 (h)  
46088  
to  
46096  
SAKI Sanity Test  
(#534)  
MINOR  
MINOR  
ON  
ON  
See footnote (h)  
1537 to  
1538 (i)  
46082  
1793 (j)  
1794 (j)  
1795 (j)  
2306 (j)  
46080  
46094  
46085  
MINOR  
MINOR  
MINOR  
ON  
ON  
ON  
LANBIC Receive  
Parity Error Counter  
Test (#595)  
3330 (k)  
3840 (l)  
46083  
MINOR  
OFF  
4096 to  
4101  
3843 (m)  
3999 (n)  
46097  
Any  
None  
Continued on next page  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack)  
3-262  
Notes:  
a. This error indicates the circuit pack totally stopped functioning or it was  
physically removed from the system.  
NOTE:  
The alarm is logged approximately 11 minutes after the circuit pack  
has been removed and/or SAKI Sanity Test (#53) fails.  
If the circuit pack is not in the system, insert a circuit pack (in the same  
slot as the error indicates) to resolve this error. Or, if the circuit pack is in  
the system and the red LED is on, then follow the instructions for a Red  
alarm in the ‘‘Control and Port Circuit Pack Status LEDs’’ section in  
Chapter 1, ‘‘Maintenance for csi systems’’.  
b. This circuit pack has been busied out via the busyout board PCSS  
command.  
c. Port(s) has(have) been administered on this circuit pack but the circuit  
pack is not physically present.  
d. This error indicates transient communication problems between the switch  
and this circuit pack. Execute the test board PCSS command and refer to  
the repair procedures for the Control Channel Loop Around Test (#52).  
e. An on-board hardware failure has been detected by the circuit pack.  
The reported aux data values correspond to the following detected errors:  
4352  
4353  
4355  
4357  
External RAM error  
Internal RAM error  
ROM Checksum error  
Instruction set error  
Reset the circuit pack by executing the busyout board PCSS and reset  
board PCSS commands. When it is reset, the circuit pack executes a set  
of tests to detect the presence of any of the above faults. The detection of  
one of these errors during initialization causes the circuit pack to lock-up  
and appear insane to the system. See the repair procedure in footnote (a)  
for error type 1.  
f. This error is reported by the circuit pack when it detects a program logic  
error. While no action is required, this error may lead to errors of other  
types being reported against this circuit pack.  
g. This error is reported by the circuit pack when it cannot update NPE  
memory and read it back. This error type can be ignored, but may lead to  
errors of other types being reported against this circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack)  
3-263  
h. A critical hardware failure has been detected on the circuit pack. Reset  
the circuit pack via the busyout board PCSS and reset board PCSS  
commands. If the Circuit Pack Restart Test (#594) passes, then the  
on-board circuitry is healthy. Retire the alarm via the test board PCSS  
long clear command. If the Circuit Pack Restart Test (#594) fails, replace  
the circuit pack.  
The reported error types correspond to the following detected errors:  
1293  
1294  
On-board auxiliary processor insane  
Internal memory access error  
i. These error types are reported when the following errors are detected:  
1537  
Frame overrun at Packet Bus interface. This condition may be caused  
by an on-board fault or by faulty data received on one of the circuit  
pack’s external ports. If any of the ports on this circuit pack are  
alarmed, refer to the repair procedures for those maintenance objects.  
1538  
Circuit packet is hyperactive; that is, it is flooding the switch with  
messages sent over the control channel. The circuit pack is taken  
out-of-service when a threshold number of these errors is reported to  
the switch. Clear the alarm via the following commands: busyout  
board PCSS, reset board PCSS, test board PCSS long clear,  
release board PCSS. If the error recurs within 10 minutes, then replace  
the circuit pack.  
j. These errors indicate that the circuit pack is having problems transmitting  
data to the Packet Bus.  
1793  
1794  
1795  
Parity errors are detected when transmitting data to the Packet Bus.  
Overflow of Packet Bus transmit buffers has occurred.  
Circuit pack cannot find end of frame when transmitting to Packet  
Bus. Clear the alarm via the following commands: busyout board  
PCSS, reset board PCSS, test board PCSS long clear, release  
board PCSS. If the error recurs within 10 minutes, then replace the  
circuit pack.  
2306  
This error occurs when the circuit pack detects an error in a received  
frame from the packet bus. These errors are most likely caused by a  
packet bus problem, but may be due to a circuit pack fault. An invalid  
Link Access Procedure Data (LAPD) frame error occurs if the frame  
contains a bad Cyclical Redundancy Checking (CRC), is greater than  
the maximum length, or violates the link level protocol. When bus  
parity errors are reported, the LANBIC Receive Parity Error Counter  
Test (#595) should be performed to determine if the condition had  
cleared.  
k. A critical failure has been detected in the Packet Bus interface of the  
circuit pack. This failure may be due to either a Packet Bus fault or an  
on-board fault. The probability of this error being related to Packet bus  
problems increases with the number of ISDN-BRI circuit packs displaying  
this error.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack)  
3-264  
If the Packet Bus is not alarmed, reset the circuit pack via the busyout  
board PCSS and reset board PCSS commands. If the Circuit Pack  
Restart Test (#594) passes, then the on-board circuitry is healthy. Retire  
the alarm via the test board PCSS long clear command. If the Circuit  
Pack Restart Test (#594) fails, replace the circuit pack. If the problem  
persists after complying with the above instructions, then follow normal  
escalation procedures.  
l. These errors are not service-affecting. No action is required. These errors  
are reported by the circuit pack when it receives a bad control channel  
message from the switch. The auxiliary data identifies the following error  
events:  
4096  
4097  
4098  
4099  
4100  
4101  
Bad major heading  
Bad port number  
Bad data  
Bad sub-qualifier  
State inconsistency  
Inconsistent downlink message  
m. This error is not service-affecting. No action is required.  
3843  
Bad translation RAM detected, but call continues by using another  
translation location.  
n. Error type 3999 Indicates that the circuit pack sent a large number of  
control channel messages to the switch within a short period of time. If  
error type 1538 is also present, then the circuit pack was taken  
out-of-service due to hyperactivity. If error type 1538 is not present, then  
the circuit pack has not been taken out-of-service, but it has generated  
50% of the messages necessary to be considered hyperactive. This may  
be completely normal during heavy traffic periods. However, if this error  
type is logged when the circuit pack is being lightly used, it may indicate a  
problem with the circuit pack or the equipment attached to it.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following tables when  
inspecting errors in the system. By clearing error codes associated with the  
Control Channel Loop Around Test, for example, you may also clear errors  
generated from other tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack)  
3-265  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Control Channel Loop-Around Test (#52)  
NPE Audit Test (#50)  
D/ND  
ND  
X
X
X
X
ND  
LANBIC Receive Parity Error Counter Test (#595)  
ND  
1. D = Destructive; ND = Nondestructive  
NPE Audit Test (#50)  
Refer to the repair procedure described in the "XXX-BD (Common Port Circuit  
Pack)" Maintenance documentation as NPE Audit Test (#50).  
Control Channel Loop Around Test (#52)  
Refer to the repair procedure described in the "XXX-BD (Common Port Circuit  
Pack)" Maintenance documentation as Control Channel Loop Around Test (#52).  
SAKI Sanity Test (#53)  
Refer to the repair procedure described in the "XXX-BD (Common Port Circuit  
Pack)" Maintenance documentation as SAKI Sanity Test (#53).  
LANBIC Receive Parity Error Counter Test (#595)  
This test is destructive.  
The test reads and clears the LANBIC Receive Parity Error Counter on the circuit  
pack. This counter is incremented by the circuit pack when it detects a parity  
error in data received from the Packet Bus.  
These errors may be indicative of a circuit pack problem, Packet Bus problem, or  
a problem with another circuit pack on the bus. This test is useful for verifying the  
repair of the problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack)  
3-266  
Table 3-116. TEST #595 LANBIC Receive Parity Error Counter Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received from the circuit pack within the  
allowable time period.  
1. If the test aborts repeatedly a maximum of 5 times, reset the circuit  
pack via the busyout board PCSS and reset board PCSS  
commands.  
2. If the test aborts again, replace the circuit pack.  
Could not allocate the necessary system resources to run this test.  
Internal system error  
2100  
2012  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1-10  
FAIL  
The circuit pack is still detecting errors of this type. The error code  
indicates the value of the on-board error counter.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, verify the validity of the Packet Bus. Run the  
Packet Bus maintenance test with the test pkt P long command.  
3. If the Packet Bus test passes, check the validity of the circuit pack.  
Execute a test that involves data transmission onto the Packet Bus. For  
example, the BRI may use the connectivity tests of the port-level  
maintenance object (BRI-PORT) by executing the test port PCSSpp  
command. Refer to the repair procedures for the executed test if it  
fails. Otherwise, proceed to the next step.  
4. Other circuit packs on the Packet Bus may be the cause of the parity  
error. Use the display errors command to check the Error Log for  
other circuit packs that are alarmed. If any alarms are present for the  
other circuit packs, retire those alarms also. Then, rerun the LANBIC  
Receive Parity Error Counter Test (#595) on this circuit pack.  
PASS  
No errors detected by circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
BRI-DAT (ISDN-BRI)  
3
3-267  
BRI-DAT (ISDN-BRI)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
Run  
Full Name of MO  
ISDN-BRI Standalone Data Module  
1
BRI-DAT  
WARNING  
test data-module  
1. The alarm level for ASAI adjuncts may be administered using the set options command. The  
alarm level can be set independently for Off-Board and On-Board alarms to WARNING, MINOR,  
or MAJOR for all ASAI adjuncts in the system.  
Refer to ‘‘BRI-SET, ASAI-ADJ, BRI-DAT’’ Maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-268  
BRI-PORT (ISDN-BRI Port),  
ABRI-PORT (ASAI ISDN-BRI Port)  
MO Name (in  
Alarm Log)  
Initial Command to  
1
Alarm Level  
MINOR  
Run  
Full Name of MO  
ISDN-BRI Port  
BRI-PORT  
BRI-PORT  
ABRI-PORT  
ABRI-PORT  
ATT-PORT  
ATT-PORT  
LGATE-PORT  
LGATE-PORT  
ATTE-PT  
test port PCSSpp l  
test port PCSSpp sh  
test port PCSSpp l  
test port PCSSpp l  
test port PCSSpp l  
test port PCSSpp l  
test port PCSSpp l  
test port PCSSpp l  
test port PCSSpp l  
test port PCSSpp l  
WARNING  
ISDN-BRI Port  
2 3  
MAJOR ,  
ASAI ISDN-BRI Port  
ASAI ISDN-BRI Port  
2 3  
WARNING ,  
2 3  
MAJOR ,  
Lucent Adjunct ISDN-BRI Port  
Lucent Adjunct ISDN-BRI Port  
Ethernet ASAI Port  
2 3  
WARNING ,  
2 3  
MAJOR ,  
2 3  
WARNING ,  
Ethernet ASAI Port  
2 3  
MAJOR ,  
Ethernet Lucent Adjunct Port  
Ethernet Lucent Adjunct Port  
2 3  
ATTE-PT  
WARNING ,  
1. Where P is the port network number (1 for PPN); C is the carrier designation (A, B, or C); and  
SS is the address of the slot in the carrier where the circuit pack is located (01, 02, ..., etc.);  
and pp is the 2-digit port number (for example, 01).  
2. The alarm level for ASAI and Lucent adjunct ports may be administered using the set  
options command. The alarm level can be set independently for Off-Board and On-Board  
alarms to WARNING, MINOR, or MAJOR for all ASAI and Lucent adjunct ports in the system.  
3. All alarming for an ASAI and Lucent adjunct and OFF-BOARD alarming for an ASAI or Lucent  
port is disabled if the ASAI or Lucent adjunct asks the switch to suspend maintenance. When  
this occurs, an error and a WARNING alarm is logged against the ASAI or Lucent adjunct.  
The Hardware Error and Alarm Logs should be checked to see if the adjunct has disabled  
alarming.  
NOTE:  
Some of the information in this section is reserved for future use.  
!
WARNING:  
If a significant Packet Bus failure occurs, errors and alarms may not be  
logged as expected for  
BRI-PORT/ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT.  
The TN2208 LGATE MFB provides DEFINITY with the interface to Adjunct-Switch  
Application Interface (ASAI) and Lucent adjuncts (for example, CONVERSANT®.  
Voice System). The circuit pack contains 12 ports of line circuit interface  
(although only 8 are usable by the switch), each of which operates with two  
B-channels (referred to as B1 and B2 throughout this section) and one D-channel  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-269  
as specified in the Lucent ISDN-BRI Specification. In this context, the term  
"ISDN-BRI port" is used to refer collectively to ports on the TN2208 circuit pack  
which are connected to ASAI or Lucent adjuncts.  
The TN556C and TN2198 ISDN-BRI Line circuit packs provide DEFINITY with the  
interface to ISDN-BRI end points, Adjunct-Switch Application Interface (ASAI)  
and Lucent adjuncts (for example, CONVERSANT®. Voice System). The circuit  
packs contain 12 ports of line circuit interface, each of which operates with two  
B-channels (referred to as B1 and B2 throughout this section) and one D-channel  
as specified in the Lucent ISDN-BRI Specification. In this context, the term  
"ISDN-BRI port" is used to refer collectively to ports on the TN556C and TN2198  
circuit packs which are connected to either BRI endpoints or ASAI or Lucent  
adjuncts.  
For BRI endpoints, each B-channel may support voice or circuit-switched data  
and may be circuit-switched simultaneously. The B-channels are not used on  
ports connected to ASAI or Lucent adjuncts. The D-channel is used for  
conveying signaling between the switch and a BRI endpoint(s) or ASAI or Lucent  
adjunct.  
ISDN-BRI endpoints are available in various configurations. All endpoints require  
the D-channel to convey signaling information to the switch. Only one B-channel  
is required for a voice-only set or a stand-alone data module (BRI-DAT). A voice  
and data-capable set requires both B-channels (one for voice and one for data).  
Therefore, each TN556 or TN2198 port can support either two voice-only sets,  
two stand-alone data modules (BRI-DAT), or one voice and data-capable set.  
Only a single ASAI or Lucent adjunct may be connected to an ISDN-BRI port.  
Multiple adjuncts per line are not supported.  
Figure 3-11 illustrates the physical connection (solid line) between an ISDN-BRI  
Port and its associated ISDN-BRI set(s). Each physical connection allows for two  
B-channels and one D-channel. Each ISDN-BRI circuit pack can support up to  
12 of these physical connections to different voice and voice/data sets or ASAI or  
Lucent adjuncts. On a TN2198 each ISDN-BRI circuit pack can support up to 12  
physical connections to a NT1, which, in turn, connects to 2 terminals.  
This section covers the maintenance documentation for ISDN-BRI ports. Some of  
the results of maintenance testing of ISDN-BRI ports may be affected by the  
health of the ISDN-BRI Line circuit pack (BRI-BD), BRI endpoint (BRI-SET), or  
ASAI adjunct (ASAI-AJ/LGATE-AJ) or Lucent adjunct (ATT_AJ/ATTE-AJ). These  
interactions should be kept in mind when investigating the cause of ISDN-BRI  
port problems. For more information on the circuit pack and endpoints, refer to  
the BRI-BD (ISDN-BRI Line Circuit Pack) Maintenance documentation, the  
BRI-SET (ISDN-BRI Endpoint) Maintenance documentation, and ASAI-AJ  
(Adjunct-Switch Application Interface) Maintenance documentation, ATT-AJ  
(Lucent Adjunct) Maintenance documentation, LGATE-AJ (Ethernet  
Adjunct-Switch Application Interface) Maintenance documentation, and ATTE-AJ  
(Ethernet Lucent Adjunct) Maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-270  
VOICE  
OR DATA  
TERMINAL  
BRI LINE  
CIRCUIT  
PACK  
D-CHANNEL  
B-CHANNEL  
B-CHANNEL  
DEFINITY  
COMMUNICATIONS  
SYSTEM  
P
O
R
T
VOICE  
OR DATA  
TERMINAL  
LOGICAL CONNECTION  
PHYSICAL CONNECTION  
Figure 3-11. ISDN-BRI Port Interactions  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-117. ISDN-BRI Port Error Log Entries  
Alarm Level  
ABRI-PORT  
ATT-PORT  
LGATE-PORT  
ATTE-PT  
Alarm  
Level  
BRI-PORT  
On/  
Off  
Board  
Error  
Type  
Aux  
Data  
Test to Clear  
Value  
Associated Test  
1
0
0
Any  
Any  
Any  
Any  
OFF  
OFF  
ON  
test port  
PCSSpp sh r 1  
2
1 (a)  
(a)  
Level 1 Status  
Inquiry (#621)  
WRN  
WRN  
WRN  
WRN  
(d)  
MAJ/MIN/ WRN  
test port  
PCSSpp sh r 2  
18  
busyout port  
PCSSpp  
release port  
PCSSpp  
130 (b)  
257 (c)  
513 (d)  
test port PCSS  
sh  
2
(c)  
(d)  
EPF Inquiry  
(#622)  
MAJ/MIN/ WRN  
OFF  
ON  
test port  
PCSSpp sh r 1  
none  
(d)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-271  
Table 3-117. ISDN-BRI Port Error Log Entries — Continued  
Alarm Level  
ABRI-PORT  
ATT-PORT  
LGATE-PORT  
ATTE-PT  
Alarm  
Level  
BRI-PORT  
On/  
Off  
Board  
Error  
Type  
Aux  
Data  
Test to Clear  
Value  
Associated Test  
769 (e)  
1281 (f)  
0
none  
WRN  
MAJ  
OFF  
ON  
2
NPE Crosstalk  
(#617)  
MIN/ WRN  
test port  
PCSSpp l r 2  
2
1537 (g)  
1793 (h)  
46210  
CRC Error  
Counter (#623)  
WRN  
MAJ/MIN/ WRN  
OFF  
ON  
2
BRI Port Local  
TDM  
MIN/ WRN  
test port  
PCSSpp l r 2  
Loop Around  
(#619)  
3841 (i)  
3842 (j)  
3843 (k)  
3844 (l)  
3845 (m)  
3846 (n)  
3847 (o)  
46208  
None  
None  
None  
None  
None  
None  
None  
0
0
46223  
TEI  
0
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description, and follow the recommended procedures.  
2. Major and Minor alarms on this MO may be downgraded to Warning alarms based on the value used in  
the set options command.  
Notes:  
a. This error occurs when the Level 1 Status Inquiry fails or when the BRI  
circuit pack detects that Level 1 has been deactivated on the port. The  
aux data field contains one of the following values:  
■
blank - this indicates that the Level 1 Status Inquiry failed.  
■
32773 - this is a message from the BRI-LINE circuit pack indicating  
Level 1 has been deactivated.  
Refer to the repair procedures for Test #621.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-272  
b. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, replace or  
reinsert the circuit pack.  
c. This error occurs when the EPF Status Inquiry fails due to an overcurrent  
condition or when the BRI-LINE circuit pack detects that the EPF is in an  
over current condition. The aux data field contains one of the following  
values:  
■
blank - this indicates that the EPF Status Inquiry failed due to an  
overcurrent condition.  
■
40988 - this indicates that the BRI-LINE circuit pack has detected  
an overcurrent condition and has turned the EPF off.  
Execute the Short Test Sequence and see the repair procedures for Test  
#622.  
d. This error indicates that the circuit pack is having problems transmitting  
data to the Packet Bus, thus affecting the conveyance of signaling  
information over the D-channel. With Aux Data 46222, this error occurs  
when the Packet Bus transmit buffers overflow. This condition probably  
indicates a hardware problem. The BRI-PORT Alarm Level for the error  
with Aux Data 46222 is "MIN/WRN," and the  
ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT Alarm Level is  
"MAJ/MIN/WNR." With Aux Data 0, this error occurs whenever the Packet  
Bus transmit FIFO buffers overflow. This condition can be caused by an  
on-board hardware problem as well as by problems on the Packet Bus  
that disrupt the BRI circuit pack’s ability to transmit data onto the Packet  
Bus. Use troubleshooting procedures for both on-board hardware  
problems and potential off-board Packet Bus problems. See the "PKT-BUS  
(Packet Bus)" Maintenance section in this chapter as well as Chapter 9,  
"Packet Bus Fault Isolation and Correction" for more details on Packet Bus  
troubleshooting procedures. The BRI-PORT Alarm Level for the error with  
Aux Data 0 is "MINOR,"and the ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT  
Alarm Level is "MAJOR."  
e. This error occurs when the NPE Crosstalk Test (#617) fails. Run the Long  
Test Sequence, and pay particular attention to the results of Test #617.  
f. This error occurs when broadcast signaling links associated with this port  
have too much link establishment related traffic. This could occur if an  
endpoint on this port is sending link establishment traffic on a port level  
broadcast link, or if there are Level 1 problems on the port. Check the error  
logs for Level 1 errors. If Level 1 problems exist, follow the repair  
procedures listed for test #621. Software will suspend activity to this port  
for 75 minutes when the port is alarmed due to this error (note that service  
suspension does not occur if the port is an  
ABRI-PORT/LGATE-PT/ATTE-PT/ATT-PORT). If this problem persists,  
replace the endpoint or endpoints associated with this port. If replacing  
the endpoints does not fix the problem, follow normal escalation  
procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-273  
g. This error occurs when the port receives an invalid frame over the  
D-channel. When CRC errors exceed five within 15 minutes, the port is  
taken out of service for five seconds. If five more CRC errors are received  
within 15 minutes of the first set of five errors, the port is taken out of  
service for one minute. If five more CRC errors are received within 15  
minutes of the last five, the port is taken out of service for 15 minutes.  
This error is most likely due to a problem with the wiring to the set or  
adjunct, interference on the wiring due to a noise source or no termination  
(an open circuit). It usually does not indicate a problem with the circuit  
pack.  
■
Check the wiring to the endpoints or the adjunct.  
■
If the problem persists, replace the endpoints or adjuncts.  
h. This error occurs when the BRI Port Local TDM Loop Around Test (#619)  
fails. Run the Long Test Sequence, and pay particular attention to the  
results of Test #619.  
There are no Test to Clear Values for the following error types. The error  
types are simply provided as additional data that may prove useful while  
troubleshooting.  
i. This error occurs when a Layer 1 Transmission error is detected for the  
port. Run the Long Test Sequence, and pay particular attention to the  
results of the Layer 1 Transmission Error Counter Test (#624).  
j. A BRI port supports up to three Terminal Endpoint Identifiers (TEIs). This  
error occurs when the switch receives a request for a fourth TEI on a port.  
Check the number of endpoints administered for this port.  
k. This error occurs when an SPID initialization request is made from an  
endpoint and the switch determines that the SPID value is invalid or is a  
duplicate of another SPID that is already initialized at Layer 3 on the port.  
Check the administration of the endpoints.  
l. This error occurs when the circuit pack detects an overflow of its receive  
buffers. Run the Long Test Sequence, and pay particular attention to the  
results of the Receive First In First Out (FIFO) Overflow Error Counter Test  
(#625).  
m. This error occurs when the BRI Port Local LAN Loop Around Test (#618)  
fails. Run the Long Test Sequence, and pay particular attention to the  
results of Test #618.  
n. This error most likely occurs when the Terminal Endpoint Identifier (TEI)  
administered for the ASAI or Lucent endpoint does not match the TEI  
administered in the ASAI or Lucent adjunct. Check the switch  
administration of the TEI against that of the adjunct, and make sure that  
both are using the same TEI.  
o. Indicates that sets on the port do not support Layer 3 initialization. Consult  
the Service Set documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-274  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following tables when  
inspecting errors in the system. By clearing error codes associated with the NPE  
Crosstalk Test, for example, you may also clear errors generated from other tests  
in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#617)  
D/ND  
D
X
X
X
X
X
X
X
X
X
X
BRI Port Local LAN Loop Around Test (#618)  
BRI Port Local TDM Loop Around Test (#619)  
Electronic Power Feed Restoral Test (#620)  
Level 1 Status Inquiry Test (#621)  
D
D
X
X
X
ND  
ND  
ND  
ND  
ND  
ND  
ND  
Electronic Power Feed Inquiry Test (#622)  
CRC Error Counter Test (#623)  
Layer 1 Transmission Error Counter Test (#624)  
Receive FIFO Overflow Error Counter Test (#625)  
Clear Error Counters (#270)  
X
1. D = Destructive; ND = Nondestructive  
NOTE:  
The NPE Crosstalk Test and the BRI Port Local TDM Loop Around Test are  
not executed for ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT.  
NPE Crosstalk Test (#617)  
This test is destructive.  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain and provides conferencing functions on  
a per-port basis. The NPECrosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is part of a port’s Long Test Sequence and takes  
approximately 20 to 30 seconds to complete. Crosstalk testing is performed on  
both B-channels (B1 and B2) associated with a BRI port. If this test fails on either  
channel, any endpoints connected to the port are taken out-of-service.  
This test is not executed for ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT because  
the B-channels associated with the port are not used by ASAI or Lucent adjuncts.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-275  
Table 3-118. TEST #161 Loop Around Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension or trunk group/member number of the port.  
Use the status bri-port PCSSpp command to determine the service state  
of the port. If the service state indicates that the port is in use, then the port  
is unavailable for certain tests. Wait until the port is idle before retesting.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
1005  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use the status station  
command for the station associated with this port and determine when the  
port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
This test is not valid for this type of translation. Ports administered as  
“ASAI” or “ADJK” can not run this test, because the B channels associated  
with the port are not used by ASAI or Lucent Adjunct Links. This is a  
normal condition.  
2012  
2100  
ABORT  
ABORT  
Internal system error  
Could not allocate the necessary resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1, 2  
FAIL  
The NPE of the tested port was found to be transmitting in error. This  
causes noisy and unreliable connections. Error code 1 indicates that the  
NPE Crosstalk Test failed on Channel B1. Error code 2 indicates that the  
NPE Crosstalk Test failed on Channel B1.  
1. Replace circuit pack.  
PASS  
The port is correctly using its allocated time slots.  
1. To be sure that this is not an intermittent problem, repeat this test a  
maximum of 10 times to make sure it continues to pass.  
2. If complaints still exist, examine the station, connections, and wiring.  
BRI Port Local LAN Loop Around Test (#618)  
This test is destructive.  
This test, which verifies the connectivity of a BRI port across the LAN Bus,  
executes only if the port is out-of-service. The test aborts if calls associated with  
the port are in-progress. Failures of this test indicate either on-board faults  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-276  
associated with the BRI-PORT hardware on the circuit pack or problems with the  
LAN Bus, which is used to form connectivity between the switch and the  
BRI-PORT.  
The dotted lines in Figure 3-12 show how a Loop Around Test is performed  
across the Packet Bus for the D-channel.  
PACKET  
INTERFACE  
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
PACKET BUS  
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . .  
BRI LINE  
CIRCUIT  
PACK  
Figure 3-12. Path of the BRI Port Local LAN Loop Around  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-277  
Table 3-119. TEST #618 BRI Port Local LAN Loop Around  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1015  
ABORT  
The port is not in the out-of-service service state.  
1. Display the BRI Port Status form via the status bri-port PCSSpp  
command to determine which stations or adjuncts are on this port.  
2. Use the extension shown on this form in the status station command  
to determine if the station or adjunct is in use.  
3. If it is in use, wait until it is idle, and then busyout the port (using the  
busyout port PCSSpp command) to place it in the out-of-service  
state and repeat this test.  
!
WARNING:  
Since the "busyout" command is destructive, execution of this  
command prior to the port being idle causes all calls associated with  
BRI endpoints and all transactions associated with ASAI or Lucent  
adjuncts on the port to be torn down. Note that third party calls  
established by an ASAI or Lucent adjunct remain connected even  
though the port is taken out-of-service.  
1139  
1141  
1144  
ABORT  
ABORT  
ABORT  
The Packet Bus in the port network is out-of-service.  
1. Follow the repair procedures for the Packet Bus.  
2. After completing Step 1, execute the test port long PCSSpp  
command, and review the results of the BRI Port Local LAN Loop  
Around Test to verify the repair.  
The PKT-CTRL is out-of-service.  
1. Follow the repair procedures for the PKT-CTRL.  
2. After completing Step 1, execute the test port long PCSSpp  
command, and review the results of the BRI Port Local LAN Loop  
Around Test to verify the repair.  
The PPN Packet Bus is out-of-service.  
1. Follow the repair procedures for the Packet Bus.  
2. After completing Step 1, execute the test port long PCSSpp  
command, and review the results of the BRI Port Local LAN Loop  
Around Test to verify the repair.  
2012  
2100  
ABORT  
ABORT  
Internal system error  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-278  
Table 3-119. TEST #618 BRI Port Local LAN Loop Around — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The Loop Around Test has failed.  
FAIL  
1. If the test fails repeatedly, attempt to reset the circuit pack if the other  
ports on the board are not in use. Reset the circuit pack by issuing the  
busyout board PCSS and the reset board PCSS commands.  
2. If the test fails again, execute test pkt P on the G3MT terminal. If this  
fails, follow failure procedures in PKT-BUS section.  
3. If tests executed in Step 2 pass, the problem is local to the BRI board.  
Replace the circuit pack.  
PASS  
The BRI Port Local LAN Loop Around Test has passed.  
BRI Port Local TDM Loop Around Test (#619)  
This test is destructive.  
This test verifies the connectivity of a BRI port across the TDM Bus. It aborts if  
calls associated with the port are in progress. Failure of this test indicates an  
on-board fault associated with the port hardware on the circuit pack.  
This Loop Around Test runs a series of individual tests on the two B-channels (B1  
and B2) associated with the port. It is a collection of the following:  
■
■
■
■
A Loop Around Test across the TDM Bus for B1.  
A Conference Circuit Test for B1.  
A Loop Around Test across the TDM Bus for B2.  
A Conference Circuit Test for B2.  
The tests are run in the above order. If one fails, the remaining tests in the  
sequence are not executed. An error code is returned at that point.  
This test is not executed for ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT because  
the B-channels associated with the port are not used by ASAI or Lucent adjuncts.  
The dotted lines in Figure 3-13 show how a Loop Around Test is performed for the  
B-channels. The figure shows a terminal connected to a BRI line board using a  
TN556. If a TN2198 is used, the terminal would be connected to a NT1, and the  
NT1 to the BRI board.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-279  
Tone  
Tone  
Generator  
Detector  
TDM Bus  
BRI Line  
Board  
Figure 3-13. Path of the BRI Port Local TDM Loop Around  
Table 3-120. TEST #619 BRI Port Local TDM Loop Around  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
The system resources required to run this test are not available. The port  
may be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension or trunk group/member number of the port.  
Use the status bri-port PCSSpp command to determine the service state  
of the port. If the service state indicates that the port is in use, then the port  
is unavailable for certain tests. Wait until the port is idle before retesting.  
1. If the port is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1002  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM Bus) Maintenance  
documentation to diagnose any active TDM Bus errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-280  
Table 3-120. TEST #619 BRI Port Local TDM Loop Around — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
(TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port has been seized by a user for a valid call. Use the status station  
command for the station associated with this port and determine when the  
port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1005  
ABORT  
This test is not valid for this type of translation. Ports administered as  
“ASAI” or “ADJK” can not run this test, because the B channels associated  
with the port are not used by ASAI or Lucent Adjunct Links. This is a  
normal condition.  
2000  
ABORT  
Response to the test was not received from the BRI-LINE circuit pack  
within the allowable time period.  
1. If this result occurs repeatedly, attempt to reset the circuit pack if the  
other ports are not in use. Reset the circuit pack by issuing the  
busyout board PCSS and the reset board PCSS commands.  
2. If this result occurs again, replace the circuit pack.  
Internal system error.  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not make the conference connection for the test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2103  
1, 2  
ABORT  
FAIL  
As stated previously, this test runs a TDM Loop Around Test on each  
B-channel. This indicates that the loop around failed on one of the  
channels. Error Code 1 indicates that the TDM Loop Around Test failed on  
B1. Error Code 2 indicates that the TDM Loop Around Test failed on B2.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-281  
Table 3-120. TEST #619 BRI Port Local TDM Loop Around — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
7, 8  
FAIL  
As stated previously, this test runs a Conference Circuit Test on each  
B-channel. A failure here indicates that one of these conference tests  
failed; Error Code 7 means that the test failed on B1; Error Code 8 means  
that the test failed on B2.  
1. If the test fails repeatedly, attempt to reset the circuit pack if the other  
ports on the circuit pack are not in use. Reset the circuit pack by  
issuing the busyout board PCSS and the reset board PCSS  
commands.  
2. If the test fails again, replace the circuit pack.  
PASS  
The BRI Port Local TDM Loop Around Test has passed.  
Electronic Power Feed Restoral Test (#620)  
This test attempts to restore the Electronic Power Feed (EPF) on an ISDN-BRI  
port twice. In this test, the processor requests that the EPF be turned on for a  
given port. An attempt is made to turn on the power unit to the station or adjunct.  
If no current is being drawn by a station, this probably indicates that the station is  
not connected. No current being drawn by an adjunct is the normal condition. If  
an overcurrent condition is sensed (that is, too much current is being drawn), this  
condition may indicate a short in the wiring to the endpoint or adjunct.  
Depending on what condition is sensed, a message is returned stating that either  
the EPF was turned on successfully with no problems or that an overcurrent  
condition is sensed. This response is reported by the Electronic Power Feed  
Inquiry (#622), which follows in the testing sequence. EPF Restoral is attempted  
again by this test five seconds later. This test always passes for the TN2198  
because it has no EPF. This test will always abort when run on the TN2208.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-282  
Table 3-121. TEST #620 Electronic Power Feed Restoral  
Error  
Code  
Test  
Result  
Description / Recommendation  
1005  
ABORT  
ABORT  
This test is not valid for this port type. The TN2208 does not  
have an electronic power feed, and the test will abort.  
2012  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5  
times.  
PASS  
The EPF Test passed. The message to turn on the power feed  
to the station or the adjunct was successfully sent to the port.  
1. Although this test should not return a fail result, after  
running this test, the Error Log should be checked for any  
entries with error type 257 to examine the real results of  
this test.  
2. An error type of 257 in the Error Log indicates some  
problem with the power to the station or the adjunct.  
Check for a short in the wiring, a damaged jack, a  
defective voice terminal or adjunct, or an incorrect type of  
terminal.  
Level 1 Status Inquiry Test (#621)  
This test determines the state of the transmission facility of a BRI port at the  
physical layer (that is, Level 1). Level 1 can be in one of three possible states:  
Activated, Pending Activation, or Deactivated.  
The Activated state is the correct state for an ISDN-BRI port. In this state the  
Level 1 interface can communicate with the BRI endpoint or ASAI or Lucent  
adjunct administered on this port. This test passes if the state of Level 1 (L1) is  
Activated. This test also passes if software has taken this port out of service. See  
the description of the Level 1 "Deactivated State" below for more details.  
The Pending Activation state indicates a problem with the endpoints or adjunct,  
the wiring to the sets or adjunct, or the BRI-LINE circuit pack. When in this state,  
the Level 1 interface is either not receiving any L1 framing from the endpoint or  
adjunct (Endpoint Idle), or it is communicating with the endpoint or adjunct but  
cannot transition to the Activated state (Endpoint Active).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-283  
The Deactivated state indicates a problem with the BRI-LINE circuit pack. When  
in this state, the Level 1 interface is idle and is not trying to communicate with the  
BRI endpoints or adjunct. When an ISDN-BRI port is placed in the out-of-service  
state, Level 1 is also put into the Deactivated state. This could be due either to  
the system detecting a fault with the port or to a busyout port PCSSpp request.  
Table 3-122. TEST #621 Level 1 Status Inquiry  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1187  
ABORT  
The board, port or station may have been busied out by a technician.  
1. Look in the Error Log for Error Type 18 (port busied out) for this port  
and BRI-BD (board busied out). If this error type is present for  
BRI-PORT only, then release the port via the release port pp  
command and run the test again. If the error is present for both BRI-BD  
and BRI-PORT, then release the board via the release port PCSS  
command and run the test again.  
NOTE:  
When you release a port, you release all ports associated with it. If  
certain ports still need to be busied out, use the release port  
PCSSpp command to busy them out.  
2. Make sure the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
ABORT  
Response to the test was not received from the circuit pack within the  
allowable time period.  
1. If the test aborts repeatedly a maximum of 5 times, reset the circuit  
pack via the busyout board PCSS and reset board PCSS  
commands.  
2. If the test aborts again, replace the circuit pack.  
Internal system error.  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-284  
Table 3-122. TEST #621 Level 1 Status Inquiry — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
FAIL  
Received a status of Level 1 Pending Activation-Endpoint Idle which  
indicates a problem with the BRI endpoint or ASAI or Lucent adjunct, the  
wiring to the endpoint or adjunct, or the ISDN-BRI port.  
For the TN2198, received a status of Level 1 Pending Activation. U  
interface down, which indicates a problem with a connection between the  
switch and the NT1.  
NOTE:  
An NT1 is a 2- to 4-wire converter that is used to connect 4-wire  
Lucent terminals to a 2-wire TN2198 circuit pack. The NT1 also has  
status lamps to determine the health of the unit.  
1. For the TN556 or TN2208, verify that an endpoint is connected to the  
port. If an endpoint is connected to the port, then proceed to step 2.  
For the TN2198 verify that the connections are good between the  
switch and the NT1. Verify that the NT1 has power.  
2. As necessary, check and repair the wiring between the circuit pack  
and the endpoint or adjunct. If a TN2198 is used, the set must have  
been plugged in for at least 15 seconds before it will stabilize. Execute  
the test port PCSSpp command, and review the results of the Level 1  
Status Inquiry Test to verify the repair. If this test is still failing, proceed  
to Step 3.  
3. For BRI endpoints, replace the BRI endpoint(s) connected to the port  
or the NT1 if a TN2198 is used. For ASAI or Lucent adjuncts, follow the  
recommended repair procedures of the manufacturer for link  
communication problems. For the NT1, follow the manufacturers repair  
procedures. Then execute the test port PCSSpp command and  
review the results of the Level 1 Status Inquiry Test to verify repair. If  
this test is still failing, proceed to Step 4.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-285  
Table 3-122. TEST #621 Level 1 Status Inquiry — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2
FAIL  
For the TN556 or TN2208, received a status of Level 1 Pending  
Activation-Endpoint Active which indicates a problem with the BRI  
endpoint or ASAI or Lucent adjunct, the wiring to the endpoint or adjunct,  
or the ISDN-BRI port.  
For the TN2198, received a status of Level 1 Pending Activation. U  
interface up S/T interface down, which indicates a problem with the NT1 or  
the wiring between the NT1 and the BRI endpoint (S/T interface).  
1. As necessary, check and repair the wiring between the circuit pack  
and the endpoint or adjunct. Execute the test port PCSSpp  
command, and review the results of the Level 1 Status Inquiry test to  
verify the repair. If this test is still failing, proceed to Step 2.  
2. For BRI endpoints, try replacing the BRI endpoint(s) connected to the  
port. For ASAI or Lucent adjuncts, follow the recommended repair  
procedures of the manufacturer for link communication problems. For  
the NT1, follow the recommended repair procedures of the  
manufacturer. Then execute the test port PCSSpp command, and  
review the results of the Level 1 Status Inquiry test to verify repair.  
3
FAIL  
Received a status of Level 1 Deactivated; the port is out-of-service.  
1. Issue the status bri-port PCSSpp command to verify that the service  
state of the port is out-of-service. If the service state of the port is not  
out-of-service, proceed to Step 2.  
2. If the port has been placed out-of-service via the busyout port  
PCSSpp command, try releasing the port by executing the release  
port PCSSpp command. Then issue the test port long PCSSpp  
command, and review the results of Level 1 Status Inquiry test. If this  
test is still failing, proceed to Step 3.  
3. After executing the test port long PCSSpp command, review the  
results of all the tests. Follow the repair procedures for any tests that  
fail. Verify repair of the problem by executing the test port PCSSpp  
command and by determining that the Level 1 Status test passes.  
4
FAIL  
For the TN2198 only:  
Received a status of Level 1 Pending Activation, the NT1 has a loss of  
power indicating a problem with the NT1.  
1. For the NT1 follow the manufacturers recommended repair  
procedures.  
2. Execute the test port PCSSpp command, and review the results of the  
Level 1 Status Inquiry test to verify the repair.  
PASS  
This test indicates that Level 1 is activated, or that software has taken the  
port out of service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-286  
Electronic Power Feed Inquiry (#622)  
This test queries the BRI-LINE circuit pack for the status of the Electronic Power  
Feed (EPF) supplied to a BRI endpoint or an ASAI or Lucent adjunct. If the EPF is  
on and no overcurrent condition exists, this test passes. All other states are not  
normal and indicate a problem with the endpoint or adjunct, the wiring to the  
endpoint or adjunct, or the BRI-LINE circuit pack. This test is not run on the  
TN2208 circuit pack or the TN2198 and will always return a pass for a TN2198.  
The TN2208 has no power feeds.  
Table 3-123. TEST #622 Electronic Power Feed Inquiry  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1005  
ABORT  
ABORT  
This test is not valid for this port type. Ports on the TN2208 cannot run  
this test because this board does not have an electronic power feed.  
2000  
Response to the test was not received from the circuit pack within the  
allowable time period.  
1. If the test aborts repeatedly a maximum of 5 times, reset the circuit  
pack via the busyout board PCSS and reset board PCSS  
commands.  
2. If the test aborts again, replace the circuit pack.  
Internal system error.  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1
FAIL  
The BRI-LINE circuit pack reports that it has detected an overcurrent  
condition and has turned off the EPF.  
1. As necessary, check and repair the wiring between the circuit pack  
and the endpoint or adjunct. Check the endpoints and replace one  
or both sets if the sets are drawing too much current. Execute the  
test port PCSSpp command and review the results of the EPF  
Inquiry Test to verify the repair. If this test is still failing, proceed to  
Step 2.  
2. Execute the test port PCSSpp command, and review the results of  
the Level 1 Status Inquiry Test. If this test is also failing, then follow  
the repair procedure for the Level 1 Status Inquiry Test.  
2000  
ABORT  
Response to the test was not received from the circuit pack within the  
allowable time period.  
1. If the test aborts repeatedly a maximum of 5 times, reset the circuit  
pack via the busyout board PCSS and reset board PCSS  
commands.  
2. If the test aborts again, replace the circuit pack.  
PASS  
The Electronic Power Feed Inquiry Test reports that the EPF is on.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-287  
Layer 1 Transmission Error Counter Test (#624)  
This test reads and clears the BRI port’s Layer 1 Transmission error counter  
maintained on the BRI-LINE circuit pack. This counter is incremented by the  
circuit pack when it detects a Layer 1 transmission problem. The test passes if  
the value of the counter is 0 (that is, the error is cleared). If the counter is not zero,  
the test fails, and the value of the counter is displayed in the Error Code field.  
This error is most likely due to a problem with the wiring or the endpoint or  
adjunct (verify that the wiring meets the configuration rules defined in DEFINITY  
Communications System Generic 1 and Generic 3i Wiring, 555-204-111). It does  
not indicate a problem with the ISDN-BRI circuit pack. This test is useful for  
verifying the repair of the problem.  
Table 3-124. TEST #624 Layer 1 Transmission Error Counter Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received from the circuit pack within the  
allowable time period.  
1. If the test aborts repeatedly a maximum of 5 times, reset the circuit  
pack via the busyout board PCSS and reset board PCSS  
commands.  
2. If the test aborts again, replace the circuit pack.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate necessary system resources to run test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
value  
FAIL  
The BRI-LINE circuit pack is still detecting errors of this type. The Error  
Code field contains the value of this counter.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, review the results of other tests in the  
Long Test Sequence. Pay particular attention to the results of the  
Level 1 Status Inquiry test. Follow repair procedures for any of the  
executed tests if they fail. Otherwise, go to the next step.  
3. If the tests for the endpoints or adjunct pass and the Layer 1  
Transmission Error Counter Test continues to fail, check the wiring  
to the endpoints or adjunct.  
PASS  
The Layer 1 Transmission error counter was read correctly and has a  
value of 0.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-288  
Receive FIFO Overflow Error Counter Test (#625)  
This test reads and clears the BRI port’s Receive FIFO Overflow error counter  
maintained on the BRI-LINE circuit pack. This counter is incremented by the  
circuit pack when it detects an overflow of its receive buffers. The test passes if  
the value of the counter is 0 (that is, the error is cleared). If the counter is  
non-zero, the test fails, and the value of the counter is displayed in the Error Code  
field.  
This error can occur if signaling frames are being received from the Packet Bus  
at a rate sufficient to overflow the receive buffers on the circuit pack for a port OR  
if a hardware fault is causing the receive buffers not to be emptied properly by  
the circuit pack. This test is useful for verifying the repair of the problem.  
Table 3-125. TEST #625 Receive FIFO Overflow Error Counter Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received from the circuit pack within the  
allowable time period.  
1. If the test aborts repeatedly a maximum of 5 times, reset the circuit  
pack via the busyout board PCSS and reset board PCSS  
commands.  
2. If the test aborts again, replace the circuit pack.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
value  
FAIL  
The BRI-LINE circuit pack is still detecting errors of this type. The Error  
Code field contains the value of this counter.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, run the Long Test Sequence and pay  
particular attention to the Loop Around Tests (#618 and #619). See  
the repair procedures for the executed test if it fails. Otherwise, go  
to the next step.  
3. Replace the circuit pack.  
PASS  
The Receive FIFO Overflow error counter was read correctly and has a  
value of 0.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port)  
3-289  
Clear Error Counters Test (#270)  
This test is not an actual test in the strict sense of the word. There are various  
error counters associated with each  
BRI-PORT/ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT. This test clears those  
counters and triggers the auditing of Terminal Endpoint Identifier (TEI) values and  
layer 3 reinitialization. This test is used only to send messages to the  
BRI-PORT/ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT and, therefore, should  
neither abort nor fail.  
Table 3-126. TEST #270 Clear Error Counters  
Error  
Code  
Test  
Result  
Description/ Recommendation  
This test should never abort.  
Any  
Any  
ABORT  
FAIL  
This test should never fail.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
The message to clear the error counters of the  
BRI-Port/ABRI-Port/ATT-PORT/LGATE-PT/ATTE-PT has been sent.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-290  
BRI-SET, ASAI-ADJ, BRI-DAT  
MO Name (in  
Alarm Log)  
1
Alarm Level  
Initial Command to Run  
Full Name of MO  
2
BRI-SET  
WARNING  
test station extension l,  
ISDN-BRI Set  
test data-module extension  
2
ASAI-ADJ  
ASAI-ADJ  
ASAI-ADJ  
ATT-ADJ  
ATT-ADJ  
ATT-ADJ  
LGATE-AJ  
LGATE-AJ  
LGATE-AJ  
ATTE-AJ  
MAJOR  
test station extension  
test data-module extension  
test data-module extension  
test station extension  
test station extension  
test station extension  
test station extension  
test station extension  
test station extension  
test station extension  
ASAI-Adjunct  
2
MAJOR  
ASAI-Adjunct  
3
WARNING  
ASAI-Adjunct  
2
MAJOR  
Lucent-Adjunct  
2
MAJOR  
Lucent-Adjunct  
3
WARNING  
Lucent-Adjunct  
2
MAJOR  
Ethernet ASAI-Adjunct  
Ethernet ASAI-Adjunct  
Ethernet ASAI-Adjunct  
2
MAJOR  
3
WARNING  
2
MAJOR  
Ethernet  
Lucent-Adjunct  
2
ATTE-AJ  
ATTE-AJ  
BRI-DAT  
MAJOR  
test station extension  
test station extension  
test data-module  
Ethernet  
Lucent-Adjunct  
3
WARNING  
Ethernet  
Lucent-Adjunct  
1. Where P is the port network number (1 for PPN); C is the carrier designation (A, B, or C); SS is  
the address of the slot in the carrier where the circuit pack is located (01, 02, ..., etc.); and pp  
is the 2-digit port number (for example, 01). The alternate name field contains the extension of  
the endpoint. This field is used to distinguish between endpoints on the same port.  
2. The alarm level for ASAI and Lucent adjuncts may be administered using the set options  
command. The alarm level can be set independently for Off-Board and On-Board alarms to  
WARNING, MINOR, or MAJOR for all ASAI and Lucent adjuncts in the system.  
3. Alarming for an ASAI and Lucent adjuncts is disabled if the adjunct asks the switch to suspend  
maintenance. When this occurs, an error and a WARNING alarm are logged against the  
endpoint. Busying out and releasing the ASAI station or ADJLK station will clear the alarm.  
The TN2208 ESAI MFB provides DEFINITY with an Ethernet interface to  
Adjunct-Switch Application Interface (ASAI) and Lucent adjuncts (for example,  
®
CONVERSANT Voice System). This circuit pack contains 8 ports of line circuit  
interface, each of which operates with two B-channels (referred to as B1 and B2  
throughout this section) and one D-channel as specified in the Lucent ISDN-BRI  
Specification. In this context, the term ‘‘ISDN-BRI port’’ is used to refer  
collectively to ports on the TN2208 MFB circuit pack which is connected to ASAI  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-291  
or Lucent adjuncts. The TN2208 ESAI MFB is handled by switch software as it is  
an ISDN BRI compatible board and all maintenance actions referring to ASAI and  
Lucent Adjunct Links in this section apply.  
ISDN-BRI endpoints come in a number of configurations. All endpoints require  
the D-channel to convey signaling information to the switch. A voice-only set  
requires only one B-channel. A voice and data-capable set requires both  
B-channels (one for voice and one for data). Therefore, each TN556 port can  
support either two voice-only sets or one voice and data-capable set. Only a  
single ASAI or Lucent adjunct may be connected to an ISDN-BRI port. Multiple  
adjuncts per line are not supported.  
Figure 3-14 illustrates the physical connection (solid line) between an ISDN-BRI  
Circuit Pack and a voice or voice/data set. Each physical connection allows for  
two B-channels, as stated above, plus one D-channel. Each ISDN-BRI circuit  
pack can support up to 12 of these PHYSICAL connections to different voice and  
voice/data sets or ASAI and Lucent adjuncts.  
VOICE  
BRI Line  
or DATA  
Circuit Pack  
SET  
D-Channel  
P
B-Channel  
O
PBX  
B-Channel  
R
T
PHYSICAL CONNECTION  
VOICE  
or DATA  
SET  
Logical Connection  
Physical Connection  
Figure 3-14. ISDN-BRI Set Interactions  
This section contains the ISDN-BRI Set, ASAI Adjunct, and Lucent Adjunct  
Maintenance documentation. Some of the results of maintenance testing of the  
ISDN-BRI Set or the ASAI and Lucent Adjunct may be affected by the health of  
the ISDN-BRI circuit pack and Port. These interactions should be kept in mind  
when investigating the cause of ISDN-BRI Set problems.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-292  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-127. BRI-SET/ASAI-ADJ Error Log Entries  
Alarm Level  
ABRI-PORT  
ATT-PORT  
LGATE-PORT  
ATTE-PT  
Alarm  
Level  
BRI-PORT  
On/  
Off  
Board  
Error  
Type  
Aux  
Data  
Associated  
Test  
Test to Clear  
Value  
1
0
0
Any  
Any  
Any  
Any  
test BRI-SET or  
ASAI-ADJ  
ATT-ADJ  
LGATE-AJ  
ATTE-AJ  
2(a)  
18  
2-102 None  
0
busyout station  
WARNING  
WARNING  
WARNING  
MAJOR/  
WARNING  
OFF  
ON  
release station  
<ext>  
2
ext  
130(b)  
257(c)  
test port PCSS  
sh  
Any  
BRI Layer 3  
MAJOR/  
WARNING  
OFF  
test station ext r  
2
2
Query (#629)  
test  
data-module ext  
r 2  
351(d)  
0
None  
WARNING  
MAJOR  
OFF  
OFF  
busyout and  
release station  
513(e)  
769(f)  
0
0
0
0
None  
None  
None  
None  
WARNING  
2561(g)  
2562-  
2566(h)  
2567(o)  
2568(p)  
2817(i)  
0
0
0
None  
None  
XID Test (#628) WARNING  
MAJOR/  
WARNING  
OFF  
test station ext r  
2
2
test  
data-module ext  
r 2  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-293  
Table 3-127. BRI-SET/ASAI-ADJ Error Log Entries — Continued  
Alarm Level  
ABRI-PORT  
ATT-PORT  
LGATE-PORT  
ATTE-PT  
Alarm  
Level  
BRI-PORT  
On/  
Off  
Board  
Error  
Type  
Aux  
Data  
Associated  
Test  
Test to Clear  
Value  
3073(j)  
0
BRI Remote  
Loop Back  
(#627)  
WARNING  
OFF  
test station ext l  
r 2  
test  
data-module ext  
l r 2  
3329(k)  
Any  
Signaling Link  
Status (626)  
WARNING  
MAJOR/  
WARNING  
OFF  
†
2
3584  
0, 1  
0
None  
None  
3585-  
3839(i)  
3840-  
4095(m)(  
n)  
0
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Major alarms on this MO may be downgraded to Warning alarms based on the value used in the  
set options command.  
Notes:  
a. Errors of this type indicate violations of the ISDN-BRI signaling protocol;  
timers associated with certain Layer 3 messages have expired before a  
required response was received. InTable 3-128, the Aux Data field  
indicates which timer has just expired. (For more information, refer to the  
Lucent ISDN-BRI Specification.)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-294  
Table 3-128. Error Type 2 Cause Values  
Aux Data  
Timer Type  
First T303 (SETUP timer)  
2
3
Second T303 (SETUP timer)  
4
T305 (DISConnect timer)  
5
First T308 (RELease timer)  
6
Second T308 (RELease timer)  
T316 (RESTart timer)  
10  
12  
16  
17  
102  
T309 (Layer 2 Failure timer)  
TM100 (Management Information Message timer 1)  
TM200 (Management Information Message timer 2)  
TASAI (ASAI Routing Timer)  
The switch sent a message to the endpoint which did not respond in the  
allotted time. This can happen occasionally due to failure of the  
point-to-point signaling link or because of a problem in the BRI endpoint or  
ASAI adjunct or Lucent adjunct. Execute the test station extension sh  
command and pay particular attention to the results of the BRI Layer 3  
Query Test (#629). If this test fails, follow the repair procedure for Test  
#629.  
b. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, replace or  
reinsert the circuit pack.  
c. This error occurs when the endpoint does not respond to the service state  
query message sent to the adjunct or the endpoint. This error causes an  
alarm to be raised. The alarm is retired when the switch receives a  
response to the service state query to the endpoint or the adjunct.  
For BRI endpoints, the Aux Data field for this error contains "0." When it  
occurs, execute the test station <extension> sh command and pay  
particular attention to the results of the BRI Layer 3 Query Test (#629). If  
this test fails, follow the repair procedure for Test #629.  
When this error occurs for an ASAI or Lucent adjunct, the Aux Data field  
indicates the state of the ASAI link or Lucent link and whether an invalid  
response or no response was received to the query from the switch, as  
shown in Table 3-129:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-295  
Table 3-129. ASAI Link State  
Aux Data ASAI Link State  
Error  
102  
104  
152  
154  
202  
204  
13-restarting  
13-restarting  
13-restarted  
13-restarted  
13-established  
13-established  
No response to RESTART message  
Invalid response to RESTART message  
No response to Layer 3 query  
Invalid response to Layer 3 query  
No response to Layer 3 query  
Invalid response to Layer 3 query  
(See ‘‘status bri-port’’ in Chapter 2, ‘‘Maintenance Commands’’ for an  
explanation of the ASAI link states.)  
For ASAI or Lucent adjuncts, the switch automatically queries the adjunct  
every two minutes (and therefore the Layer 3 Query Test is not executed  
for ASAI or Lucent adjuncts via a command issued from the G3MT  
terminal). While alarmed for this error, the switch momentarily (for five  
seconds) takes the associated port out-of-service every 15 minutes. This  
action is taken in an attempt to stimulate recovery actions to be taken by  
the adjunct.  
When this error occurs for an ASAI or Lucent adjunct, the service  
technician should:  
1. Execute the test station extension command, paying particular  
attention to any tests which fail, and perform the associated repair  
procedures for those tests.  
2. Check the health of the adjunct by following the recommended  
repair procedures of the manufacturer of the adjunct if the  
preceding step does not resolve the problem.  
3. The alarm condition persists and, if the above steps do not resolve  
the problem, follow normal escalation procedures.  
d. This error and associated WARNING alarm are logged against an ASAI or  
Lucent endpoint when the adjunct has asked the switch to suspend  
Maintenance on the ASAI or Lucent endpoint. Busying out and releasing  
the ASAI station or ADJLK station will clear this alarm.  
e. This error occurs when the endpoint sends more messages than the  
switch can handle. The switch suspends the reception of messages from  
the endpoint for a short period of time. There is no repair procedure for this  
error. If the condition persists, replace the endpoint.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-296  
f. This error occurs when the signaling link associated with a BRI endpoint  
has too much link establishment related traffic. This could occur if the  
signaling link is bouncing between assigned and established states.  
Software will suspend activity to this endpoint for 75 minutes when the  
endpoint is alarmed due to this problem (note that service suspension  
does not occur if the endpoint is an ASAI or Lucent adjunct). If this  
problem persists, replace the endpoint. If replacing the endpoint does not  
fix the problem, follow normal escalation procedures.  
g. This error occurs when the ASAI-ADJ or ATT-ADJ or LGATE-AJ or ATTE-AJ  
message is not transmitted because the PKT-CTRL (Packet Control Circuit  
Pack) transmit buffers are exhausted. Frequent or persistent occurrence  
of these events may indicate a hardware problem or traffic overload on the  
PKT-CTRL, the signaling link, or the ASAI or Lucent adjunct. Attempt to  
resolve the problem by following the repair procedures for the PKT-CTRL.  
If these attempts fail, the problem should be escalated because  
re-engineering of the traffic on the PKT-CTRL, signaling link, or adjunct  
may be necessary.  
h. This error occurs when the ASAI message is not transmitted because the  
transmit buffer for the ASAI link is full, causing the link to be flow  
controlled. Frequent or persistent occurrence of these events may indicate  
a hardware problem or traffic overload on the PKT-CTRL, the signaling link,  
or the ASAI or Lucent adjunct. Attempt to resolve the problem by following  
the repair procedures issued by the manufacturer of the adjunct. If these  
attempts fail, the problem should be escalated because re-engineering of  
the traffic on the PKT-CTRL, signaling link, or adjunct may be necessary.  
i. This error indicates a problem with Layer 2 over the D-channel between  
the switch and the endpoint. When this error occurs, an alarm is raised  
against the station or adjunct. Execute the test station extension short  
command and pay particular attention to the results of the BRI XID Test  
(#628). If this test fails, follow the repair procedure for Test #628.  
j. This error indicates a problem with the B-channel connection between the  
switch and the endpoint. When this error occurs, a warning alarm is raised  
against the endpoint. Execute the test station <extension> long  
command, and pay particular attention to the results of the BRI Remote  
Loop Back Test (#627). If this test fails, follow the repair procedure for Test  
#627.  
k. This error occurs whenever the point-to-point signaling link to the endpoint  
goes down (except when it goes down because either the PKT-CTRL or  
the PKT-BUS has failed or has been busied out by system technician).  
When this error occurs, an alarm is raised against the endpoint or adjunct.  
Execute the test station <extension> short command and pay particular  
attention to the results of the Signaling Link Status Test (#626). If this test  
fails, follow the repair procedure for Test #626. The alarm is retired when  
the signaling link is reestablished to the endpoint or adjunct.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-297  
l. Certain ASAI protocol-specific cause codes are logged by switch  
software. The cause code can be determined from the following formula:  
If the error type is greater than 3712, then the ASAI cause code is equal to  
the error type minus 3712. This code was sent to the adjunct by the  
switch.  
If the error type is less than 3712, then the ASAI cause code is equal to the  
error type minus 3584. This code was sent to the switch by the adjunct.  
A description of the various ASAI cause values is contained in the Table  
10-64. This table also contains recommended system technician actions  
associated with the cause value. Further information can also be found in  
the Lucent ASAI Specification (288-500-03). In addition, the Aux Data field  
of the Error Log entry contains additional diagnostic information.  
Table 3-130. ASAI Cause Values  
Code  
Explanation  
Recommendation  
Service or Option  
Not Available  
0
Unrecognized  
ASAIProtocol  
Operation  
Requested ASAI protocol operation is not  
implemented by the switch or adjunct. Aux Data  
field of Error Log entry contains protocol identifier  
for unrecognized operation.  
1. Consult switch and adjunct documentation to  
determine which set of operations is supported  
by the switch and the adjunct. Adjunct  
administration turning off operations not  
implemented by the switch may resolve the  
problem.  
40  
Resources not  
available  
No available internal resources to service switch or  
adjunct request. System transaction capacity for  
adjunct or switch is exceeded.  
1. Re-engineering of adjunct services my be  
required.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-298  
Table 3-130. ASAI Cause Values — Continued  
Code  
Explanation  
Recommendation  
63  
Service or Option  
Not Available  
Requested ASAI capability or resource is not  
available on the switch or adjunct. More than one  
adjunct may be contending for the same switch  
resources. Potential administration mismatch  
between the resource domains administered on  
the switch and those administered on the adjunct.  
1. Verify that no overlapping administration of  
switch resources (for example, requesting  
notifications on a single domain by multiple  
adjuncts or multiple adjuncts attempting to  
control a single call) exists across all adjuncts  
connected to the switch. If overlaps exist, then  
readminister the adjuncts to guarantee that  
each adjunct is associated with a unique set of  
switch resources.  
Service or Option  
Not Implemented  
79  
Service or Option  
Requested service or option (or combination of  
Not Implemented selected options) is not supported (implemented)  
in switch or the adjunct.  
1. Consult switch and adjunct documentation to  
determine ASAI service and options supported  
by both switch and adjunct. Readministration  
of the switch-administered capabilities (see  
Customer Optional Feature Form) or those of  
the adjunct may be necessary to correct the  
problem.  
Switch Error  
Conditions  
87  
Internal Switch  
Audit  
There is an inconsistency in switch data records.  
1. There is no action needed since the switch has  
corrected the data inconsistency.  
2. If a number of these errors continue to occur,  
then escalate to next tier.  
m. Certain ISDN-BRI cause codes are logged by switch software. The cause  
code can be determined from the following formula:  
If the error type is greater than 3968, then the ISDN-BRI cause code is  
equal to the error type minus 3968. This code was sent to the endpoint by  
the switch.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-299  
If the error type is less than 3968, then the ISDN-BRI cause code is equal  
to the error type minus 3840. This code was sent to the switch by the  
endpoint.  
A description of the various ISDN-BRI cause values is contained in Table  
10-65. This table also contains recommended system technician actions  
associated with the cause value. Further information can also be found in  
the Lucent ISDN-BRI Specification (801-802-100). In addition, the Aux  
Data field of the Error Log entry contains additional diagnostic information.  
n. Error 3847 indicates that sets on the port do not support level 3  
initialization. Consult the Set Service documentation  
o. For the Error 2567 indicates that the version of ASAI is not supported,  
check version of the software running on the ASAI or Lucent adjunct.  
p. For Error 2568 indicates that the adjunct id is invalid, check the vender id  
or software running on the Lucent adjunct.  
Table 3-131. ISDN-BRI Cause Values  
Code  
Explanation  
Recommendation  
Channel in use  
1
Requested channel is in use by another station on  
the BRI-PORT. (Not applicable for ASAI or Lucent  
adjuncts.)  
For BRI endpoints:  
1. Try to originate a call to or from this port.  
2. If the error persists, busy out and release the  
port.  
3. If the problem still persists, replace stations on  
the port.  
Switch resources  
not available  
34  
No circuit or  
channel  
available  
A resource on the switch is unavailable for a call.  
For BRI endpoints: This cause value is not logged.  
For ASAI or Lucent Adjuncts: This condition means  
that there are no available trunks for an outgoing  
call request.  
1. Verify that the adjunct is administered to  
support the trunk capabilities of the switch.  
2. Investigate trunk group status by issuing status  
trunk commands from the SAT or by requesting  
a trunk group query or queries from the adjunct.  
3. Perform trunk diagnostic procedures outlined in  
this manual.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-300  
Table 3-131. ISDN-BRI Cause Values — Continued  
Code  
Explanation  
Switch  
Equipment  
Congestion  
Recommendation  
42  
Switch takes control to limit received traffic. For BRI  
endpoints: This cause value is not logged. For ASAI  
or Lucent Adjuncts:  
1. See CallVisor protocol reference manual.  
Service or Option  
Not Available  
50  
Requested  
Facility Not  
Subscribed  
Requested facility is implemented, but not  
administered. Potential administration problem with  
endpoint or adjunct. For BRI endpoints:  
1. Verify the switch administration of endpoint  
using either the display station or display  
data-module commands.  
2. If Step 1 does not resolve the problem, refer to  
the endpoint’s service manual and verify  
administration on the endpoint.  
For ASAI adjuncts:  
1. Display the Customer Optional Features Form  
(administration screen) on the switch to  
determine which ASAI capabilities are turned  
on in the switch.  
2. Verify that the adjunct is administered to  
support the identical capabilities as the switch.  
If there is a mismatch in the administered  
capabilities, then readminister the switch and/or  
the adjunct to establish a consistent set of  
desired capabilities on both the switch and the  
adjunct.  
For Lucent adjuncts:  
1. Display the Customer Optional Features Form  
(administration screen) on the switch to  
determine if the adjunct is set enabled on in the  
switch.  
2. If error type 2567 or 2568, verify the adjunct  
version, and readminister if needed.  
58  
BearerCapability Requested bearer capability is implemented, but  
Not Presently  
Available  
not administered. No B-channel administered. See  
recommendation 50 above.  
Service or Option  
Not Implemented  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-301  
Table 3-131. ISDN-BRI Cause Values — Continued  
Code  
Explanation  
Recommendation  
Requested service not implemented in switch or  
65  
Bearer Service  
Not Implemented endpoint.  
69  
81  
Requested  
Facility Not  
Implemented  
Requested service not supported in switch or  
endpoint.  
1. Consult switch and endpoint documentation to  
determine service support.  
Adjunct switch  
error conditions  
Invalid CRV  
An invalid CRV was sent by the adjunct.  
1. This may indicate a CRV inconsistency between  
the switch and the adjunct. See the CallVisor  
protocol reference manual.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
When inspecting errors in the system and deciding which ones to address,  
always investigate errors associated with the circuit pack and port first. Clearing  
these error codes first may also clear errors generated against the endpoint.  
When all circuit pack and port errors have been cleared, and errors still exist  
against the endpoint, always investigate errors in the order they are presented in  
the table below. By clearing error codes associated with the Signaling Link Status  
Tes t, for example, you may also clear errors generated from other tests in the  
testing sequence.  
Table 3-132. System Technician-Demanded Tests: BRI-SET  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Signaling Link Status Test (#626)  
BRI XID Test (#628)  
D/ND  
ND  
X
X
X
X
ND  
BRI Layer 3 Query (#629)  
BRI Remote Loop Back (#627)  
BRI Set Audits (#630)  
X (a)  
X (a)  
X (a)  
X (a)  
ND  
ND  
X (a)  
ND  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-302  
Table 3-132. System Technician-Demanded Tests: BRI-SET — Continued  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
BRI Vendor ID Test (#631)  
D/ND  
ND  
X (a)  
X (a)  
BRI Model/Vintage ID Test (#632)  
ND  
1. D = Destructive, ND = Non-destructive  
Note:  
a. Execute the test port long PCSSpp command and review the results of  
the BRI Port Local LAN Loop Around Test to verify the repair.  
Signaling Link Status Test (#626)  
This test determines the current status of the signaling link. This test passes if the  
link is "bound" to an endpoint and fails if the link is "not bound."  
The definition of the term "bound" for a link depends upon the type of endpoint  
and may depend on the successful completion of procedures at both Layers 2  
and 3 of the protocol. The definition of "bound" for each type of endpoint is as  
follows:  
■
BRI endpoints administered for MIM (management information  
messages) initialization (multipoint):  
NOTE:  
An MIM is a level 3 message that conveys management and  
maintenance information between a communications system and a  
BRI terminal.  
For endpoints of this type, the signaling link is "bound" when the link is  
connected at Layer 2 and the link has been associated with an endpoint,  
[that is, the endpoint has completed SPID initialization (L3 established)].  
■
ASAI adjuncts and BRI endpoints not administered for MIM  
initialization (point-to-point):  
For endpoints of this type, the signaling link is "bound" when the link is  
connected at Layer 2 (L2 established).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-303  
For all endpoint types, a signaling link becomes "unbound" when it is  
disconnected at Layer 2. For BRI endpoints supporting MIM initialization, a  
signaling link may also become "unbound" if a subsequent attempt to perform  
SPID initialization on a "bound" link fails, (that is, wrong SPID is entered into the  
endpoint by the user).  
Table 3-133. TEST #626 Signaling Link Status Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The Packet Bus in the port network is out-of-service.  
1. Follow the repair procedures for the Packet Bus.  
1139  
ABORT  
2. After completing Step 1, execute the test port long PCSSpp  
command, and review the results of the BRI Port Local LAN Loop  
Around Test to verify the repair.  
1141  
1144  
ABORT  
ABORT  
The PKT-CTRL is out-of-service.  
1. Refer to PKT-CTRL (Packet Control Circuit Pack) Maintenance  
documentation.  
The PPN Packet Bus is out-of-service.  
1. Follow the repair procedures for the Packet Bus in the PPN.  
2. After completing Step 1, execute the test port long PCSSpp  
command, and review the results of the BRI Port Local LAN Loop  
Around Test to verify the repair.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-304  
Table 3-133. TEST #626 Signaling Link Status Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1187  
ABORT  
The circuit pack, port or station may have been busied out by a  
technician.  
1. Look in the Error Log for Error Type 18 (busied out ) for BRI-BD,  
BRI-PORT, or BRI-SET.  
2. If this error type is present for BRI-SET only, then release the station  
via the release station command.  
a. If this error type is present for BRI-PORT and BRI-SET, then release  
the port via the release port PCSSpp command and run the test  
again.  
b. If the error is present for BRI-BD, BRI-PORT, and BRI-SET, then  
release the circuit pack via the release port PCSSpp command  
and run the test again. If the error is present for BRI-SET only, then  
release the circuit pack via the release port PPCSS command  
and run the test again. If the error is present for both BRI-BD and  
BRI-PORT, then release the circuit pack via the release board  
PPCSS command and run the test again.  
NOTE:  
When you release the circuit pack, you release all ports  
associated with it. If certain ports still need to be busied  
out, use the release port PCSSpp command to busy  
them out.  
3. Make sure the terminal is connected.  
4. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-305  
Table 3-133. TEST #626 Signaling Link Status Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1113  
FAIL  
The signaling link is not "bound" to the adjunct or endpoint. For BRI  
endpoints supporting MIM initialization, this error indicates that the  
endpoint has not been bound to a signaling link (that is, SPID initialization  
has not been completed). Since the signaling link associated with the  
endpoint is not identified until SPID initialization completes, this error does  
not imply that the signaling link is connected or disconnected at Layer 2  
nor does it provide the status of TEI assignment for the endpoint. For ASAI  
adjuncts and BRI endpoints not supporting MIM initialization, this error  
indicates that the link is disconnected at Layer 2. Since the signaling link  
associated with the endpoint has been identified via administration, the  
link is only "unbound" from the endpoint when it is disconnected.  
1. Execute the status bri-port PCSSpp command and refer to the  
associated procedures for this command contained in the BRI-PORT  
(ISDN-BRI Port) Maintenance documentation.  
PASS  
The signaling link is connected at Layer 2 and "bound"to the BRI endpoint  
or ASAI adjunct.  
BRI Remote Loop Back Test (#627)  
This test checks the integrity of a circuit switched B-channel connection between  
the switch and the endpoint.  
In this test, the endpoint is put in the "maintenance busy" state to prevent the  
switch from issuing calls to the endpoint during the test. An application message  
containing a loop back activate request for the appropriate B-channel is sent to  
the endpoint. The endpoint responds with a loop back activated response.  
Maintenance then sends data to the endpoint over the B-channel under test.  
Since the B-channel is looped back at the endpoint, maintenance should receive  
the data that it sent. If no data is detected, the test fails. An application message  
containing a loop back deactivate request is then sent to the endpoint to  
terminate the remote loop back test. The endpoint responds with an MIM  
message containing a loop back deactivate response. Maintenance then  
releases the endpoint so that it is available to terminate calls.  
This test is not executed for ASAI adjuncts because adjuncts do not support  
MIMs upon which this test is based.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-306  
Table 3-134. TEST #627 BRI Remote Loop Back  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
ABORT  
Could not seize the endpoint or B-channels for test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1005  
The endpoint’s MIMs Supported field is administered to "no."  
1. Use the change station extension command to change parameter  
only if the endpoint documentation reflects support for ISDN-BRI  
Management and Maintenance Procedures.  
1113  
ABORT  
The signaling link between the switch and the endpoint is down.  
1. Use the test port PCSSpp long command to clear any errors which  
prevent establishment of the signaling link.  
2. Examine the results of the Signaling Link Status Test (#626) which is  
run as part of this command. If this test aborts or fails, follow the repair  
procedure for Test #626.  
3. If the XID Test continues to abort, escalate the problem.  
The Packet Bus in the port network is out-of-service.  
1. Follow the repair procedures for the Packet Bus.  
1139  
ABORT  
2. After completing Step 1, execute the test port long PCSSpp  
command, and review the results of the BRI Port Local LAN Loop  
Around Test to verify the repair.  
1141  
1144  
ABORT  
ABORT  
The PKT-CTRL is out-of-service.  
1. Refer to PKT-CTRL (Packet Control Circuit Pack) Maintenance  
documentation.  
The PPN Packet Bus is out-of-service.  
1. Follow the repair procedures for the Packet Bus in the PPN.  
2. After completing Step 1, execute the test port long PCSSpp  
command, and review the results of the BRI Port Local LAN Loop  
Around Test to verify the repair.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-307  
Table 3-134. TEST #627 BRI Remote Loop Back — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1187  
ABORT  
The circuit pack, port or station may have been busied out by a technician.  
1. Look in the Error Log for Error Type 18 (busied out ) for BRI-BD,  
BRI-PORT, or BRI-SET.  
2. If this error type is present for BRI-SET only, then release the station via  
the release station command.  
a. If this error type is present for BRI-PORT and BRI-SET, then release  
the port via release port PCSSpp command and run the test  
again.  
b. If the error is present for BRI-BD, BRI-PORT, and BRI-SET, then  
release the circuit pack via the release port PCSSpp command  
and run the test again. If the error is present for both BRI-BD and  
BRI-PORT, then release the circuit pack via the release board  
PPCSS command and run the test again. If the error is present for  
BRI-SET only, then release the circuit pack via the release port  
PPCSS command and run the test again.  
NOTE:  
When you release the circuit pack, you release all ports  
associated with it. If certain ports still need to be busied  
out, use the release port PCSSpp command to busy  
them out.  
3. Make sure the terminal is connected.  
4. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
2012  
2068  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The endpoint has rejected the switch sent application message. This  
indicates that the endpoint does not support the ISDN-BRI Management  
and Maintenance Procedure for Loop Back Testing.  
1. Use the change station extension command and change the MIMs  
Supportedfield to n.  
2069  
2100  
ABORT  
ABORT  
The endpoint has returned an error response to the application message  
sent by the switch.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-308  
Table 3-134. TEST #627 BRI Remote Loop Back — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
FAIL  
No loop back activation or deactivation response is received from the  
endpoint.  
1. Consult the endpoint documentation to determine if ISDN-BRI  
Management and Maintenance Procedures are supported. If not  
supported, use change station extension command to change the  
MIMs Supported?field to n. Use the busyout station extension  
and release station extension commands to busyout and release the  
endpoint to resolve any endpoint alarms resulting from failure of this  
test.  
2. If the endpoint supports these procedures and the test continues to  
fail, assume the endpoint is defective and replace it.  
2071  
2072  
FAIL  
FAIL  
No data is detected on Channel B1 during loop back.  
No data is detected on Channel B2 during loop back.  
1. Replace the endpoint and repeat test.  
2. If test continues to fail, check the wiring between the endpoint and the  
switch and repeat the test.  
PASS  
The endpoint has responded to the switch activate and deactivate loop  
back application messages. Data has been detected on the looped back  
channels.  
1000  
ABORT  
Could not seize the endpoint or B-channels for test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
BRI XID Test (#628)  
This test checks the D-channel connection between the SPE and the endpoint or  
adjunct.  
In this test, a D-channel XID frame is sent to the endpoint or adjunct over the  
point-to-point signaling link. The test passes if the endpoint or adjunct responds  
with a Layer 2 XID-RESPONSE frame.  
This test must be administered to not run in the station administration form for  
ports on a TN2208.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-309  
Table 3-135. TEST #628 BRI XID  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
The BRI-SET, ASAI-ADJ, ATT-ADJ, LGATE-AJ, ATTE-AJ is busy. The test  
cannot be executed at this time:  
1. Pause momentarily (30 seconds) and re-execute at this time.  
NOTE:  
A BRI-PORT can also be busy. When using this for  
BRI-PORT/ABRI-PORT tests, the words "BRI-SET, ASAI-ADJ,  
ATT-ADJ, " can be changed to "BRI-PORT, ABRI-PORT, ATT-ADJ."  
1005  
1113  
ABORT  
ABORT  
The endpoint is not administered to support XID Testing.  
1. If the endpoint documentation reflects support XID testing, use the  
change station extension command to change the XID Testing?  
field on the form to y.  
The signaling link between the switch and the endpoint is down.  
1. Use the test port PCSSpp l command to clear any errors which  
prevent establishment of the signaling link.  
2. Examine the results of the Signaling Link Status Test (#626) which is  
run as part of this command. If this test aborts or fails, follow the repair  
procedure for Test #626.  
3. If the XID test continues to abort, escalate the problem.  
The Packet Bus in the port network is out-of-service.  
1. Follow the repair procedures for the Packet Bus.  
1139  
ABORT  
2. After completing Step 1, execute the test port long PCSSpp  
command, and review the results of the BRI Port Local LAN Loop  
Around Test to verify the repair.  
1141  
1144  
ABORT  
ABORT  
The PKT-CTRL is out-of-service.  
1. Refer to PKT-CTRL (Packet Control Circuit Pack) Maintenance  
documentation.  
The PPN Packet Bus is out-of-service.  
1. Follow the repair procedures for the Packet Bus in the PPN.  
2. After completing Step 1, execute the test port long PCSSpp  
command, and review the results of the BRI Port Local LAN Loop  
Around Test to verify the repair.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-310  
Table 3-135. TEST #628 BRI XID — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1187  
ABORT  
The circuit pack, port or station may have been busied out by a technician.  
1. Look in the Error Log for Error Type 18 (busied out ) for BRI-BD,  
BRI-PORT, or BRI-SET.  
2. If this error type is present for BRI-SET only, then release the station via  
the release station command.  
a. If this error type is present for BRI-PORT and BRI-SET, then release  
the port via release port PCSSpp command and run the test  
again.  
b. If the error is present for BRI-BD, BRI-PORT, and BRI-SET, then  
release the circuit pack via the release port PCSSpp command  
and run the test again. If the error is present for BRI-SET only, then  
release the circuit pack via the release port PCSSpp command  
and run the test again. If the error is present for both BRI-BD and  
BRI-PORT, then release the circuit pack via the release board  
PPCSS command and run the test again.  
NOTE:  
When you release the circuit pack, you release all ports associated  
with it. If certain ports still need to be busied out, use the release  
port PCSSpp command to busy them out.  
3. Make sure the terminal is connected.  
4. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The XID-RESPONSE message was not received from the endpoint.  
2000  
FAIL  
1. Consult the endpoint documentation to determine if the Layer 2 XID  
and XID-RESPONSE messages are supported. If the documentation  
reflects no support for these messages, change XID Testing?  
field to n using the change station extension command.  
2. If the endpoint supports these Layer 2 messages and the test  
continues to fail, assume the endpoint is defective and replace it.  
PASS  
The switch can successfully pass messages over the D-channel to the BRI  
endpoint.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-311  
BRI Layer 3 Query Test (#629)  
This test is used to check the application layer communications between the  
switch and the endpoint or adjunct.  
For BRI endpoints, an application message containing the appropriate endpoint  
service state is sent by the switch to the endpoint. The endpoint responds with an  
acknowledgment to the application message.  
For ASAI and Lucent adjuncts, this test is not executed from the administration  
terminal. Rather, a query message is automatically sent by the switch every two  
minutes. Failure of the switch to receive a response to a query from the adjunct is  
logged in the Hardware Error Log.  
Table 3-136. TEST #629 BRI Layer 3 Query  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1005  
ABORT  
The endpoint’s MIMs Supported?field is administered to  
"no."  
1. Use the change station extension command to change  
the parameter only if the endpoint documentation reflects  
support for ISDN-BRI Management and Maintenance  
Procedures.  
1113  
ABORT  
The signaling link between the switch and the endpoint or  
adjunct is down.  
1. Use the test port PCSSpp long command to clear any  
errors which prevent establishment of the signaling link.  
2. Examine the results of Test #626, which is executed with  
the command. If this test aborts or fails, follow the repair  
procedure for the Signaling Link Status Test.  
1139  
1141  
ABORT  
ABORT  
The Packet Bus in the port network is out-of-service.  
1. Follow the repair procedures for the Packet Bus.  
2. After completing Step 1, execute the test port long  
PCSSpp command, and review the results of the BRI Port  
Local LAN Loop Around Test to verify the repair.  
The PKT-CTRL is out-of-service.  
1. Consult the repair procedure for PKT-CTRL (Packet  
Control Circuit Pack) Maintenance documentation.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-312  
Table 3-136. TEST #629 BRI Layer 3 Query — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The PPN Packet Bus is out-of-service.  
1144  
ABORT  
ABORT  
1. Follow the repair procedures for the Packet Bus in the  
PPN.  
2. After completing Step 1, execute the test port long  
PCSSpp command, and review the results of the BRI Port  
Local LAN Loop Around Test to verify the repair.  
1187  
The circuit pack, port or station may have been busied out by  
a technician.  
1. Look in the Error Log for Error Type 18 (busied out ) for  
BRI-BD, BRI-PORT, or BRI-SET.  
2. If this error type is present for BRI-SET only, then release  
the station via the release station command.  
a. If this error type is present for BRI-PORT and BRI-SET,  
then release the port via the release port PCSSpp  
command and run the test again.  
b. If the error is present for BRI-BD, BRI-PORT, and  
BRI-SET, then release the circuit pack via the release  
port PCSSpp command and run the test again. If the  
error is present for BRI-SET only, then release the  
circuit pack via the release port PPCSS command  
and run the test again. If the error is present for both  
BRI-BD and BRI-PORT, then release the circuit pack via  
the release board PPCSS command and run the test  
again.  
NOTE:  
When you release the circuit pack, you  
release all ports associated with it. If certain  
ports still need to be busied out, use the  
release port PCSSpp command to busy  
them out.  
3. Make sure the terminal is connected.  
4. Retry the command at 1-minute intervals a maximum of 5  
times.  
2012  
2100  
ABORT  
ABORT  
Internal system error  
Could not allocate the necessary system resources to run this  
test.  
1. Retry the command at 1-minute intervals a maximum of 5  
times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-313  
Table 3-136. TEST #629 BRI Layer 3 Query — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2068  
ABORT  
The endpoint has rejected the switch sent application  
message. This indicates that the endpoint does not support  
the ISDN-BRI Management and Maintenance Procedure for  
Endpoint Service Messages.  
1. Use the change station extension command and change  
the MIMs Supported?field to n.  
2069  
2000  
ABORT  
FAIL  
The endpoint has returned an error response to the switch sent  
application message.  
1. Retry the command at 1-minute intervals a maximum of 5  
times.  
No response is received from the endpoint or the adjunct. For  
BRI endpoints:  
1. Consult the endpoint documentation to determine if  
ISDN-BRI Management and Maintenance Procedures are  
supported. If not supported, use the change station  
extension command to change the MIMs Supported?  
field to n. Use the busyout station extension and release  
station extension commands to busyout and release the  
endpoint to resolve any endpoint alarms resulting from  
failure of this test.  
2. If the endpoint supports these procedures and the test  
continues to fail, assume the endpoint is defective and  
replace it.  
PASS  
The endpoint has successfully responded to the switch’s  
application message.  
BRI Set Audits Test (#630)  
This is a series of two tests which are classified as audits. The switch sends  
messages to the BRI endpoint to perform the following tests:  
■
■
■
Ringer Audit - This audit ensures that both the switch and the endpoint  
agree as to the current state of the endpoint’s ringer.  
Lamps Audit - This audit ensures that both the switch and the endpoint  
agree as to the current state of the endpoint’s lamps.  
Call Activity Audit - This audit ensures that the state of calls is consistent  
between the switch and the endpoint.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-314  
This test is not executed for ASAI or Lucent adjunct because adjuncts do not  
employ ringers or lamps, or establish calls on the B-channels associated with the  
BRI interface.  
Table 3-137. TEST #630 BRI Set Audits  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1113  
ABORT  
The signaling link between the switch and the endpoint is down.  
1. Use the test port PCSSpp long command to clear any errors which  
prevent establishment of the signaling link.  
2. Examine the results of the Signaling Link Status Test (#626) which is  
run as part of this command. If this test aborts or fails, follow the repair  
procedure for Test #626.  
1139  
ABORT  
The Packet Bus in the port network is out-of-service.  
1. Follow the repair procedures for the Packet Bus.  
2. After completing Step 1, execute the test port long PCSSpp  
command, and review the results of the BRI Port Local LAN Loop  
Around Test to verify the repair.  
1141  
1144  
ABORT  
ABORT  
The PKT-CTRL is out-of-service.  
1. Refer to PKT-CTRL (Packet Control Circuit Pack) Maintenance  
documentation.  
The PPN Packet Bus is out-of-service.  
1. Follow the repair procedures for the Packet Bus in the PPN.  
2. After completing Step 1, execute the test port long PCSSpp  
command, and review the results of the BRI Port Local LAN Loop  
Around Test to verify the repair.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-315  
Table 3-137. TEST #630 BRI Set Audits — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1187  
ABORT  
The circuit pack, port or station may have been busied out by a technician.  
1. Look in the Error Log for Error Type 18 (busied out ) for BRI-BD,  
BRI-PORT, or BRI-SET.  
2. If this error type is present for BRI-SET only, then release the station via  
the release station command.  
a. If this error type is present for BRI-PORT and BRI-SET, then release  
the port via the release port PCSSpp command and run the test  
again.  
b. If the error is present for BRI-BD, BRI-PORT, and BRI-SET, then  
release the circuit pack via the release port PCSSpp command  
and run the test again. If the error is present for both BRI-BD and  
BRI-PORT, then release the circuit pack via the release board  
PPCSS command and run the test again.  
NOTE:  
When you release the circuit pack, you release all ports associated  
with it. If certain ports still need to be busied out, use the release  
port PCSSpp command to busy them out.  
3. Make sure the terminal is connected.  
4. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
SPID Facility Test  
This test is used to verify the wiring and operation of the signaling link between  
the switch and a endpoint or adjunct on a BRI interface. This test is not  
executed from the administration terminal, but rather is executed by using a  
BRI test set equipped with a display. The test set may replace the BRI set,  
ASAI or Lucent adjunct under test by plugging it into the same jack or by  
bridging it onto the wiring at some point between the switch and the endpoint (or  
adjunct), thereby creating a pseudo-BRI multipoint configuration.  
When plugged into the port in this manner, the test set establishes a signaling  
link connection with the switch and attempts to complete SPID initialization by  
using the Service SPID administered for the system (see the System  
Maintenance DAodwmnloinadisftrroamtiWonwwF.Soormma)n.uIaflst.hceomt.eAslltMsaentudalissSpelaarychsAthndeDcoowrnrleoacdt.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-316  
administered port address for the endpoint or adjunct under test, the test passes  
(see Service SPID Display which follows). If after one minute nothing is displayed  
on the test set, the test fails.  
Table 3-138. SPID Facility Test  
Test  
Result  
Description/ Recommendation  
FAIL  
FAIL  
No response is received from the endpoint.  
1. Check the physical wiring between the switch and the endpoint or adjunct.  
Display does not match administered port address for the endpoint or adjunct.  
1. Change station administration for endpoint or adjunct to match displayed port  
address.  
PASS  
Display matches administered port address for the endpoint or adjunct.  
For BRI endpoints:  
1. Verify that the SPID values administered in the switch and the endpoint are  
consistent.  
2. If the SPID values are correct, replace the endpoint.  
For ASAI adjuncts:  
1. Verify that the TEI values administered in the switch and the adjunct are  
consistent.  
2. If the TEI values are correct, consult the recommended repair procedures of the  
manufacturer for the adjunct.  
The abbreviations used in (Service SPID Display) have the following meanings:  
P
port network (1,2, ...)  
C
Carrier (A,B,C, ...)  
SS  
pp  
ext  
SPID  
Slot (01, 02, ...)  
port (01-12)  
extension one and two (one through 99999)  
service order profile identifier  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
BRI-SET, ASAI-ADJ, BRI-DAT  
3-317  
Restricted Service  
Starting Display Column  
1
8
14  
25  
31  
PCSSpp  
-
*
-
ext1  
-
SPID111111  
-
ext2  
-
-
*
SPID222222  
Bound to First Endpoint Translation  
Starting Display Column  
1
8
14  
25  
ext2  
31  
PCSSpp  
ext1  
*
SPID111111  
-
SPID222222  
Bound to Second Endpoint Translation  
Starting Display Column  
1
8
14  
25  
31  
PCSSpp  
ext1  
-
SPID111111  
*
ext2  
SPID222222  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CABINET (Cabinet Sensors)  
3-318  
CABINET (Cabinet Sensors)  
MO Name (in  
Alarm Log)  
Initial Command to  
1
Alarm Level  
Run  
Full Name of MO  
CABINET  
MAJOR  
test environment P  
Cabinet Sensors  
1. Where P is an appropriate port network number determined in the Port field from the  
Alarm or Error Log.  
The Compact Modular Cabinet (CMC) AC Power Supply (650A) supports one  
alarm lead that indicates the state of both the power and fan. With multiple  
cabinets, alarm leads from each cabinet are tied into a single lead. The CMC  
uses variable speed fans to reduce noise. The CMC power unit contains Thermal  
Speed Control and an alarm circuit. A variable speed fan has a 3-pin connector  
for the variable input power for speed control and its alarm circuitry.  
Table 3-139 shows the LED and alarm conditions.  
Table 3-139. LED and Alarm Conditions  
Condition  
LED Status Alarm State Fan Alarm  
Normal  
Red off;  
Open  
Normal  
Yellow on  
No input power  
Red off;  
Yellow off  
Closed  
Closed  
Closed  
No input power  
DC output not present  
(except Neon)  
Red on;  
Yellow off  
DC output not present  
(except Neon)  
Fan alarm  
Red on;  
Fan alarm  
Yellow on  
Fan and Filter Removal/Replacement  
1. Remove the left door.  
2. Remove the fan/filter access panel. See Figure 3-15.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CABINET (Cabinet Sensors)  
3-319  
Figure 3-15. Fan/Filter Removal  
Fan Assembly Removal/Replacement  
1. Pull (unplug) the fan assembly from the chassis using the thumb/finger  
notch provided. The power for the fan automatically disconnects when the  
assembly is unplugged.  
2. Plug in the new fan assembly. The power for the fan automatically  
connects when the fan assembly in plugged in.  
3. Replace the fan/filter access panel and the left door.  
Fan Filter Removal/Replacement  
1. Remove the fan access panel from the left side of the cabinet.  
2. Pull the fan filter from the chassis.  
3. Clean (vacuum or wash with water) or replace the filter as needed and  
slide the filter back into the chassis.  
4. Replace the fan access panel.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CABINET (Cabinet Sensors)  
3-320  
Hardware Error Log Entries and Test to Clear  
Values  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
MAJOR  
Any  
ON  
test environment P sh r 1  
test environment P sh r 3  
1
Any  
Cabinet Temperature  
Query Test (#122)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following table. By clearing  
error codes associated with the Cabinet Temperature Query Test, for example,  
you may also clear errors generated from other tests in the testing sequence.  
Test descriptions and recommended maintenance procedures follow for all  
errors that can occur during system technician-demanded testing.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Cabinet Temperature Query Test (#122)  
Emergency Transfer Query Test (#124) (a)  
External Alarm Lead Query Test (#120) (b)  
D/ND  
ND  
X
X
X
X
X
X
ND  
ND  
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Refer to ‘‘EMG-XFER’’ for a description of this test.  
b. Refer to ‘‘EXT-DEV ADMIN? N (External Device Alarm)’’ for a description of  
this test.  
Cabinet Temperature Query Test (#122)  
This test queries the Processor circuit pack for the status of the cabinet sensors  
in the Compact Modular Cabinet. The 650A Power Supply is equipped with  
thermal protection that shuts the power supply down if the internal temperature  
exceeds the maximum rated safe operating temperture. Only one alarm lead is  
supported by this cabinet type to indicate both a power or a fan problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CABINET (Cabinet Sensors)  
3-321  
This means that a failure of this test can also mean a power problem, not  
necessarily just a temperature (fan) problem. Also, alarm leads from multiple  
cabinets are tied into one single lead.  
Table 3-140. TEST #122 Cabinet Temperature Query Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
2029  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1
FAIL  
There is a fan and/or power problem in one or more of the cabinets. The  
LEDs on the power supply may indicate the problem source. Otherwise  
follow the procedures below for each cabinet:  
1. If none of the fans are running, then:  
a. Verify 8-14 volt DC power is available to the fan units by checking  
the wiring connector.  
— If there is 8-14 volt DC power at the connector, there should be  
power to the fans. If the fans still do not run, replace the fan  
assembly.  
— If there is no 8-14 volt DC power at the connector, then the  
power unit fan output is defective or thermally shut down. Let  
the power unit cool and recycle AC input power. If not fan  
output, then replace the power unit. If the fans still do not run,  
escalate the problem.  
2. If only 1 of the fans is not running, replace the fan.  
3. If all the fans can be started, wait five minutes and rerun the test. If the  
test fails again, proceed to Step 4 or 5 as applicable.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CABINET (Cabinet Sensors)  
3-322  
Table 3-140. TEST #122 Cabinet Temperature Query Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
FAIL  
(cont’d.)  
4. If the fans are not at high speed, measure the cabinet temperature at  
the air intake and the air exhaust at the top of the cabinet.  
0
a. If the 5 - 60 C criteria is met, there is a problem with the fans that is  
preventing the fans from operating at high speed. Replace the  
fans. If the fans run at high speed, wait 5 minutes to give the  
cabinet time to cool down and, rerun the test. If the problem  
persists, go to step 5.  
0
b. If the 5 - 60 C criteria is not met, the Processor circuit pack is  
incorrectly reporting this condition. Look for and resolve all errors  
on these maintenance objects first, then rerun the test.  
5. If the fans are running at the high speed, check the items on list that  
follows. Any one of the items could be restricting or redirecting the  
flow of air within the cabinet.  
a. Check filter. If the filter is dirty or clogged it should be cleaned or  
replaced. The filter can either be washed with soap and water or  
vacuumed.  
b. Make sure there is nothing other than circuit packs in the carrier  
slots that could be restricting the air flow.  
c. Make sure there are no missing (blank) circuit pack or carrier  
faceplates. Install and/or replace them as necessary.  
d. Make sure the cabinet doors are properly closed. The doors must  
be closed for the fans to be able to properly cool the cabinet. Wait  
five minutes to give the fans a chance to cool the cabinet. Rerun  
the test. If the tests still fails, proceed to Step 6.  
1
FAIL  
(cont’d.)  
6. At this point, there should be nothing impeding the air flow, and the  
fans should be running at high speed. Check the temperatures for the  
0
5 - 60 C criteria.  
0
a. If the 5 - 60 C criteria exists, a temperature problem exists, and  
the fans (at high speed) should cool down the cabinet. Wait five  
minutes and rerun the test. If the test still fails, the ambient room  
temperature is probably too high, and the room should be cooled.  
0
b. If the 5 - 60 C criteria does not exist, the fans are defective.  
Replace the fan assembly and rerun the test. Failures can occur on  
the Processor circuit pack that is not detected by its maintenance  
object, but that cause many, if not all, environment tests to fail. If  
many environment tests are failing, check errors against the  
Processor circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CABINET (Cabinet Sensors)  
3-323  
Table 3-140. TEST #122 Cabinet Temperature Query Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
FAIL  
There is a problem with the environment of the power system:  
(cont’d.)  
7. The power unit could be defective. Refer to the ‘‘Removing Power’’  
and ‘‘Restoring Power’’ sections in Chapter 1, ‘‘Maintenance for csi  
systems’’.  
a. If the yellow LED is off, replace the power unit.  
b. If the Active Tone-Clock circuit pack loses power, the system  
performs a Cold-2 restart to finish (the login prompt appears at the  
administration terminal).  
c. Rerun the test.  
PASS  
There is neither a power nor fan a problem in any of the cabinets. If a  
problem is reported, troubleshoot by using the procedures for the FAIL  
cases described previously.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CAP-MEM (Memory Card Capacity)  
3-324  
CAP-MEM (Memory Card Capacity)  
MO Name (in  
Alarm Log)  
Alarm Level  
Initial Command to Run  
Full Name of MO  
Memory Card Capacity  
CAP-MEM  
MINOR/  
test card-mem long  
1
WARNING  
1. Downgrading the MINOR alarm (set option) generates the WARNING alarm.  
Memory Card Capacity tracks the percentage of translation storage space the  
memory card uses. When the memory card fills 98% of its translation space, the  
switch generates an alarm to inform users that they may require a larger system  
flash card.  
Error Log Entries and Test to Clear Values  
Table 3-141. Memory Card Capacity Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Alarm Level  
Test to Clear Value  
1 (a)  
112  
Memory Card Capacity Test  
(#1014)  
MINOR/  
WARNING (b)  
OFF  
test card-mem long  
Notes:  
a. The memory card translation storage space is at least 98% full.  
b. This alarm has been downgraded (set option).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CAP-MEM (Memory Card Capacity)  
3-325  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Investigate errors in the order they appear in the table below.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
12-Volt Power Supply Test (#701) (a)  
D/ND  
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
Memory Card Insertion Test (#695) (b)  
Memory Card Format and Read Test (#696) (b)  
Memory Card Match Test (#697) (b)  
Memory Card Write-Protected Test (#698) (b)  
Memory Card Directory Recovery Test (#699) (b)  
Memory Card Translation Data Integrity Test (#694) (b)  
Memory Card Erase/Write/Read Test (#693) (b)  
Memory Card Capacity Test (#1014)  
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Refer to 12V-PWR (12-Volt Power Supply) Maintenance documentation for  
a description of this test.  
b. Refer to CARD-MEM (Memory Card) Maintenance documentation for a  
description of this test.  
Memory Card Capacity Test (#1014)  
This nondestructive test verifies that the memory card is using less than 98% of  
its translation storage space.  
This test runs  
■
during periodic and schedule maintenance  
■
on demand (test card-mem long, save translation).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CAP-MEM (Memory Card Capacity)  
3-326  
Table 3-142. TEST #1014 Memory Card Capacity Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
112  
ABORT  
Memory Card Translation storage at least 98% full.  
1. Inform the user of possible need to upgrade to larger flash card.  
2. Replace the memory card with a larger one, or downgrade the alarm  
to WARNING (set option).  
3. Rerun the test.  
2012  
2106  
2114  
ABORT  
Internal System Error  
1. Retry the command at 1-minute intervals, up to 5 times.  
2013  
2100  
ABORT  
ABORT  
Could not locate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals, up to 5 times  
Memory card not present.  
2110  
1. Insert formatted memory card into TN794 or TN777B circuit pack  
slot.  
2. Retry the command at 1-minute intervals, up to 5 times.  
The Memory Card Translation storage is less than 98% full.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-327  
CARD-MEM (Memory Card)  
MO Name (in  
Alarm Log)  
CARD-MEM  
CARD-MEM  
CARD-MEM  
Alarm Level  
Initial Command to Run Full Name of MO  
1
MAJOR  
Memory Card  
MINOR  
test card-mem long  
test card-mem sh  
Memory Card  
Memory Card  
WARNING  
1. The "MAJOR" alarm occurs only at power-up time or on a Reset System 3, 4, or 5  
when the switch cannot load all translations from the memory card.  
A memory card contains a set of flash EPROM memory devices. The data can be  
stored in a memory card and can remain nonvolatile, even when the power is off.  
The memory card is installed into the Processor circuit pack to save the  
translations, announcements, and core dumps. During the system reboot or a  
system power down condition, the in-core system maintenance hardware error  
logs are temporarily saved in the memory card before the system goes down.  
When the system is restarted, the error logs file is read back from the memory  
card.  
The Hard Patch feature also uses the memory card as temporary storage when  
LMM applies an update file to the in-core system software. The system software  
is stored in the "flash" section of main memory. The memory card used for saving  
translations doesn’t contain a copy of the system software.  
The recommended size of a memory card for each configuration is described in  
the following table.  
Memory Card Size  
1 Megabyte  
Usage  
File Names  
Without Announcements translation  
4 Megabyte  
With Announcements  
With Announcements  
translation announcements  
translation announcements  
translation announcements  
10 Megabyte  
10 Megabyte  
DEFINITY Wireless  
Business System, or  
Test #1014 error on 4  
Megabyte card  
20 Megabyte  
20 Megabyte  
Maintenance  
translation announcements core_dump  
system_software  
System Upgrade  
Customers can have either 1 MB, 4 MB, or 10 MB memory cards for the normal  
operations. 10 MB memory cards are also used for maintenance and software  
upgrades. The software upgrade memory card cannot be used for saving  
translations.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-328  
Common causes for failing the Memory Card Match Test (#697) are:  
■
The customer has had a recent upgrade and is using an old card.  
The card is not formatted for announcements.  
■
Always use 4 MB memory Cards, 10 MB memory cards should only be used  
when a 4MB card gives an error in the CAP-MEM Maintenance Object Test #1014  
(Memory Card Capacity Test). 10 MB cards must also be used if a DEFINITY  
Wireless Business System is connected.  
A memory card has a write-protect switch along its edge. If the write-protect  
switch is enabled, the memory card cannot be written to.  
The 12-volt power supply unit located in Processor circuit pack supports the  
erase and write operations of on-board flash memory devices. The unit also  
supports the memory card inserted in the Processor circuit pack. If the 12 volt  
power supply unit cannot be turned on to supply 12 volts, all erase and write  
operations fail. Refer to 12V-PWR (12 volt power supply) Maintenance  
documentation for a detailed description.  
To write data (for example, translations) onto a memory card, the system software  
first erases the memory card and then writes the data. An erased bit can be  
written again, but a written bit cannot be changed or written again until after the  
next erasure. Software erase and write operations on a memory card take longer  
as the card usage increases. A memory card that cannot be erased or written to  
by software should be replaced.  
Removing A Memory Card From The Slot  
A memory card can be removed from the slot at the Processor circuit pack only  
when the yellow/red LED with a label "EmgXfr/card-in-use" is not glowing.  
Otherwise, the memory card operation might be interrupted abnormally, and the  
files stored in the memory card may become corrupted.  
Resolving an Alarm Raised Against a Memory  
Card  
The list that follows discusses the procedures for resolving an alarm that is raised  
against a memory card:  
1. Remove the inserted memory card from the slot at the Processor circuit  
pack while the "EmgXfr/card-in-use" amber LED is not glowing.  
2. Insert the new formatted memory card firmly into the slot at the Processor  
circuit pack.  
3. Enter the test card-mem command to verify the new memory card.  
4. If the alarm cannot be resolved by replacing the memory card, do the  
following:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-329  
a. Remove the memory card from the Processor circuit pack.  
b. Replace the Processor circuit pack. Follow the standard  
procedures.  
c. Insert the memory card back into the slot at the Processor circuit  
pack.  
d. Enter the test network-control [long] command to verify the new  
circuit pack and the memory card.  
5. Once the alarm is resolved, enter the save translation command to store  
the current system translations to the memory card.  
6. If applicable, enter the save announcements command to store the  
current announcements to the memory card.  
Save Translations Interference  
All of the actions used in DEFINITY R8 administration commands are listed in the  
table below. The command actions that, while active, interfere with daily  
maintenance are also indicated. They are the add, change, duplicate, remove,  
and set commands. These commands are frequently used by customer  
administrators while performing routine administration of DEFINITY.  
Table 3-143. DEFINITY Command Actions  
Likely to  
Disrupt  
Less Likely to  
Disrupt  
add  
backup  
busyout  
clear  
ping  
change  
duplicate  
remove  
set  
recycle  
release  
reset  
display  
enable  
format  
get  
restore  
resume  
save  
list  
status  
test  
mark  
monitor  
netstat  
upgrade  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-330  
Some other command actions can also interfere with daily maintenance when  
certain qualifiers are used in the command, or under certain circumstances. For  
example, certain “test” commands, when used with the modifier “continuously”,  
could potentially interfere with daily maintenance. However, such command  
actions are not used typically by customer administrators doing routine  
administration, and are less likely to disrupt daily maintenance routines than are  
the add, change, duplicate, remove, and set command actions.  
Incomplete Command Time-out  
A time-out feature has been added to the MAINTENANCE-RELATED SYSTEM  
PARAMETERS form (accessed by the command change system parameters  
maintenance). This feature improves the operation of daily maintenance by  
allowing maintenance routines to run that might otherwise not run. It also helps to  
prevent the loss of translations that were not saved by the save translation  
command, and were also not saved because daily maintenance was prevented  
from running prior to the system reset. Highlights of the feature include:  
■
■
■
Options for blank, 1, 2, 3, 4, 5, or 6 hours (the default is 2 hours)  
The blank option indicates that the feature is not active  
Only commands that block the running of daily maintenance (add,  
change, duplicate, remove, and set) are affected  
■
■
All logins will time-out if any of these commands are active for the  
prescribed time (except for the “blank” option)  
The feature applies to all logins, regardless of type (init, dadmin, craft,  
inads) or permissions granted to the specific login ID of an administration  
or maintenance user  
■
The corresponding “time-out” entry is appended to the list history log  
The new Command Time-outfield can be viewed by customer administrators.  
A craft, init, dadmin, or inads login is required to change the option for the field.  
Screen 3-3 shows the MAINTENANCE-RELATED SYSTEM PARAMETERS screen  
for DEFINITY R8r. Screen 3-4 shows an example of the LIST HISTORY form with  
the “time-out” entry. The final line indicates that the command change  
system-parameters maintenance was being executed when the time-out  
period of 2 hours expired.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-331  
change system-parameters maintenance  
Page 1 of 4  
MAINTENANCE-RELATED SYSTEM PARAMETERS  
OPERATIONS SUPPORT PARAMETERS  
Product Identification: 1000000000  
First OSS Telephone Number: 5551212  
Second OSS Telephone Number: 5551213  
Alarm Origination to OSS Numbers: both  
Cleared Alarm Notification? y  
Abbrev Alarm Report? y  
Abbrev Alarm Report? n  
Suspension Threshold: 5  
Restart Notification? y  
Test Remote Access Port? n  
CPE Alarm Activation Level: none  
SCHEDULED MAINTENANCE  
Start Time: 22: 00  
Stop Time: 04: 00  
Daily Maintenance: daily  
Save Translation: daily  
Command Time-out (hours): 2  
System Clocks Interchange: no  
Control Channel Interchange: no  
SPE Interchange: no  
Screen 3-1. Maintenance-Related System Parameters (change system-parameters  
maintenance) for R8r.  
list history  
HISTORY  
Date of Loaded Translation: no translation loaded  
Date  
Time  
Port  
Login  
Actn  
Object  
Qualifier  
9/18  
9/18  
9/18  
16:13  
16:13  
14:13  
MGR1  
MGR1  
MGR1  
init  
init  
init  
logn  
logf  
TIME-OUT  
cha system-param maintenance  
Screen 3-2. New “Command Time-out” Entry in the LIST HISTORY Form.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-332  
Error Log Entries and Test to Clear Values  
Table 3-144. Memory Card Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
test card-mem  
1
0
0
Any  
Any  
Any  
1(a)  
Memory Card Insertion  
Test (#695)  
MINOR  
OFF  
OFF  
OFF  
OFF  
test card-mem  
257(b)  
513(c)  
769(d)  
Memory Card Format and  
Read Test (#696)  
MINOR  
test card-mem  
test card-mem  
test card-mem  
Any  
Memory Card Match and  
Read Test (#697)  
WARNING  
WARNING  
Memory Card  
Write-Protected Test  
(#698)  
1025(e)  
104  
105  
106  
107  
108  
Memory Card Dir.  
Recovery Test (#699)  
MINOR  
OFF  
test card-mem  
1281(f)  
Any  
Memory Card Translation  
Data Integrity Test (#694)  
MINOR  
MINOR  
OFF  
OFF  
test card-mem long  
test card-mem long  
1537(g)  
104  
105  
106  
107  
108  
Memory Card  
Erase/Write/Read Test  
(#693)  
3329(h)  
any  
None  
MINOR/  
MAJOR  
OFF  
3841(i)  
3843(j)  
Any  
Any  
Save Translation  
Save Translation  
MINOR  
MINOR  
OFF  
OFF  
save translation  
save translation  
1. Run the Short Test sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. System detects that no memory card is inserted in the slot at the  
Processor circuit pack. If a memory card is in place, the memory card may  
have a bad physical connection.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-333  
b. System software cannot recognize the inserted memory card because the  
inserted memory card is not formatted or the directories in the memory  
card are corrupted. The system cannot use this memory card. The  
memory card must be replaced with a good memory card.  
c. The inserted memory card does not have enough storage space to  
support system operations, such as saving translations and, if applicable,  
announcements; or, the memory card is a system-upgrade memory card  
that cannot be used for saving translations. This hardware error raises a  
WARNING/OFF_BOARD alarm. The memory card should be replaced with  
one of the recommended size.  
The Aux Datafield contains the following error codes:  
101  
102  
Inserted memory card is a system-upgrade memory card  
While the announcement feature is in use, no announcement file is  
available in the memory card  
103  
The inserted memory card is a system-upgrade memory card, and,  
while the announcement feature is in use, no announcement file is  
available in the memory card.  
116  
The capacity of the inserted memory card doesn’t match the system  
configuration.  
118  
While the announcement feature is in use, no announcement file is  
available in the memory card, and the capacity of the inserted memory  
card doesn’t match the system configuration.  
132  
134  
System translation reaches a 98% capacity of the memory card  
reserved storage space.  
While the announcement feature is in use, no announcement file is  
available in the memory card, and system translation reaches a 98%  
capacity of the memory card reserved storage space.  
148  
150  
The capacity of the inserted memory card doesn’t match the system  
configuration, and system translation reaches a 98% capacity of the  
memory card reserved storage space.  
While the announcement feature is in use, no announcement file is  
available in the memory card, and the capacity of the inserted memory  
card doesn’t match the system configuration. Also, the system  
translation reaches a 98% capacity of the memory card reserved  
storage space.  
d. The write-protection switch of the memory card is in the "protected"  
position. A write-protected memory card can not be erased or written.  
Before entering the test command to resolve the alarm, follow the  
standard procedure for taking the memory card out of the slot. Then,  
change the "write-protection" switch to the "not-protected" position. Finally,  
insert the memory card back into the slot.  
e. The memory card has been detected with a broken directory. A  
MINOR/OFF_BOARD alarm is raised when maintenance cannot restore  
the broken directory. The memory card must be replaced before the test to  
resolve the alarm is run.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-334  
The Aux Datafield contains the following error codes:  
104  
Directories on the memory card are corrupted and cannot be  
recovered.  
105  
106  
107  
108  
"0" cannot be written into the memory card before an erase operation.  
Memory card cannot be erased.  
Data cannot be written into a memory card after an erasure.  
12-volt power supply for directory recovery can’t be turned on. The 12  
volt power supply on Processor circuit pack may be defective. Follow  
the standard procedure to replace the Processor circuit pack.  
f. The translations file stored in the memory card is corrupted with a  
checksum error during the read operation. The memory card can no  
longer hold the written data. Enter the save translation command to  
restore the translations. Then, run the test command to clear the alarm. If  
the error occurs repeatedly, replace the memory card.  
g. The Memory Card Erase/Write/Read Test failed. Enter the status  
card-mem command to verify that a user’s memory card is inserted and  
that the write-protection switch of the memory card is off. Rerun the test  
card-mem command to verify that the 12 volt power supply is functional.  
Enter the test card-mem long command again to verify the test result of  
the Memory Card Erase/Write/Read Test. If the test still fails, the memory  
card should be replaced. After the new memory card is inserted, enter the  
test card-mem long command again to resolve the alarm.  
The Aux Datafield contains the same error codes as for Error Type 1025.  
See Note (e).  
h. There was an error while translations were being loaded. The relevant  
alarm occurs at power-up or on a Reset System 3, 4, or 5 if the switch  
cannot load translations.  
In a standard system, the alarm invokes Emergency Transfer. The repair  
procedure for a standard system is provided in the list that follows:  
NOTE:  
Follow this procedure only if there are no other memory card errors  
or alarms. If such errors or alarms exist, resolve them before trying to  
resolve this alarm.  
1. After you resolve all other memory card problems, issue the reset  
system 3 command.  
2. After the system is restarted, issue the status card-mem  
command.  
3. If the "translation" is not present, insert a backup memory card and  
then issue the reset system 3 command.  
i. The "save translation" operation failed. The reasons for failure are  
described in the Aux Datafield and include the following:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-335  
1
Directory file on the memory card failed the checksum test  
3
Too many commands are running  
Command has been aborted  
4
5
Command has collided with a current command  
Software controller is idle  
6
7
Memory card has been erased  
8
Only one good directory is on the card  
9
All directories are corrupted, and the memory card needs reformatting  
Hard patch file is full  
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
27  
28  
29  
Hardware fault: data can’t be written into the memory card  
Software error: passed parameters were out of range  
Command has been aborted  
Magic number is illegal  
Driver was trapped when reading the memory card  
No memory card is inserted  
Second directory in the memory card could not be found  
File in the memory card is not available  
Memory card does not match the system usage  
Memory card is too small for the system usage  
Broken directory couldn’t be recovered  
System upgrade card is inserted  
Illegal write is requested  
Generic software failure  
Driver timed out  
Driver is unable to program "O’s" in the memory card  
Memory card can’t be erased  
Memory card is write-protected  
12 volt power supply could not be turned on  
A MINOR/OFF_BOARD alarm is raised when two consecutive "save  
translation" operations fail. The alarm is resolved only when the translation  
is saved onto the memory card successfully.  
j. The save translations failure is due to other hardware failures. Enter the  
test card-mem long command and resolve other card-mem failures first.  
After the all test card-mem pass message is received, use the save  
translation command to resolve this error.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-336  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the Memory Card Insertion Test for example, you  
may also clear errors generated from other tests in the testing sequence.  
Table 3-145. System Technician-Demanded Tests: CARD-MEM  
ShortTest  
Sequence  
Long Test  
Sequence  
Reset Board  
Sequence  
1
Order of Investigation  
D/ND  
ND  
12 Volt Power Supply Test (#701) (a)  
Memory Card Insertion Test (#695)  
X
X
X
X
X
X
X
X
X
X
X
X
X
ND  
Memory Card Format and Read Test (#696)  
Memory Card Match Test (#697)  
ND  
ND  
Memory Card Write-Protected Test (#698)  
Memory Card Directory Recovery Test (#699)  
ND  
ND  
Memory Card Translation Data Integrity Test  
(#694)  
ND  
Memory Card Erase/Write/Read Test (#693)  
X
ND  
1. D = Destructive; ND = Nondestructive  
Note:  
a. Refer to 12V-PWR (12 Volt Power Supply) Maintenance documentation for  
a description of this test.  
Memory Card Erase/Write/Read Test (#693)  
The purpose of this test, which is nondestructive, is to verify the erase, write, and  
read operations. The test erases the backup copy of the translation file stored in  
the memory card, and it verifies that the erase operation works. The test then  
writes the primary copy of the translation file from the same memory card to the  
erased flash segment, and it verifies that the translation file is written  
successfully.  
This test can be initiated through a system technician demanded test card-mem  
long command, or it can be executed as part of a maintenance test sequence  
when the save translation and save announcements operations fail. The test  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-337  
and relevant applications (for example, saving translations, saving  
announcements) cannot be executed at the same time.  
Table 3-146. TEST #693 Memory Card Erase/Write/Read Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Applications are accessing the memory card.  
1192  
ABORT  
1. Wait 10 minutes for the applications to complete.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
2012  
2106  
2114  
ABORT  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2013  
2100  
none  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2110  
2111  
2112  
2115  
2113  
No memory card is inserted.  
1. Insert a formatted memory card into the slot at the Processor circuit  
pack.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Inserted memory card cannot be recognized.  
ABORT  
ABORT  
ABORT  
ABORT  
1. Insert a formatted memory card into the slot at the Processor circuit  
pack.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error The inserted memory card is a "system-upgrade"  
memory card.  
1. Replace the inserted memory card with a user’s memory card.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
The memory card is write-protected.  
1. Take the memory card out, and change the "write-protection" switch to  
the "not-protected" position.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
The inserted memory card has only one directory file.  
1. Enter the test card-mem command, and verify that the Memory Card  
Directory Recovery Test (#699) passes. If the directory file cannot be  
recovered, replace the memory card.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-338  
Table 3-146. TEST #693 Memory Card Erase/Write/Read Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2117  
ABORT  
No translation file has been saved onto the memory card.  
1. Enter the save translation command, and verify that the translations are  
saved onto the memory card successfully.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Directories on the memory card are corrupted and cannot be recovered.  
"0" cannot be written into memory before an erase operation.  
Memory card cannot be erased.  
104  
105  
106  
107  
FAIL  
FAIL  
FAIL  
FAIL  
Data cannot be written onto a memory card after an erasure.  
1. Replace the memory card and re-run the test.  
108  
FAIL  
12-volt power supply for the Memory Card Erase/Write/Read Test can’t be  
turned on. The 12-volt power supply on Processor circuit pack may be  
defective.  
1. Re-enter the test card-mem command, and verify the result of Test #701  
for the 12 Volt Power Supply.  
2. If Test #701 fails, follow the Standard Repair Procedure to replace the  
Processor circuit pack.  
3. Retry the command a 1-minute intervals a maximum of 5 times.  
Memory Card Translation Data Integrity Test  
(#694)  
This test, which is nondestructive, verifies the integrity of the translation file stored  
in the memory card by reading (without any PREC updates) the translation file  
from the memory card and by then performing a checksum error checking. The  
calculated checksum value is compared with the recorded checksum value in  
the translation file. If these two values are different, this indicates that the  
translation file is corrupted.  
Table 3-147. TEST #694 Memory Card Translation Data Integrity Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2012  
2106  
2114  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-339  
Table 3-147. TEST #694 Memory Card Translation Data Integrity Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2013  
2100  
none  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2110  
2111  
2112  
Any  
ABORT  
No memory card is inserted.  
1. Insert a formatted memory card into the slot at the Processor circuit  
pack.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Inserted memory card cannot be recognized.  
ABORT  
ABORT  
FAIL  
1. Insert a new formatted memory card into the slot at the Processor  
circuit pack.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error The inserted memory card is a system-upgrade  
memory card.  
1. Replace the inserted memory card with a user’s memory card.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
A checksum error is detected in the translation file that is stored in the  
inserted memory card.  
1. Enter the save translation command, and verify that translations can  
be successfully saved onto the memory card.  
2. Rerun the test.  
3. If the test fails again, replace the memory card, and repeat Steps 1  
and 2.  
PASS  
No checksum error is found in the translation file.  
Memory Card Insertion Test (#695)  
This test, which is nondestructive, verifies whether a memory card is inserted into  
the memory card slot at the Processor circuit pack and also whether the system  
can detect its existence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-340  
Table 3-148. TEST #695 Memory Card Insertion Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2012  
2106  
2114  
ABORT  
ABORT  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2013  
2100  
none  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
No memory card is inserted in the Processor circuit pack, or the inserted  
memory card has a bad connection.  
1. Insert a memory card into the slot at the Processor circuit pack.  
2. If a memory card is already inserted, take the memory card out and  
examine the connectors of the memory card and the Processor circuit  
pack. Insert the memory card into the slot again.  
3. When a memory card is pushed into the slot, make sure that the  
memory card is inserted firmly into the slot.  
4. Re-enter the test card-mem command. If the test still fails, replace the  
memory card, and then repeat this step one more time.  
5. If the test still fails after you replace the memory card, replace the  
Processor circuit pack. Follow the Standard Repair Procedures for a  
memory card.  
PASS  
A memory card is inserted into the Processor circuit pack, and the system  
can recognize its existence.  
Memory Card Format and Read Test (#696)  
This test is a nondestructive test. The memory card must be formatted before an  
application. The test reads the directory file from the memory card, and it verifies  
the integrity of the directory file.  
Table 3-149. TEST #696 Memory Card Format and Read Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2012  
2106  
2114  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-341  
Table 3-149. TEST #696 Memory Card Format and Read Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2013  
2100  
none  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2110  
2113  
ABORT  
No memory card is inserted.  
1. Insert a formatted memory card into the slot at the Processor circuit  
pack.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
One of the two directories in the memory card is corrupted.  
ABORT  
1. Re-enter the test card-mem command, and verify that Test #699  
passes.  
2. If the test is aborted again with this error code, replace the memory  
card.  
FAIL  
System software cannot recognize the inserted memory card. The memory  
card is not formatted, or the directories of the memory card are corrupted.  
1. Replace the memory card with a new formatted memory card.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
System recognizes the inserted memory card, and it can read the  
directories from the memory card.  
Memory Card Match Test (#697)  
This test is a nondestructive test. The test verifies the inserted memory card for  
consistency with the system configuration. The test helps answer the following  
questions:  
■
Is the inserted memory card a system software upgrade card?  
■
Does the size of the inserted memory card match the capacity of the  
system configuration?  
■
■
Does the inserted memory card contain the Announcement file for a  
system with an Announcement circuit pack?  
Does the size of the translations in the system reach 98% of the reserved  
storage space on the memory card?  
If the answer to any of these questions is "yes," maintenance raises a WARNING  
alarm for service attention. A new memory card is usually required.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-342  
Table 3-150. TEST #697 Memory Card Match Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2012  
2106  
2114  
ABORT  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2013  
2100  
none  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2110  
2111  
No memory card is inserted.  
1. Insert a formatted memory card into the slot at the Processor circuit  
pack.  
2. Rerun the test.  
ABORT  
Inserted memory card is not formatted.  
1. Insert a formatted memory card into the slot at the Processor circuit  
pack.  
2. Rerun the test.  
101  
FAIL  
The inserted memory card is a system-upgrade memory card.  
1. Replace the memory card with a user’s memory card.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
102  
FAIL  
The inserted memory card does not contain an Announcements file, and  
the system is configured with the Announcement feature.  
1. Replace the memory card with a 10 MB memory card.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
103  
FAIL  
The memory card is a system-upgrade memory card and, while the  
announcement feature is in use, no announcement file is available in the  
memory card. Possible causes include:  
■ The customer has had a recent upgrade and is using an old card.  
■ The card is not formatted for announcements  
1. Replace the memory card with the appropriate size and formatting.  
See the system configuration guidelines.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
116  
FAIL  
The capacity of the inserted memory card doesn’t match the system  
configuration.  
1. Replace the memory card with one of a larger size. See the system  
configuration guidelines.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-343  
Table 3-150. TEST #697 Memory Card Match Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
118  
FAIL  
While the announcement feature is in use, no announcement file is  
available in the memory card, and the capacity of the inserted memory  
card doesn’t match the system configuration.  
1. Replace the memory card with one of a larger size. See the system  
configuration guidelines.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Translation reaches 98% of the memory card reserved storage space.  
132  
134  
FAIL  
FAIL  
1. Replace the memory card with one of a larger size. See the system  
configuration guidelines.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
While the announcement feature is in use, no announcement file is  
available in the memory card, and system translation reaches a 98%  
capacity of the memory card reserved storage space.  
1. Replace the memory card with one of a larger size. See the system  
configuration guidelines.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
148  
150  
FAIL  
FAIL  
The capacity of the inserted memory card doesn’t match the system  
configuration, and system translation reaches 98% of the memory card  
reserved storage space.  
1. Replace the memory card with one of a larger size. See the system  
configuration guidelines.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
While the announcement feature is in use, no announcement file is  
available in the memory card, and the capacity of the inserted memory  
card doesn’t match the system configuration. Also, system translation  
reaches a 98% capacity of the memory card reserved storage space.  
1. Replace the memory card with one of a larger size. See the system  
configuration guidelines.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
The inserted memory card matches the system configuration, and the card  
has enough space for saving translations and (if applicable)  
announcements.  
Memory Card Write-Protection Test (#698)  
This test, which is nondestructive, verifies whether the write-protected switch on  
the memory card is turned on. The memory card cannot be erased or written to  
when the write-protected switch is on.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-344  
Table 3-151. TEST #698 Memory Card Write-Protected Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2012  
2106  
2114  
ABORT  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2013  
2100  
none  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2110  
2111  
No memory card is inserted.  
1. Insert a formatted memory card into the slot at the Processor circuit  
pack.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Inserted memory card is not formatted.  
ABORT  
FAIL  
1. Insert a formatted memory card into the slot at the Processor circuit  
pack.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
The Write-Protect switch of the inserted memory card is set to the protect  
position.  
1. Take the memory card out, and move the write-protect switch to the  
"not-protected" position.  
2. Insert the memory card back into the slot.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
The inserted memory card is not write-protected.  
PASS  
Memory Card Directory Recovery Test (#699)  
This test is a nondestructive test. All memory cards, except the memory card for  
system software upgrade, have two copies of both directory files and translation  
files to ensure that there is at least a good translation file in the memory card at  
any time, especially during the "save translation" operation.  
If one of the two directory files (for example, the directory file) is missing or  
broken (for example, the directory file has a bad checksum), maintenance can  
build the directory file. The Memory Card Directory Recovery Test  
■
Verifies the integrity of both active and backup directory files in a memory  
card, and  
■
Requests a rebuilding of the directory file if the file is missing or corrupted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-345  
When the test passes, both directories are sane. If the memory card is a  
system-upgrade memory card, the test is aborted. If the test fails, the broken or  
missing directory cannot be rebuilt. As a result, all subsequent "write-to-memory  
card" operations are blocked. When an alarm is raised and Error Type 1025 for  
CARD-MEM is active, replace the memory card.  
Table 3-152. TEST #699 Memory Card Directory Recovery Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Contention error. Applications are accessing the memory card.  
1. Wait 10 minutes for the applications to complete.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
1192  
ABORT  
2012  
2106  
2114  
ABORT  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2013  
2100  
none  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2110  
2111  
2112  
2115  
No memory card is inserted.  
1. Insert a formatted memory card into the slot at the Processor circuit  
pack.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Inserted memory card cannot be recognized.  
ABORT  
ABORT  
ABORT  
1. Insert a new formatted memory card into the slot at the Processor  
circuit pack.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error The inserted memory card is a "system-upgrade"  
memory card.  
1. Replace the inserted memory card with a user’s memory card.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
The memory card is write-protected.  
1. Take the memory card out, flip the "write-protection" switch to the  
"not-protected" position, and insert the memory card back into the slot.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CARD-MEM (Memory Card)  
3-346  
Table 3-152. TEST #699 Memory Card Directory Recovery Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
104  
FAIL  
Directories in the memory card are corrupted and cannot be recovered.  
"0" cannot be written into memory before an erase operation.  
Memory card cannot be erased.  
105  
106  
107  
FAIL  
FAIL  
FAIL  
Data cannot be written into a memory card after the erase operation.  
Maintenance cannot restore the missing or broken directory file in the  
inserted memory card.  
1. Replace the memory card with a new, formatted one.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
108  
FAIL  
12-volt power supply for directory recovery can’t be turned on. The 12-volt  
power supply on Processor circuit pack may be defective.  
1. Re-enter the test card-mem command, and verify the result of Test  
#701 for 12 Volt Power Supply.  
2. If Test #701 fails, follow the Standard Repair Procedure to replace the  
Processor circuit pack.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
Both directory files in the inserted memory card are sane.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-347  
CLAN-BD (Control LAN Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board UUCSS long  
test board UUCSS short  
Full Name of MO  
CLAN-BD  
CLAN-BD  
MINOR  
WARNING  
Control LAN Circuit Pack  
Control LAN Circuit Pack  
1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation (A, B, C,  
D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21).  
Control LAN Circuit Pack  
The TN799 Control LAN (CLAN) packet port circuit pack provides TCP/IP  
connection to adjuncts applications such as CMS, Intuity, and DCS Networking.  
The CLAN circuit pack has 1 10baseT Ethernet connection and up to 16 DS0  
physical interfaces for PPP connections. In addition to the TCP/IP functionality,  
CLAN extends the ISDN capabilities for csi models by providing Packet bus  
access.  
A remote socket control link (RSCL) links the CLAN and the SPE to pass call  
control and other management information. Since one link serves all the ports on  
the circuit pack, maintenance of the RSCL is part of the CLAN circuit pack  
maintenance.  
The CLAN TN799 circuit pack combines the functions of the PGATE and PI circuit  
packs into one circuit pack. The PGATE or PI can be used with the CLAN to  
create an X.25-to-TCP/IP bridge for adjunct and DCS connectivity.  
Control LAN Congestion Controls  
The switch activates congestion controls on CLAN when it detects buffers  
exceeding the threshold. The switch releases the congestion controls when the  
CLAN reports that its buffer level has returned to normal levels.  
If congestion:  
Then the switch:  
Persists for a 14-minute interval, Raises MINOR alarm.  
Exhausts buffers,  
Raises MINOR alarm.  
Retires MINOR alarm.  
Ceases for 12 minutes,  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-348  
Error Log Entries and Test to Clear Values  
Table 3-153. CLAN-BD Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1(a)  
0
MINOR  
ON  
OFF  
ON  
ON  
18 (b)  
217 (c)  
257  
0
WARNING  
WARNING  
MINOR  
release board UUCSS  
test board UUCSS l r 20  
0
None  
65535  
Control Channel  
Loop Test (#52)  
257 (d)  
513 (e)  
4352-  
4357  
MINOR  
MINOR  
ON  
ON  
769 (f)  
4358  
Any  
1293 to  
reset board UUCSS  
1295 (g)  
1537(h)  
1794 (i)  
1798 (j)  
2049 (k)  
Any  
MINOR  
MINOR  
ON  
ON  
Packet Interface  
Test (#598)  
MINOR  
ON  
test board UUCSS l r 3  
2305  
2306 (l)  
2561 to  
Any  
2668 (m)  
2817  
2819 (n)  
Congestion Query  
Test (#600)  
MINOR  
MINOR  
MINOR  
ON  
ON  
ON  
test board UUCSS s r 3  
test board UUCSS s  
reset board UUCSS  
3073 (o)  
Link Status Test  
(#601)  
3330 (p)  
3586 (q)  
3999 (q)  
3840 (r)  
Any  
None  
4096-  
4102  
3841  
3843 (s)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-349  
Table 3-153. CLAN-BD Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
3842 (t)  
3844 (u)  
3845 (v)  
3846 (w)  
3848 (x)  
3849 (y)  
Any  
Any  
Any  
Any  
Any  
Any  
3850-  
3861 (z)  
3862 (aa) Any  
Notes:  
a. Error Type 1: Circuit pack stopped functioning or is not physically  
present.  
1. Verify that the circuit pack is present.  
2. If circuit pack is present, reset the circuit pack (reset board  
UUCSS).  
3. If the error persists, replace the circuit pack.  
b. Error Type 18: The CLAN circuit pack busied out.  
c. Error Type 217: applies to 10 circuit packs:  
1. Remove the circuit pack(s) against which the error is logged.  
d. Error Type 257: Transient communication problem between switch and  
circuit pack; does not affect service and can be ignored.  
1. Ignore this error, unless the Control Channel Loop Test (#52) fails.  
2. If Test #52 fails, replace the circuit pack.  
Repetitive failures of the Control Channel Loop Test indicate circuit pack  
hardware failure.  
e. Error Type 513: Circuit pack detected and reported hardware failure.  
1. Reset the circuit pack (reset board UUCSS).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-350  
Aux Data:  
4352  
4353  
4355  
4356  
4357  
External RAM error  
Internal RAM error  
ROM Checksum error  
Angel Message Corruption error  
Instruction set error  
f. Error Type 769: Logic error. By itself this error may be ignored, but it may  
result in other error types being reported.  
g. Error Type 1293-1295: Critical hardware or firmware error.  
If the switch detects:  
1 error,  
Then the switch:  
Resets circuit pack.  
Raises MINOR alarm.  
3 errors in 15 minutes,  
Error Type descriptions are as follows:  
1293  
1294  
1295  
Insane onboard processor  
Onboard translation RAM error  
(Aux 3) RSCL link down  
(Aux 0) RSCL keep alive failure  
1. Attempt to clear the alarm (reset board UUCSS).  
2. If alarm persists, replace circuit pack.  
h. Error Type 1537: Switch removed hyperactive circuit pack that reported  
threshold number of errors.  
1. Attempt to clear the alarm (reset board UUCSS).  
2. If the error recurs within 15 minutes, replace the circuit pack.  
i. Error Type 1794: Packet bus transmit buffers have overflowed..  
1. Attempt to clear the alarm (reset board UUCSS).  
2. If the error recurs within 15 minutes, replace the circuit pack.  
j. Error Type 1798: Unable to write translation RAM.  
1. Attempt to clear alarm (reset board UUCSS).  
2. If alarm recurs within 15 minutes, replace the circuit pack.  
k. Error Type 2049: Packet Interface Test (#598) failed.  
1. Attempt to clear the alarm (test board UUCSS l r 3).  
2. If alarm does not clear, reset the circuit pack (reset board UUCSS).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-351  
3. If circuit pack resets, execute Packet Interface Test (#598) several  
times.  
4. If Packet Interface Test (#598) continues to fail, replace the circuit  
pack.  
l. Error Type 2305-2306: Error in received frame from packet bus.  
Error Type:  
2305  
Description  
Received invalid LAPD frame.  
Detected parity error on received frame.  
2306  
Most likely cause—packet bus problem.  
Other cause—circuit pack fault.  
Invalid LAPD frame errors occur when the frame  
■
■
■
contains a bad Cyclic Redundancy Check (CRC),  
is greater than the maximum length,  
violates the link level protocol.  
1. Retry the command (test board UUCSS) and see if the condition  
clears.  
2. If condition persists, execute PPE/LANBIC Receive Parity Error  
Counter Test (# 597) and determine if the condition clears.  
3. If condition persists, execute Packet Interface Test (# 598) to verify  
circuit pack integrity.  
4. If Packet Interface Test (# 598) fails, consult repair procedure for  
the packet bus.  
m. Error Type 2561-2668: System software received an indication that the  
socket was closed due to an error. Errors are reported as log only. Errors  
logged here are for the sockets that had no processor channels  
associated with them, for example, sockets to read SNMP data. The  
counter base is offset by the application type of the application associated  
with this socket that is down. The Aux Data field of the log entry contains  
this application’s number, for example, a SNMP application would have its  
application number in the Aux Data field.  
NOTE:  
2561 - 2668 is a range of reserved numbers for future applications.  
2570 currently represents an SNMP socket failure.  
n. Error Type 2817-2819: Congestion Query Test (#600) failed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-352  
The Error Types correspond to the descriptions:  
2817  
2819  
All buffers exhausted.  
Utilized buffers exceed threshold.  
If:  
Then:  
Active buffers exceed threshold, CLAN enters congested state.  
1. Refer to Congestion Query Test (# 600) for Abort and Fail 3601s.  
o. Error Type 3073: Remote Socket Control Link (RSCL) or Link Status Test  
(#601) failed. This failure may be due to:  
■
■
■
This circuit pack  
The packet bus  
The packet interface circuit pack.  
If:  
Then:  
RSCL disconnects at link level  
Link fails  
Link cannot be reconnected quickly  
Switch raises MINOR alarm  
p. Error Type 3330: Critical failure in Packet Bus interface.  
Below, Error Types correspond to descriptions.  
If the switch detects:  
1 error,  
Then it:  
Resets circuit pack.  
Raises MINOR alarm.  
2 errors in 15 minutes,  
1. Attempt to clear the alarm (reset board UUCSS).  
2. If alarm persists, replace circuit pack.  
q. Error Type 3586 and 3999: Switch removed hyperactive circuit pack that  
reported threshold number of errors. One or more of the following  
symptoms may be present:  
■
Circuit pack port tests return NO BOARD.  
■
List configuration command shows circuit pack and ports are  
installed properly  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-353  
And traffic  
volume is:  
If Error Type 3999:  
Then:  
Does not accompany  
Error Type 3586,  
Heavy  
Circuit pack is in service, but  
sent at least half hyperactive  
threshold. With heavy traffic, this  
is normal.  
Does not accompany  
Error Type 3586,  
Light  
Circuit pack is in service, but  
sent at least half hyperactive  
threshold. With light traffic, this  
error indicates a problem with the  
circuit pack, its links, or the  
equipment attached to the links.  
Accompanies Error  
Type 3586,  
Either Light or  
Heavy  
Switch removed hyperactive  
circuit pack.  
1. Busyout (busyout board UUCSS) and release (release board  
UUCSS) circuit pack  
2. Allow 30 minutes for condition to clear itself.  
3. To re-establish circuit pack into service manually, busyout (busyout  
board UUCSS), reset (reset board UUCSS), and release (release  
board UUCSS) the circuit pack.  
4. If error recurs within 15 minutes, replace the circuit pack.  
5. If the same error occurs on a different circuit pack, follow normal  
escalation procedures.  
r. Error Type 3840: Circuit pack received bad control channel message  
from switch.  
Aux Data:  
4096  
4097  
4098  
4099  
4100  
4101  
4102  
Bad major heading  
Bad port number  
Bad data  
Bad sub-qualifier  
State inconsistency  
Bad logical link  
Bad application identifier  
s. Error Type 3841-3843: errors do not affect service.  
Below, Error Types correspond to descriptions.  
3841  
3843  
Internal firmware error.  
Bad translation RAM. Call uses another translation location.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-354  
These errors do not affect service, however, they may cause reports of  
other errors that do affect service.  
If Error Type 3843 begins to affect service, it escalates to Error Type 1294.  
t. Error Type 3842: Packet interface receive buffers overflowed.  
If this error occurs frequently, the overflow may be congesting the circuit  
pack.  
1. Refer to Receive FIFO Overflow Error Counter Test (#596).  
u. Error Type 3844: LAPD frame contains LAPD Protocol Error.  
By themselves, these errors do not affect service.  
v. Error Type 3845: Angel inter processor error.  
By themselves, these errors do not affect service.  
w. Error Type 3846: High CPU occupancy.  
By themselves, these errors do not affect service.  
x. Error Type 3848: Interprocessor LAPD protocol error.  
By themselves, these errors do not affect service.  
y. Error Type 3849: Interprocessor LAPD frame error.  
By themselves, these errors do not affect service.  
z. Error Type 3850 - 3861: IBL error.  
By themselves, these errors do not affect service. These errors can occur  
only on a G3csi machine that has an Interboard Link (IBL).  
aa. Error Type 3862: Memory allocation failure.  
By themselves, these errors do not affect service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-355  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Investigate errors in the order they appear in the table below.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Control Channel Loop-Around Test #52  
Circuit Pack Restart Test #252  
D/ND  
X
X
ND  
D
Invalid LAPD Frame Error Counter Test #597  
X
X
ND  
ND  
PPE/LANBIC Receive Parity Error Counter Test  
#595  
Receive FIFO Overflow Error Counter Test #596  
Packet Interface Test #598  
X
X
X
X
ND  
ND  
ND  
ND  
X
X
X
Congestion Query Test #600  
Link Status Test #601  
1. D = Destructive; ND = Nondestructive  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-356  
Control Channel Loop-Around Test (#52)  
This non-destructive test fails if the circuit pack does not return to a sane state  
after being reset. This test queries the circuit pack for its code and vintage, and  
verifies its records.  
Table 3-154. TEST #52 Control Channel Loop-Around Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Could not allocate the necessary system resources to run test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the problem persists, escalate the problem.  
None  
2100  
ABORT  
FAIL  
The circuit pack failed to return the code or vintage.  
1. Retry command at 1-minute intervals, up to 5 times.  
2. Reset the board (reset board UUCSS).  
3. If reset aborts with error code 1115, busyout (busyout board UUCSS),  
reset (reset board UUCSS), and release board (release board UUCSS).  
4. If test continues to fail, replace the circuit pack.  
5. Escalate the problem if failures continue.  
Test successful.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-357  
Circuit Pack Restart Test (#252)  
NOTE:  
This test is destructive.  
Execute this test (not part of either short or long demand test sequence) to reset  
the circuit pack only if there are PPCPU errors. This test fails if the circuit pack  
does not return to a sane state after being reset. The circuit pack resets through  
the SAKI Sanity Test (#53).  
Table 3-155. Test #252 Circuit Pack Restart Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Could not allocate the necessary system resources to run test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the problem persists, escalate the problem.  
Port is not out-of-service.  
None  
ABORT  
1015  
ABORT  
1. Busyout the circuit pack (busyout board UUCSS).  
2. Retry the command at 1-minute intervals, up to 5 times.  
3. If the problem persists, escalate the problem.  
Could not allocate the necessary system resources to run test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the problem persists, escalate the problem.  
The circuit pack failed to reset.  
2100  
1, 2  
ABORT  
FAIL  
1. Retry command at 1-minute intervals, up to 5 times.  
2. If the problem persists, pull out and reseat the circuit pack.  
3. If the problem persists, replace the circuit pack.  
The circuit pack initialized correctly.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-358  
PPE/LANBIC Receive Parity Error Counter Test  
(#595)  
This test is non-destructive. When the CLAN circuit pack detects a parity error  
with a received frame, it increments the PPE/LANBIC Receive Parity error  
counter. This test reads and clears the counter, and may verify repair of problem.  
Errors may indicate a problem with:  
■
■
■
This circuit pack  
A packet bus  
Another circuit pack on the bus  
Table 3-156. TEST #595 PPE/LANBIC Receive Parity Error Counter Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Did not receive circuit pack test response within the allowable time period.  
1. Retry command at 1-minute intervals, up to 5 times.  
2. If the problem persists, reset the circuit pack (reset board UUCSS).  
3. If the problem persists, replace the circuit pack.  
Could not allocate the necessary system resources to run test.  
Internal system error.  
2000  
ABORT  
2100  
2500  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the problem persists, escalate the problem.  
1-10  
FAIL  
Circuit pack detects parity errors. The Error Code indicates the value of the  
on-board error counter.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the test continues to fail, execute the Packet Interface Test (#598) (test  
board UUCSS).  
3. If Packet Interface Test (#598) fails, see Packet Bus repair procedures.  
Circuit pack detects no errors.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-359  
Receive FIFO Overflow Error Counter Test (#596)  
This test is non-destructive. When the CLAN circuit pack detects packet bus  
buffer overflow, it increments the error on the FIFO Overflow error counter. This  
test reads and clears the counter.  
If errors are:  
Occasional  
Persistent  
Then they may be due to:  
Statistical buffer sizing  
Circuit pack congestion that requires redistribution of traffic load  
Table 3-157. TEST #596 Receive FIFO Overflow Error  
Counter Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Did not receive circuit pack test response within the allowable time period.  
1. Retry command at 1-minute intervals, up to 5 times.  
2. If the problem persists, reset the circuit pack (reset board UUCSS).  
3. If the problem persists, replace the circuit pack.  
Could not allocate the necessary system resources to run test.  
Internal system error.  
2000  
ABORT  
2100  
2500  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the problem persists, escalate the problem.  
1-10  
FAIL  
Circuit pack detects overflow errors. The error code indicates the value of the  
on-board error counter.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the test continues to fail, execute the Packet Interface Test (#598) (test  
board UUCSS).  
3. If Packet Interface Test (#598) fails, refer to Packet Bus repair procedures.  
Circuit pack detects no errors.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-360  
Invalid LAPD Frame Error Counter Test (#597)  
This test is non-destructive.  
CLAN detects invalid frames when it receives  
■
■
■
a frame with a CRC error  
an unrecognizable frame  
a recognizable frame in an unexpected state  
When the CLAN circuit pack detects an invalid LAPD frame, it increments the  
Invalid LAPD Frame error counter. This test reads and clears the counter, and  
verifies the repair of the problem.  
Errors may indicate a  
■
■
■
circuit pack problem  
packet bus problem  
problem with another circuit pack on the bus  
Table 3-158. TEST #597 Invalid LAPD Frame Error  
Counter Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Did not receive circuit pack test response within the allowable time period.  
1. Retry command at 1-minute intervals, up to 5 times.  
2. If the problem persists, reset the circuit pack (reset board UUCSS).  
3. If the problem persists, replace the circuit pack.  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
2000  
ABORT  
2100  
2500  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the problem persists, escalate the problem.  
1-10  
FAIL  
The circuit pack detects LAPD frame errors. The error code indicates the  
value of the on-board error counter.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the test continues to fail, execute the Packet Interface Test (#598) (test  
board UUCSS long).  
3. If Packet Interface Test (#598) fails, refer to Packet Bus repair procedures.  
Circuit pack detects no errors.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-361  
Packet Interface Test (#598)  
This non-destructive test checks the packet bus interface circuitry on the CLAN  
circuit pack. Test failure indicates faulty circuit pack.  
Table 3-159. TEST #598 Packet Interface Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Did not receive circuit pack test response within the allowable time period.  
1. Retry command at 1-minute intervals, up to 5 times.  
2. If the problem persists, reset the circuit pack (reset board UUCSS).  
3. If the problem persists, replace the circuit pack.  
2000  
ABORT  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run test.  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the problem persists, escalate the problem.  
FAIL  
Circuit pack has detected a failure of the Packet Interface Test (#598).  
1. Retry command at 1-minute intervals, up to 5 times.  
2. If the problem persists, reset the circuit pack (reset board UUCSS).  
3. If the test continues to fail, replace the circuit pack.  
The Packet Interface Test (#598) passed.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-362  
Congestion Query Test (#600)  
This non-destructive test queries the number of used buffers to determine if the  
CLAN circuit pack is congested.  
If:  
Then:  
Used buffers are, or are nearly,  
exhausted,  
The test fails  
The test fails,  
The switch redirects outgoing calls to  
another available CLAN, and denies new  
incoming calls  
Normal call handling resumes when the CLAN circuit pack has recovered from  
congestion.  
Table 3-160. TEST #600 Congestion Query Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Did not receive circuit pack test response within the allowable time period.  
1. Retry command at 1-minute intervals, up to 5 times.  
2. If the problem persists, reset the circuit pack (reset board UUCSS).  
3. If the problem persists, replace the circuit pack.  
Could not allocate the necessary system resources to run test.  
Internal system error.  
2000  
ABORT  
2012  
2100  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the problem persists, escalate the problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-363  
Table 3-160. TEST #600 Congestion Query Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The buffer level is nearly exhausted.  
1
FAIL  
2
FAIL  
The CLAN is congested, and no buffers are available.  
1. Retry command at 1-minute intervals, up to 5 times.  
2. If command continues to fail, examine the CLAN port measurements to  
determine which ports are heavily utilized and the processor occupancy  
of the circuit pack.  
Low processor occupancy when CLAN congested indicates circuit pack  
failure.  
1. If the problem persists, reset the circuit pack (reset board UUCSS).  
2. If congestion recurs, replace the circuit pack.  
High processor occupancy indicates the CLAN is congested due to traffic  
load.  
1. To relieve congestion in the short term, selectively busyout ports (busyout  
port UUcSSpp) on the Control LAN circuit pack.  
2. To achieve a more permanent resolution, it may be necessary to move  
ports on this circuit pack to other Control LAN circuit packs.  
3. Consider replacing affected CLAN ports with new ports.  
3
FAIL  
The CLAN circuit pack is not operating normally and is congested.  
PASS  
Hardware setting and attached cable type match CLAN circuit pack  
administration. The circuit pack detects no errors.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLAN-BD (Control LAN Circuit Pack)  
3-364  
Link Status Test (#601)  
This non-destructive test determines the state of the call control signaling link for  
Control LANs. If the signaling link is physically connected, the test sends a test  
frame over the link and checks for a response. The test passes only if both the  
signaling link is connected and the test frame is successfully transmitted.  
A failure may indicate a problem with::  
■
■
■
This circuit pack  
The packet bus  
The packet interface circuit pack  
Table 3-161. TEST #601 Link Status Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
RSCL link or C-LAN board not in service.  
1125  
ABORT  
1. Release the board.  
2. Repeat the test.  
3. Escalate if the problem persists.  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
1. Retry command at 1-minute intervals, up to 5 times.  
2. If the problem persists, escalate the problem.  
The RSCL control link disconnected.  
1. Retry command at 1-minute intervals, up to 5 times.  
2
FAIL  
2. If the test continues to fail, execute the Packet Interface Test (#598) (test  
board UUCSS) to determine if the problem is due to the circuit pack.  
3. If the Packet Interface Test (#598) fails, refer to Packet Interface Test repair  
procedures.  
4. If the Packet Interface Test (#598) passes, refer to Packet Control Circuit  
Pack and Packet Bus repair procedures.  
3
FAIL  
Received no response to RSCL control link test frame.  
1. Retry command at 1-minute intervals, up to 5 times.  
2. If the problem persists, reset the circuit pack (reset board UUCSS).  
3. If test continues to fail, replace the circuit pack.  
RSCL control link connected.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLSFY-BD (Call Classifier Circuit Pack)  
3-365  
CLSFY-BD (Call Classifier Circuit  
Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
Call Classifier Circuit Pack  
Call Classifier Circuit Pack  
CLSFY-BD  
CLSFY-BD  
MIN  
WRN  
test board PCSS sh  
test board PCSS sh  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example,  
A, B, or C); and SS is the address of the slot in the carrier where the circuit pack is located  
(for example, 01, 02, ..., etc.).  
Refer to XXX-BD (Common Port Circuit Pack) Maintenance documentation for  
circuit pack level errors. See also Call Classifier Port (CLSFY-PT) Maintenance  
documentation for related port information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLSFY-PT (Call Classifier Port)  
3-366  
CLSFY-PT (Call Classifier Port)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test port PCSSpp sh  
test port PCSSpp sh  
release port PCSSpp  
Full Name of MO  
CLSFY-PT(a)  
CLSFY-PT  
CLSFY-PT  
MAJOR  
Call Classifier Port Maintenance  
Call Classifier Port Maintenance  
Call Classifier Port Maintenance  
MINOR  
WARNING  
1. Where P is the port network number (1 for PPN); C is the carrier designation (A, B, or C); SS is the  
address of the slot in the carrier where the circuit pack is located (01, 02, ..., and so forth); and pp  
is the 2-digit port number (01, 02, ..., and so forth).  
The TN744D Call Classifier (CLSFY-BD) circuit pack is a service circuit pack that  
enables usage of the Outbound Call Management (OCM) and the Inbound Call  
Management (ICM) features. The TN744D also enables usage of R2-MFC  
signaling for incoming and outgoing feature operation. There are eight ports  
(CLSFY-PTs) on the Call Classifier circuit pack. Each port can handle call  
classification, touch-tone reception, or MFC tone generation and detection or  
touch-tone reception.  
The CLSFY-PT maintenance feature defines a set of tests to ensure that the Call  
Classifier circuit pack ports are capable of detecting tones for call classification  
and detecting and generating necessary tones for correct MFC feature  
operation.  
NOTE:  
A TN744D Call Classifier/Tone Detector circuit pack may be required in  
systems with heavy traffic. This circuit pack can be installed into any port,  
although slot 1 of Cabinet B is preferred.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLSFY-PT (Call Classifier Port)  
3-367  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-162. Call Classifier Port (CLSFY-PT) Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1
any  
Tone Detector  
Audit/Update Test  
(#43)  
MAJOR/  
MINOR (a)  
ON  
test port PCSSpp r 2  
18  
Port has been  
busied out by  
WARNING  
OFF  
release port PCSSpp  
system technician  
257 (b)  
513 (c)  
17666  
any  
Test (#43)  
MAJOR/  
MINOR (a)  
ON  
ON  
test port PCSSpp r 3  
test port PCSSpp r 3  
Tone Detection  
Verification Test  
(#42)  
MAJOR/  
MINOR (a)  
Notes:  
a. There are two possible alarm levels for this error type: major alarm and  
minor alarm. A major alarm is raised if the total number of call classifier  
ports currently in-service is less than or equal to 1/2 of the administered  
threshold number. Otherwise, a minor alarm is raised. In either case, run  
the short test sequence against the port and follow the error code  
procedures for the individual tests.  
The threshold number of call classifier ports for service is administered  
using the change system-parameters maintenance command.  
b. The call classifier port lost its translation. Testing the call classifier port is  
sufficient to reload its translation. If testing the call classifier port does not  
clear the error, then the call classifier circuit pack containing the defective  
call classifier port should be replaced.  
c. This error indicates the call classifier port is having problems detecting  
system tones (DTMF, etc.) or detecting and generating necessary R2-MFC  
tones. This error should accompany some percentage of failed calls. If this  
error type is persistently logged, then the call classifier circuit pack  
containing the defective call classifier port should be replaced.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLSFY-PT (Call Classifier Port)  
3-368  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following tables when  
inspecting errors in the system. By clearing error codes associated with the Tone  
Detection Verification Test, for example, you may also clear errors generated from  
other tests in the testing sequence.  
Table 3-163. System Technician-Demanded Tests: CLSFY-PT  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
ND  
Tone Detection Verification Test (#42)  
Tone Detection Audit/Update Test (#43)  
X
X
X
X
ND  
1. D = Destructive, ND = Non-destructive  
Tone Detection Verification Test (#42)  
This test checks out each port in both the touch-tone receiver mode and in the  
R2-MFC tone detection/generation mode. During the first half of the test, the  
touch-tone receiver mode is tested. In the second half of the test, each port is put  
into the R2-MFC mode. During this portion of the test, each port’s ability to  
accurately detect and generate all forward and backward MFC tones is verified.  
Table 3-164. TEST #42 Tone Detection Verification Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
none  
ABORT  
The system was not able to allocate all the resources needed for this test  
OR there was an internal system error  
1
ABORT  
ABORT  
The system could not allocate all the resources needed to test the tones.  
1001  
The system was unable to put the Call Classifier port in the appropriate  
mode to test it.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLSFY-PT (Call Classifier Port)  
3-369  
Table 3-164. TEST #42 Tone Detection Verification Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1002  
ABORT  
The system could not allocate time slots for the test connection. This  
situation could occur when the system is heavily loaded. If the system is  
not heavily loaded, then test the TDM-BUS via the test tdm [1|2]  
command. Refer to the TDM-BUS (TDM Bus) Maintenance documentation  
for details.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a Tone-Clock circuit pack for the test  
connection. This situation could occur when the system is heavily loaded  
or if a Tone-Clock circuit pack is not present in the port network when this  
test is executed.  
1. Verify the existence of a Tone-Clock circuit pack in the same port  
network.  
2. If a Tone-Clock circuit pack is missing, install one in the same port  
network.  
3. Allow approximately 1 minute for the Tone-Clock circuit pack  
maintenance to run on the newly inserted Tone-Clock circuit pack.  
4. Retry the command at 1-minute intervals a maximum of 5 times.  
2006  
ABORT  
This abort code indicates that the active Tone-Clock circuit pack might not  
be functioning properly. If there is more than one Tone Detector circuit  
pack in the system, then the problem can be either with the Tone-Clock  
circuit pack or the Tone Detector circuit pack. This could also be caused  
by the companding mode administered for the system not matching that of  
the Tone Detector circuit pack.  
1. Make sure that the companding mode of the system matches that of  
the Tone Detector (TN748 for mu-law systems and TN420 for A-law  
systems).  
2. Test the active Tone-Clock circuit pack in the port network. This test is  
being executed via the test tone-clock qualifier system technician  
command. ("qualifier" is the carrier of the active Tone-Clock circuit  
pack to be tested. Valid qualifiers are: a, b, 1a, 1b, 2a, and 2b.) Refer  
to the ‘‘TONE-BD (Tone-Clock Circuit Pack)’’ Maintenance  
documentation for details.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLSFY-PT (Call Classifier Port)  
3-370  
Table 3-164. TEST #42 Tone Detection Verification Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1-3  
FAIL  
DTMF digits were not detected correctly. This may or may not impact  
reception of R2-MFC calls.  
1. Run the short test sequence via the test port PCSSpp sh r 1  
command.  
2. If the problem persists, the system is still operating properly but  
system capacity will be reduced. In order to restore system  
performance to normal, replace the Call Classifier circuit pack  
containing the defective CLSFY-PT (Call Classifier Port).  
101-122  
FAIL  
Forward or Backward MFC signals were not correctly generated or  
detected. This impacts reception of incoming MFC calls.  
1. Run the short test sequence via the test port PCSSpp sh r 1  
command.  
2. If the problem persists, the system is still operating properly but  
system capacity will be reduced. In order to restore system  
performance to normal, replace the Call Classifier circuit pack  
containing the defective CLSFY-PT (Call Classifier Port).  
PASS  
Tone Detection Verification is successful. The Call Classifier Port  
(CLSFY-PT) is able to detect/generate all necessary tones.  
Tone Detector Audit/Update Test (#43)  
A sanity audit is performed on the CLSFY-PT (Call Classifier Port).  
Table 3-165. Tone Detector Audit/Update Test (#43)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
none  
ABORT  
The system was not able to allocate all the resources needed for this test.  
1. Wait 1 minute, and repeat the command a maximum of 5 times.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CLSFY-PT (Call Classifier Port)  
3-371  
Table 3-165. Tone Detector Audit/Update Test (#43) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Hardware audit failed.  
FAIL  
1. Run the short test sequence via the test port PCSSpp sh r 1  
command.  
2. If the problem persists, the system is still operating properly but  
system capacity will be reduced. In order to restore system  
performance to normal, replace the CLSFY-BD (Call Classifier circuit  
pack) containing the defective CLSFY-PT (Call Classifier Port).  
PASS  
The (CLSFY-PT) Call Classifier Port has passed the sanity inquiry.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-BD (Central Office Trunk Circuit Pack)  
3-372  
CO-BD (Central Office Trunk Circuit  
Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
CO-BD  
CO-BD  
MIN  
WRN  
test board PCSS sh  
test board PCSS sh  
Central Office Trunk Circuit Pack  
Central Office Trunk Circuit Pack  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, C,  
D, or E); and SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02, ..., etc.).  
Refer to XXX-BD (Common Port Circuit Pack) Maintenance documentation for  
circuit pack level errors. See also CO-TRK (CO Trunk) Maintenance  
documentation for related trunk information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-373  
CO-DS1 (DS1 CO Trunk)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test trunk <grp/mbr> l  
test trunk <grp/mbr> l  
test trunk <grp/mbr>  
Full Name of MO  
DS1CO Trunk  
1
CO-DS1  
CO-DS1  
CO-DS1  
MAJOR  
MINOR  
DS1CO Trunk  
WARNING  
DS1CO Trunk  
1. A Major alarm on a trunk indicates that alarms on these trunks are not downgraded  
by the set options command and that at least 75 percent of the trunks in this trunk  
group are alarmed.  
A DS1CO (central office) trunk provides a communications channel between the  
system and a central office switch through either a 1.544 Mbps or a 2.048 Mbps  
[G3iV2-386] DS1 link. A 24 channel DS1 link consists of 24 digital DS1CO trunks.  
A 32 channel DS1 link [G3iV2-386] consists of 30 digital DS1CO trunks. A  
DS1CO trunk can be used for both voice and data communication.  
The DS1CO Trunk Maintenance provides a strategy in the system to maintain a  
CO trunk via a port on the DS1 Interface circuit pack. The TN767B or later and  
TN464C or later DS1 Interface circuit packs support the low level CO trunk  
signaling interfaces, ground-start and loop-start. This strategy covers the in-line  
errors log, initialization tests, periodic tests, system technician-demanded tests,  
and alarm resolution and escalation.  
Three trunk service states are specified in the DS1CO trunk maintenance:  
1. out-of-service: The trunk is in a deactivated state and cannot be used for  
either incoming or outgoing calls.  
2. in-service: The trunk is in an activated state and can be used for both  
incoming and outgoing calls.  
3. disconnect (ready-for-service): The trunk is in an activated state but can  
only be used for an incoming call.  
If the DS1 Interface circuit pack is out-of-service, then all trunks on the DS1  
Interface circuit pack are also in the out-of-service state, and a Warning alarm is  
raised for each trunk.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-374  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-166. DS1 CO Trunk Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test trunk <grp>/<mbr>  
1 (a)  
1 (a)  
15 (b)  
57408  
57487  
Any  
Port Audit and  
Update Test (#36)  
18 (c)  
0
busyout trunk  
<grp>/<mbr>  
WARNING  
WARNING  
OFF  
release trunk  
<grp>/<mbr>  
130 (d)  
257 (e)  
None  
ON  
test trunk <grp>/<mbr>  
2
57392  
57393  
57484  
DS1 CO Dial Tone  
Seizure Test (#314)  
MIN/MAJ  
OFF  
2
513 (f)  
DS1 CO Dial Tone  
Seizure Test (#314)  
MIN/MAJ  
OFF  
769 (g)  
1025  
DS1CO Dial Tone  
Seizure Test (#314)  
WARNING  
MAJ/MIN/  
OFF  
ON  
ON  
ON  
test trunk <grp>/<mbr>  
1281  
1537  
Conference Circuit  
Test (#7)  
test trunk <grp>/<mbr> r  
4
3
WRN  
NPE Crosstalk Test  
(#6)  
MAJ/MIN/  
test trunk <grp>/<mbr> r  
3
3
WRN  
1793 (h)  
2562(i))  
2817(j)  
test board PCSS l  
16665  
52992  
3840 (k)  
Port Audit and  
Update Test (#36)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
2. This alarm will only be raised when the System-Parameter Country form has the Base Tone Generator  
field set to 4 (Italy). This alarm will be a MINOR alarm unless 75% or more trunks in this trunk group are  
out of service, then the alarm will be upgraded to a MAJOR alarm.  
3. Minor alarms on this maintenance object (MO) may be downgraded to Warning alarms based on the  
values used in the set options command. If the Minor alarm is not downgraded by the set options  
values, the Minor alarm is upgraded to a Major alarm if 75 percent of the trunks in this group are  
alarmed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-375  
Notes:  
a. Error Type 1—Aux Data 57408—No tip ground is detected on an outgoing  
call.  
Aux Data 57487—PBX could not get "loop close" signal (TN767).  
The DS1 Interface circuit pack detected a hardware fault. These errors  
cause the Dial Tone Test (#314) to run and are only considered a problem  
if the Dial Tone Test fails (in which case Error Type 1025 also shows up). In  
this case, the trunk may be put in ready-for-service state (shown as  
"disconnected" by status command), which allows only incoming calls.  
Run the Dial Tone Test (#314) and follow its outlined procedures.  
b. Error Type 15—This is a software audit error that does not indicate any  
hardware malfunction. Run Short Test Sequence and investigate  
associated errors (if any).  
c. Error Type 18—System Technician has busied-out the trunk to the  
out-of-service state. No calls can be made on this trunk except the Facility  
Access Test Call.  
d. Error Type 130—This error type indicates that the circuit pack has been  
removed or has been insane for more than 11 minutes. To clear the error,  
reinsert or replace the circuit pack.  
e. Error Type 257—The DS1 Interface circuit pack detects a hardware fault.  
The Aux Data field contains the following error type: 57392—no external  
release on PBX disconnect [E030]. Escalate the problem.  
f. Error Type 513—The DS1 Interface circuit pack detects a hardware fault.  
The Aux Data field contains the following error type: 57393—belated  
external release on PBX disconnect [E031]. Escalate the problem.  
g. Error Type 769—The DS1 Interface circuit pack detects a hardware fault.  
The Aux Data field contains the following error type:—57484, fault is  
detected on tip/ring [E08C]. Escalate the error.  
h. Error Type 1793—DS1 Interface circuit pack is out-of-service. Look for  
DS1-BD errors in the Hardware Error Log. Refer to the DS1-BD (DS1 Trunk  
Circuit Pack) Maintenance documentation for details.  
i. Error Type 2562—Retry Failure error. This error is logged only. It is not a  
hardware failure and hence does not start any testing or generate any  
alarms. This error comes from call processing and is generated when a  
second attempt (retry) to seize an outgoing trunk fails.  
j. Error Type 2817—Glare error. This error is logged only. It is not a hardware  
failure and hence does not start any testing or generate any alarms. This  
error is the result of a simultaneous seizure of a two-way trunk from both  
the near-end and the far-end. Attempt to place the call again. If the error  
persists, execute the Dial Tone Seizure Test (#314) and follow those  
procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-376  
k. Error Type 3840—Port Audit and Update Test (#36) failed due to an  
internal system error. Enter the status trunk command to verify the status  
of the trunk. If the trunk is out-of-service, then enter the release trunk  
command to put it back into in-service. Retry the test command. If the test  
continues to abort, then escalate the problem.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order they are presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the NPE  
Crosstalk Test, for example, you may also clear errors generated from other tests  
in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
X
X
X
Conference Circuit Test (#7)  
ND  
DS1CO Trunk Seizure Test (#314)  
Port Audit and Update Test (#36)  
X
X
ND  
ND  
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
One or more Network Processing Elements (NPEs) resides on each circuit pack  
with a TDM Bus interface. The NPE controls port connectivity and gain, and  
provides conferencing functions on a per-port basis. The NPE Crosstalk Test  
verifies that this port’s NPE channel talks on the selected time slot and never  
crosses over to time slots reserved for other connections. If the NPE is not  
working correctly, one-way and noisy connections may be observed. This test is  
usually only part of a port’s Long Test Sequence and takes about 20 to 30  
seconds to complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-377  
Table 3-167. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at one-minute intervals a maximum of five times.  
1000  
System resources required to run this test were not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 1025 (see the error log table for a description of  
this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at one-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to the TDM-BUS (TDM Bus) Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at one-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some tone  
detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
(TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a user for a valid call. Use the display port  
PCSSpp command to determine the trunk group/member number of the  
port. Use the status trunk command to determine the service state of the  
port. If the service state indicates that the port is in use, then the port is  
unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-378  
Table 3-167. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1020  
ABORT  
The test did not run due to a previously existing error on the specific port or  
a more general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit  
pack and attempt to diagnose the already existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2053  
ABORT  
At least one of the following errors was found on the DS1 circuit pack: loss  
of signal (1281), blue alarm (1793), red alarm (2049), yellow alarm (2305),  
or hyperactivity (1537).  
1. Look for the above error types in the Hardware Error Log and follow the  
procedures given in the appropriate DS1-BD or UDS1-BD  
maintenance documentation for the listed error types.  
FAIL  
The NPE of the tested port was found to be transmitting in error. This  
causes noisy and unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated using other port tests and examining  
station, trunk, or external wiring.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-379  
Table 3-167. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, an insane board is inserted, or the board is hyperactive (see note  
below).  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
NOTE:  
Hyperactivity causes some special problems with the sequence  
suggested above. If the ports are translated after issuing the list  
config command but the Vintagefield reports that there is no  
board (when there really is a board), then the busyout board and  
the release busy board commands will not work (even though the  
reset board command will work). The software puts the hyperactive  
board back in service after the hyperactivityclears.  
Conference Circuit Test (#7)  
One or more Network Processing Elements (NPEs) reside on each circuit pack  
with a TDM Bus interface. The NPE controls port connectivity and gain, and  
provides conferencing functions on a per-port basis. The Conference Circuit Test  
verifies that the NPE channel for the port being tested can correctly perform the  
conferencing function. The NPE is instructed to listen to several different tones  
and conference the tones together. The resulting signal is then measured by a  
tone detector port. If the level of the tone is within a certain range, the test  
passes.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-380  
Table 3-168. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
The test was aborted. System resources required to run this test were not  
available. The port may be busy with a valid call. Use the display port  
PCSSpp command to determine the trunk group/member number of the  
port. Use the status trunk command to determine the service state of the  
port. If the service state indicates that the port is in use, then the port is  
unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 1025 (see the error log table for a description of  
this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1002  
1003  
ABORT  
ABORT  
The test was aborted. The system could not allocate time slots for the test.  
The system may be under heavy traffic conditions, or it may have time slots  
out of service due to TDM-BUS errors. Refer to the TDM-BUS (TDM bus)  
maintenance documentation to diagnose any active TDM-BUS errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic  
and the port status is idle, retry the command at 1-minute intervals for  
a maximum of 5 times.  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present or some of the tone  
detectors may be out of service. Issue the list measurements  
tone-receiver command to display basic information about the system’s  
tone receivers.  
1. Look for TTR-LEV errors in the error log. If present, refer to the TTR-LEV  
maintenance documentation.  
2. Look for TONE-PT errors in the error log. If present, refer to the  
TONE-PT maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals for a  
maximum of 5 times.  
1004  
ABORT  
The port has been seized by a user for a valid call. Use the status station  
or status trunk command to determine when the port is available for  
testing.  
1. Retry the command at one-minute intervals a maximum of five times.  
2. If the test continues to abort, and the port is not in use, escalate the  
problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-381  
Table 3-168. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1018  
ABORT  
The test was disabled via translation. You may want to determine why the  
test has been disabled before you enable it.  
1. Verify that the Maintenance Testfield on the Trunk Administration  
screen is set to n. To enable the test, change the trunk administration  
and enter y into the Maintenance Testfield.  
2. Repeat the test.  
1020  
ABORT  
The test did not run due to a previously existing error on the specific port or  
a more general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit  
pack and attempt to diagnose the previously existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2053  
ABORT  
At least one of the following errors was found on the DS1 circuit pack: loss  
of signal (1281), blue alarm (1793), red alarm (2049), yellow alarm (2305),  
or hyperactivity (1537).  
1. Look for the above error types in the Hardware Error Log and follow the  
procedures given in the appropriate DS1-BD or UDS1-BD  
maintenance documentation for the listed error types.  
Any  
FAIL  
1. Enter the list configuration board PCSS command. If the circuit  
pack is a TN767B vintage 8 or 9, replace the circuit pack with a  
TN767C V3 or later.The error log may have error type 1281 entries.  
2. Test all administered trunks on the board. If one fails, this could be an  
off-board problem (such as an incoming seizure or an off-hook port  
seizure during the test). Retest the board.  
3. If several ports fail, check the error log for TONE-BD or TONE-PT  
errors. If there are such errors, take the appropriate action. When the  
TONE errors have cleared, rerun the test.  
4. If the retry passes and troubles have been reported, coordinate  
isolation with the CO. Make sure that the switch, the CO, and any  
NTCE equipment (the CSU’s) have the correct administration.  
5. Replace the circuit pack.  
NOTE:  
If the conference circuit test fails for all ports on a circuit pack, a -5  
volt power problem is indicated.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-382  
Table 3-168. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The port can correctly conference multiple connections. User-reported  
troubles on this port should be investigated by using other port tests and  
by examining station, trunk, or external wiring.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
This result could be due to incorrect translations, no board is inserted, an  
incorrect board is inserted, an insane board is inserted, or the board is  
hyperactive (see note below).  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port. If  
this is not the case, dispatch to check to ensure that there is a valid board  
inserted.  
NOTE:  
Hyperactivity causes some special problems with the sequence  
suggested above.If the ports are translated after issuing the list  
config command but the Vintagefield reports that there is no  
board (when there really is a board), then the busyout board and  
the release busy board commands will not work (even though the  
reset board command will work). The software puts the hyperactive  
board back in service after the hyperactivity clears.  
Port Audit and Update Test (#36)  
This test sends port level translation data from switch processor to the DS1  
Interface circuit pack to assure that the trunk’s translation is correct. Translation  
updates include the following data: trunk type (in/out), dial type, timing  
parameters, and signaling bits enabled. The port audit operation verifies the  
consistency of the current state of trunk kept in the DS1 Interface circuit pack  
and in the switch software.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-383  
Table 3-169. TEST #36 Port Audit and Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
The test was aborted because system resources required to run this test  
were not available. The port may be busy with a valid call. Issue the  
display port PCSSpp command to determine the trunk group/member  
number of the port. Use the status trunk command to determine the  
service state of the port. If the service state indicates that the port is in use,  
then the port is unavailable for certain tests. You must wait until the port is  
idle before retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 1025 (see the error log table for a descriptionof  
this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
2000  
2100  
ABORT  
Response to the test request was not received within the allowable time  
period.  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
Test failed due to internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
Trunk translation has been updated successfully. The current trunk states  
kept in the DS1 Interface circuit pack and switch software are consistent. If  
the trunk is busied out, the test does not run, but returns to PASS. To verify  
that the trunk is in-service:  
1. Enter status trunk command to verify that the trunk is in-service. If the  
trunk is in-service, no further action is necessary. If the trunk is  
out-of-service, continue to Step 2.  
2. Enter release-trunk command to put trunk back into in-service.  
3. Retry the test command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-384  
Table 3-169. TEST #36 Port Audit and Update Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This result  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, an insane board is inserted, or the board is hyperactive  
(see note below).  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port. If  
this is not the case, dispatch to check to ensure that there is a valid board  
inserted.  
Hyperactivity causes some special problems with the sequence suggested  
above. If the ports are translated after issuing the list config command but  
the Vintagefield reports that there is no board (when there really is a  
board), then the busyout board and the release busy board commands  
will not work (even though the reset board command will work). The  
software puts the hyperactive board back in service after the hyperactivity  
clears.  
DS1 CO Dial Tone Seizure Test (#314)  
DS1CO Dial Tone Seizure Test checks the trunk’s signaling capability provided  
by the DS1 Interface circuit pack. The maintenance software initiates the test by  
sending a "seizure" message to the DS1 Interface circuit pack and expects an  
"active" reply from the DS1 interface circuit pack. If the "active" message is  
received, then the test passes. If no message is received and the timer expires,  
the test is aborted. If the DS1 Interface circuit pack sends a "reorder" message  
back to maintenance software, then the test fails.  
The test CANNOT be run on a trunk if one of the following cases is true:  
a. The trunk direction is administered as an incoming only trunk.  
b. The trunk has been seized by a normal trunk call.  
c. The trunk is administered with maintenance test disabled.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-385  
Table 3-170. TEST #314 DS1CO Dial Tone Seizure Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
The test was aborted because system resources required to run this test  
were not available. The port may be busy with a valid call. Use the display  
port PCSSpp command to determine the trunk group/member number of  
the port. Use the status trunk command to determine the service state of  
the port. If the service state indicates that the port is in use, then the port is  
unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 1025 (see the error log table for a description of  
this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1004  
ABORT  
The test was aborted because the port was seized by a user for a valid call.  
Use the display port PCSSpp command to determine the trunk  
group/member number of the port. Use the status trunk command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. You must wait  
until the port is idle before retesting.  
1. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1005  
ABORT  
Test failed due to incompatible configuration administered in trunk group  
form.  
1. Verify the following fields on the trunk group administration screen: Is  
trunk direction incoming only? Is trunk the port 24 of the DS1 Interface  
circuit pack while common control channel signaling is specified? Is  
trunk group type the automatic CO (for example, FX)?  
2. If the trunk has been administered using the above information, then  
this test should abort.  
1018  
ABORT  
The test is disabled via translation. You may want to determine why the test  
has been disabled before you enable it.  
1. Verify that the Maintenance Testfield on the Trunk Group form is  
set to n. To enable the test, issue the change trunk-group x command  
(x equals the number of the trunk group to be tested). Then, change  
the entry in the Maintenance Testfield on the form to y.  
2. Repeat the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-386  
Table 3-170. TEST #314 DS1CO Dial Tone Seizure Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1020  
ABORT  
The DS1 Interface circuit pack is out-of-service.  
1. Look for DS1-BD errors in the Hardware Error Log. If present, refer to  
DS1-BD (DS1 Trunk Circuit Pack) Maintenance documentation.  
2. Retry the command.  
1040  
ABORT  
The test was aborted because this port may be an access endpoint.  
1. Verify that this port is an access endpoint by issuing the display port  
command.  
2. If the port has been administered as an access endpoint, then this is a  
normal abort.  
2000  
2012  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
The test was aborted due to an internal system error.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2100  
ABORT  
FAIL  
The trunk cannot be seized for an outgoing call. This could cause in-line  
failures to be reported against the trunk (no answer would report error type  
257 with auxiliary data 57487 in the error log).  
1. Verify that the Trunk Type field on the trunk administration screen form  
matches the trunk type administered on far end switch.  
2. Look for DS1-BD/UDS1-BD errors in Hardware Error Log. If present,  
refer to the appropriate DS1-BD/UDS1-BD (DS1/UDS1 Trunk Circuit  
Pack) Maintenance documentation.  
3. Retry the test at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-387  
Table 3-170. TEST #314 DS1CO Dial Tone Seizure Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
FAIL  
Response to the seizure message was not received within the allowable  
time period.  
1. Enter the list configuration board PCSS command. If the circuit pack  
is a TN767B vintage 8 or 9, a failure of test 314 causes a subsequent  
failure of test 7 due to a firmware bug. Eventually, the board and all of  
its ports will be taken out of service and extraneous on-board alarms  
will be generated. Replace the circuit pack with a TN767C V3 or later.  
2. Verify that the ’Trunk Type’ field on the ’Trunk Administration’ screen  
matches the trunk type administered on far-end switch.  
3. Look for DS1-BD or UDS1-BD errors in the hardware error log. If  
present, refer to the DS1-BD (DS1 trunk circuit pack) maintenance  
documentation or to the UDS1-BD (UDS1 trunk circuit pack)  
maintenance documentation.  
4. Retry the test at 1-minute intervals for a maximum of 5 times.  
2053  
FAIL  
At least one of the following errors was found on the DS1 circuit pack: loss  
of signal (1281), blue alarm (1793), red alarm (2049), yellow alarm (2305),  
or hyperactivity (1537).  
1. Look for these error types in the Hardware Error Log and then follow  
the procedures given in the maintenance documentation that is  
appropriate for the error type that was found.  
PASS  
The trunk can be seized for an outgoing call.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CO-DS1 (DS1 CO Trunk)  
3-388  
Table 3-170. TEST #314 DS1CO Dial Tone Seizure Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, an insane board is inserted, or the board is hyperactive (see Note  
below).  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
NOTE:  
Hyperactivity causes some special problems with the sequence  
suggested above. If the ports are translated after issuing the list  
config command but the ’Vintage’ field reports that there is no board  
(when there really is a board), then the busyout board and the  
release busy board commands will not work (even though the reset  
board command will work). The software will put the hyperactive  
board back in service after the hyperactivity clears.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-389  
CO-TRK (CO Trunk)  
MO Name (in  
Alarm Log)  
Initial Command to  
1
Alarm Level  
Run  
Full Name of MO  
CO Trunk  
2
CO-TRK  
MAJOR  
test port PCSSpp l  
test port PCSSpp l  
test port PCSSpp l  
CO-TRK  
MINOR  
CO Trunk  
CO-TRK  
WARNING  
CO Trunk  
1. Where P is the port network number (1 for PPN); c is the carrier designation (for  
example, A, B, C, D, or E); and SS is the address of the slot in the carrier where the  
circuit pack is located (for example, 01, 02, ...etc.).  
2. A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded  
by the set options command and that at least 75 percent of the trunks in this trunk  
group are alarmed.  
NOTE:  
If ATMS testing is enabled, check the error log for ATMS Errors #3840 and  
#3841. If the error log indicates that measurements exceeded acceptable  
thresholds, and if no other trouble is found with the test trunk command,  
run the ATMS test call with the test analog-testcall port UUCCSSpp full  
command.  
Central Office (CO) trunks are 2-wire analog lines to the CO which support both  
incoming and outgoing calls. A CO trunk circuit pack provides an interface  
between the 2-wire analog line from the CO and the system’s (4-wire) Time  
Division Multiplex (TDM) Bus. The CO Trunk circuit packs include:  
■
TN747B (United States), 8 port loop start or ground start CO, foreign  
exchange (FX), or Wide Area Telecommunications (WATS) trunks.  
■
■
■
■
■
TN438B (Australia), 8 port loop start.  
TN447 (United Kingdom), 8 port ground start.  
TN465B/C (multiple countries), 8 port loop start.  
TN2138 (Italy), 8 port loop start.  
TN2147C (multiple countries), 8 port loop start and United Kingdom Earth  
Calling or Loop Calling Guarded Clearing.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-390  
Loop Start and UK Loop Calling Guarded  
Clearing Operation  
Idle State - Tip _ ground, Ring = CO Battery  
a. Outgoing Call  
1. PBX Off-Hook (Seize Message): Closes the Tip-Ring Loop  
a. CO Response: DC loop current + Dial tone  
2. PBX On-Hook (Drop Message): Open Tip-Ring loop, no loop  
current  
a. CO Response: CO goes to idle state (see Note)  
b. Incoming Call  
1. CO Applies Ringing Voltage  
a. PBX Response: Detect ringing current  
2. PBX Off-Hook (Answer Message): Close loop  
a. CO Response: Trip ringing, provide loop current  
3. PBX On-Hook (Drop Message): Open Tip-Ring loop, no loop  
current  
a. CO Response: CO goes to idle state (see Note)  
NOTE:  
Except for the Netherlands Loop Start and UK Loop Calling Guarded  
Clearing trunks, CO does not normally provide an On-Hook (Disconnect)  
signal.  
Ground Start and UK Earth Calling Operation  
Idle state - Tip _ open, Ring = CO Battery  
a. Outgoing Call  
1. PBX Off-Hook(Seize Message): Places ground on Ring  
a. CO Response: Places ground on Tip  
b. PBX Response: close the loop  
c. CO Response: provide loop current  
d. PBX response: dial out digits  
2. PBX On-Hook first (Drop Message): Open the Tip-Ring Loop, no  
loop current  
a. CO Response: Open circuit on Tip  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-391  
3. CO On-Hook first (Disconnect): Open circuit on Tip, no loop  
current.  
a. PBX Response: Open Tip-Ring loop  
b. B. Incoming Call  
1. CO Off-Hook (Seizure): CO applies ground on Tip, CO applies  
ringing voltage  
a. PBX Response: Detect ringing, ring destination  
2. PBX Off-Hook (Answer Message): Close loop  
a. CO Response: Trip ringing, provide loop current  
3. PBX On-Hook first (Drop Message): Open the Tip-Ring Loop, no  
loop current  
a. CO Response: Open circuit on Tip  
4. CO On-Hook first (Disconnect): Open circuit on Tip, no loop current  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-171. CO Trunk Error Log Entries  
Aux  
Alarm  
Level  
On/Off  
Board  
Error Type  
Data  
Associated Test  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
test port PCSSpp sh r 1  
1 (a)  
57347  
any  
None  
15 (b)  
Port Audit Update  
Test (#36)  
18  
0
busyout trunk  
<grp>/<mbr>  
WARNING  
WARNING  
OFF  
ON  
release trunk  
<grp>/<mbr>  
130(c)  
257 (a)  
513 (a)  
None  
None  
None  
test trunk <grp>/<mbr>  
50176  
57364  
MAJ/MIN/  
ON  
2
WRN  
769 (a)  
57392  
Any  
None  
MAJ/MIN/  
WRN  
OFF  
OFF  
ON  
2
1025 (e)  
1281 (e)  
Demand Diagnostic  
Test (#3)  
MAJ/MIN/  
test port PCSS sh r 2  
test port PCSS sh r 3  
2
WRN  
Any  
Demand Diagnostic  
Test (#3)  
MAJ/MIN/  
2
WRN  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-392  
Table 3-171. CO Trunk Error Log Entries — Continued  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Error Type  
Associated Test  
Test to Clear Value  
1537  
Dial Tone Test (#0)  
MAJ/MIN/  
WRN  
OFF  
test port PCSS l r 2  
2
1793  
2049  
Loop Around and  
Conference Test  
(#33)  
MAJ/MIN/  
WRN  
ON  
test port PCSS l r 3  
test port PCSS l r 3  
2
NPE Cross Talk Test  
(#6)  
MAJ/MIN/  
ON  
2
WRN  
2561 (d)  
2817 (a)  
2817 (a)  
2817 (d)  
57345  
57360  
57393  
57484  
None  
None  
None  
Dial Tone Test (#0)  
MAJ/MIN/  
WRN  
OFF  
OFF  
test port PCSS l r 1  
test port PCSS l r 1  
2
3073 (d)  
3329 (d)  
3329 (d)  
57376  
57408  
57484  
None  
None  
Dial Tone Test (#0)  
MAJ/MIN/  
2
WRN  
3585 (d)  
3840 (f)  
57424  
8000  
None  
Analog Transmission  
(#844-848)  
OFF  
OFF  
3841 (f)  
Analog Transmission  
(#844-848)  
MINOR  
test analog testcall PCSS  
pp r 2  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
2. Minor alarms on this MO may be downgraded to warning alarms based on the values used in the set  
options command. If the Minor alarm is not downgraded by the set-options values, the Minor alarm is  
upgraded to a Major alarm if 75 percent of the trunks in this trunk group are alarmed.  
Notes:  
a. These are in-line errors that have no specific test associated with them.  
Refer to Table 10-93 for an explanation and appropriate action.  
b. This is a software audit error that does not indicate any hardware  
malfunction. Run the Short Test Sequence and investigate associated  
errors (if any).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-393  
c. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
d. Aux data 57345 -- Single polarity ringing current  
Aux data 57376 -- No loop current on incoming call  
Aux data 57408 -- No tip ground detected on outgoing call  
Aux data 57424 -- No loop current on outgoing call  
Aux data 57484 -- No dial tone on outgoing call  
These errors cause the Dial Tone Test (#0) to run and are only considered  
a problem if the Dial Tone Test fails (in which case Error Type 1537 also  
shows up). In this case, the trunk may be put in "Ready-for-Service" state  
(shown as "disconnected" by status command), which allows only  
incoming calls. Run the Dial Tone Test (#0) and follow its outlined  
procedures.  
If error count associated with this error type is very high (that is, 255) and if  
Alarm Status on the Hardware Error Report is "n" (not alarmed), then the  
existence of this error type indicates that, despite the fact that many in-line  
error messages have been received, all Call Seizure Tests have passed.  
Problems at the CO may cause this condition rather than problems with  
the PBX.  
e. These errors are logged for all versions of the CO-TRK/CO-BD. However,  
no MINOR alarms are generated for Central Office Trunks [TN747B] with  
vintages V8 or greater. Any failures received by this test are still logged as  
Error type 1025/1281 as additional information for the system technician  
person.  
The system technician person should check for the use of MFT/Range  
extenders. If there are extenders present, and there are no other  
complaints or maintenance errors against this trunk, then there is a good  
chance that Test #3 failed due to excessive loop current and may be  
ignored.  
f. Test calls made by the Automatic Transmission Measurement System  
(ATMS) returned measurements that were outside the acceptable limits.  
Use the list testcall detail command to examine specific transmission  
parameters that are out of spec, and investigate the trunk for that kind of  
noise. If the noise is acceptable, the limits administered on the "change  
trunk" screen should be changed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-394  
Table 3-172. CO Trunk Errors with NO Tests  
Error  
Type  
Aux  
Data  
Description and System Action  
System Technician Action  
See Note 1 at end of table.  
1
57347  
Port error. Ringing without ground. This error  
is detected on an incoming call on a  
ground-start CO trunk. The CO trunk circuit  
pack has not detected a Tip ground before  
ringing current is detected. This may  
indicate that the ground detector is not  
working. However, the call is accepted.  
257  
50176  
Battery reversal detected. This is usually  
caused by the CO (often seen with  
step-by-step and cross-bar offices in  
connection with outgoing calls). This is  
detected if the direction of the loop current  
changes from normal to reverse for at least  
40 msec. Could occur if the trunk was just  
installed and for some reason the Tip and  
Ring wires were reversed at the PBX. If  
battery reversals occur during dialing,  
wrong numbers may result. The CO should  
be asked to remove the battery reversal  
option.  
Refer problem to CO.  
513  
57364  
Ground detector stuck active. After several  
occurrences, an on-board minor alarm is  
generated.  
Run short test. If test aborts with  
Error Code 1000, disconnect Tip  
and Ring and repeat short test. If  
test still aborts, replace circuit  
pack. If test passes, refer  
problem to CO. If any other error  
code is received, pursue that  
problem.  
769  
57392  
CO not releasing after call is dropped from  
PBX end (off-board alarm after several  
occurrences), or the loop is not open after a  
disconnect (on-board alarm after several  
occurrences).  
For off-board alarm, refer  
problem to CO. For on-board  
alarm, the circuit pack has an  
on-board problem (for example,  
stuck relay) and should be  
replaced.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-395  
Table 3-172. CO Trunk Errors with NO Tests — Continued  
Error  
Type  
Aux  
Data  
Description and System Action  
System Technician Action  
2561  
57345  
Single polarity ringing current. This error  
results from abnormal ringing current, but  
does not prevent the incoming call from  
being accepted. One cause could be that  
the reverse current detector associated with  
the port is failing. (Will not be detected by  
any tests.) Another cause could be that  
normal current is not detected. In this case,  
neither incoming nor outgoing calls can be  
completed, and the dial tone test also fails.  
The last cause could be that certain types of  
noise are present on the CO line during the  
silent period of ringing.  
Check for other errors first and  
then see Note 4 at end of table.  
2817  
57360  
Ground but no ringing. This error occurs on  
an incoming call on a ground-start trunk. If  
ringing is not detected within 5 seconds of  
the Tip being grounded, the call is still  
accepted. If the CO is of the No. 5ESS.  
switch type, ringing delays of more than 5  
seconds during heavy traffic are fairly  
common.  
Check for other errors.  
Check for other errors.  
Check for other errors.  
2817  
57393  
On the TN465, the loop is opening too slowly  
after a disconnect. This error indicates an  
on-board problem, although the trunk may  
be functional. On the TN2138, CO released  
the trunk at least 4 minutes after the PBX  
dropped the call. This error code is log-only  
and causes no other testing to occur. No  
alarm is generated.  
3073  
3329  
57376  
57408  
No loop current on incoming call. The  
incoming destination has already answered  
and no loop current has been detected. If  
this is a hard fault, the dial tone test and all  
outgoing calls should also fail.  
Trunk error. No Tip ground detected on  
outgoing call. This error occurs when an  
attempt is made to seize a ground-start CO  
trunk for an outgoing call and Tip ground is  
not detected or the caller hangs up before  
Tip ground is detected.  
See Notes 1 and 2 at end of  
table.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-396  
Table 3-172. CO Trunk Errors with NO Tests — Continued  
Error  
Type  
Aux  
Data  
Description and System Action  
System Technician Action  
See Note 3 at end of table.  
3585  
57424  
No loop current on outgoing call. This error  
occurs on attempt to seize a loop or  
ground-start trunk for an outgoing call. An  
error occurs if loop current is not detected or  
the caller hangs up before it is detected.  
Notes for Table 3-172:  
1. At the administration terminal, busyout the affected port, and run a Long  
Test Sequence. Observe the test results. If any tests fail, refer to the  
description of the tests and the associated error codes. Release the port.  
If users continue to report troubles, check for other errors and make test  
calls to determine whether the problem should be escalated or referred to  
the CO.  
2. At the administration terminal, busyout the affected port, and run a Long  
Test Sequence. If Dial Tone Test #0 passes, ignore this error. Release the  
port.  
3. At the administration terminal, busyout the affected port, and run a Long  
Test Sequence. If CO Demand Diagnostic Test #3 passes and this error  
keeps occurring, refer problems to CO. Release the port.  
4. If the error count associated with this error type is very high (that is, 255)  
and all tests pass, then either the reverse current detector is defective or  
the CO line is noisy. If the CO line is suspected, Tip and Ring observations  
should be made. If the line is determined to be noisy, the problem should  
be referred to the CO. If the reverse current detector is defective, ignore  
this error.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order they are presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the NPE  
Crosstalk Test, for example, you may also clear errors generated from other tests  
in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-397  
For example, you may also clear errors generated from other tests in the testing  
sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
X
X
X
Dial Tone Test (#0)  
ND  
CO Demand Diagnostic Test (#3) (a)  
Loop Around and Conference Test (#33)  
X
ND  
ND  
Audit Update Test (#36)  
X
X
ND  
Analog Transmission Test (#844-848) (b)  
(c)  
(c)  
1. D = Destructive; ND = Nondestructive  
Notes:  
a. A demand test of Diagnostic Test (#3) always returns a PASS indication for  
CO-TRK/CO-BD [TN747B] version 8 or greater. However, any errors  
produced as a result of this test are logged and produce no alarms.  
If errors logged by Test #3 are the only complaints against this trunk, then  
the system technician person should check if MFT/Range Extenders are  
being used. If extenders are present, then there is a good chance that  
there is excessive loop current, which causes Test #3 to log errors.  
However, all else being normal, these errors should not affect the  
customer.  
b. Refer to TIE-TRK (Tie Trunk) Maintenance documentation for a description  
of this test.  
c. ATMS test are not part of either sequence. They are run either on demand  
with the test analog-testcall command or via the ATMS schedule.  
Dial Tone Test (#0)  
This test attempts to seize a port and checks for the return of a dial tone.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-398  
Table 3-173. TEST #0 Dial Tone Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the command display port PCSSpp to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
System resources required to run this test were not available. This could  
be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM Bus) Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1004  
ABORT  
The port was seized by a user for a valid call. Use the display port  
PCSSpp command to determine the trunk group/member number of the  
port. Use the status trunk command to determine the service state of the  
port. If the service state indicates that the port is in use, then the port is  
unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1005  
1018  
ABORT  
ABORT  
Trunk has been administered as incoming-only; dial tone can only be  
obtained on outgoing trunks. This is a normal condition.  
Test has been disabled via administration.  
1. Verify that the Maintenance Tests?field on the Trunk Group  
Form is set to n. To enable the test, issue the change trunk-group x  
command where "x"equals the number of the trunk group to be tested.  
Then change the entry in the Maintenance Tests?field on the  
form to y.  
2000  
ABORT  
Response to the test was not received within the allowable time period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-399  
Table 3-173. TEST #0 Dial Tone Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
Trunk was seized, but dial tone could not be detected.  
1. Test all administered outgoing ports on the board. Failure of 1  
indicates a problem toward the CO.  
2. If all fail, see note below.  
3. Check for errors on the TONE-BD or TONE-PT. Clear any errors found,  
and repeat the test.  
4. If the error has still not cleared, refer the problem to the CO.  
5. If no service problems exist on the port, continue to use the port until  
the circuit pack can be replaced (as a last resort). Perform a trunk test  
call to see if the trunk is operable.  
NOTE:  
If the dial tone test fails for all ports on a circuit pack, a -5 volt power  
problem is indicated.  
2002  
FAIL  
Seizure portion of test failed due to hardware problem. Fault is usually  
caused by a disconnected trunk.  
1. If the CO Demand Diagnostic Test (#3) also failed, display the  
Hardware Error Log. If the CO Demand Diagnostic Test failed because  
it could not detect ground (indicated by Error Type 1281 in the  
Hardware Error Log) AND Error Type 3329 or 3585 appears in the  
Hardware Error Log (with the same last occurred time as Error Type  
1281 and 1537), replace the circuit pack.  
2. Check trunk wiring to ensure good connection; repeat test if wiring  
correction made.  
3. Locate another identical CO trunk and swap its wiring with one under  
test. Repeat test on both trunks and determine if problem follows trunk  
or remains at original port. If problem follows trunk, refer problem to  
CO. If problem remains at port, replace circuit pack and repeat test.  
4. If replacing circuit pack does not clear failure, escalate the problem.  
Detected tone was not pure dial tone. No action is required.  
1009  
PASS  
PASS  
Trunk was seized, and dial tone was detected. User-reported troubles on  
this port should be investigated by using other port tests and by examining  
trunk or external wiring.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-400  
Table 3-173. TEST #0 Dial Tone Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
CO Demand Diagnostic Test (#3)  
For ground start trunks only, port circuit pack relays are operated and checks are  
made to see if the port can detect and apply ground on the Tip lead. This test  
also verifies that there is no external ground on the Ring lead. In the absence of  
other failures, the circuit pack should be replaced only if this test fails with the CO  
line disconnected.  
For the TN2147 World Class Central Office circuit pack, this test also checks the  
on-board programmable transmission circuitry that allows the circuit pack to  
support the transmission characteristics of several countries.  
Table 3-174. TEST #3 CO Demand Diagnostic Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Could not allocate system resources to run this test.  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-401  
Table 3-174. TEST #3 CO Demand Diagnostic Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1004  
ABORT  
The port was seized by a user for a valid call. Use the display port  
PCSSpp command to determine the trunk group/member number of the  
port. Use the status trunk command to determine the service state of the  
port. If the service state indicates that the port is in use, then the port is  
unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. If the port status is idle, retry the command at 1-minute intervals a  
maximum of 5 times.  
1005  
1018  
ABORT  
ABORT  
Test inapplicable to present configuration. This is a normal condition.  
Test has been disabled via administration.  
1. Verify that the Maintenance Tests?field on the Trunk Group  
Form is set to n. To enable the test, issue the change trunk-group x  
command where "x"equals the number of the trunk group to be tested.  
Then change the entry in the Maintenance Tests?field on the  
form to y.  
2000  
ABORT  
Response to the request was not received within the allowable time period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-402  
Table 3-174. TEST #3 CO Demand Diagnostic Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
Failure to detect ground or faulty ground detected on Ring lead. Display  
the hardware errors for this trunk, to determine if the fault was on- or-off  
board. Look for Error Type 1025 or 1281 (if both appear in the Hardware  
Error Log, pick the most recent error). Error Type 1025 indicates a faulty  
ground detected on Ring lead (an off-board fault) and Error Type 1281  
indicates failure to detect (internally generated) ground (an on-board  
fault). Faulty ground detected on Ring lead (Error Type 1025):  
NOTE:  
On TN747B vintage 8 and greater circuit packs, an incoming  
seizure during this test may cause it to fail with an off-board fault.  
1. Repeat test. If test passes, ignore the original failure. If test aborts,  
follow the recommended procedures.  
2. Repeat test with CO line removed.  
3. If test fails, replace the circuit pack.  
4. If test passes, refer problem to CO.  
Failure to detect ground (Error Type 1281):  
1. Run the long test sequence. If the CO Demand Diagnostic Test fails,  
the Dial Tone Test (#0) fails with Error Code 2002, AND Error Type  
3329 or 3585 appears in the Hardware Error Log (with the same last  
occurred time as Error Type 1281 and 1537), replace the circuit pack.  
2. Repeat test with CO line removed.  
3. If test fails, replace the circuit pack.  
4. If test passes, the CO may be drawing too much current. Refer  
problem to CO.  
57481  
FAIL  
On-board test of programmable transmission circuitry failed.  
1. Replace the circuit pack.  
PASS  
This test verifies that the port is able to apply ground for outgoing calls and  
detect ground for incoming calls; however, it does not provide information  
on whether a CO line is actually connected. User-reported troubles on this  
port should be investigated by using other port tests and by examining  
trunk or external wiring.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-403  
Table 3-174. TEST #3 CO Demand Diagnostic Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
NPE Crosstalk Test (#6)  
One or more Network Processing Elements (NPEs) reside on each circuit pack  
with a TDM Bus interface. The NPE controls port connectivity and gain, and  
provides conferencing functions on a per port basis. The NPE Crosstalk Test  
verifies that this port’s NPE channel talks on the selected time slot and never  
crosses over to time slots reserved for other connections. If the NPE is not  
working correctly, one way and noisy connections may be observed. This test is  
usually only part of a port’s long test sequence and takes approximately 20 to 30  
seconds to complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-404  
Table 3-175. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
The port was seized by a user for a valid call. Use the display port  
PCSSpp command to determine the trunk group/member number of the  
port. Use the status trunk command to determine the service state of the  
port. If the service state indicates that the port is in use, then the port is  
unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 1025 (see the Error Log table for a description  
of this error and required actions). The port may be locked up. Check  
the CO wiring, check for excessive loop current, and check the trunk  
translations. (If the trunk is translated incorrectly, this test will abort.)  
2. If the port status is idle, busyout and release the trunk, and then retry  
the command at 1-minute intervals for a maximum of 5 times.  
3. If the test still aborts, replace the circuit pack.  
1001  
1002  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM-Bus) Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present or some tone  
detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-405  
Table 3-175. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the trunk  
group/member number of the port. Use the status trunk command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. You must wait  
until the port is idle before retesting.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times..  
Any  
FAIL  
The NPE of the tested port was found to be transmitting in error. This  
causes noisy and unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated by using other port tests and by  
examining trunk or external wiring.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Loop Around and Conference Circuit Test (#33)  
This test checks the reflective loop around and conference capabilities of a CO  
port circuit. The test uses 404-Hz, 1004-Hz, and 2804-Hz tones. Each tone is  
transmitted separately through the loop and checked.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-406  
Table 3-176. TEST #33 Loop Around and  
Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
Conference Circuit Test aborted.  
7
129  
131  
133  
The 404-Hz reflective loop around test aborted. Response to the test request  
was not received within the allowable time period.  
The 1004-Hz reflective loop around test aborted. Response to the test request  
was not received within the allowable time period.  
The 2804-Hz reflective loop around test aborted. Response to the test request  
was not received within the allowable time period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT  
System resources required to run this test are not available. The port may be  
busy with a valid call. Use the display port PCSSpp command to determine  
the trunk group/member number of the port. Use the status trunk command  
to determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. You must wait until  
the port is idle before retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 769 (see the Error Log table for a description of  
this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1002  
1003  
ABORT  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due to  
TDM-BUS errors. Refer to TDM-BUS Maintenance to diagnose any active  
TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic, repeat  
test at 1-minute intervals a maximum of 5 times.  
The system could not allocate a tone receiver for the test. The system may be  
oversized force.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
Maintenance documentation.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-407  
Table 3-176. TEST #33 Loop Around and  
Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1004  
ABORT  
System resources required to run this test are not available. The port may be  
busy with a valid call. Use the display port PCSSpp command to determine  
the trunk group/member number of the port. Use the status trunk command  
to determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. You must wait until  
the port is idle before retesting.  
1. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1018  
ABORT  
The test was disabled via administration. Verify that the ’Maintenance Test’  
field on the ’Trunk Group’ form is set to ’n’. To enable the test, issue the  
’change trunk-group x’ command (x equals the number of the trunk group to  
be tested). Then, change the entry in the ’Maintenance Test’ field on the form  
to ’y’.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Response to the test was not received within the allowable time period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
2100  
ABORT  
ABORT  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-408  
Table 3-176. TEST #33 Loop Around and  
Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
7,  
FAIL  
The conference capabilities of the port failed (Error Code 7).  
129,  
The reflective 404-Hz Tone Test failed. No transmission was detected to or  
from the port (Error Code 129).  
131, or  
133  
The reflective 1004-Hz Tone Test failed. No transmission was detected to or  
from the port (Error Code 131).  
The reflective 2804-Hz Tone Test failed. No transmission was detected to or  
from the port (Error Code 133).  
FAULT ISOLATION: Proceed as follows unless power or tone problems are  
suspected (see note below).  
1. To make sure the problem is on-board, disconnect the port from the CO  
and retry the test. Coordinate this with the CO, or do it after busy hours;  
otherwise, the CO may put the connection out of service.  
2. If the retry fails, replace the circuit pack.  
3. If the retry passes and no troubles have been reported, disable the test. If  
the retry passes and troubles have been reported, refer the problem to  
the CO.  
NOTE:  
If the looparound and conference circuit test fails for all ports on a  
circuit pack, a -5 volt power problem is indicated. When the tone errors  
are cleared, rerun the test. If the test fails again, see FAULT ISOLATION  
above.  
PASS  
CO Trunk Loop Around and Conference Test is successful. User-reported  
troubles on this port should be investigated by using other port tests and by  
examining trunk or external wiring.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-409  
Port Audit Update Test (#36)  
This test sends updates of the CO port translation for all ports on the circuit pack  
that have been translated. The update is non-disruptive and guards against  
possible corruption of translation data contained on the circuit pack. No  
response message is expected from the circuit pack once it receives translation  
updates. The port translation data includes: ground or loop start trunk, tone or  
rotary dialing trunk, rotary dialing inter-digit timing, network balance R/RC, and  
disconnect timing.  
Table 3-177. TEST #36 Port Audit Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1006  
The port has been placed out of service, perhaps by craft busyout. Use the  
display port PCSSpp command to determine the trunk group/member  
number of the port. Use the status trunk command to determine the  
service state of the port. If the service state indicates that the port is in use,  
then the port is unavailable for certain tests. You must wait until the port is  
idle before retesting.  
1. If the port status is idle, retry the command at 1-minute intervals a  
maximum of 5 times.  
2100  
ABORT  
System resources required to run this test were not available.  
1. If the port status is idle, retry the command at 1-minute intervals a  
maximum of 5 times.  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
This test passed. Translation information was successfully updated on the  
circuit pack. User-reported troubles on this port should be investigated by  
using other port tests and by examining trunk or external wiring. If the trunk  
is busied out, the test does not run, but returns PASS. To verify that the  
trunk is in-service:  
1. Enter status-command to verify that the trunk is in-service. If the trunk  
is in-service, no further action is necessary. If the trunk is  
out-of-service, continue to Step 2.  
2. Enter release-trunk command to put the trunk back into in-service.  
3. Retry the test command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-410  
Table 3-177. TEST #36 Port Audit Update Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Transmission Test (#844-848)  
This test is non-destructive.  
NOTE:  
Tests #844-848 are not supported on a International switch.  
These tests are run by the Automatic Transmission Measurement System (ATMS).  
They are not part of the long or short trunk test sequences. Instead, they are run  
on demand with the test analog-testcall command or as part of ATMS  
scheduled testing.  
The test call attempts to seize a port and make a call to a terminating test line  
(TTL) on the trunk’s far end. Transmission performance measurements are made  
and compared to administered thresholds. Errors are generated when results fall  
outside of ‘‘marginal’’ or ‘‘unacceptable’’ thresholds. Detail and summary  
measurement reports are obtainable via the list testcalls command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-411  
Table 3-178. TEST #844-848 Transmission Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use display port PCSSpp to determine the trunk  
group/member number of the port. Use the status trunk command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port unavailable for this test. You must wait until the  
port is idle before retesting.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate timeslots for the test. The system may be  
under heavy traffic conditions or it may have timeslots out of service due to  
TDM bus errors. Refer to TDM Bus Maintenance to diagnose any active  
TDM bus errors.  
1. If system has no TDM bus errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1004  
ABORT  
The port has been seized by a user for a valid call. Use status trunk to  
determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort and the port is not in use, escalate the  
problem.  
1005  
1115  
ABORT  
ABORT  
Trunk has been administered as incoming-only; transmission tests can  
only be run on outgoing trunks.  
The near end test line could not be allocated.  
1. Verify that the TN798 circuit pack’s port 1 is administered and in  
service with the status port command.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
1900  
1901  
ABORT  
ABORT  
The test completion message was not received from the TN798 circuit  
pack.  
1. Test the TN798 circuit pack.  
This error occurs when the TN798 circuit pack uplinks a message that is  
not the proper response for this test. The anticipated uplink messages are  
seize, ring or answer.  
1. Verify that the Trunk is administered properly.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-412  
Table 3-178. TEST #844-848 Transmission Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Intercept tone detected from far end.  
1905  
ABORT  
1. Get the test line data and verify it with the far end. Dial the test number  
manually to see if the TTL is reached. If it is not, then either the number  
is wrong, or the far end is administered incorrectly.  
1906  
1907  
1913  
1914  
1915  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
Reorder tone detected from far end.  
1. See actions for error code 1905.  
Other unexpected tone detected from far end.  
1. See actions for error code 1905.  
Audible Ring detected from far end.  
1. See actions for error code 1905.  
Unidentified interrupted tone detected from far end.  
1. See actions for error code 1905  
Busy tone detected from far end.  
1. Since the test line at the far end was busy. Try the test again.  
2. If the test continues to abort, the problem is with the far end system.  
Test progress tone not removed from far end (type 105 test line only).  
1918  
1919  
1920  
1921  
ABORT  
ABORT  
ABORT  
ABORT  
1. The problem is with the far end system; a technician at the far end  
should test the test line.  
Unexpected far end release  
1. The problem is with the far end system; a technician at the far end  
should test the test line.  
No response from far end.  
1. The problem is with the far end system; a technician at the far end  
should test the test line.  
No data returned from far end.  
1. The problem is with the far end system; a technician at the far end  
should test the test line.  
1922  
1923  
ABORT  
ABORT  
Steady, unidentifiable tone from far end  
1. See actions for error code 1905.  
Broadband energy detected from far end (such as voice or  
announcement).  
1. See actions for error code 1905.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-413  
Table 3-178. TEST #844-848 Transmission Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
No test tone from far end  
1924  
ABORT  
ABORT  
ABORT  
1. See actions for error code 1905.  
Near-end self test failed.  
1938  
1939  
1. Test the TN798 circuit pack.  
Loss self check at 0dBm at 1004 Hz failed.  
1. Test the TN798 circuit packs.  
2. If the test continues to abort escalate the problem.  
Far end noise self check failed.  
1940  
ABORT  
1. The problem is with the far end system; a technician at the far end  
should test the test line.  
1941  
1942  
1943  
1944  
1945  
1946  
1947  
2000  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
High frequency singing return loss self check failed.  
1. Test the TN798 circuit packs.  
Echo return loss self check failed.  
1. Test the TN798 circuit packs.  
Singing return loss self check failed.  
1. Test the TN798 circuit packs.  
Loss self check at -16 dBm at 1004 Hz failed.  
1. Test the TN798 circuit packs  
Loss self check at -16 dBm at 404 Hz failed.  
1. Test the TN798 circuit packs.  
Loss self check at -16 dBm at 2804 Hz failed.  
1. Test the TN798 circuit packs.  
Noise with tone self check failed.  
1. Test the TN798 circuit packs.  
The test timed out while waiting for a response from the TN798 circuit  
pack.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
An internal software error occurred.  
2012  
2053  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test call could not be established, but no information on why is  
available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
CO-TRK (CO Trunk)  
3
3-414  
Table 3-178. TEST #844-848 Transmission Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2056  
ABORT  
An error occurred while trying to obtain results from the TN798 circuit  
pack.  
1. Test the TN798 circuit pack.  
FAIL  
Measured transmission performance was in the unacceptable range as  
administered on the trunk group form. Retrieve a measurement report via  
the list testcalls command. Make sure that ATMS thresholds are set  
properly on page 4 of the trunk group form. Besides the facility, test  
failures can be caused by faulty test lines or switch paths. If the  
measurements point to a facility problem, report the results to the trunk  
vendor.  
8000  
FAIL  
Measured transmission performance was in the marginal range as  
administered on the trunk group form. This generally means that the trunk  
is usable but has an undesirable amount of noise or loss. If the user does  
not report unacceptable effects, it may not be necessary to take any  
action. Retrieve a measurement report via the list testcalls command.  
Make sure that ATMS thresholds are set properly on page 4 of the trunk  
group form.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CONFIG (System Configuration)  
3-415  
CONFIG (System Configuration)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
CONFIG  
none  
none  
System Configuration  
The System Configuration maintenance object (MO) oversees logical insertion  
and removal of circuit packs in the system. When Switch Control detects that a  
circuit pack is present in a port slot, it informs System Configuration and System  
Configuration queries the circuit pack to determine the type and vintage of the  
circuit pack. Similarly, when Switch Control detects that a circuit pack has been  
removed from a port slot, it informs System Configuration.  
There are no alarms or tests for System Configuration, but three types of errors  
are logged to the Hardware Error Log (see below).  
Hardware Error Log Entries and Test to Clear  
Values  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Error Type  
Associated Test  
Any  
Test to Clear Value  
none  
1
0
0
Any  
Any  
2-117(a)  
0-2  
0-2  
none  
none  
none  
257(b)  
1002-1117(c)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. This error indicates that a Port circuit pack in the system did not respond  
to a circuit pack type inquiry. Follow the procedures outlined in (c) to  
determine if there is an error.  
b. This error indicates that less than 25% of Trunk Group is available.  
c. This error indicates that a Port circuit pack in the system did not respond  
to a vintage inquiry.  
As a result of either of these errors, a Port circuit pack may be physically  
inserted in a Port slot, but the system may not recognize it.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CUST-ALM (Customer-Provided Alarming Device)  
3-416  
CUST-ALM (Customer-Provided  
Alarming Device)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
Full Name of MO  
Customer-Provided Alarming Device  
CUST-ALM  
none  
test customer-alarm PC  
1. Where PC is an appropriate port network number and carrier.  
The system provides customers a way to connect their own alarm indication  
device to a switch. The CUST-ALM maintenance object represents this  
Customer-Provided Alarming Device (CPAD). When an alarm occurs at least to  
the level to which the CPAD is administered, the CPAD in the Processor Port  
Network (PPN)is activated. The CPAD is administered by the  
Maintenance-Related System-Parameters Form (CPE Alarm Activation Level  
field). The CPAD is connected to the Processor circuit pack. The valid levels to  
which to set the CPE Alarm Activation Level are: none, warning, minor, or major.  
The CPAD is also activated within a cabinet whenever Emergency Transfer is  
invoked within that cabinet. The CUST-ALM MO is not maintained by the system  
and does not generate any alarms. If a problem is suspected with the CPAD, it  
may be tested using the test customer-alarm command, which activates the  
device by closing the relay on the Processor circuit pack for 1 minute. The repeat  
parameter may be used to close the relay for a longer length of time (5 minutes is  
the suggested repeat value).  
The CPAD is also activated within a cabinet whenever Emergency Transfer is  
invoked within that cabinet. The CUST-ALM MO is not maintained by the system,  
and does not generate any alarms. If a problem is suspected with the CPAD, it  
may be tested using the test customer-alarm command, which activates the  
device by closing the relay on either the Processor circuit pack for 1 minute. The  
repeat parameter may be used to close the relay for a longer length of time (5  
minutes is the suggested repeat value).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CUST-ALM (Customer-Provided Alarming Device)  
3-417  
Error Log Entries and Test to Clear Values  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
none  
Test to Clear Value  
none  
none  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
There are no errors associated with the CPAD CUST-ALM MO. The test  
customer-alarm PC command is provided to allow a technician to check that the  
customer-provided alarming device is correctly installed and functional. It is  
recommended that this test be run at least once after both the switch and the  
customer alarm have been installed.  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Customer-Provided Alarming Device Test, for example, you may also clear errors  
generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Customer-Provided Alarming Device Test (#115)  
X
X
ND  
1. D = Destructive; ND = Nondestructive  
Customer-Provided Alarming Device Test (#115)  
This test closes the relay that activates the CPAD for 1 minute only within the port  
network specified. If it takes longer than 1 minute to check that the CPAD has  
been activated, the Repeat field on the test customer-alarm PC command can  
be used to close the relay for up to 99 minutes. Note that when the repeat option  
is used, the results for Test #115 come back immediately and, for each test that  
passed, the CPAD is kept on for that many minutes. The CPAD does not go off  
after 1 minute and then come back on. Instead, the CPAD is kept on continuously  
for the entire time. If the CPAD is being activated and deactivated in a flickering  
fashion, there is a problem with either the CPAD or the Processor circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
CUST-ALM (Customer-Provided Alarming Device)  
3-418  
Table 3-179. TEST #115 Customer-Provided Alarming Device Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
(blank)  
1000  
2029  
ABORT  
Internal system error  
1. Try the command at 1-minute intervals a maximum of 5 times.  
PASS  
The switch software successfully sent the request to the Processor circuit  
pack to turn on the CPAD. The CPAD must be physically inspected to  
verify that it is working. If the CPAD is working and the customer has  
complained that the CPAD did not indicate a system alarm when it  
occurred, then check the administered levels for turning on the CPAD via  
the Display System-Parameter Maintenance screen form. Compare these  
levels with the customer’s specifications. If Test #115 passes, and the  
CPAD is not being activated, check the connection of the CPAD to the  
Processor circuit pack. If the CPAD can be activated but cannot be  
deactivated, first check to make sure Emergency Transfer is not activated  
in the affected port network via the status system command. Emergency  
Transfer can be forced to manual OFF by the Emergency Transfer switch  
on the Processor circuit pack. If Emergency Transfer is OFF and the CPAD  
still cannot be deactivated, check the administered levels for the CPAD  
with the Display System-Parameter Maintenance screen form and  
compare against the alarm levels currently present in the system (display  
alarms command).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-BD (Data Channel Processor Circuit Pack)  
3-419  
DATA-BD (Data Channel Processor  
Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm Level  
WARNING  
MINOR  
Initial Command to Run  
test network-control  
test network-control  
test network-control  
Full Name of MO  
DATA-BD  
Network Control Circuit Pack  
Network Control Circuit Pack  
Network Control Circuit Pack  
DATA-BD  
DATA-BD  
WARNING  
The DATA-BD is a generic hardware that supports the Data Channels on the  
Processor circuit pack. All circuit packs that have an interface with the TDM Bus  
have a common set of generic hardware that provides the TDM Bus interface.  
Consequently, these circuit packs share a common set of tests that verify the  
integrity of the generic hardware. The circuit packs and common set of tests that  
they share are described in XXX-BD (Common Port Circuit Pack) Maintenance  
documentation. Because the Processor circuit pack has this common set of  
hardware, it is classified in the XXX-BD Maintenance documentation as a service  
port circuit pack.  
The DATA-BD MO is different from other XXX-BD MO in that the DATA-BD MO is  
always inserted (because it is part of the Processor circuit pack). Also because  
the DATA-BD MO is part of the Processor circuit pack, some board commands  
do not apply to this MO. To access the DATA-BD MO, use the test  
network-control [short | long] command.  
Error Log Entries and Test to Clear Values  
Table 3-180. Data Channel Processor Circuit Pack Error Log Entries  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Error Type  
Associated Test  
Any  
Test to Clear Value  
1
0
0
0
0
Any  
Any  
test data-module <ext> sh  
r 1  
1 (a)  
Data Channel Reset  
Test (#107)  
MINOR  
ON  
test data-module <ext> l  
23 (b)  
257  
None  
WNG  
OFF  
ON  
Any  
Control Channel Test  
(#52)  
MINOR  
test network-control [a | b]  
sh r 20  
257 (c)  
513 (d)  
0
None  
None  
Any  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-BD (Data Channel Processor Circuit Pack)  
3-420  
Table 3-180. Data Channel Processor Circuit Pack Error Log Entries — Continued  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Error Type  
769 (e)  
Associated Test  
None  
Test to Clear Value  
4358  
1025 (f)  
4363  
NPE Audit Test (#50)  
test network-control [a | b]  
sh  
1538 (g)  
Data Channel Reset  
Test (#107)  
MINOR  
ON  
test data-module <ext> l  
3840 (h)  
3999(i)  
Any  
Any  
None  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. This error indicates the DATA-BD portion of the Processor circuit pack  
stopped functioning. Since the Processor circuit pack cannot be reset via  
the reset board PCSS command, the Data Channel Reset Test (#107) in  
the Long Test Sequence for the DATA-CHLs must be used to reset it as  
follows:  
1. Issue the list data command to determine if one, or more, Data  
Channels (DATA-CHLs) is administered.  
NOTE:  
A Data Channel (DATA-CHL) is identified by a "type" value of  
"netcon."  
2. If a Data Channel (DATA-CHL) is not administered, use the add  
data-module [<ext> | next] command to administer a DATA-CHL.  
3. From the form resulting from the list data command, choose a Data  
Channel (DATA-CHL).  
4. Issue the test data-module <ext> long command using the  
extension for the DATA-CHL chosen in Step 3.  
!
WARNING:  
Issuing this command drops all data channel extensions. See  
DATA-CHL (Data Channel) Maintenance documentation first.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-BD (Data Channel Processor Circuit Pack)  
3-421  
If the red LED stays on, then replace the Processor circuit pack.  
b. The circuit pack has been logically administered but not physically  
installed. The alarm is cleared when the circuit pact is installed.  
c. This error indicates transient communications problems with this circuit  
pack. This error is not service-affecting and no action is required.  
d. This error indicates the circuit pack has reported a hardware failure on the  
circuit pack. The circuit pack should be replaced.  
e. This error can be ignored, but look for other errors on this circuit pack.  
f. This error is not service-affecting and no action is required.  
g. This error indicates the DATA-BD portion of the Processor circuit pack is  
out-of-service. Since the Processor circuit pack cannot be reset via the  
reset board PCSS command, the Data Channel Reset Test (#107) in the  
Long Test Sequence for the DATA-CHL must be used to reset it as follows:  
1. Issue the list data command to determine if one or more Data  
Channels (DATA-CHLs) are administered.  
NOTE:  
A Data Channel (DATA-CHL) is identified by a "type" value of  
"netcon."  
2. If a Data Channel (DATA-CHL) is not administered, use the add  
data-module [<ext> | next] command to administer a DATA-CHL.  
3. From the form resulting from the list data command, choose a Data  
Channel (DATA-CHL).  
■
Refer to “DATA-CHL” before issuing the test network-  
control long command to determine if CDR, System Printer,  
Journal Printer, and/or PMS Links are using the DATA-CHLs  
and how to busyout these links prior to running destructive  
tests on the DATA-CHLs.  
■
Refer to “SW-CTL” before issuing the reset switch-control  
command to determine the consequences of running the  
Switch Control Reset Test (Test #93).  
4. Issue the test data-module <ext> long command using the  
extension for the DATA-CHL chosen in Step 3.  
If the error happens again within 15 minutes, then replace the  
circuit pack.  
h. This error is not service-affecting and no action is required.  
i. Error type 3999 Indicates that the circuit pack sent a large number of  
control channel messages to the switch within a short period of time. If  
error type 1538 is also present, then the circuit pack was taken  
out-of-service due to hyperactivity. If error type 1538 is not present, then  
the circuit pack has not been taken out-of-service, but it has generated  
50% ofDtohwenlmoaedsfrsomagWewswn.Seocmeasnusaalsr.ycotmo. bAlel McaonnuaslsidSeeraercdh AhnydpDeorwanclotiavde. . This may  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-BD (Data Channel Processor Circuit Pack)  
3-422  
be completely normal during heavy traffic periods. However, if this error  
type is logged when the circuit pack is being lightly used, it may indicate a  
problem with the circuit pack or the equipment attached to it.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the NPE Audit Test, for example, you may also clear  
errors generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Audit Test (#50) (a)  
D/ND  
ND  
X
X
Control Channel Loop Around Test (#52)  
X
ND  
1. D = Destructive; ND = Nondestructive  
Note:  
a. Refer to “DATA-CHL” and “SW-CTL” for other tests associated with  
DATA-BD maintenance.  
NPE Audit Test (#50)  
The system sends a message to the on-board microprocessor to update the  
network connectivity information for all the NPEs on the circuit pack.  
Table 3-181. TEST #50 NPE Audit Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
Could not allocate the necessary system resources to run this test.  
Could not allocate the necessary system resources to run this test.  
Test already in progress.  
ABORT  
ABORT  
ABORT  
FAIL  
2100  
1019  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The circuit pack’s NPEs have been updated with their translation.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-BD (Data Channel Processor Circuit Pack)  
3-423  
Control Channel Loop Around Test (#52)  
This test queries the circuit pack for its circuit pack code and vintage and verifies  
its records.  
Table 3-182. TEST #52 Control Channel Loop Around Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
Could not allocate the necessary system resources to run this test.  
Internal system error  
ABORT  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Communication with this circuit pack is successful.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-424  
DATA-CHL (Data Channel)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test data-module l <ext>  
test data-module sh <ext>  
Full Name of MO  
Data Channel  
Data Channel  
1
DATA-CHL  
MINOR  
2
3
DATA-CHL  
WARNING  
1. The test data-module <ext> long command drops all sessions on all of the Data Channels. Refer  
to Data Channel Reset Test (#107).  
2. <ext> is the extension of the Data Channel to be tested. The extension can be determined by  
issuing the list data-module command from the administration terminal. The resulting form  
provides a mapping from the 1CXXpp designation of the Data Channel to its corresponding  
extension, where pp indicates which one of the four Data Channels is alarmed (01, 02, 03, or 04)  
and C indicates the carrier on which the alarmed Data Channel resides.  
3. The test data-module <ext> long command drops all sessions on all of the Data Channels. Refer  
to Data Channel Reset Test (#107).  
The four Data Channels (DATA-CHLs) provide a data communications interface  
that allows data terminal equipment connected to port circuit packs to  
communicate with software applications running on the system. Each DATA-CHL  
represents a dial-up/dial-out asynchronous communications port that interfaces  
to the TDM Bus. Data is transported between the terminal equipment and the  
software application over the DATA-CHL. Data Channels may be used to support  
the following features and functions:  
■
Establishment of a connection over which to log CDR data to a printer or  
other storage unit. This connection is called PRI-CDR/SEC-CDR (PRI-CDR  
Link).  
■
Establishment of connections over which to log PMS, Automatic Wakeup,  
and Emergency Access to Attendant data to a Journal printer. This  
connection is called PMS-PRINT/JRNL-PRNT (PMS Printer Link).  
■
■
■
Establishment of a connection to a customer-owned PMS. This connection  
is called the PMS-LINK.  
Establishment of a connection to system printer. This connection is called  
the System Printer Link (SYS-PRNT).  
Establishment of connection(s) for up to two secondary administration  
terminals.  
■
■
■
Saving announcements from the ANN-BD (Announcement Circuit Pack).  
Restoring announcements to the ANN-BD (Announcement Circuit Pack).  
Maintenance testing of the DATA-CHLs.  
From the viewpoint of administration, the four DATA-CHLs on the TN798  
Processor circuit pack are numbered 01 through 04. Each DATA-CHL may be  
assigned a unique extension using the add data-module [ <ext> | next ]  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-425  
command. These extensions are called active extensions. When assigning an  
active extension to a DATA-CHL XX (where XX is 01, 02, 03, or 04) the Add  
Data-Module form also requires the user to assign a unique maintenance  
extension. The maintenance extension is required.  
1. Determine if CDR, System Printer, Journal Printer, and/or PMS Links are  
using the DATA-CHLs and busyout these links if it is necessary to use the  
test network-control long command.  
2. Refer to ‘‘SW-CTL (Switch Control)’’ Maintenance documentation before  
executing the reset switch-control command to determine the  
consequences of running the Switch Control Reset Test (Test #93).  
3. Refer to ‘‘IO-PROCR (I/O Processor)’’ Maintenance document before  
executing the reset io-processor command to determine the  
consequences of resetting the IO Processor.  
Status of Data Channels  
In order to perform maintenance testing on the DATA-CHLs, the DATA-CHLs  
cannot be busy with one of the functions described previously. A series of system  
technician commands can be used to determine if the DATA-CHLs are busy and,  
if so, to determine the function for which they are being used. This series of  
system technician commands is described below and should be done before  
testing the DATA-CHLs.  
Issue the list data-module command to determine the extensions for the  
administered Data Channels.  
NOTE:  
A Data Channel is identified by a "type" value of "netcon."  
For each Data Channel, determine if the DATA-CHL is busy by issuing the status  
data-module <ext> command using the DATA-CHL’s extension. If the DATA-CHL  
is busy, the Service State field in the resulting form will be in service/active.  
However, the form does not indicate the reason the DATA-CHL is busy. This must  
be determined using other system technician commands.  
Use the procedures below to determine whether busy Data Channels are being  
used for CDR, Journal Printer, or PMS Links. If a DATA-CHL is busy with one of  
these links then, in order to test the DATA-CHL, the link must be busied out using  
busyout smdr-link, busyout journal-printer wakeup-log, busyout  
journal-printer pms-log, or busyout pms-link command, respectively. Do not  
issue any of these busyout commands unless instructed to do so while  
investigating Error Codes according to the "System Technician-Demanded Tests:  
Descriptions and Error Codes" subsection. If one of these links must be busied  
out to perform maintenance testing, restore the link to service according to  
PRI-CDR/SEC-CDR (PRI-CDR Link), PMS-PRNT/JNL-PRNT (PMS Printer Link),  
and PMS-LINK Maintenance documentation, respectively.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-426  
If a DATA-CHL is busy but is not being used for one of these links, then it is being  
used for a secondary administration terminal connection or for maintenance  
testing. If it is being used for a secondary administration terminal connection,  
then in order to test the DATA-CHL that the connection is using, the DATA-CHL  
must be busied out using the busyout data-module <ext> command.  
NOTE:  
The busyout data-module <ext> command causes the connection over  
the associated DATA-CHL to be dropped. Do not issue this command  
unless instructed to do so.  
If the DATA-CHL must be busied out in order to perform maintenance testing, the  
secondary administration terminal connection must be re-established by  
redialing the DATA-CHL.  
CDR Links  
1. Issue the status smdr-link command to see if an CDR Link has been  
established. If the Link Statefield is Up, then the CDR Link may be  
using one of the Data Channels (DATA-CHLs).  
2. Issue the display system features command and go to the CDR  
subsection on Page 2 of the resulting form. Note the values in the Primary  
Output Extension and Secondary Output Extension fields. If the values are  
extensions, then the CDR Link is using one of the Data Channels  
(DATA-CHLs).  
3. For each of the extensions in the Primary Output Extension and Secondary  
Output Extension fields, issue the status data-module <ext> command  
using the extension. Note the value in the Connected Ports field of the  
resulting form. If there is a port value in the field, then the indicated port is  
a Data Channel (DATA-CHL).  
4. Issue the list data-module command, locate each port indicated in the  
Connected Ports fields, and determine if that port has a "type" value of  
"netcon." If so, then there is an CDR Link over that DATA-CHL.  
System Printer Links  
1. Issue the status sp-link command to see if a System Printer Link has  
been established. If the Link Statefield is Up, then the System Printer  
Link may be using one of the Data Channels (DATA-CHLs).  
2. Issue the display system features command and go to the System  
Printer subsection on Page 2 of the resulting form. Note the values in the  
Primary Output Extension and Secondary Output Extension fields. If the  
values are extensions, then the System Printer Link is using one of the  
Data Channels (DATA-CHLs).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-427  
3. For each of the extensions in the Primary Output Extension and Secondary  
Output Extension fields, issue the status data-module <ext> command  
using the extension. Note the value in the Connected Ports field of the  
resulting form. If there is a port value in the field, then the indicated port is  
a Data Channel (DATA-CHL).  
4. Issue the list data-module command, locate each port indicated in the  
Connected Portsfields, and determine if that port has a "type" value of  
netcon. If so, then there is a System Printer Link over that DATA-CHL.  
Journal Printer Links  
1. Issue the status journal-link wakeup-log and status journal-link  
pms-log commands to see if one or both of these Journal Printer Links  
have been established. If the Link Statefield is Upfor either of these,  
then that Journal Printer Link may be using one of the Data Channels  
(DATA-CHLs).  
2. Issue the display system hospitality command and note the values in  
the Extension of Journal/System Printer and Extension of PMS Log Printer  
fields. If either of these values are extensions, then that Journal Printer Link  
is using one of the Data Channels (DATA-CHLs).  
3. For each of the extensions in the Extension of Journal/Schedule Printer  
and Extension of PMS Log Printer fields, issue the status data-module  
<ext> command using the extension. Note the value in the Connected  
Portsfield of the resulting form. If there is a port value in the field, then  
the indicated port is a Data Channel (DATA-CHL).  
4. Issue the list data-module command, locate each port indicated in the  
Connected Portsfields, and determine if that port has a "type" value of  
netcon. If so, then there is a Journal Printer Link over that DATA-CHL.  
PMS Link  
1. Issue the status pms-link command to see if a PMS Link has been  
established. If the Link Statefield is Up, the PMS Link may be using  
one of the Data Channels (DATA-CHLs).  
2. Issue the display system hospitality command and note the value in the  
Extension of the PMSfield. If this value is an extension, the PMS Link is  
using one of the Data Channels (DATA-CHLs).  
3. For the extension in the Extension of PMS field, issue the status  
data-module <ext> command using the extension. Note the value in the  
Connected Portsfield of the resulting form. If there is a port value in the  
field, the indicated port is a Data Channel (DATA-CHL).  
4. Issue the list data-module command, locate the port indicated in the  
Connected Portsfield, and determine if that port has a "type" value of  
netcon. If so, there is a PMS Link over that DATA-CHL.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-428  
Error Log Entries and Test to Clear Values  
Table 3-183. Data Channel Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0 (a)  
0
Any  
Any  
ON  
test data-module <ext> sh r 1  
test data-module <ext> sh r 3  
1
Any  
Local Loop Back Test  
(#111)  
MINOR  
18  
0
busyout data-module  
<ext>  
WARNING  
OFF  
release data-module <ext>  
130  
257  
None  
WARNING  
MINOR  
ON  
ON  
test data-module <ext> sh  
Any  
Remote Maintenance  
Loop Around Test  
(#109)  
test data-module <ext> sh r 5  
513  
769  
Any  
Any  
Crosstalk Test (#110)  
MINOR  
MINOR  
ON  
ON  
test data-module <ext> sh r 3  
test data-module <ext> l r 3  
Dual Port RAM Test  
(#108)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
There are two system technician test commands that include the Data Channels  
(DATA-CHLs). The test data-module <ext> [short | long] command tests the  
single DATA-CHL that has the extension specified by <ext>. The test  
network-control [short | long] command tests each administered DATA-CHL  
that resides on the Processor circuit pack in the specified carrier.  
Always investigate tests in the order presented in the following tables when  
inspecting errors in the system. By clearing error codes associated with the Data  
Channel Reset Test, for example, you may also clear errors generated from other  
tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-429  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Data Channel Reset Test (#107) (a)  
X
D
Data Channel Dual Port Ram Test (#108) (a)  
Data Channel Remote Maintenance Loop Around Test (#109)  
Data Channel Local Loop Back Test (#111)  
Data Channel Crosstalk Test (#110)  
X
X
X
X
D
X
ND  
ND  
ND  
X
X
1. D = Destructive; ND = Nondestructive  
Note:  
a. Determine if CDR, System Printer, Journal Printer, and/or PMS Links are  
using the DATA-CHLs and busyout these links if it is necessary to use the  
test network-control long command.  
Table 3-184. System Technician-Demanded Tests: DATA-CHL  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Control Channel Test (Common Port Circuit Pack) (#52) (a)  
NPE Audit Test (Common Port Circuit Pack) (#50) (a)  
Data Channel Reset Test (#107)  
D/ND  
ND  
ND  
D
X
X
X
X
X
X
X
X
Data Channel DPR Test (#108)  
D
Data Channel Maintenance Loop Around Test (#109)  
Data Channel Crosstalk Test (#110)  
X
X
X
ND  
ND  
ND  
D
Data Channel Local Loop Back Test (#111)  
Switch Control Reset Test (#93) (b) (d)  
Time-of-Day Clock Test (#95) (b)  
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
ND  
ND  
Control Channel Interface Test (#92) (b)  
Control Channel Transmission Test (#94) (b)  
12 Volt Power Supply Test (#701) (c)  
Memory Card Insertion Test (#695) (c)  
Memory Card Format and Read Test (#696) (c)  
Memory Card Match Test (#697) (c)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-430  
Table 3-184. System Technician-Demanded Tests: DATA-CHL — Continued  
Short Test  
Long Test  
Sequence  
1
Order of Investigation  
Memory Card Write-Protected Test (#698) (c)  
Memory Card Directory Recovery Test (#699) (c)  
Memory Card Translation Data Integrity Test (#694) (c)  
Memory Card Erase/Write/Read Test (#693) (c)  
Sequence  
D/ND  
ND  
X
X
X
X
X
ND  
ND  
X
ND  
1. D = Destructive, ND = Non-destructive  
Notes:  
a. Refer to DATA-BD (Data Channel Processor Circuit Pack) Maintenance  
documentation for a description of these tests.  
b. Refer to SW-CTL (Switch Control) Maintenance documentation for a  
description of these tests.  
c. Refer to CARD-MEM for information on this test.  
d. This test is only run as part of the reset switch-control command.  
Data Channel Reset Test (#107)  
This test is destructive.  
This test resets the entire data communications interface provided by the four  
DATA-CHLs. All existing connections over the DATA-CHLs are dropped.  
Table 3-185. TEST #107 Data Channel Reset Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
System resources required to run this test are not available.  
1. Try the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-431  
Table 3-185. TEST #107 Data Channel Reset Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
System resources required for this test are unavailable.  
An ABORT has one of two different meanings:  
1. System resources required to run this test are not available.  
2. Internal system error  
2100  
ABORT  
ABORT  
10704  
Any  
ABORT  
FAIL  
Internal system error  
1. Try the command at 1-minute intervals a maximum of 5 times.  
The circuit pack failed to reset.  
1. Execute the command again.  
2. If the problem persists, replace the Processor circuit pack.  
After the Processor circuit pack has been replaced, its Time-of-Day clock  
must be set using the set time command.  
PASS  
The circuit pack initializes correctly.  
Data Channel Dual Port RAM Test (#108)  
This test is destructive.  
This is a coordinated test of the dual port RAM that is shared between the  
hardware and software. Control messages and data are passed through this dual  
port RAM to establish and tear down connections over the DATA-CHLs. This test  
requests each side to read and write the dual port RAM, first one at a time and  
then simultaneously in alternate locations.  
This test prevents any control stimuli from being received from or sent to the TDM  
Bus control channel preventing the establishment of new connections over the  
DATA-CHLs. However, existing connections are not (and cannot) be dropped.  
Table 3-186. TEST #108 Data Channel Dual Port RAM Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-432  
Table 3-186. TEST #108 Data Channel Dual Port RAM Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
FAIL  
The dual port RAM is not functioning correctly. Either the software cannot  
correctly read from it and/or write to it or the hardware cannot correctly  
read from it and/or write to it. Connections cannot be established over the  
DATA-CHLs.  
1. Execute the command again.  
2. If the problem persists, replace the Processor circuit pack. After the  
Processor circuit pack has been replaced, its Time-of-Day clock must  
be set using the set time command.  
PASS  
The dual port RAM is functioning. Connections can be established over  
the DATA-CHLs.  
Data Channel Remote Maintenance Loop Around  
Test (#109)  
This test verifies the integrity of the entire DATA-CHL (that is, the software, dual  
port RAM, and hardware that compose it). It verifies that a connection can be  
established over the DATA-CHL and that the DATA-CHL can correctly send and  
receive data over the connection (that is, over the TDM Bus). The test actually  
involves two DATA-CHLs: the DATA-CHL that is the target of the test and a  
second, arbitrary, unbusy DATA-CHL. A connection is set up by placing a call out  
from the arbitrary DATA-CHL and into the target DATA-CHL. Data is looped over  
the connection in each direction (that is, the target DATA-CHL is tested as both a  
sender of data and a receiver of data). The test checks that the data received by  
one DATA-CHL is the same as the data that was sent by the other DATA-CHL.  
Because it establishes a connection between two Data Channels (DATA-CHLs)  
across the TDM Bus, this test does more than just verify the integrity of the target  
DATA-CHL. It also verifies the integrity of the TDM Bus and Tone-Clock circuit  
pack (by sending and receiving data).  
If this test aborts or fails, it is impossible to determine from this test alone whether  
the defective DATA-CHL is the target DATA-CHL or the arbitrarily chosen  
DATA-CHL, or if the problem lies with the TDM Bus, or Tone-Clock circuit pack.  
The results of running Tests #107, #108, #110, and #111 on the DATA-CHL can  
be used to determine whether the target DATA-CHL is defective.  
NOTE:  
If an Error Code is encountered recommending that an CDR, System  
Printer, Journal Printer, and/or PMSLink be busied out, restore each busied  
out link to service according to PRI-CDR/SEC-CDR (PRI-CDR Link),  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-433  
SYS-PRNT (System Printer Link), JNL-PRNT (Journal Printer Link), or  
PMS-PRNT/JNL-PRNT (PMS Printer Link) Maintenance documentation,  
respectively, before concluding work on the problem.  
Table 3-187. TEST #109 Data Channel Remote Maintenance Loop Around Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
For this test, an Error Code of 4 can have 2 different meanings:  
a. The target DATA-CHL is busy and, therefore, not available for use.  
b. Internal system error  
4
ABORT  
Note the results of Tests #110 and #111 in the Short Test Sequence for the  
target DATA-CHL. If the results of Tests #110 and #111 are both PASS, then  
there is a high probability that the target DATA-CHL is not defective.  
Proceed with the remaining steps only if it is necessary to completely test  
the target DATA-CHL:  
1. Determine if the target DATA-CHL is in use for some other function (that  
is, CDR Link, System Printer Link, Journal Printer Link, PMS Link, or  
secondary administration terminal connection) as described previously  
in the ‘‘Status of Data Channels’’ section. If so, check for errors on the  
function that is using the DATA-CHL. If there are no errors, there is a high  
probability that the DATA-CHL is not defective. Proceed with the  
remaining steps only if it is necessary to completely test the target  
DATA-CHL.  
2. If the target DATA-CHL is in use for some other function, busyout the  
function (CDR Link, System Printer Link, Journal Printer Link, PMS Link)  
or the DATA-CHL (secondary administration terminal connection only).  
3. Retry the command at 1-minute intervals a maximum of 5 times.Restore  
any busied out CDR, System Printer, Journal Printer, or PMS Link to  
service before moving on to another activity.  
30  
31  
32  
33  
40  
41  
70  
75  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-434  
Table 3-187. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
For this test, an Error Code of 1000 can have one of several different  
meanings:  
a. The target DATA-CHL is busy and, therefore, not available for use.  
b. No other DATA-CHLs are administered and, therefore, not available to  
place the call to the target DATA-CHL.  
c. All other DATA-CHLs are busy and, therefore, not available to place  
the call to the target DATA-CHL.  
d. System resources required to run this test are not available.  
e. Internal system error  
Note the results of Tests #110 and #111 in the Short Test Sequence for the  
target DATA-CHL. If the results of Tests #110 and #111 are both PASS, then  
there is a high probability that the target DATA-CHL is not defective.  
Proceed with the remaining steps only if it is necessary to completely test  
the target DATA-CHL:  
1. Determine if the target DATA-CHL is in use for some other function (that  
is, CDR Link, System Printer Link, Journal Printer Link, PMS Link, or  
secondary administration terminal connection) as described previously  
in the "Status of network Control Data Channels" section. If so, check for  
errors on the function that is using the DATA-CHL. If there are no errors,  
there is a high probability that the DATA-CHL is not defective. Proceed  
with the remaining steps only if it is necessary to completely test the  
target DATA-CHL.  
2. If the target DATA-CHL is in use for some other function, busyout the  
function (CDR Link, System Printer Link, Journal Printer Link, PMS Link)  
or the DATA-CHL (secondary administration terminal connection only).  
(Continued)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-435  
Table 3-187. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
(cont’d.)  
3. Issue the list data-module command to determine if other DATA-CHLs  
are administered. If no other DATA-CHLs are administered, administer at  
least one at this time.  
4. Determine if the DATA-CHLs OTHER THAN the target DATA-CHL are all  
in use for some other function (that is, CDR Link, System Printer Link,  
Journal Printer Link, PMS Link, or secondary administration terminal  
connection) as described previously in the "Status of Data Channels"  
section. If so, and if it is necessary to completely test the target  
DATA-CHL, use the following preference guidelines to free one of the  
DATA-CHLs for testing.  
a. If a DATA-CHL is being used for a secondary administration terminal  
connection, busyout that DATA-CHL.  
b. Otherwise, if a DATA-CHL is being used for a PMS Link, busyout the  
PMS Link.  
c. Otherwise, if a DATA-CHL is being used for a Journal Printer Link,  
busyout the Journal Printer Link.  
d. Otherwise, if a DATA-CHL is being used for an CDR Link, busyout the  
CDR Link.  
e. Otherwise, if a DATA-CHL is being used for a System Printer Link,  
busyout the System Printer Link.  
5. Retry the command at 1-minute intervals a maximum of 5 times.  
6. Restore any busied out CDR, System Printer, Journal Printer, or PMSLink  
to service before moving on to another activity.  
1006  
ABORT  
For this test, an Error Code of 1006 can have one of several different  
meanings:  
a. No other DATA-CHLs are administered and, therefore, not available to  
place the call to the target DATA-CHL.  
b. All other DATA-CHLs are busy and, therefore, not available to place  
the call to the target DATA-CHL.  
c. System resources required to run this test are not available.  
d. Internal system error  
Note the results of Tests #110 and #111 in the Short Test Sequence for the  
target DATA-CHL. If the results of Tests #110 and #111 are both PASS, then  
there is a high probability that the target DATA-CHL is not defective.  
Proceed with the remaining steps only if it is necessary to completely test  
the target DATA-CHL:  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-436  
Table 3-187. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1006  
ABORT  
(cont’d.)  
1. Issue the list data-module command to determine if other DATA-CHLs  
are administered. If no other CATA-CHLs are administered, administer at  
least one at this time.  
2. Determine if the target DATA-CHL is in use for some other function (that  
is, CDR Link, System Printer Link, Journal Printer Link, PMS Link, or  
secondary administration terminal connection) as described previously  
in the "Status of Network Control Data Channels" section. If so, check for  
errors on the function that is using the DATA-CHL. If there are no errors,  
there is a high probability that the DATA-CHL is not defective. Proceed  
with the remaining steps only if it is necessary to completely test the  
target DATA-CHL.  
a. If a DATA-CHL is being used for a secondary administration terminal  
connection, busyout that DATA-CHL.  
b. Otherwise, if a DATA-CHL is being used for a PMS Link, busyout the  
PMS Link.  
c. Otherwise, if a DATA-CHL is being used for a Journal Printer Link,  
busyout the Journal Printer Link.  
d. Otherwise, if a DATA-CHL is being used for an CDR Link, busyout the  
CDR Link.  
e. Otherwise, if a DATA-CHL is being used for a System Printer Link,  
busyout the System Printer Link.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
4. Restore any busied out CDR, System Printer, Journal Printer, or PMSLink  
to service before moving on to another activity.  
1016  
ABORT  
Resources for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Test disabled via software patch.  
Internal system error  
1018  
2003  
2004  
ABORT  
ABORT  
ABORT  
Internal system error  
1. Check the dial plan to make sure that the extensions of the data channel  
are set up as local extensions rather than remote or UDP extensions.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-437  
Table 3-187. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
40  
41  
2000  
2003  
2004  
FAIL  
In the case of Error Codes 40 and 41, the Remote Maintenance Loop Around  
Test failed because the data received over the connection did not match the  
data sent over the connection (data was corrupted). In the case of Error  
Codes 2000, 2003, and 2004, the Remote Maintenance Loop Around Test  
failed because the data looped over the connection was not received (data  
was lost).  
However, because it involves two DATA-CHLs, the test’s failure is not  
sufficient to indict either one of the two DATA-CHLs as defective.  
1. Check the dial plan to make sure that the extensions of the data channel  
are set up as local extensions rather than remote or UDP extensions.  
2. Determine which of the DATA-CHLs is in use for some other function  
(that is, CDR Link, System Printer Link, Journal Printer Link, PMS Link, or  
secondary administration terminal connection) as described in the  
"Status of Data Channels" section.  
3. Note the test results for Tests #110 and #111 in the Short Test Sequence  
for the target DATA-CHL and refer to Steps 4, 5, and/or 6 to determine  
the appropriate actions to take based on those results.  
4. If the result of Test #110 is PASS and the result of Test #111 is PASS for  
the target DATA-CHL, then the most likely problem is that the arbitrarily  
chosen DATA-CHL is defective.  
■
Run the Short Test Sequence for each DATA-CHL that is not in use for  
some other function. Note the test results for Tests #110 and #111 for  
each of them.  
■
If the results of Tests #110 and #111 are both FAIL for at least one of  
the other DATA-CHLs, investigate the possibility of a defective  
arbitrarily chosen DATA-CHL.  
a. Issue the remove data-module <ext> for each DATA-CHL for  
which the results of Tests #110 and #111 were both FAIL to  
remove the DATA-CHL from operation.  
b. Repeat the test.  
c. Replace the Processor circuit pack at your earliest  
convenience.  
Replace the circuit pack as described in Chapter 5, "Routine  
Maintenance Procedures".  
After the Processor circuit pack has been replaced, its Time-of-Day  
clock must be set using the set time command.  
5. If the results of Tests #110 and #111 are not both FAIL for any one of the  
other DATA-CHLs that are not in use for some other function, investigate  
the possibility of a defective TDM Bus as described in Step 5.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-438  
Table 3-187. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
40  
41  
2000  
2003  
2004  
FAIL  
(cont’d.)  
6. If the result of Test #110 is FAIL and the result of Test #111 is PASS for  
the target DATA-CHL, then the most likely problem is that the TDM Bus or  
Tone-Clock circuit pack is defective.  
■
Check for the existence of TDM Bus (TDM-BUS) and/or Tone-Clock  
circuit pack (TONE-BD, TONE-PT, and TDM-CLK) errors and alarms.  
If they exist:  
a. Refer to the corresponding Maintenance documentation to  
clear the errors and alarms.  
b. Repeat the test.  
■
If TDM Bus (TDM-BUS) and/or Tone-Clock circuit pack (TONE-BD,  
TONE-PT, and TDM-CLK) errors and alarms do not exist, investigate  
the possibility that the target DATA-CHL, or the Processor circuit pack  
is defective as described in Step 6.  
7. If the result of Test #110 is either PASS or FAIL and the result of test #111  
is FAIL for the target DATA-CHL, then the most likely problem is that the  
target DATA-CHL is defective, or the Processor circuit pack is defective.  
■
Busyout all functions that are using the Data Channels (DATA-CHLs).  
!
CAUTION:  
All functions must be busied out because Test #107 is destructive and  
terminates all established connections over the DATA-CHLs.  
■
Issue the test data-module <ext> long for the target DATA-CHL.  
Note the test results for Test #107 and #108.  
a. If the result of Test #107 is FAIL, then the Processor circuit pack  
is defective.  
■
■
Replace the Processor circuit pack at your earliest convenience.  
After the Processor circuit pack has been replaced, its Time-of-Day  
clock must be set using the set time command.  
Repeat the test.  
b. If the result of Test #107 is PASS and the result of Test #108 is  
FAIL, then the Processor circuit pack is defective.  
■
■
Although all DATA-CHLs are unusable, the SW-CTL is still  
operational. Based on the customer’s use of DATA-CHLs, replace the  
Processor circuit pack at the customer’s convenience. After the  
Processor circuit pack has been replaced, its Time-of-Day clock must  
be set using the set time command.  
Repeat the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-439  
Table 3-187. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
40  
41  
FAIL  
(cont’d.)  
If the result of Test #107 is PASS and the result of Test #108 is PASS, then the  
target DATA-CHL is defective.  
2000  
2003  
2004  
■
Issue the remove data-module <ext> for the target DATA-CHL to  
remove it from operation.  
■
Replace the Processor circuit pack at your earliest convenience.  
After the Processor circuit pack has been replaced, its Time-of-Day  
clock must be set using the set time command.  
8. Restore any busied out CDR, Journal Printer, System Printer, or PMSLink  
to service before moving on to another activity.  
PASS  
The target DATA-CHL, Processor circuit pack, TDM Bus (TDM-BUS), and  
Tone-Clock circuit pack (TONE-BD, TONE-PT, TDM-CLK) are functioning.  
Connections can be established over the DATA-CHLs.  
Data Channel Crosstalk Test (#110)  
This test verifies the integrity of the entire DATA-CHL, that is, the software, dual  
port RAM, and hardware that composes it. However, unlike the Remote  
Maintenance Loop Around Test (#109), this test only involves the single  
DATA-CHL that is the target of the test. A loop around connection is established  
over the TDM Bus from the DATA-CHL back to itself. Data is looped over the  
connection in each direction, that is, the DATA-CHL is tested as both a sender of  
data and a receiver of data. The test checks that the data received by the  
DATA-CHL is the same as the data that was sent by the DATA-CHL.  
Because it establishes a loop around connection from the Network Control  
DATA-CHL back to itself across the TDM Bus, this test does more than just verify  
the integrity of the target DATA-CHL. It also verifies the integrity of the TDM Bus  
and Tone-Clock circuit pack (by sending and receiving data).  
If this test aborts or fails, it is impossible to determine from this test alone whether  
the target DATA-CHL is defective or if the problem lies with the TDM Bus, or  
Tone-Clock circuit pack. The results of running Tests #107, #108, and #111 on the  
DATA-CHL can be used to determine whether the target DATA-CHL is defective.  
NOTE:  
If an Error Code is encountered that recommends that an CDR Link, System  
Printer Link, PMS Log Printer, Wakeup-Log Printer Link, and/or PMS Link be  
busied out, restore each busied-out link to service according to the  
PRI-CDR/SEC-CDR (PRI-CDR Link), SYS-PRNT, or PMS-LINK Maintenance  
documentation, respectively, before concluding work on the problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-440  
Table 3-188. TEST #110 Data Channel Crosstalk Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
4
ABORT  
For this test, an Error Code of 4 can have one of two different meanings:  
a. The target DATA-CHL is busy and, therefore, not available for use.  
b. Internal system error  
Determine if the target DATA-CHL is in use for some other function (that is,  
CDR Link, System Printer Link, Journal Printer Link, PMS Link, or secondary  
administration terminal connection) as described previously in the ‘‘Status of  
Data Channels’’ section. If so, check for errors on the function that is using the  
DATA-CHL. If there are no errors, there is a high probability that the  
DATA-CHL is not defective.  
Proceed with the remaining steps only if it is necessary to completely test  
the target DATA-CHL:  
1. If the target DATA-CHL is in use for some other function, busyout the  
function (CDR Link, System Printer Link, Journal Printer Link, PMS Link) or  
the DATA-CHL (secondary administration terminal connection only).  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
3. Restore any busied out CDR, System Printer, Journal Printer, or PMS Link  
to service before moving on to another activity.  
40  
70  
75  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-441  
Table 3-188. TEST #110 Data Channel Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
For this test, an Error Code of 1000 can have one of several different  
meanings:  
a. The target DATA-CHL is busy and, therefore, not available for use.  
b. System resources required to run this test are not available.  
c. Internal system error  
Determine if the target DATA-CHL is in use for some other function (that is,  
CDR Link, System Printer Link, Journal Printer Link, PMS Link, or secondary  
administration terminal connection) as described previously in the ‘‘Status of  
Data Channels’’ section. If so, check for errors on the function that is using the  
DATA-CHL. If there are no errors, there is a high probability that the  
DATA-CHL is not defective.  
Proceed with the remaining steps only if it is necessary to completely test  
the target DATA-CHL:  
1. If the target DATA-CHL is in use for some other function, busyout the  
function (PRI-CDR/SEC-CDR, SYS-PRNT, PMS-PRNT/JNL-PRNT,  
PMS-LINK) or the DATA-CHL (secondary administration terminal  
connection only).  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
3. Restore any busied out PRI-CDR/SEC-CDR, SYS-PRNT,  
PMS-PRNT/JNL-PRNT, PMS-LINK MOs to service before moving on to  
another activity.  
1002  
ABORT  
For this test, an Error Code of 1002 can have one of two different meanings:  
1. System resources required to run this test are not available.  
2. Internal system error  
1006  
1016  
ABORT  
ABORT  
System resources required to run this test are not available.  
Resources for the test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Test disabled via software patch.  
1018  
2000  
2003  
ABORT  
ABORT  
ABORT  
Resources for the test are not available.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-442  
Table 3-188. TEST #110 Data Channel Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
14  
16  
40  
2000  
2003  
2004  
FAIL  
In the case of Error Code 40, the Crosstalk Test failed because the data  
received over the connection did not match the data sent over the connection  
(data was corrupted). In the case of Error Code 2000, 2003, and 2004, the  
crosstalk test failed because the data looped over the connection was not  
received (data was lost).  
1. Determine which of the DATA-CHLs are in use for some other function  
(that is, CDR Link, System Printer Link, Journal Printer Link, PMS Link, or  
secondary administration terminal connection) as described previously in  
the ‘‘Status of Data Channels’’ section.  
2. Note the test result for Test #111 in the Short Test Sequence for the target  
DATA-CHL and refer to Steps 3 and/or 4 to determine the appropriate  
actions to take based on those results.  
3. If the result of Test #111 is PASS, then the most likely problem is that the  
TDM Bus or Tone-Clock circuit pack is defective.  
a. Check for the existence of TDM Bus (TDM-BUS) and/or Tone-Clock  
circuit pack (TONE-BD, TONE-PT, and TDM-CLK) errors and alarms. If  
they exist:  
1. Refer to the corresponding Maintenance documentation to clear  
the errors and alarms.  
2. Repeat the test.  
b. If TDM Bus (TDM-BUS) and/or Tone-Clock circuit pack (TONE-BD,  
TONE-PT, and TDM-CLK) errors and alarms do not exist, investigate  
the possibility that the target DATA-CHL, or the Processor circuit pack  
is defective as described in Step 4.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-443  
Table 3-188. TEST #110 Data Channel Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
14  
16  
40  
FAIL  
(cont’d.)  
4. If the result of Test #111 is FAIL, then the most likely problem is that the  
target DATA-CHL is defective, or the Processor circuit pack is defective.  
Busyout all functions that are using the Data Channels (DATA-CHLs).  
2000  
2003  
2004  
!
CAUTION:  
All functions must be busied out because Test #107 is destructive and  
terminates all established connections over the DATA-CHLs.  
a. Issue the test data-module <ext> long command for the target  
DATA-CHL. Note the test results for Tests #107 and #108.  
1. If the result of Test #107 is FAIL, then the Processor circuit pack  
is defective.  
(a).Replace the Processor circuit pack at your earliest  
convenience. After the Processor circuit pack has been  
replaced, its Time-of-Day clock must be set using the set  
time command.  
(b).Repeat the test.  
2. If the result of Test #107 is PASS and the result of Test #108 is  
FAIL:  
(a).Although all DATA-CHLs are unusable, the SW-CTL is still  
operational. Based on the customer’s use of DATA-CHLs,  
replace the Processor circuit pack at the customer’s  
convenience. After the Processor circuit pack has been  
replaced, its Time-of-Day clock must be set using the set  
time command.  
(b).Repeat the test.  
3. If the result of Test #107 is PASS and the result of Test #108 is  
PASS, then the target DATA-CHL is defective.  
(a).Issue the remove data-module <ext> command for the  
target DATA-CHL to remove it from operation.  
(b).Replace the Processor circuit pack at your earliest  
convenience. After the Processor circuit pack has been  
replaced, its Time-of-Day clock must be set using the set  
time command.  
4. Restore any busied out function (PRI-CDR/SEC-CDR, SYS-PRNT,  
PMS-PRNT/JNL-PRNT, PMS-LINK) to service before moving on  
to another activity.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-444  
Table 3-188. TEST #110 Data Channel Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
PASS  
The target DATA-CHL, Processor circuit pack, TDM Bus (TDM-BUS), and  
Tone-Clock circuit pack (TONE-BD, TONE-PT, TDM-CLK) are functioning.  
Connections can be established over the target DATA-CHL.  
Data Channel Local Loop Back Test (#111)  
This test verifies the integrity of the dual port RAM that is shared between the  
software and hardware that composes the DATA-CHL. The dual port RAM is  
placed in local loop back mode such that data to be sent by the DATA-CHL is  
instead looped back to be received by the DATA-CHL. The loop back is done  
within the dual port RAM, that is, the data is never sent over the TDM Bus. The  
test checks that the data received by the DATA-CHL is the same as the data that  
was sent by the DATA-CHL.  
NOTE:  
If an Error Code is encountered that recommends that an CDR Link, System  
Printer Link, PMS Log Printer, Wakeup-Log Printer, and/or PMS Link be  
busied out, restore each busied-out link to service according to the  
PRI-CDR/SEC-CDR (PRI-CDR Link), SYS-PRNT (System Printer Link),  
PMS-PRNT/JNL-PRNT (PMS Printer Link), or PMS-LINK (Property  
Management System Link) Maintenance documentation, respectively,  
before concluding work on the problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-445  
Table 3-189. TEST #111 Data Channel Local Loop Back Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
4
ABORT  
For this test, an Error Code of 4 can have one of two different meanings:  
b. The target DATA-CHL is busy and, therefore, not available for use.  
c. Internal system error  
Determine if the target DATA-CHL is in use for some other function (that is,  
CDR Link, System Printer Link, Journal Printer Link, PMS Link, or secondary  
administration terminal connection) as described previously in the ‘‘Status  
of Data Channels’’ section. If so, check for errors on the function that is  
using the DATA-CHL. If there are no errors, there is a high probability that  
the DATA-CHL is not defective. Proceed with the remaining steps only if it  
is necessary to completely test the target DATA-CHL.  
1. If the target DATA-CHL is in use for some other function, busyout the  
function (PRI-CDR/SEC-CDR, SYS-PRNT, PMS-PRNT/JNL-PRNT,  
PMS-LINK) or the DATA-CHL (secondary administration terminal  
connection only).  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
3. Restore any busied out PRI-CDR/SEC-CDR, SYS-PRNT,  
PMS-PRNT/JNL-PRNT, PMS-LINK MOs to service before moving on to  
another activity.  
40  
70  
75  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-446  
Table 3-189. TEST #111 Data Channel Local Loop Back Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
For this test, an Error Code of 1000 can have one of several different  
meanings:  
a. The target DATA-CHL is busy and, therefore, not available for use.  
b. System resources required to run this test are not available.  
c. Internal system error  
Determine if the target DATA-CHL is in use for some other function (that is,  
CDR Link, System Printer Link, Journal Printer Link, PMS Link, or secondary  
administration terminal connection) as described previously in the ‘‘Status  
of Data Channels’’ section. If so, check for errors on the function that is  
using the DATA-CHL. If there are no errors, there is a high probability that  
the DATA-CHL is not defective.  
Proceed with the remaining steps only if it is necessary to completely  
test the target DATA-CHL:  
1. If the target DATA-CHL is in use for some other function, busyout the  
function (PRI-CDR/SEC-CDR, SYS-PRNT, PMS-PRNT/JNL-PRNT,  
PMS-LINK) or the DATA-CHL (secondary administration terminal  
connection only).  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
3. Restore any busied out PRI-CDR/SEC-CDR, SYS-PRNT,  
PMS-PRNT/JNL-PRNT, PMS-LINK MOs to service before moving on to  
another activity.  
1006  
1016  
ABORT  
ABORT  
For this test, an Error Code of 1006 can have one of several different  
meanings:  
a. System resources required to run this test are not available.  
b. Internal system error. Retry the command at 1-minute intervals a  
maximum of 5 times.  
Resources for the test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Test disabled via software patch.  
1018  
2000  
2003  
ABORT  
ABORT  
ABORT  
Internal system error  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-447  
Table 3-189. TEST #111 Data Channel Local Loop Back Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
40  
FAIL  
In the case of Error Code 40, the Local Loop Back Test failed because the  
data received over the connection did not match the data sent over the  
connection (data was corrupted). In the case of Error Code 2000, 2003,  
and 2004, the Local Loop Back Test failed because the data looped over  
the connection was not received (data was lost).  
2000  
2003  
2004  
1. Determine which of the DATA-CHLs are in use for some other function  
(that is, PRI-CDR/SEC-CDR, SYS-PRNT, PMS-PRNT/JNL-PRNT,  
PMS-LINK or secondary administration terminal connection) as  
described previously in the ‘‘Status of Data Channels’’ section.  
2. The most likely problem is that the target DATA-CHL is defective.  
Busyout all functions that are using the Data Channels (DATA-CHLs).  
!
CAUTION:  
All functions must be busied out because Test #107 is destructive  
and terminates all established connections over the DATA-CHLs.  
3. Issue the test data-module <ext> long command for the target  
DATA-CHL. Note the test results for Tests #107 and #108.  
a. If the result of Test #107 is FAIL, then the Processor circuit pack is  
defective.  
1. Replace the Processor circuit pack at your earliest  
convenience. After the Processor circuit pack has been  
replaced, its Time-of-Day clock must be set using the set time  
command.  
2. Repeat the test.  
b. If the result of Test #107 is PASS and the result of Test #108 is FAIL:  
1. Although all DATA-CHLs are unusable, the SW-CTL is still  
operational. Based on the customer’s use of DATA-CHLs,  
replace the Processor circuit pack at the customer’s  
convenience. After the Processor circuit pack has been  
replaced, its Time-of-Day clock must be set using the set time  
command.  
2. Repeat the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CHL (Data Channel)  
3-448  
Table 3-189. TEST #111 Data Channel Local Loop Back Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
FAIL  
c. If the result of Test #107 is PASS and the result of Test #108 is PASS,  
then the target DATA-CHL is defective.  
1. Issue the remove data-module command.  
■
Replace the Processor circuit pack at your earliest convenience.  
After the Processor circuit pack has been replaced, its  
Time-of-Day clock must be set using the set time command.  
2. Restore any busied out function (PRI-CDR/SEC-CDR,  
SYS-PRNT, PMS-PRNT/JNL-PRNT, PMS-LINK) to service  
before moving on to another activity.  
PASS  
The target DATA-CHL is functioning. Connections can be established over  
the target DATA-CHL.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CON (Network Control Driver)  
3-449  
DATA-CON (Network Control Driver)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
DATA-CON  
MINOR  
none  
Network Control Driver  
The TN798 Processor circuit pack contains the following objects: the SW-CTL  
(Switch Control), four DATA-CHLs (Data Channels), the DATA-CON (Network  
Control Driver), and the generic hardware that interfaces with the TDM Bus  
(DATA-BD). The DATA-CON (Network Control Driver) is the subject of this section.  
The DATA-CHLs (Network Control Channels) are also described.  
Together the 4 DATA-CHLs and the DATA-CON provide a data communications  
interface that allows DTE equipment connected to port circuit packs to  
communicate with software applications running on the system. The DATA-CON  
represents the interface to the control channel of the TDM Bus. Each DATA-CHL  
represents a dial-up/dial-out asynchronous communication port that interfaces to  
the TDM Bus. The DATA-CON supports the signaling required to establish and  
tear down a connection between the terminal equipment and a software  
application. Data is transported between the terminal equipment and the  
software over the connection established over the DATA-CHL.  
From an external (user) point of view, the DATA-CON is not directly accessible via  
a system technician command; that is, there is no object command word that  
represents it. Instead, the DATA-CON is tested under the guise of the DATA-CHLs  
that it controls. The test data-module <ext> [short | long] command tests the  
DATA-CON along with the DATA-CHL designated by <ext> but all Test Results  
are associated with the DATA-CHL Maintenance Name.  
From an internal (system software) point of view, the DATA-CON uses the same  
set of tests as the DATA-CHLs. Therefore, the DATA-CON assumes the same  
Error Type and Aux Data values as the DATA-CHLs in the Hardware Error Log. It  
is also alarmed at the same Alarm Level (that is, MINOR, ON BOARD) in the  
Alarm Log. In both logs, the Maintenance Name is DATA-CON.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DATA-CON (Network Control Driver)  
3-450  
Error Log Entries and Test to Clear Values  
Table 3-190. Network Control Driver Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Test to Clear  
Value (a)  
Associated Test  
1
0
0
Any  
Any  
Any  
ON  
ON  
none  
1
Local Loop Back Test (#111)  
MINOR  
MINOR  
none  
none  
257  
Any  
Any  
Remote Maintenance Loop Around  
Test (#109)  
513  
769  
Crosstalk Test (#110)  
MINOR  
MINOR  
ON  
ON  
none  
none  
Dual Port RAM Test (#108)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Note:  
a. As previously described, the DATA-CON is not directly accessible via a  
system technician command so there is no Test to Clear value that can be  
used to directly clear errors and alarms raised against the DATA-CON.  
However, since the DATA-CON and the DATA-CHLs share the same set of  
tests (that is, test the same set of hardware, firmware, and software),  
DATA-CON errors and alarms are accompanied by DATA-CHL errors and  
alarms.  
Therefore, the strategy to clear DATA-CON errors and alarms is to first clear all  
DATA-CHL errors and alarms. After DATA-CHL errors and alarms have been  
cleared, allow about 60 minutes for maintenance software to run internally and to  
automatically clear the DATA-CON errors and alarms.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Because the DATA-CON uses the same set of tests as the DATA-CHLs, refer to  
the "System Technician-Demanded Tests: Descriptions and Error Codes" in the  
DATA-CHL (Network Control Data Channel) Maintenance documentation for a  
description of the tests and their associated error codes.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DAT-LINE (Data Line)  
3
3-451  
DAT-LINE (Data Line)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run1  
test port PCSSpp l  
Full Name of MO  
Data Line  
DAT-LINE  
DAT-LINE  
MINOR  
WARNING  
test port PCSSpp sh  
Data Line  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example,  
A, B, or C); and SSis the address of the slot in the carrier where the circuit pack is located  
(for example, 01, 02, ..., etc.).  
The TN726 Data Line circuit pack is a port circuit that provides connectivity from  
the system to asynchronous CPE having RS232-compatible serial interfaces.  
There are eight data lines (DAT-LINEs) on the Data Line circuit pack. If there are  
errors associated with the DT-LN-BD (Data Line Circuit Pack), refer to the XXX-BD  
(Common Port Circuit Pack) Maintenance documentation.  
Data Lines are administered via the administration terminal add data-module  
command. The data module type is data-line. The list data-module command  
lists all administered data modules in the system.  
The TN750 Announcement circuit pack has one Data Line on it. The Data Line is  
used for saving and restoring announcements. For a description of this feature,  
refer to ANN-BD (Announcement Circuit Pack) Maintenance documentation.  
Also, if there are errors associated with the Announcement circuit pack, refer to  
the ANN-BD Maintenance documentation.  
NOTE:  
If the tests for the Data Line in question pass and there are still  
user-reported problems, there is probably an external problem. Test the  
ADU, following the procedures outlined in User Manual Z3A Asynchronous  
Data Unit, 555-401-701. If the ADU appears to be working properly, check  
the external wiring and, finally, check the customer equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DAT-LINE (Data Line)  
3
3-452  
Error Log Entries and Test to Clear Value  
Table 3-191. Data Line Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Any  
Alarm Level  
Any  
Test to Clear Value  
test port PCSSpp sh r 1  
test port PCSSpp sh r 2  
1
0
1
0
Any  
Digital Loop Around  
Test (#171)  
MINOR  
ON  
15(a)  
Any  
0
Audit Update Test  
(#36)  
18  
busyout port PCSSpp  
None  
WARNING  
WARNING  
MINOR  
OFF  
ON  
release port PCSSpp  
test port PCSSpp sh  
test port PCSSpp l r 2  
130 (b)  
257  
Conference Circuit  
Test (#7)  
ON  
513  
NPE Crosstalk Test  
(#6)  
MINOR  
ON  
test port PCSSpp l r 2  
769(a)  
Any (c)  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
Notes:  
a. This is a software audit error that does not indicate any hardware  
malfunction. Run the Short Test Sequence and investigate errors (if any).  
b. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
c. This error is logged when the Data Line circuit pack finds an error with the  
transmit/receive circuitry of an administered Data Line on circuit pack  
insertion. Perform the following procedure:  
1. Issue the busyout board PCSS command to busyout the Data Line  
circuit pack on which this port resides.  
2. Issue the reset board PCSS command. Check the Hardware Error  
Log to determine if Error Type 769 is logged again for the DAT-LINE  
MO.  
NOTE:  
When displaying errors, set the Active Alarms Onlyfield  
to n.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DAT-LINE (Data Line)  
3
3-453  
If Error Type 769 reappears, replace the DAT-LINE circuit pack. If  
Error Type 769 does not reappear, proceed to Step 3.  
3. Issue the release board PCSS command to release the Data Line  
circuit pack on which this port resides.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Digital Loop Around Test, for example, you may also clear errors generated from  
other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Digital Loop Around Test (#171)  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
X
X
X
X
ND  
Conference Circuit Test (#7)  
Audit Update Test (#36)  
ND  
X
ND  
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
The NPE Crosstalk Test verifies that this port’s NPE channel talks on the selected  
time slot and never crosses over to time slots reserved for other connections. If  
the NPE is not working correctly, one-way and noisy connections may be  
observed. This test is usually part of a port’s Long Test Sequence and takes  
about 20 to 30 seconds to complete.  
Table 3-192. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use on a valid call. Use status data-module to determine when the  
port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DAT-LINE (Data Line)  
3
3-454  
Table 3-192. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1001  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to “TDM-BUS” to diagnose TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Resolve any TTR-LEV errors.  
2. Resolve any TONE-PT errors.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
1020  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use status  
data-module to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test did not run due to an already existing error on this port (Error Type  
769).  
1. Refer to the procedure for Error Type 769. If Error Type 769 still occurs  
on this port, replace the circuit pack.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Any  
FAIL  
The NPE of the tested port was found to be transmitting in error. This  
causes noisy and unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated using other port tests, examining the  
ADU, external wiring, and customer equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DAT-LINE (Data Line)  
3
3-455  
Conference Circuit Test (#7)  
The Conference Circuit Test verifies that the NPE channel for the port being  
tested can correctly perform the conferencing function. The NPE is instructed to  
listen to several different tones and conference the tones together. The resulting  
signal is then measured by a Tone Detector port. If the level of the tone is within a  
certain range, the test passes.  
Table 3-193. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use on a valid call. Use status data-module to determine when the  
port is available for testing.  
1004  
1020  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use status  
data-module to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test did not run due to an already existing error on this port (Error Type  
769).  
1. Refer to the procedure for Error Type 769. If Error Type 769 still occurs  
on this port, replace the circuit pack.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The conference circuit test failed (possible off-board problem).  
1. Busyout and release the port (data line), and then retest.  
2. Replace the circuit pack if the test continues to fail.  
Any  
FAIL  
PASS  
The port can correctly conference multiple connections. User-reported  
troubles on this port should be investigated using other port tests,  
examining the ADU, external wiring, and customer equipment.  
Audit Update Test (#36)  
This audit makes sure that the hardware state of the Data Line is consistent with  
the system translations. When this audit is run, the port is queried for the  
switchhook state, and the software state is updated according to the returned  
value. Also, the data line options are sent down to the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DAT-LINE (Data Line)  
3
3-456  
Table 3-194. TEST #36 Audit Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2. Escalate the problem if the test continues to abort.  
1006  
ABORT  
The test did not run due to an already existing error on this port (Error Type  
769).  
1. Refer to the procedure for Error Type 769. If Error Type 769 still occurs  
on this port, replace the circuit pack.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
7
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
The hardware port state is consistent with the software state. User-reported  
troubles on this port should be investigated using other port tests,  
examining the ADU, external wiring, and customer equipment.  
Digital Loop Around Test (#171)  
The Digital Loop Around Test checks the Data Line’s ability to transmit and  
receive data on the TDM Bus. Data is sent through Data Channel 3 (data channel  
port 3) over the TDM Bus, internally looped through the Data Line back onto the  
TDM Bus, and received again by Data Channel 3.  
If data channel 3 is in use or not administered, this test aborts. This test may fail if  
Network Control Data Channel 3 is not functioning properly. If there are any  
DATA-CHL errors in the Error Log, refer to the DATA-BD (Data Channel Processor  
circuit pack) Maintenance documentation to clear them up first. This test passes  
regardless of any customer equipment that may be connected to the port, as  
long as the port is not in use by the equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DAT-LINE (Data Line)  
3
3-457  
Table 3-195. TEST #171 Digital Loop Around Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use on a valid call. Use status data-module to determine when the  
port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Data Channel 3 is not administered. This port is required to run this test.  
1005  
1007  
ABORT  
1. Verify that data channel 3 is not administered with the list data-module  
command. Administer data channel 3 with the add data-module  
command, and run this test again.  
1016  
1020  
ABORT  
ABORT  
Data Channel 3 is busy. The port may be in use on a valid call. Use status  
data-module to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test did not run due to an already existing error on this port (Error Type  
769).  
1. Reseat the circuit pack and look in the Error Log. If Error Type 769 still  
occurs on this port, replace the circuit pack.  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2. If the test continues to abort, escalate the problem.  
2003  
ABORT  
Failed to receive an off-hook from the Data Line.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Failed to receive an off-hook from the Data Channel.  
2004  
2005  
ABORT  
ABORT  
The handshake between the data channel and the data line port failed.  
1. Look for DATA-CHL errors in the Error Log. If present, refer to DATA-BD  
(Data Channel Processor circuit pack) Maintenance documentation.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
3. If the test still aborts, replace the circuit pack.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DAT-LINE (Data Line)  
3
3-458  
Table 3-195. TEST #171 Digital Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
FAIL  
The test failed because the data received did not match the data sent. This  
would indicate that there is a fault somewhere in the transmit/receive path  
to the TDM Bus, which probably results in data corruption over this port.  
This test may fail if Data Channel 3 is not functioning properly.  
1. Look for DATA-CHL errors in the Error Log. If present, refer to DATA-BD  
(Data Channel Processor circuit pack) Maintenance documentation.  
2. Repeat this test.  
3. If the test fails again, replace the Data Line circuit pack.  
The test failed waiting for the transmitted data to be looped back.  
2000  
FAIL  
1. Look for DATA-CHL errors in the Error Log. If present, refer to DATA-BD  
(Data Channel Processor circuit pack) Maintenance documentation.  
2. Repeat this test.  
3. If the test fails again, replace the Data Line circuit pack.  
PASS  
The port can correctly transmit/receive data. User-reported troubles on this  
port should be investigated by examining the ADU, external wiring, and  
customer equipment.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DETR-BD (International Version)  
3-459  
DETR-BD (International Version)  
MO Name (in  
Alarm Log)  
Initial Command to  
1
Alarm Level  
MINOR  
Run  
Full Name of MO  
DETR-BD  
DETR-BD  
test board PCSS  
test board PCSS  
Tone Detector Circuit Pack  
Tone Detector Circuit Pack  
WARNING  
1. Where P is the port network number (1 for PPN); C is the carrier number (for example, A, B, or  
C); SS is the address of the slot in the carrier where the circuit pack is located (for example, 01,  
02, ..., etc.).  
The companding mode of the DETR-BD circuit pack must match the  
administered mode for the system for proper tone detection. The companding  
mode is administered on the System-Parameters Country-Options form. Refer to  
DEFINITY Enterprise Communications Server Administrator’s Guide.  
For all DETR-BD circuit pack level errors, refer to ‘‘XXX-BD (Common Port Circuit  
Pack)’’ Maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-BD (Direct Inward Dial Trunk Circuit Pack)  
3-460  
DID-BD (Direct Inward Dial Trunk  
Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board PCSS sh  
test board PCSS sh  
Full Name of MO  
DID-BD  
DID-BD  
MIN  
WRN  
Direct Inward Dial Trunk Circuit Pack  
Direct Inward Dial Trunk Circuit Pack  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or  
C); and SS is the address of the slot in the carrier where the circuit pack is located (for example,  
01, 02, ..., etc.).  
Refer to XXX-BD (Common Port Circuit Pack) Maintenance documentation for  
circuit pack level errors. See also DID-TRK (DID Trunk) Maintenance  
documentation for related trunk information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-DS1 (DS1 DID Trunk)  
3-461  
DID-DS1 (DS1 DID Trunk)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
1
DID-DS1  
DID-DS1  
DID-DS1  
MAJOR  
test trunk <grp>/<mbr> l Direct Inward Dial Trunk  
test trunk <grp>/<mbr> l Direct Inward Dial Trunk  
MINOR  
WARNING  
test trunk <grp>/<mbr>  
Direct Inward Dial Trunk  
1. A major alarm on a trunk indicates that alarms on these trunks are not downgraded by  
the set options command and that at least 75 percent of the trunks in this trunk group  
are alarmed.  
The DID-DS1 trunk provides a digital DID trunk from a CO switch into the system  
through a DS1 link. A 24 channel DS1 link can support up to 24 DID-DS1 trunk  
calls simultaneously. A 32 channel DS1 link can support up to 30 DID-DS1 trunk  
calls simultaneously. A DID-DS1 trunk can be used for both voice and data  
communications with appropriate DS1 signaling mode (for example, common  
channel signaling). Only the TN767 and TN464 DS1 Interface circuit packs  
support the DID-DS1 trunk call processing signalings, wink-start, and  
immediate-start.  
DID-DS1 trunk maintenance provides a means to maintain a DID trunk on a port  
of DS1 Interface circuit pack. Information included covers the in-line errors log,  
initialization tests, periodic tests, system technician demand tests, and alarms  
escalation and elimination. Two trunk service states are specified in the DID-DS1  
trunk maintenance. They are: out-of-service, the trunk is in a deactivated state  
and can’t be used for incoming calls; in-service, the trunk is in an activated state  
and can be used for incoming calls. If the DS1 Interface circuit pack is  
out-of-service, then all trunks on the DS1 Interface circuit pack are put into  
out-of-service state and a Warning alarm is raised.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-196. DID-DS1 Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test trunk <grp>/<mbr> sh r 1  
1 (a)  
Any  
Any  
15 (b)  
Port Audit and  
Update Test (#36)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-DS1 (DS1 DID Trunk)  
3-462  
Table 3-196. DID-DS1 Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
18 (c)  
WARNING  
WARNING  
OFF  
ON  
release trunk <grp>/mbr>  
test trunk <grp>/<mbr>  
130 (d)  
257 (e)  
None  
57474  
57473  
2
513 (f)  
769 (g)  
1281  
57392  
57393  
None  
None  
MIN/MAJ  
OFF  
OFF  
ON  
2
MIN/MAJ  
Conference Circuit  
Test (#7)  
MAJ/MIN/  
test trunk <grp>/<mbr> l  
test trunk <grp>/<mbr> l  
test board PCSS l  
3
WRN  
1537  
NPE Crosstalk Test  
(#6)  
MAJ/MIN/  
WRN  
ON  
3
1793 (h)  
2305(i)  
3840 (j)  
ON  
2
50944  
None  
MIN/MAJ  
OFF  
Port Audit and  
Update Test (#36)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. This alarm will only be raised when the System-Parameter Country form has the Base Tone Generator  
field set to 4 (Italy). This alarm will be a MINOR alarm unless 75% or more trunks in this trunk group are  
out of service, then the alarm will be upgraded to a MAJOR alarm.  
3. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the set  
options command. If the Minor alarm is not downgraded by the set options values, the Minor alarm  
is upgraded to a Major alarm if 75 percent of the trunks in this trunk group are alarmed.  
Notes:  
a. DS1 Interface circuit pack detects a hardware error. The Aux Data field  
contains the Error Type: 57476, on-hook before wink; 57477, on-hook  
before ready to receive digits; 57485, wink too short for valid signal.  
b. This is a software audit error that does not indicate any hardware  
malfunction. Run the Short Test Sequence and investigate errors (if any).  
c. System Technician has busied out the trunk to out-of-service state. No  
calls can be made on this trunk.  
d. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-DS1 (DS1 DID Trunk)  
3-463  
e. DS1 Interface circuit pack detects a hardware error. The Aux Data field  
contains the Error Type: 57474, rotary dial rate above 12 pulses per  
second; 57473, rotary dial rate below eight pulses per second.  
f. DS1 Interface circuit pack detects a hardware error. The Aux Data field  
contains the Error Type: 57392, no external release on PBX disconnect.  
g. DS1 Interface circuit pack detects a hardware error. The Aux Data field  
contains the Error Type: 57393, belated external release on PBX  
disconnect.  
h. DS1 Interface circuit pack is out-of-service. Look for DS1-BD errors in  
Hardware Error Log. Refer to the DS1-BD (DS1 Trunk Circuit Pack)  
Maintenance documentation for details.  
i. Error Type 2305—This error indicates that a signaling change was  
detected by the PBX trunk circuit pack which is inconsistent with the  
present state of the trunk.  
j. Port Audit and Update Test (#36) failed due to an internal system error.  
Enter status trunk command to verify the status of the trunk. If the trunk is  
out-of-service, then enter the release trunk command to put it back to  
in-service. Retry the test command.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order they are presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the NPE  
Crosstalk Test, for example, you may also clear errors generated from other tests  
in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
Conference Circuit Test (#7)  
X
X
ND  
Port Audit and Update Test (#36)  
ND  
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per-port basis. The NPECrosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is usually only part of a port’s Long Test Sequence  
and takes about 20 to 30 seconds to complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-DS1 (DS1 DID Trunk)  
3-464  
Table 3-197. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
System resources required to run this test were not available.  
1000  
The port may be busy with a valid call. Use the display port PCSSpp  
command to determine the trunk group/member number of the port. Use  
the status trunk command to determine the service state of the port. If the  
service state indicates that the port is in use, then the port is unavailable  
for certain tests. You must wait until the port is idle before retesting.  
1. If the port status is active but the port is not in use (no calls), check  
the error log for error type 1025 (see the Error Log table for a  
description of this error and required actions). The port may be locked  
up.  
2. If the port status is idle, retry the command at 1 minute intervals for a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM BUS error. Refer to TDM-BUS (TDM Bus) Maintenance  
documentation to diagnose any active TDM Bus errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
(TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-DS1 (DS1 DID Trunk)  
3-465  
Table 3-197. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1004  
ABORT  
The port was seized by a user for a valid call. Use the display port  
PCSSpp command to determine the trunk group/member number of the  
port. Use the status trunk command to determine the service state of the  
port. If the service state indicates that the port is in use, then the port is  
unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. If the port status is idle, retry the command at 1 minute intervals for a  
maximum of 5 times.  
1020  
ABORT  
The test did not run due to a previously existing error on the specific port  
or a more general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit  
pack and attempt to diagnose the previously existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2053  
ABORT  
At least one of the following errors is found on the DS1 circuit pack:  
1281—Loss of signal, 1793—Blue Alarm, 2049—Red Alarm, 2305—Yellow  
Alarm, 1537—Hyperactivity.  
Look for the above error types in the Hardware Error Log and follow the  
procedures given in the appropriate DS1-BD or UDS1-BD maintenance  
documentation for the listed error types.  
ANY  
FAIL  
The test failed. This can be due to on-board or off-board problems.  
Off-board problems of concern include EXP-PN and EXP-INTF faults,  
TDM-BUS faults, and faults associated with the tone detectors/tone  
generators. Clear all off-board problems before replacing the board. Keep  
in mind that a TDM-BUS problem is usually the result of a faulty board  
connected to the backplane or bent pins on the backplane.  
1. Look for EXP-PN and/or EXP-INTF errors in the error log. If present,  
refer to the EXP-PN and the EXP-INTF Maintenance documentation.  
2. Look for TDM-BUS errors in the error log. If present, refer to the  
TDM-BUS Maintenance documentation.  
3. Look for TONE-BD and/or TONE-PT errors in the error log. If present,  
refer to the TONE-BD and the TONE-PT Maintenance documentation.  
4. Retest when the faults from steps 1, 2, and 3 are cleared. Replace the  
board only if the test fails.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated using other port tests and by  
examining station, trunk, or external wiring.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-DS1 (DS1 DID Trunk)  
3-466  
Table 3-197. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the lIst  
config command and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to see that there is a valid board inserted.  
Conference Circuit Test (#7)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per-port basis. The Conference Circuit Test verifies that the NPE channel for the  
port being tested can correctly perform the conferencing function. The NPE is  
instructed to listen to several different tones and conference the tones together.  
The resulting signal is then measured by a Tone Detector port. If the level of the  
tone is within a certain range, the test passed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-DS1 (DS1 DID Trunk)  
3-467  
Table 3-198. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test were not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the trunk group/member number of the port. Use the status trunk  
command to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain tests.  
You must wait until the port is idle before retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 1025 (see the Error Log table for a description of  
this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1002  
1003  
ABORT  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions, or it may have time slots out of service due to  
TDM-BUS errors. Refer to the TDM-BUS (TDM bus) Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic  
and the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
The system could not allocate a tone receiver for the test. The system may be  
oversized for the number of tone detectors present or some of the tone  
detectors may be out of service. Issue the list measurements tone-receiver  
command to display basic information about the system’s tone receivers.  
1. Look for TTR-LEV errors in the error log. If present, refer to the TTR-LEV  
Maintenance documentation.  
2. Look for TONE-PT errors in the error log. If present, refer to the TONE-PT  
Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals for a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a user for a valid call. Use the display port PCSSpp  
command to determine the trunk group/member number of the port. Issue the  
status trunk command to determine the service state of the port. If the  
service state indicates that the port is in use, then the port is unavailable for  
certain tests. You must wait until the port is idle before retesting.  
1. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-DS1 (DS1 DID Trunk)  
3-468  
Table 3-198. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1018  
1020  
ABORT  
The test was disabled via translation. You may want to determine why the test  
has been disabled before you enable it.  
1. Verify that the ’Maintenance Test’ field on the ’Trunk Administration’  
screen is set to ’n’. To enable the test, change the trunk administration  
and enter ’y’ into the ’Maintenance Test’ field.  
2. Repeat the test.  
ABORT  
The test did not run due to a previously existing error on the specific port or a  
more general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit pack  
and attempt to diagnose the previously existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2053  
ABORT  
At least one of the following errors is found on the DS1 circuit pack: 1281—  
Loss of signal, 1793—Blue Alarm, 2049—Red Alarm, 2305—Yellow Alarm,  
1537—Hyperactivity.  
Look for the above error types in the Hardware Error Log and follow the  
procedures given in the appropriate DS1-BD or UDS1-BD maintenance  
documentation for the listed error types.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-DS1 (DS1 DID Trunk)  
3-469  
Table 3-198. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Any  
FAIL  
The NPE of the tested port did not conference the tones correctly. This can  
cause noisy and unreliable connections.  
1. Enter the list configuration board PCSS command. If the circuit pack is  
a TN767B vintage 8 or 9, replace the circuit pack with a TN767C V3 or  
later. The error log may have error type 1281.  
2. Test all administered trunks on the board. If one fails, this could be an  
off-board problem (such as an incoming seizure or an off-hook port  
seizure during the test). Retest the board.  
3. If all of the ports fail, check the CABINET (see note below).  
4. If several ports fail, check the error log for TONE-BD or TONE-PT errors. If  
there are such errors, take the appropriate action. When the TONE errors  
have cleared, rerun the test.  
5. If the retry passes and troubles have been reported, coordinate isolation  
with the CO. Make sure that the switch, the CO, and any NTCE  
equipment (the CSUs) have the correct administration.  
6. Replace the circuit pack.  
NOTE:  
If the conference circuit test fails for all ports on a circuit pack, a -5 volt  
power problem is indicated.  
PASS  
The port can correctly conference multiple connections. User-reported  
troubles on this port should be investigated using other port tests and by  
examining station, trunk, or external wiring.  
NOTE:  
This test always passes for TN742 Analog circuit packs prior to  
Vintage 4.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the lIst  
config command and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the linkage  
between the internal ID and the port. If this is not the case, check to see  
that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-DS1 (DS1 DID Trunk)  
3-470  
Port Audit and Update Test (#36)  
This test sends port level translation data from the switch processor to the DS1  
Interface circuit pack to assure that the trunk’s translation is correct. Translation  
updates include the following data: trunk type (in/out), dial type, timing  
parameters, and signaling bits enabled. The port audit operation verifies the  
consistency of the current state of the trunk as kept in the DS1 Interface circuit  
pack and in the switch software.  
Table 3-199. TEST #36 Port Audit and Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
The port may be busy with a valid call. Issue the display port PCSSpp  
command to determine the trunk group/member number of the port. Use  
the status trunk command to determine the service state of the port. If the  
service state indicates that the port is in use, then the port is unavailable  
for certain tests. You must wait until the port is idle before retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 1025 (see the Error Log table for a description  
of this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals a  
maximum of 5 times.  
1006  
ABORT  
The test was aborted because the trunk is out of service.  
1. Use the status trunk command to verify that the trunk is out of  
service.  
2. If the trunk is out of service, determine why.  
3. If it is OK to put the trunk back in service, issue the release trunk  
command to put the trunk back in service, and then retry the test.  
2000  
2100  
ABORT  
ABORT  
Response to the test was not received within the allowable time period.  
Could not allocate resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Test failed due to Internal system error  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DID-DS1 (DS1 DID Trunk)  
3-471  
Table 3-199. TEST #36 Port Audit and Update Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
Trunk translation has been updated successfully. The current trunk states  
kept in the DS1 Interface circuit pack and switch software are consistent. If  
the trunk is busied out, the test does not run, but returns PASS. To verify  
that the trunk is in-service:  
1. Enter status-command to verify that the trunk is in-service. If the trunk  
is in-service, no further action is necessary. If the trunk is  
out-of-service, continue to Step 2.  
2. Enter release-trunk command to put trunk back into in-service.  
3. Retry the test command.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to see that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-472  
DID-TRK (DID Trunk)  
MO Name (in  
Alarm Log)  
1
Alarm Level  
Initial Command to Run  
test port PCSSpp l  
test port PCSSpp l  
test port PCSSpp l  
Full Name of MO  
DID Trunk  
2
DID-TRK  
MAJOR  
DID-TRK  
MINOR  
DID Trunk  
DID-TRK  
WARNING  
DID Trunk  
1. Where Pis the port network number (1 for PPN); C is the carrier designation (for example,  
A, B, or C); and SSis the address of the slot in the carrier where the circuit pack is located  
(for example, 01, 02, ..., etc.).  
2. A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by  
the set options command and that at least 75 percent of the trunks in this trunk group  
are alarmed.  
Direct Inward Dial (DID) trunks coming from the Central Office (CO) allow outside  
parties to call directly to an extension in the system. DID Trunk circuit packs  
include:  
TN753  
TN2146  
TN2139  
TN 436  
TN459  
United States  
Belgium and the Netherlands  
Italy  
Australia  
United Kingdom  
The DID Trunk circuit packs support eight, incoming-only, ports. Each port  
provides an interface between the 2-wire analog line from the CO and the  
DEFINITY system. The DID port receives 3 to 5 digits from the CO that is used to  
directly connect an outside caller to the called station without assistance from an  
attendant. See Figure 3-16.  
1
"DEFINITY"  
CENTRAL  
COMMUNICATIONS  
SYSTEM  
DID  
OFFICE  
SWITCH  
TRUNK  
8
INCOMING  
CALLS ONLY  
Figure 3-16. DID Trunk Interactions  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-473  
For each call, the CO switch signals the system by opening and closing  
individual DID loops (one of the eight ports) and causing the starting or stopping  
of loop current.  
A DID trunk operation involves three significant aspects:  
1. Transmission—deals with the interface requirements regarding all AC  
signals. Transmission includes gain, analog to digital encoding, and  
digital to analog decoding.  
2. Signaling—involves interpretation of DC signals appearing on Tip and  
Ring to and from the CO. These signals include off-hook, on-hook, and  
dial pulse detection.  
3. Switch Connection—involves the connection between the trunk circuitry  
and the TDM Bus of the system. It operates the switchhook connection to  
the TDM Bus.  
Four tests are implemented to diagnose the health of a DID trunk. All of them test  
on-board circuitry only. They are:  
1. Looparound and Conference Circuit Test—verifies the transmission  
operation of the circuit pack (loop around within the port), and checks the  
conference capabilities of all ports.  
This test may fail due to noise induced by adjacent electric power lines.  
Customers having this problem should resolve it with their local power  
company. To temporarily alleviate the alarm caused by the failure of this  
test, the test may be disabled from trunk administration Test field. (This  
also disables the port diagnostic test).  
2. NPE Crosstalk Test—verifies the switch connection operation of the circuit  
pack. The test also verifies that the trunk circuitry only talks on the  
selected time slot on the TDM Bus and never crosses over to time slots  
reserved for other connections.  
3. Port Diagnostic Test—the battery feed circuitry is tested for hook  
detection.  
4. Port Audit Update Test—updates the DID translation information on  
individual ports of the DID trunk. The port translation data consists of  
signaling parameters whose values depend on the CO switch connected  
to the trunk. These parameters include:  
■
wink (signal indicating PBX is ready to receive digits) or immediate  
start  
■
■
■
■
dial tone or rotary dialing trunk  
rotary dialing inter-digit timing  
network balance R/RC  
disconnect timing  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-474  
Additional in-line testing is performed while a call is in progress. Thus, in-line  
errors may occur during operation. See Error Log table for a description of these  
errors. These errors may be reproduced by using the trunk (that is, placing a call)  
and checking their occurrence in the Hardware Error Log.  
Problems detected during signaling may be caused by faults off-board (in the  
CO switch or connections) for which a Warning alarm is raised.  
Before a maintenance test can be run on a port, the port must be idle. If an  
incoming call seizes the port which is being tested by maintenance, the test is  
aborted, and the incoming call proceeds.  
For transmission and signaling standard specification, refer to Digital PBX  
Standards document RS4648.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-200. DID Trunk Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test port PCSSpp sh r 1  
1 (a)  
1 (b)  
1 (c)  
1 (d)  
15 (e)  
Any  
None  
None  
None  
None  
WRN  
WRN  
WRN  
WRN  
OFF  
OFF  
OFF  
OFF  
57476  
57477  
57483  
Any  
Port Audit Update  
(#36)  
18  
0
busyout trunk  
<grp/mbr>  
WRN  
OFF  
release trunk <grp/mbr>  
test trunk <grp>/<mbr>  
130 (f)  
257 (g)  
257 (h)  
257 (i)  
257 (j)  
513 (k)  
None  
None  
None  
None  
None  
None  
WRN  
ON  
57472  
57473  
57474  
57475  
57392  
WRN  
OFF  
OFF  
OFF  
OFF  
OFF  
WRN  
WRN  
WRN  
MAJ/MIN/  
2
WRN  
510 (l)  
769  
57393  
Any  
None  
Port Diagnostic  
(#35)  
MAJ/MIN/  
WRN  
ON  
test port PCSSpp r 3  
2
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-475  
Table 3-200. DID Trunk Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1025  
Loop Around and  
Conference (#33)  
MAJ/MIN/  
WRN  
ON  
test port PCSSpp r 3  
test port PCSSpp r 3  
test port PCSSpp r 3  
2
1281  
NPE Crosstalk (#6)  
MAJ/MIN/  
ON  
2
WRN  
1537  
Any  
57489  
Port Diagnostic  
(#35)  
MAJ/MIN/  
OFF  
2
WRN  
1793 (m)  
None  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the  
set options command. If the Minor alarm is not downgraded by the set-options values, the Minor  
alarm is upgraded to a Major alarm if 75 percent of the trunks in this trunk group are alarmed.  
Notes:  
A common trouble on DID trunks, which reports no errors or alarms, occurs when  
the CO busies out the port (disconnects port). This situation occurs when the CO  
thinks there are problems with the DID port. In this case, no incoming calls are  
possible through this port. In addition to complaints received from outside callers  
trying unsuccessfully to call in, this problem can be diagnosed by listing  
measurements on lightly used trunks. If a particular port is detected as not in  
use, a call to the CO is necessary to get the connection back in service.  
a. This condition occurs when the tone detector times out waiting for digits.  
1 – Verify trunk administered wink/immediate-start parameter.  
2 – Verify the dial type.  
3 – Refer problem to the CO.  
b. Rotary dial before wink – This condition occurs when the CO starts dialing  
before the PBX sends wink on a wink-start trunk. 1 – Verify trunk  
administered wink/immediate-start parameter.  
2 – Refer problem to CO.  
c. Rotary dial too early – This condition occurs when the CO starts dialing too  
soon after seizure on an immediate-start trunk.  
1 – Verify trunk administered wink/immediate-start parameter.  
2 – Refer problem to CO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-476  
d. Rotary dial pulse during wink – This condition occurs when the CO sends  
rotary dial digits too soon after seizure on a wink-start trunk.  
1 – Verify trunk administered wink/immediate-start parameter.  
2 – Refer problem to CO.  
e. This is a software audit error that does not indicate any hardware  
malfunction. Run the Short Test Sequence and investigate associated  
errors (if any).  
f. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
g. Rotary dial pulse on-hook longer than 105 msec – Break between rotary  
pulses is too long.  
1 – Test trunk by performing an incoming test call.  
2 – Refer problem to CO.  
h. Rotary dial rate below eight pulses/sec – More than 135 msec between  
two successive breaks.  
1 – Verify trunk administered interdigit-timing parameters.  
2 – Refer problem to CO.  
i. Rotary dial rate above 12 pulses/sec – Less than 75 msec between two  
successive breaks.  
1 – Verify trunk administered interdigit-timing parameters.  
2 – Refer problem to CO.  
j. Digit detection – Co is starting new rotary dial digit within 150 msec of  
previous digit.  
1 – Verify trunk administered interdigit timing parameters.  
2 – Refer problem to CO.  
k. Loop current active – CO not releasing trunk after PBX disconnect. Occurs  
when the PBX end drops first and the CO does not release the trunk within  
four minutes.  
1 – Verify the interface to the network with a hand telephone set. If calls are  
placed correctly, then refer problem to the CO.  
2 – If unable to place calls or this equipment is not available, check the  
status on port using the status trunk command. If active but not  
connected, disconnect bridging clips at the network interface. Check  
status on the trunk. If trunk went idle, then replace clips. If trunk is still  
active but unable to place calls, refer problem to the CO.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-477  
l. Late CO trunk release – This event only happens after the occurrence of  
Error Type 513. The CO released the trunk four minutes after the PBX  
dropped the call. This event decrements the severity (error count) of Error  
Type 513, or may mean the problem related to Error Type 513 has been  
fixed.  
1 – Verify that Error Type 513 does not occur again. Refer to Error 513.  
m. Incomplete Dial timer expired. This error applies only to the TN459.  
Problem with incoming dialing stream. Refer problem to the CO.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
DID-TRK Loop Around and Conference Circuit Test, for example, you may also  
clear errors generated from subsequent tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
X
X
X
Port Diagnostic Test (#35)  
X
X
ND  
Loop Around and Conference Circuit Test (#33)  
Port Audit Update Test (#36)  
ND  
ND  
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per-port basis. The NPE Crosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is usually only part of a port’s Long Test Sequence  
and takes about 20 to 30 seconds to complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-478  
Table 3-201. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension, attendant number, or trunk group/member  
number of the port. Use the status station, status attendant, or status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is active but the port is not in use (no calls), then  
check the Error Log for Error Type 513 (see Error Log table for  
description of this error and required actions). The port may be locked  
up.  
2. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM Bus) Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
(TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-479  
Table 3-201. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension, attendant number, or trunk group/member number of the port.  
Use the status station, status attendant, or status trunk command to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. You must  
wait until the port is idle before retesting. Attendants are always in use  
(off-hook) if the handset is plugged in and the port is not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Any  
FAIL  
This test can fail due to on-board or off-board problems. Off-board  
problems of concern include EXP-INTF faults, TDM-BUS faults, and faults  
associated with the tone detectors/tone generators. Clear all off-board  
problems before replacing the board. Keep in mind that a TDM-BUS  
problem is usually the result of a faulty board connected to the backplane  
or bent pins on the backplane.  
1. Look for EXP-INTF errors in the error log. If present, refer to the  
EXP-INTF Maintenance documentation.  
2. Look for TDM-BUS errors in the error log. If present, refer to the  
TDM-BUS Maintenance documentation.  
3. Look for TONE-BD and/or TONE-PT errors in the error log. If present,  
refer to the TONE-BD Maintenance documentation and the TONE-PT  
Maintenance documentation.  
4. Test the board when the faults from steps 1, 2, and 3 are cleared.  
Replace the board only if the test fails.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated using other port tests and by examining  
station, trunk, or external wiring.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-480  
Table 3-201. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Looparound and Conference Circuit Test (#33)  
This test checks the reflective and non-reflective loop around and conference  
capabilities of a DID port circuit. The test that uses 404-Hz, 1004-Hz, and  
2804-Hz tones is an on-board test only. Each tone is separately transmitted to  
and from the port (loop around within the port) and verified.  
This test may fail due to noise induced by adjacent electric power lines.  
Customers having this problem should resolve it with their local power company.  
To temporarily alleviate the alarm caused by the failure of this test, the test may  
be disabled from trunk administration Test field. (This also disables the port  
diagnostic test.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-481  
Table 3-202. TEST #33 Looparound and Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Could not allocate the necessary system resources to run this test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
3
ABORT  
System resources required to run this test are not available. The seized  
tone detector did not respond. This abort code is usually associated with  
tone-clock (TONE-BD, TONE-PT, and TDM-CLK) resources.  
1. Clear any tone errors in the error log.  
2. Retry the command at 1-minute intervals for a maximum of 5 times.  
3. If the test continues to abort, escalate the problem.  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension, attendant number, or trunk group/member  
number of the port. Use the status station, status attendant, or status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is active but the port is not in use (no calls), check the  
Error Log for Error Type 513 (see Error Log table for description of this  
error and required actions). The port may be locked up.  
2. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension, attendant number, or trunk group/member number of the port.  
Use the status station, status attendant, or status trunk command to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. You must  
wait until the port is idle before retesting. Attendants are always in use  
(off-hook), if the handset is plugged in and the port is not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1018  
2000  
ABORT  
ABORT  
Test disabled via administration. Verify that the "Maintenance Tests?" field  
on the Trunk Group Form is set to "n." To enable the test, issue the change  
trunk-group x command where "x" equals the number of the trunk group  
to be tested. Then change the entry in the "Maintenance Tests?" field on  
the form to "y."  
Response to the test was not received within the allowable time period.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-482  
Table 3-202. TEST #33 Looparound and Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2100  
ABORT  
System resources required to run this test are not available. This may be  
due to the port being seized.  
1. This abort code is usually associated with tone-clock (TONE-BD,  
TONE-PT, and TDM-CLK) resources. First, clear any tone errors in the  
error log.  
2. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-483  
Table 3-202. TEST #33 Looparound and Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
3
7
FAIL  
The nonreflective 1004 Hz tone test of the port failed. An echo was  
detected from the port. Poor quality transmission was detected to or from  
the port. The problem may be off-board.  
The conference capabilities of the port failed. Poor quality transmission  
was detected to or from the port. The problem may be off-board.  
129  
131  
133  
The reflective 404-Hz tone test failed. Poor quality transmission was  
detected to or from the port. The problem may be off-board.  
The reflective 1004-Hz tone test failed. Poor quality transmission was  
detected to or from the port. The problem may be off-board.  
The reflective 2804-Hz tone test failed. Poor quality transmission was  
detected to or from the port. The problem may be off-board.  
!
CAUTION:  
The port may still be operational, or the fault may be off-board  
(connections or CO). Off-board problems also include incoming  
seizures or off-hook port seizures during the test and, perhaps  
somewhat unlikely, noise induced by adjacent electric power lines.  
Customers having this problem should resolve it with their local  
power company to temporarily alleviate the alarm caused by the  
failure of this test. The test may be disabled from trunk administration  
’Test’ field. This turns off all testing for that trunk group except for  
tests 6 and 36.  
Proceed as follows unless power or tone problems are suspected (see  
note below).  
1. To make sure the problem is on-board, disconnect the port from the  
far-end and retry the test. Coordinate this with the CO, or do it after  
busy hours.  
2. If the retry fails, replace the circuit pack.  
3. If the retry passes and no troubles have been reported, disable the  
test in the trunk group administration. If the retry passes and troubles  
have been reported, coordinate isolation with the CO.  
If the loop around and conference circuit test fails for all ports on a circuit  
pack, a -5 volt power problem is indicated.  
PASS  
DID Trunk Loop Around and Conference Test is successful. This port is  
functioning properly.  
1. If users are reporting troubles, examine loop connections to the port  
and refer problem to the CO.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-484  
Table 3-202. TEST #33 Looparound and Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Port Diagnostic Test (#35)  
This test checks a port’s battery feed circuitry. The battery feed circuitry is tested  
for on-/off-hook detection, battery shutdown, and battery reversal (WINK)  
capabilities.  
Table 3-203. TEST #35 Port Diagnostic Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
System resources required to run this test were not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-485  
Table 3-203. TEST #35 Port Diagnostic Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test were not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
1. If the port status is active but the port is not in use (no calls), then  
check the error log for error type 513 (refer to the Error Log table for a  
description of this error and required actions). The port may be locked  
up.  
2. If the port status is idle, busyout and release the trunk, and then retry  
the command at 1-minute intervals for a maximum of 5 times.  
3. If the test continues to abort, check for wiring errors toward the CO  
which may cause the trunk to lock up.  
4. If the wiring is OK and the test continues to abort, replace the TN753.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension, attendant number, or trunk group/member number of the port.  
Use the status station, status attendant, or status trunk command to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. You must  
wait until the port is idle before retesting. Attendants are always in use  
(off-hook) if the handset is plugged in and the port is not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1018  
ABORT  
Test has been disabled by trunk group administration. Verify that the  
Maintenance Tests?field on the Trunk Group Form is set to n. To  
enable the test, issue the change trunk-group x command where "x"  
equals the number of the trunk group to be tested. Then change the entry  
in the Maintenance Tests?field on the form to y.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-486  
Table 3-203. TEST #35 Port Diagnostic Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
61446  
FAIL  
Battery feed test failed. A loop current fault was detected. This is most  
probably an incoming CO-line problem. This failure code is only reported  
by the TN2139 Italian DID circuit pack.  
1. Check the incoming CO-line for loop current. If none is detected refer  
the problem to the CO.  
2. If the CO-line checks out OK, the failure must be on the DID port.  
Replace the circuit pack.  
61456  
61472  
FAIL  
FAIL  
Battery feed test failed. An on-board problem was detected. This port is  
out-of-service.  
1. Replace circuit pack.  
Battery feed test failed. A problem with the incoming CO-line was  
detected.  
1. Check the incoming CO-line for proper operation. If warranted, refer  
the problem to the CO.  
2. If the CO-line checks out OK, the failure must be on the DID port.  
Replace the circuit pack.  
PASS  
Current flow was detected for this port.  
1. User-reported troubles on this port should be investigated using other  
port tests and by examining connections.  
2. Refer problem to the CO.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Port Audit Update Test (#36)  
This test sends updates of the DID port translation for all ports on the circuit pack  
that have been translated. The update is non-disruptive and guards against  
possible corruption of translation data contained on the circuit pack. No  
response message is expected from the circuit pack once it receives translation  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-487  
updates. The port translation data includes: wink or immediate start trunk, dial  
tone or rotary dialing trunk, rotary dialing inter-digit timing, Network balance  
R/RC, and disconnect timing.  
Table 3-204. TEST #36 Port Audit Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1006  
The port has been placed out of service, perhaps by craft busyout. Use the  
display port PCSSpp command to determine the trunk group/member  
number of the port. Use the status trunk command to determine the  
service state of the port. If the service state indicates that the port is out of  
service, then the port is unavailable for certain tests. You must wait until the  
port is in service and idle before retesting.  
1. If the port status is in service and idle, then retry the command at  
1-minute intervals for a maximum of 5 times.  
2100  
ABORT  
FAIL  
Could not allocate the necessary system resources to run the test.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
This test passed. Translation information was successfully updated on the  
circuit pack.  
1. If signaling troubles are reported (Error Types 1, 257, or 513 in Error  
Log table), verify translation information for this port.  
2. Refer problem to the CO. If the trunk is busied out, the test does not  
run, but returns PASS.  
To verify that the trunk is in-service:  
1. Enter status-command to verify that the trunk is in-service. If the trunk  
is in-service, no further action is necessary. If the trunk is  
out-of-service, continue to Step 2.  
2. Enter release-trunk command to put trunk back into in-service.  
3. Retry the test command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DID-TRK (DID Trunk)  
3
3-488  
Table 3-204. TEST #36 Port Audit Update Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIG-BD (Digital Line Circuit Pack)  
3-489  
DIG-BD (Digital Line Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board PCSS sh  
Full Name of MO  
Digital Line Circuit Pack  
Digital Line Circuit Pack  
DIG-BD  
DIG-BD  
MIN  
WRN  
test board PCSS sh  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); and SS is the address of the slot in the carrier where the circuit  
pack is located (for example, 01, 02, ..., etc.).  
Refer to XXX-BD (Common Port Circuit Pack) Maintenance documentation for  
circuit pack level errors. See also DIG-LINE (Digital Line) Maintenance  
documentation for related line information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIG-IP-STN (Digital IP Station)  
3-490  
DIG-IP-STN (Digital IP Station)  
MO Name (in  
Alarm Log)  
Initial Command to  
Alarm Level  
Run  
Full Name of MO  
Digital IP Station  
DIG-IP-STN  
WARNING  
test station extension  
This maintenance object covers implementation of the maintenance for  
Lucent-provided IP Softphone or the Centre-Vu Remote IP Agent. The  
Lucent-provided endpoint consists of a service provider, an application layer  
called the Telephony Manager, and a registration application. The service  
provider terminates DCP signaling carried over TCP. The Telephony Manager  
provides the GUI emulating the DCP set. The registration application handles  
H323.RAS and is used to register and authenticate the endpoint with DEFINITY.  
This group of modules is called Vphone. Note that the Vphone does not include  
any type of audio path of bearer channel. The Vphone provides a DCP control  
plane for an alternate bearer channel. Tha alternate bearer channel is provided  
by either a native H.323 station or a POTS line or trunk. The Vphone is used only  
in a dual-connect arrangement.  
The Vphone supports some level of existing DCP maintenance in the form of  
audits and updates.  
This station type is not attached to a port board. Insertion of the station is not  
driven by board insertion, rather it is driven by successful registration of the  
endpoint. It is maintained via a set of explicit TCP/IP ping requests and errors  
reported by the User Manger software, which terminates the H.323 signaling  
portion of each endpoint. The MO follows standard mtce methodology and  
supports test, busyout, release and status commands.  
Error Log Entries and Test to Clear Values  
Table 3-205. DIG-IP-STN Digital IP Station Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
0
0
Any  
Any  
test station extension  
1 (a)  
257 (b)  
(c)  
Registration Status Inquiry  
(#1372)  
WARNING  
WARNING  
WARNING  
WARNING  
OFF  
OFF  
OFF  
OFF  
Signaling Path PING Test  
(#1373)  
Digital Terminal Lamp  
Update (#16)  
(d)  
Digital Terminal Audit  
Update (#17)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIG-IP-STN (Digital IP Station)  
3-491  
Table 3-205. DIG-IP-STN Digital IP Station Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
2817  
(e)  
Station Hyperactivity  
Notes:  
a. Error Type 1: this error reports the registration status of the endpoint. If  
call processing SW claims the endpoint is registered and receives  
keep-alive handshakes from the endpoint, the test passes. If keep-alive  
handshaking has failed, the test fails. If the user has intentionally  
un-registered from DEFINITY, the station is now basically an AWOH station  
and is no longer being maintained; no tests will run for this station.  
b. Error Type 257: this error tracks failures of the signaling path PING test.  
The test attempts to send a PING packet to the endpointIP address, as  
reported during registration. The PING packet originates with the C-LAN  
board through which the endpoint is registered. If the PING response  
packet is received, the test passes. If the PING response packet times  
out, the test fails.  
c. This is a refresh of the lamp states for all lamps on the Virtual DCP station.  
The update always passes, if it runs successfully. It may abort, but it will  
never fail. This update is the same update used for existing DCP stations.  
It is test number 16.  
d. This is a refresh of the ringer state on the Virtual DCP station and a query  
of the virtual station’s switch-hook state. The audit always passes, if it runs  
successfully. It may abort, but it will never fail. This runs a subset of the  
complete audit update that runs for standard DCP sets.  
e. Error Type 2817: this error tracks failures of the port hyperactivity counter.  
If a port generates more than 50 uplink CCMS messages within 10  
seconds, the port is taken out-of-service for 30 seconds. Even though the  
Virtual phone actually signals over a TCP/IP link, DCP CCMS messages  
received over the TCP link are counted as regular CCMS uplinks and can  
cause the station to marked as hyperactive.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIG-IP-STN (Digital IP Station)  
3-492  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Signaling Path PING Test, for example, you may also clear errors generated from  
other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Registration Status Inquiry (#1372)  
Signaling Path PING Test (#1373)  
Digital Terminal Lamp Update Test (#16)  
Digital Terminal Audits Test (#17)  
D/ND  
ND  
X
X
X
X
X
X
X
ND  
ND  
ND  
1. D = Destructive; ND = Nondestructive  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIG-IP-STN (Digital IP Station)  
3-493  
Registration Status Inquiry (#1372)  
The Registration status inquiry reports the H.323 registration status of the  
endpoint. An endpoint must be registered and authenticated in order to receive  
service from the system.  
Registration is initiated when the endpoint user attempts to login using the Lucent  
registration software application running on the endpoint PC. The user must  
provide a valid extension and security code. The registration messages are sent  
to the IP address of a C-LAN ethernet port.  
A registered extension has a port type SNNNNN, where N is a digit from 0-9. A  
non-registered extension has an X port.  
Table 3-206. TEST #1372 Registration Status Inquiry  
Error  
Code  
Test  
Result  
Description/Recommendation  
1,2,3  
FAIL  
The endpoint is not successfully registered.  
1. Verify that the user is entering:  
■
■
the correct extension and security code  
the C-LAN IP address  
2. Verify that the extension has been enabled for IP softphone  
operation.  
3. If many endpoints cannot register, investigate any errors of the  
C-LAN ethernet port.  
4. Examine the ethernet cabling from the endpoint PC to the ethernet  
hub.  
PASS  
The endpoint is successfully registered and continues to respond to  
registration handshaking.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIG-IP-STN (Digital IP Station)  
3-494  
Signaling Path PING Test (#1373)  
This test is nondestructive.  
The test determines the local C-LAN through which the signaling originates and  
the endpoint’s IP address. It then requests the local C-LAN to execute a PING on  
the endpoint’s address. If the PING is successful, the test passes, if the PING is  
not successful, the test fails.  
NOTE:  
Multiple failures of this test can take the Digital IP Station out of service.  
This test checks the circuitry involved in the data path of a peer-to-peer IP layer  
connection.  
This nondestructive test runs due to in-line errors, during periodic and schedule  
maintenance, and on demand.  
Table 3-207. TEST #1373 Signaling Path PING Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Could not locate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
2100  
2500  
1003  
ABORT  
ABORT  
FAIL  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
Ping to the destination failed.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Investigate any C-LAN ethernet port errors.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIG-IP-STN (Digital IP Station)  
3-495  
Table 3-207. TEST #1373 Signaling Path PING Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1007  
FAIL  
The system could not PING the registered endpoint via the C-LAN.  
1. Verify that at least one destination reachable through this port. PING  
this destination (ping ip-address xxx.xxx.xxx.xxx).  
2. If the PING to any destination is successful through this port, the link is  
up.  
3. If PING to all destinations fail, test the C-LAN port (test port UUCSSpp  
short) and follow repair procedures for Session Status Test (#1286)  
failures.  
4. If only this station cannot be pinged:  
■
■
■
Make sure the PC is up  
Make sure the PC has a network connection (ethernet or dialup)  
Check the ethernet cabling  
PASS  
The system can successfully send IP packets to the registered endpoint  
from the C-LAN.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIG-IP-STN (Digital IP Station)  
3-496  
Digital Terminal Lamp Update (#16)  
This test updates internal lamp states that may or may not be displayed on the  
actual PC graphical user interface. The lamp updates will run only if the station is  
in-service. The status of the station is checked and the lamp updates are  
blocked from taking place if the station is not in the in-service state. This test  
does not affect the status of the Message Waiting lamp.  
Table 3-208. TEST #16 DIG-LINE Station Lamp Updates Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
This port may have been busied out by system technician.  
1
1. Look in the Error Log for Error Type 18 (port busied out) for this port. If this  
error type is present, then release the port via the release station  
<extension> command and run the test again.  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
Station may be in ready-for-service or out-of-service state.  
1. Use status station command to verify state of station.  
2. Make sure the terminal is connected.  
3
ABORT  
ABORT  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may be  
busy with a valid call.  
1. Use display port UUCSSpp to determine the station extension of the port.  
Use status station to determine the service state of the port. If the port is  
in use, wait until the port is idle before testing.  
2. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The message to light all of the station lamps was sent successfully to the port.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIG-IP-STN (Digital IP Station)  
3-497  
Digital Terminal Audits Test (#17)  
This is a series of tests that are classified as audits. The SPE sends messages to  
the softphone application to perform the following tests. These audits run only if  
the station is in-service.  
■
Switchhook Inquiry Test — This is an update of the SPE records according  
to the softphone switch hook state.  
■
Ringer Update Test — This updates the softphone ringer state according  
to the processor records.  
Table 3-209. TEST #17 Station (Digital) Audits Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Switchhook audit timed out.  
1
ABORT  
ABORT  
2
ID request fails, health bit returned from voice terminal is bad.  
1. Make sure voice terminal is connected and repeat test.  
2. If test fails, replace voice terminal and repeat test.  
Internal system error  
4
ABORT  
1. Resolve any outstanding circuit pack maintenance problems.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
5
6
ABORT  
ABORT  
Ringer update aborted due to station being in ready-for-service or  
out-of-service state.  
This port may have been busied out by system technician.  
1. Look in the Error Log for Error Type 18 (port busied out) for this port. If this  
error is present, the release the port via release station  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
System resources required for this test are not available.  
Response to the test was not received in the allowable time period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Station Audits passed.  
1000  
2000  
ABORT  
ABORT  
PASS  
1. If complaints persist, investigate by using other port tests, and by  
examining the station, wiring, and connections.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-498  
DIG-LINE (Digital Line)  
MO Name (in  
Initial Command to  
1
Alarm Log)  
DIG-LINE  
DIG-LINE  
Alarm Level  
MINOR  
Run  
Full Name of MO  
Digital Line  
test port PCSSpp l  
WARNING  
test port PCSSpp sh  
Digital Line  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); SS is the address of the slot in the carrier where the circuit pack  
is located (for example, 01, 02, ..., etc.); and pp is the 2-digit port number (for example,  
01).  
DIG-LINE maintenance monitors and tests ports on Digital Line circuit packs and  
the hardware connected to those ports for lines administered as a digital station.  
These include stations with just a digital voice terminal and stations with a digital  
voice terminal and a linked data module. Stand-alone data modules, and data  
adaptors in stand-alone mode, are covered by the PDMODULE and TDMODULE  
maintenance objects. Circuit pack-level maintenance is covered by DIG-BD  
whose strategy is described in the XXX-BD section of this chapter. The following  
circuit packs support digital lines:  
Table 3-210. Digital Line Circuit Packs  
Code  
Ports  
8
Type  
Companding  
mu-law  
Endpoints  
TN754  
4-wire DCP  
4-wire DCP  
2-wire IDCP  
2-wire IDCP  
7400 series digital voice terminals,  
attendant consoles, 510D  
personal terminals, MT515 BCTs,  
DCP data modules  
TN754B  
TN2181  
TN2224  
TN2136  
TN2181  
TN2224  
8
A-law/mu-law  
A-law/mu-law  
A-law/mu-law  
16  
24  
8
2-Wire IDCP A-law/mu-law  
Data Adaptors (DA), Italtel Digital  
Telephone Models 1 and 2  
(IDT1/2).  
16  
24  
2-wire IDCP  
2-wire IDCP  
A-law/mu-law  
A-law/mu-law  
Each digital line port supports two 64 kbps information channels (primary and  
secondary) and one 8kbps signaling channel. Digital voice terminals always use  
the primary information channel. Thus only one voice terminal can be connected  
to each port. The secondary information channel can be used to connect a data  
terminal via a Digital Terminal Data Module (DTDM) or a Data Adaptor (DA). All  
other devices currently supported by Digital Line circuit packs communicate on  
the primary information channel. Figure 10-26 shows examples of digital line  
connectivity.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-499  
Only the TN754B or TN2136 should be used in out-of-building applications. For  
important information pertaining to protection required for out-of-building digital  
voice terminals, see DEFINITY Enterprise Communications Server Installation  
and Test for Single-Carrier Cabinet, 555-230-894.  
It should be noted that TN2181 and TN2224 support both modes as shown in  
Figure 3-17 and Figure 3-18.  
TN413, TN754/B  
Digital Line  
Circuit Pack  
Port  
Port  
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D. .ig. .it.a.l. L. .in. .e. . . . . . . . . . . . . . . . . . . .  
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Physical Connection  
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . .  
Control Channel (Signaling)  
.
.
.
.
.
.
Digital  
Voice  
Terminal  
.
Port  
.
.
.
Primary Information Channel (Voice)  
.
.
. . . . . . . . . . . . . .  
.
.
DTDM  
Data  
Terminal  
.
.
.
.
.
.
Port  
.
.
Secondary Information Channel (Data)  
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
.
.
.
.
.
.
.
Figure 3-17. Digital Line Connectivity  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-500  
TN2136  
Digital Line  
Circuit Pack  
Digital Line  
Port  
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
.
.
.
.
.
.
.
.
.
.
.
Physical Connection  
.
.
.
.
.
.
.
.
.
Data  
Italtel  
Digital  
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Port  
.
Adaptor  
(Linked  
Mode)  
.
.
Control Channel (Signaling)  
.
.
IDCP  
Telephone  
Model 1/2  
.
. . . . . . . . . . . . . .  
.
.
.
.
.
.
.
Port  
.
Primary Information Channel (Voice)  
.
.
CCITT  
V24-V28  
.
.
. . . . . . . . . . . . . .  
.
Data  
Terminal  
.
.
.
.
.
.
Port  
Secondary Information Channel (Data)  
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Physical Connection  
Digital Line  
Italtel  
Digital  
Telephone  
Model 1/2  
Port  
Control Channel (Signaling)  
Primary Information Channel (Voice)  
(Secondary Information Channel Unused)  
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
.
.
.
.
.
.
.
.
.
.
Data Adaptors operating in stand-alone mode are treated as  
PDMODULE Maintenance Objects.  
Figure 3-18. Digital Line Connections  
Only 2-wire Italtel Digital Telephone Models 1 and 2 (IDT1/2) or DAs can be  
directly connected to a TN2136. Lucent DCP (4-wire) digital voice terminals and  
data modules can be connected to these circuit packs via Italtel’s 2/4-wire  
adapter. DAs can operate in either of two modes which are covered by different  
maintenance objects:  
DA Mode  
Stand-alone PDM  
Linked DTDM  
Administered as:  
Endpoint  
Maintenance Object  
PDMODULE  
Data endpoint only  
IDT1/2 and optional data  
terminal  
DIG-LINE  
Digital Line maintenance interacts with Digital Line circuit pack (DIG-BD)  
maintenance, and results of DIG-LINE testing can be affected by the health of the  
Digital Line circuit pack. Keep this in mind when investigating reported Digital  
Line problems.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-501  
There are instances where the service state of a station is mentioned. It is helpful  
to understand what os ment by the different service states that may exist. The  
different service states which apply to digital line station are explained as follows.  
Out-of-Service  
The port, and thus the station, have been removed from  
service. Busyouts put the port in the out-of-service state.  
Ready-for-Service  
The port on the circuit pack has been put into service,  
but the voice terminal has not yet established signaling  
communications with the port.  
In-Service  
The voice terminal has established signaling  
communications with the port, and the system is ready to  
process calls to and from that station. A terminal in the  
ready-for-service state will progress to the in-service  
state if it is functioning normally. It can also be forced into  
the in-service state by going off-hook.  
Downloading of Terminal Parameters  
Programmable Terminals  
The following information is presented as background information to help  
understand how maintenance software interacts with terminal parameter  
downloading.  
Terminal Types:  
The following terminals can be downloaded:  
a. 84xx multibutton digital voice terminals (8403D01A, 8410B, 8410D02A,  
8434D01A) with optional expansion module.  
b. 603A1 and 603D1 Callmaster terminals for telemarketing applications.  
c. 302B1 attendant console.  
Circuit Packs  
1. 8400x, 302B1 Terminals  
a. TN754 (4-wire, Mu-law)  
Minimum usable vintage for 8410D and 8434D terminals - V11  
b. TN754B (4-wire, A-law/Mu-law selectable)  
c. TN2181 (2-wire, 16-port, A-law/Mu-law selectable)  
d. TN2224 (2-wire, 24-port, A-law/mu-law selectable)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-502  
2. 603A1/D1 Terminals  
a. TN754 (4-wire, Mu-law),  
b. TN754B (4-wire, A-law/Mu-law selectable)  
Downloadable Terminal Parameters  
The following parameters are downloaded to programmable terminals:  
Table 3-211. Downloadable Parameters  
Parameter  
Scope  
Terminal  
International Flags (A-law/Mu-law,  
Display Mode, DLI Voltage level)  
System level  
84xx, 603x, 302B1  
84xx, 603x, 302B1  
84xx  
Primary Levels  
(Transmission & Sidetone)  
System level  
System level  
Adjunct Levels  
(Transmission & Sidetone)  
Handset Expander Option  
System level  
Per-terminal  
84xx  
84xx  
Administrable Options (Speakerphone  
& Mute Button)  
Administrable Softkeys  
Per-terminal,  
System level  
8410D, 8434D  
Nonvolatile Memory  
Nonvolatile memory is used to store downloadable parameters in programmable  
terminals. Therefore, once the terminal has been downloaded, it is not be  
necessary to download it again, even if power is removed from the terminal.  
If the nonvolatile memory fails with power still present, the terminal reverts to its  
default factory settings except for its A-law/mu-law companding settings which  
are stored in RAM. If power is removed after the nonvolatile memory fails, the  
terminal reverts to its factory default settings.  
Mu-law companding is assigned as a default setting at the factory, so for  
domestic use, a programmable terminal can place calls, even though it has not  
been downloaded from the PBX.  
Download Actions  
There are several different scenarios that cause a terminal to be downloaded. As  
described below, these can occur as part of background maintenance activity or  
on demand from the System Access Terminal or from a station.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-503  
For the background actions described below, the terminal will be downloaded  
automatically if a download retry flag for the terminal is set in software. This flag is  
set at the time translation is loaded at boot time, when translation which affects  
the parameters of a terminal is changed as part of system administration actions,  
and when a port is inserted in software as a result of board insertion or translation  
change.  
Automatic Download Actions  
1. System Reboot/Restart  
A global download action is started when periodic maintenance tests start  
after a system reboot/restart regardless of whether the parameters have  
been downloaded previously.  
2. Periodic Tests  
If the download flag is still set when periodic tests are run on a terminal, a  
download action will occur. This operation is required in case a terminal  
could not be downloaded previously because it was off-hook at the time  
the system first booted or because the terminal was off-hook at the time  
translation associated with downloadable parameters was changed.  
Note that it may take more than an hour for periodic tests to reach the  
terminal that needs to be downloaded.  
3. Terminal Administration  
A downloadable terminal is automatically downloaded when translation  
changes associated with downloadable parameters are made as part of  
system administration. As shown in Table 10-128, these changes can be  
for a specified terminal or may be system-wide. If the change is for  
system-level parameter, a background global update request is made to  
download all programmable terminals.  
This global update may take more than an hour for a system with several  
thousand programmable terminals.  
4. Port Insertion  
Whenever maintenance software initiates a request to place a port into  
service, a terminal download action is started on that terminal if that  
terminal is programmable. This port insertion action occurs under the  
following circumstances:  
a. A digital line circuit pack that is physically inserted into the system  
has ports currently administered for programmable terminals.  
If more than 20 port insertion requests are received within a few  
seconds, a global download request is started up as a background  
task. This action updates all programmable terminals instead of just  
those being inserted. This is done to avoid system overload for  
situations where there is massive board insertion.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-504  
b. A station port is added to the system by a "add station" or "change  
station" command.  
c. A TTI port is activated.  
5. Audits  
As part of periodic maintenance, the hardware status audit test queries  
programmable terminals to determine which levels and/or options are  
being used. If the reported values are not equal to the administered  
values, the system will initiate a terminal download action. This audit does  
NOT check the parameters used for softkeys.  
6. Activation of TTI  
A terminal is downloaded automatically when it is activated using the  
Terminal Translation Initialization feature. Therefore, no special user  
actions are required for TTI.  
NOTE:  
Plugging the station cord into a terminal does not automatically  
cause the terminal to be downloaded. If this terminal has factory  
defaults or if the terminal has been previously downloaded with  
parameters different than those desired, use one of the demand  
download actions described below to download the terminal.  
Demand Download Actions  
1. Busyout/Release Command  
A maintenance demand busyout/release request for a station will cause  
the terminal to be downloaded regardless of its previous download status.  
2. Feature Access Code  
A Refresh Terminal Parameters Feature Access Code can be used to  
request a terminal download action. When this code is followed by a "#",  
the programmable parameters for the current terminal are downloaded  
when the terminal goes on hook. When this code is followed by an  
extension, the programmable parameters for the specified station are  
downloaded.  
This Refresh Terminal Parameters Feature Access Code is assigned on  
the second page of the "feature-access-codes" screen.  
A confirmation is returned if the download request is accepted. A busy  
tone is returned if the request is made from a different station when the  
target station is off-hook.  
The first three green call appearance LEDs on the 84xx 603x terminal will  
be turned on for three seconds if the station was successfully downloaded  
as a result of an entry of a Refresh Terminal Parameters Facility Access  
Code. This is not true for the 302B1 terminal.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-505  
There is no visible display on a station for the other background or  
demand download actions. As described below, the "status station" and  
"status attendant" screens can be used to check the download status of a  
specified terminal.  
Status of Parameter Downloads  
The "status station" and "status attendant" screens display the current download  
status of individual 84xx, 603, and 301B1 terminals in the Download Status field.  
The possible download states are:  
Table 3-212. Terminal Download Status  
Status  
Complete  
Terminal Down Load State  
Terminal successfully downloaded sometime in the past.  
Pending  
System waiting to download the terminal. This may require the  
execution of a background periodic test which could take more  
than an hour. A demand download as described above may also  
be used to initiate an immediate download.  
Not Applicable  
Not a programmable terminal.  
Possible reasons for terminal being not downloaded include:  
— Terminal is off-hook.  
— Terminal detected a bad checksum.  
— Terminal detected a bad or missing EEPROM (refer to hardware error log).  
— Terminal is busy programming data from a previous PROGRAM message.  
— Terminal is in the Programming Disabled state.  
— Terminal is in the Local Program Options Mode.  
— Terminal is disconnected or out of service (use status station command).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-506  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-213. DIG-LINE Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test port PCSSpp sh r 1  
1 (a)  
1 (b)  
18 (c)  
40987  
1 to 20  
0
None  
None  
WARNING  
WARNING  
WARNING  
OFF  
OFF  
OFF  
busyout port  
PCSSpp  
rel port PCSSpp  
130 (d)  
257 (e)  
513  
None  
None  
WARNING  
ON  
test port PCSSpp sh  
40971  
0
Station (Digital)  
Audits Test (#17)  
WARNING(  
o)  
OFF  
test port PCSSpp sh r 6  
767 (f)  
40964  
None  
None  
WARNING  
WARNING  
OFF  
OFF  
769 (g)  
40963  
40988  
1026(o)  
1281  
NONE  
WARNING  
WARNING  
OFF  
OFF  
Any  
Station (Digital)  
test port PCSSpp sh r 4  
Audits Test (#17)  
1537 (h)  
1793  
40968  
None  
WARNING  
MINOR/  
WARNING  
OFF  
ON  
Voice & Ctrl. Local  
Loop Test (#13)  
test port PCSSpp l r 3  
test port PCSSpp l r 3  
2
2049  
NPE Crosstalk Test  
(#9)  
MINOR/  
WARNING  
ON  
3
2304 (n)  
2305 (i)  
2305 (h)  
3840 (k)  
3840 (l)  
3841 (m)  
None  
None  
None  
None  
None  
None  
32770  
40967  
40965  
40989  
41029  
Continued on next page  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Major alarms on this MO may be downgraded to Warning alarms based on the value used in the set  
options command.  
3. Major alarms on this MO may be downgraded to Warning alarms based on the value used in the set  
options command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-507  
Notes:  
a. Could experience a noisy port or link. This is an off-board problem  
detected by the port circuit. Check for defective wiring, a defective voice  
terminal, or move voice terminal closer to the switch (in terms of feet of  
wire from the jack to the switch). If the problem still exists, replace the  
circuit pack. Once the problem has been resolved, the alarm will be  
retired after a predetermined amount of time.  
b. This Error Type and Aux Data will occur when at least 15 off-board  
problems have been detected with the link to the terminal. When an error  
with the link is detected, an on-board counter is incremented.  
The user could experience a noisy port or link. This is an off-board  
problem detected by the port circuit. Check for defective wiring, a  
defective voice terminal, or move voice terminal closer to the switch (in  
terms of feet of wire from the jack to the switch). If the problem still exists,  
replace the circuit pack. Once the problem has been resolved, the alarm  
will be retired after a predetermined amount of time.  
c. This error type is logged when the port in question is busied out by  
maintenance personnel. Make sure port is released from busyout via the  
release port PCSSpp command.  
d. This error type indicates that the circuit pack has been removed or has  
been insane for more than 21 minutes. To clear the error, reinsert or  
replace the circuit pack.  
e. Problems transmitting to the voice terminal. This problem can be caused  
by defective wiring. Defective wiring can cause varying degrees of  
problems on different types of sets. Sets such as the 7410 appear to be  
more susceptible to wiring problems than other sets. This is usually an  
on-board problem and can be ignored if no user complaints are received.  
f. This is an in-line event that produces this error type when a favorable  
response is received from running the Digital Line Electronic Power Feed  
Test (#11). No craft action is necessary. This alarm will be resolved with  
the passing of time.  
g. With Aux Data 40963, this error type is a result of an unfavorable response  
to the Electronic Power Feed/ Positive Temperature Coefficient Test (#11).  
With Aux Data 40988, this error type indicates that the EPF/PTC circuit has  
been turned off due to an overcurrent condition.  
For TN754 vintage 13 or earlier, the EPF circuit senses an overcurrent  
condition at the voice terminal. Check for a short in the wiring, a damaged  
jack, an incorrect type of voice terminal, or a defective voice terminal.  
For TN754 vintage 14 or later, TN754B and TN2136, the PTC will open if  
there is a short on the power line for 1/2 second or longer. The voice  
terminal is probably not operating properly. Unplug the voice terminal for  
30 seconds and then plug it back in. If the voice terminal still does not  
operate, then check for a short in the wiring, a damaged jack, an incorrect  
type of voice terminal, or a defective voice terminal.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-508  
Once the problem has been resolved, it may take up to 1 hour for the  
alarm to clear due to ‘‘leaky bucket’’ strategy. If the problem cannot be  
resolved by one of the steps above, then replace the circuit pack.  
h. An in-line maintenance error has generated an off-board warning due to  
some problem with the link to the voice terminal. This can be ignored if no  
user complaints are received. Otherwise, make sure the voice terminal is  
connected, check for defective wiring, check for a defective voice  
terminal, and move voice terminal to a jack that is closer to the switch (in  
terms of feet of wiring between the jack and the switch). If the problem still  
exists, replace the circuit pack. Once the problem has been resolved, the  
alarm will be retired after a predetermined amount of time.  
i. This indicates that the station went off-hook while it was in the  
ready-for-service state. Use the status station command to determine the  
state of the station. The off-hook should have moved the station to  
ready-for-service. No craft action is necessary.  
j. This is the code that is generated when the link between the circuit pack  
and the voice terminal is successfully reset. No craft action is necessary.  
k. No terminal is connected to the Digital Line board. No maintenance action  
is required.  
l. An uplink message has been logged indicating that the Electric Power  
Feed (EPF) is on with no load on it. No action is necessary.  
m. The circuit pack’s message buffer is full. This may be caused by having  
many display phones with heavy traffic connected to the circuit pack. No  
action is necessary.  
n. Internal system error. No action is necessary.  
o. There is a problem with the voice terminal EEPROM. When the voice  
terminal is repaired the alarm will be resolved with the passing of time.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Voice and Control Channel Local Loop Around Test, for example, you may also  
clear errors generated from other tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-509  
Table 3-214. System Technician-Demanded Tests: DIG-LINE  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Digital Terminal Remote Loop Around Test (#1201)  
Voice and Control Channel Local Loop Around Test (#13)  
Digital Line NPE Crosstalk Test (#9)  
D/ND  
X
X
X
X
X
X
D
ND  
ND  
ND  
ND  
ND  
Digital Line Electronic Power Feed Test (#11)  
DIG-LINE Station Lamp Updates Test (#16)  
Station (Digital) Audits Test (#17)  
X
X
1. D = Destructive, ND = Non-destructive  
Digital Terminal Remote Loop Around Test  
(#1201)  
This test checks the integrity of the connection between the SPE and the  
attached Digital Terminal and the ability of the terminal and the associated port to  
send and receive data. This test is based, in principal, on procedure 622 used in  
system 85 to help isolate digital terminal problems.  
A request is presented to the terminal to go into loop back mode. Then data is  
sent to the terminal and when received back, checked for consistency. This test  
is run as a part of the craft command "test long" procedure. It is not included in  
any error recovery strategy and generates no Error Log entries or alarms. To  
begin the test, Maintenance will ask Call Processing to make the associated end  
point and port “ Maintenance Busy”. This test will succeed if the endpoint is  
"idle". If the reserve request fails then the test will abort. If the request succeeds  
then the SPE sends a message to loop around both information channels for the  
digital terminal. First the primary information (voice, Information Channel 1 or I1)  
channel loop back test is run. The test is performed by sending a digital count  
from the Tone/Clock circuit pack on the primary information channel time slot and  
receiving the same digital count with a general purpose tone detector.  
If the primary information channel test is successful, the loop around test for the  
secondary information (data, Information Channel 2 or I2) channel is then  
performed. This test is the same as the primary information channel loop around  
test and is performed only if a DTDM is administered, which is also the case for a  
linked DA.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-510  
Only one value (Pass. Fail, or Abort) is generated as a result of the two tests run.  
If any test fails aborts, the sequence is stopped. Upon completion of this test the  
associated endpoint and port are moved back into the previous service state.  
Table 3-215. TEST #1201 Digital Terminal Remote Loop Around Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension or attendant number of the port. Use  
status station or status attendant to determine the service state of the  
port. If the service state indicates that the port is in use, then the port is  
unavailable for certain test. You must wait until the port is idle before  
re-testing. Attendants are always in use (off-hook) if the handset is  
plugged in and the port is not busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
System resources required to run this test are not available.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM-Bus) Maintenance to  
diagnose any active TDM-BUS errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out of service.  
1. Look for TTR-LEV errors in the Error Log. If present refer to TTR-LEV  
(TTR-Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exist, retry the command at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-511  
Table 3-215. TEST #1201 Digital Terminal Remote Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display portPCSSpp command to determine the station  
extension or attendant number of the port. Use status station or status  
attendant to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain test.  
You must wait until the port is idle before resetting. Attendants are always  
in use (off-hook) if the handset is plugged in and the port is not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The installed circuit pack does not support this operation.  
1005  
2000  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
System resources required to run this test are not available.  
1. Make sure terminal is connected and repeat test.  
2100  
14  
ABORT  
FAIL  
2. If test fails replace terminal and repeat test.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
The primary channel (voice, Information Channel 1 or I1) is not operating  
properly. User impact may range from noticing nothing to not being able to  
use the port. Check the results of Voice and Control Channel Local Loop  
Test (#13). If that test fails, suspect the Digital Line circuit pack. If that test  
passes then replace the terminal. If both tests fail and component  
replacement does not change the results, then:  
1. Run circuit pack tests to check the tone generator circuit pack and the  
Tone Detector circuit pack using the test board PCSSpp command.  
2. Resolve any problems that are detected on the Tone Generator circuit  
pack or Tone Detector circuit pack.  
3. If the Tone Generator and Tone Detector circuit pack are functioning  
properly, and the tests still fail, escalate the problem.  
1015  
ABORT  
The system will not allow this test to be run because the station is/has not  
been busied out. Busy out the station with the busyout station command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-512  
Table 3-215. TEST #1201 Digital Terminal Remote Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
16  
FAIL  
The secondary channel (data Information Channel 2 or I2 is not operating  
properly. User impact may range from noticing nothing to not being able to  
use this terminal. Check the results of Voice and Control Channel Local  
Loop Test (#13). If that test fails, suspect the Digital Line circuit pack. If  
that test passes then replace the terminal. If both test fail, and component  
replacement does not change the results, then:  
1. Run circuit pack tests to check the tone generator circuit pack and the  
Tone Detector circuit pack using the test board PCSSpp command.  
2. Resolve any problems that are detected on the Tone Generator circuit  
pack or Tone Detector circuit pack.  
3. If the Tone Generator and Tone Detector circuit pack are functioning  
properly, and the tests still fail, escalate the problem.  
PASS  
Voice and Control Channel Local Loop test passed. All channels are  
transmitting properly.  
1. To be sure that this is not an intermittent problem, repeat this test up to  
a maximum of ten times to make sure it continues to pass.  
2. If complaints persist (noisy connections for voice. corrupted data  
transfer for data), examine the station, connections, and wiring.  
Digital Line NPE Crosstalk Test (#9)  
One or more Network Processing Elements (NPEs) reside on each circuit pack  
with a TDM Bus interface. The NPE controls port connectivity and gain, and  
provides conferencing functions on a per-port basis. The NPE Crosstalk Test  
verifies that this port’s NPE channel talks on the selected time slot and never  
crosses over to time slots reserved for other connections. If the NPE is not  
working correctly, one-way and noisy connections may be observed. This test is  
part of a port’s Long Test Sequence and takes about 20 to 30 seconds to  
complete. Crosstalk testing is performed on both the primary information channel  
(voice) and the secondary information channel (data) associated with each  
digital station port. If this test fails on either channel, the station and the DTDM  
are taken out-of-service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-513  
Table 3-216. TEST #9 Digital Line NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
ABORT  
During testing of the primary information channel, system resources may  
not have been available. Also, the port may have been busy during the  
test.  
1. Check the port status. Use the display port PCSSpp command to  
determine the station extension of the port. Use the status station  
command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for  
this test. You will have to wait until the port is idle.  
2. If the port status is idle, then retry the command a 1-minute intervals a  
maximum of 5 times.  
2
ABORT  
During testing of DTDM, system resources may not have been available.  
Also, the port may have been busy during the test.  
1. Check if port is being used. If possible, disconnect by toggling  
disconnect button on DTDM. Retry command after 1 minute.  
!
WARNING:  
This action will drop the call in progress.  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use display port PCSSpp to determine the  
station extension or attendant number of the port. Use status station or  
status attendant to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM Bus) Maintenance to  
diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-514  
Table 3-216. TEST #9 Digital Line NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR (TTR  
Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use display port PCSSpp to determine the station extension or  
attendant number of the port. Use status station or status attendant to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. You must  
wait until the port is idle before retesting. Attendants are always in use  
(off-hook) if the handset is plugged in and the port is not busied out.  
1020  
2000  
ABORT  
ABORT  
Test disabled via background testing. Use status station command to  
determine when station is available for testing.  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1
2
FAIL  
The Network Processing Element (NPE) of the tested port was found to be  
transmitting in error. This will cause noisy and unreliable connections.  
Failure code 1 indicates that the Crosstalk test failed on the primary  
channel. Failure code 2 indicates that the Crosstalk test failed on the  
secondary channel.  
1. Replace circuit pack.  
PASS  
The port is correctly using its allocated time slots.  
1. To be sure that this is not an intermittent problem, repeat this test up to  
a maximum of 10 times to make sure it continues to pass.  
2. If complaints persist, examine the station, connections, and wiring.  
Digital Line Electronic Power Feed/Positive  
Temperature Coefficient/PPF Test (#11)  
For TN754 vintage 13 or earlier, this is an Electronic Power Feed (EPF) restoral  
test. In this test, the processor requests that the EPF be turned on for a given  
port, and an attempt is made to turn on the power supply to the station. If no  
current is drawn, the station is probably not connected. If an overcurrent  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-515  
condition is sensed, there may be a short in the loop. A message is returned  
reporting that either the EPF was successfully turned on, or that an overcurrent  
condition was sensed. This test is repeated again 5 seconds later.  
For TN754 vintage 14 or later, TN754B and TN2136 this is a Positive Temperature  
Coefficient (PTC) restoral test. In this test, the processor requests that the PTC be  
turned on for a given port, and an attempt is made to turn on the power supply to  
the station. If an overcurrent condition is sensed, there is probably a short on the  
power line that causing the PTC to open and disconnect the voice terminal. Since  
the PTC does not have self-restoral capability, the voice terminal must be  
manually unplugged for 30 seconds and then plugged back in to restore the  
PTC. A message is returned reporting that either the PTC was successfully  
turned on successfully with no problem or an overcurrent condition was sensed.  
This test is repeated again 5 seconds later.  
TN2181 and TN2224 boards carry a Protected Power Feed (PPF) relays, one for  
each port. Therefore this will be a Protected Power Feed restoral test. The test  
procedure and its response is same as that of EPF. One of differences between  
EFP and PPF is that, if the port goes into a overcurrent state, PPF does not report  
this change of state because it is a transient state which will not last more than  
50ms. If the over current persists, the power shuts off automatically and an EPF_  
off_overcurrent message is sent uplink.  
Table 3-217. TEST #11 Digital Line Electronic Power Feed Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal System Error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use display port PCSSpp to determine the  
station extension or attendant number of the port. Use status station or  
status attendant to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-516  
Table 3-217. TEST #11 Digital Line Electronic Power Feed Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
Electronic Power Feed Test passed. The message to turn on the power to  
the station was successfully sent to the port.  
1. Although this test will never actually return a FAIL result except for the  
Internal system error (naught/FAIL ) described above, it will log an  
error indicating the real results of the test. Check the Error Log for any  
entries with Error Types 767 or 769 after the test completes.  
2. If Error Type 767 appears in the Error Log, this should indicate that the  
test sensed no problems with the power to the station. To verify that the  
station is powered up correctly, run a self-test on the station, if  
available, and check that all the feature buttons are operating.  
3. If Error Type 769 appears in the Error Log, this indicates some problem  
with the power to the station. Check for a short in the wiring, a  
damaged jack, a defective voice terminal, or an incorrect type of  
terminal.  
Voice and Control Channel Local Loop Test (#13)  
These tests check the information and control channels between the Switch  
Processing Element (SPE) and the Digital Line port circuit. The SPE sends a  
message to loop around both the information and control channels for the port.  
First, the primary information (voice) channel loop back test is run. The test is  
performed by sending a digital count from the Tone-Clock circuit pack on the  
primary information channel time slot and receiving the same digital count with a  
general purpose Tone Detector.  
While the primary information channel is still looped around, the Control Channel  
Loop Around Test is performed. This test consists of sending four different  
transparent patterns to the on-board microprocessor, receiving them back, and  
comparing them.  
The Loop Around Test for the secondary information (data) channel is then  
performed. This test is the same as the primary information channel loop around  
test and is performed only if a DTDM is administered.  
A Conference Test is done next for the primary information channel. This test is  
the same as Conference Test #6.  
Only one value (Pass, Fail, or Abort) is generated as a result of four tests run. If  
any test fails or aborts, the sequence is stopped.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-517  
Table 3-218. TEST #13 Voice and Control Channel Local Loop Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use display port PCSSpp to determine the  
station extension or attendant number of the port. Use status station or  
status attendant to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM Bus) Maintenance to  
diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
(TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use display port PCSSpp to determine the station extension or  
attendant number of the port. Use status station or status attendant to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. You must wait  
until the port is idle before retesting. Attendants are always in use  
(off-hook) if the handset is plugged in and the port is not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-518  
Table 3-218. TEST #13 Voice and Control Channel Local Loop Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
2100  
7
Could not allocate the necessary system resources to run this test.  
1. Rerun the test at 1-minute intervals a maximum of 5 times.  
FAIL  
Conference Test failed on primary channel. In some cases, users may not  
notice disruption in service. In extreme cases, conferencing feature may  
not work at all.  
14  
15  
FAIL  
FAIL  
The primary voice channel is not transmitting properly. User impact may  
range from noticing nothing to not being able to use this port.  
The control channel between the processor and digital circuit pack is not  
transmitting properly. User impact may range from noticing nothing to not  
being able to use the port. Could also be disruptive to other users.  
16  
FAIL  
The secondary voice channel is not transmitting properly. User impact may  
range from noticing nothing to not being able to use this port.  
1. Run circuit pack tests to check the Tone Generator circuit pack and  
the Tone Detector circuit pack using the test board PCSSpp  
command.  
2. Resolve any problems that are detected on the Tone Generator circuit  
pack or Tone Detector circuit pack.  
3. If the Tone Generator and Tone Detector circuit packs are functioning  
properly, and the test still fails, replace the Digital Line circuit pack.  
PASS  
Voice and Control Channel Local Loop test passed. All channels are  
transmitting properly.  
1. To be sure that this is not an intermittent problem, repeat this test up to  
a maximum of 10 times to make sure it continues to pass.  
2. If complaints persist (noisy connections for voice, corrupted data for  
data transfer), examine the station, connections, and wiring.  
DIG-LINE Station Lamp Updates Test (#16)  
This test lights all lamps on the terminal as specified. The lamp updates will run  
only if the station is in-service. The status of the station is checked and the lamp  
updates are blocked from taking place if the station is not in the in-service state.  
This test does not affect the status of the Message Waiting lamp.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-519  
Table 3-219. TEST #16 DIG-LINE Station Lamp Updates Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
This port may have been busied out by system technician.  
1
3
1. Look in the Error Log for Error Type 18 (port busied out) for this port. If  
this error type is present, then release the port via the release station  
<extension> command and run the test again.  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
Station may be in ready-for-service or out-of-service state.  
1. Use status station command to verify state of station.  
2. Make sure the terminal is connected.  
ABORT  
ABORT  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use display port PCSSpp to determine the  
station extension or attendant number of the port. Use status station or  
status attendant to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1392  
ABORT  
This port is currently a TTI port and the test will not execute on it.  
1. Verify that the port is a TTI port using either the display port command  
(the display shows that the port is a TTI port) or the list config  
command (the display shows a tfor the port).  
2. If either list config or display port indicates that the port is not a TTI  
port, escalate the problem. If both commands indicate that the port is  
a TTI port, the abort is correct, and no action is necessary.  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-520  
Table 3-219. TEST #16 DIG-LINE Station Lamp Updates Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The message to light all of the station lamps was sent successfully to the  
port.  
1. Observe the station lamps being lit when running the test. If all lamps  
do not light successfully, the other Digital Line test results may indicate  
related problems that will not allow the lamps to light.  
2. Investigate by using other Digital Line port tests, and by examining the  
station, wiring, and connections.  
Digital Station Audits Test (#17)  
This is a series of six tests which are classified as audits. The SPE sends  
messages to the on-board microprocessor to perform the following tests. These  
audits run only if the station is in-service.  
■
Switchhook Inquiry Test — This is an update of the SPE records according  
to the circuit pack’s records. This inquiry is sent all the way to the voice  
terminal.  
■
Bad Scan Inquiry Test — A message is sent uplink which contains a count  
that is generated due to certain events relating to the link conditions. This  
can be an indication of communications problems between the Processor  
and Digital Port circuit pack.  
■
EPF/PTC Inquiry Test — For a TN754 vintage 13 or earlier, the status of the  
Electronic Power Feed (EPF) is sent uplink. Possible conditions are:  
EPF-on-ok, EPF-off, and EPF-no-load. For TN754 vintage 14 or later,  
TN754B or TN2136, TN2181, TN2224, the status of the Positive  
Temperature Coefficient (PTC) is sent uplink. Possible conditions are:  
PTC-on-ok, PTC-off, and PTC-no-load.  
■
ID Request Test — A request is made to the station for its status. The  
station sends its configuration information and health information back.  
This information is checked and a pass/fail result is provided.  
■
■
Ringer Update Test — This updates the digital telephone ringer state  
according to the processor records.  
DTMF Administration Update Test — This is a message to the digital  
station to refresh the default value which causes the station to send  
touch-tones only in the primary information channel. This value is set  
initially when the station is put in-service and every time the station’s state  
changes from other states to in-service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-521  
Table 3-220. TEST #17 Station (Digital) Audits Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Switchhook audit timed out.  
1
2
ABORT  
ABORT  
ID request fails, health bit returned from voice terminal is bad.  
1. Make sure voice terminal is connected and repeat test.  
2. If test fails, replace voice terminal and repeat test.  
The EPF/PTC has detected an overcurrent condition.  
3
ABORT  
1. For a TN754 vintage 13 or earlier Digital Line circuit pack, issue the  
test PCSSpp long command. If Test #11 passes, then the EPF/PTC  
condition has been cleared. Rerun the Short Test Sequence. If Test  
#11 does not pass, follow the repair procedures described for Test  
#11.  
2. Look for Error Type 769 logged against DIG-LINE and follow the  
procedures in the associated footnote. If any additional problems are  
found after completion of maintenance procedures, rerun the test.  
4
ABORT  
Internal system error  
1. Resolve any outstanding circuit pack maintenance problems.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
5
6
ABORT  
ABORT  
Ringer update aborted due to station being in ready-for-service or  
out-of-service state.  
This port may have been busied out by system technician.  
1. Look in the Error Log for Error Type 18 (port busied out) for this port. If  
this error type is present, the release the port via the release station  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
System resources required to run this test are not available.  
This port is currently a TTI port and the test will not execute on it.  
1000  
1392  
ABORT  
ABORT  
1. Verify that the port is a TTI port using either the display port command  
(the display shows that the port is a TTI port) or the list config  
command (the display shows a tfor the port).  
2. If either list config or display port indicate that the port is not a TTI  
port, escalate the problem. If both commands indicate that the port is  
a TTI port, the abort is correct, and no action is necessary.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
DIG-LINE (Digital Line)  
3
3-522  
Table 3-220. TEST #17 Station (Digital) Audits Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
FAIL  
Response to the test request was not received within the allowable time  
period.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Station Audits passed. This Digital Port circuit pack is functioning properly.  
PASS  
1. If complaints persist, investigate by using other port tests, and by  
examining the station, wiring, and connections.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-DS1 (DS1 DIOD Trunk)  
3-523  
DIOD-DS1 (DS1 DIOD Trunk)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test trunk group# member# l  
test trunk group# member# l  
test trunk group# member#  
Full Name of MO  
DS1 DIOD Trunk  
DS1 DIOD Trunk  
DS1 DIOD Trunk  
1
DIOD-DS1  
DIOD-DS1  
DIOD-DS1  
MAJOR  
MINOR  
WARNING  
1. A Major alarm on a trunk indicates that alarms on these trunks are not downgraded  
by the set options command and that at least 75 percent of the trunks in this trunk  
group are alarmed.  
NOTE:  
Many trunk problems are caused by incorrect settings of parameters on the  
trunk group administration form. Settings must be compatible with the local  
environment and with parameter settings on the far-end. Refer to DEFINITY  
Enterprise Communications Server Administrator’s Guide for information on  
how to administer trunks. The Application Notes section of that book shows  
the correct settings for administrable timers and other parameters on a  
country-by-country basis.  
A DS1 DIOD trunk provides a link for digitized voice or data communications  
between the system and a central office switch. There are two types of DS1  
interfaces:  
■
■
■
24 DS0 channels on a 1.544 Mbps link  
31 DS0 channels + 1 framing channel on a 2.048 Mbps link  
32-channel mode is supported only on TN464 circuit packs and on G3r V2  
systems.  
The DS1-DIOD maintenance object monitors and maintains a DIOD trunk port on  
a TN464 UDS1 Interface circuit pack. See UDS1-BD in this chapter for more  
information about this circuit pack. The DS1 circuit pack supports low level CO  
trunk signaling interfaces for both ground-start and loop-start trunks. This  
maintenance strategy covers the in-line errors log, initialization tests, periodic  
tests, scheduled tests, demand tests, and alarm resolution and escalation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-DS1 (DS1 DIOD Trunk)  
3-524  
Three trunk service states are specified by DS1 DIOD trunk maintenance:  
out-of-service  
in-service  
The trunk is in a deactivated state and cannot be  
used for either incoming or outgoing calls.  
The trunk is in an activated state and can be used  
for both incoming and outgoing calls.  
disconnect  
(ready-for-service)  
The trunk is in an activated state but can only be  
used for an incoming call.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-221. DS1 DIOD Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test trunk <grp>/<mbr>  
1(a)  
1(a)  
57408  
57487  
57476  
57477  
57485  
15(b)  
18(c)  
Any  
Port Audit and  
Update Test (#36)  
0
busyout trunk  
<grp>/<mbr>  
WARNING  
WARNING  
OFF  
release trunk <grp>/<mbr>  
test trunk <grp>/<mbr>  
130(d)  
257(e)  
None  
ON  
2
57392  
57393  
DS1 CO Dial Tone  
Seizure Test (#314)  
MIN/MAJ  
OFF  
2
513(f)  
DS1 Tie Trunk  
MIN/MAJ  
OFF  
Seizure Test (#136)  
769(g)  
1025(h)  
1025  
57484  
51200  
DS1 CO Dial Tone  
Seizure Test (#314) WRN  
MIN/  
OFF  
ON  
ON  
test trunk <grp>/<mbr> r 2  
test trunk <grp>/<mbr> l r 4  
test trunk <grp>/<mbr> l r 3  
test board PCSS l  
3
1281  
Conference Circuit  
Test (#7)  
MIN/  
WRN  
3
1537  
NPE Crosstalk Test  
(#6)  
MIN/  
WRN  
3
1793(i)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-DS1 (DS1 DIOD Trunk)  
3-525  
Table 3-221. DS1 DIOD Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
2049(j)  
57473  
57474  
57475  
2305(k)  
2562(l)  
50944  
16665  
2817(m) 52992  
3840(n)  
Port Audit and  
Update Test (#36)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. This alarm will only be raised when the System-Parameter Country form has the Base Tone  
Generator field set to 4 (Italy). This alarm will be a MINOR alarm unless 75% or more trunks in this  
trunk group are out of service, then the alarm will be upgraded to a MAJOR alarm.  
3. Major alarms on this MO may be downgraded to Warning alarms based on the value used in the  
set options command.  
Notes:  
a. Error Type 1—Aux Data 57408—No tip ground is detected on an outgoing  
call.  
Aux Data 57476—Rotary Dial before Wink.  
Aux Data 57477—Rotary Dial pulse too early.  
Aux Data 57485—Wink too short for a valid signal.  
Aux Data 57487—PBX could not get ‘‘loop close’’ signal  
The DS1 Interface circuit pack detected a hardware fault. These errors will  
cause the Dial Tone Test (#314) to run and are only considered a problem  
if the Dial Tone Test fails (in which case Error Type 1025 will also show up).  
In this case, the trunk may be put in the ready-for-service state (shown as  
‘‘disconnected’’ by the status command), which allows only incoming  
calls. Run the Dial Tone Test (#314) and follow the procedures.  
b. Error Type 15—This is a software audit error that does not indicate any  
hardware malfunction. Run Short Test Sequence and investigate  
associated errors (if any).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-DS1 (DS1 DIOD Trunk)  
3-526  
c. Error Type 18—System Technician has busied out the trunk to the  
out-of-service state. No calls can be made on this trunk except the Facility  
Access Test Call. For details on this feature, refer to "Facility Test Calls"  
section in Chapter 5, "Routine Maintenance Procedures".  
d. Error Type 130—This error type indicates that the circuit pack has been  
removed or has been insane for more than 11 minutes. To clear the error,  
reinsert or replace the circuit pack.  
e. Error Type 257—The DS1 Interface circuit pack detects a hardware fault.  
Aux Data 57392 indicates no external release on PBX disconnect.  
f. Error Type 513—The DS1 Interface circuit pack detects a hardware fault.  
Aux Data 57393 indicates belated external release on PBX disconnect.  
g. Error Type 769—The DS1 Interface circuit pack detects a hardware fault.  
The Aux Data field contains the following error type:—57484, fault is  
detected on tip/ring.  
h. The DS1Interface circuit pack detects a hardware fault, and the Aux Data  
field contains the following error type: 51200, port is unavailable. Run the  
Dial Tone Test (#314) and follow procedures.  
i. Error Type 1793—DS1 Interface circuit pack is out-of-service. Look for  
UDS1-BD errors in the Hardware Error Log if the port is on a TN464 UDS1  
board. Refer to the UDS1-BD (DS1 Trunk Circuit Pack) Maintenance  
documentation for details  
j. Error Type 2049—With the following Aux Data:  
Aux Data 57473—Rotary dial rate below 8 pulses per second.  
Aux Data 57474—Rotary dial rate above 12 pulses per second.  
Aux Data 57475—Rotary Dial interdigit time is too short.  
The DS1 interface circuit pack detects a hardware error on the DS1 DIOD  
trunk. The trunk can not communicate with the far-end because it is unable  
to interpret digits sent from the far-end switch. Check with the far-end  
switch or Operating Company for proper trunk connection.  
k. Error Type 2305—Recorder message, trunk could not be seized (Aux Data  
50944). Run Test #314 and follow the outlined procedures.  
l. Error Type 2562—Retry Failure error. This error is logged only. It is not a  
hardware failure and hence does not start any testing or generate any  
alarms. This error comes from call processing and is generated when a  
second attempt (retry) to seize an outgoing trunk fails.  
m. Error Type 2817—Glare error. This error is logged only. It is not a hardware  
failure and hence does not start any testing or generate any alarms. This  
error is the result of a simultaneous seizure of a two-way trunk from both  
the near-end and the far-end. Attempt to place the call again. If the error  
persists, execute the Dial Tone Seizure Test (#314) and follow those  
procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-DS1 (DS1 DIOD Trunk)  
3-527  
n. Error Type 3840—Port Audit and Update Test (#36) failed due to an  
internal system error. Enter the status trunk command to verify the status  
of the trunk. If the trunk is out-of-service, then enter the release trunk  
command to put it back into in-service. Retry the test command.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order they are presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the NPE  
Crosstalk Test, for example, you may also clear errors generated from other tests  
in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
X
X
X
Conference Circuit Test (#7)  
DS1 Dial Tone Test (#314)  
Port Audit and Update Test (#36)  
ND  
X
X
ND  
ND  
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
One or more Network Processing Elements (NPEs) resides on each circuit pack  
with a TDM Bus interface. (The TN464 UDS1 circuit pack has one SCOTCH-NPE  
chip instead of several NPE chips.) The NPE controls port connectivity and gain,  
and provides conferencing functions on a per-port basis. The NPE Crosstalk Test  
verifies that this port’s NPE channel talks on the selected time slot and never  
crosses over to time slots reserved for other connections. If the NPE is not  
working correctly, one-way and noisy connections may be observed. This test is  
usually only part of a port’s Long Test Sequence and takes about 20 to 30  
seconds to complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-DS1 (DS1 DIOD Trunk)  
3-528  
Table 3-222. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use on a valid call. Use the status station or status trunk command  
to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
System resources required for this test are not available.  
1001  
1002  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. The status health command can be used to determine  
if the system is experiencing heavy traffic. Refer to the TDM-BUS (TDM  
Bus) Maintenance documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some tone  
detectors may be out-of-service. The list measurements tone-receiver  
command will display information on the system’s tone receivers.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
(TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
1020  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use the status trunk  
command to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test did not run due to a previously existing error on the specific port or  
a more general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit  
pack and attempt to diagnose the already existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-DS1 (DS1 DIOD Trunk)  
3-529  
Table 3-222. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2053  
ABORT  
At least one of the following errors is found on the DS1 circuit pack:  
1281—Loss of signal  
1793—Blue Alarm  
2049—Red Alarm  
2305—Yellow Alarm  
1537—Hyperactivity  
Look for the above error types in the Hardware Error Log and follow the  
procedures given in the appropriate DS1-BD or UDS1-BD maintenance  
documentation for the listed error types.  
FAIL  
The NPE of the tested port was found to be transmitting in error. This will  
cause noisy and unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated using other port tests and examining  
station, trunk, or external wiring.  
Conference Circuit Test (#7)  
One or more Network Processing Elements (NPEs) reside on each circuit pack  
with a TDM Bus interface. (The TN464 UDS1 circuit pack has one SCOTCH-NPE  
chip instead of several NPE chips). The NPE controls port connectivity and gain,  
and provides conferencing functions on a per-port basis. The Conference Circuit  
Test verifies that the NPE channel for the port being tested can correctly perform  
the conferencing function. The NPE is instructed to listen to several different  
tones and conference the tones together. The resulting signal is then measured  
by a tone detector port. If the level of the tone is within a certain range, the test  
passes.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-DS1 (DS1 DIOD Trunk)  
3-530  
Table 3-223. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use on a valid call. Use the status station or status trunk command  
to determine when the port is available for testing.  
1004  
1018  
1020  
ABORT  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use the status station  
or status trunk command to determine when the port is available for  
testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Test disabled via administration. This only applies to analog stations.  
1. To enable test, set the Test field on the station administration screen  
for the particular analog station being tested to ‘‘y.’’ Use the change  
station extension command.  
The test did not run due to a previously existing error on the specific port  
or a more general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit  
pack and attempt to diagnose the previously existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
At least one of the following errors is found on the DS1 circuit pack:  
2053  
ABORT  
1281—Loss of signal  
1793—Blue Alarm  
2049—Red Alarm  
2305—Yellow Alarm  
1537—Hyperactivity  
Look for the above error types in the Hardware Error Log and follow the  
procedures given in the appropriate DS1-BD or UDS1-BD maintenance  
documentation for the listed error types.  
FAIL  
The NPE of the tested port did not conference the tones correctly. This will  
cause noisy and unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port can correctly conference multiple connections. User-reported  
troubles on this port should be investigated by using other port tests and  
by examining station, trunk, or external wiring.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-DS1 (DS1 DIOD Trunk)  
3-531  
Port Audit and Update Test (#36)  
This test sends port level translation data from switch processor to the DS1  
Interface circuit pack to assure that the trunk’s translation is correct. Translation  
updates include the following data: trunk type (in/out), dial type, timing  
parameters, and signaling bits enabled. The port audit operation verifies the  
consistency of the current state of trunk kept in the DS1 Interface circuit pack  
and in the switch software.  
Table 3-224. TEST #36 Port Audit and Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Test failed due to internal system error.  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
Trunk translation has been updated successfully. The current trunk states  
kept in the DS1 Interface circuit pack and switch software are consistent. If  
the trunk is busied out, the test will not run but will return PASS. To verify  
that the trunk is in-service:  
1. Enter the status trunk command to verify that the trunk is in-service. If  
the trunk is in-service, no further action is necessary. If the trunk is  
out-of-service, continue to step 2.  
2. Enter the release trunk command to put the trunk back into in-service.  
3. Retry the test command.  
DS1 CO Dial Tone Seizure Test (#314)  
DS1 CO Dial Tone Seizure Test checks the trunk’s signaling capability provided  
by the DS1 Interface circuit pack. The maintenance software initiates the test by  
sending a ‘‘seizure’’ message to the DS1 Interface circuit pack and expects an  
‘‘active’’ reply from the DS1 interface circuit pack. If the ‘‘active’’ message is  
received, then the test passes. If no message is received and the timer expires,  
the test is aborted. If the DS1 Interface circuit pack sends a ‘‘reorder’’ message  
back to maintenance software, then the test fails.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-DS1 (DS1 DIOD Trunk)  
3-532  
This test cannot be run on a trunk in any of the following conditions:  
■
■
■
The trunk direction is administered as an incoming only trunk.  
The trunk has been seized by a normal trunk call.  
The trunk is administered with maintenance test disabled.  
Table 3-225. TEST #314 DS1 CO Dial Tone Seizure Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use on a valid call. Use the status trunk command to determine  
when the port is available for testing.  
1004  
1005  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use the status trunk  
command to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Test failed due to incompatible configuration administered in trunk group  
form.  
1. Look at the trunk group administration form and see whether the trunk  
is incoming only, port 24 on a DS1 Interface with common control  
channel signaling, or an automatic CO type such as FX. Under any of  
these conditions this is a normal abort.  
1018  
ABORT  
Test has been disabled via administration.  
1. Verify that the Maintenance Testsfield on the Trunk Group Form  
is set to n. To enable the test, issue the change trunk-group x  
command where ‘‘x’’ equals the number of the trunk group to be  
tested. Then change the entry in the Maintenance Testsfield on  
the form to y.  
2. Repeat the test.  
1020  
ABORT  
The DS1 Interface circuit pack is out-of-service.  
1. Look for UDS1-BD errors in the Hardware Error Log. If present, refer to  
the UDS1-BD (DS1/UDS1 Trunk Circuit Pack) Maintenance  
documentation.  
2. Retry the command.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-DS1 (DS1 DIOD Trunk)  
3-533  
Table 3-225. TEST #314 DS1 CO Dial Tone Seizure Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2053  
ABORT  
At least one of the following errors is found on the DS1 circuit pack:  
1281—Loss of signal  
1793—Blue Alarm  
2049—Red Alarm  
2305—Yellow Alarm  
1537—Hyperactivity  
Look for the above error types in the Hardware Error Log and follow the  
procedures given in the appropriate DS1-BD or UDS1-BD maintenance  
documentation for the listed error types.  
FAIL  
The trunk cannot be seized for an outgoing call.  
1. Verify that the Trunk Type field on the trunk administration screen form  
matches the trunk type administered on far end switch.  
2. Look for UDS1-BD errors in Hardware Error Log. If present, refer to the  
UDS1-BD (DS1/UDS1 Trunk Circuit Pack) Maintenance  
documentation.  
3. Retry the test at 1-minute intervals for a maximum of 5 times.  
The trunk can be seized for an outgoing call.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-TRK (DIOD Trunk), DIOD-BD (DIOD Circuit Pack)  
3-534  
DIOD-TRK (DIOD Trunk), DIOD-BD  
(DIOD Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
2
DIOD-BD  
MINOR  
test port PCSS s  
DIOD Circuit Pack  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); and SS is the address of the slot in the carrier where the circuit  
pack is located (for example, 01, 02, ...etc.)  
2. Where l is long, s is short, and r is repeat. Refer to the XXX-BD (Common Port Board)  
Maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-TRK (DIOD Trunk)  
3-535  
DIOD-TRK (DIOD Trunk)  
MO Name (in  
Alarm Log)  
1
Alarm Level  
Initial Command to Run  
test port PCSSpp l  
test port PCSSpp l  
Full Name of MO  
DIOD Trunk  
2
DIOD-TRK  
MAJOR  
DIOD-TRK  
DIOD-TRK  
MINOR  
DIOD Trunk  
WARNING  
test port PCSSpp l  
DIOD Trunk  
1. Where Pis the port network number (1 for PPN); C is the carrier designation (for example,  
A, B, or C); and SSis the address of the slot in the carrier where the circuit pack is located  
(for example, 01, 02, ...etc.).  
2. A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by  
the set options command and that at least 75 percent of the trunks in this trunk group  
are alarmed.  
Direct Inward and Outward Dial (TN429 DIOD) trunks are 2-wire analog lines to  
the CO which support the following services:  
■
■
■
both incoming and outgoing CO calls  
DID trunk  
DID Trunk and 1-way Outgoing DIOD  
The DIOD Trunk circuit pack provides eight ports for loop-start CO. The circuit  
pack is an interface between the 2-wire analog line from the CO and the system’s  
(4-wire) TDM Bus.  
Loop start operation  
Idle State - Tip = ground, Ring = CO Battery  
A. Outgoing Call  
1. PBX Off-Hook (Seize Message): Closes the Tip-Ring Loop  
a. CO Response: DC loop current + Dial tone  
2. PBX On-Hook (Drop Message): Open Tip-Ring loop, no loop current  
a. CO Response: CO goes to idle state (see Note)  
B. Incoming Call  
1. CO Applies Ringing Voltage  
a. PBX Response: Detect ringing current  
2. PBX Off-Hook (Answer Message): Close loop  
a. CO Response: Trip ringing, provide loop current  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-TRK (DIOD Trunk)  
3-536  
3. PBX On-Hook (Drop Message): Open Tip-Ring loop, no loop current  
a. CO Response: CO goes to idle state (see Note)  
C. Direct Inward Dialing (DID)  
1. CO Applies Ringing Voltage  
a. PBX Response: Detect ringing current and close loop  
b. CO Response: Send DTMF digits  
c. PBX Response: Acknowledge of Number dialed and open loop  
2. PBX Off-Hook (Answer Message): Close loop  
a. CO Response: Trip ringing, provide loop current  
3. PBX On-Hook (Drop Message): Open Tip-Ring loop, no loop current  
a. CO Response: CO goes to idle state (see Note)  
NOTE:  
CO does not normally provide an On-Hook (Disconnect) signal.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-226. DIOD Trunk Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test port PCSSpp sh r 1  
15 (b)  
18  
any  
Port Audit Update  
Test (#36)  
0
busyout trunk  
<grp>/<mbr>  
769 (a)  
1537  
1793  
57392  
None  
MAJ/MIN/  
WRN  
ON  
ON  
ON  
2
Dial Tone Test (#0)  
MAJ/MIN/  
test port PCSS l r 2  
test port PCSS l r 3  
2
WRN  
Loop Around and  
Conference Test  
(#33)  
MAJ/MIN/  
2
WRN  
2049  
NPE Cross Talk  
Test (#6)  
MAJ/MIN/  
WRN  
ON  
test port PCSS l r 3  
2
2561  
(a,d)  
57345  
None  
2817 (a,e) 57393  
None  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-TRK (DIOD Trunk)  
3-537  
Table 3-226. DIOD Trunk Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
None  
Test to Clear Value  
3073 (a,c) 57376  
3073 (a,c) 57424  
3585 (a,c) 57424  
None  
None  
Continued on next page  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Minor alarms on this MO may be downgraded to warning alarms based on the values used in the set  
options command. If the Minor alarm is not downgraded by the set-options values, the Minor alarm  
is upgraded to a Major alarm if 75 percent of the trunks in this trunk group are alarmed.  
Notes:  
a. These are in-line errors that have no specific test associated with them.  
Refer to the following table for an explanation and appropriate action.  
b. This is a software audit error that does not indicate any hardware  
malfunction. Run the Short Test Sequence and investigate associated  
errors (if any).  
c. Aux data 57376 - No loop current on incoming call  
Aux data 57424 - No loop current on outgoing call  
These errors cause the Dial Tone Test (#0) to run and are only considered  
a problem if the Dial Tone Test fails (in which case Error Type 1537 also  
shows up). In this case, the trunk may be put in "Ready-for-Service" state  
(shown as "disconnected" by status command), which allows only  
incoming calls. Run the Dial Tone Test (#0) and follow its outlined  
procedures.  
d. Single polarity ringing current - This error results from abnormal ringing  
current, but does not prevent the incoming call from being accepted. This  
error code is only logged as an informational event and causes no other  
testing to occur.  
e. Late CO Trunk release - This error indicates that the CO releases the trunk  
at least four minutes after the PBX dropped the call. This error code is only  
logged as an informational event and causes no other testing to occur.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-TRK (DIOD Trunk)  
3-538  
Table 3-227. DIOD Trunk Errors with NO Tests  
Error  
Type  
Aux  
Data  
Description and System Action  
System Technician Action  
769  
57392  
CO not releasing after call is dropped from PBX  
end (TN747B), or the loop is not open after a  
disconnect (TN765). After several occurrences, an  
off-board (TN747B) or on-board (TN465) warning  
alarm is generated.  
Refer problem to CO.  
2561  
57345  
Single polarity ringing current. This error results  
from abnormal ringing current, but does not  
prevent the incoming call from being accepted.  
One cause could be that the reverse current  
detector associated with the port is failing. (Will not  
be detected by any tests.) The other cause could  
be that normal current is not detected. In this case,  
neither incoming nor outgoing calls can be  
completed, and the dial tone test also fails.  
Check for other errors.  
2817  
3073  
3585  
57393  
57376  
57424  
CO released the trunk at least four minutes after the  
PBX dropped the call. This error code is log only  
and causes no other testing to occur. No alarm is  
generated.  
Check for other errors.  
Check for other errors.  
See Note at end of table.  
No loop current on incoming call. The incoming  
destination has already answered and no loop  
current has been detected. If this is a hard fault, the  
dial tone test and all outgoing calls should also fail.  
No loop current on outgoing call. This error occurs  
on attempt to seize a loop or ground-start trunk for  
an outgoing call. An error occurs if loop current is  
not detected or the caller hangs up before it is  
detected.  
NOTE:  
At the administration terminal, busyout the affected port, and run a Long  
test. If Dial Tone Test #0 passes, ignore this error. Release the port.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order they are presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the NPE  
Crosstalk Test, for example, you may also clear errors generated from other tests  
in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-TRK (DIOD Trunk)  
3-539  
For example, you may also clear errors generated from other tests in the testing  
sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
X
X
X
Dial Tone Test (#0)  
ND  
Loop Around and Conference Test (#33)  
Audit Update Test (#36)  
ND  
X
ND  
1. D = Destructive; ND = Nondestructive  
Dial Tone Test (#0)  
This test attempts to seize a port and checks for the return of a dial tone.  
Table 3-228. TEST #0 Dial Tone Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Could not allocate system resources to run this test.  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the command display port PCSSpp to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM Bus) Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1004  
ABORT  
The port has been seized by a user for a valid call. Use the status trunk  
command to determine when the port is available for testing.  
1. Retry the command at one minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-TRK (DIOD Trunk)  
3-540  
Table 3-228. TEST #0 Dial Tone Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Test has been disabled via administration.  
1018  
ABORT  
1. Verify that the Maintenance Tests?field on the Trunk Group  
Form is set to n. To enable the test, issue the change trunk-group x  
command where "x"equals the number of the trunk group to be tested.  
Then change the entry in the Maintenance Tests?field on the  
form to y.  
1005  
2000  
ABORT  
Trunk has been administered as incoming-only; or DID trunk group type;  
dial tone can only be obtained on outgoing trunks. This is a normal  
condition.  
ABORT  
FAIL  
Response to the test was not received within the allowable time period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Trunk was seized, but dial tone could not be detected.  
1. Check for errors on TONE-BD or TONE-PT. Clear any errors found and  
repeat test.  
2. If error has still not cleared, refer problem to CO.  
2002  
FAIL  
Seizure portion of test failed due to hardware problem. Fault is usually  
caused by a disconnected trunk.  
1. Check trunk wiring to ensure good connection; repeat test if wiring  
correction made.  
2. Locate another identical CO trunk and swap its wiring with one under  
test. Repeat test on both trunks and determine if problem follows trunk  
or remains at original port. If problem follows trunk, refer problem to  
CO. If problem remains at port, replace circuit pack and repeat test.  
1009  
PASS  
PASS  
Detected tone was not pure dial tone. No action required.  
Trunk was seized, and dial tone was detected. User-reported troubles on  
this port should be investigated by using other port tests and by examining  
trunk or external wiring.  
NPE Crosstalk Test (#6)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per port basis. The NPECrosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one way and noisy connections  
may be observed. This test is usually only part of a port’s long test sequence and  
takes approximately 20 to 30 seconds to complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-TRK (DIOD Trunk)  
3-541  
Table 3-229. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM-Bus) Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present or some tone  
detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the trunk  
group/member number of the port. Use the status trunk command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. You must wait  
until the port is idle before retesting.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-TRK (DIOD Trunk)  
3-542  
Table 3-229. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Any  
FAIL  
The NPE of the tested port was found to be transmitting in error. This  
causes noisy and unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated by using other port tests and by  
examining trunk or external wiring.  
Loop Around and Conference Circuit Test (#33)  
This test checks the reflective loop and conference abilities of a CO port circuit.  
The test uses 404 Hz, 1004 Hz, and 2804 Hz tones. Each tone is transmitted  
separately through the loop and checked.  
Table 3-230. TEST #33 Loop Around and Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Could not allocate system resources to run this test.  
Conference Circuit Test aborted.  
ABORT  
ABORT  
ABORT  
7
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
2100  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use the status trunk  
command to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-TRK (DIOD Trunk)  
3-543  
Table 3-230. TEST #33 Loop Around and Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
7
FAIL  
1. Check for errors on TONE-BD or TONE-PT. If there are errors, take the  
appropriate actions.  
2. If the Reflective Loop Around Test fails for all ports on a circuit pack, a  
-5 volt power problem is indicated.  
3. Rerun the test.  
4. If the test fails again, replace the circuit pack.  
PASS  
CO Trunk Loop Around and Conference Test is successful. User-reported  
troubles on this port should be investigated by using other port tests and  
by examining trunk or external wiring.  
Port Audit Update Test (#36)  
This test sends updates of the CO port translation for all ports on the circuit pack  
which have been translated. The update is non-disruptive and guards against  
possible corruption of translation data contained on the circuit pack. No  
response message is expected from the circuit pack once it receives translation  
updates. The port translation data includes: ground or loop start trunk, tone or  
rotary dialing trunk, rotary dialing inter-digit timing, network balance R/RC, and  
disconnect timing.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DIOD-TRK (DIOD Trunk)  
3-544  
Table 3-231. TEST #36 Port Audit Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Could not allocate the necessary system resources to run the test.  
Internal system error  
2100  
ABORT  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
This test passed. Translation information was successfully updated on the  
circuit pack. User-reported troubles on this port should be investigated by  
using other port tests and by examining trunk or external wiring. If the trunk  
is busied out, the test does not run, but returns PASS. To verify that the  
trunk is in-service:  
1. Enter status-command to verify that the trunk is in-service. If the trunk  
is in-service, no further action is necessary. If the trunk is  
out-of-service, continue to Step 2.  
2. Enter release-trunk command to put trunk back into in-service.  
3. Retry the test command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DLY-MTCE (MO-DAILY)  
3-545  
DLY-MTCE (MO-DAILY)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
DLY-MTCE  
DLY-MTCE  
DLY-MTCE  
MINOR  
MAJOR  
NONE  
NONE  
DLY-MTCE  
The DLY-MTCE maintenance object monitors daily translation saves. If a  
translation save times out or fails to run, an error is logged against this  
maintenance object.  
If Save Fails  
Then System Raises  
MINOR Alarm  
Three times in a row  
Seven times in a row  
MAJOR Alarm  
Daily Maintenance Interference  
All of the actions used in DEFINITY R8 administration commands are listed in the  
table below. The command actions that, while active, interfere with daily  
maintenance are also indicated. They are the add, change, duplicate, remove,  
and set commands. These commands are frequently used by customer  
administrators while performing routine administration of DEFINITY.  
Table 3-232. DEFINITY Command Actions  
Likely to  
Disrupt  
Less Likely to  
Disrupt  
add  
backup  
busyout  
clear  
ping  
change  
duplicate  
remove  
set  
recycle  
release  
reset  
display  
enable  
format  
get  
restore  
resume  
save  
list  
status  
test  
mark  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DLY-MTCE (MO-DAILY)  
3-546  
Table 3-232. DEFINITY Command Actions — Continued  
Likely to  
Disrupt  
Less Likely to  
Disrupt  
monitor  
netstat  
upgrade  
Some other command actions can also interfere with daily maintenance when  
certain qualifiers are used in the command, or under certain circumstances. For  
example, certain “test” commands, when used with the modifier “continuously”,  
could potentially interfere with daily maintenance. However, such command  
actions are not used typically by customer administrators doing routine  
administration, and are less likely to disrupt daily maintenance routines than are  
the add, change, duplicate, remove, and set command actions.  
Incomplete Command Time-out  
A time-out feature has been added to the MAINTENANCE-RELATED SYSTEM  
PARAMETERS form (accessed by the command change system parameters  
maintenance). This feature improves the operation of daily maintenance by  
allowing maintenance routines to run that might otherwise not run. It also helps to  
prevent the loss of translations that were not saved by the save translation  
command, and were also not saved because daily maintenance was prevented  
from running prior to the system reset. Highlights of the feature include:  
■
■
■
Options for blank, 1, 2, 3, 4, 5, or 6 hours (the default is 2 hours)  
The blank option indicates that the feature is not active  
Only commands that block the running of daily maintenance (add,  
change, duplicate, remove, and set) are affected  
■
■
All logins will time-out if any of these commands are active for the  
prescribed time (except for the “blank” option)  
The feature applies to all logins, regardless of type (init, dadmin, craft,  
inads) or permissions granted to the specific login ID of an administration  
or maintenance user  
■
The corresponding “time-out” entry is appended to the list history log  
The new Command Time-outfield can be viewed by customer administrators.  
A craft, init, dadmin, or inads login is required to change the option for the field.  
Screen 3-3 shows the MAINTENANCE-RELATED SYSTEM PARAMETERS screen  
for DEFINITY R8r. Screen 3-4 shows an example of the LIST HISTORY form with  
the “time-out” entry. The final line indicates that the command change  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DLY-MTCE (MO-DAILY)  
3-547  
system-parameters maintenance was being executed when the time-out  
period of 2 hours expired.  
change system-parameters maintenance  
Page 1 of 4  
MAINTENANCE-RELATED SYSTEM PARAMETERS  
OPERATIONS SUPPORT PARAMETERS  
Product Identification: 1000000000  
First OSS Telephone Number: 5551212  
Second OSS Telephone Number: 5551213  
Alarm Origination to OSS Numbers: both  
Cleared Alarm Notification? y  
Abbrev Alarm Report? y  
Abbrev Alarm Report? n  
Suspension Threshold: 5  
Restart Notification? y  
Test Remote Access Port? n  
CPE Alarm Activation Level: none  
SCHEDULED MAINTENANCE  
Start Time: 22: 00  
Stop Time: 04: 00  
Daily Maintenance: daily  
Save Translation: daily  
Command Time-out (hours): 2  
System Clocks Interchange: no  
Control Channel Interchange: no  
SPE Interchange: no  
Screen 3-3. Maintenance-Related System Parameters (change system-parameters  
maintenance) for R8r.  
list history  
HISTORY  
Date of Loaded Translation: no translation loaded  
Date  
Time  
Port  
Login  
Actn  
Object  
Qualifier  
9/18  
9/18  
9/18  
16:13  
16:13  
14:13  
MGR1  
MGR1  
MGR1  
init  
init  
init  
logn  
logf  
TIME-OUT  
cha system-param maintenance  
Screen 3-4. New “Command Time-out” Entry in the LIST HISTORY Form.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-548  
DS1-BD (DS1 Interface Circuit Pack)  
MO Name (in  
Alarm Log)  
Initial Command to  
1
Alarm Level  
MAJOR  
Run  
Full Name of MO  
DS1-BD  
DS1-BD  
DS1-BD  
test board UUCSS sh  
test board UUCSS l  
test board UUCSS sh  
DS1 Interface Circuit Pack  
DS1 Interface Circuit Pack  
DS1 Interface Circuit Pack  
MINOR  
WARNING  
1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation (A, B,  
C, D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21).  
The DS1 Interface circuit pack provides an interface to an external DS1 facility  
and supports 24 DS0 channels carried on a 1.544 Mbps DS1 link. These DS0  
channels can be administered as either trunks to other switches or lines to  
off-premises stations. The TN464C and later suffix Universal DS1 Interface also  
supports a 32-channel interface on a 2.048Mbps link. The functions and  
maintenance strategy for the TN464 circuit packs are covered under a separate  
maintenance object, UDS1-BD.  
DS1-BD maintenance logs in-line errors reported by the DS1 Interface circuit  
pack, runs tests for error diagnosis and recovery, and raises and clears alarms.  
The following table shows the capabilities of each DS1 circuit pack. The TN722  
and TN722B are not supported on G3r V1 or later systems.  
DID  
Circuit Pack  
Code  
24  
32  
Tie Trunk  
Signaling  
CO Trunk  
Signaling  
Trunk  
Signaling  
OPS Line  
Signaling  
Channel Channel  
TN722/B  
x
x
x
x
x
TN767/B/C/D/E  
TN464C/D/E/F  
x
x
x
x
x
x
x
x
(24-chl only)  
ISDN-PRI Trunk signaling (for example, Q.921, Q.931) requires a TN464D and is  
handled by system software. The TN464 is covered in the "UDS1-BD (UDS1  
Interface Circuit Pack)" section of Chapter 9.  
Each trunk and line have their own maintenance strategies. However, they all  
depend on the health of the DS1 Interface circuit pack. Refer to the following  
sections for details: TIE-DS1, CO-DS1, DID-DS1, OPS-LINE, ISDN-TRK, and  
ISDN-PLK. Signaling over the DS1 link must be synchronized between the  
transmitting and receiving ends to ensure error-free communication. Refer to  
"SYNC (Synchronization)" for details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-549  
The TN767E circuit pack combined with Lucent’s new 120A1 CSU Module forms  
an Enhanced Integrated CSU. The new 120A1 CSU Module, when combined  
with the functionality provided by the TN767E hardware and firmware, and new  
switch software, provides functionality equivalent to an external stand-alone  
Lucent ESF T1 CSU. The 120A1 CSU Module connects to the TN767E circuit  
pack on the I/O connector panel on the back of the port carrier. The new CSU  
Module, thus becomes an integrated part of the DEFINITY. system. Throughout  
the document, the term 120A1 will mean a 120A1 or later suffix CSU Module.  
The Enhanced Integrated CSU is for use in the United States of America with  
1.544 Mbps DS1 service. For further details on the 120A1 CSU Module see  
DEFINITY. Communications System Generic 1, Generic 2, and Generic 3 V1 and  
V2 - Integrated CSU Module Installation and Operation, 555-230-193.  
The TN767E and 120A1 CSU Module support on-demand loopback tests that  
assist in the detection of faults between the TN767E circuit pack and the CSU  
Module, between the Integrated CSU and the optional Customer Premises  
Loopback Jack, or between the Integrated CSU and remote CSU. These  
loopback tests are explained in detail later in this DS1-BD section, but Figure  
3-19 gives a high level overview of the loopback points.  
The following list of acronym definitions are for Figure 3-19:  
■
■
■
■
■
■
■
■
■
PLB = Payload Loopback  
BLB = Board Loopback  
ELB = Equipment Loopback  
LLB = Line Loopback  
RLB = Repeater Loopback  
CLJ = Loopback Jack Loopback  
R-LLB = Remote Line Loopback  
SMRT = Smart Jack  
LPBK = Loopback  
For more information about DS1 interfaces, see the DEFINITY Communications  
System DS1/CEPT1/ISDN-PRI Reference, 555-025-107.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-550  
NETWORK ENVIRONMENT  
NET  
CPE  
CPE  
NET  
NET-  
DS1  
CSU  
CSU  
DS1  
SMRT  
JACK  
LPBK  
JACK  
LPBK  
JACK  
SMRT  
JACK  
WORK  
BRD  
MOD  
MOD  
BRD  
Remote end  
Local end  
CSU module to CSU module  
CPE  
NETWORK  
SMRT  
DS1  
BOARD  
CSU  
LPBK  
JACK  
MOD  
JACK  
PLB  
BLB  
ELB LLB RLB  
CLJ-LB  
Local end loop backs  
NETWORK  
SMRT  
CPE  
CSU*  
MOD  
DS1  
LPBK  
JACK  
BOARD  
JACK  
R-LLB  
Remote end loop backs (* CSU or External CSU)  
Figure 3-19. High Level Overview Of Loopback Points  
Error Log Entries and Test to Clear Values  
Table 3-233. DS1 Interface Circuit Pack Maintenance Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
test board UUCSS  
1 (a)  
0
Circuit pack removed or  
SAKI Test (#53)  
MIN/WRN‡ ON  
18 (b)  
23 (c)  
0
0
busy-out board UUCSS  
WARNING  
WARNING  
OFF  
OFF  
release board UUCSS  
add ds1 UUCSS  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-551  
Table 3-233. DS1 Interface Circuit Pack Maintenance Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
12 5(d)  
257  
None  
MINOR  
MINOR  
ON  
ON  
65535 Control Channel Loop Test  
(#52)  
test board UUCSS l r 20  
257 (e)  
513 (f)  
769 (g)  
1025 (e)  
1281  
Any  
None  
Any  
MINOR  
ON  
4358  
4363  
Any  
NPE Audit Test (#50)  
Loss of Signal Alarm Inquiry  
Test (#138)  
MIN/WRN† OFF  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
1300 (h)  
1301 (i)  
1302 (j)  
1303 (k)  
1310 (l)  
1311 (m)  
1312 (n)  
1313 (o)  
1314 (p)  
1320  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Loss Of Signal Alarm Inquiry  
Test (#138)  
WARNING  
WARNING  
OFF  
OFF  
Loss Of Signal Alarm Inquiry  
Test (#138)  
Loss Of Signal Alarm Inquiry  
Test (#138)  
MIN/WRN† OFF  
Loss Of Signal Alarm Inquiry  
Test (#138)  
MIN/WRN† ON  
Board Loopback Test  
(#1209)  
MINOR  
ON  
test ds1-loop UUCSS  
ds1/csu-loopback-tests  
Equipment Loopback Test  
(#1210)  
MIN/WRN† OFF  
MIN/WRN† OFF  
MIN/WRN† OFF  
MIN/WRN† OFF  
MIN/WRN† OFF  
MIN/WRN† OFF  
test ds1-loop UUCSS  
ds1/csu-loopback-test  
Repeater Loopback Test  
(#1211)  
test ds1-loop UUCSS  
ds1/csu-loopback-tests  
CPE Loopback Jack Test  
(#1212)  
test ds1-loop UUCSS  
end-loopback/span-test  
Far CSU Loopback Test  
(#1213)  
test ds1-loop UUCSS  
end-loopback/span-test  
Loss of Signal Alarm Inquiry  
Test (#138)  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
1321  
Loss of Signal Alarm Inquiry  
Test (#138)  
1322  
Loss of Signal Alarm Inquiry  
Test (#138)  
MINOR  
ON  
1323  
Loss of Signal Alarm Inquiry  
Test (#138)  
MIN/WRN† OFF  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-552  
Table 3-233. DS1 Interface Circuit Pack Maintenance Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1324  
Any  
Loss of Signal Alarm Inquiry  
Test (#138)  
WARNING  
OFF  
test board UUCSS  
1538 (q)  
1793  
Any  
Any  
MINOR  
ON  
Blue Alarm Inquiry Test  
(#139)  
MAJ/MIN/  
WRN **  
OFF  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS r 6  
test board UUCSS r 6  
1794  
1795  
2049  
2305  
2306  
2561  
2817  
Any  
Any  
Any  
Any  
Any  
Any  
Blue Alarm Inquiry Test  
(#139)  
MAJ/MIN/  
WRN **  
OFF  
OFF  
Blue Alarm Inquiry Test  
(#139)  
MAJ/MIN/  
WRN **  
Red Alarm Inquiry Test  
(#140)  
MIN/WRN† OFF  
Yellow Alarm Inquiry Test  
(#141)  
MINOR  
MINOR  
OFF  
OFF  
Yellow Alarm Inquiry Test  
(#141)  
Major Alarm Inquiry Test  
(#142)  
MIN/WRN† OFF  
MIN/WRN† OFF  
MIN/WRN† OFF  
MIN/WRN† OFF  
Minor Alarm Inquiry Test  
(#143)  
3073 to  
3160 (r)  
Any  
Any  
Slip Alarm Inquiry Test  
(#144)  
3329 to  
3345 (s)  
Misframe Alarm Inquiry Test  
(#145)  
3840(t)  
3900(u)  
Any  
Any  
None  
CPE Loopback Jack Test  
(#1212)  
3901(v)  
Any  
Far CSU Loopback Test  
(#1213)  
3902(w)  
3999 (x)  
Any  
Any  
One-Way Span Test (#1214)  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-553  
Notes:  
a. This error indicates that the circuit pack has stopped functioning or is not  
completely administered. The alarm is logged about 15 minutes after the  
circuit pack has been removed or 11 minutes after the SAKI Test (#53)  
fails.  
To be completely administered, a DS1 circuit pack must meet all 3 of the  
following conditions:  
1. Have an entry in the circuit plan via the change circuit pack  
command  
2. Be administered via the add ds1 UUCSS command  
3. Be physically inserted in the appropriate slot  
If the circuit pack has an entry in the circuit plan and either of the other two  
conditions are not met, a MINOR alarm is logged. To resolve the error  
either  
1. Make sure all conditions for administration are met and that a  
functioning DS1 circuit pack is inserted in the correct slot.  
2. Completely remove the DS1-BD from the system using the following  
steps:  
a. Remove any administered DS1 trunks or access endpoints  
associated with the circuit pack from their trunk groups.  
b. Execute the remove ds1 UUCSS and change circuit pack  
UUCSS commands.  
If all the administration conditions are met for this circuit pack and the red  
LED is still on, follow the instructions for LED Alarms with Error Type 1 in  
Chapter 7.  
b. The DS1 Interface circuit pack has been busied out by a busy-out board  
UUCSS command.  
c. The DS1-BD circuit pack is not completely administered. A completely  
administered DS1-BD circuit pack should have an entry in the circuit plan  
via the change circuit pack command, should have been administered  
via the add ds1 UUCSS command, and should have been inserted into  
the appropriate port slot.  
d. The circuit pack in the slot does not match the type administered to that  
position. Either replace the circuit pack with one of the type administered,  
or use change circuit-pack to readminister the slot. This error may also  
indicate that the 24/32-channel selection on the DS1 administration form  
does not match the configuration of the circuit pack.  
e. This error is associated with the Common Port Circuit Pack Maintenance  
Test. Refer to "XXX-BD (Common Port Circuit Pack)" for details.  
f. The DS1 Interface circuit pack has detected a transient hardware problem  
(for example, external RAM failure, internal RAM failure, internal ROM  
failure,DoorwinnlosatdrufrcomtioWnwswe.Stofmaialnuuraels)..cTomh.isAlel MrraonruawlsilSl edairscahpApndeDaorwwnlhoaedn. no faults  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-554  
are detected for 30 minutes. The value in the Aux Data field indicates the  
type of hardware problem. However, when this error is reported with Aux  
Data in the range of 4352 to 4358, it indicates the circuit pack has  
reported a hardware failure. Escalate this problem.  
g. The DS1 Interface circuit pack has detected a transient hardware logic  
error (for example, program logic inconsistency). This error will disappear  
when no faults are detected for 100 minutes. The value in Aux Data field  
indicates the type of hardware problem.  
h. CSU Module or T1 Sync Splitter missing. The Near-End CSU Typefield  
on the add ds1 form has been administered as integratedbut the  
120A1 CSU Module or T1 Sync Splitter is not physically connected (or is  
improperly connected) to the TN767E board on the back of the port  
carrier.  
If using the 120A1 CSU Module or T1 Sync Splitter, plug (or replug) the  
CSU Module/T1 Sync Splitter into the TN767E circuit pack’s connector on  
the I/O connector panel on back of the carrier. Otherwise, change the  
Near-End CSU Typefield using the change ds1 form to other.  
If this error remains after plugging the CSU Module/ T1 Sync Splitter into  
the board’s connector, there could be a problem with the I/O connector  
panel.  
i. CSU Module/T1 Sync Splitter not expected. The 120A1 CSU Module/T1  
Sync Splitter is physically connected to the TN767E board on the back of  
the port carrier but the Near-End CSU Typefield on the add ds1 form  
has not been administered as integrated.  
If the 120A1 CSU Module/T1 Sync Splitter is to be used, use the change  
ds1 command to change the Near-End CSU Typefield to integrated.  
Otherwise, physically remove the 120A1 CSU Module/T1 Sync Splitter  
from the back of the port carrier.  
j. DS1 configuration error. Attempting to use the 120A1 CSU Module with a  
TN767E circuit pack that is configured for 32-channel (2.048 Mbps)  
operation. The CSU Module only works with a DS1 board configured for  
24-channel (1.544 Mbps) operation in the United States of America.  
k. DS1 circuit pack suffix incorrect for CSU Module/T1 Sync Splitter. The  
Near-End CSU Typefield on the add ds1 form has been administered  
as integratedbut the DS1 circuit pack is not a TN767E or later suffix  
DS1 board.  
If the 120A1 CSU Module/T1 Sync Splitter is to be used, remove the circuit  
pack and replace it with a TN767E or later suffix board. Otherwise, use the  
change ds1 command to change the Near-End CSU Typefield to  
other.  
l. BLB failure. This error occurs when the DS1 Board Loopback (BLB)  
demand test fails. Repeat the test using the following commands:  
busyout board UUCSS, test ds1-loop UUCSS ds1/csu-loopback-tests,  
release board UUCSS. If the BLB test continues to fail, then the TN767E  
circuit pack needs to be replaced.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-555  
m. ELB failure. This error occurs when the Integrated CSU (I-CSU) Module  
Equipment Loopback (ELB) test fails. This test is executed during  
I-CSU/T1 Sync Splitter power-up/reset (i.e., the TN767E board is  
physically inserted and the CSU Module/T1 Sync Splitter is already  
installed) or when the CSU Module/T1 Sync Splitter is plugged on to an  
already initialized DS1 board. The ELB test is also executed as part of the  
command test ds1-loop UUCSS ds1/csu-loopback-tests.  
Attempt to clear the alarm via the following commands: busyout board  
UUCSS, test ds1-loop UUCSS ds1/csu-loopback-tests, and release  
board UUCSS. If the ELB test continues to fail, then either the TN767E  
board, the CSU Module, the T1 Sync Splitter, or the I/O cable between the  
backplane and the CSU Module/T1 Sync Splitter (or any combination  
thereof) has failed. Attempt to isolate where the failure is occurring by  
re-executing the test. Escalate this problem.  
n. RLB failure. This error occurs when the Integrated CSU (I-CSU) Module  
Repeater Loopback (RLB) test fails. This test is executed during I-CSU/T1  
Sync Splitter power-up/reset (i.e., the TN767E board is physically inserted  
and the CSU Module/T1 Sync Splitter is already installed) or when the  
CSU Module/T1 Sync Splitter is plugged on to an already initialized DS1  
board. The RLB test is also executed as part of the command test  
ds1-loop UUCSS ds1/csu-loopback-tests.  
Attempt to clear the alarm via the following commands: busyout board  
UUCSS, test ds1-loop UUCSS ds1/csu-loopback-tests, and release  
board UUCSS. If the RLB test continues to fail, then the CSU Module/T1  
Sync Splitter needs to be replaced.  
o. CPE Loopback Jack deactivation error. This error occurs when the  
TN767E circuit pack could not deactivate a CPE Loopback Jack  
loopback.  
Attempt to clear the alarm via the following commands: busyout board  
UUCSS, test ds1-loop UUCSS end-loopback/span-test, and release  
board UUCSS. If the attempt to deactivate the CPE Loopback Jack  
loopback continues to fail, other steps must be taken to deactivate the  
loopback.  
p. Far CSU Loopback deactivation error. This error occurs when the TN767E  
circuit pack could not deactivate a far-end CSU loopback on  
power-up/reset or upon software request.  
Attempt to clear the alarm via the following commands: busyout board  
UUCSS, test ds1-loop UUCSS end-loopback/span-test, release board  
UUCSS. If the attempt to deactivate the Far CSU loopback continues to  
fail, then escalate the problem.  
q. The hyperactive circuit pack is out-of-service and may exhibit one or more  
of the following symptoms:  
1. The common circuit pack level tests such as Test #51 and/or Test  
#220 are aborting with error code 2000.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-556  
2. The tests run on the ports of this circuit pack are returning NO  
BOARD.  
3. A busy-out/release of the circuit pack has no affect on test results.  
4. A list configuration command shows that the circuit pack and  
ports are properly installed.  
The circuit pack is isolated from the system and all trunks of this circuit  
pack are placed into the out-of-service state. The system will try to restore  
the circuit pack within 15 minutes. When no faults are detected for 15  
minutes, the DS1 Interface circuit pack is restored to normal operation. All  
trunks of the DS1 Interface circuit pack are then returned to the in-service  
state. If the error recurs after 15 minutes, then escalate this problem.  
r. For later releases of G3V4 and beyond, only error 3073 will show that this  
board is receiving Slips and the AUX data shows the last Slip count that  
was reported.  
s. For later releases of G3V4 and beyond, only error 3329 will show that this  
board is receiving misframes and the AUX data shows the last misframe  
count that was reported.  
t. This error is not service-affecting and can be ignored.  
u. Error 3900 is used to give status information on a CPE Loopback Jack  
Test. The value in the Aux Data field indicates the status of the loopback  
test.  
1 — Test is currently running.  
2 — Test failed because loopback could not be activated.  
3 — Test failed because test pattern could not be detected.  
4 — Test has been terminated.  
v. Error 3901 is used to give status information on a Far CSU Loopback Test.  
The value in the Aux Data field indicates the status of the loopback test.  
1 — Test is currently running.  
2 — Test failed because loopback could not be activated.  
3 — Test failed because test pattern could not be detected.  
4 — Test has been terminated.  
w. Error 3902 is used to give status information on a One-Way Span Test. The  
value in the Aux Data field indicates the status of the span test.  
1 — Test is currently running.  
2 — Test has failed because test could not be activated.  
3 — Test pattern was not received from the far end.  
4 — Test has been terminated.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-557  
x. Error type 3999 indicates that the circuit pack sent a large number of  
control channel messages to the switch within a short period of time. If  
error type 1538 is also present, then the circuit pack was taken  
out-of-service due to hyperactivity. If error type 1538 is not present, then  
the circuit pack has not been taken out-of-service, but it has generated  
50% of the messages necessary to be considered hyperactive. This may  
be completely normal during heavy traffic periods. However, if this error  
type is logged when the circuit pack is being lightly used, it may indicate a  
problem with the circuit pack or the equipment attached to it.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order they are presented in Table 3-132. By  
clearing error codes associated with the NPE Connection Audit Test, for  
example, you may also clear errors generated from other tests in the testing  
sequence  
Table 3-234. System Technician-Demanded Tests: DS1-BD  
Reset  
Board  
Sequence  
test  
ds1-loop  
Command  
ShortTest  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Connection Audit Test (#50)  
Control Channel Loop Test (#52)  
D/ND  
ND  
X
X
X
ND  
Loss of Signal Alarm Inquiry Test  
(#138)  
X
ND  
Blue Alarm Inquiry Test (#139)  
Red Alarm Inquiry Test (#140)  
Yellow Alarm Inquiry Test (#141)  
Major Alarm Inquiry Test (#142)  
Minor Alarm Inquiry Test (#143)  
Slip Alarm Inquiry Test (#144)  
Misframe Alarm Inquiry Test (#145)  
Translation Update Test (#146)  
ICSU Status LEDs Test (#1227)  
SAKI Sanity Test (#53)  
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
D
X
X
Internal Looparound Test (#135)  
DS1/CSU Loopback Tests  
D
X
X
D
DS1 Board Loopback Test (#1209)  
D
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-558  
Table 3-234. System Technician-Demanded Tests: DS1-BD — Continued  
Reset  
test  
ShortTest  
Sequence  
Long Test  
Sequence  
Board  
Sequence  
ds1-loop  
Command  
1
Order of Investigation  
D/ND  
CSU Equipment Loopback Test  
(#1210)  
X
X
D
D
CSU Repeater Loopback Test  
(#1211)  
CPE Loopback Jack Test (#1212)  
Far CSU Loopback Test (#1213)  
One-Way Span Test (#1214)  
X
X
X
X
X
D
D
D
D
D
Inject Single Bit Error (#1215)  
End Loopback/Span Test (#1216)  
1. D = Destructive, ND = Non-destructive  
NPE Connection Audit Test (#50):  
The system sends a message to the on-board microprocessor to update the  
network connectivity translation for all the Network Processing Elements (NPEs)  
on the circuit pack.  
Table 3-235. TEST #50 NPE Connection Audit Test  
Error  
Code  
Test Result  
Description/ Recommendation  
None  
2100  
ABORT  
System resources required for this test are not available.  
1019  
ABORT  
FAIL  
Test already in progress.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The circuit pack’s NPEs have been updated with their translation.  
PASS  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-559  
Table 3-235. TEST #50 NPE Connection Audit Test — Continued  
Error  
Code  
Test Result  
Description/ Recommendation  
0
NO BOARD The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an  
incorrect board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add  
ds1 UUCSS command to administer the DS1 interface if it is not  
already administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. Issue the busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Control Channel Looparound Test (#52)  
This test queries the circuit pack for its circuit pack code and vintage and verifies  
its records.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-560  
Table 3-236. TEST #52 Control Channel Looparound Test  
Error  
Code  
Test Result  
Description/ Recommendation  
None  
2100  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
The test failed because the circuit pack did not return the circuit pack code  
or vintage.  
NOTE:  
Error type 1538 in the error log indicates hyperactivity. The  
hyperactive circuit pack is out of service and one or more of the  
following symptoms may be exhibited.  
1. The DS1-BD tests (such as Test 138 and Test 139) are aborting with  
error code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test result.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
When hyperactivity occurs, the circuit pack is isolated from the system, and  
all of the trunks for this circuit pack are placed into the out of service state.  
The system will try to restore the circuit pack within 15 minutes. When no  
faults are detected for 15 minutes, the DS1 interface circuit pack is restored  
to normal operation. All of the trunks for the DS1 interface circuit pack are  
then returned to the in service state. Hyperactivity is often caused by the  
associated facility. In such a case, faults (such as slips, misframes, or blue  
alarms) would be entered in the error log. In addition, many hardware errors  
would be logged against the associated trunk circuits. If the facility is OK  
and the error occurs again after 15 minutes, escalate this problem.  
1. Retry the command for a maximum of 5 times.  
2. If the problem continues, check for hyperactivity. Resolve the problem,  
as appropriate.  
3. If there is no longer hyperactivity, retry the command for a maximum of 5  
times.  
4. If the test continues to fail, escalate this problem.  
Communication with this circuit pack is successful.  
PASS  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-561  
Table 3-236. TEST #52 Control Channel Looparound Test — Continued  
Error  
Code  
Test Result  
Description/ Recommendation  
0
NO BOARD The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
SAKI Sanity Test (#53)  
This test is destructive. This test resets the circuit pack.  
Table 3-237. TEST #53 SAKI Sanity Test  
Error  
Code  
Test Result  
Description/ Recommendation  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
None  
ABORT  
1005  
ABORT  
Wrong circuit pack configuration to run this test. This error applies only to  
DS1 Interface circuit packs. It means the DS1 Interface circuit pack is  
providing timing for the system and, therefore, it cannot be reset without  
major system disruptions.  
1. If the circuit pack needs to be reset, then set synchronization to another  
DS1 Interface circuit pack or to the Tone-Clock circuit pack and try  
again. Refer to "SYNC (Synchronization)".  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-562  
Table 3-237. TEST #53 SAKI Sanity Test — Continued  
Error  
Code  
Test Result  
Description/ Recommendation  
Port is not out-of-service.  
1015  
ABORT  
1. Busyout the circuit pack.  
2. Execute the command again.  
2100  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The circuit pack failed to reset.  
1
2
FAIL  
FAIL  
The circuit pack failed to restart.  
1. Execute the command again.  
2. If the problem persists, escalate this problem.  
The circuit pack initializes correctly.  
PASS  
1. Run the Short Test Sequence.  
0
NO BOARD The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an  
incorrect board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add  
ds1 UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Internal Looparound Test (#135)  
This test is destructive.  
The Internal Looparound Test is run by looping the transmitted DS1 bit stream  
back into the DS1’s board receiver. The loop occurs just before the DS1 facility  
interface. The test is highly destructive and can only be initiated by a system  
technician-demanded reset board UUCSS command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-563  
All trunks on the DS1 Interface circuit pack must be busied out via the system  
technician busy-out board command before running the Internal Looparound  
Test. When the Internal Looparound Test is initiated, maintenance software sends  
appropriate messages to the DS1 Interface circuit pack to start the test. The test  
uses the Tone Generator and Tone Detector to exercise a bit pattern consistency  
test for all ports. If the transmitted and received bit patterns on a trunk are  
different, the test fails.  
When the test is complete, the maintenance software sends a stop loop around  
message to the DS1 Interface circuit pack to put the circuit pack back into the  
normal operation mode. All trunks of the DS1 Interface circuit pack are restored  
to the in-service state after the release board command is entered  
Table 3-238. TEST #135 Internal Looparound Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2012  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due to  
TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic, repeat  
test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may be  
oversized for the number of Tone Detectors present or some Tone Detectors  
may be out-of-service.  
1. Resolve any TTR-LEV errors.  
2. Resolve any TONE-PT errors.  
3. If neither condition exists, retry the test at 1-minute intervals a maximum  
of 5 times.  
1004  
1015  
ABORT  
ABORT  
Received an incoming call on a port of the DS1 circuit pack during the test.  
1. Enter the busy-out board UUCSS command to put all trunks of DS1  
Interface circuit pack to out-of-service state.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
Ports on DS1 Interface circuit pack have not been busied out.  
1. Enter the busy-out board UUCSS command to put all trunks of the DS1  
Interface circuit pack into out-of-service state.  
2. Retry the command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-564  
Table 3-238. TEST #135 Internal Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1039  
ABORT  
The DS1 Interface circuit pack is providing timing for the system. Therefore, it  
cannot be reset without major system disruption.  
1. If the DS1 Interface circuit pack needs to be tested, set the  
synchronization reference to another DS1 Interface circuit pack or to the  
Tone-Clock circuit pack via the following command sequence:  
■ Issue the disable synchronization-switch command.  
■ Next, issue the set synchronization UUCSS command.  
■ Lastly, issue the enable synchronization-switch command.  
2000  
ABORT  
The test was aborted. Response to the test was not received within the  
allowable time period. This may be due to hyperactivity. Error type 1538 in the  
error log indicates hyperactivity. The hyperactive circuit pack is out of service  
and one or more of the following symptoms may be exhibited.  
1. The DS1-BD tests (such as Test 139 and Test 140) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of  
service state. The system will try to restore the circuit pack within 15  
minutes. When no faults are detected for 15 minutes, the DS1 interface  
circuit pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in  
the error log. In addition, many hardware errors would be logged  
against the associated trunk circuits. If the facility is OK and the error  
occurs again after 15 minutes, escalate this problem.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-565  
Table 3-238. TEST #135 Internal Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
DS1 Interface circuit pack failed in the Internal Looparound Test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the DS1 Interface circuit pack is TN767, enter the list measurement  
ds1-log UUCSS command to read the error seconds measurement.  
Otherwise, skip this step.  
3. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
4. Check the physical connectivity of DS1 Interface circuit packs and cable.  
5. Contact T1 Network Service to diagnose remote DS1 endpoint.  
6. If all of the above are OK, escalate this problem.  
PASS  
All administered trunks of DS1 Interface circuit pack pass the Internal  
Looparound Test. The bit pattern consistency test is executed successfully  
over the path that covers a DS1 port, cable, and the external NCTE device.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Loss of Signal Alarm Inquiry Test (#138)  
This test verifies the synchronization status and continuity of the DS1 link. The  
Loss of Signal alarm indicates that the DS1 Interface circuit pack is unable to  
derive the synchronization clock from the DS1 facility. When the DS1 Interface  
circuit pack detects a Loss of Signal alarm, it stops providing the synchronization  
clock for the system if it is administered as a timing source and transmits a Yellow  
alarm to the remote DS1 endpoint.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-566  
When the Loss of Signal alarm is confirmed, the maintenance software places all  
trunks or ports of the DS1 Interface circuit pack into the out-of-service state. The  
inquiry test will run every 10 minutes until the loss of signal has been restored.  
The DS1 Interface circuit pack raises a Loss of Signal alarm after the signal has  
been lost for about 1second. It will not retire the alarm until the signal has  
returned for about 10 seconds.  
This test is also used to maintain the new 120A CSU Module and the 401A T1  
Sync Splitter. The CSU Module, when combined with the functionality provided  
by the TN767E circuit pack, provides functionality equivalent to an external  
standalone ESF T1 CSU. The 401A T1 Sync Splitter, when combined with the  
functionality provided by the TN767E circuit pack, allows an ATM switch to derive  
its timing from a T1 connected to the DS1 in the DEFINITY.  
If a TN767E circuit pack detects certain I-CSU/T1 Sync Splitter hardware errors, it  
will notify maintenance. When the maintenance subsystem receives notification  
of the error, it will execute this Loss of Signal Inquiry test. The test, in addition to  
querying for a Loss Of Signal alarm condition, will also query the TN767E board  
to confirm the error. A Minor or Warning alarm will be raised depending on the  
severity of the error. The trunks on the board may be taken out of service if the  
error is deemed serious.  
If a Loss Of Signal alarm and an I-CSU/T1 Sync Splitter error co-exist, the Loss Of  
Signal alarm condition will take priority and the board and all trunks on the board  
will be put in the out-of-service state. Errors will be logged, however, for both.  
When the maintenance subsystem receives notification that the ICSU/T1 Sync  
Splitter hardware error condition no longer exists, maintenance will restore the  
board and all trunks to their previous service state if the alarm can be cleared (no  
other errors or Loss Of Signal alarm exist).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-567  
Table 3-239. TEST #138 Loss of Signal Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
2100  
2000  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of  
service state. The system will try to restore the circuit pack within 15  
minutes. When no faults are detected for 15 minutes, the DS1 interface  
circuit pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against  
the associated trunk circuits. If the facility is OK and the error occurs  
again after 15 minutes, escalate this problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-568  
Table 3-239. TEST #138 Loss of Signal Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
DS1 Interface circuit pack detects a Loss of Signal alarm. The physical link is  
broken or the remote DS1 endpoint is down. All trunks or ports of this DS1  
interface circuit pack are out-of-service. If the DS1 Interface circuit pack is  
designated as the supplier of the system synchronization source, then the  
system synchronization maintenance will adopt a source elsewhere. Refer to  
"SYNC (Synchronization)" section for details.  
1. If the DS1 Interface circuit pack connects to a T1 facility, call the vendor of  
the T1 carrier to diagnose the remote DS1 endpoint. If the DS1 Interface  
circuit pack connects directly to a switch, call the system technician of the  
remote switch to diagnose the DS1 endpoint.  
2. Check the physical connection of the DS1 Interface circuit pack and the  
cable. If a 120A1 CSU Module/T1 Sync Splitter is physically connected to  
a TN767E board on the back of the port carrier, check the physical  
connection of the CSU Module/T1 Sync Splitter and make sure the  
Network Interface cable is plugged into the CSU Module’s/T1 Sync  
Splitter’s NETWORK jack.  
1300  
FAIL  
The CSU Module or the T1 Sync Splitter is missing. The Near-End CSU Type  
field on the add ds1 form has been administered as integrated but the 120A1  
CSU Module/T1 Sync Splitter is not physically connected to the TN767E board  
on the back of the port carrier.  
1. If using the 120A1 CSU Module/T1 Sync Splitter, plug the CSU Module/T1  
Sync Splitter into the TN767E circuit pack’s connector on the I/O  
connector panel on back of the carrier. Otherwise, change the Near-End  
CSU Type field using the change ds1 form to other.  
2. Run the test again.  
1301  
FAIL  
The 120A1 CSU Module or the T1 Sync Splitter is physically connected to the  
TN767E board on the back of the port carrier but the Near-End CSU Type field  
on the add ds1 form has not been administered as integrated.  
1. If the 120A1 CSU Module/T1 Sync Splitter is to be used, use the change  
ds1 command to change the Near-End CSU Type field to integrated.  
Otherwise, physically remove the 120A1 CSU Module/T1 Sync Splitter  
from the back of the port carrier.  
2. Run the test again.  
1302  
FAIL  
Attempting to use the 120A1 CSU Module with a TN767E circuit pack that is  
configured for 32-channel (2.048 Mbps) operation. The CSU Module only  
works with a DS1 board configured for 24-channel (1.544 Mbps) operation in  
the United States of America.  
1. If the 120A1 CSU Module is to be used, physically remove the TN767E  
circuit pack and reconfigure for 24-channel (1.544 Mbps) operation.  
2. Reinsert the circuit pack and run the test again.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-569  
Table 3-239. TEST #138 Loss of Signal Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1303  
FAIL  
The DS1 circuit pack Suffix is incorrect for CSU Module/T1 Sync Splitter  
administration. The Near-End CSU Type field on the add ds1 form has been  
administered as integrated but the DS1 circuit pack is not a TN767E or later  
suffix DS1 board.  
1. If the CSU Module or the T1 Sync Splitter is to be used, and the Near-End  
CSU Type field is set to integrated to allow for CSU Module/T1 Sync  
Splitter administration, remove the circuit pack and replace it with a  
TN767E or later suffix board. Otherwise use the change ds1 command to  
change the Near-End CSU Type field to other.  
1310  
1311  
FAIL  
FAIL  
The DS1 Board Loopback (BLB) demand test (#1209) failed.  
1. Repeat the test using the test ds1-loop UUCSS ds1/csu-loopback-tests  
command.  
2. If the BLB test continues to fail, then replace the TN767E circuit pack.  
3. Run this test again.  
The Integrated CSU (I-CSU) Module Equipment Loopback (ELB) test (#1210)  
failed. This test is executedduring ICSU/T1 Sync Splitter power-up/reset (the  
TN767E board is physically inserted and the CSU Module/T1 Sync Splitter is  
already installed) or when the 120A CSU Module/T1 Sync Splitter is plugged  
on to an already initialized DS1 board. The ELB test is also executed as part of  
the command test ds1-loop UUCSS ds1/csu-loopback-tests.  
1. Execute test ds1-loop UUCSS ds1/csu-loopback-tests.  
2. If the ELB test continues to fail, then either the TN767E board, the CSU  
Module/T1 Sync Splitter, or the I/O cable between the backplane and the  
CSU Module/T1 Sync Splitter (or any combination thereof) has failed.  
Attempt to isolate the problem to one of these areas. Begin by replacing  
the CSU Module/T1 Sync Splitter and running the test ds1-loop UUCSS  
ds1/csu-loopback-tests command again.  
3. If the ELB test continues to fail, then replace the TN767E board and run  
test ds1-loop UUCSS ds1/csu-loopback-tests again.  
4. If the ELB test continues to fail, the problem could be in the I/O cable  
between the backplane and the CSU Module/T1 Sync Splitter.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-570  
Table 3-239. TEST #138 Loss of Signal Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1312  
FAIL  
The Integrated CSU (I-CSU) Module Repeater Loopback (RLB) test (#1211)  
failed. This test is executed during ICSU/T1 Sync Splitter power-up/reset (the  
TN767E board is physically inserted and the CSU Module/T1 Sync Splitter is  
already installed), or when the 120A1 CSU Module/T1 Sync Splitter is plugged  
on to an already initialized DS1 board. The RLB test is also executed as part of  
the command test ds1-loop UUCSS ds1/csu-loopback-tests.  
1. Execute test ds1-loop UUCSS ds1/csu-loopback-tests.  
2. If the RLB test continues to fail, then replace the CSU Module/T1 Sync  
Splitter.  
3. Run this test again.  
1313  
FAIL  
The TN767E circuit pack could not deactivate a CPE Loopback Jack  
loopback.  
1. Execute test ds1-loop UUCSS end-loopback/span-test.  
2. If the attempt to deactivate the CPE Loopback Jack is not successful,  
check the cabling and investigate the problem at the CPE Loopback  
Jack.  
3. Run the test again.  
1314  
1320  
FAIL  
FAIL  
The TN767E circuit pack could not deactivate a far-end CSU loopback.  
1. Execute test ds1-loop UUCSS end-loopback/span-test.  
A CSU Module/T1 Sync Splitter hardware failure or an ICSU/T1 Sync Splitter  
serial interface audit failure was detected by the TN767E DS1 circuit pack.  
1. Replace the CSU Module/T1 Sync Splitter, and then run the test again.  
2. If the test continues to fail with this error code, replace the TN767E and  
run the test again.  
3. If the test continues to fail with this error code, the problem could be in the  
I/O cable between the backplane and the CSU Module/T1 Sync Splitter.  
1321  
FAIL  
DTE LOS (loss of signal) was detected between the TN767E DS1 board and  
the 120A1 CSU Module or the T1 Sync Splitter. Either the TN767E board, the  
120A1 CSU Module/T1 Sync Splitter, or the I/O cable between the backplane  
and the 120A1 CSU Module or the 401A T1 Sync Splitter (or any combination  
thereof) has failed. Attempt to isolate the problem to one of these areas.  
1. Replace the CSU Module/T1 Sync Splitter and run the test again.  
2. If the test continues to fail with this error code, then replace the TN767E  
board and run the test again.  
3. If the test continues to fail with this error code, the problem could be in the  
I/O cable between the backplane and the 120A1 CSU Module or the 401A  
T1 Sync Splitter.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-571  
Table 3-239. TEST #138 Loss of Signal Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1322  
FAIL  
No 5 volts power detected from the TN767E circuit pack to the 120A1 CSU  
Module/T1 Sync Splitter. Problem probably due to an open fuse on the DS1  
board or a faulty ICSU/T1 Sync Splitter. NOTE Do not swap DS1 boards as  
this may open the fuse on the new board.  
1. Remove the TN767E from the system and reinsert.  
2. Run the test again once the board has finished its reset.  
3. If the test continues to fail with this error code, then replace the CSU  
Module/T1 Sync Splitter and run the test again.  
4. If the test continues to fail with this error code, the problem could be in the  
I/O cable between the backplane and the 120A1 CSU Module or the 401A  
T1 Sync Splitter.  
5. If the test contines to fail with this error code, then escalate this problem.  
1323  
1324  
FAIL  
A service-affecting CSU Module/T1 Sync Splitter audit failure was detected by  
the TN767E DS1 circuit pack. All administered ports on the DS1 circuit pack  
are affected and maintenance software will place the ports into the  
out-of-service state.  
1. Replace the 120A1 CSU Module/T1 Sync Splitter.  
FAIL  
A non-service-affecting CSU Module/T1 Sync Splitter audit failure was  
detected by the TN767E DS1 circuit pack. No ports should be affected. No  
immediate action is required. These errors indicate that the CSU Module/T1  
Sync Splitter hardware may have a problem, and that it should be replaced  
when practical to avoid further deterioration.  
PASS  
DS1 signal is present and the physical link is healthy. In addition, no  
Integrated CSU errors are detected.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-572  
Table 3-239. TEST #138 Loss of Signal Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
Blue Alarm Inquiry Test (#139)  
The Blue Alarm is a signal sent by the remote DS1 endpoint when it is  
out-of-service. The Blue Alarm Inquiry Test checks the blue alarm status of the  
remote DS1 endpoint.  
When the DS1 Interface circuit pack detects a Blue Alarm signal from the remote  
DS1 endpoint, the circuit pack will transmit a Yellow alarm to the remote DS1  
endpoint and send a BLUE ALARM message to the maintenance software. When  
the Blue alarm is confirmed, the maintenance software places all trunks of the  
DS1 Interface circuit pack into the out-of-service state. The inquiry test will be run  
every 10 minutes until the Blue alarm is cleared.  
The DS1 Interface circuit pack takes 2 seconds to recognize and report a Blue  
alarm and 16 seconds to recognize and report the resolution of a Blue alarm.  
When the Blue alarm is cleared, the DS1 Interface circuit pack stops transmitting  
the Yellow alarm and places the trunks back into the service state before the Blue  
alarm occurs.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-573  
Line Loopback Alarm  
The Line Loopback (LLB) is used by the remote DS1 endpoint to put the ICSU or  
DS1 into a loopback mode. When the ICSU or DS1 Board is in the LLB mode, the  
arriving bit pattern is regenerated and sent back. Line Loopback (LLB) Alarm is  
activated when the in-band activate LLB bit pattern has been arriving  
continuously for 5 seconds on the DS1 line. LLB is deactivated when the in-band  
deactivate LLB bit pattern has been arriving continuously for 5 seconds on the  
DS1 line.  
Since LLB is a maintenance condition rendering all DS0 channels unavailable for  
signaling or bearer traffic, maintenance software treats this the same as a Blue  
Alarm.  
Payload Loopback Alarm  
The Payload Loopback (PLB) is used by the remote DS1 endpoint to put the  
switch DS1 into a loopback mode. PLB Alarm is activated when a network  
protocol activate bit pattern arrives over the 4-Kbps ESF data link on the DS1  
line. PLB is deactivated when a network protocol deactivate bit pattern arrives  
over the 4-Kbps ESF data link on the DS1 line.  
Since PLB is a maintenance condition rendering all DS0 channels unavailable for  
signaling or bearer traffic, maintenance software treats this the same as a Blue  
Alarm.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-574  
Table 3-240. TEST #139 Blue Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
2100  
2000  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the DS1 interface circuit  
pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, escalate this problem.  
FAIL  
The remote DS1 endpoint is out-of-service.  
1. If the DS1 interface circuit pack connects to a T1 facility, call the vendor of  
the T1 carrier to diagnose the remote endpoint.  
2. If the DS1 interface circuit pack connects directly to a switch, call the  
system technician of the remote switch to diagnose the DS1 endpoint.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-575  
Table 3-240. TEST #139 Blue Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1794  
FAIL  
The DS1 Interface circuit pack detects a Line Loopback Alarm (LLB).  
1. If the DS1 interface circuit pack connects to a T1 facility, call the vendor of  
the T1 carrier to diagnose the remote DS1 endpoint.  
2. If the DS1 interface circuit pack connects directly to a switch, call the  
system technician of the remote switch to diagnose the DS1 endpoint.  
3. If the DS1 interface circuit pack connects directly to a line-side terminating  
device (for example, a PRI terminal adapter), call the vendor of the  
terminating device to diagnose the equipment.  
1795  
FAIL  
The DS1 Interface circuit pack detects a Payload Loopback Alarm (PLB). If the  
DS1 Interface circuit pack connects to a leased T1 facility, call the vendor of  
the T1 carrier to diagnose the remote DS1 endpoint. If the DS1 Interface circuit  
pack connects directly to another DS1 board, call the system technician of the  
remote switch to diagnose the DS1 endpoint.  
PASS  
Remote DS1 endpoint is in-service. Neither a Blue alarm nor a Line Loopback  
alarm nor a Payload Loopback alarm is detected in the DS1 Interface circuit  
pack.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the busyout  
board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-576  
Red Alarm Inquiry Test (#140)  
DS1 Interface circuit pack raises a Red alarm when the framing pattern of the  
incoming DS1 bit stream has been lost. The Red Alarm Inquiry Test checks the  
framing status of a DS1 Interface circuit pack. DS1 Interface circuit pack takes 3  
seconds to recognize and report a Red alarm and 10 seconds to recognize and  
report the resolution of a Red alarm.  
When the DS1 Interface circuit pack detects a Red alarm, the circuit pack will  
transmit a Yellow alarm to the remote DS1 endpoint and send a RED ALARM  
message to the maintenance software. After the Red alarm is confirmed, the  
maintenance software places all trunks of the circuit pack into the out-of-service  
state. The inquiry test will be run every 10 minutes until the Red alarm is cleared.  
When the Red alarm is cleared, the DS1 Interface circuit pack will stop  
transmitting the Yellow alarm to the remote DS1 endpoint. The maintenance  
software restores all trunks of the DS1 Interface circuit pack to the service state  
before the Red alarm occurs.  
Loss of Multiframe Alarm: If the DS1 Interface circuit pack is administered using  
DMI-BOS signaling, the DS1 Interface circuit pack raises a Loss of Multiframe  
Alarm (LMA) when it cannot interpret the incoming signaling bits to synchronize  
to the multiframe pattern received in the 24th channel. Once DS1 Interface circuit  
pack detects an LMA, the circuit pack will transmit a Remote Multiframe Alarm  
(RMA) to the remote DS1 endpoint. Maintenance software handles both Red  
alarm and LMA alarm(s) using the same mechanism.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-577  
Table 3-241. TEST #140 Red Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
2100  
2000  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the DS1 interface circuit  
pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, escalate this problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-578  
Table 3-241. TEST #140 Red Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
The DS1 Interface circuit pack detects a Red alarm. An out-of-frame condition  
occurs on the DS1 Interface circuit pack. DS1 Interface circuit pack will  
transmit a Yellow alarm to the remote DS1 endpoint until the Red alarm is  
retired.  
1. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding. Likewise, verify that any  
intermediate CSU’s are administered correctly.  
2. If the DS1 interface circuit pack connects to a T1 facility, call the vendor of  
the T1 carrier to diagnose the remote DS1 endpoint. If the DS1 interface  
circuit pack connects directly to a switch, call the system technician of the  
remote switch to diagnose the DS1 endpoint.  
3. Check the physical connectivity of the DS1 pack and of the cable.  
4. If this continues to fail, escalate this problem.  
1
FAIL  
The DS1 interface circuit pack detected a loss of multiframe alarm (LMA). An  
out of frame condition occurred on the DS1 interface circuit pack. The DS1  
interface circuit pack will transmit a remote multiframe alarm (RMA) to the  
remote DS1 endpoint until the LMA is retired.  
1. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding. Likewise, verify that any  
intermediate CSU’s are administered correctly.  
2. If the DS1 interface circuit pack connects to a T1 facility, call the vendor of  
the T1 carrier to diagnose the remote DS1 endpoint. If the DS1 interface  
circuit pack connects directly to a switch, call the system technician of the  
remote switch to diagnose the DS1 endpoint.  
3. Check the physical connectivity of the DS1 pack and of the cable.  
4. If this continues to fail, escalate this problem.  
PASS  
No Red alarm is detected on DS1 Interface circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-579  
Table 3-241. TEST #140 Red Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the busyout  
board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Continued on next page  
Yellow Alarm Inquiry Test (#141)  
Receiving a Yellow alarm from remote DS1 endpoint indicates that the remote  
DS1 endpoint has an out-of-frame condition. The Yellow Alarm Inquiry Test is  
used to determine whether the remote DS1 endpoint is transmitting a Yellow  
alarm. The DS1 Interface circuit pack takes 500 msec to recognize and report a  
Yellow alarm and 500 msec to recognize and report that a Yellow alarm condition  
is cleared.  
When the DS1 Interface circuit pack detects a Yellow alarm from the remote DS1  
endpoint, it will send a YELLOW-ALARM uplink message to the maintenance  
software. After the maintenance software receives the YELLOW-ALARM  
message, the Yellow Alarm Inquiry Test is run to confirm the Yellow alarm. Once  
the Yellow alarm is confirmed, the maintenance software places all trunks on the  
circuit pack into the out-of-service state. The Inquiry Test will be run every 10  
minutes until the Yellow alarm is cleared.  
When the Yellow alarm is cleared, the maintenance software restores all trunks on  
the DS1 Interface circuit pack back to their previous service state before the  
Yellow alarm is raised.  
This Yellow Alarm corresponds to the yellow F2 state documented in CCITT  
Download from Www.Somanuals.com. All Manuals Search And Download.  
recommendation I.431.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-580  
Remote Multiframe Alarm: Remote Multiframe Alarm (RMA) indicates that the  
remote DS1 endpoint is in a Loss of Multiframe Alarm condition while the DS1  
Interface circuit pack is administered using the DMI-BOS common channel  
signaling. The RMA is handled as a Yellow alarm.  
Yellow F5 State Alarm: For 32-channel E1 operation with CRC4 on, the F5 fault  
state is defined as a fault in the user-network interface, specifically in the  
direction from the user (PBX) to the network. Refer to CCITT recommendation  
I.431  
Table 3-242. TEST #141 Yellow Alarm Inquiry Test  
Error  
Code  
2100  
2000  
Test Result  
Description/ Recommendation  
ABORT  
Internal system error  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more  
of the following symptoms may appear.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with  
error code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the  
system, and all of the trunks for this circuit pack are placed into the  
out of service state. The system will try to restore the circuit pack  
within 15 minutes. When no faults are detected for 15 minutes, the  
DS1 interface circuit pack is restored to normal operation. All of the  
trunks for the DS1 interface circuit pack are then returned to the in  
service state. Hyperactivity is often caused by the associated facility.  
In such a case, faults (such as slips, misframes, or blue alarms)  
would be entered in the error log. In addition, many hardware errors  
would be logged against the associated trunk circuits. If the facility is  
OK and the error occurs again after 15 minutes, escalate this  
problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-581  
Table 3-242. TEST #141 Yellow Alarm Inquiry Test — Continued  
Error  
Code  
Test Result  
Description/ Recommendation  
FAIL  
The DS1 interface circuit pack detected a yellow alarm sent by the remote  
DS1 endpoint. An out of frame condition occurred at the DS1 endpoint.  
1
FAIL  
FAIL  
The DS1 Interface circuit pack detects a Remote Multiframe Alarm sent by  
the remote DS1 endpoint. An out-of-frame condition occurs on the remote  
DS1 endpoint.  
2
The DS1 Interface circuit pack is reporting a yellow F5 State alarm. There is  
a fault in the user-network interface from the user (PBX) to the network.  
1. Verify that both endpoints of the DS1 link are administered using the  
same signaling mode, framing mode, and line coding. Likewise, verify  
that any intermediate CSUs are administered correctly.  
2. If the DS1 interface circuit pack connects to a T1 facility, call the vendor  
of the T1 carrier to diagnose the remote DS1 endpoint. If the DS1  
interface circuit pack connects directly to a switch, call the system  
technician of the remote switch to diagnose the DS1 endpoint.  
3. Check the physical connectivity of the DS1 pack and of the cable.  
4. If this continues to fail, escalate this problem.  
PASS  
No Yellow alarm nor Remote Multiframe Alarm nor F5 State Alarm is  
received from the remote DS1 endpoint.  
0
NO BOARD The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an  
incorrect board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add  
ds1 UUCSS command to administer the DS1 interface if it is not  
already administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-582  
Major Alarm Inquiry Test (#142)  
The Major alarm raised by a DS1 Interface circuit pack indicates that the average  
bit error rate on the DS1 facility is greater than 1/1000. The Major Alarm Inquiry  
Test is used to determine that the received DS1 bit error rate is greater than  
1/1000. When D4 framing mode is selected, the DS1 Interface circuit pack takes  
16 seconds to recognize and report a Major alarm and 16 seconds to recognize  
and report that a Major alarm condition is cleared. If ESF framing mode is  
selected, the DS1 Interface circuit pack takes 10 seconds to recognize and  
report a Major alarm and 10 seconds to recognize and report that a Major alarm  
condition is cleared.  
When the DS1 Interface circuit pack detects a Major alarm, it will send a  
MAJOR-ALARM message to the maintenance software. After the maintenance  
software receives a MAJOR-ALARM message, the Major Alarm Inquiry Test is  
initiated to confirm the Major alarm on the DS1 Interface circuit pack. The Inquiry  
Test will be run every 10 minutes until the Major alarm is cleared. The  
maintenance software places all trunks on the circuit pack in the out-of-service  
state if the Major alarm persists for more than 20 minutes.  
When the Major alarm is cleared, the maintenance software restores all trunks on  
the circuit pack to their previous service state before a Major alarm occurs.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-583  
Table 3-243. TEST #142 Major Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
2100  
2000  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the DS1 interface circuit  
pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, escalate this problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-584  
Table 3-243. TEST #142 Major Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
The DS1 Interface circuit pack detects a Major alarm. The DS1 bit error rate is  
greater than 1/1000.  
1. The performance of DS1 link between DS1 Interface circuit pack and  
remote DS1 endpoint is very poor. If the DS1 Interface circuit pack is  
TN767, enter list measurement ds1-log UUCSS command to read the  
error seconds measurement.  
2. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
3. If the DS1 interface circuit pack connects to a T1 facility, call the vendor of  
the T1 carrier to diagnose the remote DS1 endpoint. If the DS1 interface  
circuit pack connects directly to a switch, call the system technician of the  
remote switch to diagnose the DS1 endpoint.  
4. Check the physical connectivity of the DS1 pack and of the cable.  
5. Replace the local DS1 interface circuit pack, and repeat the test.  
No Major alarm is detected in DS1 Interface circuit pack.  
PASS  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the busyout  
board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
Minor Alarm Inquiry Test (#143)  
The Minor alarm raised by a DS1 Interface circuit pack indicates that the average  
bit error rate on the DS1 facility is greater than 1/1,000,000, but less than 1/1000.  
The Minor Alarm Inquiry Test is used to determine that the received DS1 bit error  
rate is greater than 1/1,000,000 and less than 1/1000. When D4 framing mode is  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-585  
selected, the DS1 Interface circuit pack takes 41 minutes to recognize and report  
a Minor alarm and 41 minutes to recognize and report that a Minor alarm  
condition is cleared. If ESF framing mode is selected, the DS1 Interface circuit  
pack takes 10 minutes to recognize and report a Minor alarm and 10 minutes to  
recognize and report that a Minor alarm condition is cleared.  
When the DS1 Interface circuit pack detects a Minor alarm condition, it will send  
a MINOR-ALARM message to the maintenance software. After the maintenance  
software receives a MINOR-ALARM message, the Minor Alarm Inquiry Test is  
initiated to confirm the Minor alarm. All trunks on the circuit pack are kept in the  
in-service state after the Minor alarm is confirmed. The Minor Alarm Inquiry Test  
is run every 10 minutes until the Minor alarm is cleared.  
Table 3-244. TEST #143 Minor Alarm Inquiry Test  
Error  
Code  
2100  
2000  
Test Result  
Description/ Recommendation  
ABORT  
Internal system error  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more  
of the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the  
system, and all of the trunks for this circuit pack are placed into the out  
of service state. The system will try to restore the circuit pack within 15  
minutes. When no faults are detected for 15 minutes, the DS1 interface  
circuit pack is restored to normal operation. All of the trunks for the  
DS1 interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in  
the error log. In addition, many hardware errors would be logged  
against the associated trunk circuits. If the facility is OK and the error  
occurs again after 15 minutes, escalate this problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-586  
Table 3-244. TEST #143 Minor Alarm Inquiry Test — Continued  
Error  
Code  
Test Result  
Description/ Recommendation  
FAIL  
The DS1 Interface circuit pack detects a Minor alarm. The DS1 bit error rate  
is greater than 1/1,000,000 and less than 1/1000.  
1. The performance of DS1 link between DS1 Interface circuit pack and  
remote DS1 endpoint is poor. If DS1 Interface circuit pack is TN767,  
enter list measurement ds1-log UUCSS command to read the error  
seconds measurement.  
2. Verify that both endpoints of the DS1 link are administered using the  
same signaling mode, framing mode, and line coding.  
3. If the DS1 interface circuit pack connects to a T1 facility, call the vendor  
of the T1 carrier to diagnose the remote DS1 endpoint. If the  
DS1interface circuit pack connects directly to a switch, call the system  
technician of the remote switch to diagnose the DS1 endpoint.  
4. Check the physical connection of the DS1 pack and of the cable.  
5. If this continues to fail, escalate this problem.  
PASS  
No Minor alarm is detected in DS1 Interface circuit pack.  
0
NO BOARD The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
Slip Alarm Inquiry Test (144)  
Slips occur when transmitter and receiver are not running at precisely the same  
clock rate. The DS1 Interface circuit pack can detect both positive and negative  
slips on the DS1 facility. The Slip Alarm Inquiry Test is used to acquire the total  
number of slips occurred on a DS1 link.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-587  
When the DS1 Interface circuit pack detects a slip condition, the circuit pack will  
increase the on-board slip counter by 1. A SLIP-COUNT message is  
spontaneously sent to the system software after the counter reaches a threshold  
(for example, 88). When the maintenance software receives the SLIP-COUNT  
message, the Slip Alarm Inquiry Test is initiated to query the slip counters on DS1  
Interface circuit pack and total the slip counts in the maintenance software.  
If the count of slips is over the threshold, a Minor alarm is raised against the DS1  
Interface circuit pack. All trunks of the DS1 Interface circuit pack are still in the  
in-service state. If the DS1 Interface circuit pack is used to supply the system  
synchronization source, the MINOR alarm will initiate a synchronization source  
switch. See “TDM-BUS” and "SYNC (Synchronization)" for details.  
Table 3-245. TEST #144 Slip Alarm Inquiry Test  
Error  
Code  
2100  
2000  
Test Result  
Description/ Recommendation  
ABORT  
Internal system error  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more  
of the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the  
system, and all of the trunks for this circuit pack are placed into the  
out of service state. The system will try to restore the circuit pack  
within 15 minutes. When no faults are detected for 15 minutes, the  
DS1 interface circuit pack is restored to normal operation. All of the  
trunks for the DS1 interface circuit pack are then returned to the in  
service state. Hyperactivity is often caused by the associated facility.  
In such a case, faults (such as slips, misframes, or blue alarms) would  
be entered in the error log. In addition, many hardware errors would  
be logged against the associated trunk circuits. If the facility is OK  
and the error occurs again after 15 minutes, escalate this problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-588  
Table 3-245. TEST #144 Slip Alarm Inquiry Test — Continued  
Error  
Code  
Test Result  
Description/ Recommendation  
1 to 88 FAIL  
The DS1 interface circuit pack detected a slip alarm. The error code equals  
the number of slips detected by the DS1 interface circuit pack since the last  
slip alarm inquiry test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the DS1 interface circuit pack is a TN767, enter the list measurement  
ds1-log UUCSS command to read the error seconds measurement.  
3. Verify that both endpoints and all intermediate equipment of the DS1 link  
are administered using the same signaling mode, framing mode, and  
line coding.  
4. If the DS1 interface circuit pack connects to a T1 facility, call the vendor  
of the T1 carrier to diagnose the remote DS1 endpoint. If the DS1  
interface circuit pack connects directly to a switch, call the system  
technician of the remote switch to diagnose the DS1 endpoint.  
5. Check the active alarm and error logs for recent alarms and errors  
against the synchronization (SYNC). Follow the suggested repair  
procedure for these errors.  
6. Check the physical connectivity of the DS1 pack and of the cable.  
7. If this continues to fail, escalate this problem.  
PASS  
No Slip alarm is detected on the DS1 Interface circuit pack.  
0
NO BOARD The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add  
ds1 UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-589  
Misframe Alarm Inquiry Test (#145)  
Misframe Alarm indicates that framing bits observed on a DS1 Interface circuit  
pack are in error. Misframe Alarm Inquiry Test queries the total number of  
misframes that occurred on a DS1 Interface circuit pack since the last inquiry.  
When the DS1 Interface circuit pack detects a misframe error, it will increase its  
misframe counter by 1. If the counter reaches the threshold, a  
MISFRAME-COUNT message is automatically sent to the switch maintenance  
software. After the maintenance software receives the MISFRAME-COUNT  
message, the Misframe Alarm Inquiry Test is initiated to collect the misframe  
counts from the DS1 Interface circuit pack.  
When the threshold of misframes is reached, if the DS1 Interface circuit pack is  
supplying the system synchronization source, then a switching synchronization  
source message is sent to the TDM Bus Clock. See TDM-BUS (TDM Bus)  
Maintenance documentation for details. A Minor alarm against the DS1 Interface  
circuit pack is raised, but all trunks of the DS1 Interface circuit pack are still in the  
in-service state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-590  
Table 3-246. TEST #145 Misframe Alarm Inquiry Test  
Error  
Code  
2100  
2000  
Test Result  
Description/ Recommendation  
ABORT  
Internal system error  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more  
of the following symptoms may appear.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the  
system, and all of the trunks for this circuit pack are placed into the  
out of service state. The system will try to restore the circuit pack  
within 15 minutes. When no faults are detected for 15 minutes, the  
DS1 interface circuit pack is restored to normal operation. All of the  
trunks for the DS1 interface circuit pack are then returned to the in  
service state. Hyperactivity is often caused by the associated facility.  
In such a case, faults (such as slips, misframes, or blue alarms) would  
be entered in the error log. In addition, many hardware errors would  
be logged against the associated trunk circuits. If the facility is OK  
and the error occurs again after 15 minutes, escalate this problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-591  
Table 3-246. TEST #145 Misframe Alarm Inquiry Test — Continued  
Error  
Code  
Test Result  
Description/ Recommendation  
ANY  
FAIL  
The test failed because the DS1 interface circuit pack detected errors in the  
received framing bits pattern. The error code equals the number of  
misframes detected by the DS1 interface circuit pack since the last misframe  
alarm inquiry test. Major bit and minor bit error rate (error types 2561 and  
2817) error logs often accompany misframe alarms. Clearing the cause of  
these error logs may clear the misframes which are occurring.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the DS1 interface circuit pack is a TN767, enter the list measurement  
ds1-log UUCSS command to read the error seconds measurement.  
3. Verify that both endpoints and all intermediate equipment of the DS1 link  
are administered using the same signaling mode, framing mode, and  
line coding.  
4. If the DS1 interface circuit pack connects to a T1 facility, call the vendor  
of the T1 carrier to diagnose the remote DS1 endpoint. If the DS1  
interface circuit pack connects directly to a switch, call the system  
technician of the remote switch to diagnose the DS1 endpoint.  
5. Check the active alarm and error logs for recent alarms and errors  
against the synchronization (SYNC). Follow the suggested repair  
procedure for these errors.  
6. Check the physical connection of the DS1 pack and of the cable.  
7. If this continues to fail, escalate this problem.  
PASS  
No Misframe alarm is detected on the DS1 Interface circuit pack.  
0
NO BOARD The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-592  
Translation Update Test (#146)  
The Translation Update Test sends the circuit-pack-level information specified by  
System Administration to the DS1 Interface circuit pack. Translation includes the  
following data administered for a DS1 Interface circuit pack (see output of  
display ds1 UUCSS command): DS1 Link Length between two DS1 endpoints,  
Synchronization Source Control, All Zero Suppression, Framing Mode, Signaling  
Mode, Time Slot Number of 697-Hz Tone, Time Slot Number of 700-Hz Tone, etc.  
If a TN767E or later DS1 circuit pack is combined with a 120A CSU Module or a  
T1 Sync Splitter to form an Integrated CSU Module, this test will also send the  
administration for this Integrated CSU to the circuit pack to assure the board’s  
translations are correct. The administration of the CSU Module is done using the  
DS1 circuit pack administration form. Translation for the CSU Module includes  
the following data: Transmit LBO, Receive ALBO, Supply CPE Loopback Jack  
Power?, and so forth.  
Table 3-247. TEST #146 Translation Update Test  
Error  
Code  
Test Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system software error.  
FAIL  
1. Enter the display ds1 UUCSS command to verify the DS1 Interface  
circuit pack translation.  
PASS  
Translation data has been downloaded to the DS1 Interface circuit pack  
successfully.  
0
NO BOARD The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-593  
DS1 Board Loopback Test (#1209)  
This test is destructive.  
The DS1 Board Loopback (BLB) Test causes a loopback at the TN767E DS1  
board edge and tests DS1 board internal circuitry.  
The test is destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS ds1/csu-loopback-tests command.  
All trunks or ports on the DS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the BLB Test.  
When the BLB Test is initiated, maintenance software sends an appropriate  
message to the TN767E DS1 Interface circuit pack to start the test. The board will  
set up the BLB loopback, transmit a test pattern, and verify that the pattern is  
received unaltered through the loopback. If the transmitted and received pattern  
is different, the test fails.  
When the test is complete, all trunks or ports on the TN767E DS1 Interface circuit  
pack are restored to the in-service state after the release board command is  
entered  
Table 3-248. TEST #1209 DS1 Board Loopback Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry test ds1-loop UUCSS ds1/csu-loopback-tests at 1-minute intervals  
a maximum of 5 times.  
1005  
1015  
ABORT  
DS1 Board Loopback Test cannot be executed in the current configuration. To  
run this Test, the TN767E or later suffix DS1 must be administered for  
24-channel operation. The "Bit Rate"field on the DS1 circuit pack administration  
form must be set to "1.544" for 24-channel operation.  
ABORT  
Ports on the DS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter busyout board UUCSS to put all trunks or ports of the DS1 Interface  
circuit pack into the out-of-service state.  
2. Retry the command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-594  
Table 3-248. TEST #1209 DS1 Board Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1039  
ABORT  
The DS1 Interface circuit pack is providing timing for the system. Executing this  
test could cause major system disruption.  
If the DS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit  
pack via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the board  
is in a network requested loopback mode (Line loopback or Payload loopback).  
The hardware error log will indicate whether a Customer Loopback Jack Test,  
Far CSU Loopback Test, or the One-Way Span Test is executing or if the board  
is in line loopback or payload loopback mode. Only one long-duration  
loopback/span test can be active at a given time. Thus, if a loopback/span test  
is already active, that test must be terminated via the test ds1-loop UUCSS  
end-loopback/span-test command in order to execute this test.  
ABORT  
ABORT  
Internal system error  
2100  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-595  
Table 3-248. TEST #1209 DS1 Board Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the DS1 interface circuit  
pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, escalate this problem.  
FAIL  
DS1 Interface circuit pack failed the DS1 Board Loopback Test.  
1. Retry test ds1-loop UUCSS ds1/csu-loopback-tests.  
2. If the BLB test continues to fail, then replace the DS1 circuit pack.  
PASS  
The BLB test executed successfully. The test pattern was transmitted and  
received successfully up to the TN767E DS1 board edge.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-596  
Table 3-248. TEST #1209 DS1 Board Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the busyout  
board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
CSU Equipment Loopback Test (#1210)  
This test is destructive.  
The CSU Equipment Loopback (ELB) Test causes a loopback at the near-edge of  
the local 120A CSU Module or T1 Sync Spilitter, and tests the connection from the  
TN767E DS1 board to the CSU Module/T1 Sync Splitter (DS1 board edge  
interconnecting cable, and CSU Module/T1 Sync Splitter edge). This test will only  
be performed if the 120A CSU Module/T1 Sync Splitter is present, administered,  
and connected to a 1.544Mbps TN767E DS1 circuit pack on the back of the port  
carrier.  
The test is destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS ds1/csu-loopback-tests command.  
All trunks or ports on the DS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the ELB Test.  
When the ELB Test is initiated, maintenance software sends an appropriate  
message to the TN767E DS1 Interface circuit pack to start the test. The board  
sets up the ELB loopback, transmit a test pattern, and verify that the pattern is  
received unaltered through the loopback. If the transmitted and received pattern  
Download from Www.Somanuals.com. All Manuals Search And Download.  
is different, the test fails.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-597  
In addition, the DS1 circuit pack hardware applies a DC current while the test is  
running in order to detect any broken wires which may not be detected by the  
loopback pattern.  
When the test is complete, all trunks or ports on the TN767E DS1 Interface circuit  
pack are restored to the in-service state after the release board command is  
entered.  
Table 3-249. TEST #1210 CSU Equipment Loopback Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry test ds1-loop UUCSS ds1/csu-loopback-tests at 1-minute intervals  
a maximum of 5 times.  
1005  
ABORT  
CSU Equipment Loopback Test cannot be executed in the current  
configuration. To run this test, the Near-End CSU Type field on the DS1 circuit  
pack administration form must be set to integrated and the "Bit Rate" field must  
be set to "1.544" (24-channel operation).  
1. Use the change ds1 UUCSS command to set the Near-End CSU Type field  
on the DS1 circuit pack administration form to integrated, and/or change  
the "Bit Rate" field to "1.544" if the board is to be used in the 24-channel  
configuration.  
2. Retry test ds1-loop UUCSS ds1/csu-loopback-tests.  
1015  
1039  
ABORT  
ABORT  
Ports on the DS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
DS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
The DS1 Interface circuit pack is providing timing for the system. Executing this  
test could cause major system disruption.  
If the DS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit pack  
via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-598  
Table 3-249. TEST #1210 CSU Equipment Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the board  
is in a network requested loopback mode (Line loopback or Payload loopback).  
The hardware error log will indicate whether a Customer Loopback Jack Test,  
Far CSU Loopback Test, or the One-Way Span Test is executing or if the board  
is in line loopback or payload loopback mode. Only one long-duration  
loopback/span test can be active at a given time. Thus, if a loopback/span test  
is already active, that test must be terminated via the test ds1-loop UUCSS  
end-loopback/span-test command in order to execute this test.  
1951  
ABORT  
The CSU Equipment Loopback Test could not be executed because the 120A  
CSU Module/T1 Sync Splitter was not physically installed. Physically connect  
the 120A CSU Module/T1 Sync Splitter to the TN767E board on the back of the  
port carrier.  
ABORT  
ABORT  
Internal system error  
2100  
2000  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the DS1 interface circuit  
pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, escalate this problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-599  
Table 3-249. TEST #1210 CSU Equipment Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
DS1 Interface circuit pack failed the CSU Equipment Loopback Test.  
1. Retry test ds1-loop UUCSS ds1/csu-loopback-tests.  
FAIL  
2. If the ELB test continues to fail, then either the TN767E board, the CSU  
Module/T1 Sync Splitter, or the I/O cable between the backplane and the  
120A1 CSU Module or the 401A T1 Sync Splitter (or any combination  
thereof) has failed. Attempt to isolate the problem to one of these areas.  
Replace the CSU Module/T1 Sync Splitter and running test ds1-loop  
UUCSS ds1/csu-loopback-tests again.  
3. If the ELB test continues to fail, then replace the TN767E board and run test  
ds1-loop UUCSS ds1/csu-loopback-tests again.  
4. If the ELB test continues to fail, the problem could be in the I/O cable  
between the backplane and the 120A1 CSU Module or the 401A T1 Sync  
Splitter.  
PASS  
The ELB test executed successfully. The test pattern was transmitted and  
received successfully over the connection from the TN767E DS1 board to the  
near-edge of the 120A1 CSU Module/T1 Sync Splitter.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the busyout  
board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-600  
CSU Repeater Loopback Test (#1211)  
This test is destructive.  
The CSU Repeater Loopback (RLB) Test causes a loopback at the far-edge of  
the local 120A CSU Module or T1 Sync Splitter, and tests the connection from the  
TN767E DS1 board to and including the CSU Module/T1 Sync Splitter circuitry.  
This test will only be performed if the 120A CSU Module/T1 Sync Splitter is  
present, administered, and connected to a 1.544 Mbps TN767E DS1 circuit pack  
on the back of the port carrier.  
The test is destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS ds1/csu-loopback-tests command.  
All trunks or ports on the DS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the RLB Test.  
When the RLB Test is initiated, maintenance software sends an appropriate  
message to the TN767E DS1 Interface circuit pack to start the test. The board will  
set up the RLB loopback, transmit a test pattern, and verify that the pattern is  
received unaltered through the loopback. If the transmitted and received pattern  
is different, the test fails.  
In addition, the DS1 circuit pack hardware applies a DC current while the test is  
running in order to detect any broken wires which may not be detected by the  
loopback pattern.  
When the test is complete, all trunks or ports on the TN767E DS1 Interface circuit  
pack are restored to the in-service state after the release board command is  
entered.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-601  
Table 3-250. TEST #1211 CSU Repeater Loopback Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry test ds1-loop UUCSS ds1/csu-loopback-tests at 1-minute  
intervals a maximum of 5 times.  
1005  
ABORT  
CSU Repeater Loopback Test cannot be executed in the current  
configuration. To run this test, the Near-End CSU Type field on the DS1circuit  
pack administration form must be set to integrated and the "Bit Rate" field on  
the DS1 circuit pack administration form must be set to "1.544" (24-channel  
configuration).  
1. Use the change ds1 UUCSS command to set the Near-End CSU Type  
field on the DS1 circuit pack administration form to integrated, and/or  
change the "Bit Rate" field to "1.544" if the board is to be used in  
24-channel configuration.  
2. Retry test ds1-loop UUCSS ds1/csu-loopback-tests.  
1015  
1039  
ABORT  
ABORT  
Ports on the DS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of  
the DS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
The DS1 Interface circuit pack is providing timing for the system. Executing  
this test could cause major system disruption.  
If the DS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit  
pack via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the  
board is in a network requested loopback mode (Line loopback or Payload  
loopback). The hardware error log indicates whether a Customer Loopback  
Jack Test, Far CSU Loopback Test, or the One-Way Span Test is executing or  
if the board is in line loopback or payload loopback mode. Only one  
long-duration loopback/span test can be active at a given time. Thus, if a  
loopback/span test is already active, that test must be terminated via the test  
ds1-loop UUCSS end-loopback/span-test command in order to execute this  
test.  
1951  
ABORT  
The CSU Repeater Loopback Test could not be executed because the 120A  
CSU Module/T1 Sync Splitter was not physically installed. Physically connect  
the 120A1 CSU Module/T1 Sync Splitter to the TN767E board on the back of  
the port carrier.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-602  
Table 3-250. TEST #1211 CSU Repeater Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
2100  
2000  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of  
service state. The system will try to restore the circuit pack within 15  
minutes. When no faults are detected for 15 minutes, the DS1 interface  
circuit pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against  
the associated trunk circuits. If the facility is OK and the error occurs  
again after 15 minutes, escalate this problem.  
FAIL  
DS1 Interface circuit pack failed the CSU Repeater Loopback Test.  
1. Retry test ds1-loop UUCSS ds1/csu-loopback-tests.  
2. If the RLB test continues to fail, and the CSU Equipment Loopback Test  
(#1210) passed, then replace the CSU Module/T1 Sync Splitter.  
PASS  
The RLB test executed successfully. The test pattern was transmitted and  
received successfully over the connection from the TN767E DS1 board to the  
far-edge of the 120A1 CSU Module/T1 Sync Splitter.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-603  
Table 3-250. TEST #1211 CSU Repeater Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
CPE Loopback Jack Test (#1212)  
This test is destructive.  
The CPE Loopback Jack (CLJ-LB) Test causes a loopback at the CPE Loopback  
Jack and tests the building wiring connection between the TN767E DS1 board  
and the CPE Loopback Jack.  
The test is highly destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS cpe-loopback-jack-test-begin  
[number-of-bits bit-pattern] command. The System technician has the choice  
of entering a loopback activation code on the command line or using the default  
code (0x47F).  
All trunks or ports on the DS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the CPE Loopback  
Jack Test.  
The CPE Loopback Jack Test has the TN767E DS1 Interface circuit pack transmit  
a loopback activation code to the CPE Loopback Jack, waits up to 10 seconds  
for return of the code to verify the loopback has been established, transmits a  
framed 3-in-24 test pattern, begins counting bit errors in the received test  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-604  
pattern, and returns a PASS result to indicate that the pattern was successfully  
sent. If the loopback is not established within the 10 seconds, the test returns  
FAIL.  
The status of the CPE Loopback Jack test will be available in the hardware error  
log via error type 3900. Several distinct aux values will be used to give the user  
information of the status of the test.  
The list measurements ds1 summary command will display the length of time the  
test has been running (Test Duration field) and number of bit errors detected  
(Loopback/Span Test Bit-Error Count field). If the test pattern is being passed  
through the loopback cleanly, the number of bit errors should be very low. The  
command will also display the type of loopback/span test executing (Test field),  
the type of pattern generated for the loopback/span test (Pattern field), and  
whether the pattern (3-in-24 Pattern) is synchronized (Synchronized Field).  
To terminate the test, enter test ds1-loop UUCSS end-loopback/span-test  
command or the release board. Using the release board command restores all  
trunks or ports on the TN767E DS1 Interface circuit pack to the in-service state.  
Table 3-251. TEST #1212 CPE Loopback Jack Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry test ds1-loop UUCSS cpe-loopback-jack-test-begin at 1-minute  
intervals a maximum of 5 times.  
1005  
1015  
ABORT  
CPE Loopback Jack Test cannot be executed in the current configuration. To  
run this Test, the TN767E or later suffix DS1 must be administered for  
24-channel operation. The "Bit Rate"field on the DS1 circuit pack administration  
form must be set to "1.544" for 24-channel operation.  
ABORT  
Ports on the DS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
DS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-605  
Table 3-251. TEST #1212 CPE Loopback Jack Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1039  
ABORT  
The DS1 Interface circuit pack is providing timing for the system. Executing this  
test could cause major system disruption.  
If the DS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit  
pack via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the board  
is in a network requested loopback mode (Line loopback or Payload loopback).  
The hardware error log will indicate whether a Customer Loopback Jack Test,  
Far CSU Loopback Test, or the One-Way Span Test is executing or if the board  
is in line loopback or payload loopback mode. Only one long-duration  
loopback/span test can be active at a given time. Thus, if a loopback/span test  
is already active, that test must be terminated via the test ds1-loop UUCSS  
end-loopback/span-test command in order to execute this test.  
ABORT  
ABORT  
Internal system error  
2100  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-606  
Table 3-251. TEST #1212 CPE Loopback Jack Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the DS1 interface circuit  
pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, escalate this problem.  
2
FAIL  
The CLJ-LB test failed because it was not set up properly. The DS1 interface  
pack could not successfully put the CPE loopback jack into loopback mode.  
1. Rerun the test ds1-loop UUCSS cpe-loopback-jack-test-begin  
command.  
2. If the test continues to fail, the problem could be with the TN767E board,  
the CPE loopback jack equipment, or somewhere between. Run the test  
ds1-loop UUCSS ds1/csu-loopback-tests command to determine if the  
loopback tests that are closer to the TN767E board are successful. If any of  
these tests fail, follow the maintenance strategy that is associated with the  
test that fails.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-607  
Table 3-251. TEST #1212 CPE Loopback Jack Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
3
FAIL  
The CPE Loopback Jack Test was not set up properly. The framed 3-in-24 test  
pattern, generated by the DS1 Interface circuit pack and looped back through  
the CPE Loopback Jack, could not be detected properly by the DS1 circuit  
pack.  
1. Retry test ds1-loop UUCSS cpe-loopback-jack-test-begin.  
2. If the CPE Loopback test continues to fail, the problem could be with the  
TN767E board, the CPE Loopback Jack equipment, or somewhere in  
between. Run test ds1-loop UUCSS ds1/csu-loopback-tests to see if the  
loopback tests closer to the TN767E board are successful. If any of those  
loopback tests fail, follow the maintenance strategy associated with those  
loopbacks.  
PASS  
The CPE Loopback Jack test has successfully began executing. The test will  
continue to run until the system technician enters the test ds1-loop UUCSS  
end-loopback/span-test command or the release board UUCSS command.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the busyout  
board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
Far CSU Loopback Test (#1213)  
This test is destructive.  
The Far CSU Loopback (R-LLB) Test causes a loopback at the far-end CSU and  
tests all circuitry and facilities from the local TN767E DS1 board to the far-end  
CSU.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-608  
The test is destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS far-csu-loopback-test-begin command.  
All trunks or ports on the DS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the Far CSU  
Loopback Test.  
If the far-end CSU is not a 120A CSU Module or a 401A T1 Sync Splitter, and the  
DS1 is administered for ami-zcs line coding, one’s density protection must be  
disabled on the CSU during the test due to the large number of zero’s in the  
3-in-24 test pattern.  
The Far CSU Loopback Test has the TN767E DS1 Interface circuit pack transmit  
a loopback activation code to the remote CSU, waits up to 15 seconds for return  
of the code to verify the loopback has been established, transmits a framed  
3-in-24 test pattern, begins counting bit errors in the received test pattern, and  
returns a PASS result. If the loopback is not established within the 15 seconds,  
the test fails.  
The status of the Far CSU Loopback test will be available in the hardware error  
log via error type 3901. Several distinct aux values will be used to give the user  
information of the status of the test.  
The list measurements ds1 summary command will display the length of time the  
test has been running (Test Duration field) and number of bit errors detected  
(Loopback/Span Test Bit-Error Count field). If the test pattern is being passed  
through the loopback cleanly, the number of bit errors should be very low. The  
command will also display the type of loopback/span test executing (Test field),  
the type of pattern generated for the loopback/span test (Pattern field), and  
whether the pattern (i.e. 3-in-24 Pattern) is synchronized (Synchronized field).  
To terminate the test, enter test ds1-loop UUCSS end-loopback/span-test or  
the release board command. Using the release board command will restore all  
trunks or ports on the TN767E DS1 Interface circuit pack to the in-service state.  
Table 3-252. TEST #1213 Far CSU Loopback Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry test ds1-loop UUCSS far-csu-loopback-test-begin at 1-minute  
intervals a maximum of 5 times.  
1005  
ABORT  
Far CSU Loopback Test cannot be executed in the current configuration. To run  
this, the TN767E or later suffix DS1 must be administered for 24-channel  
operation. The "Bit Rate" field on the DS1 circuit pack administration form must  
be set to "1.544" for 24-channel operation.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-609  
Table 3-252. TEST #1213 Far CSU Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1015  
ABORT  
Ports on the DS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
DS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
1039  
ABORT  
The DS1 Interface circuit pack is providing timing for the system. Executing this  
test could cause major system disruption.  
If the DS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit  
pack via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the board  
is in a network requested loopback mode (Line loopback or Payload loopback).  
The hardware error log will indicate whether a Customer Loopback Jack Test,  
Far CSU Loopback Test, or the One-Way Span Test is executing or if the board  
is in line loopback or payload loopback mode. Only one long-duration  
loopback/span test can be active at a given time. Thus, if a loopback/span test  
is already active, that test must be terminated via the test ds1-loop UUCSS  
end-loopback/span-test command in order to execute this test.  
ABORT  
ABORT  
Internal system error  
2100  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-610  
Table 3-252. TEST #1213 Far CSU Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the DS1 interface circuit  
pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, escalate this problem.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-611  
Table 3-252. TEST #1213 Far CSU Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2
FAIL  
The far CSU Loopback Test was not set up properly. The DS1 Interface circuit  
pack could not put the far-end CSU into loopback mode.  
3
FAIL  
The far CSU Loopback Test was not set up properly. The framed 3-in-24 test  
pattern, generated by the DS1 Interface circuit pack and looped back through  
the far-end CSU, could not be detected by the DS1 circuit pack.  
1. Retry test ds1-loop UUCSS far-csu-loopback-test-begin.  
2. If the Far CSU Loopback test continues to fail with this error code, the  
problem could be with the TN767E board, the far-end CSU equipment, or  
somewhere in between. Run test ds1-loop UUCSS  
cpe-loopback-jack-test-begin to see if the CPE Loopback Jack test which  
is closer to the TN767E board is successful. (If a CPE Loopback Jack  
device is not being used, then run test ds1-loop UUCSS  
ds1/csu-loopback-tests to see if these even closer loopback tests  
succeed). If the closer loopback test fails, follow the maintenance strategy  
associated with that loopback  
PASS  
The Far CSU Loopback test has successfully began executing. The test will  
continue to run until the system technician enters test ds1-loop UUCSS  
end-loopback/span-test or the release board UUCSS.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the busyout  
board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-612  
One-Way Span Test (#1214)  
This test is destructive.  
The One-Way Span Test allows one-way span testing to and from remote test  
equipment or another DEFINITY communications system. This will test all  
circuitry and facilities from the local TN767E DS1 board to the remote test  
equipment or other DEFINITY communications system.  
The test is destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS one-way-span-test-begin command.  
All trunks or ports on the DS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the One-Way Span  
Tes t.  
The One-Way Span Test has the TN767E DS1 Interface circuit pack transmit a  
framed 3-in-24 test pattern and attempt to receive and verify the pattern. If the  
TN767E board receives a framed 3-in-24 test pattern sent from another DEFINITY  
G3V3 or test equipment at the far-end of the DS1, it will begin counting bit errors  
within the received pattern.  
The status of the One-Way Span test will be available in the hardware error log  
via error type 3902. Several distinct aux values will be used to give the user  
information of the status of the test.  
The list measurements ds1 summary command will display the length of time the  
test has been running (Test Duration field) and number of bit errors detected  
(Loopback/Span Test Bit-Error Count field). If the test pattern is being sent  
cleanly over the span from the far-end, the number of bit errors should be very  
low. The Tes t Dur at ion field will show 0 until the test pattern is received from the  
far-end. Upon receiving the test pattern, the board will begin calculating the test  
duration and number of bit errors. The command will also display the type of  
loopback/span test executing (Test field), the type of pattern generated for the  
loopback/span test (Pattern field), and whether the pattern (i.e. 3-in-24 Pattern) is  
synchronized (Synchronized field).  
To terminate the test, enter the test ds1-loop UUCSS end-loopback/span-test  
command or the release board command. Using the release board command  
will restore all trunks or ports on the TN767E DS1 Interface circuit pack to the  
in-service state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-613  
Table 3-253. TEST #1214 One-Way Span Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the test ds1-loop UUCSS one-way-span-test-begin command at  
1-minute intervals a maximum of 5 times.  
1005  
1015  
ABORT  
One-Way Span Test cannot be executed in the current configuration. To run  
this, the TN767E or later suffix DS1 must be administered for 24-channel  
operation. The "Bit Rate" field on the DS1 circuit pack administration form must  
be set to "1.544" for 24-channel operation.  
ABORT  
ABORT  
Ports on the DS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
DS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
1039  
The DS1 Interface circuit pack is providing timing for the system. Executing  
this test could cause major system disruption.  
If the DS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit  
pack via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the  
board is in a network requested loopback mode (Line loopback or Payload  
loopback). The hardware error log will indicate whether a Customer Loopback  
Jack Test, Far CSU Loopback Test, or the One-Way Span Test is executing or  
if the board is in line loopback or payload loopback mode. Only one  
long-duration loopback/span test can be active at a given time. Thus, if a  
loopback/span test is already active, that test must be terminated via the test  
ds1-loop UUCSS end-loopback/span-test command in order to execute this  
test.  
ABORT  
ABORT  
Internal system error  
2100  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-614  
Table 3-253. TEST #1214 One-Way Span Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the DS1 interface circuit  
pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, escalate this problem.  
PASS  
The One-Way Span test has successfully began transmitting a framed 3-in-24  
test pattern. The test will continue to run until the system technician enters the  
test ds1-loop UUCSS end-loopback/span-test command or the release board  
UUCSS command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-615  
Table 3-253. TEST #1214 One-Way Span Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the busyout  
board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
Inject Single Bit Error Test (#1215)  
This test is destructive.  
The Inject Single Bit Error Test will cause a single bit error to be sent within an  
active framed 3-in-24 test pattern.  
The test is highly destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS inject-single-bit-error command. An attempt to  
use this command will be rejected if none of the three long-duration DS1  
loopback/span tests (CPE Loopback Jack Test, Far CSU Loopback Test,  
One-Way Span Test) are active on a TN767E circuit pack.  
All trunks or ports on the DS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the Inject Single Bit  
Error Test.  
The list measurements ds1 summary command displays the number of bit errors  
detected (Loopback/Span Test Bit-Error Count field). Injecting this single bit error  
should increment the bit error count of the loopback/span test by one.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-616  
Table 3-254. TEST #1215 Inject Single Bit Error Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the test ds1-loop UUCSS inject-single-bit-error command at  
1-minute intervals a maximum of 5 times.  
1015  
ABORT  
Ports on the DS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
DS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
ABORT  
ABORT  
Internal system error  
2100  
2000  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of  
service state. The system will try to restore the circuit pack within 15  
minutes. When no faults are detected for 15 minutes, the DS1 interface  
circuit pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against  
the associated trunk circuits. If the facility is OK and the error occurs  
again after 15 minutes, escalate this problem.  
PASS  
A single bit error has been successfully injected into an active framed 3-in-24  
test pattern.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-617  
Table 3-254. TEST #1215 Inject Single Bit Error Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
End Loopback/Span Test (#1216)  
This test is destructive.  
The End Loopback/Span Test will terminate an active loopback or span test on a  
TN767E DS1 circuit pack. Bit error counting against the received test pattern  
stream is terminated and sending of the framed 3-in-24 test pattern is halted. If  
either the CPE Loopback Jack or the far-end CSU is looped, the appropriate  
loopback deactivate code is sent. If the loopback could not be deactivated, then  
the test will FAIL and a MINOR alarm will be noted in the alarm log until the  
loopback is cleared.  
The test is highly destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS end-loopback/span-test command. Since only  
one of these three different long-duration loopback/span tests can be active at a  
time, the TN767E circuit pack knows which loopback/span test to terminate.  
All trunks or ports on the DS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running this End  
Loopback/Span Test.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-618  
The list measurements ds1 summary command will display the length of time the  
test ran (Test Duration field) and number of bit errors detected (Loopback/Span  
Test Bit-Error Count field).  
To restore the trunks or ports on the TN767E DS1 Interface circuit pack to the  
in-service state, execute the release board command.  
Table 3-255. TEST #1216 End Loopback/Span Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the test ds1-loop UUCSS end-loopback/span-test command at  
1-minute intervals a maximum of 5 times.  
1005  
1015  
ABORT  
End Loopback/Span Test cannot be executed in the current configuration. To  
run this, the TN767E or later suffix DS1 must be administered for 24-channel  
operation. The "Bit Rate" field on the DS1 circuit pack administration form must  
be set to "1.544" for 24-channel operation.  
ABORT  
Ports on the DS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
DS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
ABORT  
ABORT  
Internal system error  
2100  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-619  
Table 3-255. TEST #1216 End Loopback/Span Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The DS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of  
service state. The system will try to restore the circuit pack within 15  
minutes. When no faults are detected for 15 minutes, the DS1 interface  
circuit pack is restored to normal operation. All of the trunks for the DS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against  
the associated trunk circuits. If the facility is OK and the error occurs  
again after 15 minutes, escalate this problem.  
1313  
1314  
FAIL  
FAIL  
The TN767E DS1 circuit pack could not deactivate the loopback through the  
Customer Loopback Jack.  
1. Retry the test ds1-loop UUCSS end-loopback/span-test command at  
1-minute intervals for a maximum of 5 times.  
The TN767E DS1 circuit pack could not deactivate the loopback through the  
far-end CSU.  
1. Make sure that the far-end DS1 is installed if the far-end CSU is a 120A  
CSU Module/T1 Sync Splitter.  
2. Retry the test ds1-loop UUCSS end-loopback/span-test command at  
1-minute intervals for a maximum of 5 times.  
PASS  
The active long-duration loopback or span test on the TN767E circuit pack  
was successfully terminated.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-620  
Table 3-255. TEST #1216 End Loopback/Span Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the link between the internal ID and the port.  
ICSU Status LEDs Test (#1227)  
The TN767E DS1 circuit pack has four status LEDs on the faceplate in addition to  
the three standard faceplate LEDs. These four status LEDs are associated with  
the 120A1 Channel Service Unit (CSU) Module that can be connected to the  
TN767E board via the I/O connector panel on the back of the port carrier.  
This test is a visual test. It will light the four status LEDs red for 5 seconds, then  
light them green for 5 seconds, then light them yellow for 5 seconds, then turn  
the LEDs off and returns control of the status LEDs to the circuit pack.  
This test will only be executed on TN767E or later suffix DS1 circuit packs  
administered for 24-channel operation (1.544 bit rate).  
If the 1201 CSU Module/T1 Sync Splitter is not installed, the status LEDs are  
always off and this test aborts.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DS1-BD (DS1 Interface Circuit Pack)  
3-621  
Table 3-256. TEST #1227 ICSU Status LEDs Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1005  
1951  
The ICSU Status LEDs test can not be executed for the current configuration.  
The test applies only to TN767E or later DS1 circuit packs administered for  
24-channel operation (1.544 bit rate).  
1. If the circuit pack is a TN767E or later suffix DS1 circuit pack, then retry the  
command.  
ABORT  
The ICSU Status LEDs Test can not be executed because a 120A1 or later suffix  
CSU Module or a 401A or later suffix T1 Sync Splitter is not physically installed.  
If using a 120A1 CSU Module/T1 Sync Splitter, physically connect it to the  
TN767E board on the back of the port carrier otherwise, ignore this abort.  
2100  
2500  
ABORT  
ABORT  
PASS  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Internal system error.  
1. Retry the command.  
The ICSU Status LEDs test executed successfully. A PASS result, however,  
does not necessarily mean that the status LEDs behaved properly. It only  
means that the software successfully attempted to light the status LEDs. This is  
a visual test. The service technician must visually exam the behavior of the  
LEDs while the test is running. The LEDs are functioning properly if the four  
status LEDs are lit red for 5 seconds, then lit green for 5 seconds, then lit yellow  
for 5 seconds. If the LEDs behave differently, escalate this problem.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
This could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the add ds1  
UUCSS command to administer the DS1 interface if it is not already  
administered.  
2. If board was already administered correctly, check the error log to  
determine if the board is hyperactive. If this is the case, the board is shut  
down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, issue the busyout  
board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DT-LN-BD (Data Line Circuit Pack)  
3-622  
DT-LN-BD (Data Line Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board PCSS sh  
test board PCSS sh  
Full Name of MO  
Data Line Circuit Pack  
Data Line Circuit Pack  
DT-LN-BD  
DT-LN-BD  
MIN  
WRN  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); and SS is the address of the slot in the carrier where the circuit  
pack is located (for example, 01, 02, ..., etc.).  
Refer to XXX-BD (Common Port Circuit Pack) Maintenance documentation for  
circuit pack level errors. See also DAT-LINE (Data Line Circuit Port) Maintenance  
documentation for related line information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DTMR-PT [Dual Tone Multifrequency Port (TTR)]  
3-623  
DTMR-PT [Dual Tone Multifrequency  
Port (TTR)]  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
DTMR-PT  
DTMR-PT  
DTMR-PT  
MAJOR  
test port PCSSpp sh  
test port PCSSpp sh  
release port PCSSpp  
Dual Tone Multifrequency Receiver  
Port (TTR)  
MINOR  
Dual Tone Multifrequency Receiver  
Port (TTR)  
WARNING  
Dual Tone Multifrequency Receiver  
Port (TTR)  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or  
C); SS is the address of the slot in the carrier where the circuit pack is located (for example, 01, 02,  
..., etc.); and pp is the 2-digit port number (for example, 01).  
The Dual Tone Multifrequency Receiver Port (DTMR), also known as the  
Touch-Tone Receiver (TTR), resides on the Tone Detector circuit pack (TN748,  
TN420) or the TN756 Tone-Clock circuit pack. There are four Dual Tone  
Multifrequency Receiver (DTMR-PT) ports and two General Purpose Tone  
Detector (GPTD-PT) ports on a Tone Detector circuit pack. The DTMR port is  
used to detect touch-tone digits that are placed on the TDM bus. Examples of  
touch-tone digits are digits 0 through 9, #, and *. The ability of the DTMR port to  
detect touch-tone digits is essential for maintenance of other circuit packs (for  
example, Tone-Clock circuit pack) and in placing a station-to-station call. Calls  
originating from a hybrid station do not require a DTMR port.  
The Dual Tone Multifrequency Receiver Port maintenance object defines a set of  
tests to verify that the DTMF digits detection capability of the DTMR port is  
functioning properly. For all Tone Detector circuit pack level errors (DETR-BD),  
refer to the XXX-BD (Common Port Circuit Pack) Maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DTMR-PT [Dual Tone Multifrequency Port (TTR)]  
3-624  
Hardware Error Log Entries and Test to Clear  
Values  
Dual Tone Multifrequency Receiver Port (TTR) Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
ON  
test port PCSSpp sh r 1  
test port PCSSpp r 2  
1 (b)  
17664  
Tone Detector  
Audit/Update Test  
(#43)  
MAJOR/  
MINOR (a)  
18  
0
busyout port PCSSpp  
None  
WARNING  
WARNING  
ON  
ON  
ON  
release port PCSSpp  
test port PCSSpp sh r 2  
test port PCSSpp r 3  
130 (d)  
257 (c)  
17666  
Tone Detector  
Audit/Update Test  
(#43)  
MAJOR/  
MINOR (a)  
513  
Any  
Tone Detection  
MAJOR/  
ON  
test port PCSSpp r 3  
Verification Test (#42) MINOR (a)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. There are two possible alarm levels for this error: Major alarm and Minor  
alarm. A Major alarm is raised if the total number of DTMR ports currently  
in service is less than or equal to one half of the administered threshold  
number. Otherwise, a Minor alarm is raised. In either case, run the Short  
Test Sequence against the DTMR port and follow the error code  
procedures for the individual tests.  
The threshold number of DTMR ports for service is administered using the  
change system-parameters maintenance command.  
b. This error indicates the DTMR port is having problems detecting  
touch-tone digits. If this error is being constantly logged, then the Tone  
Detector circuit pack containing the defective DTMR port should be  
replaced.  
c. The DTMR port lost its translation. Testing the DTMR port is sufficient to  
reload its translation. If testing the DTMR port does not clear the error, then  
the Tone Detector circuit pack containing the defective DTMR port should  
be replaced.  
d. This error type indicates that the circuit pack has been removed or has  
been insane for at least 11 minutes. To clear the error, reinsert or replace  
the circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DTMR-PT [Dual Tone Multifrequency Port (TTR)]  
3-625  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the Tone  
Detection Verification Test, for example, you may also clear errors generated from  
other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
ND  
Tone Detection Verification Test (#42)  
Tone Detector Audit/Update Test (#43)  
X
X
X
X
ND  
1. D = Destructive; ND = Nondestructive  
Tone Detection Verification Test (#42)  
This test verifies the "touch-tone digits detection" capability of the DTMR port is  
functioning properly.  
Table 3-257. TEST #42 Tone Detection Verification Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
none  
ABORT  
ABORT  
ABORT  
ABORT  
The system was not able to allocate all the resources needed for this test  
or there was an internal system error.  
1
The system could not allocate all the resources needed to test the DTMR  
port.  
1001  
1002  
The system was unable to put the DTMR port in the appropriate mode to  
test it.  
The system could not allocate time slots for the test connection. This could  
happen when the system is heavily loaded. If the system is not heavily  
loaded, then test the TDM Bus via the test tdm [a|b] command. Refer to  
the TDM-BUS (TDM Bus) Maintenance documentation for details.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DTMR-PT [Dual Tone Multifrequency Port (TTR)]  
3-626  
Table 3-257. TEST #42 Tone Detection Verification Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1003  
ABORT  
The system could not allocate a Tone Generator for the test connection.  
This could happen when the system is heavily loaded or there is not a  
Tone-Clock circuit pack in the port network when this test is being  
executed.  
1. Make sure there is a Tone-Clock circuit pack in the same port network.  
2. If a Tone-Clock circuit pack is missing, install one in the same port  
network.  
3. Allow about 1 minute for the Tone-Clock maintenance to run on the  
newly inserted Tone-Clock circuit pack.  
4. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2006  
ABORT  
DTMF detection failed. This could be caused by the administered  
companding mode of the system not matching that of the Tone Detector  
circuit pack.  
1. Make sure that companding mode of the system matches that of the  
Tone Detector.  
1-3  
FAIL  
DTMF digits were not correctly detected.  
1. Run the Short Test Sequence: test port PCSSpp sh r 1.  
2. If the problem persists, the system is still operating properly but  
system capacity will be reduced. In order to restore the system  
performance to normal, replace the Tone Detector circuit pack  
containing the defective DTMR port.  
PASS  
The DTMR port is able to detect all the touch-tone digits.  
Tone Detector Audit/Update Test (#43)  
The DTMR port is refreshed with all time slot information and sanity audit is  
performed on the DTMR port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
DTMR-PT [Dual Tone Multifrequency Port (TTR)]  
3-627  
Table 3-258. TEST #43 Tone Detector Audit/Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
The system was not able to allocate all the resources needed for this test.  
1. Wait one minute and try again.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Hardware audit failed.  
FAIL  
1. Run the Short Test Sequence: test port PCSSpp sh r 1.  
2. If the problem persists, the system is still operating properly but  
system capacity is reduced. In order to restore the system  
performance to normal, replace the Tone Detector circuit pack  
containing the defective DTMR port.  
PASS  
The DTMR port has been successfully refreshed with its translation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-BD (Multi Application Platform Board)  
3-628  
E-DIG-BD (Multi Application  
Platform Board)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board PCSS sh  
Full Name of MO  
MO800DIG-BD  
MO800DIG-BD  
DIG800-BD  
DIG800-BD  
MIN  
WRN  
test board PCSS sh  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example,  
A, B, or C); and SS is the address of the slot in the carrier where the circuit pack is located  
(for example, 01, 02, ...).  
The maintenance strategy for DIG800-BD is the same as the one described for  
MO-COMBD (MO-XXX-BD). Maintenance testing of the common circuit pack is  
handled by on-board firmware and SPE-controlled tests. Maintenance software  
queries the firmware for error and alarm information, status, and test results. The  
firmware automatically reports error conditions that will result in SPE-controlled  
testing.  
Board Insertion  
The switch makes an additional board query if any of the following circuit packs  
are inserted:  
Circuit Pack  
Vintage  
TN754  
49  
For any of the above initial board up-links, the switch sends queries requesting  
additional data from the board for administration purposes, while also telling the  
board the switch software release and the system type.  
For the native mode, the response to the board query downlink messages  
consists of several CCMS uplink messages that identify the true board code,  
vintage, suffix, emulation type, and the number of reserved slots it needs.  
Hyperactivity  
The common circuit pack is considered "hyperactive" if the service dispatcher  
receives 200 up-link messages from the circuit pack in a 10-second period.  
Since MAPD has 32 ports, the hyperactivity limit is increased to 500 up-link  
messages per 10seconds. An alarm is issued and the board taken out of service  
when the limit reaches 400 or when it hits 500 up-link messages in 10 seconds.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-BD (Multi Application Platform Board)  
3-629  
LED Use  
The LED Control message 038x requests the Angel to drive the Red, Yellow, and  
Green LEDs on the face plate of typical port board on or off. On the MAPD, only  
the Red LED is controlled by this message. Yellow and Green change requests  
received from the switch by the MAPD drive LCD behavior rather than LED  
behavior. The switch continues to send the same LED control messages to the  
MAPD that it currently sends to all other port boards. The MAPD will handle  
proper interpretation of these messages. You should note that the PC on the  
MAPD, as well as the switch itself, can control the LEDs and the LCD on the  
MAPD.  
Port Administration  
In administration without hardware, the switch allows administration of up to 32  
MAPD ports of any port type. If the port type later reported by the board does not  
match the existing type, the switch assumes the board is a MAPD board with a  
different configuration and rejects the board. MAPD_DCP_STA and MAPD_ASAI_  
STA are the only two types of terminals are allowed on a MAPD board. Therefore,  
while administering ports on MAPD using add station form, it will allow only the  
terminals mentioned above.  
NOTE:  
Refer to XXX-BD (Common Port Circuit Pack) maintenance documentation  
for circuit pack level errors. See also DIG-LINE maintenance  
documentation for related line information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-STA (Emulated Digital Line)  
3-630  
E-DIG-STA (Emulated Digital Line)  
MO Name (in  
Alarm Log)  
Initial Command to  
1
Alarm Level  
MINOR  
Run  
Full Name of MO  
Emulated Digital St.  
Emulated Digital St.  
E-DIG-STA  
E-DIG-STA  
test port PCSSpp l  
WARNING  
test port PCSSpp sh  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); and SS is the address of the slot in the carrier where the circuit  
pack is located (for example, 01, 02, ...).  
There are 4 tests in the Emulated Digital Line station maintenance test sequence  
and only one test path in the test sequence. Once the test sequence is started,  
all tests in the test sequence are executed.  
E-DIG-ST maintenance monitors and tests ports on the TN800 MAPD circuit pack  
and the hardware connected to those ports for lines administered as a digital  
station. These include stations with an emulated digital voice terminal and  
stations with an emulated digital voice terminal and a linked data module.  
Stand-alone data modules and data adaptors in stand-alone mode are not  
supported by the TN800 circuit pack. Circuit pack maintenance is covered by  
E-DIG-BD.  
Hardware Error Log Entries and  
Test to Clear Values  
Table 3-259. Digital Line Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
test port PCSSpp sh r 1  
rel port PCSSpp  
1
0
0
Any  
Any  
Any  
OFF  
ON  
18 (a)  
0
busyout port PCSSpp  
None  
WNG  
WNG  
130 (b)  
1793 (c)  
test port PCSSpp sh  
test port PCSSpp l r 3  
Voice and Control Local  
Loop Test (#13)  
MIN/  
WNG  
ON  
2
2049 (d)  
2305 (e)  
NPE Crosstalk Test (#9)  
MIN/  
WNG  
ON  
test port PCSSpp l r 3  
2
32770  
None  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-STA (Emulated Digital Line)  
3-631  
Table 3-259. Digital Line Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
3840 (f)  
3841 (g)  
2304 (h)  
40965  
41029  
None  
None  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
2. Major alarms may be downgraded to Warning alarms based on the value used in the set options  
command.  
Notes:  
a. Maintenance personnel has busied out the port in question. Make sure  
that the port is released from busyout by using the release port PCSSpp  
command.  
b. The circuit pack has been removed or has been insane for more than 21  
minutes. To clear the error, reinsert or replace the circuit pack.  
c. The local loop test failed. Each failure increments the counter by 1 when  
the local loop test fails. The counter is decremented when the loop test  
passes. When the counter reaches a threshold of 3, an on-board MINOR  
alarm is raised. This is the code that is generated when the link between  
the circuit pack and the voice terminal is successfully reset. No technician  
action is necessary.  
d. The NPE Cross talk test failed. The counter is incremented by 1 when the  
NPE Cross talk test fails. The counter is decremented by 1 when the NPE  
Cross talk test passes. When the counter reaches a threshold of 3, an  
on-board MINOR alarm is raised and the board is taken out of service.  
e. The station went off-hook while it was in the ready-for-service state. Use  
the status station command to determine the state of the station. The  
off-hook should have moved the station to ready-for-service. No technician  
action is necessary.  
f. No terminal is connected to the Digital Line board. No maintenance action  
is required.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-STA (Emulated Digital Line)  
3-632  
g. The circuit pack’s message buffer is full. This may be caused by having  
many display phones with heavy traffic connected to the circuit pack. No  
action is necessary.  
h. Internal system error; no action is necessary. The error counters 1, 2, 3, 4,  
5, 6, 10, 11, 12, 13, 14, 15, and 16 do not have any significance for this  
MO.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Voice and Control Channel Local Loop Around Test, for example, you may also  
clear errors generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Voice and Control Channel Local Loop Around Test (#13)  
NPE Crosstalk Test (#9)  
D/ND  
D
X
X
X
ND  
Station Lamp Updates Test (#16)  
ND  
1. D = Destructive; ND = Nondestructive  
Digital Line NPE Crosstalk Test (#9)  
One or more Network Processing Elements (NPEs) reside on each circuit pack  
with a TDM Bus interface. The NPE controls port connectivity and gain and  
provides conferencing functions on a per-port basis. The NPE Crosstalk Test  
verifies that this port’s NPE channel talks on the selected time slot and never  
crosses over to time slots reserved for other connections. If the NPE is not  
working correctly, one-way and noisy connections may be observed. This test is  
part of a port’s Long Test Sequence and takes about 20 to 30 seconds to  
complete. Crosstalk testing occurs on both the primary information channel  
(voice) and the secondary information channel (data) associated with each  
digital station port. If this test fails on either channel, the station and the DTDM  
are taken out-of-service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-STA (Emulated Digital Line)  
3-633  
Table 3-260. TEST #9 Digital Line NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1
ABORT  
During testing of the primary information channel, system resources may  
not have been available or the port was busy during the test.  
1. Check the port status. Use the display port PCSSpp command to  
determine the station extension of the port. Use the status station  
command to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for this test.  
You will have to wait until the port is idle.  
2. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
2
ABORT  
During testing of DTDM, system resources may not have been available or  
he port was busy during the test.  
1. Check if port is being used. If possible, disconnect by toggling the  
disconnect button on DTDM. Retry the command after 1 minute.  
!
WARNING:  
This action drops the call in progress.  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use display port PCSSpp to determine the  
station extension or attendant number of the port. Use status station or  
status attendant to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system is under  
heavy traffic conditions or has time slots out-of-service due to TDM-BUS  
errors. Refer to TDM-BUS to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-STA (Emulated Digital Line)  
3-634  
Table 3-260. TEST #9 Digital Line NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system is  
oversized for the number of Tone Detectors present, or some Tone  
Detectors are out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR  
documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
documentation.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test.  
1. Use display port PCSSpp to determine the station extension or  
attendant number of the port.  
2. Use status station or status attendant to determine the service state  
of the port. If the service state indicates that the port is in use, then the  
port is unavailable for certain tests.  
3. Wait until the port is idle before retesting. Attendants are always in use  
(off-hook) if the handset is plugged in and the port is not busied out.  
1020  
2000  
ABORT  
ABORT  
Test disabled by background testing. Use the status station command to  
determine when the station is available for testing.  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times..  
1
2
FAIL  
The Network Processing Element (NPE) of the tested port is transmitting in  
error. This causes noisy and unreliable connections.  
Failure code 1 indicates that the Crosstalk test failed on the primary  
channel.  
Failure code 2 indicates that the Crosstalk test failed on the secondary  
channel.  
1. Replace the circuit pack.  
PASS  
The port is correctly using its allocated time slots.  
1. To ensure that this is not an intermittent problem, repeat this test a  
maximum of 10 times.  
2. If complaints persist, examine the station, connections, and wiring.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-STA (Emulated Digital Line)  
3-635  
Voice and Control Channel Local Loop Test (#13)  
These tests check the information and control channels between the Switch  
Processing Element (SPE) and the Digital Line port circuit. The SPE sends a  
message to loop around both the information and control channels for the port.  
First, the primary information (voice) channel loopback test sends a digital count  
from the Tone-Clock circuit pack on the primary information channel time slot and  
receives the same digital count with a general purpose tone detector.  
While the primary information channel is still looped around, the Control Channel  
Loop Around Test sends four different transparent patterns to the on-board  
microprocessor, receives them back, and compares them.  
The Loop Around Test for the secondary information (data) channel is the same  
as the primary information channel loop around test and is performed only if a  
DTDM is administered.  
Next, a Conference Test checks the primary information channel. This test is the  
same as Conference Test #6.  
The four tests will generate only one resulting value (Pass, Fail, or Abort). If any  
test fails or aborts, the test sequence stops.  
Table 3-261. TEST #13 Voice and Control Channel Local Loop Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use display port PCSSpp to determine the  
station extension or attendant number of the port. Use status station or  
status attendant to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for  
certain tests. Wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-STA (Emulated Digital Line)  
3-636  
Table 3-261. TEST #13 Voice and Control Channel Local Loop Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1002  
ABORT  
The system could not allocate time slots for the test. The system is under  
heavy traffic conditions or it has time slots out-of-service due to TDM-BUS  
errors. Refer to TDM-BUS to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system is  
oversized for the number of Tone Detectors present, or some Tone  
Detectors are out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
documentation.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension or attendant number of the port. Use status station or status  
attendant to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain  
tests. Wait until the port is idle before retesting. Attendants are always in  
use (off-hook) if the handset is plugged in and the port is not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Rerun the test at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-STA (Emulated Digital Line)  
3-637  
Table 3-261. TEST #13 Voice and Control Channel Local Loop Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
7
FAIL  
Conference Test failed on primary channel. In some cases, users may not  
notice disruption in service. In extreme cases, conferencing feature may  
not work at all.  
14  
15  
FAIL  
FAIL  
The primary voice channel is not transmitting properly. User impact may  
range from noticing nothing to not being able to use this port.  
The control channel between the processor and digital circuit pack is not  
transmitting properly. User impact may range from noticing nothing to not  
being able to use the port. This could disrupt other users.  
16  
FAIL  
The secondary voice channel is not transmitting properly. User impact  
may range from noticing nothing to not being able to use this port.  
1. Run circuit pack tests to check the Tone Generator circuit pack and  
the Tone Detector circuit pack using the test board PCSSpp  
command.  
2. Resolve any problems that are detected on the Tone Generator circuit  
pack or Tone Detector circuit pack.  
3. If the Tone Generator and Tone Detector circuit packs are functioning  
properly and the test still fails, replace the Digital Line circuit pack.  
PASS  
The test passed, and all channels are transmitting properly.  
1. To ensure that this is not an intermittent problem, repeat this test up to  
10 times.  
2. If noisy connections for voice or corrupted data for data transfer  
persist, examine the station, connections, and wiring.  
Station Lamp Updates Test (#16)  
This test lights all lamps on the terminal as specified. The lamp updates will run  
only if the station is in-service. The status of the station is checked and the lamp  
updates are blocked from taking place if the station is not in the in-service state.  
This test does not affect the status of the Message Waiting lamp.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-STA (Emulated Digital Line)  
3-638  
Table 3-262. TEST #16 DIG-LINE Station Lamp Updates Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
System technician may have busied out the port.  
1
3
1. Look in the Error Log for Error Type 18 (port busied out) for this port. If  
this error type is present, then release the port with the release station  
<extension> command and run the test again.  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
Station may be in ready-for-service or out-of-service state.  
1. Use the status station command to verify state of station.  
2. Make sure the terminal is connected.  
ABORT  
ABORT  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port is busy  
with a valid call. Use display port PCSSpp to determine the station  
extension or attendant number of the port. Use status station or status  
attendant to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain tests.  
Wait until the port is idle before retesting. Attendants are always in use  
(off-hook) if the handset is plugged in and the port is not busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1392  
ABORT  
This is currently a TTI port, and the test cannot execute on it.  
1. Verify that the port is a TTI port using either the display port command  
(the display shows that the port is a TTI port) or the list config  
command (the display shows a tfor the port).  
2. If either list config or display port indicates that the port is not a TTI  
port, escalate the problem. If both commands indicate that the port is a  
TTI port, the abort is correct, and no action is necessary.  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
E-DIG-STA (Emulated Digital Line)  
3-639  
Table 3-262. TEST #16 DIG-LINE Station Lamp Updates Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The message to light all of the station lamps was sent successfully to the  
port.  
1. Observe the station lamps being lit when running the test. If all lamps do  
not light successfully, the other Digital Line test results may indicate  
related problems that will not allow the lamps to light.  
2. Investigate by using other Digital Line port tests and by examining the  
station, wiring, and connections.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
EMG-XFER  
3
3-640  
EMG-XFER  
Emergency Transfer (SCC Cabinets)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test environment P  
Full Name of MO  
Emergency Transfer  
Emergency Transfer  
EMG-XFER  
EMG-XFER  
MAJOR  
WARNING  
test environment P  
1. Where Pis an appropriate port network number determined via the PORTfield from the  
Alarm or Error Log.  
The system provides the ability to cut designated analog phones through to CO  
trunks if the switch cannot provide even minimal phone service. This ability is  
known as Emergency Transfer. The EMG-XFER MO tracks the control of  
Emergency Transfer. There is one EMG-XFER MO for the port network.  
Emergency Transfer can be controlled by the system or can be manually  
controlled via the Emergency Transfer switch located on the Processor circuit  
pack. A manual ON position (up) generates a Major alarm. A manual OFF  
position (down) generates a Warning alarm. Unless a technician is currently  
working on the system, the switch should be left in the auto position.  
Error Log Entries and Test to Clear Values  
Table 3-263. Emergency Transfer Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
test environment P sh r 1  
test environment P r 3  
1
0
0
Any  
Any  
Any  
ON  
1
Any  
Emergency Transfer  
Query (#124)  
MAJOR  
257  
0
Emergency Transfer  
Query (#124)  
WARNING  
ON  
test environment P r 3  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
EMG-XFER  
3
3-641  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following tables. By  
clearing error codes associated with the Cabinet Query Test, for example, you  
may also clear errors generated from other tests in the testing sequence. For  
example, you may also clear errors generated from other tests in the testing  
sequence.  
Single Carrier System  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
ND  
Cabinet Query Test (#122) (a)  
X
X
X
X
X
X
X
X
X
X
Emergency Transfer Query Test (#124)  
External Alarm Lead Query Test (#120) (b)  
Analog Ring Generator Initialization Test (#117) (c)  
Analog Ring Generator Query Test (#118) (c)  
ND  
ND  
ND  
ND  
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Refer to “CABINET” for a description of this test.  
b. Refer to “EXT-DEV” for a description of this test.  
c. Refer to “RING-GEN” for a description of this test.  
Emergency Transfer Query Test (#124)  
This test queries the hardware for the state of the Emergency Transfer switch and  
reports the result. If the switch is in a position where the system software can  
control Emergency Transfer, then the test passes. If the switch is in a position  
where the system software cannot control Emergency Transfer, then the test fails.  
The Processor controls Emergency Transfer. The system software does not have  
control of Emergency Transfer within a cabinet if the switch is in the manual ON  
or manual OFF state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
EMG-XFER  
3
3-642  
Table 3-264. TEST #124 Emergency Transfer Query Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to ABORT with error code 2000, check for system  
powering problems with the A carrier. Resolve all CABINET alarms.  
Then, repeat the test.  
2029  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1
2
FAIL  
FAIL  
Emergency Transfer is manually turned OFF via the Emergency Transfer  
switch.  
Emergency Transfer is manually turned ON via the Emergency Transfer  
switch.  
1. Place the switch in the AUTO position.  
PASS  
The system software has control of Emergency Transfer. If Emergency  
Transfer is invoked, then there can be a Major alarm in the system that is  
invoking Emergency Transfer. Table 3-265 lists the error types and MOs  
that may cause Emergency Transfer. If any or all of these errors appear in  
the log, then refer to the appropriate Maintenance documentation and  
resolve those problems first.  
If none of these errors appear in the log, then check the Emergency  
Transfer hardware.  
Table 3-265. Test #124 Error Log Entries That Cause Emergency  
Transfer  
MO Name  
SW-CTL  
Error Type  
Aux Data  
1
2
SW-CTL  
TONE-BD  
TONE-BD  
1
0
0
2305  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
ERR-LOG (Error Log)  
3
3-643  
ERR-LOG (Error Log)  
MO Name (in  
Alarm Log)  
Initial Command to  
Run  
Alarm Level  
none  
Full Name of MO  
ERR-LOG  
none  
Error Log  
Functional Description  
The ERR-LOG MO is responsible for the sanity of the Alarm Log, the Hardware  
Error Log, and the Software Error Log. If an inconsistency is detected in any one  
of these logs, all logs are re-initialized and a hardware error is logged against  
ERR-LOG indicating the time of inconsistency. There are no tests and no alarms  
for the Error Log MO. This MO exists solely for the purpose of allowing errors to  
be logged against it.  
Hardware Error Log Entries and Test to Clear  
Values  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
none  
Test to Clear Value  
none  
none  
1
0
Any  
Any  
Any  
none  
Any  
none  
510 (a)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to  
the appropriate test description and follow the recommended procedures.  
Notes:  
a. This error indicates that an inconsistency was detected in either the Alarm  
Log, the Hardware Error Log, or the Software Error Log. To recover from  
this error, all of the logs were cleared and re-initialized. Any alarms that  
were active at the time of this error have been cleared. There is no  
associated test for this error.  
The Aux data value indicates when the inconsistency was found:  
0
Found during a periodic audit of the Error Log  
Found after an extended reboot  
1
2
Found after a reboot  
3
Found after a Reset System 3 (Cold_1)  
Found after a Reset System 2 (Cold_2)  
Found after a Warm Start  
4
16  
100  
DFoowunnlodadaffrtoemr Wanwwin.tSeormnaanl usaolsft.wcoamre. AalluMdaitnuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETH-PT (Control LAN Ethernet)  
3-644  
ETH-PT (Control LAN Ethernet)  
MO Name (in  
Alarm Log)  
1
Alarm Level  
MAJOR  
Initial Command to Run  
test port UUCSSpp long  
test port UUCSSpp long  
test port UUCSSpp  
Full Name of MO  
MO_ETH_PT  
ETH-PT  
ETH-PT  
ETH-PT  
MINOR  
MO_ETH_PT  
MO_ETH_PT  
WARNING  
1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation (A, B,  
C, D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21). pp is the two  
digit port number (01, 02, ...).  
The TN799 Control LAN (CLAN) packet port circuit pack provides TCP/IP  
connection to adjuncts applications such as CMS, Intuity, and DCS Networking.  
The CLAN circuit pack has one 10baseT Ethernet connection and up to 16 DS0  
physical interfaces for PPP connections. Multiple CLAN circuit packs in a system  
gives additional TCP/IP capacity.  
A remote socket control link (RSCL) links the CLAN and the SPE to pass call  
control and other management information. Since one link serves all the ports on  
the circuit pack, maintenance of the RSCL is part of the CLAN circuit pack  
maintenance.  
NOTE:  
The CLAN TN799 circuit pack replaces the PGATE and PI circuit packs in  
the G3r and G3si/G3vs systems, respectively. The PGATE or PI can be  
used with the CLAN to create an X.25-to-TCP/IP bridge for adjunct and  
DCS connections.  
Control LAN Congestion Controls  
The switch activates congestion controls on CLAN when it detects buffers  
exceeding the threshold. The switch releases the congestion controls when the  
CLAN reports that its buffer level has returned to normal levels.  
If congestion:  
Then the switch:  
Persists for a 14-minute interval, Raises MINOR alarm.  
Exhausts buffers,  
Raises MINOR alarm.  
Retires MINOR alarm.  
Ceases for 12 minutes,  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETH-PT (Control LAN Ethernet)  
3-645  
Error Log Entries and Test to Clear Value  
Table 3-266. ETH-PT Error Log Entries  
Aux  
Alarm  
Level  
On/Off  
Board  
Error Type  
Data  
Associated Test  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
ON  
test port UUCSSpp s  
1 (a)  
0
0
Ethernet Local  
Looparound  
Test (#1278)  
MINOR  
test port UUCSSpp l r 3  
513 (b)  
Link Integrity Inquiry  
(#1282)  
MINOR  
WNG  
OFF  
OFF  
test port UUCSSpp r 2  
769 (c)  
0
0
1281 (d)  
1537, 1538  
(e)  
Session Status Test  
(#1286)  
MINOR  
OFF  
1793-1920  
(f)  
2305-2560  
(g)  
2561-2816  
(g)  
3329 (h)  
TCP/IP Ping Test  
(#1281)  
WNG  
OFF  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. Error Type 1: Ethernet Local Looparound Test (#1278) failed.  
1. Test the port (test port UUCSSpp long).  
2. Refer to repair procedures for Test #1278.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETH-PT (Control LAN Ethernet)  
3-646  
b. Error Type 513: Link Integrity Inquiry Test (#1282) failed or CLAN port  
detected loss of Ethernet link integrity.  
Possible causes:  
■
■
Cabling  
Ethernet transceiver  
1. Test the port (test port UUCSSpp long).  
2. If the Link Integrity Inquiry Test (#1282) fils, refer to its repair  
procedure.  
c. Error Type 769: Port received invalid frame.  
Invalid Ethernet frame errors occur when the frame  
■
Contains a bad Cyclic Redundancy Check (CRC)  
Is misaligned  
■
1. Isolate the problem with the Ethernet Local Looparound Test  
(#1278).  
2. Test the port (test port UUCSSpp long).  
3. Verify the repair with the Ethernet Local Looparound Test (#1278).  
4. Clear the alarm (test port UUCSSpp long clear).  
d. Error Type 1281: System software received an indication that the far-end  
has requested a disconnect of a session on this link. This is a log-only  
error.  
e. Error Type 1537-1538: Some or all sessions on a port are down.  
If:  
Then the switch:  
Some sessions are down  
All sessions are down  
Raises WARNING alarm on circuit pack  
Raises MINOR alarm on circuit pack  
1. Test the port (test port UUCSSpp short).  
2. Refer to Session Status Test (#1286) repair procedure to verify  
repair.  
f. Error Type 1793-1920: system software received an indication that a  
socket was closed due to an error. Error Type indicates the application  
associated with this socket.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETH-PT (Control LAN Ethernet)  
3-647  
Error Type Application  
1793  
Unused  
DCS  
1794  
1795  
AUDIX  
1796  
CMS  
1797  
ISDN Gateway  
1798-1920  
Reserved for  
future  
Aux Data indicates the internal application number.  
g. Error Type 2305-2816: System software detected a session is down. Aux  
Data indicates the session number. These are log only errors. Error types  
2305-2560 are for session numbers 1-256. Error types 2561-2816 are for  
session numbers 257-512.  
h. Error Type 3329: TCP/IP Ping Test failed.  
1. Test port (test port UUCSSpp short).  
2. Refer to TCP/IP Ping Test (#1281) repair procedures.  
System Technician-Demanded Tests:  
Descriptions and Error Codes  
Investigate errors in the order they appear in the table below.  
Table 3-267. System Technician-Demanded Tests: ETH-PT  
ShortTest  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Ethernet Local Loop-Around Test (#1278)  
TCP/IP Ping Test (#1281)  
D/ND  
D
X
X
X
X
X
X
X
ND  
ND  
ND  
Session Status Test (#1286)  
Link Integrity Inquiry Test (#1282)  
1. D = Destructive, ND = Non-destructive  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETH-PT (Control LAN Ethernet)  
3-648  
Ethernet Local Looparound Test (#1278)  
This test is destructive.  
Use this test to check circuitry in the data path for an Ethernet call (from the  
on-board processor to the Ethernet Transceiver). This test fails if the data it  
receives does not match the data it transmits.  
Table 3-268. TEST #1278 Ethernet Local Looparound Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
The port is in use.  
1. Determine status of port (status clan-port UUCSSpp).  
2. Retry the command when the port is idle. The post may be forced to the  
idle state by executing a busyout port UUCSS command.  
NOTE:  
The busyout port command is destructive, causing all calls and links  
associated with the port to be torn down.  
2000  
ABORT  
Did not receive circuit pack test response within the allowable time period.  
1. If the problem persists, reset the circuit pack (busyout board UUCSS,  
reset board UUCSS, and release board UUCSS).  
2. If the problem persists, replace the circuit pack.  
Internal system error.  
2012  
2100  
1
ABORT  
ABORT  
FAIL  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. If the problem persists, escalate the problem.  
Could not allocate the necessary resources to run test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. If the problem persists, escalate the problem.  
Circuit pack detected failure in the Ethernet Local Looparound Test (#1278).  
1. If the problem persists, reset the circuit pack (busyout board UUCSS,  
reset board UUCSS, and reset board UUCSS).  
2. If the problem persists, replace the circuit pack.  
The circuitry tests properly.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETH-PT (Control LAN Ethernet)  
3-649  
TCP/IP PING Test (#1281)  
This non-destructive test fails if all the endpoints fail to respond. Use this test to  
check the circuitry in the data path for a peer-to-peer IP layer connection.  
Table 3-269. TEST #1281 TCP/IP PING Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1, 2,  
11  
ABORT  
Internal error  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
2. If the problem persists, escalate the problem.  
Destination unreachable.  
7
ABORT  
1. Verify that there is a destination to ping in the routing table (list ip-route  
and look for destinations reachable through this ethernet port).  
2. If there are no reachable destinations from this port (i.e., no routes  
administered on ethernet), administer a route and retry.  
3. Escalate if the problem persists.  
Incorrect test configuration.  
1005  
ABORT  
1. Verify Ethernet link is in service (status port UUCSSpp or status link  
n).  
2. Verify that Ethernet link is enabled (status port UUCSSpp or status  
link n or display data-module).  
3. Verify routing table has reachable destinations.  
4. Repeat the test.  
5. If problem persists while the Ethernet link is in service and enabled,  
escalate the problem.  
1124  
ABORT  
Ethernet link is not enabled.  
1. Verify that the Ethernet link is enabled (status port UUCSSpp, status  
link n, or display data-module).  
2. If the link is not enabled, enable the link (change data-module).  
3. Repeat the test.  
4. Escalate if the problem persists.  
Ethernet link not in service.  
1125  
ABORT  
1. Verify Ethernet link is in service (status port UUCSSpp or status link  
n).  
2. If the link is not in service, release the link using (release link n or  
release port UUCSSpp).  
3. Repeat the test.  
4. Escalate if the problem persists.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETH-PT (Control LAN Ethernet)  
3-650  
Table 3-269. TEST #1281 TCP/IP PING Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Did not receive circuit pack test response within the allowable time period.  
1. Reset the circuit pack (busyout board UUCSS, reset board UUCSS,  
and release board UUCSS).  
2. If the test fails again, replace the circuit pack.  
Internal system error.  
2012  
2100  
2500  
1003  
ABORT  
ABORT  
ABORT  
FAIL  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
Could not locate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
Ping to the destination failed due to on-board problem.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. If the problem persists, reset the circuit pack (busyout board UUCSS,  
reset board UUCSS, and release board UUCSS).  
3. If the problem persists, re-administer the ethernet connection through a  
different ethernet port, if available.  
4. If the problem still persists, or if there are no other available ethernet  
ports, replace the circuit pack.  
1007  
FAIL  
Ping to the destination failed due to the destination down.  
1. Verify that at least one destination reachable through this port is up.  
Ping this destination (ping ip-address xxx.xxx.xxx.xxx).  
2. If the ping to any destination is successful through this port, the link is  
up, although some destinations are unreachable. Ignore the failure.  
3. If ping to all destinations fail, test this port (test port UUCSSpp short)  
and follow repair procedures for Session Status Test (#1286) failures.  
PASS  
TCP/IP Ping Test (#1281) is successful.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETH-PT (Control LAN Ethernet)  
3-651  
Link Integrity Inquiry Test (#1282)  
This non-destructive test queries the CLAN Ethernet port’s physical connections.  
If:  
Then the test:  
Passes.  
CLAN connection is present,  
CLAN connection is absent,  
There is no response,  
Fails.  
Aborts.  
Table 3-270. TEST #1282 Link Integrity Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Ethernet link is not enabled.  
1124  
ABORT  
1. Verify that the Ethernet link is enabled (status port UUCSSpp, status  
link n, or display data-module).  
2. If the link is not enabled, enable the link (change data-module).  
3. Repeat the test.  
4. Escalate if the problem persists.  
Ethernet link not in service.  
1125  
ABORT  
1. Verify whether Ethernet link is in service (status port UUCSSpp or  
status link n).  
2. If the Ethernet link is not in service, release the link (release link n or  
release port UUCSSpp).  
3. Repeat the test.  
4. Escalate if the problem persists.  
1959  
2012  
2100  
ABORT  
ABORT  
ABORT  
Downlink message error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
Could not locate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETH-PT (Control LAN Ethernet)  
3-652  
Table 3-270. TEST #1282 Link Integrity Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2500  
ABORT  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
FAIL  
Link integrity lost due to problem with attachment of Ethernet cable to the  
port.  
1. Repeat the test.  
2. If the test fails, verify that the cable properly is secured to Ethernet port  
and to the bus.  
3. Verify the CLAN circuit pack link integrity LED is glowing.  
4. Retry the test.  
5. If problem persists, refer to Ethernet Local Looparound Test (#1278)  
repair procedures.  
PASS  
The Ethernet Link Integrity Test (#1282) detects good connections.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETH-PT (Control LAN Ethernet)  
3-653  
Session Status Test (#1286)  
This non-destructive test determines the status of all Ethernet port sessions. This  
test queries the system software on port session status.  
If the system software indicates  
that:  
Then the switch:  
All port sessions are up (ALL UP)  
Some port sessions are up (SOME UP)  
All port sessions are down (ALL DOWN)  
Raises no alarm, or retires alarm  
Raises WARNING alarm  
Raises MINOR alarm  
Table 3-271. TEST #1286 Session Status Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Ethernet link is not enabled.  
1124  
ABORT  
1. Verify that the Ethernet link is enabled (status port UUCSSpp, status  
link n, or display data-module).  
2. If the link is not enabled, enable the link (change data-module).  
3. Repeat the test.  
4. Escalate if the problem persists.  
Ethernet link not in service.  
1125  
ABORT  
1. Verify whether Ethernet link is in service (status port UUCSSpp or  
status link n).  
2. If the Ethernet link is not in service, release the link (release link n or  
release port UUCSSpp).  
3. Repeat the test.  
4. Escalate if the problem persists.  
2000  
ABORT  
Did not receive circuit pack test response within the allowable time period.  
1. If the problem persists, reset the circuit pack (busyout board  
UUCSSpp, reset board UUCSS, and release board UUCSS).  
2. If the problem persists, replace the circuit pack.  
Could not locate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
2100  
2500  
ABORT  
ABORT  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETH-PT (Control LAN Ethernet)  
3-654  
Table 3-271. TEST #1286 Session Status Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
FAIL  
System software indicates at least one Ethernet link session is down (SOME  
UP).  
1. Isolate downed sessions (status port UUCSSpp or status link n).  
2. Follow actions based on session information.  
2
FAIL  
System software indicates all Ethernet sessions are down (ALL DOWN).  
1. Test the port (test port UUCSSpp) to verify the Ethernet Local  
Looparound Test (#1278) result.  
2. If test passes, wait for system software to indicate ALL UP.  
3. If the test fails, check the destination and other components in the path.  
4. If the destination and other components in the path are in-service, take  
action based on session information.  
PASS  
All sessions are up.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETR-PT (Enhanced Tone Receiver Port)  
3-655  
ETR-PT (Enhanced Tone Receiver Port)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test port PCSSpp sh  
test port PCSSpp sh  
test port PCSSpp sh  
Full Name of MO  
ETR-PT(a)  
ETR-PT  
MAJOR  
MINOR  
Enhanced Tone Receiver Port  
Enhanced Tone Receiver Port  
Enhanced Tone Receiver Port  
ETR-PT  
WARNING  
1. P is the port network number (1 for PPN). C is the carrier designation (A, B, or C). SS is the  
number of the slot in which the circuit pack resides (01 to 21).  
NOTE:  
Replacing the tone/clock circuit pack requires a special procedure which is  
described in the documentation for TONE-BD. This section also describes  
the LED display for this board.  
The TN2182 is a combined Tone Generator/Tone Detector board, providing 8  
Enhanced Tone receiver (ETR) ports. Each of these ports provides the functions  
previously found individually on DTMR-PTs, GPTD-PTs and CLAS-PTs ports.  
Thus, each port on the TN2182 can be used for any tone detection function that  
was previously done by TN748, TN420 or TN744 Tone detection boards.  
The TN2182 provides mu-law or A-law tone detection capability.  
Since the TN2182 also provides Tone/Clock function, the TN2182 circuit pack is  
the only Tone board allowable in the CMC.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-272. Enhanced Tone Receiver Port (ETR-PT) Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Tone Detector  
Test to Clear Value  
1
any  
MAJOR/  
ON  
test port PCSSpp r 2  
Audit/Update Test  
(#43)  
MINOR (a)  
18  
busyout port  
WARNING  
OFF  
ON  
release port  
PCSSpp  
257 (b)  
17666  
Tone Detection Audit  
Update Test (#43)  
MAJOR/  
MINOR (a)  
test port PCSSpp r 3  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETR-PT (Enhanced Tone Receiver Port)  
3-656  
Table 3-272. Enhanced Tone Receiver Port (ETR-PT) Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
513 (c)  
any  
Tone Detection  
Verification Test (#42)  
MAJOR/  
MINOR (a)  
ON  
test port PCSSpp r 3  
Notes:  
a. There are two possible alarm levels for this error type: major alarm and  
minor alarm. These alarm levels are dependent on the administered  
thresholds for TTR, CPTR and CCTR. Each ETR port is capable of  
operating an any of these.  
A major alarm is raised if the total number of ports capable of TTR, CPTR  
or CCTR detection currently in-service is less than or equal to 1/2 of the  
administered TTR, CPTR or CCTR threshold number.  
Otherwise, a minor alarm is raised. In either case, run the short test  
sequence against the port (ETR-PT) and follow the error code procedures  
for the individual tests.  
The threshold number of ports for service is administered using the  
change system-parameters maintenance command.  
1. Use list configuration carrier to get the board type and location. If  
the board is TN744, then do Steps 2-4; if it is TN2182, do Steps  
5-12.  
2. Execute 3 commands: busyout board UUCSS, reset board  
UUCSS, and release board UUCSS. Reset is required to reload  
RAM associated with the TN744’s DSPs. This will take all 8 tone  
detector ports out of service for a few seconds. Only 4 of the 8  
would be out of service due to the alarm. (There are 4 tone  
detectors on each of the two DSPs.) Other than the unlikely  
potential of running out of tone detector resources in the switch,  
there is no other effect when the board is reset.  
3. Test the board (test board UUCSS long).  
4. If the test passes, terminate the repair process. If the test fails,  
replace the board.  
5. Check to see if the board is duplicated (list cabinet and status  
port-network on the affected port network.)  
6. If the board is not duplicated, use test tone UUCSS long to resolve  
the error. The long test resets the board and is required to reload  
on-board RAM associated with the TN2182”s DSPs. The effect is  
that tone detectors are taken out of service momentarily and tones  
are removed from the TDM bus for about 10 seconds. This means  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETR-PT (Enhanced Tone Receiver Port)  
3-657  
no dial or touch tones during this interval, which probably will not  
affect calls in progress, but could cause a call origination to abort  
or cause a user to not get dial tone when going off hook.  
7. If all tests pass and the alarm does not resolve, retest (test tone  
UUCSS long clear).  
8. If the test passes, terminate the repair process. If it fails, replace the  
circuit pack at the customer’s convenience.  
9. If the board is duplicated, switch to the standby side (set tone).  
10. Test the alarmed board (test tone UUCSS long). This resets the  
board and is required to reload on-board RAM associated with the  
TN2182’s DSPs.  
11. If all tests pass and the alarm does not resolve, retest with test tone  
UUCSS long clear.  
12. If the test passes, terminate the repair process. If it fails, replace the  
board.  
b. The ETR-PT lost its translation. Testing the ETR-PT is sufficient to reload its  
translation. If testing the ETR port does not clear the error, then the  
TN2182 circuit pack containing the defective ETR port should be replaced  
at a time when it is convenient to remove a clock board from the system.  
Follow the procedures described in the TONE-BD section for replacing a  
tone/clock circuit pack.  
c. This error indicates the (ETR-PT) Enhanced Tone Receiver port is having  
problems detecting touch tones, call progress or MFC tones. If this error  
type is persistently logged, then the TN2182 circuit pack containing the  
defective ETR-PT should be replaced at a time it is convenient to remove a  
clock board from the system. Follow the procedures described in the  
TONE-BD section for replacing a tone/clock circuit pack.  
d. The ETR-PT lost its translation. Testing the ETR-PT is sufficient to reload its  
translation. If testing the ETR port does not clear the error, then the  
TN2182 circuit pack containing the defective ETR port should be replaced  
at a time when it is convenient to remove a clock board from the system.  
Follow the procedures described in the TONE-BD section for replacing a  
tone/clock circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETR-PT (Enhanced Tone Receiver Port)  
3-658  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following tables when  
inspecting errors in the system. By clearing error codes associated with the Tone  
Detection Verification Test, for example, you may also clear errors generated from  
other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Tone Detection Verification Test (#42)  
Tone Detection Audit/Update Test (#43)  
D/ND  
ND  
X
X
X
X
ND  
1. D = Destructive; ND = Nondestructive  
Tone Detection Verification Test (#42)  
This test checks out a single ETR port in the touch-tone receiver mode MFC tone  
detection/generation mode and general purpose tone detection mode. During  
the first portion of the test, the touch-tone receiver mode is tested. Then general  
purpose call progress and maintenance tones are tested and lastly MFC tones  
are tested.  
Table 3-273. TEST #42 Tone Detection Verification Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
none  
ABORT  
The system was not able to allocate all the resources needed for this test  
OR there was an Internal System Error.  
1
ABORT  
ABORT  
The system could not allocate all the resources needed to test the tones.  
1001  
The system was unable to put the ETR-PT in the appropriate mode to test  
it.  
1002  
ABORT  
The system could not allocate time slots for the test connection. This  
situation could occur when the system is heavily loaded. If the system is  
not heavily loaded, then test the TDM-BUS via the test tdm command.  
Refer to TDM-BUS for details.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETR-PT (Enhanced Tone Receiver Port)  
3-659  
Table 3-273. TEST #42 Tone Detection Verification Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1003  
ABORT  
The system could not allocate a Tone-Clock for the test connection. This  
may be caused by a heavy load on the system or by a faulted Tone-Clock.  
1. Check to see if there are any alarms against the Tone-Clock in the port  
network where the test aborted. If so refer to the recommended  
procedures for TONE-BD or TONE-PT.  
2. If a new Tone-Clock has been inserted, allow about 1 minute for  
maintenance to run on the newly inserted circuit pack.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
ABORT  
Circuit Pack’s response to the test request was not received within the  
allowable time period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2006  
ABORT  
This abort code indicates that the active Tone-Clock circuit pack or a Tone  
Detector circuit pack may not be functioning properly. On G3r V2 systems,  
this abort can also be caused by a mismatch between the companding  
mode administered for the system and that of the Tone Detector circuit  
pack.  
1. [G3r V2] Make sure that the companding mode of the system matches  
that of the Tone Detector: mu-law for TN748; A-law for TN420.  
2. Test the active Tone-Clock circuit pack in the port network with the test  
tone-clock PC command and refer to the TONE-BD section for  
failures.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
DTMF digits were not detected correctly.  
2100  
ABORT  
FAIL  
1-122  
1. Run the short test sequence via the test port PCSSpp sh r 1  
command.  
2. If the problem persists, the system is still operating properly but  
capacity will be reduced. To restore performance to normal, replace  
the circuit pack containing the defective ETR-PT (Enhanced Tone  
Receiver Port). Follow the procedures described in the TONE-BD  
section for replacing a tone/clock circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETR-PT (Enhanced Tone Receiver Port)  
3-660  
Table 3-273. TEST #42 Tone Detection Verification Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
102  
FAIL  
2225 Hz Modem Answer Tone was not detected correctly. This will impact  
call-classification operation.  
1. Run the short test sequence via the test port PCSSpp sh r 1  
command.  
2. If the problem persists, the system can still operate properly but  
capacity will be reduced. In order to restore performance to normal,  
replace the circuit pack containing the defective port. Follow the  
procedures described in the TONE-BD section for replacing a  
tone/clock circuit pack.  
130  
FAIL  
Forward or Backward MFC signals were not correctly generated or  
detected. This will impact MFC calls.  
1. Run the short test sequence via the test port PCSSpp sh r 1  
command.  
2. If the problem persists, the system can still operate properly but  
capacity will be reduced. In order to restore performance to normal,  
replace the TN2182 circuit pack containing the defective ETR-PT.  
Follow the procedures described in the TONE-BD section for  
replacing a tone/clock circuit pack.  
PASS  
Tone Detection Verification is successful. The ETR Port is able to  
detect/generate all necessary tones.  
Tone Detector Audit/Update Test (#43)  
A Digital Signal Processor sanity audit is performed on the ETR-PT.  
Table 3-274. TEST #43 Tone Detector Audit/Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
none  
ABORT  
The system was not able to allocate all the resources needed for this test.  
1. Wait 1 minute, and repeat the command a maximum of 5 times.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ETR-PT (Enhanced Tone Receiver Port)  
3-661  
Table 3-274. TEST #43 Tone Detector Audit/Update Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Hardware audit failed.  
FAIL  
1. Use list configuration carrier to get the board type and location. If the  
board is TN744, then do Steps 2-4; if it is TN2182, do Steps 5-12.  
2. Execute 3 commands: busyout board UUCSS, reset board UUCSS,  
and release board UUCSS. Reset is required to reload RAM  
associated with the TN744’s DSPs. This will take all 8 tone detector  
ports out of service for a few seconds. Only 4 of the 8 would be out of  
service due to the alarm. (There are 4 tone detectors on each of the  
two DSPs.) Other than the unlikely potential of running out of tone  
detector resources in the switch, there is no other effect when the  
board is reset.  
3. Test the board (test board UUCSS long).  
4. If the test passes, terminate the repair process. If the test fails, replace  
the board. Follow the procedures in TONE-BD.  
5. Check to see if the board is duplicated (list cabinet and status  
port-network on the affected port network.)  
6. If the board is not duplicated, use test tone UUCSS long to resolve the  
error. The long test resets the board and is required to reload on-board  
RAM associated with the TN2182”s DSPs. The effect is that tone  
detectors are taken out of service momentarily and tones are removed  
from the TDM bus for about 10 seconds. This means no dial or touch  
tones during this interval, which probably will not affect calls in  
progress, but could cause a call origination to abort or cause a user to  
not get dial tone when going off hook.  
7. If all tests pass and the alarm does not resolve, retest (test tone  
UUCSS long clear).  
8. If the test passes, terminate the repair process. If it fails, replace the  
circuit pack at the customer’s convenience. Follow the procedures in  
TONE-BD.  
9. If the board is duplicated, switch to the standby side (set tone).  
10. Test the alarmed board (test tone UUCSS long). This resets the board  
and is required to reload on-board RAM associated with the TN2182’s  
DSPs.  
11. If all tests pass and the alarm does not resolve, retest with test tone  
UUCSS long clear.  
12. If the test passes, terminate the repair process. If it fails, replace the  
board. Follow the procedures in TONE-BD.  
PASS  
The ETR Port has passed the sanity inquiry.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
EXT-DEV ADMIN? N (External Device Alarm)  
3-662  
EXT-DEV ADMIN? N (External Device  
Alarm)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test environment P  
Full Name of MO  
External Device Alarm  
External Device Alarm  
EXT-DEV  
EXT-DEV  
MAJOR  
MINOR  
test environment P  
1. Where P is an appropriate cabinet number determined via the PORT field from the Alarm  
or Error Log.  
NOTE:  
Use this Maintenance Object when the External Device Alarm  
Admin?field on the change system-parameters customer-options form is  
set to n.  
The Processor in carrier A monitors the EXT-DEV alarm leads. The system only  
recognizes pairs connected to the 1M and 1m (ALARM MONITOR) leads. Refer  
to the DEFINITY Communications System Generic 1 and Generic 3i Wiring,  
555-204-111, for more details.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-275. Hardware Error Log Entries and Test to Clear Values  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test environment UU r2 or  
6
1 or 5  
Any  
External Device  
Alarm Test (#120)  
MAJOR  
MINOR  
OFF  
test environment UU r 2 or  
6
2
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. One port generates a MAJOR alarm; the other port generates a MINOR alarm.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
EXT-DEV ADMIN? N (External Device Alarm)  
3-663  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Cabinet Query Test, you may also clear errors generated from other tests in the  
testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Cabinet Query Test (#79)  
D/ND  
ND  
X
X
X
X
X
X
X
X
X
X
X
X
Emergency Transfer Query Test (#124) (a)  
ND  
External Device Alarm Test (MAJOR port) (#120)  
External Device Alarm Test (MINOR port) (#120)  
Analog Ring Generator Initialization Test (#117) (b)  
Analog Ring Generator Query Test (#118) (b)  
ND  
ND  
ND  
ND  
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Refer to EMG-XFER (Emergency Transfer) section for a description of this  
test.  
b. Refer to RING-GEN (Analog Ring Generator) section for a description of  
this test.  
External Device Alarm Test (#120)  
The External Device Alarm Test requests the state of the External Device Alarm  
from the Maintenance circuit pack and reports the results. The test has no effect  
on the external device itself.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
EXT-DEV ADMIN? N (External Device Alarm)  
3-664  
Table 3-276. TEST #120 External Device Alarm Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to ABORT with error code 2000, check for system  
powering problems with the A carrier. Look for and resolve all  
AC-POWER alarms. Then, repeat the test.  
3. If the test continues to ABORT with a 2000 error code, check for and  
resolve all SYSAM errors. Then, repeat the test.  
2029  
2319  
2320  
2500  
ABORT  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ANY  
The External Device Alarm has been activated by the external device.  
1. Clear the major alarm on the external device, and rerun the test.  
2. If the test still fails, then disconnect the External Device Alarms from  
the Maintenance circuit pack and rerun the test.  
3. If the test still fails, then there is a problem with the Maintenance circuit  
pack that is reporting the alarm. This circuit pack should be replaced.  
There are failures that can occur on Maintenance circuit pack’s that  
will not be detected by their respective maintenance, but which will  
cause many environment tests to fail. If many environment tests are  
failing, the suspect circuit pack should be replaced and the test rerun.  
PASS  
If there is a problem with the external device, but the Maintenance circuit  
pack connected to the device reports no alarm, then the External Device  
may not be properly reporting the problems or the External Device may not  
be properly connected to the External Device.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
EXT-DEV ADMIN? Y (External Device Alarm)  
3-665  
EXT-DEV ADMIN? Y (External Device  
Alarm)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
EXT-DEV  
EXT-DEV  
EXT-DEV  
MAJOR  
test eda-external-device-alrm physical  
location  
External Device Alarm  
External Device Alarm  
External Device Alarm  
MINOR  
test eda-external-device-alrm physical  
location  
WARNING  
test eda-external-device-alrm physical  
location  
NOTE:  
Use this Maintenance Object when the External Device Alarm  
Admin?field on the change system-parameters customer-options form is  
set to y. You must have INADS or INIT login permission to administer  
EXT-DEV Alarm.  
Generic 3i Maintenance circuit packs each have alarm leads which can be  
connected to external devices such as Uninterruptible Power Supplies (UPS) or  
adjuncts such as AUDIX. Certain conditions on the external device close the  
contacts on the alarm leads to notify the switch which in turn originates an  
EXT-DEV alarm.  
The special locations UUmajor and UUminor are used to designate the major or  
minor maintenance board alarm connection for cabinet UU. The major/minor  
designation specifies the port, not the alarm level associated with the  
connection; for example, the “major” port can be administered as a major, minor,  
or warning alarm, and the “minor” port can be administered as a major, minor or  
warning alarm. In addition Analog line ports can also be administered as external  
device alarms.  
NOTE:  
An unadministered maintenance board external device alarm port, that is  
sensing a contact closure will have an entry in the Error Log and in the  
Alarm Log. INADS will not receive warning alarms.  
The Processor monitors the EXT-DEV alarm leads. The system only recognizes  
pairs connected to the 1M and 1m (ALARM MONITOR) leads. Refer to the  
DEFINITY Communications System Generic 1 and Generic 3i Wiring,  
555-204-111, for more details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
EXT-DEV ADMIN? Y (External Device Alarm)  
3-666  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-277. EXT-DEV ADMIN? Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
0
0
Any  
Any  
test eda-external-device-alrm  
physical location r 2 or 6  
1 or 5  
Any  
External Device  
Alarm Test (#120)  
Any  
OFF  
test eda-external-device-alrm  
physical location r 2 or 6  
NOTE:  
The loss of -48 volt power will prevent detection of an external device  
alarm. AC-POWER and DC-POWER alarms could indicate the loss of the  
external device alarm -48 volt power source. ALARM-PT alarms may also  
indicate a loss of power. When analog line ports are administered as analog  
line external device alarms loss of -48 volts will prevent detection of an  
external device alarm.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
External Device Alarm Test, you may also clear errors generated from other tests  
in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
ND  
External Device Alarm Test (MAJOR port) (#120)  
External Device Alarm Test (MINOR port) (#120)  
External Device Alarm Test (WARNING port) (#120)  
X
X
X
X
X
X
ND  
ND  
1. D = Destructive; ND = Nondestructive  
External Device Alarm Test (#120)  
The External Device Alarm Test requests the state of the External Device Alarm  
from a Maintenance circuit pack and reports the results. The test has no effect on  
the external device itself.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
EXT-DEV ADMIN? Y (External Device Alarm)  
3-667  
Table 3-278. TEST #120 External Device Alarm Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 time.  
The Expansion Port Network containing this equipment is not available  
1035  
2000  
Look for and resolve all Expansion Port Network problems with this  
cabinet.  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 time.  
2. (Maintenance Board) If the test continues to ABORT with error code  
2000, check for system powering problems with the A carrier. Then,  
repeat the test.  
3. (Maintenance Board) If the test continues to ABORT with a 2000 error  
code, check for and resolve all maintenance circuit pack errors. Then,  
repeat the test.  
2029  
2100  
2319  
2320  
2500  
ABORT  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ANY  
The External Device Alarm has been activated by the external device.  
1. Clear the major alarm on the external device, and rerun the test.  
2. If the test still fails, then disconnect the External Device Alarm Leads  
from the Maintenance circuit pack and rerun the test.  
3. If the test still fails, then there is a problem with the analog external  
device alarm port or the Maintenance circuit pack that is reporting the  
alarm. This circuit pack should be replaced. There are failures that can  
occur on the Maintenance circuit pack that will not be detected by  
their respective maintenance, but which will cause many environment  
tests to fail. If many environment tests are failing, the suspect circuit  
pack should be replaced and the test rerun.  
PASS  
If there is a problem with the external device, but the administered analog  
line external device alarm, or the administered Maintenance circuit pack  
connected to the device reports no alarm, then the External Device may  
not be properly reporting the problems or the External Device may not be  
properly connected to the External Device Alarm Lead.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
GPTD-PT [General Purpose Tone Detector Port (CPTR)]  
3-668  
GPTD-PT [General Purpose Tone  
Detector Port (CPTR)]  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
GPTD-PT  
GPTD-PT  
GPTD-PT  
MAJOR  
test port PCSSpp sh  
test port PCSSpp sh  
release port PCSSpp  
General Purpose Tone Detector Port  
(CPTR)  
MINOR  
General Purpose Tone Detector Port  
(CPTR)  
WARNING  
General Purpose Tone Detector Port  
(CPTR)  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or  
C); SS is the address of the slot in the carrier where the circuit pack is located (for example, 01, 02,  
..., etc.); and pp is the 2-digit port number (for example, 01).  
The General Purpose Tone Detector (GPTD) Port, also known as Call Progress  
Tone Receiver (CPTR), resides on the TN2182 combined tone detector and tone  
clock circuit pack. (The TN744 is used for additional ports.) There are two GPTD  
ports and four Dual Tone Multifrequency Receiver (DTMR) ports on a Tone  
Detector circuit pack. The GPTD port is used to perform level measurements of  
test tones and to detect call progress tones. Examples of call progress tones are  
dial tone, ring back, busy, alert, confirmation, and recall dial. The abilities of the  
GPTD port to perform level measurements of test tones and to detect call  
progress tones are essential for maintenance of other circuit packs (for example,  
Tone-Clock).  
The GPTD maintenance feature defines a set of tests to ensure that the general  
purpose tone detection capability of the GPTD port is functioning properly. For all  
Tone Detector circuit pack level errors (DETR-BD), refer to the‘‘XXX-BD (Common  
Port Circuit Pack)’’ Maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-BCH (H.323 B-Channel)  
3-669  
H323-BCH (H.323 B-Channel)  
No maintenance diagnostic tests exist for this object.  
H.323 signaling is very similar to ISDN Q.931 signaling. In order to take advantage of  
existing Definity ISDN call processing software, H.323 trunk call processing includes H.323  
signaling groups, H.323 D-channels and H.323 B-channels. H.323 Signaling groups are  
similar in concept to ISDN PRI signaling groups. H.323 D-channels are an artificial  
fabrication created only to allow maximum re-use of system ISDN code. H.323 B-channels  
are also an artificial fabrication.  
No physical hardware components make up the H.323 B-channel object discussed here.  
Along with the D-channel, these objects allow existing ISDN call processing to be re-used  
for H.323 trunking. The H.323 signaling group is not a collection of physical D-channels that  
exist on one or more DS1 facilities. The H.323 signaling group can be considered to be one  
D-channel that physically rides on a C-LAN port and the IP network. Unlike ISDN  
D-channels, the H.323 D-channel may actually come up and down on a call-by-call basis.  
So the H.323 D-channel is actually a TCP/IP signaling channel. Layer 1 and 2 of this  
signaling channel can be monitored by IP PING testing.  
Performance in terms of voice latency for a signaling group is monitored by background  
measurements being collected by the TN802B Media Processor board.  
H.323 B-channels actually use TN802B Media Processor ports to carry the actual bearer.  
The TN802B is a service circuit. On a call-by-call basis, any port of a TN802B may be  
serving an H.323 station or a H.323 B-channel. Status information may exist for a specific  
H.323 B-channel, and an H.323 B-channel may be busied out and released, but no  
maintenance diagnostic tests will exist for the object.  
Errors are logged for craft busyout conditions. The system receives service state updates  
for craft-driven busyout/release. Under normal conditions the system automatically places  
H.323 B-channels into or out of service when it receives an H.323 signaling-group service  
state update. Craft busyout drops active calls.  
Error Log Entries and Test to Clear Values  
Table 3-279. H323-BCH B-Channel Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Service State  
OOS  
18  
Any  
B-channel busied out  
Warning  
off  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-BCH (H.323 B-Channel)  
3-670  
Notes:  
a. Error Type 18: this error indicates that this specific H323 trunk group  
member has been craft busied-out.  
System Technician Commands  
The following commands are available to the system technician:  
■
busyout port UUCSSpp – this command on a specific H.323 B-channel  
drops any active call that may exist on that B-channel and effectively  
reduces the trunk group capacity by one. No physical piece of hardware  
is removed from service.  
■
■
release port UUCSSpp – this command on a specific H.323 B-channel  
effectively increases the trunk group capacity by one. No physical piece  
of hardware is actually added to service.  
status trunk grp/mbr – this command is used to find the current status of  
the specific B-channel. Additional status for an H.323 B-channel shows  
near and far-end IP signaling addresses, near and far-end H.245  
addresses, tunneling status, call reference value for an active call and the  
H.323 conference ID.  
■
test port UUCSSpp – this command results in the message No tests  
applicable to this object.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-SGRP (H.323 Signaling Group)  
3-671  
H323-SGRP (H.323 Signaling Group)  
MO Name (in  
Alarm Log)  
Initial Command to  
Run  
Alarm Level  
MINOR  
Full Name of MO  
H323 Signaling Group  
H323 Signaling Group  
1
H323-SGRP  
H323-SGRP  
test sig-group grp#  
1
WARNING  
test sig-group grp#  
1. grp# is the signaling group number (1-166); the test sequence can be either short or long.  
The H.323 Signaling Group (H323-SGRP) maintenance object supports a  
signaling channel for H.323 Trunk connections. The Media Processor (MedPro)  
TN802B circuit pack provides audio connectivity, working in concert with a  
C-LAN (TN799B) circuit pack that provides control signaling to support an H.323  
connection.  
The H.323 signaling group (323-SGRP) is a signaling channel that physically  
rides on a C-LAN ethernet port (socket) and the IP network. Unlike ISDN  
D-channels, the H.323 channel may actually come up and down on a call by call  
basis. The H.323 channel is actually a TCP/IP signaling channel. Layers 1 and 2  
of this signaling channel are monitored by IP PING testing.  
Error Log Entries and Test to Clear Values  
Table 3-280. 323-SGRP Signaling Group Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
test sig-group grp#  
test sig-group grp#  
0
0
Any  
Any  
1 (a)  
Any  
Any  
Any  
Ethernet Port Status Test  
#1386  
MINOR  
OFF  
OFF  
OFF  
257 (b)  
513(c)  
H.323 SGRP PING Test  
#1387  
MINOR  
test sig-group grp#  
test sig-group grp#  
H.323 SGRP PING Test  
#1387  
WARNING  
769(d)  
1025(e)  
1281(f)  
Any  
Any  
Any  
WARNING  
MINOR  
NONE  
OFF  
OFF  
MEDPRO Status Test  
#1392  
test sig-group grp#  
1537(g)  
Any  
NONE  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-SGRP (H.323 Signaling Group)  
3-672  
Notes:  
a. Error Type 1: this error indicates that the C-LAN ethernet port used to  
carry the signaling for this H.323 signaling group is out of service. To  
determine which C-LAN had been administered for this signaling group,  
find the near-end node name on the signaling group form; then find the  
C-LAN with the same node name on the ip-interfaces form. Check for  
errors on this C-LAN board.  
b. Error Type 257: this error tracks failures of the H.323 signaling-group  
PING test. See H.323 signaling-group PING test failures documented later  
in this maintenance object.  
c. Error Type 513: this error tracks excessive round trip delay of the H.323  
signaling-group PING test (if the round-trip delay exceeds 4 seconds).  
d. Error Type:769: this error indicates that test packets sent from a media  
processor circuit pack to the far-end ip address specified on the  
signaling-group form have exceeded the IP latency and loss thresholds,  
as administered on the system-parameters maintenance form.  
Exceeding these thresholds indicates that the IP network may not be  
providing sufficient quality service for adequate transmission of voice. If  
the signaling group has been administered to enable BYPASS, then error  
type 1025 should also occur.  
e. Error Type 1025: this error indicates that the signaling group has been  
placed into a BYPASS condition due to IP network congestion. The  
signaling group accepts incoming calls, but all outgoing calls are denied.  
The system routes these calls over a secondary route if one has been  
administered.  
f. Error Type 1281: this error implies that no MedPro resources are  
in-service to provide media connections for the trunk members of the  
signaling group. Check for errors against the MEDPRO and MEDPROPT  
maintenance objects. This error causes all H323 B Channels to be in an  
out-of-service near-end state.  
g. Error Type 1537: this error indicates that the far end of the signaling  
group is not ready to handle audio bearer. If the other end of this signaling  
group is also a DEFINITY, this error means the DEFINITY on the other end  
does not have MEDPRO in-service for its signaling group.  
In the absence of error 1281, this error will place the H323 B Channels into  
an out-of-service far-end state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-SGRP (H.323 Signaling Group)  
3-673  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
CLAN Ethernet Status Test (#1386), for example, you may also clear errors  
generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
CLAN Ethernet Status Test (#1386)  
MedPro Status Test (#1392)  
D/ND  
ND  
X
X
X
X
X
X
ND  
H.323 Signaling Group Ping Test (#1387)  
ND  
1. D = Destructive; ND = Nondestructive  
CLAN Ethernet Status Test (#1386)  
This test is non-destructive.  
This test checks the status of the C-LAN ethernet port that originated this  
signaling group. If the C-LAN ethernet port is in-service, the test passes, if it is  
out of service the test fails.  
NOTE:  
Failure of this test puts the SIG-GRP in the OOS state.  
Table 3-281. TEST #1386 CLAN Ethernet Status Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2500  
ABORT Internal system Error.  
1. Retry the command at 1-minute intervals a maximum of 3 times  
2800  
ABORT A C-LAN ethernet port that corresponds to the near-end address of the  
signaling group has not been administered.  
FAIL  
The C-LAN ethernet port that corresponds to the near-end address of this  
signaling group and all trunk members controlled by this signaling group  
are out of service.  
1. Check the system for errors against the out of service C-LAN board.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-SGRP (H.323 Signaling Group)  
3-674  
Table 3-281. TEST #1386 CLAN Ethernet Status Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The C-LAN ethernet port that corresponds to the near-end address of this  
signaling group is in-service.  
H.323 Signaling Group Ping Test (#1387)  
This test is nondestructive.  
This test is only run for those signaling groups that have an administered far-end  
IP address. If the H.323 signaling group does not have an administered far-end  
IP address the test aborts.  
The test determines the local C-LAN through which the signaling originates and  
the far-end terminating IP address. It then requests the local C-LAN to execute a  
PING on the far-end address. If the ping is successful, the test passes, if the  
PING is not successful, the test fails.  
NOTE:  
Multiple failures of this test can take the H.323 signaling group out of  
service.  
If the PING is successful, this test looks at the PING round trip delay. If a round  
trip delay of greater than 4 seconds is reported, a separate error is logged.  
Excessive round trip delays within the signaling group do not take the signaling  
group out of service.  
Services can execute the standard ping command using the C-LAN board  
address and far-end IP address from the signaling group form to see the actual  
round-trip delay.  
This test checks the circuitry involved in the data path of a peer-to-peer IP layer  
connection.  
This nondestructive test runs due to in-line errors, during periodic and schedule  
maintenance, and on demand.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-SGRP (H.323 Signaling Group)  
3-675  
Table 3-282. TEST #1387 H.323 Signaling Group Ping Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1005  
2800  
ANY  
ANY  
ABORT  
ABORT  
ABORT  
FAIL  
This signaling group has no administered far-end address. The test does  
not apply to this configuration.  
A C-LAN ethernet port that corresponds to the near-end address of the  
signaling group has not been administered.  
Refer to ETH-PT, Test #1281, C-LAN port PING test for a more detailed  
description of the reasons for the abort.  
The far-end of the signaling group could not be reached.  
1. Refer to ETH-PT, Test #1281, C-LAN port PING test for a more detailed  
description of the reasons for the failure.  
PASS  
The system can PING the administered far-end address of the H323  
signaling group.  
MedPro Status Test (#1392)  
This test is non-destructive.  
Voice calls over H.323 signaling groups are carried by media processor  
resources. If there are no media processor resources in-service for the specified  
signaling group, the H323 B Channels are placed into out-of-service near-end, so  
that calls may flow to other trunk groups controlled by different signaling groups.  
On the ip-interfaces form, the field Inter-region IP connectivity  
allowed? may be set to y or n. If the field is set to n, only media processors in  
the same region as the signaling group can carry calls.  
This test determines if a media processor is in-service in the same region as the  
C-LAN that carries this signaling group. If the field is set to y, any media  
processor in the system can carry calls. This test determines if a media  
processor is in-service in any region.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-SGRP (H.323 Signaling Group)  
3-676  
Table 3-283. TEST #1392 MedPro Status Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ANY  
ABORT  
FAIL  
Internal system Error.  
No in-service Medpro ports exist for use by this signalling group. The  
H323 B Channels are placed into OOS-NE.  
1. Check the system for errors against MEDPRO and MEDPROPT  
maintenance objects.  
PASS  
In-service Medpro ports exist for use by this signaling group.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-STN (H.323 IP Station)  
3-677  
H323-STN (H.323 IP Station)  
MO Name (in  
Alarm Log)  
Initial Command to  
Alarm Level  
Run  
Full Name of MO  
H.323 IP Station  
H323-STN  
WARNING  
test station extension  
This maintenance object covers implementation of the maintenance for native  
mode H.323 endpoints. Native mode H.323 applications such as NetMeeting or  
Proshare only provide what is needed to support the H.323 standard. There is  
very little that Definity can invoke in the maintenance area. Definity will report  
errors as they are detected via the RAS registration and keep-alive mechanism.  
Definity will PING the endpoint both via the signaling path (i.e. via C-LAN) and via  
the media path (i.e. via Medpro).  
This station type is not attached to a port board. Insertion of the station is not  
driven by board insertion, rather it is driven by successful registration of the  
endpoint. It is maintained via a set of explicit TCP/IP ping requests and errors  
reported by the switch software, which terminates the H.323 signaling portion of  
each endpoint. The MO follows standard maintenance methodology and  
supports test, busyout, release and status commands.  
Error Log Entries and Test to Clear Values  
Table 3-284. H323-STN IP Station Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
0
0
Any  
Any  
test station extension  
1 (a)  
Registration Status Inquiry  
Test (#1372)  
WARNING  
WARNING  
WARNING  
OFF  
OFF  
OFF  
257 (b)  
513(c)  
Signaling Path PING Test  
(#1373)  
Media Path PING Test  
(#1374)  
Notes:  
a. Error Type 1: this error reports the registration status of the endpoint. If  
call processing SW claims the endpoint is registered and receives  
keep-alive handshakes from the endpoint, the test passes. If keep-alive  
handshaking has failed, the test fails. If the user has intentionally  
un-registered from DEFINITY, the station is now basically an AWOH station  
and is no longer being maintained; no tests will run for this station.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-STN (H.323 IP Station)  
3-678  
b. Error Type 257: this error tracks failures of the signaling path PING test.  
The test attempts to send a PING packet to the endpoint IP address, as  
reported during registration. The PING packet originates with the C-LAN  
board through which the endpoint is registered. If the PING response  
packet is received, the test passes. If the PING response packet times  
out, the test fails.  
c. Error Type 513: this error tracks failures with the media path PING test.  
The test attempts to send a PING packet to the endpoint IP address, as  
reported during registration. The PING packet originates with a Media  
Processor board. Any Media Processor board may be used as long as it  
is administered to be in the same network region as the C-LAN board  
through which the endpoint is registered. If the PING response is  
received, the test passes. If the PING response packet times out, the test  
fails.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Signaling Path PING Test (#1373), for example, you may also clear errors  
generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Registration Status Inquiry Test (#1372)  
Signaling Path PING Test (#1373)  
Media Path PING Test (#1374)  
D/ND  
ND  
X
X
X
X
X
X
ND  
ND  
1. D = Destructive; ND = Nondestructive  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-STN (H.323 IP Station)  
3-679  
Registration Status Inquiry Test (#1372)  
The Registration status inquiry reports the H.323 registration status of the  
endpoint. An endpoint must be registered and authenticated in order to receive  
service from the system.  
Registration is initiated when the endpoint user attempts to login using the Lucent  
registration software application running on the endpoint PC. The user must  
provide a valid extension and security code. The registration messages are sent  
to the IP address of a C-LAN ethernet port.  
A registered extension has a port type SNNNNN, where N is a digit from 0-9. A  
non-registered extension has an X port.  
Table 3-285. TEST #1372 Registration Status Inquiry  
Error  
Code  
Test  
Result  
Description/Recommendation  
1,2,3  
FAIL  
The endpoint is not successfully registered.  
1. Verify that the user is entering:  
■
■
the correct extension and security code  
the C-LAN IP address  
2. Verify that the extension has been enabled for IP softphone  
operation.  
3. If many endpoints cannot register, investigate any errors of the  
C-LAN ethernet port.  
4. Examine the ethernet cabling from the endpoint PC to the ethernet  
hub.  
PASS  
The endpoint is successfully registered and continues to respond to  
registration handshaking.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-STN (H.323 IP Station)  
3-680  
Signaling Path PING Test (#1373)  
This test is nondestructive.  
The test determines the local C-LAN through which the signaling originates and  
the endpoint’s IP address. It then requests the local C-LAN to execute a PING on  
the endpoint’s address. If the PING is successful, the test passes, if the PING is  
not successful, the test fails.  
NOTE:  
Multiple failures of this test can take the H.323 IP Station out of service.  
This test checks the circuitry involved in the data path of a peer-to-peer IP layer  
connection.  
This nondestructive test runs due to in-line errors, during periodic and schedule  
maintenance, and on demand.  
Table 3-286. TEST #1373 Signaling Path PING Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Could not locate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
2100  
2500  
1003  
ABORT  
ABORT  
FAIL  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
Ping to the destination failed.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Investigate any C-LAN ethernet port errors.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-STN (H.323 IP Station)  
3-681  
Table 3-286. TEST #1373 Signaling Path PING Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1007  
FAIL  
The system could not PING the registered endpoint via the C-LAN.  
1. Verify that at least one destination reachable through this port. PING  
this destination (ping ip-address xxx.xxx.xxx.xxx).  
2. If the PING to any destination is successful through this port, the link is  
up.  
3. If PING to all destinations fail, test the C-LAN port (test port UUCSSpp  
short) and follow repair procedures for Session Status Test (#1286)  
failures.  
4. If only this station cannot be pinged:  
■
■
■
Make sure the PC is up  
Make sure the PC has a network connection (ethernet or dialup)  
Check the ethernet cabling  
PASS  
The system can successfully send IP packets to the registered endpoint  
from the C-LAN.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
H323-STN (H.323 IP Station)  
3-682  
Media Path PING Test (#1374)  
This test is nondestructive.  
The test selects a Media Processor board. It then requests the local Media  
Processor to execute a PING on the endpoint address. If the PING is successful,  
the test passes, if the PING is not successful, the test fails.  
Services can execute the standard ping command using the Media Processor  
board address and endpoint IP address to see the actual round-trip delay.  
This test checks the IP network connectivity needed for audio packets to be sent  
to the endpoint.  
This nondestructive test runs due to in-line errors, during periodic and schedule  
maintenance, and on demand.  
Table 3-287. TEST #1374 Media Path PING Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Could not locate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
2100  
ABORT  
2500  
ABORT  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
2806  
ANY  
ABORT  
FAIL  
No Media Processor board found to use for this test.  
The system could not PING the registered endpoint from a Media Processor  
board. This may result in calls with no talk path.  
1. If the Registration Status Inquiry Test (#1372) fails, follow those  
procedures.  
2. Refer to MEDPRO, Test #1378, for a detailed description of the error  
codes.  
PASS  
PING through this Media Processor is successful.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-BD (Hybrid Line Circuit Pack)  
3-683  
HYB-BD (Hybrid Line Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
Hybrid Line Circuit Pack  
Hybrid Line Circuit Pack  
HYB-BD  
HYB-BD  
MIN  
WRN  
test board PCSS sh  
test board PCSS sh  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); and SSis the address of the slot in the carrier where the circuit pack  
is located (for example, 01, 02, ..., etc.).  
Refer to ‘‘XXX-BD (Common Port Circuit Pack)’’ Maintenance documentation for  
circuit pack level errors. See also ‘‘HYB-LINE (Hybrid Line)’’ Maintenance  
documentation for related line information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-684  
HYB-LINE (Hybrid Line)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to  
1
Run  
Full Name of MO  
Hybrid Line  
HYB-LINE  
HYB-LINE  
Minor  
Warning  
test port PCSSpp l  
test port PCSSpp l  
Hybrid Line  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for  
example, A, B, or C); SS is the address of the slot in the carrier where the circuit pack  
is located (for example, 01, 02, ..., etc.); and pp is the 2-digit port number (for  
example, 01).  
Hybrid Line is the user-friendly name for Hybrid Line, which was previously used  
to denote the Multifunction Analog Telephone. The Hybrid Line set is also known  
as an SCS (Small Communications System).  
The TN762B Hybrid Line circuit pack supports eight of these multifunction  
analog telephone sets, as shown in the following figure. The Hybrid Line sets use  
three pairs of wires: an analog voice pair, a transmit/receive pair, and a power  
pair.  
HYBRID  
LINE  
CIRCUIT  
PACK  
(1)  
VOICE  
PORT  
TERMINAL  
PBX  
(8)  
VOICE  
PORT  
TERMINAL  
HYBRID LINE  
Figure 3-20. Hybrid Station Interactions  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-685  
This section refers only to the HYB-LINE (Hybrid Line) maintenance that is  
performed. Please note that the HYB-LINE (Hybrid Line) maintenance is closely  
related to, and interacts with, the HYB-BD (Hybrid Line circuit pack) maintenance  
in some instances. Some of the results of maintenance testing of the Hybrid Line  
may be affected by the health of the Hybrid Line circuit pack. This interaction  
should be kept in mind when investigating the cause of reported Hybrid Line  
problems.  
There are instances in this section where "service states" of a station are  
mentioned. It is helpful to understand what is meant by the different service  
states that may exist. An explanation of these service states follows:  
■
Out-of-Service–The port, and thus the station, have been removed from  
service. A busyout of a port causes it to be out-of-service.  
■
Ready-for-Service–Once a port on the circuit pack has been put into  
service, the voice terminal must communicate that it is present. The time  
between these two events is the time when the terminal is in the  
ready-for-service state.  
■
In-Service–Once the system has received a message from the voice  
terminal communicating that it is present, the station is put into the  
in-service state. The terminal can also be forced into the in-service state if  
it goes off-hook while it is in the ready-for-service state.  
When the status station command has been run, and the status screen  
appears, the status is reported as either out-of-service or in-service, which mean  
exactly as stated in the above list, or disconnect, which means the station is in  
the ready-for-service state.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-288. Hybrid Line Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test port PCSSpp sh r 1  
1 (a)  
Any  
Any  
None  
WARNING  
OFF  
15 (b)  
Hybrid Audits Test  
(#61)  
18 (c)  
0
busyout port  
PCSSpp  
WARNING  
WARNING  
OFF  
release port PCSSpp  
test port PCSSpp sh  
130 (d)  
257 (e)  
None  
None  
ON  
2
40988  
MIN/WRN  
OFF  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-686  
Table 3-288. Hybrid Line Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
513 (f)  
769 (g)  
1025  
40965  
Hybrid Line Audits  
Test (#61)  
WARNING  
OFF  
test port PCSSpp sh r 4  
Remote Dig Loop  
Around Test (#59)  
WARNING  
OFF  
ON  
test port PCSSpp sh r 3  
test port PCSSpp l r 3  
test port PCSSpp l r 3  
2
Hybrid & Conf.  
Circuits Test (#57)  
MIN/WRN  
1281 (h)  
Local Digital Loop  
Around Test (#58)  
WARNING  
WARNING  
ON  
1537 (i)  
1793  
40968  
None  
OFF  
ON  
2
TDMNPE Crosstalk  
Test (#6)  
MIN/WRN  
test port PCSSpp l r 3  
2049 (j)  
2049 (k)  
32770  
40967  
None  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
2. Major or Minor alarms on this MO may be downgraded to Warning alarms based on the values used in  
the set options command.  
Notes:  
a. Indicates a defective data link. An off-board problem was detected by port  
circuit. Verify that the Hybrid set is connected and that the EPF test  
passes. If data transmission problems are experienced, check for  
defective wiring or a defective voice terminal, or move terminal closer to  
the switch (in terms of feet of wire from the jack to the switch). If the  
problem still exists, replace the circuit pack. Once the problem has been  
resolved, the alarm is retired after a predetermined period of time.  
b. This is a software audit error that does not indicate any hardware  
malfunction. Run Short Test Sequence and investigate associated errors  
(if any).  
c. This error type is logged when the port in question is busied out by  
maintenance personnel. Make sure port is released from busyout via the  
release port PCSSpp command.  
d. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-687  
e. This indicates that the EPF has been turned off due to an overcurrent  
condition at the voice terminal. Check for defective wiring or a damaged  
jack, and make sure the voice terminal is a Hybrid set. Once the problem  
has been resolved, the alarm is retired after a predetermined period of  
time.  
f. This indicates that the voice terminal has probably been disconnected or  
that there is a problem in the wiring to the terminal. Make sure that the  
voice terminal is connected or check for defective wiring to the voice  
terminal.  
g. Note that Error Types 769 and 1281 by themselves create Warning alarms  
only, but if both are present, a Minor alarm is logged.  
h. This indicates that there is something wrong with the data link to the voice  
terminal. An in-line maintenance error has generated an off-board  
warning. Ignore it if there are no complaints. Otherwise, make sure the  
voice terminal is connected, check for defective wiring, check for a  
defective voice terminal, and move voice terminal closer to the switch (in  
terms of feet of wire from the jack to the switch). If the problem still exists,  
replace the circuit pack.  
i. This indicates that the station went off-hook while in the disconnect state.  
Use the status station command to determine the state of the station. The  
off-hook should have moved the station to in-service. No system  
technician action is necessary.  
j. This is the code that is generated when the link between the circuit pack  
and the voice terminal is successfully reset. No system technician action  
is necessary.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Local Digital Loop Around Test, for example, you may also clear errors generated  
from other tests in the testing sequence.  
Table 3-289. System Technician-Demanded Tests: HYB-LINE  
ShortTest  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Local Digital Loop Around Test (#58)  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
X
X
X
ND  
Hybrid Electronic Power Feed Test (#56)  
Hybrid Circuit and Conference Circuit Test (#57)  
ND  
ND  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-688  
Table 3-289. System Technician-Demanded Tests: HYB-LINE — Continued  
ShortTest  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Remote Digital Loop Around Test (#59)  
Station Lamp Update Test (#60)  
Station Audits Test (#61)  
D/ND  
ND  
X
X
X
X
X
X
X
X
ND  
ND  
Ringer Update Test (#62)  
ND  
1. D = Destructive, ND = Non-destructive  
NPE Crosstalk Test (#6)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per port basis. The NPECrosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is part of a port’s Long Test Sequence and takes  
about 20 to 30 seconds to complete.  
Table 3-290. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension number of the port. Use the status station  
command to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-689  
Table 3-290. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1001  
ABORT  
Could not allocate the necessary system resources to run this test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
1003  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM Bus) Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
(TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension number of the port. Use the status station command to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. You must  
wait until the port is idle before retesting. Attendants are always in use  
(off-hook) if the handset is plugged in and the port is not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1018  
ABORT  
Test disabled via administration. This only applies to analog stations. The  
default for this field is ‘y,’ so you may want to determine why it has been  
turned off for this station.  
1. To enable test, set the Testfield on the station administration screen  
for the particular analog station being tested to y. Use the change  
station <extension> command.  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-690  
Table 3-290. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2020  
ABORT  
The test did not run due to an already existing error on the specific port or  
a more general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit  
pack and attempt to diagnose the already existing error.  
2100  
Any  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
This test can fail due to on-board or off-board problems. Off-board  
problems of concern include EXP-INTF faults, TDM-BUS faults, and faults  
associated with the tone detectors/tone generators. Clear all off-board  
problems before replacing the board. Keep in mind that a TDM-BUS  
problem is usually the result of a faulty board connected to the backplane  
or bent pins on the backplane.  
1. Look for EXP-INTF errors in the error log. If present, refer to the  
EXP-INTF Maintenance documentation.  
2. Look for TDM-BUS errors in the error log. If present, refer to the  
TDM-BUS Maintenance documentation.  
3. Retest the board when the faults from steps 1 and 2 are cleared.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated using other port tests and examining  
station, trunk, or external wiring.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-691  
Hybrid Electronic Power Feed Test (#56)  
In this test, the software requests that the EPF be turned on for a given port. An  
attempt is made to turn on the power unit from the station. If no current is being  
drawn, this probably indicates that the station is not connected. If an overcurrent  
condition is sensed (that is, too much current is being drawn), this may indicate a  
short in the loop or a defective voice terminal. Depending on what condition is  
sensed, a message is returned stating that either the EPF was turned on  
successfully with no problems or that an overcurrent condition is sensed. This  
test is repeated once more five seconds later. If either test is not successful, the  
test aborts (see first ABORT entry in the table below).  
Table 3-291. TEST #56 Hybrid Electronic Power Feed Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension number of the port. Use the status station  
command to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
EPF test passed. The message to turn on the power to the station was  
successfully sent to the port.  
1. Although this test never returns a FAIL result, after running this test, the  
Error Log should be checked for any entries with Error Type 257 to  
examine the real results of this test.  
2. If Error Type 257 does not appear in the Error Log within 10 seconds  
after completion of this test, it is safe to assume that the test sensed no  
problems with the power to the station. To verify that the station is  
powered up correctly, run a self-test on the station, if available, and  
check that all the feature buttons are operating.  
3. If Error Type 257 appears in the Error Log, this indicates some problem  
with the power to the station. The system technician should check for a  
short in the wiring, a damaged jack, a defective voice terminal, or an  
incorrect type of terminal.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-692  
Table 3-291. TEST #56 Hybrid Electronic Power Feed Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Hybrid Circuit and Conference Circuit Test (#57)  
This test checks the amount of reflection from the Hybrid loop around circuitry  
and a Conference Test. Please be aware that if no station is connected to the port  
being tested, the results of the test are not valid. The Tone-Clock circuit pack  
places a 1004-Hz tone on a time slot that the port circuit is listening on. A GPTD  
is connected to another time slot that the same port circuit is talking on. The  
on-board microprocessor places the port in the loop around mode and the GPTD  
measures the level of the reflected signal.  
The Conference Test is performed after the Circuit Test. The Conference Circuit  
Test verifies that the NPE is able to listen to several test tones and correctly  
conference them together. The test is executed in two parts. The first half of the  
test checks the operation of the NPE’s first three conference channels. The NPE  
is put in the loop around mode and instructed to talk on a selected time slot and  
listen to the 1004-Hz tone using the first three Conference Channels. The signal  
level and noise level of the conferenced output are then measured using a GPTD  
and checked to verify that they are within an acceptable range.  
The second half of the Conference Test checks the operation of the NPE’s  
remaining four Conference Channels and follows the same procedure as the  
preceding paragraph.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-693  
Table 3-292. TEST #57 Hybrid Circuit and Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension number of the port. Use the status station  
command to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM Bus) Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
(TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension number of the port. Use the status station command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. You must wait  
until the port is idle before retesting. Attendants are always in use  
(off-hook) if the handset is plugged in and the port is not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-694  
Table 3-292. TEST #57 Hybrid Circuit and Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
7
FAIL  
Conference Test failed. User may be able to use conference circuit without  
difficulty in some cases. In other extreme cases, conference calling will be  
totally restricted.  
The failure may be due to off-board circumstances, the most common of  
which is an off-hook occurring during the test. Also, check the error logs  
against the GPTD-BD, the TONE-BD, and the TONE-PT.  
1. This error can be caused by a disconnected terminal. First, ensure that  
the terminal is connected and the wiring is OK.  
2. Then, issue the display port and the status station commands to  
determine if the station is idle. If it is idle, issue the test port command  
for this port.  
3. If test continues to fail, issue the busyout port and the release port  
commands, and then retest the port.  
4. It is possible that the port may still be functional from a user’s point of  
view.  
57  
FAIL  
Hybrid Circuit Test failed. This could result in noisy or bad connections.  
1. This error can be caused by a disconnected terminal. First, ensure that  
the terminal is connected and the wiring is OK.  
2. Run circuit pack tests to check the Tone Generator circuit pack and  
the Tone Detector circuit pack using the test board PCSS short  
command.  
3. Resolve any problems that are detected on the Tone Generator circuit  
pack or Tone Detector circuit pack.  
4. If the Tone Generator and Tone Detector circuit packs are functioning  
properly, and the test still fails, replace the Hybrid Line circuit pack.  
NOTE:  
If the Hybrid Circuit and Conference Circuit Test fails for all ports on  
a circuit pack, a -5 volt power problem is indicated.  
PASS  
Hybrid Circuit and Conference Circuit Test passed. The hybrid circuitry is  
transmitting properly.  
1. If complaints still exist, investigate by using other port tests, and by  
examining the station, wiring, and connections.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-695  
Table 3-292. TEST #57 Hybrid Circuit and Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Hybrid Line Local Digital Loop Around Test (#58)  
This test checks the control channel between the SPE and the port’s digital  
circuitry. The SPE sends transparent data to the on-board microprocessor and  
compares the data echoed back. This test is repeated three times.  
Table 3-293. TEST #58 Hybrid Line Local Digital Loop Around Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension number of the port. Use the status station  
command to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-696  
Table 3-293. TEST #58 Hybrid Line Local Digital Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension number of the port. Use the status station command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. You must wait  
until the port is idle before retesting. Attendants are always in use  
(off-hook) if the handset is plugged in and the port is not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
1,2,3  
ABORT  
FAIL  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The control channel between the processor and the port is not transmitting  
properly. This port is not operable.  
1. Retry the test.  
2. If the failure still occurs, issue the busyout and the release busy  
commands, and then retest.  
3. If the failure is occurring on more than one port on the board, suspect  
the board.  
4. If the failure is occurring on several boards in the same carrier,  
escalate the problem.  
5. If the failure still occurs and appears to be isolated to one port, check  
all wiring to the set and all set connections.  
6. Replace the circuit pack as a last resort.  
PASS  
Hybrid Line Local Digital Loop Around Test passed. The control channel is  
transmitting properly.  
1. If complaints still exist, investigate by using other circuit pack tests,  
and by examining the station, wiring, and connections.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-697  
Table 3-293. TEST #58 Hybrid Line Local Digital Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Hybrid Line Remote Digital Loop Around Test  
(#59)  
This test checks the digital control pair from the port circuit to the terminal. The  
on-board microprocessor sends a message to the terminal and checks for a  
proper return message. This test is repeated three times, with two out of the three  
attempts passing being sufficient for this test to pass. This testl runs if the station  
is in-service or out-of-service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-698  
Table 3-294. TEST #59 Hybrid Line Remote Digital Loop Around Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
1
A request for a remote station audit aborted even though all internal  
resources were correctly allocated.  
1. Look in the error log for error type 18 (port busied out) for this port. If  
this error type is present, release the port via the release port  
PCSSpp command or the release station extension command, and  
then run the test again.  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals for a maximum of 5 times.  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension number of the port. Use the status station  
command to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
2000  
1,2,3  
ABORT  
FAIL  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
No response was received within the allowable time period on one of the  
transmissions to the terminal. This indicates that something is wrong with  
the data link to the voice terminal. This could be a sleeping set problem or  
it may be due to wiring or an unplugged or defective set.  
1. Check for errors in the error log, for example, error 1537.  
2. Remotely issue the busyout and release busy commands, and run  
the short test sequence on the port to check for other errors  
associated with the port or terminal.  
3. Check the wiring to the set if it appears that the terminal is not  
responding to any tests; otherwise, replace the terminal and rerun the  
test.  
4. If the test still fails, replace the circuit pack and reconnect the original  
terminal.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-699  
Table 3-294. TEST #59 Hybrid Line Remote Digital Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
Hybrid Line Remote Digital Loop Around Test passed. The hybrid circuit  
pack is sending and receiving proper messages to and from the voice  
terminal.  
1. If problems still exist, investigate using other circuit pack tests and by  
examining the station, wiring, and connections.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Hybrid Line Lamp Updates Test (#60)  
For this test, the software lights the lamps on the terminal based on the status  
record contained in the processor. The lamp updates run only if the station is  
in-service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-700  
Table 3-295. TEST #60 Hybrid Line Lamp Updates Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
ABORT  
A request for a remote station lamp update aborted even though all  
internal resources were correctly allocated.  
1. Look in the error log for error type 18 (port busied out) for this port. If  
this error type is present, release the port via the release port  
PCSSpp command or the release station extension command, and  
then run the test again.  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals for a maximum of 5 times.  
Internal system error  
2
3
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The station is in a ready for service or an out of service state. This may be  
due to wiring or an unplugged or defective set.  
1. Make sure terminal is connected and the wiring is correct.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension number of the port. Use the status station  
command to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Hybrid Line Lamp Updates completed successfully.  
PASS  
1. If complaints still exist, investigate by using other circuit pack tests,  
and by examining the station, wiring, and connections.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-701  
Table 3-295. TEST #60 Hybrid Line Lamp Updates Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Hybrid Line Audits Test (#61)  
This is a series of three tests that are classified as audits. These audits abort if  
attempted on an out-of-service station. The tests are as follows:  
■
Switchhook Audit - This is an update of the SPE records according to the  
circuit packs’ records.  
■
Bad Scan Inquiry - A message is sent uplink that contains a count that is  
generated due to certain events relating to the data link conditions. This is  
an indication of data transmission problems between the Hybrid circuit  
pack and the voice terminal.  
■
EPF Inquiry - The status of the Electronic Power Feed is sent uplink.  
Possible conditions are: EPF-on-ok, EPF-off, EPF-no-load, and  
EPF-on-overcurrent.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-702  
Table 3-296. TEST #61 Hybrid Line Audits Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal System Error  
1
2
The test was aborted due to an internal system error during the switchhook  
audit.  
ABORT  
Internal System Error occurred during bad scan inquiry audit.  
1. Make sure that the station is not in an out of service state.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
This port may have been busied out by system technician.  
3
ABORT  
1. Look in the Error Log for Error Type 18 (port busied out) for this port. If  
this error type is present, the release the port via the release station  
<extension> command and run the test again.  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp to determine the  
station extension number of the port. Use the status station command to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. You must  
wait until the port is idle before retesting. Attendants are always in use  
(off-hook), if the handset is plugged in and the port is not busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension number of the port. Use the status station command to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. You must  
wait until the port is idle before retesting. Attendants are always in use  
(off-hook), if the handset is plugged in and the port is not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
ABORT  
FAIL  
Response to the test request was not received within the allowable time  
period.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-703  
Table 3-296. TEST #61 Hybrid Line Audits Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Hybrid Line Audits Test passed.  
PASS  
1. Although this test always return a PASS result, it may enter Error Types  
257 or 513 into the Error Log. To determine if there are any problems  
that don’t show up in the test result, look for these error types in the  
Error Log.  
2. If these errors appear in the Error Log, or if user complaints still exist,  
investigate by using other circuit pack tests, and by examining the  
station, wiring, and connections.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Hybrid Line Ringer Update Test (#62)  
In this update, a "ringer on" or a "ringer off" message is sent to the firmware to  
start and stop the ringer on the set.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
HYB-LINE (Hybrid Line)  
3-704  
Table 3-297. TEST #62 Hybrid Line Ringer Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
3
ABORT  
This port may have been busied out by system technician.  
1. Look in the Error Log for Error Type 18 (port busied out) for this port. If  
this Error Type is present, the release the port via the release station  
<extension> command and run the test again.  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension number of the port. Use the status station  
command to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook), if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Hybrid Station Ringer Update passed  
PASS  
1. If complaints still exist, investigate using other circuit pack tests on this  
circuit pack, and by examining the terminal, wiring, and connections.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
INADS (INADS Link)  
3
3-705  
INADS (INADS Link)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
INADS  
none  
test inads-link  
INADS Link  
The INADS Link MO represents the software and communications link required  
by the switch to make a call to the Initialization and Administration System  
(INADS). The purpose of the INADS Link MO is to check the communications link  
between the DEFINITY Generic 1 and INADS and verify that the alarm notification  
process works correctly. An INADS technician can test the process remotely to  
verify that alarms are reported to INADS, or a system technician may want to test  
the connection while on-site at installation time or during subsequent service  
calls.  
Although the INADS Link MO is never alarmed, the errors are logged. The errors  
are only logged as a result of the test inads-link command being issued.  
Error Log Entries and Test to Clear Values  
The Hardware Error Log entries are described as part of the INADS Link Test  
description.  
Short and Long Test Sequences  
The test inads-link command is different from other test commands. This  
command does not have a long or short option, and the test on the INADS Link  
does not have an associated test number. When the test inads-link command is  
issued, the user immediately sees either the Command successfully  
completedor Command failedmessage.  
INADS Link Test (no test number)  
The INADS Link Test attempts to place a call to INADS (in the background) to  
verify the communications link to INADS. When the test inads-link command is  
issued, the user immediately sees either the Command successfully  
completedor Command failedmessage. When a previously run command is  
entered, the user immediately sees either Command successfully  
completedor Command failed. The Command failedmessage appears  
when a previously run test inads-link command is in progress or the system has  
active alarms which must be reported to INADS. The Command successfully  
completedmeans the switch will start the attempt to call INADS in two minutes  
(the test still runs even if Alarm Origination is disabled). The two-minute delay  
allows a remote INADS technician time enough to hang up the call and thus free  
up the INADS line so that the switch can call INADS back. As error conditions are  
encountered, errors are logged against INADS. Error codes 1 through 9 can be  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
INADS (INADS Link)  
3
3-706  
logged if the test result was Command successfully completedand Error  
Codes 10 and 11 can be logged if the test result was Command failed. An  
error is also logged against INADS if the call to INADS finally succeeds. The  
INADS software (release 3.2 or later) recognizes this special "test inads" type of  
alarm and automatically opens and then closes a trouble ticket which indicates  
that the reason for the trouble ticket is a command is in progress or the system  
has active alarms which must be reported to INADS. The Command  
successfully completedmeans the switch will start the attempt to call  
INADS in two minutes (the test still runs even if Alarm Origination is disabled).  
The two-minute delay allows a remote INADS technician time enough to hang up  
the call and thus free up the INADS line so that the switch can call INADS back.  
As error conditions are encountered, errors are logged against INADS. Error  
codes 1 through 9 can be logged if the test result was Command successfully  
completedand Error Codes 10 and 11 can be logged if the test result was  
Command failed. An error is also logged against INADS if the call to INADS  
finally succeeds. The INADS software (release 3.2 or later) recognizes this  
special "test inads" type of alarm and automatically opens and then closes a  
trouble ticket which indicates that the reason for the trouble ticket is a test  
inads-link command. The trouble ticket alarm contains a TESTING INADS  
LINK description field.  
After entering the command, it may take as long a nine minutes for the switch to  
place the call and for INADS to respond. The Error Log should be examined (use  
the category inads) 10 minutes after successfully entering the command to  
determine if the call was successful.  
Use Table 3-298 to interpret the Error Log entries.  
Table 3-298. INADS Link Error Log Entries Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
2
0
0
The call was successfully placed to INADS. No trouble found.  
Informative error indicating that alarm origination was disabled at the time  
of the test. The test runs even if alarm origination is disabled.  
1. If Alarm Origination is desired, then enable this feature with the  
Maintenance-Related System Parameters Form.  
2. Repeat the test.  
3
0
The INADS connection is currently in use.  
1. Wait 10 minutes and retry this command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
INADS (INADS Link)  
3
3-707  
Table 3-298. INADS Link Error Log Entries Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
INADS did not answer the alarm origination call.  
1. Verify INADS is up and running.  
4
0
2. Verify the INADS phone number and switch product ID are correct via  
the Maintenance-Related System Parameters Form.  
3. Enable alarm origination via the Maintenance-Related System  
Parameters Form and test the PR-MAINT (Maintenance/Tape  
Processor) by issuing the test processor a|b command. If PR-MAINT  
Tests #102 and #103 do not pass, then refer to ‘‘PR-MAINT  
(Maintenance Processor)’’ Maintenance documentation.  
4. Retry the command.  
5
6
0
0
No INADS phone number administered.  
1. Administer the INADS phone number via the Maintenance-Related  
System Parameters Form.  
2. Retry the command.  
INADS did not send the acknowledgment message to the "test inads  
alarm" message.  
1. Verify the INADS phone number and switch product id are correct via  
the Maintenance-Related System Parameters Form.  
2. Verify INADS is up and running.  
3. Retry the command.  
7
0
INADS sent a negative acknowledgment to the "test inads alarm"  
message.  
8
9
0
0
Internal system error; system received an invalid return code.  
Internal system error  
1. Try the command again at 1-minute intervals up to 5 times.  
There is already a test inads-link command in progress.  
1. Wait 10 minutes for the present command to finish.  
10  
0
2. Review the results of the present command by viewing the Error Log  
and selecting the category "inads-link."  
11  
0
The switch is trying to report alarms to INADS. The test cannot be run at  
this time.  
1. Wait 10 minutes and retry the command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
IO-PROCR (I/O Processor)  
3-708  
IO-PROCR (I/O Processor)  
MO Name (in  
Alarm Log)  
Alarm Level  
Initial Command to Run  
Full Name of MO  
IOP  
MAJOR  
reset io-processor  
I/O PROCR  
The I/O Processor includes the I/O Processor CPU, memory, a real-time  
operating system, and a driver. Together they support the Data Channel data  
scanners and Packet Interface functions. The I/O Processor resides on the single  
TN798 Processor circuit pack in the system.  
Error Log Entries and Test to Clear Values  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
2
0
0
MAJOR  
ON  
ON  
ON  
ON  
reset io-processor  
2
2
2
1 (a)  
Any  
Any  
Any  
None  
None  
None  
MAJOR  
MAJOR  
MAJOR  
reset io-processor  
reset io-processor  
reset io-processor  
257 (b)  
513 (c)  
1. Indicates that an alarm was raised but an associated error was not entered into the hardware error  
log due to a momentary overload condition caused by a burst of hardware or software error reports.  
Run the long test sequence. Refer to the appropriate test descriptions for any failures and follow  
the recommended procedures.  
2. An I/O Processor can only be reset if it has been taken out of service by background maintenance  
software.  
Notes:  
a. Error 1 occurs when background maintenance software has reset the I/O  
Processor as a fault recovery action. It is used to track the number of IOP  
resets, independent of whether or not the Reset test passed. Once three  
of these errors have occurred in the last 15 minutes, maintenance places  
the I/O Processor in the out-of-service state, and a MAJOR on-board  
alarm is raised on the I/O Processor. When the I/O Processor has been  
taken out-of-service, the Packet Interface and Data Channels are also  
taken out-of-service.  
1. Check to see if error codes 257 or 513 are present in the hardware  
error log. If one or more of those error codes are present, refer to  
the information associated with those errors for the appropriate  
repair procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
IO-PROCR (I/O Processor)  
3-709  
2. If no other I/O Processor errors appear in the error log, and if the I/O  
Processor is not in a held reset state as indicated by the absence of  
a MAJOR alarm with a Service State of OUT, no action should be  
taken.  
b. Error 257 indicates that an in-line error (IOP System Error) has been  
reported by I/O Processor firmware. When this error counter is active, the  
error count is decremented by 1 every 15 minutes, but only if the I/O  
Processor has not been reset three times by background maintenance. If  
the threshold is exceeded, a MAJOR alarm is raised. Execute a demand  
reset by entering reset io-processor and refer to the repair procedures  
for Test # 704.  
c. Error 513 indicates that an in-line error (IOP Handshake Failure) has been  
reported by I/O Processor driver when the driver is unable to check the  
sanity of the firmware. When this error counter is active, the error count is  
decremented by 1 every 15 minutes, but only if the I/O Processor has not  
been reset three times by background maintenance. If the threshold is  
exceeded, a MAJOR alarm is raised. Execute a demand reset by entering  
reset io-processor and refer to the repair procedures for Test # 704.  
System Technician-Demanded Tests:  
Descriptions and Error Codes  
The I/O Processor support both the Data Channel data scanners and Packet  
Interface functions. Running the I/O Processor Reset Test is as though both the  
Data Channel Reset Test and Packet Interface Reset Test are executed along  
with a reset of the I/O Processor CPU, memory, and real time operating system.  
Reset  
Sequence  
1
Order of Investigation  
D/ND  
I/O Processor Demand Reset (#704)  
X
D
1. D = Destructive; ND = Nondestructive  
Demand Reset Test (#704)  
This test is destructive.  
This action initializes the I/O Processor, and the firmware runs a comprehensive  
set of diagnostic tests. This action will abort if the I/O Processor is in the  
in-service state. The I/O Processor is put in the out-of-service state automatically  
if it has been reset three times by background maintenance within the last 15  
minute, independent of the reset action.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
IO-PROCR (I/O Processor)  
3-710  
Table 3-299. TEST #703 Demand Reset Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1362  
ABORT  
The test is not allowed to run because the I/O Processor is in-service. Running  
this test is not allowed because it is destructive.  
1. Use the display alarms command to determine the service state of the I/O  
Processor. If the state is OUT, try the reset command again.  
2000  
Any  
ABORT  
FAIL  
Response to the test request was not received within the allowable time period.  
1. Retry the command at 1-minute intervals, a maximum of 3 times.  
The I/O Processor diagnostic tests failed.  
1. Retry the command.  
2. If the reset fails, replace the Processor circuit pack.  
The I/O Processor diagnostic tests passed.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-PLK (ISDN-PRI Signaling Link Port)  
3-711  
ISDN-PLK (ISDN-PRI Signaling Link  
Port)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test port PCSSpp l  
Full Name of MO  
2
ISDN-PLK  
MINOR  
WARNING  
ISDN-PRI Signaling Link Port  
ISDN-PRI Signaling Link Port  
ISDN-PLK  
test port PCSSpp sh  
1. Where ’pp’ is ’24’ for 24-channel interfaces, and ’16’ for 32-channel interfaces.  
2. For additional repair information, see also PKT-CTRL (Packet Control), DS1-BD (DS1 Interface  
Circuit Pack) or UDS1-BD (Universal DS1 Interface Circuit Pack).  
The ISDN-PRI Signaling Link Port is the port on a TN464C or later UDS1 Interface  
circuit pack that carries D-channel messages to the processor. The ISDN-PRI  
interface uses out-of-band signaling as opposed to robbed-bit, in-band  
signaling. This port can be used as an interface to the TDM bus or to the Packet  
bus.  
The B-channels associated with a ISDN-PRI D-channel can use ports on the  
same circuit pack or ports on other TN464C or later or TN767 DS1 Interface  
circuit packs (The TN722 cannot be used for this application.)  
In a 32-channel system (see Figure 3-21), the DS1 ISDN Trunk or PRI endpoint  
port (B-channels) may use any of the ports 1-15 or 17-31, but the ISDN-PRI  
Signaling Link Port must be the 16th port on the TN464C (or higher) circuit pack.  
In certain configurations (NFAS), the 16th port may be used as a B-channel.  
Refer to the ‘‘ISDN-SGR (ISDN-PRI Signaling Group)’’ Maintenance  
documentation for further details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-PLK (ISDN-PRI Signaling Link Port)  
3-712  
Slot 1  
(Port 0)  
Framing  
Voice or data  
(Port 1)  
ISDN -TRK  
(B-Channel)  
Processor  
(TN798)  
UDS1  
Interface  
circuit pack  
TN464  
T
D
M
(Port 15)  
ISDN -TRK  
(B-Channel)  
2
Pimary  
signaling link  
ISDN -PLK  
(D-Channel)  
b
u
s
(Port 16)  
Voice or data  
(Port 17)  
ISDN -TRK  
(B-Channel)  
Voice or data  
(Port 31)  
ISDN -TRK  
(B-Channel)  
cydfisd2 RPY 061297  
Figure Notes  
1. B- and D-channel messages are  
routed over the TDM Bus. For  
additional reliability, a duplex  
D-channel can be administered for  
a signaling group and located on a  
different TN464C (or higher) circuit  
pack.  
2. TN464C or higher  
Figure 3-21. ISDN-PRI Signaling Link Port Interactions (32-Channel - TN464)  
The TN767 DS1 interface is used for 24 channel 1.544 Mbps systems. The  
TN464C or later can be used for either 24 or 32 channel systems. The 32-channel  
(31 DS0 channels + 1 framing channel on a 2.048 Mbps link) are only supported  
on TN464 series circuit packs. A description of these circuit packs appears in  
DS1-BD or UDS1-BD maintenance documentation.  
In a 24-channel system, the DS1 ISDN Trunk or PRI endpoint port (B-channels)  
may use any of the first 23 ports. The ISDN-PRI Signaling Link Port must be the  
24th port (See Figure 3-22). In certain configurations (NFAS), the 24th port may  
be used as a B-channel. Refer to the ISDN-PRI Signaling Group (ISDN-SGR)  
Maintenance documentation for further details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-PLK (ISDN-PRI Signaling Link Port)  
3-713  
Slot 1  
Processor  
(TN798)  
DS1  
Interface  
circuit pack  
TN767  
Voice or data ISDN -TRK  
(B-Channel)  
(Port 1)  
T
D
M
2
Voice or data  
(Port 23)  
ISDN -TRK  
(B-Channel)  
b
u
s
Pimary  
signaling link  
ISDN -PLK  
(D-Channel)  
(Port 24)  
cydfisd3 RPY 061297  
Figure Notes  
1. B- and D-channel messages are  
routed over the TDM Bus. For  
additional reliability, a duplex  
D-channel can be administered for  
a signaling group and located on a  
different TN464C (or higher) circuit  
pack.  
2. TN767B (or higher) or TN464C (or  
higher)  
Figure 3-22. ISDN-PRI Signaling Link Port Interactions (24 Channel -  
TN767/464C)  
ISDN-PLK handles maintenance and recovery for the D-channel port on the DS1  
carrying the signaling link. A problem with the ISDN-PRI Signaling Link Port  
(D-channel) has an effect on all of the associated DS1 ISDN Trunks or PRI  
endpoint ports (B-channels) since no call control information can be conveyed to  
the far-end switch or Terminal Adapter without it. Stable calls may remain  
operational, but no new calls can be made.  
If there are problems with the ISDN-PLK, also investigate the TN464 UDS1  
interface circuit pack (UDS1-BD).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-PLK (ISDN-PRI Signaling Link Port)  
3-714  
Error Log Entries and Test to Clear Values  
Table 3-300. ISDN-PRI Signaling Link Port Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1
2
0
0
Any  
Any  
Any  
OFF  
ON  
test port PCSSpp  
2
18(a)  
0
busyout port PCSSpp*  
None  
WARNING  
WARNING  
WARNING  
release port PCSSpp  
2
130 (b)  
1537 (c)  
1793 (d)  
3585 (e)  
3841 (f)  
3842 (g)  
test port PCSSpp  
46210  
OFF  
2
test board PCSSpp 1  
46222  
46211  
46223  
MINOR  
ON  
1. Run the short test sequence first. If all tests pass, run the long test sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
2. pp is 24-channel interfaces and 16 for 32-channel interfaces.  
Notes:  
a. The D-channel is demand busied out. No calls can be made over this  
D-channel.  
b. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
c. Link error. This error occurs when the port receives an invalid frame over  
the D-channel. This error normally indicates an off-board problem usually  
related to transmission errors on the DS1 facility. Execute the list  
measurements ds1-log command for the UDS1 TN464 circuit pack on  
which the D-channel resides. If the UDS1 is reporting some errors, then  
the DS1 facility has experienced transmission problems which could have  
caused the ISDN-PLK to report a Link Error. If the UDS1 is not reporting  
errors, execute the long test sequence for the D-channel (ISDN-SGR).  
Investigate any errors, if there are none execute a long test sequence for  
the UDS1 circuit pack (UDS1-BD) and investigate any errors.  
If no errors are reported, the Link Error is probably not affecting service.  
d. The UDS1 Interface circuit pack is out-of-service. Look for and resolve  
UDS1-BD errors in the Hardware Error Log.  
e. Transmit FIFO Overflow error. This error indicates that the circuit pack is  
having problems transmitting signaling information over the D-channel.  
This condition probably indicates a hardware problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-PLK (ISDN-PRI Signaling Link Port)  
3-715  
The actual alarming level depends on the options chosen via the set  
options command on the G3-MT terminal. ISDN-PRI Signaling Link Port  
alarms are treated as Station alarms, and their default alarming option is to  
downgrade all alarms to Warning. The value shown in the preceding table  
indicates the normal, unfiltered case (option "y" on the Set Options form).  
f. Bad DLCI error. This error occurs when a LAPD frame is received across  
the DS1 facility which contains a DLCI which does not have a valid entry in  
the on-board translation memory. This error normally indicates an  
off-board problem usually related to a broken endpoint or a state  
mismatch between a remote endpoint and the local call processing  
software. Maintenance will not start any testing or generate any alarms in  
response to this error.  
g. Receive FIFO Overflow error. This error occurs when the circuit pack  
detects an overflow of its receive buffers. If it occurs frequently, it may  
indicate a LAPD parameter mismatch between the two endpoints.  
Maintenance does not start any testing or generate any alarms in  
response to this error.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system.  
NOTE:  
The command line entry to test the ISDN-PLK MO is: test port PCSSpp (sh  
or l), where ‘pp’ is ‘24’ for 24-channel interfaces, and ‘16’ for 32-channel  
interfaces.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Signaling Link Board Check (#643)  
X
X
ND  
1. D = Destructive; ND = Nondestructive  
Signaling Link Board Check (#643)  
This test checks the state of the UDS1 Interface circuit pack (TN464C or later)  
transporting the ISDN-PRI Signaling Link.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-PLK (ISDN-PRI Signaling Link Port)  
3-716  
Table 3-301. TEST #643 Signaling Link Board Check  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1700  
Rollabout video abort. The PRI terminal adapter associated with this  
D-channel port is detached from the circuit pack. This is a normal abort  
when the rollabout video feature is enabled. To complete test on this port,  
either:  
1. Re-attach the disconnected PRI terminal adapter and retry test  
command, or  
2. Disable the rollabout video feature on this circuit pack by entering  
change ds1 PCCSS and set the field Alarm when PRI  
Endpoint Detached?to y.  
8
FAIL  
The UDS1 circuit pack (TN464C or later) is not in-service.  
1. Check the Hardware Error Log for entries logged against UDS1-BD and  
consult the UDS1-BD (UDS1 Interface Circuit Pack) Maintenance  
documentation for repair procedures.  
PASS  
The UDS1 Interface circuit pack transporting the ISDN-PRI Signaling Link  
Port is in-service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-717  
ISDN-SGR (ISDN-PRI Signaling  
Group)  
MO Name (in  
1
Alarm Log)  
ISDN-SGR  
ISDN-SGR  
Alarm Level  
MINOR  
Initial Command to Run  
test sig-group <group>  
test sig-group <group>  
Full Name of MO  
ISDN-PRI Signaling Group  
ISDN-PRI Signaling Group  
WARNING  
1. Where <group> is a number 1-8 and the test sequence can be either s (short) or l (long).  
An ISDN-PRI Signaling Group is a collection of DS1/UDS1 ISDN Trunks or PRI  
endpoint ports (B-channels) for which a given ISDN-PRI Signaling Link Port  
(D-channel) carries signaling information. ISDN-PRI requires the use of one of the  
following DS1 interface circuit packs:  
TN767B or later  
TN464C or later  
24-channel with ISDN-PRI D-channel over PI-BD  
24- or 32-channel with ISDN-PRI D-channel over PI-BD  
See DS1-BD and UDS1-BD Maintenance documentation for a description of  
these circuit packs. See DS1/CEPT1/ISDN-PRI Reference, 555-025-101, for more  
information on ISDN.  
For 24-channel interfaces, the first 23 ports on the circuit pack are used as  
B-channels. The 24th port may be used as a B-channel or as a D-channel  
depending on the type of Signaling Group used (see Figure 3-23).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-718  
Slot 1  
Processor  
(TN798)  
DS1  
Interface  
circuit pack  
TN767  
Voice or data ISDN -TRK  
(B-Channel)  
(Port 1)  
T
D
M
2
Voice or data  
(Port 23)  
ISDN -TRK  
(B-Channel)  
b
u
s
Pimary  
signaling link  
ISDN -PLK  
(D-Channel)  
(Port 24)  
cydfisd3 RPY 061297  
Figure Notes  
1. B- and D-channel messages are  
routed over the TDM Bus. For  
additional reliability, a duplex  
D-channel can be administered for  
a signaling group and located on a  
different TN464C (or higher) circuit  
pack.  
2. TN767B (or higher) or TN464C (or  
higher)  
Figure 3-23. ISDN-PRI Signaling Link Port Interactions (24 Channel -  
TN767/464C)  
For 32-channel interfaces, ports 1-15 and 17-31 on the circuit pack are used as  
B-channels. The 16th port may be used as a B-channel or as a D-channel  
depending on the type of Signaling Group used (see Figure 3-24).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-719  
Slot 1  
(Port 0)  
Framing  
Voice or data  
(Port 1)  
ISDN -TRK  
(B-Channel)  
Processor  
(TN798)  
UDS1  
Interface  
circuit pack  
TN464  
T
D
M
(Port 15)  
ISDN -TRK  
(B-Channel)  
2
Pimary  
signaling link  
ISDN -PLK  
(D-Channel)  
b
u
s
(Port 16)  
Voice or data  
(Port 17)  
ISDN -TRK  
(B-Channel)  
Voice or data  
(Port 31)  
ISDN -TRK  
(B-Channel)  
cydfisd2 RPY 061297  
Figure Notes  
1. B- and D-channel messages are  
routed over the TDM Bus. For  
additional reliability, a duplex  
D-channel can be administered for  
a signaling group and located on a  
different TN464C (or higher) circuit  
pack.  
2. TN464C or higher  
Figure 3-24. ISDN-PRI Signaling Link Port Interactions (32-Channel - TN464)  
There are two types of Signaling Groups:  
■
Facility Associated Signaling (FAS) (supported by all country protocols)  
■
Non-Facility Associated Signaling (NFAS) (supported by country protocol  
1 only)  
In an FAS Signaling Group, the 24th port of the DS1 Interface circuit pack (for 24  
channel interfaces) or the 16th port of the DS1 Interface circuit pack (for 32  
channel interfaces) is always the D-channel that carries signaling information for  
the other ports (B-channels) on the circuit pack. If a Packet Control circuit pack is  
used then only the TN464C or later circuit pack may be used.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-720  
In an NFAS Signaling Group, the 24th port of a DS1 Interface circuit pack (for 24  
channel interfaces) or the 16th port of a DS1 Interface circuit pack (for 32  
channel interfaces) is administered as a D-channel. The D-channel carries  
signaling information for the other ports (B-channels) on that circuit pack. That  
D-channel can also carry signaling information for any of the ports on other DS1  
Interface circuit packs in the NFAS Signaling Group. As a result, the 24th port on  
other 24-channel DS1 Interface circuit packs and the 16th port on other  
32-channel DS1 Interface circuit packs can be used as B-channels. A D-channel  
in an NFAS Group can signal for B-channels on a total of 20 DS1 Interface circuit  
packs. This configuration is known as NFAS Simplex.  
In addition to NFAS Simplex, there is another type of NFAS Group called NFAS  
Duplex. This provides the user with more reliability, which is desirable because  
NFAS permits the D-channel to signal for so many B-channels. NFAS Duplex  
allows the administration of a backup D-channel, which remains in a Standby  
state until the Active D-channel goes down. If the Active D-channel does go  
down, the backup D-channel takes over and provides signaling for all the  
B-channels in the signaling group.  
The ISDN-PRI Signaling Group itself depends on three other entities: the DS1  
Interface circuit pack on which the D-channel(s) resides, the ISDN-PRI Signaling  
Link Port(s), and the Processor Interface Link that provides connectivity to the  
processor. If there are any problems with the ISDN-PRI Signaling Group, also  
investigate the ISDN-PRI Signaling Link Port(s), the DS1 Interface circuit pack(s).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-721  
Error Log Entries and Test to Clear Values  
Table 3-302. ISDN-PRI Signaling Group Error Log Entries  
Error  
Codes  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
test sig-group  
<group>  
1 (a)  
Any  
Any  
none  
none  
257 (b)  
test sig-group  
<group>  
513 (c)  
769  
Any  
Any  
none  
test sig-group  
<group>  
Primary Signaling  
Link Hardware Check  
(#636)  
test sig-group  
<group>  
1025  
Any  
Secondary Signaling  
Link Hardware Check  
(#639)  
test sig-group  
<group>  
1793 (d)  
2049 (e)  
2305 (f)  
3585 (g)  
Any  
Any  
Any  
Layer 2 Status (Test  
#647)  
WARNING  
WARNING  
MINOR  
OFF  
OFF  
OFF  
test sig-group  
<group>  
Layer 2 Status (Test  
#647)  
test sig-group  
<group>  
Remote Layer 3  
Query (Test #637)  
test sig-group  
<group>  
port  
none  
none  
number  
3840-  
port  
none  
3928 (h)  
number  
1. Run the Short or Long Test Sequence. Refer to the appropriate test description and follow the  
recommended procedures.  
Notes:  
a. This switch sent a message to the far-end switch or terminal adapter, and  
the far-end did not respond in the allotted time. Possible causes include  
link failure and congestion or outage at the far-end. The Aux Data field  
contains Layer 3 protocol information used by internal counters.  
If no other symptoms are not present, no action is required. If Layer 3  
communication is down, there should be indications in the form of alarms  
and errors for link components. Check out other errors against ISDN-SGR,  
ISDN-TRK, and other hardware components on the link.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-722  
There is no test to clear these errors. The error counter is decremented by  
1 every 15 minutes.  
b. This error indicates that the primary signaling channel connection has  
been lost for more than 90 seconds. If a secondary signaling channel  
does not exist or is not in-service, the associated B-channels will be  
placed in the ISDN Maintenance/Far-End state. The B-channels will not be  
usable for outgoing calls, although incoming calls will still be accepted.  
The switch will automatically attempt to recover the signaling link. Pay  
particular attention to the results of Test #636 (Primary Signaling Link  
Hardware Check) in the test sequence. When the link does recover, the  
B-channels will be negotiated back to the In-Service state and their alarms  
will be retired.  
When this error occurs, the state of the Signaling Group is changed to  
out-of-service (verify using the status sig-group command).  
c. This error indicates that the secondary signaling channel connection has  
been lost for more than 90 seconds. If the primary signaling channel is not  
in-service, B-channels will be placed in the ISDN Maintenance/Far-End  
state. The B-channels will not be usable for outgoing calls, although  
incoming calls will still be accepted. The switch will automatically attempt  
to recover the signaling link. Pay particular attention to the results of Test  
#639 (Secondary Signaling Link Hardware Check) in the test sequence.  
When the link does recover, the B-channels will be negotiated back to the  
In-Service state and their alarms will be retired.  
When this error occurs, the state of the Signaling Group is changed to  
out-of-service (verify using the status sig-group command).  
d. This error indicates a failure of the Layer 2 Status Query Test for the  
primary signaling channel  
e. This error indicates a failure of the Layer 2 Status Query Test for the  
secondary signaling channel.  
f. A specific message was sent to the far-end switch, and it did not respond  
within the allotted time. Investigate elements of the ISDN PRI D-channel(s)  
(ISDN-LNK, ISDN-PLK, ISDN-SGRP, PKT-INT, PKT-CTRL) for both this  
switch and the Far-end switch. If Test #637 fails twice in a row, the  
B-channels will be alarmed and made unavailable for outgoing calls  
(although incoming calls will still be accepted). When Test #637 succeeds  
and the Far-end switch starts responding properly, the DS1 ISDN Trunk  
(B-channels) will be placed back into normal operation and their alarms  
will be retired.  
g. A SERV or SERV ACK ISDN D-channel message has been received by a  
non-US-type interface (country option other than 1on the DS1  
administration form). However, these messages are used only for duplex  
NFAS signaling which is supported only by country protocol 1.  
Thus, there may be a mismatch in administration between the local and  
far-end switches. Consult with the customer’s network provider to  
determine whether the D-channel is set up correctly on the far-end switch.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-723  
h. These error codes are used to report certain error messages received by  
the ISDN-PRI Signaling Group for one of its associated B-channels. The  
aux data field shows for which B-channel (port number) the message was  
received.  
The error code generated equals 3840+x, where x is a Cause Value  
defined by the ISDN PRI Specification. Note that there is no Test to Clear  
Value for these error types; selected ISDN cause values are placed in the  
log when they are received, but no direct action or alarming is performed  
solely in response to receiving them. They provide added data that may  
prove useful when tracking down obscure networking and routing  
problems. Table 3-303 provides more information:  
Table 3-303. Descriptions of Error Codes 3840-3928  
Error  
Code  
Description  
Recommendation  
3842  
A request has been made  
to use a transit network or  
common carrier that cannot  
be accessed.  
1. From the circuit pack and port number (in the Aux  
Data field), determine the trunk group against which  
the error was reported.  
2. Check all routing patterns containing this trunk group  
for validity of interexchange carriers requested (IXC  
field).  
3846  
The far-end switch has  
indicated that the  
B-channel (trunk) is not  
acceptable for use in the  
call for which it was  
requested.  
This could indicate an administration problem (for  
example, the local switch and the far-end switch have  
different B-channels administered), or could reflect the  
occurrence of a normal race condition (for example, the  
local switch has requested use of a B-channel which the  
far-end switch had just reserved for use on another call).  
1. From the circuit pack and port number (in the Aux  
Datafield), determine the trunk group against which  
the error was reported.  
2. Issue the status trunk command for the indicated  
trunk.  
3. Refer to the ‘‘DS1 ISDN Trunk Service States’’ and  
‘‘ISDN-PRI Trunk Service States’’ sections of  
ISDN-TRK for recovery suggestions.  
3858  
The switch sent an ISDN  
message to the far-end  
switch or terminal adapter  
which did not respond in  
the allotted time.  
Possible causes include link failure and congestion or  
outage at the far-end.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-724  
Table 3-303. Descriptions of Error Codes 3840-3928 — Continued  
Error  
Code  
Description  
Recommendation  
3878  
The far-end switch has  
indicated that the network  
is not functioning correctly  
and that the condition may  
last a relatively long period  
of time (for example,  
immediately re-attempting  
the call may not be  
successful).  
1. From the circuit pack and port number (in the Aux  
Data field, determine the trunk group against which  
the error was reported.  
2. Consult with the network provider to determine the  
nature and expected duration of the out of service  
condition.  
3. Consider modifying all routing patterns containing this  
trunk group, to route calls around the network which is  
out of service.  
3890  
A request to use a network  
service (e.g., SDN) has  
been denied.  
This could be a local administration problem only, or a  
mismatch between the local administration and that of the  
network provider.  
Administration somewhere  
on the network has  
indicated that the  
requested service has not  
been subscribed to or  
purchased for this trunk.  
1. From the circuit pack and port number (in the Aux  
Data field), determine the trunk group against which  
the error was reported.  
2. Display the trunk group form: If the trunk group is  
Call-by-Call (Service Type is ‘‘cbc’’), check all routing  
pattern forms containing this trunk group to see if the  
Service/Feature fields contain the correct network  
services purchased for this trunk. If the trunk group is  
not Call-by-Call, check that the Service Type field  
contains the single network service purchased for this  
trunk.  
3. If local administration appears correct, consult with  
the customer and/or the network provider to  
determine the services that the customer has  
subscribed to for this trunk group.  
3892  
3894  
Protocol detail; may offer a  
clue if customer is having  
ISDN calls denied with an  
unexpected intercept tone.  
If customer is complaining of unexpected intercept tones  
when accessing ISDN trunks or PRI endpoints and no  
other cause can be found, provide the next tier with this  
Error Log information.  
Protocol detail; may offer a  
clue if customer is having  
ISDN calls denied with an  
unexpected intercept tone.  
First, eliminate any transitory state mismatch problems by  
issuing the test port PCSSpp command for the trunk port  
shown in the aux data field. Test #256 (Service State  
Audit) is the important test in the sequence. If this passes  
satisfactorily, yet the customer continues to complain of  
unexpected intercept tones when accessing ISDN trunks  
or PRI endpoints and no other cause can be found,  
provide the next tier with this Error Log information.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-725  
Table 3-303. Descriptions of Error Codes 3840-3928 — Continued  
Error  
Code  
Description  
Recommendation  
3905  
Protocol detail; may offer a  
clue if customer is having  
ISDN calls denied with an  
unexpected intercept tone.  
If customer is complaining of unexpected intercept tones  
when accessing ISDN trunks or PRI endpoints and no  
other cause can be found, provide the next tier with this  
Error Log information.  
3906  
3909  
Protocol detail; may offer a  
clue if customer is having  
ISDN calls denied with an  
unexpected intercept tone.  
If customer is complaining of unexpected intercept tones  
when accessing ISDN trunks or PRI endpoints and no  
other cause can be found, provide the next tier with this  
Error Log information.  
A request to use a network  
service has been made,  
but the network has  
Follow the recommendations listed above for error type  
3890.  
rejected the request  
because the requested  
service is not implemented.  
3928  
A call was denied because  
of a basic incompatibility  
between the type of call  
and either the facilities  
selected by the routing  
pattern or the called user  
itself.  
This error might be helpful as a clue if the customer  
complains of receiving unexpected intercept tone after  
accessing ISDN trunks or PRI endpoints. Determine the  
trunk group from the circuit pack and port number (in the  
aux data field) and then check the BCC fields of the  
pertinent routing patterns. Also, investigate whether or not  
the calling and called endpoints are compatible (for  
example, some ISDN switches may not allow a voice  
station to call a data extension).  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the Primary Signaling Link Hardware Check, for  
example, you may also clear errors generated from other tests in the testing  
sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-726  
Table 3-304. System Technician-Demanded Tests: ISDN-SGR  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Primary Signaling Link Hardware Check  
(#636)  
X
X
ND  
Secondary Signaling Link Hardware Check  
(#639)  
X
X
ND  
Layer 2 Query Test (#647)  
X
X
X
X
ND  
ND  
Remote Layer 3 Query Test (#637)  
Continued on next page  
1. D = Destructive, ND = Non-destructive  
Primary Signaling Link Hardware Check (#636)  
The ISDN-PRI Signaling Link Port itself depends on the health of the DS1/UDS1  
Interface circuit pack on which it resides. This test will fail if there are problems  
with either the ISDN-PRI Primary D-channel port or the DS1/UDS1 circuit pack.  
See Figure 3-23 for DS1 connections, Figure 3-24 for UDS1 connections.  
If there are problems with the ISDN-PRI Signaling Link, also investigate the  
DS1/UDS1 circuit pack (DS1-BD/UDS1-BD).  
Table 3-305. TEST #636 Primary Signaling Link Hardware Check  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1700  
Rollabout video abort. The PRI terminal adapter associated with this  
D-channel port is detached from the circuit pack. This is a normal abort  
when the rollabout video feature is enabled. To complete test on this port,  
either:  
1. Re-attach the disconnected PRI terminal adapter and retry test  
command, or  
2. Disable the rollabout video feature on this circuit pack by entering  
change ds1 PCSS and set the field Alarm when PRI Endpoint  
Detached?to y.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-727  
Table 3-305. TEST #636 Primary Signaling Link Hardware Check — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
8
FAIL  
There is a problem with the DS1/UDS1 Circuit Pack, or the ISDN-PRI  
Signaling Channel (D-channel). No DS1 ISDN Trunk (B-channel) or  
wideband PRI Endpoint calls can be made until the problem is resolved.  
1. Consult the procedures for DS1/UDS1 Circuit Pack and the ISDN-PRI  
Signaling Channel (ISDN-LNK/ISDN-PLK).  
PASS  
The basic physical connectivity of the primary D-channel is intact and  
functional. Try this test repeatedly to ensure the link is up and to uncover  
any transitory problems.  
Remote Layer 3 Query (#637)  
This test will query the far-end switch or terminal adapter to determine if the  
signaling connection is functioning properly at Layer 3. It will select a B-channel  
in the in-service or maintenance service state and send an ISDN Layer 3  
SERVice message, which requires a response from the far end (similar to  
performing Test #256 on an ISDN trunk. The test will not be performed if there are  
no B-channels in an appropriate ISDN service state (as when none are  
administered or they are all out of service).  
NOTE:  
The service state can be displayed by using the status trunk <trunk  
group/trunk member> or status pri-endpoint command.  
As is the case with Test #256 for an ISDN trunk, a PASS only indicates that a  
message was composed and sent to the far-end switch or terminal adapter. The  
ISDN PRI Specification allows up to 2 minutes for a response. Check the Error  
Log for ISDN-SGR (ISDN-PRI Signaling Group) errors of type 2305 for evidence  
of a Remote Layer 3 Query failure.  
Tests #639 and #636 check the health of the D-channels and DS1/UDS1  
Interface Circuit Packs. As shown in the figures below, Test #637 goes one step  
further by checking the communication path from the processor over the TDM  
Bus, through the DS1/UDS1 Interface circuit pack, and on to the far-end switch or  
terminal adapter. A special ISDN message is sent to the far-end switch or  
terminal adapter, which must respond within a specified amount of time. This test  
is designed to ensure that the communication path between the switch and the  
far-end is up and operational, and that the two endpoints can properly exchange  
ISDN control messages.  
See Figure 3-23 for DS1 connections, Figure 3-24 for UDS1 connections.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-728  
Table 3-306. TEST #637 Remote Layer 3 Query  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1006  
This is a NORMAL ABORT. For country protocol 1 interfaces (including the  
USA), either there are no B-channels administered in this signaling group, or  
all B-channels in this signaling group are either out-of-service or are in a  
"pending" state (PINS or PMTC, indicating that a B-channel maintenance  
message for that B-channel has been sent and not yet acknowledged).  
1. Administer an ISDN Trunk or PRI Endpoint Port (B-channel) in this  
signaling group, or use the status trunk TRK-GRP/TRK or status  
pri-endpoint <extension> command to check the state of the ISDN  
Trunks or PRI Endpoint Ports associated with this signaling group. Refer  
to ISDN-TRK or PE-BCHL for further details regarding service state  
definitions and transitions. For systems not using country protocol 1  
interfaces, there are no B-channels administered in this signaling group.  
1019  
1113  
ABORT  
ABORT  
There is already a Remote Layer 3 Query in progress. This is a normal  
ABORT.  
1. Wait two minutes, then follow the procedures for when this test passes.  
The Signaling Link is down. Therefore no messages can be sent to the  
Far-end switch.  
1. Examine the results of Tests #636 and #639 and follow  
recommendations provided there.  
2. If either test passes, it may be because the signaling link was disabled  
by system technician. Verify this by using the display comm link  
command. Tests #636 and #639 pass if the signaling link is not enabled.  
2100  
2500  
2500  
ABORT  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Same as ABORT with no error code.  
1. Follow the recommendations for ABORT with no error code.  
Same as ABORT with no error code.  
1. Follow the recommendations for ABORT with no error code.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-729  
Table 3-306. TEST #637 Remote Layer 3 Query — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
PASS  
A message was composed and sent to the Far-end switch. The ISDN PRI  
specification allows up to two minutes for a reply.  
1. Check the Error Log for ISDN-SGR (ISDN-PRI Signaling Group) for  
errors of type 2305 for evidence of a Remote Layer 3 Query failure. If no  
new errors were logged since this test was run, then this switch and the  
Far-end switch processor can exchange call control messages.  
2. If there is still a problem with a particular DS1 ISDN Trunk or PRI  
Endpoint Port (B-channel), busyout the trunk or port and run the long  
test sequence, paying particular attention to the results of Test #258  
(ISDN Test Call).  
Secondary Signaling Link Hardware Check (#639)  
The ISDN-PRI Signaling Group D-Channel port depends on the health of the  
DS1/UDS1 Interface circuit pack on which it resides. This test will fail if there are  
problems with either the ISDN-PRI Primary D-channel port or the DS1/ UDS1  
circuit pack. If there are problems with the ISDN-PRI Secondary Signaling  
Channel port (ISDN-PLK), also investigate the DS1/UDS1 circuit pack.  
See Figure 3-23 for DS1 connections, Figure 3-24 for UDS1 connections.  
Table 3-307. TEST #639 Secondary Signaling Link Hardware Check  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1132  
The Secondary D-channel is not administered for this Signaling Group.  
This is a NORMAL ABORT. Only a Primary D-channel must be  
administered for a Signaling Group.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-730  
Table 3-307. TEST #639 Secondary Signaling Link Hardware Check — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
4
FAIL  
There is a problem with the Processor Interface Link. No DS1 ISDN Trunk  
(B-channel) or Wideband PRI Endpoint calls can be made until the  
problem is resolved.  
1. Display the Communication-Interface Links Form via the display  
communication-interface command to determine which link is down  
(find the one that matches the DS1 Interface circuit pack on which this  
ISDN-PRI Signaling Link Port resides) and then refer to the PKT-INT  
Maintenance documentation.  
8
FAIL  
There is a problem with the DS1/UDS1 Interface circuit pack or the  
ISDN-PRI Secondary Signaling channel (D-channel). No ISDN Trunk  
(B-channel) or Wideband PRI Endpoint calls can be made until the  
problem is resolved.  
1. Refer to the DS1/UDS1 circuit pack and the ISDN-PRI Signaling  
channel (ISDN-LNK/ISDN-PLK) Maintenance documentation.  
PASS  
The basic physical connectivity of the Signaling Group’s Secondary  
D-channel is intact and functional. Try this test repeatedly to ensure the link  
is up and to uncover any transitory problems.  
Layer 2 Status Test (#647)  
The Layer 2 Status Test checks the layer 2 status of the ISDN-PRI Signaling  
Channel (D-channel). This test will fail if there is a hardware failure or a facility  
problem, or if the primary and secondary ISDN-PRI D-channels are not  
administered correctly.  
The Primary and Secondary Signaling Link Hardware tests (test 636 and 639)  
and the Remote Layer 3 Query test (test 637) will detect most problems caused  
by hardware failures or incorrect administration. However, the Layer 3 test (test  
637) cannot detect end-to-end transmission problems with the Standby  
D-channel since Layer 3 messages are not sent on the standby channel.  
For G3r, the SYS-LINK Maintenance Object reports Layer 2 ISDN-PRI D-channel  
problems and for G3i/s/vs, the PKT-INT Maintenance Object reports Layer 2  
ISDN-PRI D-channel problems (if the D-channel is connected to the Processor  
Interface circuit pack). However, the PKT-INT Maintenance Object does not  
monitor the Layer 2 status of the ISDN-PRI D-channel when the D-channel is  
connected to the Packet Control circuit pack for the ISDN-PRI over PACCON  
feature. The Layer 2 Query test is provided to detect D-Channel Layer 2 failures  
and generate an associated Warning alarm independent of the hardware  
configurationDuoswendloafodrfrothmeWDw-wc.Shoamnanneualsls..com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-731  
Table 3-308. TEST #647 Layer 2 Status Query Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1132  
ABORT  
Internal system error  
The port location for the primary ISDN-PRI D-channel is not known. This  
condition should not be possible since an administered DS1 circuit pack  
must be specified when a Signaling Group is administered:  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
1134  
ABORT  
The associated DS1 circuit pack is not administered. This condition should  
not be possible since an administered DS1 circuit pack must be specified  
when a Signaling Group is administered.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
2500  
1
ABORT  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Layer 2 of the primary signaling channel is down:  
1. Examine the results of the Primary Signaling Link Hardware Test (#636)  
and follow recommendations provided there.  
2. If test #636 passes, the Layer 2 Query test may still fail if the Signaling  
Channel at the far end has not been administered correctly or if it has  
been busied out. Verify that the Primary Signaling Channel (D-channel)  
at the far end has been administered correctly. Verify that the DS1 port  
used for the Primary D-channel has not been busied out at the far end.  
2
FAIL  
Layer 2 of the secondary signaling channel is down.  
1. Examine the results of Secondary Signaling Link Hardware Test (#639)  
and follow recommendations provided there.  
2. If tests #639 passes, the Layer 2 Query test may still fail if the Signaling  
Channel at the far end has not been administered correctly or if the  
Signaling Channel has been busied out. Verify that the Secondary  
Signaling Channel (D-channel) at the far end has been administered  
correctly. Verify that the DS1 port used for the Secondary D-channel  
has not been busied out at the far end.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-SGR (ISDN-PRI Signaling Group)  
3-732  
Table 3-308. TEST #647 Layer 2 Status Query Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
3
FAIL  
Both the primary and secondary Channels are down.  
1. Examine the results of the Primary and Secondary Signaling Link  
Hardware Tests (#636 and #639) and follow recommendations  
provided there.  
2. If tests #636 and #639 pass, the Layer 2 Query test may still fail if the  
Signaling Channels at the far end has not been administered correctly  
or if the Signaling Channels have been busied out. Verify that the  
Primary and Secondary Signaling Channel (D-channels) at the far end  
have been administered correctly. Verify that the DS1 ports used for  
the Primary and Secondary D-channels have not been busied out at  
the far end.  
PASS  
The Primary Signaling Channel is up and, if administered the Secondary  
Channel is up.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-733  
ISDN-TRK (DS1 ISDN Trunk)  
MO Name (in  
Alarm Log)  
Alarm Level  
Initial Command to Run  
test port PCSSpp l  
Full Name of MO  
1
2
ISDN-TRK  
MAJOR  
DS1 ISDN Trunk  
DS1 ISDN Trunk  
DS1 ISDN Trunk  
ISDN-TRK  
ISDN-TRK  
MINOR  
test port PCSSpp l  
WARNING  
test port PCSSpp sh  
1. For additional repair information, refer to the "DS1-BD (DS1 Interface Circuit Pack)"  
maintenance object.  
2. A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by the  
set options command and that at least 75 percent of the trunks in this trunk group are  
alarmed.  
A DS1 ISDN Trunk is known as a B-channel. It is a 64 kbps Bearer channel that  
can be used to transmit digital traffic, be it voice or data. These trunks use a  
separate channel for signaling (for example, for call setup); this mode of  
operation is known as out-of-band signaling, as opposed to in-band, robbed-bit  
signaling, where the signaling traffic flows over the same channel as the voice or  
data traffic. The separate signaling channel is called a D-channel in ISDN  
terminology, and it carries all the call control signaling messages for the DS1  
ISDN Trunk B-channels. The D-channel for these B-channels is an ISDN-PRI  
(Primary Rate Interface) Signaling Link Port (ISDN-LNK/ISDN-PLK).  
On 24-channel interfaces, any of the first 23 ports on the DS1/UDS1 interface  
circuit pack can be a B-channel. The 24th port may be used as a B-channel or as  
a D-channel depending on the type of ISDN-PRI Signaling Group (ISDN-SGR) to  
which it belongs.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-734  
Slot 1  
Processor  
(TN798)  
DS1  
Interface  
circuit pack  
TN767  
Voice or data ISDN -TRK  
(B-Channel)  
(Port 1)  
T
D
M
2
Voice or data  
(Port 23)  
ISDN -TRK  
(B-Channel)  
b
u
s
Pimary  
signaling link  
ISDN -PLK  
(D-Channel)  
(Port 24)  
cydfisd3 RPY 061297  
Figure Notes  
1. B- and D-channel messages are  
routed over the TDM Bus. For  
additional reliability, a duplex  
D-channel can be administered for  
a signaling group and located on a  
different TN464C (or higher) circuit  
pack.  
2. TN767B (or higher) for DS1;  
TN464C (or higher) for UDS1  
Figure 3-25. DS1 ISDN Trunk Interactions (24 Channel - TN767/464C)  
On 32 channel interfaces, any of ports 1-15 and 17-31 on the DS1 interface  
circuit pack can be a B-channel. The 16th port may be used as a B-channel or as  
a D-channel depending on the type of ISDN-PRI Signaling Group (ISDN-SGR) to  
which it belongs. For more details, refer to the ISDN-SGR and DS1-BD/UDS1-BD  
Maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-735  
Slot 1  
(Port 0)  
Framing  
Voice or data  
(Port 1)  
ISDN -TRK  
(B-Channel)  
Processor  
(TN798)  
UDS1  
Interface  
circuit pack  
TN464  
T
D
M
(Port 15)  
ISDN -TRK  
(B-Channel)  
2
Pimary  
signaling link  
ISDN -PLK  
(D-Channel)  
b
u
s
(Port 16)  
Voice or data  
(Port 17)  
ISDN -TRK  
(B-Channel)  
Voice or data  
(Port 31)  
ISDN -TRK  
(B-Channel)  
cydfisd2 RPY 061297  
Figure Notes  
1. B- and D-channel messages are  
routed over the TDM Bus. For  
additional reliability, a duplex  
D-channel can be administered for  
a signaling group and located on a  
different TN464C (or higher) circuit  
pack.  
2. TN464C or higher  
Figure 3-26. ISDN-PRI Signaling Link Port Interactions (32-Channel - TN464)  
For interfaces using country protocol 1 on the DS1 Circuit Pack administration  
form (including US), the signaling protocol used for the maintenance of the  
B-channel is defined by the Lucent ISDN-PRI Specification.  
For interfaces using country protocols other than 1, the signaling protocol used  
for the maintenance of the B-channel is defined by the CCITT ISDN-PRI  
Specification.  
There are five possible Service States for a B-channel. The service state is  
negotiated with the far-end switch, changes over time, and may have a far-end or  
near-end component. The service state is initialized to Out-Of-Service/Far-End  
state and an attempt is made to negotiate it to In-Service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-736  
NOTE:  
The service state of a particular DS1 ISDN Trunk B-channel can be  
displayed by issuing the status trunk <trunk_group/trunk_member>  
system technician command.  
If a call is present, the Specification defines the permissible Call States as well.  
There are tests in the Short and Long Test Sequences for DS1 ISDN Trunk  
designed to audit these states and ensure agreement between both ends of the  
PRI connection.  
Alarming Based on Service States  
A warning alarm is logged against a DS1 ISDN B-channel trunk when it is placed  
in the Maintenance/Far-End or Out-Of-Service/Far-End states, during which the  
trunk is unusable for outgoing calls. When a warning alarm is present, use status  
trunk group#/member# command to determine the exact state. Other alarms  
can be diagnosed by using the short and/or long test sequences. Note that an  
ISDN B-channel trunk can be placed in a Far-End service state by either action  
taken by the far-end switch or by failure of the far-end switch to respond. For  
example, if the far-end does not respond to a Remote Layer 3 Query (Test #637  
for ISDN-SGR), the associated DS1 ISDN trunk B-channels is placed in the  
Maintenance/Far-End service state.  
As a port on a DS1 circuit pack (DS1-BD or UDS1-BD), and as part of a signaling  
group dependent on a D-channel (ISDN-PLK) for signaling, operation of the  
ISDN-TRK is dependent on the health of these other maintenance objects.  
DS1 ISDN Trunk Service States  
This section defines the possible service states of a DS1 ISDN trunk, explains the  
reason for each service state, and provides the recommended recovery  
procedures (when required).  
Service States  
■
In-Service (INS)  
The B-channel is in its normal operating state.  
Out-of-Service/Far-end (OOS/FE)  
■
A B-channel is initialized to this state when administered and it may also  
be in this state if there is a failure on the B-channel attributed to a problem  
on the far-end switch. The switch sends messages to the far-end to  
negotiate the B-channel into service. If the far-end does not respond to the  
messages within a certain time period, then the service state remains  
out-of-service and maintenance will periodically resend the messages.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-737  
The trunk is unusable for outgoing calls. On US interfaces, the trunk is  
unusable for incoming calls, but on non-US interfaces, incoming calls will  
be accepted.  
■
Out-of-Service/Near-end (OOS/NE)  
This is the state of the trunk when a hardware failure exists on the link, the  
NPE Crosstalk Test fails, or when the trunk is busied out by system  
technician. In this state, the trunk is unusable for incoming or outgoing  
calls. No messages are sent to the far-end until the signaling link comes  
back into service or the trunk is released by system technician.  
■
Maintenance/Far-end (MTC/FE)  
This state is reached when the far-end does not respond to messages  
sent over the signaling link for a particular trunk after a certain amount of  
time. This state is different from OOS/FE since the signaling link must have  
initially been up and the B-channels in-service. The switch will periodically  
send messages to the far-end to try to negotiate the trunk (B-channel) into  
service. The trunk is unusable for outgoing calls but will service incoming  
call requests from the far-end. Note that transitions into MTC/FE do not  
drop stable calls. Therefore, if the service state changes from in-service to  
MTC/FE, then stable calls are unaffected.  
■
Maintenance/Near-end (MTC/NE)  
The trunk (B-channel) is in this state if the signaling link (PKT-INT) is  
busied out by system technician. The trunk (B-channel) is also temporarily  
in this state if system technician has issued a test trunk trunk_  
group/trunk_member long command. This command will execute the  
ISDN-PRI test call. This test will change the state of the trunk member to  
MTC/NE for the duration of the test unless a call request comes in from the  
far-end. In that case, the test would abort. Note that transitions into  
MTC/NE do not drop stable calls. Therefore, a system technician-  
demanded busyout link lnk-no command will not drop stable trunk calls.  
In this state, the B-channel is not usable for new outgoing calls, but is  
available for incoming calls and outgoing test calls.  
■
Pending States  
If the near-end is expecting a timed response from the far-end for a  
request to change the service state of a trunk, then the state of the trunk  
reflects a Pending State.  
— Pending-in-service (PINS)  
The near-end has sent a B-channel maintenance message to the  
far-end, requesting that the B-channel service state be transitioned  
to in-service. The far-end has a certain amount of time to respond to  
the message. The service state will be PINS until either a response  
is received or the timer expires.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-738  
— Pending-maintenance (PMTC)  
This state is supported only by systems using country protocol 1  
(including US). The near-end has sent a B-channel maintenance  
message to the far-end, requesting that the B-channel service state  
be transitioned to maintenance. The far-end has a certain amount  
of time to respond to the message. The service state will be PMTC  
until either a response is received or the timer expires.  
— Call Activity States  
In addition to the service and pending state, the state of a  
B-channel also reflects its call activity. If a call is connected over the  
B-channel, then the state of the trunk will reflect the "active" call  
state, for example, "in-service/active." If there is no call on the  
B-channel, then the trunk will reflect the "idle" call state, for  
example, "OOS/FE-idle."  
The following diagram of the DS1 ISDN Trunk service states shows the  
common progression from one service state to another and the event that  
caused the change of state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-739  
Out-of-  
Service  
Near End  
Maintenance  
Near End  
Craft busyout of B-channel  
(TRK-GRP/MBR), or problem  
with near en d PI-LINK, DS1-BD,  
PI-BD, or port.  
Craft release of  
B-channel or  
clearing of near-end  
problem with  
Craft busyout of signaling link  
DS1-BD, PI-BD,  
PI-LINK or port.  
busyout link LINK-NO or  
transient state for demand  
long test of the trunk.  
Craft release  
of signaling  
link, or craft  
demanded test  
completed.  
Administer  
B-channel  
as member  
of a trunk  
group.  
Received indication  
from far end that  
B-channel in/not  
in service.  
D-channel has  
been down for at  
least 90 seconds,  
or Remote Level 3  
Query failed.  
Out-of-  
Service  
Far End  
Maintenance  
Far End  
In-Service  
Failed to receive  
reply from far end.  
MTCE will periodically  
try to resend the  
message. [Country  
protocol 1]  
Failed to receive  
reply from far  
end. MTCE will  
periodically try  
to resend the  
message.  
If D-channel control-  
ling the B-channel is  
up, send a message  
requesting transition  
to In-Service.  
Failed to receive  
If D-channel  
controlling the  
B-channel is  
up, send a  
message  
requesting  
transition to  
In-Service.  
reply from far end.  
MTCE will periodically  
try to resend the  
message. [country  
protocol other than 1]  
Received  
acknowledgement  
Received  
acknowledgement  
or other indication  
or other  
indication from the  
far end that  
B-channel is in service.  
from the far end,  
that B-channel is  
inservice.  
Out-of-  
Service  
Far End  
Pending  
Maintenance  
Far End  
Pending  
In-Service  
In-Service  
Figure 3-27. Common Progressions in Service States  
ISDN-PRI Trunk Service States  
The following chart summarizes each of the different DS1 ISDN Trunk service  
states that can result when the status trunk <trunk_group/trunk_member>  
command is issued.  
NOTE:  
Refer to ‘‘Troubleshooting ISDN-PRI Problems’’ in Chapter 1, ‘‘Maintenance  
for csi systems’’ for a layered approach to processing ISDN-PRI problems.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-740  
Table 3-309. ISDN-PRI Trunk Service States (Test #161 Loop Around Test)  
Service State  
Alarm*  
Possible Cause  
Possible Solution  
out-of-service/NE  
Warning  
Trunk is demand busied out. Enter release trunk  
grp#/mbr#.  
Minor  
None  
NPE Crosstalk Test (#6)  
failed.  
Replace DS1/UDS1 circuit  
pack.  
DS1 or UDS1 circuit pack  
lost its signal.  
Is the DS1/UDS1 circuit  
pack or cable removed? Is  
the far-end switch  
restarting? Check circuit  
pack using procedures in  
DS1-BD or UDS1-BD.  
out-of-service/FE  
Warning  
Warning  
None  
Unadministered far-end  
Administer corresponding  
trunk on far-end switch.  
The far-end trunk is busied  
out.  
Check the status of the  
far-end switch.  
pending-in-service,  
pending-maint  
Maintenance message was  
sent and the switch is  
Wait 2 minutes and check  
service state after the  
waiting up to 2 min. for a  
reply from the far-end.  
pending state has cleared.  
maint-NE  
maint-FE  
None  
ISDN test call in progress  
(test trunk long and test  
isdn-testcall commands)  
Wait several minutes for test  
to finish and check status  
again.  
None  
System link has been busied  
out by command.  
Check link status. Release  
link with release link link#.  
Warning  
Signaling channel has been  
down for over 90 sec.  
Consult ISDN-SGR and/or  
ISDN-LNK. Far-end  
signaling channel may be  
busied out, or the far-end  
switch may currently be  
restarting.  
Warning  
Repeated failure of far end  
to respond to messages.  
Maintenance software will  
periodically try to resend  
messages. You can speed  
the process with test trunk  
grp#/mbr# and/or test  
signaling-gr #.  
Warning  
None  
The far-end trunk is being  
tested.  
Check status of the far-end  
switch. Wait for testing to  
finish.  
in-service  
Normal operating state  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-741  
Error Log Entries and Test to Clear Values  
Table 3-310. DS1 ISDN Trunk Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Any  
Alarm Level  
Test to Clear Value  
1
0
0
Any  
Any  
test port PCSSpp sh r 1  
test port PCSSpp sh r 1  
1 (a)  
Any  
Any  
None  
15 (b)  
Audit and Update  
Test (#36)  
18  
0
busyout trunk  
<grp>/<mbr>  
release trunk  
<grp>/<mbr>  
129 (c)  
130 (d)  
257 (e)  
513 (f)  
769 (e)  
1281  
None  
None  
None  
None  
None  
WARNING  
WARNING  
OFF  
ON  
test port PCSSpp  
test port PCSSpp  
test port PCSSpp  
test port PCSSpp  
test port PCSSpp  
test port PCSSpp l r 4  
Any  
Any  
Any  
Any  
WARNING  
OFF  
2
Conference Circuit  
Test (#7)  
MIN/ WRN  
ON  
ON  
2
1537  
Any  
NPE Crosstalk Test  
(#6)  
MIN/WRN  
test port PCSSpp l r 3  
1793 (g)  
3073 (h)  
Any  
Any  
None  
test port PCSSpp  
test port PCSSpp  
Service State Audit  
(#256)  
3585 (i)  
3841 (j)  
Any  
Any  
None  
None  
None  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the  
set options command. If the Minor alarm is not downgraded by the set options values, then the  
Minor alarm will be upgraded to a Major alarm if 75 percent of the trunks in this trunk group are  
alarmed.  
Notes:  
a. These error types indicate a disagreement between this switch and the  
switch at the other end of the trunk connection with regard to the ISDN call  
state of the DS1 ISDN Trunk. This switch will automatically try to recover by  
clearing the call, (that is, the call will be torn down). You can use the  
status trunk <trunk_group/trunk_member> command to determine the  
state of the trunk.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-742  
When running the Short Test Sequence of tests, pay close attention to the  
results of the Call State Audit Test (#257).  
b. This is a software audit error that does not indicate any hardware  
malfunction. Run the Short Test Sequence and investigate associated  
errors (if any).  
c. The far-end switch changed its ISDN service state to either out-of-service  
or maintenance. This may be a temporary condition due to testing of that  
trunk by the far-end or a hardware problem with the trunk. Outgoing calls  
will not be allowed over the trunk. To investigate the status of the trunk,  
issue the status trunk <trunk_group/trunk_member> command.  
d. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
e. These error types indicate a disagreement between this switch and the  
switch at the other end of the trunk connection with regard to the ISDN  
service state of the DS1 ISDN Trunk. This switch will automatically try to  
recover by performing a service state audit. You can use the status trunk  
<trunk_group/trunk_member> command to determine the state of the  
trunk.  
When running the Short Test Sequence, pay close attention to the results  
of the Service State Audit Test (#256).  
f. This trunk is not recognized by the far-end switch. Investigate the trunk  
administration for both switches and make changes as necessary.  
g. This error indicates a failure of the DS1/UDS1 Interface circuit pack. When  
running the Short Test Sequence, the results of the Signaling Link State  
Check Test (#255) are important.  
h. Two Service State Audit attempts have failed (see Test #256). The trunks  
will not be usable for any outgoing calls (although incoming calls will be  
accepted) until the test passes and the trunk state is changed to  
in-service (use status trunk trunk_group/trunk_member to investigate  
trunk status).  
i. Error Type 3585 appears when the switch receives an ISDN RESTART  
message for an ISDN trunk. Calls are cleared with the RESTART message.  
Therefore, this error type may be associated with a dropped call report  
from a user.  
The following Aux Data values for Error Type 3585 represent the trunk’s  
ISDN call state at the time the unexpected request to restart the channel  
was received from the remote switch. This information can be useful if  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-743  
dropped calls (cutoffs) are being reported by users of the ISDN-PRI  
trunks. The meanings of the various Aux Data values are shown below;  
any others can be ignored.  
Aux  
Data  
Explanation  
A idle trunk received a restart.  
0
10  
A call in a stable, talking state was cleared unexpectedly by the  
far-end with an ISDN RESTART message. This state is called the  
"active" state.  
4, 7, 8  
260,  
263  
A call that has not reached the active state, but has at least reached  
a ringing state, was cleared unexpectedly by the far-end with an  
ISDN RESTART message.  
1, 3, 6  
9, 265  
A call that has not yet reached a ringing state was cleared  
unexpectedly by the far-end with an ISDN RESTART message.  
11, 12  
19, 531,  
267,  
A call that was in the process of clearing anyway has been cleared  
by the far-end with an ISDN RESTART message. If this condition  
occurs frequently, it may mean that the far-end is attempting to clear  
trunks that it thinks are in a "hung" state. The RESTART message  
brings the trunk to an idle condition.  
268  
j. An ISDN trunk selected by the near-end has been rejected 10 times by the  
far-end without a successful call. This may indicate a service state  
mismatch between the near-end and far-end for this trunk that is effecting  
the end user (that is, customer receives unexpected intercept tones when  
accessing ISDN trunks). This may indicate that the ISDN trunk is not  
administered on the far-end.  
The Aux field contains the physical name of the ISDN trunk in decimal.  
Then, verify that the far-end has this trunk administered. If problems  
persist, then busy-out the ISDN trunk to take it out of the hunt group.  
The Warning alarm will be retired automatically whenever an outgoing or  
incoming call that uses this trunk is answered by the called endpoint. If  
problems persist, then busy-out the ISDN trunk to take it out of the hunt  
group.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the NPE  
Crosstalk Test, for example, you may also clear errors generated from other tests  
in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-744  
Table 3-311. System Technician-Demanded Tests: ISDN-TRK  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
X
X
X
X
X
X
Conference Circuit Test (#7)  
Audit and Update Test (#36)  
Signaling Link State Check Test (#255)  
Service State Audit Test (#256)  
Call State Audit Test (#257)  
ISDN Test Call Test (#258)  
ND  
X
X
X
X
ND  
ND  
ND  
ND  
ND  
1. D = Destructive, ND = Non-destructive  
NPE Crosstalk Test (#6)  
The NPE Crosstalk Test verifies that this port’s NPE channel talks on the selected  
time slot and never crosses over to time slots reserved for other connections. If  
the NPE is not working correctly, one-way and noisy connections may be  
observed. This test is usually only part of a port’s Long Test Sequence and takes  
about 20 to 30 seconds to complete.  
NOTE:  
The TN464C or later UDS1 circuit pack has one SCOTCH-NPE chip instead  
of several NPE chips.  
Table 3-312. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required for this test are not available. The port may be in  
use on a valid call. Use status station or status trunk commands to  
determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-745  
Table 3-312. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1001  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due to  
TDM-Bus errors. Refer to TDM-Bus Maintenance to diagnose any active  
TDM-Bus errors.  
1. If the system has no TDM-Bus errors and is not handling heavy traffic,  
repeat the test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present or some tone  
detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a maximum  
of 5 times.  
1004  
1018  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use status station or  
status trunk commands to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Maintenance is disable on this trunk.  
1. Enable maintenance by entering ‘‘y’’ in the ‘‘Maintenance Tests?’’ field on  
page 2 of the change trunk-group form.  
1117  
2000  
ABORT  
ABORT  
A service state audit message is outstanding.  
1. Wait 2 minutes and then try again.  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2020  
2100  
ABORT  
ABORT  
The test did not run due to an already existing error on the specific port or a  
more general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit pack  
and attempt to diagnose the already existing error.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-746  
Table 3-312. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Any  
FAIL  
The NPE of the tested port was found to be transmitting in error. This will  
cause noisy and unreliable connections. The ISDN-TRK is moved to  
out-of-service/near-end state.  
1. Replace the circuit pack.  
PASS  
The port is able to communicate over the TDM Bus.  
Conference Circuit Test (#7)  
The Conference Circuit test verifies that the NPE channel for the port being  
tested can correctly perform the conferencing function. The NPE is instructed to  
listen to several different tones and conference the tones together. The resulting  
signal is then measured by a tone detector port. If the level of the tone is within a  
certain range, the test passes.  
NOTE:  
The TN464C or later UDS1 circuit pack has one SCOTCH-NPE chip instead  
of several NPE chips.  
Table 3-313. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use on a valid call. Use status station or status trunk commands to  
determine when the port is available for testing.  
1004  
1018  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use status station or  
status trunk to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Maintenance is disabled on this trunk.  
1. Enable maintenance by entering y in the Maintenance Tests?  
field on page 2 of the change trunk-group form.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-747  
Table 3-313. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1020  
ABORT  
The test did not run due to an already existing error on the specific port or a  
more general circuit pack error.  
Examine Error Log for existing errors against this port or the circuit pack  
and attempt to diagnose the already existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Any  
FAIL  
The NPE of the tested port did not conference the tones correctly. This will  
cause noisy and unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port can correctly conference multiple connections. User-reported  
troubles on this port should be investigated using other port tests and  
examining station, trunk, or external wiring.  
Audit and Update Test (#36)  
This test sends port level translation data from switch processor to the DS1  
interface circuit pack to assure that the trunk’s translation is correct. The port  
audit operation verifies the consistency of the current state of trunk kept in the  
DS1 interface circuit pack and in the switch software.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-748  
Table 3-314. TEST #36 Audit and Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
Maintenance is disabled on this trunk.  
1018  
1. Enable maintenance by entering y in the Maintenance Tests?field  
on page 2 of the change trunk-group form.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times  
Test failed due to Internal system error.  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
Trunk translation has been updated successfully. The current trunk states  
kept in the DS1 interface circuit pack and switch software are consistent. If  
the trunk is busied out, the test will not run, but will return PASS. To verify  
that the trunk is in-service:  
1. Enter status-command to verify that the trunk is in-service. If the trunk  
is in-service, no further action is necessary. If the trunk is  
out-of-service, continue to Step 2.  
2. Enter release-trunk command to put trunk back into in-service.  
3. Retry the test command.  
Signaling Link State Check Test (#255)  
As noted in the general description for a DS1 ISDN Trunk, it depends on the  
health of the DS1/UDS1 interface circuit pack and the ISDN-PRI D-channel  
(ISDN-LNK/ISDN-PLK) trunk for proper operation. This test checks the status of  
those critical elements.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-749  
Table 3-315. TEST #255 Signaling Link State Check Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
Maintenance is disable on this trunk.  
1018  
1. Enable maintenance by entering y in the Maintenance Tests?  
field on page 2 of the change trunk-group form.  
1114  
4
ABORT  
FAIL  
The signaling link is in a transitional state.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
There is a problem with the Signaling Channel.  
1. If the Packet Control circuit pack is used consult the procedures for  
the ISDN-PRI Signaling Group (ISDN-SGR). Further information may  
also be obtained by consulting the procedures for the ISDN-PRI  
Signaling Channel (ISDN-PLK).  
2. If the Packet Interface is used, consult the procedures for PKT-INT.  
There is a problem with the DS1 interface circuit pack.  
8
FAIL  
1. Consult the procedures for DS1 interface circuit pack  
(DS1-BD/UDS1-BD).  
PASS  
The signaling link hardware is OK.  
Service State Audit (#256)  
These trunks may be in one of several service states. This test performs a  
Service State Audit with the far-end switch.  
For interfaces using country protocol 1 (including US), the Service State Audit  
executes in all trunk service states. A message is sent to the far-end switch to  
ensure that both sides agree on the service state. A PASS for this test simply  
means that the message has been successfully sent. Two minutes are allowed  
for a reply. If no reply is received within that 2 minute window, the message is  
sent out again. If that attempt fails, an error is logged (Error Type 3073) and the  
switch then attempts another Service State Audit every 15 minutes. If the trunk  
was initially INS (in-service), it is then placed in the MTC/FE (maintenance state,  
far-end problem) state. No outgoing calls are placed over this trunk, but  
incoming calls are accepted. If an incoming call is presented while in such a  
state, a Service State Audit attempt is immediately attempted (that is, the switch  
does not wait for the 15-minute cycle, but tries to recover immediately).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-750  
For interfaces not using country protocol 1, the Service State Audit executes only  
if the trunk is in the OOF/FE state. A message is sent to the far-end switch to  
attempt to bring the trunk back into the in-service state. A PASS for this test  
simply means that the message has been successfully sent. Two minutes are  
allowed for a reply. If no reply is received within that two minute window, the  
message is sent out once again. If no response is received in the next two minute  
window, then the trunk remains in the OOS/FE state. The switch will attempt  
another Service State Audit in another hour.  
To investigate the service state of the DS1 ISDN Trunk, issue the status trunk  
trunk-group/trunk-member command.  
Table 3-316. TEST #256 Service State Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be on a valid call. Use status station or status trunk to determine when  
trunk is available for testing.  
1. Check the results of Test #255 (Signaling Link State Check).  
Maintenance is disable on this trunk.  
1018  
1113  
1114  
ABORT  
ABORT  
ABORT  
1. Enable maintenance by entering y in the Maintenance Tests?field  
on page 2 of the change trunk-group form.  
The signaling link has failed, so the system cannot send any messages on  
behalf of this trunk.  
1. Check the results of Test #255 (Signaling Link State Check).  
The signaling link is in a transitional state.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1116  
1117  
ABORT  
ABORT  
The trunk is not in a service state which is appropriate for running the test.  
This test is only performed in the OOS/FE state.  
A service state audit message is outstanding.  
1. Wait two minutes and then try again.  
2100  
1113  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The signaling link has failed, so the system cannot send any messages on  
behalf of this trunk.  
1. Consult the procedures for ISDN-LNK (ISDN-PRI Signaling Link Port)  
and PKT-INT (Packet Interface).  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-751  
Table 3-316. TEST #256 Service State Audit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
Wait 4 minutes and then check the Error Log for any new errors of type  
3073. If there are none, then both sides of the ISDN connection agree on  
the service state; the negotiation succeeded. If there is a new 3073 error,  
then the negotiation failed (the far-end switch twice failed to respond within  
2 minutes). The switch will automatically retry every 15 minutes. If the trunk  
was initially in-service, it is now placed in the maintenance/far-end state.  
Incoming calls will be accepted, but no outgoing calls can be originated. If  
an incoming call is presented, another Service State Audit will be  
immediately performed in an attempt to put the DS1 ISDN Trunk in the  
proper state.  
Call State Audit Test (#257)  
If a call is active on the trunk, the switches on both sides of the connection should  
agree on the ISDN state of the call, as defined in the ISDN Protocol Specification.  
This test audits internal call state data by querying the far-end switch as to the  
ISDN state of the call. It can be helpful when trying to clear a hung call. If the  
internal call state data on the near-end switch is different than that of the far-end  
switch, then the call will be torn down.  
As with Test #256 (Service State Audit), a PASS simply means that an appropriate  
message was composed and sent to the far-end switch. The ISDN Specification  
allows up to two minutes for a reply. If a reply is not received within the two minute  
window, a protocol time-out violation will be recorded in the error log against the  
associated signaling channel (ISDN-PRI Signaling Link Port, which is listed in the  
Error Log as ISDN-LNK/ISDN-PLK; the Error Type is 1).  
Table 3-317. TEST #257 Call State Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Maintenance is disable on this trunk.  
1018  
ABORT  
1. Enable maintenance by entering y in the Maintenance Tests?field  
on page 2 of the change trunk-group form.  
1019  
ABORT  
An audit is already in progress.  
1. Wait two minutes and try again.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-752  
Table 3-317. TEST #257 Call State Audit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1113  
ABORT  
The signaling link has failed, so the system cannot send any messages on  
behalf of this trunk.  
1. Check the results of Test #255 (Signaling Link State Check).  
The signaling link is in a transitional state.  
1114  
1116  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The trunk is in an out-of-service ISDN service state.  
1. A call cannot be present if the trunk is in an ISDN out-of-service state,  
so a call state audit would be inappropriate. No action necessary. (Use  
the status trunk  
2100  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
This switch sent a call state auditing message to the far-end switch to verify  
the state of the call active on this trunk. If a call state mismatch is found,  
then the call will be torn down within two minutes. If no call was active, then  
no message was sent.  
ISDN Test Call Test (#258)  
This test performs a far-end loop around to a far-end switch over an ISDN trunk.  
The trunk’s service state must be in-service, maint-NE, or out-of-service/NE, and  
no call can be active on the trunk. The test call can be initiated as part of a long  
test sequence, or as an individual test, as described below. This test is valid only  
for systems using country protocol 1 (including US), or when the far end has  
loop-around capability.  
A test call connection is established to a far-end switch over the ISDN trunk to be  
tested. The digital port on a TN711D Maintenance/Test circuit pack generates a  
test-pattern bit stream which is sent to the far-end switch and echoed back. The  
received pattern is then compared to the sent pattern and checked for errors that  
indicate a loss of integrity on the communications path.  
If a test call is running when scheduled maintenance starts, the green LED is  
turned off. To determine if a test call is still running, use the list isdn-testcall and  
status isdn-testcall commands. A lit yellow LED on the Maintenance/Test circuit  
pack also indicates that a test call is running.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-753  
There are two methods available to place an outgoing ISDN-PRI test call.  
In the first method, the test call connection is established over the TDM Bus of  
the transmit and receive sides of the ISDN-PRI trunk to a data channel. This  
method is selected when no Maintenance/Test circuit pack resides in the system.  
In the second method, the test call connection is established over the TDM Bus  
of the transmit and receive sides of the ISDN-PRI trunk to a digital trunk testing  
port on the Maintenance/Test circuit pack. The Maintenance/Test Digital Port  
generates a pseudo bit stream. A pictorial description of the outgoing ISDN-PRI  
test call connectivity is contained in Figure 3-28.  
PI (TN765)  
or  
PACCON  
(TN778)  
NETCON  
SPE  
B-channel  
D-channel Setup  
B-channel  
TDM BUS  
M/T  
TN7771B  
DS1/UDS1  
Figure 3-28. ISDN-PRI Outgoing Test Call  
Synchronous Commands  
You can demand a synchronous outgoing test call by using the following  
maintenance commands:  
■
■
■
test trunk trunk-group-no/member-no long [repeat number]  
test board board-location long [repeat number]  
test port port-location long [repeat number]  
Whenever a circuit translates to an ISDN-PRI trunk during a Long Test Sequence,  
an outgoing test call is invoked. If the B-channel is unrestricted (B8ZS or HDB3)  
the default duration of the test call is 8.6 seconds. Otherwise, if the B-channel is  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-754  
restricted (ZCS) the default duration of the test call is 9.4 seconds. Once the test  
call completes, the bit error rate is retrieved from the Maintenance/Test Digital  
Port. A bit error rate greater than zero is reported as a failure to the Manager I  
terminal (MGRI). A failure indicates the need to run further diagnostics, such as  
the test isdn-testcall command.  
If no Maintenance/Test circuit pack exists, the outgoing ISDN-PRI test call is  
established over a high speed data channel on the Network Control (NETCON)  
circuit pack (DATA-BD).  
Asynchronous Commands  
You can start, query, and stop an outgoing test call by using the following  
maintenance commands:  
■
test isdn-testcall trunk-group-no/member-no [ minutes ]  
This command enables you to start an outgoing ISDN-PRI test call for a  
maximum of two hours (120 minutes).  
■
status isdn-testcall trunk-group-no/member-no  
This command displays the progress of the outgoing test call by reporting  
the bit and block error rates of the tested B-channel specified by the "trunk  
group no/member no" identifier.  
■
clear isdn-testcall trunk-group-no/member-no  
This command enables you to stop an outgoing test call already in  
progress. The trunk-group-no/member-no identifier specifies the  
B-channel used to stop the test call. The measurements are not cleared  
until the next test call begins.  
NOTE:  
Only one trunk can be tested in a given port network, until the test call is  
canceled or completes.  
Table 3-318. TEST #258 ISDN TEST Call  
Error  
Code  
Test  
Result  
Description/ Recommendation  
There is a problem with the Processor Interface Link.  
1. Refer to PKT-INT (Packet Interface).  
4
8
ABORT  
ABORT  
There is a problem with the DS1 interface circuit pack.  
1. Refer to DS1-BD (DS1 Interface Circuit Pack).  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-755  
Table 3-318. TEST #258 ISDN TEST Call — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1004  
ABORT  
B channel in use.  
1. Determine if a call is active on this DS1 ISDN Trunk via the status trunk  
2. When the service state indicates in-service/idle, retry the test.  
Bad Configuration (that is, no Maintenance/Test circuit pack)  
1005  
ABORT  
Issue the test trunk <trunk Group/trunk member> command and make  
sure there is a DATA-CHL (NETCON channel) administered.  
1018  
1019  
ABORT  
ABORT  
Test call is disabled.  
1. Enable Maintenance on the Trunk Group form.  
Another Test call is in progress.  
1. Issue the list isdn-testcall command to locate the test call.  
2. Issue the status isdn-testcall command to find out the duration and  
start time of the test call.  
3. Issue the clear isdn-testcall command to stop the test call from  
running.  
1020  
1024  
ABORT  
ABORT  
There is a problem with DS1 Interface Circuit Pack.  
1. Refer to the DS1-BD (DS1 Trunk circuit pack).  
Maintenance/Test Digital Port in use.  
1. Wait until yellow and green LEDs are turned off on the  
Maintenance/Test circuit pack.  
2. Retry the test.  
1113  
ABORT  
The signaling link has failed. Therefore, the system cannot send any  
messages on behalf of this trunk.  
1. Check the results of Test #255 (Signaling Link State Check Test).  
The signaling link is in a transitional state.  
1114  
1116  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The switch could not appropriately change the ISDN service state.  
1. Determine if a call is active on this DS1 ISDN Trunk (use the status  
trunk  
2. If not, check the Error and Alarm Logs for problems with this ISDN-TRK  
(DS1 ISDN Trunk) MO.  
1117  
ABORT  
ISDN B-channel maintenance message is already outstanding.  
1. Wait two minutes. Then try again.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-756  
Table 3-318. TEST #258 ISDN TEST Call — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Far-end of ISDN trunk is not administered.  
1118  
ABORT  
1. Check the administration of the far-end ISDN trunk.  
2. Issue the status trunk  
3. Try the test again.  
1119  
1120  
ABORT  
ABORT  
The test call was aborted due to a normal call attempt on this trunk. The test  
call is performed only if the trunk is idle.  
1. Either wait for the normal call to terminate normally, or force it to be  
dropped by using the busyout trunk  
The DS1 ISDN Trunk is in the ISDN out-of-service/far-end state.  
1. Try to change the service state via Test #256 (Service State Audit Test).  
Then retry this test. However, the trunk may be in the  
out-of-service/far-end state due to problems at the far-end switch.  
If that is the case, no remedial action can be taken at this end.  
1122  
1123  
ABORT  
ABORT  
ABORT  
There is no test line number for the far-end switch.  
1. Check the Trunk Group Administration form.  
There is no Feature Access Code administration for this Facility Test.  
1. Check the Dial Plan and Feature Administration forms.  
Internal system error  
None  
2012  
2000  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2035  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
The call has timed out, perhaps because of a lack of system resources.  
1. Wait 1 minute and try again.  
2036  
2037  
Internal system error  
1. Follow the recommendation for ABORT code 2012.  
A problem occurred while trying to read the test data.  
1. Wait 1 minute and then try again.  
2038  
2039  
2040  
2041  
2066  
Internal system error  
1. Follow the recommendations for ABORT code 2012.  
The call has timed out, perhaps because of a lack of system resources.  
1. Follow the recommendations for ABORT code 2035.  
Could not establish test call.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-757  
Table 3-318. TEST #258 ISDN TEST Call — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2067  
ABORT  
ABORT  
The call has timed out, perhaps because of a lack of system resources.  
1. Follow the recommendations for ABORT code 2035.  
Bit and Block Error query failed.  
2074  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort, there may be a serious internal problem  
with Maintenance/Test Digital Port.  
2075  
2100  
2104  
ABORT  
ABORT  
ABORT  
Internal system error  
1. Follow the recommendations for ABORT code 2012.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Call dropped or could not be originated.  
1. Make sure service is provisioned by the network.  
2. Check the administration of the far-end test line extension on the trunk  
group administration form.  
3. Check the administration of the test call BCC (Bearer Capability Class)  
on the trunk group administration form.  
4. Check the reason for termination with status isdn-testcall.  
5. For further instructions see "Troubleshooting ISDN-PRI Test Call  
Problems" in Chapter 5, "Routine Maintenance Procedures".  
6. Try the test again.  
2201  
2202  
2203  
2204  
2205  
ABORT  
Internal system error  
1. Follow the recommendations for ABORT code 2012.  
2206  
ABORT  
ABORT  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Follow the recommendations for ABORT code 2100.  
Internal system error  
2208  
1. Follow the recommendations for ABORT code 2012.  
Could not allocate the necessary system resources to run this test.  
1. Follow the recommendations for ABORT code 2100.  
Internal system error  
2209  
2210  
2211  
1. Follow the recommendations for ABORT code 2012.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-758  
Table 3-318. TEST #258 ISDN TEST Call — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Call terminated by unexpected disconnect.  
1. Wait 1 minute and then try again.  
2212  
ABORT  
ABORT  
ABORT  
ABORT  
2213  
2214  
The call has timed-out, perhaps because of a lack of system resources.  
1. Follow the recommendations for ABORT code 2035.  
Call terminated by unexpected disconnect.  
1. Wait 1 minute and then try again.  
2215  
2216  
2217  
2218  
2219  
Internal system error  
1. Follow recommendations for ABORT code 2012.  
2220  
ABORT  
ABORT  
Call terminated prematurely.  
1. Wait 1 minute and try again.  
Internal system error  
2221  
2222  
2223  
2224  
2225  
2226  
1. Follow recommendations for ABORT code 2012.  
2227  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Follow the recommendations for ABORT code 2100.  
2042  
This is the main purpose of the test. The comparison of the data sent  
with the data received indicates a loss of integrity on the communications  
path.  
1. The trunk should be taken out-of-service and the quality of the DS1 line  
should be investigated. The investigation should include an in-depth  
analysis of the DS1 facility including the transmission facility and any  
external equipment such as DACs, CSUs, etc. If the test isdn-testcall  
command is invoked, then the investigation should include getting the  
bit and block error rates by invoking the status isdn-testcall  
command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
ISDN-TRK (DS1 ISDN Trunk)  
3-759  
Table 3-318. TEST #258 ISDN TEST Call — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The call worked. A test pattern was sent and received properly; the  
communications path is OK if the synchronous test call command was  
issued. If the test isdn-testcall command was issued, a PASS indicates  
that the test call was established. A status isdn-testcall command must be  
invoked to query the bit and block error rates to determine if the test call  
passed. An in-depth analysis of the DS1 facility including the transmission  
facility and any external equipment such as DACs, CSUs, etc., should take  
place if the bit and block error rates are not acceptable.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
LOG-SVN (Login Security Violation)  
3-760  
LOG-SVN (Login Security Violation)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
Full Name of MO  
LOG-SVN  
MAJOR  
enable login <login ID>  
Login Security Violation  
1. Where <login ID> is the services login ID for which the security violation was detected. The Alt  
Namefield indicates the login ID associated with the security violation and the major alarm.  
The Security Violation Notification (SVN) feature provides notification when the  
number of failed attempts to access the system administration/maintenance  
interface meets or exceeds customer administered threshold parameters.  
A major alarm is logged whenever a security violation is detected involving a  
services login ID and that login ID has been disabled as a result of the security  
violation. The capability to disable a login ID following detection of a security  
violation involving that login ID is administrable on a per login ID basis.  
Refer to DEFINITY Enterprise Communications System Administrator’s Guide for  
information on administration required for the Security Violation Notification  
feature and the option to disable a login ID following detection of a security  
violation involving the affected login ID.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-319. Hardware Error Log Entries and Test to Clear Value  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
None  
Test to Clear Value  
1-15  
None  
Major  
OFF  
enable login <login ID>  
General Information about log-svn Error Log  
Entries  
a. The number (1 - 15), that appears in the error type field, corresponds to  
the location the login in the internal login data structure.  
b. The Alt Namefield on the alarm report indicates the login ID associated  
with the security violation and major alarm.  
c. These errors/alarms are associated with a number of failed attempts to  
access the system management/maintenance interface using a services  
login ID that meet or exceed the customer administered threshold  
parameters. The associated alarm is immediately raised as a major alarm.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
LOG-SVN (Login Security Violation)  
3-761  
d. The affected login ID will be disabled as a result of detection of the  
security violation, unless it is the last enabled INADS type login on the  
system. The provision to disable a login ID following detection of a security  
violation involving that login ID is administrable on a login ID basis.  
e. The enable login command is used to both enable a login that has been  
disabled, and to retire any login security violation alarms associated with  
the login ID.  
f. Use of the enable login command to enable a login and/or retire alarms  
must be executed using a login ID with greater service level hierarchy  
permissions.  
g. Access to the enable login command is controlled through the  
Administer Permissionsfield on the Command Permission  
Categories form. This field (Administer Permissions) must be set to y to  
access the enable login command.  
h. The Portalarm report field will set to the port where the final invalid login  
attempt, involving the alarmed login ID, was detected. Valid port values for  
the CMC include:  
— MGR1 — Dedicated manager 1 or G3 management terminal  
connection  
— NET-n — Network controller dial up port  
— INADS — INADS port  
— EPN — EPN maintenance EIA port  
— EIA — Other EIA port  
i. The Svc Statealarm report field will be set to OUT if the login ID is in the  
disabled state as a result of detection of a security violation involving the  
login ID. Once the login ID has been enabled, the field is set to IN.  
j. The source or reason of the failed login attempts should be identified and  
the cause corrected prior to re-enabling a login ID and/or retiring any  
alarms associated with the login ID. The cause may be something as  
innocuous as the failure of the services automatic login software, to  
something as insidious as a hacker attempting to gain access to the  
switch system management interface.  
The login ID associated with that alarm is displayed in the Alt Namefield of the  
alarm report.  
Prior to retiring an SVN alarm and enabling the associated login ID, the monitor  
security-violations login command can be used to access information about  
the invalid login attempts that caused the security violation. This information can  
be useful in determining the source of the invalid attempts and analyzing why  
they occurred.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
LOG-SVN (Login Security Violation)  
3-762  
The list logins command provides status information about logins on the system.  
If a login has been disabled as a result of a security violation, the status will be  
svn-disabled.  
Procedure to Retire an SVN Alarm  
To retire a SVN alarm:  
1. Enter the command enable login <login ID>.  
The login ID associated with that alarm is displayed in the Alt Namefield  
of the alarm report and the alarm is retired.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
JNL-PRNT (Journal Printer Link)  
3-763  
JNL-PRNT (Journal Printer Link)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
PMS-PRNT/JNL-  
PRNT  
MINOR  
test journal pms-log/wakeup-log Journal Printer Link  
PMS-PRNT/JNL-  
PRNT  
WARNING  
test journal pms-log/wakeup-log Journal Printer Link  
NOTE:  
Since the maintenance strategy for both the JNL-PRNT (Journal Printer  
Link) and PMS-PRNT (PMS Printer Link) MO is the same, both of these MOs  
are described in the PMS-PRNT/JNL-PRNT Maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-764  
MAPD-BD (MAPD Interface Circuit  
Pack TN802)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board UUCSS sh  
test board UUCSS l  
Full Name of MO  
MAPD-BD  
MAPD-BD  
MAPD-BD  
MAJOR  
MAPD Interface Circuit Pack  
MAPD Interface Circuit Pack  
MAPD Interface Circuit Pack  
MINOR  
WARNING  
test board UUCSS sh  
1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation (A,  
B, C, D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21).  
The TN802 Multiple Application Platform for DEFINITY (MAPD) circuit pack  
allows sending voice and fax from DEFINITY ECS through the Internet to another  
DEFINITY also having this feature or to other PBXs that are equipped with the  
Internet Telephony Server (ITS-E).  
Throughout this section the term TN802 means the MAPD IP trunk circuit pack.  
Be sure to observe these special considerations for the TN802:  
■
■
■
Port alarms on this circuit pack display as “TIE-DS1” in the Alarm and  
Error logs.  
The reset board command reboots the MAPD PC CPU, but busyout  
board only busys out all of the emulated ports on the board.  
Switch resets that take the switch out of service for more than 20 seconds  
also cause the MAPD's PC to reboot, which takes several minutes to  
complete.  
Switch-demanded tests  
Switch-demanded diagnostic tests on the TN802 do not run unless the Internet  
trunking application is running on Windows NTTM, located on the circuit pack.  
Feature limitations  
The Internet trunking application relies on the single call scenario, or a direct,  
point-to-point call that does not terminate at multiple DEFINITY nodes through  
call processing. Table 3-320 describes the feature limitations for DEFINITY ECS.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-765  
Table 3-320. DEFINITY ECS IP trunk feature/performance limitations  
Feature/  
Performance  
Description  
Recommendation  
Abbreviated  
Dialing  
Abbreviated Dial strings with  
embedded pauses lose  
digits after the pause  
Most calls work. Do not create  
Abbreviated dial strings with  
embedded pauses.  
Compression  
limitations  
All IP trunk calls go through  
A/D conversion, which uses  
compression to reduce  
bandwidth. Each  
No more than 3  
compression/decompression  
cycles for any call.  
compression degrades the  
voice signal and creates call  
processing delay.  
NOTE:  
The compression/  
decompression that most  
voice mail systems use must  
be counted as 1 cycle.  
Call Classifier  
IP trunk’s compression/  
decompression cycle makes  
ringback, busy and voice  
detection  
Do not administer these features:  
■ Call Coverage Redirected  
Off-Net (CCRON)  
■ Certain wireless phone  
coverage  
Call Coverage  
Call Forwarding  
Call Transfer  
Calls extended across  
Multiple call paths not  
recommended  
multiple DEFINITY ECS  
nodes require multiple call  
paths. Significant voice  
quality degradation is likely.  
Conferencing  
Voice quality and delay  
problems if the party  
controlling the conference is  
on the IP trunk (voice paths  
from external callers come in  
on the IP trunk, are  
Avoid conference calls where at  
least two other parties are on the  
other side of the IP trunk.  
NOTE:  
The following conferences  
conferenced, then sent out to  
other external parties across  
an IP trunk)  
work OK:  
■
■
Conferences of parties on  
the local DEFINITY ECS  
Conferences controlled by  
the local DEFINITY ECS,  
involving local parties and  
only 1 party on the other  
side of an IP trunk  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-766  
Table 3-320. DEFINITY ECS IP trunk feature/performance limitations — Continued  
Feature/  
Performance  
Description  
Recommendation  
DCS  
Know limitations:  
■ Auto Callback  
Coordinate specific administration  
and between the IP trunk and  
DEFINITY ECS for any DCS  
functionality. Some limitations on  
routing flexibility may apply.  
ISDN  
IP trunking has no signalling  
capability.  
ISDN not supported. This includes:  
■ 10-digit number display  
■ QSIG  
■ Path replacement  
Voice mail  
Calls that have terminated at  
one location and then cover  
to a second site for voice  
mail coverage can have  
voice quality degradation.  
Centralized voice mail through an  
IP network is not recommended.  
Backing up to the PCMCIA disk  
Table 3-321 details how to back up administration data for the IP trunk  
application to and restored from the local PCMCIA disk and the Ethernet port.  
Before backing up, be sure to shut down the application running on the circuit  
pack, following the procedures in the ‘‘Shutting down NT on the TN802’’ section.  
Table 3-321. Backing up TN802 administration data  
Step Description  
Comments  
1.  
Busyout circuit pack  
At the DEFINITY ECS terminal type busyout  
board UUCSS (the address of the TN802 circuit  
pack) and press Enter.  
2.  
Backup administration  
TN802 to disk  
At the Windows NT desktop, double-click on the  
IP Trunk Backup Restore icon.  
The IP Trunk Backup/Restore Utility screen  
appears.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-767  
Table 3-321. Backing up TN802 administration data — Continued  
Step Description  
Comments  
3.  
Select utility  
In the IP Trunk Backup/Restore Utility dialog  
screen, click on Files, Backup.  
The IP Trunk Backup screen appears.  
4.  
5.  
6.  
Select backup  
Wait  
In the IP Trunk Backup screen, click on the  
Backup button  
Backup can take as much as 20 minutes to  
complete.  
Release circuit pack  
At the DEFINITY ECS terminal type release board  
UUCss (the address of the TN802 circuit pack)  
and press Enter.  
NOTE:  
Local restore of a complete system from the PCMCIA disk should not  
require more than 20 minutes assuming that a replacement MAPD pack is  
available and pre-loaded with the IP trunk application software.  
Restoring data from the PCMCIA disk  
Before you start  
1. Shut down the application running on the circuit pack. See ‘‘Shutting down  
NT on the TN802’’.  
2. Remove the defective IP Trunk circuit pack from the switch (if applicable).  
3. Install the replacement IP Trunk circuit pack in the switch (if applicable).  
4. Insert the backup diskette into the IP Trunk circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-768  
Table 3-322. Restore TN802 administration data  
Step Description  
Comments  
1.  
Restore IP Trunk  
administration  
At the Windows NT desktop, double-click on the  
IP Trunk Back UP Restore icon.  
The IP Trunk Backup/Restore Utility screen  
appears.  
2.  
Select utility  
In the IP Trunk Backup/Restore Utility dialog  
screen, click Files, Restore.  
The IP Trunk Backup screen appears  
3.  
4.  
Select restore  
Wait  
In the IP Trunk Backup screen, click on the  
Restore button.  
Wait until the yellow Disk-In-Use LED (Note 5 in  
Figure 3-29) light is out.  
PSTN fallback feature  
The Public Switched Telephone Network (PSTN) fallback feature is available on  
the Internet trunk application software, which periodically pings the remote  
destinations that the software calls. When the far end returns a poor response  
time to the ping, DEFINITY’s ARS or AAR network routing patterns bypass those  
ports and direct the call to another port, typically on a PSTN trunk.  
When the remote destinations show acceptable response times to subsequent  
pings, the corresponding ports are returned to “idle,” where they are available for  
service.  
Cabinet configuration  
Because of overheating, the TN802 circuit pack should not be placed directly  
above or below another MAPD circuit pack.  
UPS protection  
Because Windows NT is more vulnerable to damage from a power interruption  
than the DEFINITY ECS, uninterrupted power supply (UPS) protection is strongly  
recommended for systems using the TN802 circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-769  
Faceplate  
Figure 3-29 shows the TN802 faceplate.  
1
2
3
4
5
fpdfmapd KLC 030899  
Figure Notes:  
1. LCD display (see Table 3-323)  
2. Reset button (recessed)  
3. Red board status LED  
4. PCMCIA card slot  
5. Yellow PCMCIA disk-in-use LED  
Figure 3-29. TN802 faceplate  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-770  
Table 3-323 lists the TN802 LCD messages that you might see if installing or  
servicing an IP Trunk.  
Table 3-323. TN802 LCD messages for IP trunks  
Display  
Explanation  
PC BOOT  
IP TRK #  
IML DWN #  
The TN802 MAPD PC is booting up.  
IP Trunk application is running (# character blinks)  
Internal error on the IP Trunk. System shuts down  
and sends and error message to the board.  
MSHUT # where  
both MSHUT and #  
are blinking  
The system is in the process of shutting down due to  
a front panel button press. DO NOT attempt to  
remove board.  
MSHUT #, where #  
is blinking  
The system has shut down gracefully.  
Support for laptop PCs  
Field technicians can access the TN802 circuit pack through:  
1. ‘‘pcANYWHERE® client software’’  
2. ‘‘Directly-connected keyboard, monitor, and mouse’’  
®
pcANYWHERE client software  
1. Attach a male-to-male serial cable and a NULL modem connector  
(if not built into the cable you use) to the COM2 connector (Note 8  
in Figure 3-30) Attach the other end to the serial port of your laptop.  
2. Launch the pcANYWHERE® application.  
3. Click on Add Remote Control Item.  
4. In the Properties window, choose the communication port to which  
you connected the cable in Step 1.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-771  
5. Click on Details and configure the settings (Table 3-324):  
Table 3-324. Remote connection settings  
Field  
Value  
Speed  
38,400  
Parity  
None (default)  
RTS/CTS  
Flow Control  
Started by  
Ended by  
Carrier detect (DCD)  
Carrier detect (DCD)  
6. Click on the new item icon and the laptop connects to the host  
pcANYWHERE® application on the TN802 circuit pack.  
1
8
7
6
5
4
3
2
cbdfocto AWF 122398  
Figure Notes:  
1. To TN802 cabinet backplane  
2. VGA monitor  
5. Mouse  
6. Ethernet  
3. USB (Universal Serial Bus)  
4. Keyboard  
7. 25-pin modem connection  
8. 25-pin COM2 connection  
Figure 3-30. TN802 external cable assembly  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-772  
Directly-connected keyboard, monitor, and  
mouse  
NOTE:  
You need 2 power sources for the monitor and the modem in order to  
complete this procedure.  
NOTE:  
The TN802 circuit pack must be booted with a local mouse and  
keyboard connected to it for these devices to work.  
1. Connect the VGA monitor to the VGA connector of the TN802  
external cable.  
2. Plug the monitor into an AC power receptacle, and turn it on.  
3. Attach the keyboard to the keyboard connector of the TN802  
external cable assembly.  
4. Attach the mouse to the mouse connector of the TN802 external  
cable assembly.  
5. Insert the circuit pack to cause it to boot.  
Troubleshooting LAN connections  
This section contains information for troubleshooting  
■
‘‘External connections to the LAN’’  
‘‘Internal connections to the LAN’’  
■
External connections to the LAN  
Test the external connections to the LAN by pinging the  
local host  
external IP trunk server  
another device connected to the network:  
■
■
■
1. Click Start in Windows (lower lefthand corner), then select Programs, then  
Command Prompt.  
This starts a DOS command line session.  
2. At the command prompt, type ping 127.0.0.1 (the local host default  
address) and press Enter.  
If configured correctly, the system displays:  
Reply from nnn.nn.nn.nn: bytes=32 time <##ms TTL=###  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-773  
If there is no reply:  
a. Escalate the problem or replace the circuit pack. The problem is  
not with the external network but within the circuit pack.  
3. At the command prompt, type ping nnn.nn.nn.nn (the external IP trunk  
server address) and press Enter.  
If configured correctly, the system displays:  
Reply from nnn.nn.nn.nn: bytes=32 time <##ms TTL=###  
If there is no reply, verify the IP address and check the physical  
connections to and from the TN802 circuit pack.  
4. At the command prompt, type ping nnn.nn.nn.nn (the IP address of  
another computer on the network) and press Enter.  
If configured correctly, the system displays:  
Reply from nnn.nn.nn.nn: bytes=32 time <##ms TTL=###  
If there is no reply  
a. Verify the IP address  
b. Check the physical connections to and from the TN802 circuit  
pack.  
c. Check the internal cables on the TN802 circuit pack (Notes 4 and 6  
in Figure 3-32).  
d. Try pinging another device on the same subnet.  
e. Try pinging the gateway to the rest of the network from the subnet.  
f. Try pinging a device not on the local subnet but on the network or  
another subnet.  
5. When finished, at the command prompt type exit and press Enter.  
Internal connections to the LAN  
Test the internal connections to the LAN by pinging the  
local host  
internal IP trunk server  
another device connected to the network:  
■
■
■
1. Click Start in Windows (lower lefthand corner), then select Programs, then  
Command Prompt.  
This starts a DOS command line session.  
2. At the command prompt, type ping 127.0.0.1 (the local host default  
address) and press Enter.  
If configured correctly, the system displays:  
ReplyDofwrnolomad fnronmnW.wnwn..Sonmna.nnuanls:.cobmy. AtlleMsa=nu3a2ls SteiarmcheAn<d#D#omwnsloaTd.TL=###  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-774  
If there is no reply:  
a. Check that the internal cables on the TN802 circuit pack (Notes 4  
and 6 in Figure 3-32) have not worked loose.  
b. Otherwise, replace the circuit pack.  
3. At the command prompt, type ping 10.32.64.97 (the internal IP trunk  
server address) and press Enter.  
If configured correctly, the system displays:  
Reply from nnn.nn.nn.nn: bytes=32 time <##ms TTL=###  
If there is no reply:  
a. Check that the internal cables on the TN802 circuit pack (Notes 4  
and 6 in Figure 3-32) have not worked loose.  
b. Otherwise, replace the circuit pack.  
4. At the command prompt, type ping 10.32.64.96 (the IP address of the  
internal Motorola MPC860 processor) and press Enter.  
If configured correctly, the system displays:  
Reply from nnn.nn.nn.nn: bytes=32 time <##ms TTL=###  
If there is no reply:  
a. Check that the internal cables on the TN802 circuit pack (Notes 4  
and 6 in Figure 3-32) have not worked loose.  
b. Otherwise, replace the circuit pack.  
5. Ping the gateway: at the command prompt, type ping XX.XXX.XXX.XXX  
(the IP address of the gateway) and press Enter.  
6. When finished, at the command prompt type exit and press Enter.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-775  
Board assembly and cables  
Figure 3-31 shows the circuit pack with the two additional boards connected  
through the side plane.  
1
2
4
2
1
1
1
0
1
3
5
indfmap2 KLC 031699  
Figure Notes:  
1. Main TN802 board  
4. Side plane  
2. Texas Microsystems Inc. (TMI)  
board  
5. SCSA (Signal Computing System  
Architecture) ribbon cable  
3. Analogic board  
Figure 3-31. TN802 board assembly  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-776  
Figure 3-32 shows a side view of the thee boards and interconnecting cables that  
make up the TN802.  
1
3
2
5
6
4
cddfmap2 KLC 040699  
Figure Notes:  
1. Main TN802 board  
2. Side plane  
4. SCSA (Signal Computing System  
Architecture) ribbon cable  
5. Hard drive  
3. Analogic board  
6. Processor I/O ribbon cable  
Figure 3-32. TN802 board assembly and cables (side view)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-777  
Figure 3-33 shows the end view of the thee boards and interconnecting cables  
on the TN802.  
1
4
2
ckdfmap3 KLC 040699  
3
Figure Notes:  
1
1. Analogic board  
3. SIMMs (memory)  
2. Texas Microsystems Inc. (TMI)  
board  
4. SCSA (Signal Computing System  
Architecture) ribbon cable  
1. If the board is seated and you hear fast beeping, it means that one of the small boards  
containing the memory chips is dislodged. Secure the memory board firmly in the  
receptacle and reseat the circuit pack.  
Figure 3-33. TN802 board assembly and cables (end view)  
Replacing the hard disk  
The TN802 hard drive (Note 5 in Figure 3-32) is field-replaceable.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-778  
Table 3-325. Replacing the TN802 hard drive  
Step Description  
Comments  
1.  
Shut down NT  
Shut down Windows NT by either method  
described in the ‘‘Shutting down NT on the  
TN802’’ section.  
2.  
3.  
4.  
5.  
6.  
Remove the circuit pack  
Remove the hard drive  
Replace the hard drive  
Replace the circuit pack  
Wait for initialization  
Unlatch the circuit pack and remove it from  
the carrier.  
Remove the 2 screws and lift the hard drive  
out of its mounting bracket.  
Position the new hard drive in the mounting  
bracket and replace the 2 screws (Step 3).  
Slide the circuit pack into the slot and lock  
the latching lever.  
Wait for  
■ the circuit pack to reseat (faceplate  
LEDs light then go out  
■ Windows NT boots (PC BOOT displays  
on the faceplate LCD)  
■ IP Trunk application to run (IP TRK #  
displays on the faceplate LCD)  
Error Log Entries and Test to Clear Values  
Table 3-326. MAPD (TN802) Error Log entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
ON  
test board UUCSS  
1 (a)  
0
Circuit pack removed or  
SAKI Test (#53)  
MIN/  
WRN  
2
2 (b)  
18 (c)  
23 (d)  
125 (e)  
0
0
busyout board UUCSS  
WRN  
WRN  
OFF  
OFF  
ON  
release board UUCSS  
add ds1 UUCSS  
none 3 None  
MIN/  
WRN  
3
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-779  
Table 3-326. MAPD (TN802) Error Log entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
257  
65535  
Control Channel Loop  
Test (#52)  
MIN  
ON  
test board UUCSS l r 20  
257 (f)  
Any  
Any  
None  
513 (g)  
MIN/  
WRN  
ON  
ON  
ON  
ON  
3
3
3
3
514 (h)  
769 (i)  
770 (j)  
46086  
46085  
46096  
MIN/  
WRN  
MIN/  
WRN  
MIN/  
WRN  
1025 (d) 4363  
NPE Audit Test (#50)  
1281  
Any  
Loss of Signal Alarm  
Inquiry Test (#138)  
MIN/  
WRN  
OFF  
ON  
test board UUCSS  
3
3
3
1537 (k)  
1538 (l)  
1793  
46082  
Any  
MIN/  
WRN  
MIN/  
WRN  
ON  
Any  
Blue Alarm Inquiry Test  
(#139)  
MAJ/  
MIN/  
WRN  
OFF  
test board UUCSS  
4
2049  
2305  
2306  
2561  
2817  
Any  
Any  
Any  
Any  
Red Alarm Inquiry Test  
(#140)  
MIN/WR  
N
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
test board UUCSS  
test board UUCSS  
test Board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS r 6  
3
Yellow Alarm Inquiry Test  
(#141)  
MIN/  
WRN  
3
Yellow Alarm Inquiry Test  
(#141)  
MIN/  
WRN  
3
Major Alarm Inquiry Test  
(#142)  
MIN/  
WRN  
3
Minor Alarm Inquiry Test  
(#143)  
MIN/  
WRN  
3
3073 to  
3160  
(m)  
Any  
Slip Alarm Inquiry Test  
(#144)  
MIN/  
WRN  
3
3330 (n) 46083  
MIN/  
WRN  
ON  
3
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-780  
Table 3-326. MAPD (TN802) Error Log entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
3585 to  
3601 (o)  
Any  
Misframe Alarm Inquiry  
Test (#145)  
MIN/  
WRN  
OFF  
test board UUCSS r 6  
3
3840 (p) Any  
3841 (q) 4358  
None  
3842 (r)  
3843 (s)  
3999 (t)  
46097  
46081  
Any  
None  
Continued on next page  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. If ports are assigned to the circuit pack, then a minor alarm is raised. If no ports are assigned to  
the circuit pack, then a warning alarm is raised. The alarm is raised after the circuit pack has been  
missing for a period of 15 minutes. Warning alarms are also raised against any ports administered  
on the circuit pack.  
3. Minor alarms on this MO may be downgraded to warning alarms based on values set in the set  
options command.  
4. Major alarms on this MO may be downgraded to minor or warning alarms based on values set in  
the set options command.  
Notes:  
a. Error Type 1: indicates that the circuit pack has totally stopped functioning  
or is not fully administered. The alarm is logged about 15 minutes after the  
circuit pack has been removed or 11 minutes after the SAKI Test (#53)  
fails.  
To be fully administered, a MAPD circuit pack must meet all of these  
conditions:  
■
■
■
Have an entry in the circuit plan (change circuit pack)  
Be administered (add ds1 UUCSS)  
Be physically inserted into the correct slot  
If the circuit pack has an entry in the circuit plan and either of the other two  
conditions are not met, a MINOR alarm is logged. To resolve the error,  
either:  
1. Make sure the circuit pack is properly administered and that a  
functioning MAPD circuit pack is inserted in the correct slot, OR  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-781  
2. Completely remove the MAPD-BD from the system:  
a. Shut down NT (see ‘‘Shutting down NT on the TN802’’)  
b. Remove any administered DS1 trunks, access endpoints, or  
PRI endpoints associated with the circuit pack from their  
respective trunk groups.  
c. Remove the DS1 (remove ds1 UUCSS) and circuit pack  
(change circuit pack UUCSS) administration.  
If the circuit pack is properly administered and the red LED is still on,  
follow the instructions for LED Alarms with Error Type 1 in Chapter 7.  
b. Error Type 2: NT is down and the system attempts to reset the board. If the  
reset fails, the board is probably bad.  
1. Replace the circuit pack.  
c. Error Type 18: the circuit pack has been busied out.  
1. Release the board (release board UUCSS).  
d. Error Type 23 and 1025: the MAPD-BD circuit pack is not completely  
administered. In addition to insertion, the MAPD circuit pack must have all  
of the following administration:  
■
Have an entry in the circuit plan (change circuit pack)  
■
Be administered as DS1 (add ds1 UUCSS)  
The MAPD circuit pack differs from others in that inserting it into the switch  
backplane is not enough to make the board usable.  
e. Error Type 125, no Aux Data: A wrong circuit pack is inserted in the slot  
where this circuit pack is logically administered. To resolve this problem,  
either:  
1. Remove the wrong circuit pack and insert the logically  
administered circuit pack, OR  
2. Re-administer this slot (change circuit-pack) to match the circuit  
pack inserted.  
f. Error Type 257: this error is associated with the Common Port Circuit Pack  
Maintenance Test. Refer to XXX-BD (Common Port Circuit Pack)  
Maintenance documentation for details.  
g. Error Type 513: transient hardware problem.  
Aux Data:  
4352  
4353  
4355  
External RAM failure  
Internal RAM failure  
Internal ROM failure  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-782  
1. If the same Error Type/Aux Data value occurs more than once in a  
24 hour period, the circuit pack should be replaced. See ‘‘Shutting  
down NT on the TN802’’ before removing the circuit pack.  
If the MAPD board detects only one of these hardware problems, then the  
error is resolved when none of these faults are detected for 10 minutes.  
h. Error Type 514: LAN External RAM Error; hardware fault in the PPE  
external RAM, used for message buffering to and from the Packet Bus.  
This error should not occur regularly.  
1. If this error occurs 10 times within 30 minutes, replace the circuit  
pack. See ‘‘Shutting down NT on the TN802’’ before removing the  
circuit pack.  
i. Error Type 769: Transmit FIFO Underflow (threshold is 3 errors within 10  
minutes); the circuit pack cannot find the “end of frame” bit when  
transmitting a frame to Packet Bus.  
1. Clear the alarm using the following command sequence:  
a. busyout board UUCSS  
b. reset board UUCSS  
c. test board UUCSS long clear  
d. release board UUCSS  
2. If the error recurs within 10 minutes, replace the circuit pack. See  
‘‘Shutting down NT on the TN802’’ before removing the circuit pack.  
j. Error Type 770: unable to Write LAN Translation RAM (threshold is 2 errors  
within 10 minutes); a call is aborted because there are no available  
translation RAM locations for the call connection attempt.  
1. Clear the alarm using the following command sequence:  
a. busyout board UUCSS  
b. reset board UUCSS  
c. test board UUCSS long clear  
d. release board UUCSS  
2. If the error recurs within 10 minutes, replace the circuit pack. See  
‘‘Shutting down NT on the TN802’’ before removing the circuit pack.  
k. Error Type 1537: LAN Bus Timeout; the circuit pack transmitted too many  
bytes on the LAN bus for a single frame. This condition may be caused by:  
■
an on-board fault  
■
faulty data received on one of the circuit pack’s external ports. If  
any of the ports on this circuit pack are alarmed, refer to the repair  
procedures for those maintenance objects.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-783  
If the error occurs 3 times within 10 minutes, the system raises the board  
alarm and isolates it from the Packet Bus.  
1. Clear the alarm and restore the board to the Packet Bus using the  
following command sequence:  
a. busyout board UUCSS  
b. reset board UUCSS  
c. test board UUCSS long clear  
d. release board UUCSS  
2. If the problem persists, and there are no PKT-BUS alarms or port  
alarms, then replace the circuit pack. See ‘‘Shutting down NT on the  
TN802’’ before removing the circuit pack.  
l. Error Type 1538: hyperactive circuit pack is out-of-service and may exhibit  
one or more of the following symptoms:  
■
The common circuit pack tests (for example, Test #50 and/or Test  
#52) abort with Error Code 2000.  
■
■
■
Port tests on this circuit pack return NO-BOARD.  
A busyout/release of the circuit pack has no affect on test results.  
A list configuration command shows that the circuit pack and  
ports are properly installed.  
The circuit pack is isolated from the system and all trunks or ports on this  
circuit pack are placed into the out-of-service state. The system attempts  
to restore the circuit pack within 20-30 minutes. When no faults are  
detected for 20-30 minutes, the MAPD Interface circuit pack is restored to  
normal operation and all trunks or ports on the MAPD Interface circuit  
pack return to the in-service state.  
1. If the board is not restored to normal operation, or the error recurs  
after the board is restored to normal operation, escalate the  
problem.  
m. Error Type 3073 - 3160: board is reporting slip errors. Aux Data shows the  
last reported slip count.  
n. Error Type 3330: LAN Critical error; critical failure in the Packet Bus  
interface to the circuit pack. This failure may be due to an on-board or a  
Packet Bus fault.  
1. If the Packet Bus is alarmed, refer to the PKT-BUS Maintenance  
documentation for recommended repair procedures.  
2. If the Packet Bus is not alarmed, clear the alarm and restore the  
board to the Packet Bus using the following command sequence:  
a. busyout board UUCSS  
b. reset board UUCSS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-784  
c. test board UUCSS clear  
d. release board UUCSS  
3. If the problem persists, and there are no PKT-BUS alarms, then  
replace the circuit pack. See ‘‘Shutting down NT on the TN802’’  
before removing the circuit pack.  
o. Error Type 3585 - 3601: the board received misframe errors; the Aux Data  
shows the last reported misframe count.  
p. Error Type 3840: the circuit pack received a bad control channel message  
from the switch. This error is not service-affecting, and requires no action.  
The Aux Data describes the following error events:  
4096  
4097  
4098  
4099  
4100  
4101  
Bad major heading  
Bad port number  
Bad data  
Bad sub-qualifier  
State inconsistency  
Bad logical link  
q. Error Type 3841: the circuit pack detected a transient hardware logic error  
(for example, program logic inconsistency). This error resolves when no  
faults are detected for 100 minutes. The value in Aux Data field (4358)  
indicates the type of hardware problem.  
r. Error Type 3842: Bad Translation RAM Location Found error; the call  
continues by using another translation location. This error is not  
service-affecting and requires no action.  
s. Error Type 3843: LAN Receive Parity error; the circuit pack detected an  
error in a received frame from the Packet Bus. These errors are most likely  
caused by a Packet Bus problem, but may be due to a circuit pack fault.  
1. Determine whether the problem is isolated to this circuit pack or if  
the problem is caused by Packet Bus faults (see PKT-BUS).  
t. Error Type 3999: the circuit pack sent a large number of control channel  
messages to the switch within a short period of time.  
Error Type 1538  
(hyperactivity)  
also present?  
Then the switch:  
Y
N
Takes the circuit pack out-of-service due to hyperactivity  
Does not take the circuit pack out-of-service, but the  
circuit pack has generated 50% of the messages  
necessary to be considered hyperactive. This may be  
normal during heavy traffic periods.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-785  
Shutting down NT on the TN802  
Before removing the TN802 circuit pack from the carrier, shut Windows NTTM  
down first by following either procedure described in Table 3-327:  
Table 3-327. Windows NT shutdown procedures  
Step  
Faceplate button  
PC interface  
1.  
Push the recessed button on the front  
faceplate and hold it in.  
Click on the “Start” button in the lower, lefthand  
corner.  
2.  
3.  
“M shut” flashes on the LCD display  
Click on “Shut Down.”  
When shutdown is complete, “MSHUT Choose the “Shut down the computer?” radio  
#” displays (“#” is blinking).  
button.  
4.  
5.  
Remove the circuit pack.  
Click on “OK.”  
Wait for the message indicating that shutdown  
is complete.  
6.  
Remove the circuit pack.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Investigate tests in the order they are presented in Table 3-328. By clearing error  
codes associated with the NPE Connection Audit Test, for example, you may also  
clear errors generated from other tests in the testing sequence.  
Table 3-328. System Technician-Demanded Tests  
Short  
Test  
Reset  
Board  
Apply to  
TN802?  
LongTest  
1
2
Order of Investigation  
NPE Connection Audit Test (#50)  
Control Channel Loop Test (#52)  
Sequence Sequence Sequence D/ND  
Y
Y
N
X
X
X
ND  
ND  
ND  
Loss of Signal Alarm Inquiry Test  
(#138)  
X
Blue Alarm Inquiry Test (#139)  
Red Alarm Inquiry Test (#140)  
Yellow Alarm Inquiry Test (#141)  
N
N
N
X
X
X
X
X
X
ND  
ND  
ND  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-786  
Table 3-328. System Technician-Demanded Tests — Continued  
Short  
Test  
Reset  
Board  
Apply to  
TN802?  
LongTest  
1
2
Order of Investigation  
Major Alarm Inquiry Test (#142)  
Minor Alarm Inquiry Test (#143)  
Slip Alarm Inquiry Test (#144)  
Misframe Alarm Inquiry Test (#145)  
Translation Update Test (#146)  
SAKI Sanity Test (#53)  
Sequence Sequence Sequence D/ND  
N
N
N
N
N
Y
X
X
X
X
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
D
X
1. N = No; this test either passes or ABORTS with Error Code 2000 (problem with NT)  
2. D = Destructive; ND = Nondestructive  
NPE Connection Audit Test (#50)  
The system sends a message to the on-board microprocessor to update the  
network connectivity translation for the SCOTCH-NPE chip on the circuit pack.  
Table 3-329. TEST #50 NPE Connection Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test aborted because a test was already running on the port.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Internal system error  
None  
2100  
ABORT  
ABORT  
FAIL  
1019  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-787  
Table 3-329. TEST #50 NPE Connection Audit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The circuit pack’s SCOTCH-NPE chip has been updated with its translation.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the MAPD interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board  
is shut down. Reseating the board re-initializes the board.  
3. If the board was found to be correctly inserted in Step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Control Channel Looparound Test (#52)  
This test queries the circuit pack for its circuit pack code and vintage and verifies  
its records.  
Table 3-330. TEST #52 Control Channel Looparound Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The circuit pack failed to return the circuit pack code or vintage.  
1. Retry the command a maximum of 5 times.  
None  
2100  
ABORT  
FAIL  
2. If the problem continues, and if the circuit pack is one of the Port circuit  
packs, replace the circuit pack.  
3. Otherwise, if the circuit pack is part of the SPE, use the procedure  
described in Replacing SPE Circuit Packs in Chapter 5.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-788  
Table 3-330. TEST #52 Control Channel Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
Communication with this circuit pack is successful.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the MAPD interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the  
board is shut down. Reseating the board re-initializes the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
SAKI Sanity Test (#53)  
This test is destructive.  
This test resets the circuit pack. The test is highly destructive and can only be  
initiated by a system technician-demanded reset board UUCSS command.  
Table 3-331. TEST #53 SAKI Sanity Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
None  
ABORT  
System resources required for this test are not available.  
1. Retry the reset board command at 1-minute intervals a maximum of 5  
times.  
1015  
ABORT  
Port is not out-of-service.  
1. Busyout the circuit pack (busyout board UUCSS).  
2. Execute the reset board command again.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-789  
Table 3-331. TEST #53 SAKI Sanity Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2100  
ABORT  
System resources required for this test are not available.  
1. Retry the reset board command at 1-minute intervals a maximum of 5  
times.  
1
2
FAIL  
FAIL  
The circuit pack failed to reset.  
The circuit pack failed to restart.  
1. Execute the reset board command again.  
2. If the problem persists, replace the circuit pack.  
The circuit pack initializes correctly.  
1. Run the Short Test Sequence.  
PASS  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the MAPD interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board  
is shut down. Reseating the board re-initializes the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-790  
Loss of Signal Alarm Inquiry Test (#138)  
This test is meaningless for the TN802 MAPD circuit pack. Table 3-332 details the  
test results.  
Table 3-332. Loss of Signal Inquiry Test (#138) results  
Windows NT  
up on the  
TN802?  
Then  
Cause  
Y
Test passes  
Y
Test aborts with ABORT  
2000 Error Code.  
Windows NT is not communicating  
with the angel firmware.  
N
Test aborts with ABORT  
2000 Error Code.  
Windows NT down.  
Blue Alarm Inquiry Test (#139)  
This test is meaningless for the TN802 MAPD circuit pack. Table 3-333 details the  
test results.  
Table 3-333. Blue Alarm Inquiry Test (#139) results  
Windows NT  
up on the  
TN802?  
Then  
Cause  
Y
Test passes  
Y
Test aborts with ABORT  
2000 Error Code.  
Windows NT is not communicating  
with the angel firmware.  
N
Test aborts with ABORT  
2000 Error Code.  
Windows NT down.  
Red Alarm Inquiry Test (#140)  
This test is meaningless for the TN802 MAPD circuit pack. Table 3-334 details the  
test results.  
Table 3-334. Red Alarm Inquiry Test (#140) results  
If Windows NT is up  
on the TN802  
When the switch confirms Red alarm:  
Test passes  
Y
N
Test aborts with ABORT 2000 Error Code.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-791  
Yellow Alarm Inquiry Test (#141)  
This test is meaningless for the TN802 MAPD circuit pack. Table 3-335 details the  
test results.  
Table 3-335. Yellow Alarm Inquiry Test (#141) results  
If Windows NT is up  
on the TN802  
When the switch confirms Yellow alarm:  
Test passes  
Y
N
Test aborts with ABORT 2000 Error Code.  
Major Alarm Inquiry Test (#142)  
This test is meaningless for the TN802 MAPD circuit pack. Table 3-336 details the  
test results.  
Table 3-336. Major Alarm Inquiry Test (#142) results  
If Windows NT is up  
on the TN802  
When the switch confirms Major alarm:  
Test passes  
Y
N
Test aborts with ABORT 2000 Error Code.  
Minor Alarm Inquiry Test (#143)  
This test is meaningless for the TN802 MAPD circuit pack. Table 3-337 details the  
test results.  
Table 3-337. Minor Alarm Inquiry Test (#142) results  
If Windows NT is up  
on the TN802  
When the switch confirms Minor alarm:  
Test passes  
Y
N
Test aborts with ABORT 2000 Error Code.  
Slip Alarm Inquiry Test (#144)  
This test is meaningless for the TN802 MAPD circuit pack. Table 3-338 details the  
test results.  
NOTE:  
The query for slips always returns a 0 count.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-792  
Table 3-338. Slip Alarm Inquiry Test (#144) results  
If Windows NT is up  
on the TN802  
When the switch confirms Slip alarm:  
Y
N
Test passes  
Test aborts with ABORT 2000 Error Code.  
Misframe Alarm Inquiry Test (#145)  
This test is meaningless for the TN802 MAPD circuit pack. Table 3-339 details the  
test results.  
NOTE:  
The query for misframes always returns a 0 count.  
Table 3-339. Misframe Alarm Inquiry Test (#145) results  
If Windows NT is up  
on the TN802  
When the switch confirms Misframe alarm:  
Y
N
Test passes  
Test aborts with ABORT 2000 Error Code.  
Translation Update Test (#146)  
The Translation Update Test sends the circuit-pack-level information to the MAPD  
Interface circuit pack. Translation includes the following data administered for a  
MAPD Interface circuit pack (report from display ds1 UUCSS command):  
■
■
■
■
■
■
■
DS1 Link Length between two DS1 endpoints  
Synchronization Source Control  
All Zero Suppression  
Framing Mode  
Signaling Mode  
Time Slot Number of the 697-Hz tone  
Time Slot Number of the 700-Hz tone  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MAPD-BD (MAPD Interface Circuit Pack TN802)  
3-793  
Table 3-340. TEST #146 Translation Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
FAIL  
Internal system error  
1. Retry the command at 1-minute interval s a maximum of 5 times.  
Internal system software error.  
1. Verify the MAPD Interface circuit pack translation (display ds1 UUCSS).  
PASS  
Translation data has been downloaded to the MAPD Interface circuit pack  
successfully.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the MAPD interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the  
board is shut down. Reseating the board re-initializes the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-794  
MEDPRO (Media Processor MAPD  
Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board UUCSS sh  
test board UUCSS l  
Full Name of MO  
MEDPRO  
MEDPRO  
MEDPRO  
MAJOR  
MINOR  
Media Processor MAPD Circuit Pack  
Media Processor MAPD Circuit Pack  
Media Processor MAPD Circuit Pack  
WARNING  
test board UUCSS sh  
1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation (A,  
B, C, D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21).  
The TN802B MedPro circuit board is used by the DOLAN (Definity on the LAN)  
feature to provide voice over IP connectivity. The TN802B can run either:  
■
R8.1 IP Trunk application — allows the TN802B to emulate a DS1 circuit  
pack. In this mode, the circuit pack is maintained as a standard DS1  
board with its associated Tie trunk ports. The TN802B operates as an  
integrated Internet Telephony Server. It communicates with other ITS  
boxes or IP trunk boards.  
■
the Media Processor (MedPro) application — allows the TN802B to act as  
a service circuit to terminate generic RTP streams used to carry  
packetized audio over an IP network. As part of the overall H.323  
implementation, the TN802B or later circuit pack handles the audio  
streams while the TN799 C-LAN handles the TCP/IP signaling channels.  
This maintenance plan applies only to a TN802B MedPro running the  
Media Processor application.  
The MedPro hardware combines an angel complex, a Windows NT PC and a  
TAP802 DSP card in a 3-slot package. When operating as an IP trunk circuit  
pack, the MedPro emulates a DS1 Tie Trunk circuit pack and blindly responds to  
DS1 trunk maintenance requests. Actual maintenance is accomplished via the  
windows NT interface and the ITS software diagnostics.  
The Media Processor application is built upon the existing ITS software, and as  
such is not administered in DEFINITY as a DS1 trunk, and does not emulate a  
DS1 for maintenance purposes. Use the following Maintenance procedures for  
this application.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-795  
Error Log Entries and Test to Clear Values  
Table 3-341. DS1 Interface Circuit Pack Maintenance Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1
0
0
0
Any  
Any  
Any  
ON  
test board UUCSS  
2
1(a)  
Circuit pack removed or  
SAKI Test (#53)  
MIN/WRN  
18(b)  
0
busyout board UUCSS  
WARNING  
WARNING  
OFF  
OFF  
ON  
release board UUCSS  
add ds1 UUCSS  
23(c)  
0
3
125(d)  
257(e)  
None  
None  
MIN/WRN  
MINOR  
65535 Control Channel Loop Test  
(#52)  
ON  
test board UUCSS l r 2  
257(e)  
1538  
Any  
Any  
Any  
Any  
Any  
Any  
None  
3
3
3
Hyper activity  
NIC Los Of Signal  
NT PC Failure  
IP Address Inconsistency  
Ping Error  
MIN/WRN  
MIN/WRN  
MIN/WRN  
ON  
1793  
test board UUCSS l r 2  
reset board UUCSS  
2049(f)  
2305  
test board UUCSS l r 2  
test board UUCSS l r 5  
3
2561  
MIN/WRN  
Log Only  
3841(g) 4358  
3999(h) Any  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. If ports are assigned to the circuit pack, then a minor alarm is raised. If no ports are assigned to  
the circuit pack, then a warning alarm is raised. The alarm is raised after the circuit pack has been  
missing for a period of 15 minutes. Warning alarms are also raised against any ports administered  
on the circuit pack.  
3. Minor alarms on this MO may be downgraded to warning alarms based on values set in the set  
options command.  
Notes:  
a. Error Type 1 -This error indicates that the circuit pack has totally stopped  
functioning or is not fully administered. The alarm is logged about 15  
minutes after the circuit pack has been removed or 11-minutes after the  
SAKI Test (#53) fails.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-796  
To be fully administered, a MedPro circuit pack must meet all of these 4  
conditions:  
1. Have an entry in the circuit pack form (change circuit pack)  
2. Have the MedPro ip address administered (change node-names)  
3. Be enabled (change ip-interface)  
4. Be physically inserted into the correct slot  
If the circuit pack has an entry in the circuit packform and either of the  
other two conditions are not met, a MINOR alarm is logged. To resolve the  
error either  
1. Make sure all conditions for administration are met and that a  
functioning MedPro circuit pack is inserted in the correct slot  
OR  
2. Completely remove the MedPro from the system using the following  
steps:  
a. Remove the administered IP-Interface associated with the  
circuit pack.  
b. Physically remove the circuit pack from the slot.  
c. Execute the remove medpro UUCSS and change circuit  
pack UUCSS commands.  
b. ErrorType 18 -The MedPro Interface circuit pack has been busied out by  
a busyout board UUCSS command.  
1. Release the circuit pack (release board UUCSS).  
c. Error Type 23 -The MedPro circuit pack is not completely administered.  
To be fully administered, a MedPro circuit pack must meet all of these 4  
conditions:  
1. Have an entry in the circuit plan (change circuit pack)  
2. Have the MedPro IP address administered (change node-names)  
3. Be enabled (change ip-interface)  
4. Be physically inserted into the correct slot.  
A DS1 (MEDPRO, MAPD, UDS1-BD and DS1-BD) differs from most circuit  
packs in that inserting the circuit pack into the switch is not enough to  
make the board usable. It must also be administered.  
d. Error Type 125 - no Aux Data: The wrong circuit pack is inserted in the  
slot where this circuit pack is logically administered.  
1. Remove the wrong circuit pack and insert the logically  
administered circuit pack  
OR  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-797  
2. Re-administer this slot to match the circuit pack inserted (change  
circuit-pack).  
e. Error Type 257 - this error is associated with the Common Port Circuit  
Pack Maintenance Test. Refer to XXX-BD (Common Port Circuit Pack)  
Maintenance documentation for details.  
f. Error Type 2049 - This error indicates that the operating system is down;  
an attempt is made to reset the board automatically. If the reset fails, the  
board is probably bad and should be replaced.  
g. Error Type 3841 - inconsistent downlink message. This error is not  
service-affecting. No action is required.  
h. Error Type 3999 - indicates that the circuit pack sent a large number of  
control channel messages to the switch within a short period of time. If  
Error Type 1538 is also present, then the circuit pack was taken  
out-of-service due to hyperactivity. If Error Type 1538 is not present, then  
the circuit pack has not been taken out-of-service, but it has generated  
50% of the messages necessary to be considered hyperactive. This may  
be completely normal during heavy traffic periods. However, if this error  
type is logged when the circuit pack is being lightly used, it may indicate a  
problem with the circuit pack or the equipment attached to it.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-798  
System Technician-Demanded Tests:  
Descriptions and Error Codes  
Investigate tests in the order they are presented in Table 3-328. By clearing error  
codes associated with the Control Channel Loop Test, for example, you may also  
clear errors generated from other tests in the testing sequence.  
Table 3-342. System Technician-Demanded Tests  
Short  
Test  
Reset  
LongTest Board  
1
Order of Investigation  
Control Channel Loop Test (#52)  
SAKI Sanity Test (#53)  
IP Address Query (#1371)  
NIC Query Test (#1383)  
PING Test (#1379)  
Sequence Sequence Sequence D/ND  
X
ND  
D
X
X
X
X
X
X
X
D
ND  
ND  
D
NT Reset Test (#1381)  
X
1. D = Destructive; ND = Nondestructive  
Control Channel Looparound Test (#52)  
This test queries the circuit pack for its circuit pack code and vintage and verifies  
its records.  
Table 3-343. TEST #52 Control Channel Looparound Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
None  
2100  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-799  
Table 3-343. TEST #52 Control Channel Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
The circuit pack failed to return the circuit pack code or vintage.  
1. Retry the command a maximum of 5 times.  
2. If the problem continues, and if the circuit pack is one of the Port circuit  
packs, replace the circuit pack. Otherwise, if the circuit pack is part of  
the SPE, use the procedure described in Replacing SPE Circuit Packs in  
Chapter 5.  
3. Retry the command a maximum of 5 times.  
PASS  
Communication with this circuit pack is successful.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Administer the MedPro  
interface if it is not already administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the  
board is shut down. Reseating the board re-initializes the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board UUCSS command.  
4. Issue the reset board UUCSS command.  
5. Issue the release board UUCSS command.  
6. Issue the test board UUCSS long command.  
This should re-establish the linkage between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-800  
SAKI Sanity Test (#53)  
This is a destructive test.  
This test is only run as a part of a reset board procedure. For the Media  
Processor, it is necessary to use the change ip-interfaces form to disable the  
Media Processor IP interface before performing this reset board procedure.  
Other common circuit packs can be reset with the reset board UUCSS  
command which also executes this test.  
A reset of this circuit pack will take about 3 1/2 minutes.  
Table 3-344. TEST #53 SAKI Sanity Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Port is not out-of-service.  
None  
ABORT  
ABORT  
1015  
1. Busy out the circuit pack.  
2. Execute command again.  
2100  
2803  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
It is necessary to reset the board.  
1. Use the change ip-interfaces form to disable the Media Processor IP  
interface.  
2. Execute the command again.  
The circuit pack failed to reset.  
1
2
FAIL  
FAIL  
The circuit pack failed to restart.  
1. Execute command again.  
2. If the problem persists, replace the circuit pack.  
The circuit pack initializes correctly.  
1. Run the short test sequence.  
PASS  
Any  
NO  
BOARD  
This is normal if the test is being done when (a) the board is not physically in  
the system or (b) the system is booting up. Otherwise, there is some  
inconsistency between the physical configuration and the data kept in the  
system.  
1. Verify that the board is physically in the system.  
2. Verify that the system is not in a stage of booting up.  
3. Retry the command at 1-minute intervals for a maximum of 5 times.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-801  
IP Address Query Test #1371  
This test is destructive.  
The Media Processor has two interfaces for configuring the board, through the  
NT PC interface and the SAT via CCMS messages. For R8 DoLAN, the SAT and  
CCMS are the only approved interface. However, the NT PC interface cannot  
easily be disabled. It is possible that changes can be made via the NT PC  
interface that cause the Media Processor board to be inconsistent with DEFINITY  
translation. The area of concern is the IP address, subnet mask, and gateway  
translation.  
This test sends the Media processor the IP address, subnet mask, and gateway  
translation (IP parameters). If the parameters do not match DEFINITY translation,  
the new values are written into the Windows registry, and the NT PC asks the  
maintenance sub-system to reboot the board. The board goes through a physical  
board removal and insertion.  
When this test fails, it is an indication that an illegal change was made and the  
customer should be notified. Also, writing the IP address parameters to the  
registry requires NT to reboot. If the IP addresses match, there is no need to  
update the registry and reboot NT  
Table 3-345. TEST #1371 IP Address Query Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The IP address, subnet mask, and gateway translation parameters do not  
match DEFINITY translations. After the new values are written into the  
Windows registry, the NT PC must go through a reboot. The board goes  
through a physical board removal and insertion.  
1. If the problem persists, replace the circuit pack.  
Translation data matches the Windows Registry.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-802  
Ping Test (#1379)  
This test is non-destructive  
This test verifies that the MedPro circuit pack can communicate to other nodes  
on the LAN.  
This test pings the gateway IP address as defined on the IP Interface form.  
If the PING is successful, this test looks at the PING round trip delay. If a round  
trip delay of greater than 4 seconds is reported, a separate error is logged.  
Excessive round trip delays do not take the MedPro out of service.  
Services can execute the standard PING command using the C-LAN board  
address and MedPro IP address to see the actual round-trip delay. (See ping  
commands).  
This test is a nondestructive test. It runs due to in-line errors, during periodic and  
schedule maintenance, and on demand.  
Table 3-346. TEST #1379 Ping Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1, 2  
ABORT  
ABORT  
Internal Error.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
Destination unreachable.  
7
1. Verify that at least one destination reachable through this port is up.  
2. Repeat the test.  
3. If the test still aborts, escalate the problem.  
2000  
ABORT  
Response to the test was not received from the Media Processor circuit  
pack within the allowable time period.  
1. If this result occurs repeatedly, attempt to reset the circuit pack. Reset  
the circuit pack by issuing the busyout board UUCSS and the reset  
board UUCSS commands.  
2. If this result occurs again, replace the circuit pack.  
Internal system error.  
2012  
2100  
2500  
ABORT  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
The necessary system resources to execute the test could not be allocated.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-803  
Table 3-346. TEST #1379 Ping Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2801  
2802  
ABORT  
ABORT  
No IP address defined. Verify IP Interfaces translations and retest.  
Different IP address pinged than software had allocated for the test.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
2805  
FAIL  
FAIL  
The number of pings received did not match the number sent (normally one  
ping sent). This means that no ping responses were received from the  
gateway defined on the ip-interfaces form for the Media Processor.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
Ping to the destination failed through this port due to the destination down.  
1. Verify that at least one destination reachable through this port is up.  
7, 89,  
1007  
2. Once verified, execute test port UUCSSpp command to verify that the  
H.323 Signaling Group Ping Test (#1387) passes.  
PASS  
Ping through this port successful.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-804  
NT Reset Test (#1381)  
This test is destructive.  
This test resets the circuit pack. The test is highly destructive and can only be  
initiated by a system technician-demanded reset board UUCSS command.  
Table 3-347. TEST #1381 NT Reset Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
None  
ABORT  
System resources required for this test are not available.  
1. Retry the reset board UUCSS command at 1-minute intervals a  
maximum of 5 times.  
1015  
ABORT  
Port is not out-of-service.  
1. Busyout the circuit pack (busyout board UUCSS).  
2. Execute the reset board UUCSS command again.  
System resources required for this test are not available.  
2100  
ABORT  
1. Retry the reset board UUCSS command at 1-minute intervals a  
maximum of 5 times.  
1
2
FAIL  
FAIL  
The circuit pack failed to reset.  
The circuit pack failed to restart.  
1. Execute the reset board UUCSS command again.  
2. If the problem persists, replace the circuit pack.  
The circuit pack initializes correctly.  
1. Run the Short Test Sequence.  
PASS  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Administer the  
MEDPROMEDPRO interface if it is not already administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the  
board is shut down. Reseating the board re-initializes the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board UUCSS command.  
4. Issue the reset board UUCSS command.  
5. Issue the release board UUCSS command.  
6. Issue the test board UUCSS long command.  
This should re-establish the linkage between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPRO (Media Processor MAPD Circuit Pack)  
3-805  
NIC Query Test (#1383)  
This test is non-destructive.  
This test passes if the Ethernet port is connected and you can talk on the  
network. Otherwise it fails with no fail code or AUX data.  
Table 3-348. TEST #1383 NIC Query Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
None  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Port is not out-of-service.  
1015  
1. Busyout the circuit pack (busyout board UUCSS).  
2. Execute the command again.  
2100  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The Ethernet port is not connected and you cannot talk on the network.  
The Ethernet port is connected and you can talk on the network  
FAIL  
PASS  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Administer the MedPro  
interface if it is not already administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the  
board is shut down. Reseating the board re-initializes the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board UUCSS command.  
4. Issue the reset board UUCSS command.  
5. Issue the release board UUCSS command.  
6. Issue the test board UUCSS long command.  
This should re-establish the linkage between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPROPT (TN802 MED PRO DSP PORT)  
3-806  
MEDPROPT (TN802 MED PRO DSP  
PORT)  
MO Name (in  
Alarm Log)  
Initial Command to  
Run  
Alarm Level  
Full Name of MO  
TN802 MED PRO DSP PT  
MEDPROPT  
MINOR/WARNING  
test port UUCSS or  
PCSS [short/long]  
[repeat#] | [clear]  
The MEDPROPT maintenance object monitors the health of the MEDPRO digital  
signal processors (DSPs).  
The TN802B MAPD (Multi-Application Platform for DEFINITY) Media Processor  
circuit pack provides the audio bearer channels for H.323 voice over IP calls.  
One TN802B circuit pack has one MEDPROPT media processing resource.  
Based on system administration of audio codecs, a MEDPROPT can handle  
either 31 or 22 simultaneous channels of H.323 audio processing. If the  
ip-parameters form specifies only G.711 Mulaw or G.711 Alaw as the audio  
codecs, the MEDPROPT can service 31 channels. If any other codec type  
(G.723-5.3K, G.723-6.3K, or G.729) is administered, the MEDPROPT can only  
service 22 channels.  
The MEDPROPT is physically made up of 11 individual DSPs, but is treated  
logically as one port. If individual DSPs on the TN802B MAPD fail, the  
MEDPROPT remains in-service at lower capacity.  
The MEDPROPT is a shared service circuit. It is shared between H.323 trunk  
channels and H.323 stations. An idle channel is allocated to an H.323  
trunk/station on a call-by-call basis.  
Error Log Entries and Test to Clear Values  
Table 3-349. MEDPROPT Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
test board UUCCSS  
1
0
0
Any  
Any  
ON  
1(a)  
DSPCapacity Test  
(#1382)  
test board UUCCSS l r5  
258(b)  
DSPCapacity Test WARNING  
(#1382)  
ON  
test board UUCCSS l r5  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPROPT (TN802 MED PRO DSP PORT)  
3-807  
Table 3-349. MEDPROPT Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
515(c)  
DSP Capacity  
Query Test  
(##1382)  
MINOR  
ON  
test board UUCCSS l r5  
18(d)  
769  
0
busyout port  
UUCSS  
WARNING  
MIN  
OFF  
ON  
release port UUCCSS  
test port UUCCSS l r10  
Any  
TDM NIC  
Looparound Test  
(#1380)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. Error Type 1 - this error type indicates that less than three DSPs are out of  
service (OOS), and no alarm is raised. The Aux Data field contains the  
number of DSPs that are Out of Service (OOS).  
b. Error Type 258 - this error type indicates that more than three, but less  
than 9 DSPs are out of service (OOS), and a WARNING alarm is raised.  
The Aux Data field contains the number of DSPs that are Out Of Service  
(OOS).  
c. Error Type 515 - this error type indicates that all DSPs are out of service  
(OOS), and a MINOR alarm is raised. The Aux Data field contains the  
number of DSPs that are Out Of Service (OOS).  
d. Error Type 18 - the MEDPRO has been busied out by a busyout port  
UUCSS command.  
1. Release the port (release port UUCSS).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPROPT (TN802 MED PRO DSP PORT)  
3-808  
System Technician-Demanded Tests:  
Descriptions and Error Codes  
Investigate tests in the order they are presented in Table 3-350. By clearing error  
codes associated with the DSP Capacity Query Test, for example, you may also  
clear errors generated from the other test in the testing sequence.  
Table 3-350. System Technician-Demanded Tests  
Short  
Test  
Reset  
LongTest Board  
test  
1
Order of Investigation  
Sequence Sequence Sequence ds1-loop  
D/ND  
ND  
DSP Capacity Query (#1382)  
TDM NIC Looparound Test (#1380)  
X
X
X
X
ND  
1. D = Destructive; ND = Nondestructive  
DSP Capacity Query Test (#1382)  
This test is non-destructive  
This test polls the circuit pack for the number of failed DSPs. If all DSPs are  
functional, the test passes and the board is operating at maximum capacity. If  
any DSPs have failed, the test fails and reports the number of failed DSPs.  
A failure of 3 or fewer DSPs does not result in an alarm. A failure of more than 3  
up to 8 DSPs results in a warning alarm. A failure of more than 8 DSPs results in a  
minor alarm. In all cases, except all DSPs failing, the MEDPROPT continues to  
provide reduced capacity.  
Table 3-351. DSP Capacity Query Test (#1382)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
2100  
2500  
ABORT  
ABORT  
ABORT  
Response to the test was not received within the allowable time period.  
Could not allocate the necessary system resources to run this test.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPROPT (TN802 MED PRO DSP PORT)  
3-809  
Table 3-351. DSP Capacity Query Test (#1382) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1-11  
FAIL  
Some DSPs on the circuit pack have failed. The FAIL code is the number of  
bad DSPs reported.  
PASS  
All 11 DSPs are functioning and in-service.  
No board was detected by the test.  
0
NO  
BOARD  
1. Check the Error Log for wrong board (Error Type 125) or no board (Error  
Type 131). Resolve either of these issues, if applicable.  
2. Check that the board is properly translated and inserted. If so, check for  
hyperactivity. If hyperactive, use the reset board UUCSS command.  
3. Run the test again. If it fails, the circuit pack may be bad. Replace the  
circuit pack and retest.  
TDM NIC Looparound Test (#1380)  
This test is non-destructive  
This test sets up a loopback path from the TDM bus out to the NIC edge of the  
Media processor and back to the TDM bus. The loopback is established by  
setting up the outbound IP connection to send IP packets to the MedPro’s own IP  
address. The tone generator places a test tone (440Hz) onto a timeslot. The  
timeslot is listened to by the Media processor board. The tone is routed through  
the TAP802 DSP farm, where it may undergo transcoding to G.723, etc. The tone  
is looped back at the Network interface and back through the TAP802 where it is  
converted back into standard PCM. The tone is placed onto a TDM timeslot and  
detected by a tone detector port. The test passes if 440Hz is reported by the  
tone detector  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPROPT (TN802 MED PRO DSP PORT)  
3-810  
Table 3-352. TDM NIC Looparound Test (#1380)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1002  
ABORT  
The system could not allocate timeslots for the test. The system may be  
under heavy traffic conditions or it may have timeslots out of service due to  
TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic, retry  
the command at 1-minute intervals a maximum of 3 times.  
2. If system has TDM-BUS errors, clear any errors, and retry the command  
at 1-minute intervals a maximum of 3 times.  
3. If the command continues to abort, escalate the problem.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out of service.  
1. Resolve any TTR-LEV errors. Even if there are no TTR-LEV errors, there  
may not be a Tone Detector available on the network that contains the  
circuit pack being tested. Verify that there is at least one Tone Detector  
on this network. This does not harm the system.  
2. Resolve any TONE-PT errors.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 3 times.  
2000  
ABORT  
Response to the test was not received in the allowable time period.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
2100  
2500  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
2801  
ANY  
ABORT  
FAIL  
The TN802B Media Processor board has not been administered on the  
ip-interfaces form.  
The test did not detect the test tone through the looparound connection.  
1. Test the tone-clock in the port network that contains the media processor  
under test.  
2. If the tone-clock is healthy, test the media processor board again.  
3. If the test continues to fail, replace the media processor board.  
The board is functioning properly.  
PASS  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MEDPROPT (TN802 MED PRO DSP PORT)  
3-811  
Table 3-352. TDM NIC Looparound Test (#1380) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
No board was detected by the test.  
BOARD  
1. Resolve either wrong board (Error 125) or no board (Error 131) issues, if  
applicable.  
2. Check that the board is properly translated and inserted. If so, check for  
hyperactivity (Error 1538). If hyperactive, use the reset board UUCSS  
command.  
3. Run the test again. If it fails, the NCE chip on board may be bad.  
Replace the board and retest.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MET-BD (MET Line Circuit Pack)  
3-812  
MET-BD (MET Line Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board PCSS sh  
test board PCSS sh  
Full Name of MO  
MET Line Circuit Pack  
MET Line Circuit Pack  
MET-BD  
MET-BD  
MIN  
WRN  
1. Where P is the port network number (1); C is the carrier designation (for example, A, B,  
or C); and SS is the address of the slot in the carrier where the circuit pack is located  
(for example, 01, 02, ..., etc.).  
Refer to XXX-BD (Common Port Circuit Pack) Maintenance documentation for  
circuit pack level errors. See also MET-LINE maintenance documentation for  
related line information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-813  
MET-LINE (MET Line)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test port PCSSpp l  
Full Name of MO  
MET Line  
MET-LINE  
MET-LINE  
MINOR  
WARNING  
test port PCSSpp sh  
MET Line  
1. Where P is the port network number (1); C is the carrier designation (for example, A, B,  
or C); SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02, ..., etc.); and pp is the 2-digit port number (for example, 01).  
Electronic Station is the user-friendly term to denote the MET (Multibutton  
Electronic Telephone) Station Set. The MET sets were originally introduced for  
use in earlier PBX systems but can now be used in Generic 1 switches.  
The TN735 MET Line circuit pack supports four of these METsets. Each MET set  
uses three pairs of wires: an analog voice pair, a transmit pair, and a receive pair.  
Power is sent over the transmit and receive pairs. The MET Line circuit pack  
supports all 10-, 20-, and 30-button sets.  
MET Line interactions are shown in Figure 3-34.  
MET  
LINE  
CIRCUIT  
PACK  
MET LINE  
(1)  
PORT  
VOICE  
TERMINAL  
PBX  
MET LINE  
VOICE  
(4)  
PORT  
TERMINAL  
MET LINE  
Figure 3-34. MET Line Interactions  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-814  
The Recall button is used in this system as a self-test button, and, when pressed,  
lights all of the lamps on the MET set and runs the ringer update.  
This section refers only to the MET-LINE maintenance that is performed. Note that  
MET-LINE maintenance is closely related to, and interacts with, the MET-BD (MET  
line circuit pack) maintenance in some instances. Some of the results of  
maintenance testing of the MET line may be affected by the health of the MET  
Line circuit pack. This interaction should be kept in mind when investigating the  
cause of reports of MET line problems.  
There are instances in this section where service states of a station are  
mentioned. An explanation of these service states follows:  
■
Out-of-Service—The port (and station) have been removed from service.  
A busyout of a port causes it to be out-of-service.  
■
Ready-for-Service—Once a port on the circuit pack has been put into  
service, the voice terminal must communicate that it is present. The time  
between these two events is the time when the terminal is in the  
ready-for-service state.  
■
In Service—Once the system receives a message from the voice terminal  
communicating that it is present, the station is put into the in-service state.  
The terminal can also be forced into the in-service state if it goes off-hook  
while it is in the ready-for-service state.  
After running the status station command, the status is reported as either  
out-of-service, in-service (as stated in the preceding list), or disconnect (the  
station is in the ready-for-service state).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-815  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-353. MET Line Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test port PCSSpp sh r 1  
1 (a)  
40987  
0
None  
18 (b)  
130 (c)  
257 (d)  
513 (e)  
busyout port PCSSpp  
WARNING  
WARNING  
OFF  
ON  
release port PCSSpp  
test port PCSSpp sh  
None  
None  
2
40988  
40965  
MIN/WRN  
OFF  
OFF  
Hybrid Line Station  
Audits Test (#61)  
WARNING  
test port PCSSpp sh r 4  
test port PCSSpp l r 3  
test port PCSSpp l r 3  
2
769  
Port Diagnostic Test  
(#35)  
MIN/WRN  
ON  
ON  
2
1025  
Hybrid & Conf.  
MIN/WRN  
Circuits Test (#57)  
2
1537 (f)  
1793  
40968  
None  
MIN/WRN  
OFF  
ON  
2
TDMNPE Crosstalk  
Test (#6)  
MIN/WRN  
test port PCSSpp l r 3  
2049(g)  
2049(h)  
3840(i)  
32770  
40967  
40989  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Major or Minor alarms on this MO may be downgraded to Warning alarms based on the values used  
in the set options command.  
Notes:  
a. Indicates a defective data link. An off-board problem detected by port  
circuit. Make sure the MET set is connected, and that the EPF test passes.  
If data transmission problems are experienced, check for defective wiring,  
check for a defective voice terminal, and move voice terminal closer to the  
switch (in terms of feet of wire from the jack to the switch). If problem still  
exists, replace the circuit pack. Once the problem has been resolved, the  
alarm is retired due to the passing of time.  
b. This error is logged when the port in question is busied out by  
maintenance personnel. Make sure port is released from busyout.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-816  
c. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
d. This indicates that the EPF has been turned off due to the overcurrent  
condition at the voice terminal. Check for defective wiring, check for a  
damaged jack, and make sure the voice terminal is a MET set. Once the  
problem has been resolved, the alarm is retired due to the passing of time.  
e. The particular station audit that causes this error type to be produced is  
the EPF inquiry audit. If the EPF inquiry receives an "epf-no-load"message  
a certain number of times, this error occurs and, if the EPF inquiry receives  
an "epf-on-ok" or an "epf-off-ok" message, it contributes to the resolution of  
this alarm.  
This indicates that the voice terminal has probably been disconnected or  
that there is a problem in the wiring to the terminal. Make sure that the  
voice terminal is connected or check for defective wiring to the voice  
terminal.  
f. This indicates that something is wrong with the link to the voice terminal.  
An in-line maintenance error has generated an off-board Minor alarm.  
Ignore if there are no complaints. Otherwise, verify that the voice terminal  
is connected, check for defective wiring, check for a defective voice  
terminal, and move voice terminal closer to the switch (in terms of feet of  
wire from the jack to the switch). If the problem still exists, replace the  
circuit pack.  
g. This indicates that the station went off-hook while it was in the  
ready-for-service state. Use the status system command to determine  
the state of the station. The off-hook should have moved the station to  
ready-for-service. No action is necessary.  
h. This is the code that is generated when the link between the circuit pack  
and the voice terminal is successfully reset. No action is necessary.  
i. An uplink message being logged that the EPF is one with no load on it. No  
action is necessary.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the Port  
Diagnostic Test, for example, you may also clear errors generated from other  
tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-817  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
ND  
NPE Crosstalk Test (#6)  
X
X
X
X
X
X
X
Port Diagnostic Test (#35)  
ND  
MFAT Electronic Power Feed Test (#56)  
Hybrid Circuit and Conference Circuit Test (#57)  
Station Lamp Update Test (#60)  
Station Audits Test (#61)  
ND  
ND  
X
X
X
ND  
ND  
Ringer Update Test (#62)  
ND  
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per port basis. The NPECrosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is part of a port’s Long Test Sequence and takes  
about 20 to 30 seconds to complete.  
Table 3-354. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension, attendant number, or trunk group/member  
number of the port. Use the status station, status attendant, or status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-818  
Table 3-354. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1001  
ABORT  
System resources required to run this test are not available. This could be  
due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
1003  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM Bus) Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
(TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension, attendant number, or trunk group/member number of the port.  
Use the status station, status attendant, or status trunk command to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. You must  
wait until the port is idle before retesting. Attendants are always in use  
(off-hook) if the handset is plugged in and the port is not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1018  
ABORT  
Test disabled via administration. This only applies to analog stations. The  
default for this field is ‘y,’ so you may want to determine why it has been  
turned off on this station.  
1. To enable the test for the particular analog station being tested, enter  
the change station extension command and change the Testfield  
on the Station form from 'n’ to y.  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-819  
Table 3-354. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2100  
ABORT  
System resources required to run this test are not available. This could be  
due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2020  
Any  
ABORT  
The test did not run due to an already existing error on the specific port or  
a more general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit  
pack and attempt to diagnose the already existing error.  
FAIL  
This test can fail due to on-board or off-board problems. Off-board  
problems of concern include EXP-INTF faults, TDM-BUS faults, and faults  
associated with the tone detectors/tone generators. Clear all off-board  
problems before replacing the board. Keep in mind that a TDM-BUS  
problem is usually the result of a faulty board connected to the backplane  
or bent pins on the backplane.  
1. Look for TDM-BUS errors in the error log. If present, refer to the  
TDM-BUS Maintenance documentation.  
2. Look for TONE-BD and/or TONE-PT errors in the error log. If present,  
refer to the TONE-BD Maintenance documentation and the TONE-PT  
Maintenance documentation.  
3. Test the board when the faults from steps 1 and 2 are cleared.  
Replace the board only if the test fails.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated using other port tests and examining  
station, trunk, or external wiring.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-820  
Port Diagnostic Test (#35)  
This test checks a port’s battery feed circuitry. The battery feed circuitry is tested  
for proper battery voltage by testing the switchhook state. In response to the test  
message, the on-board firmware terminates the line and checks for switch-hook  
presence. The termination is then removed, and a check is made for no  
switch-hook presence. The MET set must be on-hook for the test to execute.  
Table 3-355. TEST #35 Port Diagnostic Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Internal system error.  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port  
may be busy with a valid call. Use the display port PCSSpp command  
to determine the station extension, attendant number, or trunk  
group/member number of the port. Use the status station, status  
attendant, or status trunk command to determine the service state of  
the port. If the service state indicates that the port is in use, then the  
port is unavailable for certain tests. You must wait until the port is idle  
before retesting. Attendants are always in use (off-hook) if the handset  
is plugged in and the port is not busied out.  
1. If the port status is idle, then retry the command at 1-minute  
intervals a maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the  
station extension of the port. Use the status station command to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. You must  
wait until the port is idle before retesting.  
NOTE:  
The battery feed circuitry is tested for proper battery voltage by  
testing the switchhook state. In response to the test message,  
the on-board firmware terminates the line and checks for  
switch-hook presence. The termination is then removed, and a  
check is made for no switch-hook presence. The MET set must  
be on-hook for the test to execute.  
1. If the port status is idle, then retry the command at 1-minute  
intervals a maximum of 5 times.  
1018  
ABORT  
Test disabled via software patch.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-821  
Table 3-355. TEST #35 Port Diagnostic Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
This port may have been busied out by system technician.  
1. Look in the Error Log for Error Type 18 (port busied out) for this  
port. If this error type is present, then release the port via the  
release station <extension> command and run the test again.  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
2100  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Battery Feed Test failed. This port is out-of-service.  
1. Other ports on this circuit pack are not affected. Place user on a  
different port, if available, until a replacement circuit pack can be  
obtained.  
2. Replace circuit pack when available.  
PASS  
Battery Feed Test passed. Current flow is properly detected for this  
port.  
1. If users are reporting problems, examine connections to the port.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This  
could be due to incorrect translations, no board is inserted, an  
incorrect board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
MET Electronic Power Feed (#56)  
In this test, the software requests that the EPF be turned on for a given port. An  
attempt is made to turn on the power unit to the station. If no current is being  
drawn, this probably indicates that the station is not connected. If an overcurrent  
condition is sensed (that is, too much current is being drawn), this may indicate a  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-822  
short in the loop or a defective voice terminal. Depending on what condition is  
sensed, a message is returned stating that either the EPF was turned on  
successfully with no problems or that an overcurrent condition is sensed. This  
test is repeated once more five seconds later. If either test is not successful, the  
test aborts.  
Although this test will never actually return a fail result (except for the internal  
system error), an error type 257 entry will be made in the error log when the test  
has completed if the overcurrent case is detected by the hardware.  
Table 3-356. TEST #56 MET Electronic Power Feed Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
The test was aborted due to an internal system error on a software  
request to the board.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT  
System resources required to run this test are not available. The port  
may be busy with a valid call. Use the display port PCSSpp command  
to determine the station extension, attendant number, or trunk  
group/member number of the port. Use the status station, status  
attendant, or status trunk command to determine the service state of  
the port. If the service state indicates that the port is in use, then the  
port is unavailable for certain tests. You must wait until the port is idle  
before retesting. Attendants are always in use (off-hook) if the handset  
is plugged in and the port is not busied out.  
1. If the port status is idle, then retry the command at 1-minute  
intervals a maximum of 5 times.  
FAIL  
The test failed with an internal error while it was attempting to turn on  
the EPF.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
EAF Test passed. The message to turn on the power to the station was  
successfully sent to the port.  
1. Although this test never returns a FAIL result, after running this test,  
the Error Log should be checked for any entries with Error Type 257  
to examine the real results of this test.  
2. If Error Type 257 does not appear in the Error Log within 10  
seconds after completion of this test, it is safe to assume that the  
test sensed no problems with the power to the station. To verify that  
the station is powered up correctly, run a self-test on the station, if  
available, and check that all the feature buttons are operating.  
3. If Error Type 257 appears in the Error Log, this indicates some  
problem with the power to the station. The system technician  
should check for a short in the wiring, a damaged jack, a defective  
voice terminal, or an incorrect type of terminal.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-823  
Table 3-356. TEST #56 MET Electronic Power Feed Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
MET Circuit and Conference Circuit Test (#57)  
The MET Circuit Test checks the amount of reflection from the MET loop around  
circuitry and a Conference Test. The Tone-Clock circuit pack places a 1004-Hz  
tone on a time slot that the port circuit is listening on. A General Purpose Tone  
Detector (GPTD) is connected to another time slot that the same port circuit is  
talking on. The on-board microprocessor places the port in the loop around  
mode and the GPTD measures the level of the reflected signal.  
The Conference Test is performed after the Circuit Test. The Conference Circuit  
Test verifies that the NPE is able to listen to several test tones and correctly  
conference them together, and the test is executed in two parts. The first half of  
the test checks the operation of the NPE’s first three conference channels. The  
NPE is put in the loop around mode and instructed to talk on a selected time slot  
and to listen to the 1004-Hz tone using the first three conference channels. The  
signal level and noise level of the conferenced output are then measured using a  
GPTD and checked to verify that they are within an acceptable range.  
The second half of the Conference Test checks the operation of the NPE’s  
remaining four conference channels and follows the same procedure as above.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-824  
Table 3-357. TEST #57 MET Circuit and Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port  
may be busy with a valid call. Use the display port PCSSpp command  
to determine the station extension, attendant number, or trunk  
group/member number of the port. Use the status station, status  
attendant, or status trunk command to determine the service state of  
the port. If the service state indicates that the port is in use, then the  
port is unavailable for certain tests. You must wait until the port is idle  
before retesting. Attendants are always in use (off-hook) if the handset  
is plugged in and the port is not busied out.  
1. If the port status is idle, then retry the command at 1-minute  
intervals a maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
System resources required to run this test were not available. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may  
be under heavy traffic conditions or it may have time slots  
out-of-service due to TDM-BUS errors. Refer to TDM-BUS (TDM Bus)  
Maintenance documentation to diagnose any active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system  
may be oversized for the number of Tone Detectors present or some  
Tone Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to  
TTR-LEV (TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to  
TONE-PT (Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-825  
Table 3-357. TEST #57 MET Circuit and Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the  
station extension, attendant number, or trunk group/member number of  
the port. Use the status station, status attendant, or status trunk  
command to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants  
are always in use (off-hook) if the handset is plugged in and the port is  
not busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal System Error.  
2012  
2103  
ABORT  
ABORT  
The system could not make the conference connection for the test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
7
FAIL  
The conference circuit test failed. The conference circuit test is  
performed only if the hybrid test passes. The conference circuit test  
verifies that the network processing element (NPE) is able to correctly  
conference several test tones together. The test is executed in two  
parts. The first half of the test verifies the operation of the NPE’s first  
three conference channels, while the second half verifies the NPE’s  
remaining four conference channels. The test puts the NPE in loop  
around mode and instructs it to talk on a specified time slot while  
listening to a 1004 Hz tone, using the conference channels. A GPTD  
then measures the signal and noise levels of the conferenced output  
and reports whether or not these are within an acceptable range. The  
failure may be due to off-board circumstances, the most common of  
which is an off-hook occurring during the test. It is possible that the port  
may still be functional from a user’s point of view. Also, check the error  
logs against the GPTD-BD, the TONE-BD, and the TONE-PT.  
1. This error can be caused by a disconnected terminal. First, ensure  
that the terminal is connected and the wiring is OK.  
2. Then, issue the display port and the station status commands to  
determine if the station is idle. If it is idle, issue the test port  
command for this port.  
3. If test continues to fail, issue the busyout port and the release  
port commands, and then retest the port.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-826  
Table 3-357. TEST #57 MET Circuit and Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
57  
FAIL  
Hybrid Circuit Test failed. This could result in noisy or bad connections.  
1. Run circuit pack tests to check the Tone Generator circuit pack and  
the Tone Detector circuit pack, using test board PCSS short  
command.  
2. Resolve any problems that are detected on the Tone Generator  
circuit pack or Tone Detector circuit pack.  
3. If the Tone Generator and Tone Detector circuit packs are  
functioning properly, and the test still fails, replace the MET Line  
circuit pack.  
NOTE:  
If the MET Circuit and Conference Circuit Test fails for all ports on  
a circuit pack, a -5 volt power problem is indicated.  
PASS  
Hybrid Circuit and Conference Circuit Test passed. The hybrid circuitry  
is transmitting properly.  
1. If complaints still exist, investigate by using other port tests, and by  
examining the station, wiring, and connections.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This  
could be due to incorrect translations, no board is inserted, an  
incorrect board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
MET Line Station Lamp Updates Test (#60)  
For this test, the software lights the lamps on the terminal based on the status  
record contained in the processor. The lamp updates run only if the station is  
in-service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-827  
Table 3-358. TEST #60 MET Line Station Lamp Updates Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
ABORT  
This port may have been busied out by system technician.  
1. Look in the Error Log for Error Type 18 (port busied out) for this  
port. If this error type is present, then release the port via the  
release station <extension> command and run the test again.  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal System Error.  
2
3
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Station is in ready-for-service or out-of-service state. This may be due to  
wiring or an unplugged or defective set.  
1. Make sure terminal is connected and the wiring is correct.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT  
System resources required to run this test are not available. The port  
may be busy with a valid call. Use the display port PCSSpp command  
to determine the station extension, attendant number, or trunk  
group/member number of the port. Use the status station, status  
attendant, or status trunk command to determine the service state of  
the port. If the service state indicates that the port is in use, then the  
port is unavailable for certain tests. You must wait until the port is idle  
before retesting. Attendants are always in use (off-hook) if the handset  
is plugged in and the port is not busied out.  
1. If the port status is idle, then retry the command at 1-minute  
intervals a maximum of 5 times.  
FAIL  
Internal System Error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
MET Line Station Lamp Updates completed successfully.  
PASS  
1. If complaints still exist, investigate by using other circuit pack tests,  
and by examining the station, wiring, and connections.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-828  
Table 3-358. TEST #60 MET Line Station Lamp Updates Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
MET Line Station Audits Test (#61)  
This is a series of three tests that are classified as audits. These audits abort if  
attempted on an out-of-service station. The tests are as follows:  
■
Switchhook Audit—This is an update of the SPE records according to the  
circuit packs’ records.  
■
Bad Scan Inquiry—A message is sent uplink that contains a count that is  
generated due to certain events relating to the link conditions. This is an  
indication of data transmission problems between the MET Line circuit  
pack and the voice terminal.  
■
EPF Inquiry—The status of the EPF is sent uplink. Possible conditions are:  
EPF-on-ok, EPF-off, EPF-no-load, and EPF-on-overcurrent.  
Although this test will never actually return a fail result (except for the internal  
system error), it is possible that it will enter error types 257 (over current) or 513  
(open circuit) into the error log. To determine if there are any problems that do not  
show up in the test result, look for these error types in the error log. If these errors  
appear in the error log or if user complaints still exist, investigate by using other  
circuit pack tests and by examining the station, the wiring, and the connections.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-829  
Table 3-359. TEST #61 MET Line Station Audits Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Internal System Error.  
ABORT  
ABORT  
1
2
3
The test was aborted due to an internal system error during the  
switchhook audit.  
The test was aborted due to an internal system error during the bad  
scan inquiry.  
The test was aborted due to an internal system error during the EPF  
audit inquiry.  
1. Make sure that the station is not in an out-of-service state.  
2. Retry the command at 1-minute intervals for a maximum of 5 times.  
1000  
ABORT  
System resources required to run this test are not available. The port  
may be busy with a valid call. Use the display port PCSSpp command  
to determine the station extension, attendant number, or trunk  
group/member number of the port. Use the status station, status  
attendant, or status trunk command to determine the service state of  
the port. If the service state indicates that the port is in use, then the  
port is unavailable for certain tests. You must wait until the port is idle  
before retesting. Attendants are always in use (off-hook) if the handset  
is plugged in and the port is not busied out.  
1. If the port status is idle, then retry the command at 1-minute  
intervals a maximum of 5 times.  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the  
station extension, attendant number, or trunk group/member number of  
the port. Use the status station, status attendant, or status trunk  
command to determine the service state of the port. If the service state  
indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting. Attendants are  
always in use (off-hook) if the handset is plugged in and the port is not  
busied out.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
ABORT  
FAIL  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test failed due to an internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-830  
Table 3-359. TEST #61 MET Line Station Audits Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Hybrid Line Station Audits passed.  
PASS  
1. Although this test always returns a PASS result, it may enter Error  
Types 257 or 513 into the Error Log. To determine if there are any  
problems that don’t show up in the test result, look for these error  
types in the Error Log.  
2. If these errors appear in the Error Log, or if user complaints still  
exist, investigate by using other circuit pack tests, and by  
examining the station, wiring, and connections.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
MET Line Ringer Update Test (#62)  
In this update, a "ringer on" or a "ringer off" message is sent to the firmware to  
start and stop the ringer on the set.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MET-LINE (MET Line)  
3
3-831  
Table 3-360. TEST #62 MET Line Ringer Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
3
ABORT  
This port may have been busied out by system technician.  
1. Look in the Error Log for Error Type 18 (port busied out) for this  
port. If this error type is present, then release the port via the  
release station <extension> command and run the test again.  
2. Make sure that the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT  
System resources required to run this test are not available. The port  
may be busy with a valid call. Use the display port PCSSpp command  
to determine the station extension, attendant number, or trunk  
group/member number of the port. Use the status station, status  
attendant, or status trunk command to determine the service state of  
the port. If the service state indicates that the port is in use, then the  
port is unavailable for certain tests. You must wait until the port is idle  
before retesting. Attendants are always in use (off-hook) if the handset  
is plugged in and the port is not busied out.  
1. If the port status is idle, then retry the command at 1-minute  
intervals a maximum of 5 times.  
FAIL  
Internal System Error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Hybrid Station Ringer Update passed.  
PASS  
1. If complaints still exist, investigate using other circuit pack tests,  
and by examining the terminal, wiring, and connections.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This  
could be due to incorrect translations, no board is inserted, an  
incorrect board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to ensure that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MIS (Management Information System)  
3-832  
MIS (Management Information  
System)  
MO Name (in  
Alarm Log  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
Management Information System  
MIS  
WRN  
release mis  
The Management Information System (MIS)/Call Management System (CMS) MO  
is used only for administering MIS translations, such as trunks and stations.  
There are no hardware failures associated with this MO.  
NOTE:  
To diagnose MIS link hardware errors and alarms, see PKT-INT (Packet  
Interface).  
The MIS/CMS is an adjunct processor that collects ACD data sent from the  
system. To change MIS translations, a system administrator must first enter a  
busyout mis command at the terminal. When the MIS is busied out, the system  
stops sending ACD data to the MIS, and a Warning alarm is raised. When  
finished, a release mis command should be entered at the terminal. This clears  
the Warning alarm and allows the switch to send ACD data to the MIS.  
Error Log Entries and Test to Clear Values  
On/Off  
Error Type  
Aux Data Associated Test  
Alarm Level  
Any  
Board  
Test to Clear Value  
release mis  
1
0
0
0
Any  
Any  
18(a)  
busyout mis  
WARNING  
ON  
release mis  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Note:  
a. When the busyout MIS command is issued, no data is sent to the  
MIS/CMS regardless of the link state. To allow data to be sent to MIS/CMS,  
a release mis command must be issued from the terminal.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-BD  
3
3-833  
MMI-BD  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board PCSS l r#  
test board PCSS l r#  
test board PCSS s r#  
Full Name of MO  
MMI-BD  
MMI-BD  
MAJOR  
Multimedia Interface Circuit Pack  
Multimedia Interface Circuit Pack  
Multimedia Interface Circuit Pack  
MINOR  
2
MMI-BD  
WARNING  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B,  
or C); and SSis the address of the slot in the carrier where the circuit pack is located (for example,  
01, 02, ..., and so forth).  
2. Refer to XXX-BD (Common Port Board).  
The Multimedia Interface Circuit Pack (TN787D or later) provides a number of  
H.221 protocol terminations for bit streams received from the TDM bus. The  
Multimedia Interface demultiplexes the H.221 bit stream (audio, video, data,  
control, and indication signals) and transmits the bit streams onto the TDM bus  
so that the appropriate circuit packs can process them.  
The Multimedia Interface circuit pack is commonly referred to as the MMI pack  
for H.221 protocol termination. It is also called the MMCH circuit pack. There are  
32 ports (also called resources) on the circuit pack. See MMI-PT for maintenance  
of these resources.  
The MMI circuit pack contains 4 digital signal processors that manage the 32  
resources.  
NOTE:  
Refer to ‘‘Troubleshooting Multimedia Call Handling (MMCH)’’ in Chapter 1,  
‘‘Maintenance for csi systems’’ for MMCH troubleshooting information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-BD  
3
3-834  
Figure 3-35. TN787 Multimedia Interface (MMI) Circuit Pack  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-BD  
3
3-835  
Error Log Entries and Test to Clear Values  
Table 3-361. MMI-BD Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm On/Off  
Associated Test  
Level  
Board  
Any  
ON  
Test to Clear Value  
1
0
0
Any  
Any  
test board PCSS sh r 1  
release board PCSS  
test board PCSS r 3  
1 (a)  
Any  
0
None  
MIN  
18 (b)  
217 (c)  
257 (d)  
513 (e)  
Busyout board PCSS  
None  
WNG  
WNG  
OFF  
ON  
0
65535 Control Channel Loop Test (#52) MIN  
ON  
4352  
to  
Uplink error from pack  
4357  
769 (f)  
Any  
MMI Synchronization Status  
Test (#1123)  
None  
1281 (g) Any  
1538 (h) Any  
Circuit Pack Restart Test (#594)  
Software detected error  
TSI XTalk (#6)  
MAJ  
MIN  
MIN  
MAJ  
ON  
ON  
ON  
ON  
1793 (i)  
2049 (j)  
ANY  
Any  
test board PCSS l r 3  
test board PCSS l r 3  
TSI Loop (#1108)  
1. Run the short test sequence first. If all tests pass, run the long test sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. The circuit pack stopped functioning or it was physically removed from the  
system. The alarm logs approximately 11 minutes after the circuit pack  
has been removed and/or the SAKI Sanity Test (#53) fails.  
If the circuit pack is in the system and the red LED is on, follow the  
instructions for a red alarm in ‘‘Control Circuit Packs’’ in ‘‘Maintenance for  
csi systems’’.  
b. This circuit pack has been busied out using the busyout board PCSS  
command.  
c. There are more than four MMI circuit packs in the system. Remove the  
circuit pack that generated the error in the error log by locating the slot  
indicated by the error.  
d. Indicates transient communication problems between the switch and this  
circuit pack. Execute the test board PCSS command and refer to the  
repair procedures for the Control Channel Looparound Test (#52) in the  
XXX-BD section.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-BD  
3
3-836  
e. The circuit pack detected an Angel on-board hardware failure. The  
reported aux data values correspond to the following detected errors:  
4352 - External RAM error  
4253 - Internal RAM error  
4355 - ROM Checksum error  
4357 - Instruction set error  
Reset the circuit pack by using the busyout board PCSS, reset board  
PCSS, and release board PCSS commands. When reset, the circuit pack  
executes a set of tests to detect the presence of any of the above faults.  
The detection of one these errors during initialization causes the circuit  
pack to lock up and appear insane to the system. See the repair  
procedures in note b) for Error Type 1.  
f. This MMI circuit pack reported a loss of MMI synchronization. Refer to Test  
(#1123) for repair procedures.  
g. A failure of the time slot interchanger has been detected. Reset the circuit  
pack using the busyout board PCSS, reset board PCSS, and release  
board PCSS commands. If the reset passes, then the on-board circuitry is  
healthy. Retire the alarm using the test board PCSS long clear command  
followed by release board PCSS.  
h. The circuit pack is hyperactive; that is, it is flooding the switch with  
messages sent over the control channel. The circuit pack is taken out of  
service when a threshold number of these errors is reported to the switch.  
Clear the alarm using the following commands: busyout board PCSS,  
reset board PCSS, test board PCSS long clear, release board PCSS. If  
the error recurs within 10 minutes, replace the circuit pack.  
i. The TSI Cross Talk Test (#6) failed. See the description of this test and  
follow the repair procedures.  
j. The TSI Looparound Test (#1108) failed. See the description of this test  
and follow the repair procedures.  
System Technician-Demanded Tests:  
Descriptions and Error Code  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the TSI  
Crosstalk Test (#6), for example, you may also clear errors generated from other  
tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-BD  
3
3-837  
Table 3-362. System Technician-Demanded Tests: MMI-BD  
Short Test  
Long Test  
Sequence  
Reset Board  
Sequence  
1
Order of Investigation  
Sequence  
D/ND  
ND  
ND  
ND  
ND  
ND  
D
TSI Crosstalk (#6)  
X
X
TSI Looparound Test (#1108)  
MMI SYNC Status Test (#1123)  
MMI SYNC Status Test (#1122)  
Control Channel Looparound Test (#52)  
X
X
X
X
2
2
SAKI Sanity Test (#53)  
X
1. D = Destructive, ND = Non-destructive  
2. Refer to the repair procedure described in XXX-BD (Common Port Circuit Pack) for a description  
of this test.  
TSI Crosstalk Test (#6)  
This test is non-destructive. The Time Slot Interchanger (TSI) chip controls  
connectivity to the TDM bus. The TSI Cross Talk Test verifies that this TSI talks on  
the selected TDM bus time slot and never crosses over to time slots reserved for  
other connections. If the TSI is not working correctly, one-way and noisy  
connections may occur. If the test passes, then the TSI is able to communicate  
over the TDM bus. This test is part of the circuit pack’s demand and scheduled  
long test sequence, and takes approximately 20 to 30 seconds to complete.  
Table 3-363. TEST #6 TSI Crosstalk Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
Internal system error. This is an abnormal abort.  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
The system could not allocate time slots for the test, the traffic load on the  
system is very high, or the time slots are out-of-service due to TDM-BUS  
errors. Refer to ‘‘TDM-BUS (TDM Bus)’’ to diagnose any active TDM Bus  
errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat the test at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-BD  
3
3-838  
Table 3-363. TEST #6 TSI Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1003  
ABORT  
The system could not allocate a tone detector for the test. The system is  
oversized for the number of tone detectors present, or some tone detectors  
are out-of-service.  
1. Resolve any ‘‘TTR-LEV (TTR Level)’’ errors in the Error Log.  
2. Resolve any ‘‘TONE-PT (Tone Generator)’’ errors in the Error Log.  
3. If neither condition exists, retry the test at 1-minute intervals a maximum  
of 5 times.  
2000  
ABORT  
Response to the test was not received from the MMI-BD circuit pack within  
the allowable time period.  
1. If this result occurs repeatedly, attempt to reset the circuit pack if the  
other ports are not in use. Reset the circuit pack by issuing the busyout  
board PCSS, reset board PCSS, followed by the release board PCSS  
commands.  
2. If this result occurs again, replace the circuit pack.  
Internal system error. This is an abnormal abort.  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary resources to run this test. This is an  
abnormal abort.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
The TSI was found to be transmitting in error. This causes noisy and  
unreliable connections.  
1. Replace the circuit pack.  
PASS  
The TSI is correctly using its allocated time slots.  
TSI Looparound Test (#1108)  
This test is non-destructive. During this test, the MMI’s Time Slot Interchanger  
(TSI) is listens to a TDM timeslot. A digital count tone loops back in the TSI and  
onto another TDM timeslot without passing through any resource hardware. A  
tone detector port verifies the looped data. If the digital count is correct, then the  
test passes. The test is done for both TDM buses. Failures indicate that the TSI is  
unreliable.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-BD  
3
3-839  
Table 3-364. TEST #1108 TSI Looparound Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
Internal system error. This is an abnormal abort.  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
The system could not allocate time slots for the test. Either the traffic load on the  
system is very high or time slots is out-of-service due to TDM-BUS errors. Refer  
to ‘‘TDM-BUS (TDM Bus)’’ to diagnose any active TDM Bus errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat the test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone detector for the test. The system may be  
oversized for the number of Tone Detectors present, or some Tone Detectors  
may be out-of-service.  
1. Resolve any ‘‘TTR-LEV (TTR Level)’’ errors in the Error Log.  
2. Resolve any ‘‘TONE-PT (Tone Generator)’’ errors in the Error Log.  
3. If neither condition exists, retry the test at 1-minute intervals a maximum of  
5 times.  
2000  
ABORT  
Response to the test was not received from the Tone Detector circuit pack  
within the allowable time period.  
1. If this result occurs repeatedly, attempt to reset the circuit pack (if the other  
ports are not in use). Reset the circuit pack by issuing the busyout board  
PCSSpp and the reset board PCSSpp commands followed by the release  
board PCSS command.  
2. If this result occurs again, replace the circuit pack.  
Internal system error. This is an abnormal abort.  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary resources to run this test. This is an abnormal  
abort.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
The TSI was found to be transmitting in error, causing noisy and unreliable  
connections.  
1. Replace the circuit pack.  
PASS  
The TSI is correctly using its allocated time slots.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-BD  
3
3-840  
MMI Synchronization Status Test (#1122 and  
1123)  
This test is non-destructive. To support applications involving multiple MMI circuit  
packs, the appropriate MMI circuit packs must be synchronized with one  
another. One such circuit pack is designated as the master sync source, which  
provides the synchronization signal onto the TDM bus. The other MMI circuit  
packs in the system listen to this signal.  
This test monitors this synchronization state. The test fails if the MMI circuit pack  
is not in sync. The test passes with auxiliary code 1100 if the MMI circuit pack is  
in sync and is providing the synchronization signal for the system. The test also  
passes with an auxiliary code of 1101 if the MMI circuit pack is in sync and  
listening to the sync signal. MMI circuit packs do not lose the synchronization  
signal unless an MMI circuit pack is either pulled out of the system or reset by  
using a technician command.  
Test #1122 runs when the long option of the test board command is entered,  
initiating the recovery of synchronization. Test #1123 runs when the short option  
of the test board command is entered, giving the status of the synchronization.  
You need not necessarily run the long option since synchronization signal  
recovery should be taking place within software running in the background. Use  
the long option only if synchronization is not established within 5 minutes of  
investigating the problem.  
Table 3-365. TEST #1122/1123 MMI Synchronization Status Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
Internal system error. This is an abnormal abort.  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
A response to the test was not received from the MMI circuit pack within the  
allowable time period.  
1. If this result occurs repeatedly and the MMI circuit pack is idle, reset the  
circuit pack using busyout board PCSS, then reset board PCSS,  
followed by release board PCSS.  
2. Rerun the test; if the same result occurs again, replace the MMI circuit  
pack.  
2012  
2100  
ABORT  
ABORT  
Internal system error  
Could not allocate the necessary resources to run this test. This is an  
abnormal abort.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-BD  
3
3-841  
Table 3-365. TEST #1122/1123 MMI Synchronization Status Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
FAIL  
The MMI circuit pack is out of MMI synchronization. Run the long option of the  
test board command.  
1. Wait up to 5 minutes, and then reset the circuit pack with these  
commands: busyout board PCSS, then reset board PCSS, followed by  
release board PCSS.  
2. Rerun the test; if the same result occurs again, replace the circuit pack.  
1100  
1101  
PASS  
PASS  
The MMI circuit pack is providing the synchronization correctly. This MMI  
circuit pack is designated as the Master Sync source.  
The MMI circuit pack is listening to the synchronization signal correctly.  
Control Channel Looparound Test (#52)  
Refer to the repair procedure described in the XXX-BD (Common Port Circuit  
Pack) maintenance documentation as Control Channel Looparound Test (#52).  
SAKI Sanity Test (#53)  
Refer to the repair procedure described in the XXX-BD (Common Port Circuit  
Pack) maintenance documentation as SAKI Sanity Test (#53).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MMI-LEV (Multimedia Interface Resource Level)  
3-842  
MMI-LEV (Multimedia Interface  
Resource Level)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
MMI-LEV  
MMI-LEV  
MAJOR  
See ‘‘Resolving MMI-LEV Errors/Alarms’’  
(below)  
The Multimedia Interface Resource Level MO monitors MMI efficiency by  
tracking the number of MMI ports that are in-service, and then comparing that  
number with the value entered in the MMIsfield on the System-Parameters  
Maintenance form. This MMIsfield is located under the Minimum Maintenance  
Threshold section. The MMIsfield contains the minimum number of MMI ports  
needed for the Multimedia Call Handling (MMCH) feature to run efficiently and is  
an administrable field. This field must contain a minimum threshold number for  
MMI port capacity of between 0-128. The MMCH feature must be enabled on the  
System-Parameters Customer-Options form before the MMIsfield can be  
changed to a number greater than zero. The algorithm for determining that a low  
level of MMI resources exists uses the value entered in the MMIsfield and the  
number of MMI ports that are in-service in the system.  
Each MMI circuit pack contains a maximum of 32 ports. If the number of  
in-service MMI ports falls below the minimum port capacity (value entered on the  
System Parameters Maintenance form under the Minimum Maintenance  
Threshold section and in the MMIfield), a MMI-LEV error is logged. If this outage  
continues for 15 minutes, a MAJOR alarm is raised.  
Resolving MMI-LEV Errors/Alarms  
MMI ports are a key part of the MMCH feature, and any loss in the number of  
ports available for use degrades the MMCH customer-defined service level.  
If a MMI circuit pack or port is busied out using the busyout board or busyout  
port commands, these out-of-service ports are not included in the MMI level  
calculation, thus allowing a technician to busy out a MMI circuit pack for  
maintenance reasons without causing a MAJOR alarm to be raised. However, if  
all of the ports on the MMI circuit pack are not made busy and the circuit pack is  
removed, an alarm is raised.  
NOTE:  
When diagnosing a MMI-LEV problem, begin by resolving any alarms  
raised against MMI-BD or MMI-PT maintenance objects. Clearing MMI-BD  
or MMI-PT alarms may clear the MMI-LEV alarm.  
The MMI circuit pack is maintained by the software like the Tone Detector circuit  
pack, which can be removed and reinserted in any port board slot without  
Download from Www.Somanuals.com. All Manuals Search And Download.  
administration. Similarly, if a MMI circuit pack is removed from service logically  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MMI-LEV (Multimedia Interface Resource Level)  
3-843  
by failing the Archangel sanity scan test or is removed from service physically by  
removing the circuit pack from the carrier, no error/alarm is raised against either  
the MMI-BD or the MMI-PT maintenance objects. Therefore, if a MMI-LEV  
error/alarm exists, yet no alarms have been raised against MMI-BD or MMI-PT  
maintenance objects, a MMI circuit pack may have been removed from service  
causing the MMI-LEV error/alarm. To resolve a MMI-LEV MAJOR alarm, restore  
the number of MMI ports available for service to be equal to or greater than the  
calculated port capacity.  
To determine how many MMI circuit packs are needed for the MMCH feature:  
1. Using the display system-parameters maintenance command, locate  
the number listed in the Minimum Maintenance Thresholds(MMIs)  
field and record this number.  
2. Use the list configuration command to verify the number of MMI ports.  
3. Compare this number with the value listed in the MMIfield on the  
System-Parameters Maintenance form (number listed in step 1 a minimum  
thresholds number for MMI ports of between 0-128). Each MMI circuit  
pack contains a maximum of 32 ports. If the number in the MMIsfield is  
less than or equal to 32, one MMI circuit pack is needed. If this number is  
64, then two MMI circuit pack are needed.  
4. Use the list configuration command to verify that the number of MMI  
circuit packs listed agrees with the required minimum port capacity (from  
step 1). If the number of MMI circuit packs listed in the step 2 differs from  
the calculated number, restore the number of MMI circuit packs to the  
correct value, in order to resolve the MMI-LEV alarm.  
Error Log Entries and Test to Clear Values  
Table 3-366. MMI-LEV Error Log Entries  
Error  
Type  
Aux  
Data  
On/ Off  
Board  
Associated Test  
None  
Alarm Level  
Test to Clear Value  
1
1
Any  
MAJOR  
OFF  
1. The number of MMI resources in the system that are in service has fallen below the calculated  
minimum value. If the number of in-service MMI ports falls below the MMCH port capacity (value  
entered in the Minimum Maintenance Thresholds for MMIsfield) on the  
System-Parameters Maintenance form, a MMI-LEV error is logged. If this outage continues for 15  
minutes, a MAJOR alarm is raised.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
MMI-LEV (Multimedia Interface Resource Level)  
3-844  
To resolve this alarm, correct the out-of-service problem by following these procedures:  
1. See ‘‘MMI-PT’’ and ‘‘MMI-BD’’ and resolve any associated alarms.  
2. If a MMI-LEV error/alarm exist and none has been raised against MMI-BD or  
MMI-PT maintenance objects, an MMI circuit pack may have been removed from  
service causing the MMI-LEV error/alarm. To resolve a MMI-LEV MAJOR alarm,  
restore the number of MMI ports available for service to be equal to or more than  
the calculated port capacity. See the ‘‘Resolving MMI-LEV Errors/Alarms’’ section  
above for details.  
3. If the error contines to alarm, escalate the problem.  
System Technician-Demanded Tests:  
Descriptions and Error Code  
There are no System Technician-Demanded tests for MMI-LEV.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-PT  
3
3-845  
MMI-PT  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test port PCSSpp l r#  
test port PCSSpp l r#  
test port PCSSpp l r#  
Full Name of MO  
Multimedia Interface Port  
Multimedia Interface Port  
Multimedia Interface Port  
MMI-PT  
MMI-PT  
MMI-PT  
MAJOR  
MINOR  
WARNING  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A,  
B, or C); and SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02, ..., and so forth).  
NOTE:  
Refer to ‘‘Troubleshooting Multimedia Call Handling (MMCH)’’ in Chapter 1,  
‘‘Maintenance for csi systems’’ for MMCH troubleshooting information.  
The Multimedia Interface Circuit Pack provides a number of H.221 protocol  
terminations for bit streams received from the TDM bus. The Multimedia Interface  
demultiplexes the H.221 bit stream (audio, video, data, control, and indication  
signals) and transmits the bit streams onto the TDM bus to be processed by the  
appropriate circuit packs.  
Each Multimedia Interface Circuit Pack contains 32 separately maintained  
“ports,” more commonly referred to as "resources." MMI-PT represents one of  
these 32 resources. At system boot or when the circuit pack is inserted, 32  
resources are inserted into the system.  
The MMI circuit pack contains 4 Digital Signal Processors (DSPs) which manage  
the 32 resources. These resources are directly mapped to DSPs:  
Resource  
1-8  
Direct Map  
DSP1  
9-16  
DSP2  
17-24  
25-32  
DSP3  
DSP4  
All 8 resources that the circuit pack controls may be placed out of service by the  
failure of one of these DSPs.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-PT  
3
3-846  
Figure 3-36. TN787 Multimedia Interface (MMI) Circuit Pack  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-PT  
3
3-847  
Error Log Entries and Test to Clear Values  
Table 3-367. MMI-PT Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/ Off  
Board  
Associated Test  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
test port PCSSpp sh r 1  
1 (a)  
Any  
0
Uplink error from pack  
Busyout port PCSSpp  
Software generated  
None  
18 (b)  
130 (c)  
257 (d)  
WNG  
WNG  
OFF  
ON  
ON  
release port PCSSpp  
Any  
Any  
MAJ/  
MIN  
513 (e)  
1025 (f)  
Any  
Resource Loopback  
Test (#1111)  
MIN  
ON  
test port PCSSpp sh r 3  
Any  
Any  
Uplink error from pack  
Uplink error from pack  
3841 -  
3844 (g)  
1. Run the short test sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. The customer endpoint connected on a conference sent too many  
messages to the VSP-MCU in a specified amount of time. Check the  
“status conference” forms to correlate which customer had the problem.  
This is a customer endpoint problem and not a VSP-MCU problem.  
b. This port has been busied out by the busyout port PCSSpp command.  
c. Indicates that the circuit pack has been removed or has been insane for  
more than 11 minutes. To clear the error, replace or reseat the circuit pack.  
d. This error occurs if the MMI circuit pack detects a DSP Error. Maintenance  
software will reset the DSP when this error is received. This error is logged  
for all 8 resources connected to this particular DSP. If this DSP continues  
to fail sanity, a Minor alarm is raised. Replace the circuit pack.  
e. This error occurs when the Resource Looparound Test (#1111) fails. Run  
the Long Test Sequence and note the results of Test #1111.  
f. This error occurs if either the MMI or Voice Conditioner (VC) circuit packs  
reports a loss of framing on the service channel between these two circuit  
packs. When a customer endpoint establishes a call to the VSP-MCU, a  
channel is established between the MMI resource and the VC port. If this  
channel is detected to go down by either circuit pack, an uplink message  
is sent. This error is then forwarded to maintenance for both circuit packs.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-PT  
3
3-848  
Run the Long Test Sequence for this MMI resource, and if any of the tests  
fail, follow the repair procedures for that test. If all tests pass, the cause of  
the problem might be with the VC pack. See the “VC-DSPPT” repair  
procedures.  
g. These errors are not related to VSP-MCU. They could be caused by  
network problems or from the customer endpoints. They are presented  
here for logging purposes only:  
Code  
3841  
Description  
CRC4 Error (Frame checksum error)  
3842  
3843  
3844  
Correctable BAS (Control msg single or double bit error, but  
correctable)  
Uncorrectable BAS (Control msg bit error -three or more bit,  
uncorrectable)  
Protocol Error (H.221 Protocol error from endpoint detected)  
System Technician-Demanded Tests:  
Descriptions and Error Codes  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Resource Looparound Test (#1111)  
X
X
D
1. D = Destructive; ND = Nondestructive  
Resource Looparound Test (#1111)  
This test is destructive.  
This test checks the connectivity of the resource within MMI circuit pack and out  
to the TDM bus. The object is to test the circuitry that an H.221 bit stream comes  
in contact with when that stream is demultiplexed, pre-processed, written to the  
TDM bus and then reread (looped in the TSI), post-processed, multiplexed, and  
then written back to the TDM bus for verification. The video, audio, and data  
components of the bit stream are tested separately. If any one of these tests fails,  
then the resource is taken out of service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-PT  
3
3-849  
Table 3-368. TEST #1111 Resource Looparound Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
System resources required to run this test are not available. The port may be  
busy with a valid call.  
1. Retry the command at 1-minute intervals a maximum of five times.  
2. Use the status conference command to determine if there is an active  
conference. If a call is active, the test cannot be run until the conference  
call terminates.  
1002  
ABORT  
The system could not allocate time slots for the test. The traffic load on the  
system may be very high or time slots may be out-of-service due to TDM-Bus  
errors. Refer to ‘‘TDM-BUS (TDM Bus)’’ to diagnose any active TDM Bus  
errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat the test at 1-minute intervals a maximum of five times.  
1003  
ABORT  
The system could not allocate a tone detector for the test. The system is  
oversized for the number of tone detectors present or some tone detectors  
are out-of-service.  
1. Resolve any ‘‘TTR-LEV (TTR Level)’’ errors in the Error Log.  
2. Resolve any ‘‘TONE-PT (Tone Generator)’’ errors in the Error Log.  
3. If neither condition exists, retry the test at 1-minute intervals a maximum  
of five times.  
1004  
2000  
ABORT  
ABORT  
The resource has been seized by a user for a valid call. Use the status  
conference command to verify that there is a conference call active.  
1. If there are no conference calls, retry the command at 1-minute intervals  
a maximum of five times.  
Response to the test was not received from the Tone Detector circuit pack  
within the allowable time period.  
1. If this result occurs repeatedly, reset the circuit pack, if the other ports  
are not in use. Reset the circuit pack by issuing the busyout board  
PCSSpp and the reset board PCSSpp commands, followed by the  
release board PCSS command.  
2. If this result occurs again, replace the circuit pack.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary resources to run this test. Abnormal abort.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-PT  
3
3-850  
Table 3-368. TEST #1111 Resource Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
0, 1, 2  
FAIL  
This resource cannot guarantee data integrity and is out-of-service.  
The following error codes indicate failure of a particular media loop:  
0 = video  
1 = audio  
2 = low-speed data  
1. Replace the circuit pack  
PASS  
The resource is functioning normally.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-SYNC  
3
3-851  
MMI-SYNC  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
Full Name of MO  
Multimedia Interface Circuit Pack  
MMI-SYNC  
MINOR  
test board PCSS l r#  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or  
C); and SS is the address of the slot in the carrier where the circuit pack is located (for example,  
01, 02, ..., and so forth).  
NOTE:  
Refer to ‘‘Troubleshooting Multimedia Call Handling (MMCH)’’ in Chapter 1  
for MMCH troubleshooting information.  
Each Port Network (PN) must have a TN787D or later MMI circuit pack assigned  
as the Multimedia Interface (MMI) master synchronization source for that PN. If  
one or more MMI circuit pack is administered in a PN, one MMI circuit pack is  
designated as the master synchronization source for all MMI circuit packs within  
that PN.  
The MMI circuit pack generates a synchronization signal and puts that signal on  
the TDM bus. Other MMI packs or any other circuit pack within a PN can listen to  
this signal and “synchronize up” to it. The first MMI circuit pack inserted in a PN  
is normally designated as the master. As subsequent MMI packs are inserted,  
they are instructed to listen and synchronize to the time-slot of the master MMI. In  
the unlikely case of an MMI losing this reference, an uplink message is sent from  
the MMI circuit pack that lost the signal to maintenance, which also clears the  
“event” counter on this MMI with a downlink message. This forces the MMI circuit  
pack to return the current state of the synchronization signal. If the signal is still  
lost, then the recovery algorithm is entered. Note that during this time, the MMI  
circuit pack synchronizes to its internal clock, and there should be no service  
disruption. A loss of synchronization is usually the result of a circuit pack failure.  
The maintenance strategy is to switch the master source away from the bad pack  
to another healthy MMI circuit pack within the PN.  
A synchronization switch takes place if half or more of the MMI circuit packs in a  
PN report a loss of synchronization. For example, a PN with two MMIs reporting a  
loss of sync source switches immediately, three and four MMIs switch if two  
report the loss, and so forth. A healthy MMI circuit pack becomes the master  
synchronization source providing the signal on a new timeslot. The other MMI  
circuit packs within the PN are instructed to listen to this new signal, and the old  
master stops providing the signal and now listens to the new master MMI. If an  
MMI is physically removed from the system, then the remaining MMIs report the  
loss of synchronization. The first MMI with no alarms present becomes the new  
master of that PN. Once a synchronization switch has occurred, another switch is  
not allowed for 15 minutes to avoid hyperactive switching. If all the MMIs have  
alarms, then nDoowsnwloiatcd hfroims Wmwawd.Seo.manuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
MMI-SYNC  
3
3-852  
If the MMI circuit pack that provides synchronization is craft busied out, it will not  
affect the PN synchronization. The signal is still provided by the busied-out pack.  
There is no affect on synchronization if the technician issues a release of the  
busied-out MMI. Synchronization is not affected by a warm start of the system  
(reset system 1). For all other restarts (reboot through cold 2), MMI  
synchronization recovers during board insertion.  
Error Log Entries and Test to Clear Values  
Table 3-369. MMI-SYNC Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
None  
Alarm Level  
Test to Clear Value  
1
1
Any  
Any  
See note  
2
257  
None  
MINOR  
OFF  
See note  
1. An MMI synchronization switch was successful. Refer to MMI-BD errors for the reason for the  
switch.  
2. The requested MMI synchronization switch failed. Resolve all MMI-BD alarms.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
There are no system technician-demanded tests for MMI-SYNC.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-853  
OPS-LINE (DS1 OPS Line)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test station <ext> l  
Full Name of MO  
DS1OPS Line  
OPS-LINE  
OPS-LINE  
MINOR  
WARNING  
test station <ext>  
DS1OPS Line  
An analog Off-Premises Station (OPS) can be connected to the system through a  
DS1 link. A TN767 DS1 Interface circuit pack supports up to 24 DS1OPSs. Since  
the DS1OPS is an analog telephone set, a channel multiplexer is necessary as  
the remote DS1 endpoint that converts the digital signal of a DS1 port to the OPS  
Line and vice versa. See Figure 3-37 for details.  
The DS1OPS Line Maintenance provides a strategy to maintain an OPS Line via a  
port of the DS1 Interface circuit pack. The strategy covers initialization tests,  
periodic tests, system technician-demanded tests, and alarm resolution and  
escalation. Two service states are specified in a DS1OPS Line maintenance.  
They are: out-of-service in which the line is in a deactivated state and cannot be  
used for either incoming or outgoing calls; in-service in which the line is in an  
activated state and can be used for both incoming and outgoing calls. If the DS1  
Interface circuit pack is out-of-service, then all lines on the DS1 Interface circuit  
pack are put into the out-of-service state, and a Warning alarm is raised.  
For maintenance of the remote DS1 endpoint (for example, Channel Division  
Multiplexer, D4 Channel Bank), refer to the maintenance documentation from its  
vendor for details.  
ANALOG  
STATION  
"DEFINITY"  
CHANNEL  
MULTIPLEXER  
COMMUNICATIONS  
SYSTEM  
DS1  
DS1 LINK  
ANALOG  
STATION  
Figure 3-37. DS1 OPS Line Interactions  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-854  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-370. DS1 OPS Maintenance Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Any  
Alarm Level  
Test to Clear Value  
1
0
0
Any  
Any  
test station <ext> sh r 1  
15 (a)  
Any  
Audit and Update  
Test (#36)  
18 (b)  
130 (c)  
1281  
0
busyout station <ext> WARNING  
OFF  
ON  
release station <ext>  
test station <ext>  
test station <ext> l  
None  
WARNING  
MINOR  
Conference Circuit  
Test (#7)  
ON  
1537  
NPE Crosstalk Test  
(#6)  
MINOR  
ON  
test station <ext> l  
1793 (d)  
test circuit pack PCSS l  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. This is a software audit error that does not indicate any hardware  
malfunction. Run the Short Test Sequence and investigate associated  
errors (if any).  
b. The DS1OPS Line has been busied out by a busyout station <ext>  
command. No calls can be made on this line.  
c. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
d. Error Type 1793 indicates a problem with the DS1 Interface circuit pack.  
Since there is no error against the OPS-LINE port, no alarm is raised  
against the OPS-LINE port. However, there should be errors logged  
against the DS1 Interface circuit pack. Look for DS1-BD errors in the  
Hardware Error Log and follow procedures provided in the DS1-BD (DS1  
Interface Circuit Pack) Maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-855  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the NPE  
Crosstalk Test, for example, you may also clear errors generated from other tests  
in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
X
X
X
Conference Circuit Test (#7)  
ND  
DS1OPS Switchhook Inquiry Test (#312)  
Audit and Update Test (#36)  
X
X
ND  
ND  
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per-port basis The NPE Crosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is usually only part of a port’s Long Test Sequence  
and takes about 20 to 30 seconds to complete.  
Table 3-371. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Could not allocate system resources to run this test or an internal system  
error (software) occurred.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT  
System resources required to run this test are not available. The port may be  
in use on a valid call. Use status station or status trunk command to  
determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1001  
ABORT  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-856  
Table 3-371. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1002  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due to  
TDM-BUS errors. Refer to TDM-BUS (TDM Bus) Maintenance  
documentation to diagnose any active TDM-BUS errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat the test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
(TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a maximum  
of 5 times.  
1004  
1020  
ABORT  
ABORT  
The test was aborted because the port was seized by a user for a valid call.  
Use status station command to determine the service state of the port. If  
the service state indicates that the port is in use, then the port is unavailable  
for certain tests. You must wait until the port is idle before retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test did not run due to an an already existing error on the specific port or  
due to a more general error on the circuit pack.  
1. Examine the error log for existing errors against this port or the circuit  
pack and attempt to diagnose the already existing error. (Error code  
1793 indicates a problem with the DS1 interface board, and any  
problems on the associated DS1-BD or UDS1-BD should be resolved  
first.)  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test aborts with error code 2000 again, run short test sequence on  
the associated DS1-BD or UDS1-BD. If tests 138 through 145 on the  
associated DS1-BD or UDS1-BD are also aborting with error code 2000,  
hyperactivity on the board or facility is indicated. In this case, the  
hyperactivity problem should be dealt with first.  
2100  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-857  
Table 3-371. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Any  
FAIL  
The test failed. This can be due to on-board or off-board problems.  
Off-board problems of concern include EXP-INTF faults, TDM-BUS faults,  
and faults associated with the tone detectors/tone generators. Clear all  
off-board problems before replacing the board. Keep in mind that a  
TDM-BUS problem is usually the result of a faulty board connected to the  
backplane or bent pins on the backplane.  
1. Look for TONE-BD and/or TONE-PT errors in the error log. If present,  
refer to the TONE-BD Maintenance documentation and to the TONE-PT  
Maintenance documentation.  
2. Retest when the faults from step 1 are cleared.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles on  
this port should be investigated using other port tests and by examining  
station, trunk, or external wiring.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Conference Circuit Test (#7)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per-port basis. The Conference Circuit Test verifies that the NPE channel for the  
port being tested can correctly perform the conferencing function. The NPE is  
instructed to listen to several different tones and conference the tones together.  
The resulting signal is then measured by a Tone Detector port. If the level of the  
tone is within a certain range, the test passes.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-858  
Table 3-372. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port  
may be in use on a valid call. Use the status station or status trunk  
command to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
ABORT  
The test was aborted because the system could not allocate time slots  
for the test. The system might be under heavy traffic conditions, or it  
might have time slots out of service due to TDM-BUS errors. (The  
status health command may be used to determine whether the system  
is experiencing heavy traffic.) Refer to the TDM-BUS (TDM bus)  
Maintenance documentation to diagnose any active TDM-BUS errors.  
1. If the system has no TDM-BUS errors, is not handling heavy traffic,  
and the port status is idle, retry the command at 1-minute intervals  
for a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system  
may be oversized for the number of tone detectors present or some of  
the tone detectors may be out of service. Issue the list measurements  
tone-receiver command to display basic information about the  
system’s tone receivers.  
1. Look for TTR-LEV errors in the error log. If present, refer to the  
TTR-LEV Maintenance documentation.  
2. Look for TONE-PT errors in the error log. If present, refer to the  
TONE-PT Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals for a  
maximum of 5 times.  
1004  
1018  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use status station  
or status trunk command to determine when the port is available for  
testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test was disabled via translation.  
1. You may want to determine why the test has been disabled before  
you enable it.  
2. To enable the test for the particular analog station being tested,  
enter the change station extension command, and then change  
the Testfield on the Station form to y.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-859  
Table 3-372. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1020  
ABORT  
The test did not run due to an already existing error on the specific port  
or due to a more general error on the circuit pack.  
1. Examine the error log for existing errors against this port or the  
circuit pack and attempt to diagnose the already existing error.  
(Error code 1793 indicates a problem with the DS1 interface board,  
and any problems on the associated DS1-BD or UDS1-BD should  
be resolved first.)  
2000  
ABORT  
The test was aborted because response to the test was not received  
within the allowable time period.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2. If the test aborts with error code 2000 again, run short test  
sequence on the associated DS1-BD or UDS1-BD. If tests 138  
through 145 on the associated DS1-BD or UDS1-BD are also  
aborting with error code 2000, hyperactivity on the board or facility  
is indicated. In this case, the hyperactivity problem should be dealt  
with first.  
2100  
Any  
ABORT  
FAIL  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The NPE of the tested port did not conference the tones correctly. This  
can cause noisy and unreliable connections.  
1. Enter the list configuration board PCSS command. If the circuit  
pack is a TN767B vintage 8 or 9, replace the circuit pack with a  
TN767C V3 or later. The error log may have error type 1281 entries.  
2. Test all administered trunks on the board. If one fails, this could be  
an off-board problem (such as an incoming seizure or an off-hook  
port seizure during the test). Retest the board.  
3. If all of the ports fail, check the CARR-POW (see note below).  
4. If several ports fail, check the error log for TONE-BD or TONE-PT  
errors. If there are such errors, take the appropriate action. When  
the TONE errors have cleared, rerun the test.  
5. If the retry passes and troubles have been reported, coordinate  
isolation with the far-end PBX. Make sure that the near-end and  
far-end switches and any NTCE equipment (the CSUs) have the  
correct administration.  
6. Replace the circuit pack.  
NOTE:  
If the conference circuit test fails for all ports on a circuit pack, a  
-5 volt power problem is indicated.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-860  
Table 3-372. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The port can correctly conference multiple connections. User-reported  
troubles on this port should be investigated using other port tests and  
by examining station, trunk, or external wiring.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
Continued on next page  
Audit and Update Test (#36)  
This test sends port level translation data from switch processor to the DS1  
Interface circuit pack to assure that the trunk’s translation is correct. Translation  
updates include the following data: trunk type (in/out), dial type, timing  
parameters, and signaling bits enabled. The port audit operation verifies the  
consistency of the current state of the trunk as kept in the DS1 Interface circuit  
pack and in the switch software.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-861  
Table 3-373. TEST #36 Audit and Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Internal System Error.  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
The test was aborted because system resources required to run this  
test were not available. The port may be busy with a valid call. Use the  
display port PCSSpp command to determine the station extension of  
the port. Use the status station command to determine the service  
state of the port. If the service state indicates that the port is in use, then  
the port is unavailable for certain tests. You must wait until the port is  
idle before retesting.  
1. If the port is idle, retry the command at 1-minute intervals a  
maximum of 5 times.  
1006  
ABORT  
The test was aborted because the station is out of service. This  
condition may be accompanied by an error type 18 entry in the error  
log. You may want to determine why the station was taken out of  
service. (When stations are taken out of service by maintenance  
software, the problems that preceded that point must be cleared.)  
1. Use the status station command to check the service state of the  
port. If the port is indeed out of service, enter the release station  
command to bring the station back into service.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
3. If the test continues to abort, and the service state indicates that  
the station is in service and idle, escalate the problem.  
2000  
ABORT  
The test was aborted because response to the test was not received  
within the allowable time period.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2. If the test aborts with error code 2000 again, run short test  
sequence on the associated DS1-BD or UDS1-BD. If tests 138  
through 145 on the associated DS1-BD or UDS1-BD are also  
aborting with error code 2000, hyperactivity on the board or facility  
is indicated. In this case, the hyperactivity problem should be dealt  
with first.  
2100  
ABORT  
FAIL  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Test failed due to internal system error. Do not replace port board.  
7 or 8  
■ Error code 7: the failure occurred during station translation  
download (to DS1 Interface circuit pack).  
■ Error code 8: the failure occurred during station ringer update.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-862  
Table 3-373. TEST #36 Audit and Update Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
Trunk translation has been updated successfully. The current trunk  
states kept in the DS1 Interface circuit pack and switch software are  
consistent.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This  
could be due to incorrect translations, no board is inserted, an incorrect  
board is inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
dispatch to check to ensure that there is a valid board inserted.  
DS1 OPS Switchhook Inquiry Test (#312)  
This test initiates the Switchhook Audit Test. The test queries the switchhook state  
of the Off-Premises-Station in switch software. If the state in switch software  
disagrees with the state on the DS1 Interface circuit pack. The state in the switch  
software is updated to match the state on the DS1 Interface circuit pack.  
Table 3-374. TEST #312 DS1OPS Switchhook Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal System Error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1004  
The port has been seized by a user for a valid call. Use the status station  
command to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-863  
Table 3-374. TEST #312 DS1OPS Switchhook Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1005  
1006  
ABORT  
Test failed due to incompatible configuration administered in station  
administration.  
1. Verify the station administration is the station assigned to Port 24 of the  
DS1 Interface circuit pack while common channel signaling is specified.  
ABORT  
The test was aborted because the station is out of service. This condition may  
be accompanied by an error type 18 entry in the error log. You may want to  
determine why the station was taken out of service. (When stations are taken  
out of service by maintenance software, the problems that led up to that must  
be cleared.)  
1. Use the status station command to check the state of the port. If the port  
is indeed out of service, enter the release station command to bring the  
station back into service.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
3. If the test continues to abort, and the station is in the in-service/idle state,  
escalate the problem.  
1020  
2000  
ABORT  
ABORT  
The DS1 Interface circuit pack is out-of-service.  
1. Look for DS1-BD errors in Hardware Error Log. If present, refer to the  
DS1-BD (DS1 Interface Circuit Pack) Maintenance documentation.  
2. Retry the command.  
The test was aborted because response to the test was not received within  
the allowable time period.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2. If the test aborts with error code 2000 again, run short test sequence on  
the associated DS1-BD or UDS1-BD. If tests 138 through 145 on the  
associated DS1-BD or UDS1-BD are also aborting with error code 2000,  
hyperactivity on the board or facility is indicated. In this case, the  
hyperactivity problem should be dealt with first.  
2012  
2100  
ABORT  
ABORT  
The test was aborted due to a system error.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Internal System Error.  
1
FAIL  
1. Look for DS1-BD errors in the Hardware Error Log. If present, refer to the  
DS1-BD (DS1 Interface Circuit Pack) Maintenance documentation.  
2. If a channel multiplexer is used as the remote DS1 endpoint to which the  
station connects, refer to the multiplexer vendor’s maintenance document  
for diagnosis.  
3. Retry the command at 1-minute intervals a maximum of 5 times  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
OPS-LINE (DS1 OPS Line)  
3-864  
Table 3-374. TEST #312 DS1OPS Switchhook Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The station hook states in both switch software and DS1 Interface circuit pack  
are consistent.  
0
2012  
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the linkage  
between the internal ID and the port. If this is not the case, dispatch to  
check to ensure that there is a valid board inserted.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-865  
PE-BCHL (PRI Endpoint Port)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run Full Name of MO  
1
PE-BCHL  
MINOR  
test port PCSSpp l  
test port PCSSpp sh  
PRI Endpoint Port  
PRI Endpoint Port  
PE-BCHL  
WARNING  
1. For additional repair information, see also UDS1-BD (UDS1 Interface Circuit Pack)  
maintenance documentation and ‘‘Troubleshooting PRI Endpoint Problems’’ in  
Chapter 1, ‘‘Maintenance for csi systems’’.  
A PRI Endpoint provides ISDN-PRI (Primary Rate Interface) connections for  
customers with application equipment or terminal adapters that terminate  
ISDN-PRI. The equipment or terminal adapters are connected to the switch via  
the UDS1 interface circuit pack. PRI Endpoint Port (PE-BCHL) maintenance  
provides a strategy to maintain PRI Endpoint Port hardware circuitry on the UDS1  
circuit pack. The maintenance strategy involves logging PRI Endpoint Port  
hardware errors, running tests for port initialization, periodic and scheduled  
maintenance, system technician-demanded tests, and alarm escalation and  
resolution.  
Wideband Switching  
The Wideband Switching capability supports end-to-end connectivity between  
customer endpoints at data rates from 128 to 1536 kbps over T1 facilities and to  
1984 kbps over E1 facilities. DEFINITY switching capabilities are extended to  
support wideband calls comprised of multiple DS0s that are switched end-to-end  
as a single entity.  
The Wideband Switching capability is designed for ISDN application equipment  
(for example, ISDN video codecs), but it retains provisions for non-ISDN  
application equipment by using PRI terminal adapters. In the same sense that a  
DEFINITY data module acts as a DCP or BRI terminal adapter between endpoint  
data (for example, V.35) and dialing (for example, RS-366) interfaces and a DCP  
interface, a PRI terminal adapter acts as a wideband terminal adapter between  
endpoint data and dialing interfaces and DEFINITY’s line-side ISDN PRI  
interface.  
The Wideband Switching Capability introduces PRI Endpoints on DEFINITY  
line-side interfaces. A PRI Endpoint consists of one or more contiguous  
B-channels on a line-side T1 or E1 ISDN PRI facility, and it has an extension  
number. Endpoints initiate and receive calls using ISDN SETUP messages that  
indicate the data rate and specific B-channels to be used, and they  
communicate all other call status information via standard ISDN messages. Any  
DEFINITY ISDN signaling set (for example, AT&T, CCITT, ECMA) may be used for  
a line-side ISDNPRI facility.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-866  
Multiple PRI Endpoints on a one line-side facility are separate and distinct within  
the facility. Non-overlapping contiguous sets of B-channels are associated with  
each PRI Endpoint, and the endpoint equipment is expected to initiate calls  
within these boundaries.  
The endpoint application equipment must be able to do the following: use  
standard ISDN-PRI signaling, adhere to the PRI Endpoint boundaries as  
administered on DEFINITY when initiating calls, and handle incoming calls  
appropriately based on the PRI Endpoint.  
Signaling and B-channel States  
These ports use a separate channel for signaling (for example, for call setup).  
This mode of operation is known as out-of-band signaling. The separate  
signaling channel is called a D-channel in ISDN terminology, and it carries all the  
call control signaling messages for the PRI Endpoint Port B-channels. The  
D-channel for these B-channels is an ISDN-PRI Signaling Link Port (ISDN-LNK).  
The signaling protocol used on the ISDN-PRI Signaling Link Port D-channel is  
defined by one of the four selectable ISDN-PRI Specifications: AT&T, CCITT,  
ECMA, and ANSI.  
The ISDN-PRI Specification defines the possible SERVICE STATES for a  
B-channel. The service state is negotiated with the far-end terminal adapter, and  
it changes over time. Also, the service state may have a far-end or near-end  
component, and it is initialized to the Out-Of-Service/Far-End state. An attempt is  
made to negotiate the service state to In-Service.  
NOTE:  
The service state of a particular PRI Endpoint Port B-channel can be  
displayed by issuing the status pri-endpoint <extension> system  
technician command.  
If a call is present, the ISDN-PRI Specification defines the permissible CALL  
STATES as well. There are tests in the short and long test sequences for PRI  
Endpoint Port that are designed to audit these states and to ensure agreement  
between both ends of the PRI wideband connection.  
Alarming Based on Service States:  
A PRI Endpoint Port B-channel is alarmed with a WARNING if it is placed into a  
Maintenance/Far-End or Out-Of-Service/Far-End state. While in such a state, the  
port is unusable for calls to the terminal adapter. However, the user can still use  
the other remaining ports in the PRI Endpoint to make calls to and from the  
terminal adapter. When a WARNING alarm is raised, the status pri-endpoint  
<extension> command should be used to determine the exact state of the port.  
Other alarms can be diagnosed by using the short and/or long test sequences.  
Note that a PRI Endpoint Port B-channel can be placed into a Far-End Service  
State either by direct action of the far-end terminal adapter or by inaction of the  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-867  
far-end terminal adapter. For example, if they do not respond to a Remote Layer  
3 Query (see Test #260 for ISDN-PRI Signaling Link Port), the associated PRI  
Endpoint Port B-channels are placed into the Maintenance/Far-End service state.  
A PRI Endpoint Port is a port on a UDS1 interface circuit pack. Therefore, this  
port depends on the health of the UDS1 interface circuit pack for proper  
operation (see Figure 3-38). As noted earlier, a PRI Endpoint Port B-channel also  
depends on an ISDN-PRI Signaling Link Port D-channel (ISDN-LNK) to carry the  
signaling traffic. If there is a problem with the ISDN-PRI Signaling Link Port, the  
PRI Endpoint Port is affected. The ISDN-PRI Signaling Link Port, in turn, depends  
on the PKT-INT (Packet Interface).  
SIGNALING  
ISDN-LNK  
(PORT 24)  
UDS1  
TERMINAL  
ADAPTER  
INTERFACE  
CIRCUIT  
PACK  
PI  
CIRCUIT  
PACK  
(TN765)  
PROCESSOR  
(TN773)  
DATA  
(TN464C)  
PE-BCHL  
(PORT 23)  
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
DATA  
PE-BCHL  
(PORT 1)  
TDM  
BUS  
Figure 3-38. PRI Endpoint Port Interactions [INTEL]  
PRI Endpoint Port Service States  
This section defines the possible service states of a PRI Endpoint Port, and it  
explains the reason for each service state. This section also provides the  
recommended recovery procedures (when required).  
Service States  
■
In-Service (INS)  
The B-channel is in its normal operating state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-868  
■
■
■
Out-of-Service/Far-end (OOS/FE)  
A B-channel is initialized to this state when administered. The switch  
sends messages to the far-end terminal adapter to negotiate the  
B-channel into service. If the far-end terminal adapter does not respond to  
the messages within a certain time period, the service state remains  
out-of-service, and maintenance periodically resends the messages. The  
port is unusable for calls incoming to the switch and outgoing to the  
terminal adapter (although other ports in the PRI Endpoint can still be  
used for incoming and outgoing calls).  
Out-of-Service/Near-end (OOS/NE)  
This is the state of the port whenever one of the following is true: a  
hardware failure exists on the signaling link, the NPE Crosstalk Test fails, or  
the port is busied out by system technician. In this state, the port is  
unusable for calls incoming to the switch or outgoing to the terminal  
adapter (although other ports in the PRI Endpoint can still be used for  
incoming and outgoing calls). No messages are sent to the far-end  
terminal adapter until the signaling link comes back into service or until  
the port is released by system technician.  
Maintenance/Far-end (MTC/FE)  
This state is reached when the far-end terminal adapter does not respond  
to messages sent over the signaling link for a particular port after a certain  
amount of time. This state is different from OOS/FE inasmuch as the  
signaling link must be up initially and the B-channels must be in-service.  
The switch periodically sends messages to the far-end terminal adapter in  
an attempt to negotiate the port (B-channel) into service. The port is  
unusable for calls outgoing to the terminal adapter. However, the port  
services incoming call requests from the far-end (although other ports of  
the PRI Endpoint can still be used to answer calls incoming to the switch  
or to place outgoing calls to the terminal adapter). Note that transitions  
into MTC/FE do not drop stable calls. Therefore, if the service state  
changes from in-service to MTC/FE, stable calls are unaffected.  
■
Maintenance/Near-end (MTC/NE)  
The port (B-channel) is in this state if the signaling link (PKT-INT) is busied  
out by system technician. The port (B-channel) is also temporarily in this  
state if the system technician has issued a test port PCSSpp l or a test  
pri-endpoint <extension> l command. Note that transitions into MTC/NE  
do not drop stable calls. Therefore, a system technician-demanded  
busyout link lnk-no command does not drop stable wideband calls. In  
this state, the B-channel is not usable either for new calls incoming to the  
switch or for new calls outgoing to the terminal adapter.  
■
Pending States (PEND)  
If the near-end is expecting a timed response from the far-end for a  
request to change the service state of a port, the state of the port reflects a  
Pending state. For example, if the port is out-of-service/far-end and if an  
in-service message is sent to the far-end, the service state of the port is  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-869  
OOS/FE-PEND/INS(that is, out-of-service/far-end-Pending/in-service). The  
far-end has a certain amount of time to respond to the message. The  
service state reflects this pending state until the timer expires.  
The following diagram of the PRI Endpoint Port service states shows the common  
progression from one service state to another and the event that caused the  
change of state.  
OUT-OF-  
MAINTENANCE  
NEAR END  
SERVICE  
NEAR END  
CRAFT BUSYOUT OF B-CHANNEL  
BUSYOUT PORT/PRI-ENDPOINT,  
LINK PROBLEM AT NEAR END  
(PI-LINK OR SYS-LINK),  
DS1 BOARD NOT INSERTED,  
OR DS1 BOARD FAILURE.  
CRAFT RELEASE OF  
A B-CHANNEL OR  
NEAR-END LINK  
PROBLEM (PI-LINK OR  
SYS-LINK) CLEARS UP  
CRAFT BUSYOUT OF  
SIGNALING LINK  
CRAFT RELEASE  
OF SIGNALING LINK  
"BUSYOUT LINK LINK-NO",  
OR TRANSIENT STATE FOR  
CRAFT-DEMANDED LONG  
TEST OF THE PORT.  
ADMINISTER  
B-CHANNEL AS  
MEMBER OF A  
D-CHANNEL HAS BEEN  
DOWN FOR AT LEAST  
90 SECONDS.  
PRI ENDPOINT  
OUT-OF-  
SERVICE  
FAR END  
IN-SERVICE  
MAINTENANCE  
FAR END  
FAILED TO  
RECEIVE REPLY  
FAILED TO  
FROM FAR END.  
MTCE WILL  
RECEIVE REPLY  
FROM FAR END.  
MTCE WILL  
PERIODICALLY  
TRY TO RESEND  
THE MESSAGE  
PERIODICALLY  
TRY TO RESEND  
THE MESSAGE  
IF D-CHANNEL  
CONTROLLING THE  
B-CHANNEL IS UP,  
SEND A MESSAGE  
REQUESTING  
IF D-CHANNEL  
CONTROLLING THE  
B-CHANNEL IS UP,  
SEND A MESSAGE  
REQUESTING  
TRANSITION  
TRANSITION  
TO IN-SERVICE  
RECEIVED  
ACKNOWLEDGEMENT  
FROM THE FAR END  
RECEIVED  
ACKNOWLEDGEMENT  
FROM THE FAR END  
TO IN-SERVICE  
OUT-OF-  
SERVICE  
FAR END  
PENDING  
MAINTENANCE  
FAR END  
PENDING  
IN-SERVICE  
IN-SERVICE  
Figure 3-39. Common Progressions in Service States  
PRI Endpoint Port Service States  
The following table summarizes each of the different PRI Endpoint Port service  
states that can result when the status pri-endpoint <extension> command is  
issued. From the results of the status command, match the service state to the  
corresponding column. Proceed down the column until an "X" is found. The left  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-870  
column indicates possible reasons why the port is in this state, and the right  
column suggests possible recovery mechanisms. If an alarm against PE-BCHL is  
present, it is indicated below the "X."  
NOTE:  
Refer to ‘‘Troubleshooting PRI Endpoint Problems’’ in Chapter 1,  
‘‘Maintenance for csi systems’’ for a layered approach to the processing of  
PRI Endpoint problems.  
Table 3-375. PRI Endpoint Port Service States  
Possible  
Problem  
Source  
Possible Recovery  
Route  
ISDN  
X
Normal Operation.  
wideband  
calls being  
completed.  
Port busied  
out by  
system  
X Warn  
Alarm  
Release port by the  
release pri-endpoint  
extension or release  
port PCSSpp.  
technician?  
NPE  
Crosstalk  
Test failed?  
X
Minor  
Alarm  
Replace UDS1  
Interface CP.  
DS1 circuit  
pack lost  
signal?  
X
UDS1 Interface CP  
removed?  
DS1 cable  
disconnected?  
Terminal adapter  
problems?  
Far-end terminal  
adapter restarting?  
Faulty UDS1 Interface  
CP?  
Check  
UDS1-BD.  
Refer to UDS1-BD for  
repair procedures.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-871  
Table 3-375. PRI Endpoint Port Service States — Continued  
Possible  
Problem  
Source  
Possible Recovery  
Route  
Far-end  
problems?  
X
Check administration  
and the status of the  
corresponding port  
on the far-end  
Warn Alarm  
terminal adapter.  
Service  
X
X
Wait a couple minutes  
until Pending State  
not present, check  
service state.  
Message  
sent, waiting  
for reply  
from far-end  
terminal  
adapter (2  
minutes).  
Processor  
Interface  
Link busied  
out by  
X
Release link by the  
release link lnk-no.  
system  
technician?  
Check link  
status.  
[MIPS only].  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-872  
Table 3-375. PRI Endpoint Port Service States — Continued  
Possible  
Problem  
Source  
Possible Recovery  
Route  
Signaling  
link has  
been down  
for over 90  
seconds?  
X
See ISDN-SGRP,  
ISDN-LNK, PKT-INT  
and/or SYS-LINK and  
follow repair  
Warn Alarm  
procedures.  
Is far-end terminal  
adapter currently  
restarting?  
Repeated  
failure of  
far-end to  
respond to  
messaging?  
X
Periodically  
Warn Alarm  
Maintenance will try to  
resend messages. To  
speed process, run  
system  
technician-demanded  
test test port  
PCSSpp (Test #256).  
Far-end port  
busied out  
(OOS/FE).  
X
X
Check status of  
far-end terminal  
adapter.  
Warn Alarm  
Warn Alarm  
Far-end port  
being tested  
(MTCE/FE).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-873  
Error Log Entries and Test to Clear Values  
Table 3-376. PRI Endpoint Port Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test port PCSSpp sh r 1  
test port PCSSpp sh r 1  
1 (a)  
Any  
Any  
None  
15 (b)  
Audit and Update  
Test (#36)  
18 (c)  
0
busyout pri-endpoint  
<extension> busyout  
port <PCSSpp>  
WARNING  
OFF  
release pri-endpoint  
<extension> release port  
<PCSSpp>  
129 (d)  
130 (e)  
257 (f)  
513 (g)  
76 9 (f)  
None  
None  
None  
None  
None  
WARNING  
WARNING  
OFF  
ON  
test port PCSSpp sh r 1  
test port PCSSpp sh  
Any  
Any  
Any  
test port PCSSpp sh r 1  
test port PCSSpp sh r 1  
test port PCSSpp sh r 1  
test port PCSSpp l r 4  
WARNING  
OFF  
1281 (h) Any  
Conference Circuit  
Test (#7)  
MINOR  
MINOR  
ON  
ON  
1537 (i)  
Any  
NPE Crosstalk Test  
(#6)  
test port PCSSpp l r 3  
1793 (j)  
3073 (k)  
Any  
Any  
None  
test port PCSSpp sh r 1  
test port PCSSpp sh r 2  
Service State Audit  
(#256)  
3585 (l)  
Any  
None  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. This error type indicates a disagreement between the switch and the  
terminal adapter at the other end of the connection with regard to the  
ISDN call state of the PRI Endpoint Port. This switch automatically tries to  
recover by clearing the call (that is, the call is torn down). The status  
pri-endpoint <extension> command can be used to determine the state  
of the port.  
When running the Short Test Sequence of tests, pay close attention to the  
resultsDoofwtnhloeadCfarolml SWtawtwe.SAomudanituaTles.scotm(#. A2l5l M7a).nuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-874  
b. This is a software audit error that does not indicate any hardware  
malfunction. Run the Short Test Sequence and investigate the associated  
errors (if any).  
c. The PRI Endpoint Port has been busied out by a busyout pri-endpoint  
<extension> command or by a busyout port <PCSSpp> command. No  
wideband calls can be made to this port (although wideband calls can still  
be made to other ports within this PRI Endpoint if others ports are in  
service).  
d. The far-end terminal adapter changed its ISDN service state to either  
"out-of-service" or "maintenance." This may be a temporary condition due  
to the testing of this port by the far-end terminal adapter or by a hardware  
problem with the port. Outgoing calls to the terminal adapter are not  
allowed over the port (although calls can still be made to other ports that  
are in service within the same PRI Endpoint). To investigate the status of  
the port, issue the status pri-endpoint <extension> command.  
e. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
f. This error type indicates a disagreement between this switch and the  
terminal adapter at the other end of the connection with regard to the  
ISDN service state of the PRI Endpoint Port. This switch tries to recover by  
performing a service state audit. The status pri-endpoint <extension>  
command can be used to determine the state of the port.  
When running the Short Test Sequence, pay close attention to the results  
of the Service State Audit Test (#256).  
g. This port is not recognized by the far-end terminal adapter. Investigate the  
PRI Endpoint administration for both the switch and the terminal adapter  
and make changes as necessary.  
h. The Conference Circuit Test (#7) failed on this port. See Test #7 for the  
repair procedures.  
i. The NPE Crosstalk Test (#6) failed on this port. See Test #6 for the repair  
procedures.  
j. This error indicates a failure of the UDS1 Interface circuit pack. When  
running the Short Test Sequence, the results of the Signaling Link State  
Check Test (#255) are important.  
k. Two Service State Audit attempts have failed (see Test #256). The port is  
not usable for any outgoing calls to the terminal adapter (although  
incoming calls from the terminal adapter are accepted over this port, other  
ports in the PRI Endpoint can still be used for both incoming and outgoing  
calls to and from the terminal adapter) until the test passes and the port  
state is changed to in-service (use the status pri-endpoint <extension>  
command to investigate the port status).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-875  
l. This error type appears when the switch receives an ISDN RESTART  
message for an ISDN port that is not idle. Usually, calls are not cleared via  
the RESTART message. Therefore, this error type may be associated with  
a dropped call report from a user.  
The following Aux Data values for Error Type 3585 represent the port’s  
ISDN call state at the time that the unexpected request to restart the  
channel is received from the remote terminal adapter. This information can  
be useful if dropped calls (cutoffs) are being reported by users of the PRI  
Endpoint.  
The following list contains important Aux values. Any other such values  
can be ignored.  
10  
A call in a stable, talking state was cleared unexpectedly by  
the far-end terminal adapter with an ISDN RESTART  
message. This state is called the "active" state.  
4,  
7,  
8,  
A call that did not reach the active state but at least reached a  
ringing state was cleared unexpectedly by the far-end  
terminal adapter with an ISDN RESTART message.  
260,  
263  
1,  
3,  
6,  
A call that has not yet reached a ringing state was cleared  
unexpectedly by the far-end terminal adapter with an ISDN  
RESTART message.  
9,  
265  
11,  
A call that was in the process of clearing has been  
12,  
19,  
531,  
267,  
268  
nonetheless cleared by the far-end terminal adapter with an  
ISDN RESTART message. If this condition occurs frequently, it  
may mean that the far-end terminal adapter is attempting to  
clear ports that it thinks are in a "hung" state. The RESTART  
message brings the port to an idle condition.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the NPE  
Crosstalk Test, for example, you may also clear errors generated from other tests  
in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-876  
Table 3-377. System Technician-Demanded Tests: DS1-BD  
1
Order of Investigation  
NPE Crosstalk Test (#6)  
Short Test Sequence  
Long Test Sequence  
D/ND  
ND  
X
X
X
X
X
X
Conference Circuit Test (#7)  
Audit and Update Test (#36)  
Signaling Link State Check Test (#255)  
Service State Audit Test (#256)  
Call State Audit Test (#257)  
ND  
X
X
X
X
ND  
ND  
ND  
ND  
1. D = Destructive, ND = Non-destructive  
NPE Crosstalk Test (#6)  
The NPE Crosstalk Test verifies that this port’s NPE channel talks on the selected  
time slot and that it never crosses over to time slots that are reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is usually only part of a port’s long test sequence,  
and takes about 20 to 30 seconds to complete.  
Table 3-378. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use on a valid call. Use status pri-endpoint <extension>  
commands to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1001  
ABORT  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-877  
Table 3-378. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
1002  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM Bus errors. The status health command can be used to determine  
if the system is experiencing heavy traffic. Refer to TDM Bus Maintenance  
to diagnose any active TDM Bus errors.  
1. If system has no TDM Bus errors, and if it is not handling heavy traffic,  
repeat the test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present, or some tone  
detectors may be out-of-service. The list measurements tone-receiver  
command displays information on the system’s tone receiver.  
1. Look for TTR-LEV errors in the Error Log. If errors are present, refer to  
TTR-LEV.  
2. Look for TONE-PT errors in the Error Log. If errors are present, refer to  
TONE-PT.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port has been seized by a user for a valid call. Use status  
pri-endpoint <extension> commands to determine when the port is  
available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
A service state audit message is outstanding.  
1. Wait 2 minutes and then try again.  
1117  
2000  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2020  
2100  
ABORT  
ABORT  
The test did not run due either to an already existing error on the specific  
port or to a more general circuit pack error.  
1. Examine the Error Log for existing errors against this port or the circuit  
pack and attempt to diagnose the already existing error.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-878  
Table 3-378. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
Any  
FAIL  
The NPE of the tested port was found to be transmitting in error. This  
causes noisy and unreliable connections. The PE-BCHL is moved to the  
out-of-service/near-end state.  
1. Replace the circuit pack.  
PASS  
The port is able to communicate over the TDM Bus.  
Conference Circuit Test (#7)  
One or more Network Processing Elements (NPEs) reside on each circuit pack  
with a TDM Bus interface. (The TN464C UDS1 circuit pack has one  
SCOTCH-NPE chip instead of several NPE chips.) The NPE controls port  
connectivity and gain, and it provides conferencing functions on a per port basis.  
The Conference Circuit test verifies that the NPE channel for the port being  
tested can correctly perform the conferencing function. The NPE is instructed to  
listen to several different tones and to conference the tones together. The  
resulting signal is then measured by a tone detector port. If the level of the tone is  
within a certain range, the test passes.  
Table 3-379. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
1004  
ABORT System resources required to run this test are not available. The port may be  
in use on a valid call. Use the status pri-endpoint <extension> command to  
determine when the port is available for testing.  
ABORT The port has been seized by a user for a valid call. Use the status  
pri-endpoint <extension> command to determine when the port is available  
for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1020  
ABORT The test did not run due either to an already existing error on the specific port  
or to a more general circuit pack error.  
1. Examine Error Log for existing errors against this port or against the  
circuit pack, and attempt to diagnose the already existing error.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-879  
Table 3-379. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
2000  
ABORT Response to the test request was not received within the allowable time  
period.  
2100  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Any  
FAIL  
The NPE of the tested port did not conference the tones correctly. This causes  
noisy and unreliable connections.  
1. Replace the circuit pack. Even though wideband calls do not use the  
conferencing feature on the NPE, this failure indicates problems with the  
circuit pack hardware.  
PASS  
The port can correctly conference multiple connections. User-reported  
troubles on this port should be investigated by using the other port tests and  
by examining the terminal adapter or the external wiring.  
Audit and Update Test (#36)  
This test sends port level translation data from the switch processor to the UDS1  
interface circuit pack to ensure that the port’s translation is correct. The port audit  
operation verifies the consistency of the current state of the port that is kept in the  
UDS1 interface circuit pack and in the switch software.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-880  
Table 3-380. TEST #36 Audit and Update Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Internal system error  
2000  
2100  
Response to the test request was not received within the allowable time  
period.  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test failed due to Internal system error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
The port translation has been updated successfully. The current port  
states kept in the UDS1 interface circuit pack and in the switch software  
are consistent. If the port is busied out, the test does not run, but returns  
PASS. To verify that the port is in-service:  
1. Enter status pri-endpoint <extension> to verify that the port is  
in-service. If the port is in-service, no further action is necessary. If the  
port is out-of-service, go to Step 2.  
2. Enter the release pri-endpoint <extension> command or the release  
port <PCSSpp> command to put the port back into in-service.  
3. Retry the test command.  
Signaling Link State Check Test (#255)  
As is noted in the general description for a PRI Endpoint Port, the operation of the  
PRI Endpoint Port depends on the health of the UDS1 interface circuit pack and  
of the TN765 Processor Interface Link. This test checks the status of those critical  
elements.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-881  
Table 3-381. TEST #255 Signaling Link State Check Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1700  
Rollabout video abort. The PRI terminal adapter associated with this PRI  
endpoint extension is detached from the circuit pack. This is a normal abort  
when the rollabout video feature is enabled. To complete the test on this port,  
do one of the following:  
1. Re-attach the disconnected PRI terminal adapter, or  
2. Disable the rollabout video feature on this circuit pack by entering the  
change ds1 PCSS command, and set the field Alarm when PRI  
Endpoint Detached?to y.  
4
8
FAIL  
There is a problem with the Signaling Channel and/or with the Processor  
Interface Link.  
1. Consult the procedure for the ISDN-PRI Signaling Group (ISDN-GRP)  
and/or the procedures for Packet Interface (PKT-INT). Further information  
may also be obtained by consulting the procedures for the ISDN-PRI  
Signaling Channel (ISDN-LNK).  
FAIL  
There is a problem with the UDS1 interface circuit pack.  
1. Consult the procedures for UDS1 interface circuit pack (UDS1-BD).  
The signaling link hardware is okay.  
PASS  
Service State Audit (#256)  
As is noted in the general description for PRI Endpoint Port, these ports may be  
in one of several service states as defined by the ISDN-PRI Specification. This  
test performs a service state audit with the far-end terminal adapter to ensure  
that both sides agree on the service state.  
A PASS for this test simply means that an audit message was successfully  
composed and sent out to the far-end terminal adapter. The ISDN Specification  
allows up to two minutes for a reply. If no reply is received within that two minute  
window, this switch automatically tries once again. If that attempt fails, an error is  
logged (Error Type 3073), and the switch attempts a recovery by automatically  
retrying approximately every 15 minutes. If the port was initially in the INS  
(in-service) state, it is now placed into the MTC/FE (maintenance state, far-end  
problem) state. Until a Service State Audit attempt is successful, no outgoing  
calls are placed over this port, but incoming calls are be accepted. The service  
state of this port does not affect the service state of other ports in the PRI  
Endpoint. If an incoming call that uses this port is presented while in such a state,  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-882  
a Service State Audit attempt is immediately attempted (that is, the switch does  
not wait for the 15 minute cycle, but instead tries to recover immediately). To  
investigate the status of this PRI Endpoint Port, issue the status pri-endpoint  
<extension> command.  
Table 3-382. TEST #256 Service State Audit Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1113  
ABORT  
The signaling link has failed. As a result, the system cannot send any  
messages on behalf of this port.  
1. Check the results of Test #255 (Signaling Link State Check).  
A service state audit message is outstanding.  
1. Wait two minutes and try again.  
1117  
1700  
ABORT  
ABORT  
Rollabout video abort. The PRI terminal adapter associated with this PRI  
endpoint extension is detached from the circuit pack. This is a normal abort  
when the rollabout video feature is enabled. To complete the test on this  
port, do one of the following:  
1. Re-attach the disconnected PRI terminal adapter, or  
2. Disable the rollabout video feature on this circuit pack by entering the  
change ds1 PCSS command, and set the field "Alarm when PRI  
Endpoint Detached?" to "y."  
2100  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
Wait 4 minutes and then check the Error Log for any new occurrences of  
Errors Type 3073.  
If there are no occurrences of this error, both sides of the ISDN connection  
agree on the service state, and the negotiation succeeded. If there is a new  
occurrence of Error Type 3073, the negotiation failed (that is, the far-end  
terminal adapter twice failed to respond within the mandatory two minute  
window). This switch automatically retries approximately every 15 minutes.  
If the port was initially in the INS (in-service) state, it is now be placed into  
the MTC/FE (maintenance, far-end problem) state. Incoming calls are  
accepted, but no outgoing calls are originated from this port. If an incoming  
call is presented, another Service State Audit is immediately performed in  
an attempt to bring the PRI Endpoint Port to the proper state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-883  
Call State Audit Test (#257)  
If a call is active on the port, the switches on both sides of the connection should  
agree on the ISDN state of the call as defined in the ISDN Protocol Specification.  
This test audits internal call state data by querying the far-end terminal adapter  
about the ISDN state of the call. It can be helpful when trying to clear a hung call.  
If the internal call state data on the near-end switch is different than that of the  
far-end terminal adapter, the call is torn down.  
As with Test #256 (Service State Audit), a PASS simply means that an appropriate  
message was composed and sent to the far-end terminal adapter. The ISDN  
Specification allows up to two minutes for a reply. If a reply is not received within  
the two minute window, a protocol time-out violation is recorded in the error log  
against the associated signaling channel (ISDN-PRI Signaling Link Port, which is  
listed in the Error Log as ISDN-LNK; the Error Type is 1).  
Table 3-383. TEST #257 Call State Audit Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
An audit is already in progress.  
1019  
ABORT  
ABORT  
1. Wait two minutes and try again.  
1113  
1116  
The signaling link has failed. As a result, the system cannot send any  
messages on behalf of this port.  
1. Check the results of Test #255 (Signaling Link State Check).  
The port is in an out-of-service ISDN service state.  
ABORT  
ABORT  
1. A call cannot be present if the port is in an ISDN out-of-service state.  
As a result, a call state audit would be inappropriate, and no action is  
necessary. (Use the status pri-endpoint <extension> command to  
investigate the ISDN state of the port).  
1700  
Rollabout video abort. The PRI terminal adapter associated with this PRI  
endpoint extension is detached from the circuit pack. This is a normal  
abort when the rollabout video feature is enabled.  
To complete the test on this port, do one of the following:  
1. Re-attach the disconnected PRI terminal adapter, or  
2. Disable the rollabout video feature on this circuit pack by entering the  
change ds1 PCSS command, and set the field "Alarm when PRI  
Endpoint Detached?" to "y."  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PE-BCHL (PRI Endpoint Port)  
3-884  
Table 3-383. TEST #257 Call State Audit Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
PASS  
This switch sent a call state auditing message to the far-end terminal  
adapter to verify the state of the call active on this port. If a call state  
mismatch is found, the call is torn down within two minutes. If no call was  
active, no message was sent.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
PKT-BUS (Packet Bus)  
3
3-885  
PKT-BUS (Packet Bus)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test pkt port l r 2  
test pkt port l  
Full Name of MO  
Packet Bus  
PKT-BUS  
PKT-BUS  
PKT-BUS  
MAJOR  
MINOR  
Packet Bus  
WARNING  
test pkt port l  
Packet Bus  
The Packet Bus consists of a single bus, and one such bus appears in the  
system. There is one instance of the Packet Bus maintenance object.  
The Packet Bus is used to carry ISDN-BRI, ISDN-PRI, and ASAI signaling  
information. The SPE interface to the Packet Bus is the second Packet Interface  
instance (PKT-INT, instance1A2) on the TN798 Processor Circuit Pack, which  
works in concert with the Bus Bridge circuitry on the TN799 C-LAN circuit pack to  
provide Packet Bus access. Packet Bus maintenance is performed only when the  
Packet Intf2?field on the Maintenance-Related System Parameters form is  
set to y. Packet Bus testing is dependent on the following hardware components:  
■
■
■
TN771 Maintenance/Test circuit pack, M/T-PKT port  
TN798 Processor circuit pack, PKT-INT instance 1A2  
TN556 ISDN-BRI Line circuit pack  
Packet Bus tests may abort if some of this hardware is not present in the system.  
Also, these tests may yield inconsistent results if some of this hardware is  
defective.  
The interactions between the Packet Bus and the circuit packs that use the bus  
are complex. For this reason, the Packet Bus can be alarmed due to a circuit  
pack failure and, conversely, circuit packs can be alarmed due to a Packet Bus  
failure. This section on PKT-BUS is limited to a description of the Error and Alarm  
Log entries for the Packet Bus maintenance object and to a description of the  
Packet Bus test sequence.  
NOTE:  
Refer to Chapter 9, “Packet Bus Fault Isolation and Correction”, in  
DEFINITY® Enterprise Communications Server Release 8.2, Maintenance for  
R8si, 555-233-123, Issue 1, April 2000, Comcode 108678715,for a complete  
discussion of Packet Bus maintenance and also the interactions of the bus  
with the Packet circuit packs. The chapter discusses fault isolation and  
correction procedures, and it should be referenced for all procedures and  
required decisions. The "Packet Bus Fault Isolation Flowchart"section of the  
chapter is the normal starting point for experienced technicians; however,  
technicians who are unfamiliar with the Packet Bus and its use should refer  
to the introductory material.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
PKT-BUS (Packet Bus)  
3
3-886  
A failure of one or more circuit packs that use the Packet Bus can cause a Packet  
Bus alarm. In addition, a Packet Bus failure can cause loss of service to one or  
more such circuit packs, as well as to the ports and endpoints associated with  
the ISDN-BRI circuit pack (BRI-PORT, ABRI-PORT, BRI-SET, BRI-DAT, and  
ASAI-ADJ). These interactions are discussed in the "Circuit Packs That Use the  
Packet Bus" section of the chapter referenced in the note above.  
The following list summarizes some of the important points to consider when  
working with the Packet Bus.  
■
The Maintenance/Test circuit pack (TN771) is a critical tool for isolating  
Packet Bus faults. The circuit pack is optional, and is not present in all  
systems. If a TN771 is not present, one must be taken to the customer  
site to allow for proper fault isolation. (A determination as to whether a  
TN771 circuit pack is in the system is made by entering the list  
configuration command.) Use of the Maintenance/Test Packet Bus port  
facilities is described under "The Maintenance/Test Circuit Pack (TN771)"  
in the above referenced chapter. Also, in the same chapter, the section  
entitled "Special Precautions Concerning the TN771" describes other  
circumstances when a TN771 must be taken to the customer site.  
■
Certain catastrophic failures of a Packet Bus can cause all the Packet  
circuit packs on that bus to report errors, thus generating a high volume of  
maintenance activity for maintenance objects that are healthy. In order to  
reduce this unnecessary activity, some maintenance for Packet circuit  
packs, ports, and endpoints is curtailed or disabled when such a  
catastrophic Packet Bus failure is suspected. The following list  
summarizes the error-logging and testing impact of this strategy:  
c. In-line errors indicating possible Packet Bus failures are placed into  
the error log, but are not acted upon. Circuit pack maintenance  
objects thus affected include:  
■
■
■
■
■
■
■
■
■
BRI-BD  
LGATE-BD  
ASAI-BD  
TBRI-BD  
PGATE-BD  
CLAN-BD  
UDS1-BD  
MAPD-BD  
MEDPRO  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
PKT-BUS (Packet Bus)  
3
3-887  
d. In-line errors indicating possible Packet Bus failures are neither  
placed into the error log nor acted upon. Circuit pack port and  
endpoint maintenance objects thus affected include:  
■
■
■
■
■
■
■
■
BRI-PORT, ABRI-PORT, BRI-SET, TBRI-PT  
ASAI-ADJ, ASAI-PT, ASAI-EPT  
ATT-PORT, ATT-ADJ, ATTE-PT, ATTE-AJ  
LGATE-PT, LGATE-AJ  
PGATE-PT  
ETH-PT  
PPP-PT  
MEDPRO-RES  
e. Circuit pack and port in-line errors that are not relevant to the  
Packet Bus or that indicate a circuit pack failure are acted upon in  
the normal fashion.  
f. Normal background maintenance (periodic and scheduled) is not  
affected.  
g. Foreground maintenance (for example, commands executed on the  
Manager I terminal) is not affected.  
The actions in the previous list serve to reduce the system load, which  
could become excessive if too many maintenance objects are affected by  
a Packet Bus failure. However, such an excessive load should in no way  
impede the isolation and the correction of the faults.  
When the actions in the list are implemented, Error Type 3329 is logged  
against PKT-BUS, and a Warning alarm is raised (although other Packet  
Bus errors in many cases raise more severe alarms, thereby overriding the  
Warning alarm).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
PKT-BUS (Packet Bus)  
3
3-888  
Error Log Entries and Test to Clear Values  
Table 3-384. PKT-BUS Error Log Entries  
Error  
Type  
Alarm  
Level  
On/Off  
Board  
Test to Clear  
Value  
Aux Data  
Associated Test  
1
0
0
Any  
Any  
Any  
ON  
test pkt l  
1 (a)  
1-2  
Packet Circuit Pack  
Audit Test (#570)  
MAJOR  
test pkt p l r 2  
513 (b)  
1-24  
Maintenance/Test  
Circuit Pack Query Test  
(#572)  
MAJOR  
ON  
test pkt p l r 2  
1793 (c)  
2305 (d)  
Any  
none  
1-24  
Maintenance/Test  
Circuit Pack Query Test  
(#572)  
test pkt p l  
3329 (e)  
3585 (f)  
1-7  
none  
none  
WARNING  
MINOR  
ON  
ON  
test pkt p l  
test pkt p l  
Any  
1. Run the Long Test Sequence. Refer to the appropriate test description and follow the  
recommended procedures.  
NOTE:  
For PKT-BUS, an ON-BOARD alarm indicates a problem with the Packet  
Bus itself.  
Notes:  
a. Within the last minute, packet circuit packs have reported errors that  
indicate a possible Packet Bus failure. The Aux Data value is 1 or 2,  
indicating that only one or more than one Packet circuit pack  
(respectively) have reported a possible Packet Bus failure.  
b. The Maintenance/Test Packet Bus port has determined that there are  
Packet Bus shorted-lead or stuck-lead faults. The Aux Data value  
indicates the number of faulty leads.  
c. Packet circuit packs have detected possible Packet Bus failures via in-line  
error or background test failure. Examine the Error and Alarm logs for  
more specific PKT-BUS errors.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
PKT-BUS (Packet Bus)  
3
3-889  
d. The Maintenance/Test Packet Bus port has detected open leads on the  
Packet Bus. The Aux Data value indicates the number of open leads.  
e. Packet circuit pack, port, and endpoint maintenance has been disabled  
due to a Packet Bus failure. The Aux Data value indicates which sources  
have reported errors that have caused maintenance to be disabled. These  
sources include the following:  
■
In-line errors from Packet circuit packs.  
■
Packet Bus fault report from the Maintenance/Test Packet Bus port.  
The Aux Data values that indicate these sources are identified in the  
following table:  
Packet Circuit  
Pack  
Maint/Test  
Circuit Pack  
Aux Data  
1
2
3
4
5
6
7
X
X
X
X
X
X
X
X
NOTE:  
It is important to remember that problems reported by Packet circuit  
packs may be caused by any circuit pack. However, only Packet  
circuit packs can detect such problems (inasmuch as TDM-only  
circuit packs are not affected by these problems).  
f. Packet circuit pack, port, and endpoint maintenance has been disabled  
due to more than one circuit pack reporting in-line errors. If this occurs  
more than three times in 15 minutes (that is, if maintenance is disabled  
due to errors and then re-enabled because no more errors are reported), a  
Minor alarm is raised against the Packet Bus. Note that this error may still  
be present in the error log even if the "Circuit Pack Audit Test" reports that  
only one circuit pack has indicated a problem. This occurs if more than  
one circuit pack reported errors with in any one minute interval since the  
Packet Bus fault occurred.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
PKT-BUS (Packet Bus)  
3
3-890  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following tables when you  
are inspecting errors in the system. By clearing error codes associated with the  
Packet Circuit Pack Audit Test, for example, you may also clear errors generated  
from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Packet Circuit Pack Audit Test (#573)  
D/ND  
ND  
X
X
X
X
Maintenance/Test Circuit Pack Query Test (#572)  
ND  
1. D = Destructive; ND = Nondestructive  
Maintenance/Test Circuit Pack Query Test (#572)  
This test queries the Maintenance/Test Packet Bus port about the state of health  
of the Packet Bus. If the Maintenance/Test circuit pack indicates that the Packet  
Bus has faults, the test fails. The corresponding failure code describes the  
severity, type, and number of faults. The test passes if the Packet Bus is  
fault-free.  
NOTE:  
A Maintenance/Test circuit pack is usually not present in the system unless  
the customer has purchased this circuit pack to use for ISDN-PRI test calls,  
or to enhance the system’s ability to quickly recognize a Packet Bus failure.  
Table 3-385. TEST #572 Maintenance/Test Circuit Pack Query Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1006  
ABORT  
The Packet Bus port of the Maintenance/Test circuit pack is out of service.  
1. Determine if the port is busied out. If so, release the port by entering the  
release port PCSS04 command. Re-enter the test command.  
1142  
ABORT  
No Maintenance/Test circuit pack Packet Bus port is in service in this system.  
1. The Maintenance/Test Packet Bus Port may not be present. If the port is  
present, and if it is busied out or has failed, release or replace the circuit  
pack. If there is no Maintenance/Test circuit pack, ignore the results of  
this test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
PKT-BUS (Packet Bus)  
3
3-891  
Table 3-385. TEST #572 Maintenance/Test Circuit Pack Query Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
The test timed-out while waiting for an uplink CCMS response from the  
Maintenance/Test Packet Bus port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort, check for problems with the  
Maintenance/Test Packet Bus port .  
2059  
2077  
ABORT  
ABORT  
The Maintenance/Test Packet Bus port has reported a hardware failure.  
1. Re-enter the test command.  
The Maintenance/Test Circuit Pack Query located more than one  
Maintenance/Test Packet Bus port in the system.  
NOTE:  
The software should not allow this to occur. This is an Internal system  
error. Attempt the following work-around steps.  
1. Remove all Maintenance/Test circuit packs from the system.  
2. Insert one Maintenance/Test circuit pack (there should not be more than  
one in a system).  
3. Re-enter the test command.  
2100  
2500  
ABORT  
ABORT  
Maintenance could not allocate all of the necessary system resources to  
perform this test.  
An internal operation failed; the test could not be completed.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
XYZZ  
1xxx  
FAIL  
The Maintenance/Test Packet Bus port has detected faults on the Packet Bus.  
The error code is encoded as follows:  
The Maintenance/Test Packet Bus port has reconfigured the Packet Bus  
around the faulty leads. This action occurs only in high or critical reliability  
systems, and such a failure code should not appear in an R8csi system.  
2xxx  
The Maintenance/Test Packet Bus port is unable to correct all of the Packet  
Bus faults it has detected.This action occurs only in high or critical reliability  
systems, and such a failure code should not appear in an R8csi system.  
x0xx  
x1xx  
None of the Packet Bus faults are open faults.  
At least some of the Packet Bus faults are open faults. Look for Error Type  
2305 in the Error Log. The Aux Data value indicates the number of open  
leads.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
PKT-BUS (Packet Bus)  
3
3-892  
Table 3-385. TEST #572 Maintenance/Test Circuit Pack Query Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
xxZZ  
The last 2 digits of the error code indicate the total number of faulty Packet  
Bus leads detected by the Maintenance/Test Packet Bus port.  
1. Refer to the "Packet Bus Fault Isolation Flowchart" section in Chapter 9 to  
determine the cause of the failures.  
PASS  
No faults have been detected on the Packet Bus by the Maintenance/Test  
circuit pack. This indicates that the Packet Bus is operating correctly.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
PKT-BUS (Packet Bus)  
3
3-893  
Packet Circuit Pack Audit Test (#573)  
This test determines whether Packet circuit packs have reported Packet  
Bus-related in-line errors within the last minute. If so, the failure code indicates  
whether one or more circuit packs have reported failures within the last minute.  
Due to the one-minute time constraint included as part of this test, the test is  
designed to delay 15 seconds before returning a result in cases where the test  
has failed within the last five minutes. This procedure helps ensure that a  
repeated sequence of the test does not always yield the same result. If no failure  
has occurred in the last five minutes, a PASS is returned immediately.  
Table 3-386. Test #573 Packet Circuit Pack Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2500  
ABORT An internal operation failed; the test could not be completed.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1
2
FAIL  
One Packet circuit pack has reported Packet Bus-related in-line errors within  
the last minute.  
FAIL  
More than one Packet circuit pack has reported Packet Bus-related in-line  
errors within that last minute.  
1. Refer to the "Packet Bus Fault Isolation Flowchart" section in Chapter 9 to  
determine the cause of the error reports.  
PASS  
No Packet circuit packs have reported Packet Bus-related in-line errors within  
the last minute. This indicates that the Packet Bus is healthy, or that a Packet  
Bus fault is transient or is being caused by a faulty Packet circuit pack. If this  
test passes while there are other signs of a Packet Bus failure (as indicated, for  
example, in the Error/Alarm Logs or by other test failures), refer to the "Packet  
Bus Fault Isolation Flowchart" section in Chapter 9 to isolate the problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-894  
PKT-INT (Packet Interface)  
MO Name (in  
Alarm Log)  
1
Alarm Level  
MAJOR  
Initial Command to Run  
reset packet-interface 1AS  
test packet-interface 1AS  
test packet-interface 1AS  
Full Name of MO  
Packet Interface  
PKT-INT  
PKT-INT  
MINOR  
Packet Interface  
Packet Interface  
PKT-INT  
WARNING  
1. S is the instance of the Packet Interface on the TN798 Processor circuit pack (1 or 2).  
The Packet Interface (PKT-INT) interfaces between the TN798 Processor circuit  
pack and packet endpoints (such as ISDN-BRI stations or ISDN-PRI trunks). Two  
instances of PKT-INT are provided on the TN798 Processor circuit pack:  
■
■
PKT-INT 1 (1A1) communicates through the TDM bus only. It provides  
signaling for circuit packs that can receive signaling packets over the  
TDM bus, e.g., the TN767E DS1 Interface circuit pack (for ISDN-PRI  
applications) and the TN556C circuit pack (for ISDN-BRI applications).  
PKT-INT 2 (1A2) communicates through the Packet bus only. It provides  
signaling only for circuit packs that can receive their signaling packets  
over the Packet Bus, e.g., the TN464F UDS1 circuit pack and the TN556B  
circuit pack  
The TN798 Processor circuit pack is not equipped with a direct interface to the  
Packet Bus. In order to use the Packet Bus, PKT-INT 2 (1A2) connects via the  
Processor circuit pack’s TDM Bus interface to a special Bus Bridge module on  
the TN799 C-LAN circuit pack. That module provides a Packet Bus interface on  
one side and a TDM Bus interface on the other, and PKT-INT 2 is therefore able to  
access the Packet Bus through it.  
PKT-INT 2 is enabled only when the following conditions are met:  
■
The system contains at least one TN799 C-LAN circuit pack, and  
■
The Packet Intf2? field on the Maintenance-Related System Parameters  
form is set to “y”.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-895  
Figure 3-40. PKT-INT Connections  
A failure of both Packet Interface instances prevents call origination and  
tear-down for telephones and trunks provided by the following circuit packs:  
■
■
■
■
■
■
■
TN464C, TN2464 Universal DS1 circuit packs - ISDN PRI service  
TN767E DS1 Interface circuit pack - ISDN PRI service w/o Packet Bus  
TN556B/C, TN2198 ISDN-BRI Line circuit packs — ISDN BRI service  
TN2185 ISDN Trunk-Side BRI - ISDN-BRI Trunk service  
TN566, TN2208 Multi-Function circuit packs- ASAI-over-Ethernet service  
TN800, TN801, TN803 MAPD circuit packs - LAN Gateway Emulation  
TN802 MAPD circuit packs - IP Trunk Emulation, Media Processor  
applications  
■
TN799 CLAN - Ethernet and Asynchronous PPP service  
A failure of only one PKT-INT instance may allow some links to transfer to the  
other PKT-INT instance.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-896  
The links that pass through the Packet Interfaces are application links or system  
links:  
a. Application links, such as the TCP/IP links that C-LAN supports include:  
■
■
■
■
■
■
Distributed Communication System (DCS)  
Audio Information Exchange (AUDIX)  
Messaging Service Adjunct (MSA)  
Call Management System (CMS)  
Outgoing Call Management (OCM)  
Adjunct Switch Application Interface (ASAI)  
b. System links  
■
■
■
■
ISDN PRI D channel signaling links  
ISDN BRI D channel broadcast and point-to-point signaling links  
Adjunct Switch Application Interface (ASAI) links  
Remote Socket Links (RSL) and Remote Socket Control Links  
(RSCL)  
Packet Interface Service Operations  
The following sections provide more background information about Packet  
Interface service operations:  
■
■
■
■
■
‘‘Administration’’  
‘‘Packet Interface Replacement’’  
‘‘Demand Reset of a Packet Interface’’  
‘‘Service States’’  
‘‘Maintenance Object Interactions’’  
Administration  
There are no add or remove commands for the Packet Interfaces. Instead, the  
System Parameters Maintenance Form provides Packet Interface fields (Packet  
Intf1and Packet Intf2) to:  
■
Indicate the presence of Packet Interface 1.  
Permit Packet Interface 2 to be enabled.  
■
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-897  
Packet Interface Replacement  
To replace a Packet Interface, follow the procedure to replace the TN798  
Processor circuit pack:  
■
■
■
Power down the system.  
Replace the TN798 Processor circuit pack.  
Power the system back up.  
Demand Reset of a Packet Interface  
System software denies a demand reset of a Packet Interface (reset  
packet-interface) if the Packet Interface is in service. A reset would disrupt  
service, existing calls, and links to adjuncts such as AUDIX. The software that  
controls Packet Interface maintenance puts a Packet Interface in the  
out-of-service state if that Packet Interface has been reset four times within the  
last 15 minutes, as part of the automatic recovery action that is initiated when a  
hardware fatal fault condition is detected.  
Service States  
Packet Interface maintenance software monitors the in-service/out-of-service  
state of each Packet Interface instance. If maintenance software detects that a  
Packet Interface instance has a “fatal fault,” it automatically attempts to reset that  
instance as quickly as possible. An extensive set of diagnostic tests are run  
when a Packet Interface is reset.  
If the Packet Interface diagnostic tests do not pass, the failing Packet Interface  
instance is placed in an out-of-service state. All links handled by that instance go  
out of service, except for those than can be transferred or “migrated” to the other  
Packet Interface instance.  
A Packet Interface also is put in the “out-of-service” state if it has reported a fatal  
fault at system initialization time or if the Packet Interface has been reset by  
background maintenance four times within the last 15 minutes, whether or not the  
Reset test passes. The state of both Packet Interfaces can be determined by  
using the status packet-interface command.  
Maintenance Object Interactions  
Packet Bus Maintenance  
■
Packet Interface 2 physically interacts with the PKT-BUS (Packet Bus)  
through the TDM Bus and the C-LAN circuit pack’s Bus Bridge circuitry.  
For certain types of Packet Interface errors, it may be difficult to isolate the  
fault to one of these four interconnected components. In these cases,  
Packet Interface maintenance will forward the error report to the Packet  
Bus maintenance, thus causing Packet Bus maintenance to record a  
Packet Bus fault in the hardware error log and to run appropriate Packet  
Bus tests.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-898  
■
Packet Circuit Pack Maintenance  
The operation of Packet Interface 2 affects the operation and maintenance  
of other circuit packs connected to the Packet bus. Affected applications  
include:  
— BRI applications  
— Universal DS1 applications (UDS1) using ISDN/PRI service  
— C-LAN applications  
— ASAI applications  
Some errors of Packet circuit packs may require examination of the Packet  
Interface operating status. To obtain this information, examine the Error  
and Alarm Logs for PKT-INT entries. Also issue the status  
packet-interface command to determine the service state of the Packet  
Interfaces (for example, in-service/out-of-service) and information about  
the total number of Packet Interface links assigned to a Packet Interface  
instance. In general, if all links for Packet Interface 2 are shown in the  
Failed Links category, there may be a fault on the Packet Interface or on  
the Packet Bus that caused all links to go down. If only a small percentage  
of the links are shown as Failed Links, then the Packet Interface is  
probably not the source of the problem. For example, disconnecting the  
cord to a BRI set causes three link failures. Refer to Chapter 2,  
‘‘Maintenance Commands’’ for more information on the status  
packet-interface command.  
For the case where not all links are in the Failed Links category, examine  
the alarm log and error log for failures of the following circuit pack types  
and follow the repair procedures for those circuit packs before  
considering replacing the TN798 Processor circuit pack.  
■
ISDN-BRI Line circuit packs, ports, and stations (BRI-BD,  
BRI-PORT, BRI-SET, ATT-PORT, ATT-ADJ)  
■
■
■
■
ISDN-BRI Trunk circuit pack and ports (TBRI-BD, TBRI-PT)  
Universal DS1 circuit packs and ports (UDS1-BD, TIE-DS1)  
DS1 Interface circuit packs and ports (DS1-BD, TIE-DS1)  
C-LAN circuit packs and ports (CLAN-BD, RSCL-PT, PPP-PT,  
ETH-PT)  
■
■
ASAI circuit packs and ports (ASAI-BD, ASAI-PT, ASAI-ADJ,  
ASAI-EPT, LGATE-BD, LGATE-PT, LGATE-AJ, ATTE-PT, ATTE-AJ,  
MAPD-BD)  
Media Processor circuit pack (MEDPRO, MEDPRO-RES)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-899  
Error Log Entries and Test to Clear Values  
Table 3-387. Packet Interface Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
1
Associated Test  
Any  
Alarm Level  
Any  
Test to Clear Value  
2
0
0
ON  
ON  
test packet-interface 1AS r 2  
3
1 (a)  
Any  
0
None  
MAJOR  
reset io-processor  
10 (b)  
23 (c)  
None  
0
None  
MAJOR  
OFF  
50 (d)  
100 (e)  
217 (g)  
257 (f)  
267 (g)  
513 (h)  
0
None  
0
None  
0
None  
WARNING  
MAJOR  
OFF  
ON  
3
Any  
0
None  
reset io-processor  
None  
WARNING  
MAJOR  
OFF  
ON  
3
Any  
Any  
None  
reset io-processor  
4
769 (i)  
Mtce Looparound Test  
(#886)  
MAJOR  
ON  
test packet-interface 1AS r 3  
4
3
1025 (j)  
Any  
Private Looparound  
Test (#885)  
MAJOR  
ON  
reset packet-interface 1AS  
3
1026 (j)  
Any  
Any  
Any  
None  
None  
MAJOR  
MAJOR  
MINOR  
ON  
ON  
ON  
reset packet-interface 1AS  
4
3
1281 (k)  
reset packet-interface 1AS  
1537 (l)  
Memory Checksum  
Test (#884)  
test packet-interface 1AS r 2  
test packet-interface 1AS r 2  
1793 (m)  
Any  
Memory Checksum  
Test (#884)  
MINOR  
ON  
ON  
4
2049 {n}  
Any  
Any  
Any  
None  
WARNING  
test packet-interface 1AS r 25  
test packet-interface 1AS r 2  
test packet-interface 1AS s r 2  
4
2305 (o)  
None  
3074 (p)  
3073  
Mtce Looparound Test  
(#886)  
WARNING  
OFF  
4
3072  
3
3329 (q)  
Any  
Any  
Any  
None  
None  
None  
WARNING  
WARNING  
MAJOR  
OFF  
OFF  
OFF  
reset packet-interface 1AS  
4
3
3585 (r)  
reset packet-interface 1AS  
4
3
3841 (s)  
reset packet-interface 1AS  
1
2
S is the instance of the Packet Interface (1 or 2).  
Indicates that an alarm was raised but an associated error was not entered into the hardware error log  
due to a momentary overload condition caused by a burst of hardware or software error reports. Run the  
long test sequence. Refer to the appropriate test descriptions for any failures and follow the  
recommended procedures.  
3
4
The I/O Processor or Packet Interface instance can only be reset if it has been taken out of service by  
background maintenance software.  
The error type or test applies only to Packet Interface 2, i.e., the Packet Interface instance that uses the  
Packet Bus.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-900  
Notes:  
a. Error 1 occurs when background maintenance software has reset the  
Packet Interface as a fault recovery action. It is used to keep track of the  
number of times that the Packet Interface is reset, independent of whether  
or not the Reset test passed. Once three of these errors have occurred in  
the last 15 minutes, the next such error will cause maintenance to place  
the Packet Interface into an out-of-service state, raise a MAJOR on-board  
alarm against the Packet Interface, and automatically reset the  
io-processor on the TN798 Processor circuit pack. If the io-processor reset  
does not restore to service the alarmed Packet Interface, then the  
io-processor reset attempt fails, and the software will continue to attempt  
to reset the io-processor. When three of these attempts have failed within a  
15 minute period, maintenance software puts the io-processor into a  
held-reset state and continues to attempt io-processor resets every three  
(3) minutes as long as the io-processor resets continue to fail.  
NOTE:  
Whenever the io-processor is reset, both Packet Interface instances  
and all 4 data channels (DATA-CHL) are reset as well, and service is  
interrupted for any calls using these MOs. Refer to the IO-PROCR  
section for more information concerning io-processor resets.  
1. Check to see if Error Types 257, 513, 769, 1025, 1281, or 3841 are  
present in the hardware error log. If one or more of those error  
codes are present, refer to the information associated with those  
errors for the appropriate repair procedures.  
2. If no other Packet Interface errors appear in the error log, and if the  
Packet Interface is not in a held reset state as indicated by the  
absence of a MAJOR alarm with a Service State of OUT, no action  
should be taken.  
3. If a Packet Interface MAJOR alarm is present and no other Packet  
Interface error codes are in the hardware error log, execute a  
demand reset of the IO Processor by entering reset io-processor.  
This command resets both Packet Interface instances as well as  
the IO Processor. Refer to the repair procedures for Test #704.  
b. Error 10 indicates that the Packet Interface maintenance software caused  
an escalating system WARM restart as part of a recovery action for certain  
Packet Interface failures. A SYSTEM Error Type 10 should also be present,  
indicating that a software initiated WARM restart occurred.  
1. Check to see if Error types 513, 1025, or 3074 are present in the  
hardware error log. If they are present, refer to the repair  
procedures for those errors for further action.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-901  
c. Error 23 along with an associated MAJOR alarm indicates that Packet  
Interface translation data was loaded at boot time but the Packet Interface  
was not detected to be physically present  
1. Reboot the system. If the error persists, replace the TN798  
Processor circuit pack.  
d. Error 50 indicates that the Processor is sending more downlink messages  
than the Packet Interface can keep up with. This is an in-line error not  
produced by any test. When this error is reported, application software is  
slowed down to allow the Packet Interface to process existing downlink  
messages. If there is a hardware problem, the Packet Interface test will  
normally cause other errors to be logged. In the rare case where there are  
no other PKT-INT errors logged but error 50 occurs more than 10 times in  
the last hour, follow normal escalation procedures.  
e. Error 100 indicates that the Processor requested a reset of Packet  
Interfaces as part of a Packet Interface recovery action.  
1. If no other PKT-INT errors except Error Type 1 are present, this  
means that the Packet Interface was in a fatal fault state at the time  
of system initialization and it was reset successfully. No other  
actions are required.  
2. If PKT-INT error codes other than Error Type 1 are present, refer to  
the repair procedures for those errors to correct the failure.  
f. Error 257 indicates that maintenance has detected a Packet Interface fatal  
failure. This error is a very serious, and when it occurs, maintenance  
software immediately escalates testing to the destructive reset test (#889).  
1. If the Packet Interface circuit has a MAJOR alarm, reset the Packet  
Interface (reset io-processor).  
2. If the Packet Interface is not alarmed, no action is required.  
g. Errors 267 and 217 indicate that the number of Packet Interfaces detected  
as being physically present exceeds number of Packet Interfaces  
supported by the software configuration.  
h. Error 513 is a Message Handshake failure, indicating that a failure with the  
message protocol between the System software and the Packet Interface.  
1. If the Packet Interface circuit has a MAJOR alarm, reset the Packet  
Interface (reset io-processor).  
2. If the Packet Interface is not alarmed, no action is required.  
i. Error 769 indicates that there was a failure in the Maintenance Looparound  
test (Test #886). A maintenance looparound link cannot be established or  
the Packet Interface cannot send and receive data correctly as part of the  
looparound test. If the number of errors exceeds a defined threshold, a  
MAJOR alarm is raised. For more information, refer to the repair  
procedures for Test #886.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-902  
j. Error 1025 indicates a failure of the private Level 3 Looparound Test (Test  
#885).  
1. If the Packet Interface has a MAJOR alarm:  
a. Reset the Packet Interface (reset packet-interface AS).  
b. Refer to the repair procedures for the Packet Interface Reset  
Test (#889).  
2. If the Packet Interface is not alarmed, no action is required.  
k. Error 1281 indicates that the Packet Interface has Translation RAM  
failures. PKT-INT Translation RAM is used to convert the addresses of a  
packet to the destination endpoint address.  
1. If the Packet Interface has a MAJOR alarm:  
a. Reset the Packet Interface (reset packet-interface AS).  
b. Refer to the repair procedures for the Packet Interface Reset  
Test (#889).  
2. If the Packet Interface is not alarmed, no action is required.  
l. Error 1537 indicates a Boot PROM memory failure. The Packet Interface  
may still be operational if no other errors are reported. However the TN798  
Processor circuit pack may report a fatal fault during board  
initialization.For more information, refer to the repair procedures for Test  
#884.  
m. Error 1793 indicates a FLASH Memory test failure. The Packet Interface  
may still be operational if no other errors are reported. However the TN798  
Processor circuit pack may report a fatal fault during board initialization.  
This may occur during a system recovery level more severe than a WARM  
restart. For more information, refer to the repair procedures of Test #884.  
n. Error 2049 indicates a LAPD Receive Buffer Overflow error. The Packet  
Interface Packet Bus receive buffer overflowed. For more information,  
refer to the repair procedures of Test #887.  
o. Error 2305 indicates a Packet Bus Interface Detected Parity failure. The  
Packet Interface received packets with parity error from the Packet Bus.  
1. Check for errors logged against the Packet bus and  
Maintenance/Test circuit pack. Refer to the appropriate repair  
procedures to clear those errors first.  
2. Check all other circuit packs connected to the Packet bus in the  
same cabinet. Packet Bus failures are likely to be caused by a  
faulty circuit pack connected to the backplane or bent pins on the  
backplane.  
3. If Steps 1 and 2 above do not clear the problem, execute the test  
packet-interface command and follow repair procedures  
described for Test #887.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-903  
p. Errors 3074, 3073, and 3072 indicate Packet Interface Transmit Buffer  
Overflow, which means that the number of transmit buffers required by  
software exceeded the number available. A 3074 error is generated when  
the Packet Interface sends an in-line hardware error to maintenance  
software indicating transmit buffer overflow. As part of the background  
recovery action for this error, maintenance software automatically runs the  
Maintenance Looparound Test (#886). If that test fails, maintenance  
software generates Error Types 3073 and 3072, and it requests a system  
WARM restart. If, after the WARM restart, transmit buffer overflow errors  
continue to be reported, maintenance software generates Error Type 100  
and resets the Packet Interface. These errors may be the result of system  
overload due to a problem with communication between the Packet  
Interface and the Packet Bus circuit packs.  
1. Clear errors against any of these components first:  
■
■
■
■
■
■
C-LAN circuit pack  
BRI Line circuit pack and BRI endpoints  
BRI Trunk circuit pack  
the Universal DS1 circuit pack supporting PRI service  
Media Processor circuit pack  
MAPD circuit pack  
2. Enter the test packet-interface short command against the Packet  
Interface associated with the error. If the Maintenance Looparound  
Test (#886) passes, the alarm clears.  
3. If the test fails, repeat the test 5 times.  
4. If it continues to fail, follow normal escalation procedures.  
q. Error 3329 indicates that the TDM clock has failed (TONE-BD and  
TDM-CLK alarms). Refer to TDM-CLK and/or TONE-BD for further action.  
The Packet Interface is taken out of service when this failure occurs.  
1. Execute the reset packet-interface command to bring the Packet  
Interface back into service.  
r. Error 3585 indicates a Packet bus failure. Refer to the Packet Bus  
maintenance documentation for further action.  
s. Error 3841 indicates that the Packet Interface has reported a fatal fault  
failure condition that may be caused by a Packet Bus failure.  
1. If Error Type 3585 has also been reported, refer to PKT (Packet  
Bus) maintenance. After the Packet Bus failure has been corrected,  
bring the Packet Interface back into service (reset  
packet-interface).  
2. If Error Type 3585 has not been reported, enter the reset  
packet-interface command and follow the repair steps associated  
with test #889.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-904  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the Packet Interface Private Looparound test for  
example, you may also clear errors generated from other tests in the testing  
sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
ResetBoard  
Sequence  
1
Order of Investigation  
D/ND  
D
Packet Interface Reset Test (#889)  
X
Packet Interface Private Looparound Tests  
(#885)  
X
X
X
X
ND  
Packet Interface Maintenance Looparound  
Test (#886)  
X
X
ND  
ND  
ND  
Packet Interface Memory Checksum Test  
(#884)  
Packet Interface Error Counter Read and  
Clear Test (#887)  
1. D = Destructive; ND = Nondestructive  
Memory Checksum Test (#884)  
This test involves sending a message to the Packet Interface to run private  
non-destructive memory checksum tests on the firmware text residing in Boot  
PROM and FLASH memory. If the test fails during background testing, the Packet  
Interface will remain operational until a reset packet-interface is executed. Then  
the initialization firmware will fail and will put the packet interface in an  
out-of-service state. This test causes the entire I/O-Processor memory to be  
tested. The I/O Processor does not support its own Flash Memory Checksum  
test.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-905  
Table 3-388. TEST #884 Memory Checksum Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1006  
1137  
ABORT  
Packet Interface is in the out-of-service state so normal maintenance tests  
will not run.  
1. Use the display system-parameters maintenance command to  
identify which C-LAN circuit pack is administered with the Bus  
Bridge. Verify that the C-LAN circuit pack is present and is not  
alarmed.  
2. Request a Packet Interface reset using the reset  
packet-interface AS command. Refer to the Packet Interface  
Reset Test (#889) repair procedures for further action.  
1334  
ABORT  
The Packet Interface command queue is full. This should be a temporary  
condition caused by a high rate of commands being sent to a Packet  
Interface. Continued operation with a full command queue will cause a  
system WARM restart that may escalate to more severe restart levels.  
1. Retry the command at 10-second intervals, a maximum of 5  
times.  
2000  
2500  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals, a maximum of 3 times.  
Internal system error.  
1. Retry the command.  
NO  
The Packet Interface is not detected as being physically present.  
BOARD  
1. Reboot the system, then retry the command. If the NO BOARD  
indication persists, replace the TN798 Processor circuit pack.  
1537  
FAIL  
The Boot PROM memory checksum test failed. The Packet Interface may still  
be operational.  
1. Retry the command.  
2. If the same error code occurs, replace the TN798 Processor  
circuit pack at a time that would cause the least disruption of  
service. The Packet Interface is still functional but should be  
replaced since it may not operate after a system reboot and it will  
enter a fatal fault state if it is reset for other reasons.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-906  
Table 3-388. TEST #884 Memory Checksum Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1793  
FAIL  
The Flash memory checksum test failed. The Packet Interface may still be  
operational but it will fail if a reset is executed.  
1. Retry the command.  
2. If the same error code occurs, replace the TN798 Processor circuit pack  
at a time that would cause the least disruption of service. The Packet  
Interface is still functional but should be replaced since it may not  
operate after a system reboot and it will enter a fatal fault state if it is reset  
for other reasons.  
PASS  
The Packet Interface’s firmware is in a proper state. If problems are still  
reported on the Packet Interface, check for errors on the Private Looparound  
test (#885) and Maintenance Looparound Test (#886).  
Private Looparound Tests (#885)  
This test requests the Packet Interface to execute its two private looparound  
tests:  
■
Level 2 looparound  
■
Broadcast path looparound  
These tests verify the health of the Packet Interface’s translation RAM, inward and  
outward bound data paths, parity indications and CRC calculations, the Level 2  
processing firmware, and the C-LAN’s Bus Bridge operation, including C-LAN  
TDM Bus and Packet Bus access.  
■
Level 2 (LAPD) Link Looparound  
LAPD is a link level protocol that is used for all system links. This test  
verifies the health of the processing of these links.  
■
Broadcast Link Looparound  
Each ISDN BRI port has two associated broadcast signaling links, one for  
call control and one for maintenance and management. Since these links  
have separate routing circuitry from the Level 2 Looparound, this test  
forces a CRC error to verify the CRC hardware associated with the  
broadcast data path.  
These tests are also run as part of the reset tests, and the PKT-INT firmware  
automatically executes them periodically in the background. If the Level 2  
looparound test fails as a background test, a fatal error message will be sent to  
the Packet Interface maintenance software and the Packet Interface will be put in  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-907  
the out-of-service state. Therefore, it is expected that the repair procedures  
associated with Abort Code 1137 (out-of-service) would normally be followed  
when failures with the Level 2 test occurs.  
Test #885 executes differently depending on which instance of Packet Interface  
is tested:  
1. Packet Interface 1 (TDM Bus-based) - No hardware is tested. Only  
operational firmware is tested.  
2. Packet Interface 2 (Packet Bus-based) - All three tests are executed.  
Table 3-389. TEST #885 Private Looparound Tests  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1006  
1137  
ABORT  
Packet Interface is in the out-of-service state so normal maintenance tests  
will not run on it.  
1. Use the display system-parameters maintenance command to identify  
which C-LAN circuit pack is administered with the Bus Bridge. Verify  
that the C-LAN circuit pack is present and is not alarmed.  
2. Request a Packet Interface reset using the reset  
packet-interface AS command. Refer to the Packet Interface  
Reset Test (#889) repair procedures for further action.  
1334  
ABORT  
The Packet Interface command queue is full. This should be a temporary  
condition caused by a high rate of commands being sent to a Packet  
Interface. Continued operation with a full command queue will cause a  
system WARM restart that may escalate to more severe restart levels.  
1. Retry the command at 10-second intervals, a maximum of 5  
times.  
2000  
2500  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals, a maximum of 3 times.  
Internal system error.  
1. Retry the command.  
NO  
The Packet Interface is not detected as being physically present.  
BOARD  
1. Reboot the system, then retry the command. If the NO BOARD  
indication persists, replace the TN798 Processor circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-908  
Table 3-389. TEST #885 Private Looparound Tests — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
FAIL  
The Private Link Broadcast looparound test failed. The Packet Interface will  
enter a fatal fault state when this occurs and the Packet Interface  
Maintenance software should put the Packet Interface in a out-of-service  
state. Therefore by the time further action is taken, it is expected that the test  
will abort with ABORT code 1137 and a demand reset should be used to  
test the Packet Interface.  
1. Reset the Packet Interface using the reset packet-interface AS  
command. Refer to the repair procedures for the Packet Interface Reset  
Test (#889) for further action.  
2. If the test continues to fail, replace the TN798 Processor circuit pack.  
2
FAIL  
The Private Level 2 looparound test failed. The Packet Interface will enter a  
fatal fault state when this occurs and the Packet Interface Maintenance  
software should put the Packet Interface in a out-of-service state. Therefore  
by the time further action is taken, it is expected that the test will abort with  
ABORT code 1137 and a demand reset should be used to test the circuit  
pack.  
1. Reset the Packet Interface using the reset packet-interface AS  
command. Refer to the repair procedures for the Packet Interface Reset  
Test (#889) for further action.  
2. If the test continues to fail, replace the TN798 Processor circuit pack.  
PASS  
All the private looparound tests passed. The Packet Interface is functioning  
properly. If the system is still unable to place calls, then:  
1. Display the error log (display errors) and check for errors on the  
Packet Bus and Maintenance/Test circuit pack. Clear those errors first.  
2. Check all other circuit packs connected to the Packet Bus. Packet Bus  
failures are likely to be caused by a faulty circuit pack connected to the  
backplane or bent pins on the back plane. Refer to the PKT-BUS  
maintenance documentation for repair procedures.  
Maintenance Looparound Test (#886)  
This test checks whether the Packet Interface can send and receive data  
correctly. It establishes a LAPD link from a Packet Interface back to the same  
Packet Interface and transmits and receives test data over that testing link. While  
timing signals from the Packet Bus are used for the data transfer, the data itself is  
looped around on the TN799 C-LAN circuit pack’s Bus Bridge at the interface to  
the Packet Bus and does not get sent over the Packet Bus. This test is run only  
on the second instance of Packet Interface on the TN798 Processor, since the  
first instance cannot use the Packet Bus.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-909  
Table 3-390. TEST #886 Maintenance Looparound Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1006  
1137  
ABORT  
Packet Interface is in the out-of-service state so normal maintenance tests  
will not run on it.  
1. Use the display system-parameters maintenance command to identify  
which C-LAN circuit pack is administered with the Bus Bridge. Verify that  
the C-LAN circuit pack is present and is not alarmed.  
2. Reset the Packet Interface using the reset packet-interface AS  
command. Refer to the Packet Interface Reset Test (#889)  
maintenance documentation for further action.  
1139  
ABORT  
The Packet Bus is alarmed  
1. Try to retire the alarm associated with the Packet Bus. Refer to the Alarm  
Log through the display alarms command. Refer to the maintenance  
documentation for Packet Bus Maintenance for further action.  
2. Retry the command when the alarm associated with the Packet Bus is  
retired.  
1373  
2060  
ABORT  
ABORT  
Could not establish the link loop around link to run this test.  
1. Retry the command at 1-minute intervals, a maximum of 3 times.  
Packet bus link went down during maintenance looparound test.  
1. Retry the command at 1-minute intervals, a maximum of 5 times.  
2. If there are errors associated with the Packet Bus, refer to the  
maintenance information associated with the Packet Bus.  
2100  
2500  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals, a maximum of 5 times.  
Internal system error.  
1. Retry the command at 1-minute intervals, a maximum of 5 times.  
The Packet Interface is not detected as being physically present.  
NO  
BOARD  
1. Reboot the system, then retry the command. If the NO BOARD  
indication persists, replace the TN798 Processor circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-910  
Table 3-390. TEST #886 Maintenance Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1-3  
FAIL  
The test failed. Maintenance was unable to establish a looparound link from  
the Packet Interface back to itself or was unable to receive data that was  
sent out over one side of the looparound link.  
1. Issue the test packet-interface AS command to retry the test. If the  
same error code is observed, background maintenance software will  
automatically attempt to reset the circuit pack and clear the problem.  
2. Retry the command and if the test fails, replace the TN798 Processor  
circuit pack.  
3. If the test continues to fail after replacing the TN798 Processor circuit  
pack, run the test packet P long command. If any of the tests fail, the  
fault may be on the Packet Bus. Refer to the PKT-BUS (Packet Bus)  
Maintenance documentation for recommended repair procedures.  
4. If the test continues to fail after the TN798 Processor circuit pack is  
replaced and with no other alarms associated with the Packet Bus or  
circuit packs connected to the Packet Bus, follow normal escalation  
procedures.  
PASS  
This test passed. The Packet Interface and its interface with the system  
software are functioning properly. If the system is still unable to place calls:  
1. Check for errors on the Packet Bus and Maintenance/Test circuit  
pack. Resolve those errors first.  
2. Check all other circuit packs connected to the Packet Bus. Packet Bus  
failures are likely to be caused by a faulty circuit pack connected to the  
backplane or bent pins on the back plane.  
Read and Clear Board Counters (#887)  
This test involves sending commands to read on-circuit pack error counters on  
the TN798 Processor circuit pack. It also verifies the message interface between  
the system software and the Packet Interface.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-911  
Table 3-391. TEST #887 Read and Clear Board Counters  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1006  
1137  
ABORT  
Packet Interface is in the out-of-service state so normal maintenance tests  
will not run on it.  
1. Use the display system-parameters maintenance command to identify  
which C-LAN circuit pack is administered with the Bus Bridge. Verify that  
the C-LAN circuit pack is present and is not alarmed.  
2. Reset the Packet Interface using the reset packet-interface AS  
command. Refer to the Packet Interface Reset Test (#889)  
maintenance documentation for repair procedures.  
2000  
2500  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals, a maximum of 3 times.  
Internal system error.  
1. Retry the command.  
NO  
The Packet Interface is not detected as being physically present.  
BOARD  
1. Reboot the system, then retry the command. If the NO BOARD  
indication persists, replace the TN798 Processor circuit pack.  
256  
512  
768  
FAIL  
The Packet Interface has an error counter set. The following error codes are  
possible: 256: Parity error 512: FIFO overflow 768: Parity error and FIFO  
overflow error. If error code 256 or 768 is reported, the Packet Interface  
received a parity error off the Packet Bus.  
a. First check for alarms logged against the Packet Bus. Refer to the  
PKT-BUS maintenance documentation to clear those errors first.  
b. Then check for alarms and errors logged against other circuit packs  
connected to the Packet bus. A list of packet circuit packs is  
presented in the first section of this repair procedure. Refer to the  
repair procedures for those circuit packs, in this manual, to clear  
those errors first.  
c. Replace the TN798 Processor circuit pack at a time that would cause  
the least disruption of service. The circuit pack is still functional but  
should be replaced.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-912  
Table 3-391. TEST #887 Read and Clear Board Counters — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
256  
512  
768  
FAIL  
(cont’d.)  
If error code 512 or 768 is reported for a Packet Interface, the receive  
FIFO in the Packet Interface has overflowed. This may be an  
indication that additional Packet Interface capacity is required. For  
the current hardware configuration, only two Packet Interfaces are  
provided, so the problem should be escalated if the following repair  
steps do not correct the problem:  
1. Retry the command after a one minute delay, and if the test  
continues to fail, replace the TN798 Processor circuit pack at a  
time that would cause the least service disruption.  
PASS  
The system software is able to communicate with the Packet Interface. If  
problems are still reported on the Packet Interface, check for failures using  
the Private Looparound test (#885) and Maintenance Looparound test  
(#886).  
Reset Test (#889)  
The reset action initializes the Packet Interface and causes the Packet Interface  
firmware on the TN798 Processor circuit pack to run a comprehensive set of  
diagnostic tests.  
The demand reset action aborts if the specified Packet Interface is in the  
in-service state.  
A Packet Interface is put in the out-of-service state automatically if it has been  
reset 4 times by background maintenance within the last 15 minutes,  
independent of the results of the reset action.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PKT-INT (Packet Interface)  
3-913  
Table 3-392. TEST #889 Reset Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1334  
ABORT  
The Packet Interface command queue is full. This should be a temporary  
condition caused by a high rate of commands being sent to a Packet  
Interface. Continued operation with a full command queue will cause a  
system WARM restart that may escalate to more severe restart levels.  
1. Retry the command at 10 second intervals, a maximum of 5 times.  
1362  
ABORT  
The Reset test is not allowed to run because the Packet Interface is in  
service. Resetting a Packet Interface that is in-service is not allowed, since  
this is a destructive test.  
1. Use the status packet-interface command to determine the service  
state of the Packet Interface. If the state is “out-of-service,” try the Reset  
command again.  
2000  
2500  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals, a maximum of 3 times.  
Internal system error  
1. Retry the command.  
NO  
BOARD  
The Packet Interface circuit pack is not detected as being physically  
present.  
1. Reboot the system, then retry the command. If the NO BOARD  
indication persists, replace the TN798 Processor circuit pack.  
5001  
5002  
FAIL  
FAIL  
FAIL  
The TDM clock has failed.  
1. Refer to the TDM-CLK to clear this failure.  
The Packet Bus has failed.  
1. Refer to PKT-BUS to clear this failure.  
Any  
Other  
Than  
Those  
Listed  
Above  
The Packet Interface diagnostic tests failed. The reset will run only on  
demand if the Packet Interface is in an out-of-service state.  
1. Retry the command reset packet-interface  
2. If the reset fails, replace the TN798 Processor circuit pack.  
PASS  
The Packet Interface diagnostic software passed. The Packet Interface is  
put back into service automatically.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-LINK (Property Management System Link)  
3-914  
PMS-LINK (Property Management  
System Link)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test pms l  
Full Name of MO  
PMS Link  
PMS-LINK  
PMS-LINK  
MINOR  
WARNING  
test pms  
PMS Link  
Property Management System (PMS) is a stand-alone computer system that a  
hotel/motel-type and a hospital-type environment use for services such as  
reservations, registration, messaging, housekeeping, night audit, billing, and  
inventory. The PMS Link provides a communications channel between DEFINITY  
Generic 1 or Generic 3iV2 and a customer-owned PMSs so that the PMS can  
interrogate the system about the information related to the following features:  
■
■
■
■
■
Message Waiting Notification  
Controlled Restriction  
Housekeeping Status  
Check-in/Check-out  
Room Change/Room Swap  
Refer to DEFINITY Enterprise Communications System Administrator’s Guide for  
details on the PMS feature. The PMS Link is administered to a data extension that  
provides a standard EIA 232C interface to the PMS. A PMS can be connected  
through a data module (PDM, MPDM, DTDM) and a port on the TN754 or  
TN754B Digital Line circuit pack, or through an ADU and a port on the TN726  
Digital Line circuit pack.  
The PMS Link Maintenance strategy includes a set of tests for periodic diagnosis,  
detection of errors during normal operation, actions for troubleshooting, and  
raising alarms for serious problems. PMS Link Maintenance uses a "try-and-wait"  
mechanism for maintaining the PMS Link. If a PMS Link is torn down due to an  
error, PMS Link Maintenance attempts to bring up the link immediately. If the trial  
of "Link Setup" fails, PMS Link Maintenance waits for five minutes before the next  
retry. If the number of retries reaches the value of a threshold (12), a Minor alarm  
is raised for service attention.  
PMS Link Maintenance does not cover the maintenance of the elements  
composing the PMS physical link (for example, the external PMS device, Data  
Module (PDM/MPDM/DTDM), and Digital Line Port of TN754 or TN754B Digital  
Line circuit pack, ADU and Data Line Port of TN726 Data Link circuit pack). If  
PMS Link Maintenance cannot restore the PMS Link, then the maintenance tests  
of these individual components of the PMS Link must be executed to diagnose  
faults. If system technician-demanded test pms-link command fails, no alarm is  
generated.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-LINK (Property Management System Link)  
3-915  
Procedures for Restoring the PMS Link  
1. Determine the status of the PMS Link.  
Enter status pms command and make sure that the PMS Link is not  
busied out for maintenance. If the link is "down," then continue with the  
next step.  
2. Where does the PMS Link connect?  
Enter display system hospitality and find out the destinations of the PMS  
Link.  
3. Determine the status of the data extension.  
Enter status data <extension> command and verify whether the data  
extension is in in-service/idle state. If the data extension is NOT available,  
then look for the extension number in Alt Name field of Hardware Error  
Log. Refer to the XXX-BD (Common Port Circuit Pack) Maintenance  
documentation for resolutions.  
4. Is a data channel on Network Control circuit pack in in-service/idle state?  
Enter list data command and find out the extension numbers of data  
channels on Network Control circuit pack. Enter status data <extension>  
command and make sure that at least one data channel is in  
in-service/idle state. If no data channel is available, then look for  
DATA-CHL/DATA-CON/DATA-BD errors in the Hardware Error Log. If  
present, refer to the DATA-BD (Network Control Circuit Pack) Maintenance  
documentation; if not present, escalate the error.  
5. Is the external PMS device available?  
Make sure that the PMS device is ON-LINE and ready for service. Check  
the physical connectivity between Data Module and the PMS device.  
It is recommended that you busy out the PMS Link before executing maintenance  
tests over objects composing the PMS Link. If the PMS Link is busied out, then all  
PMS Link maintenance actions are deactivated. The interference to tests of other  
MO is off.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-LINK (Property Management System Link)  
3-916  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-393. PMS-LINK Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
test pms sh r 1  
1
0
0
0
Any  
Any  
18 (a)  
busyout pms-link  
WARNING  
OFF  
OFF  
release pms-link  
test pms-link l  
257 (b)  
0-6,  
99,  
Link Retry Test  
(#215)  
MINOR/  
WARNING  
2
255  
513 (c)  
769 (d)  
1025 (e)  
1281 (f)  
1537 (g)  
1793 (h)  
2049 (i)  
2305 (j)  
0-6,255  
0-6,255  
None  
None  
None  
None  
None  
None  
None  
None  
test pms-link  
test pms-link  
3
4x  
3
1x  
3
Nx  
0-6,255  
0-6,255  
3
5x  
release pms-link or test  
pms-link  
2561 (k)  
2817 (l)  
0-6,255  
None  
None  
test pms-link  
3
10x  
3
20x  
3
30x  
3
3073 (m)  
3841 (n)  
7x  
None  
None  
3
2x  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
2. Minor alarms on this MO may be downgraded to Warning alarms based on the value used in the set  
options command.  
3. Is any integer.  
Notes:  
a. The PMS Link has been busied out for system technician-demanded  
maintenance via the busyout pms-link command. The link is torn down.  
Enter the release pms-link command to restore the link.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-LINK (Property Management System Link)  
3-917  
b. The Link Retry Test (#215) fails. The Aux Data field contains either the  
Channel ID of Data Channels on Network Control circuit pack (that is, 3 for  
Channel 01, 4 for Channel 02, 5 for Channel 03, 6 for Channel 04) or an  
Error Type of 99 indicating no data channels are available for setting up  
the link, or an Error Type of 255 for the internal system error generated  
upon initialization or power-up. Refer to the ‘‘Procedures for Restoring the  
PMS Link’’ section for resolution.  
c. The PMS physical link is down due to the following causes: cable to the  
PMS device is disconnected; the PMS device is powered off; or the data  
extension to which the PMS device connects has been busied out. The  
Aux Data field contains the Channel ID of Data Channels on Network  
Control circuit pack (that is, 3 for Channel 01, 4 for Channel 02, 5 for  
Channel 03, 6 for Channel 04) or an Error Type of 255 for the internal  
system error generated upon initialization or power-up. Check the  
connectivity of wire and cable among wall jacket, data module, and the  
PMS device. Enter status data extension and verify that the data  
extension of the PMS device is in in-service/idle state. If the data extension  
is not available, then refer to the ‘‘Procedures for Restoring the PMS Link’’  
section for recommended repair strategy.  
d. No communication between DEFINITY Generic 1 or Generic 3iV2 and  
PMS for a period of time (the time is specified in "system hospitality"  
administration). The PMS Link is torn down. To clear this error, refer to the  
‘‘Procedures for Restoring the PMS Link’’ section.  
e. The link was taken down because the switch could not receive an  
incoming message from the PMS. The message from the PMS repeatedly  
had corrupted data or the switch received requests for acknowledgment  
but never received a message to be processed. If this error type recurs  
frequently (that is, more than once a month), then advise the customer to  
call the vendor of the PMS to check out the PMS device. Once the PMS  
Link is successfully established, this error disappears from the Hardware  
Error Log.  
f. The link was taken down because the switch could not send an outgoing  
message. The message, which was sent but not acknowledged, was  
flushed. If this error type recurs frequently (that is, more than once a  
month), then advise the customer to call the vendor of the PMS to check  
out the PMS device. Once the PMS Link is successfully established, this  
error disappears from the Hardware Error Log.  
g. The PMS has been busied out for maintenance at the request of the PMS.  
The PMS Link is torn down. The reason code (N), if present, is that  
supplied by the PMS in the request message. If this error type recurs  
frequently (that is, more than once a month), then advise the customer to  
call the vendor of the PMS to check out the PMS device. Once the PMS  
Link is successfully established, this error disappears from the Hardware  
Error Log. No alarm is raised against this error.  
h. PBX buffer overflows due to either heavy call traffic or PMS protocol  
message rate being faster than the PMS/PBX protocol specifications  
allow. The PMS Link is torn down. PMS Link maintenance software waits  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-LINK (Property Management System Link)  
3-918  
for five minutes before attempting to set up the link again. If this error type  
recurs frequently (that is, more than once a month), advise the customer to  
call the vendor of the PMS to check out the PMS device. Once the PMS  
Link is successfully established, this error disappears from the Hardware  
Error Log (see Note).  
NOTE:  
The PMS should be checked for adherence to message rate defined  
in the PMS/PBX protocol specifications. No alarm is raised against  
this error.  
i. The attempt to swap the database between PBX and PMS failed 3 times  
consecutively due to excessive PMS/PBX protocol violations, buffer  
overflows, or PMS Link outages. The PMS Link is NOT torn down. If this  
error type recurs frequently (that is, more than once a month), then advise  
the customer to call the vendor of the PMS to check out the PMS device.  
Once the PMS Link is successfully established, this error disappears from  
the Hardware Error Log. No alarm is raised against this error.  
j. The PMS Link has been busied out for system technician-demanded  
maintenance via the busyout pms-link command or has been brought  
down via the test pms-link long command. The PMS Link is torn down,  
and PMS Link maintenance stops attempting to reestablish the link in the  
case where the busyout pms-link command has been used. When the  
test pms-link long command has been used, PMS Link maintenance  
continues to try to reset the link. To restore the PMS Link after use of the  
busyout pms-link command, issue the release pms-link command. To  
restore the PMS Link after use of the test pms-link long command, issue  
the test pms-link command.  
k. The PMS Link is physically established, but the protocol has not been  
started by the PMS before the protocol timer expires. The PMS Link is NOT  
torn down. If this error type recurs frequently (that is, more than once a  
month), advise the customer to call the vendor of the PMS to check out the  
PMS device. Once the PMS Link is successfully established, this error  
disappears from the Hardware Error Log.  
NOTE:  
The PMS should be checked to make sure that it attempts to start the  
protocol according to the PMS/PBX protocol specifications. No  
alarm is raised against this error.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-LINK (Property Management System Link)  
3-919  
l. Error Type 2817:  
Aux values of concern:  
10x  
20x  
30x  
The PMS violated the application protocol. The first message  
after a request to initiate a database exchange was not the start  
of a database exchange. The message is processed. If this  
error type with this aux data value recurs frequently (that is,  
more than once a month), then advise the customer to call the  
vendor of the PMS to check out the PMS device. Once the PMS  
Link is successfully established, this error disappears from the  
Hardware Error Log. See Note.  
The PMS violated the application protocol. The start of a  
database exchange was received in a state in which it was not  
expected. The message is ignored. If this error type with this  
Aux data value recurs frequently (that is, more than once a  
month), then advise the customer to call the vendor of the PMS  
to check out the PMS device. Once the PMS Link is successfully  
established, this error disappears from the Hardware Error Log.  
See the next Note.  
The PMS violated the application protocol. The end of a  
database exchange was received when no exchange was in  
progress. The message is ignored. If this error type with this Aux  
Data value recurs frequently (that is, more than once a month),  
then advise the customer to call the vendor of the PMS to check  
out the PMS device. Once the PMS Link is successfully  
established, this error disappears from the Hardware Error Log.  
NOTE:  
The PMS should be assessed for adherence to the  
PMS/PBX protocol specifications. No alarm is raised  
against this error.  
m. The link was taken down by the switch because the threshold for  
application protocol violations has been exceeded by the PMS. The  
protocol never started and messages were received and/or messages  
were received in a state in which they were not expected. (Refer to Error  
Type 2817 for recommended strategy.)  
n. Link was taken down by the switch because the threshold for link protocol  
violations has been exceeded by the PMS. PMS is sending "garbage" to  
the switch.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-LINK (Property Management System Link)  
3-920  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the Link  
Retry Test, for example, you may also clear errors generated from other tests in  
the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Link Tear Down Test (#213)  
Link Retry Test (#215)  
D/ND  
D
X
X
X
ND  
1. D = Destructive; ND = Nondestructive  
Link Tear Down Test (#213)  
This test is destructive.  
This test disconnects the existing link between the system and the external PMS  
device. If the link has been disconnected already, then this test just returns  
"PASS." All resources allocated for a PMS Link are released after this test.  
Table 3-394. TEST #213 Link Tear Down Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
40  
50  
ABORT Internal System Error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1010  
ABORT The PMS Link has been busied out and placed in the out-of-service state.  
1. Enter release pms-link command to release the PMS Link from busyout  
state.  
2. Retry test pms long command to execute the test.  
FAIL  
Internal System Error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The PMS Link is torn down.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-LINK (Property Management System Link)  
3-921  
Link Retry Test (#215)  
This test sends a message to the PMS software process to make a data call to  
the extension where the PMS device connects. If the PMS Link is already up, then  
this test passes without making any data call.  
Table 3-395. TEST #215 Link Retry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
10  
20  
ABORT  
ABORT  
Internal System Error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal System Error.  
30  
1. Refer back to the ‘‘Procedures for Restoring the PMS Link’’ section for  
resolution.  
1010  
ABORT  
The PMS Link has been busied out and placed in the out-of-service state.  
1. Enter release pms-link command to release the PMS Link from busyout  
state.  
2. Retry test pms command to execute the test.  
FAIL  
The PMS Link CANNOT be established.  
1. Refer back to the ‘‘Procedures for Restoring the PMS Link’’ section for  
restoring the PMS Link.  
PASS  
The PMS Link is up.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-PRNT/JNL-PRNT (PMS Printer Link)  
3-922  
PMS-PRNT/JNL-PRNT (PMS Printer  
Link)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
PMS-PRNT/JNL- MINOR  
PRNT  
test journal  
pms-log/wakeup-log l  
PMS Printer/ Journal Printer  
PMS-PRNT/JNL- WARNING  
PRNT  
test journal  
pms-log/wakeup-log  
PMS Printer/ Journal Printer  
NOTE:  
PMS-PRNT stands for the pms-log printer. JNL-PRNT stands for the  
wakeup-log printer. Since the maintenance strategy for the both the  
JNL-PRNT and PMS-PRNT MOs is the same, both of these MOs are  
described in this section.  
There can be up to two journal printers: the wakeup-log printer, which is shared  
between the Automatic Wakeup feature and the Emergency Access to Attendant  
feature to print scheduled reports and log of events, and the pms-log printer,  
which is used as a backup of the PMS output device to print the audit trail data of  
all PMS transactions executed by the system and the PMS Housekeeping Status  
Change events while the PMS Printer Link is not available. The journal printer link  
is administered to a data extension that provides a standard EIA 232C interface  
to the printer. The printer can be connected through a data module (PDM,  
MPDM, DTDM) and a port on the TN754 or TN754B Digital Line circuit pack, or  
through an ADU and a port on the TN726 Data Line circuit pack.  
PMS Printer Link Maintenance provides a strategy in the system for maintaining  
the link between the system and a PMS device (an external Journal Printer  
device). The strategy includes a set of tests for periodic diagnosis, detection of  
errors during normal operation, actions for troubleshooting, and raising alarms  
for serious problems. PMS Printer Link Maintenance uses a try-and-wait  
mechanism for maintaining the PMS Printer Link. If a PMS Printer Link is torn  
down due to an error, PMS Printer Link Maintenance intends to bring the link up  
immediately. If the trial of Link Setup fails, PMS Link Maintenance waits for five  
minutes before the next retry. If the number of retries reaches the value of a  
threshold (15), a Minor alarm is raised for service attention.  
PMS Printer Link Maintenance does not cover the maintenance of the elements  
composing the journal printer physical link (for example, the external printer  
device, Data Module (PDM/MPDM/DTDM) and Digital Line Port of TN754 or  
TN754B Digital Line circuit pack, ADU and Data Line Port of TN726 Data Line  
circuit pack). If PMS Printer Link Maintenance cannot restore the PMS Printer  
Link, then the maintenance tests of these individual components of the PMS Link  
must be executed to diagnose faults.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-PRNT/JNL-PRNT (PMS Printer Link)  
3-923  
Procedures for Restoring the PMS Printer Link  
1. Determine the status of the PMS Printer Link.  
Enter status journal-printer wakeup-log|pms-log command and make  
sure that the journal printer link is not busied out for maintenance. If the  
link is down, then continue to the next step.  
2. Where does the journal printer link connect?  
Enter display system hospitality and find out the destinations of the PMS  
Printer Link.  
3. Determine the status of the data extension.  
Enter status data extension command and verify whether the data  
extension is in the in-service/idle state. If the data extension is NOT  
available, then look for the extension number in Alt Name field of  
Hardware Error Log. Refer to XXX-BD (Common Port Circuit Pack)  
Maintenance documentation for resolutions.  
4. Is a data channel on the Processor circuit pack in the in-service/idle state?  
Enter list data command and find out the extension numbers of data  
channels on Processor circuit pack. Enter status data extension  
command and make sure that at least one data channel is in the  
in-service/idle state. If no data channel is available, look for  
DATA-CHL/DATA-CON/DATA-BD errors in the Error Log. If present, refer to  
“DATA-BD”Maintenance documentation.  
5. Is the external printer device available?  
Make sure that the printer device is ON-LINE and ready for service. Check  
the physical connectivity between Data Module and the printer device.  
It is recommended that you busyout the PMS Printer Link before executing  
maintenance tests over objects composing the PMS Printer Link. If the PMS  
Printer Link is busied out, then all PMS Printer Link maintenance actions are  
deactivated. The interference to tests of other MOs is off.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-PRNT/JNL-PRNT (PMS Printer Link)  
3-924  
Error Log Entries and Test to Clear Values  
Table 3-396. PMS-PRNT/JNL-PRNT Link Maintenance Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Any  
Alarm Level  
Test to Clear Value  
test journal  
1
0
0
0
Any  
Any  
wakeup-log|pms-log sh  
18 (a)  
busyout journal  
wakeup-log/  
pms-log  
WARNING  
OFF  
release journal  
wakeup-log|pms-log  
257 (b)  
513 (c)  
769 (d)  
0,  
3 to 6  
255  
Link Retry Test  
(#215)  
MINOR/  
WARNING  
OFF  
test journal  
wakeup-log|pms-log 1  
2
0,  
3 to 6  
255  
test journal  
wakeup-log|pms-log  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Both PMS Printer and Journal Printer are administered to the same extension, and the printer is not  
connected. Refer to the ‘‘Procedures for Restoring the PMS Printer Link’’ section for resolution.  
2. Minor alarms on this MO may be downgraded to Warning alarms based on the value used in the set  
options command.  
Notes:  
a. System Technician busied out the Journal Printer Link. The link is torn  
down. Enter release command to restore the link.  
b. Link Retry Test (#215) fails. Physical link cannot be set up, usually  
because of hardware problems such as power off or cable disconnect.  
The Aux Data field contains the Channel ID of Data Channels on Network  
Control circuit pack (that is, 3 for Channel 01, 4 for Channel 02, 5 for  
Channel 03, 6 for Channel 04), an Error Code 255 for the Internal system  
error, or 0 which indicates that the data module connected to the PMS  
Printer Link is out-of-service. Refer to ‘‘Procedures for Restoring the PMS  
Printer Link’’ section for resolution.  
c. Physical link cannot be set up, usually because of hardware problems  
such as power off or cable disconnect. The PMS Printer Link physical link  
is down due to the following causes: cable to the printer device is  
disconnected, the printer device is powered off, or the data extension  
where the printer device connects to has been busied out. The Aux Data  
field contains the Channel ID of Data Channels on Network Control circuit  
pack (that is, 3 for Channel 01, 4 for Channel 02, 5 for Channel 03, 6 for  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-PRNT/JNL-PRNT (PMS Printer Link)  
3-925  
Channel 04). Check the connectivity of wire and cable among wall jacket,  
data module, and the printer device. Enter status data <extension> and  
verify that the data extension of the printer device is in the in-service/idle  
state. If the data extension is not available, then refer to the ‘‘Procedures  
for Restoring the PMS Printer Link’’ section for resolution.  
d. Link idle timer; link comes down. This error indicates that the printer  
device is in an off-line state, for example, paper jam or paper out for a  
printer device. Check the printer device and act promptly to put it back to  
on-line state. Enter test journal wakeup-log|pms-log command to set up  
the printer link.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the Link  
Retry Test, for example, you may also clear errors generated from other tests in  
the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Link Tear Down Test (#213)  
Link Retry Test (#215)  
D/ND  
D
X
X
X
ND  
1. D = Destructive; ND = Nondestructive  
Link Tear Down Test (#213)  
This test is destructive.  
This test disconnects the existing link between the system and the external  
printer device. If the link has been disconnected already, this test just returns  
PASS. All resources allocated for a PMS Printer Link are released after this test.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-PRNT/JNL-PRNT (PMS Printer Link)  
3-926  
Table 3-397. TEST #213 Link Tear Down Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
40  
ABORT  
ABORT  
Internal system error  
Internal system error  
50  
1. Retry the command at 1minute intervals a maximum of 5 times.  
The link has been busied out to out-of-service.  
1010  
ABORT  
1. Enter release journal wakeup-log|pms-log command to release the  
link from busyout state.  
2. Retry test journal wakeup-log|pms-log l command to execute the  
test.  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The link is torn down.  
PASS  
Link Retry Test (#215)  
This test sends a message to the journal printer management software process  
to make a data call to the extension where the printer device connects to. If the  
journal printer link is already up, this test passes without making any data call.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PMS-PRNT/JNL-PRNT (PMS Printer Link)  
3-927  
Table 3-398. TEST #215 Link Retry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
10  
ABORT  
ABORT  
Internal system error  
Internal system error  
20  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
30  
ABORT  
1. Refer to the ‘‘Procedures for Restoring the PMS Printer Link’’ section for  
instructions.  
1010  
ABORT  
The PMS Printer Link has been busied out to out-of-service.  
1. Enter release journal wakeup-log|pms-log command to release the  
link from busyout state.  
2. Retry test journal wakeup-log|pms-log l command to execute the  
test.  
FAIL  
The link CANNOT be established.  
1. Refer to the ‘‘Procedures for Restoring the PMS Printer Link’’ section for  
instructions.  
PASS  
The link is up.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-928  
PPP-PT (Control LAN Packet/Port)  
MO Name (in  
Alarm Log)  
1
Alarm Level  
MAJOR  
Initial Command to Run  
test port UUCSSpp long  
test port UUCSSpp long  
test port UUCSSpp  
Full Name of MO  
PPP-PT  
PPP Port Maintenance  
PPP Port Maintenance  
PPP Port Maintenance  
PPP-PT  
PPP-PT  
MINOR  
WARNING  
1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation (A, B,  
C, D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21). pp is the two  
digit port number (01, 02, ...).  
The TN799 Control LAN (CLAN) packet port circuit pack provides TCP/IP  
connection to adjuncts applications such as CMS, Intuity, and DCS Networking.  
The CLAN circuit pack has 1-10baseT Ethernet connection and up to 16 DS0  
physical interfaces for PPP connections. Multiple CLAN circuit packs in a system  
gives additional TCP/IP capacity.  
A remote socket control link (RSCL) links the CLAN and the SPE to pass call  
control and other management information. Since one link serves all the ports on  
the circuit pack, maintenance of the RSCL is part of the CLAN circuit pack  
maintenance.  
NOTE:  
The CLAN TN799 circuit pack combines the functions of the PGATE and PI  
circuit packs into one circuit pack. The PGATE or PI can be used with the  
CLAN to create an X.25 to TCP/IP bridge for adjunct and DCS connectivity.  
Control LAN Congestion Controls  
The switch activates congestion controls on CLAN when it detects buffers  
exceeding the threshold. The switch releases the congestion controls when the  
CLAN reports that its buffer level has returned to normal levels.  
If congestion:  
Then the switch:  
Raises MINOR alarm  
Raises MINOR alarm  
Retires MINOR alarm  
Persists for a 14-minute interval  
Exhausts buffers  
Ceases for 12 minutes  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-929  
Error Log Entries and Test to Clear Value  
Table 3-399. PPP-PT Error Log Entries  
Aux  
Alarm  
Level  
On/Off  
Board  
Error Type  
Data  
Associated Test  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
ON  
test port UUCSSpp s  
1 (a)  
0
SCOTCH Sync  
Looparound  
Test (#1275)  
MINOR  
test port UUCSSpp l r 3  
257 (b)  
513 (c)  
769 (d)  
1281 (e)  
0
0
0
0
WARNING  
MINOR  
OFF  
OFF  
OFF  
WARNING  
1537,1538 See  
Session Status Test  
(#1286)  
MINOR  
OFF  
(f)  
note  
1793-1920  
(g)  
See  
note  
2305-2560  
(h)  
See  
note  
2561-2816  
(h)  
See  
note  
3329 (i)  
35768  
0-1  
TCP/IP Ping Test  
(#1281)  
WARNING  
MAJOR  
OFF  
ON  
3585 (j)  
TDM Looparound  
Test (#1285)  
test port UUCSSpp l r 3  
Continued on next page  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. Error Type 001: SCOTCH Synchronous Looparound Test (#1275) failed.  
1. Test the port (test port UUCSSpp long).  
2. Refer to SCOTCH Synchronous Looparound Test (#1275) repair  
procedures.  
b. Error Type 257: CLAN port detected overrun or underrun condition that  
may indicate a hardware problem.  
1. Test for hardware problem (test port UUCSSpp long).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-930  
2. Refer to SCOTCH Synchronous Looparound Test (#1275) repair  
procedures to verify repair.  
3. Clear the alarm (test port UUCSSpp long clear).  
c. Error Type 513: PPP link lost end-to-end connectivity.  
1. Test for hardware problem (test port UUCSSpp long).  
2. Run TDM Looparound Test (#1285) and refer to repair procedures if  
there is a hardware problem.  
If there is no hardware problem, the switch tries to re-establish PPP  
link.  
d. Error Type 769: Port received an invalid frame, which  
■
■
■
is greater than the maximum length  
contains CRC errors  
violates the link level protocol.  
1. Test the port (test port UUCSSpp long).  
2. Refer to TDM Port Looparound Test (#1285) to verify repair.  
3. Clear the alarm (test port UUCSSpp long clear).  
e. Error Type 1281: System software received an indication that the far-end  
has requested a disconnect of a session on this link. This is a log-only  
error.  
f. Error Type 1537, 1538: Some or all port sessions (sockets) are down.  
If the switch indicates that:  
Some of the sessions are down  
All of the sessions are down  
Then it:  
Raises off-board WARNING  
Raises off-board MINOR alarm  
1. Test the port (test port UUCSSpp short).  
2. Refer to Session Status Test (#1286) repair procedure to verify  
repair.  
g. Error Type 1793-1920: system software received an indication that a  
socket was closed due to an error. Error Type indicates the application  
associated with this socket.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-931  
Error Type Application  
1793  
Unused  
DCS  
1794  
1795  
AUDIX  
1796  
CMS  
1797  
ISDN Gateway  
1798-1920  
Reserved for  
future  
Aux Data indicates the internal application number.  
h. Error Type 2305-2816: System software detected a session is down. Aux  
Data indicates the session number. These are log only errors. Error types  
2305-2560 are for session numbers 1-256. Error types 2561-2816 are for  
session numbers 257-512.  
i. Error Type 3329: TCP/IP Ping Test failed.  
1. Test the port (test port UUCSSpp short).  
2. Refer to TCP/IP Ping Test (#1281) repair procedures.  
j. Error Type 3585: TDM Port Looparound Test (#1285) failed.  
1. Test the port (test port UUCsspp long).  
2. Refer to TDM Looparound Test (#1285) repair procedure.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Investigate errors in the order they appear in the table below.  
Table 3-400. System Technician-Demanded Tests: PPP-PT  
Short Test  
Long Test  
Sequence  
1
Order of Investigation  
Sequence  
D/ND  
D
TDM Looparound Test (#1285)  
X
X
X
X
X
SCOTCH Synchronous Looparound Test (#1275)  
TCP/IP Ping Test (#1281)  
D
X
X
X
ND  
ND  
ND  
Session Status Test (#1286)  
PPP Link Status Test (#1279)  
1. D = Destructive, ND = Non-destructive  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-932  
TDM Looparound Test (#1285)  
NOTE:  
This test is destructive.  
This test verifies whether the CLAN PPP port can send and receive data on the  
TDM bus. This test has a tone generator send tones on a timeslot, and it has a  
tone receiver receive tones on another timeslot. The tones are looped through the  
ppp port.  
If the received tones:  
Then:  
Match the tones sent  
The test passes  
The test fails  
Do not match the tones sent  
Test failure indicates failure of the  
■
■
■
CLAN (TN799) circuit pack  
TDM Bus  
Tone generator / tone receiver circuit pack  
Table 3-401. TEST #1285 TDM Looparound Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
The port is in use.  
1. Determine port status (status clan-port UUCSSpp).  
2. Retry the command when the port is idle. The port may be forced to the  
idle state by executing a busyout port UUCSS command.  
3. Escalate if the problem persists.  
NOTE:  
The busyout port command is destructive, causing all calls and links  
associated with the port to be torn down.  
1002  
1003  
ABORT  
ABORT  
No TDM bus timeslots available for the test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
No more tone receivers idle for use in this test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-933  
Table 3-401. TEST #1285 TDM Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Did not receive circuit pack test response within the allowable time period.  
1. If this problem persists, reset the circuit pack (busyout board UUCSS,  
reset board UUCSS, and release board UUCSS).  
2. If the problem persists, replace the circuit pack.  
Internal system error.  
2012  
2100  
ABORT  
ABORT  
FAIL  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
Could not allocate the necessary system resources to run test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
Received tones do not match transmitted tones.  
1. Retry command at 1-minute intervals, up to 3 times.  
2. If the problem persists, refer to TDM-BUS, Tone Generator, and Tone  
Receiver repair procedures.  
3. If the problem persists, reset the board (busyout board UUCSS, reset  
board UUCSS, and release board UUCSS). Repeat the test.  
4. If the problem persists, replace the circuit pack.  
PASS  
Port connections across the TDM bus function properly.  
SCOTCH Synchronous Looparound Test (#1275)  
NOTE:  
This test is destructive.  
This test verifies the circuit in the datapath of a ppp call. This test fails if the data  
transmitted on the port does not match the data received in the looparound  
mode. Failure of this test indicates a port hardware fault on the circuit pack.  
This test aborts if calls are using the port, or if the PPP link associated with the  
port is connected. To avoid this, first enter busyout data-module extension, or  
busyout port UUCSSpp, or busyout link link#, which will cause all calls and  
links using the port to be torn down.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-934  
Table 3-402. TEST #1275 SCOTCH Synchronous Looparound Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The port is in use or PPP link is connected.  
1000  
ABORT  
1. Determine when the port is available for testing (status clan-port  
UUCSSpp).  
2. The port may be forced to the idle state by executing a busyout port  
UUCSSpp command.  
NOTE:  
This command is destructive, causing all calls and links using the port  
to be torn down.  
1002  
1963  
ABORT  
ABORT  
No TDM bus timeslots available for the test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
Firmware indicates that the port is in use or ppp link is connected.  
1. Determine when the port is available for testing (status clan-port  
UUCSSpp).  
2. The port may be forced to the idle state by executing a busyout port  
UUCSSpp command.  
NOTE:  
This command is destructive, causing all calls and links using the port  
to be torn down.  
2000  
2012  
ABORT  
ABORT  
Did not receive circuit pack test response within the allowable time period.  
1. If this problem persists, reset the circuit pack (busyout board UUCSS,  
reset board UUCSS, and release board UUCSS).  
2. If the problem persists, replace the circuit pack.  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-935  
Table 3-402. TEST #1275 SCOTCH Synchronous Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Could not allocate the necessary system resources to run test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
2100  
ABORT  
FAIL  
CLAN circuit pack detected test failure.  
1. If the problem persists, reset the circuit pack (busyout board UUCSS,  
reset board UUCSS, and release board UUCSS).  
2. If the problem persists, replace the circuit pack.  
Port circuitry functioning properly.  
PASS  
TCP/IP Ping Test (#1281)  
This non-destructive test fails if the endpoint fails to respond. Use this test to  
check the circuitry in the data path for a peer-to-peer IP layer connection.  
Table 3-403. TEST #1281 TCP/IP Ping Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1, 2, 7,  
11  
ABORT  
Internal error  
1. Retry the command at 1-minute intervals up to 3 times  
2. Escalate if the problem persists.  
1005  
1124  
ABORT  
Test configuration is incorrect.  
1. Verity PPP link is in-service (status clan-port UUCSSpp or status link  
n).  
2. Repeat the test.  
3. Escalate if the problem persists.  
ppp link is not enabled.  
ABORT  
1. Verify that the ppp link is enabled (status port UUCSSpp, status link  
n, or display data-module).  
2. If the link is not enabled, enable the link (change data-module).  
3. Repeat the test.  
4. Escalate if the problem persists.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-936  
Table 3-403. TEST #1281 TCP/IP Ping Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PPP link not in service.  
1125  
ABORT  
1. Verify whether ppp link is in service (status port UUCSSpp or status  
link n).  
2. If the ppp link is not in service, release the link (release link n or  
release port UUCSSpp).  
3. Repeat the test.  
4. Escalate if the problem persists.  
2000  
ABORT  
Response to the test was not received from the CLAN circuit pack within  
the allowable time period.  
1. If this result occurs repeatedly, attempt to reset the circuit pack if the  
other ports on the board are not in use (Yellow LED is off). Reset the  
circuit pack (busyout board UUCSS, reset board UUCSS, and  
release board UUCSS).  
2. If this result occurs again, replace the circuit pack.  
Internal system error.  
2012  
2100  
2500  
1003  
ABORT  
ABORT  
ABORT  
FAIL  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
Could not allocate the necessary system resources to run test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
Ping to the destination failed due to on-board problem.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. If the problem persists, reset the circuit pack (busyout board UUCSS,  
reset board UUCSS, and release board UUCSS).  
3. If the problem persists, re-administer the PPP connection through a  
different PPP port, if available.  
4. If the problem still persists, or if there are no other available PPP ports,  
replace the circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-937  
Table 3-403. TEST #1281 TCP/IP Ping Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1007  
FAIL  
Ping to the destination failed due to the destination down.  
1. A PPP destination or a component in the path (e.g., DS1 trunk) may be  
down. Check the status of the destination or other components in the  
path.  
2. If the destination and all components in the path are in-service, ping  
the PPP destinations (ping ip-address xxx.xxx.xxx.xxx).  
3. Escalate if the problem persists.  
PASS  
TCP/IP Ping Test (#1281) is successful.  
Session Status Test (#1286)  
This non-destructive test determines the status of all PPP port sessions. This test  
queries the system software on port session status.  
If the system software indicates that:  
All port sessions are up (ALL UP)  
Then the switch:  
Raises no alarm, or retires alarm  
Raises MINOR alarm  
Some port sessions are up (SOME UP)  
All port sessions are down (ALL DOWN)  
Raises MINOR alarm  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-938  
Table 3-404. TEST #1286 Session Status Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ppp link is not enabled.  
1124  
ABORT  
1. Verify that the ppp link is enabled (status port UUCSSpp, status link n,  
or display data-module).  
2. If the link is not enabled, enable the link (change data-module).  
3. Repeat the test.  
4. Escalate if the problem persists.  
PPP link not in service.  
1125  
ABORT  
1. Verify whether PPP link is in service (status port UUCSSpp or status  
link n).  
2. If the PPP link is not in service, release the link (release link n or release  
port UUCSSpp).  
3. Repeat the test.  
4. Escalate if the problem persists.  
2000  
ABORT  
Did not receive circuit pack test response within the allowable time period.  
1. If the problem persists, reset the circuit pack (busyout port UUCSSpp,  
reset board UUCSS, and release board UUCSS).  
2. If the problem persists, replace the circuit pack.  
Could not locate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
2100  
2500  
1
ABORT  
ABORT  
FAIL  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
System software indicates at least one PPP link session is down (SOME UP).  
1. Isolate downed sessions (status port UUCSSpp or status link n).  
Follow actions based on session information.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-939  
Table 3-404. TEST #1286 Session Status Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2
FAIL  
System software indicates all PPP sessions are down (ALL DOWN).  
1. Test the port (test port UUCSSpp) to verify the SCOTCH Synchronous  
Looparound Test (#1275) result.  
2. If test passes, wait for system software to indicate ALL UP.  
3. If the test fails, check the destination and other components in the path.  
4. If the destination and other components in the path are in-service, take  
action based on session information.  
PASS  
All sessions up.  
PPP Link Status Inquiry Test (#1279)  
This non-destructive test determines the state of the PPP link. The test passes  
only if the link is up.  
Table 3-405. TEST #1279 PPP Link Status Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ppp link is not enabled.  
1124  
ABORT  
1. Verify that the ppp link is enabled (status port UUCSSpp, status link  
n, or display data-module).  
2. If the link is not enabled, enable the link (change data-module).  
3. Repeat the test.  
4. Escalate if the problem persists.  
PPP Link is not in service.  
1125  
ABORT  
1. Verify whether PPP link is in-service (status port UUCSSpp or status  
link n).  
2. If the PPP link is not in service, release the link (release link n or  
release port UUCSSpp).  
3. Repeat the test.  
4. Escalate if the problem persists.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PPP-PT (Control LAN Packet/Port)  
3-940  
Table 3-405. TEST #1279 PPP Link Status Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Could not locate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals, up to 5 times.  
2. Escalate if the problem persists.  
2100  
ABORT  
ABORT  
FAIL  
2500  
Internal system error.  
1. Retry the command at 1-minute intervals, up to 3 times.  
2. Escalate if the problem persists.  
PPP link is down.  
1. Test the port (test port UUCSSpp long) to verify the SCOTCH  
Synchronous Local Loop Around Test (#1275) result.  
2. If the test passes, wait for sessions to come up.  
3. If the test fails, check the destination and other components in the path  
(e.g., DS1 trunks).  
4. If the destination and other comonents in the path are in-service and  
the test still fails, execute busyout port UUCSSpp and release port  
UCCSSpp, and repeat the test.  
5. If the test still fails, reset the circuit pack (busyout board UUCSS, reset  
board UUCSS, and release board UUCSS). Repeat the test.  
6. If the problem persists, replace the circuit pack.  
PPP link is up.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-941  
PR-MAINT (Maintenance Processor)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
1
PR-MAINT  
MIN  
test processor a/b sh/l  
Maintenance/Tape Processor  
1. The full Name of the MO in a 386 system is Maintenance Processor.  
NOTE:  
For systems with a TN790 Processor Circuit Pack use maintenance object  
PR-MAINT (Maintenance Processor TN790 RISC Systems).  
The TN786B Processor circuit pack is comprised of the 80386 Processor  
(PROCR), the Maintenance Processor (PR-MAINT), and the Memory (MEMORY).  
On the TN786B circuit pack, PR-MAINT is responsible for monitoring the sanity of  
the 80386 Processor.  
The major difference between the two circuit packs is that on the TN786B circuit  
pack, there is no tape for PR-MAINT to control and Memory is on the circuit pack.  
The rest of the functionality is the same. On both circuit packs, PR-MAINT  
contains the hardware required for controlling the environmental conditions. The  
Maintenance/Tape Processor provides the serial interfaces for the administration  
terminal and CDR ports. The Maintenance/Tape Processor also provides the  
communications interface to INADS for alarm reporting and remote maintenance  
capability.  
!
WARNING:  
If the TN786B circuit pack must be replaced, and if there is a blank in the  
Expansion Memory circuit pack slot (that is, in the slot immediately to the  
right of the TN786B circuit pack), remove the blank before removing the  
circuit pack. Otherwise, the circuit pack and/or the two connectors that are  
used to connect the Expansion Memory circuit pack (if available) might  
become damaged.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-942  
Error Log Entries and Test to Clear Values  
Table 3-406. Maintenance/Tape Processor Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm On/Off  
1
Associated Test  
Level  
Board  
Test to Clear Value  
2
0
0
Any  
Any  
Any  
test processor a/b sh r 1  
test processor a/b l r 3  
test processor a/b r 2  
1 (a)  
Any  
Any  
MTP Reset Test (#101)  
MIN  
ON  
257 (b)  
MTP Sanity Handshake Test  
(#106)  
513 (c)  
769 (d)  
1025 (e)  
1537 (f)  
1793 (g)  
Any  
Any  
Any  
Any  
Any  
MTP Analog Loop Around  
Test (#103)  
MIN  
MIN  
MIN  
MIN  
MIN  
ON  
ON  
OFF  
ON  
ON  
test processor a/b r 8  
test processor a/b l r 3  
test processor a/b r 5  
test processor a/b r 3  
test processor a/b r 3  
MTP Dual Port Ram Test  
(#104)  
MTP Outpulse Relay Test  
(#102)  
MTPManager I Loop Around  
Test (#228)  
MTP Aux Loop Around Test  
(#229)  
1. You must manually repeat the command with the "long"option the designated number of times from  
the administration terminal or from a remote administration terminal because the Sanity Timer Test  
(#83) logs you off.  
2. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. The MTP Reset Test (#101) has failed.  
b. The MTP Sanity Handshake Test (#106) has failed.  
c. The MTP Analog Loop Around Test (#103) has failed.  
d. The MTP Dual Port Ram Test (#104) has failed. An error of 769 with an aux  
data of 5 indicates a hardware problem and testing will not clear it. The  
circuit pack should be replaced.  
e. The MTP Outpulse Relay Test (#102) has failed.  
f. The MTP Manager I Loop Around Test (#228) has failed.  
g. The MTP Aux Loop Around Test (#229) has failed.  
NOTE:  
Refer to the FAIL section of each test that fails for further instructions.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-943  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the MTP Reset Test, for example, you may also clear  
errors generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Processor Software Initiated Interrupt Test (#77) (a)  
Processor ROM Checksum Test (#80) (a)  
Processor Non-maskable Interrupt Test (#82) (a)  
Processor Sanity Timer Test (#83) (a)  
MTP Reset Test (#101)  
D/ND  
ND  
ND  
ND  
D
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
D
MTP Dual Port Ram Test (#104)  
D
MTP Sanity Handshake Test (#106)  
MAP Manager I Loop Around Test (#228)  
MTP Analog Loop Around Test (#103)  
MTP Outpulse Relay Test (#102)  
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
D
MTP Aux Loop Around Test (#229)  
Read All Memory Test (#85)(b)  
Memory Error Detection Test (#87)(b)  
Text Checksum Test (#86)(b)  
X
X
Memory Functional Test (#332) (b)  
Memory Board Check Test (#631) (b)  
ND  
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Refer to PROCR for a description of these tests.  
b. Refer to MEMORY [386 systems only] for a description of these tests.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                               
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-944  
MTP Reset Test (#101)  
This test is destructive. The test resets the Maintenance/Tape Processor. The  
destructive nature of this test causes the following:  
■
■
■
Administration terminal to log off  
CDR port to terminate data transmission  
Any current tape access to terminate and also to tear down any remote  
access INADS connection  
Table 3-407. TEST #101 MTP Reset Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1029  
ABORT  
Refer to STBY-SPE Maintenance documentation for a description of these  
error codes.  
2014  
2015  
2016  
2017  
2018  
2020  
2022  
2024  
2025  
2051  
10102  
10104  
ABORT  
ABORT  
System software resources required for this test are not available.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The MTP did not respond to being reset.  
10105  
10106  
FAIL  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, replace the Processor circuit pack.  
The Maintenance/Tape Processor was reset, but it responded with a NOT  
PASS status, indicating that it did not pass initialization correctly. The MTP  
is not functioning correctly. The system should continue to function, but it  
will not have the ability to save translation to tape, or to read tape if the  
system needs to be rebooted. Environmental monitoring is lost, as is  
communication with the Standby Processor.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If test continues to fail, replace the Processor circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-945  
Table 3-407. TEST #101 MTP Reset Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The Maintenance/Tape Processor was reset, and it passed initialization  
correctly. The other MTP tests should be examined to verify that the MTP is  
functioning correctly.  
1. Enter test processor a/b and verify that the MTP is functioning  
correctly.  
MTP Outpulse Relay Test (#102)  
This test is a nondestructive test. The test validates the correct operation of the  
remote access CO trunk used by INADS. The MTP first goes off-hook, then  
on-hook on this trunk. If the loop current is detected, the test passes. This test is  
not allowed if the remote access line is in use.  
Table 3-408. TEST #102 MTP Outpulse Relay Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1029  
2014  
2015  
2016  
2017  
2018  
2020  
2022  
2024  
2025  
2051  
ABORT  
Refer to STBY-SPE Maintenance documentation for a description of these  
error codes.  
1018  
ABORT  
The test has been disabled via administration.  
1. To enable the test, issue the change system-parameters maintenance  
command, and set the test remote access port field to "y." (If you have  
an INADS line, set the field to "y." If you are testing the Standby  
PR-MAINT, a refresh spe-standby command must be successfully  
executed before you proceed to Step 2.  
2. Rerun the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-946  
Table 3-408. TEST #102 MTP Outpulse Relay Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1131  
ABORT  
INADS port is busy because the system is reporting alarms to INADS, or  
because INADS is dialed into the system.  
1. Wait about ten minutes and then re-enter the command.  
System software resources required to run this test are not available.  
Internal system error  
10201  
10202  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
MTP did not respond to the test request.  
10203  
ABORT  
1. Repeat the test at 1-minute intervals a maximum of 5 times.  
2. If all MTP tests are aborting, execute the test processor a/b long  
command in order to reset MTP and to examine the results of the MTP  
Reset Test (#101).  
3. Replace the Processor circuit pack.  
4. If only the MTP outpulse relay test is aborting, escalate the problem.  
MTP reported test failure. No loop current detected.  
10204  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, examine the INADS trunk for connectivity,  
and manually check for loop current.  
3. If there is no INADS trunk, this test should be disabled. To disable the  
test, issue the change system-parameters maintenance command,  
and change the Test Remote Access Port field to "n." If this test is failing  
on the Standby SPE, issue the refresh spe-standby command, and  
rerun the test.  
4. If the INADS trunk checks out okay, but the test still fails, check the  
backplane connector wiring.  
5. If the backplane wiring checks out okay, replace the Processor circuit  
pack at your earliest convenience.  
PASS  
MTP detected a loop current on the remote access port.  
1. If the system cannot call INADS, or INADS cannot contact the system,  
check with the local Central Office for problems with the INADS trunk,  
and verify that the INADS number is correct.  
10205  
ABORT  
Internal system error  
1. Retryt the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-947  
Table 3-408. TEST #102 MTP Outpulse Relay Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
10206  
ABORT  
System could not determine if the testing of the INADS port is administered.  
1. Enter the change system-parameters maintenance command. Verify  
that the "Test Remote Access Port?" field is set to "y."  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
10208  
ABORT  
The remote access port is busy. INADS is probably dialed into the switch.  
1. If INADS is dialed in, the INADStrunk is working. There is no need to run  
the test.  
MTP Analog Loop Around Test (#103)  
This test is a nondestructive test. The test does an on-board loop around by  
using the MTPINADS channel. Test data is sent through the on-board modem out  
toward the INADS trunk. The data is looped around before the actual trunk, and it  
comes back into the on-board modem. The data is then verified for integrity.  
NOTE:  
The test does not send any data onto the INADS trunk. However, in order to  
pass, the test does require the trunk to be present.  
Table 3-409. TEST #103 MTP Analog Loop Around Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1029  
ABORT  
(Refer to STBY-SPE Maintenance documentation for a description of these  
error codes.)  
2014  
2015  
2016  
2017  
2018  
2020  
2022  
2024  
2025  
2051  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-948  
Table 3-409. TEST #103 MTP Analog Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The test has been disabled via administration.  
1018  
ABORT  
1. To enable the test, issue the change system-parameters  
maintenance command, and set the Test Remote Access Port field to  
"y". If you are testing the Standby PR-MAINT, a refresh spe-standby  
command must be successfully executed before you can proceed to  
Step 2.  
2. Rerun the test.  
1131  
ABORT  
The INADS port is busy because the system is reporting alarms to INADS,  
or because INADS is dialed into the system.  
1. Wait about 10 minutes and then re-enter the command.  
System software resources required for this test are not available.  
Internal system error  
10301  
ABORT  
ABORT  
10302  
10309  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
MTP did not respond to the test request.  
10303  
10310  
ABORT  
1. Repeat test at 1-minute intervals a maximum of 5 times.  
2. If only the MTP Analog Loop Around Test is aborting, escalate the  
problem.  
3. If all MTP tests are aborting, execute the test processor a/b long  
command in order to reset MTP, and examine the results of the MTP  
Reset Test (#101).  
10305  
10306  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
System could not determine if the testing of the INADS port is  
administered.  
1. Enter change system-parameters maintenance command, and  
verify the entry for the Test Remote Access Port field.  
2. Retry the command at 1-minute intervals a maximum of 5 times.  
10308  
10311  
ABORT  
ABORT  
The remote access port is busy. INADS is probably dialed into the switch.  
1. Wait until INADS session is terminated and then re-enter the  
command.  
Test #102 MTP Outpulse Relay Test failed.  
1. Refer to Error Code 10204 of the MTP Outpulse Relay Test (#102) for  
directions.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-949  
Table 3-409. TEST #103 MTP Analog Loop Around Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
10304  
FAIL  
MTP reported test failure. The system is not able to reliably contact INADS  
with alarm data. The system continues to provide good service.  
1. If MTP Outpulse Relay Test (#102) is also failing, check for the  
presence of the INADS trunk, and resolve any INADS trunk problems.  
2. If Test #102 passes, the fault is on the Processor circuit pack. The  
circuit pack should be replaced at your convenience.  
PASS  
MTP detected correct data through the loop back connection.  
1. If the system cannot call INADS, or if INADS cannot contact the  
system, check with the local Central Office for problems with the  
INADS trunk, and verify that the INADS number is correct.  
MTP Dual Port Ram Test (#104)  
This test is destructive.  
The test terminates any PPN Manager I session, and it is a coordinated test of the  
MTP dual port ram (DPR). The DPR is a section of memory that is shared by the  
MTP and by the 80286/386 Processor circuit pack. Control messages and data  
are passed through the DPR. The test forces both sides to read and write the  
DPR simultaneously in alternate locations.  
The DPR test causes the PPN Manager I to log off before the test result is  
displayed. The test result is determined according to the terminal from which the  
test is run. If the test is run from the PPN Manager I terminal, system technician  
should log back in and examine the Error Log for an error against PR-MAINT, with  
Error Type 769, no Aux Data. This error entry indicates that the MTPDPR Test  
failed and that the Processor circuit pack should be replaced.  
!
WARNING:  
If the TN786B circuit pack must be replaced, and if there is a blank in the  
Expansion Memory circuit pack slot (that is, in the slot immediately to the  
right of the TN786B circuit pack), remove the blank before removing the  
circuit pack. Otherwise, the circuit pack and/or the two connectors that are  
used to connect the Expansion Memory circuit pack (if available) might  
become damaged.  
If the test is being run from a terminal other than the PPN Manager I (for example,  
EPN Manager I, remote access, and so forth), the test results are displayed on  
the screen.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-950  
NOTE:  
A dial-up (through the INADS port) does not display the results discussed  
in the previous paragraph. However, a dial-up through data channels does  
display these results.  
Table 3-410. TEST #104 MTP Dual Port Ram Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1029  
ABORT  
(Refer to STBY-SPE Maintenance documentation for a description of these  
error codes.)  
2014  
2015  
2016  
2017  
2018  
2020  
2022  
2024  
2025  
2051  
1000  
ABORT  
ABORT  
System software resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1030  
The component on which the test was to be run is on the Standby SPE. This  
test may be run on this component only when it resides on the Active SPE.  
1. For a recommended maintenance procedure, refer to ABORT Error  
Code 1030 in STBY-SPE Maintenance documentation.  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
2028  
2029  
ABORT  
ABORT  
System software resources required for this test are not available.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
The dual port RAM is not functioning correctly. Communication between  
the processor and MTP is lost. The system is not able to report  
environmental alarms, communicate with the Standby SPE, or reboot from  
tape, if necessary.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, replace the Processor circuit pack.  
PASS  
Dual port RAM is functioning. Communication exists between the  
80286/386 Processor circuit pack and the MTP.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-951  
MTP Sanity Handshake Test (#106)  
This test is a nondestructive test. The MTP Sanity Handshake Test is simply a  
query from a maintenance process to the MTP. The MTP must reply for the test to  
pass.  
Table 3-411. TEST #106 MTP Sanity Handshake Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1029  
ABORT  
Refer to STBY-SPE Maintenance documentation for a description of these  
error codes.  
2014  
2015  
2016  
2017  
2018  
2020  
2022  
2024  
2025  
2051  
1000  
2033  
ABORT  
ABORT  
System software resources required to run this test are not available.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The MTP did not respond to the Sanity Handshake Query.  
1. Re-enter command with the "long" option.  
FAIL  
2. If the test continues to fail, replace the Processor circuit pack.  
The MTP responded to the Sanity Handshake Query.  
PASS  
MTP Manager I Loop Around Test (#228)  
This test is a nondestructive test. The test places the Manager I channel of the  
MTP into a loop around mode, and it verifies the data integrity of the channel.  
Although the test is nondestructive, it causes loss of keyboard input from the PPN  
Manager I.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-952  
Table 3-412. TEST #228 MTP Manager I Loop Around Test  
Error Test  
Code Result  
Description/Recommendation  
1029  
2014  
2015  
2016  
2017  
2018  
2020  
2022  
2024  
2025  
2051  
ABORT  
Refer to STBY-SPE Maintenance documentation for a description of these  
error codes.  
1000  
2000  
ABORT  
ABORT  
The system software resources required for this test are not available.  
Response to the test request was not received within the allowable time  
period.  
2033  
2034  
ABORT  
FAIL  
Internal system error  
Port busy  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The Manager I channel failed the Loop Back Test. The Manager I is  
probably unusable for administration or maintenance. The EPN  
Manager I, if available, or remote access can still be used.  
1. Repeat the command at one minute intervals a maximum of 5  
times.  
2. If the test continues to fail, replace the Processor circuit pack at  
your earliest convenience. Refer to Chapter 1 “Reliability  
Systems: A Maintenance Aid” for information on how to replace a  
circuit pack in the control carrier.  
!
WARNING:  
If the TN786B circuit pack must be replaced, and if there is a  
blank in the Expansion Memory circuit pack slot (that is, in the  
slot immediately to the right of the TN786B circuit pack),  
remove the blank before removing the circuit pack. Otherwise,  
the circuit pack and/or the two connectors that are used to  
connect the Expansion Memory circuit pack (if available) might  
become damaged.  
PASS  
The Manager I channel passed the Loop Back Test.  
1. If the PPN Manager I is not usable, check the Manager I itself,  
along with the cabling.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MAINT (Maintenance Processor)  
3-953  
MTP Auxiliary Loop Around Test (#229)  
This test is a nondestructive test. The test places the Auxiliary channel of the MTP  
into a loop around mode, and it verifies the data integrity of the channel. The  
Auxiliary channel is used as the CDR output port.  
Table 3-413. TEST #229 MTP Auxiliary Loop Around Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1029  
2014  
2015  
2016  
2017  
2018  
2020  
2022  
2024  
2025  
2051  
ABORT  
Refer to STBY-SPE Maintenance documentation for a description of these  
error codes.  
1000  
ABORT  
The system software resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1018  
2000  
ABORT  
ABORT  
ABORT  
The test has been disabled via administration. The change  
system-parameters cdr command needs to administer CDR.  
Response to the test request was not received within the allowable time  
period.  
2033  
2034  
Internal system error  
Port busy  
Retry the command at 1-minute intervals a maximum of 5 times.  
The system software resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
22902  
22903  
ABORT  
FAIL  
The Auxiliary channel failed the Loop Back Test. The AUX port is probably not  
sending any auxiliary data to the auxiliary collection device.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If test continues to fail, replace the Processor circuit pack.  
PASS  
The Auxiliary channel passed the Loop Back Test. The auxiliary port is  
functioning correctly.  
1. If no auxiliary data is being recorded, check the auxiliary collection  
device, and verify that it has been set up and connected correctly.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MEM (RISC Memory)  
3-954  
PR-MEM (RISC Memory)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test memory a lo c  
Full Name of MO  
RISC Memory  
1
PR-MEM  
MAJOR  
MINOR  
1
PR-MEM  
test memory a sh c  
RISC Memory  
1. The MO is ‘‘PR-MEM’’ because all of the Memory used by the Processor is on the  
TN798 Processor circuit pack.  
The RISC Memory contains the DEFINITY software and firmware. The Processor  
circuit pack is the most critical component in the system.  
For testing purposes, the circuit pack is logically separated into PR-MAINT,  
PROCR, and PR-MEM. This means that a memory problem requires that the  
Processor be replaced. These systems contain two types of memory: Flash ROM  
and DRAM. Flash ROM is memory that contains the boot image, part of the  
low-level maintenance firmware, and PI firmware. This type of memory is not  
erased during circuit pack resets. It can be reprogrammed via the upgrade  
software command or a Reset System 4/5 using a software memory card.  
One section of the Flash ROM (BOOTPROM) containing the system initialization  
functions and the low-level diagnostic programs is programmed at the factory  
and is not reprogrammed by the upgrade software command. DRAM is used for  
software data storage, and it changes constantly. Both types of memory are  
present on the Processor circuit pack. The diagnostics run appropriate tests on  
both memories.  
For all system activity, the Processor must be able to access the Memory. If the  
Processor cannot do this, the system goes into SPE-down mode. In SPE-down  
mode, fatal Memory errors may show up as Processor errors. This merely  
indicates that the Processor and the Memory are very closely linked as a matter  
of course.  
If the initialization diagnostics fail, refer to the ‘‘Procedure for SPE-Down Mode’’  
section in Chapter 1, ‘‘Maintenance for csi systems’’.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MEM (RISC Memory)  
3-955  
Error Log Entries and Test to Clear Values  
Table 3-414. Memory Error Log Entries  
Error  
Alarm  
Level  
On/Off  
Board  
Type  
Aux Data  
Associated Test  
Test to Clear Value  
1
0
1
0
Any  
Any  
Any  
ON  
test memory a l r 1  
test memory a l r 5  
Any  
Any  
Any  
Any  
Flash Memory  
Checksum Test (#86)  
MAJOR  
MAJOR  
MINOR  
MAJOR  
3(a)  
Flash Memory  
Checksum Test (#86)  
ON  
ON  
ON  
test memory a l r 5  
test memory a r 3  
test memory a l r 2  
1025  
1281  
Memory Parity Error  
Detection Test (#87)  
Memory Burst Read  
Test (#908)  
1793  
Any (b)(c)  
Any (b)(c)  
Read All Memory (#85)  
MAJOR  
MAJOR  
ON  
ON  
test memory a l r 1  
test memory a l r 1  
2049(d)  
Memory Functional  
Test (#332)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. This error (3) indicates that a software patch has been applied and either  
the software patch is bad or was installed incorrectly.  
1. Back out the software patch and run the test memory a long  
command to verify that the problem has been cleared.  
b. The Aux Data indicate SIMM Failures.  
c. Aux Data of 100 is an LMM Flash Checksum initialization failure.  
d. There are Functional Memory Test errors against the Processor circuit  
pack. This test is run only via a reset system 4 command or a reset  
system 5 command.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate errors in the order in which they are presented in the table that  
follows when you are inspecting errors in the system. By clearing error codes  
associated with the Read All Memory Test, for example, you may also clear errors  
generated from other tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MEM (RISC Memory)  
3-956  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
D
Processor Cache Test (#895)(a)  
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Processor Cache Audit (#896)(a)  
X
X
X
X
X
Processor Bus Time-out Exception Test (#82)(a)  
Processor BOOTPROM Checksum Test (#897)(a)  
Processor Write Buffer Test (#900)(a)  
Memory Burst Read Test (#908)  
Read All Memory Test (#85)  
Memory Parity Error Detection Test (#87)  
Flash Memory Checksum Test (#86)  
Memory Functional Test (#332) (b)  
MTP Outpulse Relay Test (#102) (c)  
MTP External Modem Present Test (#230) (c)  
MTP Analog Loop Around Test (#103) (c)  
MTP Sanity Handshake Test (#106) (c)  
MTP SAT Loop Around Test (#228) (c)  
MTP Aux Loop Around Test (#229) (c)  
MTP Reset Test (#101) (c)  
X
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
ND  
D
MTP Dual Port Ram Test (#104) (c)  
D
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Refer to ‘‘PROCR (RISC Processor Circuit Pack TN798)’’ for a description  
of these tests.  
b. This test is run only via a reset system 4 command or a reset system 5  
command.  
c. Refer to ‘‘PR-MAINT (Maintenance Processor)’’ for a description of these  
tests.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MEM (RISC Memory)  
3-957  
Read All Memory Test (#85)  
This test is a nondestructive test. The test reads every memory location in  
memory. A failure of this test indicates a DRAM failure in the Processor  
circuit pack. DRAM is replaceable and installed in 3 Single Inline Memory  
Module (SIMM) sockets on this circuit pack.  
Table 3-415. TEST #85 Read All Memory Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The requested test did not complete within the allowable time period.  
1. Retry the command.  
100  
ABORT  
2500  
1 - 7  
ABORT  
FAIL  
Internal system error  
1. Retry the command.  
If the system can still provide service, this indicates that the Processor  
circuit pack has a problem with memory or the RISC processor, but can still  
function.  
At the customers convenience run the destructive “reset system 4”  
command to boot the system and write to all of the memory locations. This  
will clear transient parity errors and test for permanent parity errors. This  
complete memory testing during initialization will cause “SPE DOWN” if a  
parity error is detected and the PROCR circuit pack should be replaced.  
If parity errors reoccur within several weeks, record the error code  
information indicating which memory modules failed, together with the  
extended interval between failures. After recording the information and at  
the customers convenience replace the PROCR circuit pack.  
PASS  
The Memory is healthy.  
Flash Memory Checksum Test (#86)  
This test is a nondestructive test. The test computes the checksum of the  
DEFINITY Generic 3 software and firmware loaded from the Software Memory  
Card (SOFTWARE MEM-CARD). A failure of this test indicates corruption of the  
Flash Memory. However, this failure does NOT always indicate a hardware  
problem. DO NOT REPLACE the Processor circuit pack when this is the only  
error. A system restart via the reset system 4 command starting with inserting  
the Software Memory Card for this system followed by re-inserting the Translation  
Memory Card memory card should be implemented at the customer’s earliest  
convenience.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MEM (RISC Memory)  
3-958  
Table 3-416. TEST #86 Text Checksum Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The test did not complete within the allowable time period.  
1. Retry the command.  
100  
ABORT  
ABORT  
FAIL  
2500  
1 - 7  
Internal system error  
1. Retry the command.  
The system may or may not continue to operate correctly. The system may  
fail later when some action requires access to the corrupted area of the  
Text.  
1. The Flash ROM should be reprogrammed via the upgrade software  
command. The memory card should contain the same vintage  
software that is currently in the system.  
2. If the test continues to fail, replace the Processor circuit pack and  
repeat step 1.  
PASS  
The checksum is correct.  
Memory Parity Error Detection Test (#87)  
This test is a nondestructive test. The test is run on a few reserved locations in  
memory. A failure of this test indicates a failure on the Processor circuit pack.  
This test determines if the parity circuitry is working. Accordingly, the test  
determines if parity errors can be detected. The parity circuitry is used to detect  
DRAM memory failures.  
Table 3-417. TEST #87 Memory Parity Error Detection Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The test did not complete within the allowable time period.  
1. Retry the command.  
100  
ABORT  
ABORT  
2500  
Internal system error  
1. Retry the command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MEM (RISC Memory)  
3-959  
Table 3-417. TEST #87 Memory Parity Error Detection Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1 - 7  
FAIL  
The parity detection circuitry is not working correctly. If the system can still  
provide service, this indicates that the Processor circuit pack has a problem  
but can still function.  
1. The Processor circuit pack should be replaced. The failure is identifying  
the PROCR as being bad and only the PROCR circuit pack needs to be  
replaced.  
PASS  
The parity detection circuitry is working.  
Memory Functional Test (#332)  
This test is destructive.  
This test ensures that every DRAM memory location can be accessed and  
changed independently. Running this test wipes out all data in DRAM memory.  
This test is performed during a reset system 4 or reset system 5. If the test fails  
during a reset system command, refer to the ‘‘Procedure for SPE-Down Mode’’  
in Chapter 1, ‘‘Maintenance for csi systems’’ for the recommended maintenance  
strategy.  
Table 3-418. TEST #332 Memory Functional Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The test did not complete within the allowable time period.  
1. Retry the command.  
100  
ABORT  
ABORT  
PASS  
1000  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 3 times.  
The DRAM is healthy.  
Memory Burst Read Test (#908)  
This test verifies that the Memory Burst Read function works properly on the  
Processor circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PR-MEM (RISC Memory)  
3-960  
Table 3-419. TEST #908 Memory Burst Read Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The test did not complete within the allowable time period.  
1. Retry the command.  
100  
ABORT  
ABORT  
1022  
1335  
2500  
Internal system error  
1. Retry the command.  
1 - 7  
FAIL  
The Burst Read circuit is not functioning properly.  
1. If the test fails, replace the Processor and retry the test.  
PASS  
The Burst Read portion of the Processor circuit pack is operating correctly.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PRI-CDR/SEC-CDR (PRI-CDR Link)  
3-961  
PRI-CDR/SEC-CDR (PRI-CDR Link)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test cdr-link primary/secondary l CDR Link  
test cdr-link primary/secondary CDR Link  
Full Name of MO  
PRI-CDR/SEC-CDR  
PRI-CDR/SEC-CDR  
MINOR  
WARNING  
The CDR feature records detailed call information on all incoming and outgoing  
calls on specified trunk groups and sends this information to an CDR output  
device. The two physical links can be administered for connecting external CDR  
output devices to the system. They are identified as the primary CDR (PRI-CDR)  
link and the secondary CDR (SEC-CDR) link. The CDR link can be administered  
to a data extension or the EIA port on the TN798 Processor circuit pack that  
provides a standard EIA-232C interface. The external CDR output devices are:  
■
■
■
■
■
■
■
■
94A Local Storage Unit (LSU)  
TELESEER CDR Unit  
Call Accounting System (CAS)  
Call Detail Recording Unit (CDRU)  
Printer  
Host computer  
Personal computer (PC)  
Customer-provided equipment  
Refer to DEFINITY Enterprise Communications Server Administrator’s Guide for  
details of the CDR feature.  
CDR Link Maintenance provides a strategy for maintaining the link between the  
system and an external CDR output device. The strategy includes a set of tests  
for periodic diagnosis, detection of errors during normal operation, actions for  
troubleshooting, and raising alarms for serious problems. CDR Link Maintenance  
uses a try-and-wait mechanism for maintaining the CDR link. If the CDR link is  
torn down due to an error, CDR Link Maintenance intends to bring the CDR link  
up. If the Link Setup trial fails, CDR Link Maintenance waits 30 seconds before  
the next retry. If the number of retries reaches the value of a threshold (two), a  
Minor alarm is raised for service attention.  
The following physical configurations are supported for the CDR link:  
■
From the EIA port of Processor circuit pack to an CDR output device  
through the standard EIA-232C interface.  
■
From a data channel on the TN798 Processor circuit pack to a data  
extension where the CDR output device connects via the standard EIA  
232C interface.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PRI-CDR/SEC-CDR (PRI-CDR Link)  
3-962  
The data extension can be a PDM, MPDM, DTDM, or ADU. The PDM,  
MPDM, and DTDM connect to a Digital Line Port of TN754 or TN754B  
Digital Line circuit pack; ADU connects to a Data Line Port of TN726 Data  
Link circuit pack.  
NOTE:  
In duplicated systems it is possible for a failure on one of the  
processor circuit packs to bring down the CDR link even if it is the  
standby processor. This problem can not be resolved by  
interchanging processors because the CDR ports on each of the  
processor circuit packs are connected via WIRE-OR.  
CDR Link Maintenance does not cover the maintenance of the elements  
composing the CDR physical link, which are as follows:  
■
■
■
External CDR output device  
EIA port on Processor circuit pack  
Data Module (PDM/MPDM/DTDM) and Digital Line Port of TN754 or  
TN754B Digital Line circuit pack  
■
■
ADU and Data Line Port of TN726 Data Link circuit pack  
Data Channels on the TN798 Processor circuit pack  
If CDR Link Maintenance cannot restore the CDR link, then the maintenance tests  
of these individual components of the CDR link must be executed to diagnose  
faults.  
Procedures for Restoring the CDR Link  
1. Get the status of CDR links.  
Enter status cdr-link command and make sure that the CDR links are not  
busied out for maintenance. If the link is down, then continue to the next  
step.  
2. Where does the CDR link connect to?  
Enter display system feature and find out the destinations of CDR links.  
Continue to the next step.  
3. Is the destination an extension or the EIA port?  
If the destination is an extension number, then enter the status data  
extension command and verify whether the data extension is in the  
in-service/idle state. If the data extension is NOT available, then look for  
the extension number in the Alt Namefield of Hardware Error Log and  
refer to ‘‘XXX-BD (Common Port Circuit Pack)’’ Maintenance  
documentation for resolutions.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PRI-CDR/SEC-CDR (PRI-CDR Link)  
3-963  
If the destination is "eia," then look for PR-MAINT errors in the Hardware  
Error Log. If present, refer to ‘‘PR-MAINT (Maintenance Processor)’’  
Maintenance documentation.  
4. Is a data channel on the TN798 Processor circuit pack in the  
in-service/idle state?  
Enter list data command and find out the extension numbers of data  
channels. Enter status data extension command and make sure that at  
least one data channel is in the in-service/idle state. If no data channel is  
available, then look for DATA-CHL/DATA-CON/DATA-BD errors in the  
Hardware Error Log. If present, refer to ‘‘DATA-BD (Data Channel  
Processor Circuit Pack)’’.  
5. Is the external CDR output device available?  
Make sure that the CDR output device is on-line and ready for service.  
Check the physical connectivity between Data Module and the CDR  
output device or between the EIA port on backplane of the switch and the  
CDR output device.  
It is recommended to busy out the CDR link before executing maintenance tests  
over the CDR link. If the CDR link is busied out, then all CDR link maintenance  
actions are deactivated. The interference to tests of other MO is off.  
Error Log Entries and Test to Clear Values  
Table 3-420. CDR Link Maintenance Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
1
Associated Test  
Test to Clear Value  
2
0
0
Any  
Any  
Any  
test cdr-link  
primary|secondary sh  
18 (a)  
25 (b)  
0
busy out cdr  
WARNI  
NG  
OFF  
release cdr-link  
primary|secondary  
primary | secondary  
0
Link Retry Test (#215)  
MINOR/ OFF  
WARNI  
test cdr-link  
primary|secondary l  
3 to 6  
9
3
NG  
99  
255  
513 (c)  
0
test cdr-link  
3 to 6  
9
primary|secondary  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PRI-CDR/SEC-CDR (PRI-CDR Link)  
3-964  
Table 3-420. CDR Link Maintenance Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
1
Associated Test  
Test to Clear Value  
1025 (d)  
1281 (e)  
1. The MTP Reset Test (#101) logs you off. The MTP Dual Port Ram Test (#104) can also log you off.  
Manually repeat the command with the ‘‘long’’ option for the designated number of times when  
testing from the PPN SAT.  
2. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
3. Minor alarms on this MO may be downgraded to Warning alarms based on the value used in the  
set options command.  
Notes:  
a. System Technician has busied out the CDR link to out-of-service state. The  
CDR link is torn down.  
b. Link Retry Test (#215) fails. The Aux Data field contains either the Channel  
ID of Data Channels on the TN798 Processor circuit pack (that is, 3 for  
Channel 01, 4 for Channel 02, 5 for Channel 03, 6 for Channel 04, and 9  
for EIA port) or an Error Code of 99 indicating that no data channels are  
available for setting up the link, or an Error Type of 255 indicating an  
internal system error. Refer to the preceding ‘‘Procedures for Restoring the  
CDR Link’’ for resolution.  
c. The CDR physical link is down due to the following causes: cable to the  
CDR output device is disconnected; CDR output device is powered off,  
the data extension where the CDR output device connects to has been  
busied out or there is a scheduled daily interchange. The Aux Data field  
contains the Channel ID of Data Channels on the TN798 Processor circuit  
pack (that is, 3 for Channel 01, 4 for Channel 02, 5 for Channel 03, 6 for  
Channel 04, and 9 for EIA port). Check the connectivity of wire and cable  
among wall jacket, data module, and the CDR output device. Enter status  
data extension and verify that the data extension of the CDR output  
device is in the in-service/idle state. If the data extension is not available,  
then refer to the preceding ‘‘Procedures for Restoring the CDR Link’’ for  
resolution. Issue the display system-parameters-maintenance  
command to see the start time of daily maintenance. If the error occurs  
and is resolved during the interval of daily maintenance, then the error can  
be ignored.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PRI-CDR/SEC-CDR (PRI-CDR Link)  
3-965  
d. This error indicates that the CDR output device is in an off-line state, for  
example, paper jam or paper out for a printer device. The CDR link is torn  
down. Check the CDR output device and act promptly to put it back to  
on-line state. Enter test cdr-link primary|secondary command to set up  
the CDR link.  
e. Software detects an overflow of CDR records generated in the switch due  
to the heavy trunk traffic and low speed CDR output device. If both  
primary and secondary links are ON, the secondary link is torn down  
temporarily for two minutes to speed up the output process to the primary  
link. No action is necessary for this error type.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the Link  
Retry Test, for example, you may also clear errors generated from other tests in  
the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Link Tear Down Test (#213)  
Link Retry Test (#215)  
D/ND  
D
X
X
X
ND  
1. D = Destructive; ND = Nondestructive  
Link Tear Down Test (#213)  
This test is destructive.  
This test disconnects the existing link between the system and the external CDR  
output device. If the link has been disconnected already, this test just returns  
PASS. All resources allocated for an CDR link are released after this test.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PRI-CDR/SEC-CDR (PRI-CDR Link)  
3-966  
Table 3-421. TEST #213 Link Tear Down Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
40  
50  
ABORT Internal system error  
ABORT Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT The CDR link has been busied out to out-of-service.  
1010  
1. Enter the release cdr-link primary|secondary command to release the  
CDR link from busyout state.  
2. Retry the test cdr-link primary|secondary long command to execute the  
test.  
FAIL  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The CDR link is torn down.  
PASS  
Link Retry Test (#215)  
This test sends a message to the CDR software process to make a data call to  
the extension where the CDR output device connects to or opens the EIA port to  
the CDR output device. If the CDR link is already up, this test is passed without  
making any data call or opening the EIA port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PRI-CDR/SEC-CDR (PRI-CDR Link)  
3-967  
Table 3-422. TEST #215 Link Retry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
10  
ABORT Internal system error  
20  
ABORT Internal system error. Internal error in Maintenance Action Process (MAP). MAP  
returns an error back to maintenance script (HMM). Timer expires while waiting  
for the reply from MAP.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT Internal system error  
30  
1. Refer to ‘‘Procedures for Restoring the CDR Link’’.  
ABORT The CDR link has been busied out to out-of-service.  
1010  
1. Enter release cdr-link primary|secondary command to release the CDR  
link from busyout state.  
2. Retry test cdr-link primary|secondary long command to execute the  
test.  
FAIL  
The CDR link CANNOT be established.  
1. Refer to the ‘‘Procedures for Restoring the CDR Link’’ for instructions.  
The CDR link is up.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PROCR (RISC Processor Circuit Pack TN798)  
3-968  
PROCR (RISC Processor Circuit Pack  
TN798)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test processor a lo r/c  
test processor a sh r/c  
Full Name of MO  
RISC Processor Circuit Pack  
RISC Processor Circuit Pack  
PROCR  
PROCR  
MAJOR  
MINOR  
NOTE:  
Alarms on the PR-MEM, PROCR and PR-MAINT maintenance objects  
(MOs) are indicated by the red LED on the Processor circuit pack.  
The TN798 has a RISC processor (PROCR) that uses on-board Flash ROM and  
DRAM memory (PR-MEM). This circuit pack also contains the Maintenance  
Processor (PR-MAINT) and IO-PROCR, which includes the I/O Processor CPU,  
memory, a real-time operating system, and a driver.  
The RISC Processor circuit pack portion is responsible for the execution of the  
DEFINITY Generic 3 software package. This includes all of the call processing,  
maintenance, and administration functions. The RISC Processor circuit pack is  
the most critical component to the operation of the system.  
The PR-MAINT (Maintenance Processor for RISC systems) is responsible for  
monitoring the sanity of the RISC Processor circuit pack and the environmental  
conditions. The PR-MAINT provides the serial interfaces for the SAT and for the  
Digital Communications Equipment (DCE) ports. The PR-MAINT also provides  
the communications interface to INADS for alarm reporting and remote  
maintenance capability. The I/O Processor elements support the Data Channel  
data scanners and Packet Interface functions. (The I/O Processor resides on the  
TN798 Processor circuit pack.)  
Error Log Entries and Test to Clear Values  
Table 3-423. RISC Processor Circuit Pack Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
1
Associated Test  
Any  
Test to Clear Value  
test processor a r 1  
test processor a r 5  
2
0
0
Any  
Any  
1(a)  
513  
Any  
BOOTPROM  
Checksum Test (#80)  
MAJOR  
ON  
Processor Write Buffer  
Test (#900)  
MAJOR  
ON  
test processor a r 1  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PROCR (RISC Processor Circuit Pack TN798)  
3-969  
Table 3-423. RISC Processor Circuit Pack Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
1
Associated Test  
Test to Clear Value  
1025(b)  
Any  
Any  
Processor Cache Audit  
(#896)  
MINOR  
ON  
test processor a r 2  
1281  
Processor Cache  
Test(#895)  
MAJOR  
MAJOR  
ON  
ON  
test processor a r 1  
test processor a r 2  
1793(c)  
Processor Bus  
Time-out Exception  
Test (#82)  
2049(d)(e Any  
)
Processor Sanity Timer  
Test  
MINOR  
ON  
test processor a l c  
1. The MTP Reset Test (#101) logs you off. The MTP Dual Port Ram Test (#104) can also log you off.  
2. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. The BOOTPROM Checksum Test (#80) failed. Refer to the FAIL condition  
of this test for further action.  
b. A parity error was detected in the processor’s data cache or instruction  
cache. Aux Data indicates the difference in the number of parity errors  
since the last report.  
c. The Processor Bus Time-out Test (#82) failed. Refer to the FAIL condition  
of this test for further action.  
d. Aux Data of 100 is an LMM initialization failure.  
e. The Processor Sanity Timer Test failed during a reset level 4 or 5  
initialization. reset system 4 at the customers convenience and if the alarm  
occurs again, replace the Processor circuit pack. The system runs with  
this failure, but it is not protected if the system software has a sanity  
problem. The test processor a long clear command clears this alarm, but  
the sanity timer is only tested during initialization so the alarm occurs  
again and the system is not protected against insane software.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PROCR (RISC Processor Circuit Pack TN798)  
3-970  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the Processor Bus Time-out Exception Test, for  
example, you may also clear errors generated from other tests in the testing  
sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Processor Cache Test (#895)  
D/ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
D
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Processor Cache Audit (#896)  
X
X
X
X
X
Processor Bus Time-out Exception Test (#82)  
Processor BOOTPROM Checksum Test (#80)  
Processor Write Buffer Test (#900)  
Memory Burst Read Test (#908)(a)  
Read All Memory Test (#85)(a)  
Memory Parity Error Detection Test (#87)(a)  
Flash Memory Checksum Test (#86)(a)  
Memory Functional Test (#332) (a) (b)  
MTP Outpulse Relay Test (#102) (c)  
MTP External Modem Present Test (#230) (c)  
MTP Analog Loop Around Test (#103) (c)  
MTP Sanity Handshake Test (#106) (c)  
MTP SAT Loop Around Test (#228) (c)  
MTP Aux Loop Around Test (#229) (c)  
MTP Reset Test (#101) (c)  
X
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
ND  
D
MTP Dual Port Ram Test (#104) (c)  
D
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Refer to ‘‘PR-MEM (RISC Memory)’’ for a description of these tests.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PROCR (RISC Processor Circuit Pack TN798)  
3-971  
b. There are Functional Memory Test errors against the Processor circuit  
pack. This test is run only via a reset system 4 command or a reset system  
5 command.  
c. Refer to ‘‘PR-MAINT (Maintenance Processor)’’ for a description of these  
tests.  
Processor BOOTPROM Checksum Test (#80)  
This test is a nondestructive test. This test computes the checksum of the  
Processor’s bootstrap BOOTPROM. A failure indicates the BOOTPROM is  
corrupt.  
Table 3-424. Test #80 Processor BOOTPROM Checksum Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The test did not complete within the allowable time period.  
1. Retry the command.  
100  
ABORT  
ABORT  
FAIL  
2500  
Internal system error  
1. Retry the command.  
The computed checksum did not match the BOOTPROM checksum. The  
system may not continue to operate correctly. The system may fail at some  
future date when the corrupted area the bootstrap BOOTPROM is  
accessed.  
1. Replace the Processor circuit pack.  
PASS  
The computed checksum matched the BOOTPROM checksum. This part  
of the Processor will continue to operate normally.  
Processor Bus Time-out Exception Test (#82)  
This test is a nondestructive test. The test is used to verify that the RISC  
Processor can intentionally cause a Bus Timeout Exception (BTE) and then  
verifies if it vectors to the correct interrupt routine. This is basically a test of the  
internal operation of the RISC Processor chip and the bus time-out circuitry.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PROCR (RISC Processor Circuit Pack TN798)  
3-972  
Table 3-425. Test #82 Processor Bus Time-out Exception Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The test did not complete within the allowable time period.  
Internal system error  
100  
ABORT  
ABORT  
2500  
1. Retry the command.  
FAIL  
The interrupt was not detected or acted upon.  
1. Repeat the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, the Processor circuit pack should be  
replaced. The replacement must have enough memory for this system.  
PASS  
The interrupt was correctly detected. The RISC Processor is functioning  
correctly.  
Processor Cache Test (#895)  
This test is a nondestructive test. This test overwrites the contents in the  
Instruction and Data Caches, requiring them to be refilled during normal  
execution.  
This test verifies that the Processor Instruction and Data Caches are functional.  
Some errors in the caches will simply reduce performance by forcing instructions  
or data to be read from memory more often than would normally be necessary. In  
any case, cache problems are serious and the Processor circuit pack must be  
replaced as soon as possible if they are detected.  
Table 3-426. Test #895 Processor Cache Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The test did not complete within the allowable time period.  
1. Retry the command.  
100  
ABORT  
ABORT  
FAIL  
2500  
Internal system error  
1. Retry the command.  
The Processor cache is not functioning correctly.  
1. Replace the Processor circuit pack immediately.  
The cache portion of the Processor circuit pack is operating correctly.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PROCR (RISC Processor Circuit Pack TN798)  
3-973  
Processor Cache Audit (#896)  
This nondestructive audit checks the state of the Cache Parity bit maintained by  
the RISC CPU. If this bit is set, there may be problems with either the CPU, the  
Instruction, or Data Cache. An indication of bad cache parity won’t itself mean  
that the system won’t operate, but minor to severe performance degradation may  
be present. For example, a single bad bit in either cache could cause this bit to  
be set. If the faulty word is seldom accessed, the impact will be small. If the bit is  
accessed frequently, there could be serious problems with much, or all, of the  
cache (stuck data bit) with the only direct indication again being the cache parity  
error or cache test error.  
Table 3-427. Test #896 Processor Cache Audit  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The test did not complete within the allowable time period.  
1. Retry the command.  
100  
ABORT  
ABORT  
FAIL  
2500  
Internal system error  
1. Retry the command.  
The Cache Parity Error bit is set, there may be problems with either the  
CPU or the Instruction or Data Cache.  
1. Retry the command.  
2. If the test continues to fail, run test processor a|b long.  
3. If the Processor Cache test (#895) or the Processor Cache Audit  
(#896) fails, replace the Processor circuit pack.  
PASS  
The Processor has not detected any parity errors in the Instruction and  
Data Caches since the last time this audit was run.  
Processor Write Buffer Test (#900)  
This test is a nondestructive test. This test verifies that the Write Buffer operates  
properly on the Processor circuit pack. Failure of this test is serious. The  
Processor circuit pack must be replaced as soon as possible.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PROCR (RISC Processor Circuit Pack TN798)  
3-974  
Table 3-428. Test #900 Processor Write Buffer Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The test did not complete within the allowable time period.  
1. Retry the command.  
100  
ABORT  
ABORT  
FAIL  
2500  
Internal system error  
1. Retry the command.  
The Processor Write Buffer is not operating correctly.  
1. Replace the Processor circuit pack immediately.  
PASS  
The Write Buffer portion of the Processor circuit pack is operating  
correctly.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
PROC-SAN (Process Sanity Audits)  
3-975  
PROC-SAN (Process Sanity Audits)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
PROC-SAN  
none  
none  
Process Sanity Audits  
The Process Sanity Audits MO is responsible for monitoring the sanity of software  
processes in the system. If the Process Sanity Audits MO detects that a process  
has gone insane (does not respond to a sanity message within an allotted time  
period), the process is restarted. If the Process Sanity Audits MO detects that  
multiple processes (or a single key process) do not respond to sanity messages  
within an allotted time period, a system recovery action is initiated.  
The Process Sanity Audits MO has no alarms and no tests. Certain errors are  
logged to the Hardware Error Log for information purposes only.  
Error Log Entries and Test to Clear Values  
Table 3-429. Process Sanity Audits Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
none  
none  
none  
10 (a)  
0
none  
none  
none  
none  
none  
none  
204 (a)  
any  
1. Look for other errors of the same type and deal with them accordingly.  
Notes:  
a. These errors indicate that a system recovery action has been taken  
because one or more software processes failed to respond to a sanity  
audit in a timely fashion. As a result of the recovery action, the system may  
have temporarily suspended service for a period of time surrounding the  
error.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
RING-GEN (Analog Ring Generator)  
3-976  
RING-GEN (Analog Ring Generator)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
Full Name of MO  
RING-GEN  
MAJOR  
test environment P  
Analog Ring Generator  
1. Where P is an appropriate port network number determined via the Port field from the  
Alarm or Error Log.  
All analog phones must be provided with a ringing voltage. The Analog Ring  
Generator is part of the 650A AC Power Supply. A ringing voltage generator  
failure means that no ringing can occur on analog phones; however, ringing on  
digital and hybrid phones can still occur. The ringing voltage is monitored by the  
Tone-Clock circuit pack.  
Hardware Error Log Entries and Test to Clear  
Values  
Analog Ring Generator Error Log Entries  
Error  
Type  
1
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
test environment PP  
test environment PP r 3  
0
0
Any  
Any  
Any  
1
Analog Ring Generator Query  
Test (#118)  
MAJOR ON  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following tables when  
inspecting errors in the system. By clearing error codes associated with the  
Analog Ring Generator Initialization Test, for example, you may also clear errors  
generated from other tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
RING-GEN (Analog Ring Generator)  
3-977  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Analog Ring Generator Initialization Test (#117)  
Analog Ring Generator Query Test (#118)  
Single-Carrier Power Query Test (#79)  
D/ND  
ND  
X
X
X
X
X
X
X
X
X
X
ND  
ND  
Emergency Transfer Query Test (#124) (a)  
External Alarm Lead Query Test (#120) (b)  
ND  
ND  
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Refer to EMG-XFER (Emergency Transfer) Maintenance documentation for  
a description of this test.  
b. Refer to EXT-DEV (External Alarm) Maintenance documentation for a  
description of this test.  
Analog Ring Generator Initialization Test (#117)  
This test reports an error to the system software if the ringing voltage falls to low  
(only if system software has made a request to the tone clock to monitor the  
voltage). The Analog Ring Generator Initialization Test sends a request to the  
active tone/clock.  
Table 3-430. TEST #117 Analog Ring Generator Initialization Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
ABORT  
The system software is unable to determine the active tone/clock circuit  
pack, unable to allocated the resources necessary to run the test, or unable  
to send a down link message.  
1000  
1001  
1003  
1115  
2012  
2100  
1. Wait for the green LED on the active tone/clock to go out; use the status  
port-network command to determine the active Tone/Clock circuit  
pack.  
2. Rerun the test. If the test aborts again, refer to TDM-CLK Maintenance  
documentation.  
2000  
ABORT  
Response to the request was not received within the allowable time period.  
1. Look for TDM-CLK errors and alarms. Resolve all other Tone/Clock  
problems first.  
2. Rerun the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
RING-GEN (Analog Ring Generator)  
3-978  
Table 3-430. TEST #117 Analog Ring Generator Initialization Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1005  
ABORT  
The tone/clock is unable to read the analog ringing voltage level when the  
tone/clock is in the Processor Interface slot. This test is not available for the  
Processor Port Network in this configuration.  
PASS  
The active Tone/Clock has successfully been enabled to monitor the ringing  
voltage level.  
Analog Ring Generator Query Test (#118)  
This test requests the Active Tone-Clock circuit pack to check the ringing  
voltage. The tone/clock circuit pack replies with PASS if the ringing voltage is  
adequate to ring the analog phones. If not, the active tone/clock circuit pack  
replies with a FAIL. The Analog Ring Generator Query Test then reports the result.  
Table 3-431. TEST #118 Analog Ring Generator Query Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
ABORT  
Could not seize the resources to run the test. Other maintenance is running  
on the active tone/clock circuit pack.  
1000  
1001  
1003  
1115  
2012  
2100  
1. Wait for the green LED on the active tone/clock circuit pack to go out;  
(use the status port-network command to determine the Active  
tone/clock circuit pack).  
2. Rerun the test. If the test aborts again, refer to TDM-CLK (TDM Bus  
Clock) Maintenance documentation.  
2000  
ABORT  
ABORT  
Response to the request was not received within the allowable time period.  
1. Look for TDM-CLK errors and alarms. Resolve all other tone/clock  
problems first.  
2. Rerun the test.  
1005  
The tone/clock is unable to read the analog ringing voltage level when the  
tone/clock is in the Processor Interface slot. This test is not available for the  
Processor Port Network in this configuration.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
RING-GEN (Analog Ring Generator)  
3-979  
Table 3-431. TEST #118 Analog Ring Generator Query Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
This failure indicates that there is no ringing voltage in the carrier where the  
active tone/clock circuit pack resides. Other carriers may or may not have  
ringing voltage.  
1. Unseat all analog circuit packs in the cabinet that contains the  
Tone/Clock circuit pack and rerun the test.  
2. If the test passes, then the Ring Generator is healthy and one of the  
analog circuit packs is defective. Replace the analog circuit packs one  
at a time, and rerun the test to determine which circuit pack is causing  
the problem. When the defective analog circuit pack is found, replace  
it. Rerun the test. If the test still fails, go to Step 4.  
3. Replace the 650A power unit, and rerun the test. If the test still fails, go  
to Step 4.  
4. The tone/clock may be faulty and incorrectly reporting the level of the  
ringing voltage. Replace the tone/clock and rerun the test. Refer to  
‘‘TONE-BD (Tone-Clock Circuit Pack)’’ Maintenance documentation for  
details on replacing the tone/clock circuit pack. Rerun the test.  
PASS  
Ringing voltage is acceptable in the cabinet containing the tone/clock  
circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-BD (Speech Synthesis Circuit Pack)  
3-980  
S-SYN-BD (Speech Synthesis Circuit  
Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board PCSS sh  
test board PCSS sh  
Full Name of MO  
S-SYN-BD  
S-SYN-BD  
MIN  
WRN  
Speech Synthesis Circuit Pack  
Speech Synthesis Circuit Pack  
1. Where P is the port network number (1); C is the carrier designation (for example, A, B, or C);  
and SS is the address of the slot in the carrier where the circuit pack is located (for example,  
01, 02, ..., etc.).  
Refer to XXX-BD (Common Port Circuit Pack) Maintenance documentation for  
circuit pack level errors. See also S-SYN-PT (Speech Synthesis Port)  
Maintenance documentation for related port information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-981  
S-SYN-PT (Speech Synthesis Port)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test port PCSSpp sh  
test port PCSSpp l  
Full Name of MO  
Speech Synthesis Port  
Speech Synthesis Port  
Speech Synthesis Port  
S-SYN-PT  
MAJOR  
MINOR  
S-SYN-PT  
S-SYN-PT  
WARNING  
test port PCSSpp sh  
1. Where P is the port network number (1); C is the carrier designation (for example, A, B, or  
C); and SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02, ..., etc.).  
The TN725 Speech Synthesis circuit pack provides four independent Speech  
Synthesis Ports which can be connected to any of the voice time slots on the  
TDM Bus. Each Speech Synthesis Port consists of a speech synthesizer device  
(SSD) and is managed by a custom-coded programmable speech synthesizer  
(PSS) controller. The PSS controller is, in turn, controlled by the on-board  
microprocessor via a command interface specifically designed for this  
application. The PSS controller’s main function is the orderly transfer of encoded  
speech from the speech vocabulary read-only memory (ROM) to the SSDs. The  
SSDs decode it and produce 64 kb/s 5-255 PCM (Pulse Code Modulation)  
speech. The encoded speech is stored in up to 512K bytes of on-board  
read-only memory (ROM). In addition, each Speech Synthesis Port has an  
associated dual-tone multifrequency (DTMF) receiver to receive touch-tone digits  
from a station set connected to the port via a voice time slot. The station set may  
be connected to the Speech Synthesis Port through either a line or trunk circuit.  
When there is an incoming call to a port, the "listen" network time slot is  
connected to the DTMF receiver input and the "talk" network time slot is  
connected to the SSD output. This enables the Speech Synthesis Port to support  
speech synthesis features or touch-tone input with voice response features.  
Some of the features that use the Speech Synthesis Port’s capabilities include  
Leave Word Calling, Automatic Circuit Assurance, Automatic Wakeup  
(hotel-motel), and do Not Disturb (hotel-motel).  
The Speech Synthesis circuit pack should not be confused with the  
Announcement circuit pack as different voice features are supported by each  
circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-982  
Hardware Error Log Entries and Test to Clear  
Values  
Speech Synthesis Port Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test port PCSSpp sh r 1  
1(a)  
18  
17672  
0
None  
busyout port PCSSpp  
None  
WARNING  
WARNING  
MAJOR  
OFF  
ON  
ON  
release port PCsspp  
test port PCSSpp sh  
test port PCSSpp sh r 2  
130(b)  
257  
Speech Synthesis  
PSS Handshake Test  
(#168)  
513  
769  
17922  
17664  
Speech Synthesis  
Memory Test (#166)  
MINOR  
MINOR  
ON  
ON  
test port PCSSpp sh r 2  
test port PCSSpp sh r 2  
Speech Synthesis  
DTMF Receiver  
Inquiry Test (#164)  
1025  
17670  
Speech Synthesis  
SSD Inquiry Test  
(#167)  
MINOR  
ON  
test port PCSSpp sh r 2  
1281  
1537  
1793  
Speech Synthesis  
DSP Tone Test (#165)  
MINOR  
MINOR  
MINOR  
ON  
ON  
ON  
test port PCSSpp sh r 2  
test port PCSSpp sh r 2  
test port PCSSpp l r 2  
Speech Synthesis  
Memory Test (#166)  
Speech Synthesis  
DTMF Receiver Test  
(#163)  
2049(c)  
2305  
Conference Circuit  
Test (#7)  
MINOR  
MINOR  
ON  
ON  
test port PCSSpp l r 2  
test port PCSSpp l r 2  
NPE Crosstalk Test  
(#6)  
3840(d)  
Any  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. An in-line failure of the on-board microprocessor/PSS handshake has  
occurred. Refer to Test #168 for repair procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-983  
b. This error type indicates that the circuit pack been removed or has been  
insane for more than 11 minutes. To clear the error, reinsert or replace the  
circuit pack.  
c. A transient error that does not cause an alarm can occasionally occur  
during a SPE, TDM BUS, or Tone Clock interchange. Test the port and  
follow the instructions for conference Test (#7).  
d. This error is not service-affecting and no action is required.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the NPE  
Crosstalk Test, for example, you may also clear errors generated from other tests  
in the testing sequence.  
For example, you may also clear errors generated from other tests in the testing  
sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Speech Synthesis PSS Handshake Test (#168)  
NPE Crosstalk Test (#6)  
D/ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
X
X
X
X
X
X
X
X
X
X
Conference Circuit Test (#7)  
Speech Synthesis DTMF Receiver Test (#163)  
Speech Synthesis Memory Test (#166)  
Speech Synthesis DSP Tone Test (#165)  
Speech Synthesis SSD Inquiry Test (#167)  
Speech Synthesis DTMF Receiver Inquiry Test (#164)  
Speech Synthesis Parameter Update Test (#169)  
X
X
X
X
X
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per-port basis. The NPECrosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may occur. This test is usually only part of a port’s Long Test Sequence and takes  
about 20 to 30 seconds to complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-984  
Table 3-432. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call and therefore unavailable for certain tests. You  
must wait until the port is idle (yellow LED if off) before retesting.  
1. If the port is idle, retry the command at 1-minute intervals a maximum  
of 5 times.  
1001  
1002  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS (TDM Bus) Maintenance  
documentation to diagnose any Active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
(TTR Level) Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
(Tone Generator) Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
1020  
ABORT  
ABORT  
The port was seized by a valid call during the test and the test has been  
aborted. You must wait until the port is idle (yellow LED if off) before  
retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test did not run due to an already existing error on the specific port or a  
more general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit  
pack and attempt to diagnose the already existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-985  
Table 3-432. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Any  
FAIL  
The NPE of the tested port was found to be transmitting in error. This  
causes noisy and unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated using other port tests and examining  
the Error Log.  
Conference Circuit Test (#7)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per-port basis. The Conference Circuit Test verifies that the NPE channel for the  
port being tested can correctly perform the conferencing function. The NPE is  
instructed to listen to several different tones and conference the tones together.  
The resulting signal is then measured by a Tone Detector port. If the level of the  
tone is within a certain range, the test passes.  
Table 3-433. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT System resources required to run this test are not available. The port may be  
busy with a valid call and therefore unavailable for certain tests. You must wait  
until the port is idle (yellow LED if off) before retesting.  
1. If the port is idle, retry the command at 1-minute intervals a maximum of 5  
times.  
1004  
1020  
ABORT The port was seized by a valid call during the test and the test has been aborted.  
You must wait until the port is idle (yellow LED if off) before retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT The test did not run due to an already existing error on the specific port or a more  
general circuit pack error.  
1. Examine Error Log for existing errors against this port or the circuit pack and  
attempt to diagnose the already existing error.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-986  
Table 3-433. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
2100  
ABORT Response to the test request was not received within the allowable time period.  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Any  
FAIL  
The NPE of the tested port did not conference the tones correctly. This causes  
noisy and unreliable connections.  
1. Retry the test.  
PASS  
The port can correctly conference multiple connections. User-reported troubles  
on this port should be investigated using other port tests and examining the Error  
Log.  
Speech Synthesis DTMF Receiver Test (#163)  
A series of DTMF tones are conferenced from the TDM Bus into the port’s DTMF  
receiver and checked to see if the correct tones have been detected during the  
correct intervals. If all the DTMF tones were detected correctly, the test passes. If  
any of the tones were not detected correctly, the test fails.  
Table 3-434. TEST #163 Speech Synthesis DTMF Receiver  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call and therefore unavailable for certain tests. You  
must wait until the port is idle (yellow LED if off) before retesting.  
1. If the port is idle, retry the command at 1-minute intervals a maximum  
of 5 times.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-987  
Table 3-434. TEST #163 Speech Synthesis DTMF Receiver — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Any  
FAIL  
DTMF tones were not detected. This type of failure may cause features  
using touch-tone input to the Speech Synthesis Port to malfunction.  
1. Verify that the Tone-Clock circuit pack is functioning correctly by  
checking the Error Log and using the test tone-clock long command.  
2. If the test fails again, replace the Speech Synthesis circuit pack.  
PASS  
The port has detected all DTMF tones correctly. User-reported troubles  
should be investigated using other tests and verifying other ports on this  
circuit pack are working correctly.  
Speech Synthesis DTMF Receiver Inquiry Test  
(#164)  
This test determines the sanity of the port’s DTMF receiver. The on-board  
microprocessor tests the port’s DTMF receiver and determines if it is in a sane  
(test passes) or insane (test fails) condition.  
Table 3-435. TEST #164 Speech Synthesis DTMF Receiver Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be busy with a valid call and therefore unavailable for certain tests. You  
must wait until the port is idle (yellow LED if off) before retesting.  
1. If the port is idle, retry the command at 1-minute intervals a maximum  
of 5 times.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-988  
Table 3-435. TEST #164 Speech Synthesis DTMF Receiver Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The DTMF receiver for this port is insane.  
1. If the test fails again, replace the circuit pack.  
Any  
FAIL  
PASS  
The DTMF receiver for this port is sane. User-reported troubles should be  
investigated using other tests and verifying other ports on this circuit pack  
are working correctly.  
Speech Synthesis DSP Tone Test (#165)  
The digital signal processor (DSP) associated with each port can generate a  
440-Hz tone whose presence can be detected by TN748 General Purpose Tone  
Detector circuit packs. A 440-Hz tone is generated for 500 msec on a specified  
time slot which is being listened to by the detector circuit. If the detector  
determines the tone is present on the time slot, the test passes; otherwise, it fails.  
Table 3-436. TEST #165 Speech Synthesis DSP Tone Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT System resources required to run this test are not available. The port may be  
busy with a valid call and therefore unavailable for certain tests. You must wait  
until the port is idle (yellow LED if off) before retesting.  
1. If the port is idle retry the command at 1-minute intervals a maximum of 5  
times.  
1001  
1002  
1003  
ABORT System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-989  
Table 3-436. TEST #165 Speech Synthesis DSP Tone Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1021  
ABORT The 440-Hz tone was not detected by the Tone Detector circuit and inter-digit  
time-out has occurred on the Tone Detector circuit.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort, verify all Tone Detector circuit packs in the  
system are functioning correctly by checking the Error Log and using the  
test board PCSS long command. Replace any faulty Tone Detector circuit  
packs and repeat the test.  
3. If the test continues to abort, replace the Speech Synthesis circuit pack.  
ABORT Response to the test request was not received within the allowable time period.  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
2100  
Any  
FAIL  
The 440-Hz tone was not detected by the Tone Detector circuits.  
1. If the test fails again, verify all Tone Detector circuit packs in the system are  
functioning correctly by checking the Error Log and using the test board  
PCSS long command. Replace any faulty Tone Detector circuit packs and  
repeat the test.  
2. If the test fails again, replace the Speech Synthesis circuit pack.  
PASS  
The 440-Hz tone has been detected correctly. User-reported troubles should  
be investigated using other tests and verifying other ports on this circuit pack  
are working correctly.  
Speech Synthesis Memory Test (#166)  
The encoded speech for the Speech Synthesis circuit pack is stored in on-board  
read-only memory. A checksum is computed for each 32K speech memory block  
and compared against a known checksum value. If all computed checksum  
values are successfully compared against the stored checksum values, the test  
passes. If, while testing the speech complex memory, the on-board  
microprocessor finds a memory error, the test is terminated and a failure is  
reported. This type of failure may affect other ports on the Speech Synthesis  
circuit pack, resulting in errors or alarms on each port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-990  
Table 3-437. TEST #166 Speech Synthesis Memory Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
1019  
ABORT System resources required to run this test are not available. The port may be  
busy with a valid call and therefore unavailable for certain tests. You must wait  
until the port is idle (yellow LED if off) before retesting.  
1. If the port is idle, retry the command at 1-minute intervals a maximum of 5  
times.  
ABORT Test is already running on a different port, possibly due to background  
maintenance activity. Only one of these tests may be active on a circuit pack at  
a time.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
ABORT Response to the test request was not received within the allowable time period.  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
2100  
Any  
FAIL  
The computed checksum from the speech vocabulary read-only memory did  
not compare correctly with the stored checksum. This type of failure may cause  
features using the Speech Synthesis Port’s speech services to malfunction and  
result in degradation of synthesized speech quality ranging from insignificant  
to major.  
1. Replace the circuit pack.  
PASS  
The computed checksum values were successfully compared against the  
stored checksum values. User-reported troubles should be investigated using  
other tests and verifying other ports on this circuit pack are working correctly.  
Speech Synthesis SSD Inquiry Test (#167)  
This test determines the sanity of the specified port’s Speech Synthesis Device  
(SSD). The on-board microprocessor tests the port’s SSD and determines if it is in  
a sane (test passes) or insane (test fails) condition. Other ports on the Speech  
Synthesis circuit pack continue to function correctly during this type of failure.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-991  
Table 3-438. TEST #167 Speech Synthesis SSD Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT System resources required to run this test are not available. The port may be  
busy with a valid call and therefore unavailable for certain tests. You must wait  
until the port is idle (yellow LED if off) before retesting.  
1. If the port is idle, retry the command at 1-minute intervals a maximum of 5  
times.  
2000  
2100  
ABORT Response to the test request was not received within the allowable time  
period.  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Any  
FAIL  
The SSD is insane.  
1. Replace the circuit pack.  
PASS  
The SSD is sane. User-reported troubles should be investigated using other  
tests and verifying other ports on this circuit pack are working correctly.  
Speech Synthesis PSS Handshake Test (#168)  
This test verifies control functionality between the on-board microprocessor and  
PSS controller. A failure occurs if either of the following events occur:  
■
The on-board microprocessor times out while waiting for the PSS controller  
to respond.  
■
An invalid command is received by the on-board microprocessor from the  
PSS controller.  
This type of failure affects all four ports on the Speech Synthesis circuit pack,  
resulting in errors or alarms on each port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-992  
Table 3-439. TEST #168 Speech Synthesis PSS Handshake Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT System resources required to run this test are not available. The port may be  
busy with a valid call and therefore unavailable for certain tests. You must wait  
until the port is idle (yellow LED if off) before retesting.  
1. If the port is idle, retry the command at 1-minute intervals a maximum of 5  
times.  
2000  
2100  
ABORT Response to the test request was not received within the allowable time period.  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Any  
FAIL  
The on-board microprocessor has timed out while waiting for the PSS controller  
to respond or an invalid command has been received by the on-board  
microprocessor from the PSS controller. This type of failure may cause features  
using the Speech Synthesis Port’s speech services to malfunction.  
1. Replace the circuit pack.  
PASS  
The on-board microprocessor/PSS handshake is working correctly.  
User-reported troubles should be investigated using other tests and verifying  
other ports on this circuit pack are working correctly.  
Speech Synthesis Parameter Update Test (#169)  
This test updates the DTMF interdigit time-out parameter used by the Speech  
Synthesis circuit pack to be consistent with that specified by the switch  
processing element (SPE).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
S-SYN-PT (Speech Synthesis Port)  
3-993  
Table 3-440. TEST #169 Speech Synthesis Parameter Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
ABORT System resources required to run this test are not available. The port may be  
busy with a valid call and therefore unavailable for certain tests. You must wait  
until the port is idle (yellow LED if off) before retesting.  
1. If the port is idle, retry the command at 1-minute intervals a maximum of 5  
times.  
2100  
Any  
ABORT Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
An internal system error has occurred.  
PASS  
The DTMF interdigit time-out parameter has been updated.  
1. User-reported troubles should be investigated using other tests and by  
verifying that other ports on this circuit pack are working correctly.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SEC-CDR (SEC-CDR Link Maintenance)  
3-994  
SEC-CDR (SEC-CDR Link  
Maintenance)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test cdr-link primary/secondary l CDR Link  
test cdr-link primary/secondary CDR Link  
Full Name of MO  
PRI-CDR/SEC-CDR  
PRI-CDR/SEC-CDR  
MINOR  
WARNING  
The SEC-CDR (SEC-CDR Link) maintenance strategy is covered in the  
PRI-CDR/SEC-CDR (PRI-CDR Link) Maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SW-CTL (Switch Control)  
3-995  
SW-CTL (Switch Control)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test network-control a sh  
test network-control a sh  
Full Name of MO  
Switch Control  
Switch Control  
SW-CTL  
SW-CTL  
MINOR  
MAJOR  
The Switch Control resides on the TN798 Processor circuit pack. The data  
channels (DATA-BD and DATA-CHL) also reside on the Processor circuit pack.  
The Switch Control is used to send control information between port circuit packs  
and the processor. This control information is sent via the PPN cabinet’s Time  
Division Multiplex (TDM) Bus. The portion of the TDM Bus used to transmit  
control messages is called the control channel. The control channel can be on  
either TDM Bus A or TDM Bus B, but only one bus is used for the control channel  
at any given time.  
The Switch Control is critical in the setup and take down of all calls but is not  
involved in the voice or data transmission that takes place during established  
calls. It is the Switch Control that detects when port circuit packs are plugged  
into or removed from the PPN cabinet. This information is then sent to the  
processor. The Switch Control monitors the health of the control channel on the  
PPN cabinet TDM Bus and informs the processor when errors occur.  
The Switch Control contains the hardware Time of Day (TIME-DAY) clock that the  
system uses for all its date and time information. In addition, the Switch Control  
also contains hardware to monitor critical system timing signals and informs the  
processor when these signals fail. For example, if the timing signals from a  
Tone-Clock circuit pack in the PPN cabinet fail, the Switch Control informs the  
processor.  
Error Log Entries and Test to Clear Values  
Table 3-441. SW-CTL Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
test network-control a sh r 1  
test network-control a r 3  
1
0
1
0
Any  
Any  
ON  
Any  
Control Channel  
Test (#94)  
MAJOR  
2 (a)  
Control Channel  
Test (#94)  
MAJOR  
ON  
test network control a r 3  
257 (b)  
0 or 1  
None  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SW-CTL (Switch Control)  
3-996  
Table 3-441. SW-CTL Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
513  
(c)  
Time of Day Clock  
Test (#95)  
MINOR  
ON  
test network-control a l r 3  
769 (d)  
1025  
Any  
None  
Switch Control  
Loop Around Test  
(#92)  
MAJOR  
ON  
test network-control a r 3  
1281 (e)  
1537  
Any  
Any  
None  
Switch Control  
Reset Test #93  
MAJOR  
MAJOR  
ON  
ON  
test network-control a l r 2  
1793 (f)  
3329 (g)  
None  
None  
(g)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. This error may not cause a Switch Control alarm if Error Type 769 is also  
present since this error may actually be caused by the loss of clock  
signals and not by a Switch Control failure.  
b. The 257 errors are reported to the processor by the Switch Control and  
indicate possible hardware problems on the Processor circuit pack. The  
receipt of these errors causes Switch Control maintenance to run specific  
Switch Control tests. If there really is a problem, the Switch Control tests  
usually causes other errors to be logged. In the rare case where no other  
errors are logged but 257 errors are occurring at a high rate (more than 10  
in the last hour), the Processor circuit pack should be replaced at the  
customer’s convenience.  
c. If the Aux Data is less than 100, the test may have been interrupted by  
LMM operations. Wait 1 minute, then test again. Retry the test a maximum  
of 3 times. If the Aux Data is more than 100 or fails two out of three times  
with Aux Data less than 100, the Processor circuit pack needs to be  
replaced.  
d. A 769 error occurs when the Switch Control reports a loss of timing signals  
to the processor. When this error is present, the Switch Control is usually  
not alarmed since any Switch Control test failures are really the result of  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SW-CTL (Switch Control)  
3-997  
faulty signals from the PPN cabinet Tone-Clock circuit pack. See  
TDM-CLK (TDM Bus Clock) Maintenance documentation for the  
procedures needed to diagnose Tone-Clock circuit pack troubles.  
e. This error indicates a loss of handshake between SW-CTL and the system  
software. Look for and resolve all other SW-CTL errors. In the rare case  
where no other errors are logged, but Error Type 1281 is occurring at a  
high rate (more than 10 in the previous hour), escalate the problem.  
A loss of handshake is caused by the Processor circuit pack. Follow these  
repair steps:  
1. Look for and resolve all other SW-CTL errors.  
2. Look for and resolve all other PKT-CTRL errors.  
3. If the error indicates a failure in the Processor circuit pack, replace  
the Processor circuit pack. Boot the system up after the Processor  
circuit pack has been inserted successfully into the control carrier.  
4. If the error of loss of handshake persists after the replacement of  
the Processor circuit pack, consider the replacement of the control  
carrier. It’s possible that the backplane of the control carrier may be  
defective.  
Recommended Repair Kits: Processor circuit pack (TN798) with  
correct software release.  
f. The Aux Data for this error is not meaningful. The 1793 errors are in-line  
errors that indicate a possible problem with the interface between the  
Switch Control and the processor. The receipt of these errors causes  
Switch Control maintenance to run specific Switch Control tests. If there  
really is a problem, the Switch Control tests usually causes other errors to  
be logged. In the rare case where no other errors are logged but 1793  
errors are occurring at a high rate (more than 10 in the last hour), the  
Processor circuit pack should be replaced at the customer’s convenience.  
g. This error indicates bad clock detection circuitry on the Processor circuit  
pack. Replace the Processor circuit pack according to the control carrier  
circuit pack replacement procedures.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Switch Control Reset Test, for example, you may also clear errors generated from  
other tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SW-CTL (Switch Control)  
3-998  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
D
Switch Control Reset Test (#93)  
X
Control Channel Interface Test (#92)  
X
X
X
X
X
X
X
X
X
X
X
ND  
ND  
ND  
ND  
ND  
D
Control Channel Transmission Test (#94)  
X
X
X
Time of Day Clock Test (#95)  
Control Channel Loop Around Test (DATA-BD) (#52) (a)  
NPE Audit Test (DATA-BD) (#50) (a)  
Data Channel Reset Test (DATA-CHL) (#107) (b)  
Data Channel Interface Test (DATA-CHL) (#108) (b)  
Maintenance Loop Around Test (DATA-CHL) (#109) (b)  
Data Channel Crosstalk Test (DATA-CHL) (#110) (b)  
Data Channel Local Loop Back Test (DATA-CHL) (#111) (b)  
D
X
X
X
ND  
ND  
ND  
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Refer to DATA-BD (Network Control Circuit Pack) Maintenance  
documentation for a description of these tests.  
b. Refer to DATA-CHL (Network Control Channel) Maintenance  
documentation for a description of these tests.  
Control Channel Interface Test (#92)  
Loop back messages are sent to the Switch Control via the interface used for  
control channel messages. The messages are returned to the SPE for verification  
via the same interface.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SW-CTL (Switch Control)  
3-999  
Table 3-442. TEST #92 Control Channel Interface Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2012  
ABORT  
ABORT  
Internal system error  
2013  
2100  
none  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
other  
FAIL  
Messages could not be looped back through the control channel interface. If  
this is a standard system, the customer probably cannot make or receive calls.  
1. This failure could be due to either a Processor circuit pack failure or the  
loss of system timing signals. If the Switch Control is alarmed, then  
suspect a Processor circuit pack failure. If the Switch Control is not  
alarmed, investigate the possible loss of system timing signals before  
replacing the Processor circuit pack. Test #94 also fails if the system  
timing signals are lost. If Test #94 passes, do not suspect the loss of timing  
signals.  
2. Run the Short Test Sequence several times to make sure that this failure is  
occurring consistently, run the Long Test Sequence to reset the Switch  
Control. Sometimes running the Long Test Sequence may clear the  
problem. If the test is still failing, proceed to Step 3 or 4.  
3. If the system can process calls, replace the Processor board.  
4. If calls cannot be made, replace the Processor board immediately.  
PASS  
The control channel interface between the processor and the Switch Control is  
working correctly.  
Switch Control Reset Test (#93)  
This test is destructive.  
This test resets the Switch Control and determines if it can successfully go  
through its initialization sequence. The test is destructive since there is the  
possibility of losing some control messages to or from port circuit packs.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SW-CTL (Switch Control)  
3-1000  
Table 3-443. TEST #93 Switch Control Reset Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2012  
ABORT  
ABORT  
Internal system error  
Could not allocate the necessary system resources to run this test.  
2013  
2100  
none  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000 or  
None  
FAIL  
The Switch Control could not be successfully reset. If this is a standard  
system, the customer probably cannot make or receive calls.  
1. This failure could be due to either a Processor circuit pack failure or the  
loss of system timing signals. If the Switch Control is alarmed, then  
suspect a Processor circuit pack failure. If the Switch Control is not  
alarmed, investigate the possible loss of system timing signals. See  
“TDM Bus Clock”. If many port circuit pack LEDs are lit, suspect a TDM  
Bus Clock problem. If only the Processor circuit pack LED is lit, suspect  
the Processor circuit pack. If the Processor circuit pack is determined  
to be at fault, proceed to Step 2.  
2. If calls cannot be made, replace the Processor board.  
PASS  
The Switch Control has initialized correctly. Look at results of the other tests  
to see if it is operating correctly.  
Control Channel Transmission Test (#94)  
Control channel messages are sent from the SPE to selected port circuit packs  
and the response from the port circuit packs is checked. This tests the ability of  
the Switch Control to send and receive messages on the control channel of the  
TDM Bus.  
Table 3-444. TEST #94 Control Channel Transmission Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
ABORT  
The port circuit packs necessary for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort, then replace the Processor circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SW-CTL (Switch Control)  
3-1001  
Table 3-444. TEST #94 Control Channel Transmission Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2012  
ABORT  
ABORT  
Internal system error  
Could not allocate the necessary system resources to run this test.  
2013  
2100  
none  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
0
FAIL  
The Switch Control cannot communicate on the TDM Bus control channel.  
The customer probably cannot make or receive calls.  
1. Run the Short Test Sequence several times to make sure this failure is  
occurring consistently, run the Long Test Sequence to reset the Switch  
Control. Sometimes, running the Long Test Sequence may clear the  
problem. Remember that the Long Test Sequence is destructive.  
Placing and receiving calls is affected for several seconds.  
2. If there are no TDM Bus alarms against the Standby TDM Bus, switch  
the control channel from its current bus to the Standby bus. If this test  
passes on the new bus, investigate the possibility of TDM Bus failures.  
If the test fails even after the control channel is switched to the standby  
TDM Bus, proceed to Step 3.  
3. If calls cannot be made, replace the Processor board.  
PASS  
The Switch Control can communicate with the port circuit packs over the  
TDM Bus.  
Time of Day Clock Test (#95)  
The short term accuracy of the Time of Day (TIME-DAY) clock is tested. The test  
reads the clock once, waits a short time, and reads the clock again. The second  
reading of the clock must be within certain limits relative to the first reading for  
the test to pass. The display time command can be used to display the current  
setting of the TIME-DAY clock.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SW-CTL (Switch Control)  
3-1002  
Table 3-445. TEST #95 Time of Day Clock Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The test was interrupted by a higher priority task.  
1000  
ABORT  
1. Rerun the test at 1-minute intervals a maximum of 5 times.  
2. If the test aborts 5 times, wait until the system is less heavily used and  
rerun the test at that time.  
2012  
2013  
ABORT  
ABORT  
Internal system error  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The Time of Day clock could not be read.  
2001  
FAIL  
1. Run the set time command and set the time to the current time.  
2. Run the Short Test Sequence several times to determine if setting the  
time corrected the error. Proceed to Step 3 if the error is still occurring.  
3. Replace the Processor circuit pack at the customer’s convenience .  
other  
FAIL  
The accuracy of Time of Day clock is not within limits.  
1. Run the Short Test Sequence several times to make sure the error is  
occurring consistently.  
2. Replace the Network Control (DATA-BD) circuit pack at the customer’s  
convenience..  
PASS  
The Time of Day clock on the Switch Control circuit pack is operating  
correctly.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
SYNC (Synchronization)  
3
3-1003  
SYNC (Synchronization)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
display errors  
Full Name of MO  
SYNC  
MAJOR  
MINOR  
Synchronization Maintenance  
Synchronization Maintenance  
Synchronization Maintenance  
SYNC  
SYNC  
display errors  
WARNING  
test synchronization  
The Synchronization Maintenance is composed of both hardware and software  
components and its purpose is to provide a common reference frequency for  
reliable digital communication between systems and other PBXs, COs or CPE.  
Synchronization is achieved via the use of several system components which  
include the Tone-Clock and the DS1 Interface.  
Depending on the network synchronization plan and the status of  
synchronization sources, the system timing reference may be a Tone-Clock  
circuit pack or DS1 interface circuit packs. Stratum 4 synchronization extracts  
timing information directly from a DS1 reference or from a Tone-Clock.  
Stratum 4 Synchronization  
The system can be configured with primary and secondary synchronization  
references (DS1 interface circuit packs) when using Stratum 4 synchronization.  
Both references are optional (since the local oscillator can be used), and the  
secondary reference is optional if a primary is provided. If this system is the  
master for the network, then its local oscillator would be used and no DS1s would  
be used as references.  
If the primary synchronization reference is not providing a valid timing signal, the  
system automatically switches to the secondary synchronization reference. If the  
secondary reference does not provide a valid timing signal or is not administered  
as a synchronization reference, a Tone-Clock circuit pack provides the system  
timing source. The system does not revert to the primary if the current reference  
is the secondary and is failing; however the system switches from the local  
oscillator to another reference when the new reference becomes available. Both  
the primary and secondary references must reside in the PPN.  
There are two kinds of Stratum 4 synchronization that are supported: Type I and  
Type II. Stratum 4 type I is more stable than Type II and provides some switching  
capability at the hardware level. It is important to note that Stratum 4 Type I  
operation is not possible when one or both of the DS1 interface circuit packs  
providing the reference sources is a TN722. Both must be the TN767B (or higher)  
or TN464C (or higher).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
SYNC (Synchronization)  
3
3-1004  
Synchronization Troubleshooting  
For Stratum 4 operation, major and minor alarms indicate that there is a problem  
with the system synchronization references. These alarms are resolved when the  
alarmed synchronization reference is restored.  
The status synchronization and display synchronization commands are used  
to determine the current system synchronization reference and the primary and  
secondary references that are administered respectively.  
Other commands associated with Synchronization Maintenance are disable  
synchronization-switch and enable synchronization-switch. These  
commands are used to disable the ability of Synchronization Maintenance to  
switch between synchronization references and to enable this switching ability,  
respectively. The set synchronization command is executed only after  
synchronization has been disabled and is used to manually switch to a specific  
synchronization reference. This command is useful to diagnose synchronization  
problems by forcing a specific reference (DS1 or Tone-Clock) to be the system  
synchronization reference to determine if a specific reference is providing a valid  
timing signal. For Stratum 3 operation, only a TN780 Tone-Clock circuit pack may  
be specified. To switch synchronization to the Stratum 3 clock, use the enable  
synchronization-switch command after verifying that the Stratum 3 clock is  
wired correctly.  
The system synchronization planner must avoid creating a timing loop when  
administering the primary and secondary synchronization references in a  
system. A timing loop exists whenever a system receives timing from another  
system whose timing reference is directly or indirectly derived from itself. Timing  
loops can lead to loss of digital data between systems that are exchanging data  
with any system within the loop. An invalid timing signal is also generated by any  
system within the loop, thus propagating the invalid timing signal to any  
system(s) using a system within the loop as a synchronization reference. Figure  
3-41 shows a timing loop and a correct distribution of timing between the  
systems.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
SYNC (Synchronization)  
3
3-1005  
"DEFINITY"  
COMMUNICATONS  
SYSTEM  
"DEFINITY"  
COMMUNICATONS  
SYSTEM  
GENERIC 2  
GENERIC 2  
"DEFINITY"  
COMMUNICATONS  
SYSTEM  
"DEFINITY"  
COMMUNICATONS  
SYSTEM  
"DEFINITY"  
COMMUNICATONS  
SYSTEM  
"DEFINITY"  
COMMUNICATONS  
SYSTEM  
GENERIC 1  
GENERIC 1  
GENERIC 1  
GENERIC 1  
TIMING LOOP  
NOTE:  
CORRECT TIMING  
DISTRIBUTION  
SYNCHRONIZATION REFERENCE  
(PRIMARY OR SECONDARY)  
Figure 3-41. Synchronization Timing Loop  
A correctly designed network has no loops and each piece of equipment in the  
network is supplied by a clock of equal or lower stratum (that is, the inputs to a  
Stratum 3 clock should NEVER be from a Stratum 4 device). It is strongly  
recommended that the network administrator be consulted before  
administering any synchronization changes.  
Error Log Entries and Test to Clear Values  
Table 3-446. Synchronization Error Log Entries  
Aux  
Alarm  
Level  
On/Off  
Board  
Error Type  
Data  
Associated Test  
Test to Clear Value  
test synchronization  
None  
1
0
0
Any  
Any  
Any  
1
1 (a)  
Any  
None  
WARNING/  
MINOR(j)  
OFF  
2
18 (b)  
0
disable sync  
None  
WARNING  
OFF  
OFF  
enable sync  
None  
1
1
257 (c)  
Any  
WARNING/  
2
MINOR(j)  
513 (d)  
Any  
None  
WARNING/  
OFF  
None  
2
MAJOR(j)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
SYNC (Synchronization)  
3
3-1006  
Table 3-446. Synchronization Error Log Entries — Continued  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Error Type  
Associated Test  
None  
Test to Clear Value  
None  
769 (e)  
MAJOR/  
WARNING  
OFF  
3
4
1793  
0-50  
None  
MAJOR/  
OFF  
enable sync  
WARNING  
4
2049 (f) (h)  
0
0
None  
None  
WARNING  
WARNING  
OFF  
OFF  
None  
None  
4
2305 (g) (h)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. This error type initially raises a Warning alarm. If this error type persists and alarms are not  
downgraded on this MO due to the value of set options, then, after a period of time, a Minor or Major  
alarm is raised.  
3. Major alarms on this MO may be downgraded to Warning alarms based on the value used in the set  
options command.  
4. It may take up to one hour for these SYNC alarms to clear due to "leaky bucket" strategy.  
Notes:  
a. This error indicates a problem with the primary DS1 reference. It is cleared  
when the primary reference is restored. The following steps should give an  
indication of the source of the problem:  
1. Check if the primary DS1 interface circuit pack is inserted in the  
carrier via the list configuration board PCSS command.  
2. Check the connection of the cable supplying the external timing  
source to the primary DS1 interface circuit pack.  
3. Test the primary DS1 interface circuit pack via the test board PCSS  
long command. Check the Error Log for DS1-BD errors and refer to  
the DS1-BD (DS1 Interface Circuit Pack) Maintenance  
documentation to resolve any errors associated with the primary  
DS1 interface circuit pack. If no errors are listed in the Error Log for  
the primary DS1 interface circuit pack, continue with the following  
steps.  
4. Test the active Tone-Clock circuit pack in the master port network  
via the test tone/clock PC long command. Check the Error Log for  
TDM-CLK errors and verify that TDM Bus Clock Test #148 passes  
successfully. If Test #148 fails with an Error Code 2 through 32, refer  
to ‘‘TDM-CLK (TDM Bus Clock)’’ to resolve the problem. If not,  
continue with the following steps.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
SYNC (Synchronization)  
3
3-1007  
5. Execute the disable synchronization-switch and the enable  
synchronization-switch commands. These two commands (when  
executed together) switch the system synchronization reference to  
the primary DS1 interface circuit pack. Check the Error Log and  
execute the status synchronization command to verify that the  
primary DS1 interface circuit pack is still the system  
synchronization reference. If the primary DS1 interface circuit pack  
is not the system synchronization reference, continue with the  
following step.  
b. This error indicates that Synchronization Maintenance has been disabled  
via the disable synchronization-switch command. Execute the enable  
synchronization-switch command to enable Synchronization  
Maintenance reference switching and to resolve this alarm.  
c. This error indicates a problem with the secondary DS1 reference. It is  
cleared when the secondary reference is restored. Refer to note (a) to  
resolve this error substituting secondary for primary in the preceding  
resolution steps.  
d. This error indicates that the Tone-Clock circuit pack is providing the timing  
source for the system. The primary and secondary (if administered) are  
not providing a valid timing signal. Investigate errors 1 and 257 to resolve  
this error.  
e. This error indicates excessive switching of system synchronization  
references has occurred. When this error occurs, synchronization is  
disabled and the Tone-Clock circuit pack (in the master port network)  
becomes the synchronization reference for the system. Execute the  
following steps to resolve this error:  
1. Check for timing loops and resolve any loops that exist.  
2. Test the active Tone-Clock circuit pack in the master port network  
via the test tone/clock PC long command. Check the Error Log for  
TDM-CLK errors and verify that TDM Bus Clock Test #148 passes  
successfully. If Test #148 fails with an Error Code 2 through 32, refer  
to the TDM-CLK (TDM Bus Clock) Maintenance documentation to  
resolve the problem. If not, continue with the following steps.  
3. Replace the primary and secondary (if administered) DS1 Interface  
circuit packs.  
4. Check for an error logged against the primary or secondary DS1  
board. If there is an error, follow the DS1 section to resolve the  
errors. If there is not, enter enable sync, and wait for two to five  
minutes for the primary sync source to come on-line.  
f. This error indicates that the slave Tone-Clock circuit pack is experiencing  
loss of signal. Refer to note (i) for error resolution steps.  
g. The following steps should be executed to resolve error 2049 and 2305:  
1. Check for timing loops, and resolve any loops that exist.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
SYNC (Synchronization)  
3
3-1008  
2. Error 2049:  
■
Test the Tone-Clock circuit packs in the master and slave  
port networks via the test tone/clock PC long command.  
Check the Error Log for TDM-CLK errors and verify that TDM  
Bus Clock Test #148 passes successfully. If Test #148 fails  
with an Error Code 2 through 32, refer to “TDM-CLK” to  
resolve the problem. If not, continue with the following steps.  
■
■
If the system synchronization reference is a Tone-Clock  
circuit pack and the master Tone-Clock circuit pack fails  
TDM Bus Clock Test #150, follow the steps listed in  
“TDM-CLK” to replace the master Tone-Clock circuit pack.  
If the system synchronization reference is a DS1 interface  
circuit pack and the master Tone-Clock circuit pack fails  
TDM Bus Clock Test #150, the primary or secondary (if  
administered) synchronization references are not providing  
valid timing signals for the system. Check the system  
synchronization references administered, and follow the  
steps outlined in note (a) if the primary synchronization  
reference is providing timing for the system or note (c) if the  
secondary synchronization reference is providing timing for  
the system.  
■
If the slave Tone-Clock circuit pack fails the TDM Bus Clock  
Test #150 but the master Tone-Clock does not fail this test,  
the master Tone-Clock circuit pack must be replaced. Follow  
the Tone-Clock replacement steps listed in the “TDM-CLK”.  
If SLIP errors remain follow SLIP ANALYSIS.  
3. Error 2305:  
■
If the problem persists, replace the Tone-Clock circuit pack  
in the slave port network. Follow the steps listed in  
“TDM-CLK” to replace the Tone-Clock circuit pack.  
h. Noise on the DS1 line can cause transient alarms on synchronization.  
Therefore, when a synchronization problem occurs causing error types 1,  
257, or 513, a WARNING alarm is first raised for 15 to 20 minutes before  
the alarm is upgraded to a MAJOR or MINOR alarm.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the Test Synchronization Test, for example, you may  
also clear errors generated from other tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
SYNC (Synchronization)  
3
3-1009  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Test Synchronization Test (#417)  
X
X
ND  
1. D = Destructive; ND = Nondestructive  
Test Synchronization Test (#417)  
This test updates all the Synchronization Maintenance component circuit packs  
with the correct information regarding their role in providing synchronization for  
the system. All the Tone-Clock and DS1 Interface circuit packs in the system are  
updated via this test. This test will either pass or abort.  
Table 3-447. TEST #417 Test Synchronization Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
PASS  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The Synchronization Maintenance component circuit pack parameters have  
been successfully updated. The system should be synchronized after  
successful execution of this test. If synchronization problems still exist, refer  
to the Error Log to obtain information regarding the source of the problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SYS-LINK (System Links)  
3-1010  
SYS-LINK (System Links)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial System Technician  
Command to Run  
Full Name of MO  
SYS-LINK  
WARNING  
test sys-link PCSSpp  
SYSTEM LINKS  
System Links are packet links that originate at the Packet Interface board and  
traverse various hardware components to specific endpoints. The hardware  
components involved on the forward and reverse routes can be different,  
depending upon the configuration and switch administration. This software  
release supports the following link types:  
PRI  
ISDN PRI D-Channel Link terminating at a Universal DS1 board  
Remote Socket Control Link for C-LAN  
RSCL  
RSL  
Remote Socket Link for C-LAN  
Recording System Link Events  
The system links maintenance object is used to record all errors encountered on  
the links. Most of these events are not extra-ordinary, unless they occur with an  
alarming frequency. The events are logged as they occur, so as to leave a trail  
helping analyze abnormal behavior exhibited by the endpoints attached to the  
links or the links themselves.  
When a link goes down, a WARNING alarm is raised immediately. Other alarming  
conditions which do not cause the link to go down also get a WARNING alarm.  
Identifying a System Link  
In order to trace problems associated with a system link, it is necessary to find its  
location. A PRI link can be uniquely identified by its endpoints.  
Display Errors/Alarms  
The output of the display errors or display alarm commands shows the location  
of the system link for entries with a Maintenance Name of SYS-LINK. You can  
restrict the scope of the output of these commands by specifying category  
sys-link on the input form. The link type is listed under the Alt Name field.  
List sys-link  
The command list sys-link lists all system links present in the system. The  
location of the system link and the link type are displayed for each link.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SYS-LINK (System Links)  
3-1011  
Common procedure for repairing link problems  
The state of a system link is dependent on the state of the various hardware  
components that it travels over. To resolve any problems associated with a  
system link, use the following procedure.  
The switch maintains a list of hardware components over which the link travels  
called the hardware path. There are two hardware paths, the current hardware  
path and the faulted hardware path for each of the system links. The current  
hardware path is present only for those links that are currently up. When a link is  
down, the current hardware path is empty. The faulted hardware path, is always  
present once the link has gone down and is not cleared when the link  
subsequently recovers. The faulted path preserves the path that the link  
traversed when it last went down. The time at which the faulted path was last  
recorded is preserved and is accessible through the status sys-link location  
and list sys-link commands. Therefore, the focus of attention for problems which  
do not involve a link that is down, is the current hardware path. If the link is down,  
faulted hardware path is the focus of attention.  
The command status sys-link location will present the state of both the  
hardware paths (current and faulted) along with the state of each of the  
components in the hardware path. When analyzing any system link problem, look  
for alarms on the components listed under desired hardware path. If any alarms  
are present, then follow the maintenance procedures for the alarmed  
components to clear those alarms first.  
When all the components are alarm free, wait for 3 minutes to allow the links to  
recover. Test the system link through test sys-link PCSSpp long clear and  
notice any tests that fail. If any failures are found, fix the problems indicated by  
the tests and repeat the procedure.  
Error Log Entries and Test to Clear Values  
Table 3-448. SYS-LINK Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
13 (a)  
System Link Status  
(985)  
WARNING  
OFF  
257 (b)  
513 (c)  
772 (d)  
1025 (e)  
1281 (f)  
WARNING  
WARNING  
WARNING  
WARNING  
WARNING  
OFF  
OFF  
OFF  
OFF  
OFF  
test sys-link PCSSpp l cl  
test sys-link PCSSpp l cl  
test sys-link PCSSpp l cl  
test sys-link PCSSpp l cl  
test sys-link PCSSpp l cl  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SYS-LINK (System Links)  
3-1012  
Table 3-448. SYS-LINK Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1537 (g)  
1793 (h)  
2049 (i)  
WARNING  
WARNING  
WARNING  
OFF  
OFF  
OFF  
test sys-link PCSSpp l cl  
test sys-link PCSSpp l cl  
test sys-link PCSSpp l cl  
Notes:  
a. Error Type 13: indicates that the link went down. The link may have gone  
down or never come up. Enter command status sys-link location and  
check the value of the field Faulted Path. If the value is default, then  
the link never came up. If the value is present, then the link came up and  
went down.  
Follow the Common Procedure described above. Wait for 3 min before  
checking the link state. Repeat the procedure until there are no problems  
with the components.  
b. Error Type 257: indicates that the link has experienced uplink flow control.  
Manifest effect of this error is that the end-point may be hyperactive. The  
system link is alarmed if 4 or more errors of this type are detected within  
10 minutes.  
To correct the problem, follow the Common Procedure described above.  
Clear errors and wait for 10 minutes.  
c. Error Type 513: indicates that the link has experienced downlink flow  
control. Manifest effect of this error is that some information packets from  
the packet interface board have been lost. The link is reset on first  
occurrence, hence, Error 1025 will also be logged. The system link is  
alarmed if 2 or more errors of this type are detected within 10 minutes.  
To correct the problem, follow the Common Procedure described above.  
Clear errors and wait for 10 minutes.  
d. Error Type 772: indicates that the link experienced a temporary  
disconnect due to excessive resets or state transitions. The effect of this  
error is that the link is taken down and then brought up again. The system  
link is alarmed if 2 or more errors of this type are detected within 10  
minutes.  
To correct the problem, follow the Common Procedure described above.  
Clear errors and wait for 10 minutes.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SYS-LINK (System Links)  
3-1013  
e. Error Type 1025: This error indicates that the link has been reset. Manifest  
effect of this error is that information packets queued at the time of reset  
are been lost. The system link is alarmed if 20 or more errors of this type  
are detected within 10 minutes.  
To correct the problem, follow the Common Procedure described above.  
Clear errors and wait for 10 minutes.  
f. This error indicates that the link has experienced slow transmit rate due to  
remote endpoint being busy. Manifest effect of this error is that the  
end-point location may experience slower throughput rate and/or noisy  
transmission. The system link is alarmed if 4 or more errors of this type are  
detected within 10 minutes.  
To correct the problem, ensure that the remote endpoint is functioning  
properly. If the problem persists, follow the Common Procedure described  
above. Clear errors and wait for 10 minutes.  
g. This error indicates that the link has experienced slow transmit rate due to  
excessive retransmission. Possible causes for this error may be that the  
switch is overrunning the end-point or that the end-point is sick. Manifest  
effect of this error is that the end-point location may experience slower  
throughput rate. The system link is alarmed if 4 or more errors of this type  
are detected within 10 minutes.  
To correct the problem, follow the Common Procedure described above.  
Clear errors and wait for 10 minutes.  
h. This error indicates that the link has experienced slow transmit rate due to  
unknown causes. Manifest effect of this error is that the end-point location  
may experience slower throughput rate and the Packet Interface may  
experience backup or congestion. The system link is alarmed if 4 or more  
errors of this type are detected within 10 minutes.  
To correct the problem, follow the Common Procedure described above.  
Clear errors and wait for 10 minutes.  
i. This error indicates that the link has transmitted an excess amount of  
packets. The transmit buffers of this link have been purged. The system  
link is alarmed if 4 or more errors of this type are detected within 10  
minutes.  
To correct the problem, follow the Common Procedure described above.  
Clear errors and wait for 10 minutes.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Testing for system links is different from the standard test procedures for  
maintenance objects. In addition to testing the system link maintenance object,  
the user is allowed to test all the components in the path of the system link. There  
are two paths preserved for the link. The current path, if present, represents the  
path traversed by the link currently. This path will not be present when the link is  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SYS-LINK (System Links)  
3-1014  
down. The other path, the faulted path is present if the link has ever gone down  
or never come up. If the link came up and went down, then the faulted path is  
marked "Present". If the link never came up, the faulted path is marked "Default".  
Either case, it represents the path on which the link was attempted or established  
unsuccessfully.  
Test command for the system links, test sys-link PCSSpp can be specified with  
current or faulted as an optional argument if the user wishes to test all the  
components in the specified path. The tests executed will be the same if the user  
were to test each component manually. In the event that the user does not  
specify any path, then only the tests specified for the system links are executed.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
System Link Status (#985)  
X
X
N
1. D = Destructive, ND = Non-destructive  
System Link Status (#985)  
This non-destructive test queries the switch for the status of the system link and  
verifies that all switch components have the same view of the link state.  
Table 3-449. TEST #985 System Link Status  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Could not locate the system link associated with this location  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Internal system error  
1007  
2500  
6
ABORT  
ABORT  
FAIL  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
The system link is down.  
1. Follow the procedure for error type 13.  
PASS  
The system link is up.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SYS-PRNT (System Printer)  
3-1015  
SYS-PRNT (System Printer)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run Full Name of MO  
SYS-PRNT  
SYS-PRNT  
MINOR  
test sp-link l  
System Printer  
System Printer  
WARNING release sp-link  
The Report Scheduler feature provides the capability to schedule selected  
administration commands to be printed by an asynchronous System Printer  
(SYS-PRNT) or sent to a Personal Computer (PC). The System Printer Link to this  
external device can be administered either as a data extension.  
System Printer Link Maintenance provides a strategy for maintaining the link  
between the system and an external SYS-PRNT output device. The strategy  
includes a set of tests for detection of errors during normal operation,  
troubleshooting actions, and alarms for serious problems. System Printer Link  
Maintenance uses a try-and-wait mechanism for maintaining the SYS-PRNT link.  
If the link set-up fails, a minor alarm is raised for service attention. A warning  
alarm is raised when the SPE has been busied out. A maximum of two link retry  
attempts is made. After the second attempt, set-up attempts are only made by  
the application software (that is, the 15-minute timer fires and jobs are printed  
unless an immediate job was entered.) After two unsuccessful attempts to  
establish the link, a MINOR alarm is raised for service attention. If the System  
Printer Link is torn down due to an error, System Printer Link Maintenance raises  
a MINOR alarm but does not attempt to bring up the System Printer Link.  
In DEFINITY Generic 1, the physical configuration for the System Printer Link is  
from a data channel (DATA-CHL) on the Processor circuit pack (DATA-BD) to a  
data extension where the SYS-PRNT output device connects via the standard EIA  
232C interface  
The data extension can be a(n) PDM, MPDM, DTDM, or ADU. The PDM, MPDM,  
or DTDM connects to a Digital Line (DIG-LINE) on the TN754 or TN754B Digital  
Line circuit pack (DIG-BD); the ADU connects to a Data Line (DAT-LINE) of the  
TN726 Data Line circuit pack (DT-LN-BD).  
System Printer Link Maintenance does not cover the elements comprising the  
SYS-PRNT physical link; that is, the external SYS-PRNT output device, the EIA  
port on the Processor circuit pack, the Data Module (PDM/MPDM/DTDM) and the  
Digital Line of TN754 or TN754B Digital Line circuit pack, the ADU and the Data  
Line of TN726 Data Line circuit pack, and the data channels on the TN798  
Processor circuit pack. If System Printer Link Maintenance cannot restore the  
System Printer Link, the maintenance tests of these individual components of the  
System Printer Link must be executed to diagnose faults.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SYS-PRNT (System Printer)  
3-1016  
Procedures for Restoring the System Printer Link  
The following procedures should be followed to restore the System Printer Link:  
1. Determine the status of the System Printer Link via the status sp-link  
command. Verify that the System Printer Link is not busied out for  
maintenance. On the System Printer Link Status Form, this is indicated by  
a "no" in the "Maintenance Busy?" field. If the System Printer Link has been  
busied out, issue the release sp-link command. If the link is "down,"  
proceed to Step 2.  
2. Issue the display system feature command to determine the destination  
of the System Printer Link.  
If the destination is an extension number, enter the status data-module  
<extension> command and verify that the data extension is  
in-service/idle. If the data extension is NOT available, refer to the  
"Port/Channel Number" field on the "Data-Module Status" Form. Look for  
errors and/or alarms on the circuit pack with which this extension is  
associated. Refer to the appropriate MO documentation for recommended  
repair strategy. Continue with Step 3.  
If the destination is eia, look for PR-MAINT errors in the Hardware Error  
Log. If errors are present, refer to Maintenance/Tape Processor  
Maintenance documentation, and continue with Step 5.  
3. Determine if a data channel on the Network Control circuit pack is  
in-service/idle as follows:  
a. Use the list data-module command to find out the extension  
numbers of the data channels on the Network Control circuit pack.  
(There is a maximum of 4. They are listed as "netcon" on the Active  
SPE. Ignore the Standby data channels.)  
b. Enter the status data-module <extension> command to verify that  
at least one Active data channel is in-service/idle.  
4. If four data channels are administered and none are available, then look  
for DATA-CHL/DATA-CON/DATA-BD errors in the Hardware Error Log. If  
errors are present, refer to these MO sections for recommended  
maintenance strategy. When problems (if any) with  
DATA-CHL/DATA-CON/DATA-BD have been resolved, continue with Step  
5.  
If fewer than four data channels are administered, then use the add  
data-module command to add a network control data module to the  
system.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SYS-PRNT (System Printer)  
3-1017  
5. Verify the availability of the external SYS-PRNT output device as follows:  
Make sure that the SYS-PRNT output device is on-line and  
ready-for-service. Check the physical connectivity between the Data  
Module and the SYS-PRNT output device or between the EIA port on the  
backplane of the switch and the SYS-PRNT output device.  
6. Verify that there are less than three active logins to the system. If this  
condition exists, a login session must be terminated before the System  
Printer Link can be established.  
NOTE:  
It is recommended that the System Printer Link be busied out before  
executing maintenance tests over objects which compose the  
System Printer Link. If the System Printer Link is busied out, then all  
System Printer Link maintenance actions are deactivated.  
Error Log Entries and Test to Clear Values  
Table 3-450. SYS-PRNT Maintenance Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Any  
Alarm Level  
Any  
Test to Clear Value  
test sp-link  
1
0
0
0
Any  
18 (a)  
busyout sp-link  
WARNING  
OFF  
OFF  
release sp-link  
test sp-link l  
257 (b)  
1 to 6  
Link Retry Test  
(#215)  
MINOR/  
WARNING  
2
513 (c)  
0
None  
MINOR  
OFF  
test sp-link  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Minor alarms on this MO may be downgraded to Warning alarms based on the value used in the  
set options command.  
Notes:  
a. System Technician has busied out the System Printer Link.  
b. A failure was encountered while attempting to set up the System Printer  
Link. This attempt could have been initiated by either the Report  
Scheduler software or link maintenance [automatic link retry or the as the  
result of a Link Retry Test (#215) request]. The Aux Data field contains the  
following diagnostic information to aid in the correction of the failure:  
1. unavailability of system resources (too many active logins to the  
system).  
2. no data channels (DATA-CHLs) available on the Network Control  
circuit pack (DATA-BD).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SYS-PRNT (System Printer)  
3-1018  
3. 4- time-out during setup attempt. Most likely due to problem with  
physical link or printer status.  
4. internal system error. Most likely temporary/sporadic failure.  
5. the data module the printer is trying to use is busy with another call.  
Use the Status data module command to determine when the port  
is available for testing.  
Refer to the ‘‘Procedures for Restoring the System Printer Link’’ section for  
recommended maintenance strategy.  
c. The SYS-PRNT was interrupted because of one of the following reasons:  
1. the cable to the SYS-PRNT output device is disconnected;  
2. the SYS-PRNT output device is powered off;  
3. the data extension to which the SYS-PRNT output device connects  
has been busied out;  
4. internal software error.  
Check the connectivity of the wires and cables among the wall jacket,  
data module, and SYS-PRNT output device. Follow the instructions  
provided in the ‘‘Procedures for Restoring the System Printer Link’’ section.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
When inspecting errors in the system and deciding which ones to address,  
always investigate errors in the order they are presented in the table below. By  
clearing error codes associated with the Link Retry Test, for example, you may  
also clear errors generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Link Tear Down Test (#213)  
Link Retry Test (#215)  
D/ND  
D
X
X
X
X
X
ND  
Link Tear Down Test (#213)  
ND  
1. D = Destructive; ND = Nondestructive  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SYS-PRNT (System Printer)  
3-1019  
Link Tear Down Test (#213)  
This test is destructive.  
The Link Tear Down Test disconnects the existing link between DEFINITY Generic  
1 and the external SYS-PRNT output device. If the link has been disconnected  
already, this test just returns PASS. All resources allocated for a System Printer  
Link are released after this test.  
Table 3-451. TEST #213 Link Tear Down Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
40, 50  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 2 times.  
The System Printer Link has been busied out.  
1010  
1. Enter the release sp-link command to release the System Printer Link  
from the busyout state.  
2. Reissue the test sp-link long command to execute the test.  
Internal system error  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 2 times.  
PASS  
The System Printer Link is torn down or a Short Test Sequence was  
executed and the link was not torn down.  
Link Retry Test (#215)  
The Link Retry Test sends a message to the SYS-PRNT software process either  
(1) to make a data call to the extension to which the SYS-PRNT output device  
connects OR (2) to open the EIA port to the SYS-PRNT output device. If the  
System Printer Link is already up, this test passes without making a data call or  
opening the EIA port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
SYS-PRNT (System Printer)  
3-1020  
Table 3-452. TEST #215 Link Retry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
10, 20  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 2 times.  
Internal system error  
30  
1. Refer to the ‘‘Procedures for Restoring the System Printer Link’’ section  
for recommended maintenance strategy.  
1010  
ABORT  
The System Printer Link has been busied out.  
1. Enter the release sp-link command to release the System Printer Link  
from the busyout state.  
2. Reissue the test sp-link long command to execute the test.  
FAIL  
The System Printer Link CANNOT be established.  
1. Refer to the ‘‘Procedures for Restoring the System Printer Link’’ section  
for recommended maintenance strategy.  
PASS  
The System Printer Link is up.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
SYSTEM (System)  
3
3-1021  
SYSTEM (System)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
Full Name of MO  
SYSTEM  
None  
None  
SYSTEM  
1. SYSTEM only has errors associated with it and thus only appears in the Error Log  
and not in the Alarm Log. There are no tests that can be run with SYSTEM.  
SYSTEM is generally used when software encounters a problem with either  
hardware or itself and requests a restart to clear the problem. SYSTEM also logs  
errors that cannot be associated with any single process. This is not a problem.  
The initcauses log should also confirm that a software-requested restart was  
performed.  
Error Log Entries and Test to Clear Values  
The Aux Data field may be 0 or the return code from a bad software call, and the  
following examples in no way exhaust the possibilities. Often, two errors are  
logged at the same time for each problem.  
Table 3-453. System Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
None  
1
0
0
0
Any  
Any  
8 (a)  
None  
None  
None  
None  
None  
None  
None  
None  
None  
None  
9 (b)  
Any  
Any  
10 (c)  
21 (d)  
133(e)  
355 (f)  
356 (g)  
601 (h)  
602 (i)  
603 (j)  
0
Any  
Any  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
SYSTEM (System)  
3
3-1022  
Notes:  
a. A System Restart Level 3 was requested.  
b. A System Restart Level 2 was requested. This can happen due to a loss of  
tones (due to a faulty Tone-Clock circuit pack).  
c. A System Restart Level 1 was requested.  
d. A process trapped.  
e. This error appears when patching, and subsequently applying the patch  
by a craft-requested reset system 1.  
f. A Restart Level 2 occurred due to a power loss.  
g. A Restart Level 2 occurred due to a tone clock loss.  
h. An error occurred during initialization.  
i. An error occurred while loading translations and the system requested a  
Restart Level 3.  
j. A process was reset.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-BD (TN2185 ISDN Trunk-Side BRI)  
3-1023  
TBRI-BD (TN2185  
ISDN Trunk-Side BRI)  
MO Name (in  
Alarm Log)  
1
Alarm Level  
Initial Command to Run  
Full Name of MO  
TBRI-BD  
TBRI-BD  
MINOR  
test board PCSS l r#  
1. Where P is the port network number (1), C is the carrier designation (A, B, or C), and SS is the  
the carrier slot address where the circuit pack is located (1, 2, and so forth).  
The TN2185 circuit pack contains eight, 4-wire ports that interface to the network  
at the ISDN S/T reference point over two 64 Kb/s channels (B1 and B2) and over  
a 16Kb/s signaling (D) channel. The B1 and B2 channels can be simultaneously  
circuit switched, or individually packet switched. Only one channel per trunk can  
be packet switched due to Packet Processing Element (PPE) limitations. The D  
channel is either circuit switched or packet switched. Packet switching uses the  
PPE to combine all D channels into a single physical channel, which is then  
routed via the concentration highway to the Network Control Element (NCE) and  
then to the TDM bus. The circuit-switched connections have a Mu-law or A-law  
option for voice and operate as 64Kb/s clear data channels. The  
packet-switched channels support the LAPD protocol and conform with the  
CCITT Q.920 Recommendations for D-channel signaling.  
LEDs  
The three LEDs on the circuit pack’s faceplate indicate board status. When  
illuminated, the red LED indicates a board failure or a major or minor on-board  
alarm, the green LED indicates that testing is in progress, and the amber LED  
indicates that the board is in use.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-BD (TN2185 ISDN Trunk-Side BRI)  
3-1024  
S
PBX  
NT2  
NT2  
CO  
TE  
4-Wire  
S
V
PRI  
1
R
4-Wire  
U
Terminal  
Adapter  
2
U
T
LT  
NT1  
TE  
3
T
NT  
2-Wire  
NT  
4-Wire  
LT  
NT1  
4
NT  
NT  
4-Wire  
NT2  
2-Wire  
LT  
NT2  
S/T  
U
NT  
2-Wire  
S/T  
NT1  
T
TE  
NT  
2-Wire  
TE  
TE  
5
PBX  
cydfisdn RPY 072397  
ISDN Interface Reference Points  
Figure 3-42. Integrated Trunk-Side BRI, ISDN Interface Reference Points  
ISDN Interface Reference Point definitions:  
LT  
V
Logical Terminal  
Primary Rate user/network (asymmetrical) trunk interface. The ECS is capable of  
acting as the user or as the network side of this 1.544 - or 2.048-Mbps interface.  
R
S
Interface between Terminal Equipment and Network Termination  
Basic Rate network-side 4-wire line interface  
1
S/T  
T
4-wire Basic Rate connection to a Network Termination .  
2
4-wire Basic Rate interface to a Network Termination.  
TE  
U
1
Terminal Equipment  
Basic Rate network-side 2-wire line interface.  
TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side)  
TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side)  
2
3
2-Wire ISDN-BRI circuit pack  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-BD (TN2185 ISDN Trunk-Side BRI)  
3-1025  
4
5
TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side)  
TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side)  
1. Network Termination 2 (NT2), that terminates Layer 1 and higher layers. PBXs, LANs, and  
terminal controllers typically provide NT2 functionality including protocol handling and  
multiplexing for Layers 2 and 3.  
2. Network Termination 1 (NT1), that terminates Layer 1 and monitors maintenance, performance,  
timing, power transfer, multiplexing, and multi-drop termination with contention resolution.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-454. TBRI-BD Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
ON  
ON  
test board PCSS sh r 1  
1 (a)  
Any  
None  
MINOR  
MINOR  
257 (b)  
65535  
Control Channel Loop  
Test (#52)  
test board PCSS r 20  
513 (c)  
4352  
to  
None  
ON  
4357  
769 (d)  
4358  
4363  
1025 (e)  
NPE/NCE Audit Test  
(#50)  
None  
ON  
ON  
ON  
1291 (f)  
1294 (g)  
4359  
Clear Error Counters  
(#270)  
MINOR  
MINOR  
46088  
to  
SAKI Sanity Test (#53)  
See (h)  
46096  
1537 (h)  
1793 (i)  
1794 (i)  
1795 (i)  
2305 (j)  
2306 (i)  
3330 (j)  
3586 (k)  
46082  
46080  
46094  
46085  
46104  
46081  
46083  
MINOR  
MINOR  
MINOR  
MINOR  
None  
ON  
ON  
ON  
ON  
ON  
ON  
OFF  
OFF  
None  
MINOR  
MINOR  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-BD (TN2185 ISDN Trunk-Side BRI)  
3-1026  
Table 3-454. TBRI-BD Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
3840(l)  
4096  
to  
4101  
3842 (m)  
3843 (n)  
46095  
46097  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. The circuit pack stopped functioning or is physically removed from the  
system.  
NOTE:  
This alarm logs approximately 11 minutes after removing the circuit  
pack and/or the SAKI Sanity Test (#53) fails.  
If the circuit pack is not in the system, insert a circuit pack in the same slot  
as the error indicates. See note (g).  
b. Transient communication problems between the switch and this circuit  
pack. Execute the test board PCSS command and refer to the repair  
procedures for the Control Channel Loop Around Test (#52).  
c. On-board hardware failure. Aux data values correspond to the following  
detected errors:  
4352  
4353  
4355  
4357  
External RAM error  
Internal RAM error  
ROM Checksum error  
Instruction set error  
Reset the circuit pack with the busyout board PCSS and reset board  
PCSS commands. When reset, the circuit pack executes a set of tests to  
detect the presence of any of the faults listed above. Detection of one of  
these errors during initialization causes the circuit pack to lock-up and  
appear insane to the system. See the repair procedure in Note (a).  
d. The circuit pack detects a program logic error. While no action is required,  
this error can lead to other errors against this circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-BD (TN2185 ISDN Trunk-Side BRI)  
3-1027  
e. The circuit pack cannot update and read back NPE/NCE memory. This  
error can be ignored, but may lead to other errors against this circuit pack.  
f. The TN2185 board notifies maintenance software that it has detected a  
parity error while accessing its dynamic RAM (that stores the board’s  
translation information and downloadable application firmware).  
Maintenance software resets the circuit pack.  
g. Unable to write LAN Translation RAM Error (internal memory access error).  
Translation RAM locations for the call connection attempt are not available,  
and one or more RAM locations are bad due to a translation RAM  
read-back error. Reset the circuit pack with the busyout board PCSS and  
reset board PCSS commands. If the Circuit Pack Restart Test (#594)  
passes, then the on-board circuitry is healthy. Retire the alarm with the  
test board PCSS long clear command. If the Circuit Pack Restart Test  
(#594) fails, replace the circuit pack.  
h. Frame overrun at Packet Bus interface. Due to an on-board fault or by  
faulty data received on one of the circuit pack’s external ports. If any of the  
ports on this circuit pack is alarmed, refer to the repair procedures for  
those maintenance objects. If this error persists, maintenance software  
removes the board from service; replace the circuit pack.  
i. The circuit pack is has problems transmitting/receiving data to/from the  
Packet Bus.  
1793  
Parity errors are detected when transmitting data to the  
Packet Bus.  
1794  
1795  
Packet Bus transmit buffers overflow.  
Circuit pack cannot find end of frame when transmitting to  
Packet Bus. Clear the alarm with: busyout board PCSS,  
reset board PCSS, test board PCSS long clear, release  
board PCSS. If the error recurs within 10 minutes, replace  
the circuit pack.  
2306  
Error in a received frame from the Packet Bus, most likely  
caused by a packet bus problem, but may be due to a  
circuit pack fault. An invalid Link Access Procedure Data  
(LAPD) frame error occurs if the frame contains a bad  
Cyclical Redundancy Check (CRC). If bus parity errors  
occur, run the LAN Receive Parity Error Counter Test (#595)  
to determine if the condition has cleared. Refer to the  
maintenance documentation to determine if the problem is  
isolated to this circuit pack or is caused by Packet Bus  
faults.  
j. Error Type (2305, 3330): A critical failure in the Circuit Pack’s Packet Bus  
interface. Possible causes include either a Packet Bus fault or an  
on-board fault, for example, the board received a bad CRC or invalid  
DLCI. The number of ISDN circuit packs displaying this error increases the  
probability of errors due to Packet Bus problems.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-BD (TN2185 ISDN Trunk-Side BRI)  
3-1028  
If there are no Packet Bus alarms, reset the circuit pack with the busyout  
board PCSS and reset board PCSS commands. If the Circuit Pack  
Restart Test (#594) passes, then the on-board circuitry is healthy. Retire  
the alarm with the test board PCSS long clear command. If the Circuit  
Pack Restart Test (#594) fails, replace the circuit pack.  
k. The SPE software detects an excessive number of up-link messages from  
the TN2185 board within a certain time period. To prevent the faulty board  
from flooding the switch with data, the switch software takes the board out  
of service and alarms it. The switch software also tells the Archangel to  
ignore up-link messages from the board.  
When the board is alarmed due to this error, the switch software  
periodically puts the board back in service and tells the Archangel to  
process up-link messages from the board. If the problem still exists, the  
software takes the circuit pack out of service again. If the circuit pack  
does not exhibit the problem for a certain time period, then maintenance  
software resolves the alarm and the circuit pack is left in service.  
l. The circuit pack received an inconsistent down-link message (a bad  
header, bad port number, bad data, bad subqualifier, or bad logical link)  
over the Control Channel.  
m. The board is receiving data from the bus faster than it can distribute the  
data to its endpoints, causing the FIFO RAM buffer to overflow. This error  
can occur occasionally due to the statistical sizing of the buffers. If it  
occurs frequently, it may indicate a LAPD parameter mismatch. LAPD  
should recover from this problem, but it may degrade the performance of  
the LAN bus.  
When this error is reported, maintenance reads and clears the board  
counter and logs the problem in the maintenance error log.  
n. Bad translation RAM detected, but the call continues by using another  
translation location. The circuit pack reports this error when it cannot  
update NPE/NCE memory and read it back. This error is not  
service-affecting and can be ignored, but can lead to other types of errors  
against this circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-BD (TN2185 ISDN Trunk-Side BRI)  
3-1029  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
When inspecting errors in the system, always investigate tests in the order listed  
below. By clearing error codes associated with the Control Channel Loop Around  
Tes t, for example, you may also clear errors generated from other tests in the  
testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Control Channel Loop-Around Test (#52)  
NPE/NCE Audit Test (#50)  
D/ND  
ND  
X
X
X
X
ND  
LAN Receive Parity Error Counter Test (#595)  
ND  
1. D = Destructive; ND = Nondestructive  
Control Channel Loop Around Test (#52)  
Refer to the repair procedure described in the ‘‘XXX-BD (Common Port Circuit  
Pack)’’ section.  
NPE /NCE Audit Test (#50)  
Refer to the repair procedure described in the ‘‘XXX-BD (Common Port Circuit  
Pack)’’ section.  
SAKI Sanity Test (#53)  
This test is destructive.  
Refer to the repair procedure described in the ‘‘XXX-BD (Common Port Circuit  
Pack)’’ section. This test is only run as a part of a reset board procedure.  
LAN Receive Parity Error Counter Test (#595)  
This test is nondestructive. The test reads and clears the circuit pack’s LAN  
Receive Parity Error Counter. This counter increments when it detects a parity  
error from the Packet Bus. These errors may indicate problems with a circuit  
pack, Packet Bus, or with another circuit pack on the bus. Use this test to verify  
the repair.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-BD (TN2185 ISDN Trunk-Side BRI)  
3-1030  
Table 3-455. TEST #595 LAN Receive Parity Error Counter Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received from the circuit pack within the  
allowable time period.  
1. If the test aborts repeatedly a maximum of 5 times, reset the circuit  
pack via the busyout board PCSS and reset board PCSS  
commands.  
2. If the test aborts again, replace the circuit pack.  
Could not allocate the necessary system resources to run this test.  
Internal system error.  
2100  
2012  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1-10  
FAIL  
The circuit pack is still detecting errors of this type. The error code  
indicates the value of the on-board error counter.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, verify the validity of the Packet Bus. Run the  
Packet Bus maintenance test with the test pkt P long command.  
3. If the Packet Bus test passes, check the validity of the circuit pack.  
Execute a test that involves data transmission onto the Packet Bus. For  
example, the test port PCSSpp command may use the connectivity  
tests of the BRI-PORT maintenance object. If the test fails, refer to the  
repair procedures; otherwise, proceed to the next step.  
4. Other circuit packs on the Packet Bus may be causing of the parity  
error. Use the display errors command to check the Error Log for  
alarmed other circuit packs. Resolve any alarms for other circuit packs  
as well. Rerun the LAN Receive Parity Error Counter Test (#595).  
PASS  
No errors detected.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1031  
TBRI-PT (TN2185  
ISDN Trunk-Side BRI Port)  
MO Name (in  
Alarm Log)  
1
Alarm Level  
MAJOR  
Initial Command to Run  
Full Name of MO  
TBRI-PT  
test port PCSS l r#  
test port PCSS l r#  
test port PCSS s r#  
TBRI-PT  
TBRI-PT  
TBRI-PT  
TBRI-PT  
TBRI-PT  
MINOR  
WARNING  
1. Where P is the port network number (1), C carrier designation (A, B, or C), and SS is the carrier  
slot address where the circuit pack is located (1, 2, and so forth).  
This document describes the port maintenance features of the DEFINITY® ISDN  
Trunk-side BRI board (TN2185). The circuit pack provides 8 S/T ISDN 2B+D  
ports which interface to either the central office or another PBX.  
The TN2185 circuit pack contains eight, 4-wire ports that interface to the network  
at the ISDN S/T reference point over two 64 Kb/s channels (B1 and B2) and over  
a 16Kb/s signaling (D) channel. The B1 and B2 channels can be simultaneously  
circuit switched, or individually packet switched. Only one channel per trunk can  
be packet switched due to Packet Processing Element (PPE) limitations. The D  
channel is either circuit switched or packet switched. Packet switching uses the  
PPE to combine all D channels into a single physical channel, which is then  
routed via the concentration highway to the Network Control Element (NCE) and  
then to the TDM bus. The circuit-switched connections have a Mu-law or A-law  
option for voice and operate as 64Kb/s clear data channels. The  
packet-switched channels support the LAPD protocol and conform with the  
CCITT Q.920 Recommendations for D-channel signaling.  
LEDs  
The three LEDs on the circuit pack’s faceplate indicate board status. When  
illuminated, the red LED indicates a board failure or a major or minor on-board  
alarm, the green LED indicates that testing is in progress, and the amber LED  
indicates that the board is in use.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1032  
S
PBX  
NT2  
NT2  
CO  
TE  
4-Wire  
S
V
PRI  
1
R
4-Wire  
U
Terminal  
Adapter  
2
U
T
LT  
NT1  
TE  
3
T
NT  
2-Wire  
NT  
4-Wire  
LT  
NT1  
4
NT  
NT  
4-Wire  
NT2  
2-Wire  
LT  
NT2  
S/T  
U
NT  
2-Wire  
S/T  
NT1  
T
TE  
NT  
2-Wire  
TE  
TE  
5
PBX  
cydfisdn RPY 072397  
ISDN Interface Reference Points  
Figure 3-43. Integrated Trunk-Side BRI, ISDN Interface Reference points  
ISDN Interface Reference Point definitions:  
LT  
V
Logical Terminal  
Primary Rate user/network (asymmetrical) trunk interface. The ECS  
is capable of acting as the user or as the network side of this 1.544 -  
or 2.048-Mbps interface.  
R
Interface between Terminal Equipment and Network Termination  
Basic Rate network-side 4-wire line interface  
S
S/T  
T
4-wire Basic Rate connection to a Network Termination1.  
4-wire Basic Rate interface to a Network Termination.2  
TermDinoawlnlEoaqdufirpommWenwtw.Somanuals.com. All Manuals Search And Download.  
TE  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1033  
U
1
2
3
4
5
Basic Rate network-side 2-wire line interface.  
TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side)  
TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side)  
2-Wire ISDN-BRI circuit pack  
TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side)  
TN2185 ISDN-BRI 4-Wire S Interface (Trunk Side)  
1. Network Termination 2 (NT2), that terminates Layer 1 and higher layers. PBXs, LANs,  
and terminal controllers typically provide NT2 functionality including protocol  
handling and multiplexing for Layers 2 and 3.  
2. Network Termination 1 (NT1), that terminates Layer 1 and monitors maintenance,  
performance, timing, power transfer, multiplexing, and multi-drop termination with  
contention resolution.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-456. TBRI-PT Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test Port UCSSPP sh r 1  
1 (a)  
Level 1 Status Test  
(#1242)  
MINOR  
OFF  
2
129  
257(b)  
513 (c)  
46222  
XMIT FIFO  
Overflow  
MINOR  
MINOR  
MINOR  
ON  
ON  
OFF  
514 (d)  
769 (e)  
XMIT FIFO  
Overflow (TDM)  
Traffic  
Hyperactivity  
1025 (f)  
1281 (g)  
NPE Crosstalk Test  
(#617)  
MINOR  
MINOR  
MINOR  
ON  
1537 (h)  
1538 (i)  
46210  
CRC error  
(D-Channel)  
OFF  
OFF  
CRC error (TDM  
D-Channel)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1034  
Table 3-456. TBRI-PT Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1793 (j)  
BRI Port Local TDM  
Looparound Test  
(#619)  
MINOR  
ON  
2049 (k)  
2305 (l)  
MINOR  
MINOR  
OFF  
OFF  
Layer 3 Query  
(#1243)  
3073 (m)  
3585 (n)  
Slip Query Test  
(#1244)  
MINOR  
OFF  
ON  
Receive FIFO  
Overflow (TDM  
D-Channel)  
Log Only  
3586 (o)  
3587 (p)  
3588 (q)  
3589 (r)  
3590 (s)  
3591 (t)  
3592 (u)  
46223  
46211  
3841 to  
3942 (v)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. The far-end switch changed the ISDN service state. This may be a temporary condition.  
Notes:  
a. Loss of continuity of Layer 1 to the far-end. It is assumed that Layer 1  
remains active, even when both B-Channels are idle.  
This test determines whether Layer 1 is active or not. If Layer 1 is not  
active, the test attempts to activate it. If Layer 1 cannot be activated, the  
port is taken out of service, and the test fails.  
b. The D-Channel failed at Layer 2. Expiration of this timer indicates that  
attempts to bring the failed link back into service have not succeeded and  
some recovery actions should be taken on the associated B-Channels.  
Upon expiration, associated in-service B-channels are put in the  
out-of-service/far end state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1035  
c. Error Type (513): On-board hardware failure. The FIFO RAM buffers have  
overflowed, indicating a hardware problem.  
d. Error Type (514): Transmit FIFO Overflow - This error indicates that the  
circuit pack is having problems transmitting data to the TDM D-Channel.  
This error only occurs only a system that switches the packet  
implementation of the D-channel over the TDM Bus. This error indicates an  
on board problem related to the packet implementation of the D-Channel.  
e. Error Type (769): The port is generating too many uplinks. The link is being  
suspended.  
f. Error Type (1025): An expired timer has created an unexpected event. The  
timer could be any of the following:  
Timer  
T3031  
T3032  
T305  
T3081  
T3082  
TL3  
Event  
ISDN T3031 timeout  
ISDN T3032 timeout  
ISDN T305 timeout  
ISDN T3081 timeout  
ISDN T3082 timeout  
Status Inquiry  
T304  
T310  
T313  
Setup ACK  
Call Proceeding Receive  
Connect SEND  
g. Error Type (1281): This error occurs when the NPE Crosstalk Test (#617)  
has failed. The test will be repeated every 15 minutes until it passes.  
Follow normal trouble shooting procedures for NPE Crosstalk Test (#617).  
If this does not fix the problem, follow normal escalation procedures.  
h. Error Type (1537): The board received a bad Cyclical Redundancy Check  
(CRC) over the D-Channel. This error is reported on a per-port basis.  
When the CRC errors exceed 5 within 15 minutes, the port is taken out of  
service for 5 seconds. If 5 more CRC errors are received within 15 minutes  
of the first set of 5 errors, the port is taken out of service for 1 minute. If 5  
more CRC errors are received within 15 minutes of the previous 5, the port  
is taken out of service for 15 minutes.  
This error is most likely due to a problem with backplane wiring, a noise  
source, or no termination (an open circuit). It usually does not indicate a  
problem with the circuit pack.  
1. Check the backplane wiring.  
2. If the problem persists escalate the problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1036  
i. Error Type (1538): This error occurs when a frame with a bad CRC is  
received by the BRI trunk board. This error only occurs on a system that  
switches the packet implementation of the D-channel over the TDM bus.  
This error indicates an off board problem related to the packet  
implementation of the TDM D-Channel.  
j. Error Type (1793): The BRI Port Local TDM Loop Around Test (#619)  
failed. Run the Long Test Sequence paying particular attention to the  
results of the BRI TDM Port Loop Test (#619).  
k. Error Type (2049): The Layer 2 Link Query failed. The test is repeated  
every 15 minutes until it passes.  
l. Error Type (2305): The Remote Layer 3 Query failed. The test is repeated  
every 15 minutes until it passes.  
m. Error Type (3073): A frame of information had to be repeated or deleted.  
Slips usually occur when the received bit rate is not synchronized with the  
TDM Bus clock.  
n. Error Type (3585): The circuit pack detected an overflow of its receive  
buffers. This error occurs only a system that switches the packet  
implementation of the D-Channel over the TDM bus. This error indicates  
an on board problem related to the packet implementation of the TDM  
D-Channel.  
o. Error Type (3586): Each port can support up to three Terminal Endpoint  
Identifiers (TEIs). Each channel on the port can request a TEI assignment  
from the switch if it supports ISDN-BRI TEI assignment procedures. If  
switch services gets a request for a fourth TEI on a port, it reports this  
event to maintenance software and initiates TEI check procedures on the  
port. Check to see if the correct number of channels are administered for  
this port.  
The user side supports automatic TEI assignment by the network. Both  
fixed and automatic TEI assignment are supported on the network side.  
p. Error Type (3587)Service Profiler IDentifier (SPID) value is invalid or is a  
duplicate of another SPID that is already initialized at Layer 3 on the port.  
SPIDs are not used on the TN2185 circuit pack. However there will be  
related events.  
q. Error Type (3588): The board receives D-Channel data from the bus faster  
than it can process the data. The FIFO RAM buffers overflowed. This error  
occurs occasionally due to the statistical sizing of the buffers; however,  
frequent occurrences may indicate a LAPD parameter mismatch between  
the two endpoints of a packet-switched connection. Run the Long Test  
Sequence paying particular attention to the results of the Receive FIFO  
Overflow Test (#625).  
r. Error Type (3589): The BRI Port Local LAN Loop Around Test (#618) failed.  
Run the Long Test Sequence and pay particular attention to the results of  
Test #618.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1037  
s. Error Type (3590): An activated BRI port receives a frame containing a  
DLCI over a D-Channel for which it does not have a translation. This error  
normally indicates an off-board problem related to a state mismatch  
between the far-end and the switch. This error is logged only.  
t. Error Type (3591): The port is generating too many uplinks and is taken out  
of service.  
u. Error Types (3841-3942): Table 3-457 contains the received ISDN cause  
values for Errors 3841-3942 that are recorded in the hardware error logs.  
Unless otherwise stated, the cause values are D-Channel events. The aux  
data field shows which port caused the error.  
Table 3-457. Cause Values for Error 3841-3942  
Value  
2
Type of Problem  
admin  
Meaning  
No route to specific transit network  
No route to destination (or Germany bcap not imp)  
Channel unacceptable  
3
admin  
6
admin  
18  
38  
50  
52  
54  
62  
63  
65  
66  
69  
70  
79  
88  
102  
switch problems  
switch problems  
subscription  
admin  
No user responding  
Network failure  
Requested facility not subscribed  
Outgoing calls barred  
admin  
Incoming calls barred  
subscription  
admin/sub  
admin/sub  
admin/sub  
admin/sub  
admin/sub  
admin  
Service not authorized  
Service/option not available  
Bearer capability not implemented  
Channel type not implemented  
Requested facility not implemented  
Only restricted digital BC available  
Service/option not implemented  
Incompatible destination  
admin  
switch problems  
Recovery on timer expired  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1038  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
When inspecting errors in the system, always investigate tests in the order listed  
below. By clearing error codes associated with the Control Channel Loop Around  
Tes t, for example, you may also clear errors generated from other tests in the  
testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
BRI Local LAN Port Loop Around Test (#618)  
BRI TDM Port Loop Around Test (#619)  
L1 State Query Test (#1242)  
D/ND  
D
X
X
X
X
X
X
X
X
X
D
X
D
CRC Error Counter Test (#623)  
Receive FIFO Overflow Test (#625)  
Layer 3 Query Test (#1243)  
ND  
ND  
ND  
ND  
ND  
D
Slip Query Test (#1244)  
X
X
Clear Error Counters Test (#270)  
NPE Crosstalk Test (#617)  
1. D = Destructive; ND = Nondestructive  
Clear Error Counters Test (#270)  
This test is nondestructive. This test clears the various error counters associated  
with each TBRI-PT. This test passes if Maintenance is able to successfully send  
the downlink messages; otherwise, the test aborts.  
Table 3-458. TEST #270 Clear Error Counters  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Any  
ABORT  
PASS  
Maintenance could not send the downlink message.  
The message to clear the error counters of the TBRI-PT maintenance  
object has been sent.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1039  
NPE Crosstalk Test (#617)  
This test is conditionally destructive.  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain and provides conferencing functions on  
a per-port basis. The NPECrosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is part of a port’s Long Test Sequence and takes  
approximately 20 to 30 seconds to complete. Crosstalk testing is performed on  
both B-channels (B1 and B2) associated with a BRI port. If this test fails on either  
channel, any channel connected to the port is taken out-of-service. The test  
aborts if the port and its associated channels are not in the idle state.  
Table 3-459. TEST #617 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the station extension or trunk group/member number of the port.  
Use the status bri-port PCSSpp command to determine the service state  
of the port. If the service state indicates that the port is in use, then the port  
is unavailable for certain tests. Wait until the port is idle before retesting.  
1. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
1005  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use the status bri-port  
command to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
This test is not valid for this type of translation. Ports administered as  
“ASAI” or “ADJK” cannot run this test, because the B channels associated  
with the port are not used by ASAI or Lucent Adjunct Links. This is a normal  
condition.  
2012  
2100  
ABORT  
ABORT  
Internal system error  
Could not allocate the necessary resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1040  
Table 3-459. TEST #617 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1, 2  
FAIL  
The NPE of the tested port was found to be transmitting in error, causing  
noisy and unreliable connections. Error code 1 indicates that the NPE  
Crosstalk Test failed on Channel B1. Error code 2 indicates that the NPE  
Crosstalk Test failed on Channel B2.  
1. Replace circuit pack.  
PASS  
The port is correctly using its allocated time slots.  
1. To be sure that this is not an intermittent problem, repeat this test a  
maximum of 10 times to ensure it continues to pass.  
2. If complaints still exist, examine the connections and wiring.  
BRI Port Local LAN Looparound Test (#618)  
This test is destructive.  
This test checks the connectivity of the BRI port across the LAN bus. Because  
this test is destructive, run this test only if the port is out-of-service.  
Failures of this test indicate either on-board faults associated with theTBRI-PT  
hardware on the circuit pack or problems with the LAN Bus, which is used to form  
connectivity between the switch and the TBRI-PT.  
If the port is in a state other than out-of-service, the BRI Port Local LAN  
Looparound Test will abort. If the port is out-of-service, then the port is put into a  
local looparound mode and the following test is executed.  
A looparound test is performed across the bus for the D-Channel. The switch  
sends data over a packet connection, which is looped back by the BRI port  
(D-Channel) and received back by the switch. The test passes if the packet  
connection can be established and the transmitted data is received unaltered.  
The test aborts if the bus is alarmed in the Processor Port Network (or the port  
network in which that circuit pack resides) or if the Packet Interface is  
out-of-service. The test fails due to either on-board faults associated with the BRI  
port hardware on the circuit pack or problems with the bus.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1041  
Table 3-460. TEST #618 BRI Port Local LAN Loop Around  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The port is not out-of-service.  
1015  
ABORT  
1. Use the status bri-port PCSSpp command to determine the status of  
the port.  
2. If it is in use, wait until it is idle, and then use the busyout port  
PCSSpp command to place it in the out-of-service state and repeat  
this test.  
!
CAUTION:  
Since the busyout command is destructive, execution of this  
command prior to the port being idle causes all calls  
associated with the BRI port to be torn down.  
1141  
ABORT  
The PKT-INT is out-of-service.  
1. Follow the repair procedures for the PKT-INT.  
2. Run the test port long PCSSpp command and verify the repair by  
viewing the results of the BRI Port Local LAN Looparound Test (#618).  
2012  
2100  
ABORT  
FAIL  
Internal System Error.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The Looparound Test failed.  
1. If the test fails repeatedly, attempt to reset the circuit pack with the  
busyout board PCSS and the reset board PCSS commands if the  
other ports on the board are not in use.  
2. If the test fails again, execute test pkt P.  
3. If the tests in Step 2 pass, the problem is local to the BRI board.  
Replace the trunk circuit pack.  
PASS  
The BRI Port Local LAN Looparound Test passed.  
BRI Port Local TDM Looparound Test (#619)  
This test is conditionally destructive.  
This test verifies the connectivity of a BRI port across the TDM Bus. It aborts if  
calls associated with the port are in progress. Failure of this test indicates an  
on-board fault associated with the port hardware on the circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1042  
This Looparound Test runs the following individual tests on the two B-channels  
(B1 and B2) associated with the port:  
■
■
■
■
A Looparound Test across the TDM Bus for B1.  
A Conference Circuit Test for B1.  
A Looparound Test across the TDM Bus for B2.  
A Conference Circuit Test for B2.  
The tests are run in the above order. If one fails, the remaining tests in the  
sequence are not executed, and the maintenance software returns an error code.  
Table 3-461. TEST #619 BRI Port Local TDM Loop Around  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
The system resources required to run this test are not available. The port  
may be busy with a valid call. Use the display port PCSSpp command to  
determine the trunk group/member number of the port. Use the status  
bri-port PCSSpp command to determine the service state of the port. If the  
service state indicates that the port is in use, then the port is unavailable for  
certain tests. Wait until the port is idle before retesting.  
1. If the port is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1002  
1003  
ABORT  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS to diagnose any active TDM Bus  
errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
The system could not allocate a tone receiver for the test.  
1. Look for TTR-LEV errors in the Error Log and if present, refer to  
TTR-LEV.  
2. Look for TONE-PT errors in the Error Log and if present, refer to  
TONE-PT.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port has been seized by a user for a valid call. Use the status trunk  
command for the trunks associated with this port and determine when the  
port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1043  
Table 3-461. TEST #619 BRI Port Local TDM Loop Around — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1005  
ABORT  
This test is not valid for this type of translation. Ports administered as ASAI  
or ADJK cannot run this test because the B channels associated with the  
port are not used by ASAI or Lucent Adjunct Links. This is a normal  
condition.  
2000  
ABORT  
Response to the test was not received from the BRI-LINE circuit pack  
within the allowable time period.  
1. If this result occurs repeatedly, attempt to reset the circuit pack with the  
busyout board PCSS and the reset board PCSS commands if the  
other ports on the board are not in use.  
2. If this result occurs again, replace the circuit pack.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not make the conference connection for the test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The TDM Looparound failed on one of the channels.  
2103  
1, 2  
ABORT  
FAIL  
■ Error Code 1 — TDM Loop Around Test failed on B1.  
■ Error Code 2 — TDM Loop Around Test failed on B2.  
The Conference Circuit Test failed on a B-channel.  
■ Error Code 7 — test failed on B1  
7, 8  
FAIL  
■ Error Code 8 — test failed on B2.  
1. If the test fails repeatedly, attempt to reset the circuit pack with the  
busyout board PCSS and the reset board PCSS commands if the  
other ports on the board are not in use.  
2. If the test fails again, replace the circuit pack.  
The BRI Port Local TDM Loop Around Test passed.  
PASS  
CRC Error Counter Test (#623)  
This test is non-destructive. This test reads the BRI port’s CRC error counters that  
are maintained on the BRI circuit pack. The Cyclic Redundancy Check (CRC) is  
a means of error detection used to determine the integrity of data frame contents.  
The CRC error counter is incremented by the circuit pack when it detects a CRC  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1044  
error. The test passes if the value of the counter is 0 (that is, the error is cleared).  
If the counter is non-zero, the test fails, and the value of the counter is displayed  
in the Error Codefield.  
Table 3-462. TEST #623 CRC Error Counter Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ANY  
FAIL  
This error occurs when a frame with a bad CRC is received over the  
D-Channel by the BRI board. This error is reported on a per-port basis  
when the counter goes over the threshold. This error is most likely due to a  
problem with the wiring or interference on the wiring caused by a noise  
source or no termination. It usually does not indicate a problem with the  
circuit pack.  
PASS  
The CRC error counter was read correctly and has a value of 0.  
Receive FIFO Overflow Error  
Counter Test (#625)  
This test is nondestructive. This test reads and clears the BRI port’s Receive FIFO  
Overflow error counter maintained on the TBRI-BD circuit pack. This counter is  
incremented by the circuit pack when it detects an overflow of its receive buffers.  
The test passes if the value of the counter is 0 (that is, the error is cleared). If the  
counter is non-zero, the test fails, and the value of the counter is displayed in the  
Error Code field.  
This error can occur if signaling frames are being received from the Packet Bus  
at a rate sufficient to overflow the receive buffers on the circuit pack for a port OR  
if a hardware fault is causing the receive buffers not to be emptied properly by  
the circuit pack. This test is useful for verifying the repair of the problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1045  
Table 3-463. TEST #625 Receive FIFO Overflow  
Error Counter Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received from the circuit pack within the  
allowable time period.  
1. If the test aborts repeatedly a maximum of 5 times, reset the circuit  
pack with the busyout board PCSS and reset board PCSS  
commands.  
2. If the test aborts again, replace the circuit pack.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
value  
FAIL  
The TBRI-BD circuit pack is still detecting errors of this type. The Error  
Code field contains the value of this counter.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, run the Long Test Sequence and pay  
particular attention to the Looparound Tests (#618 and #619). See the  
repair procedures for the executed test if it fails. Otherwise, go to the  
next step.  
3. Replace the circuit pack.  
PASS  
The Receive FIFO Overflow error counter was read correctly and has a  
value of 0.  
Level 1 Status Inquiry Test (#1242)  
This test is nondestructive. This test determines the state of the transmission  
facility of a BRI port at the Level 1 (L1) physical layer: Activated, Pending  
Activation, or Deactivated.  
The Activated state is the correct state for an ISDN-BRI port. In this state the L1  
interface can send and receive synchronized signals. This test passes if the state  
of L1 is Activated. This test also passes if software has taken this port out of  
service. See the description of the L1 “Deactivated State” below for more details.  
The Pending Activation state indicates a problem with the channels, the wiring, or  
the TBRI-BD circuit pack. When in this state, the Level 1 interface is either not  
receiving any L1 framing from the channel, or it is communicating with the  
channel or adjunct but cannot transition to the Activated state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1046  
The Deactivated state indicates a problem with the TBRI-BD circuit pack. When  
in this state, the Level 1 interface is not active, and an idle signal is transmitted to  
the channels or that Layer 1 was deactivated by the switch. When an TBRI-PT  
port is placed in the out-of-service state, Level 1 is also put into the Deactivated  
state. This could be due either to the system detecting a fault with the port or to a  
busyout port PCSSpp request.  
Table 3-464. TEST #1242 Level 1 Status Inquiry  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1187  
ABORT  
The board or port may have been busied out.  
1. Look in the Error Log for Error Type 18 (port busied out) for this port  
and TBRI-BD (board busied out). If this error type is present for  
TBRI-PT only, then release the port with the release port pp command  
and run the test again. If the error is present for both TBRI-BD and  
TBRI-PORT, then release the board with the release board PCSS  
command and run the test again.  
NOTE:  
When you release a port, you release all ports associated with it. If  
certain ports still need to be busied out, use the release port  
PCSSpp command to busy them out.  
2. Make sure the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
ABORT  
Response to the test was not received from the circuit pack within the  
allowable time period.  
1. If the test aborts repeatedly a maximum of 5 times, reset the circuit  
pack with the busyout board PCSS and reset board PCSS  
commands.  
2. If the test aborts again, replace the circuit pack.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1047  
Table 3-464. TEST #1242 Level 1 Status Inquiry — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
FAIL  
Received a status of Level 1 Pending Activation. U interface down  
indicating a problem with a connection between the switch and the NT1, a  
2- to 4-wire converter that is used to connect 4-wire terminals to a 2-wire  
TN2198 or TN2185 circuit pack.  
1. Verify that the connections between the switch and the NT1 are good.  
Verify that the NT1 has power.  
2. Execute the test port PCSSpp command and review the results of the  
Level 1 Status Inquiry Test to verify the repair. If this test still fails,  
proceed to Step 3.  
3. Follow the manufacturers repair procedures for the NT1. Then execute  
the test port PCSSpp command and review the results of the Level 1  
Status Inquiry Test to verify repair.  
2
FAIL  
Received a status of Level 1 Pending Activation. U interface up, S/T  
interface down, which indicates a problem with the NT1 or the wiring  
between the NT1 and the BRI endpoint (S/T interface).  
1. Execute the test port PCSSpp command and review the results of the  
Level 1 Status Inquiry test to verify the repair. If this test still fails,  
proceed to Step 2.  
2. Follow the manufacturer-recommended repair procedures for the NT1.  
Then execute the test port PCSSpp command and review the results  
of the Level 1 Status Inquiry test to verify repair.  
3
FAIL  
Received a status of Level 1 Deactivated; the port is out-of-service.  
1. Issue the status bri-port PCSSpp command to verify that the service  
state of the port is out-of-service. If the service state of the port is not  
out-of-service, proceed to Step 2.  
2. If the port has been placed out-of-service with the busyout port  
PCSSpp command, try releasing the port by executing the release  
port PCSSpp command. Then issue the test port long PCSSpp  
command and review the results of Level 1 Status Inquiry test. If this  
test still fails, proceed to Step 3.  
3. After executing the test port long PCSSpp command, review the  
results of all the tests. Follow the repair procedures for any tests that  
fail. Verify repair of the problem by executing the test port PCSSpp  
command and by determining that the Level 1 Status test passes.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1048  
Table 3-464. TEST #1242 Level 1 Status Inquiry — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
4
FAIL  
Received a status of Level 1 Pending Activation, the NT1 has a loss of  
power indicating a problem with the NT1.  
1. Follow the manufacturer-recommended repair procedures for the NT1.  
2. Execute the test port PCSSpp command and review the results of the  
Level 1 Status Inquiry test to verify the repair.  
PASS  
This test indicates that Level 1 is activated or that software has taken the  
port out of service.  
Layer 3 Query Test (#1243)  
This test is nondestructive. This test is used to check the application layer  
communications across the in-service ISDN D-Channel. The test passes if a  
status enquiry message was successfully sent, fails if the signaling link is down,  
and aborts if a query is already running or there is an internal error.  
Table 3-465. TEST #1243 Layer 3 Query  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Test is already running.  
1019  
ABORT  
ABORT  
1113  
The signaling link is down.  
1. Use the test port PCSSpp long command to clear any errors which  
prevent establishment of the signaling link.  
2. Examine the results of Test #626, which is executed with the  
command. If this test aborts or fails, follow the repair procedure for the  
Signaling Link Status Test.  
1141  
ABORT  
The PKT-INT is out-of-service.  
1. Consult the repair procedure for PKT-INT.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1049  
Table 3-465. TEST #1243 Layer 3 Query — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1187  
ABORT  
The circuit pack or port may have been busied out by a technician.  
1. Look in the Error Log for Error Type 18 (busied out ) for TBRI-BD or  
TBRI-PT.  
a. If this error type is present for TBRI-PT, then release the port with  
the release port PCSSpp command, and run the test again.  
b. If the error is present for both TBRI-BD and TBRI-PT, then release  
the circuit pack with the release board PPCSS command and run  
the test again.  
NOTE:  
When you release the circuit pack, you release all ports associated  
with it. If certain ports still need to be busied out, use the release  
port PCSSpp command to busy them out.  
2. Make sure the terminal is connected.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The switch has successfully sent a Status Enquiry message.  
PASS  
Slip Query Test (#1244)  
This test is non-destructive. Slips occur when the transmitter and receiver are not  
running at precisely the same clock rate. The Slip Alarm Inquiry Test polls the  
total number of slips that have occurred on a link.  
When the TN2185 circuit pack detects a slip condition, maintenance software  
initiates the Slip Alarm Inquiry Test to query the slip counters on the TN2185  
circuit pack and total the slip counts in the maintenance software.  
If the slip count is over the threshold, a Minor alarm is raised against the TN2185  
circuit pack, leaving all ports of the TN2185 circuit pack in the in-service state. If  
the TN2185 circuit pack is used to supply the system synchronization source, the  
MINOR alarm will initiate a synchronization source switch. See TDM-BUS and  
SYNC for additional information.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-PT (TN2185 ISDN Trunk-Side BRI Port)  
3-1050  
Table 3-466. TEST #1244 Slip Alarm Inquiry Test  
Error  
Code  
Test Result  
Description/ Recommendation  
ABORT  
Internal System Error  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period. If Error Type 1538 is present in the Error Log, follow the  
maintenance strategy recommended for this error type.  
2100  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
1 to 88  
The circuit pack and the remote endpoint are not synchronized to the  
same clock rate, which has generated the Slip alarm. The error code  
equals the number of slips detected by the TN2185 circuit pack since  
the last Slip Alarm Inquiry Test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the circuit pack is a TN2185, enter the list measurement ds1-log  
PCSS command to read the error seconds measurement.  
3. Verify that both endpoints of the DS1 link are administered using the  
same signaling mode, framing mode, and line coding.  
4. Check the physical connections of DS1 Interface circuit packs and  
cable.  
5. Replace the local DS1 Interface circuit pack and repeat the test.  
6. Contact T1 Network Service to diagnose the remote DS1 endpoint.  
No Slip alarm is detected on the DS1 Interface circuit pack.  
PASS  
0
NO BOARD The DS1 Interface circuit pack is not administered.  
1. Administer the DS1 Interface circuit pack by issuing the add ds1  
PCSS command.  
2. Run the test again.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-TRK (TN2185 ISDN Trunk-Side BRI)  
3-1051  
TBRI-TRK (TN2185  
ISDN Trunk-Side BRI)  
MO Name (in  
Alarm Log)  
1
Alarm Level  
Initial Command to Run  
Full Name of MO  
2
3
TBRI-TRK  
MAJOR  
test trunk PCSSpp l  
test trunk PCSSpp l  
test trunk PCSSpp sh  
MO_TBRI_TRK  
MO_TBRI_TRK  
MO_TBRI_TRK  
TBRI-TRK  
TBRI-TRK  
MINOR  
WARNING  
1. Where P is the port network number (1); C is the carrier designation (for example, A, B, or C);  
and SS is the address of the slot in the carrier where the circuit pack is located (for example, 01,  
02, and so forth).  
2. For additional repair information, also see TBRI-BD and TBRI-PT Maintenance Object  
documentation.  
3. A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by the set  
options command and that at least 75 percent of the trunks in this trunk group are alarmed.  
The TN2185 circuit pack contains eight, 4-wire ports that interface to the network  
at the ISDN S/T reference point over two 64 Kb/s channels (B1 and B2) and over  
a 16Kb/s signaling (D) channel. The B1 and B2 channels can be simultaneously  
circuit switched, or individually packet switched. Only one channel per trunk can  
be packet switched due to Packet Processing Element (PPE) limitations. The D  
channel is either circuit switched or packet switched. Packet switching uses the  
PPE to combine all D channels into a single physical channel, which is then  
routed via the concentration highway to the Network Control Element (NCE) and  
then to the TDM bus. The circuit-switched connections have a Mu-law or A-law  
option for voice and operate as 64Kb/s clear data channels. The  
packet-switched channels support the LAPD protocol and conform with the  
CCITT Q.920 Recommendations for D-channel signaling.  
LEDs  
The three LEDs on the circuit pack’s faceplate indicate board status. When  
illuminated, the red LED indicates a board failure or a major or minor on-board  
alarm, the green LED indicates that testing is in progress, and the amber LED  
indicates that the board is in use.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-TRK (TN2185 ISDN Trunk-Side BRI)  
3-1052  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-467. TBRI-TRK Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test Port UCSSPP sh r 1  
513 (a)  
Service State Audit  
(Test #256)  
WARNING  
OFF  
1793 (b)  
3073 (c)  
8, 9  
WARNING  
OFF  
OFF  
Service State Audit  
(Test #256)  
3585 (d)  
3841 (e)  
WARNING  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. The far-end has reported that this channel is not administered. The trunks  
are placed in the out-of-service state.  
b. The Signaling link is down. See the following Aux Data explanation:  
— Aux data 8 indicates the Signaling Link is down.  
— Aux data 9 indicates the Port is out of service.  
c. The Service State Audit failed. The test will be run every 15 minutes until it  
passes.  
d. Unexpected Restart message; this error causes no action and is logged  
only.  
e. B-Channel Rejection Event; this action causes the Service State Audit, the  
Call State Audit, and the Test Call Audit to be executed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-TRK (TN2185 ISDN Trunk-Side BRI)  
3-1053  
System Technician-Demanded Tests:  
Descriptions and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Services State Test, for example, you may also clear errors generated from other  
tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
Signaling Link State Check Test (#1251)  
Service State Audit Test (#256)  
Call State Audit Test (#257)  
D/ND  
ND  
X
X
X
X
X
X
X
ND  
ND  
ISDN Test Call Test (#258)  
ND  
1. Destructive; ND = Nondestructive  
Signaling Link State (#1251)  
This test is nondestructive. This test checks the current state of the signaling link.  
The test looks at the board-level translations, checks that the board is physically  
inserted, gets the state of the D-Channel and service state of the port.  
The test passes if the signaling link (D-Channel) is connected and operating  
normally. The test fails if the board is not installed, the signaling link is  
disconnected, or if the port is out of service. The test aborts otherwise.  
Table 3-468. TEST #1251 Signaling Link State Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
The test is disabled.  
1018  
1. Enable the test by entering enable test #1251.  
The signaling link is in a transitional state.  
1114  
8
ABORT  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The signaling link is down.  
1. Consult the procedures for the TBRI-PT maintenance object.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-TRK (TN2185 ISDN Trunk-Side BRI)  
3-1054  
Table 3-468. TEST #1251 Signaling Link State Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The port is out of service.  
9
FAIL  
1. Return the port too an in service state.  
PASS  
The signaling link is connected and operating normally.  
Service State Audit (#256)  
This test is nondestructive. This test performs a service state audit on an ISDN  
B-Channel. The test passes if Call Processing informs Maintenance that the  
Restart message was transmitted successfully, or if the B-Channel was busy and  
could not send the message.  
The test fails if the board is not inserted or translated properly, or if a reply is not  
received within a certain amount of time.  
The test aborts if the signaling link is disconnected, if a message is already  
outstanding, or if the necessary resources could not be allocated. Maintenance  
will take no action if the test aborts.  
To investigate the service state of the TN2185 ISDN Trunk-Side BRI Channel,  
issue the status trunk trunk-group/trunk-member command.  
Table 3-469. TEST #256 Service State Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be on a valid call. Use status trunk to determine when the trunk is  
available for testing.  
1. Check the results of Test #1251 (Signaling Link State Check).  
The test is disabled.  
1018  
1113  
ABORT  
ABORT  
1. Enable maintenance by entering y in the Maintenance Tests?  
field on page 2 of the change trunk-group form.  
The signaling link has failed, so the system cannot send any messages on  
behalf of this trunk.  
1. Check the results of Test #1251 (Signaling Link State Test ).  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-TRK (TN2185 ISDN Trunk-Side BRI)  
3-1055  
Table 3-469. TEST #256 Service State Audit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The signaling link is in a transitional state.  
1114  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1116  
1117  
ABORT  
ABORT  
The trunk is not in a service state which is appropriate for running the test.  
This test is only performed in the OOS/FE state.  
A service state audit message is outstanding.  
1. Wait two minutes and then try again.  
2100  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal System Error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
Wait 4 minutes and then check the Error Log for any new errors of type  
3073. If there are none, then both sides of the ISDN connection agree on  
the service state; the negotiation succeeded. If there is a new 3073 error,  
then the negotiation failed (the far-end switch twice failed to respond within  
2 minutes). The switch automatically retries every 15 minutes. If the trunk  
was initially in-service, it is now placed in the maintenance/far-end state.  
Incoming calls will be accepted, but no outgoing calls can be originated. If  
an incoming call is presented, another Service State Audit is immediately  
performed in an attempt to put the TN2185 ISDN Trunk-Side BRI Channel  
in the proper state.  
Call State Audit Test (#257)  
This test is nondestructive. This test performs a call state audit on an ISDN  
B-Channel, and upon successful completion, guarantees that both sides of the  
interface are in a consistent call state for connections using the B-Channel. The  
test can be helpful when trying to clear a hung call. If the internal call state data  
to the near-end switch is different from that of the far-end switch, the call will be  
torn down.  
The test passes if the audit is successful.  
The test fails if the board is not inserted, there is an internal system error, or if a  
reply was not received within a certain amount of time.  
The test aborts if the signaling link is disconnected, the request is already active,  
or if the B-Channel is in an Out-Of-Service state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-TRK (TN2185 ISDN Trunk-Side BRI)  
3-1056  
Table 3-470. TEST #257 Call State Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1018  
ABORT  
The test is disabled.  
1. Enable the test by entering y in the Maintenance Tests?field on  
page 2 of the change trunk-group form.  
1019  
1113  
ABORT  
ABORT  
An audit is already in progress.  
1. Wait two minutes and try again.  
The signaling link has failed, so the system cannot send any messages on  
behalf of this trunk.  
1. Check the results of Test #1251 (Signaling Link State Check).  
The signaling link is in a transitional state.  
1114  
1116  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The trunk is in an out-of-service ISDN service state.  
1. A call cannot be present if the trunk is in an ISDN out-of-service state,  
so a call state audit would be inappropriate. No action necessary.  
(Use the status trunk command.)  
2100  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The audit passed successfully.  
PASS  
ISDN Test Call Test (#258)  
This test performs a far-end loop around to a far-end switch over an ISDN trunk.  
The trunk’s service state must be in-service, maint-NE, or out-of-service/NE, and  
no call can be active on the trunk.  
A test call connection is established to a far-end switch over the ISDN trunk to be  
tested. The digital port on a TN711D Maintenance/Test circuit pack generates a  
test-pattern bit stream which is sent to the far-end switch and echoed back. The  
received pattern is then compared to the sent pattern and checked for errors that  
indicate a loss of integrity on the communications path.  
If a test call is running when scheduled maintenance starts, the green LED is  
turned off. To determine if a test call is still running, use the list isdn-testcall and  
status isdn-testcall commands. A lit yellow LED on the Maintenance/Test circuit  
pack also indicates that a test call is running.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-TRK (TN2185 ISDN Trunk-Side BRI)  
3-1057  
There are two methods available to place an outgoing ISDN Trunk-side BRI trunk  
test call:  
1. The test call connection is established over the TDM Bus of the transmit  
and receive sides of the ISDN Trunk-side BRI trunk to a data channel.  
2. The test call connection is established over the TDM Bus of the transmit  
and receive sides of the ISDN Trunk-side BRI trunk to a digital trunk testing  
port on the Processor circuit pack. The Processor Digital Port generates a  
pseudo bit stream.  
A test is run periodically to check if the call is hung. If so, it gracefully tears down  
the call to release the resources.  
Synchronous Commands  
You can demand a synchronous outgoing test call by using the following  
maintenance commands:  
■
■
■
test trunk trunk-group-no/member-no long [repeat number]  
test board board-location long [repeat number]  
test port port-location long [repeat number]  
Whenever a circuit translates to an ISDN Trunk-side BRI trunk during a Long Test  
Sequence, an outgoing test call is invoked, and the duration of the test call is 8.6  
seconds. The outgoing ISDN Trunk-side BRI trunk test call is established over a  
high speed data channel on the Processor circuit pack (DATA-BD). A bit error  
rate greater than zero is reported as a failure to the Manager I terminal (MGRI). A  
failure indicates the need to run further diagnostics.  
Asynchronous Commands  
NOTE:  
Only one trunk can be tested in a given port network, until the test call is  
canceled or completes.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-TRK (TN2185 ISDN Trunk-Side BRI)  
3-1058  
Table 3-471. TEST #258 ISDN TEST Call  
Error  
Code  
Test  
Result  
Description/ Recommendation  
4
ABORT  
ABORT  
There is a problem with the Processor Interface Link.  
1. Refer to the PKT-INT (Packet Interface) Maintenance documentation.  
B channel in use.  
1004  
1005  
1. Determine if a call is active on this ISDN Trunk-side BRI trunk with the  
status trunk command.  
2. When the service state indicates in-service/idle, retry the test.  
Bad Configuration (that is, no Maintenance/Test circuit pack)  
ABORT  
Issue the test trunk trunk group/trunk member command and make sure  
there is a DATA-CHL administered.  
1018  
1024  
ABORT  
ABORT  
Test call is disabled.  
1. Enable Maintenance on the Trunk Group form.  
(M/T-DIG) Maintenance/Test Digital Port in use.  
1. Wait until yellow and green LEDs are turned off on the M/T-BD  
(Maintenance/Test circuit pack).  
2. Retry the test. If problem persists, refer to M/T-DIG (Maintenance/Test  
Digital Port) Maintenance documentation.  
1113  
ABORT  
The signaling link has failed. Therefore, the system cannot send any  
messages on behalf of this trunk.  
1. Check the results of Test #1251 (Signaling Link State Check Test).  
The signaling link is in a transitional state.  
1114  
1116  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The switch could not appropriately change the ISDN service state.  
1. Determine if a call is active on this ISDN Trunk-side BRI trunk (use the  
status trunk)  
2. If not, check the Error and Alarm Logs for problems with this TBRI-TRK  
MO.  
1117  
1118  
ABORT  
ABORT  
ISDN B-channel maintenance message is already outstanding.  
1. Wait two minutes. Then try again.  
Far-end of ISDN trunk is not administered.  
1. Check the administration of the far-end ISDN trunk.  
2. Issue the status trunk command.  
3. Try the test again.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-TRK (TN2185 ISDN Trunk-Side BRI)  
3-1059  
Table 3-471. TEST #258 ISDN TEST Call — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1119  
ABORT  
The test call was aborted due to a normal call attempt on this trunk. The  
test call is performed only if the trunk is idle.  
1. Either wait for the normal call to terminate normally, or force it to be  
dropped by using the busyout trunk command.  
1120  
ABORT  
The ISDN Trunk-side BRI trunk is in the ISDN out-of-service/far-end state.  
1. Try to change the service state via Test #256 (Service State Audit Test).  
Then retry this test. However, the trunk may be in the  
out-of-service/far-end state due to problems at the far-end switch.  
If that is the case, no remedial action can be taken at this end.  
1122  
1123  
ABORT  
ABORT  
ABORT  
There is no test line number for the far-end switch.  
1. Check the Trunk Group Administration form.  
There is no Feature Access Code administration for this Facility Test.  
1. Check the Dial Plan and Feature Administration forms.  
Internal System Error.  
2012  
None  
2000  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2035  
ABORT  
ABORT  
ABORT  
The call has timed out, perhaps because of a lack of system resources.  
1. Wait 1 minute and try again.  
2036  
2037  
Internal System Error.  
1. Follow the recommendation for ABORT code 2012.  
A problem occurred while trying to read the test data.  
1. Wait one minute and then try again.  
2038  
2039  
2. If the test aborts again in the same manner, there is a serious internal  
problem.  
2040  
2041  
2066  
2067  
ABORT  
ABORT  
ABORT  
ABORT  
Internal System Error.  
1. Follow the recommendations for ABORT code 2012.  
The call has timed out, perhaps because of a lack of system resources.  
1. Follow the recommendations for ABORT code 2035.  
Could not establish test call.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The call has timed out, perhaps because of a lack of system resources.  
1. Follow the recommendations for ABORT code 2035.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-TRK (TN2185 ISDN Trunk-Side BRI)  
3-1060  
Table 3-471. TEST #258 ISDN TEST Call — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Bit and Block Error query failed.  
2074  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort, there may be a serious internal problem  
with M/T-DIG (Maintenance/Test Digital Port). If this is the case, refer to  
the M/T-DIG (Maintenance/Test Digital Port) Maintenance  
documentation.  
2075  
2100  
2104  
ABORT  
ABORT  
ABORT  
Internal System Error.  
1. Follow the recommendations for ABORT code 2012.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Call dropped or could not be originated.  
1. Make sure service is provisioned by the network.  
2. Check the administration of the far-end test line extension on the trunk  
group administration form.  
3. Check the administration of the test call BCC (Bearer Capability Class)  
on the trunk group administration form.  
4. Try the test again.  
2201  
2202  
2203  
2204  
2205  
ABORT  
Internal System Error.  
1. Follow the recommendations for ABORT code 2012.  
2206  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Follow the recommendations for ABORT code 2100.  
Internal System Error.  
2208  
1. Follow the recommendations for ABORT code 2012.  
Could not allocate the necessary system resources to run this test.  
1. Follow the recommendations for ABORT code 2100.  
Internal System Error.  
2209  
2210  
2211  
2212  
2213  
1. Follow the recommendations for ABORT code 2012.  
Call terminated by unexpected disconnect.  
1. Wait one minute and then try again.  
The call has timed-out, perhaps because of a lack of system resources.  
1. Follow the recommendations for ABORT code 2035.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TBRI-TRK (TN2185 ISDN Trunk-Side BRI)  
3-1061  
Table 3-471. TEST #258 ISDN TEST Call — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Call terminated by unexpected disconnect.  
2214  
ABORT  
ABORT  
1. Wait one minute and then try again.  
Internal System Error.  
2215  
2216  
2217  
2218  
2219  
1. Follow recommendations for ABORT code 2012.  
2220  
ABORT  
ABORT  
Call terminated prematurely.  
1. Wait one minute and try again.  
Internal System Error.  
2221  
2222  
2223  
2224  
2225  
2226  
1. Follow recommendations for ABORT code 2012.  
2227  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Follow the recommendations for ABORT code 2100.  
2042  
This is the main purpose of the test. The comparison of the data sent  
with the data received indicates a loss of integrity on the communications  
path.  
1. The trunk should be taken out-of-service and the quality of the ISDN  
Trunk-side BRI line should be investigated. The investigation should  
include an in-depth analysis of the facility including the transmission  
facility and any external equipment such as DACs, CSUs, etc.  
PASS  
The call worked. A test pattern was sent and received properly; the  
communications path is OK if the synchronous test call command was  
issued. An in-depth analysis of the ISDN Trunk-side BRI trunk facility  
including the transmission facility and any external equipment such as  
DACs, CSUs, and others should take place if the bit and block error rates  
are not acceptable.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TDMODULE (Trunk Data Module)  
3-1062  
TDMODULE (Trunk Data Module)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
Trunk Data Module  
Trunk Data Module  
1
TDMODULE  
MINOR  
test port PCSSpp l  
TDMODULE (a)  
WARNING test port PCSSpp l  
1. Where P is the port network number (1); C is the carrier designation (for example, A, B, or  
C); SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02, ...,etc.); and pp is the 2-digit port number (for example, 01).  
The TDMODULE (Trunk Data Module) Maintenance documentation is covered in  
the PDMODULE (Processor Data Module) Maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1063  
TDM-BUS (TDM Bus)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command  
to Run  
Full Name of MO  
TDM Bus  
TDM-BUS  
TDM-BUS  
TDM-BUS  
MAJOR  
MINOR  
test tdm P  
test tdm P  
test tdm P  
TDM Bus  
WARNING  
TDM Bus  
The TDM Bus consists of a duplicated TDM Bus on each port network: TDM Bus  
A and TDM Bus B. Each TDM Bus consists of 256 time slots. The first five time  
slots on each bus are called the Control Channel. The Control Channel is active  
on only one bus at a time in each Port Network. The next 17 time slots are  
reserved for dedicated tones (that is, dial tone). These time slots are called the  
dedicated tone time slots and only one bus at a time carries the dedicated tones.  
The rest of the time slots on each bus are for general system use (that is, phone  
call).  
On system initialization, the Control Channel is on TDM Bus A and the dedicated  
tones on TDM Bus B in each Port Network.  
Ter m in olo g y:  
■
■
■
■
Control Channel Bus - The TDM Bus control channel is on.  
Non-Control Channel Bus - The TDM Bus control channel is NOT on.  
Tone Bus - The TDM Bus dedicated tone time slots are on.  
Non-Tone Bus - The TDM Bus dedicated tone time slots are NOT on.  
TDM Bus Fault Detection and Isolation  
Procedure  
TDM Bus faults are most likely caused by a defective circuit pack connected to  
the backplane or bent pins on the backplane. It is possible that a circuit pack  
can cause a TDM Bus fault but still exhibit trouble-free operation. For example,  
the insertion of an MBUS (Memory Bus) only circuit pack can bend the TDM Bus  
pins on the backplane and short two leads together. Since the TDM Bus is a  
shared resource, automatic identification of the cause of a TDM Bus fault is  
difficult. If a TDM Bus problem is suspected, the system technician should run  
the test tdm P system technician command. If any of the resulting tests fail, then  
the system technician must manually perform a TDM Bus isolation procedure to  
identify the cause of the problem.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1064  
!
WARNING:  
Since the TDM Bus fault isolation procedure involves removing circuit packs  
and possibly disconnecting entire carriers, the procedure is extremely  
destructive to the port network that contains the TDM Bus being tested. If  
possible, this procedure should be used after hours or during hours with  
minimum system use.  
As circuit packs are removed or entire carriers are disconnected, any active calls  
terminating on those circuit packs or carriers are dropped. If the system  
technician has any hints about a particular circuit pack that may be causing the  
TDM Bus problem (for example, a new circuit pack was inserted into the Port  
Network just before the TDM Bus problem appeared), then those hints should be  
investigated before performing this procedure.  
For this procedure, make sure at least one Tone Detector circuit pack is in the  
same Port Network in which the TDM Bus fault is being isolated. The Tone  
Detector circuit pack is needed by maintenance to test the TDM Bus.  
Procedure 1  
This procedure is an attempt to isolate the TDM Bus fault to circuit packs that are  
essential to the system operation. For each of the following circuit packs, perform  
Procedure 1.  
Circuit Pack  
Error Log Names  
TONE-BD, TONE-PT, and TDM-CLK  
SW-CTL  
Tone-Clock  
Network Control  
Tone Detector  
DETR-BD, GPTD-PT, and DTMR-PT  
1. Display the Hardware Error and Alarm Logs for the circuit pack via the  
display errors and display alarms commands.  
2. If there are errors for the circuit pack, refer to its Maintenance  
documentation and try to resolve the errors.  
3. Whether or not all the errors can be cleared, test the TDM Bus again via  
the test tdm P command.  
4. If some TDM Bus tests fail, continue with the next circuit pack.  
5. If there are no more circuit packs in the list, go to Procedure 2.  
6. If all the TDM Bus tests pass, the problem has been fixed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1065  
Procedure 2  
This procedure removes and re-inserts port circuit packs; one or several at a  
time.  
If all of the TDM Bus tests pass when the circuit pack is removed, but some of the  
tests fail when the circuit pack is inserted, the circuit pack is the cause of the  
problem and should be replaced. If some of the tests fail regardless of whether  
the circuit pack is inserted or removed, the circuit pack is not the cause of the  
problem (see Note). Repeat this procedure for each purple slot circuit pack in the  
Port Network.  
NOTE:  
Of course, in a multiple failure situation, the circuit pack may be one cause  
of the TDM Bus problem and there may be other failures that are causing  
TDM Bus faults. Also, the circuit pack itself may not be the cause of the  
problem, but the backplane pins may have been bent when the circuit pack  
was inserted.  
1. Remove port circuit packs which have failed the NPE Crosstalk Test (#6)  
first. To find which circuit packs failed this test, display the Hardware Error  
Log via the display errors command. Refer to the Maintenance  
documentation of each port circuit pack that has port errors to check if  
any error indicates the failure of the NPE Crosstalk Test.  
2. If no circuit pack failed the NPE Crosstalk Test (#6), remove one or several  
purple slot circuit packs.  
3. Run the test tdm P command.  
4. If any of the TDM Bus tests fail:  
■
■
Check if the backplane pins in the removed circuit pack’s slot  
appear to be bent.  
If the backplane pins are bent, straighten or replace the pins,  
re-insert the circuit pack, and do this procedure again for the same  
circuit pack.  
■
If the backplane pins are not bent, re-insert the circuit pack and do  
this procedure for the next set of circuit packs.  
5. If none of the TDM Bus tests fail:  
■
■
■
Re-insert the circuit pack.  
Run the test tdm system technician command.  
If any of the TDM Bus tests fail, the re-inserted circuit pack is faulty.  
Replace the circuit pack and do this procedure again for the new  
circuit pack.  
■
If none of the TDM Bus tests fail, then the problem has been fixed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1066  
Procedure 3  
Procedure 3attempts to isolate the failure to a particular set of carriers, and then  
checks only the circuit packs in those carriers. This procedure involves  
terminating the TDM Bus so that certain carriers are disconnected from the TDM  
Bus. This is done by moving the TDM Bus terminators (AHF1) on the carrier  
backplane. To terminate a TDM Bus at the end of a particular carrier, the TDM  
Bus cable that connects the carrier to the next carrier should be unplugged and  
replaced with the TDM Bus terminator. The TDM Bus terminators can be taken  
from one carrier to the other. To get to the TDM Bus cables, remove the back  
cover of the cabinet. When the length of the TDM Bus is modified via this  
procedure, the circuit packs that are essential to system operation and TDM Bus  
maintenance (for example, Network Control circuit pack, Tone-Clock circuit pack,  
Tone Detector circuit pack) must still be connected to the new shortened TDM  
Bus.  
For the Processor Port Network (PPN)  
1. Terminate the TDM Bus so that it extends within the control carrier.  
2. Run the test tdm system technician command. If any of the TDM Bus tests  
fail, perform Procedure 2 and/or Procedure 3 for only the circuit packs in  
those carriers connected to the shortened TDM Bus. Procedure 2 is  
performed for port circuit packs (purple slots) and Procedure 3 for control  
carrier circuit packs.  
3. If none of the TDM Bus tests fail, extend the TDM Bus to another carrier  
and repeat this procedure. When a carrier is added that causes some of  
the TDM Bus tests to fail, perform Procedure 2 and/or Procedure 3 for only  
the circuit packs in that carrier.  
Restarting Nonfunctioning Port Circuit Packs  
A defective TDM Bus Control Channel or system timing reference on one of the  
networks can result in port circuit packs (that is non-control carrier circuit packs)  
on this defective network entering the reset state. When this situation occurs, the  
circuit pack stops functioning and its red LED lights. The system does not detect  
the presence of a circuit pack when the circuit pack is in the reset state. Hence,  
executing the list config board PCSS command indicates that the circuit pack is  
not present.  
If a circuit pack enters the reset state when the control channel is on TDM Bus PT  
(where network P contains the circuit pack), this circuit pack stops functioning  
until it receives a restart message when the control channel is on the same TDM  
Bus PT or when this circuit pack is powered up again.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1067  
To force the system to send a restart message to all circuit packs on a network,  
try one of the following methods depending on the circumstances:  
NOTE:  
A circuit pack functioning normally (that is, not in the reset state) ignores  
the restart message.  
Procedure 1 (Nondestructive)  
Execute the Idle Time Slot Test (#294) by issuing the command test tdm P when  
the control channel is on the same TDM Bus as it was when the circuit pack  
entered the reset state. If using this method is not feasible, try the other  
procedures in this section.  
Procedure 2 (Nondestructive)  
if you are at the site: Reseat the circuit pack. This action causes the circuit pack  
that was in the reset state to begin functioning on the current Control Channel  
bus.  
Procedure 2 (Nondestructive)  
Execute the Idle Time Slot Test (#294) by issuing the command test tdm P when  
the control channel is on the same TDM Bus as it was when the circuit pack  
entered the reset state. If using this method is not feasible, try the other  
procedures in the section.  
Procedure 3 (Destructive)  
Reset the port network that contains the circuit pack that is in the reset state.  
When a network is reset, two restart messages, one on the control channel of  
each TDM Bus, are sent to each circuit pack on the network. Executing the reset  
system L command (where L=2, 3, 4, or 5) resets all networks in the system.  
!
WARNING:  
The reset system command disrupts all calls in the system.  
Procedure 4 (Destructive)  
Execute the recycle carrier PC command where P is the Port Network Number  
of the network containing the circuit pack and C is the designation of the carrier  
containing the circuit pack.  
!
WARNING:  
This command removes power and returns power to the designated  
Medium cabinet port carrier. Thus, any other circuit packs on this carrier is  
also temporarily taken out-of-service.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1068  
Error Log Entries and Test to Clear Values  
Table 3-472. TDM Bus Error Log Entries  
Aux  
Alarm  
Level  
On/Off  
Board  
Error Type  
Data  
Associated Test  
Test to Clear Value  
test tdm  
1
0
0
0
Any  
Any  
Any  
ON  
1
Control Channel Test  
(#296)  
MINOR  
test tdm P r 3  
18 (a)  
0
busyout tdm PC  
WARNING  
MINOR  
ON  
ON  
ON  
ON  
ON  
release tdm PC  
set tdm PC  
35 (b)  
0-1  
0
TDM Bus Corruption  
none  
257 (c)  
513 (d)  
769 (e)  
769 (f)  
MAJOR  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Idle Time Slot Test (#294)  
Idle Time Slot Test (#294)  
Idle Time Slot Test (#294)  
MINOR  
test tdm P r 3  
test tdm P r 3  
(see Notes)  
WARNING  
1025  
3872 (g)  
3873 (g)  
3874 (g)  
3877 (g)  
none  
none  
none  
none  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
NOTE:  
For TDM-BUS, an ON-BOARD alarm refers to a problem with the TDM-BUS  
itself.  
Notes:  
a. The TDM Bus has been busied out by the technician. The error retires  
when the technician releases the TDM Bus.  
b. This error indicates the TDM Bus is corrupted.  
An Aux Data value of 0 indicates the last reported TDM Bus corruption  
was on the Control channel bus.  
An Aux Data value of 1 indicates the last reported TDM Bus corruption  
was on the Non-Control channel bus.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1069  
If this error is logged on both TDM Buses (A and B) within two or three  
minutes, the red LED of several circuit packs may or may not be lit and  
there could be Switch Control errors. Under these circumstances do the  
following:  
■
Display the Hardware Error Log via the display errors command  
and look for SW-CTL (Switch Control) errors.  
■
If there are any errors logged against the Switch Control, try to  
resolve them.  
■
■
■
■
Test the TDM Bus via the test tdm P command.  
If all the TDM Bus tests pass, the problem has been fixed.  
Test the TDM Bus via the test tdm P command.  
If all the TDM Bus tests pass, the problem has been fixed.  
c. This error indicates the TDM Bus was switched to the other bus due to  
TDM Bus corruption. The aux data value is not meaningful and no action is  
required.  
d. This error indicates that some time slots are corrupted in the specified  
TDM Bus. The Minor alarm is raised when there are more than 50 bad time  
slots in the bus. The aux data indicates the number of bad time slots found  
by the test.  
e. This error indicates that some time slots are corrupted in the specified  
TDM Bus. The Warning alarm is raised when there are more than 10 bad  
time slots but less than or up to 50 bad ones in the bus. The aux data  
value indicates the number of bad time slots found by the test.  
f. This error indicates the idle time slot test found less than 10 bad time slots  
in the TDM Bus. The aux data value indicates the number of bad time slots  
found by the test. There is no alarm associated with this error.  
g. These errors indicate communication problems. Test the TDM Bus via the  
test tdm P command and follow the procedures according to the error  
codes reported from the test.  
The aux data value shows the Angel ID number for which a downlink  
message was lost.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the  
Control Channel Test, for example, you may also clear errors generated from  
other tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1070  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Control Channel Test on the Control  
Channel Bus (#296)  
X
X
ND  
Digit Detection Test on the Non-Control  
Channel Bus (#297)  
X
X
X
X
ND  
ND  
Idle Time Slot Test on TDM Bus A (#294)  
1. D = Destructive; ND = Nondestructive  
Idle Time Slot Test on TDM Bus A or B (#294)  
The Idle Time Slot Test detects noisy time slots on the bus and takes them  
out-of-service. The Tone Detector circuit pack is told to listen to idle time slots  
and if it detects any noise on a time slot, it returns a failure. At the end of the test,  
any out-of-service time slots are retested to see if they are still noisy and restored  
to service if they are idle. After all the time slots have been tested, maintenance  
counts the number of bad time slots and reports the number to the technician in  
the error code field. No more than 220 time slots are taken out-of-service on one  
bus, and no more than 300 are taken out-of-service on both buses at one time.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1071  
Table 3-473. TEST #294 or #295 Idle Time Slot Test on TDM Bus A or TDM Bus B  
Error  
Code  
Test  
Result  
Description/ Recommendation  
none  
ABORT  
Could not allocate the necessary system resources to run this test. For  
example, maintenance could be running on the Tone Detector circuit pack  
and it is using the CPTRs.  
1115  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
number  
The error code indicates the number of bad time slots that were detected.  
The cause of this failure is most likely due to a bad port circuit pack and  
not the TDM Bus itself.  
1. Execute the command again.  
2. If the error persists, check the Error and Alarm Logs for alarms on port  
circuit packs from the NPE Crosstalk Test.  
3. Refer to the appropriate circuit pack’s documentation to clear the  
circuit pack’s problem.  
4. Test the TDM Bus again. If the error continues, refer to the ‘‘TDM Bus  
Fault Detection and Isolation Procedure’’ described earlier.  
PASS  
The success of this test indicates all the idle time slots that are supposed  
to be idle are indeed idle. There is no noise on any of the idle time slots.  
Control Channel Test (#296)  
This test tests the integrity of the Control Channel bus. It ensures that  
communication through the TDM Bus is operational.  
Table 3-474. TEST #296 Control Channel Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
any code ABORT  
other than  
1005  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1005  
ABORT  
Since this test is valid only on the control channel bus, it aborts execution  
when run on the non-control channel bus. This is a valid response. Use the  
status system command to verify which bus is the control channel bus.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1072  
Table 3-474. TEST #296 Control Channel Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
none  
FAIL  
Communication through the Control Channel is not working. The problem is  
not necessarily the TDM Bus itself.  
1. Display the hardware error and alarm log for the Tone-Clock circuit  
pack. Refer to TONE-BD (Tone-Clock Circuit Pack) Maintenance  
documentation.  
2. Resolve the errors for the Tone-Clock circuit pack.  
3. Display the hardware error and alarm log for the Network Control circuit  
pack. Refer to DATA-BD (Network Control Circuit Pack) Maintenance  
documentation.  
4. Execute the test tdm P command again.  
5. If the test still fails, refer to the ‘‘TDM Bus Fault Detection and Isolation  
Procedure’’ described earlier.  
PASS  
Communication through the TDM Bus is operational.  
Digit Detection Test (#297)  
This test is executed on the Non-Control Channel bus. The Tone-Clock circuit  
pack is told to put a tone on the Non-Control Channel bus and the Tone Detector  
circuit pack is told to listen to it. The test passes if the tone is successfully  
transmitted on the Non-Control Channel bus.  
Table 3-475. TEST #297 Digit Detection Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
none,  
ABORT  
Could not allocate the necessary system resources to run this test.  
1001  
2100  
1005  
ABORT  
Since this test is valid only on the non-control channel bus, it aborts  
execution when run on the control channel bus. This is a valid response.  
Use the status system command to verify which bus is the control channel  
bus.  
2000  
ABORT  
Response to the test request was not received within the allowable time  
period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1073  
Table 3-475. TEST #297 Digit Detection Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
none  
FAIL  
This failure indicates that communication on the Non-Control Channel is not  
reliable.  
1. Execute the command again.  
2. If the problem persists, test the Tone-Clock circuit pack and Tone  
Detector circuit pack to make sure they are healthy. Refer to TONE-BD  
(Tone-Clock Circuit Pack), TONE-PT (Tone Generator), GPTD-PT  
(General Purpose Tone Detector Port), and DTMR-PT (Dual Tone  
Multifrequency Port).  
3. Execute the command again.  
4. If the problems persists, refer to the ‘‘TDM Bus Fault Detection and  
Isolation Procedure’’ described earlier.  
PASS  
The non-control channel bus is operational.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Use the list configuration control command to find the Tone-Clock circuit pack  
code of the system, and then proceed to look for the Short and Long Test  
Sequences according to the Tone-Clock circuit pack code.  
Always investigate tests in the order presented in the following tables when  
inspecting errors in the system. By clearing error codes associated with the SAKI  
Reset Test, for example, you may also clear errors generated from other tests in  
the testing sequence.  
Table 3-476. System Technician-Demanded Tests: TDM-BUS with the  
TN2182 Tone-Clock Circuit Pack  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
SAKI Reset Test (#53) (a)  
D/ND  
D
X
X
X
X
Clock Health Test (#46) (b)  
X
X
ND  
ND  
ND  
Control Channel Loop Around Test (#52) (a)  
Tone Generator Crosstalk Test (#90) (c)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1074  
Table 3-476. System Technician-Demanded Tests: TDM-BUS with the  
TN2182 Tone-Clock Circuit Pack — Continued  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
ND  
Tone Generator Transmission Test (#40) (c)  
Tone Generator Audit/Update Test (#41) (c)  
TDM Bus Clock Circuit Status Inquiry Test (#148)  
TDM Bus Clock PPM Inquiry Test (#150)  
X
X
X
X
X
X
X
X
X
X
X
ND  
ND  
ND  
TDM Bus Clock Parameter Update Test (#151)  
Standby Reference Health Check Test (#651) (d)  
ND  
ND  
1. D = Destructive, ND = Non-destructive  
Notes:  
a. Refer to XXX-BD (Common Port Circuit Pack) Maintenance documentation  
for descriptions of these tests.  
b. Refer to TONE-BD (Tone-Clock Circuit Pack) documentation for a  
description of this test.  
c. Refer to TONE-PT (Tone Generator) documentation for descriptions of  
these tests.  
d. This test only runs on the Standby Tone-Clock circuit pack in a Port  
Network with more than one Tone-Clock circuit pack. The circuit pack  
must be a TN2182.  
TDM Bus Clock PPM Inquiry Test (#150)  
This test evaluates the quality of the synchronization source for the Tone-Clock  
circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1075  
Table 3-477. TEST #150 TDM Bus Clock PPM Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
The system could not allocate the necessary resources for the test.  
The system could not allocate the necessary resources for the test.  
1. Wait 1 minute, and retry the test.  
1001  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
255  
ABORT  
The test was not executed because the Tone-Clock circuit pack was using  
its local oscillator rather than synchronizing to an external source.  
1. Verify that this Tone-Clock circuit pack is expected to be the  
synchronization source. If not, correct the synchronization information  
and re-execute the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1076  
Table 3-477. TEST #150 TDM Bus Clock PPM Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ANY  
FAIL  
This error represents the number of PPM errors detected on the external  
synchronization source since the last PPM inquiry was sent to the  
Tone-Clock circuit pack. A failure of this test indicates that we are outside  
of Stratum 4 timing specifications on the external timing source. This error  
produces an invalid timing signal for any system that uses this source for a  
synchronization reference. The error code is a variable amount ranging  
from 1 to 254.  
1. If there are errors against SYNC (Synchronization), refer to SYNC  
(Synchronization) Maintenance documentation to change the system  
synchronization reference, OR  
2. If there are errors against STRAT-3 (Stratum 3 Clock), refer to the  
STRAT-3 (Stratum 3 Clock) Maintenance documentation to resolve the  
errors, OR  
3. If there are errors against DS1-BD (DS1 Interface circuit pack), refer to  
the DS1-BD (DS1 Interface Circuit Pack) Maintenance documentation  
to resolve the errors, OR  
4. If there are no other errors besides Error Type 1537 against TDM-CLK  
and if this error was logged against the Tone-Clock circuit pack that  
provided the current system synchronization reference (use the status  
synchronization command to determine this), replace the defective  
Tone-Clock circuit pack.  
!
WARNING:  
Since service may be disrupted when the following procedures are  
carried out, try to perform the following steps when it is convenient  
for the customer.  
5. If the Tone-Clock circuit pack under test is in the Active mode but is not  
providing the current system synchronization reference, switch the  
synchronization reference to the Tone-Clock circuit pack under test  
using the set synchronization PC command. Rerun the test. If the test  
still fails, replace the defective Tone-Clock circuit pack.  
6. If the Tone-Clock circuit pack under test is in the Standby mode place it  
in the Active mode via the command set tone-clock PC. Switch the  
synchronization reference to the Tone-Clock circuit pack under test  
using the set synchronization PC command. Rerun the test. If the test  
still fails, replace the defective Tone-Clock circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1077  
Table 3-477. TEST #150 TDM Bus Clock PPM Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The Tone-Clock circuit pack does not detect timing any PPM errors. This  
indicates that the external synchronization timing source is valid or that the  
system synchronization reference is a Tone-Clock circuit pack. The status  
synchronization command should be used to verify that the desired  
synchronization reference is providing timing for the system.  
TDM Bus Clock Parameter Update Test (#151)  
This action updates the Tone-Clock internal circuit pack parameters. Tone-Clock  
circuit pack:  
■
■
■
■
Disable in-line duplication status messages.  
Set the PPM threshold at 85 PPM for TN2182.  
Enable PPM threshold switching  
Set the number of slips to trigger loss of signal - currently 30 per 5  
millisecond period  
■
■
Enable the on-board synchronization switching algorithm (see above)  
Enable holdover operation (TN2182 only).  
This is not a test and will always pass without identifying or reporting any  
Tone-Clock circuit pack errors.  
Table 3-478. TEST #151 TDM Bus Clock Parameter Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
FAIL  
Internal system error  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
The Tone-Clock circuit pack parameters have been successfully updated.  
Standby Reference Health Check Test (#651)  
This test evaluates the quality of the external synchronization timing source for  
the Standby Tone-Clock circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TDM-BUS (TDM Bus)  
3
3-1078  
Table 3-479. TEST #651 Standby Reference Health Check Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
This test may already be running due to a tone-clock installation, scheduled  
maintenance, alarm activity, or a technician-demand test from another  
terminal. This abort can also occur due to an internal system error.  
1. Try the command again at 1-minute intervals up to 5 times.  
1184  
ABORT  
This test requires an external synchronization source to be administered  
(DS1 primary, DS1 primary and secondary, or Stratum 3 Clock).  
1. Administer the external synchronization source and retry the test.  
Internal system error  
2500  
0
ABORT  
FAIL  
1. Try the command again at 1-minute intervals up to 5 times.  
If the Tone-Clock circuit pack is in the PPN, the external synchronization  
timing source for side A of the Stratum 3 clock, or for the Primary DS1  
reference is either absent or invalid. If the Tone-Clock circuit pack is in  
an EPN, the synchronization reference from the active EI circuit pack is  
either absent or invalid.  
1
FAIL  
If the Tone-Clock circuit pack is in the PPN, both external  
synchronization timing sources are either absent or invalid. If the  
Tone-Clock circuit pack is in an EPN, the synchronization references  
from both EI circuit packs are either absent or invalid.  
1. Correct the synchronization source problem. Refer to the  
Synchronization (SYNC) maintenance section of this manual.  
2. If the error still exists, replace the Tone-Clock circuit pack reported in  
the error log.  
PASS  
The external synchronization timing source is valid.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TDM-CLK (TDM Bus Clock)  
3-1079  
TDM-CLK (TDM Bus Clock)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command To Run  
test tone-clock PC short  
test tone-clock PC short  
release tone-clock PC  
Full Name of MO  
TDM Bus Clock  
TDM Bus Clock  
TDM Bus Clock  
TDM-CLK  
TDM-CLK  
TDM-CLK  
MAJOR  
MINOR  
WARNING  
1. P is the cabinet number (1). C is the carrier designation (A, B, or C).  
NOTE:  
Replacing the tone/clock circuit pack requires a special procedure  
described in the documentation for TONE-BD. That section also describes  
the LED displays for this board.  
The Time Division Multiplex (TDM) Bus Clock resides on the Tone-Clock circuit  
pack, providing clocking signals both for the TDM Bus and the LAN Bus. The  
Tone-Clock circuit pack is a critical component in the system and is necessary to  
ensure the operation of all port circuit packs in the system. The TDM buses of the  
PPN are synchronized together. The system timing reference can be derived  
internally from the Tone-Clock circuit pack, or from an external (off-board) timing  
reference. Currently, the TDM Bus Clock supports synchronizing the TDM Bus  
with interface rates from Digital Signal 1 (DS1) facilities as primary or primary and  
secondary references.  
Moreover, the Tone-Clock circuit pack aids in monitoring and selecting  
synchronization references. The Tone-Clock circuit pack, after detecting that the  
external source of timing is not valid, will automatically begin its escalation  
procedure, according to the facilities administered.  
NOTE:  
Switching back to a DS1 source is handled by synchronization  
maintenance, once any problems with it have been corrected and tested.  
However, once synchronization has been switched to the internal timing  
source of the master Tone-Clock circuit pack, switching back to a Stratum 3  
Clock must be initiated by a technician after the external reference has  
been repaired.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TDM-CLK (TDM Bus Clock)  
3-1080  
Initial External  
Synchronization  
Source  
Backup External  
Synchronization  
Source  
Tone-Clock  
Role  
Synchronization  
Internal  
Source  
Facilities  
Stratum 3 Clock  
Source "A"  
Source "B"  
DS1 Primary and  
Secondary  
DS1 Primary  
DS1 Secondary  
MASTER  
SLAVE  
DS1 Primary Only  
DS1 Primary  
None  
Local  
oscillator  
No External Source None  
None  
PNC Duplication  
Active EI  
Active EI  
Standby EI  
None  
No PNC  
Duplication  
See "SYNC (Synchronization)"for more details of the escalation plan. There exists  
a strong interdependency among the DS1 Interface circuit pack Maintenance,  
Synchronization Maintenance, and TDM Bus Clock Maintenance MOs.  
Error Log Entries and Test to Clear Values  
Table 3-480. TDM Bus Clock Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
1
Associated Test  
Any  
Test to Clear Value  
2
0
0
Any  
Any  
OFF  
OFF  
test tone-clock PC sh r 1  
1(a)  
0
0
None  
MINOR  
18(b)  
busyout tone-clock  
PC  
WARNING  
release tone-clock PC  
130(c)  
257(d)  
513(e)  
None  
None  
WARNING  
OFF  
OFF  
3
Any  
Any  
Any  
Any  
Any  
Clock Circuit Status  
Inquiry (#148)  
MINOR  
test tone-clock PC  
769(f)  
Clock Circuit Status  
Inquiry (#148)  
MAJOR‡  
ON  
test tone-clock PC sh r 10  
test tone-clock PC sh  
1025(g)  
Clock Slip  
Inquiry(#149)  
1281(h)  
1282(h)  
None  
MINOR  
OFF  
1537  
Clock PPM  
test tone-clock PC sh  
Inquiry(#150)  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TDM-CLK (TDM Bus Clock)  
3-1081  
Table 3-480. TDM Bus Clock Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
1
Associated Test  
Test to Clear Value  
3
2049(i)  
Any  
Standby Reference  
Health Check  
Test(#651)  
MAJOR  
ON  
test tone-clock PC  
2305(j)  
0
None  
WARNING  
OFF  
1. As a general rule, any on board errors against the TDM Bus Clock should be resolved before  
pursuing any other errors against SPEor PNC components. Off board clock errors may be caused  
by other board errors, and should usually be addressed once any on board errors have been  
resolved.  
2. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
3. Major or Minor alarms on this MO may have been downgraded to Warning alarms based on the  
values used in the set options command.  
Notes:  
a. The Tone-Clock circuit pack may have a clock at the edge of its specified  
frequency. This can is turn cause Remote Neighbor Links (RNLs) and/or  
Local Neighbor Links LNLs) to go down. When this error is alarmed, Clock  
Health Inquiry Test (#46) will fail with an error code of 1.  
1. Replace the Tone-Clock circuit pack identified in the error log.  
b. The indicated Tone-Clock circuit pack has been made unavailable via the  
busyout tone-clock PC command. To resolve this error, execute the  
release tone-clock PC command for the alarmed circuit pack.  
c. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
d. The Tone-Clock circuit pack in the PPN is not a TN780 while a Stratum 3  
synchronization is administered. Replace the Tone-Clock in the PPN with a  
TN780, or change synchronization administration to Stratum 4 if a Stratum  
3 clock is not being used.  
e. The tone-clock has reported an out-of-lock condition. A aux value of 1  
indicates this error is an out-of-lock with the primary reference. A aux  
value of 2 indicates this error is an out-of-lock with the secondary  
reference. It could not lock onto the frequency of that synchronization  
reference. This will lead to a change in the synchronization reference if the  
condition continues.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TDM-CLK (TDM Bus Clock)  
3-1082  
f. The Tone-Clock circuit pack may be defective, however it may be a  
software failure that can be corrected by testing.  
1. Check to see if the board is duplicated (list cabinet and status  
port-network) on the affected port network.  
2. If the board is not duplicated, use test tone UUCSS long to resolve  
the errors. The long test resets the board and is required to reload  
on-board RAM associated with the TN2182’s DSPs. The effect is  
that tone detectors are taken out of service momentarily and tones  
are removed from the TDM bus for about 10 seconds, meaning that  
no dial tone or touch tones are available during this interval. This  
will probably not affect calls in progress, but could cause a call  
origination to abort or a user not to get dial tone when going off  
hook.  
3. If all tests pass and the alarm does not resolve, retest with test tone  
UUCSS long clear.  
4. If the test passes, terminate the repair process. If the test fails,  
replace the circuit pack at the customer’s convenience.  
5. If this error was logged against the standby Tone-Clock, and if the  
Aux Data value was 18369, SYNC (Synchronization) maintenance  
acts on this error. No corrective action is required. For any other  
Aux Data, go to the next step.  
6. If the board is duplicated, switch to the standby side (set tone).  
7. Test the alarmed board (test tone UUCSS long). This resets the  
board and is required to reload on-board RAM associated with the  
TN2182’s DSPs.  
8. If all tests pass and the alarm does not resolve, retest (test tone  
UUCSS long clear).  
9. If the test passes, terminate the repair process. If the test fails,  
replace the circuit pack at the customer’s convenience.  
g. Tone-Clock circuit pack on-board maintenance has detected one or more  
clock slips, timing differences between its internal reference source and  
the synchronization signal provided by the master Tone-Clock. Although  
no clock slip errors are expected during normal operation, both manual  
and automatic interchanges of Tone-Clock circuit packs, synchronization  
references, and PNCs, may result in clock slip counts.  
If error 1281 also is logged for the same Tone-Clock circuit pack, it is  
related to this problem, and should be corrected first. Otherwise, continue  
with the procedure below.  
1. Use test tone-clock PC, and examine the results of test #149 to  
see if slip errors are still occurring. If no new slip errors are  
reported, and if these errors are not causing a TDM-CLK alarm,  
they may be ignored. Use test tone-clock PC long clear to clear  
the errors.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TDM-CLK (TDM Bus Clock)  
3-1083  
2. Otherwise, enter the display errors command, and follow  
corrective procedures for any other TDM-CLK, TONE-BD, SYNC,  
DS1C-BD, EXP-INTF, SNC-BD, and SNI-BD errors logged, except  
for those in the following table.  
Error Log Entries for Slip Errors  
Error Log  
Name  
Error Log Entry  
for Slips  
Circuit Pack Name  
DS1 Interface  
DS1-BD  
3073 to 3160  
1025  
Tone-Clock  
TDM-CLK  
UDS1-BD  
DS1C-BD  
UDS1 Interface  
DS1C Circuit Pack  
3073 to 3160  
3329  
3. If 1025 errors persist, refer to SYNC Maintenance.  
h. Error Type 1281 This error is an indication that the Tone-Clock circuit  
pack has detected a loss of timing signal from the system synchronization  
reference. The Tone-Clock circuit pack has switched synchronization  
references.  
1. Resolve any errors logged against the SYNC or STRAT-13  
maintenance objects.  
2. Refer to SYNC maintenance if the error is not resolved by step 1  
Error Type 1282 Indicates that the TN2182 tone-clock was synchronized  
to a DS1 facility and that the reference frequency provided by the DS1  
drifted beyond a range that could be tracked by the TN2182. Therefore  
the TN2182 is no longer synchronized to that DS1 reference. If a second  
DS1 is available, the tone-clock may be synchronized to that reference. If  
no secondary DS1 reference is available, the tone-clock will run off of its  
internal clock. This may result in slips being reported by the tone-clock  
and all DS1 facilities.  
i. The tone-clock circuit pack in the master port network was unable to  
detect the incoming synchronization signal, but the other tone-clock was  
able to detect the references. If the aux data is 0, the problem is with the  
signal on the primary. If the aux data is 1, the problem is with the signal on  
the secondary. The system should switch clocks in this situation.  
1. Replace the Tone-Clock circuit pack.  
j. The indicated Tone-Clock circuit pack has detected a loss of timing signal.  
1. Enter display errors and display alarms, and follow the  
associated repair procedures for TDM-CLK error log entries that  
have on-board alarms.  
2. If the 2305 errors persist:  
a. Execute the test synchronization r 10 command and check  
to see if new 2305 errors were reported.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TDM-CLK (TDM Bus Clock)  
3-1084  
If no new instances of the 2305 errors were logged for either test,  
then enter test tone-clock PC long clear to clear the TDM-CLK  
errors and the procedure is complete.  
3. For Port Networks with more than one Tone-Clock circuit pack,  
interchange Tone-Clocks with the set tone-clock PC, then run test  
synchronization r 10, and check to see if new 2305 errors are  
reported against the new Tone-Clock circuit pack. If not, replace  
the Tone-Clock circuit pack. If this clears the error, the problem has  
been resolved.  
4. If the problem is still not cleared, and the Tone-Clock circuit pack  
reported in the error log has not been replaced up to now, replace  
it.  
System Technician-Demanded Tests:  
Descriptions and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the SAKI Reset Test for example, you may also clear  
errors generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
Reset Board  
Sequence  
1
Order of Investigation  
SAKI Reset Test (#53) (a)  
D/ND  
D
X
X
X
X
X
X
X
Clock Health Test (#46) (b)  
X
X
ND  
ND  
ND  
ND  
ND  
ND  
Control Channel Looparound Test (#52) (a)  
Tone Generator Crosstalk Test (#90) (c)  
Tone Generator Transmission Test (#40) (c)  
Tone Generator Audit/Update Test (#41) (c)  
X
X
X
TDM Bus Clock Circuit Status Inquiry Test  
(#148)  
TDM Bus Clock PPM Inquiry Test (#150)  
X
X
X
X
ND  
ND  
TDM Bus Clock Parameter Update Test  
(#151)  
Board Type Check Test (#574)  
X
X
ND  
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Refer to ‘‘XXX-BD (Common Port Circuit Pack)’’ for descriptions of these  
tests.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TDM-CLK (TDM Bus Clock)  
3-1085  
b. Refer to ‘‘TONE-BD (Tone-Clock Circuit Pack)’’ for a description of this test.  
c. Refer to ‘‘TONE-PT (Tone Generator)’’ for descriptions of these tests.  
TDM Bus Clock Circuit Status Inquiry Test (#148)  
The TDM Bus Clock circuitry is checked for sanity. Any problems that are found  
are reported via error codes  
Table 3-481. TEST #148 TDM Bus Clock Circuit Status Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The system could not allocate the necessary resources for the test.  
1. Wait 1 minute, and retry the test.  
None  
1001  
ABORT  
2000  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
2100  
1
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
This error means the Tone-Clock circuit pack framing verification firmware  
reports an error in the clock synchronization signal coming into this Port  
Network.  
1. If the Tone-Clock circuit pack reporting the problem is a master clock,  
then the system synchronization reference is providing a bad timing  
source. Refer to SYNC (Synchronization) Maintenance documentation  
to change the system synchronization reference.  
2. If the Tone-Clock circuit pack is a slave clock, then the EI to which it is  
listening is providing a bad timing source. Follow the diagnostic  
procedures specified for TDM-CLK Error Code 2305.  
3. If no problem can be found with the incoming synchronization signal,  
replace the Tone-Clock circuit pack.  
2
FAIL  
FAIL  
This error indicates that Tone-Clock circuit pack has inaccurately detected  
loss of signal on the incoming synchronization timing source.  
4
The local oscillator on the Tone-Clock circuit pack has failed.  
or  
8
16  
or  
FAIL  
The circuitry on the Tone-Clock circuit pack used to detect synchronization  
timing errors has failed.  
32  
1. Errors 2, 4, 8, 16, and 32 indicate that there is poor synchronization  
between port networks and external facilities. It may be noticeable to  
the customer in the form of errors in data communications. The  
Tone-Clock circuit pack is defective.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TDM-CLK (TDM Bus Clock)  
3-1086  
Table 3-481. TEST #148 TDM Bus Clock Circuit Status Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
64  
FAIL  
This message is only sent when an uplink message has reported the loss of  
valid synchronization timing information coming into this Port Network. It  
has been reported in TDM-CLK Error Log entries; one or more of 1025,  
1281, 1537, 2049 and 2305.  
1. Resolve the errors indicated. No separate corrective action is required.  
There is an on-board failure of TDM clock hardware.  
66  
FAIL  
1. Use test tone UUCSS long to resolve the problem. The long test resets  
the board and is required to reload on-board RAM associated with the  
TN2182”s DSPs. The effect is that tone detectors are taken out of  
service momentarily and tones are removed from the TDM bus for  
about 10 seconds. This means that no dial tone or touch tones are  
available during this interval. It probably will not affect calls in progress,  
but could cause a call origination to abort or a user will not get dial tone  
when going off hook.  
2. If the test passes and the alarm does not resolve, retest (test tone  
UUCSS long clear).  
3. If the test passes, terminate the repair process. If it fails, replace the  
circuit pack at the customer’s convenience.  
66  
FAIL  
There is an on-board failure of TDM clock hardware.  
1. Replace the Tone-Clock circuit pack.  
PASS  
TDM Bus Clock Circuit Status is sane. There are no clock-detection circuit  
problems on the Tone-Clock circuit pack.  
TDM Bus Clock PPM Inquiry Test (#150)  
This test evaluates the quality of the synchronization source for the Tone-Clock  
circuit pack  
Table 3-482. TEST #150 TDM Bus Clock PPM Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The system could not allocate the necessary resources for the test.  
The system could not allocate the necessary resources for the test.  
1. Wait 1 minute, and retry the test.  
ABORT  
ABORT  
1001  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TDM-CLK (TDM Bus Clock)  
3-1087  
Table 3-482. TEST #150 TDM Bus Clock PPM Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
255  
ABORT  
The Tone-Clock circuit pack was using its local oscillator rather than  
synchronizing to an external source.  
1. Verify that this Tone-Clock circuit pack is expected to be the  
synchronization source. If not, correct the synchronization information  
and re-execute the test.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Any  
FAIL  
The error code represents the rate (in Parts Per Million, or PPM) at which  
clock slip errors have been detected on the incoming synchronization  
source since the last PPM inquiry was sent to the Tone-Clock circuit pack. A  
failure of this test indicates that we are outside of Stratum 4 timing  
specifications on the incoming timing source.  
The error code is a variable amount ranging from 1 to 254.  
1. If error 1537 is entered in the hardware error log against TDM-CLK, then  
the board has switched timing sources. Follow the procedures  
associated with hardware log error code 1537.  
2. Otherwise, refer to "Approach to Troubleshooting" in the  
Synchronization (SYNC) Maintenance section of this manual.  
PASS  
The Tone-Clock circuit pack does not detect timing any PPM errors. This  
indicates that the external synchronization timing source is valid or that the  
system synchronization reference is a Tone-Clock circuit pack. The status  
synchronization command should be used to verify that the desired  
synchronization reference is providing timing for the system.  
TDM Bus Clock Parameter Update Test (#151)  
This test updates the following internal parameters on the Tone-Clock circuit  
pack:  
■
■
■
■
Disable in-line duplication status messages.  
Set the PPM threshold at 85 PPM for TN2182.  
Enable PPM threshold switching  
Set the number of slips to trigger loss of signal - currently 30 per 5  
millisecond period  
■
■
Enable the on-board synchronization switching algorithm (see above)  
EnableDhoownldlooavdefrromopWewrwa.tSioomna(nTuNals2.c1o8m2. AollnMlya)n.uals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TDM-CLK (TDM Bus Clock)  
3-1088  
This is not a test and will always pass without identifying or reporting any  
Tone-Clock circuit pack errors  
Table 3-483. TEST #151 TDM Bus Clock Parameter Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
FAIL  
Internal System Error  
Internal System Error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
The Tone-Clock circuit pack parameters have been successfully updated.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-BD (Tie Trunk Circuit Pack)  
3-1089  
TIE-BD (Tie Trunk Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board PCSS sh  
Full Name of MO  
Tie Trunk Circuit Pack  
Tie Trunk Circuit Pack  
TIE-BD  
TIE-BD  
MIN  
WRN  
test board PCSS sh  
1. Where P is the port network number (1); C is the carrier designation (for example, A, B, or  
C); and SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02, ..., etc.).  
Refer to ‘‘XXX-BD (Common Port Circuit Pack)’’ Maintenance documentation for  
circuit pack level errors. See also ‘‘TIE-TRK (Tie Trunk)’’.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1090  
TIE-DS1 (DS1 Tie Trunk)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
InitialCommand to Run  
test trunk <grp/mbr> l  
test trunk <grp/mbr> l  
test trunk <grp/mbr>  
Full Name of MO  
DS1 Tie Trunk  
DS1 Tie Trunk  
DS1 Tie Trunk  
1
2
TIE-DS1  
MAJOR  
TIE-DS1  
TIE-DS1  
MINOR  
WARNING  
1. For additional repair information, see also DS1-BD (DS1 Interface Circuit Pack)  
Maintenance documentation.  
2. A MAJORalarm on a trunk indicates that alarms on these trunks are not downgraded  
by the set options command and that at least 75 percent of the trunks in this trunk  
group are alarmed.  
The DS1 tie trunk provides both voice and data inter-PBX communication. A 24  
channel DS1 Interface circuit pack can support up to 24 digital tie trunks through  
a 1.544 Mbps DS1 link. A 32 channel DS1 Interface circuit pack can support up  
to 30 digital tie trunks through a 2.048 Mbps DS1 link. DS1 Interface circuit packs  
are described in DS1-BD. DS1 Tie Trunks are used widely in the DCS and Central  
Attendant Service (CAS) features of the system.  
A DS1 tie trunk can also be used as an access endpoint which is a non-signaling  
channel with a bandwidth of voice-grade-data, 56K-data or 64K-data.  
DS1 tie trunk maintenance provides a strategy to maintain a DS1 tie trunk via a  
port on the DS1 Interface circuit pack. The maintenance strategy covers logging  
DS1 tie trunk hardware errors, running tests for trunk initialization, periodic and  
scheduled maintenance, system technician-demanded tests, and alarm  
escalation and resolution. Three different trunk service states are specified in the  
DS1 tie trunk maintenance. They are: out-of-service in which the trunk is in a  
deactivated state and cannot be used for either incoming or outgoing calls;  
in-service in which the trunk is in an activated state and can be used for both  
incoming and outgoing calls; disconnect (ready-for-service) in which the trunk is  
in an activated state but can only be used for an incoming call. If the DS1  
Interface circuit pack is out-of-service, all trunks on the DS1 Interface circuit pack  
are placed into out-of-service state, and a Warning alarm is raised.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1091  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-484. DS1 Tie Trunk Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
Any  
Any  
test trunk <grp>/<mbr> sh  
r 1>  
1 (a)  
57476  
57477  
57485  
57487  
Any  
15 (b)  
18 (c)  
Port Audit and  
Update Test (#36)  
0
busyout trunk  
<grp>/<mbr>  
WARNING  
WARNING  
OFF  
ON  
release trunk  
<grp>/<mbr>  
130 (d)  
257 (e)  
None  
test trunk <grp>/<mbr>  
57473  
57474  
57392  
2
513(f)  
769(g)  
1025  
1281  
1537  
DS1 Tie Trunk  
MIN/MAJ  
Seizure Test (#136)  
2
57393  
DS1 Tie Trunk  
MIN/MAJ  
Seizure Test (#136)  
DS1 Tie Trunk  
Seizure (Test #136) WRN  
MAJ/MIN/  
OFF  
ON  
test trunk <grp>/<mbr> r  
2
3
Conference Circuit  
(Test #7)  
MAJ/MIN/  
test trunk <grp>/<mbr> l r  
4
3
WRN  
NPE Crosstalk Test  
(#6)  
MAJ/MIN/  
WRN  
ON  
test trunk <grp>/<mbr> l r  
3
3
1793 (h)  
2305(i)  
test board PCSS long  
3
50944  
DS1 Tie Trunk  
MIN/MAJ  
OFF  
Seizure Test (#136)  
Continued on next page  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
2. This alarm will only be raised when the System-Parameter Country form has the Base Tone Generator  
field set to 4 (Italy). This alarm will be a MINOR alarm unless 75% or more trunks in this trunk group are  
out of service, then the alarm will be upgraded to a MAJOR alarm.  
3. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the set  
options command. If the MINORalarm is not downgraded by the set options values, the MINORalarm  
is upgraded to a MAJOR alarm if 75 percent of the trunks in this trunk group are alarmed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1092  
Notes:  
a. Error Type 1—The DS1 Interface circuit pack detects a hardware error on  
the DS1 tie trunk. This error can be caused by incompatible translations.  
Make sure the parameters administered on the DS1 circuit pack form  
match those administered on the far-end switch.  
The Aux Data field indicates the following hardware error types:  
57476  
57477  
57485  
57487  
On-hook before wink  
On-hook before ready to receive digits  
Wink too short for valid signal  
The timer expired while waiting for an off-hook  
signal from the far end as a response at end of  
digits dialing. Check the far-end switch for related  
problems.  
If all administration errors between the switch and the far-end match, and  
these errors continue to recur, follow normal escalation procedures.  
b. Error Type 15—This is a software audit error that does not indicate any  
hardware malfunction. Run Short Test Sequence and investigate  
associated errors (if any).  
c. Error Type 18—The DS1 tie trunk has been busied out by a busyout trunk  
grp/mbr command. No calls can be made on this trunk except for the  
Facility Access Test Call.  
d. Error Type 130—This error type indicates that the circuit pack has been  
removed or has been insane for more than 11 minutes. To clear the error,  
reinsert or replace the circuit pack.  
e. Error Type 257—The DS1 Interface circuit pack detects a hardware error  
on the DS1 tie trunk. The trunk cannot communicate with the far end  
because it is unable to interpret digits sent from the far-end switch. The  
Aux Data field indicates the following:  
57473  
57474  
The rotary dial rate is below 8 pulses per second.  
The rotary dial rate is above 12 pulses per second.  
Check with the far-end switch or operating company for proper trunk  
connection.  
f. Error Type 513—DS1 Interface circuit pack detects a hardware error on  
the DS1 tie trunk. The trunk is in-service/active and waiting for an  
‘‘on-hook’’ from the far-end switch. No calls can be routed over the trunk  
while it is in this state. Aux Data 57392 indicates no external release on  
PBX disconnect. Check with the far-end switch or operating company for  
proper trunk connection.  
g. Error Type 769—The DS1 Interface circuit pack detects a hardware error  
on the DS1 tie trunk. This error usually occurs after one or more  
occurrences of error type 513. The trunk has received the belated  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1093  
‘‘on-hook’’ that it has been waiting for from the far-end switch. The trunk is  
restored to in-service/idle and can be used for calls. Aux Data 57393  
indicates delayed external release on PBX disconnect. This error can be  
ignored.  
h. Error Type 1793—The DS1 Interface circuit pack is out-of-service. See the  
appropriate DS1-BD/UDS1-BD (DS1/UDS1 Interface Circuit Pack)  
Maintenance documentation for details.  
i. Error Type 2305—Reorder message. The trunk could not be seized. This  
error will cause the Trunk Seizure Test (#136) to run and is only considered  
a problem if the Seizure Test fails (in which case Error Type 1025 will also  
show up). In this case, the trunk may be put in ‘‘Ready-for-Service’’ state  
(shown as ‘‘disconnected’’ by the status command), which allows only  
incoming calls. Run the Trunk Seizure Test (#136) and follow its outlined  
procedures.  
j. Error Type 2562—Retry Failure error. This error is logged only. It is not a  
hardware failure and hence does not start any testing or generate any  
alarms. This error comes from call processing and is generated when a  
second attempt (retry) to seize an outgoing trunk fails.  
k. Error Type 2817—Glare error. This error is logged only. It is not a hardware  
failure and hence does not start any testing or generate any alarms. This  
error is the result of a simultaneous seizure of a two-way trunk from both  
the near-end and the far-end. Attempt to place the call again. If the error  
persists, execute the DS1 Tie Trunk Seizure Test (#136) and follow its  
outlined procedures.  
l. Error Type 3840—Port Audit and Update Test (#36) failed due to an  
internal system error. Enter status trunk command and verify the status of  
the trunk. If the trunk is out-of-service, then enter release trunk command  
to put it back to in-service. Retry the test command.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in Table 3-485 when inspecting  
errors in the system. By clearing error codes associated with the NPE Crosstalk  
Tes t, for example, you may also clear errors generated from other tests in the  
testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1094  
Table 3-485. System Technician-Demanded Tests: TIE-DS1  
Short Test  
Long Test  
Sequence  
1
Order of Investigation  
Sequence  
D/ND  
ND  
NPE Crosstalk Test (#6)  
X
X
X
X
Conference Circuit Test (#7)  
ND  
DS1 Tie Trunk Seizure Test (#136)  
Port Audit and Update Test (#36)  
X
X
ND  
ND  
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per port basis. The NPECrosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is usually only part of a port’s Long Test Sequence  
and takes on the order of 20 to 30 seconds to complete.  
Table 3-486. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test were not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 1025 (see the error log table for a description of  
this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1001  
ABORT  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1095  
Table 3-486. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1002  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions, or it may have time slots out of service due  
to TDM-BUS errors. Refer to the TDM-BUS (TDM bus) Maintenance  
Documentation to diagnose any active TDM-BUS errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic  
and the port status is idle, retry the command at 1-minute intervals for  
a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present or some of the tone  
detectors may be out of service. Issue the list measurements  
tone-receiver command to display basic information about the system’s  
tone receivers.  
1. Look for TTR-LEV errors in the error log. If present, refer to the TTR-LEV  
Maintenance documentation.  
2. Look for TONE-PT errors in the error log. If present, refer to the  
TONE-PT Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals for a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a user for a valid call. Use the display port  
PCSSpp command to determine the trunk group/member number of the  
port. Use the status trunk command to determine the service state of the  
port. If the service state indicates that the port is in use, then the port is  
unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1020  
ABORT  
The test did not run because of a previously existing error on the specific  
port or a more general circuit pack error.  
1. Examine the Error Log for existing errors against this port or the circuit  
pack and attempt to diagnose the already existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1096  
Table 3-486. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2053  
ABORT  
At least one of the following errors is found on the DS1 circuit pack: 1281—  
Loss of signal, 1793—Blue Alarm, 2049—Red Alarm, 2305—Yellow Alarm,  
1537—Hyperactivity.  
Look for the above error types in the Hardware Error Log and follow the  
procedures given in the appropriate DS1-BD or UDS1-BD maintenance  
documentation for the listed error types.  
FAIL  
This can be due to on-board or off-board problems. Off-board problems of  
concern include EXP-PN and EXP-INTF faults, TDM-BUS faults, and faults  
associated with the tone detectors/tone generators. Clear all off-board  
problems before replacing the board. Keep in mind that a TDM-BUS  
problem is usually the result of a faulty board connected to the backplane  
or bent pins on the backplane.  
1. Look for EXP-PN and/or EXP-INTF errors in the error log. If present,  
refer to the EXP-PN Maintenance documentation and the EXP-INTF  
Maintenance documentation.  
2. Look for TDM-BUS errors in the error log. If present, refer to the  
TDM-BUS Maintenance documentation.  
3. Look for TONE-BD and/or TONE-PT errors in the error log. If present,  
refer to the TONE-BD Maintenance documentation and the TONE-PT  
Maintenance documentation.  
4. Retest when the faults from steps 1, 2, and 3 are cleared. Replace the  
board only if the test fails.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated using other port tests and by examining  
station, trunk, or external wiring.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to see that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1097  
Conference Circuit Test (#7)  
One or more NPEs reside on each circuit pack with a TDM Bus interface. The  
NPE controls port connectivity and gain, and provides conferencing functions on  
a per-port basis. The Conference Circuit Test verifies that the NPE channel for the  
port being tested can correctly perform the conferencing function. The NPE is  
instructed to listen to several different tones and conference the tones together.  
The resulting signal is then measured by a Tone Detector port. If the level of the  
tone is within a certain range, the test passes.  
Table 3-487. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test were not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 1025 (see the error log table for a description of  
this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1002  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions, or it may have time slots out of service due  
to TDM-BUS errors. The status health command can be used to  
determine if the system is experiencing heavy traffic. Refer to the  
TDM-BUS (TDM bus) Maintenance Documentation to diagnose any active  
TDM-BUS errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic  
and the port status is idle, retry the command at 1-minute intervals for  
a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1098  
Table 3-487. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of tone detectors present or some of the tone  
detectors may be out of service. Issue the list measurements  
tone-receiver command to display basic information about the system’s  
tone receivers.  
1. Look for TTR-LEV errors in the error log. If present, refer to the TTR-LEV  
Maintenance documentation.  
2. Look for TONE-PT errors in the error log. If present, refer to the  
TONE-PT Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals for a  
maximum of 5 times.  
1004  
ABORT  
The port was seized by a user for a valid call. Use the display port  
PCSSpp command to determine the trunk group/member number of the  
port. Use the status trunk command to determine the service state of the  
port. If the service state indicates that the port is in use, then the port is  
unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1018  
1020  
ABORT  
ABORT  
Test disabled via administration. This only applies to analog stations.  
1. To enable test, set the Test field on the station administration screen for  
the particular analog station being tested to "y." Use the change  
station <extension> command.  
The test did not run due to a previously existing error on the specific port or  
because of a more general circuit pack error.  
1. Examine the Error Log for existing errors against this port or circuit  
pack, and attempt to diagnose the previously existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required to run this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2053  
ABORT  
At least one of the following errors is found on the DS1 circuit pack: 1281—  
Loss of signal, 1793—Blue Alarm, 2049—Red Alarm, 2305—Yellow Alarm,  
1537—Hyperactivity.  
Look for the above error types in the Hardware Error Log and follow the  
procedures given in the appropriate DS1-BD or UDS1-BD maintenance  
documentation for the listed error types.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1099  
Table 3-487. TEST #7 Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
The NPE of the tested port did not conference the tones correctly. This can  
cause noisy and unreliable connections.  
1. Enter the list configuration board PCSS command. If the circuit pack  
is a TN767B vintage 8 or 9, replace the circuit pack with a TN767C V3  
or later. The error log may have error type 1281 entries.  
2. Test all administered trunks on the board. If one fails, this could be an  
off-board problem (such as an incoming seizure or an off-hook port  
seizure during the test). Retest the board.  
3. If all of the ports fail, check the CARR-POW (see note below).  
4. If several ports fail, check the error log for TONE-BD or TONE-PT  
errors. If there are such errors, take the appropriate action. When the  
TONE errors have cleared, rerun the test.  
5. If the retry passes and troubles have been reported, coordinate  
isolation with the far-end PBX. Make sure that the near-end and far-end  
switches and any NTCE equipment (the CSU’s) have the correct  
administration.  
FAIL  
6. Replace the circuit pack.  
(con’t.)  
NOTE:  
If the conference circuit test fails for all ports on a circuit pack, a -5  
volt power problem is indicated.  
PASS  
The port can correctly conference multiple connections. User-reported  
troubles on this port should be investigated using other port tests and by  
examining station, trunk, or external wiring.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to see that there is a valid board inserted.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1100  
Port Audit and Update Test (#36)  
This test sends port level translation data from switch processor to the DS1  
Interface circuit pack to ensure that the trunk’s translation is correct. Translation  
updates include the following data: trunk type (in/out), dial type, timing  
parameters, and signaling bits enabled. The port audit operation verifies the  
consistency of the current state of the trunk kept by the DS1 Interface circuit  
pack and the switch software.  
Table 3-488. TEST #36 Audit and Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal System Error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test were not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 1025 (see the error log table for a description of  
this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1006  
ABORT  
The test was aborted because the trunk is out of service.  
1. Use the status trunk command to verify that the trunk is out of service.  
2. If the trunk is out of service, determine why.  
3. If it is OK to put the trunk back in service, issue the release trunk  
command to put the trunk back in service, and then retry the test.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal System Error.  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1101  
Table 3-488. TEST #36 Audit and Update Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
Trunk translation has been updated successfully. The current trunk states  
kept in the DS1 Interface circuit pack and switch software are consistent. If  
the trunk is busied out, the test does not run, but it does return PASS. To  
verify that the trunk is in-service:  
1. Enter status trunk command to verify that the trunk is in-service. If the  
trunk is in-service, no further action is necessary. If the trunk is  
out-of-service, continue to Step 2.  
2. Enter release trunk command to put trunk back into in-service.  
3. Retry the test command.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to see that there is a valid board inserted.  
DS1 Tie Trunk Seizure Test (#136)  
The DS1 Tie Trunk Seizure Test is run to verify the trunk’s signaling capability. The  
test is composed of two parts. The first part queries the circuit pack for the  
following errors: Loss of Signal, Red Alarm, Blue Alarm, Yellow Alarm, and  
Hyperactivity Alarm. The second part of the test is performed by sending a  
seizure message to the DS1 Interface circuit pack and expecting an active reply  
by the DS1 Interface circuit pack. If maintenance software does not receive any  
reply and the timer expires, the test is aborted. Once the active message is  
received, a dial pause message is sent to the DS1 Interface circuit pack. If the  
DS1 Interface circuit pack replies with a dial pulse tone message when the far  
end responds to the seizure, then the DS1 tie trunk Seizure Test passes. If the far  
end does not respond to the seizure and the timer expires, and the DS1 Interface  
circuit pack sends a reorder message back to the maintenance software, then  
the test fails.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1102  
This second part of this test CANNOT be run on a trunk if one of the following  
cases is true:  
1. The trunk direction is administered as an incoming only trunk.  
2. The trunk is the 24th port on a DS1 Interface circuit pack which is  
administered using 24th Common Channel Signaling.  
3. The trunk has been seized by a normal trunk call.  
4. The trunk is administered with maintenance test disabled.  
5. The outgoing signal type of the trunk is either automatic or  
immediate-start.  
Table 3-489. TEST #136 DS1 Tie Trunk Seizure Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Internal System Error.  
ABORT  
ABORT  
1000  
System resources required to run this test were not available. The port may  
be busy with a valid call. Use the display port PCSSpp command to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, then the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
1. If the port status is active but the port is not in use (no calls), check the  
error log for error type 1025 (see the error log table for a description of  
this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
1004  
ABORT  
Far end is seizing the trunk while the test is ongoing. A glare situation is  
detected. Current test is designed to be aborted. Use the display port  
PCSSpp command to determine the trunk group/member number of the  
port. Use the status trunk command to determine the service state of the  
port. If the service state indicates that the port is in use, then the port is  
unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. If the port status is idle, retry the command at 1-minute intervals for a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1103  
Table 3-489. TEST #136 DS1 Tie Trunk Seizure Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1005  
ABORT  
Test failed due to incompatible configuration administered in trunk group  
form.  
1. Verify the following fields on the trunk group administration screen:  
a. Is trunk direction incoming only?  
b. Is trunk outgoing type either automatic or immediate-start?  
c. Is trunk the 24th port of the DS1 Interface circuit pack while  
common control channel signaling is specified?  
2. If the trunk has been administered using the above information, then  
this test should abort.  
1018  
ABORT  
The test was disabled via translation. You may want to determine why the  
test has been disabled before you enable it.  
1. Verify that the Maintenance Testfield on the Trunk  
Administration screen is set to n. To enable the test, change the trunk  
administration and enter y into the Maintenance Testfield.  
2. Repeat the test.  
1020  
1040  
ABORT  
ABORT  
The test did not run due to an already existing error on the specific port or  
due to a more general circuit pack error.  
1. Examine the error log for existing errors against this port or the circuit  
pack and attempt to diagnose the already existing error.  
2. Retry the test.  
This test is not performed for trunk ports administered as access  
endpoints.  
1. Verify this port is an access endpoint by using the display port  
command.  
2. If the port has been administered as an access endpoint, this test  
should abort.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2053  
ABORT/  
FAIL  
At least one of the following errors is found on the circuit pack: 1281: Loss  
of Signal, 1793: Blue Alarm, 2049: Red Alarm, 2305: Yellow Alarm, 1537:  
Hyperactivity.  
1
1. Look for the above error types in the Hardware Error Log and follow  
the procedures given in the DS1-BD tests for the listed error types.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1104  
Table 3-489. TEST #136 DS1 Tie Trunk Seizure Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
The far-end trunk did not respond to the seizure of the near-end trunk  
within the allowable time period. This test could have associated in-line  
errors in the error log.  
1. 1) Enter the list configuration board PCSS command. If the circuit  
pack is a TN767B vintage 8 or 9, a failure of test 136 causes a  
subsequent failure of test 7 due to a firmware bug. Eventually, the  
board and all of its ports will be taken out of service and extraneous  
on-board alarms will be generated. Replace the circuit pack with a  
TN767C V3 or later.  
2. Verify that the ’Trunk Type’ field on the ’Trunk Administration’ screen  
matches the trunk type administered on far-end switch.  
3. Look for DS1-BD or UDS1-BD errors in the hardware error log. If  
present, refer to the DS1-BD (DS1 trunk circuit pack) Maintenance  
documentation or to the UDS1-BD (UDS1 trunk circuit pack)  
Maintenance documentation.  
4. Retry the test at 1-minute intervals for a maximum of 5 times.  
2000  
FAIL  
Response to the seizure message was not received within the allowable  
time period.  
1. Enter the list configuration board PCSS command. If the circuit pack  
is a TN767B vintage 8 or 9, a failure of test 136 causes a subsequent  
failure of test 7 due to a firmware bug. Eventually, the board and all of  
its ports will be taken out of service and extraneous on-board alarms  
will be generated. Replace the circuit pack with a TN767C V3 or later.  
2. Verify that the Trunk Typefield on the Trunk Administration screen  
matches the trunk type administered on far-end switch.  
3. Look for DS1-BD or UDS1-BD errors in the hardware error log. If  
present, refer to the DS1-BD (DS1 trunk circuit pack) Maintenance  
documentation or to the UDS1-BD (UDS1 trunk circuit pack)  
Maintenance documentation.  
4. Retry the test at 1-minute intervals for a maximum of 5 times.  
The trunk can be seized for an outgoing call.  
PASS  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TIE-DS1 (DS1 Tie Trunk)  
3-1105  
Table 3-489. TEST #136 DS1 Tie Trunk Seizure Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could  
be due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Check to ensure that the board translations are correct. Use the list  
config command, and resolve any problems that are found.  
2. If the board was found to be correctly inserted in step 1, issue the  
busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board long command. This should re-establish the  
linkage between the internal ID and the port. If this is not the case,  
check to see that there is a valid board inserted.  
1. Earlier G1 Software Versions reported Error Code 2053’s Test Result as FAIL.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1106  
TIE-TRK (Tie Trunk)  
MO Name (in  
Alarm Log)  
1
Alarm Level  
Initial Command to Run  
test port PCSSpp l  
Full Name of MO  
Tie Trunk  
2
3
TIE-TRK  
MAJOR  
TIE-TRK  
TIE-TRK  
MINOR  
test port PCSSpp l  
Tie Trunk  
WARNING  
test port PCSSpp sh  
Tie Trunk  
1. Where P is the port network number (1); C is the carrier designation (for example, A, B, or  
C); SSis the address of the slot in the carrier where the circuit pack is located (for example,  
01, 02, ..., etc.); and pp is the 2-digit port number (for example, 01).  
2. Not relevant to the TN497 circuit pack.  
3. A Major alarm on a trunk indicates that alarms on these trunks are not downgraded by the  
set options command and that at least 75 percent of the trunks in this trunk group are  
alarmed. (This is not relevant to the TN497 circuit pack.)  
NOTE:  
If ATMS testing is enabled, check the error log for ATMS Errors #3840 and  
#3841. If the error log indicates that measurements exceeded acceptable  
thresholds, and if no other trouble is found with the test trunk command,  
run the ATMS test call with the test analog-testcall port PCSSpp full  
command.  
The following circuit packs are covered by this section of TIE-TRK (Tie Trunk):  
■
TN497  
■
TN2140B  
The Tie Trunk circuit pack fits into a port slot and contains four trunk circuits (see  
Figure 3-44). Each tie trunk for the TN497 circuit packs has 2-wire audio  
connection/signal leads (A and B).  
A tie trunk port can also be administered as an access endpoint, which is a  
non-signaling channel with a voice-grade data bandwidth.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1107  
TIE  
TRUNK  
CIRCUIT  
PACK  
TIE  
TRUNK  
CIRCUIT  
PACK  
PBX  
PBX  
PORT  
PORT  
TIE TRUNK  
Figure 3-44. Tie Trunk Interactions  
The number of tests to be implemented for Tie Trunk maintenance depends upon  
the TIE-TRK circuit packs involved. The test are as follows:  
1. NPE Crosstalk Test—Verifies the switch connection operation of the circuit  
pack. It verifies that the trunk circuitry talks only on the selected time slot  
on the TDM Bus and that it never crosses over to time slots reserved for  
other connections.  
2. Loop Around and Conference Circuit Test—Verifies the transmission  
operation of the circuit pack. It verifies that signals are transmitted to and  
from each port (Loop Around within the port), and it tests the conference  
capabilities of all ports.  
This test may fail due to noise induced by adjacent electric power lines.  
Customers having this problem should resolve it with their local power  
company. To temporarily alleviate the alarm caused by the failure of this  
test, the test may be disabled from trunk administration test field.  
3. Several seizure tests, including the following:  
— Tie Trunk Seizure Test verifies the seizure capabilities of the circuit  
pack. For the TN2140B circuit pack, this test activates the M lead  
and checks for a response from the distant end within 10 seconds.  
This test ABORTS on trunk ports administered as access  
endpoints.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1108  
— Seizure Test (for TN497 circuit packs only)—Verifies the seizure  
capabilities of the circuit pack. This test seizes the trunk and  
outpulses a "pause." The port reports the result of the seizure  
attempt uplink. The test can be disabled via Trunk Group  
Administration.  
4. EPF, M, and E Lead Test ABORTS on trunk ports administered as access  
endpoints. This test consists of two parts:  
■
E lead test—Checks for the proper activation and deactivation of  
the port’s E lead.  
■
M lead test—Checks the M lead EPF current flow. The results of this  
test allow for distinguishing between circuit pack and external  
facility failures.  
5. Port Audit Update Test (Audit & Update Test for the TN497 circuit pack)—  
Sends non-disruptive administrative updates to the circuit pack with no  
expected response. The test updates the translation information on  
individual ports of the Tie Trunk. Except for the TN497 circuit pack, these  
updates include:  
■
Immediate, automatic, wink start, or delay dial; for the TN2140B  
,continuous-seize-ack  
■
■
■
■
For the TN2140B, continuous or discontinuous.  
Rotary or DTMF senderization in or out  
Disconnect timing  
DMTF time slot  
Additional in-line testing is performed while a call is in progress. Thus, many  
in-line errors may occur during operation. See the Error Log table for a  
description of these errors. These errors may be reproduced by using the trunk  
(making a call), and checking their occurrence in the Hardware Error Log.  
Before a maintenance test can be run on a port, the port is required to be idle.  
Except for a TN497 circuit pack, if an incoming call seizes the port which is being  
tested by maintenance, the test is aborted, and the incoming call proceeds.  
Non-TN497 circuit packs can be configured for back-to-back testing (also known  
as connectivity testing) by making translation and cross-connect changes. This  
testing configuration allows for the connection of Tie Trunks back-to-back in the  
same switch to verify the operation of Tie Trunk ports. The tests can be  
performed in either the E&M or simplex modes.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1109  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-490. TIE Trunk Error Log Entries  
Error  
On/Off  
Board  
Type  
Aux Data  
Associated Test  
Alarm Level  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
test port PCSSpp s r 1  
2
2
2
2
2
2
3
2
2
2
1 (a)  
16384  
None  
None  
None  
None  
None  
WARNING  
OFF  
2
2
2
1 (b)  
57476  
WARNING  
OFF  
2
2
2
2
1 (c)  
1 (d)  
57477  
WARNING  
OFF  
57483  
WARNING  
OFF  
2
2
2
2
1 (e)  
57485  
WARNING  
OFF  
15 (f)  
Any  
Port Audit Update (#36);  
Audit and Update (#36)  
18 (g)  
130 (h)  
257 (i)  
257 (j)  
257 (k)  
513  
0
busyout trunk <grp/mbr>  
WARNING  
WARNING  
WARNING  
WARNING  
WARNING  
MAJ/MIN/  
OFF  
ON  
release trunk <grp/mbr>  
test trunk <grp>/<mbr>  
2
2
None  
57473  
57474  
57475  
Any  
None  
OFF  
OFF  
OFF  
OFF  
None  
None  
EPF M and E Lead (#74)  
test port PCSSpp sh r 3  
test port PCSSpp sh r 3  
1
WRN  
769  
57481  
EPF M and E Lead (#74)  
None  
MAJ/MIN/  
ON  
1
WRN  
2
1025 (l)  
Any  
57392  
MAJ/MIN/  
OFF  
3
1,2  
WRN  
3
MINOR  
1281  
1537  
Any  
EPF M and E Lead (#74)  
MAJ/MIN/  
WRN  
ON  
ON  
test port PCSSpp sh r 3  
test port PCSSpp l r 3  
1
Loop Around and  
Conference (#33)  
MAJ/MIN/  
1,  
WRN  
MINOR  
1793  
2049  
Tie Trunk Seizure (#73);  
Seizure (#73) ; Tie Trunk  
Dial (#747)  
MAJ/MIN/  
WRN;  
MINOR  
OFF  
ON  
test port PCSSpp sh r 2;  
test port PCSSpp s r 2  
3
2
NPE Crosstalk (#6)  
MAJ/MIN/  
test port PCSSpp l r 3  
1
WRN ,  
MINOR  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1110  
Table 3-490. TIE Trunk Error Log Entries — Continued  
Error  
Type  
On/Off  
Board  
Aux Data  
Associated Test  
Alarm Level  
Test to Clear Value  
3
2305 (m) 50944  
None; Seizure (#73) ; Tie  
Trunk Dial (#747)  
2305 (m) 57424  
Tie Trunk Dial (#747)  
3
3
3
3
3
3
3
3
3
2561  
2817  
3073  
0
0
0
None v  
WARNING  
OFF  
3
3
3
None  
MINOR  
OFF  
3
None  
3840 (n)  
3841 (n)  
8000  
Analog Transmission  
(#844-848)  
OFF  
OFF  
Analog Transmission  
(#844-848)  
MINOR  
test analog testcall  
PCSS pp r 2  
1. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the set  
options command. If the MINOR alarm is not downgraded by the set options values, the MINOR alarm is  
upgraded to a MAJOR alarm if 75 percent of the trunks in this trunk group are alarmed.  
2. Non-TN497 circuit packs only.  
3. TN497 circuit packs only.  
Notes:  
a. Digit time-out. This occurs when the far-end PBX begins transmitting digits  
too late (10 seconds) after receiving the signal indicating ready to receive  
digits (if any). This can occur on an incoming immediate, wink, or delay  
dial line. Check the far-end PBX to ensure a translation match at both  
ends.  
b. Rotary dial before wink. This occurs when the far-end PBX starts dialing  
before the PBX sends the wink on a wink-start or (for non-TN439 circuit  
packs) on a delay-dial line. Check the far-end PBX to ensure a translation  
match at both ends.  
c. Rotary dial too early. This occurs when the far-end PBX starts dialing too  
soon (about 50ms) after seizure on a wink start or (for non-TN439 circuit  
packs) on a delay-dial line. Check the far-end PBX to ensure a translation  
match at both ends.  
d. On hook before wink. This occurs when the far end goes on hook before a  
wink. Check the far-end PBX to ensure a translation match at both ends.  
e. On an outgoing wink-start or delay-dial trunk, the wink time was too short  
(less than 80ms) for a valid signal. Check the far-end PBX to ensure a  
translaDtioownnmloaadtfcrohmaWt wbwo.tShomeannduasl.s.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1111  
f. This is a software audit error that does not indicate any hardware  
malfunction. Run the Short Test Sequence and investigate associated  
errors (if any).  
g. This indicates that the trunk in question has been busied-out by  
maintenance personnel.  
h. This indicates that the circuit pack has been removed or has been insane  
for more than 11 minutes. To clear the error, reinsert or replace the circuit  
pack.  
i. The rotary dial rate was too slow (less than eight pulses per second.)  
Check the far-end PBX to ensure a translation match at both ends.  
j. The rotary dial rate was too fast (more than 12 pulses per second.) Check  
the far-end PBX to ensure a translation match at both ends.  
k. The time between digits was too short (less than 300ms). Check the  
far-end PBX to ensure a translation match at both ends.  
l. This indicates that the trunk is still seized with an incoming call. The  
far-end PBX is not releasing the trunk after the call is dropped. A Minor  
alarm is generated every four minutes until the far-end PBX releases the  
trunk. Check the far-end PBX for problems.  
Once the trunk is released from the call, the severity of this problem is  
decreased. If Error Type 1025 does not appear again, this means that the  
problem has been corrected. Verify that Error Type 1025 does not  
reappear in the Error Log.  
m. Reorder message. Trunk could not be seized. This error causes the Tie  
Trunk Seizure Test (#73) to run, and it is considered a problem only if the  
Seizure Test fails (in which case Error Type 1793 also shows up). In this  
case, the trunk may be placed in the "Ready-for-Service" state (shown as  
"disconnected"by the status command), which allows only incoming calls.  
Run the Tie Trunk Seizure Test and follow its outlined procedures.  
n. Test calls made by the Automatic Transmission Measurement System  
(ATMS) returned measurements that were outside the acceptable limits.  
Use the list testcall detail command to examine specific transmission  
parameters that are out of spec, and investigate the trunk for that kind of  
noise. If the noise is acceptable, the limits administered on the "change  
trunk" screen should be changed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1112  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the Loop  
Around and Conference Circuit Test, for example, you may also clear errors  
generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
X
X
Loop Around and Conference Circuit Test (#33)  
ND  
2
Tie Trunk Seizure Test (#73) , Tie Trunk Dial  
X
ND  
3
4
Test (#747) , Seizure Test (#73)  
5
Tie Trunk EPF Test (#74)  
X
X
X
X
ND  
ND  
6
Port Audit and Update Test (#36) , Audit and  
4
Update Test (#36)  
Analog Transmission Test (#844-848)  
(a)  
(a)  
1. D = Destructive; ND = Nondestructive  
2. Non-TN439 and non-TN497 circuit packs only  
3. TN439 circuit pack only  
4. TN497 circuit pack only  
5. G3iV1.1-286 and G3iV2-386 only  
6. Non-TN497 circuit packs only  
Notes:  
a. ATMS test are not part of either sequence. They are run either on demand  
with the test analog-testcall command or via the ATMS schedule.  
NPE Crosstalk Test (#6)  
One or more NPE reside on each circuit pack with a TDM Bus interface. The NPE  
controls port connectivity and gain, and provides conferencing functions on a  
per port basis. The NPE Crosstalk Test verifies that this port’s NPE channel talks  
on the selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is usually only part of a port’s Long Test Sequence  
and takes 20 to 30 seconds to complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1113  
Table 3-491. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The trunk may  
be busy with a valid call. Use the display trunk xx command to determine  
the trunk group/member number of the port. Use the status trunk  
command to determine the service state of the port. If the service state  
indicates that the port is in use, the port is unavailable for certain tests. You  
must wait until the port is idle before retesting.  
1. If the port status is active, but the port is not in use (no connected  
ports), check the Error Log for Error Type 1025 (see Error Log table for  
description of this error and required actions). The port may be locked  
up.  
2. If the port status is idle, retry the command at 1-minute intervals a  
maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
System resources required to run this test are not available. This could be  
due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS Maintenance to diagnose any  
active TDM-BUS errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
(Non-TN497 circuit packs only) The port was seized by a valid call during  
the test. The test has been aborted. Use the display trunk xx command to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1114  
Table 3-491. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
2100  
Any  
Could not allocate the necessary system resources to run this test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
This test can fail due to on-board or off-board problems. Off-board  
problems of concern include TDM-BUS faults and faults associated with  
the tone detectors/tone generators. Clear all off-board problems before  
replacing the board. Keep in mind that a TDM-BUS problem is usually the  
result of a faulty board connected to the backplane or bent pins on the  
backplane.  
1. Look for TDM-BUS errors in the error log. If present, refer to the  
TDM-BUS Maintenance documentation.  
2. Look for TONE-BD and/or TONE-PT errors in the error log. If present,  
refer to the TONE-BD Maintenance documentation and the TONE-PT  
Maintenance documentation.  
3. Test the board when the faults from steps 1 and 2 are cleared. Replace  
the board only if the test fails.  
PASS  
The port is correctly using its allocated time slots. User-reported troubles  
on this port should be investigated using other port tests and examining  
station, trunk or external wiring.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Loop Around and Conference Circuit Test (#33)  
This test checks the reflective loop around, and conference capabilities of a tie  
trunk port circuit. The test uses 404-Hz, 1004-Hz, and 2804-Hz tones. This is an  
on-board test only, and each tone is transmitted through the loop and checked  
upon return.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1115  
This test may fail due to noise induced by adjacent electric power lines.  
Customers having this problem should resolve it with their local power company.  
To temporarily alleviate the alarm caused by the failure of this test, the test may  
be disabled from the trunk administration Test field.  
Table 3-492. TEST #33 Loop Around and  
Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Could not allocate the necessary system resources to run this test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The conference circuit test was aborted.  
7
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
129  
131  
133  
The 404-Hz reflective loop around test aborted. Response to the test  
request was not received within the allowable time period.  
The 1004-Hz reflective loop around test aborted. Response to the test  
request was not received within the allowable time period.  
The 2804-Hz reflective loop around test aborted. Response to the test  
request was not received within the allowable time period.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
1000  
ABORT  
System resources required to run this test are not available. The trunk may  
be busy with a valid call. Use the display trunk xx command to determine  
the trunk group/member number of the port. Use the status trunk  
command to determine the service state of the port. If the service state  
indicates that the port is in use, the port is unavailable for certain tests. You  
must wait until the port is idle before retesting.  
1. If the port status is active, but the port is not in use (no calls), check  
the Error Log for Error Type 1025 (see Error Log table for a description  
of this error and required actions). The port may be locked up.  
2. If the port status is idle, retry the command at 1-minute intervals a  
maximum of 5 times.  
1002  
ABORT  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions or it may have time slots out-of-service due  
to TDM-BUS errors. Refer to TDM-BUS Maintenance to diagnose any  
active TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic,  
repeat test at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1116  
Table 3-492. TEST #33 Loop Around and  
Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present, or some Tone  
Detectors may be out-of-service.  
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV  
Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT  
Maintenance documentation.  
3. If neither condition exists, retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
1018  
ABORT  
ABORT  
(Non-TN497 circuit packs only.) The port was seized by a valid call during  
the test. The test has been aborted. Use the display trunk xx command to  
determine the trunk group/member number of the port. Use the status  
trunk command to determine the service state of the port. If the service  
state indicates that the port is in use, the port is unavailable for certain  
tests. You must wait until the port is idle before retesting.  
The test has been disabled via administration.  
Verify that the ’Maintenance Test’ field on the ’Trunk Group’ form is set to  
’n’. To enable the test, issue the change trunk-group x command (x  
equals the number of the trunk group to be tested). Then, change the entry  
in the Maintenance Testfield on the form to y.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1117  
Table 3-492. TEST #33 Loop Around and  
Conference Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
7,  
FAIL  
The conference capabilities of the port failed (Error Code 7).  
129,  
The reflective 404-Hz Tone Test failed. No transmission was detected to or  
from the port (Error Code 129).  
131, or  
133  
The reflective 1004-Hz Tone Test failed. No transmission was detected to  
or from the port (Error Code 131).  
The reflective 2804-Hz Tone Test failed. No transmission was detected to  
or from the port (Error Code 133).  
Proceed as follows unless power or tone problems are suspected (see  
notes on the next page).  
1. To make sure the problem is on-board, disconnect the port from the  
CO and retry the test. Coordinate this with the CO, or do it after busy  
hours; otherwise, the CO may put the connection out of service.  
2. If the retry fails, replace the circuit pack.  
3. If the retry passes and no troubles have been reported, disable the  
test. If the retry passes and troubles have been reported, refer the  
problem to the CO.  
NOTE:  
If the looparound and conference circuit test fails for all ports on a  
circuit pack, a -5 volt power problem is indicated.  
If the test fails on more than 1 port, check for errors on the TONE-BD or the  
TONE-PT. If errors, take appropriate actions. When the tone errors are  
cleared, rerun the test. If the test fails again, see FAULT ISOLATION  
above.  
PASS  
Tie trunk Loop Around and Conference Test is successful. This port is  
functioning properly.  
1. If users are reporting troubles, examine loop connections to the port.  
The test could not relate the internal ID to the port (no board).  
0
NO  
BOARD  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1118  
Audit Update Test (#36)  
This test sends updates of the Tie Trunk port translation for all ports on the circuit  
pack that have been translated. The update is non-disruptive and guards against  
possible corruption of translation data contained on the board. No response  
message is expected from the circuit pack once it receives translation updates.  
The port translation data for non-TN497 circuit packs includes the following:  
Immediate, automatic, wink-start or delay dial trunk, rotary or DTMF  
senderization in or out, disconnect timing from 10 to 2550ms in 10ms increments,  
and DMTF time slot. (Continuous-seize-ack is also included for the TN2140B  
circuit pack.)  
Table 3-493. TEST #36 Audit Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1006  
(TN497 circuit pack only.) The port is in the out-of-service state. The test  
cannot be run.  
1. Retry the command once the port is in service.  
2100  
ABORT  
Could not allocate the necessary system resources to run the test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal System Error.  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
This test passed. Translation information was successfully updated on the  
circuit pack.  
1. If signaling troubles are reported, verify translation information for this  
port.  
(Non-TN497 circuit packs only.) If the trunk is busied out, the test does not  
run, but it does return PASS.  
To verify that the trunk is in-service:  
1. Enter status trunk command to verify that the trunk is in-service.  
If the trunk is in-service, no further action is necessary. If the  
trunk is out-of-service, continue to Step 2.  
2. Enter release trunk command to put trunk back into in-service.  
3. Retry the test command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1119  
Table 3-493. TEST #36 Audit Update Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board).  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Tie Trunk Seizure Test (#73), Tie Trunk Dial Test  
(#747). Seizure Test(#73)  
The Tie Trunk Seizure Test activates the M lead and checks for a response from  
the external end within 10 seconds. This test is applicable only to wink start and  
delay dial outgoing trunks. (For the TN2140B circuit pack, the trunk must also be  
continuous-seize-ack and discontinuous-seize-ack).  
The Tie Trunk Dial Test seizes the trunk and outpulses a pause digit.  
For a port administered as TGU or a TGE, the Seizure Test internally seizes the  
trunk and outpulses a "pause." The report reports the result of the seizure attempt  
uplink.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1120  
Table 3-494. Seizure Tests (#73, #747, #73)  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The trunk may  
be busy with a valid call. Use the display trunk xx to determine the trunk  
group/member number of the port. Use the status trunk command to  
determine the service state of the port. If the service state indicates that  
the port is in use, then the port is unavailable for certain tests. You must  
wait until the port is idle before retesting.  
1. If the port status is active, but the port is not in use (no calls), then  
check the Error Log for Error Type 1025 (see Error Log table for  
description of this error and required actions). The port may be locked  
up. The far-end PBX may not be releasing.  
2. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
1005  
ABORT  
ABORT  
(Non-TN497 circuit packs only.) The port was seized by a valid call during  
the test. The test has been aborted. Use the display trunk xx to determine  
the trunk group/member number of the port. Use the status trunk  
command to determine the service state of the port. If the service state  
indicates that the port is in use, the port is unavailable for certain tests. You  
must wait until the port is idle before retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
This test is not valid for this trunk translation. For this test to run, a delay  
dial trunk (or, for non-TN497 circuit packs, a wink-start trunk) must be in  
effect, and the trunk must be outgoing or two-way. Also, for the TN2140B,  
the trunk must be continuous-seize-ack or discontinuous-seize-ack.  
1. Check trunk translation. If it is not a wink-start or delay dial trunk, this  
abort message should be ignored. (For the TN2140B, disregard this  
abort on a trunk that is not continuous-seize-ack or  
discontinuous-seize-ack.)  
1018  
ABORT  
Test disabled via administration.  
1. Verify that the Maintenance Tests?field on the Trunk Group  
Form is set to n. To enable the test, issue the change trunk-group x  
command where "x"equals the number of the trunk group to be tested.  
Then change the entry in the Maintenance Tests?field on the  
form to y.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1121  
Table 3-494. Seizure Tests (#73, #747, #73) — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1040  
ABORT  
(Non-TN497 circuit packs only.) This test is not performed for trunk ports  
administered as access endpoints.  
1. Verify this port is an access endpoint by using the display port  
command.  
2. If the port has been administered as an access endpoint, this test  
should abort.  
2000  
ABORT  
Seizure message is not received back within 10 seconds.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, check the far-end PBX to ensure a  
translation match at both ends.  
3. Check the facility.  
2100  
3
ABORT  
FAIL  
Could not allocate the necessary system resources to run the test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
(TN439 circuit packs only.) No dial tone detected from the other end.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to fail, check the far-end PBX to ensure a  
translation match at both ends.  
3. Check the facility.  
PASS  
The relevant seizure test passes. This port is functioning properly.  
1. If users are reporting troubles, examine loop connections to the port,  
wiring, and stations.  
0
NO  
The test could not relate the internal ID to the port (no board).  
BOARD  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1122  
Tie Trunk EPF Test (#74)  
This test consists of an E lead and M lead test. The E lead test checks for the  
proper activation and deactivation of the port’s E lead. The M lead test checks  
the M lead EPF current flow. The processor sends an M lead test request to the  
circuit pack and receives the results. The returned results are measured to see if  
a port or external tie trunk line fails.  
Table 3-495. TEST #74 Tie Trunk EPF Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Could not allocate the necessary system resources to run the test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal System Error.  
1
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The trunk may  
be busy with a valid call. Use the display trunk xx to determine trunk  
group/member number of the port. Use the status trunk command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port is unavailable for certain tests. You must wait  
until the port is idle before retesting.  
1. If the port status is active, but the port is not in use (no calls), then  
check the Error Log for Error Type 1025 (see Error Log table for  
description of this error and required actions). The port may be locked  
up. The far-end PBX may not be releasing.  
2. If the port status is idle, then retry the command at 1-minute intervals a  
maximum of 5 times.  
1004  
1005  
ABORT  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display trunk xx to determine the trunk group/member  
number of the port. Use the status trunk command to determine the  
service state of the port. If the service state indicates that the port is in use,  
the port is unavailable for certain tests. You must wait until the port is idle  
before retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
This test is not valid for this trunk translation. Must be a Type-1 standard  
trunk for this test to run.  
1. Check trunk configuration. If it is not a Type-1 standard trunk, this abort  
message should be ignored.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1123  
Table 3-495. TEST #74 Tie Trunk EPF Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1014  
ABORT  
The test was aborted because the circuit pack has not been inserted into  
the system.  
1. Use the list configuration board command to make sure the circuit  
pack is inserted in the carrier.  
2. If the board is not inserted, make sure the circuit pack is inserted in the  
carrier and fully seated.  
1040  
ABORT  
This test is not performed for trunk ports administered as "access  
endpoints."  
1. Verify this port is an access endpoint by using the display port  
command.  
2. If the port has been administered as an access endpoint, this test  
should abort.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run the test. This  
could be due to a failure to seize the port.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The E lead test failed due to an on-board port problem.  
1. Replace the circuit pack.  
1
2
FAIL  
FAIL  
The M lead test failed. The EPF has experienced an overcurrent condition,  
perhaps due to the external M lead.  
1. To make sure the problem is on-board, disconnect the facility from the  
pack and retry the test.  
2. If the test fails, replace the circuit pack. Otherwise, check the external  
wiring toward the far-end PBX.  
PASS  
Tie Trunk EPF test is successful. This port is functioning properly.  
1. If users are reporting troubles, examine loop connections to the port.  
The test could not relate the internal ID to the port (no board).  
0
NO  
BOARD  
1. Check to ensure that the board translations are correct. Translate the  
board, if necessary.  
2. Issue the busyout board command.  
3. Issue the reset board command.  
4. Issue the release busy board command.  
5. Issue the test board command. This should re-establish the linkage  
between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1124  
Transmission Test (#844-848)  
This test is non-destructive.  
NOTE:  
Tests #844-848 are not supported on an International switch.  
These tests are run by the Automatic Transmission Measurement System (ATMS).  
They are not part of the long or short trunk test sequences. Instead, they are run  
on demand with the test analog-testcall command or as part of ATMS  
scheduled testing.  
The test call is run from an analog port on a TN798 Processor circuit pack. It  
attempts to seize a port and make a call to a terminating test line (TTL) on the  
trunk’s far end. Transmission performance measurements are made and  
compared to administered thresholds. Errors are generated when results fall  
outside of ‘‘marginal’’ or ‘‘unacceptable’’ thresholds. Detail and summary  
measurement reports are obtainable via the list testcalls command.  
Table 3-496. TEST #844-848 Transmission Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call. Use display port PCSSpp to determine the trunk  
group/member number of the port. Use the status trunk command to  
determine the service state of the port. If the service state indicates that the  
port is in use, then the port unavailable for this test. You must wait until the  
port is idle before retesting.  
1. If the port status is idle, then retry the command at 1-minute intervals  
for a maximum of 5 retries.  
1001  
1002  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 retries.  
The system could not allocate timeslots for the test. The system may be  
under heavy traffic conditions or it may have timeslots out of service due to  
TDM bus errors. Refer to TDM Bus Maintenance to diagnose any active  
TDM bus errors.  
1. If system has no TDM bus errors and is not handling heavy traffic,  
repeat test at 1-minute intervals for a maximum of 5 retries.  
1004  
1005  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use status trunk to  
determine when the port is available for testing.  
1. Retry the command at 1-minute intervals for a maximum of 5 retries.  
Trunk has been administered as incoming-only; transmission tests can  
only be run on outgoing trunks.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1125  
Table 3-496. TEST #844-848 Transmission Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1115  
ABORT  
The near end test line on the circuit pack could not be allocated.  
1. Verify that the circuit pack is in service and that port 1 is administered  
and in service with the status port command.  
2. retry the command at 1-minute intervals for a maximum of 5 retries.  
The test completion message was not received from the circuit pack.  
1. Test the TN798 circuit packs.  
1900  
1901  
ABORT  
ABORT  
This error occurs when the TN798 circuit pack uplinks a message that is  
not the proper response for this test. The anticipated uplink messages are  
seize, ring or answer.  
1. Verify that the Trunk is administered properly.  
Intercept tone detected from far end.  
1905  
ABORT  
1. Get the test line data from theand verify it with the far end. Dial the test  
number manually to see if the TTL is reached. If it is not, then either the  
number is wrong, or the far end is administered incorrectly.  
1906  
1907  
1913  
1914  
1915  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
Reorder tone detected from far end.  
1. See actions for error code 1905.  
Other unexpected tone detected from far end.  
1. See actions for error code 1905.  
Audible Ring detected from far end.  
1. See actions for error code 1905.  
Unidentified interrupted tone detected from far end.  
1. See actions for error code 1905  
Busy tone detected from far end.  
1. Since the test line at the far end was busy. Try the test again.  
2. If the test continues to abort, the problem is with the far end system.  
Test progress tone not removed from far end (type 105 test line only).  
1918  
1919  
ABORT  
ABORT  
1. The problem is with the far end system; a technician at the far end  
should test the test line (TN798).  
Unexpected far end release  
1. The problem is with the far end system; a technician at the far end  
should test the test line (TN798).  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1126  
Table 3-496. TEST #844-848 Transmission Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
No response from far end.  
1920  
ABORT  
1. The problem is with the far end system; a technician at the far end  
should test the test line (TN798).  
1921  
ABORT  
No data returned from far end.  
1. The problem is with the far end system; a technician at the far end  
should test the test line (TN798).  
1922  
1923  
ABORT  
ABORT  
Steady, unidentifiable tone from far end  
1. See actions for error code 1905.  
Broadband energy detected from far end (such as voice or  
announcement).  
1. See actions for error code 1905.  
No test tone from far end  
1924  
1938  
1939  
1940  
ABORT  
ABORT  
ABORT  
ABORT  
1. See actions for error code 1905.  
Near-end self test failed.  
1. Test the TN798 circuit pack.  
Loss self check at 0dBm at 1004 Hz failed.  
1. Test the TN798 circuit packs.  
Far end noise self check failed.  
1. The problem is with the far end system; a technician at the far end  
should test the test line (TN798).  
1941  
1942  
1943  
1944  
1945  
1946  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
ABORT  
High frequency singing return loss self check failed.  
1. Test the TN798 circuit pack.  
Echo return loss self check failed.  
1. Test the TN798 circuit pack.  
Singing return loss self check failed.  
1. Test the TN798 circuit pack.  
Loss self check at -16 dBm at 1004 Hz failed.  
1. Test the TN798 circuit pack.  
Loss self check at -16 dBm at 404 Hz failed.  
1. Test the TN798 circuit pack.  
Loss self check at -16 dBm at 2804 Hz failed.  
1. Test the TN798 circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TIE-TRK (Tie Trunk)  
3
3-1127  
Table 3-496. TEST #844-848 Transmission Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Noise with tone self check failed.  
1. Test the TN798 circuit pack.  
1947  
ABORT  
ABORT  
2000  
The test timed out while waiting for a response from the TN798 circuit  
pack.  
1. Retry the command at 1-minute intervals for a maximum of 5 retries.  
An internal software error occurred.  
2012  
2053  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals for a maximum of 5 retries.  
The test call could not be established, but no information on why is  
available.  
1. Retry the command at 1-minute intervals for a maximum of 5 retries.  
2056  
ABORT  
FAIL  
An error occurred while trying to obtain results from the TN771 circuit  
pack.  
1. Test the TN798 circuit pack.  
Measured transmission performance was in the unacceptable range as  
administered on the trunk group form. Retrieve a measurement report via  
the list testcalls command. Make sure that ATMS thresholds are set  
properly on page 4 of the Trunk Group form. Besides the facility, test  
failures can be caused by faulty test lines or switch paths. If the  
measurements point to a facility problem, report the results to the trunk  
vendor.  
8000  
FAIL  
Measured transmission performance was in the marginal range as  
administered on the trunk group form. This generally means that the trunk  
is usable but has an undesirable amount of noise or loss. If the user does  
not report unacceptable effects, it may not be necessary to take any  
action. Retrieve a measurement report via the list testcalls command.  
Make sure that ATMS thresholds are set properly on page 4 of the Trunk  
Group form.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-BD (Tone-Clock Circuit Pack)  
3-1128  
TONE-BD (Tone-Clock Circuit Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test tone-clock PC  
Full Name of MO  
Tone-Clock Circuit Pack  
Tone-Clock Circuit Pack  
Tone-Clock Circuit Pack  
TONE-BD  
TONE-BD  
TONE-BD  
MAJOR  
MINOR  
test tone-clock PC  
WARNING  
release tone-clock PC  
1. P is the port network number (1). C is the carrier designation (A, B, or C).  
The Tone-Clock circuit pack functionality is provided by two independent objects  
in the same circuit pack. The tone generator provides all the tones needed by the  
system and the clock generates the system clocks for the Time Division Multiplex  
(TDM) Bus and aids in monitoring and selecting internal synchronization  
references.  
When resolving errors/alarms on the Tone-Clock circuit pack, the following  
should be used also:  
■
■
■
TONE-PT (Tone Generator) Maintenance documentation.  
TDM-CLK (TDM Bus Clock) Maintenance documentation.  
SYNC (Synchronization) Maintenance documentation.  
The TN2182 is a combined Tone-Clock/Detector circuit pack that contains 8  
ports used for all-purpose tone detection. These ports are called Enhanced Tone  
Receiver ports (ETR-PT) and are described in the documentation for ETR-PT.  
Tone-Clock Circuit Packs  
CMC systems have one Tone-Clock circuit pack in each port network. This is in  
the A carrier. This Tone-Clock circuit pack generates clocks and provides system  
tones for all carriers of the port network it resides on.  
Italian Tone Settings (New ISPT Value)  
Tone  
Default  
Continuous  
Cadenced  
Old ISPT Value  
Cadenced  
Dial  
Confirmation  
Continuous  
The TN2182 allows International changes, but allows the customization of up to  
24 system tones in order to meet specific country needs. These changes are  
made via the change system-parameters country-options form.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-BD (Tone-Clock Circuit Pack)  
3-1129  
How to Replace a Tone-Clock Circuit Pack  
Replacing the Tone-Clock circuit pack is a service-disrupting procedure on Port  
Networks, because the Tone-Clock circuit pack is always needed to generate  
clocks for its network. When the circuit pack is removed, all calls are dropped  
immediately. However, if the Tone-Clock is removed for replacement, the System  
Emergency Transfer feature is activated within milliseconds, and the entire  
system is disrupted; no calls can be placed, and existing calls are dropped.  
When replacing the Tone-Clock circuit pack, always replace it with a TN2182  
Tone-Clock circuit pack. The TN2182 may be used in all country configurations.  
Port Networks with a Single Tone-Clock Circuit  
Pack  
This procedure is destructive.  
1. Pull out the defective Tone-Clock circuit pack. This will remove the clocks  
and cause the system to activate emergency measures:  
■
The system will immediately go into the Emergency Transfer state.  
2. Insert a new Tone-Clock circuit pack. The system will detect the return of  
the clocks and will automatically recover as follows:  
■
The system will perform a reset system 2 (system cold 2 restart)  
automatically. First, all red LEDs of the PPN will come on and off  
within 30 seconds.  
3. If the red LEDs come on but do not go off within 30 seconds, pull the  
circuit pack out and reseat it. If the LEDs perform as expected this time,  
continue with step 4. Otherwise, there may be a problem with the TDM  
bus; possibly a bent pin in the Tone-Clock circuit pack slot. Follow the  
directions in the TDM-BUS maintenance section.  
4. If the red LEDs did light, as explained above, then go to Step 6. If the red  
LEDs do NOT light, as explained above, then go on to Step 5.  
5. Restart the affected Port Network:  
■
Restart the system via the reset system 2 command.  
6. Test the new Tone-Clock circuit pack to verify that it is functioning properly,  
using the test tone-clock PC long command, and verify that the system is  
operational by placing several phone calls. Where possible, try calls into,  
out from, and within the affected Port Network.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-BD (Tone-Clock Circuit Pack)  
3-1130  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-497. Tone-Clock Circuit Pack Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
1
0
0
0
Any  
Any  
ON  
test tone-clock PC sh  
1(a)  
Circuit pack  
MINOR  
removed or SAKI  
Sanity Test (#53)  
18(b)  
0
0
busyout tone-clock  
PC  
WARNING  
OFF  
release tone-clock PC  
23(c)  
125(d)  
126(e)  
257  
None  
None  
None  
WARNING  
MINOR  
OFF  
ON  
ON  
ON  
MINOR  
65535  
Control Channel  
Test (#52)  
MINOR  
test tone-clock PC r 20  
test tone-clock PC sh  
257(f)  
Any  
Any  
4358  
4363  
Any  
0
None  
513(g)  
769(h)  
1025(i)  
1538(j)  
2049(k)  
None  
None  
NPE Audit Test (50)  
None  
MINOR  
MAJOR  
ON  
ON  
Clock Health  
Inquiry Test (#46)  
set tone-clock PC  
override  
2305(k)  
0
Clock Health  
Inquiry Test (#46)  
MAJOR  
MAJOR  
ON  
set tone-clock PC  
override  
2561(l)  
Any  
0
None  
None  
ON  
3329(m)  
MINOR/  
WARNING  
OFF  
set tone-clock PC  
2
3840(n)  
3848(o)  
Any  
0
None  
Clock Health  
Inquiry Test (#46)  
set tone-clock PC  
override  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-BD (Tone-Clock Circuit Pack)  
3-1131  
Table 3-497. Tone-Clock Circuit Pack Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
None  
Test to Clear Value  
3872(p)  
0
set tone-clock PC  
override  
3999 (q) Any  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
2. Minor alarms on this MO may be downgraded to Warning alarms based on the value used in the  
set options command.  
Notes:  
a. Error Type 1  
This error indicates the circuit pack totally stopped  
functioning or it was physically removed from the system.  
NOTE:  
The alarm is logged approximately 11 minutes after the circuit pack  
is removed/SAKI Sanity Test (#53) fails.  
If the circuit pack is not present in the system, insert a circuit pack in the  
slot indicated by the error to resolve the error.  
If the circuit pack is present in the system, it is faulty and must be  
replaced. See the preceding section, ‘‘How to Replace a Tone-Clock  
Circuit Pack’’.  
b. Error Type 18 The indicated Tone-Clock circuit pack has been made  
unavailable via the busyout tone-clock PC command. This error applies  
only to High or Critical Reliability systems (an active Tone-Clock may not  
be busied out). To resolve this error, execute release tone-clock PC.  
c. Error Type 23 The circuit pack has been logically administered but not  
physically installed. Installing the circuit pack will resolve the alarm.  
d. Error Type 125 A wrong circuit pack is inserted in the slot where this  
circuit pack is logically administered. To resolve this problem, either  
remove the wrong circuit pack and insert the logically administered circuit  
pack OR use the change circuit-pack command to readminister this slot  
to match the circuit pack inserted.  
e. Error Type 126 The port network specified in the PORT field of the error  
log entry booted up without a Tone-Clock circuit pack, or with a one that  
cannot communicate at all with the system. The error is logged five  
minutes after the port network is restarted. If no circuit pack is present,  
install one of the proper code. If there is a circuit pack present, replace it.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-BD (Tone-Clock Circuit Pack)  
3-1132  
See the preceding section, ‘‘How to Replace a Tone-Clock Circuit Pack’’. If  
replacement does not solve the problem, follow normal escalation  
procedures.  
f. Error Type 257 Τhis error indicates transient communication problems  
with this circuit pack . This error is not service-affecting and no action is  
required.  
g. Error Type 513 This circuit pack has an on-board hardware failure.  
Replace the circuit pack using the procedure described in preceding  
section, ‘‘How to Replace a Tone-Clock Circuit Pack’’.  
h. Error Type 769 This error can be ignored, but look for other errors on this  
circuit pack.  
i. Error Type 1025 This error is not service-affecting and no action is  
required.  
j. Error Type 1538 The circuit pack was taken out of service because of an  
excessive rate of uplink messages. Use test tone-clock PC long to reset  
the circuit pack and put it back into service. If the command is not  
successful, replace the circuit pack using the procedure described in the  
preceding section, ‘‘How to Replace a Tone-Clock Circuit Pack’’. If the  
alarmed circuit pack is the active Tone-Clock of a duplicated pair, first  
interchange Tone-Clocks via the set tone-clock PC command to avoid a  
service outage. If the error occurs again within 15 minutes, follow normal  
escalation procedures.  
k. Error Type 2049 or 2305 These errors indicate the loss of one or more  
clock signals from the reported Tone-Clock circuit pack, which was active  
at the time of the error. The effect of any of these errors is described in the  
table for error type 1. Diagnosis of the problem is the same for all four error  
types, with the exception noted below.  
1. Examine the Hardware Error Log for errors reported against circuit  
packs in the same Port Network, especially TDM-CLK, TONE-BD,  
DUPINT, SW-CTL, and EXP-INTF. Follow the repair or replacement  
procedures indicated for any such errors found.  
2. If the error is not corrected by resolving errors found in step 1, the  
Tone-Clock circuit pack should be replaced. See the preceding  
section, ‘‘How to Replace a Tone-Clock Circuit Pack’’.  
NOTE:  
Replacing the circuit pack and retesting it with the test  
tone-clock command is not adequate to retire this alarm and  
return the Tone-Clock Circuit Pack to full service; the Clock  
Health Inquiry test (#46) will continue to fail. Because the  
ability to generate clocks was considered lost, once any  
repairs have been made it is necessary to execute the set  
tone-clock PC override command, forcing the circuit pack to  
become active. If the problem has not actually been  
corrected, this action may cause a disruption in service for  
active digital facilities users.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-BD (Tone-Clock Circuit Pack)  
3-1133  
3. If error 2305 or 3848 persists, all clock signals from the indicated  
board were lost. If the reported Tone-Clock circuit pack is in a Port  
Network with duplicated Tone-Clocks, the problem may lie with the  
circuit pack responsible for selecting the active Tone-Clock circuit  
pack (the t/c selector).  
■
For a PPN, the t/c selector is the DUPINT circuit pack on  
carrier A.  
■
For an EPN, the t/c selector is the active EXP-INTF circuit  
pack that is connected to the PPN. This is EXP-INTF 2A01 or  
2B02 for EPN1 and 3A01 or 3B02 for EPN2.  
The t/c selector circuit pack of interest is the one which was active  
at the time the error was logged. This is the currently active t/c  
selector unless there has been an SPE interchange for PPN  
problem, or an EXP-INTF link switch for EPN problem, In order to  
determine whether an interchange has occurred since the  
TONE-BD error, examine the display initcauses log for SPE  
interchanges, and EXP-LNK entries in the hardware error log for  
expansion link interchanges.  
If the t/c selector circuit pack was not replaced as part of the  
previous step, replace it now.  
4. If the error has not been corrected at this point, there is a problem  
with the TDM Bus within the Port Network containing the reported  
Tone-Clock circuit pack. This may include TDM Bus intercarrier  
cables, Bus terminators, bent pins on the backplane, and errors on  
any circuit pack plugged into the same Port Network. Refer to the  
TDM-BUS section.  
5. If the problem persists, follow normal escalation procedures.  
l. Error Type 2561  
This error indicates that a Tone-Clock circuit pack, with  
a different circuit pack code as required for this system, has been inserted  
in the port slot as shown in the Hardware Error Log. To resolve this error,  
refer to the ‘‘How to Replace a Tone-Clock Circuit Pack’’ section for an  
appropriate circuit pack code and replace the Tone-Clock circuit pack  
according to the procedures indicated for this system. The meanings of  
the aux data values are as follows:  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-BD (Tone-Clock Circuit Pack)  
3-1134  
1001  
1002  
1003  
1004  
1005  
A TN756 Tone-Clock circuit pack is in the PPN of a one port  
network system without High or Critical Reliability  
(Multicarrier Cabinet).  
A TN756 Tone-Clock circuit pack is in the EPN of a one port  
network system without High or Critical Reliability  
(Multicarrier Cabinet).  
Either a TN741 or TN714 Tone-Clock circuit pack (instead of  
a TN768, TN780 or TN2182) is in a one port network system  
without High or Critical Reliability (Multicarrier Cabinet).  
Either a TN741 or TN714 Tone-Clock circuit pack (instead of  
a TN768, TN780 or TN2182) is in a High or Critical Reliability  
system.  
Same as for aux value 1004.  
m. Error Type 3329 The system attempted but failed to interchange  
Tone-Clock circuit packs. (This error occurs only in Port Networks with  
duplicated Tone-Clocks.) The fault may lie in the standby Tone-Clock or in  
the circuit pack that controls selection of the active Tone-Clock (the t/c  
selector). The goal of the following procedure is to ensure that both  
Tone-Clocks can be interchanged into while either t/c-selector circuit pack  
is active.  
1. Examine the Error Log for errors reported against circuit packs in  
the same Port Network, paying special attention to TDM-CLK,  
TONE-BD, DUPINT, SW-CTL, and EXP-INTF. Follow the procedures  
indicated for any such errors found. After eliminating the above  
potential problem sources, proceed with the following steps.  
2. Determine which circuit pack was controlling the choice of  
Tone-Clock at the time the error occurred.  
■
For a PPN, the t/c selector is the DUPINT circuit pack on the  
A-carrier.  
■
For an EPN, the t/c selector is the active EXP-INTF circuit  
pack that is connected to the PPN. This is EXP-INTF 2A01 or  
2B02 for EPN1 and 3A01 or 3B02 for EPN2.  
The t/c-selector circuit pack of interest is the one which was active  
at the time the error was logged. An EXP-LNK interchange since the  
time of the error may have made that circuit pack the current  
standby. Determine whether an interchange affecting the t/c  
selector has occurred since the TONE-BD error. When investigation  
an EPN Tone-Clock, look for EXP-LNK entries in the hardware error  
log for PNC interchanges, which would affect the EXP-INTF.  
3. If the t/c selector has not undergone an interchange since the error  
occurred, go to the next step. If such an interchange has taken  
place, interchange back to the formerly active t/c selector. Use the  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-BD (Tone-Clock Circuit Pack)  
3-1135  
set expansion-interface command when investigating an EPN  
Tone-Clock.) If the interchange attempt fails due to other errors,  
resolve those problems first.  
4. Interchange the Tone-Clock circuit packs using the set tone-clock  
PC command. If the command succeeds, the interchange which  
previously failed has been accomplished and the problem has  
been satisfactorily resolved. If it fails, proceed to the next step. (You  
may want to proceed in any case to definitively test all relevant  
components.)  
5. Interchange the t/c selector using set expansion-interface if  
investigating an EPN. If errors prevent this interchange, resolve  
them first.  
6. Attempt again to interchange Tone-Clocks with the set tone-clock  
PC command.  
— If the Tone-Clock interchange failed for both t/c selectors:  
Replace the standby Tone-Clock circuit pack which could  
not be interchanged into and return to this step. (See ‘‘How  
to Replace a Tone-Clock Circuit Pack’’.) Test the new circuit  
pack as follows:  
a. Execute the set tone-clock PC command.  
b. Execute a set expansion-interface, if this is an EPN  
Tone-Clock.  
c. Execute the set tone-clock PC command again.  
If these commands successfully complete, the problem has  
been resolved.  
— If these commands successfully complete, the problem has  
been resolved.  
— If the Tone-Clock circuit packs successfully interchange  
when one EXP-INTF is active, but not when the other one is:  
The t/c-selector circuit pack on the failing side is suspect.  
a. Replace the A carrier DUPINT or EXP-INTF board that is  
active when the Tone-Clock interchange fails.  
b. Make sure the new t/c selector is active and execute the set  
tone-clock PC command.  
— If both Tone-Clocks can be interchanged, and interchanges  
succeed when either t/c selector is active, the problem has  
been resolved. If the problem persists after following the  
above steps, follow normal escalation procedures.  
n. Error Type 3840 This error is not service-affecting and can be ignored. It  
indicates that the circuit pack has received a bad control message from  
the switch.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-BD (Tone-Clock Circuit Pack)  
3-1136  
o. Error Type 3848 This error indicates that the Tone/Clock circuit pack had  
a loss of clock. If error 2305 is also logged, see note (j).  
p. Error Type 3872  
These errors indicate this Tone/Clock circuit pack had  
a loss of Data Clocks. This error will impact mainly users on station  
connected to Digital circuit packs. These users could be with out service.  
If error 2049 is also logged see note (i).  
q. Error type 3999  
indicates that the circuit pack sent a large number of  
control channel messages to the switch within a short period of time. If  
Error Type 1538 is also present, then the circuit pack was taken  
out-of-service due to hyperactivity. If Error Type 1538 is not present, then  
the circuit pack has not been taken out-of-service, but it has generated  
50% of the messages necessary to be considered hyperactive. This may  
be completely normal during heavy traffic periods. However, if this error  
type is logged when the circuit pack is being lightly used, it may indicate a  
problem with the circuit pack or the equipment attached to it.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following tables when  
inspecting errors in the system. By clearing error codes associated with the SAKI  
Sanity Test, for example, you may also clear errors generated from other tests in  
the testing sequence.  
Use the list configuration control command to find the Tone-Clock Circuit Pack  
Code of the system. Look for the Short and Long Test Sequences according to  
the Tone-Clock Circuit Pack Code.  
Table 3-498. System Technician-Demanded Tests:  
TONE-BD (TN756 only)  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
SAKI Sanity Test (#53) (a)  
D/ND  
D
X
X
X
X
X
X
X
X
Clock Health Inquiry Test (#46)  
X
X
X
X
ND  
ND  
ND  
ND  
ND  
ND  
ND  
Control Channel Loop Around Test (#52) (a)  
Tone Detection Verification Test (#42) (b)  
Tone Detection Audit/Update Test (#43) (b)  
Tone Generator Crosstalk Test (#90) (b)  
Tone Generator Transmission Test (#40) (b)  
Tone Generator Audit/Update (#41) (b)  
X
X
1. D = Destructive, ND = Non-destructive  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-BD (Tone-Clock Circuit Pack)  
3-1137  
Notes:  
a. Refer to XXX-BD (Common Port Circuit Pack) documentation for  
descriptions of these tests.  
b. Refer to TONE-PT (Tone Generator) documentation for descriptions of  
these tests.  
Table 3-499. System Technician-Demanded Tests:  
TONE-BD (TN2182 only)  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
SAKI Reset Test (#53) (a)  
D/ND  
X
X
X
X
X
X
X
X
X
X
X
X
Clock Health Inquiry Test (#46)  
X
X
Control Channel Loop Around Test (#52) (a)  
Tone Generator Crosstalk Test (#90) (b)  
Tone Generator Transmission Test (#40) (b)  
Tone Generator Audit/Update (#41) (b)  
TDM Bus Clock Circuit Status Inquiry Test (#148) (c)  
TDM Bus Clock Slip Inquiry (#149) (c)  
TDM Bus Clock PPM Inquiry Test (#150) (c)  
TDM Bus Clock Parameter Update Test (#151) (c)  
Board Type Check Test (#574) (c)  
X
X
X
X
X
X
X
Standby Reference Health Check Test (#651) (c,)  
1. D = Destructive, ND = Non-destructive  
Notes:  
a. Refer to XXX-BD for descriptions of these tests.  
b. Refer to TONE-PT for descriptions of these tests.  
c. Refer to TDM-CLK for descriptions of these tests.  
Clock Health Inquiry Test (#46)  
This inquiry reads special data stored in memory to determine if this Tone-Clock  
circuit pack had a loss of any of three clock types:  
■
■
■
SYSCLK  
SYSFM  
SYSDCLK  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-BD (Tone-Clock Circuit Pack)  
3-1138  
If this data indicates this Tone-Clock circuit pack had a loss of any of these  
clocks, the inquiry reports FAIL. In addition, if TDM-CLK error 1 is at threshold,  
this test will FAIL. TDM-CLK error 1 indicates a suspect clock is at the edge of its  
specified frequency. If the circuit pack did not have a loss of clock or TDM-CLK  
error 1 at threshold, the inquiry reports PASS.  
This is not really a test, in the sense that it simply reports status held by the  
system, and does not generate new information or raise alarms. If this test fails  
with no error code, there is at least one Major alarm against a Tone-Clock circuit  
pack. If this test fails with an error code of 1, there is at least one Minor off-board  
alarm against a TDM-CLK.  
Table 3-500. TEST #46 Clock Health Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
FAIL  
Internal System Error.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
none  
This Tone-Clock circuit pack had an apparent loss of clock. One or more of  
error types 2049, 2305, 3834, and 3872 will appear in the error log. Correct  
the problem according to the appropriate error log entries. Once this test  
fails, the only way to make it pass, and to retire the associated alarm, is to  
repair the problem and to execute the set tone-clock PC override  
command against the indicated Tone-Clock circuit pack.  
NOTE:  
If power is removed from a carrier in a duplicated system, and that  
SPE has the active TONE-CLK, a MAJOR alarm is raised for the  
TONE-BD. The TONE-BD will be out of service and when running  
Test 46 (Clock Health Test) it will fail, indicating a loss of any of these  
three clocks, SYSCLK, SYSFM, and SYSDCLK.  
To restore the TONE-BD to service you must execute the set tone  
spe health-override command.  
1
FAIL  
This Tone-Clock circuit pack is suspect of having a clock at the edge of its  
specified frequency.  
1. Replace the Tone-Clock circuit pack identified in the error log. Refer to  
the ‘‘How to Replace a Tone-Clock Circuit Pack’’ section.  
PASS  
This Tone-Clock circuit pack has not reported a loss of clock.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-PT (Tone Generator)  
3-1139  
TONE-PT (Tone Generator)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
test tone-clock PC sh  
Full Name of MO  
Tone Generator  
Tone Generator  
Tone Generator  
TONE-PT  
TONE-PT  
TONE-PT  
MAJOR  
MINOR  
test tone-clock PC sh  
WARNING  
release tone-clock PC sh  
NOTE:  
Replacing the tone/clock circuit pack requires a special procedure which is  
described in the documentation for TONE-BD. That section also describes  
the LED display for this board.  
The tone generator resides on the Tone/Clock circuit pack and provides all  
system tones such as dial tone, busy tone, and so on. If an active tone generator  
fails, its port network may not have tones (see the Tone Generator Transmission  
Test #40). For instance, a user may go off-hook and hear no dial tone. This  
problem will affect only users on the same port network in which the faulty  
Tone-Clock circuit pack resides. The system will be able to process certain type  
of calls (that is, internal calls will succeed while outgoing calls will not).  
The Tone-Clock circuit pack also provides the clocks for the system and can  
serve as the synchronization reference. Therefore, when resolving alarms on the  
Tone-Clock circuit pack, the TDM-CLK (TDM Bus Clock) and SYNC  
(Synchronization) Maintenance documentation should be utilized as well as the  
TONE-BD (Tone-Clock Circuit Pack) Maintenance documentation.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-501. Tone Generator Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Any  
Test to Clear Value  
test tone-clock PC r 1  
test tone-clock PC r 2  
1
0
0
Any  
Any  
1(a)  
17664  
Tone Generator  
Audit/ Update Test  
(#41)  
MAJOR/  
MINOR  
ON  
130(b)  
None  
None  
MINOR  
MINOR  
ON  
ON  
test tone-clock PC Sh  
257(c,e)  
17667  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-PT (Tone Generator)  
3-1140  
Table 3-501. Tone Generator Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
513(d,e)  
17666  
Tone Generator  
Audit/ Update Test  
(#41)  
MINOR  
ON  
test tone-clock PC r 3  
769  
Any  
Transmission Test  
(#40)  
MAJOR/  
MINOR  
ON  
ON  
ON  
test tone-clock PC r 3  
test tone-clock PC l r 2  
test tone-clock PC r 3  
1025  
1281  
Crosstalk Test  
(#90)  
MAJOR/  
MINOR  
Any  
Tone Generator  
Audit/ Update Test  
(#41)  
MINOR  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
Notes:  
a. A failure in the tone generation facility on the indicated circuit pack has  
been detected. Replace the circuit pack. See ‘‘How to Replace a  
Tone-Clock Circuit Pack’’ in the TONE-BD section.  
b. This error type indicates that the circuit pack has been removed or has  
been insane for more than 11 minutes. To clear the error, reinsert or  
replace the circuit pack.  
c. The tone generation facility is having problems verifying that tones have  
been connected as requested.  
d. The tone generation facility may or may not be able to generate tones.  
e. Infrequent errors, at a rate which does not bring up an alarm, probably do  
not affect service, unless there are customer complaints of no tones, or  
incorrect tones which can not be explained in any other way. However, if  
an alarm is raised because this error is being repeatedly logged, then the  
circuit pack should be replaced. See ‘‘How to Replace a Tone-Clock  
Circuit Pack’’ in the TONE-BD section.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-PT (Tone Generator)  
3-1141  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following tables when  
inspecting errors in the system. By clearing error codes associated with the SAKI  
Sanity Test, for example, you may also clear errors generated from other tests in  
the testing sequence.  
Use the list configuration control command to find the Tone-Clock Circuit Pack  
Code of the system. Then look for the Short and Long Test Sequences according  
to the Tone-Clock Circuit Pack Code.  
For a system with a TN2182 Tone-Clock Circuit Pack:  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
SAKI Reset Test (#53) (a)  
D/ND  
D
X
X
X
X
X
X
X
X
X
X
X
X
Clock Health Test (#46) (b)  
X
X
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
Control Channel Loop Around Test (#52) (a)  
Tone Generator Crosstalk Test (#90)  
Tone Generator Transmission Test (#40)  
Tone Generator Audit/Update Test (#41)  
TDM Bus Clock Circuit Status Inquiry Test (#148) (c)  
TDM Bus Clock Slip Inquiry Test (#149)(e)(c)  
TDM Bus Clock PPM Inquiry Test (#150) (c)  
TDM Bus Clock Parameter Update Test (#151) (c)  
Board Type Check Test (#574) (c)  
X
X
X
X
X
X
X
Standby Reference Health Check Test (#651) (c)  
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Refer to XXX-BD (Common Port Circuit Pack) Maintenance documentation  
for descriptions of these tests.  
b. Refer to TONE-BD (Tone-Clock Circuit Pack) section for descriptions of  
these tests.  
c. Refer to TDM-CLK (TDM Bus Clock) section for descriptions of these tests.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-PT (Tone Generator)  
3-1142  
Tone Generator Transmission Test (#40)  
The purpose of this test is to verify that the tone generation hardware on the  
tone-clock circuit pack is capable of generating a subset of system tones and a  
set of test tones. This test does not verify all system tones the tone generator  
produces during normal system operation.  
The test is performed in two parts. For the first part, the Tone Generator is told to  
generate the touch-tone digits. The digits are received and checked by a Tone  
Detector touch-tone detector. If any of the digits fail, the test is repeated using a  
touch-tone detector in another Tone Detector circuit pack.  
For the second part, the Tone Generator is told to generate call progress tones  
that are detected and identified by a tone detector. These tones are:  
■
■
■
440 Hz  
2225 Hz  
Digital Count  
The tone generator is then told to generate a sequence of test tones whose  
output levels are measured by a tone detector. These tones are:  
■
■
■
■
404 Hz at 0 dB  
1004 Hz at -16 dB  
1004 Hz at 0 dB  
2804 Hz at 0 dB  
A Tone Detector general purpose tone detector listens for the tones and  
measures the quality of the tone. If any of the measured values are not within  
limits, the test is repeated using a general purpose tone detector in a different  
Tone Detector circuit pack. If the values are still out of the limits, the test will fail.  
For all the failure cases of Test #40, do the following:  
1. Check that all Tone Detector circuit packs have the same companding  
mode as that administered for the system. Correct the situation if there is a  
mismatch.  
2. Run the long test sequence: test tone-clock PC long repeat 1.  
3. If the problem persists, replace the Tone-Clock circuit pack by following  
the steps outlined in the ‘‘How to Replace a Tone-Clock Circuit Pack’’  
section.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-PT (Tone Generator)  
3-1143  
Table 3-502. TEST #40 Tone Generator Transmission Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
None  
ABORT  
ABORT  
ABORT  
ABORT  
The system was not able to allocate all the resources needed for this test  
or there was an Internal System Error.  
1
The system could not allocate all the resources needed to test the DTMF  
tones.  
1001  
1002  
The system was not able to put the tone generation facility in the  
appropriate mode to test it.  
The system could not allocate time slots for the test connection. This can  
happen when the system is heavily loaded. If the system is not heavily  
loaded, then test the TDM Bus via the test tdm port-network PN#  
command. Refer to TDM-BUS section for details.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test connection. This  
can happen when the system is heavily loaded or there is not a Tone  
Detector circuit pack in the port network where this test is being executed.  
1. Make sure there is a Tone Detector circuit pack installed.  
2. Allow approximately 1 minute for Tone Detector maintenance to run on  
the newly inserted Tone Detector circuit pack.  
3. Retry the command at 1-minute intervals a maximum of 5 times.  
1022  
ABORT  
Tone detection for the system is administered as wide broadband (tone  
detection mode 5), and the Tone Detector used for this test was not a  
TN2182. GPTD ports on other types of Tone Detector circuit packs are  
taken out of service since they cannot provide the administered function.  
1. Change the tone-detection mode administered on the  
system-parameters country-options form.  
Or  
2. Remove all non-TN2182 circuit packs from the system.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period. System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
DTMF generation failed for the active tone generator.  
Generation of 440-Hz failed.  
1 (a)  
FAIL  
FAIL  
FAIL  
FAIL  
105 (a)  
109 (a)  
110 (b)  
Generation of 2225-Hz failed.  
Generation of 404-Hz level invalid.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-PT (Tone Generator)  
3-1144  
Table 3-502. TEST #40 Tone Generator Transmission Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Generation of 1004-Hz low level invalid.  
111 (b)  
112 (b)  
113 (b)  
FAIL  
FAIL  
FAIL  
Generation of 1004-Hz high level invalid.  
Generation of 2804-Hz level invalid.  
Generation of digital count sequence invalid.  
Generation of quiet tone failed.  
115 (b,c) FAIL  
120 (a)  
FAIL  
FAIL  
FAIL  
FAIL  
FAIL  
PASS  
1044 (a)  
1045 (a)  
1046 (a)  
1047 (a)  
DTMF generation failed to generate Digit 1 for the standby tone generator.  
DTMF generation failed to generate Digit 5 for the standby tone generator.  
DTMF generation failed to generate Digit 9 for the standby tone generator.  
DTMF generation failed to generate Digit D for the standby tone generator.  
The tone generation facility is able to generate and transmit all the tones.  
Notes:  
Replacing the circuit pack is a service disrupting procedure. The test should be  
run several times with more than one failure before the replacement policy  
specified in the following notes is executed. Use the procedure described in  
‘‘How to Replace a Tone-Clock Circuit Pack’’ in the TONE-BD section.  
a. All the failure error codes marked with (a) will affect users. When the tone  
generation facility fails, replace the faulty Tone-Clock promptly.  
b. All the failure error codes marked with (b) are almost transparent to the  
user. Users may or may not hear any noisy tones. This type of failure  
affects other MOs. Maintenance may not be able to run on other objects  
which use the tone generation facility (that is, Tone Detector Circuit Pack  
maintenance). In this case, the Tone-Clock circuit pack can be replaced  
as suitable to the customer.  
c. Error code 115 may also be caused by TDM Bus corruption. This normally  
means a physical problem with bent backplane pins, TDM/LAN Bus  
cabling, or TDM/LAN Bus terminators. Such physical problems should  
especially be suspected if board replacement or other physical activity  
has occurred just before this error is observed.  
Use display errors to look for errors on other circuit packs in the carriers  
of the same Port Network as the Tone-Clock. If any are found, they should  
be resolved if possible, and the Tone-Clock circuit pack retested. If this  
does not clear the problem, the Tone-Clock circuit pack should be  
replaced and the new one tested. If the problem persists, follow  
instrucDtioownnslofaodrfrToDmMWwBwu.Ssommaaniunatlse.cnoamn.cAell Minantuhaisls SmeaarnchuaAnl.d Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-PT (Tone Generator)  
3-1145  
Tone Generator Update/Audit Test (#41)  
The tone generation facility is refreshed with all the time slot tone information.  
This test also triggers in-line error messages the Tone-Clock circuit pack  
generates when it detects problems by itself.  
A check is also made between the type of tone-clock being tested and the type  
of tone-clock needed based on system administration. The administration on the  
system-parameters country-options form requires a TN2182 circuit pack.  
Table 3-503. TEST #41 Tone Generator Update/Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
none  
ABORT  
ABORT  
FAIL  
The system was not able to allocate all the resources needed for this test.  
System resources required for this test are not available.  
2100  
1
The system requires a TN2182 tone-clock to support the currently  
administered country-options tone generation parameters.  
1. Check the administration on the system-parameters country-option  
form. Specifically, the Base Tone Generation Set on page 1 and any  
custom tone administration beginning on page 2.  
2. Replace existing tone-clock circuit packs with a TN2182.  
2
FAIL  
The system requires TN2182 tone-clocks to support the currently  
administered country-options tone generation parameters.  
1. Check the administration on the system-parameters country-option  
form. Specifically, the Base Tone Generation Set on page 1 and any  
custom tone administration beginning on page 2.  
2. Replace existing tone-clock circuit packs with TN2182s.  
PASS  
The tone generation facility has been successfully refreshed with its  
time-slot translation and system administration is consistent with this type  
of tone-clock.  
1. Display the Hardware Error Log via the display errors command to  
make sure this circuit pack did not generate new errors.  
Tone Generator Crosstalk Test (#90)  
This test checks the ability of the Tone Generator to talk on a specific time slot.  
The other idle time slots are checked to make sure the Tone Generator put the  
tone on only the specified time slot.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TONE-PT (Tone Generator)  
3-1146  
Table 3-504. TEST #90 Tone Generator Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
None  
ABORT  
Internal System Error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1001  
1002  
ABORT  
ABORT  
The system was not able to put the tone generation facility in the  
appropriate mode to test it.  
The system could not allocate time slots for the test connection. This can  
happen when the system is heavily loaded. If the system is not heavily  
loaded, then test the TDM-BUS via the test tdm port-network PN#  
command. Refer to TDM-BUS section for details.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The Tone Generator could be defective.  
FAIL  
1. Test the Tone-Clock circuit pack again via the test tone-clock PC  
command  
2. If the test fails again, look at the Hardware Error Log for Tone Detector  
circuit pack errors.  
3. If there are Tone Detector circuit pack errors, refer to Tone Detector  
Maintenance documentation (DTMR-PT, GPTD-PT, CLAS-PT, ETR-PT)  
to resolve these errors first.  
4. If there are no Tone Detector circuit pack errors, then the Tone-Clock  
circuit pack should be replaced. See ‘‘How to Replace a Tone-Clock  
Circuit Pack’’ in the TONE-BD section.  
PASS  
The tone generation facility is able to put tones out.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TRANS-ID (Translation-ID)  
3-1147  
TRANS-ID (Translation-ID)  
MO Name (in  
Alarm Log)  
Alarm Level  
Initial Command to Run  
Full Name of MO  
Translation-ID  
TRANS-ID  
MAJOR  
N/A  
Both the system processor and the PCMCIA translation card have matching ID  
numbers. When the system detects a mismatch between the two numbers, the  
system:  
■
raises a MAJOR off-board alarm (TRANS-ID) against ports 01A or 01B.  
■
displays the warning: TRANS-ID INTERVAL EXPIRATION: x days;  
call Lucent distributor immediately.x days is the grace  
period during which only Lucent Services logins can save translations.  
■
disables the add, change, remove, and duplicate commands if the  
translation ID is not reset prior to the expiration of the grace period (reset  
translation-id -- Lucent Services login required)  
For information about changing the grace period, see ‘‘Changing the grace  
period interval’’.  
Clearing the alarm  
■
Use the reset system 3 command with the translation card that matches  
the processor(s) in place to resolve the condition.  
■
Otherwise, contact authorized Lucent Services personnel or distributor  
immediately. They can reset the translation ID (reset translation-id).  
NOTE:  
Duplicated systems raise separate MAJOR, off-board TRANS-ID alarms  
against SPE A (01A) or SPE B (01B).  
Error Log Entries and Test to Clear Values  
Error  
Type  
Aux  
Data  
Associated  
Test  
Alarm  
Level  
On/Off  
Board  
Test to Clear Value  
Any  
None  
N/A  
MAJOR  
OFF  
Reset the system (reset system 3)  
with matching translation and  
processor(s). Contact authorized  
Lucent personnel to execute the reset  
translation-id command (requires  
Lucent Services login).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TRANS-ID (Translation-ID)  
3-1148  
Processor circuit pack replacement  
When replacing a processor circuit pack, follow the procedures in Table 3-505:  
■
Standard Reliability:  
— Begin the procedure with Step #3.  
High and Critical Reliability:  
■
— Follow the procedure through once. Work on the standby side first,  
then on the active side.  
NOTE:  
Translations loaded from a duplicated system flash card into a simplex  
system, even where one of the translation IDs on the flash card  
corresponds to the ID on the processor, results in translation ID mismatch.  
Table 3-505. Processor circuit pack replacement procedure  
√
Step  
Description  
Command  
Procedure  
1.  
Supress alarms  
change  
system-parameters  
maintenance  
Change the Alarm  
Origination to OSS  
Numbers field to neither  
(Screen 3-5).  
Press Enter to effect the  
changes.  
2.  
3.  
Busyout the standby  
PPN  
busyout  
standby-spe  
Remove the old  
processor circuit pack  
Unlatch the old processor  
circuit pack and slide it out of  
its slot (no power-down  
required).  
4.  
5.  
Replace the  
processor  
Slide the replacement  
processor circuit pack in the  
slot and latch securely.  
System detects ID  
mismatch  
The system detects the  
translation ID mismatch,  
displays the warning message,  
and generates a MAJOR alarm  
(TRANS-ID).  
6.  
Release standby PPN  
release standby-spe  
Releases the standby PPN.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TRANS-ID (Translation-ID)  
3-1149  
Table 3-505. Processor circuit pack replacement procedure — Continued  
√
Step  
Description  
Command  
Procedure  
7.  
Lucentservices resets reset translation-id  
the translation ID  
Lucent Services executes the  
command. Distributors or  
third-party vendors must also  
contact Lucent Services.  
NOTE:  
The system message,  
Cannot reset  
translation-ID  
without standby  
SPE being  
accessible, means  
that both processors  
must be sane and  
operational.  
8.  
9.  
Switch to the A-side  
reset system  
interchange  
Switches SPE control to the  
active, or A-side.  
Repeat for High and  
Critical Reliability  
systems  
Go back to Steps #3 through  
#8, this time performing the  
steps on the A-side.  
Processor replacement procedure screens  
change system-parameters maintenance  
Page  
1 of  
2
SPE B  
MAINTENANCE-RELATED SYSTEM PARAMETERS  
OPERATIONS SUPPORT PARAMETERS  
Product Identification: 1501137003  
First OSS Telephone Number:  
Second OSS Telephone Number:  
Alarm Origination to OSS Numbers: neither  
Cleared Alarm Notification? n  
Restart Notification? n  
Abbrev Alarm Report? y  
Abbrev Alarm Report? n  
Suspension Threshold: 5  
Test Remote Access Port? n  
CPE Alarm Activation Level: none  
Customer Access to INADS Port? n  
Repeat Dial Interval (mins): 7  
SCHEDULED MAINTENANCE  
Start Time: 01 : 00  
Daily Maintenance: daily  
Control Channel Interchange: daily  
SPE Interchange: daily  
Stop Time: 01 : 01  
Save Translation: no  
System Clocks Interchange: daily  
Screen 3-5. Maintenance-related system parameters (change system-parameters  
maintenance)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TRANS-ID (Translation-ID)  
3-1150  
Changing the grace period interval  
NOTE:  
The following procedure requires a Lucent Services login and is for their  
use only.  
Follow the procedure in Table 3-506 to change the grace period interval.  
Table 3-506. Procedure to change the grace period interval  
√
Step  
Description  
Command  
Procedure  
1.  
Type the command  
change  
See Screen 3-6.  
system-parameters  
security  
2.  
3.  
Go to page 2  
Scroll to page 2 of the form.  
Change the field value  
Set the Translation ID  
Number Mismatch  
Intervalfield to a number  
between 1 and 90 (default is  
5). This is the number of days  
that the system allows access  
to system administration  
commands (add, change,  
remove, and duplicate)  
following detection of a  
translation ID mismatch.  
Press Enter to save the  
change.  
NOTE:  
The Translation ID  
Number Mismatch  
Intervalfield can only  
be changed by Lucent  
Services.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TRANS-ID (Translation-ID)  
3-1151  
Grace period interval screen  
change system-parameters security  
SECURITY-RELATED SYSTEM PARAMETERS  
SECURITY VIOLATION NOTIFICATION PARAMETERS  
SVN Station Security Code Violation Notification Enabled? n  
Originating Extension: ____  
Station Security Code Threshold: 10  
Announcement Extension: ____  
Referral Destination? n  
Time Interval: 0:03  
STATION SECURITY CODE VERIFICATION PARAMETERS  
Minimum Station Security Code Length: 4  
Station Security Code for Terminal Self-Administration Required: n  
SECURITY TOOLKIT LOCK PARAMETERS  
SYSAM-LCL? n  
MAINT? n  
SYSAM-RMT? n  
SYS-PORT? n  
Translation-ID Number Mismatch Interval (days): 5  
Screen 3-6. Security-related system parameters (change system-parameters security)  
Field definition  
This is the number of days (between 1 and 90, default is 5)  
that the system allows access to system administration  
commands (add, change, remove, and duplicate)  
following detection of a translation-ID mismatch.  
Translation-ID  
Number Mismatch  
Interval (days)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TR-LN-BD (Trunk Line Board)  
3-1152  
TR-LN-BD (Trunk Line  
Board)  
The TN797 Analog Trunk and Line circuit pack provides 8 ports, any of which  
may be administered as one of the following:  
Table 3-507. TN797 Analog Trunk and Line circuit pack – port  
administration  
Function  
Group Type  
Trunk Type  
LED MWI  
co  
fx  
wats  
Central Office trunk  
(CO)  
loop start  
ground start  
CAMA/E911 trunk  
cama  
did  
Direct Inward  
Dialing (DID) trunk  
wink start  
immed start  
Analog Line  
on-or-off premises  
with/  
without MWI  
n/a  
n/a  
In the U.S., Canada, and like countries, all CO trunk ports of TN797 Analog Trunk  
and Line circuit pack should be administered as ground start (GS) trunks rather  
than as loop start trunks, because GS signaling provides disconnect supervision,  
and loop start does not. If for some reason, a port on the TN797 must be  
administered as loop start, it must be administered as one-way only – either  
incoming or outgoing – not only at the DEFINITY switch, but also at the CO  
switch. This is necessary to avoid collisions, i.e., “glare”, and other highly  
undesirable conditions.  
The TN797 Analog Trunk and Line circuit pack does not support Neon Lamp  
Message Waiting Indication (MWI). No maintenance of the terminal connected to  
the Neon Analog Line circuit pack is performed.  
For circuit pack problems, refer to the “XXX-BD (common port circuit pack)”  
maintenance documentation.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TSC-ADM (Administered Temporary Signaling Connections)  
3-1153  
TSC-ADM (Administered Temporary  
Signaling Connections)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
TSC-ADM  
none  
none  
Administered Temporary Signaling  
Connections  
TSC-ADM  
none  
none  
Administered Temporary Signaling  
Connections  
No alarms are generated for the TSC-ADM (Administered Temporary Signaling  
Connections) MO. Due to the unusual length of the full name of this MO (that is,  
Administered Temporary Signaling Connections), the abbreviation Administered  
TSC is used often in this Maintenance documentation.  
In general, administered temporary signaling connections provide a path through  
ISDN-PRI switches for supplementary D-channel messages. ISDN-PRI  
applications [that is, Distributed Communications System (DCS)] use temporary  
signaling connections to exchange user information across an ISDN-PRI  
network. What makes Administered Temporary Signaling Connection unique is  
that these particular Temporary Signaling Connections stay active for an  
extended period time (that is, similar to a permanent data connection). These  
ADM Temporary Signaling Connections are used for DCS features that require a  
NCATSC, and the ADM TSC serves as the logical channel function in a DCS  
network.  
A Non-Call Associated Temporary Signaling Connection (NCATSC) is a virtual  
connection established within a D-channel. The NCATSC connection provides  
user to user service by exchanging USER INFORMATION messages through the  
virtual connection in a D-channel without associating any B-channel connections.  
An Administered TSC is a special NCA Administered TSC defined for the DCS  
over the ISDN-PRI D-channel application of G3iV1.1-286 or G3iV2-386. The  
Administered TSC connection is a special type of NCATSC that has an  
administratively defined endpoint and is established for an extended period of  
time.  
There are two types of ADMTSCs:  
■
Permanent  
TSCs are established by the originating PBX (that is Near-end ADM TSC)  
or by the terminating PBX (that is, Far-end ADM TSC). Once these  
ADMTSCs are established, they remain active.  
■
As-Needed  
TSCs are established on an as-needed basis. In this case, the ADMTSC is  
established whenever it is needed, and not before.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TSC-ADM (Administered Temporary Signaling Connections)  
3-1154  
ADMTSC maintenance provides a strategy to verify that a far-end can respond to  
an ISDN-PRI USER INFORMATION TSC heartbeat message, thereby indicating  
that user to user signaling is functioning. In addition, maintenance can retrieve  
the status of the ADMTSC’s connection state.  
Since ADMTSCs are administered on a per signaling group basis, the health of  
an ADMTSC also depends on the state of the D-channel or D-channel pair  
administered per signaling group. Refer to ISDN-SGR (ISDN-PRI Signaling  
Group) Maintenance documentation for details on ISDN-PRI NFAS and  
D-channel Backup maintenance. The two administration commands for  
ADMTSCs are as follows:  
■
add signaling group #  
■
change signaling group #  
The two maintenance commands for ADMTSCs are as follows:  
■
test tsc-administered signaling group #[/tsc index]  
status tsc-administered signaling group #/tsc index  
■
Hardware Error Log Entries and Test to Clear  
Values  
ADM TSC Error Log Entries  
Alarm  
Level  
On/Off  
Board  
Error Type  
Aux Data  
Associated Test  
Test to Clear Value  
3840-3967(a) tsc index # test tsc-administered  
Notes:  
a. There is no Test to Clear Value for error types 3840-3967. The error types  
provide the following additional data that may prove useful when tracking  
down problems.  
This error indicates that a TSC Heartbeat Inquiry Test was run on an Active  
far-end Administered TSC from the switch. Upon receiving the heartbeat  
message, the network communicated to the switch that the call reference  
value is not currently in use on the ISDN interface. As a result, the error  
was logged. Check the signaling group status of the D-channel or  
D-channel pair via the status signaling-group <group> command for the  
Administered TSC. Check the status of the Administered TSC via the  
status tsc-administered command. Also check the administration of the  
Administered TSC on the switch.  
This error may only be affecting service for some DCS customers. Upon  
receipt of this error condition, the switch tears down and re-establishes the  
ADMTSC within 20 minutes.  
b. The port field in the error log contains the signaling group number for  
TSC-ADM errors.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TSC-ADM (Administered Temporary Signaling Connections)  
3-1155  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the following tables when  
inspecting errors in the system. By clearing error codes associated with the TSC  
Heartbeat Inquiry Test, for example, you may also clear errors generated  
from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
TSC Heartbeat Inquiry Test (#604)  
ND  
1. D = Destructive; ND = Nondestructive  
TSC Heartbeat Inquiry Test(#604)  
This test can be invoked by system technician personnel for any ADMTSC  
administered in the switch. The following table indicates the possible error  
conditions that might be encountered when the test is invoked. Most of the error  
conditions do not log an error, but switched services may take some type of  
recovery action in certain instances.  
This test sends a USER INFORMATION TSC heartbeat message inquiry across  
an Administered TSC to determine if the far-end can respond to a USER  
INFORMATION TSC heartbeat message.  
Table 3-508. TEST #604 TSC Heartbeat Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Reissue the test tsc-administered command at 1-minute intervals a  
maximum of 5 times.  
1005  
1113  
ABORT  
The Administered TSC does not exist.  
1. Display the administration for the Administered TSC.  
2. If an Administered TSC is exists, reissue the test tsc-administered  
command.  
ABORT  
The D-channel is out-of-service.  
1. Refer to the ISDN-LNK (ISDN-PRI Signaling Link Port) Maintenance  
documentation.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TSC-ADM (Administered Temporary Signaling Connections)  
3-1156  
Table 3-508. TEST #604 TSC Heartbeat Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
There is congestion in the network.  
1145  
ABORT  
ABORT  
ABORT  
ABORT  
1. Issue the status tsc-administered command at 1-minute intervals a  
maximum of 5 times.  
2. If the congestion does not clear, disable and enable the Administered  
TSC via the change sig-group <group> command. To disable the  
Administered TSC, display the (administration) Signaling Group Form  
via the change sig-group <group> command where <group> refers  
to the number of the signaling group under which the suspect TSC is  
administered. Change the Enablefield to n. To enable the ADMTSC,  
change the Enablefield to y.  
3. If the congestion still does not clear, check other nodes in the network.  
The congestion just occurred in the network.  
1146  
1147  
1148  
1. Issue the status tsc-administered command at 1-minute intervals a  
maximum of 3 times.  
2. If congestion does not clear, disable and enable the Administered TSC  
via the change sig-group <group> command. To disable the  
Administered TSC, display the (administration) Signaling Group Form  
via the change sig-group <group> command where <group> refers  
to the number of the signaling group under which the suspect TSC is  
administered. Change the Enablefield to n. To enable the ADMTSC,  
change the Enablefield to y.  
3. If congestion still does not clear, check the other nodes in the network.  
The ADMTSC is being torn down.  
1. Issue the status tsc-administered command at 1-minute intervals a  
maximum of 3 times.  
2. If ADMTSC is still down, disable and enable the ADM TSC via the  
change sig-group <group> command. NOTE: To disable the  
ADMTSC, display the (administration) Signaling Group Form via the  
change sig-group <group> command where <group> refers to the  
number of the signaling group under which the suspect TSC is  
administered. Change the Enablefield to n. To enable the ADMTSC,  
change the Enablefield to y.  
3. If the ADMTSC is still down, check the other nodes in the network.  
The ADMTSC is enabled, but inactive (near-end).  
1. Disable and enable the ADMTSC.  
2. Reissue the test tsc-administered command.  
3. If the ADMTSC is still inactive, check the other nodes in the network.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TSC-ADM (Administered Temporary Signaling Connections)  
3-1157  
Table 3-508. TEST #604 TSC Heartbeat Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The ADMTSC is disabled.  
1149  
ABORT  
1. Enable the TSC, and see if the status indicates "active."  
2. Reissue the test tsc-administered command.  
3. If the TSC still disabled, remove the ADMTSC from the system.  
Ran out of ADMTSC resources.  
1181  
1182  
ABORT  
ABORT  
1. Reissue the test tsc-administered command at 1-minute intervals a  
maximum of 3 times.  
The BX.25 link is down at the gateway.  
1. Disable the ADMTSC.  
2. Check the status of the gateway link via the status link link-no  
command.  
3. Once the gateway link indicates an "in-service" state, enable the  
Administered TSC.  
4. Reissue the test tsc-administered command.  
2000  
ABORT  
The Administered TSC is not responding to a TSC heartbeat inquiry.  
1. Retry the test tsc-administered command at 1-minute intervals a  
maximum of 3 times.  
2. If the problem continues to fail, obtain the status of the D-channel or  
D-channel pair associated with the ADMTSC via the status sig-group  
<group> command. If the D-channel is INS (that is, in-service) and the  
status of the ADMTSC appears to be active, disable and enable the  
ADMTSC through administration. NOTE: To disable the ADMTSC,  
display the (administration) Signaling Group Form via the change  
sig-group <group> command where <group> refers to the number of  
the signaling group under which the suspect TSC is administered.  
Change the Enablefield to n. To enable the ADMTSC, change the  
Enablefield to y.  
3. Reissue the test tsc-administered command.  
4. If the test fails, check the ADMTSC node on the other side of the  
network to verify that the ADM TSC is indeed active.  
2012  
ABORT  
Internal System Error.  
1. Reissue the test tsc-administered command at 1-minute intervals a  
maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
TSC-ADM (Administered Temporary Signaling Connections)  
3-1158  
Table 3-508. TEST #604 TSC Heartbeat Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The Administered TSC is not active (far-end).  
1. Reissue the test tsc-administered command.  
1
FAIL  
2. Verify that the Administered TSC node on the other side of the network  
is active.  
3. Disable and enable the Administered TSC.  
4. Retry the test tsc-administered command.  
Facility IE (Information Element) reject.  
2
FAIL  
1. Check all other nodes in the network, and make sure Administered  
TSC is active.  
PASS  
The Administered TSC responded to a heartbeat.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TTR-LEV (TTR Level)  
3
3-1159  
TTR-LEV (TTR Level)  
MO Name (in  
Alarm Log)  
Alarm Level  
Initial Command to Run  
Full Name of MO  
1
TTR-LEV  
WARNING  
See Note  
TTR Level  
1. See the "Repair Procedure for the TTR Level Maintenance Object" section.  
A TN2182 Tone-Clock/Detector/Call Classifier and the TN744D Call Classifier  
circuit packs provide touch tone receivers (TTRs or DTMR-PTs) that are devices  
used to interpret touch tone calling signals and to translate the dual tones into the  
following valid digits: 0 through 9, *, and #. A Tone Detector circuit pack is a  
resource shared by all PBX users and also has general purpose tone detector  
ports (GPTD-PTs) to detect call progress tones, modem answer tones, and  
transmission test tones. Call Classifier Ports (CLSFY-PTs) have also been added  
to detect voice or network intercept tones. A Call Classifier Port (CLSFY-PT) can  
function as either a DTMR-PT or as a GPTD-PT.  
When a user places a call from a digital or analog voice terminal on the switch, a  
TTR is needed to interpret the dual tone multifrequency signals sent from the  
voice terminal. The TTR is in use until the total number of digits needed is  
collected or until a time-out occurs. Dial tone is supplied to a user after receipt of  
an off-hook signal which signifies that a TTR is connected and ready to receive  
digits. For example, if there are 20 TTRs in the system being used simultaneously  
by 20 users at a given time, then the 21st user would not receive dial tone until a  
TTR becomes available. It is for this reason that it is necessary to have sufficient  
tone detectors in the system to prevent delay in receiving dial tone. The TTR-LEV  
errors can be used to determine a shortage of tone detectors. Use the list  
measurements tone-receiver command to determine tone detector usage. The  
minimum threshold values assigned on the Maintenance-Related System  
Parameters Form for TTRs (DTMR-PTs), CPTRs (GPTD-PTs), and CCRs  
(CLSFY-PTs) should match the number of touch tone receivers (TTR) and tone  
detectors (GPTD-PT) in the system. The numbers are 8 CCRs for each Call  
Classifier Port (TN744D) circuit pack. The threshold values are administered via  
the change system-parameters maintenance command on the  
Maintenance-Related System Parameters Form. The desired numbers are  
entered in the "TTR" (DTMR-PT), "CPTR" (GPTD-PT), and "Call Classifier"  
(CLSFY-PT) fields, respectively.  
The TTR Level (Touch Tone Receiver Level) MO is used to represent the following  
possible events:  
1. The total number of General Purpose Tone Detector Ports (GPTD-PTs),  
[also known as Call Progress Tone Receivers (CPTRs)], currently in  
service is less than the administered threshold number.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TTR-LEV (TTR Level)  
3
3-1160  
2. The total number of Dual Tone Multifrequency Receiver Ports (DTMR-PTs)  
[(also known as Touch Tone Receiver (TTRs)], currently in service is less  
than the administered threshold number.  
The TTR Level maintenance performs a monitoring function. When one of the  
above events occurs, the switch reports it. At this point, the system is still  
operating properly, but the system capacity is reduced.  
The above events can occur if:  
1. The threshold number of General Purpose Tone Detector Ports  
(GPTD-PTs) for service or the threshold number of Dual Tone  
Multifrequency Receiver Ports (DTMR-PTs) for service is administered  
incorrectly on a Tone Detector circuit pack.  
2. Too many General Purpose Tone Detector Ports (GPTD-PTs) or Dual Tone  
Multifrequency Receiver Ports (DTMR-PTs) have been taken out-of-service  
for a Tone Detector circuit pack (that is, the ports have been either  
busied-out by system technician or maintenance has taken them  
out-of-service).  
3. Too many ports have been taken out-of-service for a Call Classifier circuit  
pack (that is, the ports have been busied-out by system technician or  
maintenance has taken them out-of-service).  
4. There is an insufficient number of General Purpose Tone Detector Ports  
(GPTD-PTs) or Dual Tone Multifrequency Receiver Ports (DTMR-PTs) in the  
system for a Tone Detector circuit pack. Or there is an insufficient number  
of ports in the system for a Call Classifier circuit pack.  
Repair Procedure for the TTR Level Maintenance  
Object  
The following is a step-by-step approach to resolve the TTR Level maintenance  
alarm.  
1. Execute the display error command. Determine if the TTR-LEV warning  
alarm is raised against the GPTD-PT level, the DTMR-PT level, or the  
CLSFY-PT level. In the Hardware Error Log Table, the error type field of the  
TTR-LEV MO has a value of 2 for DTMR-PT level, a value of 4 for GPTD-PT  
level, or a value of 6 for CLSFY-PT level.  
Perform the actions described in Step 2 for the DTMR-PT, the GPTD-PT, or  
the CLSFY-PT.  
2. Issue the change system-parameters maintenance command. Check  
the administered value(s) for TTRs and CPTRs for service on the Tone  
Detector circuit packs or for CCRs on the Call Classifier Port (CLSFY-PT)  
circuit pack. If a threshold value is set too high, change it to a lower value  
via the change system-parameters maintenance command and wait  
one minute for the alarm to clear.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TTR-LEV (TTR Level)  
3
3-1161  
3. Execute the display error command. Look for a GPTD-PT, DTMR-PT, or  
CLSFY-PT that has been busied out. A port that has been busied out has a  
value of 18 in the error type field of the Hardware Error Log.  
For each of the busied-out ports, use the following procedure:  
■
Determine why the port was busied out.  
■
If the port can be placed back into service, test the port via the test  
port PCSSpp command.  
■
If all the tests pass, release the port via the release port PCSSpp  
command. Then wait one minute for the TTR Level alarm to clear.  
If this does not clear the TTR Level alarm, proceed to Step 4.  
4. Execute the display alarm command. Determine the address of the Tone  
Detector circuit pack which contains the defective (alarmed) GPTD-PT or  
DTMR-PT.  
Execute the test board PCSS long rep 3 command where PCSS is the  
address (that is, port network number, carrier designation, and slot  
address) of the Tone Detector circuit pack or Call Classifier circuit pack  
containing the defective (alarmed) GPTD-PT or DTMR-PT.  
If this does not clear the TTR Level alarm, proceed to Step 5.  
5. At this point, the only way to clear the alarm is to replace the Tone Detector  
circuit pack or Call Classifier circuit pack containing the defective  
(alarmed) GPTD-PT, DTMR-PT or CLSFY-PT.  
Hardware Error Log Entries and Test to Clear  
Values  
Table 3-509. TTR Level Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Alarm Level  
Test to Clear Value  
1 (a)  
1
2
None  
2 (b)  
WARNING (See the  
WARNING message  
below)  
OFF  
3 (c)  
4 (d)  
5 (e)  
6 (f)  
3
4
5
6
7
8
9
None  
None  
WARNING  
OFF  
WARNING  
MAJOR  
MINOR  
OFF  
OFF  
OFF  
OFF  
7 (g)  
8 (h)  
9 (i)  
MINOR  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
TTR-LEV (TTR Level)  
3
3-1162  
!
WARNING:  
The Alarm is upgraded to MAJOR if the Base Tone Generator is set to 12  
(France).  
Notes:  
a. Error code 1 does not indicate a current error condition. It indicates that  
the number of DTMR ports in service was below the administered  
threshold, but is now equal to or greater than the threshold. These errors  
are typically generated during boot time or other transitional states when  
the ports are being brought into service.  
b. The total number of DTMR ports currently in service is below the  
administered threshold. To clear the alarm, refer to the repair procedure  
described above.  
c. Error code 3 does not indicate a current error condition. It indicates that  
the number of GPTD ports in service was below the administered  
threshold, but is now equal to or greater than the threshold. These errors  
are typically generated during boot time or other transitional states when  
the ports are being brought into service.  
d. The total number of GPTD ports currently in service is below the  
administered threshold. To clear the alarm, refer to the repair procedure  
describe above.  
e. Error code 5 does not indicate a current error condition. It indicates that  
the number of Call Classifier ports (CLSFY-PT) in service was below the  
administered threshold, but is now equal to or greater than the threshold.  
These errors are typically generated during boot time or other transitional  
states when the ports are being brought into service.  
f. The total number of Call Classifier ports currently in service is below the  
administered threshold. To clear the alarm, refer to the repair procedure  
described above.  
g. There are currently no DTMR ports in service. To clear the alarm, refer to  
the repair procedure described above.  
h. There are currently no GPTD ports in service. To clear the alarm, refer to  
the repair procedure described above.  
i. There are currently no Call Classifier ports in service. To clear the alarm,  
refer to the repair procedure described above.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1163  
UDS1-BD (UDS1 Interface Circuit  
Pack)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board UUCSS sh  
test board UUCSS l  
Full Name of MO  
UDS1-BD  
UDS1-BD  
UDS1-BD  
MAJOR  
MINOR  
UDS1 Interface Circuit Pack  
UDS1 Interface Circuit Pack  
UDS1 Interface Circuit Pack  
WARNING  
test board UUCSS sh  
1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation  
(A, B, C, D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21).  
2Mbit Japan trunk (TN2242)  
The TN2242 2Mbit, 30-port trunk circuit pack supports Japanese TTC private  
networking environments. This circuit pack interfaces only with network  
equipment or other circuit packs of the same model and is incompatible with all  
other digital trunk circuit packs.  
The maintenance strategy for the TN2242 is similar to that of the TN464F DS1  
interface circuit pack. The TN2242 circuit pack is functionally the same as the  
TN464F (without ICSU) with the following exceptions:  
■
■
■
The Blue Alarm Inquiry Test (#139) always passes for the TN2242.  
The test ds1-loop command is not executed for the TN2242.  
A different initialization message is sent when the local looparound test  
(Test #135) is executed when reset board is run on a TN2242.  
■
■
Any tests associated with an Integrated Channel Service Unit (ICSU) are  
not executed, since ICSU is not supported on this circuit pack.  
Any tests associated with new functionality available with the  
video-enabled TN464F are not executed for the TN2242.  
■
■
Cyclical Redundancy Check (CRC) is not defined for this circuit pack.  
The D-Channel can be user-assigned to any port 1 - 30 when the signaling  
mode is ISDN-PRI.  
■
■
Wideband is not supported.  
Stations (OPS) are not supported.  
The TN2242 circuit pack also supports specialized versions of CAS (Channel  
Associated Signaling) and ISDN-PRI signaling that pertain to the TTC private  
networking environment in Japan.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1164  
Upgrading to TN2242  
Figure 3-45 shows the hardware connections for public network access in Japan.  
The upgrade procedure requires removing the JRC (Japan Radio Corporation)  
external converter in Figure 3-45.  
1
1
2
2
4
4
3
cydfjap1 LJK 012899  
Figure Notes:  
1. DEFINITY Release 7  
3. JRC (Japan Radio Corporation) external converter  
4. TDM facilities  
2. TN464F DS1-CONV circuit pack  
(24-trunk digital tie-trunk)  
Figure 3-45. Japanese TTC public network connections  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1165  
Figure 3-46 shows the hardware connections for private network access using  
the TN2242 circuit pack.  
1
1
2
2
3
3
4
4
cydfjap2 LJK 012999  
Figure Notes:  
1. DEFINITY Release 7  
2. TN2242 2Mbit Japan trunk circuit pack  
3. H600-513 cable assembly cable. (See ‘‘H600-513  
cable pinout’’).  
4. TDM facilities  
Figure 3-46. TN2242 Japan trunk TTC private network connections  
To upgrade a system to the TN2242 circuit pack:  
1. Busyout the TN464F DS1-CONV circuit pack (busyout board UUCSS).  
2. Remove the TN464 administration (change circuit pack, change ds1,  
and change trunk group n).  
3. Remove the TN464F circuit packs.  
4. Remove the JRC (Japan Radio Corporation) external converter and cable.  
5. Insert the TN2242 circuit packs.  
6. Connect the TN2242 to the TDM with the H600-513 cable assembly.  
7. Administer the TN2242 circuit pack (see ‘‘Administration’’).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1166  
H600-513 cable pinout  
Table 3-510 shows the pinout for the H600-513 cable assembly:  
Table 3-510. H600-513 cable assembly pinout  
TN2242  
TDM  
50-pin  
15-pin  
connection pin  
number  
connection pin  
number  
Color  
W-BL  
W-O  
Lead Designation  
Line in +  
Color  
W-BL  
W-O  
22  
4
23  
Line out -  
9
47  
Bl-W  
O-W  
Line in -  
Bl-W  
O-W  
11  
2
48  
Line out +  
Administration  
The TN2242 circuit pack requires board-level translation data. Before  
administering any ports on the circuit pack, administer the following forms:  
■
■
■
Circuit pack (change circuit pack)  
DS1 (add ds1)  
Trunk group (add trunk group n)  
Table 3-511 outlines the trunk group administration parameters that are  
required for this interface to operate successfully in Japan.  
Table 3-511. TN2242 administration  
Field  
Value  
Trunk Group form, Page 1  
Trunk Type (in/out)  
wink, delay, immed  
(all permutations)  
Trunk Signaling Type  
blank  
Answer Supervision Timeout  
Receive Answer Supervision  
Disconnect Supervision - In?  
Disconnect Supervision - Out?  
0
y
y
y
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1167  
Table 3-511. TN2242 administration — Continued  
Field  
Value  
Incoming Dial Type  
tone  
rotary  
mf (to other DEFINITYs only)  
Wink Timer for wink type  
Wink Timer for delay type  
300  
4500  
Trunk Group form, Page 3 (Administrable Timers)  
Incoming Disconnect  
Incoming Glare Guard  
Incoming Dial Guard  
Incoming Incomplete Dial Alarm  
Incoming Partial Dial  
PPS  
100  
800ms or higher  
10  
25 or higher  
18  
10 or 20  
Make (for PPS 10)  
35  
Break (for PPS 10)  
65  
Make (for PPS 20)  
15  
Break (for PPS 20)  
35  
Outgoing Disconnect  
Outgoing Glare Guard  
Outgoing Rotary Dial Interdigit  
Outgoing Seizure Response  
100  
800 or higher  
800  
5
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1168  
LEDs  
The LEDs on the faceplate of the TN2242 circuit pack indicate its status as  
described in Table 3-512.  
Table 3-512. TN2242 LED interpretation  
LED  
Meaning  
Red  
■ MAJOR alarm  
■ MINOR alarm  
■ Firmware initialization during circuit pack insertion  
A port on the circuit pack is in use.  
Yellow  
Green  
Maintenance testing is in progress on the circuit pack or  
its ports.  
Interactions with other MOs  
The TN2242 maintenance object directly interacts with these maintenance  
objects:  
■
■
■
‘‘Synchronization’’  
‘‘TN2242 trunk ports’’  
‘‘Call processing’’  
Synchronization  
The DS1 facility plays a vital role in the synchronization subsystem. The  
Tone/Clock circuit pack uses either the primary or secondary timing reference,  
whether internal (local -- Tone/Clock circuit pack) or external. TN2242 circuit  
packs can be administered as “primary” or “secondary” synchronization  
references.  
TN2242 circuit pack sends DS1 link status information to the synchronization  
reference switching algorithm that determines whether timing references should  
be switched due to failure or restore conditions.  
TN2242 trunk ports  
The TN2242 circuit pack MO is responsible for monitoring the health of the DS1  
facility. If a DS1 facility goes down, then that facility’s DS1 circuit pack instructs  
all DS1 port MOs associated with the facility to place their trunks (or ISDN-PRI  
signaling link) in an out-of-service state.  
Call processing  
The busyout board command tears down all calls and signaling links associated  
with a TN2242 circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1169  
TN2242 serviceability  
Hardware connections  
This circuit pack can be  
■
mated to another circuit pack of the same type when interconnecting two  
DEFINITYs.  
■
■
directly-connected to the TDM network device.  
directly-connected to another vendor PBX using ISDN PRI signaling.  
Loopbacks  
■
■
There is no process to automatically signal the remote end to provide  
loopbacks for testing purposes. All loopbacks to be tested with a single  
circuit pack must be local loopbacks on the circuit pack.  
Remote loopbacks may be possible with the TDM network equipment with  
appropriate coordination between BCS Services Technicians and the  
service technicians of the TDM equipment (considered a CPE device).  
The TN464C, D, E, and F Universal DS1 Interface circuit packs provide an  
interface to the DS1 facility and are designed to support 24 DS0 channels on a  
1.544 Mbps DS1 link or 32 DS0 channels on a 2.048 Mbps link. (The 32-channel  
interface is not supported on G3r V1 systems.) The DS0 channels can be  
administered as trunks to other switches, lines to off-premises stations, ports to  
line-side PRI terminating devices, or ports to other line-side non-PRI terminating  
devices. (DS0 channels on TN464/Bs can only be administered as trunks to other  
switches.) For more information on how TN464 ports can be used, see the  
following sections in this chapter ISDN-SGR, ISDN-TRK, ISDN-LNK, PE-BCHL,  
TIE-DS1, CO-DS1, DID-DS1, OPS-LINE and WAE-PT. For information on other  
DS1 circuit packs, see DS1-BD.  
Throughout this section on the UDS1-BD MO name, the term TN464 will mean  
any TN464C or later suffix UDS1 circuit pack. If part of this section refers to a  
specific suffix TN464 board, it will be noted as such.  
The UDS1 maintenance strategy includes logging in-line errors reported by the  
UDS1 circuit pack, running tests for error diagnosis and recovery, and raising or  
clearing maintenance alarms.  
TN464 circuit packs support the following:  
■
■
■
■
■
Digital Tie, CO, and DID trunks  
DS1 off-premises (OPS) lines  
Narrowband and wideband access endpoint ports  
ISDN-PRI trunks and accompanying signaling channel  
PRI endpoint ports (PE-BCHL) and accompanying signaling channel  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1170  
The TN464 supports digital Tie, CO, and DID trunks, and OPS lines. On-board  
firmware performs call control signaling for the Tie, CO and DID trunks and OPS  
lines. ISDN-PRI trunk and PRI endpoint signaling (Q.921, Q.931) is received and  
generated by system software and is transmitted on a system link through the  
TN1655 Packet Interface and packet bus to the UDS1 where it is placed on the  
D-channel. Signaling over the DS1 link has to be synchronized between the  
transmitting and receiving ends to ensure error-free communication. Refer to  
‘‘SYNC (Synchronization)’’ in this chapter for details.  
Each trunk, line or endpoint has its own maintenance strategy but all depend on  
the health of the UDS1 Interface circuit pack. Refer to the following sections for  
details: TIE-DS1, CO-DS1, DID-DS1, OPS-LINE, ISDN-TRK, ISDN-LNK,  
ISDN-SGR, WAE-PT and PE-BCHL. The maintenance strategy for the TN464  
UDS1 Interface circuit pack (UDS1-BD) is very similar to the maintenance  
strategy for the TN767 DS1 Interface circuit pack (DS1-BD). The same  
commands are used for administering and testing the boards. The differences in  
maintenance strategy between the boards are due to the UDS1 circuit pack’s  
direct interface to the Packet Bus which is used for ISDN-PRI signaling  
(ISDN-LNK). While both the TN464 and TN767 can support ISDN-PRI  
B-channels, ISDN-PRI D-channel signaling applications require a TN464 UDS1  
circuit pack.  
The TN464F or later circuit pack combined with the 120A1 CSU Module forms an  
Enhanced Integrated CSU. The new 120A1 CSU Module, when combined with  
the functionality provided by the TN464F hardware and firmware, and new switch  
software, provides functionality equivalent to an external stand-alone Lucent ESF  
T1 CSU. The 120A1 CSU Module connects to the TN464F circuit pack on the I/O  
connector panel on the back of the port carrier. The new CSU Module, thus  
becomes an integrated part of the DEFINITY. system. Throughout the document,  
the term 120A1 will mean a 120A1 or later suffix CSU Module.  
The Enhanced Integrated CSU is for use in the United States of America with  
1.544 Mbps DS1 service. For further details on the 120A1 CSU Module see  
DEFINITY Communications System Generic 1, Generic 2, and Generic 3 V1 and  
V2 - Integrated CSU Module Installation and Operation.  
The TN464F and 120A1 CSU Module support on-demand loopback tests that  
assist in the detection of faults between the TN464F circuit pack and the CSU  
Module, between the Integrated CSU and the optional Customer Premises  
Loopback Jack, or between the Integrated CSU and remote CSU. These  
loopback tests are explained in detail later in this UDS1-BD section, but Figure  
3-47 gives a high level overview of the loopback points.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1171  
NETWORK ENVIRONMENT  
NET  
CPE  
CPE  
NET  
NET-  
DS1  
CSU  
CSU  
DS1  
SMRT  
JACK  
LPBK  
JACK  
LPBK  
JACK  
SMRT  
JACK  
WORK  
BRD  
MOD  
MOD  
BRD  
Remote end  
Local end  
CSU module to CSU module  
CPE  
NETWORK  
SMRT  
DS1  
BOARD  
CSU  
LPBK  
JACK  
MOD  
JACK  
PLB  
BLB  
ELB LLB RLB  
CLJ-LB  
Local end loop backs  
NETWORK  
SMRT  
CPE  
CSU*  
MOD  
DS1  
LPBK  
JACK  
BOARD  
JACK  
R-LLB  
Remote end loop backs (* CSU or External CSU)  
Figure 3-47. High Level Overview Of Loopback Points  
The following list of acronym definitions are for the Figure 3-47:  
■
■
■
■
■
■
■
■
■
PLB = Payload Loopback  
BLB = Board Loopback  
ELB = Equipment Loopback  
LLB = Line Loopback  
RLB = Repeater Loopback  
CLJ = Loopback Jack Loopback  
R-LLB = Remote Line Loopback  
SMRT = Smart Jack  
LPBK = Loopback  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1172  
Circuit Pack Administration and Options  
The DS1 configuration for each circuit pack is administered on the DS1 Circuit  
Pack form. Bit Rate is set to 1.544 Mbps for 24-channel systems, and 2.048  
Mbps for 32-channel systems. Country Protocol is used to drive layer 3 protocol  
decisions based on PRI specifications specific to a given country (not those  
related to specific features). This Country Protocol is independent of the Country  
parameter administered on the country-options system-parameters form.  
Different UDS1 circuit packs may be administered with different Country  
Protocols, allowing the switch to act as a gateway between two incompatible  
ISDN-PRI implementations (for example, between two different countries). US  
systems use country protocol 1. Near-End CSU Type is set to other for no CSU  
installed or for an external CSU such as an Lucent ESF T1 CSU, or integrated for  
the 120A1 CSU Module or the 401A T1 Sync Spliltter. Answering integrated will  
cause additional fields to be displayed for administering the Enhanced  
Integrated CSU Module. E1 Sync-Splitter? is set to y if a 402A or 403A E1 Sync  
splitter is used to provide timing to an ATM switch. In addition to the above there  
are numerous other fields defining such parameters as framing modes, line  
coding companding mode and so on. For details, see DEFINITY  
Communications System Generic 3 V2 Implementation, 555-230-653, and  
DEFINITY Communications System Generic 2.2 and Generic 3 V2  
DS1/CEPT/ISDN-PRI Reference, 555-025-107.  
Two option jumpers located on the side of the TN464C/D circuit pack must be  
installed correctly. The figures on the following page shows how to configure the  
circuit pack for 24-channel or 32-channel DS1, and for 75*W (coaxial) or 120*W  
trunk connections. The channel selection must match the parameters  
administered on the corresponding DS1 Circuit Pack Form. (US applications use  
24 Channels.)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1173  
Top  
TN464C/D  
24/32 Channel Selector  
75/120 Ohm Selector  
Bottom  
Backplane Connectors  
Faceplate  
Figure 3-48. TN464C/D DS1 Option Jumpers  
24 CHNL  
32 CHNL  
Insert the jumpers into the blocks  
so as to join the center row of  
pins and the row designating the  
desired options.  
120 OHM  
75 OHM  
Figure 3-49. TN464C/D DS1 Option Jumpers (Continued)  
The option switch located on the component side of the TN464E/F circuit pack  
must be set correctly. Figure 3-50 shows how to configure the circuit pack for  
24-channel or 32-channel DS1. The channel selection must match the  
parameters administered on the corresponding DS1 Circuit Pack Form. (US  
applications use 24 Channels.)  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1174  
Ω
Ω
Figure 3-50. TN464E/F DS1 Option switches  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1175  
Error Log Entries and Test to Clear Values  
Table 3-513. DS1 Interface Circuit Pack Maintenance Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Alarm Level  
Test to Clear Value  
1
0
0
0
Any  
Any  
Any  
ON  
test board UUCSS  
2
1(a)  
Circuit pack removed or  
SAKI Test (#53)  
MIN/WRN  
18(b)  
23(c)  
125(d)  
257  
0
0
busyout board UUCSS  
WARNING  
WARNING  
OFF  
OFF  
ON  
release board UUCSS  
add ds1 UUCSS  
3
none 3  
65535  
None  
MIN/WRN  
Control Channel Loop  
Test (#52)  
MINOR  
ON  
test board UUCSS l r 20  
257(e)  
513(f)  
514(g)  
769(h)  
770(i)  
1025(e)  
1281  
Any  
None  
3
Any  
MIN/WRN  
ON  
ON  
ON  
ON  
3
46086  
46085  
46096  
4363  
Any  
MIN/WRN  
3
MIN/WRN  
3
MIN/WRN  
NPE Audit Test (#50)  
3
Loss of Signal Alarm  
Inquiry Test (#138)  
MIN/WRN  
OFF  
OFF  
OFF  
OFF  
ON  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
1300(j)  
1301(k)  
1302(l)  
1303(m)  
1310(n)  
1311(o)  
1312(p)  
1313(q)  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Any  
Loss Of Signal Alarm  
Inquiry Test (#138)  
WARNING  
WARNING  
Loss Of Signal Alarm  
Inquiry Test (#138)  
3
Loss Of Signal Alarm  
Inquiry Test (#138)  
MIN/WRN  
3
Loss Of Signal Alarm  
Inquiry Test (#138)  
MIN/WRN  
Board Loopback Test  
(#1209)  
MINOR  
ON  
test ds1-loop UUCSS  
ds1/csu-loopback-tests  
3
Equipment Loopback  
Test (#1210)  
MIN/WRN  
OFF  
OFF  
OFF  
test ds1-loop UUCSS  
ds1/csu-loopback-tests  
3
Repeater Loopback  
Test (#1211)  
MIN/WRN  
test ds1-loop UUCSS  
ds1/csu-loopback-tests  
3
CPE Loopback Jack  
Test (#1212)  
MIN/WRN  
test ds1-loop UUCSS  
end-loopback/span-test  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1176  
Table 3-513. DS1 Interface Circuit Pack Maintenance Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Alarm Level  
Test to Clear Value  
3
1314(r)  
1320  
1321  
1322  
1323  
1324  
Any  
Far CSU Loopback Test  
(#1213)  
MIN/WRN  
OFF  
OFF  
OFF  
ON  
test ds1-loop UUCSS  
end-loopback/span-test  
3
Any  
Any  
Any  
Any  
Any  
Loss of Signal Alarm  
Inquiry Test (#138)  
MIN/WRN  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
3
Loss of Signal Alarm  
Inquiry Test (#138)  
MIN/WRN  
Loss of Signal Alarm  
Inquiry Test (#138)  
MINOR  
3
Loss of Signal Alarm  
Inquiry Test (#138)  
MIN/WRN  
OFF  
OFF  
Loss of Signal Alarm  
Inquiry Test (#138)  
WARNING  
3
1537(s)  
1538(t)  
1793  
46082  
Any  
MIN/WRN  
ON  
ON  
3
MIN/WRN  
Any  
Blue Alarm Inquiry Test  
(#139)  
MAJ/MIN/W  
OFF  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS  
test Board UUCSS  
test board UUCSS  
test board UUCSS  
test board UUCSS r 6  
4
RN  
1794  
1795  
2049  
2305  
2306  
2561  
2817  
Any  
Any  
Any  
Any  
Any  
Any  
Blue Alarm Inquiry Test  
(#139)  
MAJ/MIN/W  
RN  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
OFF  
4
Blue Alarm Inquiry Test  
(#139)  
MAJ/MIN  
4
/WNG  
3
Red Alarm Inquiry Test  
(#140)  
MIN/WRN  
3
Yellow Alarm Inquiry  
Test (#141)  
MIN/WRN  
3
Yellow Alarm Inquiry  
Test (#141)  
MIN/WRN  
3
Major Alarm Inquiry Test  
(#142)  
MIN/WRN  
3
Minor Alarm Inquiry Test  
(#143)  
MIN/WRN  
3
3073 to  
3160 (u)  
Any  
Slip Alarm Inquiry Test  
(#144)  
MIN/WRN  
3
3330(v)  
46083  
Any  
MIN/WRN  
ON  
3
3585 to  
3601 (w)  
Misframe Alarm Inquiry  
Test (#145)  
MIN/WRN  
OFF  
test board UUCSS r 6  
3840(x)  
Any  
None  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Continued on next page  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1177  
Table 3-513. DS1 Interface Circuit Pack Maintenance Error Log Entries — Continued  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Alarm Level  
Test to Clear Value  
3841(y)  
3842(z)  
3843(aa)  
3900(ab)  
4358  
46097  
46081  
Any  
CPE Loopback Jack  
Test (#1212)  
3901(ac)  
3902(ad)  
3999(ae)  
Any  
Any  
Any  
Far CSU Loopback Test  
(#1213)  
One-Way Span Test  
(#1214)  
None  
Continued on next page  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate  
test description and follow the recommended procedures.  
2. If ports are assigned to the circuit pack, then a minor alarm is raised. If no ports are assigned to the circuit  
pack, then a warning alarm is raised. The alarm is raised after the circuit pack has been missing for a  
period of 15 minutes. Warning alarms are also raised against any ports administered on the circuit pack.  
3. Minor alarms on this MO may be downgraded to warning alarms based on values set in the set options  
command.  
4. Major alarms on this MO may be downgraded to minor or warning alarms based on values set in the set  
options command.  
Notes:  
a. Error 1 indicates that the circuit pack has totally stopped functioning or is  
not fully administered. The alarm is logged about 15 minutes after the  
circuit pack has been removed or 11-minutes after the SAKI Test (#53)  
fails.  
To be fully administered, a UDS1 circuit pack must meet all of these 3  
conditions:  
1. Have an entry in the circuit plan via the change circuit pack  
command  
2. Be administered via the add ds1 UUCSS command  
3. Be physically inserted into the correct slot  
If the circuit pack has an entry in the circuit plan and either of the other two  
conditions are not met, a MINOR alarm is logged. To resolve the error  
either  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1178  
1. Make sure all conditions for administration are met and that a  
functioning UDS1 circuit pack is inserted in the correct slot, or  
2. Completely remove the UDS1-BD from the system using the  
following steps:  
a. Remove any administered DS1 trunks, access endpoints or  
PRI endpoints associated with the circuit pack from their  
trunk groups.  
b. Execute the remove ds1 UUCSS and change circuit pack  
UUCSS commands.  
If all the administration conditions are met for this circuit pack and the red  
LED is still on, follow the instructions for LED Alarms with Error Type 1 in  
Chapter 7.  
b. The UDS1 Interface circuit pack has been busied out by a busyout board  
UUCSS command.  
c. The UDS1-BD circuit pack is not completely administered. To be fully  
administered, the UDS1 circuit pack must:  
1. Have an entry in the circuit plan via the change circuit pack  
command,  
2. Be administered via the add ds1 UUCSS command, and  
3. Be physically inserted into the correct slot.  
A DS1 (UDS1-BD and DS1-BD) differs from most circuit packs in that  
inserting the circuit pack into the switch is not enough to make the board  
usable. It must also be administered with the add ds1 command.  
d. No Aux Data: A wrong circuit pack is inserted in the slot where this circuit  
pack is logically administered. To resolve this problem, either remove the  
wrong circuit pack and insert the logically administered circuit pack OR  
use the change circuit-pack command to readminister this slot to match  
the circuit pack inserted.  
Aux Data 3: The 24/32-channel option jumper setting on the circuit pack  
does not match the option set on the DS1 circuit pack administration form.  
The circuit pack must be physically removed to see the setting of the  
jumper.  
e. This error is associated with the Common Port Circuit Pack Maintenance  
Test. Refer to XXX-BD (Common Port Circuit Pack) Maintenance  
documentation for details.  
f. The UDS1 Interface circuit pack has detected a transient hardware  
problem. The value in the Aux Data field indicates the type of hardware  
problem.  
4352  
4353  
4355  
External RAM failure  
Internal RAM failure  
Internal ROM failure  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1179  
If the UDS1 board detects only one of these hardware problems, then the  
error will disappear when none of these faults are detected for 10 minutes.  
If the same Aux Data value is logged more than once in a 24 hour period,  
the circuit pack should be replaced.  
g. LAN External RAM Error. This error occurs when there is a hardware fault  
in the PPE external RAM. The RAM is used for message buffering to and  
from the Packet Bus. This error should not occur regularly. If this error is  
seen quite frequently (10 times within 30 minutes), the circuit pack should  
be replaced.  
h. Transmit FIFO Underflow Error. This error occurs when the circuit pack  
cannot find the "end of frame" bit when transmitting a frame to Packet Bus.  
An alarm will be raised if this error occurs three times within 10 minutes.  
Clear the alarm via the following commands: busyout board UUCSS,  
reset board UUCSS, test board UUCSS long, release board UUCSS. If  
the error recurs within 10 minutes, then replace the circuit pack.  
i. Unable to Write LAN Translation RAM Error. This error occurs when a call  
is aborted because there are no available translation RAM locations for  
the call connection attempt. An alarm will be raised if this error occurs two  
times within 10 minutes. Clear the alarm via the following commands:  
busyout board UUCSS, reset board UUCSS, test board UUCSS long,  
release board UUCSS. If the error recurs within 10 minutes, then replace  
the circuit pack.  
j. CSU Module/T1 Sync Splitter missing or E1 Synchronization Splitter  
(E1SS) missing.  
CSU Module/T1 Sync Splitter missing: The Near-End CSU Typefield on  
the add ds1 form has been administered as integratedbut the 120A1  
CSU Module or the 401A T1 Sync Spliltter is not physically connected (or  
is improperly connected) to the TN464F board on the back of the port  
carrier.  
If using the 120A1 CSU Module or the 401A T1 Sync Spliltter, plug (or  
replug) the CSU Module/T1 Sync Splitter into the TN464F circuit pack’s  
connector on the I/O connector panel on back of the carrier. Otherwise,  
change the Near-End CSU Typefield using the change ds1 form to  
other.  
If this error remains after plugging the CSU Module/T1 Sync Splitter into  
the board’s connector, there could be a problem with the I/O connector  
panel.  
E1 Synchronization Splitter missing: The E1 Sync-Splitter? field on  
the add ds1 form has been administered as y,but the 402A or 403A E1  
Synchronization Splitter is not physically connected (or is improperly  
connected) to the TN464F board on the back of the port carrier.  
If using the 402A or 403A E1 Synchronization Splitter, plug (or replug) the  
E1SS into the TN464F circuit pack’s connector on the I/O connector panel  
on back of the carrier. Otherwise, change the E1 Sync-Splitter?field  
using the change ds1 form to n.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1180  
If this error remains after plugging the E1SS into the board’s connector,  
there could be a problem with the I/O connector panel.  
k. CSU Module/T1 Sync Splitter not expected or E1 Synchronization Splitter  
not expected.  
CSU Module/T1 Sync Splitter not expected: The 120A1 CSU Module or the  
401A T1 Sync Spliltter is physically connected to the TN464F board on the  
back of the port carrier but the Near-End CSU Typefield on the add ds1  
form has not been administered as integrated.  
If the 120A1 CSU Module or the 401A T1 Sync Spliltter is to be used, use  
the change ds1 command to change the Near-End CSU Typefield to  
integrated. Otherwise, physically remove the 120A1 CSU Module or  
the 401A T1 Sync Spliltter from the back of the port carrier.  
E1 Synchronization Splitter not expected: The 402A or 403A E1  
Synchronization Splitter is physically connected to the TN464F board on  
the back of the port carrier but the E1 Sync-Splitter?field on the add  
ds1 form has not been administered as y.  
If the 402A or 403A E1 Synchronization Splitter is to be used, use the  
change ds1 command to change the E1 Sync-Splitter?field to y.  
Otherwise, physically remove the 402A or 403A E1 Synchronization  
Splitter from the back of the port carrier.  
l. DS1 configuration error. Attempting to use the 120A1 CSU Module with a  
TN464F circuit pack that is configured for 32-channel (2.048 Mbps)  
operation. The CSU Module only works with a DS1 board configured for  
24-channel (1.544 Mbps) operation in the United States of America.  
m. DS1 circuit pack suffix incorrect for CSU Module/T1 Sync Splitter or for E1  
Synchronization Splitter.  
DS1 circuit pack suffix incorrect for CSU Module/T1 Sync Splitter: The  
Near-End CSU Type field on the add ds1 form has been administered  
as integratedbut the DS1 circuit pack is not a TN464F or later suffix  
UDS1 board.  
If the 120A1 CSU Module or the 401A T1 Sync Spliltter is to be used,  
remove the circuit pack and replace it with a TN464F or later suffix board.  
Otherwise, use the change ds1 command to change the Near-End CSU  
Typefield to other.  
DS1 circuit pack suffix incorrect for E1 Synchronization Splitter: The E1  
Sync-Splitter? field on the add ds1 form has been administered as y  
but the DS1 circuit pack is not a TN464F or later suffix UDS1 board.  
If the 402A or 403A E1 Synchronization Splitter is to be used, remove the  
circuit pack and replace it with a TN464F or later suffix board. Otherwise,  
use the change ds1 command to change the E1 Sync-Splitter?field  
to n.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1181  
n. BLB failure. This error occurs when the DS1 Board Loopback (BLB)  
demand test fails. Repeat the test using the following commands: busyout  
board UUCSS, test ds1-loop UUCSS ds1/csu-loopback-tests, release  
board UUCSS. If the BLB test continues to fail, then the TN464F circuit  
pack needs to be replaced.  
o. ELB failure. This error occurs when the Equipment Loopback (ELB) test  
fails for the Integrated CSU (I-CSU) Module/T1 Sync Splitter or for the  
402A or 403A E1 Synchronization Splitter. This test is executed by the  
I-CSU/E1SS during I-CSU/E1SS power-up/reset (i.e.- TN464F board  
physically inserted and 120A1 CSU Module or the 401A T1 Sync Spliltter,  
or the 402A or 403A E1SS is already installed) or when the 120A1 CSU  
Module or the 401A T1 Sync Spliltter, or the 402A or 403A E1SS is  
plugged on to an already initialized TN464F DS1 board.  
NOTE:  
For the I-CSU/T1 Sync Splitter only, the ELB test is also executed  
as part of the command test ds1-loop UUCSS  
ds1/csu-loopback-tests. Attempt to clear the alarm via the following  
commands: busyout board UUCSS, test ds1-loop UUCSS  
ds1/csu-loopback-tests, release board UUCSS. If the ELB test  
continues to fail, then either the TN464F board, the CSU Module, or  
the I/O cable between the backplane and the CSU module (or any  
combination thereof) has failed. Attempt to isolate where the failure is  
occurring by re-executing the test and by replacing one piece of  
hardware at a time.  
p. RLB failure. This error occurs when the Repeater Loopback (RLB) test fails  
for the Integrated CSU (I-CSU) Module/T1 Sync Splitter or for the 402A or  
403A E1 Synchronization Splitter. This test is executed by the I-CSU/E1SS  
during I-CSU/E1SS power-up/reset (i.e.- TN464F board physically inserted  
and 120A1 CSU Module or the 401A T1 Sync Spliltter, or the 402A or 403A  
E1SS is already installed) or when the 120A1 CSU Module or the 401A T1  
Sync Spliltter, or the 402A or 403A E1SS is plugged on to an already  
initialized DS1 board.  
NOTE:  
For the I-CSU/T1 Sync Splitter only, the RLB test is also executed  
as part of the command test ds1-loop UUCSS  
ds1/csu-loopback-tests. Attempt to clear the alarm via the following  
commands: busyout board UUCSS, test ds1-loop UUCSS  
ds1/csu-loopback-tests, release board UUCSS. If the RLB test  
continues to fail, then the CSU Module needs to be replaced.  
q. CPE Loopback Jack deactivation error. This error occurs when the  
TN464F circuit pack could not deactivate a CPE Loopback Jack on  
power-up/reset or upon software request.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1182  
Attempt to clear the alarm via the following commands: busyout board  
UUCSS, test ds1-loopback UUCSS end-loopback/span-test, release  
board UUCSS. If the attempt to deactivate the CPE Loopback Jack  
continues to fail, other steps must be taken to deactivate the loopback.  
r. Far CSU Loopback deactivation error. This error occurs when the TN464F  
circuit pack could not deactivate a far-end CSU loopback on  
power-up/reset or upon software request.  
Attempt to clear the alarm via the following commands: busyout board  
UUCSS, test ds1-loop UUCSS end-loopback/span-test, release board  
UUCSS. If the attempt to deactivate the Far CSU loopback continues to  
fail, then escalate the problem.  
s. LAN Bus Timeout Error. This error occurs when the circuit pack transmits  
too many bytes on the LAN bus for a single frame. This condition may be  
caused by an on-board fault or by faulty data received on one of the circuit  
pack’s external ports. If any of the ports on this circuit pack are alarmed,  
refer to the repair procedures for those maintenance objects.  
If the error occurs three times within 10 minutes, the board will be isolated  
from the Packet Bus and the board will be alarmed. To clear the alarm and  
restore the board to the Packet Bus, use the following commands:  
busyout board UUCSS, reset board UUCSS, test board UUCSS long,  
release board UUCSS.  
If the problem persists, and there are no PKT-BUS alarms or port alarms,  
then replace the circuit pack.  
t. The hyperactive circuit pack is out-of-service and may exhibit one or more  
of the following symptoms:  
1. The common circuit pack level tests such as Test #50 and/or Test  
#52 are aborting with error code 2000.  
2. The tests run on the ports of this circuit pack are returning with a  
NO-BOARD.  
3. A busyout/release of the circuit pack has no affect on test results.  
4. A list configuration command shows that the circuit pack and  
ports are properly installed.  
The circuit pack is isolated from the system and all trunks or ports on this  
circuit pack are placed into the out-of-service state. The system will try to  
restore the circuit pack within 20-30 minutes. When no faults are detected  
for 20-30 minutes, the UDS1 Interface circuit pack is restored to normal  
operation. All trunks or ports of the UDS1 Interface circuit pack are then  
returned to the in-service state. If the board is not restored to normal  
operation, or the error recurs after the board was restored to normal  
operation, escalate the problem.  
u. For later releases of G3V4 and beyond, only error 3073 will show that this  
board is receiving slips and the AUX data shows the last slip count that  
was reported.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1183  
v. LAN Critical Error. A critical failure has been detected in the Packet Bus  
interface of the circuit pack. This failure may be due to an on-board fault or  
a Packet Bus fault. If the Packet Bus is alarmed, refer to the PKT-BUS  
Maintenance documentation for recommended repair procedures.  
This error will isolate the board from the Packet Bus and raise an alarm. If  
the Packet Bus is not alarmed, enter the following commands: busyout  
board UUCSS, reset board UUCSS, test board UUCSS, release board  
UUCSS. This should clear the alarm and restore the board to the Packet  
Bus.  
If the problem persists, and there are no PKT-BUS alarms, then replace the  
circuit pack.  
w. For later releases of G3V4 and beyond, only error 3585 will show that this  
board is receiving misframes and the AUX data shows the last misframe  
count that was reported.  
x. These errors are not service-affecting. No action is required. These errors  
are reported by the circuit pack when it receives a bad control channel  
message from the switch. The auxiliary data identifies the following error  
events:  
4096  
4097  
4098  
4099  
4100  
4101  
Bad major heading  
Bad port number  
Bad data  
Bad sub-qualifier  
State inconsistency  
Bad logical link  
y. The UDS1 Interface circuit pack has detected a transient hardware logic  
error (for example, program logic inconsistency). This error will disappear  
when no faults are detected for 100 minutes. The value in Aux Data field  
indicates the type of hardware problem.  
z. Bad Translation RAM Location Found Error. This error is not  
service-affecting. No action is required. A Bad Translation RAM is  
detected, but the call continues by using another translation location.  
aa. LAN Receive Parity Error. This error occurs when the circuit pack detects  
an error in a received frame from the Packet Bus. These errors are most  
likely caused by a Packet Bus problem, but may be due to a circuit pack  
fault.  
Refer to the PKT-BUS Maintenance documentation to determine if the  
problem is isolated to this circuit pack or if the problem is caused by  
Packet Bus faults.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1184  
ab. Error 3900 is used to give status information on a CPE Loopback Jack  
Test. The value in the Aux Data field indicates the status of the loopback  
test.  
1. Test is currently running.  
2. Test failed because loopback could not be activated.  
3. Test failed because test pattern could not be detected.  
4. Test has been terminated.  
ac. Error 3901 is used to give status information on a Far CSU Loopback Test.  
The value in the Aux Data field indicates the status of the loopback test.  
1. Test is currently running.  
2. Test failed because loopback could not be activated.  
3. Test failed because test pattern could not be detected.  
4. Test has been terminated.  
ad. Error 3902 is used to give status information on a One-Way Span Test. The  
value in the Aux Data field indicates the status of the span test.  
1. Test is currently running.  
2. Test has failed because test could not be activated.  
3. Test pattern was not received from the far end.  
4. Test has been terminated.  
ae. Error type 3999 indicates that the circuit pack sent a large number of  
control channel messages to the switch within a short period of time. If  
error type 1538 is also present, then the circuit pack was taken  
out-of-service due to hyperactivity. If error type 1538 is not present, then  
the circuit pack has not been taken out-of-service, but it has generated  
50% of the messages necessary to be considered hyperactive. This may  
be completely normal during heavy traffic periods. However, if this error  
type is logged when the circuit pack is being lightly used, it may indicate a  
problem with the circuit pack or the equipment attached to it.  
System Technician-Demanded Tests:  
Descriptions and Error Codes  
Investigate tests in the order they are presented in Table 3-328. By clearing error  
codes associated with the NPE Connection Audit Test, for example, you may also  
clear errors generated from other tests in the testing sequence.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1185  
Table 3-514. System Technician-Demanded Tests  
Short  
Test  
Reset  
Board  
LongTest  
test  
1
Order of Investigation  
NPE Connection Audit Test (#50)  
Control Channel Loop Test (#52)  
Loss of Signal Alarm Inquiry Test (#138)  
Blue Alarm Inquiry Test (#139)  
Red Alarm Inquiry Test (#140)  
Yellow Alarm Inquiry Test (#141)  
Major Alarm Inquiry Test (#142)  
Minor Alarm Inquiry Test (#143)  
Slip Alarm Inquiry Test (#144)  
Misframe Alarm Inquiry Test (#145)  
Translation Update Test (#146)  
ICSU Status LEDs Test (#1227)  
SAKI Sanity Test (#53)  
Sequence Sequence Sequence ds1-loop  
D/ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
ND  
D
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Internal Looparound Test (#135)  
D
DS1/CSU Loopback Tests:  
X
X
X
D
D
D
DS1 Board Loopback Test (#1209)  
CSU Equipment Loopback Test (#1210)  
CSU Repeater Loopback Test (#1211)  
CPE Loopback Jack Test (#1212)  
Far CSU Loopback Test (#1213)  
One-Way Span Test (#1214)  
X
X
X
X
X
D
D
D
D
D
Inject Single Bit Error (#1215)  
End Loopback/Span Test (#1216)  
1. D = Destructive; ND = Nondestructive  
NPE Connection Audit Test (#50)  
The system sends a message to the on-board microprocessor to update the  
network connectivity translation for the SCOTCH-NPE chip on the circuit pack  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1186  
Table 3-515. TEST #50 NPE Connection Audit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test aborted because a test was already running on the port.  
None  
2100  
ABORT  
ABORT  
FAIL  
1019  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
PASS  
The circuit pack’s SCOTCH-NPE chip have been updated with its translation.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Control Channel Looparound Test (#52)  
This test queries the circuit pack for its circuit pack code and vintage and verifies  
its records.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1187  
Table 3-516. TEST #52 Control Channel Looparound Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The circuit pack failed to return the circuit pack code or vintage.  
1. Retry the command a maximum of 5 times.  
None  
2100  
ABORT  
FAIL  
2. If the problem continues, and if the circuit pack is one of the Port circuit  
packs, replace the circuit pack. Otherwise, if the circuit pack is part of the  
SPE, use the procedure described in Replacing SPE Circuit Packs in  
Chapter 5.  
3. Retry the command a few times a maximum of 5 times.  
Communication with this circuit pack is successful.  
PASS  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board  
is shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
SAKI Sanity Test (#53)  
This test is destructive.  
This test resets the circuit pack. The test is highly destructive and can only be  
initiated by a system technician-demanded reset board UUCSS command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1188  
Table 3-517. TEST #53 SAKI Sanity Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
None  
ABORT  
System resources required for this test are not available.  
1. Retry the reset board command at 1-minute intervals a maximum of 5  
times.  
1005  
ABORT  
Wrong circuit pack configuration to run this test. This error applies only to DS1  
Interface circuit packs. It means the DS1 Interface circuit pack is providing  
timing for the system and, therefore, it cannot be reset without major system  
disruptions.  
1. If the circuit pack needs to be reset, then set synchronization to another  
DS1 Interface circuit pack or to the Tone-Clock circuit pack and try again.  
Refer to ‘‘SYNC (Synchronization)’’ Maintenance documentation.  
1015  
2100  
ABORT  
ABORT  
Port is not out-of-service.  
1. Busyout the circuit pack.  
2. Execute the reset board command again.  
System resources required for this test are not available.  
1. Retry the reset board command at 1-minute intervals a maximum of 5  
times.  
1
2
FAIL  
FAIL  
The circuit pack failed to reset.  
The circuit pack failed to restart.  
1. Execute the reset board command again.  
2. If the problem persists, replace the circuit pack.  
The circuit pack initializes correctly.  
1. Run the Short Test Sequence.  
PASS  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1189  
Table 3-517. TEST #53 SAKI Sanity Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Internal Looparound Test (#135)  
This test is destructive.  
The Internal Looparound Test is run by looping the transmitted DS1 bit stream  
back into the UDS1’s board receiver. The loop occurs just before the DS1 facility  
interface. The test is highly destructive and can only be initiated by a system  
technician-demanded reset board UUCSS command.  
All trunks or ports on the UDS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the Internal  
Looparound Test. When the Internal Looparound Test is initiated, maintenance  
software sends appropriate messages to the UDS1 Interface circuit pack to start  
the test. The test uses the Tone Generator and Tone Detector to exercise a bit  
pattern consistency test for all ports. If the transmitted and received bit patterns  
on a trunk or port are different, the test fails.  
When the test is complete, the maintenance software sends a stop loop around  
message to the UDS1 Interface circuit pack to put the circuit pack back into the  
normal operation mode. All trunks or ports of the UDS1 Interface circuit pack are  
restored to the in-service state after the release board command is entered.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1190  
Table 3-518. TEST #135 Internal Looparound Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1002  
ABORT  
The system could not allocate time slots for the test. The system may be under  
heavy traffic conditions or it may have time slots out-of-service due to  
TDM-BUS errors.  
1. If system has no TDM-BUS errors and is not handling heavy traffic, repeat  
test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may be  
oversized for the number of Tone Detectors present or some Tone Detectors  
may be out-of-service.  
1. Resolve any TTR-LEV errors.  
2. Resolve any TONE-PT errors.  
3. If neither condition exists, retry the reset board command at 1-minute  
intervals a maximum of 5 times.  
1004  
1015  
1039  
ABORT  
ABORT  
ABORT  
Received an incoming call on a port of the UDS1 circuit pack during the test.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
UDS1 Interface circuit pack to out-of-service state.  
2. Retry the reset board command at 1-minute intervals a maximum of 5  
times.  
Ports on the UDS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
UDS1 Interface circuit pack into the out-of-service state.  
2. Retry the reset board command.  
The UDS1 Interface circuit pack is providing timing for the system. Therefore, it  
cannot be reset without major system disruption.  
If the UDS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another UDS1 Interface circuit pack or to the Tone-Clock circuit  
pack via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
2000  
2012  
ABORT  
ABORT  
Response to the test request was not received within the allowable time period.  
If Error Type 1538 is present in the Error Log, follow the maintenance strategy  
recommended for this error type.  
Internal system error  
1. Retry the reset board command at 1-minute intervals a maximum of 5  
times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1191  
Table 3-518. TEST #135 Internal Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the reset board command at 1-minute intervals for a maximum of 5  
times.  
FAIL  
The UDS1 Interface circuit pack failed in the Internal Looparound Test.  
If the UDS1 connects to a T1 network facility or another switch:  
1. Retry the reset board command at 1-minute intervals a maximum of 5  
times.  
2. Enter the list measurement ds1-log UUCSS command to read the error  
seconds measurement.  
3. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
4. Check the physical connectivity of DS1 Interface circuit packs and cable.  
5. Replace the local UDS1 Interface circuit pack and repeat the test.  
6. Contact T1 Network Service to diagnose the remote DS1 endpoint.  
FAIL  
(cont’d.)  
If the UDS1 connects to a line-side terminating device such as a PRI terminal  
adapter:  
1. Retry the reset board command at 1-minute intervals a maximum of 5  
times.  
2. Enter the list measurement ds1-log UUCSS command to read the error  
seconds measurement.  
3. Verify that the switch DS1 and the line-side terminating device are  
administered using the same signaling mode, framing mode, and line  
coding.  
4. Investigate the maintenance status of the line-side terminating device.  
Obtain the error seconds measurement on the terminating device (if  
possible). Refer to the line-side terminating device operating manual for  
information.  
5. Check the physical connection of the UDS1 Interface circuit pack to the  
terminating device. Check premise distribution system (or intra-premise  
wiring) for physical connection failures. If the error seconds measurement  
is severe, investigate premise distribution system wiring for noise and  
distance limitation.  
6. Replace the local UDS1 Interface circuit pack and repeat the test.  
7. Contact the vendor of the line-side terminating device to diagnose the  
equipment.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1192  
Table 3-518. TEST #135 Internal Looparound Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
All administered trunks or ports of the UDS1 Interface circuit pack pass the  
Internal Looparound Test. The bit pattern consistency test is executed  
successfully over the path that covers a DS1 port, cable, and the external  
NCTE device.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Loss of Signal Alarm Inquiry Test (#138)  
This test verifies the synchronization status and continuity of the DS1 link. The  
Loss of Signal alarm indicates that the UDS1 Interface circuit pack is unable to  
derive the synchronization clock from the DS1 facility. When the UDS1 Interface  
circuit pack detects a Loss of Signal alarm, it stops providing the synchronization  
clock for the system if it is administered as a timing source and transmits a Yellow  
alarm to the remote DS1 endpoint.  
When the Loss of Signal alarm is confirmed, the maintenance software places all  
trunks or ports of the UDS1 Interface circuit pack into the out-of-service state.  
The inquiry test will run every 10 minutes until the loss of signal has been  
restored.  
The UDS1 Interface circuit pack raises a Loss of Signal alarm after the signal has  
been lost for about 1 second. It will not retire the alarm until the signal has  
returned for about 10 seconds.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1193  
This test is also used to maintain the Lucent 120A1 CSU Module or the 401A T1  
Sync Spliltter, and the 402A or 403A E1 Synchronization Spllitter. The CSU  
Module, when combined with the functionality provided by the TN464F circuit  
pack, provides functionality equivalent to an external stand-alone Lucent ESF T1  
CSU. The combination of the TN464F and 120A1 CSU Module is known as an  
Enhanced Integrated CSU (I-CSU).  
The 401A T1 Synchronization Spllitter, when combined with the functionality  
provided by the TN464F circuit pack, allows an ATM switch to derive its timing  
from a T1 connected to the UDS1 in the DEFINITY.  
The 402A or 403A E1 Synchronization Spllitter, when combined with the  
functionality provided by the TN464F circuit pack, allows an ATM switch to derive  
its timing from an E1 connected to the UDS1 in the DEFINITY.  
If a TN464F circuit pack detects certain I-CSU/Sync Splitter hardware errors, it  
will notify maintenance. When the maintenance subsystem receives notification  
of the I-CSU/Sync Splitter error, it will execute this Loss of Signal Inquiry test. The  
test, in addition to querying for a Loss Of Signal alarm condition, will also query  
the TN464F board to confirm the I-CSU/Sync Splitter error. A Minor or Warning  
alarm will be raised depending on the severity of the I-CSU/Sync Splitter error.  
The trunks on the board may be taken out of service if the I-CSU/Sync Splitter  
error is deemed serious.  
If a Loss Of Signal alarm and an I-CSU/Sync Splitter error co-exist, the Loss Of  
Signal alarm condition will take priority and the board and all trunks on the board  
will be put in the out-of-service state. Errors will be logged, however, for both.  
When the maintenance subsystem receives notification that the I-CSU/Sync  
Splitter hardware error condition no longer exists, maintenance will restore the  
board and all trunks to their previous service state if the alarm can be cleared (no  
other I-CSU/Sync Splitter errors or Loss Of Signal alarm exist).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1194  
Table 3-519. TEST #138 Loss of Signal Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2000  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
When hyperactivity occurs, the circuit pack is isolated from the system, and all  
of the trunks for this circuit pack are placed into the out of service state. The  
system will try to restore the circuit pack within 15 minutes. When no faults are  
detected for 15 minutes, the UDS1 interface circuit pack is restored to normal  
operation. All of the trunks for the UDS1 interface circuit pack are then returned  
to the in service state. Hyperactivity is often caused by the associated facility. In  
such a case, faults (such as slips, misframes, or blue alarms) would be entered  
in the error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again after 15  
minutes, replace the circuit pack.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1195  
Table 3-519. TEST #138 Loss of Signal Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
UDS1 Interface circuit pack detects a Loss of Signal alarm. The physical link is  
broken or the remote DS1 endpoint is down. All trunks or ports of this UDS1  
interface circuit pack are out-of-service. If the UDS1 Interface circuit pack is  
designated as the supplier of the system synchronization source, then the  
system synchronization maintenance will adopt a source elsewhere. Refer to  
the ‘‘SYNC (Synchronization)’’ section in this chapter for details. If the UDS1  
connects to a T1 network facility:  
1. Check the physical connection of the UDS1 Interface circuit pack and the  
cable. If a CSU Module or a Sync Splitter is physically connected to a  
TN464F board on the back of the port carrier, check the physical  
connection of the CSU Module/Sync Splitter and make sure the Network  
Interface cable is plugged into the CSU Module’s/Sync Splitter’s NETWORK  
jack.  
2. If the UDS1 Interface circuit pack connects to a T1 facility, call the vendor of  
the T1 carrier to diagnose the remote DS1 endpoint. If the UDS1 Interface  
circuit pack connects directly to a switch, call the system technician of the  
remote switch to diagnose the DS1 endpoint.  
If the UDS1 connects to a line-side terminating device such as a PRI terminal  
adapter:  
1. Check the physical connection of the UDS1 Interface circuit pack to the  
terminating device. Check premise distribution system (or intra-premise  
wiring) for physical connection failures. If a CSU Module or Sync Splitter is  
physically connected to a TN464F board on the back of the port carrier,  
check the physical connection of the CSU Module/Sync Splitter and make  
sure the Network Interface cable is plugged into the CSU Module’s/Sync  
Splitter’s NETWORK jack.  
2. Contact the vendor of the line-side terminating device to diagnose the  
equipment.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1196  
Table 3-519. TEST #138 Loss of Signal Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1300  
FAIL  
The CSU Module/T1 Sync Splitter or the E1 Sync Splitter is missing.  
The CSU Module/T1 Sync Splitter is missing: The Near-End CSU Type field on  
the add ds1 form has been administered as integrated but the 120A1 CSU  
Moduler or the 401A T1 Sync Spliltter is not physically connected to the TN464F  
board on the back of the port carrier.  
1. If using the 120A1 CSU Module or the 401A T1 Sync Spliltter, plug the CSU  
Module/T1 Sync Splitter into the TN464F circuit pack’s connector on the I/O  
connector panel on back of the carrier. Otherwise, change the Near-End  
CSU Type field using the change ds1 form to other.  
2. Run the test again.  
The E1 Sync Splitter is missing: The E1 Sync-Splitter? field on the add ds1 form  
has been administered as y but the 402A or 403A E1 Sync Splitter is not  
physically connected to the TN464F board on the back of the port carrier.  
1. If using the 402A or 403A E1 Synchronization Splitter, plug the E1SS into  
the TN464F circuit pack’s connector on the I/O connector panel on back of  
the carrier. Otherwise, change the E1 Sync-Splitter? field using the change  
ds1 form to n.  
2. Run the test again.  
1301  
FAIL  
The 120A1 CSU Module or the 401A T1 Sync Spliltter, or the 402A or 403A E1  
Synchronization Splitter is not expected.  
The 120A1 CSU Module or the 401A T1 Sync Spliltter is not expected: The  
120A1 CSU Module/T1 Sync Splitter is physically connected to the TN464F  
board on the back of the port carrier but the Near-End CSU Type field on the  
add ds1 form has not been administered as integrated.  
1. If the 120A1 CSU Module/T1 Sync Splitter is to be used, use the change  
ds1 command to change the Near-End CSU Type field to integrated.  
Otherwise, physically remove the 120A1 CSU Module/T1 Sync Splitter from  
the back of the port carrier.  
2. Run the test again.  
The 402A or 403A E1 Synchronization Splitter is not expected: The 402A or  
403A E1 Synchronization Splitter is physically connected to the TN464F board  
on the back of the port carrier but the E1 Sync-Splitter? field on the add ds1  
form has not been administered as y.  
1. If the 402A or 403A E1 Synchronization Splitter is to be used, use the  
change ds1 command to change the E1 Sync-Splitter? field to y. Otherwise,  
physically remove the 402A or 403A E1 Synchronization Splitter from the  
back of the port carrier.  
2. Run the test again.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1197  
Table 3-519. TEST #138 Loss of Signal Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1302  
FAIL  
Attempting to use the 120A1 CSU Module with a TN464F circuit pack that is  
configured for 32-channel (2.048 Mbps) operation. The CSU Module only works  
with a DS1 board configured for 24-channel (1.544 Mbps) operation in the  
United States of America.  
1. If the 120A1 CSU Module is to be used, physically remove the TN464F  
circuit pack and reconfigure for 24-channel (1.544 Mbps) operation.  
2. Reinsert the circuit pack and run the test again.  
1303  
FAIL  
The DS1 circuit pack Suffix is incorrect for CSU Module/T1 Sync Splitter or E1  
Sync Splitter administration.  
The DS1 circuit pack Suffix is incorrect for CSU Module/T1 Sync Splitter  
administration. The Near-End CSU Type field on the add ds1 form has been  
administered as integratedbut the DS1 circuit pack is not a TN464F or  
later suffix UDS1 board.  
1. If the CSU Module/T1 Sync Splitter is to be used, and the Near-End CSU  
Typ e field is set to integratedto allow for CSU Module/T1 Sync Splitter  
administration, remove the circuit pack and replace it with a TN464F or later  
suffix board. Otherwise use the change ds1 command to change the  
Near-End CSU Type field to other.  
The DS1 circuit pack Suffix is incorrect for E1 Sync Splitter administration. The  
E1 Sync-Splitter? field on the add ds1 form has been administered as y but the  
DS1 circuit pack is not a TN464F or later suffix UDS1 board.  
1. If the E1 Sync Splitter is to be used, and the E1 Sync-Splitter? field is set to  
y to allow for E1SS administration, remove the circuit pack and replace it  
with a TN464F or later suffix board. Otherwise use the change ds1  
command to change the E1 Sync-Splitter? field to n.  
1310  
FAIL  
The DS1 Board Loopback (BLB) demand test (#1209) failed.  
1. Repeat the test using the test ds1-loop UUCSS ds1/csu-loopback-tests  
command.  
2. If the BLB test continues to fail, then replace the TN464F circuit pack.  
3. Run this test again.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1198  
Table 3-519. TEST #138 Loss of Signal Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1311  
FAIL  
The Integrated CSU (I-CSU) Module Equipment Loopback (ELB) test (#1210)  
failed. This test is executed by the I-CSU during I-CSU power-up/reset (i.e., the  
TN464F board is physically inserted and a CSU Module or a Sync Spliltter is  
already installed) or when the CSU Module/Sync Splitter is plugged on to an  
already initialized DS1 board. The ELB test is also executed as part of the  
command test ds1-loop UUCSS ds1/csu-loopback-tests for the CSU Module  
and T1 Sync Splitter.  
1. Execute the test ds1-loop UUCSS ds1/csu-loopback-tests command.  
2. If the ELB test continues to fail, then either the TN464F board, the CSU  
Module/T1 Sync Splitter, or the I/O cable between the backplane and the  
CSU module/T1 Sync Splitter (or any combination thereof) has failed.  
Attempt to isolate the problem to one of these areas. Begin by replacing the  
CSU Module/T1 Sync Splitter and running the test ds1-loop UUCSS  
ds1/csu-loopback-tests command again.  
3. If the ELB test continues to fail, then replace the TN464F board and run the  
test ds1-loop UUCSS ds1/csu-loopback-tests command again.  
4. If the ELB test continues to fail, the problem could be in the I/O cable  
between the backplane and the CSU module/T1 Sync Splitter.  
1312  
FAIL  
The Integrated CSU (I-CSU) Module Repeater Loopback (RLB) test (#1211)  
failed. This test is executed during I-CSU/Sync Splitter power-up/reset (i.e., the  
TN464F board is physically inserted and the CSU Module or the Sync Spliltter is  
already installed) or when the CSU Module/Sync Splitter is plugged on to an  
already initialized DS1 board. The RLB test is also executed as part of the  
command test ds1-loop UUCSS ds1/csu-loopback-tests for the CSU  
Module/T1 Sync Splitter.  
1. Execute the test ds1-loop UUCSS ds1/csu-loopback-tests command.  
2. If the RLB test continues to fail, then replace the CSU Module/T1 Sync  
Splitter.  
3. Run this test again.  
1313  
1314  
FAIL  
FAIL  
The TN464F circuit pack could not deactivate a CPE Loopback Jack loopback.  
1. Execute the test ds1-loop UUCSS end-loopback/span-test command.  
2. If the attempt to deactivate the CPE Loopback Jack is not successful,  
check the cabling and investigate the problem at the CPE Loopback Jack.  
3. Run the test again.  
The TN464F circuit pack could not deactivate a far-end CSU loopback.  
1. Execute the test ds1-loop UUCSS end-loopback/span-test command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1199  
Table 3-519. TEST #138 Loss of Signal Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1320  
FAIL  
A CSU Module/Sync Splitter hardware failure, or an ICSU/Sync Splitter serial  
interface audit failure was detected by the TN464F UDS1 circuit pack.  
1. Replace the CSU module/Sync Splitter, and then run the test again.  
2. If the test continues to fail with this error code, replace the TN464F and run  
the test again.  
3. If the test continues to fail with this error code, then the problem could be in  
the I/O cable between the backplane and the CSU module/Sync Splitter.  
1321  
FAIL  
DTE LOS (loss of signal) was detected between the TN464F UDS1 board and  
the CSU Module or the Sync Spliltter. Either the TN464F board, the CSU  
Module/Sync Spliltter, or the I/O cable between the backplane and the CSU  
module/Sync Splitter (or any combination thereof) has failed. Attempt to isolate  
the problem to one of these areas.  
1. Replace the CSU Module/Sync Splitter and run the test again.  
2. If the test continues to fail with this error code, then replace the TN464F  
board and run the test again.  
3. If the test continues to fail with this error code, the problem could be in the  
I/O cable between the backplane and the CSU module/Sync Splitter.  
1322  
FAIL  
No 5 volts power detected from the TN464F circuit pack to the CSU Module or  
the Sync Splitter. Problem is probably due to an open fuse on the DS1 board or  
a faulty ICSU/Sync Splitter.  
NOTE:  
Do not immediately swap DS1 boards as this may blow the fuse on the  
new board.  
1. If the test continues to fail with this error code, then replace the CSU  
Module/Sync Splitter and run the test again.  
2. Remove the TN464F from the system and reinsert.  
3. Run the test again once the board has finished its reset.  
4. If the test continues to fail with this error code, then replace the TN464F  
board and run the test again.  
5. If the test continues to fail with this error code, the problem could be in the  
I/O cable between the backplane and the CSU module/Sync Splitter.  
1323  
FAIL  
A service-affecting CSU Module/Sync Splitter audit failure was detected by the  
TN464F UDS1 circuit pack. All administered ports on the UDS1 circuit pack are  
affected and maintenance software will place the ports into the out-of-service  
state.  
1. Replace the CSU Module or the Sync Splitter.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1200  
Table 3-519. TEST #138 Loss of Signal Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1324  
FAIL  
A non-service-affecting CSU Module/Sync Splitter audit failure was detected by  
the TN464F UDS1 circuit pack. No ports should be affected. No immediate  
action is required. These errors indicate that the CSU Module/Sync Splitter  
hardware may have a problem, and that it should be replaced when practical to  
avoid further deterioration.  
PASS  
DS1 signal is present and the physical link is healthy. In addition, no Integrated  
CSU/Sync Splitter errors are detected.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be due  
to incorrect translations, no board is inserted, an incorrect board is inserted, or  
an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Blue Alarm Inquiry Test (#139)  
The Blue Alarm is a signal sent by the remote DS1 endpoint when it is  
out-of-service. The Blue Alarm Inquiry Test checks the blue alarm status of the  
remote DS1 endpoint.  
When the UDS1 Interface circuit pack detects a Blue Alarm signal from the  
remote DS1 endpoint, the circuit pack will transmit a Yellow alarm to the remote  
DS1 endpoint and send a BLUE ALARM message to the maintenance software.  
When the Blue alarm is confirmed, the maintenance software places all trunks or  
ports of the UDS1 Interface circuit pack into the out-of-service state. The inquiry  
test will be run every 10 minutes until the Blue alarm is cleared.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1201  
The UDS1 Interface circuit pack takes 1 seconds to recognize and report a Blue  
alarm and 16 seconds to recognize and report the resolution of a Blue alarm.  
When the Blue alarm is cleared, the UDS1 Interface circuit pack stops  
transmitting the Yellow alarm and places the trunks or ports back into the service  
state before the Blue alarm occurs.  
Line Loopback Alarm  
The Line Loopback (LLB) is used by the remote DS1 endpoint to put the ICSU or  
DS1 board into a loopback mode. When the ICSU or DS1 board is in the LLB  
mode, the arriving bit pattern is regenerated and sent back. Line Loopback (LLB)  
Alarm is activated when the in-band activate LLB bit pattern has been arriving  
continuously for 5 seconds on the DS1 line. LLB is deactivated when the in-band  
deactivate LLB bit pattern has been arriving continuously for 5 seconds on the  
DS1 line.  
Since LLB is a maintenance condition rendering all DS0 channels unavailable for  
signaling or bearer traffic, maintenance software treats this the same as a Blue  
Alarm.  
Payload Loopback Alarm  
The Payload Loopback (PLB) is used by the remote DS1 endpoint to put the  
switch DS1 into a loopback mode. PLB Alarm is activated when a network  
protocol activate bit pattern arrives over the 4Kbps ESF data link on the DS1 line.  
PLB is deactivated when a network protocol deactivate bit pattern arrives over  
the 4Kbps ESF data link on the DS1 line.  
Since PLB is a maintenance condition rendering all DS0 channels unavailable for  
signaling or bearer traffic, maintenance software treats this the same as a Blue  
Alarm  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1202  
Table 3-520. TEST #139 Blue Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2000  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
When hyperactivity occurs, the circuit pack is isolated from the system, and all  
of the trunks for this circuit pack are placed into the out of service state. The  
system will try to restore the circuit pack within 15 minutes. When no faults are  
detected for 15 minutes, the UDS1 interface circuit pack is restored to normal  
operation. All of the trunks for the UDS1 interface circuit pack are then returned  
to the in service state. Hyperactivity is often caused by the associated facility. In  
such a case, faults (such as slips, misframes, or blue alarms) would be entered  
in the error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again after 15  
minutes, replace the circuit pack.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
The remote DS1 endpoint is out-of-service.  
FAIL  
FAIL  
1
The UDS1 Interface circuit pack detects a Line Loopback Alarm (LLB).  
1794  
If the UDS1 interface circuit pack connects to a T1 facility, call the vendor of the  
T1 carrier to diagnose the remote DS1 endpoint.  
If the UDS1 interface circuit pack connects directly to a switch, call the system  
technician of the remote switch to diagnose the DS1 endpoint.  
If the UDS1 interface circuit pack connects directly to a line-side terminating  
device (for example, a PRI terminal adapter), call the vendor of the terminating  
device to diagnose the equipment.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1203  
Table 3-520. TEST #139 Blue Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1795  
FAIL  
The UDS1 Interface circuit pack detects a Payload Loopback Alarm (PLB). If  
the UDS1 Interface circuit pack connects to a leased T1 facility, call the vendor  
of the T1 carrier to diagnose the remote DS1 endpoint. If the UDS1 Interface  
circuit pack connects directly to another DS1 board, call the system technician  
of the remote switch to diagnose the DS1 endpoint. If the UDS1 Interface circuit  
pack connects directly to a line-side terminating device such as a PRI terminal  
adapter contact the vendor of the terminating device to diagnose the  
equipment.  
PASS  
Remote DS1 endpoint is in-service. Neither a Blue alarm nor a Line Loopback  
alarm nor a Payload Loopback Alarm is detected by the UDS1 Interface circuit  
pack.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be due  
to incorrect translations, no board is inserted, an incorrect board is inserted, or  
an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Red Alarm Inquiry Test (#140)  
A UDS1 Interface circuit pack raises a Red alarm when the framing pattern of the  
incoming DS1 bit stream has been lost. The Red Alarm Inquiry Test checks the  
framing status of a UDS1 Interface circuit pack. A UDS1 Interface circuit pack  
takes 3 seconds to recognize and report a Red alarm and 10 seconds to  
recognize and report the resolution of a Red alarm.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1204  
When the UDS1 Interface circuit pack detects a Red alarm, the circuit pack will  
transmit a Yellow alarm to the remote DS1 endpoint and send a RED ALARM  
message to the maintenance software. After the Red alarm is confirmed, the  
maintenance software places all trunks or ports of the circuit pack into the  
out-of-service state. The inquiry test will be run every 10 minutes until the Red  
alarm is cleared.  
When the Red alarm is cleared, the UDS1 Interface circuit pack will stop  
transmitting the Yellow alarm to the remote DS1 endpoint. The maintenance  
software restores all trunks or ports of the UDS1 Interface circuit pack to the  
service state before the Red alarm occurs.  
Loss of Multiframe Alarm  
If the UDS1 Interface circuit pack is administered using DMI-BOS signaling, the  
UDS1 Interface circuit pack raises a Loss of Multiframe Alarm (LMA) when it  
cannot interpret the incoming signaling bits to synchronize to the multiframe  
pattern received in the 24th channel. Once the UDS1 Interface circuit pack  
detects an LMA, the circuit pack will transmit a Remote Multiframe Alarm (RMA)  
to the remote DS1 endpoint. Maintenance software handles both Red alarm and  
LMA alarm(s) using the same mechanism.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1205  
Table 3-521. TEST #140 Red Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the UDS1 interface circuit  
pack is restored to normal operation. All of the trunks for the UDS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, replace the circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1206  
Table 3-521. TEST #140 Red Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
The UDS1 interface circuit pack detected a red alarm. An out of frame  
condition occurred on the UDS1 interface circuit pack. The UDS1 interface  
circuit pack will transmit a yellow alarm to the remote UDS1 endpoint until the  
red alarm is retired.  
If the UDS1 connects to a T1 network facility or to another switch, do the  
following.  
1. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
2. Contact T1 Network Service or a technician at the far-end switch to  
diagnose the remote DS1 endpoint.  
3. Check the physical connectivity of the UDS1 packs and of the cable.  
4. Replace the local UDS1 interface circuit pack, and repeat the test.  
If the UDS1 connects to a line-side terminating device (for example, a PRI  
terminal adapter), do the following.  
1. Verify that the switch DS1 and the line-side terminating device are  
administered using the same signaling mode, framing mode, and line  
coding.  
2. Investigate the maintenance status of the line-side terminating device.  
Refer to the ’Line-Side Terminating Device Operating Manual’ for  
information.  
3. Contact the vendor of the line-side terminating device to diagnose the  
equipment.  
4. Check the physical connection of the UDS1 interface circuit pack to the  
terminating device, and check the premise distribution system (or the  
intra-premise wiring) for physical connection failures.  
5. Replace the local UDS1 interface circuit pack and repeat the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1207  
Table 3-521. TEST #140 Red Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
FAIL  
The test failed. The UDS1 interface circuit pack detected a loss of multiframe  
alarm (LMA). An out of frame condition occurred on the UDS1 interface circuit  
pack. The UDS1 interface circuit pack will transmit a remote multiframe alarm  
(RMA) to the remote UDS1 endpoint until the LMA is retired.  
If the UDS1 connects to a T1 network facility or to another switch, do the  
following:  
1. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
2. Contact T1 Network Service or a technician at the far-end switch to  
diagnose the remote DS1 endpoint.  
3. Check the physical connectivity of the UDS1 packs and of the cable.  
4. Replace the local UDS1 interface circuit pack, and repeat the test.  
If the UDS1 connects to a line-side terminating device (for example, a PRI  
terminal adapter), do the following.  
1. Verify that the switch DS1 and the line-side terminating device are  
administered using the same signaling mode, framing mode, and line  
coding.  
2. Investigate the maintenance status of the line-side terminating device.  
Refer to the ’Line-Side Terminating Device Operating Manual’ for  
information.  
3. Contact the vendor of the line-side terminating device to diagnose the  
equipment.  
4. Check the physical connection of the UDS1 interface circuit pack to the  
terminating device, and check the premise distribution system (or the  
intra-premise wiring) for physical connection failures.  
5. Replace the local UDS1 interface circuit pack and repeat the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1208  
Table 3-521. TEST #140 Red Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
No Red alarm is detected on the UDS1 Interface circuit pack.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Continued on next page  
Yellow Alarm Inquiry Test (#141)  
Receiving a Yellow alarm from remote DS1 endpoint indicates that the remote  
DS1 endpoint has an out-of-frame condition. The Yellow Alarm Inquiry Test is  
used to determine whether the remote DS1 endpoint is transmitting a Yellow  
alarm. The UDS1 Interface circuit pack takes 500 msec to recognize and report a  
Yellow alarm and 500 msec to recognize and report that a Yellow alarm condition  
is cleared.  
When the UDS1 Interface circuit pack detects a Yellow alarm from the remote  
DS1 endpoint, it will send a YELLOW-ALARM uplink message to the  
maintenance software. After the maintenance software receives the  
YELLOW-ALARM message, the Yellow Alarm Inquiry Test is run to confirm the  
Yellow alarm. Once the Yellow alarm is confirmed, the maintenance software  
places all trunks or ports on the circuit pack into the out-of-service state. The  
Inquiry Test will be run every 10 minutes until the Yellow alarm is cleared.  
When the Yellow alarm is cleared, the maintenance software restores all trunks or  
ports on the UDS1 Interface circuit pack back to their previous service state  
before the Yellow alarm was raised.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1209  
This Yellow alarm corresponds to the yellow F2 state documented in CCITT  
Recommendation I.431.  
Remote Multiframe Alarm  
Remote Multiframe Alarm (RMA) indicates that the remote DS1 endpoint is in a  
Loss of Multiframe Alarm condition while the UDS1 Interface circuit pack is  
administered using the DMI-BOS common channel signaling. The RMA is  
handled as a Yellow alarm.  
Yellow F5 Fault Alarm  
For 32-channel E1 operation with CRC4 on, the F5 fault state is defined as a fault  
in the user-network interface, specifically in the direction from the user (PBX) to  
the network. Refer to CCITT recommendation I.431.  
Table 3-522. TEST #141 Yellow Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
Response to the test was not received within the allowable time period. This may  
be due to hyperactivity. Error type 1538 in the error log indicates hyperactivity.  
The hyperactive circuit pack is out of service and one or more of the following  
symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the UDS1 interface circuit  
pack is restored to normal operation. All of the trunks for the UDS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, replace the circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1210  
Table 3-522. TEST #141 Yellow Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
The UDS1 interface circuit pack detected a yellow alarm sent by the remote DS1  
endpoint. An out of frame condition occurred at the DS1 endpoint. If the UDS1  
connects to a T1 network facility or to another switch, do the following:  
1. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
2. Contact T1 Network Service or a technician at the far-end switch to  
diagnose the remote DS1 endpoint.  
3. Check the physical connectivity of the UDS1 packs and of the cable.  
4. Replace the local UDS1 interface circuit pack, and repeat the test.  
If the UDS1 connects to a line-side terminating device (for example, a PRI  
terminal adapter), do the following:  
1. Verify that the switch DS1 and the line-side terminating device are  
administered using the same signaling mode, framing mode, and line  
coding.  
2. Investigate the maintenance status of the line-side terminating device. Refer  
to the ’Line-Side Terminating Device Operating Manual’ for information.  
3. Contact the vendor of the line-side terminating device to diagnose the  
equipment.  
4. Check the physical connection of the UDS1 interface circuit pack to the  
terminating device, and check the premise distribution system (or the  
intra-premise wiring) for physical connection failures.  
5. Replace the local UDS1 interface circuit pack and repeat the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1211  
Table 3-522. TEST #141 Yellow Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1
FAIL  
The UDS1 interface circuit pack detected a remote multiframe alarm (RMA) sent  
by the remote DS1 endpoint. An out of frame condition occurred at the DS1  
endpoint.  
If the UDS1 connects to a T1 network facility or to another switch, do the  
following:  
1. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
2. Contact T1 Network Service or a technician at the far-end switch to  
diagnose the remote DS1 endpoint.  
3. Check the physical connectivity of the UDS1 packs and of the cable.  
4. Replace the local UDS1 interface circuit pack, and repeat the test.  
If the UDS1 connects to a line-side terminating device (for example, a PRI  
terminal adapter), do the following:  
1. Verify that the switch DS1 and the line-side terminating device are  
administered using the same signaling mode, framing mode, and line  
coding.  
2. Investigate the maintenance status of the line-side terminating device. Refer  
to the ’Line-Side Terminating Device Operating Manual’ for information.  
3. Contact the vendor of the line-side terminating device to diagnose the  
equipment.  
4. Check the physical connection of the UDS1 interface circuit pack to the  
terminating device, and check the premise distribution system (or the  
intra-premise wiring) for physical connection failures.  
5. Replace the local UDS1 interface circuit pack and repeat the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1212  
Table 3-522. TEST #141 Yellow Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2
FAIL  
The UDS1 interface circuit pack is reporting a Yellow F5 fault alarm. There is a  
fault in the User-Network interface from the user (PBX) to the network. An  
out-of-frame condition occurs on the remote DS1 endpoint.  
If the UDS1 connects to a T1 network facility:  
1. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
2. Contact T1 Network Service to diagnose the remote DS1 endpoint.  
3. Check the physical connectivity of the DS1 Interface circuit packs and  
cable.  
4. Replace the local UDS1 Interface circuit pack and repeat the test.  
If the UDS1 connects to a line-side terminating device such as a PRI terminal  
adapter:  
1. Verify that the switch DS1 and the line-side terminating device are  
administered using the same signaling mode, framing mode, and line  
coding.  
2. Investigate the maintenance status of the line-side terminating device. Refer  
to the ’Line-Side Terminating Device Operating Manual’ for information.  
3. Contact the vendor of the line-side terminating device to diagnose the  
equipment.  
4. Check the physical connection of the UDS1 Interface circuit pack to the  
terminating device. Check premise distribution system (or intra-premise  
wiring) for physical connection failures.  
5. Replace the local UDS1 Interface circuit pack and repeat the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1213  
Table 3-522. TEST #141 Yellow Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
Neither a Yellow alarm nor a Remote Multiframe Alarm nor a F5 state alarm is  
being received from the remote DS1 endpoint.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be due  
to incorrect translations, no board is inserted, an incorrect board is inserted, or  
an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1 UUCSS  
command to administer the UDS1 interface if it is not already administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Continued on next page  
Major Alarm Inquiry Test (#142)  
The Major alarm raised by a UDS1 Interface circuit pack indicates that the  
average bit error rate on the DS1 facility is greater than 1/1000. The Major Alarm  
Inquiry Test is used to determine that the received DS1 bit error rate is greater  
than 1/1000. The UDS1 Interface circuit pack takes 10 seconds to recognize and  
report a Major alarm and 10 seconds to recognize and report that a Major alarm  
condition is cleared.  
When the UDS1 Interface circuit pack detects a Major alarm, it will send a  
MAJOR-ALARM message to the maintenance software. (32-channel interfaces  
send a YELLOW alarm to the far end). After the maintenance software receives a  
MAJOR-ALARM message, the Major Alarm Inquiry Test is initiated to confirm the  
Major alarm on the UDS1 Interface circuit pack. The Inquiry Test will be run every  
10 minutes until the Major alarm is cleared. The maintenance software places all  
trunks or ports on the circuit pack in the out-of-service state if the Major alarm  
persists for more than 20 minutes.  
When the Major alarm is cleared, the maintenance software restores all trunks or  
ports on the circuit pack to their previous service state before a Major alarm  
occurs.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1214  
Table 3-523. TEST #142 Major Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the UDS1 interface circuit  
pack is restored to normal operation. All of the trunks for the UDS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, replace the circuit pack.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1215  
Table 3-523. TEST #142 Major Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
If the UDS1 connects to a T1 network facility or to another switch, do the  
following:  
1. The performance of the DS1 link between the UDS1 interface circuit pack  
and the remote DS1 endpoint is very poor. Enter the list measurement  
ds1-log UUCSS command to read the error seconds measurement.  
2. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
3. Contact T1 Network Service or the technician at the remote switch to  
diagnose the equipment.  
4. Check the physical connectivity of the UDS1 interface circuit packs and the  
cable.  
5. Replace the local UDS1 interface circuit pack, and repeat the test.  
FAIL  
(cont’d.)  
If the UDS1 connects to a line-side terminating device (for example, a PRI  
terminal adapter), do the following:  
1. The performance of the DS1 link between the UDS1 interface circuit pack  
and the line-side terminating device is very poor. Enter the list  
measurement ds1-log UUCSS command to read the error seconds  
measurement.  
2. Verify that the switch DS1 and the line-side terminating device are  
administered using the same signaling mode, framing mode, and line  
coding.  
3. Investigate the maintenance status of the line-side terminating device.  
Refer to the ’Line-Side Terminating Device Operating Manual’ for  
information.  
4. Contact the vendor of the line-side terminating device to diagnose the  
equipment.  
5. Check the physical connection of the UDS1 interface circuit pack to the  
terminating device, and check the premise distribution system (or the  
intra-premise wiring) for physical connection failures.  
6. Replace the local UDS1 interface circuit pack and repeat the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1216  
Table 3-523. TEST #142 Major Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
No Major alarm is detected in the UDS1 Interface circuit pack.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Minor Alarm Inquiry Test (#143)  
The Minor alarm raised by a UDS1 Interface circuit pack indicates that the  
average bit error rate on the DS1 facility is greater than 1/1,000,000, but less than  
1/1000. The Minor Alarm Inquiry Test is used to determine that the received DS1  
bit error rate is greater than 1/1,000,000 and less than 1/1000. When D4 framing  
mode is selected, the UDS1 Interface circuit pack takes 41-minutes to recognize  
and report a Minor alarm and 41-minutes to recognize and report that a Minor  
alarm condition has cleared. If ESF framing mode is selected, the UDS1 Interface  
circuit pack takes 10 minutes to recognize and report a Minor alarm and 10  
minutes to recognize and report that a Minor alarm condition has cleared.  
When the UDS1 Interface circuit pack detects a Minor alarm condition, it will  
send a MINOR-ALARM message to the maintenance software. After the  
maintenance software receives a MINOR-ALARM message, the Minor Alarm  
Inquiry Test is initiated to confirm the Minor alarm. All trunks or ports on the circuit  
pack are kept in the in-service state after the Minor alarm is confirmed. The Minor  
Alarm Inquiry Test is run every 10 minutes until the Minor alarm is cleared.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1217  
Table 3-524. TEST #143 Minor Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
Response to the test was not received within the allowable time period. This may  
be due to hyperactivity. Error type 1538 in the error log indicates hyperactivity.  
The hyperactive circuit pack is out of service and one or more of the following  
symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the UDS1 interface circuit  
pack is restored to normal operation. All of the trunks for the UDS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, replace the circuit pack.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1218  
Table 3-524. TEST #143 Minor Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
Minor alarms are often accompanied by slip and misframe alarms against the  
board. Trunk alarms and hardware error logs may occur on the associated  
trunks.  
If the UDS1 connects to a T1 network facility or to another switch, do the  
following:  
1. The performance of the DS1 link between the UDS1 interface circuit pack  
and the remote DS1 endpoint is poor. Enter the list measurement ds1-log  
UUCSS command to read the error seconds measurement.  
2. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
3. Contact T1 Network Service or the technician at the remote switch to  
diagnose the equipment.  
4. Check the physical connectivity of the UDS1 interface circuit packs and the  
cable.  
5. Replace the local UDS1 interface circuit pack, and repeat the test.  
FAIL  
(cont’d.)  
If the UDS1 connects to a line-side terminating device (for example, a PRI  
terminal adapter), do the following:  
1. The performance of the DS1 link between the UDS1 interface circuit pack  
and the line-side terminating device is very poor. Enter the list  
measurement ds1-log UUCSS command to read the error seconds  
measurement.  
2. Verify that the switch DS1 and the line-side terminating device are  
administered using the same signaling mode, framing mode, and line  
coding.  
3. Investigate the maintenance status of the line-side terminating device.  
Obtain the error seconds measurement on the terminating device (if  
possible). Refer to the ’Line-Side Terminating Device Operating Manual’ for  
information.  
4. Contact the vendor of the line-side terminating device to diagnose the  
equipment.  
5. Check the physical connection of the UDS1 interface circuit pack to the  
terminating device, and check the premise distribution system (or the  
intra-premise wiring) for physical connection failures.  
6. Replace the local UDS1 interface circuit pack and repeat the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1219  
Table 3-524. TEST #143 Minor Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
No Minor alarm is detected in the UDS1 Interface circuit pack.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be due  
to incorrect translations, no board is inserted, an incorrect board is inserted, or  
an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1 UUCSS  
command to administer the UDS1 interface if it is not already administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Slip Alarm Inquiry Test (#144)  
Slips occur when transmitter and receiver are not running at precisely the same  
clock rate. The UDS1 Interface circuit pack can detect both positive and  
negative slips on the DS1 facility. The Slip Alarm Inquiry Test is used to acquire  
the total number of slips that have occurred on a DS1 link.  
When the UDS1 Interface circuit pack detects a slip condition, the circuit pack  
will increase the on-board slip counter by 1. A SLIP-COUNT message is  
spontaneously sent to the system software after the counter reaches a threshold  
(for example, 88). When the maintenance software receives the SLIP-COUNT  
message, the Slip Alarm Inquiry Test is initiated to query the slip counters on a  
UDS1 Interface circuit pack and total the slip counts in the maintenance  
software.  
If the count of slips is over the threshold, a Minor alarm is raised against the  
UDS1 Interface circuit pack. All trunks or ports of the UDS1 Interface circuit pack  
remain in the in-service state. If the UDS1 Interface circuit pack is used to supply  
the system synchronization source, the MINOR alarm will initiate a  
synchronization source switch. See “TDM-BUS” and ‘‘SYNC (Synchronization)’’  
for details.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1220  
Table 3-525. TEST #144 Slip Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the UDS1 interface circuit  
pack is restored to normal operation. All of the trunks for the UDS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, replace the circuit pack.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1221  
Table 3-525. TEST #144 Slip Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1 to  
88  
FAIL  
The test failed because the UDS1 interface circuit pack and the remote DS1  
endpoint are not synchronized to the same clock rate. The UDS1 interface  
circuit pack detected a slip alarm. The error code equals the number of slips  
detected by the UDS1 interface circuit pack since the last slip alarm inquiry  
test.  
If the UDS1 connects to a T1 network facility or to another switch, do the  
following:  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2. If the DS1 interface circuit pack is a TN464C, enter the list measurement  
ds1-log UUCSS command to read the error seconds measurement.  
3. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
4. Check the active alarm and error logs for recent alarms and errors against  
the synchronization (SYNC). Follow the suggested repair procedure for  
these errors.  
5. Contact T1 Network Service or the technician at the remote switch to  
diagnose the remote DS1 endpoint.  
6. Check the physical connectivity of the UDS1 interface circuit packs and the  
cable.  
7. Replace the local UDS1 interface circuit pack, and repeat the test.  
Information continues on the next page.  
1 to  
88  
FAIL  
(cont’d.)  
If the UDS1 connects to a line-side terminating device (for example, a PRI  
terminal adapter), do the following:  
(cont’  
d.)  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2. Enter the list measurement ds1-log UUCSS command to read the error  
seconds measurement.  
3. Verify that the switch DS1 and the line-side terminating device are  
administered using the same signaling mode, framing mode, and line  
coding.  
4. Investigate the maintenance status of the line-side terminating device.  
Refer to the ’Line-Side Terminating Device Operating Manual’ for  
information.  
5. Contact the vendor of the line-side terminating device to diagnose the  
equipment.  
6. Check the physical connection of the UDS1 interface circuit pack to the  
terminating device, and check the premise distribution system (or the  
intra-premise wiring) for physical connection failures.  
7) Replace the local UDS1 interface circuit pack and repeat the test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1222  
Table 3-525. TEST #144 Slip Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
No Slip alarm is detected on the UDS1 Interface circuit pack.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be due  
to incorrect translations, no board is inserted, an incorrect board is inserted, or  
an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1 UUCSS  
command to administer the UDS1 interface if it is not already administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Misframe Alarm Inquiry Test (#145)  
Misframe Alarm indicates that framing bits observed on a UDS1 Interface circuit  
pack are in error. The Misframe Alarm Inquiry Test queries the total number of  
misframes that have occurred on a DS1 Interface circuit pack since the last  
inquiry.  
When the DS1 Interface circuit pack detects a misframe error, it will increase its  
misframe counter by 1. If the counter reaches a specified threshold (i.e.- 17), a  
MISFRAME-COUNT message is automatically sent to the switch maintenance  
software. After the maintenance software receives the MISFRAME-COUNT  
message, the Misframe Alarm Inquiry Test is initiated to collect the misframe  
counts from the UDS1 Interface circuit pack.  
When the threshold of misframes is reached, if the UDS1 Interface circuit pack is  
supplying the system synchronization source, then a switching synchronization  
source message is sent to the TDM Bus Clock. See TDM-BUS (TDM Bus)  
Maintenance documentation for details. A Minor alarm against the UDS1  
Interface circuit pack is raised, but all trunks or ports of the UDS1 Interface  
circuit pack remain in the in-service state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1223  
Table 3-526. TEST #145 Misframe Alarm Inquiry Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2000  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the UDS1 interface circuit  
pack is restored to normal operation. All of the trunks for the UDS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, replace the circuit pack.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1224  
Table 3-526. TEST #145 Misframe Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1to17 FAIL  
The test failed because the UDS1 interface circuit pack detected errors in the  
received framing bits pattern. The error code equals the number of misframes  
detected by the UDS1 interface circuit pack since the last misframe alarm  
inquiry test. Major bit and minor bit error rate (error types 2561 and 2817) error  
logs often accompany misframe alarms. Clearing the cause of these error logs  
may clear the misframes which are occurring.  
If the UDS1 connects to a T1 network facility or to another switch, do the  
following:  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2. If the DS1 interface circuit pack is a TN464C, enter the list measurement  
ds1-log UUCSS command to read the error seconds measurement.  
3. Verify that both endpoints of the DS1 link are administered using the same  
signaling mode, framing mode, and line coding.  
4. Check the active alarm and error logs for recent alarms and errors against  
the synchronization (SYNC). Follow the suggested repair procedure for  
these errors.  
5. Contact T1 Network Service or the technician at the remote switch to  
diagnose the remote DS1 endpoint.  
6. Check the physical connectivity of the UDS1 interface circuit packs and the  
cable.  
7. Replace the local UDS1 interface circuit pack, and repeat the test.  
More information continues on the next page.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1225  
Table 3-526. TEST #145 Misframe Alarm Inquiry Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1 to 17 FAIL  
If the UDS1 connects to a line-side terminating device such as a PRI terminal  
adapter:  
(cont’  
d.)  
(cont’d.)  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2. Enter the list measurement ds1-log UUCSS command to read the error  
seconds measurement.  
3. Verify that the switch DS1 and the line-side terminating device are  
administered using the same signaling mode, framing mode, and line  
coding.  
4. Investigate the maintenance status of the line-side terminating device.  
Refer to the ’Line-Side Terminating Device Operating Manual’ for  
information.  
5. Contact the vendor of the line-side terminating device to diagnose the  
equipment.  
6. Check the physical connection of the UDS1 interface circuit pack to the  
terminating device, and check the premise distribution system (or the  
intra-premise wiring) for physical connection failures.  
7. Replace the local UDS1 interface circuit pack and repeat the test.  
No Misframe alarm is detected on the UDS1 Interface circuit pack.  
PASS  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1226  
Translation Update Test (#146)  
The Translation Update Test sends the circuit-pack-level information specified by  
System Administration to the UDS1 Interface circuit pack. Translation includes  
the following data administered for a UDS1 Interface circuit pack (see output of  
display ds1 UUCSS command): DS1 Link Length between two DS1 endpoints,  
Synchronization Source Control, All Zero Suppression, Framing Mode, Signaling  
Mode, Time Slot Number of 697-Hz Tone, Time Slot Number of 700-Hz Tone, etc.  
In G3V3, if a TN464F or later UDS1 circuit pack is combined with a Lucent 120A1  
CSU Module or the 401A T1 Sync Splitter to form an Integrated CSU Module/T1  
Sync Splitter, this test will also send the administration for this Integrated CSU to  
the circuit pack to assure the board’s translations are correct. The administration  
of the CSU Module/T1 Sync Splitter is done using the DS1 circuit pack  
administration form. Translation for the CSU Module/T1 Sync Splitter includes the  
following data: Transmit LBO, Receive ALBO, Supply CPE Loopback Jack  
Power?, etc.  
Table 3-527. TEST #146 Translation Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
FAIL  
Internal system error  
1. Retry the command at 1-minute interval s a maximum of 5 times.  
Internal system software error.  
1. Enter the display ds1 UUCSS command to verify the UDS1 Interface  
circuit pack translation.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1227  
Table 3-527. TEST #146 Translation Update Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
Translation data has been downloaded to the UDS1 Interface circuit pack  
successfully.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
DS1 Board Loopback Test (#1209)  
This test is destructive.  
The DS1 Board Loopback (BLB) Test causes a loopback at the TN464F DS1  
board edge and tests DS1 board internal circuitry.  
The test is destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS ds1/csu-loopback-tests command.  
All trunks or ports on the UDS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the BLB Test.  
When the BLB Test is initiated, maintenance software sends an appropriate  
message to the TN464F UDS1 Interface circuit pack to start the test. The board  
will set up the BLB loopback, transmit a test pattern, and verify that the pattern is  
received unaltered through the loopback. If the transmitted and received pattern  
is different, the test fails.  
When the test is complete, all trunks or ports on the TN464F UDS1 Interface  
circuit pack are restored to the in-service state after the release board command  
is entered.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1228  
Table 3-528. TEST #1209 DS1 Board Loopback Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the test ds1-loop UUCSS ds1/csu-loopback-tests command at  
1-minute intervals a maximum of 5 times.  
1005  
1015  
ABORT  
DS1 Board Loopback Test cannot be executed in the current configuration. To  
run this, the TN464F or later suffix UDS1 must be administered for 24-channel  
operation. The "Bit Rate" field on the DS1 circuit pack administration form must  
be set to "1.544" for 24-channel operation.  
ABORT  
ABORT  
Ports on the UDS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
UDS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
1039  
The UDS1 Interface circuit pack is providing timing for the system. Executing  
this test could cause major system disruption.  
If the UDS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit pack  
via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the board  
is in a network requested loopback mode (Line loopback or Payload loopback).  
The hardware error log will indicate whether a Customer Loopback Jack Test,  
Far CSU Loopback Test, or the One-Way Span Test is executing or if the board  
is in line loopback or payload loopback mode. Only one long-duration  
loopback/span test can be active at a given time. Thus, if a loopback/span test  
is already active, that test must be terminated via the test ds1-loop UUCSS  
end-loopback/span-test command in order to execute this test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1229  
Table 3-528. TEST #1209 DS1 Board Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the UDS1 interface circuit  
pack is restored to normal operation. All of the trunks for the UDS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, replace the circuit pack.  
2100  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
UDS1 Interface circuit pack failed the DS1 Board Loopback Test.  
1. Retry the test ds1-loop UUCSS ds1/csu-loopback-tests command.  
2. If the BLB test continues to fail, then replace the UDS1 circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1230  
Table 3-528. TEST #1209 DS1 Board Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The BLB test executed successfully. The test pattern was transmitted and  
received successfully up to the TN464F DS1 board edge.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be due  
to incorrect translations, no board is inserted, an incorrect board is inserted, or  
an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1 UUCSS  
command to administer the UDS1 interface if it is not already administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Continued on next page  
CSU Equipment Loopback Test (#1210)  
This test is destructive.  
The CSU Equipment Loopback (ELB) Test causes a loopback at the near-edge of  
the local Lucent 120A1 CSU Module or the 401A T1 Sync Splitter and tests the  
connection from the TN464F DS1 board to the CSU Module/T1 Sync Splitter (DS1  
board edge interconnecting cable, and CSU Module/T1 Sync Splitter edge). This  
test will only be performed if the Lucent 120A1 CSU Module or the 401A T1 Sync  
Splitter is present, administered, and connected to a 1.544 Mbps TN464F DS1  
circuit pack on the back of the port carrier.  
The test is destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS ds1/csu-loopback-tests command.  
All trunks or ports on the UDS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the ELB Test.  
When the ELB Test is initiated, maintenance software sends an appropriate  
message to the TN464F UDS1 Interface circuit pack to start the test. The board  
will set up the ELB loopback, transmit a test pattern, and verify that the pattern is  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1231  
received unaltered through the loopback. If the transmitted and received pattern  
is different, the test fails.  
When the test is complete, all trunks or ports on the TN464F UDS1 Interface  
circuit pack are restored to the in-service state after the release board command  
is entered.  
Table 3-529. TEST #1210 CSU Equipment Loopback Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the test ds1-loop UUCSS ds1/csu-loopback-tests command at  
1-minute intervals a maximum of 5 times.  
1005  
ABORT  
CSU Equipment Loopback Test cannot be executed in the current  
configuration. To run this test, the Near-End CSU Type field on the DS1circuit  
pack administration form must be set to integrated and the "Bit Rate" field on  
the DS1 circuit pack administration form must be set to "1.544" (24-channel  
configuration).  
1. Use the change ds1 UUCSS command to set the Near-End CSU Type field  
on the DS1 circuit pack administration form to integrated, and/or change  
the "Bit Rate" field to "1.544" if the board is to be used in 24-channel  
configuration.  
2. Retry the test ds1-loop UUCSS ds1/csu-loopback-tests command.  
1015  
1039  
ABORT  
ABORT  
Ports on the UDS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
UDS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
The UDS1 Interface circuit pack is providing timing for the system. Executing  
this test could cause major system disruption.  
If the UDS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit  
pack via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1232  
Table 3-529. TEST #1210 CSU Equipment Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the board  
is in a network requested loopback mode (Line loopback or Payload loopback).  
The hardware error log will indicate whether a Customer Loopback Jack Test,  
Far CSU Loopback Test, or the One-Way Span Test is executing or if the board  
is in line loopback or payload loopback mode. Only one long-duration  
loopback/span test can be active at a given time. Thus, if a loopback/span test  
is already active, that test must be terminated via the test ds1-loop UUCSS  
end-loopback/span-test command in order to execute this test.  
1951  
2000  
ABORT  
ABORT  
The CSU Equipment Loopback Test could not be executed because the 120A1  
CSU Module or the 401A T1 Sync Splitter was not physically installed.  
Physically connect the 120A1 CSU Module or the 401A T1 Sync Splitter to the  
TN464F board on the back of the port carrier.  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the UDS1 interface circuit  
pack is restored to normal operation. All of the trunks for the UDS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, replace the circuit pack.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1233  
Table 3-529. TEST #1210 CSU Equipment Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
FAIL  
UDS1 Interface circuit pack failed the CSU Equipment Loopback Test.  
1. Retry the test ds1-loop UUCSS ds1/csu-loopback-tests command.  
2. If the ELB test continues to fail, then either the TN464F board, the CSU  
Module/T1 Sync Splitter, or the I/O cable between the backplane and the  
CSU module/T1 Sync Splitter (or any combination thereof) has failed.  
Attempt to isolate the problem to one of these areas. Begin by replacing  
the CSU Module/T1 Sync Splitter and running the test ds1-loop UUCSS  
ds1/csu-loopback-tests command again.  
3. If the ELB test continues to fail, then replace the TN464F board and run the  
test ds1-loop UUCSS ds1/csu-loopback-tests command again.  
4. If the ELB test continues to fail, the problem could be in the I/O cable  
between the backplane and the CSU module/T1 Sync Splitter.  
PASS  
The ELB test executed successfully. The test pattern was transmitted and  
received successfully over the connection from the TN464F DS1 board to the  
near-edge of the 120A1 CSU Module or the 401A T1 Sync Splitter.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1234  
CSU Repeater Loopback Test (#1211)  
This test is destructive.  
The CSU Repeater Loopback (RLB) Test causes a loopback at the far-edge of  
the local Lucent 120A1 CSU Module or the 401A T1 Sync Splitter and tests the  
connection from the TN464F DS1 board to and including the CSU Module/T1  
Sync Splitter circuitry. This test will only be performed if the Lucent 120A1 CSU  
Module or the 401A T1 Sync Splitter is present, administered, and connected to a  
1.544 Mbps TN464F DS1 circuit pack on the back of the port carrier.  
The test is destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS ds1/csu-loopback-tests command.  
All trunks or ports on the UDS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the RLB Test.  
When the RLB Test is initiated, maintenance software sends an appropriate  
message to the TN464F UDS1 Interface circuit pack to start the test. The board  
will set up the RLB loopback, transmit a test pattern, and verify that the pattern is  
received unaltered through the loopback. If the transmitted and received pattern  
is different, the test fails.  
When the test is complete, all trunks or ports on the TN464F UDS1 Interface  
circuit pack are restored to the in-service state after the release board command  
is entered.  
Table 3-530. TEST #1211 CSU Repeater Loopback Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the test ds1-loop UUCSS ds1/csu-loopback-tests command at  
1-minute intervals a maximum of 5 times.  
1005  
ABORT  
CSU Repeater Loopback Test cannot be executed in the current configuration.  
To run this test, the Near-End CSU Type field on the DS1circuit pack  
administration form must be set to integrated and the "Bit Rate" field on the  
DS1 circuit pack administration form must be set to "1.544" (24-channel  
configuration).  
1. Use the change ds1 UUCSS command to set the Near-End CSU Type  
field on the DS1 circuit pack administration form to integrated, and/or  
change the "Bit Rate" field to "1.544" if the board is to be used in  
24-channel configuration.  
2. Retry the test ds1-loop UUCSS ds1/csu-loopback-tests command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1235  
Table 3-530. TEST #1211 CSU Repeater Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1015  
ABORT  
Ports on the UDS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of  
the UDS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
1039  
ABORT  
The UDS1 Interface circuit pack is providing timing for the system. Executing  
this test could cause major system disruption.  
If the UDS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit  
pack via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the  
board is in a network requested loopback mode (Line loopback or Payload  
loopback). The hardware error log will indicate whether a Customer Loopback  
Jack Test, Far CSU Loopback Test, or the One-Way Span Test is executing or if  
the board is in line loopback or payload loopback mode. Only one  
long-duration loopback/span tests can be active at a given time. Thus, if a  
loopback/span test is already active, that test must be terminated via the test  
ds1-loop UUCSS end-loopback/span-test command in order to execute this  
test.  
1951  
ABORT  
The CSU Repeater Loopback Test could not be executed because the 120A1  
CSU Module or the 401A T1 Sync Splitter was not physically installed.  
Physically connect the 120A1 CSU Module or the 401A T1 Sync Splitter to the  
TN464F board on the back of the port carrier.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1236  
Table 3-530. TEST #1211 CSU Repeater Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of  
service state. The system will try to restore the circuit pack within 15  
minutes. When no faults are detected for 15 minutes, the UDS1  
interface circuit pack is restored to normal operation. All of the trunks for  
the UDS1 interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against  
the associated trunk circuits. If the facility is OK and the error occurs  
again after 15 minutes, replace the circuit pack.  
2100  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
UDS1 Interface circuit pack failed the CSU Repeater Loopback Test.  
1. Retry the test ds1-loop UUCSS ds1/csu-loopback-tests command.  
2. If the RLB test continues to fail, and the CSU Equipment Loopback Test  
(#1210) passed, then replace the CSU Module/T1 Sync Splitter.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1237  
Table 3-530. TEST #1211 CSU Repeater Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
The RLB test executed successfully. The test pattern was transmitted and  
PASS  
received successfully over the connection from the TN464F DS1 board to the  
far-edge of the 120A1 CSU Module or the 401A T1 Sync Splitter.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board  
is shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
CPE Loopback Jack Test (#1212)  
This test is destructive.  
The CPE Loopback Jack (CLJ-LB) Test causes a loopback at the CPE Loopback  
Jack and tests the building wiring connection between the TN464F DS1 board  
and the CPE Loopback Jack.  
The test is highly destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS cpe-loopback-jack-test-begin  
[number-of-bits bit-pattern] command. The System technician has the choice  
of entering a loopback activation code on the command line or using the default  
code 0x47F.  
All trunks or ports on the UDS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the CPE Loopback  
Jack Test.  
The CPE Loopback Jack Test has the TN464F UDS1 Interface circuit pack  
transmit a looDpobwanclokadafcrotmivaWtwiown.Scomodaneuatlos.ctohme. CAllPMEanLuoaolspSbeaarcchkAJnadcDko,wwnloaaitds. up to 10  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1238  
seconds for return of the code to verify the loopback has been established,  
transmits a framed 3-in-24 test pattern, begins counting bit errors in the received  
test pattern, and returns a PASS result to indicate that the pattern was  
successfully sent. If the loopback is not established within the 10 seconds, the  
test returns FAIL or abort.  
The status of the CPE Loopback Jack test will be available in the hardware error  
log via error type 3900. Several distinct aux values will be used to give the user  
information of the status of the test.  
The list measurements ds1 summary command will display the length of time the  
test has been running (Test Duration field) and number of bit errors detected  
(Loopback/Span Test Bit-Error Count field). If the test pattern is being passed  
through the loopback cleanly, the number of bit errors should be very low. The  
command will also display the type of Loopback/Span test executing (Te st field),  
the type of pattern generated for the Loopback/Span test (Pattern field), and  
whether the pattern (i.e. 3-in-24 Pattern) is synchronized (Synchronized field).  
To terminate the test, enter the test ds1-loop UUCSS end-loopback/span-test  
command or the release board command. Using the release board command  
will restore all trunks or ports on the TN464F UDS1 Interface circuit pack to the  
in-service state.  
Table 3-531. TEST #1212 CPE Loopback Jack Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the test ds1-loop UUCSS cpe-loopback-jack-test-begin command at  
1-minute intervals a maximum of 5 times.  
1005  
1015  
ABORT  
CPE Loopback Jack Test cannot be executed in the current configuration. To  
run this test, the TN464F or later suffix UDS1 must be administered for  
24-channel operation. The "Bit Rate" field on the DS1 circuit pack  
administration form must be set to "1.544" for 24-channel operation.  
ABORT  
Ports on the UDS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
UDS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1239  
Table 3-531. TEST #1212 CPE Loopback Jack Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1039  
ABORT  
The UDS1 Interface circuit pack is providing timing for the system. Executing  
this test could cause major system disruption.  
If the UDS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit  
pack via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the  
board is in a network requested loopback mode (Line loopback or Payload  
loopback). The hardware error log will indicate whether a Customer Loopback  
Jack Test, Far CSU Loopback Test, or the One-Way Span Test is executing or if  
the board is in line loopback or payload loopback mode. Only one  
long-duration loopback/span test can be active at a given time. Thus, if a  
loopback/span test is already active, that test must be terminated via the test  
ds1-loop UUCSS end-loopback/span-test command in order to execute this  
test.  
2000  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the UDS1 interface circuit  
pack is restored to normal operation. All of the trunks for the UDS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, replace the circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1240  
Table 3-531. TEST #1212 CPE Loopback Jack Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2100  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2
The CLJ-LB test failed because it was not set up properly. The UDS1 interface  
pack could not successfully put the CPE loopback jack into loopback mode.  
1. Rerun the test ds1-loop UUCSS cpe-loopback-jack-test-begin  
command.  
2. If the test continues to fail, the problem could be with the TN464F board,  
the CPE loopback jack equipment, or somewhere between. Run the test  
ds1-loop UUCSS ds1/csu-loopback-tests command to determine if the  
loopback tests that are closer to the TN464F board are successful. If any  
of these tests fail, follow the maintenance strategy that is associated with  
the test that fails.  
3
FAIL  
The CPE Loopback Jack Test was not set up properly. The framed 3-in-24 test  
pattern, generated by the UDS1 Interface circuit pack and looped back  
through the CPE Loopback Jack, could not be detected properly by the UDS1  
circuit pack.  
1. Retry the test ds1-loop UUCSS cpe-loopback-jack-test-begin command.  
2. If the CPE Loopback Jack test continues to fail, the problem could be with  
the TN464F board, the CPE Loopback Jack equipment, or somewhere in  
between. Run the test ds1-loop UUCSS ds1/csu-loopback-tests command  
to see if the loopback tests closer to the TN464F board are successful. If  
any of those loopback tests fail, follow the maintenance strategy  
associated with those loopbacks.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1241  
Table 3-531. TEST #1212 CPE Loopback Jack Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The CPE Loopback Jack test has successfully began executing. The test will  
continue to run until the system technician enters the test ds1-loop UUCSS  
end-loopback/span-test command or the release board UUCSS command.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Far CSU Loopback Test (#1213)  
This test is destructive.  
The Far CSU Loopback (R-LLB) Test causes a loopback at the far-end CSU and  
tests all circuitry and facilities from the local TN464F DS1 board to the far-end  
CSU.  
The test is destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS far-csu-loopback-test-begin command.  
All trunks or ports on the UDS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the Far CSU  
Loopback Test.  
If the far-end CSU is not a Lucent 120A1 CSU Module or the 401A T1 Sync  
Splitter, and the DS1 is administered for ami-zcs line coding, one’s density  
protection must be disabled on the CSU/T1SS during the test due to the large  
number of zero’s in the 3-in-24 test pattern.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1242  
The Far CSU Loopback Test has the TN464F UDS1 Interface circuit pack transmit  
a loopback activation code to the remote CSU, waits up to 15 seconds for return  
of the code to verify the loopback has been established, transmits a framed  
3-in-24 test pattern, begins counting bit errors in the received test pattern, and  
returns a PASS result. If the loopback is not established within the 15 seconds,  
the test fails.  
The status of the Far CSU Loopback test will be available in the hardware error  
log via error type 3901. Several distinct aux values will be used to give the user  
information of the status of the test.  
The list measurements ds1 summary command will display the length of time the  
test has been running (Test Duration field) and number of bit errors detected  
(Loopback/Span Test Bit-Error Count field). If the test pattern is being passed  
through the loopback cleanly, the number of bit errors should be very low. The  
command will also display the type of Loopback/Span test executing (Te st field),  
the type of pattern generated for the type of Loopback/Span test (Pattern field),  
and whether the pattern (i.e. 3-in-24 Pattern) is synchronized (Synchronized  
field).  
To terminate the test, enter the test ds1-loop UUCSS end-loopback/span-test  
command or the release board command. Using the release board command  
will restore all trunks or ports on the TN464F UDS1 Interface circuit pack to the  
in-service state.  
Table 3-532. TEST #1213 Far CSU Loopback Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the test ds1-loop UUCSS far-csu-loopback-test-begin command at  
1-minute intervals a maximum of 5 times.  
1005  
1015  
ABORT  
Far CSU Loopback Test cannot be executed in the current configuration. To  
run this, the TN464F or later suffix UDS1 must be administered for 24-channel  
operation. The "Bit Rate" field on the DS1 circuit pack administration form must  
be set to "1.544" for 24-channel operation.  
ABORT  
Ports on the UDS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of  
the UDS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1243  
Table 3-532. TEST #1213 Far CSU Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1039  
ABORT  
The UDS1 Interface circuit pack is providing timing for the system. Executing  
this test could cause major system disruption.  
If the UDS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit  
pack via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the  
board is in a network requested loopback mode (Line loopback or Payload  
loopback). The hardware error log will indicate whether a Customer Loopback  
Jack Test, Far CSU Loopback Test, or the One-Way Span Test is executing or if  
the board is in line loopback or payload loopback mode. Only one  
long-duration loopback/span test can be active at a given time. Thus, if a  
loopback/span test is already active, that test must be terminated via the test  
ds1-loop UUCSS end-loopback/span-test command in order to execute this  
test.  
2000  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of  
service state. The system will try to restore the circuit pack within 15  
minutes. When no faults are detected for 15 minutes, the UDS1 interface  
circuit pack is restored to normal operation. All of the trunks for the  
UDS1 interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against  
the associated trunk circuits. If the facility is OK and the error occurs  
again after 15 minutes, replace the circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1244  
Table 3-532. TEST #1213 Far CSU Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2100  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
2
The test failed because it was not set up properly. The UDS1 pack could not  
successfully put the far-end CSU into loopback mode.  
1. Rerun the test ds1-loop UUCSS far-csu-loopback-test-begin command.  
2. If the test continues to fail, the problem could be with the TN464F board,  
the CPE loopback jack equipment, or somewhere between. Run the test  
ds1-loop UUCSS cpe-loopback-jack-test-begin command to determine  
if the CPE loopback jack loopback test is successful. If a CPE loopback  
jack device is not being used, issue the test ds1-loop UUCSS  
ds1/csu-loopback-tests command instead. If the closer loopback test  
fails, follow the maintenance strategy associated with that test.  
3
FAIL  
The Far CSU Loopback Test was not set up properly. The framed 3-in-24 test  
pattern, generated by the UDS1 Interface circuit pack and looped back  
through the far-end CSU, could not be detected properly by the UDS1 circuit  
pack.  
1. Retry the test ds1-loop UUCSS far-csu-loopback-test-begin command.  
2. If the Far CSU Loopback test continues to fail with this error code, the  
problem could be with the TN464F board, the far-end CSU equipment, or  
somewhere in between. Run the test ds1-loop UUCSS  
cpe-loopback-jack-test-begin command to see if the CPE Loopback Jack  
test which is closer to the TN464F board is successful. (If a CPE Loopback  
Jack device is not being used, then run the test ds1-loop UUCSS  
ds1/csu-loopback-tests command to see if these even closer loopback  
tests succeed). If the closer loopback test fails, follow the maintenance  
strategy associated with that loopback.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1245  
Table 3-532. TEST #1213 Far CSU Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The Far CSU Loopback test has successfully began executing. The test will  
continue to run until the system technician enters the test ds1-loop UUCSS  
end-loopback/span-test command or the release board UUCSS command.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1246  
One-Way Span Test (#1214)  
This test is destructive.  
The One-Way Span Test allows one-way span testing to and from remote test  
equipment or another DEFINITY communications system. This will test all  
circuitry and facilities from the local TN464F DS1 board to the remote test  
equipment or other DEFINITY communications system.  
The test is destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS one-way-span-test-begin command.  
All trunks or ports on the UDS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the One-Way Span  
Tes t.  
The One-Way Span Test has the TN464F UDS1 Interface circuit pack transmit a  
framed 3-in-24 test pattern and attempt to receive and verify the pattern. If the  
TN464F board receives a framed 3-in-24 test pattern sent from another DEFINITY  
G3V3 or test equipment at the far-end of the DS1, it will begin counting bit errors  
within the received pattern.  
The status of the One-Way Span test will be available in the hardware error log  
via error type 3902. Several distinct aux values will be used to give the user  
information of the status of the test.  
The list measurements ds1 summary command will display the length of time the  
test has been running (Test Duration field) and number of bit errors detected  
(Loopback/Span Test Bit-Error Count field). If the test pattern is being sent  
cleanly over the span from the far-end, the number of bit errors should be very  
low. The Tes t Dur at ion field will show 0 until the test pattern is received from the  
far-end. Upon receiving the test pattern, the board will begin calculating the test  
duration and number of bit errors. The command will also display the  
Loopback/Span test executing (Test field), the type of pattern generated for the  
Loopback/Span test (Pattern field), and whether the pattern (i.e. 3-in-24 Pattern)  
is synchronized (Synchronized field).  
To terminate the test, enter the test ds1-loop UUCSS end-loopback/span-test  
command or the release board command. Using the release board command  
will restore all trunks or ports on the TN464F UDS1 Interface circuit pack to the  
in-service state.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1247  
Table 3-533. TEST #1214 One-Way Span Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the test ds1-loop UUCSS one-way-span-test-begin command at  
1-minute intervals a maximum of 5 times.  
1005  
1015  
ABORT  
One-Way Span Test cannot be executed in the current configuration. To run  
this, the TN464F or later suffix UDS1 must be administered for 24-channel  
operation. The "Bit Rate" field on the DS1 circuit pack administration form must  
be set to "1.544" for 24-channel operation.  
ABORT  
ABORT  
Ports on the UDS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of  
the UDS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
1039  
The UDS1 Interface circuit pack is providing timing for the system. Executing  
this test could cause major system disruption.  
If the UDS1 Interface circuit pack needs to be tested, set the synchronization  
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit  
pack via the following command sequence:  
1. Issue the disable synchronization-switch command.  
2. Next, issue the set synchronization UUCSS command.  
3. Lastly, issue the enable synchronization-switch command.  
1950  
ABORT  
Another loopback/span test is already executing on the DS1 board or the  
board is in a network requested loopback mode (Line loopback or Payload  
loopback). The hardware error log will indicate whether a Customer Loopback  
Jack Test, Far CSU Loopback Test, or the One-Way Span Test is executing or if  
the board is in line loopback or payload loopback mode. Only one  
long-duration loopback/span test can be active at a given time. Thus, if a  
loopback/span test is already active, that test must be terminated via the test  
ds1-loop UUCSS end-loopback/span-test command in order to execute this  
test.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1248  
Table 3-533. TEST #1214 One-Way Span Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of  
service state. The system will try to restore the circuit pack within 15  
minutes. When no faults are detected for 15 minutes, the UDS1  
interface circuit pack is restored to normal operation. All of the trunks for  
the UDS1 interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against  
the associated trunk circuits. If the facility is OK and the error occurs  
again after 15 minutes, replace the circuit pack.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1249  
Table 3-533. TEST #1214 One-Way Span Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The One-Way Span test has successfully began transmitting a framed 3-in-24  
test pattern. The test will continue to run until the system technician enters the  
test ds1-loop UUCSS end-loopback/span-test command or the release board  
UUCSS command.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board  
is shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Inject Single Bit Error Test (#1215). This test is destructive.  
The Inject Single Bit Error Test will cause a single bit error to be sent within an  
active framed 3-in-24 test pattern.  
The test is highly destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS inject-single-bit-error command. An attempt to  
use this command will be rejected if none of the three long-duration DS1  
loopback/span tests (CPE Loopback Jack Test, Far CSU Loopback Test,  
One-Way Span Test) are active on a TN464F circuit pack.  
All trunks or ports on the UDS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running the Inject Single Bit  
Error Test.  
The list measurements ds1 summary command displays the number of bit errors  
detected (Loopback/Span Test Bit-Error Count field). Injecting this single bit error  
should increment the bit error count of the loopback/span test by one.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1250  
Table 3-534. TEST #1215 Inject Single Bit Error Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the test ds1-loop UUCSS inject-single-bit-error command at 1-minute  
intervals a maximum of 5 times.  
1015  
2000  
ABORT  
Ports on the UDS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of the  
UDS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
ABORT  
Response to the test was not received within the allowable time period. This may  
be due to hyperactivity. Error type 1538 in the error log indicates hyperactivity.  
The hyperactive circuit pack is out of service and one or more of the following  
symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of service  
state. The system will try to restore the circuit pack within 15 minutes.  
When no faults are detected for 15 minutes, the UDS1 interface circuit  
pack is restored to normal operation. All of the trunks for the UDS1  
interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against the  
associated trunk circuits. If the facility is OK and the error occurs again  
after 15 minutes, replace the circuit pack.  
2100  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1251  
Table 3-534. TEST #1215 Inject Single Bit Error Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
A single bit error has been successfully injected into an active framed 3-in-24  
test pattern.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be due  
to incorrect translations, no board is inserted, an incorrect board is inserted, or  
an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1 UUCSS  
command to administer the UDS1 interface if it is not already administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
End Loopback/Span Test (#1216)  
This test is destructive.  
The End Loopback/Span Test will terminate an active loopback or span test on a  
TN464F UDS1 circuit pack. Bit error counting against the received test pattern  
stream is terminated and sending of the framed 3-in-24 test pattern is halted. If  
either the CPE Loopback Jack or the far-end CSU is looped, the appropriate  
loopback deactivate code is sent. If the loopback could not be deactivated, then  
the test will FAIL and a MINOR alarm will be noted in the alarm log until the  
loopback is cleared.  
The test is highly destructive and can only be initiated by a system technician  
demanded test ds1-loop UUCSS end-loopback/span-test command. Since only  
one of these three different long-duration loopback/span tests can be active at a  
time, the TN464F circuit pack knows which loopback/span test to terminate.  
All trunks or ports on the UDS1 Interface circuit pack must be busied out via the  
system technician busyout board command before running this End  
Loopback/Span Test.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1252  
The list measurements ds1 summary command will display the length of time the  
test ran (Test Duration field) and number of bit errors detected (Loopback/Span  
Test Bit-Error Count field).  
To restore the trunks or ports on the TN464F UDS1 Interface circuit pack to the  
in-service state, execute the release board command.  
Table 3-535. TEST #1216 End Loopback/Span Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
Internal system error  
1. Retry the test ds1-loop UUCSS end-loopback/span-test command at  
1-minute intervals a maximum of 5 times.  
1005  
1015  
ABORT  
End Loopback/Span Test cannot be executed in the current configuration. To  
run this test, the TN464F or later suffix DS1 board must be administered for  
24-channel operation. The "Bit Rate" field on the DS1 circuit pack  
administration form must be set to "1.544" for 24-channel operation.  
ABORT  
Ports on the UDS1 Interface circuit pack have not been busied out to  
out-of-service.  
1. Enter the busyout board UUCSS command to put all trunks or ports of  
the UDS1 Interface circuit pack into the out-of-service state.  
2. Retry the command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1253  
Table 3-535. TEST #1216 End Loopback/Span Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
2000  
ABORT  
Response to the test was not received within the allowable time period. This  
may be due to hyperactivity. Error type 1538 in the error log indicates  
hyperactivity. The hyperactive circuit pack is out of service and one or more of  
the following symptoms may be exhibited.  
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error  
code 2000.  
2. The tests run on the ports of this circuit pack are returning a no board  
result.  
3. A busyout or a release command has no affect on the test results.  
4. A list config command shows that the circuit pack and the ports are  
properly installed.  
NOTE:  
When hyperactivity occurs, the circuit pack is isolated from the system,  
and all of the trunks for this circuit pack are placed into the out of  
service state. The system will try to restore the circuit pack within 15  
minutes. When no faults are detected for 15 minutes, the UDS1  
interface circuit pack is restored to normal operation. All of the trunks for  
the UDS1 interface circuit pack are then returned to the in service state.  
Hyperactivity is often caused by the associated facility. In such a case,  
faults (such as slips, misframes, or blue alarms) would be entered in the  
error log. In addition, many hardware errors would be logged against  
the associated trunk circuits. If the facility is OK and the error occurs  
again after 15 minutes, replace the circuit pack.  
2100  
1313  
ABORT  
FAIL  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
The TN464F UDS1 circuit pack could not deactivate the loopback through the  
Customer Loopback Jack.  
1. Retry the test ds1-loop UUCSS end-loopback/span-test command at  
1-minute intervals for a maximum of 5 times.  
1314  
FAIL  
The TN464F UDS1 circuit pack could not deactivate the loopback through the  
far-end CSU.  
1. Make sure that the far-end DS1 is installed if the far-end CSU is a 120A1  
Lucent CSU Module/T1 Sync Splitter.  
2. Retry the test ds1-loop UUCSS end-loopback/span-test command at  
1-minute intervals for a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1254  
Table 3-535. TEST #1216 End Loopback/Span Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The active long-duration loopback or span test on the TN464F circuit pack  
was successfully terminated.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board  
is shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
ICSU Status LEDs Test (#1227)  
The TN464F UDS1 circuit pack has four status LEDs on the faceplate in addition  
to the three standard faceplate LEDs. These four status LEDs are associated with  
the 120A1 Channel Service Unit (CSU) Module that can be connected to the  
TN464F board via the I/O connector panel on the back of the port carrier. The  
TN464F circuit pack combined with the 120A1 CSU Module or the 401A T1 Sync  
Splitter forms an Integrated CSU (I-CSU).  
This test is a visual test. It will light the four status LEDs red for 5 seconds, then  
light them green for 5 seconds, then light them yellow for 5 seconds, then turn  
the LEDs off and returns control of the status LEDs to the circuit pack.  
This test will only be executed on TN464F or later suffix UDS1 circuit packs  
administered for 24-channel operation (1.544 bit rate).  
If the 120A1 CSU Module or the 401A T1 Sync Splitter is not physically installed,  
the status LEDs are always off and this test will abort.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1255  
Table 3-536. TEST #1227 ICSU Status LEDs Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
Internal system error  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1005  
1951  
The ICSU Status LEDs test can not be executed for the current configuration.  
The test applies only to TN464F or later UDS1 circuit packs administered for  
24-channel operation (1.544 bit rate).  
1. If the circuit pack is a TN464F or later suffix UDS1 circuit pack, then retry  
the command.  
ABORT  
The ICSU Status LEDs Test can not be executed because a 120A1 or later  
suffix CSU Module or a 401A or later suffix T1 Sync Splitter is not physically  
installed. If using a 120A1 CSU Module or the 401A T1 Sync Splitter, physically  
connect it to the TN464F board on the back of the port carrier. Otherwise,  
ignore this abort.  
2100  
2500  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals for a maximum of 5 times.  
Internal system error.  
1. Retry the command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
UDS1-BD (UDS1 Interface Circuit Pack)  
3-1256  
Table 3-536. TEST #1227 ICSU Status LEDs Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
The ICSU Status LEDs test executed successfully. A PASS result, however,  
does not necessarily mean that the status LEDs behaved properly. It only  
means that the software successfully attempted to light the status LEDs. This is  
a visual test. The service technician must visually exam the behavior of the  
LEDs while the test is running. The LEDs are functioning properly if the four  
status LEDs are lit red for 5 seconds, then lit green for 5 seconds, then lit yellow  
for 5 seconds. If the LEDs behave differently, the board should be replaced at  
the customer’s convenience.  
0
NO  
BOARD  
The test could not relate the internal ID to the port (no board). This could be  
due to incorrect translations, no board is inserted, an incorrect board is  
inserted, or an insane board is inserted.  
1. Ensure that the board translations are correct. Execute the add ds1  
UUCSS command to administer the UDS1 interface if it is not already  
administered.  
2. If the board was already administered correctly, check the error log to  
determine whether the board is hyperactive. If this is the case, the board is  
shut down. Reseating the board will re-initialize the board.  
3. If the board was found to be correctly inserted in step 1, then issue the  
busyout board command.  
4. Issue the reset board command.  
5. Issue the release busy board command.  
6. Issue the test board long command.  
This should re-establish the linkage between the internal ID and the port.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-BD  
3
3-1257  
VC-BD  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test board PCSS l r#  
test board PCSS l r#  
test board PCSS s r#  
Full Name of MO  
VC-BD  
VC-BD  
VC-BD  
MAJOR  
MINOR  
Voice Conditioner Circuit Pack  
Voice Conditioner Circuit Pack  
Voice Conditioner Circuit Pack  
2
WARNING  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B,  
or C); and SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02, ...).  
2. Refer to XXX-BD (Common Port Board) Maintenance documentation.  
!
CAUTION:  
If the TN788 Voice Conditioner Circuit Pack (VC-BD) is not Vintage 2 or  
later, it must be replaced.  
The TN788 Voice Conditioner Circuit Pack (VC-BD) is a service circuit pack that  
provides conditioning for the audio signals from multimedia equipment based on  
the CCITT H.221 standard. The TN788 transcodes, gain adjusts, and bridges the  
audio bit streams demultiplexed by the TN787 (MMI) circuit pack and transmits  
encoded, exclusive audio conference sums onto the TDM bus so that the MMI  
can multiplex the audio, video, and data streams for the H.221 endpoints.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-BD  
3
3-1258  
Error Log Entries and Test to Clear Values  
Table 3-537. VC-BD Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
1
0
0
Any  
Any  
Any  
ON  
test board PCSS sh r 1  
1 (a)  
Any  
0
None  
MIN  
WNG  
MIN  
18 (b)  
257 (c)  
busyout board PCSS  
OFF  
ON  
release board PCSS  
test board PCSS r 20  
Any  
Control Channel Loop  
Test (#52)  
513 (d)  
4352 to  
4357  
769 (e)  
1025 (f)  
1281 (g)  
4358  
4363  
Any  
NPE Audit Test (#50)  
SAKI Sanity Test (#53)  
SAKI Sanity Test (#53)  
MAJ  
MIN  
ON  
ON  
1293 to  
1294 (h)  
46088  
to  
See note (g)  
46096  
1538 (i)  
46082  
MIN  
ON  
1. Run the short test sequence first. If all tests pass, run the long test sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. The circuit pack stopped functioning or it was removed from the system.  
This alarm is logged approximately 11 minutes after the circuit pack is  
removed and/or the SAKI Sanity Test (#53) fails.  
To resolve this error, insert a circuit pack in the same slot as the error  
indicates, if the circuit pack is not already in the system. Or, if the circuit  
pack is in the system and the red LED is on, then follow instructions for  
Red alarms.  
!
CAUTION:  
If the TN788 Voice Conditioner Circuit Pack (VC-BD) is not Vintage 2  
or later, it must be replaced.  
b. This circuit pack is busied out by the busyout board PCSS command.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-BD  
3
3-1259  
c. Transient communication problems exist between the switch and this  
circuit pack. Execute the test board PCSS command and refer to the  
repair procedures for the Control Channel Loop Around Test (#52).  
d. The circuit pack detected an on-board hardware failure. The reported aux  
data values correspond to the following detected errors:  
Error  
4352  
4353  
4355  
4357  
Description  
External RAM error  
Internal RAM error  
ROM Checksum error  
Instruction set error  
Reset the circuit pack by executing the busyout board PCSS, reset  
board PCSS, and release board PCSS commands. When it is reset, the  
circuit pack executes a set of tests to detect the presence of any of the  
above faults. The detection of one these errors during initialization causes  
the circuit pack to lock-up and appear insane to the system. See the repair  
procedures in footnote (a) for error type 1.  
e. The circuit pack detects a program logic error. While no action is required,  
this error may lead to errors of other types being reported against this  
circuit pack.  
f. The circuit pack cannot update NPE memory and read it back. This error  
type can be ignored, but it may lead to other error types being reported  
against this circuit pack.  
g. A critical hardware failure has been detected on the circuit pack. Use  
busyout board PCSS, reset board PCSS, followed by release board  
PCSS. If test #53 passes, the on-board circuitry is healthy. Use test board  
PCSS long clear to retire the alarm. If test #53 fails, replace the circuit  
pack.  
h. The circuit pack detected a critical hardware failure. Reset the circuit pack  
by issuing the busyout board PCSS, reset board PCSS, and release  
board PCSS commands. If the Circuit Pack Restart Test (#594) passes,  
then the on-board circuitry is healthy. Retire the alarm by issuing the test  
board PCSS long clear command. If the Circuit Pack Restart Rest (#594)  
fails, replace the circuit pack.  
The reported error types correspond to the following detected errors:  
Error  
1293  
1294  
Description  
On-board auxiliary processor insane  
Internal memory access error  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-BD  
3
3-1260  
i. The circuit pack is hyperactive — it is flooding the switch with messages  
sent over the control channel. The circuit pack is taken out of service when  
a threshold number of these errors is reported to the switch. Clear the  
alarm by using busyout board PCSS, reset board PCSS, test board  
PCSS long clear, and release board PCSS. If the error recurs within 10  
minutes, then replace the circuit pack.  
System Technician-Demanded Tests: Descriptions  
and Error Code  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
D/ND  
Control Channel Loop-Around Test (#52) (a)  
X
X
ND  
1. D = Destructive; ND = Nondestructive  
!
CAUTION:  
If the TN788 Voice Conditioner Circuit Pack (VC-BD) is not Vintage 2 or  
later, it must be replaced.  
Note:  
a. Refer to the repair procedure described in the ‘‘XXX-BD (Common Port  
Circuit Pack)’’) maintenance documentation for a description of this test.  
Control Channel Loop Around Test (#52)  
Refer to the repair procedure described in the XXX-BD (Common Port Circuit  
Pack) maintenance documentation as Control Channel Loop Around Test (#52).  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-DSPPT  
3
3-1261  
VC-DSPPT  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test port PCSSpp l r#  
test port PCSSpp l r#  
test port PCSSpp l r#  
Full Name of MO  
VC-DSPPT  
VC-DSPPT  
VC-DSPPT  
MAJOR  
MINOR  
Voice Conditioner DSP Port  
Voice Conditioner DSP Port  
Voice Conditioner DSP Port  
WARNING  
1. Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B,  
or C); and SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02, ...), and pp is the address of the port (for example, 01, 02, ...).  
Each Voice Conditioner Circuit Pack (VC-BD) provides two types of resources:  
1. Transcoder Resources used for encoding and decoding audio formats  
2. Summer Resources used for summing audio from different sources  
The eight Voice Conditioner DSP ports are the transcoder resources on the  
VC-BD.  
Error Log Entries and Test to Clear Values  
Table 3-538. VC-DSPPT Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/ Off  
Board  
Associated Test  
Test to Clear Value  
test port PCSSpp sh r 1  
release port PCSSpp  
test port PCSSpp 1 r 3  
test port PCSSpp sh r 3  
1
0
0
Any  
Any  
Any  
18 (a)  
0
busyout port PCSSpp  
WNG  
MIN  
MIN  
OFF  
ON  
ON  
257 (b)  
513 (c)  
Any  
Any  
NPE Crosstalk Test (#6)  
VC DSP Port Local TDM  
Loopback Test (#1104)  
778 to  
781 (d)  
Any  
Any  
VC Port Reset DSP Test  
(#1106)  
MAJ  
ON  
See note (d)  
1025 (e)  
1281 (f)  
WNG  
MIN  
ON  
ON  
VC DSP Port DSP  
test port PCSSpp sh r 3  
Loopback Test #(1105)  
3840 (g)  
1. Run the short test sequence first. If all test pass, run the long test sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-DSPPT  
3
3-1262  
Notes:  
a. This port has been busied out by the busyout port PCSSpp command.  
b. The VC DSP Port NPE Crosstalk Test(#1103) failed.  
c. The VC DSP Port Local TDM Loopback Test(#1104) failed. Run the Long  
Test Sequence.  
d. A critical hardware failure has been detected on the circuit pack. Reset  
the port by the busyout port PCSSpp and reset port PCSSpp  
commands. If the VC Reset DSP Test (#1106) passes, then the on-board  
circuitry is healthy. Retire the alarm with the test port PCSSpp long clear  
command.  
e. The VC DSP port reported loss of framing on the Service Channel between  
the VC and MMI circuit packs.  
f. The VC DSP Port DSP Loopback Test (#1105) failed.  
g. The DSP corresponding to this port on the VC circuit pack reported a  
firmware error. No action is required.  
System Technician-Demanded Tests:  
Descriptions and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the DSP NPE Crosstalk Test, for example, you may  
also clear errors generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
DSP NPE Crosstalk Test (#1103)  
TDM Loopback Test (#1104)  
DSP Loopback Test (#1105)  
D/ND  
X
X
X
D
D
D
X
X
1. D = Destructive; ND = Nondestructive  
VC DSP Port NPE Crosstalk Test (#1103)  
This test is destructive.  
The NPE controls port connectivity and gain and provides conferencing  
functions. The NPE Crosstalk test verifies that this port’s NPE channel talks on the  
selected time slot and never crosses over to time slots reserved for other  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is part of the port’s long test sequence and takes  
approximately 20 to 30 seconds to complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-DSPPT  
3
3-1263  
Table 3-539. TEST #1103 VC DSP Port NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000  
1001  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
0-3  
FAIL  
The NPE of the tested port was transmitting in error. This causes noisy and  
unreliable connections.  
1. Replace circuit pack.  
PASS  
The port is correctly using its allocated time slots.  
1. To be sure that this is not an intermittent problem, repeat this test a  
maximum of 10 times to make sure that it continues to pass.  
2. If complaints still persist, examine the station, connections, and wiring.  
VC DSP Port Local TDM Loopback Test (#1104)  
This test is destructive.  
This test verifies the connectivity of a VC DSP Port across the TDM bus. It aborts  
if calls associated with the port are in progress. Failure of this test indicates an  
on-board fault associated with the port hardware on the circuit pack. The  
Loopback Test runs the following tests (refer to Figure 3-51):  
1. A looparound test across the TDM bus.  
2. A conference circuit test.  
The tests are run in the above order; if one test fails, an error code is returned  
and the remaining tests in the sequence are not executed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-DSPPT  
3
3-1264  
Figure 3-51. VC Circuit Pack DSP Port Local TDM Loopback Test  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-DSPPT  
3
3-1265  
Table 3-540. TEST #1104 VC DSPPT Local  
TDM Loopback Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
1001  
ABORT  
System resources required to run this test are not available, or the port is  
busy with a valid call.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
ABORT  
The system could not allocate time slots for the test. The traffic load on the  
system is very high, or time slots may be out-of-service due to TDM-BUS  
errors. Refer to ‘‘TDM-BUS (TDM Bus)’’ to diagnose TDM Bus errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat the test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a Tone Detector for the test. The system is  
oversized for the number of Tone Detectors present, or some Tone  
Detectors are out-of-service.  
1. Resolve any ‘‘TTR-LEV (TTR Level)’’ errors.  
2. Resolve any ‘‘TONE-PT (Tone Generator)’’ errors.  
3. If neither condition exists, retry the test at 1-minute intervals.  
1004  
2000  
ABORT  
ABORT  
The port is seized by a user for a valid call. Use the status station  
command for the station associated with this port and determine if the port  
is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Response to the test was not received from the VC-BD circuit pack within  
the allowable time period.  
1. If this result occurs repeatedly, attempt to reset the port by using the  
busyout port PCSSpp and reset port PCSSpp commands.  
2. If this result occurs again, replace the circuit pack.  
Internal system error  
2012  
2100  
2103  
0-3  
ABORT  
ABORT  
ABORT  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Could not allocate the necessary resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not make the conference connection for the test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The TDM Looparound Test failed.  
1. Replace circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-DSPPT  
3
3-1266  
Table 3-540. TEST #1104 VC DSPPT Local  
TDM Loopback Test — Continued  
Error  
Code  
Test  
Result  
Description/Recommendation  
The Conference Circuit Test failed.  
4-7  
FAIL  
1. Replace circuit pack.  
PASS  
The VC DSP Port Local TDM Looparound Test passed.  
VC-DSP Port DSP Loopback Test (#1105)  
This test is destructive.  
This test verifies the connectivity of a VC-DSPPT across the TDM bus as shown in  
Figure 3-52. It aborts if calls associated with the port are in progress. Failure of  
this test indicates an on-board fault associated with the port hardware on the  
circuit pack.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-DSPPT  
3
3-1267  
Figure 3-52. VC Circuit pack DSP Port DSP Looparound Test  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-DSPPT  
3
3-1268  
Table 3-541. TEST #1105 VC-DSP Port DSP Loopback Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
System resources required to run this test are not available, or the port is  
busy with a valid call.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
ABORT  
The system could not allocate time slots for the test, the traffic load on the  
system is very high, or time slots are out-of-service due to TDM-BUS errors.  
Refer to ‘‘TDM-BUS (TDM Bus)’’ to diagnose TDM Bus errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat the test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a Tone Detector for the test, the system is  
oversized for the number of Tone Detectors present, or some Tone  
Detectors are out-of-service.  
1. Resolve any ‘‘TTR-LEV (TTR Level)’’ errors.  
2. Resolve any ‘‘TONE-PT (Tone Generator)’’ errors.  
3. If neither condition exists, retry the test at 1-minute intervals a maximum  
of 5 times.  
1004  
2000  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use the status station  
command for the station associated with this port and determine if the port  
is available for testing  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Response to the test request was not received from the VC-BD circuit pack  
within the allowable time period.  
1. If this result occurs repeatedly, reset the circuit pack if the other ports  
are not in use by using the busyout port PCSSpp and reset port  
PCSSpp commands.  
2. If this result occurs again, replace the circuit pack.  
Internal system error  
2012  
2100  
0, 1  
ABORT  
ABORT  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Could not allocate the necessary system resources to run this test.  
1. Rerun the test at 1-minute intervals a maximum of 5 times.  
The VC-DSPPT DSP Loopback Test failed.  
1. Replace the circuit pack.  
PASS  
The VC DSPPT DSP Loopback Test passed  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-DSPPT  
3
3-1269  
VC Port Reset DSP Test (#1106)  
This test is destructive.  
This test resets the VC-DSPPT and the DSP associated with it. As part of the reset  
procedure, the VC-DSPPT will execute a series of self- tests on the hardware. If  
these self- tests fail, the test will fail; otherwise the test will pass.  
Before executing the test, the VC-DSPPT must be busied out by executing the  
busy port PCSSpp command. After the completion of the test, the VC-DSPPT  
must be released by executing the release port PCSSpp command.  
Table 3-542. TEST #1106 VC Port Reset DSP Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
ABORT  
ABORT  
System resources required to run this test are not available, or the port may  
be busy with a call.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The VC-DSPPT is not busied out.  
1015  
2000  
1. Busy out the VC-DSPPT by executing the busy port PCSSpp command  
and then retry the test.  
Response to the test was not received from the VC-DSPPT within the  
allowable time period.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If this result occurs again, replace the circuit pack.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Could not allocate the necessary resources for this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The reset of the VC-DSPPT was unsuccessful.  
1. Replace circuit pack.  
PASS  
The VC-DSPPT was successfully reset.  
1. Release the VC-DSPPT by executing the reset port PCSSpp  
command.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
VC-LEV (Voice Conditioner DSP Port Level)  
3-1270  
VC-LEV (Voice Conditioner  
DSP Port Level)  
MO Name (in  
Alarm Log)  
Alarm  
Level  
Initial Command to Run  
Full Name of MO  
VC-LEV  
VC-LEV  
MAJOR  
See ‘‘Resolving VC-LEV Errors/Alarms’’  
Enable the MMCH feature on the System-Parameters Customer-Options form  
before changing the fields.  
The Voice Conditioner (VC) Port Level MO monitors VC efficiency by tracking the  
number of VC ports that are in-service, and then comparing that number with the  
value entered in the VC field on the System-Parameters Maintenance form. This  
VCsfield is located under the Minimum Maintenance Thresholds section. The  
VCsfield contains the minimum number of VC ports needed for the Multimedia  
Call Handling (MMCH) feature, and is an administrable field. The VCsfield must  
contain a number between 0 and 126, and is entered by the system  
administrator. The MMCH feature must be enabled on the System-Parameters  
Customer-Options form before the VCsfield can be changed to a number greater  
than 0. For example, administering 8 in that field means 1 circuit pack. The  
algorithm for determining that a low level of VC resources exists uses the number  
entered in the VCsfield, and the number of VCs that are in-service in the system.  
Each VC circuit pack contains 16 physical ports: 8 ports are reserved for  
VC-DSPPT ports, and the remaining 8 ports are designated as VC-SUMPT ports.  
The 8 DSP ports are made up of 4 encoder and 4 decoder resources that encode  
and decode audio formats. Thus, one VC circuit pack is required for every 8  
ports of MMCH port capacity. If the number of in-service VC ports falls below the  
MMCH port capacity (value entered on the System-Parameters Maintenance  
form under the Minimum Maintenance Thresholds section and in the VCsfield), a  
VEC-LEV error is logged. If this outage continues for 15 minutes a MAJOR alarm  
is raised.  
Resolving VC-LEV Errors/Alarms  
VC ports are a key part of the MMCH feature, any loss in the number of ports  
available for use degrades the MMCH customer-defined service level.  
If a VC circuit pack or port is busied out using the busyout board or busyout  
port command, these out-of-service ports are not included in the VC level  
calculation, thus allowing a technician to busy out a VC circuit pack for  
maintenance reasons without causing a MAJOR alarm to be raised.  
NOTE:  
When diagnosing a VC-LEV problem, resolve any alarms raised against  
VC-BD or VC-DSPPT maintenance objects. Clearing VC-BD or VC-DSPPT  
alarms may clear the VC-LEV alarm.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
VC-LEV (Voice Conditioner DSP Port Level)  
3-1271  
The VC circuit pack is maintained by the software similarly to the Tone Detector  
circuit pack. Tone Detector circuit packs may be removed and reinserted in any  
port board slot without administration. The same rule applies to VC circuit packs.  
If a VC circuit pack is removed from service logically (by failing the Archangel  
sanity scan test) or is removed from service physically (by physically removing  
the circuit pack from the carrier), no error/alarm is raised against VC-BD or  
VC-DSPPT maintenance objects. Therefore, if a VC-LEV error/alarm exists, and  
none has been raised against VC-BD or VC-DSPPT maintenance objects, a VC  
circuit pack may have been removed from service causing the VC-LEV  
error/alarm. To resolve a VC-LEV MAJOR alarm, restore the number of VC ports  
available for service to be equal to or more than the calculated port capacity  
(value entered in the VCsfield).  
To determine how many VC circuit packs are needed for the MMCH feature:  
1. Display the System-Parameters Maintenance form by executing the  
command display system-parameters maintenance.  
2. Locate the number listed in the Minimum Maintenance Threshold (VCs)  
field. The MMCH feature requires one VC circuit pack for each four ports  
listed in the Minimum Maintenance Threshold (VCs) field.  
3. Divide the Minimum Maintenance Threshold value by 8 to determine the  
number of VC circuit packs needed. For example, a port capacity of 12  
listed in the Minimum Maintenance Threshold (VCs) field would require 2  
VC circuit packs.  
4. Use the list configuration command to verify that the number of VC  
circuit packs listed agrees with the required number of VC circuit packs  
(determined in step 3). If the number of VC circuit packs listed in the step  
3 differs from the calculated number, restore the number of VC circuit  
packs to the correct value, in order to resolve the VC-LEV alarm.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
VC-LEV (Voice Conditioner DSP Port Level)  
3-1272  
Error Log Entries and Test to Clear Values  
Table 3-543. VC-LEV Error Log Entries  
Error  
Type  
Aux  
Data  
On/ Off  
Board  
Associated Test  
None  
Alarm Level  
Test to Clear Value  
1 (a)  
Any  
MAJOR  
OFF  
Notes:  
a. The number of VC resources in the system that are in service has fallen  
below the calculated minimum value. If the number of in-service VC ports  
falls below the MMCH port capacity (value entered in the Minimum  
Maintenance Threshold VCsfield on the system parameters maintenance  
form), a VEC-LEV error is logged. If this outage continues for 15 minutes a  
MAJOR alarm is raised. To resolve this alarm, correct the out-of-service  
problem by following the procedures below:  
1. See ‘‘VC-DSPPT’’ and ‘‘VC-BD’’ and resolve any associated alarms.  
2. If a VC-LEV error/alarm exist and none has been raised against  
VC-BD or VC-DSPPT maintenance objects, a VC circuit pack may  
have been removed from service causing the VC-LEV error/alarm.  
To resolve a VC-LEV MAJOR alarm, restore the number of VC ports  
available for service to be equal to or more than the calculated port  
capacity. See ‘‘Resolving VC-LEV Errors/Alarms’’ above for details.  
System Technician-Demanded Tests:  
Descriptions and Error Code  
There are no System Technician-Demanded test for VC-LEV.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-SUMPT  
3
3-1273  
VC-SUMPT  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
test port PCSS l r#  
Full Name of MO  
VC-SUMPT  
VC-SUMPT  
VC-SUMPT  
MAJ  
MIN  
Voice Conditioner Summer Port  
Voice Conditioner Summer Port  
Voice Conditioner Summer Port  
test port PCSS l r#  
WNG  
test port PCSS s r#  
1. Where P is the universal cabinet number (1 for PPN); C is the carrier designation (for example,  
A, B, or C); SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02, ...).  
Each Voice Conditioner Circuit Pack (VC-BD) provides two types of resources:  
1. Transcoder Resources that are used for encoding and decoding audio  
formats  
2. Summer Resources that are used for summing audio formats from  
different sources.  
The Voice Conditioner Summer ports (VC-SUMPT) are the summer resources on  
the VC-BD. There are 8 such ports on a VC-BD.  
Error Log Entries and Test to Clear Values  
Table 3-544. VC-SUMPT Error Log Entries  
Error  
Type  
Aux  
Data  
Alarm  
Level  
On/Off  
Board  
Associated Test  
Test to Clear Value  
test port PCSSpp sh r 1  
release port PCSSpp  
test port PCSSpp sh  
1
0
0
Any  
Any  
Any  
OFF  
ON  
18 (a)  
0
busyout port PCSS  
WNG  
WNG  
MIN  
130 (b)  
257 (c)  
Any  
Any  
Control Channel Loop  
Test (#52)  
ON  
test board PCSSpp 1 r 3  
513 (d)  
VC Summer Port Local  
Loopback Test #(1100)  
MIN  
ON  
test board PCSSpp sh r 3  
1. Run the short test sequence first. If all test pass, run the long test sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-SUMPT  
3
3-1274  
Notes:  
a. This port has been busied out with the busyout port PCSSpp command.  
b. The circuit pack has been removed or has been insane for more than 11  
minutes. To clear the error, replace or reinsert the circuit pack.  
c. The NPE Crosstalk Test(#1103) failed.  
d. The VC Summer Port Local TDM Loopback Test(#1100) failed.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below. By clearing  
error codes associated with the TDM Loopback Test, for example, you may also  
clear errors generated from other tests in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#6) (a)  
TDM Loopback Test (#1100)  
D/ND  
X
X
D
D
X
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
This test is destructive.  
The NPE Crosstalk test verifies that this port’s NPE channel talks on the selected  
time slot and never crosses over to time slots reserved for other connections. If  
the NPE is not working correctly, one-way and noisy connections may be  
observed. This test is part of the port’s long test sequence and takes  
approximately 20 to 30 seconds to complete.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-SUMPT  
3
3-1275  
Table 3-545. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
System resources required to run this test are not available. The port may  
be busy with a valid call.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error  
2012  
2100  
ABORT  
ABORT  
Could not allocate the necessary resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
The NPE of the tested port was transmitting in error, causing noisy and  
unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port is correctly using its allocated time slots.  
1. To be sure that this is not an intermittent problem, repeat this test a  
maximum of 10 times.  
2. If complaints still persist, examine the station, connections, and wiring.  
VC Summer Port Local TDM Loopback  
Test (#1100)  
This test is destructive.  
This test verifies the connectivity of a VC Summer Port across the TDM bus. It  
aborts if calls associated with the port are in progress. Failure of this test  
indicates an on-board fault associated with the port hardware on the circuit pack.  
The Loopback Test runs the following tests (refer to Figure 3-53):  
■
A Looparound test across the TDM bus.  
A conference circuit test.  
■
The tests are run in the above order. If the first test fails, the switch returns an  
error code, and the second test is not executed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-SUMPT  
3
3-1276  
Figure 3-53. VC Circuit Pack Summer Port Loopback Test  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
VC-SUMPT  
3
3-1277  
Table 3-546. TEST #1100 VC Summer Port  
Local TDM Loopback Test  
Error  
Code  
Test  
Result  
Description/Recommendation  
1000  
ABORT  
System resources required to run this test are not available, or the port may  
be busy with a valid call.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1002  
ABORT  
The system could not allocate time slots for the test. The traffic load on the  
system is very high or time slots are out-of-service due to TDM-BUS errors.  
Refer to ‘‘TDM-BUS (TDM Bus)’’ maintenance documentation to diagnose  
any active TDM Bus errors.  
1. If the system has no TDM-BUS errors and is not handling heavy traffic,  
repeat the test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a Tone Detector for the test, the system is  
oversized for the number of Tone Detectors present, or some Tone  
Detectors are out-of-service.  
1. Resolve any ‘‘TTR-LEV (TTR Level)’’ errors.  
2. Resolve any ‘‘TONE-PT (Tone Generator)’’ errors.  
3. If neither condition exists, retry the test at 1-minute intervals a maximum  
of 5 times.  
1004  
2000  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use the status station  
command for the station associated with this port to determine whether the  
port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Response to the test request was not received from the VC-BD circuit pack  
within the allowable time period.  
1. If this result occurs repeatedly, reset the circuit pack if the other ports  
are not in use. Reset the circuit pack by issuing the busyout board  
PCSS and the reset board PCSS commands.  
2. If this result occurs again, replace the circuit pack.  
Internal system error  
2012  
2100  
2103  
ABORT  
ABORT  
ABORT  
Could not allocate the necessary system resources to run this test.  
The system could not make the conference connection for the test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The TDM Loop Around Test failed.  
0
1
FAIL  
FAIL  
The Conference Circuit Test failed.  
1. Replace circuit pack.  
PASS  
The VC Summer Port Local TDM Loopback Test passed.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
WAE-PORT (Wideband Access Endpoint Port)  
3-1278  
WAE-PORT (Wideband Access  
Endpoint Port)  
MO Name (in  
Alarm Log)  
Alarm Level  
Initial Command to Run  
Full Name of MO  
1
WAE-PORT  
MINOR  
test access-endpoint  
<extension> l  
Wideband Access  
Endpoint Port  
WAE-PORT  
WARNING  
test access-endpoint  
<extension>  
Wideband Access  
Endpoint Port  
1. For additional repair information, see also UDS1-BD (UDS1 Interface Circuit Pack)  
Maintenance documentation.  
The Wideband Switching capability supports end-to-end connectivity between  
customer endpoints at data rates from 128 to 1536 kbps over T1 facilities and to  
1984 kbps over E1 facilities. DEFINITY switching capabilities are extended to  
support wideband calls comprised of multiple DS0s that are switched end-to-end  
as a single entity.  
The Wideband Switching capability extends the Administered Connections  
feature to include non-signaling Wideband Access Endpoints. Endpoint  
application equipment with direct T1 or E1 interfaces may connect directly to the  
switch’s line-side facilities. Application equipment without T1 or E1 interfaces  
requires a Terminal Adapter, such as a DSU/CSU. The terminal adapter or  
endpoint application equipment is connected to the Universal DS1 circuit pack  
(TN464C). These endpoints are administered as Access Endpoints, and they  
have no signaling interface to the switch. Instead, they simply transmit and  
receive data. (Some applications detect and respond to the presence or  
absence of data.) Calls are initiated from these endpoints using the Administered  
Connections feature.  
Multiple Access Endpoints on one line-side UDS1 circuit pack (TN464C) facility  
are separate and distinct within the facility, and the endpoint application  
equipment must be administered to send and receive the correct data rate over  
the correct DS0s. All Administered Connections originating from Access  
Endpoints use the entire bandwidth administered for the Access Endpoint. An  
incoming call of a different data rate then that administered for the Access  
Endpoint cannot be routed to the Access Endpoint.  
Although Wideband Access Endpoints are used primarily for line-side facilities,  
these endpoints can also be administered on network DS1 facilities to connect  
DEFINITY to non-switched network services, such as the AT&T fractional T-1  
service. An example of this is the AT&T Static Integrated Network Access, where  
a trunk group to AT&T 4Ess Switched Services shares an access T-1 facility with  
a Wideband Access Endpoint. In this case, the Wideband Access Endpoint is  
connected to the AT&T fractional T-1 service, and it does not terminate on local  
endpoint equipment but is connected to a far-end CPE (for example, another  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
WAE-PORT (Wideband Access Endpoint Port)  
3-1279  
DEFINITY PBX) via the dedicated fractional T-1. All Wideband Access Endpoint  
functionality and operation is identical on both line-side and network facilities.  
However, because maintenance capabilities are limited to the Wideband Access  
Endpoint interface, and because faults can occur end-to-end, troubleshooting  
procedures based on an end-to-end view of the network is required.  
Wideband Access Endpoint Port maintenance provides a strategy for  
maintaining a Wideband Access Endpoint Port via a port on the Universal DS1  
interface circuit pack hardware. The maintenance strategy involves logging  
Wideband Access Endpoint Port hardware errors, running tests for port  
initialization, periodic and scheduled maintenance, system  
technician-demanded tests, and alarm escalation and resolution. Two different  
port service states are specified in the Wideband Access Endpoint Port  
maintenance. These states include out-of-service, where the port is in a  
deactivated state and cannot be used for calls, and in-service, where the port is  
in an activated state and can be used for calls. If the Universal DS1 Interface  
circuit pack (TN464C) is out-of-service, all ports on the Universal DS1 Interface  
circuit pack (TN464C) are placed into the out-of-service state.  
Hardware Error Log Entries and Test to Clear  
Values  
Wideband Access Endpoint Maintenance Error Log Entries  
Error  
Type  
Aux  
Data  
On/Off  
Board  
Associated Test  
Any  
Alarm Level  
Test to Clear Value  
1
0
0
Any  
Any  
test access-endpoint  
<extension> sh r 1  
18 (a)  
0
busyout  
access-endpoint  
WARNING  
WARNING  
MINOR  
OFF  
ON  
ON  
ON  
release access-endpoint  
<extension>  
130 (b)  
1281 (c)  
1537 (d)  
None  
test access-endpoint  
<extension>  
Conference Circuit  
(Test #7)  
test access-endpoint  
<extension> l r 4  
NPE Crosstalk Test  
(#6)  
MINOR  
test access-endpoint  
<extension> l r 3  
1793 (e)  
3840 (f)  
None  
test board PCSS long  
Any  
Port Audit and  
Update (Test #36)  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
WAE-PORT (Wideband Access Endpoint Port)  
3-1280  
Notes:  
a. The wideband access endpoint has been busied out by a busyout  
access-endpoint <extension> command. No calls can be made to this  
extension.  
b. The circuit pack has been removed, or it has been insane for more than 11  
minutes. To clear the error, reinsert or replace the circuit pack.  
c. The Conference Circuit Test (#7) failed on this port. See Test #7 for repair  
procedures.  
d. The NPE Crosstalk Test (#6) failed on this port. See Test #6 for repair  
procedures.  
e. There was a failure of the TN464C UDS1 Interface circuit pack. See  
UDS1-BD Maintenance documentation for details.  
f. The Port Audit and Update Test (#36) failed due to an internal system  
error. Enter the status access-endpoint <extension> command and  
verify the status of the port. If the wideband access endpoint is  
out-of-service, enter the release access-endpoint <extension>  
command to put it back to in-service. Retry the test command. If the test  
continues to fail, escalate the problem.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in the table below when  
inspecting errors in the system. By clearing error codes associated with the NPE  
Crosstalk Test, for example, you may also clear errors generated from other tests  
in the testing sequence.  
Short Test  
Sequence  
Long Test  
Sequence  
1
Order of Investigation  
NPE Crosstalk Test (#6)  
D/ND  
ND  
X
X
X
Conference Circuit Test (#7)  
ND  
Port Audit and Update Test (#36)  
X
ND  
1. D = Destructive; ND = Nondestructive  
NPE Crosstalk Test (#6)  
One or more Network Processing Elements (NPEs) reside on each circuit pack  
with a TDM Bus interface. (The TN464C UDS1 circuit pack has one  
SCOTCH-NPE chip instead of several NPE chips). The NPE controls port  
connectivity and gain, and it provides conferencing functions on a per-port basis.  
The NPE Crosstalk Test verifies that this port’s NPE channel talks on the selected  
time slot and that it never crosses over to time slots reserved for other  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
WAE-PORT (Wideband Access Endpoint Port)  
3-1281  
connections. If the NPE is not working correctly, one-way and noisy connections  
may be observed. This test is usually only part of a port’s Long Test Sequence,  
and it takes between 20 and 30 seconds to complete.  
Table 3-547. TEST #6 NPE Crosstalk Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use on a valid call. Use the status access-endpoint <extension>  
command to determine when the port is available for testing.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
System resources required for this test are not available.  
1001  
1002  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The system could not allocate time slots for the test. The system may be  
under heavy traffic conditions, or it may have time slots that are  
out-of-service due to TDM-BUS errors. The status health command can  
be used to determine if the system is experiencing heavy traffic. Refer to  
TDM-BUS Maintenance documentation to diagnose any active TDM-BUS  
errors.  
1. If system has no TDM-BUS errors, and if it is not handling heavy traffic,  
repeat the test at 1-minute intervals a maximum of 5 times.  
1003  
ABORT  
The system could not allocate a tone receiver for the test. The system may  
be oversized for the number of Tone Detectors present, or some Tone  
Detectors may be out-of-service. The list measurement tone-receiver  
command displays information on the system’s tone receivers.  
1. Look for TTR-LEV errors in the Error Log. If errors are present, refer to  
TTR-LEV Maintenance documentation.  
2. Look for TONE-PT errors in the Error Log. If errors are present, refer to  
TONE-PT Maintenance documentation.  
3. If neither condition exists, retry the test at 1-minute intervals a  
maximum of 5 times.  
1004  
ABORT  
The port has been seized by a user for a valid call. Use the status  
access-endpoint <extension> command to determine when the port is  
available for testing. The port is available when it is in the in-service/idle  
state.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
WAE-PORT (Wideband Access Endpoint Port)  
3-1282  
Table 3-547. TEST #6 NPE Crosstalk Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1020  
ABORT  
The test did not run due either to a previously existing error on the specific  
port or to a more general circuit pack error.  
1. Examine the Error Log for existing errors against this port or the circuit  
pack, and attempt to diagnose the already existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
The NPE of the tested port was found to be transmitting in error. This  
causes noisy and unreliable connections.  
1. Replace the circuit pack.  
PASS  
The port is correctly using its allocated time slots.  
1. User-reported troubles on this port should be investigated by using  
other port tests and by examining the terminal adapter or the external  
wiring.  
Conference Circuit Test (#7)  
One or more Network Processing Elements (NPEs) reside on each circuit pack  
with a TDM Bus interface. (The TN464C UDS1 circuit pack has one  
SCOTCH-NPE chip instead of several NPE chips). The NPE controls port  
connectivity and gain, and it provides conferencing functions on a per-port basis.  
The Conference Circuit Test verifies that the NPE channel for the port being  
tested can correctly perform the conferencing function. The NPE is instructed to  
listen to several different tones and to conference the tones together. The  
resulting signal is then measured by a Tone Detector port. If the level of the tone  
is within a certain range, the test passes.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
WAE-PORT (Wideband Access Endpoint Port)  
3-1283  
Table 3-548. TEST #7 Conference Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1000  
System resources required to run this test are not available. The port may  
be in use on a valid call. Use the status access-endpoint <extension>  
command to determine when the port is available for testing.  
1004  
1020  
ABORT  
ABORT  
The port has been seized by a user for a valid call. Use the status  
access-endpoint <extension> command to determine when the port is  
available for testing. The port is available when it is in the in-service/idle  
state.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The test did not run due either to a previously existing error on the specific  
port or to a more general circuit pack error.  
1. Examine the Error Log for existing errors against this port or circuit  
pack, and attempt to diagnose the previously existing error.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
The NPE of the tested port did not conference the tones correctly. This  
causes noisy and unreliable connections. Although wideband calls do not  
use the conferencing feature on the NPE, this failure indicates problems  
with the circuit pack hardware.  
1. Replace the circuit pack.  
PASS  
The port can correctly conference multiple connections.  
1. User-reported troubles on this port should be investigated by using  
other port tests and by examining the terminal adapter or the external  
wiring.  
Continued on next page  
Port Audit and Update Test (#36)  
This test sends port level translation data from switch processor to the UDS1  
Interface circuit pack to ensure that the wideband access endpoint port’s  
translation is correct.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
WAE-PORT (Wideband Access Endpoint Port)  
3-1284  
Table 3-549. TEST #36 Audit and Update Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
Internal System Error.  
ABORT  
ABORT  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The port is out-of-service. If the port is busied out:  
1006  
1. Issue release access-endpoint <extension> command to put the  
port back into in-service.  
2. Retry the test command.  
If the port is not busied out:  
1. Check the error and alarm logs for WAE-PORT and UDS1-BD errors  
and alarms. Follow the recommended repair procedures.  
2000  
2100  
ABORT  
ABORT  
Response to the test request was not received within the allowable time  
period.  
Could not allocate the necessary system resources to run this test.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Internal system error.  
FAIL  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
Port translation has been updated successfully.  
PASS  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1285  
XXX-BD (Common Port Circuit Pack)  
The Common Port Circuit Pack Maintenance is a set of common tests used by all  
the circuit packs with the generic hardware that interfaces with the TDM bus.  
Circuit packs included in this category are listed on the following pages.  
MO Name (in  
Alarm Log)  
Alarm  
Level  
1
Initial Command to Run  
Full Name of MO  
2
XXX-BD  
MAJOR  
test board PCSS  
Common Port Circuit  
Pack Maintenance  
2
XXX-BD  
XXX-BD  
MINOR  
test board PCSS  
test board PCSS  
Common Port Circuit  
Pack Maintenance  
2
WARNING  
Common Port Circuit  
Pack Maintenance  
1. Where P is the port network number (1); C is the carrier designation (for example, A, B, or  
C); and SS is the address of the slot in the carrier where the circuit pack is located (for  
example, 01, 02,...etc.)  
2. Refer to the appropriate circuit pack documentation to get the correct MO name  
displayed in this field. It usually ends with BD.  
Notes:  
a. All circuit pack suffixes (B,C, D, etc.) are also supported by the XXX-BD  
(Common Port Circuit Pack) Maintenance documentation.  
b. The XXX-BD designation is also used in the SAT display in the case where  
a reset board command is issued to a circuit pack type which is in  
conflict to the actual circuit pack type administered for that slot or when a  
reset board command is issued to an empty circuit pack slot.  
When any of the Common Port Circuit Packs (except the TN754 Digital Line and  
TN758 Pooled Modem circuit packs) are physically removed from the backplane,  
no alarm is logged for approximately 11 minutes. In the case of the Digital Line  
and Pooled Modem circuit packs, approximately 21 minutes elapse before an  
alarm is logged. When a circuit pack that has been removed is alarmed, the  
alarm type is minor and is classified as an on-board alarm. The time delay  
permits maintenance activity to be performed without triggering an additional  
alarm. An alarm is logged only against a Common Port Circuit Pack on  
which ports have been administered. See the next Note.  
NOTE:  
In a heavily loaded system, the interval between the removal of a Common  
Port Circuit Pack and the logging of the alarm may be several minutes  
longer.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1286  
XXX-BD Common Circuit Packs  
The following list of circuit packs are listed by apparatus code, including circuit  
packs used in non-United States installations. .  
Table 550. XXX-BD Common Circuit Packs  
Apparatus Code  
Name  
DEFINITYAUDIX R3 System  
Type  
(TN566)  
(TN567)  
Port Assembly  
(TN2208)  
TN417  
Call Visor ASAI over the DEFINITY (LAN) Gateway R1  
Auxiliary Trunk  
Port Assembly  
Port  
TN429  
Direct Inward/Outward Dialing (DIOD) Trunk  
Speech Synthesizer  
Direct Inward Dialing Trunk  
Tie Trunk  
Port  
TN433  
Service  
Port  
TN436B  
TN437  
Port  
TN438B  
TN439  
Central Office Trunk  
Tie Trunk  
Port  
Port  
TN447  
Central Office Trunk  
Speech Synthesizer  
Tie Trunk  
Port  
TN457  
Service  
Port  
TN458  
TN459B  
TN464C/ D/E/ F  
TN465/B/C  
TN467  
Direct Inward Dialing Trunk  
DS1/E1 Interface - T1, 24 Channel - E1, 32 Channel  
Central Office Trunk  
Analog Line  
Port  
Port  
Port  
Port  
TN468B  
TN479  
Analog Line  
Port  
Analog Line  
Port  
TN497  
Tie Trunk  
Port  
TN722B  
TN725B  
TN726/B  
TN735  
Digital Signal Level 1 Tie Trunk  
Speech Synthesizer  
Data Line  
Port  
Service  
Port  
MET Line  
Port  
TN742  
Analog Line  
Port  
TN744/B/C  
TN744D  
TN746/B  
Call Classifier - Detector  
Call Classifier - Detector - Multi-Country  
Analog Line  
Service  
Service  
Port  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1287  
Table 550. XXX-BD Common Circuit Packs — Continued  
Apparatus Code  
TN747B  
Name  
Type  
Central Office Trunk  
Announcement  
Port  
TN750/B/C  
TN753  
Service  
Port  
Direct Inward Dialing Trunk  
Digital Line 4-Wire DCP  
Pooled Modem  
TN754/B  
TN758  
Port  
Port  
TN760B/C/D  
TN762B  
Tie Trunk  
Port  
Hybrid Line  
Port  
TN763B/C/D  
TN767B/C/D/E  
TN769  
Auxiliary Trunk  
Port  
DS1 Interface - T1, 24 Channel  
Analog Line  
Port  
Port  
TN797  
Analog Trunk and Line  
Processor  
Port  
TN798  
Control  
Port  
TN2135  
Analog Line  
TN2136  
Digital Line 2-Wire DCP  
Central Office Trunk  
Direct Inward Dialing Trunk  
Tie Trunk  
Port  
TN2138  
Port  
TN2139  
Port  
TN2140/B  
TN2144  
Port  
Analog Line  
Port  
TN2146  
Direct Inward Dialing Trunk  
Central Office Trunk  
Analog Line  
Port  
TN2147/C  
TN2149  
Port  
Port  
TN2180  
Analog Line  
Port  
TN2181  
Digital Line 2-wire DCP  
Tone-Clock - Tone Detector and Call Classifier  
Analog Line  
Port  
TN2182/B  
TN2183  
Control  
Port  
TN2184  
DIOD Trunk  
Port  
TN2199  
TN2224  
Central Office Trunk  
Digital Line, 24-Port, 2-Wire DCP  
Port  
Control  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1288  
Hardware Error Log Entries and Test to Clear  
Values  
Common Port Circuit Pack Maintenance Error Log Entries  
Aux  
Data  
On/Off  
Board  
Error Type  
Associated Test  
Any  
Alarm Level  
Any  
Test to Clear Value  
1
0
0
0
Any  
ON  
test board PCSS sh r 1  
1(a)  
Circuit pack  
MINOR  
removed or SAKI  
Sanity Test (#53)  
18(b)  
23(c)  
125 (d)  
257  
0
0
busyout board PCSS WARNING  
OFF  
OFF  
ON  
release board PCSS  
None  
None  
WARNING  
MINOR  
65535  
ControlChannel Test  
(#52)  
MINOR  
ON  
test board PCSS sh r 20  
257 (e)  
267 (d)  
513 (f)  
Any  
0
None  
None  
WARNING  
MINOR  
ON  
ON  
Any  
4358  
4363  
None  
test board PCSS sh  
769 (g)  
1025 (h)  
1281 (i)  
None  
NPE Audit Test (#50)  
test board PCSS l r 20  
test board PCSS r 2  
Ringing Application  
Test (#51)  
MINOR  
ON  
ON  
ON  
1538 (j)  
Any  
None  
WARNING/  
MINOR  
1793 (k)  
3840 (l)  
3999 (m)  
Neon Test (#220)  
None  
MINOR  
test board PCSS r 2  
Any  
Any  
None  
1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the  
appropriate test description and follow the recommended procedures.  
Notes:  
a. This error indicates the circuit pack totally stopped functioning or it was  
physically removed from the system. This error type is not applicable to  
ANN-BD, DETR-BD, S-SYN-BD, M/T-BD, or CLSFY-BD.  
NOTE:  
The alarm is logged approximately 11 minutes after the circuit pack  
has been removed and/or SAKI Sanity Test (#53) fails.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1289  
If the circuit pack is not in the system, insert a circuit pack (in the same  
slot as the error indicates) to resolve this error. Or, if the circuit pack is in  
the system and the red LED is on, follow the instructions for "Red (alarm)"  
in the ‘‘Control and Port Circuit Pack Status LEDs’’ section in Chapter 1,  
‘‘Maintenance for csi systems’’  
b. This error indicates the circuit pack has been busied out. Release the  
circuit pack via release board PCSS.  
c. The circuit pack has been logically administered but not physically  
installed. The alarm should clear when the circuit pact is installed.  
If the circuit pack is already installed:  
1. Run test board PCSS long and look at any test failures or error  
codes generated.  
2. If the test does not clear error 23, then execute reset board PCSS  
and run the long test again.  
3. If the reset/test does not clear error 23, replace the circuit pack.  
d. A wrong circuit pack is inserted in the slot where this circuit pack is  
logically administered. To resolve this problem, either remove the wrong  
circuit pack and insert the logically administered circuit pack OR use the  
change circuit-pack command to readminister this slot to match the  
circuit pack inserted.  
e. This error indicates transient communication problems with this circuit  
pack. This error is not service-affecting and no action is required.  
f. This error, when reported with Aux data in the range of 4352 to 4358,  
indicates that the circuit pack has reported an on-board hardware failure.  
The circuit pack continuously tests the hardware and report the results  
approximately every 10 minutes. If the hardware problem is resolved, the  
"leaky bucket" strategy should clear the alarm in approximately 30  
minutes. However, if the alarm does NOT clear in 30 minutes, the circuit  
pack should be replaced.  
g. This error can be ignored, but look for other errors on this circuit pack.  
h. This error is not service-affecting and no action is required.  
i. This error indicates that no ringing current is detected. Run Test #51,  
Ringing Application Test, and follow the procedures for Test #51. This error  
is only applicable to Analog Line circuit packs.  
j. The hyperactive circuit pack is out-of-service and may exhibit one or more  
of the following symptoms:  
1. The common circuit pack level tests such as Test #51 and/or Test  
#220 are aborting with error code 2000.  
2. The tests run on the ports of this circuit pack are returning with a  
NO-BOARD.  
3. A busyout/release of the circuit pack has no affect on test results.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1290  
4. A list configuration command shows that the circuit pack and  
ports are properly installed.  
If the XXX-BD is not a TN754 Digital Line Circuit Pack (DIG-BD), and if this  
error happens again within 15 minutes, replace the circuit pack. If the  
XXX-BD is a TN754 Digital Line Circuit Pack (DIG-BD), check the alarm  
level. If the alarm level is a WARNING, this indicates that users are  
probably causing the hyperactivity by playing with their digital stations. If  
the circuit pack is really hyperactive, this alarm is upgraded to a MINOR  
alarm within one hour. If the alarm level is a MINOR alarm, replace the  
circuit pack.  
k. This error indicates that no neon current is detected. Run Test #220, Neon  
Test, and follow the procedures for Test #220. This error is applicable only  
to TN769 and TN746 Analog Line circuit packs.  
l. This error is not service-affecting and no action is required.  
m. Error type 3999 indicates that the circuit pack sent a large number of  
control channel messages to the switch within a short period of time. If  
error type 1538 is also present, then the circuit pack was taken  
out-of-service due to hyperactivity. If error type 1538 is not present, then  
the circuit pack has not been taken out-of-service, but it has generated  
50% of the messages necessary to be considered hyperactive. This may  
be completely normal during heavy traffic periods. However, if this error  
type is logged when the circuit pack is being lightly used, it may indicate a  
problem with the circuit pack or the equipment attached to it.  
System Technician-Demanded Tests: Descriptions  
and Error Codes  
Always investigate tests in the order presented in Table 3-551 when inspecting  
errors in the system. By clearing error codes associated with the Control Channel  
Loop Around Test, for example, you may also clear errors generated from other  
tests in the testing sequence.  
Table 3-551. System Technician-Demanded Tests: XXX-BD  
Short Test  
Sequence  
Long Test  
Sequence  
Reset Board  
Sequence  
1
Order of Investigation  
NPE Audit Test (#50)  
D/ND  
ND  
X
X
X
X
Ringing Application Test (#51) (a)  
Control Channel Loop Around Test (#52)  
SAKI Sanity Test (#53)  
X
X
ND  
ND  
D
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1291  
Table 3-551. System Technician-Demanded Tests: XXX-BD — Continued  
Short Test  
Sequence  
Long Test  
Sequence  
Reset Board  
Sequence  
1
Order of Investigation  
Neon Test (#220) (b)  
D/ND  
X
X
ND  
1. D = Destructive; ND = Nondestructive  
Notes:  
a. Only applicable to Analog Line circuit packs.  
b. Only applicable to TN746 and TN769 Analog Line circuit packs.  
NPE Audit Test (#50)  
The system sends a message to the on-board microprocessor to update the  
network connectivity translation for all the Network Processing Elements (NPEs)  
on the circuit pack.  
Table 3-552. TEST #50 NPE Audit Test  
Error  
Code  
Test Result  
ABORT  
Description/ Recommendation  
none or  
2100  
System resources required for this test are not available.  
1019  
ABORT  
FAIL  
Test already in progress.  
Internal System Error.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The circuit pack’s NPEs have been updated with their translation.  
PASS  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1292  
Table 3-552. TEST #50 NPE Audit Test — Continued  
Error  
Code  
Test Result  
Description/ Recommendation  
EXTRA BD  
Certain circuit packs have limitations on how many circuit packs  
can be in the system such as the Call Classifier (TN744). The Call  
Classifier allow only 10 circuit packs in each system. All additional  
circuit packs return EXTRA-BD and should be removed.  
any  
NO BOARD  
This is normal if the test is being done when (a) the circuit pack is  
not physically in the system or (b) the system is booting up.  
Otherwise, there is some inconsistency between the physical  
configuration and the data kept in the system.  
1. Verify that the circuit pack is physically in the system.  
2. Verify that the system is not in a stage of booting up.  
3. Retry the command at 1-minute intervals for a maximum of 5  
times.  
Ringing Application Test (#51)  
This test checks the ringing application circuitry common to all ports on an  
Analog Line circuit pack.  
Table 3-553. TEST #51 Ringing Application Circuit Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1000 or  
2100  
ABORT  
ABORT  
ABORT  
Could not allocate the necessary system resources to run test.  
Could not allocate the necessary system resources to run test. The circuit  
pack is not installed. Internal System Error.  
2000  
There was no response from the board.  
1. If error type 1538 (hyperactivity) is present in the error log, follow the  
maintenance strategy that is recommended for this error type.  
2. Run the busyout board, reset board, and release busy board  
commands,and then retest.  
3. If the test still aborts, dispatch with the circuit pack.  
4. Check the off-board wiring and the terminal, and, if there are no  
problems found, replace the circuit pack.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1293  
Table 3-553. TEST #51 Ringing Application Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension. Use the status station command to determine the service state  
of the port. If the service state indicates that the port is in use, the port is  
unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1008  
ABORT  
Could not allocate a ringing circuit for one of the following reasons: all the  
ringing circuits are in use; the ringing generator is defective; ringing  
generator is not wired correctly.  
1. If the test continues to abort, look for RING-GEN error in Error Log.  
a. If there are RING-GEN errors, refer to RING-GEN Maintenance  
documentation and try to resolve any problem(s). Go to Step 2.  
b. If there are no RING-GEN errors, and the test continues to abort,  
issue the test board PCSS command on other TN742, TN769, or  
TN746 Analog circuit packs. If an ABORT with error code 1008  
occurs for this test on other circuit packs as well, the ringing  
generator may be defective or may not be wired properly. Refer to  
RING-GEN Maintenance documentation for details. If an ABORT  
with error code 1008 does NOT occur on the other ports, then all  
four ring generators are in use. Exit from this documentation.  
2. Retry the command.  
FAIL  
No ringing current is detected. The ringing application circuitry on this  
circuit pack probably is not healthy.  
1. Retry the command again.  
2. If the test continues to fail, look for RING-GEN error in Error Log.  
a. If there are RING-GEN errors, refer to the RING-GEN Maintenance  
documentation and try to resolve any problem(s).  
b. If there are no RING-GEN errors, replace the circuit pack.  
3. Retry the command again.  
PASS  
Ringing current is detected or this vintage of the Analog Line circuit pack  
does not support the Ringing Application Circuit Test. Analog Line circuit  
packs that DO NOT support Test #51 include TN742 Vintage 3 and earlier.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1294  
Table 3-553. TEST #51 Ringing Application Circuit Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
any  
NO  
BOARD  
This is normal if the test is being done when (a) the circuit pack is not  
physically in the system or (b) the system is booting up. Otherwise, there is  
some inconsistency between the physical configuration and the data kept  
in the system.  
1. Verify that the circuit pack is physically in the system. Verify that the  
system is not in a stage of booting up. Retry the command at 1-minute  
intervals for a maximum of 5 times.  
Control Channel Loop Around Test (#52)  
This test queries the circuit pack for its circuit pack code and vintage and verifies  
its records.  
Table 3-554. TEST #52 Control Channel Loop Around Test  
Error  
Code  
Test Result  
Description/ Recommendation  
none or  
2100  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
FAIL  
The test failed because the circuit pack failed to return the circuit pack  
code or vintage.  
1. Retry the command for a maximum of 5 times.  
2. If the test still fails, issue the busyout board, reset board, and  
release busy board commands, and then retest.  
3. If the problem continues, replace the circuit pack.  
4. Run the test again.  
PASS  
Communication with this circuit pack is successful.  
any  
NO BOARD This is normal if the test is being done when (a) the circuit pack is not  
physically in the system or (b) the system is booting up. Otherwise, there  
is some inconsistency between the physical configuration and the data  
kept in the system.  
1. Verify that the circuit pack is physically in the system.  
2. Verify that the system is not in a stage of booting up.  
3. ) Retry the command at 1-minute intervals for a maximum of 5 times.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1295  
SAKI Sanity Test (#53)  
This test is destructive.  
This test resets the circuit pack and is executed as part of the long test sequence  
only for the Tone-Clock circuit pack and DS1 interface circuit packs. All other  
common circuit packs can be reset with the reset board PCSS command.  
Table 3-555. TEST #53 SAKI Sanity Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
none  
ABORT  
ABORT  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1005  
Wrong circuit pack configuration to run this test. This error applies only to  
DS1 interface circuit packs. It means the DS1 interface circuit pack is  
providing timing for the system and, therefore, it cannot be reset without  
major system disruptions.  
1. If the circuit pack needs to be reset, set synchronization to another  
DS1 interface circuit pack or the Tone-Clock circuit pack and try again.  
Refer to SYNC (Synchronization) Maintenance documentation.  
1015  
2100  
ABORT  
ABORT  
Port is not out-of-service.  
1. Busy out the circuit pack.  
2. Execute command again.  
System resources required for this test are not available.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
The circuit pack failed to reset.  
1
2
FAIL  
FAIL  
The circuit pack failed to restart.  
1. Execute command again.  
2. If the problem persists, replace the circuit pack.  
The circuit pack initializes correctly.  
1. Run the Short Test Sequence.  
PASS  
any  
NO  
BOARD  
This is normal if the test is being done when (a) the circuit pack is not  
physically in the system or (b) the system is booting up. Otherwise, there is  
some inconsistency between the physical configuration and the data kept  
in the system.  
1. Verify that the circuit pack is physically in the system.  
2. Verify that the system is not in a stage of booting up.  
3. Retry the command at 1-minute intervals for a maximum of 5 times.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1296  
Neon Test (#220)  
This test checks the voltage required to light the neon lamp on an analog  
terminal. A relay connects a 120V DC source from the backplane of the circuit  
pack onto the voltage bus, and another relay connects a 2K shunt from the bus to  
ground. Current in the line is then monitored to determine if the voltage is  
present.  
The neon test runs only for TN746 and TN769 Analog circuit packs. If the circuit  
pack is not a TN746 or TN769, the test returns PASS, but there is no testing done  
to the circuit pack.  
Table 3-556. TEST #220 Neon Test  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1004  
ABORT  
The port was seized by a valid call during the test. The test has been  
aborted. Use the display port PCSSpp command to determine the station  
extension. Use the status station command to determine the service state  
of the port. If the service state indicates that the port is in use, then the port  
is unavailable for certain tests. You must wait until the port is idle before  
retesting.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
1008  
ABORT  
Could not allocate a ringing circuit. Either all the ringing circuits are in use,  
or the ringing generator is defective or is not wired correctly.  
1. Retry the command at 1-minute intervals a maximum of 5 times.  
2. If the test continues to abort, look for RING-GEN errors in the Error  
Log. If an ABORT 1008 occurs for this test on other circuit packs as  
well, then the ringing generator may be defective or is not wired  
correctly. If it doesn’t occur on port test 48 for ANL-16-L, then all four  
ring phases are in use.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1297  
Table 3-556. TEST #220 Neon Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
1018  
ABORT  
There are not any translated ports on the circuit pack, or if there are ports,  
then none are administered to have "neon."  
1. Verify that there are ports administered on the circuit pack. If no ports  
are administered, no further action is required.  
2. Verify that you have neon sets connected (Lucent sets that may be  
neon sets are 500 and 2500 series, also some non-Lucent may also  
be neon sets). If no neon sets are connected to the circuit pack, the  
test continues to abort, but no further action is required.  
3. If there are no neon sets connected to the circuit pack, at least one  
port needs to be translated with neon. To check if a port is translated  
with neon, use the display port PCSSpp command to determine the  
station extension of any station on this circuit pack. Use the display  
station <extension> to determine if the port is administered with  
neon. The field "Message Waiting Indicator:" must be set to "neon" for  
at least one of the administered ports. If this field is not administered to  
"neon" the test continues to abort. This is acceptable because not all  
stations have neon lamps on their analog terminals. If none of the  
terminals have neon lamps, the the test continues to abort, but no  
further action is required.  
4. Retry the command again.  
5. Retry the command at 1-minute intervals a maximum of 5 times.  
6. If the test continues to abort, look for RING-GEN errors in the Error  
Log. If an ABORT 1008 occurs for this test on other circuit packs as  
well, then the ringing generator may be defective. If it does not occur  
on port test 48 for ANL-16-L, all four ring phases are in use.  
7. Retry the command again.  
2000  
2100  
ABORT  
ABORT  
ABORT  
Response to the request was not received within the allowable time period.  
Could not allocate the necessary system resources to run this test.  
Could not allocate the necessary system resources to run this test. Internal  
System Error.  
1. If Error Type 1538 is present in the Error Log, follow the recommended  
maintenance strategy.  
FAIL  
The test failed because no neon current was detected.  
1. Look for the failure of test 220. If test 220 fails, replace the 650A power  
supply.  
2. Retry the command again.  
Continued on next page  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Maintenance Objects  
3
XXX-BD (Common Port Circuit Pack)  
3-1298  
Table 3-556. TEST #220 Neon Test — Continued  
Error  
Code  
Test  
Result  
Description/ Recommendation  
PASS  
This circuit pack is a TN746 or TN769 Analog Line circuit pack and the  
neon current is detected. This test also returns PASS for circuit packs that  
are not TN746 or TN769 circuit packs, but the test is not run on the circuit  
pack and the results of this test can be ignored.  
any  
NO  
BOARD  
This is normal if the test is being done when (a) the circuit pack is not  
physically in the system or (b) the system is booting up. Otherwise, there is  
some inconsistency between the physical configuration and the data kept  
in the system.  
1. Verify that the circuit pack is physically in the system.  
2. Verify that the system is not in a stage of booting up.  
3. Retry the command at 1-minute intervals for a maximum of 5 times.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Index  
IN-1  
Index  
Numerics  
120A ICSU, 1-76  
A
ACA, see Automatic Circuit Assurance  
Access Security Gateway, 2-24  
administration  
circuit packs, 3-1172  
logins, 1-26, 1-32  
ADX12-BD, 3-258  
ADX8D-BD, 3-258  
ADX8D-RS, 3-259  
air filters, 1-18  
alarm logs, 1-14  
Alarm Origination to OSS Numbers, 2-27  
alarms  
classifications, 1-15  
error reporting, 1-15  
logs, 1-14  
major, 1-15  
minor, 1-15  
off-board, 1-15  
on-board, 1-15  
Terminal Alarm Notification, 1-85  
warning, 1-15  
Analog Tie Trunk Back-to-Back testing, 1-56  
AN-LN-PT, 3-72  
ATM (Asynchronous Transfer Mode)  
B-channel, 3-209  
circuit emulation service (CES), 3-209  
D-channel, 3-209  
signaling group, 3-209  
trunking, 3-209  
attendant consoles, LEDs, 1-87  
AUDIX circuit pack (ADXDP-BD), 3-9  
AUDIX digital port (ADXDP-PT), 3-10  
Automatic Circuit Assurance (ACA), 1-47  
AXA12-BD, 3-258  
AXA12-RS, 3-259  
AXD12-RS, 3-259  
B
background tests, 1-15  
fixed interval, 1-15  
scheduled, 1-15  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Index  
IN-2  
bit rate  
setting, 1-101  
Busy Verification of Terminals and Trunks, 1-48  
C
cabinets  
configurations, 1-18  
carrier lead appearances  
110 cross-connect field, 1-58  
Centre-Vu Remote IP Agent, 1-2, 3-490  
channel associated signaling (CAS), 3-1163  
circuit packs  
administration, 3-1172  
processor, 1-86  
status LEDs, 1-89  
TN2242, 3-1163  
TN2305, 3-209  
TN2306, 3-209  
TN464, 3-548  
TN464F, 3-1163  
TN722, 3-548  
TN767, 3-548  
TN768, 3-1079  
TN780, 3-1079  
TN790 Processor, 1-13  
TN802 MAPD, 3-764  
universal DS1 (UDS1) interface, 3-548, 3-764, 3-794, 3-1163  
CLAN-BD, 3-347  
clocks, system, 3-1079  
cold starts  
with translations loading, 1-22  
without translations loading, 1-22  
Command Permissions Categories form, 1-33  
commands  
categories, 1-27  
configurations  
cabinets, 1-18  
control and port circuit pack status LEDs, 1-88  
control circuit packs  
replacing, 1-40  
reseating, 1-40  
unseating, 1-39  
Control LAN Circuit Pack, 3-347  
D
Data Line Circuit Pack, 3-622  
data-link layer, OSI, 1-16  
DC power  
signaling leads, 1-98  
demand tests, 1-16  
diagnostic tests, 1-21  
DIG-IP-STN, 3-490  
Digital IP Station, 3-490  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Index  
IN-3  
display alarms command, 1-38  
DS0 channels, 3-1169  
DS1  
CO trunk (CO-DS1), 3-523  
interface circuit packs, 3-548, 3-764, 3-794, 3-1163  
option jumpers, 3-1172  
signaling, 3-548  
trunks, 3-764, 3-794, 3-1163  
DS1 Interface Circuit Pack, 3-548  
DS1 loopback, 1-71  
DS1 span, 1-72, 1-73  
DS1 span test, 1-73  
DS1 span, T1, 1-71  
DS1-BD, 3-548  
DT-LN-BD, 3-622  
Duplication-Related System Parameters form, 2-78  
E
E&M mode tests, 1-56  
electromagnetic compatibility standards, xix  
enhanced integrated CSU, 3-1170  
error  
control, 1-16  
error logs, 1-14  
error reporting, 1-15  
errors  
logs, 1-14  
reporting, 1-15  
European Union Standards, xx  
F
Facility Test Calls, 1-49  
System Tone Test Call, 1-53  
Time Slot Test Call, 1-51  
Touch-Tone (DTMF) Receiver Test Call, 1-50  
Trunk Test Call, 1-49  
First OSS Telephone Number, 2-26, 2-81  
flow control, 1-16  
Forced Password Aging, 1-26  
H
H.323 B-Channel, 3-669  
H.323 IP Station, 3-677  
H.323 Signaling Group, 3-671  
H323-BCH, 3-669  
H323-SGRP, 3-671  
help  
terminal set-up commands, 2-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Index  
IN-4  
I
impedance, setting, 1-101  
Incomplete Command Time-out, 3-330, 3-546  
Internet Telephony Server (ITS-E), 3-764  
IP Softphone, 1-2, 3-490  
ISDN-PRI  
DS0 channels, 3-764, 3-794, 3-1163  
troubleshooting, 1-63  
troubleshooting test call problems, 1-67  
J
Japan Radio Corporation external converter, 3-1164, 3-1165  
L
LEDs  
alarms, 1-86  
attendant consoles, 1-87  
control and port circuit pack status, 1-88  
definition, 1-84  
indicators on maintenance/processor circuit packs, 1-86  
maintenance circuit pack, 1-86  
processor circuit pack, 1-86  
LGATE-BD, 3-260  
list ip-route, 2-114  
log in to system, 1-26  
logging in, 1-26  
Login Administration screen, 1-32  
login IDs, 1-26  
login procedure, 1-26  
logins  
administering command permissions, 1-33  
administration, 1-32  
changing attributes, 1-33  
removing, 1-30  
security, 1-26  
testing, 1-30  
logoff screen, 1-29  
loopback jack, 1-71  
M
Maintenance, 3-941  
maintenance  
background testing, 1-15  
preventative procedures, 1-18  
subsystem, 1-1  
system’s overall functions, 1-1  
testing, 1-15  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Index  
IN-5  
maintenance object repair procedures  
BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port), 3-268  
BRI-SET, ASAI-ADJ, BRI-DAT, 3-290  
DID-BD (Direct Inward Dial Trunk Circuit Pack), 3-460  
DID-DS1 (DS1 DID Trunk), 3-461  
DID-TRK (DID Trunk), 3-472  
DIG-BD (Digital Line Circuit Pack), 3-489  
DIG-LINE (Digital Line), 3-498  
DIOD-TRK (DIOD Trunk) [G1.2SE], 3-535  
DTMR-PT [Dual Tone Multifrequency Port (TTR)], 3-623  
RING-GEN (Analog Ring Generator), 3-976  
S-SYN-BD (Speech Synthesis Circuit Pack), 3-980  
S-SYN-PT (Speech Synthesis Port), 3-981  
TIE-TRK (Tie Trunk), 3-1106  
TONE-BD (Tone-Clock Circuit Pack), 3-1128  
TONE-PT (Tone Generator), 3-1139  
TSC-ADM (Administered Temporary Signaling Connections) [G3iV1.1-286, G3iV2-386], 3-1153  
TTR-LEV (TTR Level), 3-1159  
XXX-BD (Common Port Circuit Pack), 3-1285  
maintenance objects (MOs)  
definition, 1-14  
Maintenance/Test Circuit Pack Query Test (#572), 3-890  
MAP Manager I Loop Around Test (#228), 3-943  
MAPD, 1-4, 3-806  
measurements  
security, 1-26  
Media Processor, 1-2, 1-4, 3-671, 3-794, 3-806  
MEDPRO, 3-794  
MedPro, 1-2, 3-671  
Memory Board Check Test (#631), 3-943  
memory cards  
errors, 1-46  
failures, 1-46  
Memory Error Detection Test (#87), 3-943  
Memory Functional Test (#332), 3-943  
Modem Connection, 2-34, 2-86  
MTP Analog Loop Around Test (#103), 3-943  
MTP Aux Loop Around Test (#229), 3-943  
MTP Dual Port Ram Test (#104), 3-943  
MTP Outpulse Relay Test (#102), 3-943  
MTP Reset Test (#101), 3-943  
MTP Sanity Handshake Test (#106), 3-943  
N
neon voltage (ring ping), 1-24  
NetMeeting, 1-2, 3-677  
network interface, 1-76  
O
Open System Interconnect model, 1-16  
data-link layer, 1-16  
physical layer, 1-16  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Index  
IN-6  
option jumpers  
TN464, 3-1172  
universal DS1 (UDS1) interface circuit packs, 3-1172  
OSI, see Open System Interconnect model  
OSS Numbers field, 2-25  
P
Packet Bus, 3-885  
Packet Circuit Pack Audit Test (#573), 3-893  
Packet Interface, 3-894  
password, 1-26  
Password Expiration screen, 1-28  
passwords  
security, 1-26  
pcANYWHERE, 3-770  
physical  
layer, OSI, 1-16  
pinout  
H600-513 cable, 3-1166  
PKT-BUS, 3-885  
PKT-BUS Error Log Entries, 3-888  
PKT-INT, 3-894  
PNC duplication (PNC-DUP), 3-198  
port network connectivity (PNC), 2-77  
power  
controls, 1-18  
options available, 1-18  
removing, 1-40  
restoring, 1-42  
preventative maintenance  
procedures, 1-18  
PRI endpoint problems  
troubleshooting, 1-65  
Processor Non-maskable Interrupt Test (#82), 3-943  
Processor ROM Checksum Test (#80), 3-943  
Processor Sanity Timer Test (#83), 3-943  
Processor Software Initiated Interrupt Test (#77), 3-943  
PROCR, 3-941  
Proshare, 1-2, 3-677  
PSTN fallback, 3-768  
R
Read All Memory Test (#85), 3-943  
reboots, 1-20  
reset system 1, 1-22  
reset system 2, 1-22  
reset system 3, 1-22  
reset system 4, 1-23  
reset system 5, 1-24  
reset translation-id, 2-199  
ring ping, 1-24  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Index  
IN-7  
S
safety precautions, xviii  
Save Announcements screen, 1-45  
Save Translation screen, 1-45  
Second OSS Telephone Number, 2-26, 2-81  
security  
logins, 1-26  
measurements, 1-26  
passwords, 1-26  
setting  
bit rate, 1-101  
line impedance, 1-101  
signaling leads, DC power, 1-98  
simplex mode tests, 1-61  
SPE-down mode, 1-38  
switch processing elements (SPE), 2-77  
switch settings  
TN464 circuit pack, 1-101  
TN760 tie trunk, 1-98  
synchronization, 1-16  
synchronization (SYNC), 3-220  
system features  
troubleshooting system resources, 1-47  
system reboots, 1-23, 1-24  
system resets  
reasons for, 1-21  
System Tone Test Call, 1-53  
T
T1 DS1 span, 1-71  
TDM bus  
clocks, 3-1079  
TDM bus clock (TDM-CLK), 3-1079  
terminal  
type, 1-26  
Terminal Alarm Notification  
alarms, 1-85  
description, 1-85  
Terminating Trunk Transmission (TTT)  
tests, 1-63  
testing  
background, 1-15  
demand, 1-16  
maintenance, 1-15  
system technician-demanded, 3-241, 3-798, 3-808, 3-1184  
tests  
analog tie trunk back-to-back, 1-56  
E&M mode, 1-56  
logins, 1-30  
simplex mode, 1-61  
Terminating Trunk Transmission (TTT), 1-63  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Index  
IN-8  
tests and audits  
#11 Digital Line Electronic Power Feed Test, 3-515  
#1201 Digital Terminal Remote Loop Around Test, 3-510  
#1209 Board Loopback Test, 3-593  
#1209 DS1 Board Loopback Test, 3-593, 3-1228  
#1210 CSU Equipment Loopback Test, 3-596, 3-597, 3-1231  
#1211 CSU Repeater Loopback Test, 3-600, 3-601, 3-1234  
#1212 CPE Loopback Jack Test, 3-604, 3-1238  
#1213 Far CSU Loopback Test, 3-608, 3-1242  
#1214 One-Way Span Test, 3-613, 3-1247  
#1215 Inject Single Bit Error Test, 3-616, 3-1250  
#1216 End Loopback/Span Test, 3-618, 3-1252  
#122 Cabinet Temperature Query Test [Non-Variable Speed Fans], 3-321  
#1227 ICSU Status LEDs Test, 3-621, 3-1255  
#13 Voice and Control Channel Local Loop Test, 3-517  
#135 Internal Loop Around Test, 3-563, 3-1190  
#138 Loss of Signal Alarm Inquiry Test, 3-565, 3-567, 3-1194  
#139 Blue Alarm Inquiry Test, 3-574, 3-1202  
#139 Red Alarm Inquiry Test, 3-577  
#140 Red Alarm Inquiry Test, 3-576, 3-1205  
#140AY Loop Around Test, 3-104  
#141 Yellow Alarm Inquiry Test, 3-579, 3-580, 3-1209  
#142 Major Alarm Inquiry Test, 3-583, 3-1214  
#143 Minor Alarm Inquiry Test, 3-585, 3-1217  
#144 Slip Alarm Inquiry Test, 3-587, 3-1050, 3-1220  
#145 Misframe Alarm Inquiry Test, 3-589, 3-590, 3-1223  
#146 Translation Update Test, 3-592, 3-793, 3-801, 3-1226  
#148 TDM Bus Clock Circuit Status Inquiry Test, 3-1085  
#150 TDM Bus Clock PPM Inquiry Test, 3-1086  
#151 TDM Bus Clock Parameter Update Test, 3-1088  
#16 DIG-LINE Station Lamp Updates Test, 3-496, 3-519  
#161 Loop Around Test, 3-275, 3-1039  
#17 Station (Digital) Audits Test, 3-497, 3-521  
#205 Channel Administration Memory Array (CAMA) Test, 3-114  
#206 Playback Speech Memory Array (PSMA) Test, 3-116  
#208 Angel-Speech Processor (SP) Handshake Test, 3-100  
#209 Announcement Checksum Test, 3-101  
#211 Super Frame Match Inquiry Test, 3-108  
#212 Clock Match Inquiry Test, 3-108  
#222 140AY Channel Sanity Inquiry Test, 3-119  
#240 Expansion Interface Local Looparound, 3-184, 3-216, 3-255  
#241 Expansion Interface 2-way Transmission Test, 3-162  
#242 Expansion Interface Lightwave Transceiver Looparound, 3-175, 3-251, 3-810  
#252 Circuit Pack Restart Test, 3-356, 3-357  
#255 Signaling Link State Check Test, 3-131  
#256 Service State Audit Test, 3-133  
#257 Call State Audit Test, 3-134  
#258 ISDN Test Call, 3-135  
#270 Clear Error Counters, 3-289, 3-1038  
#314 DS1 CO Dial Tone Seizure Test, 3-532  
#314 DS1CO Dial Tone Seizure Test, 3-385  
#316 Expansion Interface Control Channel Test, 3-168, 3-169, 3-244  
#35 Battery Feed Test, 3-58  
#36 Port Audit and Update Test, 3-383, 3-531  
#36 Station Status and Translation Audits and Updates, 3-45  
#36 Station Status and Translation Audits and Updates Test, 3-61  
#40 Tone Generator Transmission Test, 3-1142  
#417 Test Synchronization Test, 3-226  
#42 Tone Detection Verification Test, 3-368  
#46 Clock Health Inquiry Test, 3-1137  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Index  
IN-9  
tests and audits - “(continued)”  
#47 Loop Around and Conference Test, 3-64  
#48 Station Present Test, 3-47, 3-69  
#50 NPE Connection Audit Test, 3-243, 3-558, 3-786, 3-1186  
#52 Control Channel Loop Around Test, 3-560, 3-787, 3-798, 3-1187  
#52 Control Channel Loop-Around Test, 3-189, 3-356  
#53 SAKI Sanity Test, 3-561, 3-788, 3-800, 3-804, 3-805, 3-1188  
#595 LANBIC Receive Parity Error Counter Test, 3-266, 3-358, 3-1030  
#596 Receive FIFO Overflow Error Counter Test, 3-359  
#597 Invalid LAPD Frame Error Counter Test, 3-360  
#598 Packet Interface Test, 3-361  
#599 Packet Gateway Switched Port Loop-Around Test, 3-932  
#6 NPE Crosstalk Test, 3-377, 3-528  
#600 Congestion Query Test, 3-362  
#601Link Status Test, 3-364, 3-939  
#610 Packet Gateway Port Local Loop-Around Test, 3-648, 3-649, 3-934  
#613 Level 1 State Inquiry Test, 3-651, 3-653, 3-673, 3-676, 3-938  
#618 BRI Port Local LAN Loop Around, 3-277, 3-1041  
#619 BRI Port Local TDM Loop Around, 3-279, 3-1042  
#620 Electronic Power Feed Restoral, 3-282  
#621 Level 1 Status Inquiry, 3-283, 3-1046  
#622 Electronic Power Feed Inquiry, 3-286  
#624 Layer 1 Transmission Error Counter Test, 3-287  
#625 Receive FIFO Overflow Error Counter Test, 3-288, 3-1044, 3-1045  
#626 Signaling Link Status Test, 3-303  
#627 BRI Remote Loop Back, 3-306  
#628 BRI XID, 3-309  
#629 BRI Layer 3 Query, 3-311, 3-1048  
#630 BRI Set Audits, 3-314  
#637 Remote Layer 3 Query, 3-218, 3-674, 3-802  
#643 Signaling Link Board Check, 3-141  
#7 Conference Circuit Test, 3-41, 3-380, 3-530  
#844-848 Transmission Test, 3-411, 3-1124  
#884 Memory Checksum Test, 3-710, 3-905  
#885 Private Loop Around Tests, 3-907  
#886 Maintenance Loop Around Test, 3-909  
#887 Read and Clear Board Counters, 3-911  
#9 Digital Line NPE Crosstalk Test, 3-513  
#976 Session Status Query Test, 3-494, 3-675, 3-680, 3-682, 3-802, 3-935  
#985 System Link Status, 3-1014  
Text Checksum Test (#86), 3-943  
tie trunk  
circuit pack option settings, 1-98  
Time Slot Test Call, 1-51  
TN1655 circuit packs, 3-170  
TN2182 circuit packs  
time division multiplex (TDM) bus clocks, 3-1079  
TN2242, 3-1163  
TN2793B, 3-72  
TN464 circuit pack  
option settings, 1-101  
TN464 circuit packs  
DS1 interface, 3-548, 3-764, 3-794, 3-1163  
option jumpers, 3-1172  
trunks, 3-1169  
TN464C, 3-548  
TN722 circuit packs, 3-548  
TN760 circuit pack  
option settings, 1-98  
TN767 circuit packs, 3-548  
Download from Www.Somanuals.com. All Manuals Search And Download.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi 555-233-119  
Issue 1  
April 2000  
Index  
IN-10  
TN768 circuit packs  
time division multiplex (TDM) bus clocks, 3-1079  
TN780 circuit packs  
time division multiplex (TDM) bus clocks, 3-1079  
TN786B, 3-941  
TN790 Processor, 1-13  
TN793B, 3-72  
TN797, 3-72, 3-1152  
TN798, 3-894  
TN799, 3-347  
TN799B, 1-5, 2-388  
TN802B, 1-2, 1-3, 1-4, 1-5, 2-388, 3-671, 3-794, 3-806  
tone-clock circuit packs  
time division multiplex (TDM) bus clocks, 3-1079  
Touch-Tone (DTMF) Receiver Test Call, 1-50  
traceroute, 2-388  
TRANS-ID  
Changing the grace period interval, 3-1150  
Processor circuit pack replacement, 3-1148  
TRANS-ID (Translation-ID), 3-1147  
transmission  
errors, 1-16  
stream, 1-16  
TR-LN-BD, 3-1152  
troubleshooting  
ISDN-PRI problems, 1-63  
ISDN-PRI test call problems, 1-67  
PRI endpoint problems, 1-65  
Trunk Group Busy/Warning Indicators to Attendant, 1-48  
Trunk Group form, 1-57  
Trunk Identification by Attendant, 1-48  
Trunk Test Call, 1-49  
trunks, DS1, 3-764, 3-794, 3-1163  
TTC privante networking (Japan), 3-1163  
TTT, see Terminating Trunk Transmission (TTT)  
U
UDS1 Interface Circuit Pack, 3-1163  
UDS1-BD, 3-1163  
universal DS1 (UDS1) interface circuit packs, 3-548, 3-764, 3-794, 3-1163, 3-1172  
W
warm starts, 1-22  
Download from Www.Somanuals.com. All Manuals Search And Download.  
We’d like your opinion.  
Lucent Technologies welcomes your feedback on this document. Your comments can be of great value  
in helping us improve our documentation.  
DEFINITY ECS Release 8.2 Maintenance for R8.2csi  
555-233-119, Issue 1, April 2000, Comcode 108678665  
1. Please rate the effectiveness of this document in the following areas:  
Excellent  
Good  
Fair  
Poor  
Ease of Finding  
Information  
Clarity  
Completeness  
Accuracy  
Organization  
Appearance  
Examples  
Illustrations  
Overall Satisfaction  
2. Please check the ways you feel we could improve this document:  
❒
❒
❒
❒
❒
❒
Improve the overview/introduction  
Improve the table of contents  
Improve the organization  
Add more figures  
❒
❒
❒
❒
❒
❒
Make it more concise  
Add more step-by-step procedures/tutorials  
Add more troubleshooting information  
Make it less technical  
Add more examples  
Add more/better quick reference aids  
Improve the index  
Add more detail  
Please add details about your concern.__________________________________________________  
_________________________________________________________________________________  
_________________________________________________________________________________  
3. What did you like most about this document?___________________________________________  
_________________________________________________________________________________  
_________________________________________________________________________________  
4. Feel free to write any comments below or on an attached sheet.____________________________  
_________________________________________________________________________________  
_________________________________________________________________________________  
If we may contact you concerning your comments, please complete the following:  
Name:_________________________________________Telephone Number: ( )_______________  
Company/Organization______________________________________Date:___________________  
Address:_________________________________________________________________________  
When you have completed this form, please fax to (303) 538-1741. Thank you.  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Download from Www.Somanuals.com. All Manuals Search And Download.  

Laarsen Associates Water Heater IW User Manual
LOREX Technology Switch SG6616 User Manual
LST Smoke Alarm M210E User Manual
Mace DVR DVR0404RW User Manual
Mackie Musical Instrument CR1604 User Manual
Magic Chef Oven MCSPZO12ST User Manual
Makita Grinder BGA402 User Manual
Marmitek Marine Radio um7206 User Manual
Maytag Dishwasher W10199658A User Manual
McCulloch Lawn Mower M16538H User Manual