Avaya Communication Manager Alarms Events and Logs Reference R10.2.x Dec2023

Avaya Aura® Communication Manager
Alarms, Events, and Logs Reference
Release 10.2.x
Issue 1
December 2023
© 2017-2023, Avaya LLC Virtualization
All Rights Reserved. The following applies if the product is deployed on a virtual machine.
Notice Each product has its own ordering code and license types. Unless
otherwise stated, each Instance of a product must be separately
While reasonable efforts have been made to ensure that the licensed and ordered. For example, if the end user customer or
information in this document is complete and accurate at the time Avaya Channel Partner would like to install two Instances of the
of printing, Avaya assumes no liability for any errors. Avaya reserves same type of products, then two products of that type must be
the right to make changes and corrections to the information in this ordered.
document without the obligation to notify any person or organization
of such changes. Third Party Components
Documentation disclaimer The following applies only if the H.264 (AVC) codec is distributed
with the product. THIS PRODUCT IS LICENSED UNDER THE AVC
“Documentation” means information published in varying media PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
which may include product information, subscription or service CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE
descriptions, operating instructions and performance specifications REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH
that are generally made available to users of products. THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC
Documentation does not include marketing materials. Avaya shall VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
not be responsible for any modifications, additions, or deletions PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
to the original published version of Documentation unless such PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE
modifications, additions, or deletions were performed by or on the IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
express behalf of Avaya. End user agrees to indemnify and hold ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA,
harmless Avaya, Avaya's agents, servants and employees against L.L.C. SEE HTTP://WWW.MPEGLA.COM.
all claims, lawsuits, demands and judgments arising out of, or in
connection with, subsequent modifications, additions or deletions to Service Provider
this documentation, to the extent made by End user. WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
Link disclaimer PARTNER IS HOSTING ANY PRODUCTS THAT USE OR
EMBED THE H.264 CODEC OR H.265 CODEC, THE AVAYA
Avaya is not responsible for the contents or reliability of any linked CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE
websites referenced within this site or Documentation provided by AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND
Avaya. Avaya is not responsible for the accuracy of any information, ALL RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC)
statement or content provided on these sites and does not CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO
necessarily endorse the products, services, or information described LICENSE FOR THE PERSONAL USE OF A CONSUMER
or offered within them. Avaya does not guarantee that these links will OR OTHER USES IN WHICH IT DOES NOT RECEIVE
work all the time and has no control over the availability of the linked REMUNERATION TO: (i) ENCODE VIDEO IN COMPLIANCE WITH
pages. THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC
Warranty VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
Avaya provides a limited warranty on Avaya hardware and software. PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE
Please refer to your agreement with Avaya to establish the terms of IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
the limited warranty. In addition, Avaya’s standard warranty language ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC)
as well as information regarding support for this product while under CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://
warranty is available to Avaya customers and other parties through WWW.MPEGLA.COM.
the Avaya Support website: https://support.avaya.com/helpcenter/
getGenericDetails?detailId=C20091120112456651010 under the link Compliance with Laws
“Warranty & Product Lifecycle” or such successor site as designated You acknowledge and agree that it is Your responsibility to comply
by Avaya. Please note that if the product(s) was purchased from an with any applicable laws and regulations, including, but not limited
authorized Avaya channel partner outside of the United States and to laws and regulations related to call recording, data privacy,
Canada, the warranty is provided by said Avaya Channel Partner and intellectual property, trade secret, fraud, and music performance
not by Avaya. rights, in the country or territory where the Avaya product is used.
“Hosted Service” means an Avaya hosted service subscription that Preventing Toll Fraud
You acquire from either Avaya or an authorized Avaya Channel
Partner (as applicable) and which is described further in Hosted SAS “Toll Fraud” is the unauthorized use of your telecommunications
or other service description documentation regarding the applicable system by an unauthorized party (for example, a person who is not a
hosted service. If You purchase a Hosted Service subscription, corporate employee, agent, subcontractor, or is not working on your
the foregoing limited warranty may not apply but You may be company's behalf). Be aware that there can be a risk of Toll Fraud
entitled to support services in connection with the Hosted Service associated with your system and that, if Toll Fraud occurs, it can
as described further in your service description documents for the result in substantial additional charges for your telecommunications
applicable Hosted Service. Contact Avaya or Avaya Channel Partner services.
(as applicable) for more information. Avaya Toll Fraud intervention
Copyright If You suspect that You are being victimized by Toll Fraud and You
Except where expressly stated otherwise, no use should be made need technical assistance or support, please contact your Avaya
of materials on this site, the Documentation, Software, Hosted Sales Representative.
Service, or hardware provided by Avaya. All content on this site, the Security Vulnerabilities
documentation, Hosted Service, and the product provided by Avaya
including the selection, arrangement and design of the content is Information about Avaya’s security support policies can be
owned either by Avaya or its licensors and is protected by copyright found in the Security Policies and Support section of https://
and other intellectual property laws including the sui generis rights support.avaya.com/security.
relating to the protection of databases. You may not modify, copy, Suspected Avaya product security vulnerabilities are handled
reproduce, republish, upload, post, transmit or distribute in any way per the Avaya Product Security Support Flow (https://
any content, in whole or in part, including any code and software support.avaya.com/css/P8/documents/100161515).
unless expressly authorized by Avaya. Unauthorized reproduction,
transmission, dissemination, storage, or use without the express Downloading Documentation
written consent of Avaya can be a criminal, as well as a civil offense
For the most current versions of Documentation, see the Avaya
under the applicable law.
Support website: https://support.avaya.com, or such successor site
as designated by Avaya.
Contact Avaya Support
See the Avaya Support website: https://support.avaya.com for
Product or Cloud Service notices and articles, or to report a
problem with your Avaya Product or Cloud Service. For a list of
support telephone numbers and contact addresses, go to the Avaya
Support website: https://support.avaya.com (or such successor site
as designated by Avaya), scroll to the bottom of the page, and select
Contact Avaya Support.
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation, Hosted Service(s), and product(s) provided
by Avaya are the registered or unregistered Marks of Avaya, its
affiliates, its licensors, its suppliers, or other third parties. Users
are not permitted to use such Marks without prior written consent
from Avaya or such third party which may own the Mark. Nothing
contained in this site, the Documentation, Hosted Service(s) and
product(s) should be construed as granting, by implication, estoppel,
or otherwise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya LLC.
All non-Avaya trademarks are the property of their respective owners.
Contents
Chapter 1: Introduction.......................................................................................................... 16
Purpose................................................................................................................................ 16
Discontinued support for IP Server Interface (TN2312, commonly known as “IPSI”).................... 17
Chapter 2: Server Alarms....................................................................................................... 18
Server maintenance.............................................................................................................. 19
Alarm classifications.............................................................................................................. 19
Alarm logs............................................................................................................................ 19
Alarms in Linux servers.......................................................................................................... 20
Setting up external notification for events................................................................................ 20
Displaying alarms.................................................................................................................. 21
Chapter 3: Linux Server Alarm Types................................................................................... 22
ARB (Arbiter)........................................................................................................................ 22
ARB alarms.................................................................................................................... 22
ARB Event ID 3............................................................................................................... 23
ARB Event ID 7............................................................................................................... 23
ARB Event ID 8............................................................................................................... 24
ARB Event ID 9............................................................................................................... 25
ARB Event ID 11............................................................................................................. 26
ARB Event ID 12............................................................................................................. 27
ARB Event ID 13............................................................................................................. 28
ARB Event ID 14............................................................................................................. 28
Chapter 4: Verifying the server status.................................................................................. 30
Verifying the server status using the Web interface.................................................................. 30
Verifying the server status using the command line interface..................................................... 30
String pairs of ARB Event # 9................................................................................................. 30
BKP (Backup)....................................................................................................................... 31
BKP Event ID 10............................................................................................................. 31
CMG (Common Media Gateway)............................................................................................ 31
DUP (Duplication Manager).................................................................................................... 31
DUP alarms.................................................................................................................... 32
DUP Event ID 2............................................................................................................... 32
DUP Event ID 6............................................................................................................... 33
Survivable core server........................................................................................................... 33
Survivable core server Event ID 5..................................................................................... 33
FSY (File Synchronization)..................................................................................................... 34
FSY Event ID 1 - 999....................................................................................................... 35
December 2023 Avaya Aura® Communication Manager Alarms, Events, and Logs Reference 4
Comments on this document?
FSY Event ID 1000 - 1999............................................................................................... 36
GW_ENV (Gateway Environment).......................................................................................... 36
GW_ENV alarms............................................................................................................. 37
GW_ENV Event ID 1....................................................................................................... 37
GW_ENV Event ID 2....................................................................................................... 37
GW_ENV Event ID 3....................................................................................................... 38
GW_ENV Event ID 4....................................................................................................... 38
GW_ENV Event ID 5....................................................................................................... 38
GW_ENV Event ID 6....................................................................................................... 38
GW_ENV Event ID 7....................................................................................................... 38
GW_ENV Event ID 8....................................................................................................... 38
GW_ENV Event ID 9....................................................................................................... 38
GW_ENV Event ID 10..................................................................................................... 39
_LX (Linux)........................................................................................................................... 39
LX Event ID 3.................................................................................................................. 39
LX Event ID 4.................................................................................................................. 39
LX Event ID 5.................................................................................................................. 40
LX Event ID 6.................................................................................................................. 40
LX Event ID 7.................................................................................................................. 40
LX Event ID 10................................................................................................................ 40
LX Event ID 11................................................................................................................ 41
LX Event ID 50................................................................................................................ 41
Login alarms......................................................................................................................... 41
Login Event ID 1.............................................................................................................. 42
Login Event ID 2.............................................................................................................. 42
Login Event ID 3.............................................................................................................. 42
Login Event ID 5.............................................................................................................. 42
Login Event ID 6.............................................................................................................. 43
Login Event ID 7.............................................................................................................. 43
Login Event ID 8.............................................................................................................. 43
Login Event IDs 10, 11, 12, and 13................................................................................... 43
S8300 Servers login alarms................................................................................................... 43
Event ID 1....................................................................................................................... 44
Event ID 2....................................................................................................................... 44
Event ID 3....................................................................................................................... 44
Event ID 4....................................................................................................................... 44
Event ID 5....................................................................................................................... 45
_PE (Processor Ethernet) alarms............................................................................................ 45
_PE 1 Minor alarm: PE Health Check device is not responding........................................... 45
_PE 2 Minor alarm: PE on the other server is not responding.............................................. 46
_PE 3 Major alarm: Processor Ethernet service is down..................................................... 46
_PE 4 Minor alarm: PE Priority configuration mismatch between servers............................. 47
SME (Server Maintenance Engine)......................................................................................... 47
SME Event ID 1.............................................................................................................. 48
SME Event ID 2.............................................................................................................. 49
STD (Standard SNMP Traps)................................................................................................. 49
STD Event ID 1............................................................................................................... 49
STD Event ID 2............................................................................................................... 49
STD Event ID 3 Alarm type ACT....................................................................................... 50
STD Event ID 3 Alarm type RES....................................................................................... 50
SVC_MON (Service Monitor).................................................................................................. 51
SVC MON Event ID 2...................................................................................................... 51
SVC MON Event ID 3...................................................................................................... 51
SVC MON Event ID 4...................................................................................................... 52
SVC MON Event ID 6 service rsyslog............................................................................... 52
SVC MON Event ID 5...................................................................................................... 52
SVC MON Event ID 6 service dbgserv.............................................................................. 53
SVC MON Event ID 7...................................................................................................... 53
SVC MON Event ID 8...................................................................................................... 53
Resolving SVC MON Event.................................................................................................... 54
TGP-USG (Trunk Group Usage)............................................................................................. 54
TGP-USG Event ID 1....................................................................................................... 55
TGP-USG Event ID 2....................................................................................................... 55
TM (Translation Manager)...................................................................................................... 55
TM Event ID 1................................................................................................................. 56
UPG (Upgrade)..................................................................................................................... 56
UPG Event ID 1.............................................................................................................. 56
VHEAP (Virtual Memory Heap)............................................................................................... 57
VHEAP Event ID 1.......................................................................................................... 57
VHEAP Event ID 2.......................................................................................................... 57
VHEAP Event ID 3.......................................................................................................... 58
WD (Watchdog)..................................................................................................................... 58
WD Event ID 4 S8300...................................................................................................... 59
WD Event ID 5................................................................................................................ 60
WD Event ID 6 S8300...................................................................................................... 61
WD Event ID 7 S8300...................................................................................................... 61
WD Event ID 13 ............................................................................................................. 62
WD Event ID 14.............................................................................................................. 63
WD Event ID 15 S8300E.................................................................................................. 64
WD Event ID 18 S8300E.................................................................................................. 65
WD Event ID 19 S8300.................................................................................................... 65
WD Event ID 20 S8300.................................................................................................... 66
WD Event ID 22 S8300.................................................................................................... 67
WD Event ID 23 S8300.................................................................................................... 69
WD Event ID 24 S8300.................................................................................................... 69
WD Event ID 26.............................................................................................................. 70
WD Event ID 27.............................................................................................................. 70
Chapter 5: Denial Events........................................................................................................ 71
Denial events........................................................................................................................ 71
Event type number ranges............................................................................................... 71
Event data...................................................................................................................... 72
Cause values.................................................................................................................. 77
Normal class cause values............................................................................................... 78
Resource-unavailable class cause values......................................................................... 90
Service or Option-not-available class cause values............................................................ 94
Service or Option-not-implemented class cause values.................................................... 100
Invalid-message class cause values............................................................................... 103
Protocol-error class cause values................................................................................... 107
Inter-working class cause values..................................................................................... 117
Denial event tables........................................................................................................ 118
Chapter 6: Maintenance Object Repair Procedures.......................................................... 291
Communication Manager Maintenance Object Repair Procedures.......................................... 291
Gateway Subsystems.................................................................................................... 292
Gateway MOs maintained by Communication Manager.................................................... 292
MO groupings by Media Module type.................................................................................... 293
Commands to view Communication Manager alarms............................................................. 294
Command Syntax................................................................................................................ 294
Alarm levels........................................................................................................................ 295
Abort Code 1412................................................................................................................. 295
Escalation Procedure........................................................................................................... 295
ABRI-POR (ASAI ISDN-BRI Port)......................................................................................... 296
ADJ-IP (ASAI Adjunct TCP/IP Link)...................................................................................... 296
ADJ-IP error log entries................................................................................................. 296
ADJ-IP demand test descriptions and error codes............................................................ 297
ADM-CONN (Administered Connection)................................................................................ 297
ADM-CONN error log entries.......................................................................................... 298
AESV-LNK (AE Services Link).............................................................................................. 299
AESV-LNK error log entries and recommended actions.................................................... 300
AESV-LNK demand test descriptions and error codes...................................................... 301
AESV-SES (AE Services Session)........................................................................................ 302
AESV-SES error log entries and recommended actions.................................................... 302
AESV-SES demand test descriptions and error codes...................................................... 303
ALARM-PT (Alarm Port)....................................................................................................... 303
ALM-PT error log entries and recommended actions........................................................ 304
ALM-PT demand test descriptions and error codes.......................................................... 304
AN-LN-PT (Analog Line Port)............................................................................................... 305
AN-LN-PT error log entries and recommended actions..................................................... 305
AN-LN-PT demand test descriptions and error codes....................................................... 307
ASAI-ADJ (ASAI Adjunct)..................................................................................................... 307
ASAI-BD (Multi-Application Platform Board)........................................................................... 307
ASAI-EPT (ASAI Endpoint).................................................................................................. 308
ASAI-EPT error log entries and recommended actions..................................................... 308
ASAI-EPT demand test descriptions and error codes....................................................... 313
ASAI-PT (ASAI Port)............................................................................................................ 314
ASAI-PT error log entries and recommended actions....................................................... 314
ASAI-PT demand test descriptions and error codes......................................................... 315
BRI-DAT (ISDN-BRI Data Module)........................................................................................ 316
BRI-PORT (ISDN-BRI Port).................................................................................................. 316
BRI-PORT error log entries and recommended actions.................................................... 318
BRI-PORT demand test descriptions and error codes....................................................... 320
BRI-SET, Various Adjuncts................................................................................................... 321
BRI-SET error log entries and recommended actions....................................................... 322
BRI-SET demand test descriptions and error codes............................................................... 330
SPID Facility Test.......................................................................................................... 330
CAB-EXFR (Emergency Transfer)........................................................................................ 332
CLAN-BD (Control LAN Circuit Pack).................................................................................... 333
CO-BD (Central Office trunk circuit pack).............................................................................. 333
CO-DS1 (DS1 CO Trunk)..................................................................................................... 334
CO-DS1 error log entries and recommended actions........................................................ 335
CO-DS1 demand test descriptions and error codes.......................................................... 336
CO-TRK (Analog CO Trunk)................................................................................................. 337
Interactions between switch and CO............................................................................... 337
Ground start operation for CO-TRK................................................................................. 338
CO-TRK error log entries and recommended actions....................................................... 339
CO-TRK demand test descriptions and error codes.......................................................... 343
DID-DS1 (Direct Inward Dial Trunk)...................................................................................... 343
DID-DS1 error log entries and recommended actions....................................................... 344
DID-DS1 demand test descriptions and error codes......................................................... 346
DIG-IP-S (Digital IP Station)................................................................................................. 346
DIG-IP-S error log entries and recommended actions....................................................... 347
DIG-IP-S demand test descriptions and error codes......................................................... 348
DIG-LINE (Digital Line)........................................................................................................ 349
Service states............................................................................................................... 349
Downloading terminal parameters................................................................................... 349
Programmable terminals................................................................................................ 349
Nonvolatile memory....................................................................................................... 350
Download actions.......................................................................................................... 350
Automatic download actions........................................................................................... 350
Demand download actions............................................................................................. 352
Parameter download status............................................................................................ 352
DIG-LINE error log entries and recommended actions...................................................... 353
DIG-LINE demand test descriptions and error codes........................................................ 355
DIOD-DS1 (DS1 DIOD trunk)............................................................................................... 356
DIOD-DS1 error log entries and recommended actions.................................................... 357
DIOD-DS1 demand test descriptions and error codes....................................................... 359
DLY-MTCE (Daily maintenance)........................................................................................... 359
DLY-MTCE error log entries............................................................................................ 360
Daily maintenance interference...................................................................................... 360
Incomplete command time-out........................................................................................ 361
E-DIG-ST (Emulated Digital Line)......................................................................................... 363
E-DIG-ST error log entries and recommended actions...................................................... 363
E-DIG-ST demand test descriptions and error codes........................................................ 364
EMG-XFER (Emergency Transfer)........................................................................................ 365
Emergency Transfer Status............................................................................................ 365
EMG-XFER error log entries and recommended actions................................................... 365
ERR-LOG (Error Log).......................................................................................................... 366
ERR-LOG error log entries............................................................................................. 366
Survivable Core Server........................................................................................................ 367
Survivable core server error log entries and recommended actions................................... 368
ETH-PT (Control LAN Ethernet)............................................................................................ 371
ETH-PT error log entries and recommended actions........................................................ 372
ETH-PT demand test descriptions and error codes................................................................ 374
ETR-PT (Enhanced Tone Receiver Port)............................................................................... 374
FW-STDL (Firmware Station Download)................................................................................ 374
Firmware station download commands........................................................................... 374
Firmware download to DCP stations............................................................................... 375
Downloading the firmware image.................................................................................... 375
Reading the image into memory..................................................................................... 376
Scheduling the download............................................................................................... 377
Firmware download problems......................................................................................... 377
FW-STDL error log entries and recommended actions...................................................... 378
H323-BCH (H.323 B-Channel).............................................................................................. 382
H323-BCH error log entries and recommended actions.................................................... 383
System commands........................................................................................................ 383
H323-SGR (H.323 Signaling Group)..................................................................................... 384
H.323-SGR error log entries and recommended actions................................................... 384
H323-SGR demand test descriptions and error codes...................................................... 389
H323-STN (H.323 IP Station)............................................................................................... 389
H323-STN error log entries and recommended actions..................................................... 390
H323-STN demand test descriptions and error codes....................................................... 390
INADS (INADS Link)............................................................................................................ 391
INADS demand test descriptions and error codes............................................................ 391
INADS test link - error code 1......................................................................................... 392
INADS test link - error code 10....................................................................................... 394
INADS test link - error code 11....................................................................................... 395
ISDN-PLK (ISDN-PRI signaling link port)............................................................................... 395
ISDN-PLK error log entries and recommended actions..................................................... 396
ISDN-PLK demand test descriptions and error codes....................................................... 397
ISDN-SGR (ISDN-PRI Signaling Group)................................................................................ 398
ISDN-SGR error log entries and recommended actions.................................................... 399
ISDN-SGR demand test descriptions and error codes...................................................... 404
ISDN-TRK (DS1 ISDN Trunk)............................................................................................... 405
Alarms based on service states...................................................................................... 406
DS1 ISDN Trunk Service States..................................................................................... 406
ISDN-PRI Trunk Service States...................................................................................... 409
ISDN-PRI service state - Out-of-service/NE..................................................................... 409
ISDN-PRI service state - No service state 1..................................................................... 410
ISDN-PRI service state - Out-of-service/FE..................................................................... 410
ISDN-PRI service state - Pending-in-service/pending-maint.............................................. 411
ISDN-PRI service state - Maint/NE.................................................................................. 411
ISDN-PRI service state - Maint/FE.................................................................................. 411
ISDN-PRI service state - In-service................................................................................. 412
ISDN-TRK error log entries and recommended actions..................................................... 412
ISDN-TRK demand test descriptions and error code........................................................ 415
JNL-PRNT (Journal Printer Link).......................................................................................... 416
LGATE-AJ (Ethernet ASAI Endpoint).................................................................................... 416
LIC-ERR (License Error Mode)............................................................................................. 416
LIC-ERR error log entries and recommended actions....................................................... 417
LGATE-PT (Ethernet Adjunct Port)........................................................................................ 423
LOG-SVN (Login Security Violation)...................................................................................... 423
LOG-SVN error log entries and recommended actions..................................................... 423
MED-GTWY (MEDIA GATEWAY)......................................................................................... 425
MED-GTWY error log entries and recommended actions.................................................. 425
MED-GTWY demand test descriptions and error codes.................................................... 427
MG-ANA (Analog Media Module).......................................................................................... 427
MG-ANA error log entries and recommended actions....................................................... 427
MG-ANA demand test descriptions and error codes......................................................... 429
MG-ANN (Media Gateway Announcement Module)................................................................ 429
MG-ANN error log entries............................................................................................... 430
MG-ANN (Voice Announcements)......................................................................................... 431
MG-BRI (BRI Trunk Media Module)....................................................................................... 431
MG-BRI error log entries and recommended actions........................................................ 431
MG-BRI demand test descriptions and error codes.......................................................... 433
MG-DCP (Digital Line Media Module)................................................................................... 433
MG-DCP error log entries and recommended actions....................................................... 434
MG-DCP demand test descriptions and error codes......................................................... 435
MG-DS1 (DS1 Interface Media Module)................................................................................ 436
MG-DS1 error log entries and recommended actions....................................................... 436
MG-DS1 demand test descriptions and error codes......................................................... 441
MG-IAMM (Integrated Analog Media Module)........................................................................ 442
MG-IAMM error log entries and recommended actions..................................................... 443
MG-IAMM demand test descriptions and error codes....................................................... 444
MG-IBRI (Integrated BRI Trunk Media Module)...................................................................... 445
MG-SYNC (Synchronization)................................................................................................ 445
MG-SYNC error log entries and recommended actions........................................................... 445
MIS (Management Information System)................................................................................ 446
MIS error log entries and recommended actions.............................................................. 446
No-LIC (No license)............................................................................................................. 447
How systems go into no-license mode............................................................................ 447
No-LIC error log entries and recommended actions.......................................................... 449
NR-CONN (Network-Region Connect).................................................................................. 450
Repair strategies........................................................................................................... 450
NR-CONN error log entries and recommended actions..................................................... 451
NR-CONN demand test description and error codes........................................................ 451
NR-REG (Network Region Registrations).............................................................................. 451
NR-REG error log entries and recommended actions....................................................... 452
PDMODULE (Processor Data Module).................................................................................. 453
Standalone DCP data modules....................................................................................... 454
Data adapters............................................................................................................... 454
Configurations and maintenance.................................................................................... 454
PDMODULE error log entries and recommended actions................................................. 456
PDMODULE demand test descriptions and error codes.................................................... 458
PE-BCHL (PRI Endpoint Port).............................................................................................. 459
Wideband Switching...................................................................................................... 459
Signaling and B-Channel States..................................................................................... 460
Alarming Based on Service States.................................................................................. 460
PRI Endpoint Port Service States................................................................................... 461
PRI endpoint service state OOS/NE................................................................................ 462
PRI endpoint service state OOS/FE................................................................................ 463
PRI endpoint service state OOS/FE PINS....................................................................... 463
PRI endpoint service state MTC/NE................................................................................ 463
PRI endpoint service state MTC/FE................................................................................ 464
PRI endpoint service state MTC/FE PINS........................................................................ 464
PRI endpoint service state INS....................................................................................... 464
PE-BCHL error log entries and recommended actions...................................................... 465
PLAT-ALM (Platform Alarms)................................................................................................ 468
PMS-LINK (Property Management System Link).................................................................... 469
Restoring the PMS Link................................................................................................. 470
PMS-LINK error log entries and recommended actions..................................................... 471
PMS-LINK demand test descriptions and error codes....................................................... 473
PMS-PRNT (PMS Printer Link)............................................................................................. 474
Restoring the PMS Printer Link....................................................................................... 475
PMS-PRNT error log entries and recommended actions................................................... 476
PMS-PRNT demand test descriptions and error codes..................................................... 476
PRI-CDR (Call Detail Recording Link)................................................................................... 477
Restoring the CDR Link................................................................................................. 478
PRI-CDR error log entries and recommended actions...................................................... 478
PRI-CDR demand test descriptions and error codes......................................................... 480
PROC-SAN (Process sanity audits)...................................................................................... 480
PROC-SAN error log entries and recommended actions................................................... 480
RANL-STA (Remote Analog Line Station Port)....................................................................... 481
RANL-STA error log entries and recommended actions.................................................... 481
RANL-STA demand test descriptions and error codes...................................................... 482
RDIG-STA (Remote Digital Station)...................................................................................... 483
Terminal Parameters...................................................................................................... 483
REM-OFF (Remote Office)................................................................................................... 489
REM-OFF error log entries and recommended actions..................................................... 490
RING-GEN (Analog Ring Generator)..................................................................................... 490
RING-GEN error log entries and recommended actions.................................................... 491
SEC-CDR (Call Detail Recording Link).................................................................................. 491
SIP-BCH (SIP B-Channel).................................................................................................... 491
SIP-BCH error log entries and recommended actions....................................................... 492
System commands........................................................................................................ 492
SIP-SGRP (SIP Signaling Group)......................................................................................... 492
SIP-SGRP error log entries and recommended actions.................................................... 493
SIP-SGRP demand test descriptions and error codes....................................................... 503
SP-REG-M (Survivable Processor-Main)............................................................................... 503
SP-REG-M error log entries and recommended actions.................................................... 503
SP-REG-S (Survivable Processor)........................................................................................ 504
SP-REG-S error log entries and recommended actions.................................................... 505
STRAT-3 (Stratum-3 Clock).................................................................................................. 505
Stratum-3 Clock LED Strategy........................................................................................ 507
STRAT-3 error log entries and recommended actions....................................................... 509
SYS-LINK (System Links).................................................................................................... 512
Recording System Link Events....................................................................................... 512
Identifying a System Link............................................................................................... 513
System link problems..................................................................................................... 513
Repairing system links................................................................................................... 513
SYS-LINK error log entries and recommended actions..................................................... 514
SYS-LINK demand test descriptions and error codes....................................................... 515
SYSTEM (System).............................................................................................................. 516
SYSTEM error log entries and recommended actions....................................................... 516
TDMODULE (Trunk Data Module)........................................................................................ 517
Time-day (time of day)......................................................................................................... 517
Time-day error log entries and recommended actions...................................................... 518
TSC-ADM (Administered temporary signaling connections).................................................... 518
TSC-ADM error log entries and recommended actions..................................................... 519
TSC-ADM demand test descriptions and error codes....................................................... 520
XXX-BD (Common port media module)................................................................................. 520
XXX-BD error log entries and recommended actions........................................................ 521
XXX-BD demand test descriptions and error codes.......................................................... 524
Chapter 7: Maintenance demand tests............................................................................... 525
Dial Tone Test (#0).............................................................................................................. 525
CO Port Diagnostic Test (#3)................................................................................................ 529
NPE Crosstalk Test (#6)....................................................................................................... 532
Conference Circuit Test (#7)................................................................................................. 541
GPP NPE Crosstalk Test (#9)............................................................................................... 547
Local Loop Test (#13).......................................................................................................... 553
Digital Station Lamp Update (#16)........................................................................................ 558
Digital Station Audits Test (#17)............................................................................................ 561
Looparound and Conference Test (#33)................................................................................ 566
Port Diagnostic Test (#35).................................................................................................... 570
Port Audit And Update Test (#36).......................................................................................... 577
ONS Ringer Application Test (#48)........................................................................................ 582
Control Channel Looparound Test (#52)................................................................................ 586
SAKI Sanity Test (#53)......................................................................................................... 588
Hybrid Line Local Digital Looparound Test (#58).................................................................... 591
Hybrid Line Remote Digital Looparound Test (#59)................................................................. 593
Internal Looparound Test (#135)........................................................................................... 595
DS1 Tie Trunk Seizure Test (#136)....................................................................................... 596
Loss of Signal Alarm Inquiry Test (#138)............................................................................... 601
Blue Alarm Inquiry Test (#139).............................................................................................. 601
Red Alarm Inquiry Test (#140).............................................................................................. 604
Yellow Alarm Inquiry Test (#141)........................................................................................... 606
Major Alarm Inquiry Test (#142)............................................................................................ 609
Minor Alarm Inquiry Test (#143)............................................................................................ 610
Slip Alarm Inquiry Test (#144)............................................................................................... 612
DS1 Translation Update Test (#146)..................................................................................... 614
Link Tear Down Test (#213).................................................................................................. 616
Link Retry Test (#215).......................................................................................................... 618
140AY Channel Sanity Inquiry Test (#222)............................................................................. 620
Signaling Link State Audit Test (#255)................................................................................... 620
Service State Audit Test (#256)............................................................................................ 622
Call State Audit Test (#257).................................................................................................. 626
ISDN Test Call Test (#258)................................................................................................... 629
TSC Heartbeat Inquiry Test (#604)........................................................................................ 637
Error code: 2000........................................................................................................... 640
BRI Port Local TDM Looparound Test (#619)......................................................................... 642
Electronic Power Feed Restoral Test (#620).......................................................................... 646
Level 1 Status Inquiry Test (#621)......................................................................................... 647
Electronic Power Feed Inquiry Test (#622)............................................................................. 651
CRC Error Counter Test (#623)............................................................................................ 653
Layer 1 Transmission Error Counter Test (#624).................................................................... 655
Receive FIFO Error Counter Test (#625)............................................................................... 656
Signaling Link Status Test (#626).......................................................................................... 658
BRI Remote Loopback Test (#627)....................................................................................... 660
BRI XID Test (#628)............................................................................................................. 665
BRI Layer 3 Query Test (#629)............................................................................................. 669
BRI Set Audits Test (#630)................................................................................................... 673
Primary Signaling Link Hardware Check (#636)..................................................................... 675
Remote Layer 3 Query (#637).............................................................................................. 677
Secondary Signaling Link Hardware Check (#639)................................................................. 680
Signaling Link Board Check (#643)....................................................................................... 682
Layer 2 Status Query Test (#647)......................................................................................... 684
Tie Trunk Dial Test (#747).................................................................................................... 686
SNI Destructive Facility Off-Board Test (#756)....................................................................... 690
Analog Port Sanity Test (#963)............................................................................................. 690
VC DSP Port DSP Looparound Test (#1105)......................................................................... 691
VC Port Reset DSP Test (#1106).......................................................................................... 695
TSI Looparound Test (#1108)............................................................................................... 697
Digital Terminal Remote Looparound Test (#1201)................................................................. 699
DS1 Board Loopback Test (#1209)....................................................................................... 703
CSU Equipment Loopback Test (#1210)................................................................................ 706
CSU Repeater Loopback Test (#1211).................................................................................. 710
CPE Loopback Jack Test (#1212)......................................................................................... 714
Far CSU Loopback Test (#1213)........................................................................................... 718
One-Way Span Test (#1214)................................................................................................ 722
Inject Single Bit Error Test (#1215)........................................................................................ 725
End Loopback/Span Test (#1216)......................................................................................... 727
ICSU Status LEDs Test (#1227)............................................................................................ 730
Trunk-side Layer 1 Query Test (#1242)................................................................................. 733
Ethernet Local Looparound Test (#1278)............................................................................... 737
ASAI Link Status Test (#1365).............................................................................................. 738
Registration Status Inquiry Test (#1372)................................................................................ 740
Signaling Path PING Test (#1373)........................................................................................ 741
C-LAN Ethernet Port Status Test (#1386).............................................................................. 743
Signaling Group Ping Test (#1387)........................................................................................ 746
VoIP Status Test (#1392)..................................................................................................... 750
Firmware Download Test (#1413)......................................................................................... 751
Network Region Interconnectivity Test (#1417)...................................................................... 755
Echo Canceller Test (#1420)................................................................................................ 758
Link State Audit Test (#1527)................................................................................................ 761
Power Supply Temperature Test (#1537)............................................................................... 762
Enable Survivable Core Server Cluster (#1606)..................................................................... 762
Disable Survivable Core Server Cluster (#1607).................................................................... 763
AESVCS Session Level Link Status Test (#1623)................................................................... 765
AESVCS Link Heartbeat Test (#1624)................................................................................... 765
Media Gateway Hyperactivity Audit Test (#1659).................................................................... 766
H.323 Signaling Layer 3 Test (#1673)................................................................................... 767
IP Signaling Group Far-End Status Test (#1675).................................................................... 768
Media Gateway Announcement Module Test (#1683)............................................................. 771
Media Gateway VoIP Capacity Test #1718............................................................................ 772
Error Code: 1005........................................................................................................... 772
Error code: 1706........................................................................................................... 773
Error code: 2000........................................................................................................... 773
NO BOARD........................................................................................................................ 773
Hyperactive DS1 Media Module............................................................................................ 774
Repair Procedures for DS1/UDS1 Circuit Pack/Media Module................................................ 775
T1 network facility procedures........................................................................................ 775
Line-side terminating device procedures......................................................................... 775
Chapter 8: Resources........................................................................................................... 776
Communication Manager documentation............................................................................... 776
Finding documents on the Avaya Support website........................................................... 778
Accessing the port matrix document................................................................................ 778
Avaya Documentation Center navigation......................................................................... 779
Training.............................................................................................................................. 780
Viewing Avaya Mentor videos............................................................................................... 780
Support.............................................................................................................................. 781
Using the Avaya InSite Knowledge Base......................................................................... 781
Chapter 1: Introduction
Purpose
This document contains information about:
• Server alarms generated on various platforms
• Denial events that are logged in the Communication Manager
• Logs associated with monitoring, testing, and maintaining an Avaya Server or Media
Gateway
The server alarms cover categories such as process watchdog, environmental, login, translation
monitoring, and power supply alarms. This document also lists alarm identifications, levels, and
resolutions.
The denial events cover information on denial events that are logged in the Communication
Manager denial event log.
The log references cover many of the faults and troubles that can occur, and also provides the
procedures to correct them.
The intended audience of this document are as follows:
• For alarms:
- Telecommunications managers
- Telephony Administrators
• For events:
- Telephony Administrators
- Support Personnel
• For log references
- Avaya technicians
- Provisioning specialists
- Business partners
- Customers
- Maintenance technician dispatched to a customer site in response to a trouble alarm or a
user trouble report
Discontinued support for IP Server Interface (TN2312, commonly known as “IPSI”)
- Maintenance technician located at a remote maintenance facility

- Maintenance technician assigned to the customer
The technician is expected to have a working knowledge of telecommunications
fundamentals and of the particular Avaya server and media gateway to the extent that the
procedures in this book can be performed, in most cases, without assistance.
If the trouble is not resolved, it is the maintenance technician’s responsibility to escalate the
problem to a higher level of technical support. Escalation should conform to the procedures in
the Technical and Administration Escalation Plan.
For more information about the supported servers and supported gateways, see Avaya Aura®
Communication Manager Hardware Description and Reference.
Discontinued support for IP Server Interface (TN2312,

commonly known as “IPSI”)
With Release 10.2, Communication Manager does not support the IP Server Interface (IPSI). As
a result, access and functionality are removed. This means, the IPSI connected cabinets and
gateways do not work with Communication Manager Release 10.2. Examples of IPSI connected
cabinets and systems include G3cfs, G3csi, G3i, G3r, G3s, G3si, G3vs, G3x, G600, G650, MCC,
SCC, CMC, IPSI, IP Server Interface, and IP port network.
Discontinued support also includes the TN8412, which previously paired with the TN8400 blade
server. TN8412 was last supported with Communication Manager Release 5.x.
For more information, see the End of sale G650 document published on the Avaya Support
website.
Chapter 2: Server Alarms
During normal operations, software or firmware may detect error conditions pertaining to specific
Maintenance Objects (MOs). The system automatically attempts either to fix or circumvent these
problems. The errors are detected in two ways:
• By firmware on the component during ongoing operations.
• A periodic test or a scheduled test started by software.
Tests that are run on demand are generally more comprehensive and potentially disruptive than the
scheduled tests.
The Error Log records all the errors. Communication Manager raises an alarm if a component incurs
too many errors.
Alarms on the Linux servers can occur in several areas:
• Media modules, servers, the media gateway processor, and the layer 2 switching processor are
all capable of detecting internal failures and generating traps and alarms.
• Media gateways detect faults and alert the server. The server then raises an alarm and sends
the alarm to an appropriate network management site.
• Communication Manager alarms reflect the condition of network elements such as circuit
packs, media modules, and their associated links, ports, and trunks.
• Messaging alarms provide the condition of external messaging systems.
Alarms are viewed using the following:
• System Management Interface (SMI): Provides alarms information related to Communication
Manager and the server.
Note:
For non-Communication Manager alarms, use the web page header Alarms and
Notification and Diagnostics: View System Log. Choose the appropriate heading, and, if
necessary, call Avaya support.
• Server bash shell: Provides alarms information related to Communication Manager and the
server.
• Server System Access Terminal (SAT) Command Line Interface (CLI): Provides alarms
information related to Communication Manager.
• MGP CLI on the Media Gateway: Provides alarms and traps information related to the media
gateway and its subsystems.
Server maintenance
• Layer 2 switching processor CLI on the media gateway: Provides information related to the
media gateway stack.
To display information related to Communication Manager, and the server alarms, use the System
Management Interface (SMI) or the server bash shell.
This document provides information only for server alarms.
Server maintenance
Server maintenance focuses on the following functional roles:
• Provide the alarm logging and reporting service for all other system components.
• Provide support-specific interface and information for server duplication and maintenance
software.
• Provide maintenance commands that the support technicians use to determine the condition
of the system and perform repair or recovery actions or both.
• Provide server diagnostic, recovery, or notification mechanisms when a server processor is
nonfunctional, that is, unable to execute the system software.
Alarm classifications
Alarms are classified depending on their impact 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 do not render a crucial
portion of the system inoperable. Minor alarms require attention. However, a minor alarm
typically affects only a few trunks, 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 media module or circuit pack.
• Off-board problems originate in a process or component that is external to the Media Module
or circuit pack.
Alarm logs
A user can view alarms using the web interface, CLI, and SAT command-line interface.
Server Alarms
Alarms logged by Communication Manager are stored in an alarm log. The following is an
example of a server alarm in the syslog:
20070606:012435000:36096:lxsys:MED:volunteer-srv1 : >#2,YY,ACT,001,MED-
GTWY,n,MAJ,MAJ,N,06/06:01:24:35,none,1,0x0:0x1:5156:31004:!#
When you enter the command almdisplay on the server command line, the system displays
information from the text string in the following manner:
CommunicaMgr ALARMS
===================
ID MO Source On Bd Lvl Ack Date
1 DLY-MTCE n MIN Y Fri Jun 08 10:09:07 MDT 2007
2 IPMEDPRO 01A10 y MIN Y Wed Jun 06 09:29:21 MDT 2007
3 MED-GTWY 002 n MAJ Y Wed Jun 06 01:24:35 MDT 2007
4 MED-GTWY 001 n MAJ Y Wed Jun 06 01:24:35 MDT 2007
Alarms in Linux servers

The server has an SNMP trap manager that collects traps from:
• Uploads and downloads to media modules
• VoIP media modules
• VoIP engines on media gateway motherboards
• Media gateway-associated UPS systems
Server alarms perform a similar role to Communication Manager alarms in a traditional telephony
context. Server alarms:
• Comprise related sets of alarms
• Create an internal record of actual or potential problems
• Notify maintenance personnel of a problem
• Help isolate the source of the problem
• Point to and facilitate local and remote resolution of a problem
Setting up external notification for events

About this task
A Linux-based server can be configured to serve as the trap collector and provide external alarm
notification.
Displaying alarms
Procedure
Perform one of the following tasks:
• Call INADS of the Avaya technical service center.
• Send an e-mail to specified destinations.
• Send an SNMP trap to a specified network management address.
Displaying alarms
Procedure
1. To view the verbose (-v) output of the alarm, type the almdisplay -v command.
2. If the almdisplay command returns a failure message, such as almdisplay:
4: Unable to connect to MultiVantage, enter the man almdisplay Linux
command for command-related information.
Chapter 3: Linux Server Alarm Types
ARB (Arbiter)
The Arbiter process runs on duplex servers to:
• Decide which server is in good condition and more able to be active
• Coordinate data shadowing between servers under the control of Duplication Manager
At the physical and data-link layers, three links may serve as redundant inter-arbiter UDP
communication paths: the control network A link, the control network B link (if present), or an
Ethernet-based duplication link. Two of these links must be present. The redundant inter-arbiter
UDP communication paths perform the following functions:
• Enable arbitration between the active and standby servers
• Provide the necessary status signaling for memory refreshes
All inter-arbiter communication links use triple DES encryption for secure communication and
control.
ARB alarms
The following table lists the Arbiter alarms and the related troubleshooting procedures.
Table 1: ARB alarms
Event ID Link to description

3 See ARB Event ID 3 on page 23.
14 See ARB Event ID 14 on page 28
ARB (Arbiter)
ARB Event ID 3
Alarm level MIN
Alarm text Interchange handoff failed
Cause
The standby server could not process the interchange request of the active server. The
interchange does not occur, and the active side remains active.
Proposed Solution 1
1. From the Server section of the web interface, select Status Summary to see if the standby
side is Reset.
2. To manually clear the alarm, select Current Alarms and the appropriate alarm, and click
Clear.
3. If the problem persists, troubleshoot the standby server:
a. Check if the standby side is Reset. From the Server section of the web interface,
select Status Summary.
b. Check for application problems by selecting View Process Status and restore any
applications with problems.
c. Check for problems with an Ethernet interface by selecting the Execute Ping
diagnostic. Check both sides of each failed link, and make necessary repairs.
4. If the applications and interfaces are okay but the problem persists, go to the Avaya
Support website at http://support.avaya.com to open a service request.
Proposed Solution 2
1. Type server, and check if the standby side is Reset.
2. Type almclear -n #id to manually clear the alarm.
3. If the problem persists, troubleshoot the standby server:
a. Type server and check if the standby side is Reset.
b. Type statapp and check for application problems. Restore all applications with
problems.
c. Check for problems with an Ethernet interface by typing pingall -a. Check both
sides of each failed link, and make any necessary repairs.
4. If the applications and interfaces are okay but the problem persists, go to the Avaya
ARB Event ID 7
Alarm level MAJ
Linux Server Alarm Types
Alarm text Arbiter in invalid/unknown state
Cause
Memory corruption or bad code/build.
Proposed Solution
1. Verify that the server state is corrupt by entering the following commands on the Linux
command line: server stop -Sf -s arbiter start -s arbiter server -c
If the output no longer shows Mode: Corrupt!, then the problem is fixed. Otherwise,
proceed to Step 2.
2. If the arbiter file is OK or if the problem persists, go to the Avaya Support website at
http://support.avaya.com to open a service request.
ARB Event ID 8
Alarm level MIN
Alarm text Both servers thought they were active
Cause
• A high-priority process caused the active Arbiter to hang for at least 4.1 seconds causing
an interchange. Each Arbiter then realized that the other had assumed the active role. An
automatic resolution process must leave the newly active server active, while the other server
backs down to the standby role.
• Every Inter-arbiter link is down or misconfigured.
Proposed Solution 1
1. To check server status, see Verifying the server status.
2. If one server is active and the other is standby, manually clear the alarm:
a. From the Web interface, select Current Alarms and the appropriate alarm, and click
Clear.
b. From the Linux command line, enter almclear -n #id .
3. If the problem persists, go to the Avaya Support website at http://support.avaya.com to
open a service request.
Proposed Solution 2
1. To check server status, see Verifying the server status.
2. Check for problems with an Ethernet interface:
a. From the Web interface, select the Execute Ping diagnostic.
b. From the Linux command line, enter pingall -a.
Check both sides of each failed link, and make necessary repairs.
ARB (Arbiter)
3. If the links are okay but the problem persists, go to the Avaya Support website at http://
support.avaya.com to open a service request.
ARB Event ID 9
Alarm level WRN
Cause
Before an interchange, the standby server is significantly in better condition than the active server
requesting the interchange. The active server is probably unable to sustain call processing.
Proposed Solution
1. Compare the condition of both the servers:
a. From the Server section of the Web interface, select Status Summary.
b. From the Linux command line, enter server.
2. Using the output from Step 1, check the status of the individual processes of each server.
3. Check the status of the individual processes of the active server:
a. From the Web interface, select View Process Status.
b. From the Linux command line, enter statapp.
After checking the status of the individual processes, restore any applications that have
problems.
4. Check if the standby side is reset:
a. From the Server section of the Web interface, select Status Summary.
b. From the Linux command line, enter server.
5. Check the status of the individual processes of the standby server:
a. From the web interface, select View Process Status.
b. From the Linux command line, enter statapp.
After checking the status of the individual processes, restore any applications that have
problems.
6. Check for problems with an Ethernet interface:
a. From the web interface, select the Execute Ping diagnostic.
b. From the Linux command line, enter pingall -a.
Check both sides of each failed link, and make any necessary repairs.
On the Linux command line, enter ifconfig -a.. Ensure the IP addresses
match /etc/opt/ecs/servers.conf and /etc/hosts, and check if all ethernet ports
have been assigned IP addresses. Enter /sbin/arp -a to ensure that none of the MAC
addresses display the incomplete message.
7. If the applications and interfaces of the standby server are OK but the problem persists, go
to the Avaya Support website at http://support.avaya.com to open a service request.
After the interchange, the condition of the newly active server must be better than the
condition of the standby server. See the SOH values bb and cc. See String pairs of ARB
Event #9. The server with the larger bb value is considered to be in better condition. If
the value of bb is the same for both the servers, the server with the larger cc value is
considered to be in better condition. If the condition of the newly active server is better than
the condition of the standby server, troubleshoot the standby server.
If the condition of the standby server is better than the newly active server:
a. Manually clear the alarm:
• From the web interface, select Current Alarms and the appropriate alarm, and
click Clear.
• From the Linux command line, enter almclear -n #id.
b. If the problem persists, go to the Avaya Support website at http://support.avaya.com
to open a service request.
ARB Event ID 11
Alarm level WRN
Alarm text Cannot create receive socket.

Cannot create transmit socket.
Cannot bind receive socket.
Cannot (re)bind send socket.
Cause
Since the Arbiter continuously attempts to create or bind the socket, the problem might resolve
itself. Once resolved, the Arbiter can send and receive every Interarbiter link with no subsequent
error messages in the trace log.
Proposed Solution
1. To examine the alarm log to distinguish between a bind or create problem or a send or
receive problem:
a. From the Web interface:
a. Select Current Alarms and the appropriate alarm.
b. Select the View System Logs diagnostic.
c. Select the Logmanager Debug trace.
d. Specify the Event Range for the appropriate time frame.
e. Match the cannot create pattern
b. From the Linux command line, enter almdisplay -v.
ARB (Arbiter)
2. Check for completeness and consistency of the hosts and servers.conf files
(containing IP addresses of the configured components of the system) located on the
servers:
a. From the web interface select Configure Server.
b. From the Linux command line, enter:
more /etc/hostsmore /etc/opt/ecs/servers.conf
The Arbiter uses port number 1332 for sockets. Enter netstat -a | grep 1332 to
check if the alarm is still active. This command displays an output similar to the following:
upd 0 0<server-name>-cnb:1332 *.*
upd 0 0<server-name>-cna:1332 *.*
upd 0 0<server-name>-dup:1332 *.*
3. If the IP addresses match and there are no alarms for port 1332, manually clear the alarm:
Clear.
b. From the Linux command line, enter almclear -n #id.
4. If this problem affects call processing or if the problem persists, continue with Step 6. If this
problem does not affect call processing or if the problem has resolved, continue only at the
convenience of the customer.
5. Escalate this problem for explicit guidance with Steps 5a through 6.
a. Enter server to verify that the suspected server is the standby.
b. If the suspected server is not the standby, enter server -if to force a server
interchange. Busyout the standby server from the Linux command line by entering
server -b.
c. Reboot the server (as the standby):
• From the Web interface, select Shutdown This Server.
• From the Linux command line, enter
/sbin/shutdown -r now
6. If rebooting the standby server does not help or if the problem persists, go to the Avaya
ARB Event ID 12
Alarm level MIN
Alarm text Interchange without doing prep
Cause
Since the Arbiter cannot create a thread to request file synchronization, some files did not get
shadowed.
Proposed Solution
1. Examine the trace logs for the entry, Can't create interchange-prep thread:
a. Select the View System Logs diagnostic and Logmanager Debug trace.
b. Specify the Event Range for the appropriate time frame.
c. Match the interchange-prep pattern.
b. From the Linux command line, enter logv -t ts
2. Resubmit any translation changes using the save_trans command.
3. Manually clear the alarm:
Clear.
b. From Linux command line, enter almclear -n #id.
ARB Event ID 13
Alarm level MIN
Alarm text Heartbeat timeout from ACTIVE
Cause
The two possible causes for this event are:
• An unexplained Linux lock-up that starved CPU cycles from all Communication Manager
processes for more than 3.3 seconds.
• A third main server with a server ID that matches one of the other two main servers was
somehow started and is accessible from the network.
In the case of a Linux lock-up, the problem corrects itself by the time the problem is detected and
corrective action is not required.
Proposed Solution
1. On the Linux command line, enter /sbin/arp -a to determine the MAC addresses of the
alternate server ethernet ports associated with the CNA, CNB, and duplication links.
2. Log in to the alternate server and verify that the MAC addresses match. Do this from both
servers.
3. Check for a mismatch in the MAC addresses that indicates the presence of a third system
posing as a doppelganger.
4. Use a network sniffer to find the third main server.
ARB Event ID 14
Alarm level MIN
ARB (Arbiter)
Alarm text Standby failed to come back up
Cause
The standby server in a duplex system is nonoperational for longer than 15 minutes and cannot
generate alarm on its own behalf. Typical causes are:
• The rolling Linux reboots due to reloading of a rolling Communication Manager or a failure to
start Communication Manager.
• A server was turned down (manually or UPS failure) for more than 15 minutes without first
being taken out of service (busied out). The correct procedure for doing a stop on a standby
server is to busy it out first, then stop it.
Proposed Solution
Go to the Avaya Support website at http://support.avaya.com to open a service request.
Chapter 4: Verifying the server status
Verifying the server status using the Web interface

Procedure
1. From the Server section of the web interface, select Status Summary and verify that both
the servers are active.
2. To distinguish the cause, examine the trace logs for Interarbiter messages with timestamps
shortly before to shortly after the loss of heartbeat by:
• Selecting the View System Logs diagnostic and Logmanager Debug trace.
• Specifying the Event Range for the appropriate time frame.
• Matching the Interarb pattern.
3. Depending on the cause, continue with either Step 1 or Step 2.
Verifying the server status using the command line

interface
Procedure
1. Type server, and verify that both servers are active.
2. To distinguish the cause, examine the trace logs for Interarbiter messages with timestamps
shortly before to shortly after the loss of heartbeat by entering logv -t ts.
3. Depending on the cause, continue with either Step 1 or Step 2.
String pairs of ARB Event # 9

ARB Event #9 generates pairs of SOH strings. In each string pair, the first string represents the
active and the second string represents the standby SOH of the server just before an interchange.
Since, unless prevented by external circumstances, Event 9 triggers a server interchange, the first
string normally represents a less efficient server – which became the standby. So, the data of the
first string is more pertinent.
BKP (Backup)
BKP (Backup)
The system generates a backup (BKP) alarm only when a scheduled backup job fails. A backup
now job does not have a BKP alarm.
The following table lists the Backup alarms and the related troubleshooting procedures.
Table 2: BKP Alarms

10 See BKP Event ID 10 on page 31.
BKP Event ID 10
Alarm level MAJ
Alarm text Scheduled backup was terminated
Proposed Solution
1. Log on to Communication Manager System Management Interface.
2. Click Data Backup/Restore > Backup Logs.
The system displays the reason for the backup job failure.
3. To schedule a backup, click Data Backup/Restore > Schedule Backup.
Caution:
Attempting to restore a failed backup is not a valid recommendation since there is no
backup image to restore.
CMG (Common Media Gateway)

For description of CMG traps, see Gateway Traps for the G430/G450/Avaya S8300 Servers.
DUP (Duplication Manager)

The Duplication Manager process in coordination with the Arbiter process runs on the servers to
control data shadowing between the servers.
At the physical and data-link layers, an Ethernet-based duplication link provides a TCP
communication path between the Duplication Manager of each server to control data shadowing.
This TCP/IP link provides the actual data shadowing for software duplication. For hardware
Verifying the server status
duplication, there is an additional fiber optic link between the duplication memory boards that
provides the data shadowing.
DUP alarms
The following table lists the Duplication Manager alarms and the related troubleshooting
procedures.
Table 3: DUP alarms of

2 See DUP Event ID 2 on page 32.
6 See DUP Event ID 6 on page 33.
DUP Event ID 2
Alarm level MAJ
Alarm text Duplication link down
Cause
One Duplication Manager server cannot communicate with the other Duplication Manager server.
Proposed Solution 1
1. Access the trace log:
c. Match the “ndm” or “DUPLICATION” pattern.
2. Examine the output of the trace-log query for one of the following messages:
3. “mainlp: get_addrs returned ***. Could not get IP address for other server.Verify name
and address in servers.conf. ndm exiting.” “san_check_msg() sync_msg failed: DUPLINK
DOWN.”
4. Check if the dup link status is “up” from the Server section of the Web interface by
selecting Status Summary.
5. If the dup link status is “up”, manually clear the alarm by selecting Current Alarms and the
appropriate alarm, and click Clear.
6. If the dup link status does not show “up”, check the Ethernet interface of the duplication
interface by selecting the Execute Ping diagnostic.
7. If pingall passes, check the applications of the other server by selecting View Process
Status.
Survivable core server
Proposed Solution 2
1. Access the trace log by entering logv -t ts.
2. Examine the output of trace-log query for one of the following messages:
“mainlp: get_addrs returned ***. Could not get IP address for other server.Verify name
and address in servers.conf. ndm exiting.” “san_check_msg() sync_msg failed: DUPLINK
DOWN.”
3. Enter server and check if the dup link is “up.”
4. If the dup link status shows “up”, manually clear the alarm by entering almclear -n
#id.
5. If the dup link status does not show “up”, check the Ethernet connectivity of the duplication
interface by entering pingall -d.
6. If pingall passes, enter statapp and check the applications of the other server.
DUP Event ID 6
Alarm text Incorrect duplication link speed
Cause
This alarm is generated when the NIC (Network Interface Card) that is used for the duplication
does not have 1 GB capacity, when the cable is not functioning properly, or when Communication
Manager does not have Ethernet with 1 GB capacity.
Survivable core server

The following table describes the Survivable core server alarms and the related troubleshooting
procedures.
Table 4: Survivable Core Server Alarms of

5 See Survivable Core Server Event ID 5 on page 33.
Survivable core server Event ID 5

Alarm level MIN
Alarm text Survivable Core Server not registered cls YYY: cls RRR
Cause
Survivable core server Cluster ID YYY is not registered to the active server of the main cluster.
The main active server sends this trap for each survivable core server in the system (RRR !=
YYY). A survivable core server will only report status for itself (RRR = YYY).

Alarm level MIN
Alarm text Survivable Core Server registered cls YYY svid ZZZ: cls RRR
Cause
Survivable core server Server ID ZZZ of cluster ID YYY is registered to the active server of the
main cluster. The active server of the main cluster sends this trap for each survivable core server
in the system (RRR != YYY). The survivable core server will only report status for itself (RRR =
YYY). A survivable core server will only report status for itself (RRR = YYY).

Alarm level MIN
Alarm text Survivable Core Server changed to disable state: cls RRR
Cause
Survivable core server cluster RRR is changed to the disable state.

Alarm level MIN
Alarm text Survivable Core Server changed to enable state: cls RRR
Cause
Survivable core server cluster RRR is changed to the enable state.
FSY (File Synchronization)

The File Synchronization (FSY) process uses TCP-based communication over 100BaseT Ethernet
links to provide synchronized duplication of critical data files, including translations and important
Linux files.
There are two classes of FSY alarms, one class is associated with server communication failures
and the other is associated with fileset configuration file errors.
FSY (File Synchronization)
The following table describes the FSY alarms and the related troubleshooting procedures.
Table 5: FSY Alarm

1 - 999 See FSY Event ID 1 - 999 on page 35.
1000 - 1999 See FSY Event ID 1000 - 1999 on page 36.
FSY Event ID 1 - 999

Alarm level MIN
Alarm text event string (server): [server address] type
Examples:
• filesync failure (server): 10.115.9.12 ESS
• alarm resolved (server): 10.115.9.36 ESS
• filesync failure (server): 10.115.9.25 LSP
Description Server communication errors use Event IDs in the of range of 1 - 999, where
each Event ID is associated with a particular server and the IP address of the
server. The source of these alarms is always server, which indicates the server
connection problems.
The event string can be one of the following:

• filesync failure — The alarm is generated because of a failure.
• alarm cleared — The alarm has been cleared by using a command.
• alarm resolved — The latest filesync has succeeded.
The alarm text also includes the type of the server and the IP address of the server. The following
are the different types of server:
• DUP
• ESS
• LSP
Cause
File synchronization operation failed due to a server communication error. The IP address and
server type indicate which connection to diagnose.
Proposed Solution
The type of the server and the IP address of the server indicate which connection should be
diagnosed. For ESS and LSP server types, make sure that the server connection is working. For
DUP server type, make sure that the Ethernet duplication link is working.
FSY Event ID 1000 - 1999

Alarm level MIN
Alarm text event string (prescript): [fileset name] type
Example:
• filesync failure (prescript): trans DUP
Description Fileset configuration errors use Event IDs in the range of 1000 - 1999, where
each Event ID is associated with a fileset. The source of these alarms is always
prescript, which indicates that the prescript associated with the named fileset has
failed on the local server.
Note:
The system does not detect postscript failures.
The event string can be one of the following:
• filesync failure — The alarm is generated because of a failure.
• alarm cleared — The alarm has been cleared by using a command.
• alarm resolved — The filesync that was previously failing is now no longer failing. The
latest filesync has succeeded.
The alarm text also includes the type of the server and the name of the fileset. The name of the
fileset is taken from the fileset configuration file, that is /etc/opt/ecs/filesync.conf. The
following are the different types of server:
• DUP
• ESS
• LSP
Proposed Solution
Go to the Avaya Support website at http://support.avaya.com to open a service request.
GW_ENV (Gateway Environment)

For the G650 gateway, Communication Manager generates SNMP traps to collect the threshold
exception data for the following events:
• Jitter
• Packet Loss
• Round-trip Delay
Communication Manager does not generate any alarms for these events. However,
Communication Manager generates a warning and sends the warning to the Fault and
GW_ENV (Gateway Environment)
Performance Management (FPM) or the Secure Intelligent Gateway (SIG) or both for Managed
Services. The warning message string includes the following information:
• Event Type (for example, Jitter, Packet Loss, and Round-trip Delay)
• Time Stamp of exception (in the month/day/hour:min:sec format)
• Board Type (TN2302 or TN2602)
• Board Location (5 alphanumeric characters)
• Peak threshold level/amount (in decimal notation) for the exceeded threshold
GW_ENV alarms
The following alarms apply to the G450 media gateway.
Table 6: GW_ENV Alarms

1 See GW_ENV Event ID 1 on page 37.
GW_ENV Event ID 1
Alarm level MAJ
Alarm text AvEntFanFlt - Fan fault
GW_ENV Event ID 2
Alarm level MAJ
Alarm text AvEnt48vPwrFlt - 48v Power fault
GW_ENV Event ID 3
Alarm level MAJ
Alarm text AvEnt48vPwrFlt - 48v Power faultAvEnt5vPwrFlt - 5v Power

fault
GW_ENV Event ID 4
Alarm level MAJ
Alarm text AvEnt3300mvPwrFlt - 3300 mv Power fault
GW_ENV Event ID 5
Alarm level MAJ
GW_ENV Event ID 6
Alarm level MAJ
GW_ENV Event ID 7
Alarm level MAJ
GW_ENV Event ID 8
Alarm level MAJ
Alarm text AvEntAmbientTempFlt - Ambient temperature fault
GW_ENV Event ID 9
Alarm level MAJ
_LX (Linux)
Alarm text avEntPhyChFruRemoval - Field replaceable unit removal
GW_ENV Event ID 10
Alarm level MAJ
Alarm text avEntPhyChFruPsuFlt - Power supply fault.
_LX (Linux)
The following table describes the server alarms for Linux and the related troubleshooting
procedures.
Table 7: LX Server Alarms

3 See LX Event ID 3 on page 39.
6 See LX Event ID 6 on page 40
LX Event ID 3
Alarm level WRN
Alarm text OVERLOAD CONTROL LEVEL 1
Cause
The average CPU occupancy for the last 20 seconds exceeded 92.5%. New call originations from
either stations or trunks are denied until the average CPU occupancy drops below 92.5% for at
least 30 seconds.
LX Event ID 4
Alarm level WRN
Alarm text OVERLOAD CONTROL LEVEL 2
Cause
The average CPU occupancy for the last 30 seconds exceeded 92.5%. All new call originations
and terminations are denied until the average CPU occupancy drops below 92.5% for at least 30
seconds.
LX Event ID 5
Alarm level WRN
Alarm text corevector set
LX Event ID 6
Alarm level WRN
Cause
The system firewall might not be running on the system.
Caution:
Not having a fully functional system firewall is a serious security risk.
Proposed Solution
Restart iptables by issuing the following command: root: systemctl status
nftables.service
LX Event ID 7
Alarm level WRN
Cause
The system firewall might not be running on the system.
Caution:
Not having a fully functional system firewall is a serious security risk.
Proposed Solution
Restart iptables6 by issuing the following command: root: systemctl status
nftables.service
LX Event ID 10
Alarm level WRN
Login alarms
Cause
One or more remote key servers are unreachable.
LX Event ID 11
Alarm level MIN
Cause
All remote key servers are unreachable.
LX Event ID 50
Alarm level MAJ
Alarm text DEMO CERTIFICATE IDENTIFIED
Cause
Post migration, if demo certificate is detected, then an alarm is raised against source "_LX"
as new Event ID 50. This alarm is resolved after the demo certificate is replaced with System
Manager certificate or third-party CA certificate for Web Server's ID.
Login alarms
The system monitors access to the server and alarms suspicious activity. The following table lists
the Login alarms and their related troubleshooting procedures.
For S8300E Server, see S8300E Server Login Alarms.
Table 8: Login Alarms

1 See Login Event ID 1 on page 42.
10, 11, 12, See Login Event IDs 10, 11, 12, and 13 on page 43.
and 13
Login Event ID 1
Alarm level WRN
Cause
Successful Communication Manager login.
Login Event ID 2
Alarm level MIN
Alarm text SAT_auth:Login for [inads] invalid password
Proposed Solution
1. Verify the alarm:
a. From SMI, select Current Alarms.
2. Incorrectly typing a login sequence causes this alarm. Enter almclear -n #id to clear
the alarm.
3. If this alarm occurs frequently, it may indicate a security threat. Notify the customer.
Login Event ID 3
Alarm level WRN
Cause
Successful Linux login.
Login Event ID 5
Alarm level MAJ
Alarm text Probation interval for login ends – lockout interval begins
Cause
This alarm may indicate a security threat. Notify the customer.
Proposed Solution
Using a services login, enter the command userlock -s on the Linux command line. This will
display all active logins in the system, the number of failed logins, and whether the incorrect login
attempt that raised the alarm is currently locked out.
S8300 Servers login alarms
Login Event ID 6
Alarm level WRN
Cause
Lacfile missing.
Login Event ID 7
Alarm level MAJ
Cause
Lacfile error - corrupt or expired authentication data.
Login Event ID 8
Alarm level MAJ
Cause
Access denied. Linux login failure. Access through illegal port.
Login Event IDs 10, 11, 12, and 13

Alarm level MIN
Alarm text Login for [linux] – failed – password check
Cause
A login attempt to access the Linux command line of a server failed.
Proposed Solution
1. Verify the alarm:
a. From SMI, select Current Alarms.
2. Incorrectly typing the login sequence causes this alarm. Enter almclear -n #id to clear
the alarm.
3. If this occurs frequently, it may indicate a security threat. Notify the customer.
S8300 Servers login alarms

The following table lists the S8300 Servers login alarms and their troubleshooting procedures.
Table 9: S8300 Server Login Alarms

1 See Event ID 1 on page 44.
Event ID 1
Alarm level WRN
Proposed Solution
1. Using the web interface, select View Current Alarms.
2. Notify the customer.
Event ID 2
Alarm level WRN
Proposed Solution
1. Using the Web Interface, select View Current Alarms.
Event ID 3
Alarm level MIN
Cause
Security violation.
Proposed Solution
Event ID 4
Alarm level MIN
Cause
Security violation.
_PE (Processor Ethernet) alarms
Proposed Solution
1. Using the Web Interface, select View Current Alarms.
Event ID 5
Alarm level MIN
Cause
Security violation.
Proposed Solution
_PE (Processor Ethernet) alarms

The _PE Processor Ethernet alarms are raised on servers running the duplex OVA.
The following table lists Processor Ethernet alarms and the related troubleshooting procedures.
Table 10: PE alarms

_PE 1 See _PE 1 Minor alarm: PE Health Check device is not responding on page 45.
_PE 2 See _PE 2 Minor alarm: PE on the other server is not responding on page 46.
_PE 3 See _PE 3 Major alarm: Processor Ethernet service is down on page 46.
_PE 4 See _PE 4 Minor alarm: PE Priority configuration mismatch between servers on page 47.
_PE 1 Minor alarm: PE Health Check device is not responding

MO name in log _PE 1
Alarm level MIN
Alarm text Can't ping the PE Health Check device.
Cause
Processor Ethernet (PE) Health Check device is not responding. Cannot ping the PE Health
Check device.
Proposed Solution
1. Log on to Communication Manager SMI.
2. From the Installation menu, click Configure Server. The Configure Server wizard opens.
3. On the Configure Interfaces screen, verify if IP address for PE Health Check is set to the
gateway address.
Execute the Ping diagnostics test to verify that the endpoint used for the PE Health Check
device (the gateway) responds to a ping request. For more information about the Ping
diagnostics test, see the SMI Help.
_PE 2 Minor alarm: PE on the other server is not responding

Alarm level MIN
Alarm text Can't ping the other server over the network used by the
PE Interface.
Cause
Processor Ethernet (PE) on the other server is not responding. Cannot ping the other server over
the network used by the Processor Ethernet interface.
Proposed Solution
1. Log on to Communication Manager SMI.
2. Click the Administration tab and select Server (Maintenance).
3. On the left navigation menu, click Status Summary. The system displays Status Summary
screen.
4. Verify that the other server in the duplicated server pair is running and that the Processor
Ethernet status is not Down.
a. If the other server in the duplicated server pair is not running, the status of Mode is
Not Ready and the display of items such as Alarms are blank.
b. If he Processor Ethernet status is not Down, run the troubleshooting procedures for
the alarms on the other server.
Execute the Ping diagnostic test to verify that the other server responds to a ping test.
If it does not, execute the Ping diagnostics test from the other server to verify that it is
connected to the corporate LAN.
_PE 3 Major alarm: Processor Ethernet service is down

Alarm level MAJ
Alarm text Can't ping the device used for the PE Health Check or the
IP interface used for the PE on the other server.
SME (Server Maintenance Engine)
Cause
Processor Ethernet service is down. Cannot ping the PE Health Check device and the IP interface
used for the PE on the other server.
Proposed Solution
1. Run the tests listed for the alarms associated with _PE 1 and _PE 2.
2. Verify if the server is connected to the corporate LAN.
3. If NIC alarms are present, follow the troubleshooting procedures for those alarms. For
more information, see Verify NIC Options Test (#1511) in Maintenance Alarms for Avaya
Aura® Communication Manager, Branch Gateways Servers.
4. Verify that the corporate LAN is working.
_PE 4 Minor alarm: PE Priority configuration mismatch between

servers
Alarm level MIN
Cause
The PE Interchange Priority setting on the Configure Interfaces page of the SMI of one of the
servers of a duplicated pair of server does not match the PE Interchange Priority setting on the
Configure Interfaces page of the SMI of the other server.
Proposed Solution
1. On the Status Summary screen of SMI, verify that the PE Interchange Priority setting
on the active server is the same as the PE Interchange Priority setting on the standby
server.
2. On the Configure Interface screen of SMI that displays the incorrect value, change the
incorrect value of the PE Interchange Priority setting.
Note:
Make sure that the server on which you are changing the settings on the Configure
Interface screen is on the standby server.
SME (Server Maintenance Engine)

The Server Maintenance Engine (SME) is a Linux process which provides error analysis, periodic
testing, and demand testing for the server.
The following table lists the Service Maintenance Engine alarms and the related troubleshooting
procedures.
Table 11: SME Alarms

1 See SME Event ID 1 on page 48.
2 See SME Event ID 2 on page 49.
SME Event ID 1
Alarm level MAJ
Alarm text Far end alarm service is down
Cause
No remote alarm service is available. The other server is unable to report alarms due to a failure
of either the GMM or its administered reporting mechanisms (SNMP).
Proposed Solution
1. Look for any GMM failures on the other server, either using the:
a. From the Web interface, select Diagnostics > View System Logs > Watchdog
Logs.
b. From the Linux command line, enter logv -w or by examining the /var/log/ecs/
wdlog log file.
2. If a GMM failure was found:
a. Check if the GMM application is active:
• From the Web interface, select View Process Status.
• From the Linux command line, enter statapp.
b. If the GMM application is active, continue with Step 3.
If the GMM application is not active, try to restart this application by entering start
-s GMM on the Linux command line.
c. If the GMM application restarts successfully, continue with Step 4.
If the GMM application fails to restart, go to the Avaya Support website at http://
3. If a GMM failure was not found, check if alarm reporting failed by searching for the string
snd2Inads in the trace log:
a. Select View System Logs diagnostic and Logmanager Debug trace.
b. Specify the event range for the appropriate time frame.
c. Match the snd2Inads pattern.
b. From the Linux command line, enter logv -t ts.
4. Test the administered reporting mechanisms by entering testinads on the Linux
command line.
STD (Standard SNMP Traps)
5. Once the alarm is resolved, manually clear the alarm:

Clear.
SME Event ID 2
Alarm level WRN
Cause
For security only. If the IP address in the trap does not match UPS translations, this server is
receiving a trap from an illegal source.
No action is needed.
STD (Standard SNMP Traps)

The following table lists STD traps and the related troubleshooting procedures.
Table 12: STD Alarms
Event ID Description
1 See STD Event ID 1 on page 54 on page 49.
2 See STD Event ID 2 on page 54 on page 49.
3 See STD Event ID 3 Alarm type ACT on page 55 on page 50.
3 See STD Event ID 3 Alarm type RES on page 55 on page 50.
STD Event ID 1
Alarm level MIN
Alarm type ACT
Alarm text "coldStart" - Agent Up with Possible Changes
Cause
A coldStart trap indicates that the entity sending the protocol (SNMPv2) is reinitializing itself and
this reinitialization process can either alter the agent configuration or entity implementation.
STD Event ID 2
Alarm level MIN
Alarm type ACT
Alarm text “warmStart" - Agent Up with No Changes
Cause
A warmStart trap indicates that the entity sending the protocol (SNMPv2) is reinitializing itself
and this reinitialization process keeps both the agent configuration and the entity implementation
intact.
STD Event ID 3 Alarm type ACT

Alarm level MIN
Alarm type ACT
Alarm text "linkDown" - Agent Interface Down
Cause
A linkDown trap indicates that the entity sending the protocol (SNMPv2) recognizes a failure in
one of the communication links represented in the agent configuration. The data passed within the
event is:
• The name and value of the ifIndex instance for the affected interface.
• The name of the interface can be retrieved via an snmpget of .1.3.6.1.2.1.2.2.1.2.INST,
where INST is the instance returned with the trap. The state is indicated by the included
value of ifOperStatus.
STD Event ID 3 Alarm type RES

Alarm level MIN
Alarm type RES
Alarm text "linkUP" - Agent Interface Up
Cause
A linkUp trap indicates that the entity sending the protocol (SNMPv2) recognizes that one of the
communication links represented in the agent configuration has come up. The data passed within
the event is:
• The name and value of the ifIndex instance for the affected interface.
• The name of the interface can be retrieved via an snmpget of .1.3.6.1.2.1.2.2.1.2.INST,
where INST is the instance returned with the trap. The state is indicated by the included
value of ifOperStatus.
SVC_MON (Service Monitor)

SVC_MON is a server process, started by Watchdog, that monitors Linux services and processes.
It also starts up threads to communicate with a hardware-sanity device.
The following table lists SVC_MON alarms and the related troubleshooting procedures.
Table 13: SVC_MON Alarms

2 See SVC MON Event ID 2 on page 51.
6 See SVC MON Event ID 6 service rsyslog on page 52.
6 See SVC MON Event ID 6 service dbgserv on page 53.
SVC MON Event ID 2

Alarm level MIN
Alarm text service atd could not be restarted
Cause
The Linux at daemon is down. Scheduled services such as session cleanup or daily filesync will
not work.
Proposed Solution
Enter service atd restart from the /sbin directory to restart the at daemon, and see
Resolving SVC MON Event.
SVC MON Event ID 3

Alarm level MIN
Alarm text service crond could not be restarted
Cause
The Linux cron daemon is down. Periodic services such as session cleanup or daily filesync will
not work.
Proposed Solution
Enter /sbin/service cron restart from the /sbin directory to restart the cron daemon,
and see Resolving SVC MON Event.
SVC MON Event ID 4

Alarm level MIN
Alarm text service xinetd could not be restarted
Cause
The Linux internet server daemon is down. Networking services will not work.
Proposed Solution
Enter /sbin/service inet restart from the /sbin directory to restart the inet daemon, and
see Resolving SVC MON Event.
SVC MON Event ID 6 service rsyslog

Alarm level MIN
Alarm text service rsyslog could not be restarted
Cause
Linux syslog service is down. Event logging to syslog and alarm generation fails.
Proposed Solution
Enter /sbin/service rsyslog restart from the /sbin directory to restart the syslog
service, and see Resolving SVC MON Event.
SVC MON Event ID 5

Alarm level MIN
Alarm text service xintetd could not be restarted
Cause
The Linux network time protocol daemon is down. The server clock and recently logged time
stamps may be inaccurate.
Proposed Solution
Enter /sbin/service xntpd restart from the /sbin directory to restart the xntpd daemon,
SVC MON Event ID 6 service dbgserv

Alarm level MIN
Alarm text service dbgserv could not be restarted
Cause
Debug server is down, and the Gemini debugger may not work. If this service stops running,
debugging of a currently functional server is prevented, but the normal operations of a server are
not affected.
Proposed Solution
Enter /sbin/service dbgserv restart from the /sbin directory to restart the dbgserv
service, and see Resolving SVC MON Event.
SVC MON Event ID 7

Alarm level MIN
Alarm text service prune could not be restarted
Cause
The prune service is not running. The partition usage of the hard disk is not being monitored or
cleaned.
Proposed Solution
Enter /sbin/service prune restart from the /sbin directory to restart the prune service,
SVC MON Event ID 8

Alarm level MIN
Alarm text service ntpd could not be restarted
Cause
The hypertext transfer protocol daemon is down. The web interface will not work.
Proposed Solution
Enter /sbin/service httpd restart from the /sbin directory to restart the http daemon,
Resolving SVC MON Event

Procedure
1. If the daemon or the service restarts successfully, manually clear the alarm:
• From the Web interface, select Current Alarms and the appropriate alarm, and click
Clear.
• From the Linux command line, enter almclear -n #id.
If the daemon or the service fails to restart, go to the Avaya Support website at http://
a. Enter grep svc_mon /var/log/messages to determine why the daemon failed to
restart.
Caution:
The following procedure causes a brief service outage and must be executed only
at the convenience of the customer.
b. If the output of the grep command does not help:
• For duplicated servers, enter server to verify that the suspected server is the
standby. If necessary and at the convenience of the customer, enter server -if
to force a server interchange.
• For non-duplicated servers, proceed to Step d.
c. For duplicated servers, reboot the standby server:
• From the Web interface, select Shutdown This Server.
• From the Linux command line, enter /sbin/shutdown -r now.
d. For non-duplicated servers, reboot the server:
• From the web interface, select Shutdown This Server.
• From the Linux command line, enter /sbin/shutdown -r now.
2. If rebooting the standby does not help or if the problem recurs, go to the Avaya Support
website at http://support.avaya.com to open a service request.
TGP-USG (Trunk Group Usage)

The Trunk Group Usage alarm is observed on SIP type trunk groups when the administered
threshold value for incoming or outgoing calls has been reached.
TM (Translation Manager)
Note:
You can view the administered threshold value on the SIP trunk group screens only when
MLPP and ASAC are enabled on the system.
The following table lists the TGP-USG alarms and the related troubleshooting procedures.
Table 14: TGP-USG alarms

1 See TGP-USG Event ID 1 on page 55.
2 See TGP-USG Event ID 2 on page 55.
TGP-USG Event ID 1
Alarm level WRN
Cause
The administered threshold value for incoming calls has been reached.
Proposed Solution
Ensure that the number of incoming calls is less than the administered threshold value.
TGP-USG Event ID 2
Alarm level WRN
Cause
The administered threshold value for outgoing calls has been reached.
Proposed Solution
Ensure that the number of outgoing calls is less than the administered threshold value.
TM (Translation Manager)
The Translation Manager monitors the ability of the server to read Communication Manager
translations. The following table lists the TM alarms and the related troubleshooting procedures.
Table 15: TM Alarm

1 See TM Event ID 1 on page 56.
TM Event ID 1
Alarm level MAJ
Alarm text Cannot read translations
Cause
Server could not read translations. Usually, indicates a failure loading translations, but can also
infrequently occur on a running system.
Duplicated servers: The servers spontaneously interchanged.
S8300: The server rebooted.
Proposed Solution
1. Check the integrity of the translation files xln1 and xln2 in /etc/opt/defty, and verify
that they are of non-zero length.
2. From the /etc/opt/defty directory, enter the Linux command cksum xln1 xln2
to verify that the checksums of the files are identical.
3. Duplicated servers: Copy the translation files from the backup or the other server.
4. S8300: Copy the translation files from the backup.
5. If Steps 1 to 3 do not help, load the system with null translations.
6. If the system does not start, go to the Avaya Support website at http://support.avaya.com
to open a service request.
7. After the error is resolved, manually clear the alarm:
Clear.
UPG (Upgrade)
The UPG raises an alarm if the upgrade was not made permanent within a certain amount of time
after the upgrade.
Table 16: UPG Alarms

1 See UPG Event ID 1 on page 56.
UPG Event ID 1
Alarm level MAJ
VHEAP (Virtual Memory Heap)
Cause
The upgrade was not made permanent within two hours. No commit error.
Proposed Solution
Make the upgrade permanent by using the web interface. Select Server Upgrade > Manage-
Updates > Commit..
VHEAP (Virtual Memory Heap)

The Virtual Memory Heap (VHEAP) process is a reserved memory area where individual data
elements are dynamically allocated and released as needed. Alarms are raised when the memory
usage approaches the reserved capacity. For example, when the usage exceeds a specified
threshold, an alarm is raised.
The following table lists the virtual memory heap alarms and the cause.
Table 17: VHEAP Alarms

1 See VHEAP Event ID 1 on page 57
VHEAP Event ID 1
Alarm level MAJ
Alarm text conn_m heap usage exceeds 90 percent (possible memory leak)
Cause
CONN_M (Connection Manager) VHEAP usage exceeds the alarm threshold, which may indicate
a possible memory leak.
VHEAP Event ID 2
Alarm level MAJ
Alarm text suser_m shadowed heap usage exceeds 90 percent (possible

memory leak)
Cause
SUSER_M (Station User Manager) shadowed VHEAP usage exceeds the alarm threshold, which
may indicate a possible memory leak.
VHEAP Event ID 3
Alarm level MAJ
Alarm text suser_m unshadowed heap usage exceeds 90 percent (possible

memory leak)
Cause
SUSER_M (Station User Manager) unshadowed VHEAP usage exceeds the alarm threshold,
which may indicate a possible memory leak.
WD (Watchdog)
Watchdog is a server process that performs the following:
• Creates other Communication Manager processes
• Monitors process status
• Recover process failures
Watchdog also communicates with a hardware-status check device. For alarm-related information
about these services, see SVC_MON (Service Monitor).
The following table lists the Watchdog alarms and the related troubleshooting procedures.
Table 18: _WD Alarms
Event ID Link to Description

4 S8300 See WD Event ID 4 S8300D on page 59.
5 See WD Event ID 5 on page 60.
6 S8300E See WD Event ID 6 S8300D on page 61.
WD (Watchdog)
WD Event ID 4 S8300
Alarm level MAJ
Alarm text Application <name> (pid) TOTALLY FAILED
Cause
The application is present but cannot start. The application cannot start the maximum allowed
number of times. This alarm occurs with Event ID #20.
Proposed Solution
1. To verify the alarm, locate the application name or process ID (PID):
Logs.
wdlog log file.
2. If the application is not running, enter start -s application to start the application.
3. If the application starts successfully, continue with Step 7.
If the application fails to start, check the trace log to determine the reason why the
application fails to start:
a. Select View System Logs diagnostic, and Logmanager Debug trace.
c. Match the application PID as the pattern.
b. From the Linux command line, enter logv -t ts.
Locate a related core-dump file in /var/crash directly, and go to the Avaya Support
4. Check if the file named in the log exists and is executable.
To locate the executable file of the application, enter the Linux command:
ls -l /opt/ecs/sbin/appl
If the file is present, Linux returns a symbolic link to its location.
5. If the file is present:
a. Enter ls -l on the address of the symbolic link.
b. Check if the file has execute permissions. If the file does not have execute
permission, enter chmod +x to enable execution permission for the application.
If the file is not present, Linux has returned a null link.
c. Acquire the executable from the CD.
6. Enter start -s application to start the application.

Clear.
WD Event ID 5
Alarm level MIN
Alarm text WARNING: timeout waiting for reqsvr to initialize
Cause
During the boot process of each, the Watchd process of the server waits for up to two minutes for
its reqsvr (request server) thread to initialize. If the two-minute waiting interval elapses, this server
logs this alarm, and its boot process hangs. Meanwhile, if the other server boots subsequently, it
becomes the active server.
If a server hangs during boot process when this alarm occurs, the external symptoms of this alarm
resemble those of two other _WD alarms, #13 and #14. Therefore, you must carefully discriminate
between these three events.
Proposed Solution
1. To determine the cause of this problem:
a. Check if the Linux OS and the web interface are running, including the commands:
telnet, statapp, server, logv, cat, grep, tail, vi.
b. Check if the Watchdog application is active, but no other Communication Manager
software is running.
c. The almdisplay command displays no alarms, instead, the command returns the
message:
almdisplay: 4: Unable to connect to MultiVantage
Caution:
The following procedure causes a brief service outage and must executed only at the
convenience of the customer.
2. Go to the Avaya Support website at http://support.avaya.com to open a service request.
3. Enter server to check if the suspected server is the standby.
If necessary and at the customer convenience, enter server -if to force a server
interchange.
4. Reboot the standby server:
a. From the Web interface, select Shutdown This Server.
b. From the Linux command line, enter /sbin/shutdown -r now.
WD (Watchdog)
5. Once the standby server restarts, check if the Event ID #5 was logged:
Logs.
b. From the Linux command line, enter logv -w or by examining /var/log/ecs/
wdlog log file.
6. If rebooting the server does not help or if the problem persists, go to the Avaya Support
WD Event ID 6 S8300
Alarm level MAJ
Alarm text Application <name> (pid) not started, config parm errors
Cause
Watchdog cannot read its configuration file, /etc/opt/ecs/watchd.conf.
Proposed Solution
1. To verify the alarm, locate the name of the application process ID (PID):
Logs.
wdlog log file.
2. Retrieve a fresh copy of watchd.conf from the distribution.
3. Check if all the files listed in watchd.conf exists and are executable.
a. From the web interface, select Current Alarms and the appropriate alarm, and click
Clear.
WD Event ID 7 S8300
Alarm level MAJ
Alarm text Application <name> not started, parm file errors
Cause
Since an application’s specified location in watchd.conf is incorrect, Watchdog cannot start the
application.
Proposed Solution
a. From the web interface, select Diagnostics > View System Logs > Watchdog Logs.
wdlog log file.
To locate the executable file of the application, enter the Linux command:
If the executable is present, Linux returns a symbolic link to its location.
a. Enter ls -l on the symbolic link address.
b. Check if the file has execute permissions. If the file does not have execute
permissions, enter chmod +x to enable execution of the application.
If the file is not present, Linux has returned a null link.
c. Acquire the executable from the distribution.
4. Check if the string in watchd.conf is correct.
Clear.
WD Event ID 13
Alarm level MIN
Alarm text ERROR: could not dup socket fd in reqsvr.c, heartbeat thread
not created, errno=<x>
Cause
Booting application initiates.
Restarting application re-initiates heartbeating with Watchdog (see Event ID #5), the reqsvr
(request server) thread tries to create a duplicate socket for the heartbeating thread. This alarm
indicates that reqsvr canot create the socket. Meanwhile, if the other server is started, it becomes
the active server.
If the server hangs when this alarm occurs, the external symptoms of this alarm resemble those of
two other _WD alarms, #5 and #14. Therefore, carefully discriminate between these three events.
WD (Watchdog)
Proposed Solution
1. To determine the cause of this:
a. Check if Linux OS and the Web interface are running, including the commands:
b. Check if the Watchdog application and some other Communication Manager
processes are up:
c. If the GMM process is active, the almdisplay -v command shows the message
string of Event #13.
If the GMM process is not active, check if the Watchdog log shows the message
string:
• From the Web interface, select Diagnostics > View System Logs > Watchdog
Logs.
• From the Linux command line, enter logv -w or directly examine
the /var/log/ecs/wdlog log file.
Caution:
The following procedure causes a brief service outage and must executed only at
the convenience of the customer.
If necessary and at the convenience of the customer, enter server -if to force a server
interchange.
a. From the Web interface, select Shutdown This Server.
b. From the Linux command line, enter /sbin/shutdown -r now.
WD Event ID 14
Alarm level MIN
Alarm text ERROR in req2svr.p trying to create heartbeat thread,

errno=<x>
Cause
After the reqsvr (request server) creates a duplicate socket (see Event ID #13, it tries to create a
heartbeating thread. This alarm indicates that reqsvr cannot create the thread. Meanwhile, if the
other server is started, it becomes the active server.
If the server hangs when this alarm occurs, the external symptoms of this alarm resemble those of
two other _WD alarms, #5 and #13. Therefore, carefully discriminate between these three events.
Proposed Solution
1. To determine the cause of this problem:
a. Check if Linux OS and the Web interface are active including the commands:
b. Check if the Watchdog application is partially active and other Communication
Manager processes are active:
c. The almdisplay -v command shows the message string of Event #14.
Caution:
The following procedure causes a brief service outage and must executed only at
the convenience of the customer.
If necessary and at the convenience of the customer, enter server -if to force a server
interchange.
From the Web interface, select Shutdown This Server.
WD Event ID 15 S8300E
Alarm level MAJ
Alarm text Detected a rolling reboot
Cause
Watchdog has detected x number of Linux reboots within y minutes. The x and y parameters
configurable in /etc/opt/ecs/watchd.conf. Rolling reboots have a many possible causes.
Proposed Solution
1. To verify the alarm, locate the message, WARNING: Rolling reboot detected!!:
Logs.
b. From the Linux command line, enter logv -w or directly examine
WD (Watchdog)

3. Giving priority to Communication Manager errors, examine the Watchdog log from Step 1,
and determine which application failed.
4. Check if all the files listed in watchd.conf exists and are executable. Rolling reboots are
often caused by executables in unexpected locations.
5. If the files and their locations are valid, examine the trace log to determine the cause:
c. Match the rolling reboot pattern.
b. On the Linux command line, type logv -t ts.
WD Event ID 18 S8300E
Alarm level WRN
Alarm text Application <name> restarted. Retry <retry count>, New Pid:
<pid>
Cause
An application has failed, and Watchdog successfully restarted it.
Proposed Solution
a. From the Web interface, by select Diagnostics > View System Logs > Watchdog
Logs.
the /var/log/ecs/wdlog.
2. No corrective action necessary. Manually clear the alarm:
Clear.
b. From the Linux command line, enter almclear -n #id .
WD Event ID 19 S8300
Alarm level MIN
Alarm text Application failed unintentionally
Cause
Watchdog is shutting down the system down because an application failed to start correctly. The
application failed to start because of the following:
The file did not exist, similar to Event ID #7.

Required application parameters were missing or invalid in watchd.conf.
Proposed Solution
1. To verify the alarm, locate the message, Application num <#> (<application
path>) not started. Watchdog exiting NOW:
a. From the Web interface, select Diagnostics > View System Logs > Watchdog.
3. Check if the string in watchd.conf is correct.
4. If Step 2 and Step 3 are okay, investigate the trace log to see why the application fails,
either from the:
c. Match the application number as the pattern.
b. On the Linux command line, type logv -t ts
5. Once resolved, manually clear the alarm:
Clear.
Alarm level MAJ
Alarm text Application <name> (pid) TOTALLY FAILED
Cause
Application failed the maximum allowed number of times. This alarm usually occurs with Event ID
#4.
Proposed Solution
Logs.
WD (Watchdog)
c. Check if the application is running:

2. If the application is not running down, type start -s application to start the
application.
3. If the application starts, continue with Step 7.
If the application does not start, check the trace log to determine why the application failed
to start:
c. Match the application’s PID as the pattern.
4. To locate the executable file of the application, enter the command:
If the executable is present, Linux returns a symbolic link to its location.
a. Enter ls -l on the symbolic link’s address.
b. Verify that the file has execute permissions. If not, enter chmod +x to enable
execution of the application.
If the file is not present, Linux has returned a null link:
c. Acquire the executable from the CD.
Clear.
Alarm level MIN
Alarm text Application <name> (<pid>) terminated
Cause
Watchdog successfully shut down the named application, and if necessary, watchdog will restart
the application.
Proposed Solution
Logs.
b. From the Linux command line, enter logv -w.
2. On the standby server, look for occurrences of the stop command:
a. Select View System Logs.
b. Select Platform command history log.
c. Specify the Event Range for the appropriate time frame.
d. Match the Stop pattern.
b. From the Linux command line, enter listhistory.
3. If a stop command was inappropriately executed, prevent any future misuse of the stop
command.
Note:
From the system’s perspective, this is normal behavior. However, in terms of potential
service outage due to human error, this is irregular. Shutting down a server effectively
downgrades a duplex, high or critical-reliability system to an unsupported standard-
reliability system.
4. If listhistory shows no stop commands, Watchdog responded to abnormal internal
processes by shutting down the application.
Check the trace log for information about this application:
c. Match the application PID as the pattern.
Clear.
6. Check if the alarm persists. If the alarm persists, go to the Avaya Support website at http://
WD (Watchdog)
Alarm level MAJ
Alarm text Watchd high-monitor thread is rebooting the system
Cause
The Lo-monitor thread is missing heartbeats (cannot get CPU time). The Hi-monitor thread has
tried 3 times to recover the system by killing any infinitely looping processes. If the lo-monitor
thread does not heartbeat even after three CPU-occupancy profiles and recoveries, the Watchd
reboots the server.
Proposed Solution
1. To verify the alarm, look for messages containing the CPU profiling results and attempted
recoveries and messages stating that Watchd is rebooting the server:
Logs.
No corrective action is necessary. The server restarts by the time a technician analyzes the
system. A reboot clears the alarm and fixes problems with unresponsive software.
2. Check if the alarm persists. If the alarm persists, go to the Avaya Support website at http://
Alarm level MAJ
Alarm text Watchd’s high-monitor thread is stopping tickling of hw
Cause
The call of Event ID #23 to reboot the server was unsuccessfully invoked. A semaphore of the
Linux kernel is stuck. Once this alarm is raised, Watchd stops the HW sanity timer prompting HW
sanity watchdog to execute a hard reboot of the processor.
Proposed Solution
1. To check if the alarm occurred, look for messages that indicate stopping stopping the
tickling of the HW sanity timer and CPU occupancy profiling:
Logs.
• If the HW sanity watchdog successfully executes a hard reboot, the alarm clears.
This reboot fixes problems caused by unresponsive software.
If the HW sanity watchdog fails to execute a hard reboot, disengage and reengage the
power source of the server to release it from this condition and to clear the alarm.
2. If the alarm persists, go to the Avaya Support website at http://support.avaya.com to open
a service request.
WD Event ID 26
Alarm level MIN
Alarm text Watchd handshake error
Cause
If USB alarms are also present, this strongly points to a global SAMP or networking problem. This
error implies:
• The SAMP is missing.
• The SAMP is malfunctioning.
• The SAMP is not configured properly.
• The firewall on the server is not configured.
• The SAMP firmware is not correct for the Communication Manager version.
• The server Ethernet port is misconfigured.
Proposed Solution
1. Refer to the SAMP user guide for troubleshooting procedures.
WD Event ID 27
Alarm level MAJ
Alarm text Free memory on the system is low
Proposed Solution
To check if the alarm occurred, look for messages that indicate stopping the tickling of the HW
sanity timer and messages that indicate CPU occupancy profiling:
a. From the Web interface, select Diagnostics > View System Logs > Watchdog Logs.
b. From the Linux command line, enter logv -w or directly examine the /var/log/ecs/
wdlog log file.
Chapter 5: Denial Events
Denial events
Denial Events are logged in the Communication Manager denial event log. You can use the SAT
command display events and enter denial in the Category field to gain access to the denial
event log.
The following tables define and explain the information listed on the Events Report form. The
Event Type tables are grouped by denial event category and denial event number. The event
tables list:
• The number that identifies the event type. If the number defines different denial events in
different Communication Manager releases, that information is also listed. See Event type
number ranges on page 71.
• The event description text as displayed on the Events Report screen.
• An explanation of why the event was generated.
• The type of data in the Event Data 1 and Event Data 2 fields for each applicable event type,
when the data information is available. See Event data on page 72.
The following SAT commands are commands are used to view the denial events:
• display events
• list trace station
• list trace TAC
Available calling party number and calling party name associated with the call setup can be
viewed by using the list trace command.
Event type number ranges

The following table lists the event type number ranges that define the type and source of the
denial event.
Denial Events
Table 19: Denial event types and ranges
Number range Type/source of denial Reference

0 - 499 Call Processing Vector Call Processing Vector Events on page 118.
events
500 - 999 Group Manager Vector Group Manager Vector events on page 145.
events
1000 - 2299 Call Process Call Process denial events (1001 - 1172) on
page 147.
1000 - 1299 Call Process, reorder Call Process denial events (1001 - 1172) on
page 147 and Call processing denial events (1225
- 1899) on page 168.
1164, 1167, 1173 - Call Process, ISDN, IP, SIP ISDN, IP, and SIP denial events on page 164.
1224
1300 - 1899 Call Process, intercept Call processing denial events (1225 - 1899) on
page 168.
1900 - 1906 User Manager process User manager denial events on page 222.
1907 - 2079 IP IP Denial Events on page 223.
2021-2299 Call Process Call Processing Denial Events (2021 - 2299) on
page 236.
2300 - 2399 Connection Manager Connection manager denial events on page 261.
process
2400 - 2499 Dial Plan Manager process Dial plan manager denial events on page 267.
3000 - 3099 Data Manager process Data manager denial events on page 269.
3101 - 3200 Dial Access Plan process Dial access plan denial events on page 269.
3201 - 3299 Meet-me Conference Meet-me conference denial events on page 270.
process
3400 - 3499 Data Error (corruption) Data error denial events on page 271.
process
3500 - 3599 Contact Closure process Contact closure denial events on page 273.
3600 - 3604 Survivable Core Server Survivable core server denial events on page 273.
process
3700 - 3799 User Manager User Manager Denial Events (3700 - 3915) on
page 274.
5000 - 5003 Call Processing Call processing denial events (5000 - 5099) on
page 282.
Event data
Use Event Data information to avoid incorrect translation or mismatched provisioning or both.
Event Data contains the information for:
• Internal User ID (UID) of a component involved in the call (station, IP User, gatekeeper)
Denial events
• Product ID
• Object ID
• IP address
• Extension
• IP address involved in the call.
• TTI state.
• Numeric reason code explained in the tables in this chapter.
• Numeric code showing the Cause Value, Cause Value Diagnostic, and Location Code for the
event.
Event data 2
Event Data 2 sometimes contains the following data from the denial event:
• Cause Value (CV). This data is mandatory.
• Cause Value Diagnostic (DIAG). This data is optional.
• Location Code (LOC). This data is optional.
This information (DIAG/LOC/CV) is coded as a 32-bit hexadecimal number, divided into 8-bit
fields.
• The Cause Value is the last two digits in the hexadecimal number.
• The Location Code is the two digits to the left of Cause Value in the hexadecimal number.
See Location codes on page 75.
• The Diagnostic Code is the two digits to the left of the Location Code in the hexadecimal
number.
• The first two digits are not used.
Table 20: Event Data 2 layout
8 bits 8 bits 8 bits 8 bits

NOT USED Diagnostic Code Zero + Location Code in lower 4 bits Cause Value(CV)
(DIAG) (optional) (LOC) (optional) (required)
The following example displays Denial Event 1178 with Event Data 1 and Event Data 2.
display events denial Page 1 of 1

EVENTS REPORT
Event Event Event Event First Last Evnt
Type Description Data 1 Data 2 Occur Occur Cnt
1178 Normal Call Clearing 0x64 0x429 01/09/09:53 01/09/09:53 1
Interpreting Event data 2 cause value information

About this task
To interpret Event data 2 cause value information, look at the example given in Event data 2.
Denial Events
Event Data 2 value, 0x429, includes the following information:

• Cause Value 0x29.
• Location Code 0x4.
• Diagnostic Code 0x00 (not provided for this denial event).
Procedure
1. Convert the hexadecimal number provided in Event Data 2 to three binary numbers.
Each binary number consists of eight bits. See Event data 2 conversion example on
page 74 for an example of the hexadecimal number 0x429, and .Hexadecimal, decimal,
and binary equivalents on page 75 for the binary equivalents for individual digits.
2. Add up the decimal weights that have a 1 for each of the 8-bit segments.
• Convert Cause Value 0x29 to decimal and calculate the total.
Cause Value (Bits 1 - 8): 1 +8 + 32 = 41. This is Cause Value 41.
• Convert Location Code 0x4 to decimal and calculate the total.
Location Code (Bits 9 - 16): 4 = 4. This is Location Code 4.
• Convert Diagnostic Value 0x00 (Bits 17 - 24): 0 = 0.
Diagnostic Code is 0, not provided for this example denial event.
3. Use the information to explain of the Event Data 2 information.
• Cause Value 41 = Temporary Failure. See Cause values.
• Location Code 4 = Remote Network/Public Network Serving Remote User (the Local
Exchange Carrier at the far end of the call). See Location codes on page 75.
Event data 2 conversion example
Table 21: Event Data 2 conversion example
Diagnostic Code Location Code Cause Value

Event Data 2
0 0 0 4 2 9
Binary number
0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 0 1 0 0 1
Decimal weight of each digit position
8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1
Decimal weight of the binary positions for each 8-bit field
128 64 32 16 8 4 2 1 128 64 32 16 8 4 2 1 128 64 32 16 8 4 2 1
Bit position
24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Denial events
.Hexadecimal, decimal, and binary equivalents

Table 22: Hexadecimal, decimal, and binary equivalents
Hex Decimal Binary Hex Decimal Binary

0 0 0000 8 8 1000
1 1 0001 9 9 1001
2 2 0010 A 10 1010
3 3 0011 B 11 1011
4 4 0100 C 12 1100
5 5 0101 D 13 1101
6 6 0110 E 14 1110
7 7 0111 F 15 1111
For the Denial Events that show Cause Value, Location Code, and Diagnostic Code information,
see ISDN, IP, and SIP denial events on page 164.
Location codes
Use the location information of Event Data 2 to identify the origin of Cause Value and network
location where the called number was not recognized.
Table 23: Location Code definitions
Location Definition
Code
0 User.
1 Private Network Serving Local User. This is the local PBX or telephone system on the Called
Party premise.
2 Public Network serving the Local User. This is the central office to which the PBX is directly
connected.
3 Transit network. For example, the long distance network to which the call was passed by the
Local Exchange Carrier (LEC).
4 Public Network Serving Remote User. This is the Local Exchange Carrier (LEC) at the far
end of the call.
5 Private Network Serving Remote User. This is the remote PBX or telephone system on the
Called Party premises.
7 International.
A Network beyond inter-networking point.
Denial Events
Transmission Protocols
The meaning of the Denial Event Data information differs depending on the type of protocol used
for the call. The transmission protocol for the system is defined on the DS1 screen (add/change/
display ds1 location) by:
• The numeric country code value in the Protocol field.
• The letter value for the protocol version in the Protocol Version field.
Table 24: Country Codes and Transmission Protocols
Country Code – Country Protocol Supported B- Inter-working

Protocol Version ChannelMai Message
nt.
Message
1-a US-Canada AT&T TR 41449 / 41459 SERVICE PROGRESS
1-b US Bellcore TR1268;NIUF.302; ANSI RESTART PROGRESS
T1.607
1-c US-Canada Nortel A211 AT&T TR SERVICE PROGRESS
4449/41459 (with Layer 3 timers
adjusted)
1-d US Bellcore TR3268 SERVICE PROGRESS
2 Australia AUSTEL TS014.1; Telcom RESTART PROGRESS
Australia TPH 1856
3 Japan NTT INS-NET RESTART ALERTING
4 Italy ETS 300 102 RESTART PROGRESS
5 Netherlands ETS 300 102 RESTART PROGRESS
6 Singapore ETS 300 102 RESTART PROGRESS
7 Mexico ETS 300 102 RESTART PROGRESS
8 Belgium ETS 300 102 RESTART ALERTING
9 Saudi Arabia ETS 300 102 RESTART PROGRESS
10-a UK ETS 300 102 (Connect to RESTART PROGRESS
DASS II/DPNSS through external
converter)
10-b UK ETS 300 102 (Mercury) British NONE ALERTING
Telcom ISDN 30
11 Spain Telefonica ISDN Spec RESTART PROGRESS
12-a France VN4 (French National PRI) NONE ALERTING
12-b France Modified ETS 300 102 according NONE ALERTING
to P10-20 (Euronumeris)
13-a Germany FTZ 1 TR 6 (German National NONE ALERTING
PRI)
13-b Germany ETS 300 102 RESTART ALERTING
Table continues…
Denial events
Country Code – Country Protocol Supported B- Inter-working

Protocol Version ChannelMai Message
nt.
Message
14 Czech Republic / ETS 300 102 RESTART PROGRESS
Slovakia
15 Russia (CIS) ETS 300 102 RESTART PROGRESS
16 Argentina ETS 300 102 RESTART PROGRESS
17 Greece ETS 300 102 RESTART PROGRESS
18 China ETS 300 102 RESTART PROGRESS
19 Hong Kong ETS 300 102 RESTART PROGRESS
20 Thailand ETS 300 102 RESTART PROGRESS
21 Macedonia ETS 300 102 RESTART PROGRESS
22 Poland ETS 300 102 RESTART PROGRESS
23 Brazil ETS 300 102 RESTART PROGRESS
ETSI-a Europe, etc. ETS 300 102 RESTART PROGRESS
ETSI-b ETS 300 102 NONE PROGRESS
QSIG Private network ETS 300 102 RESTART PROGRESS
Cause values
The Event Data 2 field on the display events screen sometimes contains Cause Value
information (DIAG/LOC/CV). This information is used to identify the Cause Value for each denial
event. Cause Values classes, their meaning and interpretations, and associated translations are
as follows:
Cause value classes
Table 25: Cause Value classes and ranges
Number range Cause Value class

empty to 33 Normal class cause values on page 77
• 12, 14, 15, 24 unassigned
34 to 48 Resource-unavailable class cause values on page 90
• 36, 48 unassigned
49 to 64 Service or Option-not-available class cause values on page 94
• 55, 60, 64 unassigned
65 to 80 Service or Option-not-implemented class cause values on page 100
• 67, 68, 71-78, 80 unassigned
81 to 95 Invalid-message class cause values on page 103
Table continues…
Denial Events
Number range Cause Value class

• 92-94 unassigned
96 to127 Protocol-error class cause values on page 107
• 104-109, 116-126 unassigned
Normal class cause values

Cause value (empty)
[] Normal call clearing (1TR6: AT&T ISDN Protocol)
Cause
The call is disconnected normally by users at either end.
This cause value has end-to-end significance. Communication Manager returns this cause value
to the user who has originated the call.
Cause value 00
[0x0/0x80] Normal disconnect
Cause
The call is disconnected normally by users at either end. Most equipment uses Cause value 16 on
page 84 to report normal disconnect.
Cause value 01
[0x1/0x81] Unassigned (Unallocated number)/ Invalid Call Reference Value (CRV) (1TR6:
AT&T ISDN Protocol)
Cause
The call cannot be completed because the number requested in the SETUP message is not
assigned or allocated by the ISDN network.
to the user who originated the call.
See also Cause value 22 on page 86 and Cause value 56 on page 96.
Proposed Solution
1. Check if any prefix or service value is missing from the cause value numbers.
2. Check Cause Value Information Element (LOC). See Location codes on page 75.
3. Check Communication Manager administration.
a. Dial-plan/Location: The administration of an incorrect home NPA causes an incorrect
code conversion.
Denial events
b. IXC: The administration of an incorrect IXC matching pattern or a dial plan without an
IXC matching pattern causes incorrect IXC manipulation.
c. AAR/ARS digit conversion: An incorrect digit string is substituted. The call is routed to
the wrong network and over the wrong route pattern. Further conversion is needed,
but the dial string is restricted from further conversion.
d. AAR/ARS digit analysis: Call type is incorrect for the call made with an incorrect
number type or incorrect number plan information or both, or the call type prevents
code conversion. Call routes to an incorrect route pattern with incorrect digit
manipulation and/or code conversion.
e. Automatic Route Selection (ARS) toll analysis: An incorrect toll or no-toll classification
causes incorrect code conversion at the route pattern.
f. Route pattern: Incorrect entries in the NPA, prefix mark, and toll list/prefix mark fields
cause incorrect code conversion. Incorrect number of digits are deleted or incorrect
digits are added. IXC or international code digits and user-dialed IXC code fail to
parse or IXC routes the call to the wrong interexchange carrier.
g. Trunk Group: An incorrect service or feature is specified for the call made on a CBC
trunk group preference. The dialed number format is changed to an incorrect number
format.
Cause value 02
[0x2/0x82] No route to specified transit network/ Calling party off hold (5ESS: 5 Electronic
Switching System)
Cause
The ISDN service provider’s equipment cannot route the call through the specified network. The
network either does not exist or is incompatible with the equipment of the ISDN service provider.
This cause value has local significance only. The ISDN network between the user and the
equipment generating the cause value sends:
• A no cause indication through the network
• A more generic cause value through the network
Since this cause value has only local significance on tandem calls, Communication Manager maps
it to Cause value 31 on page 89 instead of passing it back through the network.
Proposed Solution
1. Check the diagnostic information (DIAG) for the transit network identity of the unreachable
network. See Event data 2 on page 73.
3. Check that the call type (data, voice, fax) can be routed between the ISDN networks
serving both ends of the call.
4. Check that the bearer capabilities of the call are acceptable to the ISDN network serving
both ends of the call.
Denial Events

a. AAR/ARS digit analysis: Call type is incorrect for the call made with an incorrect
number type or incorrect number plan information or both, or the call type prevents
code conversion. Call routes to an incorrect route pattern with incorrect digit
manipulation and/or code conversion.
b. Route pattern: Incorrect digits or IXC were inserted. Incorrect number of digits
were deleted. An incorrect ITC or BCIE or both has affected the encoding of the
SETUP message bearer capability. An incorrect service or feature specified for the
preference. The number format specified is incorrect for the call type.
c. The ITC administered on the originating endpoint is incorrect for this call.
d. Incorrect data speed option set in the BRI device causes a call from a BRI endpoint
to sequence through Communication Manager creating a SETUP message with the
wrong bearer capability.
Cause value 03
[0x3/0x83] No route to destination/ Calling party dropped while on hold (5ESS: 5 Electronic
Switching System)/ Bearer service not implemented (1TR6: AT&T ISDN Protocol)
Cause
The ISDN service provider cannot route the call to the indicated destination. Communication
Manager does not originate Cause value 03.
Proposed Solution
2. Check the Cause Value Information Element (LOC). See Location codes on page 75.
a. Dial-plan/Location: The administration of an incorrect home NPA causes an incorrect
code conversion.
number type or number plan information or both, or the call type prevents code
conversion. Call routes to an incorrect route pattern with incorrect digit manipulation
or code conversion or both.
e. ARS toll analysis: An incorrect toll or no-toll classification causes incorrect code
conversion at the route pattern.
parse or IXC routes the call to the wrong interexchange carrier. Number format
Denial events
changed to a format incorrect for the call type. An incorrect service or feature is
specified for the call made on a CBC trunk group preference.
Cause value 04
[0x4/0x84] Send special information tone/ Vacant Code (NI-2: National ISDN 2)
Cause
Cause value 04 indicates that the dialed remote number is unreachable.
Cause value 04 (NI-2) indicates that the destination requested by the calling party is unreachable
because the Numbering Plan Area (NPA) or Central Office (CO) code is vacant (unassigned).
Proposed Solution
1. Check if any prefix or service values are missing from the cause value numbers.
a. Dial-plan/Location: The administration of an incorrect home NPA causes incorrect
code conversion.
or code conversion or both. An incorrect service or feature is specified for the call
made on a CBC trunk group preference. The dialed number format is changed to an
incorrect number format.
parse, or IXC routes the call to the wrong interexchange carrier.
Cause value 05
[0x5/0x85] Misdialed trunk prefix
Cause
The dialed remote number is unreachable.
Proposed Solution
1. Check if any prefix or service values are missing from the cause value numbers.
Denial Events
a. Dial-plan/Location: The administration of an incorrect home NPA causes incorrect
code conversion.
or code conversion or both.
parse, or IXC routes the call to the wrong interexchange carrier.
g. AAR/ARS digit analysis: Call type is incorrect for the call made with an incorrect
or code conversion or both. An incorrect service or feature is specified for the call
made on a CBC trunk group preference. The dialed number format is changed to an
incorrect number format.
Cause value 06
[0x6/0x86] Channel Unacceptable
Cause
The call attempt failed because the requested channel is unacceptable to the ISDN service
provider.
Proposed Solution
Check Communication Manager administration.
B-channels are assigned off a T1/E1 to a trunk group that is unavailable for service from the
remote end. Contact the ISDN service provider to determine which B-channels can be used.
Cause value 07
[0x7/0x87] Call awarded and being delivered in an established channel/ Call identity does not
exist (1TR6: AT&T ISDN Protocol)
Denial events
Cause
Cause value 07 indicates that a new incoming call is established and connected on a channel that
has previously been connected to the same user for similar call types.
Cause value 07 (1TR6) indicates that a call resume has been attempted for a call with an identity
different from any currently suspended calls.
Not an option for ISDN D-channels.
Cause value 08
[0x8/0x88] Preemption/ Prefix 0 dialed in error (NI-2: National ISDN 2)/ Call identity in use
(1TR6: AT&T ISDN Protocol)/ Call is proceeding (NI-1: National ISDN 1)
Cause
Cause value 8 that for Autovon switching networks, a call with a higher priority blocks the call
attempt.
Cause value 08 (NI-2) indicates that the remote user need not include prefix 0 as part of the digit
string in the CALLED PARTY NUMBER.
Cause value 08 (1TR6) indicates that the call identity that is sent in the call resume request is
already in use by the network.
Proposed Solution
Wait and redial the number later.
Cause value 09
[0x9/0x89] Preemption, circuit reserved for reuse/ Prefix 1 dialed in error (NI-2: National ISDN
2)
Cause
Cause value 09 indicates that for Autovon switching networks, a call with a higher priority blocks
the call attempt in order to reserve the requested channel for reuse.
Cause value 09 (NI-2) indicates that the remote user need not include the prefix 1 as part of the
digit string in the CALLED PARTY NUMBER.
Proposed Solution
Cause value 10
[0xA/0x8A] Prefix 1 not dialed (NI-2: National ISDN 2)/ No channel available (1TR6: AT&T
ISDN Protocol)
Cause
Cause value 10 (N1-2) indicates that the user must include the prefix 1 as part of the CALLED
PARTY NUMBER.
Denial Events
Cause value 10 (1TR6) indicates that the call cannot be completed because the circuit or channel
currently available to handle the call request is inappropriate, or the ISDN network is congested.
Cause value 11
[0xB/0x8B] Excessive digits received call proceeding (NI-2: National ISDN 2)
Cause
During call origination procedures, the equipment receives more address digits CALLED PARTY
NUMBER IE than expected. The received address information is truncated.
Cause value 13
[0xD/0x8D] Service Denied (NI-1: National ISDN 1)
Cause value 16
[0x10/0x90] Normal call clearing/ Requested facility not implemented (1TR6: AT&T ISDN
Protocol)
Cause
Cause value 16 indicates that the call was disconnected normally by users at either end.
Cause value 16 (1TR6) indicates that the call cannot be completed because the equipment
sending this cause value does not support the requested service, feature, or supplementary
service in the SETUP message.
back to the user who has originated the call.
Proposed Solution
1. Check the diagnostic information (DIAG) for the facility identifier of the unimplemented
service. See Event data 2 on page 73.
2. If the remote device terminated the connection unexpectedly, check if there is a problem
with the remote endpoint.
3. For data bearer capability calls, if the connection has failed to establish, but the CONNECT
and CONNECT_ACK messages were exchanged before the DISCONNECT was received,
the handshake between the devices involved in the call have failed due to:
a. Option settings with the endpoint devices
b. Bandwidth constriction issues on the B-channels used by the two devices to make the
call
Denial events
Cause value 17
[0x11/0x91] User busy/ Requested facility not subscribed (1TR6: AT&T ISDN Protocol)
Cause
Cause value 17 indicates that the dialed endpoint is unable to accept another call.
Cause value 17 (1TR6) indicates that the call cannot be completed because the user has not
subscribed to the service, feature, or supplementary service requested in the SETUP message.
Proposed Solution
1. Wait and redial the number later.
2. If the user has subscribed to the service, feature, or supplementary service, complete the
ordering process with the ISDN service provider.
3. Check Cause Value Information Element (LOC).
a. If the location information of the Cause Value is 4, public network serving the remote
user, the trunk group to the remote endpoint location is experiencing an all-trunks-
busy condition or not enough channels are allocated into a virtual group for the
particular NSF of the call.
b. If the location information of the Cause Value is 0, user, the endpoint is busy.
4. If Communication Manager is generating this cause value and the endpoint is not busy,
check the following Communication Manager administrations.
a. Trunk group screen: Usage Allocation is y on the CBC Service Type field. Not
enough incoming channels have been allocated for the NSF associated with this call.
b. VDNs and Call vectoring: Analyze the vector processing and the call flow to
determine the cause of the failure. Incorrect VDN vector administration sends the
call to a busy vector step. The call goes to a skill/Automatic Call Distribution (ACD)
group queue that is full and cannot accept any more calls. Look Ahead Interflow/
Best Service Routing (LAI/BSR) receives an inappropriate ISDN response while
checking other sites for available agents, and returns a busy status to the caller.
The LAI/BSR attempt interacts with the public network features: Egress on busy –
overflow to POTS, Alternate Destination Routing (ADR), and Alternate Destination
Call Redirection (ADCR).
c. Trunk and/or station Class of Restriction (COR) prevents the endpoint to terminate the
call.
d. The endpoint has the call forward feature enabled, and this is the second call within
the 30-second time limit on a station that is forwarding this call.
Cause value 18
[0x12/0x92] No user responding/ No response from the remote device
Denial Events
Cause
The remote device/endpoint/PBX does not respond with an ALERTING/PROGRESS/CONNECT
indication within the time administered in the T303 or T310 timers Q.931 specification.
Cause value 18 indicates high traffic conditions in the serving ISDN network or noisy conditions on
the T1/E1 span carrying the D-Channel messaging. The noise causes loss of messages sent to
the remote device. The remote device is also unable to respond to the incoming SETUP request.
Cause value 19
[0x13/0x93] User alerting no answer
Cause
The remote device returned an alerting [ringing] indication but does not provide a connect
indication within the time period prescribed by timer T301.
Communication Manager does not originate this cause value.
Proposed Solution
Cause value 20
[0x14/0x94] Subscriber absent [wireless networks]
Cause
The mobile remote device/endpoint is unavailable.
Proposed Solution
Cause value 21
[0x15/0x95] Call rejected
Cause
The remote endpoint does not accept this call even though the equipment is neither busy nor
incompatible.
Proposed Solution
Check the diagnostic information (DIAG) for the user-supplied condition to determine the reason
for call rejection. See Event data 2 on page 73.
Cause value 22
[0x16/0x96] Number changed
Denial events
Cause
The called party number changes to a new number.
Cause value 01 on page 78 is displayed if the ISDN network does not support Cause value 22.
A BRI or Adjunct Switch Application Interface (ASAI) application generates Cause value 22.
Communication Manager does not originate Cause value 22 for PRI.
Proposed Solution
Check the diagnostic information (DIAG) for the new number. See Event data 2 on page 73.
Cause value 23
[0x17/0x97] Redirection to new destination
Cause
The call has been redirected to a different endpoint.
Communication Manager does not originate Cause value 23.
Cause value 25
[0x19/0x99] Exchange routing error
Cause
The call cannot be routed to the remote user.
Cause value 26
[0x1A/0x9A] Non-selected user clearing
Cause
The call is cleared before the called endpoint receives the incoming call.
Cause value 27
[0x1B/0x9B] Destination out of order
Cause
The call cannot be delivered to the remote endpoint because the interface to the endpoint is
functioning incorrectly. A signaling message cannot be delivered to the remote device because
there is either a physical or data link layer failure at the remote device, or the remote device is
switched off.
Denial Events
Cause value 28
[0x1C/0x9C] Invalid number format (address incomplete) Special intercept announcement
(NI-1: National ISDN 1)
Cause
The called endpoint cannot be reached because the CALLED PARTY NUMBER information is
invalid or incomplete.
back to the user who originated the call.
Proposed Solution
2. Check Communication Manager administration for the cause value generated by the
network.
a. Dial-plan/Location: The incorrect administration of home NPA causes incorrect code
conversion.
b. IXC: The incorrect administration of IXC matching pattern or a dial plan without an
c. AAR/ARS digit conversion: An incorrect digit string is substituted. The call is routed
to the wrong network and over the wrong route pattern. Further conversion is needed
number type or an incorrect information, or the call type prevents code conversion.
Call routes to an incorrect route pattern with incorrect digit manipulation or code
conversion or both.
f. Route pattern: The incorrect administration of NPA causes incorrect code conversion.
An incorrect value entered in the Prefix mark field causes incorrect code conversion.
Toll list in combination with prefix mark causes incorrect code conversion. Incorrect
number of digits are deleted or incorrect digits are added. IXC or international code
digits and user-dialed IXC code fail to parse, or IXC routes the call to the wrong
interexchange carrier. Incorrect service or feature is specified for the call made on a
CBC trunk group preference. The dialed number is changed to an incorrect number
format.
3. Check administration for the cause value generated by Communication Manager.
Trunk group: Incoming call handling table causes Communication Manager to delete
or insert the wrong digits or number of digits to match the dial plan.
Cause value 29
[0x1D/0x9D] Facility rejected/ Special intercept announcement undefined code (NI-1: National
ISDN 1)
Denial events
Cause
The call cannot be completed because the ISDN network does not support or is not subscribed to
the network service or feature requested by this call.
Proposed Solution
1. Check the diagnostic information (DIAG) for the facility identifier of the service that was
rejected. See Event data 2 on page 73.
network.
Route pattern: The service or feature field contains an incorrect value for this route
preference. The ITC/BCIE fields indicate incorrect information for a data call.
Trunk group form: The Service type field indicates a static service type when the
network sends NSF information. Change the field to indicate CBC service.
Cause value 30
[0x1E/0x9E] Response to STATUS_ENQUIRY Special intercept announcement number
unassigned (NI-1: National ISDN 1)
Cause
Cause value 30 is included in a STATUS message when the STATUS message is generated
because a STATUS_ENQUIRY message was received. This is a normal event and does not
indicate a call-affecting problem. Communication Manager generates a call-state audit in every
maintenance cycle that elicits this response from the remote end.
• A no-cause indication through the network
Cause value 31
[0x1F/0x9F] Normal unspecified/ Special intercept announcement call blocked due to group
restriction (NI-1: National ISDN 1)
Cause
Cause value 31 reports a normal event when no other cause in the normal class is applicable.
The ISDN network substitutes this cause value for other causes generated within the network that
do not have end-to-end significance.
For most cause values with only local significance on tandem calls, Communication Manager
maps cause values to Cause value 31. See also Cause value 02 on page 79.
Denial Events
Cause value 31 can also be used as a return code on BSR polling attempts instead of Cause
value 16 on page 84 or Cause value 17 on page 85 depending on which cause value has less
impact/interaction on the intervening ISDN network.
Cause value 32
[0x20/0xA0] Outgoing calls barred (1TR6: AT&T ISDN Protocol)
Cause
The call cannot be completed because the calling user does not have permission to make an
outgoing call.
• A more generic Cause Value through the network
Cause value 33
[0x21/0xA1] User access busy (1TR6: AT&T ISDN Protocol)
Resource-unavailable class cause values

Cause value 34
[0x22/0xA2] No circuit/channel available/ Negative closed user group comparison (1TR6:
AT&T ISDN Protocol)
Cause
Cause value 34 indicates that the call cannot be completed because there is no appropriate circuit
or channel available to handle the call request, or the ISDN network is congested.
Communication Manager generates this cause value when a call is sequenced through
Communication Manager, and the trunk group to be used for the outgoing call is:
• In all-trunks-busy condition
• Unavailable for service
• Unreachable from the incoming trunk group due to Class of Restriction (COR), FRL, trunk-to-
trunk transfer restrictions, or disconnect supervision restrictions
Cause value 34 (1TR6) indicates that the packet mode call is rejected because the user is not
a member of a Closed User Group (CUG) at the remote end, which is a feature associated with
packet mode calls similar to X.25 connection made over the ISDN D-channel.
Communication Manager does not support packet mode sessions on D-channels therefore, this is
not applicable to Communication Manager.
Denial events
Proposed Solution
network.
B-channels are assigned off a T1/E1 to a trunk group that are not available for service
from the remote end. Contact the ISDN service provider to find out which B-channels
can be used.
If all of the B-channels in a span are busied out or otherwise tied up by switch
maintenance but the D-channel is still functioning, an incoming call is rejected with
this cause value because the call cannot be negotiated to another span.
Cause value 35
[0x23/0xA3] Non-existent closed user group (1TR6: AT&T ISDN Protocol)
Cause
The packet mode call was rejected because the equipment sending the cause value does not
recognize the requested Closed User Group (CUG), which is a feature associated with packet
mode calls similar to X.25 connection made over the ISDN D-channel.
Cause value 37
[0x25/0xA5] Semi-permanent connection not permitted (1TR6: AT&T ISDN Protocol)
Cause value 38
[0x26/0xA6] Network out of order
Cause
The call is not completed because the ISDN network is functioning incorrectly, and the condition is
likely to last a relatively long period of time.
Proposed solution
Cause value 39
[0x27/0xA7] Permanent frame mode connection out of service
Cause
This is Q.933 frame relay cause value. Equipment failure causes termination of a frame relay
PVC.
Denial Events
Not applicable to a Communication Manager system.
Cause value 40
[0x28/0xA8] Permanent frame mode connection is operational
Cause
This is a Q.933 frame relay cause value. A frame relay PVC that was terminated has been
restored to service.
Not applicable to a Communication Manager system.
Cause value 41
[0x29/0xA9] Temporary Failure
Cause
The call cannot be completed because the ISDN network is functioning incorrectly. The condition
is not likely to last a long period of time. The call will complete if the user reattempts the call.
Cause value 41 also indicates:
• The failure of channel negotiation at the terminating interface.
• A data link layer malfunction has occurred locally or at the remote network interface.
• The call is cleared as a result of one or more protocol errors at the remote network interface.
Cause value 42
[0x2A/0xAA] Switching equipment congestion
The call cannot be completed because the switching equipment generating this cause value is
experiencing a period of high traffic.
Proposed Solution
Cause value 43
[0x2B/0xAB] Access information discarded
Cause
The network cannot deliver access or user information (such as low-layer compatibility or calling-
name information) to the remote endpoint for any one of various reasons. For example, the call
transferred from ISDN to non-ISDN facilities, or the remote end does not support delivery of such
information.
Denial events
This cause value is usually delivered in a STATUS message. Communication Manager generates
this cause value when:
• A tandem call transfers from ISDN to non-ISDN trunking.
• Calling number or calling name information or both is sent in the SETUP message when it is
not needed.
• Connected number information is sent when the network does not support it.
Proposed Solution
Check the diagnostic information (DIAG) for the Information Element identifier of the discarded
information. See Event data 2 on page 73.
Cause value 44
[0x2C/0xAC] Requested circuit/channel not available
Cause
The call cannot be completed because the circuit or the channel requested for use in the SETUP
message is not available, and the call cannot be negotiated to another channel either because no
other channel is available, or negotiation is not supported or required for this call.
This cause value is generated when a glare condition occurs and B-channel negotiation is not
supported.
Communication Manager generates this cause value when:
• The cause value is generated on the network side of the interface and a glare condition
occurs on the requested B-channel.
• The B-channel requested in the incoming SETUP message is in the incorrect maintenance
state of call handling. For example, the B-Channel is busied out or undergoing testing.
Proposed Solution
1. CO switch default settings deactivate channel negotiation support. Make a specific request
to activate channel negotiation support when ordering CO service.
network.
Trunk group form: When the Channel Negotiation field is set to exclusive,
Communication Manager requests B-channels for calls without support for
negotiation. If the requested B-channel is unavailable at the remote end, the call
cannot be negotiated to a more acceptable B-channel and the call will be rejected with
Cause Value 44. Set the Channel Negotiation field to preferred to support channel
negotiation.
Cause value 45
[0x2D/0xAD] Pre-empted
Denial Events
Cause
The call cannot be completed because the B-channel of this equipment that sends this cause
value cannot process call requests.
Communication Manager does not support this cause value.
Cause value 46
[0x2E/0xAE] Precedence call Blocked
Cause
For Autovon switching networks, the call cannot be completed because the remote endpoint is
busy with a call having higher priority.
Cause value 47
[0x2F/0xAF] Resource unavailable, unspecified/ New destination (4ESS/5ESS: 4/5 Electronic
Switching System)
Cause
Cause value 47 indicates a resource unavailable event only when no other cause in the resource
unavailable class applies.
Cause value 47 (4ESS/5ESS) If this cause value is returned in a RELEASE_COMPLETE or
DISCONNECT message and the customer is an Alternate Destination Call Redirection (ADCR)
subscriber, the system invokes call redirection.
Service or Option-not-available class cause values

Cause value 49
[0x31/0xB1] Quality of service unavailable
Cause
The call cannot be completed because the quality of service requested in the SETUP as defined
in ITU recommendation X.213 cannot be provided. For example, requested throughput or transit
delay cannot be supported.
Cause value 50
[0x32/0xB2] Requested facility not subscribed
Cause
The call cannot be completed because the user has not subscribed to the service, feature, or
supplementary service requested in the SETUP message. If the user has subscribed but does
Denial events
not have access to this service, feature, or supplementary service, then complete the required
ordering process with the ISDN service provider.
Communication Manager does not originate this cause value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application generates this cause value.
Communication Manager translations that can affect receiving this cause value from the network
are:
• Route Pattern service or feature: An incorrect service or feature is specified for the call made
on this CBC trunk group preference. An incorrect ITC and/or BCIE is specified. These fields
affect how the bearer capability is encoded in the SETUP message.
• The ITC administered on the originating endpoint is incorrect for this call.
- Incorrect data speed option set in the BRI device causes a call from a BRI endpoint
sequencing through Communication Manager to create a SETUP message with the wrong
bearer capability.
• On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an
inappropriate NSF can be sequenced from one D-channel to another D-channel.
• The outgoing trunk group is CBC, but no service or feature was specified on the outgoing
route pattern to overwrite the incoming NSF. Add the correct service or feature to the route
pattern or make the outgoing trunk group a static trunk group. For example, public-network or
tie).
• System Parameters Features: The US NI send Calling Name ID field is y. Communication
Manager sends the Bellcore calling name ID but the customer has not subscribed to that
service. Set the US NI send Calling Name ID field to n.
Cause value 51
[0x33/0xB3] Bearer capability incompatible with service request (NI-1: National ISDN 1)
Cause
The requested action cannot be completed. The requested action is incompatible with the bearer
capability of the call (for example, trying to place a data call on hold).
Cause value 52
[0x34/0xB4] Outgoing calls barred
Cause
The call cannot be completed because the network screened the call, and the calling user is not
permitted to make an outgoing call.
Denial Events
Cause value 53
[0x35/0xB5] Service operation violated (NI-1: National ISDN 1)/ Destination not obtainable
(1TR6: AT&T ISDN Protocol)
Cause
Cause value 53 (NI-1) indicates that the user has violated the service operation.
Cause value 53 (1TR6) indicates that the call cannot be delivered to the remote endpoint because
the interface to the endpoint in functioning incorrectly. A signaling message cannot be delivered to
the remote device. For example, there is a physical or data link layer failure at the remote device,
or the remote device is switched off.
Cause value 54
[0x36/0xB6] Incoming calls barred
Cause
The call cannot be completed because the called user cannot accept the call delivered in the
SETUP message.
Proposed Solution
Check Communication Manager administration for the cause value generated by the network.
a. Trunk group: Direction: The Communication Manager field is set to two-way on a trunk group
that the ISDN network has configured as outgoing only, relative to the CO switch, and a user
on Communication Manager is attempting to make an outgoing call over this trunk group,
which is an incoming call to the CO.
b. On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an NSF
for a one-way service, for example, Megacom 800, is sequenced from one D-channel to
another D-channel. The outgoing trunk group is CBC but no overwrite the incoming NSF,
no service or feature is specified on the outgoing route pattern. Add the correct service
or feature to the route pattern, or make the outgoing trunk group a static trunk group. For
example, public-network or tie.
Cause value 56
[0x38/0xB8] Number changed (1TR6: AT&T ISDN Protocol)
Cause
The called user number has been changed to a new number sent in the diagnostic information
(DIAG) for this cause value. See Event data 2. If this cause value is not supported by the ISDN
network, Cause value 01 on page 78 is used instead.
Denial events
Cause value 57
[0x39/0xB9] Bearer capability not authorized/ Out of order (1TR6: AT&T ISDN Protocol)
Cause
Cause value 57 indicates that the call cannot be completed because the user has requested a
bearer capability in the SETUP message which is implemented by the equipment generating this
cause value, but the user either has not subscribed to the bearer capability or is not authorized to
use the bearer capability.
Cause value 57 (1TR6) indicates that the call cannot be delivered to the remote endpoint
because the interface to the endpoint is not functioning properly. There a signaling message is
not delivered to the remote device. The delivery fails due to a physical or data link layer failure at
the remote device, or the remote device is switched off.
Proposed Solution
1. Check the diagnostic information (DIAG) for the unauthorized bearer capability attributes.
See Event data 2 on page 73.
2. Check Communication Manager administration (network generated the cause value).
a. Route pattern: An incorrect ITC or BCIE specified, these fields affect how the bearer
capability is encoded in the SETUP message.
b. The ITC administered on the originating endpoint is incorrect for this call, or the speed
options for calls over these ISDN facilities in the device itself are incorrect or both.
c. Incorrect data speed option set in the BRI device causes a call from a BRI endpoint
sequencing through Communication Manager to create a SETUP message with the
d. A call sequencing through Communication Manager ISDN trunk group to ISDN trunk
group has bearer capability that is not supported by the outgoing ISDN facilities or
network.
e. A call sequencing through Communication Manager on a non-ISDN trunk group
transferring to an ISDN trunk group has an incorrect bearer capability assigned on
the incoming trunk group. The BC and ITC fields to the incoming trunk group are
administered incorrectly.
Cause value 58
[0x3A/0xBA] Bearer capability not presently available/ No user responding (1TR6: AT&T ISDN
Protocol)
Denial Events
Cause
Cause value 58 indicates that the call cannot be completed because the user has requested a
bearer capability in the SETUP message which is implemented by the equipment generating this
Cause Value. However, there are no resources available currently to complete the call.
Proposed Solution 1
CAUSE
Cause value 58 (1TR6) indicates that the remote device, endpoint, or PBX does not respond with
an ALERTING/PROGRESS/CONNECT indication within the prescribed time period allocated by
the expiry of the T303 or T310 timers in the Q.931 specification.
Proposed Solution 2
1. Check the diagnostic information (DIAG) for the bearer capability attributes that are not
available. See Event data 2 on page 73.
2. Check Communication Manager administration for cause value generated by the network.
a. Route pattern: An incorrect ITC or BCIE or both. These fields affect how the bearer
group has a bearer capability that is not supported by the outgoing ISDN facilities or
network.
transferring to an ISDN trunk group has an incorrect bearer capability assigned to
the incoming trunk group. The BC and ITC fields on the incoming trunk group are
Cause value 59
[0x3B/0xBB] User busy (1TR6: AT&T ISDN Protocol)
Cause
The endpoint called has indicated an inability to accept another call.
This cause value has end-to-end significance and must always be passed back through the
network to the user.
Denial events
Proposed Solution
1. Wait and redial the number later.
2. Check the cause value Information Element (LOC).
a. If the Location Information of the cause value is 0 (User), the endpoint is busy.
b. If the Location information of the cause value is 4 (Public Network Serving Remote
User), neither the trunk group to the remote endpoint location is experiencing an
all-trunks-busy condition or insufficient channels are allocated to a virtual group for the
particular NSF of the call.
3. If Communication Manager generates this cause value and the endpoint is free or
available, the following translations and features affect the call:
a. Trunk or station Class of Restriction (COR) or both prevent the call from terminating at
the called endpoint.
b. The endpoint is call-forwarded and this is the second call within the 30-second time
limit on a station that is forwarding this call.
c. Trunk group form: CBC service type: The Usage Allocation field is y. The usage
allocation plan has not allocated enough incoming channels for the NSF associated
with this call.
d. VDNs and Call Vectoring: The vector associated with the VDN is incorrectly
programmed, and the call is inappropriately sent to a busy vector step. The skill/
Automatic Call Distribution (ACD) group that the call attempts to join has a full queue
and cannot accept any more calls. Look Ahead Interflow/Best Service Routing (LAI/
BSR) has received an inappropriate ISDN response while checking other sites for
available agents and has inadvertently returned busy feedback to the caller. The
LAI/BSR attempt is interacting with the public network features Egress on busy –
overflow to POTS, Alternate Destination Routing (ADR), or Alternate Destination Call
Redirection (ADCR). Analyze the vector processing of the call and the call flow to
determine the cause of the failure.
Cause value 61
[0x3D/0xBD] Incoming calls barred (1TR6: AT&T ISDN Protocol)
Cause
The call cannot be completed because the called user cannot accept the call delivered in the
SETUP message.
Proposed Solution
Check Communication Manager administration (network generated the cause value).
a. Trunk group: Direction: Communication Manager is set to two-way on a trunk group that the
ISDN network has configured as outgoing only, relative to the CO switch, and a user on
Communication Manager attempts to make an outgoing call over this trunk group to the CO.
b. On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an NSF
for a one-way service, for example, Megacom 800, is sequenced from one D-channel to the
Denial Events
other D-channel. The outgoing trunk group is CBC but no service or feature was specified on
the outgoing route pattern to overwrite the incoming NSF. Add the correct service or feature
to the route pattern or make the outgoing trunk group a static trunk group. For example,
public-network or tie.
Cause value 62
[0x3E/0xBE] Service not authorized (VN4: French National PRI)/ Call rejected (1TR6: AT&T
ISDN Protocol)
Cause
This cause value has end-to-end significance. Communication Manager returns this Cause Value
Cause value 62 (VN4) indicates that the call cannot be completed because the user has not
subscribed to the service, feature, or supplementary service requested in the SETUP message. If
the user has subscribed but is unable to access this service, feature, or supplementary service,
then complete the required ordering process with the ISDN service provider.
Cause value 62 (1TR6) indicates that the user at the remote endpoint does not want to accept
the call although the user could have accepted the call because the endpoint is neither busy nor
incompatible.
The diagnostic information (DIAG) is populated with the user-supplied condition for the reason of
call rejection. See Event data 2 on page 73.
Cause value 63
[0x3F/0xBF] Service or option not available, unspecified
Cause
This cause value indicates that the requested service or option is unavailable when no other
cause in the Service or option not available class applies.
As an implementation option, this cause value either passes to the user or is mapped to Cause
value 41 on page 92 (Temporary Failure) when it is received at a CO as part of SS7 call handling.
Service or Option-not-implemented class cause values

Cause value 65
[0x41/0xC1] Bearer capability not implemented
Cause
The call cannot be completed because the equipment sending this cause value does not support
the bearer capability requested in the SETUP message.
Denial events
Proposed Solution
The diagnostic information (DIAG) of the cause value should contain the bearer capability
attributes that are not implemented. See Event data 2 on page 73.
Cause value 66
[0x42/0xC2] Channel type not implemented
Cause
the channel type requested in the SETUP message.
Proposed Solution
1. Check the diagnostic information (DIAG) for the unsupported channel type. See Event data
2 on page 73.
network.
Communication Manager is attempting to make a wideband call over an interface
to an ISDN network that does not support wideband calls. Check the trunk group
and routing translations to ensure that the attempted call inadvertently routed to this
interface or was incorrectly classified as a wideband call.
3. Check Communication Manager administration for the cause value generated by
Communication Manager.
a. The network is supporting wideband calling, and Communication Manager does not
have wideband support enabled on the Wideband Switching field on the system-
parameters customer-options screen.
b. Communication Manager does not have wideband support enabled on the Wideband
Support field on the appropriate trunk group.
c. The trunk group does not have the correct type or types of wideband channels
enabled.
d. Communication Manager does not have the wideband endpoint of the right size
programmed.
Cause value 69
[0x45/0xC5] Requested facility not implemented
Cause
the requested service, feature, or supplementary service in the SETUP message.
This Cause Value has end-to-end significance. Communication Manager returns this cause value
Denial Events
Proposed Solution
1. Check the diagnostic information (DIAG) for the facility identifier of the not-implemented
service. See Event data 2 on page 73.
network.
a. Route Pattern service or feature: An incorrect service or feature is specified for the
call made on this CBC trunk group preference. An incorrect ITC or BCIE or both.
These fields affect bearer capability encoding in the SETUP message.
b. The ITC administered on the originating endpoint is incorrect for this call.
d. On tandem calls through Communication Manager from ISDN trunks to ISDN trunks,
an inappropriate NSF can be sequenced from one D-channel to the other D-channel.
The outgoing trunk group is CBC, but no service or feature is specified on the
outgoing route pattern to overwrite the incoming NSF. Add the correct service or
feature to the route pattern or make the outgoing trunk group a static trunk group. For
example, public-network or tie.
e. System Parameters Features: US NI send Calling Name ID field is y.
Communication Manager sends the Bellcore calling name ID but the customer has
not subscribed to that service. Set the US NI send Calling Name ID field to n.
3. Communication Manager tries to send User-to-User information in a message through the
public network if the user has not subscribed to a UUS service, for example, Look Ahead
Interflow/Best Service Routing (LAI/BSR) information, Adjunct Switch Application Interface
(ASAI) information, etc.
Cause value 70
[0x46/0xC6] Only restricted digital information bearer capability is available
Cause
The call cannot be completed because the equipment sending this cause value only supports
the restricted version of the requested bearer capability, and in the SETUP message the bearer
capability is unrestricted.
Proposed Solution
Check Communication Manager administration for the cause value generated by the network.
a. Route pattern: An incorrect ITC or BCIE or both. These fields affect bearer capability
encoding in the SETUP message.
Denial events
sequencing through Communication Manager to create a SETUP message with the wrong
bearer capability.
d. A call sequencing through Communication Manager ISDN trunk group to ISDN trunk group
has a bearer capability that is not supported by the outgoing ISDN facilities or network.
e. A call sequencing through Communication Manager on a non-ISDN trunk group transferred
to an ISDN trunk group has an incorrect bearer capability assigned on the incoming trunk
group. The BC and ITC fields on the incoming trunk group are administered incorrectly.
Cause value 79
[0x4F/0xCF] Service or option not implemented, unspecified
Cause
The call cannot be completed because the equipment sending this cause value has not
implemented a service, feature, or supplementary service requested by the user, and none of
the other cause values in the Service or option apply.
As an implementation option, this Cause value is mapped to Cause value 41 on page 92
(Temporary Failure) when it is received at a CO as part of SS7 call handling.
Invalid-message class cause values

Cause value 81
[0x51/0xD1] Invalid call reference value
Cause
The equipment sending this cause value receives a message with a call reference value that is
not currently in use on this user-network (D-channel) interface. This could indicate a call state
mismatch for the attempted connection between the two sides of the interface.
This cause value is most often generated when a message in a call clearing sequence of
messages is lost in transmission due to problems experienced on the D-channel. One end of the
interface treats the call as disconnected, but the other end sends messages to connect the call.
The response to this new call clearing sequence becomes a RELEASE_COMPLETE message
with Cause value 81.
Cause value 82
[0x52/0xD2] Identified channel does not exist
Denial Events
Cause
The equipment sending this cause value receives a SETUP request to use an inactive channel for
this interface for a call. For example, when a user has subscribed to those channels on a primary
rate interface numbered 1 to 12, and the user equipment or network attempts to use one of the
channels numbered 13 to 23, this cause value is generated.
Proposed Solution
1. Check the diagnostic information (DIAG) for the channel number of the non-existent
channel. See Event data 2 on page 73.
2. Check Communication Manager administration (network generated the cause value).
Communication Manager has B-channels assigned off a T1/E1 to a trunk group that
are not available for service from the remote end. Contact the ISDN service provider
to find out which B-channels can be used.
3. Communication Manager administration that can affect sending this cause value:
Communication Manager has not assigned B-channels to an available trunk group
which is trying to request a call on one of the B-channels. Check which channel is
requested and if possible assign it into the appropriate trunk group. If the channel
requested is the 24th (T1) or 16th (E1) channel, it has been incorrectly programmed
as isdn-pri on the DS1 screen instead of isdn-ext.
Cause value 83
[0x53/0xD3] A suspended call exists, but this call identity does not
Cause
This cause value indicates that a call resume is attempted for a suspended call with a different
identity.
Cause value 84
[0x54/0xD4] Call identity in use
Cause
This cause value indicates that the call identity sent in the call resume request is already in use by
the network.
Cause value 85
[0x55/0xD5] No call suspended
Denial events
Cause
This cause value indicates that a call resume has been attempted for a call, but the network does
not currently have any calls in a suspended state within the domain of interfaces over which calls
can be suspended.
Cause value 86
[0x56/0xD6] Call having the requested call identity has been cleared
Cause
The equipment that sends this cause value receives a resume request for a suspended call that
had been cleared while in the suspended state, either by a network timeout or by the remote user.
Cause value 87
[0x57/0xD7] User not a member of the Closed User Group [CUG]
Cause
The packet mode call was rejected because the user is not a member of the Closed User Group
(CUG) at the remote end, which is a feature associated with packet mode calls, similar to X.25
connection made over the ISDN D-channel.
Cause value 88
[0x58/0xD8] Incompatible destination
Cause
The call cannot be completed because the call request in the SETUP message has low layer
compatibility, high layer compatibility, or other compatibility attributes, for example, data rate, DN,
or sub-address information, which the remote endpoint or network cannot accommodate.
This cause value has end-to-end significance and must always be passed back through the
network to the user.
Proposed Solution
network.
a. Route pattern: An incorrect ITC or BCIE specified, these fields affect how the bearer
Denial Events
group has a bearer capability that is not supported by the outgoing ISDN facilities or
network.
transferring to an ISDN trunk group has an incorrect bearer capability assigned to
the incoming trunk group. The BC and ITC fields on the incoming trunk group are
2. Communication Manager administration that can affect sending this cause value:
a. The extension number received in the incoming SETUP message for a data call is
incorrectly assigned to an analog extension.
b. The extension number received in the incoming SETUP message for a voice call is
incorrectly assigned to a data extension.
c. The outgoing route pattern for a data call sequencing through Communication
Manager to ISDN trunk group does not have the bearer capability activated.
d. The outgoing route pattern for Temporary Signaling Connection (TSC) setup attempt
sequencing through Communication Manager does not have the TSC bearer
capability activated.
Cause value 89
[0x59/0xD9] Network Congestion (1TR6: AT&T ISDN Protocol)
Cause
The call cannot be completed because the switching equipment generating this cause value is
experiencing a period of high traffic.
Proposed Solution
Wait and redial number later.
Cause value 90
[0x5A/0xDA] Non-existent closed user group (CUG)/ Remote user initiated clearing (1TR6:
AT&T ISDN Protocol)
Cause
The packet mode call is rejected because the equipment that sends the cause value does not
recognize the requested Closed User Group (CUG).
Cause value 91
[0x5B/0xDB] Invalid transit network selection
Denial events
Cause
The call cannot be completed because the equipment that sends Cause value 91 receives a
request to route a call to a disconnected transit network, or the transit network identification
received is in an incorrect format. For the correct format of a number, see Annex C of the ITU
Q.931 specification for TNS IE or NSF IE.
Proposed Solution
1. Check Communication Manager administration for the Cause value generated by the
network.
Communication Manager sends the transit network identification in the NSF IE instead of
the TNS IE. The protocol version on the DS1 screen does not match the near-end ISDN
network that is terminating the D-channel.
2. You must contact the ISDN network service provider and try to line up the protocols used.
NI-2 only supports the TNS IE, while custom protocol supports use of the NSF IE for this
purpose.
Cause value 95
[0x5F/0xDF] Invalid message, unspecified
Cause
This cause value indicates an invalid message event only when no other cause in the invalid
message class applies.
Application Interface (ASAI) application might generate this cause value.
Proposed Solution
The diagnostic information (DIAG) of the cause value must contain, if implemented, the message
type identifier of the invalid message. See Event data 2 on page 73.
Protocol-error class cause values

Cause value 96
[0x60/0xE0] Mandatory information element is missing
Cause
The equipment that sent this Cause Value Call Reference Value (CRV) receives a message that
does not contain the required information element for the message to be parsed and processed.
Depending on which message in the call establishment sequence is missing the required
information, a message returned with this Cause Value either does or does not indicate a problem
establishing a call.
Denial Events
When the public network is screening for Calling Party Number (CPN), the missing CPN causes
the network to return this Cause Value, but depending on the options administered in the CO, the
call is established.
Proposed Solution
1. Check if the protocols at each end of the interface match, for example, both sides are
AT&T Custom or both sides are NI-2. If the ends use different protocols, it indicates that
the ends use protocols with different information element encoding.
2. Check the diagnostic information (DIAG) for the Information Element (IE) identifier of the
missing information. See Event data 2 on page 73.
Cause value 96 and 100 diagnostic information

See the following table for the diagnostic information generated by Communication Manager.
Table 26: Cause Value 96 & 100 Diagnostic Information
Missing IE Identifier Information Element

Code-set 0
0C/4C CONNECTED NUMBER
0D CONNECTED SUB-ADDRESS
01 CHANGE STATUS
1C FACILITY
1E PROGRESS INDICATOR
2C KEYPAD
04 BEARER CAPABILITY
6C CALLING PARTY NUMBER
6D CALLING PARTY SUB-ADDRESS
7C LOW LAYER COMPATIBILITY
7D HIGH LAYER COMPATIBILITY
7E USER-TO-USER INFORMATION
08 CAUSE
10 CALL IDENTITY
14 CALL STATE
18 CHANNEL IDENTIFICATION
20 NETWORK SPECIFIC FACILITIES
27 NOTIFICATION INDICATOR
Table continues…
Denial events
Missing IE Identifier Information Element

28 DISPLAY
34 SIGNAL
70 CALLED PARTY NUMBER
71 CALLED PARTY SUB-ADDRESS
74 REDIRECTING NUMBER
79 RESTART INDICATOR
78 TRANSIT NETWORK SELECTION
Code-set 6
7B LOOK AHEAD INTERFLOW
08 TRAVELING CLASS MARK
28 DISPLAY
55 Distributed Communication System (DCS)
56 Distributed Communication System (DCS) AUDIX
57 AUDIX
96 LOCK SHIFT TO CODE-SET6
Cause value 97
[0x61/0xE1] Message type non-existent or not implemented
Cause
The equipment that sent this cause value receives a message containing a message type the
equipment does not recognize, either because the message type is not defined or it is defined but
not implemented by the equipment.
Proposed Solution
AT&T Custom or both sides are NI-2. If the ends use different protocols, it indicates that
the ends use protocols with different information element encoding.
2. Check the diagnostic information generated by Communication Manager for the message
type identifier of the unrecognized message.
Denial Events
Cause value 97, 98, and 101 diagnostic information
Table 27: Cause Value 97, 98, 101 Diagnostic Information (continued)
Message Type Identifier Message

0D SETUP ACKNOWLEDGE
0F CONNECT ACKNOWLEDGE
01 ALERTING
02 CALL PROCEEDING
03 PROGRESS
05 SETUP
07 CONNECT
4D RELEASE
4E RESTART ACKNOWLEDGE
5A RELEASE COMPLETE
6A FACILITY ACKNOWLEDGE
6E NOTIFY
7B INFORMATION
7D STATUS
20 USER INFORMATION
45 DISCONNECT
46 RESTART
62 FACILITY
72 FACILITY REJECT
75 STATUS ENQUIRY
79 CONGESTION CONTROL
Maintenance message
0F SERVICE
07 SERVICE ACKNOWLEDGE
Cause value 98
[0x62/0xE2] Message type, not compatible with call state, or non-existent, or not implemented
Cause
The equipment that sent this cause value receives a message, and the procedures in the protocol
specification indicates that this is not a permissible message to receive while in this call state. A
STATUS message is received indicating an incompatible call state.
Denial events
Proposed Solution
AT&T Custom or both sides are NI-2. If the ends of the interface are using different
protocols, the protocols are used with different call state machines or a different message
type encoding.
2. Check the diagnostic information generated by Communication Manager for the message
type identifier of the message that violates protocol. See Cause value 97, 98, and 101
diagnostic information on page 110.
Call state problems are reported with STATUS messages. The equipment sending the
cause value uses the CALL STATE IE of the STATUS message to indicate the call state. To
determine the call state of the remote end, process the message sequence of the call with
the SDL flow charts of the appropriate side (user or network) with the appropriate protocol
(TR41449/41459, TR1268, A211 etc.). If the call state at the remote end of the interface
does not agree with the call state reported in the STATUS message, and both sides are
already using the same protocol, then there is a problem with the implementation of the
state machine on either side.
There have been problems with the state machine implementations of some of the CO
switches for different protocols, and the state machine problems in the CO switches are
most likely not going to be corrected. Communication Manager has not revealed any
problems with its state machine implementations for the different protocols.
3. Change Communication Manager administration to alter the message sequence of the call
scenario that causes the error, and help solve state machine implementation problems. For
example:
a. change the transferring message on the DS1 screen from PROGRESS to ALERTING
b. change the wait steps in vectors to be i-silent so that they do not generate extra
PROGRESS messages in the calling message sequence.
Cause value 99
[0x63/0xE3] Information element non-existent or not implemented
Cause
The equipment that sent this cause value receives a message that includes Information Element
not recognized or implemented by the equipment sending the cause value. However, the
Information Element is optional in the message, and the equipment that sent the Cause Value
does not parse the Information Element to process the message.
This Cause Value has local significance only. The ISDN network between the user and the
Denial Events
Proposed Solution
protocols, the protocols are used with different Information Element encoding.
network.
Sending connected number information with the domestic custom Information
Element identity encoding (0C), but international encoding (4C) is expected.
Cause value 100

[0x64/0xE4] Invalid information element contents
Cause
The equipment that sends this cause value receives a message with an Information Element that
can be recognized and implemented by the equipment. However, one or more of the fields in the
Information Element are coded in a manner that the Information Element is not implemented by
the equipment sending this cause value.
Proposed Solution
protocols, the protocols are used with different Information Element encoding.
2. Check Communication Manager diagnostics for the IE identifier of the Information Element
that contains the information that violates protocol.
The PROGRESS INDICATOR IE information that Communication Manager generates
must not affect call completion. There is no way to modify how Communication Manager
generates this information.
See Cause value 96 and 100 diagnostic information on page 108.
Cause value 101

[0x65/0xE5] Message not compatible with call state/ Protocol threshold exceeded (NI-2:
National ISDN 2)
Cause
Cause value 101 indicates that the equipment that sent this cause value receives a message
that the equipment recognize, and procedures in the protocol specification indicate that it is not
permissible to receive the message while in call state.
Denial events
Cause value 101 (NI-2) can also mean that an established call or an establishing call is cleared
because the threshold for multiple signaling protocol errors occurred during an active call is
exceeded.
Proposed Solution
protocols, then the protocols are used with different call state machines.
2. Check the Communication Manager diagnostic information for the message type identifier
that is in violation of the protocol. See Cause value 97, 98, and 101 diagnostic
information on page 110.
3. Call state problems are reported with STATUS messages. The equipment sending the
cause value uses the CALL STATE IE of the STATUS message to indicate the call state.
To determine the call state of the remote end, process the message sequence of the call
with the SDL flow charts of the user side or network side with the appropriate protocol
(TR41449/41459, TR1268, A211 etc.). If the call state at the remote end of the interface
does not agree with the call state reported in the STATUS message and both sides are
already using the same protocol, then the problem is with the implementation of the state
machine on either side.
There have been problems with the state machine implementations of some of the CO
switches for different protocols, and the state machine problems in the CO switches are
most likely not going to be corrected. Communication Manager has not revealed any
problems with its state machine implementations for the different protocols.
Change Communication Manager administration to alter the message sequence of the call
scenario that causes the error. For example:
a. change the transferring message on the DS1 form from PROGRESS to ALERTING
b. change the wait steps in vectors to be i-silent so that they do not generate extra
PROGRESS messages in the calling message sequence.
Cause value 102

[0x66/0xE6] Recovery on timer Expiry
Cause
The equipment that sends this cause value sends or receives a Layer 3 Q.931 message. Sending
or receiving this message has initiated a Layer 3 timer that has expired. This cause value is
generated in conjunction with Q.931 protocol error handling procedures.
Denial Events

Communication Manager logs timer-expiry errors in the error log against the signaling group of the
D-channel where the error occurred. The signaling group, ISDN-SGR, error is Error Type 1 and
the Aux Data contains the identifier of the Layer-3 timer that expired.
Communication Manager does not generate the diagnostic information for the Cause value IE.
Proposed Solution
1. Check the diagnostic information for the timer number that has expired. See Event data
2 on page 73.
AT&T Custom or both sides are NI-2.
a. If the ends of the interface are using different protocols, then both ends are using the
protocols with different values for their Layer-3 timers.
b. If the protocols at each end of the interface match, the Communication Manager timer
has expired because:
• The remote end never processed the message because the message was
corrupted by noise on the D-channel. Check for any type of T1/E1 facility errors.
• The remote end experiences a high traffic condition, and due to time limitation,
cannot parse the sent message before the timer expires.
• Though the message is generated in an internal Communication Manager trace,
the message never transmits out onto the D-channel. Perform an external protocol
capture on the D-channel to confirm the transmission of the suspect message.
3. To interpret the receipt of Cause Value 102 from the remote end, look at a trace/protocol
capture of the messaging taking place, and locate the last message received from the
remote end before Cause Value 102 is received.
The timer that expired is most likely the Layer-3 timer associated with that last message. If
Communication Manager generated a message in between those 2 events that must have
stopped the timer, the cause is one of the following:
a. The remote end never processed the message because the message was corrupted
on the D-channel. Check for any type of T1/E1 facility errors.
b. The remote end experiences a high traffic condition, and due to time limitation, cannot
parse the sent message before the timer expires.
c. Though the message is generated in an internal Communication Manager trace,
the message never transmits out onto the D-channel. Perform an external protocol
capture on the D-channel to confirm the transmission of the suspect message.
If Communication Manager fails to respond to the last message received from the
remote end, the internal hardware and software running Communication Manager must
be checked before troubleshooting the problem.
Communication Manager administration that can contribute to timer expiry errors:
a. Trunk group form: Incoming call handling table. If you enter an incorrect value in
the Per call CPN/BN field, Communication Manager sends a FACILITY message
to the CO that causes CO to reject to the CPN/BN information. Communication
Manager logs many timer expiry errors such as Error Type 1, Aux Data 13, against
the signaling group.
Denial events
b. DS1 form: Protocol version: If Communication Manager uses protocol version “A”, and
is connected to a Nortel DMS central office that uses custom protocol, Communication
Manager logs timer expiry errors against signaling group for DISCONNECT problems
(Error Type 1, Aux Data 4) during high traffic conditions.
The DMS CO custom protocol implementation uses the ANSI-recommended timer values
for their Layer-3 timers while Communication Manager uses the ITU-recommended timer
values. The T305 timer in the Communication Manager is 4 seconds, while the same
timer in the DMS is 30 seconds this difference causes timer expiry problems in high traffic
conditions. Change the protocol version of Communication Manager to c to line up the
timers.
Cause value 102, Signaling group Error type 1, Aux data information
Table 28: Cause Value 102, Signaling Group Error Type 1, Aux Data information
Aux Timer Name Timer Description

Data Value
Value
1 T302 4s SETUP_ACK messages (overlap receiving mode)
2 T303_1 4s SETUP message 1st timer expiration
3 T303_2 4s SETUP message 2nd timer expiration
4 T305 4/30s DISCONNECT message
5 T308_1 4s RELEASE message 1st expiration
6 T308_2 4s RELEASE message 2nd expiration
7 T310 10s CALL_PROCEEDING message
8 T313 4s CONNECT message
9 T313_2 4s “no longer used”
10 T316 120s RESTART message
11 TL3 30s Layer 3 timer expired (d-channel dropped)
12 T309 90s d-channel reestablishment expiration stable calls are dropped
13 T_WRN h FACILITY message (waiting for ACK or REJ)
14 T321 120s SERVICE message (waiting for ACK)
15 TSM h retransmission of SERVICE on d-channel switchover
16 TM100 h ISDN-BRI maintenance (MIM timer)
Cause value 103
[0x67/0xE7] Parameter not implemented
Cause
The equipment receives a message with an Information Element that the equipment recognizes
and implements. However, one or more Information Element fields with unacceptable coding are
not implemented by the equipment.
Denial Events
The diagnostic information of the Cause Value should contain, if implemented, the identifier of
the Information Element that contains the information that violates protocol. See Event data 2 on
page 73.
Cause value 110
Message with unrecognized parameter
[0x6E/0xEE]
Cause
The equipment that sends Cause value 110 receives a message with the information element that
the equipment does not recognize. The information element is not mandatory in the message,
therefore, the equipment that sends this cause value does not parse the information element to
process the message.
Cause value 111
Protocol error unspecified
[0x6F/0xEF]
Cause
Cause value 111 indicates that the equipment sending this cause value experiences a protocol
error event to which no other cause value in the Protocol Error class applies.
Cause value 111 (NI-2) is used in packet mode to be able to map the X.25 Cause value 17 on
page 85 “remote procedure error.”
Denial events
Cause value 112

Local procedure error (1TR6: AT&T ISDN Protocol)
[0x70/0xF0]
Cause
This is a packet mode cause value.
Cause value 113
Remote procedure error (1TR6: AT&T ISDN Protocol)
[0x71/0xF1]
Cause
This is a packet mode cause value.
Cause value 114
[0x72/0xF2] Remote user suspended (1TR6: AT&T ISDN Protocol)
Cause
This cause value notifies the remote user that the call has been put on hold.
Cause value 115
[0x73/0xF3] Remote user resumed (1TR6: AT&T ISDN Protocol)
Cause
This cause value notifies the remote user that the call has been taken off hold.
Inter-working class cause values

Cause value 127
[0x7F/0xFF] Inter-working, unspecified/ User info discarded locally (1TR6: AT&T ISDN
Protocol)
Cause
Cause value 127 indicates that an event has occurred at a point in the network that does not
provide cause value information.
Communication Manager generates this Cause Value for events on tandem calls that have
transferred from ISDN trunk groups to non-ISDN trunk groups.
Denial Events
Proposed Solution
Check Cause Value Information Element (LOC). See Location codes on page 75.
Denial event tables

Call Processing Vector Events
Call Processing vector events are listed in the following table:
Table 29: Call Processing Vector Events (0 — 499)
Even Event Description Explanation Event EventData 2

t (keyword) Data 1
Type
1 Call dropped. Call Vector processing ended without the call High short Call ID
not queued at stop being queued to a split and, as a is a vector
step result, the call cannot be answered. This number
implies that some default condition was
Low short
not programmed or that the vector was
is a step
designed to not always answer the call.
number
Also, call was subsequently dropped.
2 Vector with no The call encountered a vector with no High short Call ID
steps steps administered. is a vector
number
Low short
is a step
number
3 10,000 step This can occur due to the following: High short Call ID
executed is a vector
• Incorrect vector programming, for
number
example, including a series of goto steps
that point to one another. Low short
is a step
• Excessive repetition of a programmed
number
loop during a single call. Fr example,
recurring announcement-wait loop.
4 Administration The administration of this step occurred High short Call ID
change while the step was being executed. The is a vector
call flow for this call is unpredictable. Do number
not change vectors when calls are active.
Low short
is a step
number
Table continues…
Denial events

t (keyword) Data 1
Type
5 Call dropped by The call was still in vector processing High short Call ID
vector disconnect when the vector disconnect timer expired. is a vector
timer The call dropped. number
Low short
is a step
number
7 Attd Vec Mismatch- There is a mismatch between Attendant High short Extention
VDN/Vec Vectoring and Call Vectoring between the is a vector
VDN and the vector. number
Low short
is a step
number
9 Attd Vec Mismatch- There is a mismatch between Attendant High short Extention
CR/Vec Vectoring and Call Vectoring between the is a vector
incoming call and the vector. number
Low short
is a step
number
10 Retrying During an announcement step, a collect High short Call ID
announcement digits step that contains an announcement, is a vector
or a disconnect step, the announcement number
was not available, and the announcement
Low short
queue was full. The step is retried at
is a step
regular intervals.
number
11 No announcement During an announcement step, a collect High short Call ID
available digits step that contains an announcement, is a vector
or a disconnect step, the announcement number
was not available for one of the following
Low short
reasons:
is a step
• Announcement was not recorded. number
• Analog announcement was busied out.
• Integrated announcement board was not
installed.
• Integrated announcement ports were
busied out.
• Integrated announcement was being
recorded or restored.
Table continues…
Denial Events

t (keyword) Data 1
Type
20 Call cannot be A queue-to split, messaging split, or check High short Call ID
queued split command failed to queue the call. is a vector
number
Note:
Low short
Event types 520, 521, 522 and 541 is a step
can be observed for the same call at number
the same time.
21 Queued to three The call attempted to queue to four splits. High short Call ID
splits Multiple split queuing allows the call to is a vector
queue to a maximum of three splits number
simultaneously. If the call queued to more
Low short
than one splits and if the call must now be
is a step
dequeued from the splits and then queued
number
elsewhere, one solution is to route the call
to a station, which can be administered
without hardware. Once this happens, the
call is forwarded to the VDN that controls
the next stage of the call.
22 Attd Vec: Cannot Applies to Attendant Vectoring and High short Call ID
requeue indicates that the call is in the attendant is a vector
queue and another attempt is made to number
queue the call to an attendant or hunt
Low short
group, or the call is in the hunt group
is a step
queue and an attempt is made to queue
number
the call to an attendant or too many
attempts are made at queuing to the hunt
group.
30 No TTR available A collect digits command failed because: High short Call ID
is a vector
• TN744 port is not available.
number
• All queue slots are occupied.
Low short
is a step
number
31 Dial-ahead Previously entered dial-ahead digits are High short Call ID
discarded discarded using access of an adjunct is a vector
routing link, converse-on, route-to number, number
or messaging split step.
Low short
is a step
number
Table continues…
Denial events

t (keyword) Data 1
Type
32 Prompting buffer The prompting digit buffer already has the High short Call ID
overflow maximum of 24 digits when additional dial- is a vector
ahead digits are entered by the caller. The number
additional digits are not stored.
Low short
is a step
number
33 ced digits left A collect ced digits step collected digits High short Call ID
behind from a UEC IE and more than 16 digits are is a vector
sent from the network. number
Low short
is a step
number
34 cdpd digits left A collect cdpd digits step collected digits High short Call ID
behind from a UEC IE and more than 16 digits are is a vector
sent from the network. number
Low short
is a step
number
35 ced digits not A collect ced digits step collected digits High short Call ID
available from a UEC IE and no digits are sent from is a vector
the network, or no digits are present in the number
UEC IE.
Low short
is a step
number
36 cdpd digits not A collect cdpd digits step collected digits High short Call ID
available from a UEC IE and no digits are sent from is a vector
the network, or no digits are present in the number
UEC IE.
Low short
is a step
number
37 collect digits for • Failed to put the local variable value in High short Call ID
variable error the local linked list of collect variables is a vector
for the call. This implies that the system number
variable limit is reached.
Low short
• Failed to put the global variable value is a step
in the Variables for Vectors table due number
to messaging issue with Communication
Manager.
• Unknown or invalid variable type defined
in the collect vector step.
Table continues…
Denial Events

t (keyword) Data 1
Type
38 Variable not • The variable conditional that is tested is High short Call ID
defined not defined in the Variables for Vectors is a vector
table. number
• A command or the messaging extension Low short
contains a variable with an invalid value is a step
of none or #. number
39 Invalid table A variable used as a table entry has an High short Call ID
number invalid assignment. is a vector
number
Low short
is a step
number
40 Messaging step A messaging step failed because the High short Call ID
failed Messaging Adjunct is not available. is a vector
number
Note:
Low short
Event types 540 and 541 are is a step
observed for the same call at the number
same time.
41 Messaging ext The messaging extension contains a High short Call ID
invalid variable with an invalid value of none or is a vector
#. Vector event 38 is also generated. number
Low short
is a step
number
50 Route -to step A route-to step failed to reach the intended High short Call ID
failed destination. is a vector
number
Note:
Low short
Event types 51 and 52 provides is a step
specific information regarding the number
reason for the failure.
Table continues…
Denial events

t (keyword) Data 1
Type
51 No digits to The route-to digits step is unable to route High short Call ID
route-to the call because the previous collect digits is a vector
step failed to collect any digits. This can number
result from an error in vector programming,
Low short
for example, a route-to digits step appears
is a step
without a preceding collect digits step.
number
More often, however, this results because
the caller is unable to enter the required
digits, that is, the caller is using a rotary
telephone, or because the caller is not
provided with enough information to do
so, as can be the case for auto-attendant
applications.
52 No available A route-to command is unable to reach High short Call ID
trunks the specified off-switch destination due to is a vector
a lack of available trunks. number
Low short
is a step
number
53 Route-to step The step is unable to seize a trunk High short Call ID
failed because of a hardware problem or glare. is a vector
number
Low short
is a step
number
54 LAI retry Look Ahead Interflow route-to step failed High short Call ID
because of glare. The route is retried is a vector
once. number
Low short
is a step
number
55 Double coverage Coverage option on route-to step is High short Call ID
attempt ignored because double coverage is not is a vector
allowed. This can happen when the call number
has covered to a VDN.
Low short
is a step
number
Table continues…
Denial Events

t (keyword) Data 1
Type
56 Call not in queue Route to step with interflow-qpos condition High short Call ID
not executed because call was not queued is a vector
at a split. number
Low short
is a step
number
57 Deny vector- The vector cannot add an observer High short Call ID
initiated MSO because SRVOBS_MAX=2 is reached. is a vector
number
Low short
is a step
number
58 Deny observing The vector cannot observe the agent High short Call ID
observer because the vector is already an observer. is a vector
number
Low short
is a step
number
59 Variable invalid The adjunct route link ID for GAZ (1-8) or High short Call ID
value MIPSLX (1-64) is invalid. is a vector
number
Low short
is a step
number
60 Adjunct route An adjunct route failed for one of reasons High short Call ID
failed indicated in event types 61 through 66. is a vector
number
Low short
is a step
number
61 Invalid The adjunct routing link command returned High short Call ID
destination digits that do not represent a valid is a vector
destination. number
Low short
is a step
number
Table continues…
Denial events

t (keyword) Data 1
Type
62 Adjunct route The adjunct routing link step is cancelled High short Call ID
cancelled because another routing step such as a is a vector
queue-to split step, is encountered in the number
vector.
Low short
is a step
number
63 Queue before route The adjunct routing link command is High short Call ID
skipped because the call has already is a vector
queued using a queue-to split or a check number
split command.
Low short
is a step
number
64 Adjunct link error The adjunct routing link command is High short Call ID
cancelled due to the following reasons: is a vector
number
• Link to the adjunct is down.
Low short
• ASAI protocol violation prevents call
is a step
completion.
number
• Software resources to complete the call
are unavailable.
65 Software resources A direct agent call is made to an agent High short Call ID
to complete who is not logged in to the relevant split. is a vector
the call are Used for adjunct routing request only. number
unavailable.
Low short
is a step
number
66 Agent not member A direct agent call is made to an agent High short Call ID
of split who is not a member of the relevant split. is a vector
Used for adjunct routing request only. number
Low short
is a step
number
67 Invalid direct A direct agent call is made to an invalid High short Call ID
agent agent extension. Used for adjunct routing is a vector
request only. number
Low short
is a step
number
Table continues…
Denial Events

t (keyword) Data 1
Type
68 Adj route via NCR NCR routing failed and a tandem trunk-to- High short Call ID
failed trunk routing cannot be done. is a vector
number
Low short
is a step
number
69 Adj rte fail-link The adjunct CTI route link ID is within High short Call ID
not adm range but not administered. is a vector
number
Low short
is a step
number
70 Busy step for CO A CO trunk call reaches a busy step in a High short Call ID
trunk vector without having previously received is a vector
answer supervision. As a result, the caller number
continues to hear ringback rather than the
Low short
busy tone.
is a step
number
80 Time not set A goto step with a time-of-day conditional High short Call ID
is processed, but the Communication is a vector
Managertime is not set. number
Low short
is a step
number
81 No digits No digits are collected and a comparison High short Call ID
collected is requested against a digit string or in- is a vector
table. The comparison test is false and the number
next step in the vector is executed.
Low short
is a step
number
82 The holiday table The holiday table is empty Vector Holiday
empty Number, Table
Step Number
Number
83 Service-hours The service-hours table is empty. The High short Holiday
table empty table must be administered. is a vector Table
number Number
Low short
is a step
number
Table continues…
Denial events

t (keyword) Data 1
Type
90 Wait step music A wait-time step with music is accessed, High short Call ID
failed but music is not connected. Check if music is a vector
is administered correctly. number
Low short
is a step
number
91 Wait step ringback A wait-time step with ringback is accessed, High short Call ID
failed but ringback is not connected. is a vector
number
Low short
is a step
number
100 Redirect The call is sent to an agent using a vector, High short Call ID
unanswered call but due to RONA, the call is redirected. is a vector
number
Low short
is a step
number
101 Redirect of call The call is sent to an agent using a vector, High short Call ID
failed but due to RONA, the call was redirected. is a vector
The call is not be redirected. number
Low short
is a step
number
110 Converse no ANI On a converse-on step with passing type High short Call ID
digits ani, no information is available to populate is a vector
the field. number
Low short
is a step
number
111 Converse no qpos On a converse-on step with passing High short Call ID
digits type qpos, no information is available to is a vector
populate the field. number
Low short
is a step
number
Table continues…
Denial Events

t (keyword) Data 1
Type
112 Converse no prompt On a converse-on step with passing High short Call ID
digits type digits, no information is available to is a vector
populate the field. number
Low short
is a step
number
113 Converse drop On a converse-on step, the converse High short Call ID
during data agent hangs up while data is being is a vector
passed. This can indicate a port failure. number
Low short
is a step
number
114 SA8835 Conference SA8835 Conference to VDN failed due to High short Call ID
to VDN failed not meeting vector step or ASAI monitor/ is a vector
control rules. number
Low short
is a step
number
115 ASAI transfer ASAI attempts transfer of a call that is High short Call ID
converse active at a converse step. The transfer is a vector
fails and vector processing continues at number
the next vector step.
Low short
is a step
number
116 Converse transfer Transfer of a call that is active at High short Call ID
denied a converse-on step is attempted. The is a vector
transfer either fails or is denied, and vector number
processing continues at the next vector
Low short
step.
is a step
number
117 Agent drops While active on a converse-on step, High short Call ID
converse an agent became available in a split is a vector
associated with a queue-to split or check number
split step. The call is delivered to the non-
Low short
converse agent and the converse agent is
is a step
dropped.
number
Table continues…
Denial events

t (keyword) Data 1
Type
118 Cannot RONA to VDN Already in a vector processing in converse High short Call ID
during converse step, do not allow RONA to VDN. If you is a vector
want to go to another VDN, then you number
should write your vector to “goto vector”
Low short
when the converse step fails rather than
is a step
use RONA in the converse hunt group.
number
125 Data return no On a converse-on step, the converse High short Call ID
digits agent activated data return but did not is a vector
return any digits. number
Low short
is a step
number
126 Data return time- On a converse-on step, the converse High short Call ID
out agent activated data return but timed is a vector
out while waiting to return digits. Vector number
processing continued at the next vector
Low short
step.
is a step
number
140 Coverage Coverage to a VDN in a coverage path High short Call ID
conference denied is denied because more than one party is is vector
active on the call. number
provided
by dial
plan
Low short
is 0
150 Invalid EAS hunt Either the skill hunt group is removed or is High short Call ID
group used in the a non-ACD hunt group. is a vector
vector step number
Low short
is a step
number
151 Skill indirection Either no VDN skills are administered or High short Active VDN
used improperly the vector command has skill indirection is a vector extension
and EAS is not enabled. number
Low short
is a step
number
Table continues…
Denial Events

t (keyword) Data 1
Type
160 No vector steps, ANI is sent to CMS for a call that reached High short Call ID
ANI sent a VDN that accessed a vector with no is a vector
steps defined. number
Low short
is a step
number
161 uui sent to CMS, A call is directed to a VDN associated with High short Call ID
but there were a vector that has no steps. is a vector
no steps in the number
vector
Low short
is a step
number
170 ASA - invalid VDN A check or goto test requested a High short Call ID
comparison of ASA for a VDN that has is a vector
been removed since the vector was number
programmed. The comparison test is false
Low short
and the next step in the vector is executed.
is a step
number
200 ANI not avail - A goto test requested a comparison of High short Call ID
digits ANI against a digit string and ANI is not is a vector
available for the call. The comparison test number
is false and the next step in the vector is
Low short
executed.
is a step
number
210 Routing table not A goto test requested a comparison with High short Call ID
assigned a vector routing table that is not assigned is a vector
or is removed since the vector was number
programmed. The comparison test is false
Low short
and the next step in the vector is executed.
is a step
number
211 No entries in A goto test requested a comparison with High short Call ID
routing table a vector routing table that has no entries. is a vector
This is a non-match. number
Low short
is a step
number
Table continues…
Denial events

t (keyword) Data 1
Type
212 ANI not avail - A goto test requested a comparison of ANI High short Call ID
table against in-table and ANI is not available for is a vector
the call. The comparison test is false and number
the next step in the vector is executed.
Low short
is a step
number
213 No digits in In-table is administered, but the variable High short Call ID
variable does not contain any digits on which to is a vector
search. number
Low short
is a step
number
220 EWT call not A goto test for a call or converse data High short Call ID
queued passing requested EWT for a call not in is a vector
queue. In this case, the wait time is treated number
as infinite and the comparison is based on
Low short
EWT > largest possible threshold.
is a step
number
221 EWT not sent to The EWT wait time for the call is not sent High short Call ID
VRU to the VRU for a converse-on passing wait is a vector
vector step because the call is not queued number
or the splits/skills that the call is queued to
Low short
is unstaffed.
is a step
number
222 System clock The system clock has changed, therefore 0 0
change any calculations involving time, that is,
ASA and EWT is inaccurate.
230 II-digits not A goto test requested a comparison of II- High short Call ID
avail - digits digits against a digit string and II-digits are is a vector
not available for the call. The comparison number
test is false and the next step in the vector
Low short
is executed.
is a step
number
231 II-digits not A goto test requested a comparison if II- High short Call ID
avail - table digits against in-table and II-digits are not is a vector
available for the call. The comparison test number
is false and the next step in the vector is
Low short
executed.
is a step
number
Table continues…
Denial Events

t (keyword) Data 1
Type
251 Call is not Occurs when a reply-best command in a High short Call ID
incoming ISDN status poll vector receives and tries to is a vector
process a non-ISDN call. Processing in the number
status poll vector terminated is without a
Low short
reply being sent.
is a step
number
261 No best location A queue-to best, check-best, or reply-best High short Call ID
found command fails because the call vector is a vector
is unable to calculate a best value or number
because no local best exists. Vector
Low short
processing continues at the next step.
is a step
Vectors in multisite BSR applications do
number
not attempt to interflow calls.
262 LAI attempt failed Interflow of the call fails since: no trunk High short VDN
was available, LAI denial, or some other is a vector extension
problem. Vector processing continues at number
the next step. In BSR applications, polling
Low short
of this resource is temporarily suppressed.
is a step
number
271 No BSR app num in A queue-to best, check-best, or consider High short VDN
VDN location command fails because the active is a vector extension
VDN for the call as determined by VDN number
override has no BSR application number
Low short
assigned. Processing continues with the
is a step
next vector step. Only occurs in multisite
number
BSR applications.
272 No BSR application A queue-to best, check best, or consider High short VDN
plan administered location command fails because the is a vector extension
application number assigned to the active number
VDN does not have an application plan
Low short
assigned. Processing continues at the next
is a step
step.
number
273 Location not on A consider command fails because the High short VDN
BSR screen command refers to a location number is a vector extension
that is not in the BSR Application screen number
assigned to the active VDN. Vector
Low short
is a step
number
Table continues…
Denial events

t (keyword) Data 1
Type
274 Status Poll VDN A consider command fails because the High short VDN
field is blank entry for this location on the BSR is a vector extension
Application screen does not contain a number
routing number for the status poll VDN.
Low short
is a step
number
275 Interflow VDN A queue-to best or check-best command High short VDN
field is blank fails because the entry on the BSR is a vector extension
Application screen for the relevant location number
does not contain a routing number for the
Low short
interflow VDN.
is a step
number
276 Agent status info A consider location command fails High short VDN
invalid because the status poll returns invalid data is a vector extension
for an available agent (AIT, skill level, or number
occupancy is missing or out of range).
Low short
Vector processing continues at the next
is a step
step. Polling of this location is temporarily
number
suppressed.
277 BSR status info A consider location command fails High short Call ID
invalid because the status poll returns invalid is a vector
EWT data. Vector processing continues at number
the next step. Polling of this location is
Low short
temporarily suppressed.
is a step
number
278 No BSR data in A consider location command fails High short Call ID
response because the status poll does not return is a vector
data in the DISCONNECT message. number
Low short
is a step
suppressed.
number
279 No response from A consider location command fails High short Call ID
status poll because the status poll does not respond is a vector
within the time allowed or because the number
status poll cannot be performed. Vector
Low short
is a step
Polling of this location is temporarily
number
suppressed.
Table continues…
Denial Events

t (keyword) Data 1
Type
280 Bad resp from A consider location command fails High short Call ID
status poll because the command receives an invalid is a vector
response from the status poll such as number
an LAI acceptance message ( ALERT or
Low short
CONNECT). Vector processing continues
is a step
at the next step. Polling of this location is
number
281 BSR EWT is A consider command fails because the High short Call ID
infinite EWT for the referenced split or skill is is a vector
infinite. This can be because all agents number
are logged out, in the Aux work mode,
Low short
or because no queue slots are available.
is a step
number
suppressed.
282 BSR status poll A consider location command fails High short Call ID
attempt failed because the status poll attempt failed. is a vector
See other events for the specific reason. number
Low short
is a step
suppressed.
number
283 BSR poll no trunks A consider location command fails High short Call ID
because there are no available trunks. is a vector
Vector processing continues at the next number
Low short
suppressed.
is a step
number
284 BSR poll seize A consider location command fails High short Call ID
fail because the status poll is unable to is a vector
connect to a trunk due to a hardware number
problem. Vector processing continues at
Low short
the next step. Polling of this location is
is a step
number
285 BSR poll glare The first status poll attempt for a consider High short Call ID
retry location command is unable to connect to is a vector
a trunk due to a race condition. The same number
trunk being seized for the outgoing call
Low short
has an incoming call from the remote end.
is a step
This status poll is attempted once more.
number
A second attempt failure results in event
282.
Table continues…
Denial events

t (keyword) Data 1
Type
286 BSR interflow BSR interflow step failed because of glare. High short Call ID
retry due to glare The route is retried once. is a vector
number
Low short
is a step
number
287 Invalid An attempt is made to perform BSR polling High short Call ID
status polling over ISDN without B-Channel over a is a vector
destination tandem trunk configuration that combines number
QSIG TSCs and AT&T; TSCs. Avaya's
Low short
ISDN protocol does not support this type
is a step
of interworking.
number
288 BSR Poll: TSC not The Trunk Group screen does not contain High short High short is
administered a trunk member administered for purposes is a vector a vector
of TSC. number number
Low short Low short is
is a step a step
number number
289 BSR: Adjust-by The consider location adjust by command High short NAA/NWA
invalid contains a variable with an invalid value is a vector ratio
of none or #. Vector event 38 is also number (Number of
generated. available
Low short
agent to
is a step
Number of
number
working
agent ratio)
290 BSR: bad naa/nwa ratio BSR: bad naa/nwa ratio (number of High short Call ID
available agent to number of working is a vector
agent ratio) number
Low short
is a step
number
291 BSR: Location The consider location command contains a High short Call ID
invalid variable with an invalid value of none or #. is a vector
number
Low short
is a step
number
Table continues…
Denial Events

t (keyword) Data 1
Type
292 Data dropped by The network does not support the High short Call ID
other app transport of all user data, so some user is a vector
data is not sent. You can prioritize the user number
data on the Shared UUI Feature Priorities
Low short
page of the Trunk screen.
is a step
number
293 No room for reply- The network or shared trunk setting does High short Call ID
best information not support the transport of all data for is a vector
the best resource. This is unlikely under number
normal circumstances since only 12 bytes
Low short
of user information are required. Also see
is a step
event 298.
number
294 No room for in-VDN The network does not support the High short Call ID
time transport of all user data. You can prioritize is a vector
the user data on the Shared UUI Feature number
Priorities page of the Trunk screen.
Low short
is a step
number
295 No room for High short Call ID
collected dgt is a vector
number
Low short
is a step
number
296 No room for VDN High short Call ID
Name is a vector
number
Low short
is a step
number
297 No room for other High short Call ID
LAI is a vector
number
Low short
is a step
number
Table continues…
Denial events

t (keyword) Data 1
Type
298 Reply-best got The network or shared trunk setting does High short Call ID
bumped not support the transport of all data for the is a vector
best resource. No other applications share number
user data included in a DISCONNECT
Low short
message.
is a step
number
299 In-VDN time got The network does not support the High short Call ID
bumped transport of all user data. You can prioritize is a vector
the user data on the Shared UUI Feature number
Priorities page of the Trunk screen.
Low short
is a step
number
300 Collected dgts got High short Call ID
bumped is a vector
number
Low short
is a step
number
301 VDN Name got High short Call ID
bumped is a vector
number
Low short
is a step
number
302 Other LAI got High short Call ID
bumped is a vector
number
Low short
is a step
number
303 Block: send reply- The transport of the best data for a High short Call ID
best reply-best command is denied because is a vector
the trunk group is neither supplementary number
service b nor shared UUI.
Low short
is a step
number
Table continues…
Denial Events

t (keyword) Data 1
Type
304 No enhanced info During the execution of a queue-to best or High short Call ID
is sent check best steps, information forwarding is a vector
transport over the trunk is denied because number
the trunk group is neither supplementary
Low short
service b nor shared UUI. This event is not
is a step
logged for LAI, for example, in execution
number
of a route-to step, in order to permit
backward compatibility.
305 A BSR local If a queue-to best step is followed by High short Call ID
treatment vector steps that use commands other than is a vector
pulled a remotely announcement, wait, or goto, the trunk number
queued call back to the remote queue is dropped. This
Low short
to the local functionality can be exploited to allow
is a step
switch to route it the local server to take back calls that
number
elsewhere are interflowed to a remote location after
a specified time limit is exceeded. To
implement this strategy, a wait step with
a specified time interval is included in
the interflow vector on the local server,
followed by more than one route-to step
that redirects the call to an alternate call
center locations.
310 NCR: Invoke trunk Check that only ISDN trunks are executing High short VDN
not ISDN the vector steps where NCR is being is a vector extension
invoked. number
Low short
is a step
number
311 Bad NCR trunk Check that all Trunk Group screen and High short VDN
admin Signaling Group screen fields related to is a vector extension
the NCR feature are correct. number
Low short
is a step
number
312 NCR: No NCT Check that the service provider has High short VDN
service activated the NCT feature for the trunk is a vector extension
being used for NCT call redirections. number
Low short
is a step
number
Table continues…
Denial events

t (keyword) Data 1
Type
313 NCR: No NCT Check that the trunk group is administered High short VDN
outgoing trk as a two-way trunk group and that the is a vector extension
Usage Allocation settings for the trunk number
have been set up correctly.
Low short
is a step
number
314 NCR: NCT outgo trk Shows that the second leg of the NCT High short VDN
drop call is dropped due to a trunk hardware is a vector extension
problem, or that a vector step is executed number
that returned and ISDN DISCONNECT
Low short
message such as a busy vector step.
is a step
number
315 NCR: PSTN NCT The PSTN switch has not accepted the High short VDN
invoke err NCT invocation attempt. Check that the is a vector extension
PSTN network switch complies with the number
NCT standards.
Low short
is a step
number
316 NCR: NCT netwrk Communication Manager has accepted High short VDN
err the NCT invocation attempt, but has is a vector extension
rejected it due to some error condition number
within the network Communication
Low short
Manager. Check that the Network Call
is a step
Redir field on the Trunk Group screen
number
is administered correctly. Make a request
to the service provider for troubleshooting
assistance.
317 NCR: Used NCT trk- NCT has not been successfully invoked, High short VDN
to-trk but the incoming call is still active as a is a vector extension
switch trunk-to-trunk connection, this is, number
only an informational message.
Low short
is a step
number
318 NCR: No NCD Check that the service provider has High short VDN
service activated the NCD feature for the trunk is a vector extension
being used for NCD call redirections. number
Low short
is a step
number
Table continues…
Denial Events

t (keyword) Data 1
Type
319 NCR: invalid nmbr Communication Manager has detected High short VDN
that the number used for the NCR is a vector extension
invocation that is administered in the ~r number
route to number vector step or in the BSR
Low short
Application Table’s VDN Interflow Number
is a step
field is an invalid number, the correct
number
number used through Communication
Manager administration.
320 NCR: NCD call The vector step is executed before the High short VDN
connect err vector step invoking NCD that sends an is a vector extension
ISDN CONNECT message to the PSTN. number
Low short
is a step
number
321 NCR: PSTN NCD The PSTN has not accepted the NCD High short VDN
invoke err invocation attempt. Check that the PSTN is a vector extension
network switch complies with the NCD number
standards. Make a request to the
Low short
PSTN service provider for troubleshooting
is a step
assistance.
number
322 NCR: netwrk err Communication Manager has accepted High short VDN
the NCD invocation attempt, but has is a vector extension
rejected it due to some error condition number
within the network Communication
Low short
Manager. Make a request to the service
is a step
provider for troubleshooting assistance.
number
323 NCR: PSTN NCD max PSTN has detected that the call is High short VDN
redirs redirected by NCD more than the is a vector extension
public network maximum number of call number
deflections limit allows. Modify vector
Low short
processing to reduce the number of NCD
is a step
attempts.
number
Table continues…
Denial events

t (keyword) Data 1
Type
325 NCR: Internal Communication Manager problem with High short VDN
system err call processing for the NCR invocation is a vector extension
attempt. Alternately, for NCT, the first number
vector step at the redirected-to endpoint
Low short
is possibly not programmed with a call
is a step
treatment vector step such as wait
number
hearing ringback, wait hearing music, or
announcement. Do not use vector steps
such as wait hearing silence or wait
hearing i-silence, for the first vector step
at the redirected Communication Manager
endpoint.
326 No ETSI ECT linkID The PSTN switch has returned a High short VDN
FACILITY message to the local is a vector extension
Communication Manager that includes number
the following reject component:
Low short
LinkIDNotAssignedByNetwork. In this
is a step
case, the local Communication Manager
number
leaves the calls in a trunk-to-trunk transfer
state.
327 NCR: Caller not Check that only SIP trunks are executing High short VDN
SIP trk the vector steps where NCR is being is a vector extension
invoked. number
Low short
is a step
number
331 BBP: No task No background task ext for Background High short Call ID
extension BSR Polling is a vector
number
Low short
is a step
number
332 BBP: Vectoring Background BSR Polling Vector High short Call ID
stopped processing stopped is a vector
number
Low short
is a step
number
Table continues…
Denial Events

t (keyword) Data 1
Type
333 BBP: Background Background task not active for High short Call ID
task not active Background BSR Polling is a vector
number
Low short
is a step
number
334 BBP: Data update Error in updating data for Background BSR High short Call ID
error Polling is a vector
number
Low short
is a step
number
335 BBP: VDN appl Background BSR Polling VDN appl High short Call ID
mismatch mismatch is a vector
number
Low short
is a step
number
336 BBP: Invalid Invalid route-to for Background BSR High short Call ID
route-to routing is a vector
number
Low short
is a step
number
337 BBP: BBP task No Background BSR routing data for first High short Call ID
started call since BBP task was just started is a vector
number
Low short
is a step
number
338 BBP: Avail agt BSR Available Agent Strategy mismatch BBP: BSR Call ID
mismatch for Background BSR routing Available
Agent
Strategy
mismatch
350 No return The return command fails and continues High short Call ID
destination to the next step because no return is a vector
destination data exists for the call. number
Low short
is a step
number
Table continues…
Denial events

t (keyword) Data 1
Type
351 Results Truncated A set command executed with operator High short Call ID
CATL or CATR. The result is truncated is a vector
because it is higher than 16 digits. number
Low short
is a step
number
352 Negative Result A set command attempts to execute. High short Call ID
A negative result is converted to # is a vector
(underflow) during the processing. number
Low short
is a step
number
353 Divide by Zero A set command attempts to execute with High short Call ID
operator DIV. The operation specified by is a vector
operand 2 divided by zero and results in a number
# (underflow) assignment.
Low short
is a step
number
354 Assignment not A set command attempts to execute. High short Call ID
allowed The assignment field contains an invalid is a vector
system-assigned variable. The variable is number
invalid because the variable is not a user-
Low short
assigned variable or a digits buffer.
is a step
number
355 Can't set, no lcl A set command attempts to assign a value High short Call ID
var to a user-assigned variable when the 8000 is a vector
system limit is reached. number
Low short
is a step
number
356 Return destination A goto vector command is executed with High short Call ID
stack error a full return destination stack for the call. is a vector
The return destination is not saved. number
Low short
is a step
number
Table continues…
Denial Events

t (keyword) Data 1
Type
357 Operand Overflow A set command attempts to execute with High short Call ID
Underflow operator ADD, SUB, MUL, or DIV. One of is a vector
the operands has a # value or a value number
greater than 4294967295.
Low short
is a step
number
358 Overflow Error A set command executes and obtains one High short Call ID
of the following results: is a vector
number
• A value greater than 4294967295 with a
ADD or MUL operator. Low short
is a step
• A number assigned to a variable from an
number
arithmetic operation has exceeded the
length definition. For example: set A =
none ADD 1000 If variable A is defined
as having a length of 3, A is set to # and
this vector event is generated.
370 VDN conf skip adj- SA8835 - Skip Adjunct-Route step High short Call ID
rte is a vector
number
Low short
is a step
number
371 VDN conf skip SA8835 - Skip Converse-On step High short Call ID
conv-on is a vector
number
Low short
is a step
number
372 VDN conf skip SA8835 - Skip Messaging step High short Call ID
msging is a vector
number
Low short
is a step
number
373 VDN conf skip Skips the collect step for Video High short Call ID
collect Conference. is a vector
number
Low short
is a step
number
Table continues…
Denial events

t (keyword) Data 1
Type
374 Suspend vectors in When the processor occupancy of Overload 0
ovld Communication Manager exceeds 92.5%, flag(bit
the system suspends the vectors for map)
6 seconds. The system re-checks the
processor occupancy and if the processor
occupancy has not still reduced, the
system continues to suspend the vectors
processing after every 6 seconds.
375 Resume vectors When the processor occupancy of Overload 0
after ovld Communication Manager reduces, the flag(bit
system resumes the vectors processing. map)
Group Manager Vector events (500 — 999)

Group Manager Vector events are listed in the following table:
Table 30: Group Manager Vector Events (500 — 999)
Even Event Description, as Explanation Event Event Data 2

tType it is displayed on the Data 1
event log (keyword)
520 Split queue is A queue-to split, check split, Hunt Call ID
full or messaging split command is group
executed, but the call did not queue number
to the split because the queue is full.
To prevent this condition, use a “goto
step...if calls queued in split...>...”
before each queue-to split or check
split step so that an alternative
treatment can be provided for such
cases.
521 Not vector- The split accessed by a queue-to Hunt Call ID
controlled split or check split command is not group
vector-controlled. As a result, the number
step is skipped.
522 AAS split cannot A queue-to split, check split, Hunt Call ID
queue or messaging split command is group
executed on an AAS, but the call did number
not queue to the split because all the
agents are logged out by RONA.
Table continues…
Denial Events

event log (keyword)
540 AUDIX link down Messaging system cannot be Hunt Call ID
accessed using a messaging split group
command because the messaging- number
system link is down. As a result, the
step is skipped.
541 Not a messaging The split administered for the Hunt Call ID
split messaging split command is not a group
messaging split, that is, the split number
does not have a messaging type
administered. As a result, the step is
skipped.
542 Can’t connect idle The call at the head of the queue Hunt Call ID
agent cannot be connected to an idle group
agent. number
550 ASA - No staffed A check or goto test requested a Hunt Call ID
agents comparison of ASA for a split or group
skill that has no staffed agents. The number
comparison was based on ASA >
largest possible threshold.
560 EWT no history for A goto test requested EWT for a Hunt Call ID
split split or skill that has not yet acquired group
history. The wait time is the default number
value.
561 EWT no split queue A goto test requested EWT for a Hunt Call ID
split or skill that has no queue. The group
wait time is treated as infinite. The number
comparison is based on EWT >
562 EWT split queue A goto test requested EWT for a Hunt Call ID
full split or skill, the queue, of which, is group
currently full. The wait time is treated number
as infinite. The comparison is based
on EWT > largest possible threshold.
563 EWT split no A goto test requested EWT for a split Hunt Call ID
working agents or skill that has no agents logged in group
or all logged in agents are in the Aux number
work mode. The wait time is treated
as infinite and the comparison is
based on EWT > largest possible
threshold.
Table continues…
Denial events

event log (keyword)
564 EWT split locked A goto test requested EWT for a Hunt Call ID
split or skill that is currently locked. group
The wait time is treated as infinite. number
The comparison is based on EWT >
565 EWT call no A goto test for a call or converse Hunt Call ID
working agents data passing wait requested EWT for group
a call that is queued only to splits number
or skills that have no agents logged
in or that have all logged in agents
in the Aux work mode. In this case,
the wait time is treated as infinite and
the comparison is based on EWT >
Call processing denial events

Denial events generated during call processing are listed in the following tables:
• Call Process denial events (1001 - 1172) on page 147
• Call processing denial events (1225 - 1899) on page 168
• Call Processing Denial Events (2021 - 2299) on page 236
• Call processing denial events (5000 - 5099) on page 282
• Event Types 1000 - 1899 help isolate the cause of receiving reorder or intercept treatment:
- Event Types 1000 -1299 explain events where reorder treatments are initiated, or to
events that eventually lead to reorder treatments.
- Event Types 1300 - 1899 explain events where intercept treatments are initiated, or to
events that eventually lead to intercept treatments.
Call Process denial events (1001 - 1172)

Table 31: Call Process denial events (1001 - 1172)
EventType Event Description, as Explanation Event Event Data 2

it is displayed on the Data 1
event log (keyword)
1001 Resource not Failure returned in response to “done Origin Call ID
available sending digits” message. ating
UID
1002 Call parked on user A call is already parked on the user. UID Call ID
Table continues…
Denial Events

event log (keyword)
1003 Can't connect Tone Cannot connect/reconnect tone UID Call ID
Det detector during outgoing wait
supervision. Automatic Number
Identification (ANI) request is
expected.
1004 Can't reserve Tone Cannot reserve tone detector. UID Call ID
Det
1005 Trunk sequence Outgoing MFE call received answer Origin Call ID
error before addressing was complete. ating
UID
1006 TTR unavailable No Touch Tone Receiver (TTR) is UID Call ID
available.
1007 CAS Remote Hold The Centralized Attendant Service UID Call ID
(CAS) Remote Hold feature was
accessed. No CAS attendant exists.
1008 CAS Remote Hold Centralized Attendant Service (CAS) UID Call ID
Remote Hold was accessed by a non-
CAS attendant.
1009 CAS Remote Hold Centralized Attendant Service (CAS) UID Call ID
Remote Hold was accessed by non-
CAS attendant. Analog Answer-Hold/
Unhold invalid.
1010 TEG denied Terminating Extension Group was NA NA
origination denied an origination.
1011 Destination Facilities were exhausted during UID Call ID
Unavailable rerouting. Received unexpected TCM
not yet used in routing. Reroute
attempt using received TCM finds
principal is NULL or attendant
extended call to ARS. The call cannot
be queued.
Unavailable rerouting. Bearer capability is VOICE,
VOICE BAND DATA. No outgoing
trunk queuing, or no trunks, or DEXT,
or Adjunct origination, or Administered
Connection, or QSIG Call Completion
Ringout attempt. The call cannot be
queued.
Table continues…
Denial events

event log (keyword)
Unavailable rerouting. Bearer capability is not
VOICE, VOICE BAND DATA. No
outgoing trunk queuing, or no trunks,
or DEXT, or Adjunct origination, or
Administered Connection, or QSIG
Call Completion Ringout attempt. The
call cannot be queued.
1014 Destination Inter-PBX attendant service UID Call ID
Unavailable termination attempt failed. The trunk
was busy.
1015 Destination Attendant seizing trunk for thru-dialing UID Call ID
Unavailable failed. The trunk was busy or not
available.
1016 Remote Cvg loop Outgoing remote coverage call with UID Call ID
denial digit conversion to the extension of the
principal. Prevent looping.
1017 AUDIX Unavailable Termination to AUDIX coverage point UID Call ID
failed. Unable to terminate at an
AUDIX hunt group.
1018 Multimedia call Multimedia call. Converting termination UID Call ID
denial to a meet-me User ID instead of
station User ID failed. Invalid bearer
capability received.
station User ID failed. Communication
Manager failed to get & return meetme
User ID.
station User ID failed. Communication
Manager returned a meetme uid is 0.
1021 Call Term overflow Call termination overflow to Direct Origin Call ID
Dialed Destination (DDD) of an ating
Electronic Tandem Network Listed UID
Directory Number. Call should be
blocked.
1022 CDR resource Call Detail Recording (CDR) resource Origin Call ID
exhaustion exhaustion. Caller from tie trunk can ating
receive reorder tone. UID
Table continues…
Denial Events

event log (keyword)
exhaustion exhaustion. Give Trunk/Personal ating
Central Office Line (TK/PCOL) caller UID
termination to announcement. User ID
not found for announcement.
exhaustion exhaustion. Caller from non-Trunk/ ating
Personal Central Office Line (TK/ UID
PCOL) (from line) can receive reorder
tone.
1025 Incompatable Terminated to an endpoint or trunk Origin UID
Bandwidth group that cannot support the ating
requested bandwidth. UID
1026 AUDIX Unavailable Call from non-trunk. Unable to Origin Call ID
terminate at an AUDIX hunt group. ating
UID
1027 Attd control trk Switch Classified Calls cannot go to a Origin Call ID
denial trunk controlled by an attendant. ating
UID
1028 Trunk Unavailable No trunks are available and cannot be Origin Call ID
queued. ating
UID
1029 Modem Unavailable Modem unavailable from pool. UID Call ID
1030 Modem Unavailable Modem unavailable from pool. UID Call ID
1031 LWC failure Leave Word Calling. Async message UID Call ID
response is reorder.
1036 Station sec code The query for the administered UID Call ID
len qry minimum station-security-code length
failed.
1037 Routing UID=0 The Routing User ID is 0 for a UID Call ID
remote Distributed Communication
System (DCS) user that has activated
automatic callback toward a station
local to this switch.
1038 ACD login failed Traditional Automatic Call Distribution UID Call ID
(ACD) agent login failed. Maximum
number of logins reached.
1039 ACD login failed Group Manager/User Manager setup UID Call ID
of the Automatic Call Distribution
(ACD) Logical Agent login info failed
before password matching, if any.
Table continues…
Denial events

event log (keyword)
1040 ACD login failed Group Manager/User Manager setup UID Call ID
of the Automatic Call Distribution
(ACD) Logical Agent login info failed
after password matching succeeded.
1041 DS0 loop around Incoming ds0 test call failed to set UID Call ID
failed up non-inverting digital looparound
capability.
1042 TTR unavailable Facility Access Test. Touch Tone UID Call ID
Receiver (TTR) is missing, unable to
attach, might be in use by some other
call.
1043 Specified TTR Facility Access Test. The specified UID Call ID
unavailable Touch Tone Receiver (TTR) needed to
collect digits was in use.
1045 FAT tone test Facility Access Test. The test to hear UID Call ID
failed tone failed. The Expansion Network
Link is down.
1046 Specified TSLOT Facility Access Test. Specified timeslot UID Call ID
busy was busy.
1047 Music port connect Facility Access Test. Completing call UID Call ID
fail to music port failed. EPN Link is
not functioning, or music port is not
administered.
1048 FAT trunk busy Facility Access Test - completing call to UID Call ID
trunk failed. Trunk is busy.
1049 ISDN trunk busy Facility Access Test - completing call to UID Call ID
ISDN trunk failed. Trunk is busy.
1050 Illegal Message Remote access user attempted to Origin Call ID
Retrieval access messages via voice coverage ating
message retrieval. This is not simple
permitted. UID
1051 Speech Port No voice synthesis speech port Origin Call ID
unavailable is available for coverage message ating
retrieval. simple
UID
1052 Called announcement Call to announcement, but UID Call ID
busy announcement is busy.
1053 Chime tone Connection of a chime tone to a UID Call ID
connection service failed. There might be an
invalid service ID or software error.
Table continues…
Denial Events

event log (keyword)
1054 TTR unavailable Collection of password digits needs UID Call ID
a Touch Tone Receiver (TTR). No in-
service TTRs are available.
1055 No call to cancel Deactivation of automatic callback UID Call ID
(ACB) was denied or outgoing trunk
queueing (OTQ) was denied. The Call
ID of the ACB/OTQ call to be cancelled
cannot be found. There is nothing to
deactivate.
1056 Adjct Rte calls Adjunct Switch Application Interface UID Call ID
can't Que (ASAI) adjunct-originated switch
classified calls and adjunct-routed calls
cannot be queued.
1057 COS - Auto Callback Class of Service of the user does not UID Call ID
permit activation of automatic callback.
1058 Auto Callback User User activating automatic callback UID Call ID
ID has software partyblock member
misrepresented.
1059 Auto Callback User is activating automatic callback, UID Call ID
double qued but the call has already been queued
or has no principal terminating User ID.
1060 Auto Callback Automatic callback cannot be activated UID Call ID
terminator when the terminating extension is a
group attendant, terminating extension
group, Vector Directory Number, or if
vector processing is active.
1061 Auto Callback Activating automatic callback. UID Call ID
terminator
• For a non-Distributed
Communication System (DCS)
terminator, if there is an
accompanying Call Detail Recording
(CDR) ineffective call attempt record,
the queue is full or zero-length.
• For a DCS terminator, termination
failed for one of several reasons
including the trunk was busy, the
trunk was unavailable, the trunk is
incoming only, the queue is full, the
extension is busy (onhk_que.c)
Table continues…
Denial events

event log (keyword)
1062 Auto Callback Activating automatic callback. Checks UID Call ID
activation on queue availability and/or Distributed
termination pass OK, but activation is
denied.
1063 Auto Callback Activating Automatic Callback (ACB). UID Call ID
ineligible Response to callback type query is
queue ineligible. ACB may be in use
or call is on hold, or there is no call ID
behind call back button.
1064 Double queueing Manual activation of queueing. Call UID Call ID
denied has already been queued (automatic).
1065 Manual queing Manual activation of queueing. There UID Call ID
terminator is no principal terminator on which to
queue.
1066 Manual queing - Manual activation of queueing. The UID Call ID
full que queue is full or queue length is zero.
1067 Manual queing Manual activation of queueing. Checks UID Call ID
denied on queue availability pass OK, but
activation is denied.
1068 queued call went Reactivation of automatic callback or UID Call ID
away outgoing trunk queueing. The call is no
longer in the queue.
1069 PMS link/printer Property Management System (PMS) UID Call ID
down cannot log housekeeping status. PMS
link is not operational and the printer is
nonfunctional.
1070 (also TTR unavailable ISDN trunk initiation of in-band end-to- UID Call ID
in ISDN, IP, end digit collection failed. Waiting for a
and SIP Touch Tone Receiver (TTR).
denial
events on
page 164)
1072 TTR TDM VC failed Time Division Multiplexed (TDM) Voice UID Call ID
Condition (VC) creation for Touch Tone
Receiver (TTR) failed while in Audio
add-on password supervision.
Table continues…
Denial Events

event log (keyword)
Condition (VC) creation for Touch
Tone Receiver (TTR) failed while in
authorization code supervision, waiting
for digit analysis of the authorization
code.
Receiver (TTR) failed while in Code
Call paging seizure supervision.
Tone Receiver (TTR) failed while in
feature supervision waiting to see
which feature is invoked.
Receiver (TTR) failed while in idle
supervision.
Receiver (TTR) failed while in normal
answer supervision.
Receiver (TTR) failed while in outgoing
trunk outpulsing supervision.
Receiver (TTR) failed while in outgoing
trunk seizure supervision.
Tone Receiver (TTR) failed while
in the supervisor for telecommuting
access waiting for certain Feature
Access Codes after the telecommuting
extension has been accessed.
Table continues…
Denial events

event log (keyword)
1081 Change SSC denied Change in Station Security Code UID Call ID
(SSC). Possible causes:
• Too many admin users
• Data already locked
• Translations saved
• SAT user changing station data
• Station recently removed from
translation
• System error
• Problem applying confirmation tone
• Terminal Translation Initiation (TTI)
feature not enabled
• TTI state not Voice (Data TTI
enabled)
1082 Rmv skill - agent Attempting a “Remove Skill” on agent UID Call ID
busy that is currently busy for that skill. The
agent either has DAC or is in After Call
Work (ACW) or on call.
1083 Add/Rmv skill Add/Remove Agent Skills. Possible UID Call ID
denied causes:
• System error
• cannot get station ID
• too many admin users
• save translation in progress
• data already locked
• SAT user is changing agent data
1084 DCS link down Remote user activation of call forward UID Call ID
failed. Distributed Communication
System (DCS) link nonfunctional.
1085 PMS response Property Management System failed to Effecti Call ID
timeout respond to maid status in the 4-second ve UID
set.
1086 MFC no answer MultiFrequency Compelled (MFC) call UID Call ID
timeout circuit congestion. No answer timeout
from MFC call.
Table continues…
Denial Events

event log (keyword)
1087 MFC no answer MultiFrequency Compelled call circuit UID Call ID
timeout congestion. No answer timeout. The
trunk may be corrupt or no Touch Tone
Receiver (TTR) is available at remote
end.
1088 No answer timeout MultiFrequency Compelled call circuit UID Call ID
congestion. No answer timeout. The
trunk may be corrupt or no Touch
Tone Receiver (TTR) is available at the
remote end.
1089 MFC no answer MultiFrequency Compelled call circuit UID Call ID
timeout congestion. No answer timeout. The
trunk may be corrupt or no Touch
Tone Receiver (TTR) is available at the
remote end.
1090 T302 intercept T302 interdigit timer timeout. UID Call ID
timeout
1091 Max Paste users The maximum stations set are Origin Call ID
Pasting currently using PC Application ating
Software Exchange (PASTE). Wait and simple
try again. UID
1092 Announcement Announcement is busy, or UID Call ID
unavailable announcement is not present on
board.
1093 Announcement memory Announcement is dropped, or UID Call ID
exh announcement memory is exhausted.
1094 Permanent Seizure Direct Inward Dialing trunk origination. UID Call ID
Digit timeout with no digits dialed.
Permanent incoming seizure treatment
is to give reorder.
1095 QSIG Call Offer QSIG Call Offer encountered timeout UID Call ID
timeout of 1 minute path retention timer.
1096 Wakeup time Collecting digits for “room wakeup by UID Call ID
unavailable tones” feature. Cannot do a wakeup for
the specified time.
1097 MFC No Answer MFC call circuit congestion. No answer UID Call ID
timeout timeout. The trunk may be corrupt
or no Touch Tone Receiver (TTR) is
available at the remote end.
Table continues…
Denial events

event log (keyword)
1098 TTI merge/unmerge Station server cannot perform Terminal UID Call ID
failed Translation Initiation (TTI) merge/
unmerge. Certain resources are
unavailable. The user can wait and try
again later.
1099 LWC access code Voice synthesis Leave Word Calling UID Call ID
rejected access code rejected.
1100 TTI - station In preparation for lock resources UID Call ID
active step for Terminal Translation Initiation
(TTI) merge/unmerge, Personal
Station Access (PSA) association/
disassociation finds that the station is
active on a call not to be interrupted.
1101 Modem unavailable There is a problem with allocating or UID Call ID
finding a modem for an incoming data
call.
1102 MM - voice call While processing a Multimedia UID Call ID
failure compatible vector, conversion to voice
call failed.
1103 Tone Detector conn Cannot connect tone detector for trunk UID Call ID
fail terminated call. Silent Reorder.
1104 Tone Detector conn Cannot connect tone detector for voice UID Call ID
fail station or DEXT. Silent Reorder.
1105 Ringback limit met Maximum limit of 4 ringbacks in a row UID Call ID
reached before far end answers. Silent
Reorder.
1106 Ringback limit met Maximum limit of 36 ringbacks in a row UID Call ID
reached before far end answers. Silent
Reorder.
1107 Reorder tone Reorder tone received before far end UID Call ID
received answers. Silent Reorder.
1108 LWC access code The message server rejected the UID Call ID
rejected Leave Word Calling Access code that
was dialed.
1109 DCS link/msg buffer Remote busy verification encountered UID Call ID
a Distributed Communication System
(DCS) link down or an exhausted DCS
message buffer.
Table continues…
Denial Events

event log (keyword)
1110 DCS link down Distributed Communication System UID Call ID
(DCS) remote trunk group selection.
Remote Direct Trunk Group Selection
(DTGS) button push by attendant, but
DCS link is down. The attendant can
use the special keys on the attendant
console to seize a trunk, instead of
dialing a Trunk Access Code.
1111 CFWD activate/ Sending a call forward activation UID Call ID
cancel message to the remote switch failed.
Message buffers exhausted, call not
UDP & not Distributed Communication
System (DCS), DCS link is down.
1112 TTR unavailable Russian Automatic Number UID Call ID
Identification (ANI) third party feature
button. Touch Tone Receiver (TTR) not
available.
1113 ANI error limit Third party feature activation. UID Call ID
Automatic Number Identification (ANI)
error on 2 tries.
1114 DCS trunk required Remote busy verification. A Distributed UID Call ID
Communication System (DCS) trunk is
required.
1115 LWC timeout Leave Word Calling timeout occurred UID Call ID
for a non-call associated attempt.
1116 DCS confirm msg Remote busy verification. A Distributed UID Call ID
timeout Communication System (DCS)
confirmation message was not
received within 4 seconds.
1117 Outgoing trk Outgoing trunk seizure failure, busy UID Call ID
seizure fail verify hit glare. There is a problem with
the selected trunk, or an incoming call
was received on a trunk selected for
an outgoing call.
1118 Analog station Analog principal station does not ring. UID Call ID
ringer
1119 Analog station Analog covering station does not ring UID Call ID
ringer and principal station did not ring
successfully.
1120 Bsy Vfy termination Busy verification terminator available, UID Call ID
fail but termination to it failed.
Table continues…
Denial events

event log (keyword)
1121 Bsy Vfy termination Busy verification trunk terminator UID Call ID
fail available, but it is maintenance busy or
otherwise unavailable.
1122 Bsy Vfy termination Busy verification terminator available, UID Call ID
fail but it is out-of-service.
1123 Bsy Vfy termination Busy verify terminator available, but UID Call ID
fail termination is denied due to:
• TRUNK
- admin busy
- incoming seizure
• STATION
- query for virtual set’s station
hunting User ID fails
- virtual set’s physical station’s
current state is not idle or call busy
- admin busy
- maintenance busy
- no available call appearance
- currently dialing
- available call appearance not idle
or busy
• HUNTGRP
- no available member in free list, at
least one not made busy
1124 Bsy Vfy termination Busy verify hunt group member UID Call ID
fail available, but hunt group is all busy
1125 Bsy Vfy call went Attempting to bridge a busy verification UID Call ID
away user to a disconnected call.
1126 Bsy Vfy merge Attempting to bridge a busy verification UID Call ID
failed user to a call that cannot be merged.l
1127 Bsy Vfy warn tone Busy verification warning tone UID Call ID
conn connection failed.
1128 Bsy Vfy warn tone Busy verify warning tone connection to UID Call ID
conn verified call failed.
Table continues…
Denial Events

event log (keyword)
1129 Bsy Vfy call went Attempting to bridge a busy-verifying UID Call ID
away call with a busy-verified call that no
longer exists.
1130 Bsy Vfy merge Attempting to bridge a busy verification UID Call ID
failed call to a call that cannot be merged.
1131 Bsy Vfy merge Merge operation failed for bridging a UID Call ID
failed busy verifying user to a call.
1132 Auto Callback Possible causes: UID Call ID
failure
• Query for calling party’s callback
type failed
• Adding an automatic callback call to
the queue of a trunk group failed or
the queue is full
• Calling party activation of automatic
callback failed
• No automatic callback button/feature
administered
• Automatic callback button already
busy.
1133 Whisp Pg Whisper paging termination to station, UID Call ID
termination fail idle call appearance failed.
1134 Whisp Pg to OS Whisper paging to Out of Service UID Call ID
station (OOS) station.
1135 Whisp Pg term Whisper page to station denied. UID Call ID
denied
Possible causes:
• user has blocked whisper pages or
has service observe pending
• (BRI) maintenance busy and the call
is already queued
• whisper page not permitted towards
analog line
• whisper page termination requires at
least two idle call appearances
• the current call is in the CA_DIAL
state
1136 Whisp Pg hunt grp Whisper paging - the hunt group is all UID Call ID
busy busy.
Table continues…
Denial events

event log (keyword)
1137 Whisp Pg user User has whisper page blocked. UID Call ID
blocked
1138 Whisp Pg Svc Obsvd Whisper page - bridging to service- UID Call ID
call observed call.
1139 Whisp Pg Attd call Whisper page - bridging to call with an UID Call ID
attendant on it.
1140 Whisp Pg Man Exclsn Whisper page - bridging to call with UID Call ID
call manual exclusion activated.
1141 Whisp Pg merge Bridging a busy whisper paging user to UID Call ID
denied a call cannot be merged.
1142 Whisp Pg warn tone Whisper page failure. Unable to apply UID Call ID
conn whisper page tone to the paging user,
cannot retrieve the whisper page tone
option, or cannot retrieve the port ID of
the paged user.
1143 Whisp Pg warn tone Whisper page failure. Cannot apply UID Call ID
conn whisper page tone to the paged user.
1144 Whisp Pg merge Merge page call with paged call - UID Call ID
failed query for originator’s port ID failed.
failed query for port ID of the paged user
failed.
1146 Whisp Pg call went Merge page call with paged call - UID Call ID
away paged user’s call is disconnected.
1147 Whisp Pg blocked Merge page call with paged call - UID Call ID
paged user has whisper page blocked.
1148 Whisp Pg Svc Obsvd Merge page call with paged call - UID Call ID
call paged user is service observed.
1149 Whisp Pg merge Attd Merge page call with paged call - UID Call ID
call paged user is on a call with an
attendant.
1150 Whisp Pg merge Man Merge page call with paged call - UID Call ID
Exclsn paged user has manual exclusion
activated.
1151 Whisp Pg merge Bridging a busy whisper paging user to UID Call ID
denied a call cannot be merged.
failed merge operation failed.
Table continues…
Denial Events

event log (keyword)
1153 ARS man activation Manual activation of queueing seen UID Call ID
queing while in ARS supervision - ARS DAC
has been dialed.
1154 Outgoing trk Seize failed. Indicates either: UID Call ID
seizure fail
• a problem with the selected trunk
• an incoming call was received on a
trunk selected for an outgoing call in
busy verification on non-Distributed
Communication System (DCS) call
type and not bridge-on case.
1155 Bsy Vfy digit Digit timeout while in busy verification UID Call ID
timeout on non-DCS call type and not bridge-
on case.
1156 Connection resrce Connection resource not available. UID Call ID
unavail This is an administered connection.
1157 TTR unavailable Activate service observing feature. UID Internal
Initiated from a vector step and only software
the Feature Access Code of service return code
observing is in the vector step. End- TTR queued.
to-end signaling digit collection of
GCOL_TTRQ
extension to be observed cannot get a
(6)
Touch Tone Receiver (TTR).
1158 Svc Obsv Ext table Validation of service observed UID Call ID
full extension. No room in software table
to store service observing User IDs.
1159 Cancel wakeup Cannot cancel wakeup. UID Call ID
failed
1160 Activate wakeup Cannot activate wakeup time. Possible UID Call ID
failed causes:
• previous request exists and cancel
flag not set
• wakeup request time is too close
• 15 min interval limit exceeded
• system limit on requests exceeded
1161 Max# connected Whisper page - bridging to a call UID Call ID
parties that has reached maximum number of
connected users.
1162 Max# connected Whisper page - bridging to call that UID Call ID
parties has reached maximum number of
connected users.
Table continues…
Denial events

event log (keyword)
Receiver (TTR) failed while in whisper
supervision.
1164 ISDN no cause value Outgoing ISDN trunk rejected/ dropped UID DIAG/LOC/CV
by remote end.
(also in
ISDN, IP,
and SIP
denial
events on
page 164)
1165 Attd ctrl of ARS Attendant control of trunk group UID Call ID
pref (s) access ARS preference(s).
1166 Unassigned number Unassigned number. UID DIAG/LOC/CV
(also in
ISDN, IP,
and SIP
denial
events on
page 164)
1167 Can’t term No Attendants or redirection extension UID Call ID
emergency call assigned for termination of emergency
call.
1168 Second call failed Russia MultiFrequency (MF) Packet UID Call ID
Signaling - Second call attempt failed.
1169 Retry option not Russia MultiFrequency (MF) Packet UID Call ID
enabled Signaling. The “Retry?” option is no,
and either T1 or T2 timer expired or a
B6 signal was received.
1170 Erroneous signal Russia MultiFrequency (MF) Packet UID Call ID
received Signaling - Erroneous signal received.
1171 ATM Blockage:TDMSVC TDM SVC creation failed due to lack of UID Internal
fail resources, call was dropped. software
return code of
the sequencer
-SEQ_ERR(0)
/
SEQ_SUSP(1
)/
SEQ_COMP(
3)/
SEQ_FREE(4
)
Denial Events
ISDN, IP, and SIP denial events

Some Event Type numbers in this section can be re-used for IP and SIP Denial Events. Please
check the log information carefully to determine what type of network experienced the event that
led to the denial, even if the explanation refers to ISDN.
Table 32: ISDN, IP, and SIP-generated denial events (1173 - 1224)

it is displayed on the Data
event log (keyword) 1
1070 (also TTR unavailable ISDN trunk initiation of in-band end-to- UID Call ID
in Call end digit collection failed. Waiting for a
Process Touch Tone Receiver (TTR).
denial
events
(1001 -
1172) on
page 147)
1164 ISDN no cause value Outgoing ISDN trunk rejected / dropped UID DIAG/LOC/C
by remote end. V
(also in
Call
Process
denial
events
(1001 -
1172) on
page 147)
1166 Unassigned number Unassigned number. UID DIAG/LOC/C
V
(also in
Call
Process
denial
events
(1001 -
1172) on
page 147)
1173 No route to transit No route to specific transit network. UID DIAG/LOC/C
ntwk V
See Cause value 02 on page 79.
1174 No route to dest No route to destination. UID DIAG/LOC/C
V
1175 ISDN channel Channel unacceptable. UID DIAG/LOC/C
unacceptable V
Table continues…
Denial events

1176 ISDN MLPP circ not MLPP preemption, circuit not reserved. UID DIAG/LOC/C
resrvd V
1177 ISDN MLPP circ resv MLPP preemption, circuit reserved for UID DIAG/LOC/C
reuse reuse. V
1178 Normal call Normal call clearing. UID DIAG/LOC/C
clearing V
1179 User busy User busy. UID DIAG/LOC/C
V
1180 No user responding No user responding. UID DIAG/LOC/C
V
1181 User alerting, no User alerting, no answer. UID DIAG/LOC/C
answer V
1182 Subscriber absent Subscriber absent. UID DIAG/LOC/C
V
1183 Call rejected Call rejected. UID DIAG/LOC/C
V
1184 Number changed Number changed. UID DIAG/LOC/C
V
1185 Dest out of order Destination out of order. UID DIAG/LOC/C
V
1186 Invalid number Invalid number format. UID DIAG/LOC/C
format V
1187 Facility rejected Facility rejected. UID DIAG/LOC/C
V
1188 Response status Response status enquiry. UID DIAG/LOC/C
enquiry V
1189 Normal, unspecified Normal, unspecified. UID DIAG/LOC/C
V
1190 No circ/chan avail No circuit or channel available. UID DIAG/LOC/C
V
Table continues…
Denial Events

1191 Network failure Network failure. UID DIAG/LOC/C
V
1192 Temporary failure Temporary failure. UID DIAG/LOC/C
V
1193 Equipment Switching equipment congestion. UID DIAG/LOC/C
congestion V
1194 ISDN user info User info discarded. UID DIAG/LOC/C
discarded V
1195 Circ/channel Requested circuit / channel not UID DIAG/LOC/C
unavail available. V
1196 ISDN blocked Blocked precedence level. UID DIAG/LOC/C
precedence V
1197 Resources unavail/ Resources unavailable, unspecified. UID DIAG/LOC/C
unspec V
1198 ISDN req fac no Requested facility not subscribed. UID DIAG/LOC/C
subscribe V
1199 ISDN outgoing call Outgoing calls barred. UID DIAG/LOC/C
barred V
1200 ISDN incoming call Incoming calls barred. UID DIAG/LOC/C
barred V
1201 Bearer cap not Bearer capability not presently UID DIAG/LOC/C
available available. V
1202 Service unauth Service not authorized / France VN4. UID DIAG/LOC/C
FranceVN4 V
1203 Serv/option Service/option not available, UID DIAG/LOC/C
unavailable unspecified. V
1204 Bearer cap not Bearer capability not implemented. UID DIAG/LOC/C
implem V
1205 ISDN chan type not Channel type not implemented. UID DIAG/LOC/C
implem V
Table continues…
Denial events

1206 Req facility not Requested facility not implemented. UID DIAG/LOC/C
implem V
1207 Only restr digital Only restricted digital BC available. UID DIAG/LOC/C
BC av V
1208 Srv/opt not imp/ Service/option not implemented, UID DIAG/LOC/C
unsp unspecified. V
1209 Invalid call Invalid call reference. UID DIAG/LOC/C
reference V
1210 Channel doesn't Identified channel does not exist. UID DIAG/LOC/C
exist V
1211 Incompatible dest Incompatible destination. UID DIAG/LOC/C
V
1212 ISDN trans ntwk not Transit network does not exist. UID DIAG/LOC/C
exist V
1213 Invalid message Invalid Message. UID DIAG/LOC/C
V
1214 Mandatory IE Mandatory IE is missing. UID DIAG/LOC/C
missing V
1215 ISDN msg typ Message type nonexistent or not UID DIAG/LOC/C
nonexist/imp implemented. V
1216 Msg not compat Message not compatible with call state. UID DIAG/LOC/C
state V
1217 ISDN nonexistant IE Nonexistent IE. UID DIAG/LOC/C
V
1218 Invalid IE contents Invalid IE contents. UID DIAG/LOC/C
V
1219 ISDN msg not compat Message not compatible with call state. UID DIAG/LOC/C
state V
1220 Recovery on timer Recovery on timer expiry. UID DIAG/LOC/C
expiry V
Table continues…
Denial Events

1221 Protocol err Protocol Error Unspecified. UID DIAG/LOC/C
unspecified V
1222 ISDN intr ana ntwk Inter-worked to analog network (France UID DIAG/LOC/C
Fr VN4 VN4) V
1223 ISDN goto con mode Go to conversation mode (France VN4) UID DIAG/LOC/C
Fr VN4 V
1224 Interwork/cause Inter-working or cause unknown. UID DIAG/LOC/C
unknown V
1570 (also TTR insertion Processing incoming digits for ISDN
in Call failed call. Insertion of Touch Tone Receiver
Processing (TTR) to collect in-band digits failed.
Denial
Events
(2021 -
2299) on
page 236)
1573 (also Principal is not The principal is not ISDN.
in Call ISDN
Processing
Denial
Events
(2021 -
2299) on
page 236)
Call processing denial events (1225 - 1899)

Denial events 1225 - 1889 are described in the following table.
EventType Event Description, as Explanation Event Event Data

it is displayed on the Data 1 2
event log (keyword)
1225 All SBS extensions Separation of Bearer and Signaling UID Call ID
in use (SBS) Signaling call tried to allocate
an SBS extension, but all SBS
extensions are in use.
1226 Cannot get SBS Sig Separation of Bearer and Signaling UID Call ID
CID (SBS) Bearer call tried to retrieve
SBS Signaling call Call ID.
Table continues…
Denial events

event log (keyword)
1227 Can't send SBS ID Separation of Bearer and Signaling Call ID SBS
to orig (SBS) Signaling call tried to send an signaling
INFO message with unique ID, but
Call ID
the message cannot be sent.
1228 Non-bearer trk to A non-trunk call terminated to an UID UID
SBS ext allocated Separation of Bearer and
Signaling (SBS) extension waiting to
receive the Bearer SBS call.
1229 Unable to get ARS Error occurred when getting the UID Call ID
fac ARS Feature Access Code (FAC) to
build the Separation of Bearer and
Signaling (SBS) complete callback
number.
1230 Unable to get Error occurred when getting the UID Call ID
country code local country code to build the
Separation of Bearer and Signaling
(SBS) complete callback number.
1231 Unable to get intl Error occurred when getting the UID Call ID
accode international access code to build
the Separation of Bearer and
Signaling (SBS) complete callback
number.
1232 TTR err SBS ID dgt Error occurred when trying to Originating Message
coll allocate a Touch Tone Receiver simple UID Type
(TTR) to collect the Unique ID in-
band at the terminating node.
1233 Invalid SBS ID Invalid or partial Separation of Message Unique ID
dgts/tmo Bearer and Signaling (SBS) Unique Type digits
ID collected, or interdigit timeout collected
while collecting Unique ID at SBS
terminating node.
1234 No VOA/Data Priv VOA not played for this call because UID for UID
Active data privacy is active. party
hearing
VOA
1235 No VOA COR User (agent, Service Observer, UID for UID of latest
Permissions etc.) cannot hear VOA because of COR VDN
lack of Class of Restriction (COR) checking
permissions.
Table continues…
Denial Events

event log (keyword)
1236 No PSA_DIS with Deny Personal Station Access UID UID of
ACD call (PSA) disassociate because there is logical
an Automatic Call Distribution (ACD) agent
call on the telephone. logged-in if
there is an
ACD call on
this station
1237 TTR err IGAR ID Error occurred when trying to Originating Internal
dgt coll allocate Touch Tone Receiver (TTR) simple UID software
to collect the Unique ID in-band at return code
the originating node. error in digit
collection
1238 Invalid IGAR ID Invalid or partial Inter-Gateway Message Digits
dgts/tmo Alternate Routing (IGAR) Index Type Collected
collected, or interdigit timeout while
collecting destination IGAR index at
IGAR originating node.
1239 Deny ACB act to Automatic Callback (ACB) to self UID Call ID
Self cannot be activated.
1240 No response to E-sigged digits three times with no E-sig digit Current
IGAR DTMF response from the far end. IGAR UID
1241 Non-numerics in Invite FNU contains non-numeric UID Call ID
Invite FNU characters in the extension field.
1242 Off-net cvg/fwd Redirect off-net coverage or forward Current Approximat
threshold was blocked due to the threshold user UID e number of
limit set on the system-parameters (Cur_user) calls to this
coverage screen. station
currently
redirected
off-net
1243 Bandwidth limit Bandwidth limit was exceeded on an UID Call ID
exceeded endpoint or trunk group.
1244 DPT:TTR err idx Error occurred when trying to UID Internal
dgt coll allocate TTR to collect the software
destination IGAR user index. return code
error in digit
collection
1245 DPT:TTR err UID Error occurred when trying to UID Internal
dgt coll allocate TTR to collect calling/called software
party User IDs. return code
error in digit
collection
Table continues…
Denial events

event log (keyword)
1246 Svs obsrv exceed New observer denied, maximum UID Call ID
max number of observers already in use.
1247 IGAR/DPT LDN grew IGAR/DPT LDN converts to a Current Number of
too big number that is longer than ARS can digit digits in
process. position in buffer
the LDN
extension
1248 Deny observing Cannot observe yourself. UID Call ID
self
1249 No ETSI ACB Activating ACB on ETSI interface. UID Call ID
available rcvd The activation was denied because
the public network did not
send a CCBS/CCNR Available in
Disconnect or Alert message.
1250 All Adjunct Users Maximum number of switch Maximum NA
in use classified (predictive dial) calls are number of
in progress with call classifiers still Adjunct
attached. Adjunct user cannot be User
allocated for a switch classified
(predictive dial) call.
1251 Invalid parameters Cur_psuid Cur_buid
in FNU Invite
1252 - 1299 not assigned
Begin intercept type source of denials
1300 Digits prevent MultiFrequency Compelled call not UID Call ID
call route routed due to invalid digit, not
enough digits, etc.
1301 Need MFC or TT dial Outgoing dial type is not UID Call ID
type MultiFrequency Compelled or Touch
Tone (TT).
1302 Dgts needed or Minimum digits not dialed before UID Call ID
caller typ pressing feature button, or calling
party is not a station or attendant.
1303 TTR queue type Touch Tone Receiver (TTR) UID Call ID
invalid queueing problem. Invalid TTR
queue type found.
1304 Dgt absorbtion/ Digit block requires preconditioning UID Call ID
insertion for digit absorption or insertion.
Error in treatment. A Touch Tone
Receiver (TTR) is available.
Table continues…
Denial Events

event log (keyword)
1305 Dgt collection Software error. Invalid return code UID Call ID
software
1306 Satlt dropped TGU Italian outgoing tie (TGU) call UID Call ID
B4 ansr dropped by satellite before answer.
1307 LoginID UID query Query for User ID of logged-in UID Call ID
failure Logical Agent’s LoginID failed.
1308 PNT or TIE Enforce (Public Network Trunk) UID Call ID
restriction PNT-PNT Restrictions. Post,
Telephone, and Telegraph
Administration (PTT) or TIE cannot
connect to this PTT trunk.
1309 Data/Voice BCC Trouble setting up voice to data UID Call ID
setup fail or data to voice (change Bearer
Capability Class) and/or outgoing
Bearer Capability Class (BCC) for
ISDN voice call.
1310 Incompatible term Tried to terminate the call to UID Call ID
endpnt incompatible endpoint.
1311 Routing software Invalid return code. Software error. UID Call ID
failure
1312 Route PTRN trunk No available trunks in the routing UID Call ID
unavail pattern.
1313 Remote DTGS Remote Direct Trunk Group UID Call ID
invalid digit Selection (DTGS) that was
processing digits (after tie
Trunk Access Code) from the
preprocessing digit buffer to the digit
buffer found invalid number of digits
(0 or more than 10).
1314 Dgt collection Error during setup for end-to-end UID Call ID
setup fail signaling digit collection.
1315 Dgt collection Error during setup for end-to-end UID Call ID
setup fail signaling digit collection prevented
setting an indication that the call
was queued during termination
waiting for a Touch Tone Receiver.
1316 No unrstrictd term No principal to terminate to, or it is UID Call ID
point termination restricted, and there is
no termination coverage point.
Table continues…
Denial events

event log (keyword)
1317 Coverage software Software error. Termination to UID Call ID
failure coverage point received invalid
return code.
1318 Split UID query Adjunct Switch Application Interface UID Call ID
failure (ASAI) Direct Agent Call termination
fails in querying for split User ID.
1319 Call record sftw Incoming QSIG call completion UID Call ID
failure ringout call. Failure retrieving
suspended Temporary Signaling
Connection (TSC) call record from
service dispatcher.
1320 Call record sftw Incoming QSIG call completion UID Call ID
failure ringout call. Call completion ringout
call record does not match
Temporary Signaling Connection
(TSC) call record retrieved from
service dispatcher.
1321 Illegal term to Adjunct Switch Application Interface UID Call ID
rmt Audix (ASAI) switch classified call. Illegal
attempt to terminate off-switch to a
remote AUDIX.
1322 Data to station Data call to station type endpoint. UID Call ID
w/o H.320 The station does not have the H.320
conversion flag set.
1323 Dgt collection Error during end-to-end signaling UID Call ID
setup fail digit collection setup. Origination
from ISDN trunk or endpoint.
1324 Data Ext code Code calling by a data extension. UID Call ID
calling
1325 ASAI SCC to UDP ASAI Switch Classified Call (SCC) UID Call ID
nite svc to hunt group with Uniform Dial Plan
(UDP) night service. This type of call
cannot go off-switch.
1326 MM to Attd ctrld Multimedia user cannot call a trunk UID Call ID
trunk under attendant control, Attendant
Control of Trunk Group Active
(ACTGA). An attendant can take
control of a trunk group using the
event.
Table continues…
Denial Events

event log (keyword)
1327 Obtaining Attd UID Call to trunk under attendant control UID Call ID
fails (Attendant Control of Trunk Group
Active (ACTGA)). Failure getting
attendant User ID.
1328 Term to ACTGA Attd Call to trunk under attendant UID Call ID
fails control (Attendant Control of Trunk
Group Active (ACTGA)). Failure
terminating caller to controlling
attendant.
1329 Term to Block termination to incoming-only UID Call ID
inappropriate pt type trunk or user with voice bearer
termination to a DEXT group.
1330 Iterative term Call termination failure rerouting to UID Call ID
attd-retry attendant. Retry of termination to
attendant was blocked to prevent an
endless retry.
1331 Italian Italian misoperation treatment. UID Call ID
misoperation
1332 Data mod options Reserving a pooled modem. Query UID Call ID
qry fail of data module for its options failed.
1333 Term to modem Seizing (terminating on) a pooled UID Call ID
failure modem failed.
1334 Term to modem Analog endpoint termination to UID Call ID
failure pooled modem (after administrable
time delay expires) failed.
1335 LWC blocked by Leave Word Calling. Async UID Call ID
msg_sv message response returns
intercept.
1336 Tone detection Tone detector timeout without UID Call ID
timeout receiving a valid tone.
1337 Intrcpt tone from Intercept tone received before UID Call ID
far end remote end answers.
1338 Wait for answer Wait answer supervision was timed UID Call ID
timeout out on a call from a station or tie
trunk.
1339 Auth code required Digit analysis and routing problem. UID Call ID
Authorization code required.
1340 Rmt cfwd invald The attendant activated call UID Call ID
local ext forwarding for a remote extension to
an invalid local extension.
Table continues…
Denial events

event log (keyword)
1341 Non-voice call Non-voice call was routed to UID Call ID
intercept attendant or announcement for
intercept treatment. Switch to
intercept tone treatment.
1342 Dest BCC The destination bearer capability UID Effective
incompatible code is incompatible. UID
1343 Need higher FRL to A higher Facility Restriction Level is UID Effective
route needed to route the call. UID
1344 Hop count The outgoing call is hop-count Effective Digits
restricted restricted. UID
1345 Multiparty caller Paging equipment with more than 1 UID Call ID
paging party on the call is inaccessible.
1346 Svc Obsrv from Service observing is not possible UID Call ID
wireless from wireless stations because they
do not support “off-hook idle” state.
1347 Svc Obsrv dpm Query of dial plan manager to see UID Call ID
query fail if Feature Access Code service
observing is optioned failed.
1348 No Fac Svc Feature Access Code service UID Call ID
Observing observing is not optioned.
1349 Term dial-up tst Feature Access Code entered to do UID Call ID
brdg app terminal dial-up test, not permitted
on bridged appearances.
1350 Term dial-up tst Terminal dial-up test is not permitted UID Call ID
term typ on attendant, BRI, wt or analog type
terminal, or the terminal does not
have a call appearance active on
the voice channel.
1351 More digits Appending “#” to end of digit buffer. UID Call ID
expected All digits have been processed
for an Adjunct Switch Application
Interface (ASAI) originated call, but
more digits are expected to be
collected.
1352 Port ntwk numbr Facility access test specified a port UID Call ID
too large network number greater than the
maximum defined.
1353 Cabinet number too Malicious call trace specified a UID Call ID
large cabinet number greater than the
maximum defined.
Table continues…
Denial Events

event log (keyword)
1354 SSC dialed ext's Station Security Code (SSC) digit UID Call ID
uid fail processing. The dialed extension’s
User ID has lost its association with
the extension number.
1355 Auth code reqired. Call is an Adjunct Switch Application UID Call ID
(ASAI) Interface (ASAI) phantom call and
requires an authorization code. This
is not permitted.
1356 ASAI SCC VDN The first leg of an Adjunct UID Call ID
destination Switch Application Interface (ASAI)
Switch Classified Call (SCC) has
Vector Directory Number (VDN) as
destination.
1357 LAGT COR/COR There is a COR-to-COR restriction UID Call ID
restriction between the originating logical
agent and the terminating facility.
1358 ASAI SCC term First leg of Adjunct Switch UID Call ID
loginID Application Interface (ASAI) Switch
Classified Call (SCC) attempting to
terminate to logical agent loginID.
This is not allowed.
1359 LoginID extensn Failure to determine if the loginID UID Call ID
qry fail extension used for the Direct Agent
call is associated with a logged-in
agent.
1360 ASAI SCC term First leg of Adjunct Switch UID Call ID
loginID Application Interface (ASAI) Switch
Classified Call (SCC) attempting to
terminate to logical agent loginID.
1361 Page data call Paging is denied if data call UID Call ID
preindictd preindication was activated.
1362 FAC follows Priority feature activation code must UID Call ID
priority FAC not be followed by other feature
activation codes. (auth)
1363 SIP Agent logins Maximum number of simultaneous UID Number of
max’d SIP EAS Agent logins exceeded.
SIP Agents
1364 Not priority Priority feature activation code must UID Call ID
destination not be followed by other feature
activation codes. (other)
Table continues…
Denial events

event log (keyword)
1365 More digits needed Adjunct Switch Application Interface UID Call ID
to rte (ASAI) call. Need more digits to
route on. There are no digits left to
use in the preprocessing buffer, and
no more digits are expected.
1366 BCC Auth code entered. Bearer UID Call ID
incompatibility Capability Class (BCC)
incompatibility.
1367 BCC No auth code entered. UID Call ID
incompatibility Bearer Capability Class (BCC)
incompatibility.
1368 MFC out dialing Outgoing MultiFrequency UID Call ID
timeout Compelled call under outpulse
supervision. Interdigit or end-of-
dialing timeout without any
expectation of user completing
dialing.
1369 Dgt tmout PCOL Unexpected digit timeout. Drop of UID Call ID
merge fail principal finds that it is a Personal
Central Office Line (PCOL) group
User ID. Merge of PCOL member(s)
into the call fails.
1370 Digit timeout - Unexpected digit timeout. Drop of UID Call ID
drop fail non-Personal Central Office Line
(PCOL)-type principal failure.
1371 Abbrv Dial DAC Abbreviated Dialing was already dial UID Call ID
limit accessed. The DAC can be dialed a
maximum of 3 times to get the digits
to route to.
1372 Abbrv Dial list/ Abbreviated Dialing. Invalid list UID Call ID
entry inv and/or list entry.
1373 Abbrv Dial Abbreviated Dialing. Software error UID Call ID
software fail while retrieving the digits stored in
the user’s abbreviated dial list.
1374 Agent skills Error while querying for system UID Call ID
enabled qry parameters to see if Expert Agent
Selection (EAS) agent skills is
enabled.
1375 Dbl agent login to Agent is logging into a station that is UID Call ID
statn already logged in by another agent.
Table continues…
Denial Events

event log (keyword)
1376 Agent login illegl Trunk user or Remote Access user UID Call ID
source trying to do Expert Agent Selection
(EAS) agent login operation. This is
not allowed.
1377 Last ACD call Query for last Automatic Call UID Call ID
skill qry Distribution (ACD) call’s skill fails.
1378 No hunt grp for Split group index from dialed UID Call ID
split idx digits is a non-existent hunt group
number.
1379 Agent logout fail Agent logout failure. Might be UID Call ID
(auto?) logging out while auto-available.
1380 Agent login Agent login failure retrieving number UID Call ID
failure of digits in logical agent’s password.
Login-id User ID was not found
or invalid logical agent login-id
extension.
1381 Agent login Possible causes: UID Call ID
failure
• An agent logging into MCH split or
adjunct controlled split is already
logged in
• The Expert Agent Selection
(EAS) Enabled field on system-
parameter features form is n
1382 agent login Login invalid or error condition. UID Call ID or
invalid/error Login-id in
packed
nyble format
1383 Agent login Logical Agent (LAGT) failure getting UID Call ID
failure/error agent login-id. Possible causes:
• error initializing agent-stat table
• login for a skill failed
• TRAD logging into split already
logged into
• already logged into maximum
number of splits.
1384 Agent logins Maximum number of simultaneous UID Current
maximum'd logins exceeded or agent login count of
failed. logged-in
agents
Table continues…
Denial events

event log (keyword)
1385 Agent passwd Failure retrieving logical agent UID Call ID
digits fail password digits from Dial Plan
Manager.
1386 Agent passwd Agent’s password does not match UID Call ID
mismatch administered password.
1387 Agent login Login invalid or error condition. UID Call ID
invalid/error
1388 Login acceptance Logical Agent login processing of UID Call ID
fails agent login message fails.
1389 Agent login max/ Maximum number of simultaneous UID Call ID
Communica error logins exceeded, or the agent failed
tion the login digits check, for example,
Manager this agent is using someone else’s
Release 2.2 login-id.
and earlier
1389 Agt CMS/BCMS login Non-EAS ACD split agent. Login UID Call ID
Communica err processing failed.
tion
Manager
Release 3.0
and later
1390 Work mode change Change of Agent Work Mode to UID Call ID
failed after-call-work failed.
1391 Work mode change Change of Logical Agent Work UID Call ID
failed Mode to aux-work failed.
failed manual-in failed.
failed auto-in failed.
1394 Agent feat act FAC Unrecognized Feature Access Code UID Call ID
error processed for Automatic Call
Distribution (ACD) agent feature
activation.
1395 Agent sup assist Agent requesting supervisor assist. UID Call ID
rqst er Possible causes:
• split group invalid
• agent not logged in
• split group has no supervisor
administered
Table continues…
Denial Events

event log (keyword)
1396 Split invalid/ Adjunct Switch Application Interface UID Call ID
agent login (ASAI) requesting supervisor
assistance. Possible causes:
• split group invalid
• agent not logged in
1397 Direct agent call Supervisor assisted call to Expert UID Call ID
setup Agent Selection (EAS) login ID.
Error encountered in setting up
Direct Agent Call.
1398 Direct agent Supervisor assisted call to Expert UID Call ID
calling COR Agent Selection (EAS) login ID.
Direct agent calling Class of
Restriction (COR) check failure.
1399 EAS not enabled Activating Add/Remove Skill feature UID Call ID
with Expert Agent Selection (EAS)
disabled.
1400 EAS not enabled Activating Add/Remove Skill feature UID Call ID
with Expert Agent Selection (EAS)
disabled.
1401 COR_AR_SKL query Activating Add/Remove Skill feature UID Call ID
failure COR_AR_SKL query failed. User ID
structure not found.
1402 Skills COR Activating Add/Remove Skill feature. UID Call ID
restricted User has no Class of Restriction
(COR) permission to Add/Remove
Agent Skills.
1403 Console prmsn, EAS Activating Add/Remove Skill feature. UID Call ID
agent User has no console permission and
is not an Expert Agent Selection
(EAS) Agent. Activator is wrong
type.
1404 LoginID prompt Activating Add/Remove Skill feature. UID Call ID
setup err Error in setting up the prompt for
agent’s loginID.
1405 Skills prompt Setting up prompting for skill UID Call ID
setup err number in the Add/Remove Skills
feature. Error in setting up prompt
for agent’s skills.
1406 LoginID tenant nbr Add agent skills translations. Failed UID Call ID
fail to get the Tenant Number for the
agent’s loginID.
Table continues…
Denial events

event log (keyword)
1407 Skills tenant nbr Add agent skills translations. Failed UID Call ID
fail to get the Tenant Number for the
agent’s skill.
1408 Tenant number Add agent skills translations. Tenant UID Call ID
mismatch Number of the Expert Agent
Selection (EAS) agent’s loginID
does not match the Tenant Number
of the skill added.
1409 Skill level out of Add agent skills translations. Skill UID Call ID
range level out of range.
1410 Short to long Remove agent skills translations. UID Digits
digit mapping Query for Logical Agent’s (LAGT)
failed for the DAC skill number failed.
agent.
1411 DAC skill not Remove agent skills translations. UID Skill number
removable Logical agent’s DAC skill is not
removable.
1412 Skills ftr msg Add/Remove agent skills UID Call ID
failure translations. Add/Remove Skills
feature message sending to station
server failed.
1413 DAC agent dest/ Adjunct Switch Application Interface UID Call ID
split (ASAI) third party direct agent call.
No DAC agent destination or split
specified in message.
1414 DAC agent dgts to Adjunct Switch Application Interface UID Call ID
uid (ASAI) third party direct agent call.
DAC agent digits conversion to User
ID failure.
1415 DAC msg err/agent Adjunct Switch Application Interface UID Call ID
login (ASAI) third party direct agent call.
Possible causes:
• adjunct agent not logged in
• adjunct gave the switch a wrong
agent extension
• adjunct gave the switch a wrong
split extension
1416 Auth code dgt coll Collecting authorization code digits UID Call ID
fail as end-to-end signaling failed.
Table continues…
Denial Events

event log (keyword)
1417 TTR queueing Collecting authorization code digits. UID Call ID
invalid TTR queueing occurred in remote
access. Not valid.
1418 Bsy vfy trk member Error on query for busy status. UID Call ID
Possible causes: trunk member
specified greater than maximum
trunks in group, or corrupted trunk
index.
1419 COS restrctn Rus Class of Service of user does not UID Call ID
Intrsn permit access to Russian Power
Trunk Intrusion feature.
1420 Bsy vfy call merge Merging the busy-verifying call with UID Call ID
fail the busy-verified call. Failure to find
an available called party slot.
1421 Bsy vfy Terminating the busy-verifying call to UID Call ID
termination fail a trunk. Failure to find an available
called party slot.
1422 Bsy vfy Terminating the busy-verifying call UID Call ID
termination fail to a trunk. Error getting the trunk’s
index.
1423 Software invalid Remote user activation/deactivation UID Call ID
stim of a type of attendant
call forwarding. Invalid stimulus
received.
1424 Cfwd dest dgts Activation of call forwarding. Call UID Call ID
storage forward destination address is
incomplete.
1425 Cfwd actvt error/ Activation of call forwarding. Error or UID Call ID
denial denial of activation.
1426 Off prem extension Request remote switch to activate UID Call ID
size CF on one of its local extensions.
Answer Distributed Communication
System (DCS) off-premise station
extension size is defined by
destination digits dialed.
1427 FWDed party Activating call forwarding. Feature UID Call ID
extension nbr button IDs forwarded party
extension number for which a user
ID cannot be found.
Table continues…
Denial events

event log (keyword)
1428 Phys ext not cfwd Logged-in Expert Agent Selection UID Call ID
avail (EAS) agent’s physical extension
is unavailable for any “simple” (on
switch?) call- forwarding.
1429 Rmte cfwd not Disallow remote call-forwarding of UID Call ID
allowed an Expert Agent Selection (EAS)
loginID extension in all cases (for
example, whether the loginID is
logged into a terminal or not).
1430 COS deny cfwd Class of Service of the user UID Call ID
activate does not allow this call forwarding
activation.
1431 Cfwd deact not Expert Agent Selection (EAS) UID Call ID
allowed agents are not permitted to
deactivate call forwarding.
1432 Cfwd deact err/ Deactivation of call forwarding. Error UID Call ID
denial or denial of deactivation.
1433 Held xfr call Converse Data Return requires that UID Call ID
missing there be a call held due to transfer
while processing the Converse Data
return code (CONV_DAT_RET).
1434 Held call Converse Data Return processing UID Call ID
retrieval fail failed to retrieve the suspended call
record from the SD for the held call.
The held call must be active on a
Converse vector step.
1435 Invalid vec step Converse Data Return processing UID Call ID
typ/pty encountered an invalid vector step
type or the party is invalid.
1436 No COS for ctl User Class of Service does not UID Call ID
rstrctn allow activation/ deactivation of
controlled restrictions.
1437 Sys parm - dir Directed-call-pickup system UID Call ID
call pkup parameter is not enabled.
1438 Invalid usr dir Directed call pickup attempt from UID Call ID
call pkup invalid user (for example, not a
station or attendant).
1439 Dir call pkup COR Directed call pickup attempt from UID Call ID
rsrtrct user without Class of Restriction
(COR) permission.
Table continues…
Denial Events

event log (keyword)
1440 Dir call pkup non- Directed call pickup attempt on a UID Call ID
station call to an endpoint other than a
station.
1441 Dir call pkup COR Directed call pickup attempt to UID Call ID
rsrtrct a station that has no Class of
Restriction (COR) permission to
accept directed call pickup.
1442 Ring check query Directed call pickup attempt. Failure UID Call ID
failure of query to see if called station is
still ringing before completing the
pickup to it.
1443 COS deny dat pvcy Class of Service of the user does UID Call ID
ftr act not allow activation of the data
privacy feature.
1444 DS0 test call DS0 test call is valid only for UID Call ID
invalid incoming data trunk calls.
1445 Rmt emrg accs to Emergency access call to attendant UID Call ID
attd dny is not permitted from a remote user.
1446 Port ID/UID Facilities Access Test call. Trunk or UID Call ID
mapping fail Touch Tone Receiver (TTR) port id
to User ID mapping failed.
1447 TTR port type Facilities Access Test call - UID Call ID
query fail Touch Tone Receiver (TTR) test.
Communication Manager query for
TTR port type fails.
1448 Tested not trunk Facilities Access Test call - user UID Call ID
or TTR type tested is neither a trunk or
Touch Tone Receiver (TTR).
1449 Vis Imprd Svc Facilities Access Test call - this UID Call ID
incompatibl feature is not compatible with
Visually Impaired Service.
Table continues…
Denial events

event log (keyword)
1450 FAT call error Facilities Access Test call. Possible UID Call ID
causes:
• Communication Manager error
connecting to tone or maintenance
timeslot
• necessary number of digits not
dialed for tone or timeslot call
• on trunk or Touch Tone Receiver
(TTR), call conversion of external
ID to internal ID failed, or port id to
User ID mapping failed.
1451 Connection to Facilities Access Test call to a music UID Call ID
music error port. Communication Manager error
connecting to music.
1452 FAT non-ISDN COR Facilities Access Test (FAT) call to UID Call ID
rstrct a trunk. User is Class of Restriction
(COR) restricted from making a FAT
test of the non-ISDN trunk.
1453 FAT test RLT/DID Facilities Access Test (FAT) call to UID Call ID
illegal a trunk. FAT is not allowed for a
Release Link Trunk (RLT) or Direct
Inward Dialing (DID).
1454 Trk svc state Facilities Access Test call to a trunk. UID Call ID
change fail Failure moving trunk from out-of-
service state to in-service. Might be
a bad User ID.
1455 FarEnd TstLn nbr Facilities Access Test call to a PRI UID Call ID
qry fail trunk. Query for far end ISDN test
line number failed (QTC_NUM).
invalid trunk. Invalid digit in far end test line
number.
invalid trunk. Invalid digit in far end test line
number.
1458 Wrg Bch Facilities Access Test (FAT) call UID Call ID
svc/usg/mnt state to a PRI trunk. Wrong B-Channel
service, usage, or maintenance
state to allow FAT test.
1459 Bad user Id Facilities Access Test call to a trunk. UID Call ID
Possible bad User ID.
Table continues…
Denial Events

event log (keyword)
1460 Trk grp qry/get Facilities Access Test call to a UID Call ID
TAC fail trunk. Failure of query to get trunk
group User ID or failure to get
trunk group’s “real” dial access code
(DAC).
1461 User Cverage path User activating Send All Calls does UID Call ID
missing not have coverage path allowing
Send All Calls. If user is an
Expert Agent Selection (EAS) agent,
neither the agent or station has a
coverage path.
1462 Split group digits User activating/deactivating Position UID Call ID
wrong Busy. Wrong number of digits used
to specify split group.
1463 Agent denied in Agent deactivating Position Busy, UID Call ID
split grp not allowed in split group.
1464 Agent not in aux Agent not in AUX_WORK activating UID Call ID
work Position Busy.
1465 Feature Invocation Send All Calls (SAC) or Position UID Call ID
Failed Busy feature activation/deactivation
denied (for example, attendant is
not allowed to activate/deactivate
SAC).
1466 No call to xfr to Route transferred or call UID Call ID
AUDIX conferenced to AUDIX. There is no
held call that would be transferred/
conferenced in with AUDIX.
1467 No call to xfr to Route transferred or call UID Call ID
AUDIX conferenced to AUDIX, but the
calling party was disconnected.
1468 Inelgbl invoker Route transferred or conferenced UID Call ID
xfr AUDIX call to AUDIX. Only the principal or
covering user (or bridges of them)
are allowed to invoke this feature.
1469 Invld remote ADX Route remote transfer to AUDIX. UID Call ID
mach-nbr Failure getting the remote principal’s
AUDIX Machine number.
1470 No ADX mach-nbr/ Route remote transfer to AUDIX. UID Call ID
node-name The remote principal’s AUDIX
Machine number does not translate
into an adjunct index.
Table continues…
Denial events

event log (keyword)
1471 Invalid AUDIX mach- Route remote transfer to AUDIX. UID Call ID
nbr The remote principal’s AUDIX
Machine number received is “0."
Query for user’s serving AUDIX
index fails.
1472 Invalid AUDIX mach- Route remote transfer to AUDIX. UID Call ID
nbr The remote principal’s AUDIX
Machine number received is “0.
“Query for user’s serving AUDIX
index returned “0.” Query for the first
AUDIX whose DCS link is up fails.
1476 Dat pvcy/rstrct User with data privacy or data UID Call ID
ICOM call restriction is trying to originate an
ICOM call. This is not allowed.
1477 Invalid ICOM grp/ ICOM call handling. Invalid ICOM UID Call ID
dial cod group or ICOM dial code of
terminating station.
1478 Block iteratve Lst Last Number Dialed was accessed UID Call ID
Nbr Dl through an Abbreviated Dialing list.
Do not allow it again.
1479 LND digits - DPM User’s Last Number Dialed (LND) UID Call ID
fail digits were not returned successfully
by dial plan manager.
1480 LND digits - DPM User’s Last Number Dialed (LND) UID Call ID
fail digits were not returned successfully
by dial plan manager. (software
error)
1481 MASI setup not Multimedia Application Server
incmg ISDN Interface (MASI) path setup call -
valid only for incoming ISDN calls.
1482 MCT on DCS trk User activating Malicious Call Trace UID Call ID
disallowed for a DCS trunk not allowed.
1483 MCT target type Malicious Call Trace target cannot UID Call ID
invalid be a group User ID. Must be a
regular trunk port or PRI.
1484 MCT target not in Malicious Call Trace target must UID Call ID
a call actually be involved in a call.
1485 MCT call serv_d Malicious Call Trace, cannot retrieve UID Call ID
rtrv fail call record for the call traced.
1486 MCT trace resorce Malicious Call Trace activation by UID Call ID
unavail button cannot get trace resources.
Table continues…
Denial Events

event log (keyword)
1487 MCT start invld Malicious Call Trace. Invalid UID Call ID
ctlr alrt controller alerting return code.
1488 MCT deact dny by Malicious Call Trace deactivation UID Call ID
GRP_M/er (not via busyout) denied or error.
1489 MCT activator grp Malicious Call Trace activation UID Call ID
uid/uid failure getting individual User ID
from activator group User ID.
1490 MCT activator COR Malicious Call Trace (MCT) UID Call ID
rstrctd activation. Activator’s Class of
Restriction (COR) does not allow
MCT feature access.
1491 Trk ext/int ID Malicious Call Trace request UID Call ID
cnvsn fail targeted to a trunk port ID. Failure
converting the external ID (gateway
#, Media Module, slot, circuit) into
an internal ID (angel, circuit).
1492 MCT act on trk pt Malicious Call Trace request UID Call ID
ID fail targeted to a trunk port ID. Failure
activating MCT for given trunk port
ID.
1493 AD prg from non Abbreviated dialing programming is UID Call ID
station messaging the station server to
enter a different mode and prepare
for digit collection. Only simple
users allowed. Wrong user type.
1494 Extension/passwd Coverage message retrieval. UID Call ID
required Remote access not allowed unless
the user supplies the extension and
password.
1495 Local only/annc Announcement record/playback UID Call ID
dest/uid session. Only local calls to
the announcement are allowed.
Call destination must be an
announcement group. Must have a
User ID slot for the announcement
board.
1496 Annc ID needed/ Begin integrated announcement UID Call ID
conn fail session. Integrated announcement
not identified.
Table continues…
Denial events

event log (keyword)
1497 Restricted by COS User’s Class of Service does not UID Call ID
permit one of:
• Leave Word Calling-cancel
• AP Demand Print
• voice synthesis principal message
retrieval
• voice synthesis coverage
message retrieval
• integrated announcement session
1498 MM call software MultiMedia Call Handling multimedia UID Call ID
failure call activation from voice station.
Notification of user manager failed.
1499 MM failure getting MultiMedia Call Handling multimedia UID Call ID
BCC call activation from voice station
button. Failure getting bearer
capability.
1500 Ext nbr or page Failure getting Code Call paging ID UID Call ID
typ invld corresponding to dialed extension.
Invalid extension number or page
type.
1501 Page call park Drop paging equipment, start park UID Call ID
failure timer, and park call permanently.
There is no record of a call having
been parked during a page.
1502 Drop software Paging zone seizure denied. Invalid UID Call ID
failure return code.
1503 Answer back merge Answer parked call, give UID Call ID
failure confirmation tone to parked party,
merge 2 calls. Have no call record
of party originating answer back.
merge 2 calls. No call parked on this
extension.
merge 2 calls. Unknown return from
query to retrieve Call ID of the
parked call.
Table continues…
Denial Events

event log (keyword)
merge 2 calls. Unknown return from
query to unpark call if the last party
drops.
merge 2 calls. Accessing the call
record of the parked call failed.
1508 Unparking vec Answer parked call, give UID Call ID
ctrld call confirmation tone to parked party,
merge 2 calls. Deny the unpark
(answer back) attempt if the parked
call is under vector control.
1509 Answr back station Answer parked call, give UID Call ID
dialed confirmation tone to parked party,
merge 2 calls. User ID of station
dialed for answer back differs from
the park user id in the call record.
1510 COR/COR user Answer parked call, give UID fail code(for
restricted confirmation tone to parked party, example,
merge 2 calls. COR-to-COR (Class DPXFR_DE
of Restriction) between user where NY_9)
call is parked and users in answer
back call record
1511 Parked call Answer parked call, give UID Call ID
already dropd confirmation tone to parked party,
merge 2 calls. The parked call was
already dropped by the originator
but the chimes haven’t finished yet.
1512 Too many parties Answer parked call, give UID Call ID
to merge confirmation tone to parked party,
merge 2 calls. The merge is not
possible because resources are not
available.
1513 Park call on Trying to park a call on a non-station UID Call ID
station only type user. Must park on a user with
a simple group type.
1514 No call to park There is no conference pending. UID Call ID
The caller to be parked must have
dropped or been dropped.
1515 Park ftr serv_d Failure encountered releasing the UID Call ID
failure call record to the service dispatcher.
Table continues…
Denial events

event log (keyword)
1516 Park ftr serv_d Failure encountered retrieving the UID Call ID
failure call record from the service
dispatcher.
dispatcher.
1518 Too many park Too many conferees in the call to UID Call ID
conferees allow parking.
1519 Vector active cant Vectoring is active on the held call. UID Call ID
park Cannot allow the held call to be
parked.
1520 Park ftr serv_d Failure encountered releasing the UID Call ID
failure call record to the service dispatcher.
dispatcher.
1522 TAAS from guest Pickup for Call Pickup or Trunk UID Call ID
room Answer Any Station (TAAS).
Attendant backup alerting is active,
maid status is dialed from guest
room on station doing pickup. Might
be maid is invoking TAAS from
guest room.
1523 Not a pickup grp Pickup for Call Pickup or Trunk UID Call ID
mbr Answer Any Station (TAAS). Pickup
initiator is not a member of a pickup
group.
1524 Picked up call ID Pickup for Call Pickup or Trunk UID Call ID
error Answer Any Station (TAAS). Error
encountered getting call ID of call to
be picked up.
1525 Call pickup from Pickup for Call Pickup or Trunk UID Call ID
adjnct Answer Any Station (TAAS). Pickup
of call originated by an adjunct is not
allowed.
1526 Pickup of call Pickup for Call Pickup. Pickup of a UID Call ID
wait call call waiting call is not allowed.
Table continues…
Denial Events

event log (keyword)
1527 Pickup of converse Pickup for Call Pickup or Trunk UID Call ID
call Answer Any Station (TAAS). Trying
to pickup a converse call, this is not
allowed. Passing data efficiently to
a party that has already cut through
on the call cannot be handled.
1528 Pickup of self's Stations A and B are in same pickup UID Call ID
call group. Station A calls Station B,
holds, and dials Feature Access
Code for pickup. Disallow pickup of
self-initiated call.
1529 Pickup COR/COR usr Pickup for Call Pickup or Trunk UID fail code(for
rstrct Answer Any Station (TAAS). COR- example,
to-COR (Class of Restriction) DPXFR_DE
restriction between the initiator of NY_9)
pickup and user or users of the call
picked up.
1530 Priority call COS Class of Service of the caller does UID Call ID
denied not allow initiation of priority calling
treatment of call.
1531 Priority call COS Caller pushes the priority calling UID Call ID
denied button after the call is dialed, but
before it is answered. Class of
Service of the caller does not allow
initiation of priority calling treatment
of call.
1532 Passwd storage Dual Tone MultiFrequency (DTMF) UID Call ID
exhausted password collection for audio add-
on party in VSP-MCU passworded
conference. No room to store
conference password.
1533 Invalid TTR Dual Tone MultiFrequency (DTMF) UID Call ID
queueing type password collection for audio add-
on party in VSP-MCU passworded
conference. Touch Tone Receiver
(TTR) queuing type in call record
has invalid indication whether/where
TTR queuing occurred.
1534 Software invalid Performing the callback of a UID Call ID
stim party after the call has been
queued. Invalid Call Processing
(CP) message processed and
passed from a call supervisor.
Table continues…
Denial events

event log (keyword)
1535 ACB held call Analog station flashooks and dials UID Call ID
dropped Automatic Callback (ACB) activation
Feature Access Code. The call from
which the user flashed is to be
removed from hold and used to
activate ACB. The call didn’t get
held or it disappeared.
1536 GRP_M que service Automatic callback cannot be UID Call ID
error initiated.
1537 Callback type sftw Invalid callback type returned from UID Call ID
error query().
1538 Auto callback COS User’s Class of Service does UID Call ID
denied not allow activation of Automatic
Callback feature.
1539 Callback type qry Query for callback type failed. UID Call ID
failed
1540 Callback type qry Invalid callback type returned from UID Call ID
failed query().
1541 Invalid call ID/ Switch has answered remote UID Call ID
conn fail access call. Set up end-to-end
signaling digit collection. Invalid Call
ID or Touch Tone Receiver (TTR)
connection failure.
1542 TTR queueing error Switch answered a remote UID Call ID
access call. Set up end-to-end
signaling digit collection. Touch
Tone Receiver (TTR) queueing
erroneously occurred.
1543 Telcmt accss ext Switch answered a remote access UID Call ID
qry fail call and set up end-to-end signaling
digit collection. Query failure for
User ID of telecommuting access
extension.
1544 Barrier/auth cod Switch answered a remote access UID Call ID
qry fail call and set up end-to-end signaling
digit collection. Invalid response
from query for whether barrier code
and authorization code are needed.
1545 Acct code length Query of Dial Plan Manager for UID Call ID
qry fail SMDR account code length failed.
Table continues…
Denial Events

event log (keyword)
1546 Held call serv_d Cannot retrieve the call record of the UID Call ID
failure held call from the service dispatcher.
Software error.
1547 Video conf deact T120 request for deactivation of UID Call ID
flag err video conference, but the call
has no indication that a video
conference exists.
1548 Dat drop not frm T120 request for deactivation of UID Call ID
dat orig video conference. It is only valid
to drop data from the originator of
data. The user who pressed the
button is not the originator.
1549 T120 drop CM Communication Manager failure on UID Call ID
failure T120 drop request from valid user
with T120 on. Possible failures:
• Cannot locate service ID
• Call does not have a conference
associated with it
• Wrong conference type
• T120 was not activated
1550 T120 activate CM Communication Manager failure UID Call ID
failure on Feature Access Code dialed
request for T120 activation. Possible
causes:
• Cannot locate service ID
• Call does not have a conference
associated with it
• Wrong conference type
• T120 already activated
• Resources not available
1551 Invalid test tone Terminating trunk transmission test UID Call ID
specfd call. Invalid test tone specified for
connection to the call.
1552 Whisp pg elgblity Query for whisper page eligibility UID Call ID
qry err encountered an error or the
response was invalid.
1553 Whisp pg too many Cannot find the call record slot with UID Call ID
parties the user ID of the page originator.
Table continues…
Denial events

event log (keyword)
1554 Whisp pg ansr Switch of the Call ID of the paging UID Call ID
merge fail party from the original call failed.
1555 Whisp pg too many Merging the paging call with the UID Call ID
parties paged call. Called party block has
no slot available for the merged call.
1556 Annc/music connect Wakeup announcement verification. UID Call ID
fail Failure of Communication Manager
to connect a wakeup announcement
or music to the call.
1557 Wakeup annc vfy Call originator does not have Class UID Call ID
COS deny of Service permission to verify
wakeup announcements.
1558 Maid status PMS Sending the PMA maid service UID Call ID
msg fail status message to the PMS failed.
1559 Maid status ext Maid status Feature Access Code UID Call ID
COS deny dialed from a room station that
does not have Class of Service
permission.
1560 Maid info digits Query failed for number of maid UID Call ID
qry fail information digits.
1561 Maid status PMS PMA maid status update failed. UID Call ID
msg fail Possible causes:
• No record available
• Invalid digits
• Invalid user ID
1562 Maid status ext Maid status Feature Access Code UID Call ID
COS deny dialed from a designated station that
does not have Class of Service
permission.
1563 Maid status ftr ID Processed the dialed maid status UID Call ID
invld code, but call record feature ID
is invalid for either maid status
dialed from a guest room or from a
designated station.
1564 PMS rejects hskp Property Management System UID Call ID
status rejected the housekeeping status
message.
1565 PMS hskp response Property Management System UID Call ID
invalid response to housekeeping status is
invalid.
Table continues…
Denial Events

event log (keyword)
1566 Guest rm station Routing call to Property UID Call ID
COS deny Management System to log or
obtain guest room status. The User
ID of the station entered by the user
is not Class of Service identified as
a guest room station.
1567 Maid info digits Routing call to Property UID Call ID
qry fail Management System to log or
obtain guest room status. Query for
number of maid information digits
failed.
1568 Maid status PMS Routing call to Property UID Call ID
msg fail Management System (PMS) to log
or obtain guest room status. Send of
a PMA maid status update message
to the PMS failed.
1569 Voice msg type Digit timeout waiting for entry of Do UID Call ID
call_r flg Not Disturb turn-off time or entry
of Automatic Wakeup time. The call
record does not have this flagged as
a Voice message type call.
1570 (also TTR insertion Processing incoming digits for UID Call ID
in ISDN, IP, failed ISDN call. Insertion of Touch Tone
and SIP Receiver (TTR) to collect in-band
denial digits failed.
events on
page 164)
1572 Call hndlng/usg Processing incoming digits for UID Call ID
alloc err ISDN call. Error during Incoming
Call Handling Treatment or Usage
allocation Check.
1573 (also Principal is not Get called digits, calling number UID Call ID
in ISDN, IP, ISDN and name, etc., and send ISDN
and SIP SETUP message to the far end. The
denial principal is not ISDN.
events on
page 164)
1574 SETUP msg IEs not Get called digits, calling number UID Call ID
created and name, etc., and send ISDN
SETUP message to the far end. IEs
necessary for SETUP not created.
Table continues…
Denial events

event log (keyword)
1575 SETUP msg send Get called digits, calling number and UID Call ID
failed name, etc., and send ISDN SETUP
message to the far end. The “send”
failed.
1576 ISDN routing Get called digits, calling number and UID Call ID
failure name, etc., and send ISDN SETUP
message to the far end. Routing
failure.
1577 ISDN SETUP msg Failure in sending the ISDN SETUP UID Call ID
failure message.
1578 Inc tst call 2many Incoming test call for talk/listen on UID Call ID
partys same timeslot. Failure to find an
available call party slot.
1579 Inc tst call wrg Incoming test call for talk/listen on UID Call ID
usr type same timeslot. This type of test call
is not permitted to access the user
type.
1580 Must be ISDN trunk Check for usage allocation UID Call ID
group restrictions on incoming overlap
receiving calls. Possible causes:
• not ISDN trunk group
• insane index into the call by call
data table
• failure from group manager
• Unexpected error)
1581 Passwd digits err/ MCU audio add-on password UID Call ID
timeout supervision. Possible causes:
• digit timeout before collecting all
the digits
• an invalid digit
• a set of digits that does not match
the conference password
1582 Spvsr state/ Generating intercept tone. Possible UID Call ID
feat_id wrong causes:
• wrong supervisory state
• wrong feature ID in call record
Table continues…
Denial Events

event log (keyword)
1583 Spvsr state/ Generating intercept tone. Possible UID Call ID
feat_id wrong causes:
• wrong supervisory state
• wrong feature ID in call record
1584 Software invalid Software error. Invalid Call UID Call ID
stim Processing stimulus received while
in supervision state that handles
Terminal Translation Initiation (TTI)
digit collection during dialing of the
TTI security code and extension.
1585 Abbrv Dial invalid Invalid digit detected while UID Call ID
digit processing abbreviated dialing.
1586 Abbrev dial prg Rejection of abbreviated dialing UID Call ID
rejected programming from station server.
1587 Agent extension Add/Remove Agent Skills. Feature UID Call ID
invalid Access Code was dialed by a user
with console permissions, but the
agent-loginID extension entered is
not a valid Expert Agent Selection
(EAS) AGENT extension.
1588 Skill grp nbr Add/Remove Agent Skills feature UID Call ID
illegal has been invoked and the Skill
number has been collected. It does
not represent a legal skill group
number.
1589 Skill number Add/Remove Agent Skills feature UID Call ID
invalid has been invoked and the Skill
number is not valid.
1590 System or software Add/Remove Agent Skills feature UID Call ID
error has been invoked. System or
software error.
1591 Digit collection Add/Remove Agent Skills feature UID Call ID
error has been invoked. Error in digit
collection.
1592 Routing not to a QSIG Call Completion ringout UID Call ID
station call from remote originating party.
Routing erroneously to a local
facility that is not an simple station.
Table continues…
Denial events

event log (keyword)
1593 Digit tmo/invld Interdigit timeout or invalid reason UID Call ID
rsn code code entered during Expert Agent
Selection (EAS) aux work and
logout reason code digit collection is
in progress.
1594 Software invalid Code Call paging seizure UID Call ID
stim supervision received a Call
Processing (CP) stimulus from one
of a large list of incompatible feature
CP stimuli.
1595 Cfwd tenant parttn Attendant-activation of call UID Call ID
rstrct forwarding, and extended
administration of call forwarding.
Error or access denial resulted
from TENANT_CHECK whether
originator’s partition is restricted
from accessing partition of
extension administered for call
forwarding.
1596 Attd must enter Attendant-activation of call UID Call ID
station forwarding, and extended
The extension administered is not a
simple station user.
1597 Attd cant fwd attd Attendant-activation of call UID Call ID
calls forwarding, and extended
Attendant is not allowed to forward
its own calls.
1598 Feature ID invalid Attendant-activation of call UID Call ID
forwarding, and extended
The feature ID in the call record
is wrong for the Call Processing
(CP) stimulus processed by this
supervisor.
1599 Change cvg COR Attendant-activation of call UID Call ID
restricted forwarding, and extended
Change coverage Feature Access
Code was dialed. Class of
Restriction (COR) of dialed
extension does not permit change
coverage.
Table continues…
Denial Events

event log (keyword)
1600 Software error Attendant-activation of call UID Call ID
forwarding, and extended
Update in station server to
administer the new active coverage
option failed.
1601 Software invalid Attendant-activation of call UID Call ID
stim forwarding, and extended
Invalid Call Processing (CP)
stimulus type sent to this supervisor.
1602 Cfwd act to paging Call forwarding supervision. UID Call ID
grp NA Activating call forwarding to a
paging group is not allowed.
1603 Cfwd offnet COS Call forwarding supervision. UID Call ID
restrcted Activating call forwarding off-net is
not allowed for this user. check the
Class of Service permissions.
1604 Cfwd offnet COS Call forwarding supervision. UID Call ID
restrcted Activating call forwarding off-net via
AAR/ARS is not allowed for this
user. Check the Class of Service
permissions.
1605 Cfwd to self Call forwarding supervision. Call UID Call ID or
denied forwarding to self is prevented. temporary
failure
unique
number
1606 Software error Call forwarding supervision. Invalid UID Call ID
feedback message type received.
1607 Software invalid Call forwarding supervision. invalid UID Message
stim Call Processing (CP) stimulus type Type
sent to this supervisor.
1608 Routing not to The “routed to” party is not a Data UID Call ID
data user User.
1609 Local rtg must be QSIG Call Completion ringout call UID Call ID
to sta from the remote originating party.
Routing locally, but not to a station.
1610 Party count not = Prepare to collect deluxe paging UID Call ID
1 & park extension. Invalid paging
message type.
Table continues…
Denial events

event log (keyword)
1611 Not MM station/ Attempt to send the MultiMedia UID Call ID
chnl busy Call Handling Basic mode activation
message fails. Possible causes:
• station not part of Multi-media
• data user busy on at least one
channel.
1612 Svc link creation Attempt to send the MultiMedia UID Call ID
failure Call Handling Enhanced mode
deactivation message fails. Might be
the creation of a service link failed.
1613 BCC query failed MultiMedia Call Handling UID Call ID
multinumber type call. Query for
bearer capability failed.
1614 Ctrl rstrct/DND Controlled restriction activation/ UID Call ID
fail deactivation with possible
interaction with do-not-disturb.
Possible causes:
• originator’s User ID not found
• invalid feature ID
• if an attendant group, controlled
restriction activation is not allowed
1615 Rstrct typ/ Initial processing supervision for UID Call ID
featid/usr id controlled restriction. Possible
causes:
• originator’s User ID not found
• restriction digit does not identify
with outward, total, termination or
station-to-station type restriction
• feature ID is not one of:
- activate user control restriction
- deactivate user control
restriction
- activate group control restriction
- deactivate group control
restriction
Table continues…
Denial Events

event log (keyword)
1616 Ctrl rstrct featid Initial processing supervision for UID Call ID
bad controlled restriction. Feature ID is
not one of:
• activate user control restriction
• deactivate user control restriction
• activate group control restriction
• deactivate group control restriction
1617 Dialing tmo/ Supervisor for Logical Agents is UID Call ID
invalid digit logging in by dialing LoginID digits.
Dialing timeout occurs or an invalid
digit is dialed.
1618 Paging timeout Loudspeaker paging seizure UID Call ID
supervision. Might be a paging
timeout.
1619 LWC access cod dgt Supervision for Leave Word Calling UID Call ID
invld access code processing. Invalid
digit dialed.
1620 LWC access code Supervision for Leave Word Calling UID Call ID
rejected access code processing. Access
code rejected.
1621 Software invalid Invalid Call Processing message UID Call ID
stim sent to Malicious Call Trace
supervisor.
1622 BCC selection Supervision for multimedia UID Call ID
digit invld parameter selection. Invalid digit
dialed for selecting bearer capability
for call.
1623 MM parm select Supervision for multimedia UID Call ID
failure parameter selection. failure.
1624 Backward tone Trunk outpulsing supervision. UID Call ID
absent tmo Outgoing backward tone absent.
Timeout on MultiFrequency
Compelled digit sending.
1625 7 min tmo - no Trunk outpulsing supervision. No UID Call ID
tone rcvd tone has been detected within 7
minutes after dialing Trunk Access
Code of a Cut Through Central
Office (CO) or Foreign Exchange
(FX) trunk.
Table continues…
Denial events

event log (keyword)
1626 MFC trk seize Trunk seizure supervision on UID Call ID
failure outgoing trunks. MultiFrequency
Compelled trunk seizure failure.
1627 Out trk seize dgt Trunk seizure supervision on UID Call ID
invld outgoing trunks.
1628 7 min tmo - no Trunk seizure supervision on UID Call ID
tone rcvd outgoing trunks. No tone has been
detected within 7 minutes after
dialing Trunk Access Code of a
Cut Through Central Office (CO) or
Foreign Exchange (FX) trunk.
1629 7 min tmo - no Supervision when there is a tone UID Call ID
tone rcvd detector on the call. A wait timer has
been set for a VOICE user, or a data
call over a trunk is waiting for a Stall
Answer feedback to DEXT. No tone
has been detected within 7 minutes
after dialing the Trunk Access Code
of a Cut Through Central Office
(CO) or Foreign Exchange (FX)
trunk.
1630 Onhk que spvsn Queued call or anticipated manually UID Call ID
invld dg queued call has an invalid digit.
1631 Rmt ACB ftr act Queued call or anticipated manually UID Call ID
timeout queued call sees timeout waiting
for remote drop by activator of
Automatic Call Back feature.
Table continues…
Denial Events

event log (keyword)
1632 PASTE enbl/rstrct/ Possible causes: UID Call ID or
usrtyp NULL
• PC Application Software
Exchange (PASTE) not enabled
• attendant use of PASTE is not
allowed.
• station Class of Restriction (COR)
does not allow PASTE
• totally restricted station cannot
use PASTE
• station has no display
• bridge appearance cannot use
PASTE
• agent not in AUX cannot use
PASTE
• COR restricted for PASTE
1633 Digit tmo/list nbr Inter-digit timeout or invalid UID Call ID
invld list number entered during PC
Application Software Exchange
(PASTE) display list number
collection.
1634 Software invalid Supervision after position busy UID Call ID
stim (de)activation dial access code has
been recognized. Collecting more
digits. Invalid Call Processing (CP)
stimulus type sent to this supervisor.
1635 Extension type qry Refresh Terminal Parameters UID Call ID
fail supervision. The query to get the
extension type failed.
1636 Not a downloadable Refresh Terminal Parameters UID Call ID
set supervision. Port type is not a valid
downloadable station port type. Only
8400/6400/4600/603 type stations
and the 302 type attendant consoles
are allowed.
Table continues…
Denial events

event log (keyword)
1637 Wrt prot/maxd/annc Supervision for announcement UID Call ID
bd record/playback session processing.
Possible causes:
• announcement is write/delete
protected
• invalid feature type or not the
same Call ID that is in the session
• Communication Manager port
connection failure
• invalid Call ID root
disconnect failure
listen failure
• no announcement board
• maximum number of
announcements already recorded
1638 Record playback Supervision for announcement UID Call ID
reject record/playback session processing.
Call processing reject stimulus
received from somewhere.
1639 Permanent seizure Standard action stimulus UID Call ID
processing. Non-Direct Inward
Dialing trunk origination. Digit
timeout with no digits dialed.
The permanent incoming seizure
treatment is to give intercept.
processing. Italian external tie
(TGU) call. Digit timeout with
no digits dialed. The permanent
incoming seizure treatment is to
give intercept.
Table continues…
Denial Events

event log (keyword)
processing. Trunk group type other
than: DID, internal TIE, external
TIE, tandem TIE, ACCESS, internal
APLT, external APLT, ISDN PRI, or
DIOD. Digit timeout with no digits
dialed. The permanent incoming
seizure treatment is to give
intercept.
1642 Ofhk alrt tmo Standard action stimulus UID Call ID
intvl admin processing. Station, attendant or
analog adjunct data extension
originator. Off-hook alert feature
activation. No off-hook alert timeout
interval administered.
1643 Off-hook dialing Standard action stimulus UID Call ID
time out processing. originator group type
not trunk, DEXT, SMPL(station), or
attendant. DEXT, SMPL, attendant
does not Class of Service allow
off-hook alert, processing a digit
timeout for Line Intercept Tone
timer.
1644 Orig block/invalid Standard action stimulus UID Call ID or
digits processing. Originator group type Message
not trunk, DEXT, SMPL(station), Type|root
or attendant. DEXT, SMPL, ATTD Call ID
does not Class of Service allow off-
hook alert and NOT processing a
digit timeout for Line Intercept Tone
timer.
1645 Talk state MFC trk MultiFrequency Compelled trunk UID Call ID
fail failure after the call is in the talking
state. (called number intercept for
MFC call).
1646 No act call_ap/ One-button transfer to data feature UID Call ID
sftw err activation failed. Possible causes:
• No active call appearance
• Call ID is not on the active call
appearance
• Button is not a data extension
button
Table continues…
Denial events

event log (keyword)
1647 Telcomtr diald Supervisor for telecommuting UID Call ID
illegl FAC access. Telecommuting extension
was accessed, then a Feature
Access Code was dialed that is not
allowed to telecommute.
1648 Ctrl rstrct VDN Supervision for controlled restriction UID Call ID
extension of user. Control Restriction
Activation/Deactivation for a Vector
Directory Number extension is not
allowed.
1649 Ctrl rstrct locl Supervision for controlled restriction UID Call ID
ext only of user. Control Restriction
Activation/ Deactivation must be on
an extension that is local to the
switch.
1650 Rstrct typ/ Supervision for controlled restriction UID Call ID
featid/COR/sta of user. Possible causes:
• Originator’s User ID not found
• Restriction digit does not identify
with outward, total, termination or
station-to-station type restriction
• Feature ID is not one of:
- activate user control restriction
- deactivate user control
restriction
- activate group control restriction
- deactivate group control
restriction
• Class of Restriction (COR)
restricted
• Controlled restriction not allowed
on trunk or attendant group type.
1651 TTI merge/unmerge Station server cannot perform UID Call ID
fail Terminal Translation Initiation (TTI)
merge/unmerge.
1652 LWC access cod dgt Voice synthesis Leave Word Calling UID Call ID
invld access code digit processing saw
an invalid digit. The request was
rejected.
Table continues…
Denial Events

event log (keyword)
1653 TTI - attd not Terminal Translation Initiation (TTI) UID Call ID
allowed unmerge operation is not allowed
from attendants.
1654 TTI - attd not Personal Station Access (PSA) UID Call ID
allowed associate operation cannot be
originated by attendant.
1655 TTI - BRI not Personal Station Access (PSA) UID Call ID
allowed associate operation cannot be
originated by BRI station.
1656 Other calls Personal Station Access (PSA) UID Call ID
active/COS associate operation. If not on a
port, check the Class of Service.
Also check for other calls active on
the station.
1657 TTI - attd not Personal Station Access (PSA) UID Call ID
allowed disassociate operation cannot be
originated by attendant.
allowed disassociate operation. Cannot PSA
disassociate a BRI station.
1659 TTI - COS Class of Service does not allow UID Call ID
restricted Personal Station Access (PSA)
disassociate operation.
allowed associate operation. Cannot PSA
associate a BRI station.
1661 TTI - COS Class of Service of the extension UID Call ID
restricted to be associated does not have
Personal Station Access (PSA)
capability.
1662 Crossing tenant Personal Station Access (PSA) UID Call ID
partition associate operation cannot cross
tenant partitions.
1663 Invalid user ID/ Personal Station Access (PSA) UID Call ID
sftw err associate operation. There is no
extension associated with user ID.
Invalid User ID or software error.
1664 Getting user ID Failure getting the User ID for the UID Call ID or
failed extension dialed in an association/ digits
dissociation step. (extension)
Table continues…
Denial events

event log (keyword)
1665 Data mod usr id Data Terminal Translation Initiation UID Call ID or
qry fail (TTI) call. The query for the real number of
User ID of data module in data digits
extension group failed.
1666 Originator ext not Unmerge sequence initiated. The UID Call ID
dialed extension dialed must be the same
as the originator’s.
1667 Non trunk Proper intercept treatment for non UID Call ID
intercept DID/TIE/ISDN trunk groups, or non-
trunk originators.
1668 Trk needs disc Activate service observing feature. UID Call ID
supervisn Service observing cannot be
activated by a trunk without
disconnect supervision.
1669 Svc obsrv from Activate service observing feature. UID Call ID
attd NA Service observing cannot be
activated by an attendant.
1670 Svc obsrv from Activate service observing UID Call ID
brdg NA feature.Service observing cannot
be activated from a bridged
appearance.
1671 Svc obsrvg svc Activate service observing UID Call ID
obsrvd NA feature.Service observing cannot be
activated by a user that is already
a service observer or is service
observed.
1672 Svc obsrvr/obsrvd Activate service observing feature. UID Call ID
COR dny Activating user’s Class of Restriction
(COR) does not allow it to be
a service observer of intended
observed.
1673 Svc obsrvr COR Activate service observing feature. UID Call ID
rstrct Activator’s Class of Restriction
(COR) check failed.
1674 Svc obsrvr/obsrvd Activate service observing feature. UID Call ID
COR dny Activating user’s Class of Restriction
(COR) does not allow it to be
a service observer of intended
observed.
Table continues…
Denial Events

event log (keyword)
1675 Svc obsrvr Activate service observing feature. UID Call ID
vecstep/extdgt Initiated from a vector step and only
the Feature Access Code of service
observing is in the vector step. End-
to-end signaling digit collection of
extension to be observed failed.
1676 Svc obsrv not on Validation of service observed UID Call ID
ext/VDN extension. Service observing is
allowed only on a simple User ID or
a Vector Directory Number.
1677 Svc obsrv cust opt Validation of service observed UID Call ID
qry extension. Query for service
observing customer-options failed.
1678 Need VDN obsrvg Validation of service observed UID Call ID or
option extension. Vector Directory Number UID
observing is not enabled.
1679 Svc obsrvee data Validation of service observed UID Call ID
rstrctd extension. Observee is data
restricted.
1680 Conf/xfer DPT sig Cannot conference/transfer DPT call UID Call ID
incompl until DMTF signaling is complete.
Communica
tion
Manager
Release 4.0
and later
1681 Svc obsrvee COR Validation of service observed UID Call ID
rstricted extension. Class of Restriction
(COR) of observee restricts
observation.
1682 Svc obsrvd COR chk Validation of service observed UID Call ID
fail extension. Class of Restriction
(COR) check failure.
1683 Svc obsrvr/obsrvd Validation of service observed UID Call ID
COR dny extension. Observer/observee Class
of Restrictions do not allow observer
to observe observee.
1684 Svc obsrvg/obsrvg Validation of service observed UID Call ID or
race extension. The observee is already UID being
in the process of activating service observed
observing for another party.
Table continues…
Denial events

event log (keyword)
1685 Svc obsrv ftr act Validation of service observed UID Call ID or
failure extension. Feature activation of UID being
selected “listen only” or “listen/talk” observed
service observing failed.
1686 Svc obsrv VDN SO Supervision after confirmation tone UID Call ID
wait flg to a service observer. Failure to
set Vector Directory Number (VDN)
Service Observing wait flag in the
VDN’s VDN information block.
1687 Obsrvr conf_state Supervision after confirmation tone UID Call ID
unclear to a service observer. Confirmation
tone is complete for an observer.
Make observer eligible to be taken
off the wait list for the Vector
Directory Number. Failure to clear
the “conf_state” for the observer.
1688 Svc obsrvg/obsrvg Supervision after confirmation UID Call ID
race tone to a service observer.
Bridging observer onto the
agent encountered race condition,
observee is already in the process
of activating service observing for
another party.
1689 Svc obsrv ftr act Supervision after confirmation tone UID Call ID
fail to a service observer. Failure
activating service observing for
observee.
1690 Software invalid Supervision after confirmation tone UID Call ID
stim to a service observer. Invalid Call
Processing (CP) stimulus received
by this supervisor.
1691 Term restriction Processing incoming Call UID Call ID
chk fail Forwarding. All Distributed
message. Other switch had problem
processing call forwarding activation
message. Termination restriction
check failed or cannot convert
designated extension to a user ID.
Table continues…
Denial Events

event log (keyword)
1692 LWCpmsn/UDPext/ Leave Word Calling (LWC) UID Call ID
dpst admin operations generate a confirm and
drop event (INT_DRP). Possible
causes:
• attendant cannot leave DCS
messages
• activator of lwc store does not
have lwc permission
• activator is not a udp ext
• no remote users involved
• LWC store operation remote to
local- Voice Mail Applications
Support is disabled
• called party not administered to
receive LWC messages
• no called party message header
• no LWC depository administered
• error in sending AUDIX STORE
message info (from remote user)
to AAP
1693 Out trk DID orig/ Italian Direct Inward Dial (DID) UID Call ID
sftw err trunk group drop treatment. Possible
causes:
• DID origination on outgoing trunk
• Software error
1694 Sta intrcpt tone Station Intercept Tone Forward UID Call ID
fwd disc Disconnect.
1695 Bsy vfy Cannot busy verify attendants. UID Call ID
sta/trk/hnt grp Only allowed to busy verify simple
stations, trunks, or hunt groups.
1696 Bsy vfy trk grp no Busy verify of trunk failure. Possible UID Call ID
mbr causes:
• No trunk in the group
• Trunk group member not found
1697 Bsy vfy access Busy verification not supported for UID Call ID
endpt trk access endpoint trunk type.
Table continues…
Denial events

event log (keyword)
1698 Bsy vfy hnt grp no Busy verify of hunt group failure. UID Call ID
mbr The hunt group is empty.
1699 LWC msg stor fail Leave Word Calling message UID Call ID
(conf) cannot be stored when there is a
conference call.
1700 LWC msg - no No destination determined for Leave UID Call ID
destination Word Calling message store.
1701 Whisp pg not to Whisper page allowed only to UID Call ID
station simple station group type of user.
1702 Whisp pg query Invalid digit or number. UID Call ID
fail
1703 Whisp pg query Whisper paging. Query not UID Call ID
fail supported for access endpoints.
1704 Whisp pg usr not Whisper paging. User is not allowed UID Call ID
allowed to make whisper pages.
1705 Whisp pg query Whisper paging. No resource UID Call ID
fail available.
1706 Wake up typ/voice VIP and DAILY type wakeup cannot UID Call ID
actvat be modified or deleted via voice-
activated process.
1707 No attd to rcv Voice synthesizer is not available. UID Call ID
wakeup Routing automatic wakeup call
to attendant, but no attendant.
(TN725).
1708 No attd to rcv Voice synthesizer not available. UID Call ID
wakeup Routing automatic wakeup call
to attendant, but no attendant.
(TN725).
1709 Bsy vfy term is Busy verify is denied, the principal UID Call ID
PCOL terminator is Personal Central Office
Line (PCOL).
1710 Bsy vfy is term Busy verify is termination restricted. UID Call ID
rstrctd
1711 Bsy vfy dgt While collecting digits for busy UID Call ID
invalid/tmo verification, supervisor got an
indication of invalid digit or digit
timeout.
Table continues…
Denial Events

event log (keyword)
1712 Ofhk alrt tmo Standard action stimulus UID Call ID
intvl admin processing. Station, attendant, or
analog adjunct data extension
originated off-hook alert feature
activation, but no off-hook alert
timeout interval is administered.
1713 Bsy vfy dgt While collecting trunk member UID Call ID
invalid/tmo number digits for busy verification,
supervisor got an indication of
invalid digit or digit timeout.
1714 Whisp pg term is Whisper page feature activated, UID Call ID
PCOL principal terminator is Personal
Central Office Line (PCOL).
1715 Whisp pg is term Whisper page feature activated, UID Call ID
rstrctd whisper page is termination
restricted.
1716 Software invalid Whisper page feature activated, UID Call ID
stim whisper page supervisor saw
an invalid Call Processing (CP)
stimulus while collecting station
digits.
1717 Self Sta Display Self Station Display feature cannot UID Call ID
denial be activated from a bridged
appearance or station does not
have a display.
1718 Grp call pkup not Group Call pickup is not enabled. Return Call ID
enabled
code (0)
1719 Invalid dgts Invalid digits were collected. Digit Call ID
collected
1720 QSIG VM-no simple Cannot obtain simple user User ID UID Call ID
uid for an SS-B ISDN trunk.
1721 QSIG VM-no remote Received a Voice mail Number UID Call ID
user id MSI but did not receive an original
diverting number.
1722 QSIG VM-prin not The local principal User ID is not a UID Call ID
smpl uid simple user User ID.
1723 QSIG VM-no The number of the voice mail UID Call ID
voicemail nbr adjunct is not known, the call cannot
transfer to the adjunct.
Table continues…
Denial events

event log (keyword)
1724 Annc Record Announcement record session was UID board’s
Session Fail denied by the board. reason for
denial.
1725 QSIG VM-hunt not Principal does not have a QSIG UID Call ID
in cvg p MWI (Message Waiting Indicator)
hunt group in its coverage path.
1726 Cant get Smpl Cannot get simple attendant User UID Call ID
Attd-uid ID.
1727 cannot use PASTE Station restriction is total, cannot UID Call ID
use PC Application Software
Exchange (PASTE).
1728 Deny PE originated PE already active on call. UID Call ID
calls
1729 Direct Agent call Direct Agent Call failed. UID Call ID
failed
1730 Trk-grp uid Call failed to retrieve Release Link UID Call ID
retrieve fail Trunk (RLT) trunk group User ID
for Centralized Attendant Service
(CAS).
1731 I/C call on O/G Incoming call on outgoing trunk. UID Call ID
Trunk
1732 Caller COR Caller Class of Restriction (COR) UID UID or Call
Restricted restricted access. ID or
Station lock
COR/
Station
COR denial
reason or
Failure code
1733 Conference 2 Cannot conference 2 attendants. UID Call ID
Attendants
1734 Max Pub Net Trks Maximum number of Public Network UID Call ID
on conf Trunks on conference.
1735 Max conf parties Maximum number of conference UID Call ID
w/PNTrks parties with Public Network Trunks.
1736 Max conf parties Maximum number of conference UID Call ID
wo/PNTrk parties without Public Network
Trunks.
1737 Max conf/xfer Maximum number of conference or UID Call ID
parties transfer parties.
Table continues…
Denial Events

event log (keyword)
1738 Conf/xfer unstable Cannot conference or transfer UID Call ID
calls unstable calls.
1739 Div Reroute/Path Cannot transfer Diversion Rerouting UID Call ID
Replace or Path Replacement call.
1740 No Disconnect Cannot transfer, no disconnect UID Call ID
Supervision control party.
1741 Transfer trunk to Cannot transfer trunk to trunk. UID Call ID
trunk
1742 Conf/xfer Whisper Cannot conference or transfer UID Call ID
Page whisper page.
1743 cnf/xfr Emergency/ Cannot conference or transfer UID Call ID
Wakeup emergency or wakeup call.
1744 Conf/xfer a tone Cannot conference or transfer tone. UID Call ID
1745 Conf/xfer Cannot conference or transfer with UID Call ID
Announcements multiple announcements.
1746 Conf/xfer a Vector Cannot conference or transfer UID Failure
call vector call. reason
or Call ID
code|Call ID
or Call ID
1747 Cnf/xfr Service Cannot conference or transfer more UID Call ID
Observers than the maximum number of
service observers.
1748 Conf/xfer a Page Cannot conference or transfer group UID Call ID
call or loudspeaker page call.
1749 No Disconnect Cannot route call, no disconnect UID Call ID
Supervision control party.
1750 FRL too low to Cannot route the call, Facility UID UID
route call Restriction Level is too low.
1751 No AAR/ARS route No route pattern or preference UID Digits
pat/pref translated.
1752 Conf with no ISDN Conference when ISDN connect UID Call ID
connect message has not been sent due to
SA8434. The conference has been
denied.
Table continues…
Denial events

event log (keyword)
1753 Caller cvgpt COR Remote/caller cannot terminate to UID Failure
restrict coverage point due to Class of return code
Restriction (COR) setting. indicating
Dial Plan
Manager
COR
restriction
1754 Caller cvgpt COR Remote/caller cannot terminate to UID Failure
Dial Plan
Manager
COR
restriction
1755 Caller cvgpt COR Remote caller cannot terminate to UID Failure
Dial Plan
Manager
COR
restriction
1756 Caller fwdto COR Remote/caller cannot terminate UID Failure
restrict forwarded to party, Class of return code
Dial Plan
Manager
COR
restriction
1757 Attd release COR Attendant cannot release call, Class UID Failure
restrict of Restriction (COR) setting. return code
indicating
Dial Plan
Manager
COR
restriction
1758 Attd release link Attendant cannot release call, link UID Call ID
failure restriction.
1759 Attd hold COR Attendant cannot release call, Class UID Failure
indicating
Dial Plan
Manager
COR
restriction
Table continues…
Denial Events

event log (keyword)
1760 Conference COR Controller cannot conference call, UID Fail code
restrict Class of Restriction (COR) setting.
1761 Transfer COR Controller cannot transfer call, Class UID Failure
indicating
Dial Plan
Manager
COR
restriction
1762 Transfer no pooled Controller cannot transfer call, no UID Call ID
modem pooled modem.
1763 Cnf/xfr Intercept Attempt to transfer/conference an UID Call ID
Anncmt intercept announcement.
1764 Btn Ring Control Button ring control activated via UID Call ID
timeout Feature Access Code and time out
has occurred. SA8428.
1765 Invalid button Invalid button pushed in button ring UID Call ID
pushed control mode. SA8428.
1766 Remote Logout Indeterminate failure. The agent is UID Call ID
Agent fail busy/on hold on an ACD call, or not
logged in, or AAS, corruption, non-
ACD split/skill.
1767 Rmt Logout COR Invalid COR permissions UID Call ID
restricted
1768 Rmt Logout COS Invalid COS permissions UID Call ID
restricted
1769 Rmt Logout invalid Only allow logout for simple UID Call ID
input extensions, stations/attd. EAS agent
may not be logged on.
1770 Rmt Logout tenant Supervisor and agent are not in the UID Call ID
number same tenant partition.
1771 Rmt Logout cant do Attempting to perform a self-remote UID Call ID
self logout.
1772 PSA on Virt EXT Personal Station Access (PSA) UID Call ID
disallow associate/disassociate not allowed
for virtual extension.
1773 Cnf/xfr Atd Intcpt Attempt to transfer an intercept UID Call ID
Ann announcement at the attendant.
1774 Stn Lock act/deact Station lock activation or UID Call ID
failed deactivation failed.
Table continues…
Denial events

event log (keyword)
1775 No adm for SBS Separation of Bearer and Signaling UID Call ID
extensions (SBS) call tried to allocate an
SBS extension, but none was
administered.
1776 Can't send SBS # Separation of Bearer and Signaling UID UID of SBS
to orig (SBS) call tried to send back Extension
an INFO message with the SBS
complete public number, but the
INFO cannot be sent. Check proper
administration of isdn-pub-unk form.
1777 Calling Pty COR Error occurred when retrieving UID Call ID
chk fail Class of Restriction (COR) of calling
party.
1778 Orig COR/Auth COR Calling party Class of Restriction UID Call ID
dny (COR) not allowed to use mapped
COR from authorization code entry.
1779 FIPN RO when call SA8506: Fujitsu Intelligent Priva UID Call ID
on hold Network (FIPN -a Fujitsu ISDN
Protocol spec) route optimization
denial. There is call on hold.
1780 AAR/ARS fac not ARS/ARR Feature Access Code is UID Call ID
administered not administered.
Note:
Error codes 1781 through 1791 apply to Feature Access Code invocations that are designed to
operate on contact closure relays on a G350 Branch Gateway. These error codes apply only to
Linux-based servers.
1781 1 CC: Improper COS Contact closure related operation UID COS
on a G350 MG is denied because
user doesn’t have contact closure
COD and does not have console
permissions.
1782 1 CC: Invalid digits Invalid digits (* or a symbol for UID Digit
a digit, etc.) entered for contact-
closure related operation on a G350
Branch Gateway.
1783 1 CC: MG# out of Gateway number is out-of-range. UID Gateway
range Number
Table continues…
1 Error codes 1781 through 1791 apply to Feature Access Code invocations that are designed to operate on contact
closure relays on a G350 Branch Gateway. These error codes apply only to Linux-based servers.
Denial Events

event log (keyword)
1784 1 CC: software error Possible memory corruption, UID ID where
possible bad number, or message error
not sent. Internal software error. occurred
1785 1 CC: Invalid Contact closure related operation UID CC number
closure# had bad closure number entered by
user.
1786 1 CC: MG not Contact closure related operation UID Gateway
administered had unadministered gateway Number
number entered by user.
1787 1 CC: MG not An unregistered gateway was UID Gateway
registered selected for a contact relay related Number
operation on a G350 Branch
Gateway.
1788 1 CC: MG in link The G350 Branch Gateway selected UID Gateway
recovery for a contact relay related operation Number
was in link recovery mode.
1789 1 CC: MG not a G350 The gateway selected for a contact UID Gateway
gateway relay related operation is not a Number
Communica
G350.
tion
Manager
Release 2.2
and earlier
1789 1 CC: No CC on this The gateway selected for a contact UID Gateway
MG type relay- related operation does not Number
Communica
have a contact relay.
tion
Manager
Release 3.0
and later
1790 1 CC: Invalid button An invalid feature button was UID Message
push pushed after invoking contact Type
closure feature.
1791 1 CC: Trunk usr not Trunk access is not allowed for UID Call ID
allowed contact closure feature.
1792 MI Chg Fail: Agt Deny change to manual-in mode UID Call ID
Burnout because the agent is in burnout
state.
1793 AI Chg Fail: Agt Deny change to auto-in mode UID Call ID
Burnout because the agent is in burnout
state.
1794 No STNHNT for Deny station hunt after coverage if UID Call ID
Remote cvg the last coverage party is remote.
Table continues…
Denial events

event log (keyword)
1795 Caller FEAC Caller FEAC restricted access. UID UID or Call
restricted ID
1796 Caller TOLL Caller TOLL restricted access. UID Call ID or
restricted UID or
failure code
1797 TTI Outcall Needs Terminal Translation Initiation (TTI) UID Call ID or
PSA COR Caller has AAR/ARS network UID
restricted access.
1798 No TTI merge to No Terminal Translation Initiation UID Call ID
AAR/UDP (TTI) merge is allowed to an
AAR/UDP network.
1799 Annc in Audio Grp Deny recording or deleting the UID Call ID
announcement if it is part of an
audio group.
1800 Parties Tenant Tenant is restricted. UID UID
restrict
1801 Public Trunk Public trunk is restricted. UID UID
restrict
1802 Parties COR Parties’ COR is restricted. UID UID
restrict
1803 Origination Origination is restricted. UID UID
restrict
1804 Manual Line Manual line is restricted. UID UID
restrict
1805 Inward restrict Inward is restricted. UID UID
1806 Termination Termination is restricted. UID UID
restrict
1807 Outward restrict Outward is restricted. UID UID
1808 Conf Hold restrict Conference hold is not allowed UID Call ID
during digit collection.
1809 Rej CFU act ECF Reject the activation of CFU UID Call ID
active because ENHCF (unconditional) is
already activated.
1810 Rej CFBDA act ECF Reject the activation of CFBDA UID Call ID
active because ENHCF (busy or no reply)
is already activated.
1811 Whisp pg denied to Reject the whisper page because UID Call ID
AVC call the target call is bridge-removed on
an Adhoc Video Conference (AVC)
conference.
Table continues…
Denial Events

event log (keyword)
1812 SIP Sta cannot be SIP station not allowed to service UID Call ID
observerg observe.
1813 Attd pickup merge Merge Failed UID Failure
failed return code
1814 EMU:No rte pattern EMU no route pattern has UID Feature ID
assigned been assigned. See form “off-pbx or Message
enterprise”. Type
1815 EMU:dny EMU visitor cannot register to itself. UID UID
registration to
self
1816 Force ws chg COR allow forcing work state change. UID Call ID
restrict
1817 No rte for unauth No route for unauthorized domain. UID DPUNAUT
domain HDMN(20)|
Feature
activation
code
1818 Selected route pat SIP route pattern is empty. UID Route
empty pattern
index
User manager denial events

Denial events generated by the User Manager are listed in the following table.
Table 34: User Manager denial events (1900 - 1906)
EventTy Event Description, as Explanation Event Event

pe it is displayed on the Data Data
event log (keyword) 1 2
1900 Invalid CFWD Call forwarding digits do not map to station User ID. UID NA
destination
1901 Control Restrn Control Restriction. UID NA
Check fail
1902 Enhanced Abbr Enhanced Abbreviated Dialing entry length failed. UID NA
List Failur
1903 LWC Button xln Ignore Leave Word Calling button push due to bad UID NA
Error translation.
1904 Override for the User not allowed to activate override for this partition UID NA
PGN disa
1905 Auto selection of Automatic selection of Direct Inward Dialing numbers UID NA
DID dis is disabled.
Table continues…
Denial events
EventTy Event Description, as Explanation Event Event

pe it is displayed on the Data Data
event log (keyword) 1 2
1906 SA8428 Btn Ring SA8428 Station User Button Ring Control has been UID NA
Ctl disab disabled, ignore button-ring button push.
IP Denial Events
IP denial events are listed in the following table and in Call Processing Denial Events (2021 -
2299) on page 236.
Table 35: IP Denial Events (1907 - 2020)
EventT Event Description, as Explanation Event Data 1 Event Data 2

ype it is displayed on the
event log (keyword)
1907 IP RRJ-Invalid RAS IP Registration Rejected because 0 IP address of
addr the RAS address in the registration the endpoint
request (RRQ) is invalid.
1908 IP RRJ-Invld call IP Registration Rejection because 0 IP address of
SigAddr the call signaling address in the endpoint
the registration request (RRQ) is
invalid.
1909 IP RRJ-RemoteOfc Registration rejected because: 0 IP address of
misadmin the endpoint
• Remote Office is enabled on
the Signaling Group screen, but
the registration request (RRQ)
is not from a supported Remote
Office product (the Remote MAX
Product/Vendor ID is invalid).
• The RRQ is from a supported
Remote Office product, but
Remote Office is disabled on the
Signaling Group screen.
• Remote Office is enabled on the
Signaling Group screen, but the
Terminal Type in the RRQ is
invalid (the Terminal Type is not
a gateway).
1910 IP RRJ-H323 IP Registration rejected because 0 IP address of
UserObj undef there is no H.323 User Object. the endpoint
Internal software error.
Table continues…
Denial Events

event log (keyword)
1911 IP RRJ-Exceed max IP Registration rejected because 0 Upper part:
endpts the capacity administered on number of
page 1 of the system-parameters registered RO
customer-options screen for either endpoints.
registered endpoints, registered
Lower part:
Remote Office endpoints,
number of
or registered un-authenticating
registered IP
endpoints has been exceeded.
endpoints.
1912 IP RRJ-Exceed IP Registration rejected because Truncated Upper part:
ProdID/Ver the capacity administered on Product ID registered
the system-parameters customer- from the limit.
options screen of registered System-
Lower part:
endpoints of a specific product ID Parameters
actual count.
and version has been exceeded. Customer-
Options
screen
1913 IP RRJ-Invalid IP Registration rejected because Truncated Major version
ProdID/Ver of an invalid Product ID / Version. Product ID of number of the
Registering Application's product the registering endpoint sent
ID is not administered on application in the RRQ
the system-parameters customer-
options screen or no Product
ID in registration request (RRQ)
message.
1914 IP RRJ-ProdID IP Registration rejected because Truncated Major version
search fail the search for the Product ID of the Product ID of number of the
registering application failed. the registering endpoint sent
application in the RRQ
1915 IP RRJ-Invalid Registration rejected because the IP address of Endpoint’s
endpt/Ver endpoint version is incompatible endpoint major version
with the gatekeeper version. number in 2nd
byte, minor
version
number in low
byte
1916 IP RRJ-No H323 Registration rejected because 0 IP address of
NonStdData Non-standard Data (NSD) is the endpoint
missing in the registration request
(RRQ) from the endpoint.
1917 IP RRJ-Invld H323 Registration rejected because the Object ID in IP address of
ObjID H.323 Object ID in the registration RRQ the endpoint
request (RRQ) is invalid.
Table continues…
Denial events

event log (keyword)
1918 IP RRJ-Invld H225 Registration rejected because 0 IP address of
NSData cannot decode H225 Non-standard the endpoint
Data (NSD) message.
1919 IP RRJ-Bad H225 Registration rejected because an NSD choice in IP address of
NSDchoice unexpected Non-standard Data RRQ the endpoint
(NSD) message was received from
the registering application.
1920 IP GRJ-RRJ: new LM Registration rejected because of UID IP address of
fail failure in creating a new Login the endpoint
Manager. Possible causes are:
• No available heap memory to
create LoginMgr
• Cannot start LoginMgr timer
• Clock not set
1921 IP RRJ-IP-TTI port Registration rejected because of UID IP address of
fail failure when inserting the IP the endpoint
port. Internal software error.
1922 IP RRJ-TTI or RO Registration rejected for an IP set 0 IP address
inactive with Terminal Translation Initiation
Commu
(TTI) service. Possible causes:
ni-
cation • TTI is disabled on the system-
Manag parameters customer-options
er screen.
Releas
• Remote Office is disabled
e 2.2
on the system-parameters
and
customer-options screen.
earlier
1922 IP RRJ-TTI Registration rejected for an IP IP address of IP address
Commu inactive set with Terminal Translation the endpoint
ni- Initiation (TTI) service. Possible
cation cause is TTI is not enabled on
Manag the system-parameters customer-
er options screen.
Releas
e 3.0
and
later
1923 IP RRJ-No E164 Registration rejected because UID IP address of
number there is no valid E.164 telephone the endpoint
number in the RRQ or the
extension is not administered.
Table continues…
Denial Events

event log (keyword)
1924 IP RRJ-No GRQ msg Registration rejected because no UID IP address of
rcvd Gatekeeper Request message was the endpoint
received.
1925 IGAR trunk routing Denied while routing an outgoing Network Internal IGAR
failed Inter-Gateway Alternate Routing Region ID
(IGAR) trunk call. Check outgoing
ARS translation for the call to the
far-end IGAR LDN.
1926 IP RRJ- Registration rejected because UID IP address of
Authenticatn fail of password authentication/ the endpoint
encryption failure. The password
that the user entered and the
administered password on the
station screen do not match or no
cryptoToken or keys sent in RRQ.
1927 IP RRJ-Invld Registration rejected because of UID set type
station type invalid set type or no Remote
Office assignment on the station
form.
1928 IP RRJ-StnTyp/ Registration rejected because UID Endpoint type
Protocl err station type and call-signaling (3rd and 2nd
protocol are inconsistent. An IP nyble); call
Softphone should be assigned as signaling
one of the following: protocol (low
nyble)
• DCP extension, with call control
set to IP Softphone
• H.323 extension, with call control
set to none
1929 IP RRJ-No idx for Registration rejected because user UID IP address of
MMCmplx record for dual-connected DCP the endpoint
set is missing the index for
the multimedia complex. Internal
software error.
1930 IP RRJ-No voice Registration rejected because UID IP address of
path spec the virtual phone has neither the endpoint
a specified voice path nor an
associated multimedia extension,
so no audio path exists.
• Add an extension on the
softphone or extension on
multimedia complex.
Table continues…
Denial events

event log (keyword)
1931 IP RRJ-H323 ext is Registration rejected because this UID IP address of
MMCmpx H.323 extension is administered the endpoint
as a Media Complex extension on
a non-H.323 set (for example, a
DCP).
1932 IP RRJ-Ext has Registration rejected because the UID IP address of
data modl extension has a data module. the endpoint
1933 IP RRJ-IP addr Registration rejected because UID IP address of
mismatch the H.323 application is not at registering
the same IP address as the endpoint
authenticating application.
1934 IP RRJ-Ext already Registration rejected because the UID IP address of
reg extension is already registered. the endpoint
1935 IP RRJ-Not Remote Registration rejected because UID IP address of
Ofc ext Remote Office is not administered the endpoint
on the station screen for this
extension.
1936 IP RRJ-RO stn Registration rejected because of UID IP address of
mismatch invalid analog station type. the endpoint
1937 IP RRJ-RemOfc not Registration rejected because the UID IP address of
admin Remote Office endpoint is not the endpoint
administered or is of unknown
station type.
1938 IP RRJ-Immediate Immediate re-registration is UID IP address of
re-reg rejected when a registration or the endpoint
unregistration is in progress for the
extension.
1939 IP RRJ-Failure Registration rejected because of UID IP address of
moving ext failure while trying to force the the endpoint
unregistration of an extension in
the process of moving it to another
port. Internal software error.
1940 IP RRJ-Duplicate Registration rejected as a duplicate UID IP address of
ext extension. the endpoint
1941 IP KA-from invld Keep Alive registration request UID IP address of
endpt ID rejected because of invalid the endpoint
endpoint identifier in RRQ.
1942 IP KA-from unreg Keep Alive registration request UID IP address of
user rejected because it was received the endpoint
from an unregistered extension.
Table continues…
Denial Events

event log (keyword)
1943 IP-KA-from unreg Keep Alive registration request UID IP address of
SigGrp rejected because it was received the far-end
from an unregistered signaling
group.
1944 IP RRJ-PSA merge Registration rejected because the UID IP address of
failure Personal Station Access (PSA) the endpoint
merge failed (internal software
error). Check for corruption
1945 IP RRJ-New IP user Registration rejected because of 0 IP address of
fail failure to construct new H323 User the endpoint
object (internal software error).
1946 IP RRJ-PSA merge Registration rejected because the 0 IP address of
failure LoginManager Personal Station the endpoint
Access (PSA) merge operation
failed (internal software error).
Check for corruption.
1947 IP RRJ-PSA unmerge Registration rejected because the UID IP address of
fail LoginManager Personal Station the endpoint
Access (PSA) unmerge operation
1948 IP RRJ-Complete Registration rejected because of UID IP address of
pend reg failure to obtain a station user the endpoint
record (internal software error –
corrupt translation).
1949 IP RRJ-Build KARCF Registration rejected because of 0 IP address of
msg failure to build a KeepAlive the endpoint
Registration Confirm (KARCF)
message (internal software error).
1950 IP RRJ-Build RCF Registration rejected because of 0 or UID IP address of
msg failure to build a Registration the endpoint
Confirm (RCF) message (internal
software error).
1951 IP GRJ-Invld IP Gatekeeper request rejected (GRJ) 0 IP address
addr/port because of invalid destination IP
address and port in the request
(GRQ).
1952 IP GRJ-Invld Gatekeeper request (GRQ) Gatekeeper ID IP address
gatekeeperID rejected because the message is
not for this gatekeeper.
Table continues…
Denial events

event log (keyword)
1953 IP GRJ-Invld auth Gatekeeper request rejected 0 IP address of
capblty because registering endpoint the endpoint
has sent authentication capability
that is not supported by this
gatekeeper.
1954 IP GRJ-Invld auth Gatekeeper request rejected 0 IP address of
algrthm because no compatible the endpoint
authentication algorithm exists
between the endpoint and the
gatekeeper.
1955 IP GRJ-Bld Gatekeeper request rejected 0 IP address
GCF:Gatewy/MCU because of failure to build
a GateKeeper Confirm (GCF)
message for a GateWay/MCU
(internal software error).
1956 IP GRJ-Bld GCF:TTI Gatekeeper request rejected 0 IP address
because of failure to build
message for an un-named
endpoint registration (internal
software error).
1957 IP GRJ-GK will not Gatekeeper request rejected TTI state IP address of
host because the gatekeeper is unable the endpoint
to host endpoint because no
alias address has been provided
or Terminal Translation Initiation
(TTI) is in an incorrect state (for
example, TTI is not enabled for
voice).
1958 IP GRJ-Invalid Gatekeeper request rejected Either IP address of
extension because the extension is not extension the endpoint
administered. number or 0
1959 IP GRJ-No stn user Gatekeeper request rejected UID IP address of
record because no station user record the endpoint
exists for registering this user
1960 IP FURQ-Shared Forced Unregistration Request. UID IP address of
Ctrl Unreg The Gatekeeper is unregistering IP Softphone
the IP Softphone because it is in
shared control with IP Telephone,
and the Telephone is unregistering.
Table continues…
Denial Events

event log (keyword)
1961 IP GRJ-Build GCF Gatekeeper request rejected UID IP address of
msg because of failure to build the endpoint
1962 IP LRJ-No H323 sig Location Request rejected UID IP address of
group because no H.323 signaling group the far-end
is administered to handle the call.
1963 IP LRJ-Build LCF Location Request rejected UID IP address
msg because of failure to build a
Location Request Confirm (LCF)
1964 IP DRJ-Null UserID Disengage Request rejected UID IP address
because the endpoint ID cannot be
converted to a User ID (UID).
1965 IP DRJ-Bld Disengage Request rejected UID IP address
DCF:Gatewy/MCU because of failure to build
Disengage Request Confirm (DCF)
message for a gateway or MCU
1966 IP DRJ-Endpt not Disengage Request rejected UID IP address
reg because the endpoint is not
registered.
1967 IP DRJ-Build DCF Disengage Request rejected UID IP address
Disengage Request Confirm (DCF)
message for a non-gateway or
MCU user (internal software error).
1968 IP BRJ-Null UserID Bandwidth Request rejected 0 IP address
because an invalid endpoint ID
was received.
1969 IP BRJ-Bld Bandwidth Request rejected UID IP address
BCF:Gatewy/MCU because of failure to build a
Bandwidth Request Confirm (BCF)
message for a Gateway or MCU
1970 IP BRJ-Endpt not Bandwidth Request rejected UID IP address
registered.
Table continues…
Denial events

event log (keyword)
1971 IP BRJ-Build BCF Bandwidth Request rejected UID IP address
Bandwidth Request Confirm (BCF)
message for a non-Gateway or
MCU user (internal software error).
1972 IP BRJ-No H323 Bandwidth Request rejected UID IP address
user because the H.323 user object
does not exist (internal software
error).
1973 IP BRJ-Call non- Bandwidth Request rejected UID IP address
existent because the request is made for a
non-existing call.
1974 IP BRJ-Bandwdth Bandwidth Request rejected UID IP address
rqst fail because of unexpected return
code from bandwidth request.
1975 IP ARJ-Null UserID Admission Request rejected 0 IP address
because of an invalid endpoint ID.
1976 IP ARJ-Endpt not Admission Request rejected UID IP address
registered.
1977 IP ARJ-No avail B- Admission Request rejected UID IP address
channel because no B channel is available
for the call.
1978 IP ARJ-Bld Admission Request rejected UID IP address
ACF:Gatewy/MCU because of failure to build an
Admission Request Confirm (ACF)
message for a Gateway or MCU
1979 IP ARJ-Not an H323 Admission Request rejected UID IP address
user because request was received
from a non-H.323 user.
1980 IP ARJ-Stn not in Admission Request rejected UID IP address
service because the station is not in
service.
1981 IP ARJ-Build ACF Admission Request rejected UID IP address
msg because there was failure to build
an Admission Request Confirm
(ACF) message for a non-Gateway
or MCU user (internal software
error).
Table continues…
Denial Events

event log (keyword)
1982 IP ARJ-No H323 Admission Request rejected UID IP address
user because the H.323 user object
does not exist (internal software
error).
1983 IP ARJ-CRV already Admission Request rejected UID IP address
in use because Call Reference Value
(CRV) is already in use by another
call.
1984 IP ARJ-CRV does Admission Request rejected UID IP address
not exist because this Call Reference Value
(CRV) does not exist.
1985 IP ARJ-CRV already Admission Request rejected: Call UID IP address
in use Reference Value (CRV) is already
in use by another call. An ARQ has
been received while an earlier one
is still pending.
1986 IP ARJ-Insuff Admission Request rejected UID IP address
bandwidth because there is insufficient
bandwidth available to support this
call.
1987 IP ARJ-Admissn Admission Request rejected UID IP address
rqst fail because of an unexpected return
code from Admission Request
1988 IP URJ-Null UserID Unregistration Request rejected 0 IP address of
because of an invalid endpoint ID. the endpoint
1989 IP URJ-Endpt not Unregistration Request rejected UID IP address of
reg because the endpoint is not the endpoint
registered.
1990 IP URJ-No endpoint Unregistration Request rejected 0 IP address of
ID because no endpoint ID provided the endpoint
in URQ.
1991 IP URJ-GW/MCU is Unregistration Request rejected UID IP address of
not reg because URQ received from a the far-end
Gateway or MCU that is not
registered.
1992 IP URJ-No H323 sig Unregistration Request rejected UID IP address of
group because there is no H.323 user the far-end
for the signaling group (internal
software error).
Table continues…
Denial events

event log (keyword)
1993 IP URJ-No non-std Unregistration Request rejected UID IP address of
data because there is no non-standard the endpoint
data in the URQ.
1994 IP URJ-NSD has Unregistration Request rejected UID IP address of
invld OID because the Non-standard Data the endpoint
(NSD) from the registered
application has an invalid object ID
in the URQ.
1995 IP URJ-Can’t Unregistration Request rejected UID IP address of
decode NSD because of failure to decode Non- the endpoint
standard Data (NSD) in the URQ.
1996 IP URJ-Unexpected Unregistration Request rejected UID IP address of
NSD msg because of unexpected Non- the endpoint
standard Data (NSD) in the URQ
from the registered endpoint.
1997 IP URJ-User is on Unregistration Request rejected UID IP address of
a call because the user is on a call. the endpoint
1998 IP URJ-PSA unmerge Unregistration Request rejected UID IP address of
failed because the Personal Station the endpoint
failed due to an internal software
error or memory corruption.
1999 IP URJ-PSA merge Unregistration Request rejected UID IP address of
Access (PSA) merge operation
Check for corruption
2000 IP URJ-No stn user Unregistration Request rejected UID IP address of
record because no station user record the endpoint
exists for the unregistering user
2001 IP URJ-TTI op Unregistration Request rejected UID IP address of
failed because of an unexpected the endpoint
return code.
2002 IP URJ-Build UCF Unregistration Request rejected 0 IP address of
msg because of failure to build an the endpoint
unregistration request confirm
(UCF) message (internal software
error).
Table continues…
Denial Events

event log (keyword)
2004 IP URJ-No stn user Unregistration Request rejected UID IP address of
record because the no station user record the endpoint
exists for the unregistering user
2006 IP FURQ-no H.323 Force Unregistration Request. UID IP address
ext reg Received a KeepAlive request
(RRQ) from a dual-connect
endpoint without a registered
H.323 extension (cannot make
calls).
2007 IP FURQ-User, no Force Unregistration Request. UID IP address of
sig conn Unregister user because there is the endpoint
no signaling connection. RAS is
alive, but there is no signaling
connection (user cannot make
calls).
2008 IP FURQ-H323, no Force Unregistration Request. UID IP address of
sig conn Unregister associated H.323 user the endpoint
because there is no signaling
connection.
2009 IP FURQ-Move user Force Unregistration Request. UID IP address of
Extension is already registered, the endpoint
but received a forced login
registration request (RRQ). The
existing extension must receive a
URQ.
2010 IP FURQ-Sig Conn Forced Unregistration Request. UID 0
closed The Gatekeeper is unregistering
the endpoint because its call
signaling connection has closed.
Table continues…
Denial events

event log (keyword)
2011 IP FURQ-NoQ931 msg Force Unregistration Request. H.323 UID IP address of
rcvd After an endpoint registers, it the endpoint
should initiate the TCP connection
and send a SETUP message. The
SETUP message has not been
received from the endpoint, and
no Q931 Call object exists. The
endpoint cannot make calls.
2012 IP FURQ-Aged Force Unregistration Request. UID IP address of
Endpt-no KA Unregister endpoint that has aged the endpoint
out. Endpoint's time to live (TTL)
expired without receiving a keep-
alive request (RRQ).
2013 IP FURQ-SigGrp Force Unregistration Request. An Gateway UID IP address of
removed H.323 Gateway (administered as the signaling
a signaling group) is registered. group
The gateway must be unregistered
before removing the administered
signaling group.
2014 IP FURQ-Siggrp Force Unregistration Request. Signaling IP address of
changed Changes have been made to group UID the near-end
a registered H.323 Gateway
(administered as a signaling
group). The gateway must be
unregistered.
2015 IP FURQ-Ext Forced Unregistration Request. UID 0
removed Unregister user because the
extension has been removed.
2016 IP FURQ-IPusr is Forced Unregistration Request. IP User-UID 0
sftphone
• A user has Personal Station
Accessed (PSA) as an extension
that was registered as an IP
endpoint.
• An IP telephone extension in
shared control was moved to
another IP port via registration.
Both shared control IP Telephone
and IP softphone unregisters if
the rejected registration attempt
is forced.
2017 IP FURQ-Records Forced Unregistration Request. IP User ID 0
exhausted Unregister the LAN port if there are
no records remaining.
Table continues…
Denial Events

event log (keyword)
2018 IP FURQ-Mtc: H323/ Forced Unregistration Request. UID 0
Vphone Maintenance has unregistered an
H.323 or Vphone station.
2019 IP FURQ-Mtc: Forced Unregistration Request. UID 0
Remote Max Maintenance has unregistered a
Remote Max station.
2020 IP FURQ-Mtc:RemOfc Forced Unregistration Request. UID 0
TTI Terminal Translation Initiation (TTI)
background maintenance task has
requested the removal of Remote
Office LAN TTI ports.
Call Processing Denial Events (2021 - 2299)

Call Process denial events 2021 - 2299 are explained in the following table.
EventT Event Description, as Explanation Event Event Data 2

ype it is displayed on the Data 1
event log (keyword)
2021 Cust Sel of DIDs Custom Selection of VIP UID 0
inactive Direct Inward Dialing numbers
feature is not active.
2022 Annc pres but not Announcement present but UID 0
admin not administered.
2023 Annc pres none on Announcement present but no UID 0
board announcements administered
for the board.
2024 Cannot create Registration rejected because UID IP address of the
entry unable to create an entry in endpoint
the MTM complex table.
2025 Unadministered Registration rejected because UID IP address of the
option the option chosen by the endpoint
endpoint in the RRQ for
the emergency call does not
match the option administered
on the station form.
2026 Xmobile OOS: Xmobile offhook request 0 CID
block orig rejected because Xmobile
station is taken out of service.
Table continues…
Denial events

event log (keyword)
2027 Annc not found on User attempted to play VAL UID 0
board Board announcement and the
file was missing.
2028 Annc file has bad User attempted to play VAL UID 0
format Board announcement and file
had incorrect format.
2029 IP GRJ-NSD has Gatekeeper Request rejected UID IP address of the
invld OID because the Non Standard endpoint
Data (NSD) from the
registered application has an
invalid object ID.
2030 IP GRJ-Can't Gatekeeper Request rejected UID IP address of the
decode NSD because of failure to decode endpoint
Non Standard Data (NSD)
element.
2031 IP GRJ-Unexpected Gatekeeper Request rejected UID IP address of the
NSD msg because of unexpected endpoint
Non Standard Data (NSD)
message from the registered
application endpoint.
2032 Force Force Unregistration Request. UID 0
Unregistration Instruct the RAS manager to
Req cleanup a User ID which had
just been registered prior to a
system restart. This event is
not logged, but only passed in
the URQ.
2033 IP FURQ-Demand Force Unregistration Request. UID IP address
Unregister The command to force
unregister endpoints is
executed from the SAT.
2034 Illegal TSC A QSIG Non Call Associated- UID 0
interaction Temporary Signaling
or
Connection (NCA-TSC) tried
to route out an AT&T TSC, or CID
vice versa, and this interaction
is not supported. This occurs
when a bsr_poll call over an
IP trunk tries to use a QSIG
TSC but is sequenced out an
AT&T TSC.
Table continues…
Denial Events

event log (keyword)
2035 NCA-TSC not Possible causes: UID CID
available
• The terminated
administered Temporary
Signaling Connection (TSC)
endpoint is disabled
• The incoming Non
Call Associated-Temporary
Signaling Connection (NCA-
TSC) call arrived at the
wrong signaling group
• The Maximum number of
NCA-TSC is set to 0
2036 Incoming QSIG LWC Failed doing a LWC on the Number of UID
Comm failed incoming side of QSIG LWC digits
unicati MSI CS0FAC message.
on
Manag
er
Releas
e 3.1
and
earlier
2036 Ext too long for Failed sending QSIG LWC UID UID
Comm QSIG LWC TSC SETUP message
unicati because the calling extension
on was too long.
Manag
er
Releas
e 4.0
and
later
2037 QSIG LWC fail Getting the voice call record UID CID
find voice on the outgoing side of
a QSIG LWC MSI SETUP
message failed.
2038 QSIG LWC fail get Getting the calling party UID CID
cling number from the receiving end
of the call failed.
2039 IP KA-No endpoint Keep Alive Registration 0 IP address
ID Request. Registration rejected
because no endpoint identifier
was provided.
Table continues…
Denial events

event log (keyword)
2040 IP GRJ-No CLAN Gatekeeper Request UID IP address
available rejected because resources
unavailable for signaling
connection.
2041 IP RRJ-No DSP Registration Request rejected UID IP address
Resource because no Digital Signal
Processor (DSP) resources
are available.
2042 460.1 Neg failed Registration Request rejected UID IP address
in ARQ because no Digital Signal
Processor (DSP) resources
are available.
2043 Multipoint call ARQ rejected because srcInfo UID IP address
to self and destinationInfo contents
indicate the multipoint
endpoint (VSX) is calling itself.
2044- not assigned
2046
2047 Reject- Registration rejected because 0 MG table index
Unauthorized MG it was received from
or
unauthorized gateway.
IP address
2048 Reject-MGC not Registration rejected because 0 MG table index
ready it is not ready for a gateway
or
re-registration.
IP address
2049 One-X Server One-X server did not respond CID UID
Timeout in timely manner.
2050 Path replacement Path replacement operation UID CID
operation denied denied because Pr_callid[]
table/array is full.
2051 IP GRJ-RemOfc No Remote Office invalid request Near IP Far IP address
Sig Grp (GRQ) No Sig Group address
available.
2052 IP RRJ-RemOfc No Remote Office invalid Near IP Far IP address
Sig Grp registration request (RRQ) No address
Sig group available.
2054 Signaling CONN UMSocket: SockWrite() Port Far-end IP address
Congestion Congestion on the Signaling number of
Link due to PCD buffer the near-
exhaustion. end
Table continues…
Denial Events

event log (keyword)
2055 Reset MG - Pkt Reset the gateway Signaling Gateway
Send Err Link due to error in Sending ID
packets.
2056 No null caps SBS IncomingMsg. Null caps not Trunk 0
orig end received on originating end Group
of Separation of Bearer and
UID
Signaling (SBS) trunk.
2057 No null caps SBS IncomingMsg. Null caps not Trunk 0
term end received on terminating end Group
of Separation of Bearer and
UID
Signaling (SBS) trunk.
2058 Null caps on H323 IncomingMsg. Null caps Trunk 0
trunk received on terminating end of Group
H.323 trunk.
UID
2059 SecCode change Change of security code UID CID
disallowed through Feature Access Code
not supported for IP.
2060 SA8508:Off Emergency access call to UID CID
the attendant using the 2nd
access code is not permitted
because the SA8508 green bit
is off.
2061 Invalid Post msg Post message digit timeout. UID CID
dgt/tmo
2062 Post msg too many Post message too many UID Ext digit count or
msg dgt digits.
CID
2063 Post msg not stn Post message not station UID UID
user user.
or
CID
2064 IP RRJ-NSD encode Registration rejected because UID IP address
failed of failure to encode
Non-standard Data (NSD)
message.
2065 IP RRJ-Invalid Registration rejected because 0 IP address
vendor id Survivable Remote Server
requesting registration has not
sent a valid vendor ID.
2066 IP RRJ-LSP obj Registration rejected because 0 IP address
not init the Survivable Remote Server
object has not been initialized.
Table continues…
Denial events

event log (keyword)
2067 IP RRJ-NSD Registration rejected because 0 IP address
improper OID the Non-standard Data (NSD)
sent by the Survivable
Remote Server contains an
invalid OID.
2068 IP RRJ-Cannot Registration rejected because 0 IP address
decode NSD of failure to decode
message sent by the
Survivable Remote Server.
2069 IP RRJ-Unxpctd Registration rejected because 0 IP address
NSD of receipt of an unexpected
message from Survivable
Remote Server.
2070 MG must send full Gateway attempted Far IP MG table index
reg msg registration with “warm start” Address of
condition, but the controller Gateway
needs “cold start” data.
2071 Serial Number Gateway attempted to register MG table Pointer offset
incorrect with a different serial number. index
2072 Conf/Transfer 2 Conference or transfer to CID CID
Meet-me Meet-me conference call.
2073 Permission denied User attempted to download UID CID
(or) firmware to a station. User
does not have console
Download
permission.
permission deny
2074 Rec fail: annc is Attempt to record a VAL GID 0
playing announcement while that
announcement is playing on a
VAL board.
2075 Var-in-Vec COS User does not have console UID CID
restricted permissions
2076 IP RRJ-Call IP Registration Rejection UID IP address
Mismatch (RRJ) because of no call
present on the switch side, but
there is a call present on the
endpoint.
2077 IP FURQ-CallTimer Force Unregistration Request. UID IP address
Expired Unregister endpoint whose
call preservation timer (H323
link loss delay timer) expires.
Table continues…
Denial Events

event log (keyword)
2078 Extend Call OPTIM Extend Call via extend Station Reason the call was
Button Denial call button press was denied. where the denied:
button was
0 - denied because the
pushed
call already has 6 ports
on it
1 - denied because the
station is at the OPTIM
call limit
2 - denied because
the application has no
termination mapping
3 - denied because call
failed to extend (check
application RTU)
2079 IP RRJ-Invld sta Registration rejected because UID IP address
state set in wrong state
(for example on call,
Out of Service (OOS),
Administered Without
Hardware (AWOH), Terminal
Translation Initiation (TTI),
shared-control endpoints
attempt to register to different
LSPs).
2080 IP FURQ-User IP Softphone in shared control UID 0
dialed TSA configuration with DCP is
forced unregistered because
user dialed TSA.
2081 IP FURQ-Invld sta IP Softphone in shared control UID Far-end IP address
state configuration with DCP is
forced unregistered because
softphone switched to invalid
state.
2082 Exceeded TLS conn A TLS socket was rejected Near-end Far-end IP address
limit because of the constraint on IP address
the maximum number of TLS
peers.
2083 TLS: No cert A peer certificate was rejected Far-end IP Near-end IP address
returned by common name checking. address
2084 TLS: Handshake Handshake failed, for Far-end IP Near-end IP address
Failure example, due to no common address
cipher suite.
Table continues…
Denial events

event log (keyword)
2085 TLS: Certificate An expired certificate was Far-end IP Near-end IP address
expired returned and rejected. address
2086 SBS bearer Auth If authorization code is UID CID
not supp required on outgoing
Separation of Bearer and
Signaling (SBS) bearer call,
this is not supported. The
call is dropped with intercept
treatment to the originator.
2087 IP RRJ-Shrd Ctrl Used to inform softphone UID IP address
OutofSrv trying to register in shared
control with an out-of-service
DCP endpoint to try
registration with Survivable
Remote Server.
2088 TLS: No CMD_ACCEPT: SSL/TLS Far-end IP Near-end IP address
Authorization verify failure. address
2089 TLS: Bad Record Bad Record Max. For Far-end IP Near-end IP address
MAC example, an attacker does not address
have the correct private key,
which can go undetected until
the MAC of the exchange is
checked.
2091 Conf/xfer Audix AUDIX one-step recording UID CID
rec while conf.
2092 Post msg invalid Post message invalid Station UID CID
SSC Security Code (SSC).
2093 Can't start Cannot start announcement. Media Context ID
announcement Gateway
Number
2094 TCP/IP sig socket Unable to establish a socket IP address Port number of the far
failure on an IP trunk. The of the far end
remote end is administered end to
incorrectly. which the
call failed
2095 Rmt Div-fwding QSIG Remote Diversion UID CID
ext local activation for local extension
not allowed.
2096 Rmt Div/EMU-SSC QSIG Remote Diversion UID CID
too long Station Security Code (SSC)
contains too many digits.
Table continues…
Denial Events

event log (keyword)
2097 Rmt Div-non QSIG QSIG Remote Diversion is UID CID
trunk not allowed over a non-QSIG
trunk.
2098 Rmt Div-act ext QSIG Remote Diversion UID CID
not stn activation only allowed from
station user.
2099 Rmt Div-act/deact QSIG Remote Diversion UID CID
failed activation/deactivation failed.
2100 Rmt Div-QSIG VALU QSIG Remote Diversion is not UID CID
disable allowed over a QSIG trunk
with QSIG VALU disabled.
2101 Feat. requires A feature was activated via a Extra Extra characters in
only dgts request URI. The part of the characters Request-URI, which are
request URI string that should in Request- not digits.
contain all digits contained URI, which
characters other than digits. are not
digits.
2102 SIP Estab Timer SIP call establishment timer Current Current B-Channel UID
expiry expired prior to 200 OK signaling (UID Cur_buid)
(incoming or outgoing call). signaling
Timer length is administered
on SIP sig-group forms.
2103 Cannot ring add- Attempt to add a party to a call UID of the Cause value/feedback
in party failed at the termination stage. party that indicating the reason.
was
attempting
to
terminate
Table continues…
Denial events

event log (keyword)
2104 Cannot add party Attempt to add a party to a call UID of the Reason code:
to call failed at or after answer. party that
1. Internal failure (look
was added
for proc_err around
in
same time)
for proc_err around
same time)
3. Conflict (ie adding
announcement to
call with tone or
announcement)
4. Already have
six connected/held
parties on the call
5. Unable to combine
voice streams
for proc_err around
same time)
for proc_err around
same time)
2105 SCCAN handover Seamless Converged UID of the reason for failure:
denied Communications Across station
0: No call found to
Networks (SCCAN) attempt to involved in
handover to
handover failed. handover
1: There is already a call
in the wireless domain
2: There are multiple
candidate calls to
handover to
3: Handover from call
not found
4: Handover to call not
found
5: Handover aborted
6: Call is at conference
limit
Table continues…
Denial Events

event log (keyword)
2106 SCCAN Seamless Converged UID of the Reason for failure:
announcement Communications Across station
0: Announcement not
denied Networks (SCCAN) attempt to involved in
administered on system-
handover failed. handover
parameters sccan form
1+ - Feedback type
2107 SCCAN call out OPTIM Seamless Converged UID of the reason for denial:
blocked Communications Across station
1: WLAN call limit
Networks (SCCAN) involved
exceeded
termination was denied
2: No termination
mapping
3: Cellular call limit
exceeded
4: No termination
mapping or call NOT
allowed or disabled.
Disabled is the most
likely cause (user
controlled)
5: Call on bridged
appearance and
termination disallowed.
2108 SCCAN retransmit There are problems UID of the reason for denial:
denied with Seamless Converged station
1:Cannot get Event
Communications Across involved
header from request
Networks (SCCAN) notify
retransmission response. 2: Cannot get time to
wait for retransmission
3: Unknown event type
4: Internal failure (look
for proc_err around
same time)
5: OPTIM application not
SCCAN
6: Station not
administered with
OPTIM
Table continues…
Denial events

event log (keyword)
2109 IP RRJ-Unknown Registration rejected because 0 IP address
unnamed an unnamed endpoint did
of the endpoint.
not have the terminal present
bit set, or because it did
not supply Lucent vendor
information.
2110 Release btn push Agent pushed IM_ACD_REL UID of 0
ignored button simultaneously with call agent
termination. pushing
IM_ACD_R
EL button
2111 MAX VuStats Max number of simultaneous UID of VuStats display format
displays actv VuStats displays permitted are agent number
in use. pushing
VuStats
button
2112 IP LRJ-No Route Send Location Request reject UID Far-end IP address
to dest message because we cannot
route to the destination.
2113 Invalid NSF for Invalid NSF for CA-Temporary NSF UID
CA-TSC Rq Signaling Connection (TSC) Information
request.
2114 No AAR/ARS acc AAR/ARS not accessible Originating Transfer operation value
from DID from Direct Inward Dial/Direct or
UID
Inward-Outward Dial (DID/
UID
DIOD) trunk.
UID
2115 Transfer denied - Special Application block of Originating Transfer operation value
SA8759 call-transfer. Drop if second or
UID
call-leg is not answered.
UID
2116 460.1 Neg failed 460.1 feature not supported. UID Network Call Redirection
in GRQ operation value
2116 Conf/drop denied - SA8759 block of call- UID Network Call Redirection
SA8759 conference/drop if second call operation value
leg is not answered.
2117 TSC attempt TSC administration is TSC Cause value
denied incorrect on the system- Úpplication
parameters customer-options
screen and the Route Pattern
screen.
2118 ACD agent tot Max number of ACD agents UID Logged-in ACD agent
exceeds max already logged-in. count
Table continues…
Denial Events

event log (keyword)
2119 Memb per skill Max number of agents already Agent UID Skill number
exceeds mx logged-in to skill.
2120 Advocate agents Max number of Business Agent UID Logged-in Business
exceed mx Advocate agents already Advocate Agent count
logged-in.
2121 Oth agt using Some other agent already Agent UID Split number
this logid using this loginID.
2122 This agt using This agent already using Agent UID Split number
oth logid some other loginID.
2123 BCMS logid val BCMS (Basic Call Agent UID Split number
failed Management System) Login
ID validation failed.
2124 Agent tot exceeds Agent total exceeds system Agent UID Agent total
sys max limit.
2125 Over CMS agent Maxed-out CMS capacity. Agent UID Skill number
login cap
2126 Over CMS agent Maxed out CMS capacity. Agent UID Skill number
login cap
2127 Over BCMS agent Maxed out BCMS (Basic Agent UID BCMS agent total
login cap Call Management System)
capacity.
2128 No far-end IGAR/DPT Missing far-end IGAR Network Internal Dial Plan
ext LDN (Inter-Gateway Alternate region Manager
Routing).
return code or call-id
2129 No near-end IGAR No idle trunks in either Max trunk Call ID
trunks network region (IGAR
request).
2130 IP RRJ-TTI reg Deny TTI registration - IP IP address TTI state
not in map endpoint not in ip-network-
map.
2131 IP RRJ-TTI reg Deny TTI registration - IP IP address TTI state
shared ctl endpoint requesting shared
control.
2132 IP RRJ-TTI Deny TTI registration - IP IP address TTI state
incapable endpoint not TTI capable.
2133 IP RRJ-Unnamed Deny TTI registration - IP address TTI state
disabled Unnamed registration feature
is disabled.
Table continues…
Denial events

event log (keyword)
2134 RAS message Incoming RAS message failed UID IP address
failed Annex H Annex H authentication and
was ignored.
2135 Q931 message Incoming Q931 message UID Auth Token
failed Annex H failed Annex H authentication
and Auth
and was ignored
Location
2136 H.245 Port alloc Unable to allocate H.245 Port 0
failure pooled port. A dynamic number
port can be tried, but the
connection attempt will likely
be blocked by firewall.
2137 H.245 Throttled excessive H245 Call ID Throttle count
VideoFastUpd VideoFastUpdate message.
throt
2138 H.245 ConfInd Throttled excessive Call ID Throttle count
Join throt H245 ConferenceIndication
EmterminalJoinedConference
message.
2139 H245 Timeout Call H245 connection timed out Signaling Current State and
Dropped and call was dropped. Entity Time Previous State
and
Timeout
Message
Type
2140 IP RRJ-TTI reg Deny TTI registration - request 0 IP address
eConsole from IP eConsole.
2141 IP RRJ-RO addr no Deny Terminal Translation IP address TTI state
admin Initiation (TTI) registration -
Remote Office address is not
administered.
2142 460.1 Neg failed 460.1 feature is not supported. UID IP address
in GRQ
2143 BRJ Rcvd-Not Received a BRJ message, UID Rejection reason choice
Bound EmBRJ_notBound_chosen.
2144 BRJ Rcvd-Inv Conf Received a BRJ message, UID Rejection reason choice
Id EmBRJ_invalidConferenceID_
chosen.
2145 BRJ Rcvd-Inv Received a BRJ message, UID Rejection reason choice
Permission EmBRJ_invalidPermission_ch
osen.
Table continues…
Denial Events

event log (keyword)
2146 BRJ Rcvd-Insuff Received a BRJ message, UID Rejection reason choice
Rsrc EmBRJ_insufficientResources
_chosen.
2147 BRJ Rcvd-Inv Received a BRJ message, UID Rejection reason choice
Revision EmBRJ_invalidRevision_chos
en.
2148 BRJ Rcvd-Security Received a BRJ message, UID Rejection reason choice
Denial EmBRJ_securityDenial_chose
n.
2149 BRJ Rcvd-Security Received a BRJ message, UID Rejection reason choice
Error EmBRJ_securityError_chosen
.
2150 BRJ Rcvd-Unknown Received a BRJ message, UID Rejection reason choice
Reason EmBRJ_undefinedReason_ch
osen.
2151 IP FURQ shrd ctrl Busyout of a shared UID Null
sftphn control softphone forces
unregistration of the
softphone, leaves base phone
in service.
2152 Conf/xfer denied- SA8652: Denial for NH Originating Call ID
SA8652 Consult call conference/ UID
transfer.
2153 Call merge SA8652: Denial for NH Controller Call ID
denied-SA8652 Consult call merge. UID
2154 NHCnsl Orig DS8652: Denial for NH Originating Call ID
denied-SA8652 Consult origination. UID
2155 Call hold denied- SA8652: Denial for NH UID : Call ID
SA8652 Consult call hold. holding
station
2156 Call Pickup SA8652: Denial for NH Originating Call ID
denied-SA8652 Consult call pickup. UID
2157 NHCnsl Brdg SA8652: Denial for bridging UID Call ID
denied-SA8652 on NH Consult call.
2158 Call Park denied- SA8652: Denial for parking a UID Call ID
SA8652 NH Consult call.
2159 NHConf orig SA8652: Denial for originating UID Call ID
denied-SA8652 NH conference call when a
consult call is active.
2160 Agent accept Non-EAS ACD split agent Agent UID CID
login error accept login failed.
Table continues…
Denial events

event log (keyword)
2161 EMU:dny act for Enterprise Mobility User UID Call ID
local ext (EMU) activation not allowed
for local extension.
2162 EMU:non-QSIG Enterprise Mobility User UID Call ID
trunk (EMU) over non-QSIG trunk
not allowed.
2163 EMU:vst login not Enterprise Mobility User Originating Call ID
allowed (EMU) login not allowed UID
based on station
administration.
2164 CC:Ringout Call QSIG-CC: Ringout call failure. CID or UID • Failure cause value -
Failure of QSIG 1013 (failureToMatch)
TSC call
• 1008 (unspecified)
• 0
• 1012
(remoteUserBusyAgai
n)
2165 CC:Comparison QSIG-CC Orig cancel: Originating Terminating UID
Failed Components did not match. UID
2166 Button lbl mem There is no more customized UID Call ID
exhausted label space.
2167 EMU:CTMI term to CtmiInform SETUP is UID Call ID
non-SSB terminating to a non-SSB
trunk (Enterprise Mobility User
(EMU)).
2168 EMU:Map/vst uid Mapped User ID does not UID UID
mismatch match the visitor User ID,
the Enterprise Mobility User
(EMU).
2169 IP GRJ-No PE in Gatekeeper Request is UID IP address
region rejected because no
resources are available on this
telephone’s region.
2170 CC:Ringout not QSIG CC: Ringout cannot Originating Cause value
Routed route. UID
2171 CC:Queueing QSIG-CC: Queueing failed. Originating Internal return code
Failed UID
2172 CC:Orig comp ck QSIG-CC Exec Possible: Originating Terminating UID
failed Components did not match. UID
Table continues…
Denial Events

event log (keyword)
2173 CC:Term comp ck QSIG-CC Term Cancel: Originating Terminating UID
failed Components did not match. UID
2174 EMU:Unsup clg pty Unsupported calling party Numbering Trunk group UID
nbr fmt numbering format for format
Enterprise Mobility User information
(EMU).
2175 reregister Module ID mismatch, re- Endpoint IP address
Servermismatch registration required. UID
2176 SigConn fail to Tried three times to bring up UID IP address
establish TCP socket and failed each
time. Do not try again.
2177 Invalid XFR to VM Deny transfer into voice mail Originating Call ID
attempt because either: UID
• QSIG transfer to QSIG voice
mail is not allowed
• an attempt was made to
interwork QSIG and SIP for
transferring into voice mail
2178 EMU:User dialed Enterprise Mobility User Originating Call ID
unsup FAC (EMU) user dialed an UID
unsupported Feature Access
Code (FAC).
2179 EMU:Non-emrg call HEMU user placed non- Originating Call ID
denial emergency call (Enterprise UID
Mobility User (EMU)).
2180 EMU:Reg-invld SSC Invalid security coded was UID 0
dialed dialed during registration
(Enterprise Mobility User
(EMU)).
2181 EMU:PSA not PSA not allowed on home UID 0
allowed station (Enterprise Mobility
User (EMU)).
2182 EMU:DeReg-inv SSC Invalid security code UID 0
dialed dialed during deregistration
(EMU)).
2183 EMU:Del-invld SSC Invalid security code UID 0
dialed dialed during deregistration
(EMU)).
Table continues…
Denial events

event log (keyword)
2184 EMU:Usr not fnd User not found in database UID • Error number 20 -
far end on far end (Enterprise Mobility indicate user not
User (EMU)). available
• Error number 24 -
User not subscribed
2185 EMU:Delete failed The delete operation failed UID Error number 30 -
far end (Enterprise Mobility User indicating timeout has
(EMU)). occurred while waiting
for response.
2186 EMU:Reg failed The registration operation UID Error number
far end failed (Enterprise Mobility
User (EMU)).
2187 EMU:DeReg failed The Deregistration operation UID Error number
far end failed (Enterprise Mobility
User (EMU)).
2188 EMU:IPReg block IP Registration is not allowed UID IP address
for VEMU when there is an active
Enterprise Mobility User
(EMU).
2191 EMU:Forced Forced deregistration of UID 0
deregistration Enterprise Mobility User
(EMU).
2192 EMU:Btn mismatch Button Mismatch (Enterprise UID Error number 9 -
far end Mobility User (EMU)). indicating unspecified
error.
2193 EMU:PSig oper Partner Signaling operation UID Error number
timeout timed out (Enterprise Mobility
User (EMU)).
2194 EMU:Reg oper Registration operation timed UID Error number 30 -
timeout out (Enterprise Mobility User indicating time-out has
for response.
2195 EMU:DeReg oper Deregistration operation timed UID Error number 30 -
timeout out (Enterprise Mobility User indicating time-out has
for response.
2196 EMU:Delete oper Delete operation timed out UID Error number 30 -
timeout (Enterprise Mobility User indicating time-out has
for response.
Table continues…
Denial Events

event log (keyword)
2197 Unsupported Deny transfer into voice mail UID Hunt group type
Remove VM typ because the voice mail hunt
group is not a supported
type (must be SIP, QSIG, or
AUDIX).
2198 Mod_ID mismatch There is a mismatch in Module Id IP address
in setup Module ID setup.
2199 call mismatch in Call mismatch in setup. Call status IP address
setup
2200 No TSC’s left in No free Temporary Signaling BRI UID
system Connection (TSC) user record signaling
available. grp index
2201 No TSC’s for this No free Temporary Signaling BRI UID
D-chan Connection (TSC) is available signaling
group
index
2202 EMU:invalid act/ EMU activation/deactivation is Originating Call ID
deact ext allowed only from the station UID
user
2203 Deny DND: E911CF Deny DND if E911 call forward Originating Call ID
is active is active UID
2204 IPFURQ-reg Force unregister the link UID Call ID
expired-nosock bounce telephone if its link
loss delay timer expired and it
is not on the call
2205 Forced Disconnect SA8847 - forced disconnect of Originating Call ID
SA8847 diverted predictive calls UID
2206 Wrong Group Page Wrong set type for group UID 0
set type page.
2207 Invalid digits are collected. Digit Call ID
2208 Extension not part of any
pickup group.
2209 Msg’ing Hunt Grp An fp-mwi, qsig-mwi, or sip- Originating Hunt group UID
Xln Bad adjunct messaging hunt group UID
does not route over the
correct trunking facility.
2210 QSIG PR:No simple Path replacement error 1005. UID UID
UID No simple UID.
2211 QSIG PR:Unrecog Denial for path replacement. CID UID
Call ID Unrecognized call identity.
Table continues…
Denial events

event log (keyword)
2212 QSIG PR:Busy Denial for path replacement Endpoint Trunk group UID
Verify Call on busy verify calls. UID
2213 QSIG PR:Malicious Denial for path replacement if Endpoint Trunk group UID
Call malicious call trace is active. UID
2214 QSIG PR:Not Voice Denial for path replacement UID Bearer capability
Data low bearer capability of
channel.
2215 QSIG PR:Preind/ Denial for path replacement UID Trunk group UID
priv Call for data preindication call or
data privacy call.
2216 QSIG PR:Measured Denial for path replacement UID Trunk group UID
Call for measured calls.
2217 QSIG PR:No Denial for path replacement 0 UID
Propose propose request not active.
2218 QSIG PR:No Old Denial for path replacement UID 0
Callr when there is no call record of
the old leg.
2219 QSIG PR:Merge Denial for path replacement UID Internal return code
Failure merge failure.
2220 QSIG PR:No IE in Denial for path replacement Call ID UID
Setup setup error.
2221 QSIG PR:Mrg Fail Denial for path replacement UID Internal return code
Old Trk merge failure of old trunk.
2222 QSIG PR:Mrg Fail Denial for path replacement UID Internal return code
New Trk merge failure of new trunk.
2223 QSIG PR:Transfer Denial for path replacement Transit call state
Active when call is not active. state
2224 QSIG PR:Outward Denial for path replacement UID Trunk group UID
Cor Res outward restriction.
2225 QSIG PR:Incoming Denial for path replacement UID Trunk group UID
Cor Res incoming restriction.
2226 QSIG PR:No Denial for path replacement Originating 0
Facilities due to no facilities available. UID
2227 QSIG PR:SS Opt Denial for path replacement. Old CID Old trunk group UID
Not Match
2228 QSIG PR:More Denial for path replacement. UID party count
Party Count
2229 QSIG PR:Same Denial for path replacement. UID Old trunk group UID
Trunk Group
Table continues…
Denial Events

event log (keyword)
2230 QSIG PR:Setup Denial for path replacement Reject UID
Reject setup rejection. indication
2231 QSIG PR:Deny Path Denial for path replacement. B-channel Invoke ID
Retain user
2232 QSIG PR:No Old Denial for path retention for no UID CID
Leg old leg of the call.
2233 QSIG RR:Call Fwd Denial for rerouting for UID Diversion count
Limit crossing call forwarding call
redirections limit.
2234 QSIG RR:Cfnr Div Denial for path rerouting for UID UID
Leg Fail cfnr DivertedLegFailed for
diversion.
2235 QSIG RR:Reroute Denial for rerouting return UID UID
Ret Err error.
2237 CTI phys ext not SA8797: CTI agent physical UID Call ID
sta usr extension not station user.
2238 CTI not dom-ctl/ SA8797: CTI agent not dom- UID Call ID
logged in ctrl logged-in agent.
2239 UUI retrieval SA8797: UUI retrieval failed UID Call ID
failed CTI physical extension.
2240 UUI len over max SA8797: UUI data length UID Dialed extension length
ext siz larger than maximum
extension.
2241 Could not get SA8797: Could not retrieve UID Call ID
modem UID modem extension UID.
2242 Modem ext not sta SA8797: Modem physical UID Modem UID
user extension not station user.
2243 Modem not SA8797: modem not analog UID Modem UID
ana/agt/on ACD logged-in agent with ACD call.
2244 Could not get SA8797: Could not retrieve UID Modem UID
ACDcall CID CID of ACD call
2245 ACD call not CMD SA8797: ACD call is not for a UID Modem skill
meas skl CMS measured skill.
2246 Could not get SA8797: Could not convert UID Login UID
agent2 UID replacement agent extension
to UID.
2247 Agent2 logid not SA8797: replacement agent UID Login UID
sta user login ID not station user.
2248 Agent2 already SA8797: Replacement agent UID Login UID
logged-in login ID already logged-in.
Table continues…
Denial events

event log (keyword)
2249 Could not get CTI SA8797: Could not retrieve Logical Modem UID
lag ext CTI agent login ID extension. agent UID
2250 Could not get CTI SA8797: Could not retrieve UID Call ID
DAC skl DAC skill for CTI agent.
2251 Could not get SA8797: Could not retrieve Modem Split UID
agt2 DAC skl DAC skill for replacement UID
agent.
2252 Could not get SA8797: Error in restoring Modem Modem CID
update ACD data ACD data to replacement UID
agent.
2253 ACD UID not in SA8797: Could not find ACD Modem Internal software group
call rec call UID in call record. UID manager query data
2254 Could not get SA8797: Could not find call Modem CID
ACDcall rec record for ACD call. CID
2255 SA8797 not SA8797 feature Green Bit not Originating CID
enabled enabled. UID
2256 CTI not dom-ctl/ SA8797: CTI agent not dom- Originating CID
logged-in ctrl logged-in agent. UID
2257 Invalid agent2 SA8797: Invalid agent2 login Originating Internal message type
logid ext ID extension. UID
2258 ECF: COS value Enhanced call forwarding: Originating CID
reject the current Class of UID
Service (COS) definition does
not allow enhanced call
forwarding.
2259 ECF: ATD CFWD Enhanced call forwarding: Originating CID
active classic call forwarding all UID
(CFWD) is active for this
station, that received a
ENHCF activation via console
permission.
2260 ECF: ATD CFBDA Enhanced call forwarding: Originating CID
active classic call forwarding busy UID
& don’t answer (CFBDA) is
active for this station, which
received a ENHCF activation
via console permission.
2261 ECF: CFWD active Enhanced call forwarding: UID Call ID or internal
classic Call forwarding all software failure error
(CFWD) is active. number
Table continues…
Denial Events

event log (keyword)
2262 ECF: CFBDA active Enhanced call forwarding: UID Call ID or internal
classic call forwarding busy software failure error
& don’t answer (CFBDA) is number
active.
2263 ECF: Attd fwd own Enhanced call forwarding: Originating Call ID
calls Attendant is not allowed to UID
forward its own calls.
2264 Cannot override Logout-ovr denied, the agent UID 0
logout is not in the logout tables.
2265 DPT not enab on DPT not enabled for both Source NR Destination NR
both NRs network regions.
2266 Answer back Parked call failed to answer Called UID 0
failed back even after second
attempt.
2267 H.248 transaction H.248 transaction timer GW index Transaction ID
timeout expired, gateway did not send
a reply in the allotted time.
See error logs for terms
affected.
2268 ECF: Number Enhanced call forwarding: UID Call ID or internal
invalid Invalid number entered in software failure error
case of extension or call number
forward destination.
2269 ECF: COS via btn Enhanced call forwarding: Originating Call ID
reject The current Class of UID
Service (COS) definition does
not allow enhanced call
forwarding via feature button.
2270 ECF: Default Enhanced call forwarding: Originating Call ID
denial Default denial. UID
2271 ECF: Invalid Enhanced call forwarding: Originating 0
station Activation, deactivation or UID
status is requested by an
invalid station type or remote
user.
2272 No Disc. Call is dropping due to Current B- Call ID
Supervision Tmo. the timeout of 2 hour no- Channel
disconnect supervision timer. UID (UID
IP Trunk LInk Bounce. Cur_buid)
Table continues…
Denial events

event log (keyword)
2273 No Disc. Sup. Call is dropping due to an Current B- Message type
-Invalid Msg invalid stim/msg on a call Channel
in no disconnect supervision UID (UID
processing. IP Trunk Link Cur_buid)
Bounce.
2274 Team Pickup of Station calls another station in Originating Call ID
selfs call the same pickup group, puts UID
the call on hold and dials FAC
for pickup. Disallow pickup of
self-initiated call.
2276 Flow ctrl out of Out of memory for Internal Internal software user
memory UMFlowControl for buffering. software manager bytes used for
queued message flow control.
message
content
length
2277 ECF: Button ext Enhanced call forwarding. Originating Call ID
invalid Feature button extension UID
cannot be mapped to a valid
user ID.
2278 ECF: EAS login Enhanced call forwarding. Originating Call ID
phys ext Logged-in EAS agent’s UID
physical extension is
unavailable for any call
forwarding.
2279 Drop: Call Sate Call state mismatch, drop the Call Call state
Mismatch call. reference
2280 Drop: CRV audit CRV audit timeout, drop the Current B- Call reference
timeout call. Channel
UID (UID
Cur_buid)
2281 ECF: Station no Enhanced call forwarding. Originating Call ID
display Display of status of ENHCF is UID
requested on a station that is
not equipped with a display.
2282 ECF: ATD station Enhanced call forwarding. Originating Call ID
no displ Extension for display of status UID
of ENHCF is questioned on
a station that is not equipped
with a display.
2283 Drop:lk loss tmr Link Loss Delay Timer Current Call ID
expired expired. Drop the call. UID
Table continues…
Denial Events

event log (keyword)
2284 ECF: Remote cfwd Enhanced call forwarding. Originating Call ID
EAS Disallow any remote call UID
forwarding of an EAS loginID
extension.
2285 DPT src/dst NRs Deny DPT request. Source Source NR Destination NR
are same and destination network
regions are the same.
2286 INVITE Domain in the INVITE’s Near-end Far-end IP address
From:domain Inval. “From” header is invalid. Block IP address
for potential toll fraud.
2287 Invalid pub-unk The public-unknown- Terminatin Internal return code
numbering numbering form has not been g UID
populated.
2288 Deny observing Cannot observe because this Originating Call ID
observer is already an observer. UID
2289 IP RRJ MAC SA8944: Registration rejected First two Last four nybles of MAC
denied-SA8944 because extension is already nybles of address.
registered based upon same MAC
MAC Address (i.e., bound to a address.
port).
2290 MAC Address SA8944: No MAC address UID IP address of the
blank-SA8944 was provided by the registering endpoint.
registering station. Must be
treated as a non-SA8944
registration and the IP
addresses instead must be
used.
2291 Rem off-net covpt For non-QSIG or non DCS Originating Call ID
is busy coverage, the offnet coverage UID
point is busy and there is no
coverage point to terminate
the call.
2292 Unable to Connect C-LAN sent CONNECT Far-end IP Far end port
request to remote end, but address
didn’t receive any response
within the timeout interval.
2293 Out Trk COR timer “Outgoing Trunk Disconnect UID Call ID
expire Timer (minutes)” expired and
disconnected the trunk. cor
form, page 2.
Table continues…
Denial events

event log (keyword)
2294 SA8702 disallow SA8702 does not allow Originating Call ID
UCID copy since UCID copy, since CCR is UID
CCR is configured configured.
2295 RAI for RAI EndpointIdentifier had a User UID IP address
unregistered user UID but no H.323 user was
found for it.
2296 No agent ID in EAS agent login FNU received Originating Call ID
login FNU without agent ID UID
2297 SIP endpoint The SIP endpoint rejected the Incoming UID
refused video video media in response to logical
the re-Invite message. channel
number
2298 H.323 endpoint The H.323 endpoint did not Incoming RTP IP Address
refused video accept the video OLC sent, logical
possibly because its receive channel
and transmit capabilities are number
non-symmetrical.
2299 Bad BRI TSC SS There is not a suitable UID UID
Protocol Supplementary Service
Protocol administered for
termination of BRI TSC
connection.
Connection manager denial events

Denial Events generated by the Connection Manager are listed in the following table.
Table 37: Connection Manager denial events (2300 - 2399)
Even Event Description, as it Explanation Event Data Event

tType is displayed on the event 1 Data 2
log (keyword)
2300 Ept capabilities Endpoint connects to TDM bus or is IP ept Failed
mismatch hairpinned capabilities mismatch. region region
2301 Tran/rec codec Transmitted or received codec mismatch. PortID Codec,
mismatch
Call ID
2302 Ip_ept is in Illegal loopback condition. PortID Call ID
loopback
2303 Silence suppress Endpoint connects to TDM bus or is UID Port-ID
mismatch hairpinned silence suppression mismatch.
Table continues…
Denial Events

log (keyword)
2306 Reject outbound OLC Reject outbound OLC. PortID Cause,
CID
2307 TDM resource Time Division Multiplexed (TDM) resource Service 0
blockage blockage. index
2308 Selected codec Codec no longer supported. PortID Codec,
mismatch
Call ID
2309 Drop call codec Drop call, codec mismatch. port-id/ Call
mismatch LAN ID/LAN
region/UID region/
message
2310 Invalid regions Invalid region. Port Service
index
2311 Invalid codec Invalid codec region. Port Service
region index
2312 No DSP resource No Digital Signal Processor (DSP) Port Service
resource. index
2313 No free list No channels on free list.
channels
2314 No channel No channel resources. IP ept Failed NR
resources region
2315 Not enough capacity Not enough prowler (media processor) Port Service
capacity. index
2316 Drop call, no bandwidth for endpoint’s PortID Call ID
codec.
2317- not assigned
2328
2329 No BW, prowler <--> No available bandwidth (BW) channel Net-work Pre-ferred
IP ept resources from the endpoint to the region of desti_natio
necessary resources. The call fails. the end- n network
point region
2330 No BW, prowler <--> No bandwidth channel resources between Master NR Slave NR
prowler processors.
2331 No VOIP channel, PN No Voice Over IP channel resources Port Service
<--> PN between port networks. index
2332 No BW, prowler <--> No bandwidth channel resources between LAN region LAN region
MG processor and gateway.
2333 No VOIP channel, PN No Voice Over IPchannel resources Port Service
<--> MG between port network and gateway. index
Table continues…
Denial events

log (keyword)
2334 No channel No available bandwidth to access the Net-work Net-work
resources necessary resources. The call fails. region region (to)
(from)
2335 RejReqMode-no Deny inbound RM, not compatible with Port Service
common mode modes received in request. index
2336 RejReqMode-no Deny inbound RM, cannot arrive at Port Service
common mode common profile. index
2337 RejReqMode-no modes Deny inbound RM, no data modes were Port Service
rcvd received in request. index
2338 RejReqMode-not 2 Deny inbound RM, there are not two Port Service
connectd pt_conn parties on call. index
2339 RejReqMode-no Deny inbound RM dirip ept, no common Port Service
common mode profile. index
2340 T38Fail-no voip Insufficient voip resources. Port Service
resources index
2341 T38Fail-far end Far-end timeout. Port Service
timeout index
2342 T38Fail-near end Near-end timeout. Port Service
timeout index
2343 ReqMode reject Request reject received - TDM/HP Port Reason for
received connection. rejection :
• (MODE_
UNAVAIL
ABLE)
• MULTIP
OINT_C
ONSTRA
INT
• REQUES
T_DENIE
D
Table continues…
Denial Events

log (keyword)
2344 ReqMode reject Request reject received - DIRIP Port Reason for
received connection. rejection:
• MODE_
UNAVAIL
ABLE
• MULTIP
OINT_C
ONSTRA
INT
• REQUES
T_DENIE
D
2345 ReqMode release Request release received - TDM/HP Port Service
received connection. index
2346 ReqMode release Request release received, DIRIP Port Service
received connection. index
2347 Rej inc T38OLC, not Deny inbound T38 OLC - not in Port Service
seq'd sequence, dropping call. index
2348 Rej inc T38OLC, no Deny inbound T38 OLC - incompatible Port Service
common mode, TDM/HP connection. Dropping index
call.
2349 Rej inc T38OLC, no Deny inbound T38 OLC - incompatible Port Service
common mode, DIRIP connection. Dropping call. index
2350 Rej inc T38OLC, Deny inbound T38 OLC - IDLE state. Port Service
idle state Dropping call. index
2351 Failed Xoip Attempt XOIP failed attempt, invalid call type. Xoip type Event type
2352 Failed Fax Relay Fax Relay XOIP failed attempt. Xoip type Event type
Xoip
2353 Failed Modem Relay Modem Relay XOIP failed. Xoip type Event type
Xoip
2355 IGAR trunk limit Attempt to exceed the number of trunks Source NR IGAR in-
exceeded allowed for Inter-Gateway Alternate use in NR
Routing (IGAR) in this network region.
2356 All IGAR managers All Inter-Gateway Alternate Routing Source Destination
in-use (IGAR) manager are in use. gateway gateway
2357 Failed Fax Prowler Prowler reports channel cannot go to FAX Port 0
mode.
2358 Failed Fax Media Gateway reports channel cannot go to Eph port 0
Gateway FAX mode.
Table continues…
Denial events

log (keyword)
2360 RejReqMode-no Deny inbound RM - no common profile. PortID Service
common mode Already in a sequence, have a collision. index
2361 RejStartT38-no Cannot start RM sequence -no common Port Service
common profile between endpoint and region/hw index
(VOIP detected a fax tone)
2362 Multimedia OLC Reject inbound multimedia Open Logical PortID Call ID
rejected Channel (OLC) due to state mismatch.
2363 Multimedia Multimedia reject outbound Open Logical PortID Call ID
OLCReject received Channel (OLC).
A video endpoint is denying
Communication Manager’s attempt to
establish video.
2364 BCF Rcvd-diff Different confirming bandwidth than what -1 Confirming
bandwidth is stored. BW
2365 RejStartT38-not in Cannot start RM sequence - T38 is not Port Service
rgn/hw supported in region/hw intersection (VOIP index
detected a fax tone).
2366 RejAckT38-no modes Deny inbound RM Acknowledgment. No PortID Service
in msg data modes were received in the request. index
(Fast Request Mode - dcap ptr is null).
2367 RejAckT38-no modes Deny inbound RM Acknowledgment. PortID Service
in msg No data modes were received in the index
request. (Fast Request Mode - no modes
received).
2368 RejAckT38-not Deny inbound RM Acknowledgment. PortID Service
common Mode received in Ack was not common index
(Fast Request Mode - TDM case).
2369 RejReqMode-fast Deny inbound RM Acknowledgment. PortID Service
collision There is a collision, already in T38 index
sequence (Fast Request Mode case).
2370 No VOIP activity detected VOIP inactivity has been detected by this Port index 0
media processor channel. Call will be torn
down.
2372 MG link needs Hardware codecs do not match. There Gateway Codec set
encryption is a non-encrypted H.248 signaling link number used
on the gateway and a codec set with
only encrypted codecs. Encryption keys
cannot be left exposed on unencrypted
signaling link.
Table continues…
Denial Events

log (keyword)
2373 No Video BW No bandwidth is available for video. NR1 NR2
available
If Event Data 1 and Event Data 2 are both
0, no bandwidth is available for video and
video is removed for the duration of the
call.
2374 No Priority BW A priority video caller was not able to get NR1 NR2
available bandwidth to make a video call.
2375 OLC master/slave OLC mismatch, master/slave mismatch. PortID Codec
conflict
2376 No codec set defined in ip-network- Master Slave
region. portId portId
2377 Avc Cannot start Cannot start Request Mode sequence IP ept port IP ept NR
Request Mode because no fax capabilities received from
sequence the endpoint.
2378 Deny inbound Deny inbound Request Mode because IP ept port IP ept NR
Request Mode T.38 is not supported on either in the
network region or media resource
2379 Cannot build CLEAR Cannot build CLEAR IGC because clear Port codecSet #
IGC channel is OFF in the codec set (page 2). used for
the IGC
2380 Old media processor Trying to setup a clear data call but media Angel PNN
firmware, does processor firmware is old and does not
not support Clear support Clear Channel.
Channel.
2381 Avc Could not add Could not add ports to primary Port index 0
ports subconference.
2382 Avc Could not req Could not acquire IGMC. Port index 0
IGMC
2384 Avc Closing while MCU closing during active conference. 0 0
active
2385 Avc Mcu non-video MCU port is not video enabled. MCU port 0
port index
2386 Avc Mcu selection No MCU available that suits the 0 0
failed conference.
2387 Avc Conference AVC flow control delayed. 0 0
delayed
2388 Avc High usage AVC flow control denied. 0 0
denial
2389 Avc Trk member AVC trunk member limited. Conference Port Count
limited ID
Table continues…
Denial events

log (keyword)
2390 Avc Video Not AVC: Network Region (NR) does not MCU MCU
Allowed allow video. region region
2391 Video Not Allowed NR does not allow video. NR1 NR1
2392 Avc Mcu drop’d AVC: MCU dropped inuse port. MCU 0
inuse port number
2393 Avc: MCU rejected Avc: MCU rejected port setup. MCU 0
port setup number
2394 Avc: Port request AVC: Port request failed. 0 0
failed
2395 AVC: Bridge move AVC: Bridge move failure. 0 0
failure
2396 No IGMC available No IGMC available on MCU. Port index 0
2397 No ports free, either administered or Conference MCU
reported by MCU. ID number
2398 Inter-region network connection failed. Source Destination
Gateway Gateway
2399 DNY_CLASS_NO_CAP CPTR with no cadence capability 0 0
requested, not found.
Dial plan manager denial events

Denial Events generated by the Dial Plan Manager denial events are listed in the following table.
Table 38: Dial Plan Manager denial events (2400 - 2406)
Event Event Description, as it Explanation Event Event

Type is displayed on the event Data 1 Data 2
log (keyword)
2400 UDP: too many Digit conversion counter exceeded. Partiti Extens
conversions on ion
numbe
r
2401 UDP: node-rte pat Node number route pattern is blank. Partiti Node
blank on Numb
numbe er
r
2402 UDP: ENP code blank ENP numbering prefix is blank. Digit End
count point
index
Table continues…
Denial Events
Event Event Description, as it Explanation Event Event

Type is displayed on the event Data 1 Data 2
log (keyword)
2403 Loc Digits Size Location Prefix digits size is not n, where the UDP Locati Numb
incorrect form’s matching row, Insert digits field is Ln. on er of
digits
to
insert
2404 Var-in-Vec No adm Variable Access Code (VAC) in Variables in Featur Digit
for VAC Vector Table not administered. e ID
2405 Var-in-Vec Invalid Invalid digit entered, or Feature Access Code Featur Digit
digit corrupted from call processing to dial plan e ID
manager.
2406 Unadministered annc Unadministered announcement extension for a Locati Intern
ext location. on al
return
code
2408 Keypad dialing an Dialed an enb-ext using keypad Locati Dialed
enb-ext on digits
2409 Proxy RP no TG No trunk group assigned in route pattern for the Route Locati
assigned proxy select route path field on the locations form. patter on
n ID
2410 DID AAR/ARS not Allow AAR/ARS Access from DID/DIOD field set Featur Port
Allowed as number. e ID type
2411 extn valid but Dialed number is valid according UDP form, but is Locati Call
unassigned unassigned. Dial Plan Parameter says to quit and on type
not try other CTA route choices.
2412 Off-PBX UID table Denial event for exceeding limit of XMUID table. UID Count
full of
curren
tly
admini
stered
Xmuid
_e
entries
2413 Off-PBX Number table Denial event for exceeding limit of XMNUM table. Xmobil Count
full e UID of
curren
tly
admini
stered
Xmnu
m_e
entries
Denial events
Data manager denial events

Denial events generated by the Data Manager are listed in the following table.
Table 39: Data Manager Denial Events (3001 - 3004)
Event Event Description, as it is displayed on the Explanation

Type event log
3001 Bridge in use PR_BRIDGE object is in use
3002 Button in use PR_BUTTON/PR_BTNTTI object is in use
3003 Station/Trunk in use One of the station/trunk PREC objects is in
use
3004 Team Group in use PR_TEAM object is in use
Dial access plan denial events

Dial Access Plan denial events are listed in the following table.
Table 40: Dial Access Plan denial events (3101 - 3199)
Even Event Description, as it Explanation Event Event

tType is displayed on the event Data Data
log (keyword) 1 2
3101 DCS invalid PBX/ Distributed Communication System (DCS) requires 0 0
Mach/Node Trunk Group pbx-id, Signal Group Mach-id, or AAR
Analysis node number.
3102 DCS no msg buffer No Distributed Communication System (DCS) 0 0
avail message buffers are available.
3103 DCS Station LWC Distributed Communication System (DCS) station Index UID
mis-admin Leave Word Calling is misadministered.
3104 DCS Trunk Group Distributed Communication System (DCS) trunk Origin Trunk
mis-admin group is mis-administered. ating group
numb
PBX
er
ID
numb
er
3105 DCS invalid PBX/ Distributed Communication System (DCS) requires Sessi Remo
Mach/Node Trunk Group pbx-id, Signal Group Mach-id, or AAR on te
Analysis node number numb
PBX-
er
ID
return
ed
3106- not assigned
3199
Denial Events
Meet-me conference denial events

Denial events generated by the Meet Me Conference process are listed in the following table.
Table 41: Meet Me Conference denial events (3201 - 3299)
Even Event Description, as Explanation Event Event Data

tType it is displayed on the Data 1 2
event log (keyword)
3201 Meet-Me Access chg Meet-me security/access change time-out. UID UID
TMO
3202 Invld Num Digits MM Meet-me security/access change received UID UID
Acc. too many digits.
3203 MM Extention not Meet-me security/access change not a UID UID
valid valid extension.
3204 MM Access Chg Not a Meet-me security/access change not a UID UID
VDN Vector Directory Number extension.
3205 MM Invalid Access Meet-me security/access change invalid UID UID
Entered security/access code.
3206 MM Access Obj/SAT SAT window with Meet-me security/access UID UID
Busy code or object is busy. Cannot make
changes via FAC.
3207 Merge Meet-me Conf User tried to merge to a existing Meet- UID UID
call me conference call and the merge failed
validation.
3208 Serv Observ Meet-me User tried to service-observe a Meet-me UID UID
VDN conference call and so_route() failed.
3209 Meet-me Conf call Meet-me conference total party number UID UID
full has exceeded the limit.
3210 Wrong MM Acc. code Party failed to dial correct Meet-me UID UID
dialed conference access.
3211 Chg Station no Meet-me security/access. The station UID UID
Cons/Perm extension does not have console
permissions.
3212 VDN not a meetme Vector Directory Number (VDN) is not a UID UID
type meetme type.
3213 MM Invalid Conf Station extension does not match controller UID UID
Ctrlr Sta extension.
3214 MM Inv Trk not Trunk User ID not allowed as a controller UID UID
Remote Acc extension.
3215 MM Invalid Station Invalid station type of calling extension. UID UID
Type
3216 Conf/Transfer 2 Conference/or transfer to Meet-me UID UID
Meet-me conference call.
Table continues…
Denial events
Even Event Description, as Explanation Event Event Data

tType it is displayed on the Data 1 2
event log (keyword)
3217 MM Abbrev Dial Cannot use abbreviated dialing - invalid. UID CID
Invalid
3218 Error in EMMC route Error retrieving Enhanced MeetMe UID UID
dgt Conferencing (EMMC) routing digits.
3219 Empty EMMC route Empty Enhanced MeetMe Conferencing UID UID
digits (EMMC) routing digits.
3220 Exceed EMMC active Exceeded Enhanced MeetMe UID UID
conf Conferencing (EMMC) active conference.
3221 Exceed EMMC license Exceeded number of Enhanced MeetMe UID UID
ports Conferencing (EMMC) license ports.
3222 Exceed EMMC party Exceeded Enhanced MeetMe UID UID
limit Conferencing (EMMC) party limit.
3223 EMMC- no new vector Enhanced MeetMe Conferencing (EMMC)- UID UID
proc no new vector proc.
3224 Add meet-me user/ Can’t add meet-me party if whisper page is UID UID
whsp pg active.
3225- not assigned
3299
3300 IP RRJ-LSP not ProcRRQ LSP is not active yet. The first Far IP 0
active value is unique ID. Second value is IP address
address of entity trying to register.
3301 LSP has not been NULL IP Address
administered
3302 LSP Version LSP is only permitted to register if it has IP None
Mismatch the same software version as the main or a Address
later software version than the main.
3303 LSP/ESS attempting IP None
to register with Address
LSP/ESS
3305 LSP Memory LSP Memory Configuration (DRAM) is Memory IP Address
Configuration inadequate to handle translations from the Capacity
(DRAM) inadequate main.
Data error denial events

Data error-generated denial events are listed in the following table.
Denial Events
Table 42: Data Error denial events (3400 - 3499)

log (keyword) 1 2
3400 Error in vector Bad step type. Drec Vector
data type numb
er
3401 Invalid vector step Bad step type. Vector Step
type step type
value
3403 Bad date in MCT Bad Malicious Call Trace date (date, month). Date Month
record
3404 Bad date in MCT Bad Malicious Call Trace date (hour, minute). Hour Minut
record e
3405 Unicode cus file Unicode translation read error. Entire customer file Error 0
not read not read. count
3406 Error in Unicode Unicode translation read error. Error found in Error 0
cus file customer file. count
3407 Unicode ava file Unicode translation read error. Entire Avaya file not Error 0
not read read. count
3408 Error in Unicode Unicode translation read error. Error found in Avaya Error 0
ava file file. count
3409 Usr-def cus file User-defined translation read error 3409. Entire Error 0
not read custom_ file not read. count
3410 Err in User-def cus User-defined translation read error (3410). Error Error 0
file found in custom_ file. count
3411 Usr-def ava file User-defined translation read error (3411). Entire Error 0
not read avaya_ file not read. count
3412 Err in User-def ava User-defined translation read error (3412). Error Error 0
file found in avaya_ file. count
3413 Unicd ava2 file not Unicode translation read error. Entire Error 0
read avaya_unicode2 file not read. count
3414 Err in Unicd ava2 Unicode translation read error. Error found in Error 0
file avaya_unicode2 file. count
Table continues…
Denial events

log (keyword) 1 2
3419 Unicd cus2 file not Unicode translation read error. Entire Error 0
read custom_unicode2 file not read. count
3420 Err in Unicd cus2 Unicode translation read error. Error found in Error 0
file custom_unicode2 file. count
3425 Unkwn Err in PhMsg Unknown error while processing unicode telephone Error 0
file message file. count
3426 Busy indicator Busy Indicator button push. Denied for TAC. UID NULL
denial event
3427- not assigned
3499
Contact closure denial events

Contact Closure Denial Event Types 3501 - 3503 show successful feature activations and are kept
as historical data, as listed in the following table.
Table 43: Contact Closure denial events (3501 - 3503)
Event Event Description Explanation Event Data 1 EventData 2

Type (keyword)
3501 Relay OPEN Contact closure OPEN event UID Feature ID
3502 Relay CLOSE Contact closure CLOSE event UID Feature ID
3503 Relay PULSE Contact closure PULSE event UID Feature ID
Survivable core server denial events

Survivable Core Server-generated denial events are listed in the following table.
Denial Events
Table 44: Survivable Core Server denial events (3600 - 3604)

t it is displayed on the Data 1
Type event log (keyword)
3600 IP RRJ-Survivable Survivable Core Server has not been 0 IP address of
Core Server not administered. sending Survivable
admin Core Server
3601 IP RRJ-Survivable Internal EssMgr_ptr has not been 0 IP address of
Core Server obj initialized. sending Survivable
not init Core Server
3602 IP RRJ-Survivable Survivable Core Server sent a bad SID IP address of
Core Server bad system ID. sending Survivable
SID sent Core Server
3603 Survivable Core Server had a failure 0 IP address of
from ParseNsdLSPInfo method. sending Survivable
Core Server
3604 IP RRJ-Survivable Survivable Core Server memory Memor IP address of sending
Core Server memory configuration (DRAM) or duplication y survivable core server
size card memory configuration is capacit
inadequate to handle translations y
from the main.
3605 Duplex Survivable Core Server 0 IP address of sending
registering via IP Address other than survivable core server
that of Duplicated PE Alias.
User Manager Denial Events (3700 - 3915)

Denial Events generated by the user manager are listed in the following table.
Table 45: User Manager denial events (3700 - 3799)
Event Event Description Explanation Event Data 1 Event Data 2

Type (keyword)
3700 IP GRJ DH-exchange from GRQ failed. UID IP address
DH Exchange Missing or incorrect data.
failure
3701 IP Trunk DH-exchange from trunk xRQ failed. UID IP address
DH Exchange Missing or incorrect data.
failure
3702 EMU:more than EMU - user has more than Local UID Registration
one act ca one active call appearance count
during registration or deregistration
operation.
Table continues…
Denial events

Type (keyword)
3703 EMU:user not EMU - trying to deregister a user that Local UID UID
registered is not registered. This is a misop by
the caller.
3704 EMU:no dereg EMU - trying to deregister a user that Local UID CID
on act user has active calls.
or
UID
3705 EMU:no reg-cur EMU - trying to register on an Local UID CID
user reg already currently registered user.
or
0
3706 No VOIP H248Msg:ErrorHandler() VOIP Gateway ID Context ID from
Resource Resources unavailable. Media Gateway
3707 No MG Resource H248Msg:ErrorHandler() no gateway Gateway ID 0
resource available.
3708 No time slot Flexible Ann Allocation. All the time Gateway ID Context ID from
on MG slots are exhausted on media GW. Media Gateway
3709 Off-Pbx Stn Station is out of service or license FN UID Station UID
OOS/License failed.
failure
3710 EMU:no reg- EMU - trying to register on an Current user UID
user emergency endpoint that recently made an
E911 call, the endpoint can be the
potential visitor or home user.
3711 Warning MM History-Info removed from SIP UID Trunk Group
hist-info rem message for a MM user.This Index
behavior is correct per requirements
but can be confusing. The Support
Request History field is set to no
on this trk grp and if a MM user is
involved then mis-admin is likely for
this trk grp.
3712 ESIG MG-VoIP VoIP FW / MG FW mismatch: Gateway ID Context ID from
FW mismatch Media Gateway
VoIP cannot ESIG to ephs, but MG's
FW version states that it can.
3713 VOA playing, If VOA (VDN of Origin Current user UID NULL
Btn denied Announcement) is playing, then (Cur_user)
button push on any other line
appearance is not allowed.
Table continues…
Denial Events

Type (keyword)
3714 Agent login INVITE is rejected since invalid Current PRI Current B-
failure INVITE FNU parameters is received. Signaling UID Channel UID
Password is present but Agent ID is (UID Cur_psuid) (UID Cur_buid)
missing.
3715 QSIP: data This is an incorrect use of H.323 Current B- current nca-tsc
cont. missing trunk with QSIP enabled, since there Channel UID UID (UID
is no surrounding SIP tunnel. (UID Cur_buid) Cur_tuid)
3717 QSIP This can occur due to erroneous Current B- Call ID
SipBchTerm: no route pattern configuration. Incorrect Channel UID
data pure SIP trunk is seized. Instead of (UID Cur_buid)
pure SIP trunk it should use QSIG
leg of the QSIP pair.
3718 QSIP: Invalid A response for QSIP INVITE is Connected party Call ID
Response received on a non QSIP enabled SIP UID
trunk. It is not a supported network
administration.
3719 QSIP Enable This occurs due to QSIP Signaling Group Trunk member
QSIP on SigGr administration issue. QSIP is not UID where the
enabled on signaling group. issue occurs.
3720 QSIP Enable This occurs due to QSIP Trunk Group Trunk member
QSIP on TrkGr administration issue. QSIP is not UID where the
enabled on trunk group. issue occurs.
3721 QSIP Invalid This occurs due to QSIP Signaling Group Signaling Group
SigGr Pair administration issue as the signaling A B
group references are either invalid
or empty. Signaling group A should
point to signaling group B and
signaling group B should point back
to signaling group A.
3722 QSIP Invalid This occurs due to QSIP Trunk Group A Trunk Group B
TrkGr Pair administration issue as the trunk
group references are either invalid or
empty. Trunk group A should point
to trunk group B and trunk group B
should point back to trunk group A.
3723 QSIP Member Both trunk group member has Trunk member Trunk member
use diff Pair valid QSIP administration but use UID A UID B
different trunk or signaling group
pairs. This can occur due to QSIP
administration issue.
3724 SIP video This occurs when a video call cannot 0(SIP)/1(H323) Media IP
dynRTP be supported in SIP and H.323 address
mismatch interworking due to dynamic RTP
payload mismatch.
Table continues…
Denial events

Type (keyword)
3725 IGAR IGAR termination is denied as user Current user UID Type of call
termination does not have any call appearance. (Cur_user)
failure
3726 Insufficient SIP call is denied due to insufficient Current B- Call ID
SIP bandwidth CAC bandwidth Channel UID
(UID Cur_buid)
3727 Call in The call termination is rejected due Current user UID Call appearance
reconstruct to an on-going active call, which is in (Cur_user)
state reconstruction state.
3728 FGDN Table not FGDN Table not administered Route pattern UID
correct correctly.
3729 FGDN RP not FGDN Route Pattern not Route Pattern UID
correct administered correctly.
3730 NO HIDDLN for AST II transfer is denied since no Station UID Current user UID
ast2 xfer hidden line appearance is available (Cur_user)
for AST 11 transfer.
3731 Incompatible Resources were available, but could Endpoint port Endpoint UID
caps for endpt not be used because of endpoint
capabilities incompatibility.
3732 No location No location proxy select route NA NA
Proxy Route pattern is defined, so REFER is
rejected.
3733 Insufficient MoIP resources are unavailable. Gateway number ContextID that is
MOIP rsrcs received from
the MG
3735 This occurs when SIP calls Maximum SIP Current number
exceeding maximum calls is allowed calls in system of SIP calls
in the system, so return without
creating an object.
3736 Video A video call is denied in SIP and UID Call ID
Encryption H.323 interworking due to encryption
mismatch mismatch.
3737 Feature on SVC This occurs when feature is Current user UID Call appearance
Link administered on a service link since (Cur_user) to simulate
features on service link are not bridge
allowed.
3738 No Softswitch Soft switch is not administered for UID Current PRI
admin failover event on a signaling group. Signaling UID
(UID Cur_psuid)
3739 ASAC: Calls Active call count is currently greater Administered outgoing active
over Budget than the budget administered on the outgoing budget call count
trunk form. on trunk
Table continues…
Denial Events

Type (keyword)
3740 TLS phone no Communication Manager rejects UID Endpoint IP
certificate the TLS connection because the address
endpoint did not provide an Identity
certificate.
3741 SA8886 Deny SA8886 has denied incoming call. Digits 0
Incoming call
3742 Direct CES Denial event when direct CES UID Direct
link Exceed subscription count is exceeded than connection count
MAX_ONEX_SUB_DIR.
3743 Total CES link Denial event when indirect (via SM) UID Count
Exceed CES subscription count is exceeded
than MAX_ONEX_SUB.
3744 Add codec For a H323 call, codec set having UID Call ID
other than only OPUS codec is not allowed.
OPUS
3745 No such button This event occurs when FNU Current PRI Current B-
on station is received but there is no Signaling UID Channel UID
corresponding feature button on (UID Cur_psuid) (UID Cur_buid)
station.
3746 Res Pri hdr This event occurs when Call ID UID
err send 417 Communication Manager received
or
an incorrect Resource-Priority along
with a required header option Current B-
tag for O_RESOURCE__PRIORITY. Channel UID
Hence Communication Manager will (UID Cur_buid)
respond with 417 response.
3747 XMOB preserved This event occurs when the Station UID Current B-
call exist Communication Manager receives Channel UID
SETUP from XMOBILE IP Dect (UID Cur_buid)
station for which a call already exists
in preserved state.
3749 NRG-Loc name An administration error occurred; Network Region Vector iterator of
inconsistent Communication Manager has Group store
received a response for bandwidth nrg_bw_tuple
PUBLISH but the response does not
include location name.
3750 Hotline brg Hotline feature is not supported for primary user for UID
app failure bridged appearance on SIP station. bridge
appearance
3751 Block Mobility OPTIM call (non-OPS) is not allowed originating UID Call ID
call to extend in telecommuter mode
when SA9135 is enabled.
Table continues…
Denial events

Type (keyword)
3752 OPTIM in call This event occurs when a user is Station UID Feature
FAC failed trying to invoke in-call FAC during associated with activation code.
an improper call state, which is not the trunk
supported. It could be that call has a member.
shared voice connection or there is
no call appearance left.
3753 Init Publish This event occurs when Init homing SIP request
Not Done Communication Manager does status of CM. 0 - received by
not send the INIT publish to INIT_PUB_NOT Communication
Session Manager yet and all _DONE 1 - Manager
the requests that Communication INIT_PUB_DON
Manager receives except for E2-
OPTION, SUBSCRIBE, NOTIFY are INIT_PUB_IN_P
rejected with a 603 response code. ROG
Note:- This applies only if
Communication Manager is in cluster
mode.
3754 Reg forbidden This event occurs when NA NA
on this CM Communication Manager forcefully
unregister a station because
Communication Manager is in
passive mode.
Note:
This is applicable only if
Communication Manager is in
cluster mode.
3756 Unhomed Stn This event occurs when a user is Current User Homing status of
Orig deny not homed on this Communication the user:
Manager, the call origination for this
• 0 - UNHOMED
user is not allowed.
• 1 - HOMED
Note:
• 2-
This is applicable only if UNHOMING_I
Communication Manager is in N_PROGRES
cluster mode. S
3757 Message This event occurs when voice mail is Station UID Current B-
Cellular VM detected. The voice mail of EC500 Channel UID
Detected receives the call instead of EC500,
and so Communication Manager
drops the call.
Table continues…
Denial Events

Type (keyword)
3758 AAAP link drop This event occurs when Station UID Current B-
by UC STN Communication Manager receives Channel UID
an unexpected bye from AAAP/RAP
link.
3759 Node: 323 Reg This event occurs when an Station UID Index of
Forbidden H323 station tries to register at Communication
cluster Node. H323 stations should Manager, where
register only at the designated this station is
Communication Manager. trying to register.
3760 Node: MG Reg This event occurs when a Media NA Index of
Forbidden Gateway tries to register at cluster Communication
Node. Media Gateway should Manager, where
register only at the designated this Media
Communication Manager. Gateway is
trying to register.
3761 Deny 323 Reg, This event occurs when the H323 Station UID Index of
HomePolicy station has a COR whose homing Communication
policy is not configured as persistent. Manager, where
this station is
trying to register.
3762 Deny 323 Reg, This event occurs when the H323 Station UID Index of
PrefCM station has a COR with a persistent Communication
homing policy, but its preferred CM Manager, where
is not the designated Communication this station is
Manager. trying to register.
3763 DNY_323_REG_DE This event occurs when a H.323 Station UID Index of
SIG_CM_PASSIVE station tries to register on a Communication
(UM_DNY_BASE+6 designated CM who is in passive Manager, where
3) mode. Passive designated CM station is trying
cannot take any H.323 station to register.
registrations.
3900 MG No G711 Media Gateway on which T.38 Gateway number NA
fback support fallback to G711 is attempted does
not support the G711 fallback
feature.
3901 V150: No GW This event occurs when the selected SID port
support gateway does not support v150mr.
3902 V150: No This event occurs when there are SID port
system mrmods no common modulations between
gateway and administered codec-
set.
3903 V150: No ept Error occurs as the endpoint is out of SID Direction of caps
MOIP memory MoIP/V150 memory. to or from the
endpoint
Table continues…
Denial events

Type (keyword)
3904 V150: No igc Error occurs as there is no MoIP/ SID Port table index
MOIP memory V150 memory to store caps in IGC
ephemeral.
3905 V150: No RTP Cap does not support RFC2833 SID Administered
RFC2833 DTMF (telephone-events) over RTP. Codec set
RFC2833 is crucial to the DSP for number
supporting V.150.1. Either of the
intersections such as IP endpoint
or gateway or administered codec-
set do not have RFC2833 in cap.
Another reason is the configuration
of the IP DTMF transmission mode
in the system-parameters ip-option
form, which is not set as rtp-payload.
3906 T38ECM: No GW ECM is optioned on codec-set. But Codec set Gateway
support gateway selected for T38 does number
not support ECM. T38 is going to
proceed with ECM=off.
3907 V150: No This event occurs when there is no SID Administered
common ANS common RFC2833 ANS events for Codec set
evnts V150mr. number
3908 V150: No Modem Relay (MR) is not supported. SID Administered
common SSE Audio and MR events are not Codec set
evnts common. number
3909 V150: No Occurs when there is no common SID Administered
common mrmods modulations for V150mr in admin, Codec set
SID
gateway capex and SDP. number
3910 V150: No RTP One or both endpoints do not IP endpoint IP endpoint
RFC2833 support RFC2833 DTMF (telephone- region 1 region 1
events) over RTP Which is required
for V150mr.
3911 Toll If SA9122 is used, then public and Location 1 Location 2
compliance - private trunks with different locations
call route cannot be used in the same call.
failure
3912 V150: no Gateway supports V150 but it has no SID port
resources V150 resources available.
avail
3913 Max Num of This event occurs when maximum SID Codec set
Video Endpts number of allowed video IP
endpoints is active on video calls. No
more video calls can be allowed.
Table continues…
Denial Events

Type (keyword)
3914 NRG denied BW Bandwidth for Network Region Network region Precedence
by SM Group (NRG) is denied by SM in group number Level and pool
response to bandwidth PUBLISH type.
sent by CM in SM managed
bandwidth.
3915 RFC2833 TTR The underlying media resource Port requesting NA
not supported could not connect TTR in TTR
CM_RFC2833_DG mode. This mode
is only supported by AMS and
Gateways having CAPEX for
RFC2833 digit determination.
Call processing denial events (5000 - 5099)

Event Types 5000 - 5099 are a continuation of call processing-generated denial events, and are
listed in the following table.
Table 46: Call processing denial events (5000 - 5099)
EventTy Event Description, Explanation Event Data 1 Event Data 2

pe as it is displayed
on the event log
(keyword)
5000 Video bridge A signaling group belonging to 0 IP address of
region mismatch a video bridge trunk had a sending
network region that didn’t match Survivable
the others. Core Server
5001 H.323 Deny hold for transfer, hold, or 0 IP address of
OgDirMedia, dny conference if the call started as sending
xfer H.323 outgoing direct media call Survivable
to a non-Communication Manager Core Server
system and H.245 is not up yet.
5002 RAI RAI EndpointIdentifier didn’t UID Far-end IP
EndpointIdentifi correspond to a UID we know of. address
er
5003 No suitable ETSI There is no suitable ETSI CCBS UID of station B-channel
CCBS support support administered for ETSI UID
trunk link.
5004 Not valid PIN SA9014 feature cannot be UID Call ID
for SA9014 activated since either the TODSL
Release Interval field of the
authentication code’s COR is
blank or PIN is invalid.
Table continues…
Denial events

on the event log
(keyword)
5005 Manual locked SA9014 feature cannot be UID Call ID
station activated as the station is locked
by manual station lock.
5006 Paging call hold Paging call cannot be put on hold UID Call ID
denied by user.
5007 RAC build The administrator receives User ID of IP address of
failure availability information from a signaling group far end
video bridge but is unable to build
an acknowledgement.
5008 SIP Alt Route This event occurs when an Current PRI Current B-
Timer expiry Alternate Route Timer has expired Signaling UID Channel UID
before any non-provisional (UID Cur_psuid) (UID
response is received. Cur_buid)
5009 HDE StatLock, Hot Desking Enhancement, on Current user UID NULL
Btn denied Station-Lock Feature button is not (Cur_user)
allowed.
5010 SHRDMAP:Parsing NOTIFY parsing failed. Return code for Content
Error parse failure. length
5011 SHRDMAP:Invalid Invalid NOTIFY Body Return code for Content
Body getting message length
buffer.
5012 SHRDMAP:Empty Empty NOTIFY Body Return code for Content
Body getting message length
buffer.
5014 SHRDMAP:SUSER Failure in inserting entry into Shared Map UID Operation
Insert Fail Shared Map Table. NOTIFY Type
values are not inserted
successfully.
5015 SHRDMAP:DPM Failure in inserting entries in Shared Map UID Operation
Insert Fail Dial Plan but NOTIFY values are Type
inserted successfully.
5016 SHRDMAP:SHM UID This event occurs when an entry Shared Map UID Operation
Not Found is not found in Shared Map Table. Type
5017 Conf/xfer on On Blast Conference, transfer UID Call ID
blast conf or conference is not allowed.
SA8893 is enabled.
5018 SA8893 not SA8893 feature Green Bit is not UID Call ID
enabled enabled.
Table continues…
Denial Events

on the event log
(keyword)
5019 HDE StatLock, Hot Desking Enhancement and UID Call ID
FAC denied On Station-Lock Feature Access
Code is not allowed.
5020 SIP Replace:More SIP replacement is denied as Bch UID of the Party count of
Pty Cnt count of party block in callr2 is full replacing trunk callr2
and there are no more slot left.
Hence the call is dropped.
5021 SIP Replace:No This event occurs since INVITE UID NA
Old Callr with Replaces has failed, since
there is no call record found of the
old call.
5022 SIP Replace:New This event occurs since INVITE UID NA
Orig Fail with Replaces has failed due to
the failure of new call origination.
5023 SIP This error has occurred since Bch UID of the Return code
Replace:Merge INVITE with Replaces has failed replacing trunk for cm_merge
Failed due to the failure of merge call. failure.
5024 SIP Replace:OTRK This error has occurred since UID Return code
Mrg Fail INVITE with Replaces has failed for gm_merge
due to merge failure of old trunk. failure.
5025 SIP Replace:NTRK This Error has occurred since UID Return code
Mrg Fail INVITE with Replaces has failed for gm_merge
due to merge failure of new trunk. failure.
5026 No pub-unk# for The public-unknown-numbering Station UID Current B-
SIPDivHdr form has not been populated. Channel UID
(UID
Cur_buid)
5027 No pub-unk# for The public-unknown-numbering UID of the station The selected
SIPDivHdr screen for the station UID has not B-channel ID
been populated.
5028 No pub-unk# for The public-unknown-numbering Diverting UID Current B-
SIPDivHdr form has not been populated. Channel UID
(UID
Cur_buid)
5029 ACB Activation This event occurs since, the Callr2 Party Principal
Aborted CC Exec Possible was received Block UID termination
before feature timer for ACB UID
timeout (8 sec) expired.
Table continues…
Denial events

on the event log
(keyword)
5030 Telcomtr btn psh No space left in pend_stims array. UID CID
ignored Larger buffer is needed to hold
delayed stims. In this case, size of
pend_stims[] in mem_rec needs
to be increased by incrementing
MAX_PEND_MTM_STIMS value.
5031 CMS VDN admin CMS is not allowed to Vector or policy Index in VDN
not allowed move a VDN or change skill routing table translation
preferences with policy routing number. table.
table administered.
5032 restore port Port restoration failed during Current user UID IP address
failed unmerge. Retry force un- (Cur_user)
registration.
5033 hmm ess active This event occurs due to failure of HMM query fail Server active
qry faild hmm SVR_ACTIVE query. return code status
5034 Invalid MCT Found invalid trunk group type UID Status of
trunk group in "MCT voice recorder trunk SA9089
group" field on system-parameter feature.
features form.
5035 NCR:Xfer/cnf drp The Network Call Redirection response type response
inv fail invocation failed for station
transfer or conference drop.
5036 Call pickup of a Pickup for Call Pickup or TAAS. UID Call ID
VOA Pickup of call listening to a VOA is
not allowed.
5037 IP Endpoint in The event occurs when IP NA NA
bad state endpoint is in bad state. Forcefully
unregister the endpoints.
5038 No agent/skill The event occurs when agent / Index of the first Available
pair avail split pair is not available since free element of agent/split
number of pairs have exhausted. the grp_memb pairs left in
array. the system.
5040 ip version The event occurs when CLAN IP index to the number of
mismatch version does not match the far Su_ip_intf array CLANs in the
end endpoint IP version. containing v4 home
CLANs in this LSP/ESS
NR. region.
5041 RTP IP version The event occurs when IP version Near-end IP Far-end IP
mismatch of near-end RTP address and far- address. address.
end RTP address do not match.
Table continues…
Denial Events

on the event log
(keyword)
5042 CTI App User in 3PCC request is not a UID Call ID
activation only simple UID.
5043 Invoking Station The event occurs when an UID Call ID
not DC Invoking station is not a domain
controlled station.
5044 SIP station Request to change the Third UID Feature ID
feature only Party Call Control (3PCC) state and Call ID
for operating on the SIP device root
is denied since only SIP station
feature requests are accepted.
5045 IP Ept needs The IP endpoint registering to UID Feature ID
expand ASN.1 administered extension needs to
support the expanded ASN.1
5046 TTR err Frcd TTR attachment failed when UID Call ID
agnt lo aux collect digits for the location or
skill for forced agent logout or
aux has been initiated from vector
step.
5047 Max agent/skill Maximum agent/skill pair has UID Call ID
pairs reached. No more addition is
allowed in agent skills feature.
5048 Chained Call Fwd Auto callback on a forwarded call UID Number of
active is not allowed when chained call times call
forward is enabled. forward was
used to route.
5049 TEAM PKUP: Invalid CID is received in INVITE UID Call ID
invalid CID FNU so deny team button
pressing.
5050 Invalid Path Path Replacement attempt is UID Incoming or
Repl attempt invalid. outgoing
ARS/AAR/UD
P
5051 PR fail: Not Inc Path Replacement failed since the UID Trunk UID
ARS/AAR call was made using TAC dialing
instead of AAR/ARS dialing.
5052 PR fail: Path Replacement failed Supplementary Administered
Improper Admin on account of improper Service option in path
administration. current B- replacement
channel user.
Table continues…
Denial events

on the event log
(keyword)
5053 MIS protocol A MIS application violated processor Request full
error protocol by sending an RLTB or channel translation
RFTB without an RTCS. block (0x06)
5054 No conf/xfer For conference factory, a call UID Call ID
ringing pty must be answered before it is
conferenced or transferred into
an existing conference factory
conference.
5055 Multiloc feature Multiple locations feature is turned Callr route block Originating
needed OFF. UID simple UID.
5056 Bad input for The event occurs when location is originating Location.
agent loc incorrect for service observer. simple UID.
5057 End-to-end signaling digit UID Return code
collection of extension failed when GM_ERR (0)
only FAC for activating service
observing is present in vector
step.
5058 Agent loc: No The event occurs when user Originating Location.
Admin attempts to activate service simple UID.
by location but entered a non-
administered location.
5059 CDR Resource The event occurs when CDR UID Call ID
Exhaustion resource has exhausted.
5060 Service observer Service observer is not allowed to UID Call ID
no hold hold, transfer or conference a call.
5061 annexh audit The event occurs when audit NA NA
force unreg for Annex H registration data
sStoredData[] is failed.
5062 Port The error has occurred since UID Port
corrupt,call station has a corrupted port due
service to conflicting data.
5063 Sup Assist Agent does not have tenant UID Call ID
tenant err calling permissions to call
supervisor
Table continues…
Denial Events

on the event log
(keyword)
5064 Qstats tenant Button push failed as agent does Current user UID Button
err not have calling permissions to (Cur_user) appearance
view the skill. structure for
values of call
appearance
or non-call
appearance
type button.
5065 DCC Activated The (MLPP) Destination code UID UID
control feature has been
activated.
5067 DCC De-activated The (MLPP) Destination code UID UID
control feature has been
deactivated.
5068 Restricted by The (MLPP) Destination code UID UID
DCC COS control feature is restricted by the
COS settings for user.
5069 Trk Outgoing Trunk Group Outgoing Budget is UID Trunk group
Budget admin blank or an active call count is UID or Call
of trunk group or
hosed up. The Destination code count
return code of
control does not know what to do
group manager
with the call.
5070 Deny Transfer by Original ad-hoc conference host is UID NCR
Cnf Host not allowed to transfer the call. operation
value.
5071 ASAC: Trunk ASAC and DSN is enabled Group index Call type –
Budget blank but outgoing budget is not Incoming (1)/
administered on trunk form. Outgoing (2)
5072 Atd vec deny grp Attendant group is in night service Current Tenant
in night but night service is blocked due to attendant group number
no active night console.
5073 SIP OPTIM TG Warning: SIP station signaling is UID NA
Meas Error on a measured SIP trunk.
5074 BCMS skill pairs Maxed out miscellaneous app Split number Agent UID
exceeded BCMS agent/skill capacity.
5075 Trk call: Too Received too many hops in UID 0
Many Hops response to an outgoing call.
5076 SIP XFER Request to transfer the call UID Transfer CID
actv;XFER denied denied, because a SIP endpoint
has a transfer in progress.
Table continues…
Denial events

on the event log
(keyword)
5077 SO-Coach-In so- SO Coach-Cannot toggle SO UID 0
coach mod LO/LT modes while coaching is
enabled.
5078 SO-Coach-not Cannot activate Coaching until UID VOA playing
reached agnt call connects to an agent. or Converse
active
5079 SO-Coach-already SO Coach-Another observer is UID 0
active already coaching.
5080 SO-Coach-invalid SO Coach-Cannot coach in SO UID 0
no-talk No Talk mode.
5081 Unsupported CMS CMS release read from PREC 0 0
release is no longer supported and was
blanked out.
5082 Unsupported AAPC AAPC release read from PREC 0 0
release is not longer supported and was
blanked out.
5083 SO-Coach-In SO Coach-Cannot coach UID 1
conference conferences.
5084 SO-Coach-in SO Coach-Cannot coach while in UID 0
wait-state wait state.
5085 SO-Coach-not SO Coach-Cannot coach unless UID 0
serv-obsrvng SO is active.
5086 Invalid user Invalid user to apply ICHT. User len Digit length
5087 Null far end IP Far end rtp ip address is NULL. UID 0
5088 Mismatched RAS Far end sends a short KARRQ UID IP address
port with mismatched RAS port.
5089 No public Station extension not in public or UID CID
private entry private tables.
5090 No call record No call record for object call. UID BCH Orig UID
5091 Reconnection Recon failure due to a trunk UID UID BCH TERM
failure not being found. UID
5092 Reconnection BCH Recon BCH exchange failure. UID CID
failure Drop object recon call.
5093 Call Call reconstruction. Could not Feature cause BCH UID
reconstruction proceed.
in Avaya-cc-
failure
reason BYE or
SIP request
method
Table continues…
Denial Events

on the event log
(keyword)
5094 Call Call reconstruction. BYE without CID
reconstruction proper reason header.
failure
5095 Call Call reconstruction. Single leg CID CID
reconstruction complete.
failure
5096 Call Call reconstruction. Single leg UID CID
reconstruction origination failure.
failure
5097 Call Call reconstruction. Tandem tasks UID CID
reconstruction complete.
failure
5098 Call Call reconstruction. 480 resource CID CID
reconstruction issue.
of call that is to
resource issues
be reconstructed
or UID
5099 Call Call reconstruction. BYE received Status of call CID
reconstruction on reconstruction attempt, likely reconstruction
by attempt from SM, thus call can not be
reconstructed.
Chapter 6: Maintenance Object Repair
Procedures
Communication Manager Maintenance Object Repair

Procedures
This chapter provides information for troubleshooting and repairing maintenance objects.
Note:
This chapter does not contain maintenance objects for the Avaya Wireless Business System
or messaging systems. Refer to the documentation that accompanies these products for this
information.
Each identifiable part in the system is considered a maintenance object (MO). A maintenance
object can be:
• An individual media module
• A hardware component that is part of a media module
• Any software process
• Significant events
• Environmental controls
Each maintenance object has its own unique set of tests, error codes, and recovery strategy.
Maintenance software logs inline errors reported by media modules, runs tests for error diagnosis
and recovery, and raises and clears alarms.
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 when applicable. These
locations display as the port field in the Alarm and Error logs and as output of commands such as
test board.
Maintenance Object Repair Procedures
Figure 1: Display of test board

Communication Manager maintenance objects are displayed using the list configuration
all or show mg list_config command.
list config all on the Communication Manager System Access Terminal (SAT) screen
displays the Board Name (location), Board Type, Code, Vintage, and the assigned ports, if any, of
all installed equipment in the system.
show mg list_config on the MGP displays information for the installed equipment in that
gateway.
Gateway Subsystems
The gateway subsystems are either field replaceable or integrated (part of the system and not
replaceable). These subsystems are not under Communication Manager control and are not
maintained by the system. The following table lists the applicable subsystems and if they are field
replaceable or not.
Table 47: Gateway Subsystems maintained by Communication Manager
Subsystem Field Replaceable

Any Media Module Yes
VOIP Media Module No
Announcement Circuitry (part of the MGP) No
Gateway MOs maintained by Communication Manager

The maintenance strategy for the gateways is intended to provide easy fault isolation procedures
and to restrict problems to field-replaceable components. The following list contains the
MO groupings by Media Module type
maintenance objects which are under Communication Manager control and are maintained by
the system:
• MED-GTWY (MEDIA GATEWAY)
• MG-ANA (Analog Media module)
• MG ANN (Media Gateway Announcement Module)
• MG-BRI (BRI Trunk Media Module)
• MG-DCP (Digital Line Media Module)
• MG-DS1 (DS1 Interface Media Module)
• MG-IAMM (Integrated Analog Media Module)
MO groupings by Media Module type

The following table shows MO groupings by Media Module type.
Table 48: Media Module Types
Media Module (MM) Maintenance Object (MO)

E1/T1 Media Module Board (MG-DS1)
DS1 CO Trunk (CO-DS1)
DS1 DID Trunk (DID-DS1)
DS1 Tie Trunk (TIE-DS1)
DS1 ISDN Trunk (ISDN-TRK)
ISDN-PRI Signaling Link Port (ISDN-PLK)
ISDN-PRI Signaling Group (ISDN-SGRP)
Wideband Access Endpoint Port (WAE-PORT)
Analog Media Module Board (MG-ANA)
Analog Line (AN-LN-PT)
Analog Co Trunk (CO-TRK)
Analog DID Trunk (DID-TRK)
DIOD Trunk (DIOD-TRK)
Alarm Port (ALARM-PT)
DCP Media Module Board (MG-DCP)
Digital Line (DIG-LINE)
BRI Trunk Media Module Board (MG-BRI)
ISDN Trunk Side BRI Port (TBRI-PT)
Table continues…
Media Module (MM) Maintenance Object (MO)

ISDN Trunk Side Signaling (TBRI-TRK)
Integrated Analog Module in V7 (G430 or G450) MG-IAMM
Integrated Analog Module in V3 (G430 or G450)
Commands to view Communication Manager alarms

Communication Manager alarms and events are viewed using commands that are available via
the Web Interface or the SAT command-line interface (CLI).
Table 49: Commands for Viewing Communication Manager Alarms
Command Interface Purpose Description

View Current Alarms Web Interface, View a list of Displays a summary of
under Alarms and outstanding alarms against alarms, if present, followed
Notification Communication Manager by a detailed table of
explanation.
Display alarms SAT CLI View logged These are alarms that have
Communication Manager not yet been cleared, either
alarms manually or via an Expert
System.
Command Syntax
Test command sequences can be either short or long (l). The default is short. The test sequence
can be repeated several times. The default is 1.
The following is an example for testing a port on a media module. It runs the short test sequence:
test port GGGVSpp r 3
• GGG = the gateway number (1 - 250)
• V = the literal letter V, which designates a gateway
• S = the media module number (1 - 9)
• pp = the 2-digit port number (01, 02,...)
• r = repeat
• 3 = the number of times the test sequence should be repeated
Alarm levels
Alarm levels
During normal operations, software or firmware may detect error conditions concerning specific
Maintenance Objects (MOs). The system automatically attempts to fix or circumvent the problem.
The alarms are classified depending on their effect on system operation:
• Major alarms— Failures that cause critical degradation of service. These alarms require
immediate attention.
• Minor alarms— Failures that cause some degradation of service, but do not render a crucial
portion of the system inoperable. A minor alarm typically affects a few trunks or stations or a
single feature. Minor alarms require attention, but the consequences are not immediate.
• Warning alarms— Failures that cause no significant degradation of service or failures in
equipment. These failures are not reported to INADS or the attendant console.
• On-Board — problems originate in the circuitry on the alarmed Media Module.
• Off-Board — problems originate in a process or component that is external to the Media
Module.
Alarms are communicated by entries in the alarm log and the turning on of LEDs located on the
attendant console, on all circuit packs, on the server, on the Ethernet switch if there is one, and,
optionally, on customer-designated voice terminals.
Abort Code 1412

Tests which are not applicable for media modules or gateways abort with Error Code 1412. This
error indicates that the test is not valid for the particular maintenance object and can be ignored.
Escalation Procedure
This document is not intended to solve all problems. If the limits of these procedures have been
reached and the problem is not resolved, the problem should be escalated to a higher level of
technical support.
This escalation should conform to the procedures in the Technical and Administration Plan.
Frequently, a repair procedure recommends repeating a test several times after waiting short
time intervals, for example, at one minute intervals up to five times. If, after these repetitions, no
response to the test has occurred or if the same Abort or Failure continues to occur, escalate the
problem to a higher level of technical support.
ABRI-POR (ASAI ISDN-BRI Port)
MO Name in Log Alarm Level Initial Command to Run Full MO Name

ABRI-POR1 MAJ test port location l ASAI ISDN-BRI port
MIN
WRN
1 Use set options to set the alarm level for ABRI ports. The alarm level can be set
independently for on- and off-board alarms to WARNING, MINOR, or MAJOR for every ABRI
port in the system.
For repair procedures, see BRI-PORT (ISDN-BRI Port).
ADJ-IP (ASAI Adjunct TCP/IP Link)
MO Name in Log Alarm Level Initial Command to Run Full Name of MO

ADJ-IP MAJMIN WRN test port location ASAI Adjunct TCP/IP
Link
The ASAI Adjunct TCP/IP Link is the Adjunct Switch Application Interface (ASAI) proprietary link
which connects to a PROCR.
ADJ-IP error log entries

Table 50: ADJ-IP Error Log Entries
Error Type Aux Associated Test Alarm On/Off Command to resolve the error
Data Level Board
0a 0 Any Any Any test aesvcs link#
2b Any test aesvcs link#
18c busyout port WRN OFF release aesvcs link#
location
257d Any ASAI Link Status MAJ OFF test aesvcs link#
Test (#1365) MIN
WRN1
1025e MAJ OFF test aesvcs link#
MIN
WRN1
Table continues…
ADM-CONN (Administered Connection)
Error Type Aux Associated Test Alarm On/Off Command to resolve the error
Data Level Board
3329f ASAI Link Status MAJ OFF test aesvcs link#
Test (#1365) MIN
WRN1
1 Alarms may be downgraded according to values set on the set options form.
a Error Type 0: Run the ASAI Link Status Test 1365 and follow its recommended procedures.
b Error Type 2: Too many Q931 protocol timeouts in a short time. No action to take.
cError Type 18: The ASAI link has been busied out by command. To release the link, enter
release aesvcs link#.
d Error Type 257: The ASAI TCP/IP link is not in an established state.
e Error Type 1025: TCP Tunnel Connection failure.
f Error Type 3329: ASAI TCP/IP link failure.
ADJ-IP demand test descriptions and error codes

Order of Investigation Short Test Sequence Long Test Sequence D/ND1
ASAI Link Status Test 1365 on X X ND
page 738
1 D=Destructive; ND=Nondestructive
ADM-CONN (Administered Connection)

MO Name in Alarm Initial Command to Run Full Name of MO
Log Level
ADM-CONN MAJ status administered-connection n 1 Administered
Connection
MIN
WRN
1 n is an administered connection number indicated in the PORT field of the Alarm or Error Log.
An administered connection provides an end-to-end connection between two access endpoints
or data modules residing in either the same switch or different switches. When administered, the
connection is automatically established and scheduled to be permanently active.
An error is logged whenever an administered connection fails or cannot be established. A failed
connection generates an error whether or not the connection is subsequently reestablished by fast
retry, re-dial, or auto restoration.
An alarm is logged when an administered connection cannot be established either initially or
after a connection failure. Both the alarm level (none to major) and a failure threshold can be
administered for each administered connection. An alarm is raised when either of the following
occurs:
• The number of consecutive failed attempts to establish a connection reaches the
administered threshold.
• The failure to establish a connection is due to a mistake in administration.
ADM-CONN error log entries

Table 51: Administered Connection Error Log Entries
Error Type Aux Data Associated Test Alarm On/Off Command to

Level Board resolve the error
0, 29 Any None Any OFF None
1, 28a, b Any None Any OFF None
2c Any None Any OFF None
6, 21, 31, 127d Any None Any OFF None
16a Any None Any OFF None
17e Any None Any OFF None
18, 102f Any None Any OFF None
22a,g Any None Any OFF None
34, 42, 44, 58h Any None Any OFF None
38, 41I Any None Any OFF None
43, 81 Any None Any OFF None
54 Any None Any OFF None
65, 66, 69a Any None Any OFF None
82 Any None Any OFF None
91, 95, 96, 97, 98, 99, Any None Any OFF None
100, 111
None of the Administered Connection Error Types have a specific associated test and, except
for errors 17 and 127, are valid only for administered connections established over ISDN-PRI
facilities. Error 127 is valid for administered connections established over non-ISDN facilities or
between two endpoints on the same switch.
Notes:
• a Error Types 1, 16, 22, 50, 52, 65, 66, 69, 88 are typically associated with administration
problems and are not expected to be temporary. The administered connection is not retried
and the failure is alarmed immediately. The alarm threshold specified by the customer is
ignored.
AESV-LNK (AE Services Link)
• b Error Types 1, 28: The address of the destination endpoint is: an unassigned number
(1), has an invalid number format (28) , or is restricted from terminating calls due to Class
of Restriction (Access Denied). 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.
• cError Type 2: 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.
• d Error Types 6, 21, 31, 127: The exact failure cause is unknown or has been mapped
to one of these values. If this is a permanent condition, try reversing the direction of the
Administered Connection (originate the administered connection from the destination switch).
This may yield another failure cause.
• eError Type 17: The destination endpoint is not available. Check the status of the destination
endpoint at the far-end switch. The status for the destination endpoint will not be available
on the switch where this error is logged. At the far end, use status access-endpoint
or status data-module to see whether the endpoint is busy, out-of-service, or otherwise
unavailable.
• f Error Types 18, 102: this switch sent an ISDN message to another switch that either did
not respond (18) or did not respond within the time allowed (102) . This could be due to link
failure, or congestion, or an outage at the other switch.
• g Error Type 22: the address of the destination endpoint has changed. Change the
administered connection accordingly. The destination endpoint will not be administered on
the switch where this error is logged.
• hError Types 34, 42, 44, 58: a resource (for example, a circuit or bearer capability) required
by the administered connection is not currently available.
• i Error Types 38, 41: a network failure (38) or temporary failure (41) has occurred. Error Log
entries for other MOs (for example, DS1-BD) may indicate a local problem.
MO Name in Log Alarm Initial Command to Run Full Name of MO

Level
AESV-LNK MAJ test aesvcs-server Application Enablement
Services (AESVCS) Link
WRN
AESVCS Links provide a connection between Communication Manager and an AESVCS Server
in which data is exchanged. Communication Manager dynamically creates and deletes AESVCS
Links as socket connections to the AESVCS Server are established and torn down. AESVCS
Links that are connected to the same AESVCS Server are grouped into an AESVCS Session.
AESV-LNK error log entries and recommended actions

Table 52: AESV-LNK Error Log Entries
Error Type Aux Associated Alarm On/Off Command to resolve the error
Data Test Level Board
513a WRN Off none
769 b AESVCS Link Log only test aesvcs link link#
Heartbeat Test
(#1624)
1537 c Any Log only
2561 d Log only
Note:
1. a Error Type 513: is displayed when an AESVCS Link is hyperactive. The hyperactivity
might be caused by fluctuations in the engineered traffic load being generated by the
AESVCS Server. Both an AESVCS Session level and Link level alarm are generated
to indicate that a link is overloaded.
Once the problem has been resolved, it might take up to 45 minutes for the alarm to
clear. If the hyperactivity persists, escalate the problem.
2. b Error type 769: is a log only error and is displayed when Communication Manager
does not receive a response from the AESVCS Server to a heartbeat message
that was sent over the AESVCS Link. Failure to receive a response to a heartbeat
message results in the deletion of the AESVCS Link by Communication Manager. Both
an AESVCS Session Level and Link level error are generated against this condition.
Escalate if the error persists.
3. c Error type 1537: is a log only error and displayed when an AESVCS Link is deleted
from an AESVCS Session for reasons other than a heartbeat failure. Both an AESVCS
Session Level and Link level error are generated against this condition. The Aux Data
field contains the reason code.
Aux Data Description
1 The far end closed the socket connection. Check the error logs on the
AEVCS Server for more information.
100 The reset aecvcs-link command was used to close the socket
connection
101 The AESVCS Interface on the IP Services form was disabled.
102 The AESVCS Interface was removed from the IP Services form.
103 The AE Services Server was disabled on the AE Services Administration
page of the IP Services form.
104 The AE Services Server was deleted on the AE Services Administration page
of the IP Services form.
Table continues…

200 The socket connection closed due to an internal error. Escalate if the problem
persists.
201 The socket connection was unexpectedly closed by Communication
Manager. Escalate if the problem persists.
202 Communication Manager detected an error and closed the socket
connection. Escalate if the problem persists.
203 Communication Manager detected an error reading from the socket and
closed the connection. Escalate if the problem persists.
204 Communication Manager failed to write a complete message and closed the
socket connection. Escalate if the problem persists.
205 AE Server established a new connection causing Communication Manager to
close the existing one. Escalate if the problem persists.
206 Communication Manager failed to send a heartbeat request and closed the
socket connection. Escalate if the problem persists.
207 Communication Manager detected a protocol violation and closed the socket
208 Communication Manager detected processing the data from the AESVCS
Server and closed the socket connection. Escalate if the problem persists.
209 Communication Manager could not read data from the socket and closed the
4. d Error Type 2561 is a log only error and is displayed when an AESVCS message is
discarded due to a link buffer overflow. Both an AESVCS Session Level and Link level
error is generated against this condition. Escalate if the problem persists.
AESV-LNK demand test descriptions and error codes

Investigate tests in the order presented. By clearing errors associated with the first test , errors
generated from other tests may also be cleared. Click on the link to see the full description of the
test, error codes, and recommended actions.
Order of Investigation Short Test Long Test D/ND 1
Sequence Sequence
AESVCS Link Heartbeat Test 1624 on page 765 X X ND
AESVCS Session Level Link Status Test 1623 on page 765 X X ND
1. D = Destructive; ND = Nondestructive
AESV-SES (AE Services Session)

Level
AESV-SES MAJ test aesvcs-server Application Enablement
Services Session
WRN
An AESVCS Session is a logical connection between Communication Manager and a single

AESVCS Server, and encompasses all the AESVCS Links that are connected between them.
AESV-SES error log entries and recommended actions

Table 53: AESV-SES Error Log Entries
Error Type Aux Associated Alarm On/Off Command to resolve the

Data Test Level Board error
513 ( a on 1-16 WRN Off none
page 302)
769 ( b on 1-16 AESVCS Link Log only
page 302) Heartbeat Test
(#1624)
1025 ( c on 1-16 MAJ Off test aesvcs-server
page 302)
1537 ( d on 1-16 Log only
page 303)
2561 ( e on 1-16 Log only
page 303)
Note:
1. aError Type 513: occurs when one or more AESVCS Links within a given AESVCS
Session is hyperactive. The hyperactivity might be caused by fluctuations in the
engineered traffic load being generated by the AESVCS Server. Both an AESVCS
Session Level and Link level alarm is generated to indicate that a link is overloaded.
The Aux Data field contains the link ID of the last AESVCS Link to report hyperactivity.
Once the problem has been resolved, it might take up to 45 minutes for the alarm to
clear. Refer to AESV-LNK (AE Services Link) on page 299for more information.
2. bError type 769 is a log only error and is displayed when Communication Manager
detects a heartbeat failure on one or more AESVCS Links within the AESVCS
Session. The Aux Data field contains the link ID of the last AESVCS Link to report a
heartbeat failure. An AESVCS Link level error is also generated against this condition.
Refer to AESV-LNK (AE Services Link) on page 299for more information.
3. cError Type 1025: If there are no AESVCS Links left in an AESVCS session, after
waiting for 10 minutes, the system displays Err Type 1025. This alarm is cleared when
ALARM-PT (Alarm Port)
Communication Manager associates a new AESVCS Link to the session. The Aux
Data field contains the link ID of the last AESVCS Link deleted from the session.
4. d Error type 1537: is a log only error and is displayed when one or more AESVCS
Links, within the AESVCS Session is deleted for reasons other than a heartbeat
failure. The Aux Data field contains the link ID of the last AESVCS Link deleted from
the session. An AESVCS Link level error is also generated against this condition.
Refer to AESV-LNK (AE Services Link) on page 299for more information.
5. e Errortype 2561: is a log only error and is displayed when one or more AESVCS
Links within the AESVCS Session is discarding messages due to a link buffer overflow.
This error represents the sum of all the discarded messages in a given session.
The Aux Data field contains the link id of the last AESVCS Link, within the session,
to discard a message. An AESVCS Link level error is also generated against this
condition. Refer to AESV-LNK (AE Services Link) on page 299for more information.
AESV-SES demand test descriptions and error codes

Investigate tests in the order presented. By clearing errors associated with the first test, errors
Order of Investigation Short Test Long Test D/ND1
Sequence Sequence
AESVCS Link Heartbeat Test 1624 on page 765 X X ND
AESVCS Session Level Link Status Test 1623 on page 765 X X ND
ALARM-PT (Alarm Port)

Level
ALARM-PT MIN test port location l Alarm Port
WRN test port location
The Alarm Port MO 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.
ALM-PT error log entries and recommended actions

Table 54: ALARM-PT Error Log Entries
Error Aux Associated Test Alarm On/Off Command to resolve the error
Type Data Level Board
0 ( a on 0 Any Any Any test port location
page
304)
15 ( b on Any Port Audit and Update
page (#36)
304)
18 0 busyout station WRN OFF release station extension
extension
130 None WRN ON test port location
( c on
page
304)
Note:
1. aError Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
repair procedures.
2. bError Type 15: software audit error that does not indicate any hardware malfunction.
Run the short test sequence and investigate errors.
3. cError Type 130: the media module was removed or has been insane for more than 11
minutes. To clear the error, reseat or replace the media module.
ALM-PT demand test descriptions and error codes

Investigate tests in the order presented. By clearing errors associated with the first test , errors
Sequence Sequence
Port Diagnostic Test 35 on page 570 X X ND
Port Audit And Update Test 36 on page 577 X X ND
AN-LN-PT (Analog Line Port)
AN-LN-PT (Analog Line Port)

AN-LN-PT MIN test port location l Analog Line port
The MM711 Analog Trunk and Line Media Module provides 8 ports. The MM716 provides 24
ports. Each of the ports may be administered in any of several ways, as described in MG-ANA
(Analog Media Module) on page 427. Not all of the tests run on the media modules. These tests
will abort with error code 1412. This error can be ignored.
Note:
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 Tests field of the
change station extension form. Be aware that this action also disables Tests #6, 7, 161,
and 35 on some software releases.
AN-LN-PT error log entries and recommended actions

Table 55: AN-LN-PT Error log entries
01 0 Any Any Any test portlocation
1 2 40960 none
40975
40977
153 Any Port Audit and Update (#36)
184 0 busy station extension WRN ON release station
extension
1305 None WRN ON test port location
2576 40973 None
513 7 Ringing Application Test WRN OFF test port location r 2
(#48)
769 Port Diagnostic Test (#35) MIN ON test port location r 2
WRN 1
1025 Looparound test (#161) MIN ON test port location l r 2
WRN2
1281 Conference Circuit Test (#7) MIN ON test port location l r 2
WRN2
Table continues…
1537 NPE Crosstalk Test (#6) MIN ON test port location l r 2
WRN2
230512 57481 None MIN ON
WRN1
1. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in
set options.
Note:
1. Error type 0: Run the short test sequence first. If every test passes, run the long test
procedures.
2. Error Type 1: These are inline 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 causes an inline error from the board.
• 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.
a. Call the terminal equipment and verify that the terminal rings.
b. If the terminal does not ring, replace it. Otherwise, run test port location,
and follow the procedure for ONS Ringer Application Test 48 on page 582.
• Aux Data 40977 indicates that no terminal equipment was connected when ringing
was attempted. Run test port location, and follow the procedure for the
results of ONS Ringer Application Test 48 on page 582.
3. Error Type 15: The software audit error that does not indicate any hardware
malfunction. Run the short test sequence, and investigate any associated errors.
4. Error Type 130: The circuit pack or media module has been removed or has been
insane for more than 11 minutes. To clear the error, reseat or replace the circuit pack
or media module.
5. Error Type 257: This is an inline error and can only be resolved over time. This error
indicates that ringing voltage is absent.
For media modules: If not resolved over time, replace the media module.
6. Error Type 513: Test #48 can 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 screen to n. In some
software releases, this also disables Tests #6, 7, 161, and 35.
7. Error Type 2305: This is an inline error that occurs when the analog board detects
an abnormal increase in the power supply to a port. The analog board then suspends
power supply to the affected port, and Communication Manager deactivates the station
connected to the port. After the power stabilizes, the analog board resumes power
ASAI-ADJ (ASAI Adjunct)
supply to the port and Communication Manager activates the station connected to the
port.
AN-LN-PT demand test descriptions and error codes

Sequence Sequence
ONS Ringer Application Test 48 on page 582 X X ND
Conference Circuit Test 7 on page 541 X ND
NPE Crosstalk Test 6 on page 532 X ND
ASAI-ADJ (ASAI Adjunct)

The error log entries and recommended actions for ASAI-ADJ (ASAI Adjunct) are the same as the
error log entries and recommended actions for BRI-SET, Various Adjuncts. For more information
about specific ASAI-ADJ (ASAI Adjunct) error type, see the same error type on the BRI-SET/
Adjunct Error Log Entries table in the BRI-SET, Various Adjuncts on page 321section.
ASAI-BD (Multi-Application Platform Board)

ASAI-BD MIN test board location ASAI-BD
WRN
See ASAI-PT (ASAI Port) on page 314and ASAI-EPT (ASAI Endpoint) on page 308for related line
information. See the following exceptions listed below:
• Hyperactivity: Currently, the common circuit pack is considered “hyperactive” if the circuit
pack sends 200 uplink messages in a 10-second period. An alarm is issued when the limit
reaches 400. When the limit reaches 500 uplink messages in 10 seconds, the board is taken
out of service.
• Port Administration: In Administration Without Hardware (AWOH), the switch allows

administration of up to 8 ports in any of the first 12 ports. If the port type later reported
by the board does not match the existing type, the switch assumes it to be a MAPD board
with a different configuration and rejects the board.
ASAI-EPT (ASAI Endpoint)

ASAI-EPT MAJ 2 test station extension ASAI-Adjunct
2The alarm level for ASAI adjuncts is administered using set options. The alarm level can be
set independently for on- and off-board alarms to WARNING, MINOR, or MAJOR for every ASAI
adjunct in the system.
The TN800 is a PC-based platform that allows interaction of multiple applications with
Communication Manager at any time. Communication Manager (native mode) supports emulation
of three types of port MOs on this board. The type of ports to be emulated is defined by the
applications running on the TN800.
Note:
If the TN800 is emulating BRI, the software/firmware supports up to 12 ports, but only 8 of the
12 ports can be administered at any one time.
ASAI-EPT error log entries and recommended actions

Table 56: ASAI-EPT Error Log Entries
Error Aux Associated Test Alarm On/ Off Command to resolve the error
ASAI-EPT
0 0 Any Any Any test ASAI-ADJ
2 2-102 None
257 Any BRI Layer 3 query MAJ WRN OFF test stationextr 2test data-
3
moduleextr 2
351 0 none WRN OFF busyout and release station
513 0 None
769 0 None MAJ OFF
2562- 0 None
2566
2567 0 None
Table continues…
Error Aux Associated Test Alarm On/ Off Command to resolve the error
ASAI-EPT
2568 0 None
3329 Any Signaling Link status (#626) MAJ OFF
WRN3
3584- Any None
3839
3841 Any None
4095
3Major alarms on this MO may be downgraded to Warning alarms based on the value used in set
options.
Note:
1. Error Type 0: Run the short test sequence first. If every test passes, run the long test
procedures.
2. Error Type 2: ISDN-BRI signaling protocol violation. Timers associated with layer-3
messages expired before a required response was received. In the following table, the
aux data column indicates which timer has just expired.
Aux Data Timer Type
2 First T303 (SETUP timer)
3 Second T303 (SETUP timer)
4 T305 (DISConnect timer)
5 First T308 (RELease timer)
6 Second T308 (RELease timer)
10 T316 (RESTart timer)
12 T309 (Layer-2 Failure timer)
16 TM100 (Management Information message Timer 1)
102 TASAI (ASAI Routing Timer)
The switch sent a message to an endpoint that did not respond in the time allowed.
This may be due to failure of the point-to-point signaling link or because of a problem
in the ASAI adjunct. To repair, enter test station extension and perform the
associated repair procedures for those tests.
3. Error Type 257: An endpoint is not responding to the service state query message sent
to the adjunct or to 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 to the adjunct.
When this error occurs for an ASAI adjunct, the Aux Data field indicates the state of
the ASAI link and whether an invalid response or no response was received to the
query from the switch, as shown in the following table:
Aux Data ASAI Link State Error
102 13-restarting No response to RESTART message
104 13-restarting Invalid response to RESTART message
152 13-restarted No response to layer-3 query
154 13-restarted Invalid response to layer-3 query
202 13-established No response to layer-3 query
204 13-established Invalid response to layer-3 query
See the section on maintenance SAT commands in Maintenance Commands

for Avaya Aura® Communication Manager, Branch Gateways and Servers for an
explanation of the ASAI link states.
For ASAI or Avaya adjuncts, the switch queries the adjunct every two minutes. The
Layer 3 Query test is not executed for ASAI or Avaya adjuncts through a command
entered from the management terminal. While alarmed for this error, the switch takes
the associated port out-of-service for five seconds every 15 minutes. This action
attempts to stimulate recovery actions to be taken by the adjunct.
When this error occurs for an ASAI or Avaya adjunct, the service technician should:
a. Execute test station extension and perform the associated repair
procedures.
b. 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.
4. Error Type 351: logged against an ASAI endpoint when the adjunct asks the switch
to suspend maintenance on the ASAI endpoint. Clear with busyout and release of the
ASAI station.
5. Error Type 513: the endpoint sent more messages than the switch could 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.
6. Error Type 769: an ASAI endpoint’s associated signaling link has too much traffic
related to link establishment. This occurs when the signaling link is alternating between
assigned and established states. If this problem persists, replace the endpoint.
7. Error Type 2562 - 2566: 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 signaling link or the ASAI adjunct. Follow the repair procedures issued
by the manufacturer of the adjunct. If these attempts fail, re-engineering of the traffic
on the signaling link or adjunct may be necessary.
8. Error Type 2567: This version of ASAI is not supported. Check the software version
that is running on the ASAI adjunct.
9. Error Type 2568: The adjunct identification is invalid. Check the vendor ID or software
running on the ASAI adjunct.
10. Error Type 3329: the point-to-point signaling link to the endpoint went down, except
when the link goes down because either a system technician has busied out the
PKT-BUS, or it has failed. This error raises an alarm against the endpoint or adjunct.
Execute test station extension short and note the results of the Signaling Link
Status Test (#626). If this test fails, follow the repair procedure for Signaling Link Status
Test 626. The alarm is retired when the signaling link is re-established to the endpoint
or adjunct.
11. Error Type 3584 - 3839: The switch software logs certain ASAI cause values. The
cause value is determined from the following formulas:
• If the Error Type is greater than 3712, the ASAI cause value is equal to the Error
Type minus 3712. The switch sent this value to the adjunct.
• If the Error Type is less than 3712, the ASAI cause value is equal to the Error Type
minus 3584. The adjunct sent this value to the switch.
The table on page 311 contains a description of the various ASAI cause values and
recommended system technician actions associated with the cause value.
12. Error Type 3841 - 4095: The switch software logs certain ASAI cause values. The
cause value is determined from the following formula:
• If the Error Type is greater than 3968, the ASAI cause value is equal to the Error
Type minus 3968. The switch sent this value to the endpoint.
• If the Error Type is less than 3968, the ASAI cause code is equal to the Error Type
minus 3840. The endpoint sent this value to the switch.
Table 57: ASAI cause values
Code Explanation Recommendation

0 Unrecognized Requested ASAI protocol is not implemented by switch or adjunct.
ASAI Protocol Aux Datafield of error log entry contains protocol identifier for
Operation. unrecognized operation.
a. Consult switch and adjunct documentation to determine which
set of operations is supported by switch and the adjunct.
Turning off adjunct operations not implemented by the switch
may resolve the problem.
Table continues…

34 No circuit or A resource on the switch is unavailable for a call. For BRI
channel endpoints, this cause value is not logged. For ASAI, this condition
available means that there are no available trunks for an outgoing call
request.
a. Verify that the adjunct is administered to support the trunk
capabilities of the switch.
b. Investigate trunk-group status by entering status trunk
from the SAT or by requesting trunk-group queries from the
adjunct.
c. Perform trunk diagnostic procedures such as test trunk.
40 Resources No available internal resources to service switch or adjunct
not available. request. Exceeds system transaction capacity for adjunct or
switch.
a. May require re-engineering of adjunct services.
50 Requested Requested facility is implemented, but not administered. Potential
facility not administration problem with endpoint or adjunct.
subscribed
For BRI endpoints:
a. Verify the switch administration of endpoint using display
station or display data-module.
b. If step 1 does not resolve the problem, refer to the endpoint’s
service manual and verify administration on the endpoint.
For ASAI adjuncts:
a. Display the Customer Optional Features screen
(administration screen) on the switch to determine which ASAI
capabilities are turned on in the switch.
b. Verify that the adjunct is administered to support the identical
capabilities as the switch. If there is a mismatch in the
administered capabilities, then re-administer the switch and/or
the adjunct to establish a consistent set of desired capabilities
on both the switch and the adjunct.
58 Bearer Requested bearer capability is implemented, but not administered.
capability not No B-Channel is administered. See code 50 above.
currently
available
Table continues…

63 Service or Requested ASAI capability or resource is not available on the
option not switch or adjunct. More than one adjunct may be contending
available for the same switch resource. Potential administration mismatch
between the resource domains administered on the switch and
those administered on the adjunct.
a. Verify that no overlapping administration of switch resources
(for example, requesting notifications on a single domain by
multiple adjuncts attempting to control a single call) exists
across any adjunct connected to the switch. If an overlap
exists, then re-administer the adjuncts to ensure that each
adjunct is associated with a unique set of switch resources.
65 Bearer Requested service not implemented in switch or endpoint.
service not
implemented
69 Requested Requested service not supported in switch or endpoint.
facility not
a. Consult switch and endpoint documentation to determine
implemented
service support.
79 Service or Requested service or option (or combination of selected options)
option not is not supported (implemented) in switch or the adjunct.
implemented
a. Consult switch and adjunct documentation to determine ASAI
service and options supported by both switch and adjunct.
Re-administration of the switch-administered capabilities (see
Customer Optional Feature screen) or those of the adjunct
may be necessary to correct the problem.
81 Invalid CRV An invalid CRV was sent by the adjunct.
a. This may indicate a CRV inconsistency between the switch
and the adjunct. See the CallVisor protocol reference manual.
87 Internal There is an inconsistency in switch data records.
switch audit
a. There is no action needed, since the switch has corrected the
data inconsistency.
ASAI-EPT demand test descriptions and error codes
Order of Investigation Short Test Long Test D/ND

Sequence Sequence
Signaling Link Status Test 626 on page 658 X X Nondestructive
ASAI-PT (ASAI Port)
MO name in log Alarm level Initial command to run Full name of MO

ASAI-PT MAJ 4,,5 test port location l ASAI ISDN BRI port
WRN
4The alarm level for ASAI adjunct ports may be administered using set options. The alarm
level can be set independently for on-board alarms and off-board alarms to WARNING, MINOR, or
MAJOR for every ASAI adjunct port in the system.
5All alarming for an ASAI adjunct and off-board alarming for an ASAI port is disabled if the ASAI
adjunct asks the switch to suspend maintenance. When this occurs, an error and a WARNING
alarm is logged against the ASAI adjunct. Check the Hardware Error and Alarm Logs to determine
if the adjunct has disabled alarming.
Unless otherwise stated, every maintenance action contained in this section applies to ASAI-PT
and ISDN-BRI ports connected to ASAI adjuncts.
ASAI-PT error log entries and recommended actions

Table 58: ASAI-PT error log entries
Error Aux Associated test Alarm level On/Off Command to resolve the error
type data board
0 0 Any Any Any test port location
1 (a) Level 1 status MAJ 1 OFF test port location r 2
inquiry (#621)
513 0 none MAJ ON
1537 46210 CRC error MAJ 1 OFF
counter (#623)
3841 46208 None
3844 46223 None
3845 46211 None
3846 TEI None
1Major and Minor alarms may be downgraded to warning alarms based on the value used in set
options.
Note:
1. Error type 0: Run the short test sequence first. If every test passes, run the long
test sequence. See each appropriate test’s description, and follow its recommended
procedures.
2. Error type 1: Level 1 Status inquiry failed or the BRI circuit pack detected that Level 1
was deactivated on the port. The Aux Data field contains one of the following values:
ASAI-PT (ASAI Port)
Blank The Level 1 status inquiry failed.

32773 The ASAI-line circuit pack detected Level 1 was deactivated.
See the repair procedures for Level 1 Status Inquiry Test 621. If the alarm does not
clear, verify the status of the personal computer/server. This could be a customer
network issue and not a board problem.
3. Error type 513: The circuit pack is having problems transmitting data to the packet
bus. This error occurs when the packet bus transmit FIFO buffer overflows and most
likely indicates a hardware problem. Use troubleshooting procedures for both on-board
hardware problems and potential off-board packet bus problems.
4. Error type 1537: The port received an invalid frame over the D-Channel. This error is
most likely because of a problem with the wiring to the set or adjunct, interference on
the wiring because of 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.
5. Error type 3841: A Layer 1 Transmission error is detected for the port. Run the long
test sequence, and note the results of the Layer 1 Transmission Error Counter Test
624.
6. Error type 3844: The circuit pack detects an overflow of its receive buffers. Run the
long test sequence, and note the results of the Receive FIFO Error Counter Test 625.
7. Error type 3845: The BRI Port Local LAN Looparound Test 618 fails. Run the long test
sequence, and note the results of Test #618.
8. Error type 3846: The Terminal Endpoint Identifier (TEI) administered for the ASAI
endpoint most likely does not match the TEI administered in the ASAI adjunct. Check
the switch administration of the TEI against that of the adjunct, and ensure that both
are using the same TEI.
ASAI-PT demand test descriptions and error codes

generated from other tests might also be cleared. Click the link to see the full description of the
Order of investigation Short test Long test D/ND
sequence sequence
Level 1 Status Inquiry Test 621 on page 647 X X ND
CRC Error Counter Test 623 on page 653 X ND
Layer 1 Transmission Error Counter Test 624 on page 655 X ND
Receive FIFO Error Counter Test 625 on page 656 X ND
BRI-DAT (ISDN-BRI Data Module)
MO name in Alarm level Initial command to run Full name of MO

log
BRI-DAT WRN 2 test data-module extension ISDN-BRI Stand-alone
Data Module
2
See BRI-SET, Various Adjuncts on page 321.
BRI-PORT (ISDN-BRI Port)
MO name in Alarm Initial command to run Full name of MO

log level
BRI-PORT MIN test port location l ISDN-BRI port
WRN test port location l
3
ABRI-POR MAJ test port location l ASAI ISDN-BRI port
3
WRN
3
ATT-PORT MAJ test port location l Avaya Adjunct ISDN-BRI port
3
WRN
3
LGATE-PT MAJ test port location l Ethernet ASAI port
3
WRN
3
ATTE-PT MAJ test port location l Ethernet Avaya Adjunct port
3
WRN
3
Note:
The section, Isolating and repairing packet-bus faults, in Maintenance Procedures for
Avaya Aura® Communication Manager, Branch Gateways and Servers, along with the other
information presented in the chapter, can help resolve problems involving more than one
station.
2 The alarm level for ASAI or Avaya adjuncts may be administered using set options. The alarm level can be set
independently for on- and off-board alarms to WARNING, MINOR, or MAJOR for every ASAI adjunct in the system.
3 Major alarms may be downgraded to Warning alarms based on the value used in set options.
Warning:
If a significant packet bus failure occurs, errors and alarms may not be logged as expected
for BRI-PORT/ABRI-POR/ATT-PORT/ LGATE-PT/ ATTE-PT. Conditions under which this
occurs are detailed in the Isolating and repairing packet-bus faults section in Maintenance
Procedures for Avaya Aura® Communication Manager, Branch Gateways and Servers.
The following media module support this maintenance object:
• MM720 BRI Media Module
The MM720 BRI Media Module provides 8 S/T ISDN 2B+D ports that interface to either the central
office or another PBX. The MM720 contains eight, 4-wire ports that interface to the network at
the ISDN S/T reference point over two 64Kb channels and over a 16Kb signaling channel. The
64Kb channels are B1 and B2, and the 16Kb channel is D. The B1 and B2 channels can be
simultaneously circuit switched, or individually packet switched. The D-channel is circuit switched.
The circuit-switched connections have a Mu-law or A-law option for voice and operate as 64Kb
clear data channels.
Note:
This maintenance object applies to the MM720 BRI Media Module only if its ports are all
configured as station line ports instead of trunk ports.
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
Avaya adjuncts. The D-Channel is used for conveying signaling between the switch and a BRI
endpoint or endpoints, ASAI or Avaya adjunct. Each ISDN-BRI D-Channel is connected to the
switch processor and the ISDN-BRI port through the packet bus.
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 BRI endpoint
BRI-SET, or ASAI adjunct ASAI-ADJ/LGATE-ADJ/LGATE-AJ or Avaya adjunct ATT-ADJ/ATTE-
AJ. These interactions should be kept in mind when investigating the cause of ISDN-BRI port
problems. For more information, see:
• BRI-SET, Various Adjuncts on page 321
and for more information about its endpoints, see:
• ASAI-ADJ (ASAI Adjunct) on page 307
• LGATE-AJ (Ethernet ASAI Endpoint) on page 416
BRI-PORT error log entries and recommended actions

Table 59: BRI-PORT Error Log Entries
Error Aux Associated test Alarm Alarm level On/Off Command to resolve the
type data level for for ABRI- board error
BRI-PORT PORTATT-
PORT
LGATE-PT
ATTE-PT
0 0 Any Any Any Any test port location
1 Level 1 Status WRN Any 1 OFF test port location r
Inquiry (#621) 2
18 busyout port WRN OFF release port location
location
130 WRN ON test port location
257 EPF Inquiry WRN Any 1 OFF test port location
(#622)
513 46222 (d) (d) ON
769 0 WRN MAJ OFF
1281 BRI NPE MIN ON test port location l
Crosstalk (#617) 1 r 2
WRN
1537 46210 CRC Error WRN Any1 OFF
Counter (#623)
1793 BRI Port Local MIN ON test port location l
TDM Looparound r 2
WRN1
(#619)
3841 46208
3842 0
3843 0
3844 46223
3845
3846 TEI
3847 0
1. Major and Minor alarms on this MO may be downgraded to Warning alarms based on the value
used in set options.
Notes:
procedures.
2. Error type 1: The Level 1 Status Inquiry fails or when the BRI detects that Level 1 has been
deactivated on the port. Refer to the repair procedures for Level 1 Status Inquiry Test 621.
Aux data blank: The Level 1 Status Inquiry failed. Aux data 32773: the BRI-LINE media
module detected that Level 1 has been deactivated.
3. Error type 130: The media module has been removed or has been insane for more than 11
minutes. To clear the error, replace or reinsert the media module.
4. Error type 257: The EPF Status Inquiry fails due to an overcurrent condition or when the
BRI-LINE media module 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 media module has detected an overcurrent
condition and has turned the EPF off.
Execute the short test sequence, and see the repair procedures for Test #622.
5. Error type 513: The media module 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 MINOR/WARNING, and the ABRI-PORT/ATT-PORT/LGATE-PT/
ATTE-PT Alarm Level is MAJOR/MINOR/WARNING. 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 Isolating and repairing packet-bus faults in Maintenance Procedures for
Avaya Aura® Communication Manager, Branch Gateways and Serversfor more information
about troubleshooting the packet bus. 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.
6. Error type 769: The BRI NPE Crosstalk Test 617 fails. Run the long test sequence, and
note the results of Test #617.
7. Error type 1281: A port’s associated broadcast-signaling links have too much traffic
related to link establishment. 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. The 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.
8. Error type 1537: 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 that is 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, or escalate the problem.
9. Error type 1793: The BRI Port Local TDM Looparound Test 619 fails. Run the long test
There are no recommended actions for the following Error Types. The Error Types are
simply provided as additional data that may prove useful while troubleshooting.
10. Error type 3841: A Layer 1 Transmission error is detected for the port. Run the long test
sequence, and note the results of the Layer 1 Transmission Error Counter Test 624.
11. Error type 3842: 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.
12. Error type 3843: 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.
13. Error type 3844: The circuit pack detects an overflow of its receive buffers. Run the long
test sequence, and note the results of the Receive FIFO Error Counter Test 625.
14. Error type 3845: The BRI Port Local LAN Looparound Test 618 fails. Run the long test
15. Error type 3846: Most likely occurs when the Terminal Endpoint Identifier (TEI)
administered for the ASAI or Avaya endpoint does not match the TEI administered in
the ASAI or Avaya adjunct. Check the switch administration of the TEI against that of the
adjunct and make sure that both are using the same TEI.
16. Error type 384: Sets on the port do not support layer-3 initialization. Consult the Service
Set documentation.
BRI-PORT demand test descriptions and error codes

sequence sequence
BRI Port Local TDM Looparound Test 619 on page 642 X D
Electronic Power Feed Restoral Test 620 on page 646 X X ND
Level 1 Status Inquiry Test 621 on page 647 X X ND
Electronic Power Feed Inquiry Test 622 on page 651 X X ND
CRC Error Counter Test 623 on page 653 X ND
Layer 1 Transmission Error Counter Test 624 on page 655 X ND
Receive FIFO Error Counter Test 625 on page 656 X ND
BRI-SET, Various Adjuncts
MO name in log Alarm Initial command to run Full name of MO

level
BRI-SET WRN 4 test station extension l ISDN-BRI Set
4
BRI-DAT WRN test data-module extension l ISDN-BRI Data Module
4
ASAI-ADJ MAJ test station extension ASAI-Adjunct
test data-module extension
WRN 5 test data-module extension
4
ATT-ADJ MAJ test station extension Avaya-Adjunct
5
WRN
4
LGATE-AJ MAJ test station extension Ethernet ASAI-Adjunct
5
WRN
4
ATTE-AJ MAJ test station extension Ethernet Avaya-Adjunct
5
WRN
45
Warning:
Information for isolating and resolving packet bus faults is included in Isolating and repairing
packet-bus faults section in Maintenance Procedures for Avaya Aura® Communication
Manager, Branch Gateways and Servers. The Troubleshooting Packet Bus Problems
flowchart, along with the other information presented in the chapter, can help resolve
problems that involve more than a single station.
Warning:
If a significant packet bus failure occurs, errors and alarms may not be logged as expected for
BRI-PORT/ABRI-POR/ATT-PORT/ LGATE-PT/ ATTE-PT. Conditions under which this occurs
are detailed in the Isolating and repairing packet-bus faults in Maintenance Procedures for
Avaya Aura® Communication Manager, Branch Gateways and Servers.
ISDN-BRI endpoints come in a number of configurations. Every endpoint requires 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 of them is for voice and the other one
is for data. Only a single ASAI or Avaya adjunct may be connected to an ISDN-BRI port. Multiple
adjuncts per line are not supported.
4 The alarm level for ASAI and Avaya adjuncts may be administered using set options. The alarm level can be set
independently for on- and off-board alarms to WARNING, MINOR, or MAJOR for every ASAI and Avaya adjunct in the
system.
5 Alarming for an ASAI and Avaya 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
ADDLE station will clear the alarm.
The figure on page 322 illustrates the physical connection between an ISDN-BRI media module
and a voice or voice/data set. The connection is represented by a solid line. Each physical
connection allows for two B-Channels, as stated above, plus one D-Channel.
Figure 2: ISDN-BRI Set Interactions
This section contains the ISDN-BRI Set, ASAI Adjunct and Avaya Adjunct Maintenance
documentation. Some of the results of maintenance testing of the ISDN-BRI Set or the ASAI
and Avaya Adjunct may be affected by the health of the ISDN-BRI media module and port. These
interactions should be kept in mind when investigating the cause of ISDN-BRI Set problems.
BRI-SET error log entries and recommended actions

Table 60: BRI-SET/Adjunct Error Log Entries
Error type Aux Associated Alarm Alarm On/ Off Command to resolve the
data test level level board error
BRI- ASAI-
SET ADJ ATT-
BRI- ADJ
DAT ATTE-AJ
LGATE-
AJ
0 0 Any Any Any Any test station ext r 2
test data-module ext r
2
2 2-10
2
18 0 busyout WRN MAJWRN OFF release station ext
station ext 1
Table continues…
Error type Aux Associated Alarm Alarm On/ Off Command to resolve the
data test level level board error
BRI- ASAI-
SET ADJ ATT-
BRI- ADJ
DAT ATTE-AJ
LGATE-
AJ
257 Any BRI Layer 3 WRN MAJ OFF test station ext r 2
Query (#629) 1
WRN test data-module ext r
2
351 0 WRN OFF busyout station and
release station
513 0
769 0 WRN MAJ OFF
2562-2566 0
2567 0
2568 0
2817 0 XID test (#628) WRN MAJ OFF test station ext r 2
WRN 1 test data-module ext r 2
3073 0 BRI Remote WRN OFF test station ext l r 2
Loopback
test data-module ext l r 2
(#627)
3329 Any Signaling Link WRN MAJ OFF
Status (#626)
WRN 1
3584- 0
3839
3840-4095 0
1. Major and Minor alarms for this MO may be downgraded to Warning alarms based on the value
used with set options.
Notes:
procedures.
2. Error type 2: Violations of the ISDN-BRI signaling protocol. Timers associated with certain
layer-3 messages have expired before a required response was received. In the following
table, the aux data field indicates what timer has just expired.
Aux Data Timer Type

2 First T303 (SETUP timer)
3 Second T303 (SETUP timer)
4 T305 (DISConnect timer)
5 First T308 (RELease timer)
6 Second T308 (RELease timer)
10 T316 (RESTart timer)
12 T309 (Layer-2 Failure timer)
102 TASAI (ASAI Routing timer)
The switch sent a message to the endpoint that 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 Avaya adjunct. Execute test station
extension sh and note the results of the BRI Layer 3 Query test (#629). If this test fails,
follow the repair procedure for BRI Layer 3 Query Test 629.
minutes. To clear the error, replace or reinsert the media module.
4. Error type 257: 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
test station extension sh and note the results of the BRI Layer 3 Query test
(#629). If this test fails, follow the repair procedure for BRI Layer 3 Query Test 629.
When this error occurs for an ASAI or Avaya adjunct, the Aux Data field indicates the
state of the ASAI link or Avaya link and whether an invalid response or no response was
received to the query from the switch, as shown in the following table:
Aux Data ASAI Link State Error
102 13-restarting No response to RESTART message
104 13-restarting Invalid response to RESTART message
152 13-restarted No response to layer-3 query
154 13-restarted Invalid response to layer-3 query
202 13-established No response to layer-3 query
204 13-established Invalid response to layer-3 query
See the section on maintenance SAT commands in Maintenance Commands for Avaya
Aura® Communication Manager, Branch Gateways and Serversfor an explanation of the
ASAI link states.
For ASAI or Avaya adjuncts, the switch automatically queries the adjunct every two
minutes and therefore the Layer 3 Query test is not executed for ASAI or Avaya adjuncts
via a command entered from the G3MT terminal. While alarmed for this error, the switch
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 Avaya adjunct:
a. Execute test station extension and note tests that fail. Perform the associated
repair procedures for those tests.
b. 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.
c. If the above steps do not resolve the problem and the alarm persists, follow normal
escalation procedures.
5. Error type 351 and associated WARNING alarm are logged against an ASAI or Avaya
endpoint when the adjunct has asked the switch to suspend Maintenance on the ASAI
or Avaya endpoint. Busy out and release the ASAI station or ADJLK station to clear the
alarm.
6. Error Type 513: 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.
7. Error Type 769: A BRI endpoint’s signaling-associated link has too much traffic related to
link establishment. This could occur if the signaling link is bouncing between assigned and
established states. Software suspends 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 Avaya adjunct. If this problem persists, replace the endpoint. If
replacing the endpoint does not fix the problem, follow normal escalation procedures.
8. Error Type 2562-2566: 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
signaling link, or the ASAI or Avaya 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 signaling link, or
adjunct may be necessary.
9. Error 2567: The version of ASAI is not supported, check version of the software running on
the ASAI or Avaya adjunct.
Table 61: ISDN-BRI CAUSE VALUES; (BRI-SET/ASAI-ADJ Error Log Notes)
Error Test Result Description / Recommendation

Code
1 Channel in use Another station is using requested channel on the BRI-PORT. Not
applicable for ASAI or Avaya adjuncts.
For BRI endpoints:
a. Try to originate a call to or from this port.
b. If the error persists, busyout and release the port.
c. If the problem still persists, replace stations on the port.
d. If the problem still persists, escalate to the next tier.
34 No circuit or A resource on the switch is unavailable for a call. For BRI endpoints:
channel This cause value is not logged. For ASAI or Avaya Adjuncts: This
available condition means that there are no available trunks for an outgoing call
request.
a. Verify that the adjunct is administered to support the trunk
capabilities of the switch.
b. Investigate trunk group status by entering status trunk
commands from the SAT or by requesting a trunk group query
or queries from the adjunct.
c. Perform trunk diagnostic procedures such as test trunk.
d. If step 3 does not resolve the problem, escalate to the next tier.
42 Switch Switch takes control to limit received traffic. For BRI endpoints: This
Equipment cause value is not logged. For ASAI or Avaya Adjuncts:
Congestion
a. Refer to the CallVisor protocol reference manual.
b. If step 1 does not resolve the problem, escalate to the next tier.
Table continues…

Code
50 Requested Requested facility is implemented, but not administered. Potential
Facility Not administration problem with endpoint or adjunct. For BRI endpoints:
Subscribed
a. Verify the switch administration of endpoint using display
station or display data-module.
b. If step 1 does not resolve the problem, refer to the endpoint’s
service manual and verify administration on the endpoint.
c. If step 2 does not resolve the problem, escalate to the next tier.
For ASAI adjuncts:
a. Display the Customer Optional Features screen also known as
administration screen on the switch to determine which ASAI
capabilities are turned on in the switch.
b. Verify that the adjunct is administered to support the identical
capabilities as the switch. If there is a mismatch in the
administered capabilities, then re-administer the switch and/or the
adjunct to establish a consistent set of desired capabilities on both
the switch and the adjunct.
c. If step 2 does not resolve the problem, escalate to the next tier.
For Avaya adjuncts:
a. Display the Customer Optional Features screen also known as
administration screen on the switch to determine whether the
Avaya adjunct is set enabled on in the switch.
b. If Error Type 2567 or 2568, verify the Avaya adjunct version, and
re-administer if needed.
c. If step 2 does not fix the problem, escalate to the next tier of
support
58 Bearer Requested bearer capability is implemented, but not administered. No
Capability Not B-Channel is administered. See recommendation for Error Code 50
Currently above.
Available
65 Bearer Service Requested service not implemented in switch or endpoint.
Not
Implemented
69 Requested Requested service not supported in switch or endpoint.
Facility Not
a. Consult switch and endpoint documentation to determine service
Implemented
support.
Table continues…

Code
81 Invalid CRV An invalid CRV was sent by the adjunct.
a. This may indicate a CRV inconsistency between the switch and
the adjunct. Refer to the CallVisor protocol reference manual.
10. Error type 2568: The adjunct ID is invalid, check the vender ID or software running on the
Avaya adjunct
11. Error type 2817: There is a layer-2 problem over the D-Channel between the switch and
the endpoint. When this error occurs, an alarm is raised against the station or adjunct.
Execute test station extension short and note the results of the BRI XID test
(#628). If this test fails, follow the repair procedure for BRI XID Test 628.
12. Error type 3073: There is 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 test station extension long and note the results of the BRI Remote
Loopback Test (#627). If this test fails, follow the repair procedure for BRI Remote
Loopback Test 627.
13. Error type 3329: Occurs whenever the point-to-point signaling link to the endpoint goes
down except when it goes down because either 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 test station extension short and note the results
of the Signaling Link Status test (#626). If this test fails, follow the repair procedure for
Signaling Link Status Test 626. The alarm is retired when the signaling link is reestablished
to the endpoint or adjunct.
14. Error type 3584-3839: 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 on page 329. This
table also contains recommended actions associated with the cause value. In addition, the
Aux Data field of the Error Log entry contains additional diagnostic information additional
diagnostic.
Table 62: ASAI CAUSE VALUES; (BRI-SET/ASAI-ADJ Error Log Entries Notes)

Code
0 Unrecognized Requested ASAI protocol operation is not implemented by the switch
ASAI Protocol or adjunct. Aux Data field of Error Log entry contains protocol
Operation identifier for unrecognized operation.
a. 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 No available internal resources to service switch or adjunct request.
available System transaction capacity for adjunct or switch is exceeded.
a. Re-engineering of adjunct services my be required. If problem
persists, escalate problem to the next tier.
63 SERVICE OR Requested ASAI capability or resource is not available on the switch
OPTION NOT or adjunct. More than one adjunct may be contending for the same
AVAILABLE switch resources. Potential administration mismatch between the
resource domains administered on the switch and those administered
on the adjunct.
a. Verify that no overlapping administration of switch resources
exists across any adjunct connected to the switch. For example,
requesting notifications on a single domain by multiple adjuncts
or multiple adjuncts attempting to control a single call. If an
overlap exists, then re-administer the adjuncts to guarantee that
each adjunct is associated with a unique set of switch resources.
79 SERVICE Requested service or option or combination of selected options is not
OROPTION NOT supported or implemented in switch or the adjunct.
IMPLEMENTED
a. Consult switch and adjunct documentation to determine ASAI
service and options supported by both switch and adjunct. Re-
administration of the switch-administered capabilities, for more
information see Customer Optional Feature screen or those of
the adjunct may be necessary to correct the problem.
b. If step 1 does not provide the set of desired services due to
deficient implementation, escalate the problem to the next tier.
87 Internal switch There is an inconsistency in switch data records.
audit
a. There is no action needed since the switch has corrected the
data inconsistency.
b. If a number of these errors continue to occur, then escalate to
next tier.
15. Error type 3840-4095: 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.
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 the table on
page 326. This table also contains recommended actions associated with the cause
value. In addition, the Aux Data field of the Error Log entry contains additional diagnostic
information.
16. Error 3847: Sets on the port do not support level 3 initialization. Consult the set service
documentation.
BRI-SET demand test descriptions and error codes

Order of Investigation Short Test Long Test D/ND
Sequence Sequence
Signaling Link Status Test 626 on page 658 X X ND
BRI XID Test 628 on page 665 X X ND
BRI Layer 3 Query Test 629 on page 669 X (a) X (a) ND
BRI Remote Loopback Test 627 on page 660 X (a) ND
BRI Set Audits Test 630 on page 673 X (a) X (a) ND
Note:
1. Execute test port long location, and review the results of the BRI Port Local LAN
Looparound Test 630 to verify the repair.
SPID Facility Test

This test verifies 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 Avaya 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 mer, the test set establishes a signaling link connection with
the switch and attempts to complete Service Profile IDentifier (SPID) initialization by using the
Service SPID administered for the system, for more information see the System Maintenance
Administration screen. If the test set displays the correct administered port address for the
BRI-SET demand test descriptions and error codes
endpoint or adjunct under test, the test passes, see the table on page 331. If after one minute
nothing is displayed on the test set, the test fails.
The abbreviations used in Service SPID Display have the following meanings:
UU Universal cabinet number (1 – 44 for PNs)

C Carrier (A,B,C,...)
SS Slot (01, 02,...)
pp port (01 – 12)
ext extension one and two (1 – 99999)
SPID service profile identifier
Table 63: Service SPID Display
Restricted service starting 8 14 25 31

display column
port location - ext1 - SPID111111 - ext2 - SPID222222
starting display column 8 14 25 31
port location * ext1 * SPID111111 - ext2 - SPID222222
Bound to second endpoint 8 14 25 31
translation starting display
column
port location - ext1 - SPID111111 * ext2 * SPID222222
SPID facility test 1

Test result
FAIL
Cause
No response is received from the endpoint.
Proposed Solution
1. Check the physical wiring between the switch and the endpoint or adjunct.
2. If test continues to fail, escalate the problem.

Test result
FAIL
Cause
Display does not match administered port address for the endpoint or adjunct.
Proposed Solution
1. Change station administration for endpoint or adjunct to match displayed port address.

Test result
PASS
Cause
Display matches administered port address for the endpoint or adjunct.
Proposed Solution
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:
4. Verify that the TEI values administered in the switch and the adjunct are consistent.
5. If the TEI values are correct, consult the recommended repair procedures of the
manufacturer for the adjunct.
CAB-EXFR (Emergency Transfer)

log level
CAB-EXFR MIN test environment location Emergency Transfer
MAJ test environment location l
The emergency transfer feature connects some central office trunks directly through to analog
user stations when the system has a serious problem or experiences a total power failure.
Emergency transfer is activated by the TN2312BP IPSI when:
• The system is booting.
• The cabinet containing the TN2312BP IPSI board is in power failure.
• The TN2312BP IPSI has detected a loss of control connectivity for more than 70 seconds.
• The server has detected a serious problem in the cabinet.
CLAN-BD (Control LAN Circuit Pack)
• A request is made from a SAT command to set the state of emergency transfer.
On, off, and auto in emergency transfer
This is introduced to set the state of emergency transfer, because a physical switch is not provided
on the faceplate of the TN2312BP IPSI circuit pack to control the state of emergency transfer. The
command for this is set emergency-xfr on | off | auto location
The TN2312BP IPSI supplies -48V DC voltage to an emergency transfer panel. This -48V supply
keeps relays within the emergency transfer panel operating which, in turn, keep analog stations
and CO trunks wired to ports (station and trunk respectively) on the system. When the TN2312BP
IPSI is supplying -48V, the state of emergency transfer is off. When a problem is detected and
the TN2312BP IPSI stops supplying -48V the state of emergency transfer is on. When the
TN2312BP IPSI is in the auto state, it is usually supplying -48V to the emergency transfer panel,
but automatically switches to the on state and stops supplying -48V if it detects a problem.
CLAN-BD (Control LAN Circuit Pack)

level
CLAN-BD MIN test board location long Control LAN circuit pack
WRN test board location
CO-BD (Central Office trunk circuit pack)
MO Name in log Alarm level Initial command to run Full name of MO

CO-BD MIN test board location Central Office trunk circuit
pack
WRN
See XXX-BD (Common Port Circuit Pack/Media Module) on page 520 for circuit pack-level errors.
See CO-TRK (Analog CO Trunk) on page 337 for related trunk information.
CO-DS1 (DS1 CO Trunk)

level
CO-DS1 MAJ 6 test trunk grp#/mem# l DS1 CO Trunk
MIN
WRN test trunk grp#/mem#
6
Many trunk problems are caused by incorrect settings of parameters on the trunk group
administration screen. Settings must be compatible with the local environment and with parameter
settings on the far end. Refer to the Administering Avaya Aura® Communication Manager for
information on how to administer trunks. Refer to your Avaya representative for the correct
settings for administrable timers and other parameters on a country-by-country basis.
A DS1 CO (central office) 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
on the TN464C or higher suffix, TN2464 circuit packs, and on DS1 Interface Media Modules.
The DS1-CO MO monitors and maintains a CO trunk port on DS1 Media Modules. Throughout
this discussion, the term DS1 applies to all. For more information, see one of the following
maintenance objects:
Circuit Pack or Media Module Maintenance Object

DS1 Interface Media Modules MG-DS1
The DS1 circuit pack or media module supports low level CO trunk signaling interfaces for both
ground-start and loop-start trunks.
Three trunk service states are specified by DS1 CO trunk maintenance:
out-of-service The trunk is in a deactivated state and cannot be used for either incoming or
outgoing calls.
Table continues…
6 A Major alarm on a trunk indicates that alarms on these trunks are not downgraded by set options and that at least
75 percent of the trunks in this trunk group are alarmed. For more information about set options, see Maintenance
Commands for Avaya Aura® Communication Manager, Branch Gateways and Servers.
Note:
For gateways, consult local records for the location and designation of the equipment rack where the gateway is
mounted.
CO-DS1 (DS1 CO Trunk)
in-service The trunk is in an activated state and can be used for both incoming and
outgoing calls.
disconnect ready-for- The trunk is in an activated state but can only be used for an incoming call.
service
CO-DS1 error log entries and recommended actions

Table 64: CO-DS1 error log entries
Error Aux Associated test Alarm On or Command to resolve the

type data level Off error
board
0 0 Any Any Any test trunk grp/mbr
1 57408
1 57487
15 Any Port Audit and Update (#36)
18 0 busyout trunk grp/mbr WRN OFF release trunk grp/mbr
130 None WRN ON test trunk grp/mbr
257 57392 DS1 CO Trunk Dial Tone Seizure MIN OFF
(#314)
WRN
513 57393 DS1 CO Trunk Dial Tone Seizure MIN OFF
(#314)
WRN
769 57484
1025 DS1 CO Trunk Dial Tone Seizure MIN OFF test trunk grp/mbrr 2
(#314)
WRN
1281 Conference Circuit (#7) MIN ON test trunk grp/mbr r 4
WRN
1537 NPE Crosstalk (#6) MIN ON test trunk grp/mbr l r
WRN 3
1793 test trunk location l
2562 16665
2817 52992
3840 Port Audit and Update (#36)
Notes:
procedures.
2. 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.
3. Error type 15: software audit error that does not indicate any hardware malfunction. Run
the short test sequence, and investigate associated errors, if any.
4. Error type 18: the trunk was busied-out and is in an out-of-service state. No calls can be
made on this trunk except Facility Access Test Calls. Release the trunk and retest.
5. Error type 130: 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 or media module.
6. Error type 257: the DS1 Interface circuit pack detects a hardware fault. Aux Data 57392
indicates no external release on PBX disconnect. This alarm will only be raised when the
System-Parameter Country screen has the Base Tone Generator field set to 4 for 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.
7. Error type 513: The DS1 Interface circuit pack detects a hardware fault. Aux Data 57393
indicates belated external release on PBX disconnect. This alarm will only be raised when
the System-Parameter Country screen has the Base Tone Generator field set to 4 for 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.
8. Error type 769: The DS1 Interface circuit pack or media module detects a hardware fault.
The Aux Data contains the following Error Type:—57484, fault is detected on tip/ring.
9. Error type 1793: DS1 Interface media module is out-of-service. Look in the Error Log:
If the port is on Look at
DS1 Interface Media Module MG-DS1 (DS1 Interface Media Module) on page 436
10. 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.
11. 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 2-way trunk from both the near and far ends. Attempt to place
the call again. If the error persists, execute the Dial Tone Seizure test (#314), and follow
those procedures.
12. Error type 3840: Port Audit and Update test (#36) failed due to an internal system error.
Enter status trunk to verify the status of the trunk. If the trunk is out-of-service, then
enter release trunk to put it back into in-service. Retry the test command.
CO-DS1 demand test descriptions and error codes

Investigate tests in the order presented. By clearing errors associated with the first test ,errors
generated from other tests may also be cleared. Click the link to see the full description of the test,
error codes, and recommended actions.
Order of investigation Short test Long test D or ND
sequence sequence
CO-TRK (Analog CO Trunk)

CO-TRK MAJ 7 test port location Analog CO Trunk
MIN
WRN
7
For systems supporting circuit packs:

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 no other trouble is found with
test trunk, run the ATMS test call with test analog-testcall port location full.
Note:
administration screen. Settings must be compatible with the local environment and with
parameter settings on the far end.
Analog CO trunks are 2-wire analog lines to the CO which support both incoming and outgoing
calls. CO trunk MM711 Analog Media Modules have eight ports.
Not all tests in the demand test sequences are applicable for media modules. These tests will
abort with error code 1412. This error can be ignored.
The following sequences show the interactions between the switch and the CO during call setup
for both loop-start and ground-start trunks.
Interactions between switch and CO

The following sequences show the interactions between the switch and the CO during call setup
for both loop-start and ground-start trunks.
Loop start operation for CO-TRK

Idle State:
Tip = ground, Ring = CO Battery
Outgoing Call:
PBX Off-Hook Seize message: Closes the Tip-Ring Loop
CO response: DC loop current + Dial tone
PBX On-Hook Drop message: Open Tip-Ring loop, no loop current
CO response: CO goes to idle state (see Note)
7 A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by set options and that at
least 75% of the trunks in this trunk group are alarmed.
Incoming Call:
CO Applies Ringing Voltage
PBX response: Detect ringing current
PBX Off-Hook Answer message: Close loop
CO response: Trip ringing, provide loop current
PBX On-Hook Drop message: Open Tip-Ring loop, no loop current
CO response: CO goes to idle state
Note:
CO does not normally provide an On-Hook Disconnect signal. Exceptions to this rule include
Netherlands loop start and UK loop-calling guarded-clearing.
Ground start operation for CO-TRK

Idle state:
Tip = open, Ring = CO Battery
Outgoing Call:
PBX Off-Hook Seize message: Places ground on Ring
CO response: Places ground on Tip
PBX response: Close the loop
CO response: Provide loop current
PBX response: Dial out digits
PBX On-Hook first Drop message: Open the Tip-Ring Loop, no loop current
CO response: Open circuit on Tip
CO On-Hook first Disconnect: Open circuit on Tip, no loop current
PBX response: Open Tip-Ring loop
Incoming Call:
CO Off-Hook Seizure: CO applies ground on Tip and applies ringing voltage to the Ring lead.
PBX response: Make trunk busy for outgoing calls
CO Ringing: CO applies ringing voltage to the Ring lead.
PBX response: Detect ringing, ring destination (Attendant, hunt group, etc.)
PBX Off-Hook Answer message: Close loop
CO response: Trip ringing, provide loop current
PBX On-Hook first Drop message: Open the Tip-Ring Loop, no loop current
CO response: Open circuit on Tip

CO On-Hook first Disconnect: Open circuit on Tip, no loop current
CO-TRK error log entries and recommended actions

Table 65: CO-TRK error log entries
Error Aux Associated test Alarm On or Command to resolve the error

type data level Off
board
1 57347
15 any Port Audit and Update (#36)
18 0 busyout trunk WRN OFF release trunk grp#/mem#
130 WRN ON test port location r 2
257 50176
513 57364 MAJ ON
MIN
WRN 1
769 57392 MAJ OFF
MIN
WRN1
1025 Any CO Port Diagnostic Test (#3) MAJ OFF test port location r 2
MIN
WRN1
1281 Any CO Port Diagnostic Test (#3) MAJ ON test port location r 3
MIN
WRN1
1537 Dial Tone Test (#0) MAJ OFF test port location l r 2
MIN
WRN1
1793 Looparound and Conference MAJ ON test port location l r 3
Test (#33) MIN
WRN1
2049 NPE Crosstalk Test (#6) MAJ ON test port location l r 3
MIN
WRN1
2561 57345
2817 57360
2817 57393
Table continues…

type data level Off
board
2817 57484 Dial Tone Test (#0) MAJ OFF test port location long
MIN
WRN
3073 57376
3329 57408
3329 57484 Dial Tone Test (#0) MAJ OFF test port location long
MIN
WRN
3585 57424
3840 8000 ATM Transmission Test OFF test analog-testcall
(#844-848) full
3841 ATM Transmission Test MIN OFF test analog-testcall
(#844-848) full
1. Major alarms may be downgraded to Warning alarms based on the value used in set options.
Note:
procedures.
2. These are in line errors that have no specific test associated with them. Numerous
Error Types have these errors. Refer to the table on page 341 for an explanation and
appropriate action.
3. Error type 15: software audit error that does not indicate any hardware malfunction.
Run short test sequence, and investigate associated errors.
4. Error type 130: the media module has been removed or has been insane for at least 11
minutes. To clear the error, reinsert or replace the circuit pack.
5. Numerous Error types have these errors.
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 will cause Dial Tone Test #0 to run and are only considered a problem
if the Dial Tone test fails in which case Error type 1537 will also show up. In this
case, the trunk may be put in Ready-for-Service state shown as disconnected by
status command, that allows only incoming calls. Run Dial Tone Test #0, and follow its
outlined procedures.
If error count associated with this Error type is very high i.e., 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,
every Call Seizure test has passed. Problems at the CO may cause this condition
rather than problems with the PBX.
6. Error types 1025/128: logged for every version of the CO-TRK/CO-BD. However, no
MINOR alarms will be generated for Central Office Trunks TN747B with vintages V8 or
greater. Any failures received by this test will still be logged as Error type 1025/1281.
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.
7. Error type 3840: test calls made by the Automatic Transmission Measurement System
(ATMS) returned measurements in the unacceptable range.
Error type 3841: measurements were in the marginal range. Enter list testcall
detail to examine the specific transmission parameters that are out of spec, and
investigate the trunk for that kind of noise. If the noise is acceptable, then the AMTS
thresholds administered on the trunk group screen should be changed.
Table 66: CO trunk errors with no tests
Error Aux Error description and repair action

type data
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 will be accepted. Busyout
the affected port, and run a long test. 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 referred to
the CO.
257 50176 Battery reversal detected. This is usually caused by the CO. 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. Refer problem to CO. Ask
them to remove the battery reversal option.
513 57364 Ground detector stuck active. After several occurrences, an on-board minor
alarm is generated. Run the short test sequence. 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, or the loop is not
open after a disconnect. After several occurrences, an off-board or on-board
warning alarm is generated. Refer problem to CO.
Table continues…
Error Aux Error description and repair action

type data
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 will also fail. The last cause
could be that certain types of noise are present on the CO line during the
silent period of ringing. First check for other errors. If the count for this error
is very high 255, and every test passes, then either the reverse current
detector is defective or the CO line is noisy. If the CO line is suspect, make
Tip and Ring observations. If the line is determined to be noisy, refer the
problem to the CO. If the reverse current detector is defective, ignore this
error.
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.
2817 57393 The loop is opening too slowly after a disconnect. This error indicates an
on-board problem, although the trunk may be functional. Check for other
errors.
3073 57376 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 every outgoing call should also fail. Check for other errors.
3329 57408 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.
a. Busyout the affected port, and run a long test. Observe the test results.
If any tests fail, refer to the description of the tests and the associated
error codes. Release the port.
b. If users continue to report troubles, check for other errors and make
test calls to determine whether the problem should be referred to the
CO. Busyout the affected port, and run a long test. If Dial Tone Test #0
passes, ignore this error. Release the port.
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. Busyout the
affected port, and run a long test. If the CO Port Diagnostic Test #3 passes
and this error keeps occurring, refer problems to CO. Release the port.
DID-DS1 (Direct Inward Dial Trunk)
CO-TRK demand test descriptions and error codes

Order of investigation Short test Long test D or /ND
sequence sequence
Dial Tone Test 0 on page 525 X ND
CO Port Diagnostic Test 3 on page 529 X X ND
Looparound and Conference Test 33 on page 566 X ND
Note:
The CO Port Diagnostic Test (#3) will always return a PASS indication for CO-TRK/CO-BD.
However, any errors produced as a result of this test will be logged and produce no alarms. If
errors logged by Test #3 are the only complaints against this trunk, then 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 will cause Test #3 to log errors. However, all else being normal,
these errors should not affect the customer.
Note:
The ATMS tests are not part of either test sequence. They are run either on demand with
test analog-testcall or by the ATMS schedule.

level
DID-DS1 MAJ8 test trunk grp#/mem# long Direct Inward Dial Trunk
MIN
The DID-DS1 trunk provides a digital Direct Inward Dial (DID) trunk from a CO switch to the
system through a DS1 link. A 24-channel DS1 link can support up to 24 DID-DS1 trunk calls
simultaneously. A 32-channel link can support up to 30.
A DID-DS1 trunk can be used for digitized voice and data communications with DS1 signaling
mode, for example, common-channel signaling. The DS1 Interface Media Module support wink-
start and immediate-start trunks and Communication Manager signaling. Throughout this section,
8 A Major alarm on a trunk indicates that alarms on these trunks are not downgraded by set options and that at least
75 percent of the trunks in this trunk group are alarmed.
the term DS1 applies to DS1 Interface Media Module. For more information, see one of the
following maintenance objects:
Media Module Maintenance object

DS1 Interface Media Module MG-DS1
Not all tests are applicable to media modules. These tests will abort with error code 1412. This
error can be ignored.
Two trunk service states are specified in the DID-DS1 trunk maintenance:
out-of-service The trunk is in a deactivated state and cannot be used for incoming calls.
in-service The trunk is in an activated state and can be used for incoming calls.
If a DS1 is out-of-service, every trunk on the media module is put into the out-of-service state, and
a warning alarm is raised.
DID-DS1 error log entries and recommended actions

Table 67: DID-DS1 Error Log Entries
Error type Aux Associated Test Alarm On or Command to resolve the error
data level Off
board
0 0 Any Any Any test trunk grp#/mem#
1 Any
15 Any Port Audit and
Update test (#36)
18 WRN OFF release trunk grp#/mem#
130 WRN ON test trunk grp#/mem#
257 57474
57473
513 57392 MAJ MIN 9
769 57393 MAJ MIN 9
1281 Conference MIN ON test trunk grp#/mem# long r
Circuit Test (#7) 4
WRN 10
1537 NPE Crosstalk MIN ON test trunk grp#/mem# long r
Test (#6) 3
WRN 10
1793 test trunk grp#/mem# long r
2305 50944 MAJ MIN 9 OFF
Table continues…
Error type Aux Associated Test Alarm On or Command to resolve the error
data level Off
board
3840 Port Audit and
Update (#36)
9 10
Notes:
sequence. Refer to each test’s description, and follow its recommended procedures.
2. Error type 1: DS1 Interface media module detects a hardware error on the DS1 DID trunk.
The Aux Data field indicates the following:
57476 On-hook before wink
57477 On-hook before ready to receive digits
57485 Wink too short for valid signal
Maintenance does not start any testing or generate any alarms in response to these errors.
3. Error type 15: Software audit error that does not indicate hardware malfunction. Run short
test sequence, and investigate any errors.
4. Error type 18: The trunk has been taken out of service by a demand busyout. No calls can
be made on this trunk.
5. Error type 130: the media module has been removed or has been insane for more than 11
minutes. To clear the error, reinsert or replace the media module.
6. Error type 257: DS1 Interface media module detects a hardware error on the DS1 DID
trunk. The Aux Data field indicate the source of the error:
57473 Rotary dial rate above 8 pulses per second
57474 Rotary dial rate below 12 pulses per second
trunk. Aux Data 57392 indicates no external release on PBX disconnect.
trunk. Aux Data 57393 indicates belated external release on PBX disconnect.
9. Error type 1793: DS1 Interface media module is out-of-service. Look in the error log:
If port is on Look in
TN767 DS1 Board DS1-BD
TN464 UDS1 Board UDS1-BD
DS1 Interface Media Module MG-DS1
9 This alarm is raised only when the Base Tone Generator field is 4 Italy on the System-Parameter Country screen. This
alarm is a MINOR alarm unless 75% or more trunks in this trunk group are out of service, when the alarm is upgraded to
a MAJOR alarm.
10. Error type 2305: Indicates that a signaling change was detected by the PBX trunk media
module which is inconsistent with the present state of the trunk.
11. Error type 3840: Port Audit and Update test (#36) failed due to an internal system error.
Enter status trunk to verify the status of the trunk. If the trunk is out-of-service, enter
release trunk to put it back to in-service. Retry the test command.
DID-DS1 demand test descriptions and error codes

Order of Investigation Short Test Long test D or
Sequence sequence ND
DIG-IP-S (Digital IP Station)

DIG-IP-S WRN test stationextension Digital IP Station
The DIG-IP-S MO represents softphone and Avaya 46XX phones. The softphone has some DCP
maintenance capability in the form of audits, updates, error log entries, and tests. Avaya46XX IP
phones communicate to the switch via an IP LAN and emulate DCP signaling carried over TCP.
The IP telephone is not attached to a port board. Insertion of the telephone is driven by successful
registration of the endpoint, not by board insertion. It is maintained via a set of explicit TCP/IP ping
requests and errors reported by the User Manager software, which terminates the H.323 signaling
portion of each endpoint. The MO follows standard maintenance methodology and supports test
busyout release status commands.
A registered extension has a port number or ID in the form of SNNNNN, where N is a digit from
0–9. This ID indicates that the extension is a virtual port and a station.
Note:
A port number or ID of SNNNNN does not necessarily indicate that the extension is
registered. A registered extension retains the SNNNNN port number or ID, even if the
extension unregisters later.
DIG-IP-S (Digital IP Station)
DIG-IP-S error log entries and recommended actions

Table 68: DIG-IP-S error log entries
Error Aux Associated test Alarm On/off Command to resolve the error
type data level board
0 0 Any Any test station extension
1 ( a on Registration status inquiry WRN Off
page (#1372)
347)
18 ( b on 0 busyout port | station WRN Off release port | station
page
348)
257 ( c on Signaling Path PING test WRN Off
page (#1373)
348)
513 Any Digital Station Audits Test WRN Off test port | station
( d on (#17)
page
348)
1281 Any Digital Station Audits Test WRN Off test port | station
( e on (#17))
page
348)
1537 40968 WRN Off test port | station
( f on
page
348)
1793 WRN Off
( g on
page
348)
2305 Any
( h on
page
348)
2817 Station Hyperactivity
( i on
page
348)
Notes:
1. Error type 1: Reports the registration status of the endpoint. If the Communication Manager
software 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 the Duplicated server, the station is now basically an
AWOH station and is no longer being maintained. No tests are run for this station.
2. Error type 18: The port/station is busied out by maintenance personnel. Ensure the port/
station is released from busy via release port | station (IP terminal only).
3. Error type 257: 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.
4. Error type 513: Indicates that the terminal failed to respond to the ID Query request. This
implies that there is something wrong with the terminal or the communication path. (IP
terminal only).
5. Error type 1281: Indicates that the terminal is reporting a bad state of health (IP terminal
only).
6. Error type 1537: Indicates that the link has gone down between the terminal and its
gateway to the switch. This likely means that the terminal has unregistered (IP terminal
only).
7. Error type 1793: Indicates the IP station has registered with a Survivable Remote Server.
Follow standard practices to repair the primary server, or network failure.
8. Error type 2305: Indicates that there was an unsolicited Link Reset even though switch
software believed the terminal to be functional and in service. This error can be ignored if
no user complaints are received (IP terminal only).
9. Error type 2817: 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 softphone 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 be marked as hyperactive.
DIG-IP-S demand test descriptions and error codes

Investigate tests in the order presented. By clearing errors associated with the first test errors
Order of Investigation Short test Long test D/ND
sequence sequence
Registration Status Inquiry Test 1372 on page 740 X X ND
Signaling Path PING Test 1373 on page 741 X X ND
Digital Station Lamp Update Test 16 on page 558 X X ND
Digital Station Audits Test 17 on page 561 X ND
DIG-LINE (Digital Line)

DIG-LINE MIN test port location long Digital line
DIG-LINE maintenance monitors and tests ports on digital line media modules, and on hardware
administered as a digital station on those ports. These include stations with only a digital
telephone and stations with a digital telephone linked to a data module.
Standalone data modules and data adaptors in standalone mode are covered by PDMODULE
(Processor Data Module) on page 453.
Service states
Digital line maintenance interacts with digital line media module (MG-DCP) maintenance. The
health of the media module can affect the results of DIG-LINE testing. Keep this in mind when
investigating digital-line problems.
It is sometimes important to know the service state of a station. These service states apply to
digital-line stations:
Out-of-service state The port, and thus the station, have been removed from service. The
busyout command puts the port in the out-of-service state.
Ready-for-service state The port on the media module has been put into service, but the voice
terminal has not yet established signaling communications with the port.
In-service state 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 terminal parameters

This section explains how maintenance software interacts with terminal parameter downloading.
For systems supporting media modules

The MM712 Media Module supports 8410D and 8434D terminals (2-wire, 8-port, A-law/mu-law
selectable).
Programmable terminals
The following parameters are downloaded to programmable terminals.
Table 69: Parameters downloadable to programmable terminals
Parameter Scope Terminal

International flags (A-law/mu-law,Display Mode, System level 84xx, 603x, 302B1
DLI Voltage level)
Primary levels (transmission & sidetone) System level 84xx, 603x, 302B1
Adjunct levels (transmission & sidetone) System level 84xx
Handset expander option System level 84xx
Administrable options (speakerphone and mute Per-terminal 84xx
button)
Administrable softkeys Per-terminal, system level 8410D, 8434D
Nonvolatile memory
Nonvolatile memory stores downloadable parameters in programmable terminals. Once the
terminal is downloaded, it is not be necessary to download it again, even if power is removed
from the terminal. If nonvolatile memory fails with the 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.
Note:
The mu-law companding mode is assigned as a default setting at the factory. For the United
States of America, a programmable terminal can place calls even though it has not been
downloaded from the system.
Download actions
There are several different scenarios that cause a terminal to be downloaded. These can occur as
part of background maintenance activity or on demand from the system access terminal or from a
station.
For the following background actions, the terminal downloads automatically if a download retry
flag for the terminal is set in software. This flag is set:
• At boot time when translation is loaded.
• When translation that affects the parameters of a terminal is changed as part of system
administration action.
• When a port is inserted in software as a result of board insertion or translation change.
Automatic download actions

This section describes download actions that occur automatically.
System reboot and restart

A global download action is started when periodic maintenance tests start after a system reboot
and restart regardless of whether the parameters have been downloaded previously.
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 either:
• Because it was off-hook at the time the system first booted.
• Because the terminal was off-hook at the time translation associated with downloadable
parameters was changed.
Note:
It may take more than 1 hour for periodic tests to reach the terminal that needs to be
downloaded.
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 the table on
page 349, 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.
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 digital line media module 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. This could occur when connectivity to an PN is reestablished
after that PN was down.
• A station port is added to the system by add station or change station.
• A TTI port is activated.
Audits
As part of periodic maintenance, the hardware status audit test queries programmable terminals
to determine what levels or options are 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 soft keys.
Activation of TTI
A terminal is downloaded automatically when it is activated using the Terminal Translation
Initialization (TTI) 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 from those desired, use one of the following demand
download actions to download the terminal.
Demand download actions

Busyout and release command
A maintenance demand busyout and release request for a station causes the terminal to be
downloaded regardless of its previous download status.
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 pound sign (#), 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.
Assign the refresh terminal parameters feature access code on 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.
There is no visible display on a station for the other background or demand download actions. Use
status station and status attendant screens to check the download status of a specified
terminal.
Parameter download status

The status station and status attendant forms display the current download status of
individual 84xx, 603 and 301B1 terminals in the Download Status field. The possible download
states are:
Status Explanation
Complete 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 previously described may also be used to initiate an immediate download.
Not applicable Not a programmable terminal.
Possible reasons for a terminal not being downloaded include:

• Terminal is off-hook.
• Terminal detected a bad checksum.

• Terminal detected a bad or missing EEPROM. Refer to 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.
DIG-LINE error log entries and recommended actions

Table 70: DIG-LINE error log entries
Error type Aux Associated test Alarm On/off Command to resolve the error
data level board
1 409871 WRN Off
– 20
18 0 busyout port WRN Off release port location
location
130 WRN On test port location
257 40971
513 0 Digital station audits WRN Off test port location r 6
(#17)
767 40964 WRN Off
769 40963 WRN Off
40988
1026 WRN Off
1281 Any Digital station audits WRN Off test port location r 4
(#17)
1537 40968 WRN Off
1793 Voice and Ctrl. Local MIN On test port location l r 3
Loop test (#13) WRN 1
2049 GPP NPE Crosstalk MIN On test port location l r 3
Test (#9) WRN
2304
2305 32770
40969
2817 Any Off
3073
3585
Table continues…
data level board
3840 40965
40989
3841 41029
Notes:
sequence.
2. Error type 1, Aux Data 40987: Could indicate 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 media module. Once the problem is resolved,
the alarm is retired after a predetermined amount of time.
3. Error type 1, Aux Data 1 - 20: Occurs when at least 15 off-board problems with the link
to the terminal have been detected. 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 media module. Once the problem is resolved, the alarm is retired after a
predetermined amount of time.
4. Error type 18: The port in question is busied out by maintenance personnel. Use release
port location to release the port from busyout.
5. Error type 130: The media module has been removed for more than 21 minutes. To clear
the error, reinsert or replace the media module.
6. Error type 257: Problems transmitting to the voice terminal. This can be caused by
defective wiring, which 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.
7. Error type 767: A favorable response was received from running the Digital Line Electronic
Power Feed Test 11. No action is necessary. This alarm is resolved with the passing of
time.
8. Error type 769, Aux Data 40963: An unfavorable response was received from the Digital
Line Electronic Power Feed Test 11. See the test for repair procedures.
9. Error type 769, Aux data 40988: The EPF/PTC circuit has been turned off due to an
overcurrent condition.
Once the problem has been resolved, it may take up to 1 hour for the alarm to clear. If the
problem cannot be resolved by one of the previous steps, then replace the media module
or media module.
10. Error type 769, Aux Data 40989: The Communication Manager software sends an EPF
query to the port board for a particular port. The board returns the failure message 40989.
This means that the power for this particular port is not working. As a recovery strategy,
you may busy out or release the port and then re-test the port. However if the failure still
continues, replace the board.
11. Error type 1026: 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.
12. Error type 1537: An off-board warning was generated due to a 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
media module. Once the problem has been resolved, the alarm will be retired after a
predetermined amount of time.
13. Error type 2304: Internal system error. No action is necessary.
14. Error Type 2305, Aux Data 32770: This indicates that the station went off-hook while it was
in the ready-for-service state. Use status station to determine the state of the station.
The off-hook should have moved the station to ready-for-service. No action is necessary.
15. Error Type 2305, Aux Data 40967: An off-board warning was generated due to some
problem with the link to the voice terminal. This can be ignored if no user complaints are
received. Otherwise, ensure 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 media module. Once the problem has been resolved, the alarm will be retired
after a predetermined amount of time.
16. Error type 2817: Port Level Hyperactivity. Fifty or more CCMS uplink messages were
received from the port within ten seconds. The user is taken out of service for a short
interval of time default 30 seconds.
17. Error type 3073: This error occurs when Communication Manager sends a query to
the endpoint for the serial number and the endpoint does not respond. Communication
Manager sends this query to the endpoint periodically and during endpoint initialization.
18. Error type 3585: An attempt to execute a firmware download of a DCP terminal has
failed. The DCP terminal must be replaced before the firmware download can be executed
successfully. Replace the DCP terminal and re-execute the firmware download.
19. Error type 3840, Aux data 40965: No terminal is connected to the Digital Line board. No
maintenance action is required.
20. Error type 3840, Aux Data 40989: The Electric Power Feed (EPF) is on with no load on it.
No action is necessary.
21. Error type 3841: The media module’s message buffer is full. This may be caused by
having many display phones with heavy traffic connected to the media module. No action
is necessary.
DIG-LINE demand test descriptions and error codes


sequence sequence
Digital Terminal Remote Looparound Test 1201 on page 699 X D
Local Loop Test 13 on page 553 X ND
GPP NPE Crosstalk Test 9 on page 547 X ND
Digital Station Audits Test 17 on page 561 X X ND
DIOD-DS1 (DS1 DIOD trunk)

DIOD-DS1 MAJ 11 test trunk grp#/mem# l DS1 DIOD Trunk
MIN
11
Note:
parameter settings on the far end. Refer to Administering Avaya Aura® Communication
Manager for information on how to administer trunks. Contact your Avaya representative for
the correct settings for administrable timers and other parameters on a country-by-country
basis.
A DS1 Direct Inward Outward Dialing (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:
• 31 DS0 channels + 1 framing channel on a 2.048-Mbps link
The DS1 media module supports low-level CO trunk signaling interfaces for both ground-start
and loop-start trunks. This maintenance strategy covers the inline errors log, initialization tests,
periodic tests, scheduled tests, demand tests, and alarm resolution and escalation.
Three trunk service states are specified by DS1 DIOD trunk maintenance:
11 A major alarm on a trunk indicates that alarms on these trunks are not downgraded by set options and that at least
75 percent of the trunks in this trunk group are alarmed.
DIOD-DS1 (DS1 DIOD trunk)
out-of-service The trunk is in a deactivated state and cannot be used for either incoming or
outgoing calls.
in-service The trunk is in an activated state and can be used for both incoming and
outgoing calls.
disconnect (ready-for- The trunk is in an activated state, but can only be used for an incoming call.
service)
DIOD-DS1 error log entries and recommended actions

Table 71: DIOD-DS1 error log entries
data level board
0 0 Any Any Any test trunk grp#/mem#
1 57408
1 57487
57476
57485
15 Any Port audit and
update (#36)
18 0 busyout trunk WRN Off release trunk grp#/mem#
grp#/mem#
130 None WRN On test trunkgrp#/mem#
257 57392 DS1 CO trunk dial MAJ Off
tone seizure (#314)
MIN 12
513 57393 DS1 CO trunk dial MAJ Off
tone seizure (#314)
MIN 12
769 57484
1025 51200
1025 DS1 CO trunk dial MIN Off test trunk grp#/mem#r2
tone seizure (#314) 13
WRN
1281 Conference circuit MIN On test trunk grp#/mem#l r 4
test (#7)
WRN 13
1537 NPE Crosstalk Test MIN On test trunk grp#/mem#l r 3
(#6)
WRN 13
1793 test board location l
2049 57473
57474
57475
Table continues…
data level board
2305 50944
2562 16665
2817 52992
3840 Port audit and
update (#36)
1213
Notes:
sequence. Refer to each test’s description, and follow its recommended procedures.
2. 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 DS1
CO Trunk 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 DS1 CO Trunk Dial Tone Seizure Test 314 and follow
the procedures.
3. Error type 15: Software audit error that does not indicate any hardware malfunction. Run
short test sequence, and investigate any errors.
4. Error type 18: The trunk has been busied out and is in the out-of-service state. No calls
can be made on this trunk except Facility Access Test Calls. For details, see Maintenance
5. Error type 130: The circuit pack has been removed or has been insane for more than 11
6. Error type 257: The DS1 interface circuit pack detects a hardware fault. Aux data 57392
indicates no external release on PBX disconnect.
indicates belated external release on PBX disconnect.
indicates fault is detected on tip/ring.
9. Error type 1025: The DS1 Interface circuit pack detects a hardware fault and Aux Data
contains 51200, port is unavailable. Run the DS1 CO Trunk Dial Tone Seizure Test 314.
10. Error type 1793: DS1 interface circuit pack is out-of-service. Look for UDS1-BD errors in
the error log if the port is on a TN464 UDS1 board.
12 This alarm is raised when the Base Tone Generator field is 4 (Italy) on the System-Parameter Country screen.
This alarm is minor unless 75% or more trunks in this trunk group are out of service, then the alarm is upgraded to a
major alarm.
13 Major alarms may be downgraded to warning alarms based on the value used in set options.
DLY-MTCE (Daily maintenance)
11. Error type 2049:

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 inter-digit time is too
short.
The DS1 interface circuit pack detects a hardware error on the DS1 DIOD trunk. The trunk
cannot 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.
12. Error type 2305: Recorder message, trunk could not be seized (Aux Data 50944). Run CO
Trunk Dial Tone Seizure Test 314 and follow the outlined procedures.
13. 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
Communication Manager and is generated when a second attempt (retry) to seize an
outgoing trunk fails.
14. 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 2-way trunk from both the near and far ends. Attempt to place
the call again. If the error persists, execute the DS1 CO Trunk Dial Tone Seizure Test 314,
and follow those procedures.
15. Error type 3840: The Port Audit And Update Test 36 failed due to an internal system error.
Enter status trunk to verify the status of the trunk. If the trunk is out-of-service, then
enter release trunk to put it back into in-service. Retry the test command.
DIOD-DS1 demand test descriptions and error codes

sequence sequence

DLY-MTCE Minor None Daily maintenance
Major
WRN
The DLY-MTCE MO performs daily translation audits and saves as part of the administered
daily maintenance options on the change system-parameters maintenance screen. If a
translation save times out or fails, an error is logged against this MO.
If save fails Then system raises

3 times in a row Minor alarm
7 times in a row Major alarm
If the audit fields are enabled on the change system-parameters maintenance screen and
the audit fails, a warning alarm is raised.
DLY-MTCE error log entries

There is no repair action for these errors. Escalate the problem.
Table 72: DLY-MTCE error log entries
Error Type Description Alarm level

542 Translation save failure during scheduled MIN
maintenance
MAJ
571 Translation save timeout during scheduled MIN
maintenance
MAJ
572 Translation save failure during translation backup via MIN
the web either scheduled or on-demand
MAJ
573 Translation audit has detected translation corruption WRN
during scheduled maintenance
Daily maintenance interference

The table on page 360lists Communication Manager SAT administration command actions that,
when active, interfere with daily maintenance. Customer administrators frequently use these
commands for routine administration of the system.
Table 73: Communication Manager SAT Command Actions
Likely to disrupt Less likely to disrupt

add backup ping
change busyout recycle
duplicate clear release
remove display reset
set enable restore
format resume
Table continues…
Likely to disrupt Less likely to disrupt

get save
list status
mark test
monitor upgrade
netstat
Other command actions can also interfere with daily maintenance when certain qualifiers are
used in the commands or under certain circumstances. For example, certain test commands,
when used with the modifier continuously could interfere with daily maintenance. However such
command actions are not typically used 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 command time-out feature exists on the system-parameters maintenance. The command
time-out 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 with save translation, and were also not saved because daily maintenance was
prevented from running prior to the system reset. The 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, such as 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, such as 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 Command Time-out field can be viewed by customer administrators. A craft, init, dadmin,
or inads login is required to change the option for the field. The figure on page 362 shows the
Maintenance-related System Parameters screen for Communication Manager.
Figure 3: Change system-parameters maintenance
change system-parameters maintenance Page 1 of 3

MAINTENANCE-RELATED SYSTEM PARAMETERS
OPERATIONS SUPPORT PARAMETERS
CPE Alarm Activation Level: none
SCHEDULED MAINTENANCE
Start Time: 22 : 00
Stop Time: 06: 00
Save Translation: daily
Update LSP and ESS Servers When Saving Translations: y
Command Time-out (minutes): 60
Control Channel Interchange: no
System Clocks/IPSI INterchange: no
change system-parameters maintenance Page 3 of 3
MAINTENANCE-RELATED SYSTEM PARAMETERS
MAINTENANCE SAVE TRANSLATION CORRUPTION AUDIT
Enable Translation Audit? y
Display Warning When Detected? n
Alarm When Detected? n
Block Save Translation When Detected? n
E-DIG-ST (Emulated Digital Line)
E-DIG-ST (Emulated Digital Line)
MO name in Log Alarm level Initial command to run Full name of MO

E-DIG-ST MIN test port location l Emulated Digital Station
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. Stand-alone data
modules and data adaptors in stand-alone mode are not supported by the TN800 circuit pack.
E-DIG-ST error log entries and recommended actions

Table 74: E-DIG-ST error log entries
Error type Aux Associated test Alarm On or Command to resolve the error
data level Off
board
18 0 busyout port WRN OFF release port location
location
257 40971
1537 40968 WRN OFF
1793 Voice and Control MIN ON test port location l r 3
Local Loop test WRN 14
(#13)
2049 GPP NPE Crosstalk MIN ON test port location l r 3
Test (#9) WRN 14
2305 32770
3840 40965
3841 41029
2304
14
Notes:
procedures.
2. Error type 18: Maintenance personnel have busied out the port in question. Release the
port by using release port location.
4. Error type 257: Problems transmitting to the voice terminal. This problem can be caused by
defective wiring that 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 others.
5. Error type 1537: There is a 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 number of feet of wiring between the jack and the switch.
If the problem still exists, replace the media module. Once the problem has been resolved,
the alarm is retired after a predetermined amount of time.
6. Error type 1793: The local loop test failed. Each failure increments an internal 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.
7. Error type 2049: The NPE Crosstalk test failed. The internal counter increments by 1 when
the NPE Crosstalk test fails. The counter is decremented by 1 when the NPE Crosstalk
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.
8. Error type 2305: The station went off-hook while it was in the ready-for-service state. Use
status station to determine the state of the station. The off-hook should have moved
the station to ready-for-service. No action is necessary.
9. Error type 3840: No terminal is connected to the Digital Line board. No maintenance action
is required.
10. Error type 3841: The media module’s message buffer is full. This may be caused by
having many display phones with heavy traffic connected to the media module. No action
is necessary.
E-DIG-ST demand test descriptions and error codes

sequence sequence
Local Loop Test 13 on page 553 X D
Digital Station Lamp Update Test 16 on page 558 X ND
EMG-XFER (Emergency Transfer)
EMG-XFER (Emergency Transfer)
MO name in log Alarm level Initial command to run 15 Full name of MO

EMG-XFER MAJ test environment UU Emergency Transfer
WRN
15
The maintenance software for Emergency Transfer monitors the position of the Emergency
Transfer switch media modules. It does not monitor whether the system is actually in Emergency
Transfer.
Emergency Transfer (ET) provides the ability to connect designated analog phones to CO trunks
when the switch cannot provide minimal telephone service.
Emergency Transfer is automatically controlled by the system or can be manually controlled via
the Emergency Transfer switch located on the Maintenance media module. 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.
Emergency Transfer Status

The status cabinet UU command shows the location of the ET switches and the current
status of ET in the designated cabinet as follows:
auto+ ET is invoked and under system control.
auto- ET is not in effect and is under system control normal operating state.
unavailable The switch settings is not available.
EMG-XFER error log entries and recommended actions

Table 75: EMG-XFER error log entries

type data level Off
board
0 0 Any Any Any test environment UU
1 0 Emergency Transfer Query MAJ ON test environment UU r 3
(#124)
257 0 Emergency Transfer Query WRN ON test environment UU r 3
(#124)
15 UU is the universal cabinet number listed in the PORT field of the Alarm or Error Log.
Notes:
1. Error type 0: Run the short test sequences first. If every tests passes, run the long test
sequence. Refer to each appropriate test description and follow its recommended repair
procedures.
2. Error Type 1: the Emergency Transfer switch located on the Processor media module is
set to the manual ON position up. When the Emergency Transfer switch is in this position,
a Major alarm in generated.
3. Error Type 257: the Emergency Transfer switch located on the Processor circuit pack is set
to the manual OFF position down. When the Emergency Transfer switch is in this position,
a Warning alarm is generated.
ERR-LOG (Error Log)

ERR-LOG none none Error Log
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, every log will
be re-initialized and a hardware error will be logged against ERR-LOG indicating the time of
inconsistency. There are no tests and no alarms for the Error Log MO. It exists solely for the
purpose of allowing errors to be logged against it.
ERR-LOG error log entries

Error Aux data Associated test Alarm On or Off Command to resolve the
type level Board error
510 See Note none none none
Notes:
1. Error type 510: An inconsistency was detected in either the Alarm Log, the Hardware Error
Log, or the Software Error Log. The system attempts to recover the logs but, depending
on the extent of the corruption, some or all entries in the logs may be lost. 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 During a periodic audit of the Error Log
1 After an extended reboot
2 After a reboot
3 After a Reset System 3 (Cold_1)
Table continues…
Survivable Core Server
0 During a periodic audit of the Error Log

4 After a Level-3 System Reset (Cold_1)
4 After a Reset System 2 (Cold_2)
8 After a Level-2 System Reset (Cold_2)
16 After a Level-1 System Reset (Warm Start)
100 After an internal software audit
2500 After a single-process (MDM) restart

Survivable Core MAJ None Survivable Core Server
Server
MIN
The Survivable Core Server maintenance object (MO) monitors the status of the Survivable Core
Server feature.
On the Main server, the MO will:
• Monitor the registration status for all administered Survivable Core Servers. The command
display survivable-processor list the administered Survivable Core Servers. The
registration status of all Survivable Core Servers is initially checked approximately ten
minutes after the Main boots up. Subsequent to this, the registration status for all Survivable
Core Servers is monitored each time a Survivable Core Server registration status change is
received at the Main server.
On a Survivable Core Server, the MO will:
• Monitor the registration status of the active server within a Survivable Core Server. Only the
active server of a Survivable Core Server pair will register with the active Main server. The
Survivable Core Server MO at a Survivable Core Server does not track the registration status
of other Survivable Core Servers.
Survivable core server error log entries and recommended

actions
Table 76: Survivable Core Server error log entries
Error Aux Associated test Alarm On or Recommended action

type data level Off
board
1 None MAJ OFF Survivable Core Server controlling Port
Network or Port Networks: Resolve any
server and network problems. Schedule or
initiate an on-demand switchback of Port
Networks to the Main server.
257 None MIN OFF Survivable Core Server is not registered:
Resolve any server and network problems.
513 None MIN OFF Connection not established between
Survivable Core Server and PROCR:
Resolve any Survivable Core Server
and network problems. Use the PING
command to verify connectivity to PROCR.
769 None MIN OFF This alarm is raised when a main
server has administration for a duplicated
Survivable Core Server that is missing the
Server A IP address.
To retire the alarm, use the change
survivable-processor command
to administer the Server A IP address for
each Duplicated Survivable Core Server.
Notes:
Note:
1. Error type 1: This error only applies to a Survivable Core Server.
Investigate and attempt to retire the alarm with the following steps:
a. Avaya Fault and Performance Management can be used to obtain a network view
of the Survivable Core Server configuration. Note any network fragmentation or
server outages for Main or Survivable Core Server.
b. Using either Avaya Fault and Performance Management or SAT sessions to each
server, determine the extent of any server or network outages.
c. Resolve any server outages. If possible, bring the Main server Main servers back
online first.
d. Resolve network fragmentation and outage issues per local practice.
2. Error type 257: This error applies to a Main or Survivable Core Server. This error
is generated when a Survivable Core Server is translated on the Main but is NOT
registered with the Main.
For detailed information on maintenance commands, see Maintenance Commands for
Avaya Aura® Communication Manager, Branch Gateways and Servers.
For detailed information on administration commands, see Avaya Aura®
Communication Manager Survivable Options.
Follow these steps to investigate and attempt to retire the alarm:
On the Main server:
a. Enter display survivable-processor to verify that the Survivable Core
Server is administered. A Survivable Core Server must be administered on the
Main server before it can register with the Main server. Record these values for
troubleshooting the Survivable Core Server.
b. Use the display events command with a category of denial to display denial
events related to Survivable Core Server. The Survivable Core Server registration
denial events are in the 36xx range. See Survivable Core Server Denial Events in
Avaya Aura® Communication Manager Denial Events for descriptions of individual
Survivable Core Server denial events.
c. Use the list trace ras ip-address command to monitor registration
requests from the Survivable Core Server. This command displays registration
requests from the Survivable Core Server and the associated response from the
Main server. Note that under normal operation a Keep-Alive (KA) message is
periodically sent from the Survivable Core Server to the Main server. This should
not be confused with a registration failure.
d. Firewalls or other security measures may prevent the Main server and Survivable
Core Server from communicating. Verify that these ports are open through the
network between the Main server and the Survivable Core Server:
• 1719 Registration between the Survivable Core Server and the Main.
• 21874 Filesync (rsync) between the Main server and Survivable Core Server.
On the Survivable Core Server that is not registered:
Caution:
In the next steps, be careful to use the Close Window button to cancel out of the
Configure Server page to avoid a reboot of the Survivable Core Server. Do
not Update the system.
a. Use the bash ping nnn.nnn.nnn.nnn command to verify connectivity between
the Survivable Core Server and Main servers, where nnn.nnn.nnn.nnn is the
IP address of the PROCR in the Main server that the Survivable Core Server
is trying to register with. To determine which IP address the Survivable Core
Server is attempting to register with, enter the Configure Server command
from the Maintenance Web Interface on the Survivable Core Server to display the
configure ESS screen.
b. Firewalls or other security measures may prevent the Main server and Survivable
Core Server from communicating. Verify that these ports are open through the
network between the Main and the Survivable Core Server:
• 1719 Registration between the Survivable Core Server and the Main server.
• 21874 Filesync (rsync) between the Main server and Survivable Core Server.
c. On the Maintenance Web Interface Configure Server pages:
• On the Set Identities page, verify that the correct Server ID (SVID) is entered.
This should be a unique value for each server. The SVID must be between
1 and 99. Gaps in the SVIDs for a configuration are allowed (10, 20, 30,...)
but the servers may be consecutively numbered if desired. Each server in the
system, duplex or simplex, Main or Survivable Core Server, requires a unique
SVID.
• On the Configure ESS page, verify that the correct platform type is selected
and the correct PROCR and Main server IP addresses are entered. The
Survivable Core Server will use these addresses to establish a connection
with the Main server and register. On the Main server, enter display
survivable-processor to verify that the Survivable Core Server is
administered. A Survivable Core Server must be administered on the Main
server before it can register with the Main server. Record these values for
troubleshooting the Survivable Core Server.
• On the Status Summary page, verify that the Cluster ID is correct. Verify that
the individual server IDs are correct.
Note:
Note: The individual server IDs should be the same as those entered on
the Set Identities page of the Configure Server procedure.
d. On the SAT, enter display system-parameters customer-options.
• Verify that the ESS Administration field is set to y.
• Verify that the Enterprise Survivable Server field is set to y.
Tip:
Customer options may only be set with the Communication Manager
license file. If the fields above are incorrect, obtain a new license file with
corrected data.
e. From the Maintenance Web Interface, click on the License File command.
Verify that the license mode is normal.
3. Error type 513: This error only applies to a Survivable Core Server. A socket
connection cannot be established between the Survivable Core Server and a PROCR.
a. From the Maintenance Web Interface pages of the Survivable Core Server that is
not connecting, initiate a ping to the administered PROCRs to verify connectivity
between the Survivable Core Server and PROCRs.
ETH-PT (Control LAN Ethernet)
b. Firewalls or other security measures may prevent the server and PROCR from
communicating. Verify that these ports are open through the network between the
server and the PROCR.
4. Error type 769: If the main Survivable Core Server detects a Survivable Core Server
administration for a duplicated Survivable Core Server which is missing the server
A IP address, an alarm is raised. In a translation upgrade, as the Main Survivable
Core Server detects Survivable Core Server administration for a duplicated Survivable
Core Server, an alarm is always raised after the upgrade to a Survivable Core Server
system that has duplex ESS. Demand test descriptions and error codes
There are no demand tests for the Survivable Core Server maintenance object. The following
table contains the explanation of the error codes from Tests 1605, 1606, and 1607 on the TEST
RESULTS screen which is displayed from the following commands:
• enable ess
• disable ess
Error code Description
1991 Requested Survivable Core Server cluster is not administered.
1992 Requested Survivable Core Server cluster is not registered.
1994 A Survivable Core Server cluster may not enable or disable other clusters for
Survivable Core Server or main. It can only change its own enable or disable state.
1995 Survivable Core Server cluster is disabled.
1996 Port network does not exist.
2500 Internal operation failed
See also:
• list survivable-processor command in Maintenance Commands for Avaya Aura®
Communication Manager, Branch Gateways and Servers
• SP-REG-M (Survivable Processor-Main) on page 503
• SP-REG-S (Survivable Processor) on page 504

ETH-PT MAJ test port location long Ethernet Port
MIN
ETH-PT error log entries and recommended actions

Table 77: ETH-PT error log entries
Error Aux Associated test Alarm On or Command to resolve the

type data level Off error
board
1 0 Ethernet Local Looparound Test MIN ON test port location l r
(#1278) 3
513 0 Link Integrity Inquiry Test (#1282) MIN OFF test port location r 3
769 0 WRN OFF
1281 0
1537 Session Status test (#1286) MIN OFF
1538
1793–
1920
2305–
2560
2561–
2816
3329 TCP/IP Ping test (#1281) MIN OFF test port location r 3
WRN 1
Notes:
procedures.
2. Error type 1: Ethernet Local Loop around Test (#1278) failed.
a. Test the port. Type test port location long
b. See Ethernet Local Looparound Test 1278 for repair procedures.
3. Error type 513: Link Integrity Inquiry test (#1282) failed, or the PROCR port detected loss
of Ethernet link integrity.
Possible causes:
• Cables
• Ethernet transceiver
a. Test the port. Type test port location long
b. If the Link Integrity Inquiry Test 1282 fails, refer to its repair procedure.
4. Error type 769: Port received invalid frame.
Invalid Ethernet frame errors occur when the frame:

• Contains a bad cyclic redundancy check (CRC)
• Is misaligned
a. Isolate the problem with the Ethernet Local Looparound Test 1278.
b. Test the port. Type test port location long
c. Verify the repair with the Ethernet Local Looparound Test 1278.
d. Clear the alarm. Type test port location long clear
5. 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. No action is necessary.
6. Error type 1537–1538: Some or all sessions on a port are down.
If Then the switch raises
Some sessions are down WARNING alarm on circuit pack
Every session is down MINOR alarm on circuit pack
a. Test the port. Type test port location

b. Refer to Session Status Test 1286 repair procedure to verify repair.
7. Error type 1793–1920: System software received an indication that a socket was closed
due to an error.
The Error type indicates the application associated with this socket. The Aux Data value
indicates the internal application number.
Error type Application
1793 Unused
1794 DCS
1795 AUDIX
1796 CMS
1797 ISDN Gateway
1798–1920 Reserved for future
8. Error type 2305–2816: System software detected a session is down. The Aux Data value
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.
9. Error type 3329: TCP/IP Ping test failed. A WARNING alarm is raised if the test fails twice.
A MAJOR alarm is raised if the test fails 6 times.
a. Test port. Type test port location
b. Refer to TCP/IP Ping Test 1281 repair procedures.
ETH-PT demand test descriptions and error codes

Investigate errors in the order they appear in the following table.
sequence sequence
Ethernet Local Looparound Test 1278 on page 737 X D
ETR-PT (Enhanced Tone Receiver Port)

level
ETR-PT MAJ test port location Enhanced Tone Receiver Port
MIN
WRN
FW-STDL (Firmware Station Download)
MO Name Alarm Level Initial Command To Run Full Name of MO

FW-STDL WRN test firmware station-download Firmware Station
Download
The Firmware Station Download feature provides the ability to download new firmware to one or
more DCP stations of the same type residing in the same system.
The download image is copied from a tftp file server into Communication Manager memory
through the change tftp command. The transfer of the download image from Communication
Manager memory to the target station is done under switch software control. The image is
downloaded to the target stations flash through the change firmware station-download
command. The target stations must be connected and in service to receive the firmware image.
Firmware station download commands

The following is a list of commands associated with the Firmware Station Download feature.
• change tftp-server - Copies the firmware image from the FTP file server into
Communication Manager memory.
• change firmware station-download - Set up a station download schedule.
• disable firmware station-download - Cancel an existing station download schedule

while allowing any active terminal downloads to complete.
• display firmware station-download - Displays information for the current download
schedule.
• status firmware station-download - Displays the status of the current scheduled
download or the one that has just finished if there were errors in any of the downloads. Use
the following tables for details on the schedule status and interpretation of error codes:
- The table on page 380
- The table on page 378
• status firmware station-download last - Displays the status of the previously
completed scheduled download.
• test firmware station-download - Resolves any alarms or errors associated with
firmware station download (FW-STDL).
Firmware download to DCP stations

Updated firmware can be downloaded to up to 1000 Avaya DCP stations. This eliminates the need
to use a feature access code (FAC) to perform the firmware update for each station. To download
firmware to these stations, Communication Manager requires:
• A valid firmware image loaded into Communication Manager memory through the change
tftp command.
• Avaya Communication Manager 2.0 or greater software.
• Craft login.
The high-level process for downloading the firmware is to:
1. Downloading the firmware image on page 375
2. Reading the image into memory on page 376
3. Scheduling the download on page 377
The target stations are automatically taken out of service before the firmware is downloaded to
them and automatically returned to service after the download is completed. Once a download has
started, the station cannot be used until the download completes. If a station is in use at the time
that it is scheduled to be downloaded, the download to that station will be aborted and the call will
not be affected. The status firmware station-download command and the error log will
provide information on aborted downloads.
Downloading the firmware image

About this task
Customers can access and download the firmware image on site using the Avaya Customer
Support Web site.
Procedure
1. Go to the Avaya Customer Support Web site ( http://support.avaya.com/) .
2. From the Support menu, select Software & Firmware Downloads.
3. Select the firmware image or images needed from the list provided.
4. Download the file or files to a temporary directory on a personal computer that has FTP
and network access to the Avaya server.
Reading the image into memory

About this task
Before the firmware can be downloaded to the target stations, the image file must first be read into
Communication Manager memory.
Procedure
1. On the System Access Terminal (SAT) using the craft login and password, enter change
tftp-server
The TFTP Server Configuration form displays the following:
change tftp-server Page 1 of 1

TFTP Server Configuration
Local Node Name: clan1 TFTP Server Node Name: tftpserv1 TFTP Server
Port: 69 File to Retrieve: 2420v01.bin File Status:
File Size:
Filename in Memory:
Station Type:
2. Enter the node name of the PROCR that connects over the LAN to the FTP file server in
the Local Node Name field.
3. Enter the host name of the FTP file server in the TFTP Server Node Name field.
4. Enter the port number in the TFTP Server Port field.
5. Enter the name of the File to Retrieve from the FTP file server and submit the command.
6. Enter display tftp-server.
display tftp-server
TFTP Server Configuration
Local Node Name: clan1
TFTP Server Node Name: gingerale
TFTP Server Port: 69
File to Retrieve: 2420v015.bin
File Status: File download successful File Size: 236
Filename in Memory: 2420v015.bin
Station Type: 2420
7. Verify the file download was successful by checking the File Status field.
Scheduling the download

About this task
The new firmware image can be downloaded immediately or scheduled for a later time. Due
to the potentially large volume of switch activity as a result of the firmware download, Avaya
recommends that the download be scheduled for a time when the system will be at its lowest
possible occupancy level. This will also limit the number of stations that are aborted because they
were in use at the scheduled download time.
Procedure
1. On the System Access Terminal (SAT) using craft login and password, enter change
firmware station-download.
The Firmware Station-Download form displays the following:
change firmware station-download Page 1 of 1

FIRMWARE STATION-DOWNLOAD
Source File: 2420v01.bin
Schedule Download? y
Start Date/Time: 10/15/2006 20:00 Stop Date/Time: 10/15/2006 23:00
Continue Daily Until Download Complete? y
Download Station Type: 2420
Beginning Station: 85001 Ending Station: 86000
2. Select parameters for the download:

• Enter the firmware filename in the Source File field.
• If you want to schedule the download for a later date/time, enter y in the Schedule
Download Field.
- Enter a start time in the Start Date/Time field.
- Enter a stop time in the Stop Date/Time field.
- If you want to stop the firmware download at the scheduled stop date/time and
resume the next day at the scheduled start time, enter y in the Continue Daily Until
Download Complete field.
• Enter extension numbers in the Beginning Station and Ending Station fields. You can
enter a maximum of 1,000 stations. Only administered stations within this range with a
set type matching the Station Type displayed on this page are available for download.
3. Submit the command.
Firmware download problems

You cannot start a station download while there are active FW-STDL alarms. To clear all
active FW-STDL alarms, use test firmware station-download. In the event of an FW-
STDL alarm, you can find more details by using the status firmware station-download
command.
status firmware station-download Page 1 of 1

STATUS FIRMWARE STATION DOWNLOAD
Image File: 2420v01.bin

Schedule Download? y Continue daily until completed?: y
Start Date/Time: 10/15/2006 20:00 Stop Date/Time: 10/15/2006 23:00
Status for this download: Active
Terminal type for download: 2420
Extension Range: 85001 to: 86000 Number of stations in range: 35
Stations completed: 0 Stations unsuccessful: 1
Extension Status Error Extension Status Error Extension Status Error
85001 ABRT 513
85002 ACTV
85017 ACTV
85034 ACTV
This command displays the Extension of the terminal, the Status, and a Error code if applicable.
All aborted (ABRT), failed (FAIL), and actively downloading (ACTV) terminals are listed on this
screen; pending or completed downloads are not listed. See the table on page 378 for a list of
these errors and their descriptions.
FW-STDL error log entries and recommended actions

Table 78: FW-STDL Error Log entries
Error Aux Associated Alarm On/Off Command to resolve the error

Type Data Test Level Board
257 1 WRN OFF test firmware station-download
513 4 MIN OFF test firmware station-download
Notes:
1. Error type 257: The problem originated with the target terminal. Resolve the alarm with the
test firmware station-download command. The Aux Data values associated with
Error Type 257 are described in the table on page 379.
Table 79: Error Type 257 Aux Data descriptions

1 Terminal failed to erase its program flash.
2 Target image file checksum is bad.
3 Target image is incompatible with the terminal (Avaya 2420 DCP sets only).
4 Target terminal rejected image as invalid.
12 Target terminal fails to go into the download mode, timeout occurred.
13 Station firmware download engine timed out waiting for download to complete.
14 Station firmware download to a terminal had too many retries, timeout occurred.
2. Error type 258 with Aux Data 5: One or more terminals in the download list were skipped
and not downloaded because the terminal was not in the appropriate state (in-service and
idle). Resolve the alarm with the test firmware station-download command. This
error can be caused by any of these problems:
• One or more target terminals were busied out by craft.
• One or more target terminals were in use when the download attempt was made.
• One or more target terminals were out of service for an unknown reason.
Use the status firmware station-download command in conjunction with the
table on page 381 to determine the specific cause of the failure to download.
3. Error type 513: Indicates a firmware download error that is not necessarily caused by
the target terminal. This error will cause the firmware download process to be stopped.
Resolve the alarm with the test firmware station-download command. The Aux
Data values associated with Error Type 513 are described in the table on page 379.
Table 80: Error Type 513 Aux Data descriptions

4 Two consecutive terminals failed to download with a failure indicating that the
terminals did not accept the firmware image. It is likely that any remaining
terminals will also fail, so the scheduled download is stopped and any terminals in
the download list that are not yet downloaded are aborted.
8 The download image file is not present. The change firmware station-
download form requires that the image file be present before the form can be
brought up. This error indicates a problem with the image file. As a result of this
failure, the schedule cannot continue, and any terminals in the download list that
are not yet downloaded are aborted.
11 There was a system error in the download process, possibly due to inter-process
calls. Escalate the problem.
13 Two consecutive terminals failed to download due to internal timeouts. It is likely
that all terminals will fail as well so the schedule is stopped and any remaining
terminals in the download list are aborted.
Table continues…

14 Could not build a list of terminals from the range specified on the change
firmware station-download form. Check the administered stations for exact
extension numbers.
15 The scheduled stop time was reached without completion of all scheduled
terminals. The status firmware station-download command indicates all
terminals not downloaded with a status of ABRT and a Reason Code of 3 (see
the table on page 381) . If the Continue daily until completed field is y, this error
will not occur because the continuation option causes the schedule to resume the
next day at the scheduled start time (see the table on page 380) .
Table 81: Schedule States of status firmware station-download
State Schedule Description

Done?
Idle No There are no downloads Pending or Active, or there are no
unresolved errors/alarms for the last download
Pending No Download has been scheduled but not yet started. Check the
start time to see when it is scheduled to start.
Active No Download is currently active. Actively downloading terminals
should be listed with a status of ACTV. If the schedule has
just started and no downloads are listed, the system may be
waiting for a FAC requested or terminal requested download to
complete before it begins.
Resume-pending No Download was stopped at the Stop Date/Time but not all of the
terminals have been attempted. Downloading will resume at the
scheduled Start Date/Time listed on the screen.
Aborted Yes Download was aborted for the entire range of terminals. This
could happen if the firmware image was bad, damaged or
disappeared.
Failed Yes At least two terminals rejected the firmware as invalid. As
a result, the download was aborted to avoid problems with
any further terminals. Check the Reason Codes of the failed
terminals in the list to find the reason why the download failed
(the table on page 381) .
Completed Yes The scheduled download has completed either due to all
terminals in the range of extensions having completed or due
to the stop timer.
Disabled Yes An Active schedule was disabled with the disable firmware
station-download command. After an active schedule is
disabled, the Schedule state remains Active until all currently
active terminal downloads have completed.
No Image Yes The download was stopped because there was no firmware
image present in memory.
Table continues…
State Schedule Description

Done?
Restart Yes The download was stopped due to a system restart. You must
schedule a new download for any Aborted terminals.
Sys Fail Yes The download was stopped due to a system error.
Sys Occ No The download has been suspended due to the system’s
occupancy level. The schedule will resume when the occupancy
level drops to a safe level.
Dnld Timeout Yes While the scheduled download was running, two or more
consecutive terminals failed to respond to the download
process.
Table 82: Reason Codes for status firmware station-download
Reason Status Description

Code
1 ABORT The firmware image that was noted on the change firmware station-
download form has disappeared. The download schedule had to be
stopped.
2 ABORT The terminal could not be downloaded due to an internal discrepancy
relating to the maximum number of downloads allowed.
3 ABORT The terminal was not downloaded before the scheduled stop time
occurred. Schedule a new download with adequate time for the downloads
to complete, or select the continue daily option to allow the schedule to
resume the following day.
4 ABORT The terminal could not be downloaded because the schedule aborted for
an unknown reason.
5 ABORT The terminal did not respond to the download request.
6 ABORT The terminal that was added to the download list at the scheduled start
time no longer exists. This can occur when a station is removed during an
active download schedule. Download to this terminal was aborted.
11 ABORT The terminal was in firmware download mode when the layer 2 link to the
terminal went down. The download was aborted as a result of the link
down condition.
18 ABORT The terminal was busied out by craft and could not be downloaded.
32 ABORT Download to the terminal timed out due to an internal error in the station
firmware download process.
1000 ABORT Terminal was in use at the time that it was to be downloaded. Download to
this terminal was aborted.
1012 ABORT An internal error occurred while preparing to download to this station.
Table continues…
Reason Status Description

Code
3841 ABORT The system restarted during an active download. As a result, all terminals
or FAIL that were not downloaded are marked with a status of ABORT with this
reason code. All terminals that were actively downloading when the reset
occurred are marked with a status of FAIL with this reason code.
128 FAIL The terminal rejected the firmware because the firmware image failed the
checksum test.
129 FAIL The terminal rejected the firmware because the firmware image failed the
image validity test. The firmware image may not be the right image for the
hardware being downloaded to.
130 FAIL The terminal being downloaded could not write its flash memory.
131 FAIL A terminal in the range was translated to be a valid terminal for this
download schedule. However, the terminal is not a valid receiver of the
download.
513 FAIL The terminal was not in service at the time that it was to be downloaded.
Download to this terminal failed.
3584 FAIL The terminal rejected the firmware image.
H323-BCH (H.323 B-Channel)

No maintenance diagnostic tests exist for this MO.
H.323 signaling is similar to ISDN Q.931 signaling. To take advantage of the existing ISDN , the
H.323 trunk Avaya Communication Manager software 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 Communication Manager software 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 IP-PROCR port and the IP network. Unlike ISDN D-channels,
the H.323 D channel may 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 may be monitored by
IP PING testing.
Performance in terms of voice latency for a signaling group is monitored by background
measurements collected by the media processor board.
H.323 B-Channels use media processor ports to carry the actual bearer. The media processor port
is a service circuit. On a call-by-call basis, any port of a media processor may be serving an H.323
station or an H.323 B-Channel. Status information may exist for a specific H.323 B-Channel, and
H323-BCH (H.323 B-Channel)
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 or 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.
H323-BCH error log entries and recommended actions

Table 83: H323-BCH B-channel error log entries
Error type Aux Associated test Alarm level On/off Service

data board state
18 Any B-Channel busied out Warning Off OOS
Note:
1. Error type 18: This specific H.323 trunk group member has been busied-out by command.
Enter release port location to put the port in the in-service state.
System commands
The following commands are available:
Command Description
Busyout port location The command to disconnect an active call on a
specific H.323 B-Channel and reduce the capacity
of the trunk group by one. No physical piece of
hardware is removed from service.
Release port location On a specific H.323 B-Channel, increases the trunk
group’s capacity by one. No physical piece of
hardware is actually added to service.
Status trunk grp#/mem# Finds 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 location Displays No tests applicable to this
object.
H323-SGR (H.323 Signaling Group)

level
H323-SGR MIN test signaling-group grp# H323 Signaling Group
WRN
The H.323 Signaling Group (H323-SGR) MO supports a signaling channel (D-Channel) for H.323
Trunk connections. The G4xx Media Gateways and Avaya Aura® Media Server provides audio
connectivity, working in concert with a PROCR that provides control signaling to support an H.323
connection.
H323-SGR is a signaling channel that physically resides on a PROCR 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.
H.323-SGR error log entries and recommended actions

Table 84: H323-SGR error log entries
0 0 Any Any test signaling-group grp#
1 Any Ethernet port status test Min Off test signaling-group grp#
(#1386)
18 0 busyout signaling-group WRN Off release signaling-
grp # groupgrp#
257 Any Signaling group ping (#1387) Min Off test signaling-groupgrp#
513 Any Signaling group ping (#1387) WRN Off test signaling-groupgrp#
770 Any WRN Off
1537 Any
2049 Keep alive failure Min Off
2305 Gateway unregistered inline Min Off
error
2561 Any Registered to Survivable Min Off
Remote Server Inline Error
2817 T303 Timer timed out
3585 Layer 3 Test (#1673) Min Off
3841 - Any
3942
Notes:
procedures.
2. Error type 1: Failure of the IP-PROCR carrying the signaling group channel.
3. Error type 18: The signaling group in question has been busied out by command. Release
the signaling group, if appropriate, with release signaling-group grp#.
4. Error type 257: Tracks failures of the H.323 signaling-group PING test. See Signaling
Group Ping Test 1387 for test failure information.
5. Error type 513: Tracks excessive round-trip delay of the H.323 signaling-group PING test,
if the round-trip delay exceeds 4 seconds. See Signaling Group Ping Test 1387 for test
failure information.
6. Error type: 770: Tracks excessive latency and packet-loss from background IP
measurements collected by the VOIP media module. Indicates that test packets sent from
a VOIP media module 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
ip-options screen. Exceeding these thresholds indicates that the IP network may not be
providing sufficient quality of service for adequate transmission of voice. If the signaling
group has been administered to enable BYPASS, then Error Type 1025 also occurs.
7. Error type 1025: The signaling group has been placed into a BYPASS condition because
of IP network congestion. The signaling group accepts incoming calls, but every outgoing
call is denied. The system routes these calls over a secondary route, if one has been
administered.
8. Error type 1281: No media resources are in service to provide VoIP connections for the
trunk members of the signaling group.
9. Error type 1537: 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 Communication Manager server, this
error means the server on the other end does not have media resource in-service for its
signaling group.
This error places the H323 B-Channels into an out-of-service far-end state.
10. Error type 1794: The Signaling Group reported that the far end has detected excessive
packet latency or loss. This error places the H323 B-Channels into an out-of-service
far-end state.
11. Error type 2049: A Keep-Alive timer is set for every registered endpoint on the Remote
Office, and the switch expects Keep-Alive updates within that timer’s time period. If the
update does not occur, an error is logged against REM-OFF as well as H323-SGR. The
error against H323-SGR generates a Minor alarm. This error is only valid if the change
signaling-group screen has the RRQ field set to y. The Keep-Alive Error type 2049 clears
only after a registration occurs and Error Type 2305 clears.
12. Error type 2305: The Gateway, the signaling group on the remote office is unregistered.
The error against H323-SGR generates a Minor alarm when this failure occurs. This error
is valid only if the change signaling-group screen has the RRQfield set to y.
13. Error type 2561: The signaling group is registered to a Survivable Remote Server.
14. Error type 2817: The T303 timer timed out. Notification only, no action is necessary.
15. Error type 3585: Layer 3 test failed. The far-end is not available. See H.323 Signaling
Layer 3 test 1673 for more information.
16. Error types 3842 - 3942: These error types report certain error messages received by the
H.323 Signaling Group for the D-Channel. The Aux datafield shows for which D-Channel
the message was received.
The error code generated equals 3840+ x, where x is a cause value. There is no
recommended action for these error types. No direct action or alarming is performed.
They provide added data that may be useful when tracking down obscure networking and
routing problems. The table on page 386 provides more information.
Table 85: Descriptions and recommendations for error types 3842-3942
Error Description Recommendation

code
3842 A request has been The equipment sending this cause event does not recognize
made to use a transit the transit network.
network or common
a. From the circuit pack or media module and port number,
carrier that cannot be
in the Aux data field, determine the trunk group against
accessed.
which the error was reported.
b. Check every routing pattern containing this trunk group for
validity of interexchange carriers requested (IXC field).
3843 No route to destination.
Request received to
route call through a
transit network that
is recognized but not
allowed to carry the call
or not able to serve the
destination.
3846 The far-end switch has This could indicate an administration problem. For example,
indicated that the B- the local switch and the far-end switch have different B-
Channel trunk is not Channels administered, or could reflect the occurrence of
acceptable for use in a normal race condition. For example, the local switch has
the call for which it was requested use of a B-Channel that the far-end switch had just
requested. reserved for use on another call.
a. From the media module and port number in the Aux Data
field, determine the trunk group against which the error
was reported.
b. Enter status trunk for the indicated trunk. Refer to
DS1 ISDN Trunk Service States on page 406and ISDN-
PRI Trunk Service States on page 409 sections of ISDN-
TRK for recovery suggestions.
Table continues…

code
3858 Similar to error type Follow same recommendations as for error type 1.
1. The switch sent
a message to the far-
end switch or terminal
adapter that did not
respond in the time
allowed.
3878 The far-end switch Network is out-of-order.
has indicated that
a. From the media module and port number in the Aux
the network is not
datafield, determine the trunk group against which the
functioning correctly and
error was reported.
that the condition may
last a relatively long b. Consult with the network provider to determine the nature
period of time. For and expected duration of the out-of-service condition.
example, immediately
c. Consider modifying every routing pattern containing this
re-attempting the call
trunk group to route calls around the network that is out-of-
may not be successful.
service.
3890 A request to This could be a local administration problem only, or a
use a network mismatch between the local administration and that of the
service has been network provider.
denied. Administration
a. From the media module and port number in the Aux data
somewhere on the
network has indicated
was reported.
that the requested
service has not been b. Display the trunk group screen: If the trunk group is
subscribed to, or Call-by-Call, the service type is cbc, check every routing
purchased for this trunk. pattern form containing this trunk group to see if the
Service/Feature Service/Featurefields 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.
c. If local administration is correct, consult with the customer
or the network provider to determine the services that the
customer has subscribed to for this trunk group.
3892 Protocol detail may offer If the customer is complaining of unexpected intercept tones
a clue if the customer is and no other cause can be found, escalate the problem and
having calls denied with provide the next tier with this error log information.
an unexpected intercept
tone.
Table continues…

code
3894 Protocol detail; may First, eliminate any transitory state mismatch problems by
offer a clue if entering test port location for the trunk port shown in the
customer is having Aux data field. Service State Audit Test 256 is the important
ISDN calls denied with test in the sequence. If this passes satisfactorily, yet the
an unexpected intercept customer continues to complain of unexpected intercept tones
tone. and no other cause can be found, escalate the problem and
provide the next tier with this error log information.
3902 FRANCE ONLY: Service
not authorized.
3903 Service or option not
available, unspecified.
This cause reports a
service or option not
available event only
when no other cause in
the service or option not
available class applies.
3905 Protocol detail; may If customer is complaining of unexpected intercept tones and
offer a clue if no other cause can be found, escalate the problem and
customer is having provide the next tier with this error log information.
ISDN calls denied with
tone.
3906 Protocol detail may If customer is complaining of unexpected intercept tones and
offer a clue if no other cause can be found, escalate to the problem and
customer is having provide the next tier with this error log information.
ISDN calls denied with
tone.
3909 A request to use a Follow the previous recommendation for error type 3890.
network service has
been made, but the
network has rejected
the request because the
requested service is not
implemented.
3910 Only restricted digital BC
available.
3919 Service or option
not implemented,
unspecified. Used when
no other cause in this
class applies.
Table continues…
H323-STN (H.323 IP Station)

code
3928 A call was denied This error might be helpful as a clue if the customer complains
because of a basic of receiving unexpected intercept tone. Determine the trunk
incompatibility existed group from the circuit pack or media module and port number
between the type of call in the Aux data field and then check the BCC fields of the
and either the facilities pertinent routing patterns. Also, investigate whether or not
selected by the routing the calling and called endpoints are compatible. For example,
pattern or the called some switches may not allow a voice station to call a data
user. extension.
3942 Timer expiry: T310 time-
out, no answer to call
proceeding.
H323-SGR demand test descriptions and error codes

sequence sequence
Signaling Group Ping Test 1387 on page 746 X X ND
H323 Signaling Layer 3 Test 1673 on page 767 X X ND
H323-STN (H.323 IP Station)

H323-STN WRN test station extension H.323 IP Station
H323-STN covers implementation of the maintenance for native mode H.323 endpoints. Native
mode H.323 applications, such as Netmeeting or Proshare provide only what is needed to support
the H.323 standard. Communication Manager can invoke very little in the maintenance area.
Communication Manager reports errors as they are detected via the RAS registration and keep-
alive mechanism. Communication Manager Pings the endpoint via the signaling path.
The H.323 station type is not attached to a port board. Insertion of the station is not driven
by board insertion, it is driven by successful registration of the endpoint. The H.323 station 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. H323-STN follows standard
maintenance methodology and supports test, busyout, release, and status commands.
H323-STN error log entries and recommended actions

Table 86: H323-STN error log entries
0 0 Any Any test station extension
1 Registration status inquiry WRN Off
test (#1372)
257 Signaling Path PING test WRN Off
(#1373)
513 Media Path PING test WRN Off
(#1374)
Notes:
1. Error type 1 reports the registration status of the endpoint. If Communication Manager
claims the endpoint is registered and receives keep-alive handshakes from the endpoint,
the test passes. If keep-alive handshaking fails, the test fails. If the user has intentionally
un-registered the station from the server, the station is basically an AWOH station and is
no longer being maintained, no tests will run for this station.
2. Error type 257 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 PROCR 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.
3. Error type 513 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 PROCR 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.
H323-STN demand test descriptions and error codes

Order of investigation Short test Long test D or
sequence sequence ND
Registration Status Inquiry Test 1372 on page 740 X X ND
Signaling Path PING Test 1373 on page 741 X X ND
INADS (INADS Link)
INADS (INADS Link)

INADS None test inads-link INADS link
The INADS link MO represents the software and communications link used by the switch to call an
alarm receiver. The purpose of the INADS Link MO is to:
• Check the communications link between the system and the alarm receiver.
• Verify that the alarm notification process works correctly.
To verify that alarms will be reported to the alarm receiver, either a centralized technician can
remotely test the process, or an on-site technician can test the connection either during an
installation or a subsequent service call.
Although the INADS Link MO never alarms, its errors are logged, and these errors are only logged
by entering test inads-link.
INADS demand test descriptions and error codes

The test inads-link command is different from other test commands:
• There is no long or short option.
• Resulting test does not have an associated test number.
When a user enters test inads-link, the system immediately returns either the Command
successfully completed or Command failed message.
INADS link test (no test number)

The INADS Link test attempts to call an alarm receiver (in the background) to verify the
communications link with the alarm receiver. When a user enters test inads-link, the system
immediately returns either a Command successfully completed or Command failed
message.
The Command successfully completed message means the switch will attempt to call the
alarm receiver in 2 minutes. This test runs even if Alarm Origination is disabled. The 2-minute
delay provides enough time for a remote technician to hang up the call and thus free up the alarm
receiver’s line so that the customer’s switch can call the alarm receiver back. The system displays
Command failed message if:
• A previously entered test inads-link is in progress.
• The system is attempting to report active alarms to the alarm receiver.
As any error conditions are encountered during the test, they are logged against the INADS Link
MO.
• If the initial test result was Command successfully completed, any logged error codes
would range from 1–9.
• If the initial test result was Command successfully completed, any logged error codes
would be 10 or 11.
An error is logged at the alarm receiver even if the call to the alarm receiver finally succeeds. The
alarm receiver’s software:
1. Recognizes this special test inads alarm type.
2. Automatically opens and closes a trouble ticket.
Within the trouble ticket, a field containing the description
TESTING
INADS
LINK
indicates that the ticket was initiated by test inads-link.

After entering the command, up to 9 minutes can elapse before the switch places the call and the
alarm receiver responds. To determine whether the call was successful, the error lLog should be
examined by using the inads category 10 minutes after successfully entering the command.
INADS test link - error code 1

Test result
0
Cause
A test call was successfully placed to the alarm receiver. No trouble was found.

Test result
0
Cause
Informative error indicating that alarm origination was disabled at the time of the test. The test runs
although alarm origination is disabled.
Proposed solution
1. Enable Alarm Origination via the Maintenance-Related System Parameters screen.
2. Repeat the test.

Test result
0
Cause
The alarm receiver’s connection is currently in use.
INADS (INADS Link)
Proposed solution
Wait for 10 minutes, and retry the command.

Test result
0
Cause
The alarm receiver did not answer the test call.
Proposed solution
1. Verify that the alarm receiver is up.
2. Verify the accuracy of the alarm receiver’s telephone number and the system’s product ID
using the Maintenance-Related System Parameters screen.
3. Enable alarm origination using the Maintenance-Related System Parameters screen.
4. Test the SYSAM (System Access Maintenance) by entering test maintenance a | b.
5. Retry the command.

Test result
0
Cause
The alarm receiver’s telephone number is not assigned.
Proposed solution
1. Assign the alarm receiver’s telephone number via the Maintenance-Related System
Parameters screen.

Test result
0
Cause
The alarm receiver did not return an acknowledgment for the test inads alarm message.
Proposed Solution
1. Verify the accuracy of the alarm receiver’s telephone number and the system’s product ID
via the Maintenance-Related System Parameters screen.
2. Verify that the alarm receiver is up.

Test result
0
Cause
The alarm receiver returned a negative acknowledgment for the TESTING INADS LINK
message.
Proposed solution
1. Verify that the product IDs match in the customer’s switch and the alarm receiver’s
database. Use the Maintenance-Related System Parameters screen to identify the product
ID of the switch.
2. Rerun the test.

Test result
0
Cause
Internal system error. System received an invalid return code.
Proposed solution
Retry the command at 1-minute intervals up to 5 times.

Test result
0
Cause
Internal system error.
Proposed solution

Test result
0
Cause
A test inads-link is already in progress.
ISDN-PLK (ISDN-PRI signaling link port)
Proposed solution
1. Wait for 10 minutes for the current command to finish.
2. Review the current command’s results by viewing the error log and selecting the category
inads-link.

Test result
0
Cause
The switch is trying to report alarms to the alarm receiver. The test cannot be run at this time.
Proposed solution
Wait for 10 minutes, and retry the command.
MO name in log Alarm Initial command to run 16 Full name of MO

level
ISDN-PLK Min test port location l ISDN-PRI signaling link port
16
This MO was formerly known as ISDN-LNK (ISDN-PRI Signaling Link Port).

Note:
See the figures in ISDN-SGR (ISDN-PRI Signaling Group) on page 398for an illustration of the
principles described below.
The ISDN-PRI interface uses out-of-band signaling as opposed to robbed-bit, in-band signaling
to transmit control messages between two endpoints. User information channels carry digitized
voice and digital data and are known as bearer channels (B-Channels). B-Channels 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.
Two types of DS1 interfaces exist:
16 Location refers to the port board location and port number. The port number is either 24 for 24-channel interfaces or 16
for 32-channel interfaces.
On 24-channel interfaces, the B-Channels may use any of the first 23 ports. The signaling link is
assigned to the 24th port.
On 32-channel interfaces, the DS1 ISDN Trunks (B-Channels) may use any of the ports 1 to 15
and 17-31. The signaling link is assigned to the 16th port. The 32nd channel (port 0) is used for
framing.
In NFAS configurations, the 16th or 24th ports on some of the DS1 circuit packs may be used for
B-Channels. Refer to ISDN-SGR (ISDN-PRI Signaling Group) on page 398 for further details.
A problem with the ISDN-PLK will affect every associated B-Channel since no call control
information can be conveyed to the far-end switch or terminal adapter. Stable calls may remain
operational, but no new calls can be placed. In turn, the ISDN-PLK depends on the DS1 Interface
Media Module that provides the link to the processor.
If there are problems with the ISDN-PLK, investigate MG-DS1 (DS1 Interface Media Module) on
page 436 for systems supporting gateways.
ISDN-PLK error log entries and recommended actions
Table 87: ISDN-PLK error log entries
Error AUX Associated test Alarm On/off Command to resolve the error
type Data level board
0 0 Any Any Any test port location 1
busyout port release port location 1
18 0 WRN Off
location 1
130 WRN On test port location 1
1537 46210 WRN Off
1793 test board location l
3585 46222 MIN On
3841 46211
3842 46223
3843 Signaling Port LAN test port location1l
Loopback (#939)
1 location is 24 for 24-channel interfaces and 16 for 32-channel interfaces.

Note:
procedures.
2. Error type 18: The D-Channel is demand busied out by command. No calls can be
made over this D-Channel.
3. Error type 130: The media module has been removed or has been insane for more
than 11 minutes. To clear the error, reinsert or replace the media module.
4. Error type 1537: 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. Enter list measurements ds1-log for
the UDS1 TN464 DS1 Media Module where the D-channel resides. If MG-DS1 is
reporting errors, the DS1 facility has experienced transmission problems that could
have caused the ISDN-PLK to report a Link Error.
If MG-DS1 is not reporting errors, execute the long test sequence for the D-Channel.
Investigate any errors. If there are none, execute a long test sequence for DS1 Media
Module (MG-DS1). Investigate any errors.
If no errors could be found by testing, the Link Error is probably not affecting service.
However if this Link Error continues to be logged, follow normal escalation procedures.
5. Error type 1793: DS1 Interface Media Module is out of service. Look for and resolve
MG-DS1 errors in the hardware error log.
6. Error type 3585: Transmit FIFO overflow error. The media module is having problems
transmitting data to the packet bus, thus affecting the conveyance of signaling
information over the D-Channel. Specifically, this error occurs when the packet bus
transmit buffers overflow. This condition probably indicates a hardware problem.
The actual alarming level will depend on the options chosen via the set options
command. ISDN-PRI Signaling Link port alarms are treated as Station alarms, and
their default alarming option is to downgrade every alarm to Warning. The value
shown in the preceding table indicates the normal, unfiltered case option yon the set
options screen.
7. Error type 3841: Bad DLCI error. This error occurs when a LAPD frame is received
across the DS1 facility that contains a DLCI that 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.
8. Error type 3842: Receive FIFO overflow error. This error occurs when the media
module detects an overflow of its receive buffers. If it occurs frequently, it may
indicate a LAPD parameter mismatch between the two endpoints of a packet-switched
connection. LAPD should be able to recover from this problem, but it may degrade the
performance of the LAN bus. Maintenance will not start any testing or generate any
alarms in response to this error.
9. Error type 3843: The Signaling Port LAN Loopback test (#939) failed. Run the long test
sequence and note the results of the Signaling Port LAN Loopback Test 939.
ISDN-PLK demand test descriptions and error codes
The command to test the ISDN-PLK MO is test port location where location is the
port board location and either 24 for 24-channel interfaces or 16 for 32-channel interfaces. For
example, test port is 8E0524.

Signaling Link Board Check 643 on page 682 X X ND
ISDN-SGR (ISDN-PRI Signaling Group)

MO name in Alarm Initial command to run 17 Full name of MO
log level
ISDN-SGR MIN test signaling-group grp# ISDN-PRI Signaling Group
WRN
17
An ISDN-PRI Signaling Group is a collection of B-Channels for which a given ISDN-PRI Signaling
Channel Port (D-channel) carries signaling information. B-Channels carry voice or data and can
be assigned to DS1 ISDN trunks (ISDN-TRK) or PRI endpoint ports (PE-BCHL).
Note:
Throughout this discussion, the term B-Channel refers to an ISDN-TRK or PE-BCHL,
depending on the application under investigation.
The following media modules are supported in the implementation of ISDN-PRI:
Media module Channel types Interface
MM710 B- and D-Channels 24 or 32 channel
These are two types of DS1 interfaces:

The following discussion describes 24-channel interface signaling groups. The 32-channel
interface works the same way, except that only port number 16 is used for signaling instead of
port number 24. Ports 1 through 15 and 17 through 31 are used for B-Channels. The 32nd channel
(port 0) is always used for framing.
ISDN-PRI D-channel signaling can be combined with a group of B-Channels in three basic ways:
• Facility-Associated Signaling (FAS)
• Non-Facility-Associated Signaling (NFAS)
• Backup NFAS signaling
In a FAS signaling group, the 24th port of the DS1 Interface Media Module carries D-channel
signaling for up to 23 B-Channel ports on the same media module.
17 grp# is the signaling group number (1–166); the test sequence can be either short or long.
In an NFAS signaling group, the 24th port of one DS1 Interface Media Module can carry D-channel
signaling for B-Channels on several other DS1 Media Modules. The 24th port on the other media
modules can be used as a B-Channel. A D-Channel in an NFAS group can signal for B channels
on a total of 20 DS1 media modules.
D-channel backup provides increased reliability, which is highly desirable since NFAS permits a
D-Channel to signal for many more B-Channels. NFAS allows the administration of a backup
D-Channel that remains in a standby state until the active D-Channel goes down. If so, the backup
D-Channel takes over and provides signaling for every B channel in the signaling group.
The operation of the entire ISDN-PRI signaling group depends on several other entities:
• The ISDN-PRI signaling channel ports, the DS1 Interface Media Module, on which the D-
Channels reside, and the system link that is carried over the packet bus to the processor.
When there are problems with the ISDN-PRI signaling group, also investigate ISDN-PLK (ISDN-
PRI Signaling Link Port) on page 395, MG-DS1 (DS1 Interface Media Module) on page 436,
SYS-LINK (System Links) on page 512.
ISDN-SGR error log entries and recommended actions

Table 88: ISDN-SGR Error Log Entries
Error Aux Associated test Alarm On/Off Command to resolve the error
1 Any
257 Any test signaling-group grp#
513 Any test signaling-group grp#
769 Any Primary Signaling test signaling-group grp#
Link Hardware
Check (#636)
1025 Any Secondary Signaling test signaling-group grp#
Link Hardware
Check (#639)
1793 Any Layer 2 Status Test WRN OFF test signaling-group grp#
(#647)
2049 Any Layer 2 Status Test WRN OFF test signaling-group grp#
(#647)
2305 Any Remote Layer 3 MIN OFF test signaling-group grp#
Query (#637)
3585 Port
number
3842 – Port
3942 number
Notes:
procedures.
2. Error type 1: 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 present, no action is required. If layer-3 communication is down,
there should be indications in the screen of alarms and errors for link components. Check
for other errors against ISDN-SGR, ISDN-TRK, and other hardware components on the
link.
There is no test to clear these errors. An error counter is decremented by 1 every 15
minutes, and the error eventually will be cleared by the system.
3. Error type 257: 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. Check the
results of the Primary Signaling Link Hardware Check 636 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
this with status signaling-group grp#.
4. Error type 513: 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. Note the results of the Secondary Signaling Link Hardware
Check 639. 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. You
can verify this using status signaling-group grp#.
5. Error type 1793: The Layer 2 Query Test failed for the primary signaling channel. See
Layer 2 Status Query Test 647.
6. Error type 2049: The Layer 2 Query Test failed for the secondary signaling channel. See
Layer 2 Status Query Test 647.
7. Error type 2305: The Remote Layer 3 Query 637 failed. A specific message was sent to
the far-end switch, and it did not respond within the time allowed. Investigate elements of
the ISDN PRI D-Channel(s) ISDN-PLK (ISDN-PRI Signaling Link Port) on page 395 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 the 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.
8. 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 1 on the DS1 Administration screen).
However, these messages are used only for NFAS D-channel backup signaling that 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 at the far-end switch.
9. Error types 3842 - 3942: These Error Types 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 recommended action 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.
The table on page 401 provides more information.
Table 89: Descriptions and Recommendations for Error Types 3842-3942

code
3842 A request has been The equipment sending this cause event does not recognize
made to use a transit the transit network.
network or common
carrier that cannot be
accessed.
was reported.
b. Check every routing pattern containing this trunk group for
validity of interexchange carriers requested (IXC field).
3843 No route to destination.
Request received to
route call through a
transit network that
is recognized but not
allowed to carry the call
or not able to serve the
destination.
Table continues…

code
3846 The far-end switch has This could indicate an administration problem (for example, the
indicated that the B- local switch and the far-end switch have different B channels
Channel (trunk) is not administered), or could reflect the occurrence of a normal race
acceptable for use in condition (for example, the local switch has requested use of a
the call for which it was B-Channel that the far-end switch had just reserved for use on
requested. another call).
was reported.
b. Enter status trunk for the indicated trunk. Refer
to the DS1 ISDN Trunk Service States and ISDN-PRI
Trunk Service States sections of ISDN-TRK for recovery
suggestions.
3858 Similar to Error Type Follow same recommendations as for Error Type 1.
1. The switch sent
an ISDN message to
the far-end switch or
terminal adapter that did
not respond in the time
allowed.
3878 The far-end switch Network is out of order.
has indicated that
the network is not
functioning correctly and
was reported.
that the condition may
last a relatively long b. Consult with the network provider to determine the nature
period of time. For and expected duration of the out of service condition.
example, immediately
c. Consider modifying every routing pattern containing this
re-attempting the call
trunk group to route calls around the network that is out of
may not be successful.
service.
Table continues…

code
3890 A request to use This could be a local administration problem only, or a
a network service mismatch between the local administration and that of the
(e.g., SDN) has been network provider.
denied. Administration
somewhere on the
network has indicated
was reported.
that the requested
service has not been b. Display the trunk group form: If the trunk group is
subscribed to or Call-by-Call (Service Type is cbc), check every routing
purchased for this trunk. pattern form 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.
c. If local administration is 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 Protocol detail; may If customer is complaining of unexpected intercept tones when
offer a clue if accessing ISDN trunks or PRI endpoints and no other cause
customer is having can be found, escalate the problem and provide the next tier
ISDN calls denied with with this Error Log information.
tone.
3894 Protocol detail; may First, eliminate any transitory state mismatch problems by
offer a clue if entering test port location for the trunk port shown
customer is having in the Aux Data field. Service State Audit Test 256 is the
ISDN calls denied with important test in the sequence. If this passes satisfactorily, yet
an unexpected intercept the customer continues to complain of unexpected intercept
tone. 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.
3902 FRANCE ONLY: Service
not authorized.
3903 Service or option not
available, unspecified.
This cause reports a
“service or option not
available” event only
when no other cause in
the “service or option not
available” class applies.
Table continues…

code
customer is having can be found, escalate the problem and provide the next tier
tone.
customer is having can be found, escalate to the problem and provide the next tier
tone.
3909 A request to use a Follow the previous recommendation for Error Type 3890.
network service has
been made, but the
network has rejected
the request because the
requested service is not
implemented.
3910 Only restricted digital BC
available.
3919 Service or option
not implemented,
unspecified. Used when
no other cause in this
class applies.
3928 A call was denied This error might be helpful as a clue if the customer complains
because of a basic of receiving unexpected intercept tone after accessing ISDN
incompatibility existed trunks or PRI endpoints. Determine the trunk group from the
between the type of call circuit pack or media module and port number in the Aux Data
and either the facilities field and then check the BCC fields of the pertinent routing
selected by the routing patterns. Also, investigate whether or not the calling and called
pattern or the called endpoints are compatible. For example, some ISDN switches
user. may not allow a voice station to call a data extension.
3942 Timer expiry: T310 time-
out, no answer to CALL
PROCEEDING.
ISDN-SGR demand test descriptions and error codes
ISDN-TRK (DS1 ISDN Trunk)

Primary Signaling Link Hardware Check 636 on page 675 X X ND
Secondary Signaling Link Hardware Check 639 on page 680 X X ND
Layer 2 Status Query Test 647 on page 684 X X ND
Remote Layer 3 Query 637 on page 677 X X ND

ISDN-TRK MAJ 18 test port location long DS1 ISDN Trunk
MIN
18
Note:
parameter settings on the far end. See Administering Avaya Aura® Communication Manager.
Refer to your Avaya representative for the correct settings for administrable timers and other
parameters on a country-by-country basis.
For additional repair information, see also DS1 Interface Media Module (MG-DS1) on page 436 for
Media Module ports.
A DS1 ISDN trunk is a 64-kbps bearer channel used to transmit digitized voice or data traffic.
These trunks, or B-Channels, use a separate channel, the D-Channel for call-control signaling.
This mode of operation is known as out-of-band signaling, as opposed to in-band robbed-bit
signaling, in which signaling is carried in the same channel as the voice or data traffic. One D-
Channel, or ISDN signaling link (ISDN-PLK), carries signaling messages for several B-Channels,
forming an ISDN signaling group (ISDN-SGR).
A B-Channel is a port on a DS1 Interface Media Module.
Two types of DS1 interfaces exist:
On 24-channel interfaces, any of the first 23 ports on the DS1 circuit packs or media modules
can be a B-Channel. On DS1 Media Module, the 24th port may be used as a B-Channel or as a
18 A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by the set options.
D-Channel depending on the type of ISDN-PRI signaling group (FAS or NFAS) implemented on
the media module. For more details, see ISDN-PRI Signaling Group (ISDN-SGR ) on page 398.
On 32-channel interfaces, any of ports 1 – 15 and 17 – 31 on the DS1 interface media module 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 (FAS or NFAS) to which it belongs. For more details, see ISDN-
PRI Signaling Group (ISDN-SGR) on page 398 and DS1 Interface Media Module (MG-DS1) on
page 436.
For interfaces using country protocol 1 on the DS1 media module administration form (including
US), the signaling protocol used for the maintenance of the B-Channel is defined by the Avaya
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 far-end and near-end components. The service
state is initialized to Out-of-Service/Far-End, and an attempt is made to negotiate it to In-Service.
Note:
The service state of a particular DS1 ISDN Trunk B-Channel can be displayed by entering
status trunk grp#/mem# on the system access terminal.
When 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.
Alarms 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 the status trunk grp#/mem# command
to determine the exact state. Other alarms can be diagnosed by using the short and/or long test
sequences.
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 will be placed in the Maintenance/Far-End service state.
As a port on a DS1 Media Module (MG-DS1), 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 MOs. In turn, the ISDN D-Channel depends on the packet bus (PKT-BUS) for
transmission through the system. Keep this hierarchy of dependencies in mind when diagnosing
problems.
DS1 ISDN Trunk Service States

The status trunk command shows the following possible service states for ISDN trunks.
• 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. 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. The trunk is unusable for incoming and
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 the NPE Crosstalk Test fails or when the trunk is busied
out by the 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 the system technician.
• Maintenance/Far-End (MTC/FE)
This state is reached when the far end does not respond after a certain amount of time
to messages sent over the signaling link for a particular trunk. 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 channel (ISDN-PLK) is busied out by
the system technician. The trunk (B-Channel) is also temporarily in this state if the system
technician enters test trunk grp#/mem# long. This command executes the ISDN-PRI
test call. This test changes 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. In this state, the B-Channel is not
usable for new incoming or outgoing calls.
• Pending States
In addition to one of the previous components, the service state may have a pending
component, indicating that the switch is waiting for a reply from the far end. These service
states remain in effect until either a response is received or the allotted waiting time expires.
- Pending-in-Service
The near end is awaiting a far-end response to a B-Channel maintenance message
requesting that a B-Channel 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.
- Pending-Maintenance
This state is supported only by systems using country protocol 1 (including US). The near
end is awaiting a far-end response to a maintenance message requesting that a B-Channel
be transitioned to the maintenance service state. 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
The in-service state also has a call activity component.
- Active
A call is connected over the B-Channel. For example, in service active.
- Idle
There is no call currently on the B-Channel. For example, in service .
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.
Figure 4: Common Progressions in Service States
ISDN-PRI Trunk Service States

Use status trunk grp#/mem# to see DS1 ISDN Trunk service states.
Note:
Refer to Maintenance Procedures for Avaya Aura® Communication Manager, Branch
Gateways and Servers for a layered approach to processing ISDN-PRI problems.
ISDN-PRI service state - Out-of-service/NE

Alarm
WRN
Cause
Trunk is demand busied out.
Proposed Solution
Enter release trunk grp#/mem#.
ISDN-PRI service state - No service state 1

Alarm
MIN
Cause
NPE Crosstalk test (#6) failed.
Proposed Solution
Replace DS1 media module.

Alarm
None
Cause
1. DS1 Media Module lost its signal.
Proposed Solution
Check if the DS1 Media Module, or cable is removed. Check if the far-end switch is restarting.
Check the media module using procedures in DS1-BD or MG-DS1.
ISDN-PRI service state - Out-of-service/FE

Alarm
WRN
Cause
Unadministered far end.
Proposed Solution
Administer corresponding trunk on far-end switch.

Alarm
WRN
Cause
The far-end trunk is busied out.
Proposed Solution
Check the status of the far-end switch.
ISDN-PRI service state - Pending-in-service/pending-maint

Alarm
None
Cause
Maintenance message was sent and the switch is waiting up to 2 min. for a reply from the far end.
Proposed Solution
Wait 2 minutes and check service state after the pending state has cleared.
ISDN-PRI service state - Maint/NE

Alarm
None
Cause
ISDN test call in progress (test trunk long grp#/mem# long and status isdnpri-
testcall).
Proposed Solution
Wait several minutes for test to finish and check status again.

Alarm
None
Cause
System link has been busied out by command.
Proposed Solution
Check link status. Release link with release link lnk#.
ISDN-PRI service state - Maint/FE

Alarm
WRN
Cause
Signaling channel has been down for over 90 sec.
Proposed Solution
Consult ISDN-SGRP and/or ISDN-PLK. Far-end signaling channel may be busied out, or the
far-end switch may currently be restarting.

Alarm
WRN
Cause
Repeated failure of far end to respond to messages.
Proposed Solution
Maintenance software will periodically try to resend messages. You can speed the process with
test trunk grp#/mem# and/or test signaling-group sig-grp#.

Alarm
WRN
Cause
The far-end trunk is being tested.
Proposed Solution
Check status of the far-end switch. Wait for testing to finish.
ISDN-PRI service state - In-service

Alarm
None
Cause
Normal operating state.
ISDN-TRK error log entries and recommended actions

Table 90: ISDN-TRK Error Log Entries
Error type Aux Associated test Alarm On/Off Command to resolve the error
data level board
1 Any test port location
15 Any Port Audit and Update
Test (#36)
Table continues…
data level board
18 0 busyout trunk release trunk grp#/mem#
grp#/mem#
19 0
129 WRN OFF test port location
513 Any WRN OFF test port location
1025 0
1281 Any Conference Circuit Test MAJ ON test port location l r 4
(#7) MIN
WRN 1
1537 Any NPE Crosstalk Test (#6) MAJ ON test port location l r 3
MIN
WRN
3073 Any Service State Audit test port location
(#256)
3585 Any
3841 Any WRN OFF
1. Major or minor alarms may be downgraded to Warning alarms based on the value used in set
options.
Notes:
procedures.
2. Error type 1: 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, call will be torn down. You can use
status trunk grp#/mem# to determine the state of the trunk.
When running the short test sequence, note the results of the Call State Audit Test 257.
3. Error type 15: Software audit error and does not indicate a hardware malfunction. Run the
short test sequence, and investigate associated errors.
4. Error type 19: Possible protocol mismatch or far end may be out of service.
5. Error type 129: The far-end switch changed its ISDN service state to either out of service
or maintenance. This may be either a temporary condition due to far-end testing of that
trunk or a hardware problem with the trunk. Outgoing calls will not be allowed over the
trunk. To investigate the status of the trunk, enter status trunk grp#/mem#.
7. Error types 257 and 796: 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 status trunk grp#/mem# to determine the state of the trunk.
When running the short test sequence, note the results of the Service State Audit Test 256.
8. Error type 513: This trunk is not recognized by the far-end switch. Investigate the trunk
administration for both switches and make changes as necessary.
9. Error type 1025: An unexpected SERVICE or SERVICE ACK was received. Possibilities
include:
• Translations conflict.
• Protocol differences.
• Survivable Core Server may be using NI3 protocol, not currently implemented in
Communication Manager.
• B-Channel negotiation problem (glare).
10. Error type 1793: failure of the DS1 media module. When running the short test sequence,
the results of the Signaling Link State Audit Test 255 are important.
11. Error type 3073: Service State Audit Test 256 failed. 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. To investigate trunk status use status trunk
grp#/mem#.
12. Error type 3585: 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 dropped calls (cutoffs) are reported by users of the
ISDN-PRI trunks.
The meanings of Aux Data values are shown below; ignore any others.
Table 91: ISDN Trunk - Error 3585 Aux Data Values
Aux Cause
Data
0 A idle trunk received a restart.
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.
Table continues…
Aux Cause
Data
4, 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.
7,
8, 260,
263
1, A call that has not yet reached a ringing state was cleared unexpectedly by the far end
with an ISDN RESTART message.
3,
6,
9, 265
11, 12, A call that was in the process of clearing anyway has been cleared by the far end with
19, an ISDN RESTART message. If this condition occurs frequently, it may mean that the
531, far end is attempting to clear trunks that it thinks are in a hung state. The RESTART
267, message brings the trunk to an idle condition.
268
13. Error type 3841: 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 and far ends for this trunk that is affecting the end user that is, customer receives
unexpected intercept tones when accessing ISDN trunks. This may indicate that the ISDN
trunk is not administered at the far end.
The Aux field contains the physical name of the ISDN trunk in decimal. Using this decimal
name, verify that the far end has this trunk administered.
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 busyout the
ISDN trunk to take it out of the hunt group.
ISDN-TRK demand test descriptions and error code

Signaling Link State Audit Test 255 on page 620 X X ND
Service State Audit Test 256 on page 622 X X ND
Call State Audit Test 257 on page 626 X X ND
ISDN Test Call Test 258 on page 629 X ND
JNL-PRNT (Journal Printer Link)

level
JNL-PRNT MIN test journal wakeup-log Journal Printer Link
WRN
The maintenance strategies for Journal Printer Link (JNL-PRNT) and PMS Printer Link (PMS-
PRNT) are the same. Refer to PMS Printer Link (PMS-PRNT) on page 474 for more information.
LGATE-AJ (Ethernet ASAI Endpoint)

See BRI-SET, Various Adjuncts on page 321.
LIC-ERR (License Error Mode)

LIC-ERR MAJ test license License Error Mode
The LIC-ERR MO works with the NO-LIC MO to look for any errors and violations associated with
a License File. Once a License File error occurs, a LIC-ERR error is logged, an alarm is raised,
and the following SAT login message is displayed:
System Administration Will Be Blocked in Approximately XXX hours. Contact Your Service
Representative.
The License File is loaded onto a server during initialization of Communication Manager software,
restoration of translations, and periodically during normal operation. After initialization, a query is
made to WebLM, a license server plug-in that
• Reads the serial number in a License file.
• Compares this file’s serial number to a serial number in hardware.
• Compares the file’s serial number with a running software version.
If a match occurs, the Web License Generator (WebLM) that resides on a designated server in
the enterprise delivers a new feature mask, an information set that controls which features are
enabled or not on the Customer Options and Special Applications screens.
Entry into License Error mode starts a timer that, when expired, causes the system to enter
No-License mode (see the figure on page 417) .
Figure 5: License mode algorithm
LIC-ERR error log entries and recommended actions

Error type Aux Associated test Alarm On/Off Command to resolve the
data level board error
1 MAJ OFF See footnote1
Table continues…
Error type Aux Associated test Alarm On/Off Command to resolve the
data level board error
Note:
These Error Types can be cleared by installing the correct License File.
Notes:
1. Error type 1: The motherboard on which the serial number resides is not responding.
The reference is not responding, or its serial number does not match the one in the
License file, and the 30-day timer begins. When the 30-day timer expires, the system
enters No-License mode. For more information, see NO-LIC (No License) on page 447,
Error Type 1.
2. Error type 513: The license has expired, and the 30-day timer has started. When the
30-day timer expires, the system enters No-License mode. For more information, see
NO-LIC (No License) on page 447, Error Type 513.
3. Error type 769: Feature use exceeds limits if the license has expired and the 30-day timer
begins. When the timer expires, the system enters No-License mode
4. Error Type 770: 12-Party Conferences and DCS (Basic) cannot be enabled together.
5. Error type 1537: The License file is missing or corrupt. A countdown timer for a license
error starts only if the previous state was License-Normal.
6. Error type 1793: The current software version does not match the software version in the
License File, and the countdown timer has started. When the timer expires, the system
enters No License mode.
7. Error type 2305: The Offer Category in translation does not match the Offer Category in
the License File, and the countdown timer has started. When the timer expires, the system
enters No-License mode. For more information, see NO-LIC (No License) on page 447.
8. Error type 2561: The license server did not respond in time during the last attempted
License File audit.
9. Error type 2817: Timer response timed out.
10. Error type 3073: This Survivable Remote Server (the one reporting the LIC-ERR) is active
because one or more gateways have registered with it. Follow standard practices to repair
the primary server or servers or control network.
11. Error type 3074: This Survivable Core Server is controlling one or more port networks.
Follow standard practices to repair the Main server, servers, or control network.
12. Error type 3329: Platform type/offer type mismatch.

13. Error type 3335: Platform type does not match the hardware.
14. Error type 3391: Platform type does not match server configuration.
15. Error type 3584: Invalid Allocation License.
16. Error type 3585: The Allocation License has an ESID/SID/MID mismatch.
17. Error type 3586: Allocation License expired.
18. Error type 3841: Application not found.
LIC-ERR demand test description and error codes

License file test - Error code 1
Test result
FAIL
Cause
The system is in License-Error mode.
Proposed Solution
See Troubleshooting License File errors.
Test result
FAIL
The system is in No-License mode.
Proposed Solution
See NO-LIC (No License).
Test result
ABORT
Cause
Within the first 30 minutes after a system restart, the system cannot test the License file.
Proposed Solution
1. Enter display initcauses to find out when the system last restarted.
2. Wait for the remaining time plus 2 minutes, and retry the test.
License file test - No error code
Test result
PASS
Cause
The system is in License-Normal mode.
License File errors
The License file enables the switch’s software category, release, features, and capacities. License
Files are created using SAP order information and/or current customer configuration information.
Without a valid license installed or with a mismatched license, the system:
1. Generates a major alarm.
2. Starts a 30-day countdown timer and call processing continues.
The License file requires a serial number from the reference IPSI circuit pack or gateway
motherboard.
The License file includes a license serial identification number that is matched against the
hardware in the system and information about the Communication Manager software version and
Call Center features, Offer Category, and capacities. Once installed or initialized, every hour, the
system compares these parameters to determine the following system status:
• License-Normal mode
- License file was installed successfully
- Feature use is within prescribed limits
- License file serial number matches the serial number of the reference IPSI
• License-Error mode
- The License file serial number reference source is not responding, or the serial number
does not match the hardware
- Communication Manager software versions do not match
- Feature use exceeded prescribed limits
- License expired
- After a system had a valid license, the License file is missing or corrupt
Note:
System resets do not reset the 30-day timer. If a system in License-Error mode is reset
and the license error remains, the timer picks up the countdown where it left off.
To clear LIC-ERR alarms, the License file must match the switch hardware and administered
parameters.
• No-License mode
- System software versions do not match.
- The License file is missing or could not be installed.
- Offer categories do not match.
- A condition that caused the system to enter License-Error mode is not corrected or
resolved, and the countdown timer expired.
- The switch returns to License-Normal mode when every license error is cleared.
Login Warning Messages
Anyone logging onto the System Administration Terminal (SAT) when the system is in License-
Error or No-License mode, receives a warning message stating the system’s License mode,
depending on the conditions.
License mode License-Normal
Cause
No mismatches between license and hardware. Stable running condition.
License mode License-Error
Cause
Warning mode: Communication Manager supported, 30-day countdown timer begins.
Proposed Solution
If you log in to the server through the SAT, a message reads: System Administration Will Be
Blocked in Approximately XXX hours. Contact Your Service Representative. Communication
Manager functions normally for XXX hours, at which time the system goes into No-License mode.
One of the following conditions is present:
• Serial number reference source not responding.
• The License file expired.
• Feature use does not match the License file.
License mode No-License
Cause
Warning period has expired.
If you log in to the server through the SAT, a message reads: System Administration Is Blocked.
Contact Your Service Representative Immediately.
One of the following conditions is present:
• No License file is installed in the system.
• The License-Error timer expired.
Initialization and Periodic Checking
Within the License file is the feature mask, an information set that controls which features
are enabled or not on the Customer Options and Special Applications screens. Each of the
approximately 150 feature mask entries is one of the following three types:
• Type I: features with a simple on or off state, for example, DCS Call Coverage.
• Type II: features with an alphanumeric setting value associated with them, for example,
Logged-in ACD Agents.
• Type III: includes the product ID, for example, license serial identification number, release
number, and capacities.
Type III features cannot be changed by any login, for example, applies to IP Telephones, IP
Softphones, and IP Agent.
Table 92: License error messages
Name of the Error message Description

mode displayed
No-License License File is Missing License could not be decrypted.
or Corrupted
Checksum did not match, data possibly lost.
Mismatched settings:
- Offer Category
- Version
- Call Center Release
- Model
Min. and Max. values of “* and # in vector collect step” do
not match the License file.
IP product defined in translations but not defined in the
License file.
No-License The License has The License has expired.
Expired
No-License Software Version The current software version does not match the software
Mismatch version in the License file.
No-License Offer Category The Offer Category in translation does not match the Offer
Mismatch Category in the License file.
License-Error Golden IPSI Not The reference source’s serial number does not match the
Responding G430/ serial number in the License file, or the reference source
G450 Motherboard Not is not responding.
Responding
License-Error Feature Usage The value of the Used field for any TYPE II or TYPE III
Exceeds Limits field on the Customer Options forms pages 1, 5, 6, and 9
is greater than the value of the field.
To identify which of these TYPE II and TYPE III features
is causing the error more quickly, compare the Used field
with the value of the field itself in the License file value.
Before usage is checked, if the value of the field is not
between the upper and lower values in the License file,
the value of the field is changed in translation to the lower
value in the License file.
LGATE-PT (Ethernet Adjunct Port)
LGATE-PT (Ethernet Adjunct Port)

See BRI-PORT (ISDN-BRI Port) on page 316.
LOG-SVN (Login Security Violation)

LOG-SVN MAJ enable login loginID1 Login Security Violation
1. Where loginID is the Avayaservices login ID for which the security violation was detected.
The Alt Name field 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 an Avaya services
login ID and that login ID has been disabled as a result of detection 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 the Administering Avaya Aura® Communication Manager, for information about
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.
LOG-SVN error log entries and recommended actions

Table 93: LOG-SVN error log entries
Error Aux Associated test Alarm On or Off Command to resolve the error
1–15 None None Major OFF enable login loginID
General Information about log-svn error log entries:

1. The number (1–15), displayed in the Error Type field, corresponds to the location of the
login in the internal login data structure.
2. The Alt Name field on the alarm report indicates the login ID associated with the security
violation and major alarm.
3. These errors/alarms are associated with a number of failed attempts to access the system
management/maintenance interface using an Avaya services login ID that meet or exceed
the customer administered threshold parameters. The associated alarm is immediately
raised as a major alarm.
4. The affected login ID will be disabled as a result of detection of the security violation,
unless it is the system’s last enabled INADS-type login. The provision to disable a login ID
following detection of a security violation involving that login ID is administrable on a login

ID basis.
5. Use enable login to enable a login that has been disabled, and to retire any login
security violation alarms associated with the login ID.
6. To use enable login to enable a login and/or retire alarms, use a login ID with greater
service level hierarchy permissions.
7. Access to enable login is controlled through the Administer Permissions field on the
Command Permission Categories screen. Set the Administer Permissions field to y to
access enable login.
8. The Port alarm report field identifies the port where the final invalid login attempt, involving
the alarmed login ID, was detected.
9. The Svc State alarm 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 will be set to IN.
10. 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 Avaya services automatic
login software, to something as insidious as a hacker attempting to gain access to the
switch system management interface.
Prior to retiring an SVN alarm and enabling the associated login ID, use monitor security-
violations login 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.
Use list logins to see status information about logins on the system. If a login has been
disabled as a result of a security violation, the status is svn-disabled.
Retiring an SVN Alarm

About this task
Procedure
Procedure
Enter enable login loginID.
The login ID associated with that alarm is displayed in the Alt Name field of the alarm report and
the alarm is retired.
MED-GTWY (MEDIA GATEWAY)
MED-GTWY (MEDIA GATEWAY)

MO name in log Alarm Level Initial command to run Full name of MO
MED-GTWY MAJ test media-gateway location Media Gateway
MIN
WRN
The MED-GTWY maintenance object monitors the H.248 link to the gateway. It logs errors when
there are H.248 link problems or when hyperactive H.248 link bounce occurs.
MED-GTWY error log entries and recommended actions

Table 94: MED-GTWY error log entries

type data level Off
board
1 Alarm OFF
levelMA
J
257 MAJ OFF
513 MAJ ON
769 MIN OFF
1025 WRN OFF
1281 Gateway MIN OFF
Hyperactive Audit
1659
3585 The Media Gateway MIN ON
perce VoIP Capacity 1718
ntage
of
media
resour
ce out
of
servic
e due
to
hardw
are
faults.
Table continues…

type data level Off
board
3329 The WRN ON
perce
ntage
of
media
resour
ces
that
have
been
busied
out.
Note:
1. Error type 1: failure of the H.248 link keep alive messages between the server and the
Gateway. This is an indication that the LAN or the platform is down.
2. Error type 257: If the server is a Survivable Remote Server, at least one gateway is
registered with the Survivable Remote Server.
3. Error type 513: there is a problem on the gateway. Log on to the gateway and check
the error log for problems using the MGP CLI.
4. Error type 769: is a transient error, indicating that the link has unregistered with the
Gateway. If the Gateway re-registers, the alarm is resolved. If the Link Loss Delay
Timer (LLDT) on the primary server expires, Error type 1 is logged.
5. Error type 1025: Due to high traffic, the gateway socket control process turned
off board and port periodic maintenance. When traffic levels decline, periodic
maintenance will be turned on again and the alarm resolved.
6. Error type 1281: This error indicates that there has been a repetitive sequence of
unregistration and subsequent re-registration of a gateway from a call server. The call
server may be a primary server, a Survivable Remote Server, or a Survivable Core
Server. This error and alarm can only be generated if Enable Detection and Alarms
for Hyperactive Media Gateway Registration has been enabled on the system-
parameters ip-options form. This alarm is most likely caused by an IP network problem
which causes the gateway to unregister and re-register multiple times to a server
within an interval that is less than the link bounce time. If a Survivable Remote Server
is present, and if the interval is greater than the link bounce time, the gateway and
affected IP phones would most likely fail over to the Survivable Remote Server, and
this MED-GTWY alarm would not be generated. The disable nr-registration or
disable nr-registration or network-region commands can be used to deny
registration of gateways and IP phones from a server to cause the gateways and IP
phones to search for an alternate server. The alarm is resolved if there is no activity for
15 minutes. See NR-REG (Network Region Registrations) on page 451.
7. Error type 3329: This error indicates that the VoIP media resources on the media
gateway have been busied out on demand. To resolve the alarm, log on to the media
gateway and check the status of the VoIP resources.
MG-ANA (Analog Media Module)
8. Error type 3585: This error indicates no VoIP or reduced VoIP capacity. To resolve the
alarm, log on to the media gateway and check the status of the VoIP resources.
MED-GTWY demand test descriptions and error codes

Order of investigation Short test Long test D or ND 1
sequence sequence
Link State Audit Test 1527 on page 761 X X ND
Media Gateway Hyperactivity Audit Test 1659 on page 766 X X ND
Media Gateway VoIP Capacity Test 1718 on page 772 X X ND
MG-ANA (Analog Media Module)

MG-ANA MIN test board location long Analog Media Module
The MG-ANA maintenance strategy supports the following:

• MM711 (8 port analog line media module)
• MM714 (4 analog line ports + 4 analog trunk ports media module)
• MM716 (24 port analog media module)
• VMM_ANA (1 analog trunk port + 2 analog line virtual ports)
• VMM_42ANA (4 analog trunk ports + 2 analog line virtual ports)
MG-ANA error log entries and recommended actions
Table 95: MG-ANA Error Log Entries
0 0 Any Any Any test board location
1 0 Board removed or SAKI MIN ON
Sanity Failure (#53)
18 0 busyout board location WRN OFF release board location
23 0 WRN OFF
125 MIN ON
Table continues…
257 65535 Control Channel Looparound MIN ON test board location r 20
Test (#52)
513 Any Angel Background Error MIN ON test board location
769 Program Logic Failure
1025 4363 NPE Audit Test (#50)
1281 Ringing Application Test
(#51)
1538 Any Hyperactive Angel WRN ON
MIN
3840 Any Inconsistent Downlink
Message
Notes:
procedures.
2. Error type 1: The media module stopped functioning or has been physically removed from
the system. The alarm is logged approximately 11 minutes after removal of the board or
failure of the SAKI Sanity Test (#53). Check for the physical presence of the media module
in the slot indicated by the alarm. If the board is absent, insert one of the proper type. If the
media module is present and its red LED is lit, see LED alarms without Alarm Log entry or
with Error Type 1 in LED Descriptions for Avaya Aura® Communication Manager Hardware
Components.
3. Error type 18: The media module has been busied out. Release the media module using
release board location long.
4. Error type 23: The media module has been logically administered but not physically
installed. The alarm should clear when the media module is installed.
If the media module is already installed:
a. Run test board location long and look at any test failures or Error Codes
generated.
b. If the test does not clear error 23, then execute reset board location and run
the long test again.
c. If the reset/test does not clear error 23, replace the media module.
5. Error type 125: The media module that is physically installed in the slot does not match the
type that is administered for that slot. Do one of the following:
• Remove the incorrect media module and replace it with one of the type that is
administered for that slot.
• Use change media-module to re-administer the slot so that it matches the board that
is installed, then enter reset board location.
MG-ANN (Media Gateway Announcement Module)
6. Error type 257: Transient communication problems between the switch and this media
module. Execute test board location and refer to the repair procedures for the
Control Channel Looparound Test 52.
7. Error type 513: There is an on-board hardware failure. The system will continuously test
the media module and report the results approximately every 10 minutes. If the hardware
problem is resolved, the alarm will clear in approximately 30 minutes. If the alarm does
NOT clear in 30 minutes, then the media module should be replaced.
8. Error type 769: This error can be ignored, but look for other errors on this media module.
9. Error type 1025: This error is not service-affecting and no action is required.
11. Error type 1538: The hyperactive media module is out-of-service and may exhibit one or
more of the following symptoms:
a. The tests such as Test #51 and/or Test #220 are aborting with Error Code 2000.
b. The tests run on the ports of this media module are returning NO-BOARD.
c. A busyout/release of the media module has no effect on test results.
d. A list configuration command shows that the media module and ports are
properly installed.
If this error happens again within 15 minutes, replace the media module.
MG-ANA demand test descriptions and error codes
Order of investigation Short test Long test Reset D/ND
sequence sequence board
sequence
Control Channel Looparound Test 52 on X X ND
page 586
SAKI Sanity Test 53 on page 588 X D
MG-ANN (Media Gateway Announcement Module)

MG-ANN MIN test board Media Gateway
Announcement
MG-ANN WRN test board Media Gateway
Announcement
MG-ANN error log entries

Table 96: MG–ANN Error Log Entries
Error Aux Associated test Alarm On/Off Test to clear value

18 0 Busyout board WRN ON release board
257 Any Test # 52 MIN ON test board
2561 (a) Any Test # 1683 MIN OFF test board
2562 (b) Any Test # 1683 MIN OFF test board
2564 (c) Any Test # 1683 MIN OFF test board
2563 Any Test # 1683 MIN OFF test board
2567 (d) Any Test # 1683 MIN OFF test board
2592 (e) Any MIN OFF
Notes:
release board location.
2. Error type 257: Transient communication problems between the switch and this circuit pack
or media module. Execute test board location and refer to the repair procedures for the
Control Channel Looparound Test (#52).
3. Error type 2561: During the last attempted License File audit, the license server did not
respond in time.
4. Error type 2562: Retry Failure error. This error is only logged. 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.
5. Error type 2563: The 2563 is a combination of 2561 and 2562.
8. Error type 2567: The 2567 is a combination of all the preceding errors. This error indicates
that the gateway registered and an enable file systems message was sent to the
gateway to enable the file system with Compact Flash. The gateway refused the message
because there is insufficient RAM to support the Compact Flash.
MG-ANN (Voice Announcements)
MG-ANN (Voice Announcements)

The MG-ANN (Voice Announcements) maintenance object provides per board announcement
storage time of up to 20 minutes (15 playback ports and 1 recording port that can also be used
as a playback port), and allows for announcement file portability via LAN connectivity. MG-ANN
also allows for LAN backup and restore of announcement files and the use of customer provided
waveform (.WAV) files.
Note:
S8300E does not support standard port networks and TN type boards.
Communication Manager supports the MG-ANN by using a virtual board concept to allow for
board insertion and maintenance testing. The virtual slot location is V9.
Announcement times and ports vary according to the gateway type.
Table 97: Gateway Announcement Times/Ports
Gateway Ports Minutes

G430 7 15
G450 63/1 = 64 45/240
MG-BRI (BRI Trunk Media Module)

MG-BRI MIN test board location BRI Trunk Media Module
The following is a list of supported BRI Media Modules:

• MM720 (8-port 4-wire BRI Trunk/Line Media Module)
• MM722 (2-port 4-wire BRI Trunk Media Module)
• TIM521 (4-port BRI Trunk Media Module in a Juniper Gateway)
• VMM_2BRI (2 port trunk-side integrated BRI Media Module)
MG-BRI error log entries and recommended actions

Table 98: MG-BRI Error Log Entries
data level board
0 0 Any Any test board location
1 Any Sanity Failure MIN ON
Table continues…
data level board
18 Media Module is release board location
busied out
257 65535 Control Channel MIN ON test board location r 20
Looparound Test
(#52)
513 4352 to Angel Background ON test board location
4357 Errors
769 4358 Program Logic
Error
1291 4359 Clear Error MIN ON
Counters (#270)
3586 MIN OFF
3840 4096 to Inconsistent
4101 Downlink Message
3842 46095 Receive FIFO
Overflow
3843 46097 Bad LAN
Translation RAM
Notes:
sequence. Refer to each test’s description, and follow its procedures.
2. Error type 1: The media module stopped functioning or is physically removed from the
system. This alarm is logged approximately 11 minutes after removing the media module
and/or the SAKI Sanity Test (#53) fails. If the media module is not in the system, insert a
media module in the same slot as the error indicates. See note ( f on page 433).
3. Error type 257: there are transient communication problems between the switch and this
media module. Execute the test board location command and refer to the repair
procedures for the Control Channel Looparound Test 52.
4. Error type 513: On-board hardware failure. Aux data values correspond to the following
detected errors:
Aux Value Detected Error
4352 External RAM error
4353 Internal RAM error
4355 ROM checksum error
4357 Message Corruption error
Reset the media module with the busyout board location and reset board
location commands. When reset, the media module 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 media module to lock-up and appear insane to the system.
MG-DCP (Digital Line Media Module)
5. Error type 769: The media module detects a program logic error. No action is required.
However, this error can lead to other errors against this media module.
6. Error Type 1291: The BRI Media Module detected a parity error while accessing
its dynamic RAM which stores the board’s translation information and downloadable
application firmware. Maintenance software resets the media module.
7. Error type 3586: The system detected an excessive number of uplink messages from the
Media Module. To prevent the faulty board from flooding the switch with data, the switch
software takes the board out of service and alarms it.
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 uplink messages from the board. If the
problem still exists, the software takes the media module out of service again. If the media
module does not exhibit the problem for a certain time period, then maintenance software
resolves the alarm and the media module is left in service.
8. Error type 3840: The media module received an inconsistent down-link message (a bad
header, port number, data, sub-qualifier, or logical link) over the Control Channel. This is a
notification only, and no action is required.
9. Error type 3842: 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.
10. Error type 3843: Bad translation RAM detected during call connection. The media module
marks the location as bad and reports it. The call continues on a different port.
MG-BRI demand test descriptions and error codes
Order of investigation Short test Long test D/ND 1
sequence sequence
Control Channel Looparound Test 52 on page 586 X X ND

MG-DCP MIN test board location Digital Line Media
Module
WRN
The following is a list of supported DCP Media Modules:

• MM712 (8 DCP port Media Module)
• MM717 (24 DCP port Media Module)
Maintenance software monitors and test ports on digital Media Modules and the hardware
connected to those ports for lines administered as a digital station.
MG-DCP error log entries and recommended actions
Table 99: MG-DCP Error Log Entries
1 0 Media Module removed or MIN ON
SAKI Sanity Failure (#53)
23 0 None WRN OFF
125 None MIN ON
257 65535 Control Channel Looparound MIN ON test board location r 20
Test (#52)
513 Any Angel Background Error MIN ON test board location
769 4358 None
1025 4363 NPE Audit Test (#50)
1281 Ringing Application Test MIN ON test board location r 2
(#51)
1538 Any None WRN ON
MIN
1. Run the short test sequence first. If every test passes, run the long test sequence. Refer to
each appropriate test’s description, and follow its recommended procedures.
Notes:
1. Error type 1: The media module stopped functioning or has been physically removed from
the system. The alarm is logged approximately 11 minutes after removal of the media
module or failure of the SAKI Sanity Test (#53).
Check for the physical presence of the media module in the slot indicated by the alarm. If
the media module is absent, insert one of the proper type. If the media module is present
and its red LED is lit, see LED alarms without Alarm Log entry or with Error Type 1 in LED
Descriptions for Avaya Aura® Communication Manager Hardware Components.
release board location.
3. Error type 23: The media module has been logically administered but not physically
installed. The alarm should clear when the media module is installed.
If the media module is already installed:
a. Run test board location long and look at any test failures or Error Codes
generated.
b. If the test does not clear error 23, then execute reset board location and run
the long test again.
c. If the reset/test does not clear error 23, replace the media module.
4. Error type 125: The media module physically installed in the slot does not match the type
that is administered for that slot. Do one of the following:
• Remove the incorrect media module and replace it with one of the type that is
administered for that slot.
• Use change circuit-pack or change media-gateway n to re-administer the slot
so that it matches the board that is installed, and follow with reset board location.
5. Error type 257: Transient communication problems between the switch and this circuit pack
or media module. Execute test board location and refer to the repair procedures for
the Control Channel Looparound Test 52.
6. Error type 513: An on-board hardware failure was detected. The system will continuously
test the media module and report the results approximately every 10 minutes. If the
hardware problem is resolved, the alarm should clear in approximately 30 minutes. If the
alarm does NOT clear in 30 minutes, then the media module should be replaced.
7. Error type 769: This error can be ignored, but look for other errors on this media module.
10. Error type 1538: The hyperactive media module is out-of-service and may exhibit one or
a. The media module level tests such as Test #51 and/or Test #220 are aborting with
Error Code 2000.
b. The tests run on the ports of this media module are returning with a NO-BOARD.
c. A busyout/release of the media module has no effect on test results.
d. A list configuration command shows that the media module and ports are
properly installed.
Check the alarm level. If the alarm level is a WARNING, users are probably causing the
hyperactivity by adjusting or changing their digital stations. If the media module is very
hyperactive, this alarm will be upgraded to a MINOR alarm within 1 hour. If the alarm level
is a MINOR alarm, then replace the media module.
MG-DCP demand test descriptions and error codes
sequence sequence
MG-DS1 (DS1 Interface Media Module)

MG-DS1 MAJ test board location long DS1 Interface
Media Module
MIN
The following is a list of supported DS1 Media Modules:

• MM710 Universal DS1 Interface Media Module (1 T1/E1 ISDN PRI trunk port)
• IMM_DS1 Integrated DS1 Media Module
• TIM510 DS1 Media Module for use in Juniper Gateways (1 T1/EI port)
MG-DS1 error log entries and recommended actions
Table 100: MG-DS1 Error Log Entries
data level board
1 Any Media Module MIN ON
removed or SAKI WRN 1
Test failed(#53)
18 0 busyout board WRN OFF release board location
location
23 0 WRN OFF add ds1 location
125 none MIN ON
WRN 1
3
257 65535 Control Channel MIN ON test board location l r 20
Looparound (#52)
Table continues…
data level board
257 Any
513 Any Angel Background MIN ON
Error WRN 1
514 46086 MIN ON
WRN 1
769 46085 MIN ON
WRN 1
770 46096 MIN ON
WRN 1
1025 NPE Audit Test
(#50)
1281 Any Loss of Signal Alarm MIN OFF test board location
Inquiry Test (#138) WRN 1
1301 Any Loss Of Signal WRN OFF test board location
Alarm Inquiry (#138)
1322 Any Loss of Signal Alarm MIN ON test board location
Inquiry Test (#138)
Inquiry (#138) WRN 1
1324 Any Loss of Signal Alarm WRN OFF test board location
Inquiry (#138)
1400 1401 Any Loss of Signal Alarm MIN ON test board location
Inquiry (#138) and
Echo Cancellation
(#1420)
1537 46082 MIN ON
WRN 1
1538 Any MIN ON
WRN 1
1793 Any Blue Alarm Inquiry MAJ OFF test board location
(#139) MIN
WRN 2
(#139) MIN
WRN 2
Table continues…
data level board
(#139) MIN
WRN
2049 Any Red Alarm Inquiry MIN OFF test board location
(#140) WRN 1
2305 Any Yellow Alarm Inquiry MIN OFF test board location
(#141) WRN 1
2306 Any Yellow Alarm Inquiry MIN OFF test board location
(#141) WRN 1
2561 Any Major Alarm Inquiry MIN OFF test board location
(#142) WRN 1
2817 Minor Alarm Inquiry MIN OFF test board location
(#143) WRN 1
3073 to Any Slip Alarm Inquiry MIN OFF test board location r 6
3160 (#144) WRN 1
3585 to Any Misframe Alarm MIN OFF test board location r 6
3601 Inquiry Test (#145) WRN 1
3840 Any
3841 4358
3842 46097
3999 Any
1. If ports are assigned to the Media Module, then a minor alarm is raised. If no ports are assigned
to the Media Module, then a warning alarm is raised. The alarm is raised after the Media Module
has been missing for a period of 15 minutes. Warning alarms are also raised against any ports
administered on the Media Module.
2. Major alarms on this MO may be downgraded to minor or warning alarms, and minor alarms on
this MO may be downgraded to warning alarms based on values set in set options.
Notes:
1. Error type 0: 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. Error type 1: The Media Module has totally stopped functioning or is not fully administered.
The alarm is logged about 15 minutes after the Media Module has been removed or
11-minutes after the SAKI Test (#53) fails. To be fully administered, a Media Module must
meet all three of the following conditions:
• Have an entry in the media-modules page on the change media module n form or
should be displayed in the list config all command.
• Be administered using the add ds1 location command
• Be physically inserted into the correct slot
If the Media Module has an entry in the circuit plan and either of the other two conditions
are not met, a MINOR alarm is logged.
a. To resolve the error do either of the following:
• Make sure that all conditions for administration are met and that a functioning
Media Module is inserted in the correct slot.
• Completely remove the Media Module from the system using the following steps.
b. Remove any administered DS1 trunks, access endpoints or PRI endpoints associated
with the Media Module from their trunk groups.
c. Execute remove ds1 location and change media module location.
3. Error type 18: The Media Module has been busied out by a busyout board location
command. Release the Media Module with the command release board location.
4. Error type 23: The Media Module is not completely administered. To be fully administered,
the Media Module must:
• Have an entry in the circuit plan using the change media module command
• Be administered using the add ds1 location command
• Be physically inserted into the correct slot
A DS1 Media Module differs from most Media Modules in that inserting the DS1 Media
Module into the gateway is not enough to make the board usable. It must also be
administered with the add ds1 command.
5. Error type 125: An incorrect Media Module is inserted in the slot where the Media Module
is logically administered.
To resolve this problem, either:
• Remove the incorrect Media Module and insert the logically administered Media Module.
• Use the change media-gateway command to re-administer this slot to match the
Media Module inserted.
6. Error type 257: Refer to Control Channel Looparound Test 52 for details.
7. Error type 513: The Media Module has detected a transient hardware problem.
The value in the Aux Data field indicates the type of hardware problem:Aux Data 4352:
External RAM failure Aux Data 4353: Internal RAM failure Aux Data 4355 Internal ROM
failure
If the board detects only one of these hardware problems, 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 Media Module should be replaced.
8. Error type 514: 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
frequently. If does (at least 10 times within 30 minutes), the Media Module should be
replaced.
9. Error type 769: Transmit FIFO Underflow Error.
This error occurs when the Media Module cannot find the end of frame bit when
transmitting a frame to the Packet Bus. An alarm is raised if this error occurs three
times within 10 minutes. Clear the alarm using the following commands: busyout board
location, reset board location, test board location long, release
board location. If the error recurs within 10 minutes, replace the Media Module.
10. Error type 770: Unable to Write LAN Translation RAM Error.
This error occurs when there are no available translation RAM locations for a call
connection attempt. An alarm is raised if this error occurs twice within 10 minutes. Clear
the alarm using the following commands: busyout board location, reset board
location, test board location long, release board location. If the error
recurs within 10 minutes, replace the Media Module.
12. Error type 1301: Error 1301 occurs when either CSU or E1 sync splitter circuitry is
currently in use and the integrated CSU is not administered on the DS1 board.
Resolution: Replace the board, or set the Near-End CSU Type field on the change ds1
screen to integrated.
13. Error types 1400, 1401: Echo Cancellation error.
Echo Cancellation errors are logged when:
• Error 1400 - The Echo Canceller Function Test failed.
• Error 1401 - The Echo Canceller Memory Test failed.
This error indicates that Echo Cancellation is no longer being supplied by the board. Clear
the alarm using the following commands: busyout board location, test board
location long, release board location. If Test #1420 that is Echo Canceller Test
fails, replace the Media Module.
14. Error type 1537: LAN Bus Timeout Error.
This error occurs when the Media Module 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 Media Module’s external ports. If any of the ports on this Media Module are
alarmed, refer to the repair procedures for those maintenance objects.
If the error occurs three times within 10 minutes, the board is isolated from the Packet Bus
and the board is alarmed. To clear the alarm and restore the board to the Packet Bus, use
the commands busyout board location, reset board location, test board
location long, release board location.
If the problem persists and there are no PKT-BUS alarms or port alarms, replace the Media
Module.
15. Error type 1538: The hyperactive Media Module is out-of-service and may exhibit one or
• The common Media Module level tests such as Test #50 abort with Error Code 2000.
• The tests run on the ports of this Media Module return NO-BOARD.
• A busyout/release of the Media Module has no affect on test results.
• A list configuration command shows that the Media Module and ports are
properly installed.
The Media Module is isolated from the system and all trunks or ports on this Media Module
are placed into the out-of-service state. The system will try to restore the Media Module
within 20-30 minutes. When no faults are detected for 20-30 minutes, the Media Module is
restored to normal operation. All trunks or ports of the Media Module 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.
16. Error types 3073 to 3160: The Media Module is receiving slips. The Error Type displays the
value of the last slip count reported.
17. Error types 3585 to 3601: The Media Module is receiving misframes. The Error Type
displays the value of the last misframe count reported.
18. Error Type 3840: Is not service-affecting. No action is required.
These errors are reported by the Media Module when it receives a bad control channel
message from the switch. The Aux Data identifies the cause of the error event.
19. Error Type 3841: The Media Module has detected a transient hardware logic error. This
error will disappear when no faults are detected for 100 minutes.
20. Error Type 3842: Bad Translation RAM Location Found. This error is not service-affecting.
No action is required. The call continues by using another translation location.
21. Error Type 3999: The Media Module sent a large number of control channel messages
to the switch within a short period of time. If Error Type 1538 is also present, the Media
Module was taken out-of-service due to hyperactivity. If Error Type 1538 is not present,
the Media Module 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 Media Module is being
lightly used, it may indicate a problem with the Media Module or the equipment attached to
it.
MG-DS1 demand test descriptions and error codes
Order of investigation Short test Long test Reset test ds1- D/ND 1
sequence sequence board loop
sequence
Echo Canceller Test 1420 on page 758 X D
Control Channel Looparound Test 52 on X ND
page 586
Loss of Signal Alarm Inquiry Test 138 on X X ND
page 601
Blue Alarm Inquiry Test 139 on page 601 X X ND
Red Alarm Inquiry Test 140 on page 604 X X ND
Yellow Alarm Inquiry Test 141 on page 606 X X ND
Table continues…
Order of investigation Short test Long test Reset test ds1- D/ND 1
sequence sequence board loop
sequence
Major Alarm Inquiry Test 142 on page 609 X X ND
Minor Alarm Inquiry Test 143 on page 610 X X ND
Slip Alarm Inquiry Test 144 on page 612 X X ND
DS1 Translation Update Test 146 on X X ND
page 614
ICSU Status LEDs Test 1227 on page 730 X X ND
Internal Looparound Test 135 on page 595 X D
MG-IAMM (Integrated Analog Media Module)

MG-IAMM MIN test board location long Integrated Analog
Media Module
The MG-IAMM Maintenance Object resides on the Integrated Analog Media Module (IAMM) which
is located on the main board of the TGM550 gateways.
The Integrated Analog Media Module is not field-replaceable.
For the G430 or G450, the Integrated Analog Media Module consists of six (6) fixed configuration
analog ports:
• Ports 1 through 4 are fixed as loop start CO trunk ports.
• Ports 5 and 6 may be administered as analog stations, DID trunks, or external alarm ports.
• Ports 4 and 5 are used by the gateway processor for emergency transfer relay (ETR)
purposes.
The Integrated Analog Media Module is a non-field-replaceable module. Slot #3 is virtual and
designated as the integrated analog media module slot. Slot #3 supports the IAMM exclusively.
For the G430 and G450, the Integrated Analog Media Module consists of three (3) fixed
configuration analog ports:
• Port 1 is fixed as an analog trunk port.
• Ports 2 and 3 are fixed as analog line ports.
• Ports 1 and 2 are used by the gateway processor for emergency transfer relay (ETR)
purposes.
MG-IAMM (Integrated Analog Media Module)
On a G430-BRI, slot #3 is virtual and designated as the integrated analog media module slot.
On a G450, slot #7 is virtual and designated as the integrated analog media module slot.
Administration will only allow port one to be administered as a loop start CO trunk. Ports 2 and 3
may only be administered as analog stations, DID trunks, or external alarm ports. Ports 1 and 2
are used by the emergency transfer relay (ETR).
The TGM550 is the Gateway blade which is integrated with the Juniper Networks Services
Routers. It provides an internal interface to the Juniper chassis backplane, 2 analog lines, and
2 analog trunks. Ports 2 and 3 are used by the emergency transfer relay (ETR).
The G450-DCP allows 4 trunks and 2 analog lines. Ports 4 and 5 are used by the ETR.
The G450-DS1 allows 1 trunk and 2 analog lines. Ports 1 and 2 are used by the ETR.
See XXX-BD (Common Port Circuit Pack/Media Module) on page 520for media module level
errors.
For individual port problems see the relevant MO:
• If the port is administered as a CO trunk, see CO-TRK (Analog CO Trunk) on page 337.
• If the port is administered as an analog line, see AN-LN-PT (Analog Line Port) on page 305.
• If the port is administered as an external device alarm, see ALARM-PT (Alarm Port) on
page 303.
MG-IAMM error log entries and recommended actions
Table 101: MG-IAMM Error Log Entries
1 0 Sanity Failure MIN ON
18 0 busyout location OFF release location
23 WRN OFF
257 65535 Control Channel MIN ON test board location r 20
Looparound Test
513 Any MIN ON
769 4358
Notes:
1. Error type 1: The Integrated Analog Media Module (IAMM) has stopped functioning or was
physically removed from the system. This alarm is logged 11 minutes after removing the
media module or the SAKI Sanity Test fails. NOTE: The IAMM is not removable. This error
indicates that there may be a firmware or hardware problem with the gateway.
a. Reset the Integrated Analog Media Module with reset board location.
b. Retest the board using test board location.
c. If this error persists, replace the gateway.

2. Error type 18: The indicated Integrated Analog Media Module circuit has been made
unavailable with the busyout location command. To resolve this error, enter release
location for the alarmed media module.
3. Error type 23: The media module has been administered but is not inserted. Because this
is an integrated media module, there may be a hardware or firmware problem with the
gateway main board.
a. Reset the Integrated Analog Media Module with reset board location. Use
list configuration media-gateway location to verify whether or not the
IAMM is inserted.
• For the G430, the code field for slot 3 should indicate 4T2LIM
• For the G430-BRI, the code field for slot 3 should indicate 1T2LIM
• For the G450, the code for slot 7 should indicate 1T2LIM
• For the TGM550, any slot may indicate the code TGM550
b. Verify that the latest version of firmware is present on the gateway main board. Use
show mg list_config. Upgrade the firmware if necessary.
c. If the problem persists, replace the gateway.
4. Error type 257: Test #52 failed. This error will clear when the test passes.
5. Error type 513: The IAMM circuitry detected a memory error during its background self-test
diagnostics (External RAM failure, Internal RAM failure, ROM checksum failure, Message
corruption). This error indicates the IAMM is running corrupted code.
a. Download and install the appropriate firmware on the gateway.
b. If the problem persists, replace the gateway.
6. Error type 769: The integrated analog media module detected an internal consistency. This
error can be ignored and no action is required.
MG-IAMM demand test descriptions and error codes

sequence sequence
MG-IBRI (Integrated BRI Trunk Media Module)
MG-IBRI (Integrated BRI Trunk Media Module)

MG-IBRI MIN test board location long Integrated BRI Trunk Media
Module
The MG-IBRI maintenance object resides on the virtual ISDN trunk-side BRI media module. It has
two ports which can either be administered as a trunk-side BRI port or BRI trunk.
MG-IBRI has the same maintenance strategy as the MG-BRI media module. See MG-BRI (BRI
Trunk Media Module) on page 431for the error codes, tests, and recommended actions.
MG-SYNC (Synchronization)
MG-SYNC MIN Not applicable. MO_MG_SYNC
MAJ
MG-SYNC error log entries and recommended actions
Table 102: MG-SYNC Error log entries
Error type Aux data Alarm level ON/OFF board Command to resolve the error
1 ANY MIN OFF Look for errors against the T1 (MG-DS1)
or BRI (TBRI-PT) interface and follow the
repair procedures.
257 ANY MIN OFF Look for errors against the T1 (MG-DS1)
or BRI (TBRI-PT) interface and follow the
repair recommendations.
Table continues…
Error type Aux data Alarm level ON/OFF board Command to resolve the error
513 ANY MAJ OFF Verify configurations to see if the media
gateway is a slave and does not have a
T1 or BRI sync source, or is a master
source whose T1 or BRI interface is
not functioning. If the media gateway
is a slave, make sure that the media
gateway is configured properly for IP
synchronization and is in an appropriate
network region to receive clock of IP
(CSoIP).
1793 ANY NA NA NA
Notes:
1. Error type 1: The primary synchronization source has lost signal. This causes a Minor
off-board alarm after 5 minutes.
2. Error type 257: The secondary synchronization source has lost signal. This causes a minor
off-board alarm after 5 minutes.
3. Error type 513: The media gateway is configured to have a primary synchronization
source, or the media gateway is configured for IP synchronization, but is running off the
local clock. This causes a major off-board alarm.
4. Error type 1793: The clock sources associated with this media gateway are switching
excessively in the last 5 minutes and caused the gateway to get locked to its local clock
source.
MIS (Management Information System)

log level
MIS WRN release mis Management Information System
Use the Management Information System (MIS)/Call Management System (CMS) to monitor MIS
busyouts during administration of MIS translations. There are no hardware failures associated with
this MO.
The MIS/CMS is an adjunct processor that collects Automatic Call Distribution (ACD) data sent
from the switch. To change MIS translations, enter busyout mis at the G3-MT. When the MIS is
busied out, the switch stops sending ACD data to the MIS, and a Warning alarm is raised.
When the busyout mis is complete, enter release mis at the terminal. This clears the
Warning alarm and allows the switch to send ACD data to the MIS.
MIS error log entries and recommended actions
No-LIC (No license)
Table 103: MIS Error Log Entries
Error Aux data Associated test Alarm level On/Off board Command to resolve the
type error
0 0 Any Any Any release mis
18 0 busyout mis WRN ON release mis
Notes:
1. Error type 0: run the short test sequence first. If every test passes, run the long test
2. Error type 18: with busyout mis, no data is sent to the MIS/CMS regardless of the link
state. To allow data to be sent to MIS/CMS, use release mis at the terminal.
No-LIC (No license)

No-LIC Maj None No license
Note:
The No-LIC MO is non-traditional. In that there are no associated tests or commands that can
be executed. There are no demand tests to run.
How systems go into no-license mode
The No-LIC MO works with the LIC-ERR MO to find any errors or violations associated with
the license file. Once a license file error occurs, LIC-ERR logs the error, raises an alarm, and
generates the following SAT login message:
System administration will be blocked in approximately XXX hours.
Contact your service representative.
Entry into license-error mode starts a timer that, when expired, causes the system to enter no-
License mode. See the figure on page 448. When Communication Manager enters the no-License
mode, the following SAT warning message displays:
System administration is blocked. Contact your service representative
immediately.
The system also responds with these conditions:
• License error displays on all stations and consoles when they go off-hook, but disappears
when the first digit is pressed. This display message does not interfere with the normal use of
any station or console.
• All terminal-login sessions are terminated.
• Any subsequent terminal-login sessions are limited to:

- Maintenance commands.
- License file installation command.
Figure 6: License mode algorithm

The License file feature is loaded onto a switch during initialization of the switch software, restore
of translations, and periodically thereafter. After initialization, a query is made to a software
module called the license server. This module reads the license file, compares a serial number
in the license file to a serial number in hardware, and compares the software version in the
license with the running software version. If a match occurs, the license server delivers a new
feature mask, an information set that controls which features are enabled or not on the Customer
Options and Special Applications screens.
No-LIC (No license)
No-LIC error log entries and recommended actions

Error type Aux Associated test Alarm level On/off board Command to resolve the
data error 49
1 ( 1 on MAJ OFF
page 449)
513 (2 on MAJ OFF
page 449)
769 (3 on MAJ OFF
page 449)
1537 (4 on MAJ OFF
page 449)
1793 (5 on MAJ OFF
page 449)
2305 (6 on MAJ OFF
page 449)
2561 (7 on MAJ OFF
page 449)
49 These error are cleared by installing a valid license file that matches the hardware ID.
Notes:
1. Error type 1: There is a serial number mismatch caused by:
• Reference IPSI not responding, or motherboard not responding.
• Expiration of the timer.
• The system enters no-license mode.
2. Error type 513: The license has expired and:
• A license error failure has occurred.
• The timer has expired.
• The system enters no-license mode.
3. Error type 769: The system is in the feature usage exceeds limits mode, and a license
error failure has occurred. System feature use has exceeded limits, and the timer has
expired. The system enters no-license mode.
4. Error type 1537: The license file is missing or corrupted. The system enters no-license
mode.
5. Error type 1793: A software version mismatch has occurred. The system enters no-license
mode.
6. Error type 2305: The offer category of the license does not match the offer category in
translations. The system enters no-license mode.
7. Error type 2561: During the last attempted license file audit, the license server did not
respond in time.
NR-CONN (Network-Region Connect)

log level
NR-CONN Min test failed-ip-network-region Network-region connect
WRN
A network region is a logical grouping of IP endpoints, including IP stations, IP trunks, and

gateways sharing the same transmission characteristics or VoIP and signaling resources. The
Network-region connect (NR-CONN) MO monitors VoIP connectivity between network regions and
raises:
• A warning alarm for a single failure.
This alarm is in response to one failed background ping test between IP endpoints
in separate network regions. This test is part of the background Network Region
Interconnectivity Test 1417.
• Minor alarm for multiple failures.
Once a single failure is detected, Test #1417 is re-executed between different IP endpoints
in the same pair of network regions. If the test still fails between these network regions,
maintenance software marks the connectivity between them as “failed.”
As a background operation during each 2-minute interval, Test #1417 checks the translated
connections between 50 pairs of network regions until every translated connection has been
tested, and then repeats. The Communication Manager translation table’s maximum capacity
for network-region connections is 31,250. Testing every possible connection would require 625
2-minute test intervals during about 21 hours.
Repair strategies
• Use display failed-ip-network-region to display pairs of network regions with
failed connectivity. In a descending order of severity, this command lists up to 100 network
regions with the most severely broken connectivity.
• Use status ip-network-region to see the status of connections from a particular
network region.
• As an on-demand operation, test failed-ip-network-region retests every network-
region connection marked as failed. Those connections that:
- Pass are returned to service.
- Fail is remarked as failed and remain on the list of bad connections.
NR-REG (Network Region Registrations)
NR-CONN error log entries and recommended actions

Table 104: NR-CONN error log entries
Error AUX Associated test Alarm On/off Command to

type data level board resolve the
error
1 0 Network Region Connectivity Test (#1417) Min On
Note:
1. Error type 1: One or more network-region connections have failed.
a. Enter display failed-ip-network-region to verify that connections between
pairs of network regions are failing.
b. If so, enter test failed-ip-network-region to retest these paths.
c. For each affected network region, check the error log for failures to related MOs, such
as:
• DIG-IP-S (Digital IP Station)
• RDIG-STA (Remote Digital Station)
and resolve any problems.
a. Enter test failed-ip-network-region to retest these paths.
b. If errors persist, escalate.
NR-CONN demand test description and error codes

sequence sequence
Network Region Interconnectivity Test 1417 on X Nondestructive
page 755
NR-REG (Network Region Registrations)

level
NR-REG Min None Network region
registrations
WRN enable nr-registration network-
region
The NR-REG maintenance object generates alarms when:

• There has been hyperactive registration of gateways within a network region
• Registration from gateways and IP phones are denied because the disable nr-
registration network-region command was executed.
It is assumed that a Survivable Remote Server is provided for the network region and that the
gateways and IP phones will register with the Survivable Remote Server based on the primary
search list for gateways and the alternate gatekeeper list for IP phones.
NR-REG alarms will only be generated if hyperactive link bounce detection is enabled on the
system-parameters ip-options screen. Registration will be denied only if the disable
nr-registration commands are entered from the SAT.
The hyperactive NR-REG alarms and the associated disable/enable nr-registration
network-region commands should only be used for situations where IP network problems
cause gateways and IP phones to repeatedly register and unregister to a server at a rate that is
too fast for the normal link bounce strategy to cause the gateways and phones to fail over to a
Survivable Remote Server.
The system detects hyperactivity by monitoring the number of link down failures reported to
the MED-GTWY maintenance object. When enough link down failures are detected within the
administered time frame, an alarm is raised against the offending gateway. Using this data, a
percentage of hyperactive gateways is calculated and checked against the administered system-
wide limit. If the limit is exceeded, a minor alarm is generated for the network region. The system
does not try to recover from hyperactivity. It only generates an alarm.
If a certain period of time passes without any additional link down events, the hyperactivity alarm
is cleared. The alarm is resolved if less than 50% of the gateways required to raise an alarm are
out of hyperactive mode.
NR-REG error log entries and recommended actions
Table 105: NR-REG error log entries
1 Min Off
257 WRN Off enable nr-registration
network-region
Notes:
1. Error type 1: The percentage of hyperactive gateways in a network region exceeds the
administered percentage.
a. Enter disable nr-registration network-region so that gateways and IP
phones in the specified network region will register to a Survivable Remote Server.
The registration of the IP network endpoints to a server is being disabled, not the IP
PDMODULE (Processor Data Module)
network region itself. The use of this command is a temporary recovery action, not a
corrective action.
b. After the network problem has been corrected, enter enable nr-registration
network-region to enable registration of the IP network endpoints to a server. This
will allow them to re-register with the main server depending upon the administered
recovery rule specified on the change media-gateway screen.
2. Error type 257: Registrations for the network region are currently disabled. Enter enable
nr-registration network-region to enable registration of the ip-network endpoints
to a server.

level
PDMODULE 1 MIN test port location long Processor Data Module
TDMODULE 2 MIN test port location long Trunk Data Module
1Digital Terminal Data Modules (DTDM), and Data Adaptors (DA) in linked mode are considered
part of the Digital Line MO. See the DIG-LINE section for maintenance of these devices. DAs in
stand-alone mode are included in PDMODULE.
Some of the alarms that are logged due to PDMODULE and TDMODULE test failures may be
related to PROCR problems reported during DIG-BD testing.
Error log entries and tests also apply to TDMODULE.
The PDMODULE and TDMODULE MOs monitor and test Digital Line circuit pack ports that
are connected to Data Communications Equipment (DCE) or Data Terminal Equipment (DTE).
DCE include processor data modules (MPDM) and Data Adaptors (DA). DTE include trunk
data modules (DTE). These stand-alone data modules provide interfaces between DCP ports
on the Digital Line PROCR and data equipment such as terminals, host computers, and data
modems. See the following list and figure. Data modules are used for dial-up and permanent
circuit-switched data calls.
Digital Line PROCR also connect to digital terminal data modules (DTDMs), which work in
conjunction with a voice terminal. Those configurations are covered by the DIG-LINE MO. PROCR
level maintenance is covered by DIG-BD whose strategy is described in the XXX-BD (Common
Port Circuit Pack/Media Module) on page 520.
Digital line PROCR include the TN754, TN754B, TN413, TN2136. See DIG-LINE (Digital Line) on
page 349 for more information about the characteristics of these PROCR.
Note:
Not all tests that run on PROCR are applicable to media modules. These tests will abort with
error code 1412. This error can be ignored.
Standalone DCP data modules

There are two types of standalone DCP data modules as shown in below table on page 454.
Table 106: Standalone DCP data modules
Type Name 50 Interfaces to:

MPDM Modular Processor Data Module DTE (data terminals, host computers, printers)
MTDM Modular Trunk Data Module DCE (modems, data modules)
50Early versions of these data modules were referred to as PDMs and TDMs, respectively. Later
models are designed to provide a variety of interfaces by using interchangeable modules and are
thus called modular data modules
Data adapters
TN2136 PROCR use IDCP signaling and a DAA2 Data Adaptor (DA) to interface to DTE. DAs can
operate in either of two modes which are covered by different MOs:
Table 107: Data adaptor modes
DA mode Administered as: Endpoint Maintenance object

Stand-Alone PDM Data endpoint only PDMODULE
Linked DTDM IDT1/251 and optional data terminal DIG-LINE
51IDT1/2: Italtel Digital Telephone, Model 1 or 2, also known as Digital Telephones TD7210 and
TD7206.
Configurations and maintenance

The MPDM provides an interface for Data Terminal Equipment terminals, and the MTDM (see
note) provides an interface for Data Communications Equipment transmission equipment such as
modems.
Note:
Early versions of these data modules were referred to as PDMs and TDMs, respectively.
Later models are designed to provide various customer interfaces through the use of
interchangeable interface modules and, therefore, are called modular data modules.
In the following discussion, the general term data module refers to MPDMs, MTDMs, and
DAs. The PBX loop or digital link between a data module and the digital line port supports
two logical information channels and one signaling channel. Data modules generally use the
primary information channel for data communications and the signaling channel for dialing and call
supervision. With 4-wire DCP, the secondary information channel can be used to support a second
data module on a shared port.
Besides being used for data calls between terminals, computers, and data communications
equipment, data modules also serve as interfaces to equipment associated with system
features, such as System Administration, Station Message Detailed Recording, Message Center
Service, Automatic Call Distribution, Distributed Communications System, and Audio Information
Exchange. Maintenance for data modules associated with these latter services are covered by
other MOs such as PMS-PRNT, JNL-PRNT, and PMS-LINK.
Maintenance of data modules is closely related to and interacts with Digital Line circuit pack
maintenance, and test results for data modules can be affected by the health of the Digital Line
PROCR. Keep this interaction in mind when investigating customer-reported problems with data
modules.
Data modules provide a variety of option switches to allow the customer to select data rates,
parity, keyboard dialing, local, and remote loopback. The DAA2 Data Adaptor has an AT (Hayes)
type interface that allows selection of the above parameters as well as mode linked or standalone.
An incorrect selection will not necessarily cause errors, alarms or test failures, but it can result in
service disruption. See the installation manual provided with the data module for more information
about those options.
This discussion occasionally refers to a station’s service state, defined as:
Out-of-Service The port, and thus the data module, have been removed from service. Causes
for this include busyout of the port, removal of the Digital Line PROCR, and
failure of the GPP NPE Crosstalk Test (#9).
Disconnected The port is administered but the associated digital link does not respond. An
administered port is put in a disconnected state after a system reboot or circuit
pack insertion. This state persists until a link-reset-pass message is received
from firmware on the PROCR.
In-Service When switch software receives a link-reset-pass message from the port, the
port is placed in service. If the link-reset-pass message is missed, and an
off-hook message is received while the port is in the disconnected state,
maintenance software will run an ID request test and put the port into service
upon receiving a correct response.
Figure 7: Typical data module configurations
PDMODULE error log entries and recommended actions

Table 108: PDMODULE, TDMODULE error log entries
Error type Aux Associated Test Alarm On/Off Command to resolve the error
Data Level Board
0 0
1 40987 WRN OFF
1 1 – 20 WRN OFF
15 Any
location
257 40971
513 0 Digital Station Audits WRN OFF test port location r 6
(#17)
Table continues…
Error type Aux Associated Test Alarm On/Off Command to resolve the error
Data Level Board
769 40988 WRN OFF
1281 Any Digital Station Audits WRN OFF test port location r 4
(#17)
1537 40968 WRN OFF
1793 Information and MIN ON test port location l r 3
Control Channel
Looparound (#13)
2049 GPP NPE Crosstalk MIN ON test port location l r 3
(#9)
2304
2305 32770
2305 40967
2561 Any Data Module Internal WRN OFF test port location l r 5
Looparound (#175)
2817 Link GPP Loop (#183) MAJ ON
Against Links
3841
Notes:
1. Error type 0: a Digital Line circuit pack that has ports administered has been removed
since the Error Log was last cleared. Make sure that the circuit pack has been re-inserted.
2. Error type 1, Aux Data 40987: An off-board problem was detected by the port circuit, and
may result in a noisy port or link. See Note ( 14 on page 458) for recommendations.
3. Error type 1, Aux Data 1 - 20: Is logged when at least 15 off-board problems have been
detected with the link to the data module. Each error detected increments an on-board
counter. The aux data gives the value of this counter divided by 15. The user could
experience a noisy port or link. See Note 14 on page 458for recommendations.
4. Error type 15: An internal error that occurs when an audit request fails.
5. Error type 18: The port in question is demand busied out. Release the port with release
port location .
6. Error type 257: Problems with transmitting to the data module. This is usually an on-board
problem and can be ignored if no user complaints are received. Otherwise, check for faulty
wiring.
7. Error type 769: EPF has been turned off due to the overcurrent condition at the data
module. See the recommendations in note n. This may also be caused by the PTC being
in the tripped position due to a short on the power line. You can correct this by removing
the short, unplugging the data module from the wall for about 30 seconds, and plugging it
back in.
8. Error type 1537: There is a problem with the link to the data module. This can be ignored if
no user complaints are received.
9. Error type 2304: Internal error. No action is necessary.

10. Error type 2305, Aux Data 32770: The data equipment went off-hook while the associated
link was being initialized in a disconnected state. Use status data-module to
determine the state of the data module. The off-hook should have changed the service
state to in-service. No action is necessary.
11. Error type 2305, Aux Data 40967: The link between the circuit pack and the data module
has been reset successfully. The link is normally reset when the circuit pack associated
with an administered port is first plugged in assuming that the data module is already in
place and connected to the associated port, when a port is first administered assuming
the associated circuit pack is plugged in and that the data module is connected to the
associated port, or when a data module is first connected to an administered port. No
action is necessary.
12. Error type 2561: The downlink buffer on the circuit pack has overflowed. No action is
necessary.
13. Error type 2817: A DCP endpoint may have been disconnected.
14. Error types 1, 769, 1537, and 3841: Ensure the data module is connected and operating
properly. Check for faulty wiring. If necessary, reduce the length of the cable between the
data module and the switch to 5000 ft. for 24-gauge wire or 4000 ft. for 24-gauge wire.
If the problem still exists, replace the circuit pack. Once the problem has been resolved,
the alarm will be retired in 60 minutes or in 90 min. for error 1537.
The DA module is not phantom-powered from the port. Thus when it is in linked mode, its
range is limited by the Italtel digital telephone’s limit: 0.7 Km (2300 ft.) on 26-gauge wire
or 1.8 Km (5900 ft.) on 22-gauge (0.6 mm) wire. If in stand-alone mode, it is limited by the
maximum length of loop allowed from the Digital Line Interface (DLI) component: up to 3.5
km (2 miles) on 22-gauge (0.6 mm) wire.
PDMODULE demand test descriptions and error codes

Order of Investigation Short test Long test D/ND
sequence sequence
Local Loop Test 13 on page 553 X ND
PE-BCHL (PRI Endpoint Port)

PE-BCHL 53 MIN test port location long PRI Endpoint Port
PE-BCHL WRN test port location PRI Endpoint Port
53Foradditional repair information, see Troubleshooting ISDN-PRI endpoints (wideband) in

Maintenance Procedures for Avaya Aura® Communication Manager, Branch Gateways and
Servers.
A PRI endpoint provides ISDN-PRI (Primary Rate Interface) connections application equipment or
terminal adapters that terminate ISDN PRI. The equipment or terminal adapters are connected to
the switch via the TN464C/D UDS1 interface circuit pack. This MO monitors the PRI endpoint’s
port hardware on the UDS1 circuit pack by:
• Logging hardware errors
• Running tests for port initialization
• Running periodic and scheduled maintenance
• Executing demand tests
Wideband Switching
Wideband switching 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. Switching capabilities
support wideband calls comprised of multiple DS0s that are switched end-to-end as a single entity.
Wideband switching is designed for ISDN application equipment such as ISDN video codecs, but
can also interface to non-ISDN application equipment by using PRI terminal adapters. In the same
sense that a data module acts as a DCP or BRI terminal adapter between endpoint data, such as
V.35 and dialing interfaces such as RS-366 and a DCP interface, a PRI terminal adapter acts as a
wideband terminal adapter between endpoint data and dialing interfaces and a line-side ISDN-PRI
interface. Wideband switching introduces PRI endpoints on line-side interfaces.
A PRI endpoint has a unique extension number and consists of one or more contiguous B-
Channels on a line-side T1 or E1 ISDN-PRI facility. Endpoints initiate and receive calls via ISDN
SETUP messages indicating the data rate and specific B-Channels to be used, and communicate
all other call status information via standard ISDN messages. Any ISDN signaling set such as
Avaya, CCITT, or ECMA may be used for a line-side ISDN-PRI facility.
Multiple PRI endpoints on 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:
• Use standard ISDN-PRI signaling
• Adhere to the administered PRI endpoint boundaries when initiating calls
• Handle incoming calls appropriately, based on the originating PRI endpoint
Signaling and B-Channel States

PRI ports use a separate channel called the D-Channel for call-control and signaling messages.
This is called out-of-band signaling. The D-Channel associated with the set of B-Channels is
an ISDN-PRI signaling link’s port (ISDN-PLK). The signaling protocol used on the ISDN-PRI
signaling-link port’s D channel is defined by one of the four selectable ISDN-PRI Specifications:
Avaya, 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, changes over time, and can have far- and
near-end components. The service state is initialized to Out-Of-Service/Far-End, and an attempt
is made to negotiate it to In-Service. Use status pri-endpoint extension to display the
service state of a particular PRI endpoint port’s B-Channel.
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 the PRI endpoint port designed to audit these states and
ensure agreement between both ends of the PRI wideband connection.
Alarming Based on Service States

A PRI endpoint port’s B-Channel logs a warning alarm when it is placed in 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, use status
pri-endpoint extension to determine the exact state of the port. Other alarms can be
diagnosed by using the short and long test sequences. Note that a PRI endpoint port’s B-Channel
can be placed in a far-end service state by direct action by the far-end terminal adapter or by
inaction of the far-end terminal adapter. For example, if it does not respond to a Remote Layer
3 Query, see Remote Layer 3 Query Test 637 (for ISDN-PLK) the associated PRI endpoint port’s
B-Channels will be placed in the Maintenance/Far-End service state.
A PRI endpoint port is a port on a UDS1 interface circuit pack and thus depends on the health
of the circuit pack for proper operation, see the following figure PRI Endpoint Port Interactions. A
problem on the associated ISDN-LNK’s (ISDN-PRI signaling-link port’s) D-Channel can also affect
the PRI endpoint. In turn, the ISDN-PLK depends on the SYS-LINK (system link) to the packet
interface. Keep this hierarchy of dependencies in mind when diagnosing problems.
Figure 8: PRI Endpoint Port Interactions
PRI Endpoint Port Service States

The status pri-endpoint extension command displays the following possible service
states for PRI endpoint ports. The table that follows gives recommended procedures for each
state. The figure following that shows typical progressions from one service state to another. Refer
to Maintenance Procedures for Avaya Aura® Communication Manager, Branch Gateways and
Servers for a layered approach to addressing PRI endpoint problems.
• 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 first administered. The switch then 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
port remains out of service, and maintenance will periodically resend the messages. The port
is unusable for incoming and outgoing calls, although other ports in the PRI endpoint can still
be used.
• Out-of-Service/Near-End (OOS/NE)
This is the state of the port when a hardware failure exists on the signaling link, the NPE
Crosstalk test fails, or when the port is busied out by command. In this state, the port is
unusable for calls coming into the switch or going out 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 the port
is released by command.
• 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 within 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 terminal
adapter to try to negotiate the port B-Channel into service. The port is unusable for outgoing
calls to the terminal adapter but will service incoming call requests from the far end. Other
ports of the PRI endpoint can still to place outgoing calls to the terminal adapter. Transitions
into MTC/FE do not drop stable calls. If the service state changes from in-service to MTC/FE,
stable calls are unaffected.
• Maintenance/Near-End (MTC/NE)
Use busyout, test port l or test pri-endpoint l to busy out the signaling link
(SYS-LINK). Transitions into MTC/NE do not drop stable calls. The busyout link lnk-no
command does not drop stable wideband calls. In this state, the B-Channel is not usable for
new incoming calls to the switch or new outgoing calls 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, a pending state is in effect. For example, if the port is out-of-service/
far-end and an in-service message was sent to the far end, then the service state of the port
is OOS/FE-PEND/INS meaning out-of-service/far-end, pending/in-service. The service state
will reflect this pending state until the far end responds or the timer expires.
PRI endpoint service state OOS/NE

Alarm
WRN
Cause
Port has been busied out by command.
Proposed Solution 1
Enter release pri-endpoint extension.
Alarm
MIN
Cause
NPE Crosstalk test (#6) failed.
Proposed Solution 2
Replace UDS1 circuit pack.
Alarm
None
Cause
UDS1 circuit pack lost its signal.
Proposed Solution 3
Check if the UDS1 circuit pack is removed. Check if the UDS1 cable disconnected. Check if
the far-end terminal is restarting or experiencing problems. Check circuit pack using UDS1-BD
procedure.
PRI endpoint service state OOS/FE

Alarm
WRN
Cause
Far-end problems or incompatibility
Proposed Solution 1
Check administration and status of the corresponding port on the terminal adapter.
Alarm
WRN
Cause
The far-end port is busied out.
Proposed Solution 2
Check the status of the far-end terminal adapter.
PRI endpoint service state OOS/FE PINS

Cause
Service message was sent and the switch is waiting up to 2 minutes for a reply from the far-end
terminal adapter.
Proposed Solution
Wait 2 minutes, and check service state after the PINS state has cleared.
PRI endpoint service state MTC/NE

Cause
System link demand busied out.
Proposed Solution
Check link status. Release with release link link#.
PRI endpoint service state MTC/FE

Alarm
WRN
Cause
Signaling channel has been down for over 90 sec.
Proposed Solution 1
Consult ISDN-SGRP, ISDN-SLK and/or SYS-LINK. Far-end terminal adapter may currently be
restarting.
Alarm
WRN
Cause
Repeated failure of far end to respond to messages.
Proposed Solution 2
Maintenance software will periodically try to resend messages. You can speed the process with
test port location (Test #256).
Alarm
WRN
Cause
The far-end port is being tested.
Proposed Solution 3
Check status of the far-end terminal adapter.
PRI endpoint service state MTC/FE PINS

Cause
Service message was sent, and the switch is waiting up to 2 minutes for a reply from the far-end
terminal adapter.
Proposed Solution
Wait 2 minutes, and check service state after the PINS state has cleared.
PRI endpoint service state INS

Cause
Normal operating state. ISDN wideband calls are completing.
Figure 9: Common Progressions in PRI Endpoint Service States
PE-BCHL error log entries and recommended actions

Table 109: PE-BCHL Error Log Entries of
data level Off
board
Table continues…
data level Off
board
15 Any Port Audit and Update
test (#36)
18 0 busyout pri- release pri-endpoint
endpoint extension extension
busyout port release port location
location
129 WRN OFF test port location
513 Any WRN OFF test port location
1281 Any Conference Circuit Test MIN ON test port location l r 4
(#7)
1537 Any NPE Crosstalk Test (#6) MIN ON test port location l r 3
3073 Any Service State audit test port location r 2
(#256)
3585 Any
Note:
1. Error type 0: run the short test sequence first. If every test passes, run the long test
sequence. Refer to each test’s description and follow its procedures.
2. Error type 1: disagreement between this 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 will automatically try to recover by clearing the call (the call will be torn down).
Use status pri-endpoint extension to determine the state of the port.
When running the short test sequence, note the results of the Call State Audit Test
257.
3. Error type 15: software audit error that does not indicate any hardware malfunction.
Run the short test sequence, and investigate associated errors.
4. Error type 18: the PRI endpoint port has been busied out by busyout pri-
endpoint extension or busyout port location. No wideband calls can be
made to this port, although wideband calls can still be made to other ports within this
PRI endpoint if they are in service. Release the port with release port location.
5. Error type 129: the far-end terminal adapter changed its ISDN service state to out-of-
service or maintenance. This may be a temporary condition due to testing of this port
by the far-end terminal adapter or a hardware problem with the port. Outgoing calls
to the terminal adapter will not be 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, enter status pri-endpoint extension.
6. Error type 130: the circuit pack has been removed or has been insane for more than 11
7. Error types 257 and Error types 769: 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. The switch will automatically try to recover
by performing a service state audit. Use status pri-endpoint extension to
determine the state of the port.
When running the short test sequence, note the results of the Service State Audit Test
256.
8. Error type 513: 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
sure they agree.
9. Error type 1281: The Conference Circuit test (#7) failed on this port. See Conference
Circuit Test 7 for repair procedures.
10. Error type 1537: The NPE Crosstalk test (#6) failed on this port. See NPE Crosstalk
Test 6 for repair procedures.
11. Error type 1793: failure of the UDS1 Interface circuit pack. Run the short test sequence
and note the results of the Signaling Link State Audit Test 255.
12. Error type 3073: Two Service State audit attempts have failed, see Service State Audit
Test 256. The port will not be usable for any outgoing calls to the terminal adapter until
the test passes and the port state is changed to in-service. Incoming calls from the
terminal adapter will be accepted over this port, and other ports in the PRI endpoint
can still be used for both incoming and outgoing calls to and from the terminal adapter.
13. Error type 3585: the switch received an ISDN RESTART message for an ISDN port
that is not idle. Because calls are not typically cleared with the RESTART message,
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 the unexpected RESTART request was received from the terminal adapter.
This information can be useful if dropped calls are being reported by users of the PRI
endpoint. Aux Data values that do not appear below can be ignored.
Table 110: PE-BCHL - Error 3585 Aux data values
Aux data Meaning

10 A call in a stable, talking state the active state was cleared unexpectedly by the
far-end terminal adapter with an ISDN RESTART message.
Table continues…
Aux data Meaning

4 A call that has not reached the active state, but has at least reached a ringing
state, was cleared unexpectedly by the far-end terminal adapter with an ISDN
7
RESTART message.
8
260
263
1 A call that has not yet reached a ringing state was cleared unexpectedly by the
far-end terminal adapter with an ISDN RESTART message.
3
6
265
11 A call that was already in the process of clearing has been cleared by the far-
end terminal adapter with an ISDN RESTART message. If this condition occurs
12
frequently, it may mean that the far-end terminal adapter is attempting to clear
19267 ports that it thinks are in a hung state. The RESTART message puts the port in an
idle condition.
268
531
PE-BCHL demand test descriptions and error codes

sequence sequence
Signaling Link State Audit Test 255 on page 620 X X ND
Service State Audit Test 256 on page 622 X X ND
Call State Audit Test 257 on page 626 X X ND
PLAT-ALM (Platform Alarms)

The PLAT-ALM is a virtual MO used by Communication Manager to keep track of its server and
gateway alarms.
Note:
CMG can be seen in some gateway traps.
PMS-LINK (Property Management System Link)
If there is an alarm against PLAT-ALM, do the following:

1. Access the server’s Linux command line by entering the SAT command go shell.
2. Log into the server’s Linux shell.
3. View the server’s current list of alarms by entering almdisplay -v. See Avaya
Aura®Communication Manager Server Alarms.
Note:
If the almdisplay command returns a failure message, such as: almdisplay: 4:
Unable to connect to Multifilament, enter man almdisplay for command-
related information.
4. Troubleshoot and clear the problems by following the procedures for the maintenance
object listed under either:
• Avaya Aura®Communication Manager Server Alarms
• Avaya Aura® Communication Manager SNMP Administration and Reference
An alternative procedure for an alarm against PLAT-ALM requires the following steps:
1. Log into the server’s Web interface.
2. View the server’s current list of alarms by clicking on the Display Alarms option.
3. Troubleshoot and clear the problems by following the procedures for the appropriate MOs
listed in the display.
Note:
After repairing the server or gateway, use the Linux command almclear to manually
clear every server or gateway alarm. This action will also clear any alarms associated
with PLAT-ALM. See Clearing Server Alarms in Avaya Aura®®Communication
Manager Server Alarms.

level
PMS-LINK MIN test pms-link long PMS Link
WRN test pms-link
Property Management System (PMS) is a stand-alone computer system that environments

such as hotels or hospitals use for services such as reservations, registration, messaging,
housekeeping, night audit, billing, and inventory. The PMS Link provides a communications
channel between the switch and the customer-owned PMS so that the PMS can interrogate the
system for information related to the following features:
• Message Waiting Notification
• Controlled Restriction
• Housekeeping Status
• Check-in/Check-out
• Room Change/Room Swap
The PMS device connects to the system via a data module (PDM, MPDM, DTDM) connected to a
port on a PROCR.
PMS Link maintenance provides a strategy for maintaining the link between the switch and a
PMS 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 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 Link
Setup fails, PMS Link Maintenance will wait for five minutes before the next retry. If the number of
retries reaches 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 (the external PMS device, Data Module (PDM/MPDM/DTDM), or ADU). 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 test pms-link fails, no
alarm will be generated.
The list pms-down command lists every meaningful event to the PMS that occurred while the
link between the switch and the PMS was down. For example, any room status codes entered by
hotel housekeeping staff during a time of PMS outage would be shown in this report.
Restoring the PMS Link

Procedure
1. Determine the status of the PMS Link.
Enter status pms-link, 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-parameters hospitality, and find out the destinations of
the PMS Link.
3. Determine the status of the data extension.
Enter status data extension, 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 Namefield of the Error Log. See XXX-BD (Common Port Circuit Pack/Media
Module) on page 520for resolutions.
4. 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.
5. If the problem is not found in the above steps, check the PROCR for any problems.
Result
When restoring the PMS link, it is necessary to execute maintenance test on different objects that
comprise the PMS link. It is recommended that you busyout the PMS link before trying to restore
the link. When the PMS Link is busied out, every PMS Link maintenance action is deactivated,
and interference with tests of other MOs is prevented.
PMS-LINK error log entries and recommended actions
Table 111: PMS-LINK Error Log Entries
Error type Aux data Associated test Alarm On/Off Command to resolve the error
level board
0 0 Any Any Any test pms-link
18 0 busyout pms-link WRN OFF release pms-link
257 Any Link Retry test (#215) MIN OFF test pms-link l
WRN1
513 Any test pms-link
769 Any
1025 40–49
1281 10–19
1537 N0–N9
2049 Any
2305 50–59 release pms-link, or
test pms-link
2817 100–109
200–209
300–309
3073 70–79
3841 20–29
1Minor alarms on this MO may be down graded to Warning alarms based on the value in set
options.
Notes:
2. Error type 18: The PMS Link has been busied out with busyout pms-link. The link is
torn down. Enter release pms-link to restore the link.
3. Error type 257: The Link Retry test (#215) fails. An error was detected when setting up the
link. Refer to the Procedures for Restoring the PMS Link above.
4. Error type 513: The PMS physical link is down for one of the following reasons:
• Cable to the PMS device is disconnected.
• The PMS device is powered off.
• The data extension to which the PMS device connects has been busied out.
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 the in-service/idle state. If the data extension is not available, then see
Procedures for Restoring the PMS Link.
5. Error type 769: There has been no communication between the switch and the PMS for a
period of time specified in “system hospitality” administration. The PMS Link is torn down.
To clear this error, see Procedures for Restoring the PMS Link.
6. Error type 1025: 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 occurs frequently (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 Error Log.
7. Error type 1281: 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 occurs frequently (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 Error Log.
8. Error type 1537: 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),
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 Error Log. No alarm is
raised against this error.
9. Error type 1793: Due to heavy call traffic, or the PMS protocol message rate being faster
than the PMS/PBX protocol specifications allow, the PMS Link is torn down. PMS Link
maintenance software will wait for five minutes before attempting to set up the link again.
If this Error Type occurs frequently (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 Error Log. The PMS should be checked for
adherence to message rate defined in the PMS/PBX protocol specifications. No alarm is
raised against this error.
10. Error type 2049: The attempt to swap the database between PBX and PMS failed three
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 occurs frequently
(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 Error Log. No alarm is raised against this error.
11. Error type 2305: The PMS Link was busied out with busyout pms-link, or it was
brought down with test pms-link long. The PMS Link is torn down, and PMS Link
maintenance stops attempts to reestablish the link in the case where the busyout pms-
link was used. When test pms-link long has been used, PMS Link maintenance
continues trying to reset the link. To restore the PMS Link after use a busyout pms-
link, enter release pms-link. To restore the PMS Link after a test pms-link
long, enter test pms-link.
12. Error type 2561: 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 occurs frequently (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 Error Log. The PMS should be checked to
make sure that it will attempt to start the protocol according to the PMS/PBX protocol
specifications. No alarm is raised against this error.
13. Error type 2817: Look for the following Aux Data:
10x 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 occurs frequently (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 Error Log.
20x 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 occurs frequently (more than once a month), advise the
is successfully established, this error disappears from the Error Log.
30x 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 occurs frequently (more than once a month), advise the
is successfully established, this error disappears from the Error Log. No alarm is raised
against this error.
The PMS should be assessed for adherence to the PMS/PBX protocol specifications.
14. Error type 3073: 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.
15. Error type 3841: 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.
PMS-LINK demand test descriptions and error codes
Order of investigation Short test sequence Long test D/ND
sequence
Link Tear Down Test 213 on page 616 X Destructive
Link Retry Test 215 on page 618 X X Nondestructive
PMS-PRNT (PMS Printer Link)

level
PMS-PRNTJNL-PRNT MIN test journal [pms-log | PMS Printer/ Journal
wakeup-log] long Printer
WRN test journal [pms-log |
wakeup-log]
The errors and tests for PMS-PRNT also apply to JNL-PRNT.

A journal printer is a printer to which Emergency Access to Attendant, Wakeup and Property
Management System (PMS) events are printed as they occur. The PMS-log printer is used
as a backup of the PMS output device to print an audit trail of every PMS transaction and
Housekeeping Status Change event when the PMS Printer Link is not available. There may be
one or two journal printers. If there is one, every event is printed there. If there are 2, then
emergency access, wakeup events, and scheduled reports are printed at one printer (JNL-PRNT),
and PMS events are printed at the other (PMS-PRNT).
The scheduled report printer is where summaries of daily wakeup activity and emergency access
activity are printed. If the customer requests a summary report, the report will be printed exactly
once per day.
The distinction between Journal and Scheduled report printers is logical rather than physical.
Whether or not there are two printers, the scheduled reports are always sent to the printer that
journals the wakeup and emergency access events. A scheduled report will temporarily suspend
the journal activity. Upon completion of the scheduled report, journaling will be resumed after the
printing of every withheld event.
The journal printer device connects to the system via a data module (PDM, MPDM, DTDM)
connected to a port on PROCR.
PMS/JOURNAL Printer Link Maintenance provides a strategy for maintaining the link between
the system and a PMS device that is 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. If a PMS Printer Link is torn down due to an error, PMS Printer Link
Maintenance will try to bring the link up immediately. If the link setup fails, PMS Link Maintenance
PMS-PRNT (PMS Printer Link)
will wait for five minutes before the next trial. If the number of retries reaches 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 instance, the external printer device, Data Module (PDM/MPDM/
DTDM), Digital Line Port or ADU and Data Line Port). If PMS Printer Link maintenance cannot
restore the PMS Printer Link, then the maintenance tests of individual components of the PMS
Link must be executed to diagnose faults.
The list pms-down command lists every meaningful event to the PMS that occurred while the
link between the switch and the PMS was down. For example, any room status codes entered by
hotel housekeeping staff during a time of PMS outage would be reflected in this report.
Restoring the PMS Printer Link

Procedure
1. Determine the status of the PMS Printer Link.
Enter status journal-printer wakeup-log | pms-log 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-parameters hospitality and find out the destinations of
the PMS Printer Link.
3. Determine the status of the data extension.
Enter status data extension and verify that the data extension is in the in-service/
idle state. If the data extension is not available, look for the extension number in the Alt
Name field of the Error Log. See XXX-BD (Common Port Circuit Pack/Media Module) on
page 520 for resolutions.
4. 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.
5. If the problem is not found in the above steps, check the PROCR.
Result
It should be noted that when restoring the PMS printer link, it is necessary to execute tests on
different MOs that comprise the link. It is recommended that you busyout the PMS printer link
before trying to restore the link. If the PMS printer Link is busied out, then every PMS printer Link
maintenance action is deactivated, and interference with tests of other MOs is prevented.
PMS-PRNT error log entries and recommended actions

Table 112: PMS-PRNT/JNL-PRNT Error Log Entries
0 0 Any Any Any test journal wakeup-log | pms-log
18 0 busyout WRN OFF release journal wakeup-log | pms-
journal log
wakeup-log |
pms-log
257 Any Link Retry test MIN OFF test journal wakeup-log | pms-log
(#215) WRN
513 Any test journal wakeup-log | pms-log
769
Note:
sequence. Refer to each test’s description and follow its 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 for resolution.
2. Error type 18: The Journal Printer Link has been busied out and the link is torn down.
Enter release journal wakeup-log | pms-log to restore the link.
3. Error type 257: Link Retry test (#215) failed. Physical link cannot be set up, usually
because of hardware problems such as power turn off or cable disconnect. See
Procedures for Restoring the PMS Printer Link.
4. Error type 513: Physical link cannot be set up, usually because of hardware problems
such as power turn 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. 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, see Procedures for Restoring the PMS Printer Link.
5. Error type 769: Link idle timer, link comes down. The printer device is in an off-line
state, for example, paper jam or paper out. Check the printer device and act promptly
to put it back to on-line state. Enter test journal wakeup-log | pms-log to set
up the printer link.
PMS-PRNT demand test descriptions and error codes

PRI-CDR (Call Detail Recording Link)

sequence sequence

MO name in log Alarm Initial command to run Full name of
level MO
PRI-CDRSEC-CDR MIN test cdr primary | secondary long CDRlLink
CDR-LNK
WRN test cdr primary | secondary
The error entries and tests for PRI-CDR also apply to CDR-LNK and SEC-CDR.
The CDR feature records detailed call information about every incoming and outgoing call on
specified trunk groups and sends this information to a 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
device connects to the system via a data module, such as, PDM, MPDM, DTDM connected to a
port on PROCR. External CDR output devices include:
• 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
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 tries to bring the CDR link up.
If the Link Setup fails, CDR link maintenance will wait for 30 seconds before the next retry. If the
number of retries reaches a threshold of two, a minor alarm is raised for service attention.
CDR Link Maintenance does not cover the maintenance of the elements composing the CDR
physical link:
• External CDR output device
If CDR link maintenance cannot restore the CDR link, the maintenance tests of these individual
components of the CDR link must be executed to diagnose faults.
Restoring the CDR Link

About this task
Procedure
Procedure
1. Determine the status of CDR links.
Enter status cdr-link, and ensure that the CDR links are not busied out for
maintenance. If the link is down, continue to the next step.
2. Where does the CDR link connect to?
Enter display system-parameters features , and find out the destinations of CDR
links. Continue to the next step.
3. Enter status data extension, and verify whether the data extension is in the in-
service or idle state. If the data extension is not available, look for the extension number
in the Alt Name field of the error log and see XXX-BD (Common Port Circuit Pack/Media
Module) on page 520 for resolutions.
4. Is the external CDR output device available?
Ensure that the CDR output device is on-line and ready for service. Check the physical
connectivity between data module and the CDR output device.
5. If the problem is not found in the above steps, check the PROCR for any problems.
Result
When restoring the CDR link, it is necessary to execute maintenance test on different objects
that comprise the CDR link. It is recommended that you busyout the CDR link before trying to
restore the link. When the CDR Link is busied out, then every CDR Link maintenance action is
deactivated, and interference to tests of other MOs is prevented.
PRI-CDR error log entries and recommended actions

Table 113: PRI-CDR error log entries
0 0 Any Any Any test cdr-link primary |
secondary
18 0 busyout cdr-link WRN Off release cd-link primary |
primary|secondary secondary
Table continues…
257 Any Link Retry test (#215) MIN1 Off test cd-link primary |
WRN secondary l
513 test cdr-link primary |
secondary
1025
1281 Any
1 Minor alarms may be downgraded to Warning alarms based on the value used in set options.
Notes:
2. Error type 18: The CDR link is busied out and the CDR link is torn down.
3. Error type 257: Link Retry test (#215) failed. An error was detected when setting up the
link. See the preceding section Procedures for Restoring the CDR Link resolution.
4. Error type 513: The CDR physical link is down for one of the following reasons:
• 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.
a. Check the connectivity of wire and cable among wall jacket, data module, and the
CDR output device.
b. 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, see
Procedures for Restoring the CDR Link for resolution.
c. Use display system-parameters maintenance to see the start time of daily
maintenance.
d. If the error occurs and is resolved during of daily maintenance, it can be ignored.
5. Error type 1025: The CDR output device is in an off-line state, for example, due to paper
jam or paper out for a printer device. The CDR link is torn down.
a. Check the CDR output device and act promptly to put it back to online state.
b. Enter test cdr-link primary | secondary command to set up the CDR link.
6. Error type 1281: 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.
PRI-CDR demand test descriptions and error codes

sequence sequence
PROC-SAN (Process sanity audits)

MO Name in Log Alarm Initial command to run Full name of MO
level
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 does not respond to a sanity
message within an allotted time, the process will be 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, a system recovery action will be initiated.
The Process Sanity Audits MO has no alarms and no tests. Certain errors are logged to the error
log for information purposes only.
PROC-SAN error log entries and recommended actions

Table 114: PROC-SAN error log entries
Error type AUX Data Associated test Alarm level On/off Command to resolve
board the error
0 0 Any Any Any None
10 0 None None None None
204 Any None None None None
Note:
1. Error types 10 and 204: A system recovery action was 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.
RANL-STA (Remote Analog Line Station Port)
RANL-STA (Remote Analog Line Station Port)

log
RANL-STA MIN test port location long Remote Analog Line Port
(RANL-STA)
The RANL-STA MO maintains the circuitry associated with a port which has been translated as
analog station.
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 XXX-BD
(Common Port Circuit Pack/Media Module) on page 520.
Note:
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 Tests field of the
change station extension screen. This also disables Test 35 on that station.
RANL-STA error log entries and recommended actions

Table 115: RANL-STA error log entries
Error AUX Associated test Alarm On/Off Command to resolve the error
1 409604
097540
977
15 Any Port Audit and
Update test (#36)
18 0 busyout station WRN ON release station extension
extension
257 40973
513 Ringing Application WRN OFF test port location r 2
Test (#48)
769 Port Diagnostic Test MIN ON test port location r 2
(#35) WRN 1
2817 Hyperactive MIN OFF
1Minor alarms on this MO may be downgraded to Warning alarms based on the values used in
set options.
Note:
2. Error type 1: In line errors, 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.
• 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. Call the terminal
equipment and verify that the terminal rings. If the terminal does not ring, then
replace it. Otherwise, enter the test portlocation command, and follow the
procedure for Test #48.
• Aux Data 40977 indicates that terminal equipment was not connected when ringing
was attempted. Run the short test using the test port location command, and
follow the procedure for the results of Test #48.
3. Error type 15: A software audit error that does not indicate hardware malfunction. Run
the short test sequence, and investigate associated errors.
4. Error type 257: An in line error and can only be resolved over time. This error indicates
that ringing voltage is absent. If only one 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.
5. Error type 513: 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 Tests field on the change station extension screen to n. On some
software releases, this will also disable Tests #7 and 35.
6. Error type 2817: The endpoint caused a large number of control channel messages
to be sent to the switch within a short period of time, 50 or more CCMS uplinks
within 10 seconds. The station will be taken out-of-service for 30 seconds due to the
hyperactivity. This may be completely normal during heavy traffic periods.
RANL-STA demand test descriptions and error codes

sequence sequence
ONS Ringer Application Test 48 on page 582 X X ND
RDIG-STA (Remote Digital Station)
1 D = Destructive; ND = Nondestructive

level
RDIG-STA MIN test station location long Remote Digital Station
WRN test station location
The RDIG-STA MO maintains the circuitry associated with a port which has been translated as a
digital station or DCP console.
Remote digital station maintenance software provides maintenance for a port administered as a
digital station on the circuit pack. This strategy covers the in line errors log, initialization tests,
periodic tests, craft-demanded tests, and alarm resolution and escalation. Each port, translated as
a digital station on a digital line board, is running as a separate RDIG-STA MO of this type. Fault
conditions discovered on one MO may or may not indicate faults on other MOs of the same type.
Maintenance testing for the port circuitry on the combo blade circuit packs is handled by on-board
firmware and server-controlled tests. Maintenance software queries the firmware for error and
alarm information, status, and test results. Firmware automatically reports in line error conditions,
which results in server-controlled testing.
There are instances where the service state of a station is mentioned. The different service states
that apply to a remote digital line station are as follows:
Out-of-Service The port, and thus the station, have been removed from service. Busyout puts 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.
Terminal Parameters
Programmable Terminals
The following information describes how maintenance software interacts with terminal parameter
downloading:
Terminal types
1. 84xx multi button digital voice terminals, such as, 8403D01A, 8410B, 8410D02A,
8434D01A with an optional expansion module.
2. 603A1 and 603D1 callmaster terminals for telemarketing applications.
3. 302B1 and 302C1 attendant console.
Downloadable terminal parameters

The following parameters are downloaded to programmable terminals:
Table 116: Parameters downloadable to programmable terminals
Parameter Scope Terminal

International Flags (A-/mu-law, display mode, DLI voltage level) System level 84xx 603x
302B1
Primary Levels like transmission and sidetone System level 84xx 603x
302B1
Adjunct Levels like transmission and sidetone System level 84xx
Handset Expander option System level 84xx
Administrable options like speakerphone and mute button Per-terminal 84xx
Administrable softkeys Per- 8410D
terminal,syste 8434D
m level
Nonvolatile memory
Nonvolatile memory stores downloadable parameters in programmable terminals. Once the
terminal is downloaded, it is not be necessary to download it again, even if power is removed
from the terminal. If nonvolatile memory fails with the 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.
Note:
The mu-law companding mode is assigned as a default setting at the factory. For the United
States of America, a programmable terminal can place calls even though it has not been
downloaded from the system.
Download actions
There are several different scenarios which causes a terminal to be downloaded. These can occur
as part of background maintenance activity or on demand from the SAT or from a station.
For the background actions described below, the terminal downloads 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 the translation that affects the parameters of a terminal is changed as part of
system administration actions, or when a port is inserted in software as a result of board insertion
or translation change.
Automatic download actions
1. System Reboot and restart
A global download action is initiated when periodic maintenance tests begin after a
system reboot and 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
occurs. This action is required in case a terminal could not be downloaded previously,
because the terminal was off-hook when the:
• System first booted
or
• Translations associated with downloadable parameters were changed.
Note:
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 the previous table, these changes can be for a specified terminal or may be
system-wide. If the change is for a system-level parameter, a background global update
request must be submitted to download every programmable terminal.
Note:
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 begun on that terminal, if that terminal is programmable. This port
insertion action occurs under the following circumstances:
• A digital line circuit pack that is physically inserted into the system and has ports
currently administered for programmable terminals.
• A station port is added to the system by add station or change station.
• 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; however, 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 (TTI) 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 and release command
A maintenance demand busyout and release request for a station will cause the terminal to
be downloaded regardless of its previous download status.
2. Feature Access Code (FAC)
A refresh terminal parameters FAC 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 FACis assigned on the third page of the change 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.
As a result of an entry of a refresh terminal parameters FAC, the first three green call
appearance LEDs on the 84xx 603x terminal are turned on for three seconds, if the station
was successfully downloaded. This is not true for the 302B1 terminal.
There is no visible display on a station for the other background or demand download
actions. As described below, use status station and status attendant 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:
Status Terminal download state
Complete The terminal successfully downloaded sometime in the past.
Pending The system is waiting to download the terminal. This may require the execution
of a background periodic test, which could take more than an hour. As previously
described, demand download can also be used to initiate an immediate download.
Not Applicable Not a programmable terminal.
Possible reasons for no terminal download include:

• Terminal is off-hook.
• Terminal detected a bad checksum.
• Terminal detected a bad or missing EEPROM. Refer to the 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.
RDIG-STA error log entries
Table 117: RDIG-STA error log entries
Error type AUX Associated test Alarm On/off Command to resolve the error
data level board
1 1 – 20, WRN OFF
40987
location
257 40971
513 0 Digital Station Audits WRN OFF test port location r 6
#17)
767 40964 WRN OFF
769 40963 WRN OFF
40988
1025 WRN OFF
1281 Any Digital Station Audits WRN OFF test port location r 4
(#17)
1537 40968 WRN OFF
2304
2305 32770
40967
2817 Hyperactive MIN OFF
3840 40965
40989
3841 41029
Note:
2. Error type 1 with Aux Data 40987: Could be caused by 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 the voice terminal closer to the switch, in terms of feet of wire
from the jack to the switch. If the problem persists, replace the circuit pack. Once the
problem has been resolved, the alarm disappears after a predetermined amount of
time.
Error type 1 with Aux Data 1-20: Occurs 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 the
voice terminal closer to the switch, in terms of feet of wire from the jack to the switch).
If the problem persists, replace the circuit pack. Once the problem has been resolved,
the alarm disappears after a predetermined amount of time.
3. Error type 18: the port in question is busied out by maintenance personnel. Make sure
the port is released from busyout by release port location.
4. Error type 257: Indicates problems transmitting to the voice terminal, which can be
caused by defective wiring. Defective wiring can cause varying degrees of problems on
different types of sets.
5. Error type 513: The result of an ID Request failure to respond to the digital endpoint
audit.
6. Error type 767: An in line event produces this Error type when a favorable response
is received from running the Digital Line Electronic Power Feed Test 11. No action is
necessary. This alarm will be resolved with the passing of time.
7. Error type 769 with Aux Data 40963: The result of an unfavorable response to the
Digital Line Electronic Power Feed Test 11.
Error type 769 with Aux Data 40988: The EPF/PTC circuit has been turned off due to
an overcurrent condition.
Once the problem has been resolved, it may take up to one hour for the alarm to clear.
If the problem cannot be resolved by one of the steps above, replace the circuit pack.
8. Error type 1025: Problem with the voice terminal EEPROM. When the voice terminal is
repaired the alarm will be resolved with the passing of time.
9. Error type 1537: There is a 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 the 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 persists, replace the circuit pack. Once
the problem has been resolved, the alarm disappears after a predetermined amount of
time.
11. Error type 2305 with Aux Data 32770: 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 action
is necessary.
Error type 2305 with Aux Data 40967: An off-board warning was generated due
to a 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 the voice terminal
to a jack that is closer to the switch, in terms of feet of wiring between the jack and the
REM-OFF (Remote Office)
switch. If the problem persists, replace the circuit pack. Once the problem has been
resolved, the alarm disappears after a predetermined amount of time.
12. Error type 2817: The endpoint caused a large number of control channel messages
to be sent to the switch within a short period of time (50 or more CCMS uplinks
within 10 seconds). The station will be taken out-of-service for 30 seconds due to the
hyperactivity. This may be completely normal during heavy traffic periods.
13. Error type 3840 with Aux Data 40965: No terminal is connected to the board. No
maintenance action is required. This is also the code that is generated when the link
between the circuit pack and the voice terminal is successfully reset. No action is
necessary.
Error type 3840 with Aux Data 40989: Indicates an uplink message has been logged
indicating that the Electric Power Feed (EPF) is on with no load on it. No action is
necessary.
14. Error type 3841: 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.
RDIG-STA demand test descriptions and error codes
sequence sequence
1D= Destructive ND = Nondestructive
REM-OFF (Remote Office)

MO name in log Alarm level Initial command to run Full Name of MO
REM-OFF MIN ping node-name node-name Remote Office
WRN ping ip-address location
An instance of this MO (REM-OFF) is associated with every Remote Office box that is
administered on the switch. This MO monitors keep-alive and periodic PING test failures.
Use ping ip-address or ping node-name to ping the Remote Office.
REM-OFF error log entries and recommended actions

Table 118: REM-OFF error log entries
Error type Aux Associated Alarm On/off Command to resolve the error
data test level board
1 MIN OFF ping node-name node-name ping
ip-address addr
257 Log only OFF ping node-name node-name ping
ip-address addr
Note:
1. Error type 1: A ping test to the remote office has failed and a MINOR alarm has
been raised. When this error is logged, as many as 26 endpoints associated with that
remote office and several H.323 signaling groups could be out of service.
2. Error type 257: The response to a keep-alive update request exceeded the time limit
for an endpoint. The error is a log-only error. It is not possible to determine which entity
has failed.
The aux data associated with this error indicates whether the endpoint that failed to
respond was a DCP, analog, or signaling group type:
• 1096 = Analog Line
• 1095 = DCP Line
• 6179 = H.323 Signaling Group
RING-GEN (Analog Ring Generator)

level
RING-GEN MAJ test environment location Analog Ring Generator
Analog phones must be provided with a voltage that allows them to ring. The Analog Ring
Generator provides the ringing voltage for every analog telephone associated with a given
gateway.
Failure of the ring generator results in loss of ringing on analog phones. Ringing on digital and
hybrid phones is not affected.
SEC-CDR (Call Detail Recording Link)
RING-GEN error log entries and recommended actions

Table 119: RING-GEN error log entries
0 0 Any Any Any test environment location
1 Ring Generator Query MAJ ON test environment location r 3
(#118)
Note:
SEC-CDR (Call Detail Recording Link)

See Call Detail Recording Link (PRI-CDR) for maintenance procedures for SEC-CDR.
SIP-BCH (SIP B-Channel)

Session Initialization Protocol (SIP) signaling groups are similar in concept to ISDN PRI signaling
groups. No physical hardware components make up the SIP B-channel or SIP D-channel objects
discussed here, and no maintenance tests are run.
The SIP signaling group can be considered to be one D-channel that physically rides on a PROCR
port and the IP network. Unlike ISDN D-channels, the SIP D-channel may come up and down on
a call-by-call basis. The SIP D-Channel is actually a TCP/IP signaling channel. Layers 1 and 2 of
this signaling channel can be monitored by IP PING testing.
SIP B-channels use Media Processor ports to carry the actual bearer. Any port of a media
processor may serve an H.323 station or a SIP B-channel. Status information may exist for a
specific SIP B-channel. A SIP B-channel may be busied out and released.
Errors are logged for command busyout conditions. Under normal conditions, the system
automatically places SIP B-channels into or out of service when it receives a SIP signaling-group
service state update. A demand busyout drops active calls.
SIP-BCH error log entries and recommended actions

Table 120: SIP-BCH B-Channel Error Log Entries
Error Aux Associated test Alarm On/Off Service

type data level board state
18 Any B-channel busied out by command Warning off OOS
System commands
The following commands are available:
Command Description
Busyout port location The command to disconnect an active call on a
specific H.323 B-Channel and reduce the capacity
of the trunk group by one. No physical piece of
hardware is removed from service.
Release port location On a specific H.323 B-Channel, increases the trunk
group’s capacity by one. No physical piece of
hardware is actually added to service.
Status trunk grp#/mem# Finds 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 location Displays No tests applicable to this
object.
SIP-SGRP (SIP Signaling Group)

level
SIP-SGRP MIN test signaling-group grp# SIP Signaling Group
WRN
The SIP Signaling Group (SIP-SGRP) MO supports a signaling channel (D-channel) for SIP
trunk connections. The G4xx Media Gateways and Avaya Aura® Media Server provide audio
connectivity, working in concert with a PROCR which provides control signaling to support a SIP
connection.
The SIP signaling group (SIP-SGRP) is a signaling channel that physically resides on a IP-
PROCR and the IP network. Unlike ISDN D-channels, the SIP channel may actually come up and
down on a call by call basis. The SIP channel is actually a TCP/IP signaling channel. Layers 1 and
2 of this signaling channel are monitored by IP PING testing.
SIP-SGRP error log entries and recommended actions

Table 121: SIP-SGRP Error Log Entries
1 Any Ethernet Port Status test MIN OFF test signaling-group grp#
(#1386)
18 0 busyout signaling-group WRN OFF release signaling-group
grp# grp#
257 Any Signaling Group Ping (#1387) MIN OFF test signaling-group grp#
258 IP Signaling Group Far-end
Status Test (#1675)
513 Any Signaling Group Ping (#1387) WRN OFF test signaling-group grp#
770 Any WRN OFF
1025 Any MEDPRO Status test (#1392) MIN OFF test signaling-group grp#
1281 Any MEDPRO Status test (#1392) MIN OFF
1537 Any IP Signaling Group Far-end MIN OFF test signaling-group
Status Test(#1675) group#
1794 MEDPRO Status test (#1392) MIN OFF test signaling-group grp#
2561 Any Registered to Survivable MIN OFF
Remote Server Inline Error
3073 19 Far-end TLS Certificate Failure MIN OFF
Inline Error
3329 21 Near-end TLS Certificate MIN OFF
failure Inline Error
3585 IP Signaling Far-end Status MIN OFF
Test (#1675)
3841 -
3942
Note:
procedures.
2. Error type 1: Failure of IP-PROCR carrying the signaling group channel.
3. Error type 18: The signaling group has been busied out by command. Release the
signaling group, if appropriate, with release signaling-group grp#.
4. Error type 257: Tracks failures of the SIP signaling-group PING test. See Signaling
Group Ping Test (#1387) for test failure information.
5. Error type 258: Tracks failure of the primary signaling channel.
When the far-end signaling group encounters a primary signaling link which is down,
it starts sending Polling Subscriptions to Communication Manager on a secondary
signaling link. Communication Manager runs the IP Signaling Group Far-End Status
Test (#1675) to validate if the primary signaling link is not working properly. Following
are the possible outcomes:
• If the test fails, the primary signaling link is withdrawn from service and an alarm is
raised.
• If the test passes, the primary signaling link is fixed back to service and the alarm is
retired.
6. Error type 513: Tracks excessive round-trip delay of the SIP signaling-group PING test,
if the round-trip delay exceeds 4 seconds. See Signaling Group Ping Test (#1387) for
test failure information.
7. Error type 770: Tracks excessive latency and packet-loss from background IP
measurements collected by the Media Processor Board. 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 ip-options form. Exceeding these
thresholds indicates that the IP network may not be providing sufficient quality
of service for adequate transmission of voice. If the signaling group has been
administered to enable BYPASS, then Error Type 1025 also occurs.
8. Error type 1025: The signaling group has been placed into a BYPASS condition
because of IP network congestion. The signaling group accepts incoming calls, but
every outgoing call is denied. The system routes these calls over a secondary route, if
one has been administered.
9. Error type 1281: 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 SIP B-channels to be in an out-of-service near-end state.
10. Error type 1537: 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 Communication Manager server, this
error means the server on the other end does not have MEDPRO in-service for its
signaling group.
This error places the SIP B-channels into an out-of-service far-end state.
11. Error type 1794: The Signaling Group reported that the far end has detected excessive
packet latency or loss. This error places the SIP B-channels into an out of service
far-end state.
12. Error type 2561: The signaling group is registered to a Survivable Remote Server.
13. Error type 3073: A TLS connection was established with the far-end but authentication
with the far-end’s TLS certificate failed. Due to this condition, the signaling group will
be placed in far-end bypass state so that no outgoing calls will be allowed,. The trunks
in the group will be placed in an out of service far end state (OOSFE). Incoming calls
will be accepted, but until the far-end’s TLS certificate is remedied, these will not be
successful. Once the far-end’s certificate is remedied, an incoming call can succeed
and the trunk group will be put back in service.
14. Error type 3329: The near end TLS certificate is bad. The trunks in the group will
be placed in a near end out of service state and the signaling group will be placed
in bypass. No trunk calls either incoming or outgoing will be allowed until the near
end’s certificate is corrected. The system is warm started (reset system 1), and the
signaling groups go through a busy/release action. If the near end certificate is bad,
listen sockets fro the signaling group will not be created, so this alarm is raised at the
creation of the listen socket stage that is when initially bringing the signaling group into
service.
Note:
Near end certificate authentication is the process of validating that the server
certificate is OK, i.e., we have the private key and the certificate is trusted. This will
only break if a user with root access has changed the certificate private key file.
15. Error type 3585: IP Signaling Far-end Status Test failed. The far-end is not available.
See IP Signaling Group Far-End Status Test (#1675) for more information.
16. Error types 3842 - 3942: These Error Types report certain error messages received
by the SIP Signaling Group for one of its associated D-channels. The aux data field
shows for which D-channel the message was received.
The generated error code is represented by the value 3840+x, where x is the Cause
Value. The Cause Value provides additional data that may be useful when tracking
down obscure networking and routing problems.
Table 229: Descriptions and Recommendations for Error Types 3842-3942 provides
a description of the error code and the recommended actions to troubleshoot the
problem.
Table 122: Descriptions and Recommendations for Error Types 3842-3942
Error Description/Recommendation
Code
3842 Cause Value 2. A request has been made to use a transit network or common
carrier that cannot be accessed. The equipment sending this cause event does
not recognize the transit network.
a. From the circuit pack or media module and port number in the Aux Data field,
determine the trunk group against which the error was reported.
b. Check every routing pattern containing this trunk group for validity of
interexchange carriers requested (IXC field).
Table continues…
Code
3843 Cause Value 3. No route to destination. Request received to route call through a
transit network that is recognized but not allowed to carry the call or not able to
serve the destination. The service provider cannot route the call to the indicated
destination. Communication Manager does not originate Cause Value 3.
The repair steps are based on Tier 4 recommendations:
a. Check the numbers sent for any missing prefixes or service values that were
needed to access the network.
b. Check the Cause Information Element Location Code.
c. Check Communication Manager administration:
a. Dial plan/Location: The home NPA is administered incorrectly, causing
incorrect code conversion.
b. IXC: The IXC matching pattern is administered incorrectly or not at all on
the dial plan, causing incorrect IXC manipulation.
c. AAR/ARS digit conversion: The wrong digit string substitution is being
made. The call is being routed into the wrong network and over the
wrong route pattern. Further conversion is needed but the dial string is
restricted from further conversion.
d. AAR/ARS digit analysis: Call type is incorrect for the call being made
specifying the wrong type of number and/or number plan information, or
it is preventing code conversion from taking place. Call is being routed to
the incorrect route pattern where the incorrect digit manipulation and/or
code conversion is taking place.
e. ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect
code conversion at the route pattern.
f. Route pattern: Incorrect code conversion due to wrong entries in NPA,
prefix mark, and toll list/prefix mark fields. Deleting the wrong number
of digits or inserting the wrong digits. Failing to strip IXC or international
code digits, stripping a user-dialed IXC code, or IXC forcing the call to
the wrong inter-exchange carrier. Number format changed to a format
incorrect for the call type. The incorrect service or feature is specified for
the call being made on a CBC trunk group preference.
Table continues…
Code
3846 Cause Value 6. 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. It could also reflect
the occurrence of a normal race condition. For example, the local switch has
requested use of a B-channel that the far-end switch had just reserved for use on
another call.
b. Enter status trunk for the indicated trunk. Refer to DS1 ISDN Trunk
Service States and ISDN-PRI Trunk Service States sections of ISDN-TRK
(DS1 ISDN Trunk) for recovery suggestions.
3858 Cause Value 18. The switch sent a message to the far-end switch or terminal
adapter that did not respond in the time allowed. The remote device/endpoint
did not respond with an ALERTING/PROGRESS/CONNect indication within the
time administered in the T303 or T310 timers Q.931 specification. Cause Value
18 indicates high traffic conditions in the serving network or noisy conditions
on the span carrying the D-channel messaging. The noise is causing the loss
of messages being sent to the remote device. The remote device might also
be unable to respond to the incoming SETUP message. This Cause Value has
end-to-end significance and should always be passed back through the network
to the user.
3878 Cause Value 38. 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. The
network is out of order.
b. Consult with the network provider to determine the nature and expected
duration of the out-of-service condition.
c. Consider modifying every routing pattern containing this trunk group to route
calls around the network that is out of service.
Table continues…
Code
3890 Cause Value 50. A request to use a network service has been denied.
Administration somewhere on the network has indicated that the requested
service has not been subscribed to or purchased for this trunk.
This could be a local administration problem only, or a mismatch between the
local administration and that of the network provider.
a. From the media module and port number in the Aux Data field, determine the
trunk group against which the error was reported.
b. Display the trunk group form: If the trunk group is Call-by-Call (Service Type
is cbc), check every routing pattern form 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.
c. If local administration is 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 Cause Value 52. Protocol detail; may offer a clue if customer is having calls
denied with an unexpected intercept tone. If the customer is complaining of
unexpected intercept tones and no other cause can be found, escalate the
problem and provide the next tier with this Error Log information.
3894 Cause Value 54. Protocol detail; may offer a clue if customer is having calls
denied with an unexpected intercept tone. First, eliminate any transitory state
mismatch problems by entering test port location for the trunk port shown
in the Aux Data field. Service State Audit Test (#256) is the important test in the
sequence. If this passes satisfactorily, yet the customer continues to complain
of unexpected intercept tones and no other cause can be found, escalate the
3902 FRANCE ONLY: Cause Value 62. Service not authorized.
Call rejected. This Cause Value has end-to-end significance and should always
be passed back through the network to the user.
Cause Value 62 (VN4) indicates that the call could not be completed because
the user has not subscribed to the service, feature, or supplementary service
requested in the SETUP message. If the user is supposed to have access to
this service, feature, or supplementary service, complete the required ordering
process with the service provider.
Cause Value 62 (1TR6) indicates that the remote endpoint does not accept this
call, although it could have accepted the call because the equipment is neither
busy nor incompatible. The diagnostic information in the Cause information
element might contain the user-supplied condition for why the call was rejected.
Table continues…
Code
3903 Cause Value 63. Service or option not available, unspecified. This cause value 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. This Cause Value shall either
be passed to the user or mapped to Cause Value 41 (temporary failure) when it is
received at a CO as part of SS7 call handling. Communication Manager does not
originate Cause Value 63.
3905 Cause Value 65. Protocol detail; may offer a clue if customer is having ISDN
calls denied with an unexpected intercept tone. If the customer is complaining
of unexpected intercept tones and no other cause can be found, escalate the
3906 Cause Value 66. Protocol detail; may offer a clue if customer is having ISDN
calls denied with an unexpected intercept tone. If the customer is complaining
of unexpected intercept tones and no other cause can be found, escalate to the
3909 Cause Value 69. A request to use a network service has been made, but
the network has rejected the request because the requested service is not
implemented. Follow the recommendation for Error Type 3890, Cause Value 50.
3910 Cause Value 70. Only restricted digital bearer capability available. The call
could not be completed because the equipment sending this Cause Value only
supports the restricted version of the requested bearer capability, and in the
SETUP message, bearer capability was unrestricted. Communication Manager
does not originate Cause Value 70.
The repair steps are based on recommendations from Tier 4 ISDN experience:
a. Check Communication Manager administration (network generated the
Cause Value):
a. Route pattern: An incorrect ITC and/or BCIE specified. These fields
affect how the bearer capability is encoded in the SETUP message.
b. The ITC administered on the originating endpoint might be incorrect for
this call and/or the speed options in the device itself might be incorrect
for calls over these ISDN facilities.
c. Incorrect data speed option is set in the BRI device, causing a call from
a BRI endpoint tandeming through Communication Manager to create a
SETUP message with the wrong bearer capability.
d. A call tandeming through Communication Manager ISDN trunk group to
ISDN trunk group might have a bearer capability that is not supported by
the outgoing ISDN facilities or network.
e. A call tandeming through Communication Manager on a non-ISDN trunk
group inter-working to an ISDN trunk group might have an incorrect
bearer capability assigned on the incoming trunk group. The BC and ITC
fields on the incoming trunk group may be set wrong.
Table continues…
Code
3919 Cause Value 79. Service or option not implemented or unspecified. The call could
not be completed because the equipment sending this Cause Value has not
implemented a service, feature, or supplementary service requested by the user,
and none of the other Cause Values in the Service or Option Not Implemented
class apply. As an implementation option, this Cause Value might be mapped to
Cause Value 41 (temporary failure) when it is received at a CO as part of SS7 call
handling. Communication Manager does not originate Cause Value 79.
3928 Cause Value 88. A call was denied because a basic incompatibility existed
between the type of call and either the facilities selected by the routing pattern or
the called user. This error may offer a clue if the customer complains of receiving
unexpected intercept tone.
a. Determine the trunk group from the media module and port number in the
Aux Data field.
b. Check the BCC fields of the pertinent routing patterns.
c. Investigate whether or not the calling and called endpoints are compatible.
For example, some switches may not allow a voice station to call a data
extension.
Table continues…
Code
3942 Cause Value 102. Recovery on timer expiry. No answer to CALL PROCEEDING.
The equipment sending this Cause Value sent or received a Layer 3 Q.931
message. Sending or receiving this message has initiated a Layer 3 timer that
has expired. This Cause Value is being generated in conjunction with Q.931
protocol error handling procedures. The ISDN network between the user and the
equipment generating the Cause Value might:
• Send no cause indication through the network.
• Send a more generic Cause Value through the network.
The repair steps are based on recommendations from Tier 4 ISDN experience:
a. Check the diagnostic information for the timer number that has expired.
b. Check that the protocols at each end of the interface match. For example,
both sides are NI-2.
If the ends of the interface are running different protocols, they might be
running with different values for their Layer 3 timers. If the protocols at each
end of the interface match, the Communication Manager timer might have
expired because:
a. The far-end never saw the message because the message was
corrupted in transmission by noise on the D-channel. Check for any type
of T1/E1 facility errors.
b. The far-end is experiencing a high traffic condition and did not have the
processing time to parse the sent message before the timer expired.
c. Even though the message was seen to be generated in an internal
Communication Manager trace, the message was never transmitted
out onto the D-channel. Perform an external protocol capture on the
D-Channel to confirm the transmission of the suspect message.
Table continues…
Code
3942 a. To interpret the receipt of Cause Value 102 from the far-end, look at a trace/
(cont’d) protocol capture of the messaging taking place, and find the last message
received from the far-end before Cause Value 102 is received. The timer that
expired is most likely the Layer 3 timer associated with that last message. If
Communication Manager generated a message in between those two events
that should have stopped the timer, the cause might be:
a. The far-end never saw the message because the message was
corrupted in transmission by noise on the D-Channel. Check for any
type of T1/E1 facility errors.
b. The far-end is experiencing a high traffic condition and did not have the
processing time to parse the sent message before the timer expired.
c. Even though the message was seen to be generated in an internal
Communication Manager trace, the message was never transmitted
out onto the D-Channel. Perform an external protocol capture on the
D-Channel to confirm the transmission of the suspect message.
b. If Communication Manager did not respond to the receipt of the last
message from the far-end, then Communication Manager internal hardware
and software become suspect, and troubleshooting the problem must
proceed from that point.
c. Communication Manager administration that can contribute to seeing timer
expiry errors:
a. Trunk group form: Incoming call handling table. If the Per call
CPN/BN field is incorrectly populated in comparison to how the CO is
programmed to send CPN or BN, it causes Communication Manager to
send a FACILITY message to the CO requesting CPN/BN information
and the CO will never respond. Communication Manager will log many
timer expiry errors against the signaling group (Error Type 1, Aux Data
13).
b. DS1 form: Protocol version: If Communication Manager is running
custom protocol (protocol version A) and is connected to a Nortel DMS
central office running custom protocol, Communication Manager will
log timer expiry errors against the signaling group for DISCONNECT
problems (Error Type 1, Aux Data 4) during high traffic conditions.
3942 a. The DMS CO custom protocol implementation uses the ANSI recommended
(cont’d) timer values for their Layer 3 timers while Communication Manager uses
the ITU recommended timer values. The T305 timer in Communication
Manager is 4 seconds while the same timer in the DMS is 30 seconds. This
difference causes timer expiry problems in high traffic conditions. Change
Communication Manager’s protocol version to c to line up the timers.
SP-REG-M (Survivable Processor-Main)
SIP-SGRP demand test descriptions and error codes

sequence sequence
C-LAN Ethernet Port Status Test 1386 on page 743 X X ND
MedPro Status Test 1392 on page 750 X X ND
Signaling Group Ping Test 1387 on page 746 X X ND
IP Signaling Group Far-End Status Test 1675 on page 768 X ND
SP-REG-M (Survivable Processor-Main)

SP-REG-M MAJ None Survivable Processor-Main
MIN
The Survivable Processor object monitors keep-alive message between the main server and the
survivable processor, which can be either:
• Survivable Remote Server
• Survivable Core Server
The server exchanges keep-alive messages with each of the survivable processors. If the server
does not receive a predetermined number of those messages, both the server and the survivable
processor alarm. If a Survivable Remote Server does not register with a Survivable Core Server, it
registers with either the main server or another Survivable Core Server and alarms are not raised.
Possible causes for SP-REG-M alarms include:
• The network is down.
• The server or survivable processor administration is incorrect.
SP-REG-M error log entries and recommended actions

Table 123: SP-REG-M error log entries
data level Off
board
1 0-63 MIN OFF status ess-cluster
769 0 MAJ OFF
Note:
1. Error type 1: no keep-alive signal from the Survivable Core Server. The Aux Data value
displays the number of unregistered and alarmed Survivable Core Server clusters (0 -
63). Possible causes include:
• The main server is down.
a. Use the status ess-cluster command to determine which survivable
processor is not registered.
b. Determine the network outage or administration problem for this processor.
2. Error type 769: invalid or wrong NIC address. Unable to access the IP address of the
native NIC. Use the Maintenance Web Page to verify or configure the NIC address
Server Configuration > Configure Server > Configure Individual Services >
Configure Interfaces.
SP-REG-S (Survivable Processor)

MO name in log Alarm Level Initial command to run Full name of MO
SP-REG-S MAJ None Survivable Processor
MIN
The Survivable Processor object monitors keep-alive message between the main server and the
survivable processor, which can be either:
• Survivable Remote Server
• Survivable Core Server
The server exchanges keep-alive messages with each of the survivable processors. If the server
does not receive a predetermined number of those messages, both the server and the survivable
processor alarm.
Possible causes for SP-REG-S alarms include:
STRAT-3 (Stratum-3 Clock)
SP-REG-S error log entries and recommended actions

Table 124: SP-REG-S Error Log Entries of
data level Off
board
513 0 MIN OFF
769 0 MAJ OFF
Notes:
1. Error type 513: the survivable processor, Survivable Core Server or Survivable Remote
Server is unregistered. Possible causes include:
• The main server is down.
2. Error type 769: invalid or wrong NIC address. Unable to access the IP address of the
native NIC. Use the Maintenance Web Page to verify or configure the NIC address
Server Configuration > Configure Server > Configure Individual Services > Configure
Interfaces.

STRAT-3 MAJ test synchronization Stratum-3 clock
MIN
The Digital Synchronization Network Plan (PUB 60110) specifies a hierarchy of synchronization
nodes consisting of Strata 1 to 4, where the public network’s sole Stratum-1 clock is the most
accurate. Release 5r and later systems support both Stratum-3 and -4 operations. See Stratum-4
Synchronization for details on Stratum-4 operation.
A Stratum-3 clock derives its timing from two DS1 references connected to a Stratum-3 or better
source. The Stratum-3 clock provides a holdover of at least 24 hours should both DS1 references
fail. After 24 hours, the Stratum-3 clock still provides service but its accuracy may be degraded.
The Digital Synchronization Network Plan (PUB 60110) requires that the Stratum-3 clock have
duplicated components.
The Stratum-3 clock can be configured with only one DS1 input if one of the Clock Input cards is
removed. Also, the Stratum-3 clock can free run use its internal clock without using DS1 inputs, if
both Clock Input cards are removed.
The only operation that software can perform is a query of the alarm leads. The only recovery
action that can be performed on a catastrophic failure of the Stratum-3 clock is using the local
oscillator on the G4xx Media Gateway. Neither software nor the G4xx Media Gateway can request
additional information about the health of the Stratum-3 clock other than the information provided
by the alarm leads. Furthermore, neither the software nor the G4xx Media Gateway can request
that the external clock switch references, change configuration, disable or enable, initialize, and so
forth.
In the system, the Stratum-3 clock has been implemented as an external which follows the
specification in PUB 60110 for Stratum 3. The only external Stratum-3 clock that is supported
is the Telecom Solutions Digital Clock Distributor for Customer Premise Timing (DCD-CPT)
Stratum-3 clock. Figure 73: Stratum-3 Clock Hardware Configuration shows how the Stratum-3
hardware configuration provides clock and alarm signals to the G4xx Media Gateway. The
reference DS1 facilities connect directly to the Stratum-3 clock for timing purposes, but the DS1
data may be routed into the switch by using a Y connector H-600-274 G1 for the 50-pin DS1 end
or H-600-274 G2 for the 15-pin DS1 end.
Figure 10: Stratum-3 Clock Hardware Configuration
Stratum-3 Clock LED Strategy

Note:
When looking in the Stratum-3 cabinet, A card is on the left and B card is on the right.
The normal LED scheme is not followed for this device. Green LEDs do not indicate maintenance
activity. There are no yellow LEDs, and there are more than three LEDs per circuit pack.
Removal of a card in the Stratum-3 clock may cause alarms to be resolved and the query test to
pass. However, the removed cards should still be replaced to restore the Stratum-3 clock to full
service.
The Stratum-3 clock has the following components:
• 2 Clock Input cards (CI)
Provides the logic to select the DS1 reference or Clock Input card. The red FAIL LED on this
card indicates a failure with the card or the DS1 reference connected to it.
• 2 Stratum-3 Cards (ST3)
Provides 24-hour holdover. The red FAIL LED on this card indicates a failure with the card.
Replace the card.
• 2 Timing Output Cards (TOC)
Provides cable length compensation, multiple output ports, selection of the ST3, and CI
outputs. This type of card has two red failure LEDs: one indicates a failure of the card, the
other indicates a failure in one or more output ports. In either case, replace the card.
• 1 PBX (Private Branch Exchange) Alarm Interface (PAI)
Filters power supplied to the clock, provides fuse protection, and provides alarm indications
based on inputs supplied by other cards. The six LEDs on this card provide indications for the
six alarm or status conditions as follows:
- Loss of DS1 reference A
- Loss of DS1 reference B
- Loss of one clock unit
- Loss of both clock units
- Loss of one power supply
- Loss of both power supplies
The output of the CI and PAI cards go directly to the TN780 Tone-Clock circuit pack via two
25-pair amphenol terminated cables. Every card has red and green LEDs for providing status or
alarm indications. The abbreviations used in the table are defined above except for SRC (source)
and Phase Locked Loop (PLL).
Table 125: Stratum-3 Clock LED Indications of
Card Name Color Indication

PAI REF A Red Loss of input reference A or CI A failed
REF B Red Loss of input reference B or CI A failed
ST A Red Failed Stratum-3 clock A
Table continues…
ST B Red Failed Stratum-3 clock B

PWR A Green -48VDC A present
PWR B Green -48VDC B present
CI FAIL Red Card failure
DS1 Green DS1 source present
CC Green Composite clock source64 present
SRC ACTIVE Green Card is currently on-line
ST3 FAIL Red Card failure
LOCK Red PLL lost sync with reference or holdover mode
REF A Red Timing Reference from CI A
REF B Red Timing Reference from CI B
TOC FAIL Red Card failure
PORT ALM Red Output port alarm (one or more)
ST Green Reference present from ST clock
INPUT Green Reference present from CI
500’ Green 500-foot phase advance
1000’ Green 1000-foot phase advance
64Composite Clock (CC) source refers to the protocol used to electrically transfer timing from the
Stratum-3 clock to the switch. The Composite Clock source is not relevant to the system.
STRAT-3 error log entries and recommended actions

Table 126: STRAT-3 error log entries

type data level Off
board
0 0 Any Any Any test synchronization r 4
1 Any Stratum-3 Clock Alarm Query MIN OFF test synchronization r 4
(#649)
18 0 disable sync WRN OFF enable sync
257 Any Stratum-3 Clock Alarm Query MIN OFF test synchronization r 4
(#649)
513 Any Stratum-3 Clock Alarm Query MIN ON test synchronization r 4
(#649
(#649)
(#649) MAJ ()
Table continues…

type data level Off
board
(#649) MAJ ()
1537 MIN ON
MAJ ()
1793 MIN ON
MAJ ()
Note:
2. Error type 1: this Error type corresponds to FAIL code 1 of the Stratum-3 Clock Alarm
Query (#649): Either reference A failed or the CI card A failed.
3. Error type 18: Synchronization Maintenance was disabled with disable
synchronization.
a. Enter enable synchronization to enable Synchronization Maintenance
reference switching and to resolve this alarm.
4. Error type 257: this Error type corresponds to FAIL code 2 of the Stratum-3 Clock
Alarm Query (#649): one power supply failed.
Alarm Query (#649): one clock unit failed.
Alarm Query (#649): either reference B failed or the CI card B failed.
Alarm Query (#649): every power supplied failed.
A Minor alarm results if the Stratum-3 clock can still provide timing to the switch;
otherwise, a Major alarm will be raised because the Stratum-3 clock is not providing
timing and the switch is referencing the local oscillator on the TN780 Tone-Clock circuit
pack. If only the active TN780 Tone-Clock circuit pack is faulty, the standby TN780
Tone-Clock circuit pack becomes active and remains synchronized to the Stratum-3
clock. When the system switches to the standby Tone-Clock circuit pack, the alarm is
resolved, and a TDM-CLK alarm is raised to indicate a possible problem on the TN780
Tone-Clock circuit pack.
If the alarm is MINOR:
a. Look for a red LED on either or both TOC cards.
b. If there is a red LED, replace the card. If there is no red LED, use the Stratum-3
Wiring Guide, and check that the wiring installation is correct.
c. After replacing the card or correctly rewiring the installation, clear the
alarm by entering disable synchronization, followed by enable
synchronization. The latter procedure causes synchronization software to
switch back to using the Stratum-3 clock again.
d. Wait 2 minutes and run status synchronization.

e. If Maintenance Name on the status screen shows STRAT-3 the problem is
resolved.
Caution:
The disable synchronization command followed by enable
synchronization may cause slip alarms. The circuit packs that can
experience slips and the associated error log entry for slips are listed in Table
241: Timing Slip Error types.
Table 127: Timing slip Error types
Circuit pack name Error log name Error log number of slips
DS1 Interface DS1-BD 3073 to 3160
Expansion Interface EXP-INTF 2305
Switch Node Interface SNI-BD 1537
Tone-Clock TDM-CLK 1025
UDS1 Interface UDS1-BD 3073 to 3160
If the alarm is MAJOR:

• Check connections between the Stratum-3 clock and the switch.
• If there are no loose connections, use the Stratum-3 Wiring Guide and check that the wiring
installation is correct.
• After reconnecting the loose connection or correctly rewiring it, clear the alarm by entering
disable synchronization, followed by enable synchronization.
• Wait 1 minute, then run status synchronization.
• If Maintenance Name on the status screen shows STRAT-3 then the problem is resolved.
If the Standby Tone-Clock circuit pack became active:
• Check the connection between the Stratum-3 clock and the TN780 Tone-Clock circuit pack
from which the system has just switched.
• If there are no loose connections, then, replace the circuit pack containing the TN780 Tone-
Clock circuit pack.
• Before switching back to the new TN780 Tone-Clock circuit pack, use test tone-clock
location long to check that the Tone-Clock is receiving a signal from the Stratum-3 clock.
• If every test passes, switch to the new Tone-Clock circuit pack using set tone-clock
location override.
• If Test #651 fails, then the original TN780 Tone-Clock circuit pack should be reinserted, and
the cable between the Stratum-3 clock and the TN780 Tone-Clock circuit pack should be
replaced.
• If Test #651 continues to fail, then escalate the problem.
• If slip alarms exist after following the repair procedures for any of the previous cases, clear
the slip alarms by running test board clear. See Table 241: Timing Slip Error types for a
list of circuit packs and associated slip error log entries.
• This error indicates that the Tone-Clock circuit pack in the master port network is not a
TN780. If duplicate Tone-Clock circuit packs exist in the master port network, this error may
mean that one or both Tone-Clock circuit packs are not TN780s. Verify that the Tone-Clocks
in the master port network are TN780s.
1. Error type 1281: this Error type corresponds to FAIL code 32 of the Stratum-3 Clock Alarm
Query (#649): every clock unit failed.
2. Error type 1537: An OFF-BOARD alarm on the Stratum-3 clock, indicates a DS1 facility
problem; an ON-BOARD alarm indicates a fault in either the Stratum-3 clock or the
connection between the Stratum-3 clock and the switch. If the Stratum-3 clock cannot
be referenced and the local oscillator on the TN780 Tone-Clock circuit pack must serve as
the reference, a Major alarm is raised. Otherwise, a Minor alarm is raised.
3. Error type 1793: this error can be caused by one of the following conditions:
• One or both Timing Output Cards (TOCs) has failed.
• The connection between the Stratum-3 clock and the TN780 Tone-Clock circuit pack is
faulty.
• The TN780 Tone-Clock circuit pack is defective.
SYS-LINK (System Links)

SYS-LINK MIN test sys-link location SYSTEM LINKS
WRN
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.
Various types of links are defined by their endpoints:
PRI ISDN-PRI D-Channel Link terminating at a Universal DS1 board
Recording System Link Events

The system records every error encountered on the system links. Most of these events are not
extraordinary unless they occur very often. The events are logged as they occur, leaving a trail
to help analyze abnormal behavior exhibited by the endpoints attached to the links or the links
themselves.
When a link goes down, an alarm is raised immediately. For EAL, INL, BFDL, and PACL link
types, a MINOR alarm is raised. For every other link type, a WRN alarm is raised. Other alarming
conditions that do not cause the link to go down get a WRN alarm, regardless of the link type.
Identifying a System Link

To trace problems associated with a system link, it is necessary to find its location. Use the
following methods to find the location of the system link.
Display Errors or Alarms
The output of display errors or display alarms 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 sys-link in the Category field on the input screen. The link type and
channel number, if any, are listed under the Alt Name field of the report.
List sys-link
The list sys-link command lists every system link location, link type, and dlci number
present in the system.
System 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 status sys-link location and list sys-link. 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.
Repairing system links

About this task
The status sys-link location command shows the state of both the hardware paths
(current and faulted) along with the state of each of the components in the hardware path.
Procedure
Procedure
1. Look for alarms on the components listed under desired hardware path.
2. If any alarms are present, then follow the maintenance procedures for the alarmed
components to clear those alarms first.
3. When every component is alarm free, wait for 3 minutes to allow the links to recover.
4. Test the system link test sys-link location long clear, and notice any tests that
fail.
5. If there are any failures, fix the problems indicated by the tests and repeat the procedure.
SYS-LINK error log entries and recommended actions

Table 128: SYS-LINK error log entries

type data level Off
board
13 System Link Status MIN OFF
(#985) WRN
257 WRN OFF test sys-link location l cl
Notes:
1. Error type 13: the link went down. The link may have gone down or never come up. Enter
status sys-link location and check the value of the Faulted Path field. If the value
is default, then the link never came up. If the value is present, then the link came up and
then went down.
a. Follow the information in Common Procedure for Repairing Link Problems.
b. Wait for 3–5 minutes before checking the link state.
c. Repeat the procedure until there are no problems.
2. Error type 257: the link has experienced uplink flow control, and the endpoint may be
hyperactive. The system link is alarmed if 4 or more errors of this type are detected within
10 minutes.
b. Clear errors and wait for 10 minutes.
3. Error type 513: the link has experienced downlink flow control, meaning that some
information packets from the packet interface board have been lost. The link is reset on
first occurrence and Error 1025 is also logged. The system link is alarmed if 2 or more
errors of this type are detected within 10 minutes.
4. Error type 772: the link experienced a temporary disconnect due to excessive resets or
state transitions, meaning 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.
5. Error type 1025: the link has been reset, meaning that information packets queued at the
time of reset are lost. The system link is alarmed if 20 or more errors of this type are
detected within 10 minutes.
6. Error type 1281: the link has experienced slow transmit rate because the remote endpoint
is busy. The effect of this error is that the endpoint 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.
a. Ensure that the remote endpoint is functioning properly.
b. Follow the information in Common Procedure for Repairing Link Problems.
c. Clear errors and wait for 10 minutes.
7. Error type 1537: the link has experienced slow transmit rate due to excessive
retransmission. Possible causes may be that the switch is overrunning the endpoint, or
that the endpoint is not operating properly. The effect is that the endpoint location may
experience slower throughput rate. The system link is alarmed if 4 or more errors of this
type are detected within 10 minutes.
8. Error type 1793: This error indicates that the link has experienced slow transmit rate due
to unknown causes, meaning that the endpoint 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.
9. Error type 2049: 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 min.
a. Follow the Common Procedure for Repairing Link Problems.
b. Clear errors and wait for 10 min.
SYS-LINK demand test descriptions and error codes

Testing for system links is different from the standard test procedures for MOs. In addition to
testing the system link MO, the user can test every component 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 is absent when the link is 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. In either case, it represents the path on which the link was attempted or
established unsuccessfully.
Test command for the system links, test sys-link location, can be specified with current
or faulted as an optional argument if the user wants to test every component in the specified path.
The tests executed are the same if the user tests 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.
SYSTEM (System)
MO name Alarm level Initial command to run 72 Full name of MO
SYSTEM None None System
72SYSTEM has no associated alarms and thus appears only in the Error Log. There are no tests
that run on SYSTEM.
The SYSTEM maintenance object logs information about system resets, including interchanges.
When software encounters a problem with hardware, or with its own processes, and requests a
restart to clear the problem, an error is logged under SYSTEM. For example, if there is a loss
of clocking in a system with duplicated servers, the system switches to the other clock and then
executes a level-2 system reset to recover from hardware problems caused by the loss of clock.
Errors logged under SYSTEM can help to determine the cause of a reset. For more information
about interchanges, see Troubleshooting duplicated servers in Maintenance Procedures for Avaya
Aura® Communication Manager, Branch Gateways and Servers.
The display initcauses screen also contains information about the reset.
SYSTEM error log entries and recommended actions

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 129: SYSTEM error log entries
Error type Aux Associated Test Alarm On or Off Command to resolve the
Data Level board error
0 (a) 0 Any Any Any
8 (b) 0
9 (c) Any
10 (d) Any
21 (e)
355 (f) Any
Table continues…
TDMODULE (Trunk Data Module)
Error type Aux Associated Test Alarm On or Off Command to resolve the
Data Level board error
356 (g) Any
601 (h)
602 (i)
603 (j)
Note:
1. Error type 0: 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. Error type 8: a System Restart Level 3 was requested.
3. Error type 9: a System Restart Level 2 was requested. This can happen due to a loss
of tones due to a faulty Tone-Clock circuit pack.
4. Error type 10: a System Restart Level 1 was requested.
5. Error type 21: a process trapped.
6. Error type 355: a Restart Level 2 occurred due to a power loss.
7. Error type 356: a Restart Level 2 occurred due to a tone clock loss.
8. Error type 601: an error occurred during initialization.
9. Error type 602: an error occurred while loading translations and the system requested
a Restart Level 3.
10. Error type 603: a process was reset.
TDMODULE (Trunk Data Module)

See PDMODULE (Processor Data Module) on page 453.
Time-day (time of day)

TIME-DAY MIN set time Time of day
The time of day contains the current year, month, day of the week, day of the month, hour,
minute, and second. The time-of-day MO monitors the time-of-day clock, and raises an alarm if
the time-of-day clock is not set or cannot be read by the software. If the time-of-day clock is not
set or cannot be read by the software, many features such as Time-of-Day Routing, CDR, ISDN
Call-by-Call, and duplication, are inoperative or incorrect. Use set time to set the time-of-day
clock when the system is initially powered up.
Use display time to read the time-of-day clock. Use set time to set the time-of-day clock.
The time-of-day clock has a backup battery to save the time of day during power failures.
There are no demand tests associated with TIME-DAY.
Time-day error log entries and recommended actions

Table 130: Time-day error log entries
Error type AUX Associated test Alarm On/off Command to resolve the
Data level board error
0 0 Any Any Any display time
247 ( a on 0 MIN OFF set time
page
518)
Note:
1. Error type 247: Software cannot read the time-of-day clock. During this condition, every
time stamp in the alarm log entry, error log entry, and software error log entry is potentially
inaccurate. In addition, any features that are sensitive to the time of day, such as SMDR,
time-of-day routing, ISDN call-by-call will not function correctly.
To resolve the alarm:
a. Use set time to set the time of day.
b. Use display time to display the time of day. If the time of day is displayed
correctly, wait 15 minutes and verify that the alarm is retired.
TSC-ADM (Administered temporary signaling connections)

level
TSC-ADM None None Administered Temporary Signaling
Connections (TSC-ADM, also
called ADM TSCs)
No alarms are generated for TSC-ADM or ADM TSCs.

Administered temporary signaling connections (TSC) provide a path through ISDN-PRI networks
for supplementary D-channel messages. ISDN-PRI applications such as the Distributed
Communications System (DCS) use temporary signaling connections to exchange user
information across an ISDN-PRI network. What makes administered TSCs unique is that these
particular TSCs stay active for an extended period of time, similar to a permanent data connection.
TSC-ADM (Administered temporary signaling connections)
These ADM TSCs are used for DCS features that require Non-Call Associated (NCA) TSCs, and
the ADM TSC provides the logical channel function in a DCS network.
An NCA TSC is a virtual connection established within a D-channel without associating any
B-channel connections. The connection provides user-to-user service by exchanging user
information messages without associated B-channel connections.
An administered TSC is a special NCA TSC defined for the DCS over the ISDN-PRI D-channel.
The ADM TSC has an administratively defined endpoint and is established for an extended period
of time.
There are two types of ADM TSCs:
• Permanent: these are established by the originating PBX, near-end ADM TSC or by the
terminating PBX, far-end ADM TSC. Once these ADM TSCs are established, they remain
active.
• As needed: these are established only when needed.
ADM TSC 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-user signaling is
functioning. In addition, maintenance can retrieve the status of the ADM TSC’s connection state.
Since ADM TSCs are administered on a per signaling-group basis, the health of an ADM TSC
also depends on the state of the D-channel or D-channel pair administered per signaling group.
See ISDN-SGR (ISDN-PRI Signaling Group) on page 398 documentation for details on ISDN-PRI
NFAS and D-channel backup maintenance.
The two administration commands for ADM TSCs are as follows:
• add signaling-group number
• change signaling-group number
The two maintenance commands for ADM TSCs are:
• test tsc-administered signaling-group-number/tsc-index
• status tsc-administered signaling-group-number/tsc-index
TSC-ADM error log entries and recommended actions

Table 131: TSC-ADM error log entries
Error AUX data Associated test Alarm On/off Command to

type level board resolve the error
3840 to tsc index # test tsc-administered
3967 (1)
Note:
1. Error types 3840 - 3967: There is no test to clear these error types.
Any of these errors 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 that the call was unable to complete. As a result, the error was logged.
a. Check the signaling group status of the D-channel or D-channel pair using status
signaling-group grp# for the administered TSC.
b. Check the status of the administered TSC using status tsc-administered.
c. 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 will tear down and reestablish the ADM TSC within 20 minutes.
The Port field in the error log contains the signaling group number for TSC-ADM errors.
TSC-ADM demand test descriptions and error codes

sequence sequence
TSC Heartbeat Inquiry Test 604 on page 637 Nondestructive
XXX-BD (Common port media module)

log
XXX-BD 1 MAJ test board location Common port media module
maintenance
MIN
WRN
1Refer to the appropriate media module documentation for the correct MO name displayed in this
field.
Common port media module maintenance is a set of common tests used by many media modules.
The common portion of these circuit packs/media modules is the generic hardware that interfaces
with the TDM bus. The XXX-BD designation is also used on SAT displays when reset board is
entered with an empty circuit pack or media module slot, or with a circuit pack or media module
type that is in conflict with the actual board type administered for that slot.
When any of the common port circuit packs or media modules are physically removed from the
backplane, no alarm will be logged for approximately 11 minutes. In the case of the following,
approximately 21 minutes will elapse before an alarm is logged:
• MM712 Digital Line Media Module
• MM717 Digital Line Media Module

• IMM-DCP Integrated Digital Line Board
• VMM-2BRI Integrated BRI Media Module
When a circuit pack or media module 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.
Alarms are logged against only those common port circuit packs or media modules on which
ports have been administered. In a heavily loaded system, the interval between the removal of a
common port circuit pack or media module and the logging of the alarm may be several minutes
longer.
The following table lists the common circuit pack and media module maintenance objects:
Table 132: Common MOs
ADX8D-BD
ADX16A-B
ADX16D-B
ANL-BD
AXA12-BD
AXD12-BD
CO-BD
DID-BD
DT-LN-BD
MET-BD
XXX-BD error log entries and recommended actions

Table 133: Common port circuit pack maintenance error log entries
1 0 Circuit pack or media module MIN ON
removed or SAKI Sanity
(#53)
23 0 None WRN OFF
36 4368 none
125 None MIN ON
Table continues…
217 0 None WRN ON
257 65535 Control channel Looparound MIN ON test board location r 20
Test (#52)
267 0 None WRN ON
513 Any None MIN ON test board location
769 4358 None
1025 4363 NPE Audit Test (#50) test board location lr 20
1281 Ringing Application Test MIN ON test board location r2
(#51)
1412
1538 Any None WRN ON
MIN
1793 Neon Test (#220) MIN ON test board location r2
3840 Any None
3999 Any None
Note:
1. Error type 1: The circuit pack or media module stopped functioning or has been
physically removed from the system. The alarm is logged approximately 11 minutes
after removal of the circuit pack or failure of the SAKI Sanity Test (#53).
Check for the physical presence of the circuit pack or media module in the slot
indicated by the alarm. If the circuit pack or media module is absent, insert one of
the proper type. If the circuit pack or media module is present and its red LED is lit,
see the LED alarms without an Alarm Log entry or with error type 1 section in LED
Descriptions for Avaya Aura® Communication Manager Hardware Components.
2. Error type 18: The circuit pack or media module has been busied out. Release the
circuit pack or media module using release board location.
3. Error type 23: The circuit pack or media module has been logically administered but
not physically installed. The alarm should clear when the circuit pact or media module
is installed.
If the circuit pack or media module is already installed:
a. Run test board location long and look at any test failures or error codes
generated.
b. If the test does not clear error 23, then execute reset board location and
run the long test again.
c. If the reset/test does not clear error 23, replace the circuit pack or media module.
4. Error type 36: This error applies only to the maintenance/test circuit pack (TN771B
or TN771C). The error indicates that the hardware associated with the analog trunk
testing port of the circuit pack failed to initialize. Note that when yhis error occurs, the
maintenance/test circuit pack may report an invalid vintage. Although this error is not
service-affecting, the maintenance/test circuit pack should be replaced.
5. Error type 125: The circuit pack or media module physically installed in the slot does
not match the type that is administered for that slot. Do one of the following:
• Remove the incorrect circuit pack or media module and replace it with one of the
type that is administered for that slot.
• Use change circuit-pack or change media-module to re-administer the
slot so that it matches the board that is installed, and follow with reset board
location .
6. Error type 217: This error applies to the maintenance/test circuit pack (TN771D), Tone
Detector (TN748B, TN748C, or TN748D), and Call Classifier (TN748) circuit packs.
For the maintenance/test circuit pack, the error indicates that there is more than one
maintenance/test circuit pack in the port network. For the tone detector or call classifier
packs, the error indicates that there are more than 10 circuit packs in the system.
Remove the circuit pack against which the error is logged.
7. Error type 257: Transient communication problems between the switch and this circuit
pack or media module. Execute test board location and refer to the repair
procedures for the Control Channel Looparound Test 52 on page 586.
8. Error type 267: Transient communication problems with this circuit pack or media
module. This error is not service-affecting and no action is required.
9. Error type 513: This error indicates an on-board hardware failure. The system will
continuously test the circuit pack or media module and report the results approximately
every 10 minutes. If the hardware problem is resolved, the alarm should clear in
approximately 30 minutes. If the alarm does NOT clear in 30 minutes, then the circuit
pack or media module should be replaced.
10. Error type 769: This error can be ignored, but look for other errors on this circuit pack
or media module.
12. Error type 1281: No ringing current is detected.
13. Error type 1412: Test is not applicable to media modules or gateways. This error can
be ignored. No action is necessary.
14. Error type 1538: The hyperactive circuit pack or media module is out-of-service and
may exhibit one or more of the following symptoms:
a. The common circuit pack/media module level tests such as Test #51 and/or Test
#220 are aborting with error code 2000.
b. The tests run on the ports of this circuit pack or media module are returning with a
no-board.
c. A busyout/release of the circuit pack or media module has no effect on test
results.
d. A list configuration command shows that the circuit pack or media module
and ports are properly installed.
If the XXX-BD is not a TN754 Digital Line Circuit Pack (DIG-BD) or digital line media
module, and if this error happens again within 15 minutes, then replace the circuit
pack or media module. If the XXX-BD is a TN754 Digital Line Circuit Pack (DIG-BD)
or Digital Line Media Module, then check the alarm level. If the alarm level is a
warning, this indicates that users are probably causing the hyperactivity by adjusting or
changing their digital stations. If the circuit pack or media module is very hyperactive,
then this alarm will be upgraded to a minor alarm within 1 hour. If the alarm level is a
minor alarm, then replace the circuit pack or media module.
15. Error type 1793: No neon current is detected.
17. Error type 3999: The circuit pack or media module 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 or media module was taken out-of-service due to
hyperactivity. If Error type 1538 is absent, then the circuit pack or media module was
not 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 or media module is being
lightly used, it may indicate a problem with the circuit pack or media module, or the
equipment attached to it.
XXX-BD demand test descriptions and error codes

Order of investigation Short test Long test Reset board D/ND
sequence sequence sequence
Chapter 7: Maintenance demand tests
Dial Tone Test (#0)

The Dial Tone Test attempts to seize a port and check for the return of a dial tone. It is run for
CO-TRK (Analog CO Trunk) on page 337.
Related links
Error code: 1005 on page 525
Error code: Any on page 529
Error code: 1005

Test result
ABORT
Cause
Could not allocate system resources to run this test.
Solution
Test result
ABORT
Cause
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.
Maintenance demand tests
Error code: 1000

Test result
ABORT
Cause
System resources required to run this test are not available. The port may be busy with a valid
call.
Solution
1. Enter display port location to determine the trunk group/member number of the
port.
2. Enter status trunk to determine the service state of the port.
If the service state indicates that the port is in use, wait until the port is idle before
retesting.
3. Retry the command at 1-minute intervals up to 5 times.
Error code: 1001

Test result
ABORT
Cause
System resources required to run this test were not available
Solution
Error code: 1002

Test result
ABORT
Cause
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. A system is
considered under heavy traffic when the Call Processing Occupancy is greater than 50% or when
the System Management and the Call Processing Occupancies together exceed 65%.
Solution
1. Enter status health to view the occupancy measurements.
2. Enter display errors and resolve errors, if any.
3. If the system has no TDM-BUS errors and is not handling heavy traffic, retry the command
at 1-minute intervals up to 5 times.
Dial Tone Test (#0)
Error code: 1004

Test result
ABORT
Cause
The port was seized by a user for a valid call.
Solution
port.
retesting.
Error code: 1018

Test result
ABORT
Cause
This test has been disabled by administration. Determine why this test was disabled before
enabling it.
Solution
1. To enable the test, enter change trunk-group <grp#>.
2. Enter y in the Maintenance Tests field, and submit the screen.
Error code: 2000

Test result
ABORT
Cause
Response to the test was not received within the time allowed.
Solution
Test result
FAIL
Cause
The trunk was seized, but dial tone could not be detected.
Solution for CO-TRK
1. Test every administered outgoing port on the board.
• Failure of one port indicates a problem toward the CO.
• If every port fails, see note below.
2. Check for TONE-BD and TONE-PT errors.
3. 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 media module
can be replaced as a last resort.
6. Perform a trunk test call to see if the trunk is operable.
If the dial tone test fails for every port on a media module, a -5 Volt power problem is
indicated.
Solution for DIOD-TRK
1. Check for TONE-BD and TONE-PT errors.
2. Clear any errors found, and repeat the test.
3. If the error has still not cleared, refer the problem to the CO.
Error code: 2002

Test result
FAIL
Cause
Seizure portion of the test failed due to a hardware problem. The fault is usually caused by a
disconnected trunk.
Solution for CO-TRK
1. If the CO Port Diagnostic Test (#3) also failed, enter display errors to display the error log.
2. If Error Type 1281 appears in the error log (the CO Port Diagnostic Test failed because it
could not detect ground) AND Error Type 3329 or 3585 appears in the error log with the
same last occurred time as Error Type 1281 and 1537, replace the media module.
3. Check the trunk wiring to ensure good connection.
4. Repeat the test if a wiring correction is made.
5. Locate another identical CO trunk and swap its wiring with the one under test.
6. Repeat the test on both trunks, and determine whether the problem follows the trunk or
remains at the original port.
CO Port Diagnostic Test (#3)
7. If the problem follows the trunk, refer the problem to the CO.
8. If the problem remains at the port, replace the media module and repeat the test.
Solution for DIOD-TRK
1. Check trunk wiring to ensure good connection.
2. Repeat the test if a wiring correction is made.
3. Locate another identical CO trunk and swap its wiring with the one under test.
4. Repeat the test on both trunks and determine whether the problem follows the trunk or
remains at the original port.
5. If the problem follows the trunk, refer the problem to the CO.
6. If the problem remains at the port, replace the media module and repeat the test.
Test result
PASS
Cause
Trunk was seized, and dial tone was detected.
Solution
Investigate user-reported troubles on this port by using other port tests and by examining the trunk
or external wiring.
Error code: Any

Test result
NO BOARD
Solution
See NO BOARD on page 773 for the repair procedures.

For ground start trunks, circuit pack or media module port relays are operated and checked 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 media module should be
replaced only if this test fails with the CO line disconnected.
This test also checks the on-board programmable transmission circuits that allow the media
module to support transmission characteristics of several different countries.
This test runs on CO-TRK (Analog CO Trunk) on page 337.
Related links
No error code on page 530
Error codes: 1000, 1004 on page 530
No error code
Test result
ABORT
Cause
Could not allocate the necessary system resources to run this test.
Solution
Error codes: 1000, 1004

Test result
ABORT
Cause
call.
Solution
port.
retesting.
Error code: 1005

Test result
ABORT
Cause
Test is not valid for the present configuration. This error can be ignored.
Error code: 1018

Test result
ABORT
Cause
Test has been disabled by administration. Determine why this test was disabled before enabling it.
Solution
1. To enable the test, enter change trunk-group <grp#> and enter y in the
Maintenance Tests field on the Trunk Group screen.
Error code: 2000

Test Result
ABORT
Cause
Solution
Test result
FAIL
Cause
Failure to detect ground or faulty ground detected on Ring lead.
Solution
1. Enter display errors to display the error log.
2. Check for Error Type 1025 or 1281.
3. If both errors appear in the error log, choose the most recent error.
Cause
• Error Type 1025: Faulty ground detected on Ring lead. This is an off-board fault.
• Error Type 1281: Failure to detect internally generated ground. This is an on-board fault.
Solution for Error type 1025
1. Repeat the test.
• If the test passes, ignore the original failure.
• If the test aborts, continue with Step 2
2. Repeat the test with the CO line removed.

3. If the test fails, replace the media module.
4. If the test passes, refer the problem to the CO.
Solution for Error type 1281
1. Run the long test sequence.
2. If all of the following conditions are true, replace the media module:
• The CO Port Diagnostic Test (#3) fails
• The Dial Tone Test (#0) fails with Error Code 2002
• Error Type 3329 or 3585 appears in the error log with the same last occurred time as
Error Type 1281 and 1537
3. Repeat the test with the CO line removed.
4. If the test fails, replace the media module.
5. If the test passes, the CO may be drawing too much current. Refer the problem to the CO.
Test result
PASS
Cause
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 about whether a CO line is actually
connected.
Solution
Investigate user-reported troubles on this port by using other port tests and by examining the trunk
or external wiring.
Error code: 0
Test result
NO BOARD
Solution
NPE Crosstalk Test (#6)

For the majority of maintenance objects, this test is known as the 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 conference functions on a per-port
basis. This test verifies that the NPE channel of the port 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 takes about 20 to 30 seconds to
complete.
For MMI-BD, this test is known as the TSI Crosstalk Test (#6). The Time Slot Interchanger (TSI)
chip controls connectivity to the TDM bus. The TSI Crosstalk 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,
the TSI can communicate over the TDM bus. This test takes approximately 20 to 30 seconds to
complete.
For VC-SUMPT, this test is known as the VC-SUMPT Port NPE Crosstalk Test (#6). It is a slightly
modified version of the NPE Crosstalk Test.
This test runs on the following maintenance objects:
• AN-LN-PT (Analog Line Port) on page 305
• CO-DS1 (DS1 CO Trunk) on page 334
• CO-TRK (Analog CO Trunk) on page 337
• DID-DS1 (Direct Inward Dial Trunk) on page 343
• DIOD-DS1 (DS1 DIOD trunk) on page 356
• ISDN-TRK (DS1 ISDN Trunk) on page 405
• PE-BCHL (PRI Endpoint Port) on page 459
Related links
Error code 1001 on page 536
No error code
Test Result
ABORT
Cause
Solution
Error code: 1000

Test result
ABORT
Cause
The port may be busy with a valid call, or the system’s Music-On-Hold port is off-hook, which it
usually is.
Solution for AUX-TRK
port.
retesting.
Solution for CO-DS1
port.
retesting.
3. If the port status is active but the port is idle (no calls), enter display errors and check
the error log for Error Type 1025.
4. If this error exists, see the error log table for a description of this error and required actions
for CO-DS1 (DS1 CO Trunk) on page 334.
The port may be locked up.
5. If the port is idle, retry the command at 1–minute intervals up to 5 times.
Solution for CO-TRK
port.
retesting.
for CO-DS1 (DS1 CO Trunk) on page 334.
5. Check the CO wiring, check for excessive loop current, and check the trunk translations.
If the test is translated incorrectly, this test will abort.
6. If the port status is idle, busyout and release the trunk, and retry the command at 1–minute
intervals up to 5 times.
7. If the test still aborts, replace the circuit pack.
Solution for DAT-LINE
1. Enter status data-module to determine the service state of the port.
If the port is in use, wait until it is idle before testing.
Solution for DID-DS, TIE-DS1, and TIE-TRK
port.
retesting.
for the appropriate maintenance object (DID-DS1 (Direct Inward Dial Trunk) on page 343).
5. If the port status is idle, busyout and release the trunk, and retry the command at 1–minute
Solution for DID-TRK
1. Enter display port location to determine the station extension, attendant number,
or trunk group/member number of the port.
2. Enter status station, status attendant, or status trunk to determine the
service state of the port.
If the port is in use, wait until it is idle before testing. Attendants are always in use
(off-hook) if the handset is plugged in and the port is not busied out.
the Error Log for Error Type 513.
4. If the port status is idle, retry the command at 1-minute intervals up to 5 times.
Solution for DIOD-TRK and ISDN-TRK

port.
retesting.
Solution for PE-BCHL
1. Enter status pri-endpoint extension to determine the service state of the port.
If the port is in use, wait until it is idle.
Solution for WAE-PORT
1. Enter status access-endpoint extension to determine the service state of the
port.
Solution for all other MOs
1. Enter display port location to determine the station’s extension.
2. Enter status station extension to determine the service state of the port
Error code 1001

Test result
ABORT
Cause
System resources required to run this test are not available.
Solution
Error code: 1002

Test result
ABORT
Cause
Solution
Error code: 1003

Test result
ABORT
Cause
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.
Solution
1. Enter list measurements tone-receiver to see information regarding the system’s
tone receivers.
Error code: 1004

Test result
ABORT
Cause
The port was seized by a valid call during the test.

port.
1. Enter display port location to determine the station extension, attendant number,
or trunk group/member number of the port.
Error code: 1005

Test result
ABORT
Cause
The test was aborted due to a configuration problem, such as when an analog port is used in a
combined modem pool. Ignore the error.
Error code: 1018

Test result
ABORT
Cause
enabling it.
Solution
1. To enable the test, enter change station extension for analog stations and change
trunk-group <grp#> for trunks.
2. Type y in the Maintenance Tests field and submit the screen.
Error code: 1020

Test result
ABORT
Cause
The test did not run due to a previously existing error on the specific port or there is a more
general circuit pack error.
Solution
1. Enter display errors and check the Error Log for existing errors against this port or
circuit pack.
2. Attempt to diagnose the previously existing error.
3. After resolving the previously existing errors, retry the command
Error code: 1017

Test result
ABORT
Cause
A service state audit message is outstanding.
Solution
Error code: 1412

Test result
ABORT
Cause
This test does not run on media modules or gateways. Ignore.
Error code: 2000

Test result
ABORT
Cause
2. If the test aborts with Error Code 2000 again, run the short test sequence on the
associated DS1-BD or UDS1-BD.
If tests 138 through 145 on the associated DS1-BD or UDS1-BD also abort with Error
Code 2000, hyperactivity on the board or facility is indicated. The hyperactivity problem
should be dealt with first. See Hyperactive DS1 Media Module on page 774.

Error code: 2012

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: Any

Test result
FAIL
Cause
The NPE of the tested port is transmitting in error. This causes noisy and unreliable connections.
Clear every off-board problem before replacing the media module. A TDM-BUS problem is usually
the result of a faulty board connected to the backplane, or bent pins on the backplane.
Solution
If the test fails, replace the media module.
Test result
PASS
Cause
The port is correctly using its allocated time slots.
Investigate user-reported troubles on this port by using other port tests, examining station and
trunk wiring, examining the station, and ensuring that the station is correctly translated.
Conference Circuit Test (#7)
Error code 0
Test result
NO BOARD
Solution

The Conference Circuit Test verifies that the Network Processing Element (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.
Related links
No error code
Test Result
ABORT
Cause
Solution
Error code: 1000

Test result
ABORT
Cause
call.
port.
Solution for CO-DS1, DID-DS1, TIE-DS1
port.
2. Enter status trunk <grp#/mem#> to determine the service state of the port.
3. If the port is in use, wait until it is idle before retesting.
See the error log table for a description of this error and required actions for this
maintenance object (CO-DS1 (DS1 CO Trunk) on page 334), DID-DS1 (Direct Inward Dial
Trunk) on page 343.

1. Enter display port location to determine the trunk group/ member number or
station extension of the port.
2. Enter status trunk <grp#/mem#> or status station to determine the service
state of the port.
3. If the port is in use, wait until it is idle before retesting.
Error code: 1002

Test result
ABORT
Cause
Solution
Error code: 1003

Test result
ABORT
Cause
Solution
tone receivers.
Error code: 1004

Test result
ABORT
Cause
1. Enter display port location to determine the trunk group/ member number or
station extension of the port.
2. Enter status trunk <grp#/mem#> or status station extension to determine
the service state of the port. If the port is in use, wait until it is idle before retesting.
Error code: 1005

Test result
ABORT
Cause
The test is not applicable to this port. This error can be ignored.
Error code: 1018

Test result
ABORT
Cause
This test has been disabled by administration. This may be due to the ONS Ringer Application
Test #48, which can be customer or terminal disturbing.
Solution
1. To enable the test for a particular station, enter change station extension.
2. Enter y in the Maintenance Tests field and submit the screen.
Error code: 1020

Test result
ABORT
Cause
Solution
1. Examine the Error Log for existing errors against this port or circuit pack.
Error code: 1412

Test result
ABORT
Cause
Error code: 2000

Test Result
ABORT
Cause
Solution
Error code: 2053

Test result
ABORT
Cause
At least one of the following errors was found on the DS1 circuit pack:
• 1281 - Loss of signal
• 1793 - Blue alarm
• 2049 - Red alarm
• 2305 - Yellow alarm
• 1537 - Hyperactivity
Error code: 2100

Test result
ABORT
Cause
Solution
1. Resolve errors, if any.
2. If there are no TONE-PT errors in the error log, retry the test at 1-minute intervals for a
maximum of 5 times.
Error code: Any

Test result
FAIL
Cause
Solution for ADX16A-P, DIOD-DS1, ISDN-TRK, PE-BCHL, S-SYN-PT, VC-SUMPT, WAE-PORT
Replace the circuit pack.
Solution for ANL-16-L, AN-LN-PT, DAT-LINE
1. Enter display port location and status station extension to determine
whether the station is idle.
2. If the station is idle, enter test port location for this port
3. If the test continues to fail, enter busy port location and release port
location, and then retest.
4. If the test still fails, replace the circuit pack.
Test result
PASS
Cause
The port can correctly conference multiple connections.
Solution
Investigate user-reported troubles on this port by using other port tests and by examining station,
trunk, or external wiring.
GPP NPE Crosstalk Test (#9)
Error code 0
Test result
NO BOARD
Solution

The General-purpose Port (GPP) Network Processing Element (NPE) Crosstalk Test verifies that
the port’s NPE channel talks on the selected time slot and that it never crosses over to time slots
reserved for other connections. 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. An NPE that is not working correctly may cause one-way and noisy connections.
This test takes about 20 to 30 seconds to run.
Crosstalk testing is performed on both the primary (for voice) and the secondary (for data)
information channel associated with each port. If this test fails on either channel, the port is taken
out of service.
This test is run on the following maintenance objects:
• DIG-LINE (Digital Line) on page 349
• E-DIG-ST (Emulated Digital Line) on page 363
• PDMODULE (Processor Data Module) on page 453
• TDMODULE (Trunk Data Module) on page 517
Related links
Error code: 1, 2, Any on page 553
Error code: 1
Test Result
ABORT
Cause
During testing of the primary information channel, system resources may not have been available
or the port may have been busy during the test.
Solution
1. Enter display port location to determine the extension of the port.
2. Enter status station extension to determine the service state of the port.
If the service state indicates that the port is in use, wait until it is idle.
Error code: 2
Test Result
ABORT
Cause
System resources may not have been available or the port may have been busy during the test.
Solution for DIG-LINE and E-DIG-ST
1. Check if port is being used.
2. If possible, disconnect by toggling the disconnect button on DTDM.
Warning:
This action will drop any calls in progress.
3. Retry the command after 1 minute.
All other Maintenance Objects
1. Verify that the port is idle.
Error code: 1000

Test result
ABORT
Cause
System resources required to run this test are not available or the port may be busy with a valid
call.
Solution for ADX8D-PT and ADX16D-P

2. Enter status station location to determine the service state of the port.
If the port is in use, wait until it is idle before retesting.
1. Enter display port location to determine the station extension or attendant number
of the port
2. Enter status station extension or status attendant location to determine
the service state of the port.
Attendants are always in use (off-hook) if the handset is plugged in and the port is not
busied out.
Solution for M/T-ANL
The port may be in use on a valid ATMS trunk call.
Solution for M/T-DIG
1. Enter list isdnpri-testcall to determine if the port is in use (listed in the M/T Port
column).
2. If so, wait for the test call to finish as indicated in the Start Time and Duration fields, or
abort the test call with clear isdnpri-testcall grp#/mem#, where grp#/mem# is
determined from the B-Channel field of list isdnpri-testcall.
Solution for PDMODULE and TDMODULE
2. Enter status data-module extension to determine the service state of the port.
Error code 1001

Test result
ABORT
Cause
Solution
Error code: 1002

Test result
ABORT
Cause
Solution
Error code: 1003

Test result
ABORT
Cause
Solution
tone receivers.
Error code: 1004

Test result
ABORT
Cause
Solution for ADX8D-PT and ADX16D-P
of the port
2. Enter status station or status attendant to determine the service state of the
port.
busied out.
1. To determine whether the port is in use by a valid ATMS test call, enter status station
ext where ext is the assigned ATMS station’s number.
3. If the port is idle and the test continues to abort, escalate the problem.
The port has been seized by a valid ISDN-PRI test call.
1. Enter list isdnpri-testcall to determine if the port is in use (listed in the M/T Port
column).
2. If so, wait for the test call to finish as indicated in the Start Time and Duration fields, or
1. Enter display port location to determine the extension of the data module port.
2. Enter status data-module extension to determine the service state of the port.
Error code: 1020

Test result
ABORT
Cause
Solution
1. Enter display errors and check the Error Log for existing errors against this port or
circuit pack.
3. After resolving the previously existing errors, retry the command
Error code: 1412

Test result
ABORT
Cause
Error code: 2000

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 2500

Test result
ABORT
Local Loop Test (#13)
Cause
Solution
Error code: 1, 2, Any

Test result
FAIL
Cause
Solution for M/T-ANL and M/T-DIG
1. If the remaining ports are currently idle (amber LED is off), try to reset the circuit pack and
rerun the test.
2. If the problem persists, replace the circuit pack.
Error code 1 = Crosstalk test failed on the primary channel.
Error code 2 = Crosstalk test failed on the secondary channel.
Replace the circuit pack.
Caution:
ADX8D-PT and ADX16D-P: Shut down AUDIX before replacing the EMBEDDED AUDIX
circuit pack.
Test result
PASS
Solution
1. To ensure that this is not an intermittent problem, repeat this test up to 10 times and see if
it continues to pass.
2. If the problem still exists, examine the stations, connections, and wiring.

This test is executed on the following maintenance objects:
• E-DIG-ST (Emulated Digital Line) on page 363

For DIG-LINE, and E-DIG-ST, this test is known as the Voice and Control Channel Local Loop Test
(#13). This test consists of four tests that check the information and control channels between the
server and the port circuit. If any of the tests fail or abort, the test sequence stops and the result is
reported.
For M/T-ANL, this test is known as the Analog Port Digital Looparound Test (#13). The test
performs a loop test on the data channel and TDM bus, then runs a conference test.
For M/T-DIG, this test is known as the Digital Port Looparound Test (#13). The test performs a
loop test on the data channel and TDM bus, then runs a conference test.
For PDMODULE and TDMODULE, this test is known as the Information and Control Channel
Looparound Test (#13). This is a set of four tests that check the operation of the information and
control channels used between Communication Manager and the Digital Line port circuit.
User impact from problems with this port many range from no noticeable effect to not being able
to use this port. Users may not notice a disruption in service. In extreme cases, the conferencing
feature may not work at all.
Related links
Error codes: 2000, 2100, 2500 on page 558
Error code: None on page 558
No error code
Test Result
ABORT
Cause
Solution
2. If the test continues to abort, escalate the problem.
Error code: 1000

Test result
ABORT
Cause
Could not seize the port. The port may be busy with a valid call.
Solution for ADX8D-PT, ADX16D-P, DIG-LINE, and E-DIG-ST
of the port
2. Enter status station extension or status attendant location to determine
busied out.
1. To determine whether the port is in use by a valid ATMS test call, enter status
station ext where ext is the assigned ATMS station’s number.
1. Enter list isdnpri-testcall to determine which call is using the port.
2. Wait for the test call to complete as indicated in the Start Time and Duration fields, or
1. Enter display port location to determine the data module extension.
2. Enter status data-module extension to determine the service state of the data
module.
Error code: 1001

Test result
ABORT
Cause
Solution
Error code: 1002

Test result
ABORT
Cause
Solution
Error code: 1003

Test result
ABORT
Cause
Solution
tone receivers.
Error code: 1004

Test result
ABORT
Cause
Solution for ADX8D-PT, ADX16D-P, DIG-LINE, and E-DIG-ST

of the port
port.
busied out.
1. To determine whether the port is in use by a valid ATMS test call, enter status station
ext where ext is the assigned ATMS station’s number.
1. Enter list isdnpri-testcall to determine which call is using the port (from the M/T
Port column).
2. Wait for the test call to complete as indicated in the Start Time and Duration fields of the
above display, or abort the test call with clear isdnpri-testcall grp#/mem# where
grp#/mem# is determined from the B-Channel field of list isdnpri-testcall.
1. Enter display port location to determine the data module extension.
2. Enter status data module extension to determine the service state of the data
module.
If the data module is in use, wait until the port is idle before retesting.
Error code: 1412

Test result
ABORT
Cause
Error codes: 2000, 2100, 2500

Test result
ABORT
Cause
• Error 2000: Response to the test was not received within the time allowed.
• Error 2100: Could not allocate the necessary system resources to run this test.
• Error 2500: Internal system error.
Solution
Error code: None

Test result
FAIL
Cause
ADX8D-PT and ADX16D-P: The test failed for reasons external to the EMBEDDED AUDIX circuit
pack.
Solution
1. Check the Tone Generator and the Tone Detector circuit packs by entering test board
location for these circuit packs.
2. Resolve any problems detected on the Tone Generator or Tone Detector circuit pack.
3. If both circuit packs are functioning properly and the test still fails, shut down AUDIX and
replace the EMBEDDED AUDIX circuit pack.
Test result
PASS
The Local Loop test passed. Every channel is transmitting properly.
1. To ensure that this is not an intermittent problem, repeat this test up to 10 times and see if
it continues to pass.
2. If the problem still exists, examine the connections, station, and wiring.
Digital Station Lamp Update (#16)

This test lights all lamps on the terminal as specified. The lamp updates run only if the station is
in-service. 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.
Digital Station Lamp Update (#16)
This test runs on the following maintenance object:

• DIG-IP-S (Digital IP Station) on page 346
Related links
No error code
Test Result
ABORT
Cause
Solution
Error code: 1
Test Result
ABORT
Cause
This port may have been busied out by a system technician.
Solution
1. Look in the Error Log for Error Type 18 (port busied out) for this port.
2. If this Error Type is present, release the port using the command release station
extension and run the test again.
3. Make sure the terminal is connected.
Error code: 3
Test Result
ABORT
Cause
Station may be in ready-for-service or out-of-service state.
Solution
1. Enter status station to verify the state of the station.
Error code: 1000

Test Result
ABORT
Cause
call.
Solution
of the port.
port.
busied out.
Error code: 1392

Test result
ABORT
Cause
This port is a TTI port. The test does not run on TTI ports.
Solution
1. Verify that the port is a TTI port using either display port (the port is a TTI port) or
list config (a “t” is displayed for 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.
Test result
FAIL
Digital Station Audits Test (#17)

Solution
Test result
PASS
Cause
The message to light every station lamp was successfully sent to the port.
Solution
1. Observe the station lamps being lit when running the test.
If all lamps do not light, the other Digital Line test results may indicate related problems
that do not allow the lamps to light.
2. Investigate troubles by using other Digital Line port tests, and by examining the station,
wiring, and connections.

This test is a series of audits. This test is run on PDMODULE, TDMODULE, digital stations,
softphone applications, and IP phones. This test is run on a station only if the station is in-service.
The following audits are performed:
• Switch hook Inquiry: This is an update of the server’s software records based on the on-hook/
off-hook status of the data module or voice terminal.
• Station ID Request: A request is made to the data module or station for its status. The data
module or station returns its configuration and health information. This information is checked
and a pass/fail result is provided.
• EPF inquiry: The test requests the status of the Electronic Power Feed. EPF is not used for
data modules.
• Bad Scan Inquiry: An uplink message is sent containing a count generated by certain events
relating to the link conditions. This can be an indication of communication problems between
the server and the digital port board or media module.
• Ringer Update: This updates the ringer state according to the server’s records.
• DTMP Administration Update: This sends a message to the digital station to refresh the
default value that causes the station to send touch-tones only in the primary information
channel. This value is initially set when the station is put in-service and each time the
station’s state changes from another state to in-service. This test is not used with data
modules.

• DIG-IP-S (Digital IP Station) on page 346
Related links
Error code: 1, 2 on page 562
Error code: 1, 2
Test Result
ABORT
Cause
Switchhook audit timed out.
Station ID request failed or the health bit is defective.
Solution
1. Verify that the data module or voice terminal is connected and repeat the test.
2. If the test aborts, replace the data module or voice terminal and repeat the test.
3. For PDMODULE or TDMODULE, if this test continues to abort, replace the circuit pack and
repeat the test.
Error code: 3
Test result
ABORT
Cause
The EPF has detected an overcurrent condition.
DIG-LINE
1. For a TN754 vintage 13 or earlier Digital Line circuit pack, enter test port location
long:
• If Test #11 passes, the EPF condition was cleared. Rerun the short test sequence.
2. Look for Error Type 769 logged against DIG-LINE and follow the procedures for DIG-LINE
(Digital Line) on page 349.
3. Rerun the test.
RDIG-STA
1. Enter test port location long:
• If Test #11 passes, the EPF condition was cleared. Rerun the short test sequence.
2. Look for Error Type 769 logged against RDIG-STA.
3. Rerun the test.
Error code: 4
Test Result
ABORT
Cause
Solution
1. Resolve any outstanding circuit pack or media module maintenance problems.
Error code: 5
Test result
ABORT
Cause
Ringer update aborted. Data module or station not in the in-service state.
PDMODULE, TDMODULE
1. Verify that the data module is powered (power LED on).
2. Make sure data module is connected to the building wiring, check for faulty wiring, check
for faulty data module.
4. Replace the Data Module and repeat the test.
5. If the test continues to abort, replace the Digital Line circuit pack and repeat the test.
DIG-LINE, RDIG-STA
The port could have been busied out by a system technician.
1. Look in the Error Log for Error Type 18 for this port.
2. If this error is present, release the port using release station extension.
Error code: 6
Test Result
ABORT
Cause
Touch-tone update failed.
Solution
Error code: 7
Test Result
ABORT
Cause
Downloadable parameter downlink failed.
Solution
Error code: 8
Test Result
ABORT
Cause
Terminal levels audit failed.
Solution
Error code: 1000

Test Result
ABORT
Cause
Solution
Error code: 1392

Test result
ABORT
Cause
Solution
1. Verify that the port is a TTI port using either display port (the port is a TTI port) or
list config (a “t” is displayed for 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.
Error code: 1706

Test result
ABORT
Cause
IP endpoint is not registered.
Solution
1. Verify the IP telephone is connected.

Test result
ABORT
Cause
Solution
Test result
FAIL
Solution
Test result
PASS
The audits passed.
Solution
If complaints still exist, investigate by using other port tests and by examining the data module
options, wiring, and connections.
Looparound and Conference Test (#33)

The Looparound and Conference Test checks the reflective and non-reflective looparound and
conference capabilities of a trunk port circuit. It transmits 404-Hz, 1004-Hz, and 2804-Hz tones.
Each tone is transmitted separately to and from the port, then verified.
Disabling this test also disables the Port Diagnostic Test (#35).
Related links
Error codes: 7, 129, 131, 133 on page 569
No error code
Test result
ABORT
Cause
Solution
Error code: 1000

Test result
ABORT
Cause
call.
Solution
port.
retesting.
Error code: 1002

Test result
ABORT
Cause
Solution
Error code: 1003

Test result
ABORT
Cause
Solution
tone receivers.
Error code: 1004

Test result
ABORT
Cause
Solution
port.
retesting.
Error code: 1018

Test result
ABORT
Cause
The test was disabled by administration.
Solution
1. To enable the test, enter change trunk-group x, where x is the trunk group number.
2. Change the Maintenance Tests field to y.
Error code: 1412

Test result
ABORT
Cause
This test does not run on media modules or gateways. Ignore this error.

Test result
ABORT
Cause
Solution
Error codes: 7, 129, 131, 133

Test result
FAIL
Cause
No transmission was detected to or from the port. The problem may be off-board.
• Error Code 7 - The conference capabilities of the port failed.
• Error Code 129 - The reflective 404-Hz tone test failed.
Solution
1. If the Looparound and Conference test fails for every port on a circuit pack, a -5 Volt power
problem is indicated.
2. If a red LED is lit on the power unit circuit pack, replace the circuit pack.
3. If the test fails on more than one port:,
a. Check for TONE-BD and TONE-PT errors.
b. When the tone errors have been resolved, rerun the test.
4. To check if the problem is on-board:
a. Disconnect the port from the auxiliary equipment or CO and retry the test.
b. If disconnecting from the CO, coordinate the disconnect with the CO or do it after
hours.
Otherwise, the CO may put the connection out of service.
c. If the retry fails, replace the circuit pack.
If the test passed after disconnecting the port from the auxiliary equipment or CO, the problem
is off-board.
5. AUX-TRK:
a. Check the wiring and connections to the auxiliary equipment and retry the test after
reconnecting the port to the auxiliary equipment.
b. If the test fails, check the auxiliary equipment. See the preceding procedure for a
failure with Error Code 7.
6. All other Maintenance Objects:
a. If the test passes and no troubles have been reported, disable the test by changing
the Maintenance Tests field to y on the change trunk-group x screen, where x
is the trunk group number.
b. If the test passes and troubles have been reported, refer the problem to the CO.
Test result
PASS
Cause
This port is functioning properly.
If users are reporting troubles, examine the loop connections to the port.
Port Diagnostic Test (#35)

This test is also known as the Battery Feed Test.
The battery feed chip provides power to the telephone equipment, signaling, rotary dial pulsing,
transmission, and balance. This test checks the signaling and switch hook capabilities of the
battery feed chip by terminating the port, applying battery, and trying to detect a current.
• ALARM-PT (Alarm Port) on page 303
• RANL-STA (Remote Analog Line Station Port) on page 481
Related links

No error code
Test result
ABORT
Cause
Solution
Error code: 1000

Test result
ABORT
Cause
ALARM-PT
The port may be reporting an external device alarm.
Solution
1. Enter test external-device-alarm port location to determine whether the port
is reporting an EXT-DEV failure.
2. If the port has no EXT-DEV failures, retry the command at 1-minute intervals up to 5 times.
ANL-16-L, ANL-LINE, AN-LN-PT, MET-LINE, RANL-STA

The port may be busy with a valid call.
Solution
of the port.
2. Enter status station extension or status attendant extension to determine
retesting. Attendants are always in use (off-hook) if the handset is plugged in and the port
is not busied out.
DID-TRK
The port may be busy with a valid call.
Solution
port.
retesting.
3. If the port status is active but the port is idle (no calls), check the error log for Error Type
513 for this maintenance object.
4. If the port status is idle, busyout and release the trunk, and retry the command at 1-minute
5. If the test continues to abort, check for wiring errors toward the CO which may cause the
trunk to lock up.
6. If the wiring is good and the test continues to abort, replace the media module.
Error code: 1004

Test result
ABORT
ALARM-PT
The port received an EXT-DEV failure during the test.
Solution
ANL-16-L, ANL-LINE, AN-LN-PT, DID-TRK, MET-LINE, RANL-STA

Solution
of the port.

Error code: 1005

Test result
ABORT
Cause
The test is not applicable for this type of port. This error can be ignored.
Error code: 1018

Test result
ABORT
DID-TRK
The test has been disabled by administration.
Solution
1. To enable the test, enter change trunk-group x, where x is the trunk group number.
2. Change the Maintenance Tests field to y.

The test has been disabled by administration. Determine why the Maintenance Tests field on the
station form was set to n on this station. It may be due to the ONS Ringer Application Test #48,
which can be customer or terminal disturbing.
1. To enable the test for the particular analog station being tested, enter change
stationextension, and set the Maintenance Tests field to y.
Error code: 1392

Test result
ABORT
Cause
Solution
1. Verify that the port is a TTI port using either display port, which shows that the port is
a TTI port, or list config, which shows a t for the port.
2. If either command indicates that the port is not a TTI port, the abort is correct, and no
action is necessary.
3. If the port is not a TTI port, escalate the problem.
Error code: 2000

Test result
ABORT
Cause
Solution
Error code: 2012

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 61446

Test result
FAIL
DID-TRK
Battery feed test failed. A loop current fault was detected. This is most likely an incoming CO-line
problem.
Solution
1. Check the incoming CO-line for loop current.
2. If none is detected refer the problem to the CO.
If the CO-line checks out OK, the failure must be on the DID port.
3. Replace the circuit pack.
Error code: 61456

Test result
FAIL
DID-TRK
Battery feed test failed. An on-board problem was detected. This port is out-of-service.
Solution
Replace the circuit pack or media module.
Error code: 61472

Test result
FAIL
DID-TRK
Battery feed test failed. A problem with the incoming CO-line was detected.
Solution
1. Check the incoming CO-line for proper operation.
2. If warranted, refer the problem to the CO.
3. If the CO-line is not at fault, the failure must be on the DID port.
4. Replace the circuit pack or media module.
ALARM-PT
The port’s battery feed chip is unable to supply sufficient power to sense the external device
alarm. This may occur when the test is performed at the same time that the external device
contact closure occurs.
Solution
Wait until the port has no EXT-DEV failures before retesting.


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 the terminal equipment goes off-hook.
Solution
1. Enter display port location to determine the station extension of the port.
4. If the test continues to fail, determine whether the customer is experiencing problems on
this line.
5. Replace the circuit pack or media module only if the customer is experiencing problems.
Test result
PASS
ALARM-PT
The port’s battery feed chip is able to provide power to the external device alarm to detect contact
closure

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.
Solution
1. If touch-tones are not heard when buttons are pressed, replace the media module.
2. Investigate user-reported troubles on this port by using other port tests, by examining
station wiring, or by examining the station.
DID-TRK
Current flow was detected for this port.
Solution
1. Investigate user-reported troubles on this port by using other port tests and by examining
connections to the port.
2. If problems continue, refer the problem to the CO.
Port Audit And Update Test (#36)
MET-LINE
Current flow was detected for this port.
Solution
Investigate user-reported troubles on this port by using other port tests and by examining
connections to the port.
Error code: 0
Test result
NO BOARD
Solution

The Port Audit and Update Test sends port level translation data from the switch processor to the
circuit pack to verify that the port’s translation and current state are correct.
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.
For an analog line port which is administered as an external alarm, this test is limited to updating
the software with the switchhook state.
• DIOD-DS1 (DS1 DIOD trunk) on page 356
This test is also known as the Station Status and Translation Audits and Updates Test (#36).
Related links

Error code: 5, 7, 8 on page 582
No error code
Test result
ABORT
Cause
Solution
Error code: 1000

Test result
ABORT
Cause
call.
1. Enter display port location to determine the station extension or trunk group/
member number of the port.
2. Enter status station or status trunk to determine the service state of the port.
If the port is in use, wait it is idle before retesting.
Error code: 1004

Test result
ABORT
ALARM-PT
The port received an EXT-DEV failure during the test. The test has been aborted.
Solution

Solution
port.
4. If the test continues to abort and the port is not in use, escalate the problem.
Error code: 1005

Test result
ABORT
Cause
Error code: 1006

Test result
ABORT
Cause
The port is out of service. The port has been busied out by command or taken out-of-service by a
failure of the NPE Crosstalk Test.
ALARM-PT
Solution
1. Check the Error Log for Error Type 18 (port busied out).
2. If this error is present, use release port location and run the test again.
3. Check the Error Log for Error Type 1025 for this port.
4. If this error is present, investigate errors associated with NPE Crosstalk Test (#6) on
page 532.
ANL-LINE, AN-LN-PT, ANL-16-L, OPS-LINE, RANL-STA

Solution
1. Check the Error Log for Error Type 18 (port busied out).
2. If this error is present, use release station extension and run the test again.
3. Check the Error Log for Error Type 1025 for this port.
4. If this error is present, investigate errors associated with NPE Crosstalk Test (#6) on
page 532.
5. Ensure that the terminal is connected and in service, and retest.
PE-BCHL
Solution
1. Enter status pri-endpoint extension to verify that the port is out of service.
2. Enter release pri-endpoint extension or release port location to put the
port back in service, then run the test again.
WAE-PORT
Solution
1. If Error 18 is present in the Error Log for this port, enter release access-endpoint
extension and retry the test.
2. If Error 18 is not present, check the error and alarm logs for WAE-PORT, DS1-BD, UDS1-
BD, or MG-DS1 errors and follow the recommended repair procedures.
See MG-DS1 (DS1 Interface Media Module) on page 436.

Solution
port. If the trunk is out of service, determine why.
2. Enter status trunk to verify that the trunk is out of service.
3. If it is OK to put the trunk back in service, enter release trunk and retry the test
4. Check the error log for Error Type 1025.
5. If this error exists, investigate errors associated with the NPE Crosstalk Test (#6).
Error code: 2000

Test result
ABORT
Cause
Error code: 2100

Test result
ABORT
Cause
FAIL
Possible internal software failure.
Error code: 1
Test result
FAIL
ALARM-PT
This failure does not indicate a hardware problem. The switchhook audit failed. This condition may
occur when the audit is performed at the same time that the terminal equipment goes off-hook.
Solution
Wait until the port has no EXT-DEV failures.

This failure does not indicate a hardware problem. This condition may occur when the audit is
performed at the same time that the terminal equipment goes off-hook.
Solution
1. Enter status station or status trunk to determine when the port is available for
testing.
2. When the port becomes available for testing, retry the command at 1-minute intervals up to
5 times.
Error code: 5, 7, 8
Test result
FAIL
Error code 5
Message Waiting Lamp update failed. Possible internal software error.
Error code 7
Translation update failed. Possible internal software error.
Error code 8
Ringer update failed. Possible internal software error.
2. If the test continues to fail, escalate the problem.
Test result
PASS
Solution
The software and the port processor have the same status.
Investigate user-reported troubles on this port by running other port tests, examining the wiring, or
by inspecting the station.
Error code: 0
Test result
NO BOARD
Solution
ONS Ringer Application Test (#48)

The Ringing Application Test applies momentary ringing voltage to the terminal equipment to
determine if the terminal equipment is connected to the port. The test may cause some terminal
equipment to ring briefly during daily maintenance. If this ringing disturbs the customer or the
terminal equipment, disable it using the Tests field on the Station screen. With some software
releases, Tests #6, #7, #35, and #161 are also disabled.
This test is also known as the Station Present Test (#48).

Related links
No error code
Test result
ABORT
Cause
Solution

Test Result
ABORT
Cause
System resources required to run this test are not available or the port was seized with a valid call
during the test.
Solution
1. Enter display port location to determine the station’s extension.
Error code: 1005

Test result
ABORT
Cause
Error code: 1008

Test Result
ABORT
Cause
Could not allocate a ringing circuit. Either every ringing circuit is in use, or the ringing generator is
defective or incorrectly wired.
Solution
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 incorrectly wired See RING-GEN (Analog Ring
Generator) on page 490.
If ABORT 1008 does not occur on other ports, then all four ring phases are in use.
Error code: 1018

Test Result
ABORT
Cause
The test has been disabled by administration. Determine why the Test field on the change station
screen has been set to n for this station. It may be due to the brief ringing disturbance that this test
may cause.
Solution
To enable the test for the particular analog station, enter change station extension and set
the Test field to y.
Error code: 1412

Test result
ABORT
Error code: 2000

Test result
ABORT
Cause
Error code: 2100

Test result
ABORT
Cause
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, see RING-GEN (Analog Ring Generator) on page 490.
3. Check all of the wiring between the station equipment and the switch. Then, run the test
again.
If the test still fails, the set may be defective.
4. Check the set and replace it, if necessary.
5. Some terminal equipment could fail even when it is connected properly. If so, enter
change station extension and set the Test field to n to disable the test.
This also disables Tests #6, #7, #35, and #161 on this port.
Test result
PASS
The station is connected properly. This test may also pass if no terminal equipment is connected
and the terminal is located very far from the switch.
Investigate user-reported troubles on this port by using other port tests, examining station wiring,
or examining the station.
Error code: 0
Test result
NO BOARD
Solution
Control Channel Looparound Test (#52)

The Control Channel Looparound test queries a media module for its board code and vintage
to check the operation of the control channel and board communication. The test passes if the
correct board code and vintage are returned. The test aborts if there is no response. The test fails
otherwise. This test runs on the following maintenance objects:
• MG-ANA (Analog Media Module) on page 427
• MG-ANN (Media Gateway Announcement Module) on page 429
• MG-BRI (BRI Trunk Media Module) on page 431
• MG-DCP (Digital Line Media Module) on page 433
• MG-DS1 (DS1 Interface Media Module) on page 436
• MG-IAMM (Integrated Analog Media Module) on page 442
• XXX-BD (Common port media module) on page 520
Related links
Error: 2000 on page 586
Error: 2000
Test result
ABORT
Cause
Solution
Error code: 2030

Test result
ABORT
Control Channel Looparound Test (#52)
Cause
EPN is down.
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 2500

Test result
ABORT
Cause
Solution
Test result
FAIL
Cause
The circuit pack or media module failed to return its board code or vintage.
Solution
2. If the test continues to fail, reset the circuit pack or media module and rerun the test.
3. If test continues to fail, replace the circuit pack or media module.
Test result
PASS
Cause
The circuit pack or media module is communicating correctly with the switch.
Test result
EXTRA BD
Cause
This result should only appear when more than one TN771D Maintenance/Test circuit pack has
been installed in this port network. Remove the extra circuit pack.
Error code: 0
Test result
NO BOARD
Solution
SAKI Sanity Test (#53)

This test is destructive.
The SAKI Sanity Test resets the media module. It is executed as part of the reset board location
command.
For DS1 Interface Media Modules, this test is executed as part of the long test sequence.
• MG-ANA (Analog Media Module) on page 427
• XXX-BD (Common port media module) on page 520
Related links
Error 1015 on page 589
No error code
Test result
ABORT
SAKI Sanity Test (#53)
Cause
Solution
Error code: 1005

Test result
ABORT
Cause
This error applies only to DS1 media modules. It means the DS1 media module is providing timing
for the system and, therefore, it cannot be reset without causing major system disruptions. If this is
not a gateway system, go to Step 1. If this is a gateway system, go to Step 2.
Solution
If the DS1 Media Module needs to be reset, set the synchronization timing source to another DS1
interface Media Module located in the same gateway and retest.
Error 1015
Test result
ABORT
Cause
Port is not out-of-service.
Solution
1. Busyout the media module with busyout board location.
2. Enter reset board location.
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 1
Test result
FAIL
Cause
The media module failed to reset.
Solution
1. Enter the command again.
2. If the problem persists, replace the media module.
Error code: 2
Test result
FAIL
Cause
The media module failed to reset.
Solution
1. Enter the command again.
2. If the problem persists, escalate this problem.
Test result
PASS
Cause
The media module initialized correctly.
Error code: Any

Test result
NO BOARD
Solution
Hybrid Line Local Digital Looparound Test (#58)
Hybrid Line Local Digital Looparound Test (#58)

This test checks the control channel between the server and the port’s digital circuitry. The server
sends data to the on-board microprocessor and compares the data echoed back. This test is run
on HYB-Line (Hybrid Line).
Related links
No error code
Test result
ABORT
Cause
Solution
Error code: 1000

Test result
ABORT
Cause
call.
2. Enter status station to determine the service state of the port.
If the port is in use, wait until the port is idle before retesting.
Error code: 1004

Test result
ABORT
Cause
Solution
Error code: 2000

Test result
ABORT
Cause
Solution
Error codes: 1, 2, 3
Test result
FAIL
Cause
The control channel between the processor and the port is not transmitting properly. This port is
not operable.
Solution
1. Retry the test.
2. If the failure still occurs, enter busyout location and release location, 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 appears to be isolated to one port, check all wiring to the set and all set
connections.
6. Replace the media module as a last resort.
Test result
PASS
Hybrid Line Remote Digital Looparound Test (#59)
Cause
The control channel is transmitting properly.
If complaints still exist, investigate by using other circuit pack tests, and by examining the station,
wiring, and connections.copy
Error code: 0
Test result
NO BOARD
Solution
Hybrid Line Remote Digital Looparound 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 test will run if the station is in service or out of service.
This test is run on HYB-Line (Hybrid Line).
Related links
No error code
Test result
ABORT
Cause
Solution
Error code: 1
Test result
ABORT
Cause
A request for a remote station audit aborted even though all internal resources were correctly
allocated.
Solution
1. Look in the Error Log for Error Type 18 (port busied out) for this port.
2. If Error Type 18 is present, release the port with release port location or release
station extension, and then run the test again.
Error code: 1000

Test result
ABORT
Cause
call.
Error code: 2000

Test result
ABORT
Cause
Solution
Test result
FAIL
Internal Looparound Test (#135)
Cause
No response was received within the allowed time on one of the transmissions to the terminal.
This indicates a problem 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.
Solution
1. Check for errors in the error log, for example, error 1537.
2. Remotely enter busyout location and release location, 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.
Test result
PASS
Hybrid Line Remote Digital Looparound test passed. The hybrid circuit pack is sending and
receiving proper messages to and from the voice terminal.
If problems still exist, investigate using other circuit pack tests and by examining the station,
wiring, and connections.
Error code: 0
Test result
NO BOARD
Solution
Internal Looparound Test (#135)

The Internal Looparound Test loops the transmitted DS1 bit stream back into the board receiver.
The loop occurs just before the DS1 facility interface. The test is highly destructive and can only
be initiated by a reset board location command.
All of the trunks on the DS1 must first be busied out using the busyout board location
command before the Internal Looparound Test can be executed. If the transmitted and received bit
patterns on a trunk are different, the test fails.
All trunks of the DS1 are restored to the in-service state after release board location is
entered.
This test is run on the following maintenance object:

Related links
Error code: 2000

Test result
ABORT
Cause
Solution
1. Enter display errors on the SAT.
2. Check for Error Type 1538 for this DS1 board.
If Error Type 1538 appears in the error log for this board, see Hyperactive DS1 Media
Module on page 774 for the repair procedures. Otherwise, retry the test at 1-minute
Error code: 2012

Test result
ABORT
Cause
Solution
Retry reset board location at 1-minute intervals up to 5 times.
DS1 Tie Trunk Seizure Test (#136)

The DS1 Tie Trunk Seizure Test verifies the trunk’s signaling capability. The test is composed of
two parts. The first part queries the media module for errors. The second part of the test sends
a seizure message to the DS1 Interface media module and expects an active reply by the DS1
Interface media module. If the system does not receive any reply and the timer expires, the test
fails.
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 media module 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.
Related links
No error code
Test result
ABORT
Cause
Solution
Error code: 1000

Test result
ABORT
Cause
call.
port.
retesting.
3. If the port status is active but the port is idle (no calls), check the error log for Error Type
1025.
See the error log table for a description of this error and required actions for this
maintenance object. The port may be locked up.
Error code: 1004

Test result
ABORT
Cause
Far end is seizing the trunk while the test is ongoing. A glare situation is detected.
port.
retesting.
Error code: 1005

Test result
ABORT
Cause
Incompatible configuration administered on Trunk Group form.
1. Verify the following fields on the Trunk Group administration form:
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 media module while common control
channel signaling is specified?
2. If the trunk has been administered using the above information, this test should abort.
Error code: 1018

Test result
ABORT
Cause
enabling it.
1. Verify that the Maintenance Test field on the Trunk Group administration form is n. To
enable the test, change the trunk administration and enter y in the Maintenance Test field.
2. Repeat the test.
Error code: 1020

Test result
ABORT
Cause
The test did not run due to an already existing error on the specific port or due to a more general
circuit pack or media module error.
1. Examine the error log for existing errors against this port or the media module and attempt
to diagnose the already existing error.
2. Retry the test.
Error code: 1040

Test result
ABORT
Cause
The test is invalid for this trunk port because it is administered as an access endpoint.
Enter display port location to verify that this port is administered as an access endpoint.
In this case the test should abort and no action is necessary.
Error code: 2000

Test result
ABORT
Cause
Error code: 2053

Test result
ABORT, FAIL
Cause
At least one of the following errors is found in the Error Log for the DS1 media module:
• 1281 – Loss of Signal
• 1793 – Blue alarm
• 2049 – Red alarm
• 2305 – Yellow alarm
• 1537 – Hyperactivity.
Look for the above Error Types in the Error Log and follow the procedures for MG-DS1 (DS1
Interface Media Module) on page 436 for the listed Error Types.
Error code: 2100

Test result
ABORT
Cause
Test result
FAIL
Cause
The far-end trunk did not respond to the seizure of the near-end trunk within the allowed time.
Solution
1. If the affected port is located on a Media Module, replace the Media Module.
2. Enter list configuration board location.
3. Verify that the Trunk Type field on the Trunk Group administration form matches the trunk
type administered on far-end switch.
4. Look for MG-DS1 errors in the error log.
If any are present, see MG-DS1 (DS1 Interface Media Module) on page 436 for repair
procedures.
Test result
PASS
The trunk can be seized for an outgoing call.
Loss of Signal Alarm Inquiry Test (#138)
Error code: 0
Test result
NO BOARD
Solution
Loss of Signal Alarm Inquiry Test (#138)

Note:
The term “board” refers to the DS1 Interface Media Modules.
The Loss of Signal Alarm Inquiry Test verifies the synchronization status, echo cancellation, and
continuity of the DS1 link.
A Loss of Signal Alarm indicates that the board is unable to derive the synchronization clock from
the DS1 facility. If the board is administered as a timing source and it detects a Loss of Signal
alarm, the board will stop providing the synchronization clock for the system and will transmit a
Yellow alarm to the remote DS1 endpoint.
When the Loss of Signal alarm is confirmed, every trunk or port of the board is put into the
out-of-service state. The inquiry test will run every 10 minutes until the loss of signal has been
restored.
Blue Alarm Inquiry Test (#139)

Note:
The term “DS1 board” refers to the DS1 Interface Media Module.
A 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 a local DS1 board detects a Blue Alarm signal from the remote DS1 endpoint, it transmits
a Yellow Alarm to the remote DS1 endpoint and sends a BLUE ALARM message to the system.
When the Blue Alarm is confirmed, the system places all trunks or ports of the DS1 board into the
out-of-service state. The inquiry test runs every 10 minutes until the Blue Alarm is cleared.
When the Blue Alarm is cleared, the DS1 board stops transmitting the Yellow alarm and places the
trunks or ports back into the service state they were in before the Blue Alarm occurred.

Related links
Line Loopback Alarm on page 602
Payload Loopback Alarm on page 602
Line Loopback Alarm

The Line Loopback (LLB) is used by the remote DS1 endpoint to put the DS1 board into a
loopback mode. When the DS1 board is in the LLB mode, the arriving bit pattern is regenerated
and sent back. The Line Loopback (LLB) Alarm activates when the in-band activate LLB bit
pattern arrives continuously for 5 seconds on the DS1 line. The LLB deactivates when the in-band
deactivate LLB bit pattern arrives continuously for 5 seconds on the DS1 line.
Since LLB is a condition rendering all DS0 channels unavailable for signaling or bearer traffic, the
system 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. The PLB Alarm activates when a network protocol activate bit pattern arrives
over the 4Kbps ESF data link on the DS1 line. The PLB deactivates when a network protocol
deactivate bit pattern arrives over the 4Kbps ESF data link on the DS1 line.
Since PLB is a condition rendering all DS0 channels unavailable for signaling or bearer traffic, the
system treats this the same as a Blue Alarm.
No error code
Test result
ABORT
Cause
Solution
Blue Alarm Inquiry Test (#139)
Error code: 2000

Test result
ABORT
Cause
Response to the test was not received within the allowed time. This may be due to hyperactivity.
3. If Error Type 1538 appears in the error log for this board, see Hyperactive DS1 Media
intervals up to 5 times
Error code: 2100

Test result
ABORT
Cause
Error codes: 1, 2
Test result
FAIL
Test Result Cause

FAIL The remote DS1 endpoint is out-of-service.
1 FAIL A Line Loopback Alarm (LLB) was detected.
2 FAIL A Payload Loopback Alarm (PLB) was detected.
Solution
1. If the DS1/UDS1 circuit pack or media module connects to a T1 network facility or to
another switch, see T1 network facility procedures on page 775.
2. If the DS1/UDS1 circuit pack or media module connects to a line-side terminating
device such as a PRI terminal adapter, see Line-side terminating device procedures on
page 775.
Test result
PASS
Remote DS1 endpoint is in-service. Neither a Blue alarm nor a Line Loopback alarm nor a
Payload Loopback Alarm was detected.
Error code: 0
Test result
NO BOARD
Solution
Red Alarm Inquiry Test (#140)

A DS1 Interface Media Module 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 board.
When the DS1 board detects a Red Alarm, it transmits a Yellow Alarm to the remote DS1 endpoint
and sends a Red Alarm message to the system. After the Red Alarm is confirmed, the system
places every trunk or port of the DS1 board into the out-of-service state. The inquiry test runs
every 10 minutes until the Red Alarm is cleared.
When the Red Alarm is cleared, the DS1 board stops transmitting the Yellow alarm to the remote
DS1 endpoint. The system restores all trunks or ports of the DS1 board to the service state they
were in before the Red Alarm occurred.
Related links
Loss of Multiframe Alarm on page 604
Loss of Multiframe Alarm

If the DS1 media module is administered using DMI-BOS signaling, it raises a LMA (Loss of
Multiframe Alarm) when it cannot interpret the incoming signaling bits to synchronize to the
multiframe pattern received in the 24th channel. Once the DS1 board detects an LMA, the circuit
pack transmits a RMA (Remote Multiframe Alarm) to the remote DS1 endpoint.
Red Alarm Inquiry Test (#140)
No error code
Test result
ABORT
Cause
Solution
Error code: 2000

Test result
ABORT
Cause
Error code: 2100

Test result
ABORT
Cause
Error code 1
Test result
FAIL
Test Result Cause

FAIL The DS1 media module detected a Red Alarm. An out-of-frame
condition occurred. The DS1 media module will transmit a Yellow
Alarm to the remote DS1 endpoint until the Red Alarm is retired.
Table continues…
Test Result Cause

1 FAIL The DS1 media module detected a loss of multiframe alarm (LMA).
An out-of-frame condition occurred on the DS1 board. The DS1 board
will transmit a remote multiframe alarm (RMA) to the remote DS1
endpoint until the LMA is retired.
Solution
1. If the DS1 media module connects to a T1 network facility or to another switch, see T1
network facility procedures on page 775.
2. If the DS1 media module connects to a line-side terminating device such as a PRI terminal
adapter, see Line-side terminating device procedures on page 775.
Test result
PASS
No Red alarm is detected on the DS1 media module.
Error code: 0
Test result
NO BOARD
Solution
Yellow Alarm Inquiry Test (#141)

The Yellow Alarm Inquiry Test determines whether the remote DS1 endpoint is transmitting
a Yellow alarm. A Yellow Alarm indicates that the remote DS1 endpoint has an out-of-frame
condition.
Once the Yellow alarm is confirmed, all trunks on the DS1 board are put 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, all trunks on the DS1 board are restored back to their previous service
state before the Yellow Alarm was raised.
The Yellow Alarm corresponds to the yellow F2 state documented in CCITT recommendation
I.431.
Related links
Remote Multiframe Alarm on page 607
Yellow Alarm Inquiry Test (#141)
Yellow F5 State Alarm on page 607

Remote Multiframe Alarm

A Remote Multiframe Alarm (RMA) indicates that the remote DS1 endpoint is in a Loss of
Multiframe Alarm condition while the DS1 board 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 to the network. Refer to CCITT
recommendation I.431.
No error code
Test result
ABORT
Cause
Solution
Error code: 2000

Test result
ABORT
Cause
Error code: 2100

Test result
ABORT
Cause
Error codes: 1, 2
Test result
FAIL
Test Result Cause

FAIL The DS1 media module detected a yellow alarm sent by the
remote DS1 endpoint. An out of frame condition occurred at the
DS1 endpoint.
1 FAIL The DS1 media module detected a Remote Multiframe Alarm
sent by the remote DS1 endpoint. An out-of-frame condition
occurs on the remote DS1 endpoint.
2 FAIL The DS1 media module is reporting a yellow F5 State alarm.
There is a fault in the user-network interface from the user to the
network.
Solution
1. If the DS1 media module connects to a T1 network facility or to another switch, see T1
network facility procedures on page 775.
2. If the DS1 media module connects to a line-side terminating device such as a PRI terminal
adapter, see Line-side terminating device procedures on page 775.
Test result
PASS
No Yellow alarm or Remote Multiframe Alarm or F5 State Alarm is received from the remote DS1
endpoint.
Error code: 0
Test result
NO BOARD
Solution
Major Alarm Inquiry Test (#142)
Major Alarm Inquiry Test (#142)

The Major Alarm Inquiry Test determines if the received average DS1 bit error rate on the DS1
facility is greater than 1/1000. All trunks on the DS1 board are put in the out-of-service state if a
Major Alarm lasts for more than 20 minutes.
When the Major Alarm is cleared, all trunks on the DS1 board are restored to their previous
service state before the Major Alarm occurred.
Related links
No error code
Test result
ABORT
Cause
Solution
Error code: 2000

Test result
ABORT
Cause
1. Enter display errors.
Error code: 2100

Test result
ABORT
Cause
Test result
FAIL
Cause
The DS1 media module detects a Major alarm. The DS1 bit error rate is greater than 1/1000. The
performance of the DS1 link between the DS1 board and the remote DS1 endpoint is very poor.
Solution
1. Enter list measurement ds1-log location to read the error seconds
measurement.
page 775.
Test result
PASS
No Major alarm is detected in DS1 board.
Error code: 0
Test result
NO BOARD
Solution
Minor Alarm Inquiry Test (#143)

The Minor Alarm Inquiry test determines if the received DS1 bit error rate is greater than
1/1,000,000 and less than 1/1000.
Minor Alarm Inquiry Test (#143)
Every trunk or port on the DS1 board is kept in the in-service state after the Minor Alarm is
confirmed. The Minor Alarm Inquiry test runs every 10 minutes until the Minor Alarm is cleared.
Related links
No error code
Test result
ABORT
Cause
Solution
Error code: 2000

Test result
ABORT
Cause
1. Enter display errors.
Error code: 2100

Test result
ABORT
Cause
Test result
FAIL
Cause
A Minor Alarm was detected. The performance of the DS1 link between the DS1 board and the
remote DS1 endpoint is poor.
Solution
measurement.
page 775.
Test result
PASS
No Minor alarm is detected in DS1 board.
Error code: 0
Test result
NO BOARD
Solution
Slip Alarm Inquiry Test (#144)

Slips occur when the transmitter and receiver are not running at precisely the same clock rate.
The DS1 media module can detect both positive and negative slips on the DS1 facility. The Slip
Alarm Inquiry Test displays the total number of slips that have occurred on a DS1 link if there are
any.
Every trunk or port of the DS1 board remains in the in-service state. If the DS1 board supplies the
system synchronization source, the MINOR alarm will initiate a synchronization source switch.
Related links
Slip Alarm Inquiry Test (#144)

Error codes: 1 to 88 on page 613
No error code
Test result
ABORT
Cause
Solution
Error code: 2000

Test result
ABORT
Cause
Error code: 2100

Test result
ABORT
Cause
Error codes: 1 to 88
Test result
FAIL
Cause
The DS1 board detected a slip alarm. The Error Code value is the number of slips detected since
the last slip alarm inquiry test.
Test result
FAIL
Cause
A Minor Alarm was detected. The performance of the DS1 link between the DS1 board and the
remote DS1 endpoint is poor.
Solution
measurement.
page 775.
Test result
PASS
No Minor alarm is detected in DS1 board.
Error code: 0
Test result
NO BOARD
Solution
DS1 Translation Update Test (#146)

The DS1 Translation Update Test sends the board-level information specified by System
Administration to the DS1 media module. Translation includes the following data (see the output
of display ds1 location): 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.
DS1 Translation Update Test (#146)
If a DS1 media module is combined with a 120A CSU module or the 401A T1 sync splitter
to screen an Integrated CSU module/T1 sync splitter, this test will also send the administration
for the Integrated CSU to the media module to assure the board’s translations are correct.
The administration of the CSU module/T1 sync splitter is done using the DS1 media module
administration screen. Translation for the CSU module/T1 sync splitter includes the following data:
Transmit LBO, Receive ALBO, Supply CPE Loopback Jack Power.
Related links
No error code
Test result
ABORT
Cause
Solution
Test result
FAIL
Cause
Internal system software error.
Solution
1. Enter display ds1 location to verify the DS1 board translation.
Test result
PASS
Translation data has been downloaded to the DS1 board successfully.
Error code: 0
Test result
NO BOARD
Solution
Link Tear Down Test (#213)

This test disconnects the existing link between the system and the external output device. If the
link has already been disconnected, this test just returns “PASS”. Each resource allocated for an
output device link is released after this test.
• JNL-PRNT (Journal Printer Link) on page 416
• PMS-LINK (Property Management System Link) on page 469
• PMS-PRNT (PMS Printer Link) on page 474
• PRI-CDR (Call Detail Recording Link) on page 477
• SEC-CDR (Call Detail Recording Link) on page 491
Related links
Error codes: 40, 50

Test result
ABORT
Cause
Solution
Error code: 1010

Test result
ABORT
Cause
The Link has been busied out and is out-of-service.
Link Tear Down Test (#213)
PMS-LINK
1. Enter release pms-link to release the PMS Link from the busyout state.
2. Enter test pms-link long to rerun the test.
PMS-PRNT, JNL-PRNT
1. Enter release journal wakeup-log or release journal pms-log to release the
link from the busyout state.
2. Enter test journal wakeup-log long or test journal pms-log long to rerun
the test.
CDR-LNK, PRI-CDR, SEC-CDR
1. Enter release cdr-link primary or release cdr-link econdary to release the
CDR link from the busyout state.
2. Enter test cdr-link primary long or test cdr-link secondary long to rerun
the test.
SYS-PRNT
1. Enter release sp-link to release the System Printer Link from the busyout state.
2. Enter test sp-link long to rerun the test.
Error code: 2012

Test result
ABORT
Cause
Solution
Test result
FAIL
Cause
Solution
Test result
PASS
The output device link is torn down.
Link Retry Test (#215)

This test sends a message to the output device software process to make a data call to the
extension where the output device connects. If the link is already up, this test passes without
making any data call.
• JNL-PRNT (Journal Printer Link) on page 416
• PMS-LINK (Property Management System Link) on page 469
• PMS-PRNT (PMS Printer Link) on page 474
• PRI-CDR (Call Detail Recording Link) on page 477
• SEC-CDR (Call Detail Recording Link) on page 491
Related links
Error codes: 30 on page 618
Error codes: 10, 20

Test result
ABORT
Cause
Solution
Error codes: 30
Test result
ABORT
Cause
Error code: 1010

Test result
ABORT
Cause
The link has been busied out and is out-of-service.
Link Retry Test (#215)
PMS-LINK
1. Enter release pms-link to release the PMS Link.
2. Enter test pms-link long to rerun the test.
PMS-PRNT, JNL-PRNT
1. Enter release journal wakeup-log or release journal pms-log to release the
link from the busyout state.
2. Enter test journal wakeup-log long or test journal pms-log long to rerun
the test.
CDR-LNK, PRI-CDR, SEC-CDR
1. Enter release cdr-link primary or release cdr-link secondary to release
the CDR link from the busyout state.
2. Enter test cdr-link primary long or test cdr-link secondary long to rerun
the test.
SYS-PRNT
1. Enter release sp-link to release the System Printer Link from the busyout state.
2. Enter test sp-link long to rerun the test.
Error code: 2012

Test result
ABORT
Cause
Solution
Test result
FAIL
Cause
The link cannot be established.
Test result
PASS
The output device link is up.
140AY Channel Sanity Inquiry Test (#222)

This test queries the angle to determine the status for a particular channel. If a channel is
insane, announcements cannot be played back on that channel. This test runs on ANN-PT
(Announcement Port).
Related links
No error code
Test result
ABORT
Cause
Solution
Error code: 2000

Test result
ABORT
Cause
Solution
Signaling Link State Audit Test (#255)

This test checks the state of critical signaling link hardware components such as DS1.
Related links
Error code: None or 0 on page 621
Signaling Link State Audit Test (#255)

Error code: None or 0

Test result
ABORT
Cause
Solution
Error code: 1018

Test result
ABORT
Cause
Test is disabled by administration.
To enable the test, enter y in the Maintenance Tests field on the change trunk-group screen.
Error code: 1114

Test result
ABORT
Cause
The signaling link is in a transitional state.
Error code: 1700

Test result
ABORT
Cause
Rollabout video abort for PE-BCHL. The PRI terminal adapter associated with this PRI endpoint
extension is detached from the media module. This is a normal abort when the rollabout video
feature is enabled.
Either reconnect the disconnected PRI terminal adapter or disable the rollabout video feature on
this media module. To do the latter, enter change ds1 location and set the Alarm when PRI
Endpoint Detached? field to y.
Error code: 4
Test Result
FAIL
Cause
There is a problem with the signaling channel.
PE-BCH
There is a problem with the Signaling Channel and/or with the System Link.
Solution
Consult procedures for ISDN-SGR (ISDN-PRI Signaling Group) on page 398 and SYS-LINK
(System Links) on page 512.
See also ISDN-PLK (ISDN-PRI signaling link port) on page 395 for useful information.
Error code: 8
Test Result
FAIL
Cause
There is a problem with the media module.
ISDN-TRK
See the repair procedures for MG-DS1 (DS1 Interface Media Module) on page 436.
Test result
PASS
The signaling link hardware is OK.
Service State Audit Test (#256)

This test performs a service state audit with the far-end terminal adapter to ensure both sides
agree on the service state.
If no reply is received within 2 minutes, the system will automatically try once again. If that
attempt fails, an error will be logged (Error Type 3073) and the system will then attempt recovery
by automatically retrying approximately every 15 minutes. If the port was initially in the INS
(in-service) state, it will now be placed in the MTC/FE (maintenance state, far-end problem) state.
Until a Service State audit attempt is successful, no outgoing calls will be placed over this port,
but incoming calls will be accepted. The service state of this port does not affect the service
state of other ports. If an incoming call that uses this port is presented while in such a state, a
Service State audit attempt will immediately be attempted (that is, the system will not wait for the
15-minute cycle, but will instead try to recover immediately).
PASS for this test only means that a message to the far end was successfully sent.
To check the service state of an TBRI-TRK ISDN BRI channel, enter status trunk grp#/
mem#.
To check the service state of a PRI endpoint port, enter status pri-endpoint extension.
Related links
Error code: 1000

Test result
ABORT
Cause
Needed resources not available, or the port is on a call or initializing.
PE-BCHL, ISDN-TRK
1. Run status trunk grp#/mem#.
2. Check the results of Signaling Link State Audit Test (#255) on page 620.
TBRI-TRK
Run status trunk grp#/mem#.
Error code: 1005

Test result
ABORT
Cause
This test is not be run on this type of port. This error can be ignored.
Error code: 1018

Test result
ABORT
Cause
Test is disabled by administration.
Solution
Enable the test by entering y in the Maintenance Tests field on the change trunk-group screen.
Error code: 1113

Test result
ABORT
Cause
Signaling link failed.
ISDN-TRK
Check the results of Signaling Link State Audit Test (#255) on page 620 and consult procedures
for ISDN-SGR (ISDN-PRI Signaling Group) on page 398.
PE-BCHL
Check the results of Signaling Link State Audit Test (#255) on page 620.
Error code: 1114

Test result
ABORT
Cause
Signaling link in transitional state.
Solution
Error code: 1116

Test result
ABORT
Cause
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.
Error code: 1117

Test result
ABORT
Cause
A service state audit message is outstanding
Solution
Wait 2 minutes, then try again.
Error code: 1700

Test result
ABORT
PE-BCH
Rollabout video abort. The PRI terminal adapter associated with this PRI endpoint extension is
detached from the media module. This is a normal abort when the rollabout video feature is
enabled.
Solution
1. Either reconnect the disconnected PRI terminal adapter or disable the rollabout video
feature on this media module.
2. To do the latter, enter change ds1 location and set the Alarm when PRI Endpoint
Detached? field to y.
Error code: 2100

Test result
ABORT
Cause
Test result
FAIL
Cause
Test result
PASS
Wait 4 minutes, then check the Error Log for any new errors of type 3073.
If there are no new errors of type 3073, then both sides of the ISDN connection agree on the
service state. The negotiation succeeded.
If there is a new error of type 3073, the negotiation failed. The system will automatically retry
approximately every 15 minutes. If the port was initially in the INS (in-service) state, it will now be
placed in the MTC/FE (maintenance, far-end problem) state. Incoming calls will be accepted, but
no outgoing calls will be originated this port. If an incoming call is presented, another Service State
audit will be immediately performed in an attempt to bring the port into the proper state.
Call State Audit Test (#257)

This test audits internal call state data by querying the far-end terminal adapter as to the ISDN
state of the call. This can be helpful when trying to clear a hung call. 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. If the internal call state data on the near-end switch is different
than that of the far-end terminal adapter, the call will be 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
(Error Type 1 for ISDN-PLK).
Related links
Error code: 1018

Test result
ABORT
Call State Audit Test (#257)
Cause
Test is disabled.
Enable the test by entering y in the Maintenance Tests field on the change trunk-group x,
where x is the number of the trunk group to be tested.
Error code: 1019

Test result
ABORT
Cause
Audit already in progress.
Wait 2 minutes, and try again.
Error code: 1113

Test result
ABORT
Cause
ISDN-TRK, PE-BCHL
Error code: 1114

Test result
ABORT
Cause
Signaling link in transitional state.
Error code: 1116

Test result
ABORT
Cause
The trunk is in an out-of-service ISDN service state. A call cannot be made if the trunk is in this
state. No action is necessary.
ISDN-TRK, TBRI-TRK
Check the trunk service state with status trunk grp#/mem#.
PE-BCHL
Enter status pri-endpoint extension to investigate the ISDN state of the port.
Error code: 1700

Test result
ABORT
PE-BCH
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.
Solution
1. Reconnect the disconnected PRI terminal adapter or disable the rollabout video feature on
this circuit pack.
2. To do the latter, enter change ds1 location and set the Alarm when PRI Endpoint
Detached? field to y.
Error code: 2100

Test result
ABORT
Cause
Test result
FAIL
Cause
Test result
PASS
A call-state auditing message was successfully sent to the far-end to verify the state of the call
active on this port.
Use display errors for the board to determine the true results of the test.
When this test is run, a 2-minute timer is started and a Layer 3 Status Inquiry message is sent to
the far-end. The test passes when a response is received from the far-end.
ISDN Test Call Test (#258)

This test performs a far-end looparound test over an ISDN trunk if:
• The trunk is in-service, maint-NE, or out-of-service/NE.
• 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 trunk to be tested. If a Maintenance/Test media
module does not reside in the system, 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.
If a Maintenance/Test media module does reside in the system, 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 media module. The digital port on a TN771D
Maintenance/Test media module sends a bit pattern to the far end which is echoed back. If the
received pattern matches the pattern that was sent, the test passes. If there are differences, the
test fails.
If a test call is running when scheduled maintenance starts, the green LED is turned off. To
determine whether a test call is still running:
• Enter list isdnpri-testcall and status isdnpri-testcall.
• Check for a lit amber LED on the Maintenance/Test media module.
Synchronous Test Calls
Enter one of the following commands to initiate a synchronous outgoing test call:
• test trunk grp#/mem# long [repeat #]
• test board location long [repeat #]
• test port location long [repeat #]
The duration of the test call is 8.6 seconds for unrestricted (B8ZS) B-Channels and 9.4 seconds
for restricted (ZCS) B-Channels. The test fails if the bit error rate retrieved from the Maintenance/
Test digital port is greater than 0. When this occurs, perform further diagnostics such as test
isdnpri-testcall.
Asynchronous Test Calls
You can start, query, and stop an outgoing test call by using the following commands:
• test isdnpri-testcall grp#/mem# [minutes #]
This command initiates an outgoing ISDN-PRI test call up to 120 minutes. Default times are
as above. Only one trunk per PN can be tested at one time.
• status isdnpri-testcall grp#/mem#
This command displays the progress of the outgoing test call by reporting bit and block error
rates of the tested B-Channel.
• clear isdnpri-testcall grp#/mem#
This command terminates an outgoing test call already in progress. Measurements already
collected are not cleared until the next test call begins.
A PASS of the asynchronous test indicates only that the test call was successfully established.
Enter status and list to get the results of the test.
Note:
Before attempting to make an ISDN-PRI test call to the public network (that is, the network
of 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.
Only one trunk can be tested in a given port network, until the test call is canceled or completes.
Related links
Error code: None, 2000, 2012, 2035, 2036, 2037, 2038, 2039, 2040, 2041, 2066, 2067 on
page 635
Error code: 4
Test result
ABORT
Cause
A trunk has not been translated.
If the trunk should not be translated, no action is necessary.
Error code: 1004

Test result
ABORT
Cause
B-Channel in use.
1. To see if a call is active, enter status trunk grp#/mem#.
2. If the service state is In-Service/Idle, retry the test.
Error code: 1005

Test result
ABORT
Cause
Bad configuration, such as no Maintenance/Test media module.
1. Make sure that the Maintenance/Test media module is inserted.
2. Repeat the test.
Error code: 1018

Test result
ABORT
Cause
Test call disabled.
1. Set the Maintenance field on the Trunk Group screen to y.
2. Repeat the test.
Error code: 1019

Test result
ABORT
Cause
Another Test call is in progress.
1. Enter list isdnpri-testcall to locate the test call.
2. Enter status isdnpri-testcall to find out the duration and start time of the test call.
3. Enter clear isdnpri-testcall to stop the test call from running.
4. If time and duration indicate that the test call should have stopped, and clear isdnpri-
testcall does not work.
Error code: 1020

Test result
ABORT
ISDN-TRK
There is a problem with the DS1 interface media module.
Solution
Consult the procedures for the appropriate DS1 interface media module.
TBRI-TRK
The B-Channels are in an inconsistent state, the B-Channel does not exist at the far-end, or the
B-Channel has been rejected by the far-end.
Error code: 1024

Test result
ABORT
Cause
Maintenance/Test digital port in use.
1. Wait until the yellow and green LEDs on the Maintenance/Test media module are OFF.
2. Rerun the test.
Error code: 1113

Test result
ABORT
Cause
ATM-BCH, ISDN-TRK
Solution
Error code: 1114

Test result
ABORT
Cause
The signaling link is in a transitional state.
Solution
Error code: 1116

Test result
ABORT
Cause
The switch could not change the service state.
1. To see if a call is active, enter status trunk grp#/mem#.
2. If a call is active, wait for the call to finish normally, or drop it by running busyout trunk
grp#/mem#.
3. Rerun the test.
4. If a call is not active:
• ATM-BCH: Check the Error and Alarm Logs for ATM-TRK problems.
• ISDN-TRK: Check the Error and Alarm Logs for ISDN-TRK problems and see ISDN-
TRK (DS1 ISDN Trunk) on page 405.
• TBRI-TRK: Check the error and alarm logs for TBRI-TRK problems.
Error code: 1117

Test result
ABORT
Cause
ISDN service message outstanding.
Wait two minutes, then try again.
Error code: 1118

Test result
ABORT
Cause
Far-end of trunk is not administered.
1. Check the administration of the far end of the trunk. Run status trunk grp#/mem#.
2. Try the test again.
Error code: 1119

Test result
ABORT
Cause
The test call was aborted due to a normal call attempt on this trunk. The test call will only be
performed if the trunk is idle.
1. Wait for the call to finish normally, or drop it by running busyout trunk grp#/mem#.
2. When the trunk is idle, retry the test.
Error code: 1120

Test result
ABORT
Cause
The trunk is in the out-of-service/far-end state.
1. Try to change the service state with Service State Audit Test (#256) on page 622.
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.
Error code: 1122

Test result
ABORT
Cause
No test-line number for the far-end switch.
1. Check the Trunk Group administration form.
Error code: 1123

Test result
ABORT
Cause
No Feature Access Code administration for this Facility test.
Check the Dial Plan and Feature Administration form.
Error code: 1412

Test result
ABORT
Cause
Error code: None, 2000, 2012, 2035, 2036, 2037, 2038, 2039, 2040,
2041, 2066, 2067
Test result
ABORT
Cause
2. If the test continues to abort, there is a serious internal problem.
Error code: 2074

Test result
ABORT
Cause
Bit and Block Error query failed.
2. If the test continues to abort, there may be a serious internal problem in the Maintenance/
Test Digital port.
Error code: 2075

Test result
ABORT
Cause
Error code: 2100

Test result
ABORT
Cause
Error code: 2104

Test result
ABORT
Cause
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 isdnpri-testcall.
For further instructions see “Troubleshooting ISDN-PRI test calls” in Maintenance
Error code: 2042

Test result
FAIL
Cause
The test data is corrupt. There is a loss of integrity on the communications path.
1. Take the trunk out of service and check the quality of the facility including the transmission
facility and any external equipment such as DACs, CSUs, etc.
TSC Heartbeat Inquiry Test (#604)
2. Enter test isdnpri-testcall and status isdnpri-testcall to get the bit and
block error rates.
Test result
PASS
The test pattern was sent and received properly. If the synchronous test call was performed (long
test sequence), the communications path is operating properly. If test isdnpri-testcall was
used, PASS indicates only that the test call was established.
1. Enter status isdnpri-testcall to get the bit and block error rates detected by the
test. etc.
2. If the bit and block error rates are not acceptable, perform a complete analysis of the
facility including the transmission facility and any external equipment such as DACs,
CSUs,

This test can be invoked for any ADM TSC administered in the switch. Most of the error conditions
in the following table will 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 ADM TSC. It
passes if the far end sends a response. It fails if there is no response.
This test runs on TSC-ADM (Administered temporary signaling connections) on page 518.
Related links
Error code: 2100

Test result
ABORT
Cause
Solution
Enter test tsc-administered at 1-minute intervals up to 5 times.
Error code: 1005

Test result
ABORT
Cause
The Administered TSC does not exist.
Solution
1. Display the administration for the Administered TSC.
2. If an Administered TSC exists, enter test tsc-administered.
Error code: 1113

Test result
ABORT
Cause
The D-channel is out-of-service.
Solution
See ISDN-PLK (ISDN-PRI signaling link port) on page 395.
Error code: 1145

Test result
ABORT
Cause
There is congestion in the network.
Solution
1. Enter status tsc-administered at 1-minute intervals up to 5 times.
2. If the congestion does not clear, disable and enable the Administered TSC using change
signaling-group grp#.
Note:
To disable the Administered TSC, display the (administration) Signaling Group screen
using change signaling-group grp#, where grp# is the number of the signaling
group under which the suspect TSC is administered. Set the Enable field to n. To
enable the ADM TSC, set the Enable field to y.
3. If the congestion still does not clear, check other nodes in the network.
Error code: 1146

Test result
ABORT
Cause
The congestion just occurred in the network.
Solution
2. If the congestion does not clear, disable and enable the Administered TSC using change
signaling-group grp#.
Note:
To disable the Administered TSC, display the (administration) Signaling Group screen
using change signaling-group grp#, where grp# is the number of the signaling
3. If the congestion still does not clear, check other nodes in the network.
Error code: 1147

Test result
ABORT
Cause
The ADM TSC is being torn down.
Solution
2. If ADM TSC is still down, disable and enable the ADM TSC using change signaling-
group grp#.
Note:
To disable the ADM TSC, display the Signaling Group administration screen using
change signaling-group grp#, where grp# refers to the number of the signaling
3. If the ADM TSC is still down, check other nodes in the network.
Error code: 1148

Test result
ABORT
Cause
The ADM TSC is enabled, but inactive at the near end.
Solution
1. Disable and enable the ADM TSC.
2. Enter test tsc-administered.
3. If the ADM TSC is still inactive, check other nodes in the network.
Error code: 1149

Test result
ABORT
Cause
The ADM TSC is disabled.
Solution
1. Enable the TSC, and see if the status indicates active.
3. If the TSC still disabled, remove the ADM TSC from the system.
Error code: 1181

Test result
ABORT
Cause
Ran out of ADM TSC resources.
Solution
Enter status tsc-administered at 1-minute intervals up to 3 times.
Error code: 2000

Test result
ABORT
Cause
The Administered TSC is not responding to a TSC heartbeat inquiry.
Solution
2. If the problem continues to fail, obtain the status of the D-channel or D-channel pair
associated with the ADM TSC using status signaling-group grp#. If the D-channel
is INS (i.e., in-service) and the status of the ADM TSC appears to be active, then disable
and enable the ADM TSC through administration.
Note:
To disable the ADM TSC, display the Signaling Group administration screen using
change signaling-group grp#, where grp# refers to the number of the signaling
4. If the test fails, check the ADM TSC node on the other side of the network to verify that the
ADM TSC is indeed active.
Error code: 2012

Test result
ABORT
Cause
Solution
Enter test tsc-administered at 1-minute intervals up to 5 times.
Error code: 1
Test result
FAIL
Cause
The Administered TSC is not active (far end).
Solution
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 test tsc-administered.
Error code: 2
Test result
FAIL
Cause
Facility IE (Information Element) reject.
Solution
Check every other node in the network, and make sure Administered TSC is active.
Test result
PASS
The Administered TSC responded to a heartbeat.
BRI Port Local TDM Looparound Test (#619)

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 looparound test runs the following individual tests on the two B-channels (B1 and B2)
associated with the port:
• Looparound test across the TDM Bus for B1.
• Conference Circuit test for B1.
• Looparound test across the TDM Bus for B2.
• Conference Circuit test for B2.
The tests are run in the above order. If one test fails, the remaining tests in the sequence are not
executed and an error code is returned at that point.
This test runs on BRI-PORT (ISDN-BRI Port) on page 316.
Related links

Error code: 1000

Test result
ABORT
Cause
call.
1. Enter display port location to determine the station extension or trunk group/
member number of the port.
2. Enter status bri-port location to determine the service state of the port.
3. If the port is in use, wait until the port is idle before retesting.
Error code: 1002

Test result
ABORT
Cause
Error code: 1003

Test result
ABORT
Cause
Solution
tone receivers.
Error code: 1004

Test result
ABORT
Cause
The port has been seized by a user for a valid call.
Solution
1. Enter status station or status trunk for the station or trunk associated with this
port, and determine when the port is available for testing.
3. If the test continues to abort and the port is idle, escalate the problem.
Error code: 1005

Test result
ABORT
Cause
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 Avaya Adjunct
Links. This error can be ignored.
Error code: 1412

Test result
ABORT
Cause
Error code: 2000

Test result
ABORT
Cause
Solution
1. If this result occurs repeatedly, attempt to reset the circuit pack if the other ports are idle.
2. If this result occurs again, replace the circuit pack.
Error codes: 2012, 2100, 2103

Test result
ABORT
Cause
• Error code 2012: Internal system error.
• Error code 2100: Could not allocate the necessary system resources to run this test.
• 2103: The system could not make the conference connection for the test.
Solution
Error codes: 1, 2, 7, 8
Test result
FAIL
Cause
• Error code 1: TDM Looparound test failed on B1.
• Error code 2: TDM Looparound test failed on B2.
• Error code 7: Conference Circuit test failed on B1.
• Error code 8: Conference Circuit test failed on B2.
Solution
1. If the test fails repeatedly, try to reset the circuit pack if the other ports on the circuit pack
are idle.
2. If the test fails again, replace the circuit pack.
Test result
PASS
Cause
The BRI Port Local TDM Looparound test 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.
Related links
Error code: 1005

Test result
ABORT
Cause
This test is not valid for this type of port. This error can be ignored.
Error code: 2012

Test result
ABORT
Cause
Solution
Test result
PASS
Level 1 Status Inquiry Test (#621)
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, the Error Log should be checked for any
entries with Error Type 257 to examine the real results of this test.
An Error Type of 257 in the Error Log indicates some problem with the power to the station
or the adjunct.
2. Check for a short in the wiring, a damaged jack, a defective voice terminal or adjunct, or an
incorrect type of terminal.

This test determines the state of the transmission facility of a BRI port at the physical layer (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 Avaya 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. 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 transit to the Activated state (Endpoint Active).
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 a busyout port
location request.
This test runs on ASAI-PT (ASAI Port) on page 314 and BRI-PORT (ISDN-BRI Port) on page 316.
Related links
Error code: 1187

Test result
ABORT
Cause
The board, port, or station may have been busied out by a technician.
Solution
1. Look in the Error Log for Error Type 18 (port busied out) for this port and ASAI-BD or
BRI-BD (board busied out).
2. If this Error Type is present for ASAI-PT or BRI-PORT only, release the port using
release port location and run the test again.
3. If the error is present for both ASAI-BD and ASAI-PT or BRI-BD and BRI-PORT, release
the board using release board location and run the test again.
Note:
When you release a port, you release every port associated with it. If certain ports still
need to be busied out, use busyout port location to busy them out.
Error code: 2000

Test result
ABORT
Cause
Solution
1. If this result occurs repeatedly up to five times, attempt to reset the circuit pack if the other
ports are idle.
2. If the test aborts again, replace the circuit pack.
Error code: 2012

Test result
ABORT
Cause
Error code: 2100

Test result
ABORT
Cause
Solution
2. If the test still fails, escalate the problem.
Error code: 1
Test result
FAIL
Cause
Received a status of Level 1 Pending Activation-Endpoint Idle which indicates a problem with the
BRI endpoint or ASAI or Avaya adjunct, the wiring to the endpoint or adjunct, or the ISDN-BRI
port.
The TN2198 received a status of Level 1 Pending Activation - 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 Avaya terminals to a 2-wire
TN2198 circuit pack. The NT1 also has status lamps to determine the health of the unit.
Solution
1. Do one of the following:
• For the TN556, 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.
3. Enter test port location, and review the results of the Level 1 Status Inquiry test to
verify the repair.
4. If this test is still failing, proceed to the next step.
• For BRI endpoints, replace the BRI endpoint(s) connected to the port or the NT1 if a
TN2198 is used.
• For ASAI or Avaya adjuncts, follow the recommended repair procedures of the
manufacturer for link communication problems.
• For the NT1, follow the manufacturer’s repair procedures.
6. Enter test port location and review the results of the Level 1 Status Inquiry test to
verify repair.
7. If this test is still failing, escalate the problem.
Error code: 2
Test result
FAIL
Cause
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 Avaya 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).
Solution
adjunct.
2. Enter test port location, and review the results of the Level 1 Status Inquiry test to
verify the repair.
• For BRI endpoints, try replacing the BRI endpoint(s) connected to the port.
• For ASAI or Avaya adjuncts, follow the recommended repair procedures of the
manufacturer for link communication problems.
• For the NT1, follow the manufacturer’s repair procedures.
5. Enter test port location and review the results of the Level 1 Status Inquiry test to
verify repair.
6. If this test is still failing, escalate the problem.
Error code: 3
Test result
FAIL
Cause
Received a status of Level 1 Deactivated; the port is out-of-service.
Electronic Power Feed Inquiry Test (#622)
Solution
1. Enter status bri-port location to verify that the service state of the port is out-of-
service.
2. If the service state of the port is not out-of-service, escalate the problem to the next tier.
Otherwise, proceed to the next step.
3. If the port has been placed out-of-service via busyout port location, try releasing the
port by executing the release port location.
4. Then enter test port long location, and review the results of Level 1 Status Inquiry
test. If this test is still failing, proceed to the next step.
5. After executing test port long location, review the results of every test.
6. Follow the repair procedures for any tests that fail.
7. Verify repair of the problem by executing test port location and by determining that the
Level 1 Status test passes. .
8. If the test continues to fail for this reason, escalate the problem
Error code: 4
Test result
FAIL
Cause
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.
Solution
1. For the NT1 follow the manufacturers recommended repair procedures.
2. Enter test port location, and review the results of Level 1 Status Inquiry test.
3. f the test is still failing, escalate the problem.
Test result
PASS
Level 1 is activated or the system has taken the port out of service.
Electronic Power Feed Inquiry Test (#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 Avaya 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 the TN2198.
The TN2208 has no power feeds.
Related links
Error code: 1005

Test result
ABORT
Cause
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. This error can be ignored.
Error code: 2000

Test result
ABORT
Cause
Solution
1. If this result occurs repeatedly up to five times, reset the circuit pack and rerun the test.

Test result
ABORT
Cause
Solution
CRC Error Counter Test (#623)
Error code: 1
Test result
FAIL
Cause
The BRI-LINE circuit pack reports that it has detected an overcurrent condition and has turned off
the EPF.
Solution
adjunct.
2. Check the endpoints and replace one or both sets if the sets are drawing too much current.
3. Enter test port location, and review the results of the EPF Inquiry test to verify the
repair.
5. Enter test port location and review the results of the Level 1 Status Inquiry test.
6. If this test is also failing, then follow the repair procedure for the Level 1 Status Inquiry test.
Otherwise, escalate this problem to the next tier.
Test result
PASS
The Electronic Power Feed Inquiry test reports that the EPF is on.
CRC Error Counter Test (#623)

This test reads the port’s CRC error counters that are maintained on the circuit pack. The Cyclic
Redundancy Check (CRC) is a means of error detection to determine the integrity of data frame
contents. The CRC error counter is incremented by the circuit pack when it detects a CRC error.
The test passes if the value of the counter is 0, meaning 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 test runs on ASAI-PT (ASAI Port) on page 314, BRI-PORT (ISDN-BRI Port) on page 316.
Related links
Error code: 2000

Test result
ABORT
Cause
Solution

Test result
ABORT
Cause
Solution
Error code: Any

Test result
FAIL
Cause
The circuit pack is detecting CRC errors. The Error Code field contains the value of the counter.
This error occurs when a frame with a bad CRC is received over the D-channel by the circuit pack.
The problem is most likely due to a problem with the wiring to the set or adjunct, interference on
the wiring caused by a noise source such as an electrical motor or generator, or no termination
(open circuit). It usually does not indicate a problem with the circuit pack.
Test result
PASS
The error counter was cleared successfully.
Layer 1 Transmission Error Counter Test (#624)
Layer 1 Transmission Error Counter Test (#624)

This test reads and clears the port’s Layer 1 Transmission error counter maintained on the ASAI
or 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. It does not
indicate a problem with the circuit pack. This test is useful for verifying the repair of the problem.
This test runs on ASAI-PT (ASAI Port) on page 314.
Related links
Error code: 2000

Test result
ABORT
Cause
Solution

Test result
ABORT
Cause
Solution
Error code: Any

Test result
FAIL
Cause
The circuit pack is still detecting errors of this type. The Error Code field contains the value of this
counter.
Solution
2. If the test continues to fail, review the results of other tests in the long test sequence.
3. Note 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.
4. 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. If the wiring appears to
be fine, escalate the problem.
Test result
PASS
The Layer 1 Transmission error counter has a value of 0.
Receive FIFO Error Counter Test (#625)

This test reads and clears the port’s Receive FIFO error counter maintained on the 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 not
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 a 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. This test is useful for verifying the repair of the problem.
• ASAI-PT (ASAI Port) on page 314
• BRI-PORT (ISDN-BRI Port) on page 316
Related links
Error code: 2000

Test result
ABORT
Receive FIFO Error Counter Test (#625)
Cause
Solution
1. If this result occurs repeatedly up to 5 times, reset the circuit pack and rerun the test.

Test result
ABORT
Cause
Solution
Error code: Any

Test result
FAIL
Cause
The circuit pack is still detecting errors of this type. The Error Code field contains the value of this
counter.
Solution
2. If the test continues to fail, review the results of other tests in the long test sequence.
3. Note the results of the Receive FIFO Error Counter test. Follow repair procedures for any
of the tests that fail. Otherwise, go to the next step.
4. If the tests for the endpoints or adjunct pass and the Receive FIFO Error Counter test
continues to fail, check the wiring to the endpoints or adjunct.
Test result
PASS
The Receive FIFO error counter has a value of 0.
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).
For every endpoint type, 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).
This test runs on ASAI-EPT (ASAI Endpoint) on page 308 and BRI-SET, Various Adjuncts on
page 321.
Related links
Error code: 1139

Test result
ABORT
Cause
The PN’s packet bus in the port network is out-of-service.
Signaling Link Status Test (#626)
Error code: 1144

Test result
ABORT
Cause
The PPN’s packet bus is out-of-service.
Solution
1. Follow the repair procedures for the PPN’s packet bus.
2. After completing step 1, enter test port long PCSSpp and view the results of the BRI
Port Local LAN Looparound Test (#618) to verify the repair.
Error code: 1187

Test result
ABORT
Cause
The circuit pack, port, or station may have been busied out by command.
Solution
1. Look in the Error Log for Error Type 18 (busied out) for ASAI-BD, ASAI-PT, ASAI-EPT,
BRI-BD, BRI-PORT, or BRI-SET.
2. If this Error Type is present for ASAI-EPT or BRI-SET only, release the port using
release station extension and run the test again.
3. If this Error Type is present for ASAI-PT and ASAI-EPT or BRI-PORT and BRI-SET, use
4. If this Error Type is present for ASAI-BD, ASAI-PT, and ASAI-EPT or BRI-BD, BRI-PORT,
and BRI-SET, enter release board location and run the test again.
Error code: 2012

Test result
ABORT
Cause
Error code: 1113

Test result
FAIL
Cause
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.
Solution
Enter status bri-port location and see the associated procedures in BRI-PORT (ISDN-BRI
Port) on page 316.
Test result
PASS
The signaling link is connected at Layer 2 and “bound” to the BRI endpoint or ASAI adjunct.
Error codes: 2100

Test result
ABORT
Cause
Solution
BRI Remote Loopback Test (#627)

This test checks the integrity of a circuit-switched B-channel connection between the switch and
the endpoint.
The endpoint is put in the “maintenance busy” state to prevent the switch from entering calls to the
endpoint during the test. An application message containing a loopback activate request for the
appropriate B-channel is sent to the endpoint. The endpoint responds with a loopback activated
response. The switch 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. The switch 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. This test is run on BRI-SET, Various Adjuncts on page 321.
Related links
Error code: 1000

Test result
ABORT
Cause
Could not seize the endpoint or B-channels for test.
Error code: 1005

Test result
ABORT
Cause
The endpoint’s MIMs Supported field is administered to “no”.
Solution
Enter change station extension to change the field only if the endpoint documentation
reflects support for ISDN-BRI Management and Maintenance Procedures.
Error code: 1113

Test result
FAIL
Cause
The signaling link between the switch and the endpoint is down.
1. Enter test port location long to clear any errors that prevent establishment of the
signaling link.
2. Examine the results of the Signaling Link Status test (#626) that is run as part of this
command.
If this test aborts or fails, follow the repair procedure for Signaling Link Status Test
(#626) on page 658.
3. If the XID test (#628) continues to abort, escalate the problem.
Error code: 1139

Test result
ABORT
Cause
The PN’s packet bus is out-of-service.
1. Follow the repair procedures for the packet bus.
2. Enter test port long location.
Error code: 1144

Test result
ABRT
Cause
2. After completing step 1, execute test port long PCSSpp, and review the results of the
BRI Port Local LAN Loop Around test (#618) to verify the repair.
Error code: 1187

Test result
ABORT
Cause
The circuit pack, port, or station may have been busied out by a technician.
Solution
1. Look in the Error Log for Error Type 18 (busied out) for BRI-BD, BRI-PORT, or BRI-SET.
a. If this Error Type is present for BRI-SET only, then release the station via release
station.
b. If this Error Type is present for BRI-PORT and BRI-SET, then release the port with
c. If the error is present for BRI-BD, BRI-PORT, and BRI-SET, then release the circuit
pack with release port location and run the test again.
d. If the error is present for both BRI-BD and BRI-PORT, release the circuit pack with
release board location and run the test again.
e. If the error is present for BRI-SET only, release the circuit pack with release port
location and run the test again.
Note:
When you release the circuit pack, you release every port associated with it. If certain
ports still need to be busied out, enter busyout port location to busy them out.
Error code: 1412

Test result
ABORT
Cause
Error code: 2012

Test result
ABORT
Cause
Solution
Error code: 2068

Test result
ABORT
Cause
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 Loopback testing.
Solution
Enter change station extension and set the MIMs Supported field to n.
Error code: 2069

Test result
ABORT
Cause
The endpoint has returned an error response to the application message sent by the switch.
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 2000

Test result
FAIL
Cause
No loopback activation or deactivation response received from the endpoint.
Solution
1. Consult the endpoint documentation to determine if ISDN-BRI Management and
Maintenance Procedures are supported.
2. If not supported, use change station extension to set the MIMs Supported field to
n.
3. Enter busyout station extension and release station extension to busyout
and release the endpoint to resolve any endpoint alarms resulting from failure of this test.
4. If the endpoint supports these procedures and the test continues to fail, assume the
endpoint is defective and replace it.

Test result
FAIL
BRI XID Test (#628)
Cause
• Error code 2071: No data is detected on Channel B1 during loopback.
• Error code 2072: No data is detected on Channel B2 during loopback.
Solution
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.
Test result
PASS
The endpoint has responded to the switch activate and deactivate loopback application messages.
Data has been detected on the looped back channels.
BRI XID Test (#628)

This test checks the D-channel connection between the server and an endpoint or adjunct.
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 on the Station Administration screen for ports on a
TN2208.
This test runs on BRI-SET, Various Adjuncts on page 321.
Related links
Error code: 1000

Test result
ABORT
Cause
The BRI-SET, ASAI-ADJ, ATT-ADJ, LGATE-AJ, ATTE-AJ is busy. The test cannot be executed at
this time.
Solution
1. Wait 1 minute and rerun the command.
2. If this problem persists, escalate this problem.
Note:
A BRI-PORT can also be busy. When running this test for BRI-PORT or ABRI-PORT,
the above maintenance objects can be changed to “BRI-PORT, ABRI-PORT, ATT-
ADJ”.
Error code: 1005

Test result
ABORT
Cause
The endpoint is not administered to support XID testing.
Solution
If the endpoint documentation reflects support XID testing, enter change station extension
and change the XID Testing field on the screen to y.
Error code: 1113

Test result
FAIL
Cause
Solution
signaling link.
2. Examine the results of the Signaling Link Status test (#626) that is run as part of this
command.
(#626) on page 658.
3. If the XID test (#628) continues to abort, escalate the problem.
BRI XID Test (#628)
Error code: 1139

Test result
ABORT
Cause
Solution
Error code: 1144

Test result
ABRT
Cause
Solution
Error code: 1187

Test result
ABORT
Cause
Solution
a. If this Error Type is present for BRI-SET only, use release station to release the
station.
b. If this Error Type is present for BRI-PORT and BRI-SET, use release port
c. If the error is present for BRI-BD, BRI-PORT, and BRI-SET, use release port
location to release the circuit pack,and run the test again.
d. If the error is present for BRI-SET only, use release port location to release
the circuit pack, and run the test again.
e. If the error is present for both BRI-BD and BRI-PORT, use release board
location to release the circuit pack, and run the test again.
Note:
ports still need to be busied out, enter busyout port location.

Test result
ABORT
Cause
Solution
Error code: 2000

Test result
FAIL
Cause
The XID-RESPONSE message was not received from the endpoint.
Solution
1. Consult the endpoint’s documentation to determine whether layer-2 XID and XID-
RESPONSE messages are supported.
2. If the documentation reflects no support for these messages, use change station
extension and change the XID Testing field to n.
3. If the endpoint supports these layer-2 messages and the test continues to fail, assume the
4. If the test continues to fail, escalate the problem.
Test result
PASS
The switch can successfully pass messages over the D-channel to the BRI endpoint.
BRI Layer 3 Query Test (#629)

The BRI Layer 3 Query Test checks 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.
This test is not executed for ASAI and Avaya adjuncts 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 Error Log.
This test runs on BRI-SET, Various Adjuncts on page 321.
Related links
Error code: 1005

Test result
ABORT
Cause
The endpoint’s MIMs Supported? field is administered to no.
Solution
Enter change station extension to change the field only if the endpoint documentation
reflects support for ISDN-BRI Management and Maintenance Procedures.
Error code: 1113

Test result
ABORT
Cause
The signaling link between the switch and the endpoint or adjunct is down.
signaling link.
2. Examine the results of the Test 626.
(#626) on page 658.
3. Escalate problem if BRI Layer 3 Query test continues to abort.
Error code: 1139

Test result
ABORT
Cause
Error code: 1144

Test result
ABRT
Cause
Error code: 1187

Test result
ABORT
Cause
Solution
a. If this Error Type is present for BRI-SET only, release the station via release
station.
b. If this Error Type is present for BRI-PORT and BRI-SET, release the port with
c. If the error is present for BRI-BD, BRI-PORT, and BRI-SET, release the circuit pack
with release port location, and run the test again.
d. If the error is present for both BRI-BD and BRI-PORT, release the circuit pack with
release board location, and run the test again.
Note:
ports still need to be busied out, enter busyout port location to busy them out.
Error code: 2012

Test result
ABORT
Cause
Solution
Error codes: 2100

Test result
ABORT
Cause
Solution
Error code: 2068

Test result
ABORT
Cause
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.
Solution
Enter change station extension and change the MIMs Supported (?) field to n.
Error code: 2069

Test result
ABORT
Cause
The endpoint has returned an error response to the switch sent application message.
Solution
Error code: 2000

Test result
FAIL
Cause
No response is received from the endpoint or the adjunct. For BRI endpoints:
Solution
1. Consult the endpoint’s documentation to determine whether ISDN-BRI Management and
Maintenance Procedures are supported.
2. If not supported, use change station extension to change the MIMs Supported
field to n.
3. Enter busyout station extension and release station extension to busyout
and release the endpoint to resolve any endpoint alarms resulting from failure of this test.
4. If the endpoint supports these procedures and the test continues to fail, assume the
Test result
PASS
The endpoint has successfully responded to the switch’s application message.
BRI Set Audits Test (#630)
BRI Set Audits Test (#630)

This is a series of tests that are classified as audits. The switch sends messages to the BRI
endpoint to perform the following tests:
• Ringer Audit – This audit verifies that both the switch and the endpoint agree as to the
current state of the endpoint’s ringer.
• Lamps Audit – This audit verifies that both the switch and the endpoint agree as to the
current state of the endpoint’s lamps.
• Call Activity Audit – This audit verifies that the state of calls is consistent between the switch
and the endpoint.
This test is not executed for ASAI or Avaya adjunct because adjuncts do not employ ringers or
lamps and do not establish calls on the B-channels associated with the BRI interface.
This test is run on BRI-SET, Various Adjuncts on page 321.
Related links
Error code: 1113

Test result
ABORT
Cause
Solution
signaling link.
2. Examine the results of the Test 626 that is run as part of this command.
(#626) on page 658.
3. If the BRI Set Audits test continues to abort, escalate the problem.
Error code: 1139

Test result
ABORT
Cause
Solution
Error code: 1144

Test result
ABRT
Cause
Solution
Error code: 1187

Test result
ABORT
Cause
Solution
a. If this Error Type is present for BRI-SET only, release the station via release
station.
b. If this Error Type is present for BRI-PORT and BRI-SET, release the port with
c. If the error is present for BRI-BD, BRI-PORT, and BRI-SET, enter release port
d. If the error is present for both BRI-BD and BRI-PORT, enter release board
Note:
When you release the circuit pack, you release every port associated with it. Enter
busyout port location if ports still need to be busied out.
Primary Signaling Link Hardware Check (#636)
Error code: 2012

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Test result
PASS
The switch has successfully executed the BRI station audit test.
Primary Signaling Link Hardware Check (#636)

This test runs on ISDN-SGR (ISDN-PRI Signaling Group) on page 398.
For ATM-SGRP, 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) MO or the TN230X circuit pack.
For ISDN-SGR, the ISDN-PRI Signaling Group D-channel port depends on the health of the
TN464 UDS1 Interface circuit pack or DS1 Interface Media Module on which it resides. This test
will fail if there are problems with either the ISDN-PRI Primary D-channel port or the UDS1 circuit
pack or DS1 Media Module. If there are problems with the ISDN-PLK (ISDN-PRI signaling link
port) on page 395, investigate MG-DS1 (DS1 Interface Media Module) on page 436.
Related links
No error code
Test result
ABORT
Cause
Solution
Error code: 1700

Test result
ABORT
Cause
Rollabout video abort. The PRI terminal adapter associated with primary D-channel port is
detached from the circuit pack or media module. This is a normal abort when the rollabout video
feature is enabled.
Solution
To complete test on this port, either:
• Re-attach the disconnected PRI terminal adapter.
• Enter change ds1 location to disable rollabout video on the board, and set the Alarm
when PRI Endpoint Detached field to y.
Error code: 8
Test Result
FAIL
ATM-SGRP
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.
Remote Layer 3 Query (#637)
ISDN-SGR
There is a problem with the UDS1 TN464 UDS1 circuit pack or the DS1 Interface Media Module
or the ISDN-PRI Signaling channel (D-channel). No ISDN trunk or PRI endpoint calls can be made
until the problem is resolved.
Consult the procedures for the MG-DS1 (DS1 Interface Media Module) on page 436, and the
ISDN-PLK (ISDN-PRI signaling link port) on page 395.
Test result
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.
Error code 0
Test result
NO BOARD
Solution

This test will query the far-end switch or terminal adapter to determine whether 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. 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:
Enter status trunk grp#/mem# or status pri-endpoint to see the service state.
A PASS indicates only that a message was successfully sent to the far-end switch or terminal
adapter. The ISDN PRI Specification allows up to 2 minutes for a response. Tests #639 and #636
check the health of the D-channels and DS1 Interface Media Modules. As shown in Remote Layer
3 Query Test Diagram (#637), this test goes one step further by checking the communication
path from the processor, through the TDM/packet bus and through the Media Module, 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.
Related links
Error code: 2500 or none on page 679
No error code
Test result
ABORT
Cause
Solution
Error code: 1006

Test result
ABORT
Cause
There are no associated B-channels in an ISDN in-service or maintenance service state.
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).
This is a NORMAL ABORT.
Solution
1. Administer or release an ISDN trunk or PRI endpoint before retrying the test.
• For an ISDN trunk, use status trunk grp#/mem# to verify the ISDN trunk state.
• For a PRI endpoint, use status pri-endpoint extension.
2. Then, retry this test when at least one B-channel is in the in-service or maintenance states.
For systems not using country protocol 1 interfaces, there are no B-channels administered
in this signaling group.
Error code: 1019

Test result
ABORT
Cause
There is already a Remote Layer 3 Query in progress. This is a normal ABORT.
Solution
Wait two minutes, then follow the procedures for when this test passes.
Error code: 1113

Test result
ABORT
Cause
The signaling channel is down. Therefore, no messages can be sent to the far-end switch or
terminal adapter.
Solution
Examine the results of Tests #636 and the Secondary Signaling Link Hardware Check (#639) on
page 680 and follow recommendations provided there.
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 2500 or none

Test result
ABORT
Cause
Internal system error or administration problem.
Solution
1. Determine whether any B-channels are administered.
2. If not, then this is a normal ABORT since this test cannot run unless at least one B-channel
is administered.
If at least one B-channel is administered, there is an internal system error.
Test result
FAIL
Internal system error. See description of ABORT with Error Code 2500.
Test result
PASS
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 reply.
Solution
1. Check the Error Log for ISDN-PLK (ISDN-PRI Signaling Link Port) 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 or terminal adapter can exchange call control messages.
2. If there is still a problem with a particular ISDN trunk or PRI endpoint, busyout the trunk
and run the long test sequence, paying particular attention to the results of ISDN Test Call
Test (#258) on page 629.
Error code 0
Test result
NO BOARD
Solution
Secondary Signaling Link Hardware Check (#639)

Interface circuit pack or DS1 Interface Media Module on which it resides. This test will fail if there
are problems with the ISDN-PRI Secondary D-channel port or the UDS1 circuit pack or the DS1
Media Module. This test will abort if a Secondary D-channel is not administered for the signaling
group. If there are problems with the ISDN-PRI Secondary Signaling Channel port (ISDN-PLK),
also investigate the MG-DS1 (DS1 Interface Media Module) on page 436.
Secondary Signaling Link Hardware Check (#639)
Related links
No error code
Test result
ABORT
Cause
Solution
Error code: 1132

Test result
ABORT
Cause
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.
No action is necessary.
Error code: 4
Test Result
FAIL
Cause
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.
Solution
Display the Communication-Interface Links Form with display communication-interface 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.
Error code: 8
Test Result
FAIL
Cause
There is a problem with the TN464 UDS1 Interface circuit pack, the DS1 Interface Media Module,
or the ISDN-PRI Secondary Signaling Channel (D-channel). No ISDN trunk or PRI endpoint calls
can be made until the problem is resolved.
Solution
Consult the procedures for MG-DS1 (DS1 Interface Media Module) on page 436, and the ISDN-
PLK (ISDN-PRI signaling link port) on page 395.
Test result
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.
Error code: 0
Test result
NO BOARD
Solution
Signaling Link Board Check (#643)

This test checks the health of the critical DS1 Interface media module hardware components
required by the signaling link.
This test runs on ISDN-PLK (ISDN-PRI signaling link port) on page 395.
Related links
No error code
Test result
ABORT
Cause
Signaling Link Board Check (#643)
Solution
Error code: 1700

Test result
ABORT
Cause
Rollabout video abort. The PRI terminal adapter associated with primary D-channel port is
detached from the circuit pack or media module. This is a normal abort when the rollabout video
feature is enabled.
Solution
To complete test on this port:
• Re-attach the disconnected PRI terminal adapter.
• Enter change ds1 location to disable rollabout video on the board, and set the Alarm
when PRI Endpoint Detached field to y.
Error code: 8
Test Result
FAIL
Cause
The circuit pack is not in service.
Solution
1. Check the Hardware Error Log for entries logged against UDS1-BD.
2. Consult MG-DS1 (DS1 Interface Media Module) on page 436 for repair procedures.
Test result
PASS
The media module transporting the ISDN-PRI Signaling Link Port is in service.
Error code: Any

Test result
NO BOARD
Solution
Layer 2 Status Query Test (#647)

The Layer 2 Status Query Test checks the Layer 2 status of the ATM-SGRP or 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 (Tests #636 and #639), the ATM
Remote Layer 3 Query Test (test #1291), and the Remote Layer 3 Query Test (#637) will detect
most problems caused by hardware failures or incorrect administration.
Related links
Error code: 1132

Test result
ABORT
Cause
The port location for the primary D-channel is not known. This condition should not be possible
since an administered circuit pack or media module must be specified when a Signaling Group is
administered.
Solution
Error code: 1134

Test result
ABORT
Cause
The associated circuit pack or media module is not administered. This condition should not be
possible since an administered circuit pack or media module must be specified when a Signaling
Group is administered.
Solution
Layer 2 Status Query Test (#647)
Error code: 2500

Test result
ABORT
Cause
Solution
Error code: 1
Test result
FAIL
Cause
Layer 2 of the primary signaling channel is down:
Solution
1. Examine the results of the Primary Signaling Link Hardware Check (#636) on page 675,
and follow recommendations provided there.
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 the signaling channel has been busied out.
2. Verify that the Primary Signaling Channel (D-channel) at the far end has been
administered correctly.
3. Verify that the port used for the Primary D-channel has not been busied out at the far end.
Error code: 2
Test result
FAIL
Cause
Layer 2 of the secondary signaling channel is down.
Solution
1. Examine the results of the Secondary Signaling Link Hardware Check (#639) on page 680,
and follow recommendations provided there.
If Test #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.
2. Verify that the Secondary Signaling Channel (D-channel) at the far end has been
administered correctly.
3. Verify that the port used for the Secondary D-channel has not been busied out at the far
end.
Error code: 3
Test result
FAIL
Cause
Both the primary and secondary signaling channels are down.
Solution
1. Examine the results of the Primary Signaling Link Hardware Check (#636) on page 675
and Secondary Signaling Link Hardware Check (#639) on page 680 and follow the
recommended procedures if either test fails.
If tests #636 and #639 pass, 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.
2. Verify that the Primary and Secondary Signaling channels (D-channel) at the far end has
been administered correctly.
3. Verify that the port used for the Primary and Secondary D-channels has not been busied
out at the far end.
Test result
PASS
The Primary Signaling channel is up and, if administered, the Secondary channel is up.
Error code: Any

Test result
NO BOARD
Solution
Tie Trunk Dial Test (#747)

This test performs a dial tone/seizure test on a 2W LD tie trunk port. It seizes a trunk and
outpulses a pause digit. It aborts on ports administered as access endpoints.
This test runs on MG-ANA (Analog Media Module) on page 427.
Related links

No error code
Test result
ABORT
Cause
Solution
Error code: 1000

Test result
ABORT
Cause
call.
Solution
1. Enter display trunk-group xx to determine the trunk group/member number of the
port.
retesting.
3. If the port status is active but the port is idle (no calls), check the Error Log for Error Type
1025.
The port may be locked up. The far-end may not be releasing.
Error code: 1004

Test result
ABORT
Cause
Solution
1. Enter display trunk-group xx to determine the trunk group/member number of the
port.
retesting.
Error code: 1005

Test result
ABORT
Cause
This test is not valid for this trunk translation. Must be a wink-start or delay dial trunk and must
be outgoing or 2-way for this test to run. For the TN2140, the trunk must also be continuous-seize-
ack or discontinuous-seize-ack.
Solution
Check trunk translation.
If it is not a wink-start or delay dial trunk, this abort message should be ignored.
Error code: 1018

Test result
ABORT
Cause
Test disabled via administration.
Solution
1. Verify that the Maintenance Tests field on the Trunk Group screen is n.
2. To enable the test, enter change trunk-group x where x is the number of the trunk
group to be tested, and enter y in the Maintenance Tests field.
Error code: 1040

Test result
ABORT
Cause
This test is not executed on trunk ports which are administered as access endpoints.
Solution
1. Verify that this port is an access endpoint by entering display port.
2. If the port has been administered as an access endpoint, this test should abort and this
error can be ignored.
Error code: 2000

Test result
ABORT or FAIL
Cause
Seizure message is not received back within 10 seconds.
Solution
2. If the test continues to fail, check the far-end to ensure a translation match at both ends.
3. Check the facility.
Error code: 3
Test result
FAIL
Cause
No dial tone detected from the other end. (TN439 circuit packs only.)
Solution
2. If the test continues to fail, check the far-end PBX to ensure a translation match at both
ends.
3. Check the facility.
Test result
PASS
The relevant Seizure test passes. This port is functioning properly.
Solution
If users are reporting troubles, examine loop connections to the port, wiring, and stations.
Error code: 0
Test result
NO BOARD
Solution
SNI Destructive Facility Off-Board Test (#756)

The SNI runs a destructive looparound of the on- and off-board looparounds. This test returns the
result of the off-board looparound, while Test 757 returns the result of the on-board looparound.
For SNI-to-SNI fiber links, this test is run on both SNI circuit pack endpoints.
Analog Port Sanity Test (#963)

This test verifies that the port circuitry involved in the analog trunk testing on the Maintenance/
Test analog port is functioning properly.
This test will abort if an ATMS test call is in progress on the Maintenance/Test analog port when
the test is requested.
Related links
Error codes: 2000, 2100, 2500

Test result
ABORT
Cause
• Error 2100: System resources required to run this test are not available.
Solution
Error codes: 50
Test result
FAIL
VC DSP Port DSP Looparound Test (#1105)
Cause
The switch was unable to communicate with the port circuitry used for analog trunk testing.
Solution
1. Reset the media module.
2. Test the port again using test port location l.
3. If the test fails again, replace the media module.
Test result
PASS
The Maintenance/Test analog port analog trunk testing capability is operating correctly.

This test verifies the connectivity of a VC-DSPPT 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 media module.
Figure 11: VC DSP Port DSP Looparound Test

Related links

Test result
ABORT
Cause
• Error 1001: The port may be busy with a valid call.
Solution
Error code: 1002

Test result
ABORT
Cause
Solution
Error code: 1003

Test result
ABORT
Cause
Solution
tone receivers.
Error code: 1004

Test result
ABORT
Cause
The resource has been seized by a user for a valid call.
Solution
1. Enter status station for the station associated with this port to determine whether the
port is available for testing.
Error code: 2000

Test result
ABORT
Cause
Solution
1. If this result occurs repeatedly, reset the media module if the other ports are idle with
busyout port location, reset port location, and release port location.
2. If this result occurs again, replace the media module.

Test result
ABORT
Cause
Solution
Error codes: 0, 1
Test result
FAIL
Cause
The VC DSP Port DSP Loopback test failed.
Solution
Replace the media module.
Test result
PASS
The VC DSP Port DSP Loopback test passed004
VC Port Reset DSP Test (#1106)
VC Port Reset DSP Test (#1106)

This test resets the VC DSP port and the DSP associated with it. As part of the reset procedure,
the VC DSP port runs a series of self-tests on the hardware. If these self-tests fail, the test fails.
Otherwise, the test passes.
Before executing the test, the VC DSP port must be busied out by entering busyout port
location. After the completion of the test, the VC DSP port must be released by entering
release port location.
Related links

Test result
ABORT
Cause
Solution
Error 1015
Test result
ABORT
Cause
The VC DSP port is not busied out.
Solution
Busyout the VC DSP port by entering busyout port location, then retry the test.
Error code: 2000

Test result
ABORT
Cause
Solution
Error code: 2012

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Test result
FAIL
The reset of the VC DSP port was unsuccessful.
Solution
Replace media module.
Test result
PASS
The VC DSP port was successfully reset.
Solution
Release the VC DSP port by entering release port location.
TSI Looparound Test (#1108)
TSI Looparound Test (#1108)

During this test, the MMI’s Time Slot Interchanger (TSI) 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.
This test runs on Multimedia Interface media module.
Related links
No error code
Test result
ABORT
Cause
Internal system error. This is an abnormal abort.
Solution
Error code: 1002

Test result
ABORT
Cause
Solution
Error code: 1003

Test result
ABORT
Cause
Solution
tone receivers.
Error code: 2000

Test result
ABORT
Cause
Solution
1. If this result occurs repeatedly, attempt to reset the media module if the other ports are idle.
2. Rerun the test.
3. If this result occurs again, replace the media module.
Error code: 2012

Test result
ABORT
Cause
Internal system error. This is an abnormal abort.
Solution
Error code: 2100

Test result
ABORT
Cause
Digital Terminal Remote Looparound Test (#1201)
Solution
Test result
FAIL
The TSI was found to be transmitting in error, causing noisy and unreliable connections.
Solution
Replace circuit pack.
Test result
PASS
The TSI is correctly using its allocated time slots.

This test checks the connection between the server and the digital terminal. It verifies the ability
of the terminal and the associated port to send and receive data. This test is based on procedure
622 to isolate digital terminal problems.
This test runs on DIG-LINE (Digital Line) on page 349.
Related links
No error code
Test result
ABORT
Cause
Solution

Test result
ABORT
Cause
Solution
of the port.
port.
Error code: 1001

Test result
ABORT
Cause
Solution
If the port status is idle, retry the command at 1-minute intervals up to 5 times.
Error code: 1002

Test result
ABORT
Cause
Solution
Error code: 1003

Test result
ABORT
Cause
Solution
tone receivers.
Error code: 1004

Test result
ABORT
Cause
The port has been seized by a user for a valid call.
Solution
of the port.
port.
If the port is in use, wait until it is idle before resetting. Attendants are always in use
Error code: 1005

Test result
ABORT
Cause
The installed circuit pack does not support this operation. Ignore this error.
Error code: 1412

Test result
ABORT
Cause
Error 1015
Test result
ABORT
Cause
The station is not busied out.
Solution
Enter busyout station and repeat the test.
Error code: 2000

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
1. Make sure the terminal is connected and repeat the test.
2. If the test fails, replace the terminal and repeat the test.
DS1 Board Loopback Test (#1209)
Error codes: 14, 16

Test result
FAIL
• Error 14: The primary channel is not operating properly.

• Error 16: The secondary channel is not operating properly.
User impact may range from noticing nothing to not being able to use the port.
Solution
1. Check the results of the Local Loop Test (#13).
If that test fails, suspect the Digital Line media module.
2. Run test board location on the Digital Line media module.
3. If the tests pass, replace the terminal.
4. If component replacement does not change the results, then:
Run media module tests to check the tone generator circuit and the Tone Detector
circuit using test board location.
Test result
PASS
The test passed. All channels are transmitting properly.
Solution
1. To verify that this is not an intermittent problem, repeat this test up to ten times.
2. If problems persist (noisy connections for voice, corrupted data transfer for data), examine
the station, connections, and wiring.

The DS1 BLB (Board Loopback) Test causes a loopback at the DS1 board edge and tests DS1
board internal circuitry.
This test is destructive and can only be initiated by entering the command test ds1-loop
location ds1/csu-loopback-test.
All trunks or ports on the DS1 Interface media module must be busied out using busyout board
before running the BLB test.
When the BLB test is initiated, maintenance software sends a message to the DS1 Interface
media module. The board sets up the BLB loopback, transmits a test pattern, and verifies that the
pattern is received unaltered through the loopback. If the transmitted and received patterns are
different, the test fails.
When the test is complete, enter release board to restore all trunks or ports on the DS1
Interface media module to the in-service state.
Related links
No error code
Test result
ABORT
Cause
Solution
Retry test ds1-loop location ds1/csu-loopback-tests at 1-minute intervals up to 5
times.
Error code: 1005

Test result
ABORT
Cause
The DS1 Board Loopback test cannot be executed in the current configuration.
Solution
1. To run this test, the DS1 must be administered for 24-channel operation.
2. The Bit Rate field on the DS1 media module administration screen must be set to 1.544
for 24-channel operation.
Error code: 1015

Test result
ABORT
Cause
Ports on the DS1 Interface media module have not been busied out.
Solution
1. Enter busyout board location to put all trunks or ports of the DS1 Interface media
module into the out-of-service state.
Error code: 1412

Test result
ABORT
Cause
Error code: 1950

Test result
ABORT
Cause
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 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.
Solution
If a loopback/span test is already active, that test must be deactivated using test ds1-loop
location end-loopback/span-test to run this test.
Error code: 2000

Test result
ABORT
Cause
Solution
Check for board hyperactivity.
See Hyperactive DS1 Media Module on page 774.
Error code: 2100

Test result
ABORT
Cause
Solution
Test result
FAIL
Cause
DS1 Interface media module failed the DS1 Board Loopback test.
Solution
1. Enter test ds1-loop location ds1/csu-loopback-tests.
2. If the BLB test continues to fail, replace the DS1 media module.
Test result
PASS
The BLB test executed successfully. The test pattern was transmitted and received successfully
up to the DS1 board edge.
Solution
Enter release board location to restore all trunks and ports.
Error code: 0
Test result
NO BOARD
Solution
CSU Equipment Loopback Test (#1210)

For documentation purposes, the term DS1 applies to the DS1 Interface media modules.
The CSU ELB (Equipment Loopback) test causes a loopback at the near-edge of the local 120A
CSU module or T1 sync splitter, and tests the connection from the 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.544-Mbps DS1 media module on the back of the port carrier.
The test is destructive and can only be initiated by entering the command test ds1-loop
location ds1/csu-loopback-tests.
Enter busyout board to busy out all trunks or ports on the DS1 Interface media module before
running the ELB test.
When the ELB test is initiated, maintenance software sends a message to the DS1 Interface
media module to start the test. The board sets up the ELB loopback, transmits a test pattern, and
verifies that the pattern is received unaltered through the loopback. If the transmitted and received
pattern is different, the test fails.
The DS1 media module hardware applies a DC current while the test is running to detect any
broken wires that may not be detected by the loopback pattern.
When the test is complete, enter release board to restore all trunks or ports on the DS1
Related links
No error code
Test result
ABORT
Cause
Solution
Enter test ds1-loop location ds1/csu-loopback-tests at 1-minute intervals up to 5
times.
Error code: 1005

Test result
ABORT
Cause
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 screen must be set to
integrated and the Bit Rate field must be set to 1.544 (for 24-channel operation).
Solution
1. Enter change ds1 location and set the Near-End CSU Type field on the DS1 circuit
pack administration screen to integrated, and/or set the Bit Rate field to 1.544 if the board
is to be used in a 24-channel configuration.
2. Retry test ds1-loop location ds1/ csu-loopback-tests.
Error code: 1015

Test result
ABORT
Cause
Solution
Error code: 1412

Test result
ABORT
Cause
Error code: 1950

Test result
ABORT
Cause
Solution
If a loopback/span test is already active, that test must be deactivated using test ds1-loop
Error code: 1951

Test result
ABORT
Cause
The CSU Equipment Loopback test could not be executed because the 120A CSU module/T1
sync splitter was not physically installed.
Solution
Physically connect the 120A CSU module/T1 sync splitter to the DS1 board on the back of the port
carrier.
Error code: 2000

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Test result
FAIL
Cause
Solution
1. Enter test ds1-loop location ds1/csu-loopback-tests.
If the ELB test continues to fail, either the DS1 board, the CSU module/T1 sync splitter,
or the I/O cable between the backplane and the 120A CSU module or the 401A T1 sync
splitter (or any combination thereof) has failed. Attempt to isolate the problem to one of
these areas.
2. Replace the CSU module/T1 sync splitter, and run test ds1-loop location ds1/
csu-loopback-tests again.
3. If the ELB test continues to fail, replace the board and run test ds1-loop location
ds1/csu-loopback-tests again.
If the ELB test continues to fail, the problem could be in the I/O cable between the
backplane and the 120A CSU module or the 401A T1 sync splitter.
Test result
PASS
The ELB test executed successfully. The test pattern was transmitted and received successfully
over the connection from the DS1 board to the near-edge of the 120A CSU module/T1 sync
splitter.
Solution
Enter release board location to release all trunks and ports.
Error code: 0
Test result
NO BOARD
Solution
CSU Repeater Loopback Test (#1211)

The CSU RLB (Repeater Loopback) test causes a loopback at the far-edge of the local 120A CSU
module or T1 sync splitter, and tests the connection from the DS1 board to and including the CSU
module/T1 sync splitter circuitry. The test runs only if the 120A CSU module/T1 sync splitter is
present, administered, and connected to a 1.544-Mbps DS1 media module on the back of the port
carrier.
The test is destructive and can only be initiated by entering the command test ds1-loop
location ds1/csu-loopback-tests.
running the RLB test.
When the RLB test is initiated, maintenance software sends a message to the DS1 Interface
media module to start the test. The board sets up the RLB loopback, transmits a test pattern, and
verifies that the pattern is received unaltered through the loopback. If the transmitted and received
pattern is different, the test fails.
The DS1 media module hardware applies a DC current while the test is running to detect any
broken wires that may not be detected by the loopback pattern.
When the test is complete, use release board to restore all trunks or ports on the DS1
Related links
No error code
Test result
ABORT
Cause
Solution
Enter test ds1-loop location ds1/csu-loopback-tests at 1-minute intervals up to 5
times.
Error code: 1005

Test result
ABORT
Cause
CCSU Repeater Loopback test cannot be executed in the current configuration.
Solution
1. Enter change ds1 location and set the Near-End CSU Type field on the DS1 circuit
pack administration screen to Integrated, and/or set the Bit Rate field to 1.544 if the board
is to be used in a 24-channel configuration.
2. Enter test ds1-loop location ds1/ csu-loopback-tests.
Error code: 1015

Test result
ABORT
Cause
Solution
Error code: 1412

Test result
ABORT
Cause
Error code: 1950

Test result
ABORT
Cause
Solution
If a loopback/span test is already active, that test must be deactivated via test ds1-loop
Error code: 1951

Test result
ABORT
Cause
The CSU Equipment Loopback test could not be executed because the 120A CSU module/T1
sync splitter was not physically installed.
Solution
Physically connect the 120A CSU module/T1 sync splitter to the TN767E board on the back of the
port carrier.
Error code: 2000

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Test result
FAIL
Cause
Solution
1. Retry test ds1-loop location ds1/csu-loopback-tests.
2. If the RLB test continues to fail, and the CSU Equipment Loopback test (#1210) passed,
replace the CSU module/T1 sync splitter.
Test result
PASS
The RLB test executed successfully. The test pattern was transmitted and received successfully
over the connection from the DS1 board to the far-edge of the 120A CSU module/T1 sync splitter.
Solution
Enter release board location to release the trunks and ports.
Error code: 0
Test result
NO BOARD
Solution
CPE Loopback Jack Test (#1212)

The CPE Loopback Jack (CLJ-LB) test causes a loopback at the CPE loopback jack and tests the
building wiring connection between the DS1 board and the CPE loopback jack.
The test is highly destructive and can only be initiated by entering the command test ds1-loop
location cpe-loopback-jack-test-begin [number-of-bits bit-pattern]. Enter a
loopback activation code on the command line or use the default code (0x47F).
running the CPE Loopback Jack test.
Use busyout board to busy out all trunks or ports on the DS1 Interface media module before
The CPE Loopback Jack test has the DS1 Interface media module 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 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 appears in the error log as Error Type 3900. Several
distinct aux values give information on the status of the test.
Use list measurements ds1 summary to show 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 passed through the loopback cleanly, the number of bit errors should be
very low. The command also shows 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).
Use test ds1-loop location end-loopback/span-test to end the test.
Use release board location to restore each trunk or port on the DS1 Interface board to the
in-service state.
Related links
No error code
Test result
ABORT
Cause
Solution
Enter test ds1-loop location cpe-loopback-jack-test-begin at 1-minute intervals
up to 5 times.
Error code: 1005

Test result
ABORT
Cause
CCSU Repeater Loopback test cannot be executed in the current configuration.
Solution
1. To run this test, the DS1 board must be administered for 24-channel operation.
Error code: 1015

Test result
ABORT
Cause
Ports on the DS1 Interface media module have not been busied out to out-of-service.
Solution
Error code: 1950

Test result
ABORT
Cause
Solution
Error code: 2000

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 2
Test result
FAIL
Cause
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.
Solution
1. Enter test ds1-loop location cpe-loopback-jack-test-begin.
If the test continues to fail, the problem could be with the DS1 board, the CPE loopback
jack equipment, or somewhere between.
2. Run test ds1-loop location ds1/csu-loopback-tests to determine if the
loopback tests that are closer to the DS1 board are successful.
3. If any of the tests fail, follow the maintenance strategy that is associated with the failing
test.
Error code: 3
Test result
FAIL
Cause
The CPE Loopback Jack test was not set up properly. The framed 3-in-24 test pattern, generated
by the DS1 Interface media module and looped back through the CPE loopback jack, could not be
detected properly by the DS1 media module.
Solution
1. Enter test ds1-loop location cpe-loopback-jack-test-begin.
If the test continues to fail, the problem could be with the DS1 board, the CPE loopback
jack equipment, or somewhere between.
2. Run test ds1-loop location ds1/csu-loopback-tests to see if the loopback

tests that are closer to the DS1 board are successful.
3. If any of the tests fail, follow the maintenance strategy that is associated with those.
Test result
PASS
The CPE Loopback Jack test has successfully began executing. The test runs until test ds1-
loop location end-loopback/span-test is entered.
Solution
Enter release board location to release the trunks or ports.
Error code: 0
Test result
NO BOARD
Solution
Far CSU Loopback Test (#1213)

The Far CSU Loopback (R-LLB) test causes a loopback at the far-end CSU, and tests all circuitry
and facilities from the local DS1 board to the far-end CSU.
location far-csu-loopback-test-begin.
Use busyout board to busy out all trunks or ports on the DS1 Interface media module before
running the Far CSU Loopback test.
If the DS1 is administered for ami-zcs line coding and the far-end CSU is not a 120A CSU module
or a 401A T1 sync splitter, density protection on the CSU must be disabled 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 DS1 Interface media module 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 appears in the error log as Error Type 3901. Several aux
values give information on the status of the test.
Use list measurements ds1 summary to show the length of time the test has been running
field). If the test pattern is passed through the loopback cleanly, the number of bit errors should be
very low. The command also shows 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).
Use test ds1-loop location end-loopback/span-test to end the test.
Use release board location to restore each trunk or port on the DS1 Interface board to the
in-service state.
Related links
Error code: 2, 3 on page 721
No error code
Test result
ABORT
Cause
Solution
Enter test ds1-loop location far-csu-loopback-test-begin at 1-minute intervals up
to 5 times.
Error code: 1005

Test result
ABORT
Cause
Far CSU Loopback test cannot be executed in the current configuration.
Solution
Error code: 1015

Test result
ABORT
Cause
Ports on the DS1 Interface media module have not been busied out to out-of-service.
Solution
Error code: 1950

Test result
ABORT
Cause
Solution
Error code: 2000

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 2, 3
Test result
FAIL
Cause
• Error code 2: 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.
• Error code 3: 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.
Solution
1. Enter test ds1-loop location far—csu-loopback-test-begin.
If the Far CSU Loopback test continues to fail with this error code, the problem could be
with the DS1 board, the far-end CSU equipment, or somewhere in between.
2. Run test ds1-loop location cpe-loopback-jack-test-begin to see if the
CPE Loopback Jack test that is closer to the DS1 board is successful.
3. If a CPE loopback jack device is not being used, run test ds1-loop location ds1/
csu-loopback-tests to see if the closer loopback tests succeed.
4. If the closer loopback test fails, follow the maintenance strategy associated with that
loopback.
Test result
PASS
The Far CSU Loopback test has successfully began executing. The test runs until test ds1-
loop location end-loopback/span-test is entered.
Solution
Error code: 0
Test result
NO BOARD
Solution
One-Way Span Test (#1214)

The One-Way Span test allows 1-way span testing to and from remote test equipment or another
Communication Manager solution. This tests all circuitry and facilities from the local DS1 board to
the remote test equipment or other Communication Manager solution.
location one-way-span-test-begin.
running the One-Way Span test.
The One-Way Span test has the DS1 Interface circuit pack transmit a framed 3-in-24 test pattern
and attempts to receive and verify the pattern. If the DS1 board receives a framed 3-in-24 test
pattern sent from another Communication Manager system or test equipment at the far end of the
DS1, it begins counting bit errors within the received pattern.
Note:
If a DS1 circuit pack and a DS1 Interface media module are connected, the test will fail
because the media module does not frame-align its test pattern.
The status of the One-Way Span test appears in the error log as Error Type 3902. Several aux
values give information on the status of the test.
Enter list measurements ds1 summary to see the length of time the test has been running
field). If the test pattern is sent cleanly over the span from the far end, the number of bit errors
should be very low. The Test Duration field is 0 until the test pattern is received from the far end.
Upon receiving the test pattern, the board begins calculating the test duration and number of bit
errors. The command also shows 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)
One-Way Span Test (#1214)
Enter test ds1-loop location end-loopback/span-test or release board to end

the test. Enter release board to restore all trunks or ports on the DS1 Interface media module
to the in-service state.
Related links
No error code
Test result
ABORT
Cause
Solution
Retry test ds1-loop location one-way-span-test-begin at 1-minute intervals up to 5
times.
Error code: 1005

Test result
ABORT
Cause
One-Way Span test cannot be executed in the current configuration.
Solution
Error code: 1015

Test result
ABORT
Cause
Solution
Error code: 1950

Test result
ABORT
Cause
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.
Solution
Error code: 2000

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Inject Single Bit Error Test (#1215)
Test result
FAIL
Cause
The test was run between a DS1 circuit pack and a DS1 media module, which generates
incompatible patterns.
Test result
PASS
The One-Way Span test has successfully began transmitting a framed 3-in-24 test pattern. The
test will continue to run until test ds1-loop location end-loopback/span-test is
entered.
Solution
Error code: 0
Test result
NO BOARD
Solution
Inject Single Bit Error Test (#1215)

The Inject Single Bit Error test causes a single bit error to be sent within an active framed 3-in-24
test pattern.
location inject-single-bit-error. An attempt to use this command is 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 ds1 media module.
running the Inject Single Bit Error test.
Enter list measurements ds1 summary to show 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.
Enter release board to restore all trunks or ports on the DS1 Interface media module to the
in-service state.
Related links
No error code
Test result
ABORT
Cause
Solution
Enter test ds1-loop location inject-single-bit-error at 1-minute intervals up to 5
times.
Error code: 1015

Test result
ABORT
Cause
Solution
Error code: 2000

Test result
ABORT
Cause
Solution
End Loopback/Span Test (#1216)
Error code: 2100

Test result
ABORT
Cause
Solution
Test result
PASS
A single bit error has been successfully injected into an active framed 3-in-24 test pattern.
Solution
Error code: 0
Test result
NO BOARD
Solution

The End Loopback/Span test deactivates an active loopback or span test on a DS1 media
module. Bit error counting against the received test pattern stream halts, and sending of the
framed 3-in-24 test pattern ceases. If either the CPE loopback jack or the far-end CSU is looped,
the loopback deactivate code is sent. If the loopback could not be deactivated, the test will FAIL
and a MINOR alarm is noted in the alarm log until the loopback is cleared.
location end-loopback/span-test. Since only one of these three different long-duration
loopback/span tests can be active at a time, the DS1 media module knows which loopback/span
test to halt.
running this End Loopback/Span test.
Enter list measurements ds1 summary to show the length of time the test ran (Test
Duration field) and number of bit errors detected (Loopback/Span Test Bit-Error Count field).
Enter release board to restore all trunks or ports on the DS1 Interface media module to the
in-service state.
Related links
No error code
Test result
ABORT
Cause
Solution
Enter test ds1-loop location end-loopback/span-test at 1-minute intervals up to 5
times.
Error code: 1005

Test result
ABORT
Cause
End Loopback/Span test cannot be executed in the current configuration.
Solution
Error code: 1015

Test result
ABORT
Cause
Solution
Error code: 2000

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Error code 1313

Test result
FAIL
Cause
The DS1 circuit pack could not deactivate the loopback through the Customer loopback jack.
Solution
Retry test ds1-loop location end-loopback/ span-test at 1-minute intervals up to 5
times.
Error code 1314

Test result
FAIL
Cause
The DS1 media module could not deactivate the loopback through the far-end CSU.
Solution
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 test ds1-loop location end-loopback/ span-test at 1-minute intervals
up to 5 times.
Test result
PASS
The active long-duration loopback or span test on the DS1 media module was successfully
deactivated.
Solution
Error code: 0
Test result
NO BOARD
Solution
ICSU Status LEDs Test (#1227)

The DS1 media module has four status LEDs on the faceplate in addition to the three standard
faceplate LEDs. These four status LEDs are associated with the 120A channel Service Unit (CSU)
Module that can be connected to the DS1 board via the I/O connector panel on the back of the
port carrier.
ICSU Status LEDs Test (#1227)
This test is a visual test. It lights the four status LEDs red for 5 seconds, green for 5 seconds, and
yellow for 5 seconds. It then turns the LEDs off and returns control of the status LEDs to the media
module.
The DS1 media module, combined with the 120A CSU module or the 401A T1 sync splitter, forms
an Integrated CSU (ICSU).
If the 120A CSU module/T1 sync splitter is not installed, the status LEDs are always off and this
test aborts.
Related links
No error code
Test result
ABORT
Cause
Solution
Error code: 1005

Test result
ABORT
Cause
The ICSU Status LEDs test cannot be executed for the current configuration. The test applies only
to TN767E or later DS1 media module and TN464F or later UDS1 media module administered for
24-channel (1.544-Mbps) operation.
Solution
If the media module is of the correct type, retry the command.
Error code: 1412

Test result
ABORT
Cause
Error code: 1951

Test result
ABORT
Cause
The ICSU Status LEDs Test cannot be executed because a 120A CSU module or a 401A T1 sync
splitter is not physically installed.
Solution
If using a 120A CSU module/T1 sync splitter, physically connect it to the TN767 or TN464 board
on the back of the port carrier. Otherwise, ignore this abort.
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 2500

Test result
ABORT
Cause
Solution
Test result
PASS
Trunk-side Layer 1 Query Test (#1242)
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.
Solution
1. 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.
2. If the LEDs behave differently, replace the circuit pack at the customer’s convenience.
Error code: 0
Test result
NO BOARD
Solution

This test determines the state of the transmission facility of a BRI port at the Layer 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 but cannot transit to the Activated state.
The Deactivated state indicates a problem with the TBRI-BD circuit pack. When in this state, the
Level 1 interface is not active, an idle signal is transmitted to the channels, or that Layer 1 was
deactivated by the switch. When a 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 location request.
Related links
Error code: 1187

Test result
ABORT
Cause
The board or port may be busied out.
Solution
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, release the port with release port
• If the error is present for both TBRI-BD and TBRI-PT, release the board with release
board location and run the test again.
Caution:
When you release a board, you release every port associated with it. If certain ports
still need to be busied out, use busyout port location to busy them out.
2. Make sure the endpoint is connected.
Error code: 2000

Test result
ABORT
Cause
Solution
2. If the test aborts repeatedly up to 5 times, reset the circuit pack.
3. Rerun the test.
4. If the test aborts again with this error code, replace the circuit pack.

Test result
ABORT
Cause
Solution
Error code: 1
Test result
FAIL
Cause
Received a status of Level 1 Pending Activation. U interface is down, indicating a problem with a
connection between the switch and the NT1.
Solution
1. Verify that the connections between the switch and the NT1 are good.
2. Verify that the NT1 has power.
3. Enter test port location and review the results of the Level 1 Status Query Test
#1242 to verify the repair. If this test still fails, proceed to Step 4.
4. Follow the manufacturers repair procedures for the NT1.
5. Then enter test port location and review the results of the Level 1 Status Query test
to verify repair.
Error code: 2
Test result
FAIL
Cause
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).
Solution
1. Enter test port location and review the results of the Level 1 Status Query test to
verify the repair. If this test still fails, proceed to Step 2.
2. Follow the manufacturer-recommended repair procedures for the NT1.
3. Then enter test port location and review the results of the Level 1 Status Query test
to verify repair.
Error code: 3
Test result
FAIL
Cause
Received a status of Level 1 Deactivated. The port is out-of-service.
Solution
1. Run status bri-port location to verify that the service state of the port is out-of-
service.
2. If the service state of the port is not out-of-service, escalate the problem to the next tier.
Otherwise, proceed to Step 3.
3. If the port has been placed out-of-service with busyout port location, try releasing the port
by entering release port location.
4. Then run test port location long and review the results of Trunk-side Layer 1
Query Test (#1242). If this test still fails, proceed to Step 5.
5. After entering test port location long, review the results of every test.
6. Follow the repair procedures for any test that fails.
7. Verify repair of the problem by entering test port location and by determining that
the Trunk-side Layer 1 Query test passes.
8. If the test continues to fail for this reason, escalate the problem to the next tier.
Error code: 4
Test result
FAIL
Cause
Received a status of Level 1 Pending Activation. The NT1 has a loss of power indicating a
problem with the NT1.
Solution
1. Follow the manufacturer-recommended repair procedures for the NT1.
2. Enter test port location and review the results of the Trunk-side Layer 1 Query Test
(#1242) to verify the repair.
Test result
PASS
Level 1 is activated or software has taken the port out of service.
Ethernet Local Looparound Test (#1278)
Ethernet Local Looparound Test (#1278)

This test checks the circuitry in the data path for an Ethernet call from the on-board processor to
the Ethernet Transceiver. This test fails if the received data does not match the transmitted data.
This test runs on ETH-PT (Control LAN Ethernet) on page 371.
Related links
Error code: 1000

Test result
ABORT
Cause
The port is in use.
Solution
1. Determine status of port using status clan-port location.
2. Retry the command when the port is idle. You can force the port to the idle state by
executing busyout port location.
Note:
The busyout port command is destructive, causing every call and link associated with
the port to be torn down.
Error code: 2000

Test result
ABORT
Cause
Solution
2. If the problem persists, reset the circuit pack.

Test result
ABORT
Cause
Solution
2. If the problem persists, escalate the problem.
Error code: 1
Test result
FAIL
Cause
Data received did not match the data transmitted.
Solution
1. Reset the circuit pack.
2. Retest the circuit pack with test board location long.
Test result
PASS
The circuitry is functioning properly.
ASAI Link Status Test (#1365)

This tests queries the system for the state of the TCP Tunnel Connection and the ASAI TCP/IP
link. If both the TCP Tunnel Connection and the ASAI TCP/IP Link are in the "established" state,
the test passes. The test fails otherwise. This test is run on ADJ-IP (ASAI Adjunct TCP/IP Link) on
page 296.
Related links
ASAI Link Status Test (#1365)
Error code: 2500

Test result
ABORT
Cause
Solution
Error code: 1
Test result
FAIL
Cause
The ASAI Adjunct TCP/IP Link is down. The TCP Tunnel Connection is established but the ASAI
TCP/IP Link is not established.
Solution
1. Use the ping command with the IP address for the Remote Node as specified on the
ip-services form.
2. If no response is received, check the entry for the local node on the ip-services form.
3. If the entry is clanX, where X is the board number, refer to the maintenance procedures for
CLAN-BD (Control LAN Circuit Pack) on page 333 to clear the problem.
Error code: 4
Test result
FAIL
Cause
The ASAI Adjunct Link is down. The ASAI Adjunct Link is established but the TCP Tunnel
Connection is not established.
Solution
1. Check the entry for the local node on the ip-services form. If the entry is clanX, where X is
the board number, refer to the maintenance procedures for CLAN-BD (Control LAN Circuit
Pack) on page 333 to clear the problem.
Test result
PASS
The ASAI Adjunct TCP/IP Link is up. The ASAI TCP/IP Link and the TCP Tunnel Connection are
both “established”.
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 to receive service from the system.
Registration is initiated when the endpoint user attempts to login using the Avaya registration
software application running on the endpoint personal computer. The user must provide a valid
extension and security code. The registration messages are sent to the IP address of the PROCR
Ethernet port.
A registered extension has a port type of SNNNNN, where N is a digit from 0–9. A non-registered
extension has a port type of X.
This test is run on DIG-IP-S (Digital IP Station) on page 346 and H323-STN (H.323 IP Station) on
page 389.
Related links
Error code: 1427

Test result
ABORT
Cause
This test does not apply to OPTIM stations. This error can be ignored.
Test result
FAIL
Cause
The endpoint is not successfully registered.
Solution
1. Verify that the user is entering the:
• correct extension and security code
Signaling Path PING Test (#1373)
• correct IP address of the PROCR

2. Verify that the extension has been enabled for IP Softphone operation.
3. If several endpoints cannot register, investigate any errors of the PROCR port.
4. Examine the Ethernet cabling from the endpoint personal computer to the Ethernet hub.
Test result
PASS
The endpoint is successfully registered and continues to respond to registration handshaking.
Signaling Path PING Test (#1373)

Run the Signaling Path PING Test to check if the Digital IP and H.323 IP endpoints connect to the
PROCR. Multiple failures of this test can take the IP Station out of service.
Signaling Path PING Test checks the circuitry in the data path of a peer-to-peer connection. When
you run this test, the PROCR pings the endpoint. If the endpoint sends a response, the test
passes.
Related links
Error code: 1003

Test result
FAIL
Cause
The system failed to ping the registered endpoint.
Solution
1. Run the command three times at 1-minute intervals.
2. Check the PROCR Ethernet port for errors.
Error code: 1007

Test result
FAIL
Cause
The system cannot ping the registered endpoint.
Solution
1. Verify that at least one destination reachable through this port. PING this destination (ping
ip-address xxx.xxx.xxx.xxx).
If the PING to any destination is successful through this port, the link is up.
2. If the PING to every destination fails, test the PROCR port using test port location.
3. If only this station cannot be pinged:
• Make sure the personal computer is up.
• Make sure the personal computer has a network connection (Ethernet or dial-up).
• Check the Ethernet cabling.
Test result
PASS
The system can successfully send IP packets to the registered endpoint from the PROCR.
Error code: 1018

Test result
ABORT
Cause
The administrator has disabled this test by setting the Maintenance Tests field on the Stations
screen to n.
Solution
1. On the Stations screen, set the Maintenance Tests field to y.
2. Run the command five times at 1-minute intervals.
Error code: 1412

Test result
ABORT
Cause
C-LAN Ethernet Port Status Test (#1386)
Error code: 1427

Test result
ABORT
Cause
The test does not apply to OPTIM stations. Ignore the error message.
Error code: 2100

Test result
ABORT
Cause
The system could not locate the resources to run this test.
Solution
Run the command three times at 1-minute intervals.
Error code: 2500

Test result
ABORT
Cause
The test resulted in an internal system error.
Solution
Run the command three times at 1-minute intervals.

This test checks the status of the PROCR port that is the near-end gatekeeper of this signaling
group. If the PROCR port is in service, the test passes. If the port is out of service, the test fails.
This test runs on H323-SGR (H.323 Signaling Group) on page 384 and SIP-SGRP (SIP Signaling
Group) on page 492.
Note:
Failure of this test will put the SIG-GRP in the OOS state.
Related links

Error code: 1005

Test result
ABORT
Cause
Ethernet Link is not in service.
The object is not in the right configuration to run this test. Either the Compact Flash has not been
turned on in the change gateway form, or the announcements have not been enabled, or the
gateway link is down.
Error code: 2000

Test result
ABORT
Cause
Response to the test was not received from the MG announcement media module within the
allowable time period.
If this result occurs repeatedly, there is not much that can be physically done as this module is a
part of the mother board.
Error code: 2012

Test result
ABORT
Cause
The System Call failed.
Solution
The command can be tried again. However, any continuous failure with this error code should be
escalated.
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 2500

Test result
ABORT
Cause
Solution
Error code: 1
Test result
FAIL
Cause
The gateway announcement module is experiencing problems with the Compact Flash. The
Compact Flash is either not inserted, or is unrecognizable.
Error code: 2
Test result
FAIL
Cause
Compact Flash does not have enough memory to support the announcements on the MG
announcement module
Error code: 4
Test result
FAIL
Cause
available RAM is not sufficient to support the Compact Flash.
Error codes: 3, 5, 6, 7
Test result
No result
Cause
The gateway announcement module is experiencing problems with the Compact Flash. Any of the
errors—3, 5, 6 and, 7—indicates multiple errors related to the Compact Flash.
For example, 3 is a combination of failures 1 and 2.
Test result
PASS
The gateway announcement module has passed all tests. Alarms and errors are cleared if they
were previously set.
Signaling Group Ping Test (#1387)

This test checks the circuitry involved in the data path of a peer-to-peer IP layer connection. It is
only run for those signaling groups that have an administered far-end IP address. If the H.323 or
SIP signaling group does not have an administered far-end IP address, the test will abort.
The test determines the local PROCR through which the signaling originates, and the far-end
terminating IP address. It then requests the local PROCR 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 will cause this signaling group’s associated H.323 or SIP B-
channels to be taken out of service (OOSFE). This will allow incoming calls to be made when
the far-end comes up before the near end has detected it. The signaling group will be left in
service, but in the far end bypass state.
If the PING is successful, the 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 will not take the signaling group out of service.
The standard PING command can be executed using the PROCR board’s address and far-end IP
address from the signaling group screen to see the actual round-trip delay.
Group) on page 492.
Related links
Error codes: None, 1, 2 on page 747
Error codes: None, 1, 2

Test result
ABORT
Cause
Internal Error.
Solution
Error code: 7
Test result
ABORT
Cause
Destination unreachable.
Solution
1. Verify that the PROCR has been administered with an IP-Route that enables the PROCR
to reach the far-end IP address.
2. Once verified, enter test sig-group grp# and verify that the Signaling Group Ping test
(#1387) passes.
Error code: 1005

Test result
ABORT
Cause
Configuration for this test is incorrect.
Solution
1. If Layer 3 or LRQ is enabled for this H.323/SIP signaling group, this error can be ignored.
There is no need to run the ping test.
2. Verify that the link is in service with status port or status link.
3. Verify that the routing table has destinations that are reachable through this port.
4. Repeat the test.
5. If the test aborts with Error Code 7 after step 2 is verified, escalate the problem.

Test result
ABORT
Cause
Link is not in service.
Solution
1. Check if the link is in service or not.
2. If the link is not in service, release the link using release link or release port, and
repeat the test.
3. If the test continues to abort after the link has been released, escalate the problem.
Error code: 2000

Test result
ABORT
Cause
Solution
1. If this result occurs repeatedly, attempt to reset the circuit pack if the other ports on the
board are idle (amber LED is off).
2. Rerun the test.
Error codes: 2012, 2100, 2500

Test result
ABORT
Solution

Test result
ABORT
Cause
• Error 2800: No PROCR in the same region. Could not find PROCR with this IP address.
• Error 2801: No IP address defined.
Solution
Verify translations and retest.
Error code: 2802

Test result
ABORT
Cause
Different IP address pinged than software had allocated for the test.
Solution

Test result
FAIL
Cause
Ping to the destination failed through this port because the destination is down.
Solution
1. Verify that at least one destination reachable through this port is “up”.
2. Once verified, enter test signaling—group grp# to verify that the Signaling Group
Ping test (#1387) passes.
Error code: Any

Test result
PASS
PING through this port was successful.
VoIP Status Test (#1392)

This test determines if at least one media processor port is in service and serves the same region
as the PROCR that the signaling group uses. If at least port one exists and is in service, the test
passes. Otherwise, the test fails.
Group) on page 492.
Related links
Error codes: None, 2012, 2100 on page 750
Error codes: None, 2012, 2100

Test result
ABORT
Cause
• None: Internal system error.
Solution
Error code: 2808

Test result
ABORT
Cause
This test is not applicable when the SBS field on the H.323 signaling group form is set to y.
Test result
FAIL
Firmware Download Test (#1413)
No VoIP resource ports in this region are in service. Every session is down.
Solution
1. Check the Error Log for errors against VoIP resource.
2. Enter test signaling-group grp# and verify the result of the H.323 Signaling Group
Ping test (#1387).
3. If the test continues to fail, escalate the problem. If the test passes, wait for the sessions to
come up.
Test result
PASS
Every session on the Ethernet link is up.

This test has two functions and can only be executed if there is a download schedule to verify or if
there are FW-DWNLD errors to resolve and alarms to clear.
1. This test verifies that the information on the FIRMWARE DOWNLOAD screen is correct.
It also verifies that the source board is of the correct type, the file to be downloaded is
present on that source board, and the file is free of errors. In addition, it verifies that the
target board code and suffix are correct. It also retrieves the new firmware vintage for the
target board and populates the appropriate field in the firmware download table.
2. If this test is executed after a FIRMWARE DOWNLOAD schedule has run and there are
FW-DWNLD alarms/errors, it resolves the errors, clears the alarms, copies the current
download status table to the last table, and clears out the current table.
Related links
No error code
Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 1
Test result
FAIL
Cause
The firmware image file entered on the change firmware download screen is not present on the
source board specified in the screen.
Solution
1. Enter list directory board location and verify that:
• A file system is enabled on the board
• The file is present
2. If the file system is not enabled:
a. Enter enable filesystem.
b. FTP the correct firmware image to the source board.
3. If the correct image file is present, the name entered on the screen is incorrect. Use
change firmware download and enter the correct file name.
Error codes: 2, 3
Test result
FAIL
Cause
• Error code 2: The image file header on the source board is invalid.
• Error code 3: The firmware image file on the source board has a bad CRC.
Solution
FTP a good firmware image file to the source board.
Error code: 4
Test result
FAIL
Cause
Firmware image file name is too long.
Solution
1. Rename the image file to a file name of the correct size.
2. FTP the new image file to the source board.
3. Use change firmware download and enter the new file name on the screen.
Error code: 5
Test result
FAIL
Cause
The TN code of the firmware image file on the source board does not match the TN code entered
on the screen. The firmware file is incorrect for the board type entered on the screen.
Solution
1. Enter list directory board location, and verify that a file system is enabled on
the board and the file is present.
2. If the file system is not enabled, enter enable filesystem and FTP the correct firmware
image to the source board.
3. Use change firmware download and enter the new file name on the screen.
Error code: 6
Test result
FAIL
Cause
The suffix of the firmware image file on the source board does not match the suffix entered on the
screen. The firmware image file is incorrect for the board types entered on the screen.
Solution
1. Enter list directory board location and verify that a file system is enabled on
the board and the file is present.
2. If the correct firmware image is not present, FTP the correct firmware image to the source
board.
3. Enter change firmware download and enter the new file name on the screen.
Error code: 7
Test result
FAIL
Cause
The source board entered on the screen is not present.
Solution
1. Enter display firmware download and verify the source board’s location.
2. Verify the source board’s translations.
3. If the location is incorrect, enter change firmware download and enter the correct
location on the screen.
Error code: 8
Test result
FAIL
Cause
The source boards entered on the screen are incorrect. The board could have been changed after
the schedule was entered.
Solution
1. Enter list configuration. Verify the source board’s location.
2. Enter change firmware download and enter the correct location on the screen.
Test result
PASS
Firmware download to this circuit pack is successful.
Error code: 0
Test result
NO BOARD
Network Region Interconnectivity Test (#1417)
Solution

This test does not specify and list Error Codes in the usual mer. If this test detects a failure, the
test is retried using different IP endpoints, if available, from the same two network regions. If the
test still fails between these network regions:
1. Maintenance software marks the connectivity between them as “failed”.
2. Communication Manager denies every attempted call between them.
For this test, IP phones or Softphones, with the ability to initiate a ping serve as IP endpoints.
For a network region, a Test #1417 looks for ping-capable endpoint. If found, the region’s testing
continues. If not, the test assumes that the region’s connectivity is operating normally.
This test runs on NR-CONN (Network-Region Connect) on page 450.
Related links
Test result
ABORT
Cause
Internal error.
Solution
2. Escalate if the problem persists.
Error code: 1005

Test result
ABORT
Cause
Incorrect test configuration
Solution
Verify the Ethernet link is in-service on all PROCR.
Error code: 1125

Test result
ABORT
Cause
Ethernet link not in service.
Solution
Verify the Ethernet link is in-service for PROCR.
If interface is enabled, the ethernet link is expected to be in-service for this test to run.
Error code: 2000

Test result
ABORT
Cause
Solution
2. If the problem persists, reset the PROCR.
3. Rerun the test.
Error code: 2012

Test result
ABORT
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Error code: 2500

Test result
ABORT
Cause
Solution
Error code: 2801

Test result
ABORT
Cause
No IP address defined.
Solution
Verify IP interfaces translations and retest.
Error code: 2802

Test result
ABORT
Cause
Different IP address pinged than software had allocated for the test.
Solution
Error code: 2807

Test result
ABORT
Cause
The board is administered but not enabled on the change ipserver-interfaces form.

Test result
FAIL
Cause
Ping to the destination failed due to the destination being down.
Solution
Verify that at least one destination reachable through the network regions being tested is up. Ping
this destination (ping ip-address xxx.xxx.xxx.xxx).
Error code: 2805

Test result
FAIL
Cause
The number of pings received did not match the number sent (normally one ping sent). This
means that no ping responses were received the destination region endpoint being tested back to
the source endpoint sending the ping.
Test result
PASS
TCP/IP Ping test between network regions is successful.
Echo Canceller Test (#1420)

Note:
This test is executed only for DS1 Interface Media Modules that have been administered on
the DS1 screen to provide echo cancellation. The media module must be busied out before
this test is run.
Echo Canceller Test (#1420)
The Echo Canceller Test is part of the test board long demand test sequence of a DS1 Media
Module. The test checks echo cancellation on a subset of channels. If any channel fails twice or
if any two channels fail once, the test fails and echo cancellation is bypassed on every channel
of the board. Otherwise, the test passes and echo cancellation is configured to the administered
parameters.
This test runs on MG-DS1 (DS1 Interface Media Module) on page 436.
Related links
Error code 1015

Test result
ABORT
Cause
The board is not busied out.
Solution
1. If the board is not in use, enter busyout board location.
2. Retry the test.
Error code: 2000

Test result
ABORT
Cause
Solution
Error codes: 2012, 2100, 2500

Test result
ABORT
Solution

Test result
FAIL
The Echo Canceller test failed. Echo Cancellation is no longer being supplied by the board.
• Error 1400: Echo canceller function test failed.
• Error 1401: Echo canceller memory test failed.
Solution
1. Clear the alarm using test board location long.
2. If the test still fails, replace the board.
The board can still be used for a T1/E1 line interface without echo cancellation. This
capability provides limited service for the customer until the board can be changed out.
Test result
PASS
The Echo Cancellation feature is functioning properly.
Solution
Enter release board location to put the board back in service.
Error code: 0
Test result
NO BOARD
Solution
Link State Audit Test (#1527)
Link State Audit Test (#1527)

This test verifies the Branch Gateway H.248 link state and alarm state. If the user knows the MG
is up but there is still an alarm indicating the link is down, this test should be run by using test
media-gateway location.
This test runs on MED-GTWY (MEDIA GATEWAY) on page 425.
Related links
Error code: 1007

Test result
ABORT
Cause
The gateway is not administered.
Error code: 2012

Test result
ABORT
Cause
System call failed.
Solution
Error code: 1
FAIL
Cause
Gateway has been unregistered longer than the Link Loss Delay Timer.
A Major alarm is raised.
Error code: 257

FAIL
Cause
Link is up on a Survivable Remote Server.
Error code: 769

FAIL
Cause
Gateway is in link bounce. It has been unregistered less than the Link Loss Delay Timer.
A Minor alarm is raised.
Test result
PASS
The link is up and there is no alarm.
Power Supply Temperature Test (#1537)

The power supply temperature test provides the status of the following temperatures:
• Inlet to the power supply (120F/49C)
Enable Survivable Core Server Cluster (#1606)

Enable an Survivable Core Server cluster. This test is run when enable ess is entered.
Related links
Error code: 1991

Test result
ABORT
Cause
Requested Survivable Core Server cluster is not administered.
Disable Survivable Core Server Cluster (#1607)
Error code: 1992

Test result
ABORT
Cause
Requested Survivable Core Server cluster is not registered.
Error code: 1993

Test result
ABORT
Cause
Requested Survivable Core Server is controlling an media gateway or Avaya Aura® Media Server.
Error code: 1994

Test result
ABORT
Cause
A Survivable Core Server cluster may not enable other clusters (Survivable Core Server or main).
It can only change its own enable state.
Error code: 2500

Test result
ABORT
Cause
Internal error.
Test result
PASS
The enable operation was successful.
Disable Survivable Core Server Cluster (#1607)

Disable an Survivable Core Server cluster. This test is run when disable ess is entered.
Related links
Error code: 1991

Test result
ABORT
Cause
Requested Survivable Core Server cluster is not administered.
Error code: 1992

Test result
ABORT
Cause
Requested Survivable Core Server cluster is not registered.
Error code: 1993

Test result
ABORT
Cause
Requested Survivable Core Server is controlling an media gateway or Avaya Aura® Media Server.
Error code: 1994

Test result
ABORT
Cause
A Survivable Core Server cluster may not disable other clusters (Survivable Core Server or main).
It can only change its own disable state.
Error code: 2500

Test result
ABORT
AESVCS Session Level Link Status Test (#1623)
Cause
Internal error.
Test result
PASS
The disable operation was successful.
AESVCS Session Level Link Status Test (#1623)

The Application Enablement Services (AESVCS) Session Level Link Status Test determines if any
AESVCS Links are associated with a given AESVCS Session. This test is run on AESV-LNK (AE
Services Link) on page 299.
Related links
Error code: 1124

Test result
ABORT
Cause
AE Services Server is disabled on the AE Services Administration page of the IP Services form.
Test result
FAIL
No AESVCS links are associated with this session.
Test result
PASS
At least one AESVCS link is assigned.
AESVCS Link Heartbeat Test (#1624)

The Application Enablement Services (AESVCS) Link Heartbeat Test sends a TCP tunnel
connection heartbeat message to the far end AESVCS Server. If the AESVCS Server fails to
return a response to the heartbeat message, the test fails. An AESVCS Link that fails a Heartbeat
test is subsequently deleted from the AESVCS Session.
This test is run for AESV-LNK (AE Services Link) on page 299 and AESV-SES (AE Services
Session) on page 302.
Related links
No error code
Test result
FAIL
Cause
The heartbeat test failed.
Solution
Check the network connectivity and check the AE Services.
Test result
PASS
The heartbeat test passed.
Media Gateway Hyperactivity Audit Test (#1659)

The Media Gateway Hyperactivity Audit Test resolves hyperactive registration alarms associated
with Error Code 1281 if the hyperactive condition no longer exists. This test sends a query to the
media gateway to get the VoIP resources hardware state. This test is executed by entering test
media-gateway location.
This test runs on MED-GTWY (MEDIA GATEWAY) on page 425.
Related links
Error code: 2012

Test result
ABORT
Cause
Internal error.
H.323 Signaling Layer 3 Test (#1673)
Solution
Test result
PASS
The hyperactivity audit test passed.
H.323 Signaling Layer 3 Test (#1673)

This test performs a Layer 3 test for an H323-SGR (H.323 Signaling Group) on page 384.
Related links
Error code: 1005

Test result
ABORT
Cause
The H.323 Signaling Layer 3 Test is not enabled for this H.323 signaling group or the far end IP
address is not specified on the signaling group form.
Error code: 1019

Test result
ABORT
Cause
A Layer 3 Test is already in progress for this signaling group.
Error codes: 1132, 2012, 2100

Test result
ABORT
• Error 1132: No channel is available to run this test.Response to the test was not received
within the time allowed.
Solution
Error code: 2800

Test result
FAIL
Cause
PROCR Ethernet connection could not be found.
Solution
Verify that the PROCR is administered and the Ethernet connection is available.
Test result
FAIL
Cause
Layer 3 Test failed.
Solution
Test result
PASS
Cause
Layer 3 Test passed.
IP Signaling Group Far-End Status Test (#1675)

For a specific IP signaling group, this test will send a status query to the far-end to check the
integrity of the trunk. This test validates that the trunks on this signaling group can be used.
This test runs on SIP-SGRP (SIP Signaling Group) on page 492.
Related links
IP Signaling Group Far-End Status Test (#1675)

No error code
Test result
ABORT
Cause
Either the maintenance object is not a SIP signaling group, the signaling group does not exist, or
the signaling group type is not SIP signaling.
Error code: 1005

Test result
ABORT
Cause
The IP Signaling Group Far-End Status Test (Layer 3) is not enabled for this SIP signaling group.
Error code: 1008

Test result
ABORT
Cause
Signaling group is not in the correct state to run this test.
Solution
Error code: 1019

Test result
ABORT
Cause
An IP Signaling Group Far-End Status Test is already in progress for this signaling group.
Error code: 1133

Test result
ABORT
Cause
System is in restart.
Solution
Retry the command after the system finishes the restart.
Error code: 1183

Test result
ABORT
Cause
The SIP signaling group is out of service.
Solution
Error code: 2000

Test result
FAIL
Cause
Solution
Error code: 2100

Test result
ABORT
Cause
Solution
Media Gateway Announcement Module Test (#1683)
Error code: 2012

Test result
ABORT
Cause
Solution
Error code: Any

Test result
FAIL
Cause
The IP signaling far-end status test failed. The response was not received within the allowed time.
Solution
Test result
PASS
The IP signaling far-end status test passed.
Media Gateway Announcement Module Test (#1683)

The Media Gateway Announcement Module test (#1683) is nondestructive and performs the
following:
• Checks the status of the Media Gateway Announcement module–verifies whether the
Compact Flash is turned on in the change media gateway administration screen.
• Makes status inquiries to the Media Gateway Announcement Module–requests for data from
the module to inquire whether the module is currently experiencing any problems related to
the Compact Flash.
This test runs as part of periodic and scheduled maintenance as well as initialization and analysis.
When running the demand test, the Media Gateway Announcement module can respond with any
of the following:
Failure code 1: if the Compact Flash is enabled, but not present, or not recognized, or there are
no announcements found after a reset.
Failure code 2: if the Compact Flash is enabled and is present, but there is not enough RAM to
support it.
Failure code 4: if the Compact Flash is enabled and is present, but there is not enough memory
left on it.
The Media Gateway Announcement module can respond with multiple failures to a single query
and make the error condition a combination of errors. If the board has multiple failures, the error
codes are effectively in a logical order together.
This test also queries the module for the size of the Compact Flash and the amount of memory
used on the Compact Flash.
Note:
Even if the Media Gateway Announcement Module test fails, the announcement module does
not go out of service. However, the announcements may not be in good working condition and
recording new announcements may fail.
Media Gateway VoIP Capacity Test #1718

This test sends a query to the media gateway to get the VoIP resources hardware state. If a
failure, there could be busied-out and hardware-faulted VoIP media resources. The associated
failure error code that might be displayed with this test indicates the percentage of busied-out or
faulted resources. To derive the percentage of faulted resources, use
%faultedchannels = errorcode & 255
To derive the percentage of busied-out resources, use:

%busiedchannels = (errorcode - %faultedchannels) / 256
Related links
Error Code: 1005 on page 772
Error Code: 1005

Test result
ABORT
Cause
The test is not applicable to this media gateway.
Related links
Media Gateway VoIP Capacity Test #1718 on page 772
NO BOARD
Error code: 1706

Test result
ABORT
Cause
The media gateway is not registered.
Related links
Error code: 2000

Test result
ABORT
Cause
Because the media gateway did not respond, the media gateway is not upgraded with the latest
firmware.
Related links
NO BOARD
Cause
No board was detected by the test. The test could not relate the internal ID to the port. This could
be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane
board is inserted.
Solution
1. Enter display errors and check the Error Log for Error Type 125 (wrong board) or
Error Type 131 (no board). Resolve either of these issues, if applicable.
2. Verify that the board is properly translated and inserted by using list configuration.
3. Resolve any problems.
4. For DS1 boards, use add ds1 location to administer the DS1 interface if it is not
already administered.
5. If the board was already administered correctly, check the Error Log to determine whether
the board is hyperactive (Error Type 1538). If so, the board was shut down. Reseating the
board will re-initialize it.
6. If the circuit pack is correctly inserted, enter the following commands:
• busyout board location
• reset board location

• release board location
• test board location long
This should re-establish the linkage between the internal ID and the port. If not, verify that
a valid board is inserted.
Note:
Hyperactivity causes some special problems with the sequence suggested above. If
the ports are translated after entering list config but the Vintage field reports
that there is no board when there really is a board, then the busyout board and
release board commands will not work even though reset board location will
work. The switch will put the hyperactive board back in service after the hyperactivity
clears.
Hyperactive DS1 Media Module

Cause
Error type 1538 in the error log indicates hyperactivity. The hyperactive DS1 board is out of
service and one or more of the following symptoms may be exhibited.
• The DS1 board tests such as test 138 and test 139 abort with error code 2000.
• The tests run on the ports are returning NO BOARD.
• A busyout or a release command has no affect on the test results.
• A list config command shows that the media module and the ports are properly
installed.
When hyperactivity occurs, the DS1 board is isolated from the system, and all of its trunks
are placed into the out-of-service state. The system will try to restore the DS1 board within
15 minutes. When no faults are detected for 15 minutes, the DS1 board is restored to normal
operation and every DS1 interface trunk is returned to the in-service state.
Hyperactivity is often caused by the associated facility. In this 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.
Solution
If the facility is OK and the error occurs again after 15 minutes, escalate this problem.
Repair Procedures for DS1/UDS1 Circuit Pack/Media Module
Repair Procedures for DS1/UDS1 Circuit Pack/Media

Module
T1 network facility procedures
About this task
If the DS1 Media Module connects to a T1 network facility or to another switch, complete the
following steps.
Procedure
1. Verify that both endpoints of the DS1 link are administered using the same signaling mode,
framing mode, and line coding.
2. Contact the T1 Network Service or a technician at the far-end switch to diagnose the
remote DS1 endpoint.
3. Check the physical connectivity of the DS1 boards and of the cable.
4. Replace the local DS1 Media Module, and repeat the test.
Line-side terminating device procedures

About this task
If the DS1 Media Module connects to a line-side terminating device such as a PRI terminal
adapter, complete the following steps.
Procedure
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 DS1 board to the terminating device, and check the
premise distribution system or the intra-premise wiring for physical connection failures.
5. Replace the local DS1 Media Module and repeat the test.
Chapter 8: Resources
Communication Manager documentation

The following table lists the documents related to Communication Manager. Download the
documents from the Avaya Support website at http://support.avaya.com.
Title Description Audience
Design
Avaya Aura® Communication Provides an overview of the features of Sales Engineers,
Manager Overview and Specification Communication Manager. Solution Architects
Avaya Aura® Communication Describes security-related issues and Sales Engineers,
Manager Security Design security features of Communication Solution Architects
Manager.
Avaya Aura® Communication Describes the system capacities for Avaya Sales Engineers,
Manager System Capacities Table Aura® Communication Manager. Solution Architects
LED Descriptions for Avaya Aura® Describes the LED for hardware Sales Engineers,
Communication Manager Hardware components of Avaya Aura® Solution Architects
Components Communication Manager.
Avaya Aura® Communication Describes the hardware requirements for Sales Engineers,
Manager Hardware Description and Avaya Aura® Communication Manager. Solution Architects
Reference
Avaya Aura® Communication Describes the system survivability options Sales Engineers,
Manager Survivability Options for Avaya Aura® Communication Manager. Solution Architects
Avaya Aura® Core Solution Provides a high level description for the Sales Engineers,
Description solution. Solution Architects
Maintenance and Troubleshooting
Avaya Aura® Communication Describes the reports for Avaya Aura® Sales Engineers,
Manager Reports Communication Manager. Solution Architects,
Implementation
Engineers, Support
Personnel
Maintenance Procedures for Avaya Provides procedures to maintain Avaya Sales Engineers,
Aura® Communication Manager, servers and gateways. Solution Architects,
Branch Gateways and Servers Implementation
Engineers, Support
Personnel
Table continues…

Maintenance Commands for Avaya Provides commands to monitor, test, and Sales Engineers,
Aura® Communication Manager, maintain Avaya servers and gateways. Solution Architects,
Branch Gateways and Servers Implementation
Engineers, Support
Personnel
Avaya Aura® Communication Provides procedures to monitor, test, and Sales Engineers,
Manager Alarms, Events, and Logs maintain Avaya servers and describes the Solution Architects,
Reference denial events listed on the Events Report Implementation
form. Engineers, Support
Personnel
Administration
Administering Avaya Aura® Describes the procedures and screens for Sales Engineers,
Communication Manager administering Communication Manager. Implementation
Engineers, Support
Personnel
Administering Network Connectivity Describes the network connectivity for Sales Engineers,
on Avaya Aura® Communication Communication Manager. Implementation
Manager Engineers, Support
Personnel
Avaya Aura® Communication Describes SNMP administration for Sales Engineers,
Manager SNMP Administration and Communication Manager. Implementation
Reference Engineers, Support
Personnel
Administering Avaya Aura® Describes server options for Sales Engineers,
Communication Manager Server Communication Manager. Implementation
Options Engineers, Support
Personnel
Avaya Aura® Communication Describes how to administer Sales Engineers,
Manager Data Privacy Guidelines Communication Manager to fulfill Data Implementation
Privacy requirements. Engineers, Support
Personnel
Implementation and Upgrading
Deploying Avaya Aura® Describes the implementation instructions Implementation
Communication Manager in while deploying Communication Manager Engineers, Support
Virtualized Environment on VMware. Personnel, Solution
Architects
Deploying Avaya Aura® Describes the implementation instructions Implementation
Communication Manager in while deploying Communication Manager Engineers, Support
Software-Only and Infrastructure as on a software-only environment and Personnel, Solution
a Service Environments Amazon Web Service, Microsoft Azure, and Architects
Google Cloud Platform.
Table continues…
Resources

®
Upgrading Avaya Aura Describes instructions while upgrading Implementation
Communication Manager Communication Manager. Engineers, Support
Personnel, Solution
Architects
Understanding
Avaya Aura® Communication Describes the features that you can Sales Engineers,
Manager Feature Description and administer using Communication Manager. Solution Architects,
Implementation Support Personnel
Avaya Aura® Communication Describes the screens that you can Sales Engineers,
Manager Screen Reference administer using Communication Manager. Solution Architects,
Support Personnel
Avaya Aura® Communication Describes the special features that specific Sales Engineers,
Manager Special Application customers request for their specific Solution Architects,
Features requirement. Avaya Business
Partners, Support
Personnel
Finding documents on the Avaya Support website

Procedure
1. Go to https://support.avaya.com.
2. At the top of the screen, click Sign In.
3. Type your EMAIL ADDRESS and click Next.
4. Enter your PASSWORD and click Sign On.
5. Click Product Documents.
6. Click Search Product and type the product name.
7. Select the Select Content Type from the drop-down list
8. In Select Release, select the appropriate release number.
For example, for user guides, click User Guides in the Content Type filter. The list only
displays the documents for the selected category.
9. Press Enter.
Accessing the port matrix document

Procedure
5. Click Product Documents.

6. Click Search Product and type the product name.
7. Select the Select Content Type from the drop-down list
8. In Choose Release, select the required release number.
9. In the Content Type filter, select one or both the following categories:
• Application & Technical Notes
• Design, Development & System Mgt
The list displays the product-specific Port Matrix document.
10. Press Enter.
Avaya Documentation Center navigation

For some programs, the latest customer documentation is now available on the Avaya
Documentation Center website at https://documentation.avaya.com.
Important:
For documents that are not available on Avaya Documentation Center, click More Sites >
Support on the top menu to open https://support.avaya.com.
Using the Avaya Documentation Center, you can:
• Search for keywords.
To filter by product, click Filters and select a product.
• Search for documents.
From Products & Solutions, select a solution category and product, and then select the
appropriate document from the list.
• Sort documents on the search results page.
• Click Languages ( ) to change the display language and view localized documents.
• Publish a PDF of the current section in a document, the section and its subsections, or the
entire document.
• Add content to your collection using My Docs ( ).
Navigate to the Manage Content > My Docs menu, and do any of the following:
- Create, rename, and delete a collection.
- Add topics from various documents to a collection.
- Save a PDF of the selected content in a collection and download it to your computer.
- Share content in a collection with others through email.
- Receive collection that others have shared with you.
Resources
• Add yourself as a watcher using the Watch icon ( ).

Navigate to the Manage Content > Watchlist menu, and do the following:
- Enable Include in email notification to receive email alerts.
- Unwatch selected content, all content in a document, or all content on the Watch list page.
As a watcher, you are notified when content is updated or deleted from a document, or the
document is removed from the website.
• Share a section on social media platforms, such as Facebook, LinkedIn, and Twitter.
• Send feedback on a section and rate the content.
Note:
Some functionality is only available when you log in to the website. The available functionality
depends on your role.
Training
The following courses are available on the Avaya Learning website at http://www.avaya-
learning.com. After logging in to the website, enter the course code or the course title in the
Search field and press Enter or click > to search for the course.
Course code Course title
20460W Virtualization and Installation Basics for Avaya Team Engagement Solutions
20980W What's New with Avaya Aura®
71201V Integrating Avaya Aura® Core Components
72201V Supporting Avaya Aura® Core Components
61131V Administering Avaya Aura® System Manager Release 10.1
61451V Administering Avaya Aura® Communication Manager Release 10.1
Viewing Avaya Mentor videos

Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot
Avaya products.
Support
About this task

Videos are available on the Avaya Support website, listed under the video document type, and on
the Avaya-run channel on YouTube.
• To find videos on the Avaya Support website, go to https://support.avaya.com/ and do one of
the following:
- In Search, type Avaya Mentor Videos, click Clear All and select Video in the Content
Type.
- In Search, type the product name. On the Search Results page, click Clear All and select
Video in the Content Type.
The Video content type is displayed only when videos are available for that product.
In the right pane, the page displays a list of available videos.
• To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor and do
one of the following:
- Enter a keyword or keywords in the Search Channel to search for a specific product or
topic.
- Scroll down Playlists, and click a topic name to see the list of videos available. For
example, Contact Centers.
Note:
Videos are not available for all products.
Support
Go to the Avaya Support website at https://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for release notes,
downloads, and resolutions to issues. Use the online service request system to create a service
request. Chat with live agents to get answers to questions, or request an agent to connect you to a
support team if an issue requires additional expertise.
Using the Avaya InSite Knowledge Base

The Avaya InSite Knowledge Base is a web-based search engine that provides:
• Up-to-date troubleshooting procedures and technical tips
• Information about service packs
• Access to customer and technical documentation
• Information about training and certification programs
• Links to other pertinent information
Resources
If you are an authorized Avaya Partner or a current Avaya customer with a support contract, you
can access the Knowledge Base without extra cost. You must have a login account and a valid
Sold-To number.
Use the Avaya InSite Knowledge Base for any potential solutions to problems.
The system displays the Avaya Support page.
5. Click Support by Product > Product-specific Support.
6. In Enter Product Name, enter the product, and press Enter.
7. Select the product from the list, and select a release.
8. Click the Technical Solutions tab to see articles.
9. Select Related Information.
Index
Special Characters alarms (continued)
SME alarm ....................................................................47
_TM, see Translation Manager ............................................ 55 SME alarms .................................................................. 47
_WD, see Watchdog ............................................................ 58 viewing ..........................................................................18
(maintenance objects warning ......................................................................... 19
H323-BCH .................................................................. 382 warning alarms ........................................................... 295
analog
ring generator (RING-GEN) ........................................490
Numerics Analog Media Module ........................................................ 427
140AY Channel Sanity Inquiry Test (#222) ........................ 620 Analog Port Sanity Test (#963) .......................................... 690
error code 2000 .......................................................... 620 error code 2000, 2100, 2500 ...................................... 690
no error code .............................................................. 620 error code 50 .............................................................. 690
ANL-LN-PT (Analog Line Port) MO ................................... 305
any
A Conference Circuit Test (#7) .......................................546
CRC Error Counter Test (#623) .................................. 654
ABRI-POR MO ...................................................................296
Dial Tone Test (#0) ......................................................529
accessing port matrix .........................................................778
IP Signaling Group Far-End Status Test (#1675) ....... 771
ADJ-IP MO .........................................................................296
Layer 1 Transmission Error Counter Test (#624) ........655
ADM-CONN (Administered Connection) MO .....................297
Layer 2 Status Query Test (#647) ...............................686
ADM-TSC, see TSC-ADM ................................................. 518
NPE Crosstalk Test (#6) ............................................. 540
administered temporary signaling connections, see TSC-
Receive FIFO Error Counter Test (#625) ....................657
ADM .................................................................... 518
SAKI Sanity Test (#53) ............................................... 590
administration
Signaling Group Ping Test (#1387) .............................750
trunks ..........................................................................334
Signaling Link Board Check (#643) ............................ 683
AESV-LNK MO .................................................................. 299
ARB (Arbiter) Linux process
AESV-SES MO .................................................................. 302
MO ................................................................................22
AESVCS Link Heartbeat Test (#1624) ...............................765
ASAI Link Status Test (#1365) ...........................................738
no error code .............................................................. 766
error code 1 ................................................................ 739
AESVCS Session Level Link Status Test (#1623) ............. 765
error code 2500 .......................................................... 739
error code 1124 ...........................................................765
error code 4 ................................................................ 739
alarm ....................................................................................57
ASAI-ADJ MO ....................................................................307
ALARM-PT (Alarm Port) MO ............................................. 303
ASAI-BD MO ......................................................................307
alarming
ASAI-EPT MO ....................................................................308
Layer 2 Switching Processor ........................................ 18
ASAI-PT MO ...................................................................... 314
Media Module ............................................................... 18
Avaya Communication Manager Web Interface
servers ..........................................................................18
viewing alarms ..............................................................19
alarming based .................................................................. 460
Avaya support website .......................................................781
Alarming Based
Service States ............................................................ 460
Alarming Based on Service States .................................... 460 B
alarms
classifications ............................................................... 19 Blue Alarm Inquiry Test (#139) .......................................... 601
generation, in server .....................................................47 error code 0 ................................................................ 604
INADS Link MO .......................................................... 391 error code 1, 2 ............................................................ 603
levels of ...................................................................... 295 error code 2000 .......................................................... 603
major .............................................................................19 error code 2100 .......................................................... 603
major and minor alarms ..............................................295 Line Loopback Alarm ..................................................602
messaging .................................................................... 18 no error code .............................................................. 602
minor .............................................................................19 Payload Loopback Alarm ............................................602
notification .................................................................... 20 BRI Layer 3 Query Test (#629) .......................................... 669
off-board ....................................................................... 19 error code 1005 .......................................................... 669
on-board ....................................................................... 19 error code 1113 ...........................................................669
reporting ....................................................................... 47 error code 1139 ...........................................................670
BRI Layer 3 Query Test (#629) (continued) C
error code 1144 ...........................................................670
error code 1187 ...........................................................670 C-LAN Ethernet Port Status Test (#1386) ..........................743
error code 2000 .......................................................... 672 C-LAN Ethernet Status Test (#1386)
error code 2012 .......................................................... 671 error code 1 ................................................................ 745
error code 2068 .......................................................... 671 error code 1005 .......................................................... 744
BRI Media Module ..................................................... 431, 445 error code 2012 .......................................................... 744
BRI Port Local LAN Looparound Test (#618) error code 2100 .......................................................... 745
error code 1, 2, 7, 8 .................................................... 645 error code 2500 .......................................................... 745
BRI Port Local TDM Looparound Test (#619) ....................642 error code 3, 5, 6, 7 .................................................... 746
error code 1002 .......................................................... 643 CAB-EXFR MO ..................................................................332
error code 1003 .......................................................... 643 Call Process denial events (1001 - 1172) .......................... 147
error code 1004 .......................................................... 644 Call State Audit Test (#257) ............................................... 626
error code 2000 .......................................................... 644 error code 1113 ...........................................................627
error code 2012, 2100, 2103 ...................................... 645 error code 1114 ...........................................................627
BRI Remote Loopback Test (#627) ....................................660 error code 1116 ...........................................................627
error code 1113 ...........................................................661 CDR link .............................................................................478
error code 1139 ...........................................................662 chmod command ........................................................... 59, 61
error code 1144 ...........................................................662 circuit packs
error code 1187 ...........................................................662 combined tone/generators ..........................................374
error code 1412 .......................................................... 663 CLAN
error code 2000 .......................................................... 664 CLAN-BD MO ............................................................. 333
error code 2012 .......................................................... 663 CLAN-BD MO .................................................................... 333
error code 2068 .......................................................... 663 CO Port Diagnostic Test (#3) ............................................. 529
error code 2071, 2072 ................................................ 664 error code 1000 .......................................................... 530
BRI Set Audits Test (#630) ................................................ 673 error code 1005 .......................................................... 530
error code 1113 ...........................................................673 error code 1018 .......................................................... 531
error code 1144 ...........................................................674 CO-BD MO ........................................................................ 333
error code 1187 ...........................................................674 CO-DS1
error code 2012 .......................................................... 675 demand test descriptions ............................................336
error code 2100 .......................................................... 675 error codes ................................................................. 336
BRI XID Test (#628) ...........................................................665 error log entries .......................................................... 335
error code 1000 .......................................................... 665 recommended actions ................................................ 335
error code 1005 .......................................................... 666 CO-DS1 demand test descriptions and error codes .......... 336
error code 1113 ...........................................................666 CO-DS1 MO ...................................................................... 334
error code 1139 ...........................................................667 CO-TRK MO ...................................................................... 337
error code 1144 ...........................................................667 collection
error code 1187 ...........................................................667 delete ..........................................................................779
error code 2000 .......................................................... 668 edit name ....................................................................779
error code 2012, 2100 ................................................ 668 generating PDF .......................................................... 779
BRI-DAT MO ...................................................................... 316 sharing content ........................................................... 779
BRI-PORT ..................................................................318, 320 combined tone generator/detectors, circuit packs ............. 374
BRI-PORT MO ................................................................... 316 Communication Manager
BRI-SET .............................................................................330 alarms ...........................................................................18
BRI-SET MO ......................................................................321 MO escalation procedure ........................................... 295
MOs ............................................................................ 291
SAT ............................................................................. 291
Communication Manager (continued) CSU Equipment Loopback Test (#1210) (continued)
viewing alarms ............................................................294 error code 2100 .......................................................... 709
companding ....................................................................... 374 no error code .............................................................. 707
Conference Circuit Test (#7) .............................................. 541 CSU Repeater Loopback Test (#1211) .............................. 710
any ..............................................................................546 error code 0 ................................................................ 714
error code 0 ................................................................ 547 error code 1005 ...........................................................711
error code 1020 .......................................................... 545 no error code ...............................................................711
error code 1412 .......................................................... 545
error code 2000 .......................................................... 545
error code 2053 .......................................................... 545
D
error code 2100 .......................................................... 546 Denial Events .....................................................................147
no error code .............................................................. 542 Call Processing (1225 - 1899) .................................... 168
content Call Processing Events (2021- 2299) ......................... 236
publishing PDF output ................................................ 779 Call Processing Vector Events (0 — 499) ...................118
searching .................................................................... 779 Connection Manager Events (2300 - 2399) ................261
sharing ........................................................................779 Contact Closure Events (3500 - 3503) ............... 273, 274
sort by last updated .................................................... 779 Data Error Events (3400 - 3499) ................................ 271
watching for updates .................................................. 779 Data Manager Events (3001 - 3004) .......................... 269
Control Channel Looparound Test (#52) ............................586 Dial Access Plan Events (3101 - 3200) ...................... 269
error code 0 ................................................................ 588 Dial Plan Manager Events (2400 - 2406) ................... 267
error code 2000 .......................................................... 586 ESS Events (3600 - 3604) ..................................273, 282
error code 2030 .......................................................... 586 Event Data ....................................................................72
error code 2100 .......................................................... 587 Group Manager Vector Events (500 — 999) .............. 145
error code 2500 .......................................................... 587 Interpreting Event Data 2 ..............................................75
Control LAN circuit pack (CLAN-BD MO) .......................... 333 ISDN, IP, and SIP (1173 - 1224) ................................. 164
CLAN .......................................................................... 333 Location Codes .............................................................75
See also TN799 ..........................................................333 Meet Me Conference Events (3201 - 3299) ............... 270
CPE Loopback Jack Test (#1212) ..................................... 714 Transmission Protocols ................................................ 76
error code 0 ................................................................ 718 Type
error code 1005 .......................................................... 715 IP Events (1900 - 1906) ........................ 223
error code 1015 .......................................................... 716 User Manager Events (1900 - 1906) .......................... 222
error code 1950 .......................................................... 716 Dial Tone Test (#0) .............................................................525
error code 2 ................................................................ 717 any ..............................................................................529
error code 3 ................................................................ 717 error code 1002 .......................................................... 526
no error code .............................................................. 715 error code 1004 .......................................................... 527
CPU occupancy error code 1005 .......................................................... 525
profiling ................................................................... 69, 70 error code 1018 .......................................................... 527
CRC Error Counter Test (#623) ......................................... 653 error code 2000 .......................................................... 527
any ..............................................................................654 error code 2002 .......................................................... 528
error code 2000 .......................................................... 654 DID-DS1 MO ......................................................................343
error code 2012, 2100 ................................................ 654 DIG-IP-S MO ..................................................................... 346
CSU Equipment Loopback Test (#1210) ........................... 706 DIG-LINE MO .................................................................... 349
error code 0 ................................................................ 710 Digital Line Media Module ................................................. 433
error code 1005 .......................................................... 708 Digital Station Audits Test (#17) .........................................561
error code 1951 .......................................................... 709 error code 2000, 2100 ................................................ 565
Digital Station Audits Test (#17) (continued) DS1 Tie Trunk Seizure Test (#136) ....................................596
error code 4 ................................................................ 563 error code 0 ................................................................ 601
error codes 1, 2 .......................................................... 562 error code 1020 .......................................................... 599
Digital Station Lamp Update (#16) .....................................558 error code 1040 .......................................................... 599
error code 3 ................................................................ 559 no error code .............................................................. 597
no error code .............................................................. 559 DS1 Translation Update Test (#146) ..................................614
Digital Terminal Remote Looparound Test (#1201) ........... 699 error code 0 ................................................................ 615
error code 1000, 1001 ................................................ 700 no error code .............................................................. 615
error code 1001 .......................................................... 700
error code 1002 .......................................................... 700
error code 1003 .......................................................... 701
E
error code 1004 .......................................................... 701 E-DIG-ST MO .................................................................... 363
error code 1005 .......................................................... 701 Echo Canceller Test (#1420) ............................................. 758
error code 14, 16 ........................................................ 703 error code 1015 .......................................................... 759
error code 2100 .......................................................... 702 error code 2012, 2100, 2500 ...................................... 760
no error code .............................................................. 699 Electronic Power Feed Inquiry Test (#622) ........................651
DIOD-DS1 MO ...................................................................356 error code 1 ................................................................ 653
Disable Survivable Core Server Cluster (#1607) ...............763 error code 1005 .......................................................... 652
error code 1993 .......................................................... 764 Electronic Power Feed Restoral Test (#620) ..................... 646
display errors ..................................................................... 335 Emergency Transfer (ET) .................................................. 365
DLY-MTCE MO .................................................................. 359 EMG-XFER MO ................................................................. 365
documentation Enable Survivable Core Server Cluster (#1606) ................762
Communication Manager ........................................... 776 error code 1991 .......................................................... 762
documentation center ........................................................ 779 error code 1992 .......................................................... 763
finding content ............................................................ 779 error code 1993 .......................................................... 763
navigation ................................................................... 779 error code 1994 .......................................................... 763
documentation portal ......................................................... 779 error code 2500 .......................................................... 763
finding content ............................................................ 779 End Loopback/Span Test (#1216) ..................................... 727
navigation ................................................................... 779 error code 0 ................................................................ 730
Downloading the firmware image ...................................... 375 error code 1005 .......................................................... 728
DS1 error code 1015 .......................................................... 729
interface circuit packs ................................................. 436 error code 1313 .......................................................... 729
trunks ..........................................................................436 error code 1314 .......................................................... 730
DS1 Board Loopback Test (#1209) ....................................703 error code 2000 .......................................................... 729
error code 1005 .......................................................... 704 no error code .............................................................. 728
error code 1015 .......................................................... 705 Enterprise Survivable Server (ESS)
error code 1412 .......................................................... 705 MO ..............................................................................367
error code 1950 .......................................................... 705 ERR-LOG MO ....................................................................366
error code 2000 .......................................................... 705 error code 0
error code 2100 .......................................................... 706 Blue Alarm Inquiry Test (#139) ................................... 604
no error code .............................................................. 704 CO Port Diagnostic Test (#3) ......................................532
DS1 Interface Media Module ............................................. 436 Conference Circuit Test (#7) .......................................547
error code 0 (continued) error code 1 (continued)
Control Channel Looparound Test (#52) .................... 588 Yellow Alarm Inquiry Test (#141) ................................ 608
CPE Loopback Jack Test (#1212) .............................. 718 error code 1 to 88
CSU Equipment Loopback Test (#1210) .................... 710 Slip Alarm Inquiry Test (#144) .................................... 613
CSU Repeater Loopback Test (#1211) ....................... 714 error code 1, 2, Any
DS1 Board Loopback Test (#1209) ............................ 706 GPP NPE Crosstalk Test (#9) .....................................553
DS1 Tie Trunk Seizure Test (#136) .............................601 error code 10
DS1 Translation Update Test (#146) .......................... 615 Link Retry Test (#215) ................................................ 618
Echo Canceller Test (#1420) ...................................... 760 error code 1000
End Loopback/Span Test (#1216) .............................. 730 BRI Port Local TDM Looparound Test (#619) ............ 643
Far CSU Loopback Test (#1213) ................................ 722 BRI Remote Loopback Test (#627) ............................ 661
Firmware Download Test (#1413) ...............................754 BRI XID Test (#628) ....................................................665
Hybrid Line Local Digital Looparound Test (#58) ........593 CO Port Diagnostic Test (#3) ......................................530
Hybrid Line Remote Digital Looparound Test (#59) ....595 Conference Circuit Test (#7) .......................................542
ICSU Status LEDs Test (#1227) ................................. 733 Dial Tone Test (#0) ......................................................526
Inject Single Bit Error Test (#1215) .............................727 Digital Station Audits Test (#17) ................................. 564
Major Alarm Inquiry Test (#142) ................................. 610 Digital Station Lamp Update (#16) ............................. 560
Minor Alarm Inquiry Test (#143) ................................. 612 Digital Terminal Remote Looparound Test (#1201) .... 700
NPE Crosstalk Test (#6) ............................................. 541 DS1 Tie Trunk Seizure Test (#136) .............................597
One-Way Span Test (#1214) ...................................... 725 Ethernet Local Looparound Test (#1278) ................... 737
ONS Ringer Application Test (#48) .............................585 GPP NPE Crosstalk Test (#9) .....................................548
Port Audit And Update Test (#36) ...............................582 Hybrid Line Local Digital Looparound Test (#58) ........591
Port Diagnostic Test (#35) .......................................... 577 Hybrid Line Remote Digital Looparound Test (#59) ....594
Primary Signaling Link Hardware Check (#636) .........677 Local Loop Test (#13) ................................................. 555
Red Alarm Inquiry Test (#140) ....................................606 Looparound and Conference Test (#33) .....................567
Remote Layer 3 Query (#637) ....................................680 NPE Crosstalk Test (#6) ............................................. 534
Secondary Signaling Link Hardware Check (#639) ....682 ONS Ringer Application Test (#48) .............................583
Signaling Link State Audit Test (#255) ........................621 Port Audit And Update Test (#36) ...............................578
Slip Alarm Inquiry Test (#144) .................................... 614 Port Diagnostic Test (#35) .......................................... 571
Tie Trunk Dial Test (#747) ...........................................689 Service State Audit Test (#256) .................................. 623
VC DSP Port DSP Looparound Test (#1105) ............. 694 Tie Trunk Dial Test (#747) ...........................................687
Yellow Alarm Inquiry Test (#141) ................................ 608 VC DSP Port DSP Looparound Test (#1105) ............. 692
error code 1 VC Port Reset DSP Test (#1106) ................................695
ASAI Link Status Test (#1365) ....................................739 error code 1001
Blue Alarm Inquiry Test (#139) ................................... 603 Dial Tone Test (#0) ......................................................526
BRI Port Local LAN Looparound Test (#618) ............. 645 Digital Terminal Remote Looparound Test (#1201) .... 700
C-LAN Ethernet Status Test (#1386) .......................... 745 GPP NPE Crosstalk Test (#9) .....................................549
Digital Station Audits Test (#17) ................................. 562 Link Loop Test (#13) ................................................... 555
Digital Station Lamp Update (#16) ............................. 559 NPE Crosstalk Test (#6) ............................................. 536
Electronic Power Feed Inquiry Test (#622) .................653 VC DSP Port DSP Looparound Test (#1105) ............. 692
Ethernet Local Looparound Test (#1278) ................... 738 VC Port Reset DSP Test (#1106) ................................695
Firmware Download Test (#1413) ...............................752 error code 1002
GPP NPE Crosstalk Test (#9) .....................................548 BRI Port Local TDM Looparound Test (#619) ............ 643
Hybrid Line Local Digital Looparound Test (#58) ........592 Conference Circuit Test (#7) .......................................543
Hybrid Line Remote Digital Looparound Test (#59) ....594 Dial Tone Test (#0) ......................................................526
Layer 2 Status Query Test (#647) ...............................685 Digital Terminal Remote Looparound Test (#1201) .... 700
Level 1 Status Inquiry Test (#621) .............................. 649 GPP NPE Crosstalk Test (#9) .....................................550
Link State Audit Test (#1527) ..................................... 761 Local Loop Test (#13) ................................................. 556
Network Region Interconnectivity Test (#1417) .......... 755 Looparound and Conference Test (#33) .....................567
Port Audit And Update Test (#36) ...............................581 NPE Crosstalk Test (#6) ............................................. 536
Red Alarm Inquiry Test (#140) ....................................605 TSI Looparound Test (#1108) ..................................... 697
Registration Status Inquiry Test (#1372) .................... 740 VC DSP Port DSP Looparound Test (#1105) ............. 693
SAKI Sanity Test (#53) ............................................... 590 error code 1003
Signaling Group Ping Test (#1387) .............................747 BRI Port Local TDM Looparound Test (#619) ............ 643
Trunk-side Layer 1 Query Test (#1242) ...................... 735 Conference Circuit Test (#7) .......................................543
TSC Heartbeat Inquiry Test (#604) .............................641 Digital Terminal Remote Looparound Test (#1201) .... 701
VC DSP Port DSP Looparound Test (#1105) ............. 694 GPP NPE Crosstalk Test (#9) .....................................550
Local Loop Test (#13) ................................................. 556 Tie Trunk Dial Test (#747) ...........................................688
Looparound and Conference Test (#33) .....................567 TSC Heartbeat Inquiry Test (#604) .............................638
NPE Crosstalk Test (#6) ............................................. 537 error code 1006
Signaling Path PING Test (#1373) ..............................741 Port Audit And Update Test (#36) ...............................579
TSI Looparound Test (#1108) ..................................... 698 Remote Layer 3 Query (#637) ....................................678
VC DSP Port DSP Looparound Test (#1105) ............. 693 error code 1007
error code 1004 Link State Audit Test (#1527) ..................................... 761
BRI Port Local TDM Looparound Test (#619) ............ 644 Network Region Interconnectivity Test (#1417) .......... 758
CO Port Diagnostic Test (#3) ......................................530 Signaling Group Ping Test (#1387) .............................749
Conference Circuit Test (#7) .......................................543 Signaling Path PING Test (#1373) ..............................742
Dial Tone Test (#0) ......................................................527 error code 1008
Digital Terminal Remote Looparound Test (#1201) .... 701 IP Signaling Group Far-End Status Test (#1675) ....... 769
DS1 Tie Trunk Seizure Test (#136) .............................598 ONS Ringer Application Test (#48) .............................584
GPP NPE Crosstalk Test (#9) .....................................550 error code 1010
Hybrid Line Local Digital Looparound Test (#58) ........591 Link Retry Test (#215) ................................................ 618
ISDN Test Call Test (#258) ......................................... 631 Link Tear Down Test (#213) ........................................616
Local Loop Test (#13) ................................................. 556 error code 1015
Looparound and Conference Test (#33) .....................568 CPE Loopback Jack Test (#1212) .............................. 716
NPE Crosstalk Test (#6) ............................................. 537 CSU Equipment Loopback Test (#1210) .................... 708
ONS Ringer Application Test (#48) .............................583 CSU Repeater Loopback Test (#1211) ....................... 712
Port Audit And Update Test (#36) ...............................578 Digital Terminal Remote Looparound Test (#1201) .... 702
Port Diagnostic Test (#35) .......................................... 572 DS1 Board Loopback Test (#1209) ............................ 705
Tie Trunk Dial Test (#747) ...........................................687 Echo Canceller Test (#1420) ...................................... 759
VC DSP Port DSP Looparound Test (#1105) ............. 693 End Loopback/Span Test (#1216) .............................. 729
error code 1005 ................................................................. 772 Far CSU Loopback Test (#1213) ................................ 720
BRI Layer 3 Query Test (#629) ...................................669 Inject Single Bit Error Test (#1215) .............................726
BRI Port Local TDM Looparound Test (#619) ............ 644 One-Way Span Test (#1214) ...................................... 723
BRI Remote Loopback Test (#627) ............................ 661 SAKI Sanity Test (#53) ............................................... 589
BRI XID Test (#628) ....................................................666 VC Port Reset DSP Test (#1106) ................................695
C-LAN Ethernet Status Test (#1386) .......................... 744 error code 1017
CO Port Diagnostic Test (#3) ......................................530 NPE Crosstalk Test (#6) ............................................. 539
Conference Circuit Test (#7) .......................................544 error code 1018
CPE Loopback Jack Test (#1212) .............................. 715 Call State Audit Test (#257) ........................................626
CSU Equipment Loopback Test (#1210) .................... 708 CO Port Diagnostic Test (#3) ......................................531
CSU Repeater Loopback Test (#1211) ....................... 711 Conference Circuit Test (#7) .......................................544
Dial Tone Test (#0) ......................................................525 Dial Tone Test (#0) ......................................................527
Digital Terminal Remote Looparound Test (#1201) .... 701 DS1 Tie Trunk Seizure Test (#136) .............................598
DS1 Board Loopback Test (#1209) ............................ 704 ISDN Test Call Test (#258) ......................................... 631
DS1 Tie Trunk Seizure Test (#136) .............................598 Looparound and Conference Test (#33) .....................568
Electronic Power Feed Inquiry Test (#622) .................652 NPE Crosstalk Test (#6) ............................................. 538
Electronic Power Feed Restoral Test (#620) .............. 646 ONS Ringer Application Test (#48) .............................584
End Loopback/Span Test (#1216) .............................. 728 Port Diagnostic Test (#35) .......................................... 573
Far CSU Loopback Test (#1213) ................................ 719 Service State Audit Test (#256) .................................. 624
H.323 Signaling Layer 3 Test (#1673) ........................ 767 Signaling Link State Audit Test (#255) ........................621
ICSU Status LEDs Test (#1227) ................................. 731 Signaling Path PING Test (#1373) ..............................742
IP Signaling Group Far-End Status Test (#1675) ....... 769 Tie Trunk Dial Test (#747) ...........................................688
ISDN Test Call Test (#258) ......................................... 631 error code 1019
Network Region Interconnectivity Test (#1417) .......... 756 Call State Audit Test (#257) ........................................627
NPE Crosstalk Test (#6) ............................................. 538 H.323 Signaling Layer 3 Test (#1673) ........................ 767
One-Way Span Test (#1214) ...................................... 723 IP Signaling Group Far-End Status Test (#1675) ....... 769
ONS Ringer Application Test (#48) .............................583 ISDN Test Call Test (#258) ......................................... 631
Port Audit And Update Test (#36) ...............................579 Remote Layer 3 Query (#637) ....................................679
Port Diagnostic Test (#35) .......................................... 573 error code 1020
SAKI Sanity Test (#53) ............................................... 589 Conference Circuit Test (#7) .......................................545
Service State Audit Test (#256) .................................. 623 DS1 Tie Trunk Seizure Test (#136) .............................599
Signaling Group Ping Test (#1387) .............................747 GPP NPE Crosstalk Test (#9) .....................................551
error code 1020 (continued) error code 1139
ISDN Test Call Test (#258) ......................................... 632 BRI Layer 3 Query Test (#629) ...................................670
NPE Crosstalk Test (#6) ............................................. 538 BRI Remote Loopback Test (#627) ............................ 662
error code 1024 BRI Set Audits Test (#630) ......................................... 673
ISDN Test Call Test (#258) ......................................... 632 BRI XID Test (#628) ....................................................667
error code 1040 Signaling Link Status Test (#626) ............................... 658
DS1 Tie Trunk Seizure Test (#136) .............................599 error code 1144
Tie Trunk Dial Test (#747) ...........................................688 BRI Layer 3 Query Test (#629) ...................................670
error code 11 BRI Remote Loopback Test (#627) ............................ 662
Network Region Interconnectivity Test (#1417) .......... 755 BRI Set Audits Test (#630) ......................................... 674
error code 1113 BRI XID Test (#628) ....................................................667
BRI Layer 3 Query Test (#629) ...................................669 Signaling Link Status Test (#626) ............................... 659
BRI Remote Loopback Test (#627) ............................ 661 error code 1145
BRI Set Audits Test (#630) ......................................... 673 TSC Heartbeat Inquiry Test (#604) .............................638
BRI XID Test (#628) ....................................................666 error code 1146
Call State Audit Test (#257) ........................................627 TSC Heartbeat Inquiry Test (#604) .............................639
Remote Layer 3 Query (#637) ....................................679 TSC Heartbeat Inquiry Test (#604) .............................639
Service State Audit Test (#256) .................................. 624 error code 1148
Signaling Link Status Test (#626) ............................... 659 TSC Heartbeat Inquiry Test (#604) .............................640
TSC Heartbeat Inquiry Test (#604) .............................638 error code 1149
error code 1114 TSC Heartbeat Inquiry Test (#604) .............................640
Call State Audit Test (#257) ........................................627 error code 1181
ISDN Test Call Test (#258) ......................................... 633 TSC Heartbeat Inquiry Test (#604) .............................640
Service State Audit Test (#256) .................................. 624 error code 1183
Signaling Link State Audit Test (#255) ........................621 IP Signaling Group Far-End Status Test (#1675) ....... 770
error code 1116 error code 1187
Call State Audit Test (#257) ........................................627 BRI Layer 3 Query Test (#629) ...................................670
ISDN Test Call Test (#258) ......................................... 633 BRI Remote Loopback Test (#627) ............................ 662
Service State Audit Test (#256) .................................. 624 BRI Set Audits Test (#630) ......................................... 674
error code 1117 BRI XID Test (#628) ....................................................667
ISDN Test Call Test (#258) ......................................... 633 Level 1 Status Inquiry Test (#621) .............................. 648
Service State Audit Test (#256) .................................. 625 Signaling Link Status Test (#626) ............................... 659
error code 1118 Trunk-side Layer 1 Query Test (#1242) ...................... 734
error code 1119 Looparound and Conference Test (#33) .....................569
error code 1120 End Loopback/Span Test (#1216) .............................. 729
error code 1122 End Loopback/Span Test (#1216) .............................. 730
error code 1123 Looparound and Conference Test (#33) .....................569
error code 1124 Digital Station Audits Test (#17) ................................. 565
AESVCS Session Level Link Status Test (#1623) ......765 Digital Station Lamp Update (#16) ............................. 560
Signaling Group Ping Test (#1387) .............................748 Port Diagnostic Test (#35) .......................................... 573
Network Region Interconnectivity Test (#1417) .......... 756 Digital Terminal Remote Looparound Test (#1201) .... 703
Signaling Group Ping Test (#1387) .............................748 error code 1400
error code 1132 Echo Canceller Test (#1420) ...................................... 760
H.323 Signaling Layer 3 Test (#1673) ........................ 767 error code 1401
Layer 2 Status Query Test (#647) ...............................684 Echo Canceller Test (#1420) ...................................... 760
Secondary Signaling Link Hardware Check (#639) ....681 error code 1412
error code 1133 BRI Port Local TDM Looparound Test (#619) ............ 644
IP Signaling Group Far-End Status Test (#1675) ....... 770 BRI Remote Loopback Test (#627) ............................ 663
error code 1134 Conference Circuit Test (#7) .......................................545
Layer 2 Status Query Test (#647) ...............................684 CSU Equipment Loopback Test (#1210) .................... 708
CSU Repeater Loopback Test (#1211) ....................... 712 Hybrid Line Local Digital Looparound Test (#58) ........592
Digital Terminal Remote Looparound Test (#1201) .... 702 Hybrid Line Remote Digital Looparound Test (#59) ....594
DS1 Board Loopback Test (#1209) ............................ 705 Layer 2 Status Query Test (#647) ...............................685
GPP NPE Crosstalk Test (#9) .....................................552 Level 1 Status Inquiry Test (#621) .............................. 650
ICSU Status LEDs Test (#1227) ................................. 732 Network Region Interconnectivity Test (#1417) .......... 755
ISDN Test Call Test (#258) ......................................... 635 Registration Status Inquiry Test (#1372) .................... 740
Local Loop Test (#13) ................................................. 557 SAKI Sanity Test (#53) ............................................... 590
Looparound and Conference Test (#33) .....................568 Signaling Group Ping Test (#1387) .............................747
NPE Crosstalk Test (#6) ............................................. 539 Trunk-side Layer 1 Query Test (#1242) ...................... 735
ONS Ringer Application (#50) .................................... 584 TSC Heartbeat Inquiry Test (#604) .............................642
Signaling Path PING Test (#1373) ..............................742 Yellow Alarm Inquiry Test (#141) ................................ 608
Registration Status Inquiry Test (#1372) .................... 740 Link Retry Test (#215) ................................................ 618
Signaling Path PING Test (#1373) ..............................743 error code 2000 ................................................................. 773
error code 16 140AY Channel Sanity Inquiry Test (#222) ................. 620
Digital Terminal Remote Looparound Test (#1201) .... 703 Analog Port Sanity Test (#963) ...................................690
error code 1700 Blue Alarm Inquiry Test (#139) ................................... 603
Call State Audit Test (#257) ........................................628 BRI Layer 3 Query Test (#629) ...................................672
Primary Signaling Link Hardware Check (#636) .........676 BRI Port Local TDM Looparound Test (#619) ............ 644
Service State Audit Test (#256) .................................. 625 BRI Remote Loopback Test (#627) ............................ 664
Signaling Link Board Check (#643) ............................ 683 BRI XID Test (#628) ....................................................668
Signaling Link State Audit Test (#255) ........................621 C-LAN Ethernet Status Test (#1386) .......................... 744
error code 1706 ................................................................. 773 CO Port Diagnostic Test (#3) ......................................531
Digital Station Audits Test (#17) ................................. 565 Conference Circuit Test (#7) .......................................545
error code 1950 Control Channel Looparound Test (#52) .................... 586
CPE Loopback Jack Test (#1212) .............................. 716 CPE Loopback Jack Test (#1212) .............................. 716
CSU Equipment Loopback Test (#1210) .................... 708 CRC Error Counter Test (#623) .................................. 654
CSU Repeater Loopback Test (#1211) ....................... 712 CSU Equipment Loopback Test (#1210) .................... 709
DS1 Board Loopback Test (#1209) ............................ 705 CSU Repeater Loopback Test (#1211) ....................... 713
Far CSU Loopback Test (#1213) ................................ 720 Dial Tone Test (#0) ......................................................527
One-Way Span Test (#1214) ...................................... 724 Digital Station Audits Test (#17) ................................. 565
error code 1951 Digital Terminal Remote Looparound Test (#1201) .... 702
CSU Equipment Loopback Test (#1210) .................... 709 DS1 Board Loopback Test (#1209) ............................ 705
CSU Repeater Loopback Test (#1211) ....................... 713 DS1 Tie Trunk Seizure Test (#136) .............................599
ICSU Status LEDs Test (#1227) ................................. 732 Echo Canceller Test (#1420) ...................................... 759
error code 1991 Electronic Power Feed Inquiry Test (#622) .................652
Disable Survivable Core Server Cluster (#1607) ........764 End Loopback/Span Test (#1216) .............................. 729
Enable Survivable Core Server Cluster (#1606) ........ 762 Ethernet Local Looparound Test (#1278) ................... 737
error code 1992 Far CSU Loopback Test (#1213) ................................ 720
Disable Survivable Core Server Cluster (#1607) ........764 GPP NPE Crosstalk Test (#9) .....................................552
Enable Survivable Core Server Cluster (#1606) ........ 763 Hybrid Line Local Digital Looparound Test (#58) ........592
error code 1993 Hybrid Line Remote Digital Looparound Test (#59) ....594
Disable Survivable Core Server Cluster (#1607) ........764 Inject Single Bit Error Test (#1215) .............................726
Enable Survivable Core Server Cluster (#1606) ........ 763 Internal Looparound Test (#135) ................................ 596
error code 1994 IP Signaling Group Far-End Status Test (#1675) ....... 770
Disable Survivable Core Server Cluster (#1607) ........764 ISDN Test Call Test (#258) ......................................... 635
Enable Survivable Core Server Cluster (#1606) ........ 763 Layer 1 Transmission Error Counter Test (#624) ........655
error code 2 Level 1 Status Inquiry Test (#621) .............................. 648
Blue Alarm Inquiry Test (#139) ................................... 603 Local Loop Test (#13) ................................................. 558
BRI Port Local LAN Looparound Test (#618) ............. 645 Looparound and Conference Test (#33) .....................569
C-LAN Ethernet Status Test (#1386) .......................... 745 Major Alarm Inquiry Test (#142) ................................. 609
CPE Loopback Jack Test (#1212) .............................. 717 Minor Alarm Inquiry Test (#143) ..................................611
Digital Station Audits Test (#17) ................................. 562 Network Region Interconnectivity Test (#1417) .......... 756
Far CSU Loopback Test (#1213) ................................ 721 NPE Crosstalk Test (#6) ............................................. 539
Firmware Download Test (#1413) ...............................752 One-Way Span Test (#1214) ...................................... 724
GPP NPE Crosstalk Test (#9) .....................................548 ONS Ringer Application Test (#48) .............................584
Port Audit And Update Test (#36) ...............................580 ISDN Test Call Test (#258) ......................................... 635
Port Diagnostic Test (#35) .......................................... 574 error code 2039
Receive FIFO Error Counter Test (#625) ....................656 ISDN Test Call Test (#258) ......................................... 635
Red Alarm Inquiry Test (#140) ....................................605 error code 2040
Signaling Group Ping Test (#1387) .............................748 ISDN Test Call Test (#258) ......................................... 635
Slip Alarm Inquiry Test (#144) .................................... 613 error code 2041
Tie Trunk Dial Test (#747) ...........................................689 ISDN Test Call Test (#258) ......................................... 635
Trunk-side Layer 1 Query Test (#1242) ...................... 734 error code 2042
TSC Heartbeat Inquiry Test (#604) .............................640 ISDN Test Call Test (#258) ......................................... 636
TSI Looparound Test (#1108) ..................................... 698 error code 2053
VC DSP Port DSP Looparound Test (#1105) ............. 694 Conference Circuit Test (#7) .......................................545
VC Port Reset DSP Test (#1106) ................................695 DS1 Tie Trunk Seizure Test (#136) .............................599
Yellow Alarm Inquiry Test (#141) ................................ 607 error code 2066
error code 2002 ISDN Test Call Test (#258) ......................................... 635
Dial Tone Test (#0) ......................................................528 error code 2067
error code 2012 ISDN Test Call Test (#258) ......................................... 635
BRI Layer 3 Query Test (#629) ...................................671 error code 2068
BRI Port Local TDM Looparound Test (#619) ............ 645 BRI Layer 3 Query Test (#629) ...................................671
BRI Remote Loopback Test (#627) ............................ 663 BRI Remote Loopback Test (#627) ............................ 663
BRI Set Audits Test (#630) ......................................... 675 error code 2069
BRI XID Test (#628) ....................................................668 BRI Layer 3 Query Test (#629) ...................................672
C-LAN Ethernet Status Test (#1386) .......................... 744 BRI Remote Loopback Test (#627) ............................ 664
CRC Error Counter Test (#623) .................................. 654 error code 2071
Echo Canceller Test (#1420) ...................................... 760 BRI Remote Loopback Test (#627) ............................ 664
Electronic Power Feed Inquiry Test (#622) .................652 error code 2072
Electronic Power Feed Restoral Test (#620) .............. 646 BRI Remote Loopback Test (#627) ............................ 664
Ethernet Local Looparound Test (#1278) ................... 738 error code 2074
H.323 Signaling Layer 3 Test (#1673) ........................ 767 ISDN Test Call Test (#258) ......................................... 635
Internal Looparound Test (#135) ................................ 596 error code 2075
IP Signaling Group Far-End Status Test (#1675) ....... 771 ISDN Test Call Test (#258) ......................................... 635
Layer 1 Transmission Error Counter Test (#624) ........655 Analog Port Sanity Test (#963) ...................................690
Level 1 Status Inquiry Test (#621) .............................. 648 Blue Alarm Inquiry Test (#139) ................................... 603
Link Retry Test (#215) ................................................ 619 BRI Layer 3 Query Test (#629) ...................................671
Link State Audit Test (#1527) ..................................... 761 BRI Port Local TDM Looparound Test (#619) ............ 645
Link Tear Down Test (#213) ........................................617 BRI Remote Loopback Test (#627) ............................ 664
Media Gateway Hyperactivity Audit Test (#1659) .......766 BRI Set Audits Test (#630) ......................................... 675
MedPro Status Test (#1392) .......................................750 BRI XID Test (#628) ....................................................668
Network Region Interconnectivity Test (#1417) .......... 756 C-LAN Ethernet Status Test (#1386) .......................... 745
NPE Crosstalk Test (#6) ............................................. 540 Call State Audit Test (#257) ........................................628
Port Diagnostic Test (#35) .......................................... 574 Conference Circuit Test (#7) .......................................546
Receive FIFO Error Counter Test (#625) ....................657 Control Channel Looparound Test (#52) .................... 587
Signaling Group Ping Test (#1387) .............................749 CPE Loopback Jack Test (#1212) .............................. 717
Signaling Link Status Test (#626) ............................... 659 CRC Error Counter Test (#623) .................................. 654
Trunk-side Layer 1 Query Test (#1242) ...................... 734 CSU Equipment Loopback Test (#1210) .................... 709
TSC Heartbeat Inquiry Test (#604) .............................641 CSU Repeater Loopback Test (#1211) ....................... 713
TSI Looparound Test (#1108) ..................................... 698 Digital Station Audits Test (#17) ................................. 565
VC DSP Port DSP Looparound Test (#1105) ............. 694 Digital Terminal Remote Looparound Test (#1201) .... 702
VC Port Reset DSP Test (#1106) ................................696 DS1 Board Loopback Test (#1209) ............................ 706
error code 2030 DS1 Tie Trunk Seizure Test (#136) .............................600
Control Channel Looparound Test (#52) .................... 586 Echo Canceller Test (#1420) ...................................... 760
error code 2035 Electronic Power Feed Inquiry Test (#622) .................652
ISDN Test Call Test (#258) ......................................... 635 End Loopback/Span Test (#1216) .............................. 729
error code 2036 Ethernet Local Looparound Test (#1278) ................... 738
ISDN Test Call Test (#258) ......................................... 635 Far CSU Loopback Test (#1213) ................................ 721
error code 2037 Firmware Download Test (#1413) ...............................752
error code 2100 (continued) error code 2800
GPP NPE Crosstalk Test (#9) .....................................552 H.323 Signaling Layer 3 Test (#1673) ........................ 768
H.323 Signaling Layer 3 Test (#1673) ........................ 767 Signaling Group Ping Test (#1387) .............................749
ICSU Status LEDs Test (#1227) ................................. 732 error code 2801
Inject Single Bit Error Test (#1215) .............................727 Network Region Interconnectivity Test (#1417) .......... 757
IP Signaling Group Far-End Status Test (#1675) ....... 770 Signaling Group Ping Test (#1387) .............................749
Layer 1 Transmission Error Counter Test (#624) ........655 Network Region Interconnectivity Test (#1417) .......... 757
Level 1 Status Inquiry Test (#621) .............................. 649 Signaling Group Ping Test (#1387) .............................749
Local Loop Test (#13) ................................................. 558 error code 2805
Looparound and Conference Test (#33) .....................569 Network Region Interconnectivity Test (#1417) .......... 758
Major Alarm Inquiry Test (#142) ................................. 610 error code 2807
MedPro Status Test (#1392) .......................................750 Network Region Interconnectivity Test (#1417) .......... 758
Minor Alarm Inquiry Test (#143) ..................................611 error code 2808
Network Region Interconnectivity Test (#1417) .......... 757 VoIP Status Test (#1392) ............................................750
NPE Crosstalk Test (#6) ............................................. 540 error code 3
One-Way Span Test (#1214) ...................................... 724 C-LAN Ethernet Status Test (#1386) .......................... 746
ONS Ringer Application Test (#48) .............................585 CPE Loopback Jack Test (#1212) .............................. 717
Port Audit And Update Test (#36) ...............................581 Digital Station Audits Test (#17) ................................. 562
Port Diagnostic Test (#35) .......................................... 574 Digital Station Lamp Update (#16) ............................. 559
Receive FIFO Error Counter Test (#625) ....................657 Far CSU Loopback Test (#1213) ................................ 721
Red Alarm Inquiry Test (#140) ....................................605 Firmware Download Test (#1413) ...............................752
Remote Layer 3 Query (#637) ....................................679 Hybrid Line Local Digital Looparound Test (#58) ........592
SAKI Sanity Test (#53) ............................................... 589 Hybrid Line Remote Digital Looparound Test (#59) ....594
Service State Audit Test (#256) .................................. 625 Layer 2 Status Query Test (#647) ...............................686
Signaling Group Ping Test (#1387) .............................749 Level 1 Status Inquiry Test (#621) .............................. 650
Signaling Link Status Test (#626) ............................... 660 Registration Status Inquiry Test (#1372) .................... 740
Signaling Path PING Test (#1373) ..............................743 Tie Trunk Dial Test (#747) ...........................................689
Slip Alarm Inquiry Test (#144) .................................... 613 Trunk-side Layer 1 Query Test (#1242) ...................... 736
Trunk-side Layer 1 Query Test (#1242) ...................... 734 error code 30
TSC Heartbeat Inquiry Test (#604) .............................638 Link Retry Test (#215) ................................................ 618
TSI Looparound Test (#1108) ..................................... 698 error code 4
VC DSP Port DSP Looparound Test (#1105) ............. 694 ASAI Link Status Test (#1365) ....................................739
VC Port Reset DSP Test (#1106) ................................696 C-LAN Ethernet Status Test (#1386) .......................... 745
Yellow Alarm Inquiry Test (#141) ................................ 608 Digital Station Audits Test (#17) ................................. 563
error code 2103 Firmware Download Test (#1413) ...............................753
BRI Port Local TDM Looparound Test (#619) ............ 645 ISDN Test Call Test (#258) ......................................... 631
error code 2104 Level 1 Status Inquiry Test (#621) .............................. 651
ISDN Test Call Test (#258) ......................................... 636 Secondary Signaling Link Hardware Check (#639) ....681
error code 2500 Signaling Link State Audit Test (#255) ........................622
Analog Port Sanity Test (#963) ...................................690 Trunk-side Layer 1 Query Test (#1242) ...................... 736
ASAI Link Status Test (#1365) ....................................739 error code 40
C-LAN Ethernet Status Test (#1386) .......................... 745 Link Tear Down Test (#213) ........................................616
Control Channel Looparound Test (#52) .................... 587 error code 5
Disable Survivable Core Server Cluster (#1607) ........764 C-LAN Ethernet Status Test (#1386) .......................... 746
Echo Canceller Test (#1420) ...................................... 760 Digital Station Audits Test (#17) ................................. 563
Enable Survivable Core Server Cluster (#1606) ........ 763 Firmware Download Test (#1413) ...............................753
GPP NPE Crosstalk Test (#9) .....................................552 Port Audit and Update Test (#36) ............................... 582
ICSU Status LEDs Test (#1227) ................................. 732 error code 50
Layer 2 Status Query Test (#647) ...............................685 Analog Port Sanity Test (#963) ...................................690
Local Loop Test (#13) ................................................. 558 Link Tear Down Test (#213) ........................................616
Network Region Interconnectivity Test (#1417) .......... 757 error code 6
Remote Layer 3 Query (#637) ....................................679 C-LAN Ethernet Status Test (#1386) .......................... 746
Signaling Group Ping Test (#1387) .............................749 Digital Station Audits Test (#17) ................................. 564
Signaling Path PING Test (#1373) ..............................743 Firmware Download Test (#1413) ...............................753
Link State Audit Test (#1527) ..................................... 761 Port Diagnostic Test (#35) .......................................... 574
error code 61456 Firmware Download Test (#1413) (continued)
Port Diagnostic Test (#35) .......................................... 575 error code 4 ................................................................ 753
error code 61472 error code 5 ................................................................ 753
Port Diagnostic Test (#35) .......................................... 575 error code 6 ................................................................ 753
error code 7 error code 7 ................................................................ 754
BRI Port Local LAN Looparound Test (#618) ............. 645 error code 8 ................................................................ 754
C-LAN Ethernet Status Test (#1386) .......................... 746 no error code .............................................................. 752
Digital Station Audits Test (#17) ................................. 564 Firmware download to DCP stations ................................. 375
Firmware Download Test (#1413) ...............................754 Firmware station download commands ............................. 374
Looparound and Conference Test (#33) .....................569 forced server interchanges
Network Region Interconnectivity Test (#1417) .......... 758 using server -if command ........................... 54, 60, 62, 63
Port Audit and Update Test (#36) ............................... 582 FSY Linux process
Signaling Group Ping Test (#1387) .....................747, 749 alarm, in servers ........................................................... 34
error code 769 FW-STDL ........................................................................... 378
Link State Audit Test (#1527) ..................................... 762 FW-STDL MO .................................................................... 374
error code 8
BRI Port Local LAN Looparound Test (#618) ............. 645
Digital Station Audits Test (#17) ................................. 564
G
Firmware Download Test (#1413) ...............................754 GPP NPE Crosstalk Test (#9) ............................................547
Port Audit and Update Test (#36) ............................... 582 error code 1 ................................................................ 548
Primary Signaling Link Hardware Check (#636) .........676 error code 1, 2, Any .................................................... 553
Secondary Signaling Link Hardware Check (#639) ....681 error code 1000 .......................................................... 548
Signaling Link Board Check (#643) ............................ 683 error code 1001 .......................................................... 549
Signaling Link State Audit Test (#255) ........................622 error code 1002 .......................................................... 550
error code 89 error code 1003 .......................................................... 550
Network Region Interconnectivity Test (#1417) .......... 758 error code 1004 .......................................................... 550
Signaling Group Ping Test (#1387) .............................749 error code 1020 .......................................................... 551
escalation procedure ......................................................... 295 error code 1412 .......................................................... 552
ESS MO .............................................................................367 error code 2 ................................................................ 548
ETH-PT MO ....................................................................... 371 error code 2000 .......................................................... 552
Ethernet Local Looparound Test (#1278) .......................... 737 error code 2100 .......................................................... 552
2012, 2100 ..................................................................738 error code 2500 .......................................................... 552
error code 1 ................................................................ 738
error code 1000 .......................................................... 737
error code 2000 .......................................................... 737 H
ETR-PT MO ....................................................................... 374
H.323
B Channel ...........................................................382, 491
F H323-SGR .................................................................. 384
IP Station .................................................................... 389
Far CSU Loopback Test (#1213) ....................................... 718 H.323 Signaling Layer 3 Test (#1673) ............................... 767
error code 1015 .......................................................... 720 error code 1132, 2012, 2100 .......................................767
error code 2, 3 ............................................................ 721 H323-BCH MO ...................................................................382
error code 2000 .......................................................... 720 H323-SGR MO .................................................................. 384
error code 2100 .......................................................... 721 H323-STN MO ................................................................... 389
no error code .............................................................. 719 Hybrid Line Local Digital Looparound Test (#58) ...............591
file synchronization error code 0 ................................................................ 593
and ARB Event #12 ...................................................... 27 error code 1 2, 3 ......................................................... 592
finding content on documentation center ...........................779 error code 1000 .......................................................... 591
finding port matrix .............................................................. 778 error code 1004 .......................................................... 591
Firmware Download Test (#1413) ......................................751 error code 2000 .......................................................... 592
error code 0 ................................................................ 754 no error code .............................................................. 591
error code 1 ................................................................ 752 Hybrid Line Remote Digital Looparound Test (#59) ...........593
error code 2, 3 ............................................................ 752 error code 0 ................................................................ 595
Hybrid Line Remote Digital Looparound Test (#59) ISDN Test Call Test (#258) (continued)
(continued) error code 1019 .......................................................... 631
error code 1 2, 3 ......................................................... 594 error code 1020 .......................................................... 632
no error code .............................................................. 593 error code 1114 ...........................................................633
Hyperactive DS1/UDS1 Interface Circuit Pack/Media error code 1116 ...........................................................633
Module .................................................................774 error code 1117 ...........................................................633
error code 1118 ...........................................................634
error code 1119 ...........................................................634
I error code 1120 ...........................................................634
ICSU Status LEDs Test (#1227) ........................................ 730 error code 1122 ...........................................................634
error code 0 ................................................................ 733 error code 1123 ...........................................................635
no error code .............................................................. 731 error code 2104 .......................................................... 636
INADS MO ......................................................................... 391 error code 4 ................................................................ 631
incomplete command time-out ...........................................361 error code none, 2000, 2012, 2035, 2036, 2037,
Initialization 2038, 2039, 2040, 2041, 2066, 2067 .................. 635
Periodic Checking .......................................................421 ISDN video codecs ............................................................ 459
Initialization and Periodic Checking ................................... 421 ISDN-PLK .................................................................. 396, 397
Inject Single Bit Error Test (#1215) .................................... 725 ISDN-PLK MO ................................................................... 395
error code 0 ................................................................ 727 ISDN-PRI
error code 1015 .......................................................... 726 DS0 channels ............................................................. 436
error code 2000 .......................................................... 726 ISDN-PRI interface ............................................................ 459
error code 2100 .......................................................... 727 ISDN-SGR ......................................................................... 404
no error code .............................................................. 726 ISDN-SGR MO .................................................................. 398
InSite Knowledge Base ......................................................781 ISDN-TRK MO ................................................................... 405
interarb pattern, in trace log .................................................30
interchanges J
forced server interchange ...........................54, 60, 62, 63
interchange-prep .......................................................... 27 JNL-PRNT MO ...................................................................416
pattern, in trace log .......................................................27
thread, and ARB Event #12 ..........................................27
Internal Looparound Test (#135) ........................................595
L
error code 2000 .......................................................... 596 Layer 1 Transmission Error Counter Test (#624) ...............655
error code 2012 .......................................................... 596 any ..............................................................................655
IP Signaling Group Far-End Status Test (#1675) .............. 768 error code 2000 .......................................................... 655
any ..............................................................................771 error code 2012, 2100 ................................................ 655
error code 1005 .......................................................... 769 Layer 2 Status Query Test (#647) ......................................684
error code 1008 .......................................................... 769 any ..............................................................................686
error code 1133 ...........................................................770 error code 1132 ...........................................................684
error code 1183 ...........................................................770 error code 1134 ...........................................................684
no error code .............................................................. 769 Layer 2 Switching Processor
ISDN SETUP ..................................................................... 459 alarming ........................................................................18
ISDN signaling ................................................................... 459 viewing alarms ..............................................................18
ISDN Test Call Test (#258) ................................................ 629 Level 1 Status Inquiry Test (#621) ..................................... 647
Level 1 Status Inquiry Test (#621) (continued) services (continued)
error code 2000 .......................................................... 648 threads ..........................................................................27
error code 2012 .......................................................... 648 list config ............................................................................291
error code 2100 .......................................................... 649 listhistory Linux command ................................................... 67
error code 3 ................................................................ 650 Local Loop Test (#13) ........................................................ 553
LGATE-AJ MO ................................................................... 416 error code 1002 .......................................................... 556
LGATE-PT MO ...................................................................423 error code 1003 .......................................................... 556
LIC-ERR MO ......................................................................416 error code 1004 .......................................................... 556
License .............................................................................. 421 error code 1412 .......................................................... 557
License file test error code 2000, 2100, 2500 ...................................... 558
Error code 1 ................................................................419 no error code .............................................................. 554
Error code 1014 ..........................................................419 LOG-SVN ...........................................................................423
Error code 2 ................................................................419 error log entries .......................................................... 423
No error code ..............................................................419 LOG-SVN ...........................................................
license files recommended actions ...........................423
LIC-ERR (License-Error Mode) MO ........................... 416 LOG-SVN MO ....................................................................423
NO-LIC MO .................................................................447 login
troubleshooting errors .................................................420 process alarm, in servers ............................................. 43
License mode Login Warning Messages .................................................. 421
License-Error .............................................................. 421 logins
License-Normal .......................................................... 421 alarms, in server ........................................................... 41
No-License ................................................................. 421 logv Linux command ............................................................30
Line Loopback Alarm, Blue Alarm Inquiry Test (#139) .......602 Looparound and Conference Test (#33) ............................ 566
line-side terminating device procedures ............................ 775 error code 1000 .......................................................... 567
Link Loop Test (#13) error code 1002 .......................................................... 567
none ............................................................................558 error code 1004 .......................................................... 568
Link Retry Test (#215) ........................................................618 error code 1018 .......................................................... 568
error code 10, 20 ........................................................ 618 error code 1412 .......................................................... 568
error code 2012 .......................................................... 619 error code 7, 129, 131, 133 ........................................ 569
error code 30 .............................................................. 618 no error code .............................................................. 566
Link State Audit Test (#1527) .............................................761 Loss of Multiframe Alarm, Red Alarm Inquiry Test (#140) . 604
error code 1 ................................................................ 761 Loss of Signal Alarm Inquiry Test (#138) ........................... 601
error code 1007 .......................................................... 761
error code 2012 .......................................................... 761
error code 257 ............................................................ 761
M
error code 769 ............................................................ 762 maintenance
Link Tear Down Test (#213) ............................................... 616 common port media module ....................................... 520
error code 1010 .......................................................... 616 maintenance object repair procedures
error code 2012 .......................................................... 617 ADJ-IP/ASAI-IP (ASAI Adjunct IP Link) ......................297
error code 40, 50 ........................................................ 616 ADM-CONN (administered connection) ..................... 297
Linux ASAI-IP (ASAI Adjunct IP Link) .................................. 314
chmod ...........................................................................59 BRI-DAT (ISDN-BRI Data Module) ............................. 316
commands BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI
chmod ..................................................... 61 ISDN-BRI Port) ....................................................316
logv ......................................................... 30 BRI-SET, ASAI-ADJ, BRI-DAT ....................................321
server -if ................................ 54, 60, 62, 63 CDR-LNK (CDR Link) .................................................333
shutdown .................................................26 PRI-CDR .....................................................................477
daemons maintenance objects ....................................18, 447, 454, 481
and ARB event #9 ...................................30 ASAI-PT ......................................................................314
interchange-prep .......................................................... 27 BRI-DAT ......................................................................316
listhistory .......................................................................67 BRI-PORT ...................................................................316
services BRI-SET ..................................................................... 321
and ARB event #9 ...................................30 CAB-EXFR ................................................................. 332
stop ...............................................................................67 Communication Manager ........................................... 291
maintenance objects (continued) Media Gateway Hyperactivity Audit Test (#1659) .............. 766
DIG-IP-S ..................................................................... 346 error code 2012 .......................................................... 766
DIG-LINE .................................................................... 349 Media Gateway Processor CLI
Digital Line Media Module .......................................... 433 viewing alarms ..............................................................18
DIOD-DS1 .................................................................. 356 media gateway voip capacity test 1718 ............................. 772
DLY-MTCE ..................................................................359 Media Module
DS1 Interface Media Module ...................................... 436 alarming ........................................................................18
FW-STDL ....................................................................374 MM711 Analog ............................................................427
H323-SGR .................................................................. 384 MM712 DCP ............................................................... 433
H323-STN ...................................................................389 MedPro Status Test (#1392) .............................................. 750
INADS .........................................................................391 error code none, 2012, 2100 ...................................... 750
ISDN-PLK ................................................................... 395 Meidia Gateway
ISDN-SGR .................................................................. 398 list config .....................................................................291
ISDN-TRK ...................................................................405 S8300E .......................................................................291
JNL-PRNT .................................................................. 416 memory leak ........................................................................ 57
LGATE-AJ ...................................................................416 messaging alarms ................................................................18
LGATE-PT .................................................................. 423 MG-ANA .................................................................... 427, 429
LIC-ERR ..................................................................... 416 MG-ANA MO ......................................................................427
MG-ANA ..................................................................... 427 MG-ANN .................................................................... 429, 431
MG-BRI ...............................................................431, 445 MG-BRI ..............................................................................433
MG-DCP ..................................................................... 433 MG-BRI MO ............................................................... 431, 445
MG-DS1 ......................................................................436 MG-DCP .................................................................... 434, 435
MG-IAMM ................................................................... 442 MG-DCP MO ..................................................................... 433
MIS ............................................................................. 446 MG-DS1 .....................................................................436, 441
MM712 ........................................................................433 MG-DS1 MO ...................................................................... 436
NO-LIC ....................................................................... 447 MG-IAMM .......................................................................... 443
NR-CONN ...................................................................450 MG-IAMM MO ....................................................................442
NR-REG ..................................................................... 451 MG-SYNC ..........................................................................445
PDMODULE ............................................................... 453 Minor Alarm Inquiry Test (#143) .........................................610
PLAT-ALM ...................................................................468 error code 0 ................................................................ 612
PMS-LINK ...................................................................469 error code 2000 ...........................................................611
PMS-PRNT .................................................................474 error code 2100 ...........................................................611
PRI-CDR .....................................................................477 no error code ...............................................................611
REM-OFF ................................................................... 489 minor alarms ................................................................ 19, 295
SIP-BCH ..................................................................... 491 MIS .................................................................................... 446
SIP-SGRP .................................................................. 492 MIS MO ..............................................................................446
TIME-DAY ...................................................................517 MM710 ...............................................................................436
Maintenance objects MM711 ............................................................................... 427
groupings ....................................................................293 MM712 ...............................................................................433
maintenance SAT command syntax .................................. 294 MM720 .......................................................................431, 445
Major Alarm Inquiry Test (#142) .........................................609 MO
error code 0 ................................................................ 610 RANL-STA .................................................................. 481
error code 2000 .......................................................... 609 MOs
error code 2100 .......................................................... 610 ETH-PT .......................................................................371
no error code .............................................................. 609 MOs (maintenance objects)
major alarms ................................................................ 19, 295 ABRI-POR .................................................................. 296
management information system (MIS) .............................446 ADJ-IP ........................................................................ 296
MED-GTWY ADM-CONN ................................................................297
demand test descriptions ............................................427 AESV-LNK .................................................................. 299
error codes ................................................................. 427 AESV-SES ..................................................................302
error log entries .......................................................... 425 ALARM-PT ................................................................. 303
MED-GTWY demand test descriptions and error codes ....427 AN-LN-PT ................................................................... 305
MED-GTWY error log entries and recommended actions . 425 ASAI-ADJ ................................................................... 307
MED-GTWY MO ................................................................ 425 ASAI-BD ..................................................................... 307
Media Gateway ASAI-EPT ................................................................... 308
list config .....................................................................291 CLAN-BD ....................................................................333
Media Gateway Announcement Module Test (#1683) .......771 CO-BD ........................................................................ 333
MOs (maintenance objects) (continued) no error code (continued)
CO-DS1 ...................................................................... 334 DS1 Board Loopback Test (#1209) ............................ 704
CO-TRK ......................................................................337 DS1 Tie Trunk Seizure Test (#136) .............................597
DID-DS1 ..................................................................... 343 DS1 Translation Update Test (#146) .......................... 615
E-DIG-ST ....................................................................363 End Loopback/Span Test (#1216) .............................. 728
EMG-XFER .................................................................365 Far CSU Loopback Test (#1213) ................................ 719
ERR-LOG ................................................................... 366 Firmware Download Test (#1413) ...............................752
ESS ............................................................................ 367 Hybrid Line Local Digital Looparound Test (#58) ........591
ETR-PT .......................................................................374 Hybrid Line Remote Digital Looparound Test (#59) ....593
LOG-SVN ................................................................... 423 ICSU Status LEDs Test (#1227) ................................. 731
MED-GTWY ................................................................425 Inject Single Bit Error Test (#1215) .............................726
PE-BCHL .................................................................... 459 IP Signaling Group Far-End Status Test (#1675) ....... 769
PROC-SAN .................................................................480 Local Loop Test (#13) ................................................. 554
RDIG-STA ...................................................................483 Looparound and Conference Test (#33) .....................566
RING-GEN ..................................................................490 Major Alarm Inquiry Test (#142) ................................. 609
SEC-CDR ................................................................... 491 Minor Alarm Inquiry Test (#143) ..................................611
SP-REG-M ..................................................................503 NPE Crosstalk Test (#6) ............................................. 533
SP-REG-S .................................................................. 504 One-Way Span Test (#1214) ...................................... 723
STRAT-3 ..................................................................... 505 ONS Ringer Application Test (#48) .............................583
SYS-LINK ................................................................... 512 Port Audit And Update Test (#36) ...............................578
SYSTEM .....................................................................516 Port Diagnostic Test (#35) .......................................... 571
TDMODULE ............................................................... 517 Primary Signaling Link Hardware Check (#636) .........676
TSC-ADM ................................................................... 518 Red Alarm Inquiry Test (#140) ....................................605
XXX-BD ...................................................................... 520 Remote Layer 3 Query (#637) ....................................678
MPDM ................................................................................454 SAKI Sanity Test (#53) ............................................... 588
Multiple PRI endpoints .......................................................459 Secondary Signaling Link Hardware Check (#639) ....681
My Docs .............................................................................779 Signaling Link Board Check (#643) ............................ 682
Slip Alarm Inquiry Test (#144) .................................... 613
Tie Trunk Dial Test (#747) ...........................................687
N TSI Looparound Test (#1108) ..................................... 697
NetMeeting ........................................................................ 389 Yellow Alarm Inquiry Test (#141) ................................ 607
Network Region Interconnectivity Test (#1417) ................. 755 No license MO ................................................................... 447
error code 1, 2, 11 .......................................................755 no-LIC MO ......................................................................... 447
error code 1005 .......................................................... 756 none
error code 1125 ...........................................................756 ISDN Test Call Test (#258) ......................................... 635
error code 2000 .......................................................... 756 Link Loop Test (#13) ................................................... 558
error code 2012 .......................................................... 756 MedPro Status Test (#1392) .......................................750
error code 2100 .......................................................... 757 Remote Layer 3 Query (#637) ....................................679
error code 2500 .......................................................... 757 Signaling Group Ping Test (#1387) .............................747
error code 2801 .......................................................... 757 Signaling Link State Audit Test (#255) ........................621
error code 2802 .......................................................... 757 NPE Crosstalk Test (#6) .................................................... 532
error code 2805 .......................................................... 758 any ..............................................................................540
error code 7, 89, 1007 ................................................ 758 error code 1000 .......................................................... 534
network regions error code 1001 .......................................................... 536
NR-CONN MO ............................................................450 error code 1002 .......................................................... 536
NO BOARD ........................................................................773 error code 1003 .......................................................... 537
no error code error code 1004 .......................................................... 537
140AY Channel Sanity Inquiry Test (#222) ................. 620 error code 1005 .......................................................... 538
AESVCS Link Heartbeat Test (#1624) ........................766 error code 1017 .......................................................... 539
Blue Alarm Inquiry Test (#139) ................................... 602 error code 1018 .......................................................... 538
Conference Circuit Test (#7) .......................................542 error code 1020 .......................................................... 538
CPE Loopback Jack Test (#1212) .............................. 715 error code 1412 .......................................................... 539
CSU Equipment Loopback Test (#1210) .................... 707 error code 2000 .......................................................... 539
CSU Repeater Loopback Test (#1211) ....................... 711 error code 2012 .......................................................... 540
Digital Station Lamp Update (#16) ............................. 559 error code 2100 .......................................................... 540
Digital Terminal Remote Looparound Test (#1201) .... 699 no error code .............................................................. 533
NR-CONN ..........................................................................451 Port Audit And Update Test (#36) (continued)
NR-CONN MO ................................................................... 450 error code 1006 .......................................................... 579
NR-REG .............................................................................452 error code 2000 .......................................................... 580
NR-REG MO ......................................................................451 error code 2100 .......................................................... 581
no error code .............................................................. 578
Port Diagnostic Test (#35) ................................................. 570
O error code 0 ................................................................ 577
off-board alarms ...................................................................19 error code 1000 .......................................................... 571
on-board alarms ...................................................................19 error code 1004 .......................................................... 572
One-Way Span Test (#1214) ............................................. 722 error code 1005 .......................................................... 573
error code 2100 .......................................................... 724 error code 61446 ........................................................ 574
no error code .............................................................. 723 error code 61456 ........................................................ 575
ONS Ringer Application (#48) error code 61472 ........................................................ 575
error code 1412 .......................................................... 584 no error code .............................................................. 571
ONS Ringer Application Test (#48) ....................................582 port matrix ..........................................................................778
error code 0 ................................................................ 585 Port Service States ............................................................ 461
error code 1000, 1004 ................................................ 583 Power Supply Temperature Test (#1537) .......................... 762
error code 1005 .......................................................... 583 PRI
error code 1008 .......................................................... 584 endpoint port (PE-BCHL) ............................................459
error code 1018 .......................................................... 584 PRI endpoin ....................................................................... 459
error code 2000 .......................................................... 584 PRI Endpoint ......................................................................461
error code 2100 .......................................................... 585 Port Service States .....................................................461
no error code .............................................................. 583 PRI Endpoint Port Service States ......................................461
PRI-CDR ....................................................................478, 480
PRI-CDR MO ..................................................................... 477
P Primary Signaling Link Hardware Check (#636) ................675
error code 0 ................................................................ 677
Payload Loopback Alarm, Blue Alarm Inquiry Test (#139) 602
error code 1700 .......................................................... 676
PDMODULE .............................................................. 456, 458
error code 8 ................................................................ 676
PDMODULE MO ................................................................453
no error code .............................................................. 676
PE-BCHL
Printer Link .........................................................................475
demand test descriptions ............................................468
PROC-SAN ........................................................................480
error codes ................................................................. 468
PROC-SAN MO ................................................................. 480
error log entries .......................................................... 465
process sanity audits (PROC-SAN) ...................................480
recommended actions ................................................ 465
programmable terminals .................................................... 483
PE-BCHL demand test descriptions and error codes ........ 468
property management system (PMS) ........................ 469, 474
PE-BCHL error log entries and recommended actions ......465
link (PMS-LINK) ..........................................................469
PE-BCHL MO .................................................................... 459
Proshare ............................................................................ 389
PLAT-ALM (Platform Alarm) MO ........................................468
purpose ................................................................................16
PMS ................................................................................... 475
printer link (PMS-PRNT/JNL-PRNT) .......................... 474
PMS-LINK ..................................................................471, 473 R
PMS-LINK MO ................................................................... 469
PMS-PRNT ........................................................................ 476 R2-MFC signaling .............................................................. 374
PMS-PRNT MO ................................................................. 474 RANL-STA ......................................................................... 481
Port Audit and Update Test (#36) RANL-STA MO ...................................................................481
error code 5, 7, 8 ........................................................ 582 RANL-STL ......................................................................... 482
Port Audit And Update Test (#36) ...................................... 577 RDIG-STA .................................................................. 487, 489
error code 0 ................................................................ 582 RDIG-STA MO ................................................................... 483
error code 1 ................................................................ 581 Receive FIFO Error Counter Test (#625) ...........................656
error code 1000 .......................................................... 578 any ..............................................................................657
recommended actions Secondary Signaling Link Hardware Check (#639)
error log entries .......................................................... 425 (continued)
Red Alarm Inquiry Test (#140) ........................................... 604 no error code .............................................................. 681
error code 0 ................................................................ 606 server
error code 1 ................................................................ 605 alarming ........................................................................18
error code 2000 .......................................................... 605 alarms
error code 2100 .......................................................... 605 _TM alarm ...............................................55
Loss of Multiframe Alarm ............................................604 _WD alarms ............................................ 58
no error code .............................................................. 605 FSY alarm ............................................... 34
Registration Status Inquiry Test (#1372) ............................740 Login alarms ........................................... 41
error code 1, 2, 3 ........................................................ 740 SVC_MON alarms .................................. 51
error code 1427 .......................................................... 740 MOs
REM-OFF MO ....................................................................489 _MP Maintenance Processor) .................39
remote analog line station port .................................. 481, 482 _TM (Translation Manager) .....................55
remote digital station ..........................................................489 _WD (Watchdog) .....................................58
Remote Layer 3 Query (#637) ........................................... 677 ARB (Arbiter) ...........................................22
error code 0 ................................................................ 680 MOS ............................................................................. 47
error code 1006 .......................................................... 678 SME (Server Maintenance Engine) .............................. 47
error code 1019 .......................................................... 679 SME alarm server .........................................................47
error code 1113 ...........................................................679 server alarms
error code 2100 .......................................................... 679 Linux servers ................................................................ 20
error code 2500, none ................................................ 679 server Linux command
no error code .............................................................. 678 with -if argument ......................................... 54, 60, 62, 63
Remote Multiframe Alarm, Yellow Alarm Inquiry Test server MOs
(#141) .................................................................. 607 _MP .............................................................................. 39
reset Server traps ......................................................................... 20
SAT commands servers
reset translation-id ................................ 490 alarms
Retiring login alarm .............................................. 43
SVN alarm .................................................................. 424 states, corrupt ...............................................................23
Retiring an SVN Alarm .......................................................424 Service State Audit Test (#256) ......................................... 622
RING-GEN (Analog Ring Generator) MO ..........................490 error code 1000 .......................................................... 623
RNG-GEN MO ................................................................... 490 error code 1005 .......................................................... 623
error code 1018 .......................................................... 624
error code 1113 ...........................................................624
S error code 1114 ...........................................................624
SAKI Sanity Test (#53) .......................................................588 error code 1116 ...........................................................624
any ..............................................................................590 error code 1117 ...........................................................625
error code 1015 .......................................................... 589 service states .....................................................................460
error code 2 ................................................................ 590 shadowed heap usage .........................................................57
error code 2100 .......................................................... 589 sharing content .................................................................. 779
no error code .............................................................. 588 shutdown Linux command ................................................... 26
sanity Signaling
audits .......................................................................... 480 B-Channel States ....................................................... 460
SAT signaling and B-Channel states ......................................... 460
command syntax ........................................................ 294 Signaling Group Ping Test (#1387) ....................................746
Communication Manager ........................................... 291 2012, 2100, 2500 ........................................................749
Scheduling the download ...................................................377 any ..............................................................................750
searching for content ......................................................... 779 error code 1005 .......................................................... 747
SEC-CDR MO ....................................................................491 error code 1124, 1125 .................................................748
Secondary Signaling Link Hardware Check (#639) ........... 680 error code 2000 .......................................................... 748
error code 0 ................................................................ 682 error code 2800, 2801 ................................................ 749
error code 4 ................................................................ 681 error code 7 ................................................................ 747
error code 8 ................................................................ 681 error code 7, 89, 1007 ................................................ 749
Signaling Group Ping Test (#1387) (continued) SRP-EPN ...........................................................................503
error code none, 1, 2 .................................................. 747 stop command ..................................................................... 67
Signaling Link Board Check (#643) ................................... 682 STRAT-3
any ..............................................................................683 error log entries .......................................................... 509
error code 1700 .......................................................... 683 recommended actions ................................................ 509
error code 8 ................................................................ 683 STRAT-3 error log entries and recommended actions .......509
no error code .............................................................. 682 STRAT-3 MO ......................................................................505
Signaling Link State Audit Test (#255) ...............................620 support ...............................................................................781
error code 1018 .......................................................... 621 SVC_MON (Service Monitor) process alarms, in server ..... 51
error code 1114 ...........................................................621 SYS-LINK MO ....................................................................512
error code 1700 .......................................................... 621 System Administration Terminal
error code 4 ................................................................ 622 License-Error mode .................................................... 421
error code 8 ................................................................ 622 No-License mode ....................................................... 421
error code none, 0 ...................................................... 621 SYSTEM MO ..................................................................... 516
Signaling Link Status Test (#626) ...................................... 658
error code 1113 ...........................................................659
error code 1139 ...........................................................658
T
error code 1144 ...........................................................659 T1 network facility procedures ........................................... 775
error code 1187 ...........................................................659 TDMODULE .......................................................................456
error code 2012 .......................................................... 659 TDMODULE MO ................................................................517
error code 2100 .......................................................... 660 terminal parameters ...........................................................484
Signaling Path PING Test (#1373) .....................................741 testing
error code 1003 .......................................................... 741 common port media module maintenance ................. 520
error code 1007 .......................................................... 742 Tie Trunk Dial Test (#747) ..................................................686
SIP-BCH error log entries and recommended actions .......492 error code 1040 .......................................................... 688
SIP-BCH MO ..................................................................... 491 error code 2000 .......................................................... 689
SIP-SGRP demand test descriptions and error codes ...... 503 error code 3 ................................................................ 689
SIP-SGRP MO ...................................................................492 no error code .............................................................. 687
Slip Alarm Inquiry Test (#144) ............................................612 TIME-DAY MO ................................................................... 517
error code 0 ................................................................ 614 timers
error code 1 to 88 ....................................................... 613 and trunk-group administration ...........................334, 405
error code 2000 .......................................................... 613 keep alive endpoint .....................................................384
error code 2100 .......................................................... 613 layer-3 messages ....................................................... 308
no error code .............................................................. 613 printer link idle ............................................................ 476
SME alarms, in server ......................................................... 47 T310 ................................................................... 384, 399
snd2Inads string, in trace log ...............................................48 trunk-group administration ..........................................356
SNI Destructive Facility Off-Board Test (#756) .................. 690 TN464 circuit packs
SNMP DS1 interface ..............................................................436
trap manager ................................................................ 20 tone detectors, enhanced tone receiver ports ................... 374
sockets trace-log patterns
and ARB Event #11 ...................................................... 26 interarb ......................................................................... 30
sort documents by last updated .........................................779 interchange-prep .......................................................... 27
SP-REG-M training ............................................................................... 780
error log entries .......................................................... 503 Translation Manager
recommended actions ................................................ 503 process alarm, in server ............................................... 55
SP-REG-M error log entries and recommended actions ... 503 server MO .....................................................................55
SP-REG-M MO .................................................................. 503 translations
SP-REG-S MO ...................................................................504 failures, reading or loading ........................................... 56
SPID Facility Test ...............................................................330 traps
SPID facility test 1 ..............................................................331 Server ........................................................................... 20
SPID facility test 2 ..............................................................331 trunk
SPID facility test 3 ..............................................................332 data module (TDMODULE) ........................................ 517
Trunk-side Layer 1 Query Test (#1242) ............................. 733 view alarms (continued)
error code 1 ................................................................ 735 SAT ............................................................................... 19
error code 1187 ...........................................................734 web interface ................................................................ 19
error code 2 ................................................................ 735 viewing alarms
error code 2000 .......................................................... 734 Communication Manager ........................................... 294
error code 2012, 2100 ................................................ 734 virtual memory heap ............................................................ 57
error code 3 ................................................................ 736 voice announcements ........................................................431
error code 4 ................................................................ 736 VoIP
trunks connectivity .................................................................450
administration ............................................................. 334 VoIP Status Test (#1392)
DS1 .............................................................................436 error code 2808 .......................................................... 750
TSC Heartbeat Inquiry Test (#604) .................................... 637 VVC DSP Port DSP Looparound Test (#1105)
error code 1 ................................................................ 641 error code 2012, 2100 ................................................ 694
error code 1005 .......................................................... 638
error code 1113 ...........................................................638
error code 1145 ...........................................................638
W
error code 1146 ...........................................................639 warning alarms ............................................................ 19, 295
error code 1147 ...........................................................639 watch list ............................................................................ 779
error code 1148 ...........................................................640 Watchdog
error code 1149 ...........................................................640 alarms, in server ........................................................... 58
error code 1181 ...........................................................640 Watchdog (_WD) server MO ................................................58
error code 2 ................................................................ 642 web interface
error code 2000 .......................................................... 640 viewing alarms ..............................................................18
error code 2012 .......................................................... 641 Wideband
error code 2100 .......................................................... 638 Switching .................................................................... 459
TSC-ADM .......................................................................... 519 Wideband Switching .......................................................... 459
TSC-ADM MO ....................................................................518
TSI Looparound Test (#1108) ............................................ 697
error code 1002 .......................................................... 697 X
error code 1003 .......................................................... 698
XXX-BD MO .......................................................................520
error code 2000 .......................................................... 698
error code 2012 .......................................................... 698
error code 2100 .......................................................... 698 Y
no error code .............................................................. 697
Yellow Alarm Inquiry Test (#141) ....................................... 606
error code 0 ................................................................ 608
U error code 1, 2 ............................................................ 608
error code 2000 .......................................................... 607
unshadowed heap usage .....................................................58
error code 2100 .......................................................... 608
no error code .............................................................. 607
V Remote Multiframe Alarm ...........................................607
Yellow F5 State Alarm ................................................ 607
VC DSP Port DSP Looparound Test (#1105) .....................691 Yellow F5 State Alarm, Yellow Alarm Inquiry Test (#141) .. 607
error code 0, 1 ............................................................ 694
error code 1000, 1001 ................................................ 692
error code 1002 .......................................................... 693
error code 1003 .......................................................... 693
error code 1004 .......................................................... 693
error code 2000 .......................................................... 694
VC Port Reset DSP Test (#1106) .......................................695
error code 1000, 1001 ................................................ 695
error code 1015 .......................................................... 695
error code 2000 .......................................................... 695
error code 2012 .......................................................... 696
error code 2100 .......................................................... 696
videos ................................................................................ 780
view alarms
CLI ................................................................................ 19

Avaya Communication Manager Alarms Events and Logs Reference R10.2.x Dec2023

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Avaya Communication Manager Alarms Events and Logs Reference R10.2.x Dec2023

Uploaded by

Copyright:

Available Formats

Avaya Aura® Communication Manager

Alarms, Events, and Logs Reference

- Maintenance technician located at a remote maintenance facility

Discontinued support for IP Server Interface (TN2312,

Alarms in Linux servers

Setting up external notification for events

Event ID Link to description

Alarm text Interchange handoff failed

Alarm text Arbiter in invalid/unknown state

Alarm text Both servers thought they were active

Alarm text Cannot create receive socket.

Alarm text Interchange without doing prep

Alarm text Heartbeat timeout from ACTIVE

Alarm text Standby failed to come back up

Verifying the server status using the Web interface

Verifying the server status using the command line

String pairs of ARB Event # 9

Event ID Link to description

Alarm text Scheduled backup was terminated

CMG (Common Media Gateway)

DUP (Duplication Manager)

Event ID Link to description

Alarm text Duplication link down

Survivable core server

Event ID Link to description

Survivable core server Event ID 5

Survivable core server Event ID 6

Survivable core server Event ID 7

Survivable core server Event ID 8

FSY (File Synchronization)

Event ID Link to description

FSY Event ID 1 - 999

Alarm text event string (server): [server address] type

The event string can be one of the following:

FSY Event ID 1000 - 1999

Alarm text event string (prescript): [fileset name] type

GW_ENV (Gateway Environment)

Event ID Link to description

Alarm text AvEntFanFlt - Fan fault

Alarm text AvEnt48vPwrFlt - 48v Power fault

Alarm text AvEnt48vPwrFlt - 48v Power faultAvEnt5vPwrFlt - 5v Power

Alarm text AvEnt3300mvPwrFlt - 3300 mv Power fault

Alarm text AvEnt2500mvPwrFlt - 2500 mv Power fault

Alarm text AvEnt1800mvPwrFlt - 1800 mv Power fault

Alarm text AvEnt1600mvPwrFlt - 1600 mv Power fault

Alarm text AvEntAmbientTempFlt - Ambient temperature fault

Alarm text avEntPhyChFruRemoval - Field replaceable unit removal

Alarm text avEntPhyChFruPsuFlt - Power supply fault.

Event ID Link to description

Alarm text OVERLOAD CONTROL LEVEL 1

Alarm text OVERLOAD CONTROL LEVEL 2

Alarm text corevector set

Alarm text DEMO CERTIFICATE IDENTIFIED

Event ID Link to description

Alarm text SAT_auth:Login for [inads] invalid password

Login Event IDs 10, 11, 12, and 13

Alarm text Login for [linux] – failed – password check

S8300 Servers login alarms

Table 9: S8300 Server Login Alarms

Event ID Link to description

_PE (Processor Ethernet) alarms

Event ID Link to description

_PE 1 Minor alarm: PE Health Check device is not responding

Alarm level MIN